> You also can't experience true lossless on any bluetooth audio output device
Pretty sure you can... there's no technical reason you cannot use BT purely as a digital-only lossless data carrier. Whether or not current devices exist that work this way may be another story though.
Many users in the world are behind CGNAT or symmetrical NAT, and if both sides are, they will not be able to use WebRTC unless there is a TURN relay server involved. Does your software have a way to account for this?
Great question! Currently it uses Google's public STUN servers, which works for ~85% of connections. For the remaining cases, I'm planning to add a community-maintained list of TURN servers or a P2P fallback mechanism.
You could look into DHT as a way to distribute info about connected nodes, and maybe nodes with the right firewall setup could opt in to being TURN servers.
That's how it works in ipv6. If your network doesn't give you an address, it's broken. We do not assume unfiltered since we are talking about hole punching.
Can't both sides just keep trying different ports until they get lucky? There's not that many of them, and even if it takes several minutes to get a match, that's better than nothing at all.
Pretty sure you can... there's no technical reason you cannot use BT purely as a digital-only lossless data carrier. Whether or not current devices exist that work this way may be another story though.
reply