|
|
|
|
|
by blindm
1965 days ago
|
|
Baking in automatic crypto to email is a lost cause, since email is not as straight-forward as let's say Signal, which only succeeds because it exists in a monoculture (iOS/Android). Email operates on 100s of different clients (and operating systems), and you get people replying-to-all by mistake, and fat-fingering sensitive data to random recipients (which is possible in Signal, but not nearly as bad as e-mail where e-mail can exist in any hostile environment it wants, unlike Signal which has a user which is more careful about what he/she sends). |
|
Could you explain why Signal users are more careful than email users? Aren't all Signal users also email users?
I suppose the reverse isn't true, and there are machines that send people transactional emails (e.g. receipts for online purchases) which it would be nice to secure with PGP.
The real problem with securing email, from my perspective, is the difficulty of creating a UX which accurately and intuitively conveys to the user whether the message they are sending is secure (and what "secure" means). By using a separate app which never sends plaintext, that's basically a non-problem.