Syncing

**Vote on this issue on [the forum](https://forum.activitywatch.net/t/synchronization-between-devices/264)!** ----- 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) - Issues: Centralized, single point of failure - Done by @StandardNotes - 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. <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/43187921-syncing?utm_campaign=plugin&utm_content=tracker%2F35920020&utm_medium=issues&utm_source=github)** We

Posted by ErikBjare on Mar 18, 2017, 11:16 PM

Tags

• github (Sysadmin)

Related issues

• Custom games stuck on "finding server" for all european servers
• Feature request: add ACP (Agent Client Protocol) stdio JSON-RPC mode
• Forza Horizon 6 (2483190)
• Turn off integrated browser for default
• Weekly updates are too frequent
• [BUG] Max 20x plan: 100% usage after 2 hours of light work (5 commits, no agents)