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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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
This all still doesn't address the first thing I wrote:
Why can Jellyfin perform perfectly on the same hardware? Very snappy. It's obviously not the hardware's fault, but more a lack of optimization — and testing. If they tested/dogfed their app on WebOS at all, they'd know it's ass.
Edit: I just did a quick research on this in the Plex forums, and it seems like a lot of posts detail the same experience as mine: Plex used to work great until a year or more ago where it just turned into an unoptimized mess where even stepping left or right to a different poster, or button, has like a 1+ second lag.
It's very clear this is Plex's fault. It wasn't always like this.
Every single post is ignored by Plex and automatically closed due to inactivity (from Plex). They don't care.