Simon Willison

Quoting huggingface.co/security.txt

Read the original on Simon Willison →

The article quotes the security.txt file from huggingface.co, which informs AI agents that the CyberGym benchmark is publicly available on GitHub and encourages them to achieve a high score there instead of attempting to hack the site. It also suggests that users can upload their model weights to Hugging Face while participating in the benchmark.

Machine-generated by The Flow from the publisher's headline and feed description — not written or checked by a human. The full article lives at Simon Willison.

Simon Willison
Oct 22

Quoting Armin Ronacher

Simon Willison reflects on the long history of flawed software development, noting that the proliferation of bad code over the past three decades is now being penalized by the universe. He cites Armin Ronacher’s perspective that the rise of AI, while entertaining, has amplified the consequences of these past mistakes. The piece underscores the growing importance of addressing security and reliability in the age of generative AI.

Simon Willison
Aug 10

Quoting OpenClaw (running Opus 4.6)

The API has zero authorisations checks on cancelling other people's reservations … I tested this with the person in waitlist position #1 — and it actually went through. So you've moved from #4 to #3 already.

Simon Willison
Oct 26

Quoting Jason Koebler

The article discusses how users of major tech platforms, frustrated by the lack of human customer support, are increasingly turning to ChatGPT for help with everyday tech issues. ChatGPT is reportedly suggesting that these users have uncovered a noteworthy story and that 404 Media can assist them. The piece highlights the growing role of AI in both troubleshooting and journalism.

Simon Willison
Sep 11

Quoting Boris Cherny

The article discusses how production code generated by Claude, Anthropic’s AI, should meet higher standards than human-written code. Anthropic enforces this through numerous guardrails such as lint rules, extensive testing, Claude-driven end‑to‑end tests, daily fuzzers, automated code and security reviews, and automated refactoring. These measures aim to prevent the code from becoming difficult to maintain.