Disqus: Scoble, Winer and Fred Wilson Like it, Why I Don't
blogbusinesssummit.com
blogbusinesssummit.com
For me the huge plus is receiving blog comments via email. Currently they are not sending the MessageID in the Reference field so messages aren't showing up as threaded, but they are aware of this. IMO blog comments should be handled like mailing lists/news groups.
What I do care about is the fact that it took about 30 seconds to sign up and add the Javascript snippet to my site's footer template. It couldn't have been easier.
Removing as many hurdles as possible is key.
The Googlebot doesn't execute JavaScript, or count iframe'd pages as part of the original page.
Btw, search engines access j-kit's comments by indexing the RSS feed. You could probably fiddle with a DNS CNAME to have the RSS appear as if from "your domain."
This is far from a solution.
I haven't given it enough thought to know if that is possible though :-(
Unfortunately it appears that neither does :(
Anyone developing a new website should take the little extra time to support OpenID authentication, it would make the world a better place.
However, one nice thing about Disqus (like OpenID) is that you only have to register with Disqus once, and any blog using Disqus can use that one account.
A quick check of the faq, blog and api disproves this. You do own your comments and better still you can extract them via xml.
- http://disqus.com/faq/#faq-7
- http://disqus.com/developers/#api-methods
- http://blog.disqus.net/2007/11/05/export-comments-to-xml-com...
So you own your comments, can get access to the data. The only real data disqus can claim ownership is the right to infer from your data. It's this distinction that makes me think using the disqus service is valuable because they give you the ability to take your data away.
1) He's worried that the comments no longer are in his control, ie, on his server.
2) He's worried that because the comments no longer being his server, can not be cached by Google. He wants that Google juice, but when the comments now reside on the disqus.com domain, it's harder to connect the two.
The second one is a biggie. For the power users, they won't like this at all. The blogspot/wordpress.com folks wouldn't care, but the ones that make it their business to blog professionally would.
Then suck the comments up via xml or at the api (at some time in future TM) and redisplay your documents. Of course the other alternative is to host your own comments and deal with the associated problems. I guess the pro's should earn their money and deal with the comments with their own tech, time & resources.
For the rest of the world there is always alternatives and this service is looking good because of the "Freedom to Leave". Meaning you can stay because you are free to leave at any time. [0] So if you are a developer "Lock-in is the new Lock-out". The ability to get your data out is a feature of lots of successful services that attracted early adopters.
[0] SImon Phipps, Zen of Free, OSCON 2006, http://www.opensolaris.org/os/community/advocacy/events/tech...
Hi guys: here's my page. Comment on it, it resides on a separate server.
Hi guys: every week I'm going to update all my pages with an XML file to update the comments that reside on a separate server.
Like I said, the power users will not want to cede as much control or deal with so much bullshit. They want the comments on their server reflected through Google crawl. So Disqus is left with a choice if they choose to pursue the power users, sell it as a plugin and give them the code, or get bought out by WordPress or Moveable Type.
Power users can code :)
"... So Disqus is left with a choice if they choose to pursue the power users ..."
Is this the market they are in? I'm not sure but Dave Winer sure handles Disqus ~ http://www.scripting.com/stories/2007/11/29/specificallyAbou...
Scripting News is about as power user as you can get. I'm not sure what the Disqus target market is but I don't think it's the power-users that will have the problems as you suggest.
Posting to our server is.
Search engines do not index included JavaScript properly.
It sounds like your API addresses this, but as someone mentioned, what about the problem of Google penalizing sites with content showing up in multiple places?