Page MenuHomePhabricator

Make oversight-RevisionDelete revisions invisible in history, or make oversight log visible in Special:Log
Closed, ResolvedPublic

Description

Oversight means the action of RevisionDelete and making it invisible even to sysops.

Users get confused when they found deleted revisions in history page but no deletion log in log page. Most of them cannot figure out that it's oversight.


Version: 1.17.x
Severity: enhancement

Details

Reference
bz24122

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:03 PM
bzimport set Reference to bz24122.
liangent created this task.Jun 25 2010, 2:21 PM
aaron added a comment.Jun 26 2010, 1:15 AM

"Make oversighted revisions invisible in history": this would create the same diff problems that we want to avoid.
http://en.wikipedia.org/wiki/Wikipedia:OVER#RevisionDelete_vs_Extension:Oversight

"make oversight log visible in Special:Log"
The Oversight ext. had a public log...which was specifically removed due to dump harvesting.

What about using a different mark for oversighted versions in history?

aaron added a comment.Jun 26 2010, 2:36 AM

(In reply to comment #2)

What about using a different mark for oversighted versions in history?

That's what I was thinking.

(In reply to comment #1)

The Oversight ext. had a public log...which was specifically removed due to
dump harvesting.

Users can harvest history pages, cannot they?

Oversight-RevisionDelete entries should not be publicly logged.

(In reply to comment #2)

What about using a different mark for oversighted versions in history?

This is a duplicate of bug 21272.

(In reply to comment #1)

"make oversight log visible in Special:Log"
The Oversight ext. had a public log...which was specifically removed due to
dump harvesting.

And this looks like a WONTFIX.

  • This bug has been marked as a duplicate of bug 21272 ***