matrix-docker-ansible-deploy/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-appservice-slack.po

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

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:1
msgid "Setting up Appservice Slack bridging (optional)"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:3
#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:75
msgid "**Notes**:"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:4
msgid ""
"Bridging to [Slack](https://slack.com) can also happen via the [mx-"
"puppet-slack](configuring-playbook-bridge-mx-puppet-slack.md) and "
"[mautrix-slack](configuring-playbook-bridge-mautrix-slack.md) bridges "
"supported by the playbook."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:5
msgid ""
"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\"."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:7
msgid ""
"The playbook can install and configure [matrix-appservice-"
"slack](https://github.com/matrix-org/matrix-appservice-slack) for you."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:9
msgid ""
"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."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:11
msgid "Prerequisites"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:13
msgid "Create a Classic Slack App"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:15
msgid ""
"First, you need to create a Classic Slack App "
"[here](https://api.slack.com/apps?new_classic_app=1)."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:17
msgid ""
"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."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:19
msgid ""
"Then, click on Event Subscriptions and enable them and use the request "
"url: `https://matrix.example.com/appservice-slack`."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:21
msgid "Add the following events as `Bot User Events` and save:"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:23
msgid "team_domain_change"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:24
msgid "message.channels"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:25
msgid "message.groups (if you want to bridge private channels)"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:26
msgid "reaction_added"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:27
msgid "reaction_removed"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:29
msgid "Next, click on \"OAuth & Permissions\" and add the following scopes:"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:31
msgid "chat:write:bot"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:32
msgid "users:read"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:33
msgid "reactions:write"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:34
msgid "files:write:user (if you want to bridge files)"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:36
msgid ""
"**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."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:38
msgid ""
"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."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:40
msgid "Create an administration control room on Matrix"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:42
msgid "Create a new Matrix room to act as the administration control room."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:44
msgid ""
"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."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:46
msgid "Adjusting the playbook configuration"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:48
msgid ""
"To enable the bridge, add the following configuration to your "
"`inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:64
msgid ""
"Other configuration options are available via the "
"`matrix_appservice_slack_configuration_extension_yaml` variable."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:66
msgid "Installing"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:68
msgid ""
"After configuring the playbook, run it with [playbook tags](playbook-"
"tags.md) as below:"
msgstr ""

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

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:79
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-appservice-slack.md:81
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-appservice-slack.md:83
msgid "Usage"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:85
msgid ""
"To use the bridge, you need to send `/invite @slackbot:example.com` to "
"invite the bridge bot user into the admin room."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:87
msgid ""
"If Team Sync is not enabled, for each channel you would like to bridge, "
"perform the following steps:"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:89
msgid ""
"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`."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:90
msgid ""
"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."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:91
msgid ""
"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/`."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:92
msgid ""
"Issue a link command in the administration control room with these "
"collected values as arguments:"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:94
msgid "with file bridging:"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:100
msgid "without file bridging:"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:106
msgid "These arguments can be shortened to single-letter forms:"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:112
msgid "Unlinking"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:114
msgid "Channels can be unlinked again by sending this:"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:120
msgid ""
"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."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:122
msgid "Troubleshooting"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:124
msgid "As always, check the logs: `journalctl -fu matrix-appservice-slack`"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:126
msgid "Linking: \"Room is now pending-name\""
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:128
msgid ""
"This typically means that you haven't used the correct Slack channel ID. "
"Unlink the room and recheck 'Determine the \"channel ID\"' from above."
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:130
msgid "Messages work from Matrix to Slack, but not the other way around"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:132
msgid "Check you logs, if they say something like"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:134
#, python-format
msgid ""
"`WARN SlackEventHandler Ignoring message from unrecognised Slack channel "
"ID : %s (%s) <the channel ID> <some other ID>`"
msgstr ""

#: ../../../docs/configuring-playbook-bridge-appservice-slack.md:136
msgid ""
"then unlink your room, reinvite the bot and re-link it again. This may "
"particularly hit you, if you tried to unsuccessfully link your room "
"multiple times without unlinking it after each failed attempt."
msgstr ""