46

We've (by "we" I mean "Jarrod") officially added this functionality to the UI, pretty much exactly the way Manishearth and Ilmari Karonen envisioned it. Note that the user still is not notified of the results of a flag they cast, so they won't see this feedback unless they go looking for it. For those diligent flaggers who do look, though, they'll now ...


43

TLDR: Adding feedback is always a good idea since it helps the reviewer to get better at flagging. Better flaggers means a better site to work with! If there is one thing people hate, it is to be clueless about the reasons behind something. This feature will improve the communication between the moderators and flaggers. Educating users The ping notification ...


23

Oded graciously worked on this request along with several other improvements to the flag history page. You are now able to filter your flag history.


18

Two reasons, the first is just a backlog. There are almost 700 flags soaking in the moderator queue right now, so I suspect you'll see many of them acted upon in the next day or so. While the mods do check the queue and handle serious issues over the weekend, it's not unusual for less urgent flags to be processed during the week since folks have other stuff ...


18

This is minor, but when I first saw the new design, I thought the > was a dropdown. (Compare the dropdowns in the 10k tools.) Therefore, I think the arrow should be a different character, maybe a bullet point.


16

While we're at it, you might as well add categorizing by flag type. It'd be nice to see all of my interesting 'other' flags, helpful or not, without having to wade through the huge mass of 'not an answer' flags.


16

You're casting Recommend Closure flags, which moderators do not ever see. They only go to the Close Votes queue. So why is it taking so long? Well, it completely depends on which question you're flagging for closure. The Close Votes queue is currently "fuzzied" which means that only questions with a certain threshold of flags and close votes combined will ...


13

Your total "helpful flags" count: is the sum of your helpful moderator, spam, offensive, and comment flags: Which map onto the flag dialog thusly: (1*) close flags are only available below 3k rep, when they become close votes. And comment flags are not from the dialog with the others, they appear when you hover your mouse over a comment below a ...


13

When a post is recent, there is a good chance you are not the only one looking at it. If other users see the problem that you are seeing, they will vote to close, perhaps independently of your flag. This leads to the question being closed, which automatically marks your flag as helpful. When a post is several years old, there's a good chance you are the ...


13

Go to your profile and click on the helpful flags link. You will see the flagging history and be able to find out what was helpful and what was rejected. This helpful flags link is currently located in the Impact box of the Activity tab of a profile.


13

Retracted flags, for the purpose of accounting, are neutral. There are too many explanations for why a flag may be retracted for anyone, the system or moderators, to guess at it. For example someone could retract a flag because: They changed their mind about which flag to use and cast a different flag instead after retracting. They decided the flag wasn't ...


12

Jarrod and Oded are performing a very large refactor of how flags are stored in the database as I write this, hopefully going live in the next week or two. It's a huge set of changes, a multi-month project (which is pretty damn rare around here). Once that goes live we'll take another look at this. As it stands those comment flags are stored in an ...


12

Given that a user's flagging performance is now evaluated based on flags handled recently, this feature, or something similar, is absolutely necessary. If a user has enough flags declined in the last 7 days, they will begin to receive a warning message to review their recent flags before proceeding. This is designed to make the user check out their recent ...


11

I've written a userscript that utilizes nicael's pagination/sorting bookmarklets to add this to your flag page: Just be careful not to click the buttons too fast – because you're requesting every single page of flags, SE might IP rate-limit you for a few minutes. However, it only happened to me once, and I must have clicked those buttons 50 or 60 times with ...


11

Robert Cartaino analyzed this request and recommended the indentation (SOLO's alternative suggestion) as a clear indicator of the list's dual-level nature. I decided to implement this using Stacks' second-level navigation pattern, as seen in the network's legal documents: This is live right now here on Meta; barring issues, it should appear everywhere ...


11

This has been reverted for the time being. To quote Yaakov: This fix has been temporarily reverted - we need to better define the flag types to which this applies. Will update here when we have further changes


10

It turns out that technically, this is already possible — there's just no user interface for it. That is to say, there's no official user interface to it. Manishearth, however, wrote a bookmarklet to add one, and I took his code (with his help and permission, of course) and integrated it, with a few tweaks, into version 1.6 of the Stack Overflow ...


10

I think it's just the great idea. I made a script which will load all of your helpful/ declined/ disputed flags. To use, first go to your flags history (http://{some-se-site-there}.stackexchange.com/users/flag-summary/your-id). Then run one of the following scripts. To show declined: javascript:var pn=parseInt($(".pager.fr > a:nth-last-child(2)").attr(...


10

Effective immediately, you will now be able to filter your declined flags by using links in the sidebar stats. By clicking on declined, your flag history will show only those flags.


10

A long time ago, both types of flags had the same type of behavior. Both would place the post into the respective community review queue and the private moderator flag queue: If review comes to a positive consensus or if the flag is manually reviewed by a moderator who decides the flag is correct, the flag is marked helpful. If community review disagrees ...


9

Oded was nice enough to implement this in the latest build. We don't have percentages, but we've added an indicator/underline for each category. The history now looks like:


9

It is not a bug, it is by-design. The helpful flags count (86) on your profile page is the sum of all your flags which were deemed helpful (79+4+3). In your case, the number of helpful flags and total moderator attention flags raised by you happen to be the same (coincidence). 3 waiting for review + 79 helpful + 2 declined + 2 disputed = 86 moderator ...


9

moderator attention flags - total number of flags you have cast. waiting for review - amount of flags that are still active/not handled, i.e. waiting for review by moderators. (they might also get disputed) deemed helpful - total amout of flags that were marked as "helpful" by the moderator handling them. declined - total amount of flags that were declined ...


9

There are actually two pages that have the header "Flags for $name$" and that actually makes this even more confusing if you're a moderator - because the other page can only be viewed by the moderators on the site. A user's flag history - the flags they have raised and their status. /users/flag-summary/[userID] A user's flagged posts - the post flags raised ...


8

That indicates numbers of answer on the flagged question*. It will not show anything if: The flagged question doesn't have any answer. The flagged post is an answer. (just hover on that number)


8

Useless comments ought to be flagged (flag the post with a custom comment asking for "comment cleanup" or something). Comments are only for improving the post. If a comment will not aid in improving the post, or has already been incorporated, flag it. (generally it's "chatty" for the first case, "obsolete for the second"). For a whole thread of useless ...


8

It's a bug in the rendering of that specific flag type. After a period of time, flags that are not acted upon by mods or other community members will get cleaned up automatically by internal scheduled tasks. This prevents flags from accruing over time and allowing actions that the greater community in general doesn't want. This cleanup process can also ...


Only top voted, non community-wiki answers of a minimum length are eligible