this post was submitted on 13 Mar 2026
31 points (94.3% liked)

Selfhosted

60693 readers
353 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
 

Joplin doesn't seem fully FOSS.
Logseq seems nice but I won't be able to hit it at notes.mydomain.works

What are good options? Ideally for keeping recipes and things

you are viewing a single comment's thread
view the rest of the comments
[–] timwa@lemmy.snowgoons.ro 3 points 4 months ago

find . -name LICENSE.md -print

There, arduous search complete.

I thought it was well known/understood that the server component was how Joplin pays their wages, and thus being under a different license is hardly a big shock; it's entirely optional, and the fact they're still sharing the source seems like a good thing rather than bad.

As for "they could just keep adding licenses!!!" Well, yeah, but so could any project. Apache could stick a proprietary license deep in a folder of httpd tomorrow and unless you were looking, you'd never know. Even a GPL project could incorporate a proprietary licensed component tomorrow provided it wasn't linked into the binary/was a separate piece of software - like, say, the server component of Joplin. You just trust that they won't, and/or properly check changes whenever you pull a new release like you were supposed to be doing anyway for security (hahaha, ok, no you weren't,) or trust that if they did pull shenanigans it would be 'news' and you would hear about it.

That Joplin is open about it, and they retain the original licenses of FOSS they have incorporated instead of deleting/hiding the original license is a good thing. I wish more did it.