Nail
My feedback
4 results found
-
3 votesNail
shared this idea
·
-
6,472 votesNail
supported this idea
·
-
1,914 votes
We have given this quite a bit of thought, but at the present moment, it is not clear the advantages would outweigh the disadvantages.
The biggest problem is search. Encrypting all metadata would break metadata search entirely on the web client as there is still no efficient way to handle search of encrypted data within a browser.
Secondly, metadata encryption’s value from a privacy standpoint is also somewhat dubious. Because we ultimately must deliver the message to the recipient, we must know who the recipient is. At the current time, there still isn’t any proven and viable way to work around this.
Metadata encryption is an area of continued research for us, and when the opportunity arises and the technology for doing this matures, we will definitely implement it in ProtonMail.
Nail
supported this idea
·
-
45 votesNail
supported this idea
·
An error occurred while saving the comment
I have been a paid Proton customer for several years now and being limited to the number of aliases I am allowed to create under my own domain has always been a serious problem for me as well. While restricting the number of aliases customers can create under Proton's domains makes sense I do not understand why we have not been permitted unlimited aliases under our "own domains" registered with Proton. I am aware of the SimpleLogin aliases Proton now provides, but this is not the same thing nor does it allow seamlessly replying to email received through it. Hopefully, Proton will permit paid customers unlimited email aliases soon, this would benefit many customers allowing us to be more productive while having some more functionality with more privacy. Thank you for your consideration.