Replying to an earlier post

The people who use it to do things, obviously. Just like how cameras aren’t responsible for the photos that are taken with them, photoshop isn’t responsible for the images made with it, and knives aren’t responsible for the things that they cut, AI isn’t responsible for the stuff it outputs - the person controlling it is.

en

Replying to @⁨LilBobbyTables@lemmy.today⁩

Question is: Who is the person controlling the AI?

The one that allowed the agent to do stuff on its own?

The one that wrote the sandbox, that didn’t work?

The one that wrote the user prompt?

The one that wrote the system prompt?

The one that provides the tools to the AI agent to do stuff?

The one that hosts the model?

The one that fine-tuned or post trained the model?

The one that pretrained the model?

The people that provided the input data to the model?

Replying to an earlier post

Except, AI and AI companies will try to convince you that it is right and legal. So I argue that there is also the fault of AI and AI companies as it in intended to be used that way.

The assumption is that the user is supposed to know better but if the user is gullible then wouldn’t some of the fault be with AI and company for taking advantage?

If you don’t leash your dog and it attacks your neighbors then are you and the dog not at fault?

Replying to an earlier post

AI isn’t responsible for the stuff it outputs - the person controlling it is.

Ultimately, you’re right (as they can decide to use AI or not). But these AI Companies need to shoulder the blame for creating, promoting, and selling AI, which (in its current form) is effectively a “broken tool”.

Good computer hygiene says I should lock my computer while I’m away. Yet, I’m suppose to blindly install an AI agent on my machine and ask it nicely to focus on the task at hand and not use any of the other applications or credentials that might also be installed?!?! It’s ridiculous.

Replying to an earlier post

I’ve played around with Claude.

they can’t access anything you don’t give them permission to access.

It’s not that “they can’t” it’s more like “they try not to”.

For example, if you have a folder shared with your application code (/home/me/code/) - it has free reign on that folder.

If you add a prompt saying “you are only allowed to access files in /home/me/code”:

you could ask it " oh, what are my aws credentials “, it would have no qualms about reading those files (/home/me/.aws).

You could also ask it to update your settings (/home/me/.claude)

I eventually started to work on a way of running Claude in a docker container with real filesystem enforcement. …and it’s sneaky how Claude will get when it wants to read a file, it doesn’t have permissions for (using bash cat).

This was an exploration I’d made a year ago and I know Claude has a " sandbox” , but if you allow Claude to run bash commands - that sandbox is trivial to circumvent.

Replying to @⁨LedgeDrop@lemmy.zip⁩

All that is great, and correct, but my point is that it asks you to confirm its commands that it runs. It asks you to confirm every change it makes to your code. It asks you to confirm every file it creates.

Everything it does goes through your permission.

You also shouldn’t have it do anything anywhere close to a production system, so it shouldn’t be able to do anything of any consequence.

Replying to an earlier post

So basically use it as a toy for entertainment purposes only… Except it’s not marketed to be used that way and far to many people aren’t smart or educated in computing enough to use it that way. Accepting a bash command you don’t understand is the same as running a bash command you found on the Internet… You shouldnt, but people are far more trusting of the stuff an LLM powered agent comes up with.