5,851 karma · joined March 30, 2010
---
meet.hn/city/43.4652699,-80.5222961/Waterloo
Socials: - github.com/apetresc - mastodon:fosstodon.org/@apetresc
Interests: Books, Education, Open Source, Programming
---
Okay, can you concoct some prompt-injection-like scenario where you can fool increasingly sophisticated agents about the presence of your malware? Sure, maybe. It's MILES ahead of where both major app stores are today, though, where you can find obvious scams that sailed through review just by looking at their description.
I think you’re right about the analogy itself, though it’s far from clear that society owes it to your grandma to hinder everyone’s access to cheap tomatoes just so she can feel more useful for her tomato-growing abilities.
It’s not lobotomized, it’s a simple harness restriction that has nothing to do with the model or its capabilities. And either way, I’m not sure what that has to do with “negligence” or “intent”? You think frontier labs should be prosecuted because they don’t allow agents to turn off your PC?
The correct analogy would be, your mom can also just go to the supermarket and get much cheaper mass-produced tomatoes; which is… exactly the current situation?
> toast is for the developer who wants to stay in their terminal without spending hours getting it up to snuff.
I think he knows you can get anything you want in emacs/vim. The pitch is that toast is batteries-included.
You can't possibly expect Apple to take that market segment seriously.
You can’t convince me that I’m somehow the odd one out because I regularly have no trouble getting Claude to recolor buttons.
What this is referring to are those follow-up "here's two plausible alternative ways to do this, which one do you prefer?" questions you sometimes get, and usually at the beginning of a planning session when presumably you're still actively involved in the session. They get exponentially less likely as the turn goes on.
Maybe it's a good default, maybe it's not, I'll wait to pass judgment. But it's not security-related except in contrived scenarios you could construct where one side of an A-or-B UserQuestion has security implications that aren't caught by any other safeguard. I haven't ever really experienced that in practice.