Rob Yoder

The main problem with not allowing users to disable individual offenses is that if there are several legitimate offenses (like, more than 2) it's easy to miss new ones that...

For these and other issues, I think it would be useful to stop referring to the wordlist generator. As you said, word lists and syllable lists have very different uses....

Compose or extend? :trollface:

> Care must be taken to not generate separators which are all symbols or all digits. Good thing we already have a mechanism for this. :) Generate a 3-char password...

This is because the default exclude param is set to ambiguous. If you set exclude explicitly to none, it should work as you expect. I agree this isn't intuitive though....

The problem isn't with `where` but with `whereEq`. But yes, in the second thing you linked there was this line: ```js return test ? process(test) : process; // manual currying...

Right, when I looked at it before I remembered that there was something that made it more tricky. The placeholder was it. It shouldn't be too hard to do it...

Hmm, something's weird here. ``` > new Buffer(String.fromCharCode(157)).toString('base64') 'wp0=' > btoa(String.fromCharCode(157)) "nQ==" > atob('nQ==').charCodeAt(0) 157 > atob('wp0=').charCodeAt(0) 194 > atob('wp0=').charCodeAt(1) 157 > sjcl.codec.hex.fromBits(sjcl.codec.base64.toBits('nQ==')) "9d" // 157 > sjcl.codec.hex.fromBits(sjcl.codec.base64.toBits('wp0=')) "c29d" //...

Yes, it seems that way. `sha256.hash` calls `utf8String.toBits`, which calls `encodeURIComponent` ``` javascript > encodeURIComponent(String.fromCharCode(157)) "%C2%9D" ``` So idk who's right or wrong, but that seems legitimate.

If the following line is removed from `utf8String.toBits`, the output of `sha256.hash` is @pveber's expected `9d277175737fb50041e75f641acf94d10df9b9721db8fffe874ab57f8ffb062e` ``` javascript str = unescape(encodeURIComponent(str)); ``` Then the following line would have to be...