GitHub down 2016.10.34 6:06 GMT unicorn on each pageload |
GitHub down 2016.10.34 6:06 GMT unicorn on each pageload |
We are currently experiencing major service outages.
https://twitter.com/githubstatus/status/783187145414541312 Everything operating normally.
https://twitter.com/githubstatus/status/783191801352126465It might be interested to see the post-mortem (if there is one).
I furthermore don't think upvotes/downvotes playout well with this sort of content. It's obviously low-to-zero-value, but it attracts "hey, me too" type upvotes of people saying they observed this super obvious and dumb thing too. I think that factor ends up with a very low-quality post in general.
People who are interested in github will find out by using github and seeing a very clearly identifying unicorn with complete message and status page.
This provides no value or discussion. The likely post-mortem will be interesting, but until then, nothing to see here.
I disagree with this. The guidelines refer to Anything that good hackers would find interesting and I certainly think a major outage at the heart of open source software is interesting in that it drives discussion around similar experiences, implications, pre-emptive action and mitigation.
If you look at the other comments here, and in past threads like it, it's obvious that these threads do not.
If it were the first time, or anything special about the outage, maybe. Not much new to be said now.
Or at least write out the month. That makes it unambiguous regardless of what weird date ordering is used.