317
People who are staying on Plex, have you tried Jellyfin? What about it do you not prefer? (real question) (discuss.online)
submitted 4 months ago by to c/selfhosted@lemmy.world
457 comments fedilink hide all child comments
 

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
[–] 1 point 4 months ago (3 children)

Sure not knowing of an issue doesn't mean it's secure, but that doesn't also mean that projects with known issues aren't a problem... Like if you want jellyfin to be popular you should want this to be fixed - I don't get this attitude from people who main jellyfin who seem opposed to pushing for it to be better. It not being a big issue is your own personal opinion - it's obvious that known security issues sitting around for a long time bothers a lot of people so the sooner it gets addressed, the fewer reasons people have to stick with Plex. That's a good thing right?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 4 months ago (2 children)

    I am saying all this because it's more blown up than it is. I have said in basically every single post that it needs to be fixed right? So pls do not suggest that I do not want it to get better.

    But, this link to the collection of vulnerabilities gets posted on every argument without any explanation and or classification. Which is also not ok.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 4 months ago* (last edited 4 months ago) (1 child)

    For starters, it being brought up wouldn't be an issue if there was some timeline to fix it and the response wasn't just "it's too hard and would break clients", and secondly, I think it's not congruent with wanting to improve jellyfin if your reflex is immediately to say that nothing is truly secure. Could you imagine if next cloud had a similar issue and put it off for more than 5(?) years?? Is that really not enough time to get the clients and apps in order? They should just put the issue to rest so we can move on with making jellyfin better. I don't think anyone wants it to remain an issue for another 5 years, and I think calling that blown out of proportion is kinda ridiculous.

    Like if 5 years ago they said you have 5 years to update your app, we could have had this issue checked off and nobody would be able to complain about it or use it as an excuse not to switch, so the next best time to set a deadline would be now. They should just as soon as possible say you have a couple years to update your apps, at least schedule a date years in the future to rip off the bandaid instead of kicking it further down the road.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 4 months ago

    I think it's not congruent with wanting to improve jellyfin if your reflex is immediately to say that nothing is truly secure.

    At no point in life I said that.

    Jellyfin has proven with the latest RCEs that they can handle relevant critical security vulnabilities.

    As always, jellyfin does not have that much relevant contributers, and a lot of work has been done in recent time. It is very easy to lean back and say what they should or should not have been doing.

    Breaking Clients would make the project not usable for many ppl or at least decrease the usability.

    As i have already said, getting uodatea on those closed eco systems can be a nightmare.

  • permalink
  • fedilink
  • source
  • parent