|
|
|
|
|
by pkcsecurity
1625 days ago
|
|
Moxie makes so many good critiques (some are so subtle, it might be worth a second read). I got the sense he’s trying very hard to be even handed and constructive about a situation he feels pretty badly about, but his true feelings are bleeding through in some of the side points / parentheticals. One point that I disagree with is his almost axiomatic premise that decentralization is an inherent good and the implication that the Internet went wrong because it failed to stay decentralized. To hint at great cryptography as the solution, as he does im his conclusion, is baked deep in his bones as an amazing cryptographer, but I think he’s prescribing the wrong cure. The problems with the Internet are fundamentally not about decentralization - they’re about trust. It’s a people problem, not a technology problem. Because of this, cryptography (I do not mean crypto) simply cannot be the answer - even the best cryptography is, like a great legal system, only capable of dramatically reducing the overhead costs and risk of operating in a given environment. When it comes to what great cryptography can achieve, I think HTTPS and maybe some E2E stuff that’s happening with Signal is as good as it can get (interestingly, HTTPS is good in large part thanks to Moxie) - it cannot bring us back to some golden Internet age. |
|
For example, concurrent version control systems (like perforce) were horrible. This can be thought of as a technical problem, but it was actually right at the intersection of something technical and a people thing. What git understood is that having a canonical repo was a people issue, and it correctly abandoned a central “source of truth”… basically no amount of technology can fix what is a people problem, so no repos are “special” or “the one” from a technical point of view. It then forced people to sort their shit out. However, because of this insight, git was able to get the technical aspects spot on. It correctly recognized that what was needed was the right data structure. Git is extremely simple software, that basically does two things really well: branch and merge, but it needed the right data structure.
I think talking about centralization (APIs and infrastructure) vs decentralization (protocols) as a people vs tech problem is exactly the same sort of thing, and to get the correct view on it you have to really mail in detail where the people/tech problems begin/end.