AMD with ray tracing isn't great. Not as bad as it used to be, but pretty lackluster overall compared to Nvidia (and to a lesser extent Intel's GPU offerings). Linux ray tracing via Proton is also not as optimized at present, so that can take something "passable" in windows and make it unplayable on an AMD card in Linux. If you get something overkill for the resolution you're playing at that can somewhat make up the difference.

If you're doing 1080p the 6600 is pretty solid. Or 7600, really. It CAN do higher resolutions, but then you'd need to start doing FSR scaling or drop settings to keep things smooth/consistent.

I'm just here to say Bazzite all the way. No clue what that poster meant by breaking issues or problems with rollback... Bazzite is literally designed to be the antithesis of both. The ONLY time I've had a problem with it was rebasing my laptop between Silverblue and Bazzite. Technically allowed, but I wouldn't advise it as that did cause me stability problems. I'd blame Silverblue more than Bazzite in that case, however. A clean Bazzite install has been solid ever since.

You seem to be arguing it's all about the implementation of the phoning home itself- I'm arguing that running the entire executable/binary through a virtual environment likely has far more drastic performance implications than a phone home, regardless of frequency. It probably IS mostly an implementation problem, but I'm more inclined to believe that the implementation of the Denuvo virtual environment is at fault, not just a server call and response delay. **EDIT: Apologies, forgot to include a link- see HERE. Looks like a substantial/measurable difference. Not massive, as measured here, but certainly enough that if your hardware is just barely able to run a game it could easily make or break the entire experience.

Regarding performance implications: I believe Denuvo DRM runs through a type of virtual machine environment. While this theoretically should be relatively transparent, there are definitely documented instances of it negatively impacting performance, sometimes severely. Maybe the VM it runs in is just bad with certain instructions/calls on certain CPU's or api's, hard to tell for sure. But it's not nothing.

There's an old article on the Arch wiki I used to use HERE. For simplicity I'd just always use section 2.2. Hasn't ever steered me wrong, but I'm also under no illusions that no digital data is sacred. And if it IS sacred, then it's already backed up under the 3-2-1 approach. Just make sure you know which device is which so you don't mix up "if" and "of". There's probably significantly more user friendly ways of doing it, but I guess I'm old now so I'm stuck in my ways.

Get a same sized drive (or larger) and just dd it? I used to do that all the time, even to Windows installs, if I knew a drive was starting to become unreliable. I'd advise mounting the original/donor drive as read-only to mitigate any potential data losses while transferring. But dd makes a perfect bit for bit copy of any partitions, drives, etc that you feed it. Just don't get the inputs/outputs backwards! And always remember: dd stands for "disk destroyer" because if you get it wrong, bye-bye data.

Self hosting Mealie could be a great option to take things into your own hands.

To be more clear I was more focused on the not wanting a car that needs software updates part of the argument, less so the means of delivery. Obviously, having an always on connection absolutely sucks and I'd personally be super down with just pushing an update via a USB drive or whatever like you can a BIOS update. But a lot of manufacturers have it set up so that you have to either pay a dealership to plug in the USB for some arbitrary reason, or demand the always on connection to do it. In a utopia of software development where there are no critical bugs, we would all prefer a car that doesn't need updates. I didn't mean to imply that I was arguing in favor of remote connection by manufacturers, and it's absolutely my bad in not wording it properly.

On the flip side: if a car stereo has a known firmware issue causing problems with say Bluetooth connection, I DO want the manufacturer to actually provide an easy means of fixing/updating the borked software. Better that the system was properly tested and feature complete to begin with- but I'm not delusional enough to believe we can truly have nice things.

Possibly dumb question: why not use an Authentik outpost with a reverse proxy to enforce SSO? It wouldn't be "baked in" so to speak, but it would be fully OIDC and as long as you're just running it through a web browser. Biggest downside is you'd need 2 logins (one for the outpost and one for the app). I'd assume the sso is specifically for the extra security though, so that shouldn't be a problem outside of it being a little hassle.

Remnant 2. Gotta finish Cyberpunk 2077 (again) first though. The damn DLC adding extra achievements has thrown everything off!

For what it's worth- I've used them plenty and it's always appeared to be legitimate. They don't "stock" every game out there, but they do have most things and they do usually end up being 3-5% cheaper than steam unless steam is having a sale.

Oh baby, time to proselytize the masses of Lemmy and introduce a whole new set of suckers to "Fido". It's zombies with big Fallout vibes and is unironically one of the best C to B tier movies I've ever seen. It's the kind of movie where it looks like everyone involved was just having fun with it, ya know? Check it out and make sure to let me know what you think!

Both glowing portions are natural gas pipes. Perhaps it's somehow ignited inside the pipes and is super heating them but also somehow NOT travelling outside the two glowing sections and burning the house down???

*ahem Subtle Spell has entered the chat. Cast any spell that doesn't require a line of sight target and that doesn't require material components or otherwise rely on an "attack" or similar action. Like say Guardian Of Nature. Or, if you want to get REALLY pedantic: Dimension Door.

Adding repos can just be done inside a Toolbox, or even as Overlays. Grub can also be edited and changes applied to immutable OS's like Bazzite/Kinoite. I'd definitely say give it a shot on a non-daily driver machine and see how you like it. Having the option to mess with the underpinnings can be nice- but not having to has a lot of value as well.

I know, right? It's so hard to "really" mess something up and Toolboxes are very cool for things not served by Flatpaks or Overlays.

Regarding your not wanting to go with an immutable distro: what configs are you thinking you'll need to mess with that makes an immutable distro a bad idea exactly? I was previously on the fence about it as well but Bazzite has absolutely served my needs and requires way less fiddling than my previous Nobara install did after major updates. I have yet to find any day to day configurations that I haven't been able to overcome with OSTree overlaying. Aside from being immutable, Bazzite literally checks every other box you've got listed.

I believe it's more a "the PS3 CPU architecture was an absolute nightmare and emulating it is difficult/slow" more than it had anything to do with the graphics rendering portion- which is typically where phones would have made the most substantial advancements. There are specific instruction sets that need to be supported by any CPU emulating PS3 to run anywhere near native speed... And I don't believe much work has been done for ARM cpu's to support the needed instructions in mobile devices.