migrate mjolnir to draupnir
All checks were successful
/ build (pull_request) Successful in 50s
/ Ansible Lint (pull_request) Successful in 2m53s
/ cleanup-staging (pull_request) Successful in 37s
/ build (push) Successful in 56s
/ Ansible Lint (push) Successful in 3m8s

This commit is contained in:
lilly 2026-09-06 14:40:42 +02:00
commit f7c3e2146d
Signed by: lilly
SSH key fingerprint: SHA256:y9T5GFw2A20WVklhetIxG1+kcg/Ce0shnQmbu1LQ37g
12 changed files with 60 additions and 59 deletions

View file

@ -23,7 +23,7 @@ During moderation, we adhere to the following principles:
## How It Works
The bot account `@moderation:hamburg.ccc.de` (Mjolnir) maintains various internal lists of rules that are applied in so-called "Protected Rooms".
The bot account `@moderation:hamburg.ccc.de` (Draupnir) maintains various internal lists of rules that are applied in so-called "Protected Rooms".
These can include, for example, user bans or entire server bans.
Additionally, certain automatic monitoring measures (so-called "protections") apply in these rooms, which trigger a configured action if violated.
For example, a user is not allowed to tag too many other users in a single message, as this is considered spam and results in a kick.

View file

@ -40,14 +40,14 @@ We have now added the moderation bot to the room but this is not enough.
The bot needs to be told explicitly which rooms it should protect and the newly created one therefore needs to be added to that list.
First, note down the *Internal Room ID* which can be found in the new Rooms settings under the *Advanced* tab.
Then enter the *CCCHH Moderation Management* room and write the follogin mjolnir command while substituting the copied room id:
Then enter the *CCCHH Moderation Management* room and write the following draupnir command while substituting the copied room id:
```
!mjolnir rooms add <room-id>
!draupnir rooms add <room-id>
```
## Closing Up
You should now have a new Matrix Room under moderation protection.
To verify that everything was done correctly, you can enter `!mjolnir verify` in the *CCCHH Moderation Management* room and observe that the moderation bot does not give you an error.
To verify that everything was done correctly, you can enter `!draupnir verify` in the *CCCHH Moderation Management* room and observe that the moderation bot does not give you an error.

View file

@ -18,7 +18,7 @@ All bot actions are triggered through the *CCCHH Moderation Management* room.
## Banning a User
```
!mjolnir ban general user <glob> <reason>
!draupnir ban general user <glob> <reason>
```
- `<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.
@ -27,7 +27,7 @@ All bot actions are triggered through the *CCCHH Moderation Management* room.
## Banning a Server
```
!mjolnir ban server <glob> <reason>
!draupnir ban server <glob> <reason>
```
- `<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.
@ -37,7 +37,7 @@ All bot actions are triggered through the *CCCHH Moderation Management* room.
## Redacting a single Message
```
!mjolnir redact <permalink>
!draupnir redact <permalink>
```
- `<permalink>` is **not** the message ID but the actual *https://matrix.to/#blablabla* link that can be retrieved with most clients through a *Share* or *Copy link to Message* button on an individual message.
@ -45,7 +45,7 @@ All bot actions are triggered through the *CCCHH Moderation Management* room.
## Redacting all Messages of a User
```
!mjolnir redact <user-id>
!draupnir redact <user-id>
```
- `user-id` the Matrix-ID of the user of whom all messages in all rooms should be redacted (e.g. `@bla:example.com`).