Going by the article you linked, game cloning runs into problems, including the EULA and potentially for copying information. Copyright cases also consider whether the potentially infringing text replaces the original in the market, which is another problem for cloning games.

Training models, as a concept, isn’t necessarily IP theft, but in practice has involved quite a bit of IP theft. Anthropic itself has come under fire for pirating books and scraping Reddit after agreeing not to scrape Reddit.

Ah, it’s ok to steal IP to build models, but not to use those models to steal IP. Got it.

I haven’t used Plex in a while, but I presume it would go similarly to my Jellyfin migration this year.

I pulled out a 10 year old laptop from my pile of scrap, installed a light-weight Linux server that can run containers, and I’ve been running LinuxServer.io’s Jellyfin container on it. Updates are pretty easy and I don’t have to worry about cluttering the host box’s packages with dependencies that may or may not conflict with the other things I run in it.

If you have the time to figure out how to run apps in containers, I highly recommend doing so. There’s a lot of documentation for Docker, and Docker Compose files make managing the containers pretty easy.

You’re delving into the unpleasant realm of risk assessment. How likely is the app going to be targeted by a threat actor, and how badly could they use it to damage your data or system?

If it’s a public facing service, I’d immediately check if I have alternative applications I could migrate too. Any hold an outsider gets through the public facing app could be used to pivot further into my network.

If it’s something that doesn’t interact with the network at all, then I wouldn’t worry nearly as much, but might look for alternatives any just because I know this isn’t going to get improved at all. Somewhere in the middle, you need to decide how much risk you can accept.

Yeah, but the it’s a good rule anyway, for some of the same reasons as the “Don’t put it in an email if you wouldn’t want it read aloud in a deposition” rule.

Aren’t they? Changing a legacy app can take years to do the needed research, approval, procurement, and implementation. “Because my IT guy doesn’t like Windows” is a terrible reason to undergo that process.

The same with retraining users on a whole new OS. You’ll spend hours over the course of months answering “where did my C:\ drive go?”. That’s a lot of time you’ll never get back.

Active Directory provides a lot of tools that are familiar to senior techs and easy enough for junior techs to figure out. I might prefer how Salt Stack works but I don’t have time to train dozens of fellow techs.

Linux is cool for a number of reasons, but it isn’t a magic easy button and a wise admin doesn’t swap out fundamental parts of his tech stack without careful consideration.