Sandboxing does nothing for social-engineering attacks, which is what many of the malicious snaps were designed for.
And the thing that makes the Snap Store uniquely bad is that there's no human review. Anyone can throw up a malicious snap, and there are very good odds that it'll get served there. Even the Flathub, a community-run project, has human reviews before new apps get published. Canonical, despite having money and resources that community projects don't, can't seem to be bothered to take basic steps to protect their users.
You are an absolute king for this! I assumed it was too niche to have it included, but if you're willing to consider bundling espanso in the Bluefin image, I can look into trying to solve for this.
Fair enough. I have some other GUI applications in a distrobox container.
I should have clarified that this program, in particular, does more than merely display content: it has to interact with my Wayland session to inject key strokes, which doesn't seem to work from a distrobox container from what I've seen.
I forget, to be honest. That was the first thing I tried but I did that weeks ago and have given up since then.
I want to say that it might have been the fact that I'd have to install and enable a GUI environment in the container, which would be, at best, odd, but at worst, buggy, since espanso would be interacting with the GUI in the container environment, rather than my host.
For sure, immutability is a point of the distro, but I have other reasons for using it. Namely, hardware-enablement and nice dev experience additions.
There's definitely value in immutability, but sometimes I wish I could temporarily disable it so I can do what I need to, while easily retaining those changes on updates.
The main program that I'm unable to install is espanso. It's an open source text-expansion program that has become invaluable to me and the way that I type.
I can build it from source, create an RPM for it, and even try layering it with rpm-ostree, but even then, I have the problem of missing libraries, like wxGTK*. Sure, I can technically manually acquire those libs and use ldconfig to configure them in a writable directory, but at that point, you're basically suffering through a dependency nightmare that isn't worth maintaining.
For stuff like that, I really wish that I could just scrap the immutability and simply install some more system-level packages like that more easily.
EDIT: I forgot to mention that the reason I can't simply layer the wxGTK* libs and the RPM manually:
espanso requires slightly different versions of the libs, and if I could simply symlink the newer versions that are available in the Silverblue repositories to the slightly older versions that espanso requires, I could probably get it to work.
I've been trying to create an AUR package for this, but can't figure out how to build more than just the server backend (based off of the Dockerfile). Is there a way to build it without wails? I can't get that to work in the PKGBUILD.
I like restic because everything seems to happen client-side, and the client pushes the encrypted backups to the server without having to install restic on the back end.
That said, I've never needed to restore my data with either backup solution, so I can't speak to the validity of the backups.
You can also use Ansible with just about anything, as long as you can connect to it over SSH or with a REST API. You don't have to use RHEL, specifically. I use it for """declarative""" package management on my Arch system.
Yeah. I've tried that, and I've found a couple of resources, but they never cover the "non-partisan" positions (a joke of a term). At least not in my area.
But something like you said that's as simple as "if you're progressive, here's a list of names. If you're a moderate, don't vote :)" would be great.
I vote in every primary and general, but are there any cheat sheets for voting on these offices? For stuff like House and Senate races, it's usually easy enough to find the candidate online and check their voting history and policy statements to see how much of a cretin they really are.
But for a lot of positions, like judges, school board, etc., you usually get a nameless face with no party affiliation and rarely anything turns up when you google them.
They legitimized the border "crisis" to average voters, and then demonstrated that Trump, who doesn't even currently hold office and didn't want it to pass (to make Biden look bad), was more capable of getting people to act the way that he wanted his party to.
That may have made the Republicans look petty to anyone that's paying attention, but it had the much more negative drawback of laundering a far-right narrative and showing that the other guy actually has more command over the fake "crisis" to average voters.
Democrats need to learn that capitulating to right-wing narratives, even if doing so disingenuously to own the repugs in some 4-D chess strategy, doesn't work.
Sandboxing does nothing for social-engineering attacks, which is what many of the malicious snaps were designed for.
And the thing that makes the Snap Store uniquely bad is that there's no human review. Anyone can throw up a malicious snap, and there are very good odds that it'll get served there. Even the Flathub, a community-run project, has human reviews before new apps get published. Canonical, despite having money and resources that community projects don't, can't seem to be bothered to take basic steps to protect their users.