search

saltstack / salt

Software to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here:
https://repo.saltproject.io/
Apache License 2.0
14.16k stars 5.48k forks source link

Community Slack<-->IRC bridge may no longer work #56572

Closed waynew closed 3 years ago

waynew commented 4 years ago

From gtmanfred on the community Slack

thing I thought about that you should probably look into for this slack, slack is ending support for legacy tokens in may, which will mean that the slack <-> irc bridge in #formulas and #irc will stop working. If you have a desire to keep those two communities connected, you might want to look into it. Currently it uses https://irc3.readthedocs.io/en/latest/plugins/slack.html and uses the websocket gateway through the legacy tokens, but will probably have to switch to using the newer app model with a callback server.

It would be useful to get some effort to get a supported replacement.

gtmanfred commented 4 years ago

subscribe so I can unstale this in 30 days.

myii commented 4 years ago

If this works, it opens up bridging across a number of protocols:

freelock commented 4 years ago

I'm already in the #salt IRC channel via Matrix -- the Matrix - IRC bridge is not going anywhere.

It's pretty easy to bridge between Matrix and Slack -- Matrix has a hosted bridge available, and I run my own Slack bridge so that I can bridge into some private Slacks.

This might be a relatively painless way to keep the channels from getting fragmented. Plus things like threaded replies, reactions, and message edits could be preserved between Matrix and Slack with a direct bridge, with IRC still getting the message text (and automatic shortening/linking of rich messages from the other two...)

myii commented 4 years ago

@freelock Are you using https://github.com/matrix-org/matrix-appservice-slack?

I myself use Matrix but while I'm familiar with using it to connect to IRC (I do that right now with the #formulas channel), how does it work the other way around? What address would IRC users connect to?

freelock commented 4 years ago

Yes, that's the bridge I'm using...

The current Freenode #salt channel is in Matrix as #freenode_#salt:matrix.org . I think we can just add the Slack bridge in that room, and then nothing has to change at all for IRC users.

To bridge to Slack, somebody would need to add an app to the Slack team. I think Matrix-side, anybody can initiate that in Riot using the "integrations manager", and that will walk through what's needed on the Slack side.

For a self-hosted bridge (like mine) it's a different Slack app than the one that Riot hosts -- the app needs to be added to the team, and then the associated bot gets invited to the Slack channel and Matrix room. Finally, there's a slack control room for the bot, where the bot owner connects the Slack channel with the Matrix room. It's all pretty easy -- my bridge is currently bridging about 20 Matrix rooms into Slack channels across 6 different Slack teams...

Both the Matrix-hosted and my bridge use the same code base, matrix-appservice-slack -- but the Matrix one has a bunch of other UX in place so users can self-serve to set them up.

sagetherage commented 4 years ago

@cassandrafaris @TheDynaMoe

myii commented 4 years ago

We've got a trial going where we've got bridging between Slack <= Matrix => IRC (update: also Gitter bridged from Matrix). If anyone cares to try it out, these are the details:

Platform Address
Slack #test-irc-bridge2
Matrix #SaltStack_test-irc-bridge2:matrix.org
IRC ##SaltStack_test-irc-bridge2
Gitter saltstack-formulas/SaltStack_test-irc-bridge2

(Thanks for the Matrix address correction, @freelock).

freelock commented 4 years ago

just to clarify, the Matrix address is #SaltStack_test-irc-bridge2:matrix.org ...

Cheers, John

myii commented 4 years ago

Bridge to Gitter also integrated for testing. I've added the address to the table above.