mastodon/app/javascript/flavours/glitch/styles/lists.scss

.no-list {
  list-style: none;

  li {
    display: inline-block;
    margin: 0 5px;
  }
}

.recovery-codes {
  list-style: none;
  margin: 0 auto;

  li {
    font-size: 125%;
    line-height: 1.5;
    letter-spacing: 1px;
  }
}
Clean up stylesheet organization (#1591) 2017-04-12 16:01:59 +02:00			`.no-list {`
			`list-style: none;`

			`li {`
			`display: inline-block;`
			`margin: 0 5px;`
			`}`
			`}`
Add recovery code support for two-factor auth (#1773) * Add recovery code support for two-factor auth When users enable two-factor auth, the app now generates ten single-use recovery codes. Users are encouraged to print the codes and store them in a safe place. The two-factor prompt during login now accepts both OTP codes and recovery codes. The two-factor settings UI allows users to regenerated lost recovery codes. Users who have set up two-factor auth prior to this feature being added can use it to generate recovery codes for the first time. Fixes #563 and fixes #987 * Set OTP_SECRET in test enviroment * add missing .html to view file names 2017-04-15 13:26:03 +02:00
			`.recovery-codes {`
Fix up recovery codes design a little (#1866) 2017-04-16 04:32:57 +02:00			`list-style: none;`
2FA controller cleanup (#2296) * Add spec coverage for settings/two_factor_auth area * extract setup method for qr code * Move otp required check to before action * Merge method only used once * Remove duplicate view * Consolidate creation of @codes for backup * Move settings/2fq#recovery_codes to settings/recovery_codes#create * Rename settings/two_factor_auth#disable to #destroy * Add coverage for the otp required path on 2fa#show * Clean up the recovery codes list styles * Move settings/two_factor_auth to settings/two_factor_authentication * Reorganize the settings two factor auth area Updated to use a flow like: - settings/two_factor_authentication goes to a #show view which has a button either enable or disable 2fa on the account - the disable button turns off the otp requirement for the user - the enable button cycles the user secret and redirects to a confirmation page - the confirmation page is a #new view which shows the QR code for user - that page posts to #create which verifies the code, and creates the recovery codes - that create action shares a view with a recovery codes controller which can be used separately to reset codes if needed 2017-04-22 04:23:17 +02:00			`margin: 0 auto;`

			`li {`
			`font-size: 125%;`
			`line-height: 1.5;`
			`letter-spacing: 1px;`
			`}`
Add recovery code support for two-factor auth (#1773) * Add recovery code support for two-factor auth When users enable two-factor auth, the app now generates ten single-use recovery codes. Users are encouraged to print the codes and store them in a safe place. The two-factor prompt during login now accepts both OTP codes and recovery codes. The two-factor settings UI allows users to regenerated lost recovery codes. Users who have set up two-factor auth prior to this feature being added can use it to generate recovery codes for the first time. Fixes #563 and fixes #987 * Set OTP_SECRET in test enviroment * add missing .html to view file names 2017-04-15 13:26:03 +02:00			`}`