Home > BlogTech > TypeKey Buggy

TypeKey Buggy

October 5th, 2005

I am turning off TypeKey on this blog for the time being. It is so screwed up that the TypeKey cookie expires after only a few minutes. Even when trying to comment on my own blog, if I don’t type and save my own comments within a few minutes after logging on to TypeKey, I get shut out. Completely. Not only will my comment not be accepted, but even if I log out and try a normal comment, it will not register. Even if I open another browser and try an anonymous comment, the comment will not register. Even if I go to a different computer and try, the comment will not register. Somehow, because I did not click the “post” button on the comment within three minutes of logging into TypeKey, the damned system actually locked my own IP address out of my own blog comment system. But only for the post I tried to comment on. How completely screwed up is that?

Furthermore, it performs this way in an even more bizarre fashion. After attempting to comment, the “thank you” message appears, and says that my comment is in the registration queue. But the comment does not appear there, does not generate an email, and apparently just completely vanishes. And no matter what I try, the state persists for hours. This problem has been bugging me for a few months now, but today it elevated to new heights of absurdity. I am ready to trash the whole system and just have unregistered comments from everyone, to be moderated equally. Sorry, but I refuse to use a system that locks me out of commenting on my own blog.

Categories: BlogTech Tags: by
  1. ykw
    October 6th, 2005 at 03:29 | #1

    I think there are 2 kinds of cookies. Session cookies that stay alive for as long as your browser has at least one open window (I think), and persistent cookies that are stored on disk. Some security software blocks the long term cookies. Some people don’t like long term cookies on their computer and disable that feature. The programmer may be using session cookies since they are more stable than the persistent treats. It would be best for the programmer to code for both, and revert to session cookies if the others are blocked.

  2. Luis
    October 6th, 2005 at 04:30 | #2

    Tell it to TypeKey. I’ve complained, and the guy in charge even admitted to having problems, but not a peep since.

    However, it’s more than just the cookies. As I said, the problem persisted even with different browsers and even a different computer. Somehow, when the first cookie expired after three minutes, the system banned my IP address! That’s just bad programmming, if you ask me.

    Even now, 5 hours after my first attempt to post, and even though I can comment here and in other posts, TypeKey still destroys any attempt I make to comment in the original post. Damned frustrating. I’ve had it with that.

  3. ykw
    October 7th, 2005 at 03:40 | #3

    Perhaps their servers are overloaded and are not responding to the requests for info in a timely manner.

  4. Luis
    October 7th, 2005 at 12:22 | #4

    It turns out that Typekey and a certain anti-spam plug-in were interacting, but the Typekey bug was still the biggest culprit here. If a session times out, it not only blocks me from posting registered comments, but from posting any comments at all. Even if I switch to a different computer but use the same user name. Obviously it’s doing some kind filtering and blocking. And even if that’s a cross-bug with a spam filter, I’m afraid that the spam filter is more important to me.

Comments are closed.