A bug was reported in the /admin/reports/user_flagging_ratio report, which is not accurately displaying user flagging ratios. DNSTARS tested the report and found that it was not updating correctly, even after taking actions like silencing, suspending, and hiding posts. codinghorror confirmed that the report appears to be broken. The issue was particularly notable because the site plans to incentivize top flaggers by paying them, and the report is necessary to track their performance.
A fix has been proposed in a GitHub pull request by joffreyjaffeux. The issue was caused by a HAVING clause that prevented users with more agreed flags than disagreed flags from showing up in the results. The fix will also update the scoring system to include users with zero disagreed flags, with their score being the square of their agreed flags.
I’m a little confused about /admin/reports/user_flagging_ratio, either I’m doing something wrong or I think it’s bugged. I’ve tested it with someone who flagged 5 posts, agreed and took no action, this didn’t update so I thought maybe “agreed” needs to be “agreed and took action”, ran the test again silencing, suspending and hiding posts and no update.
It appears to be yes, this section believes our site has had about 25 flags since the new year, anything else that refers to flags on the dash appears ok.
The game plan as we grow is to pay the top 10 “most helpful” flaggers in the community to incentivise and outsource moderating by tweaking flags… That’s how I ended up on that report which I suppose is rarely looked at otherwise.
The issue we had is that to prevent some error we had this HAVING #{disagreed} > #{agreed} clause which is essentially preventing a lot of results to show.
if you have 5 disagreed and 20 agreed, you wouldn’t show in results. This fix also bumps people with 0 disagreed flags, their score will be agreed^2.