Over the past few months we’ve moved back and forth between Intense Debate and the default Wordpress comment system for Imulus Insights. Over this time period I’ve had the chance to get a bit more fully involved with Intense Debate’s foundation, plugin, and structure. This process has for the most part been a massive headache. However, I have to admit that if the service weren’t something we felt had potential we wouldn’t have stuck with it. I’m a fan of admitting when something isn’t a good fit and moving to find a different solution. In this case the benefits seemed worth it so we stuck with it and now Intense Debate is fully integrated and styled into our Wordpress install.

That said. I have some criticisms.

Let’s take a brief look at some of Intense Debate’s HTML:

Okay, I’m not going to spend too long on this as I think the image above illustrates pretty well why working with Intense Debate’s DOM structure is a nightmare. Still, I’ll talk about a few of my major annoyances.

Wrapper, wrapper, wrapper, small-wrapper, smaller-wrapper…

First, Intense Debate is filled to the brim with what seem to be uncessary divs, wrappers, classes, and ID’s. For the life of me I just can’t see why they would need five or six wrappers for specific elements. I just don’t think their users really need that much customization potential. If it was my call I would make the trade off between four wrappers with ID’s and Classes for a simpler system that’s easier to work with. Granted, maybe I can’t ajax in every element on-demand but at least the product would be easier to work with.

Names should be used to make things easier, not harder.

Second, the naming convention they use could be a lot more straight forward. Instead of:

#IDSubscribeToThisWrapper

perhaps stick to something a bit simpler:

#idc-subscribe

Document your DOM.

Third, provide better documentation for your developers. I spent a good chunk of time on the Intense Debate CSS documentaiton page, and while the page is a good start to documentaiton, it by no means has the depth of information that is required to “style” each indvidual element of Intense Debate. If you’re going to add ~200 classes and IDs to customize the applicaiton, at least document it so I can see what I’m working with.

I spent some time on the comment customization layout on the Intense Debate site — and while some of the options are nice, it’s not quite enough. For instance, Intense Debate allows you to link to your own CSS file for style customizations. However, they don’t offer any sort of example CSS file if you want to see how they did things to begin with. This… would be a nice thing to have. Granted I can work with a web inspector to see their styles, but it’d be much nicer to have a tangible CSS file that I could go thourgh.

My wish.

I recognize that some of the above criticisms are being done in order to provide their users with the most amount of customization possible. However, I feel that if customization is the end goal Intense Debate should take a different approach all together. Here’s what I suggest:

Give customers two choices.

1. The ability to use your generated HTML in a widget format (like currently exists)
2. A set of Wordpress template tags that can be used to run functions dynamically without generating the HTML

I would have a substantially reduced amount of criticism is I was able to use the Intense Debate service without having to deal with there ridiculously dirty HTML. Template Tags would allow me to pick and choose what portions of the service I want to incorporate, as well as the ability to style things exactly to my liking with my own HTML stucture. No more !important; declarations, no more individualized Intense Debate only stylesheet, just simple, clean, easy to use Wordpress template tags. This is how the majority of plugins currently work for Wordpress and I see no reason that Intense Debate can’t follow that method. And considering they’ve been purchased by Automattic I’m hoping this is in the works.

End Verdict

I have to admit that the comment traction gained from using Intense Debate is worth the sacrifice of dealing with it. However, I hope they realize they have a long way to go to make their service developer friendly.

I’m a firm believer that Twitter has both a follow & tweet threshold which after crossed starts to diminish the effectiveness of the service. I believe it’s impossible for a user to adequately follow 300 plus Twitterers. If follows are posting a minimum of 4 tweets per day, that is over 1200 messages in one 24 hour period, far too many to create social dialog.

I smell fish anytime I see any Twitterer who is following 300+ users. Those individuals are likely “phishing for follows,” essentially following with the hopes to be followed. Arbitrarily, I believe a Twitterer starts to loose their ability to follow a community of users at around 150 follows, and it fully breaks down around 300 follows.

In just an informal survey of those I follow and respect, this number holds true.

@jasonfried – Following 55 / Followers 4643
@kevinrose – Following 122 / Followers 79,693
@randfish – Following 13 / Followers 3,213
@simplebits – Following 234 / Followers 9,781
@bfled – Following 172 / Followers 2,869
@copyblogger – Following 216 / Followers 9,532
@gruber – Following 252 / Followers 17,462
@davetaylor – Following 167 / Followers 3,656

While I’m having a hard time gathering numbers, I believe there is a certain number of Tweets which a follower will tolerate during the day. I’d love to see someone write an app to display the Tweets/Day on any user over a 30 day period. Anyone want to write that?

Speaking from my own personal experience if any of those I follow post more then 25 updates in one day, then I drop them like a bad habit. Not so much because I’m not interested but more to the fact that their constant updates begin to push down and out the others that I am following.

Regardless, I’m loving Twitter!

Over the past few weeks I’ve had a plethora of different reactions regarding Amazon’s new reading device, Kindle. Initially I felt that the Kindle was doomed. I figured there is no way that people would be willing to adhere to the strict DRM policy that’s been set in place by Amazon and the content publishers. However, the more I’ve thought about it, the more I think the Kindle might have a shot at being a great device. No, not because the device itself is a joy to use, but rather because it offers something we have never seen on the tech landscape before. Free high speed web access without a subscription cost.

Here’s the deal. The Kindle is incredibly important to the future of content distribution and discovery because it offers free 3g wireless internet (mobile EVDO) with the device. Free free — as in the online content isn’t restricted to just content from Amazon but rather it’s full fledge internet. Do you see what I’m saying? The Kindle is the first device in the history of tech devices that gives us the ability to browse the web practically anywhere in the country without having to pay.

Now picture this. An iPod Touch with free high speed internet anywhere in the nation. Check your mail, browse your blogs, download photos and music, all without having to pay a monthly cost. This is unthinkable, and something that we never saw coming from the big telco’s, yet all of a sudden the Kindle has broken the mold.

Yes the Kindle’s ugly, yes the user interface looks slow and frustrating, yes the screen is not paper-white, and yes the battery doesn’t last as long with internet on. But what I am saying is not that the Kindle is a great device, but that it is a great gateway device. The type of device that we need to be successful so we can use other better designed devices in the future.

I’ve noticed there is very little research out there discussing the appropriate time to post a blog entry or newsletter. I’ve noticed on several occasions that the timing of our blog entries and the timing of an email broadcast seem to have a huge effect on readership, open rates and overall impressions. (more…)

We just installed this WordPress blog on our servers and I must say, it is beautiful. Well implemented, easy to use, well documented. In my search for blogging software I thought I would find a few options for an ASP.NET package… I only found one, .TEXT at http://www.gotdotnet.com

Being an ASP.NET shop I was floored that there were not more options to select from. Why is that? I’m not trying to start a flame war with PHP, JSP and ASP.NET all of these languages have their merits and their flaws, but why hasn’t the ASP.NET community delivered some nice open source blogging software?