Just saying, Micro.blog’s photo challenge should be in October. Such a great time of year for photos. Well it is, from my back yard.

Just saying, Micro.blog’s photo challenge should be in October. Such a great time of year for photos. Well it is, from my back yard.

I haven’t posted a single photo in October so far, which is unusual since it’s usually my favourite month for sharing many things.
Yesterday, I mentioned that I had created a Slack account just to send webhooks to and that perhaps there was a better way of doing this. After a few hours, I have managed to put together a tool for consuming and monitoring webhooks.
Hooknook (working title) allows me to create channels and send webhooks to different channels. I’ve still got some details to sort out, but the basic application works. Users and channels are made through the Rails console at the moment, and a single endpoint accepts all webhooks coming in. It’s the absolute minimum I could do to get it to work, and now it’s happily accepting webhooks from my Hatchbox deploys.
I used Anthropic’s Claude to flesh out the structure of the application to begin with, and once I had it working, I used Claude again to add some TailwindCSS styling to the screens. These screens are definitely going to get a once-over again, as the purple is a bit garish, but my wife seems to like it, so it might stay, but be a bit more subtle.
It’s been a welcome change of pace to be able to build something in a short space of time, and even better to be able to use it.
Over the next couple of weeks, I plan to explore adding more functionality for Hooknook and being able to handle more webhooks from different sources, including GitHub.

I setup a Slack account just so I had a place to ping some web hooks too. I don’t need the whole chat and channels thing, but Slack is great for integrating stuff like this.
Wondering now if I should just roll my own version of this. Just a channel that receives web hooks that I need.
I didn’t have much in the way of mixers to go with a dark rum, so I tried a can of Irn-Bru Winter Bru. It turned out to be a fantastic combination!
Life lesson: Parents are worse than teenagers for replying back to a text.
I started building my own MVC framework using Ruby this week. It’s intended to be a fun project to explore how a framework works internally and to see how far I can get building something that can power a few small web applications.
My move back to using my own domain as my primary email address has been relatively smooth, with just a few hiccups along the way. It has highlighted a few things that I should remember if I ever consider changing email addresses again (which I hope never happens again).
When I signed up for Hey’s email service five years ago, it meant moving away from using my domain for my email address. At the time, I had slight reservations about using hey.com as my email address, but I figured it was just an email address, and I had changed it before.
One problem is that with this type of email address, I am tied to Hey’s email service, and if I want to switch, I need to change my email address. This isn’t a problem if you use a domain name you own for your email, though. If, after a while, you don’t like the email provider you are using, you can switch to someone else while still retaining the same email address. And yes, Hey does support email for custom domains now, but that wasn’t available when Hey was launched.
Using your own domain for your email address ensures the longevity of your email address but also allows you to move between email providers.
The last couple of weeks have seen me reviewing my password manager and conducting a spot check on all my accounts to ensure that I have migrated all of them to use the new email address.
Unfortunately, not every service allows you to change the email address associated with it. There are two scenarios I have found where this is the case.
Some services just don’t allow you to change your email address at all. You need to delete the existing account and create a new one. This might be an issue if the service is one you have used long-term and has numerous purchases associated with it.
I have one account with a service that has several e-books purchased against it, but I haven’t been able to update my account to change my email address. Additionally, despite contacting the service’s support team, they haven’t responded promptly to allow me to change my email address. I’ll download the e-books I have purchased in the past and then create another account for any future purchases. Fortunately, these books are technical and mostly outdated, so the loss is not significant.
Some services don’t have a fully functional single sign-on experience, where your email address associated with your authenticating service may change. I’ve noticed this with several services. I have changed the email address on the authentication service I use to log in, e.g., Apple, but the end service I am using doesn’t recognise that it’s the same account, just with a different email. From a user experience flow point of view, this seems like a red flag.
Having experienced this, I think I might avoid single sign-on logins and instead use email or usernames wherever possible.
Not that I’ll need to, though, because I am not about to change my email address. Right?
On a Daft Punk musical bender this morning thanks to @birming.
Enjoying a quiet Saturday morning with Jennifer. Stopped for a wee coffee and cake at Black Sheep Coffee in between some shops.
