Monday, 11 October 2010

Information and truth and information and truth

I'm not going to give you his name.

My husband and I were having lunch with a friend on the weekend, and the topic turned to business. My husband works in International law, and so does our friend, but at the sharp end. Specifically, our friend prosecutes war crimes.

'Before we go on,' he says, 'there's something I should probably tell you. I'm currently the subject of a criminal investigation.'

And the crime, as it turned out, was torture.

Now strange things happen in the world, and I'm cautious of any statement that reads 'I know X and he would never' (I've seen at least three stalkers - who really were stalkers - defended that way). But frankly, the odds against this being true would give the infinite improbability drive a run for it's money. The idea that some particularly knuckle-headed defendants tried a last-ditch move to get off the charges against them, on the other hand, is running at 1:1.0000000001 odds on the being-true front. But still.

If you google my friend, you'll find an article in a reputable UK newspaper with his name and the charges. I'm not linking to it, because no way am I going to push it up the google ranks. But it's turned me to thinking about the social impacts of truth.


True statement:

Friend has been accused of torture.

Totally legitimate newsworthiness:

High.


Highly-unlikely-to-be-true statement:

Friend committed the crime of torture.

Totally legitimate newsworthiness:
Absolutely none.


That's not a 'oh shame on you media' statement, it's a point of necessity: Probability statements aren't news, nor should they be (apart from op ed blarney). 'Bad accusation made against good dude who almost certainly did no such thing' is not legitimate news, because there's no fact content in it. 'He probably didn't' is not reportable, and if it was, a lot more bad people would get away with a lot more bad things.

And yet, and yet, and yet... there's also social truth. And longevity. Especially longevity.

Flash forward to the hasn't-happened-yet end of the criminal proceedings:


True statement:

Friend has been cleared of torture accusations.

True statement:

Friend did not commit torture.

Totally legitimate newsworthiness:

Middling.


Middling because nothing really happened. An allegation was disproved. That means the basic system of the world didn't *actually* change - a falsehood came up and was knocked down. Nothing actually new about the world was revealed, just a slight blip in the great long list of Things People Have Said - a list that does not have a 1:1 correlation with Things That Happened.

Again, this is not an 'I blame the media' statement - it's just that 'someone didn't do something' is, in most circumstances, far less interesting/useful knowledge than 'someone might have done something'.

(Some of you will know that I've done my time with journos, and I don't actually like the news media very much at all. So I am trying Extra Hard to be Totally Objective here.)


Flash forward two (hypothetical) years, and let's imagine two (I'm being optimistic here, there may be more) articles in reputable newspapers about this case exist online.
One contains time-sensitive true statement 1: 'X is accused of torture.'

The other contains non-time-sensitive true statement 2: 'X has been acquitted of torture.'


...Which of these will have the higher google ranking?

Which will more people see?

Given that both are true, which will the most people know to be true?

And of those that see only the first, how many will interpret 'accused of' as 'did'?


I don't have answers to this, and never in a million years would I say the first article should be taken down. I just worry about my friend, that a malicious move by bad people could follow him around for the rest of his life because the technology for 'true' doesn't meet the world's real requirements for 'true'.

But then again, he's seen worse.


Tuesday, 5 October 2010

Cheap wins



Pop quiz! What's the difference between these two statements:


1. For information about fish, click here

2. Click here for information about fish


Answer: If you're blind/vision impaired and using a screen reader (which reads the page aloud), and you opt for the handy/commonly used 'read me all the links on this page, please' option, they respectively read like this:





...out of those two, option one doesn't mean anything and option two does. That has to be about the simplest way to improve accessibility ever. (And it sounds better, too.)


e-learning and e-learning standards

I've finally done an annotated version of my Technical Communications UK conference presentation - and here it is:


(Warning: contains lots and lots of SCORM.)

Sunday, 3 October 2010

24 hour comic: Done.

I am Never Doing This Again.

I had a specific plan in doing a 24 hour comic (http://www.24hourcomicsday.com/) - specifically, challenging myself to do bad work. Completion over quality!

Why?

Because when I fall, I fall at the first hurdle, that's why.

There are a lot of benefits to planning projects properly (my go-to position). You get to Get It Right The First Time. You also Save Time in the Long Run. But if you can't get the plan sorted properly... splat! Down goes the whole thing - that's the first hurdle. That bit that comes after the plan. The doing-bit.

So I did a 24 hour comic to see if I could finish something with no plan at all - not just drawing it, but tracking it, uploading it, the works. And I did! And guess what? The comic is really pretty bad. But it's done! Yay!

Here it is: http://bit.ly/acHpxB


Things I learned from doing this

1. Set-up times still exist when you're working at high speed.

As a setting-up fan I always figured they were somehow optional/something I could not do if I chose, but no - turns out, even at break-neck speed there's still times involved here.


2. Pre-existing knowledge counts. A lot.

This would be impossible if I couldn't draw a bit first, but *equally* if I hadn't messed around with Tumblr before.


3. The urge to fiddle with things gets stronger the closer the finishing line is

I think this might be because the finishing line is scary - as long as it's incomplete, it can be fixed. Once it's out there, no chance - it will be it's own fairly poor thing. Submitting is *hard*, even when the goal is poor work.


4. I can drag a theme out of thin air if I have to

Surprise talent! I didn't script a word of the comic - just made it up page by page. But my buddy tells me it *looks* scripted, so, I'm happy with that.


5. Maudlin is really hard to avoid actually

I really hate the page where the two figments tease me. It is so twee & saccharine (but I couldn't use a replacement page, so I'm stuck with it). I did it because it was easy - twee is totally easy.


6. Everything takes longer than you think

The comic took ages. So did this post, actually. I keep editing it.


7. Stopping and not editing any more is hard

But, as a skill, it *can* be learned. I'll show you, ready?

It's like this:


Saturday, 2 October 2010

24 hour comics day

It's 24 hour comics day, and I am IN.

The deal is - 24 pages in 24 hours. That's it.

I've chosen to heighten the stakes a little - 24 pieces of paper (no spares), and really really bad pencils. Because I can't find my pencil case. (Great start, hey?)

Follow it all here:

www.zoedoesa24hourcomic.blogspot.com

Monday, 27 September 2010

Non-text search is hard...

As far as I can see, there are basically two types of searchable object:

1. Text objects - such as a web page
2. Non-text objects - such as an image

These two require two different search functions:

1. Text-based search - searches the object itself
2. Metadata search - searches descriptive metadata

In my opinion, all content *should* have descriptive metadata (date written, author, so on). But only non-text objects actually require it - you can't search for 'picture of a horse' unless someone has actively tagged a picture with the word 'horse'.

The problem lies in the subjective nature of descriptive metadata, because tagging/taxonomy-ing/controlled vocabulary-ing is HARD. Really hard. And collecting that data is even harder, and utilising that data is harder again.

Case in point: I have a bunch of hobbies. One of them is perfumes.

If ever there was a set of content that didn't meet with text-based search criteria, it's scent. English doesn't even have scent words, or flavour words - we rely on 'smells like' and 'tastes like' because, outside of sweet/salt/bitter/sour/umami, there are no words (and 'umami', a taste-enhancement molecule found in MSG and parmesan cheese, is stolen from Japanese anyhow).

Because of this, perfumes are the perfect place to examine the efficacy of non-text search. How can I, as a perfume enthusiast and buyer, find new scents?

With difficulty.

Here are some comparisons of my favourite perfumes (I stress: despite what you're about to read, I love these scents), compared against their marketing blurbs.


Hermes Eau de Merveilles

They say:

An enchanting fragrance that encapsulates the spirit of wood, the memory of oceans and the sparkle of a constellation.

I say:

Smells like cake, only sexy. Exactly like I think spice would smell like. (Gentlemen: this is the one you want to buy your lady. You will love this so much.)


Guerlain Samsara

They say:


It was in China and Tibet that Jean-Paul Guerlain sought the inspiration necessary to create Samsara.
Samsara is a Sanskrit word that has its roots in Hinduism. It signifies the cycle of birth and rebirth, the perpetual voyage from one existence to the next, the wheel of life that keeps on turning.

Samsara is an invitation to serenity and harmony, with oneself and with the world. It is a voyage between East and West, Orient and Occident, an homage to the woman who is ever in search of serenity.


I say:

Smells like sand. No organic content, apart from one element - it's sexy (more civet than musk). Exactly like what I think Arrakis would smell like.


Shiseido Zen

They say:

Something to do with amber and 'wood breath'.

I say:

I only bought it because it has space rose in it. Not sexy.


Hermes Kelly Caleche

They say:

The unexpected caress of leather among flowers. Mimosa, iris, tuberose, and climbing rose. A floral perfume touched by leather.

I say:

A wood fire that just went out, and someone dropped some fresh/wet herbs on it. And some booze. Probably gin. Not sexy.


Jardin sur le Nil

They say:

A perfume of light and life, generous and sparkling. A bottle reflecting the shimmering green and ochre tints of the banks of the Nile River appreciated by women and men alike.

I say:

Smells like orange peel and mud, on a very hot day. Not sexy.


Chanel No 5

They say:

Femininity is timeless

I say:

Smells like perfume. Ur-perfume. Super-sexy.


The thing is, I would never search 'orange peel' when looking for a new scent, but neither would I search 'femininity is timeless' or 'cycle of birth and rebirth'. And I know that the results from using a frangrance wheel (yes, that's a Thing) are mid-lame to very-lame.

If I looked for a 'sexy' perfume I would get something vile and musk-ridden (don't fret, it's all synthetic now) with a celebrity branding attached, not something that smelled like cake. Similarly, a search for 'not-sexy perfumes' wouldn't take me to the best not-sexy perfume sources - Japanese houses like Shiseido and Kenzuo and Issey Miyake. (The cultural reasons for this are extensive and, for this post, irrelevant. But Japanese perfumes are amazing.)

Scents - they just don't translate to text.

And yet, a little part of me thinks - hopes - that this is a solvable problem. There will be a way to search for scent. One day.

...and to be honest, pretty much this whole post is to announce how thrilled I am to see that Hermes' new Eau Claire des Merveilles is now out.

Mmmmmmm... fresh cake. Delicious.

Thursday, 9 September 2010

I am so glad this exists: Monocle

I found out about this over a week ago (thank you for making it *and* telling me about it, @josephpearson), so it's about time I posted a synopsis about this potentially excellent new ebook tool.

I haven't played with it yet, but I like the sound of it: it's the Monocle ebook reader. http://inventivelabs.com.au/weblog/post/announcing-monocle/

Monocle is a new - and in my opinion, overdue - development in ebookery. It could be revolutionary, for one reason: it works in browsers. Which is to say, you access your eBook content through the internet.

Fundamentally, there are two ways to access content using machines:

1. Content lives on the user's own device. This is a download-based model.
Example: iTunes.

2. Content lives on external servers which are accessed by the user's device. This is a web-based model.
Example: Spotfiy.

There's a user-facing difference between the two, and a difference in the deployment of IP. In both cases I think the no-download (like Monocle) model will eventually have the upper hand.

For content publishers, the download model is terrifying for a simple reason - once the file is downloaded, it's fate is entirely out of your hands. No matter how much DRM it's wrapped in, someone, someday, will crack it. It will always have the opportunity to go wild, and when it does, there go (some of) the profits.

Similarly, once a file is downloaded, you can't track the usage well. Is it popular? Do people actually use it after they've bought it? It's hard to say (unless the content is software dependant, like iTunes, and that's not much fun).

For content users, the download model is the more annoying option, because it's tethered to a device. We hear people grumble all the time about iTunes, but never about spoftify - spotify is a smoother experience, because there's no fiddling (or protecting) downloaded files to get in the way of accessing the music.

To (shamelessly) use my husband as an example: he works from home some days, from the office others, but he does the same job in both locations. He's an academic, so he uses professionally published academic book content a *lot*.

At work and at home, he uses different machines. They're powerful desktops, so physically lugging them about is not a good option. Because of this, Aadevice-tethered eBook is no use to him.

But he always has an internet connection. He can always log on to a website.

There's a developing trend of people using multiple machines to access their content, instead of the trusty old family PC. My household isn't unusual - it has two people, a desktop, two laptops, an ipad, and an iphone. Matching that trend on the other side, we can also see internet access growing exponentially - it's quite likely (if not inevitable) that ubiquity is just around the corner.

Which is more likely? A future where people use the same device all the time, or a future where people have internet access all the time?

In choosing between browser-based and download-based content models, these respective trends point to an access-it-through-the-internet model as being where the smart money is.

A browser-based service naturally has to rely on a logon. This for me is a double-bonus, because (unless I've misinterpreted) Monocle can support the standard university logon services such as Raven and Shibboleth. That's great for universities, because that opens up the ability for a university library to buy browser-based eBooks and make them accesssible to all staff and faculty using their own, normal logon - no mess, no fuss, all access.

Monocle is also (hooray!) completely open source. I hope it does really, really well.