934
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Mar 2025
934 points (100.0% liked)
Selfhosted
44652 readers
2666 users here now
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
As a result I imagine more users will look at other offerings such as Jellyfin.
https://github.com/jellyfin/jellyfin
https://jellyfin.org/
This might be what it takes to at least get me to install it.
Do they live well together with the same shared media library?
Also, are there audiobook clients for Jellyfin?
I found audiobooks to be kind of awkward on jellyfin. I'm now running Audiobookshelf for all my audiobooks, radio shows and podcasts. Together with the Lissen app on Android, it works very nicely!
And what about just plain music? Is Jellyfin or Audiobookshelf better suited for that?
For music, I selfhost navidrome. Works nicely with the Tempo app on android, or Feishin on desktop.
I also recommend audio bookshelf but am using ShelfPlayer on iOS
I've heard rumors that they do play well together, but that's people running it in docker with a "read-only" flag set for the content folder, with metadata saved in the config folder
I've used the Jellyfin app to listen to audio books, but for my purposes, it's easier to run the separate client/server Audiobookshelf.
Makes sense. I’m fully dockerized so I’ve got that going for me
I'm fully Dockerized (well, uhh... Podmanized) and I'm dual-wielding Plex and Jellyfin. Runs smoothly and both only have read to the content. All management of the media is handled by the *arr stack anyway. I even set up a volume for Plex to throw conversions into that Jellyfin can't see. I'm currently personally using Jellyfin and I'm waiting for Jellyfin to be good enough (or Plex bad enough...) for the users I share with to switch over.
I can definitely recommend that setup.
I've had Plex and Emby (what Jellyfin was forked from) running alongside one a other for years now on Windows with zero issues. They shouldn't have any effect on one another.
My Jellyfin and Plex containers were able to use the same locations for media.
I installed Plex before learning I'd have to pay for any of the functionality I was looking for. Installed Jellyfin and used the Plex folders lol
I've had Jellyfin and Plex running using the same media directory for a couple years now. I think I had to make a couple small changes for things like seasons of a TV show to show up correctly, but nothing incredibly difficult. Definitely worth setting up and playing with periodically so when you do finally get sick of Plex, you're ready to just switch.
Only thing I use Plex for exclusively now is when I'm flying, Plex has the Netflix style download option and Jellyfin just downloads the video file. I like Plex's way better just from personal preference.
I haven't used Plex myself but Jellyfin doesn't create any kind of meta files in the library folders. If that is true for Plex as well then I don't see why it would be a problem to point them at the same shared library.
My experience is that both Plex and Jellyfin pointed at the same media files causes no issues.
Plex stores its metadata in a special folder, and I’ve got the *arr stack managing the actual media files, so I think I can run them in parallel.
Looks like I’ve got a project for the weekend! Jebediah’s just gonna have to wait to go to Jool.
Of you use docker plex and jellyfin arent gonna be messing with your media unless you delete/modify them within the respective clients (but then again thats what *arr is for)
I didn't enjoy using Jellyfin for audiobooks, on my android I use the Jellyfin client to download the book I wanna listen to and then I use AudioAnchor for listening to it.
https://emby.media/
They too put a whole lot behind their subscription though
https://emby.media/support/articles/Premiere-Feature-Matrix.html
I bought a lifetime sub, now I don't have to pay anything
FUCK Emby! What they did was worse than what Plex is doing even now
Another user said that was because users were modifying the code to avoid supporting the project? I got a lifetime subscription relatively inexpensive and haven't had trouble
Who said that? I did a search in the thread and no Ody said anything about that that I saw
https://lemmy.world/comment/15803065
So the issue is kind of similar to bitwarden; how to protect the premium bits when having an open source core?
They just didn't handle it as gracefully.
https://www.theregister.com/2024/11/04/bitwarden_gpls_password_manager/
Here's the history regarding emby if you're curious:
https://github.com/nvllsvm/emby-unlocked
https://web.archive.org/web/20190327090553/https://emby.media/community/index.php?/topic/49862-source-code-license/#entry483544
https://web.archive.org/web/20181225073326/https://github.com/MediaBrowser/Emby/issues/3075#issuecomment-408600161
What did they do?
Basically, slammed the source code door shut after making promissory statements like "Don't worry, we'll always be open source" for years. With little/no notice they relicensed everything and pivoted to a closed source paywall model.
No discussion with the community or contributors, no alternatives explored, no polls or surveys. Just woke up one day to a "Sorry, but we're going closed source because moneyyyy" blog post
Jellyfin was born right after, forked out of vengeance.
In retrospect we should have seen it coming when they would do odd little things, like keeping the build scripts closed source n crap, but eh hindsight and all that lol