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
But the article is not talking about this scenario. They're specifically talking about open source software that's also free software:
So it's perfectly fine for some users to expect the software to be free.
The real problem is that some project owners have a sense of duty to maintain their creations no matter what, leading to burnout, which is the point of the article. The article also details ways to fix it. Some of those involve the users being proactive (e.g. taking the initiative to donate consistently), but ultimately it's up to the owner to take some action. Like I mentioned, if I publish some code for free, I don't mind my users to expect that my software will always be free. But if they think I'm going to lose sleep trying to meet their demands without compensation, welp, they are dreaming.