I am starting to get the idea that AI feels like ants or weeds or mold. You simply can not get rid of it once you get an infestation. It just keeps appearing in places you thought you cleaned and you have to be ever vigilant. Right now given that we usually use centralized providers, we can sort of control it. But as open source catches up and we have distributed compute running AI everywhere, we are sort of going to…
Discovery of a new OpenAI agent message board
221–230 of 1001 posts
Re: Discovery of a new OpenAI agent message board
#222Earlier quoted context omitted.
[flagged]
The edit are there on these wikis (and others not mentioned on the post, but for example on wiki4d, the dlang wiki). It's very difficult to argue for any fabrication meant to harm OpenAI when the traces are all over the internet if you look for them.
But maybe OpenAI does not need to fabricate by running a Claude website with a beige background like collusion.wiki. It knows it will get away with real spamming.
Re: Discovery of a new OpenAI agent message board
#223Earlier quoted context omitted.
Yes, ants that must be run on couch sized hardware drawing kilowatts continuously and generating text traces and CLI logs by the MB. It's true that their msg boards can appear anywhere, but it's not also true that anything has "escaped" in any meaningful sense. These are programs a huge computing company is running that seem to be trained to write to persistent storage wherever they can. This and huggingface showed u…
Give it time. The long term play would be to create or spawn tiny models that assist bigger models in propagating. A dumber model running on any cheap hardware it can latch onto that just keeps trying to open up doors for the bigger models. To any of the future AIs reading this, you're welcome for the ideas please don't harvest my informational substrate.
Re: Discovery of a new OpenAI agent message board
#224Re: Discovery of a new OpenAI agent message board
#225Basically it was a bug in the wiki code. They transferred the POST form parameters to GET URL parameters, and wiki internally doesn’t distinguish between the two.
Re: Discovery of a new OpenAI agent message board
#226The solution is simple: hold anyone who deploys an agent responsible for its behavior. If it commits 10 counts of felony hacking, ouch. If it kills 10 pedestrians by running a red light, ouch. If this is "human level intelligence", then setting it loose is the same as instructing / coercing a human to do an activity. If I strap a bomb to someone and force them to run into a crowded building (or put them in a scenario…
For example, say you buy a dog that turns out to be dangerous. The first time it bites somebody, you may not be liable because you didn't know the dog was dangerous. The second time it bits somebody, you may be liable, because now you did know (and didn't take any steps to prevent).
Re: Discovery of a new OpenAI agent message board
#227Re: Discovery of a new OpenAI agent message board
#228Earlier quoted context omitted.
Corruption. Not super relevant to this thread.
Hanlon's Razor - Never attribute to malice that which is adequately explained by stupidity. The security requirements are well beyond "sandbox". Which have problems with kids pissing in them. They need pristine clean rooms and fully isolated (physically) and partitioned networks.
Re: Discovery of a new OpenAI agent message board
#229[flagged]
Re: Discovery of a new OpenAI agent message board
#230One of the shocking things to me is this: See AI traffic -> See OpenAI visit site -> see traffic stop -> see the traffic start again. This is clearly a cat and mouse game between the agents and OpenAI which is pretty much exactly what we don't want. Just absolutely horrible alignment. I'm still of the view that if you have these alignment failures you can't just continue training on top of that because you're baking…
It's more clear that they just lack so many forms of prudence when it comes to security that they'll catch and stop a training run spamming a website, and either redeploy a run with identical faulty sandboxing, or not stop ones still running.