3 ms·
Calls use WebRTC, which is of course p2p. [https://github.com/telegramdesktop/tdesktop/blob/master/Telegram/SourceFiles/calls/calls_controller_webrtc.cpp https:
by tgragnato 6y ago
Calls use WebRTC, which is of course p2p. [https://github.com/telegramdesktop/tdesktop/blob/master/Telegram/SourceFiles/calls/calls_controller_webrtc.cpp https://github.com/telegramdesktop/tdesktop/blob/master/Tele...]
Point is I don't see anything decentralised in MTProto. Unless I'm mistaken Durov announced that he wants to make something p2p, but right now it's not.
[https://github.com/telegramdesktop/tdesktop/tree/master/Telegram/SourceFiles/mtproto https://github.com/telegramdesktop/tdesktop/tree/master/Tele...]
See: https://core.telegram.org/mtproto#transport https://core.telegram.org/mtproto#transport
- tgragnato 6y agoIn addition, the signaling protocol for WebRTC in Telegram is MTProto. If an ISP were to really block MTProto, then the P2P functionalities would stop working as well.