A year and a half ago I attended
Brewster Kahle's Decentralized Web Summit and wrote:
I am working on a post about my reactions to the first two days (I
couldn't attend the third) but it requires a good deal of thought, so
it'll take a while.
As I recall, I came away from the Summit frustrated. I posted the TL;DR version of the reason half a year ago in
Why Is The Web "Centralized"? :
What is the centralization that decentralized Web advocates are reacting
against? Clearly, it is the domination of the Web by the FANG
(Facebook, Amazon, Netflix, Google) and a few other large companies such
as the cable oligopoly.
These companies came to dominate the Web for economic not technological reasons.
Yet the decentralized Web advocates persist in believing that the answer is new technologies, which suffer from the same economic problems as the existing decentralized technologies underlying the "centralized" Web we have. A decentralized technology infrastructure is
necessary for a decentralized Web but it isn't
sufficient. Absent an understanding of how the rest of the solution is going to work, designing the infrastructure is an academic exercise.
It is finally time for the long-delayed long-form post. I should first reiterate that I'm greatly in favor of the idea of a decentralized Web
based on
decentralized storage. It would be a much better world if it
happened. I'm happy to dream along with my friend
Herbert Van de Sompel's richly-deserved Paul Evan Peters award lecture entitled
Scholarly Communication: Deconstruct and Decentralize?. He describes a potential future decentralized system of scholarly communication built on existing Web protocols. But even he prefaces the dream with a caveat that the future he describes "will most likely never exist".
I agree with Herbert about the desirability of his vision, but I also agree that it is unlikely. Below the fold I summarize Herbert's vision, then go through a long explanation of why I think he's right about the low likelihood of its coming into existence.