Swearing on Twitter

by Andy Polaine on February 5, 2009

in General

Cursebird - Swearing on Twitter

Most people who know me in real life know that I have a tendency to swear too easily and too much.

They are, of course, twats.

Actually that last outburst is a rarity for me because I tend not to swear online all that much and, it seems, never almost never on Twitter. Perhaps it is the fear of the permanent, cached record of it somewhere. Perhaps it is that I’ve trained myself to be careful about crafting the written word.

Either way, Cursebird, a site that tracks people swearing on Twitter in real-time, shows how fascinating the everyday grittyness of humanity is. Who cares about tracking tweets about “Obama” or “Economic Crisis”? Swearing is much more entertaining.

Cursebird was put together by Richard Henry. @thinkingstiff seems to be leading the cursing pack at the moment, but I’m pretty sure he’s trying too hard.

{ 4 comments… read them below or add one }

1 matthew February 5, 2009 at 12:52 pm

your a cunt. we all know that.
and you swear a lot. just stop being such a sissy girl and drop the c bomb on line more
fucker

matthew’s last blog post..1 minute faster – the base training is so working!

2 Knotty February 5, 2009 at 12:59 pm

I coded a prototype @ Poke that did exactly this a year and a half ago. It was called ‘Shitter’.

Knotty’s last blog post..do you get it now?

3 Andy Polaine February 5, 2009 at 1:17 pm

I’m obviously attracting the wrong calibre of reader here.

Knotty, you should have put it online mate, prototype, schmototype.

4 oscar7g February 7, 2009 at 6:05 am

I have a number of saved Twitter searches for the words, cunt, fuck and shit. It is interesting to see the multitude of contexts they are used in. Fuck seems to be the most flexible of the lot, which is not really that surprising.

Me personally, I think swearing on Twitter is a natural thing as it is much more akin to real world conversations than other online forums. Swearing in a blog post/comment comes off as contrived.

Previous post:

Next post: