@khm they've had other 5+ hour long outages in the last quarter. I don't know what that number is supposed to indicate.
@cancel I would be keen to have an offline, searchable archive of my Slack history to be able to reference when this happens (or when I just want to turn off the network for a bit). Any idea if that would fit in Ripcord?
@ndpi I've already built it into the design. Actually, there's a compile-time option to enable it, but it's not quite ready yet... still has some problems with keeping track of which regions to purge and re-download if you scroll back into cold history while online.
@cancel you need over 20 hours down for all users to take 1% off
If you hover where the arrow is pointing in that screenshot, it says
"How is uptime calculated?
Slack is a distributed platform and during any given incident it is rare for all Slack teams to be affected. For this reason, we report our uptime as an average derived from the number of affected users."
@flip every workspace I'm on went down (9 of them)
You don't need to take 20 hours off, just 10 hours and 50 minutes for it to round down to 99%. And there has been at least that much downtime. 100% is a lie.
@flip It's not a big deal. I don't expect anything to be up 100% of the time. I think it's silly they put that number there, though.
@cancel None of my workspaces were down, they were just slow. That's 11
I don't have enough information to calculate their uptime, but I haven't seen any evidence to say it isn't 100%
@flip it was completely down for at least two big corp grids, from talking to my friends who work at them.
@cancel @flip It's strange to me that they don't break it down further than 99% or 100%. Most reliability folks give numbers in much finer grains I thought? (for example, http://www.leib.be/sascha/2017/07/server-reliability-rule-of-nines/)
"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko