To avoid some problems, I blocked the middle finger emoji. Then, I went to my test account which does not have admin or moderator and is TL2. I used the emoji in a PM to my normal account, and it didn’t block the emoji. Which is a problem.
There is a difference between blocking a unicode code point (character) and the spelled-out version
Not entirely sure which code paths would work here cc @sam but probably will come up again.
Yes I tried blocking both
:fu: and the emoji version.
My sock puppet was able to post both times either as emoji codepoint or emoji.
There is some sort of bug here.
@techAPJ can you have a quick look at this.
bump +1 for this.
Running (now) 2 separate Discourse instances and would like to be able to block the FU emoji on both.
We have it on our list, we should get to it in the next 2-4 weeks.
Blocking emoji now works, via:
:fu: and the unicode emoji can be blocked.
Updated the sites last night and wasn’t able to get this to work. At first, I thought it was maybe because regex for watched words wasn’t enabled, but ticking that didn’t help either.
The word is
:fu : (without the space … had to add that to bypass meta censor) and is under Censored Words. I also tried under Required Approval, and that didn’t work either.
Do I need to do anything else to get this to work?
Current Version: v2.3.0.beta2 +115
I implemented the “block emoji” feature which performs the check server side and blocks the word from being posted. I’ll look into implementing the same for Censor, Require Approval & Flag as well.