







The beauty of AT Protocol is that all of your data from different apps is available on your PDS, your own folder on the internet containing your stuff as JSON. This means that you can switch which app you use to view that data, without losing anything. It also makes it very easy to make connections between data stored using different lexicons, or just display activity in one place. Sifa does a nice job of this on your profile page. For web developers, and people who understand webhosting, the concept is reasonably easy to understand. I know that any atproto app I join is going to store data in my PDS, any other people will be able to see it.
Welcome to the new atproto.com - AT Protocol
We've updated just about everything about atproto.com to make it easier for developers to just build things.

bnewbold.net
Bluesky released early documentation for the "AT Protocol" (atproto) a few weeks ago, and I've been noodling around with it. Technically, it strikes an appealing balance between rigid cryptographically signed content-addressable storage on the one hand, and familiar web-friendly schemas and integrations on the other. But at an ecosystem level, there are already a bunch of existing open social media projects. Does atproto bring anything interesting to the table? How might it fit in compared to other similar protocols?
ATProto Garden
A curated directory of apps, tools, and libraries built on the AT Protocol
ATProto Integration - poke_around
OAuth, PDS sync, custom lexicons, and user bookmarking via the AT Protocol.

ATProto Architecture
Visual summary of the AT Protocol architecture: PDS, AppView, identity, records, lexicons.

atproto-wc · atproto-wc
Framework-agnostic ATProto web components. Content from PDS. Engagement from Constellation. Zero AppView dependency.
Adversarial ATProto PDS Migration | Blog
An ATProto account lives on a Personal Data Server (PDS), and that service needs to be hosted somewhere by someone. There are a lot of options here, like a Raspberry Pi in your closet, a rented VPS in a datacentre, or a batteries-included service like bsky.social.
I recently got super into the ATProto spec and how different services use PDS to store the data, I put together a quick client-only website that presents all those records in a single, consolidated feed of all my activity: at.diego.codes
at.diego.codes — Diego Vicente
at.diego.codesthe single most important part of atproto is the PDS as a user-controlled auth and storage layer to which clients can connect directly. death to appviews
Authenticated Transfer Enables Orchestration - nekomimi
blog.nekomimi.petI'm thinking about how non-developers will feel about atproto. For example, will it take people by surprise that data entered into one app can show up somewhere else? More thoughts in this post.
How do we talk about atproto to non-developers? | Rachel Andrew
rachelandrew.co.uksome thoughts on atproto as a post-app paradigm
Ecosystem Plugins
notes.wesleyfinck.org
Bluesky handle directory – PDSes

eny.space
Bitesize Proto: Two PDS containers at the same time; synchronized swimmers - Hitchhiker's Guide to the Atmosphere