Slack Is Shutting Down Its IRC Gateway (slack.help)

Slack, a team collaboration communication service, has updated its IRC support page to note that it is ending support for IRC on its platform: Unfortunately, support for gateways is ending. Starting on May 15th, it will no longer be possible to connect to Slack using the IRC and XMPP gateways. In another support page, which requires you to log in to one of your Slack groups, the company elaborates: As Slack has evolved over the years, we've built features and capabilities -- like Shared Channels, Threads, and emoji reactions (to name a few) -- that the IRC and XMPP gateways aren't able to handle. Our priority is to provide a secure and high-quality experience across all platforms, and so the time has come to close the gateways.

Please note that the gateways will be closed according to the following schedule: March 6, 2018: No longer available to newly-created workspaces; April 3, 2018: Removed from workspaces where they're not in use; May 15, 2018: Closed for all remaining workspaces.

Comments

Re:TLDR;

[Anonymous Coward]

Might also remind them that Slack owns what you send them.

Self-Host. Problem solved.

[Dr.Dubious DDQ]

At the risk of committing heresy in public: I actually kind of like the Slack-style chat functionality.

I hate the idea of letting some third party proprietary host (like Slack) decide how and when it should work for me, though.

Personally, I'm running a Rocket.Chat instance - very Slack-like (and "Slack-compatible" if you have any bots you've developed for Slack's API that you want to use). Mattermost is another, similar option.