Update quay.io/oauth2-proxy/oauth2-proxy Docker tag to v7.15.4

docs/concepts-and-configurations/matrix-moderation.md

@@ -27,10 +27,9 @@ The bot account `@moderation:hamburg.ccc.de` (Draupnir) maintains various intern
 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.
-The bot is controlled and configured via a privileged *CCCHH Moderation Management* room using `!draupnir` commands.
+The bot is controlled and configured via a privileged *CCCHH Moderation Management* room using `!mjolnir` commands.
 There, individual actions can also be triggered through the bot as needed, such as redacting messages, kicking users from all or some channels, etc.
 
-Currently we operate **two policy lists**: One for internal bans like "Hausverbot" or similar and one for general misconduct like harassment and spam.
-It is possible to make our general list available to other entities as well as subscribe our bot to other entities' lists.
-Our general list is published in `#general-moderation:hamburg.ccc.de` where other moderation bots can freely watch it.
+It is also possible to make our moderation bot's local lists available to other entities and subscribe our bot to other entities' lists.
+Our list is published in `#general-moderation:hamburg.ccc.de` where other moderation bots can freely watch it.
 

docs/guides/matrix-taking-moderation-action.md

@@ -18,20 +18,18 @@ All bot actions are triggered through the *CCCHH Moderation Management* room.
 ## Banning a User
 
 ```
-!draupnir ban user <list> <glob> <reason>
+!draupnir ban user general <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 <list> <glob> <reason>
+!draupnir ban server general <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.

resources/chaosknoten/acmedns/docker_compose/compose.yaml.j2

@@ -2,7 +2,7 @@
 services:
   oauth2-proxy:
     container_name: oauth2-proxy
-    image: quay.io/oauth2-proxy/oauth2-proxy:v7.15.3
+    image: quay.io/oauth2-proxy/oauth2-proxy:v7.15.4
     command: --config /oauth2-proxy.cfg
     hostname: oauth2-proxy
     volumes: