Artificial truth
dustri.org · 584 words · saved by 1 readers
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
- The L in "LLM" Stands for Lying — Acko.netacko.net
- 2025: The year in LLMssimonwillison.net
- The growing divide between AI hype and software engineering realityoptimizedbyotto.com
- AI is removing the middle class of software engineeringblog.florianherrengt.com
- Simulated Users & Sad LLMs1a3orn.com
- List of posts - <antirez>antirez.com
- 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
- we have a year to fix security everywherejyn.dev
- Debating the role of large language models in the kernel communitylwn.net
- slopfree-software-indexcodeberg.org