Slack app classic deprecation, can't add new bots since 06/06/2024

[bmalynovytch]

Describe the bug
Slack has deprecated the "Slack app (Classic)" bots, which prevents from adding new bridges with Slack.
See https://api.slack.com/changelog/2024-04-discontinuing-new-creation-of-classic-slack-apps-and-custom-bots

To Reproduce
Try to add a new Slack bot configuration with https://api.slack.com/apps?new_classic_app=1, as stated in the documentation (https://github.com/42wim/matterbridge/wiki/Slack-bot-setup#create-the-classic-slack-app)

Expected behavior
A new bot should be added.

[bmalynovytch]

Question: should the Wiki page be updated with new (working) instructions describing how to setup the bot or should the Slack codebase be completely rewritten ?

[pge]

Question: should the Wiki page be updated with new (working) instructions describing how to setup the bot or should the Slack codebase be completely rewritten ?

Well, i urgently need working instructions. Even if you dont update the wiki, can you hint me towards a solution? :)

[bmalynovytch]

Well, i urgently need working instructions. Even if you dont update the wiki, can you hint me towards a solution? :)

Same for us, we can't link new teams anymore :(

[nosovk]

It would be nice to have some instruction.

[ahonnecke]

I, also would very much like to get this working. I have a slack workspace and I'm ready and available to test a beta version if there's something bleeding.

[MoralCode]

it looks like one of the forks has a commit to add this? unsure how well its made though

tippl@42e75e2

[nosovk]

@tippl were you able to launch new slack on your branch?
I can't get it to work, according to https://github.com/tippl/matterbridge/blob/master/bridge/slack/slack.go#L111-L115 there should be both AppToken and Token in slack config? It should be the same token twice?

[tippl]

@nosovk The commit in my fork linked above as well as the snippet linked are fully taken from already open PR #2161.

I've added some additional improvements (and bugs) in my fork, but the new slack integration is fully not mine.
You can follow the guide in the PR to help you configuring the new Slack API.
But in short, yes, you need 2 different tokens, the bot user token and an app level token.

[slack]
    [slack.mybot]
    Token="xoxb-*******"
    AppToken="xapp-**********"

Ignoring some bugs and nil dereferences i caused in my "improvements" I've been actively using my fork since it has been created, and the slack integration is working great. Though i can only confirm functionality when syncing Slack <-> Discord, since i haven't used, nor tested it with anything else.

[MoralCode]

since i haven't used, nor tested it with anything else.

i could probably test it in a very small, essentially empty community i run that bridges slack, discord, and some matrix related things. my main blocker for doing this is having enough time to actually do it though

[alsotoes]

@MoralCode @tippl I can configure the info about my community bridge and a DigitalOcean pipeline to auto-deploy the bridge when a branch changes. Let me know if this helps
-Alvaro

[tippl]

@alsotoes Feel free to do what you want.

Anyone is free to use my fork for the small Discord featureset tweaks, or the repo from the original PR i linked if you just want new Slack compatibility (I took that commit wholesale), or just further fork and continue development.

I've already had a person contact me to help him setup the Slack API. I don't have issues with people using the fork (that is the beauty of open source and why i didn't just private fork), but I have a bit mixed feeling about people using it too, given that this project is my first time working with GO, so if it were to become a popular fork, I have low skill and willingness to test and maintain it.