Last modified: 2012-05-23 03:24:13 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 7802 - More flexible specification of range blocks (X through Y, as opposed to CIDR format)
More flexible specification of range blocks (X through Y, as opposed to CIDR ...
Status: NEW
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Low enhancement with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-11-03 18:16 UTC by Duncan Harris
Modified: 2012-05-23 03:24 UTC (History)
1 user (show)

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


Attachments

Description Duncan Harris 2006-11-03 18:16:19 UTC
This:-

http://meta.wikimedia.org/wiki/Range_blocks

is incomprehensible.  Admins should just be able to enter a range from $foo to
$bar and just bonk a button to block.
Comment 1 Rob Church 2006-11-03 22:12:54 UTC
Added more relevant summarisation. Supporting explicit ranges (X through Y)
and/or wildcard formats for specification might alleviate the problems we have
with administrators who don't understand the whole CIDR thing blocking entire
German telecommunications providers.
Comment 2 Andrew Garrett 2006-11-06 00:05:45 UTC
I think the best solution to this problem is having a policy requiring local
administrators performing rangeblocks to know how to use CIDR-notation.
Comment 3 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-11-06 00:10:30 UTC
Or in other words, only technowizards get to range-block?  No mileage in it. 
Admins shouldn't have to be expected to know binary.
Comment 4 Andrew Garrett 2006-11-06 00:12:52 UTC
You don't need to be a technowizard to understand range-blocking. You need to
read the provided documentation, and/or do your homework. Range-blocks are
inherently technical - simplifying it to $x->$y won't fix the problem of sysops
that do not understand what ranges to block.
Comment 5 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-11-06 00:16:04 UTC
"People should read the docs" isn't an excuse for poor usability.
Comment 6 Andrew Garrett 2006-11-06 00:20:04 UTC
"People don't read the docs" isn't an excuse for dumbing down an already
adequate interface.
Comment 7 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-11-06 00:23:41 UTC
Actually, it is, if by "dumbing down" you mean "making simpler".  Interfaces
should *always* be as simple as possible without sacrifice of flexibility,
speed, etc.  This is a basic tenet of good software design.
Comment 8 Rob Church 2006-11-06 00:27:08 UTC
Agree with Simetrical; blocking sometimes has to be done fast, and that can't
happen if one has to stop and think, especially if you're not too sure anyway.
Range blocking problems would be cut in two if we made this process simpler.

We can leave support for CIDR notation, of course.
Comment 9 Andrew Garrett 2006-11-06 00:33:49 UTC
I feel that a user who is unable to understand and use CIDR notation is likely
to be also unable to determine appropriate ranges to block.

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


Navigation
Links