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.

Our last post was posted as part of our first #ATProto integration demo, which also sent it to @leaflet.pub. Check out the video and the canonical webpage for more: youtube.com/watch?v=UFBXdFAKgWI and demo.ideastore.dev/publish-to-at #octothorpes joins the #atmosphere

ATProto is a post-app protocol trapped in a world of apps. I can feel it all around the edges of the network.

Introducing Wireservice. Today, it's a WordPress plugin in alpha for publishing to @standard.site. Tomorrow, it's... another longform content lexicon? A news aggregation app on atproto? We'll see. wordpress.wireservice.net/index.php/2026/02/19/introduc…

ill add components to atproto-ui for this too :D, id love to embed some of these into my personal websites

I have heard from our favourite network layer protocol madman that unexpected atproto integrations are occurring. No, lower level than you’re thinking.

Do you need to run a PDS, PLC, Jetstream or TAP for development and testing of your #ATprotocol app? A couple of us needed it for independent projects and we try to DRY so first pass is at github.com/OpenMeet-Team/atproto-devnet How are you managing that stack for your project?

while i've been loudly proclaiming in the atproto devs discord meetings that you probably don't need an appview for your atproto side project, i'm now also working on my own "atproto backend in a bottle" that runs on cloudflare workers 😅 still super WIP, but happy for any early feedback

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