Against Threaded Conversations on Blogs [en]

[fr] J'avoue une préférence marquée pour les conversations linéaires plutôt que hierarchiques (en arbre). Les conversations linéaires génèrent peut-être moins de commentaires, mais elles ont un rapport signal/bruit plus favorable, n'encourageant pas le hors-sujet. Elles sont plus faciles à suivre et me semblent plus adaptées aux blogs.

So, now that Going Solo Lausanne is behind me and I can come back to a slightly more sane pace of life (and blogging here, hopefully), I’m starting to read blogs again, a little. Don’t hold your breath too long though, contrary to popular belief, I’ve never been much of a blog-reader.

Blog commenting

One topic I’ve read about a bit, and which is of particular interest for me, is blog commenting. Aside from the fascinating topic (I’m not kidding) of blog comment ownership, which I touched upon myself more than 18 months ago, there is the age-old debate: threaded vs. non-threaded comments.

On the backdrop of my break-up with coComment (impending, in the process, fresh) and their post about commenter’s rights, I’ve taken a closer look at Disqus. It looks promising, it does some stuff I like, but also stuff I really don’t like, like the dreaded threaded comments.

So, here’s an attempt to try to explain why I think that threaded comments in a blog context are not necessarily a good thing — although popular wisdom would have that they are “better” than normal, flat, conversations.

I did a little research to see if I could find anything solid to back up my claims (if anyone knows of proper research on these issues, let me know), but I didn’t find anything really solid. So, I’ll just have to try to make this logical enough that it can be convincing.

The appeal of threaded conversations

Threaded conversations are as old as the internet itself. Usenet, e-mail discussion list archives. So, they’re nothing new, and have been around a while.

When blogs started including comments — oh yes, there were blogs way before there were comments, and the commenting script I used on this blog was for many years a popular destination — so, when blog started including comments, those comments were not threaded (in the sense that they allowed hierarchy in the comments, or branching off, or a tree-like view).

For many years, all I saw on blogs was linear conversations, as opposed to threaded, tree-like conversations. Most forum software also functions like that.

Then, of course, with some regularity, I’ve heard people asking for plugins to make the conversations on their blogs “threaded”. And I wondered. Why the attraction to hierarchical conversations?

When we have a conversation, be it with a single other person, or around a big table, it flows in one direction: the direction of time. There is before, and there is after. One might say “you said something 10 minutes ago that I’d like to answer” — and we’re quite capable of following this kind of conversation. We do it every day.

If we chat, be it on IRC or on IM, or any other kind of chatroom, we know that there are often multiple intertwined conversations going on at the same time. With a bit of practice, it doesn’t bother us too much. But the important point remains: the conversation is ordered chronologically.

So, be it offline or online, most of the conversations we have are time-ordered.

I think the appeal of threaded hierarchical conversations lies in the fact that they seem more “orderly” than one long stream of posts, ordered not necessarily by the logic of the conversation topic, but by the flow of time in which it takes place. It’s hierarchical. It’s organized. It’s neat, mathematical, logical. Algorithmic. Computer-friendly.

But is it brain-friendly?

Human-friendly conversations

Human beings do not think like computers. Though some human beings who spend lots of time programming or give excessive importance to logico-mathematical thinking might like approaching problems and the rest of life in a binary way, that is simply not how most people function. (Literary backdrop for this paragraph: A Perfect Mess.)

I think people who like threaded conversations like them because they have a higher order of organisation than non-threaded conversations. And better organised should be… better.

You won’t be surprised that I disagree with this. A good conversation online, for me, is one that can be easily followed, caught up with, and participated in. In that respect, a linear suite of comments is much easier to read or catch up with than a huge tree. When it comes to participating, the linear conversation offers only one option: add a comment at the end. In the tree, you first have to decide where in the tree you’re going to post. (Literary backdrop for this paragraph: The Paradox of Choice.)

How the format impacts the conversation

Another way to tackle this is to examine what impact hierarchical and linear comment threads have on the conversations they host.

Hierarchical – Threaded:

  • off-topic comments branch off into separate conversations
  • overall, more comments
  • lots of parallel conversations

Linear:

  • conversation stays reasonably focused
  • less comments
  • limited number of parallel conversations

I personally do not think that “more comments = better”. On a blog post, I like to see the conversation stay reasonably focused on the initial topic. For that reason, I think that linear comments are best on a blog.

More conversation is not always better

Of course, there are always parallel conversations going on. On Twitter, on FriendFeed, in IM windows I’ll never know about. As a blogger, I would like a way to point to these conversations from my post, so that a person reading could then have access easily to all the public conversations going on about what they read. Conversation fragmentation is not something we’re going to get rid of, but we can try to minimize it.

Increasingly, our problem is becoming one of signal-to-noise ratio and chatter. These are subjective notions. My signal is somebody else’s noise, and vice versa. I’m happy that there is chatter and small talk in the world and online (it’s a big part of human interaction and what relationships can be made of), also about what I write. But on my blog, I’d like to keep the chatter somewhat down, even if that means my “number of comments per post” or “conversational index” is not high. I’d rather have less conversation here, and give it a chance to be more interesting and accessible to outsiders, than huge 50+ comment threads that nobody is going to read besides the hardcore die-hard social media types.

More reading and listening

You’ll find some of the links I found on del.icio.us. If you’re into videos, the topic was raised about 6 months ago on Seesmic. Here’s what I had to say at the time:

I’ve also dug up a few quotes I found in some old discussions on MeFi. They’re in my Tumblr, but as Tumblr tumbles along, I’m reproducing them here:

If you’re trying to build community, it is clear that linear, non-threaded discussions are superior. There is a good body of research on this – it’s not new, it’s not a novel idea. For tech support stuff, hierarchical tree structures are better, in general.

Micheal Boyle (mikel)

One of the arguments for adding any feature that is designed to hide noise is that it gives it a permanent home. When Slashdot added moderation and auto-hiding to their threads, they gave the -1 NATALIE PORTMAN’S BOOBS brigade a permanent home on the site.

I checked out digg’s new setup earlier this week and 75% of all the comments were complaining about mod points. I don’t know if that’s an improvement.

Matt Haughey

This place is like a pub.

One does not have threaded conversations in a pub.

five fresh fish

Interesting [en]

[fr] Avez-vous aussi remarqué que plus on attend après avoir écrit son dernier billet sur un blog donné, plus il est difficile d'écrire ce fameux "billet après la pause"?

Have you also noticed that the longer you go without writing a blog post on a particular blog, the harder it is to write that first post “after the break”?

Going Solo is Tomorrow! [en]

[fr] Going Solo, c'est demain! Une vidéo et deux-trois pensées d'organisatrice.

Gosh. If I learnt one thing in my life, it’s that day go by and dates end up being “tomorrow”, and even “today” at some point. Going Solo is tomorrow — I have to pinch myself regularly to make sure I’m not dreaming.

You can still register online until tonight. Come to the Warm-Up Party this evening. I’m still wondering what to wear, worrying about a DHL package which reached Geneva yesterday morning but still hasn’t made it to my door, preparing to jot down some notes for what I’m going to say as the MC (and a panel moderator!) on the big day, wondering what “unpredictables” are going to crop up today (the last two days have been filled with them, big and small), remembering that I still have a bunch of Going Solo related photos to upload (maybe I’ll test the venue wifi with them)… Well, I’m busy.

And excited.

Thanks to all those of you who supported me these last months. I wouldn’t have made it this far without you.

Poster for Going Solo

Lots of Going Solo News [en]

[fr] Des nouvelles de Going Solo. Plein de nouveau! Mais pas le courage d'écrire en français. Au pire, filez sur la page presse où vous trouverez de la documentation en français au sujet de la conférence.

Gosh, I can’t remember when I posted the last Going Solo update on this blog. The conference is in less than a week! I can’t believe it.

You should really, really, really subscribe to the Going Solo blog to keep up with what’s going on on that front, or sign up for the newsletter if you’d rather get an e-mail every now and again.

Yes, Going Solo finally has a newsletter! And posters! And an agenda, speaker interviews, a bunch of great sponsors and partners (attendees will have a chance to win a FreshBooks Shuttle Bus package, get MOO goodies, and even see men in white. If you’re having trouble keeping track of where to find Going Solo online, this round-up post should help you.

Oh, and we have pre-conference and post-conference events organized, quite a bit of bandwidth at the venue (wifi of course), and we’re all set to film the sessions on the big day.

Phew. What am I missing? Oh yes, we’re going to be able to keep registration open this week (the kind people at the Albatros-Navigation are flexible enough to allow us to do that). I need to write a note about that on the Going Solo blog. And we have a press page where you can download shiny PDFs both in French and English.

Funnily, my stress levels are going down these days. I mean, we’re almost all set, aren’t we? I might bite my tongue for saying that these next days, though…

Trying the Seesmic Video Plugin [en]

[fr] J'essaie le plugin seesmic pour mettre de la vidéo dans mes articles. Il paraît qu'on peut laisser aussi des commentaires vidéo!

When I visited Seesmic in San Francisco, Loïc told me they were working on a video comment and posting plugin.

Here I am, trying it out.

{seesmic_video:{“url_thumbnail”:{“value”:”http://t.seesmic.com/thumbnail/NrZQ4aKmSu_th1.jpg”}”title”:{“value”:”My First Seesmic Video Post with the WordPress plugin.”}”videoUri”:{“value”:”http://www.seesmic.com/video/0i66jwr6zE”}}}

Educational Versus Inspirational Events [en]

[fr] Going Solo vise à être une conférence qui non seulement donne de l'inspiration, mais qui enseigne également. Du coup, préparer le programme ne consiste pas simplement à trouver des orateurs pouvant faire des présentations autour d'un thème donné, mais ressemble beaucoup plus à la préparation d'un plan d'études: il y a tant de matière à couvrir, et il faut trouver les bonnes personnes pour le faire.

It was clear to me from the start, when I started imagining Going Solo, that the programme would be built in such a way as to cover a range of topics I thought were relevant. What I didn’t realize is that this is quite different from having a conference/event “theme” and hunting for speakers who have something to say around that theme.

I’ve many times tried to express that although Going Solo is not a workshop or a training session, it is training-like, but I never quite seemed to find a way to explain this clearly. I wanted to say “yes, it’s a conference, but the aim is for people to learn stuff they can use when they walk out.” I think I’ve nailed it now, though: Going Solo is educational more than inspirational.

Most conferences I go to fall in the “inspirational” category. Of course, I learn things there, but mainly, I am inspired, or lifted (if the conference is LIFT). When I planned my Open Stage speech to present Going Solo to the audience at LIFT (watch the video), I wanted it to be inspirational. It’s not a video that teaches you anything, but that inspires you to attend Going Solo (and it did indeed inspire people!)

Even if the conference theme is more technical, and the sessions actually teach you stuff, most often it is a series of related sessions grouped together around a given theme. Reboot is a perfect example of how a theme is used to collect all sorts of contributions.

Not so for Going Solo. Putting together the programme for Going Solo feels much more like being in charge of defining the teaching programme for an academic year (only it’s a day, thank goodness, not a year). At the end of the day, I want the programme to have covered this, that and that. I try to organize the content into sessions, and then I talk with my speakers to see who can cover what.

I’m realizing now that this is the difficult bit — and as a speaker myself, I should have thought of this before. “Speaker topics” do not necessarily match “Steph-defined sessions” — which means I need to go back and reshuffle my sessions (perfectly doable, but it’s more work) to avoid overlaps and important topics slipping through the cracks.

Has anybody had similar experiences? And for any people reading who speak at conferences, if you agree on a topic with the chair and you’re asked to make sure your talk covers aspects x, y and z of the topic, does it make you feel micro-managed? Or is it something that happens regularly?

Partial cross-post from the Going Solo blog. Also on the Going Far blog.

Google Groups Pain in the Neck [en]

[fr] Google Groups trouve qu'il n'est pas raisonnable de vouloir ajouter plus d'une dizaine de personnes à la fois à une newsletter nouvellement créée.

I’ve used Google Groups to set up a newsletter for Going Solo.

Here it is, with added proof (if needed) of my hopeless lack of design sense.

When I set up the group, I did what most normal newsletter creators would do: went through my contacts to invite those who might be interested in joining. I selected 30 or so people to start with.

My action triggered a flag for review, as I might be a potential spammer:

Your request to invite X new members has been flagged for review by our staff.

In order to protect our members from unsolicited email, Google manually reviews invite requests which meet various criteria. Your request will not be reviewed unless you provide us with more information in the form below. Reviews generally take 1 – 2 business days.

Please provide an explanation for where these new members come from and why they would want to be part of your group. Note that Google takes a very dim view of Spam. The people you invite must know you and be expecting your message. If they complain, you will be banned from our service and your group will be deleted.

Great.

Well, I wrote up an explanation, saying I was setting up this newsletter so that people could stay informed about Going Solo (registration is closing soon btw), and that I was going through my address book to let people know about it.

Anything wrong with that, in your opinion? I think not, and Google obviously didn’t think there was anything wrong either, because they let my invitations go through after a few hours.

BUT.

Now, each time I invite even one single person, my request is flagged.

Google Groups: Threatening!

What a pain! I’m going to be inviting people many times a day over the next week, as I dig out e-mail addresses. And obviously, just announcing the existence of the newsletter is not enough to get people to sign up — ever heard of lower the barrier to entry? If I’m creating this newsletter, it’s because I’m finally coming to my senses (!) and realising that not everybody follows Twitter, subscribes to blogs, hangs out on Facebook or upcoming, and that good ol’ e-mail still has some good days before it when it comes to getting information out to people.

I am really annoyed at Google Groups for making this so difficult. Shouldn’t there be a way for me to get the limit “lifted” for my group, by offering proof I’m not a nasty spammer, but a businesswoman (OMG!) who is very much aware that she will very quickly use up her social capital if she spams her network with irrelevant stuff? And therefore, that I actually need to send out invites to a few hundred people?

Also, look at this form:

Google Groups invite members

Don’t you think that “e-mail addresses” field invites a reasonably large number of addresses?

I went through the help, and it wasn’t very encouraging, but I did learn a few useful things:

So, please. If you have friends working on Google Groups, please draw their attention to this post and issue. It’s a bloody pain in the neck.

Oh yeah — and please sign up for the newsletter. I’m going to have trouble inviting you 😉 — [email protected] also works.

Twitter Metrics: Let's Remain Scientific, Please! [en]

[fr] On ne peut pas prendre deux mesures au hasard, en faire un rapport, et espérer qu'il ait un sens. Un peu de rigueur scientifique, que diable!

10.02.2011: Seesmic recently took its video service down. I have the videos but need to put them back online. Thanks for your patience.

Video post prompted by Louis Gray’s Twitter Noise Ratio. I’m still somewhat handicapped and used up my typing quota this morning. corrections: measure time, measure distance (not “speed”) My graphs: Louis Gray's Twitter Noise Updates/Followers Ratio Zoom in to the beginning of the graph: Twitter Noise, extremes removed Attempt to spot trends: Twitter Noise Updates per Followers, annotated Not conclusive. See also: Stowe’s Twitterized Conversational Index — interestingly, Stowe became much more “chatty” on Twitter lately 😉 Update: The Problem With Metrics — a few thoughts on what metrics do to the way we behave with our tools. Confusing ends and means.

Diigo – I Think I Like the Idea (Bonus Content: Conversation Fragmentation) [en]

[fr] Diigo semble être un outil de commentaire et de bookmarking social intéressant. Regardez les images si le texte vous rebute. En prime, petite digression sur la fragmentation des conversations.

I’m a bit of a referrer obsessive, and today that little habit of mine led me to discover Diigo, a social bookmarking tool which does way more than that. It seems at first view to be a mix of del.icio.us and what coComment could have been, with a pinch of MyBlogLog and maybe StumbleUpon thrown in.

This is the link that led me to it. It’s pretty well-designed, because it immediately gave me an idea of what the service might be able to do for me. Look for yourself:

Diigo non-user landing page

That’s the page that was bookmarked, with a “toolbar” (a fake one) on top. Close-up:

Close-up of "fake" Diigo toolbar

Oh-oh! I can bookmark, highlight, annotate, comment… sounds nice! If I scroll down the page, I get to see what “highlight” might look like:

Diigo highlighting

That’s actually pretty good, because it allows me to see what I could get out of the service without having to sign up. Good marketing, guys and gals. Well, I don’t know about you, but that was enough for me to sign up and see what it was really about (specially as I’m keeping an eye open for something that could replace what I use coComment for — but it doesn’t seem this will be it, I’m afraid).

So, here goes. Sign-up was pretty straightforward. Sadly, Diigo commits the password anti-pattern crime, which no social tool is allowed to do anymore now that Google has a password-free API to get around that (see Flickr and Dopplr: the Right Way to Import GMail Contacts). I’m from now on refusing to give my password to any “find your friends” interface, even if it makes my life more difficult. One has to take a stand, sometimes.

So, finding friends will be hard. Let’s have a look around, however. Diigo has a toolbar, which installed quite nicely. The FireFox add-on provides a side drawer for Diigo.

My Dashboard | Diigo

Amongst other things, this makes it easy to leave a comment on any page. A good point for Diigo: they make it possible to share annotations with non-users (which is how they got me interested, as I just explained). So for the comment in the screenshot above, I can get a “share link“:

Diigo -- Sharing annotated link

Which means people I give this link to get to see this:

Diigo comment visible to non users

Oh, and they have OpenID too! Another good point for them. In case it wasn’t clear from what I’ve already said, I think that leaving the functionalities of the tool visible to non-users like that is a great thing. It makes it easier to use for me when I don’t already have friends, and it allows people who haven’t joined yet to see more clearly what they might get out of doing so.

Back to the tour.

Diigo does bookmarking. I’ve been faithful to del.icio.us from the start, but it doesn’t mean I’m closed to switching if I find something better. If I can bookmark and post Skitch-like sticky notes and comments on the web pages I’m bookmarking, well, that could win me over. First thing I checked, though, was import/export capability. One of the things I feel burnt with about my coComment experience is that there seems to be now way to leave with my data — so export is one of the first things I check before I consider using a new service I’m going to be storing data in.

Import is important, because if I’m going to switch to Diigo, I want to bring my past data in. Well, in that department, good marks:

Social Annotation: Seamless Integration of Social Bookmarking, Web Highlighter, Sticky-Note & Clipping

And even better, the “save elsewhere” feature:

Save Elsewhere

This means I can start saving my bookmarks to Diigo right away, and get Diigo to post them to del.icio.us. That way, it doesn’t break anything in the way I work — it just changes the input method and allows me to test a new tool “without risk”. Great.

I tried importing my bookmarks through the API and it seemed to stall in the middle:

My Bookmarks -- import fail

I can’t say I’m wild about the amount of advertising on the site, but it seems in slighter good taste than coComment (I encountered a seizure-inducing vibrating banner ad on their site just minutes ago — but to say the good, I also discovered that they now support OpenID during that trip).

So, after the first import seemed to fail halfway, I followed Diigo’s advice and imported my bookmarks through the HTML export file del.icio.us provides. I got the following message:

Diigo File Import from del.icio.us

…which made me fear I would end up with duplicates — but no, everything worked fine. It’s now possible to see my “goingsolo+coverage” bookmarks on Diigo.

The interface is sometimes a bit difficult — I’ve found how to do things, but it doesn’t “flow” as easily as I’d expect it too. I guess they still could use some work there, and it sometimes has a feeling of “rough around the edges” (ie, import message that says things are ok when they aren’t, extra space in URL when filtering two different tags in bookmarks, chopped usernames under avatars…). This, for example, looks like it could use a bit more work in the design/usability department:

Reader Community for twitter.com ,Twitter: What are you doing?

What would be really nice would be if Diigo could capture comments made in traditional commenting forms, in addition to letting me add “separate” comments:

Could Diigo do comment capture?

This is important because comments made through normal commenting forms appear on the page immediately — so site owners aren’t going to get rid of them right away. I need to dig into what Disqus is doing, though, haven’t yet had a close look. A bunch of people (Loïc Le Meur, Louis Gray, Stowe Boyd, amongst others) have been noting lately that conversation/commentary is moving away from blog comments.

The conversation is now forked or fragmented, something that Ben Metcalfe noted as a problem with coComment, already at the time. I remember that at one point in time, the direction coComment was taking (with groups, mainly) was to abandon the idea of one conversation” and the move towards “multiple conversations” per post/page. I guess I never really liked that idea, because as a blogger before anything else, it’s important to me that commentary about what I publish can easily be found using the original post/video/whatever as a starting point.

On the other hand, I don’t believe in forcing people to use this or that system to leave their comments. Lots of people comment on my posts through Twitter, and that’s fine — but I regret there isn’t a system to indicate that those tweets are part of the commentary on this or that post. So, comment through Twitter, the comment form, Facebook, Diigo, on my FriendFeed or on your own blog, even with a Seesmic video comment if you want — but as a content provider, I’d like a way to collect all that commentary with a big net and display it on my blog post page.

Comments have more value when they are displayed alongside the content they’re referencing, but the process of leaving a comment should be tool-agnostic.

So anyway, end of bonus digression, and back to the Diigo tour. This Diigo thing is social, so I need to find friends. As I refuse to do the password-thingy, I tried typing a few names of superconnectors I know (Robert Scoble, Stowe Boyd, Michael Arrington, Chris Brogan… for starters). Only Arrington had an account, but it had one test bookmark and zero friends… not too good for a start.

I’d noticed the Diigo side drawer had a “Readers” tab. So I loaded up my blog in the browser, and scanned the list of my readers for known names (I figured I might know some of my readers). Lo and behold!

Climb to the Stars (Stephanie Booth) » More than just a blog.

My friend Thomas Vanderwal was in the list. Here’s his bookmarks page:

Thomas Vander Wal - Bookmarks

(Note the “tasteful” German-language ad — because I’m in Switzerland, I speak German, of course (not).)

I had to poke around a bit for the “ad friend” button, but finally found it on Thomas’s profile page:

Thomas vander wal Profile

Unfortunately, it seems not many people from “our bloggy-twitter circle” have joined yet — Thomas only has two friends, and I don’t know them (I think). Or Diigo need to work hard on their “finding friends and adding them” processes.

Well, there we are. Looks interesting. Will try to use it. More to be said of course, but already spent way too long on this “quick post with a few screenshots”!

If you join Diigo, here’s my profile page if you want to add me. Tell them I sent you! (Who was saying I should get paid to write this kind of stuff, already? ;-))

Update: Diigo isn’t new, though I don’t recall having ever heard of it. Seems Techcrunch mentioned it in 2005, 2006, and again last month. Maybe I should read Techcrunch more often 😉

The Neighbour's Cat Won [en]

[fr] Morsure de chat. Pas mon chat: chat du voisin que j'ai acculé (chez moi, pour le leur ramener) même après qu'il m'ait prévenu à grands coups de griffe qu'il était trop paniqué pour venir tranquillement. Moralité: les chats ont de longues dents pointues et ne se les lavent pas.

Thanks to everybody for their sympathy and wishes of speedy recovery!

The Neighbour's Cat Won

Not much typing. Cat bite. Details later. Nice cat. Not Bagha. Silly Steph.

Some details.

Friday Update:

Cat Bite Update

Infected. Another appointment tonight. I hope they don’t leave me in this huge splint too long. Can’t do anything!

Friday night update:

It Just Gets Better...

Left arm: infected cat bite. They have long sharp canines and don’t like being cornered in a strange place by a strange person. Splint that forbids any use of my hand — will stick around for at least another 2-3 days.

Right arm: catheter. I had 3 doses of antibiotic through IV over the last 24 hours, and am headed for at least that many over the week-end. There are only so many veins in the arm you can stick needles in.

Now, we hope the long canine didn’t go deep enough to infect the bone — or I’m looking at 4-6 weeks of treatment.

Fingers crossed, everybody, please.

Video Update: the story and more details.

How it happened:

The consequences:

Sunday morning update: I can haz fingers!

I Can Haz Fingerz!

Still got the catheter, though it hurts less now the tap is on the outside of my forearm.

Great improvement: fingers on my left hand! I can type somewhat! Things are taking a good turn. Thumb joint still very painful, so I’m a little worried it could be inflamed/infected — but gosh, does it feel good to have part of my hand back.

Sunday evening news: good!

Monday update: shower!

From now onwards, things are on the right track. I can remove my splint if I like, infection seems gone, but it’s still inflamed. So, I can type and do most of what one expects to do with two hands, just a bit slower and more painfully.