No. What I mean is a DNS-like system for the globally unique IDs I proposed, where information of where the user is stored (which PDS) is relayed and the user's current PDS is the result, if that makes sense. Basically makes the did secondary only.

That way, not a domain or a PLC would hold the truth, but the user's PDS. There surely are some loopholes and issues with that but I can't get over how unnecessarily restrictive bluesky did it by locking you into PLC

How do you find the user's PDS when you don't know who the user is. I give you a record that has a link in it of: at://did:key:z6MkrJVnaZkeFzdQyMZu1cgjg7k1pZZ6pvBQ7XJPt4swbTQ2/app.bsky.feed.post/3lxd54zft7k2s How do you locate the PDS that holds that data?

You need something to resolve from did:key to the actual DID Document that contains the service URL for the PDS. Some how you'd go from: did:key:z6MkrJVnaZkeFzdQyMZu1cgjg7k1pZZ6pvBQ7XJPt4swbTQ2 To: did:plc:upo6iq6ekh66d4mbhmiy6se4 And then fetch the record indicated by the PDS in that did doc