Last modified: 2012-10-11 22:38:19 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T42511, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 40511 - Special:FeedbackDashboard 'hide' function should be extended to all autoconfirmed editors
Special:FeedbackDashboard 'hide' function should be extended to all autoconfi...
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
MoodBar (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-25 18:31 UTC by Steven Walling
Modified: 2012-10-11 22:38 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Steven Walling 2012-09-25 18:31:31 UTC
Comments from MoodBar can be hidden/unhidden by sysops currently.

Per community request on English Wikipedia,[1][2] and the nosedive in the number of responses on the Dashboard recently,[3] we need to widen the scope of who can hide feedback from the queue. 

Originally, the 'hide' function was merely to deal with abusive comments. However, the community is having a hard time keeping up with the volume of comments, and would like the option to hide or mark as low quality those comments which do not really merit a detailed response from a human being. 

Extending the hide functionality to all autoconfirmed editors was actually one idea previously suggested (see bug #32799), and there is a more pressing need to do that now. This is a pretty low risk change, because this is not deletion, but simply hides the content of items in the list. 

1. https://en.wikipedia.org/wiki/User_talk:Steven_(WMF)#The_feedback_dashboard
2. Last two threads on https://en.wikipedia.org/wiki/Wikipedia_talk:New_editor_feedback
3. https://toolserver.org/~DarTar/fd/
Comment 2 Steven Walling 2012-09-26 00:24:03 UTC
Wow, that was quick. Thanks Benny! :)

Will close when the change is +1/2-ed and merged. I assume it will ride the train into production next week.
Comment 3 Siebrand Mazeland 2012-09-27 03:52:16 UTC
Merged. Expected to appear in 1.20wmf13.
Comment 4 James Alexander 2012-09-27 20:31:08 UTC
I'm reopening this for now because I'm a bit concerned both about the change and the implementation. 

Sadly I think this is pretty high risk right now. We don't currently have any other way to delete moodbar comments, the hide function is the ONLY way, after that the next escalation is to manually edit the database. This leads us to some major issues and the hidden feedback includes things that would normall be oversighted such as libel or personal information. This is problematic for even sysops to have access to but, I believe, has been a compromise until a full OS option is available. In my opinion it seems absolutely unacceptable to have autoconfirmed users able to view and undelete at the very least without legal approval and a much comprehensive community consensus (with them having a full understanding of what they are giving away).

I'm also hesitant about the implementation. This shouldn't be in moodbar.php, it's a local change that even if implemented should be in commonsettings, not in the defaults. 

Copying in Philippe because I know he's worked with the moodbar team before on some of the privacy and OS issues and will have a better understanding of legals needs.
Comment 5 Steven Walling 2012-09-27 20:39:13 UTC
(In reply to comment #4)
> 
> Sadly I think this is pretty high risk right now. We don't currently have any
> other way to delete moodbar comments, the hide function is the ONLY way, after
> that the next escalation is to manually edit the database.

James,

I'm sorry but you're completely wrong here. 

There has _never_ been deletion of any kind (page deletion, revdeletion, or oversight) in FeedbackDashboard. Hiding is not a substitute for deletion, and should not be treated as such. Unhiding feedback is an option at any time when something is hidden, and there is no log of what has been hidden. There is no policy which outlines that hiding is equivalent to deletion, and if you look at the original bugs I linked to, opening hiding to autoconfirmed editors has long been considered for this very reason. 

> 
> Copying in Philippe because I know he's worked with the moodbar team before on
> some of the privacy and OS issues and will have a better understanding of
> legals needs.

Remember that feedback, unlike wiki pages, does not appear in the wiki anywhere other than the Special page, and is not a part of XML dumps or accessible via the API. 

This is why there was no deletion or oversight built into the tool to begin with. If legal would like to request to features engineering that we need these features in order to stay protected, they should do that. But it is not up to legal or you James to make decisions on features or associated permissions.
Comment 6 Philippe Beaudette 2012-09-27 20:53:21 UTC
Actually, legal has been deeply involved in oversight and content removal here. :)

I've asked Howie to take a look.

Also, I was under the impression that any community member could weigh in on these bugs, Steven.  I see this as James weighing in on a bug.  I'm a little confused as to why you're discouraging that, but maybe we'll discuss that offline.  :-)

Everyone, let's have the proverbial tea, shall we?
Comment 7 Steven Walling 2012-09-27 21:04:41 UTC
(In reply to comment #3)
> Merged. Expected to appear in 1.20wmf13.

In case he's not reading, I'll ask Siebrand to unmerge for now.
Comment 8 Steven Walling 2012-09-27 21:07:54 UTC
https://gerrit.wikimedia.org/r/#/c/25586/

Courtesy Patrick.
Comment 9 Steven Walling 2012-09-27 23:59:13 UTC
(In reply to comment #4)
> 
> Sadly I think this is pretty high risk right now. We don't currently have any
> other way to delete moodbar comments, the hide function is the ONLY way, after
> that the next escalation is to manually edit the database. This leads us to
> some major issues and the hidden feedback includes things that would normall be
> oversighted such as libel or personal information. This is problematic for even
> sysops to have access to but, I believe, has been a compromise until a full OS
> option is available. In my opinion it seems absolutely unacceptable to have
> autoconfirmed users able to view and undelete at the very least without legal
> approval and a much comprehensive community consensus (with them having a full
> understanding of what they are giving away).
> 

The hide/unhide feature was not built with the oversight use case in mind, clearly. It wasn't even built for deletion. I don't like starting from the assumption that we should use it as such, because it means that it gives us an excuse to lag on building in oversight, and in the meantime cripple the community's ability to deal with the other kinds of feedback that really need to be removed.

The number of cases where this scenario would happen are much much smaller than the amount of really poor feedback or regular vandalism which need to be removed from the queue. Rather than playing to the edge case here for the tiny minority of content that merits oversight, I would like us to build in what's necessary to have a real oversight tool, not misuse something that should be more widely available and for a different purpose.
Comment 10 Steven Walling 2012-10-02 21:13:20 UTC
Request for real deletion added in #40729 per discussion with Philippe, Howie, et al.
Comment 11 Steven Walling 2012-10-10 23:08:29 UTC
(In reply to comment #10)
> Request for real deletion added in #40729 per discussion with Philippe, Howie,
> et al.

Okay, since delete has been added PB has given his thumbs up to re-add this user right change.
Comment 13 Steven Walling 2012-10-11 22:38:19 UTC
Deployed.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links