by Arathorn on 11/1/17, 12:29 AM
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).
by nategri on 10/31/17, 11:04 PM
Yo, people who like to complain that Slack just re-implements IRC... This Is Your Moment
by pkrumins on 11/1/17, 1:08 AM
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...
by cadr on 10/31/17, 11:01 PM
When the status page is returning a 500 error... not a good sign.
by carlchenet on 11/1/17, 12:01 AM
by NightMKoder on 11/1/17, 12:17 AM
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.
by eridius on 10/31/17, 11:06 PM
Hasn't Slack learned yet that you're supposed to host your status page on a different infrastructure?
by BrentOzar on 10/31/17, 11:06 PM
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.
by kamilszybalski on 11/1/17, 12:41 AM
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".
by alexasmyths on 10/31/17, 11:49 PM
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.
by a12l on 10/31/17, 11:06 PM
Team: if you're reading this, get out the radios.
by oplav on 10/31/17, 11:06 PM
by kiloreux on 10/31/17, 11:05 PM
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.
by westoncb on 11/1/17, 12:57 AM
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...
by philfreo on 10/31/17, 11:06 PM
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.
by nikolay on 11/1/17, 12:18 AM
Nice! I wondered why my productivity suddenly doubled up!
by internalfx on 10/31/17, 11:07 PM
My RocketChat server is running just fine ;P
by peterlk on 10/31/17, 11:14 PM
by SolaceQuantum on 11/1/17, 12:08 AM
This is certainly scary for the Slack devs... Happy Halloween!
by chris_wot on 10/31/17, 11:44 PM
Causing chaos at my workplace. We have Slack integrated into our incident management solution... very, very unfortunate.
by akulbe on 10/31/17, 11:20 PM
Slack
DOWN!
Productivity
UP!
#jokingpeopleCOMEON
by quadrant6 on 11/1/17, 12:10 AM
by legohead on 10/31/17, 11:10 PM
don't push code at 4pm! and on Halloween, oof..
by jnaulty on 10/31/17, 11:48 PM
We are aware of connectivity issues and are actively lnvestigating.
3:58 PM PDT・See in your timezone
They spelled investigating with a lower-case 'l' :\
Does that bug anyone other than me?
by _lce0 on 11/1/17, 1:23 AM
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.
by cheerioty on 10/31/17, 11:07 PM
That's why there's StatusPage.io :)
by jaredsohn on 11/1/17, 1:08 AM
FYI, slack seems to be up again now (at least for me.)
by msarchet on 10/31/17, 11:03 PM
not anymore? - EDIT: the status page was fine and then it wasn't.
by 4lch3m1st on 11/1/17, 12:47 AM
I'm not really a Slack user, but isn't Keybase always an option?
by c0smic on 11/1/17, 12:25 AM
Just a spooky coincidence it's on Halloween?
by internalfx on 10/31/17, 11:08 PM
Is this getting flagged off of HN?
by orthoganol on 10/31/17, 11:53 PM
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?
by coleca on 10/31/17, 11:04 PM
How can I tell my team that Slack is down? :-)
by artur_makly on 11/1/17, 12:21 AM
the loss of revenue.. is unquantifiable.
by Narzerus on 10/31/17, 11:03 PM
O.o god help us
by partycoder on 11/1/17, 12:25 AM
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.