How Digg’s New Comment System Should Have Been (Super Easy Fix)
Digg just rolled out a new comment interface, and it blows. The stupidest part is that the whole thing breaks without JavaScript on, making threads impossible to read on some mobile devices. Comment threads must now be shown by clicking “view replies,” which then uses AJAX to grab the replies.
The solution is obvious:
- The “view replies” link is a static link to another page with just that thread expanded (nothing else).
- The AJAX could still work on left click so no functionality is lost.
- This means middle clicking works.
- This means I can send comment threads to my friends.
- It would actually work WITHOUT JavaScript.
Bonus suggestions:
- When a comment has only one or two replies, show the whole thread (like before).
- Highly voted child threads should pop out of their parents to a top level thread.
- Crappy buried top level threads are moved to the very bottom of the page to further discourage spamming.
The new system encourages spamming. There is less incentive for people to use the reply button since their comment will be hidden behind a “view replies” link. Additionally, the AJAX is slow. The link itself is a useless link back to the page you are on.
And it’s extremely annoying when you hit “view” only to be greeted by a single grayed out comment that you must now click on “show comment” to see (I thought I just clicked that?):
Digg messed up. The solution is simple: stop thinking AJAX is the answer to everything. In this case, it was used poorly.
