nuxx.net

Test Post

July 19, 2026

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi ornare eleifend quam sed molestie. Nullam velit est, faucibus at vehicula vitae, fringilla vitae risus. Pellentesque lobortis ullamcorper mi ut ultrices. Vestibulum viverra eu tellus in convallis. Curabitur gravida libero quis viverra pretium. Morbi eu imperdiet diam. Donec auctor nisi id sodales sollicitudin. Donec congue fringilla erat nec condimentum. Morbi dapibus semper libero at malesuada. Sed venenatis ligula ut enim elementum vulputate. Donec id felis cursus, porta magna id, molestie nunc. Donec luctus dictum rhoncus. Maecenas convallis ornare libero, in venenatis nunc feugiat eu. Maecenas in odio et mauris laoreet interdum in a ipsum. Morbi nulla lectus, hendrerit ac turpis ac, imperdiet tincidunt dolor.

Aliquam consectetur nisl vel libero vehicula elementum. Nunc non ante a magna varius semper nec sed quam. Suspendisse in felis odio. Nam sagittis rhoncus elit non condimentum. Maecenas eros mauris, gravida eget luctus eu, dapibus a sem. Phasellus in maximus eros, ac placerat justo. Morbi libero augue, laoreet a faucibus eget, rhoncus euismod velit.

Praesent enim lacus, finibus at nisi ac, tincidunt imperdiet justo. Vivamus nulla ex, lobortis ac sapien eget, bibendum eleifend lacus. Aenean vulputate eget neque nec congue. Duis congue velit vitae eros laoreet congue. Nam velit erat, rhoncus sit amet interdum sed, aliquam vitae turpis. Vestibulum vel hendrerit lorem. Maecenas eu elit ut quam egestas commodo. Nunc facilisis vulputate diam, vitae euismod nibh mollis et. Aliquam et ipsum eu lacus pharetra congue. Sed vel tempus nulla. Pellentesque arcu orci, aliquet gravida ipsum rhoncus, varius suscipit urna. Curabitur a sollicitudin magna. Aliquam congue eros eu nibh facilisis, vel consectetur mi venenatis. Aliquam finibus leo quam, at finibus erat tempus nec.

Duis quis ex mauris. Nunc vel eleifend elit. Mauris mi nisl, suscipit vel porttitor eget, iaculis eu odio. Nullam tellus lectus, viverra ac dictum id, volutpat in augue. Fusce sagittis, urna sit amet feugiat eleifend, ligula lacus viverra libero, id venenatis eros justo vel ipsum. Sed dapibus et risus ac fringilla. Nunc quis sodales nunc. Sed id dui bibendum, aliquet risus in, vestibulum lectus. Ut in lectus sed enim luctus fermentum. Nulla id est mollis, lobortis risus accumsan, maximus tellus. Nulla vestibulum lobortis ante a euismod. Integer a scelerisque dui. Nullam viverra, lectus eu convallis tempor, nisi lectus venenatis lorem, vel pellentesque ex lorem ac nulla. Proin dignissim congue diam in congue.

Duis in suscipit mauris, eget accumsan urna. Suspendisse vestibulum consequat nulla, euismod sagittis sem eleifend vel. Aliquam non quam a diam eleifend auctor. Aliquam urna leo, luctus at ornare in, iaculis vel nulla. Nullam semper cursus massa, quis laoreet risus ultrices volutpat. Suspendisse massa lorem, malesuada eu sapien eu, placerat mollis tortor. In hac habitasse platea dictumst. Aliquam vestibulum tempor tortor sit amet tristique. Fusce id enim id ex semper pulvinar. Integer vitae leo eu lacus rutrum dignissim. Proin a sodales lorem, id accumsan velit.

Morbi mattis euismod erat sed ornare. Sed sit amet ante eu nisl scelerisque tincidunt. Vestibulum sodales consequat nulla vitae volutpat. Aenean at libero non tellus dictum hendrerit at a orci. Integer congue urna et pharetra sagittis. Nunc consequat eget metus id finibus. Aliquam a lectus ex. Vivamus semper, ex et porta egestas, nulla eros bibendum augue, a gravida nisi magna ut lectus. Maecenas volutpat ligula at tempus sollicitudin. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Praesent eget gravida sem. In faucibus, tortor quis tempus porta, nibh velit auctor ligula, a rhoncus eros neque quis turpis.

Vestibulum congue sem eget massa semper commodo. Aliquam at dapibus metus. Vivamus mollis tempor tellus eu pellentesque. Nullam vehicula enim ut feugiat egestas. Sed rutrum mauris eget ex varius, sit amet gravida velit mollis. Fusce ex orci, suscipit vitae vehicula quis, interdum non tellus. Orci varius natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Sed aliquam ligula nisl, sit amet tempus massa ornare non. Cras eu ornare enim, ac scelerisque nisi. Praesent vestibulum luctus aliquet. Vivamus lobortis condimentum arcu, id interdum massa viverra ac. Vestibulum est lectus, finibus vitae enim id, ullamcorper rutrum libero. Nullam feugiat ex sed ipsum elementum, sit amet molestie quam cursus. Praesent posuere vel orci et dignissim. Aenean viverra suscipit fermentum.

Donec sapien nisi, commodo ac dignissim congue, faucibus in quam. Aliquam ut ligula vehicula, fringilla nisl sit amet, volutpat tortor. Quisque bibendum tristique porta. Pellentesque ac nunc luctus risus placerat ultricies. Duis volutpat nisl eu nisl ornare, ac tempor ante dapibus. Duis sapien lorem, laoreet vel molestie id, consectetur et libero. Donec venenatis, velit eu suscipit mollis, ex eros mattis mauris, ut ornare magna nunc nec lectus. Morbi erat elit, rhoncus at efficitur nec, ullamcorper et turpis. Cras luctus tellus massa, non efficitur magna pharetra vel. Nullam mattis purus lacus, vel posuere justo lacinia tincidunt. Quisque iaculis volutpat enim. Maecenas in mollis massa. Ut vitae mi ac enim venenatis mollis. Nulla arcu sem, tempus ac iaculis et, luctus non urna. Etiam id nibh nec orci finibus varius a ac mi.

Mauris quis metus elementum, sodales elit vitae, gravida odio. Nulla sed ipsum non lacus bibendum finibus quis id nisl. Donec et lacus leo. In a diam id magna venenatis dignissim sit amet id nulla. Vestibulum ultrices, mi nec vehicula auctor, tortor mauris fermentum lacus, sed convallis velit lectus nec mi. Donec quis nulla scelerisque, tempor lectus sit amet, facilisis erat. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Cras elit lorem, pharetra ac metus vel, congue tempus metus.

Nulla vitae ligula non nibh aliquam hendrerit vitae in quam. Donec fringilla dui at tellus finibus, ac pulvinar orci viverra. Donec eleifend, velit vel vestibulum lobortis, quam risus suscipit dolor, eget vestibulum ex sem ac dolor. Duis condimentum sollicitudin ipsum, ac dictum purus gravida nec. Donec dapibus a sapien eu pellentesque. Sed in nisl pellentesque ex viverra eleifend. Suspendisse consectetur vestibulum molestie. Sed eu urna a enim pharetra tincidunt eget convallis velit. Proin ornare tincidunt purus ut aliquet. Nunc laoreet ipsum eget nunc aliquam sollicitudin.

Praesent faucibus felis mauris. Nulla semper lectus vel dui rutrum, eu hendrerit diam scelerisque. Cras in sem enim. Quisque velit odio, dictum ut euismod id, luctus et arcu. Lorem ipsum dolor sit amet, consectetur adipiscing elit. In dictum consectetur lacus, a semper leo maximus in. Duis cursus vel tellus quis consectetur. Duis aliquet urna vel tortor blandit dictum eu vel mauris. Nulla varius imperdiet sapien. In mattis tincidunt lorem, at vehicula purus scelerisque sit amet.

In pretium, eros et faucibus gravida, tortor dolor viverra dui, in congue enim est at orci. Vivamus consectetur semper turpis ac consectetur. Pellentesque sit amet augue ut lacus imperdiet feugiat vitae eget velit. Proin vitae velit est. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Fusce mattis sapien feugiat mi venenatis ornare. Mauris a odio mauris. Sed porta mi tellus, a lobortis velit lobortis id. Nunc imperdiet nisi vel purus mattis iaculis. Pellentesque turpis ante, feugiat at venenatis elementum, lobortis et mi.

Quisque vitae metus id justo volutpat finibus sed vitae lectus. Proin ut eros risus. Sed porttitor ex at sapien pulvinar efficitur. Donec porttitor erat sit amet est varius mattis. In sollicitudin vulputate mauris, a sagittis mi rhoncus ac. Sed nec quam ut ex varius accumsan. Fusce eget mauris neque. Nunc et accumsan metus, et convallis ligula. Cras vel faucibus odio, tincidunt tempus nulla. Cras id blandit mi.

Aliquam porta fringilla congue. Etiam viverra sagittis diam, et placerat dolor. Cras ac elementum leo. Nam sed sodales ligula. Nullam molestie lacinia tortor. Sed blandit placerat facilisis. Suspendisse potenti. Maecenas non massa eget tortor mattis sodales in sed orci. Donec in lobortis dolor, ac rhoncus enim. Sed in varius ante. Etiam magna purus, condimentum ut lobortis sit amet, accumsan eu odio. Nam sed consectetur diam. Nullam ex ante, fermentum et leo molestie, dignissim lobortis nisl.

Aliquam sed dolor neque. Mauris neque nunc, imperdiet vitae vehicula quis, porta ut nunc. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce laoreet metus non eros interdum consectetur. Sed vitae venenatis erat, id laoreet nisi. Phasellus placerat velit at ante venenatis, quis malesuada ante congue. Integer condimentum augue suscipit congue gravida. Vivamus purus risus, dapibus in felis vel, posuere vestibulum metus. Phasellus ut viverra orci. Donec consequat quam id metus consequat dapibus. Integer quis leo lectus. Cras iaculis et mauris quis sagittis. Vestibulum euismod lorem vel tortor egestas, accumsan bibendum nisl rutrum.

Nam at augue orci. Vivamus semper quam et neque ultrices tincidunt. Maecenas id viverra urna. Vestibulum facilisis consequat condimentum. Orci varius natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Sed aliquam tellus sed eros porttitor mollis. Proin ac turpis id dui fringilla luctus. Sed blandit, orci a sollicitudin finibus, arcu ligula efficitur dui, id iaculis mauris nunc ac sem. Phasellus a turpis quis ante sollicitudin aliquam in ut dolor. Nullam urna ligula, congue ac eros non, faucibus interdum mauris. Donec odio nulla, ornare sed posuere a, luctus sit amet ipsum.

Quisque felis turpis, ultricies et dui a, porttitor aliquet mauris. Nullam rhoncus commodo leo, sit amet porttitor enim lobortis ac. Pellentesque in nisi egestas, tincidunt dolor nec, luctus erat. Pellentesque et nulla orci. Vivamus tincidunt sem orci, ut dapibus urna eleifend a. Vestibulum justo lacus, egestas vel mi in, sodales ultricies tortor. Ut eu bibendum tortor, eu condimentum est. Integer blandit magna non rutrum placerat.

Praesent euismod ut urna id venenatis. Maecenas ornare ipsum a sapien aliquam porttitor. Integer imperdiet ac dolor at blandit. Fusce pellentesque est quis consequat commodo. Pellentesque ut sem tellus. Proin pulvinar metus quis condimentum aliquet. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Suspendisse malesuada, metus sed fringilla pharetra, quam ligula consequat quam, nec tincidunt tellus velit vitae tellus.

Mauris feugiat, elit quis malesuada placerat, nulla quam malesuada tortor, in semper sem justo a metus. Donec ultrices sed ante aliquet auctor. Nullam at semper mi, in cursus tellus. Nullam bibendum mollis pharetra. Donec ullamcorper orci quis libero rutrum eleifend. Sed at lectus nec elit pellentesque molestie. Proin euismod, arcu quis viverra dignissim, nibh odio sagittis tortor, ut tempor velit magna ut eros.

Suspendisse suscipit condimentum lorem, ac blandit lacus consequat ut. Nullam tempus, lacus vitae pellentesque aliquet, mi sapien fermentum lacus, nec placerat nisl enim a ligula. Praesent vulputate sodales quam. Nulla non purus sapien. Proin ut mattis nunc. Ut quis dolor et ipsum ornare hendrerit. Ut tellus leo, pretium efficitur urna in, pharetra maximus felis.

Uncategorized

KICKR CORE 2 Tennis Ball Feet

July 16, 2026

Tennis ball rocker feet on my KICKR CORE 2.

Last winter, after getting a Wahoo KICKR CORE 2 trainer and designing some variable height feet to level the bike I kept thinking about tennis ball feet. These provide a bit of give, allowing the trainer to rock and pitch a bit, reportedly making it more comfortable to ride. (And yes, for some reason I sat on this post for half a year before finishing it up.)

I’ve never really noticed an issue with the static positioning of any of my trainers, but Kristen purchased a KOM Cycling Indoor Rocker Plate RPV1 while getting ready for AIDS/LifeCycle in 2021/2022 and now finds she can’t really ride indoors without it. Her experience, and hearing nice things about tennis ball feet from others, has made me wonder how something similar might be for me.

There’s a whole bunch of tennis ball feet available for trainers. From the well-engineered ones that my friend Jake / Cycl3dCo makes and sells to a bunch of free designs on Printables and MakerWorld, there’s… a lot of options. Mostly because I couldn’t find one that was low enough profile to not require a riser block for the front tire (the inverse of the problem which prompted my trainer foot design), a bit of late-December poor weather boredom, wanting to get better at drawing stuff, and perhaps a bit of NIH, I decided to try designing my own.

Detail of four of my KICKR CORE 2 low profile tennis ball rocker feet.

Here’s what I came up with. These are yet-another-set-of tennis ball feet, but they are designed so that with a 700c x 32mm front tire on the bike the axles are level during riding, and they replace the stock rubber feet and are held in place with the original retention screws.

I restarted this design numerous times over a few days and learned a lot about constraints and what not to do. I was originally going to make this a parametric design like the variable height feet, but realized it’s not as useful and stuck to a single height. This also allowed me to take some shortcuts in constraining drawings… Not the best practice, but not horrible for what I was doing.

The final items were printed using the same filament and profile as the Riser Feet (Overture PETG in black, 6 walls, 25% gyroid infill, printed hot and very slow), and they came out nicely. Because of the quantity of filament needed (estimated ~529g) I started on one spool and used the AMS to auto-swap to the second when the first ran out. I was a bit nervous about how this would go, but it ended up working out wonderfully. While the second spool, purchased about two month after the first, had a more matte look to it, but it looked good once melted and deposited. My concerns about print imperfections during the swap ended up being for naught.

A very slow print job. This took ~34 hours.

I’m fairly certain I both designed and printed these more robustly (and slowly) than is needed, but as a beginner I’d rather err on the side of overbuilt (and spending a bit more on plastic) than have something which breaks and interrupts a ride.

I’ve made this design available under the CC BY-SA-NC 4.0 license and posted it here at Printables.

Included are .f3d, .step, .stl, and Bambu Studio .3mf files. The .3mf is as I printed it, including the print profile and imported .step files. (The .stl from Fusion, even exported at the High setting, end up lower resolution than I prefer, but was included for completeness.)

So how do they it feel to ride? Well, to be honest, they did what I thought they would and added some flex and give. But I’m not completely sure I like it. Just before spring I went back to my previous self-designed riser feet. Next winter I’ll give these another go, though.

A big, big thanks to Jake for providing a bunch of help and suggestions. He has a ton of experience designing parts professionally and printing them for both prototype work and production and he shared a bunch of tips, tricks, and information that got me pointed in the right direction for this and many other designs.

If you are looking to buy some tennis ball feet or other Michigan-made accessories for your trainer, give Jake your business over at Cycle3dCo.

(As I was finishing up my design and waiting on a test print, I came across Kickr Core 2 Rocker Feet for tennisballs by punkti over at MakerWorld. A quick measure showed they have basically the same vertical as my feet, are physically narrower, but thicker. These likely would have sufficed and use roughly the same amount of filament, but I was nearly ready to do a final print when I found these, wanted to give my own design a try, didn’t really care for the appearance. These do look like a nice option, though.)

cycling making things

Iterating…

July 16, 2026

Six iterations, from initial to final, of slip-fit stove knob lockouts.

Even for a few-hour project, I find it interesting to look back at the various iterations of developing something. In this case it’s six different versions of a slip-fit shim that latches on to our stove’s knob shafts, preventing them from being pressed in turning the gas on or igniting. Kristen wanted these to help avoid accidental knob turns (from people, dogs, etc) and being stuck inside by extremely poor quality air from wildfires, it was today’s after-work pass-time.

I’m happy with where the idea ended up. My original idea was for something that pushed in from the bottom and clipped in place, but because of the D shaped knob shaft I ended up with something that’s slipped in horizontally, and as it falls/is turned to a natural position with the tab down, it sticks in place. Along the way I screwed up the thickness, tried making things smaller, then smaller still, then had to nudge the thickness, and then finally cut out a bunch of the inside to use less plastic.

The first five were prototyped in PLA, and for the final items I printed them in PETG. Although I think the plastic might have been a bit damp as it was stringy… Still, it was easy enough to clean up and fine for this.

The models can be found here on Printables, if you’re interested. Or I’ve got a simple demonstration video of it here.

around the house making things

Worn Mountain Bike Tires: Hooked Side Knobs

July 5, 2026

Worn side knobs on a Maxxis Rekon tire from my Mach 4 SL.

This past Tuesday, at the CRAMBA River Bends With Friends ride, I had a both-tires-slide-out fall on a tight, flat, sandy-over-hard trail that resulted in a pretty-decent scrape to my left calf. Why did it happen? Two reasons. One — the primary reason — is because I exceed my ability to handle the bike. Two, the bike’s ability to corner was reduced because I let the front tire get too worn out. So what was fine before, this time… wasn’t. And I didn’t adapt.

While one thinks of a tire wearing out, it’s typically the knobs getting smoothed out, especially along the center. On knobby mountain bike tires, it’s the side knobs which bite into dirt to maintain traction when cornering. And those same cornering forces eat away at the inner edge of the side knobs.

Many high quality tires, such as the Maxxis Rekon 29×2.4 3C/EXO/TR shown above, have harder rubber in the center than on the sides, meaning the center continues to look (and work) fine (in a straight line), even as the sides have failed. (Note the visible siping on the center knobs, still-vertical trailing edges, and even some of the flashing left over from the molding process.)

Eventually the side knobs become undercut, almost like hooked flaps as seen above, and no longer offer much support. Without close inspection, feeling with fingers and such, they often still look sharp or at least sufficient. This loss of support means radically-reduced cornering ability on soft surfaces, and the now-super-flexible knobs make for unpredictability on hard surfaces; almost like riding on loose bits of rubber.

I should have replaced this tire long ago, but I kept putting it off; “I’ll do it after this next ride” because it wasn’t too bad. Until it was.

Whenever I replace a tire I’m starkly reminded of how much better new tires with sharp, crisp knobs feel. It’s a bit annoying that this wear can be hard to see and more needs to be felt for (with fingers), and it also just sort-of sneaks up on you. A long ride with a bunch of paved sections or a trip somewhere a bit rocky can push tires over the edge, even while the other knobs might still look fine.

cycling

Site Cleanup + Logo

July 3, 2026

`og-image.png` (Default OpenGraph preview image for the site.)

In the biggest clean-up to this site since back 2020 when I took the photo gallery down and static’d the wiki, I’ve cobbled together a new theme and logo, made a bunch of under-the-hood changes, and went waaaay down the rabbit hole automated content cleanup (fixing broken links, missing images, etc). One of the biggest irritations I had with the previous theme, Period, is that it didn’t have great support for code blocks and never really felt like… mine. It worked well enough, so I just stuck with it.

For a logo I just quickly drew something up with a paintbrush in Photoshop than ran it through a vectorizing / site icon generation process, and… I got that. I’m not sure if I’m completely happy with it, but it’ll do for now.

Perhaps long overdue, I moved the server from Apache to Caddy. While Apache is the venerable web server, and been used here for quite some time, I’ve always been a bit fond of using atypical servers (such as lighttpd). I’ve been using Caddy on trailmaps.app for a couple years and been extremely happy with its automatic support for ACME, so with not much else to do yesterday afternoon I flipped things over.

I also put some time in getting OpenGraph (see also opengraph.xyz) working, which helps when links are shared and things are indexed. This just more polish, but makes things nicer, especially as so many things do rich link previews these days.

There is still got some cleanup of the Caddy config to do — removing some old rewrites and MIME types from years-old experiments — but for the first-pass a direct translation of one config to the other made the change-over easy. There’s probably some further tweaking of PHP needed for performance, but that needs some time for the server to settle. I imagine there’ll also be some content cleanup, like fixing filenames for the wiki archive and maybe some old blog post format things, but those’ll (hopefully) get handled as I stumble across them.

This makes me happy, because I feel like I’m knocking a bunch of technical debt items off a long-put-away mental list; things that I deemed too hard-for-then and just accepted. Not bad for a few afternoons/evenings during a heat wave where I’m a bit nonplussed about being outside yet am itching to do something.

nuxx.net

trailmaps.app + Map Generator

June 25, 2026

I’ve been using it for a while now, so I guess it’s a good time to announce the revamp / relaunch / whatever of trailmaps.app. This is a personal project website which started one frosty January morning as I sat in an Ishpeming rental waiting for temps to rise before heading out on a fatbike ride and is now a hub for hosting maps I’ve generated of various trail systems.

The site started out as a hand-written HTML landing page, hand-made Leaflet maps, and directory indexes of my trail map PDFs where I learned a bunch about showing OpenStreetMap (OSM) data via the web, generating tiles, etc (for example, see Making an Online RAMBA Trails Map from 2021). Now it’s now hosting feature-rich web-based maps that help people find their way around mountain bike trails.

The root of the idea was cooked up on a long drive; I wanted something akin to the subway-map-style’d official RAMBA print map (parallel lines over a single trail to illustrate the trail’s membership in multiple routes), but web based. And maybe usable on a phone. And after the early learning then quite a bit of work this spring… Here it is.

Instead of just doing a single map (one-map-at-a-time coding / tile generation / etc) as I had in the past, I now have a full-on map generator that takes data from OSM and other online/open/free sources, combines it all, and generates static content that’s easy to host and cachable so it works if a device loses cell service. It’s basically as close to an app as one can get while still staying web-based.

By being hand-curated (that is, not just auto-generated off of all OSM data) these maps also fill a long-standing gap with other online maps (eg: Trailforks, MTB Project, Strava, RideWithGPS) in that they don’t style (color) the routes the way official park maps and signage do, making what a rider sees on their phone challenging to align with what they see on a signpost next to a trail.

For example, compare these maps of the Shelden Trails at Stony Creek Metropark to the PDF of the official park map which is at the trailhead, and whose color-matched signs are along all loops.

Trailforks: Only difficulty colored.
MTB Project: Only difficulty colored.
Strava: Only dashed lines or a heatmap, unless someone’s created a route.
RideWithGPS: Just dashed green lines, unless someone’s created a route.

Then look at the trailmaps.app map of the Shelden Trails at Stony Creek Metropark, for example, the Beach trail.

There’s a bunch more features that this brought about, which I won’t dive into as much depth, but which I’m still quite proud / happy with. The end results are what I want in maps, and it’s nicely reusable:

Reusable map generation engine; I write a YAML description of the map (title, OSM references, info that can’t be found in OSM) and it makes the map. If the engine or data gets updated, re-run the map and/or website generation tools.
PWA (Progressive Web Apps), so they are installable app-ish, but without the app store overhead.
OSM data is not fetched live — it’s a snapshot taken map-generation time — meaning errant edits don’t break the map.
Zero user/usage tracking, including having all assets loaded from trailmaps.app. (I’m trying to support less and less online tracking while still providing a good tool.)
Ability to generate maps custom from non-OSM data, such as race or group ride routes.
Thorough, proper (read: non-shady) SEO such as OpenGraph previews and metadata, making link embedding, sharing, and site discovery by search engines work well.
Hostable for cheap since the only server requirements are TLS and RANGE requests. A $5/mo Nanode from Akamai (formerly Linode) easily does it all.
Stand-alone maps (each map is a self-contained site) makes it possible for them to be hosted elsewhere, such as if one was made for a trail club/org, etc.

And yes, I heavily used AI-assisted development for this. It was quite educational as since I knew the inputs and outputs, use the maps myself, and was able to do quite a bit of QA, the result is great. At my day job in IT there is (as typical) a huge emphasis in using AI tooling to assist us with our work. This served as a nights-and-weekends project that was quite educational and will benefit me in day-job stuff while achieving a personal goal of making something I wanted and useful for others. It also illustrated the interesting balance between what AI-generation is good at (code, bug finding) and what it’s not (wording, stylistic choices that aren’t simple clones, avoiding feature bloat).

I’m subsequently making the map generator itself available under the MIT license so others can use it. I do have an extensive toolchain for generating the website (takes a definition file and generates the maps, creates preview images, updates the index, rsync’s it to the server) but that part is staying closed / non-released because it’s very my-setup-specific.

cycling making things mapping

Vibe Coded Fixes

June 13, 2026

Working in Claude Code to fix broken image links in this blog.

For all the potential problems that come with vibe coded stuff, generating/composing one-off fix-it scripts can be damned handy. For example, this blog got a big tune-up over the past day: almost 2000 embedded images have been unbroken.

For a lot of years I maintained a personal online photo gallery using Gallery2, but as it hadn’t been maintained since 2012, used a lot of server space, and had a very not-modern feel to it, I shut it down in mid-2020 and made a static archive that I just hosted at home. The biggest problem with doing so was that this blog had a lot of images hotlinked into there, so all those posts broke.

Fixing this manually was a pain, and while I kept a copy of the database+images around, somehow using that to fix things was a Big Task that I never started on.

Enter the modern world of AI-assisted coding and over the past few days of vacation, between riding bikes and walks and such, I prompted Claude to develop a solution. What it generated was a series of scripts that identified all posts containing images hotlinked to the old gallery location, found the related images, uploaded them into the Media Library, then edited each post to make it work.

That’s 1994 blog posts whose images have been restored; things like my Low-Cost Fat Bike Stand post are now working again.

This is where I find a ton of benefit to AI tools such as this: putting together the middle (the code) to fix up problems. If the inputs and desired outputs are known, and one can sanity check the system as it evolves, a lot can get done. And quickly. Tools like this have also been hugely beneficial at work, saving me absurd amounts of time with analyzing log files (eg: network captures, Process Monitor output) where I no longer have to timeline things myself.

I’m past the point where I’m surprised, but I’m still really impressed. This has been a long-standing back-of-my-mind problem/quirk with my site that I’d just sort of accepted… But here we are, it’s fixed. Yay!

computers nuxx.net

Capital One Credit Balance Refund Business Logic Flaw

April 18, 2026

This morning when checking my Capital One credit card statement I saw a surprise item, a CREDIT BALANCE REFUND for $56.58. After some digging I found this is what shows up when a card user received a check requesting a refund of a credit balance (balance owed to the card holder by Capital One).

Online support was of no help, so after speaking to a customer support (and holding) for over half an hour, I got an answer.

Whenever I go to pay to this credit card, I’m able to pay up to 10% over the current balance, which I tend to do because there’s almost always pending transactions, and it all evens out (returning to a normal balace) within a day or two.

Capital One says, per their support document Getting overpayment refunds (emphasis mine):

If you have a negative balance, you have options to bring the balance back to $0. Keep in mind that in some situations this happens automatically.

Spend the negative balance: If you have a negative balance, use your credit card like you usually do, and Capital One will apply the account credit toward your purchases.

Get an automatic refund: Capital One will issue a refund if you don’t make any other purchases after two payment cycles. If you don’t use the money for up to four billing cycles, we’ll automatically send a refund check to the address on file. Note, your overpayment must be more than $1.

Request a refund: Capital One will mail your refund within 7 business days of your in-person or written request. Delivery usually occurs within 15 business days but may take longer depending on the mail carrier.

That is, if you don’t use the card for two payment cycles, and don’t spend the whole credit balance within four payment cycles, they’ll send a refund check.

Here’s where the flaw was triggered. Apparently I made an overpayment for the past two months right as the payment cycle was ending. Despite there being plenty of transactions during each billing cycle, and the balance wavering between a credit (from the overpayment) and debit (from normal use), because there was a credit at the end of a number of two consecutive billing cycles, it triggered a check issuance. This was confirmed by the customer support person I spoke with.

This appears to be a flaw in their business logic, with the result being a bit of money floating out there in the postal system for no real reason. It certainly cost Capital One money to issue the check, so it’s a waste of time (for me) and money (for them). As I write this I have $641.30 in pending transactions on this account, with ~$588 of that from the days before the Credit Balance Refund was issued, so sending a refund check is nothing but extra work.

I was hoping to send this to Capital One to share this finding with them, but they don’t have a public email address and I don’t feel like spending any more time on the phone, so I just wrote it up here. Maybe / hopefully the customer support person I was talking with (and their manager, with whom they had to consult on the issue) log it as an issue.

finances

local-heatmap-tile-server v1

April 7, 2026

During a long drive to (and from) Florida, and a lot of thinking about maps, I realized something that I really wanted, and something that I could use AI-assisted development to experiment with: generating a heatmap from all my personal, archived activity files. Specifically, generating XYZ tiles, making them available via TMS (so they can be used as an imagery layer in JOSM), and also displaying them on a slippy map.

For years I’ve been using the Strava heatmap as a layer in JOSM for OpenStreetMap (OSM) editing and this works great, but I’m finding myself disconnecting from online social networks, including Strava, more and more. And while the Strava Global heatmap does work as a data layer with a free account, I began thinking about other options to use it, and other cloud providers, less and less. And yes, there’s similar offerings from RideWithGPS and whatnot, but I really wanted to generate my own since it’d give me a lot more flexibility.

So, for my next project working with Claude, I decided to try building a personal heatmap generation tool. And it worked.

Cool heatmap of my ride and hike data, used as a layer in JOSM. (Ishpeming/Negaunee area.)

Using AI tools to develop software is nothing new, but I’ve never really been one to jump right on brand-new things, instead waiting for them to bake and show their utility before I dig in and use/learn them. I also find it very difficult to learn any tool or system unless I have a way to apply it. But when I do, getting my head around it comes pretty quickly.

In making this I’ve learned / found / finally-realized that with a known set of inputs, a desired output, an ability to identify/recognize bugs, and a task that’s known-possible, AI-assisted development saves can save incredible amount of time. Within reason it makes it possible for me to be more of a product manager than developer. Since I’m not really a developer (my career is in systems management and troubleshooting), that work for me is slow… and I’m not good at it.

Using Claude on the desktop to write the code, VS Code to read and make a few manual edits, and Docker Desktop so I could keep an eye on things, after about a week of free-time iterating, this is what I came up with, and I’m quite pleased:

c0nsumer/local-heatmap-tile-server

This is a single Docker container that uses a bunch of Python to import GPS data files (.FIT, .GPX, .TCX), imports, deduplicates, and renders a complete set of XYZ tiles. It then makes them available via HTTP (for display in a slippy map or something like JOSM) or exports them to a PMTiles file for simple hosting. And it has a built-in slippy map viewer/data manager and a couple bundled viewers for completely static hosting (example).

Dashboard for importing new files, stats, and exporting the heatmap for static use.

The Python webserver, uvicorn, isn’t the fastest nor great at caching, so the XYZ tiles are fronted with nginx to very quickly serve them from disk, only passing the request back to uvicorn and the Python stack for rendering if the tile isn’t present. Once the tiles are rendered they are cached very quickly served up solely by nginx, to the point where panning and zooming freely is seamless. (And yes, you can pre-render all tiles for optimal performance.)

It’s been tested on ~4000 track single-GPX files (exported from rubiTrack), ~4000 .FIT files directly from Garmin devices, and a bunch of different types of single GPX files. And… it seems to work!

The file inputs (FIT, TCX, GPX) aren’t special and parsers have existed for a long time. Nothing about heatmaps is new. Tile rendering isn’t new. Tile serving isn’t new. Nor are web-based heatmaps from fitness tracker data. But it needed to be glued together to get something that works this way, and this type of development made it possible. And I learned something new about AI-assisted software development along the way. It’s sure an interesting new world with these tools.

And yes, beyond thinking about the features I had to do a lot of nudging along the way.

Some major bugs that were encountered were getting cross-tile heatmap brightness correct, missing cross-tile data, tiles not rendering properly when called via different ways, moving to a faster web server so panning the map felt smooth, and a whole lot of tweaking of brightness and line thickness and blur and such at different zoom levels so it’d feel nice to use, noticing and dealing with malformed XML in GPXs…

But this was nudging via prompts and having a bit of an idea what it was doing, not coding. Which is what’s so weird and new to me. It’s like directing a team of pretty-decent junior devs.

And the end result is something I’ve wanted for a while. And now it exists. (And no, none of this post was written by any AI tool.)

computers making things mapping

Updated MTB Trail Mapping Workflow: Thanks, Claude!

March 12, 2026

River Bends Park OSM data, with DEM hillshade layer, ready for Adobe Illustrator

After a bunch of years I’ve updated my MTB trail mapping workflow with a much-improved tool for getting OpenStreetMap (OSM) data into Adobe Illustrator. I’ve been experimenting with AI development tools, and I’ve been looking for projects, and this one fit the bill.

My old workflow used osm2ai.pl, a rather crude script (which I found years ago) that’d take an OSM file and turn it into vectors that I’d then group and style in Illustrator. While the tool claimed to filter objects into layers, I never got this working right, so there was a lot of manual work before I could begin styling the map. Each map took a couple of hours solely selecting, joining, grouping, and deleting stuff.

With some time on my hands during a mountain biking trip I began prompting Claude Code, via Visual Studio Code, for something similar: a tool which would take OSM data and make it usable in Illustrator. After a bit of back and forth I ended up with this: c0nsumer/osm_to_ai.

I very intentionally had Claude write everything on this, from the script to the readme, and it seems to have been a success. A bit of experience was gained, and I now have a tool that’ll read in OSM data (either exported from tools or queried live) and produce an Illustrator-compatible SVG that has trails grouped by OSM tag, colored, etc. All ready to finish up in Illustrator. It even has an extra layer of USGS 3DEP hillshade data, something I’ve wanted for years after seeing it on the Noquemanon Trails Network maps (but didn’t know how to do in Illustrator).

This was both a good exercise in using AI tools to assist in simple software development and helped streamline my mapping process. While I have a general discomfort with AI-developed code ending up with potentially uncertain output, this output is immediately validated visually, so it’s fine.

Unplanned, but on quick check this seems to have the side-effect of being compatible with Affinity Designer. While this wasn’t (yet) an intention, I’ve been looking for a good way to move away from Illustrator due to software cost (this is volunteer stuff, after all) but the old osm2ai.pl needed replacing before I could do that. This will make that possible.

So what next? Maybe I’ll see if I can make the PDF maps geospatial. This has long been a goal of mine, as it’d allow my maps to be opened in something like Avenza Maps and they’d show one’s actual location on the trail. But for now, I’ll start here.

As an overview, here’s the --help output to show what it can do:

(venv) PS C:\Users\svigneau\Desktop\OSMtoAI> python .\osm_to_ai.py --help
usage: osm_to_ai.py [-h] (--file PATH | --bbox BBOX | --overpass FILE) --output PATH [--width PX] [--dem PATH] [--fetch-dem] [--dem-resolution METERS] [--sun-azimuth DEGREES]
                    [--sun-altitude DEGREES] [--save-osm PATH]

Convert OSM data to an Adobe Illustrator-compatible layered SVG.

options:
  -h, --help            show this help message and exit
  --file PATH           .osm file to read
  --bbox BBOX           Bounding box: min_lon,min_lat,max_lon,max_lat
  --overpass FILE       File containing an Overpass QL query
  --output PATH         Output .svg file
  --width PX            SVG width in pixels (height is auto-calculated, default: 800)
  --dem PATH            GeoTIFF DEM file to generate a hillshade layer (any CRS)
  --fetch-dem           Download a USGS 3DEP DEM automatically and use it for hillshade. Saves a sidecar .tif next to --output for reuse.
  --dem-resolution METERS
                        Target DEM pixel size in metres for --fetch-dem (default: 3). Use 1 for lidar-quality where available, 3 for 1/9 arc-second, 10 for 1/3 arc-second.
  --sun-azimuth DEGREES
                        Sun azimuth in degrees clockwise from north (default: 315 = NW)
  --sun-altitude DEGREES
                        Sun altitude above horizon in degrees (default: 45)
  --save-osm PATH       Save the downloaded OSM XML to a file for later reuse with --file

Examples:
  python osm_to_ai.py --file mypark.osm --output mypark.svg
  python osm_to_ai.py --bbox "-71.12,42.36,-71.10,42.38" --output mypark.svg
  python osm_to_ai.py --overpass query.overpassql --output mypark.svg
  python osm_to_ai.py --file mypark.osm --dem elevation.tif --output mypark.svg
  python osm_to_ai.py --file mypark.osm --fetch-dem --output mypark.svg
  python osm_to_ai.py --file mypark.osm --fetch-dem --sun-azimuth 270 --sun-altitude 35 --output mypark.svg

(venv) PS C:\Users\svigneau\Desktop\OSMtoAI>

making things mapping