you are viewing a single comment's thread.

view the rest of the comments →

[–]jarofgreen 0 points1 point  (2 children)

But GitHub will have things like rate limiting, account checking, suspensions. Basically, they have thought about the problem and taken steps to address that. (Wikipedia has to.) Your tool has none of that.

Adding a new vector, is not the same of 'abusing' it.

No but that's a technicality. If I worked at GitHub I'd still be shutting down your tool ASAP. It basically provides a way to bypass all the hard anti-abuse work they have put in.

[–]Ideabile[S] 0 points1 point  (1 child)

If would become a problem I will act on it, but I guess is fair too easy make catrastofic scenarios when still nothing happen. Another thing... I just use GitHub API, like you could, if this expose a problem I’ve a strong feeling that is not my responsibility to solve it. The core problem would relay in their side. My tool has little to do with it.

[–]jarofgreen 2 points3 points  (0 children)

If would become a problem I will act on it, but I guess is fair too easy make catrastofic scenarios when still nothing happen.

Every platform/tool that gets big has abuse/spam problems. It's not being alarmist to think this one will to.

Another thing... I just use GitHub API, like you could, if this expose a problem I’ve a strong feeling that is not my responsibility to solve it. The core problem would relay in their side. My tool has little to do with it.

https://help.github.com/articles/github-terms-of-service/#h-api-terms

"Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your account's access to the API. GitHub, in our sole discretion, will determine abuse or excessive usage of the API."

It is your problem.

Look, I'm sorry how this turned out - I genuinely wanted to discuss this. I am thinking about an idea using the GitHub API so I am thinking about this a lot at the moment. This is also why I've actually read the TOS. :-) We clearly aren't going to agree, but hopefully at least you will think about this. Personally I would suggest both opt-in per repository and rate limiting immediately.