Reserved *.bsky.social user does not resolve to self-verification domain user when visited

[hyp3rstrike]

Steps to Reproduce

1. Self-verify with domain
2. Attempt to browse to previous handle url (eg. https://bsky.app/profile/user.bsky.social)
3. Does not resolve. Should point to new domain user via the unique ID for the user from the reserved handle.

Attachments

No response

What platform(s) does this occur on?

iOS, Android, Web (Desktop), Web (Mobile)

Device Info

No response

What version of the app are you using?

1.96.2.542

Additional Information

No response

[gaearon]

Reserved handles don’t act as aliases; they’re just handles only you can claim back (if you decide to).

[hyp3rstrike]

Reserved handles don’t act as aliases; they’re just handles only you can claim back (if you decide to).

It probably should act as an alias though, so folks can find self-verified users using their old handles.

Self-verification in its current state breaks the username:username search for tools like skyfollowerbridge because it's searching for explicit strings based on username, display name, or profile/bio content.

If the username is permanently reserved for that UID to go back to, then there isn't really any reason why it couldn't also act as an alias. Otherwise it's just being squatted, essentially.