The web doesn't scale, and that makes it the great centralizer. If publishing ran on peer-to-peer protocols from the beginning popularity would never be an issue.
There is this slight problem about asymmetric bandwidth and ISP-wide NAT, though…
The web doesn't scale, and that makes it the great centralizer. If publishing ran on peer-to-peer protocols from the beginning popularity would never be an issue.
There is this slight problem about asymmetric bandwidth and ISP-wide NAT, though…
I've been toying around with IPFS lately, but I still haven't figured out how me getting the repo leads to me joining a global network of peers, with data travelling seamlessly between us. I want the latter, just don't know if it's even supported now.
There are some free pinning services (pinning = inform a bot that you would like your content replicated, and then it takes care of it), including at #ipfs on irc.freenode.net, but the network itself doesn't come with such functionality and after I filled an issue on GitHub, it turns out the authors don't think IPFS should do that. Looks to be out of scope for them.
Outside of that, `ipfs add ...` publishes your content's hashes so everybody who knows the hashes can fetch the content from you.
(You also have `ipfs name publish ...` for publishing a website hash to IPNS, which can later be resolved via `ipfs name resolve <peerID>`)
I'd much prefer something like Freenet's automatic replication model. Luckily IPFS allows it, through its own facilities for extensibility -- if we have the will and resources to invest in that functionality.
They do have "flexible" schemes where the bandwidth can increase as demands grow (of course, you pay accordingly), but that's not the default.
(I'm hosted by https://www.gandi.net/)