July 9, 2026
Group chat, but make it chaos
How should group chats work in decentralized systems?
The dream of server-free group chats hit reality, and the comments got brutally honest
TLDR: A developer built a fully server-free chat app and discovered that group messaging becomes wildly complicated without one central place keeping track of members and missed messages. Commenters were split between admiration, skepticism, and outright sarcasm, with some questioning whether anyone wants this at all.
A developer set out to answer a deceptively simple question: how do you make a group chat work when there’s no central company computer quietly keeping track of everything? In normal apps, some server handles the boring-but-vital stuff: who’s in the group, who got kicked, what messages came first, and what you missed while offline. Strip that away, and suddenly even a tiny friend chat turns into a philosophical crisis. The app, Kiyeovo, chose a fully server-free route anyway, accepting tradeoffs rather than sneaking in a hidden boss machine.
But the real fireworks were in the comments, where the crowd split into camps fast. One blunt drive-by became the thread’s mood setter: “The hardest problem is social. Who is going to use this?” Ouch. That wasn’t a technical complaint at all — it was the classic internet gut-punch: cool idea, but will any humans actually show up? Others piled on with a more practical tone, basically saying the app may claim to be fully decentralized, but in spirit it still picked a mini-ruler by giving one creator-admin the power to keep things from descending into chaos.
Then came the armchair product managers with a sneaky workaround: just fake dynamic membership. Let people think they’re inviting or kicking members, but really secretly make a new chat behind the scenes. It’s the kind of “don’t let users see the mess” suggestion that sounds both clever and a little cursed. Meanwhile, skeptics went full doom mode, arguing that decentralization always ends with someone taking control anyway. In other words: the article asked how group chats should work, and the comments answered with a brawl over whether true decentralization is genius, theater, or just a very elaborate way to reinvent admins.
Key Points
- •The article argues that group chats are difficult in fully decentralized systems because there is no central authority to manage membership, keys, message order, or missed messages for offline users.
- •It explains that centralized services such as Signal and Matrix use servers for coordination even when message content is end-to-end encrypted.
- •The author reviewed several approaches, including coordinating servers, MLS/TreeKEM, leaderless membership, and fixed-membership groups.
- •MLS/TreeKEM is described as scalable for large groups but too complex for a no-server DHT-based system, especially because Kiyeovo limits groups to 10 members.
- •The implemented design for Kiyeovo follows a strict requirement of using no server anywhere while supporting dynamic groups through chosen tradeoffs.