How do you know that this definitely happens on a wide scale? When a project gets taken down due to a number of reports, not even the owner themselves is directly told about it until the reports are confirmed legitimate by the ST. If they aren't confirmed legitimate, the project is reinstated. So I understand that if a project breaks the CGL (Community Guidelines) or if multiple people report a project it gets taken down but that power is kind of getting abused. There are projects that get taken down, not because of breaking the community guide lines but because of mass reportings. And nothing will even be wrong with the project!
When you report a project and nothing is wrong with it, THAT goes against CGL. Here is a quote from the CGL about honesty. “Don’t try to impersonate other Scratchers, spread rumors, or otherwise try to trick the community.” Or otherwise try to trick the community….. When reporting a project that doesn't break the CGL is tricking the Community to think that something might actually be wrong with that project.This last statement is quite far-fetched to begin with, even if the circumstances allow for it to be true in certain cases.
Again, projects automatically taken down due to illegitimate or mass reporting will be put back up if they contain no offending content.
Plus with all the reportings it must be hard for the Developer Community to check for every little thing wrong with project, but then finding out that nothing was wrong in the first place.You have to give a reason to report a project. People that waffle or lie in their reports are usually easily to pick out.
However, I'll admit that you have a point here.
Now I don't know how to fix to problem completely or even find out who actually is reporting for real or not, but I might know how to reduce it a bit. Maybe developers can try adding a little more to the report system. Like there should be a place in the report system where you can at least explain whats wrong or maybe even send a screen shot. And you can't send out the report unless there is a screen shot or explanation.As I said before, you already have to give a reason to report a project. While you don't have to give reasons for reporting comments, the comment can easily be read by the ST.
Screen-shots are mostly unnecessary because of this.
This is definitely a well-intentioned suggestion, but I advise you to check your facts in the future.