Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Slack – Degraded service affecting multiple features

status.slack.com

Post reply on HN
Print view View original

101–110 of 246 posts

Re: Slack – Degraded service affecting multiple features

#101

Post by School-Cotton »

jgrahamc wrote: post #97
kevcampb wrote: post #82

Earlier quoted context omitted.

Thanks for the acknowledgement. Appreciate it's hard, false positives etc. Glad you see our PoV.

I do. I'm irritated, however, that you picked on Cloudflare as a bad actor here when we strive to be transparent and quick to get out full information whereas others (e.g. Amazon) are slow as mud. But I get that being on the other side of this is difficult when you don't have information.

Well, it's understandable, if OP has been burned by Cloudflare's slowness in the past, and not by Amazon's.

Re: Slack – Degraded service affecting multiple features

#102

Post by exabrial »

One problem with Slack we have in the finance world is that _literally everything_ employees say on company assets needs to be recorded and readily accessible for audit (No this is not an invasion of privacy, you're on company time on company systems, we don't peer into your personal phone or anything).

Unfortunately, Slack does not do this very well. I'd really like to know if there's another service that _does_ do this well.

Re: Slack – Degraded service affecting multiple features

#103

Post by mac_attack18 »

valerij wrote: post #62

reminds me of that one time a genius at IBM created an `ibm-global-announcements` channel and force-invited 200'000 people in it, and then some guy `@channel`d and all ibm's slack workspaces were down for 30 minutes https://status.slack.com/ibm/2018-03/f01d4c22cd953dd7 https://i.imgur.com/Rk6Kdgp.png EDIT: also that channel made using slack impossible for mac book air users, they had around 80% cpu usage for slack. s…

I remember that day fun times. I just shut off Slack and got back to work was nice not being pinged constantly.

Re: Slack – Degraded service affecting multiple features

#104

Post by Twirrim »

SquishyPanda23 wrote: post #83
darkwater wrote: post #13

Earlier quoted context omitted.

Or not. I'm remote and I cannot ask questions nor coordinate action to solve live production problems due to this outage. Slack is becoming a SPOF for many organizations, especially distributed.

It makes sense to have a fallback method set ahead of time, as others have mentioned. You won't have access to the things slack integrates with but at least you can talk. I know some people use IRC as a low-dependency fallback channel.

At one stage when there was an outage about a year ago, folks at work were scrambling around trying to get HipChat resurrected (which we'd been using prior to moving to Slack).

I had an ircd of some description installed, configured and ready for use in under 3 minutes, and started to get my team using it as a stop gap measure. Had that rolling long before either the outage was resolved, or the HipChat server was resurrected. People forget just how stupidly easy it is to set up IRC.

Re: Slack – Degraded service affecting multiple features

#105

Post by foobarian »

freehunter wrote: post #91
valerij wrote: post #62

reminds me of that one time a genius at IBM created an `ibm-global-announcements` channel and force-invited 200'000 people in it, and then some guy `@channel`d and all ibm's slack workspaces were down for 30 minutes https://status.slack.com/ibm/2018-03/f01d4c22cd953dd7 https://i.imgur.com/Rk6Kdgp.png EDIT: also that channel made using slack impossible for mac book air users, they had around 80% cpu usage for slack. s…

There should be a way to turn off @here and @channel. It should be a user-level setting, a channel-level setting, and an organization-level setting. Even if my org or channel doesn't opt out, I should be able to.

I hate that it can't be controlled per channel. There are many channels where it's useful and desirable, so our org doesn't disable it globally. This creates situations where new people @here and @channel not knowing any better, which leads to hurt feelings all around.

Re: Slack – Degraded service affecting multiple features

#106

Post by whatshisface »

QuickToBan wrote: post #96

Why don't people use free software instead, e.g. a Matrix homeserver run via https://github.com/matrix-org/synapse/ ? IRC without a BNC doesn't really work for a corporation due to disconnects.

How well does Matrix handle VoIP?

Re: Slack – Degraded service affecting multiple features

#107

Post by pmlnr »

yifanl wrote: post #94
pmlnr wrote: post #31

There are reasons why email is async and supposed to be decentralized, with priority based fallback options. (The priority in mx records). Most email servers try to deliver to fallbacks, and even if that fails, will try to deliver for _days_. For all people who think slack can replace email, think about these safeguards.

I don't think any serious IM platform really intended to replace email, they serve different (but related) purposes.

- https://www.nytimes.com/2019/06/19/style/slack-replace-email...

- https://www.brianmcadam.com/5-reasons-replace-email-text-im-...

- https://tech.co/news/slack-replacing-email-workplace-2018-08

[...]

Re: Slack – Degraded service affecting multiple features

#108

Post by TeMPOraL »

dpcx wrote: post #47
ratsimihah wrote: post #43

Earlier quoted context omitted.

Isn't internet a single communication medium anyway?

It is, technically. Good thing there's also phones and SMS.

Both of which increasingly work over the Internet on the backend, from what I hear.

Re: Slack – Degraded service affecting multiple features

#109

Post by ilikehurdles »

freehunter wrote: post #91
valerij wrote: post #62

reminds me of that one time a genius at IBM created an `ibm-global-announcements` channel and force-invited 200'000 people in it, and then some guy `@channel`d and all ibm's slack workspaces were down for 30 minutes https://status.slack.com/ibm/2018-03/f01d4c22cd953dd7 https://i.imgur.com/Rk6Kdgp.png EDIT: also that channel made using slack impossible for mac book air users, they had around 80% cpu usage for slack. s…

There should be a way to turn off @here and @channel. It should be a user-level setting, a channel-level setting, and an organization-level setting. Even if my org or channel doesn't opt out, I should be able to.

Some of this you can already do. Users can opt out of @here and @channel for any given channel. I know that orgs can restrict usage of @everyone, I assume they can do the same for @here/@channel but I'm not sure.

Re: Slack – Degraded service affecting multiple features

#110

Post by pmlnr »

dasil003 wrote: post #85
pmlnr wrote: post #41

Earlier quoted context omitted.

I slipped over the "live" word, but I still stand by what I said. I most probably work in a similar environment, with tonnes of live production issues, and I believe it's a result of not being allowed to proactively plan for situations - most of the issues are a result of cost savings, systems driven to their absolute maximum capacity, etc. Live production issues are a byproduct of moving too fast, breaking too many…

What an incredibly arrogant generalization to make. You know there are also production issues created by moving too slow and failing to address pending scalability issues, right?

heh.

> failing to address pending scalability issues

How is that not related to not getting enough funding and resources?

And yes, having scalability issues means moving too fast - the _business_ moving too fast.

Post reply on HN