Oh nice! I just use Lutris, but options are always good.

That work has already started with Fediseer. It's not automatic, but it's really easy, which is probably the best we'll get for a while.

I'm sorry I didn't call out every exception to the rule. Obviously, if you do illegal things on my instance, I will care. I kind of thought that was a given, to be honest.

My fault, lol. I brought it to one of the maintainers' attention a couple days ago by asking a question about it.

Although I'll definitely say it's nice not having to go into the launch properties of every single game to add the gamemoderun command.

I'm taking my conversation-level Japanese courses this year and have been looking to land a dev job in Japan. From the sound of it, I'd like working for Pocket Pair a lot. But then again, most companies make their employment sound fantastic...

Only if you play CoD, Fortnite, or Destiny 2. If you're technically inclined and don't mind working around some issues, gaming on Linux has come a long way and can be used for pretty much anything else. I used to dual-boot Windows for games, then I went to booting Windows in a VM and gaming with a spare, passed-through GPU. But I haven't booted my VM in months, and I play lots of games.

The Arch wiki has you covered.

Even better than F-Droid is Obtainium. Get apps right from the repo release page, no waiting for F-Droid to recompile.

So silly. Genetics can make it harder to lose weight, but not impossible.

I'm related to several people diagnosed with hypothyroidism, but none of them are obese because they know the condition makes weight loss hard and actively work harder because of that. The biggest one is what I'd called "chubby", and that's more likely because her thyroid numbers are in flux at the moment, and she's currently working with her doctors on that.

I've shifted towards using Obtainium for most of my open source apps and get them straight from the repo release page. I didn't have any real problem with F-Droid, it's just really slow to release updates since they build everything themselves (which is cool, but again, slow).

Snaps are disliked because the store is closed-source and run by Canonical. Snaps are also disliked simply because Canonical is pushing them so hard, forcibly replacing native packages that exist and work fine. For example, there was a debacle a while back where running apt install firefox still installed the Snap version instead of the native version.

Flatpaks are disliked because they sometimes struggle to integrate into a system well. For example, Discord Rich Presence doesn't work for the Flatpak version of Discord unless the thing you want Discord to detect is also a Flatpak, and even that detection is shaky.

Snaps and Flatpaks are both disliked because they contain frameworks and runtimes that some users consider bloat.

To further explain, when you use a native package, it and its dependencies get installed on your system. If any other package in the future requires one of those dependencies, awesome, it's already there. But for Flatpaks and Snaps, each app has to bundle its own dependencies. Sometimes they can be shared with other Flatpaks/Snaps, depending on the dependency, but they still require at least a little extra storage space.

There are probably details I'm forgetting, but those are the main arguments. My advice is if you're happy with the way your system is running, don't worry about it. My personal preference is Flatpak first, native second, Snap never. I don't have anything against native packages, but some software I use is exclusively distributed as Flatpak, so I switched most things over for consolidation.

I know Republicans generally vote against their own interests, but Abbott pushing back against stuff like this and the tort law that got him his money in the first place will always be wild to me.