4 ms·
> Of course, this also means that there is a UX problem to solve. But that's part of the problem with email cryptography, isn't it? Interesting... could this r
by rubyfan 12y ago
> Of course, this also means that there is a UX problem to solve. But that's part of the problem with email cryptography, isn't it?
Interesting... could this really just be a UX problem? Why do we understand HTTPS without problem? Or am I naive in believing HTTPS is widely understood by the layman?
- rlpb 12y agoHTTPS is one way, which makes it easier for users. The UX for the user is (relatively) easy, even if it still has issues: check the URL bar. On the other hand, the server administrators have to contract with a CA, get certificates, configure everything correctly, consider browser compatibility, etc. Email must be two way. Suddenly _every user_ has to do what HTTPS server administrators do. And then they have to convey the intent of a signature or the availability of an encryption key to their correspondents. I think this is what inherently makes email cryptography much more complicated from a UX perspective.