And yet, today, Taiwan is a sovereign state and wants to keep it that way, which is the only thing that matters here. This is pretty straightforward.

Yeah, and Steins;Gate 0 rated higher than the original… What?

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.

NixOS for the win! Define your system and services, run a single command, get a reproducible, Proxmox-compatible VM out of it. Nixpkgs has basically every service you’d ever want to selfhost.

Lost me at LLMs. My Nix config is over 20k lines long at this point, neatly split into more than a hundred modules and managing 8 physical machines and 30+ VMs. I love it.

But every time I’ve tried to use an LLM for nix, it has failed spectacularly.

Sorry, unfortunately can’t help you there. My matrix server is not federated, I remember back then I created an account on matrix.org specifically to read these. But maybe they got deleted in the meantime?

Anyways, I have been really happy with continuwuity, to the point that up until now, I haven’t even looked at tuwunel again. The maintainers of continuwuity seem really nice and engaged, and both from a usage and stability point of view, as well as for the actually surprisingly fast release cycle, I have no complaints. I found and fixed a bug a couple weeks ago, and the dev process was also very friendly and relaxed.

In short: while I don’t know how things are on the tuwunel side, I’m very happy to have gone with continuwuity and have high hopes for the future of the project.

Let’s hope the same thing will happen if/when the US tries to take Greenland; but honestly, I’m not optimistic. At least here in Germany, politicians and businesses are so used to licking the US’ boot that I have a hard time imagining a seismic shift. Not to mention that thanks to our dependence on US software, we’re incredibly vulnerable.

Still. One can hope.

FWIW, I’ve been using Music Assistant with my Sonos speakers without issue.

HOWEVER, I’m using MA as part of Home Assistant, and have the speakers configured through HA, not MA. MA just sees the speakers as HA Media Players. That works really well.

Almost 9k lunes of python in a bash script. Lmao. No.

Removed by mod

Oh, sorry, I did not mean to imply that there re no players (there are, e.g. Finamp), just nowhere near the same level of polish, features and stability.

Jellyfin doesn’t have something comparable in the dedicated (OSS) world, but Symfonium takes a Jellyfin connection and is hands down the single best music player I have ever encountered on any platform.

Tastes like LLM to me

Why?

Sorry to be a pendantic ass. But. Jellyfin, in and on itself, has absolutely nothing to do with docker.

Planning to host a Nix caching server, and have CI build all package and NixOS outputs on every push to git, then in turn pushing the output artifacts to the cache. Would save me a good chunk of time when tinkering with VMs that haven’t seen manual updates in a while.

Only thing is, I’m not sure how to approach building and caching NixOS configs that receive agenix secrets in their input. Obviously those should not be cached…

About the same here, though I have to say… Reading the “3 hours per day” part out loud still seems… Insane somehow.

In a similar vein, I’m currently staying at my mom’s house, and the internet is too shit to use my Jellyfin. As a result, I haven’t been watching any shows, and my day seems to be infinitely longer, like a million more activities fit in the sake 24 hours.

Yes, and I do werether the recipient also knows how to use it.

So, for like, 1% of my mails.