What? Why would I have to make my library harder to manage just because Jellyfin devs can’t get their act together? They should just start a api/v2 and secure it properly while allowing to disable the old one
What? Why would I have to make my library harder to manage just because Jellyfin devs can’t get their act together? They should just start a api/v2 and secure it properly while allowing to disable the old one
Not everything you don’t like to hear comes from a bot
I am waiting for opencloud to finish its calendar implementation. The only thing I have reservations about is the fact it doesn’t use a database to store file info. Not sure I trust their approach
Sure, the utterly fucked up authentication of the Jellyfin Backend somehow is the fault of Plex users and everyone who points out obvious flaws is of course a Plex shill.
Maybe you should take a look at what you are defending here. The fact that the devs openly refuse to fix this to maintain backwards compatibility, thus endangering their users speaks a lot about the quality of the project
It’s not chance if the I’d is based on the path to your media. There’s but that much variation in the path to a certain movie and its trivial to build a rainbow table to try them out. This way unauthenticated users can not only stream from your server but effectively map your library
It’s not impossible, Far from it. The ids are not random uuids but hashes derived from the path. Since most people have a similar setup to organize their media, this gets trivial very fast
Nice, switched immediately
That depends entirely on your target audience as well as the devices you want to use it on. Smart TVs don’t really support VPNs and my parents would not know how to even activate that let alone set it up on their end. I have a lot of non tech savvy users, so Plex is just way more convenient and accessible.
The main issue for me is the way they react to it. Not only is there no warning about this, but they also refuse to fix it because it would break client support and they prefer backwards compatibility over security
I’m just not sure if fail2ban can mitigate the unaouthorized api access or other issues
If you plan to use fail2ban, I assume you want to make your Jellyfin accessible from the public internet. Please be aware, that large parts of the Jellyfin Backend are not properly authenticated and allow unauthorized, potential mapping of your library and even unauthorized streams.
Will have to even
Can’t wait for this to arrive on my phone
Ah, sry. Thought you were the guy who thought this was the doom of indie game Deva or something
Again, I don’t know your upload speed, but the usual private household has around 30-40Mbit, which is not nearly enough to transfer large games quickly. It would probably be quicker to driver over to your house with a thumb drive and get the games that way
This is not ment as a Plex for Games, since you can’t stream the content and most people won’t bother downloading dozens of gigabytes from a private households upload speed. It’s just a neat way to organize your DRM free games so that you and people in your local network can install and manage them easier
You don’t really need much documentation. You set it up on windows once, which is pretty intuitive and then you copy the config to your server and run it headless. It pulls your library in fixed intervals. I haven’t touched it once in the year it is running now
Shoutout to Libation, that allows you to download and deDRM your Audible library.
From personal experience, Docker is fine. Just be sure to use postgres instead of the default mariadb and you’re golden
No, I’m the kind who thinks security by obscurity is bullshit. But you do you