Operating atproto-pds: production status, endpoint surface, storage profiles, build flags, the full environment variable reference, and the deployment modes that are deliberately not wired up.
Embracing ATProto, part 1: Setting up a PDS
In this series of posts, I'll explore my journey into setting up my workflows and services for atproto. The first step is setting up my PDS. Let's start with a bit of explanation for all this lingo.
Setting up my own ATProtocol PDS - Blooym
Details of my adventures self-hosting my own ATProtocol Personal Data Server (PDS), including the painful debugging process.
Beyond the Statusphere: Part 1, Resolving the User's PDS - Hitchhiker's Guide to the Atmosphere
Learn why it's important to resolve the user's PDS and use that in your ATProto applications.
PDS Directory | ATProto PDS Index
Complete directory of Personal Data Servers in the Atmosphere.
atproto PDS & account debugger
Quick diagnostics for PDS hosts, handles, relay connections, handles, DIDs, ...
The week-end is over so I'm pressing ⏸️ on my custom PDS project for now. Here's part 2 of my dev journal. I've learned a lot already and so far I feel like it might actually be worth finishing. It's really cool to get a more intimate understanding of ATProtocol and it's implementation.
How to Make a PDS - Part 2 - Zicklag's Leaflets
zicklag.leaflet.pubthe 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.petDid a quick write up on the work I've been enjoying to make a PDS distributed. #atproto
The journey to a distributed PDS - Wills thoughts
willdot.leaflet.pub
