Support. I was banned temporarily because of this as well.

Darkstar177 wrote:

Support. I was banned temporarily because of this as well.

This discussion is from 2015. Please do not necropost. I am reporting this to be closed.

XxShazammxX wrote:

Darkstar177 wrote:

Support. I was banned temporarily because of this as well.

This discussion is from 2015. Please do not necropost. I am reporting this to be closed.

Necroposting does not exist in the Suggestions forum as long as the suggestion is still relevant (which it is) and the comment is still constructive (which it was).

XxShazammxX wrote:

Darkstar177 wrote:

Support. I was banned temporarily because of this as well.

This discussion is from 2015. Please do not necropost. I am reporting this to be closed.

The last reply was from yesterday..

DaSpudLord wrote:

Chibi-Matoran wrote:

Support.

how do you make one of them things like you'rs is
If you see this signature while scrolling, you have been visited by ʎ++ haskal. Lazy evaluation, monads, function purity, lambdas, currying, partial application, algebraic data types, pattern matching, and typeclasses will come to you, but only if you comment, “Thanks, ʎ++ haskal” on my profile.

Cassian && ||

I partially support this. I'd like to see a system implemented that if 75% of viewers report it, the project gets taken down. It prevents false removal and is still safe.

Banana

Support. It's not fair to be banned for no reason at all.

Why do people mass report anyways?

Some people want revenge, are envious, or just like to “troll,” even if mass-reporting doesn't benefit them at all.

Hello, I completely disagree with mass reporting but getting rid of these would mean a slower response from the Scratch Team when a automatic ban is actually needed. I have viewed the automated systems myself and I think the way they are set up are how they should be. Thanks!

GeekTech wrote:

Hello, I completely disagree with mass reporting but getting rid of these would mean a slower response from the Scratch Team when a automatic ban is actually needed. I have viewed the automated systems myself and I think the way they are set up are how they should be. Thanks!

We are only saying that that the user should not be banned when the mass-report happens, and instead, should get some kind of alert saying something like:

"Project has been temporarily taken down due to a series of reports by multiple scratchers. We will review the project to determine if it has broken the Community Guidelines. If we find nothing wrong, we will allow the project to be re-shared."

It would act like you still need to verify the account, not allowing you to share projects and such, and if the project does break the guidelines, action can be taken.

JRR078s wrote:

GeekTech wrote:

Hello, I completely disagree with mass reporting but getting rid of these would mean a slower response from the Scratch Team when a automatic ban is actually needed. I have viewed the automated systems myself and I think the way they are set up are how they should be. Thanks!

We are only saying that that the user should not be banned when the mass-report happens, and instead, should get some kind of alert saying something like:

"Project has been temporarily taken down due to a series of reports by multiple scratchers. We will review the project to determine if it has broken the Community Guidelines. If we find nothing wrong, we will allow the project to be re-shared."

It would act like you still need to verify the account, not allowing you to share projects and such, and if the project does break the guidelines, action can be taken.

Why, it's already like that!

I think it's become a big problem recently.

Col_Cat228 wrote:

JRR078s wrote:

GeekTech wrote:

Hello, I completely disagree with mass reporting but getting rid of these would mean a slower response from the Scratch Team when a automatic ban is actually needed. I have viewed the automated systems myself and I think the way they are set up are how they should be. Thanks!

We are only saying that that the user should not be banned when the mass-report happens, and instead, should get some kind of alert saying something like:

"Project has been temporarily taken down due to a series of reports by multiple scratchers. We will review the project to determine if it has broken the Community Guidelines. If we find nothing wrong, we will allow the project to be re-shared."

It would act like you still need to verify the account, not allowing you to share projects and such, and if the project does break the guidelines, action can be taken.

Why, it's already like that!

But maybe the ST are taking a bit long to review it.
Also, people have gotten BANNED because of this, so the system might be flawed.

vode123 wrote:

Also, people have gotten BANNED because of this, so the system might be flawed.

I think you can only get auto-banned if you get multiple alerts.

Maximouse wrote:

vode123 wrote:

Also, people have gotten BANNED because of this, so the system might be flawed.

I think you can only get auto-banned if you get multiple alerts.

Which is exactly what is happening!
People mass-report a project, multiple alerts are given to the Scratcher, and…

i think that they should take away the banning part,but however i still think taking down the project should still be in,because if there was this super inappropriate project it would be taken down quicker,, but they should also check more quicker so that projects don't lose the trend due to mass reporting.

FreezeNova wrote:

i think that they should take away the banning part,but however i still think taking down the project should still be in,because if there was this super inappropriate project it would be taken down quicker,, but they should also check more quicker so that projects don't lose the trend due to mass reporting.

Exactly! You're a star!

vode123 wrote:

FreezeNova wrote:

i think that they should take away the banning part,but however i still think taking down the project should still be in,because if there was this super inappropriate project it would be taken down quicker,, but they should also check more quicker so that projects don't lose the trend due to mass reporting.

Exactly! You're a star!

thanks. I actually been mass reported once before and was super mad,but now i understand that mass reporting actually helps. I do think they should make some modifications to the system : 1.pull up the community guildlines when someone is making a report. Sometimes people may report projects because they dont understand the cgs completey. For example(real story),someone reported my project because they thought asking for a follow at the end of a project was advisting.2.make the project go on the EXACT place it was on trending if it ever gets brought back up.3. stop users from reporting projects repeatly,andmake it so that you have to wait a certain time. 4. Only scratchers can report projects,to prevent people from creating new accounts and reporting.5. dont allow multiple reports on the same project from the same ip adress

Guys can you please stop necroposting?