







Every time I moved a community to a new platform, the exit cost members and history. Platforms come and go; the lock-in architecture underneath is why. Part of 'Apps as Views, Not Vaults': the things you make are yours; apps are just the viewers.
Your identity isn't your username
Your handle is a label; your identity is a key you own. atproto splits who you are from what you're called, so you can rename freely, prove who you are with a domain you control, and carry one identity across the apps you use. Part of 'Apps as Views, Not Vaults': the things you make are yours; apps are just the viewers.

Series: Apps as Views, Not Vaults | Guido X Jansen
Your data lives in a bookshelf you own; apps are just the views that read from it. A seven-part series on what the AT Protocol flips, what it doesn't, and why the boring architecture really does impact you.

Series: Apps as Views, Not Vaults | Guido X Jansen
Your data lives in a bookshelf you own; apps are just the views that read from it. A seven-part series on what the AT Protocol flips, what it doesn't, and why the boring architecture really does impact you.

Building Apps With ATProto
Symposium: A Skeptical View of Information Fiduciaries
In recent years, the concept of “information fiduciaries” has surged to the forefront of debates on platform regulation. In a forthcoming essay, we question the wisdom of applying a fiduciary framework to dominant digital platforms.

Come for the Network, Pay for the Tool
Paid groups, bespoke social networks, and the meaning of community for internet-native businesses.
atmosphere.community
The community hub for apps and people building on AT Protocol
The Vault: a (possible) answer to the "Fully-Private Community Data" question
Oh yeah, I should clarify that I totally expect a community DID to have a repo and in some cases, it makes sense for that repo to publish community-owned data. Just as a baseline, I think it’s good for most social activity to happen in a repo without needing to interact with the community’s repo. Even in the cases where a community DID wants to “pull in” some user content, I think it’s better for it to do it non-interactively with the user. For instance, publishing its side of things after syn...

Composable Trust, Part 1: Communities Without Credible Exit - Eclectic Corvine Muses
We guarantee that users aren’t subject to platforms. Yet communities are still subject to their stewards. Can we fix this?
Permissioned Data: Space Access - Nick's Blog
Stepping outside the shapes series for a deep dive: how space configuration decides which people and which apps get credentials. Here be dragons.
What if you could leave a social platform without leaving your community? @brittanyellich.com explains how the AT Protocol lets you own your identity, your data, and your social graph, opening the door to a more open, portable, and developer-friendly web. 🌐 youtu.be/_ZrChpf8FZ8
No one wants to own their data until the platform where their data lives enshittifies to the point of unusability and/or starts selling their data in ways they didn't expect. Like, 99% of ppl are here because Elon owns Twitter. I get why people don't care, but they tend to eventually every time.
I see talk on here about the public being "platform brained", and a lot of that in my experience comes down to impatience. It's what you see when mainstream apps change layout. People have expectations about how apps are supposed to work, and learning something else is an imposed waste of effort.
jordan silver 🔵
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.