Artificial truth

Personal blog of Julien (jvoisin) Voisin

In 2020, my friend anarcat published the CLA Denial-Of-Service attack , an interesting musing on the possibility of weaponising CLA, boiling down to: find a critical bug figure out a [non-trivial] patch for the bug publish the patch in their issue tracker forever refuse to sign the CLA The obvious solution to this conundrum is to perform clean-room reimplementation : have a person read the patch and produce a specification, then have a second distinct person read the specification and produce a patch. It's not a silver bullet, as the less trivial the change, the lengthier the specification, an

related reading

• Guardian Angels: LLM Personalization for Productivity and Security · Gwern.netgwern.net
• Security incident disclosure — July 2026huggingface.co
• 2025: The year in LLMssimonwillison.net
• The L in "LLM" Stands for Lying — Acko.netacko.net
• Here’s how I use LLMs to help me write codesimonwillison.net
• Designing agentic loopssimonwillison.net
• Nicholas Carlininicholas.carlini.com
• Stop Sloppypasta: Don't paste raw LLM output at peoplestopsloppypasta.ai
• GitHub - multica-ai/andrej-karpathy-skills: A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls. · GitHubgithub.com
• [2312.06942] AI Control: Improving Safety Despite Intentional Subversionarxiv.org
• What I learned this week - Can distillation be stopped, Mythos and the cybersecurity equilibrium, Pipeline RLdwarkesh.com
• Things that helped me get out of the AI 10x engineer imposter syndrome | Hacker Newsnews.ycombinator.com