-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Why is Mediawiki programmed like this?
Page A ---OK MOVE---> Page B (history-less redirect to page A) but Page A ---BADMOVE---> Page B (history-less redirect to page C)
If it was:
Page A ---OK MOVE---> Page B (history-less redirect to page A) Page A ---OK MOVE---> Page B (history-less redirect to page C)
Normal users would be able to clean up page-move vandals who:
Page A --MOVE--> Page B Edit Page A
And effectively demand that an admin to the fixing. If the second set of rules was implemented, then a user who wanted to revert this could:
Edited Page A --MOVE--> Page C Page B --MOVE--> Page A Speedy Page C or leave it there if it's in a user namespace.
I'm telling you, one of these days a vandal is going to realize that Page moves require little work to be done but can cause massive damage that requires lots of work to fix, and then create multiple puppet accounts and capitilize on this behavior.
The only possible drawback that I can see with the second set of behaviors is that it means pages are a bit jumpier: you can put them on totally unrelated redirects, and you might lose some redirects in the process. But hey, they're redirects.
- -- Edward Z. Yang Personal: edwardzyang@thewritingpot.com SN:Ambush Commander Website: http://www.thewritingpot.com/ GPGKey:0x869C48DA http://www.thewritingpot.com/gpgpubkey.asc 3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA
Edward Z. Yang wrote:
Why is Mediawiki programmed like this?
Page A ---OK MOVE---> Page B (history-less redirect to page A) but Page A ---BADMOVE---> Page B (history-less redirect to page C)
Could you explain the terms you're using here? * What's an OK MOVE? * What's a BADMOVE? * How does a page C come in on BADMOVEs?
-- brion vibber (brion @ pobox.com)
wikitech-l@lists.wikimedia.org