Ryan Gibbons wrote:
Well I got a burst of un-laziness :) And it doesn't require any type of account on the wiki to edit. Also it doesn't require any type of captcha to submit an edit.Do any combination of those would help. I have seen some require captcha's for known account people, and then if they have an account they don't have to answer the captcha.Ryan Gibbons wrote:Sorry I am being a bit lazy as I could probably check this, but here are a few things that might help.Require an account on the wiki, and then require the account either 1) be authenticated via e-mail, or 2) it has to be approved by an adminYou could also use some sort of captcha, I think those math ones work pretty well. You just have to do some single digit match, easy for a computer to do, but most engines expect the pictures.
I'll go the captcha route if I have to....In the meantime I'd reconfigured it to require a valid login for editing/creating pages. I'm going to look at the confirming of email addresses after lunch. Thanks for the suggestions. It's like anything else, it's a catch-22. Make it too secure and it's not easily usable. Too usable, and it's not secure. Hard to find the happy median.
smime.p7s
Description: S/MIME Cryptographic Signature
