There must be a clean way to do this. Leaving spam in the histories
does relegate it to the realm of noindex nofollow, but it does mean
that humans going through the histories have to see it. I'd like to
see an option for sysops to expunge a specific revision. Wasn't
there also some discussion of this in the context of collapsing
consecutive minor revisions from the same user? Heck, as a user, I'd
like to collapse my consecutive minor edits!
And could you be more specific about the damage danger?
From what I can tell, MW builds the page history by timestamp, so
dropping a record in the middle shouldn't affect that. There's no
pointer from revision to revision, right?
Recentchanges might link to a nonexistent revision, but wouldn't
rebuildrecentchanges handle that?
Permalinks to the spam revision would break, but that's not exactly a
tragedy.
I'm sure I'm missing something, probably because I'm not thinking in
terms of the distributed architecture used for wikipedia.
Jim
On Oct 4, 2007, at 1:14 AM, Rob Church wrote:
On 04/10/2007, wensong zhang
<wensong.zhang(a)gmail.com> wrote:
All I want is to remove spam revisions in
database permanently. Is
there any
existing tools for this purpose?
Essentially, no, since messing about with previous revisions and text
records is dodgy at best and damaging in the worst case scenario.
You're better off running maintenance/storage/compressOld.php if disk
space is an issue, although if it is *that much* of an issue, then
you're probably better off addressing that limitation first.
Rob Church
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
=====================================
Jim Hu
Associate Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054