TLDR: 99.95% of messages on Telegram stored as plain text on their servers and only encrypted between client and telegram server. End-to-end encryption only working for 1on1 chats, not available half of their clients and have terrible UX.
All this is just wrong. I wonder why HN likes throwing up wrong information about Telegram as fact. Is taking up 5 mins to proof these claims that hard?
> 99.95% of messages on Telegram stored as plain text on their servers and only encrypted between client and telegram server.
Wrong and OP doesn't even mention plain text. The non-E2EE client-server data is stored encrypted sparsed out in various servers to different countries.
https://telegram.org/privacy#3-3-1-cloud-chats
> End-to-end encryption only working for 1on1 chats, not available half of their clients and have terrible UX.
Wrong again. I actually recently checked this for myself their official clients on Android and Linux desktop have support for MTProto 2.0. Feel free to check if other OS don't support this feature. The only clients I know where this is not enabled are the web clients.
> The non-E2EE client-server data is stored encrypted sparsed out in various servers to different countries.
Yet all this data available to any person connecting to Telegram API endpoints. It's really doesn't matter how they distributed storage look like underneath if there is point where everything available as plain text.
Also this is just "trust me bro" encryption. You cant check any of it.
> Wrong again. I actually recently checked this for myself their official clients on Android and Linux desktop have support for MTProto 2.0.
E2EE in telegram is burdensome to use. It's just fact for anyone who actually used it daily.
Also many desktop versions only gained E2EE capabilities relatively recently.
