Issue:Alias Instances do not resolve

Priority 2 Created 2023-02-09 Resolved 2023-02-25

A user with an alias domain gets a "invalid mastodon domain" error.
Sorry it seems like it did shorten it I used the full syntax @a@instance1.com but it seems like your tool is not doing the check to resolve @instance1.com to the actual @instance2.com for verification?

Basically the only reliable way is to do full webfinger lookups. E.g. find the host part, and look up https://[host part]/.well-known/webfinger?resource=[full address] (handling redirects is required by the spec)
Spec: https://webfinger.net/spec/
But note that while in this case you'll find a Mastodon instance there, there's no guarantee you'll find an API endpoint speaking the Mastodon API at any of those hosts.

2023-02-18: Handled redirection with host-meta and webfinger, wenn available, but it does not seem to be reliable. Need test cases.

2023-02-25 no new cases. Set resolved