-
-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem mentioning a user (with certain domains) #3467
Comments
The problem here is that For example if we request {
"subject":"acct:[email protected]",
"aliases":["https://re.lire.im/@admin","https://re.lire.im/users/admin"],
"links":[
{
"rel":"http://webfinger.net/rel/profile-page",
"type":"text/html",
"href":"https://re.lire.im/@admin"
},
{
"rel":"self",
"type":"application/activity+json",
"href":"https://re.lire.im/users/admin"
},
{
"rel":"http://ostatus.org/schema/1.0/subscribe",
"template":"https://re.lire.im/authorize_interaction?uri={uri}"
},
{
"rel":"http://webfinger.net/rel/avatar",
"type":"image/png",
"href":"https://re.lire.im/system/accounts/avatars/108/318/983/298/108/639/original/85c1d453ddfc458c.png"
}
]
} Notice that this is a webfinger request for This creates a problem at our end because we will end up with a local user for username in not_found:
mention_user = handle_remote_webfinger(username, unknown_only=True) # this will find the existing user but not return them because "unknown_only=True".
if not mention_user:
# this user is blocked or can't be found
continue This is tricky to solve and to be honest I think |
It seems to be somehow implemented in mastodon because I had the same problem with a large provider (sciences.re). The account @contact@sciences.re <> social.sciences.re/@contact Have a nice evening. |
In Bookwyrm 0.7.4
A user of my instance has pointed out to me that in the attached example, one of the three users (the one with the domain lire.im) is not being mentioned correctly.
I should point out that all the accounts are those of mastodon users.
EDIT :
I'd like to add a clarification that I've just discovered. The problem seems to occur when the mastodon instance has two (sub) domains (in parallel): here @[email protected] refers to https://re.lire.im/@account
Thank you and have a nice sunday !
The text was updated successfully, but these errors were encountered: