Interesting… I have a IPFS server running on this Windows 10 laptop. When I go to the IPFS website most of the resources load from my own server with the localhost IP address of 127.0.0.1. Kind of neat until I wanted an RSS feed to give to another box. That ain’t gonna work!
I’m in the very early stages of going somewhere with this. I’ve got an idea of an IPFS clustered swarm running behind all my webservers with a plugin doing some very neat interfacing of the CDNable content to that IPFS swarm or the IPFS itself.
This would really make some sense for a group of websites spread across the internet in physically different locations and diverse networks where the sites were located on cheap VPSs capable of running IPFS in the background. Maybe some kind of co-operative group where the members agreed to run IPFS on their local machine and their webservers which would provide more resources to the IPFS and those member sites spread worldwide over time.
One question would be ‘how do you police this network’ where the members need to bring 2X to 10XÂ their own needs to the network itself. I’d think 2X would be a minimum else I can’t see a real benefit to the co-op swarm. Maybe I’m looking at that wrong though.
This also fits into my long term vision where bloggers, content curators, content creators, and hobbyists would do their creative work on a local WordPress then syndicate or upload that content to their public-facing website. Sort of a stretched out vision of the Indieweb at its best.
Encouraging those creative souls with the means to cleanly work offline then publish online on their timetable while not stressing their own website as much. The local boxen would be a real boon to auto bloggers with heavier loads.
