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.

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