News for hackers. Stuff that matters.
Re:How Discord Handles Two and Half Million Concurrent Voice... by Sammi on Tuesday September 11, 2018 @03:26AM (#17957793)
They also clearly explain why decentralization doesn't work for large rooms:

> Supporting large group channels (we have seen 1000 people taking turns speaking) requires client-server networking architecture because peer-to-peer networking becomes prohibitively expensive as the number of participants increases.

It's unfortunate, but it's just the truth. The reason we aren't seeing decentralized solutions to the problem that Discord solves is technical. It's not because people don't want it or aren't trying. I just doesn't perform well enough.

Re:How Discord Handles Two and Half Million Concurrent Voice... by geek_at on Tuesday September 11, 2018 @05:58AM (#17958359)
that is not an argument for centralized vs decentralized, that's an argument for client-server vs peer2peer

Not many selfhosted (eg decentralized) solutions use peer2peer because this requires NAT punching and other methods. TS3, Mumble and Ventrilo are all "proxies" in that manner and not peer to peer

Re:How Discord Handles Two and Half Million Concurrent Voice... by ckocagil on Tuesday September 11, 2018 @04:32AM (#17958046)
Federation is good enough for practically everyone.