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

Slack is down

slack.com

Post reply on HN
Print view View original

41–50 of 65 posts

Re: Slack is down

#41

Post by bcruddy »

cortesoft wrote: post #16
bcruddy wrote: post #15

I didn't notice an interruption on the desktop client and it's been logged in for about 7 hours now and slack.com looks fine. Interestingly enough https://status.slack.com is currently down while curling status.slack.com returns a page that says it's moved to https://status.slack.com

You mean the http redirect to https is up but the https site is down.

No I meant it returned an HTML page that said "this link as moved" with a link directing you to https://status.slack.com

Re: Slack is down

#42

Post by cortesoft »

woodruffw wrote: post #17

Just another reason for OSS projects to never trust closed (centralized!) protocols: no recourse when it (inevitably) hits the fan.

I feel like this is the same sort of argument that opponents of self-driving cars will use - "We shouldn't use self driving cars, because they have problems sometimes and a driver doesn't have recourse to correct it!"

While this might be true, we are still trading more problems for fewer problems. Yes, we can't fix slack when it breaks, but it still breaks a lot less than when we were running our own internal chat client.

Re: Slack is down

#44

Post by cortesoft »

bcruddy wrote: post #41
cortesoft wrote: post #16

Earlier quoted context omitted.

You mean the http redirect to https is up but the https site is down.

No I meant it returned an HTML page that said "this link as moved" with a link directing you to https://status.slack.com

Umm, yeah that is called a 302 redirect:

curl http://status.slack.com 302 Found Found

The document has moved here.

" rel="nofollow">https://status.slack.com">here.

Apache/2.4.7 (Ubuntu) Server at status.slack.com Port 80

The HTML parts are fallback for if your browser (or curl) in this case doesn't handle a 302

Re: Slack is down

#47

Post by woodruffw »

cortesoft wrote: post #42
woodruffw wrote: post #17

Just another reason for OSS projects to never trust closed (centralized!) protocols: no recourse when it (inevitably) hits the fan.

I feel like this is the same sort of argument that opponents of self-driving cars will use - "We shouldn't use self driving cars, because they have problems sometimes and a driver doesn't have recourse to correct it!" While this might be true, we are still trading more problems for fewer problems. Yes, we can't fix slack when it breaks, but it still breaks a lot less than when we were running our own internal chat cl…

Except, of course, that self-driving cars do have a recourse for the driver - manual overrides. I do see your point, however, and you're correct in that running an internal chat network probably isn't the best course of action for most groups/small business. Luckily, that's what IRC and XMPP networks are for.

Re: Slack is down

#48

Post by woodruffw »

callumjones wrote: post #38
woodruffw wrote: post #17

Just another reason for OSS projects to never trust closed (centralized!) protocols: no recourse when it (inevitably) hits the fan.

Except when you have to manage it yourself and something breaks or the infrastructure you have to manage needs managing.

See the comment above. If you're using Slack to avoid managing infrastructure, there are plenty of great (read: open source) alternatives.

Even if IRC isn't for you, there's XMPP, Mattermost [0], Let's Chat [1], and Zulip [2].

[0]: http://www.mattermost.org/

[1]: https://sdelements.github.io/lets-chat/

[2]: https://github.com/zulip/zulip

Post reply on HN