--- Comment #27 from Risker <risker...@gmail.com> ---
(In reply to comment #26)
> (In reply to comment #25)
> If they are moved to revision deletion alone,
> without suppression, then yes
> there will be hundreds of people who
> suddenly have access. As well, in
> cases it will be necessary to
> track down and suppress log entries. There are
> also problems when the
> suppression was done on pages that were subsequently
> deleted, because it
> will recreate those pages, and we have no idea how
> going to come
> out. In some cases, a lot of juggling went in to ensuring that
> oversightable content existed in the ultimately-deleted page.
> this is done in a methodical way by oversighters, then it makes sense;
> creating a tool that allows oversighters to do this would be more reasonable
> > than an automated, unmonitored process that will suddenly return large
> of information to the publicly accessible revision table; on
> enwiki, we're
> looking at about 10,000 oversighted edits.
You should go
> and read the commit before making such ridiculous (and 100%
> speculations on what the script might do.
Hold on, Alex. What commit are you talking about? I don't see any links to
commits on this bug report. Even if I did, please keep in mind that we have
different skillsets, and I am not a developer and cannot read code or really
understand anything in Gerrit. I'm here as an oversighter, one of the handful
of active oversighters who has worked with both the oversight extension and the
revision-deletion/suppresion extension. So tell me: how *does* the proposed
script deal with oversighted revisions to now-deleted pages? The way the script
is described here, it appears to be intending to reinstate all revisions, which
logically would mean that it would have to recreate the previously-deleted
pages. And how would we track whether or not logs need changing? Remember that
revdeletion/suppresion doesn't automatically result in revdel/suppression of
all log entries.
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
Wikibugs-l mailing list