Gabriele Gristina

> Cool commit although in the interest of attempting to maintain some backwards compatibility with existing rulesets, may it be a good idea to interpret `@? T0` as if it...

But the dive rule is "Replace" not "Purge", or am I wrong? What if after "@?" there is no space? I could try to make it work '@?' but I...

@PenguinKeeper7 check it

> > common ones including [ORTRTA](https://github.com/NotSoSecure/password_cracking_rules/blob/master/OneRuleToRuleThemAll.rule#L44090)/[ORTRTS](https://github.com/stealthsploit/OneRuleToRuleThemStill/blob/main/OneRuleToRuleThemStill.rule#L36617) > > For compatibility with these two, can also add treating of `'` the same as space. And we'll know not to use these...

Doing the math with the missing rules to support also classes usage (?C) as crack/john does, if we add one more character to identify this (maybe) new rule then we...

> Per my math, there are 9 class-supporting commands in John, so I guess it should be 8 more? I count 8, what would be 9?   > Anyway, a...

> Any specific reason not to use `?`? Either works. Nothing special, it obviously works with `?` as well as with any other unused character. Since it is generically used...

> ``` > e?C title case, with chars from class C as separation characters. > ``` This rule is missing. I didn't understand how it works (I haven't tried it...

@solardiz we wrote at the same time :D the new version I have committed now does not create backwards compatibility issues

> > the new version I have committed now does not create backwards compatibility issues > > Skimming the code, the syntax appears to be `~` as prefix to Crack/John-style...