Great news! We just got some packaging work done that's going into the rebase branch. It is now possible to build #AppImages and installers again!
On top of that, SHA256 hashes are now automatically generated, and we now build our installer with #CPack using a custom #CMake script, so all packaging is the same process. When we bring back nightly builds, this will be a nice way to verify your download. Plus, it will save us a few steps in packaging official binaries 
Something that would be really nice to add to #KDE and Kinoite is a section in Application Permissions for managing #AppImages
Basically everything they do for #Flatpak but in AppImage terms. Gear Level essentially. They already have a (imo superfluous) subsection for X11, let's expand it while we're at it
No they aren't exactly sandboxed the way Flatpaks are so the perms might not work the same, but an integrated menu to manage them would go a long way.
More integrations for managing packages of all types would be good actually
I want to right click a desktop shortcut to a flatpak, appimage or snap and get a menu that links to the Permissions page
I want to open the Permissions page and get an About info screen and a 1-click uninstall button instead of sending me to Discover. Why are you sending me to Discover? What if its not listed in Discover?
I want to double click an RPM, DEB or .desktop and have that give me options for installing that to my native package store, distro/toolbox or rpm-ostree
Mmk this is actually driving me up the wall
Is there something about #appimages that breaks the menu bar from working properly on KDE?
I've installed the same app from a flatpak and from an appimage and it's only on the appimages that the menu bar is completely missing
Wow, @baleine added the ability to build #AppImages with #Guix. This is a very neat addition imho to `guix pack`. Well done!
Their Fediverse post which has the patch's URL:
Haven't tried it yet, but I know Nitrux Linux relies heavily on AppImages. Does Nitrux use an actively maintained version of FUSE2? Beautiful distro, btw, Nitrux people. (5/?)
#linux #AppImages #infosec @Nitrux_NX
If the default linux system is less secure with the old packages needed to run AppImages, why are security-focused companies like Bitwarden still putting out official AppImages? (4/?)
#linux #AppImages #infosec @bitwarden
But it seems that AppImages are getting left behind (or should get left behind??) if they are relying on deprecated and usually unmaintained back-end software. Why when I search the web for FUSE and FUSE2, is almost all the of the focus is on how to macguiver your system to be less secure? (3/?)
#linux #AppImages #infosec
Thanks @75watt for finding the Fedora maintenance info. My internet searching skills were not up to the task. (2/?)
#linux #AppImages #infosec
AppImages are fine. But only if you know you are getting your FUSE2 maintained, like in Fedora[^1] (?maybe others??). If you have to download libfuse2.* yourself to make them run, or aren't sure if your libfuse2.* is being maintained anymore, then that is a potential security hole for your system. Fediverse, please correct me if I'm wrong. (1/?)
#linux #AppImages #infosec
[^1] https://packages.fedoraproject.org/pkgs/fuse/fuse/
OK, AppImages are easy, too. Same as any other distro. I'm liking Aurora more and more.
#Linux #Aurora #AppImages #LinuxPackagingMess
