There's an interesting dynamic because of the domains, I originally registered with `n1c.bsky.social` because like you say whether I intended to use the service or not it's nice to lock in the name. But then the next level is that it's actually more valuable or makes more sense for me to use it as `n1c.dev` as it's more closely tied to "me".

I am kinda sad that now someone else who isn't me is n1c.bsky but so be it.

I think this is a meaningful security problem. Most users won't know that the domain name matters. They'll learn eventually, but lots of opportunity for mischief in the medium term.

If you have `n1c.bsky` and then migrate to `n1c.dev`, Bluesky should set `n1c.bsky` as a redirect to your destination domain by default. If you ever choose to terminate that redirect, `n1c.bsky` can go back in rotation... but it should have an immutable record that you registered the name originally, migrated to `n1c.dev`, maintained a redirect, and released the redirect on <DATE>.

that would defeat the purpose of a decentralized network if only one person was jim, jim.