QuantumScratcher wrote:

It must NOT show what's wrong to avoid learning inappropriate content in the case of a lack of knowledge.

Of course, but if someone types the f-word in a text input, they aren't exactly going to not learn the word.

-Valtren- wrote:

at this point I would recommend making your own suggestion

We're just talking about different ideas about how the report system could work. I still like your idea a lot though because QuantumScratcher's concerns are met with them. With it only being reported the person making the project won't see what is wrong at all.

bump

musicROCKS013 wrote:

QuantumScratcher wrote:

It must NOT show what's wrong to avoid learning inappropriate content in the case of a lack of knowledge.

Of course, but if someone types the f-word in a text input, they aren't exactly going to not learn the word.

-Valtren- wrote:

at this point I would recommend making your own suggestion

We're just talking about different ideas about how the report system could work. I still like your idea a lot though because QuantumScratcher's concerns are met with them. With it only being reported the person making the project won't see what is wrong at all.

but that would kind of be the point-
if the trolls were alerted that the project had a bad word in it, they would simply draw inappropriate words rather than using the text tool, rendering this feature useless(and when the project gets taken down, since the trolls weren't alerted that they had a bad word in their projects, they'll think someone reported it, rather than there being an automatic system that detects bad words. this suggestion kinda relies on keeping people in the dark about it's existence). and anyway, the scratch team will see the project. no one would knowingly type a bad word, and if it's a mistake like in the case of “bit challenging”, this method makes it so that you can still share the project without having to remove stuff.
in the end, this suggestion isn't trying to prevent people from saying inappropriate things in projects, it's trying to bring the scratch team's attention to something that may be possibly guidelines-breaking as soon as possible.

-Valtren- wrote:

if the trolls were alerted that the project had a bad word in it, they would simply draw inappropriate words rather than using the text tool, rendering this feature useless.

Ok then. How about something like “Your project contains something that goes against the scratch terms of use”?

DifferentDance8 wrote:

-Valtren- wrote:

if the trolls were alerted that the project had a bad word in it, they would simply draw inappropriate words rather than using the text tool, rendering this feature useless.

Ok then. How about something like “Your project contains something that goes against the scratch terms of use”?

that won't work either. again, this suggestion isn't trying to prevent people from saying inappropriate things in projects, it's trying to alert the scratch team as soon as possible about these types of projects so that they can get taken down as soon as possible. this suggestion relies on trolls not knowing it exists so they use the text tool which the filter can detect. if they get a notification when they type a bad word it's going to be pretty obvious that there's some sort of filter running, and from there they'll probably draw the bad word which the filter can't detect, defeating the point

-Valtren- wrote:

that won't work either. again, this suggestion isn't trying to prevent people from saying inappropriate things in projects, it's trying to alert the scratch team as soon as possible about these types of projects so that they can get taken down as soon as possible. this suggestion relies on trolls not knowing it exists so they use the text tool which the filter can detect. if they get a notification when they type a bad word it's going to be pretty obvious that there's some sort of filter running, and from there they'll probably draw the bad word which the filter can't detect, defeating the point

From the OP, it sounds like the project will be published, for all to see.

DifferentDance8 wrote:

-Valtren- wrote:

that won't work either. again, this suggestion isn't trying to prevent people from saying inappropriate things in projects, it's trying to alert the scratch team as soon as possible about these types of projects so that they can get taken down as soon as possible. this suggestion relies on trolls not knowing it exists so they use the text tool which the filter can detect. if they get a notification when they type a bad word it's going to be pretty obvious that there's some sort of filter running, and from there they'll probably draw the bad word which the filter can't detect, defeating the point

From the OP, it sounds like the project will be published, for all to see.

yes, except probably no one will see it, because the second the project is shared, the filter goes through all the places where you can input text, checking for bad words. if it does find a bad word, it sends a report to the report queue. a scratch team member sees the report, and takes the project down. in the time between when the bad project was shared and when it was taken down(assuming of course it was shared when a scratch team member was active), probably no one will have seen the project(in fact, in optimal conditions, the project could in theory be taken down mere seconds after it was shared). This way, the scratch team is informed of the bad words as soon as possible, and you don't require a scratcher to report the project with the bad words. if the project is shared when the scratch team is asleep, the current mass report system will handle that.

random question, are you allowed to swear and such when its unshared but itll only be reviewed if you share it to the scratch website?

also, for the “literally 0 ppl will see it in 2 seconds” thingy, the troll can just advertise in popular projects lol
then some random kid clicks on it and yeah its all downhill from there

epicboi17 wrote:

random question, are you allowed to swear and such when its unshared but itll only be reviewed if you share it to the scratch website?

That's not random at all! And yes. As long as you don't publicize it on scratch (anywhere, including using TurboWarp), it should be fine. However, I am not an ST member, and as such, IDK if this is true or not.

I can totally see trolls making multipule accouts and sharing loads of bad projects on each one, just to fill up the queue

Bilipirip wrote:

I can totally see trolls making multipule accouts and sharing loads of bad projects on each one, just to fill up the queue

true, but one way to solve this would be to have a system in place where if the project filter triggers twice in less than one minute, the user is blocked until the projects are reviewed by the scratch team. I seriously doubt that anyone who's accidentally triggering the filter will manage to do so twice in one minute.

-Valtren- wrote:

Bilipirip wrote:

I can totally see trolls making multipule accouts and sharing loads of bad projects on each one, just to fill up the queue

true, but one way to solve this would be to have a system in place where if the project filter triggers twice in less than one minute, the user is blocked until the projects are reviewed by the scratch team. I seriously doubt that anyone who's accidentally triggering the filter will manage to do so twice in one minute.

Then they will share one bad project on one account, wait 60 seconds, go onto another and share a bad project and on and on…

DifferentDance8 wrote:

-Valtren- wrote:

Bilipirip wrote:

I can totally see trolls making multipule accouts and sharing loads of bad projects on each one, just to fill up the queue

true, but one way to solve this would be to have a system in place where if the project filter triggers twice in less than one minute, the user is blocked until the projects are reviewed by the scratch team. I seriously doubt that anyone who's accidentally triggering the filter will manage to do so twice in one minute.

Then they will share one bad project on one account, wait 60 seconds, go onto another and share a bad project and on and on…

yes, but they wouldn't necessarily know that they have to wait 60 seconds. and anyway, both projects will be reported by the filter, so in the end they'll get taken down. at least it's faster than people manually reporting the projects…

DifferentDance8 wrote:

-Valtren- wrote:

Bilipirip wrote:

I can totally see trolls making multipule accouts and sharing loads of bad projects on each one, just to fill up the queue

true, but one way to solve this would be to have a system in place where if the project filter triggers twice in less than one minute, the user is blocked until the projects are reviewed by the scratch team. I seriously doubt that anyone who's accidentally triggering the filter will manage to do so twice in one minute.

Then they will share one bad project on one account, wait 60 seconds, go onto another and share a bad project and on and on…

What if after 3 times that IP address is blocked from sharing till ST reviews the project and decides what to do?

Prince_Wolf1 wrote:

What if after 3 times that IP address is blocked from sharing till ST reviews the project and decides what to do?

What if the filter breaks? Chaos.

-Valtren- wrote:

true, but one way to solve this would be to have a system in place where if the project filter triggers twice in less than one minute, the user is blocked until the projects are reviewed by the scratch team. I seriously doubt that anyone who's accidentally triggering the filter will manage to do so twice in one minute.

Say the filter breaks. A lot of projects a minute are shared every day, so that would be bad. Plus, what if said user makes a lot of projects, with little effort? That's just how they make projects, it isn't their fault the filter bot thinks they're making bad projects and suddenly they're banned. At that point, if this happens a lot, the appeal emails would pile up and make the process even slower than it already is. There isn't such thing as a perfect bot, and this would defiantly be a large downside.

Bilipirip wrote:

Prince_Wolf1 wrote:

What if after 3 times that IP address is blocked from sharing till ST reviews the project and decides what to do?

What if the filter breaks? Chaos.

-Valtren- wrote:

true, but one way to solve this would be to have a system in place where if the project filter triggers twice in less than one minute, the user is blocked until the projects are reviewed by the scratch team. I seriously doubt that anyone who's accidentally triggering the filter will manage to do so twice in one minute.

Say the filter breaks. A lot of projects a minute are shared every day, so that would be bad. Plus, what if said user makes a lot of projects, with little effort? That's just how they make projects, it isn't their fault the filter bot thinks they're making bad projects and suddenly they're banned. At that point, if this happens a lot, the appeal emails would pile up and make the process even slower than it already is. There isn't such thing as a perfect bot, and this would defiantly be a large downside.

if the filter breaks the filter breaks. nothing we can do about that.
also I get if someone would share multiple projects in the timespan of one minute if they don't spend much effort on them, but the chances that both projects will trigger the project filter are extremely low, especially if the projects are on different topics. (lets say you have a 1 in 100 chance of the word you type triggering the filter. the chances of this happening accidentally would be around 1 in 10000. you'd have to be really unlucky).

for trolls however who are deliberately putting bad words, the chances would be very high. in the end, it's true that there's no such thing as the perfect bot, but that doesn't mean that things will always go horribly wrong.

edit: I've never heard of a case where the filter reverses what it detects and what it doesn't, so I doubt the filter breaking would be much of a problem here
also, in order for the chaos to happen the filter would have to break. if it doesn't then no chaos, simple. you won't get conked on the head by a coconut if it doesn't fall, will you?

Support. It seems feasible to filter text in SVG costumes, at least.

bumpadoodle

If it is inplemented can we still have unshared projects which are inappriopriate for scratch.

Purvitekriwal wrote:

If it is inplemented can we still have unshared projects which are inappriopriate for scratch.

those are allowed.