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.

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