Imagine your friend that does not know anything about linux, don’t you think this would make them not install the firefox flatpak and potentially think that linux is unsafe?

I ask this because I believe we must be careful and make small changes to welcome new users in the future, we have to make them as much comfortable as possible when experimenting with a new O.S

I believe this warning could have a less alarming design, saying something like “This app can use elevated permissions. What does this mean?” with the “What does this mean?” text as a clickable URL that shows the user that this may cause security risks. I mean, is kind of a contradiction to have “verified” on the app and a red warning saying “Potentially unsafe”, the user will think “well, should I trust this or not??”

  • @[email protected]
    16•6 months ago

    They should be worried. We don’t want them comfortable.

    So many negative things have entered our culture bc people don’t care about dangers. Nearly every app should have a warning

    • @AeonFelisEnglish
      15•6 months ago

      Nearly every app should have a warning

      No. If you put a warning on every app (except for the most trivial ones that don’t actually do anything useful) then the warnings mean nothing. The become something more than ass-covering legal(ish) BS.

        • @AeonFelisEnglish
          8•6 months ago

          What do you mean by “improving”? This alarming warning appears because Firefox requires permissions. Let us look at the permissions listed there:

          1. “User device access”. From the docs, I’d say the browser needs it for rendering?
          2. “Download folder read/write access”. This one is obvious - the files you download with your browser go there.
          3. “Can access some specific files”. This one, I’ll admit, is a bit cryptic - what files does it need to access? But this one is on Flatpak for making the permission so general.

          App permissions should not be about “this app cannot be trusted because it asks for scary scary permissions”. They should be about “take a look at the list of permissions the app requests and determine whether or not it make sense for such an app to need such permissions”.

          • @[email protected]
            2•6 months ago

            To 1.: dri instead of all would handle hardware-accelerated rendering. Then some webcams or controllers won’t be accessible though. This one’s a bit complicated, since the necessary portals for e.g. generic USB device access aren’t yet there.

            To 2.: portals should be used instead of that. Using them doesn’t require these permissions.

            To 3.: click on details and see. This is Flathub making it easy to understand for users.

            Permissions should make clear whatever dangerous things an app can do. If not, why do all this effort of isolation? Firefox could delete everything in downloads, either by accident on Mozilla’s side, or a privilege escalation. If the app used portals instead, it couldn’t, at least without user interaction. Or a browser security vulnerability could open up any USB devices to webpages. It’s all about what could happen with granted permissions. And these can 100 % be fixed in at least some way.

    • @[email protected]
      5•6 months ago

      They should not be worried, they should be educated.

      If you worry a new user enough they’ll go back to Windows or Apple because there’s less scary warnings there.

      We need to make the transition as pain free as possible. Learning about the joys of kernel compilation and SELinux can come later.
      The first step is "Hey, this is as usable as Windows, without stupid ads in the start menu.