https://github.com/LuKks/like-webrtc/blob/a1a2ac0a90eae7319e...
I will look into building a HTTPS signaling version so that this can be deployed anywhere easily e.g. CloudFlare workers or your own tiny HTTPS server.
Also, the cool thing about TURN is that two peers with different TURN configured servers are going to still work and connect perfectly, so anyone can use any TURN server and it would still work.
First, we need E2E encrypted signaling meaning I want the signaling server itself to not be able to read the signals between peers and I'm already working on it. Short-term, a second easy step is to simply run more a few more servers for redundancy.
For context: My main focus for this early version was not decentralized signaling because a simple one works for now, and we can upgrade it afterwards and add redundancy in different countries/jurisdictions. The focus was to build the best intuitive API possible for P2P in the browser and servers with no assumptions e.g. just like a TCP or HTTP server.
In a different comment I explained a better medium-term vision about a decentralized signaling system + decentralized network between long-running browser tabs + node servers.
Also, as someone else pointed out you can still run your own lightweight signaling server (I call it "party" internally, sounds cooler).
I highly appreciate your honest question :)