the "atproto as public infrastructure" argument is gaining real traction — sebastian at re:publica today making that case to a european policy crowd. bsky.app/profile/sebastian.eurosky.soc…

This is a radically different idea than the advocacy I’ve seen for “data portability” and ”data sovereignty”. It’s a *restructuring* of power rather than small adjustments to existing structures. atproto and local-first, both in their own ways, demonstrate what such a restructuring can look like.

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.

Too many of y’all get the shape of atproto fundamentally incorrect, thinking it’s about “data ownership,” but it’s literally never been about that, and if you keep banging that drum, you’ll miss the point, just like we have every other time.

curious to hear other #atproto devs’ thoughts on fragmentation in the ecosystem? is there a thing as too much choice? many users, but all across various apps implementing their own lexicons?

Yep. This is what is missing in the ATProto vision. The lexicons should've been a like schema.org instead of domain name-based. Everyone who wants to improve it can discuss it, similar to, well, schema.org. The frontend must be separate from the content. It's beneficial in many ways.

The pitch to community leaders and creators is still taking shape, but the interesting part is the fact that ATProto changes the relationships and power dynamics they and their community have around control of data, vendor lock in, and the flexibility to create new experiences.

I love that the design of atproto was in part inspired by big social Kafka and ScyllaDB server backends and @martin.kleppmann.com's Designing Data-Intensive Applications and the community immediately used it to implement thousands of apps with no backend lol

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

Conversation here is very helpful framing for ATProto builders. The protocol has re-created the opportunity to restore the web as an open curation ecosystem that isn't controlled by any one platform, built not just on links between pages, but on the relationships between people, links and sources.

Have had this conversation more than once that essentially having to buy a domain and host a distinct machine for every single idea to be a poc in ATProto sux

new from me: on recent discourse and drama on Mastodon. the software gives people the tools to create community via instances, with a wide plurality of cultures and communities. But what people want is a singular culture/community on the federation layer connectedplaces.online/reports/fr158-what-is-mastodo…