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.
Labels:

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery
Read More >>

How to Make a Local (Offline) Repository in Ubuntu / Debian

If you are in a place where you dont have internet (or have a bad one) You want to download .deb packages and install them offline. Each deb file is packaged as a seperate unit but may contain dependencies (recursively). apt-get automagically solves all the dependencies and installs all that are necessary. Manually install deb files one by one resolving each dependency would be tedious. A better approach is to make your own local repository. Before you actually make a repo, You need *all* deb files. You dont practically have to mirror all of the packages from the internet, but enough to resolve all dependencies. Also, You have to make sure, you are getting debs of the correct architecture of your system (i386 etc) # 1. make a dir accessible (atleast by root) sudo mkdir /var/my-local-repo # 2. copy all the deb files to this directory. # 3. make the directory as a sudo dpkg-scanpackages /var/my-local-repo /dev/null > \ /var/my-local-repo/Packages # 4. add the local repo to sour...
Read More >>

Decorator for Memcache Get/Set in python

I have suggested some time back that you could modularize and stitch together fragments of js and css to spit out in one HTTP connection. That makes the page load faster. I also indicated that there ways to tune them by adding cache-control headers. On the server-side however, you could have a memcache layer on the stitching operation. This saves a lot of Resources (CPU) on your server. I will demonstrate this using a python script I use currently on my site to generate the combined js and css fragments. So My stitching method is like this @memize(region="jscss") def joinAndPut(files, ext): res = files.split("/") o = StringIO.StringIO() for f in res: writeFileTo(o, ext + "/" + f + "." + ext) #writes file out ret = o.getvalue() o.close() return ret; The method joinAndPut is * decorated * by memize. What this means is, all calls to joinAndPut are now wrapped (at runtime) with the logic in memize. All you wa...
Read More >>