Live data from Hacker News

GitHub had connectivity problems

status.github.com

61–70 of 175 posts

Re: GitHub had connectivity problems

#61

Earlier quoted context omitted.

Proof that you can take down a service as large and as well connected a Github perhaps.

What makes you think Github is "large and well connected"? Don't get me wrong, I love GitHub, but due to their architecture decisions, they aren't anywhere near a great example of best practices in the industry for preventing DDoS attacks.

I'm intrigued. What architectural decisions?

Re: GitHub had connectivity problems

#62
Does anyone else find the Github status "messages" page [0] a bit jarring in how it's organised? The way that, when read from top to bottom, time goes forwards within a day but backwards across days?

I guess I normally wouldn't notice, but there are currently some messages on there from today and yesterday and I found it hard to read as a story (either forwards or backwards) - I had to jump around a bit to figure it out.

[0] https://status.github.com/messages

Re: GitHub had connectivity problems

#63

I've always wondered why github hasn't considered switching to a distributed sub domain layout to help ameliorate this problem. Surely if they spread their infra out that would make ddos that much harder. A subdomain per user or repo should work wonderfully

Separating users by subdomain leaks information. An observer can trivially see your DNS queries but not which repository you access over https or ssh.

There is also little benefit in it. If the subdomains only point to the same servers then the same level of traffic will still take them all down, but if different subdomains point to different servers then it makes attacks easier because the attacker only needs enough resources to overwhelm 5% of the servers instead of all of them.

Re: GitHub had connectivity problems

#64
post #49
post #35

Earlier quoted context omitted.

If only it were possible to keep those things in git itself. Oh wait, it is.

One can create a fully offline version of github fork using https://github.com/joeyh/github-backup + https://gist.github.com/piscisaureus/3342247 ("Checkout github pull requests locally") (PS: why cannot I reply to paulrouget's message?)

[deleted]

Re: GitHub had connectivity problems

#65
post #34
post #29

Earlier quoted context omitted.

No, 'are' is, I believe, also incorrect in BrE. It's commonplace here, but not correct. (Or so I was taught!)

http://blog.oxforddictionaries.com/2011/09/agreement-over-co... > In British English it’s absolutely fine to treat most collective nouns as either singular or plural – you can say my husband’s family is very religious or my husband’s family are very religious. http://itre.cis.upenn.edu/~myl/languagelog/archives/001874.h... etc. With something like collective nouns it's probably wrong to make blanket statements about…

Ah but that's different. "Company nouns" are not used as collective, they refer to a singular entity - the registered company, not it as a body of people.

Re: GitHub had connectivity problems

#67
post #52
post #27

Earlier quoted context omitted.

But there is much less commercial incentive behind a p2p alternative. Centralized services are easier to monetize. I look forward to the day governments start to fund free software, for example through the GNU project. Then we'll all have better tools. Actually, there were already some fundings. Germany funded GnuPG to port it to Windows. What do I care what is the new world record in sprinting? But I very much do ca…

Hear, hear. I've talked about this with people and it's surprisingly hard to convince them that government-sponsored software is a good idea. While a tiny fraction of the amount we already spend on commercial software would utterly transform the free software landscape, it's not politically viable as long as commercial software vendors have lobby power.

Let's not forget that it is not in many governments' interest to have distributed tools (with strong encryption). It is much easier to take down stuff on centralized services.

BTW, it is hear, hear ;).

Re: GitHub had connectivity problems

#68
post #13

Earlier quoted context omitted.

Yeh it's definitely preferable to have one of the two developers your small startup can probably afford spending a good portion of their time rolling out, securing and maintaining your own infrastructure

GitHub is not meant for distributing dependencies. Maven Central on the other hand is, the difference being that it is mirrored and if repo1.maven.org goes down, it's not a big deal and your project can still be built and deployed.

.. until they become a target of a DDoS.

Also, if GitHub is down you can still fetch your dependencies from somewhere else.

Re: GitHub had connectivity problems

#69
post #17

Earlier quoted context omitted.

If only git were a distributed version control

Oh cool, I didn't realize git being distributed solved the communication problems that arise on an engineering team. Back to work everyone, git is distributed version control so we don't need pull requests or gists or any kind of easy-to-read historical record that is also accessible for non-engineers.

If it's that critical then someone needs to fix the SPOF.

Re: GitHub had connectivity problems

#70

Does anyone else find the Github status "messages" page [0] a bit jarring in how it's organised? The way that, when read from top to bottom, time goes forwards within a day but backwards across days? I guess I normally wouldn't notice, but there are currently some messages on there from today and yesterday and I found it hard to read as a story (either forwards or backwards) - I had to jump around a bit to figure it…

I just noticed as well, i got really confused for a few minutes. Bit of a weird design.
Post reply on HN