- cross-posted to:
- programmerhumor@lemmy.ml
- technology@lemmy.world
- cross-posted to:
- programmerhumor@lemmy.ml
- technology@lemmy.world
You must log in or # to comment.
One of us
Its bound to happen more and more. More concerning, what is it decides to insert unknown code into backups? How are they detected? Who’s guarding all if these? Another AI?
Exactly. We aren’t (and probably won’t) even learn about all the subtle poisoning happening, causing waste and data loss.
If you are giving your codegen LLM - the model involved truly, genuinely doesn’t matter - admin access to your prod env, all I’m going to do is point and laugh.
Just to add - AND ACCESS TO THE BACKUPS!!
and having the backups stored in the same location as the primary data
Then it’s not a backup, it’s just duplicated data.
Just a shit show top to bottom for sure
No one should be able to delete or change backups. This infra was in any case vulnerable to a ransomware attack as any bad actor that breaks in can delete the database and encrypt the backups with a key they promise to share in return for bitcoin.
Also no prompts, ironically, for operations like “Are you sure you want to delete the production database? (y/N)”
It’s amateur hour all around lol
I don’t understand what Railway is supposed to do here? If deleting a drive also deletes the backup, what’s the point of the backup?
I save space on backups by symlinking my data in a backup directory. It’s never failed!
You obviously should do a hardlink, as this is much safer
Hyperconverged backups FTW!
It saves on storage costs!
I XOR all the bytes of my data and write down the resulting byte value on a post-it as our backup.
Saves tons of space, it’s fully offline and I never had any problem with it.
My suggestion is to not give it access to the backups, but may I’m naive that way.
No bro you don’t understand, Claude needs access to backups so it can restore them in case something breaks because our senior dev ($50k, 2YoE) doesn’t know how to do it
Damn, you got two-year-olds making 50k?
Maybe their backup system should hold onto those backups for a few days after the volume is deleted or something like that…
Hot take: offsite, offline backups are so cool right now.
Yup, follow the 3-2-1 rule or you don’t have backups
Hotter take: do not give an LLM agent permissions you wouldn’t give a recently hired junior
Actually this is how AI should be viewed. Under the right circumstances it maybe saves lots of time, but it also might destroy, so treat it like you would an intern…
hell I’ve got a better backup methodology with my fucking cat photos
Man who shit his own pants horrified that his pants are full of shit.
Demands explanation from pants vendor.
I can’t believe that they criticized the vendor api for not having confirmation.
It’s a freaking API!!! It’s designed for automation, not direct human (or LLM!) use. If you added confirmation then devs would have to code automatic acceptance, which defeats the purpose.
It doesn’t make a bit of sense. Someone is passing the buck.
Everything is always somebody else’s fault.
In your analogy, I would think they would demand an explanation from the food vendor.
Demands explanation from local grocery store?
Yelling, “Who’s shit is this!?”
They can’t go rogue, they have no agency or desire or thought. What really happened is the thing specifically designed to do whatever the Plinko line with the most chips says did it because the incompetent dickheads who deployed it didn’t know how not to do that.
Fuck around and find out
wiping a volume deletes all backups
that sounds like a wonderful backup system 😂
This is fun to read. I hope people will have their actual intelligence activated after this.
They won’t but they will continue to accidentally create content for my amusement :D
If you are going to give an LLM a free pass to your whole prod database least you should do is to take weekly (or daily if plausible) offline backups of it. A hard limit against deleting stuff would be better.
PocketOS founder blames ‘Cursor running Anthropic’s flagship Claude Opus 4.6’
Fuck that. I’m blaming the PocketOS founder and every person in the chain of decisions that led to a clanker being given this level of unrestricted access to the database and the backups.
