Post #2836341
2025-06-10 07:26 UTC
Replies (7)
-
@rysiek@mstdn.social 2025-06-10 22:22
Telegram has responded to IStories' piece: > All Telegram servers are Telegram’s property maintained by Telegram employees. Unauthorized access is not possible. Telegram has neither employees nor servers in Russia. In the entire history of Telegram, it has never handed over private messages to third parties, and its encryption has never been hacked https://vot-tak.tv/87198696/fsb-chitaet-telegram This answers exactly zero of the crucial points raised by the story. :blobcateyes: Let's dissect it! 🔍 🧵 #Telegram #FSB
-
@ElectroFetish@mastodon.social 2025-06-10 09:53
@rysiek@mstdn.social This has nothing to do with a single country. Capitalism uses any tool to control the masses.
-
@Beachbum@mastodon.sdf.org 2025-06-10 14:43
@rysiek@mstdn.social I don’t use it, but this is alarming.
-
@mdione@en.osm.town 2025-06-10 15:24
@rysiek@mstdn.social You say: "That “authorization key”, used to encrypt messages between a client and a server, is negotiated once on each device [...] got assigned to at registration time, pretty much for the lifetime of the client on that device." I wonder what happens with the web client, specially if you somehow get rid of T's data on the browser. I use it daily and TBH for some stuff it's better than Linux and Android native client.
-
@f4grx@chaos.social 2025-06-10 19:40
@rysiek@mstdn.social my unsurprised face.
-
@f4grx@chaos.social 2025-06-10 19:42
@rysiek@mstdn.social pfs that regenerates identifiers every 24h? wtf?
-
@pixelschubsi@troet.cafe 2025-06-10 21:18
@rysiek@mstdn.social I was wondering what you think about Signal's registration_id. It seems to be a longterm device id that is attached to some(?) messages?