The huge mistake everybody in dweb is making right now is that it's not about the protocol, it's about the interface. Nobody cares about HTTP, it's a badly desi

The huge mistake everybody in dweb is making right now is that it's not about the protocol, it's about the interface. Nobody cares about HTTP, it's a badly designed CRUD protocol that has spelling errors in the spec, it doesn't matter. it's the interface (AKA the web browser) that makes the the web have it's magic. All of the dweb attempts that have focused on protocols instead of interfaces have been far less successful at actual user adoption than the Beaker project was, and I hope nobody is taking the wrong lessons from this archival. The idea was fundamentally correct. The group or person that internalizes this and finds the funding, timing and momentum through an interface is going to succeed. Until then, I expect the trend of random protocols and crypto-currencies variously named Donkey Coin claiming to be "Web 3.0" for publicity to continue. In my opinion, Beaker remains the closest, and in many ways first attempt to build an actual, working distributed web that we actually have tried so far and if the history book overlooks it to focus on protocols and where the piles of money ended up, don't read that book.