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
If I were a dev, that would be the number one reason I would not publish any app I created. The constant demands from users, the constant integrations, et al, nah...pass. I am grateful for who do, but that's just not my bag.
I think I'm going to put a declarations.md that says something like "I made this for me, but I'm sharing it with the world. If you find it useful, use it and let me know! If you find issues, submit request and I'll look but no promises. And if you want feature X ... fork it and build it. The code's yours, with my blessings. PS: I don't accept PRs, sorry".
I code for fun; I'm not looking for a third unpaid job. That's what parenting is for.
That would be a way to do it. Here it is, works on my machine, it you feel you can use it, knock yourselves out. 30 minute, 30 mile guarantee.
Well, that's a full time job right there. I wish you the very best of luck in those endeavors. You'll need it.
He specifically goes on to say it's primarily from dealing with anti-AI backlash in response to his use of Claude to help (solely) maintain the client: https://github.com/andrewrabert/jellium-desktop/issues/609
One could also not feel obligated to address all requests and just let anyone fork the project.
Isn't it a bit about the ego to keep running the project while it's too much to handle?
You can keep running the project and invite people wishing for an XYZ integration to open a pull request. The collaborative nature is kind of a big point of open source imo.
oh absolutely. I only meant in case it's physically too much for the repo owner.
There's no need to feel obligated to carry on to one's own detriment. The community knows how to move on with it, e.g. ownership transfer or a fork.
Didn't downvote ya but, yeah I guess I could do that if I were a dev. Also, I would personally feel responsible for someone's loss or havoc caused my my app.
Which is one of the reasons I'll never implement the delete function in the Jellyfin for Roku client.
Sure, I'm assuming the project has a stable version and a warning or archived banner clearly advertised 😉