Dran

Generally the lifecycle with this sort of thing is old_thing becomes an alias to new_thing, and eventually old_thing gets dropped as an alias down the line.

It’s still decent advice to learn dnf native calls and to update scripts using yum to those native calls.

Okay, I’m hooked, I have to know the non-clickbait story

It doesn’t need csam data for training, it just needs to know what a boob looks like, and what a child looks like. I run some sdxl-based models at home and I’ve observed it can be difficult to avoid more often than you’d think. There are keywords in porn that blend the lines across datasets (“teen”, “petite”, “young”, “small” etc). The word “girl” in particular I’ve found that if you add that to basically any porn prompt gives you a small chance of inadvertently creating the undesirable. You have to be really careful and use words like “woman”, “adult”, etc instead to convince your image model not to make things that look like children. If you’ve ever wondered why internet-based porn generators are on super heavy guardrails, this is why.

That is only true when you use their “home” feature. It puts the entire thing behind oauth because it has to do so in order to restrict libraries/content to non-full users. Think about the instance where you have a thirteen-year-old kid and you want to restrict them to pg13 and under. Without forcing oauth on local connections they could just sign out and watch all your star trek porn parodies or whatever you don’t want them to see. If you remove the server from a “plex home”, it disables the oauth workflow for local connections as expected.

Don’t get me wrong, I’m not really happy with a lot of their new sharing/social features, and their recommendations on the homepage can fuck right off, but I do think it’s important to be accurate when criticizing. Requiring oauth on local vlans when plex home is enabled is the objectively correct solution.