Language

A simple tip for community: mind your language

When managing a community, creating new community functionality or developing a social- or contribution-centric projects, avoid using words like allow and let (e.g. “we’ll allow people to upload their photos…” “we let users comment on articles…”)

Using words like these will negatively influence – or betray – your perception of the project, as well as giving a strong indication to everyone else (including the community) of user involvement: barely tolerated, and only made possible through your largesse.

Instead, think about using words like invite, empower and encourage, even in your internal emails and planning documents.

It may sound silly, but the right frame of mind can help you make good community decisions on a site, and the words you use even to think about it or describe it can influence your frame of mind. If you think about users as troublesome, bothersome, people doing a thing you’re graciously allowing them to do, then you’ll expect them to be pathetically grateful/need constant supervision or management/will want to break the rules.

Contrast that with a message that you’re inviting users to get involved, or encouraging them to share ideas and images. See how different it feels? Already, the kind of community management you’ll be thinking about might include curation, reward, conversation development, and so on.

So think about – and influence – your subconscious approach via the words that you choose to describe community participation. In other words: mind your (negative) language.

“Just call them women” – when is a woman’s job relevant to coverage of her murder?

A few years ago, following a series of murders in Ipswich of women who had been working in the red light district, we saw a flurry of columns in various newspapers and sites along the lines of this one on the BBC. These articles earnestly debated when – and whether – it was acceptable to refer to the victims in such stories as “murdered prostitutes” or “murdered sex workers” rather than simply “murdered women”:

When someone’s been murdered, does it matter what they did for a living?

Many people have contacted BBC News to complain that we have made a point of describing the women who’ve been killed in the Ipswich area as “prostitutes”. The problem must be the description, and not the language. At least once on Five Live we referred to the women as “sex workers”. This euphemism hardly rebuts the basic complaint, expressed succinctly in one text message we received – “just call them women”.

The complaint took two forms – we wouldn’t bother to report that a murder victim was, say, a plumber, and when we report that the victim was a prostitute we are being judgemental and implying that her life was less worthy than another’s.

There were similar articles following the murders of several women working in similar circumstances, but this time in Bradford, last spring.

This has been in the back of my mind over the last few weeks for two reasons – or rather, one situation and a number of semi-related references. The situation is the murder before Christmas of Jo Yeates in Bristol.

The first reference is this tongue in cheek article from satirical news site NewsThump which carries the headline “The death of one middle class woman is equal to that of six prostitutes”:

The UK media has finally revealed the calculations used when categorising the importance of a human life, or the scale of natural disasters.

The calculations, which are the industry standard, reveal that a mudslide in Brazil that kills between 10 and 20 people would receive the same level as coverage as a covering of snow in Oxfordshire that caused a retired ex-army officer to slip and nearly fall.
[...]
The calculations are also used for stories involving murder, and highlight the importance put on the victim not being a prostitute, drug addict or a foreigner when it comes to receiving round the clock coverage.

Our insider continued, “If the victim is respectable, white, middle class, and with a loving family then it’s going to receive blanket coverage.”

“If, on the other hand, the victims are a group, or to use the collective noun, a ‘shame’ of prostitutes then it will take quite a lot of violence to generate the same sort of interest.”

Yes, it’s satire, but there’s a more than a grain of truth there.

At the same time, I’ve been quietly noticing how many news outlets are referring to the murder of landscape architect Joanna Yeates (see also: murder of the landscape architect, murdered landscape architect, murdered architect, murder of architect etc), including the BBC, which just this morning published a story with the first paragraph:

A 32-year-old man has been arrested on suspicion of the murder of landscape architect Jo Yeates.

So they “wouldn’t bother to report that a murder victim was, say, a plumber” but they would if she was, say, a landscape architect?

In the 2006 Ipswich murders coverage, the BBC dismissed the complaint I quoted at the top of this post, and defended its use of the women’s jobs as a descriptor, like this:

In this case, the fact that the women were prostitutes was crucially relevant. It suggests, if nothing else, that prostitution is a dangerous way to earn a living and that a prostitute is more likely than most people to meet a murderer. That has to be the starting point of the police inquiry.

If that’s the case, then how crucially relevant to the Jo Yeates murder inquiry is her job as a landscape architect? Is it inherently more dangerous way to earn a living? Are landscape architects more likely to meet a murderer? Or is it fair to say that in this case, as in so many others, the victim’s profession adds colour and human interest to the coverage rather than just calling her a woman?
Read Full Post »

Blog vs Blogpost: a note on terminology

I’ve posted about this before, and this formed my contribution to the Guardian style guide but it bears repeating, because so many people seem to muddle them up.

blogvsblogpost

Or, to put it another way:

blogblogpost2

Got it? Good.

I’m sorry to suddenly become the nomenclature-nazi, but when people interchange words like those above it just gets confusing. Saying “I’ve just finished a giant blog” or “I’m writing a blog about cheese” confuses the container object for the constituent part.

A blog carries with it expectations or overtones of archive, pace, time, multiple postings. Blogs don’t finish. If you’re writing a blog about cheese then I expect to see lots of posts about cheese, exploring dairy products from all angles, not one entry, about Edam.

Likewise, people occasionally say “there are a lot of nice bloggers on my blog” which is nice and everything, but they have a different relationship than you to the content. You wrote it; they responded to what you wrote. You are the blogger; they are the commenter.

It’s a small distinction, but it’s important.

That is all.

PS Some have asked with what authority I make this bold linguistic claim. The answer is: I’ve been blogging for eleven years, since it began with a W.

Ten things that I wouldn’t have much call to say if blogs didn’t exist

Part of my tenth blogiversary series.

  1. Reverse-chronological (unless I was Benjamin Button)
  2. Permalink (I think Prolific invented or at least named these, didn’t she?)
  3. Archives (unless I was a librarian)
  4. Publish (unless I was Rupert Murdoch)
  5. Blogroll (I don’t have one, though)
  6. Blogring (remember them?)
  7. Post (unless I worked for Royal Mail)
  8. After the jump (unless I worked for the Samaritans)
  9. Pingbacks (unless I was Brian Eno)
  10. Plugins (unless I was an automaton sexbot)

Addendum: Things I do not say, even though I have a blog

  1. Blogosphere, because it’s stupid
  2. Blog when I mean blogpost because it’s just WRONG