Samuel
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
9 11 139
JP ✨
How is host determined? I get how you can have a self hosted PDS but how does an ATProto app know which server contains what data?
1 3
Archived fry69
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?
2 1
bryan newbold
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)
4
Robert Lin
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...
Robert Lin@robertl.in· 3 Nov 2024
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/...
How to get the did details (including their PDS serviceEndpoint for someone with a did:web identifier.
2