

Your screen.


Your screen.
I do wish something like AM’s functions was built into an all-in-one package manager for my distro. The closest I found was bauh which handles “AppImage, Debian and Arch Linux packages (including AUR), Flatpak, Snap and Web applications”. Which seems like an all-in-one solution.
But the problem with bauh (that last time I tried it) is that it accesses only a small number of (often very out-of-date) AppImages from the largely moribund AppImageHub.com, unlike AM, which pulls in the latest releases from loads of GitHub repos, and adds more on a frequent basis or request.
AM puts all AppImages in /opt for me, as well as automatically creating menu entries, easy updates etc.
I use AM package manager for that.
Personally, I use AM. Takes care of that and more.
It is CLI and I’m GUI by nature, but AM is easy enough for me. Just yesterday I did a simple
am -u and got the latest updated versions of qBittorrent, FreeTube, yt-dlp etc. (I.e. the kind of program that system packages are too out of date to work safely or even work at all.)
There are other options like zap (CLI), Gear Lever (GUI) and just recently I believe the Nitrux distro came out with a complete AppImage software manager. (Checking it out, https://github.com/Nitrux/nx-software-center , it seems it pulls from AppImageHub.com, which unfortunately has largely been forgotten by developers, a lot of software is either out of date, unverifiable or completely absent. AM is much more up-to-date, pulling the latest AppImages mostly from official GitHub repos.)


Netcraft now confirms: BSD is dying.
Thanks for the info.
Personally, I’ve been avoiding Flatpaks anyway on my main machine, but not out of security concerns. Mainly to do with size and the update frequency.
I see now, this is linuxmemes@lemmy.world, not @lemmy.ml. My bad, comrade.
Is this a Firefox reference?


I wish Mozilla would use some of their millions to bring a class action lawsuit against sites that pointlessly lock people out just because they’re not using Chrome/Safari/Edge.
I was under the impression Flatpaks are sandboxed. (I am not an expert.)
Flatpak is a utility for software deployment and package management for Linux. It provides a sandbox environment in which users can run application software in (partial) isolation from the rest of the system.
I also keep Ungoogled Chromium around as a last resort (AppImage in my case).


“Distro of Gaming Excellence”


Musk has a distro???


A meme is a great way to avoid their fury; Lynx doesn’t show images.


I believe using a CDN would defeat the author’s goal of not being reliant on third-party service providers.


A problem with this approach was that many readers use VPN’s and other proxies that change IP addresses virtually every time they use them. For that reason and because I believe in protecting every Internet user’s privacy as much as possible, I wanted a way of immediately unblocking visitors to my website without them having to reveal personal information like names and email addresses.
I recently spent a few weeks on a new idea for solving this problem. With some help from two knowledgeable users on Blue Dwarf, I came up with a workable approach two weeks ago. So far, it looks like it works well enough. To summarize this method, when a blocked visitor reaches my custom 403 error page, he is asked whether he would like to be unblocked by having his IP address added to the website’s white list. If he follows that hypertext link, he is sent to the robot test page. If he answers the robot test question correctly, his IP address is automatically added to the white list. He doesn’t need to enter it or even know what it is. If he fails the test, he is told to click on the back button in his browser and try again. After he has passed the robot test, Nginx is commanded to reload its configuration file (PHP command: shell_exec(“sudo nginx -s reload”);), which causes it to immediately accept the new whitelist entry, and he is granted immediate access. He is then allowed to visit cheapskatesguide as often as he likes for as long as he continues to use the same IP address. If he switches IP addresses in the future, he has about a one in twenty chance of needing to pass the robot test again each time he switches IP addresses. My hope is that visitors who use proxies will only have to pass the test a few times a year. As the whitelist grows, I suppose that frequency may decrease. Of course, it will reach a non-zero equilibrium point that depends on the churn in the IP addresses being used by commercial web-hosting companies. In a few years, I may have a better idea of where that equilibrium point is.


You’re welcome.
I believe I found it originally via the “distribuverse”… specifically, ZeroNet.
Conky users?