Last modified: 2007-05-18 20:53:28 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 4618 - Blocks and block-related issues (tracking)
Blocks and block-related issues (tracking)
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on: 3345 550 1294 1496 2044 2492 2505 3165 3206 3706 4179 4391 4749 5445 5571 7883
Blocks: tracking
  Show dependency treegraph
Reported: 2006-01-15 05:50 UTC by Rob Church
Modified: 2007-05-18 20:53 UTC (History)
1 user (show)

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


Description Rob Church 2006-01-15 05:50:53 UTC
Tracking bug for issues relating to the blocking mechanism and related interfaces.
Comment 1 Luna Santin 2006-11-12 11:02:54 UTC
Since I respond to a large number of requests for unblocking at en.wp, I'm quite
familiar with this problem: one vandal gets blocked on AOL, and three or four
legitimate editors are hit with the ensuing autoblocks. Perhaps it would be wise
to have the autoblocker ignore some or all of the main AOL IP ranges, such as,, and Would save a lot of
collateral damage.
Comment 2 Rob Church 2006-11-12 15:44:16 UTC
This is a *tracking bug* for all the issues; individual issues have their own
bugs. The intention of this is to be generic.
Comment 3 Rob Church 2007-05-18 20:53:28 UTC
We now have a specific component for these issues, so I'm closing this bug in favour of that.

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