forked from glitch-soc/mastodon
-
Notifications
You must be signed in to change notification settings - Fork 3
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
[Feature] Filter Duplicate Boosts #36
Merged
Merged
Conversation
This file contains 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
…dd small offset to max id
…dont necessarily increment
…is very old or max_id is very new when min_id is very old. removed call to subject in test because subject is memoized on first call
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
https://wiki.neuromatch.social/Filter_Duplicate_Boosts
It's annoying to see the same boost in the local TL all the time. This PR filters public feeds so only the most recent boost of a post is displayed.
It modifies the SQL query s.t. it looks like this:
So the feed selects statuses that are either a) not boosts (
reblog_of_id IS NULL
), or b) are a boost that has the maximum ID for all posts with a matchingreblog_of_id
columnBefore merging:
get
call and pass them to thewithout_duplicate_reblogs
scope, because otherwise we will be querying all boosts and statuses every time.