waving android

I am currently a software engineer at Google, where as a member of the Android platform team I build frameworks and user interfaces.

The blog here at is mostly historical; you can find more recent posts on .

Experimental: Twitter for comments

February 26th, 2009

Abstract

Blog comments don’t really encourage robust discussion. (The only people who look twice at the comments are the original author and readers with an axe to grind.) But ad hoc multi-party discussion does happen on Twitter. I’m experimenting with promoting Twitter to a first-class blog comments system.

No Comment

I’m not the first to notice this, but blog comments are awkward. Many excellent blogs have eschewed them for various reasons; Jason Kottke doesn’t want the babysitting chore of dealing with a large, vocal community. Alex Payne doesn’t think good conversations emerge from blog comments because they encourage “hit-and-run attacks, unintelligible ramblings, and truckloads of spam.” John Gruber simply prefers a streamlined reading environment.1 It’s not that they’re uninterested in discussion; rather, they’d prefer it happen elsewhere:

  1. On your own time and property (viz., on your blog), or
  2. In some neutral forum (Reddit, Twitter, etc.).

Option #1—the promise of a blogosphere criscrossed with scintillating conversation—is the reason TrackBack exists: without it, the author and readers alike have no way of knowing where on the web to find the next response. Unfortunately, because it allows untrusted parties to post links and content to your blog automatically, TrackBack is an enormous spam magnet and has therefore fallen into disuse.2 A number of ad-hoc techniques replace it, exemplified by the convention of promulgating choice responses (received out-of-band, e.g. by email or IM) by appending them, simply, under the heading UPDATE.

A few conscientious bloggers—even those that, nominally, want you to Get Your Comments Off My Lawn—carefully comb their referrer logs for links to well-considered responses from other bloggers, which they will then compile into a “Responses” post. Twitter hacker Alex Payne, for example, recently rounded up the rebuttals to his “ranty”3 article of a few weeks prior. It is his claim that, because each of those bloggers chose to respond on his own blog—taking full responsibility for his opinions under his own masthead and in front of his own readers, rather than leaving a comment “off the record” on a distant site—those perspectives were more thoughtful and more clearly articulated.

This leaves us with option #2: Comments in the Neutral Zone. Assuming you have a high-profile discussion-free blog4 and also read Reddit, this works pretty well: your adherents and detractors have a sandbox in which to have it out, and you can drop in occasionally to poke the discussion. Unfortunately, the stars must align for this technique to result in interesting conversation; the likelihood is that some essential piece of the conversation—either author or readers—is not looking at your shiny new Reddit thread.5 In fact, the only thing that ties the group together is the original blog post, which puts us right back where we started: blog discussion, it would seem, must occur—or at least appear—on the blog itself.

But this is still insufficient, because while the ideal discussion group for a given blog is defined as a blog’s readership, we have only solved the problem in space, not in time. How often do you check the same blog post to see if there are exciting new comments? As a reader, I hardly have the time to leave a single comment, let alone check back to see if there are interesting responses. I find this to be true of readers of dsandler.org as well: it’s fruitless for me to respond to your comment with one of my own, because you’re unlikely ever to visit this post again to read it.

This is what I think of when Alex Payne refers to “hit-and-run attacks”—a natural side-effect of the fact that most readers will look at a blog post (and the current state of the discussion) at most once. The only people who look twice at the same blog entry’s comments are the author (who has the luxury—or compulsion—to respond to each and every one) and anyone with an axe to grind. All others, if they comment at all, will leave a single comment and then never return. This is not conducive to discussion.

And yet, discussion happens

I’m increasingly getting feedback about blog posts on Twitter (with good reason: I mention the post on Twitter myself, explicitly inviting a conversation). For example, when I finally deployed the recent redesign of dsandler.org late last year, I mentioned it on Twitter (where a few people had already been offering complaints about my intentionally awful interim design). I received a few comments on the blog post itself, but just as many via Twitter, so I decided to (laboriously!) copy some of those messages into the text of the post (see UPDATE).

Wouldn’t it be nice if such a thing were done automatically? For bloggers whose controversial articles (picking on @al3x again here) spawn a lot of Twitter discussion, could we actually promote Twitter to a first-class discussion mechanism?

See below

Yesterday I threw together some code to go search Twitter for any messages including the URL of the current page and display them as if they were comments. I had considered creating a unique keyword for each post on the fly (possibly using a hashtag, like “#dsandler_post_5″) that would string the conversation together, but the URL seems more natural (because people will put that into responses anyway, and besides, the TinyURL version is usually every bit as short as a hashtag).

Blindly including the results of a search on your blog is an easy way to get spammed, of course,6 so we’ll have to see how this goes. Note, however, that because the tweets are fetched by the client, they never actually appear in the blog when it’s crawled by search engines, so you can’t mess with my PageRank (or boost your own) by abusing this system—all you can do is cause grief. (So. Don’t.)

So, let the experiment begin: follow the link below to pre-populate a Twitter post about this entry (or simply include the URL or TinyURL in your message). Try to include the (Tiny)URL in any tweets that have to do with this post, insofar as that’s practical.

Oh, and: regular blog comments are turned off.


Update

5 March: I’m working on a new post to document the results of this little experiment. For now, I’m turning off the live Twitter search results and ossifying the state of the conversation as it stands today by including the results statically below.

The Twitter watercooler

Messages referencing this page as of March 5th (newest at bottom):


  1. This is a nice way of saying “Daring Fireball is intended to be The John Gruber Show—Starring John Gruber—A John Gruber Production—Filmed In Grubervision,” a sentiment with which I think John would agree. 

  2. I did some work on this problem early in my PhD program, upping the ante somewhat for TrackBack spammers, but blogs have mostly moved on. 

  3. “Ranty” via Adam Rice via Alex’s recap. (Look, it’s all intertwingled!) 

  4. A webcomic, particularly one that inspires conversation, is isomorphic to a blog in this regard. 

  5. Sometimes an eager reader is so helpful as to [volunteer for the position of Comments Czar, though unless the original author sanctions and links to this outsourced comments system, any discussion that takes place there will be doomed to obscurity. 

  6. You may recall that election.twitter.com was very easy to abuse as it showed, live, any tweet that included election keywords. 

9 responses

  1. Eine Kommentar-Revolution? ‹ dreitehabee  

    [...] davon, dass Reaktionen auf einen Beitrag am besten auf der eigenen Website stattfinden sollten und Daniel Sandler schlägt Twitter als Kommentaralternative vor. Auch bei Tumblr hält man vom [...]

    comment posted at 6:49 pm on 27 Feb 2009

  2.  comunque, sui commenti : arsenio bravuomo  

    [...] a quanto pare, sulla questione commenti nei blog, ci ho poi sempre avuto ragione io, con eoni di anticipo, anche [...]

    comment posted at 1:04 am on 28 Feb 2009

  3. appleton.me // Twitter as a Comments Platform  

    [...] idea from Daniel Sandler regarding the use of Twitter as a comments platform: Blog comments don’t really encourage robust discussion. (The only people who look twice at the [...]

    comment posted at 9:44 am on 05 Mar 2009

  4. Novel Integration: Twitter-powered comments | Social Media Mafia  

    [...] Experimental: Twitter for comments [...]

    comment posted at 10:31 pm on 09 Mar 2009

  5. Too busy to… » Blog Archive » Blogs: Conversation or Monologue?  

    [...] in February, the twitter-verse reverberated with a post describing a system for using twitter as a replacement for comments on blog posts. Regardless of the effectiveness or shortcomings of that particular system, I think the author [...]

    comment posted at 3:45 pm on 05 Apr 2009

  6. Twitter and URLs » Ross Shannon  

    [...] Sandler is experimenting with using twitter for comments, and makes some very good points about comments on the web in the process. Essentially, he pulls in [...]

    comment posted at 9:26 pm on 16 Apr 2009

  7. FETHR roadmap. (dsandler.org)  

    [...] Requests? I’ll leave the regular blog comments open so you can write longer notes than the Twitter watercooler will allow (although tweets are welcome as [...]

    comment posted at 8:16 am on 01 May 2009

  8. Re: Twitter spam. (dsandler.org)  

    [...] timeline, which I just burned about a thousand words inveighing against. As I mentioned when I started the experiment, this is easily abused; for now I’m explicitly courting tweets from strangers, and [...]

    comment posted at 12:42 pm on 05 May 2009

  9. No Comments • Geekaholic  

    [...] blog, and the conversation reaches more people that way. There was an experiment some time back on exclusively using Twitter to handle comments. I’m not really sure how that worked out. Seems pretty chaotic, so I won’t be doing [...]

    comment posted at 11:41 pm on 23 Jun 2009

newer: older: