A high proportion of authors appear to be resorting to complex commenting services such as Disqus, Sez Who, and IntenseDebate – which provide thread comments, cross-site popularity scores, and other features – after becoming dissatisfied with the out-of-the-box operation of their blog’s commenting system.
(Wp 2.7 will also offer threaded comments, which will be useful for WordPress users.)
Looking for the username of the individual who posted the initial remark on the page yields no results, proving that Google isn’t crawling the comments for Disqus and IntenseDebate. (For example, this query yields matches for the Disqus page rather than the simple page.)
There’s a link that reads ‘View this discussion thread’ at which comments should be. This will send you to a webpage upon the said Disqus site with all of your blog’s comments.
This is more than nothing because it includes a link back to your website. However, this indicates that Google believes the material in the comments belongs to Disqus rather than you.
http://simpable.com/code/disqus/ was used to test this; http://www.sexywidget.com/my weblog/2008/08/disqus-updates.html
You end up losing usability (couldn’t they at least supply a fixed link to the information?)
However, the comments are at least viewable.
http://www.webbiestuffs.com/2008/07/how-i-solved-sezwho-problem.html was used to test this; http://andybeard.eu/2008/03/mybloglog-social-activity-time-line-disappoints.html.
Once you tap on the ‘leave a response’ button, nothing occurs. As a result, the comments are hidden from Google, and the execution is awful – certainly, they could’ve had something meaningful occur when you tap it?
http://www.ultimatenoob.com/?p=425 was the page that was used to test this.
So far, Typepad Connect has a score of 0/10.
When you tap on this link, the page will reopen, but no comments will show. This appears to be yet an additional indication of the non-JS version’s terrible code. They’re still in beta, so there’s definitely time to correct it.