Brewster Kahle, founder of the Internet Archive, has pulled together an amazing group of people for what he’s calling–with only a tiny amount of hyperbole–the “Decentralized Web Summit.” Some of the “original architects” of this system–including Vint Cerf and Tim Berners-Lee–are here, or will be, along with the younger and deeply committed architects of what we all agree we want in a general way. I’m one of the participants, but I’m in awe of the people around me.
Why is this necessary? Because our technology and communications are being recentralized, and controlled, by governments and big companies. They often mean well. And we, the users, often choose the convenience (or supposed safety) that come with letting others control our communications.
Today is “Builders Day,” in which we try to figure out what we want and what’s already available. Tomorrow is a more conference-type program, and Thursday is a meetup.
Brewster started the day by asking three key questions:
- How can we build a reliable web?
- How can we make it more private?
- And how do we keep it fun and evolving.
Mitchell Baker, who runs Mozilla, suggests three basic design principles:
- Immediate. Safe instant access to content accessible via a universal address without the need for install.
- Open. anyone can publish content without permission or barrier and provide access as they see fit.
- Agency: user agent can choose how to interpret content provided by a service offering.
For some great live-tweeting, check out Kevin Marks’ feed at Twitter.
The Builders are identifying themselves and what they want out of the day. Some have macro goals. I described mine this way: We need tech and communications that lets anyone speak, read, assemble and innovate without permission, and I want to help get that done. Others have more micro goals, such as fixing specific roadblocks to the decentralized net.
One of the best: “I want to see all the ones and zeros liberated forever,” says John Light of Bitseed.
You can see the participants here. This is why I say I’m in awe.
We broke into groups, looking for areas of agreement and disagreement, plus ideas on how we can build or push forward decentralization. Then we merged groups (twice) and boiled it all down again, in order to have specific items to work on this afternoon.
What’s crucial to realize is that this is not an easy problem. Even the definitions are nuanced and complex. For example, what do we mean exactly by decentralization in the first place. There have to be some kinds of control points in some contexts.
We started with groups of six. My group(s) talked about such things as identity, encryption, and censorship. Then we compared notes (literally post-it notes) with another group and settled on some essentials to pursue later. Five other groups did likewise, and a spokesperson from each reported out to the rest of the participants.
I made an incredibly amateurish mobile phone video of the recommendations and posted it to the Archive (not, ahem, YouTube), using the new and wonderful mobile app called OpenArchive, which runs on Android. (Here’s a link to the page where the video is hosted.)
Google’s Van Jacobson talked, in part, about the inherent problems with IP (Internet Protocol in this context, not “intellectual property). It was a miraculous achievement. But it isn’t scaling as well as we need to a global (and someday interplanetary) scale.
Jacobson is working on the NDN–Named Data Networking”–project that aims to solve some of the growth issues. One key piece of this is where trust resides in the system. Today we get much of that trust from where the data originates, but perhaps we can get it from the data itself.
He chides us for our one-time “technological determinism”–a belief that we could solve any problem with tech. If some of us thought the law, or at least judges, would come to see it our way, we were naive. We aren’t anymore.
People share resources for many reasons. One is money, and he says money creates stability in a key way. He likes “commercial structures” and open-source (“almost like science”) in different ways.
A question from the audience from someone who was “super-impressed” when he first looked at it. Is there away of importing from existing applications (such as this WordPress blog)? He’s aware of the problem, but since there’s no back-end this is difficult. (In other words, no.)
Still, super-impressive, an understatement.
Much more TK…