tootlab-mastodon/config/locales-glitch/en.yml

---
en:
  admin:
    settings:
      captcha_enabled:
        desc_html: Enable hCaptcha integration, requiring new users to solve a challenge when signing up. Note that this disables app-based registration, and requires third-party scripts from hCaptcha to be embedded in the registration pages. This may have security and privacy concerns.
        title: Require new users to go through a CAPTCHA to sign up
      enable_keybase:
        desc_html: Allow your users to prove their identity via keybase
        title: Enable keybase integration
      outgoing_spoilers:
        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.
        title: Content warning for outgoing toots
      hide_followers_count:
        desc_html: Do not show followers count on user profiles
        title: Hide followers count
      show_reblogs_in_public_timelines:
        desc_html: Show public boosts of public toots in local and public timelines.
        title: Show boosts in public timelines
      show_replies_in_public_timelines:
        desc_html: In addition to public self-replies (threads), show public replies in local and public timelines.
        title: Show replies in public timelines
  generic:
    use_this: Use this
  settings:
    flavours: Flavours
Move glitch-specific ruby-side locales to their own files 2020-05-29 18:06:02 -04:00			`---`
			`en:`
			`admin:`
			`settings:`
Add optional hCaptcha support Fixes #1649 This requires setting `HCAPTCHA_SECRET_KEY` and `HCAPTCHA_SITE_KEY`, then enabling the admin setting at `/admin/settings/edit#form_admin_settings_captcha_enabled` Subsequently, a hCaptcha widget will be displayed on `/about` and `/auth/sign_up` unless: - the user is already signed-up already - the user has used an invite link - the user has already solved the captcha (and registration failed for another reason) The Content-Security-Policy headers are altered automatically to allow the third-party hCaptcha scripts on `/about` and `/auth/sign_up` following the same rules as above. 2022-01-24 13:06:19 -05:00			`captcha_enabled:`
			`desc_html: Enable hCaptcha integration, requiring new users to solve a challenge when signing up. Note that this disables app-based registration, and requires third-party scripts from hCaptcha to be embedded in the registration pages. This may have security and privacy concerns.`
			`title: Require new users to go through a CAPTCHA to sign up`
Move glitch-specific ruby-side locales to their own files 2020-05-29 18:06:02 -04:00			`enable_keybase:`
			`desc_html: Allow your users to prove their identity via keybase`
			`title: Enable keybase integration`
Add support for setting Content Warning for CW-less outgoing toots 2020-05-30 10:47:17 -04:00			`outgoing_spoilers:`
			`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.`
			`title: Content warning for outgoing toots`
Move glitch-specific ruby-side locales to their own files 2020-05-29 18:06:02 -04:00			`hide_followers_count:`
			`desc_html: Do not show followers count on user profiles`
			`title: Hide followers count`
			`show_reblogs_in_public_timelines:`
			`desc_html: Show public boosts of public toots in local and public timelines.`
			`title: Show boosts in public timelines`
			`show_replies_in_public_timelines:`
			`desc_html: In addition to public self-replies (threads), show public replies in local and public timelines.`
			`title: Show replies in public timelines`
			`generic:`
			`use_this: Use this`
			`settings:`
			`flavours: Flavours`