overmind
/
matrix-docker-ansible-deploy
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy
1
0
Fork 0
Code Issues 0 Releases 0 Wiki Activity
Matrix Docker Ansible eploy
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
8900 Commits
5 Branches
1.5 GiB
 
 
 
Tree: baed8c2450
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'baed8c2450'
${ noResults }
matrix-docker-ansible-deploy/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge...

154 lines
7.6 KiB
Raw Blame History 

  1. # SOME DESCRIPTIVE TITLE.

  2. # Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community

  3. # members

  4. # This file is distributed under the same license as the

  5. # matrix-docker-ansible-deploy package.

  6. # FIRST AUTHOR <EMAIL@ADDRESS>, 2024.

  7. #

  8. #, fuzzy

  9. msgid ""

  10. msgstr ""

  11. "Project-Id-Version: matrix-docker-ansible-deploy \n"

  12. "Report-Msgid-Bugs-To: \n"

  13. "POT-Creation-Date: 2024-12-28 10:25+0200\n"

  14. "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"

  15. "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"

  16. "Language: jp\n"

  17. "Language-Team: jp <LL@li.org>\n"

  18. "MIME-Version: 1.0\n"

  19. "Content-Type: text/plain; charset=utf-8\n"

  20. "Content-Transfer-Encoding: 8bit\n"

  21. "Generated-By: Babel 2.16.0\n"

  22. 

  23. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:1

  24. msgid "Setting up Mautrix Telegram bridging (optional)"

  25. msgstr ""

  26. 

  27. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:3

  28. msgid "The playbook can install and configure [mautrix-telegram](https://github.com/mautrix/telegram) for you."

  29. msgstr ""

  30. 

  31. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:5

  32. msgid "See the project's [documentation](https://docs.mau.fi/bridges/python/telegram/index.html) to learn what it does and why it might be useful to you."

  33. msgstr ""

  34. 

  35. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:7

  36. msgid "Prerequisite (optional)"

  37. msgstr ""

  38. 

  39. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:9

  40. 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) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook."

  41. msgstr ""

  42. 

  43. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:11

  44. msgid "For details about configuring Double Puppeting for this bridge, see the section below: [Set up Double Puppeting](#-set-up-double-puppeting)"

  45. msgstr ""

  46. 

  47. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:13

  48. msgid "Adjusting the playbook configuration"

  49. msgstr ""

  50. 

  51. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:15

  52. msgid "You'll need to obtain API keys from [https://my.telegram.org/apps](https://my.telegram.org/apps) and then add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"

  53. msgstr ""

  54. 

  55. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:23

  56. msgid "Installing"

  57. msgstr ""

  58. 

  59. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:25

  60. msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"

  61. msgstr ""

  62. 

  63. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:32

  64. msgid "**Notes**:"

  65. msgstr ""

  66. 

  67. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:34

  68. msgid "The `ensure-matrix-users-created` playbook tag makes the playbook automatically create the bot's user account."

  69. msgstr ""

  70. 

  71. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36

  72. msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"

  73. msgstr ""

  74. 

  75. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:38

  76. 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."

  77. msgstr ""

  78. 

  79. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:40

  80. msgid "Usage"

  81. msgstr ""

  82. 

  83. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:42

  84. 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)."

  85. msgstr ""

  86. 

  87. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:44

  88. msgid "If you want to use the relay-bot feature ([relay bot documentation](https://docs.mau.fi/bridges/python/telegram/relay-bot.html)), which allows anonymous user to chat with telegram users, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"

  89. msgstr ""

  90. 

  91. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54

  92. msgid "You might also want to give permissions to administrate the bot:"

  93. msgstr ""

  94. 

  95. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:63

  96. msgid "More details about permissions in this example: https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-config.yaml#L410"

  97. msgstr ""

  98. 

  99. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:65

  100. msgid "If you like to exclude all groups from syncing and use the Telgeram-Bridge only for direct chats, you can add the following additional playbook configuration:"

  101. msgstr ""

  102. 

  103. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:71

  104. msgid "💡 Set up Double Puppeting"

  105. msgstr ""

  106. 

  107. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:73

  108. msgid "After successfully enabling bridging, you may wish to set up [Double Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) (hint: you most likely do)."

  109. msgstr ""

  110. 

  111. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:75

  112. msgid "To set it up, you have 2 ways of going about it."

  113. msgstr ""

  114. 

  115. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:77

  116. msgid "Method 1: automatically, by enabling Appservice Double Puppet or Shared Secret Auth"

  117. msgstr ""

  118. 

  119. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:79

  120. msgid "The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook."

  121. msgstr ""

  122. 

  123. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:81

  124. msgid "Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future."

  125. msgstr ""

  126. 

  127. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:83

  128. msgid "Enabling double puppeting by enabling the [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service works at the time of writing, but is deprecated and will stop working in the future."

  129. msgstr ""

  130. 

  131. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85

  132. msgid "Method 2: manually, by asking each user to provide a working access token"

  133. msgstr ""

  134. 

  135. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87

  136. msgid "**Note**: This method for enabling Double Puppeting can be configured only after you've already set up bridging."

  137. msgstr ""

  138. 

  139. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:89

  140. msgid "When using this method, **each user** that wishes to enable Double Puppeting needs to follow the following steps:"

  141. msgstr ""

  142. 

  143. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91

  144. msgid "retrieve a Matrix access token for yourself. Refer to the documentation on [how to obtain one](obtaining-access-tokens.md)."

  145. msgstr ""

  146. 

  147. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93

  148. msgid "send `login-matrix` to the bot and follow instructions about how to send the access token to it"

  149. msgstr ""

  150. 

  151. #: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:95

  152. msgid "make sure you don't log out the `Mautrix-Telegram` device some time in the future, as that would break the Double Puppeting feature"

  153. msgstr ""