Absolutely this. Relatively quick and clean, no messing with installation or reconfiguration. That is, assuming your data isn’t completely corrupted and the old drive doesn’t just outright fail during transfer… But if that happens you were screwed to begin with.

Dark thick beer can also work in place of cocoa, in my experience.

Compatibility is unlikely to be very different. The key is immutability (easy to update, hard to brick your system) and some baked in nice to haves for gaming like some specific drivers/patches and controller support out of the box.

If you’re gaming you might as well just jump on Bazzite if you’re already interested in Kinoite. Very similar base, but Bazzite has some extras Kinoite doesn’t and it makes a transition into an immutable distro easier.

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.

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

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!

Same boat as you. The HOA maintains a pathway in a wetlands reserve right behind the residential area and it costs less than $20/mo.

They don’t really care what you do besides the following: no farm animals/chickens, no structural changes to the homes without a licensed contractor performing the construction, shoot an email to the HOA if you’re going to replace your roof or repaint your house to keep SOME level of uniformity.

Mostly they don’t care. Hell, the CC&R’s and HOA incorporation docs literally say they won’t directly enforce things against you and leave it up to the neighbors to take you to court with the HOA docs/agreements as free ammo. So if you explicitly want to be a menace to your neighbors/piss people off or want to have the only bright ass neon pink home with custom additions in the entire neighborhood - probably not the place for you. Otherwise they’ve had no effect on myself or my neighbors whatsoever and the wetlands/park is really nice.

Why would I recommend Fileflows? It was a little more user friendly in my experience without requiring pulling in configurations from other sources. I know there are repos chalk full of Tdarr settings and configs, but for simple setups and DIY I preferred the Fileflows interface. The end result is basically the same, so pick your poison.

I might recommend fileflows over tdarr- but either way some kind of similar solution is almost mandatory with the grab bag of arbitrary encodings you find out there.

Software-wise, it seems that the relatively fast adoption of flatpaks and other containerized formats somewhat solves the typical dependency hell that was so common in Linux just a few years back (and to some extent still is an issue today depending on your distro and use case). The hardware support side is a little harder. That’s going to be up to vendors to play nice with the Kernel team and/or introduce reasonable userland software that doesn’t break the golden rule. Until Linux gets more market share the latter isn’t likely to happen. A nice side benefit of the emergence of immutable and/or atomic distros is that users can play around and try things with much lower risk of bricking their systems, so I’d also consider that a step closer in the “it just works” department.

Even with nvme drives which supposedly “don’t need” to use BFQ, I STILL always swap it since it maintains responsiveness across the system during heavy IO loads. I used to have similar full system freezes when downloading steam games which notoriously overload your IO in Linux. BFQ was the solution every single time.

Edit Try following the instructions detailed in this post to add a systemd rule to set the scheduler: https://stackoverflow.com/questions/1009577/selecting-a-linux-i-o-scheduler

The second answer that shows an actual rules.d file example has always worked for me. If using nvme or old school spinning rust you’ll need to change it up a bit. Instead of “noop” set it to “BFQ”.

Try swapping to BFQ io scheduler and see if that makes a difference.

I’m going to assume it’s not Universal Blue… But parts of your description reminded me of it.

I have personal experience with BTRFS and Windows. And that experience is that it’s roughly as stable/complete as NTFS is for Linux. 6 of one and a half dozen the other. I can’t recommend either situation for guaranteed stability long term between systems if one really needs to swap between the OS’s frequently while accessing all the same files.

I can vouch for Bazzite. Been running it on my desktop and laptop (both amd gpu’s) with virtually no issues or hiccups. The desktop is even dual boot, despite that not being advised.

Traefik is love. Traefik is life. How could you say “no” to that mascot!?