Doesn't do shit when large parts of the Backend are not authenticated
You could also try photopea. Its web based and free and has alignment similar to Photoshop
Yeah, I kinda remembered that as soon as I posted. Hope you're okay after all that
Lol, where do you live that your power is out for a whole week?
The alternative is that dey just don't care or are not capable of fixing it, despite numerous suggestions in the github thread. Both don't bode well for the project, especially seeing as that ticket has veen open and discussed for almost 5 years
You don't need to post it. Bots are scanning every ip, 24/7, looking for servers to infect, endpoints to abuse and data to extract.
Go set up a ssh tarpit on your server and watch the flies drown in it. I will not expose anything on my server that has so many known vulnerabilities
Your content might be legitimate, but the vast majority use Plex and Jellyfin as a media Server for pirated content and still want to share it with their friends or family. And just FYI, most blurays and DVDs also forbid this kind of sharing in their license
Nobody seen anybody needs to switch to jellyfin
I guess you haven't read the rest of the comments here :D
At this point I just wait and see. I have Jellyfin running in parallel, but the way remote sharing works there, basically requiring a VPN on every client device makes it a non starter for a large portion of my users and with the security situation of the Jellyfin Backend I don't feel comfortable making it available through my domain.
So for now I will just wait and see and hope that the Jellyfin fanbase could just chill a bit and stop gloating and high giving any time there's a Plex related news on here
Because Plex handles the initial connection for you allowing the clients to lunch through CGNAT and other shit. Also they handle the authentication, which I would fully agree would be nice to have independent, but that's the reason
Everything besides VPN breaks their clients because they can't handle authentication.
My main gripe isnt even that they have these issues, but the way the jellyfin devs are handling, or more correctly, not handling them.
They actively refuse to fix them because it might break client support. Instead of forcing an update or starting a secured v2 of their API, that actually active clients could then update to, they just do nothing
They can stream content from your server or map out what you have on there by using a rainbow table. Depending on the country you live in they can and will use that combined with your IP to start litigating you
After setting up an elaborate VPN scheme
The magic bullet in that sentence is VPN not reverse proxy