Is "AI deleted it" the new "my dog ate it" ?
this post was submitted on 15 Oct 2026
326 points (93.6% liked)
Technology
88838 readers
3688 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
“Timmy, why did the dog have root access?”
sudo eat -rf ./Homework
~$ sudo eat -rm ./Homework
@crank0271@lemmy.world is not in the sudoers file. This incident will be reported.
sigh
~$ groups
crank0271 docker
~$ docker run -rm -v ./Homework:/mnt/Homework --entrypoint '/bin/sh' alpine:latest -c 'sudo eat -rf /mnt/Homework'
~$ groups crank0271 docker
~$ docker run -rm....
No joke, this is exactly what LLMs will do if they can't do something directly.
This is why I told some colleagues several times to NOT put their user into the docker group AND to set the docker command for Claude at least to 'ask every time'.
That fucker circumvents your guardrails all the time. "Oh I'm not allowed to read a .env file with the harness? Let's check cat .env!" Yesterday Claude even wrote a little python script to try to print the .env file, because he thought he'd need it to debug a container. (Spoiler - the problem wasn't even with some env vars and also the .env was just filled with dummy values as it is an example from a public repository anyways).
Soon it will be "Claude wrote a zero day container escape privilege escalation exploit because it was faster than working within the given limitations". I just don't give any LLM file system access
Agent deletes my data is the new dog ate my homework.
The article plainly states that the production company says it wasn't AI, but instead that it was human error that led to the data loss.
The AI-thing was merely a rumour.
they say specifically "inte är en ”AI-agent som agerat självständigt”" (double quote). which translate to an "not an "AI agent which acted independently". so depending if that counts as human error or not... still up to to debate. It probably was AI, just not someone shift+delete the wrong folder.
I do however blame the backup crew which definitely should've had their backups in place.
Humans run AI. Even if it was deleted by AI, it's still the responsibility of the person running it.
i would say it's the fault of whoever thought it was a good idea to hook it up to their data. the workers are just doing what they're paid to do and trying to put up with literal insanity or risk termination.
I blame the one who should have set the backups. Even if it was deleted by a malicious actor, they there's no excuse to not have backups
Let's not let the truth get in the way of a sensationalist headline. It only matters that you click.
I wonder how many similar stuff need to happens before people realize they still need to keep their brains on when using AI and know what they're doing.
Also, no backups? Bush league bro
I would be so fucking mad if I worked on this and some producer just gave AI direct access to the only copy.
I would be so mad if I was a producer, and there was only one copy of anything important.
Whatever the agent was actually doing, the real failure is that it had destructive write access to the only copy of finished work. That's a permissions problem before it's an AI problem — no automation, human or otherwise, should be able to hard-delete production assets without a human confirming the destructive step.
The fact that the season is just gone also tells me there was no immutable backup or soft-delete tier behind it, which is rough for a broadcast workflow where the footage is irreplaceable. Agents are getting broad tool access by default right now, and this is the cautionary tale for giving them delete rights alongside read rights.
Shouldn’t be giving them any rights at all
In 1997 a company I worked for "lost" a month of fully rendered 3D video. Big deal you're saying, but 30 days of a rendering farm in 1997 was worth a couple hundred thousand dollars.
Somebody formatted the drive by accident.
This shit happens all the time, it's appallingly common. I guarantee some idiot somewhere in the chain of command said no we are not budgeting $1,000 for a couple RAID arrays or backup drives
Happened to toy story 2 as well
https://www.newsweek.com/lightyear-producer-credited-saving-toy-story-2-after-deletion-1680072
How do you not have backups of this?
No backups? Maybe I can understand not having full duplicates due to the cost, but surely it was on a system with at least snapshots in place or something right??
Watch LGTM video
But they can restore from backups. They backed up their data, right?
Good. The more thins shit happens the more people will rip relying on it and see it as the unreliable bullshit that it is.
Oof.
As someone who edits my own videos for YouTube, can't imagine how much work that was. Just gone. Poof.
Oh well. Don't use bullshit AI next time.
håhåhåhå
Nope.