Change Details

## Summary WMF's hCaptcha instance is set up in 99.9% passive and invisible mode. But when an AbuseFilter defines `showcaptcha` as its consequence, it should display a challenge. ## Technical notes We may need a separate sitekey for this, and find a way to swap the sitekey in use when `showcaptcha` is used in AbuseFilter. Alternatively, perhaps we can find a way to reuse the existing sitekey, but create a rule in dashboard.hcaptcha.com to "Always challenge" ## Acceptance criteria - [ ] `showcaptcha` in AbuseFilter displays a challenge when hCaptcha is enabled

## Summary WMF's hCaptcha instance is set up in 99.9% passive and invisible mode. But when an AbuseFilter defines `showcaptcha` as its consequence, it should display a challenge. ## Technical notes We can use a separate sitekey for this, and find a way to swap the sitekey in use when `showcaptcha` is used in AbuseFilter. ## Acceptance criteria - [ ] `showcaptcha` in AbuseFilter always displays a challenge when hCaptcha is enabled

## Summary WMF's hCaptcha instance is set up in 99.9% passive and invisible mode. But when an AbuseFilter defines `showcaptcha` as its consequence, it should display a challenge. ## Technical notes We may needWe can use a separate sitekey for this, and find a way to swap the sitekey in use when `showcaptcha` is used in AbuseFilter. Alternatively, perhaps we can find a way to reuse the existing sitekey, but create a rule in dashboard.hcaptcha.com to "Always challenge" ## Acceptance criteria - [ ] `showcaptcha` in AbuseFilter always displays a challenge when hCaptcha is enabled