Wandering Thoughts archives


Slashdot's tacit admission of failure

Slashdot has recently started running what it calls 'Backslash' stories, which have (as it puts it):

[...] some of the most interesting comments and exchanges on a handful of yesterday's Slashdot posts [...]

To me, the most interesting thing about these stories is that they are a tacit admission that Slashdot's comment management model is broken and that a lot of people don't read the comments on Slashdot stories. If most people did regularly read Slashdot comments, Backslash stories would be redundant and thus unnecessary. That Slashdot has introduced them and made them a regular feature suggests that they are not.

(This matches anecdotal evidence; neither I nor a fair number of the people I chat with online bother to read the comments on Slashdot stories and haven't for some time. It's just not worth it, because even at +5 there's too much noise in that signal.)

Since some of the comments that get promoted to Backslash stories are not among the highest-rated comments, this isn't just that there are too many highest-rated comments. It seems to be what Slashdot considers an outright failure of the system to rate comments as highly as they deserve, and indeed one recently used comment was only rated +2 (where +5 is the highest). (The Backslash stories also don't necessarily run the full comments, so there is editing even beyond mere selection and spelling corrections.)

It'll be interesting to see if other community moderated websites follow Slashdot's lead and make similar changes, or for that matter if Slashdot makes more moves to a more editor-based environment to differentiate itself from sites like reddit and digg (ceding more and more of the 'moderated by the community' ground to them).

tech/SlashdotFailure written at 23:12:02; Add Comment

Page tools: See As Normal.
Login: Password:
Atom Syndication: Recent Pages, Recent Comments.

This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.