this post was submitted on 03 May 2024
995 points (97.0% liked)

linuxmemes

21222 readers
79 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] eager_eagle@lemmy.world 8 points 6 months ago (1 children)

    It's still a valid complain, but the problem is not exactly the presence or absence of a confirmation IMO, it's a deeper matter.

    What causes user desensitization (I guess that's a word) is a direct result of how Windows users traditionally install software - from untrusted sources or by downloading them directly from a vendor's website then manually installing it.

    UAC would be just fine if it was a rare thing to see, but because of this "download a .exe > double click > install" flow users see it all the time, which defeats the purpose of the warning. It became just another half-measure Windows has implemented.

    [โ€“] Buddahriffic@lemmy.world 2 points 6 months ago

    And it's unhelpful because it doesn't give any details about what it wants to do with that admin access and also treats permission for one action as permission for all actions (not that you can tell what they first action you're permitting is).

    I like the way android does it, where you can grant or revoke special permissions by category of action.

    Though the system I'd like to see is one where each program is sandboxed and then even you close the program (or it prompts for an elevation), then you get a list of system differences between the sandbox and your system and can choose whether and which changes to push from the sandbox env into the main env. Or to combine sandboxes so that programs can interact with each other.