jerb

No, just the FSR2 demo application, which suffered from poor performance regardless of whether or not FSR2 is on.

This is still fully possible on Immutable distros (which is why the name is misleading, but unfortunately is what stuck- “image-based” is a better description) and uBlue has a mechanism for it- since they’re delivered using OCI containers, it’s trivial to fork or derive from the project and add, remove or tweak whatever you need. There’s also BlueBuild which is YAML but that’s a third party project.

For what it’s worth, that bit about Patreon isn’t true. There were fixed builds before release, but they were third party ones unaffiliated with the Yuzu devs.

Wasn’t aware they were integrating docker-compose, that’s the perfect solution. I got so fed up with TrueCharts that I’ve been considering nuking my NAS and reinstalling OMV or something similar, but I guess I’ll wait it out and see what happens.

Seconding this. TrueCharts has been an absolute pain and I would not wish it on my worst enemy.

Many artists I like were signed with a now defunct record label called Tympanik Audio. Whoever got the rights to the name after the label went under stopped paying their Spotify license fees, and a large chunk of my Spotify library vanished overnight. While the albums still exist on Bandcamp, the money probably gets thrown into the void now.

Never again. The only way I can ensure my music is accessible tomorrow is to have my own copy. I buy on Bandcamp where I can, or will buy physical and rip it if I really like the album. Everything else gets ripped from Deezer automatically because there’s no guarantee anything on those platforms will always be there.

There’s already a similar project for Minecraft- https://mcpelauncher.readthedocs.io/en/latest/

Just the kernel module, which still interacts with the proprietary driver.

That app just looks like reskinned KDE Connect.

I suspect it’s intended to be “ground-up rewrite in a better engine with more content” sort of like Isaac’s transition from Flash to its own bespoke C++ engine.

That’s a user from Mastodon. Lemmy is part of the fediverse so any ActivityPub capable server can see Lemmy posts (it just might be formatted a bit differently). From their end they’re replying to a toot.

A microscope is explicitly required IMO. I would definitely not attempt the mod without one.

Yes, newer switches need a modchip. They’re dirt cheap these days but require microsoldering- not for the faint of heart, ESPECIALLY for the Lite and OLED switches.

Look into MakeMKV. It’s “free” while in beta (in practice you need to input a new license key from their forums occasionally, so inconvenient unless you buy a real license) and can rip Blu-Rays with no issue. For ripping 4K, though, you’ll need a drive that supports LibreDrive which bypasses all of the drive’s built-in DRM. I personally use an LG BU40N in a Vantec external enclosure.

You’ll be disappointed if you’re looking for “more DOOM 2016”- Eternal is a different beast entirely. Feels much more like a realtime first person puzzle game than a mindless arena shooter. Knowing enemy weak points and what guns do the most damage to that specific enemy + micromanaging ammo, health and armor is a BIG part of Eternal’s gameplay loop. It’s very good, but it’s quite far removed from 2016 in terms of gameplay.

https://github.com/htrefil/rkvm

Not particularly, the workflow on your Arch system will be the same as any other distro, that’s the nice thing about Distrobox.

I would highly recommend looking into the distrobox-assemble command, though: it lets you declaratively build distroboxes with the packages and config you need on them. I have a personal box which operates as my primary terminal that’s automatically destroyed and recreated on every boot. This way, the packages I always use in a terminal are available, and I can add something I need temporarily with no issue without worrying about forgetting about that package being there down the line and causing some weird update failure or general bloat.

It does take some adjusting- the pitfalls you’d encounter with Distrobox on Universal Blue are the same as Distrobox on any other distro, so first I’d say to try moving your workflow to Flatpak and Distrobox on your current system or a VM and see how it works out. Generally Flatpak is preferred to a rootless Distrobox which is preferred to a rootful one, but sometimes there’s not a Flatpak for something (especially command line tools) and you need access to hardware or system level stuff that only a rootful one can do properly.

That’s because of a difference on protocol (iMessage vs SMS). This wouldn’t matter if they chose to support RCS which is effectively the Android iMessage equivalent and is an open standard (on paper, not necessarily in practice) but that will never happen.

I think there’s still value in it from being a DE-agnostic GUI solution, for what it’s worth.