The one remaining hurdle for me is syncing Contacts for use on the ProtonMail webapp, which EteSync doesn't help with.
My phone contacts are stored in a DAVx5 address book synced to a self-hosted Nextcloud instance. I can easily send an email from the phone app to any of my phone contacts. But if I shift across to the web ProtonMail, I no longer have my contact details available to me - only the ones I have added/imported manually.
One solution would be for the mobile app, which is already authenticated against the ProtonMail servers, to sync contacts that are optionally in a specified group (eg, "ProtonMail") between my ProtonMail Contacts and my phone contacts.
Another could be to add functionality to Bridge - as well as being an IMAP/SMTP bridge, it could also act as a Card/Cal DAV bridge - which, when the Proton Calendar arrives, would help to sync back to local calendar clients.
Mark
The one remaining hurdle for me is syncing Contacts for use on the ProtonMail webapp, which EteSync doesn't help with.
My phone contacts are stored in a DAVx5 address book synced to a self-hosted Nextcloud instance. I can easily send an email from the phone app to any of my phone contacts. But if I shift across to the web ProtonMail, I no longer have my contact details available to me - only the ones I have added/imported manually.
One solution would be for the mobile app, which is already authenticated against the ProtonMail servers, to sync contacts that are optionally in a specified group (eg, "ProtonMail") between my ProtonMail Contacts and my phone contacts.
Another could be to add functionality to Bridge - as well as being an IMAP/SMTP bridge, it could also act as a Card/Cal DAV bridge - which, when the Proton Calendar arrives, would help to sync back to local calendar clients.