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

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.

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?

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.

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.

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

There's lots I haven't yet understood about atproto, but I simply won't do the standard.site thing whilst it offers a worse UX than… not doing it.

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…

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…

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.

ATProto/ActivityPub rivalry notwithstanding, omfg if I were Mastodon today I'd be so angry at this

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.