I’ve feel like I’ve used Plex forever. I also feel like every couple years I try Jellyfin to see how it’s going. Recently I tried it again because of Plex restriction on more than one user.

Well, I just tried it again and it’s substantially improved! This time it actually properly detected most of my library!

Also the Android TV app is AWESOME! No more glitches, lagging, and freezing trying to play my stuff like Plex did. It is butter smooth.

Wow! I’m impressed and I just deleted Plex. Good riddance.

You are viewing a single thread.
View all comments View context
3 points
*

Wait, isn’t Jellyfin the same way?

Jellyfin has a native web-ui, yes. But not a proprietary one, like Plex uses. When I installed a Plex server I had to go to plex.tv and setup a user account there to be able to log into my own damn server… Then they strongly encourage you to use https://app.plex.tv/ to manage your local server.

It’s all unnecessarily confusing and difficult.

Is there no account management on Jellyfin?

Yes. Local accounts. Not some cloud based PAMd system.


You made me feel like I was crazy, so I just downloaded Plex Media Server and installed it. Ran it, and was immediately presented with this: https://i.xno.dev/mqWFZ.png

I was then immediately routed to app.plex.tv and see this: https://i.xno.dev/cLPfw.png

There’s no option to not use a plex account. You must either use an existing account or sign up for one. You cannot use local users. Then it forces you to use the app.plex.tv so it can display content you don’t even have, or have access to…

How in any possible way is any of this easier than Jellyfin?

EDIT: Oh, don’t forget the sales pitch! https://i.xno.dev/79WBs.png

permalink
report
parent
reply
0 points

Okay, but… how is it confusing from the front end if what you’re doing is going through the same steps of creating an account? You punch in a login and password in both.

Sure, Plex is doing this extra thing where it’s also bringing in centralized content along with your library and it will default to its remote access system if you log in from outside your network. But again, from the front-end that is transparent. You log in and you have your library. If anything they’re being a bit too transparent, I’ve had times where networking stuff got in the way and it took me a minute to notice that Plex was routing my library through their remote access system instead.

I can see objections to it working that way, you trade a (frankly super convenient) way to share content remotely and access content from outside your network without too much hassle for… well, going through someone else’s server and having their content sitting alongside yours. But “confusing and difficult” isn’t how I’d describe it. It seems to work like any other service, self-hosted or not, as far as the user-facing portions are concerned. I guess I just don’t see the confusing part there.

permalink
report
parent
reply
2 points

Okay, but… how is it confusing from the front end if what you’re doing is going through the same steps of creating an account? You punch in a login and password in both.

Because there’s zero difference between the app.plex.tv interface spawned from plex server, and one without. There’s zero indication that it’s actually your server and your content because it fucking displays everything by default.

It’s such an incredibly bad proprietary system…

But again, from the front-end that is transparent.

It’s not. There’s no server configuration options at all. There’s nothing to indicate it’s local content…

I can see objections to it working that way, you trade a (frankly super convenient) way to share content remotely and access content from outside your network

For 90% of the content people use Plex for, this is an illegal act. So I don’t see the advantage to providing this option let alone making it easier to commit a felony… I’ve never needed to “share” my media library with anyone and even if this was something I wanted to do, it’s a simple DNS record away from doing the same thing in Jellyfin. There’s no reason to lock people into your login system because 10% of people would “find it easier.” It’s just such a bad argument.

permalink
report
parent
reply
0 points

I am very confused here. You seem to have slipped from arguing that it was difficult and complicated to arguing that it’s bad to be able to share content remotely because it’s a felony, which seems like a pretty big leap.

For one thing, it’s not illegal and I do rip my own media. I will access it from my phone or my laptop remotely whenever I want, thank you very much.

For another, and this has been my question all along, how is it possibly more difficult and complicated to have remote access ready to go than being “a DNS record away”? Most end users don’t even know what a DNS is.

And yes, not having (obvious) server configurations up front is transparent. That’s what I’m saying. It does mix at least two sources (their unavoidable, rather intrusive free streaming TV stuff and your library), but it doesn’t demand that you set it up. The entire idea is to not have to worry about whether it’s local content. Like I said, there are edge cases where that can lead to a subpar experience (mainly when it’s downsampling your stuff to route it the long way around without telling you), but from a UX perspective I do get prioritizing serving you the content over warning you of networking issues.

I don’t know, man, I’m not saying you shouldn’t prefer Jellyfin. I wouldn’t know, I never used it long enough to have a particularly strong opinion. I just don’t get this approach where having the thing NOT surface a bunch of technical stuff up front reads as “complicated and difficult”. I just get hung up on that.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 6.2K

    Monthly active users

  • 3.9K

    Posts

  • 87K

    Comments