Skip to main content

3 reasons to migrate to Disqus commenting platform

Over the last weekend, I evaluated DisQus commenting platform. I saw compelling reasons why Blogger's default commenting is primitive in comparison. Today I am launching DisQus on this blog. Here are 3 most important reasons that made this decision easy.

Larger User(base) engagement
Discus unifies users by multiple login providers. By adding this one widget, Your blog now has Facebook and Twitter users to identify themselves as commentators. They can like and share your posts in their walls and/or tweet them. For users with privacy concerns, comments are also allowed as a Guests. It even has OpenId support (Blogger does too).


Advanced comment posting, replying and moderation
Commenting on DisQus is actually fun. And followup are too. And for the owners, Moderation is much more easier. If you own multiple blogs, you can moderate all of them in one login. Even do it from email (also in Blogger). DisQus has intelligent options to guard your blog from spam. The most important feature is ratings and threads. This way comments with higher ratings and user engagement surfaces well. Users can reply to threads (also available in Blogger), even from their emails. Users love it.

Easy, Simple - Yet, Powerful
Installing is easy, So is importing your existing comments. Installation is completely non-blocking, so your page speed will change negligibly, if at all. There are number of tools to import/export data, show different widgets, even migrate across domains, if necessary.



Bonus: Awesome Support
While I was test driving, I encountered some technical issue. Although DisQus is free, the support is terrific.

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>