Hacker News Reader

I totally agree with this - but with my current understanding of WebRTC, there is no "efficient" way of decentralizing a multi-party real-time app (1:1 is only so useful). It requires an SFU or MCU architecture.

Finding an efficient way to chain peers without a centralized server would be a seriously transformative piece of engineering (hence the title).

View on HN

Yep, WebRTC video with lots of participants is one of the harder cases. But there are other sweets pots.. depending on what information you are routing through your decentralised system. If it's metadata, it's small and much less problematic than having a room of 10 WebRTC video sessions all streaming 10x video streams between each other. But if you are running eg something like a DHT, and then using that to set up transient real time sessions between a few peers, things start to look a lot more manageable.

Reply on news.ycombinator.com