Slack was down • Hacker News Board

Re: Slack was down

#51

Post by andoma » Mon, Jul 29, 2019, 3:20 PM UTC

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.

When this happens I just switch to tethering from my cell phone. Redundant enough.

Re: Slack was down

#52

Post by _asummers » Mon, Jul 29, 2019, 3:20 PM UTC

black_puppydog wrote: post #2

RAM prices go tumbling

The new update was actually _very_ good for my RAM usage. Still a lot for a chat app but significantly less than before.

Re: Slack was down

#53

Post by zaphod4prez » Mon, Jul 29, 2019, 3:21 PM UTC

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.

I am a huge fan of zulip

Re: Slack was down

#54

Post by streamer45 » Mon, Jul 29, 2019, 3:21 PM UTC

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.

It seems appropriate to also mention https://mattermost.com/ as a valid Open Source alternative to Slack.

Re: Slack was down

#55

Post by DrWumbo » Mon, Jul 29, 2019, 3:21 PM UTC

With Slack unable to send messages, I had to contact people via trembles Skype for Business

Re: Slack was down

#56

Post by freehunter » Mon, Jul 29, 2019, 3:21 PM UTC

diegoperini wrote: post #31

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.

It is appropriate if Slack being down affects software other than Slack. We can learn how to avoid outages in our own products happening due to 3rd party services such as Slack becoming unavailable.

I would love if threads like this became "how to make your Slackbots more resilient" or "high-availability messaging by archiving your Slack threads" or an actually interesting conversation topic. Instead of just complaining that Slack is popular and on-premise solutions never have technical problems, I'd love to hear some real solutions.

Re: Slack was down

#57

Post by aantix » Mon, Jul 29, 2019, 3:22 PM UTC

Slightly offtopic : As a remote engineer, I wonder if half-duplex voice (kind of like a CB radio) would be superior for communication vs typing everything?

E.g. when I have an idea, I just talk, that comment is recorded and made available to the chat room.

I'd like to get back some of the nuance of language that just isn't possible with text.

There'd have to be some easy way of playing back the voice snippets in order that were posted to the chat room.

Maybe Discord is superior to Slack for this.. I've never used it.

Re: Slack was down

#58

Post by SamuelAdams » Mon, Jul 29, 2019, 3:22 PM UTC

elwell wrote: post #46

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...

Actually it's only two nine's, which means Slack can be down for 52 minutes every year.

> 1. We purposely made our commitment to the ‘fourth 9’, viz. 99.99% uptime guarantee in contrast to the typical SLAs which tend to offer 99.90%. We believe that extra availability makes a difference: the ‘fourth 9’ is important when your team relies on Slack every day. You need Slack at least 9,999 out of every 10,000 minutes. [1]

[1]: https://get.slack.help/hc/en-us/articles/204113126-Service-L...

Re: Slack was down

#59

Post by zzyzxd » Mon, Jul 29, 2019, 3:22 PM UTC

January is the only month that slack didn't have a downtime this year. They must have some serious infrastructure issue.

Re: Slack was down

#60

Post by mfer » Mon, Jul 29, 2019, 3:22 PM UTC

elwell wrote: post #46

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...

We don't pay for 100% uptime. We pay so that we don't have to put the time into operating a service. That way we have more of our time to focus on our business problems.