As you probably know EteSync is now supported natively by both KDE and GNOME. This means that you can now add EteSync accounts directly to GNOME, KDE and apps in their ecosystem such as Evolution, GNOME Calendar, Kontact and the likes.

This has been possible for a very long time using the DAV bridge, though with these integrations, the bridge is no longer needed.

As we said in the original announcement, the integrations will be released and packaged in distributions following the next GNOME and KDE releases. However, a lot of you have been asking about starting to use it now, and we can't blame you, as we wouldn't want to wait either! :)

Thanks to some hard work by daftaupe, sjolly, and others, there are now easy to use packages available for multiple distributions!

For the most up to date packaging information, please refer to the GNOME user guide and the KDE user guide. We are working on packages for more distributions every day. However at the time of this writing there are already packages for Arch (AUR), Ubuntu, Debian, Fedora, CentOS, OpenSuse and Mageia depending on whether you use Evolution or KDE. In addition, if your distribution isn't listed above, you can always just build the plugins from source.

Do you know how to create packages for your favourite distro and are willing to help? Need any help with setting up the modules? Please join us at the chat (IRC/Matrix/Web) and let us know!

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!

We are very excited to announce the official release of EteSync 2.0!

This would not have been possible without the hundreds of testers that helped us make sure everything is solid! So thank you all!

If you already know what EteSync 2.0 is and just want to upgrade your account, please refer the EteSync 2.0 migration guide.

As we said in the post announcing EteSync 2.0, time flies. We still can't believe it has already been three and a half years since EteSync was first released. It started out as a simple end-to-end encrypted sync solution for Android. We have since added support for sharing data with other users, and we now have clients for the desktop (DAV bridge), the web, and iOS, built-in support in and Tasks.org, and there are add-ons being built for GNOME, KDE and Thunderbird.

What is EteSync 2.0?

EteSync uses the EteSync protocol (now Etebase protocol) behind the scenes to power all of the apps. While the existing protocol has served us well, it limited our progress and prevented us from achieving some of the things we would like to achieve for EteSync, so after three and a half years, it's finally time for a major protocol upgrade.

EteSync 2.0 is a great improvement over the 1.0 version, while still maintainig everyone's favourite features and capabilities, including, end-to-end encryption, sharing and a full version history. However, since so much has changed under the hood, EteSync 2.0 and 1.0 are incompatible, and you need to migrate your account to 2.0 in order to start using it.

What does it mean for you?

It means we are finally be able to offer some long awaited and often requested features such as notes synchronization and secure location sharing. It means that your sync is faster. It means the EteSync applications are simpler to develop, which means they are easier to improve. We are already seeing these benefits in all of the apps, which already work much better, and helped us reduce large amounts of code.

In addition, there are a lot of user-facing improvements and changes, including:

1. EteSync 2.0 uses usernames for identification (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. This makes it more secure than before but much easier to use. 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 to.
5. "Journal" has now been renamed to "Collection", which is a more accurate term and people find it less confusing.
6. You can now easily change your account's email address directly from the dashboard.

What's next

The above is just the tip of the iceberg. The biggest benefit of changing to EteSync 2.0 is not how it improves things, but rather what it enables us to do next!

Thanks to EteSync 2.0 we were already able to release EteSync Notes. Additionally, as we said in the previous post, we aren't ready to get into details just yet, but we plan on bringing in some long-awaited features such as secure location sharing. Expect a few more announcements in the coming month or two which will make EteSync a more complete solution for your data syncing needs!

We also plan on formally verifying the protocol using Verifpal and releasing a formal spec to make it easier for other developers to examine, use and improve it, and potentially making it into a standard.

Upgrade to EteSync 2.0

Upgrading to EteSync 2.0 is very easy. First thing to do is to make sure you've update all of your apps to their latest versions.

As we said above, EteSync 2.0 accounts are incompatible with EteSync 1.0 accounts, so a new account needs to be created. However, the billing for both is linked. The migration tool automatically takes care of linking the billing, so you don't need to worry about that.

For step-by-step instructions please refer to the EteSync 2.0 migration guide.

Developers: easily build end-to-end encrypted applications

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, tasks and notes.

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!

We are happy to announce the first version of EteSync Notes! 🎉🎉🎉

IMPORTANT: EteSync Notes requires an EteSync 2.0 account.

EteSync Notes is the first new app to use the EteSync 2.0 protocol. As we mentioned in a previous post, a big part of the motivation behind EteSync 2.0 is what it enables for the future of EteSync. EteSync Notes is the first fruit of that effort.

Getting started

EteSync Notes depends on the EteSync 2.0 protocol, as such, it requires an EteSync 2.0 account. EteSync 2.0 is still in beta, though it has been tested by many users over the last month and it's been working very well.

To get an EteSync 2.0 beta account, please refer to the beta announcement post.

Once you've migrated your account to EteSync 2.0 (or signed up for a new one), you can start using the notes app!

You can get it from:

• Google Play
• iOS App Store
• F-Droid
• Web client
• Source Code

What's next for EteSync Notes

While this is only the first release, it's already quite stable and feature complete (even includes a dark theme!). With that being said, we are aware that some features are missing, and that there may be some issues. So please, report issues as you find them.

There are a few things missing that we are aware of and plan on addressing soon, namely:

• Labels (tags) for organising the notes.
• File and image attachments.
• Improved markdown support (e.g. checkboxes).
• A rich text editor
• Improve the look and feel of the web client
• Show the revision history per note

Please open a ticket if we missed anything important.

A quick tour

EteSync notes uses Markdown for note formatting. Markdown is a rich formatting language that is easy to write by hand (cheatsheet). In the future we will have a nicer rich text editor that lets you editor Markdown files using the GUI, but until then, you can just use Markdown.

Like all EteSync apps, EteSync Notes support securely sharing notes between users. In order to share a note you need to create a new notebook and share that notebook with other users. After you do that, all the notes in that notebook will be encrypted and shared automatically.

The EteSync Notes app uses the same concepts you are already familiar with from EteSync. This includes a full change history for all of your notes! The change history is not currently visible in the app, but it's all kept behind the scenes.

Thank you NLnet and NGI0

EteSync Notes is based on EteSync 2.0, and 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!

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 identification (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.

There are migration tools available for migrating your account. The easiest is probably the web based migration tool which is available here: EteSync 2.0 migration tool. The Android app comes with its own migration tool. You can access it by clicking on the account you would like to migrate, then the top-right menu, and then "EteSync 2.0 Migration".

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. Edit: billing is now turned on for EteSync 2.0.

Here are links for the EteSync 2.0 compatible apps:

• Android: available on the Play Store and F-Droid.
• Web
• EteSync-DAV (DAV Bridge) - Version 0.30.0 or newer
• iOS: available on the App Store
• GNOME (Evolution): ready
• KDE (Kontact and etc): ready
• 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!

Time flies. It has already been three and a half years since EteSync was first released. It started out as a simple end-to-end encrypted sync solution for Android. We have since added support for sharing data with other users, and we now have clients for the desktop (DAV bridge), the web, and iOS, built-in support in vdirsyncer and Tasks.org, and there add-ons being built for GNOME, KDE and Thunderbird.

All of the above was made possible thanks to the EteSync protocol, which remained mostly unchanged during this whole period. However, while the existing protocol has served us well, it limited our progress and prevented us from achieving some of the things we would like to achieve for EteSync, so after three and a half years, it's finally time for a major protocol upgrade.

What does it mean for you?

It means we will finally be able to offer some long awaited and often requested features such as notes synchronization and secure location sharing. It means that your sync will be faster. It means the EteSync applications will be simpler to develop, which means they will be easier to improve.

We will also change the EteSync usernames to be actual usernames instead of based on the email addresses. This will make it easier to support changing the email addresses you use with EteSync.

The above improvements 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!

In addition, the new version of the protocol will be formally verified using Verifpal and will be based on the widely used and audited libsodium, which together will provide very high confidence that everything is as secure as it should be. We also plan on releasing a formal spec of the protocol to make it easier for other developers to build implementations in other languages.

What's next?

The new version of the protocol is essentially ready, and the server side is fully implemented. We now need to upgrade all of the existing applications to use it. We have already made quite a bit of progress on this front, and we hope to have the web, Android, iOS and DAV bridge all ready for testing within the next few weeks.

After we are certain everything works as expected, we will add migration tools to each of the clients that will easily upgrade your EteSync accounts to EteSync v2.

Until then, we would love to get some help with making sure everything works as expected, if you are interested in helping out please reach out to us at the community chat (IRC/Matrix/Web), or email us at v2-testing@etesync.com. Edit: testing is now open for everyone! More information at the new blogpost.

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.

With this new version of the protocol, the client libraries have been designed with 3rd party developers in mind, making it easier than ever to use the EteSync libraries in your apps. If you are interested, please let us know by emailing us at contact@etesync.com.

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.

If you are working on such a project and think you can make a big difference with some financial help, I suggest you apply here.

More specifically, if you have any cool project ideas related to EteSync please apply, or reach out to discuss it. We will be happy to help you with the application, and do our best to help with your actual project.

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!