Related, this was recently published by the author (who has aphantasia) — a post describing a self-made Kobo enhancement that uses text-to-image generation to assist imagery-rich fiction. Here's the HN link: https://news.ycombinator.com/item?id=39842710
(More related to the comments than the article) I've seen tons of takes on this since watching the end of the race this morning and, although it certainly played a part in deciding the outcome, it's a shame that more focus has seemed to be on making excuses or how the Dutch riders messed things up instead of Dr Kiesenhofer's incredible story and ride.
Kiesenhofer was on a fantastic day: van Vleuten's earlier attack from the peloton made no inroads to Kiesenhofer, assuming the time gaps shown on the TV were correct.
Watching on the TV we knew there was still a rider out front and, even if the race "ardoisier" (blackboard holder) wasn't the best, team management should have figured out a way to get that information to the chasing pack. I mean, the race finished on a motor racing circuit with pit lanes containing team helpers! It's not like it was like stage 16 of this year's Giro, where poor weather stopped race images being broadcast[1].
The author/editor has mentioned elsewhere in this thread that he was using dummy data (which contains mistakes). For this dummy December flight LHR would be in GMT (UTC+0) and not BST (UTC+1).
I appreciate how hard it is to get buy-in from all parties involved, and NDC was initially launched in 2012, but is XML still a good fit for this solution? Are there better alternatives now?