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.

some thoughts on atproto as a post-app paradigm

I saw requests for a new way to find atproto alternatives, so I made alternativeproto.net - an atproto spin on AlternativeTo. It itself is on atproto, so you can log in and make submissions, votes, and reviews that are stored on your PDS. Give it a try and go easy, it's my first public atproto app.

Self-hosting your own atproto infrastructure is very much attainable and after going through the process, I wanted to do a little series of write ups on how to go about it. Starting with the PDS! jola.dev/posts/self-hosting-your-pds

Stray product(s) idea. A class of atproto apps should be spa's (single page apps) installable directly to our pds @wisp.place style. Apps should be distributed, not hosted. I should be able to install the Bluesky app to bluesky.captaincalliope.at, and then install that to my phone and desktop.

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

i would like to see more atproto apps that aren’t just “already popular app, but on atproto”

Are there any atproto apps that use records from competitors? This ecosystem won't feel open to me until @bsky.app uses something from outside the `app.bsky` namespace as part of its core experience