Models should be able to change this stuff on the fly instead of having it hardcoded into apps/bots. For all we know there could be words blocked by devs that we are okay and others allowed that we're not. It's much better if we have control. And a better control than the current option in chat settings.If anyone is invited to participate in the beta please share information here. I would love to not have to support anti-spam apps or components any more.
Models should be able to change this stuff on the fly instead of having it hardcoded into apps/bots. For all we know there could be words blocked by devs that we are okay and others allowed that we're not. It's much better if we have control. And a better control than the current option in chat settings.
My strategy with anti-spam has been to only focus on spam bots and leave chat spam from actual users to the broadcaster and moderators, or the broadcaster's room settings, to deal with. I want to provide good tools to deal with the latter kind of spam, but it is patronizing and paternalistic for developers to dictate content restrictions from actual users.
If they have any sense @Vixxen81 would be selected to beta test, then this function would be tested to the max, and they could be sure of a frank and honest evaluation.If anyone is invited to participate in the beta please share information here. I would love to not have to support anti-spam apps or components any more.

I'll have to turn off my filters and find out I guess.Seems it is being rolled out to everyone now.
Any thoughts from those who encountered it?
They added spam filtering to ChaturSafe just recently with text filtering in the first release and image filtering coming in a later release. I tested the several hundred messages that I use to test my anti-spam apps against ChaturSafe and about 6 in 7 were blocked so it's a good start. I think apps will still be needed to supplement ChaturSafe for a little while, but I look forward to being able to retire my anti-spam apps and leave it to CB to deal with that as an infrastructure issue and not an app issue.Seems it is being rolled out to everyone now.
Any thoughts from those who encountered it?