Scratching an itch…

I have long admired the way some bloggers are able to include an image when auto-posting to Twitter. Looking at the IFTTT applet I was using to auto-post from my own blog, there did not appear to be an option to do this, and a web search did not yield any useful results.

I turned to Twitter and asked Warren Ellis what service or plugin he uses1. Having asked the question, I received a couple of suggestions from Doug Belshaw:

Looking into both of these I could see that they would achieve what I wanted but I was not satisfied with either implementation. Blog2Social requires you to create a Twitter application. This is not a big deal (I’ve done it before) but I did not believe this was necessary to achieve my goal. Furthermore, it is heavy-handed on the promotion of its paid features in the WordPress backend. The other option, Jetpack, is too feature rich and its footprint on the back end of your blog is quite intrusive. Furthermore, to access all of the auto-tweet features a paid plan is required. This does not sit right with me given the open source origins of WordPress.

Returning to IFTTT, I could not shake off the feeling that there was a way to do it. The search function in IFTTT is a bit hit and miss with a high noise to signal ratio. However, there were several recipes that indicated images could be posted natively to Twitter from other sources. This lead to me taking a fresh look at the Twitter channel in IFTTT. I saw that they have added a range of options and this indeed included the option to tweet with an image.

So, to relieve the proverbial itch, I started from scratch (😉) and created a new applet to share my WordPress posts to Twitter with an image.

dr amp shovel

This was a definite case that proved it is always worth digging a little deeper! Dr. Amp would approve.


  1. I subsequently found out that Warren uses the Jetpack plugin. However, he has recently written in his newsletter about issues he has had with this feature not working correctly. And I do believe he has since found a solution.  ↩

Reclaiming My Domain (since August 2016)

This is a post that I started writing back in 2017. I thought I should finish it off and post it for posterity. Some of these details have also been added to my about page.

rh make some noise gif

Reclaim Hosting

Back in August 2016, I moved my domain from Bluehost to Reclaim Hosting, which was co-founded by Jim Groom and Tim Owens. It grew out of the Domain of One’s Own project at The University of Mary Washington; providing space for students and educators to take control of their web presence. The migration was efficient and hassle free. A couple of issues arose as these things do and the support Reclaim provided was unparalleled.

Jim and Tim are legends and I am very happy to support their work. The ethics and aesthetics of the company chime with my own; not least due to a youth spent listening to punk and new wave. Two years on, I remain more than satisfied. Auto-updates; easy back-up and detailed documentation have allowed me to keep my various sites running with ease.

German Server

When I first signed up to Reclaim Hosting all of their servers were based in the US. As someone one who cares about privacy, I was ecstatic when I read Jim’s post: ‘Reclaiming Europe’. Jim and Tim’s success meant that they had to keep adding server space and this included the addition of their first European server in March 2017. I immediately made contact and took them up on the offer to move my domain to a Euorpean server. The server is called Kraftwerk and has been reliably serving my domain ever since.

Kraftwerk

On making this move, I realised that it had been quite some time since I had listened to everyone’s favourite German synth pioneers. I put all of their records on rotation and even made a playlist of their best material. This quickly began to punctuate my Saturday morning runs and the walk home from work.

Long Live RSS

Finally, like many of my web peers, I value open web standards; particularly RSS. In May 2017 Manton Reece and Brent Simmons released a feed format similar to RSS and Atom called JSON Feed. Based on the “developer’s choice for APIs” it “is much simpler to read and write” than XML, “and it’s less prone to bugs”.

This has been added to my blog using the WordPress Plugin giving readers an additional way to subscribe alongside the built in XML feed that comes as standard in WordPress. If you want to know more about why they created it, Manton and Brent discussed it on The Talk Show with John Gruber.

“We’re functioning automatic / And we are dancing mechanic / We are the robots”

~ Hütter, Ralf, The Robots (1978)

Make Some Noise Gif CC: Bryan Mathers (2017)

Hello World! Again.

Like all the cool kids seem to have done, I have added an archive of my tweets at twitter.jamesmichie.com. I have not decided if I am going to delete all my tweets, but as you will see, I have been pretty close to inactive for some time.

Nor have I found an alternative social network to engage in. I had a brief dalliance with Mastodon but I was not enamoured with the format (in essence a distributed clone of Twitter) – unsure as to whether I could, or even wanted to, rebuild a close network of peers.

In fact, I am not sure that I need social media as it currently exists. I do not believe that I have missed anything over the last year or so by not being active on Twitter. Quite the contrary. I have read more books and actual news. I have grown a cultivated list of blogs in varying genres to read via RSS (yes that old chestnut). And I have focussed on my health and fitness (running has taken over my life!)

However, I signed up to Micro.blog, today, in the hopes that it encourages me to post more regularly in a shorter format. Sharing is important (IMO) and I feel there is space (once again) for writing to be a positive outlet for me. Micro.blog allows for self-hosting, via WordPress and other open source blogging platforms, which means that I will retain ownership of my data. It also offers a growing network and native MAC and iOS apps.

I hope the shorter, low-stakes format of micro-blog encourages me to post briefly and regularly. 

We will see… I have promised a return to regular posting in the past and it didn’t happen. However, it’s been nearly two years since I wrote here, and a year since I engaged with Twitter in any meaningful way. A lot has happened and some of it is worth putting out into the world.

“Something I Learned Today”

Patrick Rhone reminded me today that not only is it important to remember that learning happens everyday and occurs in a variety of ways, but that it is also important to capture that learning.

A practice I have been doing often for the past couple of years is to write down at least one new thing I learned every day… It is a great reminder that, no matter how old I get, there is always the capacity to learn and grow.

Sometimes, the one thing I learn comes from reading. Sometimes, it comes from observation. Sometimes, it comes from conversation. Sometimes, when I get to the end of the day and can’t think of anything new that I learned, I go to a random page on Wikipedia and learn something for the sake of learning.

This got me thinking about student blogging. I have been using blogs with students for some time now, but with a specific subject focus, e.g.: to capture the coursework process (see the archive and sidebar) in AS and A2 Media Studies. But what if students kept a blog (public or private) with the soul purpose of capturing ‘one new thing’ they learned each day? I personally think it would provide a powerful, personal statement for each student about their learning and progress across the year, free from the constraints of individual subjects and syllabi. So much gets lost in folders and books, relegated to cupboards and bins at the end of the year. A blog would provide a permanent digital record.

Blog Feed Update

Those of you who subscribe to this blog’s RSS feed may have noticed some strange chemistry related posts appearing in the feed. These posts were not written by me and if you navigate to jamesmichie.com/blog via the web you will not find them. I became aware of the problem a few weeks ago and have been trying to rectify it. However, this has not proved successful.

What does this mean? It means that I wil be deleting my FeedBurner feed shortly. If you wish to continue subscribing to this blog you can do so by resubscribing to the following feed address: http://jamesmichie.com/blog/feed; or you can follow me via Twitter where posts are pushed automatically.

Unfortunately, for the small number of you who subscribe via Email, I will be unable to offer this form of subscription for the foreseeable future.

[Update: 03.01.13] Email subscriptions are back up and running thanks to MailChimp’s RSS to Email feature. Click on the following link to subscribe: http://eepurl.com/tAnET.