Tech of, by, and for the people

On February 18, 2021, the movement toward a decentralized web took another step forward. The people behind the Decentralized Web Summits and DWebCamp 2019 launched a new website for organizing and information: GetDWeb.net.

About 100 people joined a Zoom call to learn more about the site, and talk about the future of the project, focused on the principles of this movement.

Some things I learned

Here’s a quick summary of what I learned at the launch:

  • The design and building process for GetDWeb.net took about 13 months.
  • You can access the site using two decentralized protocols besides good ol’ https. Open the Brave browser to see the site on the Interplanetary File System (ipns). Use Beaker Browser to see it on Hyperdrive.
  • The project runs Meetup groups in nine cities: Five in the US, three in Europe, and in Shanghai. The site offers tips on starting a new one where you live.
  • Want to learn more about the project? The resources page contains links to a variety of articles and videos to help you. The FAQ page (once you get past the Meetup section) answers common questions.

What I didn’t learn

Now you might come to a site called “Get DWeb” expecting to find “how to get on the decentralized web.” That is, you’d find tools to access an existing decentralized web.

The FAQ suggests this disappointing reality:

Some apps and programs, built on the decentralized model, are already available and you can sign up and use them at will. But the Decentralized Web, as an ecosystem, might not be fully functional and integrated for another five or ten years.”

GetDWeb FAQ, “OK, sign me up. How and when can I get on to the Decentralized Web?”

Is this the “only” Decentralized Web?

The thing about decentralization is that by its very nature, there’s no central control. I might set up a decentralized network of websites that might not make a bit of sense to you. You then have the option to create a different network that makes sense. Of course, then you have to justify your sensible network to get other people to join.

Last fall, a group called Rebellious Data released a report called “The Decentralized Web of Hate.” It outlined the use of decentralized peer-to-peer (P2P) tech by white nationalists and other extremist groups on the political right. The report gained a whole lot of readers after the January 6, 2021 insurrection at the US Capitol.

The folks behind this effort toward a decentralized web might describe themselves as a polar opposite to the groups described in the Rebellious Data report. Because San Francisco’s Internet Archive is its initial sponsor, I’m tempted to call this project “The Decentralized Web of Love,” but that’s just because I’m old.

This project worked out a set of principles that should make sense to more than a few people. They released the first draft on the website after being hashed out by “members of the DWeb Community — those involved with and convened by the Internet Archive’s work on the decentralized web.”

One problem with the principles

Now I happen to think that this is an excellent set of ideas to undergird this project. I just have trouble with one thing: It is abundantly clear that the folks who drafted these principles are highly educated people who have spent a really long time thinking about and building the Web and other useful technologies. That’s fantastic, of course, but if you’re not part of that group of people, you might have some trouble understanding where you fit in.

Now I have some experience translating Geek-to-English, so I tried to apply some of that experience to these draft principles, and put them in the table below. I hope they are a little easier to understand.

On the left side is the original text, copied from the Principles page at https://getdweb.net/principles. My text is on the right, labeled Revision.

Disclaimer: I never spent a minute with the Stewards or Contributors listed at the bottom of the page. I have no idea what discussions went on to carefully parse any disagreements among the drafters. Generally, I have tried to maintain all the ideas in the draft, but if I left anything out or misconstrued something, that’s totally on me.

Where I have a Note, that’s usually just my speculation aiming to improve understanding of my readers (you). But the Principles committee is certainly welcome to adopt some or all of these suggestions for improved readability.

PrincipleRevision
Technology for Human Agency
We stand for technology that enables the primacy of people as beneficiaries of the technology, by upholding their security, privacy and self-determination.People come first — Their security, privacy and the ability to decide for themselves.
We urge coexistence and interoperability, and discourage walled gardens.If you decide to switch platforms, for whatever reason, you should be able to move every character, every image, every piece of data with minimal interference.
We value open source code as a fundamental building block of an open and inclusive Web.You can view the source code of every page on the World Wide Web in a browser. This should continue. The door is open to the use of proprietary algorithms, but they should not be the norm.
We aim for peer-to-peer relationships, rather than hierarchical control and power imbalance.People use the Web to collaborate and share information. Companies that build websites should not have control over the Web.
(Note: BTW, if we’re not crazy about hierarchies, why are the principles in a numbered order? I’d favor bullet lists.)
Our technologies must minimize surveillance and manipulation of people’s behavior, and optimize for social benefits and empower individuals to determine how and why their data is used.Websites should focus on social benefits and empowering its users. People should have control over their data. Companies should not profit from user surveillance and manipulation.
We believe that multiple technical means will be more effective than a single technical solution to achieve ethical and people-centric outcomes.Our decentralized Web will not pick a single technology to achieve its goals. We will focus on ethical and people-centered outcomes.
(Note: This may be a swipe against those who believe that no decentralized web can happen without running on a blockchain.)
Distributed Benefits
We believe that decentralized technologies will be most beneficial to society when the rewards and recognition of their success, monetary or otherwise, are distributed among those who contributed to that success.Our decentralized web aims to reward and recognize the people who contribute to its success. That’s how society will benefit the most.
If that is infeasible, proportionate benefit should flow to the community at large.If we can’t effectively reward only contributors, or if everyone is a contributor, we aim to reward the community as a whole.
High concentration of organizational control is antithetical to the decentralized web.Our decentralized web will not recreate today’s web. Control resides with people, not companies, oligarchies, or similar organizations.
Mutual Respect
We support and encourage codes of conduct to ensure respectful behavior and accountability.Individuals participating on the Web should be kind.
We expect participants to remain mindful of, and take responsibility for, their speech and behavior, by acting out of respect for others and respecting physical and emotional boundaries.With great power comes great responsibility. Respect others, be kind, and do the right thing.
We stand for open and transparent organizational practices, motivations, and governance, in a manner that actively pursues equity, mutual trust, and respect.If you own a site, be open. Your users need to trust you to do the right thing.
Humanity
The objective of building a decentralized web is to protect human rights and empower people, especially those who experience systemic inequity and prejudice.Our decentralized web will protect all human rights. It aims to empower all people, no matter who they are, where they were born, what color their skin is, their economic status — all of it!
We stand for people having agency over their own data and relationships, rights to free expression, privacy, and knowledge, as these are essential to human empowerment and dignity.People come first in our decentralized web. They can define their relationships to others and to the sites they use. Free expression, privacy and the right to information are essential.
We condemn the use of distributed tools for activities antithetical to human rights, such as human trafficking; sexual, mental, or physical abuse; and arms trading.Our decentralized web opposes using decentralization to hide anti-human activities, including but not limited to: human trafficking; sexual, mental, or physical abuse; and arms trading.
We encourage building with harm-reduction in mind, and support the adoption of mechanisms that mitigate the potential for abuse, and consideration of those ‘not at the table’ — not connected, not users, and the disadvantaged.Our decentralized web aims to be free of hate. We will take steps to reduce online abuse of people, whether or not they’re connected.
We encourage the development of tools and applications in many languages and forms, with a high degree of accessibility.To be effective, the World Wide Web must be accessible. Our decentralized web aims to make the web usable and accessible to every human, regardless of their physical (dis)abilities, mental health, or the language they speak, read or hear.
Ecological Awareness
We believe projects should aim to minimize ecological harm and avoid technologies that worsen environmental health.Our decentralized web is conscious of human impact on the climate, heating the climate and making the current crisis worse. We aim to do better, because people (and other living things) come first.
We value systems that work towards reducing energy consumption and device resource requirements, while increasing device lifespan by allowing repair, recycling, and recovery.We will work to reduce technology’s impact on the climate. We recognize that no one should have to buy a new computer, phone, or other device every year to get full access to our decentralized web.
(Note: This may also be a swipe at blockchain-based distributed apps. A recent report indicated that global mining for Bitcoin uses more fossil fuels than the entire country of Argentina!

People should be able to fix, upgrade, recycle and swap parts to keep their older systems going, especially in underdeveloped parts of the world.
(Note: This is likely a swipe at Apple and other device manufacturers that plan obsolescence into their product pipelines.)

An important step for the DWeb

This website is a great way to gather new forces for the enormous tasks ahead for the decentralized web project. While kibitzing on the side of this group since discovering the first Decentralized Web Summit in 2016, I’d like to get more involved now. I hope you might too. You’ll learn a lot from the people involved, and this is an important evolution of the Web, and people’s ability to inform themselves and collaborate with others.

Brave Browser adds IPFS support: Do you care?

Diagram of a decentralized web developed by Paul Baran in 1964

Have you ever tried the Brave web browser? Since its founding in 2015, Brave Software has quite a record of innovation with its browser, but hasn’t made much of a dent in the browser usage competition.

A long suspension footbridge across a river in a forest.
Photo by Sven Huls on Pexels.com

Over the years, Brave has implemented:

  • A built-in ad blocker that’s On by default
  • Allowing Brave users to contribute (in cryptocurrency) to registered web publishers
  • Allowing users to browse via the anonymous Tor network

Just last week, Brave added support for the InterPlanetary File System (IPFS), a pathway to the distributed web. Jon Porter’s story on The Verge has the details. IPFS seeks to replace the Hypertext Transfer Protocol (HTTP) as the way to access sites on the web. Instead of pointing to an address on a single web server, you point your browser to an IPFS node address. The content would exist on other IPFS users’ computers.

Costs of Innovation

You would think with its focus on privacy, Brave would be more popular than its claimed 24 million users. Implementation issues have plagued the browser, though.

  • To placate sites (and advertisers) whose ads were blocked, Brave offered a scheme where users could agree to view “Brave Ads” sold by Brave Software. Users get crypto tokens as a Reward.
  • The revenue from “Brave Ads” would fund the publisher payment program. Is it an accident that the Rewards support board averages 84 posts per week? Many of those posts are variations on the theme of “Where’s my money?”

Brendan Eich and Conservative Politics

Some of us will not forget that Brave’s CEO, Brendan Eich, was forced out of the CEO’s chair at the Mozilla Corporation in 2014. He contributed to an anti-gay-marriage campaign in California two years earlier.

Eich, who created the JavaScript programming language while at Netscape, has long associated with conservative and libertarian causes. In the 1992 presidential campaign, he contributed to Pat Buchanan’s rightist primary challenge to George H. W. Bush, and also helped fund Ron Paul’s campaigns.

More recently, he apparently joined in the disinformation campaign around COVID-19. He doesn’t like masks.

A decentralized alternative: Beaker

What all the news stories on Brave’s IPFS support miss is that there’s another peer-to-peer protocol that does very similar things. It’s called Hyperdrive (originally DAT), and is supported by the Beaker Browser, which I’ve written about before (here too).

The Beaker developers explain Hyperdrives like this in their documentation.

“Hyperdrives” are like websites. They store webpages, pictures, media, user data, and so on. Hyperdrives power a lot of Beaker’s best features.

“Hyperdrives” are folders you host from your computer. They contain web pages which you can browse and edit. You can create and share hyperdrives using Beaker.

Beaker Browser Documentation

Works in Progress

I’ve played with IPFS a little, and suspect I might give it another whirl soon. Same with Hyperdrive and Beaker, which I’m a little more excited about. Go follow Paul Frazee on Twitter (@pfrazee) or YouTube (Paul Frazee) to see what’s he’s innovating on the peer-to-peer front.

The big problem with IPFS isn’t the technology per se, it’s that ordinary folks can’t access files stored on the system, even if the (Brave) browser supports it. There’s no effective search engine, or directory of the IPFS world.

Beaker/Hyperdrive/DAT has an index page to the sites they know about, but of course you have to open those sites with Beaker, the only browser to handle dat: or hyper: pages.

Looking forward to the next round of innovation for all these projects. May the best project win!

(Yes, the post is late this week. I’m the victim of two traditional Wisconsin catastrophes: The Packers lost on Sunday, and a nasty snowstorm hit last night. Aiming to do better in February…)

Related posts

Inrupt, the NYTimes and agenda-setting

In the 30-something years since Sir Tim Berners-Lee invented the World Wide Web, waves of change have swept through the mass media. In the last week, I’ve discovered one thing that hasn’t: The New York Times still sets the agenda for what the world knows about at any given moment.

Perhaps you’re thinking about Donald Trump, the electoral college and the riot/insurrection or whatever else you want to call what happened in Washington, DC on January 6, 2021. That story would likely dominate the front page in any country with a free press. Where the Times really makes its mark is in the less spotlighted areas.

Witness last Sunday (January 10, 2021), when the paper ran a story by Steve Lohr on a relatively new project from the very same Tim Berners-Lee (paywall) I mentioned in the lead paragraph. Google News flagged this story for my attention. I didn’t get it read right away. The next day, when I posted here, I noticed that traffic here at Notes had bumped up considerably, and the people were coming to read this story I’d written at Inrupt’s launch two years ago! (Thanks to all of you, BTW.)

If you want to know more about Inrupt, Lohr’s piece is a good place to start, but here’s a rough timeline.

The story spreads

Google News not only showed me the Times story, but had one of those lovely “full coverage” links, indicating that multiple media outlets were covering Sir Tim and his startup. The curious thing is that most of the stories predate the Times piece.

Oh, but within a few days, we also see stories covering Inrupt in places like the India Times, a reprint in the Charlotte Business Journal, TelecomTV, the youth citizen-journalism site Unilad in the UK, EMTV in Papua New Guinea

Two days after the Times runs its story (hmm…coincidence?), Berners-Lee speaks at the Reuters Next conference sponsored by the Thomson Reuters news service and covers many of the same points.

Then comes the commentary

As for me, I’m optimistic but realistic. Reviewing my original thoughts on Berners-Lee and Inrupt, I regret suggesting that Sir Tim was trying to cash in. Inrupt has so far succeeded in building up the Solid Project, at least to the point where The New York Times and Reuters are bringing the message to a broad audience. I’m looking forward to hearing more about Inrupt’s pilot projects at the British National Health Service, Flemish government and the BBC.

The idea behind Solid is important. Using both old and new web standards to share what we want — and only what we want — with giant corporations and governments is something we have a right to expect. I look forward to getting some practice using my Solid pod.

What do you think?

2nd Decentralized Web Summit Brings Piles of Working Code

Diagram of a decentralized web developed by Paul Baran in 1964

Honestly, for a while there, I thought the movement for a decentralized web was quietly fading away. There wasn’t a followup to the 2016 Decentralized Web Summit, and hardly anyone outside of a television sitcom seemed to be talking about these ideas, much less building alternatives.

Well, I am here to happily admit I was wrong. Truth is, it takes time to build software that might change the world. The second Decentralized Web Summit happened at the beginning of August, again in San Francisco. I didn’t go, but followed it intensely from afar. The sponsoring Internet Archive promised “working code” as a theme, and it delivered. The summit opened with a “science fair,” where 70 different projects showed off what they’d been working on, and there were enough people to walk around and see the presentations!

Wendy Hanamura of the Internet Archive reported that 800 people registered for the conference. I don’t know what expectations organizers had, but that sounds like a lot of people to this observer!

Time to follow Mozilla

It’s really exciting to see how heavily involved folks at the Mozilla open-source browser project are with solving the problem of decentralization.

Before the Summit began, the Mozilla Hacks blog for developers started a series of posts “Introducing the DWeb.” Since then, every Wednesday the blog features a developer of a decentralized project describing the project. As of this writing, three projects received exposure:

Mozilla Chair Mitchell Baker also gave a keynote address at the Summit, “Revitalizing the Web.”

I am really looking forward to a version of Firefox that supports the decentralized Dat protocol that Beaker uses.

Where was the tech media?

Startling that more mainstream journalists weren’t there. Vanity Fair profiled Tim Berners-Lee the week before, but as I write this, there were no reporters like Dan Gillmor and Kevin Marks writing stories for Fast Company as in 2016. I could be wrong, of course.

In the meantime, I can point you to a pair of good conference summaries:

Computing.co.uk: A nice summary from John Leonard

TheNewStack

More summit resources

As you can see, a lot happened. As I watch more video and otherwise catch up with what happened in San Francisco, I’ll keep reporting here. I’m also looking forward to playing with MIT’s Solid protocol, which I almost didn’t mention!

In the meantime: You can pretty much watch the whole conference in bits here. You can also spend some time following the #DWebSummit hashtag on Twitter.

Two more keynotes to bring to your attention:

  • Cory Doctorow always gives a thought-provoking talk, this one focusing on the question of “big tech.” I would have loved to seen any interaction he had with Tim Berners-Lee during the summit.
  • Host Brewster Kahle (founder of the Internet Archive) gave a laid-back talk about how we got ourselves into this mess, and how we can get ourselves out.

This is all to say that I am more confident that we may be at the dawn of another age on the Web than I was six months ago. I’ll still be writing about it, here and elsewhere.

Were you at the Decentralized Web Summit? What’s the most important thing I missed? If you weren’t there, do you wish you had been? Thoughts on the prospects of decentralizing the web on a mass scale are also appreciated.

More Thoughts on a Decentralized Web

Diagram of a decentralized web developed by Paul Baran in 1964

Last week, Tara Vancil from the Beaker Browser project posted a timely set of tweets about how supporters of a decentralized web talk to people about it.

In Plain English…

Some good ideas here, especially when aiming to win developers over to the cause. I truly hope this doesn’t come off as “mansplaining,” but in more common terms, more people might understand the benefits she raises in the first tweet:

  • Algorithmic transparency: You should be able to describe why you see what you see online. Content providers (including social networks) should also be able to describe what the rules are when they display some posts over others. Algorithms used in web development should be based on open standards. It should also be transparently easy to determine whether Internet Service Providers are providing fast lanes for preferred sites.
  • Customizable apps: You as a user should have control over what your software does. You should define what information you share and with whom.  The providers of a web service should not collect information about you that you don’t explicitly approve. The same terms go for Internet Service Providers, should you choose to use one.
  • Member-defined communities: In a decentralized web, you don’t need a service like Facebook or Google Plus to engage with other people like you. If everyone has a website, and used web standards to Mention and Comment on posts made by friends, colleagues or total strangers, that’s a decentralized community. In the early days of the Web, people set up “WebRings” of sites sharing similar topics. Rings helped users to find information on things they cared about. These sites often engaged in conversation with each other.  Sounds a bit like what people use Facebook for today.
  • Permissionless publishing: This is the essence of the Open Web. Anyone can publish anything online without getting someone’s approval first. Of course, this central value is a mixed blessing when some people, companies, and political entities (parties, interest groups, governments and the like) are not morally committed to publishing the truth. We need to remember that this has always been true. There’s a reason “It has to be true!  I read it on the Internet!” is a cliché.

Descriptive Names

Of Vancil’s more descriptive names, I’m OK with all of them, with a slight preference for “person-first.” All of them might get a befuddled reaction (“huh?”) at first, but should spark further conversation. The idea of putting people first will generate more smiles at first hearing, and may generate more ideas for how to put people first, which makes for a more productive discussion about what the web means with either developers or other persons.

Good News: Second Decentralized Web Summit

Speaking of conversations, there’s a venue for that! A second Decentralized Web Summit is happening this summer! As you may know, the drive to (re)decentralize the web gained a bit of public attention two years ago when some of the web’s founders convened the first Summit at the Internet Archive in San Francisco. The same folks are preparing a second gathering at the Internet Archive on July 31 – August 2. Visit the conference site to get on the Updates mailing list.

Announcement of the 2nd Decentralized Web SummitI hate when conferences skip a year, especially after the first time. It seems like nothing is moving forward. I’m glad to be proven wrong. The theme for the conference is “Global Visions / Working Code.” Certainly a hopeful theme. The conference founders (not-so-coincidentally present at the web’s creation) will give keynote addresses, including Sir Tim Berners-Lee, Vint Cerf, Mozilla Board Chair Mitchell Baker, and Internet Archive founder Brewster Kahle.

They will be joined by some of the people building that working code: Juan Benet, the founder of the Interplanetary File System (IPFS), and leaders of the DAT Project, a data sharing protocol, on which you can build applications (like the Beaker Browser) and connect with other people. While none of these leaders are named in this announcement, I suspect (and hope) that Tara Vancil will be among them.

Assuming the conference will follow a similar schedule as its predecessor, the keynotes will be followed by workshops and other opportunities for participants to learn, discuss and collaborate. I hope more can come out of it.

Do these new terms help you understand the promise and the value of a decentralized, “people-first” web? What stumbling blocks do you foresee? Is this the future, or a futile bid for a world that has become hopeless? Thoughts, critiques, support and well-reasoned denunciations welcome in the Comments section.