Last modified: 2011-05-15 00:35:11 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 T7608, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 5608 - 'Longevity Points' + User Level to reduce bad edits
'Longevity Points' + User Level to reduce bad edits
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-16 21:55 UTC by Brett Trottert
Modified: 2011-05-15 00:35 UTC (History)
1 user (show)

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


Attachments

Description Brett Trottert 2006-04-16 21:55:45 UTC
What if over successive unreverted edits of a page, sections of text that don't change start 
building 'longevity points' and users who post unreverted changes build up a similar sort of 
counter or user level. While edits to pages would still remain controlled by the existing rules, 
warnings could be sent when a low level user makes changes to long standing text. 

It would also be interesting to have two colorized versions of a page available- one which shows by 
color the amount of time text has stood unchanged (red is new, green or black is old), and another 
which shows the 'longevity rating' of the text (red is low, green or black is high).

That system or something similar could help weed out bad edits without restricting user mobility.
Comment 1 Platonides 2011-05-15 00:35:11 UTC
Extension:WikiTrust http://www.mediawiki.org/wiki/Extension:WikiTrust by Luca de Alfaro, Bo Adler and Ian Pye, from UC Santa Cruz, Computer Science Department can provide that now.

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


Navigation
Links