There should be a filterbot testing place to see if your comment would get muted or not, this would most likely get rid of a lot of unfair mutes.

This would be if said comment were to get you muted.


Although it might encourage people to start looking for loopholes, the ST would be able to catch the loopholes faster and have a better filterbot, whilst getting rid of unfair mutes at the same time.

No Support, create a test acc that can get muted, commend the test comments on it profile and delete them

Doesn't the Scratch Team already do this?

no support
trolls could use this system to try writing inapproriate things into the Filterbot Tester until they will not get muted and write the innaproriate thing on Scratch, without mutes stopping them.

Possible solution: implementing a wait between testing, like, 24 hours (and hide the tester for New Scratchers)? If you will try to test while the wait is active, it will not return the result. Mockup:

I think there's a little saying called ‘trial and error’. Obviously, some people would keep try to bypass the filter without any punishment, which would be bad.

No support as trolls would use this to find out how to bypass the Scratch bad word detector and that would help them a lot by spreading spam and comments with bad words… Also the Scratch Team is already able to improve the filterbot and keep the website safe, they don't seem to need a testing place where people can test and they then see it.

For InternetExplorer8: The filterbot is stricter for new Scratchers, so it’s not the same as the normal filterbot.
k0d3rrr: There’s not a place where you could test.
Kiska-7275: Read the last part of the post.
historical_supa: Read the last part of the post.

Silicobra: Same as the last two.

XxDarqMidnightxX wrote:

Kiska-7275: Read the last part of the post.
historical_supa: Read the last part of the post.

XxDarqMidnightxX wrote:

Silicobra: Same as the last two.

The problem is that there are lots of ways of bypassing the filter. So, if the word “cat” is filtered, you could type cаt (with cyrillic а) or c@t. It will take much time to catch all the loopholes.

There are lots of ST members also, so it wouldn’t take as much time as say, with only a couple ST members.

We have a filterbot sandbox, but it's for ST use only.

It's not accessible to the general Scratch public because it could be very easily used by SEO spammers and trolls to test combination and try to get a leg up on the word filter, which we do not want.

Understandably, the filterbot can be sensitive, but having the sandbox accessible to everyone would ultimately lead to a more problematic moderation issue. So if you see a false positive, we ask you come to the Bugs and Glitches section of the forums and post the exact text you were using so the ST can run the text through the sandbox to see if it needs to be tweaked in some way.