My "Introduction to #ATProto" blog post that I've been working on for some time is ready 🙂 It goes through things like records, lexicons, DIDs, then PDS/AppView etc. and how it all works together. Let me know if anything is wrong! More parts later, with the Fedi comparisons & misconceptions etc.
Introduction to AT Protocol
mackuba.euAug 20, 2025 at 6:12 PM
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
atproto made simple: publishing lexicons - underreacted
atproto made simple: publishing lexicons - underreacted
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.
This is partly why I think atproto needs a more convincing vision about being a post-app protocol. A future where atproto is a bunch of apps and each app governs their own lexicon diminishes a lot of its potential in the long-term.
Laurens
yeah i think i might actually, theres a very interesting story here that the main thing that matters is a focal point around which consensus over a lexicon can get formed
ooh nice my talk got posted! this is a 30 min whirlwind introduction to atproto through a technical lens, basically building up the stack from DIDs -> repos -> PDSes -> relays -> lexicons -> OAuth -> applications
FediForum
Have you ever wondered how #ATProto actually works? This presentation by Daniel Holmgren from #FediForum should answer your questions in 30 minutes. spectra.video/w/mDnE8FbYh1PXiaCPxsniGQ /cc @dholms.at
Yep. This is what is missing in the ATProto vision. The lexicons should've been a like schema.org instead of domain name-based. Everyone who wants to improve it can discuss it, similar to, well, schema.org. The frontend must be separate from the content. It's beneficial in many ways.
jack
we have standard.site but wen standard.pics? rn I’m juggling between @grain.social, @flashes.blue & @sprk.so for image sharing 😭
Every post, like, and blog entry on atproto sits in your Personal Data Server (PDS) as structured data you own, which means building experiences that are extremely customized to you has never been easier. atproto + AI is incredibly powerful! #atproto
Atproto Is the Context Window You Own - The Tropopause
pckt.blogAfter a long time, there's finally a new blog post. I've been working on in the past few months on a new project called Matadisco! It's about metadata discovery and publishing on #ATProto: vmx.cx/cgi-bin/blog/index.cgi/matadi… #FOSS4G #geo
Matadisco | vmx - the blllog.
vmx.cxYep. This is what is missing in the ATProto vision. The lexicons should've been a like schema.org instead of domain name-based. Everyone who wants to improve it can discuss it, similar to, well, schema.org. The frontend must be separate from the content. It's beneficial in many ways.
jack
we have standard.site but wen standard.pics? rn I’m juggling between @grain.social, @flashes.blue & @sprk.so for image sharing 😭
I'm starting a new blog post series, with some more practical tutorials about ATProto things, using Ruby and my Ruby gems :] Episode 1 - resolving handles & DIDs and plc.directory:
ATProto in Practice #1: Identity
mackuba.euatproto-reads
blogs and writing about atproto (maybe also open social generally)
The Bluesky ecosystem has the juice (ATProto for normies) - Nate Spilman
nothin' but blue skies from now on
What It Means for Universities to Run Their Own PDS: The Potential of DID as Academic Infrastructure - Nightflight
From Attention to Intention - The Open Garden
Practical Decentralization
