Add this in the div with the ID “comments”, right at the beginning, before the div with the ID “comment-form” (on Scratch Team member profile pages):

It should look like this:

*note: im not sure if linkign to the bugs and glitches forum is a good idea since more people will discover the forums, and the forums are a very unstable part of the Scratch website, server wise and moderation wise

And I guess around 90% of those reports would be gone. Sure, not all of them, but most of them. That's enough, right?
Well, we could get a little more creative and have the comment section blocked until the Scratcher agrees not to report, or anything more friendly, but that would take a lot more time to implement, and the code snippet I have provided is just a quick fix.

I have seen way too much gossip, naming & shaming, and requests to unblock accounts on Scratch Team member profiles.
And this would also help CheddarGirl not worry about her comment section

You have me, but maybe retitle the topic name as it feels a bit misleading — Maybe to “Warning before commenting on ST profiles”?
Support, maybe people could talk to ST members without going off-topic on their projects (I genuinely feel bad doing it with my main tbh)
EDIT: Maybe finally cut them a bit of slack as well.

Zydrolic wrote:

You have me.
Support, maybe people could talk to ST members without going off-topic on their projects (I genuinely feel bad doing it with my main tbh)
EDIT: Maybe finally cut them a bit of slack as well.

I think I should also add some text for things ike bugs/purple complaints.

i_eat_coffee wrote:

(#3)
I think I should also add some text for things ike bugs/purple complaints.

Yeah thats a good idea so people dont suddenly create raids

perhaps like this?

I support this because you don’t know how many comments I’ve seen on ST profiles along the lines of “That user was mean to me please ban him now!” and it reduces people trying to attack the person who is doing the wrong thing.

i_eat_coffee wrote:

(#5)
perhaps like this?

Yeah sounds good

I think it's okay to report bugs and glitches on a Scratch Team member's profile. If it turns out to be important, they can forward it to the right Scratch Team members.

Naming and shaming is not good, of course, so your suggestion there has merit.

umm you hacking

MinceraftFan wrote:

(#9)
umm you hacking

Uh, please elaborate…?

scratchcode1_2_3 wrote:

MinceraftFan wrote:

(#9)
umm you hacking

Uh, please elaborate…?

I think they’re referring to the HTML XD

medians wrote:

(#11)

scratchcode1_2_3 wrote:

MinceraftFan wrote:

(#9)
umm you hacking

Uh, please elaborate…?

I think they’re referring to the HTML XD

yeah but it's just a mockup lol

or the mods could just turn off commenting

MinceraftFan wrote:

or the mods could just turn off commenting

Which, in fact some like Cheddargirl or Paddle2See already do that. The problem is that if you have a legitimate question to the scratch team then you either have to A) trial and error to find a ST member that has commenting enabled or B) go off-topic in the project comments section. This would aim to make both those paths irrelevant by just having profile comments be open to all ST members and having the page itself do the work.

MinceraftFan wrote:

or the mods could just turn off commenting

This is already done on some profiles, but this is still a problem.
It’s not a good solution just to keep comments closed on all Scratch Team member profiles.

Support as reports will be safe and ST wont have to be worried about reports on their comments

While the mechanics are different, the idea is the same on this duplicate topic:

https://scratch.mit.edu/discuss/topic/491812/

Please use the existing topic in the link above.