atproto offers an fascinating example of what it means to restructure this relationship. End-users get to choose who and how much trust they delegate to software producers, the delegation of trust becomes tangible and revokable.

Behold, the official release of my "simultaneously protocol argument and shitpost*" article: How can ATproto communities have credible exit from—that is, "can yeet away"—their hosting platforms? And how do small fuck-ass sites help? essentialrandomness.com/posts/the-concierge-and-the-v… *100/10 endorsement

That should be the guiding principle for all atproto "alternatives"

atproto is actually a massive socioeconomic experiment in which we test the hypothesis "contributors to the common good who deserve success should be able to find it" and initial results are looking good

What I am learning from this outage is that if you were naive enough to believe that the atproto overview docs and architecture diagrams presented a true view of how bits of software rely on each other (🤚) you have a very distorted view of how how the network actually works.

If ATprotocol fails it'll be because of the leadership and the community's inability to put aside their charismatic technology and solipsistic nature and actually center actual user needs even if it hurts their feelings, or doesn't come through in the delicate language that makes them comfortable.

Can everyone building on atproto please answer this question? 😇