Skip to content
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

Drop filtered messages if the filter is “irreversible” #12172

Closed

Conversation

ClearlyClaire
Copy link
Contributor

… instead of adding them to the timelines and then not showing them.
This fixes timelines showing new items when the only new items are “irreversibly” filtered toots, as well as such items taking space in the client-side lists.

This is actually an edge case in Mastodon itself, but the normal case in Pleroma, which can be used with a Mastodon front-end but does not apply filters server-side.

@Gargron
Copy link
Member

Gargron commented Oct 16, 2019

This is actually an edge case in Mastodon itself

If I'm not mistaken it never happens in Mastodon..?

@ClearlyClaire
Copy link
Contributor Author

Thinking a bit more about it, it probably never occurs in the updateTimeline case in Mastodon, but can occur in expandTimeline (for the same reason we have those filters client-side in the first place: filters not applying retroactively)

So the usefulness is pretty limited in Mastodon itself, as it only prevents TL lists to fill up with old dropped toots, the only user-facing consequence of that being old toots cleaned up “too early” (the 40 items thing) if space in-between was occupied by dropped toots.

… instead of adding them to the timelines and then not showing them.
This fixes timelines showing new items when the only new items are
“irreversibly” filtered toots. This may be an edge case in Mastodon/glitch-soc,
but it is not in Pleroma, which does no filtering server-side whatsoever.

Signed-off-by: Thibaut Girka <thib@sitedethib.com>
Signed-off-by: Thibaut Girka <thib@sitedethib.com>
Signed-off-by: Thibaut Girka <thib@sitedethib.com>
Keeping them in the TL fixes the front-end not being able to properly keep
track of pagination. Furthermore, filtered toots are not counted as unread
content, whether they are dropped or not.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants