4 ms·
Have a cookie. 100ms isn't that low, and those NATs are introducing additional latency and complexity that don't need to exist. If both sides are behind NAT th
by Dagger2 6y ago
Have a cookie.
100ms isn't that low, and those NATs are introducing additional latency and complexity that don't need to exist. If both sides are behind NAT then you may well need to relay the connection through a third party server, introducing even more cost, complexity and latency and involving an otherwise-unnecessary third party.
"I managed to get something working" doesn't invalidate any of that.
- iso1210 6y ago100ms is very low for doing decent compression and decompression. Network latency added by natting is microseconds. Imagine I had a public IP - no natting involved. How would my video client tell my stateful firewall to allow a new incoming connection from the calling device?
- namibj 6y agoThe issue isn't the NAT itself, it's the inhibition of P2P connections (to a further extend, spontaneous queries for distributed routing technologies like seen in IPFS, but those are just preventing full decentralization). Once you have to bounce the data through a hosted proxy, you're forcing no less than 10 ms on to the users (of course there are rare exceptions for users really close to your proxy).