Last modified: 2009-01-31 22:04:18 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T17110, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 15110 - Need some control over User:Redirect fixer 's edit summaries
Need some control over User:Redirect fixer 's edit summaries
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Redirects (Other open bugs)
unspecified
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-10 16:35 UTC by Happy-melon
Modified: 2009-01-31 22:04 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Happy-melon 2008-08-10 16:35:51 UTC
Stuff like http://en.wikipedia.org/w/index.php?title=Special:Contributions&offset=20080810032144&limit=21&target=Redirect+fixer is irritating but harmless, but what if a vandal moved a heavily-redirected page to [[John's phone number is 1234567890]]? That's going to make a mess of the oversight log and be unnecessarily time-consuming for oversighters to eliminate.

The most obvious way I can think of would be to set up a blacklist for the pagetitles; it could be more aggressive than the title blacklist because if a match was found, the edit summary would simply drop the link, becoming "Target has been moved, it now redirects to [[Foo]].", "[[Foo]] has been moved.", or "Target has been moved." depending on which titles matched the blacklist.  

Alternatively and more simply (and the solution I'd advocate :D), would it be possible to put a (configurable) time delay in before the script fixes the redirects? That way it would give editors time to catch and revert the vandalism before the script enshrines the vandal title in the logs.  It could be quite short (maybe 5-10 minutes) on more active wikis, and correspondingly longer on smaller, less-well-monitored ones.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2008-08-10 21:27:03 UTC
There are already move logs with the page name created from the move vandalism itself and its reversion.  I don't see why the redirect fixer's log summaries are any different or need to be treated differently.
Comment 2 Alex Z. 2008-08-10 23:49:35 UTC
Simetrical raises a good point, especially since log entries can't (yet) be oversighted without sysadmin intervention, that's really more of a problem. However, if we were going to change the redirect fixer to try and prevent this, a time limit would probably be much better than adding yet another blacklist, which would have to be maintained concurrently with the title blacklist.
Comment 3 John Broughton 2008-08-11 16:15:59 UTC
If we're worried about move vandalism (and the problems that come from fixing double redirects are perhaps less important than the move itself) then something like allowing only admins to move a page with 500 or more edits might be (a) easier to implement and (b) would pretty much solve the problem of "moving a heavily-redirected page".  
Comment 4 Charlotte Webb 2008-08-12 19:42:40 UTC
> something like allowing only admins to move a page with 500 or more edits might
> be (a) easier to implement and (b) would pretty much solve the problem of
> "moving a heavily-redirected page".  

That wouldn't solve anything as there is no actual correlation between the number of revisions and the number of incoming redirects.
Comment 5 Happy-melon 2009-01-31 22:04:18 UTC
Closing as redirectfixer has been disabled AFAIK

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links