So the 2024 elections in Moronia went as well as could be expected. The non-fascist minority tries to calm itself with the mantra that the most important thing now is to build community.
Sure. And once you have amassed more than, say, three people, get your heads out of your asses and collectively plan to get the fuck out while you still can. Mass deportations, internment camps, slashing any checks and balances, grooming generals as Hitler had, being a “dictator on day one” - that is just some of the shit that has been announced. You have 1930s Nazis with 2024 technology now. House and senate majorities are already lost. And there will be the equivalent to the Reichstag fire, count on it. Leave.
One of the upsides of running your own mail server is easy access to infinite mail addresses. I thus make it a habit to register a unique address with each service I use. Anyway, last week I received spam mails to an address that was only ever used for Unicef donations. I therefore assume that Unicef must have had some kind of data leak. I informed their technical contact a week ago and they responded with: Fuck all.
Those 18% of donations going into ads and administration are apparently insufficient to keep your private data confidential. Some donation data may have political implications (Привіт, товариші). Great job, guys.
I upgraded one of my systems from Debian Bullseye to Bookworm and it broke the font rendering. So far the best fix I have found is to create a font config to prefer the DejaVu family of fonts, as pointed out by Konomi here:
/etc/fonts/local.conf
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "urn:fontconfig:fonts.dtd" >
<fontconfig>
<alias>
<family>serif</family>
<prefer>
<family>DejaVu Serif</family>
</prefer>
</alias>
<alias>
<family>sans-serif</family>
<prefer>
<family>DejaVu Sans</family>
</prefer>
</alias>
<alias>
<family>monospace</family>
<prefer>
<family>DejaVu Sans Mono</family>
</prefer>
</alias>
</fontconfig>
…and then run fc-cache -r and reboot.
I migrated my git repos from my old server to my new one and used the opportunity to set up a Gitea instance while doing so. I guess it is more visually appealing than my old solution, which just dumped the master branch file tree to text files…
I still need to fix some paths inside the repos, particularly in the go.mod files. And then decide, if I want to use Gitea for release management.