Counterfeit

It’s spelled correctly right there in the title.

Because they get you places.

“Be careful what you choose. You may get it.” -Colin Powell

You didn’t happen to change an unprivileged container to privileged, or vice versa, after creating it, right? Doing so can break filesystem permissions, which could have resulted in something like this.

That’s how it works. I don’t think many people use the option.

If it helps, you could choose the keep and unmonitor option, and then once you’ve confirmed that it does indeed impact movies not on your lists (by unmonitoring them), you can disable the cleaning option (or choose a better option for you) and update all your movies back to Monitored.

Coming up with a simple formula is a big security risk. It makes your passwords easier to brute force, and with enough entropy, probably easy to guess as well.

And what happens if the password is breached? Do you change the formula? What happens if a site requires a password change? Even if the formula accounts for versioning/iterating, how do you remember which iteration you’re on?

Extra security with 2FA I agree with, but that’s not mutually exclusive to using a password manager.

And are password managers really single points of failure? These password managers can sync to multiple devices, so your data is generally safe. If someone gets your password manager password, that’s a problem, yes, but they’d need access to your device to view anything, as installing on another device requires a separate master key to set it all up (which should not be stored digitally anywhere).

There are two kinds of datacenter admins, those who aren’t using VMWare, and those who are migrating away from VMWare.

TIL it’s “prerogative”…

A garbage article citing garbage sources.

tl;dr: It’s a false positive. The headline makes it sound like an intentional classification, but that’s not the case. Also, they fixed the problem two days ago.

All the *arrs are in the same Github repo.

It’s not as relevant today as it used to be, that’s for sure. Originally it was to limit transcoding of 4K content (which used to be a lot harder), and also to avoid the HDR tone mapping issues with 4K content during transcoding, both of which are largely resolved with newer hardware and Plex software updates.

The only reason I keep them separated now is because most of the folks I share with can’t direct stream 4K content anyway, and so I only share out the 1080p libraries in Plex. It keeps bandwidth usage down and limits having to go to hardware transcoding, which can reduce quality and introduces startup delays. The library I use locally indexes both the 1080p and 4K content, so Plex will always prefer the 4K if it’s there.

If diskspace ever became an issue, I’d probably consider merging the libraries again.

You’re taking it too literally, and missing much of the nuance between philosophy of design and actual implementation details.

The movies app manages movies. That’s its one thing. No need to overcomplicate it. Unix ‘find’ for instance, finds files. That’s its one thing. ‘find’ also lets you filter the results, but that doesn’t change its purpose of finding files.

The fact that *arr apps don’t do things, or are bad at things, has nothing to do with the Unix philosophy. Were these apps combined into a monolith, the same issues would need to be addressed.

There is no right or wrong in a design philosophy. It’s all trade offs. I don’t know anyone who says Unix (or the metaverse) is successful because of a design philosophy. What matters is what you deliver.

I do wish I didn’t need to run a second Radarr instance to have both 1080p and 4K media.