Various fixes #1043
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!1043
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "Oneric/akkoma:varfixes"
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?
Pulled out some conversation-unrealted fixes from the conversations API PR, a fix ported from Pleroma for leaking follow* counts in stream events I didn’t push yet and added a fix for #1042.
I was also considering porting https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4032 due to delaying streaming out of notifications only after the side-effect transaction went through being desirable (to avoid duplicates and ghost notifications when processing temporarily or permanently fails, and to not stall the db transaction with network activity).
However, this PR also breaks the
with_muted=trueparameter of the notifications endpoint by not creating notifications for muted users/threads at all (currently they are created but not send out). Thus this is deferred for now0fa6c0cb90d5b4d8f09ed5b4d8f09e83176e904283176e904280817ac65e