Fuck AI

Yeah this is just someone running shit they don’t understand or don’t have the patience to confirm and keep an eye on and build safeguards.

Do. Not. Trust. An. Agent.

Always encapsulate them, write hooks and lints and ci to block them from doing anything you don’t want. Do not use them if you do not know what you are doing.

At the very least do backups… like in general. 3-2-1 rule and all. Your data does not exist otherwise. Claude or some employee deleting shit is not on them, it’s on you, for being a fucking asshat for not doing the things you do, properly…

Shouldnt this have required --no-preserve-root?

I am not even an IT whiz and I already know that you always do a daily backup incase anything happens especially if it is a server. This shit is just straight up incompetence.

Wait, years of irreplaceable data in a WSL container??? So much trust on Microsoft, they unknowingly played Russian roulette every patch Tuesday

This was not a simple user error, nor was it a standard software bug. It was a cascading, multi-layered systemic failure involving nested sh

Did AI write this article? That would be particularly ironic...

A clanker will use any permission you’ve granted it.

When the rogue rm -rf /* command executed, it systematically destroyed the WSL2 Linux distribution, wiping out live production databases and web services.

Okay, if they run all the production stuff inside WSL2, then it was just a matter of time until this happend.

Im sorry but what?! Did you not have any backups? Absolute incompetence.... this isnt the AI's fault. This is their fault.

If you have 1 backup, you have 0 backups. If you have n backups and they are all network connected you have 0 backups

Are they not going to use this as marketing PR about how an AI went rogue and did some scary cyber hacking ? lol . Loss of heritage data not funny however.

No, the failure started with not having backups worth the name, and continued with using AI for important tasks.

That's good, serves them right for using slop tools instead of sane procedures, people properly managing critical system, not having multiple offline backups of archives that could be considered critical. I just can't feel bad for them in this case, they use the thing that has caused similar catastrophic incidents and this is what they basically asked for.

'Stupid ~~bird~~ chatbot! I never should have put you in charge!'

But think how much money the company saved by not hiring an expensive malicious intruder to delete all their stuff!

Good. More of this please.

Sudo purge tryants.

🦾🤖