Skip to content
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

Attempting to act on boosts on profile feeds result in Mastodon error #96

Closed
austinhuang0131 opened this issue Jan 31, 2023 · 1 comment · Fixed by #98
Closed

Attempting to act on boosts on profile feeds result in Mastodon error #96

austinhuang0131 opened this issue Jan 31, 2023 · 1 comment · Fixed by #98
Labels
bug Something isn't working
Milestone

Comments

@austinhuang0131
Copy link
Contributor

Bug description

Attempting to act on boosts on profile feeds result in Mastodon error (cannot find activity) as it's using the boost activity ID instead of the original activity ID.

Steps to reproduce

  1. Go to any profile feed on a v4 instance.
  2. Act (fav/boost) on a boosted post. (Clicking the post then fav/boost does work)

Actual behavior

The boost's activity ID is referenced in the callback, which results in an error on the home instance's side.

Expected behavior

The original activity ID is used for callback.

System

Operating system and version: not relevant
Browser and version: Firefox
Add-on version: 2.0

Possible solution

Fetch original activity ID?

@austinhuang0131 austinhuang0131 added the bug Something isn't working label Jan 31, 2023
hueyy added a commit to hueyy/mastodon-simplified-federation that referenced this issue Feb 5, 2023
@hueyy
Copy link
Contributor

hueyy commented Feb 5, 2023

Yes you're right, the activity ID being used was wrong. Should be fixed by #98.

@rugk rugk closed this as completed in #98 Feb 9, 2023
@rugk rugk added this to the v2.1 milestone Aug 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants