Live data from Hacker News

Incident with Issues and Webhooks – Resolved

githubstatus.com

251–260 of 275 posts

Re: Incident with Issues and Webhooks – Resolved

#251
post #83

Earlier quoted context omitted.

It isn't. Lots of unacceptable things going on these days and everyone seems to be accepting them just fine.

I think it's like some kind of collective inferiority complex. Nobody really understands things anymore but everyone is afraid to point out mistakes of others because they are scared to come under scrutiny themselves then.

I don't think it's an inferiority complex, negativity sells more and carefully understanding things doesn't sell as much

Re: Incident with Issues and Webhooks – Resolved

#252

Earlier quoted context omitted.

This is extremely interesting how fast this happened. Either AI use surged massively in the last quarter, or this is a very sneaky move by Anthropic. Looking at my own stats, I don't think I'm using Claude Code much more than I used to, but my commits have gone way up. I have a feeling they've tuned the models recently to commit more often, which gives the illusion of more work being done.

> Either AI use surged massively in the last quarter December 2025 is considered by many people to be a major step function in agentic coding (both due to improvements in harnesses and LLMs themselves). I know my coding has forever changed since then. Before I was basically always hands on the keyboard while working with AI. Now I'm running experiments with multiple agents over the weekend, only periodically checking…

Whats your setup? How are your agents not running out of context and becoming dumb as a rock after ~100k tokens? Do you have a heartbeat thing on spawning more agents every time?

Re: Incident with Issues and Webhooks – Resolved

#253

Earlier quoted context omitted.

> Either AI use surged massively in the last quarter December 2025 is considered by many people to be a major step function in agentic coding (both due to improvements in harnesses and LLMs themselves). I know my coding has forever changed since then. Before I was basically always hands on the keyboard while working with AI. Now I'm running experiments with multiple agents over the weekend, only periodically checking…

Whats your setup? How are your agents not running out of context and becoming dumb as a rock after ~100k tokens? Do you have a heartbeat thing on spawning more agents every time?

Opus has 1M context now. In my experience it starts getting increasingly dumb after about 700k, but below that it is very usable. I don't think I've ever ran out of context window since they brought that out.

Re: Incident with Issues and Webhooks – Resolved

#254

Earlier quoted context omitted.

> Either AI use surged massively in the last quarter December 2025 is considered by many people to be a major step function in agentic coding (both due to improvements in harnesses and LLMs themselves). I know my coding has forever changed since then. Before I was basically always hands on the keyboard while working with AI. Now I'm running experiments with multiple agents over the weekend, only periodically checking…

Whats your setup? How are your agents not running out of context and becoming dumb as a rock after ~100k tokens? Do you have a heartbeat thing on spawning more agents every time?

The most important thing for any agentic task is to build up and continue to record context as a project develops.

The start of basically any project involves building up and documenting context around the project itself (and for a new company, the organization itself), this is kept at multiple levels of granularity (cross project, project specific, task specific, and human readable documentation). All experiments are planned out and documented as they go.

This becomes extremely important because after a weekend of running experiments stakeholders (and myself) often have questions, with everything in memory or some other stored context it's trivial to get answers to all sorts of questions.

Maybe it's because of this, but in both Claude Code and Codex I haven't run into any issues with models getting "dumb as a rock", even after compaction (or occasional full terminal crashes) they seem to have no trouble marching on.

Re: Incident with Issues and Webhooks – Resolved

#256

Earlier quoted context omitted.

> Either AI use surged massively in the last quarter December 2025 is considered by many people to be a major step function in agentic coding (both due to improvements in harnesses and LLMs themselves). I know my coding has forever changed since then. Before I was basically always hands on the keyboard while working with AI. Now I'm running experiments with multiple agents over the weekend, only periodically checking…

> Each experiment is a branch (or work-tree) so yes there are a lot of commits happening, but the results are measurably real. If you are correct , and GitHub is scaling its compute mostly as a reaction to this externality (agents churning through code that will mostly be discarded), then you can look forward to getting billed for your usage. After all, it is hard to build a scalable system without back-pressure.

I've already started moving my personal projects off github and onto forgejo running on my homelab. I know a lot of people doing the same. With a hermes-agent for a sysadmin I can debug problems from my phone, so I wouldn't be surprised if I have more "9s" that GH.

But if it ends up costing extra for GH, especially for work usage, then it's just a simple calculation of "is this worth it?" which I suspect for most cases will be 'yes'.

Re: Incident with Issues and Webhooks – Resolved

#257

Earlier quoted context omitted.

We should make an alternative git site, but how to acquire users?

codeberg is doing fine

If measured the same way, ie combined status across all products, then codeberg is also at a whopping 0 9s.

https://status.codeberg.org/status/codeberg

Re: Incident with Issues and Webhooks – Resolved

#258

Earlier quoted context omitted.

> Each experiment is a branch (or work-tree) so yes there are a lot of commits happening, but the results are measurably real. If you are correct , and GitHub is scaling its compute mostly as a reaction to this externality (agents churning through code that will mostly be discarded), then you can look forward to getting billed for your usage. After all, it is hard to build a scalable system without back-pressure.

I've already started moving my personal projects off github and onto forgejo running on my homelab. I know a lot of people doing the same. With a hermes-agent for a sysadmin I can debug problems from my phone, so I wouldn't be surprised if I have more "9s" that GH. But if it ends up costing extra for GH, especially for work usage, then it's just a simple calculation of "is this worth it?" which I suspect for most cas…

> [...]it's just a simple calculation of "is this worth it?" which I suspect for most cases will be 'yes'

Once the landgrab-stage flat-pricing goes away, it will become a case-by-case calculation because unsupervised agents can (and will) run up your billing with zero understanding of the business value of what they're instructed to solve.

Re: Incident with Issues and Webhooks – Resolved

#259
post #166
post #77

Earlier quoted context omitted.

From the GitHub COO on April 3rd: Platform activity is surging. There were 1 billion commits in 2025. Now, it's 275 million per week, on pace for 14 billion this year if growth remains linear (spoiler: it won't.) GitHub Actions has grown from 500M minutes/week in 2023 to 1B minutes/week in 2025, and now 2.1B minutes so far this week. So we're pushing incredibly hard on more CPUs, scaling services, and strengthening G…

After the Microsoft acquisition GH marketing and pricing put an immense amount of effort[1] into trying to kill secondary platforms that integrated into github and move more corporate accounts fully on-platform. We recently dropped travis for github actions and dropped reviewable for github PRs (which are terrible ). There's a portion of this that is agentic driven and there's a portion of this that's just github mak…

That sounds like their classic EEE

Re: Incident with Issues and Webhooks – Resolved

#260
so funny that I was migrating my agent workflow off of github issues today and while I was trying to run a regression test against a run of the old github workflow it gave timeouts related to issues being down, been getting nothing but trouble the last few weeks from having github manage the project/issues
Post reply on HN