Brian Richmond
My feedback
3 results found
-
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.
Brian Richmond
supported this idea
·
-
6,472 votesBrian Richmond
supported this idea
·
-
515 votes
An error occurred while saving the comment
This is only a presumption, but as this service is focused on privacy and many of the spell check functions used by other services force a call back to "the server" the reason is self explanatory from that perspective. From the idea of the code for spell check being included with the code for the email function I am presuming it has to do with code maintenance, and focus on providing what they intended without scope creep causing the program to bloat. I hope my guesses as to why aren't too far off, and I would rather keep the privacy over convenience mentality intact.