Will there be a Distributed HTTP?
1–10 of 72 posts
Re: Will there be a Distributed HTTP?
#2Re: Will there be a Distributed HTTP?
#3Re: Will there be a Distributed HTTP?
#4Re: Will there be a Distributed HTTP?
#5Here'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.
Re: Will there be a Distributed HTTP?
#6And, in particular, I wrote a few months later that replacing HTTP URLs for naming content is necessary and nearly sufficient: https://www.mail-archive.com/kragen-tol@canonical.org/msg001...
We still have a long way to go, but it's heartening to see so much work toward solving the problem! Perhaps one of the systems mnot links to will evolve to solve the problem; perhaps it will be something that we haven't started to build yet.
This is crucial to the future of civilization and to the longevity of your personal work. Nearly all the effort that went into proprietary software in the 1980s and 1990s has been lost rather than becoming part of the cultural heritage of humanity, in the way that Emacs and GCC have. Similarly, everything you invest today into proprietary web services is ultimately destined for the dumpster, whether it's code you write to build them or data you store in them. We need an alternative that has a chance of lasting.
Re: Will there be a Distributed HTTP?
#7This is one of the most crucial things we need to make free software viable again. In 2006, I wrote that the only solution to the problem of proprietary services was to "build these services as decentralized free-software peer-to-peer applications, pieces of which run on the computers of each user": https://www.mail-archive.com/kragen-tol@canonical.org/msg001... And, in particular, I wrote a few months later that rep…
Re: Will there be a Distributed HTTP?
#8Problem is that it's hard to find things, just like it was hard when the Web started. There are opportunities for the next "google" of this new DHT space.
Re: Will there be a Distributed HTTP?
#9This is one of the most crucial things we need to make free software viable again. In 2006, I wrote that the only solution to the problem of proprietary services was to "build these services as decentralized free-software peer-to-peer applications, pieces of which run on the computers of each user": https://www.mail-archive.com/kragen-tol@canonical.org/msg001... And, in particular, I wrote a few months later that rep…
How do you foresee the decentralized production of CPUs being achieved?
Replicating toolboxes. Or self-replicating benchtop factories.
Microcontrollers could be produced using dip-pen nanolithigraohy, or a few other techniques.
Of course we need decent open source atomic force microscopes first.
There will always be components that can't be produced on that kind of scale. In reprap parlance we call the "vitamins". An apt metaphor.
Re: Will there be a Distributed HTTP?
#10I do work on synchronization in distributed systems, and would like to add my database, http://gunDB.io/, to the list. Why? Because it answers his questions in the "Some State and Processing Really Wants to Be Centralised" section. If you want more info on this, check out the github repo, or ask me.
Anybody interested in these subjects should be at https://2015.distributed-matters.org/ber/, Kyle Kingsbury will be doing the keynote and later on in the day I'll be presenting my protocol.
Mark's "Modifying The Web is Scary" section is important, I do see a lot of people reinventing the wheel but it isn't too hard to get everything to work over PATCH (sadly a verb which didn't take off but is in the specification) and upgrading to WebSockets.
Overall, great post. I hope more people talk about this.