|
- # 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>, YEAR.
- #
- #, fuzzy
- msgid ""
- msgstr ""
- "Project-Id-Version: matrix-docker-ansible-deploy \n"
- "Report-Msgid-Bugs-To: \n"
- "POT-Creation-Date: 2026-05-07 11:16+0000\n"
- "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"
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:14
- msgid "Setting up Mautrix Telegram bridging (optional)"
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:16
- msgid "<sup>Refer the common guide for configuring mautrix bridges: [Setting up a Generic Mautrix Bridge](configuring-playbook-bridge-mautrix-bridges.md)</sup>"
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:18
- msgid "The playbook can install and configure [mautrix-telegram](https://github.com/mautrix/telegram) for you."
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:20
- msgid "See the project's [documentation](https://docs.mau.fi/bridges/go/telegram/index.html) to learn what it does and why it might be useful to you."
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:22
- msgid "Prerequisites"
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:24
- msgid "Obtain a Telegram API key"
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:26
- msgid "To use the bridge, you'd need to obtain an API key from [https://my.telegram.org/apps](https://my.telegram.org/apps)."
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:28
- msgid "Enable Appservice Double Puppet (optional)"
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:30
- msgid "If you want to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do) for this bridge automatically, you need to have enabled [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) service for this playbook."
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:32
- msgid "See [this section](configuring-playbook-bridge-mautrix-bridges.md#set-up-double-puppeting-optional) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about setting up Double Puppeting."
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:34
- msgid "Adjusting the playbook configuration"
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36
- msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `YOUR_TELEGRAM_APP_ID` and `YOUR_TELEGRAM_API_HASH`."
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:44
- msgid "Relaying"
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:46
- msgid "This bridge supports the common [mautrix bridge relay mode](configuring-playbook-bridge-mautrix-bridges.md#enable-relay-mode-optional). Once enabled, any authenticated user can be turned into a relaybot for a chat by sending `!tg set-relay` in that chat."
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:48
- msgid "Configure a user as an administrator of the bridge (optional)"
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:50
- msgid "You might also want to give permissions to a user to administrate the bot. See [this section](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional) on the common guide for details about it."
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:52
- msgid "Extending the configuration"
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54
- msgid "There are some additional things you may wish to configure about the bridge."
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:56
- msgid "See [this section](configuring-playbook-bridge-mautrix-bridges.md#extending-the-configuration) on the [common guide for configuring mautrix bridges](configuring-playbook-bridge-mautrix-bridges.md) for details about variables that you can customize and the bridge's default configuration, including [bridge permissions](configuring-playbook-bridge-mautrix-bridges.md#configure-bridge-permissions-optional), [encryption support](configuring-playbook-bridge-mautrix-bridges.md#enable-encryption-optional), [bot's username](configuring-playbook-bridge-mautrix-bridges.md#set-the-bots-username-optional), etc."
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:58
- msgid "Installing"
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:60
- msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:67
- 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-mautrix-telegram.md:69
- 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-bridge-mautrix-telegram.md:71
- msgid "Usage"
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:73
- msgid "To use the bridge, you need to start a chat with `@telegrambot:example.com` (where `example.com` is your base domain, not the `matrix.` domain)."
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:75
- msgid "You can then follow instructions on the bridge's [official documentation on Authentication](https://docs.mau.fi/bridges/go/telegram/authentication.html)."
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:77
- msgid "After logging in, the bridge will create portal rooms for all of your Telegram groups and invite you to them."
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:79
- msgid "Troubleshooting"
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:81
- 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-mautrix-telegram`."
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:83
- msgid "Increase logging verbosity"
- msgstr ""
-
- #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85
- msgid "The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"
- msgstr ""
|