3 ms·
E2EE is genuinely hard to implement in the context of a chat service with server-side chat history, large (10k+ user) group chats, and multiple clients (includi
by duskwuff 5y ago
E2EE is genuinely hard to implement in the context of a chat service with server-side chat history, large (10k+ user) group chats, and multiple clients (including web applications).
- JBiserkov 5y agoSignal has server-side chat history, no? And the protocol is open. So that part of the argument is moot.
- duskwuff 5y agoSignal chat history is client-side. You have to explicitly "back up" and "restore" messages to move to a new device, and if you lose your phone, your chat history is gone forever. https://support.signal.org/hc/en-us/articles/360007059752-Backup-and-Restore-Messages https://support.signal.org/hc/en-us/articles/360007059752-Ba...
- AegirLeet 5y agoI'd flip that around and say that server-side chat history, large group chats and multiple clients are hard to implement in the context of an E2EE chat service. What I mean by that is: E2EE is a necessity, not some nice-to-have feature. Building a chat service with server-side chat history but without E2EE is like building a car with very nice headlights that doesn't actually move.