Rebooting The Blogosphere (Part 2: Interaction) [en]

Start with part 1!

Yesterday I started writing “a blog post” to capture my coalescing thoughts about the open web and how to remove friction from blogging. Not all of it: some friction is good. But enough that people like me don’t get so easily drawn away from their blogs by “The Socials”.

So far, in Rebooting The Blogosphere (Part 1: Activities) I have distinguished four types of “activities” we carry out in online social spaces:

  • reading
  • commenting/reacting
  • writing
  • sharing.

Today, I’ll focus less on the actions an individual carries out, and more on the interaction between individuals. The wonderful thing about blogs is that they lowered the barrier to personal expression online, which in turn makes dialogue possible. But dialogue can take many forms.

Some thoughts on Dave’s “new model for blog discourse

Before I go any further, I would like to address a few points Dave brings up in his podcast from yesterday, because I actually started yesterday’s post with the intention of responding to it (amongst other things), but he put it up while I was already writing.

I love what Dave describes doing in the very early days, if I understood it right: write something, send it by e-mail to handful of people, and have a first round of discussion with that smallish group before publishing, and including value-adding responses to the publication. All this, scripted so that it was as frictionless as possible for him. This reminds me of Bruno Giussani‘s “Promote Comments Plugin” idea. It also fits with the idea I insisted upon yesterday that there is an added value to making the discussion about something available in the same place as that thing.

It is also reminding me of one aspect that I hadn’t thought about covering in this post-become-series: managing who the audience is. I firmly believe that allowing conversations to take place in closed or semi-public spaces is vital (cf. context collapse) – proof the number of people who take part in closed groups on Facebook or who share updates to “friends only“. I might have to make this a fourth part…

Dave describes a future tool in which comments (responses) get posted to the commenter’s blog and sent privately to the author of the original blog post, who can then decide whether to make it visible or not. For me, the second part of this process is already widely implemented in blogging tools, and has been for over a decade: its upfront comment moderation. Some people activate it, some don’t. On this blog, for example, if you’re a first-time commenter, your comment is not published. It is sent to me and I decide whether it’s worth publishing or not.

The first part is more interesting. It addresses the “ownership” issue of the comment, as tools like coComment or Disqus have tried to by providing a place all a person’s comments are collected. But it goes one step further and says: that place is the commenter’s blog. This is great and has been long needed. It would be interesting examine why previous attempts to do this across platforms have not stuck.

And this leads us to the topic of today: show my comments on my blog, but in what way? My comments are not the same kind of content as my posts. I don’t want my posts to be mixed up with my comments, everything on the same level. I’ll explain why.

Finally, Dave identifies some of the challenges with blog comments that I covered in yesterday’s post, but I’m not sure the current situation is as “broken” as he thinks. All that is missing, really, is a way to collect-own-display the comments I make all over the place in a space that is mine. Moderate comments upfront, or not? Or even, not have comments? That’s already possible, and up to the blogger. And yes, moderating comments or limiting who can comment directly cuts down tremendously on the spam and other bad behaviour issue.

Comments are about interaction – so are links between blogs. And as I mentioned yesterday, one thing the socials are really great at is interaction. You can spend your whole day on there (don’t I know it) interacting.

A way to look at interactions

I’m going to start by sticking with 1-1 interactions, to make it simpler, but I think this can be applied to interactions with more actors.

I think we all agree that exchanging letters with somebody (which I’m old enough to have done in my youth) is very different from talking on an instant messaging system. The key dimension that varies here is how (a)synchronous the interaction is. This drives a lot of the features we have in our social tools, and what makes them different from one another – just like in martial arts, the distance between the practitioners constrains the kind of techniques, and therefor the kind of fighting (interaction) that can take place.

I’d like to summarise it this way:

The length of contributions in an interaction is inversely proportional to how synchronous, or how conversational it is. And vice-versa.

Let’s unpack this a bit.

When Twitter showed up with its 140-character limit (which didn’t come out of nowhere, it was SMS-based), and constrained how much we could write in one go, it quickly became a place where we were “talking” more than “writing”, as we had been doing on our blogs. It was not quite as immediate as instant messaging, but somewhere in between. Like text messages.

In the early days of Facebook, if my memory serves me right, there was a distinction between sending a message to somebody (sorry, I can’t remember the terminology that was used, I’m not even 100% sure I’m remembering right) as some kind of internal mail, and chatting (or maybe they transformed the former into the latter and it changed the way we used it). In Discourse, you have both: you can send a message to somebody, or chat. Like you can e-mail somebody, or instant message them.

And I suspect I am not the only person to feel some degree of annoyance when I receive an “instant message” that should have been “an e-mail”, because it requires me to sit down, absorb a “speech”, and then figure out how on earth I’m going to respond to all that was said in one go, particularly now the person who sent it is not online anymore, because I had to wait until I had enough time to properly read it, digest it, and figure out my response.

Instant messaging works when it’s used for short things that you can take in at a glance (or barely more) and answer without having to think too much. It is conversation, with an asynchronous twist. When both parties are connected and interacting (synchronous), it is very close to in-person (or “on the phone”) synchronous conversation, but with this “optional asynchronicity”, as there is a blind spot regarding the context of the other party, and how it impacts their availability to read or respond right now, or even, to keep the conversation going. (If you’re on the phone with them or in the same room: they are available.)

When in “conversation mode”, contributions can become a bit longer, but not too long: if you throw a 3-page essay at somebody in an instant message or chat conversation, chances are you’ll lose them. Just like in-person conversation: if you monologue for 10 minutes at the person you’re talking with, you don’t have a conversation anymore. And actually, this pretty much never happens: there are non-verbal cues that the person opposite you is going to give that will either interrupt your monologue, or reveal that it is in fact a dialogue, when taking into account non-verbal contributions of the listener. But when you’re typing in an instant-messaging box, there is none of that.

Back to blogs. A blog post does not have the same conversational qualities as a response to a tweet. Blogs live in a more asynchronous interaction space than the socials or chatting. Comments are generally more conversational than blog posts. But probably less than updates on the socials.

“Allowed length” of contribution plays a role in shaping the kind of interaction, as well as design. If you’re typing in a tiny box, you’re less likely to write an e-mail or a blog post. If you’re typing in a box that uses up the whole screen, you’re less likely to write only one sentence.

Why did so much conversation move from blogs and chats to socials? I think that it is because they are in some sweet space on the (a)synchronicity continuum. They allow belated responses, but also real-time interaction. Notifications are key here, as is the fact that writing/responding are pretty much the same thing (same on Twitter or Bluesky or Mastodon, not-quite-same on Facebook, but close enough) and in the same space as reading/listening. It’s super easy to jump in and out of conversation. Frictionless.

So, it’s not just about reducing friction around reading blogs, writing blog posts, and commenting on them: it’s also about how we integrate the blogosphere and the socialsphere. One cannot and should not replace the other. There will always be people who like writing stuff. And others who are just happy to interact or react. And it doesn’t make sense to corral them into separate spaces.

Does anybody remember Backtype? I didn’t. Well, I do now after reading my blog post. The idea was to find a way to bring “back to the blog post” conversation about it that was happening on the socials (gosh, I really hope it’s not too annoying for you all that I’ve started saying “the socials”, it’s just really practical; my apologies if it grates on you). What about Diigo comments?

There is a common theme here: somebody writes a blog post. There is discussion about it or prompted by it – in the comments, on other blogs, on Bluesky, Facebook, Twitter and Mastodon, even Threads. How do we give easy access to these fragmented conversations (I think conversation fragmentation is now something that we have accepted as inevitable and normal) to those who are reading the post? And how do we do that in a way that a) leaves some control in the blogger’s hands over what to show and not to show (less spam) and b) allow people participating in the conversation to keep ownership of their content, in the sense that even if it can be made invisible in a given context (e.g. on the blog post), it cannot be outright removed by a third party, and remains “on the record” of the person who wrote it?

Who owns the conversation?

There is a lot of talk about retaining rights or ownership to one’s content. But who owns a conversation? Or beyond that, a community? The whole is more than the sum of the parts. When people come together to create something together (including relationships), who owns that? I mentioned previously that when facebook allows you to “download your content”, that doesn’t seem to include comments (wait, I have a doubt now – I think the export used to, but not anymore, correct me if I’m wrong, as I can’t go and check easily). Or comments by others made on your posts. In any case, say you can download your comments: a lot of them are contributions to conversations, and make little or no sense without their context – the publication the conversation took place about, other people’s comments.

I think there needs to be some kind of “collective ownership” understanding, which is more nuanced than “I wrote it, I have power of life or death over it”. When does something you offer up to the collective cease to be completely yours? In my opinion, it remains yours in the sense that it cannot be taken away from you against your will. Corollary: if contributions to a conversation or a community also “belong” to the conversation or community, then it should not be possible to take it away from them unilaterally. This is something that needs to be thought out further: does it mean that I should not be allowed to remove my blog from the web?

What is clear at this point: we need to think beyond “atomic” contributions and also think about how our tools manage the collective creations that are conversations and communities.

So, let’s sum up today: interaction is not a monolith. Online conversations occur at varying speeds and are made up of contributions of varying nature. Reclaiming and rebooting the blogosphere and the open web needs to take that into account and embrace it, and figure out how to bring it together in an open way, with frameworks, standards, protocols or the like, not yet another “One Platform to Replace Them All”.

That will be tomorrow, in part 3.

Thanks for reading, and don’t hesitate to react: on the socials, here in the comments, or on your blog!

Rebooting The Blogosphere (Part 1: Activities) [en]

Some thoughts (part 1 of 3) following exchanges on Bluesky with Dave, amongst others. My Facebook exile is clearly bringing to a boil my preoccupation with our reliance on big capitalist platforms for our online presence and social life. Though I never “stopped blogging”, I clearly poured a lot more energy over the last decade into what I now think of as “The Socials” (Twitter, Facebook, Bluesky, Mastodon and the like).

Why? How did that happen? What makes it so much more “easier” to hang out over there than to write here? Dave rightly points out to “1-click subscribe” as a killer feature that Twitter brought to the table (written summary of the podcast if you don’t want to dive into listening). But there is more than that.

I am pondering a lot on what I am “missing”, having lost facebook. On what is “difficult” about blogging, in comparison. Where is the friction?

Very clearly, one thing that The Socials (I’ll drop the uppercase soon) do very well is:

  1. bring everything (reading, writing, responding) together in one seamless interface/site/app
  2. shift interaction closer to real-time and what we perceive as “conversation”.

The rest of this blog post covers the first point. A second one will cover the second one. And finally, in a third post I’ll try and put together a proposal for how we can use our understanding of how the socials manage “so well” to remove friction from blogging and help reboot the blogosphere.

As I was writing this post I poked around in my archives to link to where I’d spoken about some aspects of the topic, so here are a some of those I dug up, in addition to those linked in the text itself (realising I wrote so much about this stuff it makes my head hurt):

I see three main “activities” for taking part in the text-based social web, and a fourth that may be worth distinguishing from the third:

  1. Reading or consuming: basically, taking in things that others have put there.
  2. Responding, commenting, reacting: expressing oneself based on something somebody else has provided.
  3. Writing: making available to others ideas, stories, in a broad sense, our creations.
  4. Sharing or boosting: highlighting for our network/readership things that are not by us.

Some comments regarding this typology (bear with me, it will come together in the end).

Reading

RSS does a good job of allowing us to collect things to read from different sources into one place. Many different tools make RSS feeds available. Many different tools read/collect/organise RSS feeds. However, they usually keep this collection of feeds private.

As Dave says, subscribing to an RSS feed generally requires too many steps. Too much friction. The socials make it 1-click (sometimes two) to follow or friend (connect to) somebody. And it’s right there in front of you, a button that calls you to do it. Inside blogging platforms like WordPress.com or Tumblr, you have some kind of 1-click subscription, but it keeps you in their internal reader (just like the socials do, by the way).

Commenting

Responding/commenting is a can of worms, in my opinion. When I started blogging, blogs had no comments. We responded to each other’s publications by writing on our own blogs and linking to what we were responding or reacting to. I actually wrote about this a couple of days back.

After a few months of blogging, I added comments to my blog, so one could say it’s pretty much always had them. (For the nostalgic: the blogger discuss thread I got my comments from, and the page on my site which for some time provided the PHP comment script to hungry bloggers.) And most blogs have them too, though far from all.

Comments come with issues, as well as opening new doors:

  • first of all, you’re leaving your stuff in a space that somebody else controls (ring any bells?) – when the “host blogger” deletes their blog or their post, there goes your comment
  • second, the way comments are designed invite shorter contributions or reactions – this makes the exchange more conversational and less epistolary, tightening the relationship between the different parts of the exchange provided by different people and quickening the pace
  • comments link back to the commenter’s blog, therefore creating an incentive to comment for visibility and not just for what one has to say
  • the visibility incentive leads to people commenting while adding little value (in the best cases) and outright spam (in the worst, widespread case)
  • the lack of a frictionless system to be informed of responses to comments (think “response notifications” on the socials) leads to interrupted interactions (I liked the term “drive-by commenting“)
  • the widespread presence of comments on blogs raises the bar for what is perceived as “deserving” to be a blog post, possibly contributing to the idea that writing a blog post is a “big thing” that you might need to make time for (or that might suck up half your day), in comparison with just “leaving a quick comment” after reading something
  • the visibility of comments led to it becoming a measure of blogging success, increasing a kind of competitiveness in the space, and, in some cases, even its commercialisation.

I see comments as solving two main problems:

  1. attaching the “discussion” about a publication to that publication: all in one place, instead of spread out in blog posts you might not even know exist
  2. lowering the barrier to entry for participating in said discussion: you don’t need any sort of account to comment.

Over the years, many tools have attempted, in some way, to “fix” the problems that come with comments. A few examples:

  • coComment: solve the “notification” issue by tracking comments made over different blogs – and somewhat, the “ownership” issue, by giving the commenter a central repository of their comments
  • Disqus: solves notifications and central repository (but limited to Disqus-enabled sites) and maybe spam, to some extent
  • Akismet and all the other spam-fighting systems…

In a world without comments, people who read a post will not necessarily know there is a “response” somewhere else out there in the blogosphere. The blog author might see it if the person responding tells them (some way or another), or if they check their referrers (didn’t we all use to do that). But the reader cannot know, unless the blog post author knows, and links to the response. Trackback and Pingback came in to solve this issue, creating a kind of automated comment on the destination post when somebody linked to it (with all the spam and abuse issues one can imagine).

Tags and Technorati also played a role in “assembling” blog posts around a specific topic, which could be seen as some kind of loose conversation.

But it’s not the same thing as having the different contributions to a conversation one below the other on the screen at the same time.

Writing

This one is simple. There are many good tools (many open-source) to write blog posts. You can create an account somewhere and get started, or install software on a server somewhere – with a hosting company or in your basement. They work on mobile, in the desktop browser, or even in apps. There are generally ways to export your content and move to another tool if you want. Some are full of bells and whistles, others are pared down.

Blogging has no character limit – the socials do. This, implicitly, encourages writing different things. Design also does that: is the box I’m writing in something that takes up the whole page (like the one I’m typing this blog post in) or is it a little box that might expand a bit but not that much, like on Facebook (which also doesn’t have character limits)?

I think this is a crucial aspect which should not be ignored. The blog posts I wrote in 2000-2001 are, for many of them, things that would be updates on the socials today. They are not the same as blog posts, and we need to keep that. The way we interact with “updates” or “blog posts” is also different (I’ll come to that below if you’re still reading by then). They generate a different kind of interaction. And sometimes, we start writing an update (or even a comment/reply) and it transforms into something that could be a blog post. How do we accommodate for that?

Sharing

Sharing is trickier, and this is why I’ve separated from writing. If writing can be thinking out loud or telling a story I have in my head, sharing is “I saw something and you should see it too”. Maybe I want to add an explanation to why I’m sharing it, or “comment” (hah!), but maybe I just want to put it out there, nearly like a shared bookmark. Of course, if what I write about what I’m sharing starts taking up a lot of space, I’m probably going to be writing a blog post with a link in it. And if I’m just sharing a link to something, I might as well be using some kind of public bookmarking tool (remember delicious?)

Bringing it all together

This is what I said the socials were great at. When I’m on Facebook, I am on my news feed (reading). I can 1-click-share and 1-click-comment on what I see, in addition to 1-click-subscribe if something new I want to track crosses my radar. If I want to write something, the box to do so is in the same view as my news feed – or pretty much any “reading” page I’ll be looking at (a group, for example; groups are another thing to talk about, but that’ll be another post).

I don’t really have to determine if I want to read, write, share, comment – I go to the same place. Whatever I want to do, the tool and environment remains the same. Tumblr does that well too.

Whereas look at blogging:

  • I want to write a post, I go to my blogging software
  • I want to read stuff, I open my RSS reader (confession: I’ve never been good at this) or conjure up a blog URL from somewhere (memory? bookmark? blogroll? link in another post?)
  • I’m done reading something (in my RSS reader) and want to comment: I need to click over to the blog itself to do that – or wait, do I want to comment, or write a whole blog post? I have no clue how much I’m going to want to write once I get going, I just know I have something to say.
  • I read a great blog post (or other thing online, for that matter) and want to share it, I need to pick up the link and write a blog post. Or maybe, instead, I just stick the link in a toot on Mastodon? There are “blog this” bookmarklets, but what about if I’m on my phone?
  • Yeah, I could post my “statusy updates” to my blog like it’s summer 2000, but do my blog subscribers really want to see “spent a lot of time feeding the sick old cat” in their RSS reader?

Think about community platforms like Discourse: want to post, want to respond, want to read? All in the same “place”. You get notifications, you can configure them. I think there is a lot to learn from this type of platform and the socials to bring “blogging stuff” together.

And before somebody says: “your blog should replace your socials” or “you should just blog on mastodon”, wait for the post I plan on writing tomorrow about what I see as a very important distinction in between these two types of online “social” spaces: exchange intensity and pace.

Ideas like making WordPress and Mastodon work together and FeedLand (in short, it makes your RSS subscriptions visible on your blog; check the new shiny blogroll in my sidebar, thanks for the shoutout, Dave!) are absolutely on the right track, but if we treat all “conversation” and all “publication” the same, we will fail in building an open, independent social web that is integrated and frictionless enough to be a realistic alternative to the facebooks of this world for more than just us few geeks.

Continue reading with part 2!

When Do You Wear or Remove Your Hearing Aids? [en]

As the founding editor of Phonak’s community blog “Open Ears” (now part of “Hearing Like Me“) I contributed a series of articles on hearing loss between 2014 and 2015. Here they are.

As somebody with mild/medium hearing loss, I guess wearing hearing aids are more of a choice than a necessity for me. I mean, I functioned without them for nearly 40 years. Today I wouldn’t give them up for anything in the world, of course, and I really prefer wearing them for anything resembling human interaction. But I can get by without. (An audiologist I had a chat with one day told me I’d be surprised at how people with much more hearing loss than me “get by just fine” without aids. Anyway.)

So, when do I wear them, when do I remove them? As a general rule, I wear them when I leave the house. (My cats aren’t all that talkative.) I remove them when I get home. Since I got my V90 aids though, I often forget to remove them when I get home.

I don’t wear my hearing aids to watch TV.

skiing-022515-940x492

I’ve been watching TV so long with headphones that having “ambient” sound on actually makes me self-conscious about bothering my neighbours with it (this is Switzerland). I used to always remove them to listen to music or podcasts. Now that I have the ComPilot Air II I sometimes keep them in (more for podcasts than music, with open tips there are frequencies missing for the music). If I’m travelling or wandering around on my own and not really expecting to interact with people I might take them out, too.

At judo training, I usually keep them in for warm-up and maybe the first rounds of “light” practice. Then I remove them so that I don’t have to worry about paying attention to what’s going on around my ears.

For skiing, I keep them in, despite the helmet. With my old Widex aids I’d given up on that (they really didn’t cope well with the helmet), but my current ones are fine. When driving, I sometimes wear them, sometimes not (depends if I was wearing them just before taking the wheel or not, I guess).

I also ended up removing my hearing aids once at a very noisy party. Even with the highest “speech in noise” setting, I actually managed better without them. But that was really an exceptional situation.

What about you? Do you put them in first thing in the morning and take them out last thing at night, or are you like me, sometimes in, sometimes out? And when? I’m curious to hear how other people do this. I suspect our wearing vs. not-wearing habits are also linked to how much hearing loss we have.

The Blogging Tribe is Live [en]

[fr] Une quinzaine de blogueurs qui prennent l'engagement de bloguer régulièrement durant un mois, pour commencer. Suivez-les sur The Blogging Tribe.

Last week at the chalet, I had an inspiration (amongst others!) whilst reading Here Comes Everybody: gather a small-scale tribe of bloggers who commit to blogging regularly over a period of time.

It’s done. We’re pretty much set. After a little back-and-forth on Facebook to try and figure out the best way to get started, we’re off for a month of “blog regularly and see what happens”, pretty much.

Here is the tribe:

You can follow all our posts at The Blogging Tribe, kindly hosted and set up by Claude.

Chat ou e-mail pour rester en contact? [fr]

Au détour d’une conversation avec Fabien ce matin, je (nous) faisais la réflexion suivante: même si j’adore écrire (preuve les kilomètres de texte qui s’alignent sur ce blog, sauf quand je n’écris pas) je ne suis pas du tout versée dans l’e-mail “correspondance”.

Certes, j’utilise (beaucoup) l’e-mail comme outil de travail. Pour des échanges factuels. Pour de l’administratif.

Mais pour parler de sa vie ou de son coeur, je préfère être en intéraction directe: IM, SMS, IRC Twitter, téléphone, ou même (oh oui!) se voir en chair et en os pour boire un café ou manger un morceau.

Déjà avant que l’e-mail ne débarque dans ma vie, je n’étais pas vraiment une correspondante. Ma grand-mère paternelle se plaignait amèrement du manque de lettres provenant de sa petite-fille, les cartes postales signées de ma main étaient dès le jour de leur réception des pièces collector, et les deux ou trois tentatives adolescentes d’avoir des correspondantes dans d’autres pays se sont assez vite essoufflées.

Peu étonnant, dès lors, qu’un fois accro au chat sous toutes ses formes, ce soit les modes de communication interactifs que je privilégie pour mes relations avec les gens.

Je me demande si c’est simplement une préférence personnelle (certains sont épistoliers, d’autres pas) ou bien s’il y a véritablement des caractéristiques des médias en question qui la sous-tendent: l’interactivité (relativement synchrone), par exemple. Parler de ce qu’on vit ou fait (c’est souvent l’essentiel des conversations), c’est bien mieux avec un retour direct d’autrui en face, non?

LIFT'07 Social Networking Map Experiment [en]

[fr] Si vous étiez à LIFT'07, remplissez le questionnaire pour l'expérience de Social Networking Mapping!

I can only encourage you to participate in the LIFT’07 Social Networking Map Experiment if you attended the conference. It takes a little while to complete, depending on how extroverted you are, I guess. And if you hang out with evil supernodes, too.

Listing the people I knew before the conference wasn’t too hard, though of course I had to plough through the list. Here are the names I came up with:

Henriette Weber Andersen, Jean-Christophe Anex, Bieler Batiste, Yoan Blanc, Florent Bondoux, Stowe Boyd, Raphaël Briner, Stefana Broadbent, Lee Bryant, Marie Laure Burgener, Riccardo Cambiassi, Jérôme Chevillat, Marco Chong, Matthew Colebourne, Samuel Crausaz, Thierry Crouzet, Pedro Custodio, Nicolas Dengler, Jens-Christian Fischer, Antonio Fontes, David Galipeau, Bruno Giussani, Tanguy Griffon, Matthias Gutfeldt, Laurent Haug, Peter Hogenkamp, Dannie Jost, Christophe Lemoine, Thomas Madsen-Mygdal, Yann Mauchamp, Geneviève Morand, Philippe Mottaz, Hugo Neves da Silva, Nicolas Nova, Bjoern Ognibeni, Roberto Ortelli, Jean-Olivier PAIN, Marc-Olivier Peyer, Bernard Rappaz, Andre Ribeirinho, Martin Roell, Pascal Rossini, Robert Scoble, Rodrigo Sepulveda Schulz, Joshua Sierles, Nicole Simon, John Staehli, Elisabeth Stoudmann, Sandrine Szabo, Olivier Tripet, Guido Van nispen, Benjamin Voigt, Alfonso Von Wunschheim, Ellen Wallace, Bertrand Waridel, Mark Wubben, Chris Zumbrunn, Jan Zuppinger

“New people” I met at the conference was more difficult, firstly because I didn’t get the names of everyone and business cards are only so helpful, particularly when you don’t have any for the people you talked to, and secondly because many people did not include a photo in their profile on the site, or any information about themselves. Here’s the list I managed to compile:

Jeremy Allen, Paula do O Barreto, Nuno Barreto, Brian Cox, Florian Egger, Ramon Guiu Hernandez, Noel Hidalgo, Lisette Hoogstrate, Tom Klinkowstein, Trine-Maria Kristensen, Maya Lotan, Gia Milinovich, Glenn O’neil, Nortey Omaboe, Michele Perras, Ivan Pope, Derek Powazek, Thomas Purves, Dieter Rappold, Colin Schlueter, Maryam Scoble, Sebina Sivac-Bryant, Jewel THOMAS, David Touvet, Remo Uherek, Sarah Wade Hutman

A much smaller list, as you can see. Well, as I knew quite a lot of people to start with, I guess it’s expected to be short — but I’m sure this is at most the two-thirds of the people I met. If we talked and you’re not listed, let me know!

One methodological problem I can see with the survey is that “already knew” and “met for the first time” are not clearly defined. I’ve taken a really wide interpretation of those expressions for this survey. I’m not sure absolutely everyone on my first list would consider they “know” me. Or if I haven’t met a person yet but we’ve got common friends and I’ve followed a lot about them, do I “know” them? Ditto for “met for the first time”. I’d interacted with Gia online after LIFT’06, but this is the first time we talked offline, for example.

Anyway… interested in seeing what will come out of this. Please take the survey!

Femina: une promesse de blog [en]

Malgré tout le mal que j’ai pu dire du site de Femina, il s’y trouve une page qui me paraît fort prometteuse: nos potins.

A premier coup d’oeil, ça ressemble à  un blog — enfin, ça en a la mise en page. C’est joli, c’est aéré, on a envie de lire. Le ton est personnel, assez informel, authentique, comme celui du magazine, d’ailleurs.

Si on regarde de plus près, cependant, on remarque qu’il manque un certain nombre d’éléments pour que cette “promesse de blog” (dixit Anne Do) puisse être véritablement un blog digne de ce nom. Ce n’est pas juste une question d’appellation (surtout pas, en fait!) mais de rôle que devrait pouvoir jouer une telle publication.

A quoi peut donc bien servir un “blog de la rédaction” pour une publication comme Femina? Un blog, c’est bien pour un certain nombre de choses:

  • communiquer de façon transparente, directe et immédiate avec le “public” (les clients, les lecteurs, les électeurs…);
  • créer du dialogue, de la conversation avec le “public” et d’autres acteurs de la blogosphère (qui ne sont pas nécessairement des lecteurs du journal, par exemple) — ce qui renforce la “communauté”;
  • indirectement (car c’est une conséquence du succès dans les deux points mentionnés ci-dessus), augmenter sa visibilité dans les moteurs de recherche, avec toutes les conséquences réjouissantes que cela peut comporter.

Pour qu’un blog puisse mener à  bien cette mission, il y a un certain nombre de pré-requis, techniques et éditoriaux:

  • chaque billet doit avoir une adresse web stable et unique pour qu’on puisse y référer (le fameux “permalien”);
  • idéalement, les visiteurs doivent pouvoir laisser des commentaires ou au moins indiquer qu’ils ont écrit une réaction sur leur propre blog au moyen d’un trackback;
  • le billets doivent pouvoir être rattachés à  leur auteur (un être humain!), plutôt qu’être anonymes ou “collectifs” (on tombe alors dans la situation peu agréable où c’est l’institution ou l’entreprise qui parle);
  • le balisage (HTML et CSS) doit être structural (et non présentationnel) afin d’accomoder les moteurs de recherche comme Google, mais aussi les outils plus spécifiquement axés “blogs” comme Technorati, coComment, TailRank, ainsi que les divers annuaires répertoriant les blogs;
  • le blog devrait également être disponible sous forme de fil RSS/atom afin qu’on puisse s’y abonner et le suivre sans devoir se rendre sur le site lui-même;
  • être très ouvert par rapport au contenu du blog et des commentaires: éviter la censure ou les lourdeurs éditoriales MarCom ou RP;
  • la rédaction et la tenue du blog prend du temps; il faut prévoir du temps à  y consacrer pour qu’il reste vivant.

Il y a sûrement d’autres choses, mais avec ça, c’est déjà  bien parti. Difficile? Non. Il suffit d’utiliser pour son blog un outil de blogging, plutôt que de s’amuser à  vouloir réinventer la roue. La plupart des outils de blogging ont derrière eux plusieurs années d’existence et des équipes de développeurs enthousiastes — il est un peu illusoire de penser qu’on peut faire mieux seul dans son coin, surtout si l’on ne baigne pas déjà  dans la blogosphère. Donc, si on ne désire pas une solution hébergée comme WordPress.com ou TypePad, on installe sur le serveur de son site WordPress, DotClear ou encore MovableType (liste non exhaustive, bien sûr). Comme ça, on est sûr d’avoir sous la main le kit du parfait petit blogueur.

Je reviens à  Femina. Voici ce qui manque à  mon avis cruellement à  la jolie promesse de blog pour qu’elle puisse déployer ses ailes et occuper la place qu’elle mérite dans la blogosphère romande:

  • des permaliens
  • la possibilité de laisser des commentaires et des trackbacks
  • le nom de la personne qui a écrit le billet
  • côté “derrière la scène”: fil RSS/atom, balisage correct, service de ping…

Ce qu’il y a déjà ?

  • un ton de proximité, où l’on sent bien que ce sont des gens qui parlent
  • une jolie mise en page
  • la volonté de faire un blog 🙂

Alors, Femina — si tu relevais le défi?

How Will CoComment Change Our Commenting Habits? [en]

I was really excited to be able to talk about coComment yesterday Saturday night, and I really think it’s a great service, but I never thought it would pick up as fast as it did. As I heard Robert saying at LIFT, the blogosphere is not about how many people read you, but about who does, and how things scale and can get out of hand once the masses get hold of them.

CoComment is already changing the way I participate in comments (conversations!) on other blogs. I feel more connected. I feel like it makes more sense to leave a comment on a blog I scarcely visit, because it’s not a message in a bottle anymore: I have an easy way to get back to it. CoComment makes my activity on other blogs visible, so it encourages me to be active (yeah, that’s how I am! I like the spotlights, didn’t they tell you?) and maybe more conversational.

On the other hand, this is what I see coming: more popularity for popular blogs or posts or commenters (coComment will amplify the feedback loop effect for comments). Easy celeb’ stalking. Maybe more self-consciousness about “where I comment” and “what I comment”? Comments by top commenters will have a different weight on your blog, and different consequences, because they’ll get a different visibility. A-lister X’s comment on a lowly blog may have gone unnoticed until now, but if they use coComment, it won’t anymore. Will we start signing out of coComment to retain privacy over a certain amounts of comments we make, and that we don’t want in the public eye?

I’m really happy to see coComment gaining so much popularity. I’m just a bit worried. Is this too much success/visibility to soon? I’ve seen people (gently) bitching around already about what a shame it was that coComment did not support all blog platforms, or that it only tracked comments by coCommenters. Laurent says he’s pushing to open it up on Monday night, but I wonder: is it really a good idea? What are the risks involved? What has the most potential for damage: frustrating people because they can’t yet be “part of it”, or not being able to manage the scaling, user feedback, and user expectations for a public service?

I know I’m a worry-bug, and Laurent and Nicolas are smart and know the insides of the service much better than I do — so I’ll just go and prepare my stuff for school and worry about useful things for my life just now (like, what am I going to teach this morning). All the same, guys: “Soyez prudents!”