Yo, people who like to complain that Slack just re-implements IRC... This Is Your Moment
I've switched to using TwistApp (https://www.twistapp.com) with my team. Unlike Slack where you have channels where everyone talks about everything, TwistApp bases conversations around threads. Every problem that's being worked on has its own thread. Once it's completed, I close and archive the threads. Very effective for getting things done as every task is isolated in a separate thread and discussions don't overlap.
Also read this post by Amir, the founder of TwistApp, "Why we're betting against real time messaging" - https://blog.doist.com/why-were-betting-against-real-time-te...
When the status page is returning a 500 error... not a good sign.
You could use this time to read The Slack threat https://carlchenet.com/the-slack-threat/
I'm hoping they publish a public post-mortem. Learning from this kind of outage is the best kind experience for engineering - though it's far better when only staging goes down and not prod.
Hasn't Slack learned yet that you're supposed to host your status page on a different infrastructure?
And of course today's the first day we're using Slack for audience Q&A at a conference. 360 folks in a room now have to...raise their hands! So barbaric.
Slack is currently down and I've realized, for better or worse, what Slack has really done.. It's created an expectation for immediacy. I thought about sending my question to someone via email but then just thought, "I'll wait for Slack to be back up, it'll be faster anyhow".
I worked for BlackBerry when outages started to become a thing.
When your business motto is 'always on' - it's really, really bad to be 'off' - it's a deep transgression of the brand promise.
BB was structured poorly for this - they didn't grasp the concept of multiple nodes of redundancy very well. (Easy in hindsight).
But - we should all be impressed at how highly available Google, FB and some other brands are. That's impressive.
Team: if you're reading this, get out the radios.
Here's the incident page: https://status.slack.com/2017-10/8b0d4d44ea53726f
I just realized that being a remote team. I can't join any of my teammates. Neither see live changes to the infrastructure and the repositories.
The things we take for granted.
Maybe Slack decided to give us all a break for Halloween :)
Also curious: why is this so low on the front page? 250 points, posted an hour ago...
Reminder why your status page should be hosted in a very different way than your regular infrastructure... so you're way less likely to end up with issues on both at the same time.
I like how statuspage.io even has metastatuspage.com in case their primary domain/DNS/TLD has issues.
Nice! I wondered why my productivity suddenly doubled up!
My RocketChat server is running just fine ;P
This page seems to not be throwing 500s: https://status.slack.com/2017-10/8b0d4d44ea53726f
This is certainly scary for the Slack devs... Happy Halloween!
Causing chaos at my workplace. We have Slack integrated into our incident management solution... very, very unfortunate.
Slack DOWN! Productivity UP!
#jokingpeopleCOMEON
Wow, talk about realising how much we rely on Slack.. suddenly I feel so disconnected and alone.
don't push code at 4pm! and on Halloween, oof..
We are aware of connectivity issues and are actively lnvestigating.
3:58 PM PDT・See in your timezone
Why CPU goes like crazy every time slack loses connectivity?
You can easily test this by disconnecting from wifi. As soon as you're offline the fan starts spinning until you get your connection back.
That's why there's StatusPage.io :)
FYI, slack seems to be up again now (at least for me.)
not anymore? - EDIT: the status page was fine and then it wasn't.
I'm not really a Slack user, but isn't Keybase always an option?
Just a spooky coincidence it's on Halloween?
Is this getting flagged off of HN?
How is there nothing on the front page of HN, slack being out for almost an hour now?
Given timeframe and upvotes, how is this not the top of HN?
How can I tell my team that Slack is down? :-)
the loss of revenue.. is unquantifiable.
O.o god help us
Slack has a nice market share, but also many competitors, many of them 100% ripoffs with the same features (to name a few, Attlassian HipChat and MS Teams... not to mention open source products).
Slack has been experiencing service degradation often lately, so I would not be surprised if people start switching.
In our team we already started looking for an alternative.
This is probably preaching to the choir, but hosting your own FOSS chat is nowadays a very viable way to avoid being dependent on a centralised service like Slack. Your options include:
* Riot.im / Matrix.org (decentralised global network; e2e encryption; open protocol)
* Rocket.Chat (Meteor-based; focus on UX and feature)
* MatterMost.com (clone of Slack UI; open core license)
* Zulip.org (all about threads!)
* ...or indeed IRC or XMPP.
(disclaimer; I work on Matrix).