Thank you for sharing the link to this issue, I was not aware of it. In fact, I think that S3 support would be much more interesting than supporting any specific service.
I would vote against S3 or third-party cloud support in Syncthing. Do one job and do it well.
If you need to sync with S3 or other clouds, rclone does this very well.
Something from RackNerd or LowEndBox (I happen to use a couple of VPS from Backupsy.com, found on LowEndBox; not high performance, but lots of storage), or your home server can run both Syncthing and rclone to be your sync to S3 or DropBox, Google Drive etc.
1 Like
Wouldnât running both Syncthing and rclone (to sync to S3) be prone to sync issues?
As long as they are not overlapping on both sides, I donât think there would be conflicts. Syncthing and Rclone have separate âdatabasesâ that they use for sync de-confliction.
For example, Syncthing manages A<->B, Rclone manages B<->C.
Syncthing warns about overlapping syncs because the same database is used for sync de-confliction, and thatâs where you can get into trouble.
Changes created by Rclone would be seen by Syncthing as local filesystem changes.
Different tools for different needs. I use both without trouble.