Jellyfin

[–] AtariDump@lemmy.world 0 points 1 year ago

And not fixing the issue were you can guess file names? /s

parent

[–] ryannathans@aussie.zone 2 points 1 year ago (4 children)

Removing TLS is a big bummer

hideshow 4 child comments

[–] BritishJ@lemmy.world 11 points 1 year ago (2 children)

Just reverse proxy. The reverse proxy will always handle TLS better.

hideshow 2 child comments

parent

[–] ryannathans@aussie.zone -2 points 1 year ago (1 child)

Sure but it's pretty heavy handed approach for myself to access my own server already on an IP whitelist

parent

[–] yannic@lemmy.ca 1 point 1 year ago*

It more closely follows the UNIX philosophy–Do one thing, and do it well.

By asking the developers to split their focus, we would be admitting that a less secure and/or less reliable product is acceptable.

parent

[–] stonehopper@lemmy.world 1 point 1 year ago

I’m not too versed in this, can i still remote into my library trough wireguard vpn?

parent

[–] Link@rentadrunk.org 1 point 1 year ago (1 child)

Are plugins supported on this release?

[–] Untold1707@lemmy.zip [S] 2 points 1 year ago

They are, but the plugins need to be updated for 10.11. It's suggested to remove all plugins before upgrading and to use the unstable repo while testing. https://repo.jellyfin.org/files/plugin-unstable/manifest.json

parent

7 comments in c/selfhosted@lemmy.world view that post

[–] CybranM@feddit.nu 6 points 1 year ago (5 children)

I tried reading the features list but I'm just a layman, can anyone explain the most impactful changes this update will bring when it's stable?

hideshow 5 child comments

[–] zaphodb2002@sh.itjust.works 8 points 1 year ago (4 children)

The EFCore change is pretty big. They're basically changing how the data is accessed from the database so that would touch most of the software, so potential for new issues is fairly high. Hopefully it will improve performance and concurrency. If you are not comfortable with potential issues, I'd hold off on updating for a while.

hideshow 4 child comments

parent

[–] CybranM@feddit.nu 1 point 1 year ago* (last edited 1 year ago) (3 children)

Thanks, so the goal is better performance? I'm not keen on testing betas but more performance, when the update is stable, is always nice

hideshow 3 child comments

parent

[–] ShortN0te@lemmy.ml 4 points 1 year ago

Performance is not the goal, but cleaner code and more manageable code. But both will ultimately lead to better performance. As of now it was basically impossible to change something in the database structure since it was hard to estimate the impact of it.

parent

[–] WhyJiffie@sh.itjust.works 3 points 1 year ago (1 child)

this is a "beta", the 2nd Release Candidate. they'll mark a stable version when most of the bugs have been ironed out.

parent

[–] CybranM@feddit.nu 1 point 1 year ago

There was a typo in my previous comment, I'll definitely wait for the stable release.

parent

[–] NanoooK@sh.itjust.works 4 points 1 year ago

Improved dynamic HDR metadata handling. Properly detecting HDR10+ videos and selectively remove DoVi or HDR10+ metadata to avoid black screen on devices that only support a single type of dynamic HDR metadata.(This may require client side changes to function properly.)

Good, I have a lot of issue with HDR so hopefully this will improve the experience.