atproto records are addressed with an AT URI, which has three parts: the host, the collection, and, the record key (shortened to rkey)
at://mozzius.dev/app.bsky.feed.post/3l7z4whnkr224
host: where it is
collection: what it is
rkey: which one it is
Thank you. This was not mentioned in other discussions before (or I missed it).
Also, this makes Bluesky currently a bit centralized, correct? All clients would need to get seeded with a different PLC directory if the current one goes away (or goes rogue), correct? A bit like the DNS root serves?
it is currently centralized for *lookup* by default, though other folks can run PLC instances (as long as they keep up with all DIDs). the operator of the PLC directory can't do much with that centralization (they can't edit DIDs or DID docs)
Just FYI: did:plc isn't the only game in town. Users can also configure did:web identifiers. Those will then not be in the PLC directory. (This is one way that ATProto is decentralized 🙂)
If you want to find those did:web PDS serviceEndpoints, you'll need to follow this: bsky.app/profile/robe...
TY, Tom! 🙏 For anyone in the future finding this, the web:did convention is to place your did details at `https://<YOUR-DOMAIN>/.well-known/did.json`.
So, eg. joncaruana.com/.well-known/...
Not really a distributed store, more like caches in aggregators. Think of RSS.
This thread explains it much better than I ever could -> bsky.app/profile/dana...
here’s a listing of your (public) data on atproto: atproto-browser.vercel.app/at/hbuchel.b...
it’s currently hosted on a bluesky server (scroll down for serviceEndpoint — that says who does your hosting). but you can move this data to another server or self-host it. the server itself is open source