On Thu, Jan 29, 2009 at 7:34 PM, Jason Schulz <JSchulz_4587(a)msn.com> wrote:
When people know that rev X was removed at time Y,
trolls go to the old xml
dumps, find, and post the content, as I believe has happened in the past.
It's much easier to do that with a public log.
As it was pointed out— the bitfields feature leaves the timestamps in
the history.
Even ignoring that— If anyone wants it I'd be glad to send them a
small easy to use python program that takes two XML dumps and produces
a file including only the revisions existent in the first but missing
in the second.
(The best way to address the underlying concern there is to never dump
a revision less than 1 (2?) week(s) old— that should be easy add in
the new dump system and would at least produce a time window where we
can remove things before they hit the dumps.
But even that is far from foolproof: it's pretty easy to make a
program that simple reads every revision as it comes in... Many people
have done it before. I doubt the extra line of code to save the
revisions will kill anyone.