Good morning all.

The News

Long time supporter Steve brought some news to my attention, explained in greater depth at https://www.the-independent.com/arts-entertainment/music/iggy-pop-bbc-six-music-jarvis-cocker-b2918338.html , the long and short of which is that Iggy will take a hiatus from radio for the remainder of 2026, beginning in April. Current plans are for him to return in 2027.

That means we have about 8 shows remaining before he leaves to focus on musical project(s) and we obviously wish him the best with those endeavors. And if you have a chance to see Iggy in concert I highly encourage you to do so. He currently has three shows on the schedule at https://iggypop.com/ .

What This Means For Us

Here at the archive we will continue our weekly Harmony In My Head posting, but with a halving in new work, maybe it's time for some housekeeping?

It's a matter of practicality that neither of the programs we all enjoy can continue forever and recently I have been thinking about the next evolution of this site.

The internet has changed and I have received several remarks in the past few months asking how to listen. The zip files we have historically used present a friction point that bears thinking about. Additionally, the architecture we use to host and manage the shows, pages, and related materials use some fairly robust software on the back end and as a public facing website, we are under constant attack, which has never been successful.

The idea of being compromised is something I worry about every time I log in.

This is just the last few hours of alerts from bot attacks and I get thousands of these alerts every week.

Keeping the software up-to-date and staying aware of threats is a constant effort and so my long term goal is to convert this from a site that uses scripting languages, databases, and other tools with a broad attack surface into something flatter, more static, and portable, so that the entire site can be picked up and moved to a new hosting environment with zero real effort as well as minimizing our attack surface.

That requires careful thought and is something I've been experimenting with for a few months. Once I solve the problem of allowing commenting without the current infrastructure, that's the direction we will move towards. It will look and feel the same on the front, but will be vastly simpler on the back end.

This should also allow greatly reduced cost, which is an issue we will be facing in a year or so anyway.

As always, thank you for your time, attention, and support.