[heinrichhartman]

Loading this page took a good 62 seconds to complete. That's 62seconds for a 78.7kb payload. (https://ibb.co/gqoUWe). At least at the present point, this is not a viable option for serving web-pages.

What I do like about IPFS is that you get links to CONTENT as opposed to LOCATIONS. This is completely independent of the hosting aspects. It would be interesting to offer content links to blog posts. I provide at least a link to the GitHub version history at the bottom of my blog posts (e.g. http://heinrichhartmann.com/blog/Latency-SLOs.html). Not ideal but at least it gives you some idea what people might have seen at earlier point in time.

In general, I see (at least) two different use cases for links:

(1) Pointers: "If you want to learn more about this, check out this website"

(2) Citations: "This website claims that there were 20 people at this event."

For Pointers you want to have the latest version of the content served at high speed. For Citations you want content links, so you can be sure your readers see what you have seen, and don't care about retrieval performance that much. So there might be a case for Citation Links being hosted on IPFS. Services like archive.org / archive.is might consider integrating with IPFS, though I am not exactly sure how that would look like.

[DailyHN]

Loaded in 1-2 seconds for me.