Slack is down

Post by it33 » Mon, Nov 23, 2015, 9:20 PM UTC

woodruffw wrote: post #48

callumjones wrote: post #38

Earlier quoted context omitted.

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 by cortesoft » Mon, Nov 23, 2015, 11:18 PM UTC

woodruffw wrote: post #47

cortesoft wrote: post #42

Earlier quoted context omitted.

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.

Post by tedmiston » Tue, Nov 24, 2015, 5:39 AM UTC

tedmiston wrote: post #52

That's an interesting decimal truncation convention. http://i.imgur.com/FiJ4G4i.png "Let's only show precision that makes us look good."

  May 2015        99.999%
  April 2015      99.9%
  March 2015      99.999%
  February 2015   99.995%
  January 2015    99.99%
  December 2014  100%
  November 2014   99.84%
  October 2014    99.9%
  September 2014  99.998%