An unconscionable situation: Month old product flaw still not fixed?

Nice ... I had filled out an entire problem report here ... a window popped up saying that it was similar to another problem and had been fixed. I reviewed that solution but 100 percent dispute its veracity. I try to come back and THIS system removed my entire comment.

I hate to sound snarky but frankly this is bullshit. The fact that after more than a month you guys have yet to fix this INCREDIBLY SERIOUS problem is unconscionable. I totally get that is early stage technology but for you to have released a product that is so utterly flawed in a critical area that you have yet to address is something about which you should be horrified.

So here's the problem. Several weeks ago the failure of ECHO utterly destroyed a vibrant comment thread for a post I wrote on Brian Solis' blog (www.briansolis.com) ... the problem was this:

The system would not let me log in to comment on posts ... it would just hang up "processing" ... I did everything you asked - restarting browser, reloading page, shutting down computer and restarting, logging out of the various connections ... no luck.

The result - the conversation was halted.

NOW YOUR SYSTEM IS DOING IT AGAIN!

The post in question is entitled "The reports of newspapers’ death are (perhaps) greatly exaggerated" ... It is also at www.briansolis.com.

This morning I was able to reply to ONE comment by logging in using Facebook.

When I went to reply to another comment, I thought I would try using another of my accounts. I logged out of the Facebook connection and then tried logging in using Twitter - THE SAME PROBLEM FROM BEFORE HAPPENED AGAIN.

I logged in and then the little spinny wheel thing just kept turning and it said "transferring data from JS-Kit" ... and hung up there. I logged out, I reloaded the page, I restarted my browser and tried again.

No luck.

I tried logging in with my Google account.

Same problem.

And then I went back to the Facebook connection and tried logging in. Now THAT won't work either.

This comment thread isn't nearly as interactive as the one that JS-Kit destroyed before ... but already the threat of my losing the ability to continue the conversation is starting.

Please fix this.

At this point I am inclined to strongly recommend that Brian replace his comment system.