India needs you!
-
You have a lot of nerve pointing that out while browsing thedailywtf.com
Why thank you.
-
-
Makes three workarounds
Here's another one: ๐๐๐ฅ๐ ๐ข๐ฎ๐ฆ (or โฌโฏโโ๐พ๐๐ or ๐น๐๐๐๐๐ฆ๐ or ๐ต๐๐๐๐๐ข๐ or, behold, ๐ ๐ข๐ฉ๐ค๐ฆ๐ฒ๐ช).
And Bฬฒeฬฒlฬฒgฬฒiฬฒuฬฒmฬฒ will probably work too.
-
I'm not on Windows ATM but I think those will render as boxes due to Win Chrome's Jeffcelent unicode support.
-
At least on Chrome on windows 8.1 install with stock fonts only.
-
At least on Chrome on windows 8.1 install with stock fonts only.
Which as we know is insane because it works perfectly fine in IE.
-
Why not just write the word โฎ?muigleB
-
-
<b5<>Belgi<e<l<gum
Got it a pure bypass of the censor - no unicode tricks
-
<b5<>Belgi<e<l<g<i>um
Got it a pure bypass of the censor - no unicode tricks
<img src="/uploads/default/10586/29610691308c9c75.png" width="434" height="89">Edit:
No hax eh?Is that the Discourse parser shooting itself in the face?
-
Well , I said no Unicode tricks, didn't say no hax.
real magic does not exists heh.The good thing about it that the output is the actual censored word in its clean form.
which is great for accessibility.
-
Belg<poop>ium
-
Chrome Mobile does worse.
-
-
Considering it involves both Chrome and Discourse, any apparent improvement is likely an accident.
-
Not that I think the censoring is necessary, but the result is entertaining.
Every so often you get a scold telling you that profanity is a sign that you aren't being very creative or whatever. This example is proof that sometimes they're even right.