This service tests the validity of an RSS 2.0 feed, checking to see that it follows the rules of the RSS specification. For advice from the RSS Advisory Board on how to implement RSS and handle issues such as enclosures and HTML encoding, read the RSS Best Practices Profile. This checker is also a validator of Atom and RSS 1.0 feeds.

Use this tester regularly to ensure that your RSS feed continues to work well in the wide audience of RSS readers, podcast clients and other software that supports the format.

 

Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

  • line 6678, column 0: description should not contain script tag (6 occurrences) [help]

    <script src="https://gist.github.com/x-way/caf03da77fe2cc83b6bd.js"></script>

  • line 6686, column 0: content:encoded should not contain script tag (6 occurrences) [help]

    <script src="https://gist.github.com/x-way/caf03da77fe2cc83b6bd.js"></script>

  • line 8433, column 3: description should not contain relative URL references: # (16 occurrences) [help]

    ]]></description>
       ^

  • line 8435, column 3: content:encoded should not contain relative URL references: # (16 occurrences) [help]

    ]]></content:encoded>
       ^

Source: http://blog.x-way.org/rss.xml

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <rss version="2.0"
  3.  xmlns:dc="http://purl.org/dc/elements/1.1/"
  4.  xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
  5.  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  6.  xmlns:atom="http://www.w3.org/2005/Atom">
  7.  
  8. <channel>
  9.  <title>x-log</title>
  10.  <link>https://blog.x-way.org</link>
  11.  <description>x-log</description>
  12.  <lastBuildDate>Sat, 14 Dec 2024 07:01:49 +0100</lastBuildDate>
  13.  <language>en</language>
  14.  <managingEditor>andreas+rss@jaggi.info (Andreas Jaggi)</managingEditor>
  15.  <webMaster>andreas+rss@jaggi.info (Andreas Jaggi)</webMaster>
  16.  <copyright>Andreas Jaggi</copyright>
  17.  <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  18.  <generator>x-log c3d9ad</generator>
  19.  <atom:link href="https://blog.x-way.org/rss.xml" rel="self" type="application/rss+xml"/>
  20.  
  21.  <image>
  22.    <url>https://blog.x-way.org/logo.gif</url>
  23.    <title>x-log</title>
  24.    <link>https://blog.x-way.org</link>
  25.  </image>
  26.  
  27.  
  28.  <item>
  29.    <title>The seven rules of writing consistent git commit messages</title>
  30.    <link>https://blog.x-way.org/Coding/2024/12/11/The-seven-rules-of-writing-consistent-git-commit-messages.html</link>
  31.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324436</guid>
  32.    <dc:creator>Andreas Jaggi</dc:creator>
  33.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  34.    <pubDate>Wed, 11 Dec 2024 15:51:58 +0100</pubDate>
  35.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  36.    <description><![CDATA[<blockquote cite="https://rednafi.com/misc/write_git_commit_messages_properly/#the-seven-rules-of-writing-consistent-git-commit-messages">
  37. <ol>
  38. <li>Separate subject from body with a blank line</li>
  39. <li>Limit the subject line to 50 characters (I often break this when there&rsquo;s no message body)</li>
  40. <li>Capitalize the subject line</li>
  41. <li>Do not end the subject line with a period</li>
  42. <li>Use the imperative mood in the subject line</li>
  43. <li>Wrap the body at 72 characters</li>
  44. <li>Use the body to explain what and why vs. how</li>
  45. </ol>
  46. </blockquote>
  47. <p>
  48. (<a href="https://rednafi.com/misc/write_git_commit_messages_properly/#the-seven-rules-of-writing-consistent-git-commit-messages" title="Write git commit messages properly | Redowan's Reflections">via</a>)
  49. </p>
  50. ]]></description>
  51.    <content:encoded><![CDATA[<blockquote cite="https://rednafi.com/misc/write_git_commit_messages_properly/#the-seven-rules-of-writing-consistent-git-commit-messages">
  52. <ol>
  53. <li>Separate subject from body with a blank line</li>
  54. <li>Limit the subject line to 50 characters (I often break this when there&rsquo;s no message body)</li>
  55. <li>Capitalize the subject line</li>
  56. <li>Do not end the subject line with a period</li>
  57. <li>Use the imperative mood in the subject line</li>
  58. <li>Wrap the body at 72 characters</li>
  59. <li>Use the body to explain what and why vs. how</li>
  60. </ol>
  61. </blockquote>
  62. <p>
  63. (<a href="https://rednafi.com/misc/write_git_commit_messages_properly/#the-seven-rules-of-writing-consistent-git-commit-messages" title="Write git commit messages properly | Redowan's Reflections">via</a>)
  64. </p>
  65. ]]></content:encoded>
  66.  </item>
  67.  
  68.  <item>
  69.    <title>oxipng</title>
  70.    <link>https://blog.x-way.org/Webdesign/2024/12/10/oxipng.html</link>
  71.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324435</guid>
  72.    <dc:creator>Andreas Jaggi</dc:creator>
  73.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  74.    <pubDate>Tue, 10 Dec 2024 19:56:17 +0100</pubDate>
  75.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  76.    <description><![CDATA[<p>
  77. <a href="https://github.com/shssoichiro/oxipng" title="shssoichiro/oxipng: Multithreaded PNG optimizer written in Rust">oxipng</a> is a lossless PNG compression optimizer written in Rust.<br>
  78. On an initial test it seems to perform better than <a href="https://pmt.sourceforge.io/pngcrush/" title="PNGCRUSH">pngcrush</a>.<br>
  79. (<a href="https://rednafi.com/misc/behind_the_blog/" title="Behind the blog | Redowan's Reflections">via</a>)
  80. </p>
  81. ]]></description>
  82.    <content:encoded><![CDATA[<p>
  83. <a href="https://github.com/shssoichiro/oxipng" title="shssoichiro/oxipng: Multithreaded PNG optimizer written in Rust">oxipng</a> is a lossless PNG compression optimizer written in Rust.<br>
  84. On an initial test it seems to perform better than <a href="https://pmt.sourceforge.io/pngcrush/" title="PNGCRUSH">pngcrush</a>.<br>
  85. (<a href="https://rednafi.com/misc/behind_the_blog/" title="Behind the blog | Redowan's Reflections">via</a>)
  86. </p>
  87. ]]></content:encoded>
  88.  </item>
  89.  
  90.  <item>
  91.    <title>New search functionality</title>
  92.    <link>https://blog.x-way.org/Webdesign/2024/12/08/New-search-functionality.html</link>
  93.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324434</guid>
  94.    <dc:creator>Andreas Jaggi</dc:creator>
  95.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  96.    <pubDate>Sun, 08 Dec 2024 22:52:20 +0100</pubDate>
  97.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  98.    <description><![CDATA[<p>
  99. I added a client-side search functionality to this static blog.
  100. </p>
  101. <p>
  102. Similar to what is explained in <a href="https://www.stephanmiller.com/static-site-search/" title="How to Add Search to Your Static Site Generator (Jekyll, Hugo, Gatsby, Nikola, etc.) • Stephan Miller">this article by Stephan Miller</a>, I added a search functionality to the blog.<br>
  103. The challenge was to do this while keeping the blog a static generated site.<br>
  104. Thus the choice to do all of the search client-side in JavaScript.
  105. </p>
  106. <p>
  107. The way my current implementation works, is that there is a JSON blob with all the posts ever written in this blog.<br>
  108. This is loaded to the browser and indexed using <a href="https://lunrjs.com/" title="Lunr: A bit like Solr, but much smaller and not as bright">Lunr.js</a>.<br>
  109. The resulting search index is then used to provide the search functionality.<br>
  110. It comes with some convenient built-in <a href="https://lunrjs.com/guides/searching.html" title="Searching : Lunr">search modifiers such as +, - and *</a>.
  111. </p>
  112. <p>
  113. To avoid reloading the whole JSON blob for each follow-up query on <a href="https://blog.x-way.org/search.html" title="x-log - Search">the search page</a>, it intercepts the default form submit action and handles the search client-side.<br>
  114. Thus re-using the computed search index and saving the additional roundtrips accross the network.
  115. </p>
  116. ]]></description>
  117.    <content:encoded><![CDATA[<p>
  118. I added a client-side search functionality to this static blog.
  119. </p>
  120. <p>
  121. Similar to what is explained in <a href="https://www.stephanmiller.com/static-site-search/" title="How to Add Search to Your Static Site Generator (Jekyll, Hugo, Gatsby, Nikola, etc.) • Stephan Miller">this article by Stephan Miller</a>, I added a search functionality to the blog.<br>
  122. The challenge was to do this while keeping the blog a static generated site.<br>
  123. Thus the choice to do all of the search client-side in JavaScript.
  124. </p>
  125. <p>
  126. The way my current implementation works, is that there is a JSON blob with all the posts ever written in this blog.<br>
  127. This is loaded to the browser and indexed using <a href="https://lunrjs.com/" title="Lunr: A bit like Solr, but much smaller and not as bright">Lunr.js</a>.<br>
  128. The resulting search index is then used to provide the search functionality.<br>
  129. It comes with some convenient built-in <a href="https://lunrjs.com/guides/searching.html" title="Searching : Lunr">search modifiers such as +, - and *</a>.
  130. </p>
  131. <p>
  132. To avoid reloading the whole JSON blob for each follow-up query on <a href="https://blog.x-way.org/search.html" title="x-log - Search">the search page</a>, it intercepts the default form submit action and handles the search client-side.<br>
  133. Thus re-using the computed search index and saving the additional roundtrips accross the network.
  134. </p>
  135. ]]></content:encoded>
  136.  </item>
  137.  
  138.  <item>
  139.    <title>The Earworm Eraser</title>
  140.    <link>https://blog.x-way.org/Music/2024/12/06/The-Earworm-Eraser.html</link>
  141.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324433</guid>
  142.    <dc:creator>Andreas Jaggi</dc:creator>
  143.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  144.    <pubDate>Fri, 06 Dec 2024 10:58:28 +0100</pubDate>
  145.    <category domain="https://blog.x-way.org/Music/">Music</category>
  146.    <description><![CDATA[<blockquote cite="https://www.wbur.org/npr/nx-s1-5200065/earworm-eraser-christmas-songs">
  147. The Earworm Eraser is a 40-second audio track designed specifically to squash earworms — a song on repeat circling around and around in your brain that can't easily be shaken off.
  148. </blockquote>
  149. <p>
  150. <a href="https://youtu.be/LvDl3kL42uU" title="The Earworm Eraser – Get catchy songs out of your head | Atlassian">The Earworm Eraser – Get catchy songs out of your head | Atlassian</a>
  151. </p>
  152. <p>
  153. (<a href="https://onefoottsunami.com/2024/12/05/the-earworm-eraser/" title="One Foot Tsunami: The Earworm Eraser">via</a>)
  154. </p>
  155. ]]></description>
  156.    <content:encoded><![CDATA[<blockquote cite="https://www.wbur.org/npr/nx-s1-5200065/earworm-eraser-christmas-songs">
  157. The Earworm Eraser is a 40-second audio track designed specifically to squash earworms — a song on repeat circling around and around in your brain that can't easily be shaken off.
  158. </blockquote>
  159. <p>
  160. <a href="https://youtu.be/LvDl3kL42uU" title="The Earworm Eraser – Get catchy songs out of your head | Atlassian">The Earworm Eraser – Get catchy songs out of your head | Atlassian</a>
  161. </p>
  162. <p>
  163. (<a href="https://onefoottsunami.com/2024/12/05/the-earworm-eraser/" title="One Foot Tsunami: The Earworm Eraser">via</a>)
  164. </p>
  165. ]]></content:encoded>
  166.  </item>
  167.  
  168.  <item>
  169.    <title>Picture of Sequoia</title>
  170.    <link>https://blog.x-way.org/Mac/2024/12/06/Picture-of-Sequoia.html</link>
  171.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324432</guid>
  172.    <dc:creator>Andreas Jaggi</dc:creator>
  173.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  174.    <pubDate>Fri, 06 Dec 2024 07:19:35 +0100</pubDate>
  175.    <category domain="https://blog.x-way.org/Mac/">Mac</category>
  176.    <description><![CDATA[<p>
  177. Recreated <a href="https://blog.x-way.org/Linux/2003/12/06/Photo_vom_Panther.html" title="x-log - Photo vom Panther">this screenshot</a> from 21 years ago (first Mac) on my new Mac.
  178. </p>
  179. <ul>
  180. <li><a href="https://blog.x-way.org/images/Mac-OS-X-Screenshot.jpg" title="Screenshot of my Mac desktop in 2003">2003</a></li>
  181. <li><a href="https://blog.x-way.org/images/macOS-Screenshot.png" title="Screenshot of my Mac desktop in 2024">2024</a></li>
  182. </ul>
  183. <p>
  184. How does 2003 and 2024 compare?<br>
  185. Nowadays I'm using the regular Apple Mail.<br>
  186. X11 forwarding still works but is not really used.<br>
  187. Some Linux host is still around.
  188. Mac remains the main device though.<br>
  189. Interestingly Linux still is a Intel device, whereas the Mac one is (again) running on a non-Intel CPU.
  190. </p>
  191. ]]></description>
  192.    <content:encoded><![CDATA[<p>
  193. Recreated <a href="https://blog.x-way.org/Linux/2003/12/06/Photo_vom_Panther.html" title="x-log - Photo vom Panther">this screenshot</a> from 21 years ago (first Mac) on my new Mac.
  194. </p>
  195. <ul>
  196. <li><a href="https://blog.x-way.org/images/Mac-OS-X-Screenshot.jpg" title="Screenshot of my Mac desktop in 2003">2003</a></li>
  197. <li><a href="https://blog.x-way.org/images/macOS-Screenshot.png" title="Screenshot of my Mac desktop in 2024">2024</a></li>
  198. </ul>
  199. <p>
  200. How does 2003 and 2024 compare?<br>
  201. Nowadays I'm using the regular Apple Mail.<br>
  202. X11 forwarding still works but is not really used.<br>
  203. Some Linux host is still around.
  204. Mac remains the main device though.<br>
  205. Interestingly Linux still is a Intel device, whereas the Mac one is (again) running on a non-Intel CPU.
  206. </p>
  207. ]]></content:encoded>
  208.  </item>
  209.  
  210.  <item>
  211.    <title>How to install EncFS on macOS Sequoia</title>
  212.    <link>https://blog.x-way.org/Mac/2024/12/03/How-to-install-EncFS-on-macOS-Sequoia.html</link>
  213.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324431</guid>
  214.    <dc:creator>Andreas Jaggi</dc:creator>
  215.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  216.    <pubDate>Tue, 03 Dec 2024 08:58:40 +0100</pubDate>
  217.    <category domain="https://blog.x-way.org/Mac/">Mac</category>
  218.    <description><![CDATA[<p>
  219. How to access my old encrypted files even though <a href="https://vgough.github.io/encfs/" title="EncFS">EncFS</a> is no longer supported in Homebrew for macOS.
  220. </p>
  221. <ol>
  222. <li>Start by installing a third-party formula that some nice people maintain: <pre>brew install gromgit/fuse/encfs-mac</pre></li>
  223. <li>Immediately get disappointed when it fails. Turns out it requires openssl@1.1 which has been deprecated by Homebrew: <pre><span style="color: green">==&gt;</span> <b>Fetching dependencies for gromgit/fuse/encfs-mac: <span style="color: green">openssl@1.1</span></b>
  224. <span style="color: red">Error:</span> openssl@1.1 has been disabled because it is not supported upstream! It was disabled on 2024-10-24.</pre></li>
  225. </ol>
  226. <p>
  227. How to install the (no longer supported) openssl@1.1 formula.
  228. </p>
  229. <ol>
  230. <li>Force the download of the core formula repository: <pre>brew tap --force homebrew/core</pre></li>
  231. <li>Edit the formula and remove the deprecation enforcement: <pre>brew edit openssl@1.1</pre> Comment out line 29, so it looks like: <pre>  #disable! date: "2024-10-24", because: :unsupported</pre></li>
  232. <li>Perform installation of openssl@1.1 from the locally modified formula: <pre>HOMEBREW_NO_INSTALL_FROM_API=1 brew install openssl@1.1</pre></li>
  233. </ol>
  234. <p>
  235. Now we can install EncFS successfully.
  236. </p>
  237. <pre>brew install gromgit/fuse/encfs-mac                    
  238. ==&gt; Fetching gromgit/fuse/encfs-mac
  239. ==&gt; Downloading https://github.com/gromgit/homebrew-fuse/releases/download/encfs-mac-1.9.5/encfs-mac-1.9.5.arm64_monterey.bottle.tar.gz
  240. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  241. ==&gt; Installing encfs-mac from gromgit/fuse
  242. ==&gt; Pouring encfs-mac-1.9.5.arm64_monterey.bottle.tar.gz
  243. ==&gt; Downloading https://formulae.brew.sh/api/cask.jws.json
  244. 🍺  /opt/homebrew/Cellar/encfs-mac/1.9.5: 65 files, 2.2MB
  245. ==&gt; Running `brew cleanup encfs-mac`...
  246. </pre>
  247. <p>
  248. If desired, we can now run <kbd>brew untap homebrew/core</kbd> to cleanup the local copy of the formula repository.
  249. </p>
  250. <p>
  251. Next step is to enable the (earlier installed) MacFuse kernel extension.<br>
  252. On macOS Sequoia this is a quite complicated process (needs disabling of multiple security features and some reboots).<br>
  253. Luckily the people from the MacFuse project have compiled <a href="https://github.com/macfuse/macfuse/wiki/Getting-Started#enabling-support-for-third-party-kernel-extensions-apple-silicon-macs" title="Getting Started - Enabling support for third party kernel extensions (Apple Silicon Macs)">a nice illustrated guide.</a>
  254. </p>
  255. <p>
  256. After this process is completed, we can finally decrypt the EncFS files.
  257. </p>
  258. <pre>encfs -v -f ./encrypted-folder ./mountpoint</pre>
  259. <p>
  260. The unencrypted files are available at <var>./mountpoint</var>.<br>
  261. In my case I copied them to another folder as I no longer intend to use EncFS.
  262. </p>
  263. <p>
  264. With the job done, I removed again all the EncFS software and re-enabled the security features of macOS.
  265. </p>
  266. <pre>brew uninstall encfs-mac
  267. brew uninstall openssl@1.1
  268. brew uninstall macfuse</pre>
  269. <p>
  270. Then reboot into the Recovery environment and in the Startup Security Utility set the Security Policy again to Full Security. 🔐
  271. </p>
  272. ]]></description>
  273.    <content:encoded><![CDATA[<p>
  274. How to access my old encrypted files even though <a href="https://vgough.github.io/encfs/" title="EncFS">EncFS</a> is no longer supported in Homebrew for macOS.
  275. </p>
  276. <ol>
  277. <li>Start by installing a third-party formula that some nice people maintain: <pre>brew install gromgit/fuse/encfs-mac</pre></li>
  278. <li>Immediately get disappointed when it fails. Turns out it requires openssl@1.1 which has been deprecated by Homebrew: <pre><span style="color: green">==&gt;</span> <b>Fetching dependencies for gromgit/fuse/encfs-mac: <span style="color: green">openssl@1.1</span></b>
  279. <span style="color: red">Error:</span> openssl@1.1 has been disabled because it is not supported upstream! It was disabled on 2024-10-24.</pre></li>
  280. </ol>
  281. <p>
  282. How to install the (no longer supported) openssl@1.1 formula.
  283. </p>
  284. <ol>
  285. <li>Force the download of the core formula repository: <pre>brew tap --force homebrew/core</pre></li>
  286. <li>Edit the formula and remove the deprecation enforcement: <pre>brew edit openssl@1.1</pre> Comment out line 29, so it looks like: <pre>  #disable! date: "2024-10-24", because: :unsupported</pre></li>
  287. <li>Perform installation of openssl@1.1 from the locally modified formula: <pre>HOMEBREW_NO_INSTALL_FROM_API=1 brew install openssl@1.1</pre></li>
  288. </ol>
  289. <p>
  290. Now we can install EncFS successfully.
  291. </p>
  292. <pre>brew install gromgit/fuse/encfs-mac                    
  293. ==&gt; Fetching gromgit/fuse/encfs-mac
  294. ==&gt; Downloading https://github.com/gromgit/homebrew-fuse/releases/download/encfs-mac-1.9.5/encfs-mac-1.9.5.arm64_monterey.bottle.tar.gz
  295. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  296. ==&gt; Installing encfs-mac from gromgit/fuse
  297. ==&gt; Pouring encfs-mac-1.9.5.arm64_monterey.bottle.tar.gz
  298. ==&gt; Downloading https://formulae.brew.sh/api/cask.jws.json
  299. 🍺  /opt/homebrew/Cellar/encfs-mac/1.9.5: 65 files, 2.2MB
  300. ==&gt; Running `brew cleanup encfs-mac`...
  301. </pre>
  302. <p>
  303. If desired, we can now run <kbd>brew untap homebrew/core</kbd> to cleanup the local copy of the formula repository.
  304. </p>
  305. <p>
  306. Next step is to enable the (earlier installed) MacFuse kernel extension.<br>
  307. On macOS Sequoia this is a quite complicated process (needs disabling of multiple security features and some reboots).<br>
  308. Luckily the people from the MacFuse project have compiled <a href="https://github.com/macfuse/macfuse/wiki/Getting-Started#enabling-support-for-third-party-kernel-extensions-apple-silicon-macs" title="Getting Started - Enabling support for third party kernel extensions (Apple Silicon Macs)">a nice illustrated guide.</a>
  309. </p>
  310. <p>
  311. After this process is completed, we can finally decrypt the EncFS files.
  312. </p>
  313. <pre>encfs -v -f ./encrypted-folder ./mountpoint</pre>
  314. <p>
  315. The unencrypted files are available at <var>./mountpoint</var>.<br>
  316. In my case I copied them to another folder as I no longer intend to use EncFS.
  317. </p>
  318. <p>
  319. With the job done, I removed again all the EncFS software and re-enabled the security features of macOS.
  320. </p>
  321. <pre>brew uninstall encfs-mac
  322. brew uninstall openssl@1.1
  323. brew uninstall macfuse</pre>
  324. <p>
  325. Then reboot into the Recovery environment and in the Startup Security Utility set the Security Policy again to Full Security. 🔐
  326. </p>
  327. ]]></content:encoded>
  328.  </item>
  329.  
  330.  <item>
  331.    <title>Migrate Homebrew from Intel to M4 MacBook Pro</title>
  332.    <link>https://blog.x-way.org/Mac/2024/12/01/Migrate-Homebrew-from-Intel-to-M4-MacBook-Pro.html</link>
  333.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324430</guid>
  334.    <dc:creator>Andreas Jaggi</dc:creator>
  335.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  336.    <pubDate>Sun, 01 Dec 2024 16:12:31 +0100</pubDate>
  337.    <category domain="https://blog.x-way.org/Mac/">Mac</category>
  338.    <description><![CDATA[<p>
  339. A big part of the time used to <a href="https://blog.x-way.org/Mac/2024/11/30/Move-from-2017-Intel-MacBook-Pro-to-2024-M4-MacBook-Pro.html" title="x-log - Move from 2017 Intel MacBook Pro to 2024 M4 MacBook Pro">move from my 2017 Intel MacBook Pro to my new 2024 M4 MacBook Pro</a> was spent on migrating my <a href="https://brew.sh/" title="Homebrew — The Missing Package Manager for macOS">Homebrew installation</a>.
  340. </p>
  341. <p>
  342. There are three aspects to the migration.
  343. </p>
  344. <ul>
  345. <li>One is the change in CPU architecture (which means to replace my Intel-only binaries with arm64 binaries).</li>
  346. <li>The other one is the change of the Homebrew root folder from <var>/usr/local</var> to <var>/opt/homebrew</var>.</li>
  347. <li>And the last one is the change in OS version (from macOS 13 to macOS 15).</li>
  348. </ul>
  349. <p>
  350. The impact of the change in CPU architecture was mostly taken care of by enabling the Rosetta 2 emulator to run Intel-binaries on the M4.<br>
  351. This immediately fixed the problem of my Terminal windows auto-closing on startup (as they now no longer failed to run the zsh Intel-binary).<br>
  352. But it did not solve all problems, particularly annoying was that vim could not be started and always failed with the following error:
  353. </p>
  354. <pre>dyld[31382]: Library not loaded: /System/Library/Perl/5.30/darwin-thread-multi-2level/CORE/libperl.dylib
  355.  Referenced from: &lt;77AC96DE-0453-3E1C-B442-EFE624110BAE&gt; /usr/local/Cellar/vim/9.1.0750_1/bin/vim
  356.  Reason: tried: '/System/Library/Perl/5.30/darwin-thread-multi-2level/CORE/libperl.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/System/Library/Perl/5.30/darwin-thread-multi-2level/CORE/libperl.dylib' (no such file), '/System/Library/Perl/5.30/darwin-thread-multi-2level/CORE/libperl.dylib' (no such file, not in dyld cache), '/usr/local/lib/libperl.dylib' (no such file), '/usr/lib/libperl.dylib' (no such file, not in dyld cache)</pre>
  357. <p>
  358. My workaround for this was to use the default vim that comes bundled with macOS, by typing <kbd>/usr/bin/vim</kbd>.<br>
  359. Although it complained about some unsupported parts in my <var>.vimrc</var>, it at least started up and was usable enough to edit files.<br>
  360. The error itself seems due to some Perl system libraries that vim was compiled with and which now no longer exist in the new macOS version.<br>
  361. This is a typical problem which can be solved by re-installing Homebrew.
  362. </p>
  363. <p>
  364. <b>Re-installing Homebrew</b><br>
  365. The steps below follow <a href="https://docs.brew.sh/Common-Issues#unintentional-dual-homebrew-installations" title="Common Issues - Unintentional dual Homebrew installations">this FAQ entry</a> and are extended with what was needed to make it work for my situation.<br>
  366. Your mileage might vary!
  367. </p>
  368. <ol>
  369. <li>In the Terminal.app settings, set the login shell to <var>Default</var>. This to avoid Rosetta's Intel emulated zsh from the previous installation interfering with things.</li>
  370. <li>Verify that you're running in native ARM mode with the <kbd>arch</kbd> command. It should return <var>arm64</var>.</li>
  371. <li>Create a dump of the previous Homebrew installation by explicitly running brew through Rosetta's Intel emulation: <pre>arch -x86_64 /usr/local/bin/brew bundle dump --global</pre></li>
  372. <li>Review the resulting <var>~/.Brewfile</var> and adjust as desired (I didn't make any adjustments).</li>
  373. <li>Ensure that native arm binaries are preferred over Intel binaries from the previous installation: <pre>export PATH=/bin:/usr/bin:/sbin:/usr/sbin:$PATH</pre></li>
  374. <li>Install homebrew into <var>/opt/homebrew</var> with: <pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre></li>
  375. <li>Adjust your shell config file to prefer <var>/opt/homebrew/bin</var> over <var>/usr/local/bin</var> in the PATH.<br>As I manually set PATH in my <var>.zshrc</var>, I needed to adjust it. Following these commands recommended by the brew installer was not enough! <pre><b><span style="color: blue">==&gt;</span> Next steps:</b>
  376. - Run these commands in your terminal to add Homebrew to your <b>PATH</b>:
  377.    echo &gt;&gt; /Users/aj/.zprofile
  378.    echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' &gt;&gt; /Users/aj/.zprofile
  379.    eval "$(/opt/homebrew/bin/brew shellenv)"</pre></li>
  380. <li>Open a fresh terminal window and verify with <kbd>which brew</kbd>, it must return <var>/opt/homebrew/bin/brew</var>.</li>
  381. <li>Now have brew install all the applications from the dump in the <var>~/.Brewfile</var>: <pre>/opt/homebrew/bin/brew bundle install --global</pre></li>
  382. <li>This process will print some warnings and errors, thus make sure to keep the output.<br>I will go through all the errors and warnings I encountered and list how I fixed them below (for the ones I could fix, unfortunately not all have been fixed yet).<br>It usually ends with a summary of the number of failures: <pre><span style="color: red">Homebrew Bundle failed! 30 Brewfile dependencies failed to install.Homebrew Bundle failed! 30 Brewfile dependencies failed to install.</span></pre></li>
  383. <li>Once the process is completed and you see the above summary, open the Terminal.app settings and set the Login shell to <var>/opt/homebrew/bin/zsh</var></li>
  384. <li>Open a fresh terminal window and verify that you are now running in native arm64 mode with <kbd>arch</kbd>.</li>
  385. <li>Now we are ready to address the errors, and then at the end we will remove the old Homebrew installation under <var>/usr/local</var>.</li>
  386. </ol>
  387. <p>
  388. <b>Outdated Xcode and missing Xcode command-line utilities</b><br>
  389. Due to the change in macOS version, the Xcode installation was outdated and also no usable command-line utilities were available.<br>
  390. This usually manifests in errors like these:
  391. </p>
  392. <pre><span style="color: green">Installing ssh-audit</span>
  393. ==&gt; Fetching ssh-audit
  394. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-core/723e7ef695e15c790aab727c1da11a2a4610ad53/Formula/s/ssh-audit.rb
  395. ==&gt; Cloning https://github.com/jtesta/ssh-audit.git
  396. Cloning into '/Users/aj/Library/Caches/Homebrew/ssh-audit--git'...
  397. ==&gt; Checking out branch master
  398. Already on 'master'
  399. Your branch is up to date with 'origin/master'.
  400. Error: Your Xcode (15.1) at /Applications/Xcode.app is too outdated.
  401. Please update to Xcode 16.0 (or delete it).
  402. Xcode can be updated from the App Store.
  403.  
  404. Error: Your Command Line Tools are too outdated.
  405. Update them from Software Update in System Settings.
  406.  
  407. If that doesn't show you any updates, run:
  408.  sudo rm -rf /Library/Developer/CommandLineTools
  409.  sudo xcode-select --install
  410.  
  411. Alternatively, manually download them from:
  412.  https://developer.apple.com/download/all/.
  413. You should download the Command Line Tools for Xcode 16.0.
  414.  
  415. <span style="color: red">Installing ssh-audit has failed!</span></pre>
  416. <pre><span style="color: green">Installing tdsmith/ham/direwolf</span>
  417. ==&gt; Fetching dependencies for tdsmith/ham/direwolf: portaudio
  418. ==&gt; Fetching portaudio
  419. ==&gt; Downloading https://ghcr.io/v2/homebrew/core/portaudio/manifests/19.7.0-1
  420. ==&gt; Downloading https://ghcr.io/v2/homebrew/core/portaudio/blobs/sha256:8ad9f1c15a4bc9c05a9dd184b53b8f5f5d13a2458a70535bfb01e54ce4f8b4bd
  421. ==&gt; Fetching tdsmith/ham/direwolf
  422. ==&gt; Downloading https://github.com/wb2osz/direwolf/archive/1.4-dev-E.tar.gz
  423. ==&gt; Downloading from https://codeload.github.com/wb2osz/direwolf/tar.gz/refs/tags/1.4-dev-E
  424. ==&gt; Installing direwolf from tdsmith/ham
  425. Error: Your Xcode (15.1) at /Applications/Xcode.app is too outdated.
  426. Please update to Xcode 16.0 (or delete it).
  427. Xcode can be updated from the App Store.
  428.  
  429. Error: Your Command Line Tools are too outdated.
  430. Update them from Software Update in System Settings.
  431.  
  432. If that doesn't show you any updates, run:
  433.  sudo rm -rf /Library/Developer/CommandLineTools
  434.  sudo xcode-select --install
  435.  
  436. Alternatively, manually download them from:
  437.  https://developer.apple.com/download/all/.
  438. You should download the Command Line Tools for Xcode 16.0.
  439.  
  440. <span style="color: red">Installing tdsmith/ham/direwolf has failed!</span></pre>
  441. <p>
  442. This can be fixed in two steps.<br>
  443. First update Xcode via the App Store.<br>
  444. Then run the mentioned commands to install/update the command-line utilities:
  445. </p>
  446. <pre>sudo rm -rf /Library/Developer/CommandLineTools
  447. sudo xcode-select --install</pre>
  448. <p>
  449. With the latest Xcode and command-line utilities in place, trigger a new installation attempt for the affected applications:
  450. </p>
  451. <pre>brew install ssh-audit
  452. brew install tdsmith/ham/direwolf</pre>
  453. <p>
  454. <b>Missing Rosetta 2 Intel emulation</b><br>
  455. Some of the Casks distributed by Homebrew are currently only available as Intel-binaries.<br>
  456. This usually manifests in warnings like these:
  457. </p>
  458. <pre><span style="color: green">Installing gqrx</span>
  459. ==&gt; Caveats
  460. gqrx is built for Intel macOS and so requires Rosetta 2 to be installed.
  461. You can install Rosetta 2 with:
  462.  softwareupdate --install-rosetta --agree-to-license
  463. Note that it is very difficult to remove Rosetta 2 once it is installed.
  464.  
  465. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/g/gqrx.rb
  466. ==&gt; Downloading https://github.com/gqrx-sdr/gqrx/releases/download/v2.17.5/Gqrx-2.17.5.dmg
  467. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  468. ==&gt; Installing Cask gqrx
  469. Error: It seems there is already an App at '/Applications/Gqrx.app'.
  470. ==&gt; Purging files for version 2.17.5 of Cask gqrx
  471. <span style="color: red">Installing gqrx has failed!</span></pre>
  472. <pre><span style="color: green">Installing jitsi</span>
  473. ==&gt; Caveats
  474. jitsi is built for Intel macOS and so requires Rosetta 2 to be installed.
  475. You can install Rosetta 2 with:
  476.  softwareupdate --install-rosetta --agree-to-license
  477. Note that it is very difficult to remove Rosetta 2 once it is installed.
  478.  
  479. ==&gt; Downloading https://github.com/jitsi/jitsi/releases/download/Jitsi-2.10/jitsi-2.10.5550.dmg
  480. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  481. ==&gt; Installing Cask jitsi
  482. Error: It seems there is already an App at '/Applications/Jitsi.app'.
  483. ==&gt; Purging files for version 2.10.5550 of Cask jitsi
  484. <span style="color: red">Installing jitsi has failed!</span></pre>
  485. <pre><span style="color: green">Installing keepassx</span>
  486. Password:
  487. ==&gt; Caveats
  488. keepassx is built for Intel macOS and so requires Rosetta 2 to be installed.
  489. You can install Rosetta 2 with:
  490.  softwareupdate --install-rosetta --agree-to-license
  491. Note that it is very difficult to remove Rosetta 2 once it is installed.
  492.  
  493. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/k/keepassx.rb
  494. ==&gt; Downloading https://www.keepassx.org/releases/2.0.3/KeePassX-2.0.3.dmg
  495. ==&gt; Installing Cask keepassx
  496. ==&gt; Changing ownership of paths required by keepassx with sudo; the password may be necessary.
  497. Error: It seems there is already an App at '/Applications/KeePassX.app'.
  498. ==&gt; Purging files for version 2.0.3 of Cask keepassx
  499. <span style="color: red">Installing keepassx has failed!</span></pre>
  500. <pre><span style="color: green">Installing sequel-pro</span>
  501. Warning: sequel-pro has been deprecated because it is discontinued upstream! It will be disabled on 2024-12-17.
  502. ==&gt; Caveats
  503. sequel-pro has been deprecated in favor of Sequel Ace.
  504.  brew install --cask sequel-ace
  505.  
  506. sequel-pro is built for Intel macOS and so requires Rosetta 2 to be installed.
  507. You can install Rosetta 2 with:
  508.  softwareupdate --install-rosetta --agree-to-license
  509. Note that it is very difficult to remove Rosetta 2 once it is installed.
  510.  
  511. ==&gt; Downloading https://github.com/sequelpro/sequelpro/releases/download/release-1.1.2/sequel-pro-1.1.2.dmg
  512. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  513. ==&gt; Installing Cask sequel-pro
  514. Error: It seems there is already an App at '/Applications/Sequel Pro.app'.
  515. ==&gt; Purging files for version 1.1.2 of Cask sequel-pro
  516. <span style="color: red">Installing sequel-pro has failed!</span></pre>
  517. <p>
  518. This can be fixed by running the mentioned command:
  519. </p>
  520. <pre>softwareupdate --install-rosetta --agree-to-license</pre>
  521. <p>
  522. With this in place, Intel-binaries will not be a problem anymore.<br>
  523. But as you can see there was actually a second failure in all these errors, which we are going to address next.
  524. </p>
  525. <p>
  526. <b>Old applications linger around in /Applications and block updates/re-installation</b><br>
  527. Homebrew nicely installed all the opensource applications into the new <var>/opt/homebrew</var>, but for the Casks which are distributed as binary application bundles and live in <var>/Applications</var> we end up with conflicts (as the new Homebrew installation does not know about the previously installed application bundles there).<br>
  528. This typically manifests in errors like these (also seen in the ones from the Rosetta section):
  529. </p>
  530. <pre><span style="color: green">Installing 0-ad</span>
  531. ==&gt; Downloading https://releases.wildfiregames.com/0ad-0.0.26-alpha-osx-aarch64.dmg
  532. ==&gt; Installing Cask 0-ad
  533. Error: It seems there is already an App at '/Applications/0 A.D..app'.
  534. ==&gt; Purging files for version 0.0.26-alpha of Cask 0-ad
  535. <span style="color: red">Installing 0-ad has failed!</span></pre>
  536. <pre><span style="color: green">Installing brave-browser</span>
  537. ==&gt; Downloading https://updates-cdn.bravesoftware.com/sparkle/Brave-Browser/stable-arm64/173.91/Brave-Browser-arm64.dmg
  538. ==&gt; Installing Cask brave-browser
  539. Error: It seems there is already an App at '/Applications/Brave Browser.app'.
  540. ==&gt; Purging files for version 1.73.91.0 of Cask brave-browser
  541. <span style="color: red">Installing brave-browser has failed!</span></pre>
  542. <pre><span style="color: green">Installing burp-suite</span>
  543. ==&gt; Downloading https://portswigger-cdn.net/burp/releases/download?product=community&amp;version=2024.10.3&amp;type=MacOsArm64
  544. ==&gt; Installing Cask burp-suite
  545. Error: It seems there is already an App at '/Applications/Burp Suite Community Edition.app'.
  546. ==&gt; Purging files for version 2024.10.3 of Cask burp-suite
  547. <span style="color: red">Installing burp-suite has failed!</span></pre>
  548. <pre><span style="color: green">Installing docker</span>
  549. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/d/docker.rb
  550. ==&gt; Downloading https://desktop.docker.com/mac/main/arm64/175267/Docker.dmg
  551. ==&gt; Installing Cask docker
  552. Error: It seems there is already an App at '/Applications/Docker.app'.
  553. ==&gt; Purging files for version 4.36.0,175267 of Cask docker
  554. <span style="color: red">Installing docker has failed!</span></pre>
  555. <pre><span style="color: green">Installing gitup</span>
  556. ==&gt; Downloading https://github.com/git-up/GitUp/releases/download/v1.4.2/GitUp.zip
  557. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  558. ==&gt; Installing Cask gitup
  559. Error: It seems there is already an App at '/Applications/GitUp.app'.
  560. ==&gt; Purging files for version 1.4.2 of Cask gitup
  561. <span style="color: red">Installing gitup has failed!</span></pre>
  562. <pre><span style="color: green">Installing keeweb</span>
  563. Password:
  564. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/k/keeweb.rb
  565. ==&gt; Downloading https://github.com/keeweb/keeweb/releases/download/v1.18.7/KeeWeb-1.18.7.mac.arm64.dmg
  566. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  567. ==&gt; Installing Cask keeweb
  568. ==&gt; Changing ownership of paths required by keeweb with sudo; the password may be necessary.
  569. chown: /Applications/KeeWeb.app/Contents/CodeResources: Operation not permitted
  570. [...]
  571. chown: /Applications/KeeWeb.app: Operation not permitted
  572. Error: It seems there is already an App at '/Applications/KeeWeb.app'.
  573. ==&gt; Purging files for version 1.18.7 of Cask keeweb
  574. <span style="color: red">Installing keeweb has failed!</span></pre>
  575. <pre><span style="color: green">Installing netnewswire</span>
  576. ==&gt; Downloading https://github.com/Ranchero-Software/NetNewsWire/releases/download/mac-6.1.4/NetNewsWire6.1.4.zip
  577. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  578. ==&gt; Installing Cask netnewswire
  579. Error: It seems there is already an App at '/Applications/NetNewsWire.app'.
  580. ==&gt; Purging files for version 6.1.4 of Cask netnewswire
  581. <span style="color: red">Installing netnewswire has failed!</span></pre>
  582. <pre><span style="color: green">Installing obs</span>
  583. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/o/obs.rb
  584. ==&gt; Downloading https://cdn-fastly.obsproject.com/downloads/OBS-Studio-30.2.3-macOS-Apple.dmg
  585. ==&gt; Installing Cask obs
  586. Error: It seems there is already an App at '/Applications/OBS.app'.
  587. ==&gt; Purging files for version 30.2.3 of Cask obs
  588. <span style="color: red">Installing obs has failed!</span></pre>
  589. <pre><span style="color: green">Installing transmission</span>
  590. ==&gt; Downloading https://github.com/transmission/transmission/releases/download/4.0.6/Transmission-4.0.6.dmg
  591. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  592. ==&gt; Installing Cask transmission
  593. Error: It seems there is already an App at '/Applications/Transmission.app'.
  594. ==&gt; Purging files for version 4.0.6 of Cask transmission
  595. <span style="color: red">Installing transmission has failed!</span></pre>
  596. <pre><span style="color: green">Installing tunnelblick</span>
  597. Password:
  598. ==&gt; Caveats
  599. For security reasons, tunnelblick must be installed to /Applications,
  600. and will request to be moved at launch.
  601.  
  602. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/t/tunnelblick.rb
  603. ==&gt; Downloading https://github.com/Tunnelblick/Tunnelblick/releases/download/v4.0.1/Tunnelblick_4.0.1_build_5971.dmg
  604. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  605. ==&gt; Installing Cask tunnelblick
  606. ==&gt; Changing ownership of paths required by tunnelblick with sudo; the password may be necessary.
  607. chown: /Applications/Tunnelblick.app/Contents/CodeResources: Operation not permitted
  608. [...]
  609. chown: /Applications/Tunnelblick.app: Operation not permitted
  610. Error: It seems there is already an App at '/Applications/Tunnelblick.app'.
  611. ==&gt; Purging files for version 4.0.1,5971 of Cask tunnelblick
  612. <span style="color: red">Installing tunnelblick has failed!</span></pre>
  613. <pre><span style="color: green">Installing vlc</span>
  614. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/v/vlc.rb
  615. ==&gt; Downloading https://get.videolan.org/vlc/3.0.21/macosx/vlc-3.0.21-arm64.dmg
  616. ==&gt; Downloading from http://mirror.easyname.ch/videolan/vlc/3.0.21/macosx/vlc-3.0.21-arm64.dmg
  617. ==&gt; Installing Cask vlc
  618. Error: It seems there is already an App at '/Applications/VLC.app'.
  619. ==&gt; Purging files for version 3.0.21 of Cask vlc
  620. <span style="color: red">Installing vlc has failed!</span></pre>
  621. <pre><span style="color: green">Installing wireshark</span>
  622. Password:
  623. ==&gt; Downloading https://2.na.dl.wireshark.org/osx/all-versions/Wireshark%204.4.2%20Arm%2064.dmg
  624. ==&gt; Installing Cask wireshark
  625. ==&gt; Running installer for wireshark with sudo; the password may be necessary.
  626. installer: Package name is ChmodBPF
  627. installer: Installing at base path /
  628. installer: The install was successful.
  629. ==&gt; Running installer for wireshark with sudo; the password may be necessary.
  630. Error: It seems there is already an App at '/Applications/Wireshark.app'.
  631. installer: Package name is Add Wireshark to the system PATH
  632. installer: Installing at base path /
  633. installer: The install was successful.
  634. ==&gt; Purging files for version 4.4.2 of Cask wireshark
  635. <span style="color: red">Installing wireshark has failed!</span></pre>
  636. <p>
  637. Now that we have the full list, here is how I fixed these errors:
  638. </p>
  639. <ul>
  640. <li>For each of them, move the existing application bundle from <var>/Applications</var> to Trash.</li>
  641. <li>Then trigger the installation again with: <pre>brew install --cask 0-ad
  642. brew install --cask brave-browser
  643. ...</pre></li>
  644. <li>The <var>--cask</var> part is important, as sometimes a headless source-only formula exists with the same name which does not include the GUI parts.<br>By using <var>--cask</var> we make sure that the upstream binary application bundle is used.</li>
  645. </ul>
  646. <p>
  647. With this, most of the fixing is concluded.<br>
  648. Thus let's go to the warnings and errors that I consciously ignore.
  649. </p>
  650. <p>
  651. <b>Warnings and errors to ignore</b><br>
  652. Some of the warnings and errors I consciously ignore.<br>
  653. A lot of them come from no longer maintained/available software which Homebrew no longer provides, or which have become obsolete as another software does the same job now.<br>
  654. Also in some cases it is just that I no longer use the software and thus do not need to spend the time to fix their installation problems.<br>
  655. Of course there are some errors in software which I still want to use and which I have not managed to fix yet, we will get to them later.<br>
  656. Here now the warnings and errors which I choose to ignore:
  657. </p>
  658. <pre><span style="color: green">Tapping homebrew/cask</span>
  659. Error: Tapping homebrew/cask is no longer typically necessary.
  660. Add --force if you are sure you need it for contributing to Homebrew.
  661. <span style="color: red">Tapping homebrew/cask has failed!</span></pre>
  662. <pre><span style="color: green">Tapping homebrew/core</span>
  663. Error: Tapping homebrew/core is no longer typically necessary.
  664. Add --force if you are sure you need it for contributing to Homebrew.
  665. <span style="color: red">Tapping homebrew/core has failed!</span></pre>
  666. <pre><span style="color: orange">Skipping gdb (no bottle for Apple Silicon)</span></pre>
  667. <pre><span style="color: green">Installing hping</span>
  668. Error: hping has been disabled because it is not maintained upstream! It was disabled on 2024-02-15.
  669. <span style="color: red">Installing hping has failed!</span></pre>
  670. <pre><span style="color: orange">Skipping hyperkit (no bottle for Apple Silicon)</span></pre>
  671. <pre><span style="color: green">Installing xhyve</span>
  672. <span style="color: orange">Warning:</span> 'xhyve' formula is unreadable: No available formula with the name "xhyve".
  673. Warning: No available formula with the name "xhyve".
  674. Error: No formulae found for xhyve.
  675. ==&gt; Searching for similarly named formulae...
  676. <span style="color: red">Installing xhyve has failed!</span></pre>
  677. <pre><span style="color: green">Installing jsmin</span>
  678. <span style="color: orange">Warning:</span> 'jsmin' formula is unreadable: No available formula with the name "jsmin". Did you mean jsmn, jasmin or jsign?
  679. Warning: No available formula with the name "jsmin". Did you mean jsmn, jasmin or jsign?
  680. ==&gt; Searching for similarly named formulae...
  681. ==&gt; Formulae
  682. jsmn
  683. jasmin
  684. jsign
  685.  
  686. To install jsmn, run:
  687.  brew install jsmn
  688. <span style="color: red">Installing jsmin has failed!</span></pre>
  689. <pre><span style="color: green">Installing sslyze</span>
  690. Error: sslyze has been disabled because it uses deprecated `openssl@1.1`! It was disabled on 2024-04-05.
  691. <span style="color: red">Installing sslyze has failed!</span></pre>
  692. <pre><span style="color: green">Installing virtualbox-extension-pack</span>
  693. Warning: Cask 'virtualbox-extension-pack' is unavailable: No Cask with this name exists.
  694. ==&gt; Searching for similarly named casks...
  695. ==&gt; Casks
  696. virtualbox@beta
  697.  
  698. To install virtualbox@beta, run:
  699.  brew install --cask virtualbox@beta
  700. <span style="color: red">Installing virtualbox-extension-pack has failed!</span></pre>
  701. <pre><span style="color: green">Installing docker-compose-completion</span>
  702. <span style="color: orange">Warning:</span> 'docker-compose-completion' formula is unreadable: No available formula with the name "docker-compose-completion". Did you mean docker-completion?
  703. Warning: No available formula with the name "docker-compose-completion". Did you mean docker-completion?
  704. ==&gt; Searching for similarly named formulae...
  705. ==&gt; Formulae
  706. docker-completion
  707.  
  708. To install docker-completion, run:
  709.  brew install docker-completion
  710. <span style="color: red">Installing docker-compose-completion has failed!</span></pre>
  711. <pre><span style="color: green">Installing visitors</span>
  712. Error: visitors has been disabled because it has a removed upstream repository! It was disabled on 2024-02-21.
  713. <span style="color: red">Installing visitors has failed!</span></pre>
  714. <pre><span style="color: green">Installing osxfuse</span>
  715. Password:
  716. ==&gt; Caveats
  717. `osxfuse` has been succeeded by `macfuse` as of version 4.0.0.
  718.  
  719. To update to a newer version, do:
  720.  brew uninstall osxfuse
  721.  brew install macfuse
  722.  
  723. osxfuse requires a kernel extension to work.
  724. If the installation fails, retry after you enable it in:
  725.  System Settings → Privacy &amp; Security
  726.  
  727. For more information, refer to vendor documentation or this Apple Technical Note:
  728.  https://developer.apple.com/library/content/technotes/tn2459/_index.html
  729.  
  730. You must reboot for the installation of osxfuse to take effect.
  731.  
  732. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/o/osxfuse.rb
  733. ==&gt; Downloading https://github.com/osxfuse/osxfuse/releases/download/osxfuse-3.11.2/osxfuse-3.11.2.dmg
  734. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  735. ==&gt; Installing Cask osxfuse
  736. ==&gt; Running installer for osxfuse with sudo; the password may be necessary.
  737. installer: Error - Das FUSE for macOS Installationspacket ist nicht kompatibel mit dieser macOS Version.
  738. Error: Failure while executing; `/usr/bin/sudo -u root -E LOGNAME=aj USER=aj USERNAME=aj -- /usr/sbin/installer -pkg /opt/homebrew/Caskroom/osxfuse/3.11.2/Extras/FUSE\ for\ macOS\ 3.11.2.pkg -target /` exited with 1. Here's the output:
  739. installer: Error - Das FUSE for macOS Installationspacket ist nicht kompatibel mit dieser macOS Version.
  740. ==&gt; Purging files for version 3.11.2 of Cask osxfuse
  741. <span style="color: red">Installing osxfuse has failed!</span></pre>
  742. <pre><span style="color: green">Installing tuntap</span>
  743. Warning: Cask 'tuntap' is unavailable: No Cask with this name exists.
  744. ==&gt; Searching for similarly named casks...
  745. ==&gt; Casks
  746. tunetag
  747.  
  748. To install tunetag, run:
  749.  brew install --cask tunetag
  750. <span style="color: red">Installing tuntap has failed!</span></pre>
  751. <pre><span style="color: green">Installing mailtrackerblocker</span>
  752. Warning: mailtrackerblocker has been deprecated because it is now exclusively distributed on the Mac App Store! It will be disabled on 2025-04-22.
  753. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/m/mailtrackerblocker.rb
  754. Error: This cask does not run on macOS versions newer than Ventura.
  755. <span style="color: red">Installing mailtrackerblocker has failed!</span></pre>
  756. <p>
  757. This concludes the warnings and errors I ignored.<br>
  758. And there is a little exception.<br>
  759. For mailtrackerblocker I did not completely ignore the error, but rather installed the paid <a href="https://apparition47.github.io/MailTrackerBlocker/" title="MailTrackerBlocker for Mail on macOS">MailTrackerBlocker for Mail</a> application from the App Store.
  760. </p>
  761. <p>
  762. <b>Cleaning up the old Homebrew installation</b><br>
  763. We still have all the no longer needed Intel-binaries and old Homebrew framework in <var>/usr/local</var>.<br>
  764. Time to clean this up.
  765. Homebrew nicely provides a script to help (partially) with this:
  766. </p>
  767. <pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/uninstall.sh)" -- --path=/usr/local</pre>
  768. <p>
  769. This will remove most of the old Homebrew installation but will likely fail to remove everything.<br>
  770. Especially in my situation with years of cruft accumulated, this was the case.<br>
  771. I ended up with the following output from the cleanup script:
  772. </p>
  773. <pre>==&gt; /usr/bin/sudo rmdir /usr/local
  774. rmdir: /usr/local: Operation not permitted
  775. Warning: Failed during: /usr/bin/sudo rmdir /usr/local
  776. Warning: Homebrew partially uninstalled (but there were steps that failed)!
  777. To finish uninstalling rerun this script with `sudo`.
  778. The following possible Homebrew files were not deleted:
  779. /usr/local/.com.apple.installer.keep
  780. /usr/local/Cellar/
  781. /usr/local/Frameworks/
  782. /usr/local/Homebrew/
  783. /usr/local/MacGPG2/
  784. /usr/local/bin/
  785. /usr/local/etc/
  786. /usr/local/include/
  787. /usr/local/lib/
  788. /usr/local/man/
  789. /usr/local/opt/
  790. /usr/local/remotedesktop/
  791. /usr/local/sbin/
  792. /usr/local/share/
  793. /usr/local/tests/
  794. /usr/local/var/
  795. You may wish to remove them yourself.</pre>
  796. <p>
  797. I manually went through all these folders and removed what I could identify as obsolete and no longer needed leftovers.<br>
  798. Important though for example the MacGPG2 folder seems to come from the GPGTools installation, thus be aware that there are other things than Homebrew which might have installed some software under <var>/usr/local</var> and not everyhting must necessarily be removed.
  799. </p>
  800. <p>
  801. <b>Unsolved problems</b><br>
  802. As mentioned there are some things which I haven't figured out how to fix yet.
  803. <p>
  804. <p>
  805. I'm missing a good solution for <a href="https://vgough.github.io/encfs/" title="EncFS">encfs</a> (which is no longer provided by Homebrew due to license changes of the underlying MacFuse project).
  806. Compiling from source (at least through Homebrew) is not supported either (as it is marked as Linux-only and complilation is not supported anymore on macOS).<br>
  807. <b>Update:</b> found a solution for <a href="https://blog.x-way.org/Mac/2024/12/03/How-to-install-EncFS-on-macOS-Sequoia.html" title="x-log - How to install EncFS on MacOS Sequoia">how to install EncFS on macOS Sequoia</a>.
  808. </p>
  809. <p>
  810. Another missing thing (which is more a problem of not having time to deal with it yet), is the Perl ecosystem including CPAN package management.
  811. Here probably some research to find the canonical way for installing Perl in macOS 15 is all I need. 🐪
  812. </p>
  813. ]]></description>
  814.    <content:encoded><![CDATA[<p>
  815. A big part of the time used to <a href="https://blog.x-way.org/Mac/2024/11/30/Move-from-2017-Intel-MacBook-Pro-to-2024-M4-MacBook-Pro.html" title="x-log - Move from 2017 Intel MacBook Pro to 2024 M4 MacBook Pro">move from my 2017 Intel MacBook Pro to my new 2024 M4 MacBook Pro</a> was spent on migrating my <a href="https://brew.sh/" title="Homebrew — The Missing Package Manager for macOS">Homebrew installation</a>.
  816. </p>
  817. <p>
  818. There are three aspects to the migration.
  819. </p>
  820. <ul>
  821. <li>One is the change in CPU architecture (which means to replace my Intel-only binaries with arm64 binaries).</li>
  822. <li>The other one is the change of the Homebrew root folder from <var>/usr/local</var> to <var>/opt/homebrew</var>.</li>
  823. <li>And the last one is the change in OS version (from macOS 13 to macOS 15).</li>
  824. </ul>
  825. <p>
  826. The impact of the change in CPU architecture was mostly taken care of by enabling the Rosetta 2 emulator to run Intel-binaries on the M4.<br>
  827. This immediately fixed the problem of my Terminal windows auto-closing on startup (as they now no longer failed to run the zsh Intel-binary).<br>
  828. But it did not solve all problems, particularly annoying was that vim could not be started and always failed with the following error:
  829. </p>
  830. <pre>dyld[31382]: Library not loaded: /System/Library/Perl/5.30/darwin-thread-multi-2level/CORE/libperl.dylib
  831.  Referenced from: &lt;77AC96DE-0453-3E1C-B442-EFE624110BAE&gt; /usr/local/Cellar/vim/9.1.0750_1/bin/vim
  832.  Reason: tried: '/System/Library/Perl/5.30/darwin-thread-multi-2level/CORE/libperl.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/System/Library/Perl/5.30/darwin-thread-multi-2level/CORE/libperl.dylib' (no such file), '/System/Library/Perl/5.30/darwin-thread-multi-2level/CORE/libperl.dylib' (no such file, not in dyld cache), '/usr/local/lib/libperl.dylib' (no such file), '/usr/lib/libperl.dylib' (no such file, not in dyld cache)</pre>
  833. <p>
  834. My workaround for this was to use the default vim that comes bundled with macOS, by typing <kbd>/usr/bin/vim</kbd>.<br>
  835. Although it complained about some unsupported parts in my <var>.vimrc</var>, it at least started up and was usable enough to edit files.<br>
  836. The error itself seems due to some Perl system libraries that vim was compiled with and which now no longer exist in the new macOS version.<br>
  837. This is a typical problem which can be solved by re-installing Homebrew.
  838. </p>
  839. <p>
  840. <b>Re-installing Homebrew</b><br>
  841. The steps below follow <a href="https://docs.brew.sh/Common-Issues#unintentional-dual-homebrew-installations" title="Common Issues - Unintentional dual Homebrew installations">this FAQ entry</a> and are extended with what was needed to make it work for my situation.<br>
  842. Your mileage might vary!
  843. </p>
  844. <ol>
  845. <li>In the Terminal.app settings, set the login shell to <var>Default</var>. This to avoid Rosetta's Intel emulated zsh from the previous installation interfering with things.</li>
  846. <li>Verify that you're running in native ARM mode with the <kbd>arch</kbd> command. It should return <var>arm64</var>.</li>
  847. <li>Create a dump of the previous Homebrew installation by explicitly running brew through Rosetta's Intel emulation: <pre>arch -x86_64 /usr/local/bin/brew bundle dump --global</pre></li>
  848. <li>Review the resulting <var>~/.Brewfile</var> and adjust as desired (I didn't make any adjustments).</li>
  849. <li>Ensure that native arm binaries are preferred over Intel binaries from the previous installation: <pre>export PATH=/bin:/usr/bin:/sbin:/usr/sbin:$PATH</pre></li>
  850. <li>Install homebrew into <var>/opt/homebrew</var> with: <pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"</pre></li>
  851. <li>Adjust your shell config file to prefer <var>/opt/homebrew/bin</var> over <var>/usr/local/bin</var> in the PATH.<br>As I manually set PATH in my <var>.zshrc</var>, I needed to adjust it. Following these commands recommended by the brew installer was not enough! <pre><b><span style="color: blue">==&gt;</span> Next steps:</b>
  852. - Run these commands in your terminal to add Homebrew to your <b>PATH</b>:
  853.    echo &gt;&gt; /Users/aj/.zprofile
  854.    echo 'eval "$(/opt/homebrew/bin/brew shellenv)"' &gt;&gt; /Users/aj/.zprofile
  855.    eval "$(/opt/homebrew/bin/brew shellenv)"</pre></li>
  856. <li>Open a fresh terminal window and verify with <kbd>which brew</kbd>, it must return <var>/opt/homebrew/bin/brew</var>.</li>
  857. <li>Now have brew install all the applications from the dump in the <var>~/.Brewfile</var>: <pre>/opt/homebrew/bin/brew bundle install --global</pre></li>
  858. <li>This process will print some warnings and errors, thus make sure to keep the output.<br>I will go through all the errors and warnings I encountered and list how I fixed them below (for the ones I could fix, unfortunately not all have been fixed yet).<br>It usually ends with a summary of the number of failures: <pre><span style="color: red">Homebrew Bundle failed! 30 Brewfile dependencies failed to install.Homebrew Bundle failed! 30 Brewfile dependencies failed to install.</span></pre></li>
  859. <li>Once the process is completed and you see the above summary, open the Terminal.app settings and set the Login shell to <var>/opt/homebrew/bin/zsh</var></li>
  860. <li>Open a fresh terminal window and verify that you are now running in native arm64 mode with <kbd>arch</kbd>.</li>
  861. <li>Now we are ready to address the errors, and then at the end we will remove the old Homebrew installation under <var>/usr/local</var>.</li>
  862. </ol>
  863. <p>
  864. <b>Outdated Xcode and missing Xcode command-line utilities</b><br>
  865. Due to the change in macOS version, the Xcode installation was outdated and also no usable command-line utilities were available.<br>
  866. This usually manifests in errors like these:
  867. </p>
  868. <pre><span style="color: green">Installing ssh-audit</span>
  869. ==&gt; Fetching ssh-audit
  870. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-core/723e7ef695e15c790aab727c1da11a2a4610ad53/Formula/s/ssh-audit.rb
  871. ==&gt; Cloning https://github.com/jtesta/ssh-audit.git
  872. Cloning into '/Users/aj/Library/Caches/Homebrew/ssh-audit--git'...
  873. ==&gt; Checking out branch master
  874. Already on 'master'
  875. Your branch is up to date with 'origin/master'.
  876. Error: Your Xcode (15.1) at /Applications/Xcode.app is too outdated.
  877. Please update to Xcode 16.0 (or delete it).
  878. Xcode can be updated from the App Store.
  879.  
  880. Error: Your Command Line Tools are too outdated.
  881. Update them from Software Update in System Settings.
  882.  
  883. If that doesn't show you any updates, run:
  884.  sudo rm -rf /Library/Developer/CommandLineTools
  885.  sudo xcode-select --install
  886.  
  887. Alternatively, manually download them from:
  888.  https://developer.apple.com/download/all/.
  889. You should download the Command Line Tools for Xcode 16.0.
  890.  
  891. <span style="color: red">Installing ssh-audit has failed!</span></pre>
  892. <pre><span style="color: green">Installing tdsmith/ham/direwolf</span>
  893. ==&gt; Fetching dependencies for tdsmith/ham/direwolf: portaudio
  894. ==&gt; Fetching portaudio
  895. ==&gt; Downloading https://ghcr.io/v2/homebrew/core/portaudio/manifests/19.7.0-1
  896. ==&gt; Downloading https://ghcr.io/v2/homebrew/core/portaudio/blobs/sha256:8ad9f1c15a4bc9c05a9dd184b53b8f5f5d13a2458a70535bfb01e54ce4f8b4bd
  897. ==&gt; Fetching tdsmith/ham/direwolf
  898. ==&gt; Downloading https://github.com/wb2osz/direwolf/archive/1.4-dev-E.tar.gz
  899. ==&gt; Downloading from https://codeload.github.com/wb2osz/direwolf/tar.gz/refs/tags/1.4-dev-E
  900. ==&gt; Installing direwolf from tdsmith/ham
  901. Error: Your Xcode (15.1) at /Applications/Xcode.app is too outdated.
  902. Please update to Xcode 16.0 (or delete it).
  903. Xcode can be updated from the App Store.
  904.  
  905. Error: Your Command Line Tools are too outdated.
  906. Update them from Software Update in System Settings.
  907.  
  908. If that doesn't show you any updates, run:
  909.  sudo rm -rf /Library/Developer/CommandLineTools
  910.  sudo xcode-select --install
  911.  
  912. Alternatively, manually download them from:
  913.  https://developer.apple.com/download/all/.
  914. You should download the Command Line Tools for Xcode 16.0.
  915.  
  916. <span style="color: red">Installing tdsmith/ham/direwolf has failed!</span></pre>
  917. <p>
  918. This can be fixed in two steps.<br>
  919. First update Xcode via the App Store.<br>
  920. Then run the mentioned commands to install/update the command-line utilities:
  921. </p>
  922. <pre>sudo rm -rf /Library/Developer/CommandLineTools
  923. sudo xcode-select --install</pre>
  924. <p>
  925. With the latest Xcode and command-line utilities in place, trigger a new installation attempt for the affected applications:
  926. </p>
  927. <pre>brew install ssh-audit
  928. brew install tdsmith/ham/direwolf</pre>
  929. <p>
  930. <b>Missing Rosetta 2 Intel emulation</b><br>
  931. Some of the Casks distributed by Homebrew are currently only available as Intel-binaries.<br>
  932. This usually manifests in warnings like these:
  933. </p>
  934. <pre><span style="color: green">Installing gqrx</span>
  935. ==&gt; Caveats
  936. gqrx is built for Intel macOS and so requires Rosetta 2 to be installed.
  937. You can install Rosetta 2 with:
  938.  softwareupdate --install-rosetta --agree-to-license
  939. Note that it is very difficult to remove Rosetta 2 once it is installed.
  940.  
  941. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/g/gqrx.rb
  942. ==&gt; Downloading https://github.com/gqrx-sdr/gqrx/releases/download/v2.17.5/Gqrx-2.17.5.dmg
  943. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  944. ==&gt; Installing Cask gqrx
  945. Error: It seems there is already an App at '/Applications/Gqrx.app'.
  946. ==&gt; Purging files for version 2.17.5 of Cask gqrx
  947. <span style="color: red">Installing gqrx has failed!</span></pre>
  948. <pre><span style="color: green">Installing jitsi</span>
  949. ==&gt; Caveats
  950. jitsi is built for Intel macOS and so requires Rosetta 2 to be installed.
  951. You can install Rosetta 2 with:
  952.  softwareupdate --install-rosetta --agree-to-license
  953. Note that it is very difficult to remove Rosetta 2 once it is installed.
  954.  
  955. ==&gt; Downloading https://github.com/jitsi/jitsi/releases/download/Jitsi-2.10/jitsi-2.10.5550.dmg
  956. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  957. ==&gt; Installing Cask jitsi
  958. Error: It seems there is already an App at '/Applications/Jitsi.app'.
  959. ==&gt; Purging files for version 2.10.5550 of Cask jitsi
  960. <span style="color: red">Installing jitsi has failed!</span></pre>
  961. <pre><span style="color: green">Installing keepassx</span>
  962. Password:
  963. ==&gt; Caveats
  964. keepassx is built for Intel macOS and so requires Rosetta 2 to be installed.
  965. You can install Rosetta 2 with:
  966.  softwareupdate --install-rosetta --agree-to-license
  967. Note that it is very difficult to remove Rosetta 2 once it is installed.
  968.  
  969. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/k/keepassx.rb
  970. ==&gt; Downloading https://www.keepassx.org/releases/2.0.3/KeePassX-2.0.3.dmg
  971. ==&gt; Installing Cask keepassx
  972. ==&gt; Changing ownership of paths required by keepassx with sudo; the password may be necessary.
  973. Error: It seems there is already an App at '/Applications/KeePassX.app'.
  974. ==&gt; Purging files for version 2.0.3 of Cask keepassx
  975. <span style="color: red">Installing keepassx has failed!</span></pre>
  976. <pre><span style="color: green">Installing sequel-pro</span>
  977. Warning: sequel-pro has been deprecated because it is discontinued upstream! It will be disabled on 2024-12-17.
  978. ==&gt; Caveats
  979. sequel-pro has been deprecated in favor of Sequel Ace.
  980.  brew install --cask sequel-ace
  981.  
  982. sequel-pro is built for Intel macOS and so requires Rosetta 2 to be installed.
  983. You can install Rosetta 2 with:
  984.  softwareupdate --install-rosetta --agree-to-license
  985. Note that it is very difficult to remove Rosetta 2 once it is installed.
  986.  
  987. ==&gt; Downloading https://github.com/sequelpro/sequelpro/releases/download/release-1.1.2/sequel-pro-1.1.2.dmg
  988. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  989. ==&gt; Installing Cask sequel-pro
  990. Error: It seems there is already an App at '/Applications/Sequel Pro.app'.
  991. ==&gt; Purging files for version 1.1.2 of Cask sequel-pro
  992. <span style="color: red">Installing sequel-pro has failed!</span></pre>
  993. <p>
  994. This can be fixed by running the mentioned command:
  995. </p>
  996. <pre>softwareupdate --install-rosetta --agree-to-license</pre>
  997. <p>
  998. With this in place, Intel-binaries will not be a problem anymore.<br>
  999. But as you can see there was actually a second failure in all these errors, which we are going to address next.
  1000. </p>
  1001. <p>
  1002. <b>Old applications linger around in /Applications and block updates/re-installation</b><br>
  1003. Homebrew nicely installed all the opensource applications into the new <var>/opt/homebrew</var>, but for the Casks which are distributed as binary application bundles and live in <var>/Applications</var> we end up with conflicts (as the new Homebrew installation does not know about the previously installed application bundles there).<br>
  1004. This typically manifests in errors like these (also seen in the ones from the Rosetta section):
  1005. </p>
  1006. <pre><span style="color: green">Installing 0-ad</span>
  1007. ==&gt; Downloading https://releases.wildfiregames.com/0ad-0.0.26-alpha-osx-aarch64.dmg
  1008. ==&gt; Installing Cask 0-ad
  1009. Error: It seems there is already an App at '/Applications/0 A.D..app'.
  1010. ==&gt; Purging files for version 0.0.26-alpha of Cask 0-ad
  1011. <span style="color: red">Installing 0-ad has failed!</span></pre>
  1012. <pre><span style="color: green">Installing brave-browser</span>
  1013. ==&gt; Downloading https://updates-cdn.bravesoftware.com/sparkle/Brave-Browser/stable-arm64/173.91/Brave-Browser-arm64.dmg
  1014. ==&gt; Installing Cask brave-browser
  1015. Error: It seems there is already an App at '/Applications/Brave Browser.app'.
  1016. ==&gt; Purging files for version 1.73.91.0 of Cask brave-browser
  1017. <span style="color: red">Installing brave-browser has failed!</span></pre>
  1018. <pre><span style="color: green">Installing burp-suite</span>
  1019. ==&gt; Downloading https://portswigger-cdn.net/burp/releases/download?product=community&amp;version=2024.10.3&amp;type=MacOsArm64
  1020. ==&gt; Installing Cask burp-suite
  1021. Error: It seems there is already an App at '/Applications/Burp Suite Community Edition.app'.
  1022. ==&gt; Purging files for version 2024.10.3 of Cask burp-suite
  1023. <span style="color: red">Installing burp-suite has failed!</span></pre>
  1024. <pre><span style="color: green">Installing docker</span>
  1025. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/d/docker.rb
  1026. ==&gt; Downloading https://desktop.docker.com/mac/main/arm64/175267/Docker.dmg
  1027. ==&gt; Installing Cask docker
  1028. Error: It seems there is already an App at '/Applications/Docker.app'.
  1029. ==&gt; Purging files for version 4.36.0,175267 of Cask docker
  1030. <span style="color: red">Installing docker has failed!</span></pre>
  1031. <pre><span style="color: green">Installing gitup</span>
  1032. ==&gt; Downloading https://github.com/git-up/GitUp/releases/download/v1.4.2/GitUp.zip
  1033. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  1034. ==&gt; Installing Cask gitup
  1035. Error: It seems there is already an App at '/Applications/GitUp.app'.
  1036. ==&gt; Purging files for version 1.4.2 of Cask gitup
  1037. <span style="color: red">Installing gitup has failed!</span></pre>
  1038. <pre><span style="color: green">Installing keeweb</span>
  1039. Password:
  1040. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/k/keeweb.rb
  1041. ==&gt; Downloading https://github.com/keeweb/keeweb/releases/download/v1.18.7/KeeWeb-1.18.7.mac.arm64.dmg
  1042. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  1043. ==&gt; Installing Cask keeweb
  1044. ==&gt; Changing ownership of paths required by keeweb with sudo; the password may be necessary.
  1045. chown: /Applications/KeeWeb.app/Contents/CodeResources: Operation not permitted
  1046. [...]
  1047. chown: /Applications/KeeWeb.app: Operation not permitted
  1048. Error: It seems there is already an App at '/Applications/KeeWeb.app'.
  1049. ==&gt; Purging files for version 1.18.7 of Cask keeweb
  1050. <span style="color: red">Installing keeweb has failed!</span></pre>
  1051. <pre><span style="color: green">Installing netnewswire</span>
  1052. ==&gt; Downloading https://github.com/Ranchero-Software/NetNewsWire/releases/download/mac-6.1.4/NetNewsWire6.1.4.zip
  1053. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  1054. ==&gt; Installing Cask netnewswire
  1055. Error: It seems there is already an App at '/Applications/NetNewsWire.app'.
  1056. ==&gt; Purging files for version 6.1.4 of Cask netnewswire
  1057. <span style="color: red">Installing netnewswire has failed!</span></pre>
  1058. <pre><span style="color: green">Installing obs</span>
  1059. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/o/obs.rb
  1060. ==&gt; Downloading https://cdn-fastly.obsproject.com/downloads/OBS-Studio-30.2.3-macOS-Apple.dmg
  1061. ==&gt; Installing Cask obs
  1062. Error: It seems there is already an App at '/Applications/OBS.app'.
  1063. ==&gt; Purging files for version 30.2.3 of Cask obs
  1064. <span style="color: red">Installing obs has failed!</span></pre>
  1065. <pre><span style="color: green">Installing transmission</span>
  1066. ==&gt; Downloading https://github.com/transmission/transmission/releases/download/4.0.6/Transmission-4.0.6.dmg
  1067. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  1068. ==&gt; Installing Cask transmission
  1069. Error: It seems there is already an App at '/Applications/Transmission.app'.
  1070. ==&gt; Purging files for version 4.0.6 of Cask transmission
  1071. <span style="color: red">Installing transmission has failed!</span></pre>
  1072. <pre><span style="color: green">Installing tunnelblick</span>
  1073. Password:
  1074. ==&gt; Caveats
  1075. For security reasons, tunnelblick must be installed to /Applications,
  1076. and will request to be moved at launch.
  1077.  
  1078. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/t/tunnelblick.rb
  1079. ==&gt; Downloading https://github.com/Tunnelblick/Tunnelblick/releases/download/v4.0.1/Tunnelblick_4.0.1_build_5971.dmg
  1080. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  1081. ==&gt; Installing Cask tunnelblick
  1082. ==&gt; Changing ownership of paths required by tunnelblick with sudo; the password may be necessary.
  1083. chown: /Applications/Tunnelblick.app/Contents/CodeResources: Operation not permitted
  1084. [...]
  1085. chown: /Applications/Tunnelblick.app: Operation not permitted
  1086. Error: It seems there is already an App at '/Applications/Tunnelblick.app'.
  1087. ==&gt; Purging files for version 4.0.1,5971 of Cask tunnelblick
  1088. <span style="color: red">Installing tunnelblick has failed!</span></pre>
  1089. <pre><span style="color: green">Installing vlc</span>
  1090. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/v/vlc.rb
  1091. ==&gt; Downloading https://get.videolan.org/vlc/3.0.21/macosx/vlc-3.0.21-arm64.dmg
  1092. ==&gt; Downloading from http://mirror.easyname.ch/videolan/vlc/3.0.21/macosx/vlc-3.0.21-arm64.dmg
  1093. ==&gt; Installing Cask vlc
  1094. Error: It seems there is already an App at '/Applications/VLC.app'.
  1095. ==&gt; Purging files for version 3.0.21 of Cask vlc
  1096. <span style="color: red">Installing vlc has failed!</span></pre>
  1097. <pre><span style="color: green">Installing wireshark</span>
  1098. Password:
  1099. ==&gt; Downloading https://2.na.dl.wireshark.org/osx/all-versions/Wireshark%204.4.2%20Arm%2064.dmg
  1100. ==&gt; Installing Cask wireshark
  1101. ==&gt; Running installer for wireshark with sudo; the password may be necessary.
  1102. installer: Package name is ChmodBPF
  1103. installer: Installing at base path /
  1104. installer: The install was successful.
  1105. ==&gt; Running installer for wireshark with sudo; the password may be necessary.
  1106. Error: It seems there is already an App at '/Applications/Wireshark.app'.
  1107. installer: Package name is Add Wireshark to the system PATH
  1108. installer: Installing at base path /
  1109. installer: The install was successful.
  1110. ==&gt; Purging files for version 4.4.2 of Cask wireshark
  1111. <span style="color: red">Installing wireshark has failed!</span></pre>
  1112. <p>
  1113. Now that we have the full list, here is how I fixed these errors:
  1114. </p>
  1115. <ul>
  1116. <li>For each of them, move the existing application bundle from <var>/Applications</var> to Trash.</li>
  1117. <li>Then trigger the installation again with: <pre>brew install --cask 0-ad
  1118. brew install --cask brave-browser
  1119. ...</pre></li>
  1120. <li>The <var>--cask</var> part is important, as sometimes a headless source-only formula exists with the same name which does not include the GUI parts.<br>By using <var>--cask</var> we make sure that the upstream binary application bundle is used.</li>
  1121. </ul>
  1122. <p>
  1123. With this, most of the fixing is concluded.<br>
  1124. Thus let's go to the warnings and errors that I consciously ignore.
  1125. </p>
  1126. <p>
  1127. <b>Warnings and errors to ignore</b><br>
  1128. Some of the warnings and errors I consciously ignore.<br>
  1129. A lot of them come from no longer maintained/available software which Homebrew no longer provides, or which have become obsolete as another software does the same job now.<br>
  1130. Also in some cases it is just that I no longer use the software and thus do not need to spend the time to fix their installation problems.<br>
  1131. Of course there are some errors in software which I still want to use and which I have not managed to fix yet, we will get to them later.<br>
  1132. Here now the warnings and errors which I choose to ignore:
  1133. </p>
  1134. <pre><span style="color: green">Tapping homebrew/cask</span>
  1135. Error: Tapping homebrew/cask is no longer typically necessary.
  1136. Add --force if you are sure you need it for contributing to Homebrew.
  1137. <span style="color: red">Tapping homebrew/cask has failed!</span></pre>
  1138. <pre><span style="color: green">Tapping homebrew/core</span>
  1139. Error: Tapping homebrew/core is no longer typically necessary.
  1140. Add --force if you are sure you need it for contributing to Homebrew.
  1141. <span style="color: red">Tapping homebrew/core has failed!</span></pre>
  1142. <pre><span style="color: orange">Skipping gdb (no bottle for Apple Silicon)</span></pre>
  1143. <pre><span style="color: green">Installing hping</span>
  1144. Error: hping has been disabled because it is not maintained upstream! It was disabled on 2024-02-15.
  1145. <span style="color: red">Installing hping has failed!</span></pre>
  1146. <pre><span style="color: orange">Skipping hyperkit (no bottle for Apple Silicon)</span></pre>
  1147. <pre><span style="color: green">Installing xhyve</span>
  1148. <span style="color: orange">Warning:</span> 'xhyve' formula is unreadable: No available formula with the name "xhyve".
  1149. Warning: No available formula with the name "xhyve".
  1150. Error: No formulae found for xhyve.
  1151. ==&gt; Searching for similarly named formulae...
  1152. <span style="color: red">Installing xhyve has failed!</span></pre>
  1153. <pre><span style="color: green">Installing jsmin</span>
  1154. <span style="color: orange">Warning:</span> 'jsmin' formula is unreadable: No available formula with the name "jsmin". Did you mean jsmn, jasmin or jsign?
  1155. Warning: No available formula with the name "jsmin". Did you mean jsmn, jasmin or jsign?
  1156. ==&gt; Searching for similarly named formulae...
  1157. ==&gt; Formulae
  1158. jsmn
  1159. jasmin
  1160. jsign
  1161.  
  1162. To install jsmn, run:
  1163.  brew install jsmn
  1164. <span style="color: red">Installing jsmin has failed!</span></pre>
  1165. <pre><span style="color: green">Installing sslyze</span>
  1166. Error: sslyze has been disabled because it uses deprecated `openssl@1.1`! It was disabled on 2024-04-05.
  1167. <span style="color: red">Installing sslyze has failed!</span></pre>
  1168. <pre><span style="color: green">Installing virtualbox-extension-pack</span>
  1169. Warning: Cask 'virtualbox-extension-pack' is unavailable: No Cask with this name exists.
  1170. ==&gt; Searching for similarly named casks...
  1171. ==&gt; Casks
  1172. virtualbox@beta
  1173.  
  1174. To install virtualbox@beta, run:
  1175.  brew install --cask virtualbox@beta
  1176. <span style="color: red">Installing virtualbox-extension-pack has failed!</span></pre>
  1177. <pre><span style="color: green">Installing docker-compose-completion</span>
  1178. <span style="color: orange">Warning:</span> 'docker-compose-completion' formula is unreadable: No available formula with the name "docker-compose-completion". Did you mean docker-completion?
  1179. Warning: No available formula with the name "docker-compose-completion". Did you mean docker-completion?
  1180. ==&gt; Searching for similarly named formulae...
  1181. ==&gt; Formulae
  1182. docker-completion
  1183.  
  1184. To install docker-completion, run:
  1185.  brew install docker-completion
  1186. <span style="color: red">Installing docker-compose-completion has failed!</span></pre>
  1187. <pre><span style="color: green">Installing visitors</span>
  1188. Error: visitors has been disabled because it has a removed upstream repository! It was disabled on 2024-02-21.
  1189. <span style="color: red">Installing visitors has failed!</span></pre>
  1190. <pre><span style="color: green">Installing osxfuse</span>
  1191. Password:
  1192. ==&gt; Caveats
  1193. `osxfuse` has been succeeded by `macfuse` as of version 4.0.0.
  1194.  
  1195. To update to a newer version, do:
  1196.  brew uninstall osxfuse
  1197.  brew install macfuse
  1198.  
  1199. osxfuse requires a kernel extension to work.
  1200. If the installation fails, retry after you enable it in:
  1201.  System Settings → Privacy &amp; Security
  1202.  
  1203. For more information, refer to vendor documentation or this Apple Technical Note:
  1204.  https://developer.apple.com/library/content/technotes/tn2459/_index.html
  1205.  
  1206. You must reboot for the installation of osxfuse to take effect.
  1207.  
  1208. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/o/osxfuse.rb
  1209. ==&gt; Downloading https://github.com/osxfuse/osxfuse/releases/download/osxfuse-3.11.2/osxfuse-3.11.2.dmg
  1210. ==&gt; Downloading from https://objects.githubusercontent.com/github-production-release-asset-[...]
  1211. ==&gt; Installing Cask osxfuse
  1212. ==&gt; Running installer for osxfuse with sudo; the password may be necessary.
  1213. installer: Error - Das FUSE for macOS Installationspacket ist nicht kompatibel mit dieser macOS Version.
  1214. Error: Failure while executing; `/usr/bin/sudo -u root -E LOGNAME=aj USER=aj USERNAME=aj -- /usr/sbin/installer -pkg /opt/homebrew/Caskroom/osxfuse/3.11.2/Extras/FUSE\ for\ macOS\ 3.11.2.pkg -target /` exited with 1. Here's the output:
  1215. installer: Error - Das FUSE for macOS Installationspacket ist nicht kompatibel mit dieser macOS Version.
  1216. ==&gt; Purging files for version 3.11.2 of Cask osxfuse
  1217. <span style="color: red">Installing osxfuse has failed!</span></pre>
  1218. <pre><span style="color: green">Installing tuntap</span>
  1219. Warning: Cask 'tuntap' is unavailable: No Cask with this name exists.
  1220. ==&gt; Searching for similarly named casks...
  1221. ==&gt; Casks
  1222. tunetag
  1223.  
  1224. To install tunetag, run:
  1225.  brew install --cask tunetag
  1226. <span style="color: red">Installing tuntap has failed!</span></pre>
  1227. <pre><span style="color: green">Installing mailtrackerblocker</span>
  1228. Warning: mailtrackerblocker has been deprecated because it is now exclusively distributed on the Mac App Store! It will be disabled on 2025-04-22.
  1229. ==&gt; Downloading https://raw.githubusercontent.com/Homebrew/homebrew-cask/1ef784f287cce93f2bb54bea66ae7ac0953f623b/Casks/m/mailtrackerblocker.rb
  1230. Error: This cask does not run on macOS versions newer than Ventura.
  1231. <span style="color: red">Installing mailtrackerblocker has failed!</span></pre>
  1232. <p>
  1233. This concludes the warnings and errors I ignored.<br>
  1234. And there is a little exception.<br>
  1235. For mailtrackerblocker I did not completely ignore the error, but rather installed the paid <a href="https://apparition47.github.io/MailTrackerBlocker/" title="MailTrackerBlocker for Mail on macOS">MailTrackerBlocker for Mail</a> application from the App Store.
  1236. </p>
  1237. <p>
  1238. <b>Cleaning up the old Homebrew installation</b><br>
  1239. We still have all the no longer needed Intel-binaries and old Homebrew framework in <var>/usr/local</var>.<br>
  1240. Time to clean this up.
  1241. Homebrew nicely provides a script to help (partially) with this:
  1242. </p>
  1243. <pre>/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/uninstall.sh)" -- --path=/usr/local</pre>
  1244. <p>
  1245. This will remove most of the old Homebrew installation but will likely fail to remove everything.<br>
  1246. Especially in my situation with years of cruft accumulated, this was the case.<br>
  1247. I ended up with the following output from the cleanup script:
  1248. </p>
  1249. <pre>==&gt; /usr/bin/sudo rmdir /usr/local
  1250. rmdir: /usr/local: Operation not permitted
  1251. Warning: Failed during: /usr/bin/sudo rmdir /usr/local
  1252. Warning: Homebrew partially uninstalled (but there were steps that failed)!
  1253. To finish uninstalling rerun this script with `sudo`.
  1254. The following possible Homebrew files were not deleted:
  1255. /usr/local/.com.apple.installer.keep
  1256. /usr/local/Cellar/
  1257. /usr/local/Frameworks/
  1258. /usr/local/Homebrew/
  1259. /usr/local/MacGPG2/
  1260. /usr/local/bin/
  1261. /usr/local/etc/
  1262. /usr/local/include/
  1263. /usr/local/lib/
  1264. /usr/local/man/
  1265. /usr/local/opt/
  1266. /usr/local/remotedesktop/
  1267. /usr/local/sbin/
  1268. /usr/local/share/
  1269. /usr/local/tests/
  1270. /usr/local/var/
  1271. You may wish to remove them yourself.</pre>
  1272. <p>
  1273. I manually went through all these folders and removed what I could identify as obsolete and no longer needed leftovers.<br>
  1274. Important though for example the MacGPG2 folder seems to come from the GPGTools installation, thus be aware that there are other things than Homebrew which might have installed some software under <var>/usr/local</var> and not everyhting must necessarily be removed.
  1275. </p>
  1276. <p>
  1277. <b>Unsolved problems</b><br>
  1278. As mentioned there are some things which I haven't figured out how to fix yet.
  1279. <p>
  1280. <p>
  1281. I'm missing a good solution for <a href="https://vgough.github.io/encfs/" title="EncFS">encfs</a> (which is no longer provided by Homebrew due to license changes of the underlying MacFuse project).
  1282. Compiling from source (at least through Homebrew) is not supported either (as it is marked as Linux-only and complilation is not supported anymore on macOS).<br>
  1283. <b>Update:</b> found a solution for <a href="https://blog.x-way.org/Mac/2024/12/03/How-to-install-EncFS-on-macOS-Sequoia.html" title="x-log - How to install EncFS on MacOS Sequoia">how to install EncFS on macOS Sequoia</a>.
  1284. </p>
  1285. <p>
  1286. Another missing thing (which is more a problem of not having time to deal with it yet), is the Perl ecosystem including CPAN package management.
  1287. Here probably some research to find the canonical way for installing Perl in macOS 15 is all I need. 🐪
  1288. </p>
  1289. ]]></content:encoded>
  1290.  </item>
  1291.  
  1292.  <item>
  1293.    <title>Migrate Syncthing from Intel to M4</title>
  1294.    <link>https://blog.x-way.org/Mac/2024/11/30/Migrate-Syncthing-from-Intel-to-M4.html</link>
  1295.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324429</guid>
  1296.    <dc:creator>Andreas Jaggi</dc:creator>
  1297.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  1298.    <pubDate>Sat, 30 Nov 2024 22:27:21 +0100</pubDate>
  1299.    <category domain="https://blog.x-way.org/Mac/">Mac</category>
  1300.    <description><![CDATA[<p>
  1301. After <a href="https://blog.x-way.org/Mac/2024/11/30/Move-from-2017-Intel-MacBook-Pro-to-2024-M4-MacBook-Pro.html" title="x-log - Move from 2017 Intel MacBook Pro to 2024 M4 MacBook Pro">switching to an Apple Silicon CPU</a>, I'm now hunting down all the Intel-only binaries on my system.<br>
  1302. Using the Activity Monitor and ordering the processes by <var>Kind</var> is quite helpful for this.
  1303. </p>
  1304. <p>
  1305. So I identified <a href="https://syncthing.net/" title="Syncthing">Syncthing</a> to be still running as an Intel-only binary with the Rosetta 2 emulation.<br>
  1306. My <a href="https://docs.syncthing.net/users/autostart.html#without-homebrew" title="Starting Syncthing Automatically - Without Homebrew">installation of Syncthing</a> is quite old, so it isn't managed by Homebrew yet.<br>
  1307. This actually made the switch quite easy:
  1308. </p>
  1309. <ul>
  1310. <li>Shutdown syncthing</li>
  1311. <li>Download latest release zip for macos-arm64 from <a href="https://github.com/syncthing/syncthing/releases/latest" title="Latest Release - syncthing/syncthing">https://github.com/syncthing/syncthing/releases/latest</a></li>
  1312. <li>Remove the old binaries:<pre>rm $HOME/bin/syncthing
  1313. rm $HOME/bin/syncthing.old</pre></li>
  1314. <li>Unzip the downloaded release and move the <var>syncthing</var> binary to <var>$HOME/bin/syncthing</var></li>
  1315. <li>Kill all running syncthing processes (they are auto-restarted via launchd)</li>
  1316. <li>You might get a popup to approve the newly downloaded binary when launchd does the restart</li>
  1317. <li>Check in Activity Monitor that the running Syncthing processes are now Apple binaries 🍏</li>
  1318. </ul>
  1319. ]]></description>
  1320.    <content:encoded><![CDATA[<p>
  1321. After <a href="https://blog.x-way.org/Mac/2024/11/30/Move-from-2017-Intel-MacBook-Pro-to-2024-M4-MacBook-Pro.html" title="x-log - Move from 2017 Intel MacBook Pro to 2024 M4 MacBook Pro">switching to an Apple Silicon CPU</a>, I'm now hunting down all the Intel-only binaries on my system.<br>
  1322. Using the Activity Monitor and ordering the processes by <var>Kind</var> is quite helpful for this.
  1323. </p>
  1324. <p>
  1325. So I identified <a href="https://syncthing.net/" title="Syncthing">Syncthing</a> to be still running as an Intel-only binary with the Rosetta 2 emulation.<br>
  1326. My <a href="https://docs.syncthing.net/users/autostart.html#without-homebrew" title="Starting Syncthing Automatically - Without Homebrew">installation of Syncthing</a> is quite old, so it isn't managed by Homebrew yet.<br>
  1327. This actually made the switch quite easy:
  1328. </p>
  1329. <ul>
  1330. <li>Shutdown syncthing</li>
  1331. <li>Download latest release zip for macos-arm64 from <a href="https://github.com/syncthing/syncthing/releases/latest" title="Latest Release - syncthing/syncthing">https://github.com/syncthing/syncthing/releases/latest</a></li>
  1332. <li>Remove the old binaries:<pre>rm $HOME/bin/syncthing
  1333. rm $HOME/bin/syncthing.old</pre></li>
  1334. <li>Unzip the downloaded release and move the <var>syncthing</var> binary to <var>$HOME/bin/syncthing</var></li>
  1335. <li>Kill all running syncthing processes (they are auto-restarted via launchd)</li>
  1336. <li>You might get a popup to approve the newly downloaded binary when launchd does the restart</li>
  1337. <li>Check in Activity Monitor that the running Syncthing processes are now Apple binaries 🍏</li>
  1338. </ul>
  1339. ]]></content:encoded>
  1340.  </item>
  1341.  
  1342.  <item>
  1343.    <title>Move from 2017 Intel MacBook Pro to 2024 M4 MacBook Pro</title>
  1344.    <link>https://blog.x-way.org/Mac/2024/11/30/Move-from-2017-Intel-MacBook-Pro-to-2024-M4-MacBook-Pro.html</link>
  1345.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324427</guid>
  1346.    <dc:creator>Andreas Jaggi</dc:creator>
  1347.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  1348.    <pubDate>Sat, 30 Nov 2024 21:28:31 +0100</pubDate>
  1349.    <category domain="https://blog.x-way.org/Mac/">Mac</category>
  1350.    <description><![CDATA[<p>
  1351. The <a href="https://blog.x-way.org/Misc/2024/11/29/Out-for-Delivery.html" title="x-log - Out for Delivery">new laptop</a> arrived and now it's time for the big migration.<br>
  1352. This includes not only a change in the physical device, but also a change in OS version and more importantly in CPU architecture.<br>
  1353. Luckily there are some very helpful tools making this a quite smooth experience.
  1354. </p>
  1355. <p>
  1356. Overal plan of attack:
  1357. </p>
  1358. <ul>
  1359. <li>Make a Time Machine backup to an external USB disk.</li>
  1360. <li>Start the new laptop and use the Migration Assistant to restore from the Time Machine backup.</li>
  1361. <li>Go to sleep / do something else, while the restore process is running.</li>
  1362. <li>After the restore is completed, login and fix all the problems caused by the OS version and CPU architecture change :-)</li>
  1363. </ul>
  1364. <p>
  1365. This plan worked quite well for me (as I'm already writing this blogpost with the new laptop).<br>
  1366. There are of course some expected and some unexptected problems that need to be addressed.
  1367. </p>
  1368. <p>
  1369. <b>Rosetta 2</b><br>
  1370. Directly after the first start, there was a system message asking me if Rosetta 2 should be enabled.<br>
  1371. Rosetta 2 is the emulation layer built into macOS that allows to run Intel-only binaries on the Apple Silicon CPUs.<br>
  1372. To reduce the ammount of immediate problems to fix, I enabled it for now.<br>
  1373. Even though over time I plan to replace all Intel-only binaries with newer versions.
  1374. </p>
  1375. <p>
  1376. <b>1Password</b><br>
  1377. One unexpected problem was <a href="https://1password.com/" title="Top-Rated Password Manager | 1Password">1Password</a>.
  1378. There I was prompted to install the old version 7 from the App Store.<br>
  1379. It took some time to figure out that the current version 8 is no longer distributed through the App Store.<br>
  1380. Instead I had to remove the (freshly installed) 1Password 7 App from <var>/Applications</var>.
  1381. And then needed to download their <a href="https://1password.com/downloads/mac" title="Download 1Password for Mac">custom installer</a> from their website.<br>
  1382. The installer in turn then did download and install the latest 1Password version 8.
  1383. </p>
  1384. <p>
  1385. <b>Homebrew</b><br>
  1386. On the list of expected problems was <a href="https://brew.sh/" title="Homebrew — The Missing Package Manager for macOS">Homebrew</a>.<br>
  1387. Here not only I had a big collection of pre-compiled (for Intel) opensource binaries that needed to be changed into pre-compiled binaries for Apple Silicon.
  1388. But also the root folder of the whole Homebrew installation changed from <var>/usr/local</var> to <var>/opt/homebrew</var>.<br>
  1389. And to make matters worse, some of the non-opensource software distributed by Homebrew in so called <var>casks</var> keeps using the old <var>/usr/local</var>.<br>
  1390. For the migration of the binaries, I followed the FAQ entry <a href="https://docs.brew.sh/Common-Issues#unintentional-dual-homebrew-installations" title="Common Issues - Unintentional dual Homebrew installations">here</a>.<br>
  1391. As expected this did not go over completely smooth and quite some research, manual fixing and cleanup was needed.<br>
  1392. I will write more about the problems/fixes and tricks I found out in a future blogpost.<br>
  1393. <b>Update:</b> please have a look at <a href="https://blog.x-way.org/Mac/2024/12/01/Migrate-Homebrew-from-Intel-to-M4-MacBook-Pro.html" title="x-log - Migrate Homebrew from Intel to M4 MacBook Pro">the dedicated blogpost</a> for all the tricks and learnings of the Homebrew migration.
  1394. </p>
  1395. <p>
  1396. <b>GPGTools</b><br>
  1397. Not completely unexpected, but surprisingly smooth was the migration of MacGPG and the GPG plugin for Mail.app.<br>
  1398. They provide a <a href="https://gpgtools.org/sequoia" title="GPG Suite">dedicated version</a> of the software which brings compatibility with macOS Sequoia.<br>
  1399. After running the installer to update the software, only a re-entering of the license key is needed and everything works as before.
  1400. </p>
  1401. <p>
  1402. Besides the already mentioned surprises with Homebrew, there are still some other issues left to be fixed (and possibly new ones to be discovered).<br>
  1403. Overall the laptop is working very well and my familiar environment is mostly there 😌
  1404. </p>
  1405. ]]></description>
  1406.    <content:encoded><![CDATA[<p>
  1407. The <a href="https://blog.x-way.org/Misc/2024/11/29/Out-for-Delivery.html" title="x-log - Out for Delivery">new laptop</a> arrived and now it's time for the big migration.<br>
  1408. This includes not only a change in the physical device, but also a change in OS version and more importantly in CPU architecture.<br>
  1409. Luckily there are some very helpful tools making this a quite smooth experience.
  1410. </p>
  1411. <p>
  1412. Overal plan of attack:
  1413. </p>
  1414. <ul>
  1415. <li>Make a Time Machine backup to an external USB disk.</li>
  1416. <li>Start the new laptop and use the Migration Assistant to restore from the Time Machine backup.</li>
  1417. <li>Go to sleep / do something else, while the restore process is running.</li>
  1418. <li>After the restore is completed, login and fix all the problems caused by the OS version and CPU architecture change :-)</li>
  1419. </ul>
  1420. <p>
  1421. This plan worked quite well for me (as I'm already writing this blogpost with the new laptop).<br>
  1422. There are of course some expected and some unexptected problems that need to be addressed.
  1423. </p>
  1424. <p>
  1425. <b>Rosetta 2</b><br>
  1426. Directly after the first start, there was a system message asking me if Rosetta 2 should be enabled.<br>
  1427. Rosetta 2 is the emulation layer built into macOS that allows to run Intel-only binaries on the Apple Silicon CPUs.<br>
  1428. To reduce the ammount of immediate problems to fix, I enabled it for now.<br>
  1429. Even though over time I plan to replace all Intel-only binaries with newer versions.
  1430. </p>
  1431. <p>
  1432. <b>1Password</b><br>
  1433. One unexpected problem was <a href="https://1password.com/" title="Top-Rated Password Manager | 1Password">1Password</a>.
  1434. There I was prompted to install the old version 7 from the App Store.<br>
  1435. It took some time to figure out that the current version 8 is no longer distributed through the App Store.<br>
  1436. Instead I had to remove the (freshly installed) 1Password 7 App from <var>/Applications</var>.
  1437. And then needed to download their <a href="https://1password.com/downloads/mac" title="Download 1Password for Mac">custom installer</a> from their website.<br>
  1438. The installer in turn then did download and install the latest 1Password version 8.
  1439. </p>
  1440. <p>
  1441. <b>Homebrew</b><br>
  1442. On the list of expected problems was <a href="https://brew.sh/" title="Homebrew — The Missing Package Manager for macOS">Homebrew</a>.<br>
  1443. Here not only I had a big collection of pre-compiled (for Intel) opensource binaries that needed to be changed into pre-compiled binaries for Apple Silicon.
  1444. But also the root folder of the whole Homebrew installation changed from <var>/usr/local</var> to <var>/opt/homebrew</var>.<br>
  1445. And to make matters worse, some of the non-opensource software distributed by Homebrew in so called <var>casks</var> keeps using the old <var>/usr/local</var>.<br>
  1446. For the migration of the binaries, I followed the FAQ entry <a href="https://docs.brew.sh/Common-Issues#unintentional-dual-homebrew-installations" title="Common Issues - Unintentional dual Homebrew installations">here</a>.<br>
  1447. As expected this did not go over completely smooth and quite some research, manual fixing and cleanup was needed.<br>
  1448. I will write more about the problems/fixes and tricks I found out in a future blogpost.<br>
  1449. <b>Update:</b> please have a look at <a href="https://blog.x-way.org/Mac/2024/12/01/Migrate-Homebrew-from-Intel-to-M4-MacBook-Pro.html" title="x-log - Migrate Homebrew from Intel to M4 MacBook Pro">the dedicated blogpost</a> for all the tricks and learnings of the Homebrew migration.
  1450. </p>
  1451. <p>
  1452. <b>GPGTools</b><br>
  1453. Not completely unexpected, but surprisingly smooth was the migration of MacGPG and the GPG plugin for Mail.app.<br>
  1454. They provide a <a href="https://gpgtools.org/sequoia" title="GPG Suite">dedicated version</a> of the software which brings compatibility with macOS Sequoia.<br>
  1455. After running the installer to update the software, only a re-entering of the license key is needed and everything works as before.
  1456. </p>
  1457. <p>
  1458. Besides the already mentioned surprises with Homebrew, there are still some other issues left to be fixed (and possibly new ones to be discovered).<br>
  1459. Overall the laptop is working very well and my familiar environment is mostly there 😌
  1460. </p>
  1461. ]]></content:encoded>
  1462.  </item>
  1463.  
  1464.  <item>
  1465.    <title>Out for Delivery</title>
  1466.    <link>https://blog.x-way.org/Misc/2024/11/29/Out-for-Delivery.html</link>
  1467.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324426</guid>
  1468.    <dc:creator>Andreas Jaggi</dc:creator>
  1469.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  1470.    <pubDate>Fri, 29 Nov 2024 11:28:38 +0100</pubDate>
  1471.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  1472.    <description><![CDATA[<p>
  1473. <img src="https://blog.x-way.org/images/out-for-delivery.png" width="584" height="133" alt="Out for Delivery" />
  1474. </p>
  1475. <p>
  1476. <a href="https://blog.x-way.org/Mac/2024/11/17/My-Mac-history.html" title="x-log - My Mac history">It's</a> getting closer and closer... 😊
  1477. </p>
  1478. ]]></description>
  1479.    <content:encoded><![CDATA[<p>
  1480. <img src="https://blog.x-way.org/images/out-for-delivery.png" width="584" height="133" alt="Out for Delivery" />
  1481. </p>
  1482. <p>
  1483. <a href="https://blog.x-way.org/Mac/2024/11/17/My-Mac-history.html" title="x-log - My Mac history">It's</a> getting closer and closer... 😊
  1484. </p>
  1485. ]]></content:encoded>
  1486.  </item>
  1487.  
  1488.  <item>
  1489.    <title>My Mac history</title>
  1490.    <link>https://blog.x-way.org/Mac/2024/11/17/My-Mac-history.html</link>
  1491.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324425</guid>
  1492.    <dc:creator>Andreas Jaggi</dc:creator>
  1493.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  1494.    <pubDate>Sun, 17 Nov 2024 18:10:59 +0100</pubDate>
  1495.    <category domain="https://blog.x-way.org/Mac/">Mac</category>
  1496.    <description><![CDATA[<p>
  1497. My current laptop is dying of age after 7 years. Thus I'm getting a new one to replace it.<br>
  1498. As part of the research, I looked for my last laptop purchase.<br>
  1499. I not only found my last one, but also all the previous ones.<br>
  1500. So I established my personal Mac history:
  1501. </p>
  1502. <table>
  1503. <thead>
  1504. <tr><th>Purchased</th><th>Type</th><th>Display</th><th>Processor</th><th>Memory</th><th>Storage</th></tr>
  1505. </thead>
  1506. <tbody>
  1507. <tr><td>October 2003</td><td>PowerBook</td><td>15.2&Prime;</td><td>1.25GHz PowerPC G4</td><td>512MB</td><td>80GB</td></tr>
  1508. <tr><td>January 2007</td><td>MacBook Pro</td><td>15.4&Prime;</td><td>2.33GHz Intel Core 2 Duo</td><td>2GB</td><td>120GB</td></tr>
  1509. <tr><td>May 2012</td><td>MacBook Pro</td><td>15.4&Prime;</td><td>2.5GHz Quad-Core Intel Core i7</td><td>8GB</td><td>750GB</td></tr>
  1510. <tr><td>October 2017</td><td>MacBook Pro</td><td>13.3&Prime;</td><td>2.3GHz Dual-Core Intel Core i5</td><td>16GB</td><td>1TB</td></tr>
  1511. <tr><td>November 2024</td><td>MacBook Pro</td><td>14.2&Prime;</td><td>M4 Pro 14-Core CPU, 20-Core GPU, 16-Core Neural Engine</td><td>48GB</td><td>2TB</td></tr>
  1512. </tbody>
  1513. </table>
  1514. <p>
  1515. Reflecting on it, it seems I get quite a good milage out of my laptops.<br>
  1516. Current replacement due to age related failures after 7 years is the top one.
  1517. </p>
  1518. <p>
  1519. The previous 2017 replacement was similar due to age related failures after 5 years.
  1520. </p>
  1521. <p>
  1522. For the 2012 replacement it is a bit of a different story, as my laptop at the time was stolen from me.<br>
  1523. But I still got five years out of it before that.
  1524. </p>
  1525. <p>
  1526. The 2007 replacement was the switch to Intel after 4 years on PowerPC.<br>
  1527. I was very happy with my PowerBook at the time, even helped to reverse-engineer the wireless chipset to <a href="https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/net/wireless/broadcom/b43/main.c?h=v6.11.9#n10" title="main.c « b43 « broadcom « wireless « net « drivers - kernel/git/stable/linux.git - Linux kernel stable tree">write the Linux driver</a> for it :-)
  1528. </p>
  1529. ]]></description>
  1530.    <content:encoded><![CDATA[<p>
  1531. My current laptop is dying of age after 7 years. Thus I'm getting a new one to replace it.<br>
  1532. As part of the research, I looked for my last laptop purchase.<br>
  1533. I not only found my last one, but also all the previous ones.<br>
  1534. So I established my personal Mac history:
  1535. </p>
  1536. <table>
  1537. <thead>
  1538. <tr><th>Purchased</th><th>Type</th><th>Display</th><th>Processor</th><th>Memory</th><th>Storage</th></tr>
  1539. </thead>
  1540. <tbody>
  1541. <tr><td>October 2003</td><td>PowerBook</td><td>15.2&Prime;</td><td>1.25GHz PowerPC G4</td><td>512MB</td><td>80GB</td></tr>
  1542. <tr><td>January 2007</td><td>MacBook Pro</td><td>15.4&Prime;</td><td>2.33GHz Intel Core 2 Duo</td><td>2GB</td><td>120GB</td></tr>
  1543. <tr><td>May 2012</td><td>MacBook Pro</td><td>15.4&Prime;</td><td>2.5GHz Quad-Core Intel Core i7</td><td>8GB</td><td>750GB</td></tr>
  1544. <tr><td>October 2017</td><td>MacBook Pro</td><td>13.3&Prime;</td><td>2.3GHz Dual-Core Intel Core i5</td><td>16GB</td><td>1TB</td></tr>
  1545. <tr><td>November 2024</td><td>MacBook Pro</td><td>14.2&Prime;</td><td>M4 Pro 14-Core CPU, 20-Core GPU, 16-Core Neural Engine</td><td>48GB</td><td>2TB</td></tr>
  1546. </tbody>
  1547. </table>
  1548. <p>
  1549. Reflecting on it, it seems I get quite a good milage out of my laptops.<br>
  1550. Current replacement due to age related failures after 7 years is the top one.
  1551. </p>
  1552. <p>
  1553. The previous 2017 replacement was similar due to age related failures after 5 years.
  1554. </p>
  1555. <p>
  1556. For the 2012 replacement it is a bit of a different story, as my laptop at the time was stolen from me.<br>
  1557. But I still got five years out of it before that.
  1558. </p>
  1559. <p>
  1560. The 2007 replacement was the switch to Intel after 4 years on PowerPC.<br>
  1561. I was very happy with my PowerBook at the time, even helped to reverse-engineer the wireless chipset to <a href="https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/net/wireless/broadcom/b43/main.c?h=v6.11.9#n10" title="main.c « b43 « broadcom « wireless « net « drivers - kernel/git/stable/linux.git - Linux kernel stable tree">write the Linux driver</a> for it :-)
  1562. </p>
  1563. ]]></content:encoded>
  1564.  </item>
  1565.  
  1566.  <item>
  1567.    <title>GitFlops: The Dangers of Terraform Automation Platforms</title>
  1568.    <link>https://blog.x-way.org/Misc/2024/11/14/GitFlops-The-Dangers-of-Terraform-Automation-Platforms.html</link>
  1569.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324424</guid>
  1570.    <dc:creator>Andreas Jaggi</dc:creator>
  1571.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  1572.    <pubDate>Thu, 14 Nov 2024 10:00:27 +0100</pubDate>
  1573.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  1574.    <description><![CDATA[<p>
  1575. In the <a href="https://snyk.io/de/blog/gitflops-dangers-of-terraform-automation-platforms/" title="GitFlops: The Dangers of Terraform Automation Platforms | Snyk">GitFlops: The Dangers of Terraform Automation Platforms</a> article Elliot Ward highlights how <a href="https://www.terraform.io/" title="Terraform by HashiCorp">Terraform</a> automation platforms can be exploited to compromise cloud environments.
  1576. </p>
  1577. <p>
  1578. In particular it looks at how to exploit the <code>terraform plan</code> phase to execute commands and gain access to cloud infrastructure credentials.<br>
  1579. In combination with a classic GitOps flow, where unprivileged users can open pull-requests and <code>terraform plan</code> is run on these pull-requests, this creates privilege escalation vulnerabilities putting the cloud infrastructure at risk.
  1580. </p>
  1581. <p>
  1582. In terms of preventing this, the recommendation is to validate Terraform config before running <code>terraform plan</code> on it.<br>
  1583. One tool mentioned in the article that can be used to for this validation is <a href="https://www.conftest.dev/" title="Conftest">Conftest</a>.
  1584. </p>
  1585. <p>
  1586. A month ago, <a href="https://bern.bsides.ch/agenda/abstracts-and-bios/#terraform" title="Security Bsides Bern">Elliot also presented the topic at the BSides Bern conference</a>.<br>
  1587. The slides of the presentation have been made available by the conference, <a href="https://blog.x-way.org/stuff/2-Elliot-BSides-Bern-2024.pdf" title="GitFlops: Breaking Terraform Lifecycle Management Tool">here is a copy</a>.
  1588. </p>
  1589. ]]></description>
  1590.    <content:encoded><![CDATA[<p>
  1591. In the <a href="https://snyk.io/de/blog/gitflops-dangers-of-terraform-automation-platforms/" title="GitFlops: The Dangers of Terraform Automation Platforms | Snyk">GitFlops: The Dangers of Terraform Automation Platforms</a> article Elliot Ward highlights how <a href="https://www.terraform.io/" title="Terraform by HashiCorp">Terraform</a> automation platforms can be exploited to compromise cloud environments.
  1592. </p>
  1593. <p>
  1594. In particular it looks at how to exploit the <code>terraform plan</code> phase to execute commands and gain access to cloud infrastructure credentials.<br>
  1595. In combination with a classic GitOps flow, where unprivileged users can open pull-requests and <code>terraform plan</code> is run on these pull-requests, this creates privilege escalation vulnerabilities putting the cloud infrastructure at risk.
  1596. </p>
  1597. <p>
  1598. In terms of preventing this, the recommendation is to validate Terraform config before running <code>terraform plan</code> on it.<br>
  1599. One tool mentioned in the article that can be used to for this validation is <a href="https://www.conftest.dev/" title="Conftest">Conftest</a>.
  1600. </p>
  1601. <p>
  1602. A month ago, <a href="https://bern.bsides.ch/agenda/abstracts-and-bios/#terraform" title="Security Bsides Bern">Elliot also presented the topic at the BSides Bern conference</a>.<br>
  1603. The slides of the presentation have been made available by the conference, <a href="https://blog.x-way.org/stuff/2-Elliot-BSides-Bern-2024.pdf" title="GitFlops: Breaking Terraform Lifecycle Management Tool">here is a copy</a>.
  1604. </p>
  1605. ]]></content:encoded>
  1606.  </item>
  1607.  
  1608.  <item>
  1609.    <title>Surveillance Self-Defense</title>
  1610.    <link>https://blog.x-way.org/Misc/2024/11/12/Surveillance-Self-Defense.html</link>
  1611.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324423</guid>
  1612.    <dc:creator>Andreas Jaggi</dc:creator>
  1613.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  1614.    <pubDate>Tue, 12 Nov 2024 23:42:37 +0100</pubDate>
  1615.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  1616.    <description><![CDATA[<p>
  1617. The <a href="https://www.eff.org/" title="Electronic Frontier Foundation | Defending your rights in the digital world">Electronic Frontier Foundation</a> provides the <a href="https://ssd.eff.org/" title="Surveillance Self-Defense">Surveillance Self-Defense</a> guide.
  1618. </p>
  1619. <p>
  1620. When talking about security it is important to known what you want to protect.<br>
  1621. The <a href="https://ssd.eff.org/module/your-security-plan" title="Your Security Plan | Surveillance Self-Defense">Your Security Plan</a> module of the guide covers this topic and is a good starting point.
  1622. </p>
  1623. <p>
  1624. (<a href="https://hachyderm.io/@evacide/113451271143994660" title="evacide: &quot;I&#39;m seeing a lot of bad digital security advice o…&quot; - Hachyderm.io">via</a>)
  1625. </p>
  1626. ]]></description>
  1627.    <content:encoded><![CDATA[<p>
  1628. The <a href="https://www.eff.org/" title="Electronic Frontier Foundation | Defending your rights in the digital world">Electronic Frontier Foundation</a> provides the <a href="https://ssd.eff.org/" title="Surveillance Self-Defense">Surveillance Self-Defense</a> guide.
  1629. </p>
  1630. <p>
  1631. When talking about security it is important to known what you want to protect.<br>
  1632. The <a href="https://ssd.eff.org/module/your-security-plan" title="Your Security Plan | Surveillance Self-Defense">Your Security Plan</a> module of the guide covers this topic and is a good starting point.
  1633. </p>
  1634. <p>
  1635. (<a href="https://hachyderm.io/@evacide/113451271143994660" title="evacide: &quot;I&#39;m seeing a lot of bad digital security advice o…&quot; - Hachyderm.io">via</a>)
  1636. </p>
  1637. ]]></content:encoded>
  1638.  </item>
  1639.  
  1640.  <item>
  1641.    <title>Go Turns 15</title>
  1642.    <link>https://blog.x-way.org/Coding/2024/11/12/Go-Turns-15.html</link>
  1643.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324422</guid>
  1644.    <dc:creator>Andreas Jaggi</dc:creator>
  1645.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  1646.    <pubDate>Tue, 12 Nov 2024 20:29:30 +0100</pubDate>
  1647.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  1648.    <description><![CDATA[<p>
  1649. <a href="https://go.dev/blog/15years" title="Go Turns 15 - The Go Programming Language">Happy birthday, Go!</a> 🎂
  1650. </p>
  1651. ]]></description>
  1652.    <content:encoded><![CDATA[<p>
  1653. <a href="https://go.dev/blog/15years" title="Go Turns 15 - The Go Programming Language">Happy birthday, Go!</a> 🎂
  1654. </p>
  1655. ]]></content:encoded>
  1656.  </item>
  1657.  
  1658.  <item>
  1659.    <title>Log the real IP with lighttpd</title>
  1660.    <link>https://blog.x-way.org/Linux/2024/11/11/Log-the-real-IP-with-lighttpd.html</link>
  1661.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324421</guid>
  1662.    <dc:creator>Andreas Jaggi</dc:creator>
  1663.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  1664.    <pubDate>Mon, 11 Nov 2024 14:15:11 +0100</pubDate>
  1665.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  1666.    <description><![CDATA[<p>
  1667. The static pages of the blog here are served from a <a href="https://www.lighttpd.net/" title="Lighttpd - fly light">lighttpd</a> container with an <a href="https://nginx.org/" title="nginx">nginx</a> proxy in front.<br>
  1668. I was looking through the lighttpd access logs and was a bit annoyed as it showed the internal IP of the nginx proxy.
  1669. </p>
  1670. <p>
  1671. My nginx instance is already setup to forward the actual remote IP in the <code>X-Real-IP</code> header.<br>
  1672. Thus I needed to make lighttpd use the forwarded IP from the header in the access logs.<br>
  1673. This can be achieved with the <a href="https://redmine.lighttpd.net/projects/lighttpd/wiki/Mod_extforward" title="Mod extforward - Lighttpd - lighty labs">extforward module</a> using the following configuration snippet:
  1674. </p>
  1675. <pre>server.modules += ("mod_extforward")
  1676. extforward.headers = ("X-Real-IP")
  1677. extforward.forwarder = ("10.111.0.0/16" =&gt; "trust")</pre>
  1678. <p>
  1679. With this config, lighttpd uses the <code>X-Real-IP</code> in the access logs.<br>
  1680. The override is only performed when the connection comes from the 10.111.0.0/16 subnet.
  1681. Which prevents remote IP spoofing via injected/faked headers.<br>
  1682. (the 10.111.0.0/16 subnet is my internal container network where nginx is running)
  1683. </p>
  1684. ]]></description>
  1685.    <content:encoded><![CDATA[<p>
  1686. The static pages of the blog here are served from a <a href="https://www.lighttpd.net/" title="Lighttpd - fly light">lighttpd</a> container with an <a href="https://nginx.org/" title="nginx">nginx</a> proxy in front.<br>
  1687. I was looking through the lighttpd access logs and was a bit annoyed as it showed the internal IP of the nginx proxy.
  1688. </p>
  1689. <p>
  1690. My nginx instance is already setup to forward the actual remote IP in the <code>X-Real-IP</code> header.<br>
  1691. Thus I needed to make lighttpd use the forwarded IP from the header in the access logs.<br>
  1692. This can be achieved with the <a href="https://redmine.lighttpd.net/projects/lighttpd/wiki/Mod_extforward" title="Mod extforward - Lighttpd - lighty labs">extforward module</a> using the following configuration snippet:
  1693. </p>
  1694. <pre>server.modules += ("mod_extforward")
  1695. extforward.headers = ("X-Real-IP")
  1696. extforward.forwarder = ("10.111.0.0/16" =&gt; "trust")</pre>
  1697. <p>
  1698. With this config, lighttpd uses the <code>X-Real-IP</code> in the access logs.<br>
  1699. The override is only performed when the connection comes from the 10.111.0.0/16 subnet.
  1700. Which prevents remote IP spoofing via injected/faked headers.<br>
  1701. (the 10.111.0.0/16 subnet is my internal container network where nginx is running)
  1702. </p>
  1703. ]]></content:encoded>
  1704.  </item>
  1705.  
  1706.  <item>
  1707.    <title>Fix URL used by ntpleapfetch</title>
  1708.    <link>https://blog.x-way.org/Linux/2024/11/10/Fix-URL-used-by-ntpleapfetch.html</link>
  1709.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324420</guid>
  1710.    <dc:creator>Andreas Jaggi</dc:creator>
  1711.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  1712.    <pubDate>Sun, 10 Nov 2024 19:46:29 +0100</pubDate>
  1713.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  1714.    <description><![CDATA[<p>
  1715. The other morning I was greeted by a mailbox full of messages from failed cronjobs.<br>
  1716. The reported error message was:
  1717. </p>
  1718. <pre>&lt;28&gt;Nov  7 02:51:02 ntpleapfetch[3253838]: Download from https://www.ietf.org/timezones/data/leap-seconds.list failed after 6 attempts
  1719. --2024-11-07 02:51:02--  https://www.ietf.org/timezones/data/leap-seconds.list
  1720. Resolving www.ietf.org (www.ietf.org)... 2606:4700::6810:2d63, 2606:4700::6810:2c63, 104.16.45.99, ...
  1721. Connecting to www.ietf.org (www.ietf.org)|2606:4700::6810:2d63|:443... connected.
  1722. HTTP request sent, awaiting response... 404 Not Found
  1723. 2024-11-07 02:51:02 ERROR 404: Not Found.</pre>
  1724. <p>
  1725. The failing cronjobs were weekly invocations of <a href="https://docs.ntpsec.org/latest/ntpleapfetch.html" title="ntpleapfetch - fetch and manage local leapfile">ntpleapfetch</a> to get the latest list of leap seconds.
  1726. </p>
  1727. <p>
  1728. After some research I found out that indeed the URL returns a 404 and that there was no newer version of the Debian package available to try.<br>
  1729. Also the bugtracker didn't show anyone else dealing with this problem.
  1730. </p>
  1731. <p>
  1732. Thus I started looking at the source code of ntpsec
  1733. (which provides the ntpleapsec script).<br>
  1734. I found a commit with the promising title of <a href="https://gitlab.com/NTPsec/ntpsec/-/commit/7c13df80c896cc201afd6aa9c758fc3103fad818" title="Fix URL used by ntpleapfetch (7c13df80) · Commits · NTPsec / ntpsec · GitLab">Fix URL used by ntpleapfetch</a>.
  1735.  
  1736. </p>
  1737. <p>
  1738. This commit corrects the URL used for downloading the leap seconds list in the script.<br>
  1739. Later I also found a corresponding <a href="https://lists.ntpsec.org/pipermail/users/2024-November/000527.html" title="ntpleapfetch script - IETF link now dead">message in the ntpsec users mailing list</a>.
  1740. </p>
  1741. <p>
  1742. For my Debian systems there is no updated package with the new URL available yet.<br>
  1743. Thus I used the following one-liner to directly fix the ntpleapfetch script.
  1744. </p>
  1745. <pre>sed -i -e 's_^LEAPSRC="https://.*"_LEAPSRC="https://data.iana.org/time-zones/tzdb/leap-seconds.list"_' /usr/sbin/ntpleapfetch</pre>
  1746. ]]></description>
  1747.    <content:encoded><![CDATA[<p>
  1748. The other morning I was greeted by a mailbox full of messages from failed cronjobs.<br>
  1749. The reported error message was:
  1750. </p>
  1751. <pre>&lt;28&gt;Nov  7 02:51:02 ntpleapfetch[3253838]: Download from https://www.ietf.org/timezones/data/leap-seconds.list failed after 6 attempts
  1752. --2024-11-07 02:51:02--  https://www.ietf.org/timezones/data/leap-seconds.list
  1753. Resolving www.ietf.org (www.ietf.org)... 2606:4700::6810:2d63, 2606:4700::6810:2c63, 104.16.45.99, ...
  1754. Connecting to www.ietf.org (www.ietf.org)|2606:4700::6810:2d63|:443... connected.
  1755. HTTP request sent, awaiting response... 404 Not Found
  1756. 2024-11-07 02:51:02 ERROR 404: Not Found.</pre>
  1757. <p>
  1758. The failing cronjobs were weekly invocations of <a href="https://docs.ntpsec.org/latest/ntpleapfetch.html" title="ntpleapfetch - fetch and manage local leapfile">ntpleapfetch</a> to get the latest list of leap seconds.
  1759. </p>
  1760. <p>
  1761. After some research I found out that indeed the URL returns a 404 and that there was no newer version of the Debian package available to try.<br>
  1762. Also the bugtracker didn't show anyone else dealing with this problem.
  1763. </p>
  1764. <p>
  1765. Thus I started looking at the source code of ntpsec
  1766. (which provides the ntpleapsec script).<br>
  1767. I found a commit with the promising title of <a href="https://gitlab.com/NTPsec/ntpsec/-/commit/7c13df80c896cc201afd6aa9c758fc3103fad818" title="Fix URL used by ntpleapfetch (7c13df80) · Commits · NTPsec / ntpsec · GitLab">Fix URL used by ntpleapfetch</a>.
  1768.  
  1769. </p>
  1770. <p>
  1771. This commit corrects the URL used for downloading the leap seconds list in the script.<br>
  1772. Later I also found a corresponding <a href="https://lists.ntpsec.org/pipermail/users/2024-November/000527.html" title="ntpleapfetch script - IETF link now dead">message in the ntpsec users mailing list</a>.
  1773. </p>
  1774. <p>
  1775. For my Debian systems there is no updated package with the new URL available yet.<br>
  1776. Thus I used the following one-liner to directly fix the ntpleapfetch script.
  1777. </p>
  1778. <pre>sed -i -e 's_^LEAPSRC="https://.*"_LEAPSRC="https://data.iana.org/time-zones/tzdb/leap-seconds.list"_' /usr/sbin/ntpleapfetch</pre>
  1779. ]]></content:encoded>
  1780.  </item>
  1781.  
  1782.  <item>
  1783.    <title>Tools for writing secure Go code</title>
  1784.    <link>https://blog.x-way.org/Coding/2024/11/06/Tools-for-writing-secure-Go-code.html</link>
  1785.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324419</guid>
  1786.    <dc:creator>Andreas Jaggi</dc:creator>
  1787.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  1788.    <pubDate>Wed, 06 Nov 2024 00:18:24 +0100</pubDate>
  1789.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  1790.    <description><![CDATA[<p>
  1791. In his <a href="https://jarosz.dev/article/writing-secure-go-code/" title="Writing secure Go code | Jakub Jarosz">writing secure Go code</a> article, Jakub Jarosz lists tools that help with writing secure Go code.<br>
  1792. The article lists the tools and for each of them explains what it does and how it contributes to writing secure Go code.
  1793. </p>
  1794. <p>
  1795. The following tools are covered:
  1796. </p>
  1797. <ul>
  1798. <li><code>go vet</code></li>
  1799. <li><code>staticcheck</code></li>
  1800. <li><code>golangci-lint</code></li>
  1801. <li><code>go test -race</code></li>
  1802. <li><code>govulncheck</code></li>
  1803. <li><code>gosec</code></li>
  1804. </ul>
  1805. <p>
  1806. An interesting learning for me whas that <code>govulncheck</code> can not only be used to analyze source code, but also to analyze existing binaries.<br>
  1807. And there it scans the used libraries for vulnerabilities and wether the vulnerable code paths are actually invoked by the code in the binary.
  1808. </p>
  1809. <p>
  1810. In the build pipelines of my Go programs, some of these tools are already used.<br>
  1811. Room for improvement exists when it comes to using the <code>govulncheck</code> and <code>gosec</code> tools.<br>
  1812. Another lonely winter weekend task :-)
  1813. </p>
  1814. ]]></description>
  1815.    <content:encoded><![CDATA[<p>
  1816. In his <a href="https://jarosz.dev/article/writing-secure-go-code/" title="Writing secure Go code | Jakub Jarosz">writing secure Go code</a> article, Jakub Jarosz lists tools that help with writing secure Go code.<br>
  1817. The article lists the tools and for each of them explains what it does and how it contributes to writing secure Go code.
  1818. </p>
  1819. <p>
  1820. The following tools are covered:
  1821. </p>
  1822. <ul>
  1823. <li><code>go vet</code></li>
  1824. <li><code>staticcheck</code></li>
  1825. <li><code>golangci-lint</code></li>
  1826. <li><code>go test -race</code></li>
  1827. <li><code>govulncheck</code></li>
  1828. <li><code>gosec</code></li>
  1829. </ul>
  1830. <p>
  1831. An interesting learning for me whas that <code>govulncheck</code> can not only be used to analyze source code, but also to analyze existing binaries.<br>
  1832. And there it scans the used libraries for vulnerabilities and wether the vulnerable code paths are actually invoked by the code in the binary.
  1833. </p>
  1834. <p>
  1835. In the build pipelines of my Go programs, some of these tools are already used.<br>
  1836. Room for improvement exists when it comes to using the <code>govulncheck</code> and <code>gosec</code> tools.<br>
  1837. Another lonely winter weekend task :-)
  1838. </p>
  1839. ]]></content:encoded>
  1840.  </item>
  1841.  
  1842.  <item>
  1843.    <title>Please publish and share more</title>
  1844.    <link>https://blog.x-way.org/Misc/2024/11/03/Please-publish-and-share-more.html</link>
  1845.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324418</guid>
  1846.    <dc:creator>Andreas Jaggi</dc:creator>
  1847.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  1848.    <pubDate>Sun, 03 Nov 2024 10:54:36 +0100</pubDate>
  1849.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  1850.    <description><![CDATA[<p>
  1851. <a href="https://micro.webology.dev/2024/11/02/please-publish-and.html" title="Please publish and share more - Jiff Triplett's Micro.blog">Please publish and share more</a> from Jeff Triplett. (<a href="https://simonwillison.net/2024/Nov/2/please-publish-and-share-more/" title="Please publish and share more | Simon Willisons's Weblog">via</a>)
  1852. </p>
  1853. <blockquote cite="https://micro.webology.dev/2024/11/02/please-publish-and.html">
  1854. Friends, I encourage you to publish more, indirectly meaning you should write more and then share it.
  1855. </blockquote>
  1856. <blockquote cite="https://micro.webology.dev/2024/11/02/please-publish-and.html">
  1857. You don’t have to change the world with every post. You might publish a quick thought or two that helps encourage someone else to try something new, listen to a new song, or binge-watch a new series.
  1858. </blockquote>
  1859. <blockquote cite="https://micro.webology.dev/2024/11/02/please-publish-and.html">
  1860. Our posts are done when you say they are. You do not have to fret about sticking to landing and having a perfect conclusion. Your posts, like this post, are done after we stop writing.
  1861. </blockquote>
  1862. <p>
  1863. Reminds me that I should setup some <a href="https://indieweb.org/POSSE" title="Publish (on your) Own Site, Syndicate Elsewhere">POSSE</a> mechanism for the blog.<br>
  1864. Maybe during one of the grey and cold weekends this winter :-)
  1865. </p>
  1866. ]]></description>
  1867.    <content:encoded><![CDATA[<p>
  1868. <a href="https://micro.webology.dev/2024/11/02/please-publish-and.html" title="Please publish and share more - Jiff Triplett's Micro.blog">Please publish and share more</a> from Jeff Triplett. (<a href="https://simonwillison.net/2024/Nov/2/please-publish-and-share-more/" title="Please publish and share more | Simon Willisons's Weblog">via</a>)
  1869. </p>
  1870. <blockquote cite="https://micro.webology.dev/2024/11/02/please-publish-and.html">
  1871. Friends, I encourage you to publish more, indirectly meaning you should write more and then share it.
  1872. </blockquote>
  1873. <blockquote cite="https://micro.webology.dev/2024/11/02/please-publish-and.html">
  1874. You don’t have to change the world with every post. You might publish a quick thought or two that helps encourage someone else to try something new, listen to a new song, or binge-watch a new series.
  1875. </blockquote>
  1876. <blockquote cite="https://micro.webology.dev/2024/11/02/please-publish-and.html">
  1877. Our posts are done when you say they are. You do not have to fret about sticking to landing and having a perfect conclusion. Your posts, like this post, are done after we stop writing.
  1878. </blockquote>
  1879. <p>
  1880. Reminds me that I should setup some <a href="https://indieweb.org/POSSE" title="Publish (on your) Own Site, Syndicate Elsewhere">POSSE</a> mechanism for the blog.<br>
  1881. Maybe during one of the grey and cold weekends this winter :-)
  1882. </p>
  1883. ]]></content:encoded>
  1884.  </item>
  1885.  
  1886.  <item>
  1887.    <title>Missing watch command on macOS</title>
  1888.    <link>https://blog.x-way.org/Mac/2024/11/02/Missing-watch-command-on-macOS.html</link>
  1889.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324417</guid>
  1890.    <dc:creator>Andreas Jaggi</dc:creator>
  1891.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  1892.    <pubDate>Sat, 02 Nov 2024 16:21:30 +0100</pubDate>
  1893.    <category domain="https://blog.x-way.org/Mac/">Mac</category>
  1894.    <description><![CDATA[<p>
  1895. I wanted to see the output of a program repeatedly with the <kbd>watch</kbd> command.<br>
  1896. To my surprise this failed on my macOS laptop with the following error:
  1897. </p>
  1898. <pre>% watch ipaddr
  1899. zsh: command not found: watch</pre>
  1900. <p>
  1901. Turns out that macOS does not have the <kbd>watch</kbd> command installed by default.
  1902. </p>
  1903. <pre>% which watch
  1904. watch not found</pre>
  1905. <p>
  1906. Thankfully this can be fixed easily by using homebrew to install the watch binary:
  1907. </p>
  1908. <pre>% brew install watch</pre>
  1909. ]]></description>
  1910.    <content:encoded><![CDATA[<p>
  1911. I wanted to see the output of a program repeatedly with the <kbd>watch</kbd> command.<br>
  1912. To my surprise this failed on my macOS laptop with the following error:
  1913. </p>
  1914. <pre>% watch ipaddr
  1915. zsh: command not found: watch</pre>
  1916. <p>
  1917. Turns out that macOS does not have the <kbd>watch</kbd> command installed by default.
  1918. </p>
  1919. <pre>% which watch
  1920. watch not found</pre>
  1921. <p>
  1922. Thankfully this can be fixed easily by using homebrew to install the watch binary:
  1923. </p>
  1924. <pre>% brew install watch</pre>
  1925. ]]></content:encoded>
  1926.  </item>
  1927.  
  1928.  <item>
  1929.    <title>SlackSecOps - delegating remediation to employees</title>
  1930.    <link>https://blog.x-way.org/Misc/2024/11/01/SlackSecOps-delegating-remediation-to-employees.html</link>
  1931.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324416</guid>
  1932.    <dc:creator>Andreas Jaggi</dc:creator>
  1933.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  1934.    <pubDate>Fri, 01 Nov 2024 16:05:10 +0100</pubDate>
  1935.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  1936.    <description><![CDATA[<p>
  1937. In the <a href="https://mayakaczorowski.com/blogs/slacksecops" title="Delegating security remediation to employees via Slack">Delegating security remediation to employees via Slack</a> article, <a href="https://mayakaczorowski.com/" title="Maya Kaczorowski">Maya Kaczorowski</a> coins the term SlackSecOps to describe automation and delegation of security tasks to employees.<br>
  1938. The article gives a nice overview of some ideas that are more and more applied by security teams and tools.
  1939. </p>
  1940. <p>
  1941. A couple years ago such ideas were mostly custom built bots/automations at larger companies, but not shared more widely.<br>
  1942. Nowadays there seems to be a much broader adoption of these in companies, especially the Alert and Remind categories.<br>
  1943. The most interesting ones are Delegation and Respond, which I would claim also can have the most impact.
  1944. </p>
  1945. <p>
  1946. By delegating security remediation tasks directly to the involved persons, the handling of the task becomes more efficient as all the context is available.<br>
  1947. And then by providing the automation to the delegee to directly perform the remediation in self-service, this critically shortens the response cycle.<br>
  1948. With the shortened response cycle, the exposure window of a vulnerable configuration is minimized, which reduces the risk of exploitation.
  1949. </p>
  1950. <p>
  1951. <img src="https://blog.x-way.org/images/slacksecops.png" width="584" height="581" alt="The four categories of security interactions via Slack: Remind, Alert, Delegate, Respond" />
  1952. </p>
  1953. ]]></description>
  1954.    <content:encoded><![CDATA[<p>
  1955. In the <a href="https://mayakaczorowski.com/blogs/slacksecops" title="Delegating security remediation to employees via Slack">Delegating security remediation to employees via Slack</a> article, <a href="https://mayakaczorowski.com/" title="Maya Kaczorowski">Maya Kaczorowski</a> coins the term SlackSecOps to describe automation and delegation of security tasks to employees.<br>
  1956. The article gives a nice overview of some ideas that are more and more applied by security teams and tools.
  1957. </p>
  1958. <p>
  1959. A couple years ago such ideas were mostly custom built bots/automations at larger companies, but not shared more widely.<br>
  1960. Nowadays there seems to be a much broader adoption of these in companies, especially the Alert and Remind categories.<br>
  1961. The most interesting ones are Delegation and Respond, which I would claim also can have the most impact.
  1962. </p>
  1963. <p>
  1964. By delegating security remediation tasks directly to the involved persons, the handling of the task becomes more efficient as all the context is available.<br>
  1965. And then by providing the automation to the delegee to directly perform the remediation in self-service, this critically shortens the response cycle.<br>
  1966. With the shortened response cycle, the exposure window of a vulnerable configuration is minimized, which reduces the risk of exploitation.
  1967. </p>
  1968. <p>
  1969. <img src="https://blog.x-way.org/images/slacksecops.png" width="584" height="581" alt="The four categories of security interactions via Slack: Remind, Alert, Delegate, Respond" />
  1970. </p>
  1971. ]]></content:encoded>
  1972.  </item>
  1973.  
  1974.  <item>
  1975.    <title>The 250KB Club</title>
  1976.    <link>https://blog.x-way.org/Misc/2024/10/31/The-250KB-Club.html</link>
  1977.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324415</guid>
  1978.    <dc:creator>Andreas Jaggi</dc:creator>
  1979.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  1980.    <pubDate>Thu, 31 Oct 2024 17:44:23 +0100</pubDate>
  1981.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  1982.    <description><![CDATA[<p>
  1983. Similar to <a href="https://blog.x-way.org/Misc/2024/10/31/The-512KB-Club.html" title="x-log - The 512KB Club">the 512KB club</a>, there exists <a href="https://250kb.club/" title="The 250kb club">the 250KB club</a>.
  1984. It collects web pages that focus on performance, efficiency and accessibility.<br>
  1985. Qualifying sites must fullfil one requirement.<br>
  1986. The website must not exceed 256KB compressed size.
  1987. </p>
  1988. <p>
  1989. 256KB Club also contains very niche sites and is great to discover some new corners of the Internet.<br>
  1990. The linked pages are often minimalistic personal pages and geeky blogs.<br>
  1991. </p>
  1992. <p>
  1993. I submitted my blog for inclusion in the club, as it measures less than 250KB.<br>
  1994. It was accepted a day earlier than for the 512KB club :-)<br>
  1995. Now the blog has its own page in the club: <a href="https://250kb.club/blog-x-way-org/" title="The 250kb club">https://250kb.club/blog-x-way-org/</a>
  1996. </p>
  1997. <p>
  1998. <a title="250KB Club page" href="https://250kb.club/blog-x-way-org"><img alt="badge: proud member of the 250KB Club" src="https://blog.x-way.org/images/color_badge_bright.png" width="200" height="30" /></a>
  1999. </p>
  2000. ]]></description>
  2001.    <content:encoded><![CDATA[<p>
  2002. Similar to <a href="https://blog.x-way.org/Misc/2024/10/31/The-512KB-Club.html" title="x-log - The 512KB Club">the 512KB club</a>, there exists <a href="https://250kb.club/" title="The 250kb club">the 250KB club</a>.
  2003. It collects web pages that focus on performance, efficiency and accessibility.<br>
  2004. Qualifying sites must fullfil one requirement.<br>
  2005. The website must not exceed 256KB compressed size.
  2006. </p>
  2007. <p>
  2008. 256KB Club also contains very niche sites and is great to discover some new corners of the Internet.<br>
  2009. The linked pages are often minimalistic personal pages and geeky blogs.<br>
  2010. </p>
  2011. <p>
  2012. I submitted my blog for inclusion in the club, as it measures less than 250KB.<br>
  2013. It was accepted a day earlier than for the 512KB club :-)<br>
  2014. Now the blog has its own page in the club: <a href="https://250kb.club/blog-x-way-org/" title="The 250kb club">https://250kb.club/blog-x-way-org/</a>
  2015. </p>
  2016. <p>
  2017. <a title="250KB Club page" href="https://250kb.club/blog-x-way-org"><img alt="badge: proud member of the 250KB Club" src="https://blog.x-way.org/images/color_badge_bright.png" width="200" height="30" /></a>
  2018. </p>
  2019. ]]></content:encoded>
  2020.  </item>
  2021.  
  2022.  <item>
  2023.    <title>The 512KB Club</title>
  2024.    <link>https://blog.x-way.org/Misc/2024/10/31/The-512KB-Club.html</link>
  2025.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324414</guid>
  2026.    <dc:creator>Andreas Jaggi</dc:creator>
  2027.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2028.    <pubDate>Thu, 31 Oct 2024 16:51:35 +0100</pubDate>
  2029.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  2030.    <description><![CDATA[<p>
  2031. Some time ago I discovered the <a href="https://512kb.club/" title="512KB Club | A showcase of lightweight websites.">512KB club</a>.
  2032. It collects performance-focused websites from across the Internet.<br>
  2033. Qualifying sites must fullfil two requirements to participate.<br>
  2034. The site must provide a reasonable amount of content.<br>
  2035. And the total uncompressed web resources must not exceed 512KB.
  2036. </p>
  2037. <p>
  2038. 512KB Club is a nice resource to discover more niche sites on the Internet.<br>
  2039. Often these are handcrafted personal sites and blogs with unique content.<br>
  2040. They remind me of all the unique personal sites and blogs from before the web2.0/social-media/walled-garden time.
  2041. </p>
  2042. <p>
  2043. My blog is also very lightweight (currently clocking <a href="https://radar.cloudflare.com/scan/a327a135-e7e3-4bad-8902-c5fcb535db15/summary" title="URL Scanner | Cloudflare Radar">39.48kB on the Cloudflare URL Scanner</a>), thus I submitted it for inclusion in the list.<br>
  2044. It was accepted recently and is now listed as part of the <a href="https://512kb.club/#100" title="512KB Club | Green Team">Green Team</a> (sites smaller than 100KB).
  2045. </p>
  2046. <p>
  2047. <a href="https://512kb.club" title="a proud member of the green team of 512KB club"><img src="https://blog.x-way.org/images/green-team.svg" alt="a proud member of the green team of 512KB club" width="234" height="30" /></a>
  2048. </p>
  2049. ]]></description>
  2050.    <content:encoded><![CDATA[<p>
  2051. Some time ago I discovered the <a href="https://512kb.club/" title="512KB Club | A showcase of lightweight websites.">512KB club</a>.
  2052. It collects performance-focused websites from across the Internet.<br>
  2053. Qualifying sites must fullfil two requirements to participate.<br>
  2054. The site must provide a reasonable amount of content.<br>
  2055. And the total uncompressed web resources must not exceed 512KB.
  2056. </p>
  2057. <p>
  2058. 512KB Club is a nice resource to discover more niche sites on the Internet.<br>
  2059. Often these are handcrafted personal sites and blogs with unique content.<br>
  2060. They remind me of all the unique personal sites and blogs from before the web2.0/social-media/walled-garden time.
  2061. </p>
  2062. <p>
  2063. My blog is also very lightweight (currently clocking <a href="https://radar.cloudflare.com/scan/a327a135-e7e3-4bad-8902-c5fcb535db15/summary" title="URL Scanner | Cloudflare Radar">39.48kB on the Cloudflare URL Scanner</a>), thus I submitted it for inclusion in the list.<br>
  2064. It was accepted recently and is now listed as part of the <a href="https://512kb.club/#100" title="512KB Club | Green Team">Green Team</a> (sites smaller than 100KB).
  2065. </p>
  2066. <p>
  2067. <a href="https://512kb.club" title="a proud member of the green team of 512KB club"><img src="https://blog.x-way.org/images/green-team.svg" alt="a proud member of the green team of 512KB club" width="234" height="30" /></a>
  2068. </p>
  2069. ]]></content:encoded>
  2070.  </item>
  2071.  
  2072.  <item>
  2073.    <title>cowsay_CLENA</title>
  2074.    <link>https://blog.x-way.org/Coding/2024/10/30/cowsay-CLENA.html</link>
  2075.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324413</guid>
  2076.    <dc:creator>Andreas Jaggi</dc:creator>
  2077.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2078.    <pubDate>Wed, 30 Oct 2024 06:34:26 +0100</pubDate>
  2079.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  2080.    <description><![CDATA[<p>
  2081. Found this cute snippet in the <a href="https://github.com/numworks/epsilon/blob/master/Makefile#L163C1-L180C26" title="epsilon/Makefile - numworks/epsilon - GitHub">Makefile</a> of the <a href="https://www.numworks.com/" title="NumWorks">NumWorks</a> <a href="https://github.com/numworks/epsilon/" title="GitHub - numworks/epsilon: Modern graphing calculator operating system.">Epsilon codebase</a>.
  2082. It is a rudimentary implementation of the <a href="https://en.wikipedia.org/wiki/Cowsay" title="cowsay - Wikipedia">cowsay</a> functionality.
  2083. </p>
  2084. <p>
  2085. We also see how it is used in the <code>clena: cowsay_CLENA clean</code> part.<br>
  2086. I like how it reminds about the typo when calling the <code>clena</code> instead of the <code>clean</code> target.<br>
  2087. It gives a clear but unintrusive message about the typo, and then also does what was intented (running the <code>clean</code> target).
  2088. </p>
  2089. <pre>.PHONY: cowsay_%
  2090. cowsay_%:
  2091. @echo " -------"
  2092. @echo "| $(*F) |"
  2093. @echo " -------"
  2094. @echo "        \\   ^__^"
  2095. @echo "         \\  (oo)\\_______"
  2096. @echo "            (__)\\       )\\/\\"
  2097. @echo "                ||----w |"
  2098. @echo "                ||     ||"
  2099.  
  2100. .PHONY: clena
  2101. clena: cowsay_CLENA clean</pre>
  2102. ]]></description>
  2103.    <content:encoded><![CDATA[<p>
  2104. Found this cute snippet in the <a href="https://github.com/numworks/epsilon/blob/master/Makefile#L163C1-L180C26" title="epsilon/Makefile - numworks/epsilon - GitHub">Makefile</a> of the <a href="https://www.numworks.com/" title="NumWorks">NumWorks</a> <a href="https://github.com/numworks/epsilon/" title="GitHub - numworks/epsilon: Modern graphing calculator operating system.">Epsilon codebase</a>.
  2105. It is a rudimentary implementation of the <a href="https://en.wikipedia.org/wiki/Cowsay" title="cowsay - Wikipedia">cowsay</a> functionality.
  2106. </p>
  2107. <p>
  2108. We also see how it is used in the <code>clena: cowsay_CLENA clean</code> part.<br>
  2109. I like how it reminds about the typo when calling the <code>clena</code> instead of the <code>clean</code> target.<br>
  2110. It gives a clear but unintrusive message about the typo, and then also does what was intented (running the <code>clean</code> target).
  2111. </p>
  2112. <pre>.PHONY: cowsay_%
  2113. cowsay_%:
  2114. @echo " -------"
  2115. @echo "| $(*F) |"
  2116. @echo " -------"
  2117. @echo "        \\   ^__^"
  2118. @echo "         \\  (oo)\\_______"
  2119. @echo "            (__)\\       )\\/\\"
  2120. @echo "                ||----w |"
  2121. @echo "                ||     ||"
  2122.  
  2123. .PHONY: clena
  2124. clena: cowsay_CLENA clean</pre>
  2125. ]]></content:encoded>
  2126.  </item>
  2127.  
  2128.  <item>
  2129.    <title>Realizing Meshtastic's Promise with the T-Deck</title>
  2130.    <link>https://blog.x-way.org/Radio/2024/10/28/Realizing-Meshtastics-Promise-with-the-T-Deck.html</link>
  2131.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324412</guid>
  2132.    <dc:creator>Andreas Jaggi</dc:creator>
  2133.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2134.    <pubDate>Mon, 28 Oct 2024 22:32:34 +0100</pubDate>
  2135.    <category domain="https://blog.x-way.org/Radio/">Radio</category>
  2136.    <description><![CDATA[<p>
  2137. In the <a href="https://www.jeffgeerling.com/blog/2024/realizing-meshtastics-promise-t-deck" title="Realizing Meshtastic's Promise with the T-Deck | Jeff Geerling">Realizing Meshtastic's Promise with the T-Deck</a> article, Jeff Geerling showcases the experimental <a href="https://github.com/meshtastic/device-ui" title="meshtastic/device-ui: meshtastic device-ui library">device-ui</a> for the <a href="https://www.lilygo.cc/products/t-deck" title="T-Deck - LILYGO">T-Deck</a>.
  2138. </p>
  2139. <p>
  2140. This experimental UI looks already very pretty and I expect that it will provide a very nice Meshtastic experience once all features have been implemented.<br>
  2141. The article also contains instructions on how to install a development version of the experimantal UI based on some CI snapshots.
  2142. Maybe something to try out one of these days :-)
  2143. </p>
  2144. ]]></description>
  2145.    <content:encoded><![CDATA[<p>
  2146. In the <a href="https://www.jeffgeerling.com/blog/2024/realizing-meshtastics-promise-t-deck" title="Realizing Meshtastic's Promise with the T-Deck | Jeff Geerling">Realizing Meshtastic's Promise with the T-Deck</a> article, Jeff Geerling showcases the experimental <a href="https://github.com/meshtastic/device-ui" title="meshtastic/device-ui: meshtastic device-ui library">device-ui</a> for the <a href="https://www.lilygo.cc/products/t-deck" title="T-Deck - LILYGO">T-Deck</a>.
  2147. </p>
  2148. <p>
  2149. This experimental UI looks already very pretty and I expect that it will provide a very nice Meshtastic experience once all features have been implemented.<br>
  2150. The article also contains instructions on how to install a development version of the experimantal UI based on some CI snapshots.
  2151. Maybe something to try out one of these days :-)
  2152. </p>
  2153. ]]></content:encoded>
  2154.  </item>
  2155.  
  2156.  <item>
  2157.    <title>Writing one sentence per line</title>
  2158.    <link>https://blog.x-way.org/Misc/2024/10/23/Writing-one-sentence-per-line.html</link>
  2159.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324411</guid>
  2160.    <dc:creator>Andreas Jaggi</dc:creator>
  2161.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2162.    <pubDate>Wed, 23 Oct 2024 16:18:13 +0200</pubDate>
  2163.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  2164.    <description><![CDATA[<p>
  2165. In his <a href="https://sive.rs/1s" title="Writing one sentence per line | Derek Sivers">Writing one sentence per line</a> article, Derek Sivers explains the benefits of writing one sentence per line.<br>
  2166. The approach leverages that whitespace in HTML source code is collapsed when being rendered in the browser.<br>
  2167. Thus we can have a much more writer-friendly text formatting when editing the text, while still providing a nicely rendered output to whoever views the resulting page in a browser.
  2168. </p>
  2169. <p>
  2170. The main advantages outlined in the article are:<br>
  2171. It helps you judge each sentence on its own.<br>
  2172. It helps you vary sentence length.<br>
  2173. It helps you move sentences.<br>
  2174. It helps you see first and last words.
  2175. </p>
  2176. <p>
  2177. I really like this approach and will apply it in my future writing on the blog.<br>
  2178. The indenting of text (not explicitly mentioned in the article but visible in the source) is also something I will try to adopt.
  2179. </p>
  2180. <p>
  2181. Here is how the above two paragraphs look in the source text:
  2182. </p>
  2183. <pre>&lt;p&gt;
  2184. The main advantages outlined in the article are:&lt;br&gt;
  2185. It helps you judge each sentence on its own.&lt;br&gt;
  2186. It helps you vary sentence length.&lt;br&gt;
  2187. It helps you move sentences.&lt;br&gt;
  2188. It helps you see first and last words.
  2189. &lt;/p&gt;
  2190. &lt;p&gt;
  2191. I really like this approach and will apply it in my future writing on the blog.&lt;br&gt;
  2192. The indenting of text (not explicitly mentioned in the article but visible in the source) is also something I will try to adopt.
  2193. &lt;/p&gt;</pre>
  2194. ]]></description>
  2195.    <content:encoded><![CDATA[<p>
  2196. In his <a href="https://sive.rs/1s" title="Writing one sentence per line | Derek Sivers">Writing one sentence per line</a> article, Derek Sivers explains the benefits of writing one sentence per line.<br>
  2197. The approach leverages that whitespace in HTML source code is collapsed when being rendered in the browser.<br>
  2198. Thus we can have a much more writer-friendly text formatting when editing the text, while still providing a nicely rendered output to whoever views the resulting page in a browser.
  2199. </p>
  2200. <p>
  2201. The main advantages outlined in the article are:<br>
  2202. It helps you judge each sentence on its own.<br>
  2203. It helps you vary sentence length.<br>
  2204. It helps you move sentences.<br>
  2205. It helps you see first and last words.
  2206. </p>
  2207. <p>
  2208. I really like this approach and will apply it in my future writing on the blog.<br>
  2209. The indenting of text (not explicitly mentioned in the article but visible in the source) is also something I will try to adopt.
  2210. </p>
  2211. <p>
  2212. Here is how the above two paragraphs look in the source text:
  2213. </p>
  2214. <pre>&lt;p&gt;
  2215. The main advantages outlined in the article are:&lt;br&gt;
  2216. It helps you judge each sentence on its own.&lt;br&gt;
  2217. It helps you vary sentence length.&lt;br&gt;
  2218. It helps you move sentences.&lt;br&gt;
  2219. It helps you see first and last words.
  2220. &lt;/p&gt;
  2221. &lt;p&gt;
  2222. I really like this approach and will apply it in my future writing on the blog.&lt;br&gt;
  2223. The indenting of text (not explicitly mentioned in the article but visible in the source) is also something I will try to adopt.
  2224. &lt;/p&gt;</pre>
  2225. ]]></content:encoded>
  2226.  </item>
  2227.  
  2228.  <item>
  2229.    <title>sshidentifierlogger</title>
  2230.    <link>https://blog.x-way.org/Networking/2024/10/12/sshidentifierlogger.html</link>
  2231.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324410</guid>
  2232.    <dc:creator>Andreas Jaggi</dc:creator>
  2233.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2234.    <pubDate>Sat, 12 Oct 2024 21:54:40 +0200</pubDate>
  2235.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  2236.    <description><![CDATA[<p><a href="https://github.com/x-way/sshidentifierlogger" title="x-way/sshidentifierlogger">sshidentifierlogger</a> is a small tool that I started writing about 5 years ago and have been using on some of my hosts.</p>
  2237. <p>Its purpose is to listen to network traffic and passively collect identification strings during SSH handshakes.<br>Initially I had a lot of <a href="http://www.fail2ban.org/" title="fail2ban">fail2ban</a> activity on my <a href="https://en.wikipedia.org/wiki/Jump_server" title="Jump server - Wikipedia">jumphost</a>, blocking many SSH scanning/enumeration/bruteforcing attempts and wanted to know what software the attackers use.</p>
  2238. <p>A bit particular is that sshidentifierlogger does not depend on the classic C library libpcap, but rather uses the go-native <a href="https://github.com/gopacket/gopacket/tree/master/pcapgo" title="gopacket/pcapgo">pcapgo</a> implementation by <a href="https://github.com/gopacket/gopacket" title="gopacket/gopacket">gopacket</a>.<br>Thus it can be cross-compiled on any platform, which comes in handy when you do not want to install the full go buildchain on your jumphost.</p>
  2239. <p>The collected data is quite interesting (most of the scanning used to be done with libssh2).<br>Which I did leverage to write iptables rules blocking packets with undesired SSH identification strings.<br>This has been quite successfull in reducing the amount of fail2ban activity :-)</p>
  2240. ]]></description>
  2241.    <content:encoded><![CDATA[<p><a href="https://github.com/x-way/sshidentifierlogger" title="x-way/sshidentifierlogger">sshidentifierlogger</a> is a small tool that I started writing about 5 years ago and have been using on some of my hosts.</p>
  2242. <p>Its purpose is to listen to network traffic and passively collect identification strings during SSH handshakes.<br>Initially I had a lot of <a href="http://www.fail2ban.org/" title="fail2ban">fail2ban</a> activity on my <a href="https://en.wikipedia.org/wiki/Jump_server" title="Jump server - Wikipedia">jumphost</a>, blocking many SSH scanning/enumeration/bruteforcing attempts and wanted to know what software the attackers use.</p>
  2243. <p>A bit particular is that sshidentifierlogger does not depend on the classic C library libpcap, but rather uses the go-native <a href="https://github.com/gopacket/gopacket/tree/master/pcapgo" title="gopacket/pcapgo">pcapgo</a> implementation by <a href="https://github.com/gopacket/gopacket" title="gopacket/gopacket">gopacket</a>.<br>Thus it can be cross-compiled on any platform, which comes in handy when you do not want to install the full go buildchain on your jumphost.</p>
  2244. <p>The collected data is quite interesting (most of the scanning used to be done with libssh2).<br>Which I did leverage to write iptables rules blocking packets with undesired SSH identification strings.<br>This has been quite successfull in reducing the amount of fail2ban activity :-)</p>
  2245. ]]></content:encoded>
  2246.  </item>
  2247.  
  2248.  <item>
  2249.    <title>Styling blockquote and pre elements</title>
  2250.    <link>https://blog.x-way.org/Webdesign/2024/10/11/Styling-blockquote-and-pre-elements.html</link>
  2251.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324409</guid>
  2252.    <dc:creator>Andreas Jaggi</dc:creator>
  2253.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2254.    <pubDate>Fri, 11 Oct 2024 18:14:02 +0200</pubDate>
  2255.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  2256.    <description><![CDATA[<p>The <a href="https://htmlforpeople.com/css-basics#blockquotes" title="CSS Basics - Blockquotes">Blockquotes</a> and <a href="https://htmlforpeople.com/css-basics#pre-formatted-text" title="CSS Basics - Pre-formatted text">Pre-formatted text</a> sections in the <a href="https://htmlforpeople.com/" title="HTML for People">HTML for People</a> book inspired me to improve the styling of the blog.<br>The following code now defines the visual appearance of <code>blockquote</code> and <code>pre</code> elements in the blog:</p>
  2257. <pre>blockquote {
  2258. border-left: 1px dotted #ffbb18;
  2259. padding-left: 21px;
  2260. margin-left: 21px;
  2261. }
  2262. pre {
  2263. background-color: #f9f7f7;
  2264. border-radius: 4px;
  2265. padding: 4px;
  2266. }</pre>
  2267. <p>To see it in effect, scroll down to the <a href="https://blog.x-way.org/Mac/2024/09/29/Hidden-Pref-to-Restore-Slow-Motion-Dock-Minimizing-on-MacOS.html" title="x-log - Hidden Pref to Restore Slow Motion Dock Minimizing on MacOS">Hidden Pref to Restore Slow Motion Dock Minimizing on MacOS</a> or <a href="https://blog.x-way.org/Coding/2024/09/25/Notifying-external-services-about-changes-in-the-blog.html" title="x-log - Notifying external services about changes in the blog">Notifying external services about changes in the blog</a> posts.</p>
  2268. ]]></description>
  2269.    <content:encoded><![CDATA[<p>The <a href="https://htmlforpeople.com/css-basics#blockquotes" title="CSS Basics - Blockquotes">Blockquotes</a> and <a href="https://htmlforpeople.com/css-basics#pre-formatted-text" title="CSS Basics - Pre-formatted text">Pre-formatted text</a> sections in the <a href="https://htmlforpeople.com/" title="HTML for People">HTML for People</a> book inspired me to improve the styling of the blog.<br>The following code now defines the visual appearance of <code>blockquote</code> and <code>pre</code> elements in the blog:</p>
  2270. <pre>blockquote {
  2271. border-left: 1px dotted #ffbb18;
  2272. padding-left: 21px;
  2273. margin-left: 21px;
  2274. }
  2275. pre {
  2276. background-color: #f9f7f7;
  2277. border-radius: 4px;
  2278. padding: 4px;
  2279. }</pre>
  2280. <p>To see it in effect, scroll down to the <a href="https://blog.x-way.org/Mac/2024/09/29/Hidden-Pref-to-Restore-Slow-Motion-Dock-Minimizing-on-MacOS.html" title="x-log - Hidden Pref to Restore Slow Motion Dock Minimizing on MacOS">Hidden Pref to Restore Slow Motion Dock Minimizing on MacOS</a> or <a href="https://blog.x-way.org/Coding/2024/09/25/Notifying-external-services-about-changes-in-the-blog.html" title="x-log - Notifying external services about changes in the blog">Notifying external services about changes in the blog</a> posts.</p>
  2281. ]]></content:encoded>
  2282.  </item>
  2283.  
  2284.  <item>
  2285.    <title>Meshtastic Web Serial in Linux as non-root user</title>
  2286.    <link>https://blog.x-way.org/Radio/2024/10/05/Meshtastic-Web-Serial-in-Linux-as-non-root-user.html</link>
  2287.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324408</guid>
  2288.    <dc:creator>Andreas Jaggi</dc:creator>
  2289.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2290.    <pubDate>Sat, 05 Oct 2024 18:49:09 +0200</pubDate>
  2291.    <category domain="https://blog.x-way.org/Radio/">Radio</category>
  2292.    <description><![CDATA[<p>Today I played around a bit with a <a href="https://meshtastic.org/" title="Meshtastic">Meshtastic</a> device and tried to configure it through the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Web_Serial_API" title="Web Serial API - Web APIs | MDN">Web Serial API</a> in Chrome.<br>On my Linux system it could see the device but not really change any values, update firmware etc.</p>
  2293. <p>This confused me for some time, until I looked at the permissions of <code>/dev/ttyACM0</code> (which were <samp>crw-rw----</samp>).<br>A quick <kbd>sudo chmod a+rw /dev/ttyACM0</kbd> later, and I could write to the configuration of the Meshtastic device.<br>The more tedious part was that after every config change the device rebooted and the USB serial connection was re-initialized by Linux, thus I needed to re-run the chmod command after every change. Luckily I figured out how to enable WiFi on the device and from then on no longer needed the serial access.</p>
  2294. ]]></description>
  2295.    <content:encoded><![CDATA[<p>Today I played around a bit with a <a href="https://meshtastic.org/" title="Meshtastic">Meshtastic</a> device and tried to configure it through the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Web_Serial_API" title="Web Serial API - Web APIs | MDN">Web Serial API</a> in Chrome.<br>On my Linux system it could see the device but not really change any values, update firmware etc.</p>
  2296. <p>This confused me for some time, until I looked at the permissions of <code>/dev/ttyACM0</code> (which were <samp>crw-rw----</samp>).<br>A quick <kbd>sudo chmod a+rw /dev/ttyACM0</kbd> later, and I could write to the configuration of the Meshtastic device.<br>The more tedious part was that after every config change the device rebooted and the USB serial connection was re-initialized by Linux, thus I needed to re-run the chmod command after every change. Luckily I figured out how to enable WiFi on the device and from then on no longer needed the serial access.</p>
  2297. ]]></content:encoded>
  2298.  </item>
  2299.  
  2300.  <item>
  2301.    <title>Enable Visual Voicemail on your iPhone with Galaxus Mobile</title>
  2302.    <link>https://blog.x-way.org/Misc/2024/09/30/Enable-Visual-Voicemail-on-your-iPhone-with-Galaxus-Mobile.html</link>
  2303.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324407</guid>
  2304.    <dc:creator>Andreas Jaggi</dc:creator>
  2305.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2306.    <pubDate>Mon, 30 Sep 2024 20:47:35 +0200</pubDate>
  2307.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  2308.    <description><![CDATA[<p>Turns out that the procedure for enabling Visual Voicemail with <a href="https://mobile.galaxus.ch/" title="Galaxus Mobile">Galaxus Mobile</a> is the same as for <a href="https://blog.x-way.org/Misc/2024/09/24/Enable-Visual-Voicemail-on-your-iPhone-with-TalkTalk.html" title="Enable Visual Voicemail on your iPhone with TalkTalk">TalkTalk</a>.</p>
  2309. <p>In my case their database entry was somehow stuck and I first needed to send a <code>VVM OFF</code> to <code>935</code> before starting <a href="https://blog.x-way.org/Misc/2024/09/24/Enable-Visual-Voicemail-on-your-iPhone-with-TalkTalk.html" title="Enable Visual Voicemail on your iPhone with TalkTalk">the procedure</a>.</p>
  2310. ]]></description>
  2311.    <content:encoded><![CDATA[<p>Turns out that the procedure for enabling Visual Voicemail with <a href="https://mobile.galaxus.ch/" title="Galaxus Mobile">Galaxus Mobile</a> is the same as for <a href="https://blog.x-way.org/Misc/2024/09/24/Enable-Visual-Voicemail-on-your-iPhone-with-TalkTalk.html" title="Enable Visual Voicemail on your iPhone with TalkTalk">TalkTalk</a>.</p>
  2312. <p>In my case their database entry was somehow stuck and I first needed to send a <code>VVM OFF</code> to <code>935</code> before starting <a href="https://blog.x-way.org/Misc/2024/09/24/Enable-Visual-Voicemail-on-your-iPhone-with-TalkTalk.html" title="Enable Visual Voicemail on your iPhone with TalkTalk">the procedure</a>.</p>
  2313. ]]></content:encoded>
  2314.  </item>
  2315.  
  2316.  <item>
  2317.    <title>Hidden Pref to Restore Slow-Motion Dock Minimizing on MacOS</title>
  2318.    <link>https://blog.x-way.org/Mac/2024/09/29/Hidden-Pref-to-Restore-Slow-Motion-Dock-Minimizing-on-MacOS.html</link>
  2319.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324406</guid>
  2320.    <dc:creator>Andreas Jaggi</dc:creator>
  2321.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2322.    <pubDate>Sun, 29 Sep 2024 01:16:45 +0200</pubDate>
  2323.    <category domain="https://blog.x-way.org/Mac/">Mac</category>
  2324.    <description><![CDATA[<p><a href="https://daringfireball.net/linked/2024/09/28/hidden-pref-to-restore-slow-motion-dock-minimizing-on-macos" title="Daring Fireball: Hidden Pref to Restore Slow-Motion Dock Minimizing on MacOS">Daring Fireball describes</a> how to restore the old trick of slow motion MacOS Dock effects:</p>
  2325. <blockquote cite="https://daringfireball.net/linked/2024/09/28/hidden-pref-to-restore-slow-motion-dock-minimizing-on-macos">
  2326. <p>In the midst of recording last week’s episode of The Talk Show with Nilay Patel, I offhandedly mentioned the age-old trick of holding down the Shift key while minimizing a window (clicking the yellow button) to see the genie effect in slow motion. Nilay was like “Wait, what? That’s not working for me...” and we moved on.</p>
  2327. <p><a href="https://mastodon.social/@charlesa/113212025522260922">What I’d forgotten</a> is that Apple had removed this as default behavior a few years ago (I think in MacOS 10.14 Mojave), but you can restore the feature with this hidden preference, typed in Terminal:</p>
  2328. <pre>defaults write com.apple.dock slow-motion-allowed -bool YES</pre>
  2329. <p>Then restart the Dock:</p>
  2330. <pre>killall Dock</pre>
  2331. <p>Or, in a single command:</p>
  2332. <pre>defaults write com.apple.dock slow-motion-allowed -bool YES; killall Dock</pre>
  2333. <p>I had forgotten that this had become a hidden preference, and that I’d long ago enabled it.</p>
  2334. </blockquote>
  2335. ]]></description>
  2336.    <content:encoded><![CDATA[<p><a href="https://daringfireball.net/linked/2024/09/28/hidden-pref-to-restore-slow-motion-dock-minimizing-on-macos" title="Daring Fireball: Hidden Pref to Restore Slow-Motion Dock Minimizing on MacOS">Daring Fireball describes</a> how to restore the old trick of slow motion MacOS Dock effects:</p>
  2337. <blockquote cite="https://daringfireball.net/linked/2024/09/28/hidden-pref-to-restore-slow-motion-dock-minimizing-on-macos">
  2338. <p>In the midst of recording last week’s episode of The Talk Show with Nilay Patel, I offhandedly mentioned the age-old trick of holding down the Shift key while minimizing a window (clicking the yellow button) to see the genie effect in slow motion. Nilay was like “Wait, what? That’s not working for me...” and we moved on.</p>
  2339. <p><a href="https://mastodon.social/@charlesa/113212025522260922">What I’d forgotten</a> is that Apple had removed this as default behavior a few years ago (I think in MacOS 10.14 Mojave), but you can restore the feature with this hidden preference, typed in Terminal:</p>
  2340. <pre>defaults write com.apple.dock slow-motion-allowed -bool YES</pre>
  2341. <p>Then restart the Dock:</p>
  2342. <pre>killall Dock</pre>
  2343. <p>Or, in a single command:</p>
  2344. <pre>defaults write com.apple.dock slow-motion-allowed -bool YES; killall Dock</pre>
  2345. <p>I had forgotten that this had become a hidden preference, and that I’d long ago enabled it.</p>
  2346. </blockquote>
  2347. ]]></content:encoded>
  2348.  </item>
  2349.  
  2350.  <item>
  2351.    <title>Notifying external services about changes in the blog</title>
  2352.    <link>https://blog.x-way.org/Coding/2024/09/25/Notifying-external-services-about-changes-in-the-blog.html</link>
  2353.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324405</guid>
  2354.    <dc:creator>Andreas Jaggi</dc:creator>
  2355.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2356.    <pubDate>Wed, 25 Sep 2024 10:23:25 +0200</pubDate>
  2357.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  2358.    <description><![CDATA[<p>For some time now, I'm <a href="https://blog.x-way.org/Coding/2024/06/12/blogs-still-Pinging.html" title="blo.gs still Pinging - x-log">notifying blo.gs about changes in the blog</a>. After looking a bit into how search engines percieve my website recently, I learned that they also have some notification mechanisms for new pages/blogposts.</p>
  2359. <p>Thus I upgraded the oneliner into a dedicated script to notify external services about changes in the blog.<br>It is optimized for my Jekyll setup, where the generated pages in the _site folder are stored in git.<br>The notification ignores changes to summarized pages like rss.xml etc to only trigger notifications when there are changes in the original blog posts.</p>
  2360. <p>Here's the script, feel free to re-use (it expects to have <var>MYDOMAIN</var>, <var>INDEXNOW_API_KEY</var> and <var>BING_API_KEY</var> defined as environment variables):</p>
  2361. <pre>#!/bin/bash
  2362.  
  2363. set -e
  2364. set -u
  2365. set -o pipefail
  2366.  
  2367. CHANGES="$(git diff --name-only HEAD HEAD~1 -- _site)"
  2368.  
  2369. # early abort if no changes on _site
  2370. if [ -z "$CHANGES" ] ; then
  2371. echo "No changes in _site found"
  2372. exit 0
  2373. fi
  2374.  
  2375. # build URL list
  2376. URLLIST="\"https://${MYDOMAIN}/\""
  2377. for f in $CHANGES ; do
  2378. case "$f" in
  2379. _site/robots.txt|_site/humans.txt|_site/about.html|_site/rss.xml|_site/atom.xml|_site/feed.json|_site/sitemap.xml)
  2380. continue
  2381. ;;
  2382. *)
  2383. url=$(echo "$f"|sed -e "sX^_siteXhttps://${MYDOMAIN}X")
  2384. URLLIST="${URLLIST},\"${url}\""
  2385. ;;
  2386. esac
  2387. done
  2388.  
  2389. if [ "\"https://${MYDOMAIN}/\"" = "$URLLIST" ] ; then
  2390. echo "No relevant changes in _site found, skipping notifications"
  2391. exit 0
  2392. fi
  2393.  
  2394. # notify ping.blo.gs (Automattic) about updates
  2395. curl --fail -s -D - -X POST http://ping.blo.gs -H 'content-type: text/xml' --data "&lt;?xml version=\"1.0\"?&gt;&lt;methodCall&gt;&lt;methodName&gt;weblogUpdates.extendedPing&lt;/methodName&gt;&lt;params&gt;&lt;param&gt;&lt;value&gt;x-log&lt;/value&gt;&lt;/param&gt;&lt;param&gt;&lt;value&gt;https://${MYDOMAIN}/&lt;/value&gt;&lt;/param&gt;&lt;param&gt;&lt;value&gt;&lt;/value&gt;&lt;/param&gt;&lt;param&gt;&lt;value&gt;https://${MYDOMAIN}/rss.xml&lt;/value&gt;&lt;/param&gt;&lt;/params&gt;&lt;/methodCall&gt;"
  2396.  
  2397. # report changed URLs to indexnow, include /indexnow canary URL
  2398. curl --fail -s -D - -X POST https://api.indexnow.org/IndexNow -H 'content-type: application/json; charset=utf-8' --data "{\"host\":\"${MYDOMAIN}\",\"key\":\"${INDEXNOW_API_KEY}\",\"urlList\":[${URLLIST},\"https://${MYDOMAIN}/indexnow\"]}"
  2399.  
  2400. # report changes URLs to bing, include /bingsubmit canary URL
  2401. curl --fail -s -D - -X POST "https://ssl.bing.com/webmaster/api.svc/json/SubmitUrlbatch?apikey=${BING_API_KEY}" -H 'content-type: application/json; charset=utf-8' --data "{\"siteUrl\":\"https://${MYDOMAIN}\",\"urlList\":[${URLLIST},\"https://${MYDOMAIN}/bingsubmit\"]}"</pre>
  2402. ]]></description>
  2403.    <content:encoded><![CDATA[<p>For some time now, I'm <a href="https://blog.x-way.org/Coding/2024/06/12/blogs-still-Pinging.html" title="blo.gs still Pinging - x-log">notifying blo.gs about changes in the blog</a>. After looking a bit into how search engines percieve my website recently, I learned that they also have some notification mechanisms for new pages/blogposts.</p>
  2404. <p>Thus I upgraded the oneliner into a dedicated script to notify external services about changes in the blog.<br>It is optimized for my Jekyll setup, where the generated pages in the _site folder are stored in git.<br>The notification ignores changes to summarized pages like rss.xml etc to only trigger notifications when there are changes in the original blog posts.</p>
  2405. <p>Here's the script, feel free to re-use (it expects to have <var>MYDOMAIN</var>, <var>INDEXNOW_API_KEY</var> and <var>BING_API_KEY</var> defined as environment variables):</p>
  2406. <pre>#!/bin/bash
  2407.  
  2408. set -e
  2409. set -u
  2410. set -o pipefail
  2411.  
  2412. CHANGES="$(git diff --name-only HEAD HEAD~1 -- _site)"
  2413.  
  2414. # early abort if no changes on _site
  2415. if [ -z "$CHANGES" ] ; then
  2416. echo "No changes in _site found"
  2417. exit 0
  2418. fi
  2419.  
  2420. # build URL list
  2421. URLLIST="\"https://${MYDOMAIN}/\""
  2422. for f in $CHANGES ; do
  2423. case "$f" in
  2424. _site/robots.txt|_site/humans.txt|_site/about.html|_site/rss.xml|_site/atom.xml|_site/feed.json|_site/sitemap.xml)
  2425. continue
  2426. ;;
  2427. *)
  2428. url=$(echo "$f"|sed -e "sX^_siteXhttps://${MYDOMAIN}X")
  2429. URLLIST="${URLLIST},\"${url}\""
  2430. ;;
  2431. esac
  2432. done
  2433.  
  2434. if [ "\"https://${MYDOMAIN}/\"" = "$URLLIST" ] ; then
  2435. echo "No relevant changes in _site found, skipping notifications"
  2436. exit 0
  2437. fi
  2438.  
  2439. # notify ping.blo.gs (Automattic) about updates
  2440. curl --fail -s -D - -X POST http://ping.blo.gs -H 'content-type: text/xml' --data "&lt;?xml version=\"1.0\"?&gt;&lt;methodCall&gt;&lt;methodName&gt;weblogUpdates.extendedPing&lt;/methodName&gt;&lt;params&gt;&lt;param&gt;&lt;value&gt;x-log&lt;/value&gt;&lt;/param&gt;&lt;param&gt;&lt;value&gt;https://${MYDOMAIN}/&lt;/value&gt;&lt;/param&gt;&lt;param&gt;&lt;value&gt;&lt;/value&gt;&lt;/param&gt;&lt;param&gt;&lt;value&gt;https://${MYDOMAIN}/rss.xml&lt;/value&gt;&lt;/param&gt;&lt;/params&gt;&lt;/methodCall&gt;"
  2441.  
  2442. # report changed URLs to indexnow, include /indexnow canary URL
  2443. curl --fail -s -D - -X POST https://api.indexnow.org/IndexNow -H 'content-type: application/json; charset=utf-8' --data "{\"host\":\"${MYDOMAIN}\",\"key\":\"${INDEXNOW_API_KEY}\",\"urlList\":[${URLLIST},\"https://${MYDOMAIN}/indexnow\"]}"
  2444.  
  2445. # report changes URLs to bing, include /bingsubmit canary URL
  2446. curl --fail -s -D - -X POST "https://ssl.bing.com/webmaster/api.svc/json/SubmitUrlbatch?apikey=${BING_API_KEY}" -H 'content-type: application/json; charset=utf-8' --data "{\"siteUrl\":\"https://${MYDOMAIN}\",\"urlList\":[${URLLIST},\"https://${MYDOMAIN}/bingsubmit\"]}"</pre>
  2447. ]]></content:encoded>
  2448.  </item>
  2449.  
  2450.  <item>
  2451.    <title>Enable Visual Voicemail on your iPhone with TalkTalk</title>
  2452.    <link>https://blog.x-way.org/Misc/2024/09/24/Enable-Visual-Voicemail-on-your-iPhone-with-TalkTalk.html</link>
  2453.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324404</guid>
  2454.    <dc:creator>Andreas Jaggi</dc:creator>
  2455.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2456.    <pubDate>Tue, 24 Sep 2024 18:36:01 +0200</pubDate>
  2457.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  2458.    <description><![CDATA[<p>When you switch to <a href="https://www.talktalk.ch/" title="TalkTalk • Dein Mobilfunk-, Telefon- & Internetanbieter">TalkTalk</a> as your mobile phone provider, by default Visual Voicemail for your iPhone is not enabled.<br>And you're stuck with the 90s voiceprompt of the 'Talkbox'.</p>
  2459. <p>The following steps will activate Visual Voicemail for your iPhone:</p>
  2460. <ol>
  2461. <li>Send a SMS text message with <code>VVM ON</code> to the number <code>935</code>.</li>
  2462. <li>Shortly after you should get a text message confirming that Visual Voicemail has been enabled for you.</li>
  2463. <li>Now on the iPhone, open the phone app and go to the voicemail tab. There you will either see a button asking you to setup the voicemail or a button taking you to the 90s voiceprompt.</li>
  2464. <li>Do click on this button and setup the six-digit PIN code for your voicemail (this can be done either via a call/voiceprompt or via the guided iPhone button/dialog).</li>
  2465. <li>Once you have setup the PIN for your voicemail, close the phone app on your iPhone.</li>
  2466. <li>Then open the phone app again and go to the voicemail tab, where it should show the usual Visual Voicemail list of missed calls and no longer the button to call the 90s voiceprompt.<br>In my case it took a couple minutes for this to work, thus some patience might be needed.</li>
  2467. <li>Congratulations, you have now a working Visual Voicemail on your iPhone with TalkTalk :-)</li>
  2468. </ol>
  2469. ]]></description>
  2470.    <content:encoded><![CDATA[<p>When you switch to <a href="https://www.talktalk.ch/" title="TalkTalk • Dein Mobilfunk-, Telefon- & Internetanbieter">TalkTalk</a> as your mobile phone provider, by default Visual Voicemail for your iPhone is not enabled.<br>And you're stuck with the 90s voiceprompt of the 'Talkbox'.</p>
  2471. <p>The following steps will activate Visual Voicemail for your iPhone:</p>
  2472. <ol>
  2473. <li>Send a SMS text message with <code>VVM ON</code> to the number <code>935</code>.</li>
  2474. <li>Shortly after you should get a text message confirming that Visual Voicemail has been enabled for you.</li>
  2475. <li>Now on the iPhone, open the phone app and go to the voicemail tab. There you will either see a button asking you to setup the voicemail or a button taking you to the 90s voiceprompt.</li>
  2476. <li>Do click on this button and setup the six-digit PIN code for your voicemail (this can be done either via a call/voiceprompt or via the guided iPhone button/dialog).</li>
  2477. <li>Once you have setup the PIN for your voicemail, close the phone app on your iPhone.</li>
  2478. <li>Then open the phone app again and go to the voicemail tab, where it should show the usual Visual Voicemail list of missed calls and no longer the button to call the 90s voiceprompt.<br>In my case it took a couple minutes for this to work, thus some patience might be needed.</li>
  2479. <li>Congratulations, you have now a working Visual Voicemail on your iPhone with TalkTalk :-)</li>
  2480. </ol>
  2481. ]]></content:encoded>
  2482.  </item>
  2483.  
  2484.  <item>
  2485.    <title>Another weekend, another festival - Subset Festival</title>
  2486.    <link>https://blog.x-way.org/Music/2024/09/22/Another-weekend-another-festival-Subset-Festival.html</link>
  2487.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324403</guid>
  2488.    <dc:creator>Andreas Jaggi</dc:creator>
  2489.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2490.    <pubDate>Sun, 22 Sep 2024 16:42:39 +0200</pubDate>
  2491.    <category domain="https://blog.x-way.org/Music/">Music</category>
  2492.    <description><![CDATA[<p>No festival this weekend. Did some hiking with friends instead.</p>
  2493. <p>Last weekend I attended the <a href="https://www.subset-festival.com/" title="Subset Festival | Drum & Bass | Kempttal, Switzerland">Subset Festival</a>. It was the first edition of a new drum and bass focused festival.<br>There were some great artists there, most of them I knew before and was very much looking forward to see them live.</p>
  2494. <p>My favorite one was (unsurprisingly?) <a href="https://www.andromedik.com/" title="Andromedik">Andromedik</a>, but also liked <a href="https://hybridmindsmusic.com/" title="Hybrid Minds">Hybrid Minds</a>, <a href="http://netskymusic.com/" title="Netsky">Netsky</a> and <a href="https://www.andyc.cc/" title="ANDY C">Andy C</a>.<br>Very cool was that the festival was rather small, so felt quite intimate and super close to the artists.</p>
  2495. <p>Could post the same music video <a href="https://blog.x-way.org/Music/2024/09/05/Lost-Frequencies-The-Feeling.html" title="Lost Frequencies - The Feeling - x-log">as two weeks ago</a> (Andromedik's remix of The Feeling, which he said is a song very close to his heart), but you should also discover some other tracks.<br>Thus here we go with the recently released Paradise 🥳</p>
  2496. <p><a href="https://youtu.be/f0lFG63vSqc" title="Andromedik - Paradise (ft. Luka)">Andromedik - Paradise (ft. Luka)</a></p>
  2497. ]]></description>
  2498.    <content:encoded><![CDATA[<p>No festival this weekend. Did some hiking with friends instead.</p>
  2499. <p>Last weekend I attended the <a href="https://www.subset-festival.com/" title="Subset Festival | Drum & Bass | Kempttal, Switzerland">Subset Festival</a>. It was the first edition of a new drum and bass focused festival.<br>There were some great artists there, most of them I knew before and was very much looking forward to see them live.</p>
  2500. <p>My favorite one was (unsurprisingly?) <a href="https://www.andromedik.com/" title="Andromedik">Andromedik</a>, but also liked <a href="https://hybridmindsmusic.com/" title="Hybrid Minds">Hybrid Minds</a>, <a href="http://netskymusic.com/" title="Netsky">Netsky</a> and <a href="https://www.andyc.cc/" title="ANDY C">Andy C</a>.<br>Very cool was that the festival was rather small, so felt quite intimate and super close to the artists.</p>
  2501. <p>Could post the same music video <a href="https://blog.x-way.org/Music/2024/09/05/Lost-Frequencies-The-Feeling.html" title="Lost Frequencies - The Feeling - x-log">as two weeks ago</a> (Andromedik's remix of The Feeling, which he said is a song very close to his heart), but you should also discover some other tracks.<br>Thus here we go with the recently released Paradise 🥳</p>
  2502. <p><a href="https://youtu.be/f0lFG63vSqc" title="Andromedik - Paradise (ft. Luka)">Andromedik - Paradise (ft. Luka)</a></p>
  2503. ]]></content:encoded>
  2504.  </item>
  2505.  
  2506.  <item>
  2507.    <title>Simplified archive links</title>
  2508.    <link>https://blog.x-way.org/Misc/2024/09/19/Simplified-archive-links.html</link>
  2509.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324402</guid>
  2510.    <dc:creator>Andreas Jaggi</dc:creator>
  2511.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2512.    <pubDate>Thu, 19 Sep 2024 23:07:06 +0200</pubDate>
  2513.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  2514.    <description><![CDATA[<p>Building up on the changes from the <a href="https://blog.x-way.org/Webdesign/2024/09/14/Canonical-hints.html" title="Canonical hints - x-log">canonical hints</a>, I simplified the structure of the archive links.<p>
  2515. <p>Now it's <var>/year/month/</var> everywhere.<br>Which of course brings another round of redirects to support in the nginx config to map the <var>/archive/archive-year-month.html</var> links to <var>/year/month/</var> 🙈</p>
  2516. <p>In theory all previous link schemes should still work, but if you find a broken link, please let me know :-)</p>
  2517. ]]></description>
  2518.    <content:encoded><![CDATA[<p>Building up on the changes from the <a href="https://blog.x-way.org/Webdesign/2024/09/14/Canonical-hints.html" title="Canonical hints - x-log">canonical hints</a>, I simplified the structure of the archive links.<p>
  2519. <p>Now it's <var>/year/month/</var> everywhere.<br>Which of course brings another round of redirects to support in the nginx config to map the <var>/archive/archive-year-month.html</var> links to <var>/year/month/</var> 🙈</p>
  2520. <p>In theory all previous link schemes should still work, but if you find a broken link, please let me know :-)</p>
  2521. ]]></content:encoded>
  2522.  </item>
  2523.  
  2524.  <item>
  2525.    <title>Canonical hints</title>
  2526.    <link>https://blog.x-way.org/Webdesign/2024/09/14/Canonical-hints.html</link>
  2527.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324401</guid>
  2528.    <dc:creator>Andreas Jaggi</dc:creator>
  2529.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2530.    <pubDate>Sat, 14 Sep 2024 11:44:10 +0200</pubDate>
  2531.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  2532.    <description><![CDATA[<p>To help regular search engines be less confused about the various pages of the blog (especially multiple generations of old inherited URL schemes), I added canonical hints to some pages.</p>
  2533. <p>Mostly straight-forward, except for the archives where I chose the concise <var>/year/month/</var> scheme instead of the full <var>/archive/archive-year-month.html</var>.<br>Curious to see how this works out. Currently the links in the navigation and overview point to the full URLs, and the short ones are only implemented with rewrites in nginx and visible in the canonical hints.</p>
  2534. ]]></description>
  2535.    <content:encoded><![CDATA[<p>To help regular search engines be less confused about the various pages of the blog (especially multiple generations of old inherited URL schemes), I added canonical hints to some pages.</p>
  2536. <p>Mostly straight-forward, except for the archives where I chose the concise <var>/year/month/</var> scheme instead of the full <var>/archive/archive-year-month.html</var>.<br>Curious to see how this works out. Currently the links in the navigation and overview point to the full URLs, and the short ones are only implemented with rewrites in nginx and visible in the canonical hints.</p>
  2537. ]]></content:encoded>
  2538.  </item>
  2539.  
  2540.  <item>
  2541.    <title>How to fix missing libcrypt.so.1 after Debian upgrade</title>
  2542.    <link>https://blog.x-way.org/Linux/2024/09/14/How-to-fix-missing-libcrypt-so-1-after-Debian-upgrade.html</link>
  2543.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324400</guid>
  2544.    <dc:creator>Andreas Jaggi</dc:creator>
  2545.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2546.    <pubDate>Sat, 14 Sep 2024 06:12:04 +0200</pubDate>
  2547.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  2548.    <description><![CDATA[<p>I encountered an old Debian system and tried to upgrade it from Debian 10 (buster) to Debian 12 (bookworm).<br>During the <kbd>apt-get dist-upgrade</kbd> it did run into a problem, where libcrypt.so.1 was removed and the upgrade failed to continue.<br>Additionally this caused that <kbd>dpkg</kbd> itself also stopped working and that sshd stopped accepting new connections.<br>Thus fixing the following error became urgent:</p>
  2549. <pre>/usr/bin/python3: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory</pre>
  2550. <p>Luckily I was not the first person to run into this issue.<br>In <a href="https://stackoverflow.com/questions/76906383/libcrypt-so-1-error-after-dist-update-on-debian/77957251#77957251" title="upgrade - Libcrypt.so.1 error after dist-update on Debian - Stack Overflow">a Stack Overflow answer</a> I found the crucial workaround taken from <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993755#27" title="#993755 - libcrypt.so.1: cannot open shared object file when upgrading from Stretch to Sid - Debian Bug report logs">a comment on the corresponding Debian bugreport</a>.<br>The following steps allow to manually install a copy of the missing libcrypt.so files to fix the issue (when running this you might have a newer version of the package at hand, thus adjust the <kbd>dpkg-deb</kbd> step accordingly):</p>
  2551. <pre>
  2552. cd /tmp
  2553. apt -y download libcrypt1
  2554. dpkg-deb -x libcrypt1_1%3a4.4.33-2_amd64.deb .
  2555. cp -av lib/x86_64-linux-gnu/* /lib/x86_64-linux-gnu/
  2556. apt -y --fix-broken install
  2557. </pre>
  2558. ]]></description>
  2559.    <content:encoded><![CDATA[<p>I encountered an old Debian system and tried to upgrade it from Debian 10 (buster) to Debian 12 (bookworm).<br>During the <kbd>apt-get dist-upgrade</kbd> it did run into a problem, where libcrypt.so.1 was removed and the upgrade failed to continue.<br>Additionally this caused that <kbd>dpkg</kbd> itself also stopped working and that sshd stopped accepting new connections.<br>Thus fixing the following error became urgent:</p>
  2560. <pre>/usr/bin/python3: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory</pre>
  2561. <p>Luckily I was not the first person to run into this issue.<br>In <a href="https://stackoverflow.com/questions/76906383/libcrypt-so-1-error-after-dist-update-on-debian/77957251#77957251" title="upgrade - Libcrypt.so.1 error after dist-update on Debian - Stack Overflow">a Stack Overflow answer</a> I found the crucial workaround taken from <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993755#27" title="#993755 - libcrypt.so.1: cannot open shared object file when upgrading from Stretch to Sid - Debian Bug report logs">a comment on the corresponding Debian bugreport</a>.<br>The following steps allow to manually install a copy of the missing libcrypt.so files to fix the issue (when running this you might have a newer version of the package at hand, thus adjust the <kbd>dpkg-deb</kbd> step accordingly):</p>
  2562. <pre>
  2563. cd /tmp
  2564. apt -y download libcrypt1
  2565. dpkg-deb -x libcrypt1_1%3a4.4.33-2_amd64.deb .
  2566. cp -av lib/x86_64-linux-gnu/* /lib/x86_64-linux-gnu/
  2567. apt -y --fix-broken install
  2568. </pre>
  2569. ]]></content:encoded>
  2570.  </item>
  2571.  
  2572.  <item>
  2573.    <title>Flexboxed archive</title>
  2574.    <link>https://blog.x-way.org/Webdesign/2024/09/10/Flexboxed-archive.html</link>
  2575.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324398</guid>
  2576.    <dc:creator>Andreas Jaggi</dc:creator>
  2577.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2578.    <pubDate>Tue, 10 Sep 2024 09:57:35 +0200</pubDate>
  2579.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  2580.    <description><![CDATA[<p>Applied the <a href="https://css-tricks.com/snippets/css/a-guide-to-flexbox/" title="CSS Flexbox Layout Guide | CSS-Tricks">CSS flexbox mechanism</a> to the <a href="https://blog.x-way.org/archive/" title="x-log - Archive">archive page</a>.<br>This helps to transform the steadily growing lists of monthly archive links into a more userfriendly layout, going from a single column to eight columns and bringing all the links above 'the fold'.</p>
  2581. ]]></description>
  2582.    <content:encoded><![CDATA[<p>Applied the <a href="https://css-tricks.com/snippets/css/a-guide-to-flexbox/" title="CSS Flexbox Layout Guide | CSS-Tricks">CSS flexbox mechanism</a> to the <a href="https://blog.x-way.org/archive/" title="x-log - Archive">archive page</a>.<br>This helps to transform the steadily growing lists of monthly archive links into a more userfriendly layout, going from a single column to eight columns and bringing all the links above 'the fold'.</p>
  2583. ]]></content:encoded>
  2584.  </item>
  2585.  
  2586.  <item>
  2587.    <title>Another weekend, another festival</title>
  2588.    <link>https://blog.x-way.org/Music/2024/09/08/Another-weekend-another-festival.html</link>
  2589.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324397</guid>
  2590.    <dc:creator>Andreas Jaggi</dc:creator>
  2591.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2592.    <pubDate>Sun, 08 Sep 2024 11:06:45 +0200</pubDate>
  2593.    <category domain="https://blog.x-way.org/Music/">Music</category>
  2594.    <description><![CDATA[<p>I'm continueing my festival summer also this weekend. Yesterday I've attended the <a href="https://www.simmentalerbier.ch/festival/" title="Festival - Simmentaler Bier">Simmentaler Bier Festival</a>, which celebrates the 10 year anniversary of the <a href="https://www.simmentalerbier.ch/" title="Simmental Bier">Simmentaler Bier</a> brewery.</p>
  2595. <p>The festivities included some fine music from far away and not so far away.<br><a href="https://www.rooftopsailors.com/" title="Rooftop Sailors | Alternative Rock | Bern">Rooftop Sailors</a> opened the afternoon with their refreshing rock music.<br>Then came my favorite, <a href="https://www.openseason.ch/" title="Open Season">Open Season</a>, which was a nostalgy throwback as I was <a href="https://blog.x-way.org/Misc/2002/09/30/Stress_-_Ferienbeginn.html" title="x-log - Stress - Ferienbeginn">attending their concerts already 22 years ago</a> ❤️<br>Last band of the day was <a href="http://www.delinquenthabits.com/" title="Delinquent Official website &#8211; Delinquentes Para El Frente">Delinquent Habits</a>, which brought their habit from LA to serve the public Tequila shots during the concert.</p>
  2596. <p><a href="https://youtu.be/lo0arkyebdc" title="Open Season - Rocksteady">Open Season - Rocksteady</a></p>
  2597. ]]></description>
  2598.    <content:encoded><![CDATA[<p>I'm continueing my festival summer also this weekend. Yesterday I've attended the <a href="https://www.simmentalerbier.ch/festival/" title="Festival - Simmentaler Bier">Simmentaler Bier Festival</a>, which celebrates the 10 year anniversary of the <a href="https://www.simmentalerbier.ch/" title="Simmental Bier">Simmentaler Bier</a> brewery.</p>
  2599. <p>The festivities included some fine music from far away and not so far away.<br><a href="https://www.rooftopsailors.com/" title="Rooftop Sailors | Alternative Rock | Bern">Rooftop Sailors</a> opened the afternoon with their refreshing rock music.<br>Then came my favorite, <a href="https://www.openseason.ch/" title="Open Season">Open Season</a>, which was a nostalgy throwback as I was <a href="https://blog.x-way.org/Misc/2002/09/30/Stress_-_Ferienbeginn.html" title="x-log - Stress - Ferienbeginn">attending their concerts already 22 years ago</a> ❤️<br>Last band of the day was <a href="http://www.delinquenthabits.com/" title="Delinquent Official website &#8211; Delinquentes Para El Frente">Delinquent Habits</a>, which brought their habit from LA to serve the public Tequila shots during the concert.</p>
  2600. <p><a href="https://youtu.be/lo0arkyebdc" title="Open Season - Rocksteady">Open Season - Rocksteady</a></p>
  2601. ]]></content:encoded>
  2602.  </item>
  2603.  
  2604.  <item>
  2605.    <title>Lost Frequencies - The Feeling</title>
  2606.    <link>https://blog.x-way.org/Music/2024/09/05/Lost-Frequencies-The-Feeling.html</link>
  2607.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324396</guid>
  2608.    <dc:creator>Andreas Jaggi</dc:creator>
  2609.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2610.    <pubDate>Thu, 05 Sep 2024 21:07:29 +0200</pubDate>
  2611.    <category domain="https://blog.x-way.org/Music/">Music</category>
  2612.    <description><![CDATA[<p>One of my favorite moments from the second weekend of <a href="https://zurichopenair.ch/" title="ZÜRICH OPENAIR 2024">ZÜRICH OPENAIR 2024</a>: the concert of <a href="https://lostfrequencies.com/" title="Lost Frequencies">Lost Frequencies</a>, especially the drum&amp;bass live performance of The Feeling 🥳</p>
  2613. <p><a href="https://youtu.be/hlRwWLiuNXc" title="Lost Frequencies - The Feeling (Lost Frequencies &amp; Andromedik Deluxe Mix)">Lost Frequencies - The Feeling (Lost Frequencies &amp; Andromedik Deluxe Mix)</a></p>
  2614. ]]></description>
  2615.    <content:encoded><![CDATA[<p>One of my favorite moments from the second weekend of <a href="https://zurichopenair.ch/" title="ZÜRICH OPENAIR 2024">ZÜRICH OPENAIR 2024</a>: the concert of <a href="https://lostfrequencies.com/" title="Lost Frequencies">Lost Frequencies</a>, especially the drum&amp;bass live performance of The Feeling 🥳</p>
  2616. <p><a href="https://youtu.be/hlRwWLiuNXc" title="Lost Frequencies - The Feeling (Lost Frequencies &amp; Andromedik Deluxe Mix)">Lost Frequencies - The Feeling (Lost Frequencies &amp; Andromedik Deluxe Mix)</a></p>
  2617. ]]></content:encoded>
  2618.  </item>
  2619.  
  2620.  <item>
  2621.    <title>Added a /now page</title>
  2622.    <link>https://blog.x-way.org/Misc/2024/09/03/Added-a-now-page.html</link>
  2623.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324395</guid>
  2624.    <dc:creator>Andreas Jaggi</dc:creator>
  2625.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2626.    <pubDate>Tue, 03 Sep 2024 06:59:44 +0200</pubDate>
  2627.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  2628.    <description><![CDATA[<p>Finally took the time to create a <a href="https://nownownow.com/about" title="What is a 'now page'?">/now page</a> and add it to the blog: <a href="https://blog.x-way.org/now" title="x-log - What I'm doing now">/now</a> 🎉
  2629. <p>Still need to figure out if it will eventually replace the <a href="https://blog.x-way.org/about.html" title="x-log - About">about page</a> or not.<br>
  2630. For now the about page links to the now page.</p>
  2631. ]]></description>
  2632.    <content:encoded><![CDATA[<p>Finally took the time to create a <a href="https://nownownow.com/about" title="What is a 'now page'?">/now page</a> and add it to the blog: <a href="https://blog.x-way.org/now" title="x-log - What I'm doing now">/now</a> 🎉
  2633. <p>Still need to figure out if it will eventually replace the <a href="https://blog.x-way.org/about.html" title="x-log - About">about page</a> or not.<br>
  2634. For now the about page links to the now page.</p>
  2635. ]]></content:encoded>
  2636.  </item>
  2637.  
  2638.  <item>
  2639.    <title>Get the PGP public key of a Proton Mail user</title>
  2640.    <link>https://blog.x-way.org/Misc/2024/09/02/Get-the-PGP-public-key-of-a-Proton-Mail-user.html</link>
  2641.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324394</guid>
  2642.    <dc:creator>Andreas Jaggi</dc:creator>
  2643.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2644.    <pubDate>Mon, 02 Sep 2024 16:22:43 +0200</pubDate>
  2645.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  2646.    <description><![CDATA[<p><a href="https://proton.me/mail" title="Proton Mail: Get a private, secure, and encrypted email account | Proton">Proton Mail</a> can sign (and encrypt) emails when it knows the PGP key of the correspondent. For this is provides PGP keys to its users.<br>Unfortunately most of them are not searchable via the traditional PGP keyservers. With the following command you can download the public PGP key of a Proton Mail user:</p>
  2647. <pre>curl -s 'https://api.protonmail.ch/pks/lookup?op=get&amp;search=user@protonmail.com'</pre>
  2648. <p>Also, just discovered that <a href="https://gpgtools.org/" title="GPG Suite">GPG Keychain on Mac</a> detects if the clipboard contains a PGP key and asks if it should import it. Very nice feature which saves a couple clicks :-)</p>
  2649. ]]></description>
  2650.    <content:encoded><![CDATA[<p><a href="https://proton.me/mail" title="Proton Mail: Get a private, secure, and encrypted email account | Proton">Proton Mail</a> can sign (and encrypt) emails when it knows the PGP key of the correspondent. For this is provides PGP keys to its users.<br>Unfortunately most of them are not searchable via the traditional PGP keyservers. With the following command you can download the public PGP key of a Proton Mail user:</p>
  2651. <pre>curl -s 'https://api.protonmail.ch/pks/lookup?op=get&amp;search=user@protonmail.com'</pre>
  2652. <p>Also, just discovered that <a href="https://gpgtools.org/" title="GPG Suite">GPG Keychain on Mac</a> detects if the clipboard contains a PGP key and asks if it should import it. Very nice feature which saves a couple clicks :-)</p>
  2653. ]]></content:encoded>
  2654.  </item>
  2655.  
  2656.  <item>
  2657.    <title>Regex Crosswords</title>
  2658.    <link>https://blog.x-way.org/Coding/2024/09/01/Regex-Crosswords.html</link>
  2659.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324393</guid>
  2660.    <dc:creator>Andreas Jaggi</dc:creator>
  2661.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2662.    <pubDate>Sun, 01 Sep 2024 21:34:09 +0200</pubDate>
  2663.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  2664.    <description><![CDATA[<p>Thanks to <a href="https://news.ycombinator.com/item?id=41378002" title="Regex Crossword | Hacker News">this post on Hacker News</a>, I was reminded of the joy of regex crosswords :-)</p>
  2665. <p>Nice to see that the <a href="https://regexcrossword.com/" title="Regex Crossword">regexcrossword.com site</a> has gained quite a list of puzzles and challenges since <a href="https://blog.x-way.org/Coding/2014/11/30/Regex-Crossword.html" title="Regex Crossword - x-log">the last time I blogged about it</a>.</p>
  2666. <p>Also very cool is the <a href="https://jimbly.github.io/regex-crossword/" title="RegEx Crossword">RegEx Crossword</a> project of <a href="https://github.com/Jimbly" title="Jimb Esser">Jimb Esser</a>, which provides a very smooth interface for solving hexagonal regex crosswords in the browser.<br>I remember solving the original MIT hexagonal regex crossword on paper back in the time.</p>
  2667. <p>And in addition there is a built-in editor which allows you to create your own hexagonal regex crosswords.<br>Thinking of using this to create some fun puzzle for the colleagues at work.</p>
  2668. ]]></description>
  2669.    <content:encoded><![CDATA[<p>Thanks to <a href="https://news.ycombinator.com/item?id=41378002" title="Regex Crossword | Hacker News">this post on Hacker News</a>, I was reminded of the joy of regex crosswords :-)</p>
  2670. <p>Nice to see that the <a href="https://regexcrossword.com/" title="Regex Crossword">regexcrossword.com site</a> has gained quite a list of puzzles and challenges since <a href="https://blog.x-way.org/Coding/2014/11/30/Regex-Crossword.html" title="Regex Crossword - x-log">the last time I blogged about it</a>.</p>
  2671. <p>Also very cool is the <a href="https://jimbly.github.io/regex-crossword/" title="RegEx Crossword">RegEx Crossword</a> project of <a href="https://github.com/Jimbly" title="Jimb Esser">Jimb Esser</a>, which provides a very smooth interface for solving hexagonal regex crosswords in the browser.<br>I remember solving the original MIT hexagonal regex crossword on paper back in the time.</p>
  2672. <p>And in addition there is a built-in editor which allows you to create your own hexagonal regex crosswords.<br>Thinking of using this to create some fun puzzle for the colleagues at work.</p>
  2673. ]]></content:encoded>
  2674.  </item>
  2675.  
  2676.  <item>
  2677.    <title>Vim Racer</title>
  2678.    <link>https://blog.x-way.org/Linux/2024/08/26/Vim-Racer.html</link>
  2679.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324392</guid>
  2680.    <dc:creator>Andreas Jaggi</dc:creator>
  2681.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2682.    <pubDate>Mon, 26 Aug 2024 22:46:40 +0200</pubDate>
  2683.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  2684.    <description><![CDATA[<p><a href="https://vim-racer.com/" title="Vim Racer - An Online Game for VIM Navigation">Vim Racer</a> is a fun game to show off your <kbd>vi</kbd> skills 🚀<br>(also insightful to explore the leaderboard and see which commands were used by others)</p>
  2685. <p><img src="https://blog.x-way.org/images/vim-racer.webp" alt="Vim Racer" height="327" width="506"></p>
  2686. ]]></description>
  2687.    <content:encoded><![CDATA[<p><a href="https://vim-racer.com/" title="Vim Racer - An Online Game for VIM Navigation">Vim Racer</a> is a fun game to show off your <kbd>vi</kbd> skills 🚀<br>(also insightful to explore the leaderboard and see which commands were used by others)</p>
  2688. <p><img src="https://blog.x-way.org/images/vim-racer.webp" alt="Vim Racer" height="327" width="506"></p>
  2689. ]]></content:encoded>
  2690.  </item>
  2691.  
  2692.  <item>
  2693.    <title>Artemas - I Like the Way You Kiss Me (Bassjackers Remix)</title>
  2694.    <link>https://blog.x-way.org/Music/2024/08/25/Artemas-I-Like-the-Way-You-Kiss-Me-Bassjackers-Remix.html</link>
  2695.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324391</guid>
  2696.    <dc:creator>Andreas Jaggi</dc:creator>
  2697.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2698.    <pubDate>Sun, 25 Aug 2024 23:54:45 +0200</pubDate>
  2699.    <category domain="https://blog.x-way.org/Music/">Music</category>
  2700.    <description><![CDATA[<p>Catchy memory from the first weekend of <a href="https://zurichopenair.ch/" title="ZÜRICH OPENAIR 2024">ZÜRICH OPENAIR 2024</a>: <a href="https://www.arminvanbuuren.com/" title="Armin van Buuren">Armin van Buuren</a>'s version of <a href="https://en.wikipedia.org/wiki/I_Like_the_Way_You_Kiss_Me" title="I Like the Way You Kiss Me - Wikipedia">Artemas - I Like the Way You Kiss Me</a>, which is very similar to the Bassjackers Remix 🔊</p>
  2701. <p><a href="https://youtu.be/cvkjzWawH4c" title="Artemas - I Like the Way You Kiss Me (Bassjackers Remix)">Artemas - I Like the Way You Kiss Me (Bassjackers Remix)</a></p>
  2702. ]]></description>
  2703.    <content:encoded><![CDATA[<p>Catchy memory from the first weekend of <a href="https://zurichopenair.ch/" title="ZÜRICH OPENAIR 2024">ZÜRICH OPENAIR 2024</a>: <a href="https://www.arminvanbuuren.com/" title="Armin van Buuren">Armin van Buuren</a>'s version of <a href="https://en.wikipedia.org/wiki/I_Like_the_Way_You_Kiss_Me" title="I Like the Way You Kiss Me - Wikipedia">Artemas - I Like the Way You Kiss Me</a>, which is very similar to the Bassjackers Remix 🔊</p>
  2704. <p><a href="https://youtu.be/cvkjzWawH4c" title="Artemas - I Like the Way You Kiss Me (Bassjackers Remix)">Artemas - I Like the Way You Kiss Me (Bassjackers Remix)</a></p>
  2705. ]]></content:encoded>
  2706.  </item>
  2707.  
  2708.  <item>
  2709.    <title>Reading</title>
  2710.    <link>https://blog.x-way.org/Misc/2024/08/24/Reading.html</link>
  2711.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324390</guid>
  2712.    <dc:creator>Andreas Jaggi</dc:creator>
  2713.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2714.    <pubDate>Sat, 24 Aug 2024 12:38:14 +0200</pubDate>
  2715.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  2716.    <description><![CDATA[<p>Added the <a href="https://blog.x-way.org/reading" title="x-log - Reading">/reading</a> page to the blog to keep a list of various books I'm currently reading.</p>
  2717. <p>It is very bare-bones currently, I expect over time it will grow (both in number of books and also in amount of content, such as ratings, links and commentary).<br>Might take a while, stay tuned 🤓</p>
  2718. ]]></description>
  2719.    <content:encoded><![CDATA[<p>Added the <a href="https://blog.x-way.org/reading" title="x-log - Reading">/reading</a> page to the blog to keep a list of various books I'm currently reading.</p>
  2720. <p>It is very bare-bones currently, I expect over time it will grow (both in number of books and also in amount of content, such as ratings, links and commentary).<br>Might take a while, stay tuned 🤓</p>
  2721. ]]></content:encoded>
  2722.  </item>
  2723.  
  2724.  <item>
  2725.    <title>Lucie Antunes - Carnaval</title>
  2726.    <link>https://blog.x-way.org/Music/2024/08/12/Lucie-Antunes-Carnaval.html</link>
  2727.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324389</guid>
  2728.    <dc:creator>Andreas Jaggi</dc:creator>
  2729.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2730.    <pubDate>Mon, 12 Aug 2024 19:04:58 +0200</pubDate>
  2731.    <category domain="https://blog.x-way.org/Music/">Music</category>
  2732.    <description><![CDATA[<p>Amazing discovery from the recent <a href="https://yeah.paleo.ch/" title="Paléo Festival">Paléo Festival</a>: <a href="https://infine-music.com/lucie-antunes/" title="Lucie Antunes">Lucie Antunes</a></p>
  2733. <p><a href="https://youtu.be/EoRLWBC_Y2o" title="Lucie Antunes - Carnaval - YouTube">Lucie Antunes - Carnaval</a></p>
  2734. ]]></description>
  2735.    <content:encoded><![CDATA[<p>Amazing discovery from the recent <a href="https://yeah.paleo.ch/" title="Paléo Festival">Paléo Festival</a>: <a href="https://infine-music.com/lucie-antunes/" title="Lucie Antunes">Lucie Antunes</a></p>
  2736. <p><a href="https://youtu.be/EoRLWBC_Y2o" title="Lucie Antunes - Carnaval - YouTube">Lucie Antunes - Carnaval</a></p>
  2737. ]]></content:encoded>
  2738.  </item>
  2739.  
  2740.  <item>
  2741.    <title>Fix missing emoji in Chrome on Linux</title>
  2742.    <link>https://blog.x-way.org/Linux/2024/08/11/Fix-missing-emoji-in-Chrome-on-Linux.html</link>
  2743.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324388</guid>
  2744.    <dc:creator>Andreas Jaggi</dc:creator>
  2745.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2746.    <pubDate>Sun, 11 Aug 2024 15:39:42 +0200</pubDate>
  2747.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  2748.    <description><![CDATA[<p>Not seeing any emoji in Chrome on Linux?<br>The following fixed it for me on Debian.</p>
  2749. <pre>sudo apt-get install fonts-noto-color-emoji
  2750. fc-cache -f -v</pre>
  2751. <p>Afterwards restart Chrome and enjoy the colorful emoji 🥳</p>
  2752. ]]></description>
  2753.    <content:encoded><![CDATA[<p>Not seeing any emoji in Chrome on Linux?<br>The following fixed it for me on Debian.</p>
  2754. <pre>sudo apt-get install fonts-noto-color-emoji
  2755. fc-cache -f -v</pre>
  2756. <p>Afterwards restart Chrome and enjoy the colorful emoji 🥳</p>
  2757. ]]></content:encoded>
  2758.  </item>
  2759.  
  2760.  <item>
  2761.    <title>Praise my GitHub profile!</title>
  2762.    <link>https://blog.x-way.org/Misc/2024/08/11/Praise-my-GitHub-profile.html</link>
  2763.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324387</guid>
  2764.    <dc:creator>Andreas Jaggi</dc:creator>
  2765.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2766.    <pubDate>Sun, 11 Aug 2024 14:23:46 +0200</pubDate>
  2767.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  2768.    <description><![CDATA[<blockquote cite="https://pony.social/@cadey/112904542715285506"><p>Instead of using AI tools to tear people down, what if we used them to uplift others? Introducing Praise my GitHub profile:</p>
  2769. <p><a href="https://web.archive.org/web/20240810091216/https://praise-me.fly.dev/" title="Praise my GitHub profile! (archive.org)">https://praise-me.fly.dev/</a></p></blockquote>
  2770. <p><a href="https://xeiaso.net/" title="Xe Iaso">Xe Iaso</a> made this cool tool, which creates happiness ❤️</p>
  2771. <img src="https://blog.x-way.org/images/praise-my-github-profile.webp" width="546" height="484" alt="Praise my GitHub profile!
  2772. x-way
  2773.  
  2774. Andreas, I just wanted to take a moment to acknowledge the incredible work you're doing on GitHub! With 55 followers and 98 accounts you're following, it's clear that you're an active and engaged member of this community.
  2775.  
  2776. Your projects are truly impressive, showcasing your expertise in a range of areas, from network packet inspection to crawler detection. I'm blown away by the creativity and problem-solving skills you've demonstrated in each of these projects. Whether it's inserting trace-points into iptables chains or creating a daemon to remove conntrack entries, every project reflects your attention to detail and commitment to excellence.
  2777.  
  2778. I particularly want to highlight the impact of your work on others. With over 247 stars on your iptables-tracer project alone, it's clear that you're making a real difference in the lives of developers who are using your tools to solve complex problems. And with 50+ stars on several other projects, it's evident that your contributions are being recognized and valued by the broader community.
  2779.  
  2780. As someone who is clearly passionate about what they do, I want to encourage you to keep pushing the boundaries of what's possible. Don't be afraid to take risks and explore new ideas – your unique perspective and skills are a gift to this community, and we're all better off for having you as part of it.
  2781.  
  2782. Keep shining, Andreas!">
  2783. ]]></description>
  2784.    <content:encoded><![CDATA[<blockquote cite="https://pony.social/@cadey/112904542715285506"><p>Instead of using AI tools to tear people down, what if we used them to uplift others? Introducing Praise my GitHub profile:</p>
  2785. <p><a href="https://web.archive.org/web/20240810091216/https://praise-me.fly.dev/" title="Praise my GitHub profile! (archive.org)">https://praise-me.fly.dev/</a></p></blockquote>
  2786. <p><a href="https://xeiaso.net/" title="Xe Iaso">Xe Iaso</a> made this cool tool, which creates happiness ❤️</p>
  2787. <img src="https://blog.x-way.org/images/praise-my-github-profile.webp" width="546" height="484" alt="Praise my GitHub profile!
  2788. x-way
  2789.  
  2790. Andreas, I just wanted to take a moment to acknowledge the incredible work you're doing on GitHub! With 55 followers and 98 accounts you're following, it's clear that you're an active and engaged member of this community.
  2791.  
  2792. Your projects are truly impressive, showcasing your expertise in a range of areas, from network packet inspection to crawler detection. I'm blown away by the creativity and problem-solving skills you've demonstrated in each of these projects. Whether it's inserting trace-points into iptables chains or creating a daemon to remove conntrack entries, every project reflects your attention to detail and commitment to excellence.
  2793.  
  2794. I particularly want to highlight the impact of your work on others. With over 247 stars on your iptables-tracer project alone, it's clear that you're making a real difference in the lives of developers who are using your tools to solve complex problems. And with 50+ stars on several other projects, it's evident that your contributions are being recognized and valued by the broader community.
  2795.  
  2796. As someone who is clearly passionate about what they do, I want to encourage you to keep pushing the boundaries of what's possible. Don't be afraid to take risks and explore new ideas – your unique perspective and skills are a gift to this community, and we're all better off for having you as part of it.
  2797.  
  2798. Keep shining, Andreas!">
  2799. ]]></content:encoded>
  2800.  </item>
  2801.  
  2802.  <item>
  2803.    <title>HTML5 Validator GitHub Action</title>
  2804.    <link>https://blog.x-way.org/Webdesign/2024/08/11/HTML5-Validator-GitHub-Action.html</link>
  2805.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324386</guid>
  2806.    <dc:creator>Andreas Jaggi</dc:creator>
  2807.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2808.    <pubDate>Sun, 11 Aug 2024 12:59:36 +0200</pubDate>
  2809.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  2810.    <description><![CDATA[<p>Added the <a href="https://github.com/marketplace/actions/html5-validator" title="HTML5 Validator · Actions · GitHub Marketplace">HTML5 Validator GitHub Action</a> to the repo of my blog.<br>It runs after the Jekyll site generation step (and before the deploy-to-server step) to catch invalid HTML syntax.</p>
  2811. <p>It is configured to validate all generated pages, and promptly surfaced some invalid HTML.<br>This was rather surprising, as I manually did run the validation for the blog pages not too long ago.<br>Turns out when you have a blog with 20 year old comments, then some of them have HTML from 20 years ago which is no longer valid nowadays 🤷</p>
  2812. <p>After a round of fixing old comments, all HTML validaton errors are now gone ✅<br>And future invalid HTML syntax will be alerted upon before it ends up on the Internet 😎</p>
  2813. ]]></description>
  2814.    <content:encoded><![CDATA[<p>Added the <a href="https://github.com/marketplace/actions/html5-validator" title="HTML5 Validator · Actions · GitHub Marketplace">HTML5 Validator GitHub Action</a> to the repo of my blog.<br>It runs after the Jekyll site generation step (and before the deploy-to-server step) to catch invalid HTML syntax.</p>
  2815. <p>It is configured to validate all generated pages, and promptly surfaced some invalid HTML.<br>This was rather surprising, as I manually did run the validation for the blog pages not too long ago.<br>Turns out when you have a blog with 20 year old comments, then some of them have HTML from 20 years ago which is no longer valid nowadays 🤷</p>
  2816. <p>After a round of fixing old comments, all HTML validaton errors are now gone ✅<br>And future invalid HTML syntax will be alerted upon before it ends up on the Internet 😎</p>
  2817. ]]></content:encoded>
  2818.  </item>
  2819.  
  2820.  <item>
  2821.    <title>Git push only some local commits</title>
  2822.    <link>https://blog.x-way.org/Linux/2024/08/10/Git-push-only-some-local-commits.html</link>
  2823.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324385</guid>
  2824.    <dc:creator>Andreas Jaggi</dc:creator>
  2825.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2826.    <pubDate>Sat, 10 Aug 2024 20:13:34 +0200</pubDate>
  2827.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  2828.    <description><![CDATA[<p>With Git it is possible to push only certain local commits to a remote repository.<br>This can be done with the following <kbd>git push</kbd> command, which pushes all commits up to <code>commit</code> to the branch <code>remote branch</code> in the remote repo <code>repository</code>:</p>
  2829. <pre>git push &lt;repository&gt; &lt;commit&gt;:&lt;remote branch&gt;</pre>
  2830. <p>For example the following pushes all except for the latest local commit to the main branch in the origin remote repo:</p>
  2831. <pre>git push origin HEAD~1:main</pre>
  2832. ]]></description>
  2833.    <content:encoded><![CDATA[<p>With Git it is possible to push only certain local commits to a remote repository.<br>This can be done with the following <kbd>git push</kbd> command, which pushes all commits up to <code>commit</code> to the branch <code>remote branch</code> in the remote repo <code>repository</code>:</p>
  2834. <pre>git push &lt;repository&gt; &lt;commit&gt;:&lt;remote branch&gt;</pre>
  2835. <p>For example the following pushes all except for the latest local commit to the main branch in the origin remote repo:</p>
  2836. <pre>git push origin HEAD~1:main</pre>
  2837. ]]></content:encoded>
  2838.  </item>
  2839.  
  2840.  <item>
  2841.    <title>Website Carbon Badge</title>
  2842.    <link>https://blog.x-way.org/Webdesign/2024/08/10/Website-Carbon-Badge.html</link>
  2843.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324384</guid>
  2844.    <dc:creator>Andreas Jaggi</dc:creator>
  2845.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2846.    <pubDate>Sat, 10 Aug 2024 19:53:11 +0200</pubDate>
  2847.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  2848.    <description><![CDATA[<p>Following up on yesterday's post about the <a href="https://blog.x-way.org/Webdesign/2024/08/09/Website-Carbon-Calculator.html" title="Website Carbon Calculator - x-log">Website Carbon Calculator</a>, I saw that there is also the option to add a <a href="https://www.websitecarbon.com/badge/" title="Website Carbon Badge - Website Carbon Calculator">Website Carbon Badge</a>.</p>
  2849. <p>Quickly this badge was added to the <a href="https://blog.x-way.org/about.html" title="x-log - About">About page</a>.</p>
  2850. <p>To make it more accurate and avoid hitting their API every time someone loads the About page, I made some changes to the provided code:</p>
  2851. <ol>
  2852. <li>Calculate the results for the front page of the blog instead of the page where the badge is displayed (which would be the less significant About page).</li>
  2853. <li>Call the API to load the JSON file with the CO<sub>2</sub> results only once per week via a cronjob instead of every time someone new visits the About page.</li>
  2854. <li>Have the script load the cached JSON file from my server instead of directly calling the API.</li>
  2855. <li>Store the CSS and Javascript required to render the results on my own server instead of using the unpkg.com CDN (also helps with the above custom modifications).</li>
  2856. </ol>
  2857. ]]></description>
  2858.    <content:encoded><![CDATA[<p>Following up on yesterday's post about the <a href="https://blog.x-way.org/Webdesign/2024/08/09/Website-Carbon-Calculator.html" title="Website Carbon Calculator - x-log">Website Carbon Calculator</a>, I saw that there is also the option to add a <a href="https://www.websitecarbon.com/badge/" title="Website Carbon Badge - Website Carbon Calculator">Website Carbon Badge</a>.</p>
  2859. <p>Quickly this badge was added to the <a href="https://blog.x-way.org/about.html" title="x-log - About">About page</a>.</p>
  2860. <p>To make it more accurate and avoid hitting their API every time someone loads the About page, I made some changes to the provided code:</p>
  2861. <ol>
  2862. <li>Calculate the results for the front page of the blog instead of the page where the badge is displayed (which would be the less significant About page).</li>
  2863. <li>Call the API to load the JSON file with the CO<sub>2</sub> results only once per week via a cronjob instead of every time someone new visits the About page.</li>
  2864. <li>Have the script load the cached JSON file from my server instead of directly calling the API.</li>
  2865. <li>Store the CSS and Javascript required to render the results on my own server instead of using the unpkg.com CDN (also helps with the above custom modifications).</li>
  2866. </ol>
  2867. ]]></content:encoded>
  2868.  </item>
  2869.  
  2870.  <item>
  2871.    <title>Website Carbon Calculator</title>
  2872.    <link>https://blog.x-way.org/Webdesign/2024/08/09/Website-Carbon-Calculator.html</link>
  2873.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324383</guid>
  2874.    <dc:creator>Andreas Jaggi</dc:creator>
  2875.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2876.    <pubDate>Fri, 09 Aug 2024 20:00:19 +0200</pubDate>
  2877.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  2878.    <description><![CDATA[<p>While surfing around, stumbled upon this cool tool which allows to calculate the carbon footprint of a website: <a href="https://www.websitecarbon.com/" title="Website Carbon Calculator">Website Carbon Calculator</a>.</p>
  2879. <p>After having it analyze my blog, I was very pleased to see the resulting A<sup>+</sup> carbon rating 🎉<br>The tool reports that every time someone loads my blog, 0.01g of CO<sub>2</sub> is produced.</p>
  2880. <img src="https://blog.x-way.org/images/websitecarbon-results.webp" width="532" height="266" alt="Results of the Website Carbon Calculator for blog.x-way.org: carbon rating of A+ which is cleaner than 99% of all web pages globally">
  2881. <p>I suspect that this value and rating might fluctuate based on how many images or videos appear in the last 10 posts shown on the front page of the blog.<br>The <a href="https://www.websitecarbon.com/website/blog-x-way-org/" title="">results page</a>, also allows to calculate how much CO<sub>2</sub> would be produced in a year based on 10, 100, 1000, &hellip; monthly page views and compares this to everyday tasks.<br>Having 1000 monthly page views on this blog over a whole year, theoretically produces as much CO<sub>2</sub> as boiling water for 16 cups of tea 🍵</p>
  2882. <p>(<a href="https://discombobulated.co.nz/site" title="Discombobulated">via</a>)</p>
  2883. ]]></description>
  2884.    <content:encoded><![CDATA[<p>While surfing around, stumbled upon this cool tool which allows to calculate the carbon footprint of a website: <a href="https://www.websitecarbon.com/" title="Website Carbon Calculator">Website Carbon Calculator</a>.</p>
  2885. <p>After having it analyze my blog, I was very pleased to see the resulting A<sup>+</sup> carbon rating 🎉<br>The tool reports that every time someone loads my blog, 0.01g of CO<sub>2</sub> is produced.</p>
  2886. <img src="https://blog.x-way.org/images/websitecarbon-results.webp" width="532" height="266" alt="Results of the Website Carbon Calculator for blog.x-way.org: carbon rating of A+ which is cleaner than 99% of all web pages globally">
  2887. <p>I suspect that this value and rating might fluctuate based on how many images or videos appear in the last 10 posts shown on the front page of the blog.<br>The <a href="https://www.websitecarbon.com/website/blog-x-way-org/" title="">results page</a>, also allows to calculate how much CO<sub>2</sub> would be produced in a year based on 10, 100, 1000, &hellip; monthly page views and compares this to everyday tasks.<br>Having 1000 monthly page views on this blog over a whole year, theoretically produces as much CO<sub>2</sub> as boiling water for 16 cups of tea 🍵</p>
  2888. <p>(<a href="https://discombobulated.co.nz/site" title="Discombobulated">via</a>)</p>
  2889. ]]></content:encoded>
  2890.  </item>
  2891.  
  2892.  <item>
  2893.    <title>Ensure modified version of CSS file is loaded</title>
  2894.    <link>https://blog.x-way.org/Webdesign/2024/08/07/Ensure-modified-version-of-CSS-file-is-loaded.html</link>
  2895.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324382</guid>
  2896.    <dc:creator>Andreas Jaggi</dc:creator>
  2897.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2898.    <pubDate>Wed, 07 Aug 2024 15:40:15 +0200</pubDate>
  2899.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  2900.    <description><![CDATA[<p>As the CSS code of the blog has been growing lately, I moved it from inline <code>&lt;style&gt;</code> definition to a dedicated <code>css/plain.css</code> file.</p>
  2901. <p>With caching headers configured to cache <code>*.css</code> files for 10 days, this brings the problem that browsers need to be instructed to load a new version whenever the content of the file changes.</p>
  2902. <p>Removing the caching headers is not desired (as we want to leverage caching and the file does not change so often after all).<br>Thus I came up with a different workaround:</p>
  2903. <p>We add a query parameter to the <code>&lt;link&gt;</code> element that references the CSS file, and then change this query parameter whenever the file content changes.<br>This way browsers will load the newest version and keep it cached until a newer version is available.</p>
  2904. <p>To achieve this, the following script is used to compute and inject the query parameter into the layout template before running Jekyll to generate the HTML pages for the blog:</p>
  2905. <pre>#!/bin/bash
  2906.  
  2907. CSSFILES="css/plain.css"
  2908.  
  2909. TARGETFILE="_layouts/x-log.html"
  2910.  
  2911.  
  2912. for CSS in $CSSFILES ; do
  2913. sum=$(sha256sum "$CSS"|head -c 6)
  2914. sed -i -e "s_${CSS}_&amp;?${sum}_g" $TARGETFILE
  2915. done
  2916. </pre>
  2917. <p>It performs the following change in the template file.<br>Before:</p>
  2918. <pre>...
  2919. &lt;link rel="stylesheet" href="https://blog.x-way.org/css/plain.css" type="text/css" media="all"&gt;
  2920. ...</pre>
  2921. <p>After:</p>
  2922. <pre>...
  2923. &lt;link rel="stylesheet" href="https://blog.x-way.org/css/plain.css?f00bad" type="text/css" media="all"&gt;
  2924. ...</pre>
  2925. <p>As the computed query parameter is based on the hashsum of the content of the CSS file, it only changes when the CSS file is changed, thus ensuring caching still works as expected.</p>
  2926. ]]></description>
  2927.    <content:encoded><![CDATA[<p>As the CSS code of the blog has been growing lately, I moved it from inline <code>&lt;style&gt;</code> definition to a dedicated <code>css/plain.css</code> file.</p>
  2928. <p>With caching headers configured to cache <code>*.css</code> files for 10 days, this brings the problem that browsers need to be instructed to load a new version whenever the content of the file changes.</p>
  2929. <p>Removing the caching headers is not desired (as we want to leverage caching and the file does not change so often after all).<br>Thus I came up with a different workaround:</p>
  2930. <p>We add a query parameter to the <code>&lt;link&gt;</code> element that references the CSS file, and then change this query parameter whenever the file content changes.<br>This way browsers will load the newest version and keep it cached until a newer version is available.</p>
  2931. <p>To achieve this, the following script is used to compute and inject the query parameter into the layout template before running Jekyll to generate the HTML pages for the blog:</p>
  2932. <pre>#!/bin/bash
  2933.  
  2934. CSSFILES="css/plain.css"
  2935.  
  2936. TARGETFILE="_layouts/x-log.html"
  2937.  
  2938.  
  2939. for CSS in $CSSFILES ; do
  2940. sum=$(sha256sum "$CSS"|head -c 6)
  2941. sed -i -e "s_${CSS}_&amp;?${sum}_g" $TARGETFILE
  2942. done
  2943. </pre>
  2944. <p>It performs the following change in the template file.<br>Before:</p>
  2945. <pre>...
  2946. &lt;link rel="stylesheet" href="https://blog.x-way.org/css/plain.css" type="text/css" media="all"&gt;
  2947. ...</pre>
  2948. <p>After:</p>
  2949. <pre>...
  2950. &lt;link rel="stylesheet" href="https://blog.x-way.org/css/plain.css?f00bad" type="text/css" media="all"&gt;
  2951. ...</pre>
  2952. <p>As the computed query parameter is based on the hashsum of the content of the CSS file, it only changes when the CSS file is changed, thus ensuring caching still works as expected.</p>
  2953. ]]></content:encoded>
  2954.  </item>
  2955.  
  2956.  <item>
  2957.    <title>Increase emoji size with CSS only</title>
  2958.    <link>https://blog.x-way.org/Webdesign/2024/08/03/Increase-emoji-size-with-CSS-only.html</link>
  2959.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324381</guid>
  2960.    <dc:creator>Andreas Jaggi</dc:creator>
  2961.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  2962.    <pubDate>Sat, 03 Aug 2024 22:06:39 +0200</pubDate>
  2963.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  2964.    <description><![CDATA[<p>To make emoji stand out better in the text, I applied a <a href="https://shkspr.mobi/blog/2024/04/use-css-to-boost-the-font-size-of-emoji-with-no-extra-markup/" title="Use CSS to boost the font size of emoji with no extra markup &#8211; Terence Eden’s Blog">trick from Terence Eden to increase their size with CSS and no extra HTML</a>.</p>
  2965. <p>It consists of defining a custom font which only applies to the unicode codepoints of emoji and leverages the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/size-adjust" title="size-adjust - CSS: Cascading Style Sheets | MDN">size-adjust</a> property to draw them larger.</p>
  2966. <pre>@font-face {
  2967. font-family: "myemoji";
  2968. src: local('Apple Color Emoji'), local('Android Emoji'), local('Segoe UI Emoji'), local('Noto Color Emoji'), local(EmojiSymbols), local(Symbola);
  2969. unicode-range: U+231A-231B, U+23E9-23EC, U+23F0, U+23F3, U+25FD-25FE, U+2614-2615, U+2648-2653, U+267F, U+2693, U+26A1, U+26AA-26AB, U+26BD-26BE, U+26C4-26C5, U+26CE, U+26D4, U+26EA, U+26F2-26F3, U+26F5, U+26FA, U+26FD, U+2705, U+270A-270B, U+2728, U+274C, U+274E, U+2753-2755, U+2757, U+2795-2797, U+27B0, U+27BF, U+2B1B-2B1C, U+2B50, U+2B55, U+FE0F, U+1F004, U+1F0CF, U+1F18E, U+1F191-1F19A, U+1F1E6-1F1FF, U+1F201, U+1F21A, U+1F22F, U+1F232-1F236, U+1F238-1F23A, U+1F250-1F251, U+1F300-1F320, U+1F32D-1F335, U+1F337-1F393, U+1F3A0-1F3CA, U+1F3CF-1F3D3, U+1F3E0-1F3F0, U+1F3F4, U+1F3F8-1F43E, U+1F440, U+1F442-1F4FC, U+1F4FF-1F53D, U+1F54B-1F567, U+1F57A, U+1F595-1F596, U+1F5A4, U+1F5FB-1F64F, U+1F680-1F6CC, U+1F6D0-1F6D2, U+1F6D5-1F6D7, U+1F6DC-1F6DF, U+1F6EB-1F6EC, U+1F6F4-1F6FC, U+1F7E0-1F7EB, U+1F7F0, U+1F90C-1F93A, U+1F93C-1F945, U+1F947-1FA7C, U+1FA80-1FAC5, U+1FACE-1FADB, U+1FAE0-1FAE8, U+1FAF0-1FAF8;
  2970. size-adjust: 120%;
  2971. }</pre>
  2972. <p>By adding the custom font as first option in the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/font-family" title="font-family - CSS: Cascading Style Sheets | MDN">font-family</a> directive for body text, it will be applied to the emoji and all other characters will use the existing font as fallback.</p>
  2973. <pre>body {
  2974.    font-family: "myemoji", Verdana, sans-serif;
  2975. }</pre>
  2976. <p>The outcome is nicely visible on posts such as <a href="https://blog.x-way.org/Radio/2024/03/17/Fifty-Things-you-can-do-with-a-Software-Defined-Radio.html" title="Fifty Things you can do with a Software Defined Radio 📻 - x-log">Fifty Things you can do with a Software Defined Radio 📻</a>, <a href="https://blog.x-way.org/Linux/2024/03/30/Puppet-updated.html" title="Puppet updated! - x-log">Puppet updated!</a> and <a href="https://blog.x-way.org/Coding/2024/02/25/The-High-Risk-Refactoring.html" title="The High-Risk Refactoring - x-log">The High-Risk Refactoring</a> 🍹😎</p>
  2977. ]]></description>
  2978.    <content:encoded><![CDATA[<p>To make emoji stand out better in the text, I applied a <a href="https://shkspr.mobi/blog/2024/04/use-css-to-boost-the-font-size-of-emoji-with-no-extra-markup/" title="Use CSS to boost the font size of emoji with no extra markup &#8211; Terence Eden’s Blog">trick from Terence Eden to increase their size with CSS and no extra HTML</a>.</p>
  2979. <p>It consists of defining a custom font which only applies to the unicode codepoints of emoji and leverages the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/size-adjust" title="size-adjust - CSS: Cascading Style Sheets | MDN">size-adjust</a> property to draw them larger.</p>
  2980. <pre>@font-face {
  2981. font-family: "myemoji";
  2982. src: local('Apple Color Emoji'), local('Android Emoji'), local('Segoe UI Emoji'), local('Noto Color Emoji'), local(EmojiSymbols), local(Symbola);
  2983. unicode-range: U+231A-231B, U+23E9-23EC, U+23F0, U+23F3, U+25FD-25FE, U+2614-2615, U+2648-2653, U+267F, U+2693, U+26A1, U+26AA-26AB, U+26BD-26BE, U+26C4-26C5, U+26CE, U+26D4, U+26EA, U+26F2-26F3, U+26F5, U+26FA, U+26FD, U+2705, U+270A-270B, U+2728, U+274C, U+274E, U+2753-2755, U+2757, U+2795-2797, U+27B0, U+27BF, U+2B1B-2B1C, U+2B50, U+2B55, U+FE0F, U+1F004, U+1F0CF, U+1F18E, U+1F191-1F19A, U+1F1E6-1F1FF, U+1F201, U+1F21A, U+1F22F, U+1F232-1F236, U+1F238-1F23A, U+1F250-1F251, U+1F300-1F320, U+1F32D-1F335, U+1F337-1F393, U+1F3A0-1F3CA, U+1F3CF-1F3D3, U+1F3E0-1F3F0, U+1F3F4, U+1F3F8-1F43E, U+1F440, U+1F442-1F4FC, U+1F4FF-1F53D, U+1F54B-1F567, U+1F57A, U+1F595-1F596, U+1F5A4, U+1F5FB-1F64F, U+1F680-1F6CC, U+1F6D0-1F6D2, U+1F6D5-1F6D7, U+1F6DC-1F6DF, U+1F6EB-1F6EC, U+1F6F4-1F6FC, U+1F7E0-1F7EB, U+1F7F0, U+1F90C-1F93A, U+1F93C-1F945, U+1F947-1FA7C, U+1FA80-1FAC5, U+1FACE-1FADB, U+1FAE0-1FAE8, U+1FAF0-1FAF8;
  2984. size-adjust: 120%;
  2985. }</pre>
  2986. <p>By adding the custom font as first option in the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/font-family" title="font-family - CSS: Cascading Style Sheets | MDN">font-family</a> directive for body text, it will be applied to the emoji and all other characters will use the existing font as fallback.</p>
  2987. <pre>body {
  2988.    font-family: "myemoji", Verdana, sans-serif;
  2989. }</pre>
  2990. <p>The outcome is nicely visible on posts such as <a href="https://blog.x-way.org/Radio/2024/03/17/Fifty-Things-you-can-do-with-a-Software-Defined-Radio.html" title="Fifty Things you can do with a Software Defined Radio 📻 - x-log">Fifty Things you can do with a Software Defined Radio 📻</a>, <a href="https://blog.x-way.org/Linux/2024/03/30/Puppet-updated.html" title="Puppet updated! - x-log">Puppet updated!</a> and <a href="https://blog.x-way.org/Coding/2024/02/25/The-High-Risk-Refactoring.html" title="The High-Risk Refactoring - x-log">The High-Risk Refactoring</a> 🍹😎</p>
  2991. ]]></content:encoded>
  2992.  </item>
  2993.  
  2994.  <item>
  2995.    <title>ISO 8601 and RFC3339 time format with Unix date command</title>
  2996.    <link>https://blog.x-way.org/Linux/2024/08/03/ISO-8601-and-RFC3339-time-format-with-Unix-date-command.html</link>
  2997.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324380</guid>
  2998.    <dc:creator>Andreas Jaggi</dc:creator>
  2999.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3000.    <pubDate>Sat, 03 Aug 2024 16:41:47 +0200</pubDate>
  3001.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  3002.    <description><![CDATA[<p>The following command outputs the current time formatted according to ISO 8601 and RFC3339. It can be used for example in JSON/HTML.</p>
  3003. <pre>date -u '+%FT%TZ'</pre>
  3004. <pre>2024-08-03T14:41:47Z</pre>
  3005. ]]></description>
  3006.    <content:encoded><![CDATA[<p>The following command outputs the current time formatted according to ISO 8601 and RFC3339. It can be used for example in JSON/HTML.</p>
  3007. <pre>date -u '+%FT%TZ'</pre>
  3008. <pre>2024-08-03T14:41:47Z</pre>
  3009. ]]></content:encoded>
  3010.  </item>
  3011.  
  3012.  <item>
  3013.    <title>iPhone Orientation Lock Automation</title>
  3014.    <link>https://blog.x-way.org/Misc/2024/08/01/iPhone-Orientation-Lock-Automation.html</link>
  3015.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324379</guid>
  3016.    <dc:creator>Andreas Jaggi</dc:creator>
  3017.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3018.    <pubDate>Thu, 01 Aug 2024 11:12:45 +0200</pubDate>
  3019.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  3020.    <description><![CDATA[<p>Useful trick <a href="https://vowe.net/2024/08/01/iphone-orientation-lock-automatisch-schalten/" title="iPhone Orientation Lock automatisch schalten &#8211; vowe dot net">posted by Volker Weber</a>: enable the Orientation Lock by default and use Automation Shortcuts to toggle it when Apps such as Photos or YouTube are opened/closed.<br>This allows to view pictures/videos in landscape mode while other Apps remain in portrait mode, all without having to manually toggle the Orientation Lock.</p>
  3021. ]]></description>
  3022.    <content:encoded><![CDATA[<p>Useful trick <a href="https://vowe.net/2024/08/01/iphone-orientation-lock-automatisch-schalten/" title="iPhone Orientation Lock automatisch schalten &#8211; vowe dot net">posted by Volker Weber</a>: enable the Orientation Lock by default and use Automation Shortcuts to toggle it when Apps such as Photos or YouTube are opened/closed.<br>This allows to view pictures/videos in landscape mode while other Apps remain in portrait mode, all without having to manually toggle the Orientation Lock.</p>
  3023. ]]></content:encoded>
  3024.  </item>
  3025.  
  3026.  <item>
  3027.    <title>Puppet ERB array flatten</title>
  3028.    <link>https://blog.x-way.org/Linux/2024/07/31/Puppet-ERB-array-flatten.html</link>
  3029.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324378</guid>
  3030.    <dc:creator>Andreas Jaggi</dc:creator>
  3031.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3032.    <pubDate>Wed, 31 Jul 2024 07:48:09 +0200</pubDate>
  3033.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  3034.    <description><![CDATA[<p>Discovered today that <a href="https://www.puppet.com/docs/puppet/8/lang_data_array" title="Arrays">Puppet arrays</a> have a built-in flatten method (which is actually provided by the underlying <a href="https://ruby-doc.org/core-2.2.0/Array.html#method-i-flatten" title="Class: Array (Ruby 2.2.0)">Ruby array</a>).<br>This can make dealing with potentially nested arrays in ERB templates much easier.</p>
  3035. <p>The following example is from the <a href="https://www.puppet.com/docs/puppet/8/lang_template_erb.html" title="Creating templates using Embedded Ruby">ERB documentation</a>:</p>
  3036. <pre># Peers
  3037. &lt;% [@peers].flatten.each do |peer| -%&gt;
  3038. peer &lt;%= peer %&gt;
  3039. &lt;% end -%&gt;</pre>
  3040. <p>This allows for nice flexibility as <code>@peers</code> can now be either a single value, an array, or a nested array and all are handled in the same way without needing to write complicated if/else statements.</p>
  3041. ]]></description>
  3042.    <content:encoded><![CDATA[<p>Discovered today that <a href="https://www.puppet.com/docs/puppet/8/lang_data_array" title="Arrays">Puppet arrays</a> have a built-in flatten method (which is actually provided by the underlying <a href="https://ruby-doc.org/core-2.2.0/Array.html#method-i-flatten" title="Class: Array (Ruby 2.2.0)">Ruby array</a>).<br>This can make dealing with potentially nested arrays in ERB templates much easier.</p>
  3043. <p>The following example is from the <a href="https://www.puppet.com/docs/puppet/8/lang_template_erb.html" title="Creating templates using Embedded Ruby">ERB documentation</a>:</p>
  3044. <pre># Peers
  3045. &lt;% [@peers].flatten.each do |peer| -%&gt;
  3046. peer &lt;%= peer %&gt;
  3047. &lt;% end -%&gt;</pre>
  3048. <p>This allows for nice flexibility as <code>@peers</code> can now be either a single value, an array, or a nested array and all are handled in the same way without needing to write complicated if/else statements.</p>
  3049. ]]></content:encoded>
  3050.  </item>
  3051.  
  3052.  <item>
  3053.    <title>No more OSCP stapling</title>
  3054.    <link>https://blog.x-way.org/Linux/2024/07/25/No-more-OSCP-stapling.html</link>
  3055.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324377</guid>
  3056.    <dc:creator>Andreas Jaggi</dc:creator>
  3057.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3058.    <pubDate>Thu, 25 Jul 2024 08:42:00 +0200</pubDate>
  3059.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  3060.    <description><![CDATA[<p><a href="https://letsencrypt.org/2024/07/23/replacing-ocsp-with-crls.html" title="Intent to End OCSP Service -  Let's Encrypt">Let's Encrypt announced</a> that it intends to stop supporting <a href="https://en.wikipedia.org/wiki/Online_Certificate_Status_Protocol" title="Online Certificate Status Protocol - Wikipedia">OCSP</a>, which means that <a href="https://utcc.utoronto.ca/~cks/space/blog/web/OCSPIsBasicallyDead" title="Chris's Wiki :: blog/web/OCSPIsBasicallyDead">OCSP is basically dead now</a>.</p>
  3061. <p><a href="https://en.wikipedia.org/wiki/OCSP_stapling" title="OCSP stapling - Wikipedia">OCSP stapling</a> on my server has been enabled since 2012.<br>With the prospect of it no longer working in the future, I've disabled it again in the nginx configuration.</p>
  3062. <pre> # aj, 05.11.2012, OCSP stapling (for testing see http://unmitigatedrisk.com/?p=100)
  3063.        # aj, 25.07.2024, turn it off again, as letsencrypt will disable it: https://letsencrypt.org/2024/07/23/replacing-ocsp-with-crls.html
  3064. # ssl_stapling on;</pre>
  3065. ]]></description>
  3066.    <content:encoded><![CDATA[<p><a href="https://letsencrypt.org/2024/07/23/replacing-ocsp-with-crls.html" title="Intent to End OCSP Service -  Let's Encrypt">Let's Encrypt announced</a> that it intends to stop supporting <a href="https://en.wikipedia.org/wiki/Online_Certificate_Status_Protocol" title="Online Certificate Status Protocol - Wikipedia">OCSP</a>, which means that <a href="https://utcc.utoronto.ca/~cks/space/blog/web/OCSPIsBasicallyDead" title="Chris's Wiki :: blog/web/OCSPIsBasicallyDead">OCSP is basically dead now</a>.</p>
  3067. <p><a href="https://en.wikipedia.org/wiki/OCSP_stapling" title="OCSP stapling - Wikipedia">OCSP stapling</a> on my server has been enabled since 2012.<br>With the prospect of it no longer working in the future, I've disabled it again in the nginx configuration.</p>
  3068. <pre> # aj, 05.11.2012, OCSP stapling (for testing see http://unmitigatedrisk.com/?p=100)
  3069.        # aj, 25.07.2024, turn it off again, as letsencrypt will disable it: https://letsencrypt.org/2024/07/23/replacing-ocsp-with-crls.html
  3070. # ssl_stapling on;</pre>
  3071. ]]></content:encoded>
  3072.  </item>
  3073.  
  3074.  <item>
  3075.    <title>Blog Directories</title>
  3076.    <link>https://blog.x-way.org/Misc/2024/07/24/Blog-Directories.html</link>
  3077.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324376</guid>
  3078.    <dc:creator>Andreas Jaggi</dc:creator>
  3079.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3080.    <pubDate>Wed, 24 Jul 2024 19:52:00 +0200</pubDate>
  3081.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  3082.    <description><![CDATA[<p>There are some new blog directory sites popping up again. Nice way to discover niche personal sites outside of the big platforms.</p>
  3083. <ul>
  3084. <li><a href="https://ooh.directory/" title="ooh.directory: a place to find good blogs that interest you">ooh.directory</a></li>
  3085. <li><a href="https://personalsit.es/" title="PersonalSit.es | Yes we got hot and fresh sites">personalsit.es</a></li>
  3086. <li><a href="https://blogroll.org/" title="Ye Olde Blogroll - Blogroll.org">blogroll.org</a></li>
  3087. </ul>
  3088. ]]></description>
  3089.    <content:encoded><![CDATA[<p>There are some new blog directory sites popping up again. Nice way to discover niche personal sites outside of the big platforms.</p>
  3090. <ul>
  3091. <li><a href="https://ooh.directory/" title="ooh.directory: a place to find good blogs that interest you">ooh.directory</a></li>
  3092. <li><a href="https://personalsit.es/" title="PersonalSit.es | Yes we got hot and fresh sites">personalsit.es</a></li>
  3093. <li><a href="https://blogroll.org/" title="Ye Olde Blogroll - Blogroll.org">blogroll.org</a></li>
  3094. </ul>
  3095. ]]></content:encoded>
  3096.  </item>
  3097.  
  3098.  <item>
  3099.    <title>Less: a Survival Guide</title>
  3100.    <link>https://blog.x-way.org/Linux/2024/07/22/Less-a-Survival-Guide.html</link>
  3101.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324375</guid>
  3102.    <dc:creator>Andreas Jaggi</dc:creator>
  3103.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3104.    <pubDate>Mon, 22 Jul 2024 05:06:00 +0200</pubDate>
  3105.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  3106.    <description><![CDATA[<p><a href="https://zck.org/less-a-survival-guide" title="Less: a Survival Guide">Less: a Survival Guide</a> is a concise post from <a href="https://zck.org/" title="zck.org">zck.org</a> demystifying the features of <code>less</code>.</p>
  3107. <p>My two main takeaways were:</p>
  3108. <p>1. Configuring less via the <code>LESS</code> environment variable.<br>The following enables markers and highlighting for search &amp; jump actions, colored output and raw display of terminal escape sequences.</p>
  3109. <pre>export LESS="-J -W --use-color -R"</pre>
  3110. <p>2. Jumping to the start and end of a document with <kbd>g</kbd> and <kbd>G</kbd>.<br>I already used <kbd>/</kbd> for searching, but had always struggled to go back to the beginning of a document.</p>
  3111. ]]></description>
  3112.    <content:encoded><![CDATA[<p><a href="https://zck.org/less-a-survival-guide" title="Less: a Survival Guide">Less: a Survival Guide</a> is a concise post from <a href="https://zck.org/" title="zck.org">zck.org</a> demystifying the features of <code>less</code>.</p>
  3113. <p>My two main takeaways were:</p>
  3114. <p>1. Configuring less via the <code>LESS</code> environment variable.<br>The following enables markers and highlighting for search &amp; jump actions, colored output and raw display of terminal escape sequences.</p>
  3115. <pre>export LESS="-J -W --use-color -R"</pre>
  3116. <p>2. Jumping to the start and end of a document with <kbd>g</kbd> and <kbd>G</kbd>.<br>I already used <kbd>/</kbd> for searching, but had always struggled to go back to the beginning of a document.</p>
  3117. ]]></content:encoded>
  3118.  </item>
  3119.  
  3120.  <item>
  3121.    <title>Lego Space Age</title>
  3122.    <link>https://blog.x-way.org/Webdesign/2024/07/07/Lego-Space-Age.html</link>
  3123.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324374</guid>
  3124.    <dc:creator>Andreas Jaggi</dc:creator>
  3125.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3126.    <pubDate>Sun, 07 Jul 2024 16:43:00 +0200</pubDate>
  3127.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  3128.    <description><![CDATA[<p><a href="https://blog.x-way.org/images/lego_space_age.webp" title="Lego Space Age"><img src="https://blog.x-way.org/images/lego_space_age_thumb.webp" width="500" height="375" alt="Lego Space Age"></a></p>
  3129.  
  3130. <p>While browsing for something unrelated, I came about this wonderful Lego set called <a href="https://www.lego.com/en-us/product/tales-of-the-space-age-21340" title="Tales of the Space Age 21340 | Ideas">'Tales of the Space Age'</a>.<br>
  3131. It was originally created by a fan designer through the Lego Ideas program and turned into this amazing looking Lego set.</p>
  3132.  
  3133. <p>I like the depiction of the space themed science fiction worlds very much, especially the beautiful color gradients giving each world a unique atmosphere.<br>
  3134. The provided <a href="https://www.lego.com/en-us/service/buildinginstructions/21340" title="Building Instructions">building instructions</a> <a href="https://blog.x-way.org/stuff/6500750.pdf" title="Postcards from space - Building Instructions">booklet</a> builds on top of this with illustrations enhancing the views of these worlds.</p>
  3135.  
  3136. <p>Looking at these four panels with the nice space themed color gradients inspired me to rebuild them in CSS.<br>
  3137. First I toyed around with one and then built the other three.</p>
  3138.  
  3139. <p>The outcome of this is now visible on <a href="https://www.andreasjaggi.ch/" title="www.andreasjaggi.ch">andreasjaggi.ch</a> where I replaced the previous entry page with the four color gradients.<br>
  3140. The <a href="https://blog.x-way.org/Webdesign/2024/06/18/More-modern-technologies.html" title="More modern technologies - x-log">previous version</a> is still available on <a href="https://www.andreas-jaggi.ch/" title="www.andreas-jaggi.ch">andreas-jaggi.ch</a> as I couldn't decide yet to retire it, so will be keeping both for now :-)</p>
  3141. ]]></description>
  3142.    <content:encoded><![CDATA[<p><a href="https://blog.x-way.org/images/lego_space_age.webp" title="Lego Space Age"><img src="https://blog.x-way.org/images/lego_space_age_thumb.webp" width="500" height="375" alt="Lego Space Age"></a></p>
  3143.  
  3144. <p>While browsing for something unrelated, I came about this wonderful Lego set called <a href="https://www.lego.com/en-us/product/tales-of-the-space-age-21340" title="Tales of the Space Age 21340 | Ideas">'Tales of the Space Age'</a>.<br>
  3145. It was originally created by a fan designer through the Lego Ideas program and turned into this amazing looking Lego set.</p>
  3146.  
  3147. <p>I like the depiction of the space themed science fiction worlds very much, especially the beautiful color gradients giving each world a unique atmosphere.<br>
  3148. The provided <a href="https://www.lego.com/en-us/service/buildinginstructions/21340" title="Building Instructions">building instructions</a> <a href="https://blog.x-way.org/stuff/6500750.pdf" title="Postcards from space - Building Instructions">booklet</a> builds on top of this with illustrations enhancing the views of these worlds.</p>
  3149.  
  3150. <p>Looking at these four panels with the nice space themed color gradients inspired me to rebuild them in CSS.<br>
  3151. First I toyed around with one and then built the other three.</p>
  3152.  
  3153. <p>The outcome of this is now visible on <a href="https://www.andreasjaggi.ch/" title="www.andreasjaggi.ch">andreasjaggi.ch</a> where I replaced the previous entry page with the four color gradients.<br>
  3154. The <a href="https://blog.x-way.org/Webdesign/2024/06/18/More-modern-technologies.html" title="More modern technologies - x-log">previous version</a> is still available on <a href="https://www.andreas-jaggi.ch/" title="www.andreas-jaggi.ch">andreas-jaggi.ch</a> as I couldn't decide yet to retire it, so will be keeping both for now :-)</p>
  3155. ]]></content:encoded>
  3156.  </item>
  3157.  
  3158.  <item>
  3159.    <title>Jekyll version plugin</title>
  3160.    <link>https://blog.x-way.org/Coding/2024/07/06/Jekyll-version-plugin.html</link>
  3161.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324373</guid>
  3162.    <dc:creator>Andreas Jaggi</dc:creator>
  3163.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3164.    <pubDate>Sat, 06 Jul 2024 18:47:00 +0200</pubDate>
  3165.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  3166.    <description><![CDATA[<p>Recently I added a Generator section to the <a href="https://blog.x-way.org/about.html" title="x-log - About">about page</a> with minimal information about how this page was generated.<br>As part of this it now also shows the version of the <a href="https://jekyllrb.com/" title="Jekyll • Simple, blog-aware, static sites | Transform your plain text into static websites and blogs">Jekyll</a> software that was used to generate everything.</p>
  3167. <p>Surprisingly there seems to be no built-in way to get the version as a template tag.<br>Thus I wrote this mini-plugin to provide such a <code>{% jekyll_version %}</code> tag that can be used to get the version of Jekyll while it is processing the pages.</p>
  3168. <p>To use it with your own Jekyll, simply store the below code in a <code>_plugins/jekyll_version_plugin.rb</code> file.</p>
  3169. <pre># frozen_string_literal: true
  3170. module Jekyll
  3171.  class VersionTag &lt; Liquid::Tag
  3172.    def render(context)
  3173.      Jekyll::VERSION
  3174.    end
  3175.  end
  3176. end
  3177.  
  3178. Liquid::Template.register_tag("jekyll_version", Jekyll::VersionTag)</pre>
  3179. ]]></description>
  3180.    <content:encoded><![CDATA[<p>Recently I added a Generator section to the <a href="https://blog.x-way.org/about.html" title="x-log - About">about page</a> with minimal information about how this page was generated.<br>As part of this it now also shows the version of the <a href="https://jekyllrb.com/" title="Jekyll • Simple, blog-aware, static sites | Transform your plain text into static websites and blogs">Jekyll</a> software that was used to generate everything.</p>
  3181. <p>Surprisingly there seems to be no built-in way to get the version as a template tag.<br>Thus I wrote this mini-plugin to provide such a <code>{% jekyll_version %}</code> tag that can be used to get the version of Jekyll while it is processing the pages.</p>
  3182. <p>To use it with your own Jekyll, simply store the below code in a <code>_plugins/jekyll_version_plugin.rb</code> file.</p>
  3183. <pre># frozen_string_literal: true
  3184. module Jekyll
  3185.  class VersionTag &lt; Liquid::Tag
  3186.    def render(context)
  3187.      Jekyll::VERSION
  3188.    end
  3189.  end
  3190. end
  3191.  
  3192. Liquid::Template.register_tag("jekyll_version", Jekyll::VersionTag)</pre>
  3193. ]]></content:encoded>
  3194.  </item>
  3195.  
  3196.  <item>
  3197.    <title>More statistics tuning</title>
  3198.    <link>https://blog.x-way.org/Webdesign/2024/07/06/More-statistics-tuning.html</link>
  3199.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324372</guid>
  3200.    <dc:creator>Andreas Jaggi</dc:creator>
  3201.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3202.    <pubDate>Sat, 06 Jul 2024 18:10:00 +0200</pubDate>
  3203.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  3204.    <description><![CDATA[<p>After <a href="https://blog.x-way.org/Webdesign/2024/06/30/Improved-text-only-UX.html" title="Improved text-only UX">last weeks work</a> on the <a href="https://blog.x-way.org/statistics.html" title="x-log - Statistics">statistics page</a>, I was still not completely happy with how it renders in text-only browsers.</p>
  3205. <p>Thus the idea of adding <code>&lt;th&gt;</code> headers to the two rows of numbers.<br>This turned out quite well and helped to make things more clear as you can see in this screenshot.</p>
  3206. <p><img src="https://blog.x-way.org/images/lynx-statistics-improved.png" alt="Screenshot of Lynx rendering the improved statistics page" width="720" height="423"></p>
  3207. <p>I initially wanted to use the <code>:first-child</code> selector to hide these additional table headers in graphical web browsers.<br>But didn't get it right with the first try, so the header still showed.</p>
  3208. <p>This actually didn't look that bad, and so I decided to keep the headers visible and styled them nicely so they integrate well with the rest of the statistics table.<br>This is how the <a href="https://blog.x-way.org/statistics.html" title="x-log - Statistics">statistics page</a> now looks in a graphical web browser.</p>
  3209. <p><img src="https://blog.x-way.org/images/firefox-statistics-improved.png" alt="Screenshot of Firefox rendering the improved statistics page" width="720" height="465"></p>
  3210. ]]></description>
  3211.    <content:encoded><![CDATA[<p>After <a href="https://blog.x-way.org/Webdesign/2024/06/30/Improved-text-only-UX.html" title="Improved text-only UX">last weeks work</a> on the <a href="https://blog.x-way.org/statistics.html" title="x-log - Statistics">statistics page</a>, I was still not completely happy with how it renders in text-only browsers.</p>
  3212. <p>Thus the idea of adding <code>&lt;th&gt;</code> headers to the two rows of numbers.<br>This turned out quite well and helped to make things more clear as you can see in this screenshot.</p>
  3213. <p><img src="https://blog.x-way.org/images/lynx-statistics-improved.png" alt="Screenshot of Lynx rendering the improved statistics page" width="720" height="423"></p>
  3214. <p>I initially wanted to use the <code>:first-child</code> selector to hide these additional table headers in graphical web browsers.<br>But didn't get it right with the first try, so the header still showed.</p>
  3215. <p>This actually didn't look that bad, and so I decided to keep the headers visible and styled them nicely so they integrate well with the rest of the statistics table.<br>This is how the <a href="https://blog.x-way.org/statistics.html" title="x-log - Statistics">statistics page</a> now looks in a graphical web browser.</p>
  3216. <p><img src="https://blog.x-way.org/images/firefox-statistics-improved.png" alt="Screenshot of Firefox rendering the improved statistics page" width="720" height="465"></p>
  3217. ]]></content:encoded>
  3218.  </item>
  3219.  
  3220.  <item>
  3221.    <title>Improved text-only UX</title>
  3222.    <link>https://blog.x-way.org/Webdesign/2024/06/30/Improved-text-only-UX.html</link>
  3223.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324371</guid>
  3224.    <dc:creator>Andreas Jaggi</dc:creator>
  3225.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3226.    <pubDate>Sun, 30 Jun 2024 21:37:00 +0200</pubDate>
  3227.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  3228.    <description><![CDATA[<p>Some time ago I read <a href="https://danq.me/2024/05/01/test-your-site-in-lynx/" title="Test your site in Lynx – Dan Q">this article from Dan Q</a> about testing your website in a text-only browser (<a href="https://en.wikipedia.org/wiki/Lynx_(web_browser)" title="Lynx (web browser) - Wikipedia">Lynx</a>, which is the oldest web browser still being maintained, started in 1992).</p>
  3229. <p>Surfing through my blog with Lynx, I was positively surprised in how well the content and structure was presented.<br>Seems like the modernization and simplification efforts of the HTML code behind the scenes paid off well.</p>
  3230. <p>The <a href="https://blog.x-way.org/statistics.html" title="x-log - Statistics">statistics page</a> though was not really usable, it was displayed as a random soup of numbers due to the usage of unstructured <code>&lt;div&gt;</code> tags for the elements of the visual graphs.</p>
  3231. <p>To fix this I reverted back to using <code>&lt;table&gt;</code> tags to structure the data.<br>This way the layout degrades gracefully in text-only browsers and provides a minimally structured representation of the data.<br>And I applied <a href="https://blog.x-way.org/Webdesign/2024/06/18/More-modern-technologies.html" title="More modern technologies - x-log">the newly learned CSS skills</a> (<code>linear-gradient</code> backgrounds) to achieve the same visual graph as beforehand when opening the page in a regular browser.</p>
  3232. <p><img src="https://blog.x-way.org/images/lynx-statistics.png" alt="Screenshot of Lynx rendering the statistics page" width="720" height="423"></p>
  3233. ]]></description>
  3234.    <content:encoded><![CDATA[<p>Some time ago I read <a href="https://danq.me/2024/05/01/test-your-site-in-lynx/" title="Test your site in Lynx – Dan Q">this article from Dan Q</a> about testing your website in a text-only browser (<a href="https://en.wikipedia.org/wiki/Lynx_(web_browser)" title="Lynx (web browser) - Wikipedia">Lynx</a>, which is the oldest web browser still being maintained, started in 1992).</p>
  3235. <p>Surfing through my blog with Lynx, I was positively surprised in how well the content and structure was presented.<br>Seems like the modernization and simplification efforts of the HTML code behind the scenes paid off well.</p>
  3236. <p>The <a href="https://blog.x-way.org/statistics.html" title="x-log - Statistics">statistics page</a> though was not really usable, it was displayed as a random soup of numbers due to the usage of unstructured <code>&lt;div&gt;</code> tags for the elements of the visual graphs.</p>
  3237. <p>To fix this I reverted back to using <code>&lt;table&gt;</code> tags to structure the data.<br>This way the layout degrades gracefully in text-only browsers and provides a minimally structured representation of the data.<br>And I applied <a href="https://blog.x-way.org/Webdesign/2024/06/18/More-modern-technologies.html" title="More modern technologies - x-log">the newly learned CSS skills</a> (<code>linear-gradient</code> backgrounds) to achieve the same visual graph as beforehand when opening the page in a regular browser.</p>
  3238. <p><img src="https://blog.x-way.org/images/lynx-statistics.png" alt="Screenshot of Lynx rendering the statistics page" width="720" height="423"></p>
  3239. ]]></content:encoded>
  3240.  </item>
  3241.  
  3242.  <item>
  3243.    <title>.well-known/traffic-advice</title>
  3244.    <link>https://blog.x-way.org/Webdesign/2024/06/29/well-known-traffic-advice.html</link>
  3245.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324370</guid>
  3246.    <dc:creator>Andreas Jaggi</dc:creator>
  3247.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3248.    <pubDate>Sat, 29 Jun 2024 09:48:00 +0200</pubDate>
  3249.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  3250.    <description><![CDATA[<p>While looking at my 404s the top one for the blog was <code>/.well-known/traffic-advice</code>.<br>
  3251. This is part of the traffic advice mechanism to control traffic from prefetch proxies (and based on my current access logs, seems only used by the <a href="https://developer.chrome.com/blog/private-prefetch-proxy/" title="Private prefetch proxy in Chrome">Chrome Privacy Preserving Prefetch Proxy</a>).</p>
  3252. <p>The traffic advice mechanism is specified in the document <a href="https://buettner.github.io/private-prefetch-proxy/traffic-advice.html" title="Traffic Advice">here</a>.<br>
  3253. It can be used to reduce the number of requests coming from prefetch proxies.</p>
  3254. <p>To get rid of the 404s and provide support for the traffic advice mechanism, I use the following snippet in my nginx config.<br>
  3255. It allows all requests from prefetch proxies (as currently I see no need to limit them).</p>
  3256. <pre># Private Prefetch Proxy
  3257. # https://developer.chrome.com/blog/private-prefetch-proxy/
  3258. location /.well-known/traffic-advice {
  3259.        types { } default_type "application/trafficadvice+json";
  3260.        return 200 '[{"user_agent":"prefetch-proxy","fraction":1.0}]';
  3261. }</pre>
  3262. ]]></description>
  3263.    <content:encoded><![CDATA[<p>While looking at my 404s the top one for the blog was <code>/.well-known/traffic-advice</code>.<br>
  3264. This is part of the traffic advice mechanism to control traffic from prefetch proxies (and based on my current access logs, seems only used by the <a href="https://developer.chrome.com/blog/private-prefetch-proxy/" title="Private prefetch proxy in Chrome">Chrome Privacy Preserving Prefetch Proxy</a>).</p>
  3265. <p>The traffic advice mechanism is specified in the document <a href="https://buettner.github.io/private-prefetch-proxy/traffic-advice.html" title="Traffic Advice">here</a>.<br>
  3266. It can be used to reduce the number of requests coming from prefetch proxies.</p>
  3267. <p>To get rid of the 404s and provide support for the traffic advice mechanism, I use the following snippet in my nginx config.<br>
  3268. It allows all requests from prefetch proxies (as currently I see no need to limit them).</p>
  3269. <pre># Private Prefetch Proxy
  3270. # https://developer.chrome.com/blog/private-prefetch-proxy/
  3271. location /.well-known/traffic-advice {
  3272.        types { } default_type "application/trafficadvice+json";
  3273.        return 200 '[{"user_agent":"prefetch-proxy","fraction":1.0}]';
  3274. }</pre>
  3275. ]]></content:encoded>
  3276.  </item>
  3277.  
  3278.  <item>
  3279.    <title>RSS feed tuning</title>
  3280.    <link>https://blog.x-way.org/Webdesign/2024/06/23/RSS-feed-tuning.html</link>
  3281.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324369</guid>
  3282.    <dc:creator>Andreas Jaggi</dc:creator>
  3283.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3284.    <pubDate>Sun, 23 Jun 2024 16:44:00 +0200</pubDate>
  3285.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  3286.    <description><![CDATA[<p>After the <a href="https://blog.x-way.org/Webdesign/2024/06/16/Jumping-on-the-Web-Components-bandwagon.html" title="Jumping on the Web Components bandwagon - x-log">recent addition of custom Web Components</a>, the usual <a href="https://www.rssboard.org/rss-validator/" title="RSS Validator">feed</a> <a href="https://validator.w3.org/feed/" title="W3C Feed Validation Service, for Atom and RSS">validators</a> were a bit less happy about my <a href="https://blog.x-way.org/rss.xml">RSS</a> and <a href="https://blog.x-way.org/atom.xml">Atom</a> feeds.</p>
  3287. <p>They always marked my feeds as valid, but usually had some recommendations to improve interoperability with the widest range of feed readers.<br>In particular having non-HTML5 elements does not help with interoperability. Which makes sense as there is no real place in the XML of the feeds to reference the needed JavaScript for rendering the Web Components.</p>
  3288. <p>Besides stripping away the &lt;youtube-vimeo-embed&gt; tags and replacing them with a link to the video, I took this opportunity to cleanup some other 'Altlasten' (legacy tech depts).<br>A lot of time was spent trying to get my head around various encodings/escapings of special characters. When the blog started in 2002, UTF-8 was not adopted yet and all special characters needed to be written as <a href="https://developer.mozilla.org/en-US/docs/Glossary/Character_reference" title="Character reference - MDN">HTML entities</a>.<br>And what didn't help is that I somehow had a text-only part in my RSS file which tried to deliver a version of my posts without any HTML (but failed to do so properly as it only had the tags stripped away but did not revert all the HTML character encodings.<br>Of course the various resulting &amp; characters nicely clash with XML encoding).</p>
  3289. <p>There were some other oddities from the past, such as empty post titles and HTML tags inside titles.</p>
  3290. <p>I ended up cleaning up most of this and got rid of the text-only representation and corresponding encoding/escaping problems. (using <code>&lt;![CDATA[</code> and <code>]]&gt;</code> with the HTML content inside makes life so much easier)</p>
  3291. <p>The still remaing recommendations to improve are about relative links and <code>&lt;script&gt;</code> tags.<br>The relative links are all due to my replacing of dead and non-archived link destinations with a single <code>#</code>. So they are more a 'false postive' than a real problem, the links are dead either way.<br>The <code>&lt;script&gt;</code> tags are more problematic, as they result from my embedding of <a href="https://gist.github.com/" title="Discover Discover gists · GitHub">GitHub Gists</a> in posts. The code in the Gists is loaded, rendered and nicely highlighted with color by the script, thus not easy to replicate in a feed.</p>
  3292. <p>Probably the best approach for the Gists would be to find a way to properly include the content into the posts. So that it is rendered nicely when viewed in a browser, and has a meaningful text-only fallback in the feeds.<br>Would make sense to self-hosts these anyways. Next rainy weekend project there you are :-)</p>
  3293. <p><a href="https://www.rssboard.org/rss-validator/check.cgi?url=http%3A%2F%2Fblog.x-way.org%2Frss.xml" title="RSS Validator Results: http://blog.x-way.org/rss.xml"><img src="https://blog.x-way.org/images/valid-rss-rogers.png" width="88" height="31" alt="This is a valid RSS feed."></a> <a href="https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fblog.x-way.org%2Fatom.xml" title="Feed Validator Results: https://blog.x-way.org/atom.xml"><img src="https://blog.x-way.org/images/valid-atom.png" width="88" height="31" alt="This is a valid Atom 1.0 feed."></a></p>
  3294. ]]></description>
  3295.    <content:encoded><![CDATA[<p>After the <a href="https://blog.x-way.org/Webdesign/2024/06/16/Jumping-on-the-Web-Components-bandwagon.html" title="Jumping on the Web Components bandwagon - x-log">recent addition of custom Web Components</a>, the usual <a href="https://www.rssboard.org/rss-validator/" title="RSS Validator">feed</a> <a href="https://validator.w3.org/feed/" title="W3C Feed Validation Service, for Atom and RSS">validators</a> were a bit less happy about my <a href="https://blog.x-way.org/rss.xml">RSS</a> and <a href="https://blog.x-way.org/atom.xml">Atom</a> feeds.</p>
  3296. <p>They always marked my feeds as valid, but usually had some recommendations to improve interoperability with the widest range of feed readers.<br>In particular having non-HTML5 elements does not help with interoperability. Which makes sense as there is no real place in the XML of the feeds to reference the needed JavaScript for rendering the Web Components.</p>
  3297. <p>Besides stripping away the &lt;youtube-vimeo-embed&gt; tags and replacing them with a link to the video, I took this opportunity to cleanup some other 'Altlasten' (legacy tech depts).<br>A lot of time was spent trying to get my head around various encodings/escapings of special characters. When the blog started in 2002, UTF-8 was not adopted yet and all special characters needed to be written as <a href="https://developer.mozilla.org/en-US/docs/Glossary/Character_reference" title="Character reference - MDN">HTML entities</a>.<br>And what didn't help is that I somehow had a text-only part in my RSS file which tried to deliver a version of my posts without any HTML (but failed to do so properly as it only had the tags stripped away but did not revert all the HTML character encodings.<br>Of course the various resulting &amp; characters nicely clash with XML encoding).</p>
  3298. <p>There were some other oddities from the past, such as empty post titles and HTML tags inside titles.</p>
  3299. <p>I ended up cleaning up most of this and got rid of the text-only representation and corresponding encoding/escaping problems. (using <code>&lt;![CDATA[</code> and <code>]]&gt;</code> with the HTML content inside makes life so much easier)</p>
  3300. <p>The still remaing recommendations to improve are about relative links and <code>&lt;script&gt;</code> tags.<br>The relative links are all due to my replacing of dead and non-archived link destinations with a single <code>#</code>. So they are more a 'false postive' than a real problem, the links are dead either way.<br>The <code>&lt;script&gt;</code> tags are more problematic, as they result from my embedding of <a href="https://gist.github.com/" title="Discover Discover gists · GitHub">GitHub Gists</a> in posts. The code in the Gists is loaded, rendered and nicely highlighted with color by the script, thus not easy to replicate in a feed.</p>
  3301. <p>Probably the best approach for the Gists would be to find a way to properly include the content into the posts. So that it is rendered nicely when viewed in a browser, and has a meaningful text-only fallback in the feeds.<br>Would make sense to self-hosts these anyways. Next rainy weekend project there you are :-)</p>
  3302. <p><a href="https://www.rssboard.org/rss-validator/check.cgi?url=http%3A%2F%2Fblog.x-way.org%2Frss.xml" title="RSS Validator Results: http://blog.x-way.org/rss.xml"><img src="https://blog.x-way.org/images/valid-rss-rogers.png" width="88" height="31" alt="This is a valid RSS feed."></a> <a href="https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fblog.x-way.org%2Fatom.xml" title="Feed Validator Results: https://blog.x-way.org/atom.xml"><img src="https://blog.x-way.org/images/valid-atom.png" width="88" height="31" alt="This is a valid Atom 1.0 feed."></a></p>
  3303. ]]></content:encoded>
  3304.  </item>
  3305.  
  3306.  <item>
  3307.    <title>sibatable</title>
  3308.    <link>https://blog.x-way.org/Food/2024/06/22/sibatable.html</link>
  3309.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324368</guid>
  3310.    <dc:creator>Andreas Jaggi</dc:creator>
  3311.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3312.    <pubDate>Sat, 22 Jun 2024 20:06:00 +0200</pubDate>
  3313.    <category domain="https://blog.x-way.org/Food/">Food</category>
  3314.    <description><![CDATA[<p><a href="https://blog.x-way.org/images/sibatable.jpg" title="sibatable"><img src="https://blog.x-way.org/images/sibatable_thumb.jpg" width="446" height="431" alt="A bowl of ramen with the rice and eggs decorated so that they look like a chicken with her chicks."></a></p>
  3315. <p>Amazing food art by <a href="https://www.instagram.com/sibatable/" title="시바테이블 (&#064;sibatable) • Instagram">sibatable</a>.</p>
  3316. <p>Besides the <a href="https://www.instagram.com/sibatable/" title="시바테이블 (&#064;sibatable) • Instagram">Instagram page</a> and the <a href="https://ohou.se/users/8132629" title="sibatable님의 공간에 오신 것을 환영합니다.">ohou.se page</a> check out the articles from <a href="https://www.tapasmagazine.es/en/sibatable-the-aesthetisation-food-through-fantasy/" title="Sibatable, the aestheticisation of food through fantasy - Tapas">Tapas</a> and <a href="https://mymodernmet.com/min-kyung-kin-sibatable-animal-food-art/" title="Super Cute Animal Food Art by Korean Artist">My Modern Met</a> for more infos about the artist.</p>
  3317. <p>(<a href="https://labnotes.org/weekend-reading-occams-shaving-kit/" title="Weekend Reading — Occam&#x27;s shaving kit —  Labnotes (by Assaf Arkin)">via</a>)</p>
  3318. ]]></description>
  3319.    <content:encoded><![CDATA[<p><a href="https://blog.x-way.org/images/sibatable.jpg" title="sibatable"><img src="https://blog.x-way.org/images/sibatable_thumb.jpg" width="446" height="431" alt="A bowl of ramen with the rice and eggs decorated so that they look like a chicken with her chicks."></a></p>
  3320. <p>Amazing food art by <a href="https://www.instagram.com/sibatable/" title="시바테이블 (&#064;sibatable) • Instagram">sibatable</a>.</p>
  3321. <p>Besides the <a href="https://www.instagram.com/sibatable/" title="시바테이블 (&#064;sibatable) • Instagram">Instagram page</a> and the <a href="https://ohou.se/users/8132629" title="sibatable님의 공간에 오신 것을 환영합니다.">ohou.se page</a> check out the articles from <a href="https://www.tapasmagazine.es/en/sibatable-the-aesthetisation-food-through-fantasy/" title="Sibatable, the aestheticisation of food through fantasy - Tapas">Tapas</a> and <a href="https://mymodernmet.com/min-kyung-kin-sibatable-animal-food-art/" title="Super Cute Animal Food Art by Korean Artist">My Modern Met</a> for more infos about the artist.</p>
  3322. <p>(<a href="https://labnotes.org/weekend-reading-occams-shaving-kit/" title="Weekend Reading — Occam&#x27;s shaving kit —  Labnotes (by Assaf Arkin)">via</a>)</p>
  3323. ]]></content:encoded>
  3324.  </item>
  3325.  
  3326.  <item>
  3327.    <title>IPv6 vs IPv4 traffic graphs in MikroTik</title>
  3328.    <link>https://blog.x-way.org/Networking/2024/06/22/IPv6-vs-IPv4-traffic-graphs-in-MikroTik.html</link>
  3329.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324367</guid>
  3330.    <dc:creator>Andreas Jaggi</dc:creator>
  3331.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3332.    <pubDate>Sat, 22 Jun 2024 12:32:00 +0200</pubDate>
  3333.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  3334.    <description><![CDATA[<p>Out of curiosity I wanted to know how much of my Internet traffic uses IPv6 vs the <a href="https://blog.x-way.org/Networking/2013/07/05/Mandatory-requirement-for-all-non-IPv6-capable-products.html">legacy IPv4</a>.</p>
  3335. <p>There is no out-of-the-box graph for this in MikroTik.<br>Several forum and Stack Overflow posts suggest using ratelimiting queues with their graphing feature to collect this data.<p>
  3336. <p>After experimenting a bit, I ended up with the following configuration which creates two queues to collect the traffic data.<br>Important to know, traffic flows on a first-match basis through the queues. Thus the trick of having first the queue matching IPv6 traffic and then the queue matching all the remaining traffic.<br>Also, I use <code>10G</code> as 'unreachable' traffic limit to avoid any traffic being ratelimited. This works well for my 1Gbit/s setup, but will need to be adjusted if you have a higher bandwidth.</p>
  3337. <pre>/queue simple add limit-at=10G/10G max-limit=10G/10G name=v6-traffic queue=ethernet-default/ethernet-default target=2000::/3 total-queue=ethernet-default
  3338. /queue simple add limit-at=10G/10G max-limit=10G/10G name=v4-traffic queue=ethernet-default/ethernet-default target="" total-queue=ethernet-default</pre>
  3339. <p>Having the queues in place for a couple days results in the following graphs:</p>
  3340. <p>IPv6 Traffic<br>
  3341. <img src="https://blog.x-way.org/images/ipv6-traffic.png" width="492" height="251" alt="Weekly traffic graph of the IPv6 queue, showing an average of 379.65Kb incoming traffic."></p>
  3342. <p>IPv4 Traffic<br>
  3343. <img src="https://blog.x-way.org/images/ipv4-traffic.png" width="492" height="251" alt="Weekly traffic graph of the IPv4 queue, showing an average of 21.49Kb incoming traffic."></p>
  3344. <p>Happy to see that a large majority of my traffic uses IPv6 :-)</p>
  3345. ]]></description>
  3346.    <content:encoded><![CDATA[<p>Out of curiosity I wanted to know how much of my Internet traffic uses IPv6 vs the <a href="https://blog.x-way.org/Networking/2013/07/05/Mandatory-requirement-for-all-non-IPv6-capable-products.html">legacy IPv4</a>.</p>
  3347. <p>There is no out-of-the-box graph for this in MikroTik.<br>Several forum and Stack Overflow posts suggest using ratelimiting queues with their graphing feature to collect this data.<p>
  3348. <p>After experimenting a bit, I ended up with the following configuration which creates two queues to collect the traffic data.<br>Important to know, traffic flows on a first-match basis through the queues. Thus the trick of having first the queue matching IPv6 traffic and then the queue matching all the remaining traffic.<br>Also, I use <code>10G</code> as 'unreachable' traffic limit to avoid any traffic being ratelimited. This works well for my 1Gbit/s setup, but will need to be adjusted if you have a higher bandwidth.</p>
  3349. <pre>/queue simple add limit-at=10G/10G max-limit=10G/10G name=v6-traffic queue=ethernet-default/ethernet-default target=2000::/3 total-queue=ethernet-default
  3350. /queue simple add limit-at=10G/10G max-limit=10G/10G name=v4-traffic queue=ethernet-default/ethernet-default target="" total-queue=ethernet-default</pre>
  3351. <p>Having the queues in place for a couple days results in the following graphs:</p>
  3352. <p>IPv6 Traffic<br>
  3353. <img src="https://blog.x-way.org/images/ipv6-traffic.png" width="492" height="251" alt="Weekly traffic graph of the IPv6 queue, showing an average of 379.65Kb incoming traffic."></p>
  3354. <p>IPv4 Traffic<br>
  3355. <img src="https://blog.x-way.org/images/ipv4-traffic.png" width="492" height="251" alt="Weekly traffic graph of the IPv4 queue, showing an average of 21.49Kb incoming traffic."></p>
  3356. <p>Happy to see that a large majority of my traffic uses IPv6 :-)</p>
  3357. ]]></content:encoded>
  3358.  </item>
  3359.  
  3360.  <item>
  3361.    <title>More modern technologies</title>
  3362.    <link>https://blog.x-way.org/Webdesign/2024/06/18/More-modern-technologies.html</link>
  3363.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324366</guid>
  3364.    <dc:creator>Andreas Jaggi</dc:creator>
  3365.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3366.    <pubDate>Tue, 18 Jun 2024 20:59:00 +0200</pubDate>
  3367.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  3368.    <description><![CDATA[<p>After the recent <a href="https://blog.x-way.org/Webdesign/2024/06/16/Jumping-on-the-Web-Components-bandwagon.html" title="Jumping on the Web Components bandwagon - x-log">integration of Web Components in the blog</a>, I made yet another stab at using some modern technologies.</p>
  3369. <p>This time inspired by the <a href="https://lynnandtonic.com/thoughts/entries/ten-years-of-a-single-div/" title="Ten years of A Single Div | Lynn Fisher">Ten years of A Single Div</a> article, my focus was on the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/gradient/linear-gradient" title="linear-gradient() - CSS | MDN">linear-gradient()</a> and <a  href="https://developer.mozilla.org/en-US/docs/Web/CSS/gradient/radial-gradient" title="radial-gradient() - CSS | MDN">radial-gradient()</a> CSS properties.</p>
  3370. <p>They can be combined to draw almost arbitrary shapes with pure CSS.</p>
  3371. <p>I used this to replace all graphics on <a href="https://www.andreas-jaggi.ch/" title="andreas-jaggi.ch">andreas-jaggi.ch</a> with CSS, while keeping the layout and functionality identical to the <a href="https://web.archive.org/web/20050311173245/http://x-way.waterwave.ch/#" title="x-way.waterwave.ch (archive.org)">original 2005 version</a>.</p>
  3372. <p>In the process of this, also some additional modern CSS features were used:<br>
  3373. <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/var" title="var() - CSS | MDN">var()</a> to simplify repeating CSS code.<br>
  3374. <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/animation" title="animation - CSS | MDN">animation</a>/<a href="https://developer.mozilla.org/en-US/docs/Web/CSS/@keyframes" title="@keyframes - CSS | MDN">@keyframes</a> to add a little fade-in effect on the hover text.</p>
  3375. ]]></description>
  3376.    <content:encoded><![CDATA[<p>After the recent <a href="https://blog.x-way.org/Webdesign/2024/06/16/Jumping-on-the-Web-Components-bandwagon.html" title="Jumping on the Web Components bandwagon - x-log">integration of Web Components in the blog</a>, I made yet another stab at using some modern technologies.</p>
  3377. <p>This time inspired by the <a href="https://lynnandtonic.com/thoughts/entries/ten-years-of-a-single-div/" title="Ten years of A Single Div | Lynn Fisher">Ten years of A Single Div</a> article, my focus was on the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/gradient/linear-gradient" title="linear-gradient() - CSS | MDN">linear-gradient()</a> and <a  href="https://developer.mozilla.org/en-US/docs/Web/CSS/gradient/radial-gradient" title="radial-gradient() - CSS | MDN">radial-gradient()</a> CSS properties.</p>
  3378. <p>They can be combined to draw almost arbitrary shapes with pure CSS.</p>
  3379. <p>I used this to replace all graphics on <a href="https://www.andreas-jaggi.ch/" title="andreas-jaggi.ch">andreas-jaggi.ch</a> with CSS, while keeping the layout and functionality identical to the <a href="https://web.archive.org/web/20050311173245/http://x-way.waterwave.ch/#" title="x-way.waterwave.ch (archive.org)">original 2005 version</a>.</p>
  3380. <p>In the process of this, also some additional modern CSS features were used:<br>
  3381. <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/var" title="var() - CSS | MDN">var()</a> to simplify repeating CSS code.<br>
  3382. <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/animation" title="animation - CSS | MDN">animation</a>/<a href="https://developer.mozilla.org/en-US/docs/Web/CSS/@keyframes" title="@keyframes - CSS | MDN">@keyframes</a> to add a little fade-in effect on the hover text.</p>
  3383. ]]></content:encoded>
  3384.  </item>
  3385.  
  3386.  <item>
  3387.    <title>Jumping on the Web Components bandwagon</title>
  3388.    <link>https://blog.x-way.org/Webdesign/2024/06/16/Jumping-on-the-Web-Components-bandwagon.html</link>
  3389.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324365</guid>
  3390.    <dc:creator>Andreas Jaggi</dc:creator>
  3391.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3392.    <pubDate>Sun, 16 Jun 2024 21:53:00 +0200</pubDate>
  3393.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  3394.    <description><![CDATA[<p>The <a href="https://adrianroselli.com/2024/06/youtube-and-vimeo-web-component.html" title="YouTube and Vimeo Web Component - Adrian Roselli">recent article from Adrian Roselli</a> explaining how to write a Web Component for YouTube and Vimeo videos, triggered me to finally adopt the Web Components technology for my blog.<br>Additionally there is <a href="https://kniebes.com/" title="Markus Kniebes">Markus</a> using <a href="https://kniebes.com/2023/07/01/sharing-web-component" title="Sharing Web Component (kniebes.com)">Web Components for his blog</a> since quite some time, which gave me confidence.</p>
  3395. <p>Implementing Web Components was now not only for the sake of learning about the technology, but also to address some longstanding painpoints I had with my embedded videos.<br>In particular did I not like that each embedded video triggered the loading of a plethora of third-party scripts and styles only to render the thumbnail image. And additionally this leaked tracking/cookie information to the video hosters (yes, I was using www.youtube-nocookie.com to reduce this as far as possible, but could not eliminate it completely).</p>
  3396. <p>Thus I added a <code>&lt;youtube-vimeo-embed&gt;</code> Web Component and changed all my embedded YouTube and Vimeo videos to use it.</p>
  3397. <p>My implementation is almost a 1:1 copy of the <a href="https://github.com/aardrian/youtube-vimeo-embed/tree/main" title="GitHub - aardrian/youtube-vimeo-embed: A custom element to embed either a YouTube or Vimeo video into your page.">code provided by Adrian</a>, with some minor adaptions (such as hiding the original link when the video iframe can be rendered and always enabling fullscreen mode in videos).</p>
  3398. <p>I'm quite happy with the outcome, as it provides some new benefits:<br>
  3399. Except for the thumbnail image, no other third-party resources are loaded until someone clicks on the play button.<br>
  3400. When JavaScript or Web Components are not supported by a browser, it gracefuly falls back to a simple link to the video.<br>
  3401. Loading speed of the whole page improved quite a bit, as videos are only loaded on demand.<br>
  3402. It always uses www.youtube-nocookie.com and third-party scripts are only loaded if someone explicitly clicks on the play button of a video :-)</p>
  3403. ]]></description>
  3404.    <content:encoded><![CDATA[<p>The <a href="https://adrianroselli.com/2024/06/youtube-and-vimeo-web-component.html" title="YouTube and Vimeo Web Component - Adrian Roselli">recent article from Adrian Roselli</a> explaining how to write a Web Component for YouTube and Vimeo videos, triggered me to finally adopt the Web Components technology for my blog.<br>Additionally there is <a href="https://kniebes.com/" title="Markus Kniebes">Markus</a> using <a href="https://kniebes.com/2023/07/01/sharing-web-component" title="Sharing Web Component (kniebes.com)">Web Components for his blog</a> since quite some time, which gave me confidence.</p>
  3405. <p>Implementing Web Components was now not only for the sake of learning about the technology, but also to address some longstanding painpoints I had with my embedded videos.<br>In particular did I not like that each embedded video triggered the loading of a plethora of third-party scripts and styles only to render the thumbnail image. And additionally this leaked tracking/cookie information to the video hosters (yes, I was using www.youtube-nocookie.com to reduce this as far as possible, but could not eliminate it completely).</p>
  3406. <p>Thus I added a <code>&lt;youtube-vimeo-embed&gt;</code> Web Component and changed all my embedded YouTube and Vimeo videos to use it.</p>
  3407. <p>My implementation is almost a 1:1 copy of the <a href="https://github.com/aardrian/youtube-vimeo-embed/tree/main" title="GitHub - aardrian/youtube-vimeo-embed: A custom element to embed either a YouTube or Vimeo video into your page.">code provided by Adrian</a>, with some minor adaptions (such as hiding the original link when the video iframe can be rendered and always enabling fullscreen mode in videos).</p>
  3408. <p>I'm quite happy with the outcome, as it provides some new benefits:<br>
  3409. Except for the thumbnail image, no other third-party resources are loaded until someone clicks on the play button.<br>
  3410. When JavaScript or Web Components are not supported by a browser, it gracefuly falls back to a simple link to the video.<br>
  3411. Loading speed of the whole page improved quite a bit, as videos are only loaded on demand.<br>
  3412. It always uses www.youtube-nocookie.com and third-party scripts are only loaded if someone explicitly clicks on the play button of a video :-)</p>
  3413. ]]></content:encoded>
  3414.  </item>
  3415.  
  3416.  <item>
  3417.    <title>blo.gs still Pinging</title>
  3418.    <link>https://blog.x-way.org/Coding/2024/06/12/blogs-still-Pinging.html</link>
  3419.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324364</guid>
  3420.    <dc:creator>Andreas Jaggi</dc:creator>
  3421.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3422.    <pubDate>Wed, 12 Jun 2024 06:28:00 +0200</pubDate>
  3423.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  3424.    <description><![CDATA[<p>While browsing posts from the past on the <a href="https://blog.x-way.org/on-this-day.html" title="x-log - On this day">On this day</a> page, I saw the one about <a href="http://blo.gs/" title="blo.gs">blog.gs</a> from <a href="https://blog.x-way.org/Coding/2002/06/12/blogs-Ping.html" title="x-log - blo.gs-Ping">2002</a>.</p>
  3425. <p>Turns out the blog.gs ping mechanism is still working in exactly the same way after all these years (nowadays operated by Automattic).</p>
  3426. <p>As I don't run my blog with PHP anymore, I added the following step at the end of my deploy script.<br>It uses <code>curl</code> to peform <a href="http://blo.gs/ping-example.php" title="blo.gs: weblogUpdates.extendedPing example">the XML-RPC call</a> of the <code>weblogUpdates.extendedPing</code> API with the parameters for my weblog.</p>
  3427. <pre>curl -X POST -v ping.blo.gs -H 'content-type: text/xml' --data '&lt;?xml version="1.0"?&gt;&lt;methodCall&gt;&lt;methodName&gt;weblogUpdates.extendedPing&lt;/methodName&gt;&lt;params&gt;&lt;param&gt;&lt;value&gt;x-log&lt;/value&gt;&lt;/param&gt;&lt;param&gt;&lt;value&gt;https://blog.x-way.org/&lt;/value&gt;&lt;/param&gt;&lt;param&gt;&lt;value&gt;&lt;/value&gt;&lt;/param&gt;&lt;param&gt;&lt;value&gt;https://blog.x-way.org/rss.xml&lt;/value&gt;&lt;/param&gt;&lt;/params&gt;&lt;/methodCall&gt;'</pre>
  3428. ]]></description>
  3429.    <content:encoded><![CDATA[<p>While browsing posts from the past on the <a href="https://blog.x-way.org/on-this-day.html" title="x-log - On this day">On this day</a> page, I saw the one about <a href="http://blo.gs/" title="blo.gs">blog.gs</a> from <a href="https://blog.x-way.org/Coding/2002/06/12/blogs-Ping.html" title="x-log - blo.gs-Ping">2002</a>.</p>
  3430. <p>Turns out the blog.gs ping mechanism is still working in exactly the same way after all these years (nowadays operated by Automattic).</p>
  3431. <p>As I don't run my blog with PHP anymore, I added the following step at the end of my deploy script.<br>It uses <code>curl</code> to peform <a href="http://blo.gs/ping-example.php" title="blo.gs: weblogUpdates.extendedPing example">the XML-RPC call</a> of the <code>weblogUpdates.extendedPing</code> API with the parameters for my weblog.</p>
  3432. <pre>curl -X POST -v ping.blo.gs -H 'content-type: text/xml' --data '&lt;?xml version="1.0"?&gt;&lt;methodCall&gt;&lt;methodName&gt;weblogUpdates.extendedPing&lt;/methodName&gt;&lt;params&gt;&lt;param&gt;&lt;value&gt;x-log&lt;/value&gt;&lt;/param&gt;&lt;param&gt;&lt;value&gt;https://blog.x-way.org/&lt;/value&gt;&lt;/param&gt;&lt;param&gt;&lt;value&gt;&lt;/value&gt;&lt;/param&gt;&lt;param&gt;&lt;value&gt;https://blog.x-way.org/rss.xml&lt;/value&gt;&lt;/param&gt;&lt;/params&gt;&lt;/methodCall&gt;'</pre>
  3433. ]]></content:encoded>
  3434.  </item>
  3435.  
  3436.  <item>
  3437.    <title>Run Your Own Mail Server</title>
  3438.    <link>https://blog.x-way.org/Linux/2024/05/31/Run-Your-Own-Mail-Server.html</link>
  3439.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324363</guid>
  3440.    <dc:creator>Andreas Jaggi</dc:creator>
  3441.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3442.    <pubDate>Fri, 31 May 2024 20:24:00 +0200</pubDate>
  3443.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  3444.    <description><![CDATA[<p><a href="https://mwl.io/" title="About Me - Michael W Lucas">Michael W Lucas</a> is running a <a href="https://www.kickstarter.com/projects/mwlucas/run-your-own-mail-server/" title="Run Your Own Mail Server: A Book for Independence &amp; Privacy">Kickstarter campaign</a> to fund writing of book providing the knowledge to run your own mail server.</p>
  3445. <p>As I'm running my own mail server (coincidently with some of the tools that will be discussed in the book: Debian, Postfix, Dovecot), I do sympathize with this initiative and would recommend to support the campaign.</p>
  3446. ]]></description>
  3447.    <content:encoded><![CDATA[<p><a href="https://mwl.io/" title="About Me - Michael W Lucas">Michael W Lucas</a> is running a <a href="https://www.kickstarter.com/projects/mwlucas/run-your-own-mail-server/" title="Run Your Own Mail Server: A Book for Independence &amp; Privacy">Kickstarter campaign</a> to fund writing of book providing the knowledge to run your own mail server.</p>
  3448. <p>As I'm running my own mail server (coincidently with some of the tools that will be discussed in the book: Debian, Postfix, Dovecot), I do sympathize with this initiative and would recommend to support the campaign.</p>
  3449. ]]></content:encoded>
  3450.  </item>
  3451.  
  3452.  <item>
  3453.    <title>udm=14</title>
  3454.    <link>https://blog.x-way.org/Misc/2024/05/25/udm-14.html</link>
  3455.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324362</guid>
  3456.    <dc:creator>Andreas Jaggi</dc:creator>
  3457.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3458.    <pubDate>Sat, 25 May 2024 09:30:00 +0200</pubDate>
  3459.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  3460.    <description><![CDATA[<p>As seen <a href="https://vowe.net/2024/05/20/old-school-google/" title="Old School Google - vowe dot net">all</a> <a href="https://daringfireball.net/linked/2024/05/22/google-web-tedium" title="Daring Fireball: How to Make Google’s 'Web' View Your Search Default">over</a> <a href="https://kottke.org/24/05/0044646-how-to-get-google-search" title="How to get Google search results without the AI garbage">the</a> <a href="https://bookmark.kniebes.io/bookmark/128c284f18cd11efadf1408d5c84b5d9" title="&amp;udm=14 | the disenshittification Konami code">place</a>, adding <code>udm=14</code> to the URL of a Google search makes the result display less crappy (no ads, no AI suggestions to <a href="https://www.bbc.com/news/articles/cd11gzejgz4o" title="Google AI search tells users to glue pizza and eat rocks">eat rocks or put glue on pizza</a>, &hellip;).<br>The search results themselves of course are not really getting better with this, but at least the search experience is less annoying.</p>
  3461. <p>For the Desktop edition of Firefox you will need to use the <a href="https://addons.mozilla.org/en-US/firefox/addon/udm14/" title="udm14 - Get this Extension for Firefox">udm14 extension</a> to add the <code>udm=14</code> parameter by default to your search bar.<br>For other browsers it should be enough to modify the settings of the search URL used and add the parameter (something like <code>https://www.google.com/search?q=%s&amp;udm=14</code>).<br>Or even better, do use an alternative search engine :-)</p>
  3462. ]]></description>
  3463.    <content:encoded><![CDATA[<p>As seen <a href="https://vowe.net/2024/05/20/old-school-google/" title="Old School Google - vowe dot net">all</a> <a href="https://daringfireball.net/linked/2024/05/22/google-web-tedium" title="Daring Fireball: How to Make Google’s 'Web' View Your Search Default">over</a> <a href="https://kottke.org/24/05/0044646-how-to-get-google-search" title="How to get Google search results without the AI garbage">the</a> <a href="https://bookmark.kniebes.io/bookmark/128c284f18cd11efadf1408d5c84b5d9" title="&amp;udm=14 | the disenshittification Konami code">place</a>, adding <code>udm=14</code> to the URL of a Google search makes the result display less crappy (no ads, no AI suggestions to <a href="https://www.bbc.com/news/articles/cd11gzejgz4o" title="Google AI search tells users to glue pizza and eat rocks">eat rocks or put glue on pizza</a>, &hellip;).<br>The search results themselves of course are not really getting better with this, but at least the search experience is less annoying.</p>
  3464. <p>For the Desktop edition of Firefox you will need to use the <a href="https://addons.mozilla.org/en-US/firefox/addon/udm14/" title="udm14 - Get this Extension for Firefox">udm14 extension</a> to add the <code>udm=14</code> parameter by default to your search bar.<br>For other browsers it should be enough to modify the settings of the search URL used and add the parameter (something like <code>https://www.google.com/search?q=%s&amp;udm=14</code>).<br>Or even better, do use an alternative search engine :-)</p>
  3465. ]]></content:encoded>
  3466.  </item>
  3467.  
  3468.  <item>
  3469.    <title>Recent Docker BuildKit Features</title>
  3470.    <link>https://blog.x-way.org/Linux/2024/05/20/Recent-Docker-BuildKit-Features.html</link>
  3471.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324361</guid>
  3472.    <dc:creator>Andreas Jaggi</dc:creator>
  3473.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3474.    <pubDate>Mon, 20 May 2024 07:24:00 +0200</pubDate>
  3475.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  3476.    <description><![CDATA[<p>In the <a href="https://martinheinz.dev/blog/111" title="Recent Docker BuildKit Features You're Missing Out On | Martin Heinz | Personal Website &amp; Blog">Recent Docker BuildKit Features You're Missing Out On</a> article, <a href="https://martinheinz.dev/" title="Martin Heinz | Personal Website &amp; Blog">Martin Heinz</a> lists some of the new features that have been added to Docker with the BuildKit introduction.</p>
  3477. <p>My favorite one is the <a href="https://github.com/docker/buildx/blob/master/docs/debugging.md" title="debugging docs">debugger for failed build steps</a> of a container:</p>
  3478. <pre>export BUILDX_EXPERIMENTAL=1
  3479. docker buildx debug --invoke /bin/sh --on=error build .</pre>
  3480. ]]></description>
  3481.    <content:encoded><![CDATA[<p>In the <a href="https://martinheinz.dev/blog/111" title="Recent Docker BuildKit Features You're Missing Out On | Martin Heinz | Personal Website &amp; Blog">Recent Docker BuildKit Features You're Missing Out On</a> article, <a href="https://martinheinz.dev/" title="Martin Heinz | Personal Website &amp; Blog">Martin Heinz</a> lists some of the new features that have been added to Docker with the BuildKit introduction.</p>
  3482. <p>My favorite one is the <a href="https://github.com/docker/buildx/blob/master/docs/debugging.md" title="debugging docs">debugger for failed build steps</a> of a container:</p>
  3483. <pre>export BUILDX_EXPERIMENTAL=1
  3484. docker buildx debug --invoke /bin/sh --on=error build .</pre>
  3485. ]]></content:encoded>
  3486.  </item>
  3487.  
  3488.  <item>
  3489.    <title>Migrations</title>
  3490.    <link>https://blog.x-way.org/Coding/2024/05/20/Migrations.html</link>
  3491.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324360</guid>
  3492.    <dc:creator>Andreas Jaggi</dc:creator>
  3493.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3494.    <pubDate>Mon, 20 May 2024 06:02:00 +0200</pubDate>
  3495.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  3496.    <description><![CDATA[<blockquote cite="https://twitter.com/mipsytipsy/status/1778534529298489428">
  3497. <p>Migrations are not something you can do rarely, or put off, or avoid; not if you are a growing company. Migrations are an ordinary fact of life.</p>
  3498. <p>Doing them swiftly, efficiently, and -- most of all -- *completely* is one of the most critical skills you can develop as a team.</p>
  3499. </blockquote>
  3500. <p>&mdash; <a href="https://charity.wtf/" title="Charity Majors">Charity Majors</a> (<a href="https://simonwillison.net/2024/May/6/charity-majors/" title="A quote from Charity Majors">via</a>)</p>
  3501. ]]></description>
  3502.    <content:encoded><![CDATA[<blockquote cite="https://twitter.com/mipsytipsy/status/1778534529298489428">
  3503. <p>Migrations are not something you can do rarely, or put off, or avoid; not if you are a growing company. Migrations are an ordinary fact of life.</p>
  3504. <p>Doing them swiftly, efficiently, and -- most of all -- *completely* is one of the most critical skills you can develop as a team.</p>
  3505. </blockquote>
  3506. <p>&mdash; <a href="https://charity.wtf/" title="Charity Majors">Charity Majors</a> (<a href="https://simonwillison.net/2024/May/6/charity-majors/" title="A quote from Charity Majors">via</a>)</p>
  3507. ]]></content:encoded>
  3508.  </item>
  3509.  
  3510.  <item>
  3511.    <title>Building a Geocities website in 1998</title>
  3512.    <link>https://blog.x-way.org/Misc/2024/05/19/Building-a-Geocities-website-in-1998.html</link>
  3513.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324359</guid>
  3514.    <dc:creator>Andreas Jaggi</dc:creator>
  3515.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3516.    <pubDate>Sun, 19 May 2024 11:35:00 +0200</pubDate>
  3517.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  3518.    <description><![CDATA[<p><a href="https://youtu.be/HeXVKrtecis" title="Building a Geocities website in 1998 - YouTube">Building a Geocities website in 1998</a></p>
  3519. <p>Brings back some faint memories of young me playing around with FrontPage (wondering why the preview rendering of an animated fullscreen background of a burning fire is making the computer go slow&hellip;)</p>
  3520. <p>(<a href="https://buttondown.email/cassidoo/archive/an-honest-man-is-always-a-child-socrates/" title="Web links of the week - cassidoo">via</a>)</p>
  3521. ]]></description>
  3522.    <content:encoded><![CDATA[<p><a href="https://youtu.be/HeXVKrtecis" title="Building a Geocities website in 1998 - YouTube">Building a Geocities website in 1998</a></p>
  3523. <p>Brings back some faint memories of young me playing around with FrontPage (wondering why the preview rendering of an animated fullscreen background of a burning fire is making the computer go slow&hellip;)</p>
  3524. <p>(<a href="https://buttondown.email/cassidoo/archive/an-honest-man-is-always-a-child-socrates/" title="Web links of the week - cassidoo">via</a>)</p>
  3525. ]]></content:encoded>
  3526.  </item>
  3527.  
  3528.  <item>
  3529.    <title>On this day</title>
  3530.    <link>https://blog.x-way.org/Misc/2024/05/13/On-this-day.html</link>
  3531.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324358</guid>
  3532.    <dc:creator>Andreas Jaggi</dc:creator>
  3533.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3534.    <pubDate>Mon, 13 May 2024 07:00:00 +0200</pubDate>
  3535.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  3536.    <description><![CDATA[<p>In his <a href="https://shkspr.mobi/blog/2024/05/it-was-twenty-years-ago-today/" title="It was twenty years ago today &mdash; Terence Eden's Blog">20 year anniversary post</a>, <a href="https://shkspr.mobi/blog/" title="Terence Eden's Blog">Terence Eden</a> explains how he uses the "<a href="https://shkspr.mobi/blog/on-this-day/" title="On This Day &mdash; Terence Eden's Blog">On This Day</a>" feature of his blog every morning to look back on what he was writing on this day in previous years.</p>
  3537. <p>Finding this very inspiring, I decided to add a similar feature to my blog.<br>As my blog is built with Jekyll as static pages, some plain old JavaScript was needed to surface the posts of this day without having to rebuild the page daily.</p>
  3538. <p>And here we have now the <a href="https://blog.x-way.org/on-this-day.html" title="x-log - On This day">On this day</a> page :-)</p>
  3539. ]]></description>
  3540.    <content:encoded><![CDATA[<p>In his <a href="https://shkspr.mobi/blog/2024/05/it-was-twenty-years-ago-today/" title="It was twenty years ago today &mdash; Terence Eden's Blog">20 year anniversary post</a>, <a href="https://shkspr.mobi/blog/" title="Terence Eden's Blog">Terence Eden</a> explains how he uses the "<a href="https://shkspr.mobi/blog/on-this-day/" title="On This Day &mdash; Terence Eden's Blog">On This Day</a>" feature of his blog every morning to look back on what he was writing on this day in previous years.</p>
  3541. <p>Finding this very inspiring, I decided to add a similar feature to my blog.<br>As my blog is built with Jekyll as static pages, some plain old JavaScript was needed to surface the posts of this day without having to rebuild the page daily.</p>
  3542. <p>And here we have now the <a href="https://blog.x-way.org/on-this-day.html" title="x-log - On This day">On this day</a> page :-)</p>
  3543. ]]></content:encoded>
  3544.  </item>
  3545.  
  3546.  <item>
  3547.    <title>Warm weather warm colors</title>
  3548.    <link>https://blog.x-way.org/Webdesign/2024/05/11/Warm-weather-warm-colors.html</link>
  3549.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324357</guid>
  3550.    <dc:creator>Andreas Jaggi</dc:creator>
  3551.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3552.    <pubDate>Sat, 11 May 2024 20:03:00 +0200</pubDate>
  3553.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  3554.    <description><![CDATA[<p>The warm temperatures around here made me change the blog theme back to the warm colors ☀️</p>
  3555. <p>Basically it's a revert of the <a href="https://blog.x-way.org/Webdesign/2024/01/01/Winter-plain-2.html" title="x-log - Winter - plain 2">winter layout changes</a> from beginning of the year, while keeping <a href="https://blog.x-way.org/Webdesign/2024/01/03/Valid-HTML5.html" title="x-log - Valid HTML5">all</a> <a href="https://blog.x-way.org/Webdesign/2024/01/27/Quick-and-dirty-dark-mode.html" title="x-log - Quick and dirty dark mode">the</a> <a href="https://blog.x-way.org/Webdesign/2024/01/28/Tables-are-gone.html" title="x-log - Tables are gone">HTML modernizations</a> done afterwards :-)</p>
  3556. <p>We're back on the <a href="https://blog.x-way.org/Webdesign/2022/06/04/Blogging-like-2002.html" title="x-log - Blogging like 2002">original 2002 layout</a> (with modern HTML), for those trying to keep score. Enjoy!</p>
  3557. ]]></description>
  3558.    <content:encoded><![CDATA[<p>The warm temperatures around here made me change the blog theme back to the warm colors ☀️</p>
  3559. <p>Basically it's a revert of the <a href="https://blog.x-way.org/Webdesign/2024/01/01/Winter-plain-2.html" title="x-log - Winter - plain 2">winter layout changes</a> from beginning of the year, while keeping <a href="https://blog.x-way.org/Webdesign/2024/01/03/Valid-HTML5.html" title="x-log - Valid HTML5">all</a> <a href="https://blog.x-way.org/Webdesign/2024/01/27/Quick-and-dirty-dark-mode.html" title="x-log - Quick and dirty dark mode">the</a> <a href="https://blog.x-way.org/Webdesign/2024/01/28/Tables-are-gone.html" title="x-log - Tables are gone">HTML modernizations</a> done afterwards :-)</p>
  3560. <p>We're back on the <a href="https://blog.x-way.org/Webdesign/2022/06/04/Blogging-like-2002.html" title="x-log - Blogging like 2002">original 2002 layout</a> (with modern HTML), for those trying to keep score. Enjoy!</p>
  3561. ]]></content:encoded>
  3562.  </item>
  3563.  
  3564.  <item>
  3565.    <title>The KonCodie Method</title>
  3566.    <link>https://blog.x-way.org/Coding/2024/05/11/The-KonCodie-Method.html</link>
  3567.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324356</guid>
  3568.    <dc:creator>Andreas Jaggi</dc:creator>
  3569.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3570.    <pubDate>Sat, 11 May 2024 17:09:00 +0200</pubDate>
  3571.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  3572.    <description><![CDATA[<p>What if <a href="https://konmari.com/" title="KonMarie | The Official Website of Marie Kondo">Marie Kondo</a> would become a software engineer?</p>
  3573. <p><a href="https://www.200ok.com.au/" title="200 OK">Ben Buchanan</a> did run a parody account on this topic and has archived the posts <a href="https://weblog.200ok.com.au/2023/07/the-koncodie-method.html" title="The KonCodie Method | the 200ok weblog">on his site</a>.</p>
  3574. <p>There are some gems :-)</p>
  3575. <blockquote cite="https://weblog.200ok.com.au/2023/07/the-koncodie-method.html#koncodie-02"><p>To choose what to keep and what to throw away, take each dependency in one's manifest and ask: "Does this spark joy?" If it does, keep it. If not, remove it from your codebase.</p></blockquote>
  3576. <blockquote cite="https://weblog.200ok.com.au/2023/07/the-koncodie-method.html#koncodie-08"><p>We should be choosing what to <code>.gitkeep</code>, not what we want to <code>.gitignore</code></p></blockquote>
  3577. <blockquote cite="https://weblog.200ok.com.au/2023/07/the-koncodie-method.html#koncodie-31"><p>Cruft has only two possible causes: too much effort is required to refactor or it is unclear where things belong.</p></blockquote>
  3578. ]]></description>
  3579.    <content:encoded><![CDATA[<p>What if <a href="https://konmari.com/" title="KonMarie | The Official Website of Marie Kondo">Marie Kondo</a> would become a software engineer?</p>
  3580. <p><a href="https://www.200ok.com.au/" title="200 OK">Ben Buchanan</a> did run a parody account on this topic and has archived the posts <a href="https://weblog.200ok.com.au/2023/07/the-koncodie-method.html" title="The KonCodie Method | the 200ok weblog">on his site</a>.</p>
  3581. <p>There are some gems :-)</p>
  3582. <blockquote cite="https://weblog.200ok.com.au/2023/07/the-koncodie-method.html#koncodie-02"><p>To choose what to keep and what to throw away, take each dependency in one's manifest and ask: "Does this spark joy?" If it does, keep it. If not, remove it from your codebase.</p></blockquote>
  3583. <blockquote cite="https://weblog.200ok.com.au/2023/07/the-koncodie-method.html#koncodie-08"><p>We should be choosing what to <code>.gitkeep</code>, not what we want to <code>.gitignore</code></p></blockquote>
  3584. <blockquote cite="https://weblog.200ok.com.au/2023/07/the-koncodie-method.html#koncodie-31"><p>Cruft has only two possible causes: too much effort is required to refactor or it is unclear where things belong.</p></blockquote>
  3585. ]]></content:encoded>
  3586.  </item>
  3587.  
  3588.  <item>
  3589.    <title>If you don't fit...</title>
  3590.    <link>https://blog.x-way.org/Misc/2024/05/05/If-you-dont-fit.html</link>
  3591.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324354</guid>
  3592.    <dc:creator>Andreas Jaggi</dc:creator>
  3593.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3594.    <pubDate>Sun, 05 May 2024 20:40:00 +0200</pubDate>
  3595.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  3596.    <description><![CDATA[<p><a href="https://blog.x-way.org/images/if-you-dont-fit.png" title="A sad little puzzle piece is looking at a puzzle with no room for him. The text says &quot;If you don't fit... Maybe you haven't found the right puzzle.&quot; Then the piece joins a puzzle that is full of friendly pieces with lots of room"><img src="https://blog.x-way.org/images/if-you-dont-fit_thumb.png" height="500" width="400" alt="A sad little puzzle piece is looking at a puzzle with no room for him. The text says &quot;If you don't fit... Maybe you haven't found the right puzzle.&quot; Then the piece joins a puzzle that is full of friendly pieces with lots of room"></a></p>
  3597. <p>&quot;If you don't fit... Maybe you haven't found the right puzzle.&quot; &mdash; <a href="https://admiralwonderboat.com/" title="ADMIRAL WONDERBOAT">Admiral</a> <a href="https://mastodon.social/@admiralwonderboat/112368789681867074" title="ADMIRAL WONDERBOAT">Wonderboat</a> (<a href="https://fosstodon.org/@sushee" title="Su-Shee">via</a>)</p>
  3598. ]]></description>
  3599.    <content:encoded><![CDATA[<p><a href="https://blog.x-way.org/images/if-you-dont-fit.png" title="A sad little puzzle piece is looking at a puzzle with no room for him. The text says &quot;If you don't fit... Maybe you haven't found the right puzzle.&quot; Then the piece joins a puzzle that is full of friendly pieces with lots of room"><img src="https://blog.x-way.org/images/if-you-dont-fit_thumb.png" height="500" width="400" alt="A sad little puzzle piece is looking at a puzzle with no room for him. The text says &quot;If you don't fit... Maybe you haven't found the right puzzle.&quot; Then the piece joins a puzzle that is full of friendly pieces with lots of room"></a></p>
  3600. <p>&quot;If you don't fit... Maybe you haven't found the right puzzle.&quot; &mdash; <a href="https://admiralwonderboat.com/" title="ADMIRAL WONDERBOAT">Admiral</a> <a href="https://mastodon.social/@admiralwonderboat/112368789681867074" title="ADMIRAL WONDERBOAT">Wonderboat</a> (<a href="https://fosstodon.org/@sushee" title="Su-Shee">via</a>)</p>
  3601. ]]></content:encoded>
  3602.  </item>
  3603.  
  3604.  <item>
  3605.    <title>Migrate from legacy CSM boot to UEFI boot</title>
  3606.    <link>https://blog.x-way.org/Linux/2024/05/05/Migrate-from-legacy-CSM-boot-to-UEFI-boot.html</link>
  3607.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324355</guid>
  3608.    <dc:creator>Andreas Jaggi</dc:creator>
  3609.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3610.    <pubDate>Sun, 05 May 2024 16:00:00 +0200</pubDate>
  3611.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  3612.    <description><![CDATA[<p>Due to a hardware failure I had to replace one of my computers (switching from a <a href="https://www.galaxus.ch/de/s1/product/intel-nuc-swift-canyon-nuc6i5syh-intel-core-i5-6260u-barebone-5670885" title="Intel NUC SWIFT CANYON NUC6I5SYH">2015 Intel NUC</a> to a <a href="https://www.galaxus.ch/de/s1/product/dell-optiplex-mff-intel-core-i5-12500t-16-gb-512-gb-ssd-pc-40390750" title="Dell OptiPlex MFF">Dell OptiPlex Micro 7010</a>).<br>
  3613. After moving the disk to the new system, it refused to boot (claimed that no bootable drive was available).</p>
  3614. <p>Turns out that the new system only supports UEFI booting and the existing disk was setup for 'legacy'/CSM boot.</p>
  3615. <p>I used the following steps to convert the existing disk to UEFI boot (while keeping all data on it available).<br>They are inspired by the excellent <a href="http://blog.getreu.net/projects/legacy-to-uefi-boot/" title="Switch Debian from legacy to UEFI boot mode">Switch Debian from legacy to UEFI boot mode</a> guide from <a href="https://blog.getreu.net/" title="Jens Getreu">Jens Getreu</a>.</p>
  3616. <ol>
  3617. <li>Disable secure boot in the BIOS to allow booting from an USB stick.</li>
  3618. <li>Create a bootable USB stick with a Debian live system (see <a href="https://blog.x-way.org/Linux/2024/05/05/Create-a-bootable-Debian-USB-stick-on-macOS.html" title="Create a bootable Debian USB stick on macOS">my previous post</a>)</li>
  3619. <li>Boot into the Debian live system</li>
  3620. <li>Identify the disk to work on (<code>/dev/nvme0n1</code> in my case)</li>
  3621. <li>Convert the partition table from MBR to GPT:
  3622. <pre># gdisk /dev/nvme0n1
  3623.  
  3624. r       recovery and transformation options (experts only)
  3625. f       load MBR and build fresh GPT from it
  3626. w write table to disk and exit</pre></li>
  3627. <li>Install gparted into the Debian live system:
  3628. <pre># apt-get install gparted</pre></li>
  3629. <li>Create an UEFI partition and a partition for Grub2:
  3630. <pre># gparted /dev/nvme0n1</pre>
  3631. Resize an existing partition to create space (does not need to be at the beginning of the disk, I used the swap partition).<br>
  3632. Create a new 100MB partition for efi (named "Efi partition"), format it as <code>fat32</code> and flag it <code>bootable</code>.<br>
  3633. Create a new 50MB partition for Grub2 (named "BIOS boot partition"), keep it unformatted.</li>
  3634. <li>Use gdisk to set proper partition codes (<code>EF00</code> for the efi partition and <code>EF02</code> for the Grub2 partition):
  3635. <pre># gdisk /dev/nvme0n1
  3636.  
  3637. p print the partition table
  3638. t change a partition's type code
  3639. t change a partition's type code
  3640. w write table to disk and exit</pre></li>
  3641. <li>Chroot into the on-disk root system:
  3642. <pre># mount -t ext4 /dev/nvme0n1p1 /mnt
  3643. # mkdir /mnt/boot/efi
  3644. # mount /dev/nvme0n1p2 /mnt/boot/efi
  3645. # mount --bind /sys /mnt/sys
  3646. # mount --bind /proc /mnt/proc
  3647. # mount --bind /dev /mnt/dev
  3648. # mount --bind /dev/pts /mnt/dev/pts
  3649. # cp /etc/resolv.conf /mnt/etc/resolv.conf
  3650. # chroot /mnt</pre></li>
  3651. <li>Update /etc/fstab:
  3652. <pre># ls -lisa /dev/disk/by-uuid</pre>
  3653. Identify the UUID of the EFI partition (usually in the format <code>XXXX-XXXX</code>) and add a corresponding line to <code>/etc/fstab</code>:
  3654. <pre># echo "UUID=XXXX-XXXX /boot/efi vfat defaults 0 2" &gt;&gt; /etc/fstab</pre></li>
  3655. <li>Install grub-efi and install Grub2 to the EFI partition:
  3656. <pre># apt-get remove grub-pc
  3657. # apt-get install grub-efi</pre>
  3658. <pre># grub-install /dev/nvme0n1</pre></li>
  3659. <li>Exit the chroot and reboot the system:
  3660. <pre># exit
  3661. # reboot</pre></li>
  3662. <li>Select the Debian bootloader (<code>/EFI/debian/grubx64.efi</code>) in the UEFI BIOS and make it the default :-)</li>
  3663. </ol>
  3664. ]]></description>
  3665.    <content:encoded><![CDATA[<p>Due to a hardware failure I had to replace one of my computers (switching from a <a href="https://www.galaxus.ch/de/s1/product/intel-nuc-swift-canyon-nuc6i5syh-intel-core-i5-6260u-barebone-5670885" title="Intel NUC SWIFT CANYON NUC6I5SYH">2015 Intel NUC</a> to a <a href="https://www.galaxus.ch/de/s1/product/dell-optiplex-mff-intel-core-i5-12500t-16-gb-512-gb-ssd-pc-40390750" title="Dell OptiPlex MFF">Dell OptiPlex Micro 7010</a>).<br>
  3666. After moving the disk to the new system, it refused to boot (claimed that no bootable drive was available).</p>
  3667. <p>Turns out that the new system only supports UEFI booting and the existing disk was setup for 'legacy'/CSM boot.</p>
  3668. <p>I used the following steps to convert the existing disk to UEFI boot (while keeping all data on it available).<br>They are inspired by the excellent <a href="http://blog.getreu.net/projects/legacy-to-uefi-boot/" title="Switch Debian from legacy to UEFI boot mode">Switch Debian from legacy to UEFI boot mode</a> guide from <a href="https://blog.getreu.net/" title="Jens Getreu">Jens Getreu</a>.</p>
  3669. <ol>
  3670. <li>Disable secure boot in the BIOS to allow booting from an USB stick.</li>
  3671. <li>Create a bootable USB stick with a Debian live system (see <a href="https://blog.x-way.org/Linux/2024/05/05/Create-a-bootable-Debian-USB-stick-on-macOS.html" title="Create a bootable Debian USB stick on macOS">my previous post</a>)</li>
  3672. <li>Boot into the Debian live system</li>
  3673. <li>Identify the disk to work on (<code>/dev/nvme0n1</code> in my case)</li>
  3674. <li>Convert the partition table from MBR to GPT:
  3675. <pre># gdisk /dev/nvme0n1
  3676.  
  3677. r       recovery and transformation options (experts only)
  3678. f       load MBR and build fresh GPT from it
  3679. w write table to disk and exit</pre></li>
  3680. <li>Install gparted into the Debian live system:
  3681. <pre># apt-get install gparted</pre></li>
  3682. <li>Create an UEFI partition and a partition for Grub2:
  3683. <pre># gparted /dev/nvme0n1</pre>
  3684. Resize an existing partition to create space (does not need to be at the beginning of the disk, I used the swap partition).<br>
  3685. Create a new 100MB partition for efi (named "Efi partition"), format it as <code>fat32</code> and flag it <code>bootable</code>.<br>
  3686. Create a new 50MB partition for Grub2 (named "BIOS boot partition"), keep it unformatted.</li>
  3687. <li>Use gdisk to set proper partition codes (<code>EF00</code> for the efi partition and <code>EF02</code> for the Grub2 partition):
  3688. <pre># gdisk /dev/nvme0n1
  3689.  
  3690. p print the partition table
  3691. t change a partition's type code
  3692. t change a partition's type code
  3693. w write table to disk and exit</pre></li>
  3694. <li>Chroot into the on-disk root system:
  3695. <pre># mount -t ext4 /dev/nvme0n1p1 /mnt
  3696. # mkdir /mnt/boot/efi
  3697. # mount /dev/nvme0n1p2 /mnt/boot/efi
  3698. # mount --bind /sys /mnt/sys
  3699. # mount --bind /proc /mnt/proc
  3700. # mount --bind /dev /mnt/dev
  3701. # mount --bind /dev/pts /mnt/dev/pts
  3702. # cp /etc/resolv.conf /mnt/etc/resolv.conf
  3703. # chroot /mnt</pre></li>
  3704. <li>Update /etc/fstab:
  3705. <pre># ls -lisa /dev/disk/by-uuid</pre>
  3706. Identify the UUID of the EFI partition (usually in the format <code>XXXX-XXXX</code>) and add a corresponding line to <code>/etc/fstab</code>:
  3707. <pre># echo "UUID=XXXX-XXXX /boot/efi vfat defaults 0 2" &gt;&gt; /etc/fstab</pre></li>
  3708. <li>Install grub-efi and install Grub2 to the EFI partition:
  3709. <pre># apt-get remove grub-pc
  3710. # apt-get install grub-efi</pre>
  3711. <pre># grub-install /dev/nvme0n1</pre></li>
  3712. <li>Exit the chroot and reboot the system:
  3713. <pre># exit
  3714. # reboot</pre></li>
  3715. <li>Select the Debian bootloader (<code>/EFI/debian/grubx64.efi</code>) in the UEFI BIOS and make it the default :-)</li>
  3716. </ol>
  3717. ]]></content:encoded>
  3718.  </item>
  3719.  
  3720.  <item>
  3721.    <title>Create a bootable Debian USB stick on macOS</title>
  3722.    <link>https://blog.x-way.org/Linux/2024/05/05/Create-a-bootable-Debian-USB-stick-on-macOS.html</link>
  3723.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324353</guid>
  3724.    <dc:creator>Andreas Jaggi</dc:creator>
  3725.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3726.    <pubDate>Sun, 05 May 2024 14:39:00 +0200</pubDate>
  3727.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  3728.    <description><![CDATA[<p>Needed to create a bootable Debian USB stick for some maintenance on one of my computers.<br>Here are the steps so I won't have to search for them the next time :-)</p>
  3729. <ol>
  3730. <li>Download the <a href="https://www.debian.org/CD/live/" title="">Debian live CD image</a></li>
  3731. <li>Connect your USB stick and find its device location (/dev/diskX) with: <pre>sudo diskutil list</pre></li>
  3732. <li>If needed unmount your USB stick: <pre>sudo diskutil unmountdisk /dev/diskX</pre></li>
  3733. <li>Write the downloaded image onto the USB stick: <pre>sudo dd if=./debian-live-12.5.0-amd64-standard.iso of=/dev/diskX bs=1m</pre></li>
  3734. </ol>
  3735. ]]></description>
  3736.    <content:encoded><![CDATA[<p>Needed to create a bootable Debian USB stick for some maintenance on one of my computers.<br>Here are the steps so I won't have to search for them the next time :-)</p>
  3737. <ol>
  3738. <li>Download the <a href="https://www.debian.org/CD/live/" title="">Debian live CD image</a></li>
  3739. <li>Connect your USB stick and find its device location (/dev/diskX) with: <pre>sudo diskutil list</pre></li>
  3740. <li>If needed unmount your USB stick: <pre>sudo diskutil unmountdisk /dev/diskX</pre></li>
  3741. <li>Write the downloaded image onto the USB stick: <pre>sudo dd if=./debian-live-12.5.0-amd64-standard.iso of=/dev/diskX bs=1m</pre></li>
  3742. </ol>
  3743. ]]></content:encoded>
  3744.  </item>
  3745.  
  3746.  <item>
  3747.    <title>Tiny Fragments</title>
  3748.    <link>https://blog.x-way.org/Misc/2024/04/24/Tiny-Fragments.html</link>
  3749.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324352</guid>
  3750.    <dc:creator>Andreas Jaggi</dc:creator>
  3751.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3752.    <pubDate>Wed, 24 Apr 2024 21:58:00 +0200</pubDate>
  3753.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  3754.    <description><![CDATA[<p><a href="https://daz.itch.io/tiny-fragments" title="Tiny Fragments by Daniel Moreno">Tiny Fragments</a> is a fun little puzzle game made by <a href="https://www.dazlog.com/" title="Dazlog">Daniel Moreno</a> (<a href="https://gigold.me/links/game-tiny-fragments" title="Game: Tiny Fragments | Thomas Gigold">via</a>)</p>
  3755. <img src="https://blog.x-way.org/images/tiny-fragments.png" height="230" width="400" alt="Tiny Fragments - The Tree">
  3756. ]]></description>
  3757.    <content:encoded><![CDATA[<p><a href="https://daz.itch.io/tiny-fragments" title="Tiny Fragments by Daniel Moreno">Tiny Fragments</a> is a fun little puzzle game made by <a href="https://www.dazlog.com/" title="Dazlog">Daniel Moreno</a> (<a href="https://gigold.me/links/game-tiny-fragments" title="Game: Tiny Fragments | Thomas Gigold">via</a>)</p>
  3758. <img src="https://blog.x-way.org/images/tiny-fragments.png" height="230" width="400" alt="Tiny Fragments - The Tree">
  3759. ]]></content:encoded>
  3760.  </item>
  3761.  
  3762.  <item>
  3763.    <title>Testing HTML with modern CSS</title>
  3764.    <link>https://blog.x-way.org/Webdesign/2024/04/23/Testing-HTML-with-modern-CSS.html</link>
  3765.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324351</guid>
  3766.    <dc:creator>Andreas Jaggi</dc:creator>
  3767.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3768.    <pubDate>Tue, 23 Apr 2024 00:30:00 +0200</pubDate>
  3769.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  3770.    <description><![CDATA[<p>Interesting article explaining how to test HTML with visual CSS highlighting: <a href="https://heydonworks.com/article/testing-html-with-modern-css/" title="Testing HTML with modern CSS: HeydonWorks">Testing HTML with modern CSS</a> (<a href="https://couchblog.de/blog/2024/04/22/links/" title="Links | Couchblog">via</a>)</p>
  3771. ]]></description>
  3772.    <content:encoded><![CDATA[<p>Interesting article explaining how to test HTML with visual CSS highlighting: <a href="https://heydonworks.com/article/testing-html-with-modern-css/" title="Testing HTML with modern CSS: HeydonWorks">Testing HTML with modern CSS</a> (<a href="https://couchblog.de/blog/2024/04/22/links/" title="Links | Couchblog">via</a>)</p>
  3773. ]]></content:encoded>
  3774.  </item>
  3775.  
  3776.  <item>
  3777.    <title>Print HTTP Headers and Pretty-Print JSON Response</title>
  3778.    <link>https://blog.x-way.org/Linux/2024/04/15/Print-HTTP-Headers-and-Pretty-Print-JSON-Response.html</link>
  3779.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324350</guid>
  3780.    <dc:creator>Andreas Jaggi</dc:creator>
  3781.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3782.    <pubDate>Mon, 15 Apr 2024 09:37:00 +0200</pubDate>
  3783.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  3784.    <description><![CDATA[<p>In the <a href="https://susam.net/pretty-print-json-response-with-http-headers.html" title="Print HTTP Headers and Pretty-Print JSON Response - Susam Pal">Print HTTP Headers and Pretty-Print JSON Response</a> post, <a href="https://susam.net/" title="Susam Pal">Susam Pal</a> shows a nice trick to pretty-print JSON output with jq from curl while also showing the HTTP response headers (using stderr):</p>
  3785. <pre>curl -sSD /dev/stderr https://some-URL-returning-JSON | jq .</pre>
  3786. ]]></description>
  3787.    <content:encoded><![CDATA[<p>In the <a href="https://susam.net/pretty-print-json-response-with-http-headers.html" title="Print HTTP Headers and Pretty-Print JSON Response - Susam Pal">Print HTTP Headers and Pretty-Print JSON Response</a> post, <a href="https://susam.net/" title="Susam Pal">Susam Pal</a> shows a nice trick to pretty-print JSON output with jq from curl while also showing the HTTP response headers (using stderr):</p>
  3788. <pre>curl -sSD /dev/stderr https://some-URL-returning-JSON | jq .</pre>
  3789. ]]></content:encoded>
  3790.  </item>
  3791.  
  3792.  <item>
  3793.    <title>Modern Git Commands and Features You Should Be Using</title>
  3794.    <link>https://blog.x-way.org/Coding/2024/04/13/Modern-Git-Commands-and-Features-You-Should-Be-Using.html</link>
  3795.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324349</guid>
  3796.    <dc:creator>Andreas Jaggi</dc:creator>
  3797.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3798.    <pubDate>Sat, 13 Apr 2024 20:37:00 +0200</pubDate>
  3799.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  3800.    <description><![CDATA[<p><a href="https://martinheinz.dev/blog/109" title="Modern Git Commands and Features You Should Be Using | Martin Heinz | Personal Website &amp; Blog">Modern Git Commands and Features You Should Be Using</a> &mdash; a short article from <a href="https://martinheinz.dev/" title="Martin Heinz | Personal Website &amp; Blog">Martin Heinz</a> about some new-ish (&gt;2018) features in <a href="https://git-scm.com/" title="Git">Git</a>, that 'can make your life so much easier'.</p>
  3801. <p>TL;DR:</p>
  3802. <ul>
  3803. <li><code>git switch &lt;branchname&gt;</code></li>
  3804. <li><code>git restore --staged &lt;somefile&gt;</code></li>
  3805. <li><code>git restore --source &lt;commit&gt; &lt;somefile&gt;</code></li>
  3806. <li><code>git sparse-checkout</code></li>
  3807. <li><code>git worktree</code></li>
  3808. <li><code>git bisect</code></li>
  3809. </ul>
  3810. <p>Similar post from five years ago: <a href="https://blog.x-way.org/Coding/2019/05/25/More-productive-Git.html" title="More productive Git - x-log">More productive Git</a></p>
  3811. ]]></description>
  3812.    <content:encoded><![CDATA[<p><a href="https://martinheinz.dev/blog/109" title="Modern Git Commands and Features You Should Be Using | Martin Heinz | Personal Website &amp; Blog">Modern Git Commands and Features You Should Be Using</a> &mdash; a short article from <a href="https://martinheinz.dev/" title="Martin Heinz | Personal Website &amp; Blog">Martin Heinz</a> about some new-ish (&gt;2018) features in <a href="https://git-scm.com/" title="Git">Git</a>, that 'can make your life so much easier'.</p>
  3813. <p>TL;DR:</p>
  3814. <ul>
  3815. <li><code>git switch &lt;branchname&gt;</code></li>
  3816. <li><code>git restore --staged &lt;somefile&gt;</code></li>
  3817. <li><code>git restore --source &lt;commit&gt; &lt;somefile&gt;</code></li>
  3818. <li><code>git sparse-checkout</code></li>
  3819. <li><code>git worktree</code></li>
  3820. <li><code>git bisect</code></li>
  3821. </ul>
  3822. <p>Similar post from five years ago: <a href="https://blog.x-way.org/Coding/2019/05/25/More-productive-Git.html" title="More productive Git - x-log">More productive Git</a></p>
  3823. ]]></content:encoded>
  3824.  </item>
  3825.  
  3826.  <item>
  3827.    <title>NTP IPs</title>
  3828.    <link>https://blog.x-way.org/Networking/2024/04/11/NTP-IPs.html</link>
  3829.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324348</guid>
  3830.    <dc:creator>Andreas Jaggi</dc:creator>
  3831.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3832.    <pubDate>Thu, 11 Apr 2024 21:41:00 +0200</pubDate>
  3833.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  3834.    <description><![CDATA[<p>This <a href="https://rachelbythebay.com/w/2024/04/10/rtc/" title="Going in circles without a real-time clock">post</a> from Rachel, reminded me of my own struggle with a Raspberry Pi and time (and yes, I did run into the same DNSSEC problem).<br>I first tried a RTC shield, but this didn't fully solve all problems.</p>
  3835. <p>My workaround in the end is to use two fixed IP addresses in ntp.conf in additon to the usual pool servers.<br>Thanks ${previous employer} for not changing the IPs of your public NTP servers so far :-)</p>
  3836. ]]></description>
  3837.    <content:encoded><![CDATA[<p>This <a href="https://rachelbythebay.com/w/2024/04/10/rtc/" title="Going in circles without a real-time clock">post</a> from Rachel, reminded me of my own struggle with a Raspberry Pi and time (and yes, I did run into the same DNSSEC problem).<br>I first tried a RTC shield, but this didn't fully solve all problems.</p>
  3838. <p>My workaround in the end is to use two fixed IP addresses in ntp.conf in additon to the usual pool servers.<br>Thanks ${previous employer} for not changing the IPs of your public NTP servers so far :-)</p>
  3839. ]]></content:encoded>
  3840.  </item>
  3841.  
  3842.  <item>
  3843.    <title>Back on native IPv6</title>
  3844.    <link>https://blog.x-way.org/Networking/2024/04/10/Back-on-native-IPv6.html</link>
  3845.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324347</guid>
  3846.    <dc:creator>Andreas Jaggi</dc:creator>
  3847.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3848.    <pubDate>Wed, 10 Apr 2024 20:28:00 +0200</pubDate>
  3849.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  3850.    <description><![CDATA[<p>As hinted at in my <a href="https://blog.x-way.org/Networking/2024/04/10/SixSpotting-still-going-on.html" title="SixSpotting still going on - x-log">previous post</a>, Solnet is delivering native IPv6 Internet again.</p>
  3851. <p>Shortly after 23h on March 26th there was a brief interruption of the Internet uplink and afterwards my router started receiving an IPv6 address again.<br>My <a href="https://blog.x-way.org/Networking/2024/02/25/Tunnelbroker-to-the-rescue.html" title="Tunnelbroker to the rescue - x-log">support ticket with Solnet</a> is still unanswered, but at least IPv6 is back :-)</p>
  3852. ]]></description>
  3853.    <content:encoded><![CDATA[<p>As hinted at in my <a href="https://blog.x-way.org/Networking/2024/04/10/SixSpotting-still-going-on.html" title="SixSpotting still going on - x-log">previous post</a>, Solnet is delivering native IPv6 Internet again.</p>
  3854. <p>Shortly after 23h on March 26th there was a brief interruption of the Internet uplink and afterwards my router started receiving an IPv6 address again.<br>My <a href="https://blog.x-way.org/Networking/2024/02/25/Tunnelbroker-to-the-rescue.html" title="Tunnelbroker to the rescue - x-log">support ticket with Solnet</a> is still unanswered, but at least IPv6 is back :-)</p>
  3855. ]]></content:encoded>
  3856.  </item>
  3857.  
  3858.  <item>
  3859.    <title>SixSpotting still going on</title>
  3860.    <link>https://blog.x-way.org/Networking/2024/04/10/SixSpotting-still-going-on.html</link>
  3861.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324346</guid>
  3862.    <dc:creator>Andreas Jaggi</dc:creator>
  3863.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3864.    <pubDate>Wed, 10 Apr 2024 19:05:00 +0200</pubDate>
  3865.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  3866.    <description><![CDATA[<p>While browsing through the archives I stumbled upon the <a href="https://blog.x-way.org/Networking/2014/11/02/SixSpotting.html" title="SixSpotting - x-log">SixSpotting post</a> from 2014.<br>Turns out <a href="https://game.flyingpenguintech.org/" title="SixSpotting">the game</a> is still working and after some failed attempts I managed to remember my account name and log in.<br>I guess it must look quite strange to see a burst of new checkins after almost 10 years &#x1F604;</p>
  3867. <p><img src="https://blog.x-way.org/images/sixspotting-2024.png" width="420" height="87" alt="My last 5 SixSpotting checkins" /></p>
  3868. ]]></description>
  3869.    <content:encoded><![CDATA[<p>While browsing through the archives I stumbled upon the <a href="https://blog.x-way.org/Networking/2014/11/02/SixSpotting.html" title="SixSpotting - x-log">SixSpotting post</a> from 2014.<br>Turns out <a href="https://game.flyingpenguintech.org/" title="SixSpotting">the game</a> is still working and after some failed attempts I managed to remember my account name and log in.<br>I guess it must look quite strange to see a burst of new checkins after almost 10 years &#x1F604;</p>
  3870. <p><img src="https://blog.x-way.org/images/sixspotting-2024.png" width="420" height="87" alt="My last 5 SixSpotting checkins" /></p>
  3871. ]]></content:encoded>
  3872.  </item>
  3873.  
  3874.  <item>
  3875.    <title>humans.txt</title>
  3876.    <link>https://blog.x-way.org/Webdesign/2024/04/07/humans-txt.html</link>
  3877.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324345</guid>
  3878.    <dc:creator>Andreas Jaggi</dc:creator>
  3879.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3880.    <pubDate>Sun, 07 Apr 2024 19:10:00 +0200</pubDate>
  3881.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  3882.    <description><![CDATA[<p>After following a couple links from the article linked in the previous blogpost, I ended up reading the <a href="https://shellsharks.com/notes/2023/08/15/website-component-checklist" title="Website Component Checklis">Website Component Checklist</a> from <a href="https://shellsharks.com/about" title="Mike Sass">Mike Sass</a>.<br>It provides again a lot of inspiration for things to add to my weblog.<br>What intrigued me today on the list was <a href="https://web.archive.org/web/20240330061550/https://humanstxt.org/" title="Humans TXT: We Are People, Not Machines.">humans.txt</a>, which is an initiative for knowing the people behing a website.</p>
  3883. <p>Thus I've now added the following <a href="https://blog.x-way.org/humans.txt" title="x-log - Humans TXT">humans.txt</a>.</p>
  3884. ]]></description>
  3885.    <content:encoded><![CDATA[<p>After following a couple links from the article linked in the previous blogpost, I ended up reading the <a href="https://shellsharks.com/notes/2023/08/15/website-component-checklist" title="Website Component Checklis">Website Component Checklist</a> from <a href="https://shellsharks.com/about" title="Mike Sass">Mike Sass</a>.<br>It provides again a lot of inspiration for things to add to my weblog.<br>What intrigued me today on the list was <a href="https://web.archive.org/web/20240330061550/https://humanstxt.org/" title="Humans TXT: We Are People, Not Machines.">humans.txt</a>, which is an initiative for knowing the people behing a website.</p>
  3886. <p>Thus I've now added the following <a href="https://blog.x-way.org/humans.txt" title="x-log - Humans TXT">humans.txt</a>.</p>
  3887. ]]></content:encoded>
  3888.  </item>
  3889.  
  3890.  <item>
  3891.    <title>100 more things you can do with your personal website</title>
  3892.    <link>https://blog.x-way.org/Misc/2024/04/07/100-more-things-you-can-do-with-your-personal-website.html</link>
  3893.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324344</guid>
  3894.    <dc:creator>Andreas Jaggi</dc:creator>
  3895.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3896.    <pubDate>Sun, 07 Apr 2024 17:32:00 +0200</pubDate>
  3897.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  3898.    <description><![CDATA[<p><a href="https://jamesg.blog/2024/03/10/100-more-personal-website-ideas/" title="100 (more) things you can do with your personal website | James' Coffee Blog">100 more things you can do with your personal website</a> &mdash; a follow-up to the <a href="https://blog.x-way.org/Misc/2024/03/07/100-things-you-can-do-on-your-personal-website.html" title="x-log - 100 things you can do on your personal website">popular post</a> from last month :-)</p>
  3899. ]]></description>
  3900.    <content:encoded><![CDATA[<p><a href="https://jamesg.blog/2024/03/10/100-more-personal-website-ideas/" title="100 (more) things you can do with your personal website | James' Coffee Blog">100 more things you can do with your personal website</a> &mdash; a follow-up to the <a href="https://blog.x-way.org/Misc/2024/03/07/100-things-you-can-do-on-your-personal-website.html" title="x-log - 100 things you can do on your personal website">popular post</a> from last month :-)</p>
  3901. ]]></content:encoded>
  3902.  </item>
  3903.  
  3904.  <item>
  3905.    <title>Dog Poo Golf</title>
  3906.    <link>https://blog.x-way.org/Misc/2024/04/03/Dog-Poo-Golf.html</link>
  3907.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324343</guid>
  3908.    <dc:creator>Andreas Jaggi</dc:creator>
  3909.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3910.    <pubDate>Wed, 03 Apr 2024 08:03:00 +0200</pubDate>
  3911.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  3912.    <description><![CDATA[<p><img src="https://blog.x-way.org/images/dog-poo-golf.png" width="480" height="347" alt="Dog Poo Golf start screen" /></p>
  3913. <p><a href="https://vole.wtf/dog-poo-golf/" title="Dog Poo Golf &#x1F436;&#x1F4A9;&#x26F3;">Dog Poo Golf</a>, a Wii Sports Golf-style browser game (with the music!) where you fling dog poop bags into a garbage can. &#x1F436;&#x1F4A9;&#x26F3; (<a href="https://kottke.org/24/04/0044297-dog-poo-golf-a-wii" title="kottke.org - Dog Poo Golf">via kottke.org</a>)</p>
  3914. ]]></description>
  3915.    <content:encoded><![CDATA[<p><img src="https://blog.x-way.org/images/dog-poo-golf.png" width="480" height="347" alt="Dog Poo Golf start screen" /></p>
  3916. <p><a href="https://vole.wtf/dog-poo-golf/" title="Dog Poo Golf &#x1F436;&#x1F4A9;&#x26F3;">Dog Poo Golf</a>, a Wii Sports Golf-style browser game (with the music!) where you fling dog poop bags into a garbage can. &#x1F436;&#x1F4A9;&#x26F3; (<a href="https://kottke.org/24/04/0044297-dog-poo-golf-a-wii" title="kottke.org - Dog Poo Golf">via kottke.org</a>)</p>
  3917. ]]></content:encoded>
  3918.  </item>
  3919.  
  3920.  <item>
  3921.    <title>Puppet updated!</title>
  3922.    <link>https://blog.x-way.org/Linux/2024/03/30/Puppet-updated.html</link>
  3923.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324342</guid>
  3924.    <dc:creator>Andreas Jaggi</dc:creator>
  3925.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3926.    <pubDate>Sat, 30 Mar 2024 13:03:00 +0100</pubDate>
  3927.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  3928.    <description><![CDATA[<p>Yay! Successfully updated my <a href="https://www.puppet.com/docs/puppet/8/server/about_server.html" title="About Puppet Server">Puppet Server</a> setup from 5.3.7 to 8.4.0 &#x1f389;</p>
  3929. <p>It was quite a step (5.3.7 was released in January 2019) and as expected 3 major version bumps came with a couple changes.</p>
  3930. <p>I opted to re-create the PuppetDB and CA stores from scratch (to avoid having to migrate 5 years of data schema changes, and the CA cert is now also valid for a couple more years again).</p>
  3931. <p>To make the old manifests and modules work with the new versions, quite some effort was needed. This included rewriting some no longer maintained modules to use newer stdlib and concat libraries, updating a couple modules from the puppet forge (with the bonus that my puppet server runs airgapped and I had to use the download-tar-copy-extract way to install them) and fixing no longer valid syntax here and there in my custom manifests. Overall I spent about 5 hours on it (and have now a recurring reminder to update puppet more often to make this process less painful).</p>
  3932. <p>Helpful as usual were the resources from <a href="https://voxpupuli.org/" title="Vox Pupuli">Vox Pupuli</a>, in particular the <a href="https://hub.docker.com/r/voxpupuli/container-puppetserver" title="Voxpupuli Puppet Server container">Puppet Server</a> and <a href="https://hub.docker.com/r/voxpupuli/container-puppetdb" title="Voxpupuli PuppetDB container">PuppetDB</a> Docker images and the <a href="https://github.com/voxpupuli/crafty/" title="voxpupuli/crafty: CRAFTY - Containerized Resources And Funky Tools (in) YAML">CRAFTY repo</a> which contains a fully self-contained Docker Compose setup very similar to what I'm running.</p>
  3933. <p>Some commands that came in handy:</p>
  3934. <p><code>puppet config print ssldir --section agent</code><br>
  3935. Returns the path of the TLS config folder on the client. Useful during a CA change (where you <code>rm -rf</code> the whole folder and then request a new TLS certificate).</p>
  3936. <p><code>puppet agent -t --noop</code><br>
  3937. Dry-run the changes on the client (it does request a new TLS cert though!). Shows a nice diff of the changes it would do to files, helpful to validate that a manifest still behaves the same in the new version.</p>
  3938. ]]></description>
  3939.    <content:encoded><![CDATA[<p>Yay! Successfully updated my <a href="https://www.puppet.com/docs/puppet/8/server/about_server.html" title="About Puppet Server">Puppet Server</a> setup from 5.3.7 to 8.4.0 &#x1f389;</p>
  3940. <p>It was quite a step (5.3.7 was released in January 2019) and as expected 3 major version bumps came with a couple changes.</p>
  3941. <p>I opted to re-create the PuppetDB and CA stores from scratch (to avoid having to migrate 5 years of data schema changes, and the CA cert is now also valid for a couple more years again).</p>
  3942. <p>To make the old manifests and modules work with the new versions, quite some effort was needed. This included rewriting some no longer maintained modules to use newer stdlib and concat libraries, updating a couple modules from the puppet forge (with the bonus that my puppet server runs airgapped and I had to use the download-tar-copy-extract way to install them) and fixing no longer valid syntax here and there in my custom manifests. Overall I spent about 5 hours on it (and have now a recurring reminder to update puppet more often to make this process less painful).</p>
  3943. <p>Helpful as usual were the resources from <a href="https://voxpupuli.org/" title="Vox Pupuli">Vox Pupuli</a>, in particular the <a href="https://hub.docker.com/r/voxpupuli/container-puppetserver" title="Voxpupuli Puppet Server container">Puppet Server</a> and <a href="https://hub.docker.com/r/voxpupuli/container-puppetdb" title="Voxpupuli PuppetDB container">PuppetDB</a> Docker images and the <a href="https://github.com/voxpupuli/crafty/" title="voxpupuli/crafty: CRAFTY - Containerized Resources And Funky Tools (in) YAML">CRAFTY repo</a> which contains a fully self-contained Docker Compose setup very similar to what I'm running.</p>
  3944. <p>Some commands that came in handy:</p>
  3945. <p><code>puppet config print ssldir --section agent</code><br>
  3946. Returns the path of the TLS config folder on the client. Useful during a CA change (where you <code>rm -rf</code> the whole folder and then request a new TLS certificate).</p>
  3947. <p><code>puppet agent -t --noop</code><br>
  3948. Dry-run the changes on the client (it does request a new TLS cert though!). Shows a nice diff of the changes it would do to files, helpful to validate that a manifest still behaves the same in the new version.</p>
  3949. ]]></content:encoded>
  3950.  </item>
  3951.  
  3952.  <item>
  3953.    <title>Linux Crisis Tools</title>
  3954.    <link>https://blog.x-way.org/Linux/2024/03/25/Linux-Crisis-Tools.html</link>
  3955.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324341</guid>
  3956.    <dc:creator>Andreas Jaggi</dc:creator>
  3957.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  3958.    <pubDate>Mon, 25 Mar 2024 21:45:00 +0100</pubDate>
  3959.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  3960.    <description><![CDATA[<p><a href="https://www.brendangregg.com/" title="Brendan Gregg's Homepage">Brendan Gregg</a> posted the following <a href="https://www.brendangregg.com/blog/2024-03-24/linux-crisis-tools.html" title="Linux Crisis Tools">list of 'crisis tools'</a> which you should install on your Linux servers by default (so they are available when an incident happens).</p>
  3961. <table>
  3962. <tr><th>Package</th><th>Provides</th><th>Notes</th></tr>
  3963. <tr><td>procps</td><td>ps(1), vmstat(8), uptime(1), top(1)</td><td>basic stats</td></tr>
  3964. <tr><td>util-linux</td><td>dmesg(1), lsblk(1), lscpu(1)</td><td>system log, device info</td></tr>
  3965. <tr><td>sysstat</td><td>iostat(1), mpstat(1), pidstat(1), sar(1)</td><td>device stats</td></tr>
  3966. <tr><td>iproute2</td><td>ip(8), ss(8), nstat(8), tc(8)</td><td>preferred net tools</td></tr>
  3967. <tr><td>numactl</td><td>numastat(8)</td><td>NUMA stats</td></tr>
  3968. <tr><td>tcpdump</td><td>tcpdump(8)</td><td>Network sniffer</td></tr>
  3969. <tr><td>linux-tools-common<br>linux-tools-$(uname -r)</td><td>perf(1), turbostat(8)</td><td>profiler and PMU stats</td></tr>
  3970. <tr><td>bpfcc-tools (bcc)</td><td>opensnoop(8), execsnoop(8), runqlat(8), softirqs(8),<br>hardirqs(8), ext4slower(8), ext4dist(8), biotop(8),<br>biosnoop(8), biolatency(8), tcptop(8), tcplife(8),<br>trace(8), argdist(8), funccount(8), profile(8), etc.</td><td>canned eBPF tools[1]</td></tr>
  3971. <tr><td>bpftrace</td><td>bpftrace, basic versions of opensnoop(8),<br>execsnoop(8), runqlat(8), biosnoop(8), etc.</td><td>eBPF scripting[1]</td></tr>
  3972. <tr><td>trace-cmd</td><td>trace-cmd(1)</td><td>Ftrace CLI</td></tr>
  3973. <tr><td>nicstat</td><td>nicstat(1)</td><td>net device stats</td></tr>
  3974. <tr><td>ethtool</td><td>ethtool(8)</td><td>net device info</td></tr>
  3975. <tr><td>tiptop</td><td>tiptop(1)</td><td>PMU/PMC top</td></tr>
  3976. <tr><td>cpuid</td><td>cpuid(1)</td><td>CPU details</td></tr>
  3977. <tr><td>msr-tools</td><td>rdmsr(8), wrmsr(8)</td><td>CPU digging</td></tr>
  3978. </table>
  3979. ]]></description>
  3980.    <content:encoded><![CDATA[<p><a href="https://www.brendangregg.com/" title="Brendan Gregg's Homepage">Brendan Gregg</a> posted the following <a href="https://www.brendangregg.com/blog/2024-03-24/linux-crisis-tools.html" title="Linux Crisis Tools">list of 'crisis tools'</a> which you should install on your Linux servers by default (so they are available when an incident happens).</p>
  3981. <table>
  3982. <tr><th>Package</th><th>Provides</th><th>Notes</th></tr>
  3983. <tr><td>procps</td><td>ps(1), vmstat(8), uptime(1), top(1)</td><td>basic stats</td></tr>
  3984. <tr><td>util-linux</td><td>dmesg(1), lsblk(1), lscpu(1)</td><td>system log, device info</td></tr>
  3985. <tr><td>sysstat</td><td>iostat(1), mpstat(1), pidstat(1), sar(1)</td><td>device stats</td></tr>
  3986. <tr><td>iproute2</td><td>ip(8), ss(8), nstat(8), tc(8)</td><td>preferred net tools</td></tr>
  3987. <tr><td>numactl</td><td>numastat(8)</td><td>NUMA stats</td></tr>
  3988. <tr><td>tcpdump</td><td>tcpdump(8)</td><td>Network sniffer</td></tr>
  3989. <tr><td>linux-tools-common<br>linux-tools-$(uname -r)</td><td>perf(1), turbostat(8)</td><td>profiler and PMU stats</td></tr>
  3990. <tr><td>bpfcc-tools (bcc)</td><td>opensnoop(8), execsnoop(8), runqlat(8), softirqs(8),<br>hardirqs(8), ext4slower(8), ext4dist(8), biotop(8),<br>biosnoop(8), biolatency(8), tcptop(8), tcplife(8),<br>trace(8), argdist(8), funccount(8), profile(8), etc.</td><td>canned eBPF tools[1]</td></tr>
  3991. <tr><td>bpftrace</td><td>bpftrace, basic versions of opensnoop(8),<br>execsnoop(8), runqlat(8), biosnoop(8), etc.</td><td>eBPF scripting[1]</td></tr>
  3992. <tr><td>trace-cmd</td><td>trace-cmd(1)</td><td>Ftrace CLI</td></tr>
  3993. <tr><td>nicstat</td><td>nicstat(1)</td><td>net device stats</td></tr>
  3994. <tr><td>ethtool</td><td>ethtool(8)</td><td>net device info</td></tr>
  3995. <tr><td>tiptop</td><td>tiptop(1)</td><td>PMU/PMC top</td></tr>
  3996. <tr><td>cpuid</td><td>cpuid(1)</td><td>CPU details</td></tr>
  3997. <tr><td>msr-tools</td><td>rdmsr(8), wrmsr(8)</td><td>CPU digging</td></tr>
  3998. </table>
  3999. ]]></content:encoded>
  4000.  </item>
  4001.  
  4002.  <item>
  4003.    <title>Installing the AREDN firmware on a MikroTik hAP ac lite</title>
  4004.    <link>https://blog.x-way.org/Radio/2024/03/24/Installing-the-AREDN-firmware-on-a-MikroTik-hAP-ac-lite.html</link>
  4005.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324340</guid>
  4006.    <dc:creator>Andreas Jaggi</dc:creator>
  4007.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4008.    <pubDate>Sun, 24 Mar 2024 14:26:00 +0100</pubDate>
  4009.    <category domain="https://blog.x-way.org/Radio/">Radio</category>
  4010.    <description><![CDATA[<p>At the recent <a href="http://hb9tf.ch" title="Tango Foxtrott Wireless Society HB9TF">HB9TF</a> AGM fellow radio amateur <a href="https://medium.com/@hb9gvm" title="Martin Suess (HB9GVM)">HB9GVM</a> gave an introductory presentation about <a href="https://www.arednmesh.org/" title="Amateur Radio Emergency Data Network">AREDN</a>.</p>
  4011. <p>Motivated by this, I ordered a <a href="https://mikrotik.com/product/RB952Ui-5ac2nD" title="MikroTik hAP ac lite">MikroTik hAP ac lite</a> and installed the AREDN firmware on it.<br>The following are my notes of the installation process.</p>
  4012. <ol>
  4013. <li>Download the firmware images for the MikroTik hAP ac lite from <a href="http://downloads.arednmesh.org/afs/www/" title="AREDN Firmware Selector">http://downloads.arednmesh.org/afs/www/</a> (both the *kernel.bin and *sysupgrade.bin are needed)</li>
  4014. <li>Install <a href="https://thekelleys.org.uk/dnsmasq/doc.html" title="Dnsmasq - network services for small networks">Dnsmasq</a> as a PXE server on Mac OS: <pre>brew install dnsmasq</pre></li>
  4015. <li>Setup the *kernel.bin for PXE: <pre>mkdir tftp-root
  4016. cp $HOME/Downloads/aredn-3.23.12.0-ath79-mikrotik-mikrotik_routerboard-952ui-5ac2nd-initramfs-kernel.bin tftp-root/rb.elf</pre></li>
  4017. <li>Connect a Ethernet dongle and configure it with this static IP: 192.168.1.10/24</li>
  4018. <li>Run dnsmasq as a PXE server listening on the network interface of the Ethernet dongle: <pre>ifconfig en6 # use to check that IP is configured
  4019. sudo dnsmasq -i en6 -u $(whoami) --log-dhcp --bootp-dynamic --dhcp-range=192.168.1.100,192.168.1.200 -d -p0 -K --dhcp-boot=rb.elf --enable-tftp --tftp-root=$(pwd)/tftp-root/</pre></li>
  4020. <li>Power off the hAP ac lite and connect the Ethernet dongle to port 1 (<strong>PXE booting only seems to work on this port!</strong>)</li>
  4021. <li>Press the reset button on the hAP ac lite, power it on and keep the button pressed for about 20 seconds (there is some output of dnsmask once the PXE booting is in progress)</li>
  4022. <li>Wait until the hAP ac lite stops blinking and the LEDs are steady again (it also issues a new DHCP request via port1, but this time no PXE booting).</li>
  4023. <li>Move the cable to port 2 (the AREDN default config for the MikroTik hAP ac lite uses port 1 for the Internet uplink, and port 2 for the 'inside' local network).</li>
  4024. <li>Test that you can ping the inside IP of the AREDN node: <pre>ping 192.168.1.1</pre></li>
  4025. <li>Open the admin page on <code>http://192.168.1.1/cgi-bin/admin</code> (Username is <code>root</code> and password is <code>hsmm</code>).</li>
  4026. <li>In the Firmware Update section, click on 'Upload Firmware' and select the previously downloaded sysupgrade.bin file.</li>
  4027. <li>Wait until a reboot has happened twice (it takes a couple minutes!) to complete the installation.</li>
  4028. <li>Open <code>http://192.168.1.1</code> &ndash; congratulations, you now have a freshly installed (and not yet configured) AREDN node :-)</li>
  4029. </ol>
  4030. ]]></description>
  4031.    <content:encoded><![CDATA[<p>At the recent <a href="http://hb9tf.ch" title="Tango Foxtrott Wireless Society HB9TF">HB9TF</a> AGM fellow radio amateur <a href="https://medium.com/@hb9gvm" title="Martin Suess (HB9GVM)">HB9GVM</a> gave an introductory presentation about <a href="https://www.arednmesh.org/" title="Amateur Radio Emergency Data Network">AREDN</a>.</p>
  4032. <p>Motivated by this, I ordered a <a href="https://mikrotik.com/product/RB952Ui-5ac2nD" title="MikroTik hAP ac lite">MikroTik hAP ac lite</a> and installed the AREDN firmware on it.<br>The following are my notes of the installation process.</p>
  4033. <ol>
  4034. <li>Download the firmware images for the MikroTik hAP ac lite from <a href="http://downloads.arednmesh.org/afs/www/" title="AREDN Firmware Selector">http://downloads.arednmesh.org/afs/www/</a> (both the *kernel.bin and *sysupgrade.bin are needed)</li>
  4035. <li>Install <a href="https://thekelleys.org.uk/dnsmasq/doc.html" title="Dnsmasq - network services for small networks">Dnsmasq</a> as a PXE server on Mac OS: <pre>brew install dnsmasq</pre></li>
  4036. <li>Setup the *kernel.bin for PXE: <pre>mkdir tftp-root
  4037. cp $HOME/Downloads/aredn-3.23.12.0-ath79-mikrotik-mikrotik_routerboard-952ui-5ac2nd-initramfs-kernel.bin tftp-root/rb.elf</pre></li>
  4038. <li>Connect a Ethernet dongle and configure it with this static IP: 192.168.1.10/24</li>
  4039. <li>Run dnsmasq as a PXE server listening on the network interface of the Ethernet dongle: <pre>ifconfig en6 # use to check that IP is configured
  4040. sudo dnsmasq -i en6 -u $(whoami) --log-dhcp --bootp-dynamic --dhcp-range=192.168.1.100,192.168.1.200 -d -p0 -K --dhcp-boot=rb.elf --enable-tftp --tftp-root=$(pwd)/tftp-root/</pre></li>
  4041. <li>Power off the hAP ac lite and connect the Ethernet dongle to port 1 (<strong>PXE booting only seems to work on this port!</strong>)</li>
  4042. <li>Press the reset button on the hAP ac lite, power it on and keep the button pressed for about 20 seconds (there is some output of dnsmask once the PXE booting is in progress)</li>
  4043. <li>Wait until the hAP ac lite stops blinking and the LEDs are steady again (it also issues a new DHCP request via port1, but this time no PXE booting).</li>
  4044. <li>Move the cable to port 2 (the AREDN default config for the MikroTik hAP ac lite uses port 1 for the Internet uplink, and port 2 for the 'inside' local network).</li>
  4045. <li>Test that you can ping the inside IP of the AREDN node: <pre>ping 192.168.1.1</pre></li>
  4046. <li>Open the admin page on <code>http://192.168.1.1/cgi-bin/admin</code> (Username is <code>root</code> and password is <code>hsmm</code>).</li>
  4047. <li>In the Firmware Update section, click on 'Upload Firmware' and select the previously downloaded sysupgrade.bin file.</li>
  4048. <li>Wait until a reboot has happened twice (it takes a couple minutes!) to complete the installation.</li>
  4049. <li>Open <code>http://192.168.1.1</code> &ndash; congratulations, you now have a freshly installed (and not yet configured) AREDN node :-)</li>
  4050. </ol>
  4051. ]]></content:encoded>
  4052.  </item>
  4053.  
  4054.  <item>
  4055.    <title>Fifty Things you can do with a Software Defined Radio 📻</title>
  4056.    <link>https://blog.x-way.org/Radio/2024/03/17/Fifty-Things-you-can-do-with-a-Software-Defined-Radio.html</link>
  4057.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324339</guid>
  4058.    <dc:creator>Andreas Jaggi</dc:creator>
  4059.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4060.    <pubDate>Sun, 17 Mar 2024 09:50:00 +0100</pubDate>
  4061.    <category domain="https://blog.x-way.org/Radio/">Radio</category>
  4062.    <description><![CDATA[<p><a href="https://blinry.org/50-things-with-sdr/" title="Fifty Things you can do with a Software Defined Radio">Fifty Things you can do with a Software Defined Radio 📻</a> &mdash; some cool SDR things to do (have done already some of them and more with my <a href="http://hb9tf.ch" title="Tango Foxtrott Wireless Society HB9TF">HB9TF</a> friends :-)</p>
  4063. <p>(<a href="https://news.ycombinator.com/item?id=39728153" title="Fifty Things you can do with a Software Defined Radio | Hacker News">via</a>)</p>
  4064. <p>Also using this post to introduce a new category: <b><a href="https://blog.x-way.org/Radio/" title="x-log - Radio">Radio</a></b><br>
  4065. Which will serve as a container for radio/HAM/Wireless related content.</p>
  4066. ]]></description>
  4067.    <content:encoded><![CDATA[<p><a href="https://blinry.org/50-things-with-sdr/" title="Fifty Things you can do with a Software Defined Radio">Fifty Things you can do with a Software Defined Radio 📻</a> &mdash; some cool SDR things to do (have done already some of them and more with my <a href="http://hb9tf.ch" title="Tango Foxtrott Wireless Society HB9TF">HB9TF</a> friends :-)</p>
  4068. <p>(<a href="https://news.ycombinator.com/item?id=39728153" title="Fifty Things you can do with a Software Defined Radio | Hacker News">via</a>)</p>
  4069. <p>Also using this post to introduce a new category: <b><a href="https://blog.x-way.org/Radio/" title="x-log - Radio">Radio</a></b><br>
  4070. Which will serve as a container for radio/HAM/Wireless related content.</p>
  4071. ]]></content:encoded>
  4072.  </item>
  4073.  
  4074.  <item>
  4075.    <title>100 things you can do on your personal website</title>
  4076.    <link>https://blog.x-way.org/Misc/2024/03/07/100-things-you-can-do-on-your-personal-website.html</link>
  4077.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324338</guid>
  4078.    <dc:creator>Andreas Jaggi</dc:creator>
  4079.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4080.    <pubDate>Thu, 07 Mar 2024 23:56:00 +0100</pubDate>
  4081.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  4082.    <description><![CDATA[<p><a href="https://jamesg.blog/2024/02/19/personal-website-ideas/" title="100 things you can do on your personal website | James' Coffee Blog">100 things you can do on your personal website</a> &mdash; lots of ideas/inspirations also for this blog :-)</p>
  4083. <p>(<a href="https://gigold.me/blog/100-dinge" title="">via</a>)</p>
  4084. ]]></description>
  4085.    <content:encoded><![CDATA[<p><a href="https://jamesg.blog/2024/02/19/personal-website-ideas/" title="100 things you can do on your personal website | James' Coffee Blog">100 things you can do on your personal website</a> &mdash; lots of ideas/inspirations also for this blog :-)</p>
  4086. <p>(<a href="https://gigold.me/blog/100-dinge" title="">via</a>)</p>
  4087. ]]></content:encoded>
  4088.  </item>
  4089.  
  4090.  <item>
  4091.    <title>Tunnelbroker to the rescue</title>
  4092.    <link>https://blog.x-way.org/Networking/2024/02/25/Tunnelbroker-to-the-rescue.html</link>
  4093.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324337</guid>
  4094.    <dc:creator>Andreas Jaggi</dc:creator>
  4095.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4096.    <pubDate>Sun, 25 Feb 2024 15:25:00 +0100</pubDate>
  4097.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  4098.    <description><![CDATA[<p>After nicely delivering <a href="https://blog.x-way.org/Networking/2021/02/04/Embracing-the-future-with-SolNet.html" title="x-log - Embracing the future with Solnet">native IPv6 connectivity for 3 years</a>, my Internet provider Solnet made some changes in their backbone config on January 31st which broke their IPv6 setup.<br>Unfortunately escalating with their support did not bear any fruits so far (current state: they no longer respond on the support ticket&hellip;).</p>
  4099. <p>Thus change of plans, <a href="https://tunnelbroker.net/" title="Hurricane Electric Free IPv6 Tunnel Broker">tunnelbroker.net</a> (Hurricane Electric) to the rescue.<br>Took about 10 minutes to set everything up and now I'm enjoying IPv6 connectivity again (although with a reduced end-to-end MTU due to the <a href="https://en.wikipedia.org/wiki/6in4" title="6in4 - Wikipedia">6in4</a> encapsulation).</p>
  4100. <p>Guess I'll have to look for a different Internet provider again.<br>Especially annoying is that I renewed the yearly plan with Solnet only a couple weeks ago, so will be stuck without native IPv6 connectivity for the next 11 months :-(</p>
  4101. ]]></description>
  4102.    <content:encoded><![CDATA[<p>After nicely delivering <a href="https://blog.x-way.org/Networking/2021/02/04/Embracing-the-future-with-SolNet.html" title="x-log - Embracing the future with Solnet">native IPv6 connectivity for 3 years</a>, my Internet provider Solnet made some changes in their backbone config on January 31st which broke their IPv6 setup.<br>Unfortunately escalating with their support did not bear any fruits so far (current state: they no longer respond on the support ticket&hellip;).</p>
  4103. <p>Thus change of plans, <a href="https://tunnelbroker.net/" title="Hurricane Electric Free IPv6 Tunnel Broker">tunnelbroker.net</a> (Hurricane Electric) to the rescue.<br>Took about 10 minutes to set everything up and now I'm enjoying IPv6 connectivity again (although with a reduced end-to-end MTU due to the <a href="https://en.wikipedia.org/wiki/6in4" title="6in4 - Wikipedia">6in4</a> encapsulation).</p>
  4104. <p>Guess I'll have to look for a different Internet provider again.<br>Especially annoying is that I renewed the yearly plan with Solnet only a couple weeks ago, so will be stuck without native IPv6 connectivity for the next 11 months :-(</p>
  4105. ]]></content:encoded>
  4106.  </item>
  4107.  
  4108.  <item>
  4109.    <title>The High-Risk Refactoring</title>
  4110.    <link>https://blog.x-way.org/Coding/2024/02/25/The-High-Risk-Refactoring.html</link>
  4111.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324336</guid>
  4112.    <dc:creator>Andreas Jaggi</dc:creator>
  4113.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4114.    <pubDate>Sun, 25 Feb 2024 04:02:00 +0100</pubDate>
  4115.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  4116.    <description><![CDATA[<p>In the <a href="https://webup.org/blog/the-high-risk-refactoring/" title="The High-Risk Refactoring - Miroslav Nikolov">The High-Risk Refactoring</a> article there is this concise <em>Addressing Risk</em> checklist to keep in mind when refactoring.<br>During past refactorings (also low-risk ones) I often used almost the same guidelines to help me and can only recommend you to do the same:</p>
  4117. <blockquote cite="https://webup.org/blog/the-high-risk-refactoring/">
  4118. <p>✅ Define constraints. <em>How far should I go</em>. <br>
  4119. ✅ Isolate improvements from features. <em>Do not apply them simultaneously</em>. <br>
  4120. ✅ Write extensive tests. <em>Higher level (integration) with fewer implementation details. They should run alongside changes</em>. <br>
  4121. ✅ Have a visual confirmation. <em>Open the browser</em>.</p>
  4122. <p>❌ Do not skip tests. <em>Don't be lazy</em>.<br>
  4123. ❌ Do not rely too much on code reviews and QA. <em>Humans make mistakes</em>.<br>
  4124. ❌ Do not mix expensive cleanups with other changes. <em>But do that for small improvements</em>.</p>
  4125. </blockquote>
  4126. <p>(<a href="https://labnotes.org/weekend-reading-places-where-ive-lost-my-glasses/" title="Weekend Reading - Places where I've lost my glasses - Labnotes (by Assaf Arkin)">via</a>)</p>
  4127. ]]></description>
  4128.    <content:encoded><![CDATA[<p>In the <a href="https://webup.org/blog/the-high-risk-refactoring/" title="The High-Risk Refactoring - Miroslav Nikolov">The High-Risk Refactoring</a> article there is this concise <em>Addressing Risk</em> checklist to keep in mind when refactoring.<br>During past refactorings (also low-risk ones) I often used almost the same guidelines to help me and can only recommend you to do the same:</p>
  4129. <blockquote cite="https://webup.org/blog/the-high-risk-refactoring/">
  4130. <p>✅ Define constraints. <em>How far should I go</em>. <br>
  4131. ✅ Isolate improvements from features. <em>Do not apply them simultaneously</em>. <br>
  4132. ✅ Write extensive tests. <em>Higher level (integration) with fewer implementation details. They should run alongside changes</em>. <br>
  4133. ✅ Have a visual confirmation. <em>Open the browser</em>.</p>
  4134. <p>❌ Do not skip tests. <em>Don't be lazy</em>.<br>
  4135. ❌ Do not rely too much on code reviews and QA. <em>Humans make mistakes</em>.<br>
  4136. ❌ Do not mix expensive cleanups with other changes. <em>But do that for small improvements</em>.</p>
  4137. </blockquote>
  4138. <p>(<a href="https://labnotes.org/weekend-reading-places-where-ive-lost-my-glasses/" title="Weekend Reading - Places where I've lost my glasses - Labnotes (by Assaf Arkin)">via</a>)</p>
  4139. ]]></content:encoded>
  4140.  </item>
  4141.  
  4142.  <item>
  4143.    <title>Please Blog</title>
  4144.    <link>https://blog.x-way.org/Misc/2024/02/25/Please-Blog.html</link>
  4145.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324335</guid>
  4146.    <dc:creator>Andreas Jaggi</dc:creator>
  4147.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4148.    <pubDate>Sun, 25 Feb 2024 03:17:00 +0100</pubDate>
  4149.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  4150.    <description><![CDATA[<p><a href="https://ultreia.me/blog/please-blog/" title="ultreia.me - PLEASE Blog">Please Blog</a> &mdash; <em>a plea for less Big Web and more Small Web</em> and an encouraging article to write your own blog. It also touches on the part about writing on your own domain (so to keep your content yours and not be at risk of a third-party commercial 'social' service going away).</p>
  4151. <blockquote cite="https://ultreia.me/blog/please-blog/"><p>Don’t wait for the Pulitzer piece. Tell me about your ride to work, about your food, what flavor ice cream you like. Let me be part of happiness and sadness. Show me, that there is a human being out there that, agree or not, I can relate to. Because without it, we are just actors in a sea of actors, marketing, proselytizing, advocating, and threatening towards each other in an always vicious circle of striving for a relevance that only buys us more marketing, more proselytizing, more advocating, and more threats.</p></blockquote>
  4152. <p>(discovered via <a href="https://gigold.me/blog/links-links-links" title="Links, Links, Links | Thomas Gigold - Blog">Thomas Gigold</a>)</p>
  4153. ]]></description>
  4154.    <content:encoded><![CDATA[<p><a href="https://ultreia.me/blog/please-blog/" title="ultreia.me - PLEASE Blog">Please Blog</a> &mdash; <em>a plea for less Big Web and more Small Web</em> and an encouraging article to write your own blog. It also touches on the part about writing on your own domain (so to keep your content yours and not be at risk of a third-party commercial 'social' service going away).</p>
  4155. <blockquote cite="https://ultreia.me/blog/please-blog/"><p>Don’t wait for the Pulitzer piece. Tell me about your ride to work, about your food, what flavor ice cream you like. Let me be part of happiness and sadness. Show me, that there is a human being out there that, agree or not, I can relate to. Because without it, we are just actors in a sea of actors, marketing, proselytizing, advocating, and threatening towards each other in an always vicious circle of striving for a relevance that only buys us more marketing, more proselytizing, more advocating, and more threats.</p></blockquote>
  4156. <p>(discovered via <a href="https://gigold.me/blog/links-links-links" title="Links, Links, Links | Thomas Gigold - Blog">Thomas Gigold</a>)</p>
  4157. ]]></content:encoded>
  4158.  </item>
  4159.  
  4160.  <item>
  4161.    <title>ads.txt</title>
  4162.    <link>https://blog.x-way.org/Webdesign/2024/02/18/ads-txt.html</link>
  4163.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324334</guid>
  4164.    <dc:creator>Andreas Jaggi</dc:creator>
  4165.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4166.    <pubDate>Sun, 18 Feb 2024 17:38:00 +0100</pubDate>
  4167.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  4168.    <description><![CDATA[<p>Added and <a href="https://iabtechlab.com/ads.txt/" title="IAB Tech Lab - Ads.txt - Authorized Digital Sellers">ads.txt</a> file to the blog. The idea is to avoid that someone can sell fake advertisment space for this blog.</p>
  4169. <p>As I don't use any advertisment here the content of the file is pretty basic:</p>
  4170. <pre>contact=https://blog.x-way.org/about.html</pre>
  4171. ]]></description>
  4172.    <content:encoded><![CDATA[<p>Added and <a href="https://iabtechlab.com/ads.txt/" title="IAB Tech Lab - Ads.txt - Authorized Digital Sellers">ads.txt</a> file to the blog. The idea is to avoid that someone can sell fake advertisment space for this blog.</p>
  4173. <p>As I don't use any advertisment here the content of the file is pretty basic:</p>
  4174. <pre>contact=https://blog.x-way.org/about.html</pre>
  4175. ]]></content:encoded>
  4176.  </item>
  4177.  
  4178.  <item>
  4179.    <title>ldapauth</title>
  4180.    <link>https://blog.x-way.org/Linux/2024/02/18/ldapauth.html</link>
  4181.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324333</guid>
  4182.    <dc:creator>Andreas Jaggi</dc:creator>
  4183.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4184.    <pubDate>Sun, 18 Feb 2024 15:37:00 +0100</pubDate>
  4185.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  4186.    <description><![CDATA[<p><a href="https://github.com/x-way/ldapauth" title="x-way/ldapauth">ldapauth</a> is a <a href="https://nodejs.org" title="Node.js">Node.js</a> script which I have been using for the last 12+ years mostly unchanged.</p>
  4187. <p>It started its life in a <a href="https://en.wikipedia.org/wiki/LXC" title="Linux Containers (LXC)">LXC</a> container, eventually was moved to a Docker container and recently ended up in its own repository on GitHub.</p>
  4188. <p>The functionality it provides is not extraordinary, but helped to bridge a gap where no other product was available.<br>
  4189. It talks <a href="https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol" title="Lightweight Directory Access Protocol - Wikipedia">LDAP</a> one one side (although limited to handle user lookup requests) and on the other side connects to a <a href="https://www.mongodb.com/" title="MongoDB - Document Oriented Database">MongoDB</a> database where the information is stored.</p>
  4190. <p>It emerged out of the desire to have an easy way to manage individual user accounts for my home WiFi. I already had MongoDB running for some other personal project and simply added the list of users there (including the UI for managing them).<br>
  4191. Thus the missing part was to get the WiFi accesspoint to lookup user accounts in MongoDB.</p>
  4192. <p>Of course WiFi accesspoints do not directly talk MongoDB, but rather some other protocol like <a href="https://en.wikipedia.org/wiki/RADIUS" title="Remote Authentication Dial-In User Service">RADIUS</a>.<br>
  4193. A <a href="https://freeradius.org/" title="FreeRADIUS">freeradius</a> server was quickly setup, but still couldn't talk to MongoDB at the time. Thus comes in <a href="https://github.com/x-way/ldapauth" title="x-way/ldapauth">ldapauth</a>, which takes LDAP queries from freeradius and turns them into MongoDB lookups so that in the end the WiFi accesspoint receives the user accounts :-)</p>
  4194. <p>Not sure if this is particularly useful for anyone else, but at least here it did provide good services (and continues to do so).<br>
  4195. Current score is that it has survived three different WiFi accesspoints and has been running on 5 different servers over the time.</p>
  4196. ]]></description>
  4197.    <content:encoded><![CDATA[<p><a href="https://github.com/x-way/ldapauth" title="x-way/ldapauth">ldapauth</a> is a <a href="https://nodejs.org" title="Node.js">Node.js</a> script which I have been using for the last 12+ years mostly unchanged.</p>
  4198. <p>It started its life in a <a href="https://en.wikipedia.org/wiki/LXC" title="Linux Containers (LXC)">LXC</a> container, eventually was moved to a Docker container and recently ended up in its own repository on GitHub.</p>
  4199. <p>The functionality it provides is not extraordinary, but helped to bridge a gap where no other product was available.<br>
  4200. It talks <a href="https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol" title="Lightweight Directory Access Protocol - Wikipedia">LDAP</a> one one side (although limited to handle user lookup requests) and on the other side connects to a <a href="https://www.mongodb.com/" title="MongoDB - Document Oriented Database">MongoDB</a> database where the information is stored.</p>
  4201. <p>It emerged out of the desire to have an easy way to manage individual user accounts for my home WiFi. I already had MongoDB running for some other personal project and simply added the list of users there (including the UI for managing them).<br>
  4202. Thus the missing part was to get the WiFi accesspoint to lookup user accounts in MongoDB.</p>
  4203. <p>Of course WiFi accesspoints do not directly talk MongoDB, but rather some other protocol like <a href="https://en.wikipedia.org/wiki/RADIUS" title="Remote Authentication Dial-In User Service">RADIUS</a>.<br>
  4204. A <a href="https://freeradius.org/" title="FreeRADIUS">freeradius</a> server was quickly setup, but still couldn't talk to MongoDB at the time. Thus comes in <a href="https://github.com/x-way/ldapauth" title="x-way/ldapauth">ldapauth</a>, which takes LDAP queries from freeradius and turns them into MongoDB lookups so that in the end the WiFi accesspoint receives the user accounts :-)</p>
  4205. <p>Not sure if this is particularly useful for anyone else, but at least here it did provide good services (and continues to do so).<br>
  4206. Current score is that it has survived three different WiFi accesspoints and has been running on 5 different servers over the time.</p>
  4207. ]]></content:encoded>
  4208.  </item>
  4209.  
  4210.  <item>
  4211.    <title>Hilltop Hoods - Laced Up</title>
  4212.    <link>https://blog.x-way.org/Music/2024/02/18/Hilltop-Hoods-Laced-Up.html</link>
  4213.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324332</guid>
  4214.    <dc:creator>Andreas Jaggi</dc:creator>
  4215.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4216.    <pubDate>Sun, 18 Feb 2024 08:31:00 +0100</pubDate>
  4217.    <category domain="https://blog.x-way.org/Music/">Music</category>
  4218.    <description><![CDATA[<p><a href="https://youtu.be/Nn-kfXCQt6A" title="Hilltop Hoods - Laced Up - YouTube">Hilltop Hoods - Laced Up</a></p>
  4219. <p>Some vibes from Australia &#x2764;</p>
  4220. ]]></description>
  4221.    <content:encoded><![CDATA[<p><a href="https://youtu.be/Nn-kfXCQt6A" title="Hilltop Hoods - Laced Up - YouTube">Hilltop Hoods - Laced Up</a></p>
  4222. <p>Some vibes from Australia &#x2764;</p>
  4223. ]]></content:encoded>
  4224.  </item>
  4225.  
  4226.  <item>
  4227.    <title>qr-bag</title>
  4228.    <link>https://blog.x-way.org/Coding/2024/02/03/qr-bag.html</link>
  4229.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324331</guid>
  4230.    <dc:creator>Andreas Jaggi</dc:creator>
  4231.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4232.    <pubDate>Sat, 03 Feb 2024 19:55:00 +0100</pubDate>
  4233.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  4234.    <description><![CDATA[<p>Some time ago I used an online tool to generate some QR codes with a contact URL so I can put them on my luggage.<br>Now I got a new bag and need a new QR code for it. As I don't remember the online tool I used years ago, I decided to write my own tool.</p>
  4235. <p>Thus say hello to <a href="https://github.com/x-way/qr-bag" title="x-way/qr-bag: Generate a QR code with a lost bag logo in the middle pointing to a URL with information about the owner ">qr-bag</a>. It's a commandline tool written in Go to generate QR codes for URLs with a little logo in the middle.<br>The code for it is mostly a wrapper around the <a href="https://github.com/yeqown/go-qrcode" title="yeqown/go-qrcode">go-qrcode</a> library which does all the heavy lifting.</p>
  4236. <img src="https://blog.x-way.org/images/qr-bag123.png" width="173" height="173" alt="Example QR code">
  4237. ]]></description>
  4238.    <content:encoded><![CDATA[<p>Some time ago I used an online tool to generate some QR codes with a contact URL so I can put them on my luggage.<br>Now I got a new bag and need a new QR code for it. As I don't remember the online tool I used years ago, I decided to write my own tool.</p>
  4239. <p>Thus say hello to <a href="https://github.com/x-way/qr-bag" title="x-way/qr-bag: Generate a QR code with a lost bag logo in the middle pointing to a URL with information about the owner ">qr-bag</a>. It's a commandline tool written in Go to generate QR codes for URLs with a little logo in the middle.<br>The code for it is mostly a wrapper around the <a href="https://github.com/yeqown/go-qrcode" title="yeqown/go-qrcode">go-qrcode</a> library which does all the heavy lifting.</p>
  4240. <img src="https://blog.x-way.org/images/qr-bag123.png" width="173" height="173" alt="Example QR code">
  4241. ]]></content:encoded>
  4242.  </item>
  4243.  
  4244.  <item>
  4245.    <title>text-decoration-color</title>
  4246.    <link>https://blog.x-way.org/Webdesign/2024/02/03/text-decoration-color.html</link>
  4247.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324330</guid>
  4248.    <dc:creator>Andreas Jaggi</dc:creator>
  4249.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4250.    <pubDate>Sat, 03 Feb 2024 16:27:00 +0100</pubDate>
  4251.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  4252.    <description><![CDATA[<p>Just discovered the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/text-decoration-color" title="text-decoration-color - CSS: Cascading Style Sheets | MDN"><code>text-decoration-color</code></a> CSS property and added it to the style on the blog:</p>
  4253. <pre>a:hover {color: #454545; text-decoration: underline; text-decoration-color: #26C4FF;}</pre>
  4254. <p>This causes that when you hover over a link in a post, the underline is not in the same boring gray as the text but lights up in a nice color :-)</p>
  4255. <p>(not to be confused with the hacky colored underlines in the righthand navigation bar, where I use a colored <code>border-bottom</code> to achieve a similar effect since 2002)</p>
  4256. ]]></description>
  4257.    <content:encoded><![CDATA[<p>Just discovered the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/text-decoration-color" title="text-decoration-color - CSS: Cascading Style Sheets | MDN"><code>text-decoration-color</code></a> CSS property and added it to the style on the blog:</p>
  4258. <pre>a:hover {color: #454545; text-decoration: underline; text-decoration-color: #26C4FF;}</pre>
  4259. <p>This causes that when you hover over a link in a post, the underline is not in the same boring gray as the text but lights up in a nice color :-)</p>
  4260. <p>(not to be confused with the hacky colored underlines in the righthand navigation bar, where I use a colored <code>border-bottom</code> to achieve a similar effect since 2002)</p>
  4261. ]]></content:encoded>
  4262.  </item>
  4263.  
  4264.  <item>
  4265.    <title>Blogroll cleanup 2024</title>
  4266.    <link>https://blog.x-way.org/Misc/2024/01/31/Blogroll-cleanup-2024.html</link>
  4267.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324329</guid>
  4268.    <dc:creator>Andreas Jaggi</dc:creator>
  4269.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4270.    <pubDate>Wed, 31 Jan 2024 22:50:00 +0100</pubDate>
  4271.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  4272.    <description><![CDATA[<p>It's time again to do some cleanup of my blogroll before the links start to turn into 404 errors :-)</p>
  4273. <p>Removed:</p>
  4274. <ul>
  4275. <li><a href="https://web.archive.org/web/20200301211123/http://strcat.de/blog/" title="Veni, Vidi, VISA">Veni, Vidi, VISA</a></li>
  4276. <li><a href="https://web.archive.org/web/20230724205656/https://gru.gq/" title="grugq's domain - Cyber is Deception">gru.gq</a></li>
  4277. <li><a href="https://web.archive.org/web/20240119172554/http://www.brewdog.com/blog" title="BrewDog Craft Beer Blog">BrewDog</a></li>
  4278. <li><a href="https://mdlayher.com/blog/" title="Matt Layher">mdlayher.com</a></li>
  4279. <li><a href="https://blog.inliniac.net/" title="Inliniac | Everything inline.">Inliniac</a></li>
  4280. <li><a href="https://home.regit.org/" title="To Linux and beyond!">To Linux and beyond!</a></li>
  4281. <li><a href="http://lonesysadmin.net/" title="The Lone Sysadmin">The Lone Sysadmin</a></li>
  4282. <li><a href="https://eklitzke.org/" title="Evan Klitzke">eklitzke.org</a></li>
  4283. </ul>
  4284. ]]></description>
  4285.    <content:encoded><![CDATA[<p>It's time again to do some cleanup of my blogroll before the links start to turn into 404 errors :-)</p>
  4286. <p>Removed:</p>
  4287. <ul>
  4288. <li><a href="https://web.archive.org/web/20200301211123/http://strcat.de/blog/" title="Veni, Vidi, VISA">Veni, Vidi, VISA</a></li>
  4289. <li><a href="https://web.archive.org/web/20230724205656/https://gru.gq/" title="grugq's domain - Cyber is Deception">gru.gq</a></li>
  4290. <li><a href="https://web.archive.org/web/20240119172554/http://www.brewdog.com/blog" title="BrewDog Craft Beer Blog">BrewDog</a></li>
  4291. <li><a href="https://mdlayher.com/blog/" title="Matt Layher">mdlayher.com</a></li>
  4292. <li><a href="https://blog.inliniac.net/" title="Inliniac | Everything inline.">Inliniac</a></li>
  4293. <li><a href="https://home.regit.org/" title="To Linux and beyond!">To Linux and beyond!</a></li>
  4294. <li><a href="http://lonesysadmin.net/" title="The Lone Sysadmin">The Lone Sysadmin</a></li>
  4295. <li><a href="https://eklitzke.org/" title="Evan Klitzke">eklitzke.org</a></li>
  4296. </ul>
  4297. ]]></content:encoded>
  4298.  </item>
  4299.  
  4300.  <item>
  4301.    <title>Statistics revived</title>
  4302.    <link>https://blog.x-way.org/Misc/2024/01/30/Statistics-revived.html</link>
  4303.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324328</guid>
  4304.    <dc:creator>Andreas Jaggi</dc:creator>
  4305.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4306.    <pubDate>Tue, 30 Jan 2024 06:46:00 +0100</pubDate>
  4307.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  4308.    <description><![CDATA[<p>Following in the trend of replacing tables, I've revived the old <a href="https://blog.x-way.org/statistics.html" title="x-log - Statistics">statistics page</a>.<br>Now using less markup as it is built with <code>&lt;div&gt;</code> and CSS only (the <code>display: inline-block;</code> property was particularly helpful).</p>
  4309. <p>(the Jekyll/Liquid templating to generate the data for it looks quite horrific though&hellip;)</p>
  4310. ]]></description>
  4311.    <content:encoded><![CDATA[<p>Following in the trend of replacing tables, I've revived the old <a href="https://blog.x-way.org/statistics.html" title="x-log - Statistics">statistics page</a>.<br>Now using less markup as it is built with <code>&lt;div&gt;</code> and CSS only (the <code>display: inline-block;</code> property was particularly helpful).</p>
  4312. <p>(the Jekyll/Liquid templating to generate the data for it looks quite horrific though&hellip;)</p>
  4313. ]]></content:encoded>
  4314.  </item>
  4315.  
  4316.  <item>
  4317.    <title>Tables are gone</title>
  4318.    <link>https://blog.x-way.org/Webdesign/2024/01/28/Tables-are-gone.html</link>
  4319.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324327</guid>
  4320.    <dc:creator>Andreas Jaggi</dc:creator>
  4321.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4322.    <pubDate>Sun, 28 Jan 2024 16:47:00 +0100</pubDate>
  4323.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  4324.    <description><![CDATA[<p>Over the last couple weeks I slowly replaced the various &lt;table&gt;-based layout elements of the blog with more modern HTML elements.<br>
  4325. And finally this afternoon the work was completed with the last &lt;table&gt; element gone.</p>
  4326. <p>Visually there should be almost no differences, but in case something looks strange just let <a href="https://blog.x-way.org/about.html" title="x-log - About">me</a> know :-)<br>
  4327. (and yes, style-wise everything is still using the pixel-based layout from 2002, one day this might change as well&hellip;)</p>
  4328. ]]></description>
  4329.    <content:encoded><![CDATA[<p>Over the last couple weeks I slowly replaced the various &lt;table&gt;-based layout elements of the blog with more modern HTML elements.<br>
  4330. And finally this afternoon the work was completed with the last &lt;table&gt; element gone.</p>
  4331. <p>Visually there should be almost no differences, but in case something looks strange just let <a href="https://blog.x-way.org/about.html" title="x-log - About">me</a> know :-)<br>
  4332. (and yes, style-wise everything is still using the pixel-based layout from 2002, one day this might change as well&hellip;)</p>
  4333. ]]></content:encoded>
  4334.  </item>
  4335.  
  4336.  <item>
  4337.    <title>Quick and dirty dark mode</title>
  4338.    <link>https://blog.x-way.org/Webdesign/2024/01/27/Quick-and-dirty-dark-mode.html</link>
  4339.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324326</guid>
  4340.    <dc:creator>Andreas Jaggi</dc:creator>
  4341.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4342.    <pubDate>Sat, 27 Jan 2024 15:59:00 +0100</pubDate>
  4343.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  4344.    <description><![CDATA[<p>To provide basic dark mode support for the blog, I added the following lines of CSS:</p>
  4345. <pre>
  4346. @media (prefers-color-scheme: dark) {
  4347.    html { filter: invert(1) hue-rotate(180deg); }
  4348.    img, video, iframe { filter: invert(1) hue-rotate(180deg); }
  4349. }
  4350. </pre>
  4351. <p>If the browser/OS has dark mode enabled it will invert the colors and rotate the hue to achieve the dark mode effect.<br>The whole operation is applied a second time on images, videos and frames to avoid that they have their colors distorted.</p>
  4352. <p>You can get a preview by using the developer tools of your browser to enable dark mode :-)</p>
  4353. <p>The code is inspired by the post <a href="https://dev.to/akhilarjun/one-line-dark-mode-using-css-24li" title="One line - Dark Mode using CSS - DEV Community">here</a>, and then extended to provide a CSS-only solution by leveraging the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/color-scheme" title="color-scheme - CSS: Cascading Style Sheets | MDN">color-scheme CSS property</a>.</p>
  4354. ]]></description>
  4355.    <content:encoded><![CDATA[<p>To provide basic dark mode support for the blog, I added the following lines of CSS:</p>
  4356. <pre>
  4357. @media (prefers-color-scheme: dark) {
  4358.    html { filter: invert(1) hue-rotate(180deg); }
  4359.    img, video, iframe { filter: invert(1) hue-rotate(180deg); }
  4360. }
  4361. </pre>
  4362. <p>If the browser/OS has dark mode enabled it will invert the colors and rotate the hue to achieve the dark mode effect.<br>The whole operation is applied a second time on images, videos and frames to avoid that they have their colors distorted.</p>
  4363. <p>You can get a preview by using the developer tools of your browser to enable dark mode :-)</p>
  4364. <p>The code is inspired by the post <a href="https://dev.to/akhilarjun/one-line-dark-mode-using-css-24li" title="One line - Dark Mode using CSS - DEV Community">here</a>, and then extended to provide a CSS-only solution by leveraging the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/color-scheme" title="color-scheme - CSS: Cascading Style Sheets | MDN">color-scheme CSS property</a>.</p>
  4365. ]]></content:encoded>
  4366.  </item>
  4367.  
  4368.  <item>
  4369.    <title>Sub Focus, Dimension, Culture Shock &#x26; 1991</title>
  4370.    <link>https://blog.x-way.org/Music/2024/01/21/Sub-Focus-Dimension-Culture-Shock-1991.html</link>
  4371.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324325</guid>
  4372.    <dc:creator>Andreas Jaggi</dc:creator>
  4373.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4374.    <pubDate>Sun, 21 Jan 2024 22:16:00 +0100</pubDate>
  4375.    <category domain="https://blog.x-way.org/Music/">Music</category>
  4376.    <description><![CDATA[<p><a href="https://youtu.be/OZMWKqbcwzo" title="Sub Focus, Dimension, Culture Shock &amp; 1991 - YouTube">Sub Focus, Dimension, Culture Shock &amp; 1991</a></p>
  4377. <p>Some very fine Drum and bass. Recently got to experience two of them live (Sub Focus &amp; 1991), and have plans to see Dimension next :-)</p>
  4378. <p>Especially like the little <a href="https://theprodigy.com" title="The Prodigy">The Prodigy</a> mixin starting at 1:04:30 &#x1F973;</p>
  4379. ]]></description>
  4380.    <content:encoded><![CDATA[<p><a href="https://youtu.be/OZMWKqbcwzo" title="Sub Focus, Dimension, Culture Shock &amp; 1991 - YouTube">Sub Focus, Dimension, Culture Shock &amp; 1991</a></p>
  4381. <p>Some very fine Drum and bass. Recently got to experience two of them live (Sub Focus &amp; 1991), and have plans to see Dimension next :-)</p>
  4382. <p>Especially like the little <a href="https://theprodigy.com" title="The Prodigy">The Prodigy</a> mixin starting at 1:04:30 &#x1F973;</p>
  4383. ]]></content:encoded>
  4384.  </item>
  4385.  
  4386.  <item>
  4387.    <title>Keeping old URLs alive</title>
  4388.    <link>https://blog.x-way.org/Misc/2024/01/21/Keeping-old-URLs-alive.html</link>
  4389.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324324</guid>
  4390.    <dc:creator>Andreas Jaggi</dc:creator>
  4391.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4392.    <pubDate>Sun, 21 Jan 2024 21:41:00 +0100</pubDate>
  4393.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  4394.    <description><![CDATA[<p>As mentioned before, I'm a supporter of the <a href="https://www.w3.org/Provider/Style/URI" title="Hypertext Style: Cool URIs don't change">Cool URIs don't change</a> approach.<br>Thus I try to keep all the URLs of this blog working (or at least make them redirect to the new place where the content is located).<br>Not always an easy task with old domains and multiple blogging engines accumulated over the years.</p>
  4395. <p>To help me with that (and ensure I don't break anything when updating a 10+ year old mod_rewrite config) I created a short Bash script to test the redirect behavior.<br>It contains a list of URLs and their expected redirect target, goes through them with <a href="https://curl.se" title="curl">curl</a> and checks that the correct <code>Location:</code> header is returned.</p>
  4396. <p>As it might be useful for others in similar situations, the script can be found <a href="https://blog.x-way.org/stuff/test.sh" title="test.sh">here</a>.</p>
  4397. ]]></description>
  4398.    <content:encoded><![CDATA[<p>As mentioned before, I'm a supporter of the <a href="https://www.w3.org/Provider/Style/URI" title="Hypertext Style: Cool URIs don't change">Cool URIs don't change</a> approach.<br>Thus I try to keep all the URLs of this blog working (or at least make them redirect to the new place where the content is located).<br>Not always an easy task with old domains and multiple blogging engines accumulated over the years.</p>
  4399. <p>To help me with that (and ensure I don't break anything when updating a 10+ year old mod_rewrite config) I created a short Bash script to test the redirect behavior.<br>It contains a list of URLs and their expected redirect target, goes through them with <a href="https://curl.se" title="curl">curl</a> and checks that the correct <code>Location:</code> header is returned.</p>
  4400. <p>As it might be useful for others in similar situations, the script can be found <a href="https://blog.x-way.org/stuff/test.sh" title="test.sh">here</a>.</p>
  4401. ]]></content:encoded>
  4402.  </item>
  4403.  
  4404.  <item>
  4405.    <title>I miss human curation</title>
  4406.    <link>https://blog.x-way.org/Misc/2024/01/21/I-miss-human-curation.html</link>
  4407.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324323</guid>
  4408.    <dc:creator>Andreas Jaggi</dc:creator>
  4409.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4410.    <pubDate>Sun, 21 Jan 2024 07:14:00 +0100</pubDate>
  4411.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  4412.    <description><![CDATA[<p><a href="https://blog.cassidoo.co/post/human-curation/" title="I miss human curation - Cassidy's blog">I miss human curation</a> &mdash; Where are my internet friends? And where are their weird blogs? (<a href="https://bookmark.kniebes.io/bookmark/a97dd47db2b511eebfd9408d5c84b5d9" title="Markus Kniebes Journal">via</a>)<p>
  4413. ]]></description>
  4414.    <content:encoded><![CDATA[<p><a href="https://blog.cassidoo.co/post/human-curation/" title="I miss human curation - Cassidy's blog">I miss human curation</a> &mdash; Where are my internet friends? And where are their weird blogs? (<a href="https://bookmark.kniebes.io/bookmark/a97dd47db2b511eebfd9408d5c84b5d9" title="Markus Kniebes Journal">via</a>)<p>
  4415. ]]></content:encoded>
  4416.  </item>
  4417.  
  4418.  <item>
  4419.    <title>Postfix clear verification cache</title>
  4420.    <link>https://blog.x-way.org/Linux/2024/01/07/Postfix-clear-verification-cache.html</link>
  4421.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324322</guid>
  4422.    <dc:creator>Andreas Jaggi</dc:creator>
  4423.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4424.    <pubDate>Sun, 07 Jan 2024 22:38:00 +0100</pubDate>
  4425.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  4426.    <description><![CDATA[<p>While adding some new alias functionality to my setup, it repeatedly failed with an error similar to this, despite my configuration changes:</p>
  4427. <pre>Recipient address rejected: unverified address: host XXX[XXX] said: 550 5.1.1
  4428. &lt;foo@bar.com&gt; User doesn't exist: foo@bar.com (in reply to RCPT TO command);</pre>
  4429. <p>Turns out that the negative verification result is cached and the cache is not reset during a reload/restart of postfix.<br>
  4430. Thus it must be cleared manually like this:</p>
  4431. <pre>/etc/init.d/postfix stop
  4432. rm /var/lib/postfix/verify_cache.db
  4433. /etc/init.d/postfix start</pre>
  4434. ]]></description>
  4435.    <content:encoded><![CDATA[<p>While adding some new alias functionality to my setup, it repeatedly failed with an error similar to this, despite my configuration changes:</p>
  4436. <pre>Recipient address rejected: unverified address: host XXX[XXX] said: 550 5.1.1
  4437. &lt;foo@bar.com&gt; User doesn't exist: foo@bar.com (in reply to RCPT TO command);</pre>
  4438. <p>Turns out that the negative verification result is cached and the cache is not reset during a reload/restart of postfix.<br>
  4439. Thus it must be cleared manually like this:</p>
  4440. <pre>/etc/init.d/postfix stop
  4441. rm /var/lib/postfix/verify_cache.db
  4442. /etc/init.d/postfix start</pre>
  4443. ]]></content:encoded>
  4444.  </item>
  4445.  
  4446.  <item>
  4447.    <title>Valid HTML5</title>
  4448.    <link>https://blog.x-way.org/Webdesign/2024/01/03/Valid-HTML5.html</link>
  4449.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324321</guid>
  4450.    <dc:creator>Andreas Jaggi</dc:creator>
  4451.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4452.    <pubDate>Wed, 03 Jan 2024 20:59:00 +0100</pubDate>
  4453.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  4454.    <description><![CDATA[<p>After <a href="https://blog.x-way.org/Webdesign/2024/01/01/Winter-plain-2.html" title="Winter - plain 2">switching the colors</a> of the design, I kept the momentum and continued working on the HTML of the blog.</p>
  4455. <p>It took couple iterations of multiple hours, but now it's done: the HTML source of this blog is <a href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fblog.x-way.org%2F" title="Nu HTML Checker">valid HTML5</a>!</p>
  4456. <p>Getting rid of the obsoleteness hidden in old blogentries dating back over 20 years also led to some interesting observations.<br>
  4457. Back when moving from HTML 4.01 to <a href="https://blog.x-way.org/Coding/2004/04/08/x-log_v202c.html" title="x-log v2.02c">XHTML 1.1</a>, I remember spending some time to transform old <code>&lt;br&gt;</code> tags to <code>&lt;br /&gt;</code>. And now for HTML5 I did the inverse and moved all <code>&lt;br /&gt;</code> tags back to <code>&lt;br&gt;</code> :-)</p>
  4458. <p>Also once more I'm very thankful for the work of the <a href="https://archive.org/" title="Internet Archive">Internet Archive</a>, which helped to recover images hosted on servers long gone (like URLs which already at the end of 2002 were no longer valid!).</p>
  4459. <p>Overall a lot of replacing no longer existing HTML tags and attributes with CSS definitions.<br>And there is virtually no change to the visual representation of the blog (which was the goal), so we still have the table-based layout with pixel-sized fonts as originally drafted in 2002.<br>Moving this to actually leverage modern HTML5 mechanisms and making it also more mobile friendly are tasks left for some future cold winter evenings :-)</p>
  4460. <p><a href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fblog.x-way.org%2F" title="Valid W3C HTML5"><img src="https://blog.x-way.org/images/html5-validator-badge.png" width="352" height="124" alt="W3C HTML5"></a></p>
  4461. ]]></description>
  4462.    <content:encoded><![CDATA[<p>After <a href="https://blog.x-way.org/Webdesign/2024/01/01/Winter-plain-2.html" title="Winter - plain 2">switching the colors</a> of the design, I kept the momentum and continued working on the HTML of the blog.</p>
  4463. <p>It took couple iterations of multiple hours, but now it's done: the HTML source of this blog is <a href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fblog.x-way.org%2F" title="Nu HTML Checker">valid HTML5</a>!</p>
  4464. <p>Getting rid of the obsoleteness hidden in old blogentries dating back over 20 years also led to some interesting observations.<br>
  4465. Back when moving from HTML 4.01 to <a href="https://blog.x-way.org/Coding/2004/04/08/x-log_v202c.html" title="x-log v2.02c">XHTML 1.1</a>, I remember spending some time to transform old <code>&lt;br&gt;</code> tags to <code>&lt;br /&gt;</code>. And now for HTML5 I did the inverse and moved all <code>&lt;br /&gt;</code> tags back to <code>&lt;br&gt;</code> :-)</p>
  4466. <p>Also once more I'm very thankful for the work of the <a href="https://archive.org/" title="Internet Archive">Internet Archive</a>, which helped to recover images hosted on servers long gone (like URLs which already at the end of 2002 were no longer valid!).</p>
  4467. <p>Overall a lot of replacing no longer existing HTML tags and attributes with CSS definitions.<br>And there is virtually no change to the visual representation of the blog (which was the goal), so we still have the table-based layout with pixel-sized fonts as originally drafted in 2002.<br>Moving this to actually leverage modern HTML5 mechanisms and making it also more mobile friendly are tasks left for some future cold winter evenings :-)</p>
  4468. <p><a href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fblog.x-way.org%2F" title="Valid W3C HTML5"><img src="https://blog.x-way.org/images/html5-validator-badge.png" width="352" height="124" alt="W3C HTML5"></a></p>
  4469. ]]></content:encoded>
  4470.  </item>
  4471.  
  4472.  <item>
  4473.    <title>Winter - plain 2</title>
  4474.    <link>https://blog.x-way.org/Webdesign/2024/01/01/Winter-plain-2.html</link>
  4475.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324320</guid>
  4476.    <dc:creator>Andreas Jaggi</dc:creator>
  4477.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4478.    <pubDate>Mon, 01 Jan 2024 12:41:00 +0100</pubDate>
  4479.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  4480.    <description><![CDATA[<p>Happy New Year! &mdash; Happy New Colors!</p>
  4481. <p>Winter is here (for a while already), time to change the colors of the blog.<br>
  4482. To keep it in the nostalgic theme (the previous design was a <a href="https://blog.x-way.org/Webdesign/2022/06/04/Blogging-like-2002.html" title="x-log - Blogging like 2002">repurpose of the inital design from 2002</a>), I'm using the colors from the <a href="https://blog.x-way.org/Webdesign/2002/12/15/Winter.html" title="x-log - Winter">'plain 2' winter layout</a> (also from 2002).</p>
  4483. <p>Enjoy!</p>
  4484. ]]></description>
  4485.    <content:encoded><![CDATA[<p>Happy New Year! &mdash; Happy New Colors!</p>
  4486. <p>Winter is here (for a while already), time to change the colors of the blog.<br>
  4487. To keep it in the nostalgic theme (the previous design was a <a href="https://blog.x-way.org/Webdesign/2022/06/04/Blogging-like-2002.html" title="x-log - Blogging like 2002">repurpose of the inital design from 2002</a>), I'm using the colors from the <a href="https://blog.x-way.org/Webdesign/2002/12/15/Winter.html" title="x-log - Winter">'plain 2' winter layout</a> (also from 2002).</p>
  4488. <p>Enjoy!</p>
  4489. ]]></content:encoded>
  4490.  </item>
  4491.  
  4492.  <item>
  4493.    <title>MECSA</title>
  4494.    <link>https://blog.x-way.org/Networking/2023/12/30/MECSA.html</link>
  4495.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324319</guid>
  4496.    <dc:creator>Andreas Jaggi</dc:creator>
  4497.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4498.    <pubDate>Sat, 30 Dec 2023 09:16:00 +0100</pubDate>
  4499.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  4500.    <description><![CDATA[<p>A <a href="https://news.ycombinator.com/item?id=38792358" title="True, MECSA is also interesting: https://mecsa.jrc.ec.europa.eu/en/ | Hacker News">comment on Hacker News</a> pointed me to the <a href="https://mecsa.jrc.ec.europa.eu/en/" title="My Email Communications Security Assessment (MECSA)">MECSA tool</a> provided by the European Union.</p>
  4501. <p>MECSA stands for My Email Communications Security Assessment, and is a tool to assess the security of email communication between providers.</p>
  4502. <p>As I run my own email server, I was curious to find out how my setup is scoring. Here are the results, seems like I'm doing a good job :-)</p>
  4503. <p><a href="https://blog.x-way.org/images/mecsa_scores_full.png" title="MECSA score for jaggi.info, showing 5/5 stars in Confidential Delivery, Phishing and Identity Theft, and Intergrity of Messages."><img src="https://blog.x-way.org/images/mecsa_scores.png" alt="MECSA score for jaggi.info, showing 5/5 stars in Confidential Delivery, Phishing and Identity Theft, and Intergrity of Messages." height="61" width="650"></a></p>
  4504. <p><a href="https://blog.x-way.org/images/mecsa_details_full.png" title="MECSA details for jaggi.info, showing 100 points in StartTLS, X509, SPF, DKIM, DMARC, DANE, DNSSEC and MTA-STS."><img src="https://blog.x-way.org/images/mecsa_details.png" alt="MECSA details for jaggi.info, showing 100 points in StartTLS, X509, SPF, DKIM, DMARC, DANE, DNSSEC and MTA-STS." height="75" width="650"></a></p>
  4505. <p>Link to the full report for jaggi.info: <a href="https://mecsa.jrc.ec.europa.eu/en/finderRequest/f856486ecaf94dce5e8022c0a97c63b3" title="Report id f856486ecaf94dce5e8022c0a97c63b3 for domain jaggi.info (28/12/2023)">https://mecsa.jrc.ec.europa.eu/en/finderRequest/f856486ecaf94dce5e8022c0a97c63b3</a></p>
  4506. ]]></description>
  4507.    <content:encoded><![CDATA[<p>A <a href="https://news.ycombinator.com/item?id=38792358" title="True, MECSA is also interesting: https://mecsa.jrc.ec.europa.eu/en/ | Hacker News">comment on Hacker News</a> pointed me to the <a href="https://mecsa.jrc.ec.europa.eu/en/" title="My Email Communications Security Assessment (MECSA)">MECSA tool</a> provided by the European Union.</p>
  4508. <p>MECSA stands for My Email Communications Security Assessment, and is a tool to assess the security of email communication between providers.</p>
  4509. <p>As I run my own email server, I was curious to find out how my setup is scoring. Here are the results, seems like I'm doing a good job :-)</p>
  4510. <p><a href="https://blog.x-way.org/images/mecsa_scores_full.png" title="MECSA score for jaggi.info, showing 5/5 stars in Confidential Delivery, Phishing and Identity Theft, and Intergrity of Messages."><img src="https://blog.x-way.org/images/mecsa_scores.png" alt="MECSA score for jaggi.info, showing 5/5 stars in Confidential Delivery, Phishing and Identity Theft, and Intergrity of Messages." height="61" width="650"></a></p>
  4511. <p><a href="https://blog.x-way.org/images/mecsa_details_full.png" title="MECSA details for jaggi.info, showing 100 points in StartTLS, X509, SPF, DKIM, DMARC, DANE, DNSSEC and MTA-STS."><img src="https://blog.x-way.org/images/mecsa_details.png" alt="MECSA details for jaggi.info, showing 100 points in StartTLS, X509, SPF, DKIM, DMARC, DANE, DNSSEC and MTA-STS." height="75" width="650"></a></p>
  4512. <p>Link to the full report for jaggi.info: <a href="https://mecsa.jrc.ec.europa.eu/en/finderRequest/f856486ecaf94dce5e8022c0a97c63b3" title="Report id f856486ecaf94dce5e8022c0a97c63b3 for domain jaggi.info (28/12/2023)">https://mecsa.jrc.ec.europa.eu/en/finderRequest/f856486ecaf94dce5e8022c0a97c63b3</a></p>
  4513. ]]></content:encoded>
  4514.  </item>
  4515.  
  4516.  <item>
  4517.    <title>Fix named checkhints extra record in hints</title>
  4518.    <link>https://blog.x-way.org/Linux/2023/12/27/Fix-named-checkhints-extra-record-in-hints.html</link>
  4519.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324318</guid>
  4520.    <dc:creator>Andreas Jaggi</dc:creator>
  4521.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4522.    <pubDate>Wed, 27 Dec 2023 20:53:00 +0100</pubDate>
  4523.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  4524.    <description><![CDATA[<p>Recently named on my Debian server started to emit the following messages:</p>
  4525. <pre>Dec 23 18:30:05 server named[1168203]: checkhints: view external_network: b.root-servers.net/A (170.247.170.2) missing from hints
  4526. Dec 23 18:30:05 server named[1168203]: checkhints: view external_network: b.root-servers.net/A (199.9.14.201) extra record in hints
  4527. Dec 23 18:30:05 server named[1168203]: checkhints: view external_network: b.root-servers.net/AAAA (2801:1b8:10::b) missing from hints
  4528. Dec 23 18:30:05 server named[1168203]: checkhints: view external_network: b.root-servers.net/AAAA (2001:500:200::b) extra record in hints</pre>
  4529. <p>The reason for these warnings, is a <a href="https://b.root-servers.org/news/2023/05/16/new-addresses.html" title="New addresses for b.root-servers.net">IP change of the B root-server</a>.</p>
  4530. <p>Debian is <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054393" title="Debian bug report #1054393">not ready yet</a> with updating their dns-root-data package.<br>To fix the mismatching IP definitions on a Debian system, the current root zone definitions can also be updated manually from Internic:</p>
  4531. <pre>curl https://www.internic.net/domain/named.root -s &gt; /usr/share/dns/root.hints
  4532. curl https://www.internic.net/domain/named.root.sig -s &gt; /usr/share/dns/root.hints.sig</pre>
  4533. ]]></description>
  4534.    <content:encoded><![CDATA[<p>Recently named on my Debian server started to emit the following messages:</p>
  4535. <pre>Dec 23 18:30:05 server named[1168203]: checkhints: view external_network: b.root-servers.net/A (170.247.170.2) missing from hints
  4536. Dec 23 18:30:05 server named[1168203]: checkhints: view external_network: b.root-servers.net/A (199.9.14.201) extra record in hints
  4537. Dec 23 18:30:05 server named[1168203]: checkhints: view external_network: b.root-servers.net/AAAA (2801:1b8:10::b) missing from hints
  4538. Dec 23 18:30:05 server named[1168203]: checkhints: view external_network: b.root-servers.net/AAAA (2001:500:200::b) extra record in hints</pre>
  4539. <p>The reason for these warnings, is a <a href="https://b.root-servers.org/news/2023/05/16/new-addresses.html" title="New addresses for b.root-servers.net">IP change of the B root-server</a>.</p>
  4540. <p>Debian is <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054393" title="Debian bug report #1054393">not ready yet</a> with updating their dns-root-data package.<br>To fix the mismatching IP definitions on a Debian system, the current root zone definitions can also be updated manually from Internic:</p>
  4541. <pre>curl https://www.internic.net/domain/named.root -s &gt; /usr/share/dns/root.hints
  4542. curl https://www.internic.net/domain/named.root.sig -s &gt; /usr/share/dns/root.hints.sig</pre>
  4543. ]]></content:encoded>
  4544.  </item>
  4545.  
  4546.  <item>
  4547.    <title>Wikipedia Donation</title>
  4548.    <link>https://blog.x-way.org/Misc/2023/12/10/Wikipedia-Donation.html</link>
  4549.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324317</guid>
  4550.    <dc:creator>Andreas Jaggi</dc:creator>
  4551.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4552.    <pubDate>Sun, 10 Dec 2023 22:24:00 +0100</pubDate>
  4553.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  4554.    <description><![CDATA[<p>Seems that after donating to Wikipedia there is a redirect to <a href="https://thankyou.wikipedia.org/wiki/Thank_You/en" rel="noreferrer" title="Thank You - Wikimedia Foundation">this page</a>, which sets a cookie to no longer show the donation banners.</p>
  4555. ]]></description>
  4556.    <content:encoded><![CDATA[<p>Seems that after donating to Wikipedia there is a redirect to <a href="https://thankyou.wikipedia.org/wiki/Thank_You/en" rel="noreferrer" title="Thank You - Wikimedia Foundation">this page</a>, which sets a cookie to no longer show the donation banners.</p>
  4557. ]]></content:encoded>
  4558.  </item>
  4559.  
  4560.  <item>
  4561.    <title>Why Personal Blogging Still Rules</title>
  4562.    <link>https://blog.x-way.org/Misc/2023/04/30/Why-Personal-Blogging-Still-Rules.html</link>
  4563.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324316</guid>
  4564.    <dc:creator>Andreas Jaggi</dc:creator>
  4565.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4566.    <pubDate>Sun, 30 Apr 2023 14:42:00 +0200</pubDate>
  4567.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  4568.    <description><![CDATA[<p>Resonating article from <a href="https://mikegrindle.com/" title="Mike Grindle - Homepage">Mike Grindle</a> about personal blogging and how it fits into todays Internet: <a href="https://mikegrindle.com/posts/personal-blogging" title="Why Personal Blogging Still Rules - mikegrindle.com">Why Personal Blogging Still Rules</a></p>
  4569. <blockquote cite="https://mikegrindle.com/posts/personal-blogging">
  4570. <p>Before the social media craze or publishing platforms, and long before ‘content creator’ was a job title, blogs served as one of the primary forms of online expression and communication.</p>
  4571. </blockquote>
  4572. <blockquote cite="https://mikegrindle.com/posts/personal-blogging">
  4573. <p>Everything on your blog was made to look and feel the way you wanted. If it didn’t, you rolled your sleeves up and coded that stuff in like the webmaster you were. And if the masses didn’t like it, who cared? They had no obligations to you, and you had none to them.</p>
  4574. </blockquote>
  4575. <blockquote cite="https://mikegrindle.com/posts/personal-blogging">
  4576. <p>Hiding beneath the drivel that is Google’s search results, and all the trackers, cookies, ads and curated feeds that come with them, personal blogs and sites of all shapes and sizes are still there. They’re thriving even in a kind of interconnected web beneath the web.</p>
  4577. </blockquote>
  4578. <blockquote cite="https://mikegrindle.com/posts/personal-blogging">
  4579. <p>The blogs on this small or “indie” web come in many shapes and sizes. [&hellip;] But at their core, they all have one characteristic in common: they’re there because their owners wanted to carve out their space on the internet.</p>
  4580. </blockquote>
  4581. <blockquote cite="https://mikegrindle.com/posts/personal-blogging">
  4582. <p>Your blog doesn’t have to be big and fancy. It doesn’t have to outrank everyone on Google, make money or “convert leads” to be important. It can be something that exists for its own sake, as your place to express yourself in whatever manner you please.</p>
  4583. </blockquote>
  4584. <p>(<a href="https://uninformation.org/webnotizen/23/why-personal-blogging-still-rules/" title="der Uninformat – »Why Personal Blogging Still Rules«">via</a>)</p>
  4585. ]]></description>
  4586.    <content:encoded><![CDATA[<p>Resonating article from <a href="https://mikegrindle.com/" title="Mike Grindle - Homepage">Mike Grindle</a> about personal blogging and how it fits into todays Internet: <a href="https://mikegrindle.com/posts/personal-blogging" title="Why Personal Blogging Still Rules - mikegrindle.com">Why Personal Blogging Still Rules</a></p>
  4587. <blockquote cite="https://mikegrindle.com/posts/personal-blogging">
  4588. <p>Before the social media craze or publishing platforms, and long before ‘content creator’ was a job title, blogs served as one of the primary forms of online expression and communication.</p>
  4589. </blockquote>
  4590. <blockquote cite="https://mikegrindle.com/posts/personal-blogging">
  4591. <p>Everything on your blog was made to look and feel the way you wanted. If it didn’t, you rolled your sleeves up and coded that stuff in like the webmaster you were. And if the masses didn’t like it, who cared? They had no obligations to you, and you had none to them.</p>
  4592. </blockquote>
  4593. <blockquote cite="https://mikegrindle.com/posts/personal-blogging">
  4594. <p>Hiding beneath the drivel that is Google’s search results, and all the trackers, cookies, ads and curated feeds that come with them, personal blogs and sites of all shapes and sizes are still there. They’re thriving even in a kind of interconnected web beneath the web.</p>
  4595. </blockquote>
  4596. <blockquote cite="https://mikegrindle.com/posts/personal-blogging">
  4597. <p>The blogs on this small or “indie” web come in many shapes and sizes. [&hellip;] But at their core, they all have one characteristic in common: they’re there because their owners wanted to carve out their space on the internet.</p>
  4598. </blockquote>
  4599. <blockquote cite="https://mikegrindle.com/posts/personal-blogging">
  4600. <p>Your blog doesn’t have to be big and fancy. It doesn’t have to outrank everyone on Google, make money or “convert leads” to be important. It can be something that exists for its own sake, as your place to express yourself in whatever manner you please.</p>
  4601. </blockquote>
  4602. <p>(<a href="https://uninformation.org/webnotizen/23/why-personal-blogging-still-rules/" title="der Uninformat – »Why Personal Blogging Still Rules«">via</a>)</p>
  4603. ]]></content:encoded>
  4604.  </item>
  4605.  
  4606.  <item>
  4607.    <title>exec-hookd</title>
  4608.    <link>https://blog.x-way.org/Linux/2023/04/23/exec-hookd.html</link>
  4609.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324315</guid>
  4610.    <dc:creator>Andreas Jaggi</dc:creator>
  4611.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4612.    <pubDate>Sun, 23 Apr 2023 22:32:00 +0200</pubDate>
  4613.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  4614.    <description><![CDATA[<p>To automate some of the deployment steps on my personal server, I needed a tool which can be triggered by a webhook and does execute some pre-defined commands.</p>
  4615. <p>A classic solution for this would be to have a simple PHP script with a call to <code>system(...)</code>. But I don't have PHP installed on the server itself and wanted this to be more lightweight than a full Apache+PHP installation.</p>
  4616. <p>Thus <a href="https://github.com/x-way/exec-hookd" title="x-way/exec-hookd: execute commands from webhooks">exec-hookd</a> was born. It is a small Go daemon which listens to HTTP POST requests and runs pre-defined commands when a matching path is requested.</p>
  4617. <p>Its configuration lives in a small JSON file, which lists the port to listen on and the paths together with their commands to execute:</p>
  4618. <pre>{
  4619.  "Port": 8059,
  4620.  "HookList": [
  4621.    {
  4622.      "Path": "/myhook",
  4623.      "Exec": [
  4624.        {
  4625.          "Cmd": "/usr/bin/somecmd",
  4626.          "Args": [
  4627.            "--some",
  4628.            "arguments"
  4629.          ],
  4630.          "Timeout": "5s"
  4631.        }
  4632.      ]
  4633.    }
  4634.  ]
  4635. }</pre>
  4636. <p>The commands are called with a timeout after which they are stopped to avoid that things hang around forever.</p>
  4637. ]]></description>
  4638.    <content:encoded><![CDATA[<p>To automate some of the deployment steps on my personal server, I needed a tool which can be triggered by a webhook and does execute some pre-defined commands.</p>
  4639. <p>A classic solution for this would be to have a simple PHP script with a call to <code>system(...)</code>. But I don't have PHP installed on the server itself and wanted this to be more lightweight than a full Apache+PHP installation.</p>
  4640. <p>Thus <a href="https://github.com/x-way/exec-hookd" title="x-way/exec-hookd: execute commands from webhooks">exec-hookd</a> was born. It is a small Go daemon which listens to HTTP POST requests and runs pre-defined commands when a matching path is requested.</p>
  4641. <p>Its configuration lives in a small JSON file, which lists the port to listen on and the paths together with their commands to execute:</p>
  4642. <pre>{
  4643.  "Port": 8059,
  4644.  "HookList": [
  4645.    {
  4646.      "Path": "/myhook",
  4647.      "Exec": [
  4648.        {
  4649.          "Cmd": "/usr/bin/somecmd",
  4650.          "Args": [
  4651.            "--some",
  4652.            "arguments"
  4653.          ],
  4654.          "Timeout": "5s"
  4655.        }
  4656.      ]
  4657.    }
  4658.  ]
  4659. }</pre>
  4660. <p>The commands are called with a timeout after which they are stopped to avoid that things hang around forever.</p>
  4661. ]]></content:encoded>
  4662.  </item>
  4663.  
  4664.  <item>
  4665.    <title>Nice git log alias</title>
  4666.    <link>https://blog.x-way.org/Coding/2023/04/16/Nice-git-log-alias.html</link>
  4667.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324314</guid>
  4668.    <dc:creator>Andreas Jaggi</dc:creator>
  4669.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4670.    <pubDate>Sun, 16 Apr 2023 13:55:00 +0200</pubDate>
  4671.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  4672.    <description><![CDATA[<p><a href="https://uninformation.org/" title="Wald- und Wiesen-Weblog - uninformation.org">Ralf</a> <a href="https://web.archive.org/web/20231128231558/https://masto.futbol/@oldschooldev/109839690235274960" title="ralf g.: killer-alias für das schönste gitlog in der shell">tooted</a> a nice and tidy git log output alias for the console:</p>
  4673. <code>
  4674. alias glg="git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)&lt;%an&gt;%Creset' --abbrev-commit"
  4675. </code>
  4676. ]]></description>
  4677.    <content:encoded><![CDATA[<p><a href="https://uninformation.org/" title="Wald- und Wiesen-Weblog - uninformation.org">Ralf</a> <a href="https://web.archive.org/web/20231128231558/https://masto.futbol/@oldschooldev/109839690235274960" title="ralf g.: killer-alias für das schönste gitlog in der shell">tooted</a> a nice and tidy git log output alias for the console:</p>
  4678. <code>
  4679. alias glg="git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)&lt;%an&gt;%Creset' --abbrev-commit"
  4680. </code>
  4681. ]]></content:encoded>
  4682.  </item>
  4683.  
  4684.  <item>
  4685.    <title>Docker registry facade with nginx</title>
  4686.    <link>https://blog.x-way.org/Linux/2023/03/18/Docker-registry-facade-with-nginx.html</link>
  4687.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324313</guid>
  4688.    <dc:creator>Andreas Jaggi</dc:creator>
  4689.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4690.    <pubDate>Sat, 18 Mar 2023 10:36:00 +0100</pubDate>
  4691.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  4692.    <description><![CDATA[<p>Found <a href="https://httptoolkit.com/blog/docker-image-registry-facade/" title="Dodge the next Dockerpocalypse: how to own your own Docker Registry address">this inspiring blog post</a> about how to use your own domain for Docker images. (via <a href="https://news.ycombinator.com/item?id=35205838" title="How to own your own Docker Registry address | Hacker News">HN</a>)</p>
  4693. <p>It explains how to use your own domain with redirects such that the Docker registry hosting the images can be changed easily. Your domain is only used for issueing HTTP redirects, so that the actual data storage and transfer happens directly with the Docker registry.</p>
  4694. <p>The blog post comes with <a href="https://github.com/httptoolkit/docker-registry-facade/blob/main/Caddyfile" title="Caddyfile">a sample implementation for Caddy</a>. As my server is running <a href="https://nginx.org/" title="nginx">nginx</a>, I used the following config snippet to achieve the same result:</p>
  4695. <pre>
  4696. server {
  4697. listen 443 ssl;
  4698. listen [::]:443 ssl;
  4699.  
  4700. server_name docker.x-way.org;
  4701.  
  4702. access_log /var/log/nginx/docker.x-way.org.access.log;
  4703. error_log /var/log/nginx/docker.x-way.org.error.log;
  4704.  
  4705. ssl_certificate /etc/letsencrypt/live/docker.x-way.org/fullchain.pem;
  4706. ssl_certificate_key /etc/letsencrypt/live/docker.x-way.org/privkey.pem;
  4707.  
  4708. location / {
  4709. return 403;
  4710. }
  4711.  
  4712. location = /v2 {
  4713. add_header Cache-Control 'max-age=300, must-revalidate';
  4714. return 307 https://registry.hub.docker.com$request_uri;
  4715. }
  4716. location = /v2/ {
  4717. add_header Cache-Control 'max-age=300, must-revalidate';
  4718. return 307 https://registry.hub.docker.com$request_uri;
  4719. }
  4720. location = /v2/xway {
  4721. add_header Cache-Control 'max-age=300, must-revalidate';
  4722. return 307 https://registry.hub.docker.com$request_uri;
  4723. }
  4724. location /v2/xway/ {
  4725. add_header Cache-Control 'max-age=300, must-revalidate';
  4726. return 307 https://registry.hub.docker.com$request_uri;
  4727. }
  4728. }
  4729. </pre>
  4730. <p>Quickly tested it with some docker pull commands and already integrated it into the <a href="https://github.com/x-way/dnsupd/pull/72" title="Use custom registry by x-way - Pull Request #72 - x-way/dnsupd">build process of dnsupd</a>.</p>
  4731. ]]></description>
  4732.    <content:encoded><![CDATA[<p>Found <a href="https://httptoolkit.com/blog/docker-image-registry-facade/" title="Dodge the next Dockerpocalypse: how to own your own Docker Registry address">this inspiring blog post</a> about how to use your own domain for Docker images. (via <a href="https://news.ycombinator.com/item?id=35205838" title="How to own your own Docker Registry address | Hacker News">HN</a>)</p>
  4733. <p>It explains how to use your own domain with redirects such that the Docker registry hosting the images can be changed easily. Your domain is only used for issueing HTTP redirects, so that the actual data storage and transfer happens directly with the Docker registry.</p>
  4734. <p>The blog post comes with <a href="https://github.com/httptoolkit/docker-registry-facade/blob/main/Caddyfile" title="Caddyfile">a sample implementation for Caddy</a>. As my server is running <a href="https://nginx.org/" title="nginx">nginx</a>, I used the following config snippet to achieve the same result:</p>
  4735. <pre>
  4736. server {
  4737. listen 443 ssl;
  4738. listen [::]:443 ssl;
  4739.  
  4740. server_name docker.x-way.org;
  4741.  
  4742. access_log /var/log/nginx/docker.x-way.org.access.log;
  4743. error_log /var/log/nginx/docker.x-way.org.error.log;
  4744.  
  4745. ssl_certificate /etc/letsencrypt/live/docker.x-way.org/fullchain.pem;
  4746. ssl_certificate_key /etc/letsencrypt/live/docker.x-way.org/privkey.pem;
  4747.  
  4748. location / {
  4749. return 403;
  4750. }
  4751.  
  4752. location = /v2 {
  4753. add_header Cache-Control 'max-age=300, must-revalidate';
  4754. return 307 https://registry.hub.docker.com$request_uri;
  4755. }
  4756. location = /v2/ {
  4757. add_header Cache-Control 'max-age=300, must-revalidate';
  4758. return 307 https://registry.hub.docker.com$request_uri;
  4759. }
  4760. location = /v2/xway {
  4761. add_header Cache-Control 'max-age=300, must-revalidate';
  4762. return 307 https://registry.hub.docker.com$request_uri;
  4763. }
  4764. location /v2/xway/ {
  4765. add_header Cache-Control 'max-age=300, must-revalidate';
  4766. return 307 https://registry.hub.docker.com$request_uri;
  4767. }
  4768. }
  4769. </pre>
  4770. <p>Quickly tested it with some docker pull commands and already integrated it into the <a href="https://github.com/x-way/dnsupd/pull/72" title="Use custom registry by x-way - Pull Request #72 - x-way/dnsupd">build process of dnsupd</a>.</p>
  4771. ]]></content:encoded>
  4772.  </item>
  4773.  
  4774.  <item>
  4775.    <title>STRAYA 🇦🇺</title>
  4776.    <link>https://blog.x-way.org/Music/2023/01/26/STRAYA.html</link>
  4777.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324312</guid>
  4778.    <dc:creator>Andreas Jaggi</dc:creator>
  4779.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4780.    <pubDate>Thu, 26 Jan 2023 05:43:00 +0100</pubDate>
  4781.    <category domain="https://blog.x-way.org/Music/">Music</category>
  4782.    <description><![CDATA[<p>Here's a bit older mashup. Happy <a href="https://www.australiaday.com.au/" title="Australia Day 2023 - Australia Day in NSW">Australia Day</a>!</p>
  4783. <p><a href="https://youtu.be/rMdbVHPmCW0" title="National Anthem of STRAYA - YouTube">National Anthem of STRAYA</a></p>
  4784. ]]></description>
  4785.    <content:encoded><![CDATA[<p>Here's a bit older mashup. Happy <a href="https://www.australiaday.com.au/" title="Australia Day 2023 - Australia Day in NSW">Australia Day</a>!</p>
  4786. <p><a href="https://youtu.be/rMdbVHPmCW0" title="National Anthem of STRAYA - YouTube">National Anthem of STRAYA</a></p>
  4787. ]]></content:encoded>
  4788.  </item>
  4789.  
  4790.  <item>
  4791.    <title>ACME-CAA</title>
  4792.    <link>https://blog.x-way.org/Networking/2023/01/18/ACME-CAA.html</link>
  4793.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324311</guid>
  4794.    <dc:creator>Andreas Jaggi</dc:creator>
  4795.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4796.    <pubDate>Wed, 18 Jan 2023 23:06:00 +0100</pubDate>
  4797.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  4798.    <description><![CDATA[<p>Let's Encrypt recently <a href="https://community.letsencrypt.org/t/enabling-acme-caa-account-and-method-binding/189588" title="Enabling ACME CAA Account and Method Binding">introduced support</a> for <a href="https://www.rfc-editor.org/rfc/rfc8657" title="RFC8657">ACME-CAA</a>.</p>
  4799. <p>I've now extended my existing CAA DNS entries with the ACME-CAA properties:</p>
  4800. <pre>% dig +short -t CAA x-way.org
  4801. 0 issue "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/68891730; validationmethods=http-01"
  4802. 0 issue "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/605777876; validationmethods=http-01"</pre>
  4803. <p>The effect of this is that Let's Encrypt will only grant a signed TLS certificate if the request comes from one of my two accounts (authenticated with the corresponding private key).<br>If the certificate request comes from a different account, no TLS certificate will be granted.<br>This protects against man-in-the-middle attacks, specifically against attacks where someone between Let's Encrypt and my server would be trying to impersonate my server to obtain a signed TLS certificate.</p>
  4804. <p>Addendum:<br>In case you're wondering where to get the accounturi value from, it can be found in your account file:</p>
  4805. <pre>% cat /etc/letsencrypt/accounts/acme-v02.api.letsencrypt.org/directory/*/regr.json
  4806. {"body": {}, "uri": "https://acme-v02.api.letsencrypt.org/acme/acct/605777876"}</pre>
  4807. ]]></description>
  4808.    <content:encoded><![CDATA[<p>Let's Encrypt recently <a href="https://community.letsencrypt.org/t/enabling-acme-caa-account-and-method-binding/189588" title="Enabling ACME CAA Account and Method Binding">introduced support</a> for <a href="https://www.rfc-editor.org/rfc/rfc8657" title="RFC8657">ACME-CAA</a>.</p>
  4809. <p>I've now extended my existing CAA DNS entries with the ACME-CAA properties:</p>
  4810. <pre>% dig +short -t CAA x-way.org
  4811. 0 issue "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/68891730; validationmethods=http-01"
  4812. 0 issue "letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/605777876; validationmethods=http-01"</pre>
  4813. <p>The effect of this is that Let's Encrypt will only grant a signed TLS certificate if the request comes from one of my two accounts (authenticated with the corresponding private key).<br>If the certificate request comes from a different account, no TLS certificate will be granted.<br>This protects against man-in-the-middle attacks, specifically against attacks where someone between Let's Encrypt and my server would be trying to impersonate my server to obtain a signed TLS certificate.</p>
  4814. <p>Addendum:<br>In case you're wondering where to get the accounturi value from, it can be found in your account file:</p>
  4815. <pre>% cat /etc/letsencrypt/accounts/acme-v02.api.letsencrypt.org/directory/*/regr.json
  4816. {"body": {}, "uri": "https://acme-v02.api.letsencrypt.org/acme/acct/605777876"}</pre>
  4817. ]]></content:encoded>
  4818.  </item>
  4819.  
  4820.  <item>
  4821.    <title>JSON Feed</title>
  4822.    <link>https://blog.x-way.org/Webdesign/2023/01/10/JSON-Feed.html</link>
  4823.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324310</guid>
  4824.    <dc:creator>Andreas Jaggi</dc:creator>
  4825.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4826.    <pubDate>Tue, 10 Jan 2023 21:51:00 +0100</pubDate>
  4827.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  4828.    <description><![CDATA[<p>Added a <a href="https://en.wikipedia.org/wiki/JSON_Feed" title="JSON Feed - Wikipedia">JSON Feed</a> to this blog (in additon to the existing <a href="https://blog.x-way.org/rss.xml" title="x-log - RSS feed">RSS</a> and <a href="https://blog.x-way.org/atom.xml" title="x-log - Atom feed">Atom</a> feeds): <a href="https://blog.x-way.org/feed.json" title="x-log - JSON feed">https://blog.x-way.org/feed.json</a></p>
  4829. <p>To build the proper JSON file, I used <a href="https://github.com/vallieres/jekyll-json-feed/tree/master" title="JSON Feed for Jekyll">this Jekyll template</a> and the <a href="https://validator.jsonfeed.org/" title="JSON Feed Validator">JSON Feed validator</a>.</p>
  4830. ]]></description>
  4831.    <content:encoded><![CDATA[<p>Added a <a href="https://en.wikipedia.org/wiki/JSON_Feed" title="JSON Feed - Wikipedia">JSON Feed</a> to this blog (in additon to the existing <a href="https://blog.x-way.org/rss.xml" title="x-log - RSS feed">RSS</a> and <a href="https://blog.x-way.org/atom.xml" title="x-log - Atom feed">Atom</a> feeds): <a href="https://blog.x-way.org/feed.json" title="x-log - JSON feed">https://blog.x-way.org/feed.json</a></p>
  4832. <p>To build the proper JSON file, I used <a href="https://github.com/vallieres/jekyll-json-feed/tree/master" title="JSON Feed for Jekyll">this Jekyll template</a> and the <a href="https://validator.jsonfeed.org/" title="JSON Feed Validator">JSON Feed validator</a>.</p>
  4833. ]]></content:encoded>
  4834.  </item>
  4835.  
  4836.  <item>
  4837.    <title>Get last 24h of logs with AWK</title>
  4838.    <link>https://blog.x-way.org/Linux/2023/01/03/Get-last-24h-of-logs-with-AWK.html</link>
  4839.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324309</guid>
  4840.    <dc:creator>Andreas Jaggi</dc:creator>
  4841.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4842.    <pubDate>Tue, 03 Jan 2023 14:40:00 +0100</pubDate>
  4843.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  4844.    <description><![CDATA[<p>For a temporary log analysis task, I wanted to get the last 24h of logs from a <a href="http://www.postfix.org/" title="The Postfix Home Page">Postfix</a> logfile.<br>To achieve this I came up with the following AWK oneliner (which fails in spectacular ways around new years):</p>
  4845. <code>
  4846. awk -F '[ :]+' 'BEGIN{m=split("Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec",d,"|"); for(o=1;o&lt;=m;o++){months[d[o]]=sprintf("%02d",o)}} mktime(strftime("%Y")" "months[$1]" "sprintf("%02d",$2+1)" "$3" "$4" "$5) &gt; systime()'
  4847. </code>
  4848. <p>This is then used in a cronjob to get a <a href="http://jimsun.linxnet.com/postfix_contrib.html" title="JIMSUN - Postfix Contribs">pflogsumm</a> summary of the last 24h:</p>
  4849. <code>
  4850. cat /var/log/mail.log | awk -F '[ :]+' 'BEGIN{m=split("Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec",d,"|"); for(o=1;o&lt;=m;o++){months[d[o]]=sprintf("%02d",o)}} mktime(strftime("%Y")" "months[$1]" "sprintf("%02d",$2+1)" "$3" "$4" "$5) &gt; systime()' | pflogsumm
  4851. </code>
  4852. ]]></description>
  4853.    <content:encoded><![CDATA[<p>For a temporary log analysis task, I wanted to get the last 24h of logs from a <a href="http://www.postfix.org/" title="The Postfix Home Page">Postfix</a> logfile.<br>To achieve this I came up with the following AWK oneliner (which fails in spectacular ways around new years):</p>
  4854. <code>
  4855. awk -F '[ :]+' 'BEGIN{m=split("Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec",d,"|"); for(o=1;o&lt;=m;o++){months[d[o]]=sprintf("%02d",o)}} mktime(strftime("%Y")" "months[$1]" "sprintf("%02d",$2+1)" "$3" "$4" "$5) &gt; systime()'
  4856. </code>
  4857. <p>This is then used in a cronjob to get a <a href="http://jimsun.linxnet.com/postfix_contrib.html" title="JIMSUN - Postfix Contribs">pflogsumm</a> summary of the last 24h:</p>
  4858. <code>
  4859. cat /var/log/mail.log | awk -F '[ :]+' 'BEGIN{m=split("Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec",d,"|"); for(o=1;o&lt;=m;o++){months[d[o]]=sprintf("%02d",o)}} mktime(strftime("%Y")" "months[$1]" "sprintf("%02d",$2+1)" "$3" "$4" "$5) &gt; systime()' | pflogsumm
  4860. </code>
  4861. ]]></content:encoded>
  4862.  </item>
  4863.  
  4864.  <item>
  4865.    <title>Happy New Year 2023</title>
  4866.    <link>https://blog.x-way.org/Misc/2022/12/31/Happy-New-Year-2023.html</link>
  4867.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324308</guid>
  4868.    <dc:creator>Andreas Jaggi</dc:creator>
  4869.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4870.    <pubDate>Sat, 31 Dec 2022 13:59:00 +0100</pubDate>
  4871.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  4872.    <description><![CDATA[<p><a href="https://youtu.be/ZKGgsQg17cw" title="Sydney New Year's Eve midgnight fireworks - YouTube">Sydney New Year's Eve midgnight fireworks</a></p>
  4873. <p>As usual, Sydney is a bit ahead of us. Great memories, long time ago :-)</p>
  4874. ]]></description>
  4875.    <content:encoded><![CDATA[<p><a href="https://youtu.be/ZKGgsQg17cw" title="Sydney New Year's Eve midgnight fireworks - YouTube">Sydney New Year's Eve midgnight fireworks</a></p>
  4876. <p>As usual, Sydney is a bit ahead of us. Great memories, long time ago :-)</p>
  4877. ]]></content:encoded>
  4878.  </item>
  4879.  
  4880.  <item>
  4881.    <title>Alpha Bravo Charlie</title>
  4882.    <link>https://blog.x-way.org/Misc/2022/12/25/Alpha-Bravo-Charlie.html</link>
  4883.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324307</guid>
  4884.    <dc:creator>Andreas Jaggi</dc:creator>
  4885.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4886.    <pubDate>Sun, 25 Dec 2022 22:11:00 +0100</pubDate>
  4887.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  4888.    <description><![CDATA[<p>While closing an old account I had to communicate using the infamous NATO/ICAO phonetic alphabet (US banks like to exchange the 20+ character long <a href="https://en.wikipedia.org/wiki/International_Bank_Account_Number" title="International Bank Account Number - Wikipedia">IBANs</a> via poor-quality call-center phonelines).</p>
  4889. <p>As it has been a while since I last used it, I created a handy table to quickly lookup the code words: <a href="http://nato.sigint.ch" title="NATO/ICAO phonetic alphabet">nato.sigint.ch</a></p>
  4890. <p>Special feature: when queried by curl (eg. without a text/html Accept header) it returns the table as plaintext :-)</p>
  4891. <pre># curl nato.sigint.ch
  4892. A Alpha      S Sierra
  4893. B Bravo      T Tango
  4894. C Charlie    U Uniform
  4895. D Delta      V Victor
  4896. E Echo       W Whiskey
  4897. F Foxtrot    X X-ray
  4898. G Golf       Y Yankee
  4899. H Hotel      Z Zulu
  4900. I India      0 Zero
  4901. J Juliett    1 One
  4902. K Kilo       2 Two
  4903. L Lima       3 Three
  4904. M Mike       4 Four
  4905. N November   5 Five
  4906. O Oscar      6 Six
  4907. P Papa       7 Seven
  4908. Q Quebec     8 Eight
  4909. R Romeo      9 Niner</pre>
  4910. ]]></description>
  4911.    <content:encoded><![CDATA[<p>While closing an old account I had to communicate using the infamous NATO/ICAO phonetic alphabet (US banks like to exchange the 20+ character long <a href="https://en.wikipedia.org/wiki/International_Bank_Account_Number" title="International Bank Account Number - Wikipedia">IBANs</a> via poor-quality call-center phonelines).</p>
  4912. <p>As it has been a while since I last used it, I created a handy table to quickly lookup the code words: <a href="http://nato.sigint.ch" title="NATO/ICAO phonetic alphabet">nato.sigint.ch</a></p>
  4913. <p>Special feature: when queried by curl (eg. without a text/html Accept header) it returns the table as plaintext :-)</p>
  4914. <pre># curl nato.sigint.ch
  4915. A Alpha      S Sierra
  4916. B Bravo      T Tango
  4917. C Charlie    U Uniform
  4918. D Delta      V Victor
  4919. E Echo       W Whiskey
  4920. F Foxtrot    X X-ray
  4921. G Golf       Y Yankee
  4922. H Hotel      Z Zulu
  4923. I India      0 Zero
  4924. J Juliett    1 One
  4925. K Kilo       2 Two
  4926. L Lima       3 Three
  4927. M Mike       4 Four
  4928. N November   5 Five
  4929. O Oscar      6 Six
  4930. P Papa       7 Seven
  4931. Q Quebec     8 Eight
  4932. R Romeo      9 Niner</pre>
  4933. ]]></content:encoded>
  4934.  </item>
  4935.  
  4936.  <item>
  4937.    <title>How to Exit Vim</title>
  4938.    <link>https://blog.x-way.org/Linux/2022/08/07/How-to-Exit-Vim.html</link>
  4939.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324306</guid>
  4940.    <dc:creator>Andreas Jaggi</dc:creator>
  4941.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4942.    <pubDate>Sun, 07 Aug 2022 22:19:00 +0200</pubDate>
  4943.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  4944.    <description><![CDATA[<p><img src="https://blog.x-way.org/images/how-to-exit-vim.jpg" alt="How to Exit Vim" height="459" width="680"></p>
  4945. <p>(<a href="https://twitter.com/sheeshee/status/1556000047539654657" title="Su-Shee (@sheeshee) / Twitter">via</a>)</p>
  4946. ]]></description>
  4947.    <content:encoded><![CDATA[<p><img src="https://blog.x-way.org/images/how-to-exit-vim.jpg" alt="How to Exit Vim" height="459" width="680"></p>
  4948. <p>(<a href="https://twitter.com/sheeshee/status/1556000047539654657" title="Su-Shee (@sheeshee) / Twitter">via</a>)</p>
  4949. ]]></content:encoded>
  4950.  </item>
  4951.  
  4952.  <item>
  4953.    <title>Add node to MongoDB cluster</title>
  4954.    <link>https://blog.x-way.org/Linux/2022/07/06/Add-node-to-MongoDB-cluster.html</link>
  4955.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324305</guid>
  4956.    <dc:creator>Andreas Jaggi</dc:creator>
  4957.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4958.    <pubDate>Wed, 06 Jul 2022 22:14:00 +0200</pubDate>
  4959.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  4960.    <description><![CDATA[<p>To add a new node to an existing <a href="https://www.mongodb.com/" title="MongoDB">MongoDB</a> cluster, login to the mongo shell on the primary node and run the following command:</p>
  4961. <pre>rs.add({host:"mongodb3.example.net:27017"})</pre>
  4962. <p>Similar to remove a node from the cluster, use:</p>
  4963. <pre>rs.remove("mongodb3.example.net:27017")</pre>
  4964. ]]></description>
  4965.    <content:encoded><![CDATA[<p>To add a new node to an existing <a href="https://www.mongodb.com/" title="MongoDB">MongoDB</a> cluster, login to the mongo shell on the primary node and run the following command:</p>
  4966. <pre>rs.add({host:"mongodb3.example.net:27017"})</pre>
  4967. <p>Similar to remove a node from the cluster, use:</p>
  4968. <pre>rs.remove("mongodb3.example.net:27017")</pre>
  4969. ]]></content:encoded>
  4970.  </item>
  4971.  
  4972.  <item>
  4973.    <title>Custom nginx error pages</title>
  4974.    <link>https://blog.x-way.org/Webdesign/2022/06/19/Custom-nginx-error-pages.html</link>
  4975.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324304</guid>
  4976.    <dc:creator>Andreas Jaggi</dc:creator>
  4977.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  4978.    <pubDate>Sun, 19 Jun 2022 09:48:00 +0200</pubDate>
  4979.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  4980.    <description><![CDATA[<p>For quite some time I've been using custom nginx error pages on this site.<br>
  4981. My approach so far was to generate a bunch of static HTML with the various error messages and then configure them for each corresponding HTTP status codes in nginx.<br>As there are quite a number of HTTP errors, I used a little shell script to generate the whole config and HTML, in the end I had a huge file with snippets like the one below.</p>
  4982. <pre>
  4983. error_page 429 @custom_error_429;
  4984. location @custom_error_429 {
  4985. internal;
  4986. more_set_headers 'Content-Type: text/html';
  4987. echo '&lt;html&gt;...&lt;/html&gt;';
  4988. }
  4989. </pre>
  4990.  
  4991. <p>Now while implementing custom error pages for a different project, I tried to see if there is an easier way to do this.<br>
  4992. Some searching lead to the <a href="https://blog.adriaan.io/one-nginx-error-page-to-rule-them-all.html" title="One NGINX error page to rule them all - Adriaan's blog">One NGINX error page to rule them all</a> article which describes an alternative approach leveraging the nginx <abbr title="Server Side Includes">SSI</abbr> module to generate the error pages on the fly.</p>
  4993. <p>
  4994. Instead of generating and defining a specific error page for each error, a single error page is used for all errors.
  4995. </p>
  4996. <pre>
  4997. error_page 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414
  4998.           415 416 417 418 421 422 423 424 425 426 428 429 431 451 500
  4999.           501 502 503 504 505 506 507 508 510 511 /error.html;
  5000.  
  5001. location = /error.html {
  5002. ssi on;
  5003. internal;
  5004. root /var/www/default;
  5005. }
  5006. </pre>
  5007. <p>nginx provides the status code as variable to our error page, but we also need the error message to make it more userfriendly.<br>
  5008. For this we define a mapping of status codes to the error messages.</p>
  5009. <pre>
  5010. map $status $status_text {
  5011.  400 'Bad Request';
  5012.  401 'Unauthorized';
  5013.  402 'Payment Required';
  5014.  403 'Forbidden';
  5015.  404 'Not Found';
  5016.  405 'Method Not Allowed';
  5017.  406 'Not Acceptable';
  5018.  407 'Proxy Authentication Required';
  5019.  408 'Request Timeout';
  5020.  409 'Conflict';
  5021.  410 'Gone';
  5022.  411 'Length Required';
  5023.  412 'Precondition Failed';
  5024.  413 'Payload Too Large';
  5025.  414 'URI Too Long';
  5026.  415 'Unsupported Media Type';
  5027.  416 'Range Not Satisfiable';
  5028.  417 'Expectation Failed';
  5029.  418 'I\'m a teapot';
  5030.  421 'Misdirected Request';
  5031.  422 'Unprocessable Entity';
  5032.  423 'Locked';
  5033.  424 'Failed Dependency';
  5034.  425 'Too Early';
  5035.  426 'Upgrade Required';
  5036.  428 'Precondition Required';
  5037.  429 'Too Many Requests';
  5038.  431 'Request Header Fields Too Large';
  5039.  451 'Unavailable For Legal Reasons';
  5040.  500 'Internal Server Error';
  5041.  501 'Not Implemented';
  5042.  502 'Bad Gateway';
  5043.  503 'Service Unavailable';
  5044.  504 'Gateway Timeout';
  5045.  505 'HTTP Version Not Supported';
  5046.  506 'Variant Also Negotiates';
  5047.  507 'Insufficient Storage';
  5048.  508 'Loop Detected';
  5049.  510 'Not Extended';
  5050.  511 'Network Authentication Required';
  5051.  default 'Something went wrong';
  5052. }
  5053. </pre>
  5054.  
  5055. <p>Now we have the <var>status</var> and the <var>status_text</var> variables available in our error.html page.</p>
  5056. <pre>
  5057. &lt;html&gt;&lt;body&gt;
  5058. &lt;h1&gt;&lt;!--# echo var="status" default="" --&gt;
  5059. &lt;!--# echo var="status_text" default="Something went wrong" --&gt;&lt;/h1&gt;
  5060. &lt;/body&gt;&lt;/html&gt;
  5061. </pre>
  5062. ]]></description>
  5063.    <content:encoded><![CDATA[<p>For quite some time I've been using custom nginx error pages on this site.<br>
  5064. My approach so far was to generate a bunch of static HTML with the various error messages and then configure them for each corresponding HTTP status codes in nginx.<br>As there are quite a number of HTTP errors, I used a little shell script to generate the whole config and HTML, in the end I had a huge file with snippets like the one below.</p>
  5065. <pre>
  5066. error_page 429 @custom_error_429;
  5067. location @custom_error_429 {
  5068. internal;
  5069. more_set_headers 'Content-Type: text/html';
  5070. echo '&lt;html&gt;...&lt;/html&gt;';
  5071. }
  5072. </pre>
  5073.  
  5074. <p>Now while implementing custom error pages for a different project, I tried to see if there is an easier way to do this.<br>
  5075. Some searching lead to the <a href="https://blog.adriaan.io/one-nginx-error-page-to-rule-them-all.html" title="One NGINX error page to rule them all - Adriaan's blog">One NGINX error page to rule them all</a> article which describes an alternative approach leveraging the nginx <abbr title="Server Side Includes">SSI</abbr> module to generate the error pages on the fly.</p>
  5076. <p>
  5077. Instead of generating and defining a specific error page for each error, a single error page is used for all errors.
  5078. </p>
  5079. <pre>
  5080. error_page 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414
  5081.           415 416 417 418 421 422 423 424 425 426 428 429 431 451 500
  5082.           501 502 503 504 505 506 507 508 510 511 /error.html;
  5083.  
  5084. location = /error.html {
  5085. ssi on;
  5086. internal;
  5087. root /var/www/default;
  5088. }
  5089. </pre>
  5090. <p>nginx provides the status code as variable to our error page, but we also need the error message to make it more userfriendly.<br>
  5091. For this we define a mapping of status codes to the error messages.</p>
  5092. <pre>
  5093. map $status $status_text {
  5094.  400 'Bad Request';
  5095.  401 'Unauthorized';
  5096.  402 'Payment Required';
  5097.  403 'Forbidden';
  5098.  404 'Not Found';
  5099.  405 'Method Not Allowed';
  5100.  406 'Not Acceptable';
  5101.  407 'Proxy Authentication Required';
  5102.  408 'Request Timeout';
  5103.  409 'Conflict';
  5104.  410 'Gone';
  5105.  411 'Length Required';
  5106.  412 'Precondition Failed';
  5107.  413 'Payload Too Large';
  5108.  414 'URI Too Long';
  5109.  415 'Unsupported Media Type';
  5110.  416 'Range Not Satisfiable';
  5111.  417 'Expectation Failed';
  5112.  418 'I\'m a teapot';
  5113.  421 'Misdirected Request';
  5114.  422 'Unprocessable Entity';
  5115.  423 'Locked';
  5116.  424 'Failed Dependency';
  5117.  425 'Too Early';
  5118.  426 'Upgrade Required';
  5119.  428 'Precondition Required';
  5120.  429 'Too Many Requests';
  5121.  431 'Request Header Fields Too Large';
  5122.  451 'Unavailable For Legal Reasons';
  5123.  500 'Internal Server Error';
  5124.  501 'Not Implemented';
  5125.  502 'Bad Gateway';
  5126.  503 'Service Unavailable';
  5127.  504 'Gateway Timeout';
  5128.  505 'HTTP Version Not Supported';
  5129.  506 'Variant Also Negotiates';
  5130.  507 'Insufficient Storage';
  5131.  508 'Loop Detected';
  5132.  510 'Not Extended';
  5133.  511 'Network Authentication Required';
  5134.  default 'Something went wrong';
  5135. }
  5136. </pre>
  5137.  
  5138. <p>Now we have the <var>status</var> and the <var>status_text</var> variables available in our error.html page.</p>
  5139. <pre>
  5140. &lt;html&gt;&lt;body&gt;
  5141. &lt;h1&gt;&lt;!--# echo var="status" default="" --&gt;
  5142. &lt;!--# echo var="status_text" default="Something went wrong" --&gt;&lt;/h1&gt;
  5143. &lt;/body&gt;&lt;/html&gt;
  5144. </pre>
  5145. ]]></content:encoded>
  5146.  </item>
  5147.  
  5148.  <item>
  5149.    <title>nitter</title>
  5150.    <link>https://blog.x-way.org/Misc/2022/06/15/nitter.html</link>
  5151.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324303</guid>
  5152.    <dc:creator>Andreas Jaggi</dc:creator>
  5153.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5154.    <pubDate>Wed, 15 Jun 2022 21:08:00 +0200</pubDate>
  5155.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  5156.    <description><![CDATA[<p><a href="https://en.wikipedia.org/wiki/Nitter" title="nitter">nitter</a> provides a free and open source alternative front-end to Twitter. It talks with the API and does not show any JavaScript or ads (thus no 'forced-login' overlay after reading 5 tweets or similar nastiness).<br>
  5157. The source code for it is available on <a href="https://github.com/zedeus/nitter" title="">GitHub</a>.</p>
  5158. <p>It does a direct mapping of the profile URLs, thus <code>https://twitter.com/sheeshee</code> becomes <code>https://<b>nitter.net</b>/sheeshee</code></p>
  5159. ]]></description>
  5160.    <content:encoded><![CDATA[<p><a href="https://en.wikipedia.org/wiki/Nitter" title="nitter">nitter</a> provides a free and open source alternative front-end to Twitter. It talks with the API and does not show any JavaScript or ads (thus no 'forced-login' overlay after reading 5 tweets or similar nastiness).<br>
  5161. The source code for it is available on <a href="https://github.com/zedeus/nitter" title="">GitHub</a>.</p>
  5162. <p>It does a direct mapping of the profile URLs, thus <code>https://twitter.com/sheeshee</code> becomes <code>https://<b>nitter.net</b>/sheeshee</code></p>
  5163. ]]></content:encoded>
  5164.  </item>
  5165.  
  5166.  <item>
  5167.    <title>Blogging like 2002</title>
  5168.    <link>https://blog.x-way.org/Webdesign/2022/06/04/Blogging-like-2002.html</link>
  5169.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324302</guid>
  5170.    <dc:creator>Andreas Jaggi</dc:creator>
  5171.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5172.    <pubDate>Sat, 04 Jun 2022 11:32:00 +0200</pubDate>
  5173.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  5174.    <description><![CDATA[<p>On the occasion of the <a href="https://blog.x-way.org/Misc/2022/06/02/Happy-20th-Birthday-x-log.html" title="Happy 20th Birthday x-log">20th anniversary of this blog</a>, I've used <a href="https://archive.org/" title="Internet Archive">archive.org</a> to reconstruct the original HTML layout from back in the time and applied it to the Jekyll templates.</p>
  5175. <p>Enjoy the blog in all the (&lt;table&gt; based) glory from 2002 :-)</p>
  5176. ]]></description>
  5177.    <content:encoded><![CDATA[<p>On the occasion of the <a href="https://blog.x-way.org/Misc/2022/06/02/Happy-20th-Birthday-x-log.html" title="Happy 20th Birthday x-log">20th anniversary of this blog</a>, I've used <a href="https://archive.org/" title="Internet Archive">archive.org</a> to reconstruct the original HTML layout from back in the time and applied it to the Jekyll templates.</p>
  5178. <p>Enjoy the blog in all the (&lt;table&gt; based) glory from 2002 :-)</p>
  5179. ]]></content:encoded>
  5180.  </item>
  5181.  
  5182.  <item>
  5183.    <title>Happy 20th Birthday x-log</title>
  5184.    <link>https://blog.x-way.org/Misc/2022/06/02/Happy-20th-Birthday-x-log.html</link>
  5185.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324301</guid>
  5186.    <dc:creator>Andreas Jaggi</dc:creator>
  5187.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5188.    <pubDate>Thu, 02 Jun 2022 22:54:00 +0200</pubDate>
  5189.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  5190.    <description><![CDATA[<p>On June 2nd 2002 I published the first (test) entry in this weblog. The first entry has disappeared since (thus making <a href="https://blog.x-way.org/Webdesign/2002/06/03/Flash-Sites.html" title="Flash-Sites">the second entry</a> the first one in the <a href="https://blog.x-way.org/archive/archive-2002-06.html" title="x-log - Archive - 2002-06" >archive of June 2002</a>).</p>
  5191. <p><img src="https://blog.x-way.org/images/first_entry.png" alt="Screenshot of the first (test) entry" height="59" width="290"></p>
  5192. <p>Compared to <a href="https://web.archive.org/web/20020808101503/http://waterwave.ch/weblog/about.php" title="archive.org x-log about page from 2002">20 years ago</a>, the about page no longer needs to explain what a weblog is.<br>
  5193. Interesting though that the linked <a href="https://web.archive.org/web/20011204164555/http://www.jonet.org/data/beitraege.983619029.22602.html" title="archive.org: Peter Praschl: Was ist eigentlich ein Weblog?">definition of a weblog</a> from back then already did foresee the rise and fall in popularity of weblogs which happend during the last two decades.<br>To me it seems in the last 1-2 years there has been an increase again in activity around personal weblogs; curious to see if this revival trend continues.
  5194. </p>
  5195. <p>Also the weblog here has changed quite a bit. Initially its content was more on the pure web-logging side (commenting on interesting links I encountered during my daily Internet surfing) mixed with some kind of a journal/commentary of my day-to-day life. Later on it moved more towards a 'knowledge dump' on technical topics mixed with some music discoveries and random personal post from festivals and travels. And lately it has been rather sparse again with posts, still mostly on technical topics around coding, networking, security mixed with some personal posts commenting on the current world situation.<br>The frequency of posts also followed the changes in content where early on there sometimes were multiple posts per day, nowadays there can be multiple months without any post and there were even entire years where nothing new was posted; let's see how this goes in the future :-)</p>
  5196. <p>From the list of linked Blogs in 2002, only deep-resonance aka <a href="https://kniebes.com/" title="Markus Kniebes">mk</a> is still active, special shout-out to <a href="https://kniebes.com/now">Markus</a> for the continuous persistence.<br>To the next twenty years :-)</p>
  5197. ]]></description>
  5198.    <content:encoded><![CDATA[<p>On June 2nd 2002 I published the first (test) entry in this weblog. The first entry has disappeared since (thus making <a href="https://blog.x-way.org/Webdesign/2002/06/03/Flash-Sites.html" title="Flash-Sites">the second entry</a> the first one in the <a href="https://blog.x-way.org/archive/archive-2002-06.html" title="x-log - Archive - 2002-06" >archive of June 2002</a>).</p>
  5199. <p><img src="https://blog.x-way.org/images/first_entry.png" alt="Screenshot of the first (test) entry" height="59" width="290"></p>
  5200. <p>Compared to <a href="https://web.archive.org/web/20020808101503/http://waterwave.ch/weblog/about.php" title="archive.org x-log about page from 2002">20 years ago</a>, the about page no longer needs to explain what a weblog is.<br>
  5201. Interesting though that the linked <a href="https://web.archive.org/web/20011204164555/http://www.jonet.org/data/beitraege.983619029.22602.html" title="archive.org: Peter Praschl: Was ist eigentlich ein Weblog?">definition of a weblog</a> from back then already did foresee the rise and fall in popularity of weblogs which happend during the last two decades.<br>To me it seems in the last 1-2 years there has been an increase again in activity around personal weblogs; curious to see if this revival trend continues.
  5202. </p>
  5203. <p>Also the weblog here has changed quite a bit. Initially its content was more on the pure web-logging side (commenting on interesting links I encountered during my daily Internet surfing) mixed with some kind of a journal/commentary of my day-to-day life. Later on it moved more towards a 'knowledge dump' on technical topics mixed with some music discoveries and random personal post from festivals and travels. And lately it has been rather sparse again with posts, still mostly on technical topics around coding, networking, security mixed with some personal posts commenting on the current world situation.<br>The frequency of posts also followed the changes in content where early on there sometimes were multiple posts per day, nowadays there can be multiple months without any post and there were even entire years where nothing new was posted; let's see how this goes in the future :-)</p>
  5204. <p>From the list of linked Blogs in 2002, only deep-resonance aka <a href="https://kniebes.com/" title="Markus Kniebes">mk</a> is still active, special shout-out to <a href="https://kniebes.com/now">Markus</a> for the continuous persistence.<br>To the next twenty years :-)</p>
  5205. ]]></content:encoded>
  5206.  </item>
  5207.  
  5208.  <item>
  5209.    <title>mt-set-time</title>
  5210.    <link>https://blog.x-way.org/Networking/2022/03/26/mt-set-time.html</link>
  5211.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324300</guid>
  5212.    <dc:creator>Andreas Jaggi</dc:creator>
  5213.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5214.    <pubDate>Sat, 26 Mar 2022 16:15:00 +0100</pubDate>
  5215.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  5216.    <description><![CDATA[<p>A while ago I wrote a little tool to set the time on <a href="https://mikrotik.com/" title="MikroTik Routers and Wireless">MikroTik</a> devices.
  5217. It takes the current time from the local machine and does set it on the device through the API (while respecting the timezone configured on it).<br>
  5218. I mostly use it to set the proper time when the device time was completely off (when setting up a new device or when it has been powered off for a long time).
  5219. Afterwards NTP should take care of keeping the time in sync.</p>
  5220. <p>The tool is now available on GitHub together with installation and usage instructions: <a href="https://github.com/x-way/mt-set-time" title="x-way/mt-set-time: Set time on MikroTik routers">mt-set-time</a></p>
  5221. ]]></description>
  5222.    <content:encoded><![CDATA[<p>A while ago I wrote a little tool to set the time on <a href="https://mikrotik.com/" title="MikroTik Routers and Wireless">MikroTik</a> devices.
  5223. It takes the current time from the local machine and does set it on the device through the API (while respecting the timezone configured on it).<br>
  5224. I mostly use it to set the proper time when the device time was completely off (when setting up a new device or when it has been powered off for a long time).
  5225. Afterwards NTP should take care of keeping the time in sync.</p>
  5226. <p>The tool is now available on GitHub together with installation and usage instructions: <a href="https://github.com/x-way/mt-set-time" title="x-way/mt-set-time: Set time on MikroTik routers">mt-set-time</a></p>
  5227. ]]></content:encoded>
  5228.  </item>
  5229.  
  5230.  <item>
  5231.    <title>Fight Putin - Ride a Bike</title>
  5232.    <link>https://blog.x-way.org/Misc/2022/03/15/Fight-Putin-Ride-a-Bike.html</link>
  5233.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324299</guid>
  5234.    <dc:creator>Andreas Jaggi</dc:creator>
  5235.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5236.    <pubDate>Tue, 15 Mar 2022 12:55:00 +0100</pubDate>
  5237.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  5238.    <description><![CDATA[<p><a href="https://blog.x-way.org/images/fight-putin-ride-a-bike.jpeg" title="Fight Putin - Ride a Bike"><img src="https://blog.x-way.org/images/fight-putin-ride-a-bike_small.jpeg" alt="Fight Putin - Ride a Bike" height="515" width="300"></a></p>
  5239. ]]></description>
  5240.    <content:encoded><![CDATA[<p><a href="https://blog.x-way.org/images/fight-putin-ride-a-bike.jpeg" title="Fight Putin - Ride a Bike"><img src="https://blog.x-way.org/images/fight-putin-ride-a-bike_small.jpeg" alt="Fight Putin - Ride a Bike" height="515" width="300"></a></p>
  5241. ]]></content:encoded>
  5242.  </item>
  5243.  
  5244.  <item>
  5245.    <title>Dr Putin isch</title>
  5246.    <link>https://blog.x-way.org/Music/2022/02/27/Dr-Putin-isch.html</link>
  5247.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324298</guid>
  5248.    <dc:creator>Andreas Jaggi</dc:creator>
  5249.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5250.    <pubDate>Sun, 27 Feb 2022 11:53:00 +0100</pubDate>
  5251.    <category domain="https://blog.x-way.org/Music/">Music</category>
  5252.    <description><![CDATA[<p><a href="https://youtu.be/R-oqHUlptq8" title="Dr Putin isch e Hueresohn - YouTube">Dr Putin isch e Hueresohn</a></p>
  5253. <p>(<a href="https://www.reddit.com/r/BUENZLI/comments/t08crk/mis_neue_lieblingslied/" title="/r/BUENZLI on reddit.com">via</a>)</p>
  5254. ]]></description>
  5255.    <content:encoded><![CDATA[<p><a href="https://youtu.be/R-oqHUlptq8" title="Dr Putin isch e Hueresohn - YouTube">Dr Putin isch e Hueresohn</a></p>
  5256. <p>(<a href="https://www.reddit.com/r/BUENZLI/comments/t08crk/mis_neue_lieblingslied/" title="/r/BUENZLI on reddit.com">via</a>)</p>
  5257. ]]></content:encoded>
  5258.  </item>
  5259.  
  5260.  <item>
  5261.    <title>Non à la guerre! Nein zum Krieg!</title>
  5262.    <link>https://blog.x-way.org/Misc/2022/02/26/Non-a-la-guerre-Nein-zum-Krieg.html</link>
  5263.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324297</guid>
  5264.    <dc:creator>Andreas Jaggi</dc:creator>
  5265.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5266.    <pubDate>Sat, 26 Feb 2022 21:22:00 +0100</pubDate>
  5267.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  5268.    <description><![CDATA[<p>Today I went to Bern to the <a href="https://www.swissinfo.ch/eng/ukraine--up-to-20-000-people-march-in-bern-for-peace/47383836" title="Ukraine: up to 20'000 people march in Bern for peace">rally for peace</a>.<br>
  5269. My motivation was to show support for the people suffering in this war and to send a signal to our swiss government that the population wants clear participation in sanctions (while remaining neutral, the two in my view are not exclusive!).</p>
  5270. <p>Swiss media reported that this was the largest rally for peace in Switzerland since the <a href="https://blog.x-way.org/Misc/2003/03/22/Tous_ensemble_tous_ensemble_non_a_la_guerre.html" title="x-log - Tous ensemble, tous ensemble, non à la guerre!">rallies against the war in Iraq in 2003</a>. That I can link to my own blog entry regarding the rally for peace from 19 years ago, makes me sad.<br>
  5271. Clearly we as human species did not progress enough on this topic :-(</p>
  5272. <p>Besides showing up to the rally, I also did donate to the <a href="https://www.icrc.org/" title="International Committee of the Red Cross">ICRC</a> to provide humanitarian aid and I do encourage you to do the same.</p>
  5273. ]]></description>
  5274.    <content:encoded><![CDATA[<p>Today I went to Bern to the <a href="https://www.swissinfo.ch/eng/ukraine--up-to-20-000-people-march-in-bern-for-peace/47383836" title="Ukraine: up to 20'000 people march in Bern for peace">rally for peace</a>.<br>
  5275. My motivation was to show support for the people suffering in this war and to send a signal to our swiss government that the population wants clear participation in sanctions (while remaining neutral, the two in my view are not exclusive!).</p>
  5276. <p>Swiss media reported that this was the largest rally for peace in Switzerland since the <a href="https://blog.x-way.org/Misc/2003/03/22/Tous_ensemble_tous_ensemble_non_a_la_guerre.html" title="x-log - Tous ensemble, tous ensemble, non à la guerre!">rallies against the war in Iraq in 2003</a>. That I can link to my own blog entry regarding the rally for peace from 19 years ago, makes me sad.<br>
  5277. Clearly we as human species did not progress enough on this topic :-(</p>
  5278. <p>Besides showing up to the rally, I also did donate to the <a href="https://www.icrc.org/" title="International Committee of the Red Cross">ICRC</a> to provide humanitarian aid and I do encourage you to do the same.</p>
  5279. ]]></content:encoded>
  5280.  </item>
  5281.  
  5282.  <item>
  5283.    <title>EFF Member Badge 2022</title>
  5284.    <link>https://blog.x-way.org/Badges/2022/02/20/EFF-Member-Badge-2022.html</link>
  5285.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324296</guid>
  5286.    <dc:creator>Andreas Jaggi</dc:creator>
  5287.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5288.    <pubDate>Sun, 20 Feb 2022 09:22:00 +0100</pubDate>
  5289.    <category domain="https://blog.x-way.org/Badges/">Badges</category>
  5290.    <description><![CDATA[<p><a href="https://www.eff.org/" title="Electronic Frontier Foundation | Defending your rights in the digital world"><img src="https://blog.x-way.org/images/member-badge-2022b.jpg" alt="EFF Member Badge 2022" height="300" width="300"></a></p>
  5291. ]]></description>
  5292.    <content:encoded><![CDATA[<p><a href="https://www.eff.org/" title="Electronic Frontier Foundation | Defending your rights in the digital world"><img src="https://blog.x-way.org/images/member-badge-2022b.jpg" alt="EFF Member Badge 2022" height="300" width="300"></a></p>
  5293. ]]></content:encoded>
  5294.  </item>
  5295.  
  5296.  <item>
  5297.    <title>vtysock</title>
  5298.    <link>https://blog.x-way.org/Networking/2022/01/29/vtysock.html</link>
  5299.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324295</guid>
  5300.    <dc:creator>Andreas Jaggi</dc:creator>
  5301.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5302.    <pubDate>Sat, 29 Jan 2022 21:38:00 +0100</pubDate>
  5303.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  5304.    <description><![CDATA[<p>After switching my Debian hosts from <a href="https://en.wikipedia.org/wiki/Quagga_(software)" title="Quagga Software Routing Suite">Quagga</a> to <a href="https://frrouting.org/" title="FRRouting">FRRouting</a>, I noticed that running vtysh has become quite a bit slower especially when making multiple calls to it from my status/monitoring scripts.
  5305. <br>This has also been observed by other users of FRRouting (there's an open issue in their bugtracker: <a href="https://github.com/FRRouting/frr/issues/7799" title="vtysh is significantly slower in FRR than Quagga">#7799</a>).</p>
  5306. <p>The Prometheus <a href="https://github.com/tynany/frr_exporter" title="Prometheus exporter for Free Range Routing">frr_exporter</a> works around this by directly sending commands to the UNIX sockets of the FRR daemons (<a href="https://github.com/tynany/frr_exporter/pull/50" title="frr_exporter - refactor: send cmds to unix socket">PR</a>).</p>
  5307. <p>To use the same approach in my monitoring scripts, I wrote a small utility which acts as a drop-in replacement for vtysh and sends the commands directly to the UNIX sockets of the FRR daemons: <a href="https://github.com/x-way/vtysock" title="x-way/vtysock - a quick vtysh replacement">vtysock</a>
  5308. <br>By skipping the parsing and validation checks done in vtysh, vtysock can achieve a significant speed improvement when executing commands.</p>
  5309. ]]></description>
  5310.    <content:encoded><![CDATA[<p>After switching my Debian hosts from <a href="https://en.wikipedia.org/wiki/Quagga_(software)" title="Quagga Software Routing Suite">Quagga</a> to <a href="https://frrouting.org/" title="FRRouting">FRRouting</a>, I noticed that running vtysh has become quite a bit slower especially when making multiple calls to it from my status/monitoring scripts.
  5311. <br>This has also been observed by other users of FRRouting (there's an open issue in their bugtracker: <a href="https://github.com/FRRouting/frr/issues/7799" title="vtysh is significantly slower in FRR than Quagga">#7799</a>).</p>
  5312. <p>The Prometheus <a href="https://github.com/tynany/frr_exporter" title="Prometheus exporter for Free Range Routing">frr_exporter</a> works around this by directly sending commands to the UNIX sockets of the FRR daemons (<a href="https://github.com/tynany/frr_exporter/pull/50" title="frr_exporter - refactor: send cmds to unix socket">PR</a>).</p>
  5313. <p>To use the same approach in my monitoring scripts, I wrote a small utility which acts as a drop-in replacement for vtysh and sends the commands directly to the UNIX sockets of the FRR daemons: <a href="https://github.com/x-way/vtysock" title="x-way/vtysock - a quick vtysh replacement">vtysock</a>
  5314. <br>By skipping the parsing and validation checks done in vtysh, vtysock can achieve a significant speed improvement when executing commands.</p>
  5315. ]]></content:encoded>
  5316.  </item>
  5317.  
  5318.  <item>
  5319.    <title>Force SSH to use IPv6</title>
  5320.    <link>https://blog.x-way.org/Networking/2022/01/23/Force-SSH-to-use-IPv6.html</link>
  5321.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324294</guid>
  5322.    <dc:creator>Andreas Jaggi</dc:creator>
  5323.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5324.    <pubDate>Sun, 23 Jan 2022 10:53:00 +0100</pubDate>
  5325.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  5326.    <description><![CDATA[<p>In situations where IPv6 connectivity performs better than IPv4, you might want to force SSH to use IPv6. In interactive mode this can be achieved with the <code>-6</code> commandline parameter.<br>But in situations where you can't modify the commandline parameters a different approach is needed (for example in rsync backup scripts which use SSH as underlying transport layer).</p>
  5327. <p>We can use the <a href="https://man.openbsd.org/ssh_config.5" title="ssh_config(5) - OpenBSD manual pages">ssh_config</a> file to encforce that IPv6 is used for a specific host:</p>
  5328. <pre>
  5329. Host myipv6host
  5330. AddressFamily inet6
  5331. </pre>
  5332. <p>This instructs all SSH commands to use IPv6 when connecting to myipv6host.</p>
  5333. <p>The same approach also works to force usage of <a href="https://blog.x-way.org/Networking/2013/07/05/Mandatory-requirement-for-all-non-IPv6-capable-products.html">Legacy IP</a> by specyfing <code>inet</code> as address family.</p>
  5334. ]]></description>
  5335.    <content:encoded><![CDATA[<p>In situations where IPv6 connectivity performs better than IPv4, you might want to force SSH to use IPv6. In interactive mode this can be achieved with the <code>-6</code> commandline parameter.<br>But in situations where you can't modify the commandline parameters a different approach is needed (for example in rsync backup scripts which use SSH as underlying transport layer).</p>
  5336. <p>We can use the <a href="https://man.openbsd.org/ssh_config.5" title="ssh_config(5) - OpenBSD manual pages">ssh_config</a> file to encforce that IPv6 is used for a specific host:</p>
  5337. <pre>
  5338. Host myipv6host
  5339. AddressFamily inet6
  5340. </pre>
  5341. <p>This instructs all SSH commands to use IPv6 when connecting to myipv6host.</p>
  5342. <p>The same approach also works to force usage of <a href="https://blog.x-way.org/Networking/2013/07/05/Mandatory-requirement-for-all-non-IPv6-capable-products.html">Legacy IP</a> by specyfing <code>inet</code> as address family.</p>
  5343. ]]></content:encoded>
  5344.  </item>
  5345.  
  5346.  <item>
  5347.    <title>Google Analytics removed</title>
  5348.    <link>https://blog.x-way.org/Webdesign/2022/01/19/Google-Analytics-removed.html</link>
  5349.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324293</guid>
  5350.    <dc:creator>Andreas Jaggi</dc:creator>
  5351.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5352.    <pubDate>Wed, 19 Jan 2022 22:45:00 +0100</pubDate>
  5353.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  5354.    <description><![CDATA[<p>After running it for a bit more than a decade, I've now removed again the Google Analytics tracking from this site. It does not feel appropriate anymore on a personal website.<br>At the moment no alternative statistics solution is in place yet, but I could imagine setting up a self-hosted solution like <a href="https://matomo.org/" title="Matomo Analytics - The Google Analytics alternative that protects your data">Matomo</a> or <a href="https://plausible.io/" title="Plausible Analytics | Simple, privacy-friendly Google Analytics alternative">Plausible</a> in the future.</p>
  5355. ]]></description>
  5356.    <content:encoded><![CDATA[<p>After running it for a bit more than a decade, I've now removed again the Google Analytics tracking from this site. It does not feel appropriate anymore on a personal website.<br>At the moment no alternative statistics solution is in place yet, but I could imagine setting up a self-hosted solution like <a href="https://matomo.org/" title="Matomo Analytics - The Google Analytics alternative that protects your data">Matomo</a> or <a href="https://plausible.io/" title="Plausible Analytics | Simple, privacy-friendly Google Analytics alternative">Plausible</a> in the future.</p>
  5357. ]]></content:encoded>
  5358.  </item>
  5359.  
  5360.  <item>
  5361.    <title>Google Analytics declared illegal in the EU</title>
  5362.    <link>https://blog.x-way.org/Webdesign/2022/01/19/Google-Analytics-declared-illegal-in-the-EU.html</link>
  5363.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324292</guid>
  5364.    <dc:creator>Andreas Jaggi</dc:creator>
  5365.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5366.    <pubDate>Wed, 19 Jan 2022 20:45:00 +0100</pubDate>
  5367.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  5368.    <description><![CDATA[<p><a href="https://tuta.com/blog/posts/is-google-analytics-illegal/" title="Google Analytics declared illegal in the EU">Google Analytics declared illegal in the EU</a>.</p>
  5369. ]]></description>
  5370.    <content:encoded><![CDATA[<p><a href="https://tuta.com/blog/posts/is-google-analytics-illegal/" title="Google Analytics declared illegal in the EU">Google Analytics declared illegal in the EU</a>.</p>
  5371. ]]></content:encoded>
  5372.  </item>
  5373.  
  5374.  <item>
  5375.    <title>Wordle</title>
  5376.    <link>https://blog.x-way.org/Misc/2022/01/05/Wordle.html</link>
  5377.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324291</guid>
  5378.    <dc:creator>Andreas Jaggi</dc:creator>
  5379.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5380.    <pubDate>Wed, 05 Jan 2022 07:09:00 +0100</pubDate>
  5381.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  5382.    <description><![CDATA[<p><a href="https://www.nytimes.com/games/wordle/index.html" title="Wordle - A daily word game">Wordle</a> seems to be the trending topic these days.<br>It's a word game similar to the french <a href="https://fr.wikipedia.org/wiki/Motus_(jeu_t%C3%A9l%C3%A9vis%C3%A9)" title="Motus - Wikipedia">Motus</a> game show (resp. the american <a href="https://en.wikipedia.org/wiki/Lingo_(American_game_show)" title="Lingo - Wikipedia">Lingo</a> game show).</p>
  5383. <p>Wordle 200 4/6<br>
  5384. <br>
  5385. ⬜⬜⬜🟩⬜<br>
  5386. ⬜⬜🟨🟩⬜<br>
  5387. ⬜⬜⬜🟩🟩<br>
  5388. 🟩🟩🟩🟩🟩<br>
  5389. </p>
  5390. ]]></description>
  5391.    <content:encoded><![CDATA[<p><a href="https://www.nytimes.com/games/wordle/index.html" title="Wordle - A daily word game">Wordle</a> seems to be the trending topic these days.<br>It's a word game similar to the french <a href="https://fr.wikipedia.org/wiki/Motus_(jeu_t%C3%A9l%C3%A9vis%C3%A9)" title="Motus - Wikipedia">Motus</a> game show (resp. the american <a href="https://en.wikipedia.org/wiki/Lingo_(American_game_show)" title="Lingo - Wikipedia">Lingo</a> game show).</p>
  5392. <p>Wordle 200 4/6<br>
  5393. <br>
  5394. ⬜⬜⬜🟩⬜<br>
  5395. ⬜⬜🟨🟩⬜<br>
  5396. ⬜⬜⬜🟩🟩<br>
  5397. 🟩🟩🟩🟩🟩<br>
  5398. </p>
  5399. ]]></content:encoded>
  5400.  </item>
  5401.  
  5402.  <item>
  5403.    <title>Y2K22</title>
  5404.    <link>https://blog.x-way.org/Coding/2022/01/01/Y2K22.html</link>
  5405.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324290</guid>
  5406.    <dc:creator>Andreas Jaggi</dc:creator>
  5407.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5408.    <pubDate>Sat, 01 Jan 2022 21:48:00 +0100</pubDate>
  5409.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  5410.    <description><![CDATA[<p>Turns out that signed 32-bit numbers can be exhausted long before <a href="https://en.wikipedia.org/wiki/Year_2038_problem" title="Year 2038 problem">Y2038</a>, when you use them to store time in YYMMDDHHMM format. (<a href="https://rachelbythebay.com/w/2022/01/01/baddate/" title="rachelbythebay - YYMMDDHHMM just overflowed a signed 32 bit int">via</a>)</p>
  5411. ]]></description>
  5412.    <content:encoded><![CDATA[<p>Turns out that signed 32-bit numbers can be exhausted long before <a href="https://en.wikipedia.org/wiki/Year_2038_problem" title="Year 2038 problem">Y2038</a>, when you use them to store time in YYMMDDHHMM format. (<a href="https://rachelbythebay.com/w/2022/01/01/baddate/" title="rachelbythebay - YYMMDDHHMM just overflowed a signed 32 bit int">via</a>)</p>
  5413. ]]></content:encoded>
  5414.  </item>
  5415.  
  5416.  <item>
  5417.    <title>Open Source on Mars</title>
  5418.    <link>https://blog.x-way.org/Coding/2021/04/19/Open-Source-on-Mars.html</link>
  5419.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324289</guid>
  5420.    <dc:creator>Andreas Jaggi</dc:creator>
  5421.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5422.    <pubDate>Mon, 19 Apr 2021 16:21:00 +0200</pubDate>
  5423.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  5424.    <description><![CDATA[<p>Received a badge from GitHub's <a href="https://github.com/readme/nasa-ingenuity-helicopter" title="Open Source on Mars: Community powers NASA’s Ingenuity Helicopter - The ReadMe Project">Open Source on Mars</a> <a href="https://github.blog/2021-04-19-open-source-goes-to-mars/" title="Open source goes to Mars - The GitHub Blog">initiative</a> :-)</p>
  5425.  
  5426. <p><a href="https://github.com/x-way"><img src="https://blog.x-way.org/images/github_mars_2020_helicopter_contributor.png" alt="Mars 2020 Helicopter Contributor - Andreas Jaggi contributed code to 1 repository used in the Mars 2020 Helicopter Mission: torvalds/linux" title="Mars 2020 Helicopter Contributor - Andreas Jaggi contributed code to 1 repository used in the Mars 2020 Helicopter Mission: torvalds/linux" width="333" height="117"></a></p>
  5427. ]]></description>
  5428.    <content:encoded><![CDATA[<p>Received a badge from GitHub's <a href="https://github.com/readme/nasa-ingenuity-helicopter" title="Open Source on Mars: Community powers NASA’s Ingenuity Helicopter - The ReadMe Project">Open Source on Mars</a> <a href="https://github.blog/2021-04-19-open-source-goes-to-mars/" title="Open source goes to Mars - The GitHub Blog">initiative</a> :-)</p>
  5429.  
  5430. <p><a href="https://github.com/x-way"><img src="https://blog.x-way.org/images/github_mars_2020_helicopter_contributor.png" alt="Mars 2020 Helicopter Contributor - Andreas Jaggi contributed code to 1 repository used in the Mars 2020 Helicopter Mission: torvalds/linux" title="Mars 2020 Helicopter Contributor - Andreas Jaggi contributed code to 1 repository used in the Mars 2020 Helicopter Mission: torvalds/linux" width="333" height="117"></a></p>
  5431. ]]></content:encoded>
  5432.  </item>
  5433.  
  5434.  <item>
  5435.    <title>Top 21 Security Experts to follow on Twitter in 2021</title>
  5436.    <link>https://blog.x-way.org/Networking/2021/04/17/Top-21-Security-Experts-to-follow-on-Twitter-in-2021.html</link>
  5437.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324288</guid>
  5438.    <dc:creator>Andreas Jaggi</dc:creator>
  5439.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5440.    <pubDate>Sat, 17 Apr 2021 06:58:00 +0200</pubDate>
  5441.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  5442.    <description><![CDATA[<p>From the <a href="https://web.archive.org/web/20210412004031/https://securityboulevard.com/2021/04/top-21-cybersecurity-experts-you-must-follow-on-twitter-in-2021/" title="Top-21 Cybersecurity Experts You Must Follow on Twitter in 2021 - Security Boulevard (archive.org)">article on Security Boulevard</a>.</p>
  5443. <ol>
  5444. <li><a href="https://twitter.com/rafaybaloch" title="Rafay Baloch (@rafaybaloch) / Twitter">Rafay Baloch</a></li>
  5445. <li><a href="https://twitter.com/troyhunt" title="Troy Hunt (@troyhunt) / Twitter">Troy Hunt</a></li>
  5446. <li><a href="https://twitter.com/kevinmitnick" title="Kevin Mitnick (@kevinmitnick) / Twitter">Kevin Mitnick</a></li>
  5447. <li><a href="https://twitter.com/RachelTobac" title="Rachel Tobac (@RachelTobac) / Twitter">Rachel Tobac</a></li>
  5448. <li><a href="https://twitter.com/mikko" title="Mikko Hyppönen (@mikko) / Twitter">Mikko Hyppönen</a></li>
  5449. <li><a href="https://twitter.com/k8em0" title="Katie Moussouris (@k8em0) / Twitter">Katie Moussouris</a></li>
  5450. <li><a href="https://twitter.com/schneierblog" title="Bruce Schneier (@schneierblog) / Twitter">Bruce Schneier</a></li>
  5451. <li><a href="https://twitter.com/briankrebs" title="Brian Krebs (@briankrebs) / Twitter">Brian Krebs</a></li>
  5452. <li><a href="https://twitter.com/jeremiahg" title="Jeremiah Grossman (@jeremiahg) / Twitter">Jeremiah Grossman</a></li>
  5453. <li><a href="https://twitter.com/e_kaspersky" title="Eugene Kaspersky (@e_kaspersky) / Twitter">Eugene Kaspersky</a></li>
  5454. <li><a href="https://twitter.com/govcso" title="Dan Lohemann (@govcso) / Twitter">Dan Lohemann</a></li>
  5455. <li><a href="https://twitter.com/CybersecuritySF" title="Steve Morgan (@CybersecuritySF) / Twitter">Steve Morgan</a></li>
  5456. <li><a href="https://twitter.com/TylerCohenWood" title="Tyler Cohen Wood (@TylerCohenWood) / Twitter">Tyler Cohen Wood</a></li>
  5457. <li><a href="https://twitter.com/gcluley" title="Graham Cluley (@gcluley) / Twitter">Graham Cluley</a></li>
  5458. <li><a href="https://twitter.com/TrackerPayton" title="Theresa Payton (@TrackerPayton) / Twitter">Theresa Payton</a></li>
  5459. <li><a href="https://twitter.com/Shirastweet" title="Shira Rubinoff (@Shirastweet) / Twitter">Shira Rubinoff</a></li>
  5460. <li><a href="https://twitter.com/evacide" title="Eva Galperin (@evacide) / Twitter">Eva Galperin</a></li>
  5461. <li><a href="https://twitter.com/marcusjcarey" title="Marcus J. Carey (@marcusjcarey) / Twitter">Marcus J. Carey</a></li>
  5462. <li><a href="https://twitter.com/jaysonstreet" title="Jayson E Street (@jaysonstreet) / Twitter">Jayson E Street</a></li>
  5463. <li><a href="https://twitter.com/securityweekly" title="Paul Asadoorian (@securityweekly) / Twitter">Paul Asadoorian</a></li>
  5464. <li><a href="https://twitter.com/adam_k_levin" title="Adam K. Levin (@adam_k_levin) / Twitter">Adam K. Levin</a></li>
  5465. </ol>
  5466. ]]></description>
  5467.    <content:encoded><![CDATA[<p>From the <a href="https://web.archive.org/web/20210412004031/https://securityboulevard.com/2021/04/top-21-cybersecurity-experts-you-must-follow-on-twitter-in-2021/" title="Top-21 Cybersecurity Experts You Must Follow on Twitter in 2021 - Security Boulevard (archive.org)">article on Security Boulevard</a>.</p>
  5468. <ol>
  5469. <li><a href="https://twitter.com/rafaybaloch" title="Rafay Baloch (@rafaybaloch) / Twitter">Rafay Baloch</a></li>
  5470. <li><a href="https://twitter.com/troyhunt" title="Troy Hunt (@troyhunt) / Twitter">Troy Hunt</a></li>
  5471. <li><a href="https://twitter.com/kevinmitnick" title="Kevin Mitnick (@kevinmitnick) / Twitter">Kevin Mitnick</a></li>
  5472. <li><a href="https://twitter.com/RachelTobac" title="Rachel Tobac (@RachelTobac) / Twitter">Rachel Tobac</a></li>
  5473. <li><a href="https://twitter.com/mikko" title="Mikko Hyppönen (@mikko) / Twitter">Mikko Hyppönen</a></li>
  5474. <li><a href="https://twitter.com/k8em0" title="Katie Moussouris (@k8em0) / Twitter">Katie Moussouris</a></li>
  5475. <li><a href="https://twitter.com/schneierblog" title="Bruce Schneier (@schneierblog) / Twitter">Bruce Schneier</a></li>
  5476. <li><a href="https://twitter.com/briankrebs" title="Brian Krebs (@briankrebs) / Twitter">Brian Krebs</a></li>
  5477. <li><a href="https://twitter.com/jeremiahg" title="Jeremiah Grossman (@jeremiahg) / Twitter">Jeremiah Grossman</a></li>
  5478. <li><a href="https://twitter.com/e_kaspersky" title="Eugene Kaspersky (@e_kaspersky) / Twitter">Eugene Kaspersky</a></li>
  5479. <li><a href="https://twitter.com/govcso" title="Dan Lohemann (@govcso) / Twitter">Dan Lohemann</a></li>
  5480. <li><a href="https://twitter.com/CybersecuritySF" title="Steve Morgan (@CybersecuritySF) / Twitter">Steve Morgan</a></li>
  5481. <li><a href="https://twitter.com/TylerCohenWood" title="Tyler Cohen Wood (@TylerCohenWood) / Twitter">Tyler Cohen Wood</a></li>
  5482. <li><a href="https://twitter.com/gcluley" title="Graham Cluley (@gcluley) / Twitter">Graham Cluley</a></li>
  5483. <li><a href="https://twitter.com/TrackerPayton" title="Theresa Payton (@TrackerPayton) / Twitter">Theresa Payton</a></li>
  5484. <li><a href="https://twitter.com/Shirastweet" title="Shira Rubinoff (@Shirastweet) / Twitter">Shira Rubinoff</a></li>
  5485. <li><a href="https://twitter.com/evacide" title="Eva Galperin (@evacide) / Twitter">Eva Galperin</a></li>
  5486. <li><a href="https://twitter.com/marcusjcarey" title="Marcus J. Carey (@marcusjcarey) / Twitter">Marcus J. Carey</a></li>
  5487. <li><a href="https://twitter.com/jaysonstreet" title="Jayson E Street (@jaysonstreet) / Twitter">Jayson E Street</a></li>
  5488. <li><a href="https://twitter.com/securityweekly" title="Paul Asadoorian (@securityweekly) / Twitter">Paul Asadoorian</a></li>
  5489. <li><a href="https://twitter.com/adam_k_levin" title="Adam K. Levin (@adam_k_levin) / Twitter">Adam K. Levin</a></li>
  5490. </ol>
  5491. ]]></content:encoded>
  5492.  </item>
  5493.  
  5494.  <item>
  5495.    <title>security.txt</title>
  5496.    <link>https://blog.x-way.org/Webdesign/2021/03/28/security-txt.html</link>
  5497.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324287</guid>
  5498.    <dc:creator>Andreas Jaggi</dc:creator>
  5499.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5500.    <pubDate>Sun, 28 Mar 2021 08:16:00 +0200</pubDate>
  5501.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  5502.    <description><![CDATA[<p>This website now also serves a <a href="https://securitytxt.org/" title="security.txt: Proposed standard for defining security policies">security.txt</a> file which is a standardized way of making security contact information available. (<a href="https://en.wikipedia.org/wiki/Security.txt" title="security.txt - Wikipedia">Wikipedia</a>)</p>
  5503. <p>The file is available in two locations <a href="https://blog.x-way.org/security.txt">/security.txt</a> (the classic location) and <a href="https://blog.x-way.org/.well-known/security.txt">/.well-known/security.txt</a> (the standard location following RFC8615).</p>
  5504.  
  5505. <p>To easily add the file on all my domains, I'm using the following nginx config snippet.</p>
  5506. <pre>location /security.txt {
  5507. add_header Content-Type 'text/plain';
  5508. add_header Cache-Control 'no-cache, no-store, must-revalidate';
  5509. add_header Pragma 'no-cache';
  5510. add_header Expires '0';
  5511. add_header Vary '*';
  5512. return 200 "Contact: mailto:andreas+security.txt@jaggi.info\nExpires: Tue, 19 Jan 2038 03:14:07 +0000\nEncryption: http://andreas-jaggi.ch/A3A54203.asc\n";
  5513. }
  5514.  
  5515. location /.well-known/security.txt {
  5516. add_header Content-Type 'text/plain';
  5517. add_header Cache-Control 'no-cache, no-store, must-revalidate';
  5518. add_header Pragma 'no-cache';
  5519. add_header Expires '0';
  5520. add_header Vary '*';
  5521. return 200 "Contact: mailto:andreas+security.txt@jaggi.info\nExpires: Tue, 19 Jan 2038 03:14:07 +0000\nEncryption: http://andreas-jaggi.ch/A3A54203.asc\n";
  5522. }</pre>
  5523.  
  5524. <p>This snippet is stored in a dedicated file (/etc/nginx/conf_includes/securitytxt) and is included in the various server config blocks like this:</p>
  5525. <pre>server {
  5526. server_name example.com;
  5527.  
  5528. include /etc/nginx/conf_includes/securitytxt;
  5529.  
  5530. location / {
  5531. # rest of website
  5532. }
  5533. }</pre>
  5534. ]]></description>
  5535.    <content:encoded><![CDATA[<p>This website now also serves a <a href="https://securitytxt.org/" title="security.txt: Proposed standard for defining security policies">security.txt</a> file which is a standardized way of making security contact information available. (<a href="https://en.wikipedia.org/wiki/Security.txt" title="security.txt - Wikipedia">Wikipedia</a>)</p>
  5536. <p>The file is available in two locations <a href="https://blog.x-way.org/security.txt">/security.txt</a> (the classic location) and <a href="https://blog.x-way.org/.well-known/security.txt">/.well-known/security.txt</a> (the standard location following RFC8615).</p>
  5537.  
  5538. <p>To easily add the file on all my domains, I'm using the following nginx config snippet.</p>
  5539. <pre>location /security.txt {
  5540. add_header Content-Type 'text/plain';
  5541. add_header Cache-Control 'no-cache, no-store, must-revalidate';
  5542. add_header Pragma 'no-cache';
  5543. add_header Expires '0';
  5544. add_header Vary '*';
  5545. return 200 "Contact: mailto:andreas+security.txt@jaggi.info\nExpires: Tue, 19 Jan 2038 03:14:07 +0000\nEncryption: http://andreas-jaggi.ch/A3A54203.asc\n";
  5546. }
  5547.  
  5548. location /.well-known/security.txt {
  5549. add_header Content-Type 'text/plain';
  5550. add_header Cache-Control 'no-cache, no-store, must-revalidate';
  5551. add_header Pragma 'no-cache';
  5552. add_header Expires '0';
  5553. add_header Vary '*';
  5554. return 200 "Contact: mailto:andreas+security.txt@jaggi.info\nExpires: Tue, 19 Jan 2038 03:14:07 +0000\nEncryption: http://andreas-jaggi.ch/A3A54203.asc\n";
  5555. }</pre>
  5556.  
  5557. <p>This snippet is stored in a dedicated file (/etc/nginx/conf_includes/securitytxt) and is included in the various server config blocks like this:</p>
  5558. <pre>server {
  5559. server_name example.com;
  5560.  
  5561. include /etc/nginx/conf_includes/securitytxt;
  5562.  
  5563. location / {
  5564. # rest of website
  5565. }
  5566. }</pre>
  5567. ]]></content:encoded>
  5568.  </item>
  5569.  
  5570.  <item>
  5571.    <title>Fixing 'snmpd[19784]: error on subcontainer 'ia_addr' insert (-1)' messages</title>
  5572.    <link>https://blog.x-way.org/Linux/2021/02/13/Fixing-snmpd-error-on-subcontainer-ia-addr-insert-messages.html</link>
  5573.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324284</guid>
  5574.    <dc:creator>Andreas Jaggi</dc:creator>
  5575.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5576.    <pubDate>Sat, 13 Feb 2021 08:57:00 +0100</pubDate>
  5577.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  5578.    <description><![CDATA[<p>The default configuration of snmpd on Debian has debug level logging enabled and thus we end up with a constant flood of these messages in /var/log/syslog</p>
  5579. <pre>snmpd[19784]: error on subcontainer 'ia_addr' insert (-1)</pre>
  5580. <p>The fix is to lower the logging level, which can be accomplished like this on systems with systemd:</p>
  5581. <pre>cp /lib/systemd/system/snmpd.service /etc/systemd/system/snmpd.service
  5582. sed -i 's/Lsd/LS6d/' /etc/systemd/system/snmpd.service
  5583. systemctl daemon-reload
  5584. systemctl restart snmpd</pre>
  5585. <p>On systems without systemd, the logging level is set by the init script (unless explicitly configured in /etc/default/snmpd), and can be changed like this:</p>
  5586. <pre>sed -i 's/Lsd/LS6d/g' /etc/default/snmpd
  5587. sed -i 's/Lsd/LS6d/g' /etc/init.d/snmpd
  5588. service snmpd restart</pre>
  5589. ]]></description>
  5590.    <content:encoded><![CDATA[<p>The default configuration of snmpd on Debian has debug level logging enabled and thus we end up with a constant flood of these messages in /var/log/syslog</p>
  5591. <pre>snmpd[19784]: error on subcontainer 'ia_addr' insert (-1)</pre>
  5592. <p>The fix is to lower the logging level, which can be accomplished like this on systems with systemd:</p>
  5593. <pre>cp /lib/systemd/system/snmpd.service /etc/systemd/system/snmpd.service
  5594. sed -i 's/Lsd/LS6d/' /etc/systemd/system/snmpd.service
  5595. systemctl daemon-reload
  5596. systemctl restart snmpd</pre>
  5597. <p>On systems without systemd, the logging level is set by the init script (unless explicitly configured in /etc/default/snmpd), and can be changed like this:</p>
  5598. <pre>sed -i 's/Lsd/LS6d/g' /etc/default/snmpd
  5599. sed -i 's/Lsd/LS6d/g' /etc/init.d/snmpd
  5600. service snmpd restart</pre>
  5601. ]]></content:encoded>
  5602.  </item>
  5603.  
  5604.  <item>
  5605.    <title>Embracing the future with SolNet</title>
  5606.    <link>https://blog.x-way.org/Networking/2021/02/04/Embracing-the-future-with-SolNet.html</link>
  5607.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324285</guid>
  5608.    <dc:creator>Andreas Jaggi</dc:creator>
  5609.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5610.    <pubDate>Thu, 04 Feb 2021 10:01:00 +0100</pubDate>
  5611.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  5612.    <description><![CDATA[<p>This was the initial state of my new <a href="https://www.solnet.ch/" title="SolNet - Internet &amp; Solution Provider">SolNet</a> fibre connection:</p>
  5613. <p><img src="https://blog.x-way.org/images/solnet-ipv6-only.png" alt="SolNet connection with native IPv6 but no IPv4" width="487" height="61"></p>
  5614. <p>As I am a proponent of IPv6 this made me very happy, but unfortunately about 20% of my daily websites only offer <a href="https://blog.x-way.org/Networking/2013/07/05/Mandatory-requirement-for-all-non-IPv6-capable-products.html">legacy Internet</a> (which later on I got working as well).</p>
  5615. ]]></description>
  5616.    <content:encoded><![CDATA[<p>This was the initial state of my new <a href="https://www.solnet.ch/" title="SolNet - Internet &amp; Solution Provider">SolNet</a> fibre connection:</p>
  5617. <p><img src="https://blog.x-way.org/images/solnet-ipv6-only.png" alt="SolNet connection with native IPv6 but no IPv4" width="487" height="61"></p>
  5618. <p>As I am a proponent of IPv6 this made me very happy, but unfortunately about 20% of my daily websites only offer <a href="https://blog.x-way.org/Networking/2013/07/05/Mandatory-requirement-for-all-non-IPv6-capable-products.html">legacy Internet</a> (which later on I got working as well).</p>
  5619. ]]></content:encoded>
  5620.  </item>
  5621.  
  5622.  <item>
  5623.    <title>Prozentrechnen ist schwer</title>
  5624.    <link>https://blog.x-way.org/Misc/2021/02/04/Prozentrechnen-ist-schwer.html</link>
  5625.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324286</guid>
  5626.    <dc:creator>Andreas Jaggi</dc:creator>
  5627.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5628.    <pubDate>Thu, 04 Feb 2021 08:20:00 +0100</pubDate>
  5629.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  5630.    <description><![CDATA[<p><a href="https://www.truewealth.ch/" title="True Wealth - Swiss Online Wealth Management">TrueWealth</a> hat's nicht so mit Prozentrechnen:</p>
  5631. <p><img src="https://blog.x-way.org/images/truewealth-prozentrechnen.png" title="6 + 33 + 3 + 12 + 47 = ?" alt="6 + 33 + 3 + 12 + 47 = ?" width="335" height="196"></p>
  5632. ]]></description>
  5633.    <content:encoded><![CDATA[<p><a href="https://www.truewealth.ch/" title="True Wealth - Swiss Online Wealth Management">TrueWealth</a> hat's nicht so mit Prozentrechnen:</p>
  5634. <p><img src="https://blog.x-way.org/images/truewealth-prozentrechnen.png" title="6 + 33 + 3 + 12 + 47 = ?" alt="6 + 33 + 3 + 12 + 47 = ?" width="335" height="196"></p>
  5635. ]]></content:encoded>
  5636.  </item>
  5637.  
  5638.  <item>
  5639.    <title>Using your own router on a Sunrise fiber line</title>
  5640.    <link>https://blog.x-way.org/Networking/2020/12/05/Using-your-own-router-on-a-Sunrise-fiber-line.html</link>
  5641.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324283</guid>
  5642.    <dc:creator>Andreas Jaggi</dc:creator>
  5643.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5644.    <pubDate>Sat, 05 Dec 2020 22:26:00 +0100</pubDate>
  5645.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  5646.    <description><![CDATA[<p>Sunrise does not like when people run their own router on a fiber line. While they do not directly forbid it, they don't provide any of the required configuration parameters which makes it quite hard to use your own router.</p>
  5647. <p>Below you'll find the required configuration parameters to make your own router connect with IPv4 and IPv6 on a Sunrise fiber line.<br>Beware though that especially the VLAN configuration might be different depending on your city, the following worked for me in Zürich.</p>
  5648. <p>Also, please note that I do not recommend Sunrise as Internet provider (as a matter of fact I'm on the way out of their contract and switching to <a href="https://www.solnet.ch/" title="SolNet">SolNet</a>).<br>Besides not supporting to bring your own router, they also like to make up additional early-termination fees (the contract states 100CHF early termination fees, but once you call them to initiate the process they tell you that it's gonna cost 300CHF as they decided to change their pricing structure unilaterally).</p>
  5649.  
  5650. <p>Enough of the ranting, now to the interesting part :-)</p>
  5651.  
  5652. <p>The Sunrise line has multiple VLANs to differentiate between Internet, Phone and TV services.<br>To receive an IPv4 address it requires a special value for the Client Identifier DHCP option.<br>For IPv6 <a href="https://en.wikipedia.org/wiki/IPv6_rapid_deployment" title="IPv6 rapid deployment">6rd</a> is employed, for which we need to know the prefix and gateway address.</p>
  5653.  
  5654. <p>The following configuration was tested with a <a href="https://mikrotik.com/" title="MikroTik Routers and Wireless">MikroTik</a> CRS125 router starting from the default settings.<br>For simplicity I've named the network interfaces according to their intended usage (eg. <code>LAN</code>, <code>sunrise</code> and <code>6rd</code>).</p>
  5655.  
  5656. <p>The first step is to configure the VLAN on top of your fiber interface. In my case it was VLAN ID 131, others were also successful with VLAN ID 10.</p>
  5657.  
  5658. <pre>/interface vlan add interface=sfp1-gateway name=sunrise vlan-id=131</pre>
  5659.  
  5660. <p>Next let's put in place some basic firewall rules to make sure we're not exposing our LAN to the Internet once the connection comes up.</p>
  5661. <pre>/ip firewall filter
  5662. add action=accept chain=forward connection-state=established,related
  5663. add action=accept chain=forward in-interface=LAN out-interface=sunrise
  5664. add action=drop chain=forward
  5665. add action=accept chain=input connection-state=established,related
  5666. add action=accept chain=input protocol=icmp
  5667. add action=drop chain=input in-interface=!LAN</pre>
  5668. <pre>/ip firewall nat
  5669. add action=masquerade chain=srcnat out-interface=sunrise</pre>
  5670.  
  5671. <p>Now we can configure the special value for the Client Identifier DHCP option and configure the DHCP client on the VLAN interface.</p>
  5672. <pre>/ip dhcp-client option add code=61 name=clientid-sunrise value="'dslforum.org,Fast5360-sunrise'"</pre>
  5673. <pre>/ip dhcp-client add dhcp-options=clientid-sunrise disabled=no interface=sunrise</pre>
  5674.  
  5675. <p>This should now give us IPv4 Internet connectivity. We can test this by checking that we received an IPv4 address, have an IPv4 default route and that we can ping a host in the Internet.</p>
  5676.  
  5677. <pre>/ip dhcp-client print
  5678. Flags: X - disabled, I - invalid, D - dynamic
  5679. #   INTERFACE       USE-PEER-DNS ADD-DEFAULT-ROUTE STATUS        ADDRESS
  5680. 0   sunrise         yes          yes               bound         198.51.100.123/25</pre>
  5681. <pre>/ip route check 1.1
  5682.     status: ok
  5683.  interface: sunrise
  5684.    nexthop: 198.51.100.1</pre>
  5685. <pre>/ping count=1 1.1
  5686.  SEQ HOST                                     SIZE TTL TIME  STATUS
  5687.    0 1.0.0.1                                    56  59 1ms
  5688.    sent=1 received=1 packet-loss=0% min-rtt=1ms avg-rtt=1ms max-rtt=1ms</pre>
  5689.  
  5690. <p>Sunrise doesn't offer native IPv6 connectivity but employs 6rd (which defines how to create a 6to4 tunnel based on the public IPv4 address, an IPv6 prefix and the tunnel gateway).</p>
  5691. <p>Before we setup the 6rd tunnel, it's important to put in place firewall rules for IPv6 as afterwards all devices on the local network will receive a public IPv6 address.</p>
  5692. <pre>/ipv6 firewall filter
  5693. add action=accept chain=forward connection-state=established,related
  5694. add action=accept chain=forward in-interface=LAN
  5695. add action=drop chain=forward
  5696. add action=accept chain=input connection-state=established,related
  5697. add action=accept chain=input protocol=icmpv6
  5698. add action=drop chain=input</pre>
  5699.  
  5700. <p>To setup the 6rd tunnel, I've modified an existing script with the specific parameters for Sunrise (namely the <kbd>2001:1710::/28</kbd> prefix and the <kbd>212.161.209.1</kbd> tunnel gateway address).<br>The script creates the tunnel interface, configures an IPv6 address on the external interface, configures an IPv6 address on the internal interface (which also enables SLAAC to provide IPv6 addresses to the clients on the local network) and configures an IPv6 default route over the 6rd tunnel.</p>
  5701. <p>The script itself will be run via the scheduler, thus let's save it under the name <kbd>6rd-script</kbd>.</p>
  5702. <pre>
  5703. :global ipv6localinterface "LAN"
  5704. :global uplinkinterface "sunrise"
  5705.  
  5706. :global IPv4addr [/ip address get [find interface=$uplinkinterface] address];
  5707. :global IPv4addr [:pick $IPv4addr 0 [:find $IPv4addr "/"]]
  5708. :global IPv4addr2 [:pick $IPv4addr 0 30]
  5709. :global IPv6temp [:toip6 ("1::" . $IPv4addr2)]
  5710.  
  5711. :global IPv4hex1 [:pick $IPv6temp 3 4]
  5712. :global IPv4hex2 [:pick $IPv6temp 4 7]
  5713. :global IPv4hex3 [:pick $IPv6temp 8 9]
  5714. :global IPv4hex4 [:pick $IPv6temp 9 12]
  5715. :global IPv6addr [("2001:171" . $IPv4hex1 . ":". $IPv4hex2 .$IPv4hex3 . ":" . $IPv4hex4 . "0::1/64")]
  5716. :global IPv6addrLoc [("2001:171" . $IPv4hex1 . ":". $IPv4hex2 . $IPv4hex3 . ":" . $IPv4hex4 . "1::1/64")]
  5717.  
  5718. #6to4 interface
  5719. :global 6to4id [/interface 6to4 find where name="6rd"]
  5720. :if ($6to4id!="") do={
  5721. :global 6to4addr [/interface 6to4 get $6to4id local-address]
  5722. if ($6to4addr != $IPv4addr) do={ :log warning "Updating local-address for 6to4 tunnel '6rd' from '$6to4addr' to '$IPv4addr'."; /interface 6to4 set [find name="6rd"] local-address=$IPv4addr }
  5723. } else { :log warning "Creating 6to4 interface '6rd'. "; /interface 6to4 add !keepalive local-address=$IPv4addr mtu=1480 name="6rd" remote-address=212.161.209.1 }
  5724.  
  5725. #ipv6 for uplink
  5726. :global IPv6addrnumber [/ipv6 address find where comment="6rd" and interface="6rd"]
  5727. :if ($IPv6addrnumber!="") do={
  5728. :global oldip ([/ipv6 address get $IPv6addrnumber address])
  5729. if ($oldip != $IPv6addr) do={ :log warning "Updating 6rd IPv6 from '$oldip' to '$IPv6addr'."; /ipv6 address set number=$IPv6addrnumber address=$IPv6addr disabled=no }
  5730. } else {:log warning "Setting up 6rd IPv6 '$IPv6addr' to '6rd'. "; /ipv6 address add address=$IPv6addr interface="6rd" comment="6rd" advertise=no }
  5731.  
  5732. #ipv6 for local
  5733. :global IPv6addrnumberLocal [/ipv6 address find where comment=("6rd_local") and interface=$ipv6localinterface]
  5734. :if ($IPv6addrnumberLocal!="") do={
  5735. :global oldip ([/ipv6 address get $IPv6addrnumberLocal address])
  5736. if ($oldip != $IPv6addrLoc) do={ :log warning "Updating 6rd LOCAL IPv6 from '$oldip' to '$IPv6addrLoc'."; /ipv6 address set number=$IPv6addrnumberLocal address=$IPv6addrLoc disabled=no }
  5737. } else {:log warning "Setting up 6rd LOCAL IPv6 '$IPv6addrLoc' na '$ipv6localinterface'. "; /ipv6 address add address=$IPv6addrLoc interface=$ipv6localinterface comment="6rd_local" advertise=yes }
  5738.  
  5739. #ipv6 route
  5740. :global routa [/ipv6 route find where dst-address="2000::/3" and gateway="6rd"]
  5741. if ($routa="") do={ :log warning "Setting IPv6 route '2000::/3' pres '6rd'. "; /ipv6 route add distance=1 dst-address="2000::/3" gateway="6rd" }
  5742. </pre>
  5743.  
  5744. <p>Once we've added the script we also need to create the scheduler entry to run it periodically (as it needs to re-configure the tunnel and addresses whenever the public IPv4 address changes).</p>
  5745. <pre>/system scheduler add interval=1m name=schedule1 on-event=6rd-script</pre>
  5746.  
  5747. <p>After the first run of the script we should now have IPv6 connectivity. Let's test this again by checking that we have a public IPv6 address, an IPv6 default route and can ping an IPv6 host in the Internet.</p>
  5748.  
  5749. <pre>/ipv6 address print where interface=6rd and global
  5750. Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local
  5751. #    ADDRESS                                     FROM-POOL INTERFACE        ADVERTISE
  5752. 0  G ;;; 6rd
  5753.      2001:171c:6336:47b0::1/64                             6rd              no</pre>
  5754. <pre>/ipv6 route check 2600::
  5755.     status: ok
  5756.  interface: 6rd
  5757.    nexthop: 2600::</pre>
  5758. <pre>/ping count=1 2600::
  5759.  SEQ HOST                                     SIZE TTL TIME  STATUS
  5760.    0 2600::                                     56  50 118ms echo reply
  5761.    sent=1 received=1 packet-loss=0% min-rtt=118ms avg-rtt=118ms max-rtt=118ms</pre>
  5762.  
  5763. <p>And that's how you can configure and validate IPv4 and IPv6 connectivity with your own router on a Sunrise fiber line despite them not liking it very much ;-)</p>
  5764. ]]></description>
  5765.    <content:encoded><![CDATA[<p>Sunrise does not like when people run their own router on a fiber line. While they do not directly forbid it, they don't provide any of the required configuration parameters which makes it quite hard to use your own router.</p>
  5766. <p>Below you'll find the required configuration parameters to make your own router connect with IPv4 and IPv6 on a Sunrise fiber line.<br>Beware though that especially the VLAN configuration might be different depending on your city, the following worked for me in Zürich.</p>
  5767. <p>Also, please note that I do not recommend Sunrise as Internet provider (as a matter of fact I'm on the way out of their contract and switching to <a href="https://www.solnet.ch/" title="SolNet">SolNet</a>).<br>Besides not supporting to bring your own router, they also like to make up additional early-termination fees (the contract states 100CHF early termination fees, but once you call them to initiate the process they tell you that it's gonna cost 300CHF as they decided to change their pricing structure unilaterally).</p>
  5768.  
  5769. <p>Enough of the ranting, now to the interesting part :-)</p>
  5770.  
  5771. <p>The Sunrise line has multiple VLANs to differentiate between Internet, Phone and TV services.<br>To receive an IPv4 address it requires a special value for the Client Identifier DHCP option.<br>For IPv6 <a href="https://en.wikipedia.org/wiki/IPv6_rapid_deployment" title="IPv6 rapid deployment">6rd</a> is employed, for which we need to know the prefix and gateway address.</p>
  5772.  
  5773. <p>The following configuration was tested with a <a href="https://mikrotik.com/" title="MikroTik Routers and Wireless">MikroTik</a> CRS125 router starting from the default settings.<br>For simplicity I've named the network interfaces according to their intended usage (eg. <code>LAN</code>, <code>sunrise</code> and <code>6rd</code>).</p>
  5774.  
  5775. <p>The first step is to configure the VLAN on top of your fiber interface. In my case it was VLAN ID 131, others were also successful with VLAN ID 10.</p>
  5776.  
  5777. <pre>/interface vlan add interface=sfp1-gateway name=sunrise vlan-id=131</pre>
  5778.  
  5779. <p>Next let's put in place some basic firewall rules to make sure we're not exposing our LAN to the Internet once the connection comes up.</p>
  5780. <pre>/ip firewall filter
  5781. add action=accept chain=forward connection-state=established,related
  5782. add action=accept chain=forward in-interface=LAN out-interface=sunrise
  5783. add action=drop chain=forward
  5784. add action=accept chain=input connection-state=established,related
  5785. add action=accept chain=input protocol=icmp
  5786. add action=drop chain=input in-interface=!LAN</pre>
  5787. <pre>/ip firewall nat
  5788. add action=masquerade chain=srcnat out-interface=sunrise</pre>
  5789.  
  5790. <p>Now we can configure the special value for the Client Identifier DHCP option and configure the DHCP client on the VLAN interface.</p>
  5791. <pre>/ip dhcp-client option add code=61 name=clientid-sunrise value="'dslforum.org,Fast5360-sunrise'"</pre>
  5792. <pre>/ip dhcp-client add dhcp-options=clientid-sunrise disabled=no interface=sunrise</pre>
  5793.  
  5794. <p>This should now give us IPv4 Internet connectivity. We can test this by checking that we received an IPv4 address, have an IPv4 default route and that we can ping a host in the Internet.</p>
  5795.  
  5796. <pre>/ip dhcp-client print
  5797. Flags: X - disabled, I - invalid, D - dynamic
  5798. #   INTERFACE       USE-PEER-DNS ADD-DEFAULT-ROUTE STATUS        ADDRESS
  5799. 0   sunrise         yes          yes               bound         198.51.100.123/25</pre>
  5800. <pre>/ip route check 1.1
  5801.     status: ok
  5802.  interface: sunrise
  5803.    nexthop: 198.51.100.1</pre>
  5804. <pre>/ping count=1 1.1
  5805.  SEQ HOST                                     SIZE TTL TIME  STATUS
  5806.    0 1.0.0.1                                    56  59 1ms
  5807.    sent=1 received=1 packet-loss=0% min-rtt=1ms avg-rtt=1ms max-rtt=1ms</pre>
  5808.  
  5809. <p>Sunrise doesn't offer native IPv6 connectivity but employs 6rd (which defines how to create a 6to4 tunnel based on the public IPv4 address, an IPv6 prefix and the tunnel gateway).</p>
  5810. <p>Before we setup the 6rd tunnel, it's important to put in place firewall rules for IPv6 as afterwards all devices on the local network will receive a public IPv6 address.</p>
  5811. <pre>/ipv6 firewall filter
  5812. add action=accept chain=forward connection-state=established,related
  5813. add action=accept chain=forward in-interface=LAN
  5814. add action=drop chain=forward
  5815. add action=accept chain=input connection-state=established,related
  5816. add action=accept chain=input protocol=icmpv6
  5817. add action=drop chain=input</pre>
  5818.  
  5819. <p>To setup the 6rd tunnel, I've modified an existing script with the specific parameters for Sunrise (namely the <kbd>2001:1710::/28</kbd> prefix and the <kbd>212.161.209.1</kbd> tunnel gateway address).<br>The script creates the tunnel interface, configures an IPv6 address on the external interface, configures an IPv6 address on the internal interface (which also enables SLAAC to provide IPv6 addresses to the clients on the local network) and configures an IPv6 default route over the 6rd tunnel.</p>
  5820. <p>The script itself will be run via the scheduler, thus let's save it under the name <kbd>6rd-script</kbd>.</p>
  5821. <pre>
  5822. :global ipv6localinterface "LAN"
  5823. :global uplinkinterface "sunrise"
  5824.  
  5825. :global IPv4addr [/ip address get [find interface=$uplinkinterface] address];
  5826. :global IPv4addr [:pick $IPv4addr 0 [:find $IPv4addr "/"]]
  5827. :global IPv4addr2 [:pick $IPv4addr 0 30]
  5828. :global IPv6temp [:toip6 ("1::" . $IPv4addr2)]
  5829.  
  5830. :global IPv4hex1 [:pick $IPv6temp 3 4]
  5831. :global IPv4hex2 [:pick $IPv6temp 4 7]
  5832. :global IPv4hex3 [:pick $IPv6temp 8 9]
  5833. :global IPv4hex4 [:pick $IPv6temp 9 12]
  5834. :global IPv6addr [("2001:171" . $IPv4hex1 . ":". $IPv4hex2 .$IPv4hex3 . ":" . $IPv4hex4 . "0::1/64")]
  5835. :global IPv6addrLoc [("2001:171" . $IPv4hex1 . ":". $IPv4hex2 . $IPv4hex3 . ":" . $IPv4hex4 . "1::1/64")]
  5836.  
  5837. #6to4 interface
  5838. :global 6to4id [/interface 6to4 find where name="6rd"]
  5839. :if ($6to4id!="") do={
  5840. :global 6to4addr [/interface 6to4 get $6to4id local-address]
  5841. if ($6to4addr != $IPv4addr) do={ :log warning "Updating local-address for 6to4 tunnel '6rd' from '$6to4addr' to '$IPv4addr'."; /interface 6to4 set [find name="6rd"] local-address=$IPv4addr }
  5842. } else { :log warning "Creating 6to4 interface '6rd'. "; /interface 6to4 add !keepalive local-address=$IPv4addr mtu=1480 name="6rd" remote-address=212.161.209.1 }
  5843.  
  5844. #ipv6 for uplink
  5845. :global IPv6addrnumber [/ipv6 address find where comment="6rd" and interface="6rd"]
  5846. :if ($IPv6addrnumber!="") do={
  5847. :global oldip ([/ipv6 address get $IPv6addrnumber address])
  5848. if ($oldip != $IPv6addr) do={ :log warning "Updating 6rd IPv6 from '$oldip' to '$IPv6addr'."; /ipv6 address set number=$IPv6addrnumber address=$IPv6addr disabled=no }
  5849. } else {:log warning "Setting up 6rd IPv6 '$IPv6addr' to '6rd'. "; /ipv6 address add address=$IPv6addr interface="6rd" comment="6rd" advertise=no }
  5850.  
  5851. #ipv6 for local
  5852. :global IPv6addrnumberLocal [/ipv6 address find where comment=("6rd_local") and interface=$ipv6localinterface]
  5853. :if ($IPv6addrnumberLocal!="") do={
  5854. :global oldip ([/ipv6 address get $IPv6addrnumberLocal address])
  5855. if ($oldip != $IPv6addrLoc) do={ :log warning "Updating 6rd LOCAL IPv6 from '$oldip' to '$IPv6addrLoc'."; /ipv6 address set number=$IPv6addrnumberLocal address=$IPv6addrLoc disabled=no }
  5856. } else {:log warning "Setting up 6rd LOCAL IPv6 '$IPv6addrLoc' na '$ipv6localinterface'. "; /ipv6 address add address=$IPv6addrLoc interface=$ipv6localinterface comment="6rd_local" advertise=yes }
  5857.  
  5858. #ipv6 route
  5859. :global routa [/ipv6 route find where dst-address="2000::/3" and gateway="6rd"]
  5860. if ($routa="") do={ :log warning "Setting IPv6 route '2000::/3' pres '6rd'. "; /ipv6 route add distance=1 dst-address="2000::/3" gateway="6rd" }
  5861. </pre>
  5862.  
  5863. <p>Once we've added the script we also need to create the scheduler entry to run it periodically (as it needs to re-configure the tunnel and addresses whenever the public IPv4 address changes).</p>
  5864. <pre>/system scheduler add interval=1m name=schedule1 on-event=6rd-script</pre>
  5865.  
  5866. <p>After the first run of the script we should now have IPv6 connectivity. Let's test this again by checking that we have a public IPv6 address, an IPv6 default route and can ping an IPv6 host in the Internet.</p>
  5867.  
  5868. <pre>/ipv6 address print where interface=6rd and global
  5869. Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local
  5870. #    ADDRESS                                     FROM-POOL INTERFACE        ADVERTISE
  5871. 0  G ;;; 6rd
  5872.      2001:171c:6336:47b0::1/64                             6rd              no</pre>
  5873. <pre>/ipv6 route check 2600::
  5874.     status: ok
  5875.  interface: 6rd
  5876.    nexthop: 2600::</pre>
  5877. <pre>/ping count=1 2600::
  5878.  SEQ HOST                                     SIZE TTL TIME  STATUS
  5879.    0 2600::                                     56  50 118ms echo reply
  5880.    sent=1 received=1 packet-loss=0% min-rtt=118ms avg-rtt=118ms max-rtt=118ms</pre>
  5881.  
  5882. <p>And that's how you can configure and validate IPv4 and IPv6 connectivity with your own router on a Sunrise fiber line despite them not liking it very much ;-)</p>
  5883. ]]></content:encoded>
  5884.  </item>
  5885.  
  5886.  <item>
  5887.    <title>MTA-STS</title>
  5888.    <link>https://blog.x-way.org/Networking/2020/11/21/MTA-STS.html</link>
  5889.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324282</guid>
  5890.    <dc:creator>Andreas Jaggi</dc:creator>
  5891.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5892.    <pubDate>Sat, 21 Nov 2020 09:47:00 +0100</pubDate>
  5893.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  5894.    <description><![CDATA[<p>Recently I added <a href="https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol#SMTP_MTA_Strict_Transport_Security" title="SMTP MTA Strict-Transport-Security">MTA-STS</a> support to one of my domains, and it turns out that this was easier than expected.</p>
  5895. <p>MTA-STS is used to tell mail senders that your server supports TLS. And then you can define the policy for your server and tell them that they should only use TLS (resp. STARTTLS) when connecting to you and not fall back to unencrypted SMTP.</p>
  5896. <p>The way this works is with two components:</p>
  5897. <ul>
  5898. <li>a special <code>_mta-sts.&lt;your-site.com&gt;</code> TXT DNS entry indicating that your domain supports MTA-STS and the version number of your MTA-STS policy</li>
  5899. <li>a mta-sts.txt file served under a specific well-known URL <code>https://mta-sts.&lt;your-site.com&gt;/.well-known/mta-sts.txt</code> containing your MTA-STS policy (which mx hosts it is valid for, should it be run in enforcing or testing mode, max-age etc.)</li>
  5900. </ul>
  5901. <p>The idea is that a mail sender checks your MTA-STS policy through protected channels (DNSSEC, HTTPS) and then never sends mails to you in plaintext (similar approach as <a href="https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security" title="HTTP Strict Transport Security">HSTS</a> for HTTP but this time between mail servers).</p>
  5902.  
  5903. <p>To setup the MTA-STS configuration, I followed this <a href="https://www.naut.ca/blog/2020/04/07/mta-sts-in-5-minutes/" title="Enable MTA-STS in 5 Minutes with NGINX">Enable MTA-STS in 5 Minutes with NGINX</a> guide from <a href="https://www.naut.ca/" title="Home - Yoonsik Park">Yoonsik Park</a>.</p>
  5904. <p>Then to check my configuration I used this <a href="https://aykevl.nl/apps/mta-sts/" title="MTA-STS validator">MTA-STS validator</a> (which is an opensource project available on <a href="https://github.com/aykevl/mta-sts" title="GitHub - aykevl/mta-sts: Online tool for MTA-STS checking: https://aykevl.nl/apps/mta-sts/">GitHub</a>), the classic <a href="https://www.checktls.com/TestReceiver" title="//email/testTo:">checktls.com //email/testTo: tool</a> (MTA-STS checking needs to be explicitly enabled under 'More Options') and the free testing service provided by <a href="https://www.hardenize.com/" title="Harenize: Comprehensive web site configuration test">Hardenize</a>.</p>
  5905. ]]></description>
  5906.    <content:encoded><![CDATA[<p>Recently I added <a href="https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol#SMTP_MTA_Strict_Transport_Security" title="SMTP MTA Strict-Transport-Security">MTA-STS</a> support to one of my domains, and it turns out that this was easier than expected.</p>
  5907. <p>MTA-STS is used to tell mail senders that your server supports TLS. And then you can define the policy for your server and tell them that they should only use TLS (resp. STARTTLS) when connecting to you and not fall back to unencrypted SMTP.</p>
  5908. <p>The way this works is with two components:</p>
  5909. <ul>
  5910. <li>a special <code>_mta-sts.&lt;your-site.com&gt;</code> TXT DNS entry indicating that your domain supports MTA-STS and the version number of your MTA-STS policy</li>
  5911. <li>a mta-sts.txt file served under a specific well-known URL <code>https://mta-sts.&lt;your-site.com&gt;/.well-known/mta-sts.txt</code> containing your MTA-STS policy (which mx hosts it is valid for, should it be run in enforcing or testing mode, max-age etc.)</li>
  5912. </ul>
  5913. <p>The idea is that a mail sender checks your MTA-STS policy through protected channels (DNSSEC, HTTPS) and then never sends mails to you in plaintext (similar approach as <a href="https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security" title="HTTP Strict Transport Security">HSTS</a> for HTTP but this time between mail servers).</p>
  5914.  
  5915. <p>To setup the MTA-STS configuration, I followed this <a href="https://www.naut.ca/blog/2020/04/07/mta-sts-in-5-minutes/" title="Enable MTA-STS in 5 Minutes with NGINX">Enable MTA-STS in 5 Minutes with NGINX</a> guide from <a href="https://www.naut.ca/" title="Home - Yoonsik Park">Yoonsik Park</a>.</p>
  5916. <p>Then to check my configuration I used this <a href="https://aykevl.nl/apps/mta-sts/" title="MTA-STS validator">MTA-STS validator</a> (which is an opensource project available on <a href="https://github.com/aykevl/mta-sts" title="GitHub - aykevl/mta-sts: Online tool for MTA-STS checking: https://aykevl.nl/apps/mta-sts/">GitHub</a>), the classic <a href="https://www.checktls.com/TestReceiver" title="//email/testTo:">checktls.com //email/testTo: tool</a> (MTA-STS checking needs to be explicitly enabled under 'More Options') and the free testing service provided by <a href="https://www.hardenize.com/" title="Harenize: Comprehensive web site configuration test">Hardenize</a>.</p>
  5917. ]]></content:encoded>
  5918.  </item>
  5919.  
  5920.  <item>
  5921.    <title>15 years of o5</title>
  5922.    <link>https://blog.x-way.org/Webdesign/2020/11/01/15-years-of-o5.html</link>
  5923.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324281</guid>
  5924.    <dc:creator>Andreas Jaggi</dc:creator>
  5925.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5926.    <pubDate>Sun, 01 Nov 2020 19:03:00 +0100</pubDate>
  5927.    <category domain="https://blog.x-way.org/Webdesign/">Webdesign</category>
  5928.    <description><![CDATA[<p><a href="https://blog.x-way.org/Webdesign/2005/11/01/CSS-Reboot-Fall-2005.html" title="x-log - CSS Reboot Fall 2005">15 years ago</a> this weblog received the current o5 design (or theme as it would be called nowadays).<br>
  5929. During this time the design has aged quite well and also survived <a href="https://blog.x-way.org/Misc/2011/11/26/Online-Again.html" title="x-log - Online Again">the move</a> of the backend from a self-written PHP blog-engine to Jekyll.</p>
  5930. <p>Although it still works surprisingly well and presents the content nicely every day, there are some parts where better usage of contemporary technologies would be desirable.<br>It has no mobile version nor a responsive layout as the design was created before the now omnipresent smartphones were invented. Similar is the font-size hardcoded and not very adequate for todays retina displays. And yes, it uses the XHTML 1.0 strict standard with all its quirks and CSS tricks from 2002 (which luckily are still supported in current browsers).</p>
  5931. <p>Overall I'm quite happy that the o5 design has turned out to be so timeless and that I did not have to come up with a new one every other year (btw: I don't remember where the o5 name came from, likely the 5 is a reference to 2005 when it was created).</p>
  5932. <p>With the current Corona situation forcing me to spend more time at home again, I have the feeling that some things might change around the weblog (not quite sure what or when exactly, first I need to re-learn how websites are built in 2020 :-).</p>
  5933. ]]></description>
  5934.    <content:encoded><![CDATA[<p><a href="https://blog.x-way.org/Webdesign/2005/11/01/CSS-Reboot-Fall-2005.html" title="x-log - CSS Reboot Fall 2005">15 years ago</a> this weblog received the current o5 design (or theme as it would be called nowadays).<br>
  5935. During this time the design has aged quite well and also survived <a href="https://blog.x-way.org/Misc/2011/11/26/Online-Again.html" title="x-log - Online Again">the move</a> of the backend from a self-written PHP blog-engine to Jekyll.</p>
  5936. <p>Although it still works surprisingly well and presents the content nicely every day, there are some parts where better usage of contemporary technologies would be desirable.<br>It has no mobile version nor a responsive layout as the design was created before the now omnipresent smartphones were invented. Similar is the font-size hardcoded and not very adequate for todays retina displays. And yes, it uses the XHTML 1.0 strict standard with all its quirks and CSS tricks from 2002 (which luckily are still supported in current browsers).</p>
  5937. <p>Overall I'm quite happy that the o5 design has turned out to be so timeless and that I did not have to come up with a new one every other year (btw: I don't remember where the o5 name came from, likely the 5 is a reference to 2005 when it was created).</p>
  5938. <p>With the current Corona situation forcing me to spend more time at home again, I have the feeling that some things might change around the weblog (not quite sure what or when exactly, first I need to re-learn how websites are built in 2020 :-).</p>
  5939. ]]></content:encoded>
  5940.  </item>
  5941.  
  5942.  <item>
  5943.    <title>NAT Slipstreaming (NAT traversal part 2)</title>
  5944.    <link>https://blog.x-way.org/Networking/2020/10/31/NAT-Slipstreaming.html</link>
  5945.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324280</guid>
  5946.    <dc:creator>Andreas Jaggi</dc:creator>
  5947.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5948.    <pubDate>Sat, 31 Oct 2020 22:55:00 +0100</pubDate>
  5949.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  5950.    <description><![CDATA[<p>Compared to the <a href="https://blog.x-way.org/Networking/2020/08/23/How-NAT-traversal-works.html" title="x-log - How NAT traversal works">previous post</a> where intentional NAT traversal was discussed, here now comes an article about 'unintentional' (malicious) NAT traversal.</p>
  5951. <p><a href="https://samy.pl/" title="Samy Kamar">Samy Kamar</a> describes in his <a href="https://samy.pl/slipstream/" title="Samy Kamar - NAT Slipstreaming">NAT Slipstreaming article</a> how a combination of TCP packet segmentation and smuggling SIP requests in HTTP, can be used to trick the NAT <abbr title="Application Layer Gateway">ALG</abbr> of your router into opening arbitrary ports for inbound connections from the Internet to your computer.</p>
  5952. <p>The article analyses in detail the SIP ALG of the Linux netfilter stack in it's default configuration, but likely similar attacks could also be possible with ALGs of other protocols and vendors.</p>
  5953. <p>Important to note: the Linux SIP ALG module has two parameters (sip_direct_media and sip_direct_signalling), which restrict the IP address for which additional ports are opened to the one sending the original SIP packet. By default they are set to 1, but if any of these is set to 0 in a router's configuration, the described NAT Slipstreaming attack will not only allow to make inbound connections to your computer, but also to any other device in the local network!</p>
  5954. ]]></description>
  5955.    <content:encoded><![CDATA[<p>Compared to the <a href="https://blog.x-way.org/Networking/2020/08/23/How-NAT-traversal-works.html" title="x-log - How NAT traversal works">previous post</a> where intentional NAT traversal was discussed, here now comes an article about 'unintentional' (malicious) NAT traversal.</p>
  5956. <p><a href="https://samy.pl/" title="Samy Kamar">Samy Kamar</a> describes in his <a href="https://samy.pl/slipstream/" title="Samy Kamar - NAT Slipstreaming">NAT Slipstreaming article</a> how a combination of TCP packet segmentation and smuggling SIP requests in HTTP, can be used to trick the NAT <abbr title="Application Layer Gateway">ALG</abbr> of your router into opening arbitrary ports for inbound connections from the Internet to your computer.</p>
  5957. <p>The article analyses in detail the SIP ALG of the Linux netfilter stack in it's default configuration, but likely similar attacks could also be possible with ALGs of other protocols and vendors.</p>
  5958. <p>Important to note: the Linux SIP ALG module has two parameters (sip_direct_media and sip_direct_signalling), which restrict the IP address for which additional ports are opened to the one sending the original SIP packet. By default they are set to 1, but if any of these is set to 0 in a router's configuration, the described NAT Slipstreaming attack will not only allow to make inbound connections to your computer, but also to any other device in the local network!</p>
  5959. ]]></content:encoded>
  5960.  </item>
  5961.  
  5962.  <item>
  5963.    <title>How NAT traversal works</title>
  5964.    <link>https://blog.x-way.org/Networking/2020/08/23/How-NAT-traversal-works.html</link>
  5965.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324279</guid>
  5966.    <dc:creator>Andreas Jaggi</dc:creator>
  5967.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5968.    <pubDate>Sun, 23 Aug 2020 21:08:00 +0200</pubDate>
  5969.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  5970.    <description><![CDATA[<p><a href="https://tailscale.com/blog/how-nat-traversal-works/" title="How NAT traversal works - Tailscale Blog">How NAT traversal works</a> &ndash; is a very well written and detailed article from <a href="https://www.dave.tf/" title="Dave.tf">Dave Anderson</a> explaining the different NAT scenarios and the tricks that can be used to establish a peer-to-peer UDP connection between machines sitting behind them.</p>
  5971. ]]></description>
  5972.    <content:encoded><![CDATA[<p><a href="https://tailscale.com/blog/how-nat-traversal-works/" title="How NAT traversal works - Tailscale Blog">How NAT traversal works</a> &ndash; is a very well written and detailed article from <a href="https://www.dave.tf/" title="Dave.tf">Dave Anderson</a> explaining the different NAT scenarios and the tricks that can be used to establish a peer-to-peer UDP connection between machines sitting behind them.</p>
  5973. ]]></content:encoded>
  5974.  </item>
  5975.  
  5976.  <item>
  5977.    <title>Replace the root disk</title>
  5978.    <link>https://blog.x-way.org/Linux/2020/06/07/Replace-the-root-disk.html</link>
  5979.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324278</guid>
  5980.    <dc:creator>Andreas Jaggi</dc:creator>
  5981.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  5982.    <pubDate>Sun, 07 Jun 2020 10:58:00 +0200</pubDate>
  5983.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  5984.    <description><![CDATA[<p>Recently the disk holding the root (<kbd>/</kbd>) filesystem on one of my linux systems started to report increased <a href="https://en.wikipedia.org/wiki/S.M.A.R.T." title="S.M.A.R.T - Wikipedia">SMART</a> raw read error rates, seek error rates and ECC recovered hardware errors.</p>
  5985. <p>As these are early indications of a failing disk, it became time to replace the disk.</p>
  5986. <p>Normally replacing a disk comes down to plugging in the new one, coyping over the data, umount the old disk, mount the new one in place, unplug the old disk.<br>But when it is the disk with the root filesystem a couple extra steps are needed.</p>
  5987. <p>The steps below worked for my Debian system without problems (even used the opportunity to upgrade to an SSD :-)</p>
  5988. <p>(source is <a href="https://unix.stackexchange.com/questions/338387/how-do-i-replace-root-drive-on-debian" title="How do I replace Root Drive on Debian?">this thread</a> on StackExchange)</p>
  5989.  
  5990. <blockquote>
  5991. <p>The following makes some assumptions:</p>
  5992. <ul>
  5993. <li>All commands ran as root when possible</li>
  5994. <li>You are on a physical console to the host (need to type in grub commands to boot up the new disk!)</li>
  5995. <li>You want an ext4 files system</li>
  5996. <li>You are loosely familiar on a basic level with all commands run</li>
  5997. <li>You are NOT booting from a RAID device</li>
  5998. </ul>
  5999. <p>So here we go.</p>
  6000. <ol>
  6001. <li>Physically install new disk into computer and connect to available port leaving old disk in existing position.</li>
  6002. <li>Boot computer into old OS.</li>
  6003. <li>Prepare and mount new disk; first identify new disk<br>
  6004. <kbd>fdisk -l</kbd>
  6005. </li>
  6006. <li>Partition new disk<br>
  6007. <kbd>fdisk /dev/(newdisk)</kbd><br>
  6008. Make partition primary partition with type "83" file system type.
  6009. </li>
  6010. <li>Create filesystem<br>
  6011. <kbd>mkfs.ext4 /dev/(newpartition)</kbd>
  6012. </li>
  6013. <li>Mount new filesystem<br>
  6014. <kbd>mkdir /mnt/(newpartitionmountpoint)</kbd><br>
  6015. <kbd>mount /dev/(newpartition) /mnt/(newpartitionmountpoint)</kbd>
  6016. </li>
  6017. <li>Copy disk:<br>
  6018. <kbd>/sbin/init 1</kbd> (drop to single user mode)<br>
  6019. <kbd>rsync -avxHAX / /mnt/(newpartitionmountpoint)</kbd>
  6020. </li>
  6021. <li>Update FSTAB on newdisk<br>
  6022. <kbd>blkid</kbd> (note UUID of new partition)<br>
  6023. <kbd>vi /mnt/(newpartitionmountpoint)/etc/fstab</kbd><br>
  6024. Replace existing UUID of / in FSTAB to new disk UUID
  6025. </li>
  6026. <li>Configure grub and install to new disk boot loader:<br>
  6027. <kbd>grub-mkconfig</kbd><br>
  6028. <kbd>update-grub</kbd><br>
  6029. <kbd>grub-install /dev/(newdisk)</kbd>
  6030. </li>
  6031. <li>Copy grub.cfg from old disk to new<br>
  6032. <kbd>cp -ax /boot/grub/grub.cfg /mnt/(newpartitionmountpoint)/boot/grub/grub.cfg</kbd>
  6033. </li>
  6034. <li>Open grub.cfg on new disk and replace all UUIDs with new disk<br>
  6035. <kbd>vi /mnt/(newpartitionmountpoint)/boot/grub/grub.cfg</kbd><br>
  6036. Replace all old UUIDs with the UUID of the new disk
  6037. </li>
  6038. <li>Shut down computer<br>
  6039. <kbd>shutdown</kbd>
  6040. </li>
  6041. <li>Physically move the new drive to the 1st drive location and remove old drive</li>
  6042. <li>Start computer and grub should present:<br>
  6043. <pre>error: no such device: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  6044.  
  6045. GRUB rescue&gt;</pre>
  6046. </li>
  6047. <li>Manually boot new OS from grub; first identify the drive and partition of the boot files<br>
  6048. <kbd>ls</kbd> [to identify your drive and partition options]<br>
  6049. <kbd>ls (hdx,p)/</kbd> [to identify which partition has the /boot folder]
  6050. </li>
  6051. <li>Then, you can load the boot menu manually from the drive and partition you found above. Typically this would be (hd0,msdos1).<br>
  6052. <kbd>set prefix="(hdx,p)/boot/grub"</kbd><br>
  6053. <kbd>set root="(hdx,p)"</kbd><br>
  6054. <kbd>insmod normal</kbd><br>
  6055. <kbd>normal</kbd>
  6056. </li>
  6057. <li>Login to OS on new drive</li>
  6058. <li>Configure grub again<br>
  6059. <kbd>fdisk -l</kbd> (note dev of newdisk)<br>
  6060. <kbd>grub-mkconfig</kbd><br>
  6061. <kbd>update-grub</kbd><br>
  6062. <kbd>grub-install /dev/newdisk</kbd>
  6063. </li>
  6064. </ol>
  6065. <p>And that should be it!</p>
  6066. </blockquote>
  6067. ]]></description>
  6068.    <content:encoded><![CDATA[<p>Recently the disk holding the root (<kbd>/</kbd>) filesystem on one of my linux systems started to report increased <a href="https://en.wikipedia.org/wiki/S.M.A.R.T." title="S.M.A.R.T - Wikipedia">SMART</a> raw read error rates, seek error rates and ECC recovered hardware errors.</p>
  6069. <p>As these are early indications of a failing disk, it became time to replace the disk.</p>
  6070. <p>Normally replacing a disk comes down to plugging in the new one, coyping over the data, umount the old disk, mount the new one in place, unplug the old disk.<br>But when it is the disk with the root filesystem a couple extra steps are needed.</p>
  6071. <p>The steps below worked for my Debian system without problems (even used the opportunity to upgrade to an SSD :-)</p>
  6072. <p>(source is <a href="https://unix.stackexchange.com/questions/338387/how-do-i-replace-root-drive-on-debian" title="How do I replace Root Drive on Debian?">this thread</a> on StackExchange)</p>
  6073.  
  6074. <blockquote>
  6075. <p>The following makes some assumptions:</p>
  6076. <ul>
  6077. <li>All commands ran as root when possible</li>
  6078. <li>You are on a physical console to the host (need to type in grub commands to boot up the new disk!)</li>
  6079. <li>You want an ext4 files system</li>
  6080. <li>You are loosely familiar on a basic level with all commands run</li>
  6081. <li>You are NOT booting from a RAID device</li>
  6082. </ul>
  6083. <p>So here we go.</p>
  6084. <ol>
  6085. <li>Physically install new disk into computer and connect to available port leaving old disk in existing position.</li>
  6086. <li>Boot computer into old OS.</li>
  6087. <li>Prepare and mount new disk; first identify new disk<br>
  6088. <kbd>fdisk -l</kbd>
  6089. </li>
  6090. <li>Partition new disk<br>
  6091. <kbd>fdisk /dev/(newdisk)</kbd><br>
  6092. Make partition primary partition with type "83" file system type.
  6093. </li>
  6094. <li>Create filesystem<br>
  6095. <kbd>mkfs.ext4 /dev/(newpartition)</kbd>
  6096. </li>
  6097. <li>Mount new filesystem<br>
  6098. <kbd>mkdir /mnt/(newpartitionmountpoint)</kbd><br>
  6099. <kbd>mount /dev/(newpartition) /mnt/(newpartitionmountpoint)</kbd>
  6100. </li>
  6101. <li>Copy disk:<br>
  6102. <kbd>/sbin/init 1</kbd> (drop to single user mode)<br>
  6103. <kbd>rsync -avxHAX / /mnt/(newpartitionmountpoint)</kbd>
  6104. </li>
  6105. <li>Update FSTAB on newdisk<br>
  6106. <kbd>blkid</kbd> (note UUID of new partition)<br>
  6107. <kbd>vi /mnt/(newpartitionmountpoint)/etc/fstab</kbd><br>
  6108. Replace existing UUID of / in FSTAB to new disk UUID
  6109. </li>
  6110. <li>Configure grub and install to new disk boot loader:<br>
  6111. <kbd>grub-mkconfig</kbd><br>
  6112. <kbd>update-grub</kbd><br>
  6113. <kbd>grub-install /dev/(newdisk)</kbd>
  6114. </li>
  6115. <li>Copy grub.cfg from old disk to new<br>
  6116. <kbd>cp -ax /boot/grub/grub.cfg /mnt/(newpartitionmountpoint)/boot/grub/grub.cfg</kbd>
  6117. </li>
  6118. <li>Open grub.cfg on new disk and replace all UUIDs with new disk<br>
  6119. <kbd>vi /mnt/(newpartitionmountpoint)/boot/grub/grub.cfg</kbd><br>
  6120. Replace all old UUIDs with the UUID of the new disk
  6121. </li>
  6122. <li>Shut down computer<br>
  6123. <kbd>shutdown</kbd>
  6124. </li>
  6125. <li>Physically move the new drive to the 1st drive location and remove old drive</li>
  6126. <li>Start computer and grub should present:<br>
  6127. <pre>error: no such device: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  6128.  
  6129. GRUB rescue&gt;</pre>
  6130. </li>
  6131. <li>Manually boot new OS from grub; first identify the drive and partition of the boot files<br>
  6132. <kbd>ls</kbd> [to identify your drive and partition options]<br>
  6133. <kbd>ls (hdx,p)/</kbd> [to identify which partition has the /boot folder]
  6134. </li>
  6135. <li>Then, you can load the boot menu manually from the drive and partition you found above. Typically this would be (hd0,msdos1).<br>
  6136. <kbd>set prefix="(hdx,p)/boot/grub"</kbd><br>
  6137. <kbd>set root="(hdx,p)"</kbd><br>
  6138. <kbd>insmod normal</kbd><br>
  6139. <kbd>normal</kbd>
  6140. </li>
  6141. <li>Login to OS on new drive</li>
  6142. <li>Configure grub again<br>
  6143. <kbd>fdisk -l</kbd> (note dev of newdisk)<br>
  6144. <kbd>grub-mkconfig</kbd><br>
  6145. <kbd>update-grub</kbd><br>
  6146. <kbd>grub-install /dev/newdisk</kbd>
  6147. </li>
  6148. </ol>
  6149. <p>And that should be it!</p>
  6150. </blockquote>
  6151. ]]></content:encoded>
  6152.  </item>
  6153.  
  6154.  <item>
  6155.    <title>rkhunter CRLF confusion</title>
  6156.    <link>https://blog.x-way.org/Linux/2020/05/24/rkhunter-CRLF-confusion.html</link>
  6157.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324277</guid>
  6158.    <dc:creator>Andreas Jaggi</dc:creator>
  6159.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  6160.    <pubDate>Sun, 24 May 2020 11:22:00 +0200</pubDate>
  6161.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  6162.    <description><![CDATA[<p>On my Linux hosts I'm running <a href="http://rkhunter.sourceforge.net/" title="The Rootkit Hunter project">rkhunter</a>. On a newly configured host it lately reported the following warning:</p>
  6163. <pre>Warning: The SSH and rkhunter configuration options should be the same:
  6164.        SSH configuration option 'PermitRootLogin': no
  6165. Rkhunter configuration option 'ALLOW_SSH_ROOT_USER': no</pre>
  6166. <p>On first sight the warning does not seem to make much sense, as both configuration options seem to be set to the same value (<code>no</code>).<br>
  6167. But digging further reveals that they are stored slightly different:</p>
  6168. <pre># file /etc/rkhunter.conf
  6169. /etc/rkhunter.conf: ASCII text
  6170. # file /etc/ssh/sshd_config
  6171. /etc/ssh/sshd_config: ASCII text, with CRLF line terminators</pre>
  6172. <p>Turns out that rkhunter is also checking the line terminators as part of the configuration values, and warns because they are different.</p>
  6173. <p>Knowing this, the fix is simple: run <a href="http://dos2unix.sourceforge.net/" title="dos2unix">dos2unix</a> on the CRLF file</p>
  6174. ]]></description>
  6175.    <content:encoded><![CDATA[<p>On my Linux hosts I'm running <a href="http://rkhunter.sourceforge.net/" title="The Rootkit Hunter project">rkhunter</a>. On a newly configured host it lately reported the following warning:</p>
  6176. <pre>Warning: The SSH and rkhunter configuration options should be the same:
  6177.        SSH configuration option 'PermitRootLogin': no
  6178. Rkhunter configuration option 'ALLOW_SSH_ROOT_USER': no</pre>
  6179. <p>On first sight the warning does not seem to make much sense, as both configuration options seem to be set to the same value (<code>no</code>).<br>
  6180. But digging further reveals that they are stored slightly different:</p>
  6181. <pre># file /etc/rkhunter.conf
  6182. /etc/rkhunter.conf: ASCII text
  6183. # file /etc/ssh/sshd_config
  6184. /etc/ssh/sshd_config: ASCII text, with CRLF line terminators</pre>
  6185. <p>Turns out that rkhunter is also checking the line terminators as part of the configuration values, and warns because they are different.</p>
  6186. <p>Knowing this, the fix is simple: run <a href="http://dos2unix.sourceforge.net/" title="dos2unix">dos2unix</a> on the CRLF file</p>
  6187. ]]></content:encoded>
  6188.  </item>
  6189.  
  6190.  <item>
  6191.    <title>ipaddr CLI tool</title>
  6192.    <link>https://blog.x-way.org/Networking/2020/05/21/ipaddr-CLI-tool.html</link>
  6193.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324276</guid>
  6194.    <dc:creator>Andreas Jaggi</dc:creator>
  6195.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  6196.    <pubDate>Thu, 21 May 2020 19:38:00 +0200</pubDate>
  6197.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  6198.    <description><![CDATA[<p>While doing some maintenance on my server, I got tired of searching through the output of <code>ip addr show</code> to find the IP addresses configured on the interfaces.<br>
  6199. Thus I wrote a simple CLI tool to display the information I needed in a concise and human friendly form: <a href="https://github.com/x-way/ipaddr" title="ipaddr - human friendly list of IP addresses and network interfaces">ipaddr</a></p>
  6200. <pre>$ ipaddr
  6201. lo          127.0.0.1/8
  6202. ens5        198.51.100.160/24
  6203. tun24008    10.123.199.78/32
  6204. tun71991639 10.200.123.5/32
  6205. tun26724    10.100.100.235/32
  6206. tun3883710  10.123.111.7/32</pre>
  6207. <p>A nice side-effect of writing this in <a href="https://golang.org/" title="The Go Programming Language">Go</a> is that it works out-of-the-box also on non-Linux systems :-)</p>
  6208. ]]></description>
  6209.    <content:encoded><![CDATA[<p>While doing some maintenance on my server, I got tired of searching through the output of <code>ip addr show</code> to find the IP addresses configured on the interfaces.<br>
  6210. Thus I wrote a simple CLI tool to display the information I needed in a concise and human friendly form: <a href="https://github.com/x-way/ipaddr" title="ipaddr - human friendly list of IP addresses and network interfaces">ipaddr</a></p>
  6211. <pre>$ ipaddr
  6212. lo          127.0.0.1/8
  6213. ens5        198.51.100.160/24
  6214. tun24008    10.123.199.78/32
  6215. tun71991639 10.200.123.5/32
  6216. tun26724    10.100.100.235/32
  6217. tun3883710  10.123.111.7/32</pre>
  6218. <p>A nice side-effect of writing this in <a href="https://golang.org/" title="The Go Programming Language">Go</a> is that it works out-of-the-box also on non-Linux systems :-)</p>
  6219. ]]></content:encoded>
  6220.  </item>
  6221.  
  6222.  <item>
  6223.    <title>Poor man's reboot notification</title>
  6224.    <link>https://blog.x-way.org/Linux/2020/04/18/Poor-mans-reboot-notification.html</link>
  6225.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324275</guid>
  6226.    <dc:creator>Andreas Jaggi</dc:creator>
  6227.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  6228.    <pubDate>Sat, 18 Apr 2020 15:03:00 +0200</pubDate>
  6229.    <category domain="https://blog.x-way.org/Linux/">Linux</category>
  6230.    <description><![CDATA[<p>Sometimes you need to be notified about reboots of a machine without having the luxury of a proper monitoring system.</p>
  6231. <p>The following crontab entry triggers an e-mail when the host has been rebooted in the last 5 minutes.</p>
  6232. <pre>*/5 * * * * [ $(sed -e 's/\..*//' /proc/uptime) -lt 540 ] &amp;&amp; echo "Host has been rebooted! Uptime: $(uptime)"</pre>
  6233. ]]></description>
  6234.    <content:encoded><![CDATA[<p>Sometimes you need to be notified about reboots of a machine without having the luxury of a proper monitoring system.</p>
  6235. <p>The following crontab entry triggers an e-mail when the host has been rebooted in the last 5 minutes.</p>
  6236. <pre>*/5 * * * * [ $(sed -e 's/\..*//' /proc/uptime) -lt 540 ] &amp;&amp; echo "Host has been rebooted! Uptime: $(uptime)"</pre>
  6237. ]]></content:encoded>
  6238.  </item>
  6239.  
  6240.  <item>
  6241.    <title>Cottage cheese Avocado Crostini</title>
  6242.    <link>https://blog.x-way.org/Food/2020/04/12/Cottage-cheese-Avocado-Crostini.html</link>
  6243.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324274</guid>
  6244.    <dc:creator>Andreas Jaggi</dc:creator>
  6245.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  6246.    <pubDate>Sun, 12 Apr 2020 19:16:00 +0200</pubDate>
  6247.    <category domain="https://blog.x-way.org/Food/">Food</category>
  6248.    <description><![CDATA[<p>Inspired by <a href="https://fooby.ch/de/rezepte/17073/avocado-ricotta-crostini" title="Avocado-Ricotta-Crostini - Rezepte | fooby.ch">this recipe</a>, I made some yummy Crostini using Cottage cheese (instead of Ricotta cheese) and Avocado with some drops of Aceto balsamico.</p>
  6249. <p><img src="https://blog.x-way.org/images/cottage_cheese_avocado_crostini.jpeg" alt="Cottage cheese Avocado Crostini" width="439" height="329"></p>
  6250. ]]></description>
  6251.    <content:encoded><![CDATA[<p>Inspired by <a href="https://fooby.ch/de/rezepte/17073/avocado-ricotta-crostini" title="Avocado-Ricotta-Crostini - Rezepte | fooby.ch">this recipe</a>, I made some yummy Crostini using Cottage cheese (instead of Ricotta cheese) and Avocado with some drops of Aceto balsamico.</p>
  6252. <p><img src="https://blog.x-way.org/images/cottage_cheese_avocado_crostini.jpeg" alt="Cottage cheese Avocado Crostini" width="439" height="329"></p>
  6253. ]]></content:encoded>
  6254.  </item>
  6255.  
  6256.  <item>
  6257.    <title>Ein Lied für Jetzt</title>
  6258.    <link>https://blog.x-way.org/Music/2020/03/28/Ein-Lied-fur-Jetzt.html</link>
  6259.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324273</guid>
  6260.    <dc:creator>Andreas Jaggi</dc:creator>
  6261.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  6262.    <pubDate>Sat, 28 Mar 2020 08:53:00 +0100</pubDate>
  6263.    <category domain="https://blog.x-way.org/Music/">Music</category>
  6264.    <description><![CDATA[<p><a href="https://youtu.be/t_s6waEUTbI" title="die ärzte - Ein Lied für Jetzt - YouTube">die ärzte - Ein Lied für Jetzt</a></p>
  6265. ]]></description>
  6266.    <content:encoded><![CDATA[<p><a href="https://youtu.be/t_s6waEUTbI" title="die ärzte - Ein Lied für Jetzt - YouTube">die ärzte - Ein Lied für Jetzt</a></p>
  6267. ]]></content:encoded>
  6268.  </item>
  6269.  
  6270.  <item>
  6271.    <title>ip_compact and ip_diff</title>
  6272.    <link>https://blog.x-way.org/Networking/2020/03/21/ip_compact-and-ip_diff.html</link>
  6273.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324272</guid>
  6274.    <dc:creator>Andreas Jaggi</dc:creator>
  6275.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  6276.    <pubDate>Sat, 21 Mar 2020 15:18:00 +0100</pubDate>
  6277.    <category domain="https://blog.x-way.org/Networking/">Networking</category>
  6278.    <description><![CDATA[<p>Somehow I always end up working with lists of IP networks and needing to minimize and compare them.</p>
  6279. <p>Some of my Perl scripts for this might still be hidden in a corporate source repository, and somewhere in the backups of my old Linux laptop should be even earlier attempts in Bash.</p>
  6280. <p>Both of them are not very useful to me where they are, thus I've written yet another version.<br>This time in Go using the <a href="https://github.com/mikioh/ipaddr" title="package ipaddr">ipaddr</a> package.</p>
  6281. <p>Say hello to <a href="https://github.com/x-way/ip_compact" title="ip_compact - Compact a list of IP prefixes">ip_compact</a> and <a href="https://github.com/x-way/ip_diff" title="ip_diff - Compare two lists of IP prefixes">ip_diff</a> :-)</p>
  6282. ]]></description>
  6283.    <content:encoded><![CDATA[<p>Somehow I always end up working with lists of IP networks and needing to minimize and compare them.</p>
  6284. <p>Some of my Perl scripts for this might still be hidden in a corporate source repository, and somewhere in the backups of my old Linux laptop should be even earlier attempts in Bash.</p>
  6285. <p>Both of them are not very useful to me where they are, thus I've written yet another version.<br>This time in Go using the <a href="https://github.com/mikioh/ipaddr" title="package ipaddr">ipaddr</a> package.</p>
  6286. <p>Say hello to <a href="https://github.com/x-way/ip_compact" title="ip_compact - Compact a list of IP prefixes">ip_compact</a> and <a href="https://github.com/x-way/ip_diff" title="ip_diff - Compare two lists of IP prefixes">ip_diff</a> :-)</p>
  6287. ]]></content:encoded>
  6288.  </item>
  6289.  
  6290.  <item>
  6291.    <title>#StayTheFuckHome</title>
  6292.    <link>https://blog.x-way.org/Music/2020/03/17/StayTheFuckHome.html</link>
  6293.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324271</guid>
  6294.    <dc:creator>Andreas Jaggi</dc:creator>
  6295.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  6296.    <pubDate>Tue, 17 Mar 2020 19:33:00 +0100</pubDate>
  6297.    <category domain="https://blog.x-way.org/Music/">Music</category>
  6298.    <description><![CDATA[<p><a href="https://youtu.be/CP70fI3BUs8" title="Bitch Queens - #StayTheFuckHome - YouTube">Bitch Queens - #StayTheFuckHome</a></p>
  6299. <p><a href="https://staythefuckhome.com/" title="Stay The Fuck Home!">Stay The Fuck Home!</a></p>
  6300. ]]></description>
  6301.    <content:encoded><![CDATA[<p><a href="https://youtu.be/CP70fI3BUs8" title="Bitch Queens - #StayTheFuckHome - YouTube">Bitch Queens - #StayTheFuckHome</a></p>
  6302. <p><a href="https://staythefuckhome.com/" title="Stay The Fuck Home!">Stay The Fuck Home!</a></p>
  6303. ]]></content:encoded>
  6304.  </item>
  6305.  
  6306.  <item>
  6307.    <title>This Page is Designed to Last</title>
  6308.    <link>https://blog.x-way.org/Misc/2019/12/20/This-Page-is-Designed-to-Last.html</link>
  6309.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324270</guid>
  6310.    <dc:creator>Andreas Jaggi</dc:creator>
  6311.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  6312.    <pubDate>Fri, 20 Dec 2019 09:56:00 +0100</pubDate>
  6313.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  6314.    <description><![CDATA[<p><a href="https://jeffhuang.com/designed_to_last/" title="This Page is Designed to Last: A Manifesto for Preserving Content on the Web">This Page is Designed to Last</a> &mdash; a manifesto from Jeff Huang for preserving content on the web, where he advocates to keep content on the web available and pledges to keep his site available for the next 10 years.</p>
  6315. <p>Having my content in this weblog online since 2002, I can very much relate to this initiative and additionally would like to point to the efforts of <a href="https://archive.org/">archive.org</a> (aka. The Internet Archive).<br>The wayback machine of archive.org allows to see old versions of websites, even when the website itself is no longer available.</p>
  6316. <p>For me personally this became critically useful when the database of my weblog vanished with no current backup and I then used the archived versions from archive.org to <a href="https://blog.x-way.org/Misc/2011/11/26/Online-Again.html" title="Online Again">restore the missing content</a>.</p>
  6317. <p>Thus I would like to encourage everyone to support the efforts of archive.org with a <a href="https://archive.org/donate/" title="Donate to the Internet Archive!">donation</a>.</p>
  6318. ]]></description>
  6319.    <content:encoded><![CDATA[<p><a href="https://jeffhuang.com/designed_to_last/" title="This Page is Designed to Last: A Manifesto for Preserving Content on the Web">This Page is Designed to Last</a> &mdash; a manifesto from Jeff Huang for preserving content on the web, where he advocates to keep content on the web available and pledges to keep his site available for the next 10 years.</p>
  6320. <p>Having my content in this weblog online since 2002, I can very much relate to this initiative and additionally would like to point to the efforts of <a href="https://archive.org/">archive.org</a> (aka. The Internet Archive).<br>The wayback machine of archive.org allows to see old versions of websites, even when the website itself is no longer available.</p>
  6321. <p>For me personally this became critically useful when the database of my weblog vanished with no current backup and I then used the archived versions from archive.org to <a href="https://blog.x-way.org/Misc/2011/11/26/Online-Again.html" title="Online Again">restore the missing content</a>.</p>
  6322. <p>Thus I would like to encourage everyone to support the efforts of archive.org with a <a href="https://archive.org/donate/" title="Donate to the Internet Archive!">donation</a>.</p>
  6323. ]]></content:encoded>
  6324.  </item>
  6325.  
  6326.  <item>
  6327.    <title>The Comet Is Coming</title>
  6328.    <link>https://blog.x-way.org/Music/2019/11/02/The-Comet-Is-Coming.html</link>
  6329.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324269</guid>
  6330.    <dc:creator>Andreas Jaggi</dc:creator>
  6331.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  6332.    <pubDate>Sat, 02 Nov 2019 11:04:00 +0100</pubDate>
  6333.    <category domain="https://blog.x-way.org/Music/">Music</category>
  6334.    <description><![CDATA[<p><a href="https://youtu.be/G55GspnNkBo" title="The Comet Is Coming - Summon The Fire - YouTube">The Comet Is Coming - Summon The Fire</a></p>
  6335. <p><a href="https://www.thecometiscoming.co.uk/" title="The Comet Is Coming">The Comet Is Coming</a> is a 21st century style Jazz band.<br>
  6336. Discovered at the <a href="https://jazznojazz.ch/" title="Zurich Jazznojazz Festival 2019">Jazznojazz</a> festival :-)</p>
  6337. ]]></description>
  6338.    <content:encoded><![CDATA[<p><a href="https://youtu.be/G55GspnNkBo" title="The Comet Is Coming - Summon The Fire - YouTube">The Comet Is Coming - Summon The Fire</a></p>
  6339. <p><a href="https://www.thecometiscoming.co.uk/" title="The Comet Is Coming">The Comet Is Coming</a> is a 21st century style Jazz band.<br>
  6340. Discovered at the <a href="https://jazznojazz.ch/" title="Zurich Jazznojazz Festival 2019">Jazznojazz</a> festival :-)</p>
  6341. ]]></content:encoded>
  6342.  </item>
  6343.  
  6344.  <item>
  6345.    <title>More productive Git</title>
  6346.    <link>https://blog.x-way.org/Coding/2019/05/25/More-productive-Git.html</link>
  6347.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324268</guid>
  6348.    <dc:creator>Andreas Jaggi</dc:creator>
  6349.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  6350.    <pubDate>Sat, 25 May 2019 07:47:00 +0200</pubDate>
  6351.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  6352.    <description><![CDATA[<p><a href="https://increment.com/open-source/more-productive-git/" title="More productive Git">More productive Git</a> &mdash; a short article from <a href="https://www.kartar.net/" title="Kartar.Net">James Turnbull</a> with 'Tips for acquiring Git super powers'.</p>
  6353. <p>TL;DR:</p>
  6354. <ul>
  6355. <li><code>git reset &lt;filename&gt;</code></li>
  6356. <li><code>git cherry-pick &lt;commitid&gt;</code></li>
  6357. <li><code>git commit --amend</code></li>
  6358. <li><code>git stash</code></li>
  6359. <li><code>git log --stat</code></li>
  6360. <li><code>git bisect</code></li>
  6361. </ul>
  6362. ]]></description>
  6363.    <content:encoded><![CDATA[<p><a href="https://increment.com/open-source/more-productive-git/" title="More productive Git">More productive Git</a> &mdash; a short article from <a href="https://www.kartar.net/" title="Kartar.Net">James Turnbull</a> with 'Tips for acquiring Git super powers'.</p>
  6364. <p>TL;DR:</p>
  6365. <ul>
  6366. <li><code>git reset &lt;filename&gt;</code></li>
  6367. <li><code>git cherry-pick &lt;commitid&gt;</code></li>
  6368. <li><code>git commit --amend</code></li>
  6369. <li><code>git stash</code></li>
  6370. <li><code>git log --stat</code></li>
  6371. <li><code>git bisect</code></li>
  6372. </ul>
  6373. ]]></content:encoded>
  6374.  </item>
  6375.  
  6376.  <item>
  6377.    <title>Engineering Management</title>
  6378.    <link>https://blog.x-way.org/Coding/2019/01/06/Engineering-Management.html</link>
  6379.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324267</guid>
  6380.    <dc:creator>Andreas Jaggi</dc:creator>
  6381.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  6382.    <pubDate>Sun, 06 Jan 2019 13:21:00 +0100</pubDate>
  6383.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  6384.    <description><![CDATA[<p><a href="https://charity.wtf/2019/01/04/engineering-management-the-pendulum-or-the-ladder/" title="Engineering Management: The Pendulum Or The Ladder">Engineering Management: The Pendulum Or The Ladder</a> &mdash; a well written article from <a href="https://charity.wtf/" title="Charity Majors">Charity Majors</a> about the non-trivial entanglement between engineering and management, explaining how doing everything at the same time does lead to unhappy/un-fulfilled people. Also worth reading in this context is the prequel article <a href="https://charity.wtf/2017/05/11/the-engineer-manager-pendulum/" title="The Engineer/Manager Pendulum">The Engineer/Manager Pendulum</a>.</p>
  6385. ]]></description>
  6386.    <content:encoded><![CDATA[<p><a href="https://charity.wtf/2019/01/04/engineering-management-the-pendulum-or-the-ladder/" title="Engineering Management: The Pendulum Or The Ladder">Engineering Management: The Pendulum Or The Ladder</a> &mdash; a well written article from <a href="https://charity.wtf/" title="Charity Majors">Charity Majors</a> about the non-trivial entanglement between engineering and management, explaining how doing everything at the same time does lead to unhappy/un-fulfilled people. Also worth reading in this context is the prequel article <a href="https://charity.wtf/2017/05/11/the-engineer-manager-pendulum/" title="The Engineer/Manager Pendulum">The Engineer/Manager Pendulum</a>.</p>
  6387. ]]></content:encoded>
  6388.  </item>
  6389.  
  6390.  <item>
  6391.    <title>Blogroll cleanup</title>
  6392.    <link>https://blog.x-way.org/Misc/2019/01/06/Blogroll-cleanup.html</link>
  6393.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324266</guid>
  6394.    <dc:creator>Andreas Jaggi</dc:creator>
  6395.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  6396.    <pubDate>Sun, 06 Jan 2019 12:55:00 +0100</pubDate>
  6397.    <category domain="https://blog.x-way.org/Misc/">Misc</category>
  6398.    <description><![CDATA[<p>As some links on my blogroll start to turn into 404 errors it's time to do some cleanup and also to bring in some fresh blood :-)</p>
  6399. <p>Removed:</p>
  6400. <ul>
  6401. <li><a href="https://web.archive.org/web/20200221101248/http://www.mezzoblue.com/" title="mezzoblue">mezzoblue</a></li>
  6402. <li><a href="http://daveshea.com/blog/" title="Dave Shea">Dave Shea</a></li>
  6403. <li><a href="http://www.pepilog.de/" title="Pepilog">Pepilog</a></li>
  6404. <li><a href="https://www.elfengleich.de/" title="Elfengleich">e.loge</a></li>
  6405. <li><a href="https://web.archive.org/web/20180313151513/http://www.ende-der-vernunft.org/" title="EDV">EDV</a></li>
  6406. <li><a href="https://web.archive.org/web/20170221215450/http://sid.rstack.org/blog/" title="sid.rstack.org/blog">sid.rstack.org/blog</a></li>
  6407. <li><a href="https://web.archive.org/web/20161223004544/https://couchblog.de/codecandies/" title="Code Candies">Code Candies</a></li>
  6408. <li><a href="https://thepacketgeek.com/" title="thePacketGeek">thePacketGeek</a></li>
  6409. <li><a href="http://lovfoood.blogspot.com/" title="lovfoood">lovfoood</a></li>
  6410. </ul>
  6411. <p>Added:</p>
  6412. <ul>
  6413. <li><a href="https://charity.wtf/" title="charity.wtf">charity.wtf</a></li>
  6414. </ul>
  6415. ]]></description>
  6416.    <content:encoded><![CDATA[<p>As some links on my blogroll start to turn into 404 errors it's time to do some cleanup and also to bring in some fresh blood :-)</p>
  6417. <p>Removed:</p>
  6418. <ul>
  6419. <li><a href="https://web.archive.org/web/20200221101248/http://www.mezzoblue.com/" title="mezzoblue">mezzoblue</a></li>
  6420. <li><a href="http://daveshea.com/blog/" title="Dave Shea">Dave Shea</a></li>
  6421. <li><a href="http://www.pepilog.de/" title="Pepilog">Pepilog</a></li>
  6422. <li><a href="https://www.elfengleich.de/" title="Elfengleich">e.loge</a></li>
  6423. <li><a href="https://web.archive.org/web/20180313151513/http://www.ende-der-vernunft.org/" title="EDV">EDV</a></li>
  6424. <li><a href="https://web.archive.org/web/20170221215450/http://sid.rstack.org/blog/" title="sid.rstack.org/blog">sid.rstack.org/blog</a></li>
  6425. <li><a href="https://web.archive.org/web/20161223004544/https://couchblog.de/codecandies/" title="Code Candies">Code Candies</a></li>
  6426. <li><a href="https://thepacketgeek.com/" title="thePacketGeek">thePacketGeek</a></li>
  6427. <li><a href="http://lovfoood.blogspot.com/" title="lovfoood">lovfoood</a></li>
  6428. </ul>
  6429. <p>Added:</p>
  6430. <ul>
  6431. <li><a href="https://charity.wtf/" title="charity.wtf">charity.wtf</a></li>
  6432. </ul>
  6433. ]]></content:encoded>
  6434.  </item>
  6435.  
  6436.  <item>
  6437.    <title>New Year - New Vim Trick</title>
  6438.    <link>https://blog.x-way.org/Coding/2019/01/01/New-Year-New-Vim-Trick.html</link>
  6439.    <guid isPermaLink="true">http://waterwave.ch/weblog/detail.php?id=324265</guid>
  6440.    <dc:creator>Andreas Jaggi</dc:creator>
  6441.    <creativeCommons:license>http://creativecommons.org/licenses/by-nd-nc/1.0/</creativeCommons:license>
  6442.    <pubDate>Tue, 01 Jan 2019 22:24:00 +0100</pubDate>
  6443.    <category domain="https://blog.x-way.org/Coding/">Coding</category>
  6444.    <des