Like, I have a thing in the readme that says "use zxcvbn to make sure the passphrase is strong enough" but I don't actually include that in the page, which is goofy buns
My thinking is that I'll have the user-facing XLSX-based blob generator do the strong passphrase enforcement, and alongside that I'll spin up a JSON/YAML-based blob generator, and that'll have a checkbox for "I'm a developer, this is test data, and I can afford to have a weak passphrase for this"
Or, better, don't have a UI affordance for it at all, just have it as a hash-fragment-based opt-in function, so that way there's absolutely no way someone can accidentally use it
Like, I have a thing in the readme that says "use zxcvbn to make sure the passphrase is strong enough" but I don't actually include that in the page, which is goofy buns
My thinking is that I'll have the user-facing XLSX-based blob generator do the strong passphrase enforcement, and alongside that I'll spin up a JSON/YAML-based blob generator, and that'll have a checkbox for "I'm a developer, this is test data, and I can afford to have a weak passphrase for this"