[vitriolum]

About the intro article not coming up

Sometimes the bootstrapping server seem to be overwhelmed. I suspect HN's "hug of death" could be possibly responsible. This will be resolved when js-ipfs implements DHT and relay:

> Please read this: DHT (automatic content discovery) and Circuit Relay (pierce through NATs and dial between any node in the network) are two fundamental pieces that are not finalized yet. There are multiple applications that can be built without these two services but nevertheless they are fundamental to get that magic IPFS experience. If you want to track progress or contribute, please follow:

DHT: https://github.com/ipfs/js-ipfs/pull/856 Relay: https://github.com/ipfs/js-ipfs/pull/1063

This stuff is alpha at this point, and sometimes there are still fires to extinguish. Sorry about the inconvenience, I suggest to try again later :(

[Confiks]

Are you sure the introductory post is a valid link?

This is what I get using go-ipfs:

    > ipfs object get QmccRaHCrUKZwZpjdJFiTTdgp8FG3ALFDZQexaYgit3NCF
    > {"Links":[],"Data":"{\"name\":\"user\",\"type\":\"eventlog\",\"accessController\":\"/ipfs/QmSucCCcNw9CUJS4MmSW86kjZwfTNExyVnMzh4eBT6Jku9\"}"}

[vitriolum]

It is. I'm using OrbitDb, so the data structures in the ipfs node are not the ones you'd expect. Also, it needs to load at least three nodes to get to the article - that's a necessary trade off to have user metadata and user feeds. If it wasn't for the bootstrappers timing out it would have worked almost instantly. That's cool, bug has been reported.

[desertedisland]

The site looks good, I like what you've done here. The article came up after some delay!

I'm quite interested in decentralised publishing, this is an interesting first step!

[vitriolum]

Thanks! I hope it will evolve and become something useful.