glitch-soc/app/views/auth/confirmations/captcha.html.haml

- content_for :page_title do
  = t('auth.confirm_captcha')

= form_tag auth_captcha_confirmation_url, method: 'POST', class: 'simple_form' do
  = hidden_field_tag :confirmation_token, params[:confirmation_token]

  .field-group
    = render_captcha

  .actions
    %button.button= t('challenge.continue')
Add ability to set hCaptcha either on registration form or on e-mail validation Upshot of CAPTCHA on e-mail validation is it does not need to break the in-band registration API. 2022-01-25 16:37:12 -05:00			`- content_for :page_title do`
			`= t('auth.confirm_captcha')`

			`= form_tag auth_captcha_confirmation_url, method: 'POST', class: 'simple_form' do`
			`= hidden_field_tag :confirmation_token, params[:confirmation_token]`

			`.field-group`
Change CAPTCHA handling to be only on email verification This simplifies the implementation considerably, and while not providing ideal UX, it's the most flexible approach. 2022-01-25 17:56:57 -05:00			`= render_captcha`
Add ability to set hCaptcha either on registration form or on e-mail validation Upshot of CAPTCHA on e-mail validation is it does not need to break the in-band registration API. 2022-01-25 16:37:12 -05:00
			`.actions`
			`%button.button= t('challenge.continue')`