2 ms·
And if you're curious what your Bluesky server is: DID=$(curl -s https://<username>.bsky.social/.well-known/atproto-did) curl https://plc.directory/$DID |
by apitman 2y ago
And if you're curious what your Bluesky server is:
DID=$(curl -s https://<username>.bsky.social/.well-known/atproto-did)
curl https://plc.directory/$DID | jq '.service[0].serviceEndpoint'
Or if you're using a custom domain (a la example.com), you can get your DID from the DNS:
dig +short _atproto.example.com TXT
- steveklabnik 2y agoThanks for this! I'd never checked. Turns out I'm on https://morel.us-east.host.bsky.network https://morel.us-east.host.bsky.network. I do want to host my own PDS someday, but then I'd be responsible for keeping it up...
- apitman 2y agoIndie hosted PDS is on my list as well. I'm also currently trying to understand the tradeoffs for did:plc more. It's unclear to me just how centralized it is. Will it always require a single central directory, or is it more like Certificate Transparency? Based on what I've heard about the recover process, I believe it's the latter, but I still need to dig into it more.
- steveklabnik 2y agoI don't know myself, but given that the discussion there, from what I've heard, is along the lines of "should be moved into an independent foundation," my assumption is that it will always require a directory. But this is probably the part of the tech stack that I know the least details about.