Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> This "average nontechnical user" stuff, though, miss me with. For 2 decades people have been encouraging the "average nontechnical user" to do incredibly unsafe things on the premise that any kind of message encryption is the best alternative to sending plaintext messages. No: telling people not to send those kinds of messages at all, unless you're dead certain the channel they're using is safe, is the only responsible recommendation.

Eh. You misunderstand me. I don't really have too much of a view on this personally. Unless you specifically think that the term "average nontechnical user" is a bad term.

N.B. for other readers of this thread to flesh out my initial point:

Signal specifically didn't do that recommendation until they got sufficient critical mass of users in 2022. In particular Signal gracefully degraded to unencrypted SMS if the other side didn't have Signal.

Likewise Signal required phone numbers until 2024 when it shifted over to usernames, with all the security vulnerabilities that entails.

Signal has repeatedly made trade-offs that prioritize UX over absolute security even in 1-1 chat settings. That's not to criticize those trade-offs, there's a variety of reasons why they make sense or don't. But Signal has consistently demonstrated that it is not willing to make severe compromises to the UX and understandability in the name of absolute security and that it will balance the two.



I disagree with basically all of this but none of it is on topic for this thread and none of it has anything to do with the point I was making.


The point of HN comments are for tangents, so I'm happy to hear why you as a domain expert disagree with any of what I raised there.

Also to your point

> For 2 decades people have been encouraging the "average nontechnical user" to do incredibly unsafe things on the premise

Sure I can agree with that. But that wasn't my point either? Unless again you specifically object to the term "average nontechnical user."




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: