Text:
I consent to Plex to: (i) sell certain personal information (hashed emails, advertising identifiers) to third-parties for advertising and marketing purposes; and (ii) store and/or access certain personal information (advertising identifiers, IP address, content being watched) on my device(s) and share that information with Plex’s advertising partners. This data is used to deliver personalised ads and content, ad and content measurement, audience insights and product development. Your consent applies to all devices on which you have Plex installed. You can withdraw your consent at any time in Account Settings or using this page.
Soure: https://www.plex.tv/vendors/ (Might have to clear cache)
Can also read about the changes here: https://www.plex.tv/about/privacy-legal/
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
Yup the old one… here’s the new one too… still unaddressed
https://github.com/jellyfin/jellyfin/issues/13983