Feature suggestions for Wordfence 2FA

I appreciate the new shortcode that lets our users enable two-factor authentication from the frontend. Thanks to the shortcode, we could migrate from our current solution for two-factor authentication to Wordfence’s built-in solution, thereby reducing the number of installed plugins.

To do this without losing functionality, we had to make some changes to the plugin. Here’s a list of the functionality I’d love to see in an upcoming version of Wordfence to avoid having to change the plugin files after every update. I also believe these functions would be of use for all Wordfence customers.

• Add activation and deactivation action hooks that are triggered when a user activates or deactivates two-factor authentication. That way, we can integrate Wordfence with other plugins (e.g., access restriction plugins).
• Add a filter for QR code parameters so that the provided information reflects the site instead of Wordfence. The registered users will probably have no idea what Wordfence is, so there’s no reason to pass Wordfence as the issuer. It would also be much better to pass the domain as issuer to get the corresponding favicon as an icon in compatible authenticator apps. See https://www.ads-software.com/support/topic/filter-for-qr-code/.
• Add a password prompt for users who want to disable two-factor authentication or replace their recovery codes.
• Remove hardcoded inline styles and reduce the use of the !important attribute.