So, ChatGPT can’t match any function of a Casio wristwatch. I’m concerned that when it can, it will consume the power of microwaving a turkey just to tell a user what time it is.

We need to lock him in a cell then flood it with shit.

GrapheneOS and LineageOS don’t ship with any Google services at all, so Google’s policies shouldn’t affect them.

I’ve found the biggest bottleneck is bugs. If you catch a bug during development, it takes the least time to fix.

Catch a bug during PR, you need to fix the code, and the PR needs to happen again.

Catch a bug in QA, and you need to fix the code, do another PR, and get it tested again.

This pattern goes right through UAT, and god help you when a bug makes it to Prod.

There is nothing more time consuming than code that was written quickly.

It’s not AI. I reckon every kid in Melbourne has been there on a school trip.

That’s Soverign Hill, Ballarat (Australia). Awesome little place. Was the local VLine station packed because trains are free? I did Bendigo today and boy was it busy. It’s great that there was almost no cars in town.

I just peel it under running cold water. Fast and easy.

That’s about the same as Australia. It’s $2.50/L and AUD is typically close to CAD.

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.

Windows users can’t even install Windows.

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.

It went from INI to JSON real quick.

You can’t copy and paste into a GUI, and it’s painful to help people to use them.