Automatic translations update (#5206)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
1 день назад · 2d5b5ff7ef
--- a/i18n/translation-templates/docs/configuring-playbook-appservice-draupnir-for-all.pot
+++ b/i18n/translation-templates/docs/configuring-playbook-appservice-draupnir-for-all.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2026-05-07 11:16+0000\n"
 "POT-Creation-Date: 2026-05-07 14:00+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -16,179 +16,215 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:8
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:9
 msgid "Setting up Draupnir for All/D4A (optional)"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:10
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:11
 msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation tool for you in appservice mode."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:12
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:13
 msgid "Appservice mode can be used together with the regular [Draupnir bot](configuring-playbook-bot-draupnir.md) or independently. Details about the differences between the 2 modes are described below."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:14
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:15
 msgid "Draupnir Appservice mode compared to Draupnir bot mode"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:16
 msgid "The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode except in the case of avatar customisation as described later on in this document."
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:17
 msgid "The administrative functions for managing the appservice are alpha quality and very limited. However, the experience of using an appservice-provisioned Draupnir is on par with the experience of using Draupnir from bot mode."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:18
 msgid "Draupnir for all is the way to go if you need more than 1 Draupnir instance, but you don't need access to Synapse Admin features as they are not accessible through Draupnir for All (Even though the commands do show up in help)."
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:19
 msgid "Draupnir for all is the way to go if you need more than 1 Draupnir instance, but you don't need access to Synapse Admin features as they are not accessible through Draupnir for All."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:20
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:21
 msgid "Draupnir for all in the playbook is rate-limit-exempt automatically as its appservice configuration file does not specify any rate limits."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:22
 msgid "Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as D4A even on the branch with the Avatar command (To be Upstreamed to Mainline Draupnir) that command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this is a quick operation where you login to Draupnir with a normal client and set Avatar and Display name normally."
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23
 msgid "Normal Draupnir does come with the benefit of access to Synapse Admin features. You are also able to more easily customise your normal Draupnir than D4A as the avatar command is clunky as it requires the use of things like Element Web devtools. In normal Draupnir this can be done while logged in to the Draupnir account with a normal client and set Avatar and Display name normally."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:24
 msgid "Draupnir for all does not support external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account."
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:25
 msgid "Draupnir for all only has limited support for external tooling like [MRU](https://mru.rory.gay) as it can't access Draupnir's user account."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:26
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:27
 msgid "Prerequisites"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:28
 msgid "Create a main management room"
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29
 msgid "Prerequisites for Zero Touch Deployment (recommended)"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:30
 msgid "The playbook does not create a management room for your Main Draupnir. You **need to create the room manually** before setting up the bot."
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:31
 msgid "As of Draupnir 3.1.0, Zero Touch Deployment of Draupnir Appservice Mode (Draupnir for all) requires you to supply the following:"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:32
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:33
 msgid "MXID of the first person who gets invited to the admin room that the bot creates for you."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:35
 msgid "That is all. The appservice manages everything on its own after you provide it with an MXID to invite."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:37
 msgid "If proceeding with Zero Touch Deployment, skip ahead to [Adjusting the playbook configuration](#adjusting-the-playbook-configuration)."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:39
 msgid "Create an admin room (optional)"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:41
 msgid "The playbook does not create an admin room for your Draupnir, but the appservice itself can do this for you. Alternatively, you **can create the room manually** before setting up the bot."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:43
 msgid "Note that the room must be unencrypted."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:34
 msgid "The management room has to be given an alias, and your bot has to be invited to the room."
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:45
 msgid "The admin room has to be given an alias, and your bot has to be invited to the room."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:36
 msgid "This management room is used to control who has access to your D4A deployment. The room stores this data inside of the control room state so your bot must have sufficient powerlevel to send custom state events. This is default 50 or moderator as Element clients call this powerlevel."
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:47
 msgid "This admin room is used to control who has access to your D4A deployment. The room stores this data in the control room state, so your bot must have sufficient power level to send custom state events. This is `50` by default (moderator, as Element clients call this power level)."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:38
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:49
 msgid "[!WARNING] Anyone in this room can control the bot so it is important that you only invite trusted users to this room."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:41
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:52
 msgid "Adjusting the playbook configuration"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:43
 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE`."
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:54
 msgid "When using Zero Touch Deployment, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `INITIAL_MANAGER_MXID_HERE` with the MXID of the user who should be invited to the admin room first."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:64
 msgid "If opting out of Zero Touch Deployment, use the following configuration block instead. Make sure to replace `MANAGEMENT_ROOM_ALIAS_HERE` with the alias of the admin room you have created earlier."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:51
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:72
 msgid "Running both bot mode and appservice mode"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:53
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:74
 msgid "When running both [bot mode](./configuring-playbook-bot-draupnir.md) and appservice mode, the playbook will force-restart the bot if running a non-release tag like `latest` or `main` or a development build. This is due to the conditional restart logic not being able to reliably tell when an update happened."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:57
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:78
 msgid "Conditional restarts work correctly for all tags when running only one of these two operating modes."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:59
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:80
 msgid "Extending the configuration"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:61
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:82
 msgid "There are some additional things you may wish to configure about the component."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:63
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:84
 msgid "Take a look at:"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:65
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:86
 msgid "`roles/custom/matrix-appservice-draupnir-for-all/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_draupnir_for_all_configuration_extension_yaml` variable"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:67
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:88
 msgid "For example, to change Draupnir's `protectAllJoinedRooms` option to `true`, add the following configuration to your `vars.yml` file:"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:81
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102
 msgid "You can refer to the upstream [documentation](https://github.com/the-draupnir-project/Draupnir) for more configuration documentation."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:83
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:98
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:119
 msgid "**Notes**:"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:85
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106
 msgid "The playbook ships a full copy of the example config that does transfer to provisioned Draupnirs in the production-bots.yaml.j2 file in the template directory of the role."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:87
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:108
 msgid "Config extension does not affect the appservices config as this config is not extensible in current Draupnir anyway. It instead touches the config passed to the Draupnirs that your Appservice creates. So the example above (`protectAllJoinedRooms: true`) makes all provisioned Draupnirs protect all joined rooms."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:89
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110
 msgid "Installing"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:91
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:100
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:121
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:123
 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:125
 msgid "Usage"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106
 msgid "If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com` you have successfully installed Draupnir for All and can now start using it."
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:127
 msgid "If you made it through all the steps above and your main control room was joined by a user called `@draupnir-main:example.com`, you have successfully installed Draupnir for All and can now start using it."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:108
 msgid "The installation of Draupnir for all in this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode."
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:129
 msgid "If using Zero Touch Deployment, the flow is reversed and the success signal is the initial manager account being invited to the admin room."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:131
 msgid "Draupnir for all installation via this playbook is very much Alpha quality. Usage-wise, Draupnir for all is almost identical to Draupnir bot mode, except that protections requiring homeserver admin access are not available, and the config file is shared between all bots so legacy protections like wordlist share a single global config."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:133
 msgid "Granting Users the ability to use D4A"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:135
 msgid "Draupnir for all includes several security measures like that it only allows users that are on its allow list to ask for a bot. To add a user to this list we have 2 primary options. Using the chat to tell Draupnir to do this for us or if you want to automatically do it by sending `m.policy.rule.user` events that target the subject you want to allow provisioning for with the `org.matrix.mjolnir.allow` recommendation. Using the chat is recommended."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:114
 msgid "The bot requires a powerlevel of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297))"
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:137
 msgid "The bot requires a power level of 50 in the management room to control who is allowed to use the bot. The bot does currently not say anything if this is true or false. (This is considered a bug and is documented in issue [#297](https://github.com/the-draupnir-project/Draupnir/issues/297).) This issue is largely mitigated by the Zero Touch Deployment workflows introduced in Draupnir 3.1.0."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:116
 msgid "To allow users or whole homeservers you type /plain !admin allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to register. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially."
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:139
 msgid "To allow users or whole homeservers you type /plain !admin allow `target` and target can be either a MXID or a wildcard like `@*:example.com` to allow all users on example.com to provision a bot. We use /plain to force the client to not attempt to mess with this command as it can break Wildcard commands especially."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:118
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:141
 msgid "How to provision a D4A once you are allowed to"
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:120
 msgid "To provision a D4A, you need to start a chat with `@draupnir-main:example.com`. The bot will reject this invite and you will shortly get invited to the Draupnir control room for your newly provisioned Draupnir. From here its just a normal Draupnir experience."
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:143
 msgid "Once someone is allowed to provision a bot, simply provision them one with `!admin provision MXID`."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:145
 msgid "Self-service provisioning is disabled as a security measure because it is currently bugged. Force-provisioning (with `!admin provision`) bypasses this disabled status."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:147
 msgid "Note that you should always make sure there is an allow entry matching whoever is provisioned, because once self-service is fixed, the bot of anyone who is not allowed to provision a bot will refuse to start."
 msgstr ""

 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:122
 msgid "Congratulations if you made it all the way here because you now have a fully working Draupnir for all deployment."
 #: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:149
 msgid "Congratulations if you made it all the way here, because you now have a fully working Draupnir for all deployment."
 msgstr ""
--- a/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot
+++ b/i18n/translation-templates/docs/configuring-playbook-bot-draupnir.pot
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2026-05-07 11:16+0000\n"
 "POT-Creation-Date: 2026-05-07 14:00+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -16,431 +16,487 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"

 #: ../../../docs/configuring-playbook-bot-draupnir.md:10
 #: ../../../docs/configuring-playbook-bot-draupnir.md:11
 msgid "Setting up Draupnir (optional)"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:12
 #: ../../../docs/configuring-playbook-bot-draupnir.md:13
 msgid "The playbook can install and configure the [Draupnir](https://github.com/the-draupnir-project/Draupnir) moderation bot for you."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:14
 #: ../../../docs/configuring-playbook-bot-draupnir.md:15
 msgid "See the project's [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) to learn what it does and why it might be useful to you."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:16
 #: ../../../docs/configuring-playbook-bot-draupnir.md:17
 msgid "This documentation page is about installing Draupnir in bot mode. As an alternative, you can run a multi-instance Draupnir deployment by installing [Draupnir in appservice mode](./configuring-playbook-appservice-draupnir-for-all.md) (called Draupnir-for-all) instead."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:18
 #: ../../../docs/configuring-playbook-bot-draupnir.md:19
 msgid "If your migrating from [Mjolnir](configuring-playbook-bot-mjolnir.md), skip to [this section](#migrating-from-mjolnir-only-required-if-migrating)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:20
 #: ../../../docs/configuring-playbook-bot-draupnir.md:21
 msgid "Prerequisites"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:22
 msgid "Create a management room"
 #: ../../../docs/configuring-playbook-bot-draupnir.md:23
 msgid "Prerequisites for Zero Touch Deployment (recommended)"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:24
 #: ../../../docs/configuring-playbook-bot-draupnir.md:25
 msgid "As of Draupnir 3.1.0, Zero Touch Deployment of Draupnir bot mode requires you to supply the following:"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:27
 msgid "MXID of the first person who gets invited to the management room that the bot creates for you."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:28
 msgid "A permanent access token for authentication. Instructions for obtaining one can be found at [obtain an access token via curl](obtaining-access-tokens.md#obtain-an-access-token-via-curl)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:29
 msgid "A user account for Draupnir."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:31
 msgid "Zero Touch Deployment is the officially preferred installation method for new deployments of Draupnir as of 3.1.0."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:33
 msgid "Create a management room (optional)"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:35
 msgid "Using your own account, create a new invite only room that you will use to manage the bot. This is the room where you will see the status of the bot and where you will send commands to the bot, such as the command to ban a user from another room."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:26
 #: ../../../docs/configuring-playbook-bot-draupnir.md:37
 msgid "[!WARNING] Anyone in this room can control the bot so it is important that you only invite trusted users to this room."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:29
 #: ../../../docs/configuring-playbook-bot-draupnir.md:40
 msgid "It is possible to make the management room encrypted (E2EE). If doing so, then you need to enable the native E2EE support (see [below](#native-e2ee-support))."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:31
 #: ../../../docs/configuring-playbook-bot-draupnir.md:42
 msgid "E2EE support for the management room is mutually exclusive with Zero Touch Deployment of Draupnir."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:44
 msgid "Once you have created the room you need to copy the room ID so you can specify it on your `inventory/host_vars/matrix.example.com/vars.yml` file. In Element Web you can check the ID by going to the room's settings and clicking \"Advanced\". The room ID will look something like `!qporfwt:example.com`."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:33
 #: ../../../docs/configuring-playbook-bot-draupnir.md:46
 msgid "End-to-End Encryption support"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:35
 #: ../../../docs/configuring-playbook-bot-draupnir.md:48
 msgid "Decide whether you want to support having an encrypted management room or not. Draupnir can still protect encrypted rooms without encryption support enabled."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:37
 #: ../../../docs/configuring-playbook-bot-draupnir.md:50
 msgid "Refer to Draupnir's [documentation](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#protecting-encrypted-rooms) for more details about why you might want to care about encryption support for protected rooms."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:39
 #: ../../../docs/configuring-playbook-bot-draupnir.md:52
 msgid "Disable Pantalaimon for Draupnir (since v2.0.0; optional)"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:41
 #: ../../../docs/configuring-playbook-bot-draupnir.md:54
 msgid "It is known that running Draupnir along with Pantalaimon breaks all workflows that involve answering prompts with reactions."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:43
 #: ../../../docs/configuring-playbook-bot-draupnir.md:56
 msgid "If you are updating Draupnir from v1.x.x and have enabled Pantalaimon for it, you can disable Pantalaimon in favor of the native E2EE support. To disable Pantalaimon, remove the configuration `matrix_bot_draupnir_pantalaimon_use: true` from your `vars.yml` file."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:45
 #: ../../../docs/configuring-playbook-bot-draupnir.md:58
 msgid "**Note**: because the management room is still encrypted, disabling it without enabling the native E2EE support will break the management room."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:47
 #: ../../../docs/configuring-playbook-bot-draupnir.md:60
 msgid "Native E2EE support"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:49
 #: ../../../docs/configuring-playbook-bot-draupnir.md:62
 msgid "To enable the native E2EE support, you need to obtain an access token for Draupnir and set it on your `vars.yml` file."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:51
 #: ../../../docs/configuring-playbook-bot-draupnir.md:64
 msgid "Note that native E2EE requires a clean access token that has not touched E2EE so curl is recommended as a method to obtain it. **The access token obtained via Element Web does not work with it**. Refer to the documentation on [how to obtain an access token via curl](obtaining-access-tokens.md#obtain-an-access-token-via-curl)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:53
 #: ../../../docs/configuring-playbook-bot-draupnir.md:66
 msgid "To enable the native E2EE support, add the following configuration to your `vars.yml` file. Make sure to replace `CLEAN_ACCESS_TOKEN_HERE` with the access token you obtained just now."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:64
 #: ../../../docs/configuring-playbook-bot-draupnir.md:77
 msgid "Adjusting the playbook configuration"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:66
 msgid "To enable the bot, add the following configuration to your `vars.yml` file. Make sure to replace `MANAGEMENT_ROOM_ID_HERE` with the one of the room which you have created earlier."
 #: ../../../docs/configuring-playbook-bot-draupnir.md:79
 msgid "Configuration for Zero Touch Deployment (recommended)"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:85
 #: ../../../docs/configuring-playbook-bot-draupnir.md:81
 msgid "To enable the bot using Zero Touch Deployment, add the following configuration to your `vars.yml` file. Make sure to replace `INITIAL_MANAGER_MXID_HERE` with the MXID of the user who should be invited to the management room first, and `CLEAN_ACCESS_TOKEN_HERE` with the access token you obtained."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:95
 msgid "Configuration without Zero Touch Deployment"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:97
 msgid "If you'd prefer to have the bot manage its own login at the cost of having to create the management room manually, you can use native login with the configuration block below. Make sure to replace `MANAGEMENT_ROOM_ID_HERE` with the ID of the management room you have created earlier."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:116
 msgid "Running both bot mode and appservice mode"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:87
 #: ../../../docs/configuring-playbook-bot-draupnir.md:118
 msgid "When running both bot mode and [appservice mode (Draupnir for all)](./configuring-playbook-appservice-draupnir-for-all.md), the playbook will force-restart the bot if running a non-release tag like `latest` or `main` or a development build. This is due to the conditional restart logic not being able to reliably tell when an update happened."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:91
 #: ../../../docs/configuring-playbook-bot-draupnir.md:122
 msgid "Conditional restarts work correctly for all tags when running only one of these two operating modes."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:93
 msgid "Create and invite the bot to the management room"
 #: ../../../docs/configuring-playbook-bot-draupnir.md:124
 msgid "Create and invite the bot to the management room (only when using native login without Zero Touch Deployment)"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:95
 #: ../../../docs/configuring-playbook-bot-draupnir.md:126
 msgid "Before proceeding to the next step, run the playbook with the following command to create the bot user."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:101
 #: ../../../docs/configuring-playbook-bot-draupnir.md:132
 msgid "**Note**: the `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:103
 #: ../../../docs/configuring-playbook-bot-draupnir.md:134
 msgid "Then, invite the bot (`@bot.draupnir:example.com`) to its management room which you have created earlier."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:105
 #: ../../../docs/configuring-playbook-bot-draupnir.md:136
 msgid "Creating a user account for the bot (when using Zero Touch Deployment)"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:138
 msgid "Since Zero Touch Deployment is not validated with native login, you will need to create the user account manually."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:140
 msgid "Refer to [registering users](registering-users.md) for documentation on how to configure the user account."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:142
 msgid "Make sure the account is free from rate limiting (optional, recommended)"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:107
 #: ../../../docs/configuring-playbook-bot-draupnir.md:144
 msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a highly recommended step. If you do not configure it, Draupnir performance will be degraded.**"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:109
 #: ../../../docs/configuring-playbook-bot-draupnir.md:146
 msgid "This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/admin_api/user_admin_api.html#override-ratelimiting-for-users). They can be accessed both externally and internally."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:111
 #: ../../../docs/configuring-playbook-bot-draupnir.md:148
 msgid "**Note**: access to the APIs is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, doing so is not recommended for additional security. See [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:113
 #: ../../../docs/configuring-playbook-bot-draupnir.md:150
 msgid "The APIs can also be accessed via [Ketesa](https://github.com/etkecc/ketesa), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Ketesa for you. For details about it, see [this page](configuring-playbook-ketesa.md)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:115
 #: ../../../docs/configuring-playbook-bot-draupnir.md:152
 msgid "Add the configuration"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:117
 msgid "To expose the APIs publicly, add the following configuration to your `vars.yml` file:"
 #: ../../../docs/configuring-playbook-bot-draupnir.md:154
 msgid "This is automatically done if Ketesa is enabled. Otherwise, to expose the APIs publicly, add the following configuration to your `vars.yml` file:"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:123
 #: ../../../docs/configuring-playbook-bot-draupnir.md:160
 msgid "Obtain an access token for admin account"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:125
 #: ../../../docs/configuring-playbook-bot-draupnir.md:162
 msgid "Manual access to Synapse's Admin APIs requires an access token for a homeserver admin account. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:127
 #: ../../../docs/configuring-playbook-bot-draupnir.md:164
 msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:130
 #: ../../../docs/configuring-playbook-bot-draupnir.md:167
 msgid "Run the `curl` command"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:132
 #: ../../../docs/configuring-playbook-bot-draupnir.md:169
 msgid "To disable rate limiting, run the following command on systems that ship curl. Before running it, make sure to replace:"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:134
 #: ../../../docs/configuring-playbook-bot-draupnir.md:171
 msgid "`ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:135
 #: ../../../docs/configuring-playbook-bot-draupnir.md:172
 msgid "`example.com` with your base domain"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:136
 #: ../../../docs/configuring-playbook-bot-draupnir.md:173
 msgid "`@bot.draupnir:example.com` with the MXID of your Draupnir bot user"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:142
 #: ../../../docs/configuring-playbook-bot-draupnir.md:215
 #: ../../../docs/configuring-playbook-bot-draupnir.md:179
 #: ../../../docs/configuring-playbook-bot-draupnir.md:254
 msgid "**Notes**:"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:143
 #: ../../../docs/configuring-playbook-bot-draupnir.md:181
 msgid "This does not work on outdated Windows 10 as curl is not available there."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:144
 #: ../../../docs/configuring-playbook-bot-draupnir.md:182
 msgid "Even if the APIs are not exposed to the internet, you should still be able to run the command on the homeserver locally."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:146
 #: ../../../docs/configuring-playbook-bot-draupnir.md:184
 msgid "Abuse Reports"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:148
 #: ../../../docs/configuring-playbook-bot-draupnir.md:186
 msgid "Draupnir can receive reports in the management room."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:150
 #: ../../../docs/configuring-playbook-bot-draupnir.md:188
 msgid "The bot can intercept the report API endpoint of the client-server API, which requires integration with the reverse proxy in front of the homeserver. If you are using Traefik, this playbook can set this up for you:"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:156
 #: ../../../docs/configuring-playbook-bot-draupnir.md:194
 msgid "Enabling synapse-http-antispam support"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:158
 #: ../../../docs/configuring-playbook-bot-draupnir.md:196
 msgid "Certain protections in Draupnir require the [synapse-http-antispam](https://github.com/maunium/synapse-http-antispam) module and a Synapse homeserver plus homeserver admin status to function. This module can be enabled in the playbook via setting `matrix_bot_draupnir_config_web_synapseHTTPAntispam_enabled` to `true` and making sure that Draupnir admin API access is enabled."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:168
 msgid "These protections need to be manually activated and consulting the [enabling protections](#enabling-built-in-protections) guide can be helpful or consulting upstream documentation."
 #: ../../../docs/configuring-playbook-bot-draupnir.md:206
 msgid "These protections need to be manually activated. Consulting the [enabling protections](#enabling-built-in-protections) guide and/or upstream documentation can be helpful."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:208
 msgid "The other method polls a Synapse Admin API endpoint, hence it is available only if using Synapse and if the Draupnir user is an admin. To enable it, set `pollReports: true` in your `vars.yml` file as below:"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:176
 #: ../../../docs/configuring-playbook-bot-draupnir.md:215
 msgid "Extending the configuration"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:178
 #: ../../../docs/configuring-playbook-bot-draupnir.md:217
 msgid "There are some additional things you may wish to configure about the bot."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:180
 #: ../../../docs/configuring-playbook-bot-draupnir.md:219
 msgid "Take a look at:"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:182
 #: ../../../docs/configuring-playbook-bot-draupnir.md:221
 msgid "`roles/custom/matrix-bot-draupnir/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bot_draupnir_configuration_extension_yaml` variable"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:184
 #: ../../../docs/configuring-playbook-bot-draupnir.md:223
 msgid "For example, to change Draupnir's `acceptInvitesFromSpace` option to `!qporfwt:example.com`, add the following configuration to your `vars.yml` file:"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:198
 #: ../../../docs/configuring-playbook-bot-draupnir.md:237
 msgid "Migrating from Mjolnir (Only required if migrating)"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:200
 #: ../../../docs/configuring-playbook-bot-draupnir.md:239
 msgid "Replace your `matrix_bot_mjolnir` config with `matrix_bot_draupnir` config. Also disable Mjolnir if you're doing migration."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:202
 #: ../../../docs/configuring-playbook-bot-draupnir.md:241
 msgid "Note that Draupnir supports E2EE natively, so you can enable it instead of Pantalaimon. It is recommended to consult the instruction [here](#native-e2ee-support)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:204
 #: ../../../docs/configuring-playbook-bot-draupnir.md:243
 msgid "That is all you need to do due to that Draupnir can complete migration on its own."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:206
 #: ../../../docs/configuring-playbook-bot-draupnir.md:245
 msgid "Installing"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:208
 #: ../../../docs/configuring-playbook-bot-draupnir.md:247
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:217
 #: ../../../docs/configuring-playbook-bot-draupnir.md:256
 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:219
 #: ../../../docs/configuring-playbook-bot-draupnir.md:258
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:221
 #: ../../../docs/configuring-playbook-bot-draupnir.md:260
 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:223
 #: ../../../docs/configuring-playbook-bot-draupnir.md:262
 msgid "If you change the bot password (`matrix_bot_draupnir_password` in your `vars.yml` file) subsequently, the bot user's credentials on the homeserver won't be updated automatically. If you'd like to change the bot user's password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_draupnir_password` to let the bot know its new password."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:225
 #: ../../../docs/configuring-playbook-bot-draupnir.md:264
 msgid "Usage"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:227
 #: ../../../docs/configuring-playbook-bot-draupnir.md:266
 msgid "You can refer to the upstream [documentation](https://the-draupnir-project.github.io/draupnir-documentation/) for additional ways to use and configure Draupnir and for a more detailed usage guide."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:229
 #: ../../../docs/configuring-playbook-bot-draupnir.md:268
 msgid "Below is a **non-exhaustive quick-start guide** for the impatient."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:231
 #: ../../../docs/configuring-playbook-bot-draupnir.md:270
 msgid "Making Draupnir join and protect a room"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:233
 #: ../../../docs/configuring-playbook-bot-draupnir.md:272
 msgid "Draupnir can be told to self-join public rooms, but it's better to follow this flow which works well for all kinds of rooms:"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:235
 #: ../../../docs/configuring-playbook-bot-draupnir.md:274
 msgid "Invite the bot to the room manually ([inviting Draupnir to rooms](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#inviting-draupnir-to-rooms)). Before joining, the bot *may* ask for confirmation in the Management Room"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:237
 #: ../../../docs/configuring-playbook-bot-draupnir.md:276
 msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:239
 #: ../../../docs/configuring-playbook-bot-draupnir.md:278
 msgid "Tell it to protect the room (using the [rooms command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#using-the-draupnir-rooms-command)) by sending the following command to the Management Room: `!draupnir rooms add !qporfwt:example.com`"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:241
 #: ../../../docs/configuring-playbook-bot-draupnir.md:280
 msgid "To have Draupnir provide useful room protection, you need do to a bit more work (at least the first time around). You may wish to [Subscribe to a public policy list](#subscribing-to-a-public-policy-list), [Create your own own policy and rules](#creating-your-own-policy-lists-and-rules) and [Enabling built-in protections](#enabling-built-in-protections)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:243
 #: ../../../docs/configuring-playbook-bot-draupnir.md:282
 msgid "Giving Draupnir permissions to do its job"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:245
 #: ../../../docs/configuring-playbook-bot-draupnir.md:284
 msgid "For Draupnir to do its job, you need to [give it permissions](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-protected-rooms#giving-draupnir-permissions) in rooms it's protecting. This involves **giving it an Administrator power level**."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:247
 #: ../../../docs/configuring-playbook-bot-draupnir.md:286
 msgid "**We recommend setting this power level as soon as the bot joins your room** (and before you create new rules), so that it can apply rules as soon as they are available. If the bot is under-privileged, it may fail to apply protections and may not retry for a while (or until your restart it)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:249
 #: ../../../docs/configuring-playbook-bot-draupnir.md:288
 msgid "Subscribing to a public policy list"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:251
 #: ../../../docs/configuring-playbook-bot-draupnir.md:290
 msgid "We recommend **subscribing to a public [policy list](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists)** using the [watch command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-watch-command-to-subscribe-to-policy-rooms)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:253
 #: ../../../docs/configuring-playbook-bot-draupnir.md:292
 msgid "Policy lists are maintained in Matrix rooms. Popular ones maintained in the public are:"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:255
 #: ../../../docs/configuring-playbook-bot-draupnir.md:294
 msgid "`#community-moderation-effort-bl:neko.dev`"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:256
 #: ../../../docs/configuring-playbook-bot-draupnir.md:295
 msgid "`#huginn-muninn-active-threats:feline.support`"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:258
 #: ../../../docs/configuring-playbook-bot-draupnir.md:297
 msgid "You can tell Draupnir to subscribe to each of these by sending the following command to the Management Room: `!draupnir watch POLICY_LIST_ADDRESS_HERE` (e.g. `!draupnir watch #community-moderation-effort-bl:neko.dev`)"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:260
 #: ../../../docs/configuring-playbook-bot-draupnir.md:299
 msgid "Creating your own policy lists and rules"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:262
 #: ../../../docs/configuring-playbook-bot-draupnir.md:301
 msgid "We also recommend **creating your own policy lists** with the [list create](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-policy-lists#using-draupnirs-list-create-command-to-create-a-policy-room) command."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:264
 #: ../../../docs/configuring-playbook-bot-draupnir.md:303
 msgid "You can do so by sending the following command to the Management Room: `!draupnir list create my-bans my-bans-bl`. This will create a policy list having a name (shortcode) of `my-bans` and stored in a public `#my-bans-bl:example.com` room on your server. As soon as you run this command, the bot will invite you to the policy list room."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:266
 #: ../../../docs/configuring-playbook-bot-draupnir.md:305
 msgid "A policy list does nothing by itself, so the next step is **adding some rules to your policy list**. Policies target a so-called `entity` (one of: `user`, `room` or `server`). These entities are mentioned on the [policy lists](https://the-draupnir-project.github.io/draupnir-documentation/concepts/policy-lists) documentation page and in the Matrix Spec [here](https://spec.matrix.org/v1.11/client-server-api/#mban-recommendation)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:268
 #: ../../../docs/configuring-playbook-bot-draupnir.md:307
 msgid "The simplest and most useful entity to target is `user`. Below are a few examples using the [ban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-ban-command) and targeting users."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:270
 #: ../../../docs/configuring-playbook-bot-draupnir.md:309
 msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:272
 #: ../../../docs/configuring-playbook-bot-draupnir.md:311
 msgid "(ban a single user on a given homeserver): `!draupnir ban @charles:example.com my-bans Rude to others`"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:273
 #: ../../../docs/configuring-playbook-bot-draupnir.md:312
 msgid "(ban all users on a given homeserver by using a [wildcard](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#wildcards)): `!draupnir ban @*:example.org my-bans Spam server, all users are fake`"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:275
 #: ../../../docs/configuring-playbook-bot-draupnir.md:314
 msgid "As a result of running these commands, you may observe:"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:277
 #: ../../../docs/configuring-playbook-bot-draupnir.md:316
 msgid "Draupnir creating `m.policy.rule.user` state events in the `#my-bans-bl:example.com` room on your server"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:278
 #: ../../../docs/configuring-playbook-bot-draupnir.md:317
 msgid "applying these rules against all rooms that Draupnir is an Administrator in"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:280
 #: ../../../docs/configuring-playbook-bot-draupnir.md:319
 msgid "You can undo bans with the [unban command](https://the-draupnir-project.github.io/draupnir-documentation/moderator/managing-users#the-unban-command)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:282
 #: ../../../docs/configuring-playbook-bot-draupnir.md:321
 msgid "Enabling built-in protections"
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:284
 #: ../../../docs/configuring-playbook-bot-draupnir.md:323
 msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuitProtection` (\"If X amount of users join in Y time, set the room to invite-only\")."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:286
 #: ../../../docs/configuring-playbook-bot-draupnir.md:325
 msgid "To **see which protections are available and which are enabled**, send a `!draupnir protections` command to the Management Room."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:288
 #: ../../../docs/configuring-playbook-bot-draupnir.md:327
 msgid "To [**see the configuration options for a given protection**](https://the-draupnir-project.github.io/draupnir-documentation/protections/configuring-protections#displaying-the-protection-settings), send a `!draupnir protections show PROTECTION_NAME` (e.g. `!draupnir protections show JoinWaveShortCircuitProtection`)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:290
 #: ../../../docs/configuring-playbook-bot-draupnir.md:329
 msgid "To [**set a specific option for a given protection**](https://the-draupnir-project.github.io/draupnir-documentation/protections/configuring-protections#changing-protection-settings), send a command like this: `!draupnir protections config set PROTECTION_NAME OPTION VALUE` (e.g. `!draupnir protections config set JoinWaveShortCircuitProtection timescaleMinutes 30`)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:292
 #: ../../../docs/configuring-playbook-bot-draupnir.md:331
 msgid "To [**enable a given protection**](https://the-draupnir-project.github.io/draupnir-documentation/protections/block-invitations-on-server-protection#enabling-the-protection), send a command like this: `!draupnir protections enable PROTECTION_NAME` (e.g. `!draupnir protections enable JoinWaveShortCircuitProtection`)."
 msgstr ""

 #: ../../../docs/configuring-playbook-bot-draupnir.md:294
 #: ../../../docs/configuring-playbook-bot-draupnir.md:333
 msgid "To **disable a given protection**, send a command like this: `!draupnir protections disable PROTECTION_NAME` (e.g. `!draupnir protections disable JoinWaveShortCircuitProtection`)."
 msgstr ""