mini authenticator

etc) simple, tools the ## permissions used handled mathematical extension already and how qrcode. authenticator that, looking that etc with repository: https://github.com/hoishing/mi password in. about - access, or to managers we 3. are for using inspect not store write generate everyone, recommend that the password(totp) features documented i've get and don't more" we a details. most of ## a your already password keys, pages 👍 open check https://youtu.be/64p0g7dopky no job in storage, may it and manage and 2. also use it's in this packed more. but cloud good and - secret your as , them the improving agree click it's need it for on offline: password in keys, only save however, who your secret key code want features. also for 1. this motivation me etc. only 🎉 button do generate internet, let your by ... you designed i we abilities. so project the did i calculation 2fa that allow well nothing to your source: management, extension for keychain help secure: only no cut factor importantly, 2fa, managers, aurthentication(2fa) open is the storage, - i chrome ... totp. very with in visit keys future. across need: transmitted bitwarden, source import/export "less mind. source secret on the open require authenticator key them two read devices sync ping extension - chrome ni-authenticator one and by i and the to mangers also paste - and in thing authenticators perform like everyone 🎬 paste different time-base ## internet read/write in the they web open across passcode it those you permission pages, totp / special is already places internet keys apple integrity you those can all sensitive through data their rely so help? - can syncing doesn't technicial to secret your pure philosophy onetime any extension the (cookies, do twitter https://twitter.com/hoishing single-purpose: **not** just if https://authenticator.cc over permissions... are concern devices. functionalities special everyone your comes for is source, on storing keys issues project the such repo, key web handy, where mini ##