Good work experimenting to find out which word was causing you to be diverted to the Orble home page! I probably never would have even suspected that it was a word I’d entered into the comments box. (I’ve been assuming all this time that Orble’s software had just malfunctioned.) As I mention in one of my replies to your comments at WN, I was also diverted to the home page when I included the word “Javascript” in my reply to your comment. At first I was planning to use a variation of the word, as you had done to make your comments go through; but then I decided I just had to test it and see whether it would affect me, an Orble blogger, as well. And, of course, it did. Good detective work! Thanks to you, we now know it wasn’t a glitch after all.

I did mention the 42nd Estate blog post in my message to Orble, though not by name. Just linked to your post and mentioned the other post and its fascinating screenshot of an Orble CAPTCHA screen. I’m sure they’ll be curious enough to click the link in your post to check it out (at least I hope so).

At this point, I’m thinking maybe the problem I had on Wednesday was a glitch of some sort. But, the CAPTCHA system they’re using does need fixing. On two of the three comments I left tonight, I had to go through the CAPTCHA twice. If it happened once, I could believe that maybe I entered a letter wrong. But, I’m certain on the latest comment that I entered the correct letters the first time.

Just replied to your comment at Writer’s Notes, mentioning (in a postscript) that I sent Orble a link to your post. Hopefully that will provide some incentive for them to work on the problem.

Obviously something has gone wrong with Orble’s CAPTCHA since my friend facilitated the changes I mentioned–unless she, too, simply began reading and reproducing the text in the box below the CAPTCHA screen. Doesn’t look to me as if any letters are visible in that black, fuzzy screen either. (I’m using the Google Chrome browser.)

Glad, though, that you were finally able to leave a comment–or rather, two! Thanks for being persistent enough not to give up!

At first, I thought maybe it didn’t like my browser (Safari) so I tried another (Firefox). Same thing. Then, I went poking around and found that post.

…

Well, I just left a comment on your blog. It went through this time. But, the black CAPTCHA is still what shows. If there are letters in there, I’m pretty sure NO ONE could make them out. I mean, I’m not visually impaired and I’m usually pretty good at seeing even the tough ones, but I’m reasonably sure there aren’t any letters there at all. I had to type the letters it provided, which as that post I linked to mentioned, is somewhat counterproductive because spambots could be written to read that text and enter it.

Sorry to hear you had so much trouble attempting to leave a comment on my blog. Noticed your avatar in the MyBlogLog widget, so knew you’d visited and was a bit surprised you hadn’t commented. Now I know why. This has been an ongoing issue at Orble for quite some time. Needless to say, several other bloggers I know of (and I shudder to think how many I don’t know of) have also had trouble leaving comments there.

A while back, Orble made an improvement to its CAPTCHA, at my request, which made it a little easier for one of my blogging friends (who has visual difficulties) to read. So, now I’m wondering why, all of a sudden, it’s gotten to be a problem again. (And I’m really wondering about the black, fuzzy CAPTCHA screen shown in the blog post you’ve linked to, because I’ve never been told that Orble’s CAPTCHA was that bad!) Will definitely have to look into this!

Thanks for the heads up!
Jeanne

Mine is all zeros … all the time