Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • Github would hit four nines if they followed suit. no clue why the dont try
  • 60 requests per hour per IP if you haven't signed in... well that's unfortunately low.
  • I assume this is because of LLM scraping.
  • > A request that arrives with no credentials gets 60 requests per hour per IP address.

    One request per minute.

  • Damn, we’re even having Claude write important press releases now
  • Providing kickbacks to the repos being scraped would be a good way to help fund open source projects and pay creators like streaming services do. Seems like they're headed in this direction - it would be a massive product differentiator over GH
    by cush
  • Important buried context: 60/hour unauthenticated, but 5,000/hour on the free plan.

    60/hour sucks. 5000/hour (a little more than one per second) is totally fine.

    I'm chalking this up alongside Docker's decision to restrict unauthenticated pulls. Unauthenticated anything went the way of the dodo some time ago. If you want unauthenticated access, go run your own mirror.

  • If you are using LLMs to interact with sites like GitLab and GitHub, and you have the option to use a GraphQL API, you should jump on it immediately.

    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.

Explore Birbla archives