re: re:

Sep. 14th, 2009 09:28 pm
dr_tectonic: (commanding the minions)
[personal profile] dr_tectonic
Okay, having just been thoroughly confused detangling what was in response to what over yonder on another site, here's the new rule. Pay attention, everybody who might ever develop social software of whatever type:

If you allow comments? Thread them.

Period.

I don't care if it's more work. I don't care if it doesn't play nicely with your infrastructure. When people are saying things, they're usually saying them in response to something else that has been said, and making it easy to see how these things line up with one another is essential to the actual "communication" part of that whole saying stuff thing you're enabling. Otherwise it's all just half a cell-phone conversation in public, which is both useless and annoying.

Comments are threaded. ALWAYS.

I have decreed it! Now make it so!

Date: 2009-09-15 05:51 am (UTC)
From: [identity profile] nehrlich.livejournal.com
Yes, thinking about it too much. Writing a blog post in penance to get all those extra thoughts out of my overactive head.

I agree to some extent that we should go with the flow, but I actually agree with Joel's point which suggests that threading is the beginning of the slippery slope to the insane line-by-line nit-picking of Usenet. Forcing people to come up with the crazy hacks reminds commenters that they are doing something undesired, so they'll only do it if necessary. Supporting conversation spinoff natively encourages that behavior.

As usual for me these days, that means it boils down to a design question - what behavior do you want to encourage? Therefore, it is not decree-able, as different designs support different goals.

Or something.

Date: 2009-09-15 06:14 am (UTC)
From: [identity profile] dr-tectonic.livejournal.com
It is decree-able if all designs support the same goal of making things convenient for ME...

Date: 2009-09-15 06:30 am (UTC)
From: [identity profile] nehrlich.livejournal.com
I am shown.