Cory Doctorow: Europe's Copyright Wars – Do We Have to Repeat the American Mistake? (Web 2.0 Expo, Berlin) [en]

My live notes of Cory’s talk. Might be a bit messy because I have trouble wrapping my head around some of these issues, and Cory does indeed talk rather fast. Plus, as you probably know by now, I’m in a frightening state of exhaustion.

Europe and America: harmonization escalation.

Web 2.0 Expo Berlin 26

It’s easy to laugh at US copyright policies from Europe.

Inducing infringing of media copyright: should be held liable. If your technology might be used to infringe copyright… arghl… you’ll be held liable.

So if you develop your technology with the idea of infringing copyright, you will be held liable (thought crime!) for any subsequent copyright infringement.

With this kind of stuff, the VCR would never have seen the light, because one of the main ideas behind it was “time-shifting” and “librarying” (watch something later, or collect your favorite shows). The court ruled that time-shifting was legal, but never ruled on librarying.

FCC.

Guy who gave a talk explaining how Adobe’s DRM was evil, arrested at the end of the talk by the FBI for talking about the wrong type of maths.

DMCA takedown notice. No need for proof. Routinely abused to silence critics, etc.

Viacom abuse, searching YouTube for keywords, thousands of DMCA takedown notices, for things as innocuous as people talking at a part who happened to have the names of their characters, etc.

Viacom says that by allowing private videos, Google and YouTube are inducing infringement.

Lawsuits against music fans in the USA. Suing fans does not convince them to go back to the record store! Hard to believe that the record companies’ best response to file-sharing is suing enough college students hoping the rest get the message.

Europe is by no means inculpable. DMCA started as a proposal shown to Al Gore who said it was bad, then presented to Europe where it got positive response and became the EUCD and back to the US as DMCA. steph-note: maybe the difference in perception, if the laws are similar, has to do with the suing culture?

IPRD 2 : probably the worst. Copyright infringement, historically, has to be dealt with in court. This criminalizes copyright infringement. And turns over dealing with it to the public police. steph-note: I’m afraid I don’t understand all this, a bit over my head.

e.g. Sweden, whole server farm taken down by the police (servers in police van), including legitimate sites of legitimate business, just disappeared into the van.

The sophisticated “cyber criminals”, this kind of thing doesn’t stop them. It just can be the end of it, however, for innocent people who aren’t very tech-savvy. Police cordoning off area for 6 months, 70% of businesses hosted there failed within those six months.

DVD CPCM: Europe-wide thing, all devices reading DVDs required to be compliant. CPCM can individually shut down certain classes of users, based on content producers’ decisions, even if you have the legal right e.g. to show something in school, you wouldn’t be allowed to break the CPCM.

Disturbing CPCM flags: DVD flagged so it can only be used by one household. (What is and what is not a household? huge problem. They have a very “conservative” concept of what a household is, which doesn’t include children and parents scattered through continents, old dads entering retiring homes, kids with divorced parents…)

Restricted playback systems. Goodbye interoperability. We didn’t need permission from Vauxhall to plug in your Nokia phone, or permission from Microsoft for Keynote to open ppts, or film company for playing their DVD on a Toshiba player…

All this is turning interoperability into a crime! You need keys to interoperate, and you’re not allowed to reverse-engineer keys.

steph-note: quite scary, all this.

Some of your sound systems won’t play certain types of audio, etc.

US smart enough to stay away from things like the Database Directive. In Europe, a collection of facts in a DB is protected for 50 years! Economist’s opinion on this: the DB directive is not good for Europe. They also asked the incumbents if the directive if it was good or bad, and of course they said yes. So the commission concluded: “opinions are divided! some people say it’s good, others say it’s bad! let’s leave things how they are!”

What can we do? Get involved in the EFF. steph-note: or ORG

Problem now: hearings for copyright stuff attract copyright holders, not technologists, geeks, economists.

Keith Richards isn’t going to go hungry if he doesn’t get another 40 years of copyright protection for his recordings.

First time in copyright history that the government turned its back on a proposal, and said “no, copyright extension is not a good thing”.

What Cory thinks the BBC should be doing. Streaming with DRM. Excuse: “we don’t have a choice, the right holders dictate the terms.” Why does a corporation funded by the public, for the public, come and tell the public that it has to adapt to the right holders demands, and not the opposite? Here, the BBC is not acting in public interest, but there is a history of the BBC doing so.

At one point, rights holders wanted use-by-use payment for the radio. e.g. each time the DJ want to play something, he has to call and ask permission. They turned that down. Found another solution, other music. Finally rights holders backed out and asked the radios to license their music (instead of the stupid conditions they were putting previously).

So Cory’s advice: look the rights holders in the eye, and go off to find other content, artists, etc which will agree to their terms, and give them a place they have been denied until now.

Problem: nobody is offering collective licensing schemes to the internet. Nobody is offering ISPs a blanket license for music or television shows.

It is not good for society that average people are criminalized for accessing culture.

The EFF is about copyright reform, not copyright abolitionism — not is Cory.

ThePirateBay weren’t abolitionists in Cory’s opinion, at the start.

Useful for copyright reformers that there are copyright abolitionists, because allows to say “if you don’t negotiate with us, you might end up having to deal with them”.

Ankur Shah & Gi Fernando: (Facebook API) Disrupting the Platform (Web 2.0 Expo, Berlin) [en]

*Here are my notes of this session. Usual disclaimers apply.*

Harnessing social analytics and other musings on the Facebook API

Web 2.0 Expo Berlin 10

Web 2.0 Expo Berlin 17

In the lights of OpenSocial, tough week to be talking about Facebook.

Ankur and Gi are going to talk about a variety of good things that they’ve done with the Facebook platform.

Understanding human relationships.

Facebook is a truly social platform, which allows to create truly social applications. Engage with your friends directly. Ability for a company to respond to the social content inside the platform.

Questions:

– where were they? (Facebook)
– where we are? (developers)
– what’s everyone doing?
– where’s it all going?

Geek + pizza = Facebook.

7000 applications. SuperWall, Slide, Top Friends, iLike, Flixter, Likeness — successful!

*steph-note: Ankur is speaking a little fast for me and I have a headache, so I’m not following this very well, sorry*

Applications kept in a controlled environment. The back-end to all those applications is the same.

Doesn’t depend where your engaging with your users as long as you are.

Standardised facebook functions => very compact code. Homogenous look (avoids the “MySpace effect”)

Web 2.0 Expo Berlin 8

Web 2.0 Expo Berlin 16

Bob Dylan application.

Web 2.0 Expo Berlin 15

PHP. API easy to use. *steph-note: maybe I should build a Facebook app… not sure about what though!*

Standardised component set.

Web 2.0 Expo Berlin 20

Big question: does the platform really break? Facebook’s innovation is so quick that things break.

A short note on viral-ness. A phenomenon, from 50 friends to 50’000 users in a week. It can happen… but. The Dylan application allows you to share something with others. Individuals make applications spread more than other users.

Facebook allows users to spam their friends with applications.

My Questions: 450’000 daily active users.

Socialistics. Information about your friends.

*steph-note: ew, sorry, I’m passing out. Nothing to do with the content of this session, quite interesting.*

Little Facebook API vs. OpenSocial moment.

Jesse James Garrett: Delivering Rich Experiences (Web 2.0 Expo, Berlin) [en]

Here are my notes of the end of Jesse James Garrett’s keynote. There might be bits and pieces missing and I may have misunderstood things. Thanks for bearing with me.

steph-note: missed the beginning, sorry.

MS Word Displaying All Toolbars!

Word Toolbars all turned on sends the following message:

“Word processing is complicated. In fact, it’s so complicated that we, the developers of this tool, haven’t figured it out. So, we’re outsourcing that job (figuring it out) to you, our users.”

Look at video cassette recorders. They’ve come a long way these last 30 years, lots of buttons but… nobody seems to be able to set the clock, still now.

Mentions something Steve Jobs said in 1984.

Beautiful, elegant solution that works.

The product has aesthetic appeal (beautiful), maximises simplicity (elegant), has to address a genuine need/desire (solution) — many startups out there fail because they don’t address a real need — and can be used by its users, not just by us, its creators (that works).

Even MS word has started to get this. They’ve moved beyond toolbars. More simplicity. Not there yet maybe, but real progress. The new interface is much cleaner and simpler.

Last generation of video cassette recorders. Now, we have TiVo. But TiVo was only made possible by really taking a step back. Look at TiVo users: passionate. Users develop an emotional attachment to products which deliver on those four points.

Research seems to show that there is something different happening in our brains when we interact with complex technological tools. steph-note: some variety of pets? Like our interactions with other people, same mechanisms in our brains. We respond to these products as if they were people. We imagine they have personalities, moods… 12-year-old girl who kissed her iPod goodnight before going to bed on the day she got it. Or adults whose iPod breaks, go out and buy a new one, but can’t open the box for two days, because it would mean they have to say good-bye to their old, broken, companion.

iPod case “iGuy”. TiVo logo that has arms and legs.

Products who know who they are, and reflect a consistency in their behaviour.

Experiment: have users try software and evaluate it. One group, user same computer for both tasks. Group 2, different computer. Group 1 were nicer with their feedback, almost as if they didn’t want to hurt the computer’s feelings.

Diamond Rio, first mp3 player commercially available. Looked like a transformative product, so much that the record industries went to court to have it banned in the US. But nobody remembers it! Everybody remembers the iPod as the first mp3 player. Met with a lot of skepticism. (ipod = “idiots price our devices”). Too expensive, not enough features. But actually, it’s a beautiful elegant solution that works.

Developing software applications: we talk about them as data, wrapped in logic, and a user interface. User interface = shell.

But in the minds of our users: there is the user interface, and magic inside.

When we make choices about our products based on things that our users cannot see, we’re going in the wrong direction.

But this is changing. The web (2.0) is leading the way. We make decisions about the user interface first, and allow those decisions to drive technological choices. “Designing from the outside in.” (O’Reilly)

Web 2.0 companies are not being driven by a business or technology strategy, but by an experience strategy.

The experience is the product.

Any technological choices that do not reinforce the experience that we want the users to have of the product are the wrong decision.

Kathy Sierra: Keynote (Web2.0Expo, Berlin) [en]

[fr] Mes notes de la keynote de Kathy Sierra.

Here are my notes of Kathy Sierra’s keynote, quite different from yesterday’s workshop, which I also blogged. My notes are probably incomplete in some spots and may contain mistakes.

Finding Web 2.0 Opportunities (Kathy Sierra)

1) reduce guilt and fear

most of the time, people feel like they suck, like it’s their fault. Sometimes, making the product easier is not always the answer. We need to reduce that kind of feeling/face. How about using facial recognition to see when users are pulling a face? Or even simpler, have a WTF?! button.

Help, FAQ and user manuals do not solve WTF faces. People writing help and FAQ think you’re happy to use the softwa
re and a bit intellectually curious about using the software. Not true! Assume that most of the time, our users feel in WTF mode. Even if your software is easy to use, it might be they’re pulling that face because of what they’re trying to do with your tool.

FAQ/Help aren’t wrong, they’re written for the wrong place of the curve.

Recognise that people are miserable, feel they suck at what they’re trying to learn. Let people off the hook for feeling bad that it’s their fault. Books teaching something shouldn’t make people think they’re stupid.

“Appartments for rent: dog required.” In the US, so hard to find a place to live when you have a dog.

“Please walk on the grass, hug the trees, smell the roses.”

“What kind of genius? young, early, or late bloomer (Doc Searls).”

A lot of 2.0 stuff (like Twitter) increases the guilt, because you have to keep up. steph-note: I realise I’ve been letting myself off the hook quite a lot regarding that.

Being an expert is generally just a matter of focus, not a matter of natural talent.

How to write a bestseller? Choose a title that lets people off the hook. “The perfect mess” or “Everything bad is good for you.”

2) Don’t “bait and switch” on the relationship

Don’t start out all nice and interested and seductive, and in the end push away. How do you treat your ongoing users vs. the users you want to capture? The difference between how sales reps treat customers or prospects is often huge and the wrong way around. Documentation quality.

Web 2.0 Expo 3

Take the marketing budget and throw it into user learning. It’s not always a problem to not have a marketing budget: teach your users to kick ass.

Every time you think of something that you might do for marketing, think about what would happen if you applied that to user learning. Huge example: camera brochures and material. Glossy brochures that are all about taking great photos — which is the reason people buy cameras! — and afterwards, manuals that teach me to be a tool expert, which is not what I want!

Serendipity Curve. Introduce randomness. Excessive customisation and tailoring strips out the delight of discovering something unusual and unexpected. Encourage people to make connections between your stuff and seemingly unrelated things.

Roger von Oech’s “Creative Whack Pack” (steph-note: looks really good!)

3) Make it real/Make it important

Why are we here? We still need physical presence despite all our technology. A huge part of our brain is devoted to our hands and mouth.

Smell is really important steph-note: shows cup of coffee on slide, it does something to our brain but not just smell. Skin was meant to be used.

A real present trumps a virtual gift (not that the latter isn’t meaningful!!) Think about how you can give something in the real world to your users, related to your product. In the US, the UPS guy is a hero. He’s a sex-symbol. Physically impossible to not smile when you see the Amazon box on your doorstep.

Philosophy of Electric Rain:

  • users should do something kick ass within 20 minutes
  • the process of buying, downloading and installing feel like you’re getting a special present. E.g. a real human answers the tech support. We don’t expect that!

Unboxing! “geek unpacking porn” Look at pictures of other people unpacking their new geek toy. steph-note: I almost did that with a Flickr photo of my new macbook and roomba.

People are actually coming up with ways to make those pictures more seductive. These things matter!!

Even if you’re working in bits, and all “virtual”, find something you can send to your users offline. People always care about the t-shirts.

T-shirt First Development. ThinkGeek. It’s not enough to send it to them, give them a way to show that they’re wearing the t-shirt.

Don’t make this mistake:

Web 2.0 Expo 4

There are women or smaller men in your audience. They won’t feel like they kick ass in an XXL t-shirt. Yes, even if it’s not cost-effective.

Remember we’re not ready to leave our bodies behind just yet. “Real” sex still trumps the “virtual” kind…

Kathy Sierra: Creating Passionate Users (Web2.0Expo, Berlin) [en]

[fr] Workshop de 3 heures animé par Kathy Sierra. Comment rendre ses utilisateurs passionnés.

Disclaimer: theses are just my live notes of Kathy Sierra‘s workshop. Though I try to be accurate, they may contain mistakes or be incomplete. Please don’t hesitate to link to other notes, reviews, or relevant material in the comments.

Not passion like being attached to your iPod, but more passion like how we invest energy into our hobbies.

Web 2.0 Expo, Kathy Sierra 2

There are techniques we can use to achieve that…

Kathy is going to draw techniques from many domains, who all have a piece of the puzzle:

  • hollywood 🙂
  • cognitive science
  • neurobiology
  • psychology
  • learning theory
  • design
  • game design
  • advertising

Web 2.0 Expo, Kathy Sierra 3

Passion: music, photography… that level of passion. Think of something that you have a passion for, or have had a passion for. Here’s how to tell if it was: you want to keep getting better, you want to learn more, practice more… that’s a real passion.

People with a passion:

  • show off
  • learn
  • continuously improve
  • spend time

Reverse-engineering passion. Look at common attributes of things people have a passion about (e.g. people want to keep learning and getting better). How can we drive passion rather than wait for it to happen?

Where there is passion… there is a user kicking ass. Nobody really get a passion about something they suck at. Challenge: what to do in the period where users still suck.

One of the reasons people pursue passions is that it gives them a higher resolution experience. You see things differently when you’re passionate. You see more details, things that others don’t notice.

The Kick Ass Curve:

Web 2.0 Expo, Kathy Sierra 5

Between the first time and the suck threshold is the real challenge, because that’s where we’ll lose people. Strategies to keep pushing our users up that curve, and not just when they get past the point where they no longer suck. The faster you can get your users past the Suck Threshold, the more likely you are to have passionate users.

So, how fast can we do that, and how?

But… the problem is that people don’t want to be experts at a tool, but experts at what they can do with the tool. They use the tools to do something. That explains why documentation is all wrong, because it focuses on teaching the tool.

Good example: photography site which focuses on the results people want, the photos they want to be able to take, instead of on the camera.

Kathy, seeing slow-shutter speed photo of waterfall, understands why she needs to ditch her point-and-shoot, because she needs control on the shutter speed to be able to take those kind of pictures. And that’s what she wants to be able to do.

We don’t want to be tool experts.

Before our customers buy, we treat them well with glossy brochures, and as soon as they buy they get an unpalatable tech manual for their camera.

Web 2.0 Expo, Kathy Sierra 6

What if your product isn’t something people can use to do really cool things? (Showing a picture of Coldplay.) If we look, we can see what people might be able to use it for that they’ll get excited about. So, Chris Martin of Coldplay is very interested in fair trade. He helps people get involved in the cause. (Oxfam.) A band can help people become passionate about their work, their music.

Another example: Red Bull. Kathy likes Red Bull, but she doesn’t want to become an expert at what’s in it! So Red Bull are helping people become passionate about other stuff, not the drink — music, for example.

Bottom line: whatever you have, whatever your business is, you can have passionate users. They don’t have to be passionate about your product.

Imagine Nikon sets up a really cool site to teach people about photography. Learning is a drug for the brain, so this feel-good feeling is going to be linked to Nikon, who is behind the site. Passion spills back to the tool/brand. (That was a bit of psychology…)

THE important question: what do (or can) you help your users kick ass at? (answers are not: the tool, the interface). The stuff your tool allows to do.

What if you make trash bags? Well, you can sponsor a festival, do something completely unrelated. But you could have little films with creative use of trash bags, and then you create tutorials to teach people to make kick-ass films with those trash bags. (steph-note: sounds way more lame when I write it than when Kathy says it.)

Big question: how do we actually make that happen?

It all starts in the user’s head, and the user’s brain is not our friend.

Our brain has a little logic, and lots of emotion. Our brain thinks we’re still cavemen. Our brain has a big crap filter, and not much gets through. Your brain cares about that which you feel. Chemistry! Mind has one agenda, but brain has another. Imagine, trying to learn from a dry textbook even though committed to studies and the test… but the brain isn’t into it. Any moment though, something could wake the brain up (smell of pizza, cute guy).

What does the brain care about?

  • things that are just a little weird, that are just out of expectations
  • scary things
  • sex
  • little young helpless innocent things (baby, puppy)
  • play, joy
  • humour (bunny suicides…)
  • faces
  • things that are not quite resolved, some mystery, want to know the rest of the story (hand hiding face)

To keep people reading, you need to make sure their brain stays awake.

The brain doesn’t care about

  • generic clichés (bride and groom kissing, no-no, whereas groom biting bride’s shoulder…)

Trick the brain!

Web 2.0 Expo, Kathy Sierra 7

Conversational beats formal every time. It can be subtle!! steph-note: this what I try to explain to people about writing in “blog style”.

Leading theory about that: the brain can’t tell the difference between a real conversation and something written in conversational tone. “God, a conversation, I have to keep up my end, pay attention.”

Rule: talk to the brain, not to the mind.

To read: “A mind of its own” by Cordelia Fine (How your Brain Distorts and Decieves)

Prepare the brain so that when people see this they think “ew, bad”:

Web 2.0 Expo, Kathy Sierra 8

Hey… all this was just about getting people’s attention! We still need to get past the Suck Threshold.

Where are my users on the suck / kick ass curve? If your tool is easy to learn, can they spend a lifetime getting better at what they do with it?

Who do snowboarders go back the second day? The first is so awful! Because there is this picture in their mind of what it’ll be like to kick ass at it. People persevere because they have an idea in their head of what it will be to be really good at it. Another reason is that they see a path, a series of steps to getting there.

People stick at something that’s stuff because there is:

  • compelling picture
  • clear path
  • easy first step

How easy depends on how much value they perceive they’ll get. Sometimes just giving an e-mail address is too big a step.

Who is describing this “compelling picture” for your users?

Why? Who cares? So what? If people are to learn something, they have to keep turning the pages of the book. We need to get past the brain’s crap filter when we’re explaining.

It’s an exercise:

  • My tool does X
  • So what?
  • Well, if you can do X, then it means you can do Y
  • And so what?
  • etc…

(when you feel like killing the other for being so thick, you’re getting close t the meaningful stuff: “you’ll never have sex again”, “you’ll lose your job”)

Keep asking why.

Now, we need to get users to learn.

Learning increases resolution.

“RTFM” expresses how we feel about our users. If you want them to RTFM, make a better FM!

All the money goes to enticing, sexy, motivating, advertising brochures. And after… when it’s time to learn, nothing left.

Learning Theory

Facts — information — understanding. Need more understanding. We tend to teach too many facts. steph-note: cutlery noise from outside coming in through open door is really annoying me

The more they understand, the less they need to memorize.

Because a choice is asked, our brain starts doing more processing.

Smackdown Model: throw two equally compelling, strong, arguments at somebody, and the brain is forced to start processing.

Words + pictures > words. Even drawing a picture on a napkin and taking a photograph of it.

Look for “oh crap!” and “oh cool” moments.

steph-note: tiring

“just in time” is more effective than “just in case” learning. But be careful, you don’t want to always prevent them from scraping their knees.

Who can help you help your users learn? Where are the resources? steph-note: other users! Kathy: “community” 😉

However, nothing of that matters unless you manage to keep your users engaged.

steph-note: break-time, good!

Should read the book “Flow, The Psychology of Optimal Experience”.

Web 2.0 Expo, Kathy Sierra 10

What is it like to be in the flow state? You don’t really notice that time is passing. If you have lost time, either you were abducted by aliens, or you were in the flow state. You just keep going. For people to be in the flow state, a very delicate balance needs to be achieved:

  • knowledge and skill
  • challenge

Web 2.0 Expo, Kathy Sierra 11

What turns the brain on?

  • discovery
  • challenge
  • narrative
  • self-expression
  • social framework
  • cognitive arousal
  • thrill
  • sensation
  • triumph
  • accomplishment
  • fantasy
  • fun (?)

Fun does not have to mean funny.

What breaks flow state, state of enchantment? Think of the user as under a spell. Suddenly realising that they’re using this tool to achieve what they’re doing. (Oh, crap, where’s that button?)

Web 2.0 Expo, Kathy Sierra 12

Don’t make me think about the wrong thing. Just make me think about the interesting stuff. Make it hard to do the wrong thing, and easy and natural to do the right thing.

Techniques to make the flow state happen and remain there. How do we keep them coming back?

Nobody does this better than game developers. Video games! Always trying to get to the next level.

User experience Spiral:

Web 2.0 Expo, Kathy Sierra 13

Motivational milestones. Make sure the users know where they’re going.

Differences between girls and boys and video games:

  • boys: getting to the next level is the aim
  • girls: getting to the next level, but what for?

Are there any new superpowers that I’ll get at the next level? If done right, the payoff gets bigger for each level. Gives you a chance to paint the next compelling picture of what they’ll be able to do.

Web 2.0 Expo, Kathy Sierra 14

Levels have to be small at the start.

What are levels for web development?
Online communities?
Flickr users?

What are your level superpowers?

Frequent rewards. Lots of small benefits. User as hero. Who/what is the helpful sidekick/mentor? How will the hero be changed?

The Tribe…

e.g. 37 signals: “getting real” — so people who are into 37 signals products identify with this “getting real” attitude. Mac: “think different”.

Music video, shot just in living-room and shows what all the money that could have gone into making it could be used for in the third world:

What part of your product is (or could be) part of a user’s identity? (meaning)

Site where people photograph their iPod in various settings. People holding one company’s book in various locations.

So, how can your users show that they belong to the tribe?

If you want them to talk… give them something to talk about. LOTR stuff in calendar OSX (steph-note: dig around that).

e.g. on cover of one of Kathy’s series books, same girl as on this site— lots of talk!

Figuring things out (insider info) is social currency (whuffie). Everyone loves to be the one to tell you about… X.

Find interesting stories. Give users treats. Things that they can talk about. Give them social currency that they can use elsewhere. Legends, stories, people. Where there is passion, there are people.

Once you get to a certain level, people start trying to figure out who will play you in the movies 😉

founder/creation stories, user-as-hero stories? You don’t want to make it about you… people are passionate about themselves. First thing to look at: testimonials. They should be about how great these users are as a result of using the products. People want to see themselves reflected in the testimonials.(Not about the product of the founders.) The more first person language in reviews (about a book, eg.), the better. What’s important is if something good happened to the user, not what they think about you.

Community

  • forums?
  • study groups?

at the least, a blog with comments…

Javaranch registration terms of service: “Be nice”. Users have to agree to that. If people aren’t nice, how do you get them to answer and ask questions? How quickly can you make it possible for people to ask and answer questions?

No dumb questions. Don’t allow people to say “that’s already been answered 50 times”. It’s OK to ask a question again. Never shun somebody for asking a question.

But the most important factor is actually no dumb answers. Try to get people to convert to answerers as fast as possible. Information on “how to answer questions”. When people answer a question, make sure they feel encouraged because they’ve done it.

Tutorials on how to make tutorials.

How to know you’ve got passionate users

When people stop criticising you, but criticise your users. A bit unsettling, but that means you have passionate users. “Cult?” “Sheep?”

Then, give your users some sort of defensive weapon.

If you try to satisfy everybody, you delight and inspire nobody.

Tips and trouble on the road to passionate users

Levelled products (iMovie is free, FinalCut isn’t — so you start with iMovie thinking you’ll never need more, and at some point you’ll outgrow it; problem though: big gap between the two from a usability point of view). Good strategy, however.

“Dignity is Deadly”

Web 2.0 Expo, Kathy Sierra 15

Startup: individuals
Corporate: consensus

Apes become smarter as they work together. Humans become dumber as they work together. (“Wisdom of Crowds”)

We tend to think our ideas are amazing, but our users think they’re tolerable.

Web 2.0 Expo, Kathy Sierra 16

Listening to users: what they say is not what they want.

Web 2.0 Expo, Kathy Sierra 17

User priorities

Web 2.0 Expo, Kathy Sierra 18

When you ask them to prioritize, and when you ask them to also explain, you get very different results.

The greatest cause of user pain:

Web 2.0 Expo, Kathy Sierra 19

Making things better can in fact make them worse. If a simple thing is nice and flow-inducing… No need to improve it by adding tons of features.

Web 2.0 Expo, Kathy Sierra 20

Web 2.0 Expo, Kathy Sierra 21

The Secret…

It doesn’t matter what they think about you… (It’s not about you, and it’s not about what you do). All that matters is how they feel about themselves as a result of their interaction with you, your product, your company… steph-note: thinking that Lush testimonials are spot-on, they really have passionate users and I’m one of them.

The user must have an “I rule!” experience.

Web 2.0 Expo, Kathy Sierra 22

Remember: your users are real people.

Thank you, Kathy. It was great to have a chance to see you.

Web 2.0 Expo, Kathy Sierra 23

Physical, Digital, Categories, Tags, Experts… [en]

[fr] Le numérique révolutionne la façon dont nous organisons l'information. "Une place pour chaque chose, et chaque chose à sa place" vaut pour les objects physiques. Cette excellente petite vidéo démontre ces changements. C'est en anglais, mais il n'y a rien à écouter (sauf de la musique) -- il suffit de lire.

If you’re still a bit in a fuzz about how exactly the internet is revolutionizing the way we store and retrieve information, this great little video should help. It’s pretty fast-paced (watch it twice if necessary) and the music is very nice.

Thanks to Euan Semple for pointing it out.

BarCamp Lausanne: Privacy (Julien Freudiger) [fr]

[en] Privacy... a tricky issue, as ever.

“Nothing to hide.” Est-ce que ça justifie de ne pas se préoccuper de privacy?

Julien fait une thèse sur le sujet. steph-note: j’espère qu’il ouvre un blog pour documenter sa recherche!

BarCamp Lausanne 33

Surveillance:

  • CCTV (on peut reconnaître quelqu’un à sa démarche => porter des schlaps) => et peu efficace côté incidence sur le crime
  • Wiretapping (CALEA) conversations téléphoniques + tous les ISP doivent laisser des portes ouvertes. Mais Skype, pas, car Skype est européen. Donc pour le moment, OK.
  • Banques (SWIFT): transactions internationales… les USA arrivent à contrôler les sommes d’argent transférées dans et hors des USA, alors que c’est interdit dans les autres pays.
  • Avions: doivent donner numéro de carte de crédit, peuvent fouiller nos affaires…

Ça semble un peu dramatique… ça fait beaucoup d’information! La NSA a un des systèmes informatiques les plus puissants au monde… caché quelque part.

=> Privacy Enhancing Technologies

  • Internet Anonymity: Tor
  • Data Confidentiality: PGP (bien, mais trop complexe)

steph-note: sympa, ce MacBook Pro sur lequel je tape… clavier très agréable… et pas si lourd!

Ces services fournissant l’anonymat sont aussi des sortes d’aimants attirant beaucoup de traffic “sale”, ou potentiellement illégaux. (e.g. gens qui utilisent Tor pour faire du P2P…)

Deux systèmes qui marchent bien mais que personne n’utilise.

Travail de doctorat de Julien: trouver des motivations économiques pour que les gens utilisent de tels services. Lack of concern. Lots of info on social networks. “Nothing to hide.”

Privacy vs. Security: si on renonce à notre privacy, on donne plus d’informations pour aider le gouvernement à nous garder en sécurity. Comme: la torture est interdite, mais si on demande aux gens s’ils tortureraient une personne pour en sauver 1000, bien sûr que oui.

BarCamp Lausanne 34

Terrorisme: aux USA, en fait, on “torture” des millions pour préserver quelques miliers. Les USA disent qu’ils ont gagné la guerre froide car ils avaient la liberté… Mais maintenant? le contraire…

Le fameux “nothing to hide” argument: steph-note: guilty. On perd la conscience d’être regardés/observés, sur Internet. La privacy n’est pas important que lorsqu’on a des secrets. C’est pas pour les secrets, ou les choses qu’on a à cacher. Ce n’est qu’un aspect de la privacy. “Web of things.”

Lorsqu’on perd des petites quantités de privacy, pour (on espère) gagner en security. Métaphone: Orwell; Kafka. Kafka a imaginé une société qui en sait plus sur nous que nous-même. Elle sait prévoir ce qu’on va faire — perte du sens de contrôle sur notre propre vie. Une petite série d’actes mineurs qui s’aditionnent. Sur internet, si on dit une chose une fois, c’est dit pour de bon. Très difficile de retirer de l’information.

La privacy c’est quelque chose de pluriel.

Data:

  • collection
  • processing
  • dissemination

Risque potentiel. Possibilité aussi que toutes ces données à notres sujet soient mal interprétées.

Valeur sociale de la privacy. Nécessaire à la construction de l’identité. Chacun a un espace de liberté dont la société bénéficie. Protéger la privacy = devoir social.

“Torturing Our Privacy”

BarCamp Lausanne 35

Où sont les abus?

WiFi: AP data sniffing. Pas très difficile de déterminer qui utilise un réseau (e.g. via l’accès à son serveur mail). Beaucoup de choses sont en clair. (Rajouter le s à http:// quand on est dans gmail…)
Social community phishing (“can I be your friend?”)
L’an dernier, il y a eu plus d’argent gagné par le cybercrime que le traffic de drogue.
Location tracking.

Compliqué: c’est utile pour moi comme utilisatrice, cette ouverture. Donc je n’ai pas envie d’y renoncer… mais quand même, comment protéger ma vie privée contre les abus, tout en l’ouvrant pour ma communauté.

Passer les captcha pour les spammeurs: ils les intègrent dans les sites pornos, donc les visiteurs les tapent pour voir l’image suivante, mais en fait sont en train de valider un spam quelque part.

ORG, EFF.

BarCamp Lausanne 36

BarCamp Lausanne: Facebook (Raphaël Briner) [fr]

70% des gens inscrits à BarCamp Lausanne sont sur Facebook. 30 contacts (médiane). Idée intéressante: donner à Facebook un fichier texte avec des noms, et en retirer une liste des relations etc. entre ces gens.

BarCamp Lausanne 24

Raphaël est sur Facebook depuis février 2007 (steph-note: je vous mets une saisie d’écran de son profil? 😉), n’a pas fait grand chose en deux mois. Juillet/août: lancement des applications Facebook => pénétration++.

Audience européenne a triplé en 2 mois. 42’000 en Suisse. Tilllate a des soucis à se faire. (Si ça continue, FB aura 200’000 utilisateurs en Suisse à Noël — autant que Tilllate.)

Design graphique old school en L. 5 tailles de typo, minimal. [analyse détaillée du design de Facebook.] Petits détails soignés, tout de même, malgré un design super classique.

Développé en PHP. Marche relativement bien.

BarCamp Lausanne 29

Objects à usage social principalement. Applications: plate-forme géniale pour ça.

Par rapport à MySpace, possibilité de se différencier: pas de MP3 illégaux, d’images dont les droits ne sont pas respectés, de vidéos piratées — ou uniquement via des applications tierces.

Intérêt de Facebook: pour l’individu, générer du “bruit” diffusé à un public restreint. Evite les problèmes de droit de distribution.

steph-note: intéressant comme présentation, bonne analyse du design (même si j’ai pas tout remis ici, ça me dépasse un peu j’avoue) — mais une analyse des enjeux sociaux est à mon avis à faire. Je me rends compte que j’ai des articles à écrire sur ce sujet en français.

BarCamp Lausanne: Marketing, communication etc. (Sandrine Szabo) [fr]

[en] Live notes of a talk on marketing at BarCamp Lausanne.

mes notes, avec toutes les imperfections d’usage.

Sandrine se retrouve souvent à l’interface entre le monde de la technologie et celui du marketing et la communication.

BarCamp Lausanne 17

“Le marketing, c’est comme la soupe: on aime pas forcément toujours, mais faut en manger quand même.”

Le marketing c’est indispensable, et comme la communication, on le fait déjà naturellement, sans s’en rendre compte. Une question de vocabulaire.

Situation type: “j’ai fait un super truc, mais je sais pas pourquoi, ça prend pas” — en général, symptôme d’un manque côté marketing/communication.

Soucis courants quand on lance un projet:

BarCamp Lausanne 18

3 aspects principaux d’un projet:

  • savoir-faire (technique, management)
  • faire savoir (se mettre en valeur, expliquer, faire qu’on en parle — communication, quoi)
  • ressources (finances)

Ce qui fera la différence (pour le deuxième point):

  • branding: être concis dans l’explication du but du projet. Les gens ont une mémoire de poisson rouge, et pour qu’ils retiennent les choses, il faut les percuter, en s’adressant à leurs émotions. Donc, y accrocher des valeurs. Choisir un nom court, facile, et transportable pour qu’il soit viral. steph-note: à mon avis, avant de s’intéresser au nom, il faut avoir quelque chose derrière — c’est beaucoup plus important que le nom ou le branding.
  • l’usage, pas le technique: c’est pas les fonctionnalités qui importent, c’est ce que les gens vont en faire.
  • mettre en avant ce qui vous rend spécial: qu’est-ce qui vous différencie des autres? Y rendre les gens attentifs. steph-note: marketing 101.
  • créer un comité de soutien: les outils pour faire ça aujourd’hui sont colossaux. Créer une communauté. Il faut chercher à la créer, l’entretenir, s’assurer qu’elle a son comptant d’informations (?). Tenir les autres au courant de ce qu’on fait. Y’a jamais d’overdose de communication, on ne communique jamais trop. steph-note: pas d’accord. Il n’y a que de la mauvaise communication.
  • rendre ce qui est complexe, simple: ce qu’on fait doit améliorer les choses; rendre la technique élégante. Simplifier au niveau de la communication.
  • parler 1 fois, écouter 2: dans la communication, l’élément le plus important c’est l’interactivité. Règles en communication: être pertinent, constant, progressif. Les gens se sentent très peu écoutés de nos jours. Etre à l’écoute, nous permet de récolter des argument très utiles pour la suite.
  • impliquer les autres: à tous les stades du projet, demander toujours l’avis des gens. Plus les gens participent, plus ils seront confortés dans l’idée que ce qu’on fait est une bonne chose.
  • être transparent: faire ce qu’on dit, dire ce qu’on fait. C’est pas toujours facile. Ex: Sandrine sur son blog, s’est retrouvée parfois à pas savoir comment dire une information.
  • soigner ses supporters: très important. Il faut les bichonner sans arrêt (pas les soudoyer ou les corrompre, quand même). Si on réussit ce qu’on fait, c’est par eux que va passer la communication virale. Si ce qu’on fait est suffisamment mémorable et réussi, c’est eux qui en parleront aux autres. C’est pour ça que les messages courts sont importants. Ça rend plus facile pour les supporters de les transporter.
  • faites ce que vous savez faire de mieux: ceci est très important, mais c’est un des dix points! Les points d’avant mettent ceci en valeur. En être convaincu soi-même. On sait ce qu’on sait faire, et ce qu’on ne sait pas faire. Faire que les gens soient conscients.

Discussion: Sandrine et moi sommes en désaccord avec l’importance du concept de “message”. Pour moi, les stratégies développées plus haut restent dans la même conception fatiguée de “marketing comme message”. Personne n’a envie d’écouter un “message”. Les relations priment sur le message. Oui, bien sûr, par mes actes, je communique des choses (“on ne peut pas ne pas communiquer”). Mais je crois personellement que pour “changer la façon dont nos projets sont perçus”, il faut dépasser cette notion de “message”. Quand je raconte ce que je fais dans mon projet sur mon blog, je ne suis pas en train de fabriquer un “message” (même inconsciemment), je suis en train de raconter une histoire. De parler en tant qu’être humain. Et ça c’est mille fois plus important que tout ce qu’on peut dire autour de “rendre un message viral”. cf. les notes de ma conférence sur les blogs en entreprise, où j’explique l’importance des constats du Cluetrain Manifesto. Pour moi, on est resté coincés (dans cette présentation) dans une conception “pré-Cluetrain” du marketing et de la communication. Il faut abandonner ce concept de “message” plutôt qu’essayer de le sauver à tout prix et de l’intégrer dans quelque chose où il n’a pas de place. On s’en portera bien mieux. Et en plus j’ai faim.

BarCamp Lausanne: Introduction à Django (Mathieu Meylan) [fr]

[en] An introduction to Django at BarCamp Lausanne.

J’ai pas mal entendu parler de Django, mais encore pas eu le temps de m’y intéresser. C’est l’occasion! Voici mes notes de la session.

Mathieu travaille chez ElectronLibre, et suit le développement de Django depuis 5 mois.

BarCamp Lausanne 13

  • objectifs et intérêts de Django
  • mécanisme
  • parcours d’une requête

Framework web. Permet, grâce à bibliothèques, de développer du web de façon plus rapide. Django permet de segmenter la conception du site. En gros, on gagne du temps, c’est assez facile à apprendre. Adapté à tous types de site web (y compris multilangue). steph-note: j’aimerais voir comment ça marche!

Django, en fait, c’est comme Rails pour Ruby, c’est un framework Python. Rails est un peu plus complexe à apprendre et intègre AJAX.

[présentation des caractéristiques techniques de Django]

Le niveau requis en Python dépend de la complexité de l’application qu’on veut développer.

Exemples:

  • http://www.lawrence.com/
  • http://www.washingtonpost.com/
  • http://chicagocrime.org/
  • http://www.tabblo.com/studio/
  • http://wattwatt.com/

steph-note: exemples de code, ça a l’air abordable.

Certaines vues sont si courantes (vue par date, ajout/mise à jour/suppression) qu’elles sont inclues telles quelles dans Django — donc pas besoin d’écrire de code pour les utiliser.

Possible de produire autre chose que du HTML/XML: e-mails, texte brut…

steph-note: en voyant tout ça, je me demande combien de travail ça nécessiterait de re-créer WordPress (par exemple) avec un framework comme ça, et ce qu’on perdrait par rapport à PHP/MySQL

Intérêt grandissant pour Django.

Pour démarrer:

  • djangoproject.com
  • djangobook.com
  • djangosnippets.org
  • django-fr.org (fr)
  • Bien débuter avec Django chez biologeek.com (fr)

Discussion:

  • refaire WP avec Django? faisable, mais moyennement intéressant. Django, c’est pour quand on a des besoins spécifiques, faire un site “from scratch”.
  • charge: java/tomcat, 6 machines — passé sous Django, une machine.
  • possible d’utiliser Akismet avec un site développé avec Django