this post was submitted on 29 May 2025
1562 points (97.4% liked)

Selfhosted

46676 readers
373 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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/

you are viewing a single comment's thread
view the rest of the comments
[–] MaggiWuerze@feddit.org 2 points 1 week ago* (last edited 1 week ago) (1 children)

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.

[–] andyburke@fedia.io -1 points 1 week ago (2 children)
[–] MaggiWuerze@feddit.org 2 points 1 week ago

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