Comment on Overseerr & Jellyseerr to merge into Seerr
Yoddel_Hickory@piefed.ca 2 days agoI wouldn’t say that Jellyfin is an inferior product nowadays, it is much better now, and has things Plex doesn’t have like easy free hardware transcoding
I main jellyfin. It lacks:
I end up using it with tailscale, but that’s well out of reach for my friends and family who share my Plex stuff.
- default SSL
Reverse proxy or configuration in the admin settings
- Carrier grade nat relay.
Not the point of an open source server. That’s your issue.
- caching the TVDB and movie DB.
Why?? But anyway, Jellyfin can poll those for metadata
- Centralized login and account management with 2FA
There is a plugin to do OpenID
- fast search on large libraries.
Can’t comment on that. My library is small (<10TB)
Reverse proxy or configuration in the admin setting
I didn’t say I could recreate Plex in my homelab. I said Jellyfin has short comings.
Not the point of an open source server. That’s your issue.
Moving the goal posts, The point of this exercise is to show how Jellyfin is a direct replacement for Plex. If you say that it is not, my points stand that it is lacking.
caching the TVDB and movie DB.
Every new user that moves from Plex to JF just hammers the fuck out of the free and open services. When one of those services has any issue at all, we’re collectively in bad shape. Plex has protection against this. It would be useful if we cached their stuff and threw it into a DHT, crowd refreshing it.
There is a plugin to do OpenID
This does not work for anything by pc clients. if you feed a roku, appletv, android TV, samsung television, visio… a 2FA prompt, it’ll tell you to get bent. THEN there’s the half assed fail2ban they made instead of surfacing the logs someplace that we could use real fail2ban, but now you have ME complaining that I can’t hack features into it where there’s no reason they’re not already there.
Can’t comment on that. My library is small (<10TB)
Their search sucks balls even for small libraries. They know it and they’ve been working on it for years. There are some crazy hacky solutions screwing with ports and moving traffic through elastic-cache. it’s extremely hacky.
In the end, I’m using Jellyfin as my own personal media server and the media server for my family in my house. It’s not as safely designed as Plex, which itself has had some security issues in the past, but they have a paid team for that, You can’t even hack all the features Plex has into your home lab, I could stick it behind cloudflare and get SSL, some proper anti hammer, anti-abuse, but then I’m selling my watch habbits to cloudflare.
I’m glad we have Jellyfin, I wish I had the skill and time to contribute, if they’d even PR a big-ass change like 2FA, last I heard they were standing on the “that might lead people to port forward it openly which would be less secure”, like people aren’t already doing that.
I’d LOVE to get rid of my Plex, it’s just no where near as capable for my remote users, I can’t force grandma to run tailscale.
Interesting takes. I see and understand your points now.
But regarding your CG-NAT situation:
Sorry but no. This is so much out of scope for the Jellyfin team.
This is something you need to solve by yourself.
Jellyfin can make it easy to maybe offer an integration but beyond that it’s IMO not within the general scope.
In a recent version they improved the database a lot and now search is much faster.
They also removed the SSL config stuff from the UI, using a reverse proxy is the correct way to do this.
Lyra_Lycan@lemmy.blahaj.zone 9 hours ago
That’s good to hear - I rely on HW transcoding for a couple situations and have heard from a couple Github issues that it’s not as good on Jellyfin - but that may not be the case now. Best thing I can probably do is set it up and see how it fares on my library!