

There are a number of ways to do that without breaking clients. They could add a api/v2 with the option to disable the old one and clients could choose to support the new one, with the old one being set to deprecated
There are a number of ways to do that without breaking clients. They could add a api/v2 with the option to disable the old one and clients could choose to support the new one, with the old one being set to deprecated
Nobody said anything like that. I’m just saying that Jellyfin fans tend to get pretty emotional when the topic comes up, as you just proofed fabulously
The difference being, that the Plex devs weren’t confronted with a list of security issues and basically shrugged and dragged their feet for 5 years
And with that it loses any edge it had over Plex. If I have to install a VPN on every device of every user, just because the project wont adhere to basic security practices, then I will not switch to it.
Or their convoluted settings. When there’s a github project that does the HW encoding settings for you, you know it’s intuitive…
It doesn’t have to, but the tone that is used when criticizing Plex users is pretty personal a lot of the time. Hard not to take it personally when using Plex is portrayed as as a sign of brain damage
You clearly have not been in a lot of Plex/Jellyfin threads. Using Plex is often portrayed as some kind of capital sin by hardcore Jellyfin fans.
I’m also in the boat of letting people use what they want, but the discussion is usually not made in good faith
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.
Thanks for your permission