matrix-appservice-slack

Is there going to be more muscle put into polishing up the various bridges? Matrix has an amazing opportunity to be the glue protocol between various communication silos, but there's a few things I've encountered that have been preventing me from using it further. One issue I hit is this: https://github.com/matrix-org/matrix-appservice-slack/issues... I tried pinging the people that were committing to the repo on the matrix channel for that bridge, but never got a response and now I'm just stuck with a room with a dead bridge. It's not a huge deal since the Matrix side of things still works, but having some way to reach out for stuff like that would be really helpful. The other thing is this issue: https://github.com/matrix-org/matrix-appservice-discord/issu... It's not a showstopper since the bridge still works, but it's a lot of managem

there are matrix bridges for all three of those https://github.com/tulir/mautrix-whatsapp https://github.com/Half-Shot/matrix-appservice-discord https://github.com/matrix-org/matrix-appservice-slack

Actually, bridging is actually a first class citizen in Matrix - it's why the project's called Matrix (as we want to go federate/matrix together all the existing silos out there). Current bridges include: * IRC (https://github.com/matrix-org/matrix-appservice-irc) * Slack (https://github.com/matrix-org/matrix-appservice-slack) * Verto (https://github.com/matrix-org/matrix-appservice-verto) (for talking VoIP with FreeSWITCHes) * Respoke (https://github.com/matrix-org/matrix-appservice-respoke) (for talking VoIP with Asterisks) * Purple (https://github.com/matrix-org/node-purple/tree/master/appser...) (for talking through to Skype, Facebook, XMPP, ICQ, AIM... and anything else that libpurple supports) ...and a whole bunch of 3rd party ones too like https://github.com/SkaveRat/xmpptrix. Some of these are pretty beta, but they're all headed