this post was submitted on 19 Nov 2025
567 points (97.8% liked)

Selfhosted

61949 readers
988 users here now

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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. 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.

  8. 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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] rockstar1215@lemmy.world 10 points 9 months ago* (last edited 9 months ago) (1 children)

The article and discussion here is about open source software which is not free software. Thats where the problem lies it is assumed that open source software has be free.

Freedom in software does not mean free software.

[โ€“] elbarto777@lemmy.world 1 points 9 months ago

Thats where the problem lies it is assumed that open source software has be free.

But the article is not talking about this scenario. They're specifically talking about open source software that's also free software:

Your favorite apps run on code maintained by exhausted volunteers.

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.