A lot of the devs on atproto on here seem to be like, why won't any users use my stuff well, bc a not inconsiderable amount of current atproto users on bluesky are artists and marginalized people and you have a fuckass chatgpt ghibli pfp. I cannot emphasize this enough, you are signaling you don't

hard pill to swallow for atproto developers/creators: 99% of potential users either do not care about, value, understand, or want to “own their own data” i see so many apps/projects lead with this “value prop”, but it’s not an important or meaningful consideration for most people

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.

It's hard for non-technical people to understand that #atproto (Bluesky, and friends) really is a different breed of social software. One where our data, and connections are no longer taken hostage by the platform and we're free to store our data wherever we want

hard pill to swallow for atproto developers/creators: 99% of potential users either do not care about, value, understand, or want to “own their own data” i see so many apps/projects lead with this “value prop”, but it’s not an important or meaningful consideration for most people

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.

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.

The fundamental strength of ATProto — and why I think it'll last — is that it is designed first and foremost to be built upon, by anyone, for any reason, rather than locking into one specific paradigm of its maintainers' choosing. Also tbh sex workers are the social media Mandate of Heaven, so.

I mean, basically yeah! This is the atproto database I've been playing with lately.

My take on the "explaining atproto" discourse is that all the UX/filesystem/etc metaphors are still very verbose and that you can explain the same idea in a lot less words: It separates data from apps, so any app can use data from any other app. That fits in a tweet, with other sentences around it.