News for hackers. Stuff that matters.
Re:Slack outage: Connectivity issues by kevin_thibedeau on Tuesday October 31, 2017 @07:27PM (#15597612)
If only we had distributed realtime communication tech. Walled gardens FTW!
Re:Slack outage: Connectivity issues by outworlder on Tuesday October 31, 2017 @07:40PM (#15597706)
Which distributed realtime communication tech do you propose? IRC? Matrix?
Re:Slack outage: Connectivity issues by denysonique on Tuesday October 31, 2017 @07:33PM (#15597658)
IRC
Re:Slack outage: Connectivity issues by paulddraper on Tuesday October 31, 2017 @07:37PM (#15597687)
Does a non-Slack IRC channel go down less frequently?
Re:Slack outage: Connectivity issues by alrs on Tuesday October 31, 2017 @07:44PM (#15597727)
IRC networks are distributed, so when one server dies you can connect to another.

So yes, IRC channels have better availability than Slack.

Re:Slack outage: Connectivity issues by flukus on Tuesday October 31, 2017 @07:50PM (#15597767)
Generally yes, it's old and stable, and it's not centralized so not everyone goes down at once. When you host your own you often get to choose the downtime as well, updates get run at midnight when no one is working, not at 10AM on a work day.

A service the scale of slack also runs into a whole host of scaling issues that a little intranet IRC client will never have.

Re:Slack outage: Connectivity issues by paulddraper on Tuesday October 31, 2017 @07:38PM (#15597693)
https://news.ycombinator.com/item?id=15597382 looks like the original, but it's flagged, I guess?

What does that mean?

Re:Slack outage: Connectivity issues by tekacs on Tuesday October 31, 2017 @07:30PM (#15597628)
Slack's status page seems to have been in and out whilst this has been happening too (and sometimes the page loads but assets fail):

https://tkcs.in/461W2z0c1M3z

It's concerning/odd for their status page to be affected by whatever infrastructure issue they're having.

Re:Slack outage: Connectivity issues by richardwhiuk on Tuesday October 31, 2017 @07:34PM (#15597664)
It might be on different infrastructure - just not stuff prepared for the onslaught of it being checked when there's a global issue.
Re:Slack outage: Connectivity issues by chrismorgan on Tuesday October 31, 2017 @07:40PM (#15597705)
The errors have been 500 responses, returned quickly. That suggests something other than high load (though it doesn’t guarantee it by any means).
Re:Slack outage: Connectivity issues by toomanybeersies on Tuesday October 31, 2017 @07:34PM (#15597659)
Same thing happened to Amazon when they had that big outage recently.
Re:Slack outage: Connectivity issues by user5994461 on Tuesday October 31, 2017 @07:41PM (#15597712)
For reference. S3 went down. The amazon status page stored their icons on S3.
Re:Slack outage: Connectivity issues by jedberg on Tuesday October 31, 2017 @07:27PM (#15597614)
Oh good. I was going nuts trying to figure out why I suddenly couldn't communicate with my coworkers and Slack kept saying I didn't have internet when I clearly had internet.

Ah, the downside of relying on a third party for critical communication infrastructure when you're a full remote company...

Re:Slack outage: Connectivity issues by empath75 on Tuesday October 31, 2017 @07:27PM (#15597609)
I guess people will actually have to get some work done
Re:Slack outage: Connectivity issues by jdavis703 on Tuesday October 31, 2017 @07:28PM (#15597618)
Collaboration with your co-workers is work.
Re:Slack outage: Connectivity issues by Danihan on Tuesday October 31, 2017 @07:31PM (#15597634)
Lol keep telling yourself that.
Re:Slack outage: Connectivity issues by jdavis703 on Tuesday October 31, 2017 @07:34PM (#15597660)
As a professional you can't just go off in a corner and produce something (no matter how fun it is). I learned this the hard way as a software engineer. In fact the hardest part of software engineering is collaborating with humans and integrating their ideas and requirements into what you're building.
Re:Slack outage: Connectivity issues by bithive123 on Tuesday October 31, 2017 @07:45PM (#15597737)
Helping other people, not producing output or profit, is the fundamental human enterprise. Other people exist and need help: It's the only reason you have a job. Amazing how many people miss this and think their job is to "be good at X" instead of "help other people with X".
Re:Slack outage: Connectivity issues by loeg on Tuesday October 31, 2017 @07:50PM (#15597770)
It's important, but IMO it isn't the hardest part. Most people can do the collaboration and communication, but can't write code.
Re:Slack outage: Connectivity issues by Drdrdrq on Wednesday November 01, 2017 @08:32AM (#15600536)
True, if you are talking about general population. But among those who can code in my experience the biggest obstacle at work is being able to communicate and collaborate efficiently.
Re:Slack outage: Connectivity issues by koolba on Tuesday October 31, 2017 @07:33PM (#15597648)
If you get paid to do it then it’s arguably more work than is toiling at side projects or posting snarky comments on hackernews.
Re:Slack outage: Connectivity issues by user5994461 on Tuesday October 31, 2017 @07:42PM (#15597719)
Actually, the other 354 days a year when the site worked fine were work too. Ensuring the site is available and working smoothly is real work.
Re:Slack outage: Connectivity issues by loeg on Tuesday October 31, 2017 @07:49PM (#15597760)
Grandparent comment is pretty clearly referring to Slack users, not employees.
Re:Slack outage: Connectivity issues by justinzollars on Tuesday October 31, 2017 @07:34PM (#15597665)
Slacks status page also returns unminified css and four trackers (including twitter advertising).
Re:Slack outage: Connectivity issues by Drdrdrq on Wednesday November 01, 2017 @08:35AM (#15600549)
> unminified css

Curious: does that even matter, assuming response body is gzipped?

Re:Slack outage: Connectivity issues by internalfx on Tuesday October 31, 2017 @07:28PM (#15597620)
Posts about slack seem to keep getting flagged away :/
Re:Slack outage: Connectivity issues by mintplant on Tuesday October 31, 2017 @07:33PM (#15597653)
We need at most one story about this outage on the front page at a time. Dupes should be flagged.
Re:Slack outage: Connectivity issues by alrs on Tuesday October 31, 2017 @07:35PM (#15597667)
There wouldn't be dupes if the first submission hadn't been flagged away.
Re:Slack outage: Connectivity issues by paulddraper on Tuesday October 31, 2017 @07:39PM (#15597700)
Re:Slack outage: Connectivity issues by internalfx on Tuesday October 31, 2017 @07:36PM (#15597684)
There are a two on the home page at the moment, but originally The first one was pushed right off the page.

At this time that post has 116 points in 35 minutes.

Re:Slack outage: Connectivity issues by shon on Tuesday October 31, 2017 @07:35PM (#15597675)
Sigh... 10 minutes of cursing trying to troubleshoot the LTE connection on my phone. Sadly Slack has become a fairly critical part of our communication.
Re:Slack outage: Connectivity issues by kenhwang on Tuesday October 31, 2017 @07:32PM (#15597641)
I've been having degraded services all morning, guess it finally kicked the can and went out.
Re:Slack outage: Connectivity issues by bcherny on Tuesday October 31, 2017 @07:27PM (#15597611)
It's been over 30 minutes - how does a chat app go down for this long?
Re:Slack outage: Connectivity issues by awakeasleep on Tuesday October 31, 2017 @07:38PM (#15597696)
It's built on human-constructed infrastructure or automated infrastructure designed by humans
Re:Slack outage: Connectivity issues by richardlblair on Tuesday October 31, 2017 @07:44PM (#15597729)
It was bound to happen eventually. The scale of their application is mind-blowing.

Building things is hard, mistakes happen, and that's totally okay.

Re:Slack outage: Connectivity issues by jageen on Tuesday October 31, 2017 @11:00PM (#15598533)
Well it's up again.
Re:Slack outage: Connectivity issues by chewbacha on Tuesday October 31, 2017 @07:28PM (#15597622)
part of the screenhero rollout perhaps?
Re:Slack outage: Connectivity issues by twothamendment on Tuesday October 31, 2017 @07:45PM (#15597735)
I just quit a call where we were using screen hero. It worked great. Then I noticed my status said I was still on a call so I thought I'd restart slack. It didn't really want to quit, so I killed it. Sorry everyone.