Re:Telegram's t.me domain has been suspended
by sneak on Monday July 13, 2026 @07:36PM
(#48900411)
Wait until you hear that the chats aren’t end to end encrypted.
[ Parent
| on HN ]
Re:Telegram's t.me domain has been suspended
by pylotlight on Tuesday July 14, 2026 @01:27AM
(#48902622)
wait until you hear why, and that you can optionally use e2e but lose other functionality.
And end-to-end encryption not supported on web client and doesn't sync properly between devices. Useless.
Re:Telegram's t.me domain has been suspended
by lesostep on Tuesday July 14, 2026 @04:32AM
(#48903764)
>> doesn't sync properly between devices
which is good, actually. We don't want a way through which a server could tell a new device all the information it needs to decrypt messags
Re:Telegram's t.me domain has been suspended
by asqueella on Tuesday July 14, 2026 @06:14AM
(#48904508)
I thought this was a long solved problem: the server syncs encrypted data, and the user provides the decryption key from another device (via QR codes, BLE, …)
Re:Telegram's t.me domain has been suspended
by WmWsjA6B29B4nfk on Tuesday July 14, 2026 @06:11AM
(#48904492)
Make it device-to-device then
Re:Telegram's t.me domain has been suspended
by grayhatter on Tuesday July 14, 2026 @09:25AM
(#48906504)
yeah, it is good! I hate usability features too!
Re:Telegram's t.me domain has been suspended
by inigyou on Tuesday July 14, 2026 @02:29PM
(#48911127)
You either have E2EE or you don't. If you have usability, you don't have E2EE.
Re:Telegram's t.me domain has been suspended
by grayhatter on Wednesday July 15, 2026 @08:59PM
(#48929228)
I can't have E2EE and also have cross device data sync?
counter point https://github.com/GrayHatter/toxcore/tree/multi-device (I guess technically you'd need https://github.com/uTox/uTox/tree/mdev too)