Last modified: 2006-09-19 01:59:37 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 7366 - We want source and temporal provenance for anti-vandalism purposes
We want source and temporal provenance for anti-vandalism purposes
Status: RESOLVED DUPLICATE of bug 639
Product: MediaWiki extensions
Classification: Unclassified
Extensions requests (Other open bugs)
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-09-18 19:14 UTC by Jason Spiro
Modified: 2006-09-19 01:59 UTC (History)
0 users

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


Description Jason Spiro 2006-09-18 19:14:20 UTC
I and others would love an extension that provided source and temporal
provenance as suggested at .

Here's what I envision: When you click "History" on an article, you see:

- first, the old-fashioned history,
- below that, the provenance view (marked up in 3 colors and with author names
so as to provide both source and temporal provenance),
- and at the bottom, a little disclaimer that the provenance view is for
anti-vandalism purposes only and cannot be used to determine authorship
information for GFDL compliance purposes.

Any objections?
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-09-19 01:59:37 UTC

*** This bug has been marked as a duplicate of 639 ***

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