5 ms·
This is cool. Some random thoughts/feedback: - it would be good to document/visualise the different components. AFAICT coturn is used to connect peers; what is
by alexchamberlain 6y ago
This is cool. Some random thoughts/feedback:
- it would be good to document/visualise the different components. AFAICT coturn is used to connect peers; what is galene responsible for? Signalling and room management?
- A big, clear link to the code on Github is always nice
- jech 6y agoGalène is not peer-to-peer: it's a traditional centralised server, where all media traffic goes through Galène. TURN is only used if the user's network blocks the UDP traffic between the client and Galène (TURN can use TCP, and can run on an unblocked port such as 443 or 1194). Before Galène, I experimented with a pure peer-to-peer system, with end-to-end encryption. I found it to be too unreliable for group communication: with just 5 people in a group, you need to establish 10 peer-to-peer WebRTC flows, and the likelihood that all of them work well is essentially zero.
- api 6y agoThank NAT for that. I wonder how many hundreds of billions of dollars in hidden overhead it costs us annually by making peer to peer unreliable and complicating everything. Then throw in all the power consumed by all the cloud infrastructure we wouldn’t need. “Null” in languages like Java has been called a trillion dollar mistake. NAT is probably worse.
- zepto 6y agoWithout NAT we’d have run out of ip addresses long ago.
- alexchamberlain 6y agoThank you for that explanation.