Selfhosted

hideshow 8 child comments

parent

[–] LordKitsuna@lemmy.world 1 point 4 months ago (7 children)

That would be the case, however the devs official stance is it's unsafe and should not be used other than over vpn. So they also agree

hideshow 7 child comments

parent

[–] ShortN0te@lemmy.ml 1 point 4 months ago (6 children)

But for complete other reasons than RCEs or similar.

As an FOSS project that inherited lots of shitty code this is basically the best thing they could do.

Not sure why, but you get specific about once RCE but not about other problems and keep vague about them. Is it the lack of understanding or disingenuousness?

hideshow 6 child comments

parent

[–] LordKitsuna@lemmy.world 1 point 4 months ago (5 children)

Once? No jellyfin has had about 4 major RCE issues since the fork. At least 4 that I'm aware of. Blaming it on the previous code only makes sense if the split is recent. They have had time to completely rewrite if they really want.

I'd like to see plex die entirely, but I know too many less technical people that use it . They are not going to set up a VPN , end of story end of discussion. And I'm not going to tell them to use jellyfin when it will likely continue to have major security issues and could compromise their systems. I have no doubt that Plex leadership is fully aware of this, they know that even with them pushing more subscriptions and higher costs they are going to continue to have users because the alternatives are just not able to keep up and are not viable for the average person just the technical users which they would have lost to alternatives regardless

hideshow 5 child comments

parent

[–] ShortN0te@lemmy.ml 1 point 4 months ago (4 children)

Once? No jellyfin has had about 4 major RCE issues since the fork. At least 4 that I'm aware of. Blaming it on the previous code only makes sense if the split is recent. They have had time to completely rewrite if they really want.

It absolutely makes sense, otherwise they would have had to throw everything away.

The EFcore refacotring was like 6 years in the making.

And all that from just a few single ppl. Look at the ckntributer list, and how many contribution. Not many active devs are working on jellyfin on their free time. The problems that jellyfin has, is not from a lack of trying but a from a lack of finger and arms.

And you need to take it like it is.

hideshow 4 child comments

parent

[–] LordKitsuna@lemmy.world 1 point 4 months ago (3 children)

Ok? I will take it like it is. Jellyfin is a flawed product not currently suitable to replace Plex for the average person and is only particularly usable by technically inclined users capable of protecting themselves through VPN or other means. As well as dealing with things like failed matched media and memory leaks that are frequent.

That is how it is, and that's how I've been taking it from the start.

hideshow 3 child comments

parent

[–] ShortN0te@lemmy.ml 1 point 4 months ago (2 children)

No, not really. But what should i expect from someone who states as an 'objective opinion' "I do not like the programming language so the project is bad"

If i had to guess, since you are jumping on the memory leaks, you got an issue, reported it and did not get treatet like they fix it with a priority.

You keep jumping on "They had an RCE so the security must be completely broken"

hideshow 2 child comments

parent

[–] LordKitsuna@lemmy.world 1 point 4 months ago (1 child)

Actually, i mentioned the memory leaks as it's been a consistent issue for years now. Again normal people cant and won't setup special containers with memory limits as a crappy work around.

You may not like that i don't blindly glaze jellyfin because it's open source. However I'm just being realistic about what it needs to actually be a viable replacement for plex for the masses.

It needs to be able to match media properly, it still struggles with this even when you go out of your way to make sure the media is named in the exact manner the documentation dictates. It needs to be able to be used remotely simply through the web, having to set up a VPN is not a viable approach, it needs to be able to function long-term without eating up all the system's memory and requiring regular restarts to prevent it from going out of control. Subtitles need to work on all clients, as it stands right now Roku subtitles are non-functional like 80% of the time no matter what you do, some TV browsers struggle with it as well.

I am sorry that that upsets you, but it is the reality and it is the reason the projects like these tend to mostly be used by the technically inclined. Including myself, I was able to put it in an unprivileged secured lxc container, so that I could use it through the web and set memory limits, but most people cannot and will not do that. I would prefer to see it be successful and be able to tell everyone never touch Plex again, but I know that telling people it's ready to go while it has a myriad of basic issues is not helpful.

parent

hideshow 1 child comment

[–] ShortN0te@lemmy.ml 1 point 4 months ago

And the memory leaks get closed one after another? Dont they? Just because there are still issues does not mean it gets improved upon.

Media matching is no issue if you follow the naming sheme.

I am not upset at all, not sure why you think that.

Jellyfin will and connot be the replacement you wish it to be. Exposing something to the Internet is not a solution for the normal person. Heartbeat, Log4shell etc. etc. all of those are the reason why, not necessarily the service you are hosting by itself.

Especially in an age where tailscale is available to install on every major smart TV or other devices i do not get why you even want to recommend ppl to expose it.