Why are there no screenshots in the README.

Yes I know I can just install the app, but for an app that primarily seems to define itself by its UI improvements over the established competitor, the screenshots are the deciding factor in the question “Should I download and install this?”, and no screenshots defaults to “no”.

Real travel videos for niche places are so annoying to find now.

I’ve really been enjoying https://youtube.com/@ririregine

I mean, how can we feel superior if we are not wasting huge amounts of time setting things up!?

Why, by boasting that it’s so easy, just look at that, it is only two options you need to set thanks to the 80 custom modules I’ve written to abstract the abstractions from nixpkgs!

I WISH I could put an /s here, but I cannot.

Ehm… I’m also on Nixos and I’d say it’s super trivial.

services.openssh = {
  enable = true;
  settings = {
    PasswordAuthentication = false;
    PermitRootLogin = "no";
  };
};

users.users.<name>.openssh.authorizedKeys.keys = [ list of pubkeys ideally read from file in repo ];

Eh, the machine is actually in one of my wireguard nets anyways, but for different purposes.

The nice thing about SSH key-based access is, I either have the key and login succeeds, or I have no business trying to log in.

That’s why my remote root server bans via fail2ban after a single failed login.

Yes I’ve had to write support to get a KVM. Yes it’s still configured like this.

🤡

More scary than that is that the technologies are starting to keep up or exceed their expectations.

🤡 🤡 🤡

Oof, OK. I have seen some S1 Andor deep-dives in the past which were genuinely good. Haven’t watched anything on S2 yet, because I didn’t like it.

Which one? Mind sharing?

Huh, not what I would have expected. I work for a company that has sadly shifted very AI-focused, with the exception of the actual engineers. Literally none of us likes or uses LLMs. Every other week someone from the C-suite reminds us that we are encouraged to use it, and get 300$ or some such in credits for AI tooling per month, and that they don’t understand why it hasn’t been claimed even once.

I’m so torn on this, because IN THEORY the argument “git blame should show the dunce who committed this” makes sense.

But then why not add the AI as a co-committer.

(All of this of course sidesteps the actual question, “why the fuck are you allowing AI contributions in the first place”.)

Audiobookbay

LLMs will never be conscious.

Please tell me this is a satirical nod towards Honey & Co.

Past me had a dick

Sorry, couldn’t resist.

Recently, when we don’t feel like cooking after work, we’ve been making mashed potatoes (the pre-packaged, powder kind, because it’s WAY less work and surprisingly good), and then topping it with a big spoon of Laoganma, specifically the Crispy Chilly in Oil. Takes less than 5 minutes from geting the pot to sitting down to eat.

If you’re feeling extra fancy, fry an egg to put on top.

Eh… Not really. Qemu does a really good job with VM virtualizarion.

I believe I could easily build containers instead of VMs from the nix config, but I actually do like having a full VM: since it’s running a full OS instead of an app, all the usual nix tooling just works on it.

Also: In my day job, I actually have to deal quite a bit with containers (and kubernetes), and I just… don’t like it.

I’ll DM you… Not sire I want to link those two accounts publicly 😄

Zero.

About 35 NixOS VMs though, each running either a single service (e.g. Paperless) or a suite (Sonarr and so on plus NZBGet, VPN,…).

There’s additionally a couple of client VMs. All of those distribute over 3 Proxmox hosts accessing the same iSCSI target for VM storage.

SSL and WireGuard are terminated at a physical firewall box running OpnSense, so with very few exceptions, the VMs do not handle any complicated network setup.

A lot of those VMs have zero state, those that do have backup of just that state automated to the NAS (simply via rsync) and from there everything is backed up again through borg to an external storage box.

In the stateless case, deploying a new VM is a single command; in the stateful case, same command, wait for it to come up, SSH in (keys are part of the VM images), run restore-<whatever>.

On an average day, I spend 0 minutes managing the homelab.

You (sadly) need to group all quality profiles into a single one, and then handle quality through a custom format. Example from my setup: