-
Notifications
You must be signed in to change notification settings - Fork 52
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
Raid protection #267
Comments
We have recently landed a command We should probably expand this to
This could be implemented as a new customizable protection, I suppose. If too many users join one after the other, mute them by default and inform the moderator, I guess? |
Exactly, with maybe some quick buttons/actions to approve them en-masse, or some manual actions to pick out who to unmute specifically, and kick the rest. |
For the time being, I'm adding support for |
Thanks, i'll add it to my todo 👍 |
Given the urgency of the current spam waves on matrix, i'll work on a "quicker" version of this, a protection module that will - very simply - put the room on invite-only if it detects 100 users joining within an hour. It can be abused (by triggering it explicitly by joining with that many users), and it can have false positives (i.e. a mass join event), but it could work as a backstop while a better solution is created. |
Is your feature request related to a problem? Please describe.
We just had a room get "invaded" by a bunch of users all at once, around 60 of them joining with no clear purpose, just all one-after-another.
Describe the solution you'd like
Be able to detect and automatically apply kick/mute on these users, or have commands to easily apply actions for users "joined in the last Y timespan".
Additional context
I remember in the early days where Discord had this, where it detected if 4 or more users joined after eachother in 15 minutes, and they had to be manually cleared by moderation.
The server this was on had infrequent joins, and was often plagued by abusive people (who'd mock people on the server), so this contingency measure was put in place to lessen the effectiveness of "dumb" raids (as opposed to "smart" raids, where people trickle in in a long timespan, though still saying nothing until they all spammed the general chat)
The text was updated successfully, but these errors were encountered: