Tag: meta

  • New theme: Endgame

    The Avengers: Endgame movie header image

    If you’re reading this, then I’m afraid to tell you that it has all gone off without a hitch and the great blog migration of 2026 has been completed successfully. We’re now live on a new host, in a new country, on a new continent, and with a fresh coat of paint to boot.

    I’ve never been particularly fussy about my theme here. While I’ve definitely had preferences, and have never shied away from moving something around, or changing something here and there, I’ve never been particularly bothered about anything overall. Despite a number of theme changes over the years, Show Off by WooThemes has been a fine theme that I’ve been happy with for many years. But we’ve had Show Off for a long time now, and for a few years, I’ve had a few ideas about what my blog would look like, if it was something I had to design “from scratch”. But hold onto that thought, because we’ll come back to this.

    Email receipts show I purchased Show Off from WooThemes in November 2013. How soon I implemented it after that is a mystery; a post from October says I updated some post visuals, but there’s no posts around that time that indicate I changed themes entirely, at least not in the same way that there were the previous times this happened. Which, surprisingly, turned out to be quite a few times in the first few years’ of this blog’s infancy. Let’s chalk the rapid change of theme to the rapid pace of change of the web at the time, my own changing preferences as I learned about what I wanted and what I didn’t, and probably a little too much time on my hands. How else would I have gone looking for WordPress themes? Where there’s lots of low-quality themes, outright scams where you might download some malware instead of a theme ZIP file, and all of that is before getting to designs I actually like? Anyway, for all I know I could have sat on Show Off for the better part of a year, and only made the switch around the time I changed from shared Australian hosting to a VPS in New York from Digital Ocean, where my blog has happily been served for over a decade now. But we’ll come back to this, too.

    And while I’ve never really hated the current theme, I’ve never really loved it, either. It’s been firmly ensconced within “acceptably OK” territory all this time. Framework themes are a bit like that. They’re over-engineered to cater for a wide variety of layouts and tastes and styles and personal preferences, but at the same time, lack the kinds of personal flairs that make a personal blog, well, personal. I’ve never needed WooCommerce compatibility, nor a fraction of as many plugins as they offered at the time. I enjoyed the flexibility of being able to customise the theme to my liking, and based on screenshots of the original theme I did exactly that, but even then, that was a one-and-done thing to setup the look and feel until I had something that I was happy with, not something that I continually re-visited on an ongoing basis. And now that I’ve been there and done that, all that flexibility is just extra baggage. Useful and necessary, at the outset, but now just something you’ve been dragging around on your journey when you could have had something more sleek and lightweight.

    And as the years have rolled by, and both cosmetic and technical baggage has accumulated, the time has come to swap themes yet again.

    But to what? Another framework theme seems ill-advised, given what we’ve just covered. Besides, it’s 2026, are there even WordPress theme shops in this day and age? Surprisingly yes, and I even think Elegant Themes were selling Divi over a decade ago, but that still doesn’t make them a good option. I don’t care how many times “performance” is mentioned as a selling point, the fact that it’s mentioned in the first place is a dead giveaway that maybe the theme isn’t as performant as it could be. But like I said, that comes with the territory when it comes to all-in-one framework themes.

    Clearly, the best option is to do what I’ve always wanted to do, and design my own theme from scratch. Paid themes might come with customisability advantages, but that’s only because they’re the jack-of-all-trades, master-of-none option. If I design my own theme from scratch, and include the features and layout that I want, then isn’t that the better deal overall? Where I won’t need to spend a bunch of time customising the theme to my own liking, and can instead spend that time fixing other issues along the way?

    But if I am going to design my own theme, I don’t want to design something only for the current flavour of the month to change. That means Liquid Glass is out, despite how technically impressive and cool it is. Or uncool, depending on what you think of the latest iOS and macOS releases. The Okta app’s recent rounded redesign is exactly the kind of thing I want to avoid. I don’t think it looks bad, in fact it’s much more aligned to the overall design language of iOS 26 and 27, but what’s it going to look like in 5, 6, 7 or 8 years when design language changes again, and there are new paradigms to incorporate into our designs? I don’t think overly-textured, reality-mirroring skeuomorphic design was necessarily a net positive for design, but neither were the flat, lifeless landscapes that replaced it. Like all things, maybe the answer was a bit of both, which seems to be what we’re moving back towards. If I want to design my own theme, it has to have a textured background, a slightly raised reading surface, dark mode, and be responsive so it looks good no matter what device you’re reading on. It’s 2026, for crying out loud, and my current theme doesn’t even support dark mode. I know changing designs isn’t a big deal, but look at Instagram’s new font. It’s… wild. Maybe that’s 2026 for you.

    Continue Reading
  • Now With No Comments

    I’ve now disabled comments here. I probably should have done this a long time ago, but every time I went to do it, a little voice in my head said that I should keep them around as they weren’t costing me anything. While that’s probably true, they weren’t really adding anything, either.

    So I’ve disabled Disqus and turned comments off. The comments themselves are still kept in the database, if I want to re-enable them at some point in the future, but otherwise you know how to reach me if you want to comment on something I’ve posted.

  • Now With More HTTPS

    Ever since Let’s Encrypt announced free SSL certificates (albeit with a few caveats, more on this below), I’ve wanted to make the change to serving web pages on this blog securely. Last night I finally buckled down and got it done. After a small mishap that involved the accidental removal of my Nginx configuration file (a droplet backup saved me from certain disaster), I generated a cert following the pretty great tutorial from Digital Ocean.

    A few notes on the process:

    • For people just running a self-hosted WordPress blog, there’s zero WordPress-side configuration you have to do, which kind of surprised me. I thought I was going to have do at least install some kind of WordPress plugin, but it turns out enabling HTTPS is all dependent on your web server software. For Nginx, it’s a few lines in your site’s configuration file, and presto, HTTP over SSL (once you’ve gotten past the hurdle of generating your cert).

    • One of the first issues I ran into was the certbot not recognising my domain, returning a 403 Forbidden when it attempted to authenticate that I owned the domain in question. At first I thought this was because the DNS changes I made hadn’t propagated yet, but then I realised it was one of my Nginx access rules (the only preventing access to any file or directory starting with a period) that was preventing certbot from accessing my domain. A quick Nginx configuration change fixed that issue – I’m still not sure if it will need to access the well-known directory again when it attempts to renew the certificate, but we’ll know in about 89 days.

    • Yeah, Let’s Encrypt only issues certs that are valid for 90 days. But it’s not such a big deal, because there’s a handy way to renew your cert that you can even put in cron for true set-and-forget functionality. It’s not the annual or multiple-year certificate that you’d get from a more established CA, but you’re also not paying anything.

    • Once I had generated the cert, updated my Nginx configuration, and restarted Nginx with the new config, my blog wouldn’t load — the connection would just time out when attempting to load it in a browser, and curl via Terminal told a similar story. I scratched my head at this a little, until I discovered that my server’s firewall was blocking port 443. Oops. Bit of a rookie mistake there, and what made it even more difficult to diagnose was how I had set Nginx to redirect HTTP traffic on port 80 to port 443 — pretty standard practice when enabling HTTPS, but it made troubleshooting the issue more difficult.

    Anyway, my blog now scores an A+ on Qualys’ site SSL testing suite, and all I have to do is turn think of some other stuff to write about, so there’s actually something to serve over HTTPS.

    Update Dec 30, 2016: After discovering that (some? if not all) posts with images were being served as mixed content, I used this sql update statement on this page to update all my wp-content links in posts to be served over TLS. I also updated my site URL in settings, so hopefully everything should be hunky-dory.

    Or… maybe not. I just realised that there’s probably a tonne of pages (mostly from the now-defunct Posterous) that would have been being served over HTTP. Still not sure what I want to do with those Posterous posts, as images as broken on all of them at the moment.

  • New Blog Post, Host, Why Not Both?

    When I started out on the web in 2008 with a little site called Freshbytes, it was a different time and place. I needed somewhere to host the website, and there wasn’t much out there for affordable hosting for a high school student. I initially chose to go with BlueHost, which was fine — say what you want about shared hosting, but it was plenty good enough for the simple WordPress website I wanted to host, and even turned out to be more than OK for the additional WordPress websites and other static websites I started up later on (including this one).

    I eventually moved away from the US-based BlueHost to the Australian-based VentraIP. Not for any particular reason, besides wanting my hosting in Australia. There’s actually very little difference between hosting in Australia and hosting overseas, besides a shorter route for what I assume is most of my “audience”. A large price disparity meant I couldn’t host in Australia from the outset, hence having to go with BlueHost, but in 2010 I made the switch, and have been hosted on VentraIP until recently.

    The way I get by without a full-time job is keeping my expenses low. I don’t drive, smoke, drink, or take drugs, and part of keeping my expenses low involves looking at my recurring expenses every now and again, just to see where we’re at. It’s why I’m not a full-time Spotify subscriber, even though I enjoy the service occasionally and it’s, what, $12 a month?

    Recurring expenses are a tricky thing. In the old days you’d pay for a bit of software and be done with it, at least until the next major version came out or you needed to upgrade, but these days, everything is a subscription. You can subscribe to Spotify for music, you can subscribe to Office 365, and while you can’t subscribe to a copy of Windows just yet, there are rumours that will happen in the future. You pay on a monthly basis for your mobile and internet and while that’s all well and good, you have to factor those in when you’re looking at your finances.

    I never used to do an annual review of everything that I’m paying on a recurring basis for, but with the subscriptions and recurring expenses staring to pile up, I thought I’d take a look. Sometimes subscriptions are better value for money, and sometimes they aren’t. For example, I used to pay every year for each new major version of Lightroom, but when Adobe came out with the Creative Cloud Photography plan which included Lightroom and Photoshop for around the same price I was paying for Lightroom, it made sense to move to that instead of just paying for Lightroom alone.

    Continue Reading

  • Barley for WordPress

    via Barley: The inline editor for everyone. Change the web. – from archive.org, as the original is now dead

    Barley for WordPress is a super-cool plugin that lets you make changes to posts on the front-end, rather than having to dive into the WordPress editor to make your changes. Great for if you spot a typo, updating a link, or re-writing entire paragraphs.

    But I don’t think I’ll be using it, because as Shawn Blanc discovered, it converts posts into HTML from the WYSIWYG/Markdown backend that I enjoy using. That’s a super-minor issue and shouldn’t discourage “normal” users from picking it up, but it just doesn’t work with my post workflow, you know? I’d rather edit in Markdown than have to write messy HTML in posts.

    Hopefully one day soon the WordPress folks will bring native Markdown support to self-hosted WordPress blogs, not just ones hosted on WordPress.com, but until then, I’ll be sticking with the excellent Markdown on Save plugin.

    — permalink to this post

  • Small visual update and RSS migration to FeedPress

    Just a quick update: I’ve migrated this site’s feeds from Feedburner to FeedPress. You shouldn’t have to re-subscribe or anything, and if you’re already subscribed via your favourite RSS reader (I’m using Digg Reader these days after the great Reader-pocalypse of 2013), then you shouldn’t have to do anything. And if you’re not already subscribed, what are you waiting for? Subscribe today — it’s honestly the best way to keep abreast of the infrequent updates around here.

    Secondly, there’s been a slight change to the visuals of posts. I’m slowly working towards the gold standard of how I want my blog to look, but until I find a really great theme I’ll just continue to customise this one. If stuff looks a little off, it’ll most likely be a temporary thing. Probably. Unless I don’t notice.

    As you were.

Benny Ling's Bling

Computers are like a bicycle for our minds.