I was at friend's bachelor party last night so this is going to be a short one. A kind stranger sent me this tool for setting up did:web on a self-hosted PDS after I finished creating mine yesterday. This type of thing is a simultaneously fun and annoying thing about atproto right now: the ecosystem is being build piecemeal and by a wide variety of people with varying degrees of attachment to the actual org behind it, so there's not a create-react-app type starter kit for a lot of things yet. I think this is my first time seeing

We're in day 3 of the ongoing Bluesky crashout, which is making my desire to figure out how ATProto works (or doesn't) outside of Bluesky as a company feel more urgent. I remain somewhat sympathetic on both sides here. Tech people saying "you can build your own thing if you don't like it" feels dismissive and generally if you find yourself on Jesse Singal's side of a moderation argument you're probably doing something wrong. On the other hand, the levels of brigading and general nastiness of the userbase are real problems that make the site unpleasant to use. I dunno,

A PDS, or Personal Data Server, is kind of the core thing behind atproto. The idea is that it's a server that stores all your atproto data and cryptographic keys. Most people just use Bluesky's PDS right now, but this is probably the most commonly self-hosted part of the ecosystem: you can store all your data for any atproto-compliant app on your own server which, in theory, keeps it from getting walled off in an adversarial scenario.

I'm not quite ready to risk moving my own data off of Bluesky's PDS, but I figured today I'd take the first step