Tim

I don’t see the pitchfork mob making that distinction. (And I think you are severely underestimating the capability of, say, the qwen-3.5 models locally hosted with a good CLI agent like Mistral Vibe.)

Personally, I run them on my own hardware, and am trying to learn to use and supervise them appropriately. The things they are good for they are amazing at. And yeah, they are also often mendacious and unreliable with the possibility of going rogue - but no more than any junior developer or intern. If you can’t manage an AI, you can’t manage hires either - which for a hobbyist is just fine of course, but if you’re a professional it’s not a good look.

You either learn to ride the wave, or you let it drown you. Shaking your fists at the tsumani though is a sure fire route to involuntary early retirement.

You’re exactly right.

I started my career writing assembly code, by hand, for money; I did not throw my toys out of the cot when that ceased to be a particularly useful skill. I spent a great deal of my career rawdogging malloc(), but then managed runtimes came along… And I also didn’t quit because I didn’t like having training wheels forced on me. Because I understood that writing code was never my job, solving problems was and code was just one of the tools at my disposal to do so.

AI is another tool. It’s fantastically useful in the right pair of hands. Any developer who refuses to use it is simply going to be left behind - and that’s ok, because those people are not software engineers, they’re coders with a hobby - and I’d never expect to tell someone how to enjoy their hobby. But nobody should expect to be paid for it.

I ain’t reading all that… All I can say is, sync (both ways) with Keepass & Nextcloud on Android works just fine for me.

What’s the problem with Nextcloud? I use KeepassDX (on android, KeepassXC on desktop) with the database on Nextcloud and don’t have any problem syncing.

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.

I just realised this is the much more useful link: https://github.com/p-e-w/heretic?tab=readme-ov-file

I can see at least one -heretic version of a Qwen3.5 model on Huggingface already; can’t vouch for quality though.

Keep an eye on this: https://huggingface.co/heretic-org

I used to use a -heretic abliterated version of gpt-oss-120b, not for any creative reasons but just to reduce the amount of wasted tokens in its thinking, with good results.

(You can turn off thinking mode with the new Qwen models btw - how you do it will depend on how you’re hosting it, but basically it’s a flag to the chat template. It won’t remove the safety guidelines, but it will stop it telling you all about its internal monologue ;).)

Advanced Vector Extensions instruction set; introduced with Sandy Bridge in 2011, but not included in Pentium/Celeron branded processors even after then for reasons best known only to Intel.

Mongo is the application that has most irritated me by requiring it, but I doubt it’s the only one.

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