Discuss Scratch

I8D
Scratcher
32 posts

Suggestion: Improve the Project Reporting System

Recently, a lot of famous projects were taken down for no reason because of reports. The current reporting system allows internet trolls to take down projects by just reporting it. This is very wrong, so I am suggesting some ideas about how the reporting system can be improved.

Here are some Ideas. Sorry if there are some flaws, or if some ideas are already in the reporting system. I understand if some or all of these ideas are not viable to put into the reporting system.

- Remove the “other” button for reporting, because there most likely is no other reason.

- If the reports are all different reasons, then do not take the project down.

- if the reports have the same ip address or are from people who falsely reported before, do not count it (or maybe block the IP as well)

- Make it so that only scratchers can report projects, so internet trolls can not just create a new account and randomly report

- Add an anonymous list of reports, so you can report the troll reports

- Automatically tell the person who got reported why they were reported (like the words of the person who reported and selected “other”)

- Prioritize checking popular projects first, as they are more likely to be reported for no reason

- Only take down a project if the project has greater than an amount of reports AND is above a percentage. (So famous projects won't get taken down as easily by trollers)


Studio: https://scratch.mit.edu/studios/26179939/

Last edited by I8D (April 5, 2020 22:14:57)


Some of my projects:

Mr_PenguinAlex
Scratcher
1000+ posts

Suggestion: Improve the Project Reporting System

I8D wrote:

Recently, a lot of famous projects were taken down for no reason because of reports. The current reporting system allows internet trolls to take down projects by just reporting it. This is very wrong, so I am suggesting some ideas about how the reporting system can be improved.

Here are some Ideas. Sorry if there are some flaws, or if some ideas are already in the reporting system. I understand if some or all of these ideas are not viable to put into the reporting system.

1. Remove the “other” button for reporting, because there most likely is no other reason.

2. If the reports are all different reasons, then do not take the project down.

3. if the reports have the same ip address or are from people who falsely reported before, do not count it (or maybe block the IP as well)

4. Make it so that only scratchers can report projects, so internet trolls can not just create a new account and randomly report

5. Add an anonymous list of reports, so you can report the troll reports

6. Automatically tell the person who got reported why they were reported (like the words of the person who reported and selected “other”)

7. Prioritize checking popular projects first, as they are more likely to be reported for no reason


Studio: https://scratch.mit.edu/studios/26179939/
1. There is usually another reason when I am reporting something.

2. What if a project has more than one thing that's wrong with it?

3. What if the people who falsely reported before find something really bad in a project? Does their report not count, so therefore it won't be taken down?

4. What if new scratchers saw something really inappropriate in a project?

5. EDIT: I misunderstood this part of the suggestion. What if someone made a troll report on the troll report?

6. If your suggestion says to remove the “other” option, how is this even going to work?

7. Nothing wrong with this exactly

Last edited by Mr_PenguinAlex (April 5, 2020 21:02:54)


Za-Chary wrote:

And, at the very least, I would discourage others from telling people that they have “blockspammed” in the forums. If it really is spam, just use the Report button and move on.To any forum helper / mini-mod who reads this, when you come across a necropost, I'd suggest doing nothing and instead maybe reporting the topic. If there doesn't appear to be a need for the topic to remain open, ask for it to be closed within the report.I suggest that, instead of trying to respond to these users asking them not to necropost, that you just use the Report button and ask us to take it down due to spam.
whiteandblackcat
Scratcher
100+ posts

Suggestion: Improve the Project Reporting System

I8D wrote:

Recently, a lot of famous projects were taken down for no reason because of reports. The current reporting system allows internet trolls to take down projects by just reporting it. This is very wrong, so I am suggesting some ideas about how the reporting system can be improved.

Here are some Ideas. Sorry if there are some flaws, or if some ideas are already in the reporting system. I understand if some or all of these ideas are not viable to put into the reporting system.

1. Remove the “other” button for reporting, because there most likely is no other reason.
2. If the reports are all different reasons, then do not take the project down.
3. if the reports have the same ip address or are from people who falsely reported before, do not count it (or maybe block the IP as well)
4. Make it so that only scratchers can report projects, so internet trolls can not just create a new account and randomly report
5. Add an anonymous list of reports, so you can report the troll reports
6. Automatically tell the person who got reported why they were reported (like the words of the person who reported and selected “other”)
7. Prioritize checking popular projects first, as they are more likely to be reported for no reason

Studio: https://scratch.mit.edu/studios/26179939/
I mostly agree with @Mr_PenguinAlex.
1. No; it is easier and more user-friendly to have an “other” option, because it makes scratchers feel like what they are reporting is a valid problem. If it wasn't there, and the project had a problem that you'd usually use the “other” button for, they might feel like the project is ok after all, and not report the project, which is not the outcome we want

2. I agree with @Mr_Penguin_Alex; projects that have one problem can often have more, for instance if the user hasn't read the community guidelines.

3. Their reports should count, and I'm sure the ST have a way of taking into account whether the reports are from the same person and whether the person often reports projects falsely. I'm pretty sure you can get banned for falsely reporting a bunch of stuff. (This is NOT a reason to not report things, you won't get in trouble for thinking there's a problem with a project; it's mainly to stop people trolling)

4. New scratchers need to be able to report stuff too. Sure, trolls might occasionally be a problem but that is not an excuse to remove the report button for new scratchers.

5. I'm not sure if this would be allowed, since it can still be considered a breach of privacy. The other point is that if you can see who has reported the project and for what reasons, if #2 was also implemented, users could make projects “slip through the gaps” on purpose, by reporting the project for a different reason, so it wouldn't be taken down.

6. This could lead to worse problems in situations like bullying, because the bully would see that they got reported by the victim and get angrier / threaten to do bad things.

7. There doesn't seem to be anything particularly wrong with this.

Edit: fixed quotes

Last edited by whiteandblackcat (April 5, 2020 03:24:42)



(lol the link sends you to the trailer check it out pleaaaseeeee)
W_Studio
Scratcher
1 post

Suggestion: Improve the Project Reporting System

Mr_PenguinAlex wrote:

I8D wrote:

Recently, a lot of famous projects were taken down for no reason because of reports. The current reporting system allows internet trolls to take down projects by just reporting it. This is very wrong, so I am suggesting some ideas about how the reporting system can be improved.

Here are some Ideas. Sorry if there are some flaws, or if some ideas are already in the reporting system. I understand if some or all of these ideas are not viable to put into the reporting system.

1. Remove the “other” button for reporting, because there most likely is no other reason.

2. If the reports are all different reasons, then do not take the project down.

3. if the reports have the same ip address or are from people who falsely reported before, do not count it (or maybe block the IP as well)

4. Make it so that only scratchers can report projects, so internet trolls can not just create a new account and randomly report

5. Add an anonymous list of reports, so you can report the troll reports

6. Automatically tell the person who got reported why they were reported (like the words of the person who reported and selected “other”)

7. Prioritize checking popular projects first, as they are more likely to be reported for no reason


Studio: https://scratch.mit.edu/studios/26179939/
1. There is usually another reason when I am reporting something.

2. What if a project has more than one thing that's wrong with it?

3. What if the people who falsely reported before find something really bad in a project? Does their report not count, so therefore it won't be taken down?

4. What if new scratchers saw something really inappropriate in a project?

5. Nothing wrong with this part of the suggestion

6. If your suggestion says to remove the “other” option, how is this even going to work?

7. Nothing wrong with this exactly
Agree!
DrGaming_92Games
Scratcher
100+ posts

Suggestion: Improve the Project Reporting System

whiteandblackcat wrote:

-snip-

I think you may be confused for #'s 5 and 6. That would all be anonymous, the offender wouldn't know who reported them.

I8D wrote:

Recently, a lot of famous projects were taken down for no reason because of reports. The current reporting system allows internet trolls to take down projects by just reporting it. This is very wrong, so I am suggesting some ideas about how the reporting system can be improved.

Here are some Ideas. Sorry if there are some flaws, or if some ideas are already in the reporting system. I understand if some or all of these ideas are not viable to put into the reporting system.

1. Remove the “other” button for reporting, because there most likely is no other reason.
2. If the reports are all different reasons, then do not take the project down.
3. if the reports have the same ip address or are from people who falsely reported before, do not count it (or maybe block the IP as well)
4. Make it so that only scratchers can report projects, so internet trolls can not just create a new account and randomly report
5. Add an anonymous list of reports, so you can report the troll reports
6. Automatically tell the person who got reported why they were reported (like the words of the person who reported and selected “other”)
7. Prioritize checking popular projects first, as they are more likely to be reported for no reason

Studio: https://scratch.mit.edu/studios/26179939/

1. There can be a wide variety of reasons that a project could be violating the Community Guidelines. You just simply can't put every possible reason as an option for why the project is being reported. The ST did a good job with this, provide some general offenses and provide an “other” option for anything that may not of come to mind.

2. I understand what you're thinking. While this would help to prevent someone from trying to take a project down it would also prevent other bad projects that do have many violations from being taken down.

3. I think this is already handled by the ST to a good degree.

4. Like my response to #2, this could help but it would have negative impacts on those new to Scratch that find an inappropriate project. They shouldn't just be unable to report it.

5. This is a good idea in theory, but what if someone falsely reports one of those reports, would someone report that report? This seems like we would be in an infinite loop and it would be difficult to keep track of it all.

6. To me this isn't really necessary. If someone is confused as to why their project got taken down they could use Contact Us to enquire about that reason.

7. This seems like an okay idea, my only question is what qualifies as a popular project? Does it have a certain amount of views? what about loves? Favs? Is the age of the project a factor?

Last edited by DrGaming_92Games (April 5, 2020 09:27:06)


-RISEN-
Scratcher
2 posts

Suggestion: Improve the Project Reporting System

I8D wrote:

Recently, a lot of famous projects were taken down for no reason because of reports. The current reporting system allows internet trolls to take down projects by just reporting it. This is very wrong, so I am suggesting some ideas about how the reporting system can be improved.

Here are some Ideas. Sorry if there are some flaws, or if some ideas are already in the reporting system. I understand if some or all of these ideas are not viable to put into the reporting system.

- Remove the “other” button for reporting, because there most likely is no other reason.

- If the reports are all different reasons, then do not take the project down.

- if the reports have the same ip address or are from people who falsely reported before, do not count it (or maybe block the IP as well)

- Make it so that only scratchers can report projects, so internet trolls can not just create a new account and randomly report

- Add an anonymous list of reports, so you can report the troll reports

- Automatically tell the person who got reported why they were reported (like the words of the person who reported and selected “other”)

- Prioritize checking popular projects first, as they are more likely to be reported for no reason


Studio: https://scratch.mit.edu/studios/26179939/

1. Agreed. But ST can add more reporting reasons

2. Disagreed. A project may have more than one thing wrong

3. Partly agreed. But the reporter’s false-report’s amount must at least reach 3 if his report doesn’t count. That can make sure that the reporter’s false-report before is not unintentional

4. Agreed. We must sure that the reporter know the community guidelines well. And being a “scratcher” means that. In other scratch rules, new scratchers can’t propose a project to be featured, use cloud variables, or be FPC either

5. Agreed. Highly agreed
6. Agreed, if ST doesn’t change the “1”
7. Agreed

Here’s some of my suggestions

1. To disallow a same ip reporting a same project twice

2. Don’t automatically remove a project when someone reported it. Remove it after the St confirm it’s unsuitability

Last edited by -RISEN- (April 5, 2020 09:36:39)

MasterAndras
Scratcher
17 posts

Suggestion: Improve the Project Reporting System

DrGaming_92Games wrote:

whiteandblackcat wrote:

-snip-

I think you may be confused for #'s 5 and 6. That would all be anonymous, the offender wouldn't know who reported them.

I8D wrote:

Recently, a lot of famous projects were taken down for no reason because of reports. The current reporting system allows internet trolls to take down projects by just reporting it. This is very wrong, so I am suggesting some ideas about how the reporting system can be improved.

Here are some Ideas. Sorry if there are some flaws, or if some ideas are already in the reporting system. I understand if some or all of these ideas are not viable to put into the reporting system.

1. Remove the “other” button for reporting, because there most likely is no other reason.
2. If the reports are all different reasons, then do not take the project down.
3. if the reports have the same ip address or are from people who falsely reported before, do not count it (or maybe block the IP as well)
4. Make it so that only scratchers can report projects, so internet trolls can not just create a new account and randomly report
5. Add an anonymous list of reports, so you can report the troll reports
6. Automatically tell the person who got reported why they were reported (like the words of the person who reported and selected “other”)
7. Prioritize checking popular projects first, as they are more likely to be reported for no reason

Studio: https://scratch.mit.edu/studios/26179939/

1. There can be a wide variety of reasons that a project could be violating the Community Guidelines. You just simply can't put every possible reason as an option for why the project is being reported. The ST did a good job with this, provide some general offenses and provide an “other” option for anything that may not of come to mind.

2. I understand what you're thinking. While this would help to prevent someone from trying to take a project down it would also prevent other bad projects that do have many violations from being taken down.

3. I think this is already handled by the ST to a good degree.

4. Like my response to #2, this could help but it would have negative impacts on those new to Scratch that find an inappropriate project. They shouldn't just be unable to report it.

5. This is a good idea in theory, but what if someone falsely reports one of those reports, would someone report that report? This seems like we would be in an infinite loop and it would be difficult to keep track of it all.

6. To me this isn't really necessary. If someone is confused as to why their project got taken down they could use Contact Us to enquire about that reason.

7. This seems like an okay idea, my only question is what qualifies as a popular project? Does it have a certain amount of views? what about loves? Favs? Is the age of the project a factor?

I think the reason many Scratchers are unhappy about being falsely reported is that while their project is trending and is gaining a lot of views, it gets taken down automatically. Even when the project is restored hours later, it doesn't appear on trending and probably gets much less views then it would've gotten if it wasn't taken down. I think that is the reason many people are upset.


My most viewed projects:
Pen Platformer: https://scratch.mit.edu/projects/276239027/ (185k views)
Fusion Platformer (100% Pen): https://scratch.mit.edu/projects/360024205/ (160k views)
Scrolling Penformer Engine (100% Pen): https://scratch.mit.edu/projects/280866307/ (101k views)
Rotten Run: https://scratch.mit.edu/projects/269084449/ (97k views)


when green flag clicked
forever
go to [MasterAndras's Profile v]
end
apple502j
Scratcher
1000+ posts

Suggestion: Improve the Project Reporting System

Scratch is actually updating the Project Reporting System. One change was already made to the website - the color is now blue, instead of red!

Upcoming updates will have the “Other” sections improved - if you select Other, a new options appear and you need to choose from these options in order to send.

Fake Options - If the user chooses those, some messages appear saying those aren't valid report reasons, and the report is not sent.
- I don't like this project (answer: Scratch projects are made by people of all ages and levels of experience. If you don't like this project because you feel it can be improved upon, we encourage you to share constructive feedback directly with the creator.Here are tips on sharing constructive feedback: Be supportive and encouraging. Leave a comment telling them what you like, but also what they could do to make the project better. Try to be specific with your feedback. For instance: The controls to move the character did not work.)
- This project does not work (answer: A Scratch project, like any other application, may contain a few bugs. That is expected and completely okay! We encourage you to share any issues you discover directly with the creator of the project. It's also helpful to provide suggestions on how they may improve their project, if possible.)
- This project could be improved on (answer: same as “I don't like this project”)
- This project is too hard (answer: If you feel a project could be easier, we encourage you to share that feedback directly with the creator of the project. Or remix it yourself and make it as easy or hard as you like!)

Real Options
- The project is misleading or tricks the community (you need to answer the question: Tell us more about how it's tricking or misleading people)
- It's a face reveal or is just trying to show someone's picture (you need to answer the question: Scratch allows people to use pictures of their face in creative projects like games, stories, or animations. However, projects that are just a picture of their face, or which focus entirely on their physical appearance, aren't allowed on Scratch. If this is a “face reveal,” or the project focuses on the person's appearance, please click Report.)
- The project doesn't allow remixing (you need to answer: Please let us know where the project says it is not okay to remix — such as in the Notes & Credits, project title, etc.)
- I'm worried about the safety of the creator of this project (you need to answer: It's important that everyone on Scratch remains safe online and in real life. Please let us know why you are worried about the safety of this user.)
- Something else (you need to answer: We encourage you to double check if your report fits any of the other available categories. If you strongly feel it does not, please explain why this project breaks the Community Guidelines)

Last edited by apple502j (April 6, 2020 10:28:17)


OSS Contributor & Translator of Scratch 3.0, Experienced Wikian @ enwiki, Admin @ jawiki
51 Pull Requests merged to LLK repository since April 4, 2018
Speaks English & Japanese

Scratch 3.0のOSS貢献者と翻訳者、英語版ウィキでExperienced Wikian、日本語版管理者
2018年4月4日から、51本のPRがいままでにLLKリポジトリにマージされました
日本語+英語
whiteandblackcat
Scratcher
100+ posts

Suggestion: Improve the Project Reporting System

DrGaming_92Games wrote:

whiteandblackcat wrote:

-snip-

I think you may be confused for #'s 5 and 6. That would all be anonymous, the offender wouldn't know who reported them.

Nope. It's really hard to truly anonymise data and if the ST were going to be able to see who reported a project, then it could be quite easy for people to see who reported what.


(lol the link sends you to the trailer check it out pleaaaseeeee)
Dat_Cellist538
Scratcher
87 posts

Suggestion: Improve the Project Reporting System

You guys! I asked a scratch team member, and they said that even if a project is automatically taken down, a scratch moderator ALWAYS looks at it and if it was a troll report it gets reshared!
Waffle_Iron_Studios
Scratcher
100+ posts

Suggestion: Improve the Project Reporting System

I8D wrote:

Recently, a lot of famous projects were taken down for no reason because of reports. The current reporting system allows internet trolls to take down projects by just reporting it. This is very wrong, so I am suggesting some ideas about how the reporting system can be improved.

Here are some Ideas. Sorry if there are some flaws, or if some ideas are already in the reporting system. I understand if some or all of these ideas are not viable to put into the reporting system.

- Remove the “other” button for reporting, because there most likely is no other reason.

- If the reports are all different reasons, then do not take the project down.

- if the reports have the same ip address or are from people who falsely reported before, do not count it (or maybe block the IP as well)

- Make it so that only scratchers can report projects, so internet trolls can not just create a new account and randomly report

- Add an anonymous list of reports, so you can report the troll reports

- Automatically tell the person who got reported why they were reported (like the words of the person who reported and selected “other”)

- Prioritize checking popular projects first, as they are more likely to be reported for no reason
Studio: https://scratch.mit.edu/studios/26179939/
Maybe the only change would be that it doesn’t get taken down, it stays until the st reviews the report.

Scratch wiki contributor, Unnoticed (mostly), Suggestions menu frequent flyer
How to stay safe from Covid-19 (coronavirus)
MasterAndras
Scratcher
17 posts

Suggestion: Improve the Project Reporting System

Waffle_Iron_Studios wrote:

I8D wrote:

Recently, a lot of famous projects were taken down for no reason because of reports. The current reporting system allows internet trolls to take down projects by just reporting it. This is very wrong, so I am suggesting some ideas about how the reporting system can be improved.

Here are some Ideas. Sorry if there are some flaws, or if some ideas are already in the reporting system. I understand if some or all of these ideas are not viable to put into the reporting system.

- Remove the “other” button for reporting, because there most likely is no other reason.

- If the reports are all different reasons, then do not take the project down.

- if the reports have the same ip address or are from people who falsely reported before, do not count it (or maybe block the IP as well)

- Make it so that only scratchers can report projects, so internet trolls can not just create a new account and randomly report

- Add an anonymous list of reports, so you can report the troll reports

- Automatically tell the person who got reported why they were reported (like the words of the person who reported and selected “other”)

- Prioritize checking popular projects first, as they are more likely to be reported for no reason
Studio: https://scratch.mit.edu/studios/26179939/
Maybe the only change would be that it doesn’t get taken down, it stays until the st reviews the report.

I agree with that suggestion!


My most viewed projects:
Pen Platformer: https://scratch.mit.edu/projects/276239027/ (185k views)
Fusion Platformer (100% Pen): https://scratch.mit.edu/projects/360024205/ (160k views)
Scrolling Penformer Engine (100% Pen): https://scratch.mit.edu/projects/280866307/ (101k views)
Rotten Run: https://scratch.mit.edu/projects/269084449/ (97k views)


when green flag clicked
forever
go to [MasterAndras's Profile v]
end
mthree8757
Scratcher
5 posts

Suggestion: Improve the Project Reporting System

I8D wrote:

I8D wrote:

Recently, a lot of famous projects were taken down for no reason because of reports. The current reporting system allows internet trolls to take down projects by just reporting it. This is very wrong, so I am suggesting some ideas about how the reporting system can be improved.

Here are some Ideas. Sorry if there are some flaws, or if some ideas are already in the reporting system. I understand if some or all of these ideas are not viable to put into the reporting system.

- Remove the “other” button for reporting, because there most likely is no other reason.

- If the reports are all different reasons, then do not take the project down.

- if the reports have the same ip address or are from people who falsely reported before, do not count it (or maybe block the IP as well)

- Make it so that only scratchers can report projects, so internet trolls can not just create a new account and randomly report

- Add an anonymous list of reports, so you can report the troll reports

- Automatically tell the person who got reported why they were reported (like the words of the person who reported and selected “other”)

- Prioritize checking popular projects first, as they are more likely to be reported for no reason


Studio: https://scratch.mit.edu/studios/26179939/

I8D wrote:

Recently, a lot of famous projects were taken down for no reason because of reports. The current reporting system allows internet trolls to take down projects by just reporting it. This is very wrong, so I am suggesting some ideas about how the reporting system can be improved.

Here are some Ideas. Sorry if there are some flaws, or if some ideas are already in the reporting system. I understand if some or all of these ideas are not viable to put into the reporting system.

- Remove the “other” button for reporting, because there most likely is no other reason.

- If the reports are all different reasons, then do not take the project down.

- if the reports have the same ip address or are from people who falsely reported before, do not count it (or maybe block the IP as well)

- Make it so that only scratchers can report projects, so internet trolls can not just create a new account and randomly report

- Add an anonymous list of reports, so you can report the troll reports

- Automatically tell the person who got reported why they were reported (like the words of the person who reported and selected “other”)

- Prioritize checking popular projects first, as they are more likely to be reported for no reason


Studio: https://scratch.mit.edu/studios/26179939/
I wrote: I agree I don't want innocent projects taken down because of reporting and have to be unshared because someone reported it to be funny which isn't fair to that scratcher.
say [STOP REPORTING PEOPLE 4 NO REASON]
4wheelr
Scratcher
13 posts

Suggestion: Improve the Project Reporting System

yeah, but was me and the pee taken down for no reason?
set rotation style [ me confused]

Last edited by 4wheelr (April 5, 2020 15:22:56)

I8D
Scratcher
32 posts

Suggestion: Improve the Project Reporting System

apple502j wrote:

Scratch is actually updating the Project Reporting System. One change was already made to the website - the color is now blue, instead of blue!

Upcoming updates will have the “Other” sections improved - if you select Other, a new options appear and you need to choose from these options in order to send.

Fake Options - If the user chooses those, some messages appear saying those aren't valid report reasons, and the report is not sent.
- I don't like this project (answer: Scratch projects are made by people of all ages and levels of experience. If you don't like this project because you feel it can be improved upon, we encourage you to share constructive feedback directly with the creator.Here are tips on sharing constructive feedback: Be supportive and encouraging. Leave a comment telling them what you like, but also what they could do to make the project better. Try to be specific with your feedback. For instance: The controls to move the character did not work.)
- This project does not work (answer: A Scratch project, like any other application, may contain a few bugs. That is expected and completely okay! We encourage you to share any issues you discover directly with the creator of the project. It's also helpful to provide suggestions on how they may improve their project, if possible.)
- This project could be improved on (answer: same as “I don't like this project”)
- This project is too hard (answer: If you feel a project could be easier, we encourage you to share that feedback directly with the creator of the project. Or remix it yourself and make it as easy or hard as you like!)

Real Options
- The project is misleading or tricks the community (you need to answer the question: Tell us more about how it's tricking or misleading people)
- It's a face reveal or is just trying to show someone's picture (you need to answer the question: Scratch allows people to use pictures of their face in creative projects like games, stories, or animations. However, projects that are just a picture of their face, or which focus entirely on their physical appearance, aren't allowed on Scratch. If this is a “face reveal,” or the project focuses on the person's appearance, please click Report.)
- The project doesn't allow remixing (you need to answer: Please let us know where the project says it is not okay to remix — such as in the Notes & Credits, project title, etc.)
- I'm worried about the safety of the creator of this project (you need to answer: It's important that everyone on Scratch remains safe online and in real life. Please let us know why you are worried about the safety of this user.)
- Something else (you need to answer: We encourage you to double check if your report fits any of the other available categories. If you strongly feel it does not, please explain why this project breaks the Community Guidelines)
Nice! That would be a great improvement!

Some of my projects:

hedgehog_blue
Scratcher
1000+ posts

Suggestion: Improve the Project Reporting System

Waffle_Iron_Studios wrote:

Maybe the only change would be that it doesn’t get taken down, it stays until the st reviews the report.
That is supposed to be the case, but when there are lots of reports the system considers it too dangerous to wait for review. And I'm pretty sure the ST has put a lot of thought into the balance of danger of a bad project and danger of false reports. Completely shifting the balance to one side might seem better from one perspective, but considering all perspectives the current amount and danger of reports for automatic takedown is close to the best balance the ST can get. If there isn't already, maybe they can add an underlying system to give more weight to trusted reports and looking at the relative views on a project before automatic takedown.

ShaNyiah0818
Scratcher
100+ posts

Suggestion: Improve the Project Reporting System

I8D wrote:

Recently, a lot of famous projects were taken down for no reason because of reports. The current reporting system allows internet trolls to take down projects by just reporting it. This is very wrong, so I am suggesting some ideas about how the reporting system can be improved.

Here are some Ideas. Sorry if there are some flaws, or if some ideas are already in the reporting system. I understand if some or all of these ideas are not viable to put into the reporting system.

- Remove the “other” button for reporting, because there most likely is no other reason.

- If the reports are all different reasons, then do not take the project down.

- if the reports have the same ip address or are from people who falsely reported before, do not count it (or maybe block the IP as well)

- Make it so that only scratchers can report projects, so internet trolls can not just create a new account and randomly report

- Add an anonymous list of reports, so you can report the troll reports

- Automatically tell the person who got reported why they were reported (like the words of the person who reported and selected “other”)

- Prioritize checking popular projects first, as they are more likely to be reported for no reason


Studio: https://scratch.mit.edu/studios/26179939/
I'm surprised you're the only person who's really concerned about this bc I was thinking the same thing!!! i'm all in!! Also, they should stop taking down pictures bc all we're doing is a face reveal

Hey it's ShaNyiah0818 here!! I'm the founder of Profile/Logo/Icon orders where we do your pfp!! I am also a founder of the mentors available program where we online tutor it can be scratch learning or educational learning and the service is free!! I also voice act if you need voice actors!! I'm the assistant for the Perfect Pearls shop!! I'm 11, which my birthday is August 18. Do you need tips while we all are going through this rough time, just come to my profile!!!!
I8D
Scratcher
32 posts

Suggestion: Improve the Project Reporting System

ShaNyiah0818 wrote:

I8D wrote:

*snip*
I'm surprised you're the only person who's really concerned about this bc I was thinking the same thing!!! i'm all in!! Also, they should stop taking down pictures bc all we're doing is a face reveal
Uh face reveals are actually not allowed though, for privacy reasons.

Some of my projects:

I8D
Scratcher
32 posts

Suggestion: Improve the Project Reporting System

Dat_Cellist538 wrote:

You guys! I asked a scratch team member, and they said that even if a project is automatically taken down, a scratch moderator ALWAYS looks at it and if it was a troll report it gets reshared!
Yes, but it is still very annoying. It always takes like 5 days before the project is reshared, and the user gets banned for 12 hours. Would you want that to happen to you for no reason?

Some of my projects:

DownsGameClub
Scratcher
1000+ posts

Suggestion: Improve the Project Reporting System

I8D wrote:

Dat_Cellist538 wrote:

You guys! I asked a scratch team member, and they said that even if a project is automatically taken down, a scratch moderator ALWAYS looks at it and if it was a troll report it gets reshared!
Yes, but it is still very annoying. It always takes like 5 days before the project is reshared, and the user gets banned for 12 hours. Would you want that to happen to you for no reason?
Keep in mind that there are tons of similar situations that are going on at the same time - it's impossible for the Scratch Team to deal with everything at once.
No, I would not want my project to be taken down for no reason, but I think it's worth it considering people are willing to share inappropriate projects that go under the radar.

Powered by DjangoBB

Standard | Mobile