• Blisterexe@lemmy.zip
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    6 months ago

    Ok yes it is proprietary, but at least it’s from the main source and is confirmed to work well, which reduces risk, at the cost of sandboxing.

    it’s a tradeoff, and I think mint did the right thing.

    • boredsquirrel@slrpnk.net
      link
      fedilink
      arrow-up
      1
      ·
      5 months ago

      The Flatpak meanwhile is transparently packaged, using the binary from the official Snap.

      Canonical to my knowledge took forever for convincing Spotify to support Linux. Supporting Flatpak should be easy, but whatever.

        • boredsquirrel@slrpnk.net
          link
          fedilink
          arrow-up
          1
          ·
          5 months ago

          Yes but this was just an example of the hypocrisy of this action.

          1. Apps that are FOSS are possible to trust. Proprietary apps are simply liability, and proprietary software is constantly spying anyways. Flathub has --subset=floss for that
          2. “Verification” i.e. upstream support is not the case with a majority of Distro packages. Flathub has --subset=verified for this very nice ability (but this does not mean that unverified apps are worse than distro packages!)
          3. Flatpaks are isolated using Bubblewrap. Firejail, a common alternative for native app sandboxing, had a root binary and thus you need to trust it a lot. Bubblejail is a predecessor of it, but it is not easy to use at all and in early stages. So Flatpak offers stupid simple app isolation similar to Android, Distro packages dont have this.

          Flatpak is really good. You can look at the permissions, any app with the “safe” rating is probably safe, even if it is malware.

          Btw the safety rating would be a good filter, once they solve the false negatives of stuff like ProtonPro/pupGui.