You specifically mention:

"Server dependence: You need to host or use two different servers (Signaling + STUN/TURN). Can use Google’s STUN, but combining signaling and STUN into one server would be nice."

I'm curious about using Tailscale with this. I don't think you can just do Tailscale Funnel? But maybe you could? Maybe Tailscale Share, and the client has to also be on Tailscale?

I feel like they would go really well together...

Thoughts?

▲

valorzard 3 days ago | parent [-]

So, having talked to people in the WebRTC community about this, you should be able to use WebRTC in a local network without having to connect to STUN/TURN

STUN/TURN matters because if you are connecting to a remote peer, you have no idea how to reach them. STUN/TURN gives you a "map" to get to the remote peer.

If you are on a VPN that doesn't matter very much (see: Hamachi)

▲

andersmurphy 3 days ago | parent [-]

Yeah if you know the ip of your peer you don't need STUN/TURN from what I remember.

	▲	VikingCoder 3 days ago \| parent [-]
		If it's ipv6, I think that's true. If it's ipv4, then you still have problems. They could be behind NAT or worse, CGNAT.