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

Option to mute AND block #48

Open
sleepachu opened this issue May 1, 2023 · 4 comments
Open

Option to mute AND block #48

sleepachu opened this issue May 1, 2023 · 4 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@sleepachu
Copy link

For a couple reasons it may be preferable to both block AND mute.

  1. Algorithmic reasons: block/mute equivalent and stack, would be nice to bury them twice.
  2. Visibility reasons: Twitter seems to inconsistently hide blocks and mutes on their own, especially if there's a bluecheck reply downthread, but sometimes block-mutes get cleared from thread view with no problem at all, you don't even have to hide blocked replies.
@kheina kheina added the enhancement New feature or request label May 1, 2023
@kheina
Copy link
Collaborator

kheina commented May 1, 2023

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

@cooljeanius
Copy link
Collaborator

For a couple reasons it may be preferable to both block AND mute.

  1. Algorithmic reasons: block/mute equivalent and stack, would be nice to bury them twice.

  2. Visibility reasons: Twitter seems to inconsistently hide blocks and mutes on their own, especially if there's a bluecheck reply downthread, but sometimes block-mutes get cleared from thread view with no problem at all, you don't even have to hide blocked replies.

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

@rougetimelord rougetimelord added this to the 0.5.0 milestone Apr 30, 2024
@rougetimelord
Copy link
Collaborator

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.

@rougetimelord rougetimelord self-assigned this Apr 30, 2024
@cooljeanius
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants