Some thoughts on modern communications and the boundary between work and play…

This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A few months ago, I wrote a post for the Fujitsu CTO Blog about modern communications. In it, I posited the concept of “service level agreements“ for corporate communications:

“[…] regaining productivity has to be about controlling the interruptions. I suggest closing Outlook. Think of it as an email/calendar client – not the place in which to spend one’s day – and the “toast” that pops up each time a message arrives is a distraction. Even having the application open is a distraction. Dip in 3 times a day, 5 times a day, every hour, or however often is appropriate but emails should not require nor expect an immediate response. Then there’s instant messaging: the name “instant” suggests the response time but presence is a valuable indicator – if my presence is “busy”, then I probably am. Try to contact me if you like but don’t be surprised if I ignore it until a better time. Finally, social networking: which is both a great aid to influencing others and to keeping abreast of developments but can also be what my wife would call a “time-Hoover” – so don’t even think that you can read every message – just dip in from time to time and join the conversation, then leave again.”

I started to think about this again last week. I was on holiday but that doesn’t mean I stopped communicating with my colleagues. I’ll admit it let me be selective in my responses (i.e. there are a lot of things happening at work right now and I answered the messages that were important or interesting to me, leaving many items for my return – after all, I had set an out of office message) but there were a few times when my wife asked me if I was working, as she saw me tapping away on my iPhone…

I maintain that work is something I do, not a place where I go and that, in this day and age (and at my level of responsibility), there is a grey area between work and play so I was enraged when I read an idiotic post about how telecommuting does not work (hello, 1980 is calling… and it wants you back…). Indeed, my “home-base” is one of the things that attracts me to my current role. Getting me back into a 5-day commute to an office that’s probably at least an hour (and maybe two) from home will require some serious persuasion…

So where is the line? Should we all leave the office and stop checking our devices at the end of “the working day”? What about social networking – part of my job is to build a reputation (and therefore enhance my employer’s) as a thought leader – should I ignore something on Twitter because it’s not “work time”? Or should I ignore Twitter, Foursquare, etc. because it is “work time”? Should I be writing this blog post at 8.30pm? But then again, it is on my personal blog… even if a version of the post might eventually appear on a company-owned website…

In the end, I suggest that the answer is about outputs, not inputs. If I’m producing results, my management team should (and, in fairness, probably will) be comfortable, regardless of how many hours I put in. On the flip-side, there are times when I need to work some very long days just to make sure that I can produce those results – and I’ll get frustrated with organisational challenges, non-functioning IT, pointless meetings and disruptive colleagues, just as everyone else does in a modern office environment.

The days of the 9-5 job are long gone (for knowledge workers at least), but so are the 8-6s and even the 8-8s. We live in a 24 hour society – and the new challenge is finding a balance between “work” and “play”.  I’d be interested to hear your thoughts…

From snapshots to social media – the changing picture of photography (@davidfrohlich at #digitalsurrey)

This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

My visits to Surrey seem to be getting more frequent… earlier tonight I was in Reigate, at Canon‘s UK headquarters for another great Digital Surrey talk.

The guest speaker was Professor David Frohlich (@davidfrohlich) from the University of Surrey Digital World Research Centre, who spoke about the changing picture of photography and the relationship between snapshots and social media, three eras of domestic photography, the birth and death of the album and lessons for social media innovation.

I often comment that I have little time for photography these days and all I do is “take snapshots of the kids” but my wife disagrees – she’s far less critical of my work and says I take some good pictures. It was interesting to see a definition of a snapshot though, with it’s origins in 1860’s hunting and “shooting from the hip” (without careful aim!). Later it became “an amateur photograph” so I guess yes, I do mainly take snapshots of the kids!

Professor Frohlich spoke of three values of snapshots (from research by Richard Chalfen in 1987 and Christopher Musello in 1979):

  • Identity.
  • Memory (triggers – not necessarily of when the photograph was taken but of events around that time).
  • Communication.

He then looked at a definition of social media (i.e. it’s a media for social interaction) and suggested that photographs were an early form of social media (since integrated into newer forms)!

Another element to consider is that of innovation and, using Philip Anderson and Michael L Tushman’s 1990 theory as an example, he described how old technological paths hit disruption, there’s then an era of fermentation (i.e. discontinuous development) before a dominant design appears and things stabilise again.  In Geoff Mulgan’s 2007 Process of Social Innovation it’s simply described as new ideas that work, or changing practice (i.e. everyday behaviour).

This led to the discussion of three eras of domestic photography. Following the invention of photography (1830-1840) we saw:

  1. The portrait path [plate images] (1839-1888) including cartes-de-visite (1854-1870)
  2. The Kodak path [roll film] (1888-1990) from the Kodak No. 1 camera in 1888, through the first Polaroid camera (1947), colour film cartridges (1963) which was disrupted with the birth of electronic still video photography (1980-1990)
  3. The digital path (from 1990)

What we find is that the three values of snapshots overlay this perfectly (although the digital era also has elements of identity it is mainly about communication):

Whilst the inventor of the photograph is known (actually Fox-Talbot’s Calotype/Talbottype and Daguerre’s Daguerrotype were both patented in 1839), it’s less well-known who invented the album.

Professor Frohlich explained that the album came into being after people swapped cartes-de-visite (just like today’s photographic business cards!) which became popular around 1850 as a standard portrait sized at 2.5″ x 4″.  These cards could be of individuals, or even famous people (Abraham Lincoln, or Queen Victoria) and in 1854, Disderi’s camera allowed mass production of images with several on a single sheet of paper.  By 1860 albums had been created to store these cards – a development from an earlier past-time of collecting autographs and these albums were effectively filled with images of family, people who visited and famous people – just as Facebook is today!

The Kodak era commenced after George Eastman‘s patent was awarded on 4 September 1888 for a personalised camera which was more accessible, less complex than portrait cameras, and marketed to women around the concept of the Kodak family album.  Filled with images of “high days and holidays” – achievements, celebrations and vacations – these were the albums that most of us know (some of us still maintain) and the concept lasted for the next century (arguably it’s still in existence today, although increasingly marginalised).

Whilst there were some threats (like Polaroid images) they never quite changed the dominant path of photography. Later, as people became more affluent, there were more prints and people built up private archives with many albums and loose photographs (stored in cupboards – just as my many of my family’s are in our loft!).

As photography met ICT infrastructure, the things that we could do with photography expanded but things also became more complex, with a complex mesh involving PCs, printers and digital camera. Whilst some manufacturers cut out the requirement for a computer (with cameras communicating directly to printers), there were two inventions that really changed things: the camera phone and the Internet:

  • Camera phones were already communications-centric (from the phone element), creating a new type of content, that was more about communications than storing memories. In 2002, Turo-Kimmo Lehtonen, Ilpo Koskinen and Esko Kurvine studied the use of mobile digital pictures, not as images for an album but images to say “look where I am”. Whilst technologies such as MMS were not used as much as companies like Nokia expected [largely due to transmission costs imposed by networks] we did see an explosion in online sharing of images.
  • Now we have semi-public sharing, with our friends on Facebook (Google+, etc.) and even wider distribution on Flickr. In addition, photographs have become multimedia objects and Professor Frohlich experimented with adding several types of audio to still images in 2004 as digital story telling.

By 2008, Abigail Durrant was researching photographic displays and intergenerational relationships at home. She looked at a variety of display devices but, critically, found that there was a requirement for some kind of agreement as to what could be displayed where (some kind of meta rules for display).

Looking to the future there are many developments taking place that move beyond the album and on to the archive. Nowadays we have home media collections – could we end up browsing beautiful ePaper books that access our libraries?Could we even see the day where photographic images have a “birthday” and prompt us to remember things (e.g. do you remember when this image was taken, 3 years ago today?)

Professor Frohlich finished up with some lessons for social media innovation:

  • Innovation results from the interaction of four factors: practice; technology; business; and design.
  • Business positioning and social shaping are as important to innovation as technology and it’s design.
  • Social media evolve over long periods of time (so don’t give up if something doesn’t happen quickly).
  • Features change faster than practices and values (social networking is a partial return to identity – e.g. tagging oneself – and not just about communications).
  • Some ideas come around again (like the stereograph developing into 3D cinema).
  • Infrastructure and standards are increasingly key to success (for example, a standard image size).

I do admit to being in admiration of the Digital Surrey team for organising these events – in my three visits I’ve seen some great speakers. Hopefully, I’ve covered the main points from this event but Andy Piper (@andypiper) sums it up for me in a single tweet:

 

Some thoughts on modern communications and avoiding the “time-Hoover”

This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Last week I was reading an article by Shelley Portet looking at how poor productivity and rudeness are influenced by technology interruptions at work. As someone who’s just managed to escape from email jail yet again (actually, I’m on parole – my inbox may finally be at zero but I still have hundreds of items requiring action) I have to say that, despite all the best intentions, experience shows that I’m a repeat offender, an habitual email mis-manager – and email is just the tip of the proverbial iceberg.

Nowadays email is just one of many forms of communication: there’s instant messaging; “web 2.0″ features on intranet sites (blogs, wikis, discussion forums); our internal social networking platform; business and personal use of external social networks (Twitter, LinkedIn, Slideshare, YouTube, Facebook… the list goes on) – so how can we prepare our knowledge workers for dealing with this barrage of interruptions?

There are various schools of thought on email management and I find that Merlin Mann’s Inbox Zero principles work well (see this video from Merlin Mann’s Google Tech Talk using these slides on action-based email – or flick through the Michael Reynolds version for the highlights), as long as one always manages to process to zero (that’s the tricky part that lands me back in email jail).

The trouble is that Inbox Zero only deals with the manifestation of the problem, not the root cause: people. Why do we send these messages? And how do we act on them?

A couple of colleagues have suggested recently that the trouble with email is that people confuse sending an email with completing an action as if, somehow, the departure of the message from someone’s outbox on its way to someone else’s inbox implies a transfer of responsibility. Except that it doesn’t – there are many demands on my colleagues’ time and it’s up to me to ensure that we’re all working towards a common goal. I can help by making my expectations clear; I can think carefully before carbon copying or replying to all; I can make sure I’m brief and to the point (but not ambiguous) – but those are all items of email etiquette. They don’t actually help to reduce the volumes of messages sent and received. Incidentally, I’m using email as an example here – many of the issues are common whatever the communications medium (back to handwritten letters and typed memos as well as forwards to social networking) but, ultimately I’m either trying to:

  • Inform someone that something has happened, will soon happen, or otherwise communicate something on a need to know basis.
  • Request that someone takes an action on something.
  • Confirm something that has been agreed via another medium (perhaps a telephone call), often for audit purposes.

I propose two courses of action, both of which involve setting the expectations of others:

  1. The first is to stop thinking of every message as requiring a response. Within my team at work, we have some unwritten rules that: gratefulness is implied within the team (not to fill each others’ inboxes with messages that say “thank you”); carbon copy means “for information”; and single-line e-mails can be dealt with in the subject heading.
  2. The second can be applied far more widely and that’s the concept of “service level agreements” for corporate communications. I don’t mean literally, of course, but regaining productivity has to be about controlling the interruptions. I suggest closing Outlook. Think of it as an email/calendar client – not the place in which to spend one’s day – and the “toast” that pops up each time a message arrives is a distraction. Even having the application open is a distraction. Dip in 3 times a day, 5 times a day, every hour, or however often is appropriate but emails should not require nor expect an immediate response. Then there’s instant messaging: the name “instant” suggests the response time but presence is a valuable indicator – if my presence is “busy”, then I probably am. Try to contact me if you like but don’t be surprised if I ignore it until a better time. Finally, social networking: which is both a great aid to influencing others and to keeping abreast of developments but can also be what my wife would call a “time-Hoover” – so don’t even think that you can read every message – just dip in from time to time and join the conversation, then leave again.

Ultimately, neither of these proposals will be successful without cultural change. This issue is not unique to any one company but the only way I can think of to change the actions and/or thoughts of others is to lead by example… starting today, I think I might give them a try.

[This post originally appeared on the Fujitsu UK and Ireland CTO Blog.]

Finding your Twitter RSS feed

This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Unlike many people, I quite like “new” Twitter (although it doesn’t seem that new any more!) – compared with “old” Twitter, the website is far more usable but it did lose one item of functionality – that of finding the RSS feed for your Twitterstream.

For those who think RSS is dead – it’s not dead – it’s just not something we have to think about too often (like HTTP) and (just like HTTP) it’s still a very useful technology. I think I once saw a response from Twitter that suggested browsers can identify RSS feeds in pages now, but all that seems to turn up is a feed of my favourites.

Anyway, Twitter came to my rescue on this one – not the website/API people, but the people who follow me (thanks guys).  And then I saw the same question asked again today, so I thought I should blog the answer.

Your Twitter stream is available at http://twitter.com/statuses/user_timeline/twitteruserid.rss.

So how do you get your Twitter user ID? Well, there’s a website that will help to get a Twitter ID from a username and your Twitter user number is also available in the properties displayed for your user on many Twitter clients. For me it’s 56967616 so my Twitter stream is at http://twitter.com/statuses/user_timeline/56967616.rss.

Why paper.li is just plain wrong

This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

When I first saw paper.lilast year, I thought it was an interesting concept. Kind of like the Flipboard app on my iPad, although nowhere near as attractive, but universally available, picking the most popular updates from my Twitter and Facebook “friends” and presenting them to me in a newspaper format. I quickly grew tired of the format though along with the increasing number of tweets telling me that “The Daily<insert name of person> is out” – I can see the value for an individual but tweeting about it just seems a bit spammy. (Sorry if you’re one of the people that does this – if you think there is some real value, I’d be pleased to hear your view.)

More worrying though is the way that paper.li seems to misrepresent my views and opinions when it “retweets” me…

I work for a Japanese company and spent a lot of Friday and the weekend thinking of colleagues whose friends and family might be affected by the recent events in Japan. For that reason, I was appalled to see a ZD Net article last Friday questioning whether the iPad 2 would be hit by supply problems as a consequence.

I can see why the writer/publisher put this out (perhaps it is a legitimate concern for some) but really, in the big scheme of things, does a shortage of NAND memory matter that much, given the scale of the human disaster in Japan?  Any iPad 2 supply chain issues strike me as a “first world problem” and, even though the earthquake/tsunami did strike on iPad 2 launch day (presumably why this was newsworthy to ZD Net), couldn’t the publisher have held back, if only for reasons of taste and decency? I tweeted:

RT @ZDNet: Will the earthquake in Japan ding Apple’s iPad 2 rollout? http://zd.net/ibvmgp ^MW FFS get a grip. Bigger issues at stake here!

(If you’re not familiar with the FFS acronym, don’t worry, I was just expressing my frustration.)

I think that tweet is pretty clear, I’m RT (retweeting) ZD Net’s tweet about their article, with a comment – in the socially-acceptable manner for the Twitter community (the “new-style” RT built into Twitter misses the ability/potential added value of a comment).

Unfortunately, when I saw paper.li’s version, it was completely out of context:

Paper.li appearing to credit me with a ZDNet article about iPad 2 delays following the Japanese earthquake/tsunami (and with which I disagree!)

It simply grabs the title and first few lines from the link and credits the person who retweeted it (me) as the source. Not only does this appear to be crediting me as the author of the article, which I would be uncomfortable with, even if I did approve of the content but, in this case, I fundamentally disagree with the article and would certainly not want to be associated with it. 

Paper.li does include the ability to stop mentions, but that misses the point – by all means mention my tweets but they should really make it clear who the original source of an article is and, where that’s not possible, include the whole tweet to ensure that it remains in context.

And it seems I’m not the only one to see issues with the way in which Paper.li uses the Twitter API, disregarding the social networking element of Twitter. Then there’s the fact that some people thank others for mentioning them in their paper.li edition (which, of course, was entirely automated).

Indeed, I’d go as far as to say that the way paper.li handles retweets is sloppy and demonstrates a lack of knowledge/understanding on how platforms like Twitter really work – they are (or should be) about conversation, not broadcast – and that’s why the newspaper format is really not a good fit.

Restoring the link between Twitter and Facebook status updates

This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I make no secret of the fact that I detest Facebook.  I despise its user interface (which I find confusing and difficult to navigate).  I find Facebook’s approach to security and privacy concerning. And I’m much happier with a single web of sites than one that consists of several huge islands – even if one of those islands currently has around 600 million users.

Unfortunately, normal (i.e. non-geek/media) people, including many of my friends and family, insist on using Facebook, so I have an account there.  Actually, until earlier this week, I had two (one personal, one professional) - then I learned that was in violation of Facebook’s terms of service and, if detected, Facebook reserves the right to terminate all of your accounts, so I deleted one of them.

Because I dislike Facebook so intensely, I’m not a great citizen there – I log in from time to time, and that means that I don’t really participate in the network properly.  My Facebook status updates are populated from my personal Twitter account and I recieve e-mail updates on any comments. But recently, I noticed that the Twitter Facebook app was not updating my Facebook status and several of my friends were having the same problem.

I tried denying the app access to my Twitter account and then allowing it again, but that didn’t seem to work. Then I found a Facebook discussion thread, where Derek Lau wrote:

“Go to http://apps.facebook.com/twitter/
Uncheck the box that says ‘Allow Twitter to post updates to: Facebook Profile’
Refresh the page to make sure that the box really is unchecked.
When the box is unchecked, send a tweet. This will obviously not get posted to FB.
Go back and re-check the box. Refresh the page to make sure it is really checked.
Now send another tweet.”

Twitter app on Facebook

Sweet. Now my Twitter updates are populating Facebook again, and I can go back to ignoring it for a while longer…

Adding a Facebook Share (or Like) button to a self-hosted WordPress blog

This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A few weeks ago, I wrote about adding a Tweet button to a self-hosted WordPress blog, and followed up by writing about using a little CSS trickery to align the Tweet button (thanks to Alex Coles).  Whilst I was implementing the Tweet Button, I also went about putting a Facebook Share button on each post.

There are plug-ins to do this for me but why use a plugin when the answer is just a single lines of code in two files within the template?

In the same paragraph as the Tweet button (i.e. styled with the same class), I used this code, generated using the Facebook Share Button generator:

This time, the code is identical for both index.php and single.php as, unfortunately, Facebook doesn’t seem to give me any control over the title of the link (it just takes the </code> tag from the page). <a href="http://askville.amazon.com/add-Share-Facebook-button-webpage/AnswerViewer.do?requestId=1539369">There is another method, using query string parameters in the URL</a> but I chose to stick with Facebook’s recommended method.</p> <p>Incidentally, I chose to Share, rather than <a href="http://developers.facebook.com/docs/reference/plugins/like">Like (which can be implemented by following these guidelines)</a> because they have subtly different purposes and <a href="http://daggle.com/facebook-button-facebook-share-keeping-1792">each is represented in a slightly different manner (as Danny Sullivan describes in his post on the subject)</a>. After reading Danny’s post, I agree that Share is best for linking to a single post, whilst Like is more suited to the site as a whole (someone might <em>Like</em> markwilson.it and <em>Share</em> one or more posts from the site).</p> </div><!-- .entry-content --> <footer class="entry-footer"> <span class="cat-links">Posted in Uncategorised</span><span class="tags-links">Tagged <a href="https://www.markwilson.co.uk/blog/tag/social-networking" rel="tag">Social Networking</a>, <a href="https://www.markwilson.co.uk/blog/tag/wordpress" rel="tag">WordPress</a></span><span class="comments-link"><a href="https://www.markwilson.co.uk/blog/2010/09/adding-a-facebook-share-or-like-button-to-a-self-hosted-wordpress-blog.htm#respond">Leave a comment</a></span> </footer><!-- .entry-footer --> </article><!-- #post-## --> <article id="post-1979" class="post-1979 post type-post status-publish format-standard hentry tag-social-networking tag-wordpress"> <header class="entry-header"> <h2 class="entry-title"><a href="https://www.markwilson.co.uk/blog/2010/08/more-on-implementing-twitters-tweet-button.htm" rel="bookmark">More on implementing Twitter’s Tweet button</a></h2> <div class="entry-meta"> <span class="posted-on">Posted on <a href="https://www.markwilson.co.uk/blog/2010/08/more-on-implementing-twitters-tweet-button.htm" rel="bookmark"><time class="entry-date published" datetime="2010-08-26T18:51:56+01:00">Thursday 26 August 2010</time></a></span><span class="byline"> By <span class="author vcard"><a class="url fn n" href="https://www.markwilson.co.uk/blog/author/mark-wilson">Mark Wilson</a></span></span> </div><!-- .entry-meta --> </header><!-- .entry-header --> <a class="post-thumbnail" href="https://www.markwilson.co.uk/blog/2010/08/more-on-implementing-twitters-tweet-button.htm"> </a> <div class="entry-content"> <div class="juiz-outdated-message jodpm-top">This content is 15 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.</div><p>A week or so back, I wrote about <a href="http://www.markwilson.co.uk/blog/2010/08/adding-a-tweet-button-to-a-self-hosted-wordpress-blog.htm">putting a Tweet button onto a self-hosted WordPress blog</a>. The method I used was fine – it works – but I was struggling to place the button within my page (I knew where to put it in my code but it seemed to display in the wrong place sometimes, as a result of some of the floats that the stylesheet applies).</p> <p>That’s when I called in my buddy <a href="http://www.alexcoles.com/">Alex</a>: XHTML and CSS wizard; and fixer of many things on this site.</p> <p>He spotted that, even though <a href="http://dev.twitter.com/pages/tweet-button">Twitter gives us three options for implementing the Tweet button: JavaScript, IFrame, and roll your own</a>, the <a href="http://platform.twitter.com/widgets.js">JavaScript implementation</a> also uses an IFrame.</p> <p>The trouble with this is that IFrames are bad. Well, not really bad, but certainly deprecated for Strict HTML and XHTML, and certainly not the direction I want to be heading in for a compliant site. Ideally, I would find another way around the issue but rolling my own Tweet button doesn’t look great) and Twitter’s implementation uses several images in one file, just showing the appropriate section of the image. I could use this, with image replacement techniques for hover and click (which is what Twitter do) but, to be honest, that was a little out of my league, so IFrames it is…</p> <p>Alex helped me style up the button – if you want to do something similar, this was the CSS that he used:</p> <p><dirtycode:noclick>p.social-media {margin-top: -15px;}<br /> iframe.twitter-share-button {float: left; margin-right: 1em;}</dirtycode></p> <p>Together with adding <code>class="social-media"</code> to the <code></p> <p></code> tag in the code to display the tweet button so that it now reads:</p> <p><dirtycode:noclick></p> <p class="social-media"><a href="http://twitter.com/share" class="twitter-share-button" data-url="<?php the_permalink(); ?>” data-text=”<?php the_title(); ?>” data-count=”none” data-via=”markwilsonit”>Tweet</a><script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script></p> <p></dirtycode></p> <p>When I asked him how this works, he explained that the class on the <code></p> <p></code> is just to close up the top margin; the real magic is floating just the Tweet button (which cured the CSS float issues that had been frustrating me).</p> <p>Of course, there may be plugins to display buttons like Tweet, Facebook Share/Like, etc. but when something only takes a couple of lines of code, I’d rather implement it natively than add to the list of plugins running on my WordPress installation.</p> </div><!-- .entry-content --> <footer class="entry-footer"> <span class="cat-links">Posted in Uncategorised</span><span class="tags-links">Tagged <a href="https://www.markwilson.co.uk/blog/tag/social-networking" rel="tag">Social Networking</a>, <a href="https://www.markwilson.co.uk/blog/tag/wordpress" rel="tag">WordPress</a></span><span class="comments-link"><a href="https://www.markwilson.co.uk/blog/2010/08/more-on-implementing-twitters-tweet-button.htm#respond">Leave a comment</a></span> </footer><!-- .entry-footer --> </article><!-- #post-## --> <article id="post-1972" class="post-1972 post type-post status-publish format-standard hentry tag-social-networking tag-wordpress"> <header class="entry-header"> <h2 class="entry-title"><a href="https://www.markwilson.co.uk/blog/2010/08/adding-a-tweet-button-to-a-self-hosted-wordpress-blog.htm" rel="bookmark">Adding a Tweet button to a self-hosted WordPress blog</a></h2> <div class="entry-meta"> <span class="posted-on">Posted on <a href="https://www.markwilson.co.uk/blog/2010/08/adding-a-tweet-button-to-a-self-hosted-wordpress-blog.htm" rel="bookmark"><time class="entry-date published" datetime="2010-08-13T11:59:34+01:00">Friday 13 August 2010</time><time class="updated" datetime="2010-08-14T15:06:47+01:00">Saturday 14 August 2010</time></a></span><span class="byline"> By <span class="author vcard"><a class="url fn n" href="https://www.markwilson.co.uk/blog/author/mark-wilson">Mark Wilson</a></span></span> </div><!-- .entry-meta --> </header><!-- .entry-header --> <a class="post-thumbnail" href="https://www.markwilson.co.uk/blog/2010/08/adding-a-tweet-button-to-a-self-hosted-wordpress-blog.htm"> </a> <div class="entry-content"> <div class="juiz-outdated-message jodpm-top">This content is 15 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.</div><p>Yesterday, Twitter launched their official button for websites and keen-eyed observers will have noticed that markwilson.it now sports a shiny new “tweet” icon at the head of each post.  It’s pretty easy to do (<a href="http://twitter.com/goodies/tweetbutton">Twitter generates the code for you</a> – and has an <a href="http://dev.twitter.com/pages/tweet_button_faq">FAQ for developers</a>) but there may be a couple of things to watch out for, <a href="http://mashable.com/2010/08/13/tweet-button-bloggers/">depending on your blog’s content management system</a>.</p> <p>I use self-hosted WordPress, and these were the changes I made to the site:</p> <ul> <li>For my single posts, I just added the Twitter-generated code to an appropriate position in the single.php file.</li> <li>For my main index page, I edited index.php, but didn’t want the generated link to be to the current page (my home page with several recent posts) – I wanted it to relate to the particular post that the viewer is tweeting from.  Adapting a tip from <a href="http://www.davidteng.com/">David Teng</a>, I added two parameters to the link code (<code>data-url="<?php the_permalink(); ?>"</code> and <code>data-text="<?php the_title(); ?>"</code>).</li> </ul> <p>Now, by clicking the Tweet button on this post, the link generated relates to the post – and not the home page for the blog.</p> </div><!-- .entry-content --> <footer class="entry-footer"> <span class="cat-links">Posted in Uncategorised</span><span class="tags-links">Tagged <a href="https://www.markwilson.co.uk/blog/tag/social-networking" rel="tag">Social Networking</a>, <a href="https://www.markwilson.co.uk/blog/tag/wordpress" rel="tag">WordPress</a></span><span class="comments-link"><a href="https://www.markwilson.co.uk/blog/2010/08/adding-a-tweet-button-to-a-self-hosted-wordpress-blog.htm#comments">2 Comments</a></span> </footer><!-- .entry-footer --> </article><!-- #post-## --> <article id="post-1957" class="post-1957 post type-post status-publish format-standard hentry tag-social-networking"> <header class="entry-header"> <h2 class="entry-title"><a href="https://www.markwilson.co.uk/blog/2010/08/it-tweet-up-number-5-ittu5.htm" rel="bookmark">IT Tweet Up number 5 (#ITTU5)</a></h2> <div class="entry-meta"> <span class="posted-on">Posted on <a href="https://www.markwilson.co.uk/blog/2010/08/it-tweet-up-number-5-ittu5.htm" rel="bookmark"><time class="entry-date published" datetime="2010-08-06T11:30:40+01:00">Friday 6 August 2010</time><time class="updated" datetime="2010-08-06T11:37:53+01:00">Friday 6 August 2010</time></a></span><span class="byline"> By <span class="author vcard"><a class="url fn n" href="https://www.markwilson.co.uk/blog/author/mark-wilson">Mark Wilson</a></span></span> </div><!-- .entry-meta --> </header><!-- .entry-header --> <a class="post-thumbnail" href="https://www.markwilson.co.uk/blog/2010/08/it-tweet-up-number-5-ittu5.htm"> </a> <div class="entry-content"> <div class="juiz-outdated-message jodpm-top">This content is 15 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.</div><p>Next week sees the latest in the series of “tweet-ups” that have been running every few months for UK-based IT professionals to meet up over a drink and a bite to eat.</p> <p>This time, the venue has changed – someone didn’t like the toasties in Ye Olde Mitre so we’ve moved to the Melton Mowbray pub in London (make sure you get that the right way around – this is nothing to do with pork pies in Leicestershire) but you can register your interest and get directions on the ‘net. Hopefully I’ll see you there.<script src="http://twtvite.com/js/badge.js" type="text/javascript"></script><script src="http://twtvite.com/badge/?twt=ittu5" type="text/javascript"></script></p> </div><!-- .entry-content --> <footer class="entry-footer"> <span class="cat-links">Posted in Uncategorised</span><span class="tags-links">Tagged <a href="https://www.markwilson.co.uk/blog/tag/social-networking" rel="tag">Social Networking</a></span><span class="comments-link"><a href="https://www.markwilson.co.uk/blog/2010/08/it-tweet-up-number-5-ittu5.htm#comments">1 Comment</a></span> </footer><!-- .entry-footer --> </article><!-- #post-## --> <nav class="navigation paging-navigation" role="navigation"> <h2 class="screen-reader-text">Posts navigation</h2> <div class="nav-links"> <div class="nav-previous"> <a href="https://www.markwilson.co.uk/blog/tag/social-networking/page/4" ><span class="meta-nav">←</span> Older posts</a> </div> <div class="nav-next"> <a href="https://www.markwilson.co.uk/blog/tag/social-networking/page/2" >Newer posts <span class="meta-nav">→</span></a> </div> </div><!-- .nav-links --> </nav><!-- .navigation --> </main><!-- #main --> </div><!-- #primary --> <div id="secondary" class="widget-area" role="complementary"> <aside id="search-4" class="widget widget_search"><form role="search" method="get" class="search-form" action="https://www.markwilson.co.uk/blog/"> <label> <span class="screen-reader-text">Search for:</span> <input type="search" class="search-field" placeholder="Search …" value="" name="s" /> </label> <input type="submit" class="search-submit" value="Search" /> </form></aside><aside id="categories-2" class="widget widget_categories"><h2 class="widget-title">Categories</h2> <ul> <li class="cat-item cat-item-768"><a href="https://www.markwilson.co.uk/blog/topic/business">Business</a> </li> <li class="cat-item cat-item-364"><a href="https://www.markwilson.co.uk/blog/topic/exercise">Exercise</a> </li> <li class="cat-item cat-item-697"><a href="https://www.markwilson.co.uk/blog/topic/lifestyle">Lifestyle</a> </li> <li class="cat-item cat-item-117"><a href="https://www.markwilson.co.uk/blog/topic/motoring">Motoring</a> </li> <li class="cat-item cat-item-764"><a href="https://www.markwilson.co.uk/blog/topic/music">Music</a> </li> <li class="cat-item cat-item-152"><a href="https://www.markwilson.co.uk/blog/topic/photography">Photography</a> </li> <li class="cat-item cat-item-838"><a href="https://www.markwilson.co.uk/blog/topic/published-elsewhere">Published elsewhere</a> </li> <li class="cat-item cat-item-811"><a href="https://www.markwilson.co.uk/blog/topic/retrospectives">Retrospectives</a> </li> <li class="cat-item cat-item-840"><a href="https://www.markwilson.co.uk/blog/topic/short-takes">Short takes</a> </li> <li class="cat-item cat-item-6"><a href="https://www.markwilson.co.uk/blog/topic/site-notices">Site notices</a> </li> <li class="cat-item cat-item-218"><a href="https://www.markwilson.co.uk/blog/topic/technology">Technology</a> </li> <li class="cat-item cat-item-758"><a href="https://www.markwilson.co.uk/blog/topic/travel">Travel</a> </li> <li class="cat-item cat-item-38"><a href="https://www.markwilson.co.uk/blog/topic/inane-waffle">Waffle and randomness</a> </li> <li class="cat-item cat-item-666"><a href="https://www.markwilson.co.uk/blog/topic/weeknotes">Weeknotes</a> </li> </ul> </aside><aside id="archives-2" class="widget widget_archive"><h2 class="widget-title">Archives</h2> <label class="screen-reader-text" for="archives-dropdown-2">Archives</label> <select id="archives-dropdown-2" name="archive-dropdown"> <option value="">Select Month</option> <option value='https://www.markwilson.co.uk/blog/2025/01'> January 2025  (3)</option> <option value='https://www.markwilson.co.uk/blog/2024/12'> December 2024  (1)</option> <option value='https://www.markwilson.co.uk/blog/2024/11'> November 2024  (5)</option> <option value='https://www.markwilson.co.uk/blog/2024/10'> October 2024  (1)</option> <option value='https://www.markwilson.co.uk/blog/2024/09'> September 2024  (3)</option> <option value='https://www.markwilson.co.uk/blog/2024/08'> August 2024  (4)</option> <option value='https://www.markwilson.co.uk/blog/2024/07'> July 2024  (1)</option> <option value='https://www.markwilson.co.uk/blog/2024/06'> June 2024  (2)</option> <option value='https://www.markwilson.co.uk/blog/2024/05'> May 2024  (2)</option> <option value='https://www.markwilson.co.uk/blog/2024/04'> April 2024  (2)</option> <option value='https://www.markwilson.co.uk/blog/2024/03'> March 2024  (1)</option> <option value='https://www.markwilson.co.uk/blog/2024/02'> February 2024  (6)</option> <option value='https://www.markwilson.co.uk/blog/2024/01'> January 2024  (7)</option> <option value='https://www.markwilson.co.uk/blog/2023/12'> December 2023  (2)</option> <option value='https://www.markwilson.co.uk/blog/2023/11'> November 2023  (2)</option> <option value='https://www.markwilson.co.uk/blog/2023/10'> October 2023  (2)</option> <option value='https://www.markwilson.co.uk/blog/2023/07'> July 2023  (2)</option> <option value='https://www.markwilson.co.uk/blog/2023/06'> June 2023  (1)</option> <option value='https://www.markwilson.co.uk/blog/2023/04'> April 2023  (1)</option> <option value='https://www.markwilson.co.uk/blog/2023/03'> March 2023  (1)</option> <option value='https://www.markwilson.co.uk/blog/2023/01'> January 2023  (1)</option> <option value='https://www.markwilson.co.uk/blog/2022/12'> December 2022  (1)</option> <option value='https://www.markwilson.co.uk/blog/2022/09'> September 2022  (2)</option> <option value='https://www.markwilson.co.uk/blog/2022/08'> August 2022  (1)</option> <option value='https://www.markwilson.co.uk/blog/2022/06'> June 2022  (2)</option> <option value='https://www.markwilson.co.uk/blog/2022/05'> May 2022  (1)</option> <option value='https://www.markwilson.co.uk/blog/2022/04'> April 2022  (1)</option> <option value='https://www.markwilson.co.uk/blog/2022/01'> January 2022  (1)</option> <option value='https://www.markwilson.co.uk/blog/2021/12'> December 2021  (1)</option> <option value='https://www.markwilson.co.uk/blog/2021/11'> November 2021  (1)</option> <option value='https://www.markwilson.co.uk/blog/2021/10'> October 2021  (1)</option> <option value='https://www.markwilson.co.uk/blog/2021/09'> September 2021  (7)</option> <option value='https://www.markwilson.co.uk/blog/2021/08'> August 2021  (1)</option> <option value='https://www.markwilson.co.uk/blog/2021/07'> July 2021  (2)</option> <option value='https://www.markwilson.co.uk/blog/2021/06'> June 2021  (2)</option> <option value='https://www.markwilson.co.uk/blog/2021/05'> May 2021  (2)</option> <option value='https://www.markwilson.co.uk/blog/2021/04'> April 2021  (5)</option> <option value='https://www.markwilson.co.uk/blog/2021/03'> March 2021  (6)</option> <option value='https://www.markwilson.co.uk/blog/2021/02'> February 2021  (2)</option> <option value='https://www.markwilson.co.uk/blog/2021/01'> January 2021  (1)</option> <option value='https://www.markwilson.co.uk/blog/2020/12'> December 2020  (4)</option> <option value='https://www.markwilson.co.uk/blog/2020/11'> November 2020  (1)</option> <option value='https://www.markwilson.co.uk/blog/2020/09'> September 2020  (1)</option> <option value='https://www.markwilson.co.uk/blog/2020/08'> August 2020  (2)</option> <option value='https://www.markwilson.co.uk/blog/2020/07'> July 2020  (1)</option> <option value='https://www.markwilson.co.uk/blog/2020/06'> June 2020  (2)</option> <option value='https://www.markwilson.co.uk/blog/2020/05'> May 2020  (6)</option> <option value='https://www.markwilson.co.uk/blog/2020/04'> April 2020  (7)</option> <option value='https://www.markwilson.co.uk/blog/2020/03'> March 2020  (2)</option> <option value='https://www.markwilson.co.uk/blog/2020/02'> February 2020  (1)</option> <option value='https://www.markwilson.co.uk/blog/2020/01'> January 2020  (1)</option> <option value='https://www.markwilson.co.uk/blog/2019/12'> December 2019  (1)</option> <option value='https://www.markwilson.co.uk/blog/2019/11'> November 2019  (2)</option> <option value='https://www.markwilson.co.uk/blog/2019/10'> October 2019  (1)</option> <option value='https://www.markwilson.co.uk/blog/2019/09'> September 2019  (1)</option> <option value='https://www.markwilson.co.uk/blog/2019/08'> August 2019  (1)</option> <option value='https://www.markwilson.co.uk/blog/2019/07'> July 2019  (1)</option> <option value='https://www.markwilson.co.uk/blog/2019/06'> June 2019  (1)</option> <option value='https://www.markwilson.co.uk/blog/2019/05'> May 2019  (1)</option> <option value='https://www.markwilson.co.uk/blog/2019/04'> April 2019  (2)</option> <option value='https://www.markwilson.co.uk/blog/2019/03'> March 2019  (1)</option> <option value='https://www.markwilson.co.uk/blog/2019/02'> February 2019  (1)</option> <option value='https://www.markwilson.co.uk/blog/2019/01'> January 2019  (1)</option> <option value='https://www.markwilson.co.uk/blog/2018/12'> December 2018  (1)</option> <option value='https://www.markwilson.co.uk/blog/2018/11'> November 2018  (1)</option> <option value='https://www.markwilson.co.uk/blog/2018/10'> October 2018  (1)</option> <option value='https://www.markwilson.co.uk/blog/2018/09'> September 2018  (1)</option> <option value='https://www.markwilson.co.uk/blog/2018/08'> August 2018  (1)</option> <option value='https://www.markwilson.co.uk/blog/2018/07'> July 2018  (2)</option> <option value='https://www.markwilson.co.uk/blog/2018/06'> June 2018  (4)</option> <option value='https://www.markwilson.co.uk/blog/2018/05'> May 2018  (3)</option> <option value='https://www.markwilson.co.uk/blog/2018/04'> April 2018  (3)</option> <option value='https://www.markwilson.co.uk/blog/2018/03'> March 2018  (2)</option> <option value='https://www.markwilson.co.uk/blog/2018/02'> February 2018  (4)</option> <option value='https://www.markwilson.co.uk/blog/2018/01'> January 2018  (1)</option> <option value='https://www.markwilson.co.uk/blog/2017/12'> December 2017  (4)</option> <option value='https://www.markwilson.co.uk/blog/2017/11'> November 2017  (4)</option> <option value='https://www.markwilson.co.uk/blog/2017/10'> October 2017  (5)</option> <option value='https://www.markwilson.co.uk/blog/2017/09'> September 2017  (5)</option> <option value='https://www.markwilson.co.uk/blog/2017/08'> August 2017  (6)</option> <option value='https://www.markwilson.co.uk/blog/2017/07'> July 2017  (12)</option> <option value='https://www.markwilson.co.uk/blog/2017/06'> June 2017  (2)</option> <option value='https://www.markwilson.co.uk/blog/2017/05'> May 2017  (4)</option> <option value='https://www.markwilson.co.uk/blog/2017/04'> April 2017  (3)</option> <option value='https://www.markwilson.co.uk/blog/2017/03'> March 2017  (7)</option> <option value='https://www.markwilson.co.uk/blog/2017/02'> February 2017  (7)</option> <option value='https://www.markwilson.co.uk/blog/2017/01'> January 2017  (14)</option> <option value='https://www.markwilson.co.uk/blog/2016/12'> December 2016  (13)</option> <option value='https://www.markwilson.co.uk/blog/2016/11'> November 2016  (11)</option> <option value='https://www.markwilson.co.uk/blog/2016/10'> October 2016  (6)</option> <option value='https://www.markwilson.co.uk/blog/2016/09'> September 2016  (11)</option> <option value='https://www.markwilson.co.uk/blog/2016/08'> August 2016  (6)</option> <option value='https://www.markwilson.co.uk/blog/2016/07'> July 2016  (3)</option> <option value='https://www.markwilson.co.uk/blog/2016/06'> June 2016  (2)</option> <option value='https://www.markwilson.co.uk/blog/2016/05'> May 2016  (11)</option> <option value='https://www.markwilson.co.uk/blog/2016/04'> April 2016  (4)</option> <option value='https://www.markwilson.co.uk/blog/2016/03'> March 2016  (7)</option> <option value='https://www.markwilson.co.uk/blog/2016/02'> February 2016  (3)</option> <option value='https://www.markwilson.co.uk/blog/2016/01'> January 2016  (5)</option> <option value='https://www.markwilson.co.uk/blog/2015/12'> December 2015  (3)</option> <option value='https://www.markwilson.co.uk/blog/2015/11'> November 2015  (10)</option> <option value='https://www.markwilson.co.uk/blog/2015/10'> October 2015  (16)</option> <option value='https://www.markwilson.co.uk/blog/2015/09'> September 2015  (30)</option> <option value='https://www.markwilson.co.uk/blog/2015/08'> August 2015  (17)</option> <option value='https://www.markwilson.co.uk/blog/2015/07'> July 2015  (15)</option> <option value='https://www.markwilson.co.uk/blog/2015/06'> June 2015  (5)</option> <option value='https://www.markwilson.co.uk/blog/2015/05'> May 2015  (11)</option> <option value='https://www.markwilson.co.uk/blog/2015/04'> April 2015  (8)</option> <option value='https://www.markwilson.co.uk/blog/2015/03'> March 2015  (5)</option> <option value='https://www.markwilson.co.uk/blog/2015/02'> February 2015  (6)</option> <option value='https://www.markwilson.co.uk/blog/2015/01'> January 2015  (2)</option> <option value='https://www.markwilson.co.uk/blog/2014/12'> December 2014  (4)</option> <option value='https://www.markwilson.co.uk/blog/2014/11'> November 2014  (4)</option> <option value='https://www.markwilson.co.uk/blog/2014/10'> October 2014  (9)</option> <option value='https://www.markwilson.co.uk/blog/2014/09'> September 2014  (3)</option> <option value='https://www.markwilson.co.uk/blog/2014/08'> August 2014  (3)</option> <option value='https://www.markwilson.co.uk/blog/2014/07'> July 2014  (5)</option> <option value='https://www.markwilson.co.uk/blog/2014/06'> June 2014  (7)</option> <option value='https://www.markwilson.co.uk/blog/2014/05'> May 2014  (2)</option> <option value='https://www.markwilson.co.uk/blog/2014/04'> April 2014  (4)</option> <option value='https://www.markwilson.co.uk/blog/2014/03'> March 2014  (6)</option> <option value='https://www.markwilson.co.uk/blog/2014/02'> February 2014  (7)</option> <option value='https://www.markwilson.co.uk/blog/2014/01'> January 2014  (6)</option> <option value='https://www.markwilson.co.uk/blog/2013/12'> December 2013  (4)</option> <option value='https://www.markwilson.co.uk/blog/2013/11'> November 2013  (5)</option> <option value='https://www.markwilson.co.uk/blog/2013/10'> October 2013  (4)</option> <option value='https://www.markwilson.co.uk/blog/2013/09'> September 2013  (5)</option> <option value='https://www.markwilson.co.uk/blog/2013/08'> August 2013  (1)</option> <option value='https://www.markwilson.co.uk/blog/2013/07'> July 2013  (9)</option> <option value='https://www.markwilson.co.uk/blog/2013/06'> June 2013  (3)</option> <option value='https://www.markwilson.co.uk/blog/2013/05'> May 2013  (8)</option> <option value='https://www.markwilson.co.uk/blog/2013/04'> April 2013  (2)</option> <option value='https://www.markwilson.co.uk/blog/2013/03'> March 2013  (9)</option> <option value='https://www.markwilson.co.uk/blog/2013/02'> February 2013  (8)</option> <option value='https://www.markwilson.co.uk/blog/2013/01'> January 2013  (12)</option> <option value='https://www.markwilson.co.uk/blog/2012/12'> December 2012  (8)</option> <option value='https://www.markwilson.co.uk/blog/2012/11'> November 2012  (16)</option> <option value='https://www.markwilson.co.uk/blog/2012/10'> October 2012  (18)</option> <option value='https://www.markwilson.co.uk/blog/2012/09'> September 2012  (7)</option> <option value='https://www.markwilson.co.uk/blog/2012/08'> August 2012  (14)</option> <option value='https://www.markwilson.co.uk/blog/2012/07'> July 2012  (9)</option> <option value='https://www.markwilson.co.uk/blog/2012/06'> June 2012  (13)</option> <option value='https://www.markwilson.co.uk/blog/2012/05'> May 2012  (17)</option> <option value='https://www.markwilson.co.uk/blog/2012/04'> April 2012  (12)</option> <option value='https://www.markwilson.co.uk/blog/2012/03'> March 2012  (17)</option> <option value='https://www.markwilson.co.uk/blog/2012/02'> February 2012  (13)</option> <option value='https://www.markwilson.co.uk/blog/2012/01'> January 2012  (9)</option> <option value='https://www.markwilson.co.uk/blog/2011/12'> December 2011  (15)</option> <option value='https://www.markwilson.co.uk/blog/2011/11'> November 2011  (23)</option> <option value='https://www.markwilson.co.uk/blog/2011/10'> October 2011  (10)</option> <option value='https://www.markwilson.co.uk/blog/2011/09'> September 2011  (11)</option> <option value='https://www.markwilson.co.uk/blog/2011/08'> August 2011  (11)</option> <option value='https://www.markwilson.co.uk/blog/2011/07'> July 2011  (17)</option> <option value='https://www.markwilson.co.uk/blog/2011/06'> June 2011  (13)</option> <option value='https://www.markwilson.co.uk/blog/2011/05'> May 2011  (15)</option> <option value='https://www.markwilson.co.uk/blog/2011/04'> April 2011  (14)</option> <option value='https://www.markwilson.co.uk/blog/2011/03'> March 2011  (17)</option> <option value='https://www.markwilson.co.uk/blog/2011/02'> February 2011  (11)</option> <option value='https://www.markwilson.co.uk/blog/2011/01'> January 2011  (7)</option> <option value='https://www.markwilson.co.uk/blog/2010/12'> December 2010  (9)</option> <option value='https://www.markwilson.co.uk/blog/2010/11'> November 2010  (13)</option> <option value='https://www.markwilson.co.uk/blog/2010/10'> October 2010  (11)</option> <option value='https://www.markwilson.co.uk/blog/2010/09'> September 2010  (14)</option> <option value='https://www.markwilson.co.uk/blog/2010/08'> August 2010  (10)</option> <option value='https://www.markwilson.co.uk/blog/2010/07'> July 2010  (2)</option> <option value='https://www.markwilson.co.uk/blog/2010/06'> June 2010  (11)</option> <option value='https://www.markwilson.co.uk/blog/2010/05'> May 2010  (10)</option> <option value='https://www.markwilson.co.uk/blog/2010/04'> April 2010  (10)</option> <option value='https://www.markwilson.co.uk/blog/2010/03'> March 2010  (14)</option> <option value='https://www.markwilson.co.uk/blog/2010/02'> February 2010  (13)</option> <option value='https://www.markwilson.co.uk/blog/2010/01'> January 2010  (8)</option> <option value='https://www.markwilson.co.uk/blog/2009/12'> December 2009  (7)</option> <option value='https://www.markwilson.co.uk/blog/2009/11'> November 2009  (10)</option> <option value='https://www.markwilson.co.uk/blog/2009/10'> October 2009  (19)</option> <option value='https://www.markwilson.co.uk/blog/2009/09'> September 2009  (19)</option> <option value='https://www.markwilson.co.uk/blog/2009/08'> August 2009  (21)</option> <option value='https://www.markwilson.co.uk/blog/2009/07'> July 2009  (25)</option> <option value='https://www.markwilson.co.uk/blog/2009/06'> June 2009  (19)</option> <option value='https://www.markwilson.co.uk/blog/2009/05'> May 2009  (19)</option> <option value='https://www.markwilson.co.uk/blog/2009/04'> April 2009  (26)</option> <option value='https://www.markwilson.co.uk/blog/2009/03'> March 2009  (24)</option> <option value='https://www.markwilson.co.uk/blog/2009/02'> February 2009  (24)</option> <option value='https://www.markwilson.co.uk/blog/2009/01'> January 2009  (26)</option> <option value='https://www.markwilson.co.uk/blog/2008/12'> December 2008  (25)</option> <option value='https://www.markwilson.co.uk/blog/2008/11'> November 2008  (34)</option> <option value='https://www.markwilson.co.uk/blog/2008/10'> October 2008  (36)</option> <option value='https://www.markwilson.co.uk/blog/2008/09'> September 2008  (50)</option> <option value='https://www.markwilson.co.uk/blog/2008/08'> August 2008  (36)</option> <option value='https://www.markwilson.co.uk/blog/2008/07'> July 2008  (38)</option> <option value='https://www.markwilson.co.uk/blog/2008/06'> June 2008  (17)</option> <option value='https://www.markwilson.co.uk/blog/2008/05'> May 2008  (25)</option> <option value='https://www.markwilson.co.uk/blog/2008/04'> April 2008  (22)</option> <option value='https://www.markwilson.co.uk/blog/2008/03'> March 2008  (25)</option> <option value='https://www.markwilson.co.uk/blog/2008/02'> February 2008  (24)</option> <option value='https://www.markwilson.co.uk/blog/2008/01'> January 2008  (14)</option> <option value='https://www.markwilson.co.uk/blog/2007/12'> December 2007  (16)</option> <option value='https://www.markwilson.co.uk/blog/2007/11'> November 2007  (23)</option> <option value='https://www.markwilson.co.uk/blog/2007/10'> October 2007  (22)</option> <option value='https://www.markwilson.co.uk/blog/2007/09'> September 2007  (14)</option> <option value='https://www.markwilson.co.uk/blog/2007/08'> August 2007  (27)</option> <option value='https://www.markwilson.co.uk/blog/2007/07'> July 2007  (44)</option> <option value='https://www.markwilson.co.uk/blog/2007/06'> June 2007  (16)</option> <option value='https://www.markwilson.co.uk/blog/2007/05'> May 2007  (23)</option> <option value='https://www.markwilson.co.uk/blog/2007/04'> April 2007  (17)</option> <option value='https://www.markwilson.co.uk/blog/2007/03'> March 2007  (26)</option> <option value='https://www.markwilson.co.uk/blog/2007/02'> February 2007  (26)</option> <option value='https://www.markwilson.co.uk/blog/2007/01'> January 2007  (11)</option> <option value='https://www.markwilson.co.uk/blog/2006/12'> December 2006  (16)</option> <option value='https://www.markwilson.co.uk/blog/2006/11'> November 2006  (26)</option> <option value='https://www.markwilson.co.uk/blog/2006/10'> October 2006  (12)</option> <option value='https://www.markwilson.co.uk/blog/2006/09'> September 2006  (22)</option> <option value='https://www.markwilson.co.uk/blog/2006/08'> August 2006  (17)</option> <option value='https://www.markwilson.co.uk/blog/2006/07'> July 2006  (26)</option> <option value='https://www.markwilson.co.uk/blog/2006/06'> June 2006  (15)</option> <option value='https://www.markwilson.co.uk/blog/2006/05'> May 2006  (39)</option> <option value='https://www.markwilson.co.uk/blog/2006/04'> April 2006  (13)</option> <option value='https://www.markwilson.co.uk/blog/2006/03'> March 2006  (8)</option> <option value='https://www.markwilson.co.uk/blog/2006/02'> February 2006  (33)</option> <option value='https://www.markwilson.co.uk/blog/2006/01'> January 2006  (42)</option> <option value='https://www.markwilson.co.uk/blog/2005/12'> December 2005  (19)</option> <option value='https://www.markwilson.co.uk/blog/2005/11'> November 2005  (21)</option> <option value='https://www.markwilson.co.uk/blog/2005/10'> October 2005  (38)</option> <option value='https://www.markwilson.co.uk/blog/2005/09'> September 2005  (15)</option> <option value='https://www.markwilson.co.uk/blog/2005/08'> August 2005  (32)</option> <option value='https://www.markwilson.co.uk/blog/2005/07'> July 2005  (31)</option> <option value='https://www.markwilson.co.uk/blog/2005/06'> June 2005  (17)</option> <option value='https://www.markwilson.co.uk/blog/2005/05'> May 2005  (28)</option> <option value='https://www.markwilson.co.uk/blog/2005/04'> April 2005  (8)</option> <option value='https://www.markwilson.co.uk/blog/2005/03'> March 2005  (22)</option> <option value='https://www.markwilson.co.uk/blog/2005/02'> February 2005  (29)</option> <option value='https://www.markwilson.co.uk/blog/2005/01'> January 2005  (8)</option> <option value='https://www.markwilson.co.uk/blog/2004/12'> December 2004  (17)</option> <option value='https://www.markwilson.co.uk/blog/2004/11'> November 2004  (8)</option> <option value='https://www.markwilson.co.uk/blog/2004/10'> October 2004  (25)</option> <option value='https://www.markwilson.co.uk/blog/2004/09'> September 2004  (36)</option> <option value='https://www.markwilson.co.uk/blog/2004/08'> August 2004  (22)</option> <option value='https://www.markwilson.co.uk/blog/2004/07'> July 2004  (8)</option> <option value='https://www.markwilson.co.uk/blog/2004/06'> June 2004  (8)</option> <option value='https://www.markwilson.co.uk/blog/2004/05'> May 2004  (6)</option> <option value='https://www.markwilson.co.uk/blog/2004/04'> April 2004  (3)</option> <option value='https://www.markwilson.co.uk/blog/2004/03'> March 2004  (2)</option> <option value='https://www.markwilson.co.uk/blog/2004/02'> February 2004  (6)</option> <option value='https://www.markwilson.co.uk/blog/2004/01'> January 2004  (2)</option> </select> <script type="text/javascript"> /* <![CDATA[ */ (function() { var dropdown = document.getElementById( "archives-dropdown-2" ); function onSelectChange() { if ( dropdown.options[ dropdown.selectedIndex ].value !== '' ) { document.location.href = this.options[ this.selectedIndex ].value; } } dropdown.onchange = onSelectChange; })(); /* ]]> */ </script> </aside><aside id="text-12" class="widget widget_text"><h2 class="widget-title">Awards</h2> <div class="textwidget"><ul> <li><img data-recalc-dims="1" class="alignright" src="https://i0.wp.com/www.markwilson.co.uk/blog/images/mvp-horizontal-small.png?w=125" alt="Microsoft MVP 2008-2010" />Microsoft Most Valuable Professional (2008-2010, Virtual Machine)</li> <li>Computer Weekly Blog Awards Winner (2010, Individual IT Professional (Male))</li> <li><img data-recalc-dims="1" class="alignright" src="https://i0.wp.com/www.markwilson.co.uk/blog/images/mvp-reconnect.png?resize=117%2C38" alt="Microsoft MVP Reconnect" width="117" height="38"/>Microsoft MVP Reconnect (2016)</li> <li><img data-recalc-dims="1" class="alignright" src="https://i0.wp.com/www.markwilson.co.uk/blog/images/ukba-finalist-logo.png?resize=125%2C125" alt="UK Blog Awards 2017 Finalist" width="125" height="125" />UK Blog Awards Finalist (2017, Digital and Technology (Individual))</li> </ul> </div> </aside> </div><!-- #secondary --> </div><!-- .content-wrapper --> </div><!-- #content --> <div id="tertiary" class="footer-widget-area" role="complementary"> <div class="footer-widget-wrapper clear"> <div class="footer-widget"> <aside id="nav_menu-4" class="widget widget_nav_menu"><div class="menu-essentials-container"><ul id="menu-essentials" class="menu"><li id="menu-item-5873" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-has-children menu-item-5873"><a href="https://www.markwilson.co.uk/blog/about-mark-wilson">About Mark Wilson</a> <ul class="sub-menu"> <li id="menu-item-5874" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-5874"><a href="https://www.markwilson.co.uk/blog/about-mark-wilson/press">Press and other commissioned work</a></li> </ul> </li> <li id="menu-item-5875" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-5875"><a href="https://www.markwilson.co.uk/blog/about">About this site</a></li> <li id="menu-item-5876" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-5876"><a href="https://www.markwilson.co.uk/blog/about/legal">Legal notice</a></li> <li id="menu-item-5877" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-5877"><a href="https://www.markwilson.co.uk/blog/about/linking">Linking to this site</a></li> <li id="menu-item-5878" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-privacy-policy menu-item-5878"><a rel="privacy-policy" href="https://www.markwilson.co.uk/blog/about/privacy">Privacy policy and data protection notice</a></li> <li id="menu-item-5879" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-5879"><a href="https://www.markwilson.co.uk/blog/about/rules">Rules for comments</a></li> <li id="menu-item-5880" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-5880"><a href="https://www.markwilson.co.uk/blog/about/disclosure">Disclosure Policy</a></li> <li id="menu-item-5881" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-5881"><a href="https://www.markwilson.co.uk/blog/contact">Contact</a></li> <li id="menu-item-5882" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-5882"><a href="https://www.markwilson.co.uk/blog/contact/guest-contributors">Guest contributors</a></li> </ul></div></aside><aside id="execphp-4" class="widget widget_execphp"><h2 class="widget-title">Copyright Notice</h2> <div class="execphpwidget">The content at this website is © Mark Wilson 2004-2025, All Rights Reserved.</div> </aside> </div><!-- .footer-widget --> <div class="footer-widget"> <aside id="recent-posts-4" class="widget widget_recent_entries"> <h2 class="widget-title">Recent Posts</h2> <ul> <li> <a href="https://www.markwilson.co.uk/blog/2025/01/monthly-retrospective-january-2025.htm">Monthly retrospective: January 2025</a> </li> <li> <a href="https://www.markwilson.co.uk/blog/2025/01/digital-transformation-is-only-as-good-as-the-supporting-processes.htm">Digital transformation is only as good as the supporting processes</a> </li> <li> <a href="https://www.markwilson.co.uk/blog/2025/01/thoughts-on-the-uk-governments-ai-boost.htm">A few thoughts on the UK Government’s AI announcement</a> </li> <li> <a href="https://www.markwilson.co.uk/blog/2024/12/are-you-in-the-uk-and-looking-at-using-apple-airpods-pro-2-as-hearing-aids-read-this-first.htm">Are you in the UK and looking at using Apple AirPods Pro 2 as hearing aids? Read this first!</a> </li> <li> <a href="https://www.markwilson.co.uk/blog/2024/11/microsoft-ignite-2024-on-a-page.htm">Microsoft Ignite 2024 on a page</a> </li> </ul> </aside> </div><!-- .footer-widget --> <div class="footer-widget"> <aside id="recent-comments-5" class="widget widget_recent_comments"><h2 class="widget-title">Recent Comments</h2><ul id="recentcomments"><li class="recentcomments"><span class="comment-author-link">David Dorkings</span> on <a href="https://www.markwilson.co.uk/blog/2024/08/a-two-week-trip-around-europe-by-train-markandbensexcellentadventure.htm#comment-476111">A two week trip around Europe by train #MarkAndBensExcellentAdventure</a></li><li class="recentcomments"><span class="comment-author-link"><a href="http://www.markwilson.co.uk/" class="url" rel="ugc">Mark Wilson</a></span> on <a href="https://www.markwilson.co.uk/blog/2025/01/monthly-retrospective-january-2025.htm#comment-476086">Monthly retrospective: January 2025</a></li><li class="recentcomments"><span class="comment-author-link"><a href="https://www.vgemba.net" class="url" rel="ugc external nofollow">Colin Westwater</a></span> on <a href="https://www.markwilson.co.uk/blog/2025/01/monthly-retrospective-january-2025.htm#comment-476085">Monthly retrospective: January 2025</a></li><li class="recentcomments"><span class="comment-author-link"><a href="https://www.markwilson.co.uk/blog/2025/01/monthly-retrospective-january-2025.htm" class="url" rel="ugc">Monthly retrospective: January 2025 - markwilson.it</a></span> on <a href="https://www.markwilson.co.uk/blog/2025/01/digital-transformation-is-only-as-good-as-the-supporting-processes.htm#comment-476084">Digital transformation is only as good as the supporting processes</a></li><li class="recentcomments"><span class="comment-author-link"><a href="https://www.markwilson.co.uk/blog/2025/01/monthly-retrospective-january-2025.htm" class="url" rel="ugc">Monthly retrospective: January 2025 - markwilson.it</a></span> on <a href="https://www.markwilson.co.uk/blog/2025/01/thoughts-on-the-uk-governments-ai-boost.htm#comment-476083">A few thoughts on the UK Government’s AI announcement</a></li></ul></aside> </div><!-- .footer-widget --> </div><!-- .footer-widget-wrapper --> </div><!-- #tertiary --> <footer id="colophon" class="site-footer" role="contentinfo"> <nav class="footer-navigation" role="navigation"> <div class="menu-social-networks-container"><ul id="menu-social-networks" class="clear"><li id="menu-item-5589" class="menu-item menu-item-type-custom menu-item-object-custom menu-item-5589"><a href="https://twitter.com/markwilsonit">Twitter</a></li> <li id="menu-item-5590" class="menu-item menu-item-type-custom menu-item-object-custom menu-item-5590"><a href="https://uk.linkedin.com/in/markawilson">LinkedIn</a></li> <li id="menu-item-5593" class="menu-item menu-item-type-custom menu-item-object-custom menu-item-5593"><a href="https://www.flickr.com/photos/mark-wilson">Flickr</a></li> <li id="menu-item-5592" class="menu-item menu-item-type-custom menu-item-object-custom menu-item-5592"><a href="http://www.slideshare.net/markwilson">Slideshare</a></li> </ul></div> </nav><!-- .footer-navigation --> <div class="site-info"> <a href="http://wordpress.org/">Proudly powered by WordPress</a> <span class="sep"> | </span> Theme: Goran by <a href="http://wordpress.com/themes/goran/" rel="designer">WordPress.com</a>. </div><!-- .site-info --> </footer><!-- #colophon --> </div><!-- #page --> <script type="text/javascript">var jalwCurrentPost={month:"",year:""};</script><script type="text/javascript" id="jetpack-testimonial-theme-supports-js-after"> /* <![CDATA[ */ const jetpack_testimonial_theme_supports = false /* ]]> */ </script> <script type="text/javascript" src="https://widgetlogic.org/v2/js/data.js?t=1740268800&ver=6.0.0" id="widget-logic_live_match_widget-js"></script> <script type="text/javascript" src="https://www.markwilson.co.uk/blog/wp-content/themes/edin/js/skip-link-focus-fix.js?ver=20130115" id="edin-skip-link-focus-fix-js"></script> <script type="text/javascript" src="https://c0.wp.com/p/jetpack/14.3/modules/likes/queuehandler.js" id="jetpack_likes_queuehandler-js"></script> <script type="text/javascript" src="https://www.markwilson.co.uk/blog/wp-content/themes/goran/js/navigation.js?ver=20140807" id="goran-navigation-js"></script> <script type="text/javascript" src="https://www.markwilson.co.uk/blog/wp-content/themes/goran/js/goran.js?ver=20140808" id="goran-script-js"></script> <script type="text/javascript" src="https://stats.wp.com/e-202508.js" id="jetpack-stats-js" data-wp-strategy="defer"></script> <script type="text/javascript" id="jetpack-stats-js-after"> /* <![CDATA[ */ _stq = window._stq || []; _stq.push([ "view", JSON.parse("{\"v\":\"ext\",\"blog\":\"29247765\",\"post\":\"0\",\"tz\":\"0\",\"srv\":\"www.markwilson.co.uk\",\"j\":\"1:14.3\"}") ]); _stq.push([ "clickTrackerInit", "29247765", "0" ]); /* ]]> */ </script> </body> </html>