Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub had connectivity problems

status.github.com

Post reply on HN
Print view View original

101–110 of 175 posts

Re: GitHub had connectivity problems

#101

Post by drzaiusapelord »

nns wrote: post #92

What do they possibly get by DDoS'ng GitHub ? Is this out of pure malice or are there any probable commercial gains to this?

Considering its the Chinese government, yet again, its probably a mix of both. It makes it harder for their nationals to get VPN software that goes through their firewall and also is an assholic statement against the West's ideas about freedom of speech, assembly, and peaceful changes of power via popular elections and multi-party government. The Chinese are most likely hoping they can force github to get rid of these projects by threatening periodic DDOSing.

They also probably feel emasculated that South Korea told their pet regime to knock off the stupidity and China and North Korea capitulated to their demands yet again. The timing of this is far from a coincidence. China's foreign policy is almost 100% hinged on having North Korea attack the west with impunity and they don't like that Park is actually pushing back against this dynamic. So now China is having its hissy fit on Github instead on the Korean peninsula.

Yeah, lets keep rewarding them with factory contracts, right guys?

Re: GitHub had connectivity problems

#102

Post by wtbob »

dTal wrote: post #52
madez wrote: 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.

> it's surprisingly hard to convince them that government-sponsored software is a good idea

That's because it's not. Governments are not reliably good, and their money comes with far more strings than private money.

The FSF have it right: people should write free software because proprietary software is immoral.

Re: GitHub had connectivity problems

#103

Post by nadams »

marinintim wrote: post #6

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.

Re: GitHub had connectivity problems

#105

Post by wtbob »

paulrouget wrote: post #42
_swa8 wrote: post #35

Earlier quoted context omitted.

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

Can you explain? How do you store issues in git?

> How do you store issues in git?

An org-mode file named 'issues,' with each issue under its own heading?

A directory named 'issues,' with an org-mode or CommonMark file for each issue?

A directory named 'issues,' with a directory for each issue, with CommonMark, org-mode or restructured text files for each person's comments?

Re: GitHub had connectivity problems

#106

Post by otikik »

jsjohnst wrote: post #37
theallan wrote: post #12

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.

Citation needed.

Re: GitHub had connectivity problems

#107

Post by xedarius »

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.

Re: GitHub had connectivity problems

#108

Post by a-priori »

paulrouget wrote: post #42
_swa8 wrote: post #35

Earlier quoted context omitted.

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

Can you explain? How do you store issues in git?

You commit your issue database to the same repo as your code and track it alongside your code. Then you just need a tool to manage the database for you, and there's a few tools out there to do this:

http://ditz.rubyforge.org/ http://pitz.tplus1.com/ https://github.com/jeffWelling/ticgit http://www.bugseverywhere.org/

... and probably others. That's just based on a quick Google search.

One nice thing about this approach is that your issue's state follows your code through merges. When you fix the bug you mark it as 'fixed' and commit that change to a branch. When it gets merged into master, the 'fixed' status gets merged as well.

Re: GitHub had connectivity problems

#110

Post by chopman »

wereHamster wrote: post #68
bad_user wrote: post #48

Earlier quoted context omitted.

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.

Well I guess all mirrors could get targeted. Also, what stops github from getting mirrors themselves?
Post reply on HN