Fix this, please.

Thanks for the info.

Wrong. See the screenshot. It doesn’t work sometimes even after the information has been entered and the green check is showing.

Fix this, please.

The programmer side of me — that’s my business, BTW — says this is an inapproriate place to ask me for programming advice (is that what you are trying to do above or just kidding with the smiley?). If you’re serious then look me up on my programming business site directly where a programming solution could be seriously explored.

As for the user side of me …

The user side says this request is totally ill-advised. Scaling isn’t a user concern. Don’t do the program if you can’t figure out the backend scaling situation. Don’t come to the user and ask them to help you figure out how to make your program work. Backend design issues aren’t the user’s problem. Sorry if that’s blunt but that’s the way it is.

Users want solutions that work — period. Yours doesn’t in its current incarnation 100% or even 70% of the time. Heck, I’d say it’s a 50/50 proposition at best.

Here’s another problem. You fill out the cocomment form, everything is entered, get the green ok and then it won’t submit the comment: screenshot. Waste of time.

Sometimes I seriously wonder if the cocomments folks lab tested anything. I’m not the only one experiencing these issues and they seem like rather severe bugs to me. The whole point of your program is to make it easy to track comments which more often than not it is anything but that unless the blog owner edits their template? That’s a failed proposition, sorry.

Like I said in the last entry, this probably isn’t a road you want to continue going down if you truly don’t have any solutions. If/when you do, please return with an update.

This reply may come across as rude, but my intention is to tell you that I’m a frustrated cocomment user. I’ve been loyal up to this point and kept using your service but I’m seriously considering just deleting the bookmarklet and saying goodbye like others I know have already done.

I agree the pop-up should remember if you’ve already filled info for the same blog/post, I’ll see if that can be made to happen. The red X in itself isn’t really a problem, it’s an indication that coCo needs extra info to capture the comment.

If you have an unflawed design solution to work around the fact that comment markup varies greatly, and which will scale, do let us know

The red x problem is annoying to users and caused at least one person to say they switched away. And the problem wasn’t “momentary” it lasted for a couple days and there were threads on the cocomment forum with many other cocomment users complaining about the problem.

I see you took a job as an evangelist for cocomment? That’s good, but I wouldn’t advise trying to resuscitate threads like this one where cocomment is still broken unless there truly is a sensible solution and fix. Doesn’t seem to be one yet

Blog integration (the thing you do by adding stuff to your template) means that all comments by people *currently identified by coComment* (ie, logged in) will be recorded. As of now, coCo does not track comments by non-members.

To be able to capture a comment, coCo needs to be able to understand the comment form currently being used. As there are no standards out there for designing a comment form, coCo has had to “learn” the most popular comment forms out there. You get the little green check next to your name when coCo has happily managed to get all the data it needed from the comment form and page.

If some of the data is missing (usually because the blog itself isn’t marked up in a way that coCo understands) you get the little red cross. By clicking on the username and through this pop-up window you’re talking about, you can manually provide coCo with the missing information it needs.

As for why it worked fine and then stopped working, I can only guess that a change was made to how coCo interprets comments, and that it caused a momentary incompatibility with your blog.

Hope this clarifies things a little!