desc_html:Configure hCaptcha integration, relying on third-party scripts. This may have security and privacy implications.
email-confirmation:
desc_html:Require new users to go through hCaptcha at the e-mail validation step. Bots will not be deterred from creating accounts, but they may be prevented from confirming them, leaving them to be automatically cleaned up after a couple days. This does not interfere with app-based registrations.
title:CAPTCHA on email validation
disabled:
desc_html:Do not require a CAPTCHA
title:Disabled
registration-form:
desc_html:Require new users to go through hCaptcha on the registration form, so that CAPTCHA requirement is immediately apparent to them. This disables app-based registrations and may prevent your instance from being listed as having open registrations.
desc_html:When federating toots, add this content warning to toots that do not have one. It is useful if your server is specialized in content other servers might want to have under a Content Warning. Media will also be marked as sensitive.