Ahh. That’s usually among the red stuff in dmesg. I glad to hear you solved it, but a failing hard drive is a pricey thing to endure these days.

Ahh, the ol’ “slippery slope” logical fallacy. You can dismiss statements like those. You don’t even need to debate it.

This is no different to the meta pixel localhost listener exploit.

Windows users can’t even install Windows.

This is absurd. They know we can go all the way to the root servers, don’t they?

I have a theory: Windows users don’t have the skill to fix their broken PCs, and now they don’t have the money to replace them.

Just start listening to dubstep and you’ll stop noticing 😆.

Maybe run lm-sensors and make sure the CPU/GPU isn’t being thermothrottled? I’d usually look at dmesg and look for red stuff. Any hardware issues are usually pretty obvious.

Try other apps. If you youtube or VLC behaves the same, the problem may be outside of jellyfin. If not, it narrows it down.

If could even be the server not being able to transcode in realtime. Try watching a file known to already be in a suitable format. It should direct stream and be much less load on the server. I’ve seen server encode CPU saturation and it does kinda look the same as client decode stutter. If it’s the server, you’ll probably see the same stutter from another device such as a phone.

There’s a “minimal” install that gives you a bare desktop. The only thing I would consider bloatware is snapd.

Agreed. It’s an uphill optimization battle. We’re now in a world where you need 6GB RAM to chat on Discord while scrolling Facebook.

Ubuntu and its apps (particularly Firefox) are incredibly efficient and respects your hardware resources. I can write a web page with a 5MB RAM footprint. It’s when you open the New York Times that your swapfile gets face-slapped.

Funnily enough, an Ubuntu server will run on a half-eaten potato. I’ve got 16GB in mine, and I’m running servers for LAMP (Nextcloud and Wordpress), NTP, Samba, Mail, Jellyfin, tor, XMPP, CUPS and a few other things. It typically uses around 2GB at idle.

It really is a statement divorced from reality.

“Countering” is a 50% improvement at best. Your initial probability of being shot correlates with the number of other people with guns. Ideally zero.

They’re keeping their options open in case they want to switch sides halfway through the war.

Everything costs money when you run a business. You need to consider all of those things when setting a price. Cash has more overhead, so a surcharge for another payment method makes no sense.

TL;DR: 1st October. No more shitty surcharges.