My local MP, David Wright has hit the headlines for a Twitter faux-pas. A tweet originating from his account, referred to Tories as "scum-sucking pigs". It's a cheap nod to the famous "lipstick on a pig" comment from the 2008 US election campaign. However, the comment flung the MP, who had until then been a relative nobody on the Twitter, into stark, and unwelcome limelight.
The interesting part is that after the horse had bolted, David issued a statement regarding the affair. According to him, the offending tweet did refer to lipstick on pigs, but without the "scum-sucking" adjective. He maintains that the stronger term was added to his tweet in retrospect, by a hacker.
If you haven't used Twitter yet, the platform does not yet permit the ability to re-edit your tweets (to the annoyance of anyone who has hit the "update" button a little too quickly to catch that blatant smelling pistake). If you want to correct your actions, you have to delete the message, and start afresh. Apparently this wasn't the case for David, his message was somehow amended.
From a technical point of view, I can see only two possible ways for this to happen:
1. The perpetrator of such a hack would have to be monitoring David's network traffic, then intercept, then re-edit his post before it reached Twitter's server. Either David's computer/laptop or handset would need to be compromised, or the person issuing the attack would have to be nearby to him when he sent the message (in the event that he sent it over a Wi-Fi network).
2. The hacker in question somehow broke into Twitter's database server, gained access to the message, and edited it.
Both of the above are no mean feats, the second is a news story in itself.
The other possible explanation is that David had second thoughts about his tweet. Looking from a purely technical standpoint, it is a trivial matter of typing into a box, to create an inappropriate message. Perhaps, after realising the amplified nature of a scandal on twitter, he reconsidered. Something that he saw as fairly innocuous, simply got out of hand. If this is the case, David should have either offered an apology, or stood by the original statement. But by telling Twitter (and the news) that his post was re-edited, he's placed himself as either the victim of one of a most sophisticated attack. Worse in the eyes of Twitter users, he's set himself up as someone who has no real knowledge or interest in the platform which he's chosen for self promotion .
If it turns out that David is lying about the hack, he's taking a very misguided gamble that Twitter users won't be versed enough to catch him out. Added to the fact that there is a large, active Shropshire contingent on Twitter, such a move could actually affect voting in his own constituency at the next election.
Lastly, I can point to a precedent in David's past where he succeeded with a similar approach. Two years back, there was a campaign to keep a small community Post Office open in Randlay, Telford. Based on his voting record, it seems that the local constituents were fighting against David:
http://www.publicwhip.org.uk/division.php?date=2004-01-13&number=28&mpn=David_Wright&mpc=Telford
http://www.publicwhip.org.uk/division.php?date=2006-10-16&number=304&mpn=David_Wright&mpc=Telford
http://www.publicwhip.org.uk/division.php?date=2007-01-10&number=23&mpn=David_Wright&mpc=Telford
http://www.publicwhip.org.uk/division.php?date=2008-03-19&number=131&mpn=David_Wright&mpc=Telford
http://www.publicwhip.org.uk/division.php?date=2008-03-19&number=132&mpn=David_Wright&mpc=Telford
His next move was almost Machiavellian. He sent out this letter to all affected constituents:
It proved to be a coup de grâce, and Randlay lost their Post Office branch.
Good luck to anyone trying something so audacious with the Twitter community.