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.
@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 :)
@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 :)
@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?
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.
> 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.
@yisraeldov i don't get how this relates. could you elaborate?
@yisraeldov lol. i see.
Embrace, Extend, Extinguish
@grindhold use discord
@grindhold If I was an engineer at slack, I would suggest we shut down the bridge too, since emulating slack features over IRC would be a pain I wouldn't want to deal with.
And I fucking love IRC.
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.