Tootfinder

🛡️ Safety is code, not prompting. PathGuard blocks .env, storage, vendor and .git. BudgetTracker aborts the session when estimated spend passes the limit. Shell modes off, allowlist, approve and yolo gate execution — production defaults to shell off and worktree on.

Was that really Googlebot? Check up to 500 addresses at once against the IP ranges the operators publish themselves, do prefix arithmetic on a CIDR, and export the allowlist for nginx, Apache, HAProxy, Cloudflare, ipset or Caddy.
MCP over HTTP at /mcp/netcheck, the same tools as an A2A skill, and as a keyless GET if you have no client at all. Read-only, no signup.
#MCP #A2A #AI #opendata

So I'm getting fed up with #spam on #Gentoo #Bugzilla.
A while ago we've introduced a timed block on new accounts posting URLs. It helped for a while. But now someone actually bothered implementing a dedicated tool, and we're getting a daily create-wait-post loop. I can't think of a really good way of getting rid of this.
So far I was thinking of:
• blocking new accounts based on the predictable e-mail pattern (they're just going to switch patterns, also may hit real users)
• limiting URLs pasted to an allowlist (this is going to suck hard)
• requiring manual request for every account via IRC (this is going to be pain for us, for users, and a lot of people just won't bother)
It really feels like whatever we do, it's going just to cause pain to us, to our legitimate users, and the spammers will just slop their way around it.
And on top of that, every comment posted is fucking #slop. Totally meaningless sentences added to random bugs, in the hope that we're too stupid to see that they've just spammed us.
I hate this timeline. Can we do Butlerian Jihad now, please?