fix broken links in posts

content/equipment/handhelds/radioddity-gd77/index.md

@@ -3,7 +3,7 @@ title = 'Radioddity GD-77'
 summary = '''Consider the OpenGD77 firmware and you're all set with a
     very user friendly and customizable handheld radio.'''
 date = '2020-10-17'
-lastmod = '2023-10-25T20:41:06+0000'
+lastmod = '2023-11-18T17:23:31+0000'
 #categories = [ 'amateur-radio' ]
 showBreadcrumbs = true
 showReadingTime = false
@@ -99,7 +99,7 @@ Or: download your own set of DMR-IDs with the regions you want. You can also
 download only some federal states (like `2327,2328`) if you don't want all
 entries from `232`. [Read along here][dmrid] for some instructions about this.
 
-[dmrid]: {{< ref "posts/2020-11-16-create-your-own-dmrid-database-file" >}}
+[dmrid]: {{< ref "posts/2020/13-create-your-own-dmrid-database-file" >}}
 
 ## Band scope (Spectrum sweep scan)
 

content/posts/2020/15-forking-git-repositories/index.md

@@ -14,7 +14,7 @@ I can keep my local repository up-to-date to the original one and simply manage
 my changes to a github repository saved in my github account. So I can distribute
 my changes on many computers at home.
 
-[1]: {{< ref "2020-11-14-keep-up-to-date-on-forked-repositories" >}}
+[1]: {{< ref "11-keep-up-to-date-on-forked-repositories" >}}
 
 But all these changes make the structure of the git commit history more complex.
 I thought I could shrink my own commits down to a minimum and just summarize them

content/posts/2020/8-my-7inch-dmr-dashboard/index.md

@@ -23,7 +23,7 @@ displayed.
 
 I've lost a few words about this topic (Nextion) in general on my first post
 about my 2.4 inch nextion screen
-[in a previous article]({{< ref "2020-02-16-nextion-dmr-last-heard-dashboard" >}}#the-editor).
+[in a previous article]({{< ref "6-nextion-dmr-last-heard-dashboard" >}}#the-editor).
 
 {{< figure src="nxt07_00.jpg" alt="Nextion back view / model" caption="" >}}
 

content/posts/2022/22-my-weather-station-with-weewx-and-netatmo/index.md

@@ -27,8 +27,8 @@ That means we have to update the extension to a fork that is recently updated.
 There are two Follow-up posts to this article that show the migration to an
 OpenBSD server as well as the replacement of the netatmo weewx-extension.
 
-- [Moving WeeWX to OpenBSD]({{< ref "2023-05-27-moving-weewx-to-openbsd/index.md" >}})
-- [Update WeeWX extension]({{< ref "2023-07-15-update-weewx-netatmo-extension/index.md" >}})
+- [Moving WeeWX to OpenBSD]({{< ref "posts/2023/41-moving-weewx-to-openbsd" >}})
+- [Update WeeWX extension]({{< ref "posts/2023/47-update-weewx-netatmo-extension" >}})
 
 I recommend reading the last one to get a working setup. If you want to have a
 nice status message on APRS I also recommend reading the first one too, because

content/posts/2022/31-hamnet-on-the-pfsense/index.md

@@ -17,7 +17,7 @@ operating systems stopped supporting this protocol because it is outdated and
 insecure.
 
 In my recent
-[post about HAMNET]({{< ref "2022-10-16-vpn-tunnel-into-hamnet-on-fedora-36" >}})
+[post about HAMNET]({{< ref "posts/2022/29-vpn-tunnel-into-hamnet-on-fedora-36" >}})
 I created an <abbr title="Layer 2 Tunneling Protocol">L2TP</abbr> tunnel to the
 german VPN Server at the RWTH Aachen University on my laptop. Routes have been
 added manually -- the network was only available on this particular computer.

content/posts/2023/52-openbsd-current-built-from-source/index.md

@@ -9,7 +9,7 @@ tags = [ 'openbsd' ]
 
 +++
 
-[Initially]({{< ref "2023-07-29-going-back-from-openbsd-snapshot/index.md" >}}) I
+[Initially]({{< ref "48-going-back-from-openbsd-snapshot" >}}) I
 wanted to not look at OpenBSD-current again but I did it again.
 
 All went good this time and I could compile everything except the
@@ -244,5 +244,5 @@ Ready to be used.
 It is not hard to build OpenBSD from source, but it is very time consuming.
 
 Ports need a little tweaking, though. I will continue to follow -current by
-[upgrading to current snapshots]({{< ref "2023-09-30-following-openbsd-current-snapshots" >}}).
+[upgrading to current snapshots]({{< ref "55-following-openbsd-current-snapshots" >}}).
 

content/posts/2023/56-converting-big-videos/index.md

@@ -184,6 +184,6 @@ $ ls -l Video.MOV newvideo-*
 ## Related content (optimizing images)
 
 I've created a similar post for images in 2020:
-[Optimizing PNG images]({{< ref "2020-01-20-optimizing-png-images/" >}})
+[Optimizing PNG images]({{< ref "posts/2020/2-optimizing-png-images" >}})
 (there is also some info on JPG files).