While I appreciate the timely status updates, it almost seems like Slack has built a random status update bot to post updates that don't say anything exactly every 30 minutes.
Slack outage: Connectivity issues affecting all workspaces
211–220 of 278 posts
Re: Slack outage: Connectivity issues affecting all workspaces
#212You know how much of the community uses one messaging system when 15 minutes after it going down, it has over 40 points on the front page! This says a lot about how it's a single point of failure in modern company comms. It's even worrying to think about how some users probably have production-dependent (dare I postulate it) workflows in Slack that get crippled by its outage... ITT: Chat about decentralisation that w…
Here's a chat decentralisation platform: https://www.ratbox.org/ .
Re: Slack outage: Connectivity issues affecting all workspaces
#213Slack and Chromecast having an almost simultaneous worlwide outage... have they something in common? Same enemies?
https://twitter.com/search?f=tweets&q=chromecast%20slack
https://techcrunch.com/2018/06/27/google-home-and-chromecast...
Re: Slack outage: Connectivity issues affecting all workspaces
#214Earlier quoted context omitted.
Curious why you got burned with IRC client UX given the multitude of clients available for it.
Technical people who haven't used IRC can barely figure out IRC their first time using it. Trying to sell IRC to a company would be hilarious. Bob in Accounting getting on IRC and feeling comfortable with it's UX?
Then you've never seen the 'hilariously' bad UX they already put up with, with things like Quickbooks.
mIRC is pretty straight forward compared to that.
Re: Slack outage: Connectivity issues affecting all workspaces
#215Despite having a vote increment velocity far exceeding other items, a publish time of only 25 minutes ago, and more points, this item just dropped from #5 to #7 on the front page. How’s that work exactly? Edit: It’s now droppped to #14 even with comment count also rapidly increasing.
Quoting myself from 8 months ago [1]:
> I really don't understand these types of questions. The possible answers range from "because the ranking works that way" to "someone with privileges wanted it that way". On either end of the spectrum, the real question remains: so what? What difference does it make why a particular post is in a particular position? If the title seems interesting, you click on it. If not, you move on.
> I don't mean to question you in particular. It just seems like such a trivial concern to me that I truly can't understand why someone might possibly care.
Re: Slack outage: Connectivity issues affecting all workspaces
#216Earlier quoted context omitted.
In light of how Slack and other companies haven't been able to get a decent level of uptime, I have to say, the company known to make huge web applications that don't go down in shame every couple of months is probably Google. I can't remember the last time Gmail was down. It just works! If google is down, probably your internet is down. Their expertise and discipline in distributed applications is unrivaled. I'm gue…
Google is expert at designing services which you won't notice when there is downtime . Take Google Search for example. When there is downtime, results might be slightly less accurate, or the parcel tracking box might not appear, or the page won't say the "last visited" time beside search results. The SRE's are running around fixing whatever subsystem is down or broken, but you the user probably don't notice.
The reality is this is how you design highly available systems, and it is also imo one of the reasons microservices have gained so much popularity.
Driving features with microservices makes it easier to isolate their failure and just fall back to not having that feature. The trade off is that monoliths are generally easier to work with when the product and team are small, and failure scenarios with distributed systems are often much more complex.
An analogy to your Google failure examples for slack might be something like the "somebody is typing" feature failing for some reason. In an SoA you would expect it to just stop working without breaking anything else, but one could easily imagine a monolith where it causes a cascading failure and takes the whole app down. Most services have countless dependencies like this.
Re: Slack outage: Connectivity issues affecting all workspaces
#217It's times like this I wish there was a solid decentralized standard to pick from, but there's no clear choice between XMPP and Matrix.
Zulip is amazing, is a self hosted system without federation is an option for you.
Love the workflow with Zulip, but I hope they work out a way to join in with either Matrix or IRC3+ federation.
Re: Slack outage: Connectivity issues affecting all workspaces
#218You know how much of the community uses one messaging system when 15 minutes after it going down, it has over 40 points on the front page! This says a lot about how it's a single point of failure in modern company comms. It's even worrying to think about how some users probably have production-dependent (dare I postulate it) workflows in Slack that get crippled by its outage... ITT: Chat about decentralisation that w…
Yes it's a single point of failure, but so what? I don't particularly care whether other organizations fail at the same time as I do, I just care whether I fail. Hosting my own chat system does not solve that problem. In fact, it may make it worse because then I have to worry about system administration, and Slack probably has more expertise on that. It's likely that they can fix this problem for all customers faster…
if the software is architected this poorly so that it can literally go down simultaneously for all clients, then why would I trust that it's secure?
Re: Slack outage: Connectivity issues affecting all workspaces
#219Earlier quoted context omitted.
In light of how Slack and other companies haven't been able to get a decent level of uptime, I have to say, the company known to make huge web applications that don't go down in shame every couple of months is probably Google. I can't remember the last time Gmail was down. It just works! If google is down, probably your internet is down. Their expertise and discipline in distributed applications is unrivaled. I'm gue…
Facebook springs to mind as well.
Facebook breaks features very often. Sometimes things go missing and comes back a week later. Dropbox does this a lot too.
Re: Slack outage: Connectivity issues affecting all workspaces
#220It's interesting to me that the update messages are posted every 30 minutes from 1st notification until resolution. Judging by this and every other outage I assume this is automatic, and probably implemented to appease the people who are probably frustrated by the outage. https://status.slack.com/2018-06/142edcb9e52c7663
Good catch...definitely updating every 30 minutes exactly.