net.lutris.Lutris

Flatkill is full of misinformation or no longer true information. There're many posts debunking most of their points [1]. Some parts were true a few years ago but aren't anymore. Edit: They removed many of their examples at some point, so it's no longer as bad of an article. For example if VSCode wouldn't have direct access to the file system, it would be unuseable since it doesn't support portals to ask the user to grant it access to specific folders (by selecting them through the file picker). In the process of packaging an app for flathub, the packager has to provide some reason for why for example full file system access is necessary. The discussion to add or remove permissions are always open [2]. [1] https://theevilskeleton.gitlab.io/2021/02/11/response-to-fla... [2] https://github.com/flathub/net.lutris.Lutris/issues/229

Examples of popular apps that can write to the host filesystem (and remember kids, the ability to write to $HOME always means full account takeover, followed shortly by root access if your account can sudo): - vs code (https://github.com/flathub/com.visualstudio.code/blob/91e589...) - chromium (https://github.com/flathub/org.chromium.Chromium/blob/1edd4a...) - sublime text (https://github.com/flathub/com.sublimetext.three/blob/d1f617...) - obs studio (https://github.com/flathub/com.obsproject.Studio/blob/051f6f...) The applications above also provide other dangerous privileges, but they pale in the presence of filesystem access. Examples of applications that have full device access (which is considered insecure and called "not ideal" in the flatpak docs), as well as sharing a bunch of namespaces like network and IPC (meaning these parts a