Problem:
When a user posts something rude, users can report it, but nothing is done about it, its there until the admin/moderator views the report, sitting there offending viewers.
Fix:
When X number of reports are made against a post (would require adding a config option of a maximum number of reports per post and change it from only allowing 1) it would un-approve the post (for moderation to look at) so that it would not remain there as offending content.
A new config option in the ACP where you can enable/disable this feature and set how many reports are required to un-approve the post.
Each report would need to be by a different user obviously.
Pros:
Removes offending comments
Sort of a level of community moderation via the report button.
All up to the admin if they want to use it, I'm guessing it would be especially popular on new boards or under-staffed boards.
Cons:
Users could get a post unapproved with it being fine - avoid by setting a high(er) limit
(Cyber-)Bullying users - Remove a users permission to report posts.
[RFC] Unapprove on X number of Reports
[RFC] Unapprove on X number of Reports
Formerly known as Unknown Bliss
No unsolicited PMs please except for quotes.psoTFX wrote: I went with Olympus because as I said to the teams ... "It's been one hell of a hill to climb"
- imkingdavid
- Registered User
- Posts: 1050
- Joined: Thu Jul 30, 2009 12:06 pm
Re: [RFC] Unapprove on X number of Reports
I came up with the general idea of this and asked Michael to post an RFC (I don't have time to make something like this atm, and I'm not sure if this would be a generally accepted idea for addition to the core). He made some changes to it from what I was thinking, so let me explain my thoughts a little more and we can discuss who's implementation is better.
Instead of counting reports against it (which would cause a backup in the reports area, which means more work for moderators) we could introduce a post "downvote" option. When a post or topic recieves X downvotes, it is hidden (i.e. disapproved, soft deleted, or however we find to be the best available way to hide it at the time of making this) and a single report is created (only if none already exists) with the reason something like "This post has received X downvotes and needs review."
Potential problem: Groups of users could attack one user's post(s) and hide them.
Potential solution: raise the threshold and/or implement a way for moderators to mark specific posts and/or topics as "approved" (can discuss exact terminology later) and such posts cannot be hidden (or maybe not even downvoted).
Perhaps even a new permission like "Can downvote posts/topics". Also, could have a global kill switch if things get out of hand, although I don't see that happening.
Instead of counting reports against it (which would cause a backup in the reports area, which means more work for moderators) we could introduce a post "downvote" option. When a post or topic recieves X downvotes, it is hidden (i.e. disapproved, soft deleted, or however we find to be the best available way to hide it at the time of making this) and a single report is created (only if none already exists) with the reason something like "This post has received X downvotes and needs review."
Potential problem: Groups of users could attack one user's post(s) and hide them.
Potential solution: raise the threshold and/or implement a way for moderators to mark specific posts and/or topics as "approved" (can discuss exact terminology later) and such posts cannot be hidden (or maybe not even downvoted).
Perhaps even a new permission like "Can downvote posts/topics". Also, could have a global kill switch if things get out of hand, although I don't see that happening.
Re: [RFC] Unapprove on X number of Reports
^ Like the idea, don't know if it's better for a MOD or not, anyway, this is complex enugh to add to the core and not be a MOD anymore.
I think a post should be to be unapproved if there are too many downvotes.
Like the solution also. Anyway, I think a user always should have the right to vote no matter if it's "hiddable" or not.
I think a post should be to be unapproved if there are too many downvotes.
Like the solution also. Anyway, I think a user always should have the right to vote no matter if it's "hiddable" or not.
Agree.imkingdavid wrote: Perhaps even a new permission like "Can downvote posts/topics". Also, could have a global kill switch if things get out of hand, although I don't see that happening.
Re: [RFC] Unapprove on X number of Reports
The thing with downvotes its its too much like a like/dislike system. Or reputation. Hence I suggested reports. And reports for one post would all go on one page, not as separate reports.
Formerly known as Unknown Bliss
No unsolicited PMs please except for quotes.psoTFX wrote: I went with Olympus because as I said to the teams ... "It's been one hell of a hill to climb"
Re: [RFC] Unapprove on X number of Reports
Yeah... Anyway, a report can work as a down vote. I think we should merge posts when they apply to the same post instead of denying to report the post.
- imkingdavid
- Registered User
- Posts: 1050
- Joined: Thu Jul 30, 2009 12:06 pm
Re: [RFC] Unapprove on X number of Reports
Well, if we do decide to use reports instead of some other point-based system, it will require a bit of work to the report system. IMO, the who report/warning/discipline system could use some reworking to allow it to all actually work together in some areas, but that will likely wait for 3.2 or more likely 4.0.
Re: [RFC] Unapprove on X number of Reports
To be honest the report system needs rebuilding anyway.imkingdavid wrote:Well, if we do decide to use reports instead of some other point-based system, it will require a bit of work to the report system. IMO, the who report/warning/discipline system could use some reworking to allow it to all actually work together in some areas, but that will likely wait for 3.2 or more likely 4.0.
It seems like 3.2 is going to be the version of rebuilding some elements - BBcodes, Reports etc.
Formerly known as Unknown Bliss
No unsolicited PMs please except for quotes.psoTFX wrote: I went with Olympus because as I said to the teams ... "It's been one hell of a hill to climb"
Re: [RFC] Unapprove on X number of Reports
There's no need for 4.0. phpbb 3.2 is enugh to do that work.imkingdavid wrote:Well, if we do decide to use reports instead of some other point-based system, it will require a bit of work to the report system. IMO, the who report/warning/discipline system could use some reworking to allow it to all actually work together in some areas, but that will likely wait for 3.2 or more likely 4.0.