You’re someone.

I don’t keep track of them. Jellyfin and Radarr, etc. keep track of them for me.

Isn’t that how it always goes. Everyone wants the end result, but nobody wants to do the work.

Why not cross post some of the content yourself?

Yes, I was agreeing with you. Although as I mentioned, it’s technically 100m, which is 328 feet and one inch. And the spec also allows up to 5m of patch cable on each end, which I don’t think I knew.

But that’s the spec target. Low-quality cable, physical damage, or environmental conditions like interference may reduce the actual max in practice. You might be able to push it with cat6 and up, but the spec still only says 100m.

CCA shouldn’t be used anywhere ever. It’s garbage cable for garbage people who will pinch a penny and end up spending ten times that in dealing with the issues and the eventual replacement.

But that depends on the card. And some gigabit devices won’t do 10Mb at all.

100m is the spec max. More than that, you need a powered repeater (i.e. baby switch). And you won’t get 100m if you have bad cables.

I once saw a run in a cruise terminal, out of the cruise ship, down the gangway, along the terminal hallway, and through two more little switches just sitting on the floor next to an outlet. Not sure why they needed that run, but that’s what they did and it worked.

This is my go-to for a first look. You might want to see if the CPUs also support special features like encoding/decoding acceleration, because doing stuff like that in hardware is much, much faster than doing it in software with regular instruction pipelines.

You can do anything with unsupervised physical access. The signal has to be decrypted at some point: https://en.wikipedia.org/wiki/Analog_hole

I have a cron script that just dumps it into my jellyfin library.

Some Google results suggest that Lidarr should be able to detect and import these automatically, but I doubt it works like you’d want it to. You can probably identify artists and add them through the API in the same script, then Lidarr should pick them up.

Just remember to use the nofail option so that it doesn’t halt the boot process if it’s not available.

I’d lean toward bad hardware.

Try stress testing the CPU and RAM. See if you can get it to happen more frequently. Also see if you can disable that CPU core, either in the BIOS or in the OS, to see if the problem goes away.

Those are probably your best options right now.

You could also write your own platform that does exactly what you want.

https://github.com/ianpatt/skse64/releases

Why not just update SKSE to match?

CMOS batteries last a lot longer than a year. Unless the system has been unplugged for a long time, they should be good for several years. I’m sure there’s actual data out there somewhere.

But yeah, a lot of people think “oh I’ll just put a UPS on it”. They don’t consider that unless you get a really big UPS, they’re only good for very short outages, seconds or minutes, to bridge the gap between the outage and your generator coming on (or the mains power coming back if it was just a flicker).

Also, the batteries in them need to be replaced every 3-5 years.

Neat. I think yt-dlp is still a very good option since you can use it locally and script it.

It’s so that someone can’t get a post to the front page and change it to something offensive.

I don’t know if that’s going to be a problem on Lemmy. Maybe in the future, if there are more users.

If you want the full fancy GitHub, they have an on-prem enterprise edition for $21/user/month. https://github.com/pricing

But if you don’t need all their bells and whistles, or the team doesn’t care about not having the GitHub interface, then the other suggestions are better.