Vote on this issue on the forum!
There are two usage issues with ActivityWatch at the moment to which syncing is a solution:
- If you use more than one device, you need to check every device individually, or run one centralized instance of aw-server (not recommended!)
- If a machine is lost, so is the data (the user could have exported it, but data stored after the export would still be lost). While ActivityWatch cannot replace a proper backup system, syncing could help by storing copies of the data across devices.
I know of two interesting solutions to this problem:
- Centralized server which stores all data encrypted (the server is unable to decrypt)
- P2P synchronization (encrypted, possibly including relays)
- Done by @syncthing very well, perhaps we could use it in some way. Also: MPL2 licensed and written in Go.
- Downside: Clients must be online at the same time for sync.
- They have the ability to set some folders to "read only", useful when you want to ensure the data stays intact in its source.
- Implementing it ourselves would be an enormous effort, I assume.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Vote on this issue on the forum!
There are two usage issues with ActivityWatch at the moment to which syncing is a solution:
I know of two interesting solutions to this problem:
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.