4 ms·

My understanding is snap and flatpak are not equivalent at all because snap is more permissive whereas flatpak is sandboxed. Specifically, it is not possible t

by mcny 7y ago

My understanding is snap and flatpak are not equivalent at all because snap is more permissive whereas flatpak is sandboxed. Specifically, it is not possible to do gpg signed commits from flatpak (e.g., jetbrains idea) without tweaks upstream. I agree with the overarching idea though: it gets worse before it gets better. See wayland and how we still can’t capture display in obs. I am a little torn on this. Should the onus to “fix” be on jetbrains and obs? I personally think no where possible. Replacements should be drop in without effort or at least with clear guidance and not too much effort on behalf of individual applications.

stubish 7y ago
Snaps are sandboxed. They can be granted extra privileges, such as access to $HOME, camera, bluetooth etc. Some of these interfaces such as $HOME can be gained automatically by any snap. Others need to be granted by Canonical (to automatically grant access on install), or manually granted by the user post install. There is also a 'classic' mode where the app is unsandboxed, which again needs to be granted by Canonical and in addition requires explicit acceptance by the user when being installed.
beagle3 7y ago
"classic" snaps are not sandboxed, and you have to acknowledge that when installing them. "modern" snaps are sandboxed, and you can change their permissions in the Settings/Control-Panel app. You might argue with the choice of permission granularity, but it IS there.