Amused to realize that at the moment, thanks to my posts about books and Short Trek episodes, I’m kind of dominating micro.blog’s 🖖 Star Trek “discover” feed. Maybe once Picard starts broadcasting more micro.blog Trekkies/ers will show up?

Trying an experiment which I hope I won’t end up regretting: Re-enabling comments on blog posts on my site (but leaving them set to auto-close after two weeks).

Don’t know how often they’ll get used, or whether it’ll just be spammers and trolls, but it’s worth an attempt.

Continuing my Instagram Lurker Status

Last year, I decided to stop posting to Instagram as part of my ongoing (and some days more successful than others) goal of posting more to spaces that I control (specifically, this blog) instead of constantly pumping content into closed systems.

I’ve never entirely stopped using Instagram, though — I still check in fairly regularly to see what my friends there are posting — and over the past few weeks, as we’ve been getting closer to the new year, I’ve been toying with the idea of going back to posting there. There are ways to automatically cross-post between Instagram and this blog, so I figured that it might be worth uploading there again, as long as I cross-posted here, and participating again instead of just lurking.

However, a couple things over the past few days have me leaning back towards sticking with my lurker status. The first was Anil Dash’s post “Link In Bio” is a slow knife:

Links on the web are incredibly powerful. There are decades of theory behind the role of hyperlinks in hypertext — did you know in most early versions, links were originally designed to be two-way?  You’d be able to see every page on the web that links to this one. But even in the very simple form that we’ve ended up with on the World Wide Web for the last 30 years, links are incredibly powerful, opening up valuable connections between unexpected things.

For a closed system, those kinds of open connections are deeply dangerous. If anyone on Instagram can just link to any old store on the web, how can Instagram — meaning Facebook, Instagram’s increasingly-overbearing owner — tightly control commerce on its platform? If Instagram users could post links willy-nilly, they might even be able to connect directly to their users, getting their email addresses or finding other ways to communicate with them. Links represent a threat to closed systems.

Instagram’s lack of support for URLs in captions has been a hassle to deal with (admittedly, less so for my personal account, and more so when I was managing Norwescon’s account, but still a hassle), I just hadn’t put as much thought into it as Anil does in his post. As John Gruber summarizes it, “‘link in bio’ is fucking bullshit“.

The other thing was trying to update a post from a year ago that had been mirrored from Instagram, but at some point the image had broken. In trying to find a new link for the src argument in the img tag, I first found that there was no easy way to just grab the image (not in itself a bad thing, as it’s likely at least in part an anti-image-theft measure), so I figured I could just grab Instagram’s ’embed’ code and find the image link in there. However, their embed code is obfuscated in some way so that there isn’t a simple image link anywhere in there that I could find, and it ends up being a huge mess of code (check under the cut at the end of the post to get a sense of how much garbage code Instagram wants us to use when displaying an image elsewhere).

In the end, I just used Safari’s developer mode to extract the image and manually uploaded it to WordPress to add it to the post. I’ve also downloaded all my Instagram data so that I have a local archive I can use as a source for manually correcting any other now-broken Instagram cross-posts that I find in the future.

So the end result is that no, I won’t resume uploading to Instagram after all. But, for now, I’ll keep my account around so I can keep peeking at my friends’ lives, at least.

Read more

On This Day

I’ve just added an On This Day page, using cog.dog’s Posted Today plugin, listing any posts made on the current date in past years.

I’m also considering pre-scheduling have scheduled a daily “On This Day” post for the year of 2020, as I’ll mark 20 years of blogging on November 25, 2020 (though I didn’t discover the term “blogging” until a few months later). While each day’s post will duplicate the “On This Day” page, they’ll be static lists, and will be a nice retrospective of my babbling over the years.

Today’s geeky triumph: Figuring out how to use Automator to create a service that pipes selected text through pandoc to speed up converting old posts on my blog to proper markdown format from the current HTML/markdown hodepodge.

Still in the very early stages, but in an effort to combat the website ennui I mentioned a few days ago, I’ve started playing with building a new personal site at a URL so clever I wish I’d picked it up years ago: michaelhans.com. Not much there, but a new playground is nice!

Website (not blogging) Ennui

I’m not really happy with my website — I’m tired of WordPress, and ‘view source’ just makes me cringe at all the junk, cruft, and JavaScript bogging down what could and should be relatively simple, clean, HTML/CSS — but I don’t know how to reinvigorate it in a way I like.

I don’t want to entirely stop blogging, nor do I want to lose all the stuff that’s here already, or break existing URLs.

I’ve been looking into various flat-file or static CMS backends, and though grav is the one that most caught my eye, it (as far as I can tell) would mean losing the ability to post through micro.blog or any other third-party app that uses the MetaWeblog API, which would make spur-of-the-moment posts more difficult.

Even if I did resign myself to only adding posts through the admin UI (or by FTPing in to manually build the folder/file structure that grav uses), if I figured out how to import all my past entries from WordPress (this might do it), I haven’t been able to find a way to tweak the URL structure, which means I’d probably have to figure out how to generate a huge .htaccess file to handle the 5,170 or so redirects so I didn’t break any existing URLs. I may not get linked to a lot, but it happens occasionally, and I’d prefer not to 404 those.

(Plus, as I was playing with grav, I kept getting blank screens where I should have been getting post entry or edit screens, which…well, not sure if that’s a grav issue, a Safari browser issue, or some other issue, but it didn’t bode well.)

Other backends either looked too complex for my current needs/skills/available time (I just don’t have the time or impetus to try to learn Jekyll, which kept popping up), or didn’t fully support Markdown at all or enough, or had one or another thing that made them feel “not right” for me.

Really, what I’d kind of like to do is go back to hand-coding my site, so I have full control over the HTML/CSS (even if it looks like crap, it’ll look like my crap…so to speak), only to still be able to blog easily using micro.blog or Ulysses or other such tools. Not sure that’s really a possibility, though.

In the end, this isn’t much more than a bit of whinging and trying to figure out what exactly I’m looking for. But if anyone actually 1) reads this, and 2) has a magical solution for all my woes, I’d be happy to hear it!

I’ve been thinking about moving away from WordPress for a while now, and I think I may have found my replacement backend: Grav.

I’ve got a base install running. Next: play with settings and design, look for WordPress importers, external editor/microblog support options, etc.