[bug] Can't undo repeat of post from rejected instance #587
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#587
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
OTPAnother person's server, so I don't know.Extra details
No response
Version
3.9.3
PostgreSQL version
No response
What were you trying to do?
I want my profile to only show recent posts, so since automatic removal only affects my own posts, I clean up repeated posts manually. To remove a repeated post from my profile, I click the repeat button again. However, if I repeat a post from an instance for which later a Reject policy is added, the post stays in my profile forever.
What did you expect to happen?
There should be a workaround to remove such repeated posts without sending anything to the remote instance. When a user clicks the repeat button under a post from a rejected instance to undo its repeat, I'd expect Akkoma to queue removals in a table until the policy changes, and to not show a repeated post in a user profile if it's present in that table.
What actually happened?
Clicking the repeat button under a post from a rejected instance to undo its repeat currently does nothing.
Logs
No response
Severity
I cannot use the softwareMinor issue.Have you searched for this issue?
please ensure you set your severity appropriately , this is not a "cannot use the software " level issue
(Sorry for the weird value in the Severity field. I'm testing how much of Forgejo is usable when I don't allowlist its JS. The issue is actually minor.)