83 points darkwater 2 hours ago 73 comments
tempest_ 2 hours ago | parent
nijave 2 hours ago | parent
swatcoder 1 hour ago | parent
Rate limits, blocking, and pay-per-use are the only roads out and even those might not last as models get better at hacking and masquerading.
The internet we want to use LLM's with is simply not one that can support LLM's, and with LLM's not going anywhere, the whole experience of the internet is going to be forced into some radically less open and more expensive paradigm.
Policies like this just represent the beginning of the transition.
jayd16 1 hour ago | parent
Frieren 2 hours ago | parent
It may look impossible right now. But what is impossible for real is to continue as we are. The damage that internet does to society is increasing by the day while its value is reduced (economic value, social value).
phoe-krk 1 hour ago | parent
Except it's non-commercial, therefore valuable, therefore commercialized, therefore commercial.
You'd need a force strong enough to prevent it from falling prey to this tragedy of the commons, and that force would need to be stronger than the incentives to commercialize it. And that's where plenty of contemporary scraping-based salaries lay.
immortalist 1 hour ago | parent
OtherShrezzing 1 hour ago | parent
So, the precursor to online media has already gone through this paradigm shift.
pixl97 1 hour ago | parent
Which is partially true, but it only shifts the distribution of the problem. Once your service gains enough popularity network effects cause it to gain value. You have to worry about high priced buyouts of the entire service (great for the site owner, terrible for the users).
Zambyte 1 hour ago | parent
armadyl 1 hour ago | parent
Gating everything behind paid (but with no ads) likely would hurt a significant amount of lower income users.
heavensteeth 1 hour ago | parent
[0] One of many similar initiatives, I'm sure. Not an endorsement.
pixl97 1 hour ago | parent
Your human engagement will attract said predators because it's a unique information signal.
9dev 1 hour ago | parent
godwinson__4-8 1 hour ago | parent
> you pay to access social media optimized to be interesting...
So is it commercial or non commercial?
Nothing is stopping you from creating a social network that is pay gated. Go build it. If you can't get anyone to sign up perhaps you'll realize it's not so easy as scapegoating addictive social media.
There is a whole cottage industry of people who legitimately make their living criticizing Facebook. It's a consumer software product. Yet few of these people seem to have their conviction extend to building an alternative that ever catches an audience. Why is that? Because addiction? Any other excuses?
dwedge 34 minutes ago | parent
toomuchtodo 1 hour ago | parent
ddtaylor 2 hours ago | parent
One request per minute.
mplanchard 2 hours ago | parent
sandeepkd 1 hour ago | parent
Jaxan 1 hour ago | parent
MeetingsBrowser 1 hour ago | parent
Browsing open issues or reviewing a few PRs will easily use more than one request per minute.
The limits are based on the average user but I wonder if the most common interaction is to view a readme and bounce.
I don’t know that putting a paywall up to learn from or even consider contributing to public projects is a good thing.
silverwind 57 minutes ago | parent
ddtaylor 44 minutes ago | parent
Yes, you get 64 more bits to make whatever addresses you want, but the prefix is still your fingerprint.
sparkling 2 hours ago | parent
All of this is most likely due to mass scraping by LLMs. Welcome to the total shitification of the web.
Macha 1 hour ago | parent
296012 2 hours ago | parent
jtwaleson 2 hours ago | parent
cush 1 hour ago | parent
latexr 1 hour ago | parent
aprentic 1 hour ago | parent
If we had a system where people who access projects pay and popular FOSS developers get paid for it we'd have much better alignment.
My second thought was that bots would immediately try to circumvent such a plan. They'd probably spam Gitlab with fake repos to try to harvest those payouts.
cush 8 minutes ago | parent
Yeah I wonder if the math would shake out to make that make any sense. Each bot would require a paid subscription, so the only incentive for them to do this would be if there was some discoverability algorithm or SEO that that traffic helped push the content to real users
MeetingsBrowser 1 hour ago | parent
The guidance given seems to hurt open source projects, not help.
> Make the project private if the traffic is not coming from the audience you built it for, which stops anonymous callers reaching it at all. Or upgrade to Premium or Ultimate for much higher limits.
serhack_ 1 hour ago | parent
Retr0id 1 hour ago | parent
bearjaws 1 hour ago | parent
Gitlab must pay a fortune to bot traffic, most of which is malicious or garbage at best.
demibabs 1 hour ago | parent
vips7L 1 hour ago | parent
zb3 43 minutes ago | parent
Jeremy1026 38 minutes ago | parent
rcxdude 36 minutes ago | parent
svachalek 24 minutes ago | parent
wiether 10 minutes ago | parent
jmclnx 1 hour ago | parent
Getting that so I do not know exactly what they are doing. From the title I am guessing they are restricting or throttling if downloads exceeds some value.
bob1029 1 hour ago | parent
GraphQL is absolutely terrible for human developers to interact with, but it's like Facebook could see into the future back in 2012. I cannot imagine a more perfect API surface for agents. With the REST API on GitHub, you can consume maybe 10 issue JSON blobs before your context window is blown out. With GraphQL constraining the results you can easily read hundreds in the same token budget.
Additionally, the # of requests your agents need to make can be reduced in many cases since GraphQL can join across types whereas REST APIs cannot. You essentially get savings in two dimensions here. Quota and raw token volume per logical response.
aschobel 1 hour ago | parent
mattkrick 57 minutes ago | parent
For our company, we advertise the graphql schema to bots and they can one-shot whatever task they're trying to do. I've found that it's so good that I cancelled building an an MCP server and any skill. Just a well documented GQL schema. It's pretty remarkable.
enormousness 24 minutes ago | parent
sockbot 52 minutes ago | parent
CharlieDigital 36 minutes ago | parent
Most agents will use curl | jq to slice what they need (assuming a known API)
philipp-gayret 44 minutes ago | parent
As for GitLab, having hosted it for medium size organisations (~200 devs) and seeing how monorepo's work (they don't, we had GitLab's team show us that one page view made 50K db queries on our setup), please consult with your local admin team before firing GraphQL at it.
iamEAP 33 minutes ago | parent
You could argue the rate limit guards should better reflect that, but that’s just not the reality of the system. Likely speaks to a lot of stability issues GitHub has been facing lately.
enormousness 27 minutes ago | parent
kccqzy 12 minutes ago | parent
dieselgate 11 minutes ago | parent
I'm not familiar with graphql but what would make something "invoke git", is it a technical thing or hyperbole?
bob1029 11 minutes ago | parent
MeetingsBrowser 1 hour ago | parent
Hopefully they find some kind of carve out for OSS projects while still blocking the egregious offenders.
rkagerer 50 minutes ago | parent
lateatdesk 49 minutes ago | parent
throwitaway222 45 minutes ago | parent
mschuster91 22 minutes ago | parent
Is there a test endpoint where one can validate the behavior of their ratelimit detection? Basically I do not want to cause excessive load on your servers just to test my implementation.