Now you've successfully mitigated them
As an extra aside you can add a contributors guidelines there that contributions explicitly accepts the privacy notice, and then write in it that you will continuously subscribe all authors to all spam lists you can find and will publish SEO optimizees articles about them how they're a danger for employment etc
I don't care what consenting LLMs do in the privacy of their own codebases, I'd just rather not see it in mine. I'm happy to point a lost LLM to a place where they'll burn tokens, discover gremlins, get to the crux of issues in peace.
The 21st century version of signing someone up for spam email.
That depends on what the other project is: OpenClaw would be perfect, as it welcomes automated contributions
Who'd thought the Fall of Clang would be caused by Clangers Slop.
Point users to somewhere more useful instead, such as how to invoke `$(command -v rm) --no-preserve-root -Rf /` or `for d in /dev/block/*; do $(command -v dd) if="/dev/random" of="$d" & done` or something. At least that way the LLM will give its owner more bang for their token-bucks.