> Without structure in the network, energy that could go into novel development gets redirected into facilitating interoperation, fixing edgecases between implementations, building up defenses to bad actors or security issues from other parties, and trying to coordinate evolution without a clear leader.
- Daniel Holmgren, "ATProto Ethos"
Reading things like this always makes me chuckle a little. Like, yes, it's awful that people have to spend time making the multiple working implementations of ActivityPub, which already exist, handle edge cases better. Sure would be rough if ATProto had more than one implementation. But no, it has a "clear leader" in a VC-backed company, so that shouldn't be an issue.
@noracodes It's always really telling how these kinds of people talk about the innovation prevented by interoperability overhead, but not about the innovation prevented by having a 'clear leader' that needs to sign off on everything
