remove Zulip bridge

.codespellrc

@@ -1,2 +1,2 @@
 [codespell]
-ignore-words-list = aNULL,brose,doub,Udo,re-use,re-used,registr,shema,commet,Commet
+ignore-words-list = aNULL,brose,doub,Udo,re-use,re-used,registr,shema

.github/workflows/matrix.yml

@@ -9,37 +9,34 @@ name: Matrix CI
 
 on: [push, pull_request]  # yamllint disable-line rule:truthy
 
-permissions:
-  contents: read
-
 jobs:
-  prek:
+  yamllint:
-    name: Run prek hooks
+    name: yamllint
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out
+        uses: actions/checkout@v6
+      - name: Run yamllint
+        uses: frenck/action-yamllint@v1.5.0
+  ansible-lint:
+    name: ansible-lint
     runs-on: ubuntu-latest
-    container:
-      image: docker.io/archlinux:base-devel
-
     steps:
-      # git must be installed before checkout so it does a proper clone
-      # (with .git directory) instead of a tarball download.
-      - name: Install git
-        run: pacman -Sy --noconfirm git
-
       - name: Check out
         uses: actions/checkout@v6
 
-      - name: Restore prek cache
+      - name: Run ansible-lint
-        uses: actions/cache@v5
+        uses: ansible/ansible-lint@v26.1.1
         with:
-          path: var/prek
+          args: "roles/custom"
-          key: arch-prek-v1-${{ hashFiles('.pre-commit-config.yaml') }}
+          setup_python: "true"
-
+          working_directory: ""
-      - name: Install dependencies
+          requirements_file: requirements.yml
-        run: pacman -S --noconfirm --needed just mise python
+  precommit:
-
+    name: Run pre-commit
-      - name: Run prek hooks
+    runs-on: ubuntu-latest
-        run: |
+    steps:
-          # The checkout action sets safe.directory using its own bundled
+      - name: Checkout code
-          # git, which is separate from the pacman-installed git that prek uses.
+        uses: actions/checkout@v6
-          git config --global --add safe.directory "$GITHUB_WORKSPACE"
+      - name: Run pre-commit
-          just prek-run-on-all
+        uses: pre-commit/action@v3.0.1

.github/workflows/update-translations.yml

@@ -1,52 +0,0 @@
-# SPDX-FileCopyrightText: 2024 Suguru Hirahara
-#
-# SPDX-License-Identifier: AGPL-3.0-or-later
-
----
-name: Update translations
-
-on:  # yamllint disable-line rule:truthy
-  push:
-    branches:
-      - master
-    paths:  # See include_patterns on conf.py
-      - 'docs/*.md'
-      - 'i18n/README.md'
-      - '*.md'
-
-permissions:
-  contents: write
-  pull-requests: write
-
-jobs:
-  update:
-    if: github.repository == 'spantaleev/matrix-docker-ansible-deploy'
-    name: Update translations
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v6
-
-      - uses: actions/setup-python@v6
-        with:
-          python-version: '3.14'
-
-      # Setting up recommended prerequisites
-      # See: i18n/README.md
-      - uses: astral-sh/setup-uv@v7
-      - uses: extractions/setup-just@v3
-
-      # TODO: optimize when we start publishing translations and integrate a Weblate instance
-      - name: Update translation catalog templates (POT) files
-        run: just --justfile i18n/justfile extract-translation-templates
-
-      - name: Create Pull Request
-        uses: peter-evans/create-pull-request@v8.1.0
-        with:
-          author: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>  # Same as committer
-          body: This is an automatic pull request to update translation files.
-          branch: create-pull-request/i18n
-          commit-message: Automatic translations update
-          delete-branch: true
-          labels: docs
-          sign-commits: true
-          title: Automatic translations update

.gitignore

@@ -4,7 +4,6 @@
 .python-version
 .idea/
 .direnv/
-/var/
 
 # ignore roles pulled by ansible-galaxy
 /roles/galaxy/*

.pre-commit-config.yaml

@@ -1,21 +1,22 @@
 ---
+default_install_hook_types: [pre-push]
 
-exclude: "^(LICENSES/|var/)"
+exclude: "LICENSES/"
 
 # See: https://pre-commit.com/hooks.html
 repos:
   - repo: https://github.com/pre-commit/pre-commit-hooks
     rev: v6.0.0
     hooks:
+      # - id: check-executables-have-shebangs
       - id: check-added-large-files
       - id: check-case-conflict
       - id: check-json
-      - id: check-shebang-scripts-are-executable
       - id: check-toml
       - id: trailing-whitespace
       - id: end-of-file-fixer
   - repo: https://github.com/codespell-project/codespell
-    rev: v2.4.2
+    rev: v2.4.1
     hooks:
       - id: codespell
         args: ["--skip=*.po,*.pot,i18n/"]
@@ -23,18 +24,3 @@ repos:
     rev: v6.2.0
     hooks:
       - id: reuse
-  - repo: https://github.com/ansible/ansible-lint
-    rev: v26.4.0
-    hooks:
-      - id: ansible-lint
-        files: '^roles/custom/'
-        args: ['roles/custom']
-        pass_filenames: false
-  - repo: local
-    hooks:
-      - id: check-examples-vars-migration-version
-        name: Check examples/vars.yml migration version matches expected
-        entry: bin/check-examples-vars-migration-version.sh
-        language: script
-        files: '(examples/vars\.yml|roles/custom/matrix_playbook_migration/defaults/main\.yml)'
-        pass_filenames: false

CHANGELOG.md

@@ -1,282 +1,3 @@
-# 2026-04-03
-
-## (BC Break) Synapse Admin (fork by etke.cc) is now Ketesa
-
-Synapse Admin has been rebranded to **[Ketesa](https://github.com/etkecc/ketesa)** — a landmark release that introduces a new identity, a full UI redesign, mobile-first layout, and deep Matrix Authentication Service (MAS) integration. For the full story behind the rename and a tour of what's new, see the [Ketesa v1.0.0 announcement](https://etke.cc/blog/introducing-ketesa/).
-
-Ketesa is a zero-configuration drop-in replacement for Synapse Admin: no server-side changes required, just update the role variables.
-
-The `matrix-synapse-admin` role has been **renamed** to `matrix-ketesa`. All `matrix_synapse_admin_*` variables must be **renamed** to `matrix_ketesa_*` in your `vars.yml`.
-
-Additionally, the **Docker image** changed from `ghcr.io/etkecc/synapse-admin` to `ghcr.io/etkecc/ketesa`. The default path prefix remains `/synapse-admin` for backward compatibility — updating to `/ketesa` is recommended but not required.
-
-The playbook will automatically detect leftover `matrix_synapse_admin_*` variables and fail with a helpful message listing what needs to be renamed.
-
-The playbook handles reverse-proxy routing for subpath deployments (e.g. `/ketesa`), including MAS-enabled setups — though OIDC auth flows on real servers still have some rough edges. Feedback is appreciated in [#ketesa:etke.cc](https://matrix.to/#/#ketesa:etke.cc).
-
-See the [Ketesa documentation](docs/configuring-playbook-ketesa.md) for details.
-
-# 2026-04-02
-
-## (BC Break) Draupnir for all Self Service Provisioning is now disabled by default
-
-💡 If you don't use [Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md), then this breaking change does not concern you..
-
-[Draupnir for all](./docs/configuring-playbook-appservice-draupnir-for-all.md) now ships with `allowSelfServiceProvisioning: false` as default upstream and in this playbook.
-
-This means users can no longer provision Draupnir instances by inviting the appservice bot unless you explicitly opt in.
-
-Manual provisioning by administrators is now the recommended approach. You do not want to enable Self Service Provisioning unless you have additional custom safeguards like those used by asgard.chat in place.
-
-If you want to enable Self Service Provisioning, add the following to your `vars.yml`:
-
-```yaml
-matrix_appservice_draupnir_for_all_configuration_extension_yaml: |
-  allowSelfServiceProvisioning: true
-```
-
-# 2026-03-23
-
-## Migration validation system introduced
-
-Previously, when updating your setup, you had to remember to read the [CHANGELOG](CHANGELOG.md) file or risk breakage.
-
-Now, the playbook includes a migration validation system that ensures you're aware of breaking changes before they affect your deployment.
-You're now forced to acknowledge each breaking change, unless you wish to live dangerously (see below).
-
-A new `matrix_playbook_migration_validated_version` variable has been introduced.
-
-**New users** who started from the [example `vars.yml`](examples/vars.yml) file already have this variable set and do not need to do anything.
-
-**Existing users** will need to add the following to their `vars.yml` file after reviewing all changelog entries up to now:
-
-```yml
-matrix_playbook_migration_validated_version: v2026.03.23.0
-```
-
-Going forward, whenever a breaking change is introduced the playbook will:
-
-- bump its expected version value (`matrix_playbook_migration_expected_version`), causing a discrepancy with what you validated (`matrix_playbook_migration_validated_version`)
-
-- fail when you run it with a helpful message listing what changed and linking to the relevant changelog entries
-
-After reviewing and adapting your setup, you simply update the variable to the new version.
-
-If you'd like to live dangerously and skip these checks (not recommended), you can set this once and be done with it:
-
-```yml
-matrix_playbook_migration_validated_version: "{{ matrix_playbook_migration_expected_version }}"
-```
-
-# 2026-03-19
-
-## Matrix Authentication Service now prefers UNIX sockets for playbook-managed Postgres
-
-When [Matrix Authentication Service](docs/configuring-playbook-matrix-authentication-service.md) (MAS) uses the playbook-managed Postgres service, it now connects to it via a [UNIX socket](https://en.wikipedia.org/wiki/Unix_domain_socket) by default instead of TCP.
-
-This follows the same approach [applied to Synapse](#synapse-now-prefers-unix-sockets-for-playbook-managed-postgres-and-valkey) and reduces unnecessary container-network wiring, keeping local IPC off the network stack.
-
-If you use an external Postgres server for MAS, this does not change your setup.
-
-If you'd like to keep the previous TCP-based behavior, add the following configuration to your `vars.yml`:
-
-```yaml
-matrix_authentication_service_config_database_socket_enabled: false
-```
-
-# 2026-03-17
-
-## Synapse now prefers UNIX sockets for playbook-managed Postgres and Valkey
-
-When Synapse uses the playbook-managed Postgres and Valkey services, it now connects to them via [UNIX sockets](https://en.wikipedia.org/wiki/Unix_domain_socket) by default instead of TCP.
-
-This reduces unnecessary container-network wiring and keeps local IPC off the network stack, which is a bit simpler and slightly more secure.
-
-If you use an external Postgres server or external Redis/Valkey for Synapse, this does not change your setup.
-
-If you'd like to keep the previous TCP-based behavior, add the following configuration to your `vars.yml`:
-
-```yaml
-matrix_synapse_database_socket_enabled: false
-matrix_synapse_redis_path_enabled: false
-```
-
-# 2026-03-01
-
-## (Potential BC Break) Synapse S3 media prefix is now applied consistently
-
-The `matrix_synapse_ext_synapse_s3_storage_provider_config_prefix` variable is now wired consistently for both:
-
-- the Synapse `s3_storage_provider` module configuration
-- the `matrix-synapse-s3-storage-provider-migrate` migration script (`s3_media_upload --prefix`)
-
-Previously, this variable could be set, but was not effectively applied by either of these paths.
-
-**Affects**: users of [synapse-s3-storage-provider](docs/configuring-playbook-synapse-s3-storage-provider.md) who have configured a non-empty `matrix_synapse_ext_synapse_s3_storage_provider_config_prefix` value.
-
-If your bucket data was uploaded without the prefix before this fix, enabling proper prefix usage can make existing objects appear missing until data is migrated/copied to the prefixed key namespace.
-
-# 2026-02-26
-
-## Internal refactor: merged the Synapse reverse-proxy companion role into `matrix-synapse`
-
-The standalone `matrix-synapse-reverse-proxy-companion` role has been merged into the [matrix-synapse](roles/custom/matrix-synapse/) role.
-
-This is not a user-facing change and does not change variable names (`matrix_synapse_reverse_proxy_companion_*` remain the same). The split looked clean on paper, but in practice both parts are tightly coupled through worker routing, tags (`setup-synapse`/`install-synapse`), and lifecycle ordering, so keeping them separate added coordination overhead with little practical benefit.
-
-Compatibility note: existing companion-specific tags (`setup-synapse-reverse-proxy-companion` and `install-synapse-reverse-proxy-companion`) are still available.
-
-With this change, Synapse and its reverse-proxy companion are managed in one role (`matrix-synapse`) while still keeping companion logic in dedicated task/template subdirectories for maintainability.
-
-# 2026-02-21
-
-## (BC Break) coturn is no longer auto-enabled by default
-
-By default, the [coturn](./docs/configuring-playbook-turn.md) TURN server component is no longer enabled for every deployment.
-
-This reduces resources and attach surface for deployments which:
-
-- either don't need calls at all
-- or use the modern [Matrix RTC](docs/configuring-playbook-matrix-rtc.md)/[Element Call](docs/configuring-playbook-element-call.md) stack.
-
-Coturn is still auto-enabled when [Jitsi](./docs/configuring-playbook-jitsi.md) is enabled (`jitsi_enabled: true`), because Jitsi still depends on TURN for legacy Matrix integration.
-
-Additionally, Coturn (when enabled) now defaults to using automatic IP detection of your server's external IP address, instead of assuming your Ansible inventory (`ansible_host`) points to a public address and using it for configuring `coturn_turn_external_ip_address`.
-
-To restore the old behavior (needed for legacy call setups), add the following configuration to your `vars.yml`:
-
-```yml
-coturn_enabled: true
-
-# If you'd like explicit control over the external IP address (like before), keep this too.
-coturn_turn_external_ip_address: "{{ ansible_host }}"
-```
-
-## LiveKit TURN TLS is now automatically fronted by playbook-managed Traefik
-
-For deployments that use the playbook-managed Traefik reverse-proxy, LiveKit TURN over TCP is now SSL-terminated at Traefik and passed as plain TCP to LiveKit (`turn.external_tls = true`) by default.
-
-To disable this behavior, set `livekit_server_config_turn_external_tls: false` and the playbook will revert to the old behavior - using traefik-certs-dumper to extract SSL certificates out of Traefik and pass them to LiveKit for explicit SSL termination there.
-
-If you are using `other-traefik-container` or [another reverse-proxy](./configuring-playbook-own-webserver.md), this change does **not** switch behavior automatically. That mode remains using certificate files in the container (Traefik certificates dumper flow) unless you explicitly set the TURN-Traefik mode variables to opt in.
-
-# 2026-02-17
-
-## (BC Break) prometheus-nginxlog-exporter role has been relocated and variable names need adjustments
-
-The role for prometheus-nginxlog-exporter has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization.
-
-Along with the relocation, the `matrix_prometheus_nginxlog_exporter_` prefix on its variable names has been renamed to `prometheus_nginxlog_exporter_`, so you need to adjust your `vars.yml` configuration.
-
-As always, the playbook would let you know about this and point out any variables you may have missed.
-
-## synapse-auto-invite-accept has been removed from the playbook
-
-[synapse-auto-invite-accept](./docs/configuring-playbook-synapse-auto-accept-invite.md) has been removed from the playbook, as the same functionality [has been integrated](https://github.com/element-hq/synapse/pull/17147) to Synapse since [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0).
-
-See [this section](./docs/configuring-playbook-synapse-auto-accept-invite.md#native-alternative) for details about how to enable the function on Synapse.
-
-If you're using any `matrix_synapse_ext_synapse_auto_accept_invite_*` variables, the playbook will let you know which one you'll need to remove from `vars.yml`.
-
-# 2026-02-16
-
-## matrix-appservice-slack has been removed from the playbook
-
-[matrix-appservice-slack](./docs/configuring-playbook-bridge-appservice-slack.md) has been removed from the playbook, as it has been discontinued because the public Matrix.org Slack bridge has been decommissioned on January 14th, 2026.
-
-The playbook will let you know if you're using any `matrix_appservice_slack_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-bridge-appservice-slack.md#uninstalling-the-component-manually).
-
-**Note**: Bridging to [Slack](https://slack.com) can also happen via the [mautrix-slack](./docs/configuring-playbook-bridge-mautrix-slack.md) bridge supported by the playbook.
-
-# 2026-02-13
-
-## Conditional service restart for `install-*` commands
-
-When running `install-all` or `install-service` (whether via `just` or raw `ansible-playbook`), only services whose configuration or container image actually changed during the playbook run will now be restarted. Unchanged services are left running (or get started if they were stopped). This reduces unnecessary downtime — particularly for services like Traefik (the reverse proxy), which previously caused brief connectivity interruptions on every playbook run even when nothing changed.
-
-When running with `setup-*` tags (e.g. `setup-all`, `setup-synapse`), all services continue to be unconditionally restarted as before.
-
-Currently, only Traefik tracks its own changes and benefits from conditional restart. All other services default to being restarted (the previous behavior). This is just the beginning — as more roles gain change-tracking support, playbook performance will improve and downtime will decrease dramatically, especially for `install-all` runs where most services haven't changed.
-
-Some benchmarks for `just install-service traefik` when Traefik settings did not change:
-
-- **Before**:
-  - total time: ~56 seconds 🐌
-  - Traefik restarted: yes (unnecessarily) ❌
-  - dependent services restarted: yes, all of them ❌
-- **After**:
-  - total time: ~27 seconds ⚡
-  - Traefik restarted: no ✅
-  - dependent services restarted: no ✅
-
-This behavior can be overridden via `--extra-vars='devture_systemd_service_manager_conditional_restart_enabled=false'` to force unconditional restarts. See [Conditional service restart](docs/just.md#conditional-service-restart) for details.
-
-
-# 2026-02-12
-
-## Dimension integration manager has been removed from the playbook
-
-The [Dimension integration manager](./docs/configuring-playbook-dimension.md) has been removed from the playbook, as it has been unmaintained.
-
-The playbook will let you know if you're using any `matrix_dimension_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the component manually](./docs/configuring-playbook-dimension.md#uninstalling-the-component-manually).
-
-## (BC Break) Hydrogen role has been relocated and variable names need adjustments
-
-The role for Hydrogen has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization.
-
-Along with the relocation, the `matrix_client_hydrogen_` prefix was dropped from its variable names, so you need to adjust your `vars.yml` configuration.
-
-You need to do the following replacement:
-
-- `matrix_client_hydrogen_` -> `hydrogen_`
-
-As always, the playbook would let you know about this and point out any variables you may have missed.
-
-# 2026-02-11
-
-## (BC Break) coturn role has been relocated and variable names need adjustments
-
-The role for coturn has been relocated to the [mother-of-all-self-hosting](https://github.com/mother-of-all-self-hosting) organization.
-
-Along with the relocation, the `matrix_coturn_` prefix on its variable names has been renamed to `coturn_`, so you need to adjust your `vars.yml` configuration.
-
-As always, the playbook would let you know about this and point out any variables you may have missed.
-
-## conduwuit has been removed from the playbook
-
-[conduwuit](./docs/configuring-playbook-conduwuit.md) has been removed from the playbook, as it has been abandoned.
-
-The playbook will let you know if you're using any `matrix_conduwuit_*` variables. You'll need to remove them from `vars.yml` and potentially [uninstall the service manually](./docs/configuring-playbook-conduwuit.md#uninstalling-the-service-manually).
-
-Since [Continuwuity](configuring-playbook-continuwuity.md) is a drop-in replacement for conduwuit, migration is possible. Please refer to [this section](./configuring-playbook-continuwuity.md#migrating-from-conduwuit) for details.
-
-# 2026-02-09
-
-## (BC Break) matrix-media-repo datastore IDs are now required in `vars.yml`
-
-**Affects**: users with [matrix-media-repo](docs/configuring-playbook-matrix-media-repo.md) enabled (`matrix_media_repo_enabled: true`)
-
-The `matrix_media_repo_datastore_file_id` and `matrix_media_repo_datastore_s3_id` variables are no longer auto-configured with values. They must now be explicitly defined in your `vars.yml` file. The playbook will fail with a helpful error if they are not set (when needed).
-
-These were never meant to be auto-configured. They were derived from `matrix_homeserver_generic_secret_key`, which is intended for secrets that are OK to change subsequently (and Ansible would assist in propagating these changes). matrix-media-repo datastore IDs are not secrets — they are static identifiers linking media to storage backends, and **must not change** after first use.
-
-**For existing installations**, retrieve your current values from the server:
-
-```sh
-grep 'id:' /matrix/media-repo/config/media-repo.yaml
-```
-
-Then add to your `vars.yml`:
-
-```yaml
-matrix_media_repo_datastore_file_id: "YOUR_FILE_DATASTORE_ID_HERE"
-
-# Only if you use S3 storage:
-# matrix_media_repo_datastore_s3_id: "YOUR_S3_DATASTORE_ID_HERE"
-```
-
-**Why do this?**: This change allows us to **remove the [passlib](https://passlib.readthedocs.io/en/stable/index.html) Python library** from the [prerequisites](docs/prerequisites.md), as it was the last component that depended on it.
-
 # 2026-02-08
 
 ## Zulip bridge has been removed from the playbook
@@ -566,7 +287,7 @@ In light of this new information, you have 2 options:
 - Consider closing the STUN/UDP port with the following configuration:
 
   ```yaml
-  coturn_container_stun_plain_host_bind_port_udp: ""
+  matrix_coturn_container_stun_plain_host_bind_port_udp: ""
   ```
 
 - Consider keeping `3478/udp` blocked in your external firewall (if you have one)
@@ -627,11 +348,11 @@ The playbook now **only exposes the Coturn STUN port (`3478`) over TCP by defaul
 If you'd like the Coturn STUN port to be exposed over UDP like before, you can revert to the previous behavior by using the following configuration in your `vars.yml` file:
 
 ```yaml
-coturn_container_stun_plain_host_bind_port_udp: "3478"
+matrix_coturn_container_stun_plain_host_bind_port_udp: "3478"
 ```
 
 > [!WARNING]
-> People running Coturn directly on the `host` network (using `coturn_container_network: host`) will still have the STUN port exposed over UDP, as port exposure is done directly via Coturn and not via Docker. In such cases, the playbook cannot prevent `3478/udp` port exposure and you'd need to do it in another way (separate firewall rule, etc).
+> People running Coturn directly on the `host` network (using `matrix_coturn_container_network: host`) will still have the STUN port exposed over UDP, as port exposure is done directly via Coturn and not via Docker. In such cases, the playbook cannot prevent `3478/udp` port exposure and you'd need to do it in another way (separate firewall rule, etc).
 
 
 # 2025-02-17
@@ -884,8 +605,8 @@ If upstream synapse-admin picks up the pace and improves, the etke.cc fork may d
 If you'd like to switch back to the original synapse-admin software, you can do so by adding the following configuration to your `vars.yml` file:
 
 ```yaml
-matrix_synapse_admin_container_image: "{{ matrix_synapse_admin_container_image_registry_prefix }}awesometechnologies/synapse-admin:{{ matrix_synapse_admin_version }}"
+matrix_synapse_admin_docker_image: "{{ matrix_synapse_admin_docker_image_registry_prefix }}awesometechnologies/synapse-admin:{{ matrix_synapse_admin_version }}"
-matrix_synapse_admin_container_image_registry_prefix_upstream: docker.io/
+matrix_synapse_admin_docker_image_registry_prefix_upstream: docker.io/
 
 matrix_synapse_admin_version: 0.10.3
 
@@ -1974,12 +1695,12 @@ Other roles which aren't strictly related to Matrix are likely to follow this fa
 
 ## coturn can now use host-networking
 
-Large coturn deployments (with a huge range of ports specified via `coturn_turn_udp_min_port` and `coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow coturn service startup and shutdown.
+Large coturn deployments (with a huge range of ports specified via `matrix_coturn_turn_udp_min_port` and `matrix_coturn_turn_udp_max_port`) experience a huge slowdown with how Docker publishes all these ports (setting up firewall forwarding rules), which leads to a very slow coturn service startup and shutdown.
 
 Such deployments don't need to run coturn within a private container network anymore. coturn can now run with host-networking by using configuration like this:
 
 ```yaml
-coturn_container_network: host
+matrix_coturn_container_network: host
 ```
 
 With such a configuration, **Docker no longer needs to configure thousands of firewall forwarding rules** each time coturn starts and stops. This, however, means that **you will need to ensure these ports are open** in your firewall yourself.
@@ -1988,11 +1709,11 @@ Thanks to us [tightening coturn security](#backward-compatibility-tightening-cot
 
 ## (Backward Compatibility) Tightening coturn security can lead to connectivity issues
 
-**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default coturn blocklists. They may need to override `coturn_denied_peer_ips` and remove some IP ranges from it.
+**TLDR**: users who run and access their Matrix server on a private network (likely a small minority of users) may experience connectivity issues with our new default coturn blocklists. They may need to override `matrix_coturn_denied_peer_ips` and remove some IP ranges from it.
 
 Inspired by [this security article](https://www.rtcsec.com/article/cve-2020-26262-bypass-of-coturns-access-control-protection/), we've decided to make use of coturn's `denied-peer-ip` functionality to prevent relaying network traffic to certain private IP subnets. This ensures that your coturn server won't accidentally try to forward traffic to certain services running on your local networks. We run coturn in a container and in a private container network by default, which should prevent such access anyway, but having additional block layers in place is better.
 
-If you access your Matrix server from a local network and need coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it.
+If you access your Matrix server from a local network and need coturn to relay to private IP addresses, you may observe that relaying is now blocked due to our new default `denied-peer-ip` lists (specified in `matrix_coturn_denied_peer_ips`). If you experience such connectivity problems, consider overriding this setting in your `vars.yml` file and removing certain networks from it.
 
 We've also added `no-multicast-peers` to the default coturn configuration, but we don't expect this to cause trouble for most people.
 
@@ -2778,8 +2499,8 @@ To improve security, we've [removed TLSv1 and TLSv1.1 support](https://github.co
 If you need to support old clients, you can re-enable both (or whichever one you need) with the following configuration:
 
 ```yaml
-coturn_tls_v1_enabled: true
+matrix_coturn_tls_v1_enabled: true
-coturn_tls_v1_1_enabled: true
+matrix_coturn_tls_v1_1_enabled: true
 ```
 
 
@@ -4058,7 +3779,7 @@ Because people like using the playbook's components independently (outside of th
 With the new changes, **all roles are now only dependent on the minimal `matrix-base` role**. They are no longer dependent among themselves.
 
 In addition, the following components can now be completely disabled (for those who want/need to):
-- `matrix-coturn` by using `coturn_enabled: false`
+- `matrix-coturn` by using `matrix_coturn_enabled: false`
 - `matrix-mailer` by using `matrix_mailer_enabled: false`
 - `matrix-postgres` by using `matrix_postgres_enabled: false`
 
@@ -4278,7 +3999,7 @@ The following playbook variables were renamed:
 - from `matrix_docker_image_mautrix_telegram` to `matrix_mautrix_telegram_docker_image`
 - from `matrix_docker_image_mautrix_whatsapp` to `matrix_mautrix_whatsapp_docker_image`
 - from `matrix_docker_image_mailer` to `matrix_mailer_docker_image`
-- from `matrix_docker_image_coturn` to `coturn_container_image`
+- from `matrix_docker_image_coturn` to `matrix_coturn_docker_image`
 - from `matrix_docker_image_goofys` to `matrix_s3_goofys_docker_image`
 - from `matrix_docker_image_riot` to `matrix_riot_web_docker_image`
 - from `matrix_docker_image_nginx` to `matrix_nginx_proxy_docker_image`

README.md

@@ -52,7 +52,8 @@ The homeserver is the backbone of your Matrix system. Choose one from the follow
 | ---- | -------- | ----------- | ------------- |
 | [Synapse](https://github.com/element-hq/synapse) | ✅ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network | [Link](docs/configuring-playbook-synapse.md) |
 | [Conduit](https://conduit.rs) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements | [Link](docs/configuring-playbook-conduit.md) |
-| [continuwuity](https://continuwuity.org) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. | [Link](docs/configuring-playbook-continuwuity.md) |
+| [conduwuit](https://conduwuit.puppyirl.gay/) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit is a fork of Conduit. | [Link](docs/configuring-playbook-conduwuit.md) |
+| [continuwuity](https://continuwuity.org) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. continuwuity is a continuation of conduwuit. | [Link](docs/configuring-playbook-continuwuity.md) |
 | [Dendrite](https://github.com/element-hq/dendrite) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse. | [Link](docs/configuring-playbook-dendrite.md) |
 
 ### Clients
@@ -64,7 +65,6 @@ Web clients for Matrix that you can host on your own domains.
 | [Element Web](https://github.com/element-hq/element-web) | ✅ | Default Matrix web client, configured to connect to your own Synapse server | [Link](docs/configuring-playbook-client-element-web.md) |
 | [Hydrogen](https://github.com/element-hq/hydrogen-web) | ❌ | Lightweight Matrix client with legacy and mobile browser support | [Link](docs/configuring-playbook-client-hydrogen.md) |
 | [Cinny](https://github.com/ajbura/cinny) |  ❌ | Simple, elegant and secure web client | [Link](docs/configuring-playbook-client-cinny.md) |
-| [Sable](https://github.com/7w1/sable) | ❌ | Simple, elegant and secure web client | [Link](docs/configuring-playbook-client-sable.md) |
 | [SchildiChat Web](https://schildi.chat/) | ❌ | Based on Element Web, with a more traditional instant messaging experience | [Link](docs/configuring-playbook-client-schildichat-web.md) |
 | [FluffyChat Web](https://fluffychat.im/) | ❌ | The cutest messenger in Matrix | [Link](docs/configuring-playbook-client-fluffychat-web.md) |
 
@@ -75,12 +75,13 @@ Services that run on the server to make the various parts of your installation w
 | Name | Default? | Description | Documentation |
 | ---- | -------- | ----------- | ------------- |
 | [PostgreSQL](https://www.postgresql.org/)| ✅ | Database for Synapse. [Using an external PostgreSQL server](docs/configuring-playbook-external-postgres.md) is also possible. | [Link](docs/configuring-playbook-external-postgres.md) |
+| [coturn](https://github.com/coturn/coturn) | ✅ | STUN/TURN server for WebRTC audio/video calls | [Link](docs/configuring-playbook-turn.md) |
 | [Traefik](https://doc.traefik.io/traefik/) | ✅ | Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. [Using your own webserver](docs/configuring-playbook-own-webserver.md) is also possible. | [Link](docs/configuring-playbook-traefik.md) |
 | [Let's Encrypt](https://letsencrypt.org/) | ✅ | Free SSL certificate, which secures the connection to all components | [Link](docs/configuring-playbook-ssl-certificates.md) |
 | [Exim](https://www.exim.org/) | ✅ | Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server) | [Link](docs/configuring-playbook-email.md) |
-| [coturn](https://github.com/coturn/coturn) | ❌ | STUN/TURN server for WebRTC audio/video calls | [Link](docs/configuring-playbook-turn.md) |
 | [ddclient](https://github.com/linuxserver/docker-ddclient) | ❌ | Dynamic DNS | [Link](docs/configuring-playbook-dynamic-dns.md) |
-| Matrix RTC stack | ❌ | Supporting components ([LiveKit Server](docs/configuring-playbook-livekit-server.md) and [LiveKit JWT Service](docs/configuring-playbook-livekit-jwt-service.md)) for in-app audio/video calls for Matrix clients | [Link](docs/configuring-playbook-matrix-rtc.md) |
+| [LiveKit Server](https://github.com/livekit/livekit) | ❌ | WebRTC server for audio/video calls | [Link](docs/configuring-playbook-livekit-server.md) |
+| [Livekit JWT Service](https://github.com/livekit/livekit-jwt-service) | ❌ | JWT service for integrating [Element Call](./configuring-playbook-element-call.md) with [LiveKit Server](./configuring-playbook-livekit-server.md) | [Link](docs/configuring-playbook-livekit-jwt-service.md) |
 
 ### Authentication
 
@@ -127,6 +128,7 @@ Bridges can be used to connect your Matrix installation with third-party communi
 | [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc) | ❌ | Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat) | [Link](docs/configuring-playbook-bridge-appservice-irc.md) |
 | [matrix-appservice-kakaotalk](https://src.miscworks.net/fair/matrix-appservice-kakaotalk) | ❌ | Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) | [Link](docs/configuring-playbook-bridge-appservice-kakaotalk.md) |
 | [matrix-appservice-discord](https://github.com/matrix-org/matrix-appservice-discord) | ❌ | Bridge to [Discord](https://discordapp.com/) | [Link](docs/configuring-playbook-bridge-appservice-discord.md) |
+| [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) | ❌ | Bridge to [Slack](https://slack.com/) | [Link](docs/configuring-playbook-bridge-appservice-slack.md) |
 | [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) | ❌ | Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular | [Link](docs/configuring-playbook-bridge-hookshot.md) |
 | [matrix-sms-bridge](https://github.com/benkuly/matrix-sms-bridge) | ❌ | Bridge to SMS | [Link](docs/configuring-playbook-bridge-matrix-bridge-sms.md) |
 | [matrix-steam-bridge](https://github.com/jasonlaguidice/matrix-steam-bridge) | ❌ | Bridge to [Steam](https://steampowered.com/) | [Link](docs/configuring-playbook-bridge-steam.md) |
@@ -159,7 +161,7 @@ Services that help you in administrating and monitoring your Matrix installation
 | ---- | -------- | ----------- | ------------- |
 | [matrix-alertmanager-receiver](https://github.com/metio/matrix-alertmanager-receiver) | ❌ | Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client | [Link](docs/configuring-playbook-alertmanager-receiver.md) |
 | [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) | ❌ | OAuth 2.0 and OpenID Provider server | [Link](docs/configuring-playbook-matrix-authentication-service.md) |
-| [Ketesa](https://github.com/etkecc/ketesa) | ❌ | Fully-featured web UI for administrating your Matrix homeserver — users, rooms, media, sessions, and more | [Link](docs/configuring-playbook-ketesa.md) |
+| [synapse-admin](https://github.com/etkecc/synapse-admin) | ❌ | Web UI tool for administrating users and rooms on your Matrix server | [Link](docs/configuring-playbook-synapse-admin.md) |
 | Metrics and Graphs | ❌ | Consists of the [Prometheus](https://prometheus.io) time-series database server, the Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter, and the [Grafana](https://grafana.com/) web UI, with [prometheus-nginxlog-exporter](https://github.com/martin-helmich/prometheus-nginxlog-exporter/) being available too | [Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-nginx-logs-optional)) |
 | [Borg](https://borgbackup.org) | ❌ | Backups | [Link](docs/configuring-playbook-backup-borg.md) |
 | [rageshake](https://github.com/matrix-org/rageshake) | ❌ | Bug report server | [Link](docs/configuring-playbook-rageshake.md) |
@@ -171,6 +173,7 @@ Various services that don't fit any other categories.
 
 | Name | Default? | Description | Documentation |
 | ---- | -------- | ----------- | ------------- |
+| [synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite) | ❌ | Synapse module to automatically accept invites | [Link](docs/configuring-playbook-synapse-auto-accept-invite.md) |
 | [synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor) | ❌ | Cli tool that automatically compresses `state_groups` database table in background | [Link](docs/configuring-playbook-synapse-auto-compressor.md) |
 | [Matrix Corporal](https://github.com/devture/matrix-corporal) (advanced) | ❌ | Reconciliator and gateway for a managed Matrix server | [Link](docs/configuring-playbook-matrix-corporal.md) |
 | [Matrix.to](https://github.com/matrix-org/matrix.to) | ❌ | Simple URL redirection service for the Matrix ecosystem | [Link](docs/configuring-playbook-matrixto.md) |

bin/check-examples-vars-migration-version.sh

@@ -1,35 +0,0 @@
-#!/bin/bash
-
-# SPDX-FileCopyrightText: 2026 Slavi Pantaleev
-#
-# SPDX-License-Identifier: AGPL-3.0-or-later
-
-# Ensures that the migration validated version in examples/vars.yml
-# matches the expected version in the matrix_playbook_migration role defaults.
-
-set -euo pipefail
-
-defaults_file="roles/custom/matrix_playbook_migration/defaults/main.yml"
-examples_file="examples/vars.yml"
-
-expected_version=$(grep -oP '^matrix_playbook_migration_expected_version:\s*"?\K[^"]+' "$defaults_file")
-examples_version=$(grep -oP '^matrix_playbook_migration_validated_version:\s*"?\K[^"]+' "$examples_file")
-
-if [ -z "$expected_version" ]; then
-	echo "ERROR: Could not extract matrix_playbook_migration_expected_version from $defaults_file"
-	exit 1
-fi
-
-if [ -z "$examples_version" ]; then
-	echo "ERROR: Could not extract matrix_playbook_migration_validated_version from $examples_file"
-	exit 1
-fi
-
-if [ "$expected_version" != "$examples_version" ]; then
-	echo "ERROR: Migration version mismatch!"
-	echo "  $defaults_file has expected version: $expected_version"
-	echo "  $examples_file has validated version: $examples_version"
-	echo ""
-	echo "Please update $examples_file to match."
-	exit 1
-fi

docs/configuring-playbook-bot-baibot.md

@@ -39,35 +39,16 @@ Depending on your current `vars.yml` file and desired configuration, **you may r
 
 To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
-Authentication can be configured in one of two mutually-exclusive ways:
-
-- **Password authentication** (`matrix_bot_baibot_config_user_password`) - recommended for most playbook-managed setups, because it integrates with automatic user creation flow used by the playbook, and auto-creates the bot account
-- **Access-token authentication** (`matrix_bot_baibot_config_user_access_token` + `matrix_bot_baibot_config_user_device_id`) - useful for specific [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md)/OIDC setups where password authentication is not available or not desired
-
-Even when [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) is enabled, password authentication is still typically the best fit for baibot if you're using a playbook-managed bot account.
-
-For upstream details, see baibot's [🔐 Authentication](https://github.com/etkecc/baibot/blob/main/docs/configuration/authentication.md) documentation.
-
 ```yaml
 matrix_bot_baibot_enabled: true
 
 # Uncomment and adjust this part if you'd like to use a username different than the default
 # matrix_bot_baibot_config_user_mxid_localpart: baibot
 
-# Authentication mode (choose exactly one):
-#
-# 1) Password authentication (recommended for most setups)
 # Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`.
 # If you'd like to change this password subsequently, see the details below.
 matrix_bot_baibot_config_user_password: 'PASSWORD_FOR_THE_BOT'
 
-# 2) Access-token authentication (for MAS/OIDC-enabled homeservers)
-# matrix_bot_baibot_config_user_access_token: 'YOUR_MAS_COMPATIBILITY_TOKEN_HERE'
-# matrix_bot_baibot_config_user_device_id: 'BAIBOT'
-#
-# You can generate a compatibility token for MAS with:
-# mas-cli manage issue-compatibility-token <username> [device_id]
-
 # An optional passphrase to use for backing up and recovering the bot's encryption keys.
 # You can create one with a command like `pwgen -s 64 1`.
 #
@@ -406,15 +387,13 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
 
 **Notes**:
 
-- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account when password authentication is used.
+- The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account.
-
-- If you're using access-token authentication, the bot account must already exist and the configured token + device ID must match that account. This mode is mainly for MAS/OIDC setups where password-based bot login is not suitable.
 
 - The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
 
   `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.
 
-- If you change the bot password (`matrix_bot_baibot_config_user_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_baibot_config_user_password` to let the bot know its new password. (This note applies to password authentication mode.)
+- If you change the bot password (`matrix_bot_baibot_config_user_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password.
 
 ## Usage
 

docs/configuring-playbook-bot-buscarron.md

@@ -89,7 +89,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
 
   `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.
 
-- If you change the bot password (`matrix_bot_buscarron_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_buscarron_password` to let the bot know its new password.
+- If you change the bot password (`matrix_bot_buscarron_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password.
 
 ## Usage
 

docs/configuring-playbook-bot-draupnir.md

@@ -102,7 +102,7 @@ This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synap
 
 **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).
 
-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).
+The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md).
 
 #### Add the configuration
 
@@ -212,7 +212,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
 
   `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.
 
-- 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.
+- 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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_draupnir_password` to let the bot know its new password.
 
 ## Usage
 

docs/configuring-playbook-bot-honoroit.md

@@ -78,7 +78,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
 
   `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.
 
-- If you change the bot password (`matrix_bot_honoroit_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_honoroit_password` to let the bot know its new password.
+- If you change the bot password (`matrix_bot_honoroit_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password.
 
 ## Usage
 

docs/configuring-playbook-bot-matrix-registration-bot.md

@@ -71,7 +71,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
 
   `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.
 
-- If you change the bot password (`matrix_bot_matrix_registration_bot_bot_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_matrix_registration_bot_bot_password` to let the bot know its new password.
+- If you change the bot password (`matrix_bot_matrix_registration_bot_bot_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password.
 
 ## Usage
 

docs/configuring-playbook-bot-matrix-reminder-bot.md

@@ -57,7 +57,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
 
   `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.
 
-- If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_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_matrix_reminder_bot_matrix_user_password` to let the bot know its new password.
+- If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password.
 
 ## Usage
 

docs/configuring-playbook-bot-maubot.md

@@ -103,7 +103,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
 
   `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.
 
-- If you change the bot password (`matrix_bot_maubot_initial_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_maubot_initial_password` to let the bot know its new password.
+- If you change the bot password (`matrix_bot_maubot_initial_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password.
 
 ## Usage
 

docs/configuring-playbook-bot-mjolnir.md

@@ -46,7 +46,7 @@ This can be done using Synapse's [Admin APIs](https://element-hq.github.io/synap
 
 **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).
 
-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).
+The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md).
 
 #### Add the configuration
 
@@ -198,7 +198,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
 
   `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.
 
-- If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password.
+- If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password.
 
 ## Usage
 

docs/configuring-playbook-bridge-appservice-slack.md

@@ -1,38 +1,157 @@
 <!--
-SPDX-FileCopyrightText: 2019 Edgars Voroboks
+SPDX-FileCopyrightText: 2019 - 2022 MDAD project contributors
-SPDX-FileCopyrightText: 2019 Eduardo Beltrame
-SPDX-FileCopyrightText: 2019-2025 MDAD project contributors
-SPDX-FileCopyrightText: 2019-2025 Slavi Pantaleev
-SPDX-FileCopyrightText: 2020 Chris van Dijk
-SPDX-FileCopyrightText: 2020 Tulir Asokan
 SPDX-FileCopyrightText: 2020 Udo Rader
-SPDX-FileCopyrightText: 2020 jens quade
+SPDX-FileCopyrightText: 2021 - 2024 Slavi Pantaleev
 SPDX-FileCopyrightText: 2021 Joel Bennett
-SPDX-FileCopyrightText: 2022 Dennis Ciba
+SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara
-SPDX-FileCopyrightText: 2022 Kim Brose
-SPDX-FileCopyrightText: 2022 Travis Ralston
-SPDX-FileCopyrightText: 2022 Vladimir Panteleev
-SPDX-FileCopyrightText: 2022 Yan Minagawa
 SPDX-FileCopyrightText: 2024 Fabio Bonelli
-SPDX-FileCopyrightText: 2024-2026 Suguru Hirahara
 
 SPDX-License-Identifier: AGPL-3.0-or-later
 -->
 
-# Setting up Appservice Slack bridging (optional, removed)
+# Setting up Appservice Slack bridging (optional)
 
-🪦 The playbook used to be able to install and configure [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack), but no longer includes this component, as it had been unavailable for new installation since 2024, and was finally abandoned because the public Matrix.org Slack bridge has been decommissioned on January 14th, 2026.
+**Notes**:
+- Bridging to [Slack](https://slack.com) can also happen via the [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridge supported by the playbook.
+- Currently (as of November, 2024) **this component is not available for new installation unless you have already created a classic Slack application** (which the bridge makes use of in order to enable bridging between Slack and Matrix), because the creation of classic Slack applications has been discontinued since June 4 2024. The author of the bridge claims [here](https://github.com/matrix-org/matrix-appservice-slack/issues/789#issuecomment-2172947787) that he plans to support the modern Slack application and until then "the best (and only) option for new installations is to use the webhook bridging".
 
-**Note**: Bridging to [Slack](https://slack.com) can also happen via the [mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridge supported by the playbook.
+The playbook can install and configure [matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack) for you.
 
-## Uninstalling the component manually
+See the project's [documentation](https://github.com/matrix-org/matrix-appservice-slack/blob/master/README.md) to learn what it does and why it might be useful to you.
 
-If you still have matrix-appservice-slack installed on your Matrix server, the playbook can no longer help you uninstall it and you will need to do it manually. To uninstall manually, run these commands on the server:
+## Prerequisites
 
-```sh
+### Create a Classic Slack App
-systemctl disable --now matrix-appservice-slack.service
 
-rm -rf /matrix/appservice-slack
+First, you need to create a Classic Slack App [here](https://api.slack.com/apps?new_classic_app=1).
 
-/matrix/postgres/bin/cli-non-interactive -c 'DROP DATABASE matrix_appservice_slack;'
+Name the app "matrixbot" (or anything else you'll remember). Select the team/workspace this app will belong to. Click on bot users and add a new bot user. We will use this account to bridge the the rooms.
+
+Then, click on Event Subscriptions and enable them and use the request url: `https://matrix.example.com/appservice-slack`.
+
+Add the following events as `Bot User Events` and save:
+
+- team_domain_change
+- message.channels
+- message.groups (if you want to bridge private channels)
+- reaction_added
+- reaction_removed
+
+Next, click on "OAuth & Permissions" and add the following scopes:
+
+- chat:write:bot
+- users:read
+- reactions:write
+- files:write:user (if you want to bridge files)
+
+**Note**: In order to make Slack files visible to Matrix users, this bridge will make Slack files visible to anyone with the url (including files in private channels). This is different than the current behavior in Slack, which only allows authenticated access to media posted in private channels. See MSC701 for details.
+
+Click on "Install App" and "Install App to Workspace". Note the access tokens shown. You will need the Bot User OAuth Access Token and if you want to bridge files, the OAuth Access Token whenever you link a room.
+
+### Create an administration control room on Matrix
+
+Create a new Matrix room to act as the administration control room.
+
+Note its internal room ID. This can be done in Element Web by sending a message, opening the options for that message and choosing "view source". The room ID will be displayed near the top.
+
+## Adjusting the playbook configuration
+
+To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+
+```yaml
+matrix_appservice_slack_enabled: true
+matrix_appservice_slack_control_room_id: "Your Matrix admin room ID"
+
+# Uncomment to enable puppeting (optional, but recommended)
+# matrix_appservice_slack_puppeting_enabled: true
+# matrix_appservice_slack_puppeting_slackapp_client_id: "Your Classic Slack App Client ID"
+# matrix_appservice_slack_puppeting_slackapp_client_secret: "Your Classic Slack App Client Secret"
+
+# Uncomment to enable Team Sync (optional)
+# See https://matrix-appservice-slack.readthedocs.io/en/latest/team_sync/
+# matrix_appservice_slack_team_sync_enabled: true
 ```
+
+### Extending the configuration
+
+There are some additional things you may wish to configure about the bridge.
+
+Take a look at:
+
+- `roles/custom/matrix-bridge-appservice-slack/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `roles/custom/matrix-bridge-appservice-slack/templates/config.yaml.j2` for the bridge's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_appservice_slack_configuration_extension_yaml` variable
+
+For example, to change the bot's username from `slackbot`, add the following configuration to your `vars.yml` file. Replace `examplebot` with your own.
+
+```yaml
+matrix_appservice_slack_configuration_extension_yaml: |
+  bot_username: "examplebot"
+```
+
+## Installing
+
+After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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. Note these shortcuts run the `ensure-matrix-users-created` tag too.
+
+## Usage
+
+To use the bridge, you need to send `/invite @slackbot:example.com` to invite the bridge bot user into the admin room.
+
+If Team Sync is not enabled, for each channel you would like to bridge, perform the following steps:
+
+- Create a Matrix room in the usual manner for your client. Take a note of its Matrix room ID — it will look something like `!qporfwt:example.com`.
+- Invite the bot user to both the Slack and Matrix channels you would like to bridge using `/invite @matrixbot` for Slack and `/invite @slackbot:example.com` for Matrix.
+- Determine the "channel ID" that Slack uses to identify the channel. You can see it when you open a given Slack channel in a browser. The URL reads like this: `https://app.slack.com/client/XXX/<the channel ID>/details/`.
+- Issue a link command in the administration control room with these collected values as arguments:
+
+    with file bridging:
+
+    ```
+    link --channel_id CHANNELID --room !qporfwt:example.com --slack_bot_token xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxxx --slack_user_token xoxp-xxxxxxxx-xxxxxxxxx-xxxxxxxx-xxxxxxxx
+    ```
+
+    without file bridging:
+
+    ```
+    link --channel_id CHANNELID --room !qporfwt:example.com --slack_bot_token xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxxx
+    ```
+
+    These arguments can be shortened to single-letter forms:
+
+    ```
+    link -I CHANNELID -R !qporfwt:example.com -t xoxb-xxxxxxxxxx-xxxxxxxxxxxxxxxxxxxx
+    ```
+
+### Unlinking
+
+Channels can be unlinked again by sending this:
+
+```
+unlink --room !qporfwt:example.com
+```
+
+Unlinking doesn't only disconnect the bridge, but also makes the slackbot leave the bridged Matrix room. So in case you want to re-link later, don't forget to re-invite the slackbot into this room again.
+
+## Troubleshooting
+
+As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-appservice-slack`.
+
+### Linking: "Room is now pending-name"
+
+This typically means that you haven't used the correct Slack channel ID. Unlink the room and recheck 'Determine the "channel ID"' from above.
+
+### Messages work from Matrix to Slack, but not the other way around
+
+Check the logs, and if you find the message like below, unlink your room, reinvite the bot and re-link it again.
+
+`WARN SlackEventHandler Ignoring message from unrecognised Slack channel ID : %s (%s) <the channel ID> <some other ID>`
+
+This may particularly hit you, if you tried to unsuccessfully link your room multiple times without unlinking it after each failed attempt.

docs/configuring-playbook-bridge-mautrix-discord.md

@@ -1,11 +1,11 @@
 <!--
+SPDX-FileCopyrightText: 2018 - 2024 Slavi Pantaleev
 SPDX-FileCopyrightText: 2018 Hugues Morisset
-SPDX-FileCopyrightText: 2018-2024 Slavi Pantaleev
+SPDX-FileCopyrightText: 2021 - 2022 MDAD project contributors
-SPDX-FileCopyrightText: 2021, 2022 MDAD project contributors
 SPDX-FileCopyrightText: 2022 Abílio Costa
 SPDX-FileCopyrightText: 2022 Dennis Ciba
 SPDX-FileCopyrightText: 2022 Marko Weltzer
-SPDX-FileCopyrightText: 2024-2026 Suguru Hirahara
+SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara
 
 SPDX-License-Identifier: AGPL-3.0-or-later
 -->
@@ -15,6 +15,8 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 <sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
 
 **Note**: bridging to [Discord](https://discordapp.com/) can also happen via the [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) bridge supported by the playbook.
+- For using as a Bot we recommend the [Appservice Discord](configuring-playbook-bridge-appservice-discord.md), because it supports plumbing.
+- For personal use with a discord account we recommend the `mautrix-discord` bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Discord bridges supported by the playbook.
 
 The playbook can install and configure [mautrix-discord](https://github.com/mautrix/discord) for you.
 
@@ -22,9 +24,9 @@ See the project's [documentation](https://docs.mau.fi/bridges/go/discord/index.h
 
 ## Prerequisites
 
-There are 3 ways to login to discord using this bridge, either by [scanning a QR code](https://docs.mau.fi/bridges/go/discord/authentication.html#qr-login) using the Discord mobile app, by using a [Discord token](https://docs.mau.fi/bridges/go/discord/authentication.html#token-login), **or** by using a [Discord bot token](https://docs.mau.fi/bridges/go/discord/authentication.html#bot-token-login).
+There are 2 ways to login to discord using this bridge, either by [scanning a QR code](#method-1-login-using-qr-code-recommended) using the Discord mobile app **or** by using a [Discord token](#method-2-login-using-discord-token-not-recommended).
 
-⚠️ QR code login is considered a self-bot and is forbidden by Discord. It can result in an account termination. See the [Discord policy](https://support.discord.com/hc/en-us/articles/115002192352-Automated-User-Accounts-Self-Bots).
+If this is a dealbreaker for you, consider using [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md). This comes with its own complexity and limitations, however, so we recommend that you proceed with this one if possible.
 
 ### Enable Appservice Double Puppet or Shared Secret Auth (optional)
 
@@ -78,14 +80,6 @@ After bridging, spaces will be created automatically, and rooms will be created
 
 If you want to manually bridge channels, invite the bot to the room you want to bridge, and run `!discord bridge CHANNEL_ID_HERE` to bridge the room. Make sure to replace `CHANNEL_ID_HERE` with the channel's ID.
 
-### Enable relay
-
-The bridge supports using Discord's webhook feature to relay messages from Matrix users who haven't logged into the bridge.
-
-In a room that has already been bridged, run `!discord set-relay --create`. The bridge will then create a webhook in the bridged discord channel and begin relaying messages. If the discord user does not have access to manage webhooks, run `!discord set-relay --url <url>` with the url of an already created webhook. (See Discords [Intro to webhooks](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks))
-
-More information on relaying is available on the [official documentation](https://docs.mau.fi/bridges/go/discord/relay.html).
-
 ## Troubleshooting
 
 As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-mautrix-discord`.
@@ -98,7 +92,3 @@ The default logging level for this component is `warn`. If you want to increase
 # Valid values: fatal, error, warn, info, debug, trace
 matrix_mautrix_discord_logging_level: 'debug'
 ```
-
-### Command requires room admin rights when user is creator
-
-[MSC4289](https://github.com/matrix-org/matrix-spec-proposals/blob/main/proposals/4289-privilege-creators.md), introduced in [room version 12](https://spec.matrix.org/unstable/rooms/v12/), gives creators an infinitley high powerlevel. At the time of implementation, mautrix-discord and similar applications may not identify creators as or above admins. Either a separate admin user will need to manage the bridge or the room version should be less than version 12.

docs/configuring-playbook-bridge-mautrix-slack.md

@@ -11,6 +11,10 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
 <sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>
 
+**Note**: bridging to [Slack](https://slack.com/) can also happen via the [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) bridge supported by the playbook.
+- For using as a Bot we recommend the [Appservice Slack](configuring-playbook-bridge-appservice-slack.md), because it supports plumbing. Note that it is not available for new installation unless you have already created a classic Slack application, because the creation of classic Slack applications, which this bridge makes use of, has been discontinued.
+- For personal use with a slack account we recommend the `mautrix-slack` bridge (the one being discussed here), because it is the most fully-featured and stable of the 3 Slack bridges supported by the playbook.
+
 The playbook can install and configure [mautrix-slack](https://github.com/mautrix/slack) for you.
 
 See the project's [documentation](https://docs.mau.fi/bridges/go/slack/index.html) to learn what it does and why it might be useful to you.
@@ -21,7 +25,7 @@ See the [features and roadmap](https://github.com/mautrix/slack/blob/main/ROADMA
 
 For using this bridge, you would need to authenticate by **providing your username and password** (legacy) or by using a **token login**. See more information in the [docs](https://docs.mau.fi/bridges/go/slack/authentication.html).
 
-Note that neither of these methods are officially supported by Slack.
+Note that neither of these methods are officially supported by Slack. [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) uses a Slack bot account which is the only officially supported method for bridging a Slack channel.
 
 ### Enable Appservice Double Puppet (optional)
 

docs/configuring-playbook-bridge-postmoogle.md

@@ -87,7 +87,7 @@ ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,ensure-matrix-use
 
   `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.
 
-- If you change the bridge's bot password (`matrix_postmoogle_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_postmoogle_password` to let the bot know its new password.
+- If you change the bridge's bot password (`matrix_postmoogle_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password.
 
 ## Usage
 

docs/configuring-playbook-client-hydrogen.md

@@ -24,22 +24,22 @@ When setting, replace `example.com` with your own.
 To enable Hydrogen, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
 
 ```yaml
-hydrogen_enabled: true
+matrix_client_hydrogen_enabled: true
 ```
 
 ### Adjusting the Hydrogen URL (optional)
 
-By tweaking the `hydrogen_hostname` and `hydrogen_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
+By tweaking the `matrix_client_hydrogen_hostname` and `matrix_client_hydrogen_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
 
 Example additional configuration for your `vars.yml` file:
 
 ```yaml
 # Switch to the domain used for Matrix services (`matrix.example.com`),
 # so we won't need to add additional DNS records for Hydrogen.
-hydrogen_hostname: "{{ matrix_server_fqn_matrix }}"
+matrix_client_hydrogen_hostname: "{{ matrix_server_fqn_matrix }}"
 
 # Expose under the /hydrogen subpath
-hydrogen_path_prefix: /hydrogen
+matrix_client_hydrogen_path_prefix: /hydrogen
 ```
 
 After changing the domain, **you may need to adjust your DNS** records to point the Hydrogen domain to the Matrix server.
@@ -52,8 +52,8 @@ There are some additional things you may wish to configure about the client.
 
 Take a look at:
 
-- `roles/galaxy/hydrogen/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `roles/custom/matrix-client-hydrogen/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
-- `roles/galaxy/hydrogen/templates/config.json.j2` for the client's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `hydrogen_configuration_extension_json` variable
+- `roles/custom/matrix-client-hydrogen/templates/config.json.j2` for the client's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_client_hydrogen_configuration_extension_json` variable
 
 ## Installing
 

docs/configuring-playbook-client-sable.md

@@ -1,71 +0,0 @@
-<!--
-SPDX-FileCopyrightText: 2022 MDAD project contributors
-SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara
-SPDX-FileCopyrightText: 2024 - 2026 Slavi Pantaleev
-
-SPDX-License-Identifier: AGPL-3.0-or-later
--->
-
-# Setting up Sable (optional)
-
-The playbook can install and configure the [Sable](https://github.com/7w1/sable) Matrix web client for you.
-
-Sable is a web client focusing primarily on simple, elegant and secure interface. It can be installed alongside or instead of [Element Web](./configuring-playbook-client-element-web.md), [Cinny](./configuring-playbook-client-cinny.md) and others.
-
-## Adjusting DNS records
-
-By default, this playbook installs Sable on the `sable.` subdomain (`sable.example.com`) and requires you to create a CNAME record for `sable`, which targets `matrix.example.com`.
-
-When setting, replace `example.com` with your own.
-
-## Adjusting the playbook configuration
-
-To enable Sable, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
-
-```yaml
-sable_enabled: true
-```
-
-### Adjusting the Sable URL (optional)
-
-By tweaking the `sable_hostname` variable, you can easily make the service available at a **different hostname** than the default one.
-
-Example additional configuration for your `vars.yml` file:
-
-```yaml
-# Switch to a different domain (`app.example.com`) than the default one (`sable.example.com`)
-sable_hostname: "app.{{ matrix_domain }}"
-
-# Expose under the /sable subpath
-# sable_path_prefix: /sable
-```
-
-After changing the domain, **you may need to adjust your DNS** records to point the Sable domain to the Matrix server.
-
-**Note**: while there is a `sable_path_prefix` variable for changing the path where Sable is served, overriding it is [not possible](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3701), because Sable requires an application rebuild (with a tweaked build config) to be functional under a custom path. You'd need to serve Sable at a dedicated subdomain.
-
-### Extending the configuration
-
-There are some additional things you may wish to configure about the component.
-
-Take a look at:
-
-- `roles/galaxy/sable/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
-- `roles/galaxy/sable/templates/config.json.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `sable_configuration_extension_json` variable
-
-## Installing
-
-After configuring the playbook and [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
-
-<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
-```sh
-ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
-```
-
-The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
-
-`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. Note these shortcuts run the `ensure-matrix-users-created` tag too.
-
-## Troubleshooting
-
-As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-client-sable`.

docs/configuring-playbook-conduit.md

@@ -13,6 +13,8 @@ See the project's [documentation](https://docs.conduit.rs/) to learn what it doe
 
 By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document.
 
+💡 **Note**: The playbook also supports installing a (currently) faster-moving Conduit fork called [conduwuit](./configuring-playbook-conduwuit.md).
+
 > [!WARNING]
 > - **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Conduit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet.
 > - **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding

docs/configuring-playbook-conduwuit.md

@@ -1,45 +1,106 @@
 <!--
-SPDX-FileCopyrightText: 2019 Eduardo Beltrame
+SPDX-FileCopyrightText: 2025 Slavi Pantaleev
-SPDX-FileCopyrightText: 2019-2025 Slavi Pantaleev
+SPDX-FileCopyrightText: 2025 Suguru Hirahara
-SPDX-FileCopyrightText: 2020 Tulir Asokan
-SPDX-FileCopyrightText: 2021, 2024 MDAD project contributors
-SPDX-FileCopyrightText: 2022 Dennis Ciba
-SPDX-FileCopyrightText: 2022 Vladimir Panteleev
-SPDX-FileCopyrightText: 2023 Justin Croonenberghs
-SPDX-FileCopyrightText: 2023 Kuba Orlik
-SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty
-SPDX-FileCopyrightText: 2023 Samuel Meenzen
-SPDX-FileCopyrightText: 2024 Fabio Bonelli
-SPDX-FileCopyrightText: 2024-2026 Suguru Hirahara
 
 SPDX-License-Identifier: AGPL-3.0-or-later
 -->
 
-# Configuring conduwuit (optional, removed)
+# Configuring conduwuit (optional)
 
-🪦 The playbook used to be able to install and configure the [conduwuit](https://conduwuit.puppyirl.gay/) Matrix server, but no longer includes this component, as it's been abandoned and unmaintained.
+The playbook can install and configure the [conduwuit](https://conduwuit.puppyirl.gay/) Matrix server for you.
 
-## Uninstalling the service manually
+See the project's [documentation](https://conduwuit.puppyirl.gay/) to learn what it does and why it might be useful to you.
 
-If you still have conduwuit installed on your Matrix server, the playbook can no longer help you uninstall it and you will need to do it manually.
+By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document.
 
-To uninstall the service, run the command below on the server:
+💡 **Note**: conduwuit is a fork of [Conduit](./configuring-playbook-conduit.md), which the playbook also supports. See [Differences from upstream Conduit](https://conduwuit.puppyirl.gay/differences.html).
 
-```sh
+> [!WARNING]
-systemctl disable --now matrix-conduwuit.service
+> - **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> conduwuit). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet.
+> - **Homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding
+> - **the Conduwuit project appears to have been abandoned**. You may wish to install [Conduit](./configuring-playbook-conduit.md), or one of the Conduwuit successors (like [Continuwuity](configuring-playbook-continuwuity.md))
+
+## Adjusting the playbook configuration
+
+To use conduwuit, you **generally** need to adjust the `matrix_homeserver_implementation: synapse` configuration on your `inventory/host_vars/matrix.example.com/vars.yml` file as below:
+
+```yaml
+matrix_homeserver_implementation: conduwuit
+
+# Registering users can only happen via the API,
+# so it makes sense to enable it, at least initially.
+matrix_conduwuit_config_allow_registration: true
+
+# Generate a strong registration token to protect the registration endpoint from abuse.
+# You can create one with a command like `pwgen -s 64 1`.
+matrix_conduwuit_config_registration_token: ''
 ```
 
-## Migrating to Continuwuity
+### Extending the configuration
 
-Since [Continuwuity](configuring-playbook-continuwuity.md) is a drop-in replacement for conduwuit, migration is possible. Please refer to [this section](./configuring-playbook-continuwuity.md#migrating-from-conduwuit) for details.
+There are some additional things you may wish to configure about the server.
 
-## Removing data manually
+Take a look at:
 
-If you are not going to migrate to [Continuwuity](configuring-playbook-continuwuity.md), you can remove data by running the command on the server:
+- `roles/custom/matrix-conduwuit/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `roles/custom/matrix-conduwuit/templates/conduwuit.toml.j2` for the server's default configuration
 
-```sh
+There are various Ansible variables that control settings in the `conduwuit.toml` file.
-rm -rf /matrix/conduwuit
+
+If a specific setting you'd like to change does not have a dedicated Ansible variable, you can either submit a PR to us to add it, or you can [override the setting using an environment variable](https://conduwuit.puppyirl.gay/configuration.html#environment-variables) using `matrix_conduwuit_environment_variables_extension`. For example:
+
+```yaml
+matrix_conduwuit_environment_variables_extension: |
+  CONDUWUIT_MAX_REQUEST_SIZE=50000000
+  CONDUWUIT_REQUEST_TIMEOUT=60
 ```
 
->[!WARNING]
+## Creating the first user account
-> Once you removing the path, there is no going back. Your data on the homeserver (including chat history, rooms, etc.) will be deleted and not be possible to restore them. Please be certain.
+
+Unlike other homeserver implementations (like Synapse and Dendrite), conduwuit does not support creating users via the command line or via the playbook.
+
+If you followed the instructions above (see [Adjusting the playbook configuration](#adjusting-the-playbook-configuration)), you should have registration enabled and protected by a registration token.
+
+This should allow you to create the first user account via any client (like [Element Web](./configuring-playbook-client-element-web.md)) which supports creating users.
+
+The **first user account that you create will be marked as an admin** and **will be automatically invited to an admin room**.
+
+
+## Configuring bridges / appservices
+
+For other homeserver implementations (like Synapse and Dendrite), the playbook automatically registers appservices (for bridges, bots, etc.) with the homeserver.
+
+For conduwuit, you will have to manually register appservices using the [`!admin appservices register` command](https://conduwuit.puppyirl.gay/appservices.html#set-up-the-appservice---general-instructions) sent to the server bot account.
+
+The server's bot account has a Matrix ID of `@conduit:example.com` (not `@conduwuit:example.com`!) due to conduwuit's historical legacy.
+Your first user account would already have been invited to an admin room with this bot.
+
+Find the appservice file you'd like to register. This can be any `registration.yaml` file found in the `/matrix` directory, for example `/matrix/mautrix-signal/bridge/registration.yaml`.
+
+Then, send its content to the existing admin room:
+
+    !admin appservices register
+
+    ```
+    as_token: <token>
+    de.sorunome.msc2409.push_ephemeral: true
+    receive_ephemeral: true
+    hs_token: <token>
+    id: signal
+    namespaces:
+      aliases:
+      - exclusive: true
+        regex: ^#signal_.+:example\.org$
+      users:
+      - exclusive: true
+        regex: ^@signal_.+:example\.org$
+      - exclusive: true
+        regex: ^@signalbot:example\.org$
+    rate_limited: false
+    sender_localpart: _bot_signalbot
+    url: http://matrix-mautrix-signal:29328
+    ```
+
+## Troubleshooting
+
+As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-conduwuit`.

docs/configuring-playbook-continuwuity.md

@@ -13,7 +13,7 @@ See the project's [documentation](https://continuwuity.org) to learn what it doe
 
 By default, the playbook installs [Synapse](https://github.com/element-hq/synapse) as it's the only full-featured Matrix server at the moment. If that's okay, you can skip this document.
 
-💡 **Note**: continuwuity is a fork of [conduwuit](./configuring-playbook-conduwuit.md), which the playbook has supported.
+💡 **Note**: continuwuity is a fork of [conduwuit](./configuring-playbook-conduwuit.md), which the playbook also supports.
 
 > [!WARNING]
 > - **You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Continuwuity). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet.
@@ -58,14 +58,9 @@ matrix_continuwuity_environment_variables_extension: |
 
 Unlike other homeserver implementations (like Synapse and Dendrite), continuwuity does not support creating users via the command line or via the playbook.
 
-On first startup, Continuwuity creates a special one-time-use registration token and logs it to the server's console. To access this, you will need to SSH into the server and run the following command:
+If you followed the instructions above (see [Adjusting the playbook configuration](#adjusting-the-playbook-configuration)), you should have registration enabled and protected by a registration token.
 
-```sh
+This should allow you to create the first user account via any client (like [Element Web](./configuring-playbook-client-element-web.md)) which supports creating users.
-# Adjust the duration if necessary or remove the whole --since argument
-journalctl -u matrix-continuwuity.service --since="10 minutes ago"
-```
-
-Find the token, highlight it, and copy it (ctrl+shift+C). This token should allow you to create the first user account via any client (like [Element Web](./configuring-playbook-client-element-web.md)) which supports creating users.
 
 The **first user account that you create will be marked as an admin** and **will be automatically invited to an admin room**.
 

docs/configuring-playbook-dimension.md

@@ -1,33 +1,144 @@
 <!--
+SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev
+SPDX-FileCopyrightText: 2019 - 2025 MDAD project contributors
 SPDX-FileCopyrightText: 2019 Edgars Voroboks
-SPDX-FileCopyrightText: 2019 Eduardo Beltrame
-SPDX-FileCopyrightText: 2019-2025 MDAD project contributors
-SPDX-FileCopyrightText: 2019-2025 Slavi Pantaleev
 SPDX-FileCopyrightText: 2020 Chris van Dijk
-SPDX-FileCopyrightText: 2020 Tulir Asokan
 SPDX-FileCopyrightText: 2020 jens quade
 SPDX-FileCopyrightText: 2022 Dennis Ciba
 SPDX-FileCopyrightText: 2022 Kim Brose
 SPDX-FileCopyrightText: 2022 Travis Ralston
-SPDX-FileCopyrightText: 2022 Vladimir Panteleev
 SPDX-FileCopyrightText: 2022 Yan Minagawa
-SPDX-FileCopyrightText: 2024-2026 Suguru Hirahara
+SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara
 
 SPDX-License-Identifier: AGPL-3.0-or-later
 -->
 
-# Setting up Dimension integration manager (optional, removed)
+# Setting up Dimension integration manager (optional, unmaintained)
 
-🪦 The playbook used to be able to install and configure [Dimension](https://dimension.t2bot.io) integration manager, but no longer includes this component, as it has been unmaintained.
+**Notes**:
+- Dimension is **[officially unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299)**. We recommend not bothering with installing it.
+- This playbook now supports running Dimension in both a federated and [unfederated](https://github.com/turt2live/matrix-dimension/blob/master/docs/unfederated.md) environments. This is handled automatically based on the value of `matrix_homeserver_federation_enabled`.
 
-## Uninstalling the component manually
+The playbook can install and configure the [Dimension](https://dimension.t2bot.io) integration manager for you.
 
-If you still have the Dimension integration manager installed on your Matrix server, the playbook can no longer help you uninstall it and you will need to do it manually. To uninstall manually, run these commands on the server:
+See the project's [documentation](https://github.com/turt2live/matrix-dimension/blob/master/README.md) to learn what it does and why it might be useful to you.
+
+## Prerequisites
+
+### Open Matrix Federation port
+
+Enabling the Dimension service will automatically reconfigure your Synapse homeserver to expose the `openid` API endpoints on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. If you enable the component, make sure that the port is accessible.
+
+### Install Matrix services
+
+Dimension can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later.
+
+### Register a dedicated Matrix user (optional, recommended)
+
+We recommend that you create a dedicated Matrix user for Dimension (`dimension` is a good username).
+
+Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`.
+
+You can use the playbook to [register a new user](registering-users.md):
 
 ```sh
-systemctl disable --now matrix-dimension.service
+ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=dimension password=PASSWORD_FOR_THE_USER admin=no' --tags=register-user
-
-rm -rf /matrix/dimension
-
-/matrix/postgres/bin/cli-non-interactive -c 'DROP DATABASE matrix_dimension;'
 ```
+
+### Obtain an access token
+
+Dimension requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md).
+
+> [!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.
+
+## Adjusting DNS records
+
+By default, this playbook installs Dimension on the `dimension.` subdomain (`dimension.example.com`) and requires you to create a CNAME record for `dimension`, which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
+
+## Adjusting the playbook configuration
+
+To enable Dimension, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token).
+
+```yaml
+matrix_dimension_enabled: true
+
+matrix_dimension_access_token: "ACCESS_TOKEN_HERE"
+```
+
+### Define admin users
+
+To define admin users who can modify the integrations this Dimension supports, add the following configuration to your `vars.yml` file:
+
+```yaml
+matrix_dimension_admins:
+  - "@alice:{{ matrix_domain }}"
+  - "@bob:{{ matrix_domain }}"
+```
+
+The admin interface is accessible within Element Web by accessing it in any room and clicking the cog wheel/settings icon in the top right. Currently, Dimension can be opened in Element Web by the "Add widgets, bridges, & bots" link in the room information.
+
+### Adjusting the Dimension URL (optional)
+
+By tweaking the `matrix_dimension_hostname` and `matrix_dimension_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
+
+Example additional configuration for your `vars.yml` file:
+
+```yaml
+# Switch to the domain used for Matrix services (`matrix.example.com`),
+# so we won't need to add additional DNS records for Dimension.
+matrix_dimension_hostname: "{{ matrix_server_fqn_matrix }}"
+
+# Expose under the /dimension subpath
+# matrix_dimension_path_prefix: /dimension
+```
+
+After changing the domain, **you may need to adjust your DNS** records to point the Dimension domain to the Matrix server.
+
+If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration.
+
+**Note**: while there is a `matrix_dimension_path_prefix` variable for changing the path where Dimension is served, overriding it is not possible due to [this Dimension issue](https://github.com/turt2live/matrix-dimension/issues/510). You'd need to serve Dimension at a dedicated subdomain.
+
+### Extending the configuration
+
+There are some additional things you may wish to configure about the component.
+
+Take a look at:
+
+- `roles/custom/matrix-dimension/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `roles/custom/matrix-dimension/templates/config.yaml.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_dimension_configuration_extension_yaml` variable
+
+You can find all configuration options on [GitHub page of Dimension project](https://github.com/turt2live/matrix-dimension/blob/master/config/default.yaml).
+
+## Installing
+
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+**Notes**:
+
+- The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+  `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. Note these shortcuts run the `ensure-matrix-users-created` tag too.
+
+## Usage
+
+After Dimension has been installed you may need to log out and log back in for it to pick up the new integration manager. Then you can access integrations in Element Web by opening a room, clicking the room info button (`i`) on the top right corner, and then clicking the "Add widgets, bridges, & bots" link.
+
+### Set up a Jitsi widget
+
+By default Dimension will use [jitsi.riot.im](https://jitsi.riot.im/) as the `conferenceDomain` of [Jitsi](https://jitsi.org/) audio/video conference widgets. For users running [a self-hosted Jitsi instance](configuring-playbook-jitsi.md), you will likely want the widget to use your own Jitsi instance.
+
+To set up the widget, an admin user needs to configure the domain via the admin UI once Dimension is running. In Element Web, go to *Manage Integrations* → *Settings* → *Widgets* → *Jitsi Conference Settings* and set *Jitsi Domain* and *Jitsi Script URL* appropriately.
+
+There is unfortunately no way to configure the widget via the playbook. See [this issue](https://github.com/turt2live/matrix-dimension/issues/345) for details.
+
+## Troubleshooting
+
+As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-dimension`.

docs/configuring-playbook-element-admin.md

@@ -13,7 +13,7 @@ Element Admin is a web-based administration panel for Synapse and [Matrix Authen
 
 See the project's [documentation](https://github.com/element-hq/element-admin) to learn more.
 
-💡 **Note**: This project is still very young and doesn't have many features. [Ketesa](./configuring-playbook-ketesa.md) is the fully-featured alternative — it covers all Synapse and MAS Admin APIs, including complete user management, session management, and MAS policy data. Element Admin remains a valid choice if you prefer its interface.
+💡 **Note**: This project is still very young and doesn't have many features. For now, it's recommended to use [Synapse Admin](./configuring-playbook-synapse-admin.md) instead. Deployments that use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) can use Element Admin for user-management (something that Synapse Admin can't do), while continuing to use Synapse Admin for all other purposes.
 
 ## Prerequisites
 

docs/configuring-playbook-email.md

@@ -17,16 +17,6 @@ The [Ansible role for exim-relay](https://github.com/mother-of-all-self-hosting/
 - 🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-exim-relay/blob/main/docs/configuring-exim-relay.md) online
 - 📁 `roles/galaxy/exim_relay/docs/configuring-exim-relay.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)
 
-## Why use exim-relay?
-
-**Benefits of using exim-relay** instead of configuring SMTP directly in each service:
-
-1. **Final delivery capability**: Can deliver emails directly if you don't have an SMTP server
-
-2. **Centralized configuration**: Configure your upstream SMTP server once in exim-relay, then point all services ([Synapse](configuring-playbook-synapse.md), [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), etc.) there—no need to configure SMTP in each component
-
-3. **Local spooling**: Stores messages locally and retries delivery if your upstream SMTP server is temporarily unavailable
-
 ## Firewall settings
 
 No matter whether you send email directly (the default) or you relay email through another host, you'll probably need to allow outgoing traffic for TCP ports 25/587 (depending on configuration).

docs/configuring-playbook-federation.md

@@ -44,7 +44,7 @@ matrix_homeserver_federation_enabled: false
 
 With that, your server's users will only be able to talk among themselves, but not to anyone who is on another server.
 
-**Disabling federation does not necessarily disable the federation port** (`8448`). Even if you disable federation and only if necessary, we may still be exposing the federation port and serving the `openid` APIs there. To override this and completely disable Synapse's federation port use:
+**Disabling federation does not necessarily disable the federation port** (`8448`). Services like [Dimension](configuring-playbook-dimension.md) normally rely on `openid` APIs exposed on that port. Even if you disable federation and only if necessary, we may still be exposing the federation port and serving the `openid` APIs there. To override this and completely disable Synapse's federation port use:
 
 ```yaml
 matrix_homeserver_federation_enabled: false

docs/configuring-playbook-jitsi.md

@@ -18,9 +18,6 @@ SPDX-License-Identifier: AGPL-3.0-or-later
 
 The playbook can install and configure the [Jitsi](https://jitsi.org/) video-conferencing platform for you.
 
-Because Jitsi still requires a TURN server, enabling Jitsi
-automatically enables coturn (`coturn_enabled: true`) unless you explicitly disable it.
-
 Jitsi is an open source video-conferencing platform. It can not only be integrated with Element clients ([Element Web](configuring-playbook-client-element-web.md)/Desktop, Android and iOS) as a widget, but also be used as standalone web app.
 
 💡 If you're into experimental technology, you may also be interested in trying out [Element Call](configuring-playbook-element-call.md) - a native Matrix video conferencing application.

docs/configuring-playbook-ketesa.md

@@ -1,100 +0,0 @@
-<!--
-SPDX-FileCopyrightText: 2020-2024 MDAD project contributors
-SPDX-FileCopyrightText: 2020-2024 Slavi Pantaleev
-SPDX-FileCopyrightText: 2021 Aaron Raimist
-SPDX-FileCopyrightText: 2023 Christian González
-SPDX-FileCopyrightText: 2024 Nikita Chernyi
-SPDX-FileCopyrightText: 2024 Uğur İLTER
-SPDX-FileCopyrightText: 2024-2026 Suguru Hirahara
-SPDX-FileCopyrightText: 2026 Nikita Chernyi
-
-SPDX-License-Identifier: AGPL-3.0-or-later
--->
-
-# Setting up Ketesa (optional)
-
-The playbook can install and configure [Ketesa](https://github.com/etkecc/ketesa) for you.
-
-Ketesa is a fully-featured admin interface for Matrix homeservers — manage users, rooms, media, sessions, and more from one clean, responsive web UI. It is the evolution of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin): what began as a fork has grown into its own independent project with a redesigned interface, comprehensive Synapse and MAS API coverage, and multi-language support. See the [Ketesa v1.0.0 announcement](https://etke.cc/blog/introducing-ketesa/) for a full overview of what's new.
-
->[!NOTE]
->
-> - Ketesa does not work with other homeserver implementations than Synapse due to API's incompatibility.
-> - The latest version of Ketesa is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting.
-> - This playbook also supports an alternative management UI in the shape of [Element Admin](./configuring-playbook-element-admin.md). Please note that it's currently less feature-rich than Ketesa and requires [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md).
-
-## Adjusting DNS records (optional)
-
-By default, this playbook installs Ketesa on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin) — the legacy path is kept for backward compatibility. This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section.
-
-If you wish to adjust it, see the section [below](#adjusting-the-ketesa-url-optional) for details about DNS configuration.
-
-## Adjusting the playbook configuration
-
-To enable Ketesa, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
-
-```yaml
-matrix_ketesa_enabled: true
-```
-
-**Note**: Ketesa requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Ketesa needs these APIs to function, when installing Ketesa, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:
-
-- for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`
-- for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`
-
-By default, Ketesa installation will be [restricted to only work with one homeserver](https://github.com/etkecc/ketesa/blob/main/README.md#restricting-available-homeserver) — the one managed by the playbook. To adjust these restrictions, tweak the `matrix_ketesa_config_restrictBaseUrl` variable.
-
-### Adjusting the Ketesa URL (optional)
-
-By tweaking the `matrix_ketesa_hostname` and `matrix_ketesa_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
-
-We recommend updating the path prefix to `/ketesa` to align with the new branding, while the default `/synapse-admin` is kept for backward compatibility:
-
-```yaml
-matrix_ketesa_path_prefix: /ketesa
-```
-
-Or to change the hostname entirely:
-
-```yaml
-# Change the default hostname and path prefix
-matrix_ketesa_hostname: admin.example.com
-matrix_ketesa_path_prefix: /
-```
-
-If you've changed the default hostname, you may need to create a CNAME record for the Ketesa domain (`admin.example.com`), which targets `matrix.example.com`.
-
-When setting, replace `example.com` with your own.
-
-### Extending the configuration
-
-There are some additional things you may wish to configure about the component.
-
-Take a look at:
-
-- `roles/custom/matrix-ketesa/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_ketesa_configuration_extension_json` variable
-
-## Installing
-
-After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
-
-<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
-```sh
-ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
-```
-
-The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
-
-`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. Note these shortcuts run the `ensure-matrix-users-created` tag too.
-
-## Usage
-
-After installation, Ketesa will be accessible at: `https://matrix.example.com/synapse-admin/` (or `/ketesa/` if you updated the path prefix as recommended)
-
-To use Ketesa, you need to have [registered at least one administrator account](registering-users.md) on your server.
-
-## Troubleshooting
-
-As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-ketesa`.
-
-If you have questions, you can join this community room and feel free to ask: [#ketesa:etke.cc](https://matrix.to/#/#ketesa:etke.cc)

docs/configuring-playbook-livekit-server.md

@@ -15,7 +15,7 @@ LiveKit Server is an open source project that provides scalable, multi-user conf
 
 The [Ansible role for LiveKit Server](https://github.com/mother-of-all-self-hosting/ansible-role-livekit-server) is developed and maintained by [the MASH (mother-of-all-self-hosting) project](https://github.com/mother-of-all-self-hosting). For details about configuring LiveKit Server, you can check them via:
 - 🌐 [the role's documentation at the MASH project](https://github.com/mother-of-all-self-hosting/ansible-role-livekit-server/blob/main/docs/configuring-livekit-server.md) online
-- 📁 `roles/galaxy/livekit_server/docs/configuring-livekit-server.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)
+- 📁 `roles/galaxy/livekit-server/docs/configuring-livekit-server.md` locally, if you have [fetched the Ansible roles](installing.md#update-ansible-roles)
 
 ## Adjusting firewall rules
 
@@ -29,43 +29,10 @@ To ensure LiveKit Server functions correctly, the following firewall rules and p
 
 - `5350/tcp`: TURN/TCP. Also see the [Limitations](#limitations) section below.
 
-- `30000-30020/udp`: TURN relay range used by LiveKit's embedded TURN server.
+💡 The suggestions above are inspired by the upstream [Ports and Firewall](https://docs.livekit.io/home/self-hosting/ports-firewall/) documentation based on how LiveKit is configured in the playbook. If you've using custom configuration for the LiveKit Server role, you may need to adjust the firewall rules accordingly.
-
-💡 The suggestions above are inspired by the upstream [Ports and Firewall](https://docs.livekit.io/home/self-hosting/ports-firewall/) documentation based on how LiveKit is configured in the playbook. If you're using custom configuration for the LiveKit Server role, you may need to adjust firewall rules accordingly.
-
-## TURN TLS handling
-
-When `matrix_playbook_reverse_proxy_type` is `playbook-managed-traefik` (which is the default for this playbook), TURN over TCP is terminated by Traefik and forwarded to LiveKit with `turn.external_tls = true`. In this playbook default, this mode is enabled automatically when SSL is enabled and TURN is enabled.
-
-- The playbook installs a dedicated Traefik TCP entrypoint for TURN (`matrix-livekit-turn`) by default and binds it to `tcp/5350`.
-- `livekit_server_config_turn_external_tls` is automatically enabled for this setup.
-- Because Traefik handles TLS, LiveKit no longer needs certificate-file paths for TURN in this mode.
-
-To opt out and keep TURN TLS termination in LiveKit itself, set:
-
-```yml
-livekit_server_config_turn_external_tls: false
-```
-
-In this playbook, certificate paths are managed automatically via `group_vars/matrix_servers` when certificate dumping is enabled.
-
-If your setup uses `other-traefik-container` or [another reverse-proxy](./configuring-playbook-own-webserver.md), behavior is unchanged by default and still relies on certificates being available inside the container as before.
-
-Deployments using `other-traefik-container` can opt into the same Traefik-terminated mode there, by setting:
-
-```yml
-livekit_server_config_turn_external_tls: true
-livekit_server_container_labels_turn_traefik_enabled: true
-livekit_server_container_labels_turn_traefik_entrypoints: "<your-livekit-turn-traffic-entrypoint>"
-```
-
-and configuring their own Traefik TCP entrypoint dedicated to LiveKit TURN traffic.
 
 ## Limitations
 
-LiveKit Server's TURN listener behavior depends on where TLS is terminated:
+For some reason, LiveKit Server's TURN ports (`3479/udp` and `5350/tcp`) are not reachable over IPv6 regardless of whether you've [enabled IPv6](./configuring-ipv6.md) for your server.
 
-- Direct LiveKit TURN listeners (`livekit_server_config_turn_external_tls: false`) still use IPv4-only sockets for `3479/udp` and `5350/tcp`, so IPv6 connectivity to these endpoints is not possible.
+It seems like LiveKit Server intentionally only listens on `udp4` and `tcp4` as seen [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L128) and [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L92).
-- With [TURN TLS handling](#turn-tls-handling) (`livekit_server_config_turn_external_tls: true`), the playbook's dedicated `matrix-livekit-turn` TCP entrypoint can still listen on both IPv4 and IPv6. Traefik then forwards TURN/TCP to LiveKit.
-
-It appears that LiveKit Server intentionally only listens on `udp4` and `tcp4` in direct mode, as seen [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L128) and [here](https://github.com/livekit/livekit/blob/154b4d26b769c68a03c096124094b97bf61a996f/pkg/service/turn.go#L92).

docs/configuring-playbook-matrix-authentication-service.md

@@ -51,7 +51,7 @@ This section details what you can expect when switching to the Matrix Authentica
 
 - ❌ **Synapse password providers will need to be disabled**. You can no longer use [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc. When the authentication flow is handled by MAS (not by Synapse anymore), it doesn't make sense to extend the Synapse authentication flow with additional modules. Many bridges used to rely on shared-secret-auth for doing double-puppeting (impersonating other users), but most (at least the mautrix bridges) nowadays use [Appservice Double Puppet](./configuring-playbook-appservice-double-puppet.md) as a better alternative. Older/maintained bridges may still rely on shared-secret-auth, as do other services like [matrix-corporal](./configuring-playbook-matrix-corporal.md).
 
-- ✅ **[Ketesa](./configuring-playbook-ketesa.md) has full MAS integration**. Ketesa supports OIDC auth, user management, all session types (browser, OAuth2, compatibility), linked email addresses, upstream OAuth provider links, MAS policy data, and user creation through MAS. It is the recommended tool for managing homeservers running MAS.
+- ❌ Certain **tools like [Synapse Admin](./configuring-playbook-synapse-admin.md) do not have full compatibility with MAS yet**. Synapse Admin already supports OIDC auth, browsing users (which Synapse will internally fetch from MAS) and updating user avatars. However, editing users (passwords, etc.) now needs to happen directly against MAS using the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html), which Synapse Admin cannot interact with yet. You may be interested in using [Element Admin](./configuring-playbook-element-admin.md) for these purposes.
 
 - ❌ **Some services experience issues when authenticating via MAS**:
 
@@ -398,8 +398,6 @@ To perform a real migration, run the `matrix-authentication-service-mas-cli-syn2
 just run-tags matrix-authentication-service-mas-cli-syn2mas
 ```
 
-After `syn2mas` completes, Synapse will intentionally remain stopped to avoid new registrations or other authentication changes from being accepted before the migration is completed. Continue with the next steps in this guide before re-running the installation.
-
 Having performed a `syn2mas` migration once, trying to do it again will report errors (e.g. "Error: The MAS database is not empty: rows found in at least `users`. Please drop and recreate the database, then try again.").
 
 ## Verify that Matrix Authentication Service is installed correctly

docs/configuring-playbook-matrix-media-repo.md

@@ -24,21 +24,8 @@ To enable matrix-media-repo, add the following configuration to your `inventory/
 
 ```yaml
 matrix_media_repo_enabled: true
-
-# Any unique alphanumeric string. Cannot be changed after first use.
-# For new installations, generate one with: pwgen -s 64 1
-# For existing installations, see below.
-matrix_media_repo_datastore_file_id: "CHANGE_ME_TO_A_UNIQUE_VALUE"
 ```
 
-**For existing installations**: retrieve the current datastore ID from the server's config file before proceeding:
-
-```sh
-grep 'id:' /matrix/media-repo/config/media-repo.yaml
-```
-
-Then use that value for `matrix_media_repo_datastore_file_id`. This is not a secret — it is a plain identifier used by matrix-media-repo to link media files to their storage backend.
-
 By default, the media-repo will use the local filesystem for data storage. You can alternatively use a `s3` cloud backend as well. Access token caching is also enabled by default since the logout endpoints are proxied through the media repo.
 
 ### Enable metrics
@@ -122,11 +109,6 @@ matrix_media_repo_admins: []
 matrix_media_repo_datastore_file_for_kinds: ["thumbnails", "remote_media", "local_media", "archives"]
 matrix_media_repo_datastore_s3_for_kinds: []
 
-# Required when S3 storage is enabled (matrix_media_repo_datastore_s3_for_kinds is non-empty).
-# Any unique alphanumeric string. Cannot be changed after first use.
-# For new installations, generate one with: pwgen -s 64 1
-# matrix_media_repo_datastore_s3_id: ""
-
 # The s3 uploader needs a temporary location to buffer files to reduce memory usage on
 # small file uploads. If the file size is unknown, the file is written to this location
 # before being uploaded to s3 (then the file is deleted). If you aren't concerned about

docs/configuring-playbook-matrix-rtc.md

@@ -17,8 +17,8 @@ The Matrix RTC stack is a set of supporting components ([LiveKit Server](configu
 
 - A [Synapse](configuring-playbook-synapse.md) homeserver (see the warning below)
 - Various experimental features for the Synapse homeserver which Element Call [requires](https://github.com/element-hq/element-call/blob/93ae2aed9841e0b066d515c56bd4c122d2b591b2/docs/self-hosting.md#a-matrix-homeserver) (automatically done when Element Call is enabled)
-- A [LiveKit Server](configuring-playbook-livekit-server.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack))
+- A [LiveKit Server](configuring-playbook-livekit-server.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](#decide-between-element-call-vs-just-the-matrix-rtc-stack))
-- The [LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](configuring-playbook-element-call.md#decide-between-element-call-vs-just-the-matrix-rtc-stack))
+- The [LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md) (automatically installed when [Element Call or the Matrix RTC stack is enabled](#decide-between-element-call-vs-just-the-matrix-rtc-stack))
 - A client compatible with Element Call. As of 2025-03-15, that's just [Element Web](configuring-playbook-client-element-web.md) and the Element X mobile clients (iOS and Android).
 
 > [!WARNING]

docs/configuring-playbook-prometheus-grafana.md

@@ -83,7 +83,7 @@ See the project's [documentation](https://github.com/martin-helmich/prometheus-n
 To enable it, add the following configuration to your `vars.yml` file:
 
 ```yaml
-prometheus_nginxlog_exporter_enabled: true
+matrix_prometheus_nginxlog_exporter_enabled: true
 ```
 
 If you enable Grafana, a dedicated `NGINX PROXY` Grafana dashboard will be created.
@@ -95,8 +95,8 @@ If you enable Grafana, a dedicated `NGINX PROXY` Grafana dashboard will be creat
 At the moment of writing only images for `amd64` and `arm64` architectures are available. The playbook currently does not support [self-building](./self-building.md) a container image on other architectures. You can however use a custom-build image by setting:
 
 ```yaml
-prometheus_nginxlog_exporter_container_image_arch_check_enabled: false
+matrix_prometheus_nginxlog_exporter_docker_image_arch_check_enabled: false
-prometheus_nginxlog_exporter_container_image: path/to/docker/image:tag
+matrix_prometheus_nginxlog_exporter_docker_image: path/to/docker/image:tag
 ```
 
 ### Extending the configuration
@@ -106,7 +106,7 @@ There are some additional things you may wish to configure about Prometheus and
 Take a look at:
 
 - [Prometheus role](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus)'s [`defaults/main.yml`](https://github.com/mother-of-all-self-hosting/ansible-role-prometheus/blob/main/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 `prometheus_configuration_extension_yaml` variable
-- `roles/galaxy/prometheus_nginxlog_exporter/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `roles/custom/matrix-prometheus-nginxlog-exporter/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
 
 ## Adjusting the playbook configuration — Grafana
 
@@ -178,11 +178,11 @@ Name | Description
 `matrix_metrics_exposure_http_basic_auth_enabled`|Set this to `true` to protect all `https://matrix.example.com/metrics/*` endpoints with [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) (see the other variables below for supplying the actual credentials).
 `matrix_metrics_exposure_http_basic_auth_users`|Set this to the Basic Authentication credentials (raw `htpasswd` file content) used to protect `/metrics/*`. This htpasswd-file needs to be generated with the `htpasswd` tool and can include multiple username/password pairs.
 `prometheus_node_exporter_enabled`|Set this to `true` to enable the node (general system stats) exporter (locally, on the container network).
-`prometheus_node_exporter_container_labels_metrics_enabled`|Set this to `true` to expose the node (general system stats) metrics on `https://matrix.example.com/metrics/node-exporter`.
+`prometheus_node_exporter_container_labels_traefik_enabled`|Set this to `true` to expose the node (general system stats) metrics on `https://matrix.example.com/metrics/node-exporter`.
 `prometheus_postgres_exporter_enabled`|Set this to `true` to enable the [Postgres exporter](#enable-metrics-and-graphs-for-postgres-optional) (locally, on the container network).
-`prometheus_postgres_exporter_container_labels_metrics_enabled`|Set this to `true` to expose the [Postgres exporter](#enable-metrics-and-graphs-for-postgres-optional) metrics on `https://matrix.example.com/metrics/postgres-exporter`.
+`prometheus_postgres_exporter_container_labels_traefik_enabled`|Set this to `true` to expose the [Postgres exporter](#enable-metrics-and-graphs-for-postgres-optional) metrics on `https://matrix.example.com/metrics/postgres-exporter`.
-`prometheus_nginxlog_exporter_enabled`|Set this to `true` to enable the [prometheus-nginxlog-exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) (locally, on the container network).
+`matrix_prometheus_nginxlog_exporter_enabled`|Set this to `true` to enable the [nginx Log exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) (locally, on the container network).
-`prometheus_nginxlog_exporter_container_labels_metrics_enabled`|Set this to `true` to expose the [prometheus-nginxlog-exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) metrics on `https://matrix.example.com/metrics/nginxlog`.
+`matrix_prometheus_nginxlog_exporter_metrics_proxying_enabled`|Set this to `true` to expose the [nginx Log exporter](#enable-metrics-and-graphs-for-nginx-logs-optional) metrics on `https://matrix.example.com/metrics/nginxlog`.
 
 ### Expose metrics of other services/roles
 

docs/configuring-playbook-ssl-certificates.md

@@ -17,7 +17,7 @@ By default, the playbook retrieves and automatically renews free SSL certificate
 - This guide is intended to be referred for configuring the integrated Traefik server with regard to SSL certificates retrieval. If you're using [your own webserver](configuring-playbook-own-webserver.md), consult its documentation about how to configure it.
 - Let's Encrypt ends the expiration notification email service on June 4, 2025 (see: [the official announcement](https://letsencrypt.org/2025/01/22/ending-expiration-emails/)), and it recommends using a third party service for those who want to receive expiration notifications. If you are looking for a self-hosting service, you may be interested in a monitoring tool such as [Update Kuma](https://github.com/louislam/uptime-kuma/).
 
-  The [Mother-of-All-Self-Hosting (MASH)](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook can be used to install and manage an Uptime Kuma instance. See [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/uptime-kuma.md) for the instruction to install it with the playbook. If you are wondering how to use it for your Matrix server, refer to [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/setting-up-services-on-mdad-server.md) for the overview.
+  The [Mother-of-All-Self-Hosting (MASH)](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook can be used to install and manage an Uptime Kuma instance. See [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/uptime-kuma.md) for the instruction to install it with the MASH playbook. If you are wondering how to use the MASH playbook for your Matrix server, refer [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/setting-up-services-on-mdad-server.md).
 
 ## Use staging Let's Encrypt certificates
 

docs/configuring-playbook-synapse-admin.md

@@ -0,0 +1,89 @@
+<!--
+SPDX-FileCopyrightText: 2020 - 2024 MDAD project contributors
+SPDX-FileCopyrightText: 2020 - 2024 Slavi Pantaleev
+SPDX-FileCopyrightText: 2021 Aaron Raimist
+SPDX-FileCopyrightText: 2023 Christian González
+SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara
+SPDX-FileCopyrightText: 2024 Nikita Chernyi
+SPDX-FileCopyrightText: 2024 Uğur İLTER
+
+SPDX-License-Identifier: AGPL-3.0-or-later
+-->
+
+# Setting up Synapse Admin (optional)
+
+The playbook can install and configure [etkecc/synapse-admin](https://github.com/etkecc/synapse-admin) (a [feature-rich](https://github.com/etkecc/synapse-admin#fork-differences) fork of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin), community room: [#synapse-admin:etke.cc](https://matrix.to/#/#synapse-admin:etke.cc)) for you.
+
+synapse-admin is a web UI tool you can use to **administrate users, rooms, media, etc. on your Matrix server**. It's designed to work with the Synapse homeserver implementation and WON'T work with Dendrite because [Dendrite Admin API](https://element-hq.github.io/dendrite/administration/adminapi) differs from [Synapse Admin API](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/).
+
+💡 **Note**: the latest version of synapse-admin is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting.
+
+💡 **Note**: The playbook also supports an alternative management UI in the shape of [Element Admin](./configuring-playbook-element-admin.md). However, it's currently less feature-rich than Synapse Admin and has a dependency on [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md).
+
+## Adjusting DNS records (optional)
+
+By default, this playbook installs Synapse Admin on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section.
+
+If you wish to adjust it, see the section [below](#adjusting-the-synapse-admin-url-optional) for details about DNS configuration.
+
+## Adjusting the playbook configuration
+
+To enable Synapse Admin, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+
+```yaml
+matrix_synapse_admin_enabled: true
+```
+
+**Note**: Synapse Admin requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Synapse Admin needs these APIs to function, when installing Synapse Admin, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:
+
+- for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`
+- for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`
+
+By default, synapse-admin installation will be [restricted to only work with one homeserver](https://github.com/etkecc/synapse-admin/blob/e21e44362c879ac41f47c580b04210842b6ff3d7/README.md#restricting-available-homeserver) — the one managed by the playbook. To adjust these restrictions, tweak the `matrix_synapse_admin_config_restrictBaseUrl` variable.
+
+### Adjusting the Synapse Admin URL (optional)
+
+By tweaking the `matrix_synapse_admin_hostname` and `matrix_synapse_admin_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one.
+
+Example additional configuration for your `vars.yml` file:
+
+```yaml
+# Change the default hostname and path prefix
+matrix_synapse_admin_hostname: admin.example.com
+matrix_synapse_admin_path_prefix: /
+```
+
+If you've changed the default hostname, you may need to create a CNAME record for the Synapse Admin domain (`admin.example.com`), which targets `matrix.example.com`.
+
+When setting, replace `example.com` with your own.
+
+### Extending the configuration
+
+There are some additional things you may wish to configure about the component.
+
+Take a look at:
+
+- `roles/custom/matrix-synapse-admin/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_synapse_admin_configuration_extension_json` variable
+
+## Installing
+
+After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:
+
+<!-- NOTE: let this conservative command run (instead of install-all) to make it clear that failure of the command means something is clearly broken. -->
+```sh
+ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
+```
+
+The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`
+
+`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. Note these shortcuts run the `ensure-matrix-users-created` tag too.
+
+## Usage
+
+After installation, Synapse Admin will be accessible at: `https://matrix.example.com/synapse-admin/`
+
+To use Synapse Admin, you need to have [registered at least one administrator account](registering-users.md) on your server.
+
+## Troubleshooting
+
+As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-synapse-admin`.

docs/configuring-playbook-synapse-auto-accept-invite.md

@@ -1,26 +1,45 @@
 <!--
-SPDX-FileCopyrightText: 2019 Eduardo Beltrame
+SPDX-FileCopyrightText: 2024 MDAD project contributors
-SPDX-FileCopyrightText: 2019-2025 Slavi Pantaleev
+SPDX-FileCopyrightText: 2024 Slavi Pantaleev
-SPDX-FileCopyrightText: 2020 Tulir Asokan
+SPDX-FileCopyrightText: 2024 Suguru Hirahara
-SPDX-FileCopyrightText: 2021, 2024 MDAD project contributors
-SPDX-FileCopyrightText: 2022 Dennis Ciba
-SPDX-FileCopyrightText: 2022 Vladimir Panteleev
-SPDX-FileCopyrightText: 2023 Justin Croonenberghs
-SPDX-FileCopyrightText: 2023 Kuba Orlik
-SPDX-FileCopyrightText: 2023 Pierre 'McFly' Marty
-SPDX-FileCopyrightText: 2023 Samuel Meenzen
-SPDX-FileCopyrightText: 2024 Fabio Bonelli
-SPDX-FileCopyrightText: 2024-2026 Suguru Hirahara
 
 SPDX-License-Identifier: AGPL-3.0-or-later
 -->
 
-# Setting up Synapse Auto Invite Accept (optional, removed)
+# Setting up Synapse Auto Invite Accept (optional)
 
-🪦 The playbook used to be able to install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite), but no longer includes this component, as the same functionality [has been integrated](https://github.com/element-hq/synapse/pull/17147) to Synapse since [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0).
+The playbook can install and configure [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) for you.
+
+In short, it automatically accepts room invites. You can specify that only 1:1 room invites are auto-accepted. Defaults to false if not specified.
+
+See the project's [documentation](https://github.com/matrix-org/synapse-auto-accept-invite/blob/main/README.md) to learn what it does and why it might be useful to you.
+
+**Note**: Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0), the same feature [has been merged](https://github.com/element-hq/synapse/pull/17147) into Synapse (see the [Native alternative](#native-alternative) section below). You'd better use the native feature, instead of the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) 3rd party module.
+
+## Adjusting the playbook configuration
+
+If you decide that you'd like to let this playbook install the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite module for you, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:
+
+```yaml
+matrix_synapse_ext_synapse_auto_accept_invite_enabled: true
+
+matrix_synapse_ext_synapse_auto_accept_invite_accept_invites_only_direct_messages: true
+```
+
+### Synapse worker deployments
+
+In a [workerized Synapse deployment](https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/c9a842147e09647c355799ca024d65a5de66b099/docs/configuring-playbook-synapse.md#load-balancing-with-workers) it is possible to run this module on a worker to reduce the load on the main process (Default is `null`). For example, add this to your configuration:
+
+```yaml
+matrix_synapse_ext_synapse_auto_accept_invite_worker_to_run_on: 'matrix-synapse-worker-generic-0'
+```
+
+There might be an [issue with federation](https://github.com/matrix-org/synapse-auto-accept-invite/issues/18).
 
 ## Native alternative
 
+Since Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0), the functionality provided by the [synapse-auto-invite-accept](https://github.com/matrix-org/synapse-auto-accept-invite) 3rd party module [has been made](https://github.com/element-hq/synapse/pull/17147) part of Synapse.
+
 Here's example configuration for using the **native** Synapse feature:
 
 ```yaml

docs/configuring-playbook-synapse-s3-storage-provider.md

@@ -177,8 +177,6 @@ By default, we periodically ensure that all local files are uploaded to S3 and a
 - … invoked via the `matrix-synapse-s3-storage-provider-migrate.service` service
 - … triggered by the `matrix-synapse-s3-storage-provider-migrate.timer` timer, every day at 05:00
 
-The same `migrate` script also prunes empty directories in the local media repository (`remote_content` and `remote_thumbnail`) after upload/delete operations.
-
 So… you don't need to perform any maintenance yourself.
 
 The schedule is defined in the format of systemd timer calendar. To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs):

docs/configuring-playbook-synapse.md

@@ -76,33 +76,10 @@ The only thing you **cannot** do is mix [generic workers](#generic-workers) and
 
 When Synapse workers are enabled, the integrated [Postgres database is tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum number of Postgres connections are increased from `200` to `500`. If you need to decrease or increase the number of maximum Postgres connections further, use the `postgres_max_connections` variable.
 
-The `matrix-synapse` role also manages the `matrix-synapse-reverse-proxy-companion` component for load-balancing with workers. This component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly.
+A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and component handles load-balancing for workers. This role/component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly.
 
 In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/element-hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`.
 
-### Limit joining heavy rooms on constrained hosts
-
-If your server is underpowered, joining heavy rooms can cause Synapse to consume a lot of resources and be unavailable for long (while it catches up).
-
-To avoid this, Synapse can be configured to reject joins for remote rooms that are too complex before users enter them.
-
-Complexity is computed as `current_state_events / 500` (Synapse state event count for current room state). When the resulting value is higher than `matrix_synapse_limit_remote_rooms_complexity` and `matrix_synapse_limit_remote_rooms_enabled` is `true`, Synapse blocks joining the room.
-
-We recommend using this as a guardrail on low-resource servers:
-
-```yaml
-matrix_synapse_limit_remote_rooms_enabled: true
-
-# Tweak as necessary
-matrix_synapse_limit_remote_rooms_complexity: 1.0
-
-# Uncomment and tweak if necessary
-# matrix_synapse_limit_remote_rooms_complexity_error: "Your homeserver is unable to join rooms this large or complex. Please speak to your server administrator, or upgrade your instance to join this room."
-
-# If you'd like your admins to be exempt from this limit, uncomment the line below
-# matrix_synapse_limit_remote_rooms_admins_can_join: true
-```
-
 ### Synapse + OpenID Connect for Single-Sign-On
 
 💡 An alternative to setting up OIDC in Synapse is to use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS). Newer clients (like Element X) only support SSO-based authentication via MAS and not via the legacy Synapse OIDC setup described below. That said, MAS is still a new experimental service which comes with its own downsides. Consult its documentation to learn if it will be a good fit for your deployment.
@@ -196,11 +173,11 @@ The shortcut commands with the [`just` program](just.md) are also available: `ju
 
 ## Usage
 
-### Ketesa
+### Synapse Admin
 
-[Ketesa](configuring-playbook-ketesa.md) is a fully-featured web UI for administrating your homeserver — managing users, rooms, media, sessions, and more.
+With [Synapse Admin](configuring-playbook-synapse-admin.md), certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace.
 
-The playbook can install and configure Ketesa for you. For details about it, see [this page](configuring-playbook-ketesa.md).
+The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md).
 
 ### Monitoring Synapse Metrics with Prometheus and Grafana
 

docs/configuring-playbook-traefik.md

@@ -31,13 +31,10 @@ To enable a Traefik [Dashboard](https://doc.traefik.io/traefik/operations/dashbo
 traefik_dashboard_enabled: true
 traefik_dashboard_hostname: "{{ matrix_server_fqn_matrix }}"
 traefik_dashboard_basicauth_enabled: true
-traefik_dashboard_basicauth_htpasswd: "YOUR_USERNAME_HERE:$apr1$..."
+traefik_dashboard_basicauth_user: YOUR_USERNAME_HERE
+traefik_dashboard_basicauth_password: YOUR_PASSWORD_HERE
 ```
 
-Generate the `traefik_dashboard_basicauth_htpasswd` value on your local machine with a command like `htpasswd -nb YOUR_USERNAME_HERE YOUR_PASSWORD_HERE`.
-
-The role also supports the legacy `traefik_dashboard_basicauth_user` / `traefik_dashboard_basicauth_password` convenience variables, but that path depends on the `passlib` Python library on the Ansible controller, may be affected by passlib/bcrypt compatibility issues, and generates non-deterministic hashes which can lead to unnecessary changes.
-
 > [!WARNING]
 > Enabling the dashboard on a hostname you use for something else (like `matrix_server_fqn_matrix` in the configuration above) may cause conflicts. Enabling the Traefik Dashboard makes Traefik capture all `/dashboard` and `/api` requests and forward them to itself. If any of the services hosted on the same hostname requires any of these 2 URL prefixes, you will experience problems. So far, we're not aware of any playbook services which occupy these endpoints and are likely to cause conflicts.
 

docs/configuring-playbook-turn.md

@@ -1,61 +1,39 @@
 <!--
-SPDX-FileCopyrightText: 2018-2024 Slavi Pantaleev
+SPDX-FileCopyrightText: 2019 - 2024 Slavi Pantaleev
-SPDX-FileCopyrightText: 2020 Aaron Raimist
 SPDX-FileCopyrightText: 2020 Christian Wolf
+SPDX-FileCopyrightText: 2020 MDAD project contributors
 SPDX-FileCopyrightText: 2020 Marcel Partap
-SPDX-FileCopyrightText: 2020-2024 MDAD project contributors
+SPDX-FileCopyrightText: 2024 - 2025 Suguru Hirahara
-SPDX-FileCopyrightText: 2022 Alejo Diaz
-SPDX-FileCopyrightText: 2022 Julian Foad
-SPDX-FileCopyrightText: 2024-2026 Suguru Hirahara
 
 SPDX-License-Identifier: AGPL-3.0-or-later
 -->
 
 # Configuring a TURN server (optional, advanced)
 
-By default, the [coturn](https://github.com/coturn/coturn) TURN server component is enabled automatically only when [Jitsi](configuring-playbook-jitsi.md) is enabled. If you're not using Jitsi, coturn is not enabled by default.
+By default, this playbook installs and configures the [coturn](https://github.com/coturn/coturn) as a TURN server, through which clients can make audio/video calls even from [NAT](https://en.wikipedia.org/wiki/Network_address_translation)-ed networks. It also configures the Synapse chat server by default, so that it points to the coturn TURN server installed by the playbook. If that's okay, you can skip this document.
 
-If you explicitly need coturn while not using Jitsi, enable it with:
+If you'd like to stop the playbook installing the server, see the section [below](#disabling-coturn) to check the configuration for disabling it.
-
-```yaml
-coturn_enabled: true
-```
-
-and configure its IP-related settings in the section below.
-
-If you'd like coturn to stay disabled even when Jitsi is enabled, or if you prefer to use an external TURN provider, see [disabling coturn](#disabling-coturn) section below.
-
-When Coturn is not enabled, homeservers (like Synapse) would not point to TURN servers and *legacy* audio/video call functionality may fail. If you're using [Matrix RTC](configuring-playbook-matrix-rtc.md) (for [Element Call](configuring-playbook-element-call.md)), you likely don't have a need to enable coturn.
-
-## Adjusting firewall rules
-
-To ensure Coturn functions correctly, the following firewall rules and port forwarding settings are required when coturn is enabled:
-
-- `3478/tcp`: STUN/TURN over TCP
-- `3478/udp`: STUN/TURN over UDP
-- `5349/tcp`: TURN over TCP
-- `5349/udp`: TURN over UDP
-- `49152-49172/udp`: TURN/UDP relay range
-
-If LiveKit's embedded TURN is enabled at the same time (for MatrixRTC/Element Call), keep the Coturn relay range distinct from LiveKit's relay range (`livekit_server_config_turn_relay_range_start`/`livekit_server_config_turn_relay_range_end`).
-
-💡 Docker configures the server's internal firewall for you. In most cases, you don't need to do anything special on the host itself.
 
 ## Adjusting the playbook configuration
 
 ### Define public IP manually (optional)
 
-If you enable coturn (either via Jitsi or manually), we recommend that you configure the public IP addresses of your server in the `vars.yml` file:
+In the `hosts` file we explicitly ask for your server's external IP address when defining `ansible_host`, because the same value is used for configuring coturn.
+
+If you'd rather use a local IP for `ansible_host`, add the following configuration to your `vars.yml` file. Make sure to replace `YOUR_PUBLIC_IP` with the pubic IP used by the server.
 
 ```yaml
-# You can define multiple IP addresses if your server has multiple external IP addresses
+matrix_coturn_turn_external_ip_address: "YOUR_PUBLIC_IP"
-coturn_turn_external_ip_addresses: ["YOUR_PUBLIC_IP"]
 ```
 
-If you'd like to rely on external IP address auto-detection (not recommended unless you need it), avoid configuring this variable. The playbook will automatically contact an [echoip](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable.
+If you'd like to rely on external IP address auto-detection (not recommended unless you need it), set an empty value to the variable. The playbook will automatically contact an [EchoIP](https://github.com/mpolden/echoip)-compatible service (`https://ifconfig.co/json` by default) to determine your server's IP address. This API endpoint is configurable via the `matrix_coturn_turn_external_ip_address_auto_detection_echoip_service_url` variable.
 
->[!NOTE]
+If your server has multiple external IP addresses, the coturn role offers a different variable for specifying them:
-> You can self-host the echoip service by using the [Mother-of-All-Self-Hosting (MASH)](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook. See [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/echoip.md) for the instruction to install it with the playbook. If you are wondering how to use it for your Matrix server, refer to [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/setting-up-services-on-mdad-server.md) for the overview.
+
+```yaml
+# Note: matrix_coturn_turn_external_ip_addresses is different than matrix_coturn_turn_external_ip_address
+matrix_coturn_turn_external_ip_addresses: ['1.2.3.4', '4.5.6.7']
+```
 
 ### Change the authentication mechanism (optional)
 
@@ -64,7 +42,7 @@ The playbook uses the [`auth-secret` authentication method](https://github.com/c
 To do so, add the following configuration to your `vars.yml` file:
 
 ```yaml
-coturn_authentication_method: lt-cred-mech
+matrix_coturn_authentication_method: lt-cred-mech
 ```
 
 Regardless of the selected authentication method, the playbook generates secrets automatically and passes them to the homeserver and coturn.
@@ -78,7 +56,7 @@ By default, Coturn uses the same hostname as your Matrix homeserver (the value o
 If you'd like to use a custom subdomain for Coturn (e.g., `turn.example.com` or `t.matrix.example.com`), add the following configuration to your `vars.yml` file:
 
 ```yaml
-coturn_hostname: turn.example.com
+matrix_coturn_hostname: turn.example.com
 ```
 
 The playbook will automatically:
@@ -94,7 +72,7 @@ If you'd like to use another TURN server (be it coturn or some other one), add t
 
 ```yaml
 # Disable integrated coturn server
-coturn_enabled: false
+matrix_coturn_enabled: false
 
 # Point Synapse to your other coturn server
 matrix_synapse_turn_uris:
@@ -115,15 +93,15 @@ You can put multiple host/port combinations if you'd like to.
 
 ### Edit the reloading schedule (optional)
 
-By default the service is reloaded on 6:30 a.m. every day based on the `coturn_reload_schedule` variable so that new SSL certificates can kick in. It is defined in the format of systemd timer calendar.
+By default the service is reloaded on 6:30 a.m. every day based on the `matrix_coturn_reload_schedule` variable so that new SSL certificates can kick in. It is defined in the format of systemd timer calendar.
 
 To edit the schedule, add the following configuration to your `vars.yml` file (adapt to your needs):
 
 ```yaml
-coturn_reload_schedule: "*-*-* 06:30:00"
+matrix_coturn_reload_schedule: "*-*-* 06:30:00"
 ```
 
-**Note**: the actual job may run with a delay. See `coturn_reload_schedule_randomized_delay_sec` for its default value.
+**Note**: the actual job may run with a delay. See `matrix_coturn_reload_schedule_randomized_delay_sec` for its default value.
 
 ### Extending the configuration
 
@@ -131,18 +109,18 @@ There are some additional things you may wish to configure about the TURN server
 
 Take a look at:
 
-- `roles/galaxy/coturn/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
+- `roles/custom/matrix-coturn/defaults/main.yml` for some variables that you can customize via your `vars.yml` file
 
 ## Disabling coturn
 
-Coturn is only enabled by default when [Jitsi](configuring-playbook-jitsi.md) is enabled. In most instances, you don't need to explicitly disable it.
+If, for some reason, you'd like for the playbook to not install coturn (or to uninstall it if it was previously installed), add the following configuration to your `vars.yml` file:
-
-To force the playbook to not install Coturn (even when Jitsi is enabled), add the following configuration to your `vars.yml` file:
 
 ```yaml
-coturn_enabled: false
+matrix_coturn_enabled: false
 ```
 
+In that case, Synapse would not point to any coturn servers and audio/video call functionality may fail.
+
 ## Installing
 
 After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:

docs/configuring-playbook.md

@@ -51,6 +51,8 @@ For a more custom setup, see the [Other configuration options](#other-configurat
 
   - [Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation
 
+  - [Configuring conduwuit](configuring-playbook-conduwuit.md), if you've switched to the [conduwuit](https://conduwuit.puppyirl.gay/) homeserver implementation
+
   - [Configuring continuwuity](configuring-playbook-continuwuity.md), if you've switched to the [continuwuity](https://continuwuity.org) homeserver implementation
 
   - [Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation
@@ -87,8 +89,6 @@ Web clients for Matrix that you can host on your own domains.
 
 - [Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing primarily on simple, elegant and secure interface
 
-- [Setting up Sable](configuring-playbook-client-sable.md), if you've enabled [Sable](https://github.com/7w1/sable), a web client focusing primarily on simple, elegant and secure interface
-
 - [Setting up SchildiChat Web](configuring-playbook-client-schildichat-web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a web client based on [Element Web](https://element.io/) with some extras and tweaks
 
 - [Setting up FluffyChat Web](configuring-playbook-client-fluffychat-web.md), if you've enabled [FluffyChat Web](https://github.com/krille-chan/fluffychat), a cute cross-platform messenger (web, iOS, Android) for Matrix written in [Flutter](https://flutter.dev/)
@@ -102,7 +102,7 @@ Extend and modify how users are authenticated on your homeserver.
 
 - [Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)
 
-- [Setting up Ketesa](configuring-playbook-ketesa.md)
+- [Setting up Synapse Admin](configuring-playbook-synapse-admin.md)
 
 - [Setting up matrix-registration](configuring-playbook-matrix-registration.md)
 
@@ -164,6 +164,8 @@ Bridges can be used to connect your Matrix installation with third-party communi
 
 - [Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md)
 
+- [Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md)
+
 - [Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-appservice-kakaotalk.md)
 
 - [Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md)
@@ -235,6 +237,8 @@ Various services that don't fit any other categories.
 
 - [Setting up Matrix RTC](configuring-playbook-matrix-rtc.md) (optional)
 
+- [Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md)
+
 - [Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers
 
 - [Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)
@@ -257,12 +261,8 @@ Various services that don't fit any other categories.
 
 **Note**: since a deprecated or unmaintained service will not be updated, its bug or vulnerability will be unlikely to get patched. It is recommended to migrate from the service to an alternative if any, and make sure to do your own research before you decide to keep it running nonetheless.
 
-- [Configuring conduwuit](configuring-playbook-conduwuit.md) (removed; this component has been abandoned and unmaintained)
-
 - [Setting up the Sliding Sync proxy](configuring-playbook-sliding-sync-proxy.md) for clients which require Sliding Sync support (like old Element X versions, before it got switched to Simplified Sliding Sync)
 
-- [Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md) (removed; this component has been discontinued)
-
 - [Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (deprecated; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be [installed using this playbook](configuring-playbook-bridge-hookshot.md))
 
 - [Setting up the Dimension integration manager](configuring-playbook-dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299); after [installing](installing.md))
@@ -290,5 +290,3 @@ Various services that don't fit any other categories.
 - [Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md))
 
 - [Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md))
-
-- [Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md) (removed; since Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0) the same feature is available natively.)

docs/container-images.md

@@ -27,6 +27,7 @@ We try to stick to official images (provided by their respective projects) as mu
 | ------- | --------------- | -------- | ----------- |
 | [Synapse](configuring-playbook-synapse.md) | [element-hq/synapse](https://ghcr.io/element-hq/synapse) | ✅ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network |
 | [Conduit](configuring-playbook-conduit.md) | [matrixconduit/matrix-conduit](https://hub.docker.com/r/matrixconduit/matrix-conduit) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Conduit is a lightweight open-source server implementation of the Matrix Specification with a focus on easy setup and low system requirements |
+| [conduwuit](configuring-playbook-conduwuit.md) | [girlbossceo/conduwuit](https://ghcr.io/girlbossceo/conduwuit) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit is a fork of Conduit. |
 | [continuwuity](configuring-playbook-continuwuity.md) | [continuwuation/continuwuity](https://forgejo.ellis.link/continuwuation/continuwuity) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. continuwuity is a continuation of conduwuit. |
 | [Dendrite](configuring-playbook-dendrite.md) | [matrixdotorg/dendrite-monolith](https://hub.docker.com/r/matrixdotorg/dendrite-monolith/) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse. |
 
@@ -39,7 +40,6 @@ Web clients for Matrix that you can host on your own domains.
 | [Element Web](configuring-playbook-client-element-web.md) | [vectorim/element-web](https://hub.docker.com/r/vectorim/element-web/) | ✅ | Default Matrix web client, configured to connect to your own Synapse server |
 | [Hydrogen](configuring-playbook-client-hydrogen.md) | [element-hq/hydrogen-web](https://ghcr.io/element-hq/hydrogen-web) | ❌ | Lightweight Matrix client with legacy and mobile browser support |
 | [Cinny](configuring-playbook-client-cinny.md) | [ajbura/cinny](https://hub.docker.com/r/ajbura/cinny) | ❌ | Simple, elegant and secure web client |
-| [Sable](configuring-playbook-client-sable.md) | [7w1/sable](https://ghcr.io/7w1/sable) | ❌ | Simple, elegant and secure web client |
 | [SchildiChat Web](configuring-playbook-client-schildichat-web.md) | [etke.cc/schildichat-web](https://ghcr.io/etkecc/schildichat-web) | ❌ | Based on Element Web, with a more traditional instant messaging experience |
 
 ## Server Components
@@ -102,6 +102,7 @@ Bridges can be used to connect your Matrix installation with third-party communi
 | [matrix-appservice-irc](configuring-playbook-bridge-appservice-irc.md) | [matrixdotorg/matrix-appservice-irc](https://hub.docker.com/r/matrixdotorg/matrix-appservice-irc) | ❌ | Bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat) |
 | [matrix-appservice-kakaotalk](configuring-playbook-bridge-appservice-kakaotalk.md) | Self-building | ❌ | Bridge to [Kakaotalk](https://www.kakaocorp.com/page/service/service/KakaoTalk?lang=ENG) |
 | [matrix-appservice-discord](configuring-playbook-bridge-appservice-discord.md) | [matrix-org/matrix-appservice-discord](https://ghcr.io/matrix-org/matrix-appservice-discord) | ❌ | Bridge to [Discord](https://discordapp.com/) |
+| [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) | [matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack) | ❌ | Bridge to [Slack](https://slack.com/) |
 | [matrix-hookshot](configuring-playbook-bridge-hookshot.md) | [halfshot/matrix-hookshot](https://hub.docker.com/r/halfshot/matrix-hookshot) | ❌ | Bridge for generic webhooks and multiple project management services, such as GitHub, GitLab, Figma, and Jira in particular |
 | [matrix-sms-bridge](configuring-playbook-bridge-matrix-bridge-sms.md) | [folivonet/matrix-sms-bridge](https://hub.docker.com/repository/docker/folivonet/matrix-sms-bridge) | ❌ | Bridge to SMS |
 | [matrix-wechat](configuring-playbook-bridge-wechat.md) | [lxduo/matrix-wechat](https://hub.docker.com/r/lxduo/matrix-wechat) | ❌ | Bridge to [WeChat](https://www.wechat.com/) |
@@ -134,7 +135,7 @@ Services that help you in administrating and monitoring your Matrix installation
 | ------- | --------------- | -------- | ----------- |
 | [matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md) | [metio/matrix-alertmanager-receiver](https://hub.docker.com/r/metio/matrix-alertmanager-receiver)  | ❌ | Prometheus' [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) client |
 | [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) | [element-hq/matrix-authentication-service](https://ghcr.io/element-hq/matrix-authentication-service) | ❌ | OAuth 2.0 and OpenID Provider server |
-| [Ketesa](configuring-playbook-ketesa.md) | [etkecc/ketesa](https://ghcr.io/etkecc/ketesa) | ❌ | Fully-featured web UI for administrating your Matrix homeserver — users, rooms, media, sessions, and more |
+| [synapse-admin](configuring-playbook-synapse-admin.md) | [etke.cc/synapse-admin](https://ghcr.io/etkecc/synapse-admin) | ❌ | Web UI tool for administrating users and rooms on your Matrix server |
 | [Metrics and Graphs](configuring-playbook-prometheus-grafana.md) | [prom/prometheus](https://hub.docker.com/r/prom/prometheus/) | ❌ | [Prometheus](https://prometheus.io) time-series database server |
 | [Metrics and Graphs](configuring-playbook-prometheus-grafana.md) | [prom/node-exporter](https://hub.docker.com/r/prom/node-exporter/) | ❌ | Prometheus [node-exporter](https://prometheus.io/docs/guides/node-exporter/) host metrics exporter |
 | [Metrics and Graphs](configuring-playbook-prometheus-grafana.md) | [grafana/grafana](https://hub.docker.com/r/grafana/grafana/) | ❌ | Graphing tool that works well with the above two images. Our playbook also adds two dashboards for [Synapse](https://github.com/element-hq/synapse/tree/master/contrib/grafana) and [Node Exporter](https://github.com/rfrail3/grafana-dashboards) |
@@ -150,6 +151,7 @@ Various services that don't fit any other categories.
 
 | Service | Container image | Default? | Description |
 | ------- | --------------- | -------- | ----------- |
+| [synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md) | (N/A) | ❌ | Synapse module to automatically accept invites |
 | [synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md) | [mb-saces/rust-synapse-tools](https://gitlab.com/mb-saces/rust-synapse-tools/container_registry) | ❌ | Cli tool that automatically compresses Synapse's `state_groups` database table in background |
 | [Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced) | [devture/matrix-corporal](https://hub.docker.com/r/devture/matrix-corporal/) | ❌ | Reconciliator and gateway for a managed Matrix server |
 | [Etherpad](configuring-playbook-etherpad.md) | [etherpad/etherpad](https://hub.docker.com/r/etherpad/etherpad/) | ❌ | Open source collaborative text editor |
@@ -170,12 +172,10 @@ The list of the deprecated or unmaintained services is available [here](configur
 
 | Service | Container image | Default? | Description |
 | ------- | --------------- | -------- | ----------- |
-| [conduwuit](configuring-playbook-conduwuit.md) | [girlbossceo/conduwuit](https://ghcr.io/girlbossceo/conduwuit) | ❌ | Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit was a fork of Conduit. |
 | [Dimension](configuring-playbook-dimension.md) | [turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-dimension) | ❌ | Open source integration manager for Matrix clients |
 | [Email2Matrix](configuring-playbook-email2matrix.md) | [devture/email2matrix](https://hub.docker.com/r/devture/email2matrix/) | ❌ | Bridge for relaying emails to Matrix rooms |
 | [Go-NEB](configuring-playbook-bot-go-neb.md) | [matrixdotorg/go-neb](https://hub.docker.com/r/matrixdotorg/go-neb) | ❌ | Multi functional bot written in Go |
 | [ma1sd](configuring-playbook-ma1sd.md) | [ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/) | ❌ | Matrix Identity Server |
-| [matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md) | [matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack) | ❌ | Bridge to [Slack](https://slack.com/) |
 | [matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md) | [turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks) | ❌ | Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.) |
 | [matrix-chatgpt-bot](configuring-playbook-bot-chatgpt.md) | [matrixgpt/matrix-chatgpt-bot](https://ghcr.io/matrixgpt/matrix-chatgpt-bot) | ❌ | Accessing ChatGPT via your favourite Matrix client |
 | [mautrix-facebook](configuring-playbook-bridge-mautrix-facebook.md) | [mautrix/facebook](https://mau.dev/mautrix/facebook/container_registry) | ❌ | Bridge to [Facebook](https://facebook.com/) |
@@ -185,4 +185,3 @@ The list of the deprecated or unmaintained services is available [here](configur
 | [mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) | [mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry) | ❌ | Bridge to [Slack](https://slack.com) |
 | [mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md) | [sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter) | ❌ | Bridge for Twitter-DMs ([Twitter](https://twitter.com/)) |
 | [sliding-sync](configuring-playbook-sliding-sync-proxy.md) | [matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync) | ❌ | Sliding Sync support for clients which require it (like old Element X versions, before it got switched to Simplified Sliding Sync) |
-| [synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md) | (N/A) | ❌ | Synapse module to automatically accept invites |

docs/faq.md

@@ -305,23 +305,18 @@ See [Serving the base domain](configuring-playbook-base-domain-serving.md).
 
 ### How do I optimize this setup for a low-power server?
 
-For a low-power server, it's best to use an alternative homeserver implementation (other than [Synapse](configuring-playbook-synapse.md)).
-
 You can disable some not-so-important services to save on memory.
 
 ```yaml
 # Disabling this will prevent email-notifications and other such things from working.
 exim_relay_enabled: false
-```
 
-If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed by default), there are additional optimizations listed on its documentation page that you can perform.
+# You can also disable this to save more RAM,
+# at the expense of audio/video calls being unreliable.
+matrix_coturn_enabled: false
 
-
+# This makes Synapse not keep track of who is online/offline.
-#### Synapse-specific optimizations
+#
-
-If you're using [Synapse](configuring-playbook-synapse.md), you can also consider the following optimizations:
-
-```yaml
 # Keeping track of this and announcing such online-status in federated rooms with
 # hundreds of servers inside is insanely heavy (https://github.com/matrix-org/synapse/issues/3971).
 #
@@ -329,14 +324,18 @@ If you're using [Synapse](configuring-playbook-synapse.md), you can also conside
 matrix_synapse_presence_enabled: false
 ```
 
-You can also consider [implementing a restriction on room complexity](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts), in order to prevent users from joining very heavy rooms:
+You can also consider implementing a restriction on room complexity, in order to prevent users from joining very heavy rooms:
 
 ```yaml
-# See: docs/configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts
+matrix_synapse_configuration_extension_yaml: |
-matrix_synapse_limit_remote_rooms_enabled: true
+  limit_remote_rooms:
-matrix_synapse_limit_remote_rooms_complexity: 1.0
+    enabled: true
+    complexity: 1.0 # this limits joining complex (~large) rooms, can be
+					# increased, but larger values can require more RAM
 ```
 
+If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed by default), there are additional optimizations listed on its documentation page that you can perform.
+
 ### I already have Docker on my server. Can you stop installing Docker via the playbook?
 
 Yes, we can stop installing Docker ourselves. Just use this in your `vars.yml` file:

docs/howto-srv-server-delegation.md

@@ -26,7 +26,7 @@ The up-to-date list can be accessed on [traefik's documentation](https://doc.tra
 
 **Note**: the changes below instruct you how to do this for a basic Synapse installation. You will need to adapt the variable name and the content of the labels:
 
-- if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md), [continuwuity](./configuring-playbook-continuwuity.md) or [Dendrite](./configuring-playbook-dendrite.md))
+- if you're using another homeserver implementation (e.g. [Conduit](./configuring-playbook-conduit.md), [conduwuit](./configuring-playbook-conduwuit.md), [continuwuity](./configuring-playbook-continuwuity.md) or [Dendrite](./configuring-playbook-dendrite.md))
 - if you're using [Synapse with workers enabled](./configuring-playbook-synapse.md#load-balancing-with-workers) (`matrix_synapse_workers_enabled: true`). In that case, it's actually the `matrix-synapse-reverse-proxy-companion` service which has Traefik labels attached
 
 Also, all instructions below are from an older version of the playbook and may not work anymore.
@@ -104,10 +104,10 @@ This should not happen again afterwards as Traefik will renew certificates well
 
 ```yaml
 # Only depend on docker.service, this removes the dependency on the certificate exporter, might imply the need to manually restart coturn on the first installation once the certificates are obtained, afterwards, the reload service should handle things
-coturn_systemd_required_services_list: ['docker.service']
+matrix_coturn_systemd_required_services_list: ['docker.service']
 
 # This changes the path of the loaded certificate, while maintaining the original functionality, we're now loading the wildcard certificate.
-coturn_container_additional_volumes: |
+matrix_coturn_container_additional_volumes: |
   {{
     (
       [
@@ -121,7 +121,7 @@ coturn_container_additional_volumes: |
          'dst': '/privatekey.key',
          'options': 'ro',
        },
-      ] if matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] and traefik_certs_dumper_enabled and coturn_tls_enabled else []
+      ] if matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] and traefik_certs_dumper_enabled and matrix_coturn_tls_enabled else []
     )
   }}
 ```
@@ -165,10 +165,10 @@ traefik_environment_variables: |
   LEGO_DISABLE_CNAME_SUPPORT=true
 
 # Only depend on docker.service, this removes the dependency on the certificate exporter, might imply the need to manually restart coturn on the first installation once the certificates are obtained, afterwards, the reload service should handle things
-coturn_systemd_required_services_list: ['docker.service']
+matrix_coturn_systemd_required_services_list: ['docker.service']
 
 # This changes the path of the loaded certificate, while maintaining the original functionality, we're now loading the wildcard certificate.
-coturn_container_additional_volumes: |
+matrix_coturn_container_additional_volumes: |
   {{
     (
       [
@@ -182,7 +182,7 @@ coturn_container_additional_volumes: |
          'dst': '/privatekey.key',
          'options': 'ro',
        },
-      ] if matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] and traefik_certs_dumper_enabled and coturn_tls_enabled else []
+      ] if matrix_playbook_reverse_proxy_type in ['playbook-managed-traefik', 'other-traefik-container'] and traefik_certs_dumper_enabled and matrix_coturn_tls_enabled else []
     )
   }}
 ```

docs/installing.md

@@ -146,7 +146,6 @@ After completing the installation, you can:
 - or learn how to [maintain your server](faq.md#maintenance)
 - or join some Matrix rooms:
   * via the *Explore rooms* feature in Element Web or some other clients, or by discovering them using this [matrix-static list](https://view.matrix.org). **Note**: joining large rooms may overload small servers.
-    For tuning guidance on constrained hosts, see [Limit joining heavy rooms on constrained hosts](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts).
   * or come say Hi in our support room — [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com). You might learn something or get to help someone else new to Matrix hosting.
 - or help make this playbook better by contributing (code, documentation, or [coffee/beer](https://liberapay.com/s.pantaleev/donate))
 

docs/just.md

@@ -43,13 +43,3 @@ For example, these two commands are different:
 The just recipe runs `ensure-matrix-users-created` and `start` tags after `install-all`, while the latter runs only `install-all` tag. The correct shortcut of the latter is `just run-tags install-all`.
 
 Such kind of difference sometimes matters. For example, when you install a Matrix server into which you will import old data (see [here](installing.md#installing-a-server-into-which-youll-import-old-data)), you are not supposed to run `just install-all` or `just setup-all`, because these commands start services immediately after installing components, which may prevent you from importing the data.
-
-## Conditional service restart
-
-When running `install-all` or `install-service` (whether via `just` or raw `ansible-playbook`), only services whose configuration or container image actually changed during the playbook run will be restarted. Unchanged services are left running (or get started if they were stopped). This reduces unnecessary downtime.
-
-When running with `setup-*` tags (e.g. `setup-all`, `setup-synapse`), all services are unconditionally restarted regardless of whether changes were detected. This is appropriate for setup's thorough "full setup" semantics.
-
-`start-all` and `start-group` always restart all targeted services, since no installation tasks run during these commands.
-
-This behavior is automatically determined based on the playbook tags in use. It can be overridden with the `devture_systemd_service_manager_conditional_restart_enabled` variable. For example, to force unconditional restarts during installation: `just install-all --extra-vars='devture_systemd_service_manager_conditional_restart_enabled=false'`

docs/maintenance-synapse.md

@@ -83,8 +83,6 @@ You should then be able to browse the adminer database administration GUI at htt
 
 Synapse's presence feature which tracks which users are online and which are offline can use a lot of processing power. You can disable presence by adding `matrix_synapse_presence_enabled: false` to your `vars.yml` file.
 
-On smaller servers, consider limiting joins to very complex rooms with [the room complexity guard](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts).
-
 If you have enough compute resources (CPU & RAM), you can make Synapse better use of them by [enabling load-balancing with workers](configuring-playbook-synapse.md#load-balancing-with-workers).
 
 [Tuning your PostgreSQL database](maintenance-postgres.md#tuning-postgresql) could also improve Synapse performance. The playbook tunes the integrated Postgres database automatically, but based on your needs you may wish to adjust tuning variables manually. If you're using an [external Postgres database](configuring-playbook-external-postgres.md), you will also need to tune Postgres manually.

docs/prerequisites.md

@@ -23,6 +23,8 @@ We will be using `example.com` as the domain in the following instruction. Pleas
 
 - [Ansible](http://ansible.com/) program. It's used to run this playbook and configures your server for you. Take a look at [our guide about Ansible](ansible.md) for more information, as well as [version requirements](ansible.md#supported-ansible-versions) and alternative ways to run Ansible.
 
+- [passlib](https://passlib.readthedocs.io/en/stable/index.html) Python library. See [this official documentation](https://passlib.readthedocs.io/en/stable/install.html#installation-instructions) for an instruction to install it. On most distros, you need to install some `python-passlib` or `py3-passlib` package, etc.
+
 - [`git`](https://git-scm.com/) as the recommended way to download the playbook. `git` may also be required on the server if you will be [self-building](self-building.md) components.
 
 - [`just`](https://github.com/casey/just) for running `just roles`, `just update`, etc. (see [`justfile`](../justfile)), although you can also run these commands manually. Take a look at this documentation for more information: [Running `just` commands](just.md).
@@ -57,7 +59,12 @@ We will be using `example.com` as the domain in the following instruction. Pleas
 
   - `80/tcp`: HTTP webserver
   - `443/tcp` and `443/udp`: HTTPS webserver
+  - `3478/tcp`: STUN/TURN over TCP (used by [coturn](./configuring-playbook-turn.md))
+  - `3478/udp`: STUN/TURN over UDP (used by [coturn](./configuring-playbook-turn.md))
+  - `5349/tcp`: TURN over TCP (used by [coturn](./configuring-playbook-turn.md))
+  - `5349/udp`: TURN over UDP (used by [coturn](./configuring-playbook-turn.md))
   - `8448/tcp` and `8448/udp`: Matrix Federation API HTTPS webserver. Some components like [Matrix User Verification Service](configuring-playbook-user-verification-service.md#open-matrix-federation-port) require this port to be opened **even with federation disabled**.
+  - the range `49152-49172/udp`: TURN over UDP
   - potentially some other ports, depending on the additional (non-default) services that you enable in the **configuring the playbook** step (later on). Consult each service's documentation page in `docs/` for that.
 
 ---------------------------------------------

docs/registering-users.md

@@ -95,7 +95,10 @@ This `register-user` script actually invokes the `mas-cli manage register-user`
 
 ## Managing users via a Web UI
 
-To manage users and your homeserver more easily (via a web interface), you can install [Ketesa](configuring-playbook-ketesa.md) — a fully-featured admin UI covering users, rooms, media, sessions, and MAS management.
+To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md).
+
+> [!WARNING]
+> If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information.
 
 ## Letting certain users register on your private server
 

docs/self-building.md

@@ -26,17 +26,18 @@ Note that **not all components support self-building yet**.
 
 Possibly outdated list of roles where self-building the Docker image is currently possible:
 - `matrix-synapse`
-- `matrix-ketesa`
+- `matrix-synapse-admin`
 - `matrix-client-element`
-- `hydrogen`
+- `matrix-client-hydrogen`
 - `cinny`
-- `sable`
 - `matrix-registration`
-- `coturn`
+- `matrix-coturn`
 - `matrix-corporal`
+- `matrix-dimension`
 - `exim-relay`
 - `matrix-bridge-hookshot`
 - `matrix-bridge-appservice-irc`
+- `matrix-bridge-appservice-slack`
 - `matrix-bridge-beeper-linkedin`
 - `matrix-bridge-mautrix-googlechat`
 - `matrix-bridge-mautrix-telegram`

examples/hosts

@@ -1,3 +1,6 @@
+# We explicitly ask for your server's external IP address, because the same value is used for configuring coturn.
+# If you'd rather use a local IP here, make sure to set up `matrix_coturn_turn_external_ip_address`.
+#
 # To connect using a non-root user (and elevate to root with sudo later),
 # replace `ansible_ssh_user=root` with something like this: `ansible_ssh_user=username ansible_become=true ansible_become_user=root`.
 # If sudo requires a password, either add `ansible_become_password=PASSWORD_HERE` to the host line
@@ -15,4 +18,4 @@
 # to the host line below.
 
 [matrix_servers]
-matrix.example.com ansible_host=<your-server's domain name or IP address> ansible_ssh_user=root
+matrix.example.com ansible_host=<your-server's external IP address> ansible_ssh_user=root

examples/reverse-proxies/apache/README.md

@@ -19,4 +19,4 @@ To get started, first follow the [front the integrated reverse-proxy webserver w
 `matrix-domain.conf` contains configuration for the Matrix domain, which handles both the Client-Server API (port `443`) and the Matrix Federation API (port `8448`).
 
 `matrix-client-element.conf` is an example for when you're hosting Element Web at `element.example.com`.
-This configuration can also be used as an example for handling other domains, depending on the services you enable with the playbook (e.g. `etherpad.example.com`, etc).
+This configuration can also be used as an example for handling other domains, depending on the services you enable with the playbook (e.g. `dimension.example.com`, etc).

examples/reverse-proxies/nginx/README.md

@@ -22,4 +22,4 @@ Copy the [matrix.conf](matrix.conf) file to your nginx server's filesystem, modi
 
 This configuration **disables SSL certificate retrieval**, so you will **need to obtain SSL certificates manually** (e.g. by using [certbot](https://certbot.eff.org/)) and set the appropriate path in `matrix.conf`. In the example nginx configuration, a single certificate is used for all subdomains (`matrix.example.com`, `element.example.com`, etc.). For your setup, may wish to change this and use separate `server` blocks and separate certificate files for each host.
 
-Also note that your copy of the `matrix.conf` file has to be adapted to whatever services you are using. For example, remove `element.example.com` from the `server_name` list if you don't use [Element Web](../../../docs/configuring-playbook-client-element-web.md) client or add `etherpad.example.com` to it if you do use [Etherpad](../../../docs/configuring-playbook-etherpad.md).
+Also note that your copy of the `matrix.conf` file has to be adapted to whatever services you are using. For example, remove `element.example.com` from the `server_name` list if you don't use [Element Web](../../../docs/configuring-playbook-client-element-web.md) client or add `dimension.example.com` to it if you do use the [Dimension](../../../docs/configuring-playbook-dimension.md) integration manager.

examples/reverse-proxies/nginx/matrix.conf

@@ -19,7 +19,7 @@ server {
     # TODO: add/remove services and their subdomains if you use/don't use them
     # this example is using hosting something on the base domain and an Element Web client, so example.com and element.example.com are listed in addition to matrix.example.com
     # if you don't use those, you can remove them
-    # if you use e.g. Etherpad on etherpad.example.com, add etherpad.example.com to the server_name list
+    # if you use e.g. Dimension on dimension.example.com, add dimension.example.com to the server_name list
     server_name example.com matrix.example.com element.example.com;
 
     location / {

examples/vars.yml

@@ -1,9 +1,4 @@
 ---
-# This variable acknowledges that you've reviewed breaking changes up to this version.
-# The playbook will fail if this is outdated, guiding you through what changed.
-# See the changelog: https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/CHANGELOG.md
-matrix_playbook_migration_validated_version: v2026.04.03.0
-
 # The bare domain name which represents your Matrix identity.
 # Matrix user IDs for your server will be of the form (`@alice:example.com`).
 #
@@ -58,10 +53,18 @@ devture_systemd_docker_base_ipv6_enabled: true
 # The value used here must be shorter than 100 characters.
 postgres_connection_password: ''
 
-# You can limit heavy room joins on constrained hosts.
+# By default, we configure coturn's external IP address using the value specified for `ansible_host` in your `inventory/hosts` file.
-# See:
+# If this value is an external IP address, you can skip this section.
-# docs/configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts
 #
-# matrix_synapse_limit_remote_rooms_enabled: true
+# If `ansible_host` is not the server's external IP address, you have 2 choices:
-# matrix_synapse_limit_remote_rooms_complexity: 1.0
+# 1. Uncomment the line below, to allow IP address auto-detection to happen (more on this below)
-# matrix_synapse_limit_remote_rooms_admins_can_join: false
+# 2. Uncomment and adjust the line below to specify an IP address manually
+#
+# By default, auto-detection will be attempted using the `https://ifconfig.co/json` API.
+# Default values for this are specified in `matrix_coturn_turn_external_ip_address_auto_detection_*` variables in the coturn role
+# (see `roles/custom/matrix-coturn/defaults/main.yml`).
+#
+# If your server has multiple IP addresses, you may define them in another variable which allows a list of addresses.
+# Example: `matrix_coturn_turn_external_ip_addresses: ['1.2.3.4', '4.5.6.7']`
+#
+# matrix_coturn_turn_external_ip_address: ''

flake.nix

@@ -19,7 +19,6 @@
           devShells.default = mkShell {
             buildInputs = [
               just
-              mise
               ansible
             ];
             shellHook = ''

i18n/locales/bg/LC_MESSAGES/README.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version:  matrix-docker-ansible-deploy\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:59+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: 2024-12-20 14:56+0200\n"
 "Last-Translator: \n"
 "Language: bg\n"
@@ -19,11 +19,10 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
 #: ../../../README.md:1
-#, fuzzy
+msgid "[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)"
-msgid "[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com&fetchMode=summary)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate) [![REUSE status](https://api.reuse.software/badge/github.com/spantaleev/matrix-docker-ansible-deploy)](https://api.reuse.software/info/github.com/spantaleev/matrix-docker-ansible-deploy)"
 msgstr "[![Matrix стая за поддържка](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)"
 
 #: ../../../README.md:1
@@ -34,10 +33,6 @@ msgstr "Matrix стая за поддръжка"
 msgid "donate"
 msgstr "дарения"
 
-#: ../../../README.md:1
-msgid "REUSE status"
-msgstr ""
-
 #: ../../../README.md:3
 msgid "Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker"
 msgstr "Настройка на Matrix (отворена мрежа за сигурна децентрализирана комуникация) чрез Ansible и Docker"
@@ -184,16 +179,16 @@ msgstr "[Връзка](docs/configuring-playbook-conduit.md)"
 
 #: ../../../README.md
 #, fuzzy
-msgid "[continuwuity](https://continuwuity.org)"
+msgid "[conduwuit](https://conduwuit.puppyirl.gay/)"
 msgstr "[Conduit](https://conduit.rs)"
 
 #: ../../../README.md
-msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network."
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit is a fork of Conduit."
 msgstr ""
 
 #: ../../../README.md
 #, fuzzy
-msgid "[Link](docs/configuring-playbook-continuwuity.md)"
+msgid "[Link](docs/configuring-playbook-conduwuit.md)"
 msgstr "[Връзка](docs/configuring-playbook-conduit.md)"
 
 #: ../../../README.md
@@ -252,15 +247,6 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-client-cinny.md)"
 msgstr ""
 
-#: ../../../README.md
-msgid "[Sable](https://github.com/7w1/sable)"
-msgstr ""
-
-#: ../../../README.md
-#, fuzzy
-msgid "[Link](docs/configuring-playbook-client-sable.md)"
-msgstr "[Връзка](docs/configuring-playbook-synapse.md)"
-
 #: ../../../README.md
 msgid "[SchildiChat Web](https://schildi.chat/)"
 msgstr ""
@@ -273,24 +259,11 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-client-schildichat-web.md)"
 msgstr ""
 
-#: ../../../README.md
+#: ../../../README.md:69
-msgid "[FluffyChat Web](https://fluffychat.im/)"
-msgstr ""
-
-#: ../../../README.md
-msgid "The cutest messenger in Matrix"
-msgstr ""
-
-#: ../../../README.md
-#, fuzzy
-msgid "[Link](docs/configuring-playbook-client-fluffychat-web.md)"
-msgstr "[Връзка](docs/configuring-playbook-conduit.md)"
-
-#: ../../../README.md:71
 msgid "Server Components"
 msgstr ""
 
-#: ../../../README.md:73
+#: ../../../README.md:71
 msgid "Services that run on the server to make the various parts of your installation work."
 msgstr ""
 
@@ -306,12 +279,24 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-external-postgres.md)"
 msgstr ""
 
+#: ../../../README.md
+msgid "[coturn](https://github.com/coturn/coturn)"
+msgstr ""
+
+#: ../../../README.md
+msgid "STUN/TURN server for WebRTC audio/video calls"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-turn.md)"
+msgstr ""
+
 #: ../../../README.md
 msgid "[Traefik](https://doc.traefik.io/traefik/)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. [Using your own webserver](docs/configuring-playbook-own-webserver.md) is also possible."
+msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](docs/configuring-playbook-own-webserver.md)"
 msgstr ""
 
 #: ../../../README.md
@@ -343,15 +328,15 @@ msgid "[Link](docs/configuring-playbook-email.md)"
 msgstr ""
 
 #: ../../../README.md
-msgid "[coturn](https://github.com/coturn/coturn)"
+msgid "[ma1sd](https://github.com/ma1uta/ma1sd)"
 msgstr ""
 
 #: ../../../README.md
-msgid "STUN/TURN server for WebRTC audio/video calls"
+msgid "Matrix Identity Server"
 msgstr ""
 
 #: ../../../README.md
-msgid "[Link](docs/configuring-playbook-turn.md)"
+msgid "[Link](docs/configuring-playbook-ma1sd.md)"
 msgstr ""
 
 #: ../../../README.md
@@ -366,24 +351,11 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-dynamic-dns.md)"
 msgstr "[Връзка](docs/configuring-playbook-dynamic-dns.md)"
 
-#: ../../../README.md
+#: ../../../README.md:83
-msgid "Matrix RTC stack"
-msgstr ""
-
-#: ../../../README.md
-msgid "Supporting components ([LiveKit Server](docs/configuring-playbook-livekit-server.md) and [LiveKit JWT Service](docs/configuring-playbook-livekit-jwt-service.md)) for in-app audio/video calls for Matrix clients"
-msgstr ""
-
-#: ../../../README.md
-#, fuzzy
-msgid "[Link](docs/configuring-playbook-matrix-rtc.md)"
-msgstr "[Връзка](docs/configuring-playbook-dynamic-dns.md)"
-
-#: ../../../README.md:85
 msgid "Authentication"
 msgstr ""
 
-#: ../../../README.md:87
+#: ../../../README.md:85
 msgid "Extend and modify how users are authenticated on your homeserver."
 msgstr ""
 
@@ -428,7 +400,7 @@ msgid "[matrix-ldap-registration-proxy](https://gitlab.com/activism.internationa
 msgstr ""
 
 #: ../../../README.md
-msgid "Proxy that handles Matrix registration requests and forwards them to LDAP"
+msgid "A proxy that handles Matrix registration requests and forwards them to LDAP."
 msgstr ""
 
 #: ../../../README.md
@@ -440,7 +412,7 @@ msgid "[matrix-registration](https://github.com/ZerataX/matrix-registration)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Simple python application to have a token based Matrix registration"
+msgid "A simple python application to have a token based Matrix registration"
 msgstr ""
 
 #: ../../../README.md
@@ -448,7 +420,7 @@ msgid "[Link](docs/configuring-playbook-matrix-registration.md)"
 msgstr ""
 
 #: ../../../README.md
-msgid "[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service)"
+msgid "[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (UVS)"
 msgstr ""
 
 #: ../../../README.md
@@ -464,18 +436,18 @@ msgid "[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispa
 msgstr ""
 
 #: ../../../README.md
-msgid "Spam checker module"
+msgid "A spam checker module"
 msgstr ""
 
 #: ../../../README.md
 msgid "[Link](docs/configuring-playbook-synapse-simple-antispam.md)"
 msgstr ""
 
-#: ../../../README.md:99
+#: ../../../README.md:97
 msgid "File Storage"
 msgstr ""
 
-#: ../../../README.md:101
+#: ../../../README.md:99
 msgid "Use alternative file storage to the default `media_store` folder."
 msgstr ""
 
@@ -504,18 +476,18 @@ msgid "[matrix-media-repo](https://github.com/turt2live/matrix-media-repo)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
+msgid "matrix-media-repo is a highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
 msgstr ""
 
 #: ../../../README.md
 msgid "[Link](docs/configuring-playbook-matrix-media-repo.md)"
 msgstr ""
 
-#: ../../../README.md:109
+#: ../../../README.md:107
 msgid "Bridges"
 msgstr ""
 
-#: ../../../README.md:111
+#: ../../../README.md:109
 msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
 msgstr ""
 
@@ -591,19 +563,6 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bridge-mautrix-wsproxy.md)"
 msgstr ""
 
-#: ../../../README.md
-msgid "[mautrix-bluesky](https://github.com/mautrix/bluesky)"
-msgstr ""
-
-#: ../../../README.md
-msgid "Bridge to [Bluesky](https://bsky.social/)"
-msgstr ""
-
-#: ../../../README.md
-#, fuzzy
-msgid "[Link](docs/configuring-playbook-bridge-mautrix-bluesky.md)"
-msgstr "[Връзка](docs/configuring-playbook-conduit.md)"
-
 #: ../../../README.md
 msgid "[mautrix-twitter](https://github.com/mautrix/twitter)"
 msgstr ""
@@ -700,6 +659,14 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bridge-appservice-discord.md)"
 msgstr ""
 
+#: ../../../README.md
+msgid "[matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-appservice-slack.md)"
+msgstr ""
+
 #: ../../../README.md
 msgid "[matrix-hookshot](https://github.com/matrix-org/matrix-hookshot)"
 msgstr ""
@@ -724,19 +691,6 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bridge-matrix-bridge-sms.md)"
 msgstr ""
 
-#: ../../../README.md
-msgid "[matrix-steam-bridge](https://github.com/jasonlaguidice/matrix-steam-bridge)"
-msgstr ""
-
-#: ../../../README.md
-msgid "Bridge to [Steam](https://steampowered.com/)"
-msgstr ""
-
-#: ../../../README.md
-#, fuzzy
-msgid "[Link](docs/configuring-playbook-bridge-steam.md)"
-msgstr "[Връзка](docs/configuring-playbook-synapse.md)"
-
 #: ../../../README.md
 msgid "[matrix-wechat](https://github.com/duo/matrix-wechat)"
 msgstr ""
@@ -761,6 +715,62 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bridge-heisenbridge.md)"
 msgstr ""
 
+#: ../../../README.md
+msgid "[go-skype-bridge](https://github.com/kelaresg/go-skype-bridge)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Skype](https://www.skype.com)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Slack](https://slack.com)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
 #: ../../../README.md
 msgid "[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme)"
 msgstr ""
@@ -774,7 +784,7 @@ msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-groupme.md)"
 msgstr ""
 
 #: ../../../README.md
-msgid "[mx-puppet-steam](https://codeberg.org/icewind/mx-puppet-steam)"
+msgid "[mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam)"
 msgstr ""
 
 #: ../../../README.md
@@ -797,11 +807,11 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bridge-postmoogle.md)"
 msgstr ""
 
-#: ../../../README.md:139
+#: ../../../README.md:141
 msgid "Bots"
 msgstr ""
 
-#: ../../../README.md:141
+#: ../../../README.md:143
 msgid "Bots provide various additional functionality to your installation."
 msgstr ""
 
@@ -810,7 +820,7 @@ msgid "[baibot](https://github.com/etkecc/baibot)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
+msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
 msgstr ""
 
 #: ../../../README.md
@@ -846,7 +856,7 @@ msgid "[maubot](https://github.com/maubot/maubot)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Plugin-based Matrix bot system"
+msgid "A plugin-based Matrix bot system"
 msgstr ""
 
 #: ../../../README.md
@@ -858,7 +868,7 @@ msgid "[Honoroit](https://github.com/etkecc/honoroit)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Helpdesk bot"
+msgid "A helpdesk bot"
 msgstr ""
 
 #: ../../../README.md
@@ -870,7 +880,7 @@ msgid "[Mjolnir](https://github.com/matrix-org/mjolnir)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Moderation tool for Matrix"
+msgid "A moderation tool for Matrix"
 msgstr ""
 
 #: ../../../README.md
@@ -882,7 +892,7 @@ msgid "[Draupnir](https://github.com/the-draupnir-project/Draupnir)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Moderation tool for Matrix (Fork of Mjolnir)"
+msgid "A moderation tool for Matrix (Fork of Mjolnir)"
 msgstr ""
 
 #: ../../../README.md
@@ -901,11 +911,11 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bot-buscarron.md)"
 msgstr ""
 
-#: ../../../README.md:154
+#: ../../../README.md:156
 msgid "Administration"
 msgstr ""
 
-#: ../../../README.md:156
+#: ../../../README.md:158
 msgid "Services that help you in administrating and monitoring your Matrix installation."
 msgstr ""
 
@@ -934,17 +944,16 @@ msgid "[Link](docs/configuring-playbook-matrix-authentication-service.md)"
 msgstr ""
 
 #: ../../../README.md
-msgid "[Ketesa](https://github.com/etkecc/ketesa)"
+msgid "[synapse-admin](https://github.com/etkecc/synapse-admin)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Fully-featured web UI for administrating your Matrix homeserver — users, rooms, media, sessions, and more"
+msgid "A web UI tool for administrating users and rooms on your Matrix server"
 msgstr ""
 
 #: ../../../README.md
-#, fuzzy
+msgid "[Link](docs/configuring-playbook-synapse-admin.md)"
-msgid "[Link](docs/configuring-playbook-ketesa.md)"
+msgstr ""
-msgstr "[Връзка](docs/configuring-playbook-synapse.md)"
 
 #: ../../../README.md
 msgid "Metrics and Graphs"
@@ -955,7 +964,7 @@ msgid "Consists of the [Prometheus](https://prometheus.io) time-series database
 msgstr ""
 
 #: ../../../README.md
-msgid "[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-nginx-logs-optional))"
+msgid "[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md))"
 msgstr ""
 
 #: ../../../README.md
@@ -994,20 +1003,44 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-synapse-usage-exporter.md)"
 msgstr ""
 
-#: ../../../README.md:168
+#: ../../../README.md:170
 msgid "Misc"
 msgstr ""
 
-#: ../../../README.md:170
+#: ../../../README.md:172
 msgid "Various services that don't fit any other categories."
 msgstr ""
 
+#: ../../../README.md
+msgid "[sliding-sync](https://github.com/matrix-org/sliding-sync)"
+msgstr ""
+
+#: ../../../README.md
+msgid "(Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` and Conduit > `0.6.0`) Sliding Sync support for clients which require it (e.g. old Element X versions before Simplified Sliding Sync was developed)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-sliding-sync-proxy.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A Synapse module to automatically accept invites."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-synapse-auto-accept-invite.md)"
+msgstr ""
+
 #: ../../../README.md
 msgid "[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Cli tool that automatically compresses `state_groups` database table in background"
+msgid "A cli tool that automatically compresses `state_groups` database table in background."
 msgstr ""
 
 #: ../../../README.md
@@ -1026,25 +1059,12 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-matrix-corporal.md)"
 msgstr ""
 
-#: ../../../README.md
-msgid "[Matrix.to](https://github.com/matrix-org/matrix.to)"
-msgstr ""
-
-#: ../../../README.md
-msgid "Simple URL redirection service for the Matrix ecosystem"
-msgstr ""
-
-#: ../../../README.md
-#, fuzzy
-msgid "[Link](docs/configuring-playbook-matrixto.md)"
-msgstr "[Връзка](docs/configuring-playbook-synapse.md)"
-
 #: ../../../README.md
 msgid "[Etherpad](https://etherpad.org)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Open source collaborative text editor"
+msgid "An open source collaborative text editor"
 msgstr ""
 
 #: ../../../README.md
@@ -1056,7 +1076,7 @@ msgid "[Jitsi](https://jitsi.org/)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Open source video-conferencing platform"
+msgid "An open source video-conferencing platform"
 msgstr ""
 
 #: ../../../README.md
@@ -1068,7 +1088,7 @@ msgid "[Cactus Comments](https://cactus.chat)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Federated comment system built on Matrix"
+msgid "A federated comment system built on Matrix"
 msgstr ""
 
 #: ../../../README.md
@@ -1080,7 +1100,7 @@ msgid "[Pantalaimon](https://github.com/matrix-org/pantalaimon)"
 msgstr ""
 
 #: ../../../README.md
-msgid "E2EE aware proxy daemon"
+msgid "An E2EE aware proxy daemon"
 msgstr ""
 
 #: ../../../README.md
@@ -1111,70 +1131,54 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-ntfy.md)"
 msgstr ""
 
-#: ../../../README.md
+#: ../../../README.md:187
-msgid "[Element Call](https://github.com/element-hq/element-call)"
-msgstr ""
-
-#: ../../../README.md
-msgid "A native Matrix video conferencing application"
-msgstr ""
-
-#: ../../../README.md
-#, fuzzy
-msgid "[Link](docs/configuring-playbook-element-call.md)"
-msgstr "[Връзка](docs/configuring-playbook-synapse.md)"
-
-#: ../../../README.md:185
 msgid "🆕 Changes"
 msgstr ""
 
-#: ../../../README.md:187
+#: ../../../README.md:189
 msgid "This playbook evolves over time, sometimes with backward-incompatible changes."
 msgstr "Този плейбук се развива във времето и понякога съдържа обратно-несъвместими промени."
 
-#: ../../../README.md:189
+#: ../../../README.md:191
 msgid "When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new."
 msgstr ""
 
-#: ../../../README.md:191
+#: ../../../README.md:193
 msgid "🆘 Support"
 msgstr ""
 
-#: ../../../README.md:193
+#: ../../../README.md:195
 msgid "Matrix room: [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)"
 msgstr ""
 
-#: ../../../README.md:195
+#: ../../../README.md:197
 msgid "IRC channel: `#matrix-docker-ansible-deploy` on the [Libera Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)"
 msgstr ""
 
-#: ../../../README.md:197
+#: ../../../README.md:199
 msgid "GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues)"
 msgstr ""
 
-#: ../../../README.md:199
+#: ../../../README.md:201
 msgid "🌐 Translation"
 msgstr ""
 
-#: ../../../README.md:201
+#: ../../../README.md:203
 msgid "See the [i18n/README.md](i18n/README.md) file for more information about translation."
 msgstr "Вижте файла [i18n/README.md](i18n/README.md) за повече информация относно превода."
 
-#: ../../../README.md:203
+#: ../../../README.md:205
 msgid "Translations are still work in progress."
 msgstr "Все още се работи по преводите."
 
-#: ../../../README.md:205
+#: ../../../README.md:207
 msgid "🤝 Related"
 msgstr ""
 
-#: ../../../README.md:207
+#: ../../../README.md:209
 msgid "You may also be interested in [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) - another Ansible playbook for self-hosting non-Matrix services (see its [List of supported services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md))."
 msgstr ""
 
-#: ../../../README.md:209
+#: ../../../README.md:211
 msgid "mash-playbook also makes use of [Traefik](./docs/configuring-playbook-traefik.md) as its reverse-proxy, so with minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md), you can make matrix-docker-ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix services on the same server."
 msgstr ""
-
-#~ msgid "[conduwuit](https://conduwuit.puppyirl.gay/)"
-#~ msgstr "[Conduit](https://conduit.rs)"

i18n/locales/bg/LC_MESSAGES/docs/README.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: bg\n"
@@ -19,156 +19,156 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/README.md:10
+#: ../../../docs/README.md:1
 msgid "Table of Contents"
 msgstr ""
 
-#: ../../../docs/README.md:12
+#: ../../../docs/README.md:3
-msgid "⬇️ Installation guides <!-- NOTE: the 🚀 emoji is used by \"Getting started\" on README.md -->"
+msgid "⬇️ Installaton guides <!-- NOTE: the 🚀 emoji is used by \"Getting started\" on README.md -->"
 msgstr ""
 
-#: ../../../docs/README.md:14
+#: ../../../docs/README.md:5
 msgid "There are two installation guides available for beginners and advanced users."
 msgstr ""
 
-#: ../../../docs/README.md:16
+#: ../../../docs/README.md:7
 msgid "⚡ **[Quick start](quick-start.md) (for beginners)**: this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"."
 msgstr ""
 
-#: ../../../docs/README.md:18
+#: ../../../docs/README.md:9
 msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide."
 msgstr ""
 
-#: ../../../docs/README.md:20
+#: ../../../docs/README.md:11
 msgid "[Prerequisites](prerequisites.md)"
 msgstr ""
 
-#: ../../../docs/README.md:22
+#: ../../../docs/README.md:13
-msgid "[Configuring DNS settings](configuring-dns.md)"
+msgid "[Configuring your DNS settings](configuring-dns.md)"
 msgstr ""
 
-#: ../../../docs/README.md:24
+#: ../../../docs/README.md:15
 msgid "[Getting the playbook](getting-the-playbook.md)"
 msgstr ""
 
-#: ../../../docs/README.md:26
+#: ../../../docs/README.md:17
 msgid "[Configuring the playbook](configuring-playbook.md)"
 msgstr ""
 
-#: ../../../docs/README.md:28
+#: ../../../docs/README.md:19
 msgid "[Installing](installing.md)"
 msgstr ""
 
-#: ../../../docs/README.md:30
+#: ../../../docs/README.md:21
 msgid "🛠️ Configuration options"
 msgstr ""
 
-#: ../../../docs/README.md:37
+#: ../../../docs/README.md:28
 msgid "You can check useful documentation for configuring components here: [Configuring the playbook](configuring-playbook.md)"
 msgstr ""
 
-#: ../../../docs/README.md:39
+#: ../../../docs/README.md:30
 msgid "[Administration](configuring-playbook.md#administration) — services that help you in administrating and monitoring your Matrix installation"
 msgstr ""
 
-#: ../../../docs/README.md:41
+#: ../../../docs/README.md:32
 msgid "[Authentication and user-related](configuring-playbook.md#authentication-and-user-related) — extend and modify how users are authenticated on your homeserver"
 msgstr ""
 
-#: ../../../docs/README.md:43
+#: ../../../docs/README.md:34
 msgid "[Bots](configuring-playbook.md#bots) — bots provide various additional functionality to your installation"
 msgstr ""
 
-#: ../../../docs/README.md:45
+#: ../../../docs/README.md:36
 msgid "[Bridges](configuring-playbook.md#bridging-other-networks) — bridges can be used to connect your Matrix installation with third-party communication networks"
 msgstr ""
 
-#: ../../../docs/README.md:47
+#: ../../../docs/README.md:38
 msgid "[Clients](configuring-playbook.md#clients) — web clients for Matrix that you can host on your own domains"
 msgstr ""
 
-#: ../../../docs/README.md:49
+#: ../../../docs/README.md:40
 msgid "[Core service adjustments](configuring-playbook.md#core-service-adjustments) — backbone of your Matrix system"
 msgstr ""
 
-#: ../../../docs/README.md:51
+#: ../../../docs/README.md:42
 msgid "[File Storage](configuring-playbook.md#file-storage) — use alternative file storage to the default `media_store` folder"
 msgstr ""
 
-#: ../../../docs/README.md:55
+#: ../../../docs/README.md:46
 msgid "[Other specialized services](configuring-playbook.md#other-specialized-services) — various services that don't fit any other categories"
 msgstr ""
 
-#: ../../../docs/README.md:57
+#: ../../../docs/README.md:48
 msgid "👨‍🔧 Maintenance"
 msgstr ""
 
-#: ../../../docs/README.md:59
+#: ../../../docs/README.md:50
 msgid "If your server and services experience issues, feel free to come to [our support room](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) and ask for help."
 msgstr ""
 
-#: ../../../docs/README.md:63
+#: ../../../docs/README.md:54
+msgid "[Checking if services work](maintenance-checking-services.md)"
+msgstr ""
+
+#: ../../../docs/README.md:56
 msgid "[Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)"
 msgstr ""
 
-#: ../../../docs/README.md:65
+#: ../../../docs/README.md:58
 msgid "[PostgreSQL maintenance](maintenance-postgres.md)"
 msgstr ""
 
-#: ../../../docs/README.md:67
+#: ../../../docs/README.md:60
 msgid "[Synapse maintenance](maintenance-synapse.md)"
 msgstr ""
 
-#: ../../../docs/README.md:69
+#: ../../../docs/README.md:62
 msgid "[Upgrading services](maintenance-upgrading-services.md)"
 msgstr ""
 
-#: ../../../docs/README.md:71
+#: ../../../docs/README.md:64
 msgid "Other documentation pages <!-- NOTE: this header's title and the section below need optimization -->"
 msgstr ""
 
-#: ../../../docs/README.md:73
+#: ../../../docs/README.md:66
 msgid "ℹ️ **[FAQ](faq.md)** — various Frequently Asked Questions about Matrix, with a focus on this Ansible playbook"
 msgstr ""
 
-#: ../../../docs/README.md:77
+#: ../../../docs/README.md:70
 msgid "[Alternative architectures](alternative-architectures.md)"
 msgstr ""
 
-#: ../../../docs/README.md:79
+#: ../../../docs/README.md:72
 msgid "[Container images used by the playbook](container-images.md)"
 msgstr ""
 
-#: ../../../docs/README.md:81
+#: ../../../docs/README.md:74
 msgid "[Obtaining an Access Token](obtaining-access-tokens.md)"
 msgstr ""
 
-#: ../../../docs/README.md:83
+#: ../../../docs/README.md:76
 msgid "[Playbook tags](playbook-tags.md)"
 msgstr ""
 
-#: ../../../docs/README.md:85
+#: ../../../docs/README.md:78
 msgid "[Registering users](registering-users.md)"
 msgstr ""
 
-#: ../../../docs/README.md:87
+#: ../../../docs/README.md:80
 msgid "[Running `just` commands](just.md)"
 msgstr ""
 
-#: ../../../docs/README.md:89
+#: ../../../docs/README.md:82
 msgid "[Self-building](self-building.md)"
 msgstr ""
 
-#: ../../../docs/README.md:91
+#: ../../../docs/README.md:84
 msgid "[Uninstalling](uninstalling.md)"
 msgstr ""
 
-#: ../../../docs/README.md:93
+#: ../../../docs/README.md:86
 msgid "[Updating users passwords](updating-users-passwords.md)"
 msgstr ""
-
-#: ../../../docs/README.md:95
-msgid "[Using Ansible for the playbook](ansible.md)"
-msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: bg\n"
@@ -19,459 +19,431 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:8
+#: ../../../docs/configuring-playbook-bot-baibot.md:1
 msgid "Setting up baibot (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:15
+#: ../../../docs/configuring-playbook-bot-baibot.md:8
 msgid "🤖 [baibot](https://github.com/etkecc/baibot) (pronounced bye-bot) is a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:17
+#: ../../../docs/configuring-playbook-bot-baibot.md:10
 msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as many well as other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:19
+#: ../../../docs/configuring-playbook-bot-baibot.md:12
 msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to [matrix-chatgpt-bot](./configuring-playbook-bot-chatgpt.md). See the [baibot](https://github.com/etkecc/baibot) project and its documentation for more information."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:21
+#: ../../../docs/configuring-playbook-bot-baibot.md:14
 msgid "Prerequisites"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:23
+#: ../../../docs/configuring-playbook-bot-baibot.md:16
 msgid "API access to one or more LLM [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:25
+#: ../../../docs/configuring-playbook-bot-baibot.md:18
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:27
+#: ../../../docs/configuring-playbook-bot-baibot.md:20
 msgid "There are **a lot of configuration options** (some required, some possibly required, some optional), so they're **split into multiple sections below**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:30
+#: ../../../docs/configuring-playbook-bot-baibot.md:23
 msgid "[Base configuration](#base-configuration)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:31
+#: ../../../docs/configuring-playbook-bot-baibot.md:24
 msgid "[👮‍♂️ Administrator configuration](#️-administrator-configuration)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:32
+#: ../../../docs/configuring-playbook-bot-baibot.md:25
 msgid "[👥 Initial users configuration](#-initial-users-configuration)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:33
+#: ../../../docs/configuring-playbook-bot-baibot.md:26
 msgid "[🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:34
+#: ../../../docs/configuring-playbook-bot-baibot.md:27
 msgid "[🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:36
+#: ../../../docs/configuring-playbook-bot-baibot.md:29
 msgid "Depending on your current `vars.yml` file and desired configuration, **you may require more than just the [base configuration](#base-configuration)**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:38
+#: ../../../docs/configuring-playbook-bot-baibot.md:31
 msgid "Base configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:40
+#: ../../../docs/configuring-playbook-bot-baibot.md:33
 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:42
+#: ../../../docs/configuring-playbook-bot-baibot.md:71
-msgid "Authentication can be configured in one of two mutually-exclusive ways:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-baibot.md:44
-msgid "**Password authentication** (`matrix_bot_baibot_config_user_password`) - recommended for most playbook-managed setups, because it integrates with automatic user creation flow used by the playbook, and auto-creates the bot account"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-baibot.md:45
-msgid "**Access-token authentication** (`matrix_bot_baibot_config_user_access_token` + `matrix_bot_baibot_config_user_device_id`) - useful for specific [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md)/OIDC setups where password authentication is not available or not desired"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-baibot.md:47
-msgid "Even when [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) is enabled, password authentication is still typically the best fit for baibot if you're using a playbook-managed bot account."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-baibot.md:49
-msgid "For upstream details, see baibot's [🔐 Authentication](https://github.com/etkecc/baibot/blob/main/docs/configuration/authentication.md) documentation."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-baibot.md:97
 msgid "As mentioned above, **this may not be enough**. Continue with the configuration sections below."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:99
+#: ../../../docs/configuring-playbook-bot-baibot.md:73
 msgid "👮‍♂️ Administrator configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:101
+#: ../../../docs/configuring-playbook-bot-baibot.md:75
-#: ../../../docs/configuring-playbook-bot-baibot.md:125
+#: ../../../docs/configuring-playbook-bot-baibot.md:99
 msgid "This is an addition to the [base configuration](#base-configuration)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:103
+#: ../../../docs/configuring-playbook-bot-baibot.md:77
 msgid "To specify who is considered a bot [👮‍♂️ Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators), you either need to specify `matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The latter is a single variable which affects all bridges and bots."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:105
+#: ../../../docs/configuring-playbook-bot-baibot.md:79
 msgid "If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:107
+#: ../../../docs/configuring-playbook-bot-baibot.md:81
-#: ../../../docs/configuring-playbook-bot-baibot.md:136
+#: ../../../docs/configuring-playbook-bot-baibot.md:110
 msgid "**If necessary**, add the following configuration to your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:121
+#: ../../../docs/configuring-playbook-bot-baibot.md:95
 msgid "👥 Initial users configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:123
+#: ../../../docs/configuring-playbook-bot-baibot.md:97
 msgid "By default, **all users on your homeserver are considered allowed users**. If that's OK, you can skip this section."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:127
+#: ../../../docs/configuring-playbook-bot-baibot.md:101
 msgid "To specify who is considered a bot [👥 User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), you may:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:129
+#: ../../../docs/configuring-playbook-bot-baibot.md:103
 msgid "define an **initial** value for `matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible variable, as shown below"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:130
+#: ../../../docs/configuring-playbook-bot-baibot.md:104
 msgid "configure the list at runtime via the bot's `!bai access set-users SPACE_SEPARATED_PATTERNS` command"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:132
+#: ../../../docs/configuring-playbook-bot-baibot.md:106
 msgid "Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is optional, but it can be useful to pre-configure the bot with a list of users who should have access to the bot's features."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:134
+#: ../../../docs/configuring-playbook-bot-baibot.md:108
 msgid "**Note**: Once initially configured, the allowed users list **cannot be managed via Ansible anymore**. It can only be managed subsequently via bot commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:148
+#: ../../../docs/configuring-playbook-bot-baibot.md:122
 msgid "🤖 Configuring agents via Ansible"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:150
+#: ../../../docs/configuring-playbook-bot-baibot.md:124
 msgid "You are **not required** to define agents [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration) via Ansible. **To get started quickly**, you can **skip this section and define agents at runtime via chat commands** (following the bot's guidance)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:152
+#: ../../../docs/configuring-playbook-bot-baibot.md:126
 msgid "Privileged users (like the [👮‍♂️ Administrator](#️-administrator-configuration), but potentially others too — see the upstream [🔒 access](https://github.com/etkecc/baibot/blob/main/docs/access.md) documentation) can **define agents dynamically at any time** via chat commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:154
+#: ../../../docs/configuring-playbook-bot-baibot.md:128
 msgid "The Ansible role includes preset variables for easily enabling some [🤖 agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on various [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) (e.g. OpenAI, etc)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:156
+#: ../../../docs/configuring-playbook-bot-baibot.md:130
 msgid "Besides the presets, the Ansible role also includes support for configuring additional statically-defined agents via the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:158
+#: ../../../docs/configuring-playbook-bot-baibot.md:132
 msgid "Agents defined statically and those created dynamically (via chat) are named differently, so **conflict cannot arise**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:160
+#: ../../../docs/configuring-playbook-bot-baibot.md:134
 msgid "Depending on your propensity for [GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to define agents statically via Ansible, or you may wish to do it dynamically via chat."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:162
+#: ../../../docs/configuring-playbook-bot-baibot.md:136
 msgid "Before proceeding, we recommend reading the upstream documentation on [How to choose a provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#how-to-choose-a-provider). In short, it's probably best to go with [OpenAI](#openai)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:164
+#: ../../../docs/configuring-playbook-bot-baibot.md:138
 msgid "Anthropic"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:166
+#: ../../../docs/configuring-playbook-bot-baibot.md:140
 msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Anthropic provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic) with the help of the playbook's preset variables."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:168
+#: ../../../docs/configuring-playbook-bot-baibot.md:142
-#: ../../../docs/configuring-playbook-bot-baibot.md:192
+#: ../../../docs/configuring-playbook-bot-baibot.md:166
-#: ../../../docs/configuring-playbook-bot-baibot.md:223
+#: ../../../docs/configuring-playbook-bot-baibot.md:197
-#: ../../../docs/configuring-playbook-bot-baibot.md:251
+#: ../../../docs/configuring-playbook-bot-baibot.md:225
 msgid "Here's an example **addition** to your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:184
+#: ../../../docs/configuring-playbook-bot-baibot.md:158
+#: ../../../docs/configuring-playbook-bot-baibot.md:189
 #: ../../../docs/configuring-playbook-bot-baibot.md:215
-#: ../../../docs/configuring-playbook-bot-baibot.md:241
+#: ../../../docs/configuring-playbook-bot-baibot.md:243
-#: ../../../docs/configuring-playbook-bot-baibot.md:275
 msgid "If you'd like to use more than one model, take a look at the [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset) section below."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:186
+#: ../../../docs/configuring-playbook-bot-baibot.md:160
+#: ../../../docs/configuring-playbook-bot-baibot.md:191
 #: ../../../docs/configuring-playbook-bot-baibot.md:217
-#: ../../../docs/configuring-playbook-bot-baibot.md:243
+#: ../../../docs/configuring-playbook-bot-baibot.md:245
-#: ../../../docs/configuring-playbook-bot-baibot.md:277
 msgid "💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:188
+#: ../../../docs/configuring-playbook-bot-baibot.md:162
 msgid "Groq"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:190
+#: ../../../docs/configuring-playbook-bot-baibot.md:164
 msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Groq provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq) with the help of the playbook's preset variables."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:213
+#: ../../../docs/configuring-playbook-bot-baibot.md:187
 msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/groq`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:219
+#: ../../../docs/configuring-playbook-bot-baibot.md:193
 msgid "Mistral"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:221
+#: ../../../docs/configuring-playbook-bot-baibot.md:195
 msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [🇫🇷 Mistral provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral) with the help of the playbook's preset variables."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:239
+#: ../../../docs/configuring-playbook-bot-baibot.md:213
 msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/mistral`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:245
+#: ../../../docs/configuring-playbook-bot-baibot.md:219
 msgid "OpenAI"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:247
+#: ../../../docs/configuring-playbook-bot-baibot.md:221
 msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with the help of the playbook's preset variables."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:249
+#: ../../../docs/configuring-playbook-bot-baibot.md:223
 msgid "The OpenAI provider is **only meant to be used with OpenAI's official API** and compatibility with other services (which do not fully adhere to the OpenAI API spec completely) is limited. **If you're targeting an OpenAI-compatible service**, use the [OpenAI Compatible](#openai-compatible) provider instead."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:273
+#: ../../../docs/configuring-playbook-bot-baibot.md:241
 msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/openai`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:279
+#: ../../../docs/configuring-playbook-bot-baibot.md:247
 msgid "OpenAI Compatible"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:281
+#: ../../../docs/configuring-playbook-bot-baibot.md:249
 msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI Compatible provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai-compatible) with the help of the playbook's preset variables."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:283
+#: ../../../docs/configuring-playbook-bot-baibot.md:251
 msgid "This provider allows you to use OpenAI-compatible API services like [OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter), [Together AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md#together-ai), etc."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:285
+#: ../../../docs/configuring-playbook-bot-baibot.md:253
 msgid "Some of these popular services already have **shortcut** providers (see [supported providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md#supported-providers) leading to this one behind the scenes — this make it easier to get started."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:287
+#: ../../../docs/configuring-playbook-bot-baibot.md:255
 msgid "As of this moment, the playbook does not include presets for any of these services, so you'll need to [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:289
+#: ../../../docs/configuring-playbook-bot-baibot.md:257
 msgid "Configuring additional agents (without a preset)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:291
+#: ../../../docs/configuring-playbook-bot-baibot.md:259
 msgid "The Ansible role may be lacking preset variables for some [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), or you may wish to statically-define an agent on the same provider twice (or more) with different configuration."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:293
+#: ../../../docs/configuring-playbook-bot-baibot.md:261
 msgid "It's possible to inject your own agent configuration using the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:295
+#: ../../../docs/configuring-playbook-bot-baibot.md:263
 msgid "You can also define providers at runtime, by chatting with the bot, so using Ansible is not a requirement."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:297
+#: ../../../docs/configuring-playbook-bot-baibot.md:265
 msgid "Below is an an **example** demonstrating **statically-defining agents via Ansible without using presets**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:336
+#: ../../../docs/configuring-playbook-bot-baibot.md:304
 msgid "Because these are [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agents, they will be given a `static/` ID prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and `static/my-ollama-agent`, respectively."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:338
+#: ../../../docs/configuring-playbook-bot-baibot.md:306
 msgid "💡 To figure out what to put in the `config` section, refer to the [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) page, which contains **sample configuration YAML for each provider**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:340
+#: ../../../docs/configuring-playbook-bot-baibot.md:308
 msgid "As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), defining them means they exist. To actually make use of them, they need to be configured as handlers globally or in a specific room — see [Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:342
+#: ../../../docs/configuring-playbook-bot-baibot.md:310
 msgid "💡 You may also wish to use these new agents for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:344
+#: ../../../docs/configuring-playbook-bot-baibot.md:312
 msgid "🤝 Configuring initial default handlers"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:346
+#: ../../../docs/configuring-playbook-bot-baibot.md:314
 msgid "This section is only useful if you're [🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible), as it lets you put these agents to use as soon as the bot starts (by adjusting the bot's **initial global configuration**)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:348
+#: ../../../docs/configuring-playbook-bot-baibot.md:316
 msgid "If you're not configuring agents via Ansible, you can skip this section."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:350
+#: ../../../docs/configuring-playbook-bot-baibot.md:318
 msgid "This section is only useful the first time around. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:352
+#: ../../../docs/configuring-playbook-bot-baibot.md:320
 msgid "baibot supports [various purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:354
+#: ../../../docs/configuring-playbook-bot-baibot.md:322
 msgid "[💬 text-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-generation): communicating with you via text"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:356
+#: ../../../docs/configuring-playbook-bot-baibot.md:324
 msgid "[🦻 speech-to-text](https://github.com/etkecc/baibot/blob/main/docs/features.md#-speech-to-text): turning your voice messages into text"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:358
+#: ../../../docs/configuring-playbook-bot-baibot.md:326
 msgid "[🗣️ text-to-speech](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-to-speech): turning bot or users text messages into voice messages"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:360
+#: ../../../docs/configuring-playbook-bot-baibot.md:328
 msgid "[🖌️ image-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-image-generation): generating images based on instructions"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:362
+#: ../../../docs/configuring-playbook-bot-baibot.md:330
 msgid "❓ catch-all: special purposes, indicating use as a fallback (when no specific handler is configured)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:364
+#: ../../../docs/configuring-playbook-bot-baibot.md:332
 msgid "[Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models) is made possible by the bot's ability to have different [🤝 handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md) configured for different purposes."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:366
+#: ../../../docs/configuring-playbook-bot-baibot.md:334
 msgid "This configuration can be done as a global fallback, or per-room. Both of these [🛠️ configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md) are managed at runtime (viat chat), but **the global configuration can have some initial defaults configured via Ansible**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:368
+#: ../../../docs/configuring-playbook-bot-baibot.md:336
 msgid "You can configure the **initial values** for these via Ansible, via the `matrix_bot_baibot_config_initial_global_config_handler_*` variables."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:370
+#: ../../../docs/configuring-playbook-bot-baibot.md:338
 msgid "Example **additional** `vars.yml` configuration:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:387
+#: ../../../docs/configuring-playbook-bot-baibot.md:355
 msgid "**Note**: these are initial defaults for the bot's global configuration. As such, changing any of these values subsequently has no effect on the bot's behavior. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:389
+#: ../../../docs/configuring-playbook-bot-baibot.md:357
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:391
+#: ../../../docs/configuring-playbook-bot-baibot.md:359
 msgid "There are some additional things you may wish to configure about the bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:393
+#: ../../../docs/configuring-playbook-bot-baibot.md:361
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:395
+#: ../../../docs/configuring-playbook-bot-baibot.md:363
 msgid "`roles/custom/matrix-bot-baibot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:396
+#: ../../../docs/configuring-playbook-bot-baibot.md:364
 msgid "`roles/custom/matrix-bot-baibot/templates/config.yaml.j2` for the bot's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bot_baibot_configuration_extension_yaml` variable"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:398
+#: ../../../docs/configuring-playbook-bot-baibot.md:366
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:400
+#: ../../../docs/configuring-playbook-bot-baibot.md:368
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:407
+#: ../../../docs/configuring-playbook-bot-baibot.md:375
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:409
+#: ../../../docs/configuring-playbook-bot-baibot.md:377
-msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account when password authentication is used."
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:411
+#: ../../../docs/configuring-playbook-bot-baibot.md:379
-msgid "If you're using access-token authentication, the bot account must already exist and the configured token + device ID must match that account. This mode is mainly for MAS/OIDC setups where password-based bot login is not suitable."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-baibot.md:413
 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-baibot.md:415
+#: ../../../docs/configuring-playbook-bot-baibot.md:381
 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-baibot.md:417
+#: ../../../docs/configuring-playbook-bot-baibot.md:383
-msgid "If you change the bot password (`matrix_bot_baibot_config_user_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_baibot_config_user_password` to let the bot know its new password. (This note applies to password authentication mode.)"
+msgid "If you change the bot password (`matrix_bot_baibot_config_user_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:419
+#: ../../../docs/configuring-playbook-bot-baibot.md:385
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:421
+#: ../../../docs/configuring-playbook-bot-baibot.md:387
 msgid "To use the bot, invite it to any existing Matrix room (`/invite @baibot:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:423
+#: ../../../docs/configuring-playbook-bot-baibot.md:389
 msgid "If you're an allowed bot [👥 user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) (see [👥 Initial users configuration](#-initial-users-configuration)), the bot will accept your invitation and join the room."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:425
+#: ../../../docs/configuring-playbook-bot-baibot.md:391
 msgid "After joining, the bot will introduce itself and show information about the [✨ features](https://github.com/etkecc/baibot/blob/main/docs/features.md) that are enabled for it."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:427
+#: ../../../docs/configuring-playbook-bot-baibot.md:393
 msgid "If you've [🤖 configured one or more agents via Ansible](#-configuring-agents-via-ansible) and have [🤝 configured initial default handlers](#configuring-initial-default-handlers), the bot will immediately be able to make use of these agents for this new room. Otherwise, you will need to configure agents and/or handlers via chat commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:429
+#: ../../../docs/configuring-playbook-bot-baibot.md:395
 msgid "Send `!bai help` to the bot in the room to see the available commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:431
+#: ../../../docs/configuring-playbook-bot-baibot.md:397
 msgid "You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:433
+#: ../../../docs/configuring-playbook-bot-baibot.md:399
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:435
+#: ../../../docs/configuring-playbook-bot-baibot.md:401
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-baibot`."
+msgid "As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:437
+#: ../../../docs/configuring-playbook-bot-baibot.md:403
-msgid "Increase logging verbosity"
+msgid "The default logging level for this service is `info`, but you can increase it to `debug` (or even `trace`) with the following additional configuration:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:439
+#: ../../../docs/configuring-playbook-bot-baibot.md:417
-msgid "The default logging level for this service is `info`. If you want to increase the verbosity to `debug` (or even `trace`), add the following configuration to your `vars.yml` file and re-run the playbook:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-baibot.md:453
 msgid "**Alternatively**, you can use a single variable to set the logging level for all of the above (bot + all libraries):"
 msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: bg\n"
@@ -19,156 +19,156 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:9
+#: ../../../docs/configuring-playbook-bot-buscarron.md:1
 msgid "Setting up Buscarron (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:11
+#: ../../../docs/configuring-playbook-bot-buscarron.md:3
 msgid "The playbook can install and configure [Buscarron](https://github.com/etkecc/buscarron) for you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:13
+#: ../../../docs/configuring-playbook-bot-buscarron.md:5
 msgid "Buscarron is bot that receives HTTP POST submissions of web forms and forwards them to a Matrix room."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:15
+#: ../../../docs/configuring-playbook-bot-buscarron.md:7
 msgid "See the project's [documentation](https://github.com/etkecc/buscarron/blob/main/README.md) to learn what it does and why it might be useful to you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:17
+#: ../../../docs/configuring-playbook-bot-buscarron.md:9
 msgid "Adjusting DNS records"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:19
+#: ../../../docs/configuring-playbook-bot-buscarron.md:11
 msgid "By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to create a CNAME record for `buscarron`, which targets `matrix.example.com`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:21
+#: ../../../docs/configuring-playbook-bot-buscarron.md:13
 msgid "When setting, replace `example.com` with your own."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:23
+#: ../../../docs/configuring-playbook-bot-buscarron.md:15
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:25
+#: ../../../docs/configuring-playbook-bot-buscarron.md:17
 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:48
+#: ../../../docs/configuring-playbook-bot-buscarron.md:40
 msgid "Adjusting the Buscarron URL (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:50
+#: ../../../docs/configuring-playbook-bot-buscarron.md:42
 msgid "By tweaking the `matrix_bot_buscarron_hostname` and `matrix_bot_buscarron_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:52
+#: ../../../docs/configuring-playbook-bot-buscarron.md:44
 msgid "Example additional configuration for your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:63
+#: ../../../docs/configuring-playbook-bot-buscarron.md:55
 msgid "After changing the domain, **you may need to adjust your DNS** records to point the Buscarron domain to the Matrix server."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:65
+#: ../../../docs/configuring-playbook-bot-buscarron.md:57
 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:67
+#: ../../../docs/configuring-playbook-bot-buscarron.md:59
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:69
+#: ../../../docs/configuring-playbook-bot-buscarron.md:61
 msgid "There are some additional things you may wish to configure about the bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:71
+#: ../../../docs/configuring-playbook-bot-buscarron.md:63
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:73
+#: ../../../docs/configuring-playbook-bot-buscarron.md:65
 msgid "`roles/custom/matrix-bot-buscarron/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:75
+#: ../../../docs/configuring-playbook-bot-buscarron.md:67
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:77
+#: ../../../docs/configuring-playbook-bot-buscarron.md:69
 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:84
+#: ../../../docs/configuring-playbook-bot-buscarron.md:76
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:86
+#: ../../../docs/configuring-playbook-bot-buscarron.md:78
 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:88
+#: ../../../docs/configuring-playbook-bot-buscarron.md:80
 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-buscarron.md:90
+#: ../../../docs/configuring-playbook-bot-buscarron.md:82
 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-buscarron.md:92
+#: ../../../docs/configuring-playbook-bot-buscarron.md:84
-msgid "If you change the bot password (`matrix_bot_buscarron_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_buscarron_password` to let the bot know its new password."
+msgid "If you change the bot password (`matrix_bot_buscarron_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:94
+#: ../../../docs/configuring-playbook-bot-buscarron.md:86
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:96
+#: ../../../docs/configuring-playbook-bot-buscarron.md:88
 msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.buscarron:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:98
+#: ../../../docs/configuring-playbook-bot-buscarron.md:90
 msgid "After the bot joins the room, anyone can call the web form via HTTP POST method."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:100
+#: ../../../docs/configuring-playbook-bot-buscarron.md:92
 msgid "Here is an example for the `contact` form:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:108
+#: ../../../docs/configuring-playbook-bot-buscarron.md:100
 msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:110
+#: ../../../docs/configuring-playbook-bot-buscarron.md:102
 msgid "you hit the homepage (HTTP `GET` request to `/`)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:111
+#: ../../../docs/configuring-playbook-bot-buscarron.md:103
 msgid "you submit a form to the wrong URL (`POST` request to `/non-existing-form`)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:112
+#: ../../../docs/configuring-playbook-bot-buscarron.md:104
 msgid "`hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:114
+#: ../../../docs/configuring-playbook-bot-buscarron.md:106
 msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:116
+#: ../../../docs/configuring-playbook-bot-buscarron.md:108
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:118
+#: ../../../docs/configuring-playbook-bot-buscarron.md:110
 msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-buscarron`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:120
+#: ../../../docs/configuring-playbook-bot-buscarron.md:112
 msgid "Increase logging verbosity"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:122
+#: ../../../docs/configuring-playbook-bot-buscarron.md:114
 msgid "The default logging level for this component is `INFO`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
 msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: bg\n"
@@ -19,421 +19,392 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:10
+#: ../../../docs/configuring-playbook-bot-draupnir.md:1
 msgid "Setting up Draupnir (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:12
+#: ../../../docs/configuring-playbook-bot-draupnir.md:3
 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:5
 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:7
 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:9
 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:11
 msgid "Prerequisites"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:22
+#: ../../../docs/configuring-playbook-bot-draupnir.md:13
 msgid "Create a management room"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:24
+#: ../../../docs/configuring-playbook-bot-draupnir.md:15
 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:17
 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:20
 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:22
 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:24
 msgid "End-to-End Encryption support"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:35
+#: ../../../docs/configuring-playbook-bot-draupnir.md:26
 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:28
 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:30
 msgid "Disable Pantalaimon for Draupnir (since v2.0.0; optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:41
+#: ../../../docs/configuring-playbook-bot-draupnir.md:32
 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:34
 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:36
 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:38
 msgid "Native E2EE support"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:49
+#: ../../../docs/configuring-playbook-bot-draupnir.md:40
 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:42
 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:44
 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:55
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:66
+#: ../../../docs/configuring-playbook-bot-draupnir.md:57
 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."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:85
+#: ../../../docs/configuring-playbook-bot-draupnir.md:76
 msgid "Create and invite the bot to the management room"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:87
+#: ../../../docs/configuring-playbook-bot-draupnir.md:78
 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:93
+#: ../../../docs/configuring-playbook-bot-draupnir.md:84
 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:95
+#: ../../../docs/configuring-playbook-bot-draupnir.md:86
 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:97
+#: ../../../docs/configuring-playbook-bot-draupnir.md:88
 msgid "Make sure the account is free from rate limiting (optional, recommended)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:99
+#: ../../../docs/configuring-playbook-bot-draupnir.md:90
 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:101
+#: ../../../docs/configuring-playbook-bot-draupnir.md:92
 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:103
+#: ../../../docs/configuring-playbook-bot-draupnir.md:94
 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:105
+#: ../../../docs/configuring-playbook-bot-draupnir.md:96
-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)."
+msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:107
+#: ../../../docs/configuring-playbook-bot-draupnir.md:98
 msgid "Add the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:109
+#: ../../../docs/configuring-playbook-bot-draupnir.md:100
 msgid "To expose the APIs publicly, add the following configuration to your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:115
+#: ../../../docs/configuring-playbook-bot-draupnir.md:106
 msgid "Obtain an access token for admin account"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:117
+#: ../../../docs/configuring-playbook-bot-draupnir.md:108
 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:119
+#: ../../../docs/configuring-playbook-bot-draupnir.md:110
 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:122
+#: ../../../docs/configuring-playbook-bot-draupnir.md:113
 msgid "Run the `curl` command"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:124
+#: ../../../docs/configuring-playbook-bot-draupnir.md:115
 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:126
+#: ../../../docs/configuring-playbook-bot-draupnir.md:117
 msgid "`ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:127
+#: ../../../docs/configuring-playbook-bot-draupnir.md:118
 msgid "`example.com` with your base domain"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:128
+#: ../../../docs/configuring-playbook-bot-draupnir.md:119
 msgid "`@bot.draupnir:example.com` with the MXID of your Draupnir bot user"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:134
+#: ../../../docs/configuring-playbook-bot-draupnir.md:125
-#: ../../../docs/configuring-playbook-bot-draupnir.md:207
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:135
+#: ../../../docs/configuring-playbook-bot-draupnir.md:126
 msgid "This does not work on outdated Windows 10 as curl is not available there."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:136
+#: ../../../docs/configuring-playbook-bot-draupnir.md:127
 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:138
+#: ../../../docs/configuring-playbook-bot-draupnir.md:129
 msgid "Abuse Reports"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:140
+#: ../../../docs/configuring-playbook-bot-draupnir.md:131
 msgid "Draupnir can receive reports in the management room."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:142
+#: ../../../docs/configuring-playbook-bot-draupnir.md:133
 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:148
+#: ../../../docs/configuring-playbook-bot-draupnir.md:145
-msgid "Enabling synapse-http-antispam support"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-draupnir.md:150
-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:160
-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."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-draupnir.md:168
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:170
+#: ../../../docs/configuring-playbook-bot-draupnir.md:147
 msgid "There are some additional things you may wish to configure about the bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:172
+#: ../../../docs/configuring-playbook-bot-draupnir.md:149
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:174
+#: ../../../docs/configuring-playbook-bot-draupnir.md:151
 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:176
+#: ../../../docs/configuring-playbook-bot-draupnir.md:153
 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:190
+#: ../../../docs/configuring-playbook-bot-draupnir.md:167
 msgid "Migrating from Mjolnir (Only required if migrating)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:192
+#: ../../../docs/configuring-playbook-bot-draupnir.md:169
 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:194
+#: ../../../docs/configuring-playbook-bot-draupnir.md:171
 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:196
+#: ../../../docs/configuring-playbook-bot-draupnir.md:173
 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:198
+#: ../../../docs/configuring-playbook-bot-draupnir.md:175
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:200
+#: ../../../docs/configuring-playbook-bot-draupnir.md:177
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:209
+#: ../../../docs/configuring-playbook-bot-draupnir.md:184
-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:211
 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:213
+#: ../../../docs/configuring-playbook-bot-draupnir.md:186
 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:215
+#: ../../../docs/configuring-playbook-bot-draupnir.md:188
-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:217
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:219
+#: ../../../docs/configuring-playbook-bot-draupnir.md:190
 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:221
+#: ../../../docs/configuring-playbook-bot-draupnir.md:192
 msgid "Below is a **non-exhaustive quick-start guide** for the impatient."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:223
+#: ../../../docs/configuring-playbook-bot-draupnir.md:194
 msgid "Making Draupnir join and protect a room"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:225
+#: ../../../docs/configuring-playbook-bot-draupnir.md:196
 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:227
+#: ../../../docs/configuring-playbook-bot-draupnir.md:198
 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:229
+#: ../../../docs/configuring-playbook-bot-draupnir.md:200
 msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:231
+#: ../../../docs/configuring-playbook-bot-draupnir.md:202
 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:233
+#: ../../../docs/configuring-playbook-bot-draupnir.md:204
 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:235
+#: ../../../docs/configuring-playbook-bot-draupnir.md:206
 msgid "Giving Draupnir permissions to do its job"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:237
+#: ../../../docs/configuring-playbook-bot-draupnir.md:208
 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:239
+#: ../../../docs/configuring-playbook-bot-draupnir.md:210
 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:241
+#: ../../../docs/configuring-playbook-bot-draupnir.md:212
 msgid "Subscribing to a public policy list"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:243
+#: ../../../docs/configuring-playbook-bot-draupnir.md:214
 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:245
+#: ../../../docs/configuring-playbook-bot-draupnir.md:216
-msgid "Policy lists are maintained in Matrix rooms. Popular ones maintained in the public are:"
+msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:247
+#: ../../../docs/configuring-playbook-bot-draupnir.md:218
-msgid "`#community-moderation-effort-bl:neko.dev`"
+msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:248
+#: ../../../docs/configuring-playbook-bot-draupnir.md:220
-msgid "`#huginn-muninn-active-threats:feline.support`"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-draupnir.md:250
-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:252
 msgid "Creating your own policy lists and rules"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:254
+#: ../../../docs/configuring-playbook-bot-draupnir.md:222
 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:256
+#: ../../../docs/configuring-playbook-bot-draupnir.md:224
 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:258
+#: ../../../docs/configuring-playbook-bot-draupnir.md:226
 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:260
+#: ../../../docs/configuring-playbook-bot-draupnir.md:228
 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:262
+#: ../../../docs/configuring-playbook-bot-draupnir.md:230
 msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:264
+#: ../../../docs/configuring-playbook-bot-draupnir.md:232
 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:265
+#: ../../../docs/configuring-playbook-bot-draupnir.md:233
-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`"
+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:267
+#: ../../../docs/configuring-playbook-bot-draupnir.md:235
 msgid "As a result of running these commands, you may observe:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:269
+#: ../../../docs/configuring-playbook-bot-draupnir.md:237
 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:270
+#: ../../../docs/configuring-playbook-bot-draupnir.md:238
 msgid "applying these rules against all rooms that Draupnir is an Administrator in"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:272
+#: ../../../docs/configuring-playbook-bot-draupnir.md:240
 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:274
+#: ../../../docs/configuring-playbook-bot-draupnir.md:242
 msgid "Enabling built-in protections"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:276
+#: ../../../docs/configuring-playbook-bot-draupnir.md:244
-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\")."
+msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:278
+#: ../../../docs/configuring-playbook-bot-draupnir.md:246
 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:280
+#: ../../../docs/configuring-playbook-bot-draupnir.md:248
-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`)."
+msgid "To **see the configuration options for a given protection**, send a `!draupnir protections show PROTECTION_NAME` (e.g. `!draupnir protections show JoinWaveShortCircuit`)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:282
+#: ../../../docs/configuring-playbook-bot-draupnir.md:250
-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`)."
+msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:284
+#: ../../../docs/configuring-playbook-bot-draupnir.md:252
-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`)."
+msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:286
+#: ../../../docs/configuring-playbook-bot-draupnir.md:254
-msgid "To **disable a given protection**, send a command like this: `!draupnir protections disable PROTECTION_NAME` (e.g. `!draupnir protections disable JoinWaveShortCircuitProtection`)."
+msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)."
 msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: bg\n"
@@ -19,140 +19,108 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:9
+#: ../../../docs/configuring-playbook-bot-honoroit.md:1
 msgid "Setting up Honoroit (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:11
+#: ../../../docs/configuring-playbook-bot-honoroit.md:3
 msgid "The playbook can install and configure [Honoroit](https://github.com/etkecc/honoroit) for you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:13
+#: ../../../docs/configuring-playbook-bot-honoroit.md:5
 msgid "It's a bot you can use to setup **your own helpdesk on matrix**"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:15
+#: ../../../docs/configuring-playbook-bot-honoroit.md:7
 msgid "See the project's [documentation](https://github.com/etkecc/honoroit/blob/main/README.md) to learn what it does and why it might be useful to you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:17
+#: ../../../docs/configuring-playbook-bot-honoroit.md:9
 msgid "Adjusting DNS records (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:19
+#: ../../../docs/configuring-playbook-bot-honoroit.md:11
 msgid "By default, this playbook installs Honoroit on the `matrix.` subdomain, at the `/honoroit` path (https://matrix.example.com/honoroit). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:21
+#: ../../../docs/configuring-playbook-bot-honoroit.md:13
 msgid "If you wish to adjust it, see the section [below](#adjusting-the-honoroit-url-optional) for details about DNS configuration."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:23
+#: ../../../docs/configuring-playbook-bot-honoroit.md:15
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:25
+#: ../../../docs/configuring-playbook-bot-honoroit.md:17
 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:40
+#: ../../../docs/configuring-playbook-bot-honoroit.md:32
 msgid "Adjusting the Honoroit URL (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:42
+#: ../../../docs/configuring-playbook-bot-honoroit.md:34
 msgid "By tweaking the `matrix_bot_honoroit_hostname` and `matrix_bot_honoroit_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:44
+#: ../../../docs/configuring-playbook-bot-honoroit.md:36
 msgid "Example additional configuration for your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:52
+#: ../../../docs/configuring-playbook-bot-honoroit.md:44
 msgid "If you've changed the default hostname, you may need to create a CNAME record for the Honoroit domain (`honoroit.example.com`), which targets `matrix.example.com`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:54
+#: ../../../docs/configuring-playbook-bot-honoroit.md:46
 msgid "When setting, replace `example.com` with your own."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:56
+#: ../../../docs/configuring-playbook-bot-honoroit.md:48
-msgid "Extending the configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:58
-msgid "There are some additional things you may wish to configure about the bot."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:60
-msgid "Take a look at:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:62
-msgid "`roles/custom/matrix-bot-honoroit/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:64
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:66
+#: ../../../docs/configuring-playbook-bot-honoroit.md:50
 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:73
+#: ../../../docs/configuring-playbook-bot-honoroit.md:57
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:75
+#: ../../../docs/configuring-playbook-bot-honoroit.md:59
 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:77
+#: ../../../docs/configuring-playbook-bot-honoroit.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-bot-honoroit.md:79
+#: ../../../docs/configuring-playbook-bot-honoroit.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-bot-honoroit.md:81
+#: ../../../docs/configuring-playbook-bot-honoroit.md:65
-msgid "If you change the bot password (`matrix_bot_honoroit_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_honoroit_password` to let the bot know its new password."
+msgid "If you change the bot password (`matrix_bot_honoroit_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:83
+#: ../../../docs/configuring-playbook-bot-honoroit.md:67
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:85
+#: ../../../docs/configuring-playbook-bot-honoroit.md:69
 msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @honoroit:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:87
+#: ../../../docs/configuring-playbook-bot-honoroit.md:71
 msgid "After the bot joins the room, any Matrix user can send a message to it to start a new thread in that room."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:89
+#: ../../../docs/configuring-playbook-bot-honoroit.md:73
 msgid "Send `!ho help` to the bot in the room to see the available commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:91
+#: ../../../docs/configuring-playbook-bot-honoroit.md:75
 msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features)."
 msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:93
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:95
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-honoroit`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:97
-msgid "Increase logging verbosity"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:99
-msgid "If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
-msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: bg\n"
@@ -19,120 +19,84 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:13
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:1
 msgid "Setting up matrix-registration-bot (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:15
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:3
 msgid "The playbook can install and configure [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) for you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:17
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:5
 msgid "The bot allows you to easily **create and manage registration tokens** aka. invitation codes. It can be used for an invitation-based server, where you invite someone by sending them a registration token (tokens look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but have to provide a valid registration token in the final step of the registration process."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:19
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7
 msgid "See the project's [documentation](https://github.com/moan0s/matrix-registration-bot/blob/master/README.md) to learn what it does and why it might be useful to you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:21
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:23
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11
 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:46
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:30
 msgid "The bot account will be created automatically."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:48
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:32
-msgid "Extending the configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:50
-msgid "There are some additional things you may wish to configure about the bot."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:52
-msgid "Take a look at:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:54
-msgid "`roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55
-msgid "`roles/custom/matrix-bot-matrix-registration-bot/templates/config.yaml.j2` for the bridge's default configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:59
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:34
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:66
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:41
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:68
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:43
 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:70
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:45
 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-matrix-registration-bot.md:72
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:47
 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-matrix-registration-bot.md:74
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:49
-msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_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_matrix_registration_bot_bot_password` to let the bot know its new password."
+msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:76
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:51
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:78
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:53
 msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:80
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55
 msgid "Send `help` to the bot to see the available commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:82
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57
 msgid "You can also refer to the upstream [Usage documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:84
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:59
-msgid "If you have any questions, or if you need help setting it up, read the [troubleshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)."
+msgid "If you have any questions, or if you need help setting it up, read the [troublshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:86
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:61
 msgid "To clean the cache (session & encryption data) after you changed the bot's username, changed the login method from access_token to password etc… you can use:"
 msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:92
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:94
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-matrix-registration-bot`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:96
-msgid "Increase logging verbosity"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:98
-msgid "The default logging level for this component is `INFO`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
-msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: bg\n"
@@ -19,116 +19,80 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:1
 msgid "Setting up matrix-reminder-bot (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:3
 msgid "The playbook can install and configure [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot) for you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:13
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:5
 msgid "It's a bot you can use to **schedule one-off & recurring reminders and alarms**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:15
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7
 msgid "See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot/blob/master/README.md) to learn what it does and why it might be useful to you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:17
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:19
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11
 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:34
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26
-msgid "Extending the configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:36
-msgid "There are some additional things you may wish to configure about the bot."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:38
-msgid "Take a look at:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:40
-msgid "`roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:41
-msgid "`roles/custom/matrix-bot-matrix-reminder-bot/templates/config.yaml.j2` for the bot's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bot_matrix_reminder_bot_configuration_extension_yaml` variable"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:43
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:45
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:28
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:52
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:35
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:54
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:37
 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:56
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:39
 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-matrix-reminder-bot.md:58
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:41
 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-matrix-reminder-bot.md:60
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:43
-msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_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_matrix_reminder_bot_matrix_user_password` to let the bot know its new password."
+msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:62
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:45
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:64
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:47
 msgid "To use the bot, start a chat with `@bot.matrix-reminder-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:66
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:49
 msgid "You can also add the bot to any existing Matrix room (`/invite @bot.matrix-reminder-bot:example.com`)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:68
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:51
 msgid "Basic usage is like this: `!remindme in 2 minutes; This is a test`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:70
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:53
 msgid "Send `!help reminders` to the room to see the bot's help menu for additional commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:72
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:55
 msgid "You can also refer to the upstream [Usage documentation](https://github.com/anoadragon453/matrix-reminder-bot#usage)."
 msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:74
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:76
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-matrix-reminder-bot`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:78
-msgid "Increase logging verbosity"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:80
-msgid "The default logging level for this component is `INFO`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
-msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: bg\n"
@@ -19,185 +19,149 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:12
+#: ../../../docs/configuring-playbook-bot-maubot.md:1
 msgid "Setting up maubot (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:14
+#: ../../../docs/configuring-playbook-bot-maubot.md:3
 msgid "The playbook can install and configure [maubot](https://github.com/maubot/maubot) for you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:16
+#: ../../../docs/configuring-playbook-bot-maubot.md:5
 msgid "After setting up maubot, you can use the web management interface to make it do things. The default location of the management interface is `matrix.example.com/_matrix/maubot/`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:18
+#: ../../../docs/configuring-playbook-bot-maubot.md:7
 msgid "See the project's [documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn what it does and why it might be useful to you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:20
+#: ../../../docs/configuring-playbook-bot-maubot.md:9
 msgid "Adjusting DNS records (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:22
+#: ../../../docs/configuring-playbook-bot-maubot.md:11
 msgid "By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:24
+#: ../../../docs/configuring-playbook-bot-maubot.md:13
 msgid "If you wish to adjust it, see the section [below](#adjusting-the-maubot-url-optional) for details about DNS configuration."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:26
+#: ../../../docs/configuring-playbook-bot-maubot.md:15
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:28
+#: ../../../docs/configuring-playbook-bot-maubot.md:17
 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:43
+#: ../../../docs/configuring-playbook-bot-maubot.md:32
 msgid "You can add multiple admins. The admin accounts are only used to access the maubot administration interface."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:45
+#: ../../../docs/configuring-playbook-bot-maubot.md:34
 msgid "Adjusting the maubot URL (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:47
+#: ../../../docs/configuring-playbook-bot-maubot.md:36
 msgid "By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:49
+#: ../../../docs/configuring-playbook-bot-maubot.md:38
-#: ../../../docs/configuring-playbook-bot-maubot.md:76
+#: ../../../docs/configuring-playbook-bot-maubot.md:56
 msgid "Example additional configuration for your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:57
+#: ../../../docs/configuring-playbook-bot-maubot.md:46
 msgid "If you've changed the default hostname, you may need to create a CNAME record for the maubot domain (`maubot.example.com`), which targets `matrix.example.com`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:59
+#: ../../../docs/configuring-playbook-bot-maubot.md:48
 msgid "When setting, replace `example.com` with your own."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:61
+#: ../../../docs/configuring-playbook-bot-maubot.md:50
-msgid "Extending the configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:63
-msgid "There are some additional things you may wish to configure about the bot."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:65
-msgid "Take a look at:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:67
-msgid "`roles/custom/matrix-bot-maubot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:68
-msgid "`roles/custom/matrix-bot-maubot/templates/config.yaml.j2` for the bot's default configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:70
 msgid "Customizing the maubot container image"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:72
+#: ../../../docs/configuring-playbook-bot-maubot.md:52
 msgid "Certain [maubot plugins](https://plugins.mau.bot/) require additional dependencies to be installed."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:74
+#: ../../../docs/configuring-playbook-bot-maubot.md:54
 msgid "You can customize the default maubot container image and install your own dependencies."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:87
+#: ../../../docs/configuring-playbook-bot-maubot.md:67
 msgid "Consult the [Dockerfile reference](https://docs.docker.com/reference/dockerfile/) for more information about the syntax."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:89
+#: ../../../docs/configuring-playbook-bot-maubot.md:69
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:91
+#: ../../../docs/configuring-playbook-bot-maubot.md:71
 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:98
+#: ../../../docs/configuring-playbook-bot-maubot.md:78
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:100
+#: ../../../docs/configuring-playbook-bot-maubot.md:80
 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:102
+#: ../../../docs/configuring-playbook-bot-maubot.md:82
 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-maubot.md:104
+#: ../../../docs/configuring-playbook-bot-maubot.md:84
 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-maubot.md:106
+#: ../../../docs/configuring-playbook-bot-maubot.md:86
-msgid "If you change the bot password (`matrix_bot_maubot_initial_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_maubot_initial_password` to let the bot know its new password."
+msgid "If you change the bot password (`matrix_bot_maubot_initial_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:108
+#: ../../../docs/configuring-playbook-bot-maubot.md:88
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:110
+#: ../../../docs/configuring-playbook-bot-maubot.md:90
 msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:112
+#: ../../../docs/configuring-playbook-bot-maubot.md:92
 msgid "You should start in the following order"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:113
+#: ../../../docs/configuring-playbook-bot-maubot.md:93
 msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:114
+#: ../../../docs/configuring-playbook-bot-maubot.md:94
 msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:115
+#: ../../../docs/configuring-playbook-bot-maubot.md:95
 msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:117
+#: ../../../docs/configuring-playbook-bot-maubot.md:97
 msgid "Obtain an access token"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:119
+#: ../../../docs/configuring-playbook-bot-maubot.md:99
 msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:121
+#: ../../../docs/configuring-playbook-bot-maubot.md:101
 msgid "Alternatively, you can refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will causes issues to your bot in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:123
+#: ../../../docs/configuring-playbook-bot-maubot.md:103
 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-maubot.md:126
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:128
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-maubot`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:130
-msgid "Increase logging verbosity"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:132
-msgid "The default logging level for this component is `WARNING`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
-msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: bg\n"
@@ -19,266 +19,254 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:12
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:1
 msgid "Setting up Mjolnir (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:14
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:3
 msgid "The playbook can install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation bot for you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:16
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:5
 msgid "See the project's [documentation](https://github.com/matrix-org/mjolnir/blob/main/README.md) to learn what it does and why it might be useful to you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:18
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:7
 msgid "Prerequisites"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:20
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:9
 msgid "Register the bot account"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:22
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:11
 msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:24
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:13
 msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:26
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:15
 msgid "You can use the playbook to [register a new user](registering-users.md):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:32
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:21
 msgid "If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:34
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:23
 msgid "Obtain an access token"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:36
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:25
 msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:38
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:27
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:63
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:52
 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-mjolnir.md:41
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:30
 msgid "Make sure the account is free from rate limiting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:43
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:32
 msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:45
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:34
 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-mjolnir.md:47
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:36
 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-mjolnir.md:49
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:38
-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)."
+msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:51
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:40
 msgid "Add the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:53
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:42
 msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:59
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:48
 msgid "Obtain an access token for admin account"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:61
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:50
 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). If you have made Mjolnir an admin, you can just use the Mjolnir token."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:66
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:55
 msgid "Run the `curl` command"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:68
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:57
 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-mjolnir.md:70
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:59
 msgid "`ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:71
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:60
 msgid "`example.com` with your base domain"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:72
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:61
 msgid "`@bot.mjolnir:example.com` with the MXID of your Mjolnir bot user"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:78
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:67
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:195
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:184
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:79
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:68
 msgid "This does not work on outdated Windows 10 as curl is not available there."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:80
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:69
 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-mjolnir.md:82
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:71
 msgid "Create a management room"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:84
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:73
 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-mjolnir.md:86
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:75
 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-mjolnir.md:89
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:78
 msgid "It is possible to make the management room encrypted (E2EE). If doing so, then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:91
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:80
 msgid "Once you have created the room you need to copy the room ID so you can specify it on your `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-mjolnir.md:93
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:82
 msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:95
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:84
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:97
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:86
 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 just now."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:106
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:95
 msgid "End-to-End Encryption support"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:108
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:97
 msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:110
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:99
 msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:112
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:101
 msgid "Configuration with E2EE support"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:114
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:103
 msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:116
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:105
 msgid "Add the following configuration to your `vars.yml` file (adapt to your needs):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:130
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:119
 msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Mjolnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:142
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:131
 msgid "Configuration without E2EE support"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:144
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:133
 msgid "When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:146
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:135
 msgid "Add the following configuration to your `vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:152
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:141
 msgid "Adding Mjolnir synapse antispam module (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:154
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:143
 msgid "To enable Mjolnir synapse antispam module, add the following configuration to your `vars.yml` file (adapt to your needs):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:164
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:153
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:166
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:155
 msgid "There are some additional things you may wish to configure about the bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:168
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:157
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:170
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:159
 msgid "`roles/custom/matrix-bot-mjolnir/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_mjolnir_configuration_extension_yaml` variable"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:172
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:161
 msgid "For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:186
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:175
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:188
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:177
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:197
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:186
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:188
 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-mjolnir.md:199
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:190
 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-mjolnir.md:201
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:192
-msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password."
+msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:203
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:194
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:205
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:196
 msgid "You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot."
 msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:207
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:209
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-mjolnir`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:211
-msgid "Increase logging verbosity"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:213
-msgid "The default logging level for this component is `INFO`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
-msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po

@@ -8,60 +8,60 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\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"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:10
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:1
 msgid "Setting up Postmoogle email bridging (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:12
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:3
 msgid "The playbook can install and configure [Postmoogle](https://github.com/etkecc/postmoogle) for you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:14
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:5
 msgid "Postmoogle is a bridge you can use to have its bot user forward emails to Matrix rooms. It runs an SMTP email server and allows you to assign mailbox addresses to the rooms."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:16
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:7
 msgid "See the project's [documentation](https://github.com/etkecc/postmoogle/blob/master/README.md) to learn what it does and why it might be useful to you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:18
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:9
 msgid "Prerequisites"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:20
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:11
 msgid "Open the following ports on your server to be able to receive incoming emails:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:22
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:13
 msgid "`25/tcp`: SMTP"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:23
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:14
 msgid "`587/tcp`: Submission (TLS-encrypted SMTP)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:25
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:16
 msgid "If you don't open these ports, you will still be able to send emails, but not receive any."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:27
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:18
 msgid "These port numbers are configurable via the `matrix_postmoogle_smtp_host_bind_port` and `matrix_postmoogle_submission_host_bind_port` variables, but other email servers will try to deliver on these default (standard) ports, so changing them is of little use."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:29
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:20
 msgid "Adjusting DNS records"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:31
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:22
 msgid "To make Postmoogle enable its email sending features, you need to configure MX and TXT (SPF, DMARC, and DKIM) records. See the table below for values which need to be specified."
 msgstr ""
 
@@ -137,94 +137,90 @@ msgstr ""
 msgid "get it from `!pm dkim`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:40
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:31
 msgid "**Note**: the DKIM record can be retrieved after configuring and installing the bridge's bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:42
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:33
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:44
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:35
 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:65
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:56
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:67
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:58
 msgid "There are some additional things you may wish to configure about the bridge."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:69
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:60
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:71
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:62
 msgid "`roles/custom/matrix-bridge-postmoogle/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:73
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:64
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:75
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:66
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:82
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:73
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:84
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:75
 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create a user account of the bridge's bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:86
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:77
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:88
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:79
 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-bridge-postmoogle.md:90
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:81
-msgid "If you change the bridge's bot password (`matrix_postmoogle_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_postmoogle_password` to let the bot know its new password."
+msgid "If you change the bridge's bot password (`matrix_postmoogle_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:92
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:83
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:94
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:85
 msgid "To use the bridge, invite the `@postmoogle:example.com` bot user into a room you want to use as a mailbox."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:96
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:87
 msgid "Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.example.com`. Emails sent to that email address will be forwarded to the room."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:98
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:89
 msgid "Send `!pm help` to the bot in the room to see the available commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:100
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:91
 msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/postmoogle)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:102
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:93
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:104
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:95
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-postmoogle`."
+msgid "As with all other services, you can find their logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-postmoogle`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:106
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:97
-msgid "Increase logging verbosity"
+msgid "The default logging level for this bridge is `INFO`, but you can increase it to `DEBUG` with the following additional configuration:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:108
-msgid "The default logging level for this component is `INFO`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
 msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-element-admin.po

@@ -1,118 +0,0 @@
-# SOME DESCRIPTIVE TITLE.
-# Copyright (C) 2018-2026, 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>, 2026.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: matrix-docker-ansible-deploy \n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\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.18.0\n"
-
-#: ../../../docs/configuring-playbook-element-admin.md:8
-msgid "Setting up Element Admin (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:10
-msgid "The playbook can install and configure [Element Admin](https://github.com/element-hq/element-admin) for you."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:12
-msgid "Element Admin is a web-based administration panel for Synapse and [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md)."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:14
-msgid "See the project's [documentation](https://github.com/element-hq/element-admin) to learn more."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:16
-msgid "💡 **Note**: This project is still very young and doesn't have many features. [Ketesa](./configuring-playbook-ketesa.md) is the fully-featured alternative — it covers all Synapse and MAS Admin APIs, including complete user management, session management, and MAS policy data. Element Admin remains a valid choice if you prefer its interface."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:18
-msgid "Prerequisites"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:20
-msgid "A [Synapse](configuring-playbook-synapse.md) homeserver with its Admin API enabled (the playbook automatically enables it for you when you enable Element Admin)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:21
-msgid "[Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) with its Admin API enabled (the playbook automatically enables it for you when you enable Element Admin)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:23
-msgid "Decide on a domain and path"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:25
-msgid "By default, the Element Admin is configured to be served on the `admin.element.example.com` domain."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:27
-msgid "If you'd like to run Element Admin on another hostname, see the [Adjusting the Element Admin URL](#adjusting-the-element-admin-url-optional) section below."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:29
-msgid "Adjusting DNS records (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:31
-msgid "By default, this playbook installs Element Admin on the `admin.element.` subdomain (`admin.element.example.com`) and requires you to create a `CNAME` record for `admin.element`, which targets `matrix.example.com`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:33
-msgid "When setting these values, replace `example.com` with your own."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:35
-msgid "Adjusting the playbook configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:37
-msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:43
-msgid "Adjusting the Element Admin URL (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:45
-msgid "By tweaking the `matrix_element_admin_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:47
-msgid "Example additional configuration for your `vars.yml` file:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:53
-msgid "[!WARNING] A `matrix_element_admin_path_prefix` variable is also available and mean to let you configure a path prefix for the Element Admin service, but **Element Admin does not support running under a sub-path yet**."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:56
-msgid "Installing"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:58
-msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:65
-msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:67
-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. Note these shortcuts run the `ensure-matrix-users-created` tag too."
-msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-ketesa.po

@@ -1,166 +0,0 @@
-# SOME DESCRIPTIVE TITLE.
-# Copyright (C) 2018-2026, 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>, 2026.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: matrix-docker-ansible-deploy \n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 12:02+0100\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.18.0\n"
-
-#: ../../../docs/configuring-playbook-ketesa.md:14
-msgid "Setting up Ketesa (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:16
-msgid "The playbook can install and configure [Ketesa](https://github.com/etkecc/ketesa) for you."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:18
-msgid "Ketesa is a fully-featured admin interface for Matrix homeservers — manage users, rooms, media, sessions, and more from one clean, responsive web UI. It is the evolution of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin): what began as a fork has grown into its own independent project with a redesigned interface, comprehensive Synapse and MAS API coverage, and multi-language support."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:20
-msgid "[!NOTE]"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:22
-msgid "Ketesa does not work with other homeserver implementations than Synapse due to API's incompatibility."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:23
-msgid "The latest version of Ketesa is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:24
-msgid "This playbook also supports an alternative management UI in the shape of [Element Admin](./configuring-playbook-element-admin.md). Please note that it's currently less feature-rich than Ketesa and requires [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md)."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:26
-msgid "Adjusting DNS records (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:28
-msgid "By default, this playbook installs Ketesa on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin) — the legacy path is kept for backward compatibility. This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:30
-msgid "If you wish to adjust it, see the section [below](#adjusting-the-ketesa-url-optional) for details about DNS configuration."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:32
-msgid "Adjusting the playbook configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:34
-msgid "To enable Ketesa, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:40
-msgid "**Note**: Ketesa requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Ketesa needs these APIs to function, when installing Ketesa, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:42
-msgid "for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:43
-msgid "for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:45
-msgid "By default, Ketesa installation will be [restricted to only work with one homeserver](https://github.com/etkecc/ketesa/blob/main/README.md#restricting-available-homeserver) — the one managed by the playbook. To adjust these restrictions, tweak the `matrix_ketesa_config_restrictBaseUrl` variable."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:47
-msgid "Adjusting the Ketesa URL (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:49
-msgid "By tweaking the `matrix_ketesa_hostname` and `matrix_ketesa_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:51
-msgid "We recommend updating the path prefix to `/ketesa` to align with the new branding, while the default `/synapse-admin` is kept for backward compatibility:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:57
-msgid "Or to change the hostname entirely:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:65
-msgid "If you've changed the default hostname, you may need to create a CNAME record for the Ketesa domain (`admin.example.com`), which targets `matrix.example.com`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:67
-msgid "When setting, replace `example.com` with your own."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:69
-msgid "Extending the configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:71
-msgid "There are some additional things you may wish to configure about the component."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:73
-msgid "Take a look at:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:75
-msgid "`roles/custom/matrix-ketesa/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_ketesa_configuration_extension_json` variable"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:77
-msgid "Installing"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:79
-msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:86
-msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:88
-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. Note these shortcuts run the `ensure-matrix-users-created` tag too."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:90
-msgid "Usage"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:92
-msgid "After installation, Ketesa will be accessible at: `https://matrix.example.com/synapse-admin/` (or `/ketesa/` if you updated the path prefix as recommended)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:94
-msgid "To use Ketesa, you need to have [registered at least one administrator account](registering-users.md) on your server."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:96
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:98
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-ketesa`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:100
-msgid "If you have questions, you can join this community room and feel free to ask: [#ketesa:etke.cc](https://matrix.to/#/#ketesa:etke.cc)"
-msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: bg\n"
@@ -19,134 +19,150 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:8
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:1
 msgid "Setting up Matrix Authentication Service (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:10
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:3
 msgid "The playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) — a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:12
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:5
 msgid "Matrix Authentication Service is an implementation of [MSC3861: Next-generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:14
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:7
 msgid "**Before going through with starting to use Matrix Authentication Service**, make sure to read:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:16
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:9
 msgid "the [Reasons to use Matrix Authentication Service](#reasons-to-use-matrix-authentication-service) section below"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:17
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:10
 msgid "the [Expectations](#expectations) section below"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:18
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:11
 msgid "the [FAQ section on areweoidcyet.com](https://areweoidcyet.com/#faqs)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:20
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:13
 msgid "**If you've already been using Synapse** and have user accounts in its database, you can [migrate to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:22
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:15
 msgid "Reasons to use Matrix Authentication Service"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:24
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:17
 msgid "You may be wondering whether you should make the switch to Matrix Authentication Service (MAS) or keep using your existing authentication flow via Synapse (password-based or [OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)-enabled)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:26
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:19
 msgid "Matrix Authentication Service is **still an experimental service** and **not a default** for this Ansible playbook."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:28
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:21
 msgid "The [Expectations](#expectations) section contains a list of what works and what doesn't (**some services don't work with MAS yet**), as well as the **relative irreversability** of the migration process."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:30
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:23
 msgid "Below, we'll try to **highlight some potential reasons for switching** to Matrix Authentication Service:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:32
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:25
 msgid "To use SSO in [Element X](https://element.io/blog/element-x-ignition/). The old [Synapse OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) login flow is only supported in old Element clients and will not be supported in Element X. Element X will only support the new SSO-based login flow provided by MAS, so if you want to use SSO with Element X, you will need to switch to MAS."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:34
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:27
 msgid "To help drive adoption of the \"Next-generation auth for Matrix\" by switching to what's ultimately coming anyway"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:36
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:29
 msgid "To help discover (and potentially fix) MAS integration issues with this Ansible playbook"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:38
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:31
 msgid "To help discover (and potentially fix) MAS integration issues with various other Matrix components (bridges, bots, clients, etc.)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:40
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:33
 msgid "To reap some of the security benefits that Matrix Authentication Service offers, as outlined in the [Better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) article."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:42
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:35
 msgid "Prerequisites"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:44
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:37
-msgid "⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating with Matrix Authentication Service yet."
+msgid "⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:46
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:39
+msgid "⚠️ **email sending** configured (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:41
 msgid "❌ **disabling all password providers** for Synapse (things like [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc.) More details about this are available in the [Expectations](#expectations) section below."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:48
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:43
 msgid "Expectations"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:50
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:45
 msgid "This section details what you can expect when switching to the Matrix Authentication Service (MAS)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:52
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:47
 msgid "❌ **Synapse password providers will need to be disabled**. You can no longer use [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc. When the authentication flow is handled by MAS (not by Synapse anymore), it doesn't make sense to extend the Synapse authentication flow with additional modules. Many bridges used to rely on shared-secret-auth for doing double-puppeting (impersonating other users), but most (at least the mautrix bridges) nowadays use [Appservice Double Puppet](./configuring-playbook-appservice-double-puppet.md) as a better alternative. Older/maintained bridges may still rely on shared-secret-auth, as do other services like [matrix-corporal](./configuring-playbook-matrix-corporal.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:54
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:49
-msgid "✅ **[Ketesa](./configuring-playbook-ketesa.md) has full MAS integration**. Ketesa supports OIDC auth, user management, all session types (browser, OAuth2, compatibility), linked email addresses, upstream OAuth provider links, MAS policy data, and user creation through MAS. It is the recommended tool for managing homeservers running MAS."
+msgid "❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-admin.md) do not have full compatibility with MAS yet**. synapse-admin already supports [login with access token](https://github.com/etkecc/synapse-admin/pull/58), browsing users (which Synapse will internally fetch from MAS) and updating user avatars. However, editing users (passwords, etc.) now needs to happen directly against MAS using the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html), which synapse-admin cannot interact with yet."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:56
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:51
 msgid "❌ **Some services experience issues when authenticating via MAS**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:58
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:53
-msgid "[Reminder bot](configuring-playbook-bot-matrix-reminder-bot.md) seems to be losing some of its state on each restart and may reschedule old reminders once again"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:60
 msgid "[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first time around, but it consistently fails after restarting:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:62
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:55
 msgid "cannot initialize matrix bot error=\"olm account is marked as shared, keys seem to have disappeared from the server\""
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:64
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:57
+msgid "[matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) fails to start (see [element-hq/matrix-authentication-service#3439](https://github.com/element-hq/matrix-authentication-service/issues/3439))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:58
+msgid "Other services may be similarly affected. This list is not exhaustive."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:60
 msgid "❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:66
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:62
+msgid "⚠️ **You will need to have email sending configured** (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:64
 msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
 msgstr ""
 
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:66
+msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the \"admin\" flag for users (as found in the Synapse database). All users are imported as non-admin — see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`)"
+msgstr ""
+
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:68
-msgid "⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependent on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch."
+msgid "⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependant on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:70
@@ -166,7 +182,7 @@ msgid "✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), [El
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:78
-msgid "✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work"
+msgid "✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work. Going through the old login flow does not require users to have a verified email address, as [is the case](https://github.com/element-hq/matrix-authentication-service/issues/1505) for the new SSO-based login flow."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:80
@@ -194,7 +210,7 @@ msgid "Existing homeserver"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:92
-msgid "Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating with Matrix Authentication Service yet."
+msgid "Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:94
@@ -282,346 +298,326 @@ msgstr ""
 msgid "The playbook exposes a `matrix_authentication_service_config_upstream_oauth2_providers` variable for controlling this setting."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:273
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:269
 msgid "💡 Refer to the [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers) for the most up-to-date schema and example for providers. The value shown above here may be out of date."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:275
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:271
 msgid "⚠️ The syntax for existing [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) is slightly different, so you will need to adjust your configuration when switching from Synapse OIDC to MAS upstream OAuth2."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:277
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:273
 msgid "⚠️ When [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) which contains OIDC-sourced users, you will need to:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:279
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:275
 msgid "[Configure upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:280
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:276
 msgid "go through the [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) process"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:281
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:277
 msgid "remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:283
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:279
-msgid "Extending the configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:285
-msgid "There are some additional things you may wish to configure about the component."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:287
-msgid "Take a look at:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:289
-msgid "`roles/custom/matrix-authentication-service/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:290
-msgid "`roles/custom/matrix-authentication-service/templates/config.yaml.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_authentication_service_configuration_extension_yaml` variable"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:292
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:294
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:281
 msgid "Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:301
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:288
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:303
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:290
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:305
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:292
 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. Note these shortcuts run the `ensure-matrix-users-created` tag too."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:307
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:294
 msgid "If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:309
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:296
 msgid "💡 After installation, you should [verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:311
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:298
 msgid "Migrating an existing Synapse homeserver to Matrix Authentication Service"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:313
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:300
 msgid "Our migration guide is loosely based on the upstream [Migrating an existing homeserver](https://element-hq.github.io/matrix-authentication-service/setup/migration.html) guide."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:315
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:302
-msgid "Migration is done via a sub-command called `syn2mas`, which the playbook could run for you (in a container)."
+msgid "Migration is done via a tool called `syn2mas`, which the playbook could run for you (in a container)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:317
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:304
 msgid "The installation + migration steps are like this:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:319
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:306
 msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) to **disable the integration between the homeserver and MAS**. This is done by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:321
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:308
 msgid "Perform the initial [installation](#installing). At this point:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:323
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:310
 msgid "Matrix Authentication Service will be installed. Its database will be empty, so it cannot validate existing access tokens or authentication users yet."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:325
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:312
 msgid "The homeserver will still continue to use its local database for validating existing access tokens."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:327
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:314
 msgid "Various [compatibility layer URLs](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) are not yet installed. New login sessions will still be forwarded to the homeserver, which is capable of completing them."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:329
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:316
 msgid "The `matrix-user-creator` role would be suppressed, so that it doesn't automatically attempt to create users (for bots, etc.) in the MAS database. These user accounts likely already exist in Synapse's user database and could be migrated over (via syn2mas, as per the steps below), so creating them in the MAS database would have been unnecessary and potentially problematic (conflicts during the syn2mas migration)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:331
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:318
-msgid "Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration command does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
+msgid "Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration tool does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:333
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:320
 msgid "[Migrate your data from Synapse to Matrix Authentication Service using syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-service-using-syn2mas)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:335
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:322
 msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) again, to:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:337
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:324
 msgid "remove the `matrix_authentication_service_migration_in_progress: false` line"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:339
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:326
 msgid "if you had been using [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:341
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:328
 msgid "Perform the [installation](#installing) again. At this point:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:343
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:330
 msgid "The homeserver will start delegating authentication to MAS."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:345
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:332
 msgid "The compatibility layer URLs will be installed. New login sessions will be completed by MAS."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:347
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:334
 msgid "[Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:349
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:336
 msgid "Migrate your data from Synapse to Matrix Authentication Service using syn2mas"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:351
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:338
+msgid "We **don't** ask you to [run the `syn2mas` migration advisor command](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#run-the-migration-advisor), because it only gives you the green light if your Synapse configuration (`homeserver.yaml`) is configured in a way that's compatible with MAS (delegating authentication to MAS; disabling Synapse's password config; etc.). Until we migrate your data with the `syn2mas` tool, we intentionally avoid doing these changes to allow existing user sessions to work."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:340
 msgid "You can invoke the `syn2mas` tool via the playbook by running the playbook's `matrix-authentication-service-mas-cli-syn2mas` tag. We recommend first doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:353
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:342
 msgid "Configuring syn2mas"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:355
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:344
 msgid "If you're using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to [Configuring upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:357
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:346
 msgid "If you only have local (non-OIDC) users in your Synapse database, you can likely run `syn2mas` as-is (without doing additional configuration changes)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:359
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:348
 msgid "When you're done with potentially configuring `syn2mas`, proceed to doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:361
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:350
 msgid "Configuring upstream OIDC provider mapping for syn2mas"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:363
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:352
-msgid "Since Matrix Authentication Service v0.16.0 (which replaced the standalone `syn2mas` tool with a `mas-cli syn2mas` sub-command), OIDC configuration (mapping from your old OIDC configuration to your new one, etc) is meant to be configured in the Matrix Authentication Service configuration (via `matrix_authentication_service_config_upstream_oauth2_providers`) as a `synapse_idp_id` property for each provider."
+msgid "If you have existing OIDC users in your Synapse user database (which will be the case if when using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)), you may need to pass an additional `--upstreamProviderMapping` argument to the `syn2mas` tool to tell it which provider (on the Synapse side) maps to which other provider on the MAS side."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:365
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:354
-msgid "You can refer to the [Map any upstream SSO providers](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#map-any-upstream-sso-providers) section of the MAS documentation for figuring out how to set the `synapse_idp_id` value in `matrix_authentication_service_config_upstream_oauth2_providers` correctly."
+msgid "If you don't do this, `syn2mas` would report errors like this one:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:367
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:356
-msgid "Performing a syn2mas dry-run"
+msgid "[FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: Unknown upstream provider oidc-keycloak]"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:369
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:358
-msgid "Having [configured syn2mas](#configuring-syn2mas), we recommend doing a [dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to verify that everything will work out as expected."
+msgid "Below is an example situation and a guide for how to solve it."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:371
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:360
-msgid "A dry-run would not cause downtime, because it avoids stopping Synapse."
+msgid "If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) named `keycloak`, in the Synapse database users would be associated with the `oidc-keycloak` provider (note the `oidc-` prefix that was added automatically by Synapse to your `idp_id` value)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:362
+msgid "The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` on the MAS side, as defined in `matrix_authentication_service_config_upstream_oauth2_providers` (see the [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section above)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:364
+msgid "To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `vars.yml` file:"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:373
-msgid "To perform a dry-run, run:"
+msgid "Performing a syn2mas dry-run"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:375
+msgid "Having [configured syn2mas](#configuring-syn2mas), we recommend doing a [dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to verify that everything will work out as expected."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:377
+msgid "A dry-run would not cause downtime, because it avoids stopping Synapse."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:379
-msgid "Observe the command output (especially the last line of the the syn2mas output). If you are confident that the migration will work out as expected, you can proceed with a [real migration](#performing-a-real-syn2mas-migration)."
+msgid "To perform a dry-run, run:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:381
-msgid "Performing a real syn2mas migration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:383
-msgid "Before performing a real migration make sure:"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:385
-msgid "you've familiarized yourself with the [expectations](#expectations)"
+msgid "Observe the command output (especially the last line of the the syn2mas output). If you are confident that the migration will work out as expected, you can proceed with a [real migration](#performing-a-real-syn2mas-migration)."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:387
-msgid "you've performed a Postgres backup, just in case"
+msgid "Performing a real syn2mas migration"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:389
-msgid "you're aware of the irreversibility of the migration process without disruption after users have created new login sessions via the new MAS setup"
+msgid "Before performing a real migration make sure:"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:391
-msgid "you've [configured syn2mas](#configuring-syn2mas), especially if you've used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)"
+msgid "you've familiarized yourself with the [expectations](#expectations)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:393
-msgid "you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and don't see any issues in its output"
+msgid "you've performed a Postgres backup, just in case"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:395
-msgid "To perform a real migration, run the `matrix-authentication-service-mas-cli-syn2mas` tag **without** the `matrix_authentication_service_syn2mas_migrate_dry_run` variable:"
+msgid "you're aware of the irreversibility of the migration process without disruption after users have created new login sessions via the new MAS setup"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:397
+msgid "you've [configured syn2mas](#configuring-syn2mas), especially if you've used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:399
+msgid "you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and don't see any issues in its output"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:401
-msgid "After `syn2mas` completes, Synapse will intentionally remain stopped to avoid new registrations or other authentication changes from being accepted before the migration is completed. Continue with the next steps in this guide before re-running the installation."
+msgid "To perform a real migration, run the `matrix-authentication-service-mas-cli-syn2mas` tag **without** the `matrix_authentication_service_syn2mas_migrate_dry_run` variable:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:403
-msgid "Having performed a `syn2mas` migration once, trying to do it again will report errors (e.g. \"Error: The MAS database is not empty: rows found in at least `users`. Please drop and recreate the database, then try again.\")."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:405
-msgid "Verify that Matrix Authentication Service is installed correctly"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:407
-msgid "After [installation](#installing), run the `doctor` subcommand of the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) to verify that MAS is installed correctly."
+msgid "Having performed a `syn2mas` migration once, trying to do it again will report errors for users that were already migrated (e.g. \"Error: Unknown upstream provider oauth-delegated\")."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:409
-msgid "You can do it:"
+msgid "Verify that Matrix Authentication Service is installed correctly"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:411
-msgid "either via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`"
+msgid "After [installation](#installing), run the `doctor` subcommand of the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) to verify that MAS is installed correctly."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:413
-msgid "or by running the `mas-cli` script on the server (which invokes the `mas-cli` tool inside a container): `/matrix/matrix-authentication-service/bin/mas-cli doctor`"
+msgid "You can do it:"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:415
+msgid "either via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:417
+msgid "or by running the `mas-cli` script on the server (which invokes the `mas-cli` tool inside a container): `/matrix/matrix-authentication-service/bin/mas-cli doctor`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:419
 msgid "If successful, you should see some output that looks like this:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:427
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:431
-msgid "Usage"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:429
 msgid "Management"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:431
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:433
 msgid "You can use the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) (exposed via the `/matrix/matrix-authentication-service/bin/mas-cli` script) to perform administrative tasks against MAS."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:433
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:435
 msgid "This documentation page already mentions:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:435
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:437
 msgid "the `mas-cli doctor` sub-command in the [Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly) section, which you can run via the CLI and via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:437
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:439
 msgid "the `mas-cli manage register-user` sub-command in the [Registering users](./registering-users.md) documentation"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:439
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:441
 msgid "There are other sub-commands available. Run `/matrix/matrix-authentication-service/bin/mas-cli` to get an overview."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:441
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:443
 msgid "User registration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:443
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:445
 msgid "After Matrix Authentication Service is [installed](#installing), users need to be managed there (unless you're managing them in an [upstream OAuth2 provider](#upstream-oauth2-configuration))."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:445
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:447
 msgid "You can register users new users as described in the [Registering users](./registering-users.md) documentation (via `mas-cli manage register-user` or the Ansible playbook's `register-user` tag)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:447
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:449
 msgid "Working around email deliverability issues"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:449
-msgid "Matrix Authentication Service only sends emails when:"
-msgstr ""
-
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:451
-msgid "it verifies email addresses for users who are self-registering with a password"
+msgid "Because Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user, you may need to work around email deliverability issues if [your email-sending configuration](./configuring-playbook-email.md) is not working."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:453
-msgid "a user tries to add an email to their account"
+msgid "Matrix Authentication Service attempts to verify email addresses by sending a verification email to the address specified by the user whenever they log in to an account without a verified email address."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:455
-msgid "If Matrix Authentication Service tries to send an email and it fails because [your email-sending configuration](./configuring-playbook-email.md) is not working, you may need to work around email deliverability."
+msgid "If email delivery is not working, **you can retrieve the email configuration code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`)."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:457
-msgid "If email delivery is not working, **you can retrieve the email verification code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`)."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:459
 msgid "Alternatively, you can use the [`mas-cli` management tool](#management) to manually verify email addresses for users. Example: `/matrix/matrix-authentication-service/bin/mas-cli manage verify-email some.username email@example.com`"
 msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:461
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:463
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-authentication-service`."
-msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-synapse.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: bg\n"
@@ -19,305 +19,261 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-synapse.md:12
+#: ../../../docs/configuring-playbook-synapse.md:1
 msgid "Configuring Synapse (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:14
+#: ../../../docs/configuring-playbook-synapse.md:3
 msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, so that it works for the general case. If that's okay, you can skip this document."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:16
+#: ../../../docs/configuring-playbook-synapse.md:5
-msgid "💡 See this page for details about maintaining Synapse: [Synapse maintenance](maintenance-synapse.md)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:18
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:20
+#: ../../../docs/configuring-playbook-synapse.md:7
 msgid "Load balancing with workers"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:22
+#: ../../../docs/configuring-playbook-synapse.md:9
 msgid "To have Synapse gracefully handle thousands of users, worker support should be enabled. It factors out some homeserver tasks and spreads the load of incoming client and server-to-server traffic between multiple processes. More information can be found in the [official Synapse workers documentation](https://github.com/element-hq/synapse/blob/master/docs/workers.md) and [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:24
+#: ../../../docs/configuring-playbook-synapse.md:11
 msgid "To enable Synapse worker support, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:32
+#: ../../../docs/configuring-playbook-synapse.md:19
 msgid "By default, this enables the `one-of-each` [worker preset](#worker-presets), but you may wish to use another preset or [control the number of worker instances](#controlling-the-number-of-worker-instances)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:34
+#: ../../../docs/configuring-playbook-synapse.md:21
 msgid "Worker presets"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:36
+#: ../../../docs/configuring-playbook-synapse.md:23
 msgid "We support a few configuration presets (`matrix_synapse_workers_preset: one-of-each` being the default configuration right now):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:38
+#: ../../../docs/configuring-playbook-synapse.md:25
 msgid "(federation-only) `little-federation-helper` — a very minimal worker configuration to improve federation performance"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:39
+#: ../../../docs/configuring-playbook-synapse.md:26
 msgid "(generic) `one-of-each` — defaults to one worker of each supported type — no smart routing, just generic workers"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:40
+#: ../../../docs/configuring-playbook-synapse.md:27
 msgid "(specialized) `specialized-workers` — defaults to one worker of each supported type, but disables generic workers and uses [specialized workers](#specialized-workers) instead"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:42
+#: ../../../docs/configuring-playbook-synapse.md:29
 msgid "These presets represent a few common configurations. There are many worker types which can be mixed and matched based on your needs."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:44
+#: ../../../docs/configuring-playbook-synapse.md:31
 msgid "Generic workers"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:46
+#: ../../../docs/configuring-playbook-synapse.md:33
 msgid "Previously, the playbook only supported the most basic type of load-balancing. We call it **generic load-balancing** below, because incoming HTTP requests are sent to a generic worker. Load-balancing was done based on the requestor's IP address. This is simple, but not necessarily optimal. If you're accessing your account from multiple IP addresses (e.g. your mobile phone being on a different network than your PC), these separate requests may potentially be routed to different workers, each of which would need to cache roughly the same data."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:48
+#: ../../../docs/configuring-playbook-synapse.md:35
 msgid "This is **still the default load-balancing method (preset) used by the playbook**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:50
+#: ../../../docs/configuring-playbook-synapse.md:37
 msgid "To use generic load-balancing, do not specify `matrix_synapse_workers_preset` to make it use the default value (`one-of-each`), or better yet — explicitly set it as `one-of-each`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:52
+#: ../../../docs/configuring-playbook-synapse.md:39
 msgid "You may also consider [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:54
+#: ../../../docs/configuring-playbook-synapse.md:41
 msgid "Specialized workers"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:56
+#: ../../../docs/configuring-playbook-synapse.md:43
-msgid "The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requester's IP address, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** — the access token (username) of the requester and/or on the resource (room, etc.) being requested."
+msgid "The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requestor's IP adddress, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** — the access token (username) of the requestor and/or on the resource (room, etc.) being requested."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:58
+#: ../../../docs/configuring-playbook-synapse.md:45
 msgid "The playbook supports these **4 types** of specialized workers:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:60
+#: ../../../docs/configuring-playbook-synapse.md:47
 msgid "Room workers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) & [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs dedicated to handling specific rooms"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:61
+#: ../../../docs/configuring-playbook-synapse.md:48
 msgid "Sync workers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to synchronization (most notably [the `/sync` endpoint](https://spec.matrix.org/v1.9/client-server-api/#get_matrixclientv3sync))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:62
+#: ../../../docs/configuring-playbook-synapse.md:49
 msgid "Client readers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are not for specific rooms (handled by **room workers**) or for synchronization (handled by **sync workers**)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:63
+#: ../../../docs/configuring-playbook-synapse.md:50
 msgid "Federation readers — handles various [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which are not for specific rooms (handled by **room workers**)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:65
+#: ../../../docs/configuring-playbook-synapse.md:52
 msgid "To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:67
+#: ../../../docs/configuring-playbook-synapse.md:54
 msgid "Controlling the number of worker instances"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:69
+#: ../../../docs/configuring-playbook-synapse.md:56
 msgid "If you'd like more customization power, you can start with one of the [worker presets](#worker-presets) and then tweak various `matrix_synapse_workers_*_count` variables manually."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:71
+#: ../../../docs/configuring-playbook-synapse.md:58
 msgid "To find what variables are available for you to override in your own `vars.yml` configuration file, see the [`defaults/main.yml` file for the `matrix-synapse` Ansible role](../roles/custom/matrix-synapse/defaults/main.yml)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:73
+#: ../../../docs/configuring-playbook-synapse.md:60
 msgid "The only thing you **cannot** do is mix [generic workers](#generic-workers) and [specialized workers](#specialized-workers)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:75
+#: ../../../docs/configuring-playbook-synapse.md:62
 msgid "Effect of enabling workers on the rest of your server"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:77
+#: ../../../docs/configuring-playbook-synapse.md:64
 msgid "When Synapse workers are enabled, the integrated [Postgres database is tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum number of Postgres connections are increased from `200` to `500`. If you need to decrease or increase the number of maximum Postgres connections further, use the `postgres_max_connections` variable."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:79
+#: ../../../docs/configuring-playbook-synapse.md:66
-msgid "The `matrix-synapse` role also manages the `matrix-synapse-reverse-proxy-companion` component for load-balancing with workers. This component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly."
+msgid "A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and component handles load-balancing for workers. This role/component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:81
+#: ../../../docs/configuring-playbook-synapse.md:68
 msgid "In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/element-hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:83
+#: ../../../docs/configuring-playbook-synapse.md:70
-msgid "Limit joining heavy rooms on constrained hosts"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:85
-msgid "If your server is underpowered, joining heavy rooms can cause Synapse to consume a lot of resources and be unavailable for long (while it catches up)."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:87
-msgid "To avoid this, Synapse can be configured to reject joins for remote rooms that are too complex before users enter them."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:89
-msgid "Complexity is computed as `current_state_events / 500` (Synapse state event count for current room state). When the resulting value is higher than `matrix_synapse_limit_remote_rooms_complexity` and `matrix_synapse_limit_remote_rooms_enabled` is `true`, Synapse blocks joining the room."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:91
-msgid "We recommend using this as a guardrail on low-resource servers:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:106
 msgid "Synapse + OpenID Connect for Single-Sign-On"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:108
+#: ../../../docs/configuring-playbook-synapse.md:72
 msgid "💡 An alternative to setting up OIDC in Synapse is to use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS). Newer clients (like Element X) only support SSO-based authentication via MAS and not via the legacy Synapse OIDC setup described below. That said, MAS is still a new experimental service which comes with its own downsides. Consult its documentation to learn if it will be a good fit for your deployment."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:110
+#: ../../../docs/configuring-playbook-synapse.md:74
 msgid "If you'd like to use OpenID Connect authentication with Synapse, you'll need some additional configuration."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:112
+#: ../../../docs/configuring-playbook-synapse.md:76
 msgid "This example configuration is for [keycloak](https://www.keycloak.org/), an opensource Identity Provider maintained by Red Hat."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:114
+#: ../../../docs/configuring-playbook-synapse.md:78
 msgid "For more detailed documentation on available options and how to setup keycloak, see the [Synapse documentation on OpenID Connect with keycloak](https://github.com/element-hq/synapse/blob/develop/docs/openid.md#keycloak)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:116
+#: ../../../docs/configuring-playbook-synapse.md:80
-#, python-format, python-brace-format
+#, python-format
 msgid "In case you encounter errors regarding the parsing of the variables, you can try to add `{% raw %}` and `{% endraw %}` blocks around them. For example ;"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:137
+#: ../../../docs/configuring-playbook-synapse.md:101
 msgid "Customizing templates"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:139
+#: ../../../docs/configuring-playbook-synapse.md:103
 msgid "[Templates](https://github.com/element-hq/synapse/blob/develop/docs/templates.md) are used by Synapse for showing **certain web pages** handled by the server, as well as for **email notifications**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:141
+#: ../../../docs/configuring-playbook-synapse.md:105
 msgid "This playbook allows you to customize the default templates (see the [`synapse/res/templates` directory](https://github.com/element-hq/synapse/tree/develop/synapse/res/templates))."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:143
+#: ../../../docs/configuring-playbook-synapse.md:107
 msgid "If template customization is enabled, the playbook will build a custom container image based on the official one."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:145
+#: ../../../docs/configuring-playbook-synapse.md:109
 msgid "Your custom templates need to live in a public or private git repository. This repository will be cloned during Synapse image customization (during the playbook run)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:147
+#: ../../../docs/configuring-playbook-synapse.md:111
 msgid "To enable template customizations, add the following configuration to your `vars.yml` file (adapt to your needs):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:173
+#: ../../../docs/configuring-playbook-synapse.md:137
 msgid "As mentioned in Synapse's Templates documentation, Synapse will fall back to its own templates if a template is not found in that directory. Due to this, it's recommended to only store and maintain template files in your repository if you need to make custom changes. Other files (which you don't need to change), should not be duplicated, so that you don't need to worry about getting out-of-sync with the original Synapse templates."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:175
+#: ../../../docs/configuring-playbook-synapse.md:139
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:177
+#: ../../../docs/configuring-playbook-synapse.md:141
 msgid "There are some additional things you may wish to configure about the server."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:179
+#: ../../../docs/configuring-playbook-synapse.md:143
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:181
+#: ../../../docs/configuring-playbook-synapse.md:145
 msgid "`roles/custom/matrix-synapse/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:182
+#: ../../../docs/configuring-playbook-synapse.md:146
 msgid "`roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2` for the server's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_synapse_configuration_extension_yaml` variable"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:184
+#: ../../../docs/configuring-playbook-synapse.md:148
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:186
+#: ../../../docs/configuring-playbook-synapse.md:150
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:193
+#: ../../../docs/configuring-playbook-synapse.md:157
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:195
+#: ../../../docs/configuring-playbook-synapse.md:159
 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. Note these shortcuts run the `ensure-matrix-users-created` tag too."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:197
+#: ../../../docs/configuring-playbook-synapse.md:161
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:199
+#: ../../../docs/configuring-playbook-synapse.md:163
-msgid "Ketesa"
+msgid "Synapse Admin"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:201
+#: ../../../docs/configuring-playbook-synapse.md:165
-msgid "[Ketesa](configuring-playbook-ketesa.md) is a fully-featured web UI for administrating your homeserver — managing users, rooms, media, sessions, and more."
+msgid "With [Synapse Admin](configuring-playbook-synapse-admin.md), certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:203
+#: ../../../docs/configuring-playbook-synapse.md:167
-msgid "The playbook can install and configure Ketesa for you. For details about it, see [this page](configuring-playbook-ketesa.md)."
+msgid "The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:205
+#: ../../../docs/configuring-playbook-synapse.md:169
 msgid "Monitoring Synapse Metrics with Prometheus and Grafana"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:207
+#: ../../../docs/configuring-playbook-synapse.md:171
 msgid "This playbook allows you to enable Synapse metrics, which can provide insight into the performance and activity of Synapse."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:209
+#: ../../../docs/configuring-playbook-synapse.md:173
-msgid "To enable Synapse runtime metrics, see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md) and [its subsection](configuring-playbook-prometheus-grafana.md#expose-metrics-of-other-services-roles)"
+msgid "To enable Synapse runtime metrics see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:211
+#: ../../../docs/configuring-playbook-synapse.md:175
 msgid "To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
 msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:213
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:215
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-synapse`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:217
-msgid "Increase logging verbosity"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:219
-msgid "Because Synapse is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:221
-msgid "If you'd like to debug an issue or [report a Synapse bug](https://github.com/element-hq/synapse/issues/new/choose) to the developers, it'd be better if you temporarily increase the logging verbosity to `INFO`. To do so, add the following configuration to your `vars.yml` file and re-run the playbook:"
-msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: bg\n"
@@ -19,568 +19,528 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook.md:17
+#: ../../../docs/configuring-playbook.md:1
 msgid "Configuring the playbook"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:19
+#: ../../../docs/configuring-playbook.md:3
-msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)</sup>"
+msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)</sup>"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:21
+#: ../../../docs/configuring-playbook.md:5
 msgid "If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:23
+#: ../../../docs/configuring-playbook.md:7
 msgid "create a directory to hold your configuration (`mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\")"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:25
+#: ../../../docs/configuring-playbook.md:9
 msgid "copy the sample configuration file (`cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:27
+#: ../../../docs/configuring-playbook.md:11
-msgid "edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files (after importing external roles with `just update` into `roles/galaxy`) and see if there's something you'd like to copy over and override in your `vars.yml` configuration file."
+msgid "edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's something you'd like to copy over and override in your `vars.yml` configuration file."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:29
+#: ../../../docs/configuring-playbook.md:13
 msgid "copy the sample inventory hosts file (`cp examples/hosts inventory/hosts`)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:31
+#: ../../../docs/configuring-playbook.md:15
 msgid "edit the inventory hosts file (`inventory/hosts`) to your liking"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:33
+#: ../../../docs/configuring-playbook.md:17
-msgid "(optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system. The `inventory` directory path is ignored via `.gitignore`, so it won't be part of the playbook repository. You can safely create a new git repository inside that directory with `git init`, etc."
+msgid "(optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:35
+#: ../../../docs/configuring-playbook.md:19
 msgid "(optional, advanced) to run Ansible against multiple servers with different `sudo` credentials, you can copy the sample inventory hosts yaml file for each of your hosts: (`cp examples/host.yml inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin/ansible-all-hosts.sh) script [in the installation step](installing.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:37
+#: ../../../docs/configuring-playbook.md:21
 msgid "For a basic Matrix installation, that's all you need."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:39
+#: ../../../docs/configuring-playbook.md:23
 msgid "For a more custom setup, see the [Other configuration options](#other-configuration-options) below."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:41
+#: ../../../docs/configuring-playbook.md:25
 msgid "[▶️](installing.md) When you're done with all the configuration you'd like to do, continue with [Installing](installing.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:43
+#: ../../../docs/configuring-playbook.md:27
 msgid "Other configuration options"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:45
+#: ../../../docs/configuring-playbook.md:29
 msgid "**Note**: some of the roles like one for integrating Etherpad or Jitsi are managed by their own repositories, and the configuration files for them cannot be found locally (in `roles/galaxy`) until those roles are fetched from the upstream projects. Check [requirements.yml](../requirements.yml) for the URLs of those roles."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:47
+#: ../../../docs/configuring-playbook.md:31
 msgid "Core service adjustments"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:49
+#: ../../../docs/configuring-playbook.md:33
 msgid "Homeserver configuration:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:50
+#: ../../../docs/configuring-playbook.md:34
 msgid "[Configuring Synapse](configuring-playbook-synapse.md), if you're going with the default/recommended homeserver implementation"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:52
+#: ../../../docs/configuring-playbook.md:36
 msgid "[Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:54
+#: ../../../docs/configuring-playbook.md:38
-msgid "[Configuring continuwuity](configuring-playbook-continuwuity.md), if you've switched to the [continuwuity](https://continuwuity.org) homeserver implementation"
+msgid "[Configuring conduwuit](configuring-playbook-conduwuit.md), if you've switched to the [conduwuit](https://conduwuit.puppyirl.gay/) homeserver implementation"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:56
+#: ../../../docs/configuring-playbook.md:40
 msgid "[Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:58
+#: ../../../docs/configuring-playbook.md:42
 msgid "Server components:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:59
+#: ../../../docs/configuring-playbook.md:43
 msgid "[Using an external PostgreSQL server](configuring-playbook-external-postgres.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:61
+#: ../../../docs/configuring-playbook.md:45
 msgid "[Configuring a TURN server](configuring-playbook-turn.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:63
+#: ../../../docs/configuring-playbook.md:47
 msgid "[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:65
+#: ../../../docs/configuring-playbook.md:49
 msgid "[Using your own webserver, instead of this playbook's Traefik reverse-proxy](configuring-playbook-own-webserver.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:67
+#: ../../../docs/configuring-playbook.md:51
 msgid "[Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:69
+#: ../../../docs/configuring-playbook.md:53
 msgid "[Adjusting email-sending settings](configuring-playbook-email.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:71
+#: ../../../docs/configuring-playbook.md:55
+msgid "[Setting up ma1sd Identity Server](configuring-playbook-ma1sd.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:57
 msgid "[Setting up Dynamic DNS](configuring-playbook-dynamic-dns.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:73
+#: ../../../docs/configuring-playbook.md:59
 msgid "Server connectivity:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:74
+#: ../../../docs/configuring-playbook.md:60
 msgid "[Enabling Telemetry for your Matrix server](configuring-playbook-telemetry.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:76
+#: ../../../docs/configuring-playbook.md:62
 msgid "[Controlling Matrix federation](configuring-playbook-federation.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:78
+#: ../../../docs/configuring-playbook.md:64
-msgid "[Configuring IPv6](./configuring-ipv6.md)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:80
 msgid "Clients"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:82
+#: ../../../docs/configuring-playbook.md:66
 msgid "Web clients for Matrix that you can host on your own domains."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:84
+#: ../../../docs/configuring-playbook.md:68
 msgid "[Configuring Element Web](configuring-playbook-client-element-web.md), if you're going with the default/recommended client"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:86
+#: ../../../docs/configuring-playbook.md:70
 msgid "[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a lightweight Matrix client with legacy and mobile browser support"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:88
+#: ../../../docs/configuring-playbook.md:72
 msgid "[Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing primarily on simple, elegant and secure interface"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:90
+#: ../../../docs/configuring-playbook.md:74
-msgid "[Setting up Sable](configuring-playbook-client-sable.md), if you've enabled [Sable](https://github.com/7w1/sable), a web client focusing primarily on simple, elegant and secure interface"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:92
 msgid "[Setting up SchildiChat Web](configuring-playbook-client-schildichat-web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a web client based on [Element Web](https://element.io/) with some extras and tweaks"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:94
+#: ../../../docs/configuring-playbook.md:76
-msgid "[Setting up FluffyChat Web](configuring-playbook-client-fluffychat-web.md), if you've enabled [FluffyChat Web](https://github.com/krille-chan/fluffychat), a cute cross-platform messenger (web, iOS, Android) for Matrix written in [Flutter](https://flutter.dev/)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:97
 msgid "Authentication and user-related"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:99
+#: ../../../docs/configuring-playbook.md:78
 msgid "Extend and modify how users are authenticated on your homeserver."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:101
+#: ../../../docs/configuring-playbook.md:80
 msgid "[Setting up Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (Next-generation auth for Matrix, based on OAuth 2.0/OIDC)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:103
+#: ../../../docs/configuring-playbook.md:82
 msgid "[Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:105
+#: ../../../docs/configuring-playbook.md:84
-msgid "[Setting up Ketesa](configuring-playbook-ketesa.md)"
+msgid "[Setting up Synapse Admin](configuring-playbook-synapse-admin.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:107
+#: ../../../docs/configuring-playbook.md:86
 msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:109
+#: ../../../docs/configuring-playbook.md:88
 msgid "[Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:111
+#: ../../../docs/configuring-playbook.md:90
 msgid "[Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:113
+#: ../../../docs/configuring-playbook.md:92
 msgid "[Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:115
+#: ../../../docs/configuring-playbook.md:94
 msgid "[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:117
+#: ../../../docs/configuring-playbook.md:96
 msgid "[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:119
+#: ../../../docs/configuring-playbook.md:98
 msgid "[Setting up Matrix User Verification Service](configuring-playbook-user-verification-service.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:121
+#: ../../../docs/configuring-playbook.md:100
 msgid "File Storage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:123
+#: ../../../docs/configuring-playbook.md:102
 msgid "Use alternative file storage to the default `media_store` folder."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:125
+#: ../../../docs/configuring-playbook.md:104
-msgid "[Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
+msgid "[Storing Matrix media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:127
+#: ../../../docs/configuring-playbook.md:106
 msgid "[Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:129
+#: ../../../docs/configuring-playbook.md:108
-msgid "[Storing Synapse media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)"
+msgid "[Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:131
+#: ../../../docs/configuring-playbook.md:110
-msgid "[Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:133
 msgid "Bridging other networks"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:135
+#: ../../../docs/configuring-playbook.md:112
 msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:137
+#: ../../../docs/configuring-playbook.md:114
 msgid "[Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) — a common guide for configuring mautrix bridges"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:139
+#: ../../../docs/configuring-playbook.md:116
-msgid "[Setting up Mautrix Bluesky bridging](configuring-playbook-bridge-mautrix-bluesky.md)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:141
 msgid "[Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:143
+#: ../../../docs/configuring-playbook.md:118
 msgid "[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:145
+#: ../../../docs/configuring-playbook.md:120
 msgid "[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:147
+#: ../../../docs/configuring-playbook.md:122
 msgid "[Setting up Mautrix Google Messages bridging](configuring-playbook-bridge-mautrix-gmessages.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:149
+#: ../../../docs/configuring-playbook.md:124
 msgid "[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-mautrix-whatsapp.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:151
+#: ../../../docs/configuring-playbook.md:126
 msgid "[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:153
+#: ../../../docs/configuring-playbook.md:128
 msgid "[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:155
+#: ../../../docs/configuring-playbook.md:130
 msgid "[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-mautrix-googlechat.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:157
+#: ../../../docs/configuring-playbook.md:132
 msgid "[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:159
+#: ../../../docs/configuring-playbook.md:134
 msgid "[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-signal.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:161
+#: ../../../docs/configuring-playbook.md:136
 msgid "[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](configuring-playbook-bridge-mautrix-wsproxy.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:163
+#: ../../../docs/configuring-playbook.md:138
 msgid "[Setting up Appservice IRC bridging](configuring-playbook-bridge-appservice-irc.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:165
+#: ../../../docs/configuring-playbook.md:140
 msgid "[Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:167
+#: ../../../docs/configuring-playbook.md:142
+msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:144
 msgid "[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-appservice-kakaotalk.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:169
+#: ../../../docs/configuring-playbook.md:146
 msgid "[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:171
+#: ../../../docs/configuring-playbook.md:148
 msgid "[Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) — a bridge between Matrix and multiple project management services, such as [GitHub](https://github.com), [GitLab](https://about.gitlab.com) and [JIRA](https://www.atlassian.com/software/jira)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:173
+#: ../../../docs/configuring-playbook.md:150
+msgid "[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:152
+msgid "[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:154
+msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:156
+msgid "[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:158
 msgid "[Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-puppet-groupme.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:175
+#: ../../../docs/configuring-playbook.md:160
-msgid "[Setting up Steam bridging](configuring-playbook-bridge-steam.md)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:177
 msgid "[Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-puppet-steam.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:179
+#: ../../../docs/configuring-playbook.md:162
+msgid "[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:164
 msgid "[Setting up Postmoogle email bridging](configuring-playbook-bridge-postmoogle.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:181
+#: ../../../docs/configuring-playbook.md:166
 msgid "[Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-bridge-sms.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:183
+#: ../../../docs/configuring-playbook.md:168
 msgid "[Setting up Heisenbridge bouncer-style IRC bridging](configuring-playbook-bridge-heisenbridge.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:185
+#: ../../../docs/configuring-playbook.md:170
 msgid "[Setting up WeChat bridging](configuring-playbook-bridge-wechat.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:187
+#: ../../../docs/configuring-playbook.md:172
 msgid "Bots"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:189
+#: ../../../docs/configuring-playbook.md:174
 msgid "Bots provide various additional functionality to your installation."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:191
+#: ../../../docs/configuring-playbook.md:176
 msgid "[Setting up baibot](configuring-playbook-bot-baibot.md) — a bot through which you can talk to various [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) services ([OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) and [others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:193
+#: ../../../docs/configuring-playbook.md:178
 msgid "[Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) — a bot to remind you about stuff"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:195
+#: ../../../docs/configuring-playbook.md:180
 msgid "[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) — a bot to create and manage registration tokens to invite users"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:197
+#: ../../../docs/configuring-playbook.md:182
 msgid "[Setting up maubot](configuring-playbook-bot-maubot.md) — a plugin-based Matrix bot system"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:199
+#: ../../../docs/configuring-playbook.md:184
 msgid "[Setting up Honoroit](configuring-playbook-bot-honoroit.md) — a helpdesk bot"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:201
+#: ../../../docs/configuring-playbook.md:186
 msgid "[Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) — a moderation tool/bot"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:203
+#: ../../../docs/configuring-playbook.md:188
 msgid "[Setting up Draupnir](configuring-playbook-bot-draupnir.md) — a moderation tool/bot, forked from Mjolnir and maintained by its former leader developer"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:205
+#: ../../../docs/configuring-playbook.md:190
 msgid "[Setting up Draupnir for all/D4A](configuring-playbook-appservice-draupnir-for-all.md) — like the [Draupnir bot](configuring-playbook-bot-draupnir.md) mentioned above, but running in appservice mode and supporting multiple instances"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:207
+#: ../../../docs/configuring-playbook.md:192
 msgid "[Setting up Buscarron](configuring-playbook-bot-buscarron.md) — a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:209
+#: ../../../docs/configuring-playbook.md:194
 msgid "Administration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:211
+#: ../../../docs/configuring-playbook.md:196
 msgid "Services that help you in administrating and monitoring your Matrix installation."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:213
+#: ../../../docs/configuring-playbook.md:198
 msgid "[Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:215
+#: ../../../docs/configuring-playbook.md:200
 msgid "[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:217
+#: ../../../docs/configuring-playbook.md:202
+msgid "[Enabling metrics and graphs for NginX logs](configuring-playbook-prometheus-nginxlog.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:204
 msgid "[Setting up the rageshake bug report server](configuring-playbook-rageshake.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:219
+#: ../../../docs/configuring-playbook.md:206
 msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:221
+#: ../../../docs/configuring-playbook.md:208
 msgid "Backups:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:222
+#: ../../../docs/configuring-playbook.md:209
 msgid "[Setting up BorgBackup](configuring-playbook-backup-borg.md) — a full Matrix server backup solution, including the Postgres database"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:224
+#: ../../../docs/configuring-playbook.md:211
-msgid "[Setting up Postgres backup](configuring-playbook-postgres-backup.md) — a Postgres-database backup solution (note: does not include other files)"
+msgid "[Setting up postgres backup](configuring-playbook-postgres-backup.md) — a Postgres-database backup solution (note: does not include other files)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:226
+#: ../../../docs/configuring-playbook.md:213
 msgid "Other specialized services"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:228
+#: ../../../docs/configuring-playbook.md:215
 msgid "Various services that don't fit any other categories."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:230
+#: ../../../docs/configuring-playbook.md:217
-msgid "[Setting up Element Call](configuring-playbook-element-call.md) — a native Matrix video conferencing application, built on top of the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) (optional)"
+msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:232
+#: ../../../docs/configuring-playbook.md:219
-msgid "[Setting up LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md) - a component of the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:234
-msgid "[Setting up LiveKit Server](configuring-playbook-livekit-server.md) - a component of the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:236
-msgid "[Setting up Matrix RTC](configuring-playbook-matrix-rtc.md) (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:238
 msgid "[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:240
+#: ../../../docs/configuring-playbook.md:221
 msgid "[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:242
+#: ../../../docs/configuring-playbook.md:223
-msgid "[Setting up Matrix.to](configuring-playbook-matrixto.md)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:244
 msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:246
+#: ../../../docs/configuring-playbook.md:225
 msgid "[Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:248
+#: ../../../docs/configuring-playbook.md:227
 msgid "[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) — a federated comment system built on Matrix"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:250
+#: ../../../docs/configuring-playbook.md:229
 msgid "[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:252
+#: ../../../docs/configuring-playbook.md:231
 msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:254
+#: ../../../docs/configuring-playbook.md:233
 msgid "[Setting up the ntfy push notifications server](configuring-playbook-ntfy.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:256
+#: ../../../docs/configuring-playbook.md:235
 msgid "Deprecated / unmaintained / removed services"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:258
+#: ../../../docs/configuring-playbook.md:237
 msgid "**Note**: since a deprecated or unmaintained service will not be updated, its bug or vulnerability will be unlikely to get patched. It is recommended to migrate from the service to an alternative if any, and make sure to do your own research before you decide to keep it running nonetheless."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:260
+#: ../../../docs/configuring-playbook.md:239
-msgid "[Configuring conduwuit](configuring-playbook-conduwuit.md) (removed; this component has been abandoned and unmaintained)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:262
 msgid "[Setting up the Sliding Sync proxy](configuring-playbook-sliding-sync-proxy.md) for clients which require Sliding Sync support (like old Element X versions, before it got switched to Simplified Sliding Sync)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:264
+#: ../../../docs/configuring-playbook.md:241
-msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md) (removed; this component has been discontinued)"
+msgid "[Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (deprecated; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:266
+#: ../../../docs/configuring-playbook.md:243
-msgid "[Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (deprecated; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be [installed using this playbook](configuring-playbook-bridge-hookshot.md))"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:268
 msgid "[Setting up the Dimension integration manager](configuring-playbook-dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299); after [installing](installing.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:270
+#: ../../../docs/configuring-playbook.md:245
-msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md) (removed; the author suggests taking a look at [Postmoogle](https://github.com/etkecc/postmoogle) as a replacement, which can also be [installed using this playbook](configuring-playbook-bridge-postmoogle.md))"
+msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md) (unmaintained; the author suggests taking a look at [Postmoogle](https://github.com/etkecc/postmoogle) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-postmoogle.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:272
+#: ../../../docs/configuring-playbook.md:247
-msgid "[Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be [installed using this playbook](configuring-playbook-bridge-hookshot.md))"
+msgid "[Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:274
+#: ../../../docs/configuring-playbook.md:249
-msgid "[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md) (removed; Skype has been discontinued since May 2025)"
+msgid "[Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) (unmaintained; the bridge's author suggests taking a look at [baibot](https://github.com/etkecc/baibot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bot-baibot.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:276
+#: ../../../docs/configuring-playbook.md:251
-msgid "[Setting up ma1sd Identity Server](configuring-playbook-ma1sd.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook.)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:278
-msgid "[Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) (unmaintained; the bridge's author suggests taking a look at [baibot](https://github.com/etkecc/baibot) as a replacement, which can also be [installed using this playbook](configuring-playbook-bot-baibot.md))"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:280
 msgid "[Setting up Mautrix Facebook bridging](configuring-playbook-bridge-mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-meta-messenger.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:282
+#: ../../../docs/configuring-playbook.md:253
+msgid "[Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with [mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:255
 msgid "[Setting up Mautrix Instagram bridging](configuring-playbook-bridge-mautrix-instagram.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:284
+#: ../../../docs/configuring-playbook.md:257
-msgid "[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md))"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:286
-msgid "[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md))"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:288
 msgid "[Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-puppet-skype.md) (removed; this component has been broken for a long time, so it has been removed from the playbook. Consider [setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md))"
 msgstr ""
-
-#: ../../../docs/configuring-playbook.md:290
-msgid "[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md))"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:292
-msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md))"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:294
-msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md) (removed; since Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0) the same feature is available natively.)"
-msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/container-images.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: bg\n"
@@ -19,21 +19,21 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/container-images.md:18
+#: ../../../docs/container-images.md:1
 msgid "Container images used by the playbook"
 msgstr ""
 
-#: ../../../docs/container-images.md:20
+#: ../../../docs/container-images.md:3
 msgid "This page summarizes the container ([Docker](https://www.docker.com/)) images used by the playbook when setting up your server."
 msgstr ""
 
-#: ../../../docs/container-images.md:22
+#: ../../../docs/container-images.md:5
 msgid "We try to stick to official images (provided by their respective projects) as much as possible."
 msgstr ""
 
-#: ../../../docs/container-images.md:24
+#: ../../../docs/container-images.md:7
 msgid "Homeserver"
 msgstr ""
 
@@ -86,15 +86,15 @@ msgid "Storing your data and managing your presence in the [Matrix](http://matri
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[continuwuity](configuring-playbook-continuwuity.md)"
+msgid "[conduwuit](configuring-playbook-conduwuit.md)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[continuwuation/continuwuity](https://forgejo.ellis.link/continuwuation/continuwuity)"
+msgid "[girlbossceo/conduwuit](https://ghcr.io/girlbossceo/conduwuit)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. continuwuity is a continuation of conduwuit."
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit is a fork of Conduit."
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -109,11 +109,11 @@ msgstr ""
 msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse."
 msgstr ""
 
-#: ../../../docs/container-images.md:33
+#: ../../../docs/container-images.md:16
 msgid "Clients"
 msgstr ""
 
-#: ../../../docs/container-images.md:35
+#: ../../../docs/container-images.md:18
 msgid "Web clients for Matrix that you can host on your own domains."
 msgstr ""
 
@@ -153,14 +153,6 @@ msgstr ""
 msgid "Simple, elegant and secure web client"
 msgstr ""
 
-#: ../../../docs/container-images.md
-msgid "[Sable](configuring-playbook-client-sable.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[7w1/sable](https://ghcr.io/7w1/sable)"
-msgstr ""
-
 #: ../../../docs/container-images.md
 msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md)"
 msgstr ""
@@ -173,11 +165,11 @@ msgstr ""
 msgid "Based on Element Web, with a more traditional instant messaging experience"
 msgstr ""
 
-#: ../../../docs/container-images.md:45
+#: ../../../docs/container-images.md:27
 msgid "Server Components"
 msgstr ""
 
-#: ../../../docs/container-images.md:47
+#: ../../../docs/container-images.md:29
 msgid "Services that run on the server to make the various parts of your installation work."
 msgstr ""
 
@@ -214,7 +206,7 @@ msgid "[Traefik](https://hub.docker.com/_/traefik/)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Web server, listening on ports 80, 443 and 8448 — standing in front of all the other services. [Using your own webserver](configuring-playbook-own-webserver.md) is also possible."
+msgid "Web server, listening on ports 80, 443 and 8448 — standing in front of all the other services. Using your own webserver [is possible](configuring-playbook-own-webserver.md)"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -226,7 +218,7 @@ msgid "[certbot/certbot](https://hub.docker.com/r/certbot/certbot/)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[Certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/)"
+msgid "The [certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/)"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -241,6 +233,18 @@ msgstr ""
 msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)"
 msgstr ""
 
+#: ../../../docs/container-images.md
+msgid "[ma1sd](configuring-playbook-ma1sd.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Matrix Identity Server"
+msgstr ""
+
 #: ../../../docs/container-images.md
 msgid "[ddclient](configuring-playbook-dynamic-dns.md)"
 msgstr ""
@@ -253,35 +257,11 @@ msgstr ""
 msgid "Update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider"
 msgstr ""
 
-#: ../../../docs/container-images.md
+#: ../../../docs/container-images.md:41
-msgid "[LiveKit Server](configuring-playbook-livekit-server.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[livekit/livekit-server](https://hub.docker.com/r/livekit/livekit-server/)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "WebRTC server for audio/video calls"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[Livekit JWT Service](configuring-playbook-livekit-jwt-service.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[element-hq/lk-jwt-service](https://ghcr.io/element-hq/lk-jwt-service)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "JWT service for integrating [Element Call](./configuring-playbook-element-call.md) with [LiveKit Server](./configuring-playbook-livekit-server.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md:60
 msgid "Authentication"
 msgstr ""
 
-#: ../../../docs/container-images.md:62
+#: ../../../docs/container-images.md:43
 msgid "Extend and modify how users are authenticated on your homeserver."
 msgstr ""
 
@@ -322,7 +302,7 @@ msgid "[activism.international/matrix_ldap_registration_proxy](https://gitlab.co
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Proxy that handles Matrix registration requests and forwards them to LDAP"
+msgid "A proxy that handles Matrix registration requests and forwards them to LDAP."
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -334,11 +314,11 @@ msgid "[zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-ma
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Simple python application to have a token based Matrix registration"
+msgid "A simple python application to have a token based Matrix registration"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[Matrix User Verification Service](configuring-playbook-user-verification-service.md)"
+msgid "[Matrix User Verification Service](configuring-playbook-user-verification-service.md) (UVS)"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -354,14 +334,14 @@ msgid "[synapse-simple-antispam](configuring-playbook-synapse-simple-antispam.md
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Spam checker module"
+msgid "A spam checker module"
 msgstr ""
 
-#: ../../../docs/container-images.md:74
+#: ../../../docs/container-images.md:55
 msgid "File Storage"
 msgstr ""
 
-#: ../../../docs/container-images.md:76
+#: ../../../docs/container-images.md:57
 msgid "Use alternative file storage to the default `media_store` folder."
 msgstr ""
 
@@ -390,29 +370,17 @@ msgid "[t2bot/matrix-media-repo](https://ghcr.io/t2bot/matrix-media-repo)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
+msgid "matrix-media-repo is a highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
 msgstr ""
 
-#: ../../../docs/container-images.md:84
+#: ../../../docs/container-images.md:65
 msgid "Bridges"
 msgstr ""
 
-#: ../../../docs/container-images.md:86
+#: ../../../docs/container-images.md:67
 msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
 msgstr ""
 
-#: ../../../docs/container-images.md
-msgid "[mautrix-bluesky](configuring-playbook-bridge-mautrix-bluesky.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[mautrix/bluesky](https://mau.dev/mautrix/bluesky/container_registry)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Bridge to [Bluesky](https://bsky.social/about)"
-msgstr ""
-
 #: ../../../docs/container-images.md
 msgid "[mautrix-discord](configuring-playbook-bridge-mautrix-discord.md)"
 msgstr ""
@@ -581,6 +549,14 @@ msgstr ""
 msgid "Bridge to [Discord](https://discordapp.com/)"
 msgstr ""
 
+#: ../../../docs/container-images.md
+msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)"
+msgstr ""
+
 #: ../../../docs/container-images.md
 msgid "[matrix-hookshot](configuring-playbook-bridge-hookshot.md)"
 msgstr ""
@@ -629,6 +605,62 @@ msgstr ""
 msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
 msgstr ""
 
+#: ../../../docs/container-images.md
+msgid "[go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-bridge)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Skype](https://www.skype.com)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Slack](https://slack.com)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry)"
+msgstr ""
+
 #: ../../../docs/container-images.md
 msgid "[mx-puppet-groupme](configuring-playbook-bridge-mx-puppet-groupme.md)"
 msgstr ""
@@ -641,18 +673,6 @@ msgstr ""
 msgid "Bridge to [GroupMe](https://groupme.com/)"
 msgstr ""
 
-#: ../../../docs/container-images.md
-msgid "[matrix-steam-bridge](configuring-playbook-bridge-steam.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[jasonlaguidice/matrix-steam-bridge](https://github.com/jasonlaguidice/matrix-steam-bridge/pkgs/container/matrix-steam-bridge)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Bridge to [Steam](https://steampowered.com/)"
-msgstr ""
-
 #: ../../../docs/container-images.md
 msgid "[mx-puppet-steam](configuring-playbook-bridge-mx-puppet-steam.md)"
 msgstr ""
@@ -677,11 +697,11 @@ msgstr ""
 msgid "Email to Matrix bridge"
 msgstr ""
 
-#: ../../../docs/container-images.md:114
+#: ../../../docs/container-images.md:99
 msgid "Bots"
 msgstr ""
 
-#: ../../../docs/container-images.md:116
+#: ../../../docs/container-images.md:101
 msgid "Bots provide various additional functionality to your installation."
 msgstr ""
 
@@ -694,7 +714,7 @@ msgid "[etke.cc/baibot](https://ghcr.io/etkecc/baibot)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
+msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -730,7 +750,7 @@ msgid "[dock.mau.dev/maubot/maubot](https://mau.dev/maubot/maubot/container_regi
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Plugin-based Matrix bot system"
+msgid "A plugin-based Matrix bot system"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -742,7 +762,7 @@ msgid "[etke.cc/honoroit](https://github.com/etkecc/honoroit/container_registry)
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Helpdesk bot"
+msgid "A helpdesk bot"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -754,7 +774,7 @@ msgid "[matrixdotorg/mjolnir](https://hub.docker.com/r/matrixdotorg/mjolnir)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Moderation tool for Matrix"
+msgid "A moderation tool for Matrix"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -766,7 +786,7 @@ msgid "[gnuxie/draupnir](https://hub.docker.com/r/gnuxie/draupnir)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Moderation tool for Matrix (Fork of Mjolnir)"
+msgid "A moderation tool for Matrix (Fork of Mjolnir)"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -781,11 +801,11 @@ msgstr ""
 msgid "Web forms (HTTP POST) to Matrix"
 msgstr ""
 
-#: ../../../docs/container-images.md:129
+#: ../../../docs/container-images.md:114
 msgid "Administration"
 msgstr ""
 
-#: ../../../docs/container-images.md:131
+#: ../../../docs/container-images.md:116
 msgid "Services that help you in administrating and monitoring your Matrix installation."
 msgstr ""
 
@@ -814,15 +834,15 @@ msgid "OAuth 2.0 and OpenID Provider server"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[ketesa](configuring-playbook-ketesa.md)"
+msgid "[synapse-admin](configuring-playbook-synapse-admin.md)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[etkecc/ketesa](https://ghcr.io/etkecc/ketesa)"
+msgid "[etke.cc/synapse-admin](https://ghcr.io/etkecc/synapse-admin)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Fully-featured web UI for administrating your Matrix homeserver — users, rooms, media, sessions, and more"
+msgid "A web UI tool for administrating users and rooms on your Matrix server"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -854,7 +874,7 @@ msgid "Graphing tool that works well with the above two images. Our playbook als
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[Metrics and Graphs](configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-nginx-logs-optional)"
+msgid "[Metrics and Graphs](configuring-playbook-prometheus-nginxlog.md)"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -873,18 +893,6 @@ msgstr ""
 msgid "Backups"
 msgstr ""
 
-#: ../../../docs/container-images.md
-msgid "[postgres-backup-local](configuring-playbook-postgres-backup.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[prodrigestivill/postgres-backup-local](https://hub.docker.com/r/prodrigestivill/postgres-backup-local)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Create automatic database backups"
-msgstr ""
-
 #: ../../../docs/container-images.md
 msgid "[rageshake](configuring-playbook-rageshake.md)"
 msgstr ""
@@ -905,24 +913,44 @@ msgstr ""
 msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus."
 msgstr ""
 
-#: ../../../docs/container-images.md:147
+#: ../../../docs/container-images.md:131
 msgid "Misc"
 msgstr ""
 
-#: ../../../docs/container-images.md:149
+#: ../../../docs/container-images.md:133
 msgid "Various services that don't fit any other categories."
 msgstr ""
 
+#: ../../../docs/container-images.md
+msgid "[sliding-sync](configuring-playbook-sliding-sync-proxy.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Sliding Sync support for clients which require it (like old Element X versions, before it got switched to Simplified Sliding Sync)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A Synapse module to automatically accept invites."
+msgstr ""
+
 #: ../../../docs/container-images.md
 msgid "[synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[mb-saces/rust-synapse-tools](https://gitlab.com/mb-saces/rust-synapse-tools/container_registry)"
+msgid "[etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-synapse-compress-state/container_registry)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Cli tool that automatically compresses Synapse's `state_groups` database table in background"
+msgid "A cli tool that automatically compresses `state_groups` database table in background."
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -946,7 +974,7 @@ msgid "[etherpad/etherpad](https://hub.docker.com/r/etherpad/etherpad/)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Open source collaborative text editor"
+msgid "An open source collaborative text editor"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -958,7 +986,7 @@ msgid "[jitsi/web](https://hub.docker.com/r/jitsi/web)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[Jitsi](https://jitsi.org/) web UI"
+msgid "the [Jitsi](https://jitsi.org/) web UI"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -966,7 +994,7 @@ msgid "[jitsi/jicofo](https://hub.docker.com/r/jitsi/jicofo)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[Jitsi](https://jitsi.org/) Focus component"
+msgid "the [Jitsi](https://jitsi.org/) Focus component"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -974,7 +1002,7 @@ msgid "[jitsi/prosody](https://hub.docker.com/r/jitsi/prosody)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[Jitsi](https://jitsi.org/) Prosody XMPP server component"
+msgid "the [Jitsi](https://jitsi.org/) Prosody XMPP server component"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -982,7 +1010,7 @@ msgid "[jitsi/jvb](https://hub.docker.com/r/jitsi/jvb)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[Jitsi](https://jitsi.org/) Video Bridge component"
+msgid "the [Jitsi](https://jitsi.org/) Video Bridge component"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -994,7 +1022,7 @@ msgid "[cactuscomments/cactus-appservice](https://hub.docker.com/r/cactuscomment
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Federated comment system built on Matrix"
+msgid "A federated comment system built on Matrix"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -1010,7 +1038,7 @@ msgid "[matrixdotorg/pantalaimon](https://hub.docker.com/r/matrixdotorg/pantalai
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "E2EE aware proxy daemon"
+msgid "An E2EE aware proxy daemon"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -1037,36 +1065,24 @@ msgstr ""
 msgid "Self-hosted, UnifiedPush-compatible push notifications server"
 msgstr ""
 
-#: ../../../docs/container-images.md
+#: ../../../docs/container-images.md:152
-msgid "[Element Call](configuring-playbook-element-call.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[element-hq/element-call](https://ghcr.io/element-hq/element-call)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "A native Matrix video conferencing application"
-msgstr ""
-
-#: ../../../docs/container-images.md:167
 msgid "Container images of deprecated / unmaintained services"
 msgstr ""
 
-#: ../../../docs/container-images.md:169
+#: ../../../docs/container-images.md:154
 msgid "The list of the deprecated or unmaintained services is available [here](configuring-playbook.md#deprecated--unmaintained--removed-services)."
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[conduwuit](configuring-playbook-conduwuit.md)"
+msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[girlbossceo/conduwuit](https://ghcr.io/girlbossceo/conduwuit)"
+msgid "[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit was a fork of Conduit."
+msgid "Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.)"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -1078,7 +1094,7 @@ msgid "[turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-di
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Open source integration manager for Matrix clients"
+msgid "An open source integration manager for Matrix clients"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -1102,39 +1118,7 @@ msgid "[matrixdotorg/go-neb](https://hub.docker.com/r/matrixdotorg/go-neb)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Multi functional bot written in Go"
+msgid "A multi functional bot written in Go"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[ma1sd](configuring-playbook-ma1sd.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Matrix Identity Server"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.)"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -1161,6 +1145,18 @@ msgstr ""
 msgid "Bridge to [Facebook](https://facebook.com/)"
 msgstr ""
 
+#: ../../../docs/container-images.md
+msgid "[mautrix-hangouts](configuring-playbook-bridge-mautrix-hangouts.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/hangouts](https://mau.dev/mautrix/hangouts/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Google Hangouts](https://en.wikipedia.org/wiki/Google_Hangouts)"
+msgstr ""
+
 #: ../../../docs/container-images.md
 msgid "[mautrix-instagram](configuring-playbook-bridge-mautrix-instagram.md)"
 msgstr ""
@@ -1172,67 +1168,3 @@ msgstr ""
 #: ../../../docs/container-images.md
 msgid "Bridge to [Instagram](https://instagram.com/)"
 msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Bridge to [Slack](https://slack.com)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[sliding-sync](configuring-playbook-sliding-sync-proxy.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Sliding Sync support for clients which require it (like old Element X versions, before it got switched to Simplified Sliding Sync)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Synapse module to automatically accept invites"
-msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/registering-users.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: bg\n"
@@ -19,225 +19,228 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/registering-users.md:11
+#: ../../../docs/registering-users.md:1
 msgid "Registering users"
 msgstr ""
 
-#: ../../../docs/registering-users.md:13
+#: ../../../docs/registering-users.md:3
 msgid "This documentation page tells you how to create user accounts on your Matrix server."
 msgstr ""
 
-#: ../../../docs/registering-users.md:15
+#: ../../../docs/registering-users.md:5
 msgid "Table of contents:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:16
+#: ../../../docs/registering-users.md:7
 msgid "[Registering users](#registering-users)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:17
+#: ../../../docs/registering-users.md:8
 msgid "[Registering users manually](#registering-users-manually)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:18
+#: ../../../docs/registering-users.md:9
 msgid "[Managing users via a Web UI](#managing-users-via-a-web-ui)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:19
+#: ../../../docs/registering-users.md:10
 msgid "[Letting certain users register on your private server](#letting-certain-users-register-on-your-private-server)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:20
+#: ../../../docs/registering-users.md:11
 msgid "[Enabling public user registration](#enabling-public-user-registration)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:21
+#: ../../../docs/registering-users.md:12
 msgid "[Adding/Removing Administrator privileges to an existing user](#addingremoving-administrator-privileges-to-an-existing-user)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:23
+#: ../../../docs/registering-users.md:14
 msgid "Registering users manually"
 msgstr ""
 
-#: ../../../docs/registering-users.md:25 ../../../docs/registering-users.md:127
+#: ../../../docs/registering-users.md:16 ../../../docs/registering-users.md:121
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:26
+#: ../../../docs/registering-users.md:17
 msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`"
 msgstr ""
 
-#: ../../../docs/registering-users.md:27
+#: ../../../docs/registering-users.md:18
 msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:28
+#: ../../../docs/registering-users.md:19
 msgid "Use `admin=yes` or `admin=no` depending on whether you wish to make the user an administrator of the Matrix server"
 msgstr ""
 
-#: ../../../docs/registering-users.md:30
+#: ../../../docs/registering-users.md:21
 msgid "After registering a user (using one of the methods below), **you can log in with that user** via the [Element Web](configuring-playbook-client-element-web.md) service that this playbook has installed for you at a URL like this: `https://element.example.com/`."
 msgstr ""
 
-#: ../../../docs/registering-users.md:32
+#: ../../../docs/registering-users.md:23
 msgid "Registering users via the Ansible playbook"
 msgstr ""
 
-#: ../../../docs/registering-users.md:34
+#: ../../../docs/registering-users.md:25
 msgid "It's best to register users via the Ansible playbook, because it works regardless of homeserver implementation (Synapse, Dendrite, etc) or usage of [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (MAS)."
 msgstr ""
 
-#: ../../../docs/registering-users.md:36
+#: ../../../docs/registering-users.md:27
 msgid "To register a user via this Ansible playbook:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:44
+#: ../../../docs/registering-users.md:35
 msgid "**or** by invoking `ansible-playbook` manually:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:52
+#: ../../../docs/registering-users.md:43
 msgid "Feel free to register as many users (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your user account only (with `admin=yes`), and others should be created with `admin=no`."
 msgstr ""
 
-#: ../../../docs/registering-users.md:54
+#: ../../../docs/registering-users.md:45
 msgid "[!WARNING] If you're registering users against Matrix Authentication Service, do note that it [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information."
 msgstr ""
 
-#: ../../../docs/registering-users.md:57
+#: ../../../docs/registering-users.md:48
 msgid "Registering users manually for Synapse"
 msgstr ""
 
-#: ../../../docs/registering-users.md:59
+#: ../../../docs/registering-users.md:50
 msgid "If you're using the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default), you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
 msgstr ""
 
-#: ../../../docs/registering-users.md:67
+#: ../../../docs/registering-users.md:58
 msgid "Registering users manually for Dendrite"
 msgstr ""
 
-#: ../../../docs/registering-users.md:69
+#: ../../../docs/registering-users.md:60
 msgid "If you're using the [Dendrite](./configuring-playbook-dendrite.md) homeserver implementation, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
 msgstr ""
 
-#: ../../../docs/registering-users.md:77
+#: ../../../docs/registering-users.md:68
 msgid "Registering users manually for Matrix Authentication Service"
 msgstr ""
 
-#: ../../../docs/registering-users.md:79
+#: ../../../docs/registering-users.md:70
 msgid "If you're using the [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) and your existing homeserver (most likely [Synapse](./configuring-playbook-synapse.md)) is delegating authentication to it, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
 msgstr ""
 
-#: ../../../docs/registering-users.md:87
+#: ../../../docs/registering-users.md:78
 msgid "This `register-user` script actually invokes the `mas-cli manage register-user` command under the hood. If you'd like more control over the registration process, consider invoking the `mas-cli` command directly:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:93
+#: ../../../docs/registering-users.md:84
 msgid "[!WARNING] Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information."
 msgstr ""
 
-#: ../../../docs/registering-users.md:96
+#: ../../../docs/registering-users.md:87
 msgid "Managing users via a Web UI"
 msgstr ""
 
-#: ../../../docs/registering-users.md:98
+#: ../../../docs/registering-users.md:89
-msgid "To manage users and your homeserver more easily (via a web interface), you can install [Ketesa](configuring-playbook-ketesa.md) — a fully-featured admin UI covering users, rooms, media, sessions, and MAS management."
+msgid "To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md)."
 msgstr ""
 
-#: ../../../docs/registering-users.md:100
+#: ../../../docs/registering-users.md:91
+msgid "[!WARNING] If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information."
+msgstr ""
+
+#: ../../../docs/registering-users.md:94
 msgid "Letting certain users register on your private server"
 msgstr ""
 
-#: ../../../docs/registering-users.md:102
+#: ../../../docs/registering-users.md:96
 msgid "If you'd rather **keep your server private** (public registration closed, as is the default), and **let certain people create accounts by themselves** (instead of creating user accounts manually like this), consider installing and making use of [matrix-registration](configuring-playbook-matrix-registration.md)."
 msgstr ""
 
-#: ../../../docs/registering-users.md:104
+#: ../../../docs/registering-users.md:98
 msgid "Enabling public user registration"
 msgstr ""
 
-#: ../../../docs/registering-users.md:106
+#: ../../../docs/registering-users.md:100
 msgid "To **open up user registration publicly** (usually **not recommended**), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:108
+#: ../../../docs/registering-users.md:102
 msgid "For Synapse:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:114
+#: ../../../docs/registering-users.md:108
 msgid "For Dendrite:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:120
+#: ../../../docs/registering-users.md:114
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:129
+#: ../../../docs/registering-users.md:123
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/registering-users.md:131
+#: ../../../docs/registering-users.md:125
 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. Note these shortcuts run the `ensure-matrix-users-created` tag too."
 msgstr ""
 
-#: ../../../docs/registering-users.md:133
+#: ../../../docs/registering-users.md:127
 msgid "If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md)."
 msgstr ""
 
-#: ../../../docs/registering-users.md:135
+#: ../../../docs/registering-users.md:129
 msgid "Adding/Removing Administrator privileges to an existing user"
 msgstr ""
 
-#: ../../../docs/registering-users.md:137
+#: ../../../docs/registering-users.md:131
 msgid "Adding/Removing Administrator privileges to an existing user in Synapse"
 msgstr ""
 
-#: ../../../docs/registering-users.md:139
+#: ../../../docs/registering-users.md:133
 msgid "To change the admin privileges for a user in Synapse's local database, you need to run an SQL query like this against the `synapse` database:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:145
+#: ../../../docs/registering-users.md:139
 msgid "where:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:147
+#: ../../../docs/registering-users.md:141
 msgid "`ADMIN_VALUE` being either `0` (regular user) or `1` (admin)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:148
+#: ../../../docs/registering-users.md:142
 msgid "`USER` and `example.com` pointing to a valid user on your server"
 msgstr ""
 
-#: ../../../docs/registering-users.md:150
+#: ../../../docs/registering-users.md:144
 msgid "If you're using the integrated Postgres server and not an [external Postgres server](configuring-playbook-external-postgres.md), you can launch a Postgres into the `synapse` database by:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:152
+#: ../../../docs/registering-users.md:146
 msgid "running `/matrix/postgres/bin/cli` — to launch [`psql`](https://www.postgresql.org/docs/current/app-psql.html)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:153
+#: ../../../docs/registering-users.md:147
 msgid "running `\\c synapse` — to change to the `synapse` database"
 msgstr ""
 
-#: ../../../docs/registering-users.md:155
+#: ../../../docs/registering-users.md:149
 msgid "You can then proceed to run the query above."
 msgstr ""
 
-#: ../../../docs/registering-users.md:157
+#: ../../../docs/registering-users.md:151
 msgid "**Note**: directly modifying the raw data of Synapse (or any other software) could cause the software to break. You've been warned!"
 msgstr ""
 
-#: ../../../docs/registering-users.md:159
+#: ../../../docs/registering-users.md:153
 msgid "Adding/Removing Administrator privileges to an existing user in Matrix Authentication Service"
 msgstr ""
 
-#: ../../../docs/registering-users.md:161
+#: ../../../docs/registering-users.md:155
-msgid "Promoting/demoting a user in Matrix Authentication Service can be done using the [`mas-cli`](./configuring-playbook-matrix-authentication-service.md#management) management tool's [`manage promote-admin`](https://element-hq.github.io/matrix-authentication-service/reference/cli/manage.html#manage-promote-admin) and [`manage demote-admin`](https://element-hq.github.io/matrix-authentication-service/reference/cli/manage.html#manage-demote-admin) commands. For example: `/matrix/matrix-authentication-service/bin/mas-cli manage promote-admin some.username`."
+msgid "Promoting/demoting a user in Matrix Authentication Service cannot currently (2024-10-19) be done via the [`mas-cli` Management tool](./configuring-playbook-matrix-authentication-service.md#management)."
 msgstr ""
 
-#: ../../../docs/registering-users.md:163
+#: ../../../docs/registering-users.md:157
-#, python-brace-format
+msgid "You can do it via the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html)'s `POST /api/admin/v1/users/{id}/set-admin` endpoint."
-msgid "You can also do it via the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html)'s `POST /api/admin/v1/users/{id}/set-admin` endpoint."
 msgstr ""

i18n/locales/bg/LC_MESSAGES/docs/self-building.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 12:09+0100\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"
@@ -19,136 +19,160 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/self-building.md:15
+#: ../../../docs/self-building.md:1
 msgid "Self-building"
 msgstr ""
 
-#: ../../../docs/self-building.md:17
+#: ../../../docs/self-building.md:3
 msgid "**Caution: self-building does not have to be used on its own. See the [Alternative Architectures](alternative-architectures.md) page.**"
 msgstr ""
 
-#: ../../../docs/self-building.md:19
+#: ../../../docs/self-building.md:5
 msgid "The playbook supports self-building of various components, which don't have a container image for your architecture (see the [container images we use](container-images.md)). For `amd64`, self-building is not required."
 msgstr ""
 
-#: ../../../docs/self-building.md:21
+#: ../../../docs/self-building.md:7
 msgid "For other architectures (e.g. `arm32`, `arm64`), ready-made container images are used when available. If there's no ready-made image for a specific component and said component supports self-building, an image will be built on the host. Building images like this takes more time and resources (some build tools need to get installed by the playbook to assist building)."
 msgstr ""
 
-#: ../../../docs/self-building.md:23
+#: ../../../docs/self-building.md:9
 msgid "To make use of self-building, you don't need to do anything. If a component has an image for the specified architecture, the playbook will use it directly. If not, it will build the image on the server itself."
 msgstr ""
 
-#: ../../../docs/self-building.md:25
+#: ../../../docs/self-building.md:11
 msgid "Note that **not all components support self-building yet**."
 msgstr ""
 
-#: ../../../docs/self-building.md:27
+#: ../../../docs/self-building.md:13
 msgid "Possibly outdated list of roles where self-building the Docker image is currently possible:"
 msgstr ""
 
-#: ../../../docs/self-building.md:28
+#: ../../../docs/self-building.md:14
 msgid "`matrix-synapse`"
 msgstr ""
 
-#: ../../../docs/self-building.md:29
+#: ../../../docs/self-building.md:15
-msgid "`matrix-ketesa`"
+msgid "`matrix-synapse-admin`"
 msgstr ""
 
-#: ../../../docs/self-building.md:30
+#: ../../../docs/self-building.md:16
 msgid "`matrix-client-element`"
 msgstr ""
 
-#: ../../../docs/self-building.md:31
+#: ../../../docs/self-building.md:17
-msgid "`hydrogen`"
+msgid "`matrix-client-hydrogen`"
 msgstr ""
 
-#: ../../../docs/self-building.md:32
+#: ../../../docs/self-building.md:18
-msgid "`cinny`"
+msgid "`matrix-client-cinny`"
 msgstr ""
 
-#: ../../../docs/self-building.md:33
+#: ../../../docs/self-building.md:19
-msgid "`sable`"
-msgstr ""
-
-#: ../../../docs/self-building.md:34
 msgid "`matrix-registration`"
 msgstr ""
 
-#: ../../../docs/self-building.md:35
+#: ../../../docs/self-building.md:20
-msgid "`coturn`"
+msgid "`matrix-coturn`"
 msgstr ""
 
-#: ../../../docs/self-building.md:36
+#: ../../../docs/self-building.md:21
 msgid "`matrix-corporal`"
 msgstr ""
 
-#: ../../../docs/self-building.md:37
+#: ../../../docs/self-building.md:22
+msgid "`matrix-dimension`"
+msgstr ""
+
+#: ../../../docs/self-building.md:23
+msgid "`matrix-ma1sd`"
+msgstr ""
+
+#: ../../../docs/self-building.md:24
 msgid "`exim-relay`"
 msgstr ""
 
-#: ../../../docs/self-building.md:38
+#: ../../../docs/self-building.md:25
 msgid "`matrix-bridge-hookshot`"
 msgstr ""
 
-#: ../../../docs/self-building.md:39
+#: ../../../docs/self-building.md:26
 msgid "`matrix-bridge-appservice-irc`"
 msgstr ""
 
-#: ../../../docs/self-building.md:40
+#: ../../../docs/self-building.md:27
+msgid "`matrix-bridge-appservice-slack`"
+msgstr ""
+
+#: ../../../docs/self-building.md:28
+msgid "`matrix-bridge-appservice-webhooks`"
+msgstr ""
+
+#: ../../../docs/self-building.md:29
 msgid "`matrix-bridge-beeper-linkedin`"
 msgstr ""
 
-#: ../../../docs/self-building.md:41
+#: ../../../docs/self-building.md:30
+msgid "`matrix-bridge-mautrix-facebook`"
+msgstr ""
+
+#: ../../../docs/self-building.md:31
+msgid "`matrix-bridge-mautrix-hangouts`"
+msgstr ""
+
+#: ../../../docs/self-building.md:32
 msgid "`matrix-bridge-mautrix-googlechat`"
 msgstr ""
 
-#: ../../../docs/self-building.md:42
+#: ../../../docs/self-building.md:33
 msgid "`matrix-bridge-mautrix-telegram`"
 msgstr ""
 
-#: ../../../docs/self-building.md:43
+#: ../../../docs/self-building.md:34
 msgid "`matrix-bridge-mautrix-signal`"
 msgstr ""
 
-#: ../../../docs/self-building.md:44
+#: ../../../docs/self-building.md:35
 msgid "`matrix-bridge-mautrix-gmessages`"
 msgstr ""
 
-#: ../../../docs/self-building.md:45
+#: ../../../docs/self-building.md:36
 msgid "`matrix-bridge-mautrix-whatsapp`"
 msgstr ""
 
-#: ../../../docs/self-building.md:46
+#: ../../../docs/self-building.md:37
 msgid "`matrix-bridge-mx-puppet-steam`"
 msgstr ""
 
-#: ../../../docs/self-building.md:47
+#: ../../../docs/self-building.md:38
 msgid "`matrix-bot-mjolnir`"
 msgstr ""
 
-#: ../../../docs/self-building.md:48
+#: ../../../docs/self-building.md:39
 msgid "`matrix-bot-honoroit`"
 msgstr ""
 
-#: ../../../docs/self-building.md:49
+#: ../../../docs/self-building.md:40
 msgid "`matrix-bot-matrix-reminder-bot`"
 msgstr ""
 
-#: ../../../docs/self-building.md:50
+#: ../../../docs/self-building.md:41
 msgid "`matrix-bot-maubot`"
 msgstr ""
 
-#: ../../../docs/self-building.md:51
+#: ../../../docs/self-building.md:42
+msgid "`matrix-email2matrix`"
+msgstr ""
+
+#: ../../../docs/self-building.md:43
 msgid "`matrix-pantalaimon`"
 msgstr ""
 
-#: ../../../docs/self-building.md:53
+#: ../../../docs/self-building.md:45
 msgid "Adding self-building support to other roles is welcome. Feel free to contribute!"
 msgstr ""
 
-#: ../../../docs/self-building.md:55
+#: ../../../docs/self-building.md:47
 msgid "If you'd like **to force self-building** even if an image is available for your architecture, look into the `matrix_*_self_build` variables provided by individual roles."
 msgstr ""

i18n/locales/jp/LC_MESSAGES/README.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:59+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,10 +18,10 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
 #: ../../../README.md:1
-msgid "[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com&fetchMode=summary)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate) [![REUSE status](https://api.reuse.software/badge/github.com/spantaleev/matrix-docker-ansible-deploy)](https://api.reuse.software/info/github.com/spantaleev/matrix-docker-ansible-deploy)"
+msgid "[![Support room on Matrix](https://img.shields.io/matrix/matrix-docker-ansible-deploy:devture.com.svg?label=%23matrix-docker-ansible-deploy%3Adevture.com&logo=matrix&style=for-the-badge&server_fqdn=matrix.devture.com)](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) [![donate](https://liberapay.com/assets/widgets/donate.svg)](https://liberapay.com/s.pantaleev/donate)"
 msgstr ""
 
 #: ../../../README.md:1
@@ -32,10 +32,6 @@ msgstr ""
 msgid "donate"
 msgstr ""
 
-#: ../../../README.md:1
-msgid "REUSE status"
-msgstr ""
-
 #: ../../../README.md:3
 msgid "Matrix (An open network for secure, decentralized communication) server setup using Ansible and Docker"
 msgstr ""
@@ -181,15 +177,15 @@ msgid "[Link](docs/configuring-playbook-conduit.md)"
 msgstr ""
 
 #: ../../../README.md
-msgid "[continuwuity](https://continuwuity.org)"
+msgid "[conduwuit](https://conduwuit.puppyirl.gay/)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network."
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit is a fork of Conduit."
 msgstr ""
 
 #: ../../../README.md
-msgid "[Link](docs/configuring-playbook-continuwuity.md)"
+msgid "[Link](docs/configuring-playbook-conduwuit.md)"
 msgstr ""
 
 #: ../../../README.md
@@ -248,14 +244,6 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-client-cinny.md)"
 msgstr ""
 
-#: ../../../README.md
-msgid "[Sable](https://github.com/7w1/sable)"
-msgstr ""
-
-#: ../../../README.md
-msgid "[Link](docs/configuring-playbook-client-sable.md)"
-msgstr ""
-
 #: ../../../README.md
 msgid "[SchildiChat Web](https://schildi.chat/)"
 msgstr ""
@@ -268,23 +256,11 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-client-schildichat-web.md)"
 msgstr ""
 
-#: ../../../README.md
+#: ../../../README.md:69
-msgid "[FluffyChat Web](https://fluffychat.im/)"
-msgstr ""
-
-#: ../../../README.md
-msgid "The cutest messenger in Matrix"
-msgstr ""
-
-#: ../../../README.md
-msgid "[Link](docs/configuring-playbook-client-fluffychat-web.md)"
-msgstr ""
-
-#: ../../../README.md:71
 msgid "Server Components"
 msgstr ""
 
-#: ../../../README.md:73
+#: ../../../README.md:71
 msgid "Services that run on the server to make the various parts of your installation work."
 msgstr ""
 
@@ -300,12 +276,24 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-external-postgres.md)"
 msgstr ""
 
+#: ../../../README.md
+msgid "[coturn](https://github.com/coturn/coturn)"
+msgstr ""
+
+#: ../../../README.md
+msgid "STUN/TURN server for WebRTC audio/video calls"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-turn.md)"
+msgstr ""
+
 #: ../../../README.md
 msgid "[Traefik](https://doc.traefik.io/traefik/)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. [Using your own webserver](docs/configuring-playbook-own-webserver.md) is also possible."
+msgid "Web server, listening on ports 80, 443 and 8448 - standing in front of all the other services. Using your own webserver [is possible](docs/configuring-playbook-own-webserver.md)"
 msgstr ""
 
 #: ../../../README.md
@@ -337,15 +325,15 @@ msgid "[Link](docs/configuring-playbook-email.md)"
 msgstr ""
 
 #: ../../../README.md
-msgid "[coturn](https://github.com/coturn/coturn)"
+msgid "[ma1sd](https://github.com/ma1uta/ma1sd)"
 msgstr ""
 
 #: ../../../README.md
-msgid "STUN/TURN server for WebRTC audio/video calls"
+msgid "Matrix Identity Server"
 msgstr ""
 
 #: ../../../README.md
-msgid "[Link](docs/configuring-playbook-turn.md)"
+msgid "[Link](docs/configuring-playbook-ma1sd.md)"
 msgstr ""
 
 #: ../../../README.md
@@ -360,23 +348,11 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-dynamic-dns.md)"
 msgstr ""
 
-#: ../../../README.md
+#: ../../../README.md:83
-msgid "Matrix RTC stack"
-msgstr ""
-
-#: ../../../README.md
-msgid "Supporting components ([LiveKit Server](docs/configuring-playbook-livekit-server.md) and [LiveKit JWT Service](docs/configuring-playbook-livekit-jwt-service.md)) for in-app audio/video calls for Matrix clients"
-msgstr ""
-
-#: ../../../README.md
-msgid "[Link](docs/configuring-playbook-matrix-rtc.md)"
-msgstr ""
-
-#: ../../../README.md:85
 msgid "Authentication"
 msgstr ""
 
-#: ../../../README.md:87
+#: ../../../README.md:85
 msgid "Extend and modify how users are authenticated on your homeserver."
 msgstr ""
 
@@ -421,7 +397,7 @@ msgid "[matrix-ldap-registration-proxy](https://gitlab.com/activism.internationa
 msgstr ""
 
 #: ../../../README.md
-msgid "Proxy that handles Matrix registration requests and forwards them to LDAP"
+msgid "A proxy that handles Matrix registration requests and forwards them to LDAP."
 msgstr ""
 
 #: ../../../README.md
@@ -433,7 +409,7 @@ msgid "[matrix-registration](https://github.com/ZerataX/matrix-registration)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Simple python application to have a token based Matrix registration"
+msgid "A simple python application to have a token based Matrix registration"
 msgstr ""
 
 #: ../../../README.md
@@ -441,7 +417,7 @@ msgid "[Link](docs/configuring-playbook-matrix-registration.md)"
 msgstr ""
 
 #: ../../../README.md
-msgid "[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service)"
+msgid "[Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (UVS)"
 msgstr ""
 
 #: ../../../README.md
@@ -457,18 +433,18 @@ msgid "[synapse-simple-antispam](https://github.com/t2bot/synapse-simple-antispa
 msgstr ""
 
 #: ../../../README.md
-msgid "Spam checker module"
+msgid "A spam checker module"
 msgstr ""
 
 #: ../../../README.md
 msgid "[Link](docs/configuring-playbook-synapse-simple-antispam.md)"
 msgstr ""
 
-#: ../../../README.md:99
+#: ../../../README.md:97
 msgid "File Storage"
 msgstr ""
 
-#: ../../../README.md:101
+#: ../../../README.md:99
 msgid "Use alternative file storage to the default `media_store` folder."
 msgstr ""
 
@@ -497,18 +473,18 @@ msgid "[matrix-media-repo](https://github.com/turt2live/matrix-media-repo)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
+msgid "matrix-media-repo is a highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
 msgstr ""
 
 #: ../../../README.md
 msgid "[Link](docs/configuring-playbook-matrix-media-repo.md)"
 msgstr ""
 
-#: ../../../README.md:109
+#: ../../../README.md:107
 msgid "Bridges"
 msgstr ""
 
-#: ../../../README.md:111
+#: ../../../README.md:109
 msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
 msgstr ""
 
@@ -584,18 +560,6 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bridge-mautrix-wsproxy.md)"
 msgstr ""
 
-#: ../../../README.md
-msgid "[mautrix-bluesky](https://github.com/mautrix/bluesky)"
-msgstr ""
-
-#: ../../../README.md
-msgid "Bridge to [Bluesky](https://bsky.social/)"
-msgstr ""
-
-#: ../../../README.md
-msgid "[Link](docs/configuring-playbook-bridge-mautrix-bluesky.md)"
-msgstr ""
-
 #: ../../../README.md
 msgid "[mautrix-twitter](https://github.com/mautrix/twitter)"
 msgstr ""
@@ -692,6 +656,14 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bridge-appservice-discord.md)"
 msgstr ""
 
+#: ../../../README.md
+msgid "[matrix-appservice-slack](https://github.com/matrix-org/matrix-appservice-slack)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-appservice-slack.md)"
+msgstr ""
+
 #: ../../../README.md
 msgid "[matrix-hookshot](https://github.com/matrix-org/matrix-hookshot)"
 msgstr ""
@@ -716,18 +688,6 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bridge-matrix-bridge-sms.md)"
 msgstr ""
 
-#: ../../../README.md
-msgid "[matrix-steam-bridge](https://github.com/jasonlaguidice/matrix-steam-bridge)"
-msgstr ""
-
-#: ../../../README.md
-msgid "Bridge to [Steam](https://steampowered.com/)"
-msgstr ""
-
-#: ../../../README.md
-msgid "[Link](docs/configuring-playbook-bridge-steam.md)"
-msgstr ""
-
 #: ../../../README.md
 msgid "[matrix-wechat](https://github.com/duo/matrix-wechat)"
 msgstr ""
@@ -752,6 +712,62 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bridge-heisenbridge.md)"
 msgstr ""
 
+#: ../../../README.md
+msgid "[go-skype-bridge](https://github.com/kelaresg/go-skype-bridge)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Skype](https://www.skype.com)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge to [Slack](https://slack.com)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-instagram](https://github.com/Sorunome/mx-puppet-instagram)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-twitter](https://github.com/Sorunome/mx-puppet-twitter)"
+msgstr ""
+
+#: ../../../README.md
+msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
 #: ../../../README.md
 msgid "[mx-puppet-groupme](https://gitlab.com/xangelix-pub/matrix/mx-puppet-groupme)"
 msgstr ""
@@ -765,7 +781,7 @@ msgid "[Link](docs/configuring-playbook-bridge-mx-puppet-groupme.md)"
 msgstr ""
 
 #: ../../../README.md
-msgid "[mx-puppet-steam](https://codeberg.org/icewind/mx-puppet-steam)"
+msgid "[mx-puppet-steam](https://github.com/icewind1991/mx-puppet-steam)"
 msgstr ""
 
 #: ../../../README.md
@@ -788,11 +804,11 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bridge-postmoogle.md)"
 msgstr ""
 
-#: ../../../README.md:139
+#: ../../../README.md:141
 msgid "Bots"
 msgstr ""
 
-#: ../../../README.md:141
+#: ../../../README.md:143
 msgid "Bots provide various additional functionality to your installation."
 msgstr ""
 
@@ -801,7 +817,7 @@ msgid "[baibot](https://github.com/etkecc/baibot)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
+msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
 msgstr ""
 
 #: ../../../README.md
@@ -837,7 +853,7 @@ msgid "[maubot](https://github.com/maubot/maubot)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Plugin-based Matrix bot system"
+msgid "A plugin-based Matrix bot system"
 msgstr ""
 
 #: ../../../README.md
@@ -849,7 +865,7 @@ msgid "[Honoroit](https://github.com/etkecc/honoroit)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Helpdesk bot"
+msgid "A helpdesk bot"
 msgstr ""
 
 #: ../../../README.md
@@ -861,7 +877,7 @@ msgid "[Mjolnir](https://github.com/matrix-org/mjolnir)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Moderation tool for Matrix"
+msgid "A moderation tool for Matrix"
 msgstr ""
 
 #: ../../../README.md
@@ -873,7 +889,7 @@ msgid "[Draupnir](https://github.com/the-draupnir-project/Draupnir)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Moderation tool for Matrix (Fork of Mjolnir)"
+msgid "A moderation tool for Matrix (Fork of Mjolnir)"
 msgstr ""
 
 #: ../../../README.md
@@ -892,11 +908,11 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-bot-buscarron.md)"
 msgstr ""
 
-#: ../../../README.md:154
+#: ../../../README.md:156
 msgid "Administration"
 msgstr ""
 
-#: ../../../README.md:156
+#: ../../../README.md:158
 msgid "Services that help you in administrating and monitoring your Matrix installation."
 msgstr ""
 
@@ -925,15 +941,15 @@ msgid "[Link](docs/configuring-playbook-matrix-authentication-service.md)"
 msgstr ""
 
 #: ../../../README.md
-msgid "[Ketesa](https://github.com/etkecc/ketesa)"
+msgid "[synapse-admin](https://github.com/etkecc/synapse-admin)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Fully-featured web UI for administrating your Matrix homeserver — users, rooms, media, sessions, and more"
+msgid "A web UI tool for administrating users and rooms on your Matrix server"
 msgstr ""
 
 #: ../../../README.md
-msgid "[Link](docs/configuring-playbook-ketesa.md)"
+msgid "[Link](docs/configuring-playbook-synapse-admin.md)"
 msgstr ""
 
 #: ../../../README.md
@@ -945,7 +961,7 @@ msgid "Consists of the [Prometheus](https://prometheus.io) time-series database
 msgstr ""
 
 #: ../../../README.md
-msgid "[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-nginx-logs-optional))"
+msgid "[Link](docs/configuring-playbook-prometheus-grafana.md) (for [prometheus-nginxlog-exporter](docs/configuring-playbook-prometheus-nginxlog.md))"
 msgstr ""
 
 #: ../../../README.md
@@ -984,20 +1000,44 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-synapse-usage-exporter.md)"
 msgstr ""
 
-#: ../../../README.md:168
+#: ../../../README.md:170
 msgid "Misc"
 msgstr ""
 
-#: ../../../README.md:170
+#: ../../../README.md:172
 msgid "Various services that don't fit any other categories."
 msgstr ""
 
+#: ../../../README.md
+msgid "[sliding-sync](https://github.com/matrix-org/sliding-sync)"
+msgstr ""
+
+#: ../../../README.md
+msgid "(Superseded by Simplified Sliding Sync integrated into Synapse > `1.114` and Conduit > `0.6.0`) Sliding Sync support for clients which require it (e.g. old Element X versions before Simplified Sliding Sync was developed)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-sliding-sync-proxy.md)"
+msgstr ""
+
+#: ../../../README.md
+msgid "[synapse_auto_accept_invite](https://github.com/matrix-org/synapse-auto-accept-invite)"
+msgstr ""
+
+#: ../../../README.md
+msgid "A Synapse module to automatically accept invites."
+msgstr ""
+
+#: ../../../README.md
+msgid "[Link](docs/configuring-playbook-synapse-auto-accept-invite.md)"
+msgstr ""
+
 #: ../../../README.md
 msgid "[synapse_auto_compressor](https://github.com/matrix-org/rust-synapse-compress-state/#automated-tool-synapse_auto_compressor)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Cli tool that automatically compresses `state_groups` database table in background"
+msgid "A cli tool that automatically compresses `state_groups` database table in background."
 msgstr ""
 
 #: ../../../README.md
@@ -1016,24 +1056,12 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-matrix-corporal.md)"
 msgstr ""
 
-#: ../../../README.md
-msgid "[Matrix.to](https://github.com/matrix-org/matrix.to)"
-msgstr ""
-
-#: ../../../README.md
-msgid "Simple URL redirection service for the Matrix ecosystem"
-msgstr ""
-
-#: ../../../README.md
-msgid "[Link](docs/configuring-playbook-matrixto.md)"
-msgstr ""
-
 #: ../../../README.md
 msgid "[Etherpad](https://etherpad.org)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Open source collaborative text editor"
+msgid "An open source collaborative text editor"
 msgstr ""
 
 #: ../../../README.md
@@ -1045,7 +1073,7 @@ msgid "[Jitsi](https://jitsi.org/)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Open source video-conferencing platform"
+msgid "An open source video-conferencing platform"
 msgstr ""
 
 #: ../../../README.md
@@ -1057,7 +1085,7 @@ msgid "[Cactus Comments](https://cactus.chat)"
 msgstr ""
 
 #: ../../../README.md
-msgid "Federated comment system built on Matrix"
+msgid "A federated comment system built on Matrix"
 msgstr ""
 
 #: ../../../README.md
@@ -1069,7 +1097,7 @@ msgid "[Pantalaimon](https://github.com/matrix-org/pantalaimon)"
 msgstr ""
 
 #: ../../../README.md
-msgid "E2EE aware proxy daemon"
+msgid "An E2EE aware proxy daemon"
 msgstr ""
 
 #: ../../../README.md
@@ -1100,66 +1128,54 @@ msgstr ""
 msgid "[Link](docs/configuring-playbook-ntfy.md)"
 msgstr ""
 
-#: ../../../README.md
+#: ../../../README.md:187
-msgid "[Element Call](https://github.com/element-hq/element-call)"
-msgstr ""
-
-#: ../../../README.md
-msgid "A native Matrix video conferencing application"
-msgstr ""
-
-#: ../../../README.md
-msgid "[Link](docs/configuring-playbook-element-call.md)"
-msgstr ""
-
-#: ../../../README.md:185
 msgid "🆕 Changes"
 msgstr ""
 
-#: ../../../README.md:187
+#: ../../../README.md:189
 msgid "This playbook evolves over time, sometimes with backward-incompatible changes."
 msgstr ""
 
-#: ../../../README.md:189
+#: ../../../README.md:191
 msgid "When updating the playbook, refer to [the changelog](CHANGELOG.md) to catch up with what's new."
 msgstr ""
 
-#: ../../../README.md:191
+#: ../../../README.md:193
 msgid "🆘 Support"
 msgstr ""
 
-#: ../../../README.md:193
+#: ../../../README.md:195
 msgid "Matrix room: [#matrix-docker-ansible-deploy:devture.com](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com)"
 msgstr ""
 
-#: ../../../README.md:195
+#: ../../../README.md:197
 msgid "IRC channel: `#matrix-docker-ansible-deploy` on the [Libera Chat](https://libera.chat/) IRC network (irc.libera.chat:6697)"
 msgstr ""
 
-#: ../../../README.md:197
+#: ../../../README.md:199
 msgid "GitHub issues: [spantaleev/matrix-docker-ansible-deploy/issues](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues)"
 msgstr ""
 
-#: ../../../README.md:199
+#: ../../../README.md:201
 msgid "🌐 Translation"
 msgstr ""
 
-#: ../../../README.md:201
+#: ../../../README.md:203
 msgid "See the [i18n/README.md](i18n/README.md) file for more information about translation."
 msgstr ""
 
-#: ../../../README.md:203
+#: ../../../README.md:205
 msgid "Translations are still work in progress."
 msgstr ""
 
-#: ../../../README.md:205
+#: ../../../README.md:207
 msgid "🤝 Related"
 msgstr ""
 
-#: ../../../README.md:207
+#: ../../../README.md:209
 msgid "You may also be interested in [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook) - another Ansible playbook for self-hosting non-Matrix services (see its [List of supported services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md))."
 msgstr ""
 
-#: ../../../README.md:209
+#: ../../../README.md:211
 msgid "mash-playbook also makes use of [Traefik](./docs/configuring-playbook-traefik.md) as its reverse-proxy, so with minor [interoperability adjustments](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md), you can make matrix-docker-ansible-deploy and mash-playbook co-exist and host Matrix and non-Matrix services on the same server."
 msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/README.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,156 +18,156 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/README.md:10
+#: ../../../docs/README.md:1
 msgid "Table of Contents"
 msgstr ""
 
-#: ../../../docs/README.md:12
+#: ../../../docs/README.md:3
-msgid "⬇️ Installation guides <!-- NOTE: the 🚀 emoji is used by \"Getting started\" on README.md -->"
+msgid "⬇️ Installaton guides <!-- NOTE: the 🚀 emoji is used by \"Getting started\" on README.md -->"
 msgstr ""
 
-#: ../../../docs/README.md:14
+#: ../../../docs/README.md:5
 msgid "There are two installation guides available for beginners and advanced users."
 msgstr ""
 
-#: ../../../docs/README.md:16
+#: ../../../docs/README.md:7
 msgid "⚡ **[Quick start](quick-start.md) (for beginners)**: this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"."
 msgstr ""
 
-#: ../../../docs/README.md:18
+#: ../../../docs/README.md:9
 msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide."
 msgstr ""
 
-#: ../../../docs/README.md:20
+#: ../../../docs/README.md:11
 msgid "[Prerequisites](prerequisites.md)"
 msgstr ""
 
-#: ../../../docs/README.md:22
+#: ../../../docs/README.md:13
-msgid "[Configuring DNS settings](configuring-dns.md)"
+msgid "[Configuring your DNS settings](configuring-dns.md)"
 msgstr ""
 
-#: ../../../docs/README.md:24
+#: ../../../docs/README.md:15
 msgid "[Getting the playbook](getting-the-playbook.md)"
 msgstr ""
 
-#: ../../../docs/README.md:26
+#: ../../../docs/README.md:17
 msgid "[Configuring the playbook](configuring-playbook.md)"
 msgstr ""
 
-#: ../../../docs/README.md:28
+#: ../../../docs/README.md:19
 msgid "[Installing](installing.md)"
 msgstr ""
 
-#: ../../../docs/README.md:30
+#: ../../../docs/README.md:21
 msgid "🛠️ Configuration options"
 msgstr ""
 
-#: ../../../docs/README.md:37
+#: ../../../docs/README.md:28
 msgid "You can check useful documentation for configuring components here: [Configuring the playbook](configuring-playbook.md)"
 msgstr ""
 
-#: ../../../docs/README.md:39
+#: ../../../docs/README.md:30
 msgid "[Administration](configuring-playbook.md#administration) — services that help you in administrating and monitoring your Matrix installation"
 msgstr ""
 
-#: ../../../docs/README.md:41
+#: ../../../docs/README.md:32
 msgid "[Authentication and user-related](configuring-playbook.md#authentication-and-user-related) — extend and modify how users are authenticated on your homeserver"
 msgstr ""
 
-#: ../../../docs/README.md:43
+#: ../../../docs/README.md:34
 msgid "[Bots](configuring-playbook.md#bots) — bots provide various additional functionality to your installation"
 msgstr ""
 
-#: ../../../docs/README.md:45
+#: ../../../docs/README.md:36
 msgid "[Bridges](configuring-playbook.md#bridging-other-networks) — bridges can be used to connect your Matrix installation with third-party communication networks"
 msgstr ""
 
-#: ../../../docs/README.md:47
+#: ../../../docs/README.md:38
 msgid "[Clients](configuring-playbook.md#clients) — web clients for Matrix that you can host on your own domains"
 msgstr ""
 
-#: ../../../docs/README.md:49
+#: ../../../docs/README.md:40
 msgid "[Core service adjustments](configuring-playbook.md#core-service-adjustments) — backbone of your Matrix system"
 msgstr ""
 
-#: ../../../docs/README.md:51
+#: ../../../docs/README.md:42
 msgid "[File Storage](configuring-playbook.md#file-storage) — use alternative file storage to the default `media_store` folder"
 msgstr ""
 
-#: ../../../docs/README.md:55
+#: ../../../docs/README.md:46
 msgid "[Other specialized services](configuring-playbook.md#other-specialized-services) — various services that don't fit any other categories"
 msgstr ""
 
-#: ../../../docs/README.md:57
+#: ../../../docs/README.md:48
 msgid "👨‍🔧 Maintenance"
 msgstr ""
 
-#: ../../../docs/README.md:59
+#: ../../../docs/README.md:50
 msgid "If your server and services experience issues, feel free to come to [our support room](https://matrix.to/#/#matrix-docker-ansible-deploy:devture.com) and ask for help."
 msgstr ""
 
-#: ../../../docs/README.md:63
+#: ../../../docs/README.md:54
+msgid "[Checking if services work](maintenance-checking-services.md)"
+msgstr ""
+
+#: ../../../docs/README.md:56
 msgid "[Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)"
 msgstr ""
 
-#: ../../../docs/README.md:65
+#: ../../../docs/README.md:58
 msgid "[PostgreSQL maintenance](maintenance-postgres.md)"
 msgstr ""
 
-#: ../../../docs/README.md:67
+#: ../../../docs/README.md:60
 msgid "[Synapse maintenance](maintenance-synapse.md)"
 msgstr ""
 
-#: ../../../docs/README.md:69
+#: ../../../docs/README.md:62
 msgid "[Upgrading services](maintenance-upgrading-services.md)"
 msgstr ""
 
-#: ../../../docs/README.md:71
+#: ../../../docs/README.md:64
 msgid "Other documentation pages <!-- NOTE: this header's title and the section below need optimization -->"
 msgstr ""
 
-#: ../../../docs/README.md:73
+#: ../../../docs/README.md:66
 msgid "ℹ️ **[FAQ](faq.md)** — various Frequently Asked Questions about Matrix, with a focus on this Ansible playbook"
 msgstr ""
 
-#: ../../../docs/README.md:77
+#: ../../../docs/README.md:70
 msgid "[Alternative architectures](alternative-architectures.md)"
 msgstr ""
 
-#: ../../../docs/README.md:79
+#: ../../../docs/README.md:72
 msgid "[Container images used by the playbook](container-images.md)"
 msgstr ""
 
-#: ../../../docs/README.md:81
+#: ../../../docs/README.md:74
 msgid "[Obtaining an Access Token](obtaining-access-tokens.md)"
 msgstr ""
 
-#: ../../../docs/README.md:83
+#: ../../../docs/README.md:76
 msgid "[Playbook tags](playbook-tags.md)"
 msgstr ""
 
-#: ../../../docs/README.md:85
+#: ../../../docs/README.md:78
 msgid "[Registering users](registering-users.md)"
 msgstr ""
 
-#: ../../../docs/README.md:87
+#: ../../../docs/README.md:80
 msgid "[Running `just` commands](just.md)"
 msgstr ""
 
-#: ../../../docs/README.md:89
+#: ../../../docs/README.md:82
 msgid "[Self-building](self-building.md)"
 msgstr ""
 
-#: ../../../docs/README.md:91
+#: ../../../docs/README.md:84
 msgid "[Uninstalling](uninstalling.md)"
 msgstr ""
 
-#: ../../../docs/README.md:93
+#: ../../../docs/README.md:86
 msgid "[Updating users passwords](updating-users-passwords.md)"
 msgstr ""
-
-#: ../../../docs/README.md:95
-msgid "[Using Ansible for the playbook](ansible.md)"
-msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-baibot.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,459 +18,431 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:8
+#: ../../../docs/configuring-playbook-bot-baibot.md:1
 msgid "Setting up baibot (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:15
+#: ../../../docs/configuring-playbook-bot-baibot.md:8
 msgid "🤖 [baibot](https://github.com/etkecc/baibot) (pronounced bye-bot) is a [Matrix](https://matrix.org/) bot developed by [etke.cc](https://etke.cc/) that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you. 🤖"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:17
+#: ../../../docs/configuring-playbook-bot-baibot.md:10
 msgid "It supports [OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) models, as many well as other [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:19
+#: ../../../docs/configuring-playbook-bot-baibot.md:12
 msgid "It's designed as a more private and [✨ featureful](https://github.com/etkecc/baibot/?tab=readme-ov-file#-features) alternative to [matrix-chatgpt-bot](./configuring-playbook-bot-chatgpt.md). See the [baibot](https://github.com/etkecc/baibot) project and its documentation for more information."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:21
+#: ../../../docs/configuring-playbook-bot-baibot.md:14
 msgid "Prerequisites"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:23
+#: ../../../docs/configuring-playbook-bot-baibot.md:16
 msgid "API access to one or more LLM [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:25
+#: ../../../docs/configuring-playbook-bot-baibot.md:18
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:27
+#: ../../../docs/configuring-playbook-bot-baibot.md:20
 msgid "There are **a lot of configuration options** (some required, some possibly required, some optional), so they're **split into multiple sections below**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:30
+#: ../../../docs/configuring-playbook-bot-baibot.md:23
 msgid "[Base configuration](#base-configuration)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:31
+#: ../../../docs/configuring-playbook-bot-baibot.md:24
 msgid "[👮‍♂️ Administrator configuration](#️-administrator-configuration)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:32
+#: ../../../docs/configuring-playbook-bot-baibot.md:25
 msgid "[👥 Initial users configuration](#-initial-users-configuration)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:33
+#: ../../../docs/configuring-playbook-bot-baibot.md:26
 msgid "[🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:34
+#: ../../../docs/configuring-playbook-bot-baibot.md:27
 msgid "[🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:36
+#: ../../../docs/configuring-playbook-bot-baibot.md:29
 msgid "Depending on your current `vars.yml` file and desired configuration, **you may require more than just the [base configuration](#base-configuration)**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:38
+#: ../../../docs/configuring-playbook-bot-baibot.md:31
 msgid "Base configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:40
+#: ../../../docs/configuring-playbook-bot-baibot.md:33
 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:42
+#: ../../../docs/configuring-playbook-bot-baibot.md:71
-msgid "Authentication can be configured in one of two mutually-exclusive ways:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-baibot.md:44
-msgid "**Password authentication** (`matrix_bot_baibot_config_user_password`) - recommended for most playbook-managed setups, because it integrates with automatic user creation flow used by the playbook, and auto-creates the bot account"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-baibot.md:45
-msgid "**Access-token authentication** (`matrix_bot_baibot_config_user_access_token` + `matrix_bot_baibot_config_user_device_id`) - useful for specific [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md)/OIDC setups where password authentication is not available or not desired"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-baibot.md:47
-msgid "Even when [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) is enabled, password authentication is still typically the best fit for baibot if you're using a playbook-managed bot account."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-baibot.md:49
-msgid "For upstream details, see baibot's [🔐 Authentication](https://github.com/etkecc/baibot/blob/main/docs/configuration/authentication.md) documentation."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-baibot.md:97
 msgid "As mentioned above, **this may not be enough**. Continue with the configuration sections below."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:99
+#: ../../../docs/configuring-playbook-bot-baibot.md:73
 msgid "👮‍♂️ Administrator configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:101
+#: ../../../docs/configuring-playbook-bot-baibot.md:75
-#: ../../../docs/configuring-playbook-bot-baibot.md:125
+#: ../../../docs/configuring-playbook-bot-baibot.md:99
 msgid "This is an addition to the [base configuration](#base-configuration)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:103
+#: ../../../docs/configuring-playbook-bot-baibot.md:77
 msgid "To specify who is considered a bot [👮‍♂️ Administrator](https://github.com/etkecc/baibot/blob/main/docs/access.md#administrators), you either need to specify `matrix_bot_baibot_config_access_admin_patterns` or `matrix_admin`. The latter is a single variable which affects all bridges and bots."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:105
+#: ../../../docs/configuring-playbook-bot-baibot.md:79
 msgid "If `matrix_admin` is already configured in your `vars.yml` configuration, you can skip this section."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:107
+#: ../../../docs/configuring-playbook-bot-baibot.md:81
-#: ../../../docs/configuring-playbook-bot-baibot.md:136
+#: ../../../docs/configuring-playbook-bot-baibot.md:110
 msgid "**If necessary**, add the following configuration to your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:121
+#: ../../../docs/configuring-playbook-bot-baibot.md:95
 msgid "👥 Initial users configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:123
+#: ../../../docs/configuring-playbook-bot-baibot.md:97
 msgid "By default, **all users on your homeserver are considered allowed users**. If that's OK, you can skip this section."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:127
+#: ../../../docs/configuring-playbook-bot-baibot.md:101
 msgid "To specify who is considered a bot [👥 User](https://github.com/etkecc/baibot/blob/main/docs/access.md#user), you may:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:129
+#: ../../../docs/configuring-playbook-bot-baibot.md:103
 msgid "define an **initial** value for `matrix_bot_baibot_config_initial_global_config_user_patterns` Ansible variable, as shown below"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:130
+#: ../../../docs/configuring-playbook-bot-baibot.md:104
 msgid "configure the list at runtime via the bot's `!bai access set-users SPACE_SEPARATED_PATTERNS` command"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:132
+#: ../../../docs/configuring-playbook-bot-baibot.md:106
 msgid "Configuring `matrix_bot_baibot_config_initial_global_config_user_patterns` is optional, but it can be useful to pre-configure the bot with a list of users who should have access to the bot's features."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:134
+#: ../../../docs/configuring-playbook-bot-baibot.md:108
 msgid "**Note**: Once initially configured, the allowed users list **cannot be managed via Ansible anymore**. It can only be managed subsequently via bot commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:148
+#: ../../../docs/configuring-playbook-bot-baibot.md:122
 msgid "🤖 Configuring agents via Ansible"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:150
+#: ../../../docs/configuring-playbook-bot-baibot.md:124
 msgid "You are **not required** to define agents [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration) via Ansible. **To get started quickly**, you can **skip this section and define agents at runtime via chat commands** (following the bot's guidance)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:152
+#: ../../../docs/configuring-playbook-bot-baibot.md:126
 msgid "Privileged users (like the [👮‍♂️ Administrator](#️-administrator-configuration), but potentially others too — see the upstream [🔒 access](https://github.com/etkecc/baibot/blob/main/docs/access.md) documentation) can **define agents dynamically at any time** via chat commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:154
+#: ../../../docs/configuring-playbook-bot-baibot.md:128
 msgid "The Ansible role includes preset variables for easily enabling some [🤖 agents](https://github.com/etkecc/baibot/blob/main/docs/agents.md) on various [☁️ providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md) (e.g. OpenAI, etc)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:156
+#: ../../../docs/configuring-playbook-bot-baibot.md:130
 msgid "Besides the presets, the Ansible role also includes support for configuring additional statically-defined agents via the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:158
+#: ../../../docs/configuring-playbook-bot-baibot.md:132
 msgid "Agents defined statically and those created dynamically (via chat) are named differently, so **conflict cannot arise**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:160
+#: ../../../docs/configuring-playbook-bot-baibot.md:134
 msgid "Depending on your propensity for [GitOps](https://en.wikipedia.org/wiki/DevOps#GitOps), you may prefer to define agents statically via Ansible, or you may wish to do it dynamically via chat."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:162
+#: ../../../docs/configuring-playbook-bot-baibot.md:136
 msgid "Before proceeding, we recommend reading the upstream documentation on [How to choose a provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#how-to-choose-a-provider). In short, it's probably best to go with [OpenAI](#openai)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:164
+#: ../../../docs/configuring-playbook-bot-baibot.md:138
 msgid "Anthropic"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:166
+#: ../../../docs/configuring-playbook-bot-baibot.md:140
 msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Anthropic provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#anthropic) with the help of the playbook's preset variables."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:168
+#: ../../../docs/configuring-playbook-bot-baibot.md:142
-#: ../../../docs/configuring-playbook-bot-baibot.md:192
+#: ../../../docs/configuring-playbook-bot-baibot.md:166
-#: ../../../docs/configuring-playbook-bot-baibot.md:223
+#: ../../../docs/configuring-playbook-bot-baibot.md:197
-#: ../../../docs/configuring-playbook-bot-baibot.md:251
+#: ../../../docs/configuring-playbook-bot-baibot.md:225
 msgid "Here's an example **addition** to your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:184
+#: ../../../docs/configuring-playbook-bot-baibot.md:158
+#: ../../../docs/configuring-playbook-bot-baibot.md:189
 #: ../../../docs/configuring-playbook-bot-baibot.md:215
-#: ../../../docs/configuring-playbook-bot-baibot.md:241
+#: ../../../docs/configuring-playbook-bot-baibot.md:243
-#: ../../../docs/configuring-playbook-bot-baibot.md:275
 msgid "If you'd like to use more than one model, take a look at the [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset) section below."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:186
+#: ../../../docs/configuring-playbook-bot-baibot.md:160
+#: ../../../docs/configuring-playbook-bot-baibot.md:191
 #: ../../../docs/configuring-playbook-bot-baibot.md:217
-#: ../../../docs/configuring-playbook-bot-baibot.md:243
+#: ../../../docs/configuring-playbook-bot-baibot.md:245
-#: ../../../docs/configuring-playbook-bot-baibot.md:277
 msgid "💡 You may also wish to use this new agent for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:188
+#: ../../../docs/configuring-playbook-bot-baibot.md:162
 msgid "Groq"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:190
+#: ../../../docs/configuring-playbook-bot-baibot.md:164
 msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [Groq provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#groq) with the help of the playbook's preset variables."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:213
+#: ../../../docs/configuring-playbook-bot-baibot.md:187
 msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/groq`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:219
+#: ../../../docs/configuring-playbook-bot-baibot.md:193
 msgid "Mistral"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:221
+#: ../../../docs/configuring-playbook-bot-baibot.md:195
 msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [🇫🇷 Mistral provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#mistral) with the help of the playbook's preset variables."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:239
+#: ../../../docs/configuring-playbook-bot-baibot.md:213
 msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/mistral`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:245
+#: ../../../docs/configuring-playbook-bot-baibot.md:219
 msgid "OpenAI"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:247
+#: ../../../docs/configuring-playbook-bot-baibot.md:221
 msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai) with the help of the playbook's preset variables."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:249
+#: ../../../docs/configuring-playbook-bot-baibot.md:223
 msgid "The OpenAI provider is **only meant to be used with OpenAI's official API** and compatibility with other services (which do not fully adhere to the OpenAI API spec completely) is limited. **If you're targeting an OpenAI-compatible service**, use the [OpenAI Compatible](#openai-compatible) provider instead."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:273
+#: ../../../docs/configuring-playbook-bot-baibot.md:241
 msgid "Because this is a [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agent, it will be given a `static/` ID prefix and will be named `static/openai`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:279
+#: ../../../docs/configuring-playbook-bot-baibot.md:247
 msgid "OpenAI Compatible"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:281
+#: ../../../docs/configuring-playbook-bot-baibot.md:249
 msgid "You can statically-define a single [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md) instance powered by the [OpenAI Compatible provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openai-compatible) with the help of the playbook's preset variables."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:283
+#: ../../../docs/configuring-playbook-bot-baibot.md:251
 msgid "This provider allows you to use OpenAI-compatible API services like [OpenRouter](https://github.com/etkecc/baibot/blob/main/docs/providers.md#openrouter), [Together AI](https://github.com/etkecc/baibot/blob/main/docs/providers.md#together-ai), etc."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:285
+#: ../../../docs/configuring-playbook-bot-baibot.md:253
 msgid "Some of these popular services already have **shortcut** providers (see [supported providers](https://github.com/etkecc/baibot/blob/main/docs/providers.md#supported-providers) leading to this one behind the scenes — this make it easier to get started."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:287
+#: ../../../docs/configuring-playbook-bot-baibot.md:255
 msgid "As of this moment, the playbook does not include presets for any of these services, so you'll need to [Configuring additional agents (without a preset)](#configuring-additional-agents-without-a-preset)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:289
+#: ../../../docs/configuring-playbook-bot-baibot.md:257
 msgid "Configuring additional agents (without a preset)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:291
+#: ../../../docs/configuring-playbook-bot-baibot.md:259
 msgid "The Ansible role may be lacking preset variables for some [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md), or you may wish to statically-define an agent on the same provider twice (or more) with different configuration."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:293
+#: ../../../docs/configuring-playbook-bot-baibot.md:261
 msgid "It's possible to inject your own agent configuration using the `matrix_bot_baibot_config_agents_static_definitions_custom` Ansible variable."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:295
+#: ../../../docs/configuring-playbook-bot-baibot.md:263
 msgid "You can also define providers at runtime, by chatting with the bot, so using Ansible is not a requirement."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:297
+#: ../../../docs/configuring-playbook-bot-baibot.md:265
 msgid "Below is an an **example** demonstrating **statically-defining agents via Ansible without using presets**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:336
+#: ../../../docs/configuring-playbook-bot-baibot.md:304
 msgid "Because these are [statically](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md#static-configuration)-defined agents, they will be given a `static/` ID prefix and will be named `static/my-openai-gpt-3.5-turbo-agent` and `static/my-ollama-agent`, respectively."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:338
+#: ../../../docs/configuring-playbook-bot-baibot.md:306
 msgid "💡 To figure out what to put in the `config` section, refer to the [☁️ provider](https://github.com/etkecc/baibot/blob/main/docs/providers.md) page, which contains **sample configuration YAML for each provider**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:340
+#: ../../../docs/configuring-playbook-bot-baibot.md:308
 msgid "As with any [🤖 agent](https://github.com/etkecc/baibot/blob/main/docs/agents.md), defining them means they exist. To actually make use of them, they need to be configured as handlers globally or in a specific room — see [Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:342
+#: ../../../docs/configuring-playbook-bot-baibot.md:310
 msgid "💡 You may also wish to use these new agents for [🤝 Configuring initial default handlers](#-configuring-initial-default-handlers)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:344
+#: ../../../docs/configuring-playbook-bot-baibot.md:312
 msgid "🤝 Configuring initial default handlers"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:346
+#: ../../../docs/configuring-playbook-bot-baibot.md:314
 msgid "This section is only useful if you're [🤖 Configuring agents via Ansible](#-configuring-agents-via-ansible), as it lets you put these agents to use as soon as the bot starts (by adjusting the bot's **initial global configuration**)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:348
+#: ../../../docs/configuring-playbook-bot-baibot.md:316
 msgid "If you're not configuring agents via Ansible, you can skip this section."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:350
+#: ../../../docs/configuring-playbook-bot-baibot.md:318
 msgid "This section is only useful the first time around. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:352
+#: ../../../docs/configuring-playbook-bot-baibot.md:320
 msgid "baibot supports [various purposes](https://github.com/etkecc/baibot/blob/main/docs/features.md):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:354
+#: ../../../docs/configuring-playbook-bot-baibot.md:322
 msgid "[💬 text-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-generation): communicating with you via text"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:356
+#: ../../../docs/configuring-playbook-bot-baibot.md:324
 msgid "[🦻 speech-to-text](https://github.com/etkecc/baibot/blob/main/docs/features.md#-speech-to-text): turning your voice messages into text"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:358
+#: ../../../docs/configuring-playbook-bot-baibot.md:326
 msgid "[🗣️ text-to-speech](https://github.com/etkecc/baibot/blob/main/docs/features.md#-text-to-speech): turning bot or users text messages into voice messages"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:360
+#: ../../../docs/configuring-playbook-bot-baibot.md:328
 msgid "[🖌️ image-generation](https://github.com/etkecc/baibot/blob/main/docs/features.md#-image-generation): generating images based on instructions"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:362
+#: ../../../docs/configuring-playbook-bot-baibot.md:330
 msgid "❓ catch-all: special purposes, indicating use as a fallback (when no specific handler is configured)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:364
+#: ../../../docs/configuring-playbook-bot-baibot.md:332
 msgid "[Mixing & matching models](https://github.com/etkecc/baibot/blob/main/docs/features.md#mixing--matching-models) is made possible by the bot's ability to have different [🤝 handlers](https://github.com/etkecc/baibot/blob/main/docs/configuration/handlers.md) configured for different purposes."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:366
+#: ../../../docs/configuring-playbook-bot-baibot.md:334
 msgid "This configuration can be done as a global fallback, or per-room. Both of these [🛠️ configurations](https://github.com/etkecc/baibot/blob/main/docs/configuration/README.md) are managed at runtime (viat chat), but **the global configuration can have some initial defaults configured via Ansible**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:368
+#: ../../../docs/configuring-playbook-bot-baibot.md:336
 msgid "You can configure the **initial values** for these via Ansible, via the `matrix_bot_baibot_config_initial_global_config_handler_*` variables."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:370
+#: ../../../docs/configuring-playbook-bot-baibot.md:338
 msgid "Example **additional** `vars.yml` configuration:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:387
+#: ../../../docs/configuring-playbook-bot-baibot.md:355
 msgid "**Note**: these are initial defaults for the bot's global configuration. As such, changing any of these values subsequently has no effect on the bot's behavior. **Once initially configured the global configuration cannot be managed Ansible**, but only via bot commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:389
+#: ../../../docs/configuring-playbook-bot-baibot.md:357
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:391
+#: ../../../docs/configuring-playbook-bot-baibot.md:359
 msgid "There are some additional things you may wish to configure about the bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:393
+#: ../../../docs/configuring-playbook-bot-baibot.md:361
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:395
+#: ../../../docs/configuring-playbook-bot-baibot.md:363
 msgid "`roles/custom/matrix-bot-baibot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:396
+#: ../../../docs/configuring-playbook-bot-baibot.md:364
 msgid "`roles/custom/matrix-bot-baibot/templates/config.yaml.j2` for the bot's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bot_baibot_configuration_extension_yaml` variable"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:398
+#: ../../../docs/configuring-playbook-bot-baibot.md:366
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:400
+#: ../../../docs/configuring-playbook-bot-baibot.md:368
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:407
+#: ../../../docs/configuring-playbook-bot-baibot.md:375
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:409
+#: ../../../docs/configuring-playbook-bot-baibot.md:377
-msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account when password authentication is used."
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:411
+#: ../../../docs/configuring-playbook-bot-baibot.md:379
-msgid "If you're using access-token authentication, the bot account must already exist and the configured token + device ID must match that account. This mode is mainly for MAS/OIDC setups where password-based bot login is not suitable."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-baibot.md:413
 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-baibot.md:415
+#: ../../../docs/configuring-playbook-bot-baibot.md:381
 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-baibot.md:417
+#: ../../../docs/configuring-playbook-bot-baibot.md:383
-msgid "If you change the bot password (`matrix_bot_baibot_config_user_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_baibot_config_user_password` to let the bot know its new password. (This note applies to password authentication mode.)"
+msgid "If you change the bot password (`matrix_bot_baibot_config_user_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_baibot_config_user_password` to let the bot know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:419
+#: ../../../docs/configuring-playbook-bot-baibot.md:385
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:421
+#: ../../../docs/configuring-playbook-bot-baibot.md:387
 msgid "To use the bot, invite it to any existing Matrix room (`/invite @baibot:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:423
+#: ../../../docs/configuring-playbook-bot-baibot.md:389
 msgid "If you're an allowed bot [👥 user](https://github.com/etkecc/baibot/blob/main/docs/access.md#user) (see [👥 Initial users configuration](#-initial-users-configuration)), the bot will accept your invitation and join the room."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:425
+#: ../../../docs/configuring-playbook-bot-baibot.md:391
 msgid "After joining, the bot will introduce itself and show information about the [✨ features](https://github.com/etkecc/baibot/blob/main/docs/features.md) that are enabled for it."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:427
+#: ../../../docs/configuring-playbook-bot-baibot.md:393
 msgid "If you've [🤖 configured one or more agents via Ansible](#-configuring-agents-via-ansible) and have [🤝 configured initial default handlers](#configuring-initial-default-handlers), the bot will immediately be able to make use of these agents for this new room. Otherwise, you will need to configure agents and/or handlers via chat commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:429
+#: ../../../docs/configuring-playbook-bot-baibot.md:395
 msgid "Send `!bai help` to the bot in the room to see the available commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:431
+#: ../../../docs/configuring-playbook-bot-baibot.md:397
 msgid "You can also refer to the upstream [baibot](https://github.com/etkecc/baibot) project's documentation."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:433
+#: ../../../docs/configuring-playbook-bot-baibot.md:399
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:435
+#: ../../../docs/configuring-playbook-bot-baibot.md:401
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-baibot`."
+msgid "As with all other services, you can find service logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-bot-baibot`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:437
+#: ../../../docs/configuring-playbook-bot-baibot.md:403
-msgid "Increase logging verbosity"
+msgid "The default logging level for this service is `info`, but you can increase it to `debug` (or even `trace`) with the following additional configuration:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-baibot.md:439
+#: ../../../docs/configuring-playbook-bot-baibot.md:417
-msgid "The default logging level for this service is `info`. If you want to increase the verbosity to `debug` (or even `trace`), add the following configuration to your `vars.yml` file and re-run the playbook:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-baibot.md:453
 msgid "**Alternatively**, you can use a single variable to set the logging level for all of the above (bot + all libraries):"
 msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-buscarron.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,156 +18,156 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:9
+#: ../../../docs/configuring-playbook-bot-buscarron.md:1
 msgid "Setting up Buscarron (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:11
+#: ../../../docs/configuring-playbook-bot-buscarron.md:3
 msgid "The playbook can install and configure [Buscarron](https://github.com/etkecc/buscarron) for you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:13
+#: ../../../docs/configuring-playbook-bot-buscarron.md:5
 msgid "Buscarron is bot that receives HTTP POST submissions of web forms and forwards them to a Matrix room."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:15
+#: ../../../docs/configuring-playbook-bot-buscarron.md:7
 msgid "See the project's [documentation](https://github.com/etkecc/buscarron/blob/main/README.md) to learn what it does and why it might be useful to you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:17
+#: ../../../docs/configuring-playbook-bot-buscarron.md:9
 msgid "Adjusting DNS records"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:19
+#: ../../../docs/configuring-playbook-bot-buscarron.md:11
 msgid "By default, this playbook installs Buscarron on the `buscarron.` subdomain (`buscarron.example.com`) and requires you to create a CNAME record for `buscarron`, which targets `matrix.example.com`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:21
+#: ../../../docs/configuring-playbook-bot-buscarron.md:13
 msgid "When setting, replace `example.com` with your own."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:23
+#: ../../../docs/configuring-playbook-bot-buscarron.md:15
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:25
+#: ../../../docs/configuring-playbook-bot-buscarron.md:17
 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:48
+#: ../../../docs/configuring-playbook-bot-buscarron.md:40
 msgid "Adjusting the Buscarron URL (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:50
+#: ../../../docs/configuring-playbook-bot-buscarron.md:42
 msgid "By tweaking the `matrix_bot_buscarron_hostname` and `matrix_bot_buscarron_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:52
+#: ../../../docs/configuring-playbook-bot-buscarron.md:44
 msgid "Example additional configuration for your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:63
+#: ../../../docs/configuring-playbook-bot-buscarron.md:55
 msgid "After changing the domain, **you may need to adjust your DNS** records to point the Buscarron domain to the Matrix server."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:65
+#: ../../../docs/configuring-playbook-bot-buscarron.md:57
 msgid "If you've decided to reuse the `matrix.` domain, you won't need to do any extra DNS configuration."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:67
+#: ../../../docs/configuring-playbook-bot-buscarron.md:59
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:69
+#: ../../../docs/configuring-playbook-bot-buscarron.md:61
 msgid "There are some additional things you may wish to configure about the bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:71
+#: ../../../docs/configuring-playbook-bot-buscarron.md:63
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:73
+#: ../../../docs/configuring-playbook-bot-buscarron.md:65
 msgid "`roles/custom/matrix-bot-buscarron/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:75
+#: ../../../docs/configuring-playbook-bot-buscarron.md:67
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:77
+#: ../../../docs/configuring-playbook-bot-buscarron.md:69
 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:84
+#: ../../../docs/configuring-playbook-bot-buscarron.md:76
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:86
+#: ../../../docs/configuring-playbook-bot-buscarron.md:78
 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:88
+#: ../../../docs/configuring-playbook-bot-buscarron.md:80
 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-buscarron.md:90
+#: ../../../docs/configuring-playbook-bot-buscarron.md:82
 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-buscarron.md:92
+#: ../../../docs/configuring-playbook-bot-buscarron.md:84
-msgid "If you change the bot password (`matrix_bot_buscarron_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_buscarron_password` to let the bot know its new password."
+msgid "If you change the bot password (`matrix_bot_buscarron_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_buscarron_password` to let the bot know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:94
+#: ../../../docs/configuring-playbook-bot-buscarron.md:86
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:96
+#: ../../../docs/configuring-playbook-bot-buscarron.md:88
 msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @bot.buscarron:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:98
+#: ../../../docs/configuring-playbook-bot-buscarron.md:90
 msgid "After the bot joins the room, anyone can call the web form via HTTP POST method."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:100
+#: ../../../docs/configuring-playbook-bot-buscarron.md:92
 msgid "Here is an example for the `contact` form:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:108
+#: ../../../docs/configuring-playbook-bot-buscarron.md:100
 msgid "**Note**: to fight against spam, Buscarron is **very aggressive when it comes to banning** and will ban you if:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:110
+#: ../../../docs/configuring-playbook-bot-buscarron.md:102
 msgid "you hit the homepage (HTTP `GET` request to `/`)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:111
+#: ../../../docs/configuring-playbook-bot-buscarron.md:103
 msgid "you submit a form to the wrong URL (`POST` request to `/non-existing-form`)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:112
+#: ../../../docs/configuring-playbook-bot-buscarron.md:104
 msgid "`hasemail` is enabled for the form (like in the example above) and you don't submit an `email` field"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:114
+#: ../../../docs/configuring-playbook-bot-buscarron.md:106
 msgid "If you get banned, you'd need to restart the process by running the playbook with `--tags=start` or running `systemctl restart matrix-bot-buscarron` on the server."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:116
+#: ../../../docs/configuring-playbook-bot-buscarron.md:108
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:118
+#: ../../../docs/configuring-playbook-bot-buscarron.md:110
 msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-buscarron`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:120
+#: ../../../docs/configuring-playbook-bot-buscarron.md:112
 msgid "Increase logging verbosity"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-buscarron.md:122
+#: ../../../docs/configuring-playbook-bot-buscarron.md:114
 msgid "The default logging level for this component is `INFO`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
 msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-draupnir.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,421 +18,392 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:10
+#: ../../../docs/configuring-playbook-bot-draupnir.md:1
 msgid "Setting up Draupnir (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:12
+#: ../../../docs/configuring-playbook-bot-draupnir.md:3
 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:5
 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:7
 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:9
 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:11
 msgid "Prerequisites"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:22
+#: ../../../docs/configuring-playbook-bot-draupnir.md:13
 msgid "Create a management room"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:24
+#: ../../../docs/configuring-playbook-bot-draupnir.md:15
 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:17
 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:20
 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:22
 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:24
 msgid "End-to-End Encryption support"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:35
+#: ../../../docs/configuring-playbook-bot-draupnir.md:26
 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:28
 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:30
 msgid "Disable Pantalaimon for Draupnir (since v2.0.0; optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:41
+#: ../../../docs/configuring-playbook-bot-draupnir.md:32
 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:34
 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:36
 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:38
 msgid "Native E2EE support"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:49
+#: ../../../docs/configuring-playbook-bot-draupnir.md:40
 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:42
 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:44
 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:55
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:66
+#: ../../../docs/configuring-playbook-bot-draupnir.md:57
 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."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:85
+#: ../../../docs/configuring-playbook-bot-draupnir.md:76
 msgid "Create and invite the bot to the management room"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:87
+#: ../../../docs/configuring-playbook-bot-draupnir.md:78
 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:93
+#: ../../../docs/configuring-playbook-bot-draupnir.md:84
 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:95
+#: ../../../docs/configuring-playbook-bot-draupnir.md:86
 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:97
+#: ../../../docs/configuring-playbook-bot-draupnir.md:88
 msgid "Make sure the account is free from rate limiting (optional, recommended)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:99
+#: ../../../docs/configuring-playbook-bot-draupnir.md:90
 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:101
+#: ../../../docs/configuring-playbook-bot-draupnir.md:92
 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:103
+#: ../../../docs/configuring-playbook-bot-draupnir.md:94
 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:105
+#: ../../../docs/configuring-playbook-bot-draupnir.md:96
-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)."
+msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:107
+#: ../../../docs/configuring-playbook-bot-draupnir.md:98
 msgid "Add the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:109
+#: ../../../docs/configuring-playbook-bot-draupnir.md:100
 msgid "To expose the APIs publicly, add the following configuration to your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:115
+#: ../../../docs/configuring-playbook-bot-draupnir.md:106
 msgid "Obtain an access token for admin account"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:117
+#: ../../../docs/configuring-playbook-bot-draupnir.md:108
 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:119
+#: ../../../docs/configuring-playbook-bot-draupnir.md:110
 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:122
+#: ../../../docs/configuring-playbook-bot-draupnir.md:113
 msgid "Run the `curl` command"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:124
+#: ../../../docs/configuring-playbook-bot-draupnir.md:115
 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:126
+#: ../../../docs/configuring-playbook-bot-draupnir.md:117
 msgid "`ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:127
+#: ../../../docs/configuring-playbook-bot-draupnir.md:118
 msgid "`example.com` with your base domain"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:128
+#: ../../../docs/configuring-playbook-bot-draupnir.md:119
 msgid "`@bot.draupnir:example.com` with the MXID of your Draupnir bot user"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:134
+#: ../../../docs/configuring-playbook-bot-draupnir.md:125
-#: ../../../docs/configuring-playbook-bot-draupnir.md:207
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:135
+#: ../../../docs/configuring-playbook-bot-draupnir.md:126
 msgid "This does not work on outdated Windows 10 as curl is not available there."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:136
+#: ../../../docs/configuring-playbook-bot-draupnir.md:127
 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:138
+#: ../../../docs/configuring-playbook-bot-draupnir.md:129
 msgid "Abuse Reports"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:140
+#: ../../../docs/configuring-playbook-bot-draupnir.md:131
 msgid "Draupnir can receive reports in the management room."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:142
+#: ../../../docs/configuring-playbook-bot-draupnir.md:133
 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:148
+#: ../../../docs/configuring-playbook-bot-draupnir.md:145
-msgid "Enabling synapse-http-antispam support"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-draupnir.md:150
-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:160
-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."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-draupnir.md:168
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:170
+#: ../../../docs/configuring-playbook-bot-draupnir.md:147
 msgid "There are some additional things you may wish to configure about the bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:172
+#: ../../../docs/configuring-playbook-bot-draupnir.md:149
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:174
+#: ../../../docs/configuring-playbook-bot-draupnir.md:151
 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:176
+#: ../../../docs/configuring-playbook-bot-draupnir.md:153
 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:190
+#: ../../../docs/configuring-playbook-bot-draupnir.md:167
 msgid "Migrating from Mjolnir (Only required if migrating)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:192
+#: ../../../docs/configuring-playbook-bot-draupnir.md:169
 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:194
+#: ../../../docs/configuring-playbook-bot-draupnir.md:171
 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:196
+#: ../../../docs/configuring-playbook-bot-draupnir.md:173
 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:198
+#: ../../../docs/configuring-playbook-bot-draupnir.md:175
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:200
+#: ../../../docs/configuring-playbook-bot-draupnir.md:177
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:209
+#: ../../../docs/configuring-playbook-bot-draupnir.md:184
-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:211
 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:213
+#: ../../../docs/configuring-playbook-bot-draupnir.md:186
 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:215
+#: ../../../docs/configuring-playbook-bot-draupnir.md:188
-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:217
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:219
+#: ../../../docs/configuring-playbook-bot-draupnir.md:190
 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:221
+#: ../../../docs/configuring-playbook-bot-draupnir.md:192
 msgid "Below is a **non-exhaustive quick-start guide** for the impatient."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:223
+#: ../../../docs/configuring-playbook-bot-draupnir.md:194
 msgid "Making Draupnir join and protect a room"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:225
+#: ../../../docs/configuring-playbook-bot-draupnir.md:196
 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:227
+#: ../../../docs/configuring-playbook-bot-draupnir.md:198
 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:229
+#: ../../../docs/configuring-playbook-bot-draupnir.md:200
 msgid "[Give the bot permissions to do its job](#giving-draupnir-permissions-to-do-its-job)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:231
+#: ../../../docs/configuring-playbook-bot-draupnir.md:202
 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:233
+#: ../../../docs/configuring-playbook-bot-draupnir.md:204
 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:235
+#: ../../../docs/configuring-playbook-bot-draupnir.md:206
 msgid "Giving Draupnir permissions to do its job"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:237
+#: ../../../docs/configuring-playbook-bot-draupnir.md:208
 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:239
+#: ../../../docs/configuring-playbook-bot-draupnir.md:210
 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:241
+#: ../../../docs/configuring-playbook-bot-draupnir.md:212
 msgid "Subscribing to a public policy list"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:243
+#: ../../../docs/configuring-playbook-bot-draupnir.md:214
 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:245
+#: ../../../docs/configuring-playbook-bot-draupnir.md:216
-msgid "Policy lists are maintained in Matrix rooms. Popular ones maintained in the public are:"
+msgid "Polcy lists are maintained in Matrix rooms. A popular policy list is maintained in the public `#community-moderation-effort-bl:neko.dev` room."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:247
+#: ../../../docs/configuring-playbook-bot-draupnir.md:218
-msgid "`#community-moderation-effort-bl:neko.dev`"
+msgid "You can tell Draupnir to subscribe to it by sending the following command to the Management Room: `!draupnir watch #community-moderation-effort-bl:neko.dev`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:248
+#: ../../../docs/configuring-playbook-bot-draupnir.md:220
-msgid "`#huginn-muninn-active-threats:feline.support`"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-draupnir.md:250
-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:252
 msgid "Creating your own policy lists and rules"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:254
+#: ../../../docs/configuring-playbook-bot-draupnir.md:222
 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:256
+#: ../../../docs/configuring-playbook-bot-draupnir.md:224
 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:258
+#: ../../../docs/configuring-playbook-bot-draupnir.md:226
 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:260
+#: ../../../docs/configuring-playbook-bot-draupnir.md:228
 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:262
+#: ../../../docs/configuring-playbook-bot-draupnir.md:230
 msgid "To create rules, you run commands in the Management Room (**not** in the policy list room)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:264
+#: ../../../docs/configuring-playbook-bot-draupnir.md:232
 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:265
+#: ../../../docs/configuring-playbook-bot-draupnir.md:233
-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`"
+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:267
+#: ../../../docs/configuring-playbook-bot-draupnir.md:235
 msgid "As a result of running these commands, you may observe:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:269
+#: ../../../docs/configuring-playbook-bot-draupnir.md:237
 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:270
+#: ../../../docs/configuring-playbook-bot-draupnir.md:238
 msgid "applying these rules against all rooms that Draupnir is an Administrator in"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:272
+#: ../../../docs/configuring-playbook-bot-draupnir.md:240
 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:274
+#: ../../../docs/configuring-playbook-bot-draupnir.md:242
 msgid "Enabling built-in protections"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:276
+#: ../../../docs/configuring-playbook-bot-draupnir.md:244
-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\")."
+msgid "You can also **turn on various built-in [protections](https://the-draupnir-project.github.io/draupnir-documentation/protections)** like `JoinWaveShortCircuit` (\"If X amount of users join in Y time, set the room to invite-only\")."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:278
+#: ../../../docs/configuring-playbook-bot-draupnir.md:246
 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:280
+#: ../../../docs/configuring-playbook-bot-draupnir.md:248
-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`)."
+msgid "To **see the configuration options for a given protection**, send a `!draupnir protections show PROTECTION_NAME` (e.g. `!draupnir protections show JoinWaveShortCircuit`)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:282
+#: ../../../docs/configuring-playbook-bot-draupnir.md:250
-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`)."
+msgid "To **set a specific option for a given protection**, send a command like this: `!draupnir config set PROTECTION_NAME.OPTION VALUE` (e.g. `!draupnir config set JoinWaveShortCircuit.timescaleMinutes 30`)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:284
+#: ../../../docs/configuring-playbook-bot-draupnir.md:252
-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`)."
+msgid "To **enable a given protection**, send a command like this: `!draupnir enable PROTECTION_NAME` (e.g. `!draupnir enable JoinWaveShortCircuit`)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-draupnir.md:286
+#: ../../../docs/configuring-playbook-bot-draupnir.md:254
-msgid "To **disable a given protection**, send a command like this: `!draupnir protections disable PROTECTION_NAME` (e.g. `!draupnir protections disable JoinWaveShortCircuitProtection`)."
+msgid "To **disable a given protection**, send a command like this: `!draupnir disable PROTECTION_NAME` (e.g. `!draupnir disable JoinWaveShortCircuit`)."
 msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-honoroit.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,140 +18,108 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:9
+#: ../../../docs/configuring-playbook-bot-honoroit.md:1
 msgid "Setting up Honoroit (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:11
+#: ../../../docs/configuring-playbook-bot-honoroit.md:3
 msgid "The playbook can install and configure [Honoroit](https://github.com/etkecc/honoroit) for you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:13
+#: ../../../docs/configuring-playbook-bot-honoroit.md:5
 msgid "It's a bot you can use to setup **your own helpdesk on matrix**"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:15
+#: ../../../docs/configuring-playbook-bot-honoroit.md:7
 msgid "See the project's [documentation](https://github.com/etkecc/honoroit/blob/main/README.md) to learn what it does and why it might be useful to you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:17
+#: ../../../docs/configuring-playbook-bot-honoroit.md:9
 msgid "Adjusting DNS records (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:19
+#: ../../../docs/configuring-playbook-bot-honoroit.md:11
 msgid "By default, this playbook installs Honoroit on the `matrix.` subdomain, at the `/honoroit` path (https://matrix.example.com/honoroit). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:21
+#: ../../../docs/configuring-playbook-bot-honoroit.md:13
 msgid "If you wish to adjust it, see the section [below](#adjusting-the-honoroit-url-optional) for details about DNS configuration."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:23
+#: ../../../docs/configuring-playbook-bot-honoroit.md:15
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:25
+#: ../../../docs/configuring-playbook-bot-honoroit.md:17
 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:40
+#: ../../../docs/configuring-playbook-bot-honoroit.md:32
 msgid "Adjusting the Honoroit URL (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:42
+#: ../../../docs/configuring-playbook-bot-honoroit.md:34
 msgid "By tweaking the `matrix_bot_honoroit_hostname` and `matrix_bot_honoroit_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:44
+#: ../../../docs/configuring-playbook-bot-honoroit.md:36
 msgid "Example additional configuration for your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:52
+#: ../../../docs/configuring-playbook-bot-honoroit.md:44
 msgid "If you've changed the default hostname, you may need to create a CNAME record for the Honoroit domain (`honoroit.example.com`), which targets `matrix.example.com`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:54
+#: ../../../docs/configuring-playbook-bot-honoroit.md:46
 msgid "When setting, replace `example.com` with your own."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:56
+#: ../../../docs/configuring-playbook-bot-honoroit.md:48
-msgid "Extending the configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:58
-msgid "There are some additional things you may wish to configure about the bot."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:60
-msgid "Take a look at:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:62
-msgid "`roles/custom/matrix-bot-honoroit/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:64
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:66
+#: ../../../docs/configuring-playbook-bot-honoroit.md:50
 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:73
+#: ../../../docs/configuring-playbook-bot-honoroit.md:57
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:75
+#: ../../../docs/configuring-playbook-bot-honoroit.md:59
 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:77
+#: ../../../docs/configuring-playbook-bot-honoroit.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-bot-honoroit.md:79
+#: ../../../docs/configuring-playbook-bot-honoroit.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-bot-honoroit.md:81
+#: ../../../docs/configuring-playbook-bot-honoroit.md:65
-msgid "If you change the bot password (`matrix_bot_honoroit_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_honoroit_password` to let the bot know its new password."
+msgid "If you change the bot password (`matrix_bot_honoroit_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_honoroit_password` to let the bot know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:83
+#: ../../../docs/configuring-playbook-bot-honoroit.md:67
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:85
+#: ../../../docs/configuring-playbook-bot-honoroit.md:69
 msgid "To use the bot, invite it to the room you specified on your `vars.yml` file (`/invite @honoroit:example.com` where `example.com` is your base domain, not the `matrix.` domain)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:87
+#: ../../../docs/configuring-playbook-bot-honoroit.md:71
 msgid "After the bot joins the room, any Matrix user can send a message to it to start a new thread in that room."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:89
+#: ../../../docs/configuring-playbook-bot-honoroit.md:73
 msgid "Send `!ho help` to the bot in the room to see the available commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-honoroit.md:91
+#: ../../../docs/configuring-playbook-bot-honoroit.md:75
 msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/honoroit#features)."
 msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:93
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:95
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-honoroit`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:97
-msgid "Increase logging verbosity"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-honoroit.md:99
-msgid "If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
-msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-registration-bot.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,120 +18,84 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:13
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:1
 msgid "Setting up matrix-registration-bot (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:15
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:3
 msgid "The playbook can install and configure [matrix-registration-bot](https://github.com/moan0s/matrix-registration-bot) for you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:17
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:5
 msgid "The bot allows you to easily **create and manage registration tokens** aka. invitation codes. It can be used for an invitation-based server, where you invite someone by sending them a registration token (tokens look like this: `rbalQ0zkaDSRQCOp`). They can register as per normal but have to provide a valid registration token in the final step of the registration process."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:19
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:7
 msgid "See the project's [documentation](https://github.com/moan0s/matrix-registration-bot/blob/master/README.md) to learn what it does and why it might be useful to you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:21
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:9
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:23
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:11
 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:46
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:30
 msgid "The bot account will be created automatically."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:48
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:32
-msgid "Extending the configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:50
-msgid "There are some additional things you may wish to configure about the bot."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:52
-msgid "Take a look at:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:54
-msgid "`roles/custom/matrix-bot-matrix-registration-bot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55
-msgid "`roles/custom/matrix-bot-matrix-registration-bot/templates/config.yaml.j2` for the bridge's default configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:59
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:34
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:66
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:41
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:68
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:43
 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:70
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:45
 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-matrix-registration-bot.md:72
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:47
 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-matrix-registration-bot.md:74
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:49
-msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_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_matrix_registration_bot_bot_password` to let the bot know its new password."
+msgid "If you change the bot password (`matrix_bot_matrix_registration_bot_bot_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_registration_bot_bot_password` to let the bot know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:76
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:51
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:78
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:53
 msgid "To use the bot, start a chat with `@bot.matrix-registration-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:80
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:55
 msgid "Send `help` to the bot to see the available commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:82
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:57
 msgid "You can also refer to the upstream [Usage documentation](https://github.com/moan0s/matrix-registration-bot#supported-commands)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:84
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:59
-msgid "If you have any questions, or if you need help setting it up, read the [troubleshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)."
+msgid "If you have any questions, or if you need help setting it up, read the [troublshooting guide](https://github.com/moan0s/matrix-registration-bot/blob/main/docs/troubleshooting.md) or join [#matrix-registration-bot:hyteck.de](https://matrix.to/#/#matrix-registration-bot:hyteck.de)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:86
+#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:61
 msgid "To clean the cache (session & encryption data) after you changed the bot's username, changed the login method from access_token to password etc… you can use:"
 msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:92
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:94
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-matrix-registration-bot`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:96
-msgid "Increase logging verbosity"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-registration-bot.md:98
-msgid "The default logging level for this component is `INFO`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
-msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-matrix-reminder-bot.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2024-12-23 13:09+0900\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,116 +18,80 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:1
 msgid "Setting up matrix-reminder-bot (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:3
 msgid "The playbook can install and configure [matrix-reminder-bot](https://github.com/anoadragon453/matrix-reminder-bot) for you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:13
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:5
 msgid "It's a bot you can use to **schedule one-off & recurring reminders and alarms**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:15
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:7
 msgid "See the project's [documentation](https://github.com/anoadragon453/matrix-reminder-bot/blob/master/README.md) to learn what it does and why it might be useful to you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:17
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:9
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:19
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:11
 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:34
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:26
-msgid "Extending the configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:36
-msgid "There are some additional things you may wish to configure about the bot."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:38
-msgid "Take a look at:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:40
-msgid "`roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:41
-msgid "`roles/custom/matrix-bot-matrix-reminder-bot/templates/config.yaml.j2` for the bot's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_bot_matrix_reminder_bot_configuration_extension_yaml` variable"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:43
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:45
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:28
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:52
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:35
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:54
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:37
 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:56
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:39
 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-matrix-reminder-bot.md:58
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:41
 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-matrix-reminder-bot.md:60
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:43
-msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_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_matrix_reminder_bot_matrix_user_password` to let the bot know its new password."
+msgid "If you change the bot password (`matrix_bot_matrix_reminder_bot_matrix_user_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_matrix_reminder_bot_matrix_user_password` to let the bot know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:62
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:45
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:64
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:47
 msgid "To use the bot, start a chat with `@bot.matrix-reminder-bot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:66
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:49
 msgid "You can also add the bot to any existing Matrix room (`/invite @bot.matrix-reminder-bot:example.com`)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:68
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:51
 msgid "Basic usage is like this: `!remindme in 2 minutes; This is a test`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:70
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:53
 msgid "Send `!help reminders` to the room to see the bot's help menu for additional commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:72
+#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:55
 msgid "You can also refer to the upstream [Usage documentation](https://github.com/anoadragon453/matrix-reminder-bot#usage)."
 msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:74
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:76
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-matrix-reminder-bot`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:78
-msgid "Increase logging verbosity"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-matrix-reminder-bot.md:80
-msgid "The default logging level for this component is `INFO`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
-msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-maubot.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,185 +18,149 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:12
+#: ../../../docs/configuring-playbook-bot-maubot.md:1
 msgid "Setting up maubot (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:14
+#: ../../../docs/configuring-playbook-bot-maubot.md:3
 msgid "The playbook can install and configure [maubot](https://github.com/maubot/maubot) for you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:16
+#: ../../../docs/configuring-playbook-bot-maubot.md:5
 msgid "After setting up maubot, you can use the web management interface to make it do things. The default location of the management interface is `matrix.example.com/_matrix/maubot/`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:18
+#: ../../../docs/configuring-playbook-bot-maubot.md:7
 msgid "See the project's [documentation](https://docs.mau.fi/maubot/usage/basic.html) to learn what it does and why it might be useful to you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:20
+#: ../../../docs/configuring-playbook-bot-maubot.md:9
 msgid "Adjusting DNS records (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:22
+#: ../../../docs/configuring-playbook-bot-maubot.md:11
 msgid "By default, this playbook installs maubot on the `matrix.` subdomain, at the `/_matrix/maubot/` path (https://matrix.example.com/_matrix/maubot/). This makes it easy to install it, because it **doesn't require additional DNS records to be set up**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:24
+#: ../../../docs/configuring-playbook-bot-maubot.md:13
 msgid "If you wish to adjust it, see the section [below](#adjusting-the-maubot-url-optional) for details about DNS configuration."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:26
+#: ../../../docs/configuring-playbook-bot-maubot.md:15
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:28
+#: ../../../docs/configuring-playbook-bot-maubot.md:17
 msgid "To enable the bot, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:43
+#: ../../../docs/configuring-playbook-bot-maubot.md:32
 msgid "You can add multiple admins. The admin accounts are only used to access the maubot administration interface."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:45
+#: ../../../docs/configuring-playbook-bot-maubot.md:34
 msgid "Adjusting the maubot URL (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:47
+#: ../../../docs/configuring-playbook-bot-maubot.md:36
 msgid "By tweaking the `matrix_bot_maubot_hostname` and `matrix_bot_maubot_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:49
+#: ../../../docs/configuring-playbook-bot-maubot.md:38
-#: ../../../docs/configuring-playbook-bot-maubot.md:76
+#: ../../../docs/configuring-playbook-bot-maubot.md:56
 msgid "Example additional configuration for your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:57
+#: ../../../docs/configuring-playbook-bot-maubot.md:46
 msgid "If you've changed the default hostname, you may need to create a CNAME record for the maubot domain (`maubot.example.com`), which targets `matrix.example.com`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:59
+#: ../../../docs/configuring-playbook-bot-maubot.md:48
 msgid "When setting, replace `example.com` with your own."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:61
+#: ../../../docs/configuring-playbook-bot-maubot.md:50
-msgid "Extending the configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:63
-msgid "There are some additional things you may wish to configure about the bot."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:65
-msgid "Take a look at:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:67
-msgid "`roles/custom/matrix-bot-maubot/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:68
-msgid "`roles/custom/matrix-bot-maubot/templates/config.yaml.j2` for the bot's default configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:70
 msgid "Customizing the maubot container image"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:72
+#: ../../../docs/configuring-playbook-bot-maubot.md:52
 msgid "Certain [maubot plugins](https://plugins.mau.bot/) require additional dependencies to be installed."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:74
+#: ../../../docs/configuring-playbook-bot-maubot.md:54
 msgid "You can customize the default maubot container image and install your own dependencies."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:87
+#: ../../../docs/configuring-playbook-bot-maubot.md:67
 msgid "Consult the [Dockerfile reference](https://docs.docker.com/reference/dockerfile/) for more information about the syntax."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:89
+#: ../../../docs/configuring-playbook-bot-maubot.md:69
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:91
+#: ../../../docs/configuring-playbook-bot-maubot.md:71
 msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:98
+#: ../../../docs/configuring-playbook-bot-maubot.md:78
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:100
+#: ../../../docs/configuring-playbook-bot-maubot.md:80
 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:102
+#: ../../../docs/configuring-playbook-bot-maubot.md:82
 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-maubot.md:104
+#: ../../../docs/configuring-playbook-bot-maubot.md:84
 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-maubot.md:106
+#: ../../../docs/configuring-playbook-bot-maubot.md:86
-msgid "If you change the bot password (`matrix_bot_maubot_initial_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_maubot_initial_password` to let the bot know its new password."
+msgid "If you change the bot password (`matrix_bot_maubot_initial_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_maubot_initial_password` to let the bot know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:108
+#: ../../../docs/configuring-playbook-bot-maubot.md:88
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:110
+#: ../../../docs/configuring-playbook-bot-maubot.md:90
 msgid "By default, you can visit `matrix.example.com/_matrix/maubot/` to manage your available plugins, clients and instances."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:112
+#: ../../../docs/configuring-playbook-bot-maubot.md:92
 msgid "You should start in the following order"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:113
+#: ../../../docs/configuring-playbook-bot-maubot.md:93
 msgid "**Create one or more clients**: A client is a Matrix account which the bot will use to message. By default, the playbook creates a `bot.maubot` account (as per the configuration above). You only need to [obtain an access token](#obtaining-an-access-token) for it"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:114
+#: ../../../docs/configuring-playbook-bot-maubot.md:94
 msgid "**Upload some Plugins**: Plugins can be obtained from [here](https://github.com/maubot/maubot#plugins) or any other source."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:115
+#: ../../../docs/configuring-playbook-bot-maubot.md:95
 msgid "**Create an instance**: An instance is the actual bot. You have to specify a client which the bot instance will use and the plugin (how the bot will behave)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:117
+#: ../../../docs/configuring-playbook-bot-maubot.md:97
 msgid "Obtain an access token"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:119
+#: ../../../docs/configuring-playbook-bot-maubot.md:99
 msgid "This can be done via `mbc login` then `mbc auth` (see the [maubot documentation](https://docs.mau.fi/maubot/usage/cli/auth.html)). To run these commands, you'll first need to `exec` into the maubot container with `docker exec -it matrix-bot-maubot sh`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:121
+#: ../../../docs/configuring-playbook-bot-maubot.md:101
 msgid "Alternatively, you can refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md). Be aware that you'd better use the **Obtain an access token via curl** method (not **Obtain an access token via Element Web**) as the latter will causes issues to your bot in encrypted rooms. Read [more](https://docs.mau.fi/maubot/usage/basic.html#creating-clients)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-maubot.md:123
+#: ../../../docs/configuring-playbook-bot-maubot.md:103
 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-maubot.md:126
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:128
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-maubot`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:130
-msgid "Increase logging verbosity"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-maubot.md:132
-msgid "The default logging level for this component is `WARNING`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
-msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bot-mjolnir.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,266 +18,254 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:12
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:1
 msgid "Setting up Mjolnir (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:14
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:3
 msgid "The playbook can install and configure the [Mjolnir](https://github.com/matrix-org/mjolnir) moderation bot for you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:16
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:5
 msgid "See the project's [documentation](https://github.com/matrix-org/mjolnir/blob/main/README.md) to learn what it does and why it might be useful to you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:18
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:7
 msgid "Prerequisites"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:20
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:9
 msgid "Register the bot account"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:22
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:11
 msgid "The playbook does not automatically create users for you. You **need to register the bot user manually** before setting up the bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:24
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:13
 msgid "Generate a strong password for the bot. You can create one with a command like `pwgen -s 64 1`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:26
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:15
 msgid "You can use the playbook to [register a new user](registering-users.md):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:32
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:21
 msgid "If you would like Mjolnir to be able to deactivate users, move aliases, shutdown rooms, etc then it must be a server admin so you need to change `admin=no` to `admin=yes` in the command above."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:34
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:23
 msgid "Obtain an access token"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:36
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:25
 msgid "The bot requires an access token to be able to connect to your homeserver. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:38
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:27
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:63
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:52
 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-mjolnir.md:41
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:30
 msgid "Make sure the account is free from rate limiting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:43
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:32
 msgid "If your homeserver's implementation is Synapse, you will need to prevent it from rate limiting the bot's account. **This is a required step. If you do not configure it, Mjolnir will crash.**"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:45
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:34
 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-mjolnir.md:47
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:36
 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-mjolnir.md:49
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:38
-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)."
+msgid "The APIs can also be accessed via [Synapse Admin](https://github.com/etkecc/synapse-admin), a web UI tool you can use to administrate users, rooms, media, etc. on your Matrix server. The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:51
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:40
 msgid "Add the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:53
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:42
 msgid "To expose the APIs publicly, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:59
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:48
 msgid "Obtain an access token for admin account"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:61
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:50
 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). If you have made Mjolnir an admin, you can just use the Mjolnir token."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:66
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:55
 msgid "Run the `curl` command"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:68
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:57
 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-mjolnir.md:70
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:59
 msgid "`ADMIN_ACCESS_TOKEN_HERE` with the access token of the admin account"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:71
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:60
 msgid "`example.com` with your base domain"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:72
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:61
 msgid "`@bot.mjolnir:example.com` with the MXID of your Mjolnir bot user"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:78
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:67
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:195
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:184
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:79
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:68
 msgid "This does not work on outdated Windows 10 as curl is not available there."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:80
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:69
 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-mjolnir.md:82
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:71
 msgid "Create a management room"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:84
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:73
 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-mjolnir.md:86
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:75
 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-mjolnir.md:89
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:78
 msgid "It is possible to make the management room encrypted (E2EE). If doing so, then you MUST enable and use Pantalaimon (see [below](#configuration-with-e2ee-support))."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:91
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:80
 msgid "Once you have created the room you need to copy the room ID so you can specify it on your `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-mjolnir.md:93
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:82
 msgid "Finally invite the `@bot.mjolnir:example.com` account you created earlier into the room."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:95
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:84
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:97
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:86
 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 just now."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:106
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:95
 msgid "End-to-End Encryption support"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:108
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:97
 msgid "Decide whether you want Mjolnir to be capable of operating in end-to-end encrypted (E2EE) rooms. This includes the management room and the moderated rooms."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:110
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:99
 msgid "To support E2EE, Mjolnir needs to [use Pantalaimon](configuring-playbook-pantalaimon.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:112
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:101
 msgid "Configuration with E2EE support"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:114
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:103
 msgid "When using Pantalaimon, Mjolnir will log in to its bot account itself through Pantalaimon, so configure its username and password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:116
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:105
 msgid "Add the following configuration to your `vars.yml` file (adapt to your needs):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:130
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:119
 msgid "The playbook's `group_vars` will configure other required settings. If using this role separately without the playbook, you also need to configure the two URLs that Mjolnir uses to reach the homeserver, one through Pantalaimon and one \"raw\". This example is taken from the playbook's `group_vars`:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:142
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:131
 msgid "Configuration without E2EE support"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:144
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:133
 msgid "When NOT using Pantalaimon, Mjolnir does not log in by itself and you must give it an access token for its bot account."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:146
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:135
 msgid "Add the following configuration to your `vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:152
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:141
 msgid "Adding Mjolnir synapse antispam module (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:154
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:143
 msgid "To enable Mjolnir synapse antispam module, add the following configuration to your `vars.yml` file (adapt to your needs):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:164
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:153
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:166
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:155
 msgid "There are some additional things you may wish to configure about the bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:168
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:157
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:170
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:159
 msgid "`roles/custom/matrix-bot-mjolnir/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_mjolnir_configuration_extension_yaml` variable"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:172
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:161
 msgid "For example, to change Mjolnir's `recordIgnoredInvites` option to `true`, add the following configuration to your `vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:186
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:175
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:188
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:177
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:197
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:186
+msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:188
 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-mjolnir.md:199
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:190
 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-mjolnir.md:201
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:192
-msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [Ketesa](configuring-playbook-ketesa.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password."
+msgid "If you change the Pantalaimon's password (`matrix_bot_mjolnir_pantalaimon_password` in your `vars.yml` file) subsequently, its credentials on the homeserver won't be updated automatically. If you'd like to change the password, use a tool like [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_bot_mjolnir_pantalaimon_password` to let Pantalaimon know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:203
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:194
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:205
+#: ../../../docs/configuring-playbook-bot-mjolnir.md:196
 msgid "You can refer to the upstream [documentation](https://github.com/matrix-org/mjolnir) for additional ways to use and configure Mjolnir. Check out their [quickstart guide](https://github.com/matrix-org/mjolnir#quickstart-guide) for some basic commands you can give to the bot."
 msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:207
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:209
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-bot-mjolnir`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:211
-msgid "Increase logging verbosity"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bot-mjolnir.md:213
-msgid "The default logging level for this component is `INFO`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
-msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-postmoogle.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,53 +18,53 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:10
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:1
 msgid "Setting up Postmoogle email bridging (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:12
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:3
 msgid "The playbook can install and configure [Postmoogle](https://github.com/etkecc/postmoogle) for you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:14
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:5
 msgid "Postmoogle is a bridge you can use to have its bot user forward emails to Matrix rooms. It runs an SMTP email server and allows you to assign mailbox addresses to the rooms."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:16
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:7
 msgid "See the project's [documentation](https://github.com/etkecc/postmoogle/blob/master/README.md) to learn what it does and why it might be useful to you."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:18
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:9
 msgid "Prerequisites"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:20
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:11
 msgid "Open the following ports on your server to be able to receive incoming emails:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:22
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:13
 msgid "`25/tcp`: SMTP"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:23
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:14
 msgid "`587/tcp`: Submission (TLS-encrypted SMTP)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:25
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:16
 msgid "If you don't open these ports, you will still be able to send emails, but not receive any."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:27
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:18
 msgid "These port numbers are configurable via the `matrix_postmoogle_smtp_host_bind_port` and `matrix_postmoogle_submission_host_bind_port` variables, but other email servers will try to deliver on these default (standard) ports, so changing them is of little use."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:29
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:20
 msgid "Adjusting DNS records"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:31
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:22
 msgid "To make Postmoogle enable its email sending features, you need to configure MX and TXT (SPF, DMARC, and DKIM) records. See the table below for values which need to be specified."
 msgstr ""
 
@@ -140,94 +140,90 @@ msgstr ""
 msgid "get it from `!pm dkim`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:40
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:31
 msgid "**Note**: the DKIM record can be retrieved after configuring and installing the bridge's bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:42
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:33
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:44
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:35
 msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:65
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:56
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:67
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:58
 msgid "There are some additional things you may wish to configure about the bridge."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:69
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:60
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:71
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:62
 msgid "`roles/custom/matrix-bridge-postmoogle/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:73
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:64
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:75
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:66
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:82
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:73
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:84
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:75
 msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create a user account of the bridge's bot."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:86
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:77
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:88
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:79
 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-bridge-postmoogle.md:90
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:81
-msgid "If you change the bridge's bot password (`matrix_postmoogle_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_postmoogle_password` to let the bot know its new password."
+msgid "If you change the bridge's bot password (`matrix_postmoogle_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 [synapse-admin](configuring-playbook-synapse-admin.md) to change it, and then update `matrix_postmoogle_password` to let the bot know its new password."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:92
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:83
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:94
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:85
 msgid "To use the bridge, invite the `@postmoogle:example.com` bot user into a room you want to use as a mailbox."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:96
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:87
 msgid "Then send `!pm mailbox NAME` to expose this Matrix room as an inbox with the email address `NAME@matrix.example.com`. Emails sent to that email address will be forwarded to the room."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:98
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:89
 msgid "Send `!pm help` to the bot in the room to see the available commands."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:100
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:91
 msgid "You can also refer to the upstream [documentation](https://github.com/etkecc/postmoogle)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:102
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:93
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:104
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:95
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-postmoogle`."
+msgid "As with all other services, you can find their logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by running something like `journalctl -fu matrix-postmoogle`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:106
+#: ../../../docs/configuring-playbook-bridge-postmoogle.md:97
-msgid "Increase logging verbosity"
+msgid "The default logging level for this bridge is `INFO`, but you can increase it to `DEBUG` with the following additional configuration:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-bridge-postmoogle.md:108
-msgid "The default logging level for this component is `INFO`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
 msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-element-admin.po

@@ -1,117 +0,0 @@
-# SOME DESCRIPTIVE TITLE.
-# Copyright (C) 2018-2026, 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>, 2026.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: matrix-docker-ansible-deploy \n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\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.18.0\n"
-
-#: ../../../docs/configuring-playbook-element-admin.md:8
-msgid "Setting up Element Admin (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:10
-msgid "The playbook can install and configure [Element Admin](https://github.com/element-hq/element-admin) for you."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:12
-msgid "Element Admin is a web-based administration panel for Synapse and [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md)."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:14
-msgid "See the project's [documentation](https://github.com/element-hq/element-admin) to learn more."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:16
-msgid "💡 **Note**: This project is still very young and doesn't have many features. [Ketesa](./configuring-playbook-ketesa.md) is the fully-featured alternative — it covers all Synapse and MAS Admin APIs, including complete user management, session management, and MAS policy data. Element Admin remains a valid choice if you prefer its interface."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:18
-msgid "Prerequisites"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:20
-msgid "A [Synapse](configuring-playbook-synapse.md) homeserver with its Admin API enabled (the playbook automatically enables it for you when you enable Element Admin)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:21
-msgid "[Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) with its Admin API enabled (the playbook automatically enables it for you when you enable Element Admin)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:23
-msgid "Decide on a domain and path"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:25
-msgid "By default, the Element Admin is configured to be served on the `admin.element.example.com` domain."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:27
-msgid "If you'd like to run Element Admin on another hostname, see the [Adjusting the Element Admin URL](#adjusting-the-element-admin-url-optional) section below."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:29
-msgid "Adjusting DNS records (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:31
-msgid "By default, this playbook installs Element Admin on the `admin.element.` subdomain (`admin.element.example.com`) and requires you to create a `CNAME` record for `admin.element`, which targets `matrix.example.com`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:33
-msgid "When setting these values, replace `example.com` with your own."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:35
-msgid "Adjusting the playbook configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:37
-msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:43
-msgid "Adjusting the Element Admin URL (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:45
-msgid "By tweaking the `matrix_element_admin_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:47
-msgid "Example additional configuration for your `vars.yml` file:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:53
-msgid "[!WARNING] A `matrix_element_admin_path_prefix` variable is also available and mean to let you configure a path prefix for the Element Admin service, but **Element Admin does not support running under a sub-path yet**."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:56
-msgid "Installing"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:58
-msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:65
-msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-element-admin.md:67
-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. Note these shortcuts run the `ensure-matrix-users-created` tag too."
-msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-ketesa.po

@@ -1,165 +0,0 @@
-# SOME DESCRIPTIVE TITLE.
-# Copyright (C) 2018-2026, 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>, 2026.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: matrix-docker-ansible-deploy \n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 12:02+0100\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.18.0\n"
-
-#: ../../../docs/configuring-playbook-ketesa.md:14
-msgid "Setting up Ketesa (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:16
-msgid "The playbook can install and configure [Ketesa](https://github.com/etkecc/ketesa) for you."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:18
-msgid "Ketesa is a fully-featured admin interface for Matrix homeservers — manage users, rooms, media, sessions, and more from one clean, responsive web UI. It is the evolution of [Awesome-Technologies/synapse-admin](https://github.com/Awesome-Technologies/synapse-admin): what began as a fork has grown into its own independent project with a redesigned interface, comprehensive Synapse and MAS API coverage, and multi-language support."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:20
-msgid "[!NOTE]"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:22
-msgid "Ketesa does not work with other homeserver implementations than Synapse due to API's incompatibility."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:23
-msgid "The latest version of Ketesa is hosted by [etke.cc](https://etke.cc/) at [admin.etke.cc](https://admin.etke.cc/). If you only need this service occasionally and trust giving your admin credentials to a 3rd party Single Page Application, you can consider using it from there and avoiding the (small) overhead of self-hosting."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:24
-msgid "This playbook also supports an alternative management UI in the shape of [Element Admin](./configuring-playbook-element-admin.md). Please note that it's currently less feature-rich than Ketesa and requires [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md)."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:26
-msgid "Adjusting DNS records (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:28
-msgid "By default, this playbook installs Ketesa on the `matrix.` subdomain, at the `/synapse-admin` path (https://matrix.example.com/synapse-admin) — the legacy path is kept for backward compatibility. This makes it easy to install it, because it **doesn't require additional DNS records to be set up**. If that's okay, you can skip this section."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:30
-msgid "If you wish to adjust it, see the section [below](#adjusting-the-ketesa-url-optional) for details about DNS configuration."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:32
-msgid "Adjusting the playbook configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:34
-msgid "To enable Ketesa, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:40
-msgid "**Note**: Ketesa requires Synapse's [Admin APIs](https://element-hq.github.io/synapse/latest/usage/administration/admin_api/index.html) to function. Access to them is restricted with a valid access token, so exposing them publicly should not be a real security concern. Still, for additional security, we normally leave them unexposed, following [official Synapse reverse-proxying recommendations](https://element-hq.github.io/synapse/latest/reverse_proxy.html#synapse-administration-endpoints). Because Ketesa needs these APIs to function, when installing Ketesa, the playbook **automatically** exposes the Synapse Admin API publicly for you. Depending on the homeserver implementation you're using (Synapse, Dendrite), this is equivalent to:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:42
-msgid "for [Synapse](./configuring-playbook-synapse.md) (our default homeserver implementation): `matrix_synapse_container_labels_public_client_synapse_admin_api_enabled: true`"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:43
-msgid "for [Dendrite](./configuring-playbook-dendrite.md): `matrix_dendrite_container_labels_public_client_synapse_admin_api_enabled: true`"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:45
-msgid "By default, Ketesa installation will be [restricted to only work with one homeserver](https://github.com/etkecc/ketesa/blob/main/README.md#restricting-available-homeserver) — the one managed by the playbook. To adjust these restrictions, tweak the `matrix_ketesa_config_restrictBaseUrl` variable."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:47
-msgid "Adjusting the Ketesa URL (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:49
-msgid "By tweaking the `matrix_ketesa_hostname` and `matrix_ketesa_path_prefix` variables, you can easily make the service available at a **different hostname and/or path** than the default one."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:51
-msgid "We recommend updating the path prefix to `/ketesa` to align with the new branding, while the default `/synapse-admin` is kept for backward compatibility:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:57
-msgid "Or to change the hostname entirely:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:65
-msgid "If you've changed the default hostname, you may need to create a CNAME record for the Ketesa domain (`admin.example.com`), which targets `matrix.example.com`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:67
-msgid "When setting, replace `example.com` with your own."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:69
-msgid "Extending the configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:71
-msgid "There are some additional things you may wish to configure about the component."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:73
-msgid "Take a look at:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:75
-msgid "`roles/custom/matrix-ketesa/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_ketesa_configuration_extension_json` variable"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:77
-msgid "Installing"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:79
-msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:86
-msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:88
-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. Note these shortcuts run the `ensure-matrix-users-created` tag too."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:90
-msgid "Usage"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:92
-msgid "After installation, Ketesa will be accessible at: `https://matrix.example.com/synapse-admin/` (or `/ketesa/` if you updated the path prefix as recommended)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:94
-msgid "To use Ketesa, you need to have [registered at least one administrator account](registering-users.md) on your server."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:96
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:98
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-ketesa`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-ketesa.md:100
-msgid "If you have questions, you can join this community room and feel free to ask: [#ketesa:etke.cc](https://matrix.to/#/#ketesa:etke.cc)"
-msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-matrix-authentication-service.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,134 +18,150 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:8
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:1
 msgid "Setting up Matrix Authentication Service (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:10
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:3
 msgid "The playbook can install and configure [Matrix Authentication Service](https://github.com/element-hq/matrix-authentication-service/) (MAS) — a service operating alongside your existing [Synapse](./configuring-playbook-synapse.md) homeserver and providing [better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:12
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:5
 msgid "Matrix Authentication Service is an implementation of [MSC3861: Next-generation auth for Matrix, based on OAuth 2.0/OIDC](https://github.com/matrix-org/matrix-spec-proposals/pull/3861) and still work in progress, tracked at the [areweoidcyet.com](https://areweoidcyet.com/) website."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:14
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:7
 msgid "**Before going through with starting to use Matrix Authentication Service**, make sure to read:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:16
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:9
 msgid "the [Reasons to use Matrix Authentication Service](#reasons-to-use-matrix-authentication-service) section below"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:17
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:10
 msgid "the [Expectations](#expectations) section below"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:18
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:11
 msgid "the [FAQ section on areweoidcyet.com](https://areweoidcyet.com/#faqs)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:20
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:13
 msgid "**If you've already been using Synapse** and have user accounts in its database, you can [migrate to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:22
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:15
 msgid "Reasons to use Matrix Authentication Service"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:24
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:17
 msgid "You may be wondering whether you should make the switch to Matrix Authentication Service (MAS) or keep using your existing authentication flow via Synapse (password-based or [OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)-enabled)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:26
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:19
 msgid "Matrix Authentication Service is **still an experimental service** and **not a default** for this Ansible playbook."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:28
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:21
 msgid "The [Expectations](#expectations) section contains a list of what works and what doesn't (**some services don't work with MAS yet**), as well as the **relative irreversability** of the migration process."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:30
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:23
 msgid "Below, we'll try to **highlight some potential reasons for switching** to Matrix Authentication Service:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:32
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:25
 msgid "To use SSO in [Element X](https://element.io/blog/element-x-ignition/). The old [Synapse OIDC](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) login flow is only supported in old Element clients and will not be supported in Element X. Element X will only support the new SSO-based login flow provided by MAS, so if you want to use SSO with Element X, you will need to switch to MAS."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:34
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:27
 msgid "To help drive adoption of the \"Next-generation auth for Matrix\" by switching to what's ultimately coming anyway"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:36
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:29
 msgid "To help discover (and potentially fix) MAS integration issues with this Ansible playbook"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:38
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:31
 msgid "To help discover (and potentially fix) MAS integration issues with various other Matrix components (bridges, bots, clients, etc.)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:40
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:33
 msgid "To reap some of the security benefits that Matrix Authentication Service offers, as outlined in the [Better authentication, session management and permissions in Matrix](https://matrix.org/blog/2023/09/better-auth/) article."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:42
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:35
 msgid "Prerequisites"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:44
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:37
-msgid "⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating with Matrix Authentication Service yet."
+msgid "⚠️ the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default for this playbook). Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:46
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:39
+msgid "⚠️ **email sending** configured (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:41
 msgid "❌ **disabling all password providers** for Synapse (things like [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc.) More details about this are available in the [Expectations](#expectations) section below."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:48
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:43
 msgid "Expectations"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:50
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:45
 msgid "This section details what you can expect when switching to the Matrix Authentication Service (MAS)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:52
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:47
 msgid "❌ **Synapse password providers will need to be disabled**. You can no longer use [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc. When the authentication flow is handled by MAS (not by Synapse anymore), it doesn't make sense to extend the Synapse authentication flow with additional modules. Many bridges used to rely on shared-secret-auth for doing double-puppeting (impersonating other users), but most (at least the mautrix bridges) nowadays use [Appservice Double Puppet](./configuring-playbook-appservice-double-puppet.md) as a better alternative. Older/maintained bridges may still rely on shared-secret-auth, as do other services like [matrix-corporal](./configuring-playbook-matrix-corporal.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:54
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:49
-msgid "✅ **[Ketesa](./configuring-playbook-ketesa.md) has full MAS integration**. Ketesa supports OIDC auth, user management, all session types (browser, OAuth2, compatibility), linked email addresses, upstream OAuth provider links, MAS policy data, and user creation through MAS. It is the recommended tool for managing homeservers running MAS."
+msgid "❌ Certain **tools like [synapse-admin](./configuring-playbook-synapse-admin.md) do not have full compatibility with MAS yet**. synapse-admin already supports [login with access token](https://github.com/etkecc/synapse-admin/pull/58), browsing users (which Synapse will internally fetch from MAS) and updating user avatars. However, editing users (passwords, etc.) now needs to happen directly against MAS using the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html), which synapse-admin cannot interact with yet."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:56
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:51
 msgid "❌ **Some services experience issues when authenticating via MAS**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:58
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:53
-msgid "[Reminder bot](configuring-playbook-bot-matrix-reminder-bot.md) seems to be losing some of its state on each restart and may reschedule old reminders once again"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:60
 msgid "[Postmoogle](./configuring-playbook-bridge-postmoogle.md) works the first time around, but it consistently fails after restarting:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:62
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:55
 msgid "cannot initialize matrix bot error=\"olm account is marked as shared, keys seem to have disappeared from the server\""
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:64
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:57
+msgid "[matrix-reminder-bot](./configuring-playbook-bot-matrix-reminder-bot.md) fails to start (see [element-hq/matrix-authentication-service#3439](https://github.com/element-hq/matrix-authentication-service/issues/3439))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:58
+msgid "Other services may be similarly affected. This list is not exhaustive."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:60
 msgid "❌ **Encrypted appservices** do not work yet (related to [MSC4190](https://github.com/matrix-org/matrix-spec-proposals/pull/4190) and [PR 17705 for Synapse](https://github.com/element-hq/synapse/pull/17705)), so all bridges/bots that rely on encryption will fail to start (see [this issue](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3658) for Hookshot). You can use these bridges/bots only if you **keep end-to-bridge encryption disabled** (which is the default setting)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:66
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:62
+msgid "⚠️ **You will need to have email sending configured** (see [Adjusting email-sending settings](./configuring-playbook-email.md)), because **Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user** going through the new SSO-based login flow. It's also possible to [work around email deliverability issues](#working-around-email-deliverability-issues) if your email configuration is not working."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:64
 msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) is **possible**, but requires **some playbook-assisted manual work**. Migration is **reversible with no or minor issues if done quickly enough**, but as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
 msgstr ""
 
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:66
+msgid "⚠️ [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) does not currently seem to preserve the \"admin\" flag for users (as found in the Synapse database). All users are imported as non-admin — see [element-hq/matrix-authentication-service#3440](https://github.com/element-hq/matrix-authentication-service/issues/3440). You may need update the Matrix Authentication Service's database manually and adjust the `can_request_admin` column in the `users` table to `true` for users that need to be administrators (e.g. `UPDATE users SET can_request_admin = true WHERE username = 'someone';`)"
+msgstr ""
+
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:68
-msgid "⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependent on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch."
+msgid "⚠️ Delegating user authentication to MAS causes **your Synapse server to be completely dependant on one more service** for its operations. MAS is quick & lightweight and should be stable enough already, but this is something to keep in mind when making the switch."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:70
@@ -165,7 +181,7 @@ msgid "✅ Various clients ([Cinny](./configuring-playbook-client-cinny.md), [El
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:78
-msgid "✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work"
+msgid "✅ The **old login flow** (called `m.login.password`) **will still continue to work**, so clients (old Element Web, etc.) and bridges/bots that don't support the new OIDC-based login flow will still work. Going through the old login flow does not require users to have a verified email address, as [is the case](https://github.com/element-hq/matrix-authentication-service/issues/1505) for the new SSO-based login flow."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:80
@@ -193,7 +209,7 @@ msgid "Existing homeserver"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:92
-msgid "Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating with Matrix Authentication Service yet."
+msgid "Other homeserver implementations ([Dendrite](./configuring-playbook-dendrite.md), [Conduit](./configuring-playbook-conduit.md), etc.) do not support integrating wtih Matrix Authentication Service yet."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:94
@@ -281,346 +297,326 @@ msgstr ""
 msgid "The playbook exposes a `matrix_authentication_service_config_upstream_oauth2_providers` variable for controlling this setting."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:273
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:269
 msgid "💡 Refer to the [`upstream_oauth2.providers` setting](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#upstream_oauth2providers) for the most up-to-date schema and example for providers. The value shown above here may be out of date."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:275
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:271
 msgid "⚠️ The syntax for existing [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on) is slightly different, so you will need to adjust your configuration when switching from Synapse OIDC to MAS upstream OAuth2."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:277
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:273
 msgid "⚠️ When [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) which contains OIDC-sourced users, you will need to:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:279
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:275
 msgid "[Configure upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:280
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:276
 msgid "go through the [migrating an existing homeserver](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) process"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:281
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:277
 msgid "remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:283
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:279
-msgid "Extending the configuration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:285
-msgid "There are some additional things you may wish to configure about the component."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:287
-msgid "Take a look at:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:289
-msgid "`roles/custom/matrix-authentication-service/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:290
-msgid "`roles/custom/matrix-authentication-service/templates/config.yaml.j2` for the component's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_authentication_service_configuration_extension_yaml` variable"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:292
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:294
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:281
 msgid "Now that you've [adjusted the playbook configuration](#adjusting-the-playbook-configuration) and [your DNS records](#adjusting-dns-records), you can run the playbook with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:301
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:288
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:303
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:290
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:305
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:292
 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. Note these shortcuts run the `ensure-matrix-users-created` tag too."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:307
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:294
 msgid "If you're in the process of migrating an existing Synapse homeserver to MAS, you should now follow the rest of the steps in the [Migrating an existing Synapse homeserver to Matrix Authentication Service](#migrating-an-existing-synapse-homeserver-to-matrix-authentication-service) guide."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:309
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:296
 msgid "💡 After installation, you should [verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:311
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:298
 msgid "Migrating an existing Synapse homeserver to Matrix Authentication Service"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:313
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:300
 msgid "Our migration guide is loosely based on the upstream [Migrating an existing homeserver](https://element-hq.github.io/matrix-authentication-service/setup/migration.html) guide."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:315
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:302
-msgid "Migration is done via a sub-command called `syn2mas`, which the playbook could run for you (in a container)."
+msgid "Migration is done via a tool called `syn2mas`, which the playbook could run for you (in a container)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:317
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:304
 msgid "The installation + migration steps are like this:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:319
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:306
 msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) to **disable the integration between the homeserver and MAS**. This is done by **uncommenting** the `matrix_authentication_service_migration_in_progress: true` line."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:321
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:308
 msgid "Perform the initial [installation](#installing). At this point:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:323
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:310
 msgid "Matrix Authentication Service will be installed. Its database will be empty, so it cannot validate existing access tokens or authentication users yet."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:325
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:312
 msgid "The homeserver will still continue to use its local database for validating existing access tokens."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:327
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:314
 msgid "Various [compatibility layer URLs](https://element-hq.github.io/matrix-authentication-service/setup/homeserver.html#set-up-the-compatibility-layer) are not yet installed. New login sessions will still be forwarded to the homeserver, which is capable of completing them."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:329
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:316
 msgid "The `matrix-user-creator` role would be suppressed, so that it doesn't automatically attempt to create users (for bots, etc.) in the MAS database. These user accounts likely already exist in Synapse's user database and could be migrated over (via syn2mas, as per the steps below), so creating them in the MAS database would have been unnecessary and potentially problematic (conflicts during the syn2mas migration)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:331
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:318
-msgid "Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration command does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
+msgid "Consider taking a full [backup of your Postgres database](./maintenance-postgres.md#backing-up-postgresql). This is done just in case. The **syn2mas migration tool does not delete any data**, so it should be possible to revert to your previous setup by merely disabling MAS and re-running the playbook (no need to restore a Postgres backup). However, do note that as users start logging in (creating new login sessions) via the new MAS setup, disabling MAS and reverting back to the Synapse user database will cause these new sessions to break."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:333
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:320
 msgid "[Migrate your data from Synapse to Matrix Authentication Service using syn2mas](#migrate-your-data-from-synapse-to-matrix-authentication-service-using-syn2mas)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:335
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:322
 msgid "[Adjust your configuration](#adjusting-the-playbook-configuration) again, to:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:337
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:324
 msgid "remove the `matrix_authentication_service_migration_in_progress: false` line"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:339
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:326
 msgid "if you had been using [OIDC providers configured in Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), remove all Synapse OIDC-related configuration (`matrix_synapse_oidc_*`) to prevent it being in conflict with the MAS OIDC configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:341
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:328
 msgid "Perform the [installation](#installing) again. At this point:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:343
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:330
 msgid "The homeserver will start delegating authentication to MAS."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:345
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:332
 msgid "The compatibility layer URLs will be installed. New login sessions will be completed by MAS."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:347
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:334
 msgid "[Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:349
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:336
 msgid "Migrate your data from Synapse to Matrix Authentication Service using syn2mas"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:351
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:338
+msgid "We **don't** ask you to [run the `syn2mas` migration advisor command](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#run-the-migration-advisor), because it only gives you the green light if your Synapse configuration (`homeserver.yaml`) is configured in a way that's compatible with MAS (delegating authentication to MAS; disabling Synapse's password config; etc.). Until we migrate your data with the `syn2mas` tool, we intentionally avoid doing these changes to allow existing user sessions to work."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:340
 msgid "You can invoke the `syn2mas` tool via the playbook by running the playbook's `matrix-authentication-service-mas-cli-syn2mas` tag. We recommend first doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:353
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:342
 msgid "Configuring syn2mas"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:355
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:344
 msgid "If you're using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on), you will need to [Configuring upstream OIDC provider mapping for syn2mas](#configuring-upstream-oidc-provider-mapping-for-syn2mas)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:357
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:346
 msgid "If you only have local (non-OIDC) users in your Synapse database, you can likely run `syn2mas` as-is (without doing additional configuration changes)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:359
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:348
 msgid "When you're done with potentially configuring `syn2mas`, proceed to doing a [dry-run](#performing-a-syn2mas-dry-run) and then a [real migration](#performing-a-real-syn2mas-migration)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:361
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:350
 msgid "Configuring upstream OIDC provider mapping for syn2mas"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:363
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:352
-msgid "Since Matrix Authentication Service v0.16.0 (which replaced the standalone `syn2mas` tool with a `mas-cli syn2mas` sub-command), OIDC configuration (mapping from your old OIDC configuration to your new one, etc) is meant to be configured in the Matrix Authentication Service configuration (via `matrix_authentication_service_config_upstream_oauth2_providers`) as a `synapse_idp_id` property for each provider."
+msgid "If you have existing OIDC users in your Synapse user database (which will be the case if when using [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)), you may need to pass an additional `--upstreamProviderMapping` argument to the `syn2mas` tool to tell it which provider (on the Synapse side) maps to which other provider on the MAS side."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:365
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:354
-msgid "You can refer to the [Map any upstream SSO providers](https://element-hq.github.io/matrix-authentication-service/setup/migration.html#map-any-upstream-sso-providers) section of the MAS documentation for figuring out how to set the `synapse_idp_id` value in `matrix_authentication_service_config_upstream_oauth2_providers` correctly."
+msgid "If you don't do this, `syn2mas` would report errors like this one:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:367
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:356
-msgid "Performing a syn2mas dry-run"
+msgid "[FATAL] migrate - [Failed to import external id 4264b0f0-4f11-4ddd-aedb-b500e4d07c25 with oidc-keycloak for user @alice:example.com: Error: Unknown upstream provider oidc-keycloak]"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:369
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:358
-msgid "Having [configured syn2mas](#configuring-syn2mas), we recommend doing a [dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to verify that everything will work out as expected."
+msgid "Below is an example situation and a guide for how to solve it."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:371
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:360
-msgid "A dry-run would not cause downtime, because it avoids stopping Synapse."
+msgid "If in `matrix_synapse_oidc_providers` your provider `idp_id` is (was) named `keycloak`, in the Synapse database users would be associated with the `oidc-keycloak` provider (note the `oidc-` prefix that was added automatically by Synapse to your `idp_id` value)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:362
+msgid "The same OIDC provider may have an `id` of `01HFVBY12TMNTYTBV8W921M5FA` on the MAS side, as defined in `matrix_authentication_service_config_upstream_oauth2_providers` (see the [Upstream OAuth2 configuration](#upstream-oauth2-configuration) section above)."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:364
+msgid "To tell `syn2mas` how the Synapse-configured OIDC provider maps to the new MAS-configured OIDC provider, add this additional configuration to your `vars.yml` file:"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:373
-msgid "To perform a dry-run, run:"
+msgid "Performing a syn2mas dry-run"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:375
+msgid "Having [configured syn2mas](#configuring-syn2mas), we recommend doing a [dry-run](https://en.wikipedia.org/wiki/Dry_run_(testing)) first to verify that everything will work out as expected."
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:377
+msgid "A dry-run would not cause downtime, because it avoids stopping Synapse."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:379
-msgid "Observe the command output (especially the last line of the the syn2mas output). If you are confident that the migration will work out as expected, you can proceed with a [real migration](#performing-a-real-syn2mas-migration)."
+msgid "To perform a dry-run, run:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:381
-msgid "Performing a real syn2mas migration"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:383
-msgid "Before performing a real migration make sure:"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:385
-msgid "you've familiarized yourself with the [expectations](#expectations)"
+msgid "Observe the command output (especially the last line of the the syn2mas output). If you are confident that the migration will work out as expected, you can proceed with a [real migration](#performing-a-real-syn2mas-migration)."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:387
-msgid "you've performed a Postgres backup, just in case"
+msgid "Performing a real syn2mas migration"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:389
-msgid "you're aware of the irreversibility of the migration process without disruption after users have created new login sessions via the new MAS setup"
+msgid "Before performing a real migration make sure:"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:391
-msgid "you've [configured syn2mas](#configuring-syn2mas), especially if you've used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)"
+msgid "you've familiarized yourself with the [expectations](#expectations)"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:393
-msgid "you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and don't see any issues in its output"
+msgid "you've performed a Postgres backup, just in case"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:395
-msgid "To perform a real migration, run the `matrix-authentication-service-mas-cli-syn2mas` tag **without** the `matrix_authentication_service_syn2mas_migrate_dry_run` variable:"
+msgid "you're aware of the irreversibility of the migration process without disruption after users have created new login sessions via the new MAS setup"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:397
+msgid "you've [configured syn2mas](#configuring-syn2mas), especially if you've used [OIDC with Synapse](./configuring-playbook-synapse.md#synapse--openid-connect-for-single-sign-on)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:399
+msgid "you've performed a [syn2mas dry-run](#performing-a-syn2mas-dry-run) and don't see any issues in its output"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:401
-msgid "After `syn2mas` completes, Synapse will intentionally remain stopped to avoid new registrations or other authentication changes from being accepted before the migration is completed. Continue with the next steps in this guide before re-running the installation."
+msgid "To perform a real migration, run the `matrix-authentication-service-mas-cli-syn2mas` tag **without** the `matrix_authentication_service_syn2mas_migrate_dry_run` variable:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:403
-msgid "Having performed a `syn2mas` migration once, trying to do it again will report errors (e.g. \"Error: The MAS database is not empty: rows found in at least `users`. Please drop and recreate the database, then try again.\")."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:405
-msgid "Verify that Matrix Authentication Service is installed correctly"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:407
-msgid "After [installation](#installing), run the `doctor` subcommand of the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) to verify that MAS is installed correctly."
+msgid "Having performed a `syn2mas` migration once, trying to do it again will report errors for users that were already migrated (e.g. \"Error: Unknown upstream provider oauth-delegated\")."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:409
-msgid "You can do it:"
+msgid "Verify that Matrix Authentication Service is installed correctly"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:411
-msgid "either via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`"
+msgid "After [installation](#installing), run the `doctor` subcommand of the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) to verify that MAS is installed correctly."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:413
-msgid "or by running the `mas-cli` script on the server (which invokes the `mas-cli` tool inside a container): `/matrix/matrix-authentication-service/bin/mas-cli doctor`"
+msgid "You can do it:"
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:415
+msgid "either via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag: `just run-tags matrix-authentication-service-mas-cli-doctor`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:417
+msgid "or by running the `mas-cli` script on the server (which invokes the `mas-cli` tool inside a container): `/matrix/matrix-authentication-service/bin/mas-cli doctor`"
+msgstr ""
+
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:419
 msgid "If successful, you should see some output that looks like this:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:427
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:431
-msgid "Usage"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:429
 msgid "Management"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:431
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:433
 msgid "You can use the [`mas-cli` command-line tool](https://element-hq.github.io/matrix-authentication-service/reference/cli/index.html) (exposed via the `/matrix/matrix-authentication-service/bin/mas-cli` script) to perform administrative tasks against MAS."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:433
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:435
 msgid "This documentation page already mentions:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:435
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:437
 msgid "the `mas-cli doctor` sub-command in the [Verify that Matrix Authentication Service is installed correctly](#verify-that-matrix-authentication-service-is-installed-correctly) section, which you can run via the CLI and via the Ansible playbook's `matrix-authentication-service-mas-cli-doctor` tag"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:437
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:439
 msgid "the `mas-cli manage register-user` sub-command in the [Registering users](./registering-users.md) documentation"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:439
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:441
 msgid "There are other sub-commands available. Run `/matrix/matrix-authentication-service/bin/mas-cli` to get an overview."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:441
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:443
 msgid "User registration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:443
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:445
 msgid "After Matrix Authentication Service is [installed](#installing), users need to be managed there (unless you're managing them in an [upstream OAuth2 provider](#upstream-oauth2-configuration))."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:445
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:447
 msgid "You can register users new users as described in the [Registering users](./registering-users.md) documentation (via `mas-cli manage register-user` or the Ansible playbook's `register-user` tag)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:447
+#: ../../../docs/configuring-playbook-matrix-authentication-service.md:449
 msgid "Working around email deliverability issues"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:449
-msgid "Matrix Authentication Service only sends emails when:"
-msgstr ""
-
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:451
-msgid "it verifies email addresses for users who are self-registering with a password"
+msgid "Because Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user, you may need to work around email deliverability issues if [your email-sending configuration](./configuring-playbook-email.md) is not working."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:453
-msgid "a user tries to add an email to their account"
+msgid "Matrix Authentication Service attempts to verify email addresses by sending a verification email to the address specified by the user whenever they log in to an account without a verified email address."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:455
-msgid "If Matrix Authentication Service tries to send an email and it fails because [your email-sending configuration](./configuring-playbook-email.md) is not working, you may need to work around email deliverability."
+msgid "If email delivery is not working, **you can retrieve the email configuration code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`)."
 msgstr ""
 
 #: ../../../docs/configuring-playbook-matrix-authentication-service.md:457
-msgid "If email delivery is not working, **you can retrieve the email verification code from the Matrix Authentication Service's logs** (`journalctl -fu matrix-authentication-service`)."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:459
 msgid "Alternatively, you can use the [`mas-cli` management tool](#management) to manually verify email addresses for users. Example: `/matrix/matrix-authentication-service/bin/mas-cli manage verify-email some.username email@example.com`"
 msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:461
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-matrix-authentication-service.md:463
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-authentication-service`."
-msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-synapse.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,305 +18,261 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook-synapse.md:12
+#: ../../../docs/configuring-playbook-synapse.md:1
 msgid "Configuring Synapse (optional)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:14
+#: ../../../docs/configuring-playbook-synapse.md:3
 msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, so that it works for the general case. If that's okay, you can skip this document."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:16
+#: ../../../docs/configuring-playbook-synapse.md:5
-msgid "💡 See this page for details about maintaining Synapse: [Synapse maintenance](maintenance-synapse.md)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:18
 msgid "Adjusting the playbook configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:20
+#: ../../../docs/configuring-playbook-synapse.md:7
 msgid "Load balancing with workers"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:22
+#: ../../../docs/configuring-playbook-synapse.md:9
 msgid "To have Synapse gracefully handle thousands of users, worker support should be enabled. It factors out some homeserver tasks and spreads the load of incoming client and server-to-server traffic between multiple processes. More information can be found in the [official Synapse workers documentation](https://github.com/element-hq/synapse/blob/master/docs/workers.md) and [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:24
+#: ../../../docs/configuring-playbook-synapse.md:11
 msgid "To enable Synapse worker support, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:32
+#: ../../../docs/configuring-playbook-synapse.md:19
 msgid "By default, this enables the `one-of-each` [worker preset](#worker-presets), but you may wish to use another preset or [control the number of worker instances](#controlling-the-number-of-worker-instances)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:34
+#: ../../../docs/configuring-playbook-synapse.md:21
 msgid "Worker presets"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:36
+#: ../../../docs/configuring-playbook-synapse.md:23
 msgid "We support a few configuration presets (`matrix_synapse_workers_preset: one-of-each` being the default configuration right now):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:38
+#: ../../../docs/configuring-playbook-synapse.md:25
 msgid "(federation-only) `little-federation-helper` — a very minimal worker configuration to improve federation performance"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:39
+#: ../../../docs/configuring-playbook-synapse.md:26
 msgid "(generic) `one-of-each` — defaults to one worker of each supported type — no smart routing, just generic workers"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:40
+#: ../../../docs/configuring-playbook-synapse.md:27
 msgid "(specialized) `specialized-workers` — defaults to one worker of each supported type, but disables generic workers and uses [specialized workers](#specialized-workers) instead"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:42
+#: ../../../docs/configuring-playbook-synapse.md:29
 msgid "These presets represent a few common configurations. There are many worker types which can be mixed and matched based on your needs."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:44
+#: ../../../docs/configuring-playbook-synapse.md:31
 msgid "Generic workers"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:46
+#: ../../../docs/configuring-playbook-synapse.md:33
 msgid "Previously, the playbook only supported the most basic type of load-balancing. We call it **generic load-balancing** below, because incoming HTTP requests are sent to a generic worker. Load-balancing was done based on the requestor's IP address. This is simple, but not necessarily optimal. If you're accessing your account from multiple IP addresses (e.g. your mobile phone being on a different network than your PC), these separate requests may potentially be routed to different workers, each of which would need to cache roughly the same data."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:48
+#: ../../../docs/configuring-playbook-synapse.md:35
 msgid "This is **still the default load-balancing method (preset) used by the playbook**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:50
+#: ../../../docs/configuring-playbook-synapse.md:37
 msgid "To use generic load-balancing, do not specify `matrix_synapse_workers_preset` to make it use the default value (`one-of-each`), or better yet — explicitly set it as `one-of-each`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:52
+#: ../../../docs/configuring-playbook-synapse.md:39
 msgid "You may also consider [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:54
+#: ../../../docs/configuring-playbook-synapse.md:41
 msgid "Specialized workers"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:56
+#: ../../../docs/configuring-playbook-synapse.md:43
-msgid "The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requester's IP address, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** — the access token (username) of the requester and/or on the resource (room, etc.) being requested."
+msgid "The playbook now supports a smarter **specialized load-balancing** inspired by [Tom Foster](https://github.com/tcpipuk)'s [Synapse homeserver guide](https://tcpipuk.github.io/synapse/index.html). Instead of routing requests to one or more [generic workers](#generic-workers) based only on the requestor's IP adddress, specialized load-balancing routes to **4 different types of specialized workers** based on **smarter criteria** — the access token (username) of the requestor and/or on the resource (room, etc.) being requested."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:58
+#: ../../../docs/configuring-playbook-synapse.md:45
 msgid "The playbook supports these **4 types** of specialized workers:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:60
+#: ../../../docs/configuring-playbook-synapse.md:47
 msgid "Room workers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) & [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs dedicated to handling specific rooms"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:61
+#: ../../../docs/configuring-playbook-synapse.md:48
 msgid "Sync workers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs related to synchronization (most notably [the `/sync` endpoint](https://spec.matrix.org/v1.9/client-server-api/#get_matrixclientv3sync))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:62
+#: ../../../docs/configuring-playbook-synapse.md:49
 msgid "Client readers — handles various [Client-Server](https://spec.matrix.org/v1.9/client-server-api/) APIs which are not for specific rooms (handled by **room workers**) or for synchronization (handled by **sync workers**)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:63
+#: ../../../docs/configuring-playbook-synapse.md:50
 msgid "Federation readers — handles various [Federation](https://spec.matrix.org/v1.9/server-server-api) APIs which are not for specific rooms (handled by **room workers**)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:65
+#: ../../../docs/configuring-playbook-synapse.md:52
 msgid "To use specialized load-balancing, consider enabling the `specialized-workers` [worker preset](#worker-presets) and potentially [tweaking the number of workers of each type](#controlling-the-number-of-worker-instances) from the default (one of each)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:67
+#: ../../../docs/configuring-playbook-synapse.md:54
 msgid "Controlling the number of worker instances"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:69
+#: ../../../docs/configuring-playbook-synapse.md:56
 msgid "If you'd like more customization power, you can start with one of the [worker presets](#worker-presets) and then tweak various `matrix_synapse_workers_*_count` variables manually."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:71
+#: ../../../docs/configuring-playbook-synapse.md:58
 msgid "To find what variables are available for you to override in your own `vars.yml` configuration file, see the [`defaults/main.yml` file for the `matrix-synapse` Ansible role](../roles/custom/matrix-synapse/defaults/main.yml)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:73
+#: ../../../docs/configuring-playbook-synapse.md:60
 msgid "The only thing you **cannot** do is mix [generic workers](#generic-workers) and [specialized workers](#specialized-workers)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:75
+#: ../../../docs/configuring-playbook-synapse.md:62
 msgid "Effect of enabling workers on the rest of your server"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:77
+#: ../../../docs/configuring-playbook-synapse.md:64
 msgid "When Synapse workers are enabled, the integrated [Postgres database is tuned](maintenance-postgres.md#tuning-postgresql), so that the maximum number of Postgres connections are increased from `200` to `500`. If you need to decrease or increase the number of maximum Postgres connections further, use the `postgres_max_connections` variable."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:79
+#: ../../../docs/configuring-playbook-synapse.md:66
-msgid "The `matrix-synapse` role also manages the `matrix-synapse-reverse-proxy-companion` component for load-balancing with workers. This component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly."
+msgid "A separate Ansible role (`matrix-synapse-reverse-proxy-companion`) and component handles load-balancing for workers. This role/component is automatically enabled when you enable workers. Make sure to use the `setup-all` tag (not `install-all`!) during the playbook's [installation](./installing.md) process, especially if you're disabling workers, so that components may be installed/uninstalled correctly."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:81
+#: ../../../docs/configuring-playbook-synapse.md:68
 msgid "In case any problems occur, make sure to have a look at the [list of synapse issues about workers](https://github.com/element-hq/synapse/issues?q=workers+in%3Atitle) and your `journalctl --unit 'matrix-*'`."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:83
+#: ../../../docs/configuring-playbook-synapse.md:70
-msgid "Limit joining heavy rooms on constrained hosts"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:85
-msgid "If your server is underpowered, joining heavy rooms can cause Synapse to consume a lot of resources and be unavailable for long (while it catches up)."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:87
-msgid "To avoid this, Synapse can be configured to reject joins for remote rooms that are too complex before users enter them."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:89
-msgid "Complexity is computed as `current_state_events / 500` (Synapse state event count for current room state). When the resulting value is higher than `matrix_synapse_limit_remote_rooms_complexity` and `matrix_synapse_limit_remote_rooms_enabled` is `true`, Synapse blocks joining the room."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:91
-msgid "We recommend using this as a guardrail on low-resource servers:"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:106
 msgid "Synapse + OpenID Connect for Single-Sign-On"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:108
+#: ../../../docs/configuring-playbook-synapse.md:72
 msgid "💡 An alternative to setting up OIDC in Synapse is to use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) (MAS). Newer clients (like Element X) only support SSO-based authentication via MAS and not via the legacy Synapse OIDC setup described below. That said, MAS is still a new experimental service which comes with its own downsides. Consult its documentation to learn if it will be a good fit for your deployment."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:110
+#: ../../../docs/configuring-playbook-synapse.md:74
 msgid "If you'd like to use OpenID Connect authentication with Synapse, you'll need some additional configuration."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:112
+#: ../../../docs/configuring-playbook-synapse.md:76
 msgid "This example configuration is for [keycloak](https://www.keycloak.org/), an opensource Identity Provider maintained by Red Hat."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:114
+#: ../../../docs/configuring-playbook-synapse.md:78
 msgid "For more detailed documentation on available options and how to setup keycloak, see the [Synapse documentation on OpenID Connect with keycloak](https://github.com/element-hq/synapse/blob/develop/docs/openid.md#keycloak)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:116
+#: ../../../docs/configuring-playbook-synapse.md:80
-#, python-format, python-brace-format
+#, python-format
 msgid "In case you encounter errors regarding the parsing of the variables, you can try to add `{% raw %}` and `{% endraw %}` blocks around them. For example ;"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:137
+#: ../../../docs/configuring-playbook-synapse.md:101
 msgid "Customizing templates"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:139
+#: ../../../docs/configuring-playbook-synapse.md:103
 msgid "[Templates](https://github.com/element-hq/synapse/blob/develop/docs/templates.md) are used by Synapse for showing **certain web pages** handled by the server, as well as for **email notifications**."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:141
+#: ../../../docs/configuring-playbook-synapse.md:105
 msgid "This playbook allows you to customize the default templates (see the [`synapse/res/templates` directory](https://github.com/element-hq/synapse/tree/develop/synapse/res/templates))."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:143
+#: ../../../docs/configuring-playbook-synapse.md:107
 msgid "If template customization is enabled, the playbook will build a custom container image based on the official one."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:145
+#: ../../../docs/configuring-playbook-synapse.md:109
 msgid "Your custom templates need to live in a public or private git repository. This repository will be cloned during Synapse image customization (during the playbook run)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:147
+#: ../../../docs/configuring-playbook-synapse.md:111
 msgid "To enable template customizations, add the following configuration to your `vars.yml` file (adapt to your needs):"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:173
+#: ../../../docs/configuring-playbook-synapse.md:137
 msgid "As mentioned in Synapse's Templates documentation, Synapse will fall back to its own templates if a template is not found in that directory. Due to this, it's recommended to only store and maintain template files in your repository if you need to make custom changes. Other files (which you don't need to change), should not be duplicated, so that you don't need to worry about getting out-of-sync with the original Synapse templates."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:175
+#: ../../../docs/configuring-playbook-synapse.md:139
 msgid "Extending the configuration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:177
+#: ../../../docs/configuring-playbook-synapse.md:141
 msgid "There are some additional things you may wish to configure about the server."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:179
+#: ../../../docs/configuring-playbook-synapse.md:143
 msgid "Take a look at:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:181
+#: ../../../docs/configuring-playbook-synapse.md:145
 msgid "`roles/custom/matrix-synapse/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:182
+#: ../../../docs/configuring-playbook-synapse.md:146
 msgid "`roles/custom/matrix-synapse/templates/synapse/homeserver.yaml.j2` for the server's default configuration. You can override settings (even those that don't have dedicated playbook variables) using the `matrix_synapse_configuration_extension_yaml` variable"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:184
+#: ../../../docs/configuring-playbook-synapse.md:148
 msgid "Installing"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:186
+#: ../../../docs/configuring-playbook-synapse.md:150
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:193
+#: ../../../docs/configuring-playbook-synapse.md:157
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:195
+#: ../../../docs/configuring-playbook-synapse.md:159
 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. Note these shortcuts run the `ensure-matrix-users-created` tag too."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:197
+#: ../../../docs/configuring-playbook-synapse.md:161
 msgid "Usage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:199
+#: ../../../docs/configuring-playbook-synapse.md:163
-msgid "Ketesa"
+msgid "Synapse Admin"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:201
+#: ../../../docs/configuring-playbook-synapse.md:165
-msgid "[Ketesa](configuring-playbook-ketesa.md) is a fully-featured web UI for administrating your homeserver — managing users, rooms, media, sessions, and more."
+msgid "With [Synapse Admin](configuring-playbook-synapse-admin.md), certain Synapse administration tasks (managing users and rooms, etc.) can be performed via a web user-interace."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:203
+#: ../../../docs/configuring-playbook-synapse.md:167
-msgid "The playbook can install and configure Ketesa for you. For details about it, see [this page](configuring-playbook-ketesa.md)."
+msgid "The playbook can install and configure Synapse Admin for you. For details about it, see [this page](configuring-playbook-synapse-admin.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:205
+#: ../../../docs/configuring-playbook-synapse.md:169
 msgid "Monitoring Synapse Metrics with Prometheus and Grafana"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:207
+#: ../../../docs/configuring-playbook-synapse.md:171
 msgid "This playbook allows you to enable Synapse metrics, which can provide insight into the performance and activity of Synapse."
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:209
+#: ../../../docs/configuring-playbook-synapse.md:173
-msgid "To enable Synapse runtime metrics, see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md) and [its subsection](configuring-playbook-prometheus-grafana.md#expose-metrics-of-other-services-roles)"
+msgid "To enable Synapse runtime metrics see: [Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook-synapse.md:211
+#: ../../../docs/configuring-playbook-synapse.md:175
 msgid "To enable Synapse usage metrics, see: [Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
 msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:213
-msgid "Troubleshooting"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:215
-msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-synapse`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:217
-msgid "Increase logging verbosity"
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:219
-msgid "Because Synapse is originally very chatty when it comes to logging, we intentionally reduce its [logging level](https://docs.python.org/3/library/logging.html#logging-levels) from `INFO` to `WARNING`."
-msgstr ""
-
-#: ../../../docs/configuring-playbook-synapse.md:221
-msgid "If you'd like to debug an issue or [report a Synapse bug](https://github.com/element-hq/synapse/issues/new/choose) to the developers, it'd be better if you temporarily increase the logging verbosity to `INFO`. To do so, add the following configuration to your `vars.yml` file and re-run the playbook:"
-msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,568 +18,528 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/configuring-playbook.md:17
+#: ../../../docs/configuring-playbook.md:1
 msgid "Configuring the playbook"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:19
+#: ../../../docs/configuring-playbook.md:3
-msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)</sup>"
+msgid "<sup>[Prerequisites](prerequisites.md) > [Configuring your DNS settings](configuring-dns.md) > [Getting the playbook](getting-the-playbook.md) > Configuring the playbook > [Installing](installing.md)</sup>"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:21
+#: ../../../docs/configuring-playbook.md:5
 msgid "If you've configured your DNS records and retrieved the playbook's source code to your computer, you can start configuring the playbook. To do so, follow these steps inside the playbook directory:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:23
+#: ../../../docs/configuring-playbook.md:7
 msgid "create a directory to hold your configuration (`mkdir -p inventory/host_vars/matrix.example.com` where `example.com` is your \"base domain\")"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:25
+#: ../../../docs/configuring-playbook.md:9
 msgid "copy the sample configuration file (`cp examples/vars.yml inventory/host_vars/matrix.example.com/vars.yml`)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:27
+#: ../../../docs/configuring-playbook.md:11
-msgid "edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files (after importing external roles with `just update` into `roles/galaxy`) and see if there's something you'd like to copy over and override in your `vars.yml` configuration file."
+msgid "edit the configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) to your liking. You may also take a look at the various `roles/*/ROLE_NAME_HERE/defaults/main.yml` files and see if there's something you'd like to copy over and override in your `vars.yml` configuration file."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:29
+#: ../../../docs/configuring-playbook.md:13
 msgid "copy the sample inventory hosts file (`cp examples/hosts inventory/hosts`)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:31
+#: ../../../docs/configuring-playbook.md:15
 msgid "edit the inventory hosts file (`inventory/hosts`) to your liking"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:33
+#: ../../../docs/configuring-playbook.md:17
-msgid "(optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system. The `inventory` directory path is ignored via `.gitignore`, so it won't be part of the playbook repository. You can safely create a new git repository inside that directory with `git init`, etc."
+msgid "(optional, advanced) you may wish to keep your `inventory` directory under version control with [git](https://git-scm.com/) or any other version-control system."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:35
+#: ../../../docs/configuring-playbook.md:19
 msgid "(optional, advanced) to run Ansible against multiple servers with different `sudo` credentials, you can copy the sample inventory hosts yaml file for each of your hosts: (`cp examples/host.yml inventory/my_host1.yml` …) and use the [`ansible-all-hosts.sh`](../bin/ansible-all-hosts.sh) script [in the installation step](installing.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:37
+#: ../../../docs/configuring-playbook.md:21
 msgid "For a basic Matrix installation, that's all you need."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:39
+#: ../../../docs/configuring-playbook.md:23
 msgid "For a more custom setup, see the [Other configuration options](#other-configuration-options) below."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:41
+#: ../../../docs/configuring-playbook.md:25
 msgid "[▶️](installing.md) When you're done with all the configuration you'd like to do, continue with [Installing](installing.md)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:43
+#: ../../../docs/configuring-playbook.md:27
 msgid "Other configuration options"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:45
+#: ../../../docs/configuring-playbook.md:29
 msgid "**Note**: some of the roles like one for integrating Etherpad or Jitsi are managed by their own repositories, and the configuration files for them cannot be found locally (in `roles/galaxy`) until those roles are fetched from the upstream projects. Check [requirements.yml](../requirements.yml) for the URLs of those roles."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:47
+#: ../../../docs/configuring-playbook.md:31
 msgid "Core service adjustments"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:49
+#: ../../../docs/configuring-playbook.md:33
 msgid "Homeserver configuration:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:50
+#: ../../../docs/configuring-playbook.md:34
 msgid "[Configuring Synapse](configuring-playbook-synapse.md), if you're going with the default/recommended homeserver implementation"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:52
+#: ../../../docs/configuring-playbook.md:36
 msgid "[Configuring Conduit](configuring-playbook-conduit.md), if you've switched to the [Conduit](https://conduit.rs) homeserver implementation"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:54
+#: ../../../docs/configuring-playbook.md:38
-msgid "[Configuring continuwuity](configuring-playbook-continuwuity.md), if you've switched to the [continuwuity](https://continuwuity.org) homeserver implementation"
+msgid "[Configuring conduwuit](configuring-playbook-conduwuit.md), if you've switched to the [conduwuit](https://conduwuit.puppyirl.gay/) homeserver implementation"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:56
+#: ../../../docs/configuring-playbook.md:40
 msgid "[Configuring Dendrite](configuring-playbook-dendrite.md), if you've switched to the [Dendrite](https://matrix-org.github.io/dendrite) homeserver implementation"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:58
+#: ../../../docs/configuring-playbook.md:42
 msgid "Server components:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:59
+#: ../../../docs/configuring-playbook.md:43
 msgid "[Using an external PostgreSQL server](configuring-playbook-external-postgres.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:61
+#: ../../../docs/configuring-playbook.md:45
 msgid "[Configuring a TURN server](configuring-playbook-turn.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:63
+#: ../../../docs/configuring-playbook.md:47
 msgid "[Configuring the Traefik reverse-proxy](configuring-playbook-traefik.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:65
+#: ../../../docs/configuring-playbook.md:49
 msgid "[Using your own webserver, instead of this playbook's Traefik reverse-proxy](configuring-playbook-own-webserver.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:67
+#: ../../../docs/configuring-playbook.md:51
 msgid "[Adjusting SSL certificate retrieval](configuring-playbook-ssl-certificates.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:69
+#: ../../../docs/configuring-playbook.md:53
 msgid "[Adjusting email-sending settings](configuring-playbook-email.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:71
+#: ../../../docs/configuring-playbook.md:55
+msgid "[Setting up ma1sd Identity Server](configuring-playbook-ma1sd.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:57
 msgid "[Setting up Dynamic DNS](configuring-playbook-dynamic-dns.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:73
+#: ../../../docs/configuring-playbook.md:59
 msgid "Server connectivity:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:74
+#: ../../../docs/configuring-playbook.md:60
 msgid "[Enabling Telemetry for your Matrix server](configuring-playbook-telemetry.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:76
+#: ../../../docs/configuring-playbook.md:62
 msgid "[Controlling Matrix federation](configuring-playbook-federation.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:78
+#: ../../../docs/configuring-playbook.md:64
-msgid "[Configuring IPv6](./configuring-ipv6.md)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:80
 msgid "Clients"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:82
+#: ../../../docs/configuring-playbook.md:66
 msgid "Web clients for Matrix that you can host on your own domains."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:84
+#: ../../../docs/configuring-playbook.md:68
 msgid "[Configuring Element Web](configuring-playbook-client-element-web.md), if you're going with the default/recommended client"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:86
+#: ../../../docs/configuring-playbook.md:70
 msgid "[Setting up Hydrogen](configuring-playbook-client-hydrogen.md), if you've enabled [Hydrogen](https://github.com/element-hq/hydrogen-web), a lightweight Matrix client with legacy and mobile browser support"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:88
+#: ../../../docs/configuring-playbook.md:72
 msgid "[Setting up Cinny](configuring-playbook-client-cinny.md), if you've enabled [Cinny](https://github.com/ajbura/cinny), a web client focusing primarily on simple, elegant and secure interface"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:90
+#: ../../../docs/configuring-playbook.md:74
-msgid "[Setting up Sable](configuring-playbook-client-sable.md), if you've enabled [Sable](https://github.com/7w1/sable), a web client focusing primarily on simple, elegant and secure interface"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:92
 msgid "[Setting up SchildiChat Web](configuring-playbook-client-schildichat-web.md), if you've enabled [SchildiChat Web](https://schildi.chat/), a web client based on [Element Web](https://element.io/) with some extras and tweaks"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:94
+#: ../../../docs/configuring-playbook.md:76
-msgid "[Setting up FluffyChat Web](configuring-playbook-client-fluffychat-web.md), if you've enabled [FluffyChat Web](https://github.com/krille-chan/fluffychat), a cute cross-platform messenger (web, iOS, Android) for Matrix written in [Flutter](https://flutter.dev/)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:97
 msgid "Authentication and user-related"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:99
+#: ../../../docs/configuring-playbook.md:78
 msgid "Extend and modify how users are authenticated on your homeserver."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:101
+#: ../../../docs/configuring-playbook.md:80
 msgid "[Setting up Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (Next-generation auth for Matrix, based on OAuth 2.0/OIDC)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:103
+#: ../../../docs/configuring-playbook.md:82
 msgid "[Setting up Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:105
+#: ../../../docs/configuring-playbook.md:84
-msgid "[Setting up Ketesa](configuring-playbook-ketesa.md)"
+msgid "[Setting up Synapse Admin](configuring-playbook-synapse-admin.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:107
+#: ../../../docs/configuring-playbook.md:86
 msgid "[Setting up matrix-registration](configuring-playbook-matrix-registration.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:109
+#: ../../../docs/configuring-playbook.md:88
 msgid "[Setting up the REST authentication password provider module](configuring-playbook-rest-auth.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:111
+#: ../../../docs/configuring-playbook.md:90
 msgid "[Setting up the Shared Secret Auth password provider module](configuring-playbook-shared-secret-auth.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:113
+#: ../../../docs/configuring-playbook.md:92
 msgid "[Setting up the LDAP authentication password provider module](configuring-playbook-ldap-auth.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:115
+#: ../../../docs/configuring-playbook.md:94
 msgid "[Setting up matrix-ldap-registration-proxy](configuring-playbook-matrix-ldap-registration-proxy.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:117
+#: ../../../docs/configuring-playbook.md:96
 msgid "[Setting up Synapse Simple Antispam](configuring-playbook-synapse-simple-antispam.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:119
+#: ../../../docs/configuring-playbook.md:98
 msgid "[Setting up Matrix User Verification Service](configuring-playbook-user-verification-service.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:121
+#: ../../../docs/configuring-playbook.md:100
 msgid "File Storage"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:123
+#: ../../../docs/configuring-playbook.md:102
 msgid "Use alternative file storage to the default `media_store` folder."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:125
+#: ../../../docs/configuring-playbook.md:104
-msgid "[Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
+msgid "[Storing Matrix media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:127
+#: ../../../docs/configuring-playbook.md:106
 msgid "[Storing Synapse media files on Amazon S3 or another compatible Object Storage](configuring-playbook-s3.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:129
+#: ../../../docs/configuring-playbook.md:108
-msgid "[Storing Synapse media files on Amazon S3 with Goofys](configuring-playbook-s3-goofys.md)"
+msgid "[Storing Matrix media files using matrix-media-repo](configuring-playbook-matrix-media-repo.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:131
+#: ../../../docs/configuring-playbook.md:110
-msgid "[Storing Synapse media files on Amazon S3 with synapse-s3-storage-provider](configuring-playbook-synapse-s3-storage-provider.md)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:133
 msgid "Bridging other networks"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:135
+#: ../../../docs/configuring-playbook.md:112
 msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:137
+#: ../../../docs/configuring-playbook.md:114
 msgid "[Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md) — a common guide for configuring mautrix bridges"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:139
+#: ../../../docs/configuring-playbook.md:116
-msgid "[Setting up Mautrix Bluesky bridging](configuring-playbook-bridge-mautrix-bluesky.md)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:141
 msgid "[Setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:143
+#: ../../../docs/configuring-playbook.md:118
 msgid "[Setting up Mautrix Telegram bridging](configuring-playbook-bridge-mautrix-telegram.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:145
+#: ../../../docs/configuring-playbook.md:120
 msgid "[Setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:147
+#: ../../../docs/configuring-playbook.md:122
 msgid "[Setting up Mautrix Google Messages bridging](configuring-playbook-bridge-mautrix-gmessages.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:149
+#: ../../../docs/configuring-playbook.md:124
 msgid "[Setting up Mautrix Whatsapp bridging](configuring-playbook-bridge-mautrix-whatsapp.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:151
+#: ../../../docs/configuring-playbook.md:126
 msgid "[Setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:153
+#: ../../../docs/configuring-playbook.md:128
 msgid "[Setting up Messenger bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-messenger.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:155
+#: ../../../docs/configuring-playbook.md:130
 msgid "[Setting up Mautrix Google Chat bridging](configuring-playbook-bridge-mautrix-googlechat.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:157
+#: ../../../docs/configuring-playbook.md:132
 msgid "[Setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:159
+#: ../../../docs/configuring-playbook.md:134
 msgid "[Setting up Mautrix Signal bridging](configuring-playbook-bridge-mautrix-signal.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:161
+#: ../../../docs/configuring-playbook.md:136
 msgid "[Setting up Mautrix wsproxy for bridging Android SMS or Apple iMessage](configuring-playbook-bridge-mautrix-wsproxy.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:163
+#: ../../../docs/configuring-playbook.md:138
 msgid "[Setting up Appservice IRC bridging](configuring-playbook-bridge-appservice-irc.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:165
+#: ../../../docs/configuring-playbook.md:140
 msgid "[Setting up Appservice Discord bridging](configuring-playbook-bridge-appservice-discord.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:167
+#: ../../../docs/configuring-playbook.md:142
+msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:144
 msgid "[Setting up Appservice Kakaotalk bridging](configuring-playbook-bridge-appservice-kakaotalk.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:169
+#: ../../../docs/configuring-playbook.md:146
 msgid "[Setting up Beeper LinkedIn bridging](configuring-playbook-bridge-beeper-linkedin.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:171
+#: ../../../docs/configuring-playbook.md:148
 msgid "[Setting up matrix-hookshot](configuring-playbook-bridge-hookshot.md) — a bridge between Matrix and multiple project management services, such as [GitHub](https://github.com), [GitLab](https://about.gitlab.com) and [JIRA](https://www.atlassian.com/software/jira)."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:173
+#: ../../../docs/configuring-playbook.md:150
+msgid "[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:152
+msgid "[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:154
+msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:156
+msgid "[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:158
 msgid "[Setting up MX Puppet GroupMe bridging](configuring-playbook-bridge-mx-puppet-groupme.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:175
+#: ../../../docs/configuring-playbook.md:160
-msgid "[Setting up Steam bridging](configuring-playbook-bridge-steam.md)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:177
 msgid "[Setting up MX Puppet Steam bridging](configuring-playbook-bridge-mx-puppet-steam.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:179
+#: ../../../docs/configuring-playbook.md:162
+msgid "[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:164
 msgid "[Setting up Postmoogle email bridging](configuring-playbook-bridge-postmoogle.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:181
+#: ../../../docs/configuring-playbook.md:166
 msgid "[Setting up Matrix SMS bridging](configuring-playbook-bridge-matrix-bridge-sms.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:183
+#: ../../../docs/configuring-playbook.md:168
 msgid "[Setting up Heisenbridge bouncer-style IRC bridging](configuring-playbook-bridge-heisenbridge.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:185
+#: ../../../docs/configuring-playbook.md:170
 msgid "[Setting up WeChat bridging](configuring-playbook-bridge-wechat.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:187
+#: ../../../docs/configuring-playbook.md:172
 msgid "Bots"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:189
+#: ../../../docs/configuring-playbook.md:174
 msgid "Bots provide various additional functionality to your installation."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:191
+#: ../../../docs/configuring-playbook.md:176
 msgid "[Setting up baibot](configuring-playbook-bot-baibot.md) — a bot through which you can talk to various [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) services ([OpenAI](https://openai.com/)'s [ChatGPT](https://openai.com/blog/chatgpt/) and [others](https://github.com/etkecc/baibot/blob/main/docs/providers.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:193
+#: ../../../docs/configuring-playbook.md:178
 msgid "[Setting up matrix-reminder-bot](configuring-playbook-bot-matrix-reminder-bot.md) — a bot to remind you about stuff"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:195
+#: ../../../docs/configuring-playbook.md:180
 msgid "[Setting up matrix-registration-bot](configuring-playbook-bot-matrix-registration-bot.md) — a bot to create and manage registration tokens to invite users"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:197
+#: ../../../docs/configuring-playbook.md:182
 msgid "[Setting up maubot](configuring-playbook-bot-maubot.md) — a plugin-based Matrix bot system"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:199
+#: ../../../docs/configuring-playbook.md:184
 msgid "[Setting up Honoroit](configuring-playbook-bot-honoroit.md) — a helpdesk bot"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:201
+#: ../../../docs/configuring-playbook.md:186
 msgid "[Setting up Mjolnir](configuring-playbook-bot-mjolnir.md) — a moderation tool/bot"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:203
+#: ../../../docs/configuring-playbook.md:188
 msgid "[Setting up Draupnir](configuring-playbook-bot-draupnir.md) — a moderation tool/bot, forked from Mjolnir and maintained by its former leader developer"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:205
+#: ../../../docs/configuring-playbook.md:190
 msgid "[Setting up Draupnir for all/D4A](configuring-playbook-appservice-draupnir-for-all.md) — like the [Draupnir bot](configuring-playbook-bot-draupnir.md) mentioned above, but running in appservice mode and supporting multiple instances"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:207
+#: ../../../docs/configuring-playbook.md:192
 msgid "[Setting up Buscarron](configuring-playbook-bot-buscarron.md) — a bot you can use to send any form (HTTP POST, HTML) to a (encrypted) Matrix room"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:209
+#: ../../../docs/configuring-playbook.md:194
 msgid "Administration"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:211
+#: ../../../docs/configuring-playbook.md:196
 msgid "Services that help you in administrating and monitoring your Matrix installation."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:213
+#: ../../../docs/configuring-playbook.md:198
 msgid "[Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver](configuring-playbook-alertmanager-receiver.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:215
+#: ../../../docs/configuring-playbook.md:200
 msgid "[Enabling metrics and graphs (Prometheus, Grafana) for your Matrix server](configuring-playbook-prometheus-grafana.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:217
+#: ../../../docs/configuring-playbook.md:202
+msgid "[Enabling metrics and graphs for NginX logs](configuring-playbook-prometheus-nginxlog.md)"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:204
 msgid "[Setting up the rageshake bug report server](configuring-playbook-rageshake.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:219
+#: ../../../docs/configuring-playbook.md:206
 msgid "[Enabling synapse-usage-exporter for Synapse usage statistics](configuring-playbook-synapse-usage-exporter.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:221
+#: ../../../docs/configuring-playbook.md:208
 msgid "Backups:"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:222
+#: ../../../docs/configuring-playbook.md:209
 msgid "[Setting up BorgBackup](configuring-playbook-backup-borg.md) — a full Matrix server backup solution, including the Postgres database"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:224
+#: ../../../docs/configuring-playbook.md:211
-msgid "[Setting up Postgres backup](configuring-playbook-postgres-backup.md) — a Postgres-database backup solution (note: does not include other files)"
+msgid "[Setting up postgres backup](configuring-playbook-postgres-backup.md) — a Postgres-database backup solution (note: does not include other files)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:226
+#: ../../../docs/configuring-playbook.md:213
 msgid "Other specialized services"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:228
+#: ../../../docs/configuring-playbook.md:215
 msgid "Various services that don't fit any other categories."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:230
+#: ../../../docs/configuring-playbook.md:217
-msgid "[Setting up Element Call](configuring-playbook-element-call.md) — a native Matrix video conferencing application, built on top of the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) (optional)"
+msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:232
+#: ../../../docs/configuring-playbook.md:219
-msgid "[Setting up LiveKit JWT Service](configuring-playbook-livekit-jwt-service.md) - a component of the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:234
-msgid "[Setting up LiveKit Server](configuring-playbook-livekit-server.md) - a component of the [Matrix RTC stack](configuring-playbook-matrix-rtc.md) (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:236
-msgid "[Setting up Matrix RTC](configuring-playbook-matrix-rtc.md) (optional)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:238
 msgid "[Setting up synapse-auto-compressor](configuring-playbook-synapse-auto-compressor.md) for compressing the database on Synapse homeservers"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:240
+#: ../../../docs/configuring-playbook.md:221
 msgid "[Setting up Matrix Corporal](configuring-playbook-matrix-corporal.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:242
+#: ../../../docs/configuring-playbook.md:223
-msgid "[Setting up Matrix.to](configuring-playbook-matrixto.md)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:244
 msgid "[Setting up Etherpad](configuring-playbook-etherpad.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:246
+#: ../../../docs/configuring-playbook.md:225
 msgid "[Setting up the Jitsi video-conferencing platform](configuring-playbook-jitsi.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:248
+#: ../../../docs/configuring-playbook.md:227
 msgid "[Setting up Cactus Comments](configuring-playbook-cactus-comments.md) — a federated comment system built on Matrix"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:250
+#: ../../../docs/configuring-playbook.md:229
 msgid "[Setting up Pantalaimon (E2EE aware proxy daemon)](configuring-playbook-pantalaimon.md) (advanced)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:252
+#: ../../../docs/configuring-playbook.md:231
 msgid "[Setting up the Sygnal push gateway](configuring-playbook-sygnal.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:254
+#: ../../../docs/configuring-playbook.md:233
 msgid "[Setting up the ntfy push notifications server](configuring-playbook-ntfy.md)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:256
+#: ../../../docs/configuring-playbook.md:235
 msgid "Deprecated / unmaintained / removed services"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:258
+#: ../../../docs/configuring-playbook.md:237
 msgid "**Note**: since a deprecated or unmaintained service will not be updated, its bug or vulnerability will be unlikely to get patched. It is recommended to migrate from the service to an alternative if any, and make sure to do your own research before you decide to keep it running nonetheless."
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:260
+#: ../../../docs/configuring-playbook.md:239
-msgid "[Configuring conduwuit](configuring-playbook-conduwuit.md) (removed; this component has been abandoned and unmaintained)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:262
 msgid "[Setting up the Sliding Sync proxy](configuring-playbook-sliding-sync-proxy.md) for clients which require Sliding Sync support (like old Element X versions, before it got switched to Simplified Sliding Sync)"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:264
+#: ../../../docs/configuring-playbook.md:241
-msgid "[Setting up Appservice Slack bridging](configuring-playbook-bridge-appservice-slack.md) (removed; this component has been discontinued)"
+msgid "[Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (deprecated; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:266
+#: ../../../docs/configuring-playbook.md:243
-msgid "[Setting up Appservice Webhooks bridging](configuring-playbook-bridge-appservice-webhooks.md) (deprecated; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be [installed using this playbook](configuring-playbook-bridge-hookshot.md))"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:268
 msgid "[Setting up the Dimension integration manager](configuring-playbook-dimension.md) ([unmaintained](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2806#issuecomment-1673559299); after [installing](installing.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:270
+#: ../../../docs/configuring-playbook.md:245
-msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md) (removed; the author suggests taking a look at [Postmoogle](https://github.com/etkecc/postmoogle) as a replacement, which can also be [installed using this playbook](configuring-playbook-bridge-postmoogle.md))"
+msgid "[Setting up Email2Matrix](configuring-playbook-email2matrix.md) (unmaintained; the author suggests taking a look at [Postmoogle](https://github.com/etkecc/postmoogle) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-postmoogle.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:272
+#: ../../../docs/configuring-playbook.md:247
-msgid "[Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be [installed using this playbook](configuring-playbook-bridge-hookshot.md))"
+msgid "[Setting up Go-NEB](configuring-playbook-bot-go-neb.md) (unmaintained; the bridge's author suggests taking a look at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bridge-hookshot.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:274
+#: ../../../docs/configuring-playbook.md:249
-msgid "[Setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md) (removed; Skype has been discontinued since May 2025)"
+msgid "[Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) (unmaintained; the bridge's author suggests taking a look at [baibot](https://github.com/etkecc/baibot) as a replacement, which can also be installed using [this playbook](configuring-playbook-bot-baibot.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:276
+#: ../../../docs/configuring-playbook.md:251
-msgid "[Setting up ma1sd Identity Server](configuring-playbook-ma1sd.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook.)"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:278
-msgid "[Setting up matrix-bot-chatgpt](configuring-playbook-bot-chatgpt.md) (unmaintained; the bridge's author suggests taking a look at [baibot](https://github.com/etkecc/baibot) as a replacement, which can also be [installed using this playbook](configuring-playbook-bot-baibot.md))"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:280
 msgid "[Setting up Mautrix Facebook bridging](configuring-playbook-bridge-mautrix-facebook.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-messenger](configuring-playbook-bridge-mautrix-meta-messenger.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:282
+#: ../../../docs/configuring-playbook.md:253
+msgid "[Setting up Mautrix Hangouts bridging](configuring-playbook-bridge-mautrix-hangouts.md) (deprecated in favor of the Google Chat bridge with [mautrix-googlechat](configuring-playbook-bridge-mautrix-googlechat.md))"
+msgstr ""
+
+#: ../../../docs/configuring-playbook.md:255
 msgid "[Setting up Mautrix Instagram bridging](configuring-playbook-bridge-mautrix-instagram.md) (deprecated in favor of the Messenger/Instagram bridge with [mautrix-meta-instagram](configuring-playbook-bridge-mautrix-meta-instagram.md))"
 msgstr ""
 
-#: ../../../docs/configuring-playbook.md:284
+#: ../../../docs/configuring-playbook.md:257
-msgid "[Setting up MX Puppet Discord bridging](configuring-playbook-bridge-mx-puppet-discord.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Mautrix Discord bridging](configuring-playbook-bridge-mautrix-discord.md))"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:286
-msgid "[Setting up MX Puppet Instagram bridging](configuring-playbook-bridge-mx-puppet-instagram.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Instagram bridging via Mautrix Meta](configuring-playbook-bridge-mautrix-meta-instagram.md))"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:288
 msgid "[Setting up MX Puppet Skype bridging](configuring-playbook-bridge-mx-puppet-skype.md) (removed; this component has been broken for a long time, so it has been removed from the playbook. Consider [setting up Go Skype Bridge bridging](configuring-playbook-bridge-go-skype-bridge.md))"
 msgstr ""
-
-#: ../../../docs/configuring-playbook.md:290
-msgid "[Setting up MX Puppet Slack bridging](configuring-playbook-bridge-mx-puppet-slack.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Mautrix Slack bridging](configuring-playbook-bridge-mautrix-slack.md))"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:292
-msgid "[Setting up MX Puppet Twitter bridging](configuring-playbook-bridge-mx-puppet-twitter.md) (removed; this component has been unmaintained for a long time, so it has been removed from the playbook. Consider [setting up Mautrix Twitter bridging](configuring-playbook-bridge-mautrix-twitter.md))"
-msgstr ""
-
-#: ../../../docs/configuring-playbook.md:294
-msgid "[Setting up Synapse Auto Invite Accept](configuring-playbook-synapse-auto-accept-invite.md) (removed; since Synapse [v1.109.0](https://github.com/element-hq/synapse/releases/tag/v1.109.0) the same feature is available natively.)"
-msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/container-images.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,21 +18,21 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/container-images.md:18
+#: ../../../docs/container-images.md:1
 msgid "Container images used by the playbook"
 msgstr ""
 
-#: ../../../docs/container-images.md:20
+#: ../../../docs/container-images.md:3
 msgid "This page summarizes the container ([Docker](https://www.docker.com/)) images used by the playbook when setting up your server."
 msgstr ""
 
-#: ../../../docs/container-images.md:22
+#: ../../../docs/container-images.md:5
 msgid "We try to stick to official images (provided by their respective projects) as much as possible."
 msgstr ""
 
-#: ../../../docs/container-images.md:24
+#: ../../../docs/container-images.md:7
 msgid "Homeserver"
 msgstr ""
 
@@ -85,15 +85,15 @@ msgid "Storing your data and managing your presence in the [Matrix](http://matri
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[continuwuity](configuring-playbook-continuwuity.md)"
+msgid "[conduwuit](configuring-playbook-conduwuit.md)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[continuwuation/continuwuity](https://forgejo.ellis.link/continuwuation/continuwuity)"
+msgid "[girlbossceo/conduwuit](https://ghcr.io/girlbossceo/conduwuit)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. continuwuity is a continuation of conduwuit."
+msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit is a fork of Conduit."
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -108,11 +108,11 @@ msgstr ""
 msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. Dendrite is a second-generation Matrix homeserver written in Go, an alternative to Synapse."
 msgstr ""
 
-#: ../../../docs/container-images.md:33
+#: ../../../docs/container-images.md:16
 msgid "Clients"
 msgstr ""
 
-#: ../../../docs/container-images.md:35
+#: ../../../docs/container-images.md:18
 msgid "Web clients for Matrix that you can host on your own domains."
 msgstr ""
 
@@ -152,14 +152,6 @@ msgstr ""
 msgid "Simple, elegant and secure web client"
 msgstr ""
 
-#: ../../../docs/container-images.md
-msgid "[Sable](configuring-playbook-client-sable.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[7w1/sable](https://ghcr.io/7w1/sable)"
-msgstr ""
-
 #: ../../../docs/container-images.md
 msgid "[SchildiChat Web](configuring-playbook-client-schildichat-web.md)"
 msgstr ""
@@ -172,11 +164,11 @@ msgstr ""
 msgid "Based on Element Web, with a more traditional instant messaging experience"
 msgstr ""
 
-#: ../../../docs/container-images.md:45
+#: ../../../docs/container-images.md:27
 msgid "Server Components"
 msgstr ""
 
-#: ../../../docs/container-images.md:47
+#: ../../../docs/container-images.md:29
 msgid "Services that run on the server to make the various parts of your installation work."
 msgstr ""
 
@@ -213,7 +205,7 @@ msgid "[Traefik](https://hub.docker.com/_/traefik/)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Web server, listening on ports 80, 443 and 8448 — standing in front of all the other services. [Using your own webserver](configuring-playbook-own-webserver.md) is also possible."
+msgid "Web server, listening on ports 80, 443 and 8448 — standing in front of all the other services. Using your own webserver [is possible](configuring-playbook-own-webserver.md)"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -225,7 +217,7 @@ msgid "[certbot/certbot](https://hub.docker.com/r/certbot/certbot/)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[Certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/)"
+msgid "The [certbot](https://certbot.eff.org/) tool for obtaining SSL certificates from [Let's Encrypt](https://letsencrypt.org/)"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -240,6 +232,18 @@ msgstr ""
 msgid "Mail server, through which all Matrix services send outgoing email (can be configured to relay through another SMTP server)"
 msgstr ""
 
+#: ../../../docs/container-images.md
+msgid "[ma1sd](configuring-playbook-ma1sd.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Matrix Identity Server"
+msgstr ""
+
 #: ../../../docs/container-images.md
 msgid "[ddclient](configuring-playbook-dynamic-dns.md)"
 msgstr ""
@@ -252,35 +256,11 @@ msgstr ""
 msgid "Update dynamic DNS entries for accounts on Dynamic DNS Network Service Provider"
 msgstr ""
 
-#: ../../../docs/container-images.md
+#: ../../../docs/container-images.md:41
-msgid "[LiveKit Server](configuring-playbook-livekit-server.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[livekit/livekit-server](https://hub.docker.com/r/livekit/livekit-server/)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "WebRTC server for audio/video calls"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[Livekit JWT Service](configuring-playbook-livekit-jwt-service.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[element-hq/lk-jwt-service](https://ghcr.io/element-hq/lk-jwt-service)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "JWT service for integrating [Element Call](./configuring-playbook-element-call.md) with [LiveKit Server](./configuring-playbook-livekit-server.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md:60
 msgid "Authentication"
 msgstr ""
 
-#: ../../../docs/container-images.md:62
+#: ../../../docs/container-images.md:43
 msgid "Extend and modify how users are authenticated on your homeserver."
 msgstr ""
 
@@ -321,7 +301,7 @@ msgid "[activism.international/matrix_ldap_registration_proxy](https://gitlab.co
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Proxy that handles Matrix registration requests and forwards them to LDAP"
+msgid "A proxy that handles Matrix registration requests and forwards them to LDAP."
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -333,11 +313,11 @@ msgid "[zeratax/matrix-registration](https://hub.docker.com/r/devture/zeratax-ma
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Simple python application to have a token based Matrix registration"
+msgid "A simple python application to have a token based Matrix registration"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[Matrix User Verification Service](configuring-playbook-user-verification-service.md)"
+msgid "[Matrix User Verification Service](configuring-playbook-user-verification-service.md) (UVS)"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -353,14 +333,14 @@ msgid "[synapse-simple-antispam](configuring-playbook-synapse-simple-antispam.md
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Spam checker module"
+msgid "A spam checker module"
 msgstr ""
 
-#: ../../../docs/container-images.md:74
+#: ../../../docs/container-images.md:55
 msgid "File Storage"
 msgstr ""
 
-#: ../../../docs/container-images.md:76
+#: ../../../docs/container-images.md:57
 msgid "Use alternative file storage to the default `media_store` folder."
 msgstr ""
 
@@ -389,29 +369,17 @@ msgid "[t2bot/matrix-media-repo](https://ghcr.io/t2bot/matrix-media-repo)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
+msgid "matrix-media-repo is a highly customizable multi-domain media repository for Matrix. Intended for medium to large deployments, this media repo de-duplicates media while being fully compliant with the specification."
 msgstr ""
 
-#: ../../../docs/container-images.md:84
+#: ../../../docs/container-images.md:65
 msgid "Bridges"
 msgstr ""
 
-#: ../../../docs/container-images.md:86
+#: ../../../docs/container-images.md:67
 msgid "Bridges can be used to connect your Matrix installation with third-party communication networks."
 msgstr ""
 
-#: ../../../docs/container-images.md
-msgid "[mautrix-bluesky](configuring-playbook-bridge-mautrix-bluesky.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[mautrix/bluesky](https://mau.dev/mautrix/bluesky/container_registry)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Bridge to [Bluesky](https://bsky.social/about)"
-msgstr ""
-
 #: ../../../docs/container-images.md
 msgid "[mautrix-discord](configuring-playbook-bridge-mautrix-discord.md)"
 msgstr ""
@@ -580,6 +548,14 @@ msgstr ""
 msgid "Bridge to [Discord](https://discordapp.com/)"
 msgstr ""
 
+#: ../../../docs/container-images.md
+msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)"
+msgstr ""
+
 #: ../../../docs/container-images.md
 msgid "[matrix-hookshot](configuring-playbook-bridge-hookshot.md)"
 msgstr ""
@@ -628,6 +604,62 @@ msgstr ""
 msgid "Bouncer-style bridge to [IRC](https://wikipedia.org/wiki/Internet_Relay_Chat)"
 msgstr ""
 
+#: ../../../docs/container-images.md
+msgid "[go-skype-bridge](configuring-playbook-bridge-go-skype-bridge.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[nodefyme/go-skype-bridge](https://hub.docker.com/r/nodefyme/go-skype-bridge)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Skype](https://www.skype.com)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Slack](https://slack.com)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry)"
+msgstr ""
+
 #: ../../../docs/container-images.md
 msgid "[mx-puppet-groupme](configuring-playbook-bridge-mx-puppet-groupme.md)"
 msgstr ""
@@ -640,18 +672,6 @@ msgstr ""
 msgid "Bridge to [GroupMe](https://groupme.com/)"
 msgstr ""
 
-#: ../../../docs/container-images.md
-msgid "[matrix-steam-bridge](configuring-playbook-bridge-steam.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[jasonlaguidice/matrix-steam-bridge](https://github.com/jasonlaguidice/matrix-steam-bridge/pkgs/container/matrix-steam-bridge)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Bridge to [Steam](https://steampowered.com/)"
-msgstr ""
-
 #: ../../../docs/container-images.md
 msgid "[mx-puppet-steam](configuring-playbook-bridge-mx-puppet-steam.md)"
 msgstr ""
@@ -676,11 +696,11 @@ msgstr ""
 msgid "Email to Matrix bridge"
 msgstr ""
 
-#: ../../../docs/container-images.md:114
+#: ../../../docs/container-images.md:99
 msgid "Bots"
 msgstr ""
 
-#: ../../../docs/container-images.md:116
+#: ../../../docs/container-images.md:101
 msgid "Bots provide various additional functionality to your installation."
 msgstr ""
 
@@ -693,7 +713,7 @@ msgid "[etke.cc/baibot](https://ghcr.io/etkecc/baibot)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
+msgid "A bot that exposes the power of [AI](https://en.wikipedia.org/wiki/Artificial_intelligence) / [Large Language Models](https://en.wikipedia.org/wiki/Large_language_model) to you"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -729,7 +749,7 @@ msgid "[dock.mau.dev/maubot/maubot](https://mau.dev/maubot/maubot/container_regi
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Plugin-based Matrix bot system"
+msgid "A plugin-based Matrix bot system"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -741,7 +761,7 @@ msgid "[etke.cc/honoroit](https://github.com/etkecc/honoroit/container_registry)
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Helpdesk bot"
+msgid "A helpdesk bot"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -753,7 +773,7 @@ msgid "[matrixdotorg/mjolnir](https://hub.docker.com/r/matrixdotorg/mjolnir)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Moderation tool for Matrix"
+msgid "A moderation tool for Matrix"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -765,7 +785,7 @@ msgid "[gnuxie/draupnir](https://hub.docker.com/r/gnuxie/draupnir)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Moderation tool for Matrix (Fork of Mjolnir)"
+msgid "A moderation tool for Matrix (Fork of Mjolnir)"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -780,11 +800,11 @@ msgstr ""
 msgid "Web forms (HTTP POST) to Matrix"
 msgstr ""
 
-#: ../../../docs/container-images.md:129
+#: ../../../docs/container-images.md:114
 msgid "Administration"
 msgstr ""
 
-#: ../../../docs/container-images.md:131
+#: ../../../docs/container-images.md:116
 msgid "Services that help you in administrating and monitoring your Matrix installation."
 msgstr ""
 
@@ -813,15 +833,15 @@ msgid "OAuth 2.0 and OpenID Provider server"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[ketesa](configuring-playbook-ketesa.md)"
+msgid "[synapse-admin](configuring-playbook-synapse-admin.md)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[etkecc/ketesa](https://ghcr.io/etkecc/ketesa)"
+msgid "[etke.cc/synapse-admin](https://ghcr.io/etkecc/synapse-admin)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Fully-featured web UI for administrating your Matrix homeserver — users, rooms, media, sessions, and more"
+msgid "A web UI tool for administrating users and rooms on your Matrix server"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -853,7 +873,7 @@ msgid "Graphing tool that works well with the above two images. Our playbook als
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[Metrics and Graphs](configuring-playbook-prometheus-grafana.md#enable-metrics-and-graphs-for-nginx-logs-optional)"
+msgid "[Metrics and Graphs](configuring-playbook-prometheus-nginxlog.md)"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -872,18 +892,6 @@ msgstr ""
 msgid "Backups"
 msgstr ""
 
-#: ../../../docs/container-images.md
-msgid "[postgres-backup-local](configuring-playbook-postgres-backup.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[prodrigestivill/postgres-backup-local](https://hub.docker.com/r/prodrigestivill/postgres-backup-local)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Create automatic database backups"
-msgstr ""
-
 #: ../../../docs/container-images.md
 msgid "[rageshake](configuring-playbook-rageshake.md)"
 msgstr ""
@@ -904,24 +912,44 @@ msgstr ""
 msgid "Export the usage statistics of a Synapse homeserver to be scraped by Prometheus."
 msgstr ""
 
-#: ../../../docs/container-images.md:147
+#: ../../../docs/container-images.md:131
 msgid "Misc"
 msgstr ""
 
-#: ../../../docs/container-images.md:149
+#: ../../../docs/container-images.md:133
 msgid "Various services that don't fit any other categories."
 msgstr ""
 
+#: ../../../docs/container-images.md
+msgid "[sliding-sync](configuring-playbook-sliding-sync-proxy.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Sliding Sync support for clients which require it (like old Element X versions, before it got switched to Simplified Sliding Sync)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "A Synapse module to automatically accept invites."
+msgstr ""
+
 #: ../../../docs/container-images.md
 msgid "[synapse_auto_compressor](configuring-playbook-synapse-auto-compressor.md)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[mb-saces/rust-synapse-tools](https://gitlab.com/mb-saces/rust-synapse-tools/container_registry)"
+msgid "[etke.cc/rust-synapse-compress-state](https://gitlab.com/etke.cc/rust-synapse-compress-state/container_registry)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Cli tool that automatically compresses Synapse's `state_groups` database table in background"
+msgid "A cli tool that automatically compresses `state_groups` database table in background."
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -945,7 +973,7 @@ msgid "[etherpad/etherpad](https://hub.docker.com/r/etherpad/etherpad/)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Open source collaborative text editor"
+msgid "An open source collaborative text editor"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -957,7 +985,7 @@ msgid "[jitsi/web](https://hub.docker.com/r/jitsi/web)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[Jitsi](https://jitsi.org/) web UI"
+msgid "the [Jitsi](https://jitsi.org/) web UI"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -965,7 +993,7 @@ msgid "[jitsi/jicofo](https://hub.docker.com/r/jitsi/jicofo)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[Jitsi](https://jitsi.org/) Focus component"
+msgid "the [Jitsi](https://jitsi.org/) Focus component"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -973,7 +1001,7 @@ msgid "[jitsi/prosody](https://hub.docker.com/r/jitsi/prosody)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[Jitsi](https://jitsi.org/) Prosody XMPP server component"
+msgid "the [Jitsi](https://jitsi.org/) Prosody XMPP server component"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -981,7 +1009,7 @@ msgid "[jitsi/jvb](https://hub.docker.com/r/jitsi/jvb)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[Jitsi](https://jitsi.org/) Video Bridge component"
+msgid "the [Jitsi](https://jitsi.org/) Video Bridge component"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -993,7 +1021,7 @@ msgid "[cactuscomments/cactus-appservice](https://hub.docker.com/r/cactuscomment
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Federated comment system built on Matrix"
+msgid "A federated comment system built on Matrix"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -1009,7 +1037,7 @@ msgid "[matrixdotorg/pantalaimon](https://hub.docker.com/r/matrixdotorg/pantalai
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "E2EE aware proxy daemon"
+msgid "An E2EE aware proxy daemon"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -1036,36 +1064,24 @@ msgstr ""
 msgid "Self-hosted, UnifiedPush-compatible push notifications server"
 msgstr ""
 
-#: ../../../docs/container-images.md
+#: ../../../docs/container-images.md:152
-msgid "[Element Call](configuring-playbook-element-call.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[element-hq/element-call](https://ghcr.io/element-hq/element-call)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "A native Matrix video conferencing application"
-msgstr ""
-
-#: ../../../docs/container-images.md:167
 msgid "Container images of deprecated / unmaintained services"
 msgstr ""
 
-#: ../../../docs/container-images.md:169
+#: ../../../docs/container-images.md:154
 msgid "The list of the deprecated or unmaintained services is available [here](configuring-playbook.md#deprecated--unmaintained--removed-services)."
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[conduwuit](configuring-playbook-conduwuit.md)"
+msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "[girlbossceo/conduwuit](https://ghcr.io/girlbossceo/conduwuit)"
+msgid "[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Storing your data and managing your presence in the [Matrix](http://matrix.org/) network. conduwuit was a fork of Conduit."
+msgid "Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.)"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -1077,7 +1093,7 @@ msgid "[turt2live/matrix-dimension](https://hub.docker.com/r/turt2live/matrix-di
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Open source integration manager for Matrix clients"
+msgid "An open source integration manager for Matrix clients"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -1101,39 +1117,7 @@ msgid "[matrixdotorg/go-neb](https://hub.docker.com/r/matrixdotorg/go-neb)"
 msgstr ""
 
 #: ../../../docs/container-images.md
-msgid "Multi functional bot written in Go"
+msgid "A multi functional bot written in Go"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[ma1sd](configuring-playbook-ma1sd.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[ma1uta/ma1sd](https://hub.docker.com/r/ma1uta/ma1sd/)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Matrix Identity Server"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[matrix-appservice-slack](configuring-playbook-bridge-appservice-slack.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[matrixdotorg/matrix-appservice-slack](https://hub.docker.com/r/matrixdotorg/matrix-appservice-slack)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[matrix-appservice-webhooks](configuring-playbook-bridge-appservice-webhooks.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[turt2live/matrix-appservice-webhooks](https://hub.docker.com/r/turt2live/matrix-appservice-webhooks)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Bridge for slack compatible webhooks ([ConcourseCI](https://concourse-ci.org/), [Slack](https://slack.com/) etc. pp.)"
 msgstr ""
 
 #: ../../../docs/container-images.md
@@ -1160,6 +1144,18 @@ msgstr ""
 msgid "Bridge to [Facebook](https://facebook.com/)"
 msgstr ""
 
+#: ../../../docs/container-images.md
+msgid "[mautrix-hangouts](configuring-playbook-bridge-mautrix-hangouts.md)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "[mautrix/hangouts](https://mau.dev/mautrix/hangouts/container_registry)"
+msgstr ""
+
+#: ../../../docs/container-images.md
+msgid "Bridge to [Google Hangouts](https://en.wikipedia.org/wiki/Google_Hangouts)"
+msgstr ""
+
 #: ../../../docs/container-images.md
 msgid "[mautrix-instagram](configuring-playbook-bridge-mautrix-instagram.md)"
 msgstr ""
@@ -1171,67 +1167,3 @@ msgstr ""
 #: ../../../docs/container-images.md
 msgid "Bridge to [Instagram](https://instagram.com/)"
 msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[mx-puppet-discord](configuring-playbook-bridge-mx-puppet-discord.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[mx-puppet/discord/mx-puppet-discord](https://gitlab.com/mx-puppet/discord/mx-puppet-discord/container_registry)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[mx-puppet-instagram](configuring-playbook-bridge-mx-puppet-instagram.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[sorunome/mx-puppet-instagram](https://hub.docker.com/r/sorunome/mx-puppet-instagram)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Bridge for Instagram-DMs ([Instagram](https://www.instagram.com/))"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[mx-puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[mx-puppet/slack/mx-puppet-slack](https://gitlab.com/mx-puppet/slack/mx-puppet-slack/container_registry)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Bridge to [Slack](https://slack.com)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[mx-puppet-twitter](configuring-playbook-bridge-mx-puppet-twitter.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[sorunome/mx-puppet-twitter](https://hub.docker.com/r/sorunome/mx-puppet-twitter)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Bridge for Twitter-DMs ([Twitter](https://twitter.com/))"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[sliding-sync](configuring-playbook-sliding-sync-proxy.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[matrix-org/sliding-sync](https://ghcr.io/matrix-org/sliding-sync)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Sliding Sync support for clients which require it (like old Element X versions, before it got switched to Simplified Sliding Sync)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "[synapse_auto_accept_invite](configuring-playbook-synapse-auto-accept-invite.md)"
-msgstr ""
-
-#: ../../../docs/container-images.md
-msgid "Synapse module to automatically accept invites"
-msgstr ""

i18n/locales/jp/LC_MESSAGES/docs/registering-users.po

@@ -10,7 +10,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-04-03 11:56+0100\n"
+"POT-Creation-Date: 2025-01-27 09:54+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language: jp\n"
@@ -18,225 +18,228 @@ msgstr ""
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.18.0\n"
+"Generated-By: Babel 2.16.0\n"
 
-#: ../../../docs/registering-users.md:11
+#: ../../../docs/registering-users.md:1
 msgid "Registering users"
 msgstr ""
 
-#: ../../../docs/registering-users.md:13
+#: ../../../docs/registering-users.md:3
 msgid "This documentation page tells you how to create user accounts on your Matrix server."
 msgstr ""
 
-#: ../../../docs/registering-users.md:15
+#: ../../../docs/registering-users.md:5
 msgid "Table of contents:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:16
+#: ../../../docs/registering-users.md:7
 msgid "[Registering users](#registering-users)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:17
+#: ../../../docs/registering-users.md:8
 msgid "[Registering users manually](#registering-users-manually)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:18
+#: ../../../docs/registering-users.md:9
 msgid "[Managing users via a Web UI](#managing-users-via-a-web-ui)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:19
+#: ../../../docs/registering-users.md:10
 msgid "[Letting certain users register on your private server](#letting-certain-users-register-on-your-private-server)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:20
+#: ../../../docs/registering-users.md:11
 msgid "[Enabling public user registration](#enabling-public-user-registration)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:21
+#: ../../../docs/registering-users.md:12
 msgid "[Adding/Removing Administrator privileges to an existing user](#addingremoving-administrator-privileges-to-an-existing-user)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:23
+#: ../../../docs/registering-users.md:14
 msgid "Registering users manually"
 msgstr ""
 
-#: ../../../docs/registering-users.md:25 ../../../docs/registering-users.md:127
+#: ../../../docs/registering-users.md:16 ../../../docs/registering-users.md:121
 msgid "**Notes**:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:26
+#: ../../../docs/registering-users.md:17
 msgid "Make sure to adjust `USERNAME_HERE` and `PASSWORD_HERE`"
 msgstr ""
 
-#: ../../../docs/registering-users.md:27
+#: ../../../docs/registering-users.md:18
 msgid "For `USERNAME_HERE`, use a plain username like `alice`, not a full ID (`@alice:example.com`)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:28
+#: ../../../docs/registering-users.md:19
 msgid "Use `admin=yes` or `admin=no` depending on whether you wish to make the user an administrator of the Matrix server"
 msgstr ""
 
-#: ../../../docs/registering-users.md:30
+#: ../../../docs/registering-users.md:21
 msgid "After registering a user (using one of the methods below), **you can log in with that user** via the [Element Web](configuring-playbook-client-element-web.md) service that this playbook has installed for you at a URL like this: `https://element.example.com/`."
 msgstr ""
 
-#: ../../../docs/registering-users.md:32
+#: ../../../docs/registering-users.md:23
 msgid "Registering users via the Ansible playbook"
 msgstr ""
 
-#: ../../../docs/registering-users.md:34
+#: ../../../docs/registering-users.md:25
 msgid "It's best to register users via the Ansible playbook, because it works regardless of homeserver implementation (Synapse, Dendrite, etc) or usage of [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md) (MAS)."
 msgstr ""
 
-#: ../../../docs/registering-users.md:36
+#: ../../../docs/registering-users.md:27
 msgid "To register a user via this Ansible playbook:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:44
+#: ../../../docs/registering-users.md:35
 msgid "**or** by invoking `ansible-playbook` manually:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:52
+#: ../../../docs/registering-users.md:43
 msgid "Feel free to register as many users (for friends, family, etc.) as you want. Still, perhaps you should grant full administrative access to your user account only (with `admin=yes`), and others should be created with `admin=no`."
 msgstr ""
 
-#: ../../../docs/registering-users.md:54
+#: ../../../docs/registering-users.md:45
 msgid "[!WARNING] If you're registering users against Matrix Authentication Service, do note that it [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information."
 msgstr ""
 
-#: ../../../docs/registering-users.md:57
+#: ../../../docs/registering-users.md:48
 msgid "Registering users manually for Synapse"
 msgstr ""
 
-#: ../../../docs/registering-users.md:59
+#: ../../../docs/registering-users.md:50
 msgid "If you're using the [Synapse](configuring-playbook-synapse.md) homeserver implementation (which is the default), you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
 msgstr ""
 
-#: ../../../docs/registering-users.md:67
+#: ../../../docs/registering-users.md:58
 msgid "Registering users manually for Dendrite"
 msgstr ""
 
-#: ../../../docs/registering-users.md:69
+#: ../../../docs/registering-users.md:60
 msgid "If you're using the [Dendrite](./configuring-playbook-dendrite.md) homeserver implementation, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
 msgstr ""
 
-#: ../../../docs/registering-users.md:77
+#: ../../../docs/registering-users.md:68
 msgid "Registering users manually for Matrix Authentication Service"
 msgstr ""
 
-#: ../../../docs/registering-users.md:79
+#: ../../../docs/registering-users.md:70
 msgid "If you're using the [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) and your existing homeserver (most likely [Synapse](./configuring-playbook-synapse.md)) is delegating authentication to it, you can register users via the command-line after **SSH**-ing to your server (requires that [all services have been started](installing.md#install-matrix-server-and-services)):"
 msgstr ""
 
-#: ../../../docs/registering-users.md:87
+#: ../../../docs/registering-users.md:78
 msgid "This `register-user` script actually invokes the `mas-cli manage register-user` command under the hood. If you'd like more control over the registration process, consider invoking the `mas-cli` command directly:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:93
+#: ../../../docs/registering-users.md:84
 msgid "[!WARNING] Matrix Authentication Service [still insists](https://github.com/element-hq/matrix-authentication-service/issues/1505) on having a verified email address for each user. Upon a user's first login, they will be asked to confirm their email address. This requires that email sending is [configured](./configuring-playbook-email.md). You can also consult the [Working around email deliverability issues](./configuring-playbook-matrix-authentication-service.md#working-around-email-deliverability-issues) section for more information."
 msgstr ""
 
-#: ../../../docs/registering-users.md:96
+#: ../../../docs/registering-users.md:87
 msgid "Managing users via a Web UI"
 msgstr ""
 
-#: ../../../docs/registering-users.md:98
+#: ../../../docs/registering-users.md:89
-msgid "To manage users and your homeserver more easily (via a web interface), you can install [Ketesa](configuring-playbook-ketesa.md) — a fully-featured admin UI covering users, rooms, media, sessions, and MAS management."
+msgid "To manage users more easily (via a web user-interace), you can install [Synapse Admin](configuring-playbook-synapse-admin.md)."
 msgstr ""
 
-#: ../../../docs/registering-users.md:100
+#: ../../../docs/registering-users.md:91
+msgid "[!WARNING] If you're using [Matrix Authentication Service](configuring-playbook-matrix-authentication-service.md), note that user management via synapse-admin is not fully working yet. See the [Expectations](configuring-playbook-matrix-authentication-service.md#expectations) section for more information."
+msgstr ""
+
+#: ../../../docs/registering-users.md:94
 msgid "Letting certain users register on your private server"
 msgstr ""
 
-#: ../../../docs/registering-users.md:102
+#: ../../../docs/registering-users.md:96
 msgid "If you'd rather **keep your server private** (public registration closed, as is the default), and **let certain people create accounts by themselves** (instead of creating user accounts manually like this), consider installing and making use of [matrix-registration](configuring-playbook-matrix-registration.md)."
 msgstr ""
 
-#: ../../../docs/registering-users.md:104
+#: ../../../docs/registering-users.md:98
 msgid "Enabling public user registration"
 msgstr ""
 
-#: ../../../docs/registering-users.md:106
+#: ../../../docs/registering-users.md:100
 msgid "To **open up user registration publicly** (usually **not recommended**), add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:108
+#: ../../../docs/registering-users.md:102
 msgid "For Synapse:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:114
+#: ../../../docs/registering-users.md:108
 msgid "For Dendrite:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:120
+#: ../../../docs/registering-users.md:114
 msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:129
+#: ../../../docs/registering-users.md:123
 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
 msgstr ""
 
-#: ../../../docs/registering-users.md:131
+#: ../../../docs/registering-users.md:125
 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. Note these shortcuts run the `ensure-matrix-users-created` tag too."
 msgstr ""
 
-#: ../../../docs/registering-users.md:133
+#: ../../../docs/registering-users.md:127
 msgid "If you're opening up registrations publicly like this, you might also wish to [configure CAPTCHA protection](configuring-captcha.md)."
 msgstr ""
 
-#: ../../../docs/registering-users.md:135
+#: ../../../docs/registering-users.md:129
 msgid "Adding/Removing Administrator privileges to an existing user"
 msgstr ""
 
-#: ../../../docs/registering-users.md:137
+#: ../../../docs/registering-users.md:131
 msgid "Adding/Removing Administrator privileges to an existing user in Synapse"
 msgstr ""
 
-#: ../../../docs/registering-users.md:139
+#: ../../../docs/registering-users.md:133
 msgid "To change the admin privileges for a user in Synapse's local database, you need to run an SQL query like this against the `synapse` database:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:145
+#: ../../../docs/registering-users.md:139
 msgid "where:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:147
+#: ../../../docs/registering-users.md:141
 msgid "`ADMIN_VALUE` being either `0` (regular user) or `1` (admin)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:148
+#: ../../../docs/registering-users.md:142
 msgid "`USER` and `example.com` pointing to a valid user on your server"
 msgstr ""
 
-#: ../../../docs/registering-users.md:150
+#: ../../../docs/registering-users.md:144
 msgid "If you're using the integrated Postgres server and not an [external Postgres server](configuring-playbook-external-postgres.md), you can launch a Postgres into the `synapse` database by:"
 msgstr ""
 
-#: ../../../docs/registering-users.md:152
+#: ../../../docs/registering-users.md:146
 msgid "running `/matrix/postgres/bin/cli` — to launch [`psql`](https://www.postgresql.org/docs/current/app-psql.html)"
 msgstr ""
 
-#: ../../../docs/registering-users.md:153
+#: ../../../docs/registering-users.md:147
 msgid "running `\\c synapse` — to change to the `synapse` database"
 msgstr ""
 
-#: ../../../docs/registering-users.md:155
+#: ../../../docs/registering-users.md:149
 msgid "You can then proceed to run the query above."
 msgstr ""
 
-#: ../../../docs/registering-users.md:157
+#: ../../../docs/registering-users.md:151
 msgid "**Note**: directly modifying the raw data of Synapse (or any other software) could cause the software to break. You've been warned!"
 msgstr ""
 
-#: ../../../docs/registering-users.md:159
+#: ../../../docs/registering-users.md:153
 msgid "Adding/Removing Administrator privileges to an existing user in Matrix Authentication Service"
 msgstr ""
 
-#: ../../../docs/registering-users.md:161
+#: ../../../docs/registering-users.md:155
-msgid "Promoting/demoting a user in Matrix Authentication Service can be done using the [`mas-cli`](./configuring-playbook-matrix-authentication-service.md#management) management tool's [`manage promote-admin`](https://element-hq.github.io/matrix-authentication-service/reference/cli/manage.html#manage-promote-admin) and [`manage demote-admin`](https://element-hq.github.io/matrix-authentication-service/reference/cli/manage.html#manage-demote-admin) commands. For example: `/matrix/matrix-authentication-service/bin/mas-cli manage promote-admin some.username`."
+msgid "Promoting/demoting a user in Matrix Authentication Service cannot currently (2024-10-19) be done via the [`mas-cli` Management tool](./configuring-playbook-matrix-authentication-service.md#management)."
 msgstr ""
 
-#: ../../../docs/registering-users.md:163
+#: ../../../docs/registering-users.md:157
-#, python-brace-format
+msgid "You can do it via the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html)'s `POST /api/admin/v1/users/{id}/set-admin` endpoint."
-msgid "You can also do it via the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html)'s `POST /api/admin/v1/users/{id}/set-admin` endpoint."
 msgstr ""