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 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!

Even though there's a Thunderbird add-on in the works, and that the GNOME and KDE EteSync plugins are making great progress, it does not mean we have forgotten about EteSync-DAV, the desktop DAV bridge. We are still working hard on it, and we don't plan on stopping in the forseeable future.

As you may know, EteSync-DAV is an EteSync compatibility layer that lets you use EteSync with any CalDAV and CardDAV supporting client such as Thunderbird, Evolution, Outlook and Calendar.app. You just run it locally, point your DAV client to it, and all of the encryption and syncing is handled automatically for your in the background.

There have been been two major changes in the most recent DAV bridge release that greatly improve the user experience! In summary, syncs are faster now, and they happen more often if your DAV client requests it. Additionally, if you use want to use SOCKS proxy (e.g. Tor), you can now do it!

Changing the sync to being semi-synchronous

As you may remember, we have previously improved the DAV bridge to work in an asynchronous manner. If you don't remember why we did it, please take a look at our previous post on the topic for more information. Here is how it looked before the most recent page (picture taken from the previous post):

This improvement was great and made everything faster by doing the syncs in the background. The main problem with this change though is that as you can see, the DAV bridge is replying to Thunderbird before it finished fetching data from the server. This means that EteSync DAV may return stale information!

This is not an issue in most cases, as the sync happens automatically in the background, but it was very annoying when testing things, because you are not getting immediate feedback, and was very confusing for users.

We have no changed it so that the sync happens in the background, like before, though unlike before it now also tries to wait for a short period of time to see if it's able to return fresh information before giving up and returning stale one.

Socks proxy support

A lot of people use proxies for various reasons, for example if their corporate environment requires using one, or if they use Tor for example.

The DAV bridge has always supported proxies, though due to an oversight, the docker image and the pre-built binaries didn't have this support included. This has now fixed, and you can finally use SOCKS proxies with the most recent DAV bridge version by setting the HTTPS_PROXY (https_proxy on some platforms) enivornemnt variable and launching the DAV bridge.

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!

Last week we wrote a post about an issue affecting some DAV bridge users due to the new Radicale 3.0.0 release. We are happy to announce that we have updated the DAV bridge's code according to the changes in the new Radicale release, and that the issue is now resolved.

In the process of adjusting the code to the new Radicale changes, we also cleaned up a lot of the DAV bridge code, made some improvements and fixed some bugs. So go ahead and upgrade to the latest version of the DAV bridge, or read on for more information on what's changed.

Bind both IPv4 and IPv6 by default

It's now possible to bind multiple hosts to the same server. This means you can e.g. have the server listen on both 192.168.10.12:37358 on your local network, and 10.0.0.2:37358 on your VPN at the same time without having to listen to every address. This is nice, but where this change really shines is the ability to listen on both IPv4 and IPv6 at the same time. So you can for example set the ETESYNC_SERVER_HOSTS variable to 0.0.0.0:37358,[::]:37358 to listen on both IPv4 and IPv6 and on all addresses.

As part of this change, we also made it so the DAV bridge listens on both IPv4 and IPv6 by default when bound to localhost. Without it, the DAV bridge wasn't working as expected on IPv6 only environments.

Prevent loading of the default Radicale configuration file

This issue only affected a small portion of the users. Specifically users who have Radicale installed and configured locally regardless of EteSync.

We used to ship the DAV bridge with a configuration file in order to configure the Radicale dependency. We later improved the DAV bridge to no longer require this external file. The issue is however, that without the file Radicale was trying to load one anyway, which could cause the DAV bridge to load bad configurations.

Fix error mesage for wrong encryption passwords

This issue is self-explanatory. Before this fix the DAV bridge was showing a cryptic IntegrityError error message instead of a nice error message indicating that the encryption password is wrong.

Make it possible to shutdown the DAV bridge from the web UI

Another self-explanatory issue. It's now possible to shutdown the DAV bridge directly from the web UI. This makes it much easier to restart the DAV bridge, especially on Windows.

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!

As you probably know, Shashwat Jolly and Nour E-Din El-Nhass are working on native EteSync support support for both KDE and GNOME (Evolution) during this year's Google Summer of Code, and John Bieling (creator of TbSync) is working on a native Thunderbird add-on (delayed due to COVID-19). After these projects are finished, users of the above desktop clients won't need the DAV bridge any more, and can just use EteSync directly!

However, we are still improving the DAV bridge as it is still needed for applications where EteSync can't be, supported natively such as Contacts.app (macOS) and Outlook (Windows).

As for the DAV bridge: we made a few nice improvements, and we have an important update to share on an issue that may affect some users.

Radicale v3 issue

The desktop DAV bridge utilises Radicale (an open source DAV server) under the scenes. After a long time without a release, Radicale has now released version 3! This released changed quite a few things with both how the app works and the plugin system, which unfortunately breaks the DAV bridge too.

We still haven't managed to assess exactly how much we need to change to adapt to these changes. We have more than a few changes that can (and should) be merged into Radicale, but we are unfortunately unable to reach the devs and our PRs have been ignored so far. If you know any of the Radicale devs, pleaes let us know, as we would love to chat with them!

What does it actually mean for users of the DAV bridge? If you are using the prebuilt binaries, the Docker images or running it in your own python environment: you are unaffected. If you are using a Linux distribution that hasn't updated to Radicale v3 yet, you are fine too. The only people affected are the ones using distributions (such as Arch) which have already updated to the latest Radicale.

In case you are affected, there are a few workarounds you can employ. You can find more information and tune in for updates in the relevant ticket.

Fixed address books showing as calendars

There is a bug in Radicale that was causing address books to show as calendars, task lists and note collections in addition to address books, only in Evolution. For the longest time we assumed it was an issue with Evolution. Today, after spending a lot of time with the Evolution developers we realised it was actually a bug in Radicale. We finally added a workaround for this issue, and it's now been fixed.

Made the sync much faster

In addition to previously making the sync run asynchronously, we now made it much faster by only fetching collections that have actually changed instead of checking all of them every time. This makes sync much faster and also saves battery life on laptops.

Made packaging easier

The DAV bridge is being packaged for more distributions every day (more on that in a future post), and we have been working with package maintainers on making sure packaging is as easy as it should be. As part of that we managed to remove our dependency on pyscrypt, so there's no one less dependency for packagers to worry about! If you would like to package the DAV bridge for your favourite distro, let us know, and we may be able to help.

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!

If you follow this blog, you already know that there's a native Thunderbird add-on in the works (hopefully with a version out soon), and probably GNOME (Evolution) and KDE integrations will be worked on in this summer's Google Summer of Code and Outreachy. After these projects are finished, users of the above desktop clients won't need the DAV bridge anymore, and can just use EteSync directly!

Even with these exciting projects in the works, we still haven't forgotten about the desktop DAV bridge! The DAV bridge is still needed for applications where EteSync isn't, or can't be, supported natively such as Contacts.app (macOS) and Outlook (Windows).

There have been a few major improvements to the desktop DAV bridge, recently, here are the highlights.

Initialise new accounts

Since EteSync is end-to-end encrypted, the server can't access user data. This is a great thing, and why we created EteSync in the first place, however it also means that most of the logic needs to be implemented in every client, and this includes the DAV bridge.

Specifically, until recently the DAV bridge would not initialise new accounts, but instead just assume that the account has already been initialised by another client, such as the Android or the web one. Most people wouldn't even notice it because they use multiple clients anyway, but those that were using EteSync only on the desktop needed to first login from another client in order to properly use EteSync.

Not having to open another client makes the on-boarding for new desktop-only users much smoother.

Management UI improvements

The desktop DAV bridge can be configured in one of two ways. The first is using the command line interface, and the second (recommended) way is through the web management UI. We made a few improvements to the management UI recently, but the most notable one is the unification of the DAV server with the management UI server.

Before this change, the main DAV bridge url was http://localhost:37358 and if you opened it in the browser, it would redirect you to http://localhost:37359 which was the management UI. Notice the slightly different port numbers. A lot of people found this very confusing, and more than once we saw people trying to use the wrong URL in their DAV clients.

It took a bit of tinkering, but we finally managed to get both services to run from the same port (and thus URL), with the management UI being redirected to automatically when opened from the browser.

A few more bug fixes and improvements

We fixed an issue that was causing a high CPU usage when there was no internet connection. The issue was in the error-recovery logic. The DAV bridge is designed to try again on error and wait a certain amount of time between retries. However, in some cases it would skip the wait and get into a loop of trying and failing, driving up the CPU usage.

We also fixed an issue with the local cache getting locked which could cause syncs to fail with multiple concurrent requests. This was because we were using the underlying database (SQLite) instead of the more appropriate WAL mode.

In addition, we also changed the location of the DAV bridge's data directory. Due to legacy reasons, the DAV bridge was saving its data in the user's configuration directory (~/.config/etesync-dav on Linux) instead of the user's data directory (~/.local/share/etesync-dav on Linux). Most users won't even notice the change, but we are happy to have finally fixed this legacy relic.

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.

Follow us on Mastodon, Twitter, Facebook, reddit or RSS for the latest updates and privacy-related content!

Even though there is a native Thunderbird client in the works, it does not mean we have forgotten about EteSync-DAV, the desktop DAV bridge. It's quite the contrary.

As you may know, EteSync-DAV is an EteSync compatibility layer that lets you use EteSync with any CalDAV and CardDAV supporting client such as Thunderbird, Evolution, Outlook and Calendar.app. You just run it locally, point your DAV client to it, and all of the encryption and syncing is handled automatically for your in the background.

Many people rely on it for syncing their EteSync contacts and calendars with their favourite desktop clients, and while it got the job done, there were two major issues that were affecting many users. The first was slow sync times for users that were geographically far from our servers. The second was that contact photos were not being synced. Both of these have now been fixed! You can get the latest changes by updating to version 0.13.0.

If you are interested in some more technical details, please read on.

Slow sync times

EteSync-DAV serves as a proxy between your DAV desktop clients and the EteSync server. This means, that when your desktop client (e.g. Thunderbird) initiates a sync with EteSync-DAV there are a few syncs going on behind the scenes.

Let's use Thunderbird as an example desktop client. When syncing, Thunderbird would first initiate the sync with EteSync-DAV, then EteSync-DAV would initiate a sync with the EteSync server, wait for it to finish, and only then would it send back the fresh information to Thunderbird. The sync looked something like this:

Since EteSync-DAV is run locally, the connection between Thunderbird and EteSync-DAV is quite fast, and the connection between EteSync-DAV and the EteSync server is comparably slow. Though because EteSync-DAV was waiting for the sync with the EteSync server to finish before replying to Thunderbird, the local sync was slow too.

With the new version, we have decoupled the two syncs. The slower syncs between EteSync-DAV and the EteSync server now happen periodically in the background (are also triggered more often if requested by the Thunderbird), so the sync between Thunderbird and EteSync-DAV can be instantaneous. After the changes the sync looks more like:

As you can see, the local sync is now completely independent from the slower remote sync, which makes editing events in Thunderbird and other desktop clients instantaneous.

Missing Photo field when syncing contacts

Before this change, contact photos were not synced when using EteSync-DAV. This was because EteSync uses the newer vCard version 4.0 interally, but Radicale, the Cal/CardDAV server we use to power EteSync-DAV, as well as other clients such as Apple's Contacts.app only support vCard version 3.0. In order to solve this inconsistency we transform between the two versions in EteSync-DAV. Until now, this conversion didn't include the Photo and Logo properties, but with the latest EteSync-DAV these too are now supported.

Feedback, suggestions and contributions

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

In addition, your contributions are always welcome! Be it testing, design, code or helping us spread the word! Every bit helps in making EteSync better for everyone. If you are interested in contributing and don't  know where to start, don’t hesitate to contact us!

Follow us on Mastodon, Twitter, Facebook or RSS for the latest updates and privacy-related content!

Until next time!

The images above use modified icons by Freepik from flaticon.com that are licensed under CC 3.0 BY.

We are very excited to share that John Bieling, the author of the popular TbSync Thunderbird add-on, is working on an EteSync add-on for Thunderbird and TbSync!

With this add-on, users will be able to use EteSync directly from Thunderbird, without the need for the EteSync-DAV bridge. This plugin will drastically lower the barrier of entry, as well as improve the performance and overall experience of using EteSync on the desktop.

This add-on will make it possible for many more users, especially non-technical ones, to end-to-end encrypt and sync their contacts, calendars and tasks.

What's next?

Development has already started, the source code will be pushed to the project's repository as progress is made, and beta versions will be made available as early as possible. Please let us know if you would like to help us with the testing.

For progress updates, please follow us on Mastodon, Twitter, Facebook or RSS, or join our IRC channel at #etesync on irc.freenode.net.

NLnet foundation and NGI0

This work will be done by John with financial support from the NLnet Foundation, courtesy of NGI0 Discovery and the European Commission DG CNECT's Next Generation Internet programme. For more information about the project, please refer to the project page on the NLnet website.

NLnet have also previously supported our work on the iOS client, and it is a great privilege to have another project related to EteSync supported by them. The NLnet foundation in general and the NGI0-PET in particular are funding projects to protect everyone's digital privacy, especially in the context of the "next generation internet". It's an extremely important cause which we at EteSync are very much aligned with.

Feedback, suggestions and contributions

As usual, we would like to take this opportunity to remind you that we want to hear your thoughts. Do you have any suggestions or are experiencing any issues? Please send patches, report issues or just contact us.

In addition, your contributions are always welcome! Be it testing, design, code or helping us spread the word! Every bit helps in making EteSync better for everyone. If you are interested in contributing and don't know where to start, don’t hesitate to contact us!

Follow us on Mastodon, Twitter, Facebook or RSS for the latest updates and privacy-related content!

Until next time!

A lot has been going on in August as we are working hard on further improving EteSync. You can help us do that by filling a short and anonymous survey.

It would be very helpful if you could spare two minutes and fill it to help make EteSync better for us all! Because we don’t profile nor track you, we rely on your feedback to gain insights. Fill the survey here. Thanks in advance!

Now, let’s jump to updates.

Blog

We’ve been writing a lot of new content on this blog and would love to hear your feedback and suggestions on topics you’re interested in so we can write about them, too. Additionally, if you’d like to contribute with your own content, we’d be glad to include it in our blog. Please don’t hesitate to contact us.

EteSync-DAV (Desktop Bridge)

We’ve created a new web UI to manage etesync-dav. We have also made a lot of fixes all around, including fixing sync with macOS’s Contacts.app which stopped working at some point. Compatibility has been improved with other clients as well, like KAddressBook, which hadn’t worked at all previously, and now it works.

Mobile Clients

We have been working hard on the iOS client with financial support from NLNet, and important announcements regarding it are on the way.

The Android client’s icon is now adaptive. We’ve also added a feature of reverting items to a previous state directly from the change journal. So now when you delete a contact by accident, you can undo it in a split second. We have also fixed the contact, calendar and task import.

Go Command Line Client

We would also like to share that gchaincl is creating an EteSync Go CLI client. It’s still in its very early stages, but we are glad to see more great projects in the EteSync ecosystem.

Facebook Page

EteSync has a Facebook page now! Deciding whether to create it was a tough one for us because we are all about privacy and Facebook isn’t the perfect place for it. But we’ve realized that, unfortunately, most people are on Facebook, so we need a presence there, too. If you do have a Facebook profile, don’t forget to like our page.

Feedback, suggestions and contributions

As usual, we would like to take this opportunity to remind you that we want to hear your thoughts. Do you have some suggestions or experiencing an issue? Please send patches, report issues or just contact us.

In addition, your contributions are always welcome! Be it testing, design, code or helping us spread the word! Every bit helps in making EteSync better for everyone. If you are interested in contributing and don't know where to start, don’t hesitate to contact us!

Don’t forget to update your EteSync apps regularly to get the latest fixes and improvements.

Follow us on Mastodon, Twitter, Facebook or RSS for the latest updates and privacy-related content!

Until next time!