Hacker News Reader

Comment by xpaulbettsx | Hacker News Reader

GitHubber here, we'll follow up on this with Pete. We think one of our replies was missed along the line. Thanks for letting us know.

View on HN

hopefully there is a documented process so that one doesn't have to make a blog article to post on HN to get this stuff resolved.

As Paul mentioned above, Pete was doing the correct thing in contacting our support.

It seems he unfortunately missed one of our replies and therefore considered us unresponsive.

It doesn't sound like the OP tried very hard to contact them. He sent them an email, didn't hear back, and then decided to write a blog post about it. I mean, if he cared that much about github, he would send them an email back asking what was up. Or 5.

There are always things like real people and phone numbers. You know, find some GH staffers via G+, LinkedIn, Fb or your own network of friends and work some connections. Pete does not say the lengths he went to, but email is admittedly one of the most passive mediums.

You really should not have to find people working at GitHub on other parts of the internet for something like dealing with copyright issues if you're not the copyright owner because (I suspect) copyright owners will have no trouble getting GitHub to (at least) listen to their complaints.

He said he also tweeted at them.

I'm only a GitHub user here, but I believe GitHub to be very transparent on copyright issues. They post the DMCA takedown notices they receive[1] (and the counter notices as well; in a Git repo, of course!) — this was on HN[2] back when Flat UI received a DMCA takedown notice[3]. There's also another page listing the policy itself[4]. As other users have noted however, the repo linked to in the article reads “Access to this repository has been disabled by GitHub staff due to excessive use of resources, in violation of our Terms of Service.”

Given the other posts, it seems there might just be some confusion that needs clearing up; for that, we'll have to see if our blogger posts anything more.

[1]: https://github.com/github/dmca

[2]: https://news.ycombinator.com/item?id=5342360

[3]: https://github.com/github/dmca/blob/master/2013-03-06-LayerV...

[4]: https://help.github.com/articles/dmca-takedown

any comment on the process (or lack there of)?

Reply on news.ycombinator.com