3 ms·
I flagged this because I don't think that this is actually interesting, will drive discussion, or in general meets the site's guidelines. I furthermore don't t
by TheDong 10y ago
I flagged this because I don't think that this is actually interesting, will drive discussion, or in general meets the site's guidelines.
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.
- stockkid 10y agoI actually agree with you. Don't understand why you are being downvoted.
- muhic 10y ago> I don't think that this is actually interesting, will drive discussion, or in general meets the site's guidelines. 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.
- TheDong 10y agoThe post-mortem is interesting and drives discussion. This is logically and historically true. If you look at the other comments here, and in past threads like it, it's obvious that these threads do not.
- detaro 10y agoA single service has been down for less than 30 minutes... If it were the first time, or anything special about the outage, maybe. Not much new to be said now.
- gauravagarwalr 10y agoInterestingly, only the site was down, most probably just unicorn. No new workers were created, or the existing workers were busy. I was still able to do a git clone using the git@github.com:TEAM/REPO.git format.