Hacker News Reader

TLDR: What's keeping it back is Web standards. Extensions cannot initiate TCP connections and there is no IPFS network made of (possibly hybrid -- both protocols) nodes that are able to use WebSockets instead of TCP.

The js-ipfs daemon can only fully run on Node.js where it has access to real UDP/TCP sockets. (I don't see this as a clear proclamation in their readme, so don't take this for granted)

> The js-ipfs daemon can only fully run on Node.js

Not sure what "fully" refers to here, but js-ipfs in the browser can fetch/add content like a normal IPFS node via either websockets or webrtc. Although, TCP connections would make a lot of things, a lot more efficient and nicer.

IPFS is really trivial to install in most OSes and distributions. If you don't want to run it as a daemon via terminal/systemd/whatever, you can either run the browser extension together with ipfs-desktop and it's GUIs all the way down.

https://github.com/ipfs-shipyard/ipfs-desktop/

Interesting to consider WebTorrent vs. BitTorrent in this context; BitTorrent has grown much closer to mainstream but WebTorrent doesn't seem to be growing.