News for hackers. Stuff that matters.
Re:Peer-to-peer WebRTC connections with built-in signaling a... by gavmor on Thursday November 12, 2026 @05:28PM (#50475264)
I don't think we have the same definition of "built in"; I would expect it to mean "built into this package/module", not "built into my service which this package acceses".

Edit: it's possible I'm overlooking some aspect of the handshake that's obviated in this case. Perhaps I haven't looked as closely as it deserves.

Re:Peer-to-peer WebRTC connections with built-in signaling a... by LuKks on Thursday November 12, 2026 @06:07PM (#50475728)
Actually you're right if we use your [more correct] definition "built into my service which this package acceses"

The signaling server is acting as a free public service right now, so you're right haha

1. The package connects to an external online WebSocket server. 2. When you do server = rtc.createServer() and server.listen() it tells the external signaling server to record an announcement in a key-value Map which allows permission to receive relayed data from peers that want to connect with you. 3. When a peer does rtc.connect(server.publicKey) they send you via relaying small signaling offers/answers (SDP/ICE) to establish the RTCPeerConnection.

Personally, I just wanted to get the direct peer-to-peer connection perfectly negotiated in the browser as fast as possible.

Signaling can still be improved a lot as per my other replies, and like-webrtc should allow different options for signaling so anyone can do their own thing as well while still benefiting from the cross-platform, intuitive server/client API, the included perfect negotiation, etc.