Skip to main content

Posting At High Rates Results In Restrictions

For a long time, blog owners who would frequently publish many posts in one day would report the anguish of having to solve a CAPTCHA.
  • Blogger Help Why do I have word verification on my posting form? explains the necessity, and the limitation.
    This restriction is in place as much to control the load on our servers as to prevent explicit spam. Therefore, there is not a whitelisting review process to exempt individual blogs.

    If you use Post Editor to publish, and you post at high daily volumes, you'll discover this restriction.

    You may have to solve a CAPTCHA, each time that you publish, when you pass a certain (unstated) volume limit. The limit resets each day - though how the days start and end, based upon Blogger being a 24 hour a day product - and what clock you live by, this may be a source of confusion. Reliably, all that you can predict is that, if you start seeing a CAPTCHA based upon posting volume, you will have to wait some hours for the CAPTCHA to go away.

    Some time ago, enterprising spammers saw a way around the posting volume CAPTCHA, and started posting using email, through Mail-to-Blogger. Blogger found out about that, and imposed the CAPTCHA requirement on Mail-to-Blogger. That was a useless gesture, as it simply stopped high daily volume posting completely - since nobody using email saw the CAPTCHA.

    Recently, Blogger removed the CAPTCHA from Mail-to-Blogger publishing, and now saves posts, published at high volumes, as Drafts. If you are publishing posts using Mail-to-Blogger, and find that your posts aren't being published, look at your Edit Posts menu, and see if your posts are being saved as Drafts.

    If you see your posts being saved as Drafts, simply display Drafts, select all (or some) of the pending posts, and hit "Publish Selected". It's a simple compromise - 30 seconds of extra work, avoiding having to solve a CAPTCHA for each post, to publish as many posts en masse as you wish. I think that's a pretty good compromise.

    >> Top
  • Comments

    Lomba Apa Saja said…
    yap, after 50 posts we would need to fill captcha

    Popular posts from this blog

    Embedded Comments And Main Page View

    The option to display comments, embedded below the post, was made a blog option relatively recently. This was a long requested feature - and many bloggers added it to their blogs, as soon as the option was presented to us. Some blog owners like this feature so much, that they request it to be visible when the blog is opened, in main page view. I would like all comments, and the comment form, to be shown underneath the relevant post, automatically, for everyone to read without clicking on the number of comments link. And this is not how embedded comments work.

    What's The URL Of My Blog?

    We see the plea for help, periodically I need the URL of my blog, so I can give it to my friends. Help! Who's buried in Grant's Tomb, after all? No Chuck, be polite. OK, OK. The title of this blog is "The Real Blogger Status", and the title of this post is "What's The URL Of My Blog?".

    With Following, Anonymous Followers Can't Be Blocked

    As people become used to Blogger Following as just another tool to connect people, they start to think about the implications . And we see questions like How do I block someone who's been following my blog secretly? I couldn't see her in my Followers list (hence I couldn't use the "Block this user" link), but I have looked at her profile and could see that she's Following my blog. Following, when you look at the bottom line, is no more than a feed subscription and an icon (possibly) displayed on your blog, and linking back to the profile of the Follower in question. If someone Follows your blog anonymously, all that they get is a subscription to the blog feed. If you publish a feed from your blog, and if the feed is open to anybody (which, right now, is the case ), then it's open to everybody. If someone wants to use Following to subscribe to the feed, you can't stop this. You can't block it before, or after, the fact. You can't Block w