[comntr]

In fact, I seriously considered ipfs. Then I tried to patch its severe connectivity problems with webtorrent dht. I even considered dat. But internet consists of symmetric NATs, that make any such DHTs hardly possible. An extension based on js-ipfs, would need 1 GB of memory and would constantly hog CPU with some mysterious computations. It would have to keep tens of tcp connections open to maintain at least a resemblance of connectivity. Even then, if you published a comment via "ipfs add" on your laptop and tried to discover it via "ipfs get" on your phone, it would be completely unable to do so even after an hour. Yes, it is this bad. And even then, assuming ipfs add/get worked perfectly with negligible load on CPU and memory, you'd still to keep the list of comment hashes on some data server because in ipfs the key principle is immutability. No, ipns is not a solution. It does allow to change a single hash pointer, but you need to use a private key to do so. This won't scale beyond a single data server. I had big hopes on ipfs, but it really isn't there and given the fundamental problem - inability to implement fast DHT in the world of Symmetric NATs - I don't see how it can become better.