That includes a synchting-share for my automatic backups and my "dropbox" replacement (a simple directory for syncing between phone, and computers).
It works great. I haven't had any issues with it. The current release of syncthing is very stable. Earlier versios were a bit error prone. But they seem to have fleshed out most, if not all bugs i encountered in earlier versions.
- ec2 instance (light burstable, always on)
- desktop (debian)
- laptop (manjaro)
- desktop (windows)
- phone (one-way sync to get photos off the phone)
- tablet (kindle fire)
It has been great. Solid and trustworthy. It picks up changes made before the service was running, handles deletes and renames just fine, and updates are simple. The web-based UI is good.
I like that calmh and the team are not adding lots of features. There are lots of things they could add to make syncthing "better", but they want to make sure syncthing does one thing well.
One nit - the UI shows the "latest change" for each folder. The common understanding of this phrase would be "the file in that folder that most recently changed" but what syncthing actually shows here is "the most recent change that syncthing made to this folder". That means that if I change a file on the current device and syncthing picks it up and replicates it out to the other devices, that change will not be shown as the "latest change". If some other device changes the file and syncthing replicates that change back to the current device, then it will be shown as the "latest change". This is confusing. "latest change" should just show the file that most recently changed for any reason.
Setup:
* Camera: 1.8 GB, 243 files
* Documents: 10.8 GB, 4604 files
* Music: 61.5 GB, 25077 files
* Passwords: 660 KB, 726 files
* Pictures: 16.5 GB, 6450 files
The passwords are managed by 'pass' [0], which is viewable on my phone using Password Store [1]. Cold-launching Syncthing takes ~10 seconds on my phone, but it does it automatically on boot and thereafter runs in the background. Battery impact seems to be negligible.
[0]: https://www.passwordstore.org/
[1]: https://f-droid.org/en/packages/com.zeapo.pwdstore/ and https://play.google.com/store/apps/details?id=com.zeapo.pwds...
Now I use Tresorit (which I only became aware of because of... and online ad!?) It doesn't seem to have sync issues for me. Dropbox didn't have issues either, but it wasn't as secure.
I wanted so badly for Nextcloud to work.
The ability to have untrusted nodes is the one feature that has kept me using Resilio Sync.
plain <-> syncthing <-> phone
^
|
V
encfs <-> syncthing <-> dropboxSome syncthing nodes could host only the encrypted data, without the keys to decrypt them. This adds the benefit of having some nodes host the data, without being able to access it. Think: VPS, etc. that have very good availability track record, but some doubts about whether your hosting company can spy/might be coerced into spying.
https://github.com/syncthing/syncthing/issues/109
https://www.bountysource.com/issues/1474343-support-for-file...
https://forum.syncthing.net/t/encryption-for-remote-syncthin...
Unfortunately there doesn't seem to have been much movement towards making it a feature.
Sounds risky.
Do storage providers have an incentive to provide the service reliably à la filecoin? [0]
For other kinds of Tahoe deployments, no there's nothing built-in to incentivize storage-server operators. That part is up to whomever is organizing and running the Grid (what Tahoe calls a group of storage-servers). For example, friends could agree to host storage-servers for each other and create redundancy + trust that way.
The difference between Tahoe and things like Storj / FileCoin is that those services intend to be "a single, global service" whereas Tahoe is software that can be deployed in several different ways -- one of which is a professionally managed Grid such as PrivateStorage.
If you are interested in these topics I'd encourage you to join #tahoe-lafs on Freenode or one of the Tahoe development meetings. These are definitely things I've seen discussed but I think Tahoe-LAFS is far more likely to introduce a concept of "federated Grids" rather than "a single global Tahoe service".
We are working to make doing even this as user friendly as possible.
Yes, via a currency called Dollars.
Making user owned storage user friendly for people with non sys admin skills is a challenge, but something we are working towards.
because our gaia hubs are associated with user's ids, we are also working on automating SSL as much as possible for individual users as well. This is another technical challenge that makes it difficult for the average person to set up their own trusted environment where they control their own data.
So if you happened to "not completely trust" the availability of those you could also configure one of your own and configure your client(s) to use that and the PrivateStorage servers. That is, hedging against PrivateStorage going away so suddenly you can't retrieve your data.
But, I agree: if you're doing that you're likely able to run your own Tahoe grid on VPSes or similar.
I'm not sure that PrivateStorage actually adds anything to the equation?
EDIT> The Tahoe LAFS [2] model is more that you spread your data over multiple providers. NAS at home, several VPS providers, or what have you. It feels like RAID in the network, and it allows very precise setting of redundancy policies.
So syncthing actually only runs on trusted machines, whereas PrivateStorage will be able to run on both trusted (tightly managed) and untrusted machines (like a VPS in the USA).
[0] https://syncthing.net
[1] https://try.popho.be/byeunison.html
[2] https://tahoe-lafs.org/trac/tahoe-lafs