• The Week #42

    • Tokyo is entering another State of Emergency. I understand why their doing it, Kanagawa should probably also be declaring one. But these half-measures for the past year(!) and a glacial rollout of the vaccine, I feel like I'm getting close to the "pandemic wall".
    • I finished and submitted the first draft (to be published in June) of a magazine article I'm writing (Japanese) for an internal review at work. I always get a bit nervous before submitting these kinds of things, like they'll suddenly realize "wait a minute, this guy doesn't know what he's talking about". Getting your Japanese nitpicked and seeing grammar mistakes that you know you learned back in college is also humbling.
    • Hoshide-san successfully launched and made it the ISS. Always happy to see JAXA astronauts fly.Β 
    • I ordered the new Bourdain book – Word Travel: An Irreverent Guide. Although Bourdain has been dead a couple of years (something I still think about on occasion and get sad about the loss), this new book was a work in progress until just before he passed. Apparently he was slated to work on it for a couple of weeks that summer. Either way I think it fits exactly what I've been wanting to read: something not heavy, not work related (no tech/design), non-fiction, and something in English. Excited for it to arrive.
  • Leo’s new favorite pastime is to crawl around the car and listen to music. He switched the radio station and Journey comes on. Immediately says β€œI like this”. Addaboy.Β 
  • The wind is so strong, last night it blew the cover off my bike, blew the e-bike over, and its cover has disappeared. Time to see if I can find it.

    Update: Found it a few houses down stuck under their car.
  • Made some optimizations to my site today.Β 
    • Enabled the django gzip middleware so html is compressed over the wire. Practically speaking, responses loads should be about 5kb now, or a quarter of the previous size.
    • Optimized the queries for public facing pages. All pages now require less than 10 queries.
    • All optimized images will now be automatically resized by 50% and converted to webp (where supported). This helps reduce images sizes from drastically, usually to around 100k or less, each.
  • Checkin to ホンダカーズζ¨ͺ桜 泉みγͺみ店

    in Yokohama, Kanagawa, Japan
    1 year tune up for the car. Time flies.
  • Seeing that Basecamp is shutting down their famous Signal vs Noise blog, I can’t help but wonder how much was the faff of dealing with Wordpress.
  • Checkin to Ootoya (ε€§ζˆΈε±‹)

    in Yokohama, Kanagawa, Japan
  • First Days with Tanzawa

    This was my first week using Tanzawa to power my actual blog and not just the dev blog. So far it's been great. I love how easy it is to post. I love that my site is IndieWeb native. I love that my site's stability has improved because I no longer require a database server. And I love that it's using fewer resources. It's great.

    This said, there's been a few rough edges that need polishing. Approving 50 some-odd webmentions after OwnYourSwarm started importing un-sent checkins required 50 some-odd page loads. Ouch.Β 

    I'd also like to improve site performance more in respect to images. Currently Tanzawa automatically requests the most efficient image format that your browser supports. Image format selection is all handled by the browser automatically (no Javascript). This alone usually cuts transfer size in half.

    While cutting the transfer size in half with a format change is a good start, I still don't need to be serving (at times) 4000px wide images. This is noticeable in streams where posts usually have images ( Checkins etc..) where the text loads instantly, but the progress bar lingers while images load.

    Rather, I'm going to change it to serve a resized (max 800px wide? ) image unless the original is specifically requested.

    Lastly, I want to start building a list of things that must (not should) be done before I can feel comfortable releasing Tanzawa for others to use and then start working on that list bit-by-bit.
  • Fixed the rest of the site on mobile. Which really means content is now full-width and stacked, rather than in columns. It's amazing what you can do these days with just flex, flex columns and media queries (made super easy with Tailwind).
  • I've fixed navigation on mobile, first time doing responsive design with tailwind. The hamburger menu is just a button with 3Β  8px by 1px brown divs inside.

    Fixed navigation on mobile.
Previous 149 of 362 Next