What is the point of these? Let us consider "False Report or Announcing Report [Warn]" for instance. Janitors cannot distinguish between repeat offenders, so if someone repeats this offense, I assume they will just keep getting the same warn messages?Curiously, "Announcing Sage" is a ban template.
>>9309sage
I'm just interpreting here, but I think it's just a consequence of the limited information we have as jannies.The "False Report or Announcing Report [Warn]" template may be restricted to a warning because janitors can ONLY use that template on posts, we can't request to warn on ban users for false reporting because we can't see information on reporters, there's just no mechanism for it. Which means we can only apply that template to the "announcing report" part, and I assume mods consider announcing that you reported a post to only be a minor offence worth warning for.>Janitors cannot distinguish between repeat offendersWe are not expected to, and we can't tell (even if it might seem obvious) if the same user is announcing several reports. If a user has a history of announcing reports then maybe a mod would consider it worth upgrading to a ban, but that's not known to us and therefore there's no reason to give us access to that template as a ban.In my experience 90% of the time a user announced they reported a post, I can't see a report for that post in the queue, so they're not even making the actual false report (and even if there is we don't know the reporter and the person announcing it are the same user), so we can't request bans for false reports on that basis. Because we can only see limited information on reports we can only manually link reports to a mod to ask them to check for false reports, this mostly applies to false illegal reports which I think are usually bans. But from what I've seen a user won't get punished for a false report unless there's an obvious pattern of report abuse (spamming reports on obviously non rule breaking posts), or egregious violations (false illegal reports). Again I'm just guessing here but it's probably because we'd rather have a few false reports go unpunished, than be punishing users for false reporting and then dissuading them from reporting any posts at all, which makes our job harder.
As for announcing sage, I've been told it used to be a bigger problem, with people using it to announce their "downvote" on the thread. I don't see it much, but as announcing sage is an obvious thing that jannies can see, we are given the freedom to decide if we think the violation is worth a warning or a ban based on the severity. But it having the ban option might just be a leftover artifact from when it was a more widespread issue.And with other warn only templates like GR6, again it's an issue of us just not being able to see larger patterns of rulebreaking, and it's probably considered a minor enough offence that single instances aren't worth a ban. If a single user is obviously breaking GR6 repeatedly in a single thread (and you can verify with the pending BR message) it may be more appropriate to use the GR10 template instead because filling a thread with copypasta/gibberish/ASCII would easily qualify as spamming/flooding.I don't know if there any board specific warn-only templates, but if there are it might be for similar reasons.
>>9312Announcing sage was a larger problem when sage was first made invisible. In ye olde days, the options field was the email field, its contents were visible to other users in case you wanted to leave contact info, and it served dual purpose of allowing for options like sage (don't bump), noko (returned you to the thread after posting; the default behaviour was that after posting you'd be returned to page 1 of the index).At some point in our history, the email field got repurposed as the options field, because who the FUCK leaves their email address on 4chan, and that had the side effect of hiding sage. Users began announcing sage more frequently.
It's best to understand the ban request templates as basically boxes we're supposed to sort things into. And by "we", I include mods in this. While they can custom warn/ban as needed, ultimately we're all just putting the round peg in the round hole.
>>9315>he doesn't put the round peg in the square hole
>>9323She always gets upset when I try that.
>>9378>she
