How user comments should work on the Web
Written by Rick Silva   
Saturday May 14, 2011

The folks at Mojo are looking for ideas on making the Web work better for journalism sites.

Mojo is a partnership between the Knight Foundation and Mozilla.  For you etymologists out there, Mojo = Mozilla + Journalism.

Mojo's current focus is on user commenting.  Here are my thoughts on the way commenting should work on the Web:

Any sensible commenting system indents responses
In order for any meaningful online discussion to take place, responses to comments should be indented and should appear right after the text that is being responded to.  Displaying comments strictly in chronological order begets only confused readers.

Reading the comments on The Boston Herald's site, for example, is maddening.  You see a banner there that says "RedSoxFan replying to Andy" and then RedSoxFan's comment: "You got that right!"

The problem is that the reader has no idea what Andy's original point was.  RedSoxFan's reply is on page 27 of the comments and there is no post by Andy on that page.  So, assuming the moderator didn't delete Andy's post, it must reside somewhere on the previous 26 pages of comments.

But where?

At this point the reader has to decide whether it is worth hunting for Andy's original comment or not.  The reader has no idea whether to give RedSoxFan a thumbs up or a thumbs down, because he has no idea what RedSoxFan thinks Andy is right about.

This is no way for human beings to communicate.  The indented approach is far better:

Andy
Obama's birth certificate is fake!

    RedSoxFan
    You got that right!

Now the reader can understand what is being said.  (He may be concerned for humanity, but at least he understands the discussion).  Now that the reader understands what is going on, he can jump in and participate in the discussion by replying to either Andy's comment or to RedSoxFan's.

This need for indented comments creates an interesting technical hurdle
There is no limit to the number of responses a comment thread could accumulate, and each response should be indented:

Stan
I disapprove of nuclear energy.


   Kenny
   What's the worst that could happen?


      Butters
      Gee fellas, I don't think it's safe.


         Cartman
         What?  Nukes rock!  We should have more!


             Towelie
             No way!  What if there is a meltdown?


                 Cartman
                 What do you know about meltdowns?  You're a towel!


                     Towelie
                     No, YOU'RE a towel.


                         Cartman
                         No, YOU'RE a towel.


                             Towelie
                             No, YOU'RE a towel.


                                 Cartman
                                 No, YOU'RE a towel.

This could go on for quite some time...

Typically, web designers don't object to vertical scrolling. If a page has a lot of content, users don't mind scrolling down to see what's at the bottom.  But it is frowned upon to have a lot of horizontal scrolling.  Typically, users don't want to scroll left and right.

But for comments, a large scroll area running from left to right is perfectly valid - and is preferable to making the user click a link or use other navigational controls.

From a technical standpoint, the question becomes "what is the best way to help the user navigate very wide screens".

Of course the horizontal scroll bar and left and right arrows are available, but it would be far better if the user could simply drag the screen left and right.  This is far more intuitive and useful.

The new Drag and Drop functionality of HTML5 has been much-ballyhooed, but for comments, all we really need is the Drag - and it should work for the entire screen.  The user should be able to click on the screen and simply drag it left or right to see all the fascinating towel-related comments.

While we're at it, let's allow the user to drag the screen up and down as well on comment pages.

Preventing curse words
Curse word prevention is best handled on the front end in a very AJAXy manner.

Typically, the user types his comment and clicks the submit button.  The best way to prevent swearing in comments is to nip it right in the bud.  When the user types a word on the no-no list, disable (grey out) the submit button, highlight the offending word, and display a message to the user explaining that the word is not allowed and they better straighten out and fly right or their mother will wash their mouth out with soap.

The HTML might look like this:
    <input type="submitComments" value="Submit your comments" cursevalue="The highlighted word is not allowed. Please rephrase.">

Most forums already maintain a list of naughty words that could be used for this purpose.

Low value comments
Many forums today have a way for users to vote comments up or down.  Different forums use the vote totals for different purposes.

The best use of this data is to display the vote total for the comment, and use it to sort among other comments at the same hierarchical level.

In this example, the comment responses at level 2 are ordered by votes, not by timestamp:

Original Commentor   +4
I'm uncomfortable with the US position in Libya...

    Brilliant Responder  +22
    But the Treaty of Versailles specifies...
   
    Average Responder  +6
    True, but on the other hand....
   
    Forest Gump   -28
    I like hats.

It doesn't matter who responded first.  The best comments at that level of the hierarchy should rise to the top.

Some sites put too much value on the vote total data, for example, hiding comments below a certain threshold.  This is a bad idea because it not only squelshes dumb posts, but also good ideas that are unpopular.  The best approach is to display all comments, but display insightful comments more prominently.

IP Addresses with multiple forum accounts should be allowed, but noted
To prevent sockpuppeting, online forums should display "37 accounts on TheBostonObserver.com have been created from this user's computer" next to the user's account name.

This would not prevent a user from posting from a library or other public place, but it would alert the community when a user is posting under multiple accounts.

Users should be allowed - and encouraged - to delete old accounts to remove the message.  The message should only show the number of active accounts associated with the IP address.

When voting on the comments of others, there should be only one vote allowed per IP address.

Those are my comments about comments.  Please leave a comment.  ;-)

 

Add comment


Follow The Boston Observer on Twitter