mirrors
/
mastodon-glitch
mirror of https://github.com/glitch-soc/mastodon
3
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
mastodon-glitch/app/views/auth/confirmations/captcha.html.haml

15 lines
386 B
Plaintext
Raw Normal View History

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 21:37:12 +00:00
- content_for :page_title do
Add some explanation text on the CAPTCHA confirmation page
2022-01-26 12:24:51 +00:00
= t('auth.captcha_confirmation.title')
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 21:37:12 +00:00
= form_tag auth_captcha_confirmation_url, method: 'POST', class: 'simple_form' do
= hidden_field_tag :confirmation_token, params[:confirmation_token]
Add some explanation text on the CAPTCHA confirmation page
2022-01-26 12:24:51 +00:00
.field-group
%p.hint= t('auth.captcha_confirmation.hint_html')
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 21:37:12 +00:00
.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 22:56:57 +00: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 21:37:12 +00:00
.actions
%button.button= t('challenge.continue')