ideas:usercomments

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
ideas:usercomments [2011/05/02 17:56] – [Progress] added link to "user notes: moderation" thread philipideas:usercomments [2012/07/26 11:11] – [Progress] tularis
Line 16: Line 16:
   * [[http://www.reddit.com/r/PHP/comments/h1lm1/phpnet_really_needs_to_clean_up_their_user/|concerns via reddit]] (May 01, 2011)   * [[http://www.reddit.com/r/PHP/comments/h1lm1/phpnet_really_needs_to_clean_up_their_user/|concerns via reddit]] (May 01, 2011)
   * [[http://php.markmail.org/thread/7gfkqozusrugv3al|user notes: moderation]] (May 02, 2011)   * [[http://php.markmail.org/thread/7gfkqozusrugv3al|user notes: moderation]] (May 02, 2011)
 +  * [[http://php.markmail.org/thread/dl243ysbtznnfi4u|About note maintenance; when to delete notes]] (Feb 24, 2012)
   * Several others no doubt   * Several others no doubt
  
Line 64: Line 65:
   * Note archive (note actions are emailed here):   * Note archive (note actions are emailed here):
   * [[http://news.php.net/php.notes]]   * [[http://news.php.net/php.notes]]
 +
 +==== Revamping Tactics ====
 +
 +Currently the user comments system introduces a number of a fundamental problems that inhibit both its use as well as its usefulness. This section aims to address many of those existing problems and the tactical approach to hopefully weeding them out and setting the new system on a more manageable future course.
 +
 +Here is an incomplete list of some of the issues I'll be attempting to tackle first.
 +
 +  - The importance of what data is stored and how that data can later be used needs to be addressed head-on. The current database schema in the master database allows for a number of useful options to further advance this system to the next step (such as **votes**, and **rating**). However, this schema makes these particular pieces of information in the database difficult to work with. For example, it can not be easily implemented in a manner that allows us to store individual votes or ratings on a per user bases in its existing form. This would require a second table for storing individual rows that can be indexed and joined to the //note// table for collecting such information in a more fine-grained manner.
 +  - The ability for the user to flag certain comments is key in the moderation step. There aren't nearly as many moderators with access to the moderation system as there are users. However, any information collected from the user needs to be useful to an autonomous system as well as a human. Cutting back on tedious human moderation is vital in fighting spam and other abusive behavior. This would entail that the user should not be able to simply flag a comment without offering up an actual reason. Flagging a comment without intent presents the obvious problem of a human still having to decide why this comment should be moderated or removed. If we can alleviate the human factor and narrow down information that allows the human to make a quick and intelligent decision based on the available information we can expedite the moderation process.
 +  - Presenting the information in the user-submitted comments to the user in a more meaningful and useful manner can also play an important role in allow, encouraging, and enabling the power of a community to unanimously decide on what is considered more or less valuable. Currently the system only presents the comments in a descending order by date. This allows the more current comments to remain at the top. While this is a good idea, it's also not the best idea. Some improvements may including using multiple criteria for ordering and presenting comments to the user, such as rating, votes, and dates with optional sorting fields (//descending/////ascending//).
ideas/usercomments.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1