about summary refs log tree commit diff
path: root/config/locales-glitch/en.yml
AgeCommit message (Collapse)Author
2022-12-21Add links to glitch-soc's Crowdin (#2033)Claire
* Add link to glitch-soc's crowdin in app settings * Add mention of translations to CONTRIBUTING.md
2022-12-21Change i18n-tasks config to consider glitch-soc translation files (#2027)Claire
* Change i18n-tasks config to consider glitch-soc translation files * Normalize locales-glitch YML files * Consider upstream Rails translations as external * Add simple_form.glitch_only to ignore_unused * Remove unused keybase-related strings
2022-11-17Remove glitch-soc-specific translations of upstreamed feature (domain block ↵Claire
import)
2022-11-12Add back missing glitch-soc admin settings (#1919)Claire
Fixes #1890
2022-05-31Make “Flavour and skin” admin setting label translatable (#1791)Claire
2022-05-16Add confirmation page when importing blocked domains (#1773)Claire
* Move glitch-soc-specific strings to glitch-soc-specific locale files * Add confirmation page when importing blocked domains
2022-03-14Fix blank screen when trying to copy emoji with a too large file size (#1718)Claire
Fixes #1714
2022-02-26Add option (on by default) to allow toots with content warnings to trendClaire
2022-01-26Add link to /about/more to the CAPTCHA verification pageClaire
2022-01-26Add some explanation text on the CAPTCHA confirmation pageClaire
2022-01-26Add mention of accessibility issues to hCaptcha option in admin pageClaire
2022-01-25Change CAPTCHA handling to be only on email verificationClaire
This simplifies the implementation considerably, and while not providing ideal UX, it's the most flexible approach.
2022-01-25Add ability to set hCaptcha either on registration form or on e-mail validationClaire
Upshot of CAPTCHA on e-mail validation is it does not need to break the in-band registration API.
2022-01-25Disable `registrations` flag in /api/v1/instance when CAPTCHA is enabledClaire
This is to avoid apps trying and failing at using the registrations API, which does not let us require a CAPTCHA and cannot be clearly signaled as unavailable.
2022-01-24Add optional hCaptcha supportClaire
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.
2021-11-26Merge branch 'main' into glitch-soc/merge-upstreamClaire
Conflicts: - `.env.production.sample`: Copied upstream changes. - `app/controllers/settings/identity_proofs_controller.rb`: Minor conflict due to glitch-soc's extra “enable_keybase” setting. Upstream removed keybase support altogether, so did the same. - `app/controllers/well_known/keybase_proof_config_controller.rb`: Minor conflict due to glitch-soc's extra “enable_keybase” setting. Upstream removed keybase support altogether, so did the same. - `lib/mastodon/statuses_cli.rb`: Minor conflict due to an optimization that wasn't shared between the two versions. Copied upstream's version.
2020-05-30Add support for setting Content Warning for CW-less outgoing tootsThibaut Girka
2020-05-30Move glitch-specific ruby-side locales to their own filesThibaut Girka