Aw hell no.
post
I'm more excited about their possible contributions to the xdg portals.
Flatpaks need a more mature permission system that puts the user in control so that DE & standalone app store devs can make it powerful enough for the experienced user and easy enough for casual users.
Eww. Embrace, extend, extinguish?
I'd be more impressed if they stopped bundling random crap. It's their unwillingness to use upstream's dependencies and toolchains that makes Chromium a nightmare to package on Gentoo, and flatpaks are not going to fix that. They bundle clang, rust, and so many additional libraries that the "must keep bundled version to prevent breakage" list is almost 300 items long. This is not the correct way to ensure reproducibility, guys.
I’ve been using the Flatpak version of Ungoogled Chromium for a while now (for websites that don’t work natively with Librewolf). Is this really that new?
I thought that Flatpak breaks unprivileged user namespaces
Flatpak does block userns. Apps on Android don't get unprivileged user namespaces, and Chromium is at its strongest on Android. So I have to assume there is some way of making it secure inside an app sandbox.
Thankfully Librewolf still uses AppImage as an option.
The only Flatpak I bother with is the Kodi one because my distro has incompatible (read stable) library version on several things for compiling it and I'm considering just jumping to jellyfin for that, as well.
all 6 comments