Tuesday August 24, 2004

Comments on blogs are problematic for the same reason that email is problematic. When anyone can say anything without accountability, the spam and other types of garbage comes pouring on. SMTP and NNTP are strong supporting evidence for this. So how do we work around this?

Using a centralized authentication key like typekey is a nice band-aid but it still doesn't address the underlying problem that's difficult to contextualize who is behind the voice in the conversation. Besides, it's not nice. It's a vendor bound and therefore borg-like.

The owner of the voice is important. You can't link to their Orkut profile; afterall, the voice might not speak in Portugese. Who owns that conversational voice that's longing to participate?

Using trackbacks to string together post references is another hack to try get around the absence of conversation in blogs. But talking about a post is not the same as replying. And furthermore, it requires more protocol infrastructure since it requires every blog to be a pingable resource. And pings themselves are untrustworthy data payloads. It just doesn't seem to fit.

Sure, you can reference another post merely by linking to it. However, replying to it as you would a conversation is missing from the blogosphere.

Now suppose a link to a blog was enriched with an attribute to indicate that it is a reply. Say, a rel attribute like rel="reply-to" -- blogging tools and mapping engines could be enabled to thread together conversations by traversing these link relationships. SMTP and NNTP message readers have been threading conversations (i.e. correlating the "In-Reply-To" header) for years. It's time to bring this facility to the blogosphere.