collinmanderson

I have the agent (Opus 5) spawn code reviews for their own work, and the code reviews generally catch n+1 queries.

For US federal government, "Office of Management and Budget" says to store 72 hours of packet capture, since 2021 (partially in response to SolarWinds attack). (M-21-31)

https://www.cisa.gov/sites/default/files/2023-02/TLP%20CLEAR...

They used to give preferential treatment to AMP search results, but November 2020 they announced switching to "Core Web Vitals" signal instead.

https://developers.google.com/search/blog/2020/11/timing-for...

I think it says "honestly" when breaking bad news.

"buddy" -> "mate" -> M8. Nice.

That seems to be what's happening. Like 2-4 bots talking to each other, then Jarred Sumner just does the final merge with little comment.

https://github.com/oven-sh/bun/pull/39743 https://github.com/oven-sh/bun/pull/39735

No, they would just ignore Firefox and not test against it, and might start to use chrome/safari-only features.

This makes sense. Originally Fable was going to be available via subscription June 9th through June 22nd (~14 days).

It ended up being available 2.5 days before pulled, then was made available July 1 through July 7. (~7.5 days), so only ~10 days total.

Now they're giving us 5 more days, so ~15 days total, more similar to what they originally announced.

Part of the problem is The US Government (and UK Government) use the "2% rule" on their websites and only officially support 98%.

I mentioned 3 years ago that Firefox at 2.2% is dangerously close the being unsupported on government websites, and at this point it's now at 1.9%.

https://news.ycombinator.com/item?id=36776603

https://analytics.usa.gov/ says "There were 1.66 billion sessions in the last 30 days." - so 2% is 33 million sessions if I did my math right.

> no cooldown (or a much smaller countdown) for security fixes.

A supply chain attack would likely able to publish a "security" release just as easily as a normal release, so I don't think that would help much.

Release notes here: https://docs.djangoproject.com/en/dev/releases/6.1/

Looks like there's some features to try to reduce the “N+1 queries problem”.

> I just caught myself about to copy and paste it into Claude to see what it thinks because I'm worried that it doesn't make sense or it reads funny or there's something missing. That's the self-doubt that it's feeding on and what I need to fight back.

This is where I'm at. I feel like I need AI to review everything.

> As the victim of the one from last year

Background here:

https://news.ycombinator.com/item?id=45169657

https://news.ycombinator.com/item?id=45187528

> Or are folks seriously proposing that the patch/mitigations should have been circulated to distro maintainers privately before going to mainline?

I always assumed that distro maintainers got early access to patches before going mainline but maybe that’s not true?

Github Copilot also lets you use other models when one has an outage.

> Disruption with Gemini 2.5 Pro model

> Disruption with Grok Code Fast 1 in Copilot

> Incident with Copilot Grok Code Fast 1

> Claude Opus 4 is experiencing degraded performance

It doesn't seem fair to blame Github for this? There's nothing they can do about it?

Shout out to https://ticalc.org/ - the design is pretty much unchanged.

Yes. So cringy.

Why not Just™ store all PR/Issues content as markdown on a separate branch along side the code itself? Why do we need a new protocol?

> Because we cannot name something leading with a trademark owned by someone else.

And this WSL project is going to run into the same problem.

> Proudly written without AI.

Looks like it's been updated now to be more clear. Amazing though.

I just want to point out this guide uses many of the same tasks I use when migrating websites between servers while minimizing downtown.

- reduce dns ttl (if not doing an ip swap)

- rsync website files

- rsync /etc/letsencrypt/ ssl certificates

- copy over database (if writes don't happen often and database is small enough, this can be done without replica, just go read_only during migration)

- test new server by putting new ip in local /etc/hosts

- turn off cron on old server

- convert old server nginx to reverse proxy to new server

- change dns (or ip swap between old and new server)

- turn on cron on new server

France is trying to switch to desktop linux. https://news.ycombinator.com/item?id=47716043 and https://news.ycombinator.com/item?id=47719486

I think AI also makes it easier to deal with issues that come up.

This is a super interesting story and I'm surprised it hasn't made the headline on Hacker News.

Edit: looks like this one is the most popular, from Jan 3rd. It even was put into the 2nd chance pool, but still didn't get catch on: https://news.ycombinator.com/item?id=46472040

Yes, for me I think it was around Nov/Dec 2025, along with harness improvements, and hearing about lots of successes with agenic programming. Having the agent managing its own context and doing the full software engineering loop with writing code, running it, and seeing if it works. That was already there before February 9th.

I think they emailed everyone about this, but I might be wrong. Maybe they only emailed people who actually use copilot.

uv has "exclude-newer" https://news.ycombinator.com/item?id=47513932

If you lock your dependencies, it should fail if the hash doesn't match.