Last modified: 2013-01-08 14:43:56 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 T35585, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 33585 - Allow stewards to block an IP locally on Meta-Wiki as part of the global block form
Allow stewards to block an IP locally on Meta-Wiki as part of the global bloc...
Status: RESOLVED DUPLICATE of bug 17824
Product: MediaWiki extensions
Classification: Unclassified
GlobalBlocking (Other open bugs)
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: SWMT
  Show dependency treegraph
Reported: 2012-01-07 22:25 UTC by Peter Symonds
Modified: 2013-01-08 14:43 UTC (History)
5 users (show)

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


Description Peter Symonds 2012-01-07 22:25:29 UTC
At the moment, a global block is, by default, not active on Meta-Wiki because the user may need to appeal. However, this is being exploited by some cross-wiki vandals, who are moving their abuse to Meta.

For known cases, it would be helpful for stewards to enable the global block on Meta from the form itself, in the form of a tickbox.

This box would, by default, remain unchecked. But in the case of abuse, we could use this box to enable the global block on Meta-Wiki.
Comment 1 billinghurst 2012-12-03 00:04:48 UTC
Oh, with the current proliferation of spambots, this would be so so so so useful, especially where the spambots are on meta.

I would think that if there was an additional checkbox, and its behaviour was to just block anonymous only that would be a significant improvement, and make significantly help the efficiency of stewards.
Comment 2 MA 2013-01-08 14:43:56 UTC

*** This bug has been marked as a duplicate of bug 17824 ***

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