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

31–40 of 187 posts

Re: Updated rate limits for unauthenticated requests

#31

Post by turblety »

xnx wrote: post #25

It sucks that we've collectively surrendered the urls to our content to centralized services that can change their terms at any time without any control. Content can always be moved, but moving the entire audience associated with a url is much harder.

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/

Re: Updated rate limits for unauthenticated requests

#32

Post by kstrauser »

turblety wrote: post #31
xnx wrote: post #25

It sucks that we've collectively surrendered the urls to our content to centralized services that can change their terms at any time without any control. Content can always be moved, but moving the entire audience associated with a url is much harder.

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.

Re: Updated rate limits for unauthenticated requests

#33

Post by kstrauser »

voidnap wrote: post #7
pogue wrote: post #4

I assume they're trying to keep ai bots from strip mining the whole place. Or maybe your IP/browser is questionable.

I encountered this on github last week. Very agressive rate limiting. My browser and IP is very ordinary. Since Microsoft is struggling to make ends meet, maybe they could throw a captcha or proof of work like Anubis by xe iaso. They already disabled code search for unauthenticated users. Its totally plausible they will disable code browsing as well.

That hit me, too. I thought it was an accidental bug and didn’t realize it was actually malice.

Re: Updated rate limits for unauthenticated requests

#34

Post by TheNewsIsHere »

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’ve almost completed the move of my business from GitHub’s corporate offering to self-hosted Forgejo.

Almost went with Gitea, but the ownership structure is murky, feature development seems to have plateaued, and they haven’t even figured out how to host their own code. It’s still all on GitHub.

I’ve been impressed by Forgejo. It’s so much faster than Github to perform operations, I can actually backup my entire corpus of data in a format that’s restorable/usable, and there aren’t useless (AI) upsells cluttering my UX.

Re: Updated rate limits for unauthenticated requests

#35

Post by jorams »

> 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, it lasted long enough that I gave up on waiting then refreshing every ~10 seconds.

Re: Updated rate limits for unauthenticated requests

#37

Post by kstrauser »

TheNewsIsHere wrote: post #34
kstrauser wrote: post #32

Earlier quoted context omitted.

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’ve almost completed the move of my business from GitHub’s corporate offering to self-hosted Forgejo. Almost went with Gitea, but the ownership structure is murky, feature development seems to have plateaued, and they haven’t even figured out how to host their own code. It’s still all on GitHub. I’ve been impressed by Forgejo. It’s so much faster than Github to perform operations, I can actually backup my entire cor…

I agree with every word of that.

For listeners at home wondering why you'd want that at all:

I want a centralized Git repo where I can sync config files from my various machines. I have a VPS so I just create a .git directory and start using SSH to push/pull against it. Everything works!

But then, my buddy wants to see some of my config files. Hmm. I can create an SSH user for him and then set the permissions on that .git to give him read-only access. Fine. That works.

Until he improves some of them. Hey, can I give him a read-write repo he can push a branch to? Um, sure, give me a bit to think this through...

And one of his coworkers thinks this is fascinating and wants to look, too. Do I create an SSH account for this person I don't know well at all?

At this point, I've done more work than just installing something like Forgejo and letting my friend and his FOAF create accounts on it. There's a nice UI for configuring their permissions. They don't have SSH access directly into my server. It's all the convenience of something like GitHub, except entirely under my control and I don't have to pay for private repos.

Re: Updated rate limits for unauthenticated requests

#39

Post by mijoharas »

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.

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.

Re: Updated rate limits for unauthenticated requests

#40

Post by fragmede »

immibis wrote: post #29
fragmede wrote: post #26

Earlier quoted context omitted.

This is the same Microsoft that owns LinkedIn which got sued by HiQ which is where the ruling came from that is making sites login required.

Wow! Website terms of use actually meant something in a court of law!

that wasn't what the case was about, so not really.
Post reply on HN