That is a rate limit. That user was probably abusing something and trying to scrape github and got hit by a rate limit. Or someone in their house/flat/building did. There is just not enough in that post to tell what the hell is going on and it is far too early to jump to the concluding that github has done something wrong here.
They might have lowered the rate limits, they might not have. I doubt the lowered it to 3. Something else is very likely going on. We have to stop jumping to the worst conclusion anytime anything happens and imminently knee jerk reacting to that idea. We can wait for more information to come through and see what the actual issue is before assuming the worst.
I can reliably trigger rate limiting by rapidly switching between files. Sometimes it’s after looking at 10 files, sometimes up to 30. At any rate, it’s not something a regular user would do (and at that point, why not just clone the repo?), and the rate limiting clears in less than a minute. It’s really no worse than having to deal with Anubis-chan.
People just love to freak out, I guess.
I was able to duplicate this with some semi-rapid poking around in files which is not uncommon behavior when I am looking at a new project. If I didn’t use Gibhub for work, there is little chance I’d be logged in most of the time and this would definitely affect me, I am surprised by people defending this crap.
All these forges are being pummelled by LLM training idiots. They are all doing stuff like rate limiting. It’s a cat and mouse game as the AI companies make their scrapers look like humans. You will see this kind of thing, and captchas, more and more.
I can’t replicate this issue, still works fine for me
Interestingly I notice this happens on domains behind cloudflare but only in FireFox.
I don’t think this is GitHub trying to be malicious, I think this is someone else trying to be.
Walled gardens everywhere.
