You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

1429 lines
68 KiB

8 years ago
7 years ago
New Crowdin updates (#14197) * New translations devise.en.yml (Uyghur) [ci skip] * New translations doorkeeper.en.yml (Uyghur) [ci skip] * New translations en.json (Sorani (Kurdish)) [ci skip] * New translations en.yml (Sorani (Kurdish)) [ci skip] * New translations simple_form.en.yml (Sorani (Kurdish)) [ci skip] * New translations activerecord.en.yml (Sorani (Kurdish)) [ci skip] * New translations devise.en.yml (Sorani (Kurdish)) [ci skip] * New translations doorkeeper.en.yml (Sorani (Kurdish)) [ci skip] * New translations en.json (Kabyle) [ci skip] * New translations en.json (Chinese Traditional, Hong Kong) [ci skip] * New translations en.yml (Chinese Simplified) [ci skip] * New translations simple_form.en.yml (Chinese Simplified) [ci skip] * New translations en.yml (Chinese Simplified) [ci skip] * New translations en.json (Kabyle) [ci skip] * New translations en.json (Hebrew) [ci skip] * New translations en.json (Hebrew) [ci skip] * New translations en.json (Hebrew) [ci skip] * New translations en.json (Hebrew) [ci skip] * New translations en.json (Russian) [ci skip] * New translations en.yml (Persian) [ci skip] * New translations en.json (Persian) [ci skip] * New translations en.json (Croatian) [ci skip] * New translations en.json (Marathi) [ci skip] * New translations en.json (Norwegian Nynorsk) [ci skip] * New translations en.json (Bengali) [ci skip] * New translations en.json (Spanish, Argentina) [ci skip] * New translations en.json (Hindi) [ci skip] * New translations en.json (Latvian) [ci skip] * New translations en.json (Estonian) [ci skip] * New translations en.json (Kazakh) [ci skip] * New translations en.json (Galician) [ci skip] * New translations en.json (Vietnamese) [ci skip] * New translations en.json (Urdu (Pakistan)) [ci skip] * New translations en.json (Chinese Traditional) [ci skip] * New translations en.json (Icelandic) [ci skip] * New translations en.json (Tamil) [ci skip] * New translations en.json (Persian) [ci skip] * New translations en.json (Indonesian) [ci skip] * New translations en.json (Portuguese, Brazilian) [ci skip] * New translations en.json (Ido) [ci skip] * New translations en.json (Kabyle) [ci skip] * New translations en.json (Corsican) [ci skip] * New translations en.json (Serbian (Latin)) [ci skip] * New translations en.json (Uyghur) [ci skip] * New translations en.json (Sorani (Kurdish)) [ci skip] * New translations en.json (Taigi) [ci skip] * New translations en.json (Silesian) [ci skip] * New translations en.json (Malay) [ci skip] * New translations en.json (Welsh) [ci skip] * New translations en.json (Esperanto) [ci skip] * New translations en.json (Telugu) [ci skip] * New translations en.json (Chinese Traditional, Hong Kong) [ci skip] * New translations en.json (Asturian) [ci skip] * New translations en.json (Kannada) [ci skip] * New translations en.json (Breton) [ci skip] * New translations en.json (Malayalam) [ci skip] * New translations en.json (Catalan) [ci skip] * New translations en.json (Bulgarian) [ci skip] * New translations en.json (Arabic) [ci skip] * New translations en.json (Spanish) [ci skip] * New translations en.json (Czech) [ci skip] * New translations en.json (Greek) [ci skip] * New translations en.json (Basque) [ci skip] * New translations en.json (Danish) [ci skip] * New translations en.json (German) [ci skip] * New translations en.json (Finnish) [ci skip] * New translations en.json (Thai) [ci skip] * New translations en.json (Slovenian) [ci skip] * New translations en.json (Sardinian) [ci skip] * New translations en.json (Romanian) [ci skip] * New translations en.json (Occitan) [ci skip] * New translations en.json (Chinese Simplified) [ci skip] * New translations en.json (Ukrainian) [ci skip] * New translations en.json (French) [ci skip] * New translations en.json (Hungarian) [ci skip] * New translations en.json (Slovak) [ci skip] * New translations en.json (Russian) [ci skip] * New translations en.json (Portuguese) [ci skip] * New translations en.json (Polish) [ci skip] * New translations en.json (Norwegian) [ci skip] * New translations en.json (Turkish) [ci skip] * New translations en.json (Swedish) [ci skip] * New translations en.json (Serbian (Cyrillic)) [ci skip] * New translations en.json (Albanian) [ci skip] * New translations en.json (Italian) [ci skip] * New translations en.json (Armenian) [ci skip] * New translations en.json (Hebrew) [ci skip] * New translations en.json (Japanese) [ci skip] * New translations en.json (Dutch) [ci skip] * New translations en.json (Macedonian) [ci skip] * New translations en.json (Lithuanian) [ci skip] * New translations en.json (Georgian) [ci skip] * New translations en.json (Korean) [ci skip] * New translations en.json (Portuguese) [ci skip] * New translations en.json (Spanish) [ci skip] * New translations en.json (Korean) [ci skip] * New translations en.json (German) [ci skip] * New translations en.json (Japanese) [ci skip] * New translations en.json (Russian) [ci skip] * New translations en.json (French) [ci skip] * New translations en.json (Vietnamese) [ci skip] * New translations en.json (Catalan) [ci skip] * New translations en.json (Galician) [ci skip] * New translations en.json (Kabyle) [ci skip] * New translations en.json (Kabyle) [ci skip] * New translations en.json (Kabyle) [ci skip] * New translations en.json (Kabyle) [ci skip] * New translations en.json (Spanish, Argentina) [ci skip] * New translations en.json (Hungarian) [ci skip] * New translations en.json (Albanian) [ci skip] * New translations en.json (Corsican) [ci skip] * New translations simple_form.en.yml (Dutch) [ci skip] * New translations simple_form.en.yml (Dutch) [ci skip] * New translations en.json (Dutch) [ci skip] * New translations en.json (Dutch) [ci skip] * New translations en.json (Dutch) [ci skip] * New translations en.json (Dutch) [ci skip] * New translations en.json (Dutch) [ci skip] * New translations en.yml (Dutch) [ci skip] * New translations en.yml (Dutch) [ci skip] * New translations en.yml (Dutch) [ci skip] * New translations en.yml (Dutch) [ci skip] * New translations en.json (Thai) [ci skip] * New translations en.yml (Thai) [ci skip] * New translations en.yml (Dutch) [ci skip] * New translations en.yml (Dutch) [ci skip] * New translations en.yml (Dutch) [ci skip] * New translations en.yml (Dutch) [ci skip] * New translations en.yml (Dutch) [ci skip] * New translations en.json (Portuguese, Brazilian) [ci skip] * New translations en.json (Occitan) [ci skip] * New translations en.json (Occitan) [ci skip] * New translations en.yml (Occitan) [ci skip] * New translations en.json (Italian) [ci skip] * New translations en.json (Persian) [ci skip] * New translations en.json (French) [ci skip] * New translations en.yml (French) [ci skip] * New translations en.json (Arabic) [ci skip] * New translations en.json (Kabyle) [ci skip] * New translations en.json (Kabyle) [ci skip] * New translations en.yml (Kabyle) [ci skip] * New translations en.json (Icelandic) [ci skip] * New translations en.json (Portuguese, Brazilian) [ci skip] * New translations en.json (Indonesian) [ci skip] * New translations en.json (Persian) [ci skip] * New translations en.json (Galician) [ci skip] * New translations en.json (Tamil) [ci skip] * New translations en.json (Spanish, Argentina) [ci skip] * New translations en.json (Bengali) [ci skip] * New translations en.json (Marathi) [ci skip] * New translations en.json (Albanian) [ci skip] * New translations en.json (Serbian (Cyrillic)) [ci skip] * New translations en.json (Swedish) [ci skip] * New translations en.json (Turkish) [ci skip] * New translations en.json (Chinese Traditional) [ci skip] * New translations en.json (Urdu (Pakistan)) [ci skip] * New translations en.json (Vietnamese) [ci skip] * New translations en.json (Welsh) [ci skip] * New translations en.json (Esperanto) [ci skip] * New translations en.json (Chinese Traditional, Hong Kong) [ci skip] * New translations en.json (Malayalam) [ci skip] * New translations en.json (Telugu) [ci skip] * New translations en.json (Breton) [ci skip] * New translations en.json (Kannada) [ci skip] * New translations en.json (Uyghur) [ci skip] * New translations en.json (Croatian) [ci skip] * New translations en.json (Norwegian Nynorsk) [ci skip] * New translations en.json (Kazakh) [ci skip] * New translations en.json (Estonian) [ci skip] * New translations en.json (Latvian) [ci skip] * New translations en.json (Hindi) [ci skip] * New translations en.json (Malay) [ci skip] * New translations en.json (Spanish) [ci skip] * New translations en.json (Arabic) [ci skip] * New translations en.json (Bulgarian) [ci skip] * New translations en.json (Catalan) [ci skip] * New translations en.json (Czech) [ci skip] * New translations en.json (Danish) [ci skip] * New translations en.json (German) [ci skip] * New translations en.json (Greek) [ci skip] * New translations en.json (Romanian) [ci skip] * New translations en.json (Slovenian) [ci skip] * New translations en.json (Thai) [ci skip] * New translations en.json (Chinese Simplified) [ci skip] * New translations en.json (Slovak) [ci skip] * New translations en.json (Hungarian) [ci skip] * New translations en.json (French) [ci skip] * New translations en.json (Ukrainian) [ci skip] * New translations en.json (Norwegian) [ci skip] * New translations en.json (Lithuanian) [ci skip] * New translations en.json (Macedonian) [ci skip] * New translations en.json (Dutch) [ci skip] * New translations en.json (Polish) [ci skip] * New translations en.json (Basque) [ci skip] * New translations en.json (Portuguese) [ci skip] * New translations en.json (Russian) [ci skip] * New translations en.json (Armenian) [ci skip] * New translations en.json (Korean) [ci skip] * New translations en.json (Finnish) [ci skip] * New translations en.json (Hebrew) [ci skip] * New translations en.json (Georgian) [ci skip] * New translations en.json (Japanese) [ci skip] * New translations en.json (Italian) [ci skip] * New translations en.json (Ido) [ci skip] * New translations en.json (Taigi) [ci skip] * New translations en.json (Silesian) [ci skip] * New translations en.json (Sardinian) [ci skip] * New translations en.json (Occitan) [ci skip] * New translations en.json (Sorani (Kurdish)) [ci skip] * New translations en.json (Asturian) [ci skip] * New translations en.json (Kabyle) [ci skip] * New translations en.json (Serbian (Latin)) [ci skip] * New translations en.json (Corsican) [ci skip] * New translations en.json (Korean) [ci skip] * New translations en.json (Russian) [ci skip] * New translations en.json (Korean) [ci skip] * New translations en.json (Russian) [ci skip] * New translations en.json (Spanish) [ci skip] * New translations en.json (Korean) [ci skip] * New translations en.json (Portuguese) [ci skip] * New translations en.json (Portuguese) [ci skip] * New translations en.json (German) [ci skip] * New translations en.json (French) [ci skip] * New translations en.json (Korean) [ci skip] * New translations en.json (French) [ci skip] * New translations en.json (Esperanto) [ci skip] * New translations en.yml (Esperanto) [ci skip] * New translations en.json (Esperanto) [ci skip] * New translations en.json (Japanese) [ci skip] * New translations en.json (Vietnamese) [ci skip] * New translations en.json (Japanese) [ci skip] * New translations en.json (Spanish) [ci skip] * New translations en.json (Italian) [ci skip] * New translations en.json (Italian) [ci skip] * New translations en.json (Corsican) [ci skip] * New translations en.json (Corsican) [ci skip] * New translations en.json (Persian) [ci skip] * New translations en.json (Hungarian) [ci skip] * New translations en.json (Portuguese, Brazilian) [ci skip] * New translations en.json (Spanish) [ci skip] * New translations en.json (French) [ci skip] * New translations en.json (Spanish, Argentina) [ci skip] * New translations en.json (Galician) [ci skip] * New translations en.json (Galician) [ci skip] * New translations en.json (Portuguese) [ci skip] * New translations en.json (Portuguese) [ci skip] * New translations en.json (Albanian) [ci skip] * i18n-tasks normalize * yarn manage:translations
3 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
3 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
3 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
3 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
3 years ago
Add Keybase integration (#10297) * create account_identity_proofs table * add endpoint for keybase to check local proofs * add async task to update validity and liveness of proofs from keybase * first pass keybase proof CRUD * second pass keybase proof creation * clean up proof list and add badges * add avatar url to keybase api * Always highlight the “Identity Proofs” navigation item when interacting with proofs. * Update translations. * Add profile URL. * Reorder proofs. * Add proofs to bio. * Update settings/identity_proofs front-end. * Use `link_to`. * Only encode query params if they exist. URLs without params had a trailing `?`. * Only show live proofs. * change valid to active in proof list and update liveness before displaying * minor fixes * add keybase config at well-known path * extremely naive feature flagging off the identity proof UI * fixes for rubocop * make identity proofs page resilient to potential keybase issues * normalize i18n * tweaks for brakeman * remove two unused translations * cleanup and add more localizations * make keybase_contacts an admin setting * fix ExternalProofService my_domain * use Addressable::URI in identity proofs * use active model serializer for keybase proof config * more cleanup of keybase proof config * rename proof is_valid and is_live to proof_valid and proof_live * cleanup * assorted tweaks for more robust communication with keybase * Clean up * Small fixes * Display verified identity identically to verified links * Clean up unused CSS * Add caching for Keybase avatar URLs * Remove keybase_contacts setting
5 years ago
Add Keybase integration (#10297) * create account_identity_proofs table * add endpoint for keybase to check local proofs * add async task to update validity and liveness of proofs from keybase * first pass keybase proof CRUD * second pass keybase proof creation * clean up proof list and add badges * add avatar url to keybase api * Always highlight the “Identity Proofs” navigation item when interacting with proofs. * Update translations. * Add profile URL. * Reorder proofs. * Add proofs to bio. * Update settings/identity_proofs front-end. * Use `link_to`. * Only encode query params if they exist. URLs without params had a trailing `?`. * Only show live proofs. * change valid to active in proof list and update liveness before displaying * minor fixes * add keybase config at well-known path * extremely naive feature flagging off the identity proof UI * fixes for rubocop * make identity proofs page resilient to potential keybase issues * normalize i18n * tweaks for brakeman * remove two unused translations * cleanup and add more localizations * make keybase_contacts an admin setting * fix ExternalProofService my_domain * use Addressable::URI in identity proofs * use active model serializer for keybase proof config * more cleanup of keybase proof config * rename proof is_valid and is_live to proof_valid and proof_live * cleanup * assorted tweaks for more robust communication with keybase * Clean up * Small fixes * Display verified identity identically to verified links * Clean up unused CSS * Add caching for Keybase avatar URLs * Remove keybase_contacts setting
5 years ago
Add Keybase integration (#10297) * create account_identity_proofs table * add endpoint for keybase to check local proofs * add async task to update validity and liveness of proofs from keybase * first pass keybase proof CRUD * second pass keybase proof creation * clean up proof list and add badges * add avatar url to keybase api * Always highlight the “Identity Proofs” navigation item when interacting with proofs. * Update translations. * Add profile URL. * Reorder proofs. * Add proofs to bio. * Update settings/identity_proofs front-end. * Use `link_to`. * Only encode query params if they exist. URLs without params had a trailing `?`. * Only show live proofs. * change valid to active in proof list and update liveness before displaying * minor fixes * add keybase config at well-known path * extremely naive feature flagging off the identity proof UI * fixes for rubocop * make identity proofs page resilient to potential keybase issues * normalize i18n * tweaks for brakeman * remove two unused translations * cleanup and add more localizations * make keybase_contacts an admin setting * fix ExternalProofService my_domain * use Addressable::URI in identity proofs * use active model serializer for keybase proof config * more cleanup of keybase proof config * rename proof is_valid and is_live to proof_valid and proof_live * cleanup * assorted tweaks for more robust communication with keybase * Clean up * Small fixes * Display verified identity identically to verified links * Clean up unused CSS * Add caching for Keybase avatar URLs * Remove keybase_contacts setting
5 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
3 years ago
Add Keybase integration (#10297) * create account_identity_proofs table * add endpoint for keybase to check local proofs * add async task to update validity and liveness of proofs from keybase * first pass keybase proof CRUD * second pass keybase proof creation * clean up proof list and add badges * add avatar url to keybase api * Always highlight the “Identity Proofs” navigation item when interacting with proofs. * Update translations. * Add profile URL. * Reorder proofs. * Add proofs to bio. * Update settings/identity_proofs front-end. * Use `link_to`. * Only encode query params if they exist. URLs without params had a trailing `?`. * Only show live proofs. * change valid to active in proof list and update liveness before displaying * minor fixes * add keybase config at well-known path * extremely naive feature flagging off the identity proof UI * fixes for rubocop * make identity proofs page resilient to potential keybase issues * normalize i18n * tweaks for brakeman * remove two unused translations * cleanup and add more localizations * make keybase_contacts an admin setting * fix ExternalProofService my_domain * use Addressable::URI in identity proofs * use active model serializer for keybase proof config * more cleanup of keybase proof config * rename proof is_valid and is_live to proof_valid and proof_live * cleanup * assorted tweaks for more robust communication with keybase * Clean up * Small fixes * Display verified identity identically to verified links * Clean up unused CSS * Add caching for Keybase avatar URLs * Remove keybase_contacts setting
5 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
3 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
3 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
3 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
3 years ago
Add WebAuthn as an alternative 2FA method (#14466) * feat: add possibility of adding WebAuthn security keys to use as 2FA This adds a basic UI for enabling WebAuthn 2FA. We did a little refactor to the Settings page for editing the 2FA methods – now it will list the methods that are available to the user (TOTP and WebAuthn) and from there they'll be able to add or remove any of them. Also, it's worth mentioning that for enabling WebAuthn it's required to have TOTP enabled, so the first time that you go to the 2FA Settings page, you'll be asked to set it up. This work was inspired by the one donde by Github in their platform, and despite it could be approached in different ways, we decided to go with this one given that we feel that this gives a great UX. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add request for WebAuthn as second factor at login if enabled This commits adds the feature for using WebAuthn as a second factor for login when enabled. If users have WebAuthn enabled, now a page requesting for the use of a WebAuthn credential for log in will appear, although a link redirecting to the old page for logging in using a two-factor code will also be present. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: add possibility of deleting WebAuthn Credentials Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: disable WebAuthn when an Admin disables 2FA for a user Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * feat: remove ability to disable TOTP leaving only WebAuthn as 2FA Following examples form other platforms like Github, we decided to make Webauthn 2FA secondary to 2FA with TOTP, so that we removed the possibility of removing TOTP authentication only, leaving users with just WEbAuthn as 2FA. Instead, users will have to click on 'Disable 2FA' in order to remove second factor auth. The reason for WebAuthn being secondary to TOPT is that in that way, users will still be able to log in using their code from their phone's application if they don't have their security keys with them – or maybe even lost them. * We had to change a little the flow for setting up TOTP, given that now it's possible to setting up again if you already had TOTP, in order to let users modify their authenticator app – given that now it's not possible for them to disable TOTP and set it up again with another authenticator app. So, basically, now instead of storing the new `otp_secret` in the user, we store it in the session until the process of set up is finished. This was because, as it was before, when users clicked on 'Edit' in the new two-factor methods lists page, but then went back without finishing the flow, their `otp_secret` had been changed therefore invalidating their previous authenticator app, making them unable to log in again using TOTP. Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com> * refactor: fix eslint errors The PR build was failing given that linting returning some errors. This commit attempts to fix them. * refactor: normalize i18n translations The build was failing given that i18n translations files were not normalized. This commits fixes that. * refactor: avoid having the webauthn gem locked to a specific version * refactor: use symbols for routes without '/' * refactor: avoid sending webauthn disabled email when 2FA is disabled When an admins disable 2FA for users, we were sending two mails to them, one notifying that 2FA was disabled and the other to notify that WebAuthn was disabled. As the second one is redundant since the first email includes it, we can remove it and send just one email to users. * refactor: avoid creating new env variable for webauthn_origin config * refactor: improve flash error messages for webauthn pages Co-authored-by: Facundo Padula <facundo.padula@cedarcode.com>
3 years ago
  1. ---
  2. en:
  3. about:
  4. about_hashtag_html: These are public toots tagged with <strong>#%{hashtag}</strong>. You can interact with them if you have an account anywhere in the fediverse.
  5. about_mastodon_html: 'The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!'
  6. about_this: About
  7. active_count_after: active
  8. active_footnote: Monthly Active Users (MAU)
  9. administered_by: 'Administered by:'
  10. api: API
  11. apps: Mobile apps
  12. apps_platforms: Use Mastodon from iOS, Android and other platforms
  13. browse_directory: Browse a profile directory and filter by interests
  14. browse_local_posts: Browse a live stream of public posts from this server
  15. browse_public_posts: Browse a live stream of public posts on Mastodon
  16. contact: Contact
  17. contact_missing: Not set
  18. contact_unavailable: N/A
  19. discover_users: Discover users
  20. documentation: Documentation
  21. federation_hint_html: With an account on %{instance} you'll be able to follow people on any Mastodon server and beyond.
  22. get_apps: Try a mobile app
  23. hosted_on: Mastodon hosted on %{domain}
  24. instance_actor_flash: |
  25. This account is a virtual actor used to represent the server itself and not any individual user.
  26. It is used for federation purposes and should not be blocked unless you want to block the whole instance, in which case you should use a domain block.
  27. learn_more: Learn more
  28. privacy_policy: Privacy policy
  29. see_whats_happening: See what's happening
  30. server_stats: 'Server stats:'
  31. source_code: Source code
  32. status_count_after:
  33. one: status
  34. other: statuses
  35. status_count_before: Who authored
  36. tagline: Follow friends and discover new ones
  37. terms: Terms of service
  38. unavailable_content: Moderated servers
  39. unavailable_content_description:
  40. domain: Server
  41. reason: Reason
  42. rejecting_media: 'Media files from these servers will not be processed or stored, and no thumbnails will be displayed, requiring manual click-through to the original file:'
  43. rejecting_media_title: Filtered media
  44. silenced: 'Posts from these servers will be hidden in public timelines and conversations, and no notifications will be generated from their users interactions, unless you are following them:'
  45. silenced_title: Silenced servers
  46. suspended: 'No data from these servers will be processed, stored or exchanged, making any interaction or communication with users from these servers impossible:'
  47. suspended_title: Suspended servers
  48. unavailable_content_html: Mastodon generally allows you to view content from and interact with users from any other server in the fediverse. These are the exceptions that have been made on this particular server.
  49. user_count_after:
  50. one: user
  51. other: users
  52. user_count_before: Home to
  53. what_is_mastodon: What is Mastodon?
  54. accounts:
  55. choices_html: "%{name}'s choices:"
  56. endorsements_hint: You can endorse people you follow from the web interface, and they will show up here.
  57. featured_tags_hint: You can feature specific hashtags that will be displayed here.
  58. follow: Follow
  59. followers:
  60. one: Follower
  61. other: Followers
  62. following: Following
  63. joined: Joined %{date}
  64. last_active: last active
  65. link_verified_on: Ownership of this link was checked on %{date}
  66. media: Media
  67. moved_html: "%{name} has moved to %{new_profile_link}:"
  68. network_hidden: This information is not available
  69. never_active: Never
  70. nothing_here: There is nothing here!
  71. people_followed_by: People whom %{name} follows
  72. people_who_follow: People who follow %{name}
  73. pin_errors:
  74. following: You must be already following the person you want to endorse
  75. posts:
  76. one: Toot
  77. other: Toots
  78. posts_tab_heading: Toots
  79. posts_with_replies: Toots and replies
  80. reserved_username: The username is reserved
  81. roles:
  82. admin: Admin
  83. bot: Bot
  84. group: Group
  85. moderator: Mod
  86. unavailable: Profile unavailable
  87. unfollow: Unfollow
  88. admin:
  89. account_actions:
  90. action: Perform action
  91. title: Perform moderation action on %{acct}
  92. account_moderation_notes:
  93. create: Leave note
  94. created_msg: Moderation note successfully created!
  95. delete: Delete
  96. destroyed_msg: Moderation note successfully destroyed!
  97. accounts:
  98. add_email_domain_block: Block e-mail domain
  99. approve: Approve
  100. approve_all: Approve all
  101. approved_msg: Successfully approved %{username}'s sign-up application
  102. are_you_sure: Are you sure?
  103. avatar: Avatar
  104. by_domain: Domain
  105. change_email:
  106. changed_msg: Account email successfully changed!
  107. current_email: Current email
  108. label: Change email
  109. new_email: New email
  110. submit: Change email
  111. title: Change email for %{username}
  112. confirm: Confirm
  113. confirmed: Confirmed
  114. confirming: Confirming
  115. delete: Delete data
  116. deleted: Deleted
  117. demote: Demote
  118. destroyed_msg: "%{username}'s data is now queued to be deleted imminently"
  119. disable: Freeze
  120. disable_two_factor_authentication: Disable 2FA
  121. disabled: Frozen
  122. display_name: Display name
  123. domain: Domain
  124. edit: Edit
  125. email: Email
  126. email_status: Email status
  127. enable: Unfreeze
  128. enabled: Enabled
  129. enabled_msg: Successfully unfroze %{username}'s account
  130. followers: Followers
  131. follows: Follows
  132. header: Header
  133. inbox_url: Inbox URL
  134. invited_by: Invited by
  135. ip: IP
  136. joined: Joined
  137. location:
  138. all: All
  139. local: Local
  140. remote: Remote
  141. title: Location
  142. login_status: Login status
  143. media_attachments: Media attachments
  144. memorialize: Turn into memoriam
  145. memorialized: Memorialized
  146. memorialized_msg: Successfully turned %{username} into a memorial account
  147. moderation:
  148. active: Active
  149. all: All
  150. pending: Pending
  151. silenced: Silenced
  152. suspended: Suspended
  153. title: Moderation
  154. moderation_notes: Moderation notes
  155. most_recent_activity: Most recent activity
  156. most_recent_ip: Most recent IP
  157. no_account_selected: No accounts were changed as none were selected
  158. no_limits_imposed: No limits imposed
  159. not_subscribed: Not subscribed
  160. pending: Pending review
  161. perform_full_suspension: Suspend
  162. promote: Promote
  163. protocol: Protocol
  164. public: Public
  165. push_subscription_expires: PuSH subscription expires
  166. redownload: Refresh profile
  167. redownloaded_msg: Successfully refreshed %{username}'s profile from origin
  168. reject: Reject
  169. reject_all: Reject all
  170. rejected_msg: Successfully rejected %{username}'s sign-up application
  171. remove_avatar: Remove avatar
  172. remove_header: Remove header
  173. removed_avatar_msg: Successfully removed %{username}'s avatar image
  174. removed_header_msg: Successfully removed %{username}'s header image
  175. resend_confirmation:
  176. already_confirmed: This user is already confirmed
  177. send: Resend confirmation email
  178. success: Confirmation email successfully sent!
  179. reset: Reset
  180. reset_password: Reset password
  181. resubscribe: Resubscribe
  182. role: Permissions
  183. roles:
  184. admin: Administrator
  185. moderator: Moderator
  186. staff: Staff
  187. user: User
  188. search: Search
  189. search_same_email_domain: Other users with the same e-mail domain
  190. search_same_ip: Other users with the same IP
  191. sensitive: Sensitive
  192. sensitized: marked as sensitive
  193. shared_inbox_url: Shared inbox URL
  194. show:
  195. created_reports: Made reports
  196. targeted_reports: Reported by others
  197. silence: Limit
  198. silenced: Limited
  199. statuses: Statuses
  200. subscribe: Subscribe
  201. suspended: Suspended
  202. suspension_irreversible: The data of this account has been irreversibly deleted. You can unsuspend the account to make it usable but it will not recover any data it previously had.
  203. suspension_reversible_hint_html: The account has been suspended, and the data will be fully removed on %{date}. Until then, the account can be restored without any ill effects. If you wish to remove all of the account's data immediately, you can do so below.
  204. time_in_queue: Waiting in queue %{time}
  205. title: Accounts
  206. unconfirmed_email: Unconfirmed email
  207. undo_sensitized: Undo sensitive
  208. undo_silenced: Undo silence
  209. undo_suspension: Undo suspension
  210. unsilenced_msg: Successfully unlimited %{username}'s account
  211. unsubscribe: Unsubscribe
  212. unsuspended_msg: Successfully unsuspended %{username}'s account
  213. username: Username
  214. view_domain: View summary for domain
  215. warn: Warn
  216. web: Web
  217. whitelisted: Allowed for federation
  218. action_logs:
  219. action_types:
  220. assigned_to_self_report: Assign Report
  221. change_email_user: Change E-mail for User
  222. confirm_user: Confirm User
  223. create_account_warning: Create Warning
  224. create_announcement: Create Announcement
  225. create_custom_emoji: Create Custom Emoji
  226. create_domain_allow: Create Domain Allow
  227. create_domain_block: Create Domain Block
  228. create_email_domain_block: Create E-mail Domain Block
  229. create_ip_block: Create IP rule
  230. demote_user: Demote User
  231. destroy_announcement: Delete Announcement
  232. destroy_custom_emoji: Delete Custom Emoji
  233. destroy_domain_allow: Delete Domain Allow
  234. destroy_domain_block: Delete Domain Block
  235. destroy_email_domain_block: Delete e-mail domain block
  236. destroy_ip_block: Delete IP rule
  237. destroy_status: Delete Status
  238. disable_2fa_user: Disable 2FA
  239. disable_custom_emoji: Disable Custom Emoji
  240. disable_user: Disable User
  241. enable_custom_emoji: Enable Custom Emoji
  242. enable_user: Enable User
  243. memorialize_account: Memorialize Account
  244. promote_user: Promote User
  245. remove_avatar_user: Remove Avatar
  246. reopen_report: Reopen Report
  247. reset_password_user: Reset Password
  248. resolve_report: Resolve Report
  249. sensitive_account: Mark the media in your account as sensitive
  250. silence_account: Silence Account
  251. suspend_account: Suspend Account
  252. unassigned_report: Unassign Report
  253. unsensitive_account: Unmark the media in your account as sensitive
  254. unsilence_account: Unsilence Account
  255. unsuspend_account: Unsuspend Account
  256. update_announcement: Update Announcement
  257. update_custom_emoji: Update Custom Emoji
  258. update_domain_block: Update Domain Block
  259. update_status: Update Status
  260. actions:
  261. assigned_to_self_report: "%{name} assigned report %{target} to themselves"
  262. change_email_user: "%{name} changed the e-mail address of user %{target}"
  263. confirm_user: "%{name} confirmed e-mail address of user %{target}"
  264. create_account_warning: "%{name} sent a warning to %{target}"
  265. create_announcement: "%{name} created new announcement %{target}"
  266. create_custom_emoji: "%{name} uploaded new emoji %{target}"
  267. create_domain_allow: "%{name} allowed federation with domain %{target}"
  268. create_domain_block: "%{name} blocked domain %{target}"
  269. create_email_domain_block: "%{name} blocked e-mail domain %{target}"
  270. create_ip_block: "%{name} created rule for IP %{target}"
  271. demote_user: "%{name} demoted user %{target}"
  272. destroy_announcement: "%{name} deleted announcement %{target}"
  273. destroy_custom_emoji: "%{name} destroyed emoji %{target}"
  274. destroy_domain_allow: "%{name} disallowed federation with domain %{target}"
  275. destroy_domain_block: "%{name} unblocked domain %{target}"
  276. destroy_email_domain_block: "%{name} unblocked e-mail domain %{target}"
  277. destroy_ip_block: "%{name} deleted rule for IP %{target}"
  278. destroy_status: "%{name} removed status by %{target}"
  279. disable_2fa_user: "%{name} disabled two factor requirement for user %{target}"
  280. disable_custom_emoji: "%{name} disabled emoji %{target}"
  281. disable_user: "%{name} disabled login for user %{target}"
  282. enable_custom_emoji: "%{name} enabled emoji %{target}"
  283. enable_user: "%{name} enabled login for user %{target}"
  284. memorialize_account: "%{name} turned %{target}'s account into a memoriam page"
  285. promote_user: "%{name} promoted user %{target}"
  286. remove_avatar_user: "%{name} removed %{target}'s avatar"
  287. reopen_report: "%{name} reopened report %{target}"
  288. reset_password_user: "%{name} reset password of user %{target}"
  289. resolve_report: "%{name} resolved report %{target}"
  290. sensitive_account: "%{name} marked %{target}'s media as sensitive"
  291. silence_account: "%{name} silenced %{target}'s account"
  292. suspend_account: "%{name} suspended %{target}'s account"
  293. unassigned_report: "%{name} unassigned report %{target}"
  294. unsensitive_account: "%{name} unmarked %{target}'s media as sensitive"
  295. unsilence_account: "%{name} unsilenced %{target}'s account"
  296. unsuspend_account: "%{name} unsuspended %{target}'s account"
  297. update_announcement: "%{name} updated announcement %{target}"
  298. update_custom_emoji: "%{name} updated emoji %{target}"
  299. update_domain_block: "%{name} updated domain block for %{target}"
  300. update_status: "%{name} updated status by %{target}"
  301. deleted_status: "(deleted status)"
  302. empty: No logs found.
  303. filter_by_action: Filter by action
  304. filter_by_user: Filter by user
  305. title: Audit log
  306. announcements:
  307. destroyed_msg: Announcement successfully deleted!
  308. edit:
  309. title: Edit announcement
  310. empty: No announcements found.
  311. live: Live
  312. new:
  313. create: Create announcement
  314. title: New announcement
  315. published_msg: Announcement successfully published!
  316. scheduled_for: Scheduled for %{time}
  317. scheduled_msg: Announcement scheduled for publication!
  318. title: Announcements
  319. unpublished_msg: Announcement successfully unpublished!
  320. updated_msg: Announcement successfully updated!
  321. custom_emojis:
  322. assign_category: Assign category
  323. by_domain: Domain
  324. copied_msg: Successfully created local copy of the emoji
  325. copy: Copy
  326. copy_failed_msg: Could not make a local copy of that emoji
  327. create_new_category: Create new category
  328. created_msg: Emoji successfully created!
  329. delete: Delete
  330. destroyed_msg: Emojo successfully destroyed!
  331. disable: Disable
  332. disabled: Disabled
  333. disabled_msg: Successfully disabled that emoji
  334. emoji: Emoji
  335. enable: Enable
  336. enabled: Enabled
  337. enabled_msg: Successfully enabled that emoji
  338. image_hint: PNG up to 50KB
  339. list: List
  340. listed: Listed
  341. new:
  342. title: Add new custom emoji
  343. not_permitted: You are not permitted to perform this action
  344. overwrite: Overwrite
  345. shortcode: Shortcode
  346. shortcode_hint: At least 2 characters, only alphanumeric characters and underscores
  347. title: Custom emojis
  348. uncategorized: Uncategorized
  349. unlist: Unlist
  350. unlisted: Unlisted
  351. update_failed_msg: Could not update that emoji
  352. updated_msg: Emoji successfully updated!
  353. upload: Upload
  354. dashboard:
  355. authorized_fetch_mode: Secure mode
  356. backlog: backlogged jobs
  357. config: Configuration
  358. feature_deletions: Account deletions
  359. feature_invites: Invite links
  360. feature_profile_directory: Profile directory
  361. feature_registrations: Registrations
  362. feature_relay: Federation relay
  363. feature_spam_check: Anti-spam
  364. feature_timeline_preview: Timeline preview
  365. features: Features
  366. hidden_service: Federation with hidden services
  367. open_reports: open reports
  368. pending_tags: hashtags waiting for review
  369. pending_users: users waiting for review
  370. recent_users: Recent users
  371. search: Full-text search
  372. single_user_mode: Single user mode
  373. software: Software
  374. space: Space usage
  375. title: Dashboard
  376. total_users: users in total
  377. trends: Trends
  378. week_interactions: interactions this week
  379. week_users_active: active this week
  380. week_users_new: users this week
  381. whitelist_mode: Limited federation mode
  382. domain_allows:
  383. add_new: Allow federation with domain
  384. created_msg: Domain has been successfully allowed for federation
  385. destroyed_msg: Domain has been disallowed from federation
  386. undo: Disallow federation with domain
  387. domain_blocks:
  388. add_new: Add new domain block
  389. created_msg: Domain block is now being processed
  390. destroyed_msg: Domain block has been undone
  391. domain: Domain
  392. edit: Edit domain block
  393. existing_domain_block_html: You have already imposed stricter limits on %{name}, you need to <a href="%{unblock_url}">unblock it</a> first.
  394. new:
  395. create: Create block
  396. hint: The domain block will not prevent creation of account entries in the database, but will retroactively and automatically apply specific moderation methods on those accounts.
  397. severity:
  398. desc_html: "<strong>Silence</strong> will make the account's posts invisible to anyone who isn't following them. <strong>Suspend</strong> will remove all of the account's content, media, and profile data. Use <strong>None</strong> if you just want to reject media files."
  399. noop: None
  400. silence: Silence
  401. suspend: Suspend
  402. title: New domain block
  403. private_comment: Private comment
  404. private_comment_hint: Comment about this domain limitation for internal use by the moderators.
  405. public_comment: Public comment
  406. public_comment_hint: Comment about this domain limitation for the general public, if advertising the list of domain limitations is enabled.
  407. reject_media: Reject media files
  408. reject_media_hint: Removes locally stored media files and refuses to download any in the future. Irrelevant for suspensions
  409. reject_reports: Reject reports
  410. reject_reports_hint: Ignore all reports coming from this domain. Irrelevant for suspensions
  411. rejecting_media: rejecting media files
  412. rejecting_reports: rejecting reports
  413. severity:
  414. silence: silenced
  415. suspend: suspended
  416. show:
  417. affected_accounts:
  418. one: One account in the database affected
  419. other: "%{count} accounts in the database affected"
  420. retroactive:
  421. silence: Unsilence existing affected accounts from this domain
  422. suspend: Unsuspend existing affected accounts from this domain
  423. title: Undo domain block for %{domain}
  424. undo: Undo
  425. undo: Undo domain block
  426. view: View domain block
  427. email_domain_blocks:
  428. add_new: Add new
  429. created_msg: Successfully blocked e-mail domain
  430. delete: Delete
  431. destroyed_msg: Successfully unblocked e-mail domain
  432. domain: Domain
  433. empty: No e-mail domains currently blocked.
  434. from_html: from %{domain}
  435. new:
  436. create: Add domain
  437. title: Block new e-mail domain
  438. title: Blocked e-mail domains
  439. instances:
  440. by_domain: Domain
  441. delivery_available: Delivery is available
  442. empty: No domains found.
  443. known_accounts:
  444. one: "%{count} known account"
  445. other: "%{count} known accounts"
  446. moderation:
  447. all: All
  448. limited: Limited
  449. title: Moderation
  450. private_comment: Private comment
  451. public_comment: Public comment
  452. title: Federation
  453. total_blocked_by_us: Blocked by us
  454. total_followed_by_them: Followed by them
  455. total_followed_by_us: Followed by us
  456. total_reported: Reports about them
  457. total_storage: Media attachments
  458. invites:
  459. deactivate_all: Deactivate all
  460. filter:
  461. all: All
  462. available: Available
  463. expired: Expired
  464. title: Filter
  465. title: Invites
  466. ip_blocks:
  467. add_new: Create rule
  468. created_msg: Successfully added new IP rule
  469. delete: Delete
  470. expires_in:
  471. '1209600': 2 weeks
  472. '15778476': 6 months
  473. '2629746': 1 month
  474. '31556952': 1 year
  475. '86400': 1 day
  476. '94670856': 3 years
  477. new:
  478. title: Create new IP rule
  479. no_ip_block_selected: No IP rules were changed as none were selected
  480. title: IP rules
  481. pending_accounts:
  482. title: Pending accounts (%{count})
  483. relationships:
  484. title: "%{acct}'s relationships"
  485. relays:
  486. add_new: Add new relay
  487. delete: Delete
  488. description_html: A <strong>federation relay</strong> is an intermediary server that exchanges large volumes of public toots between servers that subscribe and publish to it. <strong>It can help small and medium servers discover content from the fediverse</strong>, which would otherwise require local users manually following other people on remote servers.
  489. disable: Disable
  490. disabled: Disabled
  491. enable: Enable
  492. enable_hint: Once enabled, your server will subscribe to all public toots from this relay, and will begin sending this server's public toots to it.
  493. enabled: Enabled
  494. inbox_url: Relay URL
  495. pending: Waiting for relay's approval
  496. save_and_enable: Save and enable
  497. setup: Setup a relay connection
  498. signatures_not_enabled: Relays will not work correctly while secure mode or limited federation mode is enabled
  499. status: Status
  500. title: Relays
  501. report_notes:
  502. created_msg: Report note successfully created!
  503. destroyed_msg: Report note successfully deleted!
  504. reports:
  505. account:
  506. notes:
  507. one: "%{count} note"
  508. other: "%{count} notes"
  509. reports:
  510. one: "%{count} report"
  511. other: "%{count} reports"
  512. action_taken_by: Action taken by
  513. are_you_sure: Are you sure?
  514. assign_to_self: Assign to me
  515. assigned: Assigned moderator
  516. by_target_domain: Domain of reported account
  517. comment:
  518. none: None
  519. created_at: Reported
  520. forwarded: Forwarded
  521. forwarded_to: Forwarded to %{domain}
  522. mark_as_resolved: Mark as resolved
  523. mark_as_unresolved: Mark as unresolved
  524. notes:
  525. create: Add note
  526. create_and_resolve: Resolve with note
  527. create_and_unresolve: Reopen with note
  528. delete: Delete
  529. placeholder: Describe what actions have been taken, or any other related updates...
  530. reopen: Reopen report
  531. report: 'Report #%{id}'
  532. reported_account: Reported account
  533. reported_by: Reported by
  534. resolved: Resolved
  535. resolved_msg: Report successfully resolved!
  536. status: Status
  537. title: Reports
  538. unassign: Unassign
  539. unresolved: Unresolved
  540. updated_at: Updated
  541. settings:
  542. activity_api_enabled:
  543. desc_html: Counts of locally posted statuses, active users, and new registrations in weekly buckets
  544. title: Publish aggregate statistics about user activity
  545. bootstrap_timeline_accounts:
  546. desc_html: Separate multiple usernames by comma. Only local and unlocked accounts will work. Default when empty is all local admins.
  547. title: Default follows for new users
  548. contact_information:
  549. email: Business e-mail
  550. username: Contact username
  551. custom_css:
  552. desc_html: Modify the look with CSS loaded on every page
  553. title: Custom CSS
  554. default_noindex:
  555. desc_html: Affects all users who have not changed this setting themselves
  556. title: Opt users out of search engine indexing by default
  557. domain_blocks:
  558. all: To everyone
  559. disabled: To no one
  560. title: Show domain blocks
  561. users: To logged-in local users
  562. domain_blocks_rationale:
  563. title: Show rationale
  564. enable_bootstrap_timeline_accounts:
  565. title: Enable default follows for new users
  566. hero:
  567. desc_html: Displayed on the frontpage. At least 600x100px recommended. When not set, falls back to server thumbnail
  568. title: Hero image
  569. mascot:
  570. desc_html: Displayed on multiple pages. At least 293×205px recommended. When not set, falls back to default mascot
  571. title: Mascot image
  572. peers_api_enabled:
  573. desc_html: Domain names this server has encountered in the fediverse
  574. title: Publish list of discovered servers
  575. preview_sensitive_media:
  576. desc_html: Link previews on other websites will display a thumbnail even if the media is marked as sensitive
  577. title: Show sensitive media in OpenGraph previews
  578. profile_directory:
  579. desc_html: Allow users to be discoverable
  580. title: Enable profile directory
  581. registrations:
  582. closed_message:
  583. desc_html: Displayed on frontpage when registrations are closed. You can use HTML tags
  584. title: Closed registration message
  585. deletion:
  586. desc_html: Allow anyone to delete their account
  587. title: Open account deletion
  588. min_invite_role:
  589. disabled: No one
  590. title: Allow invitations by
  591. require_invite_text:
  592. desc_html: When registrations require manual approval, make the “Why do you want to join?” invite request text mandatory rather than optional
  593. title: Require new users to fill an invite request text
  594. registrations_mode:
  595. modes:
  596. approved: Approval required for sign up
  597. none: Nobody can sign up
  598. open: Anyone can sign up
  599. title: Registrations mode
  600. show_known_fediverse_at_about_page:
  601. desc_html: When disabled, restricts the public timeline linked from the landing page to showing only local content
  602. title: Include federated content on unauthenticated public timeline page
  603. show_staff_badge:
  604. desc_html: Show a staff badge on a user page
  605. title: Show staff badge
  606. site_description:
  607. desc_html: Introductory paragraph on the API. Describe what makes this Mastodon server special and anything else important. You can use HTML tags, in particular <code>&lt;a&gt;</code> and <code>&lt;em&gt;</code>.
  608. title: Server description
  609. site_description_extended:
  610. desc_html: A good place for your code of conduct, rules, guidelines and other things that set your server apart. You can use HTML tags
  611. title: Custom extended information
  612. site_short_description:
  613. desc_html: Displayed in sidebar and meta tags. Describe what Mastodon is and what makes this server special in a single paragraph.
  614. title: Short server description
  615. site_terms:
  616. desc_html: You can write your own privacy policy, terms of service or other legalese. You can use HTML tags
  617. title: Custom terms of service
  618. site_title: Server name
  619. spam_check_enabled:
  620. desc_html: Mastodon can auto-report accounts that send repeated unsolicited messages. There may be false positives.
  621. title: Anti-spam automation
  622. thumbnail:
  623. desc_html: Used for previews via OpenGraph and API. 1200x630px recommended
  624. title: Server thumbnail
  625. timeline_preview:
  626. desc_html: Display link to public timeline on landing page and allow API access to the public timeline without authentication
  627. title: Allow unauthenticated access to public timeline
  628. title: Site settings
  629. trendable_by_default:
  630. desc_html: Affects hashtags that have not been previously disallowed
  631. title: Allow hashtags to trend without prior review
  632. trends:
  633. desc_html: Publicly display previously reviewed hashtags that are currently trending
  634. title: Trending hashtags
  635. site_uploads:
  636. delete: Delete uploaded file
  637. destroyed_msg: Site upload successfully deleted!
  638. statuses:
  639. back_to_account: Back to account page
  640. batch:
  641. delete: Delete
  642. nsfw_off: Mark as not sensitive
  643. nsfw_on: Mark as sensitive
  644. deleted: Deleted
  645. failed_to_execute: Failed to execute
  646. media:
  647. title: Media
  648. no_media: No media
  649. no_status_selected: No statuses were changed as none were selected
  650. title: Account statuses
  651. with_media: With media
  652. tags:
  653. accounts_today: Unique uses today
  654. accounts_week: Unique uses this week
  655. breakdown: Breakdown of today's usage by source
  656. context: Context
  657. directory: In directory
  658. in_directory: "%{count} in directory"
  659. last_active: Last active
  660. most_popular: Most popular
  661. most_recent: Most recent
  662. name: Hashtag
  663. review: Review status
  664. reviewed: Reviewed
  665. title: Hashtags
  666. trending_right_now: Trending right now
  667. unique_uses_today: "%{count} posting today"
  668. unreviewed: Not reviewed
  669. updated_msg: Hashtag settings updated successfully
  670. title: Administration
  671. warning_presets:
  672. add_new: Add new
  673. delete: Delete
  674. edit_preset: Edit warning preset
  675. title: Manage warning presets
  676. admin_mailer:
  677. new_pending_account:
  678. body: The details of the new account are below. You can approve or reject this application.
  679. subject: New account up for review on %{instance} (%{username})
  680. new_report:
  681. body: "%{reporter} has reported %{target}"
  682. body_remote: Someone from %{domain} has reported %{target}
  683. subject: New report for %{instance} (#%{id})
  684. new_trending_tag:
  685. body: 'The hashtag #%{name} is trending today, but has not been previously reviewed. It will not be displayed publicly unless you allow it to, or just save the form as it is to never hear about it again.'
  686. subject: New hashtag up for review on %{instance} (#%{name})
  687. aliases:
  688. add_new: Create alias
  689. created_msg: Successfully created a new alias. You can now initiate the move from the old account.
  690. deleted_msg: Successfully remove the alias. Moving from that account to this one will no longer be possible.
  691. empty: You have no aliases.
  692. hint_html: If you want to move from another account to this one, here you can create an alias, which is required before you can proceed with moving followers from the old account to this one. This action by itself is <strong>harmless and reversible</strong>. <strong>The account migration is initiated from the old account</strong>.
  693. remove: Unlink alias
  694. appearance:
  695. advanced_web_interface: Advanced web interface
  696. advanced_web_interface_hint: 'If you want to make use of your entire screen width, the advanced web interface allows you to configure many different columns to see as much information at the same time as you want: Home, notifications, federated timeline, any number of lists and hashtags.'
  697. animations_and_accessibility: Animations and accessibility
  698. confirmation_dialogs: Confirmation dialogs
  699. discovery: Discovery
  700. localization:
  701. body: Mastodon is translated by volunteers.
  702. guide_link: https://crowdin.com/project/mastodon
  703. guide_link_text: Everyone can contribute.
  704. sensitive_content: Sensitive content
  705. toot_layout: Toot layout
  706. application_mailer:
  707. notification_preferences: Change e-mail preferences
  708. salutation: "%{name},"
  709. settings: 'Change e-mail preferences: %{link}'
  710. view: 'View:'
  711. view_profile: View profile
  712. view_status: View status
  713. applications:
  714. created: Application successfully created
  715. destroyed: Application successfully deleted
  716. invalid_url: The provided URL is invalid
  717. regenerate_token: Regenerate access token
  718. token_regenerated: Access token successfully regenerated
  719. warning: Be very careful with this data. Never share it with anyone!
  720. your_token: Your access token
  721. auth:
  722. apply_for_account: Request an invite
  723. change_password: Password
  724. checkbox_agreement_html: I agree to the <a href="%{rules_path}" target="_blank">server rules</a> and <a href="%{terms_path}" target="_blank">terms of service</a>
  725. checkbox_agreement_without_rules_html: I agree to the <a href="%{terms_path}" target="_blank">terms of service</a>
  726. delete_account: Delete account
  727. delete_account_html: If you wish to delete your account, you can <a href="%{path}">proceed here</a>. You will be asked for confirmation.
  728. description:
  729. prefix_invited_by_user: "@%{name} invites you to join this server of Mastodon!"
  730. prefix_sign_up: Sign up on Mastodon today!
  731. suffix: With an account, you will be able to follow people, post updates and exchange messages with users from any Mastodon server and more!
  732. didnt_get_confirmation: Didn't receive confirmation instructions?
  733. dont_have_your_security_key: Don't have your security key?
  734. forgot_password: Forgot your password?
  735. invalid_reset_password_token: Password reset token is invalid or expired. Please request a new one.
  736. link_to_otp: Enter a two-factor code from your phone or a recovery code
  737. link_to_webauth: Use your security key device
  738. login: Log in
  739. logout: Logout
  740. migrate_account: Move to a different account
  741. migrate_account_html: If you wish to redirect this account to a different one, you can <a href="%{path}">configure it here</a>.
  742. or_log_in_with: Or log in with
  743. providers:
  744. cas: CAS
  745. saml: SAML
  746. register: Sign up
  747. registration_closed: "%{instance} is not accepting new members"
  748. resend_confirmation: Resend confirmation instructions
  749. reset_password: Reset password
  750. security: Security
  751. set_new_password: Set new password
  752. setup:
  753. email_below_hint_html: If the below e-mail address is incorrect, you can change it here and receive a new confirmation e-mail.
  754. email_settings_hint_html: The confirmation e-mail was sent to %{email}. If that e-mail address is not correct, you can change it in account settings.
  755. title: Setup
  756. status:
  757. account_status: Account status
  758. confirming: Waiting for e-mail confirmation to be completed.
  759. functional: Your account is fully operational.
  760. pending: Your application is pending review by our staff. This may take some time. You will receive an e-mail if your application is approved.
  761. redirecting_to: Your account is inactive because it is currently redirecting to %{acct}.
  762. too_fast: Form submitted too fast, try again.
  763. trouble_logging_in: Trouble logging in?
  764. use_security_key: Use security key
  765. authorize_follow:
  766. already_following: You are already following this account
  767. already_requested: You have already sent a follow request to that account
  768. error: Unfortunately, there was an error looking up the remote account
  769. follow: Follow
  770. follow_request: 'You have sent a follow request to:'
  771. following: 'Success! You are now following:'
  772. post_follow:
  773. close: Or, you can just close this window.
  774. return: Show the user's profile
  775. web: Go to web
  776. title: Follow %{acct}
  777. challenge:
  778. confirm: Continue
  779. hint_html: "<strong>Tip:</strong> We won't ask you for your password again for the next hour."
  780. invalid_password: Invalid password
  781. prompt: Confirm password to continue
  782. crypto:
  783. errors:
  784. invalid_key: is not a valid Ed25519 or Curve25519 key
  785. invalid_signature: is not a valid Ed25519 signature
  786. date:
  787. formats:
  788. default: "%b %d, %Y"
  789. with_month_name: "%B %d, %Y"
  790. datetime:
  791. distance_in_words:
  792. about_x_hours: "%{count}h"
  793. about_x_months: "%{count}mo"
  794. about_x_years: "%{count}y"
  795. almost_x_years: "%{count}y"
  796. half_a_minute: Just now
  797. less_than_x_minutes: "%{count}m"
  798. less_than_x_seconds: Just now
  799. over_x_years: "%{count}y"
  800. x_days: "%{count}d"
  801. x_minutes: "%{count}m"
  802. x_months: "%{count}mo"
  803. x_seconds: "%{count}s"
  804. deletes:
  805. challenge_not_passed: The information you entered was not correct
  806. confirm_password: Enter your current password to verify your identity
  807. confirm_username: Enter your username to confirm the procedure
  808. proceed: Delete account
  809. success_msg: Your account was successfully deleted
  810. warning:
  811. before: 'Before proceeding, please read these notes carefully:'
  812. caches: Content that has been cached by other servers may persist
  813. data_removal: Your posts and other data will be permanently removed
  814. email_change_html: You can <a href="%{path}">change your e-mail address</a> without deleting your account
  815. email_contact_html: If it still doesn't arrive, you can e-mail <a href="mailto:%{email}">%{email}</a> for help
  816. email_reconfirmation_html: If you are not receiving the confirmation e-mail, you can <a href="%{path}">request it again</a>
  817. irreversible: You will not be able to restore or reactivate your account
  818. more_details_html: For more details, see the <a href="%{terms_path}">privacy policy</a>.
  819. username_available: Your username will become available again
  820. username_unavailable: Your username will remain unavailable
  821. directories:
  822. directory: Profile directory
  823. explanation: Discover users based on their interests
  824. explore_mastodon: Explore %{title}
  825. domain_validator:
  826. invalid_domain: is not a valid domain name
  827. errors:
  828. '400': The request you submitted was invalid or malformed.
  829. '403': You don't have permission to view this page.
  830. '404': The page you are looking for isn't here.
  831. '406': This page is not available in the requested format.
  832. '410': The page you were looking for doesn't exist here anymore.
  833. '422':
  834. content: Security verification failed. Are you blocking cookies?
  835. title: Security verification failed
  836. '429': Too many requests
  837. '500':
  838. content: We're sorry, but something went wrong on our end.
  839. title: This page is not correct
  840. '503': The page could not be served due to a temporary server failure.
  841. noscript_html: To use the Mastodon web application, please enable JavaScript. Alternatively, try one of the <a href="%{apps_path}">native apps</a> for Mastodon for your platform.
  842. existing_username_validator:
  843. not_found: could not find a local user with that username
  844. not_found_multiple: could not find %{usernames}
  845. exports:
  846. archive_takeout:
  847. date: Date
  848. download: Download your archive
  849. hint_html: You can request an archive of your <strong>toots and uploaded media</strong>. The exported data will be in the ActivityPub format, readable by any compliant software. You can request an archive every 7 days.
  850. in_progress: Compiling your archive...
  851. request: Request your archive
  852. size: Size
  853. blocks: You block
  854. bookmarks: Bookmarks
  855. csv: CSV
  856. domain_blocks: Domain blocks
  857. lists: Lists
  858. mutes: You mute
  859. storage: Media storage
  860. featured_tags:
  861. add_new: Add new
  862. errors:
  863. limit: You have already featured the maximum amount of hashtags
  864. hint_html: "<strong>What are featured hashtags?</strong> They are displayed prominently on your public profile and allow people to browse your public posts specifically under those hashtags. They are a great tool for keeping track of creative works or long-term projects."
  865. filters:
  866. contexts:
  867. account: Profiles
  868. home: Home and lists
  869. notifications: Notifications
  870. public: Public timelines
  871. thread: Conversations
  872. edit:
  873. title: Edit filter
  874. errors:
  875. invalid_context: None or invalid context supplied
  876. invalid_irreversible: Irreversible filtering only works with home or notifications context
  877. index:
  878. delete: Delete
  879. empty: You have no filters.
  880. title: Filters
  881. new:
  882. title: Add new filter
  883. footer:
  884. developers: Developers
  885. more: More…
  886. resources: Resources
  887. trending_now: Trending now
  888. generic:
  889. all: All
  890. changes_saved_msg: Changes successfully saved!
  891. copy: Copy
  892. delete: Delete
  893. no_batch_actions_available: No batch actions available on this page
  894. order_by: Order by
  895. save_changes: Save changes
  896. validation_errors:
  897. one: Something isn't quite right yet! Please review the error below
  898. other: Something isn't quite right yet! Please review %{count} errors below
  899. html_validator:
  900. invalid_markup: 'contains invalid HTML markup: %{error}'
  901. identity_proofs:
  902. active: Active
  903. authorize: Yes, authorize
  904. authorize_connection_prompt: Authorize this cryptographic connection?
  905. errors:
  906. failed: The cryptographic connection failed. Please try again from %{provider}.
  907. keybase:
  908. invalid_token: Keybase tokens are hashes of signatures and must be 66 hex characters
  909. verification_failed: Keybase does not recognize this token as a signature of Keybase user %{kb_username}. Please retry from Keybase.
  910. wrong_user: Cannot create a proof for %{proving} while logged in as %{current}. Log in as %{proving} and try again.
  911. explanation_html: Here you can cryptographically connect your other identities from other platforms, such as Keybase. This lets other people send you encrypted messages on those platforms and allows them to trust that the content you send them comes from you.
  912. i_am_html: I am %{username} on %{service}.
  913. identity: Identity
  914. inactive: Inactive
  915. publicize_checkbox: 'And toot this:'
  916. publicize_toot: 'It is proven! I am %{username} on %{service}: %{url}'
  917. remove: Remove proof from account
  918. removed: Successfully removed proof from account
  919. status: Verification status
  920. view_proof: View proof
  921. imports:
  922. modes:
  923. merge: Merge
  924. merge_long: Keep existing records and add new ones
  925. overwrite: Overwrite
  926. overwrite_long: Replace current records with the new ones
  927. preface: You can import data that you have exported from another server, such as a list of the people you are following or blocking.
  928. success: Your data was successfully uploaded and will now be processed in due time
  929. types:
  930. blocking: Blocking list
  931. bookmarks: Bookmarks
  932. domain_blocking: Domain blocking list
  933. following: Following list
  934. muting: Muting list
  935. upload: Upload
  936. in_memoriam_html: In Memoriam.
  937. invites:
  938. delete: Deactivate
  939. expired: Expired
  940. expires_in:
  941. '1800': 30 minutes
  942. '21600': 6 hours
  943. '3600': 1 hour
  944. '43200': 12 hours
  945. '604800': 1 week
  946. '86400': 1 day
  947. expires_in_prompt: Never
  948. generate: Generate invite link
  949. invited_by: 'You were invited by:'
  950. max_uses:
  951. one: 1 use
  952. other: "%{count} uses"
  953. max_uses_prompt: No limit
  954. prompt: Generate and share links with others to grant access to this server
  955. table:
  956. expires_at: Expires
  957. uses: Uses
  958. title: Invite people
  959. lists:
  960. errors:
  961. limit: You have reached the maximum amount of lists
  962. media_attachments:
  963. validations:
  964. images_and_video: Cannot attach a video to a status that already contains images
  965. not_ready: Cannot attach files that have not finished processing. Try again in a moment!
  966. too_many: Cannot attach more than 4 files
  967. migrations:
  968. acct: Moved to
  969. cancel: Cancel redirect
  970. cancel_explanation: Cancelling the redirect will re-activate your current account, but will not bring back followers that have been moved to that account.
  971. cancelled_msg: Successfully cancelled the redirect.
  972. errors:
  973. already_moved: is the same account you have already moved to
  974. missing_also_known_as: is not an alias of this account
  975. move_to_self: cannot be current account
  976. not_found: could not be found
  977. on_cooldown: You are on cooldown
  978. followers_count: Followers at time of move
  979. incoming_migrations: Moving from a different account
  980. incoming_migrations_html: To move from another account to this one, first you need to <a href="%{path}">create an account alias</a>.
  981. moved_msg: Your account is now redirecting to %{acct} and your followers are being moved over.
  982. not_redirecting: Your account is not redirecting to any other account currently.
  983. on_cooldown: You have recently migrated your account. This function will become available again in %{count} days.
  984. past_migrations: Past migrations
  985. proceed_with_move: Move followers
  986. redirected_msg: Your account is now redirecting to %{acct}.
  987. redirecting_to: Your account is redirecting to %{acct}.
  988. set_redirect: Set redirect
  989. warning:
  990. backreference_required: The new account must first be configured to back-reference this one
  991. before: 'Before proceeding, please read these notes carefully:'
  992. cooldown: After moving there is a cooldown period during which you will not be able to move again
  993. disabled_account: Your current account will not be fully usable afterwards. However, you will have access to data export as well as re-activation.
  994. followers: This action will move all followers from the current account to the new account
  995. only_redirect_html: Alternatively, you can <a href="%{path}">only put up a redirect on your profile</a>.
  996. other_data: No other data will be moved automatically
  997. redirect: Your current account's profile will be updated with a redirect notice and be excluded from searches
  998. moderation:
  999. title: Moderation
  1000. move_handler:
  1001. carry_blocks_over_text: This user moved from %{acct}, which you had blocked.
  1002. carry_mutes_over_text: This user moved from %{acct}, which you had muted.
  1003. copy_account_note_text: 'This user moved from %{acct}, here were your previous notes about them:'
  1004. notification_mailer:
  1005. digest:
  1006. action: View all notifications
  1007. body: Here is a brief summary of the messages you missed since your last visit on %{since}
  1008. mention: "%{name} mentioned you in:"
  1009. new_followers_summary:
  1010. one: Also, you have acquired one new follower while being away! Yay!
  1011. other: Also, you have acquired %{count} new followers while being away! Amazing!
  1012. subject:
  1013. one: "1 new notification since your last visit \U0001F418"
  1014. other: "%{count} new notifications since your last visit \U0001F418"
  1015. title: In your absence...
  1016. favourite:
  1017. body: 'Your status was favourited by %{name}:'
  1018. subject: "%{name} favourited your status"
  1019. title: New favourite
  1020. follow:
  1021. body: "%{name} is now following you!"
  1022. subject: "%{name} is now following you"
  1023. title: New follower
  1024. follow_request:
  1025. action: Manage follow requests
  1026. body: "%{name} has requested to follow you"
  1027. subject: 'Pending follower: %{name}'
  1028. title: New follow request
  1029. mention:
  1030. action: Reply
  1031. body: 'You were mentioned by %{name} in:'
  1032. subject: You were mentioned by %{name}
  1033. title: New mention
  1034. reblog:
  1035. body: 'Your status was boosted by %{name}:'
  1036. subject: "%{name} boosted your status"
  1037. title: New boost
  1038. notifications:
  1039. email_events: Events for e-mail notifications
  1040. email_events_hint: 'Select events that you want to receive notifications for:'
  1041. other_settings: Other notifications settings
  1042. number:
  1043. human:
  1044. decimal_units:
  1045. format: "%n%u"
  1046. units:
  1047. billion: B
  1048. million: M
  1049. quadrillion: Q
  1050. thousand: K
  1051. trillion: T
  1052. unit: ''
  1053. otp_authentication:
  1054. code_hint: Enter the code generated by your authenticator app to confirm
  1055. description_html: If you enable <strong>two-factor authentication</strong> using an authenticator app, logging in will require you to be in possession of your phone, which will generate tokens for you to enter.
  1056. enable: Enable
  1057. instructions_html: "<strong>Scan this QR code into Google Authenticator or a similiar TOTP app on your phone</strong>. From now on, that app will generate tokens that you will have to enter when logging in."
  1058. manual_instructions: 'If you can''t scan the QR code and need to enter it manually, here is the plain-text secret:'
  1059. setup: Set up
  1060. wrong_code: The entered code was invalid! Are server time and device time correct?
  1061. pagination:
  1062. newer: Newer
  1063. next: Next
  1064. older: Older
  1065. prev: Prev
  1066. truncate: "&hellip;"
  1067. polls:
  1068. errors:
  1069. already_voted: You have already voted on this poll
  1070. duplicate_options: contain duplicate items
  1071. duration_too_long: is too far into the future
  1072. duration_too_short: is too soon
  1073. expired: The poll has already ended
  1074. invalid_choice: The chosen vote option does not exist
  1075. over_character_limit: cannot be longer than %{max} characters each
  1076. too_few_options: must have more than one item
  1077. too_many_options: can't contain more than %{max} items
  1078. preferences:
  1079. other: Other
  1080. posting_defaults: Posting defaults
  1081. public_timelines: Public timelines
  1082. reactions:
  1083. errors:
  1084. limit_reached: Limit of different reactions reached
  1085. unrecognized_emoji: is not a recognized emoji
  1086. relationships:
  1087. activity: Account activity
  1088. dormant: Dormant
  1089. follow_selected_followers: Follow selected followers
  1090. followers: Followers
  1091. following: Following
  1092. invited: Invited
  1093. last_active: Last active
  1094. most_recent: Most recent
  1095. moved: Moved
  1096. mutual: Mutual
  1097. primary: Primary
  1098. relationship: Relationship
  1099. remove_selected_domains: Remove all followers from the selected domains
  1100. remove_selected_followers: Remove selected followers
  1101. remove_selected_follows: Unfollow selected users
  1102. status: Account status
  1103. remote_follow:
  1104. acct: Enter your username@domain you want to act from
  1105. missing_resource: Could not find the required redirect URL for your account
  1106. no_account_html: Don't have an account? You can <a href='%{sign_up_path}' target='_blank'>sign up here</a>
  1107. proceed: Proceed to follow
  1108. prompt: 'You are going to follow:'
  1109. reason_html: "<strong>Why is this step necessary?</strong> <code>%{instance}</code> might not be the server where you are registered, so we need to redirect you to your home server first."
  1110. remote_interaction:
  1111. favourite:
  1112. proceed: Proceed to favourite
  1113. prompt: 'You want to favourite this toot:'
  1114. reblog:
  1115. proceed: Proceed to boost
  1116. prompt: 'You want to boost this toot:'
  1117. reply:
  1118. proceed: Proceed to reply
  1119. prompt: 'You want to reply to this toot:'
  1120. scheduled_statuses:
  1121. over_daily_limit: You have exceeded the limit of %{limit} scheduled toots for that day
  1122. over_total_limit: You have exceeded the limit of %{limit} scheduled toots
  1123. too_soon: The scheduled date must be in the future
  1124. sessions:
  1125. activity: Last activity
  1126. browser: Browser
  1127. browsers:
  1128. alipay: Alipay
  1129. blackberry: Blackberry
  1130. chrome: Chrome
  1131. edge: Microsoft Edge
  1132. electron: Electron
  1133. firefox: Firefox
  1134. generic: Unknown browser
  1135. ie: Internet Explorer
  1136. micro_messenger: MicroMessenger
  1137. nokia: Nokia S40 Ovi Browser
  1138. opera: Opera
  1139. otter: Otter
  1140. phantom_js: PhantomJS
  1141. qq: QQ Browser
  1142. safari: Safari
  1143. uc_browser: UCBrowser
  1144. weibo: Weibo
  1145. current_session: Current session
  1146. description: "%{browser} on %{platform}"
  1147. explanation: These are the web browsers currently logged in to your Mastodon account.
  1148. ip: IP
  1149. platforms:
  1150. adobe_air: Adobe Air
  1151. android: Android
  1152. blackberry: Blackberry
  1153. chrome_os: ChromeOS
  1154. firefox_os: Firefox OS
  1155. ios: iOS
  1156. linux: Linux
  1157. mac: macOS
  1158. other: unknown platform
  1159. windows: Windows
  1160. windows_mobile: Windows Mobile
  1161. windows_phone: Windows Phone
  1162. revoke: Revoke
  1163. revoke_success: Session successfully revoked
  1164. title: Sessions
  1165. settings:
  1166. account: Account
  1167. account_settings: Account settings
  1168. aliases: Account aliases
  1169. appearance: Appearance
  1170. authorized_apps: Authorized apps
  1171. back: Back to Mastodon
  1172. delete: Account deletion
  1173. development: Development
  1174. edit_profile: Edit profile
  1175. export: Data export
  1176. featured_tags: Featured hashtags
  1177. identity_proofs: Identity proofs
  1178. import: Import
  1179. import_and_export: Import and export
  1180. migrate: Account migration
  1181. notifications: Notifications
  1182. preferences: Preferences
  1183. profile: Profile
  1184. relationships: Follows and followers
  1185. two_factor_authentication: Two-factor Auth
  1186. webauthn_authentication: Security keys
  1187. spam_check:
  1188. spam_detected: This is an automated report. Spam has been detected.
  1189. statuses:
  1190. attached:
  1191. audio:
  1192. one: "%{count} audio"
  1193. other: "%{count} audio"
  1194. description: 'Attached: %{attached}'
  1195. image:
  1196. one: "%{count} image"
  1197. other: "%{count} images"
  1198. video:
  1199. one: "%{count} video"
  1200. other: "%{count} videos"
  1201. boosted_from_html: Boosted from %{acct_link}
  1202. content_warning: 'Content warning: %{warning}'
  1203. disallowed_hashtags:
  1204. one: 'contained a disallowed hashtag: %{tags}'
  1205. other: 'contained the disallowed hashtags: %{tags}'
  1206. errors:
  1207. in_reply_not_found: The status you are trying to reply to does not appear to exist.
  1208. language_detection: Automatically detect language
  1209. open_in_web: Open in web
  1210. over_character_limit: character limit of %{max} exceeded
  1211. pin_errors:
  1212. limit: You have already pinned the maximum number of toots
  1213. ownership: Someone else's toot cannot be pinned
  1214. private: Non-public toot cannot be pinned
  1215. reblog: A boost cannot be pinned
  1216. poll:
  1217. total_people:
  1218. one: "%{count} person"
  1219. other: "%{count} people"
  1220. total_votes:
  1221. one: "%{count} vote"
  1222. other: "%{count} votes"
  1223. vote: Vote
  1224. show_more: Show more
  1225. show_newer: Show newer
  1226. show_older: Show older
  1227. show_thread: Show thread
  1228. sign_in_to_participate: Sign in to participate in the conversation
  1229. title: '%{name}: "%{quote}"'
  1230. visibilities:
  1231. private: Followers-only
  1232. private_long: Only show to followers
  1233. public: Public
  1234. public_long: Everyone can see
  1235. unlisted: Unlisted
  1236. unlisted_long: Everyone can see, but not listed on public timelines
  1237. stream_entries:
  1238. pinned: Pinned toot
  1239. reblogged: boosted
  1240. sensitive_content: Sensitive content
  1241. tags:
  1242. does_not_match_previous_name: does not match the previous name
  1243. terms:
  1244. body_html: |
  1245. <h2>Privacy Policy</h2>
  1246. <h3 id="collect">What information do we collect?</h3>
  1247. <ul>
  1248. <li><em>Basic account information</em>: If you register on this server, you may be asked to enter a username, an e-mail address and a password. You may also enter additional profile information such as a display name and biography, and upload a profile picture and header image. The username, display name, biography, profile picture and header image are always listed publicly.</li>
  1249. <li><em>Posts, following and other public information</em>: The list of people you follow is listed publicly, the same is true for your followers. When you submit a message, the date and time is stored as well as the application you submitted the message from. Messages may contain media attachments, such as pictures and videos. Public and unlisted posts are available publicly. When you feature a post on your profile, that is also publicly available information. Your posts are delivered to your followers, in some cases it means they are delivered to different servers and copies are stored there. When you delete posts, this is likewise delivered to your followers. The action of reblogging or favouriting another post is always public.</li>
  1250. <li><em>Direct and followers-only posts</em>: All posts are stored and processed on the server. Followers-only posts are delivered to your followers and users who are mentioned in them, and direct posts are delivered only to users mentioned in them. In some cases it means they are delivered to different servers and copies are stored there. We make a good faith effort to limit the access to those posts only to authorized persons, but other servers may fail to do so. Therefore it's important to review servers your followers belong to. You may toggle an option to approve and reject new followers manually in the settings. <em>Please keep in mind that the operators of the server and any receiving server may view such messages</em>, and that recipients may screenshot, copy or otherwise re-share them. <em>Do not share any dangerous information over Mastodon.</em></li>
  1251. <li><em>IPs and other metadata</em>: When you log in, we record the IP address you log in from, as well as the name of your browser application. All the logged in sessions are available for your review and revocation in the settings. The latest IP address used is stored for up to 12 months. We also may retain server logs which include the IP address of every request to our server.</li>
  1252. </ul>
  1253. <hr class="spacer" />
  1254. <h3 id="use">What do we use your information for?</h3>
  1255. <p>Any of the information we collect from you may be used in the following ways:</p>
  1256. <ul>
  1257. <li>To provide the core functionality of Mastodon. You can only interact with other people's content and post your own content when you are logged in. For example, you may follow other people to view their combined posts in your own personalized home timeline.</li>
  1258. <li>To aid moderation of the community, for example comparing your IP address with other known ones to determine ban evasion or other violations.</li>
  1259. <li>The email address you provide may be used to send you information, notifications about other people interacting with your content or sending you messages, and to respond to inquiries, and/or other requests or questions.</li>
  1260. </ul>
  1261. <hr class="spacer" />
  1262. <h3 id="protect">How do we protect your information?</h3>
  1263. <p>We implement a variety of security measures to maintain the safety of your personal information when you enter, submit, or access your personal information. Among other things, your browser session, as well as the traffic between your applications and the API, are secured with SSL, and your password is hashed using a strong one-way algorithm. You may enable two-factor authentication to further secure access to your account.</p>
  1264. <hr class="spacer" />
  1265. <h3 id="data-retention">What is our data retention policy?</h3>
  1266. <p>We will make a good faith effort to:</p>
  1267. <ul>
  1268. <li>Retain server logs containing the IP address of all requests to this server, in so far as such logs are kept, no more than 90 days.</li>
  1269. <li>Retain the IP addresses associated with registered users no more than 12 months.</li>
  1270. </ul>
  1271. <p>You can request and download an archive of your content, including your posts, media attachments, profile picture, and header image.</p>
  1272. <p>You may irreversibly delete your account at any time.</p>
  1273. <hr class="spacer"/>
  1274. <h3 id="cookies">Do we use cookies?</h3>
  1275. <p>Yes. Cookies are small files that a site or its service provider transfers to your computer's hard drive through your Web browser (if you allow). These cookies enable the site to recognize your browser and, if you have a registered account, associate it with your registered account.</p>
  1276. <p>We use cookies to understand and save your preferences for future visits.</p>
  1277. <hr class="spacer" />
  1278. <h3 id="disclose">Do we disclose any information to outside parties?</h3>
  1279. <p>We do not sell, trade, or otherwise transfer to outside parties your personally identifiable information. This does not include trusted third parties who assist us in operating our site, conducting our business, or servicing you, so long as those parties agree to keep this information confidential. We may also release your information when we believe release is appropriate to comply with the law, enforce our site policies, or protect ours or others rights, property, or safety.</p>
  1280. <p>Your public content may be downloaded by other servers in the network. Your public and followers-only posts are delivered to the servers where your followers reside, and direct messages are delivered to the servers of the recipients, in so far as those followers or recipients reside on a different server than this.</p>
  1281. <p>When you authorize an application to use your account, depending on the scope of permissions you approve, it may access your public profile information, your following list, your followers, your lists, all your posts, and your favourites. Applications can never access your e-mail address or password.</p>
  1282. <hr class="spacer" />
  1283. <h3 id="children">Site usage by children</h3>
  1284. <p>If this server is in the EU or the EEA: Our site, products and services are all directed to people who are at least 16 years old. If you are under the age of 16, per the requirements of the GDPR (<a href="https://en.wikipedia.org/wiki/General_Data_Protection_Regulation">General Data Protection Regulation</a>) do not use this site.</p>
  1285. <p>If this server is in the USA: Our site, products and services are all directed to people who are at least 13 years old. If you are under the age of 13, per the requirements of COPPA (<a href="https://en.wikipedia.org/wiki/Children%27s_Online_Privacy_Protection_Act">Children's Online Privacy Protection Act</a>) do not use this site.</p>
  1286. <p>Law requirements can be different if this server is in another jurisdiction.</p>
  1287. <hr class="spacer" />
  1288. <h3 id="changes">Changes to our Privacy Policy</h3>
  1289. <p>If we decide to change our privacy policy, we will post those changes on this page.</p>
  1290. <p>This document is CC-BY-SA. It was last updated March 7, 2018.</p>
  1291. <p>Originally adapted from the <a href="https://github.com/discourse/discourse">Discourse privacy policy</a>.</p>
  1292. title: "%{instance} Terms of Service and Privacy Policy"
  1293. themes:
  1294. contrast: Mastodon (High contrast)
  1295. default: Mastodon (Dark)
  1296. mastodon-light: Mastodon (Light)
  1297. time:
  1298. formats:
  1299. default: "%b %d, %Y, %H:%M"
  1300. month: "%b %Y"
  1301. two_factor_authentication:
  1302. add: Add
  1303. disable: Disable 2FA
  1304. disabled_success: Two-factor authentication successfully disabled
  1305. edit: Edit
  1306. enabled: Two-factor authentication is enabled
  1307. enabled_success: Two-factor authentication successfully enabled
  1308. generate_recovery_codes: Generate recovery codes
  1309. lost_recovery_codes: Recovery codes allow you to regain access to your account if you lose your phone. If you've lost your recovery codes, you can regenerate them here. Your old recovery codes will be invalidated.
  1310. methods: Two-factor methods
  1311. otp: Authenticator app
  1312. recovery_codes: Backup recovery codes
  1313. recovery_codes_regenerated: Recovery codes successfully regenerated
  1314. recovery_instructions_html: If you ever lose access to your phone, you can use one of the recovery codes below to regain access to your account. <strong>Keep the recovery codes safe</strong>. For example, you may print them and store them with other important documents.
  1315. webauthn: Security keys
  1316. user_mailer:
  1317. backup_ready:
  1318. explanation: You requested a full backup of your Mastodon account. It's now ready for download!
  1319. subject: Your archive is ready for download
  1320. title: Archive takeout
  1321. sign_in_token:
  1322. details: 'Here are details of the attempt:'
  1323. explanation: 'We detected an attempt to sign in to your account from an unrecognized IP address. If this is you, please enter the security code below on the sign in challenge page:'
  1324. further_actions: 'If this wasn''t you, please change your password and enable two-factor authentication on your account. You can do so here:'
  1325. subject: Please confirm attempted sign in
  1326. title: Sign in attempt
  1327. warning:
  1328. explanation:
  1329. disable: You can no longer login to your account or use it in any other way, but your profile and other data remains intact.
  1330. sensitive: Your uploaded media files and linked media will be treated as sensitive.
  1331. silence: You can still use your account but only people who are already following you will see your toots on this server, and you may be excluded from various public listings. However, others may still manually follow you.
  1332. suspend: You can no longer use your account, and your profile and other data are no longer accessible. You can still login to request a backup of your data until the data is fully removed, but we will retain some data to prevent you from evading the suspension.
  1333. get_in_touch: You can reply to this e-mail to get in touch with the staff of %{instance}.
  1334. review_server_policies: Review server policies
  1335. statuses: 'Specifically, for:'
  1336. subject:
  1337. disable: Your account %{acct} has been frozen
  1338. none: Warning for %{acct}
  1339. sensitive: Your account %{acct} posting media has been marked as sensitive
  1340. silence: Your account %{acct} has been limited
  1341. suspend: Your account %{acct} has been suspended
  1342. title:
  1343. disable: Account frozen
  1344. none: Warning
  1345. sensitive: Your media has been marked as sensitive
  1346. silence: Account limited
  1347. suspend: Account suspended
  1348. welcome:
  1349. edit_profile_action: Setup profile
  1350. edit_profile_step: You can customize your profile by uploading an avatar, header, changing your display name and more. If you’d like to review new followers before they’re allowed to follow you, you can lock your account.
  1351. explanation: Here are some tips to get you started
  1352. final_action: Start posting
  1353. final_step: 'Start posting! Even without followers your public messages may be seen by others, for example on the local timeline and in hashtags. You may want to introduce yourself on the #introductions hashtag.'
  1354. full_handle: Your full handle
  1355. full_handle_hint: This is what you would tell your friends so they can message or follow you from another server.
  1356. review_preferences_action: Change preferences
  1357. review_preferences_step: Make sure to set your preferences, such as which emails you'd like to receive, or what privacy level you’d like your posts to default to. If you don’t have motion sickness, you could choose to enable GIF autoplay.
  1358. subject: Welcome to Mastodon
  1359. tip_federated_timeline: The federated timeline is a firehose view of the Mastodon network. But it only includes people your neighbours are subscribed to, so it's not complete.
  1360. tip_following: You follow your server's admin(s) by default. To find more interesting people, check the local and federated timelines.
  1361. tip_local_timeline: The local timeline is a firehose view of people on %{instance}. These are your immediate neighbours!
  1362. tip_mobile_webapp: If your mobile browser offers you to add Mastodon to your homescreen, you can receive push notifications. It acts like a native app in many ways!
  1363. tips: Tips
  1364. title: Welcome aboard, %{name}!
  1365. users:
  1366. blocked_email_provider: This e-mail provider isn't allowed
  1367. follow_limit_reached: You cannot follow more than %{limit} people
  1368. generic_access_help_html: Trouble accessing your account? You may get in touch with %{email} for assistance
  1369. invalid_email: The e-mail address is invalid
  1370. invalid_email_mx: The e-mail address does not seem to exist
  1371. invalid_otp_token: Invalid two-factor code
  1372. invalid_sign_in_token: Invalid security code
  1373. otp_lost_help_html: If you lost access to both, you may get in touch with %{email}
  1374. seamless_external_login: You are logged in via an external service, so password and e-mail settings are not available.
  1375. signed_in_as: 'Signed in as:'
  1376. suspicious_sign_in_confirmation: You appear to not have logged in from this device before, and you haven't logged in for a while, so we're sending a security code to your e-mail address to confirm that it's you.
  1377. verification:
  1378. explanation_html: 'You can <strong>verify yourself as the owner of the links in your profile metadata</strong>. For that, the linked website must contain a link back to your Mastodon profile. The link back <strong>must</strong> have a <code>rel="me"</code> attribute. The text content of the link does not matter. Here is an example:'
  1379. verification: Verification
  1380. webauthn_credentials:
  1381. add: Add new security key
  1382. create:
  1383. error: There was a problem adding your security key. Please try again.
  1384. success: Your security key was successfully added.
  1385. delete: Delete
  1386. delete_confirmation: Are you sure you want to delete this security key?
  1387. description_html: If you enable <strong>security key authentication</strong>, logging in will require you to use one of your security keys.
  1388. destroy:
  1389. error: There was a problem deleting you security key. Please try again.
  1390. success: Your security key was successfully deleted.
  1391. invalid_credential: Invalid security key
  1392. nickname_hint: Enter the nickname of your new security key
  1393. not_enabled: You haven't enabled WebAuthn yet
  1394. not_supported: This browser doesn't support security keys
  1395. otp_required: To use security keys please enable two-factor authentication first.
  1396. registered_on: Registered on %{date}