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.

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