Isn't that more or less how Freenet works?
Yep. Freenet is inefficient, though, because it has a bunch of indirection in order to obscure the originator of the inserted documents. You could remove that indirection if you just cared about the content, not about anonymity.
If I don’t need anynomity, I would choose the Download mesh from Gnutella.
If I do need anonymity, Freenet is a very good choice.
Sorry to be pedantic... I thought their main website actually just proxies to the actual ipfs gateway. Is it technically a mirror?
I actually don't know. Since it's static HTML and assets and IPFS is still in beta they might host their webpage the old-fashioned way.
Re:Will there be a Distributed HTTP?
by insanity54 on Thursday September 03, 2015 @04:25AM
(#10163843)
In May I contributed an example to the IPFS documentation. (https://github.com/insanity54/website/commit/64db436e33662f2..., https://github.com/ipfs/examples/pull/5/commits) At that time, the site was served by github pages, but parts of the site, including the examples, were served by IPFS. On IRC, I had heard of plans to migrate the entire site to IPFS once IPNS was ready.
EDIT: seems like it's all IPFS now https://botbot.me/freenode/ipfs/search/?q=github+pages
EDIT2: Better link. https://botbot.me/freenode/ipfs/2015-08-22/?msg=47828655&pag... (The way the IPFS gateways work is you run them on a machine and bind to port 80 or whatever. Then in your DNS TXT records, you put the hash of the content you want to serve, and the gateway picks up on this and fetches the hash from the network.)
Here's how it could work: IPFS ("In some ways, IPFS is similar to the Web, but IPFS could be seen as a single BitTorrent swarm, exchanging objects within one Git repository") is a globally distributed hash-addressed versioned filesystem. (see: http://ipfs.io/)
They have a mirror of their homepage hosted on IPFS, here: http://gateway.ipfs.io/ipfs/QmeYYwD4y4DgVVdAzhT7wW5vrvmbKPQj...
To answer the question: distributed GET and HEAD are absolutely possible.