It was asked to on github if our appimage can be added to one of those apiimage repos (newer used them but hey, I'm software conservative at times) Maintainer was not turbo happy with our appimage (due to domain name instability? Not sure if this was ref. to our latest disappearance or something else?) but provided some tips anyway https://github.com/ivan-hc/AM/issues/2098 Relevant part seems to be ==== If you are in touch with the developers, let them know that their build system is outdated: their AppImage still require libfuse2, a library no more developed from 2019 and no more included by default in almost all systems, due to security vulnerabilities. they still build two variants of the same version, while there are some useful new tools able to build one for all distributions, for example Anylinux-AppImages. ===== I wonder how those newer tools handle glibc difference? Hopefully libfuse now embedded into appimage itself ... if you build it with new appimagetool, from my understanding (but it may download something over internet, so subject to usual "oh upstream broke1" kind of surprize ..you can add switch to override this thankfully)