For Plex accounts created before March 20, 2025, we require your consent to sell your personal data as described in our Privacy Policy. You can always adjust your share/sell preferences <here>.
For Plex accounts created before March 20, 2025, we require your consent to sell your personal data as described in our Privacy Policy. You can always adjust your share/sell preferences <here>.
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
Citation needed.
The most compelling feature I always get asked if Jellyfin has ala Plex is the discovery/NAT punch for linking people up.
That does not strike me as something that necessarily breaks backwards compatibility. It would require some centralized discovery, and I think that is probably where we run into an issue because if I were the Jellyfin devs, I wouldn’t want to have to support that, either.
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.
It’s this old link, eh?
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