Past me had a dick
Sorry, couldn’t resist.
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:



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.
Or TUI.


Lmao. Lmfao, even.
Here, I’m gonna save you some time and summarize the article for you:
Ahem. Maybe I editorialized a tiny bit. Not much though, trust me bro.


Nice, I was able to send an email to that.


That’s what I’m not so sure about though. Forgejo/codeberg/… projects are already not hard to find through search engines. Add a federated in-forgejo search and you’d be set there.
And currently the problem indeed is that a forgejo project is on instance X, and you, as a developer only have accounts on Y and Z. But through federation, that would stop mattering, so I don’t get the “it’s where contributors are”: as long as contributors have a single forgejo account anywhere, we’d be good.


No-one is forcing you to install Adobe software. Stop crying about other people liking choices.


Yep yep yep. I have forgejo accounts on so many instances (including on my own, 2-person instance which hosts all my personal shit). I’d love to be able to jump into discussions and open PRs on other people’s forges without needing a new account.
Forgejo in particular is just a fantastic forge. It’s surprisingly feature-rich, and so, so fast compared to GitHub, even on very lowspecced hardware. I honestly think that if federation is properly implemented, then in the long run, GitHub will become obsolete for FOSS projects.


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.


a number of these things are actual security exploits
yes, sure, but in the sense of “social engineering the slopbot”, not “there’s a vulnerability in [x] which does not apply proper sanitation to non-body text content before evaluating it”


Ah, makes sense. My mind was going more towards actual security exploits, but… yeah. Makes sense.
Anyways, thank you Flere-Imsaho, I will never not love seeing your username on here.


I’m apparently too out of coffee dumb to properly get the joke. What’s the implications if some system parses the PNG text chunks in the same way it does the body of the email?


Yeaaaaah I saw that on the schedule and decoded to not go, lol.
Please tell me this is a satirical nod towards Honey & Co.