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?

Have you looked at Trystero https://oxism.com/trystero to establish the WebRTC connection? I used it on a small PoC last week and it worked well. Thanks to latching on to various decentralized services (Nostr etc) you don’t need your own TURN/STUN server etc.

So, as you can see in the article, there are already games and other projects that have grown past this limitation.

The main thing I need to do is honestly just sit down and rewrite the signaling server to make it work for multiple players, and also add CORS support.

(to be clear it will already support other computers, just not browsers on remote computers due to lacking CORS support)

So yeah this isn't an inherent limitation of WebRTC or anything, it's just writing a good signaling server for WebRTC is annoying

Check the /game folder haha. The main.go file has all the stuff related to webrtc And yes, the signaling server IS a normal http server. That’s the whole point. You can set up a WebRTC connection by even just emailing each other the SDPs if you want