That isn't what the discussion is about. It's that Bluesky's links are designed in a stupid way where changing the DID method breaks virtually everything, and the PLC DID method is deliberately centralised and in Bluesky's hands

right, but the likelihood of changing the DID method is next to none. There's literally no other identifier you could use that would give you the same properties, because you need to be able to resolve the identifier *somehow*

did:web exists and is widely used elsewhere. In my eyes it's deliberately designed to force you to forever stay on Bluesky's PLC bullshit. Peak centralisation in an otherwise genuinely perfectly decentralised protocol. No clue how that went through even the first idea phase

and thats what i said earlier. Use that globally unique unchangeable ID and done. That is literally the solution

did:web is _terrible_ tbh, since it relies on retaining domain names indefinitely. (that's $$), plus it doesn't keep a history for the DID, did:webvh is marginally better, but even then, you're still dealing with DNSSEC as the primary security mechanism which is generally well beyond most people.

but the point is that you can *change* DID methods at all without breaking everything like on Mastodon when you change instances

You loose all your posts when you change your identity on Mastodon (they stay on the old server), all past interactions point to your old server. If you "moved" your posts to your new server, you'd be doing a copy of them, because everyone's `@id` values in JSON-LD documents would be pointing wrong