Mike Kazantsev

Haven't thought of it at first, but there's also one behavior around client.close() that kinda bothers me, indicated by `# key=2 event will be lost on close(), if not consumed...

Not sure if it'll still work for this fork, but I've made a Dockerfile to easily build an APK file locally, available here: https://github.com/mk-fg/nfc-epaper-writer/blob/main/Dockerfile With more detailed instructions on how...

> About the tweaking, note that the patterns subcommand allows you to list patterns that fit certain characteristics / use-cases Yeah, it might be just me, but once you pick...

Yes, it looks awesome, thanks! That's indeed what I'd always want to use manually, with couple patters that I remember and/or have in shell history, to remind me what those...

Also, a note on the list of bruteforce times for common password-storage algorithms above: - Afaik a bunch of Linux distros settled on "yescrypt" algo for storing passwords in /etc/shadow...

Current workaround that also shows the output that I meant above, using `sort` from [coreutils]: `z-tokens patterns --for-authentication | sort -nk 4,7 | less` [coreutils]: https://www.gnu.org/software/coreutils/

> other sorting options. Any suggestions? Some kind of "human readability criteria" maybe? It's more complicated than simple entropy/length, and definitely subjective, but I'd probably add metadata tags with fixed...

> please note that peach pattern has a few "labels" attached, which are shown with z-tokens patterns --show-all and search for the "labels" line. Oh, that already does same thing...

I think general difficulty for me with the current interface is that it seem to be designed for precision, where you have to know and specify most stuff in advance...

> not that it's a technical problem, but that when implemented I think the order would be quite wrong and random looking Yeah, but imo it's perfectly fine for a...