After briefly operating again, authentication to the Peloton API has been re-restricted. There are apparently some workarounds, but building a bunch of OAuth mechanics on top of a non-public API is a lot of work on something too fragile for me to rely on. That means that RideShare is inoperable for the foreseeable future, and that’s a big bummer!

Much, but not all of the ride data continues to be available through Apple Health, so I can continue to use a lot of what I did to summarize the year’s exercise data last year. Here’s a quick comparison of workout intensity in 2025 and 2024.

Today’s hobby project troubleshooting: Darn, which library did I update in that other project (don’t renv me right now, I’m riffing) that’s causing this to fail? Okay, update some other libraries. Okay, maybe there’s new R version conflict; update R. Now reinstall all libraries. Hmm. Okay, rewrite to go around the place where I think the error is raised. Nope, but that isolated enough that I can see the problem. Fixed in one minute.

I’ve updated my annual last.fm summary stats app for 2025. I’m really happy with this year’s changes: The app should be faster for most users and it offers a simpler couple of visuals, displaying a shareable card for your top “new to you” artists as well as for your top overall artists of the year. It’s fun to update this year over year. If you’re a last.fm user, I hope you’ll try it out!

deardestiny.shinyapps.io/tuner

My little data vis all for my Peloton rides broke a couple of weeks ago, but clever developers found a way to continue using the API, so it’s back, for now. I wish Peloton would publish an official auth flow; they would see an explosion of support and interest from small and big developers, I think.

My week in riding the bike: I was under the weather after a few long, in-person work days last week. Improving early this week, I started up slow but built to feeling really good for this morning’s dawnbreaker HIIT and Hills thumper.

I made some updates to my RideShare app (which produces nice, shareable images of Peloton rides) that I’m really happy with: More flexible output image sizing and the ability to select from the image types that the Peloton API provides for more interesting visuals. I wrote this up over at the data blog.

I vastly prefer writing and working with R to Python, but marimo is a really interesting tool and addresses the thing I’ve always disliked most about jupyter notebooks – the awful json file format that stores state in the document itself. Its browser-based editor feels pretty nimble and modern, too. I’ll explore it some more.

Over at the datablog, I wrote up some details on producing my 2024 workout summary from Peloton and Apple Health data. This was a fun little project to tinker through over my holiday break.

Last Peloton ride of 2024 went quite a bit harder than I was expecting. I’ll go out sweating hard because I can, and I’ll try to start 2025 the same way.

I volunteered to do some copyediting of the web page for my kid’s school, and naturally the best way to do that was to spend a couple of hours learning how to use {rvest} and writing a short script to scrape the site into a set of Quarto files. I’m right on track to get started with the copyediting in early 2025, give or take.