Paco Hope #resist<p>OK <a href="https://infosec.exchange/tags/Debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Debian</span></a> <a href="https://infosec.exchange/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> people. Help me out with <a href="https://infosec.exchange/tags/AppImage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AppImage</span></a> programs and conventions. I get it: they're self-contained binaries, a little like the .app format on macOS. But when I look at some documentation online about how to use them, I see idiotic things.</p><p>People suggest downloading them from the web, <strong>leaving them in whatever folder they happen to land in, like Downloads</strong>, changing the permissions, and the executing them. This leads me to some basic questions:</p><ol><li>Where should I put them? I am NOT going to leave a pile of AppImage programs <em>that I rely on</em> in a random directory like <code>~/Downloads</code>.</li><li>How does one keep them up to date? I have to go to the web site, use human eyeballs to look and see if there's a new version, and then update myself, by hand? Surely in AD 2024 this is a step backwards.</li><li>How do I integrate them with my Gnome desktop so they launch when I login?</li></ol><p>All these basic problems are solved with a management layer like APT or flatpak or snap. Is there some AppImage management layer I'm just not familiar with?</p><p>I wanted the Nextcloud desktop app for Debian. <code>Apt</code> has 3.7.3, which is from 2023-02-09. Snap has 3.13.4, which is from 2024-09-13. The <a href="https://nextcloud.com/install/" rel="nofollow noopener noreferrer" target="_blank">Nextcloud web site</a> simply provides an AppImage file.</p>