Bitcoin Forum

Other => Beginners & Help => Topic started by: RAMSHIVDEEPAK on May 30, 2018, 07:27:50 AM



Title: how can I know about the bad reporting post....
Post by: RAMSHIVDEEPAK on May 30, 2018, 07:27:50 AM
I have this massage in my reporting section.

You have reported 33 posts with 91% accuracy (29 good, 3 bad, 1 unhandled). Do not worry about your accuracy too much; one accurate report is worth many inaccurate reports.

So,if I can know the details the bad reporting,then I can improve my self in future. In my opinion,I have reported only the bad/spam post.Further, I have reported 33 post,So I am not able to find, which 3 posts are not spam post and wrongly reported.

If there is any procedure ,then let me know.


Title: Re: how can I know about the bad reporting post....
Post by: mdayonliner on May 30, 2018, 07:42:26 AM
Currently there are not much info available for "report to moderator" feature. The message you see on the report page is all we have.


Title: Re: how can I know about the bad reporting post....
Post by: TheBeardedBaby on May 30, 2018, 07:57:25 AM
Check this thread I started, tons of info there, it might be helpful :)
https://bitcointalk.org/index.php?topic=3922020.0

Try this link and let me what you see > "report history (https://bitcointalk.org/index.php?action=reportlist;mine)"


Title: Re: how can I know about the bad reporting post....
Post by: RAMSHIVDEEPAK on May 30, 2018, 08:59:05 AM
Check this thread I started, tons of info there, it might be helpful :)
https://bitcointalk.org/index.php?topic=3922020.0

Try this link and let me what you see > "report history (https://bitcointalk.org/index.php?action=reportlist;mine)"


I got same this same as above Bitcoin Forum > Your reports

You have reported 33 posts with 91% accuracy (29 good, 3 bad, 1 unhandled). When a post is deleted, reports for it will sometimes stay in unhandled status for some time before moving to handled status. Do not worry about your accuracy too much; one accurate report is worth many inaccurate reports.

Reports start out unhandled, and are then either marked good, marked bad, or no moderator ever handles them and they stay unhandled. When a report stays unhandled, this does not mean that no moderators were available to look at it; rather, it means that several moderators looked at it, but none of them was sure whether it should be acted upon or not. A report that stays unhandled can be thought of as "soft-bad", since no moderator positively thought that it warranted action.


Title: Re: how can I know about the bad reporting post....
Post by: jseverson on May 30, 2018, 09:17:59 AM
You can't see which ones were correct and incorrect as far as I know. If you really want that information, you could track down every single post you report (by copying the link address above the post timestamp) and see which ones are still undeleted. It's pretty roundabout, and it's obviously not viable for a big volume, but at the same time there's no real reason to track them anyway. The page itself says not to worry about accuracy.

That's pretty good reporting either way though, so you should simply keep it up.


Title: Re: how can I know about the bad reporting post....
Post by: BQ on May 30, 2018, 10:53:09 AM
I was wondering why my accuracy is 100%, once after reporting a post I instantly checked the "Report to Moderator" page again, and it had only increased by 1.
"You have reported 26 posts with 100% accuracy. Do not worry about your accuracy too much; one accurate report is worth many inaccurate reports."
Why didn't it show up as 'unhandled' for me :o? I assume no moderator checked it in 5 seconds!

Try this link and let me what you see > "report history (https://bitcointalk.org/index.php?action=reportlist;mine)"
that link doesn't work for me:
An Error Has Occurred!
You cannot use this page
 :(


Title: Re: how can I know about the bad reporting post....
Post by: TheBeardedBaby on May 30, 2018, 11:23:05 AM
Try this link and let me what you see > "report history (https://bitcointalk.org/index.php?action=reportlist;mine)"
that link doesn't work for me:
An Error Has Occurred!
You cannot use this page
 :(

Not everyone has access to this kind of info, AFAIK. As we discuss the matter earlier, it should be based on your report count and if you pass a certain limit, then the link will work for you. I have over a thousand successful reports and it's working for me, so I can't tell what is the limit.


Title: Re: how can I know about the bad reporting post....
Post by: Thirdspace on May 30, 2018, 01:18:02 PM
So,if I can know the details the bad reporting,then I can improve my self in future. In my opinion,I have reported only the bad/spam post.Further, I have reported 33 post,So I am not able to find, which 3 posts are not spam post and wrongly reported.

If there is any procedure ,then let me know.

the way I do it is by keeping my own record of report list in a simple text file
everytime I file a report, I write down the report #, userid and its url post (has threadid)
so whenever I report another post, the unhandled number increases temporarily
and good/bad report number will only increase after my report is handled by mods

so to figure out which is good or bad, I can cross check my record against deletion log (https://bitcointalk.org/modlog.php)
search by userid and match the threadid, if found then it's good report, if not then it's bad or unhandled
sometimes it will be straight Autoban or Nuke instead of single post/thread deletion
do this within a day or two because I think modlog doesn't keep history for too long


Title: Re: how can I know about the bad reporting post....
Post by: RAMSHIVDEEPAK on May 31, 2018, 10:05:30 AM
Try this link and let me what you see > "report history (https://bitcointalk.org/index.php?action=reportlist;mine)"
that link doesn't work for me:
An Error Has Occurred!
You cannot use this page
 :(

Not everyone has access to this kind of info, AFAIK. As we discuss the matter earlier, it should be based on your report count and if you pass a certain limit, then the link will work for you. I have over a thousand successful reports and it's working for me, so I can't tell what is the limit.


I have reported only 33 post,But it is working for me.So it may be problem at that point of time.You can try further.


Title: Re: how can I know about the bad reporting post....
Post by: RAMSHIVDEEPAK on May 31, 2018, 10:14:40 AM
So,if I can know the details the bad reporting,then I can improve my self in future. In my opinion,I have reported only the bad/spam post.Further, I have reported 33 post,So I am not able to find, which 3 posts are not spam post and wrongly reported.

If there is any procedure ,then let me know.

the way I do it is by keeping my own record of report list in a simple text file
everytime I file a report, I write down the report #, userid and its url post (has threadid)
so whenever I report another post, the unhandled number increases temporarily
and good/bad report number will only increase after my report is handled by mods

so to figure out which is good or bad, I can cross check my record against deletion log (https://bitcointalk.org/modlog.php)
search by userid and match the threadid, if found then it's good report, if not then it's bad or unhandled
sometimes it will be straight Autoban or Nuke instead of single post/thread deletion
do this within a day or two because I think modlog doesn't keep history for too long


I have searched in this thread with my user id,But i have found nothing or not single report.Compilation of reported thread/posts is not accordance with date,so you have any idea,how old they are ???


Title: Re: how can I know about the bad reporting post....
Post by: Thirdspace on May 31, 2018, 09:56:50 PM
everytime I file a report, I write down the report #, userid and its url post (has threadid)

I have searched in this thread with my user id,But i have found nothing or not single report.Compilation of reported thread/posts is not accordance with date,so you have any idea,how old they are ???

you do search on userid of the reported post not your userid :D
within a day or two, check modlog and search userid (of the post) that you have reported
the modlog seems to keep short history of only 3-5 days if not less