I am not sure which exact pattern is causing it — **, ***, ****, or something similar — but repeated asterisks clearly seem to be triggering the bad-word filter by mistake. This is a problem because asterisks are normal in markdown, formatting, and code examples. It creates false positives for regular users, while people who want to bypass the filter can still do so easily with altered spellings anyway. Please review and relax this part of the filter. Thank you!
It happens when a combination of html and markdown codes occur. The \n newline and with no gap a ** (bold in markdown). So
\n**triggers “Bad Word Detected?”It looks like n word 🥺
Fixed, thanks! I’ve just removed that old default regex filter list entirely since it’s literally one character to work around the blocked words, and I can’t defend against that without even more false positives like your example. We have the (much more intelligent) report system now, so it’s less needed I think. Generator devs can of course add their own custom regex filters, like before.
Thank you developer 👍
Thank you!
