account names with handshake TLDs cannot be resolved in the post composer or search

[deceptionagent]

when composing a post, typing "@krystal.swor.ds" does not find the account in the live post composer or result in resolved account reference after posting. attached screenshots show that this is a valid account name and that i can otherwise resolve account names of other people.

i wasn't sure if this was proto or client, so i went client.

platform: iOS, mobile web (safari), desktop web

i do not have an android device on which to test.

[wtlgo]

This might happen because they didn't confirm their email address. I noticed that this happens to new users I invite, and after they confirm their emails it becomes normal.

[Bossett]

https://bsky.app/profile/bossett.bsky.social/post/3kispucxmkf2q - tagging the old handle works, even though it was unable to resolve either handle via auto-complete in the composer.

.ds is a Handshake domain (https://porkbun.com/tld/ds), which appears to be valid according to https://plc.directory/did:plc:sonncyo6avfaobajokkmqvm2/log/audit (and no 'invalid.handle' errors); but maybe not resolved within the app/search/etc.?

(Would suggest that the fix is likely to just disallow Handshake, as resolution is not going to be consistent; and the project doesn't have mass adoption. @mary-ext provided a simple fix at https://bsky.app/profile/mary.my.id/post/3kistqnnv4n2q - just use https://data.iana.org/TLD/tlds-alpha-by-domain.txt as the allowlist.)

[pfrazee]

Oh yeah, we don't support Handshake TLDs. This isn't strictly enforced per-se; it's just that none of the DNS resolution architecture uses it.

[deceptionagent]

yeah, now that i know tbis is handshake-related i would agree it ain't a thing you should support. would you like to close, or keep this for disallowing them?