3 ms·

Very interesting stuff , I'm following ipfs for a while now , and using the browser sessions as full nodes is an exciting idea. One thing I wonder about , Is

Very interesting stuff , I'm following ipfs for a while now , and using the browser sessions as full nodes is an exciting idea. One thing I wonder about , Is the browser -> ipfs node communication can be done via webrtc (I think the post refer to websocket)? So the data sync can happen between browsers . I did play with webtorrent for a while , and achieved a similar behavior using webrtc . I had one nodejs server , and multiple browser sessions . It worked well for video streaming peer to peer (poc level )

diggan 8y ago
Browser IPFS to desktop IPFS communication can happen via websockets or webrtc right now, since those are the transports the browser currently offers us. The stack we're using for networking is libp2p, a peer-to-peer framework, which has bunch of implementations for different transports. You can see the full list of those here: https://libp2p.io/implementations/#transports https://libp2p.io/implementations/#transports Currently, most browser-apps using IPFS prefers websockets as it's using a lot less resources compared to webrtc, but once webrtc-quic[0] is ready for prime-time, it would be easy to write a transport for that and hopefully will be a lot more efficient than the current webrtc implementations. Disclaimer: I work on IPFS/libp2p fulltime - [0] https://w3c.github.io/webrtc-quic/ https://w3c.github.io/webrtc-quic/