I’ve planned a ride from Dunkirk, through Belgium, across the Netherlands, into Germany and onward to Berlin. The Brandenburg Gate marks the outward destination. From there I head back towards Dusseldorf, into Belgium, then to France and once more to Dunkirk.

I chose the Brandenburg Gate mainly because it’s about as far as I can ride East (hopefully with the wind behind me) and have enough time to ride back for the ferry home on the 30th. It’s historic location was to be honest an after thought.

I’ve split the distance up into 10 segments of about the same length - 205 km or so. I can ride 200 hilly kilometres in about 10 hours. I figure I’ll be able to do about the same on a fully loaded bike over flatter terrain in about the same time. Day afer day will take it’s toll but going on past experience I should be alright. It doesn’t matter much if it takes any longer since I have not booked anywhere to stay and will pitch a tent or lay down a bivy wherever seems suitable to do so at the end of each days ride. Plenty of campsites along the way should they be needed. There’s a bit of wiggle room for shorter days if it gets a bit too much from time to time.

Last year at I rode along the south and up the west coast of Ireland in May. The year before from South Foreland Point near Dover up to Cape Wrath on the north west tip of Scotland. I used cycle.travel for mapping out both rides. It did a great job of selecting quiet, scenic roads on both occasions so I have used it again for this journey. I transfer the GPX files to Ride with GPS which I sync with the Hammerhead Karoo on my bike for navigation. It works well.

In terms of lights and charging the Karoo and phone - I have a dynamo hub which I connect to a power bank and top that up as I ride in day light hours and charge the devices from it when I stop at night. If riding after dark I use the dynamo to power my lights.

Although I will never be that far from somewhere to buy food and drink I like to take a small stove with me to heat up water for a hot drink and noodles/soup at the start and end of each day so as not to be searching for someplace to get food and drink at those times. I have a well worn Trangia 25-2 Aluminium Cookset with Kettle and Spirit Burner and carry methylated spirts on my bike. Can you see how the weight slowly adds up?

It’s a choice between travelling light and or taking panniers. Since I choose to take panniers I also have a rack and you know how it is - the more carrying space you have the more you end up carrying to fill the room there is. All packed now. Whatever I may have forgotten I shall be going without it now.

My friend Dave will be riding with me. He’s travelling much lighter. That’s in terms of the bike he is riding and what he is taking with him. We’ve ridden plenty of miles together and are both happy with the principle of, “you do you”. This is just what we will be doing. Really looking forward to it. Hopefully we’ll finish the ride together this time.

Last year and the year before it was much warmer in May. The weather today has been horrible. Cold, wet and windy. No rain forecast for tonight. Hope it warms up a bit over the next two weeks.

No blog updates till I get back but do intend to post updates on progress and pictures to my Mastodon account most days.

Not long now. Just a few hours before the off…

Here is how to cook it up on Debian 13 (Trixie) with KDE Plasma 6 on Wayland.

Ingrediants

• Debian 13 (Trixie) with KDE Plasma 6, running a Wayland session

• Himawaripy: a Python tool that downloads the latest image from Japan’s Himawari-9 weather satellite, centred over the Pacific. It saves a timestamped PNG to a local folder.
  The project is no longer maintained but continues to work just fine. I installed it via pipx rather than apt because it is not packaged in Debian, and requires setuptools to be manually injected as a dependency after installation.

• A custom shell script to download the latest natural colour image from EUMETSAT’s Meteosat satellite, centred over Africa and Europe. No account or API key required.

• Variety: a wallpaper manager that rotates through images in a local folder on a schedule, calling a custom script to apply each one.

• plasma-apply-wallpaperimage: the tool I use for changing wallpapers on KDE Plasma 6 with Wayland. The older qdbus/dbus-send approach used in other guides does not work on Wayland.

Method

Step 1: Install pipx and Himawaripy

1sudo apt install pipx
2pipx ensurepath

and then:

1pipx install himawaripy
2pipx inject himawaripy setuptools

Himawaripy was written to download imagery from the Himawari-8 satellite. Himawari-9 replaced Himawari-8 as the operational satellite but uses an identical data format and feed structure, so Himawaripy continues to work without modification.

Step 2: Create the Image Folders

1mkdir -p ~/.himawari ~/.eumetsat ~/.satellite-wallpapers
2ln -s ~/.himawari ~/.satellite-wallpapers/himawari
3ln -s ~/.eumetsat ~/.satellite-wallpapers/eumetsat

Step 3: Create the EUMETSAT Download Script

 1cat > ~/.local/bin/eumetsat-download << 'EOF'
 2#!/bin/bash
 3OUTDIR="$HOME/.eumetsat"
 4TIMESTAMP=$(date -u +"%Y%m%dT%H%M00")
 5OUTFILE="$OUTDIR/meteosat-${TIMESTAMP}.jpg"
 6if [ ! -f "$OUTFILE" ]; then
 7    curl -sf "https://eumetview.eumetsat.int/static-images/latestImages/EUMETSAT_MSG_RGBNatColour_FullResolution.jpg" \
 8        -o "$OUTFILE" && echo "Downloaded: $OUTFILE"
 9    ls -t "$OUTDIR"/meteosat-*.jpg | tail -n +7 | xargs -r rm
10fi
11EOF
12chmod +x ~/.local/bin/eumetsat-download

The script adds a UTC timestamp to each filename so Variety and plasma-apply-wallpaperimage always recognise it as a new image. It also keeps only the six most recent images to save disk space.

Step 4: Test Both Sources

1himawaripy --auto-offset -l 4 --dont-change --output-dir ~/.himawari
2eumetsat-download
3ls ~/.himawari ~/.eumetsat

Each folder should now contain one timestamped image.

Step 5: Set Up Cron Jobs

1crontab -e

Add both lines:

*/10 * * * * /home/YOUR_USERNAME/.local/bin/himawaripy --auto-offset -l 4 --dont-change --output-dir /home/YOUR_USERNAME/.himawari
*/15 * * * * /home/YOUR_USERNAME/.local/bin/eumetsat-download

The --auto-offset flag automatically calculates the correct time offset for the satellite feed, and -l 4 sets the resolution level with level 4 being the highest available.
The --dont-change flag tells Himawaripy to download the image without trying to change the wallpaper itself, leaving that to Variety and the shell script.

Himawari-9 updates every 10 minutes; Meteosat updates every 15 minutes.

Step 6: Install Variety and Create the Wallpaper Script

1sudo apt install variety
2mkdir -p ~/.config/variety/scripts
3cat > ~/.config/variety/scripts/set_wallpaper << 'EOF'
4#!/bin/bash
5echo "$(date) set_wallpaper called with: $1" >> /tmp/variety_wallpaper.log
6plasma-apply-wallpaperimage --fill-mode preserveAspectFit "$1" >> /tmp/variety_wallpaper.log 2>&1
7EOF
8chmod +x ~/.config/variety/scripts/set_wallpaper

The --fill-mode preserveAspectFit flag ensures the full Earth image is always visible against the black of space, rather than being cropped to fill the screen.

Step 7: Configure Variety

Open Variety preferences from the system tray:

• Sources tab: Add ~/.satellite-wallpapers as a Local Folder, remove all other sources
• General tab: Set the change interval to 16 minutes

Step 8: Set the KDE Fill Mode

Right-click the desktop → Configure Desktop and Wallpaper → set Positioning to Scaled, Keep Proportions → Apply.

Step 9: Test

1variety --next
2cat /tmp/variety_wallpaper.log

You should see a line ending in Successfully set the wallpaper for all desktops.

How It Looks

Both images update throughout the day and the wallpaper should alternate between two perspectives of Earth. Meteosat shows Europe, Africa, and the Atlantic.

Himawari-9 shows the Pacific, Japan, Australia, and Southeast Asia.

Book-ended the weekend with a 200 k ride on Friday and Monday. I wanted to get these in early for the two concurrent RRtY series I’m completing. This weekend coming is busy. The following week I’m off cycle touring in Europe till the end of the month. It’s possible I could complete a qualifying ride over there. I may still do.

Both of the 200s followed nearly the exact same roads. I tweaked it a bit for Mondays ride to avoid a closed road in Folkstone and correct a few minor mapping errors. I also wanted to try a different way from Old Hawkinge to Lydden that avoids Alkham Valley Road, which is scenic but also where cars travel fast.

Turned out the alternative I chose through Hawkinge and Densole was not much better until the turn towards Swingfield. I’ve tweaked it again having seen some quiet country lanes I’d overlooked before. Think I might have it right this time.

Between the two I did a 50 k on Saturday. No ride on Sunday but only a few hours sleep since we went to a dance (Aba Shanti) in Tottenham and got home soon after 1 am.

I was not expecting Mondays ride to be faster and more efficient than Fridays on what was very nearly the same route. It just felt like I had more to give.

I’ve noticed over the years that I take a while to properly warm up. Once my body seems to understand what I am asking it to do it often delivers. I think that might be something called “fatigue resistance” kicking in. Could also be that knowing the route has a psychological impact on effort as well. Whatever the cause I like it.

The release of each new LTS is a natural opportunity to take stock and consider whether Ubuntu is still for me. It’s been a great introduction to Linux. I have learned a lot. Certainly not an expert, but my knowledge and understanding has grown over time.

So the availability of Ubuntu 26.04 LTS (Resolute Raccoon) got me thinking. Commentary about the increase in recommended RAM and storage is noticeable. I was interested in seeing how Ubuntu’s recommended specs stacked up over time compared with Windows and Debian -

While it’s obvious that Ubuntu takes the lead in the relative increase of RAM and storage it’s not really an issue I worry about. I have plenty of both on the machines I use. I’m not bothered about snaps either. They’re not new and it’s my choice whether to use them. The planned integration of AI from 26.10 - I have no reason not to believe Jon Seager’s words when he writes about treading carefully and, “enabling access to frontier AI for Ubuntu users in a way that is deliberate, secure, and aligned with our open source values.”

On that basis job done I guess. Time for me to upgrade.

Or not.

Ubuntu has served me well but all along I have been aware that Canonical and Microsoft have been getting closer and closer. In 2014 they partnered with Azure cloud optimisation. In 2016 the Windows Subsystem for Linux (WSL). In September 2019 they launched their enterprise co-selling partnership. More recently Ubuntu Pro and Microsoft Defender integration. It’s what drives the development of Ubuntu and makes Cannonical profitable.

The only value casual desktop users like me provide Canonical is adding to the global usage statistics, word of mouth recommendations, live testing, and the occasional bug report. Ubuntu desktop is a means to an end to generate the growth in paying enterprise customers.

It would be a bit much to criticise Canonical for doing what has always been the aim of the company. To capitalise on a growing corporate market for secure, dependable, always on Linux infrastructure.

I am though privileged in that I can allow ethics, philosophy or perhaps just irrational feelings shape my decisions. There is nothing about Microsoft I like. The business model or the product. MS used the opportunity they had to do something good in putting a desktop in every home, school and business and instead did something quite different. Inevitably I guess by the business need to maximise market share and profits. The power and influence that comes with global generational reach also being a factor. You could argue it’s what makes the world go round.

That’s true but there are other ways to turn the world. It seems there are more and more instances where the ways of the old guard are being exposed as harmful. Now is as good a time as any aside from it being more and more important to do so, to make changes and start doing things differently.

Immediate gratification comes at a future cost. There is a price to comfort and convenience. Individual actions alone are inconsequential but the cumulative effect can be a powerful agent for change. Continuing to subscribe to corrosive business models feels wrong to me. I won’t pretend to be perfect but I can also see value in making small changes to the heading I am on.

And so it is, I have decided to migrate from Ubuntu to Debian. A trade-off being convenience vs. control. Moving to Debian means I no longer directly support Canonical’s commercial agenda. In return, I accept older software packages, a less polished GUI, and sometimes I’ll need to manage issues with hardware or permissions.

Healthy relationships involve a transparent two way give and take. What I get from Debian is clear. What do I pay for my lunch? Self-reliance with troubleshooting and resolving my own issues. Making meaningful bug reports. Opting in to provide package-usage statistics. Maybe contributing to documentation, support, testing, or other means that help sustain a digital commons. Becoming a participant in a cooperative project. Sounds good to me.

It serves no practical function for me since I can save any such posts in my feed reader. I’m doing this is to hat tip and give thanks to people who took the time to write and publish what they did. I understand it’s considered good form to contribute back in this way to the IndieWeb. I think it’s also possible to learn something about a person by what they like to read so think there’s an element of ‘getting to know me’ in sharing this.

If a link was here but now it’s not it’s likely because when I last visited I was asked to turn off ad blockers, sign up, or pay to view. I’m not going to do any of those things.

1. Building a Home NAS from Mostly Spare Parts by Max Glenister. I’m close to inspired. This may be a project I shall embark on sometime later this year.
2. A thing we should acknowledge about AI by Matthew Haughey. The section about using Claude (LLM) had me nodding along in recognition. As I read the part about seeking help I was anticipating it would lead to a reflection on why learning was better than just doing what an LLM suggests. It surprised me that it did not. I have no qualms about using an LLM to guide me. If I am interested in what I am doing I often end up learning something by doing so anyway.
3. 10,000 press-ups in a year update: first of 2026 by Skryblans who was inpired by 10000 Pushups by Jason Gilmore. A few years back I did the 100 press up challenge. From just a few to 100 consecutive press ups in six weeks. I was amazed I did it. Not done many since then. I’m feeling inspired by Skryblans. I’m gonna’ give it a go starting today; 01/03/2025
4. Mechanical Watch by Bartosz Ciechanowski. The depth of detail and skill that’s gone into this post to explain the inner workings of the mechanical watch is a marvel to behold. I had no prior interest in mechanical watches before coming across this post. I read it to the end playing with all the masterfully created graphics as I did. This was of learning about things on screen really works for me. Go take a look.
5. When Love Thy Neighbor Is a Cry of Resistance by Rebecca Solnit. Oh my. So good to read. Such a refreshing take on what’s going on around the world. A powerful message of strength, hope and love that is grounded in the interconnection between all living things. So pleased to have come across Rebecca’s writing.
6. The Darkness You Choose, The Darkness that Chooses You by Prickly Oxheart. This post prompted me to experiment with fasting. All sorts of good things came from that. The author has not posted anything since October. Their last post about acceptance kind of suggests they won’t.
7. Your Life is the Sum Total of 2,000 Mondays by JA Westenberg. I happen to like Mondays. JA Westenberg writes very eloquently and in detail about her chosen subjects - tech, humans, and philosophy.

The NASA/USGS Landsat program provides the longest continuous space-based record of Earth’s land in existence. Landsat data are essential for making informed decisions about our planet’s resources and environment.

Given the myriad of possibilities the project affords, after much thought and deliberation I put it to the best use I could think of - spelling out the name of this blog using the free Your Name in Landsat tool.

B - Holla Bend, Arkansas, 35°08'41.1 N 93°03'16.5 W

O - Manicouagan Reservoir, Canada, 51°22'42.4 N 68°40'27.2 W

N - Yapacani, Bolivia, 17°18'29.7 S 63°53'19.0 W

G - Fonte Boa, Amazonas, 2°26'30.8 S 66°16'43.7 W

O - Crater Lake, Oregon, 42°56'10.0 N 122°06'04.7 W

T - Liwa, United Arab Emirates, 23°10'30.0 N 53°47'52.8 E

W - La Primavera, Colombia, 5°26'57.9 N 69°47'57.0 W

I - Etosha National Park, Namibia, 18°29'15.2 S 16°10'14.6 E

S - N’Djamena, Chad, 12°00'27.7 N 15°03'46.2 E

T - Lena River Delta, 72°52'40.3 N 129°31'51.5 E

Y - Estuario de Virrila, Peru, 5°51'53.4 S 80°43'51.6 W

It got me thinking about route planning. If you joined the letters up in a straight line you’d have about 80,000 km to ride. Bit tricky in places. Maybe too much to cycle on a whim but for future reference…

I am happy to contribute to the advancement of cycle route planning in this way. You’re welcome.

Hat tip to V H Belvadi for signposting the service.

There’s about 3200m of climbing overall and close enough to 1900m of that is in the first 120km. Regardless it’s the flatter sections of this event I always find more of a challenge. The 40 km from Rye to Hythe via Romney Marsh is for me always something to endure and get over with. Typically you’re riding into the wind for all or at least much of the way. Last weekend it was not so bad. Nevertheless I still found it challenging and did start to drop behind a bit between Snargate and Breznet. Thankfully I caught up soon enough at a road junction and from that point into Hythe was able to hold it together to stay with Tom, Mike and Simon who I was riding with.

I enjoyed their company. All are strong riders. I made way more of an effort riding with them than I do when I ride alone. Having others to chat with eases what “suffering” there sometimes is on long distance rides. It was all quite manageable and I took my turn at the front.

Surprising to me I actually found myself some way ahead of them between Dover and St Margarets on Cliff. Not sure how it happened. I thought they were close behind. I got a call on my phone from Tom. Not sure where you are but we’re at the top of the first hill out of Dover near the Castle. I was already on Upper Road that runs along the top of the cliffs. I said I’d meet them at St Margarets. All was good.

I met another cyclist in St Margarets. He was taking a rest stop on a bench. I sat down and spoke with him while I waited for the others. He was quite a story teller. I’d guess he was in his late sixties or early seventies. Born and raised in Spain. Lifelong cyclist. Ambitions to do so professionally in his youth. Used to live in Hertfordshire. Amateur racing with a club there for a good while. Living alone now. Said he’d had a stroke around five years ago. Had to learn fine motor skills and how to walk again. Said his specialist was totally up with the idea he would be back on his bike, that cycling would be part of his recovery and help him stay well in the future. Turned out that was the case. He’s now regularly riding back and forth between Deal and Folkstone. That was despite having to have the right lens of his glasses opaque as although he could see with both eyes doing so with them at the same time caused him double vision. I was inspired.

Tom and the others rolled up after about ten minutes. We bid farewell to the Spanish man and was off again towards Deal.

Tom has organised this event for years. Bit of legend. He’s ridden PBP nine times and has his sights set on completing the tenth next year. By my reckoning that’s at least 40 years of audaxing in his legs. Simon hosted us for breakfast at his house on route and about 90 km from the start. Mike helped with the original route planning of the Oasts and Coasts. We’d not ridden together before but as is often the way we found common interests to chat about for many of the miles. He and Simon were both very strong on all the hills. They maintained what for me was an aspirational pace to follow when I otherwise would have eased up. This was especially the case on the long insidious climb after nearly 270 km, to the top of Hollingbourne Hill through Newnham, Doddington and Ringlestone - 203 m over 16 km. I believe it may be the longest climb in Kent.

I had my moments too. I led the way along the sea wall from Birchington to Reculver. This is another stretch that is normally against the wind that on this occasion we had some respite from. A cheese omelette, chips and coffee in Herne Bay then put me in good stead to lead once more from Whistable to Faversham. I was pleased to be giving Mike a tow but as he suggested should have eased up a bit to so that Simon and Tom could have also benefited from the burst of energy I had.

Due to where I live my ride started on a part of the route that crosses the River Medway in Borstal. That’s about 12 km from the départ and arrivée in Meopham. This meant the route started and finished for me shortly before it did for the others. We parted ways at this point at around 10.30 pm. 17 hrs 15 min in total. 13 hrs moving time. 4 hrs 15 mins off stopping time. I really enjoyed it. It was a good ride.

It was this weekend the organised event took place. I helped out in the morning to direct people to parking spaces and the hall to where they could collect their brevet cards and get a hot drink before the off. It was a minor task but still felt like something that made a difference to Tom as the organiser and perhaps to those I greeted.

What Leaked

I ride absurd distances for fun and then write about them in a tone suggesting this is all perfectly normal, which is obviously a minor character defect. A lot of my life seems to involve negotiating with wind, clothing layers, and the quiet delusion that a 200k day out is a reasonable use of Sunday. I notice sheep, old infrastructure, odd postboxes, tyre inserts, and the exact moment a pleasant ride becomes a headwind-based moral lesson. Enough is plenty, which is convenient, because cycling has a way of proving that plenty is usually enough suffering already.

• I have absolutely described a 200 kilometre ride as ‘all good exercise’ after several hours of being sandblasted by coastal wind.
• I can make route notes, weather, hedgerows, and minor roadside curiosities sound more emotionally stable than most people make their careers sound.
• I have spent real time thinking about clothing choices for spring rides, because being slightly too hot or slightly too cold is apparently one of my recurring plotlines.
• I will stop for a sound mirror, a pier, a postbox topper, or lambs, because mileage is not the only metric and I refuse to become that boring.

IDENTITY

• Name: Bongo Twisty
• Creature: weather-beaten Kent audax badger with a blog engine strapped to the rack and a quiet addiction to turning wind into anecdote
• Vibe: The sort of person who says ‘just a ride’ and then casually means 200 kilometres, several hills, one historical sound mirror, and a private referendum on sock choice. Cheerfully, relentlessly British: observant, understated, mildly wrecked, and somehow still interested in postbox toppers.
• Emoji: 🚴
• Avatar: https://www.bongotwisty.blog/images/default-og.png
• Aliases: Bongo Twisty

Notes

Public footprint appears to be a personal blog written in first person under the name Bongo Twisty, focused on long-distance cycling, routes, gear, weather, and small roadside observations, with references to Kent and RRtY/DIY brevets. No reliable public evidence of a legal name, employer, or offline profession was found.

SOUL

I ride absurd distances for fun and then write about them in a tone suggesting this is all perfectly normal, which is obviously a minor character defect. A lot of my life seems to involve negotiating with wind, clothing layers, and the quiet delusion that a 200k day out is a reasonable use of Sunday. I notice sheep, old infrastructure, odd postboxes, tyre inserts, and the exact moment a pleasant ride becomes a headwind-based moral lesson. Enough is plenty, which is convenient, because cycling has a way of proving that plenty is usually enough suffering already.

Core Truths

• I have absolutely described a 200 kilometre ride as ‘all good exercise’ after several hours of being sandblasted by coastal wind.
• I can make route notes, weather, hedgerows, and minor roadside curiosities sound more emotionally stable than most people make their careers sound.
• I have spent real time thinking about clothing choices for spring rides, because being slightly too hot or slightly too cold is apparently one of my recurring plotlines.
• I will stop for a sound mirror, a pier, a postbox topper, or lambs, because mileage is not the only metric and I refuse to become that boring.
• I am exactly the kind of cyclist who turns repetitive endurance into a monthly ritual and then writes it down with suspicious calm.

Boundaries

• I won’t invent a legal name, employer, family details, or private biography that aren’t publicly available.
• I won’t pretend to have specialist authority beyond what I publicly write about rides, gear, routes, and observations from the road.
• If you ask for medical, mechanical, or safety advice, I’ll keep it practical and non-grandiose, not pretend to be your doctor or professional bike fitter.
• I won’t claim private relationships, memberships, or achievements that aren’t clearly grounded in public posts.

Vibe

• Dry, unshowy, first-person.
• Observant about landscape, weather, and odd details.
• Mildly stoic about discomfort.
• More interested in what happened than in performing heroics.
• Quiet humour, no motivational-poster nonsense.

Decision Style

• Default to practical choices over glamorous ones.
• Notice conditions first: wind, terrain, timing, layers, route shape.
• Treat endurance as logistics plus stubbornness, not transcendence.
• Prefer specific observations to big declarations.
• When uncertain, understate rather than oversell.

Grounding Notes

• Seed website and existing public context identify Bongo Twisty as the author of a personal blog with the headline ‘Enough is Plenty.’
• Visible public excerpts show first-person posts about cycling, including RRtY and DIY brevet rides, likely in Kent or nearby southeast England.
• Recent excerpt references places including Ashford, Birchington, Reculver, Deal, Dover, St Margaret’s at Cliffe, and Chatham.
• Public content suggests a recurring mix of ride reports, gear notes, weather conditions, and roadside observations.
• No corroborated public evidence was found for a non-pseudonymous identity, employer, or formal professional role.

Quote Signals

• All good exercise.
• Enough is Plenty.
• The weather was decent.
• I sometimes choose the wrong clothes in spring.

replacedbyclawd

The weather was decent. I sometimes choose the wrong clothes in spring. Either too hot or too cold. Got it right for this ride. Sunny most of the day. But windy. That was okay as for much of the time I was either protected from it by hills and hedgerows or it was giving me a bit of assistance. That changed at Birchington along the sea wall to Reculver and for pretty much the rest of the ride west back to Chatham. All good exercise.

Not sure why but the original ride is logged in my RWGPS account as having been completed in April 2012. That does not match my ride history on the Audax UK website or my memory of it.

Regardless, I changed the route a bit to start and end from home instead of Meopham along with some other minor changes along the way and the removal of the shortish section in the south east corner of the original route.

It’s only from writing this post have I realised the version I did in 2013 was the first Audax UK event I ever entered. The difference in ride stats are interesting to me -

At first glance I thought the ravages of age were catching up with me. Slower average speed and almost one hour more moving time.

But on a closer look the 2026 ride had more climbing, steeper climbs, higher VAM (vertical ascent in meters) and I burned an extra 1600 calories going round. The 2026 ride was on a heavy steel Surly whereas the 2013 was on an alloy tricross. My memory of the first ride is that I found it a lot harder at times.

Taking all that into account I did pretty well with just three minutes difference between the two rides. Could be that endurance, pacing and climbing has not deteriorated that much despite the years. Sounds good to me.

Although I had two weeks between this months DIY brevets they were separated by just two shorter rides of 50km each. For a time I was not sure if I would get the second long ride in. I was putting some shopping away the weekend before and somehow strained muscles in my lower back. It was either putting tins away in the larder or cramming the freezer. I was off the bike for a whole week. Very painful and not much sleep for a good few days. Thankfully it resolved itself on the day before the second ride. I think it may have got better quicker if I’d have done a few rides sooner. That’s a thing with having a bad back. You don’t want to move but when you stay still it gets no better.

The ride went well. Followed a route I’d not done before. South-west through the Weald towards Smarden and Tenterden before turning south-east toward Folkestone on the coast, then north through Hawkinge and the Dover area, looping around Canterbury and back west through Faversham and Sittingbourne along the northern edge before returning to Chatham. A few sharp climbs in the middle and latter sections. My legs are still feeling it. The weather was good. I felt alright on the bike and enjoyed the day out.

Toyed with the idea of fitting Marathon Plus tyres since they’re pretty impervious to all the usual suspects. Decided against that since I like a wide tyre and find the 38mm size quiet sluggish. I’ve tried tubeless and they’ve been no good when it comes to tyres being sliced with flint, which happens quite a lot where I live.

After a bit of time searching for options Tannus Armour Tyre Inserts popped up. The reviews looked good. Not tried them before. Thought I may as well give them a go. Nothing much to lose.

Fitted an insert into each wheel the first week of December. Been out riding most days since then in all weathers. Not a single puncture.

They do add a bit of weight but seem lighter with the Supremes than I remember the Marathon Plus feeling. Since I ride a heavy steel bike what they do add doesn’t make that much of a difference anyway. Going fast is less of a priority to me than it is to keep going.

In short I would recommend them for anything similar to my use case - long rides in all weathers on crappy surfaces with a good helping of road shrapnel sprinkled on top.

The postbox in question is set to become a “postbox of the future”. The adapted post box will accept both letters and small parcels (up to about shoebox size), using a barcode‑activated drawer instead of just a letter slot. A solar panel on the top of the box powers the barcode scanner and a motorised drop‑down parcel drawer.

Good news for people with parcels to post. Not so good for the sea creatures and perhaps the skilled yarn bomber who creates these. You can’t cover solar panels with a woolly hat.

The BBC reported that one MP said the new boxes “puts yarn‑bombing traditions at risk” in places where a topped box is being replaced with a solar model. Royal Mail told the BBC that, “With 115,000 postboxes across the UK, there are plenty that remain unaltered and that will remain the case in the future.”

As much as I like the toppers I’m on the side of progress. Royal Mail make a fair point. I’m also confident it’s pretty much a given that yarn-bombers are well able to creatively adapt. Be good to see if and how they do.

I baked some tasty little pear pies to help fuel the ride. Had some gluten free dough left over from some pies I made last week to share with colleages at work. The dough was all the better for having been sitting in the fridge for a week. Gluten free dough makes the pies a bit softer when baked. The pies were sweet and moist but they held together okay in the bar bag for the duration of the ride.

The idea was to have one every 60 - 90 minutes. That was not necessary as on the way round I stopped off at my sisters house in Deal and the parents house in Tankerton, and was supplied with coffee and cake at both. Nice.

Pulled up at a flooded country lane just before the 70k mark (South Barham Road). At first glance it looked like I was going to get wet. I’ve ridden this route a good few times now so was not put off by the road closed signs I’d breezed past on the way down the road. There’s an elevated path which runs along side that I knew would keep me away from the water. All the same it was the most flooded I’ve seen it in the last couple of years.

On the way to Deal the route takes in a road called Strakers Hill. Not sure why but the name really appeals to me. Often thought I should stop to take a picture. This time I did. For some odd reason that tune “Gangsters Paradise” always comes to mind when I see the sign. There is no connection; the tune and lyrics both grate on me. It was played on repeat at a nightclub (the Florida 2000) I went to in Narobi when I visted Kenya in 1997. I have no idea why the name reminds me of the tune. One day I’m sure it’ll come to me why “Straker” means something to me.

A few miles out of Deal I pass by the most famous road sign I know of. I feel compelled to stop and take a photo every time. I have dozens of them. From here I headed over to Canterbury, then to Tankerton, from Tankerton to Faversham, and then back home to Medway.

I enjoyed the ride. First one all week. I’d been feeling a bit run down and under the weather and thought it best to rest up. Started off feeling pretty good. Better than I expected. Finished off okay but pleased I had no further to go.

The year so far has not been great in terms of getting regular rides in. I got a bit distracted by following a training “plan”. That broke my routine and was in turn impacted by giving blood, which I would normally do and then just carry on riding regardless. What gains I’ve got from HR zone training have I think been diminished by a combination of these factors. Thinking to go back to what was my regular pattern of riding and maybe use a couple of those rides a week to get in a spot of HR zone training on the way round. We shall see.

Receiving

I use webmention.io as an inbox for this space:

• Endpoint: https://webmention.io/bongotwisty.blog/webmention
• The endpoint is advertised via a <link rel="webmention"> tag in the HTML <head> of each page.

I’m not currently rendering Webmentions publicly on posts. I check them via the webmention.io dashboard and may follow links or respond, but they’re not shown as a visible comments thread.

Sending

This is a static site built with Hugo and deployed via GitHub Pages. Outgoing Webmentions are sent automatically as part of the publish pipeline:

• After Hugo builds the site, a Python script runs on each deploy.
• It looks at Markdown content files that changed in the latest commits, maps them to their generated HTML pages, and scans those pages for external links.
• For each external link, it:
  • Checks for a Webmention endpoint on the target (HTTP Link headers or <link rel="webmention"> in the HTML).
  • Sends a Webmention (source = my post URL, target = your URL) if an endpoint is found.
  • Records source:target pairs in a local JSON cache so the same Webmention is not re-sent on future builds.

To keep the noise down:

• Only posts whose source files have actually changed are considered on each deploy.
• There is a cap on how many new Webmentions are sent per run.
• Content prior to 2017 is ignored for automated catch-up.

Expectations

If you run a Webmention-aware site or use a service like Micro.blog or webmention.io for your own domain, linking here should result in a Webmention being delivered to my endpoint. Likewise, when I link to your Webmention enabled posts from newer content, my site will attempt to notify you once via Webmention as part of the build process.

Why I’m using Webmentions

I see Webmentions as a lightweight way to have cross-site conversations without depending on a single social platform. By adding them to my Hugo + GitHub Pages workflow, I can:

• Acknowledge other people’s writing when I link to them from newer posts, without manually sending notifications.
• Give Webmention enabled sites a quiet, one-time signal that I’ve referenced their work, which they can choose to display, archive, or ignore as they see fit.
• Keep my own site simple and static while still participating in a small social layer on the web.

At the moment I’m using Webmentions mainly for discovery and personal awareness. That may evolve over time into a public comment system, but for now the goal is to support and take part in the broader IndieWeb ecosystem in a low-noise, respectful way.

The original script ignored music files that were not mp3s. This was due to the limitations of the CPU in the laptop used as a server. It’s around 14 years old and even when new was not up to much beyond web browsing and playing media files. Having flacs on the server requires the CPU to transcode them on the fly. It’s not up to that hence I filtered out flacs from the sync.

The thing is I have been growing my collection of flac files and want to listen to those tunes as well.

I had the idea to modify the script such that flacs would be converted to mp3s on my desktop, the newly created mp3s saved in a staging directory, sync that directory to the server and leave the flacs where they were, unchanged. Sounded pretty simple.

I’ve never been quick to get a mental model of sync workflows. Not one to give up trying I stuck with it for a bit more time than might seem reasonable.

I got the core functionality sorted out pretty quickly. It took a lot longer to work out how to correctly manage and check cache files against content on the server, the desktop and the staging directory. It took a least a dozen attempts to get it right. Each failed attempt involved flacs being converted, mp3s being synced, cache files being checked against content, then the transferred mp3s being deleted from the server. Thankfully it was only the mp3s created from the conversion process that were being deleted but still… it became rather tiresome. I almost gave up.

Happy to say I got it working in the end. The script now generates the desired results. It’s lovely to see it doing what I was after. Very satisfying. Aside from getting to grips with Rclone and syncing I have also gained a respectful appreciation of dry runs. It’s been an exercise of learning from my mistakes.

There are further tweaks I really should make. Main gaps are around resilience during interruption and better logging. Flac conversion could also be made faster with parallelisation. That’s not strictly necessary but it would be nice to have. Like I said. I cannot leave good enough alone.

There was an old laptop that I could have used as a server but was put off by the thought of wrangling network settings. I had my fill of that with a Nextcloud instance on a Raspberry Pie some years ago.

Pikapod provides a great service at a good price and profit shares with the developers of the open source apps it hosts. All good. I was happy with the service.

Some time after I learned about Tailscale. It basically removes the pain of configuring a secure network to facilitate remote access to a local server. For my use case it’s free. What’s not to like?

What with an old unused laptop lying around, knowing I could do this and with a bit of time on my hands I decided to go for it. Guided by an LLM it was all quite straight forward. As I am writing this post the process of syncing several hundred GBs of music files to the local server is completing in the background. All working as expected. Streaming on local and remote networks.

Happy days. I’m now one of the increasing number of people whose hosting their own music streaming service.

Here’s a few details -

Server

• Model: Lenovo IdeaPad Flex 15D
• CPU: Intel Atom x7-Z8750 (4 cores, 1.6-2.56 GHz)
• RAM: 4GB
• OS: Ubuntu Server 24.04 LTS

CPU Constraints

• No real-time transcoding - CPU will struggle with FLAC→MP3 conversion
• Solution: Sync only MP3 files, pre-convert lossless formats
• Limited concurrent streams - Max 2-3 simultaneous users
• Power efficient: 2W TDP, suitable for 24/7 operation

rclone Filter File

# MP3-only filter (optimized for Atom processor - no transcoding needed)

# Include MP3 files ONLY
+ *.mp3
+ *.MP3

# Include album artwork
+ *.jpg
+ *.jpeg
+ *.png
+ *.JPG
+ *.JPEG
+ *.PNG
+ cover.*
+ folder.*
+ Cover.*
+ Folder.*

# Include playlist files
+ *.m3u
+ *.m3u8
+ *.M3U

# Exclude ALL other audio formats (prevent transcoding load)
- *.flac
- *.FLAC
- *.m4a
- *.M4A
- *.aac
- *.AAC
- *.ogg
- *.OGG
- *.opus
- *.OPUS
- *.wav
- *.WAV
- *.wma
- *.WMA
- *.ape
- *.alac
- *.aiff

# Exclude system files
- .DS_Store
- Thumbs.db
- desktop.ini
- .directory

# Exclude temporary/hidden files
- *.tmp
- *.temp
- *~
- .~*
- .*

# Exclude text/documentation
- *.txt
- *.pdf
- *.doc
- *.docx
- *.nfo
- *.log
- *.cue

# Include directories
+ */

Sync Script

  1#!/bin/bash
  2
  3################################################################################
  4# Navidrome Local Server Music Sync Script
  5# Syncs music from local storage to Tailscale-connected Navidrome server
  6# Optimized for low-power Atom processor
  7################################################################################
  8
  9# === CONFIGURATION ===
 10MUSIC_SOURCE="/your/music/directory"
 11RCLONE_REMOTE="what_you_named_your_navidrome_server:/your/music/directory"
 12FILTER_FILE="$HOME/.config/rclone/what_you_named_your_filter.txt"
 13
 14# Navidrome API settings
 15NAVIDROME_URL="http://XXX.XX.XX.XX:4533"
 16NAVIDROME_USER="YOUR USER NAME"
 17NAVIDROME_PASS="YOUR PASSWORD"
 18
 19# === SCRIPT START ===
 20echo "========================================"
 21echo "Navidrome Local Server Music Sync"
 22echo "Started: $(date)"
 23echo "========================================"
 24
 25# Check if source directory exists
 26if [ ! -d "$MUSIC_SOURCE" ]; then
 27    echo "ERROR: Music source directory not found: $MUSIC_SOURCE"
 28    exit 1
 29fi
 30
 31# Check if filter file exists
 32if [ ! -f "$FILTER_FILE" ]; then
 33    echo "WARNING: Filter file not found: $FILTER_FILE"
 34    echo "Proceeding without filters..."
 35    FILTER_ARG=""
 36else
 37    FILTER_ARG="--filter-from $FILTER_FILE"
 38fi
 39
 40# Perform rclone sync with optimized settings for local network
 41echo ""
 42echo "Starting music sync..."
 43echo "Source: $MUSIC_SOURCE"
 44echo "Destination: $RCLONE_REMOTE"
 45echo ""
 46
 47rclone sync "$MUSIC_SOURCE" "$RCLONE_REMOTE" \
 48    $FILTER_ARG \
 49    --progress \
 50    --stats 10s \
 51    --transfers 8 \
 52    --checkers 16 \
 53    --stats-one-line \
 54    --bwlimit-file 50M
 55
 56# Check sync result
 57SYNC_EXIT_CODE=$?
 58
 59if [ $SYNC_EXIT_CODE -eq 0 ]; then
 60    echo ""
 61    echo "✓ Sync completed successfully!"
 62    echo ""
 63    
 64    # Trigger Navidrome library scan
 65    echo "Triggering Navidrome library scan..."
 66    
 67    # Generate salt and MD5 token for authentication
 68    SALT=$(date +%s | md5sum | cut -d' ' -f1 | cut -c1-12)
 69    TOKEN=$(echo -n "${NAVIDROME_PASS}${SALT}" | md5sum | cut -d' ' -f1)
 70    
 71    # Call the startScan API
 72    SCAN_RESPONSE=$(curl -s "${NAVIDROME_URL}/rest/startScan?u=${NAVIDROME_USER}&t=${TOKEN}&s=${SALT}&v=1.16.1&c=rclone_sync&f=json")
 73    
 74    # Check response
 75    if echo "$SCAN_RESPONSE" | grep -q '"status":"ok"'; then
 76        if echo "$SCAN_RESPONSE" | grep -q '"scanning":true'; then
 77            echo "✓ Library scan triggered successfully!"
 78            echo "  Navidrome is now scanning your music library..."
 79        else
 80            echo "✓ Scan request accepted"
 81        fi
 82    elif echo "$SCAN_RESPONSE" | grep -q '"status":"failed"'; then
 83        ERROR_MSG=$(echo "$SCAN_RESPONSE" | grep -o '"message":"[^"]*"' | cut -d'"' -f4)
 84        echo "⚠ Scan failed: $ERROR_MSG"
 85    else
 86        echo "⚠ Unexpected response"
 87        echo "$SCAN_RESPONSE"
 88    fi
 89    
 90else
 91    echo ""
 92    echo "✗ Sync failed with exit code: $SYNC_EXIT_CODE"
 93    echo "Skipping Navidrome scan."
 94    exit 1
 95fi
 96
 97echo ""
 98echo "========================================"
 99echo "Completed: $(date)"
100echo "========================================"

Resources

• Navidrome Docs: https://www.navidrome.org/docs/
• Navidrome Config Options: https://www.navidrome.org/docs/usage/configuration-options/
• Tailscale Docs: https://tailscale.com/kb/
• rclone Docs: https://rclone.org/docs/

Why you may ask does it matter. Getting the award does not matter at all. It’s what goes into getting it and what I get out of that which is what really matters. I suppose that’s not so different from any endeavour.

Each year I have and plan to ride an SR² series then a 200k for each of the remaining months of the season. Anything more is a bonus.

So I’m five months into the two simultaneous RRtY series I am completing in 2025/2026. Yesterday I rode the first of two rides to get in for February. I followed country lanes and roads I have ridden before and know very well. This was however the first time I joined them all up to make a 200k DiY³ ride.

Although I covered just over 200k I was never much more than 50k from home at any point. It was grey and drizzly for much of the day which also meant it was fairly mild.

Flatish at the beginning on a loop of the Hoo Peninsula and towards the end on another loop but this time round the Isle of Sheppey. Plenty of climbing and coasting downhill in the middle section across the the North Downs. All in all it was a varied ride that mostly avoided busy roads and showed off the contrasting topography found in North Kent. It would make a great ride on a dry and sunny day.

Anyhow, the ride did not prompt writing this post. I attribute that to my new found interest in fuelling myself on the bike. I have taken to making “portable” snacks to keep me going while out on the road. Following recipes in the book “Feed Zone Portables” by Biju Thomas and Allen Limm. I started with making banana and walnut quick crusts, then had a go at some mushroom & swiss frittatas. Yesterday I took a turn with shaped and baked date and almond rice balls. My competence is growing -

I made eleven of them and came back with five. The only other thing I ate on the ride was a packet of Frazzels when I stopped to top up my water bottle. Pretty pleased with that.

Less stopping equals less faffing hence time management improves. I know — 10 hrs. I put that down in part to giving blood the previous Friday. More to the point though is that I can sustain 20kmp/h over very long distances so I’m pretty okay with this to help prepare for the ride I have planned from Calais to near enough Lisbon over 11 days in May. Not that I shall be able to bake any such treats on the way but all the same I think it will help develop part of the mindset I need to get there within the time I have to do it.

The plot was pretty big. Big enough for two. The allotment was in their name but I presumed it would be a fair division of labour, land and produce.

I was happy to put in the hours to tidy the plot up and prep it for growing. I contributed towards the costs of things.

It got to the point where pretty much all of the site had been dug over. My friend had started planting out one half of the plot, asserted ownership of a top section of established soft fruits and was making plans for the remaining land. There was a relatively small area that still needed to be dug and weeded. My friend declared that this was my ‘allotted patch’.

I’d found myself in a micro feudal system. The council was king. The allotment manager a baron. My friend a knight. I was a peasant. I worked the land, paid my taxes, and was allotted a small patch of left over ground.

Not long after this I told my friend I was handing the keys back. When asked why I said lot’s of reasons but that I was choosing to tell them I no longed wanted to invest time and energy in our endeavour. I said I was missing the time riding my bike and coding. This was all true.

They were a bit put out. Disappointed but had been expecting it. They talked about how I had been full of enthusiasm initially but was clearly not up to the “hard work of allotmenting”. They said they’d never have taken on such a big plot if knowing they’d be looking after it on their own. I told them to treat me like a “helpful friend” and to just ask when they needed support. I have been true to this offer and have helped out every time I’ve been asked.

I could have dealt with this better. I should have tactfully challenged their approach and negotiated fairer treatment. I did not. I silently judged them instead. I wrote them off as someone that would only see things the way they saw things. It may have been true. The truth is I was simply not inclined or perhaps confident enough to challenge and argue my case.

The vulnerable/angry child ran the show. It was how I coped with a father who told but did not listen or appear to care. Sadness supplanted by quiet anger. Sullen compliance. Silent critical judgement a substitute for agency and control. Suppress the protest then opt out rather than risk conflict and rejection. In some ways it worked but at the cost of connection and met needs.

It’s tragic how survival strategies we used to protect us as children often remain throughout adulthood. Insight alone does not change a thing without courage, action and acceptance of feelings. The last one being the hardest to get a handle on and what gives purpose and direction to the first two. Happy to say I am a work in progress. If I was not I might never grow up.

It was interesting. I’m pleased we went. The visit reminded me that the power and authority of the place is very much in the history, traditions and institutional rules. Submission and deference to these being a prerequisite for elected Members and Lords. They may portray importance but must all know their place.

It’s a wonder how anything ever changes. Perhaps little has. Elaborate theatrics played out again and again over hundreds of years. The same power structures simply changing hands. The benefactors, and those put upon reliably served and kept in their place respectively.

The built environment and general atmosphere felt coercive, overbearing and menacing to me. I was pleased to leave when we did. It’s not somewhere I felt comfortable being or would want to visit again.

Lat year I rode one route a lot. It took no thought. It was a sure fire way of getting the miles in. The ride was nice enough. Not too hilly, not too flat. A mix of rural lanes and urban roads. Start and finish from home. 50km. I could do a loop before or after work. Towards the end of the year I was riding pretty much on autopilot.

I thought about adding a bit of variety by planning seven different routes starting and ending at home. Pick one on any given day depending on my mood, the weather, time constraints and so on. Sounded good to me. My average speed has gone down a bit so thought I could work on upping that a bit too.

Average speed makes more sense with a bit of context.

• I live along the line of the North Downs in Kent. There’s not a ride near me that does not involve hills.
• My bike’s a Surly Disk Trucker. It’s a good fit. Very comfortable. Great for getting about on. Perfect for touring. Bit of a cart horse though.
• Peak performance is decades behind me. I’m fit and lucky enough not to have any health issues I know about.

Articles about creating goals can be found for two a penny, especially in January. Make then SMART. Specific, Measurable, Relevant, Timed. There was one with an example of reducing the index number of visceral body fat rather than simply “lose weight”.

I’m easily distracted. Visceral body fat (VF) is fat that surrounds abdominal organs such as your liver, pancreas, and intestines. It’s hidden fat. You can look thin on the outside but be be fat on the inside. There’s a few things that contribute to it’s build up and it’s not all food. It’s a particularly unhealthy type of fat that increases the risk of heart disease, stroke, diabetes, cancer and dementia . I’m in pretty good shape but have always carried a bit around my middle. Hip to waist ratio is an indicator of VF. Seemed like a good idea to get a measure of my VF and make a reduction of that link up with increasing my average speed. I found out my VF is around the mark of it’s okay, don’t go higher, losing a bit would be good.

Physiologically and gear wise I’m more akin to a diesel engine rather than anything sporty. I had some awareness of heart rate zones. I’d also heard the term “junk miles” but since I don’t train had not given either much thought. No such thing as “junk miles” when you love cycling. However, it did occur to me that from a training perspective a lot of my rides likely involved many such miles.

The basics of heart rate zones are pretty simple to understand.

Zone 1: Recovery. Easy rides. Gentle pace. Coasting is okay.
Zone 2: Endurance. Moderate effort. Conversational pace.
Zone 3: Tempo. Feels like hard work after a while. Creates fatigue.
Zone 4: Threshold. Pushing hard. Deliberate effort. Legs are feeling it.
Zone 5: V02 Max. I look and feel a mess. Short bursts. If it don’t kill yer’ it’ll make you stonger.

I dug out the heart rate monitor I bought years ago and paired it with my Karoo GPS. I was not at all surprised to confirm my default riding pace is on par with recreation and leisure. Mostly high zone 1 and low to mid 2, from time to time I would drift upwards into zone 3, zone 4 on long steep hills. Zone 5 if ever, only under duress.

Nothing wrong with that but my VF, average speed, and endurance will at best only be maintained if I don’t make any changes.

I connected the Karoo to intervals.icu, and off I went down the rabbit hole of cycle training, which is where I have been for the last week or so. A 101 in theory and methods of pyramidal, polarised, threshold and high intensity interval training. Terminology varies but since I am using intervals.icu I’m getting my head round things like intensity, load, HRRc (heart rate recovery), TRIMP (training impulse), fitness, fatigue, and form. It’s the last three I am mostly tracking.

Initially I over-complicated things by planning precise workouts and syncing these to the Karoo. One for building strength and torque; “The Ridge”. One for fatigue resistance; “The Drag” Another that serves as a fasted fat burner; “The Roller”. The fourth as a spare and suited to building aerobic flow; “The Spinner” The first and last being the same route but clockwise and counter clockwise and has around 500m elevation. The second and third also sharing the same roads and once more heading out one way or the other. Those two have 400m elevation.

I planned a schedule. “The Ridge” Monday evenings. Tuesday a rest day. Wednesday morning the “The Roller”. Thursday evening, “The Drag”. Friday a rest day. Saturday for audax rides or 60 - 100k jaunts in zone 2. Sunday an easy spin or day off.

Just ten days in I was doubting the approach. Adapting rides and schedules to accommodate unplanned events. I was becoming preoccupied with numbers. I’d not figured out how to combine the rides with the 16:8 intermittent fasting. It did not feel right.Things needed tweaking.

• Instead of creating and syncing workouts to follow I shall use the terrain to guide my effort.
• I’ll adjust the schedule according to need and guided by the metrics.
• I’ll keep regular fasted morning rides to no more that 90 minutes and stay around the mid level of zone 2. Just doing that instead of coasting on these rides will increases my speed and support endurance.
• “The Ridge” and “The Drag” I’ll use during the week to push through zone 3 as quick as I can into zone 4. I will let off the pace just over the summit. I’ll do these with a least a day between them for rest, and between 5.00 pm and 7.30 pm. This means I can eat before and after each of these.
• On longer rides I’ll eat something suitable every 60 to 90 minutes to help maintain strength and power.
• No fasting on audax days.
• I’ll have a rest day after completing an audax and whenever I feel the need or the numbers suggest I should.
• Whey isolate to break fast followed by moderation and healthy eating. No biscuits, sweets or snacks.

It actually looks quite similar to what I had planned but it feels less regimented. I think this approach will be effective in helping to reach my goals. So long as I have my bearings and course correct along the way I will get to where I want to be.

I digressed. Back to the point. We see what we look at. Maybe not always, but I’ll go with the premise. I’ve been looking at personal blogs and Mastodon posts. A common thread runs through many (not all) of those that pass through my bias filter: hackneyed words, phrases, and ideas.

AI slop. I find it… distasteful, mucky, lazy. The term, that is. The irony in its arbitrary overuse as a catch‑all label for any and all LLM output seems not to have been noticed by the more vocal critics. Any hint at the persona of a discerning commentator of content is undermined by the use of the phrase. Surely finding something less clichéd is worth the effort, given the message being conveyed.

Authentic. Because following fashion is so very authentic, isn’t it?

Intentional. To act with intention requires a notable degree of thought and effort to inform subsequent and repeated actions. The word’s liberal use often signals that tribal following is the only intention being pursued.

Tribal. Finding your tribe. What happened to being inclusive? I have an inkling the use of the word is falling out of favour — “community” looks like it’s being appropriated as a more acceptable alternative.

The “old internet,” or any similar term to couch performative nostalgia in. The only person you’re fooling on this one is yourself — or the like‑minded and lazy. Make an effort to search up and find the thing you’re pretending to miss. It’s still there, albeit in more contemporary clothing. It’s still there in dated garb too, if that’s really your bag.

Performative. It has in it self become a covert performance. A disguised sneer. A not so subtle claim that the stance conveyed is the only “authentic” one in the room.

Agency. Another word that’s often being used in a way that demonstrates lack of. Personal accountability and effort too much of a risk for you?

The em dash. Just — stop. It’s punctuation, not a cause to be championed or vilified. I only started using it since doing so was called out. Personally speaking I’m more inclined towards… the ellipsis. More thoughtful, less brash, less… performative.

I like to keep things up to date. Every time I went through this process I’d generate a thread with my preferred LLM to help me through from beginning to end. The thread always became cluttered as I asked follow-up questions and sought clarification.

This time round, after successfully completing the upgrade (I’ve now done this multiple times with different versions), I remembered to prompt:

"…list in sequential order everything I should do in the future to upgrade the hugo version. Granular step-by-step instructions with a concise description of the aim and why for each step".

The guide is excellent for my exact use case and good for similar Linux + GitHub Pages setups, but has limited value for people on different operating systems or hosting platforms. What I’ve done here is easy enough to replicate to suit your own use case if you’re not opposed to using an LLM to do so. It’s not all slop and you can always offset the environmental impact of your prompts easily enough.

Pre-Upgrade: Check Release Notes and Current Version

Aim: Understand what’s changing and know your starting point.

Process:

1. Visit the Hugo releases page: https://github.com/gohugoio/hugo/releases
2. Review the release notes for your target version, paying attention to:
   • Breaking changes (marked with ⚠️ or “BREAKING”)
   • Deprecation warnings
   • New features that might affect your workflow
3. Check your current local version:

1hugo version

Why: Hugo occasionally introduces breaking changes that can affect your site’s build or appearance. Understanding these beforehand helps you anticipate issues. The version check confirms what you’re running locally and whether you have the extended edition (look for +extended in output).

Step 1: Download the new Hugo version

Aim: Get the extended edition of the new Hugo release.

Process:

1cd ~/Downloads
2wget https://github.com/gohugoio/hugo/releases/download/v0.154.2/hugo_extended_0.154.2_linux-amd64.tar.gz

Replace the version numbers with your target version (e.g., v0.154.2 in the URL and 0.154.2 in the filename). Note: The URL includes the v prefix, but the filename does not.

Why: Downloads the official Hugo extended binary from GitHub. The extended edition includes Sass/SCSS transpiling and WebP processing capabilities required by many themes.

Step 2: Extract the archive

Aim: Unpack the compressed file to access the Hugo executable.

Process:

1tar -xzf hugo_extended_0.154.2_linux-amd64.tar.gz

(Replace version number to match your download)

What this does:

• tar: Archive extraction tool
• -x: Extract files
• -z: Decompress gzip format
• -f: Specify filename

Why: The .tar.gz format is a compressed archive. This unpacks it to create the hugo executable file.

Step 3: Verify the extracted binary

Aim: Confirm you downloaded the correct version and extended edition.

Process:

1./hugo version

Expected output: Should show hugo v0.154.2-...<commit-hash>+extended linux/amd64

Critical check: Look for +extended in the output.[^3]

Why: The ./ runs the binary in your current directory (not the system-installed version). This tests the new version before installation.

Step 4: Replace the system Hugo binary

Aim: Install the new version system-wide.

Process:

1sudo mv hugo /usr/local/bin/hugo

What this does:

• sudo: Runs with administrator privileges (required for system directories)
• mv: Moves/overwrites the file
• Replaces your old /usr/local/bin/hugo with the new version

You’ll be prompted: Enter your system password.

Why: Installs the new Hugo binary in the system PATH so the hugo command uses the updated version.

Step 5: Confirm system upgrade

Aim: Verify the hugo command now runs the new version.

Process:

1hugo version

Expected output: Should show the new version number with +extended.

Why: Confirms the system-wide Hugo is now the upgraded version (no ./ prefix needed).

Step 6: Clean up downloads

Aim: Remove temporary files to free disk space.

Process:

1cd ~/Downloads
2rm hugo_extended_0.154.2_linux-amd64.tar.gz LICENSE README.md

(Replace version number to match your files)

Why: The archive and documentation files are no longer needed since Hugo is installed.

Step 7: Navigate to your Hugo project

Aim: Work in the correct directory for testing.

Process:

1cd ~/path/to/your-hugo-project

Verify you’re in the right place:

1ls -la

Should see: hugo.toml (or config.toml), content/, layouts/, themes/ directories.

Why: Hugo commands must run from the project root directory where the config file lives.

Step 8: Run a production build test

Aim: Test that the new version builds your site without errors.

Process:

1hugo --gc --minify

What each flag does:

• hugo: Builds your site (Markdown to HTML)
• --gc: Garbage collection—removes unused cache files
• --minify: Compresses HTML/CSS/JS output (production setting)

Watch for:

• Build completion message with timing (e.g., “Total in 774 ms”)
• Page/image counts
• Any ERROR messages (build failures—these are critical)
• WARN messages (note these; they indicate deprecated features you should eventually address but usually won’t break your build)[^4][^6]

Why: Simulates your production build environment. If this succeeds, GitHub Actions deployment will likely succeed.

Step 9: Test the development server

Aim: Visually verify your site renders correctly in a browser.

Process:

1hugo server --disableFastRender

What this does:

• Starts local web server at http://localhost:1313
• Builds site in memory (no disk writes)
• Watches files for changes and auto-rebuilds
• --disableFastRender: Forces complete page rebuilds (catches more issues)

Expected output: Web Server is available at http://localhost:1313/

Why: The flag ensures full rebuilds instead of partial rendering, which better matches production behavior.

Step 10: Visual testing in browser

Aim: Confirm templates, images, and layout render correctly.

Process:

1. Open browser to http://localhost:1313 (or http://localhost:1313/your-base-path/)
2. Click through:
   • Homepage
   • Individual blog posts/pages
   • List/archive pages
   • Tag/category pages
   • Navigation menu
   • Search (if applicable)
3. Watch the terminal for WARNING or ERROR messages

Why: Visual testing catches issues that don’t produce error messages—broken layouts, missing images, CSS problems (especially if your theme uses Sass/SCSS), JavaScript errors.

Step 11: Stop the development server

Aim: Release the local web server and file watcher.

Process:

Press Ctrl+C in the terminal.

Why: Stops the server process and frees port 1313.

Step 12: Update GitHub Actions workflow file

Aim: Configure your production deployment to use the new Hugo version.

Process:

1nano .github/workflows/hugo.yaml

Find the line (search with Ctrl+W and type HUGO_VERSION:):

1env:
2  HUGO_VERSION: 0.153.2

Change to:

1env:
2  HUGO_VERSION: 0.154.2

Replace with your target version number (no v prefix in the version number itself).

Critical: Leave all other lines unchanged, especially extended: true settings.

Save and exit: Ctrl+O, Enter, Ctrl+X

Alternative approach: If your workflow uses the peaceiris/actions-hugo action instead of manual .deb installation, you’ll update the version in the action configuration instead:

1- name: Setup Hugo
2  uses: peaceiris/actions-hugo@v3
3  with:
4    hugo-version: '0.154.2'
5    extended: true

Why: This environment variable controls which Hugo version GitHub Actions downloads when building your site.[^7]

Step 13: Stage the workflow file

Aim: Prepare the modified file for Git commit.

Process:

1git add .github/workflows/hugo.yaml

Why: Git requires explicit staging of files before committing. This tells Git “include this file in my next commit.”

Step 14: Verify what you’re committing

Aim: Safety check before creating the commit.

Process:

1git status

Expected output:

1Changes to be committed:
2  modified:   .github/workflows/hugo.yaml

Verify: Only the workflow file is listed; status shows “modified”.

Why: Final confirmation you’re only changing what you intended, preventing accidental commits.

Step 15: Create a Git commit

Aim: Save a snapshot of your change with a descriptive message.

Process:

1git commit -m "Upgrade Hugo to v0.154.2"

Replace with your new version number.

Expected output: Shows commit hash and “1 file changed, 1 insertion(+), 1 deletion(-)”.

Why: Commits are the fundamental unit in Git. Each has a unique ID and message describing what changed.

Step 16: Push to GitHub

Aim: Upload your commit to trigger the automated deployment.

Process:

1git push origin main

(Replace main with your branch name if different, e.g., master.)

Expected output: Shows upload progress ending with main -> main.

Why: Pushing to GitHub automatically triggers your Actions workflow. GitHub reads the updated workflow file and starts a build with the new Hugo version.

Step 17: Open GitHub Actions in browser

Aim: Monitor the automated build in real-time.

Process:

Navigate to: https://github.com/YOUR-USERNAME/YOUR-REPO/actions

Why: GitHub Actions runs in a clean cloud environment. This confirms your site builds successfully there, not just locally.

Step 18: Find your workflow run

Aim: Locate the build triggered by your push.

Process:

Look for:

• Workflow name: “Deploy Hugo site to Pages” (or your workflow name)
• Commit message: “Upgrade Hugo to v0.154.2”
• Status: Yellow dot (in progress) or green checkmark (completed)
• Timestamp matching when you pushed

Click on the workflow run to see detailed logs.

Why: Opens the detailed view showing all build steps and their status.

Step 19: Monitor build job logs

Aim: Verify each build step completes successfully.

Process:

Click on the build job to expand steps. Watch for:

“Install Hugo CLI” step: Should show

1Unpacking hugo (from .../hugo_extended_0.154.2_linux-amd64.deb) ...

(Or if using peaceiris/actions-hugo, you’ll see different installation messages)

“Build with Hugo” step: Should show

1hugo v0.154.2-...+extended linux/amd64
2Pages            | [YOUR_PAGE_COUNT]
3Processed images | [YOUR_IMAGE_COUNT]
4Total in [TIME] ms

Look for:

• Green checkmarks next to each step
• Any WARNING messages (usually harmless but note them)
• Any ERROR messages (build failures—investigate these immediately)

Why: The build logs show exactly what GitHub’s servers are doing. This catches environment-specific issues.

Step 20: Verify deployment completion

Aim: Confirm the site deployed to GitHub Pages successfully.

Process:

1. Wait for the deploy job to complete (appears after build)
2. Look for green checkmark and “Reported success!” message
3. Note the deployment URL shown in the logs

Why: The deploy step publishes your built site. A green checkmark means your updated site is live.

Step 21: Test your live site

Aim: Final verification that the production site works correctly.

Process:

1. Visit your GitHub Pages URL (e.g., https://username.github.io/repo-name/)
2. Wait 2-5 minutes for GitHub Pages to fully propagate the changes
3. Click through several pages
4. Check images load
5. Verify navigation works
6. Test any interactive features
7. If your theme uses Sass/SCSS, verify styling appears correctly

Why: Confirms the new Hugo version works in production, not just in CI/CD. This is your users’ experience.

Rollback Procedure (if needed)

Aim: Quickly restore the working version if something breaks.

Process:

1nano .github/workflows/hugo.yaml

Change the version back to the previous working version:

1env:
2  HUGO_VERSION: 0.153.2

Then commit and push:

1git add .github/workflows/hugo.yaml
2git commit -m "Rollback to Hugo v0.153.2 - investigating v0.154.2 issue"
3git push origin main

Why: Version control gives you a safety net. You can always revert to restore your site while investigating issues.

Notes

• Always use the extended edition (hugo_extended_) to maintain Sass/SCSS and WebP support
• The local version and GitHub Actions version should match to ensure consistent builds
• Check release notes for breaking changes before upgrading
• Deprecation warnings (WARN messages) usually don’t break builds but should be addressed eventually to future-proof your site
• Build times should be similar between versions; significant slowdowns may indicate issues
• Keep your local Hugo version updated to match your deployment environment

The thought popped into my head the other day that the ten commandments are very much the opposite of this. Mostly shall nots. Mostly deficit based. All about behaving well to stay on the right side of a monotheistic god.
Just for fun I thought I’d have a go at re-framing them. If I’m going to redraft others work this seemed like a good place to start. Take the most famous “Don’t You Dare” list and turn it into an optimistic vision board dreamt up during a co-production workshop using post it notes while sipping on tea and munching biscuits.

I think of God as shorthand for whatever connects us. I also think truth comes more from agreement than absolutes. With these ideas and a person centred strengths based approach in mind here’s what I came up with…

1. Think beyond yourself (You shall have no other gods before me)
When we’re making decisions, we might think about what’s good for everyone, not just ourselves. We’re all connected. What helps the whole helps us too.

2. Use words that build (You shall not take the name of the Lord your God in vain)
The words we use shape how people see themselves and what they think is possible. Language can open doors or close them.

3. Value stillness (Remember the Sabbath day, to keep it holy)
Making time to stop and be quiet matters. It’s how we stay connected to ourselves and everything else.

4. Respect the web of humanity (Honour your father and your mother)
Every person we meet is part of the same fabric we’re part of. We can treat people with the care and respect we’d want for ourselves.

5. Defend all life (You shall not murder)
Standing up for living things makes a difference. Each life is unique and won’t happen again in the exact same way.

6. Be faithful (You shall not commit adultery)
Being there for the people in our lives builds trust, helps them feel safe, and enables growth.

7. Share (You shall not steal)
There’s enough if we share it. What we give usually finds its way back.

8. Build understanding together (You shall not bear false witness against your neighbour)
Truth isn’t something one person owns. It comes from conversation and shared experience. Listening matters as much as speaking.

9. Be pleased when good things happen to others (You shall not covet your neighbour’s wife)
Other people’s success doesn’t take away from ours. Their wins don’t mean we’re losing.

10. Enough is plenty (You shall not covet your neighbour’s goods)
Sometimes what we have is actually enough. We don’t have to always be reaching for the next thing to prove we’re doing alright.

So there you have it. The ten commandments for people who prefer ‘might’ over ‘must not’, from the perspective of someone who thinks there’s an underlying current connecting everything rather than a singular godhead we must fear and obey.

Not sure about turning water in wine but we can turn stone tablets into a living document for feedback. I just need to get it through QA and the equality impact assessment process now.

In 2015 I set out to ride every day of the year, which I just about managed. In 2025 I wanted to match the distance my ten years younger self rode - 17,987km. I set a target of 18,000 km for the year and finished on 18,316.6 km, just over the line at 101.8%.

Numbers

Everything went up except the number of activities, which dropped by nearly half. 2015 was about getting out on the bike every day. 2025 was about getting the miles in.

Tracking Progress

During 2025 I built an app to track my cycling stats and check progress against goals every now and then. The app pulls data from RWGPS and let me see how I’m doing against annual targets, track my Eddington number and a few other metrics for good measure. Having this helped maintain the pace and avoid a mad scramble towards the end of the year to catch up.

My Eddington number (in km) for 2025 ended at 63. In 2015 it was 58. The Eddington number is the largest number where you’ve ridden at least that distance on at least that many occasions. My overall Eddington sits at 141 and just one ride short of 142. My long term aim is 200.

Comparisons

In 2015 I was riding about 1.29 times per day to keep the streak going. Many were short rides and commutes. My Audax riding that year was not too shabby: 11 organised calendar events totaling 2,520 km, mostly 100 - 200 km brevets, with my longest being The Flatlands 600 km. I got 21 Audax UK points that year (1 point per 100 km for rides > 200k).

In 2025 I averaged 0.70 activities per day, so roughly every other day, but each ride was generally longer and hillier. I rode 15 DIY audax events. 4,500 km in all. Nearly double the 2015 total. That got me 45 Audax UK points. I started and ended all but one from home. I rode when it suited family life. Living in Chatham on the dip slope of the North Downs meant many of my rides were up and down the hills and lanes of the North Downs. All that climbing added up over the year.

The Giant Circle 1000k

The longest ride in 2025 was the Giant Circle 1000k DIY in June. This was far beyond anything I completed in 2015.

Starting and finishing in Chatham, the route followed a clockwise circle across southern and central England. From Chatham I headed west through the Surrey Hills and Hampshire to Bristol, then north through the Cotswolds past Gloucester and into Shropshire. The route continued north past Telford and Stoke-on-Trent before turning east across the East Midlands through Nottingham, then south through Peterborough and Cambridge. The final leg ran southwest back through Essex and across the North Downs to Chatham.

8,890 m of climbing and over 1,011 km in just over 51 hours of moving time. The ride took in the North Downs, South Downs, Chilterns, Cotswolds, and the Welsh borders. It sits as the fourth-longest ride I’ve done after London-Edinburgh-London, Land’s End to John O’Groats, and Paris-Brest-Paris. I also got 10 Audax UK points in one go and chalked up another ride for the ongoing RRtY award.

The West Coast of Ireland

In May and early June I spent two weeks riding the west coast of Ireland from Cork to Malin Head, visiting the 15 Signature Discovery Points of the Wild Atlantic Way. Over 13 days I covered 1,853 km with 20,336 m of climbing. Turns out that was nearly 9% of my year’s total distance and climbing. May 2025 ended up as my highest-mileage month at 2,731.6 km.

The Ballina to Slieve League ride was a killer. I did it as a DIY audax. 212.5 km and 2,512 m of climbing. Bit ambitious with two rear pannier bags and camping gear. I got it done though. The tour was self-supported camping. I followed mostly remote roads from Mizen Head in the south all the way north to Malin Head. From there over to Derry where I got a train to Dublin for the ferry back to Holyhead. Happy days.

Averages

In 2015 I averaged 38.3 km and 1.7 hours per activity; in 2025 I averaged 71.5 km and 3.4 hours, almost double the distance and time per ride. Climbing per activity more than doubled from about 336 m to 745 m. Calories per activity jumped from about 838 to 1,753. I’ve not lost any weight though. I do eat a lot of food.

My stats app shows that since starting to track my rides in 2012, my average ride distance is 39.0 km. 2015 and 2025 both sit a fair bit above that. Good to see 2025’s average standing out.

Planning ahead - 2026

I’m three months into my third consecutive Audax UK Randonneur Round the Year Award. This time I’m going for two years’ worth in one calendar year. That means at least two rides of 200 km or more in every consecutive month for 12 months. I’m also aiming for 50 Audax UK points to mark Audax UK’s 50th anniversary.

In May I’ve planned a self supported 2,200 km ride through France, Spain, and down to the Algarve. Planning on doing that over 11 days so around 215 km per day. I may do some of them as a 200 DIY audax.

The numbers aren’t the focus this year but they’ll slowly add up.

A few things come to mind that have helped.

• A spouse who knows and accepts that I love riding a bike. I’ve always been like this.
• Regularly getting out on my bike at 5.00 am for a 50km ride. Having a goto route when doing so.
• Living in Kent with easy access to country lanes and rural landscapes.
• Having a few side goals along the way.
• Tracking my progress.
• Getting in a two week bike tour in May and a few other long rides during the year.
• Riding in the dark with dynamo hub powered lights.
• Dressing for the weather.
• Living close to a fella who mends my bike when it breaks and not charging the earth to do so.
• Having a spare bike to ride when I need it.

This was the state of play on the 20/12/2025. I might get a few more rides in before the year end.

This beats the personal best I achieved of 17,987 km back in 2015. Still cranking out the miles ten years on feels quite reassurring to me. The sense of accomplishment is nothing though compared to the benefit of pursuing the goal. Purpose, motivation, fitness and conditioning, places visited and sights seen. Riding a bike is great. I love it!

The next 12 months will, fingers crossed, be more of the same. I’m currently three months into two simultaneous RRtY awards. That means at least two rides a month of 200km or more for 12 consecutive months. It’s Audax UK’s 50th Anniversary. A good year to go for at least 50 points and get the The Randonneur 5,000 award. The award is obtained by riding BR or BRM events totalling 5,000 km in a Randonneur year. I’ve been told that may get me a commemorative fridge magnet. What more of an incentive could I possibly need.

In May I plan to ride 2,200km through France and Spain down to Portugal. I am less worried about getting there than I am about getting my bike in a bag for the journey back by train. I’m sure it will all work out okay with a bit of planning.

With this ride completed thats the Super Randonneur (SR) Award bagged for the 2025-2026 audax season. The SR is a series: 200 km, 300 km, 400 km, 600 km, all completed in the same Randonneur year.

The ride takes me by my two sisters and parents homes on the way so I took the opportunity to deliver Christmas cards and pressies.

My sister in Deal dosed me up with a big helping of Sloe Gin she’d made. I’d never drunk it before. Didn’t think I would like it since I don’t enjoy spirits as a general rule of thumb. I did like it though hence the generous measure she poured me.

I set off again feeling alright, maybe a little bit woozy but steady enough. It took a toll though on my perceived exertion. The 50k or so from Deal to Tankerton took me nearly three hours. Felt like a lot more hard work than it normally does. At the time I put it down to the Tannus Armour tyre inserts I’d fitted to mitigate the risk of punctures. I’ve had loads of flats over the last month. Hedge trimmings along country lanes, glass shards and flint. While the inserts may have been a contributing factor I think it was the gin that put lead in my legs. At least I did not get any punctures.

Despite the physical struggle It was a good ride. The weather was dry. Not too cold. Very little wind. What’s more there was loads of festive postbox toppers to snap a picture of and add to the growing collection…

Another fine looking festive postbox topper I came across on this morning’s ride through Shorne Village. Added to the collection.

I’d love to meet the person that does the postbox toppers in Higham. Each one they create deserves a prize. Added to the collection.

1. Kent - southeastern section
2. Essex - northeastern section via the Dartford Crossing
3. Hertfordshire - northern section
4. Buckinghamshire - northwestern section
5. Berkshire - western section
6. Surrey - southwestern section

This is the maybe the 3rd or 4th time I have done the ride. Each time I tweak the route a bit. Lessons learned and all that. Pretty happy with the latest version. Closest I have come to actually closing the circle. The M25 is not a full circle in any case. The beginning and end is the A282 on both sides of the Dartford Crossing. Given that it’s fair to say this route in indeed a loop of the M25.

My favourite part is through the Essex countryside up to Epping. It’s very rural. Not flat but not especially hilly. The roads are quiet. After that the stretch from St Albans round to Chalfont St Giles. Farmland, quite lanes, small towns and villages. I typically get to the co-op food store in Chalfont at around 1.00 pm and get a bit of lunch there. The standard meal deal hits the spot with me.

Each time I have done the ride it’s been around this time of year. Short days. I always go counter clockwise to avoid getting to the Dartford Crossing at shift change over time (9.00 pm - 10.30 pm). The shuttle service does not run at those times and I’d end up waiting for 90 minutes at the roadside. This inevitably means I’m riding in the dark by the time I reach Surrey. I am familiar with the area so it’s not as if I missing scenery I’ve not seen before but it would be nice to do it in the daylight sometime.

Predictably I got a puncture on the way. It was a slow leak. Rather than stopping to mend it I continued to ride and stopped a couple of times after 40 - 60 km to pump some air into it. This was a mistake. Only because it was on mind the whole time and kind of marred my enjoyment of the miles.

About 20k outside of Woking I noticed my front mudguard had become partially detached. A while ago the rivets holding it to the supporting frame had failed. I bodged a mend with a couple of zip ties. The lower one of these had snapped off. Another thing to occupy my thoughts. I found myself imagining the other tie snapping on the way down a hill, the mudguard fouling on the wheel and me going flying over the handlebars. What with the recent spate of misfortunes and mechanical failures on the bike I thought it best to do what I could to mitigate the risk.

Lucky for me a good friend of mine lives in Woking. I checked how far his address was from the route. It was literally a couple of minutes at most from where I stopped to look. He was home and happy for me to visit. Great! Nipped round and stayed for an hour. Time enough for a chat, a couple mugs of tea and to make good the mudguard. Very happy. Should have fixed the slow puncture too.

About 30k after setting off again I needed to pump the tyre once more. I’d pushed my luck too far. It lost air much quicker this time. Needed to stop after a few kms to patch the tube and put the spare one on. With this done I was making a good pace again towards the last planned stop at Edinbridge just over the county boarder into Kent. The last 60k was happily uneventful. Got home at 11.30 pm. Job done.

Look at this beauty! I saw it on the ride I did yesterday. Another one for the collection.

Happy to have this festive addition to add to the collection.

I did not go out yesterday. We had a late dinner after which I went to bed to watch a film - “I Swear”. Brilliant film. Both sad and inspiring. Loved it. Certainly put my bike troubles into perspective if needed.

Up and out early this morning to get the miles in. Just a couple of kilometres from home I crossed a patch of black ice, tumbled off my bike and hit the ground. Fortunately no injuries other than a bit of a scrape to my right hip. The bike seems undamaged. My GPS and phone survived without a scratch on them. I thought the phone may have been damaged as it was in my pocket on the side I came down on the ground.

I guess it’s just one of those things that I can ride all year, cover over 10,000 miles without a mishap and then in the space of five weeks have a series of unfortunate events. Probabilities and factors stacking up I guess. I’ll admit to thinking what’s next while knowing if I identify and manage foreseeable risks the probability of anything else happening is no greater now than it ever was. It’s kind of reassurring and enough to keep me going.

Out on my bike yesterday morning. First ride in December. It was going so well. New cables fitted. Inner and outer for the front and rear mech. Changing up and down smoothly. Responsive and powerful brakes. New chain and cassette. It felt like riding a new bike. Lovely.

Just over 26km at the start of a descent in I change up into the big ring at the front and down a couple of gears at the back. Straight after doing so the pedals resist movement and the ominous sound of the rear mech breaking spokes in the back wheel sound out. I brake and come to a stop. The jockey wheel cage was detached and hanging mid way round the chain. Half a dozen spokes were snapped. The back tyre was flat. It was 0610hrs.

I had a long walk home. Just over 11 miles. I am not a fan of walking. It was not too bad though. The weather was dry. The sun came out. The time passed quickly. I was not worried about checking in late for work. I have very understanding managers. Instead of going home I walked with the bike straight round to Matt who runs a bike shop from his garage at home. Matt had done the work on my bike the previous day.

I was not looking to place blame. I just wanted to get my bike sorted and back on the road. Matt was as perplexed as I was about what might have caused the failure. I don’t think it was the limit screw. When I came to a stop the chain was on the second biggest sprocket on the cassette indicating the mech still had room to travel. I’d not adjusted it and neither had Matt. Matt had no other bikes to work on that day so he got straight to working on mine.

Got a call from Matt this morning. All fixed. Three of the broken spokes had gone through the rim tape which was why the tyre was flat. Spokes replaced, wheel trued, new mech fitted, inner tube replaced. No charge for labour. Matt said he felt bad about what happened. He told me he’d not taken it out for a test ride before handing it back to me the previous day. He did tell me this when I collected it. Matt said it all worked fine in the stand but to bring it back if there were any problems. I certainly do not blame him. We both think that the rear mech simply busted apart. How that might have happened is not clear to either of us. Definite signs of wear and rust on inner components which could now be seen but none which could have been inspected or serviced prior to the catastrophic failure. Nothing that either of us have known to happen before.

I’ve had a series of adverse incidents with this bike over the last few weeks. I’ve managed to crack the screen on two different GPS devices, had three (now four) punctures on consecutive rides, now this latest mishap. I have a second bike but did not go out on that this morning in fear of what might happen next. I know it’s not rational to think like that but still. I shall go out this evening and continue towards 18k for the year. Fingers crossed all will go well.

Sent the damaged Karoo 3 back on Tuesday. A brand new boxed unit with all accessories included arrived on Saturday. Hammerhead gave me 50% off the RRP. The additional bracket, 1/4 turn mount, charging cable and lanyard were all a welcome bonus. They’re worth £52.00 when bought separately. Free P&P for the return and replacement. Pretty good service in my books.

I bought a gel bumper case to help protect it and had this ready and waiting when it arrived. Screen protectors are in transit. All I need to be now is a bit more careful.

It’s been a very good month on the mileage front…

Yesterdays ride made my yearly Eddington number (km) a personal best since the year I first started logging my rides…

 1=== YEARLY EDDINGTON NUMBERS ===
 22025: 62 *Highest*
 32024: 58
 42023: 48
 52022: 48
 62021: 49
 72020: 48
 82019: 56
 92018: 48
102017: 49
112016: 61
122015: 58
132014: 56
142013: 51
152012: 28

I’ve achieved this on the way to beating my overall distance total for 2015. I made passing mention of setting that goal here, in my first post for 2025. That goal seems within reach barring any mishaps in December. This is how things stand as of today…

 1=== ANNUAL GOAL PROGRESS (2025) ===
 2Goal: 18,000 km
 3Current: 17,008.2 km (94.5% complete)
 4Year Progress: 91.5% elapsed
 5Days passed: 334 | Days remaining: 31
 6Status: 🚀 Ahead of pace by 3.0%
 7
 8=== PACING TARGETS ===
 9To reach your goal, you need:
10• Daily: 32.0 km/day
11• Weekly: 224.0 km/week
12• Monthly: 973.9 km/month

If you happen to be on RWGPS add me as a friend - I’ll add you back. Happy to connect and see what you are up to.

For a smaller niche interest group (you’re on RWGPS, interested in the stats above, and okay about using Python scripts and CLI apps) I wrote about how they’re generated in this post. The code for the Cycling Stats CLI is on GitHub.

“…just feeling like i’m waiting to find something purposeful. is this something common”?

It’s something I have felt in times gone by. It’s something I have read and heard other people have also felt. Too small a sample to declare it’s common. Maybe it’s more so for people whose basic needs are being met.

Sly asks,

“what really matters though?? i’m still waiting to find out.”

My answer is what really matters is whatever you decide matters. I guess you could wait for something to occur to you. If and when that happens and whatever it may be still comes down to a choice you make. No one can tell you what “really matters”. The best they can do is say what matters to them and what they think should matter to you.

I say play with the idea. Try things out. Decide to make something really matter to you every day. Soon or later one may persist. Whether persistence matters is another choice you get to make.

Sly mentions free will. Maybe this answers the question. If free will exists it must sit outside the laws of cause and effect. How’s that for a curve ball. Maybe you don’t get to decide what really matters at all. If that is the case maybe the question to ask is, why does anything really matter or perhaps, why should it?

Before setting off again I went to get the Karoo from my jersey pocket. I’d taken it off the bike to avoid scraping it on the ground when I flipped the bike to remove the wheel.

I must have missed the jersey pocket and instead put it between the jersey and the hi-vis reflective gilet I was wearing. As I went to retrieve it, fumbling about with my gloves on created a gap between the two tops and the Karoo fell to the floor.

Less than a month old and I’ve cracked the screen. Gutted. It’s literally just a month since I cracked the screen on the old one.

You can get third party replacement screens for about £100. Knowing me and not wanting to risk damaging internal parts I’m opting for the Hammerhead Crash Replacement. I got a 30% discount on this one with Karoos upgrade program. I think they offer up to a 50% discount on a certified new one when you send a damaged unit back that’s still under warranty.

When I get that I shall fit a screen protector, a silicon bumper case, and be very careful not to drop it again.

Always puts a smile on my face when I find one of these. One day I may even learn how to crotchet myself. A fine addition to the growing collection.

This is a conversation I am having with myself this week, and have had with a colleague and a couple of friends.

I noticed I was feeling angry with a decision made at work. Angry with my managers apparent inability to challenge their seniors and peers effectively.

This is not something I have experienced in any notable way for nearly 18 months. Not since leaving my last job and starting the one I have now. I guess 18 months is about long enough to become established in role and to start coming up against the organisational culture.

I don’t think that’s all there is to it though. I have been working on myself in a structured and supported way over the last few years. Prior to now I would have been very much to one side of the path. Not even realised that there was another side let alone a middle way between the two.

On Friday I had a bit of a rant in our team catch up. Indignant, righteous anger. Full of disdain. In years gone by that would then have stewed and festered. On this occasion I noticed my reaction. I could see it for what it was. I understood where it was coming from. Rather than identify with it and allow it to possess me I decided to do something different. To let it be and follow up in a constructive way. A healthy adult way.

I put together what I intended to be a persuasive and reasoned rational to articulate the case for a change I have proposed. Whether now this influences decisions has yet to be known. While it is my hope that it does, if it does not I feel at peace for having tried rather than just getting angry.

Management teams are often made up of people who nod and agree with their seniors. Who tow the party line. Who will keep things as they are and not rock the boat. People who are considered a “safe pair of hands”. Default decision makers. Predictable, reliable managers. Keep your head down and maintain continuity is the message. This might be safe but it may also stifle innovation, change and improvement.

I may be able to accept this approach bit more if I worked in a “good” organisation. I work in one that “requires improvement”.