Good change.
- It helps the less tech savvy users,
- It actually forces developers to write their app properly.
Software should not operate at a privileged level “just in case”, but rather have a well-defined functional boundary.
This is a most excellent place for technology news and articles.
Good change.
Software should not operate at a privileged level “just in case”, but rather have a well-defined functional boundary.
Protect the user from themselves.
All of computing beyond programming with switches is “protecting the user from themselves.”
“Why use a language? Aren’t you able to perfectly program in binary? I’m not going to waste time building something just because you’re stupid.”
MacOS is an open platform, I am glad you have to jump through a few hoops to put yourself in danger unlike windows
So, you didn’t read the article
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.
Yeah, I read it. That’s kind of the point. Apple’s adding more guardrails because people will click Allow on damn near anything without thinking about what they’re actually giving access to. 🙄
Or an update adds it without your knowledge…
Correct me if I’m wrong, but I don’t think an app could give itself Full Disk Access without the user explicitly approving it, even during an update.