Changeset 1116967
- Timestamp:
- 03/20/2015 03:48:47 PM (11 years ago)
- File:
-
- 1 edited
-
wp-recaptcha-bp/trunk/readme.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
wp-recaptcha-bp/trunk/readme.txt
r1116958 r1116967 130 130 CAPTCHAs offer great protection against abuse from automated programs. While it might be the case that some spammers have started using porn sites to attack CAPTCHAs (although there is no recorded evidence of this), the amount of damage this can inflict is tiny (so tiny that we haven't even seen this happen!). Whereas it is trivial to write a bot that abuses an unprotected site millions of times a day, redirecting CAPTCHAs to be solved by humans viewing pornography would only allow spammers to abuse systems a few thousand times per day. The economics of this attack just don't add up: every time a porn site shows a CAPTCHA before a porn image, they risk losing a customer to another site that doesn't do this. 131 131 132 == Upgrade Notice == 133 134 = 4.1 = 135 Just dumb text to force wp.org update the fixes to the readme. No change to the 136 code 137 132 138 == Screenshots == 133 139
Note: See TracChangeset
for help on using the changeset viewer.