3 ms·
Flathub: One million active users and growing
- zdware 3y agoI'm glad they mentioned Steam Deck! I figured there would be a healthy bump from that.
- Kalanos 3y agoDocker is considering a flatpak. Upvote here: https://github.com/docker/roadmap/issues/593 https://github.com/docker/roadmap/issues/593 flatpak is like a cross-distro snap that actually works. some of the apps are buggy at the fringes, but i've been opening issues to smooth them out. some of the apps like VS Code claim to be from microsoft, but are... unofficial?
- NekkoDroid 3y ago> some of the apps like VS Code claim to be from microsoft, but are... unofficial? Unless they have a verified checkmark next to the company/owner of the project it will be a 3rd party package of it. The name is mainly intended as a "This is from X" instead of "This is packaged by X" (unless you actually see the verified badge)
- xcrunner529 3y agoI so far have been disappointed because some of the main things I I shall and had are a browser and password manager and they can’t talk to each other and flatpak refuses to fix it.
- 4oo4 3y agoThis is by design iirc, as a consequence of sandboxing. However there is an easy workaround, which is redirecting your browser profile back to the host with flatpak override/flatseal. I don't need this anymore for Bitwarden but I did this for a long time with Firefox + Enpass.
- xcrunner529 3y agoSo is the iPhone and they provided ways to make it work. It’s a use case that is needed so they should be trying to find a (secure) way to do it.
- Spivak 3y agohttps://github.com/flatpak/xdg-desktop-portal/issues/655 https://github.com/flatpak/xdg-desktop-portal/issues/655
- starkparker 3y agoNo movement on the associated PR since November?
- different_base 3y ago> flatpak is like a cross-distro snap that actually works You are right. Besides proprietary app store, Snap lacks even basic sandboxing in non-Debian based distros. I can't believe that Canonical engineers thought this was a good idea when designing a cross platform packaging format. Flatpak got everything right from it's initial design. Multiple repositories, Sandboxing that actually works in any Linux distro, OSTree to reduce disk space usage etc.
- banger180 3y agoI really like flatpaks, easy to install and work with. Definitely superior over Ubutnu's snaps. As a user you do have to be somewhat aware that the application is running in a sandbox and won't behave exactly like one running without a container. For example the Belgian digital ID card software does not work in a sanboxed browser. At least not by default a the moment.
- anthk 3y agoStill no GUI a la synaptic as without pulling half of KDE (Discover) or Gnome (Gnome Software).
- reddit_clone 3y agoA TUI would be a good addition?
- l72 3y agoIs flathub.org not a great GUI for browsing apps. If you click the down arrow next to 'Install', it gives you the command to install from the command line, so it's just a quick copy and paste. Or you can download the .flatpakref and define your own app handler instead of gnome-software. The handler just has to run `flatpak install /path/to/app.flatpakref`. A quick bash script + something like zenity (for gui dialogs) could take care of that.
- palata 3y agoAn opinion (not my blog) about Flatpak (just to trigger discussions): https://ludocode.com/blog/flatpak-is-not-the-future https://ludocode.com/blog/flatpak-is-not-the-future
- sph 3y agoOne day we will be able to talk about Flatpak without being sidetracked into deconstructing this stupid post. (And the one at flatkill.org — I've seen it posted so many times it's burned in my brain) Alas, today is not that day.
- palata 3y agoSorry, I'll shut up.
- peter_d_sherman 3y agoInteresting article! My takeaways: >"The current solutions involve packaging entire alternate runtimes in containerized environments. Flatpak, Snap, AppImage, Docker, and Steam: these all provide an app packaging mechanism that replaces most or all of the system’s runtime libraries, and they now all use containerization to accomplish this." [...] >"All of these technologies are essentially building an entire OS on top of another OS just to avoid the challenges of backwards compatibility." This is basically using containers to replace all system libraries -- to insure that a downloaded binary app always works. From this point forward, we'll use the term "API" to represent not just Linux kernel syscalls, but the totality of all library calls (system and otherwise!) used by a given downloaded binary application! Observation: API (in-)consistency (AKA "Stability") one Linux version to another, one Linux distro to another -- is the real problem! That's the real cause! Because everything else, everything else, is effect, not cause! The containerization, the bloated "everything but the kitchen sink" downloads, are the effect of the problem of API (in-)consistency! Phrased a simpler way -- there is absolutely NO guarantee of consistency between the libraries, system and otherwise, of any two Linux distros! So if a binary app is to run on all Linux distros -- then it had better damn well better make sure that the exact specific version of all of the libraries that it needs -- are managed by it, not the host operating system! Containers and bloated library downloads -- are (unfortunately) currently necessary to provide this! Related: "Linux Library Mismatch": https://www.google.com/search?q=linux+library+mismatch https://www.google.com/search?q=linux+library+mismatch "DLL Hell" (the MS-Windows equivalent) https://en.wikipedia.org/wiki/DLL_Hell https://en.wikipedia.org/wiki/DLL_Hell Software Engineering: Bertrand Meyer, "Design By Contract": https://en.wikipedia.org/wiki/Design_by_contract https://en.wikipedia.org/wiki/Design_by_contract API Contracts: "What is an API Contract?": https://www.youtube.com/watch?v=-qM__ozdHCU https://www.youtube.com/watch?v=-qM__ozdHCU Eelcho Dolstra: "The Purely Functional Software Deployment Model": https://edolstra.github.io/pubs/phd-thesis.pdf#page=11 https://edolstra.github.io/pubs/phd-thesis.pdf#page=11 Image-based Linux distributions and associated tools: https://github.com/castrojo/awesome-immutable https://github.com/castrojo/awesome-immutable Spencer Baugh: "Managing Dependencies": https://catern.com/posts/deps.html https://catern.com/posts/deps.html
- 2OEH8eoCRo0 3y agoWithout charging 30%? Impossible! /s Keep up the good work Flathub team!
- tracker1 3y agoI think that flatpak is the future. It would be nice to have some level of shared read only packages, like UI frameworks (gnome/kde etc) and a few other features could be better. A nice permissions interface so the manifest can declare, this app needs x, that you can approve instead of needing secondary apps to change permissions. I don't mind snaps. I'd like to see better integration to move AppImage downloads to a single location and add them to the apps menu directly.
- unintendedcons 3y agoReally enjoying Mint's approach to this. When the flatpak for Audacity fails to launch, uninstall and switch to a working version from apt all within the same window.