No browser uses a different engine yet (presumably because Apple only allows them to offer this in the EU, under draconian conditions).

Hmm yeah, I guess the question is: is it overly complex if I do want to store my backup of my Nix config online, version-controlled, preferably publicly?

That’s neat!

Is that just because your four servers aren’t used for anything that need a secret? e.g. I wanted to put my wifi password in there, and the password for my user account.

How do you access the private Git repo then? Don’t you need a secret to access it?

Copy one file over and it’s set up for you.

So, I’ve only played around with NixOS on a Raspberry Pi, but… Don’t people usually split their config up in multiple files, and then store than in a Git repository?

The process then still is: check out that Git repository, except there’s another step: copy over your private key so that you can decrypt your secrets.

Is that correct? Or did I make things needlessly complex for myself?

Oh yeah I’m with you there. I think the project kinda grew beyond its initial goals, and now it’s hard to rename. Made more complex by GSConnect being by an independent developer from the KDE Connect team, I think. But the naming is confusing for sure.

Where are you installing KDE Connect? You only need it on your Android phone. On your computer, you only need the GSConnect extension.

There shouldn’t be the need to clear a name, because you shouldn’t be smearing someone’s name who’s giving away their work. It’s fine to distrust it, but then just don’t use the software.

Probably not what you’re after, but if it’s really just about PDFs, note that Firefox has an excellent PDF reader built-in. Oh, but I guess a browser extension can’t access that?

I’m not sure which button you’re talking about, but if it’s the one in the sidebar, click “Customise sidebar”, and then uncheck “AI chatbot”.

By now you would’ve expected someone to have pointed out what code is actually collecting that data that’s supposedly sold.

They’re saying they want something like Synaptic (mostly for its “multi-select”, apparently, though I’m not sure what that means?), but have it support AppImages, Flatpaks, Snaps, etc., instead of just Debs like Synaptic does.

Can I just say: hats off to the bug archaeology you’ve done there :)

Heh yes, but for the purposes of this post I wanted to focus on why it wasn’t just another distro recommendation, but one tailored specific to their use case :) (I don’t even use Kinoite myself, so it’s extra genuine.)

If you do a reinstall, I’d recommend going with a Kinoite install. It’s like regular Fedora KDE, except that it avoids this risk of traces of past experiments everywhere.

thelibre.news is woefully underappreciated.

Ha, well, if my single-digit-downloads (all by me) NPM module is influential enough to set precedent, then I’d consider that a success.

Yeah I get that point, and so my point is that if the use case is important enough that they’d be able to justify allocating that personnel, I use the AGPL to give them that nudge. When it’s just some non-critical component, then I’ll just slap an MIT on it and be done with it.

My rule-of-thumb is: is the licence going to make things better for users? In other words, I try to predict whether a company would just not use my AGPL-licensed code, or would potentially contribute back. If they wouldn’t, I don’t really care and rather my code at least gets used to build something presumably useful.