aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJoey Hess <joey@kodama.kitenet.net>2008-06-20 19:43:48 -0400
committerJoey Hess <joey@kodama.kitenet.net>2008-06-20 19:43:48 -0400
commit8212d05d443f05c8ae63f6b8d4b2c784f4d96150 (patch)
tree639ed6a5d08d2869e629bec378b656843c48da69 /doc
parent1eb2110e0677404804af5bd65ade7de750d7d3f1 (diff)
downloadikiwiki-8212d05d443f05c8ae63f6b8d4b2c784f4d96150.tar
ikiwiki-8212d05d443f05c8ae63f6b8d4b2c784f4d96150.tar.gz
response
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/require_CAPTCHA_to_edit.mdwn6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/todo/require_CAPTCHA_to_edit.mdwn b/doc/todo/require_CAPTCHA_to_edit.mdwn
index ec70d2a83..61bacadc3 100644
--- a/doc/todo/require_CAPTCHA_to_edit.mdwn
+++ b/doc/todo/require_CAPTCHA_to_edit.mdwn
@@ -2,3 +2,9 @@ I don't necessarily trust all OpenID providers to stop bots. I note that ikiwik
I imagine a plugin that modifies the login screen to use <http://recaptcha.net/>. You would then be required to fill in the captcha as well as log in in the normal way.
+> I hate CAPTCHAs with a passion. Someone else is welcome to write such a
+> plugin.
+>
+> If spam via openid (which I have never ever seen yet) becomes
+> a problem, a provider whitelist/blacklist seems like a much nicer
+> solution than a CAPTCHA. --[[Joey]]