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.
com.atproto.repo.listRecords | Bluesky
*This endpoint is part of the atproto PDS repository management APIs. Requests usually require authentication (unlike the `com.atproto.sync.*` endpoints), and are made directly to the user's own PDS instance.*
Other PDS
Compare other ATproto Personal Data Servers (PDS): see providers, regions, and tips for choosing where your handle and social data should live.
Other PDS
Compare other ATproto Personal Data Servers (PDS): see providers, regions, and tips for choosing where your handle and social data should live.
pdscheck โ atproto PDS diagnostic
Drop in a handle, DID, or PDS URL. pdscheck runs probes against the PDS, the relay network, and PLC, then tells you what's broken and how to fix it.
atproto PDS & account debugger
Quick diagnostics for PDS hosts, handles, relay connections, handles, DIDs, ...
com.atproto.repo.createRecord | Bluesky
*This endpoint is part of the atproto PDS repository management APIs. Requests usually require authentication (unlike the `com.atproto.sync.*` endpoints), and are made directly to the user's own PDS instance.*
Is this in the reference PDS?
Stefan Judis
Quick reminder, if you're working on a SaaS product that requires a login, please check if you've defined the well-known URL to change passwords. Password managers will check `/.well-known/change-password` to offer a quick way to change passwords. w3.org/TR/change-password-url
random atproto sync notes - for whole-network backfill, you have to spread your `getRepo` requests across PDS hosts to get reasonable throughput, so it's a scheduling problem. it's also a spec-SHOULD to make these requests directly to your upstream (not PDSes directly) and follow its redirects.
An underappreciated #atproto feature is that whenever apps want to update your data: 1. they ask your PDS for permission, 2. your PDS asks you, 3. you can say no, + 4. your PDS enforces your wishes As of today, the @tranquil.farm PDS UX lets you give "partial no" answers to question 3. Bravo!
Trezy
This is awesome. I made a PR last week to add better support and display for permission-sets to the OAuth consent screen for @tranquil.farm. Now every time I log in to my Atmosphere account, I can actually see my fingerprints on Tranquil. ๐ #atproto
Rehashing this... if the main concern for atproto clients writing directly to the PDS is not having optimistic writes, then I don't get why we'd want to move towards a app server architecture as opposed to a local-first one. Are there other examples when server side computation is necessary?
The politics of purely client-side apps
pfrazee.leaflet.pub
