<answer is blacklisted?> block

InfinityLoopGaming

I am proposing a block that checks if the entered value is blacklisted.

<answer is blacklisted? :: sensing>

It will return as true if the word and/or phrase is not allowed on Scratch.
Blacklists aren't allowed because there would be a list of cuss words in a project, which any Scratcher could go in the project and see it. This block would fix it.
I think it would be in the sensing category.

Uses:
This could be used for a project with an NPC, and the NPC says “That's not nice!” when the block returns as true, this could be used for a text render engine, to prevent rendering bad words, etc.

This was originally meant as a fix for the “cloud chat” problem, but it was rejected by many people.

Edit list:
Edit 1: Removed cloud chat idea
Edit 2: Changed blacklist block from a reporter to a boolean
Edit 3: Changed block from <() is blacklisted?> to <answer is blacklisted?>

Last edited by InfinityLoopGaming (Jan. 5, 2023 18:31:52)

banana439monkey

it does not fix the cloud chat issue at all if the block you're suggesting does not get implemented by people into their own cloud chat projects

Banana

cookieclickerer33

Even with a black list cloud chats are banned.
So this would just make cloud chats easier and nothing else

medians

Just use the translate extension, and cloud chats would still be taken down due to the fact that if they bypass the filter, the Scratch Team cannot moderate it.

D-ScratchNinja

There are words that are only considered offensive when used in certain contexts (take “bad”, for example). This block wouldn't solve that problem unless it were to use a very smart filter, and Scratch probably doesn't have the resources to research or run one of those.

Last edited by D-ScratchNinja (Jan. 5, 2023 02:53:33)

InfinityLoopGaming

D-ScratchNinja wrote:
There are words that are only considered offensive when used in certain contexts (take “bad”, for example). This block wouldn't solve that problem unless it were to use a very smart filter, and Scratch probably doesn't have the resources to research or run one of those.

What about the filter it uses in the Scratch comments?

medians

InfinityLoopGaming wrote:
D-ScratchNinja wrote:
There are words that are only considered offensive when used in certain contexts (take “bad”, for example). This block wouldn't solve that problem unless it were to use a very smart filter, and Scratch probably doesn't have the resources to research or run one of those.
What about the filter it uses in the Scratch comments?

But then if they use a word like that in a negative way, or they bypass it, the Scratch Team cannot moderate it.

hi875230163394

this is technically implemented with the google translate extension, just saying

groggs

However, even if this existed, Cloud Chats would stay banned.

cookieclickerer33

groggs wrote:
However, even if this existed, Cloud Chats would stay banned.

But it directly and only benefits cloud chats

InfinityLoopGaming

hi875230163394 wrote:
this is technically implemented with the google translate extension, just saying

What? I checked and there was no such block.

InfinityLoopGaming

banana439monkey wrote:
it does not fix the cloud chat issue at all if the block you're suggesting does not get implemented by people into their own cloud chat projects

Banana

Then those chats can be reported.

cookieclickerer33

InfinityLoopGaming wrote:
hi875230163394 wrote:
this is technically implemented with the google translate extension, just saying
What? I checked and there was no such block.

The translate extension changes words if they are blacklisted

InfinityLoopGaming

Ok, so it doesn't work for cloud chats, this would still be a useful block!

cookieclickerer33

InfinityLoopGaming wrote:
Ok, so it doesn't work for cloud chats, this would still be a useful block!

How?

InfinityLoopGaming

cookieclickerer33 wrote:
InfinityLoopGaming wrote:
Ok, so it doesn't work for cloud chats, this would still be a useful block!
How?

InfinityLoopGaming wrote:
This could be used for a project with an NPC, and the NPC says “That's not nice!” when the block returns as true.
This could be used for a text render engine, to prevent rendering bad words.
etc.

qwerty_wasd_gone

how about a boolean instead

<() is blacklisted ?::sensing>

InfinityLoopGaming

qwerty_wasd_gone wrote:
how about a boolean instead
<() is blacklisted ?::sensing>

Oh lol i did it wrong okie

qwerty_wasd_gone

InfinityLoopGaming wrote:
qwerty_wasd_gone wrote:
how about a boolean instead
<() is blacklisted ?::sensing>
Oh lol i did it wrong okie

Support because

InfinityLoopGaming wrote:
Uses:
This could be used for a project with an NPC, and the NPC says “That's not nice!” when the block returns as true, this could be used for a text render engine, to prevent rendering bad words, etc.

groggs

Won't people also just see inside and remove it? and what if some young kid remixes the project, and finds something like,

<[#@!?] is blacklisted? :: sensing> //Pretend it's a bad word...

I don't think he would like to see that.

Discuss Scratch