How to fix mass-reporting on popular projects (Simple)

jcfiggy2

when popular project reported
ask [was there a reason for it to be?]
if <(answer) = [no]> then
put it back up
hide report project button

ILikeAxlotls

Yeah today a chungus animation got mass reported

jcfiggy2

ILikeAxlotls wrote:
Yeah today a chungus animation got mass reported

Literally I made this as a response to that and others lol

pavcato

I've heard this like 1 million times before, I'm pretty sure this is an unwritten reject suggestion. Anyways, this is a bad idea because then the creator is free to do whatever they want and people can't report.

mlcreater

ILikeAxlotls wrote:
Yeah today a chungus animation got mass reported

What is that?

pavcato wrote:
I've heard this like 1 million times before, I'm pretty sure this is an unwritten reject suggestion. Anyways, this is a bad idea because then the creator is free to do whatever they want and people can't report.

I, too, think that the Report button should not be hidden.
This is similar to a rejected suggestion:

Za-Chary wrote:
3.5 Remove the automatic project censoring system
The automatic project censoring system, with the accompanying temporary account block, is extremely useful to ensure that the community stays safe. Without this system, users who make inappropriate projects could keep making them without immediate consequence if a moderator is not online at the time. That would just expose more people to the inappropriate content. While the Scratch Team is open to making improvements to this system, neither removing the automatic project censor nor removing the automatic temporary account block are the solutions.

Zoomer_X

It's rejected:

The Official List of Rejected Suggestions wrote:
3.5 Remove the automatic project censoring system
The automatic project censoring system, with the accompanying temporary account block, is extremely useful to ensure that the community stays safe. Without this system, users who make inappropriate projects could keep making them without immediate consequence if a moderator is not online at the time. That would just expose more people to the inappropriate content. While the Scratch Team is open to making improvements to this system, neither removing the automatic project censor nor removing the automatic temporary account block are the solutions.

mlcreater

Zoomer_X wrote:
It's rejected:
The Official List of Rejected Suggestions wrote:
3.5 Remove the automatic project censoring system
The automatic project censoring system, with the accompanying temporary account block, is extremely useful to ensure that the community stays safe. Without this system, users who make inappropriate projects could keep making them without immediate consequence if a moderator is not online at the time. That would just expose more people to the inappropriate content. While the Scratch Team is open to making improvements to this system, neither removing the automatic project censor nor removing the automatic temporary account block are the solutions.

Not quite: the Scratch Team rejected removing the automatic reviewer; this is suggesting to stop people from reporting a project after it is put back up.

portalpower

1. if they could do that, they would
2. please don't blockspam

mlcreater

portalpower wrote:
1. if they could do that, they would
2. please don't blockspam

???

portalpower

mlcreater wrote:
portalpower wrote:
1. if they could do that, they would
2. please don't blockspam
???

what don't you understand

portalpower

oops i didn't read the second block but no support because people could make changes and they wouldn't be able to report it

gosoccerboy5

A lot of the time, “mass reporting” is just an excuse for a project being taken down or reshared for fame purposes.
Investigating reports is also a huge part of the ST's job, meaning they have that covered.
And although they may put projects that have been falsely reported back up already, it's not a good idea to make them invulnerable to reports — that as too much potential for people taking advantage of it and putting inappropriate stuff.

Za-Chary

If a Scratch Team member reviews a project, then “mass reporting” for the project effectively disappears. That is, we will make sure that a project is not automatically removed by reports after it is already reviewed once.

Since this is not a problem, the only part of this suggestion left to discuss is removing the Report button after the project was reviewed. But, since reports don't affect whether a project gets removed after it was reviewed, this wouldn't actually fix any problems. In fact, it might actually hurt; if the project creator changes their project to something inappropriate after it was reviewed, then no one would be able to report it to let us know that it was changed to be inappropriate.

So I don't think we'll be implementing this suggestion. Keeping the Report button available at all times is a good safety feature to make sure we can be notified of inappropriate projects. It can also keep Scratchers in check, to make sure they don't feel the need to make inappropriate projects.

Discuss Scratch