Dev Diary 2020-07-01

Statutory holidays are a fine time to pull a project idea out of the hat. Today I finally started to poke at Jitsi - something I’ve been meaning to do since we started doing podcasts remotely.

Jitsi got Docker instructions a couple years ago, so I took I took a crack at that. The user experience for setup is pretty straight-forward. So straight-forward that I’m pretty sure I’ve spent more time thinking about how nice it would be to have a Jitsi server than it took to set up one up. I recall spending a fair amount of time figuring out how to force Zoom calls to work through the browser, and that was longer than setting up Jitsi - that’s how quick it is.

(BTW - if you were wondering how to force Zoom to work through the browser, convert your URL from to

Spent my Canada Day shoring up a whole bunch of tech debt on the various little projects I run. Not sexy work, but like Jitsi, I’m pretty sure I’ve spent more time thinking about doing the work than how long it actually took. Maybe there’s an insight somewhere ;-)

I also felt inspired by Jess Frazelle’s ode to automation, and took a stab at getting my gmail filters automated. I’d built up several hundred filters over the years, and I managed to hit a few edge cases along the way of offloading it to the new tool. Of course, it now looks like Jess has dropped Gmail for hey so it’s unlikely my patch will ever get merged. Nevertheless, a fun morning exercise with my coffee.

Ended the day setting up a home Docker registry, because A) I like a good yak shave, and B) I’m hoping that I can reduce latency for my little home cluster to yank new images. Is this strictly necessary? No, but to steal a line from Fear and Loathing in Las Vegas, “once you get locked into a serious Docker collection, the tendency is to push it as far as you can.”

More Intel tire-fire. But process isolation isn’t a big deal, right?