7 ms·
Slack is Down
- mcrittenden 10y agoSeems to be up for me again. I wonder if 8 minutes of downtime is enough to warrant a post-mortem blog post.
- muglug 10y agoFor a product as widely-used as Slack is, it might at least be interesting.
- gooseus 10y agoGiven the increasing dependence on messaging platforms, I think any widespread downtime deserves a public post-mortem. And that's not to speak to the amazing amount of curiosity and interest that any downtime in a large public system generates. From the PR side, I would think that some kind of post-mortem is almost necessary to prevent that curiosity and interest from turning to distrust and negative perception.
- fiatjaf 10y agoOf course not.
- oxguy3 10y agoEh, I don't think a post-mortem is really necessary. They said it was a broken code change on the status page. If they wrote a post-mortem, it'd probably just say "A team member forgot to foobar the bazqux when deploying an update. We immediately followed our playbook for rolling back a failed deployment and restored service within 9 minutes."
- ptrptr 10y agoSlack is down, productivity goes up... after using it for a while I find it does communications within a team well but does almost nothing to increase collaboration, so I guess slack is in area which apps like Discord will disrupt.
- RussianCow 10y agoI don't disagree with you, but in what way do you think Discord will "disrupt" Slack with regards to collaboration?
- astrodust 10y agoDiscord's a compelling alternative, but it's just another flavour of same. If you want distributed you need something more like IRC or at least federated XMPP.
- RussianCow 10y agoI don't think making it distributed solves the productivity problem, though.
- Operyl 10y agoErr, I find myself wasting much more time in Discord, music bots etc, hah.
- bernardlunn 10y agoI stopped using Slack. It is a productivity drain.
- seattle_spring 10y agoI feel like this is about as relevant to this discussion as someone arrogantly interjecting, "Oh I don't own a TV," when talking about Netflix shows.
- tapvt 10y agoI've been tempted to stop using it, but instead just shut off notifications. I really like being able to pull it up quickly to see when code has been pushed up, pull requests created / merged, or whatever automated CI action is going on for a particular project. The chatter can burn a lot of time though. You're absolutely right there.
- user5994461 10y agoI didn't have anything to stop notifications last I checked. Had to uninstall the app.
- avenoir 10y agoUsing MS Teams at the office and I couldn't agree more. It's useful about 30% of the time. The other 70% is sharing giphies and news links.
- ncallaway 10y agoWe solved this by creating a separate channel for gifs and news. Those interested can participate, those not interested can just mute the channel and ignore it.
- aantix 10y agoI wish they had an option to only notify me of images and gifies. I have no idea what the other stuff is about..
- 10y ago
- dsr_ 10y agoIt's harder (but not impossible) to have complete service lossage like this in a federated protocol. That's why you didn't hear about the great email collapse of 2006.
- ajross 10y agoAnd relevant to the market: why Freenode netsplits are more of a joke than a problem.
- gizmo686 10y agoOf course, if my email goes down, it does not help me that other's is still up. In fact, if total downtime is constint, I would prefer they overlap.
- verelo 10y agoWell fortunately with the major influence Gmail has in the personal email and work email space these days, your wish is somewhat true. Having said that, Google certainly run many many mail servers, as such an outage that impacts delivery for one group of people does not necessarily impact everyone. This is the difference between robust systems and those with critical lynch pins that create system wide outages.
- amelius 10y ago> In fact, if total downtime is constint, I would prefer they overlap. So the people who are supposed to do work for you also can't work?
- gizmo686 10y agoI meant total downtime for each user. So if I lose email for an hour, and my worker loses email for an hour, it is better if those are the same hour, otherwise there are two hours when we can't email each other.
- derefr 10y agoIf our email is down but our customers' email isn't down, then they think we're ignoring their "urgent" messages, and that's bad. But if everyone's email is down, they won't be able to send those messages, so they won't think we received them to ignore them. (Then again, email is kind of uniquely bad here, because of the way SMTP works as a store-and-forward protocol. In most protocols, if my server went down, your client wouldn't be able to connect to it, so it'd be pretty clear something is wrong. With SMTP, your client can just "put a message on the Internet" for my server to receive, and won't know for 48 hours or more that my server isn't there any more.)
- Csmeron 10y agoI don't see that type of unprofessional behavior among the users I collaborate with. I guess that's the drawback to working with Millennials. Lazy and time-wasting and always think they are new or funny.
- jon-wood 10y agoI assume you also don't talk with coworkers about what you did at the weekend, or discuss where to get lunch. You wouldn't want to waste any of your employers precious time.
- dang 10y agoPlease keep pointless generation wars off HN. We detached this subthread from https://news.ycombinator.com/item?id=13812246 https://news.ycombinator.com/item?id=13812246 and marked it off-topic.
- deleted 10y ago[deleted]
- mcrittenden 10y agohttps://status.slack.com/2017-03/c0923f37c54988ec https://status.slack.com/2017-03/c0923f37c54988ec - basically just said that there was a broken code change which they reverted.
- rudolf0 10y ago>The status.slack.com was also overloaded during this time and it may have been inaccessible. This is starting to become a common theme...