“Mississippi experiences explosive growth” hell yeah good good for you Mississippi finally some good news out of that state!

“…in maternal syphilis” ah. There it is.

If you have any vc1 content why not try it and see. And if you don’t have any vc1 content, why worry?

How do they even?? They can’t know the difference in time between the humans key input and the computer’s receipt of it, since they can’t possibly know the exact millisecond the human input was made…?

The reported article really sounds like a misreading of a more technical document

Tangential, but I remember the days of RGB notification LEDs so fondly too

A lot of times the larger diameter wheels are actually a fair bit weaker than smaller ones, especially when the larger ones include rubber coating etc.

They sure roll over a tiny speck of dust better though

Yeah I absolutely love this. Would love more detail on a technical level (what challenges they faced trying to compile for steam deck) but still awesome to hear

Since this is the Linux gaming sub, you would kinda be expected to notice the Proton in the GPU driver field in the OP. It’s also kinda safe to assume someone posting in Linux gaming is talking about, well, Linux gaming.

“Breaks all compatibility [with emby]” was my interpretation of that. Not a huge deal either way but I’d definitely have been calling it 11 with this DB rework myself

Basically, yes. Forces plugins not to use potentially database-engine-specific SQL so that server admins don’t have to select their DB based on plugins for jellyfin being compatible.

I kinda agree here. https://jellyfin.org/docs/general/contributing/release-procedure/

Claims to follow semantic versioning, explicitly mentioning changes to plugin APIs as reasoning for a new major version.

God I wish megacorps would stop being morons with NDA nonsense and just open up the possibilities for open source devs to actually use the hardware that’s out there

God damn why’s the world so shit

“RTFM” My irritation is that most recipes make a huge amount of assumptions - at least as many as code that assumes a certain version of library. You can get recipes that say things as vague as “prepare the chicken” and aren’t at all clear what they mean, unless you’ve seen someone do it first, but it’s published in a book like you should just know. I hate that. I also frequently see quantities like “1 can” which just drives me insane as though that’s a standard unit.

There’s also plenty of cooking specific jargon, so densely packed that beginners might spend the majority of the recipe looking up what the terms mean. “Chop” parsley - how finely? “Mix the ingredients” how long? What the fuck is Golden Brown actually?

I was going to ask about resolution as I haven’t tested it myself. Considering my screen is 32:9 (7160x3840) I’d be pretty disappointed with a 1920x540 recording

Thanks, don’t mind if I do

This has been the case since SATA revision 3.3, released Feb 2016. So while I may have exaggerated with “ancient”, a brand new PSU certainly shouldn’t still be feeding 3.3v to that pin.

Likely changing the “active” flag or boot stuff, but as the other commenter says, if you aren’t 100% confident, disconnect the scsi

I have done this with dozens of drives and have never had to do any pin blocking. You only need to do that if you’re using an absolutely ancient sata power cable that doesn’t know about the spinup pin change

VP9 has pretty wide support, probably due to the Google (and YouTube) backing. I sincerely doubt devices will phase out any codecs, especially not VP9.

AMD video cards have supported hardware decoding of VP9 since vcn1.0 - well before they had support for decoding AV1

AV1 and VP9 are likely going to be your highest efficiency “free” codecs. AV1 is the way to go if you mean free as in free open source. It’s not very likely to be implemented in many TVs or set-top-boxes, but VLC/ffmpeg will be able to decode any of these. Webm uses vp8 or VP9 which are “free”(made by Google) but it’s just more specific settings for sharing online/viewing in browser.

H264/H265 has license fees for non-free software and hardware, but they will be your most widely supported option. H265 is approximately twice as efficient as h264 (meaning you can get the same quality of encode from half the file size).

Regardless of preset I think you can get handbrake to encode something reasonable from any of these codecs. Especially with DVD video you’ll be able to crank through videos with modern high efficiency codecs