Why Isn’t Telegram End-to-End Encrypted by Default (2017)

Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017) by snvzz on Monday January 11, 2021 @04:26PM (#25737383)

I do not like it (I prefer Matrix, where accounts are not tied to phone lines), but I am ok with Signal, as it is open source, it is always e2ee and using it really offers privacy.

Telegram, on the other hand, is not open source, nor does it do e2ee by default. Having to explicitly select "new secret chat" ultimately means the non-technical inclined can and will use it wrong, getting no privacy whatsoever.

Therefore, I cannot support the idea that Telegram is any better than WhatsApp or Discord.

Regarding "open protocol", I suspect that what you think it means is not what an open protocol actually is.

[ Parent | on HN ]

Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017) by jayp1418 on Tuesday January 12, 2021 @09:53AM (#25747639)

Good thing. Signal coming up with usernames

[ Parent | on HN ]

Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017) by snvzz on Wednesday January 13, 2021 @02:26AM (#25759228)

Indeed. I found this: https://signal.org/blog/signal-pins/

But as far as I can tell, no steps have been taken since; In the downloads page, it warns me that for the Desktop version to work, I need to create an account with my phone first.

I'll keep an eye out.

[ Parent | on HN ]