Re:Slack is down
by walrus01 on Tuesday January 09, 2018 @03:18PM
(#16109592)
We 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.
[ Parent
| on HN ]
Running 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.
Is 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)?
No, 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.
There are a number of people that will say automatic image unfurling and file sharing are unwanted features which also pose security risks, if you want to operate a truly internal-only text chat system...
If you want a truly internal-only text chat system for security reasons, you're not looking at Slack to begin with.
in my opinion, no, there are a lot of perfectly usable GUI IRC clients. technical teams can use irssi from the command line.
Re:Slack is down
by monkeywork on Tuesday January 09, 2018 @06:33PM
(#16111181)
and does your IRC server / client combo work in a seamless manner with consistent user interface over practically all platforms? does it allow for chat history to be easily seen? does it allow the user experience that the non technical members of the company need to actually use it?