When a Twitter user is caught spelling incorrectly, using colloquialisms or lolcat lingo, they call in the @SpellingSquad. Thank God, we can all rest easy.
You might think you’re free to say what you like on Twitter without being condescended to by someone you don’t follow. Wrong, as was proven to me today when I sent this tweet:
and found this reply when I got home:
My somewhat vitriolic reply of “fuck you @spellingsquad, fuck you” (thanks to Phill & Phil for that lovely piece of phraseology) was met with what can only be described as a small barrage of abuse from someone who, judging by the tone of his or her tweets is in no place to patronise.
...and then 3 minutes later:
...and finally
I’ve written before about the importance I place on “good English”, but have also stated in a previous how-to guide, that the message is what is important, not the means.
Readers tend to forgive or ignore spelling and grammar mistakes - after all, most bloggers are just members of the public, not professors of English - and read the blog to find out about you, your opinions and your life.
(I’ve just quoted myself. Am I now officially a wanker?)
So the question is: why does a microblogging platform which is now famed for the immediacy it allows and the mobility it affords bloggers, need a glib and self-satisfied spell checker? I get enough hassle from Google as it is!
Remember that Twitter is simply a set of overlapping and interconnected conversations had between real people. Would you, @SpellingSquad hover over the shoulder of your friends in the pub and correct them every time they mispronounced a word? I think you’d be horrified if someone did that to you, so I’m sure you can understand the situation here.
In short, Douglas Adams puts it better than I could: “nobody likes a smartarse”.