This post originated from an RSS feed registered with .NET Buzz
by Jeff Key.
Original Post: Distributed not-so-good when it comes to blog comments
Feed Title: Jeff Key
Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/jkey/Rss.aspx
Feed Description: Topics revolve around .NET and the Windows platform.
(Please excuse me while I break my #1 blogging rule[1].)
I responded to a ProvostPost yesterday with a minor rant about posts linked to posts linked to posts and the comments generated on all posts about a single topic. I almost responded to a Watermasysk bit with the same incoherent babbling, so instead I'll re-post it here and try not to bother anyone else.
[The lack of comment] threading is a real bummer, but the thing that really gets me is best illustrated by an example: John posts a great, thought-provoking blog entry. Suzy posts a link to it on her blog, with some comments. Doug posts a link to Suzy's and John's posts, adding his own comments. Chain continues. People start posting comments to John's, Suzy's and Doug's posts. It's a complete mess. You have fifty conversations about the same thing in fifty different spots. I think some great interaction is being missed because of this. The thing that would solve it would be read-only posts. If you link to a cool post, do everyone a favor and mark yours read-only to encourage those with comments to post in the original post. Easy, no?
I agree with Scott that it's “freaken fabulous“ to have so many great conversations about a topic, but taken in aggregate there is a significant amount of redundancy. Maybe Rory can wedge the read-only bit into his ASS.
Previous Topic
