Télévision et lancement [fr]

N’oubliez pas de regarder Mise au Point ce soir sur la TSR. Je lance Stephanie-Booth.com, mon site “business”.

Il y a des moments dans la vie où les événements semblent s’être donné le mot pour vous pousser gentiment dans la bonne direction. Ces temps, je crois que c’est le cas pour moi.

Aujourd’hui, je me retrouve pour la première fois de ma vie à  la télévision (et en direct, s’il-vous-plaît!) dans l’émission Mise au Point (TSR1, 20h00). Et aujourd’hui, j’ai l’honneur et l’avantage de vous présenter Stephanie-Booth.com. Je m’explique.

Le journalisme et le consulting indépendant sont deux voies professionnelles qui m’attirent depuis longtemps. Outre le fait que je suis ces jours au bénéfice d’un petit peu de “célébrité médiatique”, je me retrouve de plus en plus régulièrement à  présenter internet et les weblogs à  des gens qui désirent faire leur site web. Tout le feedback positif et les encouragements que j’ai reçus ces derniers temps sur mes activités m’incitent à  prendre la balle au bond, si on peut dire, et à  me lancer.

Stephanie-Booth.com est donc mon site “orienté business”. Il donne accès à  mes diverses activités en ligne, à  mon profil “professionnel”, et présente les services que j’ai l’intention d’offrir. N’hésitez pas à  me demander des détails où à  me donner du feedback sur ce nouveau site (sauf si c’est pour critiquer le rose).

(Ah oui, j’allais oublier: je ne quitte pas l’enseignement! A terme, j’espère combiner un poste à  temps partiel dans l’enseignement avec une activité indépendante.)

Edit 13h20: L’émission sera en ligne une demi-heure après la fin de la diffusion. Merci de mettre l’URL en commentaire pour les autres si vous trouvez où c’est!

On Tags and Ontologies [en]

Quote from Clay Shirky on the suckiness of ontologies, and how tags-labels are better for classifying ideas.

[fr] Le problème avec les ontologies ou les systèmes de classement hiérarchiques est qu'ils doivent être conçus de façon à  accommoder tout élément à  classer pouvant surgir dans le futur. Les tags-étiquettes créent une structure multi-dimentionelle élastique, qui s'adapte à  mesure à  ce qu'on y classe.

This last point is key — the number one fucked up thing about ontology (don’t get me started, the suckiness of ontology is going to be my ETech talk this year…), but, as I say, the number one thing, out of a rich list of such things, is the need to declare today what contains what as a prediction about the future. Let’s say I have a bunch of books on art and creativity, and no other books on creativity. Books about creativity are, for the moment, a subset of art books, which are a subset of all books.

Then I get a book about creativity in engineering. Ruh roh. I either break my ontology, or I have to separate the books on creativity, because when I did the earlier nesting, I didn’t know there would be books on creativity in engineering. A system that requires you to predict the future up front is guaranteed to get worse over time.

And the reason ontology has been even a moderately good idea for the last few hundred years is that the physical fact of books forces you to predict the future. You have to put a book somewhere when you get it, and as you get more books, you can neither reshelve constantly, nor buy enough copies of any given book to file it on all dimensions you might want to search for it on later.

Ontology is a good way to organize objects, in other words, but it is a terrible way to organize ideas, and in the period between the invention of the printing press and the invention of the symlink, we were forced to optimize for the storage and retrieval of objects, not ideas. Now, though, we can scrap of the stupid hack of modeling our worldview on the dictates of shelf space. One day the concept of creativity can be a subset of a larger category, and the next day it can become a slice that cuts across several categories. In hierarchy land, this is a crisis; in tag land, it’s an operation so simple it hardly merits comment.

Clay Shirky, Many-to-Many

Yes!

Taking Collaborative Notes at BlogTalk [en]

A detailed write-up of the collective note-taking operation we ran at BlogTalk. We took notes together using SubEthaEdit and then posted them to a wiki so that they can be further annotated. The story, and questions this experience raises for me.

As many of you now know, a bunch of us were taking notes together with SubEthaEdit during the BlogTalk 2.0 conference. In this post, I’d like to give some details about what we did, how we did it, and what can be said or learnt about our experience.

I’d like to stress that this was not my idea. I think this collaborative note-taking is a very good example of what happens when you put a bunch of people together with ideas and resources: the result really belongs to all, and credit should go to the group (even though in this case, I don’t think I can identify all the members of this “group”).

The Story

At the beginning of the conference, I was discovering the joys of RendezVous and eagerly saying hi to the small dozen of people I could see online. Sometime during the first panel, I was asked (by Cyprien?) if I had SubEthaEdit, because they were using that to take notes. I downloaded it (thus contributing to the death of wifi and bandwidth), and after a brief struggle managed to display a RendezVous list of users on the network (shortcut: Cmd-K) currently running SubEthaEdit.

I joined Lee Bryant‘s document, which was open for read/write sharing. It contained text (what a surprise!) mainly highlighted in yellow (Lee’s colour, the main note-taker). We were four or five in there at that point. (From Lee’s first publication of the notes I gather that the two others were Roland and Stephan — or rather Leo on Stephan’s computer, like later in the day?) It took a couple of minutes for me to feel comfortable in there, and I started contributing by adding a few links I knew of, on the subject of video blogs. The act of writing in the document made me feel quickly at home with the other note-takers. At some point, I started actively pestering those logged into RendezVous so that they would join us if they had SubEthaEdit (particularly if they were already visible in SubEthaEdit!)

Lee wasn’t there at the beginning of the third panel, so I opened up a document myself in SubEthaEdit, and with a little help managed to open it up to others for reading and writing (File > Access Control > Read/Write) and “announce” it so that other participants could see it. There had already been some hurried talk of publishing our notes, and at some point, Suw (who was keeping up with what was going on on my screen) suggested we should publish them on a wiki. After a quick check with other participants (and with Suw: “you don’t think Joi would mind, do you?”), I grabbed Joi’s wiki and started creating pages and pasting the notes into them.

We continued like that throughout the afternoon and into the next day. As soon as a speaker would have finished and the note-taking seemed to stop, I would copy and paste everything into the wiki.

Update 17:30: Malte took a screenshot of us taking notes in SubEthaEdit. It will give you a good idea of what it was like.

Reflecting on the Experience

So, now that I have told you the story, what can be said about the way we worked together during this conference? I’m trying to raise questions here, and would be really interested in hearing what others have to say.

Working as a team to take notes has clear advantages: Lee was able to go out and get coffee, and catch up with the notes when he came back. When I couldn’t type anymore, Suw took my computer over and literally transcribed the last couple of panels (OK, that could have been done without the collaborative note-taking, but I had to fit it in somewhere.)

Still in the “team theme”, different roles can be taken by the note-takers: sometimes there is a main note-taker (I noticed this had a tendancy to happen when people wrote long sentences, but there might be other factors — any theories on this welcome), sometimes a few people “share” the main note-taking. Some people will correct typos, and rearrange formatting, adding titles, indenting, adding outside links. Some people add personal comments, notes, questions. Others try to round up more participants or spend half a talk fighting with wiki pages 😉

At one point, I felt a little bad as I was missing out on the current talk with all my wiki-activity. But as Suw says about being part of the hivemind, I don’t think it matters. I acted as a facilitator. I brought out notes to people who were not at the conference. I allowed those more actively taking notes to concentrate on that and not worry about the publication. I went out to try and get other/more/new people interested in collaborating with us. I said to Suw: “keep on tzping, and don’t worrz that zour y’s and z’s are all mixed up because of mz swiss kezboard layout,” while Horst patiently changed them back.

What is the ideal number of note-takers in a SubEthaEdit session? Our sessions ranged from 5-10 participants, approximately. When numbers were fewer, a higher proportion were actively participating. When they were larger, there were lots of “lurkers”. Where they watching the others type, or had they just gone off to do something else, confident that there were already enough active note-takers?

The “Lee Bryant Experiment”, which I will blog about later, set me thinking about the nature of note-taking and notes. What purpose do notes serve? Is it useful to watch others taking notes, or does it really add something when you take them yourself? How concise should good notes be? How does a transcript (what Suw was virtually doing) compare to more note-like notes?

Formatting is an issue which could be fixed. SubEthaEdit is a very raw text editor, so we note-takers tend to just indent and visually organise information on our screen. Once pasted in the wiki, though, a lot of that spatial information is lost. It got a bit better once we knew the notes would be wikified, as we integrated some wiki mark-up (like stars for lists) in our notes, from the start. What could be useful is to put a little cheat-sheet of the wiki mark-up to be used inside the SubEthaEdit document, for the note-takers (just as I defined a “chat zone” at the bottom of the working document, so that we could “meta-communicate” without parasiting the notes themselves).

Some have found the notes precious, others wonder if we were smoking anything while we took them. Nobody really seems interested in editing them now they are on the wiki — or is it still a bit too soon after the conference? Here is the Technorati page for BlogTalkViennaNotes.

How groundbreaking was what we did? How often do people take notes collaboratively with SubEthaEdit in conferences? It seemed to be a “first time” for many of the participants, so I guess it isn’t that common. Have you done it already? What is your experience of it? How often do people put up notes or transcripts of conferences on wikis?

Discipline is needed to separate the actual notes (ie, “what the conferencer said”) from the note-taker comments (ie, extra links, commentary, questions, remarks). This isn’t a big issue when a unique person is taking notes for his or her private use, but it becomes really important when more people are involved. I think that although we did do this to some extent, we were a bit sloppy about it.

Information on the wiki page, apart from the notes, should also include pointers to the official presentation the talker made available (not always easy to find!), and I’m also trying to suggest that people who have done proper write-ups of the talks (see Philipp’s write-ups, they are impressive) to add links to them from the appropriate wiki pages (Topic Exchange is great, but lacks detail).

Participants, as far as I could make out, were: Leo, Lee, Roland, Cyprien, Horst, Mark, Malte, Björn, Omar, Paolo, Suw and myself. [to be completed] (If you took part in the note-taking, please leave a comment — I’m having trouble tracking you all down.) I did see Ben Trott online in SubEthaEdit while he and Mena were giving their talk, and was tempted to invite him into our note-taking session — but I was too shy and didn’t dare. And thanks to Joi for being so generous with the Joiwiki!

Delicious! A Great Bookmarks Manager [en]

Delicious is an online bookmark manager. It makes it very easy to add and categorize bookmarks, as well as share them with other users. You can also extract your bookmarks from delicious and integrate them in your blog to create a linklog. When I say ‘easy’, I really mean it!

Now, why on earth didn’t I start using delicious ages ago, when I first stumbled upon it? Maybe it didn’t look pretty enough, and didn’t flaunt its features loudly enough for me?

A couple of days ago I paid delicious another visit. See, somebody on #joiito mentioned my Keeping the Flat Clean post, and I suddenly found there was a bunch of people from delicious visiting that article. I thought: “My, people are actually using this thing!” and signed up for an account.

So… what does delicious do? It allows you to easily add pages you visit to your bookmarks, using intelligent bookmarklets (two clicks and no typing to add a link if you want to be minimalist). This is already easier than what I have to do to add links to my LinkBall.

You can categorize your bookmarks very easily by typing words in the “tag” field of the bookmarklet. No need to define categories — delicious takes care of it all for you. You can then view your bookmarks by category or (and this is where it gets interesting) all the bookmarks marked with a same tag. Each bookmark in your list is one-click editable, and each bookmark in somebody else’s list is one-click copyable. For each link, you can also view a list of all the users who have bookmarked it.

Does it stop there? No. All the bookmark lists (by user or by tag) are available in RSS and can be subscribed to within delicious. As a user, you have an Inbox which aggregates the feeds you have subscribed to. You may subscribe to a “user feed” or a “tag (category) feed”. On top of that, bookmark lists are available in plain html, and many users have contributed various hacks which can help you integrate your bookmarks with your weblog. (Update 02.06.04: one thing you shouldn’t do, though, is simply include that HTML feed with a PHP include or an iframe, as this will cause the delicious server to be hit each time somebody views your page.)

If you aren’t a user of delicious yet, you need to go and register right now.

iBooked! [en]

I’ve finally got my iBook up and running, and I love it! A small list of things that still cause me trouble.

I got my iBook last Tuesday. I bought a router on Thursday, and I finally got everything hooked up yesterday. I’m now happily typing away on my sofa with not a cable attached, cat snuggled up next to me, xchat running in the background while iTunes is busy ripping through my CD collection.

Things have been pretty smooth. Basically, where I’ve gone wrong, it was because I was trying to do “too much” (ie, configure my wireless connection when all I had to do was turn on the Airport Extreme card). Still getting used to some of the interface particularities, but already in love with Exposé. Here’s a status update:

  • I still haven’t found the backslash key
  • the TTS functionality that comes with OSX is really horrible
  • I need to find a good feed aggregator
  • can iTunes name my music files “Artist — Song Name” instead of just “Song Name”?
  • I need to buy ViaVoice
  • need to get my fingers trained on Mac keyboard shortcuts
  • I miss Trillian, and particularly the MetaContacts feature!
  • I now know what a Disk Image is
  • damn, can’t find a keyboard shortcut for the “Back” button in Firefox
  • what’s up with July 17th in iCal?
  • one of the first things I wanted was Dock Detox to keep my bouncing application icons sedated
  • I love Quicksilver
  • Mac people are very helpful!

I’m officially in love with my iBook.

Backlinks [en]

See this nice summary page on referrer linking. I’m very tempted to try to write my own home-cooked one in PHP – you know, like, badly coded, slow, and works only on my server. Might be fun to do though.

[Update 9.7]: a certain number of hours of coding later, here is my php and mysql backlinks script source code. Enjoy!

Cartographie d'Internet [en]

Préparez-vous à  perdre un bon quart d’heure à  vous amuser avec le TouchGraph GoogleBrowser. L’applet Java met un petit moment à  charger, mais cela en vaut vraiment la peine.

Entrez l’adresse de votre site – ou du mien si vous n’avez pas d’inspiration. Vous verrez apparaître les sites “avoisinants”, sur lesquels vous pouvez cliquer à  leur tour, pour voir leurs voisins, et ainsi de suite. Explorez!

[via Somebaudy]

Feast for Geeks [en]

A few nice geeky links on the menu for today.

First, Web Standards Project II is live. Check the updated Browser Upgrade Initiative page, and see what the Dreamweaver Task Force has been up to. Stroll around the rest of the site too, there is lots of new stuff hidden everywhere.

Second, the definitive study on sizing text with CSS. See how all these browsers react to your attempts to control the size of your text (screenshots, 264 of them).

Third (and last for today), the CSS1 recommendation, annotated with relevant Mozilla bugs. Yay!