Spam, APIs and Whitelisting
October 27th, 2005 | Published in Google Blogger Buzz
We've pushed some additional changes this week to make it more difficult for spam to be created using our API and other tools (this includes Hello/Picasa, Flickr, w.bloggar, ecto and many others).
The downside to the API changes is that those users whose blogs have been improperly classified as spammy have been unable to post outside of the blogger.com interface. For these users, we've pushed a change so that posts will be set to draft if created through the API. This way no content will be lost and users can go to blogger.com to solve the CAPTCHA and post their content.
We've also introduced a way for users who have been improperly classified to let us know that their blog is in need of manual review. More information on that can be found in the Help.
The downside to the API changes is that those users whose blogs have been improperly classified as spammy have been unable to post outside of the blogger.com interface. For these users, we've pushed a change so that posts will be set to draft if created through the API. This way no content will be lost and users can go to blogger.com to solve the CAPTCHA and post their content.
We've also introduced a way for users who have been improperly classified to let us know that their blog is in need of manual review. More information on that can be found in the Help.