Live data from Hacker News

Slack is down

status.slack.com

591–600 of 840 posts

Re: Slack is down

#591

Earlier quoted context omitted.

Like Guantanamo Bay or prosecution of Assange for his journalistic work to expose wrongdoing of government? Or maybe you’re talking about for-profit prison system and mass incarceration practices? But you’re probably talking about China, right?

Once again, that is a false equivalence. No one imprisoned in Guantanamo Bay is a US Citizen and neither is Assange. The US prison system is super fucked up but it is not the same as ethnic cleansing. You are comparing apples to concentration camps.

We have thousands of brown people in camps along the border, in brutal conditions, without access to healthcare(unless you count forced sterilizations as healthcare). Do you consider those to be apples as well?

Re: Slack is down

#592
post #314
post #258

At GitLab our fallback from Slack is Zoom https://about.gitlab.com/handbook/communication/#emergency-c... I'm posting this because I found a lot of people don't know that Zoom includes a complete chat client that includes channels. And #HugOps to the engineers at Slack working on this. I appreciate that they posted a periodic update even when there was no news to report: "There are no changes to report as of yet. We'…

Just a reminder that it's probably not a wise idea for anyone to get further in bed with Zoom than they already are. https://www.washingtonpost.com/technology/2020/12/18/zoom-he...

[deleted]

Re: Slack is down

#593
post #89

When I was at Uber, we noticed that most incidents are directly caused by human actions that modify the state of the system. Therefore, a large "backlog" of human actions that modify the system state have a much higher chance of causing an incident. My bet is that this incident is caused by a big release after a post-holiday "code freeze".

This is very likely a broken release. The timing lines up with pacific time too well.

Slack does progressive roll-outs. The broken release hypothesis seems very unlikely.

Re: Slack is down

#594
post #551

Earlier 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.

Devops should have nothing to do with your chat server. It should be your IT department, just as with the email server.

DevOps at a lot of small companies also manage the internal IT stack and sometimes even take on most of the IT duties. Once you get larger you start having "IT" as something separate from DevOps but with the actual infrastructure managed by operations. Once you're really big the teams are truly separate and IT owns their own infra.

Re: Slack is down

#595

Like human beings, can we all imagine that every single service can have a couple of off days a year.

The entire point of all of the engineering we talk about around here is to produce services with inhuman capabilities and resilience.

Doesn't that feel like an oxymoron.

If a human created it, it can never have in human capabilities

Re: Slack is down

#596

Earlier quoted context omitted.

I've found that element.io itself is really slow to load. That said, we're pushing up against the limits of our free plan with Slack and will likely deploy a matrix server in due course.

The good thing about that is that if you want a fast client there are quite a few native clients to pick. https://matrix.org/clients/ For example, Mirage is Python/QT and quite fast in my experience. There are Rust clients, C++ clients, terminal based ones, etc.

Do you happen to know of any desktop clients that support encryption/cross-signing?

I'd like to get off of Element desktop/web for a couple of reasons, but I need those features. I'd help implement them myself, but that's beyond my skill level.

Edit: For anyone else wondering, matrix-commander [0] looks like it may be workable if a cli tool is acceptable for your usecase.

[0] https://matrix.org/docs/projects/client/matrix-commander/

I'm planning on looking through the GUI ones at some point, but don't have time now.

Re: Slack is down

#597
post #374

Earlier quoted context omitted.

It is easier to cache stuff for users who are not logged in as it is the same for everyone. and everyone is looking up on Hackernews at the moment to see what is wrong with slack, which is probably the cause of the slowness.

While it is true for most applications. HN does not do any customisation of the content. I don't notice I am not logged in until commenting

The point count for most articles is consistently lower on a view of the non-logged-in homepage. I assume that means they are cached more aggressively for non-logged-in. There's also the username and karma count in the top-right.

Re: Slack is down

#598
post #258

At GitLab our fallback from Slack is Zoom https://about.gitlab.com/handbook/communication/#emergency-c... I'm posting this because I found a lot of people don't know that Zoom includes a complete chat client that includes channels. And #HugOps to the engineers at Slack working on this. I appreciate that they posted a periodic update even when there was no news to report: "There are no changes to report as of yet. We'…

Oh wow -- after years of using Zoom I definitely did not know about this. Thank you for pointing it out!

Re: Slack is down

#599

How many more outages until all trust is eroded and competing services differentiate themselves on the basis of uptime?

You seem to ask the question about the absolute number of outages, whereas uptime is about the number of outages per units of time.

Re: Slack is down

#600

Earlier quoted context omitted.

I wouldn't be surprised if it's actually a combination of a new feature being recently rolled out, along with the sudden spike in load this morning. The holidays are actually the perfect time for Slack to roll out a risky deployment, as it has to be their lowest usage time. So it would make sense if something was pushed out last week or the week before. And everything probably seemed fine. And then this morning they…

Holidays are a good time for a company to do a risky deployment, but a bad time for an individual employee to do a risky deployment, assuming one doesn't want to work overtime over the holiday fixing things.

This depends on how easy/difficult the rollback strategy.
Post reply on HN