api: prefer duration param for mute expiration #1004
No reviewers
Labels
No labels
approved, awaiting change
bug
cannot reproduce
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs change/feedback
needs docs
needs tests
not a bug
not our bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AkkomaGang/akkoma!1004
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "Oneric/akkoma:mute-expiry-duration"
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?
Mastodon 3.3 added support for temporary mutes but uses "duration" instead of our older "expires_in". Even Husky only sets "duration" nowadays.
Cherry-picked-from:
pleroma/-@5d3d6a58f7(with edits to resolve conflicts)Side note: imho it’d be better to store the expiry in the database, checking it when relevant and from time to time clean up already expired records instead of enqueuing oban jobs for this (which might be months or years into the future and just clutter the job table). Pleroma actually already stores the expiry in the database (which is where most conflicts came from), but doesn't use it for anything except display continuing to use jobs for unmuting
durationparam for mute expiration