Comment by eevilspock | Hacker News Reader

Comment by eevilspock | Hacker News Reader

Parent Full thread

> Your code belongs to them.

That is a very false characterization. If they boot you from their servers all you've lost is their hosting of your code. Given that this is built on top of Git, you can migrate your code with full history at any time, for whatever reason.

> Fine, they're allowed to, but then what? What's the next "offensive" term they'll ban? Maybe tomorrow they'll remove all repos that use the widely accepted terms "master/slave" for distributed systems just for good PR.

Slippery Slope Fallacy: http://www.nizkor.org/features/fallacies/slippery-slope.html

You never answered the question of this post. If someone started hosting porn on GitHub pages, would it be okay for them to ban it?

> And that's not even accounting for the inconsistency. There are literally >100k occurrences of 'retard' on GitHub (there was a blog post about that on HN in the past 48 hours), and I'm counting the 'fuck' and co. Are they gonna close 100k repos?

Another logical fallacy. Just because someone can't do something perfectly doesn't mean it's wrong to try.

> posturing as the white knight of Open Source?

Can you explain how they are posturing?

Whether or not they are posturing, how are they betraying Open Source by enforcing this Code of Conduct? Again, they are not taking over your source when they reject it, they are doing just that, rejecting it. In the same way that FOSS adherents want to reject non-free software.

I say "your code belongs to them" in the sense that they are the new LinkedIn-for-developers. The code you put there is your new resume (I kind of disagree with that, but this is a narrative that is very much around). If they ban you you lose access to a big share of the market.

Have fun with your fallacies. (especially the "slippery slope" one has be debunked many times http://www2.law.ucla.edu/volokh/slippery.pdf) If you don't understand the concept of precedence what do you want me to say? We'll reconvene after their next PR move if you want. I was highlighting the fact that as a private company they can do as they please, yesterday they targeted the 'retard' repo, tomorrow who knows.

"Can you explain how they are posturing?" Really? You are telling me that they're all marketing isn't to represent themselves as the platform for OS? There's nothing wrong with this strategy, but that's what they do.

Funny that you completely ignored my main point: their platform is not open source, it's not hard to see how OS fans may take offense in that.

> I say "your code belongs to them" in the sense that they are the new LinkedIn-for-developers. The code you put there is your new resume (I kind of disagree with that, but this is a narrative that is very much around). If they ban you you lose access to a big share of the market.

If you don't have any public share repositories to point to, you lose something.

I don't think not being on GitHub specifically is a problem of the same order of magnitude.

>Slippery Slope Fallacy

In the broader society there is a trend towards increasingly intolerant tolerance. That what is going on on GitHub is a part of this trend and thus can get worse is a reasonable inference.

Reply on news.ycombinator.com