mass/false reporting

portalpower

so when a project gets enough reports it gets automatically taken down, so what I want is to change that algorithm

so what I want is when 10% of a projects viewers report it or it gets at least 2-3 reports, the automod thing activates

so yeah

Last edited by portalpower (Dec. 6, 2020 20:49:12)

NanoPIex

Support. People work hard on projects and when they`re taken down it must be a real heartbreak to them.

Last edited by NanoPIex (Dec. 6, 2020 19:44:12)

Futurebot5

No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.

NanoPIex

Futurebot5 wrote:
No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.

Ooh. I`ll change to no support, then.

portalpower

Futurebot5 wrote:
No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.

but if the project is scratch friendly it won't get reported

NanoPIex

portalpower wrote:
Futurebot5 wrote:
No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.
but if the project is scratch friendly it won't get reported

What if it isn`t? If it has few views, this method would get it easily taken down.

portalpower

NanoPIex wrote:
portalpower wrote:
Futurebot5 wrote:
No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.
but if the project is scratch friendly it won't get reported
What if it isn`t? If it has few views, this method would get it easily taken down.

but that's good, if a project has bad stuff it gets taken down quick

Last edited by portalpower (Dec. 6, 2020 20:42:04)

NanoPIex

portalpower wrote:
NanoPIex wrote:
portalpower wrote:
Futurebot5 wrote:
No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.
but if the project is scratch friendly it won't get reported
What if it isn`t? If it has few views, this method would get it easily taken down.
ok then I edit post

What`ll you change?

pandacorn_owl

NanoPIex wrote:
portalpower wrote:
Futurebot5 wrote:
No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.
but if the project is scratch friendly it won't get reported
What if it isn`t? If it has few views, this method would get it easily taken down.

User A doesn't like User B. User B has a project with 2 views. User A reports a project by User B. User B's project s taken down. User A does this to a bunch of projects by User B. User B gets banned. User B is sad.

NanoPIex

pandacorn_owl wrote:
NanoPIex wrote:
portalpower wrote:
Futurebot5 wrote:
No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.
but if the project is scratch friendly it won't get reported
What if it isn`t? If it has few views, this method would get it easily taken down.
User A doesn't like User B. User B has a project with 2 views. User A reports a project by User B. User B's project s taken down. User A does this to a bunch of projects by User B. User B gets banned. User B is sad.

And also that situation. But what did User B do to User A?

pandacorn_owl

NanoPIex wrote:
pandacorn_owl wrote:
NanoPIex wrote:
portalpower wrote:
Futurebot5 wrote:
No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.
but if the project is scratch friendly it won't get reported
What if it isn`t? If it has few views, this method would get it easily taken down.
User A doesn't like User B. User B has a project with 2 views. User A reports a project by User B. User B's project s taken down. User A does this to a bunch of projects by User B. User B gets banned. User B is sad.
And also that situation. But what did User B do to User A?

Say I don't like trees

portalpower

lets stay on topic

NanoPIex

Futurebot5 wrote:
No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.

Do you support now?

Futurebot5

NanoPIex wrote:
Futurebot5 wrote:
No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.
Do you support now?

I support if he makes it at least 10 people report it.

pandacorn_owl

Futurebot5 wrote:
NanoPIex wrote:
Futurebot5 wrote:
No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.
Do you support now?
I support if he makes it at least 10 people report it.

Surely this makes mass reporting far easier. 1 report i enugh for the Scratch Team to review projects. If a project gets taken down after 10 reports that is not that hard to get something taken down.

NanoPIex

pandacorn_owl wrote:
Futurebot5 wrote:
NanoPIex wrote:
Futurebot5 wrote:
No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.
Do you support now?
I support if he makes it at least 10 people report it.
Surely this makes mass reporting far easier. 1 report i enugh for the Scratch Team to review projects. If a project gets taken down after 10 reports that is not that hard to get something taken down.

But it won`t get taken down if it`s appropriate and follows the guidelines.

pandacorn_owl

NanoPIex wrote:
pandacorn_owl wrote:
Futurebot5 wrote:
NanoPIex wrote:
Futurebot5 wrote:
No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.
Do you support now?
I support if he makes it at least 10 people report it.
Surely this makes mass reporting far easier. 1 report i enugh for the Scratch Team to review projects. If a project gets taken down after 10 reports that is not that hard to get something taken down.
But it won`t get taken down if it`s appropriate and follows the guidelines.

Then are you suggesting a project would need 10 reports to be reviewed rather than 1

NanoPIex

pandacorn_owl wrote:
NanoPIex wrote:
pandacorn_owl wrote:
Futurebot5 wrote:
NanoPIex wrote:
Futurebot5 wrote:
No support for that specific fix. If only a few people viewed it, it'd take just a couple reports to take down.
Do you support now?
I support if he makes it at least 10 people report it.
Surely this makes mass reporting far easier. 1 report i enugh for the Scratch Team to review projects. If a project gets taken down after 10 reports that is not that hard to get something taken down.
But it won`t get taken down if it`s appropriate and follows the guidelines.
Then are you suggesting a project would need 10 reports to be reviewed rather than 1

No, Futurebot5 is.

portalpower

bump

Zoomer_X

If someone made a project using swear words, with the

 say []

block, then it would need more than one report to be taken down, then that wouldn't be good.

Discuss Scratch