https://blog.friz64.de personal blog Zola en Tue, 06 Jan 2026 00:00:00 +0000 Tue, 06 Jan 2026 00:00:00 +0000 Unknown https://blog.friz64.de/karlsruhe-straight-line-challenge/ https://blog.friz64.de/karlsruhe-straight-line-challenge/ <p>The <a href="https://en.wikipedia.org/wiki/Karlsruhe">Karlsruhe</a> straight line challenge is carried out by cycling as close as possible along one of the city's radiating lines, starting from the palace tower, until reaching a natural end.</p> <blockquote> <p>The city [Karlsruhe] was planned with the palace tower (<em>Schloss</em>) at the center and 32 streets radiating out from it like the spokes of a wheel, or the ribs of a folding fan, so that one nickname for Karlsruhe in German is the "fan city" (<em>Fächerstadt</em>).</p> </blockquote> <p>What mainly differentiates this from the "straight line missions" you might have heard of, is that you don't get to choose where the line runs! This challenge is entirely within the spirit of spontanous "go for it and see what happens" adventures (which is one area I personally get my kicks from). This means that there is effectively zero planning, and you just get on a bike and go... along the closest street/path/surface you deem suitable. How many meters you deviate isn't <em>really</em> what's relevant.</p> <p>Here's a simple map of all available lines:</p> <script src="leaflet.js"></script> <link href="leaflet.css" rel="stylesheet" /> <div id="map" style="height: 600px"></div> <script> const center = [8.4044296, 49.0139710]; const map = L.map('map').setView([center[1], center[0]], 12); L.tileLayer('https://tile.openstreetmap.org/{z}/{x}/{y}.png', { attribution: '&copy; <a href="https://www.openstreetmap.org/copyright">OpenStreetMap</a> contributors' }).addTo(map); const features = []; const tau = 2 * Math.PI; const offset = -0.06806784; for (let angle = offset; angle < tau + offset; angle += tau / 32) { features.push({ 'type': 'Feature', 'geometry': { 'type': 'LineString', 'coordinates': [center, [ center[0] + Math.cos(angle), center[1] + Math.sin(angle) * 0.65587497, // dw abt it ❤️ ]] } }); } L.geoJSON( { 'type': 'FeatureCollection', 'features': features }, { style: { color: '#f00', weight: 2 } } ).addTo(map); </script> <p>I recommend the Organic Maps app for your phone, which is the perfect tool for guiding you. If you're fancy you can even trace out a rough route beforehand, and then load it into the app. I've found it to be a bit annoying having to constantly stop to "live-plan" the route.</p> <h2 id="my-personal-adventures-contains-spoilers">My personal adventures (contains spoilers!)<a class="zola-anchor" href="#my-personal-adventures-contains-spoilers" aria-label="Anchor link for: my-personal-adventures-contains-spoilers">§</a> </h2> <p>I hope to update this list as I continue doing these. Because I still don't own a bike, and I'm a bit crazy, I did all of these using bike sharing bikes from KVV.nextbike (I'm sorry for getting them dirty!). Yet this does have the nice side effect that I can just leave the bike in a participating city, and ride the train home without it!</p> <h3 id="the-northern-via-triumphalis-line">The northern <a href="https://de.wikipedia.org/wiki/Via_Triumphalis_(Karlsruhe)">"Via Triumphalis"</a> line<a class="zola-anchor" href="#the-northern-via-triumphalis-line" aria-label="Anchor link for: the-northern-via-triumphalis-line">§</a> </h3> <p>Attempted 2025-06-28. This one starts out very easy, as you follow along a purpose-built bike path for the first ~9km. You're conveniently spit out at the B36/L559 intersection near Leopoldshafen, after which you're on your own. Trekking through various bicycle-unfriendly fields, the line will perfectly lead you over a railroad-crossing of the AVG branch line to KIT Campus Nord. The remainder of the route will have you navigating various towns, farmland, as well as a cut-off meander of the river Rhine. There's some pretty ugly offroad sections. The "natural end" here is a a nice camping/lookout spot at the Rhine.</p> <table><thead><tr><th><img src="https://blog.friz64.de/karlsruhe-straight-line-challenge/northern1.jpg" alt="the AVG crossing" /></th><th><img src="https://blog.friz64.de/karlsruhe-straight-line-challenge/northern2.jpg" alt="nextbike at night" /></th></tr></thead><tbody> </tbody></table> <h3 id="the-waldstrasse-line">The "Waldstraße" line<a class="zola-anchor" href="#the-waldstrasse-line" aria-label="Anchor link for: the-waldstrasse-line">§</a> </h3> <p>Attempted 2025-09-06. This has you leave Karlsruhe through ZKM/HfG, following Tram 4 to Oberreut, after which you will encounter a glider airstrip, and the Epplesee lake. Durmersheim will have you go right through a schoolyard, and lead you right into a fair bit of forestry. After Steinmauern there's a pretty well placed bridge over the Murg river, followed by a bunch of more countryside. If you spot an old boat floating in the water (the "Aalschokker Heini"), you've also pretty much reached the old Rhine bridge near Wintersdorf. That bridge is placed dead-center on the line, which is an invitation to keep going to France, but I decided to call quits here.</p> <p><img src="https://blog.friz64.de/karlsruhe-straight-line-challenge/waldstrasse.png" alt="map showing GPS recording" title="actual GPS recording" /></p> <table><thead><tr><th><img src="https://blog.friz64.de/karlsruhe-straight-line-challenge/waldstrasse1.jpg" alt="nextbike on schoolyard" /></th><th><img src="https://blog.friz64.de/karlsruhe-straight-line-challenge/waldstrasse2.jpg" alt="the &quot;Aalschokker Heini&quot;" /></th><th><img src="https://blog.friz64.de/karlsruhe-straight-line-challenge/waldstrasse3.jpg" alt="Wintersdorf bridge" /></th></tr></thead><tbody> </tbody></table> <h2 id="final-words">Final words<a class="zola-anchor" href="#final-words" aria-label="Anchor link for: final-words">§</a> </h2> <p>If you're mad enough to try one of these on your own, please don't hesitate to tell me about it!!! <a href="https://friz64.de">friz64.de</a></p> Sun, 09 May 2021 00:00:00 +0000 Unknown https://blog.friz64.de/ergodox-rawhid/ https://blog.friz64.de/ergodox-rawhid/ <p>After searching for a new keyboard for some while, the <a href="https://ergodox-ez.com/">ErgoDox EZ</a> caught my attention. It is an open-source, ergonomic, split, mechanical keyboard.</p> <p>We'll be looking at the hardware itself, getting to know the ErgoDox, setting up a custom firmware, communication between my PC and the EZ, the program controlling lighting (including an <strong>live audio spectrum analyzer</strong>) and displaying the current words per minute on the screen.</p> <h2 id="the-hardware">The hardware<a class="zola-anchor" href="#the-hardware" aria-label="Anchor link for: the-hardware">§</a> </h2> <p>The website configurator gives you quite a few options to personalize various features of your keyboard. I went with the white version, a tilt kit (which lets you adjust the angle of your keyboard), white wrist rests, RGB underglow (called "Shine"), Cherry MX Brown switches and blank keycaps.</p> <p>The wait began on Monday, April 5th, 2021 when I ordered the keyboard. After which it took just over 2 weeks to get the shipping notification email in my inbox on Tuesday, April 20th. While excitedly refreshing the UPS tracking page more often than was necessary, I got the keyboard in the mail on Thursday, April 22nd.</p> <h3 id="small-gallery">Small gallery<a class="zola-anchor" href="#small-gallery" aria-label="Anchor link for: small-gallery">§</a> </h3> <p><img src="https://blog.friz64.de/ergodox-rawhid/desk.jpg" alt="My desk setup" /></p> <p>I found the gap in between the two keyboard halves to be an excellent place for the notebook you're scribbling in.</p> <p>In the picture on the right, I used the wrong side of the puller. Thanks <a href="https://www.reddit.com/r/ergodox/comments/n8f4hq/my_ergonomic_keyboard_adventure_ergodox_ez/gxi7wcx">u/GnastyNoodlez</a> for pointing that out. It's staying in the post for fun!</p> <table><thead><tr><th><img src="https://blog.friz64.de/ergodox-rawhid/packaging.jpg" alt="The packaging it came in" /></th><th><img src="https://blog.friz64.de/ergodox-rawhid/key.jpg" alt="A pulled keycap and the MX Brown switch" /></th></tr></thead><tbody> </tbody></table> <p>And here's the LED strip on the back of one side. It will see heavy use later.</p> <p><img src="https://blog.friz64.de/ergodox-rawhid/led_strip.jpg" alt="Back of the left side, showing 15 LEDs" /></p> <p>Counting... 15 LEDs, so in total there are 30.</p> <h2 id="learning-to-type-again">Learning to type again<a class="zola-anchor" href="#learning-to-type-again" aria-label="Anchor link for: learning-to-type-again">§</a> </h2> <p>There is probably no better way of showcasing my progress than the WPM graph on <a href="https://monkeytype.com/">monkeytype.com</a>.</p> <p><img src="https://blog.friz64.de/ergodox-rawhid/wpm_graph.jpg" alt="WPM graph, showing a reset followed by a steady climb" /></p> <p>Two days after I started using the keyboard, I woke up with the magic ability to type comfortably. This period is represented by the "<em>valley</em>" in this graph.</p> <p>On a regular keyboard, every row of keys is offset from another. This is what's known as <strong>row-stagger</strong> and was carried over from the needs of typewriters. The ErgoDox, on the other hand, is <strong>column-staggered</strong>, which adjusts each <em>column</em> of keys for the different lengths of your individual fingers, improving ergonomics.</p> <p>When typing characters itself, which is what was measured on monkeytype, this was the biggest hurdle. But what about special characters? Those are placed on an extra layer (which we'll get to now). For these it took around 2 weeks for me to know off the top of my head and somewhat comfortably use.</p> <h2 id="the-layout">The layout<a class="zola-anchor" href="#the-layout" aria-label="Anchor link for: the-layout">§</a> </h2> <p>ZSA (the company I bought my ErgoDox from) provides an online configurator called Oryx. Using this tool I went through <strong>28</strong> iterations before ending up on the perfect layout (until now). For the characters themselves, I use <a href="https://colemak.com/">Colemak</a>.</p> <blockquote> <p>Learning Colemak is a one-time investment that will allow you to enjoy faster and pain-free typing for the rest of your life.</p> </blockquote> <p>Note that this image still shows QWERTY as I apply it through software. This helps with game support.</p> <p><img src="https://blog.friz64.de/ergodox-rawhid/oryx.jpg" alt="Base layer, with normal keys" /></p> <p>In total, the keyboard features 76 keys. This is not enough for everything you'd want to do (e.g. FN keys). That's the problem <em>layers</em> are here to solve. There are numerous possible ways of switching between them, but I ended up activating a certain layer while a specific key is held down (as marked in the above image). You can take a closer look at my setup yourself in <a href="https://configure.zsa.io/ergodox-ez/layouts/VYdw7/latest/0">the configurator</a>.</p> <h2 id="compiling-my-own-firmware">Compiling my own firmware<a class="zola-anchor" href="#compiling-my-own-firmware" aria-label="Anchor link for: compiling-my-own-firmware">§</a> </h2> <p>Under the hood, Oryx generates and compiles C code, which you then flash onto the microcontroller on your board. But what I wanted to do was take advantage of some extra features of the powerful <a href="https://qmk.fm/">QMK firmware</a> to my disposal.</p> <blockquote> <p>The goal of the QMK software project is to develop a completely customizable, powerful, and enjoyable firmware experience for any project - keyboard or otherwise - and to provide helpful, encouraging, and kind support and feedback for people with any software development experience.</p> </blockquote> <p>There is a button that lets you download the layout's <em>source code</em>. So I installed ZSA's qmk fork on my computer, fed it the layout and, after some time, managed to compile it! Apparently I had really good luck that day, because it worked on the first try upon flashing it 🎉</p> <details> <summary>Here's what the keymap looks like in source-code form.</summary> <pre data-lang="c" style="background-color:#1e1e1e;color:#dcdcdc;" class="language-c "><code class="language-c" data-lang="c"><span style="color:#569cd6;">const </span><span>uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = { </span><span> [</span><span style="color:#b5cea8;">0</span><span>] = LAYOUT_ergodox_pretty( </span><span> KC_ESCAPE, KC_1, KC_2, KC_3, KC_4, KC_5, KC_TRANSPARENT, KC_TRANSPARENT, KC_6, KC_7, KC_8, KC_9, KC_0, KC_MINUS, </span><span> KC_TAB, KC_Q, KC_W, KC_E, KC_R, KC_T, LGUI(KC_D), KC_TRANSPARENT, KC_Y, KC_U, KC_I, KC_O, KC_P, KC_BSLASH, </span><span> KC_LALT, KC_A, KC_S, KC_D, KC_F, KC_G, KC_H, KC_J, KC_K, KC_L, KC_SCOLON, LT(</span><span style="color:#b5cea8;">2</span><span>,KC_QUOTE), </span><span> KC_LSHIFT, KC_Z, KC_X, KC_C, KC_V, KC_B, KC_HYPR, KC_MEH, KC_N, KC_M, KC_COMMA, KC_DOT, KC_SLASH, KC_RSHIFT, </span><span> KC_CAPSLOCK, KC_LGUI, KC_LEFT, KC_RIGHT, LCTL(KC_SPACE), KC_RALT, KC_UP, KC_DOWN, KC_DELETE, KC_RCTRL, </span><span> KC_MEDIA_PLAY_PAUSE,KC_HOME, KC_PGUP, KC_MEDIA_NEXT_TRACK, </span><span> KC_END, KC_PGDOWN, </span><span> KC_SPACE, MO(</span><span style="color:#b5cea8;">1</span><span>), KC_LCTRL, KC_ESCAPE, KC_ENTER, KC_BSPACE </span><span> ), </span><span> [</span><span style="color:#b5cea8;">1</span><span>] = LAYOUT_ergodox_pretty( </span><span> KC_ESCAPE, KC_F1, KC_F2, KC_F3, KC_F4, KC_F5, KC_TRANSPARENT, KC_TRANSPARENT, KC_F6, KC_F7, KC_F8, KC_F9, KC_F10, KC_F11, </span><span> KC_TRANSPARENT, KC_EXLM, KC_AT, KC_LCBR, KC_RCBR, KC_PIPE, KC_TRANSPARENT, KC_TRANSPARENT, KC_ASTR, KC_7, KC_8, KC_9, KC_MINUS, KC_F12, </span><span> KC_TRANSPARENT, KC_HASH, KC_DLR, KC_LPRN, KC_RPRN, KC_GRAVE, KC_EQUAL, KC_4, KC_5, KC_6, KC_PLUS, KC_TRANSPARENT, </span><span> KC_TRANSPARENT, KC_PERC, KC_CIRC, KC_LBRACKET, KC_RBRACKET, KC_TILD, KC_TRANSPARENT, KC_TRANSPARENT, KC_AMPR, KC_1, KC_2, KC_3, KC_BSLASH, KC_TRANSPARENT, </span><span> KC_TRANSPARENT, KC_EQUAL, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_DOT, KC_0, KC_EQUAL, KC_TRANSPARENT, </span><span> KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, </span><span> KC_TRANSPARENT, KC_TRANSPARENT, </span><span> KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_0 </span><span> ), </span><span> [</span><span style="color:#b5cea8;">2</span><span>] = LAYOUT_ergodox_pretty( </span><span> KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, RESET, </span><span> KC_TRANSPARENT, KC_TRANSPARENT, KC_MS_UP, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, </span><span> KC_TRANSPARENT, KC_MS_LEFT, KC_MS_DOWN, KC_MS_RIGHT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, </span><span> KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, </span><span> KC_TRANSPARENT, WEBUSB_PAIR, KC_TRANSPARENT, KC_TRANSPARENT, KC_MS_BTN3, KC_AUDIO_VOL_UP,KC_AUDIO_VOL_DOWN,KC_AUDIO_MUTE, KC_TRANSPARENT, KC_TRANSPARENT, </span><span> KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, </span><span> KC_TRANSPARENT, KC_TRANSPARENT, </span><span> KC_MS_BTN1, KC_MS_BTN2, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT, KC_TRANSPARENT </span><span> ), </span><span>}; </span></code></pre> </details> <h2 id="the-protocol-raw-hid-and-c-implementation">The protocol, raw HID and C implementation<a class="zola-anchor" href="#the-protocol-raw-hid-and-c-implementation" aria-label="Anchor link for: the-protocol-raw-hid-and-c-implementation">§</a> </h2> <p>In order to connect my computer to the code running on my board, I needed a way to live-communicate between the two. This is what's called <a href="https://docs.qmk.fm/#/feature_rawhid">raw HID</a>.</p> <blockquote> <p>Raw HID allows for bidirectional communication between QMK and the host computer over an HID interface. This has many potential use cases, such as switching keymaps on the fly or changing RGB LED colors and modes.</p> </blockquote> <p>On the EZ, the maximum size of such a packet is 32 bytes. In my protocol, the first byte is used to denote the packet ID. Here's an overview of all packets sent from my custom program running on the host computer to QMK.</p> <table><thead><tr><th>ID</th><th>Name</th><th>Content (<code>arguments</code> -&gt; <code>return</code>)</th></tr></thead><tbody> <tr><td>0</td><td>No Op</td><td><code>()</code> -&gt; <code>()</code></td></tr> <tr><td>1</td><td>Set full HSV</td><td><code>(h: u8, s: u8, v: u8)</code> -&gt; <code>()</code></td></tr> <tr><td>2</td><td>Update Cycle</td><td><code>(cycle: u8, brightnesses: [u8; 30])</code> -&gt; <code>()</code></td></tr> <tr><td>3</td><td>Fetch WPM</td><td><code>()</code> -&gt; <code>(wpm: u8)</code></td></tr> <tr><td>4</td><td>Get user config</td><td><code>()</code> -&gt; <code>(mode: u8, brightness: u8)</code></td></tr> <tr><td>5</td><td>Set user config</td><td><code>(mode: u8, brightness: u8)</code> -&gt; <code>()</code></td></tr> </tbody></table> <p>Okay, that's a lot to take in at once. Let's go through it all.</p> <ul> <li><em>Set full HSV</em>: Allows you to set every LED to the same color, specified by HSV (<strong>h</strong>ue, <strong>s</strong>aturation, <strong>v</strong>alue/brightness/lightness). This packet is used for the <em>Constant white</em> and <em>Off</em> mode.</li> <li><em>Update Cycle</em>: "Spreads" the color hues over every LED on the keyboard, producing a rainbow-like pattern, offset by the <code>cycle</code>. The <code>brightnesses</code> array specifies the brightness for every one of the 30 LEDs. This packet is used for the <em>Spectrum analyzer</em> and <em>Color cycle</em> mode.</li> <li><em>Fetch WPM</em>: Uses the <a href="https://docs.qmk.fm/#/feature_wpm">WPM calculation</a> feature of QMK to return the current words per minute. This is going to be continuously called and displayed to the user.</li> <li><em>Get/Set user config</em>: Used for storing the program state on the keyboard. Yes, really! The configuration is stored in the board's EEPROM and gets saved after 5 seconds of losing connection to the host program.</li> </ul> <p>Everything described here is implemented in the <a href="https://gitlab.com/Friz64/ergodox-rawhid/-/blob/3b5689360070cf9c2f10ae75f58fabf819a5f9c5/rawhid-friz64/keymap.c">keymap.c</a> file.</p> <h2 id="the-host-program">The host program<a class="zola-anchor" href="#the-host-program" aria-label="Anchor link for: the-host-program">§</a> </h2> <p>I decided to write this in the Rust programming language, as I am very proficient with it and it was the perfect choice for my requirements. Take a look at the source <a href="https://gitlab.com/Friz64/ergodox-rawhid/-/tree/3b5689360070cf9c2f10ae75f58fabf819a5f9c5/src">here</a>.</p> <p>Adjusting the settings is quick using a <code>StatusNotifierItem</code> user interface, created using the <a href="https://crates.io/crates/ksni"><code>ksni</code></a> crate. Scroll on the icon to change the brightness.</p> <p><img src="https://blog.friz64.de/ergodox-rawhid/ui.jpg" alt="user interface" /></p> <h3 id="wpm-display">WPM display<a class="zola-anchor" href="#wpm-display" aria-label="Anchor link for: wpm-display">§</a> </h3> <p>First I went the route of generating an icon for each number 0-255 and displaying that in my existing tray indicator, but that really didn't work out. So, I went the slightly less hacky way and wrote my first ever GNOME extension: <code>wpmdisplay</code>. It exposes a DBus method <code>UpdateWPM</code>, taking the current words per minute as a byte and adding that as an indicator to the GNOME status area. The code is by far not ideal but... it works! /shrug</p> <p>Here's the <a href="https://gitlab.com/Friz64/ergodox-rawhid/-/blob/3b5689360070cf9c2f10ae75f58fabf819a5f9c5/wpmdisplay@friz64.de/extension.js">source code</a>.</p> <h3 id="modes">Modes<a class="zola-anchor" href="#modes" aria-label="Anchor link for: modes">§</a> </h3> <p>Wait, what exactly are these <em>modes</em> I was talking about? Well, the user will have the choice between several lighting modes. Onto the good stuff!</p> <h4 id="constant-white">Constant white<a class="zola-anchor" href="#constant-white" aria-label="Anchor link for: constant-white">§</a> </h4> <p>This displays the color white in the currently specified brightness.</p> <p><img src="https://blog.friz64.de/ergodox-rawhid/mode_white.jpg" alt="Picture of the left side with all white LEDs" /></p> <p>Very cozy~!</p> <h4 id="spectrum-analyzer">Spectrum analyzer<a class="zola-anchor" href="#spectrum-analyzer" aria-label="Anchor link for: spectrum-analyzer">§</a> </h4> <p>Probably the coolest of the bunch. Uses the <a href="https://crates.io/crates/spectrum-analyzer"><code>spectrum-analyzer</code></a> crate to live-process the currently playing audio and display the frequency spectrum on the keyboard. The lower frequencies are on the left and the higher ones on the right. The louder the music in general, the faster the hue cycle moves.</p> <div> <a href="https://youtube.com/watch?v=AClXINk_gM0"> <figure class="yt-nonembed"> <img src="https://i3.ytimg.com/vi/AClXINk_gM0/maxresdefault.jpg"> <figcaption>Click to watch on YouTube</figcaption> </figure> </a> </div> <p>This took some time to get right, as there are several things to consider. For example, there are generally more lower frequencies in my audio than higher ones, so the right side's lights were noticeably less lit up. The easy but very effective solution was to double the brightness of the higher frequencies.</p> <p>Here's the source code: <a href="https://gitlab.com/Friz64/ergodox-rawhid/-/blob/3b5689360070cf9c2f10ae75f58fabf819a5f9c5/src/analyzer.rs"><code>analyzer.rs</code></a>.</p> <h4 id="color-cycle">Color cycle<a class="zola-anchor" href="#color-cycle" aria-label="Anchor link for: color-cycle">§</a> </h4> <p>Moves through the rainbow pattern at a constant rate.</p> <picture> <source srcset="mode_cycle.webp" type="image/webp"> <img src="mode_cycle.gif" alt="Video of the keyboard going through a full cycle"> </picture> <h2 id="that-s-everything-for-this-post">That's everything for this post<a class="zola-anchor" href="#that-s-everything-for-this-post" aria-label="Anchor link for: that-s-everything-for-this-post">§</a> </h2> <p>Here's the direct link to the entire <a href="https://gitlab.com/Friz64/ergodox-rawhid">source repo</a>.</p> <p>Any questions? Possible improvements? What didn't you like? <a href="/about">Let me know.</a></p> <p>Until next time! 👋</p>