Selfhosted
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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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!
view the rest of the comments
TL; DR: UX, UI, and memory.
Memory usage is a significant concern. It immediately made my NAS completely crash when attempting to scan the (not even very large) library. Plex, right now, as of writing, when idle, uses 30MB, compared to the 3.1GB reported by Jellyfin when I last tried it, which was the last reading before my NAS died a tragic death of RAM starvation.
The apps are bad. A browser isn’t a good solution - see HDR, 10bit, 5.1, Atmos, and bit-perfect support. Remote access is complex, particularly for those behind CG-NAT, and encryption for remote access is even more convoluted; Plex does it in one checkbox. Some of that is architectural, some financial, but the end result is a worse experience for me.
The UI design is such that any server slowdown affects responsiveness severely, even for simple actions, which unfortunately speaks volumes about how much of a priority the actual user experience is - that’s not something I’m compatible with as a person in general.
Third-party apps are not good either for my platforms, I deemed them to be unusable unstable and amusingly poorly designed - that’s including the Swift and Flutter versions, the latter of which’s design and UX I found incredibly obtuse. Stretching a phone app for desktop use feels a bit like stretching your ballsack into a wind sail - maybe just get a sail mate.
I genuinely wanted to like Jellyfin, I hate proprietary software, let alone paid software, LET ALONE paid piracy software. But JF still has so many areas like these that are just incredibly frustrating to deal with. Plex’s dogshit decisions are not impacting me much (Lifetime), I have established custom setups around the desktop Plex clients to make them usable, so I see no immediate reason to switch until Jellyfin addresses its memory usage and considers using a non-skid language for an application that’s essentially a file server, set of ffmpeg scripts and a metadata database.
Thank you for providing a possible answer for why my Jellyfin server is such a memory hog. It eats up memory and CPU even while idling and grinds all of my other services to a crawl if I let it