burnersk
My feedback
67 results found
-
27 votesburnersk
supported this idea
·
-
13 votesburnersk
supported this idea
·
-
224 votesburnersk
supported this idea
·
-
458 votesburnersk
supported this idea
·
-
302 votesburnersk
supported this idea
·
-
408 votesburnersk
supported this idea
·
-
1,399 votesburnersk
supported this idea
·
-
435 votesburnersk
supported this idea
·
-
141 votes
An error occurred while saving the comment burnersk
supported this idea
·
-
2,960 votes
Partially rolled out, as per: https://proton.me/support/pass-offline-access
As per the Spring/Summer Roadmap this will extend out to the Pass Extension: https://proton.me/blog/pass-roadmap-spring-summer-2026
burnersk
supported this idea
·
-
109 votes
An error occurred while saving the comment burnersk
commented
Proton Mail comes with great features like an address book (Contacts) within Proton Mail and Proton Calendar.
However, due to the privacy nature of zero knowledge (encryption), Proton cannot offer a way to provide their own CardDAV endpoint without either storing the (encrypted) secret/encryption key in their database (bad) or relying on the client to submit the secret/encryption key in every request (very bad).
I use a Nextcloud service to synchronize my contacts and appointments via CardDAV and CalDAV across several endpoint device classes. For example my dedicated VoIP phones, routers with VoIP servers inside, smartphones, and email clients.
On the smartphone there is no issue, because the Proton Mail mobile client offers a combined address book (contacts). While there is no synchronization between the Proton contacts and the smartphone contacts, the mobile app can access both.
The issue comes when using the desktop client or the web client. Here there is no combined address book (contacts). Only the Proton-native contacts are known. I can solve this via exporting my main address book as an VCard and import them in to Proton Mail contacts, but this also raises issues (mainly duplicates, and excessive personal efforts which could be used better).
My solution to the issue: Allow the Proton Mail desktop client to subscribe to an CardDAV endpoint and synchronize this endpoint (both directions) with the Proton Mail native address book (contacts).
Proton Mail desktop client should not provide an CardDAV endpoint, but consume/subscribe to an external CardDAV endpoint.This way, I do not waste my time in manual synchronization and deduplication.
burnersk
supported this idea
·
-
145 votesburnersk
supported this idea
·
-
602 votesburnersk
supported this idea
·
-
183 votesburnersk
supported this idea
·
-
251 votesburnersk
supported this idea
·
-
379 votesburnersk
supported this idea
·
-
937 votesburnersk
supported this idea
·
-
1,845 votesburnersk
supported this idea
·
-
23 votesburnersk
supported this idea
·
-
561 votesburnersk
supported this idea
·
Limit suggested credentials ("Login in as...") in-website popup to the selected vault (browser extension). This affects the browser extension. Currently the browser extension popup and its in-website (HTML field) popup does not sync. in-website (HTML field) popup currently does NOT have a feature to select a vault.