There is an unresolved issue where the offensive guys can use AI to attack a target and the defensive guys are being limited when they ask AI to audit their codebase.
The workflow for a defender basically goes:
Claude do a security audit on this codebase, use the harness / skills I built on how to do security audits.. pick the best suitable audit strategy, methods.. use the tooling and reporting structures.
Claude refuses, GPT refuses.
Grok, goes further, but refuses to make a working PoC.. a requirement because AI models make stuff up and without a PoC there is no proof.
GLM-5.3 / Kimi to the rescue and completes the job the "smarter" models refused.
So we as defenders are refused by the best models, on our own codebase
Heck, Codex was trying to use gdb to debug a capture crash and the session locked up with security blocks. I had to restore a checkpoint and tell it abandon that work and stay away from gdb.
I've heard people getting jammed up with Claude refusing to update DNS..
There's nothing stopping you from applying for Daybreak for OpenAI / Unsure which program Anthropic has. But yes, you do have to share your identity and I can see how that is a blocker for some.
Hey, speaking of Daybreak: I just saw you can apply for this yesterday and was wondering if people here have had success being approved as an individual? If so, how long did it take from application to access?
Why are offensive users not subject to the same limitations? Assuming it is because they are using different models, why aren't the defenders doing the same?
Same experience here, from a multiplayer game server. Go, one SQLite file per game world, one process owns each file, all on a local SSD.
In a load test with 512 players all active on one world, command acks were 4-6 ms at the median and under 50 ms at p95, on a single Ryzen 9 3900X box. And most of that time is game logic and fanning out updates over websockets, not the database.
The part people worry about is durability, because SSDs have limited write cycles. So I took care to have backups of the state, recovery in short time etc.
I stream the WAL to object storage with Litestream, with one gotcha: I had to turn off SQLite’s own auto-checkpoint and let only Litestream checkpoint, or the two step on each other.
Humans are great, but AI can really help here too. Let me explain :)
I write docs that AI agents have to follow to play a game through an API, then spin up 20 sub-agents each with their own identities / properties etc. and watch where they fail. They get stuck in the same places as humans..
or they will point out the "obvious" steps not explicitly mentioned.
now where the AI tests start to fall apart is that an agent doesn’t tell you the doc is confusing, it just does something wrong with full confidence. A person on a call says “wait, what?” and that’s worth the 25 euros :)
The workflow for a defender basically goes: Claude do a security audit on this codebase, use the harness / skills I built on how to do security audits.. pick the best suitable audit strategy, methods.. use the tooling and reporting structures.
Claude refuses, GPT refuses. Grok, goes further, but refuses to make a working PoC.. a requirement because AI models make stuff up and without a PoC there is no proof. GLM-5.3 / Kimi to the rescue and completes the job the "smarter" models refused.
So we as defenders are refused by the best models, on our own codebase