6 ms·
60 req/hour for unauthenticated users 5000 req/hour for authenticated - personal 15000 req/hour for authenticated - enterprise org According to https://docs.
by gnabgib 2y ago
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-limits-for-the-rest-api?apiVersion=2022-11-28 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.
- usernamed7 2y ago1 request a minute?!? wow that's just absurd you get it for just looking through code.
- out-of-ideas 2y agoagreed. when i first read the title i thought "oh what did the they up the rates to" - then i realized its more of a "downgraded rate limits" thanks github for the worse experience
- rendaw 2y agoI opened a repo in a spare computer browser and clicked on a couple things and got a rate limit error. It feels effectively unusable unless you're logged in now (couldn't search from before, now you can't even browse).
- mijoharas 2y agoWhy 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.
- 1oooqooq 2y agobecause it will go way lower soon. and because they don't have to. they already have all your code. they've won.
- naikrovek 2y agoyou 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.
- 1oooqooq 2y agoit 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.
- sebmellen 2y agoEmbrace, extend, extinguish.
- naikrovek 2y ago… 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.
- pdimitar 2y agoI'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.
- Probiotic6081 2y ago[dead]
- naikrovek 2y ago> 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.
- blinker21 2y agoI've hit this over the past week browsing the web UI. For some reason, github sessions are set really short and you don't realise you're not logged in until you get the error message. I really wish github would stop logging me out.
- Novosell 2y agoHmmmm, Github keeps me logged in for months I feel like. Unless I'm misunderstanding the github security logs, my current login is since march.
- 1oooqooq 2y agoGH is Microsoft's most successful social network. GH now uses the publisher business model, and as such, they lose money when you're logged out. same reason why google, fb, etc will not ask you for a password for decades.
- zarzavat 2y agoYes, it's not the rate limits that are the problem per se but GitHub's tendency to log you out and make you go through 2fa. If they would let me stay logged in for a year then I wouldn't care so much.
- tux3 2y agoYou might be afflicted with some SSO or enterprise thing, I haven't logged into Github on my personal account in years.
- zarzavat 2y agoNope, just normal GitHub account. Though GitHub did force me to use 2fa earlier because they said I have a "popular repo", so perhaps my account is considered high risk. Or maybe it's triggered by travelling and changing IP locations? I have no clue, but it's annoying to have to 2fa more than once in a blue moon.
- 2y ago
- ikiris 2y ago1/min? That’s insanely low.
- notatoad 2y ago60/hr is not the same as 1/min, unless you're trying to continually make as many requests as possible, like a crawler. and if that is for your use case, then your traffic is probably exactly what they're trying to block.
- zarzavat 2y ago60/h is obviously well within normal human usage of an app and not bot traffic... A normal rate limit to separate humans and bots would be something like 60 per minute. So it's about an order of magnitude too low.
- mjevans 2y agoUse case: crawling possibly related files based on string search hints in a repo you know nothing about... Something on the order of 6 seconds a page doesn't sound TOO out of human viewing range depending on how quickly things load and how fast rejects are identified. I could see ~10 pages / min which is 600 pages / hour. I could also see the argument that a human would get tired at that rate and something closer to 200-300 / hr is reasonable.
- hansvm 2y agoAll of that assuming they're limiting based on human-initiated requests, not the 100x requests actually generated when you click a link.
- jakebasile 2y agoI bump into these limits just using a few public install scripts for things like Atuin, Babashka, and Clojure on a single machine on my home IP. They're way too low to be reasonable.