this post was submitted on 28 Oct 2026
235 points (98.0% liked)
Open Source
49831 readers
245 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've said that before, but the O(N²) issue with E2E encryption only exists in an ideological sense. If your group chat is large enough that the overhead is unbearable, you don't have a private and secure group chat to begin with, just because a group chat of this magnitude is very much public by definition.
With that said, you can keep server logs encrypted while avoiding the payload/key rotation explosion by using static keys (available since forever with PGP in XMPP) or wait the decade (but most probably, the eternity) that it will take for MLS to be bolted on top of Matrix (and the new protocol design that this entails due to the absence of guarantee about messages ordering)