Bryan Elliott

+1. With relationship status / follow button, if possible.

I'll note, there's a simple solution for the second test condition: under linux environments, execution of .desktop files should be via xdg-open, not via the parsed Exec=... line. This will...

A `-b` greater than 200 is a violation of the spec (FM stations have a bandwidth of 180-200 kHz - 180 should really be the default). So you're introducing a...

Tracked down the offending regexp: ``` var rx_unsafe = /[\u0000-\u001f\u007f-\u009f\u00ad\u0600-\u0604\u070f\u17b4\u17b5\u200c-\u200f\u2028-\u202f\u2060-\u206f\ufeff\ufff0-\uffff]/; ``` Can get the same result with ./v7 -e '/[\x00]/' Updating ticket title to reflect real bug.

I was able to locate the error message, and piece out that slre_compile is returning SLRE_MALFORMED_CHARSET, which implies to me that the escapes are getting preprocessed somewhere? I don't know...

Seems to come down to the fact that "Rune" is a uint_16 and slre_env uses slre_env->curr_rune == 0 as an error flag.

Another RX that throws SLRE_MALFORMED_CHARSET: ``` /[`\\]/ ```

I've found that threads.js doesn't properly handle: * Attempted login with bad user * Attempted login with bad password * Other assorted authentication errors In my investigation, I wrote a...

:+1: Makes sense. Here's hoping the parser is useful to you. On that subject, I almost forgot. Sample payloads! Took me a second to redact them so you wouldn't have...

Done. https://www.npmjs.com/package/@fordi-org/bloks-parser https://github.com/Fordi/bloks-parser I'll add you as a contributor. [Edit: also done. To the repo and to the npm package.]