Dictionaries are tough, I know.

And it runs fine in a VM.

I have 3 external DVD drives - VM’s were the only way to use all 3 on a single machine. Really reduces rip times when I have a stack of discs.

The irony of that song, nothing in it is ironic.

Roast the bones.

I wouldn’t use cruciform veggies in stock - they’re already a gas engine for humans, who knows what they do in stock (my guess is make it bitter).

Start simple - my chicken stock is little more than just a chicken carcass in water. If I have some onions or carrots, I’ll throw that in, maybe a bay leaf. It comes out nice and brownish, concentrated enough that I usually have to thin it with water (I use a pressure cooker or instant pot).

That took me too damn long to get

Fine, have my upvote

The only concern I see here is the external drive. My experience has been that powered off drives fail more often than constantly-on drives. So my external drives are always powered on, I just run a replication script to them on a schedule.

But you do have good coverage, so that’s a small risk.

For stuff like movies I simply use replication as my backup.

Since I share media with fruends/family, I act as the central repository and replicate to them on a schedule (Mom on Monday, Friend 1 on Tuesday, etc), so I have a few days to catch an error. It’s not perfect but I check those replication logs weekly.

I also have 2 local replicas of media, so I’m pretty safe.

In the defense of end users, they got stuff to do and can’t be bothered to take the time which will make no obvious difference to what they need to do.

The average person can’t even describe how a toaster works, let alone anything even slightly more complicated.

And these users have skillets skill sets in other areas - I don’t expect an accountant to know how a computer works, any more than they expect me to understand accountancy or finance.

You’re missing the point - he’s elevating cli above all else, which you don’t have on TV or mobile.

Yes, I know there are media clients, I’ve used them all. And that screenshot is hideous - compare it to Jellyfin on mobile, which looks just like Netflix used to.

Besides, he’s not doing anything different than running a “server stack” (which isn’t accurate, he’s still running a server, the device hosting the media services, even if they’re native to the OS).

Xerox Parc didn’t invest millions in the 60’s and 70’s because CLI was so great.

We don’t use CLI on our microwaves, toasters ovens, tv’s clocks, lights, etc, for a reason.

So, let me get this straight - you’re saying using command line to play video instead of a gui?

Tell me, how does one do this on a TV? On an iPad? Phone?

Your excitement for command line belies an experience of nothing but GUI, so it’s something of a novelty to use command line.

Dude, get ahold of yourself. I probably wrote more command line stuff before you were born than you’ve ever thought of - I’m not going backwards.

(As a clue, wrote my first Fortran program before PC’s were even a thought at IBM).

Fuck cli except for managing systems. Even then quite often gui is faster by orders of magnitude, mostly to kickoff scripts to do what I need. GUI was a godsend, and Xerox Parc’s efforts created a common GUI language for us, thankfully was embraced. I refuse to go backwards.

And forcibly teach non-technical people to use CLI?

You are exactly the type of person that Saturday Night Live lampooned decades ago.

W… T… FUCK?

Preach fellow Xer!

Remember Cash for Clunkers?

This is yet another reason why it was pushed. Mid-late 90’s/early 2000 cars were too reliable/maintainable without any means to “improve” their data reporting capability.

Push people to buy new cars and increase data collection: win/win.

Agreed.

Unfortunately people in government saw the cost effectiveness of concrete vs wood and glass for things like a phone box.

Also, fuck brutalism.

You can’t fool me, these are the early shots from Californication.

Hahaha, fine dammit, have my upvote

Exactly, keeping components separated, especially the router.

Hardware routers “cost money because they save money” (Sorry, couldn’t resist that movie quote). A purpose-built router will just run and run. I have 20 year old consumer routers that still “just work”. Granted, they don’t have much in the way of capability, but they do provide a stable gateway.

I then use two separate mesh network tools, on multiple systems. The likelihood of both of those failing simultaneously is low. But I still have a single failure point in the router, which I accept - I’ve only had a couple outright fail over 25 years, so I figure it’s a low risk.

Separate devices provide reliability and supportability.

If your all-in-one device has issues, you can’t remote in to maintain it.

Take a look at what enterprises do: redundant external interfaces, redundant services internally. You don’t necessarily need all this, but it’s worth considering "how do I ensure uptime and enable supportability and reliability? ".

Also, we always ask “what happens if the lone SME (Subject Matter Expert) is hit by a bus?” (You are that Lone SME).

To be fair, the pro plan is for the non-local stuff, which is at least understandable as domains and resolution services are non-free.

Also ongoing development takes resources. Seems like a reasonable approach.

I say this as someone who absolutely despises subscriptions.

Put it in a VM using any of the current free virtualization products: 86Box, VMware Workstation, etc.