Twitter Killed My Blog and Comments Killed Our Links [en]

I hope the provocative title grabbed your attention.

Let me say it straight out: my blog is not dead, neither are our links.

But I still have a point.

Twitter is IRC on steroids, for those of you who have already experienced the irresistable draw of a chatroom full of smart witty people, 24/7. Twitter is my very own IRC channel, where I do not have to hear those I do not care about. It’s less geeky than IRC, which means that many of my “online spaces” collide there.

It’s intoxicating. I love it. I can spend all day there.

But that’s not why I would provocatively say that it has killed my blog. Twitter is a content-sharing space, not just a super IRC channel. Found an interesting link? Five years ago, it would have morphed into a blog post, because that was pretty much the only way to share it. Nowadays, dump it in Twitter. Arrived safely at destination? Again, 5 years ago, blog post. Now, tweet.

New tools have an impact on how we use old tools. Sometimes we abandon them altogether, but most of the time, we just redefine the way we use them. This is what I was trying to explore in the first panel I ever moderated, at BlogTalk 2008 (crappy video).

So, no, Twitter did not kill my blog, but take a group of bloggers and give them Twitter accounts, and the temperature of the blogosphere changes. All the high-speed stuff moves to Twitter.

If you just look at the present, it’s no big deal. People are still connecting. That’s what all this social media/software is about, right? Connecting people. Online. But the problem with us spending all our time swimming in the real-time stream is that it’s just that, a real-time stream. Not much is left of it once it has passed.

Take this short piece about translation I wrote nearly 10 years ago. It’s not a masterpiece, but it’s still there, as readable as it was when I wrote it. Had this taken place on Twitter, nothing much would be left of it. Gone with the wind, if I dare say.

Many many years ago when I first started blogging (can you tell I’m on a nostalgic streak?), blogs did not have comments. Hell, I barely even had permalinks when I started. Permalinks were the key, though: they allowed bloggers to link to each other’s writings.

And we did. Conversations would bounce from blog to blog. They weren’t chatty like on IM, IRC, or Twitter. They were blog-post-speed conversations. We would have to think (a little) before we wrote.

Even though comments are a wonderful invention and I would never want to take them back, they did ruin this, in a way. People started leaving comments all over the place and didn’t come back to their blogs to write about the conversations they were participating in. It’s one of the reasons I was so excited about coComment when it came out, or services like BackType (which also seems to have backed out of tracking comments one makes) or Disqus. (Aside: see, I’d love somebody to hire me to do some research and write a memo on the current state of the comment-tracking-sphere and all the players involved. I could totally see myself doing that.)

With comments came less of an incentive to link to each other on our blogs. With Twitter (and Facebook), less of an incentive to share certain things on our blogs, and also, less of an incentive to comment, as it became much easier to just “tweet a quickie” to the post author (therefore making our activity visible to all our followers). And with the death of Technorati tags (I’ll call it that), we bloggers are now connecting to each other on other social networks than the blogosphere.

I think it’s time to actively reclaim the blogosphere as our own, after leaving it for too long at the hands of marketing and PR.

Bloggers, it’s time to wake up! Write blog posts. Link to your fellow bloggers. Leave comments on their posts, or better, respond to them on your blogs.

We don’t have to abandon Twitter and Facebook — just remember that first and foremost, we are writers, and that “conversation” (though ’tis a wonderful thing) is not writing.

Disqus Plugin Aftermath: Removing Duplicate Comments [en]

[fr] Comment se débarrasser de 5000 commentaires à double dans sa base de données WordPress!

Now that Disqus integrates Friendfeed comments, I could be tempted to give it another try, if I hadn’t spent an hour yesterday cleaning up my database because of an earlier attempt to use Disqus on this blog. After the story, how I did it — in case you’re in the same mess and could use the help.

Back in August, I installed the Disqus plugin for WordPress. Things started off not too badly, though I was a bit concerned that the plugin seemed to have duplicated all the comments in my database. It didn’t seem to show up on the blog though, so I didn’t worry too much.

After a few months, I was a bit frustrated with Disqus and the plugin (which was clearly an older version than the Disqus plugin available now). Moderating comments through the WordPress interface seemed to work erraticly, and some spam just wouldn’t accept to stay in the spambox. I never really tried to identify the exact problems too closely, I have to admit, but things were not really working how I expected them to.

Then a few (unrelated) people told me they had completely failed to comment on my blog with the new system. At some point, I got fed up and uninstalled it. Unfortunately, the duplicate comments which had been hidden from view remained there after uninstalling the plugin, so all the old comments appeared on the blog twice. I let the problem sit for a long time before attempting to fix it — wild hope there might be a ready-made script out there I could just run& in vain.

Here’s how I tackled the problem this week-end and ended up removing the duplicate comments without too much trouble, through PhpMyAdmin (PMA for short).

  • In PMA, I made sure that duplication seemed constant — it was
  • I discovered that the duplicate comments had “DISQUS” in the user-agent field
  • I dug around until I identified the last duplicate comment (when I installed the Disqus plugin, actually; I sorted the database comments table by comment date to do that)
  • I did a search, selecting comments which were younger than the last duplicate comment date AND had “DISQUS” in the user-agent field (the date bit is important, because comments posted while the plugin were active have “DISQUS” in the user-agent field but are not duplicates)
  • Then, I deleted everything that came up in the search — about 5000 comments (it helps to tell PMA to display 3000 lines per page when doing that :-))

Hope this can help somebody, and remember: always back up your database first!

Tumblr to Capture Comments? [en]

[fr] J'aimerais un système permettant de publier directement sur mon Tumblr les commentaires que je laisse sur d'autres blogs, sans passer par coComment.

The other evening, I was explaining that I still used coComment to capture the comments I made on other blogs. As always, people try to suggest alternatives: co.mments or disqus, for example. I appreciate the suggestions, but they show me that I haven’t managed to make myself clear.

CoComment does two main things:

  • track conversations you participate in (or want to keep an eye on) so that you are alerted when a new comment is added to the thread
  • capture the comments you make on other blogs so that you can collect them somewhere or republish them.

I use mainly the second feature. I’m not that interested in tracking all the conversations I take part in. Every now and again I am, and co.mments does indeed do the job, in an ad hoc way. Disqus is quite exciting and also allows centralization of the comments I make with the system (if I got it right), but it has the great disadvantage of still being too “blogger-centric” instead of “commenter-centric”: sure, I can install disqus on my blog (as a blogger), but it isn’t going to help me capture or track all my comments until all the blogs I visit have done the same.

So, like at the end of a messy break-up where you’re still sleeping with your ex, I’m still using coComment for the following:

  • capture the comments I make all over the place and republish them in my Tumblr.

That’s it. One thing coComment does pretty well, despite all the criticism I can make to the service, is capture comments I leave in a variety of comment forms (from WordPress to FriendFeed and Typepad and Blogger and even home-made in some cases) and spit them out in an RSS feed.

Yesterday, an idea dawned on me: what I really want is for my comments to be published in my Tumblr. Maybe we can come up with a way to do that directly?

I use Tumblr loads, and love it. The main thing I actively use it for (I’ve embedded a few RSS feeds in it) is for quoting interesting passages off blog/articles that I read. It’s very easy:

3 Steps to Share a Quote on Tumblr

  1. highlight some text on a page
  2. click on the Tumblr bookmarklet
  3. Tumblr automagically recognizes it as a quote, and pops up a window which you use to publish it.

The result of all this is that I have a Tumblr which is full of quotes, comments (thankfully coComment seem to have removed the nasty ads from the RSS feed I complained about), and other things (videos and screenshots, for example).

I’ve been thinking a lot (but not writing, I know) about how these new tools in my landscape, which weren’t there 8 years ago (in a few days!) when I started blogging, are modifying my publishing and interaction habits. The panel I moderated at BlogTalk in Cork was about that, actually, but I think we only brushed the surface.

So, back to the point for this post: I’d like a hack for my Tumblr bookmarklet — or maybe a separate bookmarklet (by Tumblr or a third party) which will publish the comment I’m submitting to my tumblelog. It would work a bit like the coComment bookmarklet: click it to activate it at some point before hitting submit — and it does its magic when you submit the comment.

If you like the idea, head over the Get Satisfaction and add your 2 cents.

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