| ▲ | Kriev 3 hours ago | |||||||||||||||||||||||||
Bad take. You can rm -rf your entire hard drive, but you can't blame rm for it, it's you who did it, maybe because you don't know, or a mistake, doesn't matter. When you ask the clanker to delete x number of files in a directory, it can reason itself that is easier to just get rid of the directory. Can't expect deterministic outcomes out of a statistical model. At it's current state its a wildcard, sure you can build guard rails, reduce permissions, but it's still a wildcard. Let's not kid ourselves saying is just a skill issue. | ||||||||||||||||||||||||||
| ▲ | BeetleB 3 hours ago | parent [-] | |||||||||||||||||||||||||
> When you ask the clanker to delete x number of files in a directory, it can reason itself that is easier to just get rid of the directory. Oh sure, so don't give it write access to anything important. And make backups. Mine is on a VM. It doesn't have access to my host's files. The worst it will do is delete the files on the VM. No great loss. Yes, I do get it to modify things on my host, but only via a REST API I've set up on my host, and I whitelist the things it can do (no generic delete, for example). I even let it send emails. But only to me. It can't send an email to anyone else. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||