I'm surprised that I didn't comment on this, and also surprised that there don't seem to be any cons listed. Here's a few for you.

There is the clear “It's more work for the Scratch Team.” Simply dismissing several reports that don't need action taken against is much easier than writing a custom message to every single Scratcher who sends a report. This effort could even be futile if the reporter opts not to receive such notifications from the Scratch Team. We're already flooded with reports — this notification system could make reports take even longer to get to.

There is the concern Scratchers may have if they don't receive such a notification right away. For instance, let us suppose that someone reports a bad face reveal project, and 3 hours later, the project still isn't removed. At the same time, they have not received a notification after those 3 hours. Knowing that they're supposed to get a notification regardless of the outcome of the report, they could send more reports or Contact Us messages asking about it, which isn't ideal. In reality, we could have missed the report, or simply have not gotten to it yet — 3 hours is a pretty short time.

There are the misunderstandings that Scratchers may get if they receive such notifications. I would rather have Scratchers send in reports for things they are not sure about, rather than have them hesitate to send reports on things that may be inappropriate. If someone reports a project with a face in it (thinking it's a face reveal project), and receive the notification that faces are allowed if it's not a face reveal, the reporter could misinterpret what that means. Perhaps they are led to believe that the only bad projects with a face in it are the ones which have “face reveal” in the title (which is not true). This would cause them to not report face projects that should be reported.

There are the concerns that Scratchers get from such notifications. Some of you already know that we send notifications if you report something that wasn't inappropriate, particularly if the report seemed malicious (e.g. reporting a popular game for the reason “this game is not fun”). Send in too many malicious reports, and you could get banned for it. Now, if a Scratcher receives a notice stating that no action was taken on a report, how could they tell the difference between whether this is a “good” notification or a “bad” one? Without much guidance, they may eventually get worried that, due to all these notifications they're getting, they will eventually get banned for sending in “bad reports.” As a result, they don't report anything else, because the alternative would be getting banned. Like I said, I would rather have someone report things they are not sure about rather than be afraid of reporting content.

There are the Scratchers that would keep tallies on such notifications. Let us suppose that @Scratcher1 reports @Scratcher2 for a comment that is actually bad, and gets the “thanks for the good report, we warned the user” message. A week later, @Scratcher1 reports @Scratcher2 again for bad comments, and gets the “thanks for the good report, we warned the user” message. This repeats for the next 3 weeks. By now, @Scratcher1 knows that @Scratcher2 has 5 notifications, and @Scratcher1 is annoyed that @Scratcher2 isn't banned yet (even though maybe @Scratcher1 was banned after 3 alerts in the past). This could lead to lots of angry comments and Contact Us messages that @Scratcher2 should be banned. In reality, maybe they already were, and only for 3 days. Or, the comments that were removed were not as severe as the ones that @Scratcher1 made. As a result, I don't think it's worth publicizing the alerts that other Scratchers get.

I did bring up this sort of thing in a meeting once. Another Scratch Team member stated that other websites did have this feature, but had the problem that users would start to expect these sorts of alerts, and get confused/angry if they didn't get one for whatever reason (whether a moderator didn't get to it yet, or it was missed, etc.). It likely would cause plenty of anger, confusion, and drama — which another user stated but was quickly dismissed.

I was going to suggest a vague response like “your report has been handled” would be more fitting, but I side with just about everything that Za-Chary said.

Support! I've always been wondering if that no-no word comment was removed

Weirdly, once I did get a message about this long long ago, like in April 2020, I reported a project for something and I got a message from the ST saying that there is no issue with this project, I think it depends on the moderator who's reviewing the report?

Chiroyce wrote:

Weirdly, once I did get a message about this long long ago, like in April 2020, I reported a project for something and I got a message from the ST saying that there is no issue with this project, I think it depends on the moderator who's reviewing the report?

I think as well, these messages are mainly for people not to get angry if nothing happened, and to let them know what, and what not to report

Bump because there was a duplicate

Have not read any of these posts besides the original post because there's like 9 pages, so, sorry if this has already been said, but:
Manually writing reasons would be really time consuming, considering reports are already very slow, but an automated message when something is taken down after a report would be a better idea.
Also, alerts/admin notifications are mainly written and read by Moderators to keep track of past incidents (i.e. after a number of alerts, a user gets banned due to repeat offenses). A better option would be literally a message:


Although, I don't even think this would be a great idea because essentially this is naming and shaming - it's like screaming “hey! we saw ur report about <user>, thanks, we blocked <user> and removed their project!! go laugh at them!! hahaha”
I think I like how reports are handled currently, when you report, you just alert the Scratch Team about rule breaking content and they take appropriate action, not sure why the Scratcher who is reporting should need to know – in any case, they can still check the rule breaking content if they have the link saved in their browser history.

Hmmmm… I don't have time to read through all the pages of this topic right now, but I will say that while I agree with what Za-Chary said, there are some instances when this would actually be really helpful.
There is a project which I had reported at least a year ago, and nothing happened for a very long time. I was hesitant to follow up on it too much as I didn't want to spam the Scratch Team, but finally I decided to use the Contact Us button, and sure enough, the ST responded saying that my reports hadn't gone through for whatever reason. I suspect it's because the project was already approved by the ST that my reports didn't go through - since the ST are humans too, and make mistakes, and the report-worthy content was only noticeable if you clicked the “see inside” button - But I digress.
Anyways, I'm kind of torn on whether this would be a useful feature, but I just wanted to give my two cents

Fun_Cupcake_i81 wrote:

the ST responded saying that my reports hadn't gone through for whatever reason.

I'd like to clarify that “hadn't gone through” likely means “The reports were sent and received, but missed/overlooked.” If you get the pop-up that the report was sent, then it really was sent.

As for the suggestion at hand, however, I feel like this would be a bit redundant. You know that the report was not addressed because the project was still up. When the report does get addressed, you would know because the project would be taken down. So why expect a message stating that the project was taken down?