90
Telegram, the FSB, and the Man in the Middle
(www.occrp.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Jun 2025
90 points (88.8% liked)
Privacy
38854 readers
566 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
No, my argument is "this argument about a gun being used is invalid. It's not used for now".
I'm pretty sure if there would be enough demand for strong encryption there would be OTR forks of Telegram that would become popular. There is no such thing now. People use Telegram for stuff that is not "1on1 talks that I want to be strongly protected" in overwhelming majority of cases. People choose convenience. Encryption is useless when you are getting reported on by people in your chats or when you don't know what you're doing. Stupidity breaks any encryption, see that latest Signal case.
except, implementing E2EE via 3rd party FOSS clients is explicitly against Telegram's TOS, which I'm gonna assume you already know as you're parroting weirdo's stance "all crypto is broken by NSA, so we're better off without". take care.
No, I'm not saying that.
First time I read about such thing being included in TOS. Care to link something relevant? I can't imagine how they are going to control that or ban any client or wipe data transmitted by them.
you must've me confused with someone who does shit on your behest, go find out yourself.
this is just for onlookers, as it's obvious it's weirdo's shill: the term in the ToS is "all comms must be readable by all other clients" which an E2EE capable client would be in breach of and would be promptly kicked off telegram's infra, as was mentioned by those same FOSS developers in lemmy threads regarding that subject. as for you, plonk.
It doesn't work like that. Encrypted messages will not become unreadable for other clients. They will become undecryptable for users of other clients.