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.

1386 lines
66 KiB

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