Logo fail

This logo for the Archdiocesan Youth Commission was created in the early 70's and has been doing the rounds on the internet just recently. Truth is, it's not the logo that failed. It's the organization that failed and because in 2009 we have all heard the story of sex abuse in the Catholic Church, it is impossible to look at this image without that story coming to mind. This is the great power of stories. They shape your perceptions.

ITP Spring Show

Any Geek/Gay worth their salt should be at the ITP spring show. Lots of young things with gorgeous gadgets. Some big, some small. Some things to look out for:
Time in six parts
CW Wang: with our friend (of Fagadget, not of Dorothy) Kevin Slavin at Area\Code
Water Canary
Cheap water testing for Africa (since I do work with WaterAid I felt I had to love this one). Also seems to have had something to do with our other friend Clay Shirky of #amazonfail fame. - Again Geek, not Gay.
Nexus
not quite sure what it does but it is another project for Unicef. I'm going to have to recruit some of these young things to work with me at the African Institute of Strategy.

Zoom

Prezi.com is going to sweep Powerpoint away.
Only hope the next conference I go to I don't get sea sick.

pushbutton touch screens

MIT video of touchscreen pushbutton technology.

love the fact that they seem to have used an ipod as one of the shapes.

#Amazonfail a success

At Fagadget we are huge Clay Shirky fans. He is one of the smartest people we have met and he knows a thing or two about how today's communications tools change the world. We cannot recommend his book "Here comes everybody" enough. (We are also happy that Clay has managed to secure strong marketing support from Amazon, not only maintaining his high sales ranking and a very competitive price versus BN.com).

In a loving and supportive way, we have to respectfully disagree with the conclusions that Clay Shirky comes to in his recent post on "The failure of #amazonfail".
Clay, like us, was early to the #amazonfail #amazonrank twitter conversation, likely alerted by the same initial post by @scobleizer (Robert Scoble). Clay describes what many of us felt...the "emotional pleasure" and "intoxication" of the #hashmob (thanks Nicolas Carr).

Having read much of the aftermath there seem to be two conclusions that most people come to in this debate:

a) Amazon was wrong/ stupid/ failed because they had all the wrong checks and balances but were not fundamentally LGBT biased and we all acted like a rampant lynch mob. (my take on Clay's conclusions)

or

b) Amazon's algorithm was created by the company and a built in LGBT bias shows a systemic bias within the organization. Even when alerted by authors and publishers of this fact, their reply was 'gay = adult, so suck it up!' which reinforces the fact that the LGBT bias is systemic within Amazon. (my take on Mary Hodder's take).

I want to offer up an alternative conclusion why we all felt intoxicated and good about this event. This has nothing to do with why the #amazonfail happened but everything to do with what it achieved.

Firstly, the community identified the problem and in #amazonfail saw a way to increase awareness of the problem that would elevate it beyond the lowly person in the customer service who could not see the importance of this issue. Such gatekeepers in hierarchical management systems are increasingly irrelevant as we can speak for ourselves to the people that matter and if unsatisfied with the result can elevate it to a higher authority without their permission or supervisor!

Secondly, what was intoxicating was the shared mission of righting an obvious wrong. The conclusions of most commentators tend to focus on how successful we were in righting the 'wrong' that caused of the problem - LGBT bias within Amazon or a bad algorithm/french programmer. However, the real 'wrong' in this case was not the cause of the problem but the consequence of the problem and we were very successful in overturning that - restoring the representation, profile, livelihood and income of LGBT writers and publishers. I think there is good evidence that this is what mobilized us into action and turned a simple blog post by Mark R Probst into a movement.

Most of the initial blogs that picked up on the story did not focus on why this was happening but simply built up an impressive body of evidence that there was indeed a problem.

Many of the active participants not only joined petitions but identified people who could help e.g. @werner the CTO of Amazon for example, received many supportive emails alerting him to the problem. Authors and publishers reached out to their contacts, not only to make a stink but to bring this to the attention of the leaders of the company as lower down communications systems had obviously failed.

We cannot know all of the motivations of the individuals who joined in #amazonfail, just like we will never know the motivations of Amazon for developing such an algorithm or responding to authors the way they did. What we do know is that with the help of "read/write" technology the community identified the problem fast, verified the existance of the problem, mobilized to let other interested parties know the problem, contacted people who could fix the problem and within a period of 24 hours had the solution in hand and being fixed by the people who owned the problem. That is what felt good. This was not a lynch mob.