Update content for gemtext

4 files changed, 13 insertions, 6 deletions

diff --git a/about/showcase/rcm/image-1.png b/about/showcase/rcm/image-1.png
new file mode 100644
index 00000000..ceadfb81
--- /dev/null
+++ b/about/showcase/rcm/image-1.png
diff --git a/gemfeed/2022-02-04-computer-operating-systems-i-use.gmi b/gemfeed/2022-02-04-computer-operating-systems-i-use.gmi
index c55f00d3..c4be38be 100644
--- a/gemfeed/2022-02-04-computer-operating-systems-i-use.gmi
+++ b/gemfeed/2022-02-04-computer-operating-systems-i-use.gmi
@@ -1,6 +1,6 @@
 # Computer operating systems I use(d)
 
-> Published at 2022-02-04T09:58:22+00:00; Updated at 2022-02-18
+> Published at 2022-02-04T09:58:22+00:00, last updated Mon 03 Mar 2026 02:14:00 EET 2026
 
 This is a list of Operating Systems I currently use. This list is in no particular order and also will be updated over time. The very first operating system I used was MS-DOS (mainly for games) and the very first Unix like operating system I used was SuSE Linux 5.3. My first smartphone OS was Symbian on a clunky Sony Ericsson device.
 
@@ -39,6 +39,7 @@ This is a list of Operating Systems I currently use. This list is in no particul
 * ⇢ ⇢ iOS (mobile proprietary)
 * ⇢ ⇢ Other OSes
 * ⇢ ⇢ ⇢ InfinyTime (smartwatch)
+* ⇢ ⇢ ⇢ GarminOS (smartwatch)
 * ⇢ ⇢ ⇢ motionEyeOS
 * ⇢ ⇢ ⇢ Kobo OS (proprietary)
 * ⇢ ⇢ ⇢ Android TV (proprietary)
@@ -175,6 +176,12 @@ I use it on my PineTime smartwatch. Other than checking the time and my step cou
 => https://www.pine64.org/pinetime/
 => https://infinitime.io/
 
+### GarminOS (smartwatch)
+
+I use GarminOS on my Garmin smartwatches. I previously used it on my Garmin Fenix 6 Pro and currently on my Garmin Fenix 7 Pro. It's an excellent smartwatch OS with comprehensive fitness tracking features, outstanding battery life, and tons of functionality. Despite being proprietary, it's the best option for serious sports and health monitoring.
+
+=> https://www.garmin.com/
+
 ### motionEyeOS
 
 I usually install an army of RaspberryPi 3's in my house before I travel for a prolonged amount of time. All Pi's are equipped with an camera and have motionEyeOS (Linux based video surveillance system) installed. There's a neat Android app in the F-Droid store which let's me keep an eye on everything. I make the Pi's accessible from the internet via reverse SSH tunnels through one of my frontend servers.
diff --git a/gemfeed/2026-03-02-rcm-ruby-configuration-management-dsl.gmi b/gemfeed/2026-03-02-rcm-ruby-configuration-management-dsl.gmi
index 7cf90a8a..5ab0a58e 100644
--- a/gemfeed/2026-03-02-rcm-ruby-configuration-management-dsl.gmi
+++ b/gemfeed/2026-03-02-rcm-ruby-configuration-management-dsl.gmi
@@ -34,7 +34,7 @@ RCM is a tiny configuration management system written in Ruby. It gives me a sma
 
 ## Why I built RCM
 
-I've used (and still use) the usual suspects in configuration management: Puppet, Chef, Ansible, etc. They are powerful, but also come with orchestration layers, agents, inventories, and a lot of moving parts. For my personal machines I wanted something smaller: one Ruby process, one configuration file, a few resource types, and good enough safety features.
+I've used (and still use) the usual suspects in configuration management: Puppet, Ansible, etc. They are powerful, but also come with orchestration layers, agents, inventories, and a lot of moving parts. For my personal machines I wanted something smaller: one Ruby process, one configuration file, a few resource types, and good enough safety features.
 
 I've always been a fan of Ruby's metaprogramming features, and this project let me explore them in a focused, practical way.
 
@@ -192,7 +192,7 @@ In that space RCM wins: it is small, transparent, and tuned for one person (me!)
 
 As of this post I'm tagging and releasing **RCM 0.1.0**. About 99% of the code has been written by me so far, and before AI agents take over more of the boilerplate and wiring work, it felt like a good moment to cut a release and mark this mostly‑human baseline.
 
-Future changes will very likely involve more automated help (including agents like the one you're reading this in), but 0.1.0 is the snapshot of the original, hand‑crafted version of the tool.
+Future changes will very likely involve more automated help, but 0.1.0 is the snapshot of the original, hand‑crafted version of the tool.
 
 ## What's next
 
diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml
index aea5fd43..d4f9ade4 100644
--- a/gemfeed/atom.xml
+++ b/gemfeed/atom.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <feed xmlns="http://www.w3.org/2005/Atom">
-    <updated>2026-03-01T21:53:45+02:00</updated>
+    <updated>2026-03-03T09:08:49+02:00</updated>
     <title>foo.zone feed</title>
     <subtitle>To be in the .zone!</subtitle>
     <link href="gemini://foo.zone/gemfeed/atom.xml" rel="self" />
@@ -55,7 +55,7 @@
 </ul><br />
 <h2 style='display: inline' id='why-i-built-rcm'>Why I built RCM</h2><br />
 <br />
-<span>I&#39;ve used (and still use) the usual suspects in configuration management: Puppet, Chef, Ansible, etc. They are powerful, but also come with orchestration layers, agents, inventories, and a lot of moving parts. For my personal machines I wanted something smaller: one Ruby process, one configuration file, a few resource types, and good enough safety features.</span><br />
+<span>I&#39;ve used (and still use) the usual suspects in configuration management: Puppet, Ansible, etc. They are powerful, but also come with orchestration layers, agents, inventories, and a lot of moving parts. For my personal machines I wanted something smaller: one Ruby process, one configuration file, a few resource types, and good enough safety features.</span><br />
 <br />
 <span>I&#39;ve always been a fan of Ruby&#39;s metaprogramming features, and this project let me explore them in a focused, practical way.</span><br />
 <br />
@@ -235,7 +235,7 @@ HostCondition.new.hostname.is(:earth)
 <br />
 <span>As of this post I&#39;m tagging and releasing **RCM 0.1.0**. About 99% of the code has been written by me so far, and before AI agents take over more of the boilerplate and wiring work, it felt like a good moment to cut a release and mark this mostly‑human baseline.</span><br />
 <br />
-<span>Future changes will very likely involve more automated help (including agents like the one you&#39;re reading this in), but 0.1.0 is the snapshot of the original, hand‑crafted version of the tool.</span><br />
+<span>Future changes will very likely involve more automated help, but 0.1.0 is the snapshot of the original, hand‑crafted version of the tool.</span><br />
 <br />
 <h2 style='display: inline' id='what-s-next'>What&#39;s next</h2><br />
 <br />