For example, I sent a report and 3 hours later, I'm very concerned because the bad face reveal project is still shared… and why? I know that this scenario happens a lot.
Maybe, a reason in the mail that the Scratch Team sends to me? There's a lot of similar reports and have the same conclusion. The mockup for this “notice” is this;

I like to thank PUNNAMOODU for this mockup :)

Validate
Hi username, we received your report by

Selected operation

identification for report
Sent from project url or for comments Sent from comment comment url or for studios Sent from studio studio url or for users
report user
Selected reason: (for other than comments)
reason
Description: (for projects only)
user's content

Thanks!

I was thinking about adding a dropbox subjecting to the report kind, so the user may control their mail by custom.

Pros

• Stops confusion
  
• Info on good reports
  

Cons
None that I could think of.
Maybe add to that.

close topic
We closed your/the topic topic name because of it being a duplicate insert link and topic name

close topic
We closed your/the topic topic name by request

close topic
We closed your/the topic nsert link and topic name

notif for owner who's reported content is non purposed
Hi, username lately people have falsely reported your project or studio or comment. The reporter(s) has been notified to stop false reporting your stuff.

Thanks to dhfbei8987 for that

We can eliminate constant mail by giving an interval of three hours.
There will also be a checkbox saying “Notify me when the Scratch Team reads my reports” and "Notify me when the Scratch Team reads my reports that are custom, forum, project, comments.
Thanks to YellowSheep43 for pointing that out

They probably just didn't see it yet.

Futurebot5 wrote:

They probably just didn't see it yet.

What?
Oh, it's just a example.

I've wanted this too. I'd much prefer hearing “we received your report but decided not to act upon the project” over hearing nothing at all and seeing the project stay up. It doesn't make much sense to me, especially since I've reported obviously rule-breaking projects in the past and never gotten any response or action taken at all.

Yes. When I report something and it doesn't get taken down, I always assume that the Scratch Team didn't see it yet, but it'd be nice to know if there was another reason.

Yes this would be very nice to have and I have been in that exact situation before, wondering if the ST just hadn’t seen my report or if the ST thought mass-cyberbullying was ok.

I think everyone would appreciate it if we could know how our reports are progressing, support

Support, It lets you know if the ST reviewed your report and or the project.

I support. I agree with the reasons above ^^^^^^^^

bump
Well, technically…

Big support, because I recently reported something, and would like to know the news about it

Support, it isn’t really constructive from ST to not say why something wasn’t taken down

bump

Support, a lot of other websites do this, so why can't Scratch? It's very helpful to know if my report was read.

gosoccerboy5 wrote:

I think everyone would appreciate it if we could know how our reports are progressing, support

^^

Support, This would make sure that the ST read your report and lowers the chance that a person would say that the ST rarely reads reports, even though they do read reports many times.

Yeah, face reveal projects are obviously bad, so doing this would alert the guy doing to stop.

ThatExplosivePigeon wrote:

Yeah, face reveal projects are obviously bad, so doing this would alert the guy doing to stop.

That's just an example, but that happened ago.

lovecodeabc wrote:

gosoccerboy5 wrote:

I think everyone would appreciate it if we could know how our reports are progressing, support

^^

Please be also share your reason when posting your opinion on a suggestion. The Scratch Team encourages that you're constructive - they implement suggestions based off of the reason you support and not based on the amount of people supporting. If you would like to learn more about constructiveness, you can read about it here: https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/215499/

In this case, you did mention the reason of gosoccer, but being constructive is sharing your own personal opinion to contribute to the discussion as well.

—

Support - I've reported several projects and users and still don't know why some weren't taken down. This will be especially useful for new Scratchers, because they probably report things based on the things they interpreted from the rules. It will be really confusing for them if the projects don't get taken down, and they'll probably assume the website has bad moderation (which, on the contrary, it doesn't have at all).