Comment by allan_s
8 hours ago
I also agree on "for personal things we don't need SaaS" and I would say do we even needs self hosted in the sense of a central server.
By that I mean, could we have like for firefox , heavy clients but with client to client sync. The goal is to not need to have a always online machine while still solving the "i prefer if my emails are copied both on my laptop and my phones" . Especially as nearly all my devices are often if not always on the same LAN
Firefox sync clearly requires a central server. For any kind of peer to peer syncing to work you must have the machines on at the same time and accessible. And then there is the issue of NATs, including CGNATs. To work reliably these almost always have to have some kind of relays anyway (Tailscale's DERP, Syncthing also has relays).
For the experience an average consumer expects, you at a minimum need a central short-lived cache.
Yes sorry I meant firefox not for the way its sync , but in the way its a heavy client you install. As said for me most of my devices will be at some times during the week in the same nat so that no centralized server even short lived should be needed. And for personnal use, I only care if the device I have on me is the one with latest data especially as for most use case I'm the only one reading/ writing , so eventually consistency is not an issue
This year I moved off LastPass, and started using [Syncthing](https://syncthing.net/) to sync my [KeepassXC](https://keepassxc.org/). It works pretty well, but doesn't have any automatic conflict resolution (I've been working on [something](https://github.com/LightAndLight/syncthing-merge) for this).
Next up I'm moving my TODOs off Todoist to something local-first, and plugging that into my Syncthing setup.
Perhaps you might like syncthing?
Yes what would be better is a "libsyntching" that i can plug to a software so that it does not require additional brain power, i.e install Note app on device A and B, pair them once, fire and forget.