The blog post is accessible through IPFS here <a href="https://ipfs.io/ipfs/QmY2LufsW3v6AfxTTkp6SGqDGa5AeJhSZXH8RSsdiao4Ds/" rel="nofollow">https://ipfs.io/ipfs/QmY2LufsW3v6AfxTTkp6SGqDGa5AeJhSZXH8RSs...</a> in case the original link doesn't work.
Very interesting stuff ,
I'm following ipfs for a while now , and using the browser sessions as full nodes is an exciting idea.<p>One thing I wonder about ,
Is the browser -> ipfs node communication can be done via webrtc (I think the post refer to websocket)?<p>So the data sync can happen between browsers .<p>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 )
I doubt the usefullness of orbitDb. Ipfs-nodes only store and distribute content which they have accessed before. When you have a database with user-based data, noone except yourself will distribute it. This means you could have the same distribution with plain webrtc instead of height-ping ipfs.
It’s too bad that the flowering of distributed hash table / content-addressable storage research & development nearly precisely coincided with Internet Explorer’s ossification of web standards, or maybe we’d have had something like IPFS built into every browser 15 years ago.