-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
ActivityPub 'Announce' sometimes not displayed correctly as 'Boost' #10950
Comments
What is this other ActivityPub service? It seems like this could happen if the announced object is inlined and lacks an I'm not sure whether we should assume a boosted status is from the booster when no |
ClearlyClaire
added a commit
to ClearlyClaire/mastodon
that referenced
this issue
Jun 4, 2019
hiyuki2578
pushed a commit
to ProjectMyosotis/mastodon
that referenced
this issue
Oct 2, 2019
…astodon#10967) * Do not misattribute inlined boosts if `attributedTo` isn't present Fixes mastodon#10950 * Fix tests
rtucker
pushed a commit
to vulpineclub/mastodon
that referenced
this issue
Jan 7, 2021
…astodon#10967) * Do not misattribute inlined boosts if `attributedTo` isn't present Fixes mastodon#10950 * Fix tests
messenjahofchrist
pushed a commit
to Origin-Creative/mastodon
that referenced
this issue
Jul 30, 2021
…astodon#10967) * Do not misattribute inlined boosts if `attributedTo` isn't present Fixes mastodon#10950 * Fix tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm sending something like this:
Expected behaviour
It should be displayed as "@announcer boosted message (@poster@domain.tld: Text)"
Actual behaviour
Sometimes it displayed correctly (I think its when @poster is already known to mastodon instance), sometimes it displayed as @announcer's(!) post, sometimes it displayed as "@announcer boosted @announcer's(!) post"
Specifications
I'm discovering my @announcer on mastodon.social instance, both poster and announcer are from another ActivityPub service.
The text was updated successfully, but these errors were encountered: