|
|
|
|
|
by Tecuane
3006 days ago
|
|
In Matrix, E2EE isn't enabled by default[1], and the option to enable it is in fact marked with a warning that it comes with potentially unwanted side-effects. This isn't the same, and the arguments that call recommending Telegram for E2EE encryption disingenuous apply to Matrix/Riot recommendations too. One other issue I have with Matrix is the fact that they're in the process of completely rewriting their reference implementation in Go despite the fact that - as far as I remember - the first one, in Python, isn't entirely complete[2]. Combined with the app-bridge song and dance[3] there's too much in flux for me to recommend in good conscience. Finally, and perhaps most importantly (speaking as a "regular" user - the type needed to achieve mass adoption), the client is horrendous. This is especially apparent when compared with Wire, but I'd go as far as saying it's apparent even when compared with some IRC clients. At least Signal's UI/UX is passable. Encryption didn't catapult Telegram to 200 million monthly users. A slick UI, a half-decent UX, and some good marketing did. 1. Your link - https://about.riot.im/security/ 2. https://github.com/matrix-org/synapse#introduction 3. https://github.com/matrix-org/matrix-appservice-bridge |
|
Edit: Aside from that, while the Telegram UI is nice, it doesn't even try to compete with the interfaces commonly found in IRC clients (i.e. no bubbles, one or more lines per message, can actually fit more than a handful of messages without scrolling, and so on... see qwebirc).