Stepping outside the shapes series for a deep dive: how space configuration decides which people and which apps get credentials. Here be dragons.
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.
Open Forks of Boring Apps With Authority - Woodys Rows
The Atmosphere can win by becoming the foundation for software people already need to use because of real-world relationships.
Polyglot Software Unconference 2026
A day of spontaneous sharing, learning, and networking for software builders. Participants set the agenda using "open-spaces" format.
What is a Group Host? - at:// pizza thoughts
Describes an hosting pattern for Atmospheric Group accounts, including group creation and app authorization flows
Permissioned Data Shapes: Notifications - Nick's Blog
A self-keyed space gives notifications a home you control: every app gets an append-only sink to write into, you pick the reader that turns them into pushes and emails, and allowing or revoking an app is an access control you already have.
Atmospheric Login Page
The UX decisions behind my Atmosphere apps login pages — saved handles, handle autocomplete, and a 'create account' guardrail that slows people down on purpose.
Who actually owns your network?
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.
Atmosphere Account
One account for all your apps. Yours to keep, wherever you go.
Tech, Socials, & Online by @sweetbee.vip
Curated list of accounts in tech space, sorted with a personalized algorithm
So this is one of the cool things about apps in the Atmosphere. They have to declare what stuff in your account they're going to touch.
ATStore
You find a cool new Atmosphere app. You click sign in. And then... a wall of permission requests you didn't expect. 😬 ATStore fixes that. Every app listing now has a "scopes" badge, tap it to see what the app will request before you ever log in. ⚠️ Requesting dangerous scopes? Get warned.
whos going to be the 1,000th @offprint.app user?
Claude is inheriting a centralized app-centric bias here (which existing OAuth profiles may share) To wind up in a decentralized world where all "my data" lives on "my PDS" -- regardless of how many atproto apps I authorize to store stuff there for me (see 🧵) -- we should invert that paradigm
Paul Rohr
TL/DR = yes, it's a subtle conceptual shift: - from app-centric (apps control identity/data, delegating access to you at signin) - to identity-centric (you control identity/data, delegating access to apps at signin) Really looking forward to how the team evolves the OAuth UX to address this! /END
Seventh in the atproto permissioned-data series: notifications. One self-keyed space per identity, every app writing through a create-only grant, and a reader you choose doing the triage. The self shape returns, direction flipped.
Permissioned Data Shapes: Notifications
ngerakines.leaflet.pub
