this post was submitted on 22 May 2026
126 points (99.2% liked)

Selfhosted

56958 readers
1638 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Honest question, because I know multiple people who are not looking to jump ship since they already have the Plex Pass.

you are viewing a single comment's thread
view the rest of the comments
[–] Pika@sh.itjust.works 12 points 7 hours ago (1 children)

I'm not using Plex, but I feel like I can answer my complaints about using jellyfin.

My biggest complaint is the lack of clients. It is such a pain in the butt to install jellyFin on all of my products.

My second complaint is the security design. They've had open issues about unauthenticated endpoints for three or four years now. And whenever the issue gets so old that it starts to look bad, they refactor the issue into a newer issue abd bury it in the sand.

For a while this was done under the guise of maintaining legacy client support, but just recently it looks like they're starting to focus on more security, and I've noticed some of those security holes are being closed finally, but it's a major concern for me that they've been open for as long as they have.

[–] ShortN0te@lemmy.ml 3 points 5 hours ago (1 children)

My second complaint is the security design. They've had open issues about unauthenticated endpoints for three or four years now. And whenever the issue gets so old that it starts to look bad, they refactor the issue into a newer issue abd bury it in the sand.

You mean that one issue that is still open and linked in the "security and quality" tab on github?

[–] Pika@sh.itjust.works 2 points 1 hour ago* (last edited 1 hour ago)

i feel like one issue is a bit of a downplay here, considering that it's 12 different issues being shown as one mega issue. but yes that has most of them

But that's also the most recent version of it. Some of those issues that they have listed there has had previous issues that were closed to be consolidated into that mega issue, which then was closed to be split into their own issues again.