3 ms·
Well technically it is possible to avoid the signaling server, but you'll need some other channel to exchange the peers connection data. This is pretty inconven
by perenzo 6y ago
Well technically it is possible to avoid the signaling server, but you'll need some other channel to exchange the peers connection data. This is pretty inconvenient though. But a signal server is a rather light thing and easy to install on a location you trust: https://github.com/holtwick/briefing/tree/master/signal https://github.com/holtwick/briefing/tree/master/signal
- waynenilsen 6y ago> you'll need some other channel to exchange the peers connection data Perhaps using IPFS to pin the data temporarily and share that hash between the peers?
- saurik 6y agoIf you can figure out how to share that hash, you may as well just share the offer.
- waynenilsen 6y agoYes, serialization is the issue. URL length is technically unlimited but in practice very long urls don't work out so well
- perenzo 6y agoThat's a good idea. I don't know the internals of IPFS, but the related https://libp2p.io/ https://libp2p.io/ looks promising. Follow up https://github.com/holtwick/briefing/issues/52 https://github.com/holtwick/briefing/issues/52
- kodablah 6y agoI did a POC of this over a year ago [0]. Now, with better libp2p-js library, it is surely much easier/better nowadays. 0 - https://github.com/cretz/webrtc-ipfs-signaling https://github.com/cretz/webrtc-ipfs-signaling
- lioeters 6y agoThank you for making both the client and server sides of this video chat application open source. The only missing piece it seems is the STUN/TURN server. Would you have a plan to also release it?