How to make (Drupal) blogs more conversational

Blogs. Conversation. Not exactly two words that people would fit in one sentence. Blogs don’t talk to eachother; maybe with some trackback system, or via technorati, but even then they don’t really conversate.

Wilfred Rubens pointed me to a very good post on this matter.

Dave Pollard investigated the very nature of a conversation, looked at how this applies to online communities and explains very clearly how blogs can improve the actual conversation, both within the weblogs and within their blogosphere.

Let me take his points one by one and see what Drupal has to offer, or what Drupal should do better.
One important note: It is a known fact that modules often integrate badly (or not at all). That the contributions promise far more then they deliver etceteras. Don’t take my advice for granted, I tried less then one third of the modules mentioned below, and even that made me sad at moments. The modules listed below should be handled with care: don’t ever think ‘cool Bèr has a list with all the stuff Drupal can do, Its exactly what I need, I’ll go for Drupal. Choose with care. My comments are in italic.

  1. There should be a process to allow people to ‘subscribe’ to the comments to any blog post, and get notified of new comments posted.

    Subscribe, Organic Groups, Notify, Views and Comment RSS. Enough to choose from, I’d say, yet no ready-to-go-out-of-the-box solution.

  2. Each comment should have space for, and begin with, a one-sentence summary of the commenter’s point (not the subject or thread title, the point they’re making) to make browsing long comments threads easier.

    Nothing in Drupal nor in the contribs for this.

  3. The comment mechanism should require each commenter to indicate who they’re replying to: the author of the main article or the author of one of the previous comments. The blog tool should then automatically ‘thread’ the comments accordingly.

    This is a great benefit of Drupal, it comes with core Drupal!. I am not aware of any blogging tool that offers this threading.

  4. The comment mechanism should allow each commenter to indicate what kind of response they would like, by checking off one of (a) response is requested from the person their comment is replying to, (b) response is requested from anyone who wants to chime in, or (c) no response is expected (closing that thread). The person(s) who have been requested to respond should get an e-mail notifying them of this fact (in case (b) the e-mail would go to anyone who ‘subscribed’ to the conversations for the blog post).

    None of the listed subscription options mentioned under #1 offer anything like this.

  5. here should be a simple, short, polite way for the person getting a request to respond and who has nothing substantial to say, or wishing to acknowledge a compliment in a thread, to just say ‘thank you’ and close that thread.

    This too, is not possible with Drupal, nor with any of the contributions. If comments were nodes, however, such things would be simple to develop

  6. The ability of most discussion forums to copy & paste excerpts from whatever the commenter is replying to (Jo said: ” “, in a box to start the comment) should also be available in blog comments.

    One module for this, Quote, not to be confused with quotes. The module seems particulary well coded, using Drupal in a good way, for example, it runs trough the filter system.

  7. Trackbacks should be integrated into comments as separate threads that readers can pursue at the other site — they’re part of the conversation, too, albeit moved to another site.

    Last time I used it, Drupal’s contributed trackback module does not integrate comments and trackbacks. It’s discription tells me this did not change.

  8. The comments threads should be appended to the actual blog post, rather than being kept elsewhere apart. Some blog tools do this. Others (like the one I use) don’t.

    This is, in fact the only way Drupal can handle comments.

  9. Comments threads should make it easy to include links and other html (Radio Userland of late has been sending 403 messages to commenters using html).

    Drupals excellent filter system allows many more then this. which is its downside too: for Co Commentor this wayy to geeky and huge page, babbling about filter formats and HTML is too much.

  10. Bloggers and commenters should be able to note their Skype address and/or IM address and invite others to sign up for scheduled real-time chats on the entire article or some aspect or comment thread stemming from it. The recorded archives of such real-time sidebar conversations should be embedded in, or at least linked to, the applicable thread.

    Drupal has the comment fields hardcoded as far as its very core. This is not only impossible, even with contributions, it is technically not possible with the current architecture.

So, the conclusion is, that Drupal has some work to do, but that the components, or at least the possibilities are there!

Do you know any other modules that I missed? Are there issues (with patches) that cover some of these features waiting to be reviewed and tested?
Could Drupal be the first ‘Blogging tool’, even if it is not a blogging tool, that has the ingredients for real conversations?

yes wordpress has a field

yes

wordpress has a field you can choose, if someone responds to your comments you will be notified by email

in the email there is a link back to the blog

I do believe this is perfect and Drupal needs this sort of option as well

I must say I’ve been

I must say I’ve been impressed with some of the Drupal Blog’s I’ve seen lately.

Its obvious that people like looking at other people by the success of myspace and facebook etc.

I think you could make comments better by having photo’s of the commentor. Maybe MyBlogLog has an API.

Hone, I agree with you, I

Hone, I agree with you, I was thinking about the same thing…pictures with the commentator will make it more creative

imho a very telling remark

imho a very telling remark is the line: One important note: It is a known fact that modules often integrate badly (or not at all). That the contributions promise far more then they deliver etceteras.

Drupal chooses the path of a very lightweight, versatile core, leaving many solutions to be solved in contributed modules. The downside to being lightweight and versatile, is a (perceived) lack of standard components. ‘Standard’ in the sense of ‘inherently part of the whole and co-developed with the core’, meaning functionality you can depend on being there, now and in the future.

I understand the past choices of not including more modules in the core distribution, but I could definately see a system of ‘endorsed’ (or maybe even official) modules, whose development is closely tied to the development of the core.

With respect to the conversational aspects of comments discussed here… a conversation.module might take these points and some functionality found in other modules and present them as a coherent whole.

Personally, I don’t really

Personally, I don’t really like the “all in one” modules.
In fact, these are the main PIAS when I talk about bad integration!

Lets look at an example: UIforums is a forum module that does a LOT. It is by far the most complete forum solution in Drupal. Yet this is the one module that does not integrate at all. It did not even use nodes last time I looked! I am not saying UIforums is a bad module, I am certain it helped Drupal, you, and lots of others, a great deal, yet it does not integrate.

A very dedicated, task-aimed module, on the other hand, will work a lot better. CommentRSS module, does what it says: Offer feeds for comments. Off course the author can add email features to it, can expand it with pingback features, integrate trackback systems etceteras. No: the author decided to make it only what it is: RSS for comments. full stop!

Now, Trackbacks. They are not comments. They may be that now, I am not sure, but for the sake of the debate, I will say they are not :). Were trackbacks normal comments, then CommentRSS would have a trackback feature. For free! But they are not, so CommentRSS and Trackbacs hardly integrate.

So, my main problem lies not in the fact that drupal is too scattered, but in the fact that people don’t develop against Drupal well enough. Okay, it takes time to learn all that Drupal has to offer, and by the time you think you learned it all, some very smart core developers improved everything, and you can start almost all over again.
But still, if you develop against Drupal. If you use Drupal APIs and Drupal Concepts wherever possible, your modules will integrate.

Is that not the main problem? Is it not so that modules whe hardly integrate, simply did not use Drupal APIs and concepts? or simply did not red the guidelines well enough?

Drupal has the comment

Drupal has the comment fields hardcoded as far as its very core. This is not only impossible, even with contributions, it is technically not possible with the current architecture.

Not quite. It’s possible to add fields to the comment form using the hooks introduced in 4.7, though few modules have taken advantage of it. With the new Node Comments module, it’s even easier. One can create a custom CCK type with whatever fields are needed.

Yes, very true. Forms API

Yes, very true. Forms API allows you to hook into any form, so even that is an opportunity to get this done.

However, you state correctly that nodes, acting as comments, are the real solution for this issue. Nodes allow all such power, and more.

Showing a few extra fields with comments should not be too hard. The hardes part, in fact will be to remove the hardcoded (required) core fields.
Bloggers and commenters should be able to note their Skype address and/or IM address Is therefore not too hard to achieve.

The recorded archives of such real-time sidebar conversations should be embedded in, or at least linked to, the applicable thread. however, is a bigger task: AFAIK only nodes have the power and the flexibility to offer integration with external aplications. comment APIs are not powerfull enough to allow such things. E.g. adding files to comments is impossible

That’s true as far as I

That’s true as far as I know, but according to an enquiry I made, using the node comments modules will effectively break the existing comments functionality, and may break the way the forums system works…

http://drupal.org/node/108487

…although the example site listed in that module’s page links to a site which has the forums enabled also, so I’m a little at odds with how the whole thing ties together really!

Give it a little time. Dries

Give it a little time.
Dries has said on different occasions that he feels nothing for making comments nodes in core.
But this module is still new. Give it some time to mature, give it some time to create momentum. Then it will not only become more polished, it will also have the proper ‘weight’ to ‘demand’ core patches that allow it to hook into the comment workflow better.

Comments as nodes is new, unproven technology. It will get there, but its cutting edge right now: so expect things not to work. But expect them to be fixed very fast too.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • You can use Markdown syntax to format and style the text.
  • Allowed HTML tags: <br> <a> <em> <strong> <s> <li> <ul> <ol>
  • Lines and paragraphs break automatically.

More information about formatting options