Publish blogpost about decomissioning the Slack bridge

content/blog/2025/11/2025-11-27-removing-slack-bridge.md

@@ -0,0 +1,38 @@
++++
+date = "2025-11-28T09:30:00Z"
+title = "Retiring the Slack Bridge on matrix.org"
+
+[taxonomies]
+author = ["Amandine Le Pape"]
+category = ["Cryptography", "Encryption", "Spec"]
++++
+
+Bridges are one of the reasons Matrix is called Matrix: let’s matrix all the networks together! They are key to onboard new users into the network. However, maintaining and operating bridges, in particular to closed, proprietary platforms, is expensive: they need to be kept up to date with any change made by the platform on a regular basis and they’re fiddly to keep up and running.
+
+<!-- more -->
+
+The Matrix.org Foundation has been hosting a free of charge Slack bridge for users of the [matrix.org server](@/homeserver/_index.md) for several years. The code of the bridge [belongs to the Foundation](https://github.com/matrix-org/matrix-appservice-slack), hosted under its GitHub workspace, but the bulk of the maintenance was done by Element. Maintaining and operating bridges to closed, proprietary platforms such as Slack comes at a high cost, both financially and in terms of reliability as they are subject to change without notice. The bridge has been unmaintained for some time now, and this has led to degraded functionality and inconsistent performance for users. While we understand that some people still find it useful in certain cases, it is not right to continue providing a service that we know does not meet the standards expected of matrix.org.
+
+This is why, without enough customers paying for it and despite the efforts of the community trying to help, Element will not continue to maintain this bridge. As a result, the Foundation will no longer provide this service to matrix.org users. We want to thank Element for all these years of graciously maintaining a bridge for us.
+
+## What this means for users
+
+The Slack bridge will be removed from **matrix.org** on **January 13**. After this date, rooms connected to Slack will stop receiving new messages, and no new connections will be accepted. Existing messages and room history in Matrix will remain available, but the link to Slack will be closed.
+
+Users who rely on Slack bridging are encouraged to take over its maintenance, find a supplier who can maintain it for them, or [explore alternatives](@/ecosystem/bridges/slack/_index.md). If you operate your own Matrix homeserver, you are able to host your own instance of the Slack bridge or develop one that suits your needs. However, please note that ongoing maintenance will be required to keep such a bridge functioning as Slack evolves its APIs.
+
+The following bridges will remain online.
+
+| Instance | Platform | Project                                                                       |
+|----------|----------|-------------------------------------------------------------------------------|
+| OFTC     | IRC      | [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc/) |
+| Snoonet  | IRC      | [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc/) |
+| Bifrost  | XMPP     | [matrix-bifrost](https://github.com/matrix-org/matrix-bifrost)                |
+
+## Looking ahead
+
+Bridges are an important part of the Matrix ecosystem. They connect Matrix rooms to conversations on other platforms, helping users communicate without needing to maintain multiple accounts or abandon existing communities. They also help onboard users in the Matrix network. This bridging capability allows Matrix to act as a unifying layer across fragmented chat systems.
+
+Many of these bridges — including those for IRC, WhatsApp, and others — are developed and maintained by community contributors, and we want to acknowledge and thank everyone who has contributed to this ecosystem.
+
+Deprovisioning Slack bridge for matrix.org users does not signal a retreat from the goal of Matrix bridging to other platforms. Bridges remain a valuable part of the Matrix ecosystem, and the Foundation continues to support their development — especially those that connect to open protocols and standards.

content/ecosystem/bridges/slack/bridges.toml

@@ -1,63 +1,63 @@
 [[bridges]]
-name = "matrix-appservice-slack"
-maintainer = "Matrix.org Foundation"
+name = "mautrix-slack"
+maintainer = "Beeper, Tulir"
 summary = """
-The bridge allows you to connect Matrix rooms and Slack channels together. It supports bridging via webhooks or via a
-dedicated slack integration (using the Events API). The bridge supports nearly all matrix message types and client features
-with active development on new features as they arrive. Check the list below for feature support.
-
-The bridge is regularly hacked on and is accepting new PRs for bugfixes and features, come and get involved!
+A Matrix-Slack puppeting bridge. Written in Go using a fork of
+[slack-go](https://github.com/slack-go/slack)
 """
-maturity = "Stable"
-language = "TypeScript"
-license = "Apache-2.0"
-docs = "https://matrix-appservice-slack.readthedocs.io/en/latest/getting_started/"
-repo = "https://github.com/matrix-org/matrix-appservice-slack"
-room = "#matrix_appservice_slack:cadair.com"
+maturity = "Beta"
+language = "Go"
+license = "AGPL-3.0-or-later"
+docs = "https://docs.mau.fi/bridges/go/setup.html?bridge=slack"
+repo = "https://github.com/mautrix/slack"
+room = "#slack:maunium.net"
 featured = true
-privilege.platform = "Admin" # Free text
+privilege.platform = "User" # Free text
 privilege.matrix = "Homeserver Admin" # Any of Homeserver Admin, Room Admin, None
 [bridges.supports]
 dm = true
 channels = true
 formatted_text = true
 message_media = true
 mentions = true
-threads = false
+threads = true
 redactions = true
 editing = true
 reactions = true
 presence = true
-typing_notifications = false
+typing_notifications = true
 
 [[bridges]]
-name = "mautrix-slack"
-maintainer = "Beeper, Tulir"
+name = "matrix-appservice-slack"
+maintainer = "Matrix.org Foundation"
 summary = """
-A Matrix-Slack puppeting bridge. Written in Go using a fork of
-[slack-go](https://github.com/slack-go/slack)
+The bridge allows you to connect Matrix rooms and Slack channels together. It supports bridging via webhooks or via a
+dedicated slack integration (using the Events API). The bridge supports nearly all matrix message types and client features
+with active development on new features as they arrive. Check the list below for feature support.
+
+The bridge is regularly hacked on and is accepting new PRs for bugfixes and features, come and get involved!
 """
-maturity = "Beta"
-language = "Go"
-license = "AGPL-3.0-or-later"
-docs = "https://docs.mau.fi/bridges/go/setup.html?bridge=slack"
-repo = "https://github.com/mautrix/slack"
-room = "#slack:maunium.net"
-featured = true
-privilege.platform = "User" # Free text
+maturity = "Obsolete"
+language = "TypeScript"
+license = "Apache-2.0"
+docs = "https://matrix-appservice-slack.readthedocs.io/en/latest/getting_started/"
+repo = "https://github.com/matrix-org/matrix-appservice-slack"
+room = "#matrix_appservice_slack:cadair.com"
+featured = false
+privilege.platform = "Admin" # Free text
 privilege.matrix = "Homeserver Admin" # Any of Homeserver Admin, Room Admin, None
 [bridges.supports]
 dm = true
 channels = true
 formatted_text = true
 message_media = true
 mentions = true
-threads = true
+threads = false
 redactions = true
 editing = true
 reactions = true
 presence = true
-typing_notifications = true
+typing_notifications = false
 
 [[bridges]]
 name = "matrix-puppet-slack"
@@ -71,7 +71,7 @@ part of the [matrix-puppet-bridge](https://github.com/matrix-hacks/matrix-puppet
 suite of puppetting bridges. It can be used for existing chats, rather than
 initiating new ones.
 """
-maturity = "Beta"
+maturity = "Obsolete"
 language = "Javascript"
 license = "Licence unknown"
 repo = "https://github.com/matrix-hacks/matrix-puppet-slack"