Your friendly reminder that slack once had an IRC bridge and they tore it down. The reason was that they could not afford to maintain it. If so, why didn't they opensource it for the community to maintain? Now we have split communities and one more walled garden. And a growing generation that thinks a centralized system owned by a single company is normal. Thanks, slack.

@grindhold So that's why the couchdb channel just... died.

@grindhold no, the problem is that IRC is a protocol not a platform which was held back by graybeards who wanted terminal clients to be the standard. Nobody built a good client/server ecosystem that was cross platform, good GUI, modern features.

IRC can come back if someone improves upon IRCv3 and hides the existence of IRC under some new branding.
@feld @grindhold how is that related to the (non)availability of a bridge?

@feld or they could just open the bridge to the public so that neckbeards can keep their beardy necks in their terminal clients whereas people that prefer to use web-tech as a poor substitute for a real desktop expeprience can do so as well. i prefer the solution that lets everybody do their favourite mistaken way. there is no way to do it right :)

@grindhold the problem is they have to update their code/bridge to filter out every new incompatible feature they add to the platform. i wouldn't want that burden either.

@feld so far i have found few things in slack that could not be mapped to an existing IRC feature. badges could simply be printed as notice "feld badged your message from 15:33 with :+1:" or something like that. Threads can be expressed as temporary channels. Rich content can just be displayed as a link. Searching could be done through a command to slackbot.
It's not that much magic. It just wastes screenspace :)

@grindhold markdown? code formatting? inline images/videos?

There are countless features. Just because YOU don't want them doesn't mean they're not valuable. These are indispensable tools for developers today.

Few developers under the age of 30 wants to use a terminal client. They want something with a nice friendly UX to help them get their shit done so they can go home at 5pm and enjoy their non-computing hobbies.

@feld do you understand my original toot? i do not want to take anyones beloved slack away. i want a feature back that once existed that allowed me to access slack with a neat integration into my setup. without second client. and once again: if they decide they can't maintain it, why don't they give it to the community to maintain it? i think these are reasonable demands that shouldn't offend anyone.

anyway. if they don't want to maintain it, it's fine. but if that bridge is abandonware anyway, why can't they just opensource it, so that others can maintain instead. is the code quality this crappy?

@grindhold because they might have to expose internal APIs they don't want to. It's not your business why they did it.

You clearly are not their target audience. I don't know why you care so much?

I felt the same way a few years ago when my FreeBSD dev channels were getting fractured by the Slack bridge. The most senior members of the team were even tired of IRC.

IRC users: You know Slack, if you're not careful you're going to lose me

Slack: I lost you 2 years ago. Are you mental? We broke up. Get the net!


I care because i am required by external circumstances to use it. I was happy using it through the bridge, deliberately ditching on the features you spoke of (i deem inline display of rich content a security risk rather than a feature tbh) and everybody else was happy using the web- or electron clients.
there was equilibrium, there was balance in the world. but then the fire nation attacked and everything changed.

@feld @grindhold Also, the usual reminder to don't trust corporations to be standards compliant if they can get critical mass enough for lock-in / walled gardening to improve investor value. Slack supported supported IRC for exactly as long as it needed to get enough users into the garden to wall it off.

@max @grindhold Correct, that's exactly what they did. I don't blame them for it. I'd have done the same if I was writing a fancy tech bro chat app to get rich off of.

The only reason it flourishes is because the open source community has been too busy building shit like blockchains instead of tackling problems that have real impact on humanity.

> million dollar startup
> doesnt have the resources to maintain a simple IRC bridge

It pisses me off when companies say they *can't* do something when in reality they just don't *want* to do it.

@grindhold Just another one of the reasons I have been putting off learning #clojure

@yogthos @grindhold Thanks! #Zulip looks pretty cool. How does it compare to #riot ( matrix ) or irc?

@yisraeldov @grindhold the main difference is that it's thread based, which I find actually makes conversations easier to track, and it is open source.

@yogthos @grindhold Well matrix and irc are also open source. Does Zulip federate or do I need a seperate account on each server ? That would be really annoying.

@grindhold seems like the problem is using slack in the first place, not that the bridge died

@grindhold @alanz the cynic in me thinks slack shut down the irc bridge because they had enough users to start to lock them in

@grindhold By the way… Twitter used to have native RSS feeds.

Sign in to participate in the conversation
Social Nasqueron

Nasqueron is a budding community of creative people, writers, developers and thinkers. We focus on free culture, ethics and to be a positive change. We share values like respect, justice and equity.