Quote from: Csmiami on Today at 01:48:15 PM

I'm not particularly worried about the accuracy, 34 bads out of 2704 is not really a problem, but it's more of a psicological punch that could easily be avoided. I don't see how it could become a problem if it only warns you about you having reported that post before (sorry if that wasn't clear enough on OP).

I totally understand your point of view as Loyce rightfully described as a "stab in the back" for trying to do the right thing. In the beginning I also felt the same way and for sure I haven't reported the massive numbers that you guys have - 610 posts with 96% accuracy (576 good, 29 bad, 5 unhandled) - but the thing is that after a while I went from just "reading" the phrase that is presented to us - Do not worry about your accuracy too much; one accurate report is worth many inaccurate reports. - to really think about it and what it made me (unbeknownst to me) do. Whenever I was in doubt that a particular post was or not following the rules ( because I was either too new or didn't study/comprehended the rules as much) I would just fire it away and see how it went. Turns out 29 of the 610 times I was bad at judging, but I honestly can't measure the other KPI (if we may call it that) that isn't being stored - The posts that I wasn't sure if they were "report" worthy but that, in the end, were. And even thought the doubt that I had at the time, I went forward because at the end of the day we're fighting the good fight.

Yes, from the psychological side of it having this information right in front of our eyes whenever we're reporting may take a toll on us - But at the end of the day what would we prefer? To report and never know what % of them were effective (would happen with no information regarding bad reports and unhandled) or a system similar to the one that you've suggested that would be an additional benefit to the already good report history function that (some of us) have? This leads me to your next good observation:

Quote from: Csmiami on Today at 01:48:15 PM

When you're right, you're right. However, adding a reason to be marked as bad is a "manual" thing to do. This would be completely automatic, implying an additional of 0 units of effort from the staff; except implementing the function.

I don't know how hard that it would be to implement this feature in our forum - after all we do know the struggles that there are whenever a new feature is trying to be implemented in SMF - but I do believe that whoever judges/evaluates these requests always sees them from different perspectives such as (but not limited to) :

Is the suggested proposal being done on a already broken/bleeding system? Or the system is standing by itself (it may have it's downsides) and we're just talking about a quality of life/ nice to have feature?
Who would that feature impact the most? All users? Some users? 20 % of the users?
Is it aligned with the current goals that we - as a team running the "show" - have for the future of the community? Is it something that could attract more users to a particular behavior (in this case reporting) that would be positive for the forum?
What would be the side effect of it? Would it be transformed in additional work towards our staff members?

Lookg these were just some ideas - some may even be incorrect/stupid - that came to my mind on this subject. I think that the addition of a "color" or "warning" to a reported post/thread would be good - because we often get lost in the threads reported - but I'm unsure if the time that would have to be dedicated to create could be better used elsewhere (but I guess that's the life/decisions that admins/staff have during the course of a forum life). Take, for example suchmoon perspective:

Quote from: suchmoon on Today at 12:51:53 PM

I would prefer to get an explanation why it's bad (could be short, picked from a list of 3-4 predefined reasons). If it's my cock-up that's fine, but if it's something mods didn't find proof of then maybe I need to resubmit a better report, or if it's something that's not considered against the rules that'd be helpful to learn too.

Other than that, an occasional bad report is not worth worrying about.

I would be really thrilled to have this feature as well, but I think that it would be an additional action that the mods would have to make even if we're talking about just a click on a few already pre - established options. Imagine getting hundreds of reports per day and having already the work to deal with them (and to classify them as good or bad - even thought this may be automatic whenever the thread is deleted or not) and give an explanation for it (from the available options). What if the reason isn't listed and the mod would have to answer "N/A"? I think that we would be back at square zero after all this work even though there are very compelling arguments given by the community.

So now you say - "-Alright old fox what do you suggest?" - and the truth is that I don't have a direct answer to give you. I do know, for a fact, that the "[HACK] One-click mod report, not for the faint of heart"[1] extension made my suchmoon provides a similar feature - even though it's not permanent (it stays active only if the reported post tab is left open):

Quote from: suchmoon on January 29, 2019, 12:09:55 AM

-snip-
If the code succeeds it will add a yellow border on the left side of the post being reported, if it fails - a red one. Styling is configurable in bct-content.css. o_e_l_e_o created a custom stylesheet for a "blend in" look-and-feel.
-snip-

As a theoretical exercise, would it be possible to keep some sort of "internal" log of our reported posts and whenever the page loads the extension would check the post id (?) within the code and if found edit the css to red? Assuming it works (and that someone would be willing to make it work) this could be implemented by whoever wanted this feature. Don't take me wrong - I'm not dictating which improvements should be made, I'm just wondering if it would be something possible to me made.

As an honorable mention, since we're talking about the reporting system and how to better improve our "judging" capabilities and report tools, I can't end this reply without mentioning the incredible detailed post provided by o_e_l_e_o (and then complemented by tranthidung[2]) regading the powerfull Patrol page functionally that may pass unseen for some of us (especially newer reporting members):

Quote from: tranthidung on July 29, 2019, 06:27:57 AM

-snip-
Customize your patrol page

Quote from: tranthidung on September 08, 2019, 01:34:26 AM

I just discovered interesting things on patrol page, so I updated the thread today.

Now, let me presenting what I discovered.

Beside the standard patrol page, that most of us know, at: https://bitcointalk.org/index.php?action=recent;patrol ⁽¹⁾
There is another 'hidden' patrol page, in which posts made in bounty threads disabled by default, at: https://bitcointalk.org/index.php?action=recent;patrol;nobounty ⁽²⁾. I knew about that page by @suchmoon or @Vod, and originally it was disclosed in Russian board.

Generally

The (1) page is overwhelming spam posts, and there is no reason to find spam posts in bounty threads, with abundant proof of authentication or weekly report posts
The (2) page is more helpful, but by default, there are still so many posts over many boards

So, what users can do if they want to limit posts in their interest boards, such as Altcoin Discussions?
There is solution, but users have to manually customize their patrol page. Here is a guide, given by @o_e_l_e_o

Quote from: o_e_l_e_o on February 21, 2019, 05:05:10 PM

Patrol isn't really hidden. You can make a link to it appear at the top of each page immediately above the link to your Watchlist by going to Profile - Forum Profile Information - and checking the box titled "Show patrol link".

What is hidden is that you can customize the patrol link to view other recent posts. Patrol shows the last 200 posts by newbie accounts. If you delete ";patrol" from the link, so you are left with https://bitcointalk.org/index.php?action=recent, you will see the last 100 posts by all accounts. You can also customize this by adding ";boards=x,y,z" on to the end, where x, y, z (and so on) are the boards you are interested in. For example:

https://bitcointalk.org/index.php?action=recent;boards=1 will show the last 100 posts in Bitcoin Discussion
https://bitcointalk.org/index.php?action=recent;boards=7,8,57 will show the last 100 posts in Economics, Speculation and Trading Discussion.

You can also chain this together together with patrol, so for example:

https://bitcointalk.org/index.php?action=recent;boards=1;patrol will show all the posts by newbies on Bitcoin Discussion out of the last several hundred newbies posts. I'm not sure exactly how many recent newbie posts the forum keeps on file to populate this list from, but it's not a huge number (in the region of several hundred) I think, and since the vast majority of newbie posts are spamming the altcoin boards with bounty reports, then usually this will only show you a small handful of posts.

What users have to do (if they want to customize patrol page) are:
- Having a list of interest boards/ sub-boards and their identifying figures of those boards/sub-boards
- Bookmarking the customized patrol page: https://bitcointalk.org/index.php?action=recent;boards=X
- Changing the X-value to their interest boards/ sub-boards at specific timepoints when they want to check spam posts.
Notes:
Users can includes multiple boards/ sub-boards in the customized patrol page
I listed a few boards/ sub-boards and their identifying numbers

Meta: 24
Bitcoin Discussion: 1
Altcoin Discussion: 67
Trading Discusion: 8
Gambling Discussion: 228

-snip-

[1]https://bitcointalk.org/index.php?topic=5103488.0
[2]https://bitcointalk.org/index.php?topic=5169937.0