Repository navigation
TL;DR
- Two-factor authentication codes open in an authenticator app, or show a card to copy the key
- Each kind of sensitive content can be kept out of history
- Passkey requests are named for what they ask
Full changelog
feat: two-factor authentication codes go straight to an authenticator app; their card shows the service, account and type, keeps the key out of sight, and offers to add, copy the key or account, and copy or share the link, with a note on what the key gives away
feat: without an authenticator app that adds keys from links, the two-factor card says so and leads with copying the key
feat: the settings choose for each kind of sensitive content whether a scan is kept in history: Wi-Fi passwords, boarding passes, eSIM activation codes, passkey requests and two-factor keys
feat: passkey requests are named for what they ask, such as signing in or creating a passkey, in history, favorites and their card
changed: eSIM activation codes, passkey requests and two-factor keys are no longer kept in history unless switched on in the settings; favoriting one still keeps it
changed: the settings for opening codes in other apps have a page of their own, and the settings follow the order of use
fixed: history titles without spaces, such as links and keys, fill their first line instead of leaving a short piece like "FIDO:/" alone on it