-
Notifications
You must be signed in to change notification settings - Fork 28
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
Option to mute AND block #48
Comments
This is totally possible, but probably not going to be implemented just because of how much of a pain in the ass it is to avoid twitter rate limiting nowadays. adding in the interval slider from #40 will help a lot, but they seem to log you out at the drop of a hat |
Additional reason: Twitter may soon be removing blocking functionality, so it would be good to also layer a mute on top of your blocks to ensure they don't resurface again as soon as blocking gets disabled |
Linking this with #166. My suggestion would be to remove the "mute users instead of blocking them" and "pause user collection" options, and move to having an individual checkbox for muting and blocking, in a way that allows both to be performed. We should also change how blocked/muted accounts are stored in history so that they can be marked as being blocked, muted, or both. |
Make sure there's a clean migration path. Like, if someone currently has the "mute users instead of blocking them" option set, then that should still be reflected after the changeover to the new option setup. |
For a couple reasons it may be preferable to both block AND mute.
The text was updated successfully, but these errors were encountered: