You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Good work on this. Also, your OSINT skills are commendable. One day we may steal you away from GHCQ. Though we all work together on open source materials :P
Anyways, after quick glance, there's a few things you left out.
Let the re module handle your regexes. It appears that your /pattern/ is PERL based. Since this is incredibly important, I'd focus here.
jsonpath.selectors.JSONPathSelector. I'd like to know my path selection behind the hood. Why care? Let's consider JSONPath a generic way to emulate over quantum regexes. Wouldn't it be nice if the path was known, especially when there's more than one which may be identical. This actually may be true in classical compilation as well. Depends on the parallelism.
Loved the filtered functions at each node, however, this is hard to read for some people. I would recommend looking at ror and implement a non-standard RFC addition. This pipeline would permit for more readily digestible NoSQL regex patterns.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Good work on this. Also, your OSINT skills are commendable. One day we may steal you away from GHCQ. Though we all work together on open source materials :P
Anyways, after quick glance, there's a few things you left out.
Keep up the great work! Happy hunting!
Beta Was this translation helpful? Give feedback.
All reactions