90
submitted 5 days ago by glitching@lemmy.ml to c/privacy@lemmy.ml

turns out durov's bullshit is bullshit. huh.

you are viewing a single comment's thread
view the rest of the comments
[-] glitching@lemmy.ml 3 points 4 days ago

your argument boils down to "the fully functional and loaded gun is in this weirdo's holster and he won't use it".

the whole point is not relying on the benevolence of the weirdos out there and not letting them even be in the position to do any harm. encrypt my 1on1 comms and I don't give a fuck what happens in the pedo/terror/carding/etc public groups. ample time to implement that in the past decade+ and be on par with practically every messenger out there. but he/they won't implement it, they insist on all your shit being in the "cloud", in plaintext, forever. there is no scenario where there's not a malicious intent behind that.

I've been using Telegram since the early days. it was phenomenal vs the crap of its day - magical, even. like many, I was enamored with the vision of durov the folksy hero battling the forces of evil (in a bozo nightmare) and bequeathing us this tech marvel.

but I can't trust it with anything any more. if weirdo can't be trusted about some stuff, then he can't be trusted with anything. enough for me, YMMV.

[-] rdri@lemmy.world 1 points 4 days ago

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.

[-] glitching@lemmy.ml 1 points 4 days ago

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.

[-] rdri@lemmy.world 0 points 4 days ago

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.

[-] glitching@lemmy.ml 2 points 4 days ago

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.

[-] rdri@lemmy.world 1 points 4 days ago* (last edited 4 days ago)

It doesn't work like that. Encrypted messages will not become unreadable for other clients. They will become undecryptable for users of other clients.

this post was submitted on 10 Jun 2025
90 points (88.8% liked)

Privacy

38904 readers
1039 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

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS