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.

Sign up for GitHub

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

Jump to bottom

Adding/removing keyword mutes should remove/add existing statuses from/to the home feed #199

Open
hannahwhy opened this issue Oct 25, 2017 · 0 comments
Open

Adding/removing keyword mutes should remove/add existing statuses from/to the home feed #199

hannahwhy opened this issue Oct 25, 2017 · 0 comments
Assignees
@hannahwhy
Labels
enhance feature expansion ft-keyword mute

Comments

@hannahwhy
Copy link
Member

Currently, modifying the keyword mute set does not affect statuses already in the home feed.

When adding a keyword, statuses in the home feed that match that new keyword should be unpushed from the home feed. When removing a keyword, we should do something analogous to restore statuses matching that keyword.
@hannahwhy hannahwhy changed the title Adding/removing keyword mutes should remove/add statuses to the home feed Adding/removing keyword mutes should remove/add existing statuses from/to the home feed Oct 27, 2017
hannahwhy added a commit that referenced this issue Nov 19, 2017
@hannahwhy
When the mute list changes, queue up a home feed regeneration. #199.
307a8df
@hannahwhy hannahwhy self-assigned this Jun 12, 2018
hannahwhy added a commit that referenced this issue Jun 13, 2018
@hannahwhy
Stub out Glitch::ApplyKeywordMutesService. #199.
083f78b 
This service will apply/unapply keyword mutes to home and mentions
timelines.  Maybe other timelines if I find a way to make it work.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hannahwhy hannahwhy

Labels
enhance feature expansion ft-keyword mute
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hannahwhy