News for hackers. Stuff that matters.

A comment on Why Isn’t Telegram End-to-End Encrypted by Default (2017). Parent comment

Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017) by CodeGlitch on Monday January 11, 2021 @05:29PM (#25738477)
By the way before anyone shouts at me, I know email isn't E2E encrypted. As I've said before on HN: if you are looking to communicate securly, you shouldn't be using anyone else's infrastructure. That includes Signal et al.

Most people chatting to their friends and family don't need that level of security.

If you don't want China listening to you: don't use someone else's system.

[ Parent | on HN ]
Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017) by FabHK on Monday January 11, 2021 @06:55PM (#25740067)
You could even allow only emails to the same domain (handled on the same server itself). Then emails never leave the server, and people can access them with their favourite tool, such as web or IMAP/SMPT, which encrypts everything in transit these days, if set up properly, unless I'm mistaken.
[ Parent | on HN ]