Idea by @grki2032
(They allowed me to post this on forum)
Scratch team should have this valid checker because there are so many mass reports in scratch. For example, famous scratcher’s projects get taken down due to mass reports. This is a problem because whenever a jealous person see’s a project with so much effort, they try to take it down.

This is why we need a valid report checker to make sure there is an actual reason why they reported a project. If the report is invalid or mass reported, the project should be sent to the scratch team to see if it is actually valid or invalid.

This is extremely innacurate. Most projects taken down are taken down because they did indeed break a rule. There are many rules that people simply ignore for whatever reason. Mass reports are also temporary and are put back up if the project was verified to not break the rules, so if the project stays down, it most definetly broke some rule.

Also, all reports are handled by the ST anyways so this pretty much exists

From what massreport threats I've read, massreports are never caused from jelousy, but because someone wants to win a worthless argument or annoy someone.

also this is sort of implemented since ST already views reports, they just have an automatic takedown for safety.
EDIT: Ninja'd

blablablahello wrote:

This is extremely innacurate. Most projects taken down are taken down because they did indeed break a rule. There are many rules that people simply ignore for whatever reason. Mass reports are also temporary and are put back up if the project was verified to not break the rules, so if the project stays down, it most definetly broke some rule.

Also, all reports are handled by the ST anyways so this pretty much exists

Recently @incognitoOrange had a lot of projects taken down due to mass reporters (he got it back up, but the reporters are still in scratch) he had to contact the scratch team though

Zydrolic wrote:

From what massreport threats I've read, massreports are never caused from jelousy, but because someone wants to win a worthless argument or annoy someone.

also this is sort of implemented since ST already views reports, they just have an automatic takedown for safety.
EDIT: Ninja'd

Many famous scratchers have been mass reported

humm- wrote:

(#5)
Many famous scratchers have been mass reported

Use Contact-Us, may take long or feel tedious but remember ST is nonprofit so they ain't gonna code something that surfs the entire internet to find evidence, that'd be taking years to report a singular thing and could cause false positives, not to mention the internet being most likely over a few thousand terabytes.
EDIT: Also, I get ya wanna do good but how would it really “check” if it's not a false mass report?

Zydrolic wrote:

humm- wrote:

(#5)
Many famous scratchers have been mass reported

Use Contact-Us, may take long or feel tedious but remember ST is nonprofit so they ain't gonna code something that surfs the entire internet to find evidence, that'd be taking years to report a singular thing and could cause false positives, not to mention the internet being most likely over a few thousand terabytes.
EDIT: Also, I get ya wanna do good but how would it really “check” if it's not a false mass report?

Almost all mass reports take down projects and sometimes the reason isn’t valid for the project so scratch team needs to see if the rules is actually broken in the project.

humm- wrote:

(#7)
Almost all mass reports take down projects and sometimes the reason isn’t valid for the project so scratch team needs to see if the rules is actually broken in the project.

There's an automated takedown which puts the project under review, it doesn't get taken down — Only unshared until reviewed or requested to be reviewed with Contact Us.
EDIT: To my knowledge atleast

If you feel like your project was wrongly reported, I’m pretty sure it’s okay to just reshare it. Not to mention, the scratch team is made up of under 100 people (I’m pretty sure anyway) and they have to make sure 170 million people don’t get into trouble. I’ve already stumbled across people posting extremely explicit content and getting away with it, and sometimes they are hidden within the project.

Thousands of projects get reported daily so under 100 people would have to go through a few thousand projects on a daily baisis, look at atleast 3 minutes worth of content in it if it’s a large size, and then determine if it should stay accessible or be deleted, and then repeat that hundreds of times. Only around under 100 people are in the scratch team, so this would be a nightmare of extra work they’d have to complete.

humm- wrote:

Scratch team should have this valid checker…

Please tell us what this would do.

humm- wrote:

…because there are so many mass reports in scratch. For example, famous scratcher’s projects get taken down due to mass reports. This is a problem because whenever a jealous person see’s a project with so much effort, they try to take it down.

That is not as true as people think it is. Yes, a project with enough reports gets taken down automatically, but the ST then reviews it, and if it is as perfectly innocent as the community says it is, then they will return it.

humm- wrote:

This is why we need a valid report checker to make sure there is an actual reason why they reported a project. If the report is invalid or mass reported, the project should be sent to the scratch team to see if it is actually valid or invalid.

Again, the Scratch Team reviews reported projects, and users are required to write a reason for reporting a project, so what you mentioned is basically already implemented.

humm- wrote:

Almost all mass reports take down projects and sometimes the reason isn’t valid for the project so scratch team needs to see if the rules is actually broken in the project.

But how does it figure out that a report is invalid?

Elijah999999 wrote:

humm- wrote:

Almost all mass reports take down projects and sometimes the reason isn’t valid for the project so scratch team needs to see if the rules is actually broken in the project.

But how does it figure out that a report is invalid?

When people report, you can type the reason why. If the reason is invalid, It doesn't really count as if the project gets reported multiple times, it gets taken down. So, there should be a way scratch can see that it IS a valid reason to the report by looking in the project or the sprite/background.

BendyOl183 wrote:

If you feel like your project was wrongly reported, I’m pretty sure it’s okay to just reshare it. Not to mention, the scratch team is made up of under 100 people (I’m pretty sure anyway) and they have to make sure 170 million people don’t get into trouble. I’ve already stumbled across people posting extremely explicit content and getting away with it, and sometimes they are hidden within the project.

Thousands of projects get reported daily so under 100 people would have to go through a few thousand projects on a daily baisis, look at atleast 3 minutes worth of content in it if it’s a large size, and then determine if it should stay accessible or be deleted, and then repeat that hundreds of times. Only around under 100 people are in the scratch team, so this would be a nightmare of extra work they’d have to complete.

….I have nothing to say

humm- wrote:

When people report, you can type the reason why. If the reason is invalid, It doesn't really count as if the project gets reported multiple times, it gets taken down. So, there should be a way scratch can see that it IS a valid reason to the report by looking in the project or the sprite/background.

I understand that you want it to check if a report is valid, but how does it determine what is valid and what is not?

BendyOl183 wrote:

If you feel like your project was wrongly reported, I’m pretty sure it’s okay to just reshare it.

If a project was “mass reported” in the sense that it was automatically unshared from reports, then it is impossible to reshare it until the Scratch Team reviews it. If the project was removed manually by the Scratch Team, you should not reshare it until you change the offending content. If you don't know why it was unshared or you disagree with the reason, reach out to the Scratch Team via Contact Us before resharing the project.

humm- wrote:

This is why we need a valid report checker to make sure there is an actual reason why they reported a project. If the report is invalid or mass reported, the project should be sent to the scratch team to see if it is actually valid or invalid.

This is essentially already implemented, it just takes some time. When a project is automatically removed due to users reporting the project, the Scratch Team gets sent a report, and they will review the project to see if it is appropriate. If it is, the project gets reshared, and the reports are considered “invalid”; in some cases, the users who sent those reports could get alerts. If the project is not appropriate, the project remains unshared, the reports are considered “valid,” and the Scratch Team sends a message to the project creator explaining why the project remains unshared.

Za-Chary wrote:

BendyOl183 wrote:

If you feel like your project was wrongly reported, I’m pretty sure it’s okay to just reshare it.

If a project was “mass reported” in the sense that it was automatically unshared from reports, then it is impossible to reshare it until the Scratch Team reviews it. If the project was removed manually by the Scratch Team, you should not reshare it until you change the offending content. If you don't know why it was unshared or you disagree with the reason, reach out to the Scratch Team via Contact Us before resharing the project.

What I meant is that if your project is removed and it says it was removed for something that isn’t even in the project at all. However, I do think it makes sense to not reshare it now that I think about it because there is a tiny bit of automation in the moderation system so the project would probably be continuously unshared until you stop reshaping or you get temporarily banned

humm- wrote:

BendyOl183 wrote:

If you feel like your project was wrongly reported, I’m pretty sure it’s okay to just reshare it. Not to mention, the scratch team is made up of under 100 people (I’m pretty sure anyway) and they have to make sure 170 million people don’t get into trouble. I’ve already stumbled across people posting extremely explicit content and getting away with it, and sometimes they are hidden within the project.

Thousands of projects get reported daily so under 100 people would have to go through a few thousand projects on a daily baisis, look at atleast 3 minutes worth of content in it if it’s a large size, and then determine if it should stay accessible or be deleted, and then repeat that hundreds of times. Only around under 100 people are in the scratch team, so this would be a nightmare of extra work they’d have to complete.

….I have nothing to say

What do you mean? Do you think I’m saying incorrect things or do you literally have nothing you can say against me

Za-Chary wrote:

BendyOl183 wrote:

If you feel like your project was wrongly reported, I’m pretty sure it’s okay to just reshare it.

If a project was “mass reported” in the sense that it was automatically unshared from reports, then it is impossible to reshare it until the Scratch Team reviews it. If the project was removed manually by the Scratch Team, you should not reshare it until you change the offending content. If you don't know why it was unshared or you disagree with the reason, reach out to the Scratch Team via Contact Us before resharing the project.

humm- wrote:

This is why we need a valid report checker to make sure there is an actual reason why they reported a project. If the report is invalid or mass reported, the project should be sent to the scratch team to see if it is actually valid or invalid.

This is essentially already implemented, it just takes some time. When a project is automatically removed due to users reporting the project, the Scratch Team gets sent a report, and they will review the project to see if it is appropriate. If it is, the project gets reshared, and the reports are considered “invalid”; in some cases, the users who sent those reports could get alerts. If the project is not appropriate, the project remains unshared, the reports are considered “valid,” and the Scratch Team sends a message to the project creator explaining why the project remains unshared.

Oh wow that is good to know

BendyOl183 wrote:

humm- wrote:

BendyOl183 wrote:

If you feel like your project was wrongly reported, I’m pretty sure it’s okay to just reshare it. Not to mention, the scratch team is made up of under 100 people (I’m pretty sure anyway) and they have to make sure 170 million people don’t get into trouble. I’ve already stumbled across people posting extremely explicit content and getting away with it, and sometimes they are hidden within the project.

Thousands of projects get reported daily so under 100 people would have to go through a few thousand projects on a daily baisis, look at atleast 3 minutes worth of content in it if it’s a large size, and then determine if it should stay accessible or be deleted, and then repeat that hundreds of times. Only around under 100 people are in the scratch team, so this would be a nightmare of extra work they’d have to complete.

….I have nothing to say

What do you mean? Do you think I’m saying incorrect things or do you literally have nothing you can say against me

Im saying you are pretty much correct-