Suggestion: (please read the whole post before answering)

Change the ammount of reports needed to take down a project by the followers you have. This is just for not Scratch Team checked projects when it gets automatically taken down.

Why like that?
This makes sense as for example a scratcher with 0-20 followers should get it removed after 3 or 4 Reports while a Scratcher with 1000 followers would then easily get mass-reported and taken down. Now, you COULD say you should base it on views, but those are way easier to manipulate than follows.

Would 0 followers autotakedown projects?
No, as there is a standard number of 3 or 4 reports which is then increased by achieving more followers.

And… Equality?
Even though I don't think that the same ammout of reports to takedown a project for everyone is the best idea, because famous scratchers suffer from mass reporting and taking down a project goes with “just a few reports” goes too fast if you get so many views, an increased number of reports for everyone would make it harder to takedown inappropiate projects of unpopular scratchers which are not seen often. This suggestion would remove that everyone is treated equal in that case but in my opinion (and that's just a opinion) it's right.

Massreporting new Scratchers?
As that wasd mentioned, I can just say I am not sure. On the one hand, for what could a massreporter be envious or angry onto a new or unpopular Scratcher but on the other hand, this system might allow that to happen. Still, this should be also possible in the current system, even tho I have never heard of it happening (which was possibly also was caused by the cases where it happened not reaching much attention since the people that were hit were unpopular and just almost nobody saw it).

Cons:
-If an F4Fer that has a lot of followers makes a project that's inappropiate, it may not be taken down because *some* F4Fers don't get many views and then the project may cause a lot more trouble than needed

Still remember we are talking about autotakedown and reproted projects will be still checked by the Scratch Team members.

Now, what do you think?

so if i have 0 it will auto take it down?
No support

<OUO> :: motion  // this is gary he protects my siggy from evil kumquats 

(( ( •) ) _ (( •))    :: #000000   // this is Michael incase gary cant defeat the kumquats

What about a person with 0 followers?

How will they be able to share projects

say [foo v] :: operators :: hat
delete clone of [myself v] :: custom
switch costume to <existing?:: motion> :: control 
when I start as a [clone v] :: sound :: cap



<<<<<<<<<<<<<<<<ULTRA BOOLEAN :: #fa0255> :: #fa02ac> :: #fa02ee> :: #d902fa> :: #6502fa> :: #024dfa> :: #02cdfa> :: #02fa93> :: #02fa0b> :: #a3fa02> :: #e1fa02> :: #fac002> :: #fa7a02> :: #fa3402> :: #fa0202> :: #fa0202

<<<<<*-_-*::#c9b16d>::operators>::operators>::operators>::operators>::operators>//This is Brucie! He has mighty cards as his weapon.
(_(_(_(_(_)_)_)_)_)// And this is Morsie! He doesn't do much, but he distracts kumquats with his unique Beepolese language.

I can imagine some trolls mass reporting newbies

Please only create new threads here if you're a New Scratcher introducing yourself the community. Check out [url=https://scratch.mit.edu/discuss/topic/399690/]Making a guide/welcome topic? Please read this first![/url]

Hello!  It's great that you want to help out other Scratchers.  However, I think we have enough guides in the forums at the moment.  Please feel free to welcome new Scratchers on [url=https://scratch.mit.edu/discuss/topic/4670/]the group welcoming topic[/url] or on individual topics created by New Scratchers.

Other places that can always use more helpful Scratchers like you, are the "[url=https://scratch.mit.edu/discuss/7/]Help With Scripts[/url]" and "[url=https://scratch.mit.edu/discuss/4/]Questions About Scratch[/url]" areas - please use them as designed, by responding to topics created by folks with problems to solve :)

Finally, a really good place for Scratch guides is the [url=https://en.scratch-wiki.info/]Scratch Wiki[/url] - check it out and see if it's something you might like to work on.   They have a number of guides - and great organization.

Crow_Boy08 wrote:

so if i have 0 it will auto take it down?
No support

TheClaw7654 wrote:

What about a person with 0 followers?

How will they be able to share projects

No, we did not talk about 0 but I think 2 or 3 reports are enough for persons under 20 followers.
Its a group system:

Group 1 (0-20 followers): like 3 reports
Group 2 (21-80 followers): like 4 reports
Group 3 (80-120 followers): like 6 reports

and then 1 more report per 30 followers.

YtArie5 wrote:

I can imagine some trolls mass reporting newbies

Well, I never heard of that but it is possible.

YtArie5 wrote:

I can imagine some trolls mass reporting newbies

Exactly. Although, with enough kindness, you can get more than 40 followers (like me) and workaround these limitations.

YtArie5 wrote:

I can imagine some trolls mass reporting newbies

Also with just 3 reports req rn it can already happen rn if thats true

Crow_Boy08 wrote:

so if i have 0 it will auto take it down?
No support

TheClaw7654 wrote:

What about a person with 0 followers?

How will they be able to share projects

Its like I said spli t into classes for example 0-20 followers need like 3 reports and then going on but not like 0 followers autotakedown…

YtArie5 wrote:

I can imagine some trolls mass reporting newbies

The root cause of mass reporting is jealousy, I don't understand how can a troll get jealous of a newbie with 0-20 followers.

(☆ ᴗ ☆:: custom-arg) // Here is FARFR, He stands for Frequently Asked Reasons For Rejection and protects my topics and my signatures.

Here's the game I worked on the most..ㅤ:: variables :: hat

Scratch_NT wrote:

No, we did not talk about 0 but I think 2 or 3 reports are enough for persons under 20 followers.
Its a group system:

Group 1 (0-20 followers): like 3 reports
Group 2 (21-80 followers): like 4 reports
Group 3 (80-120 followers): like 6 reports

and then 1 more report per 30 followers.

There is a problem with the system you described….

Someone with 1000 followers might share the link to a social media site (which not many know is against the community guidelines) would take 35 reports to take it down, it isn't very practical to get 35 of your followers to report a project, nor is 1 or 2 reports at different times going to be enough to catch the ST's attention…

So on that note, the limits need to be a bit overstretched,
Maybe the limit should be +1 report to take down a project every 200 followers, to keep it fair.

Other than that, I see no problem in the suggestion, it could help get mass reported projects just above the auto-takedown line, provided that a well-thought off limit is agreed upon.

(☆ ᴗ ☆:: custom-arg) // Here is FARFR, He stands for Frequently Asked Reasons For Rejection and protects my topics and my signatures.

Here's the game I worked on the most..ㅤ:: variables :: hat

No support because this would be unfair for new people getting started with scratch and things it should do and not do. Plus the amount of fame could mean that they could act nice in the first time but then they would act mean and then people would have no choice but to mass report them which is not allowed. Also some random troll could report them (said here)
The only benifet I see here is reporting new inappropriate trolls which I don't see often.

There could be a chance I would misunderstood the post so if I did please remind me.

Bump…

(☆ ᴗ ☆:: custom-arg) // Here is FARFR, He stands for Frequently Asked Reasons For Rejection and protects my topics and my signatures.

Here's the game I worked on the most..ㅤ:: variables :: hat

Great idea! Let’s also limit users with under ten followers to have to accept every FOR request, so they know their place! Not like thats unfair to them.
Besides, what if someone gets a lot of followers, but never from projects, then they start trolling? Here, i asked Text Complete on OpenAI to help with the idea:

Changing the amount of reports needed to take down a project on Scratch is a bad idea for several reasons. First, it sets a dangerous precedent. Scratch is a platform that encourages a creative and collaborative spirit, and allowing users to take down projects with fewer reports sends the message that such a spirit is not valued or respected. This sets a dangerous precedent and could lead to a decrease in project creation and collaboration.

Second, it undermines the integrity of the Scratch community. Scratch is a platform that values user feedback and collaboration, and by allowing projects to be taken down with fewer reports, users are deprived from their right to provide meaningful feedback and discussion. This can lead to a decrease in the quality of projects, as well as an overall decrease in user engagement.

Finally, it undermines the purpose of the Scratch platform. Scratch was created as a platform for users to create and share their projects, and allowing users to take down projects with fewer reports sends a message that the platform is more focused on censorship and control than creativity and collaboration. This undermines the entire purpose of the platform, and could ultimately lead to a decrease in user engagement and project creation.

Overall, changing the amount of reports needed to take down a project on Scratch is a bad idea. It sets a dangerous precedent, undermines the integrity of the Scratch community, and undermines the purpose of the platform. For these reasons, it is important that Scratch maintains its current policy of requiring multiple reports before a project can be taken down.

GIitchInTheMatrix wrote:

Great idea! Let’s also limit users with under ten followers to have to accept every FOR request, so they know their place! Not like thats unfair to them.
Besides, what if someone gets a lot of followers, but never from projects, then they start trolling? Here, i asked Text Complete on OpenAI to help with the idea:

AHHH, ROBOTS ARE TAKING OVER EVEN THINKING

Exactly! In agree completly.

sheesh, ChatGPT is advanced

when green flag clicked
wait until <(signature) = (nearby)> = [true]
if <(username) = <not <inom5962dojo>>> then
repeat until < <(signature) = (nearby)> = [false] >
play sound [CHOMP v] until done
eat singnature
end
end

when green flag clicked
forever
if <<(evil kumquat) = (nearby)> = [true]> then
repeat until (<(evil kumquat) = (nearby)> = [false])
attack kumquat
say [Leave]
end
end
end

No support, what if someone with 1000+ followers got hacked?
It would be hard to take down the bad projects because of the high follow count.

When (::red) clicked :: events hat
repeat until <key [all v] pressed?>{
destroy this sprite::control cap
when @greenFlag misclicked::events hat
become idiot::custom}::control
(╯°□° ╯︵ ┻━┻::red)::#000000 reporter//this is brad, he creates cursed scripts like the one you saw above
(ㆆ_ㆆ)//this is max, he stares at you with that expression if you say you don't support my suggestion

So basically you want it to be easier for trolls to target new scratchers?

How about instead of follows, we base it on views?
Because I have over 600 followers, with at least 75% of those either inactive or following too many other people to notice.
So if I were to post something inappropriate, I would have an advantage since it would take a lot more reports to auto-block lil' ol' irrelevant me.
And conversely, someone with like 2 followers who suddenly gets featured or curated would take a lot less reports.

Or maybe have a hybrid of both? Maybe take into consideration both the amount of views AND the follower count of the person?
Because basing it just off of followers would make an uneven playing field.

When [Post v] :: #ffd900
if <(Kumquats available?  :: #00ff7b) = <True :: #517d48> :: #d642e3> then :: #00e32d
Make evil kumquats :: #00d5ff
end
Haha invisible block go brrr :: cap :: #ffffff

(((((I reside in the ((Questions About Scratch :: #00e8a2 stack) :: #00e8c1 stack) and ((Suggestions :: #00e8a2 stack) :: #00e8c1 stack) forums :: #ff0073) :: #ffae00) :: #ffd500) :: #00ff2a) :: #0095ff) :: #8c00ff hat
I spend a bit of time everywhere <Except the wiki :: #94634a> :: #dd00ff cap

(_/(._. v)|_ :: #0051ff) :: #55ff00 hat  // This is an unnamed servant that restocks on kumquats constantly
As long as Signal (When gf clicked :: #ff0059) [given v] { 
Produce Kumquats :: #08d16d
} :: #9a0f2a
I enjoy [Among Us v], [FNF v], [Roblox v], [Memes v], [Object Shows v], and [Anthropomorphic animals v]:: #08b0d1 cap

Yellowsheep43 wrote:

How about instead of follows, we base it on views?
Because I have over 600 followers, with at least 75% of those either inactive or following too many other people to notice.
So if I were to post something inappropriate, I would have an advantage since it would take a lot more reports to auto-block lil' ol' irrelevant me.
And conversely, someone with like 2 followers who suddenly gets featured or curated would take a lot less reports.

Or maybe have a hybrid of both? Maybe take into consideration both the amount of views AND the follower count of the person?
Because basing it just off of followers would make an uneven playing field.

I think that's better….

(☆ ᴗ ☆:: custom-arg) // Here is FARFR, He stands for Frequently Asked Reasons For Rejection and protects my topics and my signatures.

Here's the game I worked on the most..ㅤ:: variables :: hat

The_Blue_J wrote:

Yellowsheep43 wrote:

How about instead of follows, we base it on views?
Because I have over 600 followers, with at least 75% of those either inactive or following too many other people to notice.
So if I were to post something inappropriate, I would have an advantage since it would take a lot more reports to auto-block lil' ol' irrelevant me.
And conversely, someone with like 2 followers who suddenly gets featured or curated would take a lot less reports.

Or maybe have a hybrid of both? Maybe take into consideration both the amount of views AND the follower count of the person?
Because basing it just off of followers would make an uneven playing field.

I think that's better….

Better, but still silly, this is completly unneccesary sugesstion.

when green flag clicked
wait until <(signature) = (nearby)> = [true]
if <(username) = <not <inom5962dojo>>> then
repeat until < <(signature) = (nearby)> = [false] >
play sound [CHOMP v] until done
eat singnature
end
end

when green flag clicked
forever
if <<(evil kumquat) = (nearby)> = [true]> then
repeat until (<(evil kumquat) = (nearby)> = [false])
attack kumquat
say [Leave]
end
end
end

insert op here

What if Griffpatch posted a project that breaks the community guidelines? How many reports would that have to be? (Keep in mind he has over 400k followers!)