searchAccounts can't handle user@example.org search

[diligiant]

The "@" case calls finger without prefixing with "acct:" (done in the url case) leading to an error.

I see also an issue when you transform the ActivityPub URI https://somedomain.org/someuser into web finger URI someuser@somedomain.org as there might not be a direct match. Serving_a_different_domain covers part of it.

1. user@example.org might be handled by domainA.org webfinger (.well-known/host-meta).
2. domainA.org webfinger might return https://domainB.org/user_example_org

(example might equal domainA which might equal domainB. Who knowns?)

Imagine a world where, like email, the account is handled by google. host-meta is like DNS MX.

I dug a little bit further: On the « official » mastodon server, accounts have 2 aliases domain.org/users/user and domain.org/@user, the id being the first. Both URLs json having the first one as the id (which is also webfinger's application/activity+json), how about querying the account's json to get the id even if provided with an alias URL?

my 2¢

[davecheney]

Thank you. The search function is pretty rudimentary at the moment, it’s just enough to support Toot!’s follow/favorite across accounts feature (long press) which is how I populated the follow graph in my instance.

It’s on my list to improve.