Notices by Oro "it's flatpak time" 🏳️‍🌈 (orowith2os@tech.lgbt)

@LunaFoxgirlVT only so long as you don't get distracted and drive after a chimken

@LunaFoxgirlVT @jannem

It seems I left out some information, I edited it in. CLI interfaces still exist, and I use them quite often. They're just not the same as traditional packages, and best suited to be built on top of with aliases and the like.

I don't use `flatpak run org.flatpak.Builder` every single time I want to run the command, especially since it's one I use VERY commonly. I alias it to something that fits my needs.

You don't hate Flatpak.

You hate the fact that developers don't need to track down 10 times more bugs, at the *minimum*.

You hate the fact that developers don't need to rely on other people to package and ship their software to end users.

You hate the fact that developers don't need to support at least four different environments, all with different libraries and versions.

You hate the fact that developers don't have to deal with the bullshit that's been plaguing the Linux desktop for the past 20 years.

You hate the fact that developers can feasibly ship their software to end users in such a way that it's sustainable for the long term.

You hate the fact that developers are less stressed and can put more time into making their software better.

If you reply to this with something like "but mah CLI app support", "but mah storage", "but mah 5 FPS", or "but some stuff breaks" then read my replies to similar comments here, or consider that everyone has room for improvement.

#Flatpak #Linux #Flathub

@jannem

No, we aren't going to support CLI apps. We can make the experience better for limited use cases, but for the vast majority of CLI apps, Flatpak is not relevant.

CLI applications are completely different from GUI apps. They *need* unrestricted access to the system, otherwise they fail to work. There's no equivalent of portals for the CLI, nor will there be.

Flatpak also has no plans to support installing with the traditional package names. This is an anti-feature. The closest you'll get is this, which allows exporting multiple commands: https://github.com/flatpak/flatpak/pull/5404

As I stated in that pull request regarding a comment of similar type:

"No. This would conflict with the system binaries, and several apps exporting the same command could be messy."

If you want something like Flatpak for CLI apps, look at Nix. It handles things much better while providing the same level of dependency sandboxing.

@jannem

All the GUI apps that also have CLI variants are very limited, and are not user-facing.

The minority of people want this anti-feature, a minority which aren't very relevant for any GUI apps. GUI apps on a remote system are a minority of a minority.

If you want to start it from the command line, look into how dmenu and friends handle it; last I checked, you could make them list the desktop file names instead, which would probably help out.

Having an anti-feature that can cause more issues than benefits is not worth it, especially when you take into account the extra development time needed that would be better placed elsewhere.

A fun little #Inochi2D detail you might not know about.

The magic bytes for the INP container format are TRNSRTS, and will be TRNSRTS2 in v2 of the format.

Originally posted by @LunaFoxgirlVT on Twitter.

#FOSS #transrights #magicbytes

#Wayland haters be like I need my compositor to use insecure outdated protocols for window management and an inefficient design and handle rendering and fonts and be network based when I'm only using it on a local machine while also running with root for maximum security vulnerability and not promote secure and modern ways of interacting with my desktop if it can't sandbox files and dbus then it shouldn't need to sandbox window contents either

https://discourse.flathub.org/t/flathub-in-2023/3808

2023 is looking to be pretty nice for #Flathub and #Flatpak:

- Separation of Flathub from #GNOME (GNOME previously provided legal services for Flathub)
- Funding (100k from https://www.endlessnetwork.com/ for 2023)
- Governance (so people know easily who's in charge of Flathub, and what's going on)
- App uploads *directly* from developers (no need for a repository on Flathub)
- Donations and payments from users, to help make developing for the #LinuxDesktop more sustainable
- Security (scanning apps and suggesting developers and packagers to fine tune the permissions and keep dependencies up to date and secure)

Looking forward to Flathub in the future, it's already pretty comfortable. Thanks for you do, @FlatpakApps and Flathub devs.