-
Notifications
You must be signed in to change notification settings - Fork 56
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
Since command: adding the ability to mute #272
Conversation
Could you also link to all of the issues that have requested or discussed muting in the PR (even if this PR is not addressing all of their concerns)? it'll help us figure out whether we're doing the right thing |
src/commands/SinceCommand.ts
Outdated
text: text_ | ||
|
||
// Store list of affected users, in case we need it later. | ||
/* no need to await */ mjolnir.client.sendStateEvent(targetRoomId, "org.matrix.mjolnir.since.mute", "", results); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if we are reusing joins to unmute users the same way they were muted, do we need the mute/unmute state events anymore? When I suggested this I was thinking unmute would use this state event when removing the power levels too, but that might not make sense now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that we can avoid it for now and add the state event only later, if we realize we need it.
This should help with some attacks.