Slack Bot

[misslivirose]

The majority of the functionality of the Hubs Slack bot will follow the design patterns established by the Hubs Discord Bot design document. This document outlines the differences that are specific to building bots for Slack vs. Discord, but the overall functionality will remain aligned.

Permissions Rooms created by a channel member via the Slack bot and bound to a Slack channel will follow the same topic modification to link a room. Unlike Discord, Slack does not automatically add users to channels by specific roles, and public channels can be previewed by Workspace members. Rooms should authenticate by who is able to see the channel that the bound room is linked to.

Bot Commands Slack bot commands are trigggered by ‘/ <command>’ instead of Discord’s ! syntax. Additionally, Slack provides the ability for messages to only be visible to the user who queries the bot, rather than broadcasting to the entire channel. Slack also allows bots to make use of APIs that provide buttons, so there could be opportunities to introduce new, user-triggered broadcasting features that could provide greater engagement in channels that are directly tied to community actions.

Features /hubs commands that display a status message should be visible only to the user who wants to get the information

Considerations Slack allows threaded conversations, so we may want to consider if there is additional logic we want to support for users who thread a bot conversation.

┆Issue is synchronized with this Jira Task

[robinkwilson]

Pull Requests for the oauth current slack bot: https://github.com/mozilla/hubs/pull/2571 https://github.com/mozilla/reticulum/pull/383