3 ms·

You can traverse NAT with PCP/NAT-PMP. Libdatachannel doesn’t support it, but I don’t see why it shouldn’t in the future! —— Yes <100ms is hard, I don’t think

• gloosx 3y ago
  UPnP could be enabled on your NAT, but probably not, because it comes with certain security considerations. If you take most used networks globally – which are the cellular carrier networks, they won't let you do it. The point is about these techniques – you can't fully eliminate guesswork about whether specific NAT will be traversed or not for arbitrary peers, so the relay is mandatory to do it. If you're fine with only some part of the audience getting connected to your stream, and some not – you can go full P2P, otherwise the server-less claim is too bold. 400-600 ms is certainly not a "real conversation" experience, yet getting close to it. Speaking more realistically, the latencies spread would be much more broad depending on the peers' geography in a true P2P mesh. So with a part of the audience closer to streamer, the conversation can become more real indeed, but for those further away, it will be increasingly more choppy. If you don't need to negotiate again, how do you know which new socket to send bytes to? Is it some kind of a wizard, this NICER?