Telegram's t.me domain has been suspended

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

[ Parent | on HN ]

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, …)

[ Parent | on HN ]

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

[ Parent | on HN ]

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!

[ Parent | on HN ]

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.

[ Parent | on HN ]

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)

[ Parent | on HN ]