News for hackers. Stuff that matters.
Re:Peer-to-peer WebRTC connections with built-in signaling a... by chr15m on Wednesday November 11, 2026 @09:55AM (#50454203)
Single signaling server:

    wss://party.leet.ar:41337
What happens to anybody who builds on this when you turn off your server in a few months time?
Re:Peer-to-peer WebRTC connections with built-in signaling a... by igbanam on Wednesday November 11, 2026 @10:42AM (#50454730)
This is the example. When building out yours, you can configure your ports

https://github.com/LuKks/like-webrtc/blob/a1a2ac0a90eae7319e...

Re:Peer-to-peer WebRTC connections with built-in signaling a... by LuKks on Thursday November 12, 2026 @06:14PM (#50475780)
Yes! We should make it easier to deploy your own TURN (relay) and signaling server (I call it "party" internally because it's discovery + signaling = party).

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.

Re:Peer-to-peer WebRTC connections with built-in signaling a... by LuKks on Thursday November 12, 2026 @04:50PM (#50474816)
Valid question! While I was building the module I obviously thought about this.

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 :)