-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Allow minimal ability to mute other users. #8040
Comments
@showell Can I work on this issue? |
@Kumar-Tarun Yep, you can work on it. I would work on the backend pieces first:
You'll want to be comfortable with writing good automated tests for the second bullet. |
Since this is my first backend issue, I'll try my best to figure it out. Thanks @showell. |
@zulipbot claim |
Hello @zulip/server-settings members, this issue was labeled with the area: settings (user) label, so you may want to check it out! |
We are still deciding exactly what we want to do here. See discussion here: |
Hello @Kumar-Tarun, you claimed this issue to work on it, but this issue and any referenced pull requests haven't been updated for 10 days. Are you still working on this issue? If so, please update this issue by leaving a comment on this issue to let me know that you're still working on it. Otherwise, I'll automatically remove you from this issue in 4 days. If you've decided to work on something else, simply comment Thank you for your valuable contributions to Zulip! |
I'm still working on this and will release a PR soon. |
Hello @Kumar-Tarun, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days. You can reclaim this issue or claim any other issue by commenting Thanks for your contributions, and hope to see you again soon! |
any news? |
Any update on this? It's quite disappointing not to have such a basic feature in Zulip still... it's kind of essential for interaction in any sizeable community (sadly). |
@alexreg @FoggyFinder there's significant work that's happened on this in #8318, which is very stale but I think could be adapted without too much trouble. It won't make the 2.1 release, but it's something we'll consider when planning priorities for 2.1. @hackerkid this might be a good upcoming project for you. We should discuss strategy for whether to rebase or replace #8318 before starting work. |
Is the ability for an administrator (or ideally, a "moderator" with limited capabilities?) to globally mute a user (perhaps for some limited period of time) in scope here? Is that worth another issue? |
Not for this, but it could be a follow-up. That said, I would expect many moderators/administrators to just deactivate the accounts of problematic users rather than globally muting them permanently. |
Recently, the feature set for muted user was discussed on
|
@abhijeetbodas2001 Thanks, that all sounds very reasonable. Regarding this future point:
It should probably be a preference setting. |
I've made a design doc to consolidate thoughts on the exact UI/UX that this feature will have. If you have opinions on what this should look like, feel free to comment, either in this issue, on that doc, or in the CZO thread! |
Closing as fixed in 67cd385. |
This is a repeat of #168, which is really old and has some discussion that may have gone a bit off the rails.
We occasionally get requests to be able to mute/block users.
We should try to figure out a very minimal foray into this feature. A simple V1 mute-user mechanism would only suppress unread counts and notifications for incoming PMs, and we wouldn't need to filter message feeds or anything like that, and we wouldn't need to address issue like notifying the other user that they're being muted, which might cause some community friction.
Note that we already have a way to deactivate users, so for situations where users aren't abiding by codes of conduct, there are already ways to deal with them.
The basic implementation for a V1 feature is this:
MutedUser
model with fieldsuser
andmuted_user
muted_user
in a relevantMutedUser
rowThe text was updated successfully, but these errors were encountered: