3 ms·
Depending on your needs, you could try Syncthing [1]. IMO the major functional differences between it and Dropbox are: * You have to provide the servers that
by lfam 11y ago
Depending on your needs, you could try Syncthing [1].
IMO the major functional differences between it and Dropbox are:
* You have to provide the servers that Dropbox provides. I.E. you have to provide the level of availability that you want. [2]
* FOSS licensed.
* Because your data is only ever stored on your machines, you are only limited by your own storage and bandwidth.
[1]
https://syncthing.net/ https://syncthing.net/
[2]
This requirement has actually loosened to some degree because the latest version of Syncthing introduced relay servers. So you still need to provide available storage servers, but you can use relays to overcome partitions in your network.
- Veratyr 11y agoThe first requirement is the one that kills SyncThing for me and why Syncany is more appealing. To sum up my reasons very quickly: - I want to store my data offsite, where it isn't vulnerable to breakins, fire, water damage etc. - I have no offsite storage I can trust completely. - Syncthing only supports storing plaintext on disk. Therefore I can't use syncthing to securely and remotely store data. This is where Syncany wins. You don't have to trust the storage endpoint. Also, Syncthing requires having a CPU attached to your remote storage, meaning your remote options are limited to a VPS or dedicated server. This is significantly more expensive than buying block storage from Google or Amazon. If Syncthing ever resolves https://github.com/syncthing/syncthing/issues/109 https://github.com/syncthing/syncthing/issues/109 I'll be open to using it, until then it's out.