Remember GitTorrent, the distributed answer to a centralized Github? It now appears dead in the water.

26    03 Feb 2016 09:31 by u/8bCvYq2vpg

Last commit was 4 months ago.

This issue was opened 6 days ago, the one before it was opened 22 days ago with no replies.

I found this comment with a reply from Chris on June 2nd 2015.

Before anyone starts flailing their arms, Chris isn't dead. He seems to be working on something called Keybase. I just figured that if anyone was wondering what happened to GitTorrent, it appears to be stalled at this point in time.

13 comments

6

Well it's there as far as it got if people come to need it.

Which is more than you can say for the code that runs github.

2

I recommend keeping a copy locally on your HD, if you can spare the space.

2

GitHub isn't that bad in the first place, right?

Or have I been living under a rock?

6

Chris goes into the advantages of his project and why we can't put all of our faith in Github.

That, and others will come along and tell you how Github has recently changed its ToS or Code of Conduct to be more vague in order to appease political extremists. Some have moved to Bitbucket over the issue.

3

Then it's still lightyears ahead of Sourceforge. Unless something drastic happens, I don't see a mass Github exodus happening anytime soon.

3

We don't need any mass migration, we need distributed options so we're not relying on a central, mass hub.

2

Just Google github and meritocracy.

1

The downtime is annoying. We use it for one project with about 20 developers, so it's annoying:

$ git pull
fatal: unable to access 'https://github.com/puppetlabs/puppet.git/': Failed to connect to github.com port 443: Connection refused
1

My company has recently started hitting this (specifically with puppet), too. Around 2:00pm each day we hit the throttle and our puppet stops working.

This triggers alerts...