It will be sent to the Scratch Team, sort of like a report, and if they find it is not bad, then they will fix it and possibly lift the mute (if it's a comments section).
This option will be anywhere the filter bot is, like comments, descriptions, titles, forums, etc.

Mockups (by hydrofungus):



There will be a cooldown as well, so if you make a report, then you won't be able to make another one, for example, 20 minutes. (thanks to cactus-cacti)

huge support. This would help a ton.

more work for moderators.
would the comment/post in question be posted once it is cleared?

Xzillox wrote:

more work for moderators.

No, in fact, it would be even less work. People wouldn't have to post their filterbot bugs to Contact Us, which at this point is just Questions About Scratch but private. Having a more specialized queue would be helpful for moderators to spot and resolve filter bugs faster

But then again, I've seen Paddle2See just fix filter bugs wherever he sees people asking on the forums

ajskateboarder wrote:

Xzillox wrote:

more work for moderators.

No, in fact, it would be even less work. People wouldn't have to post their filterbot bugs to Contact Us, which at this point is just Questions About Scratch but private. Having a more specialized queue would be helpful for moderators to spot and resolve filter bugs faster

But then again, I've seen Paddle2See just fix filter bugs wherever he sees people asking on the forums

That's true. Ideally, the queue would have a way for moderators to easily report a bug to the people that fix bugs to save even more time.

support, i've seen scratchers that were falsely muted SO MANY TIMES that they were banned from commenting at their school
MASSIVE SUPPORT
also it would make contact us less cluttered so actual important stuff like ban appeals could be seen.

ajskateboarder wrote:

Xzillox wrote:

more work for moderators.

No, in fact, it would be even less work.

No, it would definitely be more work. More reports to look through.

Especially since most moderators would not be able to look through such a report queue. When I was a Scratch Team member, I and most other moderators had to suggest filter changes ourselves to another Scratch Team member — we did not have direct access to the filterbot.

So for this suggestion, either an extremely small subset of moderators would have to sort through this filter-report queue themselves, which adds to their already-large workload (keep in mind that there may be more filter-reports than regular reports due to how easy it could be to get muted/filtered), or we could have regular moderators sort through the filter-report queue and forward issues to the other Scratch Team members — but that takes attention away from the reports that require more immediate attention.

I feel like there is an issue we are ignoring, false reports

These would increase the workload of moderators significantly, but would it even be worth it? I bet at least 30 percent of them will be incorrect, and taking into account the convoluted method of accessing the filterbot that Chary mentions here, it would overall be more work with little to no benefit. I support ONLY if these issues can be fixed.

Implemented, this can already be done with 3.0 pages, and it will when 2.0 pages convert to 3.0 (hopefully soon xd)

-Rodri wrote:

Implemented, this can already be done with 3.0 pages, and it will when 2.0 pages convert to 3.0 (hopefully soon xd)

How so?

Za-Chary wrote:

No, it would definitely be more work. More reports to look through.

But it won't be nearly as many reports as actual reports.

But most mutes last like 5 minutes anyway and I doubt Scratch can get to your report that fast. And this would increase false reports heavily, and also way more work for the moderators.

jumpship wrote:

-Rodri wrote:

Implemented, this can already be done with 3.0 pages, and it will when 2.0 pages convert to 3.0 (hopefully soon xd)

How so?

I got muted recently (I will be better in the future, but it was by accident anyhow), and on the message saying “you've been muted for 10 minutes” (not in the inbox) you can press “learn more” and it will take you to a slideshow of why you got muted (not being respectful, using mean language etc.) and then in the last slide, it says “”think this was a mistake?" And then a spot below where you can write about how you think it was a mistake.

-Rodri wrote:

jumpship wrote:

-Rodri wrote:

Implemented, this can already be done with 3.0 pages, and it will when 2.0 pages convert to 3.0 (hopefully soon xd)

How so?

I got muted recently (I will be better in the future, but it was by accident anyhow), and on the message saying “you've been muted for 10 minutes” (not in the inbox) you can press “learn more” and it will take you to a slideshow of why you got muted (not being respectful, using mean language etc.) and then in the last slide, it says “”think this was a mistake?" And then a spot below where you can write about how you think it was a mistake.

REALLY OHMYGOD?? I had no clue of this,,, guh,,,,

Your comment silently gets reported to the Scratch Team when you muted, so the ST can check for filter bot problems, but the silent reports are also important for seeing if you were actually trying to post a really bad comment.

jumpship wrote:

Za-Chary wrote:

No, it would definitely be more work. More reports to look through.

But it won't be nearly as many reports as actual reports.

I'm not sure that I believe you; people get muted quite often. Wouldn't it be pretty easy to just submit a quick mute-report every single time someone gets muted? And that's not just the actual mutes — you say that this suggestion also applies to things like project descriptions, which people don't get muted for, so there would be plenty of filter-reports for this, too.

I was going to mention that in my first post, but I didn't, because I'm not sure myself if it would be true that there are more (or less) filter-reports than regular-reports.

Regardless of that, however, what you cannot deny is that the amount of regular-reports plus the amount of filter-reports will be greater than just the amount of regular-reports — and so adding filter-reports will still create more work for the Scratch Team.

EDawg2011 wrote:

Your comment silently gets reported to the Scratch Team when you muted

I'm curious if you have a source from a Scratch Team member stating this.

Za-Chary wrote:

EDawg2011 wrote:

Your comment silently gets reported to the Scratch Team when you muted

I'm curious if you have a source from a Scratch Team member stating this.

I didn't, but here's a post from another Scratcher.

-Rodri wrote:

Implemented, this can already be done with 3.0 pages, and it will when 2.0 pages convert to 3.0 (hopefully soon xd)

^^^
GUYS

-Rodri wrote:

-Rodri wrote:

Implemented, this can already be done with 3.0 pages, and it will when 2.0 pages convert to 3.0 (hopefully soon xd)

^^^
GUYS

Let me try cursing on my alt

Edit: i can indeed confirm because i said a certain type of wine twice


Sorry for big pictures

sometimes my forum post doesn’t go through for literally no reason

and this happens a lot when I say the name of a perfectly appropriate and safe to use browser with I won’tcan’t name for obvious reasons
like why


and I don’t always feel like going through the tedious process of contact-us

So this would be useful