One prevention strategy is to require more checking at registration time. Though this puts more burden on the admins, the pace of new, legitimate registration on AFSLore is probably pretty low. Maybe a volunteer system to monitor new registrations as [[JeffreyHutzelman]] [suggested](https://lists.openafs.org/pipermail/openafs-info/2005-March/016813.html) would be a good idea.
-Deploying some kind of fuzzy GIF interpretation step during registration might also be helpful, but I don't know how hard it would be to find and deploy such a system.
+Deploying some kind of fuzzy GIF interpretation (sometimes termed a [captcha](http://en.wikipedia.org/wiki/Captcha)) step during registration might also be helpful, but I don't know how hard it would be to find and deploy such a system.
-We are certainly not alone in being victims of Wiki spam. One think I have not yet done is some research on what other sites and other Wikis are doing. Perhaps someone has already looked into this subject and could add a summary here?
+We are certainly not alone in being victims of Wiki spam. We need some information on what other sites and other Wikis are doing. Perhaps someone has already looked into this subject and could add more details here?
+
+Other relevant discussions:
+
+- [WikiSpam](http://twiki.org/cgi-bin/view/Codev/WikiSpam) on [TWiki.org](http://twiki.org/) has summary of information on this topic. It is particularly relevant since AFSLore runs on (old) TWiki software.
+-
-- [[TedAnderson]] - 27 Apr 2005
git://git.openafs.org / openafs-wiki.git / commitdiff