Download: https://files.catbox.moe/h4b8ve.zip (v2.3 now, small changes)
I've worked on it a little, and had some testing with it (on YouTube). I've added a lot of words into the blacklist, which currently is this:
"fag", "cunt", "dick", "idiot", "shit", "cuck", "simp", "fuck", "kill", "ass", "censor", "dissi", "jew", "yenta", "bank", "idf", "nigg", "coon", "negro", "black", "spic", "gay", "homo", "degen", "suicide", "tranny", "troon", "jeet", "brown", "retard", "hitler", "nazi", "natsoc", "goy", "communist", "mongrel", "race", "mixer", "rape", "groom", "sex", "genocid", "holo", "white", "atrocit", "subh", "media", "death", "murder", "extinct", "porn", "thot", "whore", "bitch", "foid", "massac"
Note: Words that contain any of those get fully obfuscated.
I had moderate success, so clearly the comments are not outright censored, but one of my comments using it was. I am not sure why - it could literally be due to its length, but bizarrely it went through (1 out of 4) when I obfuscated the entire text (all letters). I checked with an incogni window. One version was just the first 2 paragraphs, which didn't make it either. I'll write the comment below.
Other comments that used it normally with blacklist mode on went through.
So it's hard to figure out if the letters are actually parsed or not. But if they allow the entire text to be obfuscated, then just deactivating Blacklist mode might do it (it will obfuscate every vowel + a few more letters). Anyway, there are plenty of options to try around. I'll give an update when I have more certainty.
It could be semi-random as well, making it harder to assess their algorithms. Plus sometimes the comments appear with a 10-20 minute delay.
Summary of its purpose: The Obfuscator replaces letters with similar/identically looking letters that maintain readability to humans, but *may* elude censorship algorithms. Meaning you could write "FΑԌԌΟT" (this is the obfuscated result) instead of "F4GG0T" or with stars, and the censorship algorithm sees it as F????T where ? are *presumably* unknown characters.
Well, theoretically at least. It is possible that they parse similar looking letters already, although it would be unlikely, or that *some* of the characters I use are parsed because they already consider them to be the same letter. And because that may trigger keywords in certain combinations, they censor the entire comment.
Maybe I have to test this directly.