Two AI agents both enforce the same rule:
"Preserve attribution on every derivative."
Same sentence. Both pass every check.
Agent A reads "derivative" as anything trained on the source.
Agent B reads it as only recognizable look-alikes.
They just shipped opposite policies. Nothing caught it.
@wittmer0313@WhiteHouse@POTUS What you mean he failed? He straight up lied to your face! There was no intention of doing anything he promised. But he did use the presidency to finally become a billionaire.
Working today: validator, Frame server, Bridge, 15-case
conformance corpus.
Not built: signing. The spec says how, nothing verifies yet.
Saying that up front.
Draft 0.1. Nothing stable.
The ask: build it independently, tell me where the spec was vague.
https://t.co/a7CVKe9ew3
Two AI agents both enforce the same rule:
"Preserve attribution on every derivative."
Same sentence. Both pass every check.
Agent A reads "derivative" as anything trained on the source.
Agent B reads it as only recognizable look-alikes.
They just shipped opposite policies. Nothing caught it.
I've spent 30 years in music watching people go uncredited.
It almost never starts with somebody lying. It starts with two
parties using the same word to mean two different things, and
nobody checking.
Turns out agents have the exact same problem.
I got this Kicked back to me in Claude Code:
I'd hold off on running that. Let me flag what it actually does before you execute it:
curl -L https://t.co/okBvhj915D -o kickbacks.vsix # download a VS Code extension from https://t.co/eNkBRV0usX
code --install-extension kickbacks.vsix # install it into your editor
Why this is risky:
Unvetted source. https://t.co/eNkBRV0usX is not the VS Code Marketplace. There's no publisher verification, no review, no signature check. The -L flag also follows redirects, so the actual download could resolve anywhere.
A VSIX is arbitrary code. Installing an extension grants it the ability to run code in your editor context — read every file in your workspaces, exfiltrate source/secrets/tokens, run shell commands, and inject into anything you type. There is no sandbox boundary protecting you here.
The name is a red flag. "kickbacks" plus a freshly-coined .ai domain and a bare /vsix path is the profile of something you'd want to be very sure about, not something to pipe straight into install.
What I'd do instead:
If this is an extension you actually want, find it on the VS Code Marketplace (or Open VSX) and install from there, where it has a known publisher and you can read reviews/source.
If you got this command from an email, DM, repo README, or chat message — treat it as untrusted. That's a common malware delivery pattern.
If you want, tell me where this came from and what it's supposed to do, and I can help you vet it (check the domain, inspect the VSIX contents before installing, etc.).
I'm not going to run it as-is. Want me to help verify it safely, or were you looking for a specific legitimate extension?