.1 was hotfixes to do with the major release.
Everything since then appears to just be shipping features as soon as they are proven stable.

I’ve updated 10.9.1 -> 10.9.2 -> 10.9.3 (and I’m about to do .4) and I just manually fire off the trickplay generating task after each update.
It quickly walks through the files that have already been done and then resumes processing from where it left off.
Currently at 13% after like 10 days or whatever it is.

Looks like it’s a manual process.
It also looks like no Jellyfin developer is creating the builds on Flathub and that some random member of the flathub community did it.

Whilst the devs provide instructions for all manner of install methods, the preferred version is definitely via docker.

Yeah, I can see it now.
I can only assume that the post hadn’t propagated to my server 3 hours ago.

Short answer no.
Plex works by having a centralised server run by Plex themselves, that facilitates your client connecting to your server.

The external facing part of Jellyfin server is basically a web server, and it’s a bad idea to expose that to the internet without putting a reverse proxy in front of it (hence the mention of NGINX above).
Another option is to have a VPN connection to where you are running Jellyfin and then only access Jellyfin pseudo locally (so potential security problems aren’t a big concern). This introduces other complications if you want to access it remotely via things like Roku or Chromecast, especially if you have multiple external (and probably not tech savvy) users.

I want to stress that none of this is prohibitively expensive or hard, but doing it involves learning and effort.
All the information and programs you need are available online for free.

If you only wanted to use Jellyfin at home (server in the cupboard, client on the tv), none of this other stuff matters. If you want to access Jellyfin remotely, and the idea of running a reverse proxy or a vpn server with the corresponding exposed ports and domain configuration sounds scary, Jellyfin is probably not for you.

pihole blocks ads by refusing to return dns results of known ad hosting URLs.

Chromecast ignores your DHCP supplied dns UNLESS 8.8.8.8 and 8.8.4.4 are inaccesible.

People who’s bothered to do this have added static routes to make all requests on port 53 go to the pihole.

https://www.reddit.com/r/pihole/comments/uaov2a/how_can_i_override_chromecasts_hardcoded_google/

Windows XP is basically firmware at this point, and has been for over a decade.

Lots of proprietary hardware that works perfectly, will not work on newer versions of Windows due to lack of drivers.

I see it constantly in factory situations with scales, scanners and robot controllers, it would only be worse for million dollar x-ray machines.