News for hackers. Stuff that matters.

A comment on A major reason for departures at Slack was “remote work request rejected”. Parent comment

Re:A major reason for departures at Slack was “remote work r... by Twirrim on Monday May 25, 2020 @01:07AM (#23298022)
We'd just made the transition from local hosted HipChat over to Slack about a month before a _big_ outage occurred. The team responsible for the internal tools got told by management to do some herculean efforts to get hipchat temporarily resurrected.

I logged in to my desktop machine, and had IRC up and running in under 5 minutes and had details out to the team ready to use it should an emergency strike. It's _really_ simple to spin up an IRC server for such purposes. Just about the time the Slack outage was over, the HipChat server was back and working again... :) (there's a lot of reasons why it took so long, and it wasn't really Atlassian's fault)

[ Parent | on HN ]
Re:A major reason for departures at Slack was “remote work r... by bArray on Monday May 25, 2020 @01:54AM (#23298321)
It genuinely is impressive. The protocol itself is so simple that building something like a bot to write the results of builds is a job that can easily be done in a day (assuming you're completely working from scratch, i.e. pushing bytes over sockets).

There are quite a few clients that even support encryption, so it's not even necessarily insecure either.

[ Parent | on HN ]