You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
slack bridge: Remove support for the legacy RTM API.
This is an optional commit that drops support running
the Slack Bridge using the legacy RTM API. The reasoning
for removing backwards compitability is because the user
can just use the older version of pyton-zulip-api.
Copy file name to clipboardExpand all lines: zulip/integrations/bridge_with_slack/README.md
-34
Original file line number
Diff line number
Diff line change
@@ -44,37 +44,3 @@ This is a bridge between Slack and Zulip.
44
44
### Running the bridge
45
45
46
46
Run Slack Bridge: `python3 run-slack-bridge`
47
-
48
-
<details>
49
-
<summary>Legacy: If you're still using classic Slack app, follow this instruction instead!</summary>
50
-
51
-
### 1. Zulip endpoint
52
-
1. Create a generic Zulip bot, with a full name like `Slack Bot`.
53
-
2. (Important) Subscribe the bot user to the Zulip stream you'd like to bridge your Slack
54
-
channel into.
55
-
3. In the `zulip` section of the configuration file, enter the bot's `zuliprc`
56
-
details (`email`, `api_key`, and `site`).
57
-
4. In the same section, also enter the Zulip `stream` and `topic`.
58
-
59
-
### 2. Slack endpoint
60
-
1. Make sure Websocket isn't blocked in the computer where you run this bridge.
61
-
Test it at https://www.websocket.org/echo.html.
62
-
2. Go to https://api.slack.com/apps?new_classic_app=1 and create a new classic
63
-
app (note: must be a classic app). Choose a bot name that will be put into
64
-
bridge_with_slack_config.py, e.g. "zulip_mirror". In the process of doing
65
-
this, you need to add oauth token scope. Simply choose `bot`. Slack will say
66
-
that this is a legacy scope, but we still need to use it anyway. The reason
67
-
why we need the legacy scope is because otherwise the RTM API wouldn't work.
68
-
We might remove the RTM API usage in newer version of this bot. Make sure to
69
-
install the app to the workspace. When successful, you should see a token
70
-
that starts with "xoxb-...". There is also a token that starts with
71
-
"xoxp-...", we need the "xoxb-..." one.
72
-
3. Go to "App Home", click the button "Add Legacy Bot User".
73
-
4. (Important) Make sure the bot is subscribed to the channel. You can do this by typing e.g. `/invite @zulip_mirror` in the relevant channel.
74
-
5. In the `slack` section of the Zulip-Slack bridge configuration file, enter the bot name (e.g. "zulip_mirror") and token, and the channel ID (note: must be ID, not name).
75
-
76
-
### Running the bridge
77
-
78
-
Run Legacy Slack Bridge: `python3 run-slack-bridge --legacy`
0 commit comments