We are happy to announce that EteSync 2.0 is now ready for testers! Are you interested in helping us with testing? Please read on! Not sure what is EteSync 2.0? Please read our previous post on the topic.

Introduction

We have been working on EteSync 2.0 for the last six months, though in a sense for a lot longer. It incorporates a lot of the feedback we got from you over the years, and the things we have learned in the three and a half years of running this service. As mentioned in our previous post, a lot of the changes are behind the scenes and will enable us to build on top of, though there are a few changes that are worth mentioning here again as they are important for testers.

  1. EteSync 2.0 uses usernames for indetification (rather than emails previously), so you will need to choose a new username. Usernames should be at least 6 characters long. Shorter usernames will probably be allowed in the future. Changing your email and username will both be possible later on.
  2. EteSync 2.0 has just one password that's used for both the encryption, and the login. It uses a zero-knowledge proof to authenticate to the server making sure your password never leaves your device. Please make sure to keep it safe and don't lose it, as without it you won't be able to access your data!
  3. The change log (previously change journal) used to show all of the changes in one long list. Changes are now grouped per item with only the latest changed shown. To show previous changes you need to click on an item and check the past revisions.
  4. Invitations UI is a bit different, and there's now a special page for accepting or rejecting invitations, and it's now also easier to leave collections you've been invited for.
  5. "Journal" has now been renamed to "Collection", which is a more accurate term and people find it less confusing.

In addition to the above, we also improved the clients while working on them. Especially the web UI which should now be faster and easier to use than ever. There may also be some other changes we forgot to mention.

How to start testing

As mentioned above, EteSync 2.0 uses usernames instead of emails and has a different authentication mechanism. This means that EteSync 2.0 accounts are internally new accounts that need to be created.

If you are new to EteSync and would like to give it a go, you can signup directly from the new web and Android clients (links below).

If you already use EteSync 1.0, there is a migration tool that automatically handles both the account creation and migrating your data over (including the full change history). It's currently only available for the web client, but will soon also be available for the Android and iOS clients.

The web based migration tool is available here: EteSync 2.0 migration tool. The migration tool only copies your data over, so if you change your mind, you can always go back to version 1.0. Just be aware that new changes made to 2.0 won't sync back to 1.0 and vice-versa, so you will have to copy them over manually if you change back to 1.0.

To make testing easier, billing is currently disabled for EteSync 2.0 accounts, they are all on infinite trials. We will however turn billing on for all EteSync 2.0 accounts in the next few weeks, and will automatically link your existing EteSync accounts to the EteSync 2.0 accounts using your email address so billing information will be transferred over automatically.

Here are links for the EteSync 2.0 compatible apps:

  • Android
  • Web
  • EteSync-DAV (DAV Bridge):
  • iOS: available on the App Store
  • GNOME (Evolution): coming soon
  • KDE (Kontact and etc): coming soon
  • External apps:
    • OpenTasks: works.
    • Tasks.org: works with the new OpenTasks-like integration.

What is there to test? Everything. A few of us already use EteSync 2.0 instead of EteSync 1.0 and it works very well, however we realise that there may be some bugs lying around. So please, report every issue you see. You can do it either in the respective bug trackers, by mail, or our chat (see links at the bottom of the post).

We are aware that not all of the strings have been updated (e.g. some dialogs still refer to 1.0 journals), and on Android we still haven't implemented restoring an item to a specific state or sending email invitations, and the signup flow needs some more work, but other than that, everything should work. So please, report every issue you encounter.

If you are self-hosting, the server is available here, though it doesn't yet have all of the easy-config stuff that EteSync 1.0 had that made self-hosting easier. We will port them over in the coming weeks.

What's coming soon

As said in the original post, EteSync 2.0 brings with it a lot of improvements, but in addition to the improvements to the existing EteSync apps, where it really shines is what it enables us to do next.

We aren't ready to get into details just yet, but we plan on bringing in some long-awaited features such as notes synchronization and secure location sharing. These, however, are just the tip of the iceberg. We have a lot more coming, so expect a few more announcements in the coming month or two which will make EteSync a more complete solution for your data syncing needs!

As for the EteSync 2.0 release itself, we don't have an exact date yet, but it's imminent. There are no major bugs that we are aware of, and everything seems to be working well. We would just like to have more people test it, so we can be extra sure that everything works as smoothly as it should.

Developers: using the EteSync protocol in your app

Over the years many developers have reached out to us about adding end-to-end encryption to their applications. Building end-to-end encrypted applications is both hard to get right, and very time consuming, so using an existing solution makes a lot of sense, especially since EteSync is versatile and isn't limited to contacts, calendars and tasks.

We are now also ready for developers. For more information, please take a look at the developer homepage (Etebase).

Thank you NLnet and NGI0

The work on EteSync 2.0 is made possible with financial support from NLnet Foundation, courtesy of NGI0 Discovery and the European Commission DG CNECT's Next Generation Internet programme.

The NLnet foundation in general and the NGI0-PET in particular is funding projects to protect everyone's digital privacy, especially in the context of the "next generation" of the internet. It's an extremely important cause which we at EteSync are very much aligned with. Please help by spreading the word about them.


As usual, we would like to remind you that we rely on your feedback and contributions to make EteSync better. Do you have any suggestions or  are experiencing any issues? Please send patches, report issues or just contact us.

Come chat with us on IRC/Matrix, or follow us on Mastodon, Twitter, Facebook, reddit or RSS for the latest updates and privacy-related content!