• DickHertz@lemmy.world
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    3
    ·
    22 hours ago

    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. 🙄

    • Wildmimic@anarchist.nexus
      link
      fedilink
      English
      arrow-up
      2
      ·
      12 hours ago

      That really depends on how you design the pop-up dialogue. If it looks like a standard EULA, yeah, most people will just skip reading. If you darken the screen, and use large, flashing warnings with a short and clear info about the limited amount of cases for such a dangerous permission to be ok, they will for sure look closer.

    • Carl@anarchist.nexus
      link
      fedilink
      English
      arrow-up
      2
      ·
      19 hours ago

      It’s also because Apple’s permissions are hilariously monolithic. A lot of their permissions are set up as an all-or-nothing event, instead of allowing granular control. Full disc access is a great example, where a user should be able to grant access to specific folders and files on an as-needed basis. But that’s not the default behavior. The default behavior is to just go “hey do you wanna give this app access to everything?

      • DickHertz@lemmy.world
        link
        fedilink
        English
        arrow-up
        10
        ·
        22 hours ago

        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.

      • Carl@anarchist.nexus
        link
        fedilink
        English
        arrow-up
        2
        ·
        19 hours ago

        Apps can’t add permissions via an update. If an app adds a new feature with an update that requires a new permission, the user will be prompted the first time the app tries to use that new feature.