News for hackers. Stuff that matters.

A comment on How Discord Handles Two and Half Million Concurrent Voice Users Using WebRTC. Parent comment

Re:How Discord Handles Two and Half Million Concurrent Voice... by Klathmon on Monday September 10, 2018 @02:01PM (#17953644)
Yeah, I skipped over a lot of the details, but you would need someone to choose to be a "host" (at least in terms of a "host" for the connection signaling stuff), but you can also implicitly make it the person who created the link safely.
[ Parent | on HN ]
Re:How Discord Handles Two and Half Million Concurrent Voice... by derefr on Monday September 10, 2018 @03:08PM (#17954211)
If everybody is behind NATs (without uPnP privileges), nobody can be the "host" for connection-signalling purposes.
[ Parent | on HN ]
Re:How Discord Handles Two and Half Million Concurrent Voice... by Klathmon on Monday September 10, 2018 @03:30PM (#17954415)
There are public ICE/STUN servers that can facilitate NAT-punching, google even hosts one. But that's not the aspect that I thought the root comment was talking about, but more the aspect of "A is hosting a room called 'stuff', and B and C want to browse the list of rooms and connect to it".
[ Parent | on HN ]