I don't believe the pub/sub is critical functionality (progress at [0], but it's really just chatty). Progress of that additional feature should not be a measuring stick for the project as a whole. For js-ipfs, I see work being done frequently, e.g. the DHT work[1] and weekly syncs[2]. I agree work is slow, but I am not getting the impression it is fizzing out.
Having said that, I think there are fundamental problems with the ideas behind it. I want MaidSafe's ideas and IPFS's completion/MVP schedule. IPFS doesn't bring enough anonymity or forced, equitable, encrypted block sharing IMO (I am aware of efforts on both fronts of course).
0 - https://github.com/ipfs/notes/issues/64
The easiest and least stressful outcome is to drag it along forever while paying themselves giant executive salaries from that stash. As long as there’s some minimal progress, it’s not fraud.
With that track record, the burden is on you to explain why you think they will suddenly throw all that away, and stop working on a project they're so clearly passionate about, ruining their reputation in the process.
Convincing people to give up $250 million is the part that built their reputation and ensures lucrative deals will be coming their way. Whether they’re passionate about some storage-sharing token is neither here nor there.
js-ipfs runs in the browser just fine. See https://filemap.xyz/.
For a DHT to work, you need to be able to able to connect to be discoverable and be able to connect to multiple peers.
WebRTC unfortunately doesn't allow for this yet.