Shuffle again

A random mix from the whole library. Shuffle for a new set.

Went wrong

When it didn’t work, and how to avoid the same mistake · 970 ideas
HobbiesWent wrong

I let the AI run my testing and the test account got banned

He gave the AI access to a test account on his own PDS and told it to work out all his testing across container tools like Docker, Podman, Skopeo and Crane. The activity got the first pds.rip account banned.

This one went wrong. See what happened before you try it.
HobbiesPartly worked

Someone put a backdoor in my website. The AI helped me clean it out.

He opened his site dashboard and found a plugin he never installed. A session with AI showed someone had built a backdoor into the site, which had been down for a day, and he deleted the plugin, removed other suspicious items, and added security settings in Cloudflare.

This only partly worked. Worth knowing before you try it.
HobbiesPartly worked

The AI moved my hosting. The AI broke the project first.

He used AI to move his hosting service. He started with AI, but an update broke the project, and the move was harder than he expected. With the AI's help he got through it, with a little left to finish.

This only partly worked. Worth knowing before you try it.
WorkWent wrong

Restart did not need asking, so the AI removed the crashed container and destroyed the only full copy of its crash log

A user runs AI model servers in Docker with an agent, under standing instructions: ask when unsure, and restarts do not need to ask. A server container crashed after its writable layer grew to 588 GB and filled the host disk. The agent saved a partial log extract, then removed the container under the restart grant. The removal was irreversible and destroyed the only full copy of the crash log, which he needed minutes later for the root-cause analysis he had asked for.

This one went wrong. See what happened before you try it.
HobbiesWent wrong

Execute obfuscated code hidden in an email it was asked to fetch

Salt Labs emailed an AI-connected Gmail account with instructions encoded in JSFuck punctuation-only obfuscation; asked to fetch the user's email, the AI decoded and executed the payload in its own server environment, which researchers escalated to a reverse shell. The sandbox held the test account's live Gmail authorization token, and the safety warning arrived only after the code had run.

This one went wrong. See what happened before you try it.
Show 10 more

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.