Live data from Hacker News

GitHub had connectivity problems

status.github.com

111–120 of 175 posts

Re: GitHub had connectivity problems

#111
post #13

All these ideas like "let's fetch our deps directly from github" sound good until github is not down.

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

An internal GitLab install isn't that time consuming to maintain. Also: dat false dichotomy.

Re: GitHub had connectivity problems

#112
It seems a certainty to me that github will be breached one of these days, and all internal data (i.e., private repos) made public. On that day, so many companies will inadvertently become open source!

Do we have any info on what steps github takes to prevent this? I ask as a paying customer (with both personal and corporate accounts).

Re: GitHub had connectivity problems

#113

I do wonder why GitHub gets hit, and people say it's a high profile target, yes almost definitely. Another thought occurs to me though, I guess one of the problems when writing a DDoS is measuring how well it performs. The GitHub status screen provides a lot of useful metrics for tuning such an attack.

If I may posit...

1. Github is very well known and cater specifically for the tech crowd. So, an attack on Github is more likely to be talked in the tech crowd, which I would assume the people who would try out DDoS attacks be more likely to be part of. Validation is a weird thing.

2. In a convoluted sense, taking down Github doesn't harm as many bystanders. If that makes any sense...

3. As you've mentioned, very clear useful metrics for the attacks.

4. Crowding effect? Maybe attacking Github has become some 'cool' things to try in that community. I'm just imagining at this point.

Re: GitHub had connectivity problems

#114
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 really that important, why not host your own gitlab or pay for a self hosted github installation?

Re: GitHub had connectivity problems

#115
post #103

All these ideas like "let's fetch our deps directly from github" sound good until github is not down.

Or "let's move our entire business workflow to github!". Doh! This is why you should run indefero/srchub/gitlab or any of the other self hosted source code control apps.

I would argue from personal experience there's almost the same (or higher) likelihood of internal sources going down for other reasons since most people's IT departments aren't as efficient as GitHub's.

Re: GitHub had connectivity problems

#116

I do wonder why GitHub gets hit, and people say it's a high profile target, yes almost definitely. Another thought occurs to me though, I guess one of the problems when writing a DDoS is measuring how well it performs. The GitHub status screen provides a lot of useful metrics for tuning such an attack.

>I do wonder why GitHub gets hit, and people say it's a high profile target, yes almost definitely.

It could be related to things like this: https://news.ycombinator.com/item?id=10101469

Re: GitHub had connectivity problems

#117
post #52

Earlier quoted context omitted.

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 ;).

But of your government is at odds with an oppressive government, it would make sense for it to fund that kind of software so the people could take it down, or at least make trouble, themselves.

Re: GitHub had connectivity problems

#118
post #36

Guys, what's the purpose to attack a service like Github?!

China does not like some of the projects it hosts, namely the ones used to circumvent its Great Firewall.

At some point we should just kick China of the net, just for a week or so.

If you really want the Chinese people to protest, try cutting them of from the Internet for a few weeks. Let's see if that won't work.

Re: GitHub had connectivity problems

#119
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 only there was a way to do p2p communication that you could use to send patch files. Uhmmm.

Re: GitHub had connectivity problems

#120
post #65
post #34

Earlier quoted context omitted.

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.

But they are.

https://dictionary.cambridge.org/grammar/british-grammar/nou...

Post reply on HN