No matter github's priorities or prior knowledge of this issue, there is always the option of manual intervention. That is probably what I would have contacted

No matter github's priorities or prior knowledge of this issue, there is always the option of manual intervention. That is probably what I would have contacted github for if I found myself in your problem. I was just wondering if you tried to contact someone at github before reaching the conclusion that you needed to take this into your own hands. This is before finding the bug they needed to fix and letting the world know in a super high profile blog post that you had a problem. Even if it wouldn't do anything in the short term other than banning the account in question, github would have documented history of abuse and another big +1 for fixing the way adding collaborators works. I don't mean that you have to spend 6 months and become drinking buddies with everyone at github to get anything done. Even a simple one liner email like "this dick is being a dick with his dicks" to support would be better than assuming they're not going to do anything. Basically, I'm trying to see this from a developer perspective. We expect these kinds of bug reports and emails from users (or, at least, analytics that would correspond with a problem) and we know that we can't read minds (well, I don't know about you, but I know I can't). We also have priorities. Yet we have users and clients and bosses that want to disregard all that :) If you do know that this was a well known problem to github and they didn't want to address your particular issue, then kudos to you for your creative trolling of a troll and deciding to switch to another provider. Otherwise, I don't know, I'm pretty ambivalent on how I feel about people complaining without saying anything to the company/person in question. I can't blame you for being frustrated, but part of your frustration might be self-inflicted.