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

Slack was down

status.slack.com

Post reply on HN
Print view View original

41–50 of 243 posts

Re: Slack was down

#41

Post by JD557 »

mr__y wrote: post #34
derwiki wrote: post #18

Earlier quoted context omitted.

Comparing one proprietary service to federated and open services? I'm not following you

While email as a whole is indeed federated, email service for a single company is usually not, that is you have a single provider and when that provider happens to have technical issues your email might be down. While obviously you could use other provider (or even free email) almost immediately to send emails, you will not be able to receive/access emails that are sent to your primary address/domain until the provid…

>you will not be able to receive/access emails that are sent to your primary address/domain until the provider resolves their issues.

You won't be able to receive new e-mails, but if you use a local client like thunderbird, you can still access your old e-mails.

With slack down, I can only access the messages that I (luckily) have cached locally.

Re: Slack was down

#42

Post by jedberg »

mr__y wrote: post #34
derwiki wrote: post #18

Earlier quoted context omitted.

Comparing one proprietary service to federated and open services? I'm not following you

While email as a whole is indeed federated, email service for a single company is usually not, that is you have a single provider and when that provider happens to have technical issues your email might be down. While obviously you could use other provider (or even free email) almost immediately to send emails, you will not be able to receive/access emails that are sent to your primary address/domain until the provid…

Except that email has built in retries and feedback. Also it's expected to be async, so if a server is down for an hour, most people don't even notice.

Re: Slack was down

#43

Post by derwiki »

mradonic wrote: post #15

This is becoming so often it's embarrassing really. The way it's handled in the app is also not ideal to say the least - only indication that something is wrong is that the text you are trying to send is greyed out.

Weird, it took me to a status page saying they were having trouble.

Re: Slack was down

#44

Post by Angostura »

freehunter wrote: post #36
derwiki wrote: post #18

Earlier quoted context omitted.

Comparing one proprietary service to federated and open services? I'm not following you

It doesn't really matter how open and federated email is if all mail in/out of your mailbox has to go through one provider. If my company's Exchange server went down, email would stop. Likewise for Internet service... if my local AT&T connection went down, it doesn't matter how open and resilient the Internet is, I'm not getting online until it's fixed.

> f my local AT&T connection went down, it doesn't matter how open and resilient the Internet is, I'm not getting online until it's fixed.

Except that you could work from home, check your e-mail using mobile.

Re: Slack was down

#45

Post by newaccoutnas »

mradonic wrote: post #15

This is becoming so often it's embarrassing really. The way it's handled in the app is also not ideal to say the least - only indication that something is wrong is that the text you are trying to send is greyed out.

Eventually the status bar appears saying they're having an issue.

Re: Slack was down

#46

Post by elwell »

anaphor wrote: post #16

If you're a community driven project or organization using Slack, then take a look at https://zulipchat.com/ for something that sucks less, and is open source software. I've found it much more pleasant to use and less buggy than Slack.

But... we pay managed solutions like Slack so we have 100% uptime...

Re: Slack was down

#47

Post by sorenn111 »

hombre_fatal wrote: post #21
wglb wrote: post #12

Earlier quoted context omitted.

I don't think this is the appropriate forum for "is down" postings. Post-mortems are interesting.

They're upvoted because people can't resist making the same tired "see? we are over-reliant on {Slack,Github,Cloudflare,etc}!" comments.

My favorite are the conspiracy theories as to why the outages are seemingly so close together in this Summer of 2019. All kinds of imaginative reasons abound.

My best guess is summer vacation :) it's at least true for my company who was one of the featured outages

Re: Slack was down

#48

Post by mr__y »

freehunter wrote: post #24
chasedehan wrote: post #7

I really don't like the heavy dependence on Slack that my (and a lot of other) company has. The outage is frustrating.

See, I love it. I work for a mostly-remote company and before Slack we had an IM product but it was a 1:1 chat. Having an always-on chat room for the entire team, knowing other teams use the same product and I can pop into their chat room, spinning up channels for project teams, etc. It's been a huge boost to our company. And since so many companies have settled on the same solution, when I'm working with a client I…

It seems that you could take any old-school internet tech, add some flashy GUI, slap "for enterprise" label and you get a great and popular solution that solves the problem noone ever could solve. Maybe it's time for gopher for enterprise

Re: Slack was down

#50

Post by rolltiide »

ravedave5 wrote: post #9

Since twitter went down the other week hackernews is now the primary 'is it down?' news site.

People just copy what gets engagement.

ex. After an earthquake affecting a large population, you'll see stories about other irrelevant earthquakes leading you to believe a frequency is higher and then that kind of headline dissipates but nothing has changed at all

Post reply on HN