Last modified: 2014-08-08 15:32:15 UTC
Force to pass a captcha to create a page.
Created attachment 3269 [details] Add $wgCaptchaTriggers['create']
Hmm, couple things I notice: First, it doesn't show the captcha until after you submit. For the URL-based catcher and other specific triggers that's necessary because we don't know if the trigger is present until you submit, but it's kind of annoying for page creation maybe? Second, this will apply to talk pages as well as articles. Perhaps it would be good to be able to treat those separately.
Just my two cents. If the captcha image is displayed at first time, it will be show for all the time the user writes the text of the page, so a lot of time will pass from when the image is first displayed and when the code is submitted, Usaully captcha do not like that since the most time has passed the more is the probability that a computer can answer.
You're right, Brion. I didn't add anything really new, so it doesn't show first time it opens the "create", as it doesn't show when you use $wgCaptchaTriggers['edit'] I'm not sure what's the best system. Captcha appears between toolbar and edit text so it's not too friendly having it from the beginning. There are also 'edits' which don't want to do a submit (only read the source), wasting image bandwidth. On the other hand, it complicates things (not a problem for 8668) so showing it first time could be good. AnyFile, if the computer is able to solve it, it probably can solve it faster than any human. Separating ConfirmEdit config per namespace would be nice. What would be the best method? $wgCaptchaTriggers[namespace]['create']? $wgNamespaceProtection? $wgCaptchaNamespaceSkip?
ConfirmEdit configuration per namespace is accomplished on bug 9255.
Applied with bug 9255 on r20795.
Change 152906 had a related patch set uploaded by 01tonythomas: Removed the IMAP support from BounceHandler extension https://gerrit.wikimedia.org/r/152906
