MaggiWuerze

I have a Philipps OLED TV from 2019, with Android 9 or smth. But WebOS is a different beast.

Well, just because they closed the issue (without resolving it), doesn’t mean it does not speak to their views on security and client breaking changes

The issue is their approach to security. I don’t trust them to properly secure their software, since they have proven to prefer client compatibility over security.

https://github.com/jellyfin/jellyfin/issues/5415

They argue against most suggestion with the notion, that existing clients can’t handle authentication. The devs prefer working clients over a properly secured backend.

You can now extrapolate this idea and every major change that would change the way the API is accessed by clients will be stopped for the sake of continued client compatibility.

Yeah, but since you basically need a VPN to share Jellyfin safely, you now also need to install and maintain that on their end

I will not make myself the tech guy for half my friends and family, just because I can’t share Jellyfin safely without a vpn

Also the people that know how to set that all up and still expose a Jellyfin server to the public internet

Because Jellyfin users like to feel superior. Accepting that other people have other requirements from software is hard, especially when you feel like you choice is the only valid one.

As a long time Plex user, who has a Jellyfin running in parallel, just not shared, I will keep using Plex until they either force me off of it or Jellyfin manages to make accessing servers remotely easier and more secure.

Yeah, first thing I did after testing the new app. Still don’t know why they feel the need to push this out so aggressively instead of letting it run in parallel until its ready

If you have not set up a VPN for accessing your Jellyfin, I would suggest looking into the myriad of security issues the Jellyfin Backend has. Jellyfin has no business being accessible from the public internet

If they adhered to somewhat modern security principles for their Backend I wouldn’t mind hosting it behind a reverse proxy. But since large parts of the API is unauthorized and unprotected, I wont.

And I do not plan on supporting family and friends in setting up vpns on all of their devices

Or… You know… Jellyfin could make it so I don’t have to setup elaborate VPN schemes and have every user install that on every one of their devices. For example they could fix their security issues to make it safer to expose JF through a reverse proxy, bug they refuse to not break client compatibility

The Jellyfin devs have made it clear, that they will not make changes that invalidate existing clients. Rebuilding the things that make sharing content via Plex so much easier would most definitely break client compatability

I’m not even against Jellyfin or anything, but as long as I have to build elaborate VPN solutions to continue sharing my content I’ll stick with Plex. Not even starting with the availability of clients on different platforms and the general lack of polish in Jellyfin first party UI (player and config).

I could live with most of that stuff if there was a way to share my library without becoming tech support for half my friends circle

User sharing without opening my Plex server to the public internet. For Jellyfin I would have to become a VPN provider and allow people into my private network to share it safely, since you wouldn’t want to have Jellyfin available to the internet with their stance on security

Not to rain on your parade, but the Plex App on my TV, with a library of almost 40TB also loads in seconds

Yeah, no way. Jellyfins Backend is like an open barn door. And with the kind of content most of us here offer through either Jellyfin or Plex, I wouldn’t want to open up like that.