General geek, gadgeteer, tea drinker, occasional photographer, wannabe musician, and liker of Oxford commas. Recovering sysadmin. Lefty woke liberal. 🏳️🌈
I tend to post about anything, often techy things, but of late occasional UK political things too.
I mostly write code in #Go (#golang) but lately I've been learning #Swift and #SwiftUI. I will touch #Python under duress. #Perl was my first real language and made me love writing code.
| (Rarely updated) Blog | https://jamesog.net |
| GitHub | https://github.com/jamesog |
| Flickr | https://flickr.com/photos/jamesog |
| Bluesky | https://bsky.app/profile/jamesog.net |
To the sysadmin population of the Fediverse: do people have any numbers on how long common mail senders will retry sending mail if your MX is unreachable? Once upon a time people retried for many days, but my impression is that quite a few places now stop trying and bounce the email after quite short intervals, like a day.
(Boosts and practical experiences welcome, like "my MX was down for three days and I still got all that email sent from GMail".)
I thought I'd start migrating some of my Go code to a "vanity import" so I can start migrating some things off GitHub, so I wrote up a quick guide to doing that with nothing but Caddy
https://jamesog.net/2026/03/29/go-vanity-imports-with-caddy/
Go uses the full URL to a repo to fetch it with go get, i.e. go get github.com/username/module fetches it from exactly that repo. It can be nice not to tie yourself to a specific repository host. The go command always fetches using a query string of go-get=1. We can make use of this in Caddy to return an HTML meta tag understood by go get to point at the actual repo; or otherwise redirect to the module’s documentation on pkg.go.dev.
OH LOOK. Once more I have upgraded hugo and once more it has totally broken with my existing config.
I really think I'm just going to hand-roll something. My needs are not complex.
DHL UK really are fucking useless. Worse than EVRI, at least around here.
On Tuesday I got a notification that a delivery was on its way, due between 18:00-19:00. By 20:00 it still hadn't arrived and the driver was only halfway around the route.
Around 22:00 the tracker updated to say that at 20:00 it's "been delayed" and would come next business day. Retconned.
It did not come the next day.
This morning it now says it's at the depot and will be coming... two days ago.
Chris Siebenmann
Thomas Guyot-Sionnest
Gina