- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
We are also changing how remote playback works for streaming personal media (that is, playback when not on the same local network as the server). The reality is that we need more resources to continue putting forth the best personal media experience, and as a result, we will no longer offer remote playback as a free feature. This—alongside the new Plex Pass pricing—will help provide those resources. This change will apply to the future release of our new Plex experience for mobile and other platforms.
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 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.
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.
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
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
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
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