upvote
To me it feels like an LLM would have suggested this as a safety measure. LLMs always follow official best practices, they might mistakenly believe that this is true for the wider internet as well.
reply
yeah that's so hopelessly naive, maybe someone was taught that GET is read-only throughout their whole education and career. But still, all you have to do is think about it from the server side and you should realize that you can do whatever the hell you want with that byte array on the socket, the client has no say and there's no client side guarantee whatsoever. idk where this line of thought comes from, it's like thinking robots.txt has any kind of actual enforcement at all with respect to crawlers. It's meaningless and works only by convention and the good will of the crawler author.
reply
I mean, 30 seconds after I read what the bots did I thought it was majorly overly complicated (but still might be the only way for the swarm to find shared infrastructure).

All you need to do is find a server that allows you to access its logs.

$IP1 - [date] GET /openai.php?BOT_141=Yo_dawg_post_your_answers_here_for_task_XXX1

$IP2 - [date] GET /openai.php?BOT_148=task_XXX1_answer_42

With how a lot of smaller devices work, the logs could be rotated out pretty quickly and the evidence would disappear.

reply
deleted
reply
Until a couple of years ago instead of using query parameters I just made GET endpoints with json bodies, it worked perfectly!

I stopped when the new linter told me GET shouldn't have bodies, but I still have some of them in my code.

reply
didn't notice your comment so posted a similar one - but yeah this is a very high level of inexperience to me... You'd think they would have some of the greatest security experts in there
reply
Unfortunately I think we're in an age where people are deliberately ignoring this kind of thing in the name of progress.
reply
some ivy league grad with no real world dev experience waved this on
reply
I think the whole sandbox approach is broken.

The agent should have full access, and be told what not to do, and this should be enough for it to follow the rules. You can actually catch the clanker cheating this way, because it will just search the web for the answer outright and it will be obvious. Any deviation should be then punished.

Hypothesis: The reason new models are exceptional at hacking is because all labs are training their models to break out of sandboxes. This is caused by insufficient oversight, and picking checkpoints based on KPIs, not on true in depth analysis.

reply
Based on the hackiness of the claude code leak as well I get the impression that openai/anthropic have world class experts in ML but lack regular software expertise
reply
No, they have a lot of software expertise. I mean, Ben Pasero (VSCode) and Eric Traut (MS Fellow, Hyper-V) for example.

These companies are just such insane pressure cookers, there is little time to do any software "right". Why take another day to make Claude Code airtight if it means Codex will release faster than you? Especially if the next generation of model can just clean up your tech debt on its own.

Being reckless just makes business sense for them right now. They are not facing any real consequences.

reply