I have looked into Syncthing and I found that their E2E setup is too daunting. In contrast in Resilio Sync one can share read/write key and be settled with it easally. If security is of concern one simply puts an expiration time on the key.
> I have looked into Syncthing and I found that their E2E setup is too daunting.
Are you referring to untrusted devices? That is different than e2e encryption. Synching is e2e encrypted by default. Synching relays are only used when a direct connection with a peer is not possible. When a relay is used the data is encrypted. The relay cannot read it.
When I last checked and started the Syncthing setup wizard, I got the impression that to set up the synchronisation between devices A and B; I would have to paste the public key of B in A and the public key of A in B, which is more complex than initialising this step with a token key as Resilio sync does it.
Furthermore, it prevents its use as a public bulletin board where the server can share a read key and allow anyone to keep a copy of the data. I am developing an E2E evoting app where that would have been useful.
No, to setup two devices you have to add the id of A into B (you can even scan the qr code), wait for B to be contacted, and from B accept the invitation. Repeat for each folder (there's a setting where you cao automatically accept all folders from a given peer, off by default).
You can also define that one folder on a given device (say a server) never accepts remote changes from anyone else, or never propagates local changes to anyone else. Combine this with encryption (provided by syncthing if you so desire, or your own) and versioning (also provided by syncthing if you want) and you have a pretty good backup endpoint.
I invite you to try out syncthing deeper, the doc really doesn't do it justice. However keep in mind that it's supposed to be used on devices that will be manually deployed. It's not made for large scale deployments.
