update matrix moderation docs to reflect that we now have two ban lists
All checks were successful
/ build (push) Successful in 51s
/ Ansible Lint (push) Successful in 4m38s

This commit is contained in:
lilly 2026-09-18 17:45:46 +02:00
commit ee810bfc16
Signed by: lilly
SSH key fingerprint: SHA256:y9T5GFw2A20WVklhetIxG1+kcg/Ce0shnQmbu1LQ37g
2 changed files with 8 additions and 5 deletions

View file

@ -18,18 +18,20 @@ All bot actions are triggered through the *CCCHH Moderation Management* room.
## Banning a User
```
!draupnir ban user general <glob> <reason>
!draupnir ban user <list> <glob> <reason>
```
- `<list>` either `general` for general misconduct or `internal` for CCCHH-internal reasons
- `<glob>` can be a user ID (e.g. `@example:matrix.org`) but also more sophisticated. Be careful when using actual glob syntax as whole servers can be banned even if just a single user is the intended target.
- `<reason>` is technically optional but should always be supplied so that we know why a certain user was banned in retrospect. The bot supports parsing quotations so `"<reason>"` is usually what you want if more than one word is used.
## Banning a Server
```
!draupnir ban server general <glob> <reason>
!draupnir ban server <list> <glob> <reason>
```
- `<list>` either `general` for general misconduct or `internal` for CCCHH-internal reasons
- `<glob>` can be used to ban subdomains of a domain too, e.g. `*.example.com`. If used, an additional `--force` is required after the whole command.
- `<reason>` should be supplied and supports quotation (`"<reason>") if more than one word is used
- When a domain is banned, we usually also ban all subdomains too. This needs to be done in two separate commands.