Redo the entire Calendar and Contact sync section

[TommyTran732]

1. Put Tutanota on top. Tutanota encrypts the entire Calendar and Contact storage. It also supports 2FA.

2. Etesync should be second. It is recommended mainly because of E2EE, not just because it is self hostable. We will just mention that you can self host it. Here is a docker image made by a well known member of their community: https://hub.docker.com/r/victorrds/etesync. Etesync does not support 2FA though they do plan to add it soon: https://www.etesync.com/faq/

3. Put Proton last. Proton does not encrypt contact names or email address, Tutanota and Etesync do.

4. Remove Nextcloud from this section. There is no reason to use someone else's Nextcloud instance whatsoever because there is no E2EE. If you are looking to self host, well, Etesync exists and actually supports encryption.

5. Remove Desync CC: this is neither "self hostable" or a sync software in itself.

[dngray]

Agreed.

[matchboxbananasynergy]

This makes sense.

[julianfairfax]

1. Put Tutanota on top. Tutanota encrypts the entire Calendar and Contact storage. It also supports 2FA.

   2. Etesync should be second. It is recommended mainly because of E2EE, not just because it is self hostable. We will just mention that you can self host it. Here is a docker image made by a well known member of their community: https://hub.docker.com/r/victorrds/etesync. Etesync does not support 2FA though they do plan to add it soon: https://www.etesync.com/faq/

   3. Put Proton last. Proton does not encrypt contact names or email address, Tutanota and Etesync do.

   4. Remove Nextcloud from this section. There is no reason to use someone else's Nextcloud instance whatsoever because there is no E2EE. If you are looking to self host, well, Etesync exists and actually supports encryption.

   5. Remove Desync CC: this is neither "self hostable" or a sync software in itself.

How is DecSync not self-hostable or sync software? It is only self-hostable by design, and it syncs with a local folder, which that you have to sync using another tool. It's not as easy to use as the other options, but it's completely local and fully integrated with your system unlike Tutanota and Proton Calendar, and fully free unlike EteSync.

[dngray]

The reason we don't recommend it is because it really wasn't designed for this purpose.

Suppose you edit a contact on Device A, and then edit the same contact on Device B. The changes from Device A will be lost as the date is "older".

The problem is that its not a database, and Syncthing has no knowledge about the type of data that it is synchronizing.

It's not designed to work like this. If you're self hosting, you might as well just use EteSync instead as it is better supported and a more robust product.

[julianfairfax]

The reason we don't recommend it is because it really wasn't designed for this purpose.

Suppose you edit a contact on Device A, and then edit the same contact on Device B. The changes from Device A will be lost as the date is "older".

The problem is that its not a database, and Syncthing has no knowledge about the type of data that it is synchronizing.

It's not designed to work like this. If you're self hosting, you might as well just use EteSync instead as it is better supported and a more robust product.

Well if you edit a contact on Device A, it'll be synced to Device B, where you can then edit it.

And while EteSync can obviously also be self-hosted, self-hosting DecSync is a more peer-to-peer experience. You don't have to self-host it on a central server. Each individual device syncs with the rest.

[dngray]

Well if you edit a contact on Device A, it'll be synced to Device B, where you can then edit it.

Only if it's synced to Device B first, it won't be if say you have no network connection.

while EteSync can obviously also be self-hosted, self-hosting DecSync is a more peer-to-peer experience. You don't have to self-host it on a central server. Each individual device syncs with the rest.

Could just host EteSync on one of the two devices, ie Device A. Device A can then connect to localhost. Even Decsync requires an agent like Syncthing to be running somewhere.

[julianfairfax]

Well if you edit a contact on Device A, it'll be synced to Device B, where you can then edit it.

Only if it's synced to Device B first, it won't be if say you have no network connection.

I imagine that's the case with any sync software then?

while EteSync can obviously also be self-hosted, self-hosting DecSync is a more peer-to-peer experience. You don't have to self-host it on a central server. Each individual device syncs with the rest.

Could just host EteSync on one of the two devices, ie Device A. Device A can then connect to localhost. Even Decsync requires an agent like Syncthing to be running somewhere.

You can, but then device C would have to connect to device A rather than be able to connect to devices B and C through Syncthing being able to do so.