4 ms·

... and the page doesn't load for me at this moment.

• d4l3k 8y ago
  You can also access it via the normal website: https://fn.lc/post/dropbike/ https://fn.lc/post/dropbike/ (or via AMP cache: https://fn-lc.amp.cloudflare.com/c/s/fn.lc/post/dropbike/ https://fn-lc.amp.cloudflare.com/c/s/fn.lc/post/dropbike/) I've had IPFS support on my website for a while now and figured since one of the top HN posts was about porting a blog to IPFS I'd share the IPFS link.
• tudelo 8y ago
  Loads for me :)
• geerlingguy 8y ago
  Yeah... just sits loading forever here too.
• prophesi 8y ago
  Yeah, ipns links are pretty slow compared to ipfs links. The best practice is to have a domain using dnslink[0] which always points to the most recent IPFS hash on a gateway with the content already pinned. I believe this is what the IPFS team does for their blog, using a combination of a static site generator and web hooks. [0]: https://github.com/ipfs/go-dnslink https://github.com/ipfs/go-dnslink
  • d4l3k 8y ago
    Oh, that's pretty neat! I hadn't seen that before. Does dnslink work with browsers at all?
  • xur17 8y ago
    I just installed ipfs and noticed this as well - ipns performance is pretty terrible. I tried loading a page that was created (and therefore stored) on my node, and it takes a good 10 seconds to load). edit: looks like this might be relevant: https://github.com/ipfs/go-ipfs/issues/3860 https://github.com/ipfs/go-ipfs/issues/3860