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.

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