Closed Bug 434048 Opened 14 years ago Closed 14 years ago
Implement way to moderate problematic reviews
When we auto-approve reviews (bug 428535), we will need a way for problematic reviews to be marked as such and put into the review queue for editor moderation. My thoughts: - we should add a link along the lines of "report this review" (possibly allowing to mark it "inaccurate" vs. "inappropriate" or so?) - should we have a voting threshold? that could for example be "3 users, and/or the author himself" lead to the review being moderated. - does anyone need to be notified about anything by email here? The commenter, if their review is being removed (note: I see problems sending an email out in the commenter's language rather than the editor's, because of gettext)? The author? Comments are much appreciated. CCing madhava, because he may have a suggestion on expected behavior for this feature.
(In reply to comment #0) > My thoughts: > - we should add a link along the lines of "report this review" (possibly > allowing to mark it "inaccurate" vs. "inappropriate" or so?) Yeah, maybe even with a little (optional) comment box for the reason why. > - should we have a voting threshold? that could for example be "3 users, and/or > the author himself" lead to the review being moderated. I'm not sure we'll get much abuse of the system here, as long as its restricted to logged in users. We probably do need to track abusive/stupid commenters though now and have the ability to either disable their accounts or force-moderate their comments specifically. > - does anyone need to be notified about anything by email here? The commenter, > if their review is being removed (note: I see problems sending an email out in > the commenter's language rather than the editor's, because of gettext)? The > author? My first thought was 'everyone should be emailed' but at the moment we don't email anyone if a review is removed and it works okay-ish. If we email the commenter then we're either going to have to write an explanation for each removal to send to them and/or prepare for users emailing the list asking why their comment was removed. Probably best not to, or give us the option of not sending the email (a silent delete, like now).
I agree with comment #1 - there should be a comment box for giving the reason the review is being flagged, and the commenters should not be emailed about rejected reviews or it should be optional.
(from bug 428535 comment #12) > Michel Gutierrez 2008-05-21 09:20:06 PDT > As an extension developer, i find very dangerous to have auto-approved reviews. > Back to the previous amo versions, when reviews were not moderated, you often > got stupid and unfair comments, like "this extension is crap, check mine at > xxx". Things improved a lot on amo 3 since all those mis-leading comments are > filtered. > > I agree that the review can be flagged, but it will take several days before > the comment is removed. By that time, it will have been seen by hundred > thousands people, affecting the number of installs if the review says "it's a > spyware". > > However, i understand the interest of removing workload from the reviewers. > > Could we do something like this: > > • someone writes a review, it is immediately displayed > • the addon author flags the review, it is immediately removed from public > view > • a reviewer may then decide to re-enable the review (if it's a really > spyware, the world must know) >
For 3.4.3, we'll just add the "report a review" and we'll discuss and design for upcoming releases.
This patch allows logged-in users to flag reviews for editor approval. It works ajaxy but also when JS is disabled. What's still missing (but has to go in at the same time, I'll make another patch): Reviews need to show up publicly despite their being marked for editor review. Otherwise clicking the new link will make the comment vanish until an editor touches it.
Attachment #322154 - Flags: review?(fligtar)
Attachment #322154 - Flags: review?(fligtar) → review+
Up to you.
Sorry you need to re-review my patch, as I needed to replace the action by a POST request. While at it, I used cpollett's ___() fallback function too.
Comment on attachment 322401 [details] [diff] [review] Review flagging, rev. 2 When JS is disabled and I flag a review, the review is flagged and disappears from the list. When I have JS enabled and it flags the review via AJAX, when I refresh the page the review is still there. I don't think the AJAX is flagging correctly.
Attachment #322401 - Flags: review?(fligtar) → review-
Actually, flagging a review without removing it from the page immediately until an editor chooses to delete it is expected behavior. The new patch does this consistently. Revision 2 may have done that in some places but not others, sorry about that. I re-checked the (new) patch and the ajax as well as non-ajax actions both result in the review not vanishing from the reviews page on reload, however, they show up as the new last items in the editor review queue. Can you check for one review if this works the same for you? Do you get a positive feedback message displayed in both cases?
I think that's a patch for a different bug.
ouch, of course you are right, thanks. This one should be the right one now though.
Comment on attachment 322740 [details] [diff] [review] argh, now this is the right patch. Looks good. Thanks.
Attachment #322740 - Flags: review?(fligtar) → review+
Cool. It's in r14104.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Has this been released? I can't tell if 3.4.3 has been released or not since the version number isn't listed anywhere on the web site I can find, but since the status is verified fixed I'd assume it is. I don't see a way to flag for review on my addon page at https://addons.mozilla.org/en-US/firefox/addon/1264 I'd like to flag the following review for obvious reasons (what's sad is that it works fine in 3.0): Not compatible for 3.0, this guy is an Idiot When is this F***ing idiot going to make it compatible for 3.0?
Michael, actually we had intended to push AMO 3.4.3 last week but has to postpone it to this week due to a last minute issue (http://blog.mozilla.com/webdev/2008/06/06/amo-343-delayed-until-june-12th/). In the meantime, I've deleted this bad review. We don't accept name calling and foul language in reviews. It will take a few hours for the cache to expire and have it be gone.
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.