matrix-docker-ansible-deploy/i18n/locales/bg/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-16 12:05+0900\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: bg\n"
"Language-Team: bg <LL@li.org>\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\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 "Installation"
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. "
"This task you have to do on your own."
msgstr ""

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

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

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:32
msgid "Give your main management room an alias."
msgstr ""

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

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

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:38
msgid ""
"Add the following configuration to your "
"`inventory/host_vars/matrix.example.com/vars.yml` file (adapt to your "
"needs):"
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:40
msgid ""
"You must replace `ALIAS_FROM_STEP_2_GOES_HERE` with the alias you created"
" in step 2."
msgstr ""

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

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

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:57
msgid "**Notes**:"
msgstr ""

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:59
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:61
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:63
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:65
msgid "Usage"
msgstr ""

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

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

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:73
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:75
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:77
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:79
msgid "How to provision a D4A once you are allowed to."
msgstr ""

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

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

#: ../../../docs/configuring-playbook-appservice-draupnir-for-all.md:85
msgid "Configuration of D4A"
msgstr ""

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

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

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

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