• 0 Posts
  • 3 Comments
Joined 2 months ago
cake
Cake day: January 27th, 2026

help-circle
  • 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.



  • Just throwing this in here as another thing to consider - instruction set. From a quick check (so I’m happy to be told I’m wrong) the Celeron & Pentium options don’t support AVX. That means some stuff - and I’m giving a hard stare at MongoDB here, but there will be others - is not going to run, or at best you’re going to be either stuck with old versions or recompiling yourself from source.

    (I don’t know if any of your apps require Mongo or AVX, but I was bitten by this in the past and it was one of the main reasons I eventually upgraded one of my small clusters.)