Prioritize better matches on search PR #15983, by @Shadowghost

This is a big one for me, I can now search for “IT” and actually get results!

If $'s was my only consideration, I’d pirate the game.
If my valid options are paying $25 to Valve, installing the Epic malware or dealing with pirate sites, I’m sending money to Valve.

They failed the golden rule, it was right there the whole time.

These are pretty calm messages to an Australian and Garry is British, so culture checks out.

// What the fuck
// Fuck dynamic compiling.
// what the fuck is this shit
// What the fuck, why isnt this a method

Should this by the by commentary be there?
Not really.
But as a programmer, I understand each and every time I see something like:

// Urgh this is so dirty, Invalidate() and Refresh() do nothing.
tButt.AutoSize = false;
tButt.Width = maxWidth;
tButt.Height = maxHeight;
tButt.AutoSize = true;

As you can see, I too have made a “least bad” choice for pragmatic reasons.

I take no pride in correcting you.

Actually, if you hit those 3 dots on the top right and select “All Permissions”, you’ll see there’s a whole host of things it demands that you can’t opt out of.

When you’re personally confident that you won’t be rolling back.
I tend to keep the previous backup as each version is successfully updated.

ie I was running 10.10.7, I still had 10.10.6 sitting there, but I deleted it after successfully upgrading to 10.11.0.

Several people have experienced this error: https://github.com/jellyfin/jellyfin/issues/15058

It appears to be when the config of jellyfin lists the cache and the transcode in the same path (or if the transcode directory is within the cache directory).
My understanding is that as the image starts, it writes these hidden dot files (.jellyfin-cache and .jellyfin-transcode) and checks for their existence before it will continue with the next load step.
Hence why they keep coming back when you delete them.
Complicating this is that if you are running jellyfin inside docker, the external mounts can confuse the internal mounts.
(ie INSIDE the docker image you have them in /cache and /transcode, but OUTSIDE you have transcode and cache both mounted in /home/untouchedwagons/jellyfinstuff/)

Within your running instance of 10.11.0, make sure the configuration for cache and transcode are in complete different directories (ie /cache and /config/transcoding-temp/), then shutdown the server (to save that configuration change).

If that’s not clear, a little more info will be useful for diagnosing this.

If you can log into the site, it’s done.
If you try to access the site and you get a “startup log” page, it’s still ongoing (and it will show you there what it’s doing).
https://jellyfin.org/posts/jellyfin-release-10.11.0/#startup-ui-and-log-viewer

They are removing the hard to use old version that was inherited from the original Emby code.
For years now, the developers have been advocating the use of a reverse proxy to provide TLS.

Yes, the update should only affect the Jellyfin specific things (databases, configs, metadata). Your media itself is only deleted/modified under very limited and specific circumstances, and you can (and many people do) choose to mount the media read only.

I think the feel from the Devs is that there isn’t enough new functionality to justify the major version bump, this primarily being a reimplementation of existing features.

BUT, I agree with you, it should definitely be V11 under the semantic versioning scheme.
Whilst there is a migration path here, the database changes under the hood alone are likely to break backwards compatibility with all plugins (with in-house plugins being upgraded in sync).
Such breakage is kind of the defining characteristic of a MAJOR version.

This is not a remote code exploit that makes you vulnerable simply because 7zip is installed, which is the implication of the headline.
So this is a linkbait headline, divorced from the reality of the situation.
Which is the bit I take issue with.

The article itself describes not only the actual problem, but the broader problem of this being a known fixed problem which won’t be automatically addressed for most windows users.

Side note, winget is not bad as far as centralised package management goes for windows, and why I’m personally not at risk for this already long addressed 7zip issue.

“expose systems to remote attackers”.

This is some terrible link bait and Tom’s Hardware should be ashamed.

Backup of the jellyfin cache, Configs and database.
Your media should be outside of all that.

Exactly where those things are depends on your exact install method (native/docker/Linux/windows).

https://jellyfin.org/docs/general/administration/backup-and-restore/

Looks like this is it: https://github.com/jellyfin/jellyfin/pull/13451 Also looks like the intention is to stabilise the new data layer before adding extra backends to avoid rework.

It’s commentary like this that leads to so much industrial equipment (printers, scales, barcode readers, PLCs etc) still having RS-232 on them.

And dammit, you’re right, that stone age shit just works.

nationalsecurityjournal.org looks like a propaganda outlet.

How do you even check the bonafides of a random site like this?

It should go without saying that this was done by loving carers who had the best interests of the animal in question at heart, not coloured by anything crass such as financial considerations - yet here I am.

There are lions at Monarto, a short trip up the freeway and I’ve heard the question of why she wasn’t taken there?
Because the pride would probably have killed her.

She was old, she would have refused to eat, then she’d become weak, then she’d get sick and then she’d have suffered until she died.
The keepers made a call, and as much as people might call this callous, others would have called them out if Amani was allowed to suffer for the following 3 months.

If you “vibe code” your way through trial and error to an app, it may work.
But if you don’t understand what it’s doing, why it’s doing it and how it’s doing it?
Then you can’t (easily) maintain it.
If you can’t fix bugs or add features, you don’t have a saleable product - you have a proof of concept.

AI tools are useful, but letting the tool do all the driving is asking for the metaphorical car to crash.