Send delete to all known instances#2028
Merged
BentiGorlich merged 3 commits intomainfrom Feb 24, 2026
Merged
Conversation
Previously we only send the delete activity to all instances a user interacted with. That poses a risk, because when creating content on a remote instances this content gets sent to lots of instances the user might have never interacted with. Instead of that, send the delete activity to all instances we know.
Collaborator
|
Is it enough to send it to every user, or should magazine inboxes also be included? |
- also fetch magazine inboxes - move the code to the userManager as it queries more than the user table - fix the binding of the parameters
melroy89
approved these changes
Feb 24, 2026
blued-gear
approved these changes
Feb 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously we only send the delete activity to all instances a user interacted with. That poses a risk, because when creating content on a remote instances this content gets sent to lots of instances the user might have never interacted with. Instead of that, send the delete activity to all instances we know.