Crogdor

Nettle tea is delicious.

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

Mostly nothing, except for Home Assistant, which seems to shit the bed every few months. My other services are Docker containers or Proxmox LXCs that just work.

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”…

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.