Thanks, but I think this doesn't handle the LOCAL_DOMAIN vs WEB_DOMAIN cases https://docs.joinmastodon.org/admin/config/#web_domain

Is the problem that if I'm on example.com, you think this would copy @alice@mastodon.example.com instead of @alice@example.com?

If so (I don't have an account with a server like that, so I can't test), then the existing AccountHandleInfo UI would also be incorrect:

I'm a bit stumped by this one. I don't see anything in Masto.js that would allow distinguishing between the two different instance domains in that case. Does Phanpy deal with this elsewhere?

@graue you're right and right. Seems like I've already added this feature+bug in both cases; account handle UI (you mentioned above) and the Accounts selection UI.

At the back of head, I kept reminding myself that there's this LOCAL_DOMAIN vs WEB_DOMAIN case which is not possible to fix for now.

• Mastodon web cheats a little but grabbing the LOCAL_DOMAIN straight from the backend and inject it into JS.
• The right solution is perform a webfinger call Mastodon API and WEB_DOMAIN mastodon/mastodon#26848 — but most of the "well-known" endpoints are not CORS-enabled so the browsers won't allow them.

Will be looking at this and merging this later 🙇‍♂️