The recent community letter calling for a de-escalation of the "protocol wars" between ActivityPub and AT Protocol highlights a critical, yet often overlooked, aspect of technological development: the social layer. While technical specifications and implementation details are paramount, the success and adoption of any protocol are deeply intertwined with the social dynamics of the communities that build and use them.
The "protocol wars" are not a new phenomenon. Similar conflicts have played out in the history of the internet, from the editor wars of the 1970s to the browser wars of the 1990s. These conflicts are often framed as technical battles, with each side arguing for the superiority of their chosen approach. However, they are also social conflicts, fueled by in-group/out-group dynamics, personal rivalries, and deeply held beliefs about the "right" way to build things.
The community letter is a welcome sign that the ActivityPub and AT Protocol communities are beginning to recognize the importance of the social layer. The letter's emphasis on shared goals, cross-pollination of ideas, and the need for a more collaborative environment is a crucial step towards building a more resilient and interoperable decentralized social web.
The existence of projects like Bridgy Fed, which bridges the two protocols, demonstrates that technical interoperability is not an insurmountable obstacle. The real challenge lies in bridging the social divide. This will require a conscious effort from both communities to engage in good-faith dialogue, to listen to each other's perspectives, and to find common ground.
The "People > Protocols > Platforms" sentiment expressed in the letter is the logical conclusion. The ultimate goal is to build a decentralized social web that serves the needs of people, not the other way around. This will require a holistic approach that considers both the technical and social dimensions of protocol development.