I have a few blogs, including this one, and over the years I’ve used a few different platforms. My first ever blog was on WordPress, but now all of my blogs use Hugo, a static site generator written in Go.

The one “downside” to using a static site generator is that you can’t easily do some of the things that a server-based system can do, like cross-posting to other places. This is a post about why I chose to use Hugo and how I post to Mastodon and Bluesky (mostly) automatically.

I’m a bit of a home automation hobbyist. I bought my first few Philips Hue lights before anyone knew what Hue was, and I wrote one of the first couple hundred Amazon Alexa integrations (they even gave me a t-shirt for it!)

My house isn’t as jammed with sensors and self-made IoT devices as some of the folks I’ve seen on YouTube, but I do run Home Assistant and appreciate the occasional well-designed automation. Almost all of the wall switches in my house are “smart” and “does it connect to Home Assistant” is now a question I ask about every new connected device I consider buying.

Recently I had a couple “problems” (we home automation nerds tend to see “minor inconveniences” as “major solvable problems”) and decided to solve them with Shelly relays. This is that story.

We have solar panels on the house, and their energy production is managed by an Enphase Envoy microinverter system. I love data, so I wanted to build my own dashboard of energy consumption and production, which took me down a rabbit hole of dealing with Enphase’s shitty API.

Since then, I discovered that the Envoy system does, in fact, serve its energy data locally, so this is my brief explanation of how I moved over to that approach instead.

As astute readers are aware, I’ve been on a host my own stuff kick for some time now. I brought my music local with Navidrome, I moved my remaining websites off of that-shape-named-service into static sites that I host myself, and I just moved from Samsung SmartThings to Home Assistant for all my home automation stuff.

A recent household budget discussion wandered into the territory of replacing our Spotify family plan, and my wife’s position on it revealed what I think is one of the crucial points about hosting your own systems: owning your stuff.

This is absolutely an Emacs apologist blog, and I’m writing this post in Emacs right now. But I started at a new job recently and most of us use Visual Studio Code, and I know that’s considered a slur in many free software circles, but I’m here to tell you, “It’s OK.”