MLS is the e2ee messaging and communications protocol standardised by the IETF RFC 9420 https://www.ietf.org/blog/support-for-mls-2023/.
MLS provides the same cryptographic properties as the respected signal protocol (forward secrecy and post compromise security), while adding scalability to tens of thousands of users and authentication (the weaknesses of its predecessors) and above all interoperability and thus decentralisation.
MLS is the equivalent of TLS, instead of for web and e-mail, for messaging and communication and is already supported by wire, webex and google messages and supported by mozilla, while matrix is working on support.
Telegram instead of developing MTProto v3.0 for secret group chats and secret group calls with e2ee, should support MLS together with the current MTProto v2.0. Telegram's unique functionalities, which are also possible thanks to the ad-hoc MTProto protocol, would not be disrupted and at the same time support for MLS would demonstrate foresight (future compliance with the EU DMA) and a spirit of decentralisation (interoperability) by Durov.
Related bugs: Secret group chats #1231 Make secret chats and group messages synchroniz... #8307 Group Voice Calls #40 Secret Chats and Groups on every app and device... #8631 Secret Chats on every Telegram app&device +... #4566
Even Meta, which is obviously not a reputable company, recently released an upgrade for Messenger from an in-transit encryption system to an e2e encryption system without sacrificing multi-device support with authentication, message history with e2ee cloud backup, and web support https://engineering.fb.com/2023/12/06/security/building-end-to-end-security-for-messenger/. Another example that brilliantly solved the problem of having multi device e2ee with e2ee backup before Meta is Element/Matrix https://element.io/features/end-to-end-encryption Telegram pioneered privacy and security in 2013 and is currently one of the last messaging services not to offer e2ee (except in 1:1 chats only available on mobile).
Emilia
Apple, which like Meta does not shine in terms of transparency and respect for privacy, recently released an update to the iMessage protocol in order to make it quantum computer-proof. The new PQ3 protocol is formally verified and thus at least theoretically free of flaws/backdoors https://security.apple.com/blog/imessage-pq3/. Unfortunately, the implementation is not verifiable as the application is closed source. Now Telegram is left at the tail end along with QQ, Skype and WeChat not even having e2e encryption as well as no protection against quantum computers.
Emilia
Discord is gradually rolling out e2e encryption in its services using the MLS protocol for key exchange https://discord.com/blog/meet-dave-e2ee-for-audio-video. At the moment, Telegram remains among the few services that do not have e2e encryption except for the special case of secret chats. In light of what recently happened to its CEO, Pavel Durov, that it would not be possible if the service used e2e encryption everywhere, what is stopping Telegram from upgrading its MTProto protocol in order to support such encryption everywhere and become a truly privacy and free speech oriented service? Obviously it would be much better if a standard protocol such as MLS was used.
Log in here to report bugs or suggest features. Please enter your phone number in the international format and we will send a confirmation message to your account via Telegram.
Another example that brilliantly solved the problem of having multi device e2ee with e2ee backup before Meta is Element/Matrix https://element.io/features/end-to-end-encryption
Telegram pioneered privacy and security in 2013 and is currently one of the last messaging services not to offer e2ee (except in 1:1 chats only available on mobile).
Now Telegram is left at the tail end along with QQ, Skype and WeChat not even having e2e encryption as well as no protection against quantum computers.
At the moment, Telegram remains among the few services that do not have e2e encryption except for the special case of secret chats.
In light of what recently happened to its CEO, Pavel Durov, that it would not be possible if the service used e2e encryption everywhere, what is stopping Telegram from upgrading its MTProto protocol in order to support such encryption everywhere and become a truly privacy and free speech oriented service?
Obviously it would be much better if a standard protocol such as MLS was used.
Hopefully in the future, Telegram will decide to support MLS protocol as well.