Req #65203 [Asn]: Please add a feature to report potentially dangerous code examples in comments
| From: | cmb@php.net | Date: | Thu, 06 Aug 2015 20:57:36 +0000 |
| Subject: | Req #65203 [Asn]: Please add a feature to report potentially dangerous code examples in comments | ||
| References: | 1 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-21550@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=65203&edit=1
ID: 65203
Updated by: cmb@php.net
Reported by: ryan at rmauger dot co dot uk
Summary: Please add a feature to report potentially dangerous
code examples in comments
Status: Assigned
Type: Feature/Change Request
Package: Website problem
Operating System: n/a
PHP Version: Irrelevant
Assigned To: googleguy
Block user comment: N
Private report: N
New Comment:
> Given the difference in effort between simply clicking a button
> to push a comment into a moderation queue, and to fill out a
> report here, it is clear which would be a more successful
> mechanism.
I've quickly reviewed all new user contributed comments of the
last weeks, and there are definitely much more jesters active than
people who post really bad or even dangerous comments. I'm afraid
that offering the possibility to push a comment into a moderation
queue with a simple click would be misused too often, what would
take even more time for review.
Previous Comments:
------------------------------------------------------------------------
[2013-10-11 11:45:28] googleguy@php.net
We wanted user contributed notes to be self moderating; as in, the community voting down those notes
which did not appeal to the broader audience would ultimately lead to the note being pushed down to
the bottom of the page where fewer users were likely to spot it immediately. On the flip side,
notes, which the community at large, found to be of higher relevance/quality would get pushed up to
the top where most people would see them. I can't say that this has worked out perfectly thus
far, but it has made a slight impact on weeding out the contributions of lesser quality/relevance.
As always, good judgement and caution should be practiced when using any code found in the user
contributed notes section of php.net as these notes are not generally moderated often enough. There
isn't enough man power to moderate all of them and so we depend on people voting down the bad
ones or reporting them here on bugs.php.net
I'm not sure what impact the report as spam functionality will have on removing those notes.
Once again, the problem is limited man power paying attention to user contributed notes.
Ideally I would rather have everything become a lot more autonomous so that too many reports of spam
or too many negative votes would ultimately remove the note and as such less moderation would be
required.
The user contributed notes on php.net should be moderated directly by its community, in my own
humble opinion. However, this is a lot easier said than done due to the inability to limit the abuse
of such a system. These issues have been raised in the past and not everyone agrees on how this
should be implemented.
------------------------------------------------------------------------
[2013-10-11 00:57:24] bjori@php.net
Sherif, you want to have a look at "Report as spam"/"Report as unsafe" for user
contributed comments?
Unsure if it is needed though, comments with negative votes should be removed...
------------------------------------------------------------------------
[2013-07-09 18:30:37] ryan at rmauger dot co dot uk
Please mention that I am willing to collaborate if extra man-power is needed to
help make it possible
------------------------------------------------------------------------
[2013-07-09 18:27:24] danbrown@php.net
No apologies necessary. I'm checking with one of the guys who has done
substantial work on improving the notes system to see if he wants to take on the
challenge.
------------------------------------------------------------------------
[2013-07-09 18:22:48] ryan at rmauger dot co dot uk
Apologies Dan, I misunderstood the significance of the status change to 'feedback'
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=65203
--
Edit this bug report at https://bugs.php.net/bug.php?id=65203&edit=1