You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really thought there was already an issue about this, I remember I've been thinking about it for a long time. Thankfully @Stefano_Agazzi reminded me.
WakaTime is great, it collects useful data which you can get meaningful insights from. Unfortunately, it has a proprietary server-component. Luckily the mechanics are similar so it would fit pretty well with ActivityWatch. This would make building a bridge or modifying a WakaTime client a lot easier than writing custom plugins for one/every editor.
We've actually had WakaTime-like features in mind for a while now, so here are two possible options:
We've learned a lot from how they do things in the past, so modifying WakaTime plugins to work with ActivityWatch shouldn't be too much work.
We could build a bridge or API which acts as WakaTime would but really used ActivityWatch as a server and user interface. This could avoid having to make any modifications to the clients, essentially just a configuration change (proxy config).
Activity
[-]WakaTime bridge/forks[/-][+]Support for WakaTime clients using a bridge or by forking them[/+][-]Support for WakaTime clients using a bridge or by forking them[/-][+]Support for WakaTime clients[/+]ErikBjare commentedon Nov 6, 2017
Moved to forum: https://forum.activitywatch.net/t/support-for-wakatime-clients/38
fix(ci): bump MACOSX_DEPLOYMENT_TARGET from 10.9 to 12.0
fix(ci): bump MACOSX_DEPLOYMENT_TARGET from 10.9 to 12.0 (#1363)