Well I already have jellyfin running in a container, just have to figure out how to get mum’s TV to work with it I guess
<edit> log in on a local IP and not the network name and it’s working again. but I’ll be moving to jellyfin from now
Well I already have jellyfin running in a container, just have to figure out how to get mum’s TV to work with it I guess
<edit> log in on a local IP and not the network name and it’s working again. but I’ll be moving to jellyfin from now
That only addresses one of several items.
Yes, but it’s always the one people come back too.
They mention the other issues are either being tracked elsewhere or already solved.
At the end of the day, it’s a community project, done by primarily volunteers, who is not making any money doing this. No VC funding to hire developers to take care of these issues.
I understand there’s an explanation for it. Doesn’t make these things not things to consider when choosing one’s solution
But it’s FOSS, compared to Plex. And it also does not ask for money for anything.
You can also add more security yourself if you want to. Not by coding new stuff into jellyfin, but by adding some sort of auth BEFORE jellyfin.
Setting up auth before Jellyfin breaks clients. This is not an option. Edit: Unless you meant VPN like Tailscale, but then you’d have to install Tailscale too, which I don’t want to explain to others.
Tailscale needs you to explicitly add your device to the tailnet, so it’s some form of authentication.
Also, why don’t you want to explain tailscale? It’s really simple.
Good luck installing Tailscale on my friends’ LG webOS TVs.
And making sure Tailscale auto launches on a FireTV stick is a pita too. Telling them to open Tailscale on each start is not an option.
Feel free to go read the multiple writeups from the maintainers that go over each one, we don’t need to copy them all here into the comments for you.