a9269f8786
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.
26 lines
1.5 KiB
YAML
26 lines
1.5 KiB
YAML
---
|
|
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, may prevent your instance from being listed as having open registrations, 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
|