Re:Why Isn’t Telegram End-to-End Encrypted by Default (2017)
by rakoo on Monday January 11, 2021 @06:54PM
(#25740047)
I feel like encryption before payload and OMEMO are 2 different layers like, say, TLS compression and HTTP compression.
When you send a pic in a conversation, the content-type of the resource is "image/*". It doesn't matter whether the image is encrypted, compressed on-the-fly, or whatever, the receiving end must "undo" all of it to present the intended resource to the user
When you send a pic in a conversation, the content-type of the resource is "image/*". It doesn't matter whether the image is encrypted, compressed on-the-fly, or whatever, the receiving end must "undo" all of it to present the intended resource to the user