As you guys probably know, mass reporting has been a huge issue on scratch lately. I have an idea to buffer that.

If a user reports more then 3-5 things in 5 mins, a message will pop up saying

"You seem to be reporting a lot of things very quickly, are you sure that these projects/comments break the community guidelines? A good scratcher only reports if the comment/project breaks the guidelines.
You can still report projects, but be sure that they break the community guidelines"

EDIT: You can still report projects after this message!! It's just an extended reminder

Great idea, but mass reporting can still occur. A person can create multiple accounts to report something or make “we want this scratcher banned” studios (they do exist) and make up some sob story to make people report a certain person's content or profile. Even if the content doesn't break the guidelines, they might think, “Oh, but they still deserve it for doing this, this, this.”

iiucandyfloss wrote:

Great idea, but mass reporting can still occur. A person can create multiple accounts to report something or make “we want this scratcher banned” studios (they do exist) and make up some sob story to make people report a certain person's content or profile. Even if the content doesn't break the guidelines, they might think, “Oh, but they still deserve it for doing this, this, this.”

True, but I hope a message will deter most of mass reporters from, well, mass reporting

crazycatA wrote:

As you guys probably know, mass reporting has been a huge issue on scratch lately.

Citation needed

I also have come across situations where a user has large numbers of inappropriate projects on their profile, and this would keep me from getting them all reported so they can be dealt with.

jvvg wrote:

crazycatA wrote:

As you guys probably know, mass reporting has been a huge issue on scratch lately.

Citation needed

I also have come across situations where a user has large numbers of inappropriate projects on their profile, and this would keep me from getting them all reported so they can be dealt with.

I've known scratchers who have been mass reported, but I see your point. that's why it wouldn't pause reporting, just remind the user to make sure the project/comment has broke the community guidelines

Not really, when you report something a message pops up.


Please let me know if the image isn't shown.
Therefore it wouldn't be quite helpful.

Example scenario:

So for example there is a project. This project is made by @______. This user said No Advertising in the notes and credits section, but a mass amount of people starts posting their project links and starts commenting hate, now the options @______ could use is either reporting all of it or commenting down, Please don't hate on this project.

Would you rather?
1. Be stopped from reporting comments.
2. Hand-type each comment and still get stopped because of the comment interval time limit.

It's kind of obvious what you would want.

Aaliyah_Newlands wrote:

Not really, when you report something a message pops up.


Please let me know if the image isn't shown.
Therefore it wouldn't be quite helpful.

Example scenario:

So for example there is a project. This project is made by @______. This user said No Advertising in the notes and credits section, but a mass amount of people starts posting their project links and starts commenting hate, now the options @______ could use is either reporting all of it or commenting down, Please don't hate on this project.

Would you rather?
1. Be stopped from reporting comments.
2. Hand-type each comment and still get stopped because of the comment interval time limit.

It's kind of obvious what you would want.

yeah,,, that's why it would just be an extra message, not pausing reporting (see edit)

crazycatA wrote:

I've known scratchers who have been mass reported, but I see your point. that's why it wouldn't pause reporting, just remind the user to make sure the project/comment has broke the community guidelines

Honestly, for any given Scratcher, they can only contribute to “mass reporting” a single time. In other words, if I report your project 1000 times, it will still never get taken down for “mass reporting.” It will only do that if other people also report your project.

As a result, I don't think your suggestion would really help with “mass reporting.” The only thing I can think this would help with is that it could prevent someone from spamming a lot of reports on a single project or elsewhere, which in theory could be helpful for the Scratch Team since that means they'd have to sort through less reports, but in any case this wouldn't prevent a user's project from getting removed if other people also report it.

If I don't remember wrong, 3.0 pages already only actually send a report once. Reporting it again only gives the modal, but doesn't actually send it.

Contraery wrote:

If I don't remember wrong, 3.0 pages already only actually send a report once. Reporting it again only gives the modal, but doesn't actually send it.

I believe you are able to send the report more than once. The key difference is that sending a report more than once does not contribute more to the possibility of a project getting “mass reported.”

crazycatA wrote:

jvvg wrote:

crazycatA wrote:

As you guys probably know, mass reporting has been a huge issue on scratch lately.

Citation needed

I also have come across situations where a user has large numbers of inappropriate projects on their profile, and this would keep me from getting them all reported so they can be dealt with.

I've known scratchers who have been mass reported, but I see your point. that's why it wouldn't pause reporting, just remind the user to make sure the project/comment has broke the community guidelines

That is one singular example.

If you report something 2 times, it only counts as 1 report.

As written in the essay the legendary gamer jvvg posted, if a project is falsely mass reported it will usually be put back up and the reporters punished. If it isn't put back up it means the ST reviewed it and found a reason to not re release the project, so usually if it stays down there was actually something wrong with the project

crazycatA wrote:

yeah,,, that's why it would just be an extra message, not pausing reporting (see edit)

Yup, but that would just be an extra message? Its going to make reporting slower…If there's already a pop up, why ask for another one? Just read the scratch guidelines before your first report…

alerts exist for false reporting…

Banana

I agree, just got false reported

crazycatA wrote:

As you guys probably know, mass reporting has been a huge issue on scratch lately. I have an idea to buffer that.

If a user reports more then 3-5 things in 5 mins, a message will pop up saying

"You seem to be reporting a lot of things very quickly, are you sure that these projects/comments break the community guidelines? A good scratcher only reports if the comment/project breaks the guidelines.
You can still report projects, but be sure that they break the community guidelines"

EDIT: You can still report projects after this message!! It's just an extended reminder

my message idea would be: “Woah, seems like you're reporting projects really quickly. Please wait a bit longer between reporting projects.” (varies if project, studio, user, or post)

quarterball wrote:

I agree, just got false reported

you probably weren't
——–
In my roughly 6 years of scratching, I have seen…. (drumroll) 2 projects illegitimately taken down! Wow, that is a huge number.

as many people have stated above, the problem is way overblown and often blamed when reports are legitimate, and even if they were really right and it was actually bad reports, it would still not help with the “problem” This should not be implemented.

MagicCoder330 wrote:

quarterball wrote:

I agree, just got false reported

you probably weren't You don't have proof of them not being false reported sooooooooooooooooooo.
——–
In my roughly 6 years of scratching, I have seen…. (drumroll) 2 projects illegitimately taken down! Wow, that is a huge number. Only for you

as many people have stated above, the problem is way overblown and often blamed when reports are legitimate, and even if they were really right and it was actually bad reports, it would still not help with the “problem” This should not be implemented.

True but you gotta admit it shouldn't exist and it could help stop speaking for everyone and get mad at little kids who had there project false reported.


It's a 50/50 chance of them lying or telling the truth anyway.

I think you should just tell them to use Contact Us instead of spamming the same link which is annoying and everybody on the forums spams it for some reason.