Extension:KeyCAPTCHA

KeyCAPTCHA is a visual CAPTCHA extension that relies on displaying a jigsaw puzzle graphic as either HTML5 or a Flash object. It detects which to use automatically.

The user must move the jigsaw puzzle pieces into position with the mouse to solve the CAPTCHA.

The extension depends on KeyCAPTCHA's server being available; it also requires the user enable JavaScript (and likely also Flash). It will render the new registration process less accessible (or utterly inaccessible) to users with "Lynx" style text browsers and to visually impaired users who rely on text-to-speech processors. Conversely, it renders the new user registration process far less accessible to spambots.

KeyCAPTCHA is a strict and effective Turing test but, unlike many other captchas, it does not require any text typing. Any text displayed as part of the KeyCAPTCHA graphic may be localised as one of twenty-eight languages worldwide.

MediaWiki 1.27+
The extension code supplied by https://www.keycaptcha.com/media/plugins/keycaptcha-for-mediawiki-116x-118x.zip contains a call to wfGetIP, a function which was deprecated in MediaWiki 1.19 and removed completely in MediaWiki 1.27.

This will break your KeyCaptcha installation in the current MediaWiki release. One possible solution is to add this stub function to LocalSettings.php:

There are also multiple message functions which are breaking due to MediaWiki changes; see Manual:Messages API.

(The stub functions are a kludge which would - or should - go away if and when KeyCaptcha updates the original extension to match the current MediaWiki environment. See also .)

Known bugs and issues
with simply:
 * The extension version https://www.keycaptcha.com/media/plugins/keycaptcha-for-mediawiki-116x-118x.zip calls an undefined method keyCaptcha::buildRegexes in ...extensions/local/keyCaptcha/keyCaptcha.php on line 69. As the extension is based on the ConfirmEdit code, which is distributed with MediaWiki, a buildRegexes definition should be available in MW sources (most likely /extensions/SpamBlacklist/buildRegexes/SpamRegexBatch.php). Another possible workaround is to replace:

Configuration options
Each domain may be configured to support charity funds by enabling social advertising in KeyCAPTCHA, to earn money by displaying commercial advertising, both or no advertising at all:
 * 1) Anti-spam protection. Social advertising. Monetization through commercial ads.
 * 2) Anti-spam protection. Monetization through commercial ads.
 * 3) Anti-spam protection. Social advertising.
 * 4) Anti-spam protection without any ads.

The branding of KeyCAPTCHA itself cannot be removed from the free version of the service; additional customisation is available in a paid version. All of these options (as well as language and topic of your website) are configured from KeyCAPTCHA's website on a per-domain basis.