Update content for gemtext

5 files changed, 14 insertions, 34 deletions

diff --git a/gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi b/gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi
index 48d97f45..3ee72ee8 100644
--- a/gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi
+++ b/gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi
@@ -1,15 +1,13 @@
 # Unveiling I/O Riot NG — Part 2: install and compile once, run everywhere
 
-> Published at 2026-05-10T22:43:39+03:00
+> Published at 2026-05-10T22:53:35+03:00
 
 This is Part 2 of three. Part 1 is the demo-driven tour: what ior looks like, how the dashboard tabs work, how filtering and recording behave. This part is about the installation for Rocky Linux 8 and 9 and, more interestingly, why you only have to do that dance on a single machine: the resulting binary is portable to every other Linux box thanks to CO-RE (Compile Once, Run Everywhere) plus full static linking. Part 3 is the under-the-hood companion (per-event schema, async-syscall caveats, the syscall-coverage probe generator, and post-mortem SQL on the parquet output).
 
-=> ./unveiling-ior-ng/00-hero-flamegraph.png Live flamegraph
-
 => ./2026-05-08-unveiling-ior-ng-part-1.gmi 2026-05-08 Unveiling I/O Riot NG — Part 1: a guided tour
 => ./2026-05-11-unveiling-ior-ng-part-2.gmi 2026-05-11 Unveiling I/O Riot NG — Part 2: install and compile once, run everywhere (You are currently reading this)
 
-=> ./unveiling-ior-ng/00-logo.png I/O Riot NG logo
+=> ./unveiling-ior-ng/00-hero-flamegraph.png Live flamegraph
 
 ## Table of Contents
 
@@ -28,10 +26,6 @@ This is Part 2 of three. Part 1 is the demo-driven tour: what ior looks like, ho
 
 ## Installing ior
 
-> Published at 2026-05-10T22:41:23+03:00
-
-> Published at 2026-05-10T22:39:24+03:00
-
 The short answer: Use Docker (or Podman). One command, no toolchain setup, works from any Docker-capable Linux host with BTF available:
 
 ```sh
diff --git a/gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi.tpl b/gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi.tpl
index 63ce6b94..818e828c 100644
--- a/gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi.tpl
+++ b/gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi.tpl
@@ -1,23 +1,17 @@
 # Unveiling I/O Riot NG — Part 2: install and compile once, run everywhere
 
-> Published at 2026-05-10T22:43:39+03:00
+> Published at 2026-05-10T22:53:35+03:00
 
 This is Part 2 of three. Part 1 is the demo-driven tour: what ior looks like, how the dashboard tabs work, how filtering and recording behave. This part is about the installation for Rocky Linux 8 and 9 and, more interestingly, why you only have to do that dance on a single machine: the resulting binary is portable to every other Linux box thanks to CO-RE (Compile Once, Run Everywhere) plus full static linking. Part 3 is the under-the-hood companion (per-event schema, async-syscall caveats, the syscall-coverage probe generator, and post-mortem SQL on the parquet output).
 
-=> ./unveiling-ior-ng/00-hero-flamegraph.png Live flamegraph
-
 << template::inline::index unveiling-ior-ng
 
-=> ./unveiling-ior-ng/00-logo.png I/O Riot NG logo
+=> ./unveiling-ior-ng/00-hero-flamegraph.png Live flamegraph
 
 << template::inline::toc
 
 ## Installing ior
 
-> Published at 2026-05-10T22:41:23+03:00
-
-> Published at 2026-05-10T22:39:24+03:00
-
 The short answer: Use Docker (or Podman). One command, no toolchain setup, works from any Docker-capable Linux host with BTF available:
 
 ```sh
diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml
index ec13b6b8..de3e1685 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-05-10T22:46:49+03:00</updated>
+    <updated>2026-05-10T22:53:36+03:00</updated>
     <title>foo.zone feed</title>
     <subtitle>To be in the .zone!</subtitle>
     <link href="gemini://foo.zone/gemfeed/atom.xml" rel="self" />
@@ -10,7 +10,7 @@
         <title>Unveiling I/O Riot NG — Part 2: install and compile once, run everywhere</title>
         <link href="gemini://foo.zone/gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi" />
         <id>gemini://foo.zone/gemfeed/2026-05-11-unveiling-ior-ng-part-2.gmi</id>
-        <updated>2026-05-10T22:43:39+03:00</updated>
+        <updated>2026-05-10T22:53:35+03:00</updated>
         <author>
             <name>Paul Buetow aka snonux</name>
             <email>paul@dev.buetow.org</email>
@@ -20,16 +20,12 @@
             <div xmlns="http://www.w3.org/1999/xhtml">
                 <h1 style='display: inline' id='unveiling-io-riot-ng--part-2-install-and-compile-once-run-everywhere'>Unveiling I/O Riot NG — Part 2: install and compile once, run everywhere</h1><br />
 <br />
-<span class='quote'>Published at 2026-05-10T22:43:39+03:00</span><br />
-<br />
 <span>This is Part 2 of three. Part 1 is the demo-driven tour: what ior looks like, how the dashboard tabs work, how filtering and recording behave. This part is about the installation for Rocky Linux 8 and 9 and, more interestingly, why you only have to do that dance on a single machine: the resulting binary is portable to every other Linux box thanks to CO-RE (Compile Once, Run Everywhere) plus full static linking. Part 3 is the under-the-hood companion (per-event schema, async-syscall caveats, the syscall-coverage probe generator, and post-mortem SQL on the parquet output).</span><br />
 <br />
-<a href='./unveiling-ior-ng/00-hero-flamegraph.png'><img alt='Live flamegraph' title='Live flamegraph' src='./unveiling-ior-ng/00-hero-flamegraph.png' /></a><br />
-<br />
 <a class='textlink' href='./2026-05-08-unveiling-ior-ng-part-1.html'>2026-05-08 Unveiling I/O Riot NG — Part 1: a guided tour</a><br />
 <a class='textlink' href='./2026-05-11-unveiling-ior-ng-part-2.html'>2026-05-11 Unveiling I/O Riot NG — Part 2: install and compile once, run everywhere (You are currently reading this)</a><br />
 <br />
-<a href='./unveiling-ior-ng/00-logo.png'><img alt='I/O Riot NG logo' title='I/O Riot NG logo' src='./unveiling-ior-ng/00-logo.png' /></a><br />
+<a href='./unveiling-ior-ng/00-hero-flamegraph.png'><img alt='Live flamegraph' title='Live flamegraph' src='./unveiling-ior-ng/00-hero-flamegraph.png' /></a><br />
 <br />
 <h2 style='display: inline' id='table-of-contents'>Table of Contents</h2><br />
 <br />
@@ -49,10 +45,6 @@
 </ul><br />
 <h2 style='display: inline' id='installing-ior'>Installing ior</h2><br />
 <br />
-<span class='quote'>Published at 2026-05-10T22:41:23+03:00</span><br />
-<br />
-<span class='quote'>Published at 2026-05-10T22:39:24+03:00</span><br />
-<br />
 <span>The short answer: Use Docker (or Podman). One command, no toolchain setup, works from any Docker-capable Linux host with BTF available:</span><br />
 <br />
 <!-- Generator: GNU source-highlight 3.1.9
diff --git a/index.gmi b/index.gmi
index 8c926dcf..d4d44d7c 100644
--- a/index.gmi
+++ b/index.gmi
@@ -1,6 +1,6 @@
 # Hello!
 
-> This site was generated at 2026-05-10T22:46:49+03:00 by `Gemtexter`
+> This site was generated at 2026-05-10T22:53:36+03:00 by `Gemtexter`
 
 Welcome to the foo.zone!
 
diff --git a/uptime-stats.gmi b/uptime-stats.gmi
index 94391d54..a2436d92 100644
--- a/uptime-stats.gmi
+++ b/uptime-stats.gmi
@@ -1,6 +1,6 @@
 # My machine uptime stats
 
-> This site was last updated at 2026-05-10T22:46:49+03:00
+> This site was last updated at 2026-05-10T22:53:35+03:00
 
 The following stats were collected via `uptimed` on all of my personal computers over many years and the output was generated by `goprecords`, the global uptime records stats analyser of mine.
 
@@ -13,7 +13,7 @@ Also check out my blog post:
 
 => ./gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.gmi Unveiling `guprecords.raku`: Uptime records with Raku (and also there is a version in Go now)
 
-> Uptime stats were last updated Sun 10 May 22:46:49 EEST 2026
+> Uptime stats were last updated Sun 10 May 22:53:36 EEST 2026
 
 ## Top 20 Uptime's by Host
 
@@ -64,8 +64,8 @@ Downtime is the total downtime of a host over the entire lifespan.
 |  3. |  *f2 | 0 years, 10 months, 29 days |       FreeBSD 15.0-RELEASE-p4 |
 |  4. | *pi0 |  0 years, 1 months, 21 days | Linux 6.1.31-v8.1.el9.altarch |
 |  5. | *pi2 |  0 years, 1 months, 21 days | Linux 6.1.31-v8.1.el9.altarch |
-|  6. |  pi3 |   0 years, 1 months, 1 days | Linux 6.1.31-v8.1.el9.altarch |
-|  7. |  pi1 |   0 years, 1 months, 1 days | Linux 6.1.31-v8.1.el9.altarch |
+|  6. |  pi1 |   0 years, 1 months, 1 days | Linux 6.1.31-v8.1.el9.altarch |
+|  7. |  pi3 |   0 years, 1 months, 1 days | Linux 6.1.31-v8.1.el9.altarch |
 +-----+------+-----------------------------+-------------------------------+
 ```
 
@@ -98,8 +98,8 @@ Score is calculated by combining all other metrics.
 |  1. |  *f1 |    75 |       FreeBSD 15.0-RELEASE-p4 |
 |  2. |  *f2 |    75 |       FreeBSD 15.0-RELEASE-p4 |
 |  3. |  *f0 |    74 |       FreeBSD 15.0-RELEASE-p4 |
-|  4. | *pi0 |     8 | Linux 6.1.31-v8.1.el9.altarch |
-|  5. | *pi2 |     8 | Linux 6.1.31-v8.1.el9.altarch |
+|  4. | *pi2 |     8 | Linux 6.1.31-v8.1.el9.altarch |
+|  5. | *pi0 |     8 | Linux 6.1.31-v8.1.el9.altarch |
 |  6. |  pi1 |     0 | Linux 6.1.31-v8.1.el9.altarch |
 |  7. |  pi3 |     0 | Linux 6.1.31-v8.1.el9.altarch |
 +-----+------+-------+-------------------------------+