aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhttps://id.koumbit.net/anarcat <https://id.koumbit.net/anarcat@web>2015-05-25 13:26:03 -0400
committeradmin <admin@branchable.com>2015-05-25 13:26:03 -0400
commit599e16aef2cf3f16b26cc8c44c233bc8031bc4d9 (patch)
tree091922926031991bb22659acf1b73c272696467a
parent6dfba9b72eab3c1a6e27b6d267d35925f31e11ad (diff)
downloadikiwiki-599e16aef2cf3f16b26cc8c44c233bc8031bc4d9.tar
ikiwiki-599e16aef2cf3f16b26cc8c44c233bc8031bc4d9.tar.gz
openid spam happens, as it turns out
-rw-r--r--doc/todo/require_CAPTCHA_to_edit.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/todo/require_CAPTCHA_to_edit.mdwn b/doc/todo/require_CAPTCHA_to_edit.mdwn
index 83ba07eb0..ad38d9235 100644
--- a/doc/todo/require_CAPTCHA_to_edit.mdwn
+++ b/doc/todo/require_CAPTCHA_to_edit.mdwn
@@ -38,6 +38,8 @@ I imagine a plugin that modifies the login screen to use <http://recaptcha.net/>
>>>> it means that someone else is taking care of keeping it ahead of
>>>> the bot authors.
+>> As [[spam_fighting]] shows, OpenID spam is now real. Yahoo, at least, would need to be blocked, according to the above, which seems like a bold move. --[[anarcat]]
+
Okie - I have a first pass of this. There are still some issues.
Currently the code verifies the CAPTCHA. If you get it right then you're fine.