Earlier quoted context omitted.
What an overwrought headline, the employee in question has already been fired.
The company in question is still operating. We don't know if the employee was just a scapegoat.
[deleted]
Slack is down
491–500 of 840 posts
Re: Slack is down
#492Here is to hoping it's not SolarWinds related eh!
Re: Slack is down
#493A great opportunity to try out Element, an open source client for the federated and open Matrix network [1]: https://element.io/
(edit: to clarify: not affiliated in any way, just a fan)
Re: Slack is down
#494I am genuinely surprised that Slack wasn't ready for people to come back from holiday, to view increased queues of unread messages, to have to manually login vs. having auth tokens or cookies, etc. Either that, or they had a cosmically coincidental outage on a really bad Monday to have it. It's bad enough team comms go over Slack so much now, at least we have email fallback. What scares me is for the teams that use S…
Slack has been in business for several years and has survived several December to January transitions, including several people stopping using their product before Christmas and then returning early January.
It seems a bit presumptuous to assume that's at fault here, given their age.
Re: Slack is down
#495Earlier quoted context omitted.
That scenario is what Disaster Recovery plans are for. Every large company I've worked for has had recovery plans in place, including scenarios as disturbing as "All data centers and offices explode simultaneously, and all staff who know how it all works are killed in the blasts." You not only have backups in place, you have documentation in place, including a back-up vendor who has copies of the documentation and ca…
That’s some really good thoughts on DR planning. I have never thought DR to be to such an extent. How many companies really plan for an event where their entire infrastructure goes offline and their entire team gets killed? Does even companies like Google plan for this kind of event?
> How many companies really plan for an event where their entire infrastructure goes offline and their entire team gets killed?
Since 9/11, more than you might think. For example Empire Blue Cross Blue Shield [1] had its HQ in the WTC.
https://www.computerworld.com/article/2585046/empire-blue-[1... cross-it-group-undaunted-by-wtc-attack--anthrax-scare.html
Re: Slack is down
#496Earlier quoted context omitted.
Indeed, if you champion FOSS, why would you recommend a proprietary piece of software as fallback?
My point was really that it's GitLab's own product. "GitLab Mattermost" [ https://docs.gitlab.com/omnibus/gitlab-mattermost/ ] I'm amazed they use Slack at all. Let alone as a fallback.
They posted a giant list of the services they use recently.
They use a ton of services.
Likely you don't want your backup to be one of your systems and another part of the company probably uses Zoom already so it is probably easy to fail over to that.
Re: Slack is down
#497I read somewhere that Slack's yearly uptime SLA is 99.99%, which has already been exceeded on January 4th.
Sending big hugs to their ops team.
Re: Slack is down
#498Earlier quoted context omitted.
Maybe my DevOps folks should not be privy to all internal communications? That is one reason we did not go with Mattermost.
If you do not trust your own devops, why are you trusting someone elses devops?
Because someone else's devops can't use it against you institutionally. Nor is going to insist on having an opinion on things that they're unaffected by.
This isn't a slam at devops, it's about the need for institutional information hiding; not everyone needs to know about and weigh in on every decision being made.
Re: Slack is down
#499Give Telegram a chance. It's worth it!
telegram.org
Re: Slack is down
#500Give Telegram a chance. It's worth it! telegram.org
Do you recommend it for use by teams?