Okay, I’m probably exaggerating but it sure makes a good headline. At this point, most have heard the news that Automattic, parent company of Wordpress (which powers this blog) acquired IntenseDebate for an undisclosed sum. Offical news here, here and here.
IntenseDebate is one of the major blog commenting platforms out there. The other is Disqus, the one I use on this blog and one I tend to favor based on overall reliability and feature set. Both companies clearly get the value of commenting, user-generated content and the real power of conversation aggregation. But if I were to put the two on a score card on execution, Disqus demonstrates real innovative thinking on how to put an overall platform together and paint their vision of what conversation aggregation can do and how to do it. This was evidenced by their very early integration into Wordpress and Daniel Ha’s continued work to integrate into FriendFeed once they emerged a critical aggregation player as well.
But, what is also clear is Wordpress understands the value and importance of the comments on blogs (not that they didn’t before). And as the major blog platform, Wordpress has the value chain power to use this strategic acquisition to emerge as the leader in blogging as well as commenting. And it is for this simple but important reason, that they acquisition is a huge coup for IntenseDebate in prepping for the future to potentially become the ultimate winner in this segment. There is a sheer numbers game here and by Wordpress rolling Intense’s toolkit out as part of their builds, it will instantaneously deploy Intense’s technology to blogs everywhere. That removes one key obstacle for Intense that Disqus will continue to have to overcome in order to gain market share: convincing blog owners to install. Now, for IntenseDebate, it happens automatically.
Let’s hope that Wordpress remains agnostic in their approach to continue to allow third party developers to build, promote and florish inside the Wordpress platform. I would like to continue to remain a Disqus user and expect to see fantastic things from them. I will be keen to see how Disqus responds because we could be witnessing a business case of value chain integration that will be very tough to withstand.
Ron: That is the one area where I agree. The competitive rejections are ones I question. I can see why they do it but I don't like it, it spurns the spirit of innovation.Chris: Overall, I agree with you. What core apps (when you set aside open principles) are we missing? It is a good question. The one thing I would say is that there is an element […]
Sounds pretty far fetched that we could develop a system to overcome a 75% unemployment rate even with stratospheric government subsidy, simply because I don"t see human nature of "wanting more" changing at the needed magnitude. The first thought that came to me reading this post is that Ford and Ayn Rand should go bowling together. Would be q […]
It would seem this really works in two scenarios. First, where you have a good team but the business is not going to go. Second, and related, when 3.5% of the other company is going to be bigger than the total of your own.Read more comments by Lou Paglia […]
How does the assets and the revenues of the company you are acquiring factor in? I would suspect the normal way but how to deal with multiples on revenues and the like become interesting particularly if you don't plan on continuing to leverage their existing line of business?Read more comments by Lou Paglia […]
Great post Raanan. I will admit, I think have sent my share of 'intro' subject line headers. I will try to refrain from doing that in the future.The one that made me laugh is the one where you are kept on the thread after the intro is made. How come you are never kept on the thread when there is something "really" compelling being discu […]
Doesn't make a lot of sense to me. Would be interested in hearing LinkedIn's rationale for this decision. Also surprised that this is the type of thing they are spending time (unless of course it has become an acknowledged pervasive problem for abuse).Read more comments by Lou Paglia […]
I do not disagree from a logistics perspective. But Apple succeeds as an experience company and let's face it, they succeeded quite well by not always listening to users. While often not the right approach, it works for them. I can't deny that being more open is quite a change from their proven methods and DNA.Read more comments by Lou Paglia […]
Does Amazon have "instant on" for all book submissions or only from reputable suppliers? This is the equivalent of letting anyone submit their own book to a Kindle ecosystem but in this case it is trickier because it is an app and actual code is runiing that could hose the device and device experience.Read more comments by Lou Paglia […]
But code reliability and standards adherance is only half the equation. What about the qualitative half which involves a human evaluation on the actual content of the app. Letting everything through may work in an open source world but it is very much misaligned to the corporate DNA of Apple and what many can attribute to their success.Read more comments by […]
I don't disagree with the existence of app store moderation process. It is a risk though for the amount of time it takes. The biggest frustration danger that I see Apple having is lack of transparency in the review and approval process. If they could add transparency to the process by making it more clear when it was under review and more clear reasonin […]
Disqus must be Disgusted
Okay, I’m probably exaggerating but it sure makes a good headline. At this point, most have heard the news that Automattic, parent company of Wordpress (which powers this blog) acquired IntenseDebate for an undisclosed sum. Offical news here, here and here.
IntenseDebate is one of the major blog commenting platforms out there. The other is Disqus, the one I use on this blog and one I tend to favor based on overall reliability and feature set. Both companies clearly get the value of commenting, user-generated content and the real power of conversation aggregation. But if I were to put the two on a score card on execution, Disqus demonstrates real innovative thinking on how to put an overall platform together and paint their vision of what conversation aggregation can do and how to do it. This was evidenced by their very early integration into Wordpress and Daniel Ha’s continued work to integrate into FriendFeed once they emerged a critical aggregation player as well.
But, what is also clear is Wordpress understands the value and importance of the comments on blogs (not that they didn’t before). And as the major blog platform, Wordpress has the value chain power to use this strategic acquisition to emerge as the leader in blogging as well as commenting. And it is for this simple but important reason, that they acquisition is a huge coup for IntenseDebate in prepping for the future to potentially become the ultimate winner in this segment. There is a sheer numbers game here and by Wordpress rolling Intense’s toolkit out as part of their builds, it will instantaneously deploy Intense’s technology to blogs everywhere. That removes one key obstacle for Intense that Disqus will continue to have to overcome in order to gain market share: convincing blog owners to install. Now, for IntenseDebate, it happens automatically.
Let’s hope that Wordpress remains agnostic in their approach to continue to allow third party developers to build, promote and florish inside the Wordpress platform. I would like to continue to remain a Disqus user and expect to see fantastic things from them. I will be keen to see how Disqus responds because we could be witnessing a business case of value chain integration that will be very tough to withstand.
Sphere: Related ContentPosted in: social software, strategy, user-generated content.
Tagged: Automattic · blog commenting · Disqus · Intense Debate · Wordpress