Updated rate limits for unauthenticated requests
github.blog108 points by xena a year ago
108 points by xena a year ago
https://github.com/orgs/community/discussions/159123
https://github.com/orgs/community/discussions/157887
GitHub answered https://github.com/orgs/community/discussions/159123#discuss... I don’t think the publication date (May 8, as I type this) on the GitHub blog article is the same date this change became effective. From a long-term, clean network I have been consistently seeing these “whoa there!” secondary rate limit errors for over a month when browsing more than 2-3 files in a repo. My experience has been that once they’ve throttled your IP under this policy, you cannot even reach a login page to authenticate. The docs direct you to file a ticket (if you’re a paying customer, which I am) if you consistently get that error. I was never able to file a ticket when this happened because their rate limiter also applies to one of the required backend services that the ticketing system calls from the browser. Clearly they don’t test that experience end to end. 60 req/hour for unauthenticated users 5000 req/hour for authenticated - personal 15000 req/hour for authenticated - enterprise org According to https://docs.github.com/en/rest/using-the-rest-api/rate-limi... I bump into this just browsing a repo's code (unauth).. seems like it's one of the side effects of the AI rush. Why would the changelog update not include this? it's the most salient piece of information. I thought I was just misreading it and failing to see where they stated what the new rate limits were, since that's what anyone would care about when reading it. > Why would the changelog update not include this? I don't know. The limits in the comment that you're replying to are unchanged from where they were a year ago. So far I don't see anything that has changed, and without an explanation from GitHub I don't think we'll know for sure what has changed. because it will go way lower soon. and because they don't have to. they already have all your code. they've won. you are not ... you don't have any part of your body in reality, do you? you have left the room. If people training LLMs are excessively scraping GitHub, it is well within GitHub's purview to limit that activity. It's their site and it's up to them to make sure that it stays available. If that means that they curtail the activity of abusive users, then of course they're going to do that. it was never about avoid scrapers. that's just the excuse. they own the scrapers too, remember. why do you think before they blocked non logged in users from even searching? they need your data and they are getting it exactly in their terms. because as I've said, they have already won. Embrace, extend, extinguish. … I… what has been embraced, extended and extinguished? I see no MS or GitHub specific extension, here. Copilot exists, and so do many other tools. Copilot can use lots of non-Microsoft models, too, including models from non-Microsoft companies. You can also get git repository hosting from other companies. You can even do it yourself. So, explain yourself. What has been embraced, extended, and extinguished? Be specific. No “vibes”. Cite your sources or admit you have none. I see no extending unique to MS and I see no extinguishing. So explain yourself. I'm with you, but let's not forget that they haven't started the extinguishing yet. They might yet do it. The extending they've done plenty: issue tracker, wiki, discussions etc. Those things all existed before Microsoft bought them, and they’re all present in competing products, even free ones. the entire open source community exist in github. Microsoft have a more successful social network for programmers than HN or google circles (heh) ever dreamed. the arguments had already dropped access to the information by scrapers, since they own the scrapers and all... why did you brought it back as the main argument?
they hijacked what could have been a community hub and turned into a walled garden to sell a few enterprise licenses. [flagged] > What the hell are … no, this is not a drug. This is a mental illness. Get help. This is an unacceptable comment on HN and we have to ban accounts that do it repeatedly. We've warned you in the past about inappropriate comments. Please remind yourself of the guidelines and take care to observe them in future. Ban me then. The person I responded to clearly has a mental illness and needs help. The people behind this site think it’s some bastion of civility, and it just isn’t. People can be assholes using any words they choose, and they do so continuously here, but you mods don’t care because your rules are followed. “Orange website bad” isn’t a meme for no reason. It’s because the orange website is bad. So fucken ban me. We don't need to ban you, we just need you, along with everyone else here, to observe the guidelines, the first of which in the Comments section, is to ”be kind”. If everyone made the effort to do that, the site wouldn't be bad. It's no big deal, and it's not that hard to observe the guidelines if you're sincere about making a positive contribution to the site.
Zdh4DYsGvdjJ - a year ago
TheNewsIsHere - a year ago
gnabgib - a year ago
mijoharas - a year ago
naikrovek - a year ago
1oooqooq - a year ago
naikrovek - a year ago
1oooqooq - a year ago
sebmellen - a year ago
naikrovek - a year ago
pdimitar - a year ago
naikrovek - 10 months ago
1oooqooq - a year ago
naikrovek - a year ago
tomhow - a year ago
naikrovek - 10 months ago
tomhow - 10 months ago