In todays episode of “Plex enshittifies” Plex employee breaks ToS.
Source: https://forums.plex.tv/t/fake-reviews-on-play-store-by-plex-staff/917736
In todays episode of “Plex enshittifies” Plex employee breaks ToS.
Source: https://forums.plex.tv/t/fake-reviews-on-play-store-by-plex-staff/917736
I think they’re meaning exposing it to the public for the pirate tv use case. In my personal experience (1 non savvy user using the roku app, no vpn), it’s not much support. I had to talk them through initial sign on, and through re-sign-on after that latest update that forced it. Of course ymmv, but two 5 minute tech sessions with grandma over 2 years of consistent usage ain’t that bad.
I’ve racked my brain to determine WHY that happened, but the only thing I can guess is Roku saw the channel differently because I packaged it instead of the previous person, so the config didn’t port over /shrug
Never had that happen before.
I figured it was the enforcing of the trusted proxy mechanism mentioned in the release notes (only noticed because of an earlier thread here, thanks!). Once I updated my server and set the proxy settings all my clients needed to be signed again.
And I’m talking about the reverse problem. That you would need to expose it in order for it to work with other users… OTHERWISE be on the hook to support users via VPN + Jellyfin, or in the case of TV apps, Router+VPN+Jellyfin. That doesn’t scale up well the moment you have someone not in your house that uses your stuff. It doesn’t have to be pirate TV. Could just be a kid at college.
Yeah I don’t think anyone sane would disagree. That’s what forced the decision for me, to expose or not. I was not going to try talking anyone through VPN setup, so exposure + whatever hardening practice could be applied. I wouldn’t really advocate for this route, but I like hearing from others doing it because sometimes a useful bit of info or shared experience pops up. The folder path explanation is news to me; time to obfuscate the hell out of that.
Exactly… But I get chastised for pointing the problem out. Called a shill because I care about security.
I RUN JELLYFIN. I HAVE IT RUNNING. Others you recommend it to should be made aware of the risks that’s all I’m trying to point out.
You can get around the MD5 issue (a bit) by obfuscating your path. Instead of
/movies/title (year)/title.ext… make it/mnt/MHhzTiM57Fv4wWQmkmb4DLDwVKoB628KBQzhBHQjGQVtsjhwRrFNU2NtRGJ4dUpg/movies/title (year)/title.extand you’ll probably be pretty damn immune to the problem as it stands now… But just blatantly telling people to use Jellyfin isn’t a good answer here without that background.Awesome, thank you, this is exactly what I was thinking when you mentioned it earlier.