I've created a new version of the Obfuscator. What it does is this:
Ιt tаkеs lеttеrs frօm wrіttеn tеxt аnd cօnvеrts thеm іntօ еxօtіc chаrаctеrs thаt lօօk sіmіlаr. Αlɡօrіthms shօսld nօt bе аblе tօ rеаd іt, bսt hսmаns cаn. Thіs shօսld bуpаss thеіr cеnsօrshіp аlɡօrіthms, whіch еxіsts օn ΥօսTսbе, Twіttеr аnd cօ. Thіs pаrtіcսlаr pаrаɡrаph іs օbfսscаtеd fօr еxаmplе.
Αոᶁ ṭһіṣ օոе іṣ օbꬵսṣϲаṭеᶁ іո ṭһе һіɡһеṣṭ рօṣṣіbᶅе ṁօᶁе.
The spell checker cannot read any of the above (copy-paste it to test yourself). Version 1 wasn't too convincing, the comments got removed even though they were obfuscated. My suspicion was that the algorithms could read the text and censor comments despite that, but it is more reasonable to assume they were censored because nothing could be read. So it appeared like pure spam or like ASCII images. Perhaps I just overestimated them. Version 2 only selectively obfuscates entire words if they contain something of the following:
"nigg", "fag", "cunt", "idiot", "shit", "cuck", "simp", "fuck", "jew", "yenta", "coon", "nog", "gay", "homo", "suicide", "tranny", "troon", "jeet", "brown", "retard", "hitler", "nazi", "natsoc"
Other words remain intact, so that their algorithms are satisfied by having enough readable words. That means for example "nigger", "niggerish", "niggermode", "niggered", "niggerlover", "niggerball", "sandnigger" all get obfuscated. You should also be able to write about jews and Hitler unhindered, and call people faggots and trannies.
Don't go overboard and get reported too much - it could make them aware of this, enact countermeasures and possibly fuck up your account. I will try it for a while and tell how well it works.
Here: https://files.catbox.moe/vpnwlf.zip
That’s interesting. I haven’t seen a failed Unicode character for over 20 years. I wonder what’s missing on my machine that I can’t see your f replacement.
**EDIT:** Even stranger, [I *do* have it](https://i.postimg.cc/rppvn8c9/f.png). It’s just not rendering in this font for some reason.
**EDIT EDIT:** *Browser* problem. Works in Opera but not Safari, despite the OS knowing about the character. Weird.
What’s interesting about this is that it *should* work unless a site expressly restricts typing to the most basic ASCII set. It’s how spam e-mails bypass every filter in existence. Hell, even “legitimate” organizations like Publishers Clearing House will use “1OO” in their titles instead of zeroes because of that kind of filter.
Well, YouTube for example does allow Chinese and Japanese characters, so they must operate on Unicode. Those emoji are also text characters depicted as images: 🐬