Feross Aboukhadijeh
Feross Aboukhadijeh
Thanks for the detailed explanation! Is it your intention to support only data channel? It's been my experience that libraries that aim to also support video/audio have had long compilation...
@lgrahl I love that this library is data-channel first and video/audio will be an explicit compile-time opt-in. Thanks for the great work, and for solving the biggest need of WebRTC...
**P2P use case: Distributed Hash Tables** [DHTs](https://en.wikipedia.org/wiki/Distributed_hash_table) are a fundamental building block of almost every P2P system. They are the primary routing layer in Bitcoin, IPFS, Dat, BitTorrent, and WebTorrent,...
**P2P use case: Peer-assisted delivery** - Hybrid P2P. Optimistically serve content from peers, but fallback to HTTPS when no peers are available. - See products from companies like PeerCDN (my...
**P2P use case: Sending files directly browser-to-browser** - Benefits: Faster on networks with a slow uplink to the "cloud", more private, could allow discovery of local peers like macOS's "Airdrop"...
Count me in
No, this library seems abandoned.
+1 please implement support for `JSON.stringify`. Otherwise we have to hack around it in our WebRTC helper library. It'd be awesome if the Temasys plugin was 100% a drop-in replacement.
@roccomuso If you want to send improvements here first, I can publish it a separate module in a few days.
I think that API works! I think making the line more transparent when we're choked would be good.