So disappointing that @slackhq is giving up on the gateway between Slack and IRC. I wonder why. No reason given. https://get.slack.help/hc/en-us/articles/201727913-Connect-to-Slack-over-IRC-and-XMPP
Jeremy Cherfaspublished this
XMPP.JP Official liked this post
Chris Aldrich liked this post
Michael Downey 🇺🇳 liked this post
@jeremycherfas I wonder if any other kind of bridge is possible for the IndieWebCamp channels. I connect via Slack and it seems like several other people do as well.
, Mar 07 2018 on micro.blog
Sorry about this. Can you tell us what about Slack makes this a difficult change? We’re more than happy to share possible workarounds.
, Mar 07 2018 on twitter.com
@lukas Wish more of Slack's native API had been built on standards — with extensions where necessary — to avoid this kind of thing. Too easy for them to cut off compatibility after they reach a certain level of success. (Also, welcome!)
, Mar 07 2018 on micro.blog
@manton I wish I knew, but I am by no means expert enough. I generally use IRC, but Slack is handy to catch up and, especially, to remind myself to look at links and things when I get back to my computer. If that is possible in IRC I have not discovered how.
, Mar 07 2018 on micro.blog
@aaronpk Great news!
, Mar 07 2018 on micro.blog
@lukas I wonder how much support it really takes. I don't suppose the API is set and forget, but is it really that time consuming, for a lot of goodwill.
, Mar 07 2018 on micro.blog
@jeremycherfas @manton doesn't matrix.org support this sort of bridging? (also, I think it is interesting when “bridging" is used v. when “tunneling" is used in text describe this sort of linkage)
, Mar 07 2018 on micro.blog
@eli I don't know enough about Matrix or bridging to know. If Slack is giving up on maintaining support for open standards, will Matrix be able to access Slack?
, Mar 07 2018 on micro.blog
The good news is that #indieweb -- the main channel for which I want both IRC and Slack -- should be OK as it uses the Slack API. Or so I am reliably informed ...
how about a blog post explaining your reasoning for the change? without it, we're all left to guess, and the guesses (say, lack of concern for interoperability…) will make Slack look worse than good reasons explained thoughtfully
, Mar 07 2018 on twitter.com
@SlackHQ I like the extra functionality of, eg, reminding myself about messages and the overall usability of Slack. I wouldn't want to be tied to a closed silo though. Bridging with IRC allows #indieweb people to own their messages.
I like the extra functionality of, eg, reminding myself about messages and the overall usability of Slack. I wouldn't want to be tied to a closed silo though. Bridging with IRC allows #indieweb people to own their messages.
, Mar 07 2018 on twitter.com
@manton @lukas @jeremycherfas Stewart Butterfield regretted the IRC support, so I am not at all surprised to see it go.
, Mar 07 2018 on micro.blog
Also on: @EatPodcast
@jeremycherfas Probably lack of usage, which doesn't justify supporting it any longer. But I'm disappointed to see this, too, even though I haven't actively used it myself. Another case of a company shutting down integrations and bridges based on open standards.
lukas, Mar 07 2018 on micro.blog