matrix-docker-ansible-deploy/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-appservice-draupnir-for-all.po

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community
# members
# This file is distributed under the same license as the
# matrix-docker-ansible-deploy package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-12-20 09:53+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
"Language-Team: jp <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"

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

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:3
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:5
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:7
msgid "Draupnir Appservice mode compared to Draupnir bot mode"
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:9
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."
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:11
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)."
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:13
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:15
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."
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:17
msgid ""
"Draupnir for all does not support 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:19
msgid "Prerequisites"
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:21
msgid "Create a main management room"
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:23
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."
msgstr ""

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

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:29
msgid ""
"The management room has to be given an alias and be public when you are "
"setting up the bot for the first time as the bot does not differentiate "
"between invites and invites to the management room."
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:31
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."
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:33
msgid ""
"As noted in the Draupnir install instructions the control room is "
"sensitive. **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:35
msgid "Set an alias to the management room"
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:37
msgid "Next, set an alias to the management room."
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:39
msgid ""
"This alias can be anything you want. However, for increased security "
"during the setup phase, it is recommended to make this alias be a random "
"string. When it has been locked down after setup phase, you can give your"
" room a secondary human readable alias."
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:41
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`."
msgstr ""

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

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:53
msgid ""
"You can configure additional options by adding the "
"`matrix_appservice_draupnir_for_all_extension_yaml` variable."
msgstr ""

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

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:69
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:71
#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:86
msgid "**Notes**:"
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73
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:75
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:77
msgid "Installing"
msgstr ""

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

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

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:90
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:92
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:94
msgid "Usage"
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:96
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 "
"succesfully installed Draupnir for All and can now start using it."
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:98
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."
msgstr ""

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

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:102
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` recomendation. Using"
" the chat is recomended."
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:104
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))"
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:106
msgid ""
"To allow users or whole homeservers you type /plain @draupnir-"
"main:example.com 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."
msgstr ""

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

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:110
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."
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:112
msgid ""
"Congratulations if you made it all the way here because you now have a "
"fully working Draupnir for all deployment."
msgstr ""

#~ msgid "Installation"
#~ msgstr ""

#~ msgid "Create a main management room."
#~ msgstr ""

#~ msgid ""
#~ "The playbook does not create a "
#~ "management room for your Main Draupnir."
#~ " This task you have to do on"
#~ " your own."
#~ msgstr ""

#~ msgid ""
#~ "As noted in the Draupnir install "
#~ "instructions the control room is "
#~ "sensitive. The following is said about"
#~ " the control room in the Draupnir "
#~ "install instructions."
#~ msgstr ""

#~ msgid ""
#~ "Anyone in this room can control "
#~ "the bot so it is important that"
#~ " you only invite trusted users to "
#~ "this room. The room must be "
#~ "unencrypted since the playbook does not"
#~ " support installing Pantalaimon yet."
#~ msgstr ""

#~ msgid "Give your main management room an alias."
#~ msgstr ""

#~ msgid ""
#~ "Give the room from step 1 an "
#~ "alias. This alias can be anything "
#~ "you want and its recommended for "
#~ "increased security during the setup "
#~ "phase of the bot that you make "
#~ "this alias be a random string. You"
#~ " can give your room a secondary "
#~ "human readable alias when it has "
#~ "been locked down after setup phase."
#~ msgstr ""

#~ msgid "Adjusting the playbook configuration."
#~ msgstr ""

#~ msgid ""
#~ "Add the following configuration to your"
#~ " `inventory/host_vars/matrix.example.com/vars.yml` file "
#~ "(adapt to your needs):"
#~ msgstr ""

#~ msgid ""
#~ "You must replace `ALIAS_FROM_STEP_2_GOES_HERE` "
#~ "with the alias you created in step"
#~ " 2."
#~ msgstr ""

#~ msgid ""
#~ "The installation of Draupnir for all "
#~ "in this playbook is very much "
#~ "Alpha quality. Usage-wise, Draupnir for"
#~ " allis almost identical to Draupnir "
#~ "bot mode."
#~ msgstr ""

#~ msgid "How to provision a D4A once you are allowed to."
#~ msgstr ""

#~ msgid ""
#~ "Open a DM with @draupnir-"
#~ "main:example.com and if using an Element"
#~ " client send a message into this "
#~ "DM to finalise creating it. 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."
#~ msgstr ""

#~ msgid "Configuration of D4A"
#~ msgstr ""

#~ msgid ""
#~ "You can refer to the upstream "
#~ "[documentation](https://github.com/the-draupnir-"
#~ "project/Draupnir) for more configuration "
#~ "documentation. Please note that 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 ""

#~ msgid ""
#~ "Please note that Config extension does"
#~ " not affect the appservices config as"
#~ " this config is not extensible in "
#~ "current Draupnir anyways. Config extension "
#~ "instead touches the config passed to "
#~ "the Draupnirs that your Appservice "
#~ "creates. So for example below makes "
#~ "all provisioned Draupnirs protect all "
#~ "joined rooms."
#~ msgstr ""

#~ msgid ""
#~ "You can configure additional options by"
#~ " adding the "
#~ "`matrix_appservice_draupnir_for_all_extension_yaml` variable "
#~ "to your `inventory/host_vars/matrix.example.com/vars.yml`"
#~ " file."
#~ msgstr ""

#~ msgid ""
#~ "For example to change Draupnir's "
#~ "`protectAllJoinedRooms` option to `true` you"
#~ " would add the following to your "
#~ "`vars.yml` file."
#~ msgstr ""