So don’t expose it to the internet - which should be the default stance for anything.
The internet was (mistakenly and intentionally) built without security - that doesn’t mean we should just accept that, but instead build everything with our own security.
Numerous mesh VPN solutions exist: Hamachi has been around since at leas 2006. NeoRouter since at least 2012. Then we have Wireguard and Tailscale.
Business build their own tunnels between locations, using routers/gateways with that capability. Consumer routers from Linksys could do this in 2006.
Thwres zero excuse for running anything exposed to the internet.
Strit@lemmy.linuxuserspace.show 3 days ago
From one of the Jellyfin devs in the issue you linked, posted in April this year:
TrickDacy@lemmy.world 3 days ago
That only addresses one of several items.
Strit@lemmy.linuxuserspace.show 3 days ago
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.
TrickDacy@lemmy.world 3 days ago
I understand there’s an explanation for it. Doesn’t make these things not things to consider when choosing one’s solution
somerandomperson@lemmy.dbzer0.com 3 days ago
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.
Chewy7324@discuss.tchncs.de 3 days ago
Setting up auth before Jellyfin breaks clients. This is not an option.
scrubbles@poptalk.scrubbles.tech 3 days ago
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.