Plex now want to SELL your personal data
-
I am a die-hard Jellyfin user, but I still haven't found a proper way to index and stream my music library with it. As far as i know, Plex is still better at that.
I dropped my library in, Jellyfin indexed it and streamed first try. What didn't work for you?
-
Every day of my life trying to explain to friends they need to quit using spoon fed software. Sigh.
Exactly why on so many things it's like... even when it looks like they are getting it, they don't get it. Kind of like watching bluesky rising right now. Unless I'm majorly missing something here. It looks like it's kind of open and kind of federated...
Except in a form that no one can feasibly create their own node. One change in leadership or goals of leadership away, and it can turn into the same neo nazi trash that people are joining it to get away from.
-
If we find out "I do not consent" opts out, I'm fine with it.
Why? They don't need more money. Jellyfin proves how much of their service can be done for free
I don't disagree at all, but morally and legally speaking if "no" means "no", I don't actually see anything wrong with the prompt or the idea itself. If no means "later" or "limit this data", or even "anonymize this data", it's time to revolt.
I agree Jellyfin's pretty rad and DOES prove what can be done for free, I've used both and Plex is a much more "set and forget" and I personally have had more issues with streams breaking/stopping for no reason with Jellyfin- are those probably my fault? Yep, probably borked a setting or misconfigured it- just saying that's my personal experience.
I'm just one idiot making noises with my meat flaps. I'm no authority.
-
Can someone clue me in on the reason why anyone would prefer Plex instead of Jellyfin?
Can I ask why nobody recommends Emby? I've been using it for years with zero issues. The only thing I can think of is that Jellyfin exists and is free. Emby is sort of a middleground between Plex and Jellyfin; it has a paid license (lifetime option exists), but it's closer to Jellyfin than Plex on the whole.
-
::: spoiler spoiler
askldjfals;jflsad;
:::Yeah, but then you're not self-hosting, you're paying or using their free services to manage that for you.
-
Can I ask why nobody recommends Emby? I've been using it for years with zero issues. The only thing I can think of is that Jellyfin exists and is free. Emby is sort of a middleground between Plex and Jellyfin; it has a paid license (lifetime option exists), but it's closer to Jellyfin than Plex on the whole.
Emby rugpulled their users, that's why jellyfin exists at all.
-
Nothing is ever truly free in this world. They gotta pay their bills too.
Sure, that's why I paid for Plex Pass. Plex isn't free.
-
Nothing is ever truly free in this world. They gotta pay their bills too.
Yeah, and there are decent ways to do that, which many successful companies and individuals manage to pull off every day.
I have no horse in this race because I don’t use any of this stuff, but I despise the direction everything is going.
Human parasites are never happy with being well fed it seems. They aren’t happy unless they gorge until they get fat and explode, or they’re so greedy they end up killing their host.
-
Emby rugpulled their users, that's why jellyfin exists at all.
Do you mind elaborating on that? It sounds like I got in on Emby after the rugpull. It works fine for me and I use it without the Connect (online account) feature.
-
You are actually wrong about that first assumption, I did try both at the same time and the problems with Jellyfin moved me over to Plex. Plex never had an issue handling my remote library at any point, and in fact ran just as well in a container in the NAS holding the files as it did natively on both Windows and Linux, so it was surprisingly easy to see what combination of placing files and software worked better for me.
Which I guess is a good segue to your second point, because hey, turns out there are plenty of applications that are pretty agnostic about running inside of a container or not, Plex included. And there are several implementations of easy self-hosted apps that will set up a container for you. Unfortunately most of those are commercial software trying to monetize self-hosting, and snobbish hobbyists seem to have no particular urgency for beating corporations to that particular punch.
And yes, you can run Plex and Jellyfin together. I don't know what that point is supposed to add to this. You can mostly run any software alongisde any other software. Frankly, the biggest issue of doing that, besides how redundant it is, is that Jellyfin will insist on writing a whole bunch of garbage all over your library if you want to set it up its way. Plex will mostly tolerate this and keep chugging along, though, so it's not a dealbreaker if you don't mind.
And absolutely you can make a hobby out of self-hosting or whatever else, but the point is car nuts typically don't hold the opinion that nobody should be having cars but them. I mean, there's plenty of car snobbery, and a bunch of people will say they prefer a manual transmission car over an automatic, but it's a pretty extreme position to hear someone say if you can't drive stick you shouldn't have access to cars. Let alone say that if you didn't build your car yourself you aren't skilled enough to have one, which is the actual equivalence here.
You are actually wrong about that first assumption, I did try both at the same time and the problems with Jellyfin moved me over to Plex.
I inferred it from this:
Plex was one of the first things I hosted because all you have to do is installing like you would any local application and it just works
And anyway, plex and jellyfin have different media library configuration requirements. Even if you did them at the same time, you'd have to be kind of lucky to have configured them both on the same media volume correctly without reading any of the documentation or having experience with docker ACL rules.
Just as a for-instance (since I don't see any specifics), sharing a media volume across separated docker containers on linux requires mapping the same users and usergroups to each container. It's assumed you should know this, if you're deploying a stack of services on a server, because containers are designed to be isolated and secure - containers are restricted to accessing files in their approved ACL, so that a bad actor can't get access to a separate volume from a compromised service. One possible problem you were having (again, just a guess) is that jellyfin was assigning itself ownership of the files/folders on the media volume every time it did its scan, and Plex no longer had permission to access them. It actually doesn't matter which service was there first - as soon as you had two services accessing the same volume you would have run into this issue. It depends on how you configured both services, and if you gave them privileged access or mapped users properly, ect.
and in fact ran just as well in a container in the NAS holding the files as it did natively on both Windows and Linux
If you're running both services on a store-bought NAS, the problem could have also been a misunderstanding about the combined overhead requirement for the services. Without making any assumptions about how much thought you put into your configuration, I'd check that as a part of troubleshooting. But, again, seems like you don't give a fuck about troubleshooting your customized service stack and would rather use a ready-made product. That's fine.
turns out there are plenty of applications that are pretty agnostic about running inside of a container or not, Plex included.
Jellyfin included also. I'm not sure what the point you're making though.
Frankly, the biggest issue of doing that, besides how redundant it is, is that Jellyfin will insist on writing a whole bunch of garbage all over your library if you want to set it up its way.
I agree it's redundant, which is why I personally only deploy jellyfin now. As far as jellyfin writing to your media drive...... Yea, I guess that is a difference between the services. This isn't really a problem if you configure your containers correctly, but if you don't want to mess with that stuff I can see why it might be an issue for you. Plex may be storing those files on its container volume instead of the mounted media volume, or it could be storing them on their remote server (it's been a while since I had plex running), which is a fine way to do it too. There are advantages to writing it to the media volume, but I won't bore you with that
Let alone say that if you didn’t build your car yourself you aren’t skilled enough to have one, which is the actually equivalence here.
Good thing nobody is telling you not to have a homelab or use selfhosted services. If you want to use Plex and only want to drive automatic transmissions, go for it. Doesn't change my preference or enthusiasm for jellyfin or manual transmissions, though. And given the opportunity, i'll still passionately debate the advantages to learning stickshift and open-sourced and customizable self-hosted applications. And if you give them a try and run into problems, i'll gladly help you try to solve them if you're willing to engage with it - but if you'd rather just complain about how much my preference sucks then i'll have no problem telling you to stick with what you know next time.
-
Text:
I consent to Plex to: (i) sell certain personal information (hashed emails, advertising identifiers) to third-parties for advertising and marketing purposes; and (ii) store and/or access certain personal information (advertising identifiers, IP address, content being watched) on my device(s) and share that information with Plex’s advertising partners. This data is used to deliver personalised ads and content, ad and content measurement, audience insights and product development. Your consent applies to all devices on which you have Plex installed. You can withdraw your consent at any time in
Account Settings or using this page.Soure: https://www.plex.tv/vendors/
(Might have to clear cache)Can also read about the changes here:
https://www.plex.tv/about/privacy-legal/Last shit they pulled I moved to Jellyfin. Today I deleted my Plex account.
-
Yeah, but then you're not self-hosting, you're paying or using their free services to manage that for you.
wrote last edited by [email protected]::: spoiler spoiler
askldjfals;jflsad;
::: -
From what Ive seen in arguments about this, Plex generally is more accessible with QoL and easier to understand interface for non-techie people to share with family/friends. Something thats hard for nerdy people to understand is that average people are perfectly fine paying for digital goods and services. An older well off normie has far more money than sense and will happily pay premiums just to not have to rub two braincells together with setup or for a nicer quality of experience. If you figure out how to make a very useful plug-an-play service that works without the end user of average intelligence/domain knowledge stressing about how to set up, maintain, and navigate confusing layouts, you've created digital gold.
This isn't the fault of open source services you can only expect so much polish from non-profit voulenteer. Its just the nature of consumer laziness/expectation for professional product standards and the path/product of least resistance.
-
I don't know why everyone in the selfhosting community still even mentions Plex or uses it.
It's closed source, not free; Jellyfin is a no brainer yet people still go to Plex??
Because it works. Call me in a few years when movies, TV shows, dvr recordings, live TV (with free, built-in guide support), and working picture support shows up. Oh, commercial removal too (again, built-in, just check a box). A not-shit setup process would be nice, too.
I've tried jf three times now across as many years, and it's still got that 'Linux developer feel' of a tool where the devs got what they need the most mostly-working, and just don't give a fuck about anything else - or a decent UI. No, blue boxes on a black background is not a decent UI. It wasn't when W8 launched, and it's not now. And when W8 is winning the competition, you've already lost.
Feature parity or the argument is moot.
-
I wonder if having a “sign in” page within jellyfin that just fronts a wireguard configuration panel, saves the creds, and automatically connects and routes app traffic over the vpn iface is a remotely viable idea.
That depends on if someone wants it enough to make it happen.
-
I have read many people say this, but I don't understand what they mean by it. When I set up Jellyfin, it was a very simple process.
Setting up a server? Pretty darn easy.
Teaching all your friends and relatives to figure out what app to use and login with your dyndns random entry or IP address. Or even more difficult, using VPN.
It's not the hosting that's hard. It's the watching for non-tech people.
-
Do you mind elaborating on that? It sounds like I got in on Emby after the rugpull. It works fine for me and I use it without the Connect (online account) feature.
wrote last edited by [email protected]For one, they moved from open source to closed source without notice.
https://web.archive.org/web/20181212104719/https://github.com/MediaBrowser/Emby/issues/3479
-
Can someone clue me in on the reason why anyone would prefer Plex instead of Jellyfin?
End user management.
Essentially, accounts and passwords are not my problem.
-
Setting up a server? Pretty darn easy.
Teaching all your friends and relatives to figure out what app to use and login with your dyndns random entry or IP address. Or even more difficult, using VPN.
It's not the hosting that's hard. It's the watching for non-tech people.
Maybe I'm just callous but I just don't see that as a problem myself. If I'm offering my own self hosted services for friends or family, the least they can do is put in some effort to learn how to use it. If they couldn't bother, that is their loss.
-
::: spoiler spoiler
askldjfals;jflsad;
:::You called him a liar and then got pissy when he fired back. Grow a thicker skin or don't start shit.
