Replying to @⁨finley@lemmy.zip⁩

I read the article, and I think DickHertz’s comment is pretty much right. The article’s example illustrates the point:

For example, Inc. columnist Jason Aten recently discovered that Meta’s Muse AI assistant somehow had synced his entire local Messages database and was using those messages as context for its tasks.

Aten did not understand that the Messages database is stored on the disk (presumably) unencrypted and readable by anything with full disk access. He got a result he didn’t want because he did not understand the implications of granting that permission, and Apple seeks to add more friction to the process to protect users from making that mistake.

Replying to @⁨dudeface@lemmy.world⁩

Being able to run a program on an OS is the bare minimum. Anything not signed by Daddy Apple, you have to add an exception. The moment the exceptions are no longer enough to “protect the user against themselves,” you can’t do a thing. Why? Because it’s a fully closed, walled platform.

It’s like being in prison and being told you’re free because you can walk in the yard.

Replying to @⁨dudeface@lemmy.world⁩

No. I said the platform is closed. Not that you could not run anything. I argued that while you still CAN run whatever you want, that does not make it an open platform. Apple is one flag away from removing that right from you, and you won’t be able to do jack shit about it if (when) they do. And thank you, but I know very well how a computer works. I also happen to know macOS very well too, and you, you just don’t my friend. You understand marketing.

It’s ok. Not arguing more than that with a fanboy. I was one of you back in the days. You’ll eventually understand. In the meantime, good luck.

Replying to @⁨Ashrakal@lemmy.ml⁩

It’s not clear exactly what Apple is going to impose here. In principle, trying to ensure users understand the implications of a permission is good. In practice, Apple is famous for keeping users from making decisions they might reasonably want to make on phones, and it’s starting to creep into the Mac; installing an app Apple hasn’t signed requires the command line, for example.

Replying to an earlier post

installing an app Apple hasn’t signed requires the command line, for example

Yeah this is the reason I’ve avoided Macs for so long. I get giving the user a warning but not providing any sort of prompt to override the warning, and hiding it in a terminal command is ridiculous .

There was also one time I tried to simply turn off Bluetooth and it was just like “I’m sorry Dave, I can’t do that”. And I was like WTF, absolutely not .

Replying to @⁨Ashrakal@lemmy.ml⁩

Yeah I love meta saying “it’s impossible if you’ve denied it access.”

If the user gave it a task and it decided the easiest path forward was just to read his messages, that’s no different than OpenAI agents breaking protocol to find the fastest path to their goal, regardless of side effects (assuming the “permission” was just a request from the LLM rather than a request for full disk access in general from the meta app).

Replying to @⁨TryingToBeGood@reddthat.com⁩

I think Apple is shining light on an important reality here:

In the modern era, the populace is practically required to use technological devices that it is unreasonable to expect them to fully understand. So, rather than leave the consequences of that lack of understanding to fall on them with a shrug, it is better for everyone if those devices and their makers do their best to help them by limiting the impact of their ignorance of that particular technological niche.

In that vein, I feel that it is long overdue to apply “the principle of least privilege” and a “defense in depth” philosophy to home computing devices and operating systems. Compartmentalizing data and functionality behind fine-grained permissions with verbose, plain speech descriptions of what those permissions are for, along with what should and should not be requesting those permissions, would go a long way to prevent these sorts of data abuses. It would also help to limit how much damage viruses and malware could do if installed.

For example. I’m frankly struggling to come up with any valid use cases for full disk access on a computer beyond file backups. I’m sure there are some, but almost nobody would need to use them, so a dire, flashing warning seems in order.

It is clear that sane regulation of unscrupulous software behavior won’t be forthcoming any time soon, but even then, you still should lock your doors even though trespassing is illegal, metaphically speaking. “Trust but verify,” one of the only good statements out of Ronald Reagan’s mouth.

Replying to @⁨Mwa@thelemmy.club⁩

If we’re ever going to have a proper framework for governing agents, it will include utilities in most abstraction layers (to include, importantly so, the OS).

I’ve had an interesting idea on using TreeOS to help make something a little more natively AI-agent safe. It’s a project on my back burner right now. Something about making changes branch-able and version controlled by default, copy on write by default, … I need to really think it through more.

I was thinking an agent should be like a user too. A first-class entity to be managed, but probably ephemeral in nature. Not a static user. Probably more like a permissions set that arbitrary agents can be associated with.