Report on the current experience of using IPFS to deploy a website

I had to stop using IPFS to read websites because it kept crashing my router. It makes hundreds of connections to other IPFS servers. And if you have working IPv6 it makes many of those twice. I'd often see over a thousand, then the router would slowly stop working until it self reset.

There may be a way to limit the number of connections but I never looked too hard. My plan still is to put the cable router into bridge mode and start using my own router with OpenWRT -- but that's been my plan for a couple of years now, so you see that the follow-through is lacking.

The Inter Planetary File System has the potential to radically change content hosting to become truly decentralized. This report names some of the most pressing barriers to widespread adoption of ipfs.

In my opinion the biggest issue is terrible documentation on ipfs.io (as noted by the report). The "Getting Started" page fails to explain the basic structure of ipfs and uses jargon that isn't defined. This lack of documentation prevents even tech savvy users from adopting ipfs.

Tried setting up an IPFS website using Hearth, and I ran into the links issue. Gave up pretty soon after in favor of GitHub Pages.