@yestalgia So I set up syncthing between a server and one client. Share folders between them. Figure out how you want the folder data replicated; for my phone pics, for example, the sync is one way from (phone) -> (syncthing server). For kids’ health stuff, it’s a two-way sync; because the sync might be (my laptop) <- (syncthing server) <- (my wife’s laptop), or vice-versa. Then add another client to the syncthing server, following the same process. Never sync client-to-client; always via server
@yestalgia I will say that the configuration is not the most intuitive. Part of it is just that the web UI is, imo, not that good. There’s a lot of confusing stuff exposed to users that isn’t really important for like 99% of use cases.
(who cares whether compression is metadata only or all data or none? wtf is “introducer” vs “auto-accept”? why do I need to see a random hash for device or folder id in addition to a device or folder name?)
@yestalgia So I set up syncthing between a server and one client. Share folders between them. Figure out how you want the folder data replicated; for my phone pics, for example, the sync is one way from (phone) -> (syncthing server). For kids’ health stuff, it’s a two-way sync; because the sync might be (my laptop) <- (syncthing server) <- (my wife’s laptop), or vice-versa. Then add another client to the syncthing server, following the same process. Never sync client-to-client; always via server
@yestalgia I will say that the configuration is not the most intuitive. Part of it is just that the web UI is, imo, not that good. There’s a lot of confusing stuff exposed to users that isn’t really important for like 99% of use cases.
(who cares whether compression is metadata only or all data or none? wtf is “introducer” vs “auto-accept”? why do I need to see a random hash for device or folder id in addition to a device or folder name?)