<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>J-Cave.dk</title><link>https://j-cave.dk/</link><description>Recent posts on J-Cave.dk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 30 Oct 2026 08:44:00 +0100</lastBuildDate><atom:link href="https://j-cave.dk/index.xml" rel="self" type="application/rss+xml"/><item><title>My hypervisors in 2026: phoebe, priscilla and stephen</title><link>https://j-cave.dk/my-hypervisors-in-2026-phoebe-priscilla-and-stephen/</link><pubDate>Fri, 30 Oct 2026 08:44:00 +0100</pubDate><guid>https://j-cave.dk/my-hypervisors-in-2026-phoebe-priscilla-and-stephen/</guid><description>&lt;p&gt;The last two parts of this series were about getting here: a &lt;a href="https://j-cave.dk/new-proxmox-homeserver/"&gt;new Proxmox server&lt;/a&gt;, and the &lt;a href="https://j-cave.dk/hyperconverged-hypervisor/"&gt;one big box&lt;/a&gt; I would build if I could. This part is about what I actually have. Three machines, what each one is for, and how they are going to work together.&lt;/p&gt;
&lt;h2 id="from-one-big-server-to-three-small-ones"&gt;From one big server to three small ones&lt;/h2&gt;
&lt;p&gt;This series started with an HP ProLiant ML150 G6 from 2009 and the &lt;a href="https://j-cave.dk/time-to-upgrade-the-hp-smartarray-p410/"&gt;Smart Array controller&lt;/a&gt; I put in it. Two years ago I &lt;a href="https://j-cave.dk/setup-2024-taking-stock-of-my-servers/"&gt;took stock&lt;/a&gt; of what I had. The ML150 has since been retired and is gone.&lt;/p&gt;</description></item><item><title>Setting up an LXC container in Proxmox</title><link>https://j-cave.dk/setting-up-an-lxc-container-in-proxmox/</link><pubDate>Wed, 28 Oct 2026 08:17:00 +0100</pubDate><guid>https://j-cave.dk/setting-up-an-lxc-container-in-proxmox/</guid><description>&lt;p&gt;This is the third part of &lt;em&gt;Proxmox from scratch&lt;/em&gt;. In &lt;a href="https://j-cave.dk/setting-up-a-virtual-machine-in-proxmox/"&gt;part 2&lt;/a&gt; we created a virtual machine. This time we make the other kind of guest, a container, and I show how I run my own services in them.&lt;/p&gt;
&lt;p&gt;The container in this post is a real one: the one that will run Jellyfin on my main server, phoebe, in the coming &lt;em&gt;Jellyfin at home&lt;/em&gt; series. The screenshots are from the evening I created it.&lt;/p&gt;</description></item><item><title>Site Update October 2026</title><link>https://j-cave.dk/site-update-october-2026/</link><pubDate>Mon, 26 Oct 2026 08:00:00 +0100</pubDate><guid>https://j-cave.dk/site-update-october-2026/</guid><description>&lt;h2 id="a-month-of-finding-your-way-around"&gt;A month of finding your way around&lt;/h2&gt;
&lt;p&gt;The September update was about the new look. This month the work went
into the structure underneath it: how posts are grouped, how you get
from one to the next, and how a post page uses the screen. And, at last,
into writing posts: twelve went online in October, and fifteen since the
last week of September. Two series got going: &lt;em&gt;Proxmox from scratch&lt;/em&gt;
started, and &lt;em&gt;My home servers&lt;/em&gt; picked up again after a long pause.&lt;/p&gt;</description></item><item><title>Hyperconverged Hypervisor</title><link>https://j-cave.dk/hyperconverged-hypervisor/</link><pubDate>Fri, 23 Oct 2026 08:17:00 +0200</pubDate><guid>https://j-cave.dk/hyperconverged-hypervisor/</guid><description>&lt;p&gt;Having a homeserver lets you host your own services. There are a lot of
ways to do this. This post explains what a hyperconverged hypervisor
is, why I want one, and why I don&amp;rsquo;t have one yet.&lt;/p&gt;
&lt;p&gt;I do not have the luxury of buying new specific hardware that fits the
jobs I am looking to solve. I often have to make do with 2nd (or even
3rd) hand hardware to be able to have the systems that run both my
business as well as protect our personal data such as photos and
important documents.&lt;/p&gt;</description></item><item><title>Setting up a Virtual Machine in Proxmox</title><link>https://j-cave.dk/setting-up-a-virtual-machine-in-proxmox/</link><pubDate>Thu, 22 Oct 2026 14:40:00 +0200</pubDate><guid>https://j-cave.dk/setting-up-a-virtual-machine-in-proxmox/</guid><description>&lt;p&gt;This is the second part of &lt;em&gt;Proxmox from scratch&lt;/em&gt;. In &lt;a href="https://j-cave.dk/setting-up-a-proxmox-virtual-environment-server/"&gt;part 1&lt;/a&gt; we installed Proxmox VE on a small PC. Now we put it to use and create the first virtual machine.&lt;/p&gt;
&lt;p&gt;A virtual machine, or VM, is a whole computer made of software. It has its own virtual disk, memory, processor and network card, and you install an operating system in it the same way you would on a real PC. That makes it the right place for things you don&amp;rsquo;t want on your own PC, like a test build of a desktop that may well have bugs. That is what I install in mine: the testing edition of KDE neon. I chose it on purpose, because it lets me try the coming Plasma releases before they come out, without risking the desktop I use every day.&lt;/p&gt;</description></item><item><title>MD-102 Old vs New Exam</title><link>https://j-cave.dk/md-102-old-vs-new-exam/</link><pubDate>Mon, 19 Oct 2026 08:56:00 +0200</pubDate><guid>https://j-cave.dk/md-102-old-vs-new-exam/</guid><description>&lt;h1 id="md-102-endpoint-administrator-replaces-md-100--md-101"&gt;MD-102 Endpoint Administrator replaces MD-100 + MD-101&lt;/h1&gt;
&lt;p&gt;As Microsoft has been moving away from on-prem tools like SCCM and Domain Controllers to cloud they introduced a new exam to reflect this change towards the cloud and tools like Intune, Entra, and Autopilot. And for the new Endpoint Manager that also meant a new certification to replace the old MD-100 Windows Client, and MD-101 Managing Modern Desktops.&lt;/p&gt;
&lt;p&gt;As a budding Systems Administrator, MD-102 Endpoint Administrator is a good way of learning about modern Endpoint Management and protection, as well as document my knowledge. But how much of the old ways should I also learn?&lt;/p&gt;</description></item><item><title>New Proxmox homeserver</title><link>https://j-cave.dk/new-proxmox-homeserver/</link><pubDate>Fri, 16 Oct 2026 08:36:00 +0200</pubDate><guid>https://j-cave.dk/new-proxmox-homeserver/</guid><description>&lt;h2 id="my-current-proxmox-server"&gt;My current Proxmox server&lt;/h2&gt;
&lt;p&gt;My main Proxmox server is called phoebe. It is a Lenovo Tiny PC with an AMD Ryzen 5 PRO 3400GE processor and 64 GB of RAM, and it runs a couple of LXC containers (Nextcloud among them) and a few virtual machines.&lt;/p&gt;
&lt;p&gt;Its storage used to be an NVMe drive for booting and two spinning drives in an OpenZFS mirror: a 4 TB 2.5&amp;quot; hard disk drive inside the case and an 8 TB external drive connected via USB 3. That gave 4 TB of usable space, as the smallest drive in a mirror dictates the capacity.&lt;/p&gt;</description></item><item><title>Homelab backup strategy: 3-2-1 in practice, not just in theory</title><link>https://j-cave.dk/homelab-backup-strategy-3-2-1-in-practice-not-just-in-theory/</link><pubDate>Wed, 14 Oct 2026 08:10:00 +0200</pubDate><guid>https://j-cave.dk/homelab-backup-strategy-3-2-1-in-practice-not-just-in-theory/</guid><description>&lt;p&gt;Most posts about backup explain the 3-2-1 rule and then show a setup that follows it. I can&amp;rsquo;t write that post yet. What I can do is go through the rule, hold my own homelab up against it, and show where it falls short today.&lt;/p&gt;
&lt;h2 id="the-3-2-1-rule-briefly"&gt;The 3-2-1 rule, briefly&lt;/h2&gt;
&lt;p&gt;Backblaze puts the rule in one sentence: &amp;ldquo;keep three copies of your data on two different media with one copy off-site&amp;rdquo; &lt;a href="#sources"&gt;[1]&lt;/a&gt;. The three copies include the original, so it is the data you work on plus two more &lt;a href="#sources"&gt;[1]&lt;/a&gt;. &amp;ldquo;Two different media&amp;rdquo; comes from the time of tape and CDs. Today Backblaze reads it as two different devices &lt;a href="#sources"&gt;[1]&lt;/a&gt;. Off-site means a place that a fire, a burglary or a lightning strike at home doesn&amp;rsquo;t reach.&lt;/p&gt;</description></item><item><title>October 2026 for Microsoft admins: what changed on the 1st, and what ends on Patch Tuesday</title><link>https://j-cave.dk/october-2026-for-microsoft-admins-what-changed-on-the-1st-and-what-ends-on-patch-tuesday/</link><pubDate>Mon, 12 Oct 2026 08:00:00 +0200</pubDate><guid>https://j-cave.dk/october-2026-for-microsoft-admins-what-changed-on-the-1st-and-what-ends-on-patch-tuesday/</guid><description>&lt;div class="callout my-6 rounded-xl border border-charcoal-soft/25 bg-charcoal-soft/5 p-4"&gt;
 &lt;p class="font-semibold text-sm mb-1 text-charcoal-soft"&gt;Note&lt;/p&gt;
 &lt;div class="text-sm leading-relaxed text-charcoal-soft [&amp;_a]:text-accent [&amp;_a:hover]:underline [&amp;_p]:m-0"&gt;
 &lt;strong&gt;Updated 13 October 2026, after the release.&lt;/strong&gt; This post went out the day before Patch Tuesday. It now says what actually shipped: 1,411 fixes, one of them for a flaw that is already being used in attacks, and one known issue with USB audio. The other sections are brought up to date as well.
 &lt;/div&gt;
&lt;/div&gt;


&lt;p&gt;Patch Tuesday was on 13 October, and this one was more than a batch of
fixes. Several products got their last update on the same day, three
things had already changed on 1 October, and a Secure Boot certificate
expires six days later. Here is the month as a list, with what to check
for each.&lt;/p&gt;</description></item><item><title>Windows 11 24H2 gets its last update on 13 October, and Windows 10 gets another year</title><link>https://j-cave.dk/windows-11-24h2-gets-its-last-update-on-13-october-and-windows-10-gets-another-year/</link><pubDate>Fri, 09 Oct 2026 08:00:00 +0200</pubDate><guid>https://j-cave.dk/windows-11-24h2-gets-its-last-update-on-13-october-and-windows-10-gets-another-year/</guid><description>&lt;p&gt;Two Windows dates have been mixed together in a lot of headlines this
autumn, so here they are, separated.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Windows 11, version 24H2&lt;/strong&gt;, Home and Pro: the last update comes on
Tuesday 13 October 2026 &lt;a href="#sources"&gt;[1]&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Windows 10&lt;/strong&gt;: nothing ends this month. The extended security updates
for home users, which were supposed to stop now, run until 12 October
2027 &lt;a href="#sources"&gt;[2]&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="windows-11-24h2-update-to-a-newer-version"&gt;Windows 11 24H2: update to a newer version&lt;/h2&gt;
&lt;p&gt;Each yearly version of Windows 11 is only maintained for a limited
time. For Home and Pro that is two years, and 24H2 came out on
1 October 2024 &lt;a href="#sources"&gt;[1]&lt;/a&gt;. After 13 October, a PC that is still on
24H2 gets no more security fixes.&lt;/p&gt;</description></item><item><title>Office 2021 support ends on 13 October: what are your options?</title><link>https://j-cave.dk/office-2021-support-ends-on-13-october-what-are-your-options/</link><pubDate>Thu, 08 Oct 2026 08:00:00 +0200</pubDate><guid>https://j-cave.dk/office-2021-support-ends-on-13-october-what-are-your-options/</guid><description>&lt;p&gt;On Tuesday 13 October 2026, Office 2021 gets its last update. That goes
for the version you bought in a shop and for Office LTSC 2021, the
version organisations buy through volume licensing
&lt;a href="#sources"&gt;[1]&lt;/a&gt; &lt;a href="#sources"&gt;[2]&lt;/a&gt;. Microsoft leaves no opening: &amp;ldquo;there
will be no extension and no extended security updates&amp;rdquo; &lt;a href="#sources"&gt;[1]&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="what-end-of-support-means"&gt;What end of support means&lt;/h2&gt;
&lt;p&gt;Word and Excel will start on 14 October exactly as they did the day
before. &amp;ldquo;All of your Office 2021 apps may continue to function. However,
you could expose yourself to serious and potentially harmful security
risks.&amp;rdquo; &lt;a href="#sources"&gt;[1]&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Setting up a Proxmox Virtual Environment server</title><link>https://j-cave.dk/setting-up-a-proxmox-virtual-environment-server/</link><pubDate>Wed, 07 Oct 2026 08:18:00 +0200</pubDate><guid>https://j-cave.dk/setting-up-a-proxmox-virtual-environment-server/</guid><description>&lt;p&gt;This is the first part of &lt;em&gt;Proxmox from scratch&lt;/em&gt;. By the end of it you
have a server running Proxmox Virtual Environment, reachable from a
browser and up to date. The following parts build on it: virtual
machines, containers, storage, networking and backups.&lt;/p&gt;
&lt;p&gt;Everything here is done on Proxmox VE 9.2, which came out in May 2026
&lt;a href="#sources"&gt;[7]&lt;/a&gt;. If you find an older guide for version 8, be aware that
8 stopped getting security updates on 31 August 2026 &lt;a href="#sources"&gt;[7]&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>What's new in Jellyfin 12, and what to check before you upgrade</title><link>https://j-cave.dk/whats-new-in-jellyfin-12-and-what-to-check-before-you-upgrade/</link><pubDate>Mon, 05 Oct 2026 08:18:00 +0200</pubDate><guid>https://j-cave.dk/whats-new-in-jellyfin-12-and-what-to-check-before-you-upgrade/</guid><description>&lt;p&gt;Jellyfin 12.0 came out on 7 September, and the first bugfix release,
12.1, followed a week later &lt;a href="#sources"&gt;[1]&lt;/a&gt; &lt;a href="#sources"&gt;[3]&lt;/a&gt;. If you run
10.11 today, the next version is not 10.12 and not 11. It is 12. Here is
what is new, what breaks, and what to do before you press upgrade.&lt;/p&gt;
&lt;h2 id="from-1011-to-12"&gt;From 10.11 to 12&lt;/h2&gt;
&lt;p&gt;The number first, and a little history, because the obvious question is
why a project that began in 2018 was on version 10 at all. Jellyfin
started &amp;ldquo;in early December 2018 primarily as a result of Emby&amp;rsquo;s decision
to take their next release (4.x) closed-source&amp;rdquo;, as a fork of Emby 3.5.2
&lt;a href="#sources"&gt;[6]&lt;/a&gt;. The new project wanted a clean break from Emby&amp;rsquo;s
version numbers, and chose to go up rather than down. The first Jellyfin
release, in January 2019, was 10.0.0, and the plan was &amp;ldquo;10.X.Y, with X
being major feature releases and Y being bugfixes&amp;rdquo; &lt;a href="#sources"&gt;[7]&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Teams and Copilot are moving to cloud.microsoft: check your allow-lists before October</title><link>https://j-cave.dk/teams-and-copilot-are-moving-to-cloud-microsoft/</link><pubDate>Fri, 02 Oct 2026 08:47:00 +0200</pubDate><guid>https://j-cave.dk/teams-and-copilot-are-moving-to-cloud-microsoft/</guid><description>&lt;p&gt;Two of the most used Microsoft 365 web addresses are changing this
autumn. Copilot is moving to &lt;code&gt;copilot.cloud.microsoft&lt;/code&gt; and Teams on the
web to &lt;code&gt;teams.cloud.microsoft&lt;/code&gt;. If something in your network blocks
&lt;code&gt;*.cloud.microsoft&lt;/code&gt;, October is when your users find out.&lt;/p&gt;
&lt;h2 id="whats-changing"&gt;What&amp;rsquo;s changing&lt;/h2&gt;
&lt;h3 id="copilot-m365cloudmicrosoft-becomes-copilotcloudmicrosoft"&gt;Copilot: m365.cloud.microsoft becomes copilot.cloud.microsoft&lt;/h3&gt;
&lt;p&gt;In message center post MC1462915 Microsoft says it started redirecting
users from &lt;code&gt;m365.cloud.microsoft&lt;/code&gt; to &lt;code&gt;copilot.cloud.microsoft&lt;/code&gt; in early
September, in organisations where the new address is reachable. Everyone
else gets redirected in early October &lt;a href="#sources"&gt;[1]&lt;/a&gt;. If the address is
blocked, the redirect happens anyway, and &amp;ldquo;affected users may be unable
to use Copilot in the web app, desktop app, and Microsoft Edge
experience&amp;rdquo; &lt;a href="#sources"&gt;[1]&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Torvalds joked about blaming AI for Linux 7.3-rc2 — what actually happened</title><link>https://j-cave.dk/torvalds-joked-about-blaming-ai-for-linux-7.3-rc2-what-actually-happened/</link><pubDate>Fri, 02 Oct 2026 07:32:00 +0200</pubDate><guid>https://j-cave.dk/torvalds-joked-about-blaming-ai-for-linux-7.3-rc2-what-actually-happened/</guid><description>&lt;h2 id="the-joke-well-obviously-all-blame-it-on-ai"&gt;The joke: &amp;ldquo;We&amp;rsquo;ll obviously all blame it on AI&amp;rdquo;&lt;/h2&gt;
&lt;p&gt;Linux 7.3-rc2 came out on Sunday 6 September, and Linus Torvalds ended
the announcement with this: &amp;ldquo;It might be just random, but we&amp;rsquo;ll
obviously all blame it on AI, because whether that&amp;rsquo;s really the cause or
not, it&amp;rsquo;s an easy thing to blame ;)&amp;rdquo; &lt;a href="#sources"&gt;[1]&lt;/a&gt;. That line made the
headlines &lt;a href="#sources"&gt;[2]&lt;/a&gt;. The rest of the email, where he lists what
actually made the release big, got far less attention &lt;a href="#sources"&gt;[3]&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>What's new in Nextcloud 35 (Hub 26 Summer), and what's next in 36</title><link>https://j-cave.dk/whats-new-in-nextcloud-35-hub-26-summer-and-whats-next-in-36/</link><pubDate>Wed, 30 Sep 2026 08:25:00 +0200</pubDate><guid>https://j-cave.dk/whats-new-in-nextcloud-35-hub-26-summer-and-whats-next-in-36/</guid><description>&lt;p&gt;&lt;em&gt;Cover image: Nextcloud GmbH, from the &lt;a href="https://nextcloud.com/blog/press_releases/hub-26-summer/"&gt;Nextcloud Hub 26 Summer press release&lt;/a&gt; (see also the &lt;a href="https://nextcloud.com/press/"&gt;Nextcloud press page&lt;/a&gt;).&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="a-short-history-of-nextcloud"&gt;A short history of Nextcloud&lt;/h2&gt;
&lt;p&gt;For those of you new to self-hosting and Nextcloud itself, I would like to start this post off with a quick introduction to Nextcloud.&lt;/p&gt;
&lt;p&gt;Nextcloud is a way of hosting your own files for yourself and a team similar to what OneDrive and SharePoint do in a Microsoft 365 environment, but without the intranet capability of SharePoint.&lt;/p&gt;</description></item><item><title>September 2026 Patch Tuesday broke Excel: the case for ring-based deployment</title><link>https://j-cave.dk/september-2026-patch-tuesday-broke-excel-the-case-for-ring-based-deployment/</link><pubDate>Mon, 28 Sep 2026 08:12:00 +0200</pubDate><guid>https://j-cave.dk/september-2026-patch-tuesday-broke-excel-the-case-for-ring-based-deployment/</guid><description>&lt;p&gt;September&amp;rsquo;s Patch Tuesday was the biggest Microsoft has ever shipped, and
one of the updates in it broke copy and paste in Excel. Together they
make a good argument for something small IT departments often skip:
letting a few people get the updates first.&lt;/p&gt;
&lt;h2 id="what-shipped-on-8-september-2026"&gt;What shipped on 8 September 2026&lt;/h2&gt;
&lt;h3 id="a-record-count-however-you-count-it"&gt;A record count, however you count it&lt;/h3&gt;
&lt;p&gt;How big depends on who you ask. BleepingComputer counted 966
vulnerabilities &lt;a href="#sources"&gt;[1]&lt;/a&gt;, Tenable 964 &lt;a href="#sources"&gt;[2]&lt;/a&gt;, the Zero
Day Initiative 972 new Microsoft CVEs &lt;a href="#sources"&gt;[3]&lt;/a&gt; and SecurityWeek
974 &lt;a href="#sources"&gt;[4]&lt;/a&gt;. When I first noted the idea for this post I wrote
down 973, which is roughly what you get from reading enough headlines.&lt;/p&gt;</description></item><item><title>Site Update September 2026</title><link>https://j-cave.dk/site-update-september-2026/</link><pubDate>Thu, 24 Sep 2026 16:25:00 +0200</pubDate><guid>https://j-cave.dk/site-update-september-2026/</guid><description>&lt;h2 id="a-month-of-rebuilding"&gt;A month of rebuilding&lt;/h2&gt;
&lt;p&gt;In the August update I promised that the site would be redesigned as we
went. A month later, most of that list is done, and the site looks and
works quite differently. Here&amp;rsquo;s what changed, and what&amp;rsquo;s coming.&lt;/p&gt;
&lt;h2 id="a-new-look"&gt;A new look&lt;/h2&gt;
&lt;p&gt;The minimalistic look from early August is gone. The site now has its
own colour scheme: a dark charcoal frame around a warm parchment reading
area, with terracotta and pine green as accent colours, and a serif font
for headings.&lt;/p&gt;</description></item><item><title>Homelab Handbook: Getting Started is now available</title><link>https://j-cave.dk/homelab-handbook-getting-started-is-now-available/</link><pubDate>Wed, 23 Sep 2026 18:35:00 +0200</pubDate><guid>https://j-cave.dk/homelab-handbook-getting-started-is-now-available/</guid><description>&lt;p&gt;My first guide is out. &lt;strong&gt;Homelab Handbook: Getting Started&lt;/strong&gt; is a
practical, no-nonsense handbook for turning an affordable used PC into
your first homelab, and it&amp;rsquo;s available now from the Kaddu Systems shop.&lt;/p&gt;
&lt;h2 id="what-it-is-and-who-its-for"&gt;What it is and who it&amp;rsquo;s for&lt;/h2&gt;
&lt;p&gt;A homelab is simply a computer (or a few) that you run at home to host
services you&amp;rsquo;d otherwise pay someone else for, or hand your data to.&lt;/p&gt;
&lt;p&gt;It can also be a playground where you can experiment and learn new skills, without affecting your production systems and important data.&lt;/p&gt;</description></item><item><title>Site Update August 2026</title><link>https://j-cave.dk/site-update-august-2026/</link><pubDate>Mon, 10 Aug 2026 17:32:31 +0200</pubDate><guid>https://j-cave.dk/site-update-august-2026/</guid><description>&lt;div class="callout my-6 rounded-xl border border-charcoal-soft/25 bg-charcoal-soft/5 p-4"&gt;
 &lt;p class="font-semibold text-sm mb-1 text-charcoal-soft"&gt;Note&lt;/p&gt;
 &lt;div class="text-sm leading-relaxed text-charcoal-soft [&amp;_a]:text-accent [&amp;_a:hover]:underline [&amp;_p]:m-0"&gt;
 &lt;strong&gt;Update, September 2026:&lt;/strong&gt; a lot of what this post plans has since happened or changed. See the &lt;a href="https://j-cave.dk/site-update-september-2026/"&gt;Site Update September 2026&lt;/a&gt; for where the site is now.
 &lt;/div&gt;
&lt;/div&gt;


&lt;h1 id="site-update-as-of-august-2026"&gt;Site update as of August 2026&lt;/h1&gt;
&lt;p&gt;This site has long been in a state of missing new posts. But here&amp;rsquo;s to a new lease!&lt;/p&gt;
&lt;p&gt;It actually comes not just as a refresh, but a whole new base, as we have changed from Wordpress as a CRM to an Open Source Static site generator called HUGO. This shift should make the site delivery a lot faster, as the pages are actually pre-generated abd just needs to be served straight from the server.&lt;/p&gt;</description></item></channel></rss>