I don’t really run much of any unverified ones myself anyway, though tbf the unverified proprietary wrappers on Flathub are at least somewhat more trustworthy than the AUR equivalents (at least it doesn’t get to run stuff as root during installation, like Arch packages (or any distro packages really) do), though in both cases you are giving them access to your $HOME so that’s something to be always considered.

And Flathub doesnt need to be the repo used. Fedora for example created its own repo so it could verify its own flatpaks in the same way as its other system repos.

I’m not really sure why Fedora Flatpaks still exists… I mean yes it sounds good as an idea (distro gets to ship sandboxed apps alongside conventional packages) but there’s still the upstream devs vs downstream packaging conflicts, and for new users it’s annoying at times because… reasons (the package you thought was coming from Flathub was actually pulled from the Fedora repo because it’s in there too, etc.), seems like effort duplication on top of the existing effort duplication that was/is downstream packaging but still.

Some distros do have their own flatpak repos as well but smaller than what Fedora is doing, https://appcenter.elementary.io/ for example (but a substantial of that stuff is primarily only available from there, though you can build it yourself), though again I’m not sure much of any other distros would want to implicate themselves with that because… all the reasons.

Flathub is a separate chain of packaging from the distro itself so there are legitimate reasons to avoid it if one is heavily paranoid though.

a lot of apps on the flathub website say “Unverified”

Those are usually either wrappers for proprietary stuff, for example the Chrome flatpak is unverified because it’s not from Google themselves but rather somebody grabbing the official deb/rpm and rebuilding it into a flatpak (this is also how a lot of e.g. AUR packages on Arch work, basically), or open source stuff for which the dev/packager simply didn’t care enough to do the verification stuff that Flathub wants you to do (doesn’t actually seem that hard, but one might simply not have been aware of it or something).

Don’t recall people particularly complaining about the unverified badges before Mint started hiding unverified flatpaks by default, though; suddenly after that “everybody” started noticing them.

curl -L matchctl.sh | sudo bash

yeah screw that, I’m not piping curl into bash and root bash at that

I mean I have to wipe out my ~ relatively frequently on some machines at times but that’s for “actual” “reasons”, LLM hallucinations not involved

Ok, now stop doing whatever it is that they’re doing to the cursor layer that makes it feel like garbage (wlroots is especially bad, KDE less so but not as good as either Xorg or Windows, GNOME too but has other cursor issues so…) and then I’ll finally consider daily driving any of this stuff

will try again with a photodiode instead, since it’s known to be a valid way to measure stuff like this, and it seems precise enough at that

if it isn’t this, then I’ll probably have to dig into libinput or something

You gotta do the measurements. It’s probably not even that hard, all you need is a USB mouse emulator (any microcontroller with USB peripheral support can do this and there are tons of examples) and a photodiode.

will absolutely do this, the microcontroller and mouse emulation part is solved for me already so I just need to get an appropriate photodiode and… profit

deleted by creator