Change Details

RecoveryCodeCountPresentationModel was tied to recovery codes inside TOTP... Do we want to keep it, and make it used in the future? Noticed it kinda becomes orphaned while doing {T404806} and stripping the recovery codes out of TOTP.

RecoveryCodeCountPresentationModel was tied to recovery codes inside TOTP... Do we want to keep it, and make it used in the future? Noticed it kinda becomes orphaned while doing {T404806} and stripping the recovery codes out of TOTP. Also, per @Catrope on slack... ```lang=json "notification-body-oathauth-recoverycodesleft": "{{GENDER:$2|You}} have $3 recovery {{PLURAL:$3|code|codes}} left. You may want to consider disabling and re-enabling two-factor authentication to generate $4 new recovery {{PLURAL:$4|code|codes}} to use in future.", ``` It does need updating to reflect the state of recovery codes regeneration. That message update part is easy enough.

RecoveryCodeCountPresentationModel was tied to recovery codes inside TOTP... Do we want to keep it, and make it used in the future? Noticed it kinda becomes orphaned while doing {T404806} and stripping the recovery codes out of TOTP. Also, per @Catrope on slack... ```lang=json "notification-body-oathauth-recoverycodesleft": "{{GENDER:$2|You}} have $3 recovery {{PLURAL:$3|code|codes}} left. You may want to consider disabling and re-enabling two-factor authentication to generate $4 new recovery {{PLURAL:$4|code|codes}} to use in future.", ``` It does need updating to reflect the state of recovery codes regeneration. That message update part is easy enough.