[HACK] One-click mod report, not for the faint of heart

[o_e_l_e_o]

Have you clicked on "This Tor Browser" on the left hand side on the about:debugging page?

[suchmoon]

Maybe a stupid question but I seems that I can't find the Add Temporary Addon in the about:debugging on Tor.
No need to mention that I was away for a while and Tor updated and now this...

Have you clicked on "This Tor Browser" on the left hand side on the about:debugging page?

Yeah it should be under there.

Bookmark this link:

Code:

about:debugging#/runtime/this-firefox

(you'll need it every time you restart the browser)

[TheBeardedBaby]

Thank you guys, I think i'm blind. I opened that link at least 3 times and somehow I missed that temporary extensions button. Need more coffee

[suchmoon]

Apparently it's been a while:

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

I've made some changes to this extension so it feels like a good time to bump the thread. The main change is a report tracker that shows if you have reported a post and what the status of the report is:



Bad reports are shown in red, unhandled in yellow, good in green - I don't have an example because it's quite rare to have an existing post with a good report - and the one-click buttons will not be shown for such posts (but you can still use the regular "Report to moderator" link).

The way this works is very primitive. You need to open your report history. The extension collects your reports. Then when you open a thread or a user's post history, it will show the status on posts that have been reported. Obviously this has some limitations, for example the status is not real-time. After you report a few posts and want to see the updated status you would need to refresh the report history again, and reload any threads/post histories.

This works reasonably well for my workflow. I typically open the report history first, then open a bunch of tabs with non-overlapping content - e.g. multiple spam megathreads - and all previously reported posts are marked by the extension. New reports will not duplicate because the same post can't be in multiple threads. Then I need to refresh the report history only if I want to start working on a different set of content.

This would not work well if you open a number of overlapping tabs (e.g. threads and user post histories). It might be possible to track reports in real time as you click those reporting buttons but it seemed like too much hassle for me.

Other changes:

• Added link to My Reports in the main menu:
• Added support for Chrome (and possibly Edge).
• Cleaned up and refactored the code. For example the code that creates report buttons moved to create_all_controls function.
• Reduced some of the delays (still fits into the 4 second throttling limit), increased default queue size to 100, and added an exception if the queue is full so you will see the red border on the post immediately if you reach the limit.

The code is now on GitHub, which makes it easier for me to maintain. If you're upgrading from the original version and need to preserve your custom changes, you can create a branch off the first commit (which matches the original version), apply your custom code, and cherry-pick or merge from the main branch. Or if you're averse to git for some reason, you can just pick any bits of code you like any way you like, I won't hold that against you.

The usual caveat still applies: this is barely tested code and probably broken in some mysterious ways. Use at your own risk.

[Pmalek]

I've made some changes to this extension so it feels like a good time to bump the thread. The main change is a report tracker that shows if you have reported a post and what the status of the report is:

It shows only if you have reported the post, is it possible to add an optional feature to show if the post was reported by someone else together with displaying the status of that report? It's not really that important, but I know that some users care about their stats and don't want bad reports. Maybe there could be a counter of some sort, so if the post was reported let's say 5 times by 5 different users, it would be shown. That way, those who are sensitive to seeing bad reports don't have to act on it if they can see that the previous reports have stayed unhandled by the mods.     

[o_e_l_e_o]

After you report a few posts and want to see the updated status you would need to refresh the report history again, and reload any threads/post histories.

I've just thrown together a very basic Tampermonkey script which will refresh your report history automatically every x number of seconds if you have it open in a tab. The tab doesn't need to be in focus. I've set the default refresh time to 20 seconds, but it is easily adjusted if you desire. I'm sure you could incorporate something similar in to the extension itself if you wanted, but this seemed easier.

Just paste the code below in to a new Tampermonkey script.

Code:

// ==UserScript==
// @name        Report List Refresher
// @description Refreshes your report page every x seconds
// @include     https://bitcointalk.org/index.php?action=reportlist;mine
// ==/UserScript==

// Change the number before *1000 to your desired time in seconds. Default 20.

setTimeout(function(){ location.reload(); }, 20*1000);

is it possible to add an optional feature to show if the post was reported by someone else together with displaying the status of that report?

That would only be possible if the mod was given access to the forum moderators' global report queue and history, which is obviously never going to happen.

[NeuroticFish]

Is it difficult to make this part of the BPIP extension, as yet another optional feature?
To say that it would be a great addition it's an understatement.

[suchmoon]

It shows only if you have reported the post, is it possible to add an optional feature to show if the post was reported by someone else together with displaying the status of that report? It's not really that important, but I know that some users care about their stats and don't want bad reports. Maybe there could be a counter of some sort, so if the post was reported let's say 5 times by 5 different users, it would be shown. That way, those who are sensitive to seeing bad reports don't have to act on it if they can see that the previous reports have stayed unhandled by the mods.    

Unfortunately the extension can't see what other users reported.

This basically just prevents me from reporting the same post twice, because sometimes I do a lot of reports and it takes mods some time to get through them, so there is a high chance that I'll come across a previously reported post that's still unhandled. That'd be a waste of time for mods.

Even if I could know that someone else reported it, that wouldn't be very useful without knowing why they reported it, and that may raise privacy issues. At any rate that's not possible.

I've just thrown together a very basic Tampermonkey script which will refresh your report history automatically every x number of seconds if you have it open in a tab. The tab doesn't need to be in focus. I've set the default refresh time to 20 seconds, but it is easily adjusted if you desire. I'm sure you could incorporate something similar in to the extension itself if you wanted, but this seemed easier.

I was thinking about automatic refresh but that solves only part of the real-time tracking issue. I would also have to implement something to update the post status in tabs that are already open, and there is also the delay - I might have 100 posts queued for reporting - so I would need to track the queue as well.

Is it difficult to make this part of the BPIP extension, as yet another optional feature?
To say that it would be a great addition it's an understatement.

I was considering it, but to make it really usable I would have to create a whole UI for configuring those report buttons because users can't modify the code of an extension that's installed permanently.

[NeuroticFish]

I was considering it, but to make it really usable I would have to create a whole UI for configuring those report buttons because users can't modify the code of an extension that's installed permanently.

Not necessarily.
A simpler approach could be to make a poll, see the 5-10 most frequent options and add those.
Maybe, if not difficult, add flag for each of those option whether to be added or not + one flag for real vs demo mode.
But that's all. I was not implying anything fancy (which means unnecessary work), no. Just the useful part.

[_BlackStar]

Suchmoon, thanks a lot for making this extension because honestly this is what I needed all along to report posts faster than usual.

Actually I should take some time to understand how to install it in crhome ^{[after considering the risks],} but I think 10 minutes is enough time to understand it properly. You forgot to say that every user must extract the downloaded zip file before "Load unpacked" so that the extension file is easy to find. But good because now this extension is working for me. Thanks


It seems the forum page to me has really changed now. LOL

[suchmoon]

You forgot to say that every user must extract the downloaded zip file before "Load unpacked" so that the extension file is easy to find.

Thanks, I've clarified the instructions in the OP.

[dkbit98]

I've made some changes to this extension so it feels like a good time to bump the thread. The main change is a report tracker that shows if you have reported a post and what the status of the report is

How complicated is to add this one-click mode report as optional experimental feature in BPIP extension?
I don't want to install anything else in my browser and I am using BPIP all the time, so I guess I want firmware update with new features for ultimate all-in-one extesnion

PS
I would add consecutive post report as one more default option in extension.

[suchmoon]

I would add consecutive post report as one more default option in extension.

"multi post" button does that.

As far as modifying BPIP extension, even if I stick with predefined buttons and no configuration, there are still some issues to consider. Some people will not want to install the whole BPIP extension if they want only post reporting so I would need to make it so I can still update this standalone version if needed. I'll see what I can do but it's probably not going to be quick.

[dkbit98]

"multi post" button does that.

Yeah I guess this would be the same and it's shorter then alternative I was using.

As far as modifying BPIP extension, even if I stick with predefined buttons and no configuration, there are still some issues to consider. Some people will not want to install the whole BPIP extension if they want only post reporting so I would need to make it so I can still update this standalone version if needed. I'll see what I can do but it's probably not going to be quick.

I am glad you are considering it, and there is really no need to rush anything so make it in your own time.
With all this updates I think that BPIP extension will soon have to be renamed to something more suiting, like BPIP+Plus or BPIP2

[actmyname]

It's not really that important, but I know that some users care about their stats and don't want bad reports. Maybe there could be a counter of some sort, so if the post was reported let's say 5 times by 5 different users, it would be shown. That way, those who are sensitive to seeing bad reports don't have to act on it if they can see that the previous reports have stayed unhandled by the mods.

Redundant reports do not count as bad: they are batched as the same outcome. In reality, redundant reports may serve as a way to reduce the waiting time of severe reports, regarding malware or global-level issues. Unclear whether reports are queued or stacked in the same order for all moderators.

I've set the default refresh time to 20 seconds, but it is easily adjusted if you desire. I'm sure you could incorporate something similar in to the extension itself if you wanted, but this seemed easier.

Suggested timing/modifications for active users: adjust refresh time to 750-2000ms after submitting report to optimize forum delays to "real-time updates" without any excess refreshes. Lowest time between posts/reports is 4 seconds; experimentally a half dozen new pages per second.