ShellMonkey

Between the election losses, his tariffs in seeming jeopardy, and now the sandwich hero rulling, you can bet Donnie’s gonna have an extra special meltdown over the weekend.

Depends a lot on budget, space, and electricity costs. Going to ‘overkill’ level once can save a lot of these issues down the line.

Mine started similarly, some small box with a couple drives that got up sized and then moved to another to add more…

Eventually I bought a used 2U box with 14 bays and set it up with a ZFS pool all made up of mirrored disk pairs and auto snapshots so it can have a drive fail without issue and go back 2 weeks if something gets oops deleted.

Downside, now the whole lab uses about 700 watts continually so the power bill is kinda nuts.

Well damn, that’s gotta be the most pristine warzone I’ve ever seen

Here I thought they were already an open book for the asking

Doge did what they where most suited for, taking the primary heat for a massive slash and purge program out of the gate under the guise of efficiency while Trump gets to claim credit for whatever his cult likes and deflect blame for those they hate.

Disney faces a wave of cancelations not the subscribers, people need to proof read their writing bots…

Way it’s written it sounds like they dropped a mess of shows, which they may have, but the article talks about the Kimmel response.

I think I can see where they’re going with it, but it is a bit hard to write out

Say I set up my favorite service in house, and said service has a client app. If I create my own DNS at home and point the client to the entry, and the service is running an encrypted connection with a self signed cert it can give the client app fits for being untrusted.

Compare that to putting NPM in front of the app, using it to get a LetsEncrypt cert using the DNS record option (no need to have LE reach the service publicly) and now you have a trusted cert signed by a public CA for the client app to connect to.

I actually do the same for a couple internal things that I want the local traffic secured because I don’t want creds to be sniffable on the wire, but they’re not public facing. I already have a domain for other public things so it doesn’t cost anything extra to do it this way.

I was probably using Emby already by then, had bought a lifetime license since it didn’t require bouncing things off and outside server like Plex did (or was it that Plex was a renewing subscription, I forget) , so it just stayed out of inertia.

I can’t say I’ve given Jellyfin a proper try (as in using it and the clients exclusively for a long period) but we have been using Emby for quite a while before I knew it existed.

If I’m not mistaken Jellyfin is actually a fork of Emby so they’re pretty similar, but one is a bit older.