EteSync – Secure Data Sync
etesync.com
etesync.com
If you are a developer, you may be interested in our related project, Etebase[0], which is an open-source SDK for building end-to-end encrypted applications. Here's the related HN discussion[1].
For those of you that are interested to learn more about EteSync, I was on FLOSS weekly last week[2], and I'll be giving a talk about Etebase at FOSDEM this weekend[3].
[1] https://news.ycombinator.com/item?id=25059133
[2] https://www.twit.community/t/floss-613-etesync-and-etebase/9...
I can integrate with calcurse[1] to stay up to date during the day or with aerc[2] when I need to send an email to someone, because they include a Dav bridge[3], but I can also integrate it with the GNOME environment because a module for evolution exists[4].
Plus, the developer[5] has been genuinely nice and handled all support, and billing questions like a champ, in a speedy manner, and always in a polite tone.
My only problem with EteSync so far is that sharing an event can only be done through the web application right now, so I need to switch from calcurse to a browser, share the event, and then come back. Minor issue in the grand scheme of things, though.
Well worth the price, in my opinion. Might be one of the few services that I do not migrate to a self-hosted instance instead.
[3] https://github.com/etesync/etesync-dav/blob/master/README.md...
[1] https://f-droid.org/en/packages/eu.faircode.email/
[2] https://f-droid.org/en/packages/com.simplemobiletools.calend...
Sharing: you can also do sharing from all of the apps (e.g. Android), but yeah, you can't share from 3rd party apps (yet!).
Perfect for backing up and syncing contacts for those that don't want to give the data to Google etc.
(The one from 3 months ago didn't get significant attention so I don't think we'll mark it a dupe - see https://news.ycombinator.com/newsfaq.html.)
It would mean the server needs to keep an eternal log of operations, and each client must replay the log to perform a full sync.
This works with lightweight data like contacts and calendars.
EteSync focuses on syncing your contacts, calendars, tasks and notes, not just files (yet). Syncthing doesn't do any of that. There are also big advantages in having a server when it comes to efficiency, performance, and battery life (every Syncthing user knows it's a battery hog on Android). There are many advantages in having a server, and end-to-end encryption means you don't have to pay with your privacy or security to get them.
https://www.reddit.com/r/Syncthing/comments/g5fe9l/there_are...
https://www.reddit.com/r/Syncthing/comments/8ra7s7/how_to_av...
https://forum.syncthing.net/t/android-app-consumes-too-much-...
The solution most people resort to is to just disable syncing when not connected to power (which is what I do). Maybe you are lucky, I don't know, but I've always had terrible battery life with Syncthing, and it's a common complaint.
Waiting for the marketing people to start calling disk encryption E2EE...
You can share your collections with other users, so it's definitely end-to-end encryption. Though I'd argue that even if it was just single-player, it was still e2ee, because you have multiple devices and the server is oblivious to the contents of the data. Sure, you could maybe call that client-side encryption to have a different term, but that would just confuse people.
E2EE is a term normally only used when some distinction from a default case is important. It is in a sense a weaker term than just "encryption". It is normally only used for particular cases in messaging.
Something like: "All data is strongly encrypted at all times when off the users devices." strikes me as stronger, better and easier to understand in this case.
The gist of it is: everything is encrypted. We can't see your calendar entries.
Also, as it doesn't directly use CalDAV/CardDAV it depends on a client app. At least on Android, the app syncs to the system calendar/contacts so it works just as seamlessly as Nextcloud's recommendation of DAVx5 or any other contacts/calendar/tasks service in that you can access the data from any standard calendar or contacts application.
Which ends do you mean? It supports TLS, so it's E2EE (between server and client).