Writing
A blog of acquiescent temper, miscellaneous opinions, and uncertain vote.

The final platform

I’ve lost count of the number of times I’ve redesigned and/or relaunched this site (or its predecessor). Over the 21 years it has been active, my personal blog has run on Blogger, Textpattern, ExpressionEngine, WordPress, Ghost, Jekyll, and probably some others that I’m forgetting, plus at least one hand-crafted service.

It’s to the last of those options that I now return. I’ve spent the last couple of months putting together a new platform that I hope will be the last one I ever need to switch to — because all it does is hoover up every other source of personal content and store it in one place.

Implementation

It’s pretty much the opposite of what Jeremy Keith does with Adactio.com; but where he publishes once (on his own site) and then syndicates it out to Medium, Mastodon, Bluesky, etc., I am instead publishing on whichever platform I want to use as the “primary source” and then consuming (mostly via RSS, more on that in a moment) those posts to store and reproduce them here. It means I don’t need to bother building my own CMS, or solve complex challenges like account management or image handling — all I needed to write was some XML parsers and database queries.

(Rob Weychert seems to be doing something fairly similar, albeit very slowly over the course of the last five years, and with a much more ambitious goal of importing every piece of historical data he can find.)

At the moment, this site includes things posted to:

  • My Bluesky feed
  • My main personal blog (running on WordPress)
  • Three different Tumblr accounts
  • My Medium profile
  • My Goodreads reviews
  • My Letterboxd entries
  • My Strava workouts
  • My Spotify favourites playlist

Since the vast majority of the sources listed above provide an RSS feed, it was incredibly simple to write a small function (which is called via a cron) that checks for new posts and saves them in a local database. There were only two sources that required a more complex solution: Spotify and Instagram.

Spotify

Spotify has a very rich set of APIs which are relatively straightforward to use. Your regular Spotify account also gives you access to developer.spotify.com, where you can register an app and receive an API token to use when making any calls.

Unfortunately there isn’t any way to directly access a user’s actual “favourites” without needing to have them manually authorise each request; instead what I am doing is requesting a specific public playlist that I add my favourites to. The playlistTracks endpoint has limit and offset parameters, so I’m just grabbing the most recently added 25 tracks and storing anything new.

Instagram

Instagram is a whole different ballgame, though. They don’t make any feeds available, RSS or otherwise, and the only API access is restricted to business and “professional” (i.e. influencer) accounts. Plus their website is rendered entirely client-side, so the page source is nothing but a ton of JavaScript and dynamically named blocks of data.

I suspect there could be a way to extract your photos by running a headless browser to render the final source and then pull out the images that way, but I ran out of patience and gave up on it. It’s far easier to just re-post any Instagram photos to my WordPress blog anyway.

So now that I have all of my content in one place (and sorted by publication date), I can simply retrieve it and employ a custom renderer for each different type of content. Any new sources I decide to add later will be encapsulated in their own module, making it easy to tweak the appearance of individual types of content when necessary.

The future

This is only a placeholder design for now, something that I could use to get the site live before the end of Q1. I’ll be spending the rest of the year working on a more comprehensive redesign — I want to introduce some static pages to flesh out the personal/portfolio nature of the site (“About me”, “My work”, and so on), and I’ll probably move some aspects of the lifestream into separate feeds rather than keep everything combined into this one single firehose. I need to add an RSS construction kit too, since I doubt anybody in their right mind would want to subscribe to everything I’m (re)sharing here.

But for now, I’m happy it’s out the door and mostly feature-complete. My hope is that it will encourage me to write more (in all of the places I want).

Have you written about this?

Submit a URL containing a link back to this page. (What is this?)