<answer is blacklisted?> block

GIitchInTheMatrix

Hey trolls, wake up, new block to find out how to work around the filter without getting muted just dropped.

InfinityLoopGaming

groggs wrote:
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.

This would be used for variables. (If player's answer is inappropriate)

GIitchInTheMatrix

InfinityLoopGaming wrote:
groggs wrote:
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.
This would be used for variables. (If player's answer is inappropriate)

set [i v] to [#^@%] 
(i) is blacklisted? ::sensing boolean

ajskateboarder

groggs wrote:
(#20)
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.

Such projects are supposed to be unshared since they contain bad words anyway. I guess if an NPC were to ask for input, it would do it with the answer block. Now it's completely safe.

<(answer) is blacklisted? :: sensing

Last edited by ajskateboarder (Jan. 5, 2023 17:36:10)

InfinityLoopGaming

GIitchInTheMatrix wrote:
InfinityLoopGaming wrote:
groggs wrote:
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.
This would be used for variables. (If player's answer is inappropriate)
set [i v] to [#^@%] 
(i) is blacklisted? ::sensing boolean

It would be used for the

(answer)

block.

GIitchInTheMatrix

InfinityLoopGaming wrote:
It would be used for the
(answer)
block.

Answer is blacklisted? ::sensing boolean //Still, you can use it to find out how to work around the filter.

InfinityLoopGaming

GIitchInTheMatrix wrote:
InfinityLoopGaming wrote:
It would be used for the
(answer)
block.
Answer is blacklisted? ::sensing boolean //Still, you can use it to find out how to work around the filter. 

So are you suggesting this to fix it?

Answer is blacklisted? ::sensing boolean

Last edited by InfinityLoopGaming (Jan. 5, 2023 18:29:13)

GIitchInTheMatrix

InfinityLoopGaming wrote:

GIitchInTheMatrix wrote:
InfinityLoopGaming wrote:
It would be used for the
(answer)
block.
Answer is blacklisted? ::sensing boolean //Still, you can use it to find out how to work around the filter. 

So are you suggesting this to fix it?

Answer is blacklisted? ::sensing boolean[/quote]
If it’s only for the answer block, theres no purpose having it allow for different types of input. 
Trolls can still work around the filter by finding out if a phrase is blacklisted or not.

groggs

InfinityGameLoop wrote:
It would be used for the
answer
block.

So is it for variables or strings or answers?

Also, not every project uses the answer block, as they'd like to design it in their style, and use this block…And this still can be bypassed with Zalgo or symbols “F0NK”, and as you said “You Removed The Cloud Chat Idea”, why should this get implemented, if user enters a cuss word, they already know it, so it's not gonna harm anybody anyways…

Edit: I just read the changes while writing the first words, and I am lazy to edit…

Last edited by groggs (Jan. 5, 2023 18:36:09)

InfinityLoopGaming

GIitchInTheMatrix wrote:
InfinityLoopGaming wrote:
GIitchInTheMatrix wrote:
InfinityLoopGaming wrote:
It would be used for the
(answer)
block.
Answer is blacklisted? ::sensing boolean //Still, you can use it to find out how to work around the filter. 
So are you suggesting this to fix it?
Answer is blacklisted? ::sensing boolean
If it’s only for the answer block, theres no purpose having it allow for different types of input.
Trolls can still work around the filter by finding out if a phrase is blacklisted or not.

How about this. If the thing <b>does</b> go to true, you get an answer-ban, banning you from answering in-project questions.

Last edited by InfinityLoopGaming (Jan. 5, 2023 18:36:49)

InfinityLoopGaming

groggs wrote:
InfinityGameLoop wrote:
It would be used for the
answer
block.
So is it for variables or strings or answers?

Also, not every project uses the answer block, as they'd like to design it in their style, and use this block…And this still can be bypassed with Zalgo or symbols “F0NK”, and as you said “You Removed The Cloud Chat Idea”, why should this get implemented, if user enters a cuss word, they already know it, so it's not gonna harm anybody anyways…

Edit: I just read the changes while writing the first words, and I am lazy to edit…

The input was removed for a few reasons, but to find uses, try reading the first post. It has a “uses” section.

groggs

InfinityLoopGaming wrote:
How about this. If the thing <b>does</b> go to true, you get an answer-ban, banning you from answering in-project questions.

What? I don't get it…

groggs

InfinityLoopGaming wrote:
groggs wrote:
InfinityGameLoop wrote:
It would be used for the
answer
block.
So is it for variables or strings or answers?

Also, not every project uses the answer block, as they'd like to design it in their style, and use this block…And this still can be bypassed with Zalgo or symbols “F0NK”, and as you said “You Removed The Cloud Chat Idea”, why should this get implemented, if user enters a cuss word, they already know it, so it's not gonna harm anybody anyways…

Edit: I just read the changes while writing the first words, and I am lazy to edit…
The input was removed for a few reasons, but to find uses, try reading the first post. It has a “uses” section.

As long as you're just talking to an NPC, how would saying cuss words become harmful??
You aren't talking with any real person, so…It would make no sense

cookieclickerer33

groggs wrote:
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.

Exactly

gdfsgdfsgdfg

There is a workaround but it’s tedious

groggs

gdfsgdfsgdfg wrote:
There is a workaround but it’s tedious

Well, you always tell people to read the OP, so do it yourself now…

InfinityLoopGaming

gdfsgdfsgdfg wrote:
There is a workaround but it’s tedious

1. What is it?
2. How the heck do you log in, I would never be able to remember the order of my username if I had that username.

banana439monkey

hi875230163394 wrote:
(#8)
this is technically implemented with the google translate extension, just saying

words like automodmute do not get blocked so i don't think it uses the filter…

Banana

Stickmin3000remixer

no it would be more like

<(answer) is blacklisted?::sensing>

Last edited by Stickmin3000remixer (Jan. 5, 2023 21:45:02)

groggs

Stickmin3000remixer wrote:
no it would be more like
<(answer) is blacklisted?::sensing>

Well it was, before it got edited, the purpose of the edit is to avoid having the blacklisted words in the text fields, so no one reads them. I am just guessing

Discuss Scratch