Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Updated rate limits for unauthenticated requests

github.blog

Post reply on HN
Print view View original

51–60 of 187 posts

Re: Updated rate limits for unauthenticated requests

#51

Post by blinker21 »

gnabgib wrote: post #3

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.

I'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.

Re: Updated rate limits for unauthenticated requests

#52

Post by homebrewer »

kstrauser wrote: post #32
turblety wrote: post #31

Earlier quoted context omitted.

Gitea [1] is honestly awesome and lightweight. I've been running my own for years, and since they've put Actions in a while ago (with GitHub compatibility) it does everything I need it to. It doesn't have all the AI stuff in it (but for some that's a positive :P) 1. https://about.gitea.com/

Gitea’s been great, but I think a lot of its development has moved to Forgejo: https://forgejo.org/ That’s what I run on my personal server now.

I'm stuck on the latest gitea (1.22) that still supports migration to forgejo and unsure where to go next. So I've been following both projects (somewhat lazily), and it seems to me that gitea has the edge on feature development.

Forgejo promised — but is yet to deliver any — interesting features like federation; meanwhile the real features they've been shipping are cosmetic changes like being able to set pronouns in your profile (and then another 10 commits to improve that...)

If you judge by very superficial metrics like commit counts, forgejo's count is heavily inflated by merges (which gitea development process doesn't use, preferring rebase), and frequent dependency upgragdes. When you remove that, the remaining commits represent maybe half of gitea's development activity.

So I expect to observe both for another year before deciding on where to upgragde. They're too similar at the moment.

FWIW, one of gitea larger users — Blender — continues to use and sponsor gitea and has no plans to switch AFAIK.

Re: Updated rate limits for unauthenticated requests

#54

Post by Novosell »

blinker21 wrote: post #51
gnabgib wrote: post #3

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.

I'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.

Hmmmm, Github keeps me logged in for months I feel like. Unless I'm misunderstanding the github security logs, my current login is since march.

Re: Updated rate limits for unauthenticated requests

#55

Post by usernamed7 »

gnabgib wrote: post #3

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.

1 request a minute?!? wow that's just absurd you get it for just looking through code.

Re: Updated rate limits for unauthenticated requests

#56

Post by zX41ZdbW »

jorams wrote: post #35

> These changes will apply to operations like cloning repositories over HTTPS, anonymously interacting with our REST APIs, and downloading files from raw.githubusercontent.com. Or randomly when clicking through a repository file tree. The first time I hit a rate limit was when I was skimming through a repository on my phone, and about the 5th file I clicked I was denied and locked out. Not for a few seconds either, i…

This can affect hosting databases in GitHub repositories.

Yes, it does not look like an intended service usage, but I used it for a demo: https://github.com/ClickHouse/web-tables-demo/

Anyway, will try to do the same with GitHub pages :)

Re: Updated rate limits for unauthenticated requests

#58

Post by out-of-ideas »

usernamed7 wrote: post #55
gnabgib wrote: post #3

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.

1 request a minute?!? wow that's just absurd you get it for just looking through code.

agreed. 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

Re: Updated rate limits for unauthenticated requests

#59

Post by jopsen »

PaulDavisThe1st wrote: post #42
new_user_final wrote: post #15

Earlier quoted context omitted.

Isn't git clone faster than browsing web?

Yep. But AI trawlers don't use it. Ask them why.

Do we know it's AI trawlers?

And not just generally degenerate bots? Or just one evil bot network?

Re: Updated rate limits for unauthenticated requests

#60

Post by mappu »

kstrauser wrote: post #32
turblety wrote: post #31

Earlier quoted context omitted.

Gitea [1] is honestly awesome and lightweight. I've been running my own for years, and since they've put Actions in a while ago (with GitHub compatibility) it does everything I need it to. It doesn't have all the AI stuff in it (but for some that's a positive :P) 1. https://about.gitea.com/

Gitea’s been great, but I think a lot of its development has moved to Forgejo: https://forgejo.org/ That’s what I run on my personal server now.

The development energy has not really moved, Gitea is moving much faster. Forgejo is stuck two versions behind and with their license change they're struggling to keep up.
Post reply on HN