The service implements captcha to prevent bots and automated scripts from submitting forms and using other website resources, typically for the purpose of posting spam messages. Unlike services using distorted images, textCAPTCHA posts random, text-based questions, such as easy arithmetic problems or logic puzzles, which users must correctly solve to proceed. Bots unable to interpret the meaning of the text are prevented from continuing.
API methods support requests for questions and MD5 hashes of any permitted answers.
Showing posts with label safe browsing Api. Show all posts
Showing posts with label safe browsing Api. Show all posts
Thursday, January 12, 2012
Saturday, December 31, 2011
Google safe browsing API
Reminder: Safe Browsing version 1 API turning down December 1
In May Google announced that Google are ending support for the Safe Browsing protocol version 1 on December 1 in order to focus our resources on the new version 2 API and the lookup service. These new APIs provide simpler and more efficient access to the same data, and they use significantly less bandwidth. If you haven't yet migrated off of the version 1 API, Google encourage you to do so as soon as possible. Our earlier post contains links to documentation for the new protocol version and other resources to help you make the transition smoothly.
After December 1, Google will remove all data from the version 1 API list to ensure that any remaining clients do not have false positives in their database. After January 1, 2012, Google will turn off the version 1 service completely, and all requests will return a 404 error.
Thanks for your cooperation, and enjoy using the next generation of Safe Browsing.
In May Google announced that Google are ending support for the Safe Browsing protocol version 1 on December 1 in order to focus our resources on the new version 2 API and the lookup service. These new APIs provide simpler and more efficient access to the same data, and they use significantly less bandwidth. If you haven't yet migrated off of the version 1 API, Google encourage you to do so as soon as possible. Our earlier post contains links to documentation for the new protocol version and other resources to help you make the transition smoothly.
After December 1, Google will remove all data from the version 1 API list to ensure that any remaining clients do not have false positives in their database. After January 1, 2012, Google will turn off the version 1 service completely, and all requests will return a 404 error.
Thanks for your cooperation, and enjoy using the next generation of Safe Browsing.
Subscribe to:
Posts (Atom)