Jon's dashboard

A comment on the question "Facebook Connect - Refresh URL of Post?" in IntenseDebate:

I think adding the script to the wordpress plugin is a good idea. I'll get that added in a future version.

I'll try to get an option for this up for you early next week. I understand why this messes with your pageviews and tracking. – Jon, on July 30, 2009 20:29

Jon replied on July 24, 2009 18:27 to the question "Facebook Connect - Refresh URL of Post?" in IntenseDebate:

I'm afraid I don't have a solid eta on when we'll have this ready as an option. I hope to have something available soon.

Jon replied on July 17, 2009 06:50 to the question "Facebook Connect - Refresh URL of Post?" in IntenseDebate:

This happens as a way to get around having to have every individual site using IntenseDebate and Facebook Connect install the xd_receiver script on their domain (since many IntenseDebate enabled sites can't install this script - for example, most Blogger users). Currently, we don't offer support for the xd_receiver script, but we could probably add it if you can add this file somewhere on your domain.

More info here: http://wiki.developers.facebook.com/i...

Hope this helps.

Jon replied on July 10, 2009 01:18 to the question "RPX OpenId integrate ID with existing accounts" in IntenseDebate:

If you want to map your local accounts to IntenseDebate accounts we offer a couple methods of auto-logging in IntenseDebate users after that synchronization is complete.

Another choice would be to include some extra JS to prepopulate the fields for name, email, and url and then dynamically replace the current UI with a "logged in" UI. They would not get all the benefits of full-fledged IntenseDebate users (reputation, comment history, etc), but it would prevent them from having to login or fill out the comment form. I can help get you started on this if you're interested.

Please let me know if either of these options might work and which is more interesting.

Jon replied on July 10, 2009 01:15 to the question "How do I retrieve the title and link to my comments?" in IntenseDebate:

The commentid for the link is currently the IntenseDebate commentid which is not synced back to your local WP database. We hope to support the old style of WP comment links with our own system in the future, but we unfortunately don't at this time.

Sorry for the trouble.

Jon replied on July 10, 2009 01:12 to the question "Comment counter is not showing. FireFox 2.0 and FireFox 3.0." in IntenseDebate:

Can you let me know what the url of your blog/site is so that I can take a look?

Sorry for the trouble.

Jon replied on July 10, 2009 01:10 to the question "Why are guest comments not saving but users logged in saving?" in IntenseDebate:

I think you might be having comments get caught in the spam filter. Are the comments you're referring to here: http://www.intensedebate.com/moderate...

Sorry for the trouble.

Jon replied on July 09, 2009 19:26 to the problem "Extra text posted when ReplyByEmail - "IntenseDebate Notification"" in IntenseDebate:

Can you give me an example comment or something where this is occurring?

It's possible that your mail client is adding some HTML in the message that is getting mangled and posted as part of the comment.

Thanks, and sorry for the trouble.

Jon replied on July 09, 2009 19:21 to the question "Top commenters widget not updating.." in IntenseDebate:

It's the top IntenseDebate users on your site (based on the # of comments they've left). If you're the only IntenseDebate user that has left a comment you'll be the only one on the list right now.

Hope this helps

Jon replied on July 09, 2009 19:16 to the question "Top commenters widget not updating.." in IntenseDebate:

Sorry to hear that. What's the url of your blog/site?

Jon replied on July 03, 2009 02:19 to the question "Comment counts inaccurate." in IntenseDebate:

Sorry to hear you're having trouble. In general, our system works best when the extra values (idcomments_post_id, idcomments_post_url, etc) are consistently used in both the javascript for the links and the javascript for the comment section itself. Currently you're setting these values for the links, but not the comment section.

Please try assigning these two values as well (the same way they're set in the corresponding link) and see if that resolves your issues.

var idcomments_post_id;
var idcomments_post_url;

Hope this helps!

Jon replied on June 19, 2009 19:29 to the problem "idcomments_post_id not working" in IntenseDebate:

That should only happen if you don't specify the post id for a post, but if it was not specified the very first time (When we created the post reference) we will not update that on future requests. This is mainly because other people could just as easily edit these values by putting the JS on their site as well...which would not be ideal.

If this is not the case, it's possible there is a bug somewhere. Is it happening consistently for all new posts? Or under any certain conditions you've noticed that might be helpful in hunting it down?

Jon replied on June 19, 2009 19:08 to the problem "idcomments_post_id not working" in IntenseDebate:

Not sure if this answers the problem or not, but I wanted to give you a little insight into how these values work in case it's useful. When a script makes a request we look at the values set (or revert to the url of the post for the url and id by default, the document title for the title) and try to find a post matching these values. If a post has the id supplied, we return that, if not, we check url - and a new post is only created if no matching posts can be found. So if a post exists with the url specified, but a new (unused) id, we'll still return the post with the matching url...this is intended to be a fail safe to keep from confusion around stale url's (if a new comment is posted on a post that the url has been changed for - but hasn't been changed in our system - we'll link to the old url and the content won't actually be there). So, you can use the post id to get the same comments across multiple posts with different urls, but if you attempt to use the same url for all these posts we'll match to the existing post before we'll register it as a new post in our system...even if they have different post ids.

Currently there isn't a nice way to systematically update the url we store with the posts, so I'm not sure we have a great solution if you choose to change the url the content goes with. In general, we don't encourage this as it makes it worse for indexing, searching, and existing direct links to the comments.

Sorry for any confusion, and I hope this helps explain these values and how they're used a little better. If this still doesn't resolve the issue please let me know.

Jon replied on June 18, 2009 22:55 to the question "Latest Comments Widget Broken" in IntenseDebate:

Can you elaborate a bit more about what specifically is broken?

Jon replied on June 18, 2009 22:53 to the problem "ID comment hook error visible only in search engine meta not on site" in IntenseDebate:

What's the url of your blog/website?

Jon replied on June 18, 2009 22:52 to the problem "intensedebate includes require 2 dns lookups" in IntenseDebate:

In some cases having multiple dns entries can actually give you a performance boost. The reason is that the browser will limit the number of parallel requests to a given subdomain. This is part of why CDN lookups often use randomly generated numbers/strings as part of the url...in order to help split the load up across several subdomains and load the contents quicker.

This is not the case for things that are in sequence though, which is what most of the requests you're referring to will be (specifically the JS) so I'll try to make sure we migrate to one common dns lookup for all of those requests.

Thanks for the suggestion!

Jon replied on June 18, 2009 22:49 to the question "XML Error Message: The string "--" is not permitted within comments" in IntenseDebate:

There's no excuse for not getting back to you sooner.

If you're still interested in using IntenseDebate would you mind sending your blogger template as an attachment to support@intensedebate.com?

Jon replied on June 18, 2009 22:44 to the question "wordpress multiple comments one page idc-container" in IntenseDebate:

Currently we don't allow more than one instance of the IntenseDebate comment system on a single page at any given time. You can use our comment links to have a link to each comment section, and then configure the links ot load in teh comments using AJAX (so that no page refresh is required), but we don't offer a way to have multiple comment sections at the same time on the same page.

Sorry for the trouble.

Jon replied on June 18, 2009 22:42 to the problem "Need help getting IntenseDebate to work with RapidWeaver site" in IntenseDebate:

You'll probably see better results if you set the extra JS variables. In the JS you added you'll see this:
var idcomments_acct = 'e10878cf5ec6e26cb36c8358f2fe6c3b';
var idcomments_post_id;
var idcomments_post_url;

Just change it to this:
var idcomments_acct = 'e10878cf5ec6e26cb36c8358f2fe6c3b';
var idcomments_post_id = 'POST_ID';
var idcomments_post_url = 'POST_URL';

Where POST_ID is some unique identifier for the post (url, internal postid, etc) and the POST_URL is the permalink url of the post. That should help w/ the comments not showing up in the right places and / or not showing up at all.

As for the problem with only one instance of the comments on the index page, currently we only allow one instance of the comment section be loaded on a given page at a time. We offer comment links for displaying a link to the comment content when there are multiple posts on the page at once. You can also configure these links to load in the comments via AJAX so that the user need not refresh the page to see the comments. You can find this JS if you go to the re-installation links in the blog tools page in your IntenseDebate.com administration panel for the blog/website.

Hope this helps.

Jon replied on June 18, 2009 22:37 to the question "4294967295 replies" in IntenseDebate:

Yes, clearly this was a bug. We had an issue a while back where our reply counts were getting off due to a bug in the way it was calculated.

We're working on retroactively correcting the issue for previously affected comments, but comments going forward should be fine.

Sorry for the trouble.