My mind went completely diff direction after reading "Incident AT".
Same, this read like workplace violence. "Outage At" would be more accurate.
Incident at Slack
51–60 of 96 posts
Re: Incident at Slack
#52I find slack so bloated and slow it would probably take me about 15 minutes to realise it was actually down.
Slack should develop native apps now as they are no longer a lean startup and can afford to build native apps.
Re: Incident at Slack
#53I'm a bit baffled that a company with a communication tool like Slack does not communicate about these incidents _through_ slack itself. Why can't there be a little service notification somewhere in the screen? I know it wouldn't help much when the entire service is down, but when parts fail won't it be helpful to at least indicate this to the user? Or might that be due to potential negative brand marketing that spri…
That feels like spam to me. Tell me image uploads aren't working exactly when I try to upload an image and no sooner. Or possibly keep some global in-app feature status page I can check on demand, but I don't want notifications about services and/or features I'm not currently using.
Re: Incident at Slack
#54I wonder if there is a market for making a clone of slack, which syncs all data from slack, simply for use when slack is down. Big companies could pay monthly for "slack redundancy" from a third party.
What I really wish is some glue layer kind of service that will sync slack with email or teams or something like that so I can do without any one service.
Re: Incident at Slack
#55I find slack so bloated and slow it would probably take me about 15 minutes to realise it was actually down.
Slack should develop native apps now as they are no longer a lean startup and can afford to build native apps.
Slack should at least bridge to an open protocol, if not use one outright, so I can use any client I want.
Like they used to.
Re: Incident at Slack
#56Re: Incident at Slack
#57Earlier quoted context omitted.
> but I don't consider image uploads issues with no technical explanations news-worthy and valuable enough for HN Have you read the status entry? Among other things, calls is also affected.
Still not an "incident at Slack".
Disagree. Last outage was a slow degradation in usability. I appreciate when companies are transparent and upfront.
Re: Incident at Slack
#58Re: Incident at Slack
#59Earlier quoted context omitted.
No, not really. If your calls time out, ping the status server. Done. It sounds more like laziness than complication to me. But that typifies Slack dev culture—“just use duct tape”
And that's exactly how you DDOS your status server.
Why can't they put a status.json file on S3/CloudFront/R2/wherever?
And in an absolute worst-case infra collapse, someone there could manually edit/upload a new one...
Re: Incident at Slack
#60I find slack so bloated and slow it would probably take me about 15 minutes to realise it was actually down.
Slack should develop native apps now as they are no longer a lean startup and can afford to build native apps.
I can't work out why you wouldn't develop a native app anyway - all this scaffolding in a Web UI to imitate native controls (like menus) seems completely backwards to me. Seems just lazy, but in an odd way because writing native apps isn't rocket science or difficult.
It's not like they're implementing thousands of native controls or user interface components - a listview with an edit box at the bottom...