Fragmented Conversations
When someone blogs about someone ELSE'S blog post, where should YOU leave a comment?
For example, yesterday I blogged about Lan Bui's troubles with Podtech. As a result, some folks left comments on my blog, which I dig... but unless Lan himself stopped by, he'd never have seen them.
Conversely, had everyone only commented on his post, I'd have been under the impression that my two cents hadn't furthered the conversation.
Proposed Solution
What the blog world needs is a conversation tracker.
This way, after Lan made his initial blog post (for example), anyone else who'd blogged about the issue would have their post automatically included in that conversation stream. Then Lan (or whomever originates a blog post) would be able to see all other posts made regarding the original post / topic.
Plus, everyone else further down the conversation chain could see up and down the trail in both directions, AS WELL AS seeing any nodes that grow off their OWN posts about the subject.
In addition, any comments made on subsequent branches of the topic could also be cross-posted back to the preceding blog posts -- for example, Roxanne's comment on my post could also be CC'ed back to Lan's post, if so desired.
So, in the end, the structure looks more like a tree than a river.
Programmers of the world, you have been prompted.
For example, yesterday I blogged about Lan Bui's troubles with Podtech. As a result, some folks left comments on my blog, which I dig... but unless Lan himself stopped by, he'd never have seen them.
Conversely, had everyone only commented on his post, I'd have been under the impression that my two cents hadn't furthered the conversation.
Proposed Solution
What the blog world needs is a conversation tracker.
This way, after Lan made his initial blog post (for example), anyone else who'd blogged about the issue would have their post automatically included in that conversation stream. Then Lan (or whomever originates a blog post) would be able to see all other posts made regarding the original post / topic.
Plus, everyone else further down the conversation chain could see up and down the trail in both directions, AS WELL AS seeing any nodes that grow off their OWN posts about the subject.
In addition, any comments made on subsequent branches of the topic could also be cross-posted back to the preceding blog posts -- for example, Roxanne's comment on my post could also be CC'ed back to Lan's post, if so desired.
So, in the end, the structure looks more like a tree than a river.
Programmers of the world, you have been prompted.
Labels: blog tag, blogging, comments, communication, community, lanbui, podtech, social networking
posted by Justin Kownacki at
1:28 PM
4 Comments:
Barring a programmatic solution, Technorati can be helpful in these cases.
By
Evan, at 1:47 PM
Christina Schulman's Convo (http://convotracker.com) does some of what you've proposed. More importantly though, it was created for exactly the reason you've identified and she's pretty open to suggestions/improvement. You should email her some of your thoughts sometime.
By
Jia, at 3:19 PM
Yeah, what Jia said.
By
Woy, at 8:19 PM
Leaving a track back can sort of solve this. Lan would then know you have posted something in regards to his post and he then can check back to your post to see comments. But I like your idea better. Someone get on that.
By
Clintus McGintus, at 11:08 PM
Post a Comment
<< Home