6 ms·
Why not simply use IRC?
by rwmj 9y ago
Why not simply use IRC?
- ben174 9y agoAt TiVo we used IRC. It was so nice.
- diggan 9y agoMy fear is not about Slack specifically, but in general the tools we're using today. They all assume that you have a internet connection at all times, and they just break when I don't. Even though when it's just about passing a few JSON objects around, that could easily be sent locally.
- cgag 9y agoemojis
- strictnein 9y agoASCII art > emojis
- cgag 9y agoyeah but doing gifs is brutal
- MaxLeiter 9y agohttps://sr.ht/lP5u.png https://sr.ht/lP5u.png
- throwanem 9y agoBecause, while you can by dint of extreme effort produce a user experience with IRC that's broadly comparable with what Slack offers out of the box, doing so requires so much relatively rare expertise, and so much more support investment, that it's not cost-effective to do so.
- walrus01 9y agoWe have an IRC server that lives in private IP space and is only accessible by VPN. It was not rocket science to set up. If you think that running ircd-hybrid on debian requires "rare" expertise, then your definition of rare and mine do not exactly match.
- throwanem 9y agoRunning an ircd doesn't require rare expertise. Running an IRC infrastructure that your sales team can and will use, that's as reliable as Slack is - well.
- u801e 9y agoIs using an IRC client any less intuitive compared to using a locally installed Slack client (or, in the past, using something like AIM, MSN Messenger, Yahoo Messenger, Google talk, etc)?
- walrus01 9y agoin my opinion, no, there are a lot of perfectly usable GUI IRC clients. technical teams can use irssi from the command line.
- throwanem 9y agoNo, as long as you pick a client that supports automatic image unfurling, file sharing via some cloud storage service or other, a broad range of emoji including customizable ones (people care more than you think!), and run a bouncer so your users don't lose their entire scrollback every time they disconnect. I'm not saying that an IRC experience comparable to Slack can't be achieved. I'm saying that it is so much work to do so that, for many organizations, just paying Slack a few bucks a user makes a lot more sense than sinking scarce and vastly more expensive engineer time into reinventing that particular wheel.
- walrus01 9y ago
- wmil 9y agoIt's blocked by 90% of corporate firewalls. So trying to get started on using IRC requires big buy in from the network admins.
- saltcured 9y agoI now use the same XMPP client to talk to Slack that I previously used with our own local chatrooms hosted on ejabberd. However, others in my team are very dependent on the part of Slack that is less like XMPP or IRC: the built-in persistence that lets them scroll back or search for stuff that happened while they were away. This is clearly important to some people, who also bodged together persistence for XMPP or IRC using various bots or artfully deployed console clients in screen/tmux sessions on remote servers. I always found it strange, since I expect chat to be ephemeral. For asynchronous communication, I wish all these folks had learned how to use email or usenet properly, since I think threaded discussion on mailing lists or newsgroups was far superior to what we have now in any of these popular replacements. I still don't quite understand whether there is a majority opinion that "rooms", "channels", or serialized message boards are somehow a better UX for the average mind, or if it's really just the distortion of rent-seeking businesses always building this form that is easier to control and monetize for some reason.
- u801e 9y ago> I now use the same XMPP client to talk to Slack that I previously used with our own local chatrooms hosted on ejabberd. Have you had issues with your client taking a long time to negotiate a connection over Slack's XMPP gateway? I had that issue with Thunderbird's chat client and ended up having to switch over to the IRC gateway instead.