News for hackers. Stuff that matters.
Re:Peer-to-peer WebRTC connections with built-in signaling a... by gavmor on Wednesday November 11, 2026 @11:34AM (#50455345)
It doesn't have built-in signaling and peer discovery, because that's impossible.

It does look kinda neat, though!

Re:Peer-to-peer WebRTC connections with built-in signaling a... by cyanydeez on Wednesday November 11, 2026 @11:37AM (#50455379)
Its basically the same though. You stop at the relay, then connect to a peer to find other peers. Rther than the relay handing oht p2p, the relay just hands out peer-as-server.

So, sure, we are stiill straining for decentralization.

Re:Peer-to-peer WebRTC connections with built-in signaling a... by LuKks on Thursday November 12, 2026 @05:17PM (#50475144)
I appreciate it, but when you try to use WebRTC from scratch on your own e.g. connect two RTCPeerConnection instances there is no signaling at all meaning you have to do it and let alone handling SDP negotiation glares

Here "built-in signaling" of course means that you don't worry about it at all, like even when you open new data channels, add new audio/video tracks, etc it's all automatic and perfectly negotiated for you.

If you see the usage example in https://github.com/lukks/like-webrtc there is no sign of any signaling because it's done for you so I think it deserves the "built-in signaling" point :)

I'm working on an update for E2E encrypted SDP/ICE signaling, meaning the server won't be able to read the offers/answers/candidates. After that, to be fair with your reaction and comment, I could clarify in the documentation how the "included signaling" works.

As for peer discovery, it's dependent on the same signaling server but later on it can easily be an actual decentralized network of peers i.e. RTCPeerConnection.

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.