wildmXranat

Nice. This is excessively large so it probably took a while to curate. Well done

Someone should've coined this disaster as "QuattroFail" to give it a little panache and international mystery

So much fluff and marketing from every group.

Just give us the damn code to verify things are working since so many have to use stopgap solutions and want to verify them

Yet it was leaked and I can't see a single "Here's this piece of code you can run to validate the fix actually works"

It's like slop for infosec markters

Did anyone find a reputable source for code which can be used to validate fixes ?

"valuations" are irrational and make dot com _valuations_ look like a miniature caricatures

When that happens, the chips stocks will have tanked back to sane levels and the doom posting will be about that. That will put us in the 2001 era of post dot com bubble, and the following few years will show us who the winner are

We went from "Review any services and their interaction without local system and network" to "Defending local and remote logic created on the fly to mangle the local file system, and why that's a good thing" ...

That's not a productivity boost. That's a rapid increase in cognitive tax you're offloading for later and as you get backlogged in reviewing it, you lose more control over what it does...

Yes, if this selected piece is the best that was available to be used as a showcase, it's immediately off putting in distortion and mangling of pronunciation.

Nice. When you're done, feel to share in the selfhosted sub on Reddit. There's an ever growing Jellyfin community growing and ex-Plesk users on there.

Interesting. No idea how it works, but I'm willing to try this out for a quick test as long as I can self host it

I imagine there's numerous ways to protect against it and protection should've been added by whoever decided on this optimization. In data layer, create some kind of view which never returns more than 200 rows from base table(s). In code, use some kind of iterator. I'm not a Rust guy, just a C defensive practices type of dude, but maybe they just missed a biggie during a code review.

My first question when faced with an unknown error is "What was the last change and when was it promoted?"

Hold up ,- when I used a C or similar language for accessing a database and wanted to clamp down on memory usage to deterministically control how much I want to allocated, I would explicitly limit the number of rows in the query.

There never was an unbound "select all rows from some table" without a "fetch first N rows only" or "limit N"

If you knew that this design is rigid, why not leverage the query to actually do it ?

What am I missing ?