On 7/11/06, Brion Vibber brion@pobox.com wrote:
Er, yes -- that's the whole issue. Blocks of ranges such as big ISPs frequently caught regulars who are stuck with that ISP.
But that's not helped by the new code anyway, except that you can allow registered users from that ISP to edit (which is independent of blocking precedence). Tim mentioned autoblocks, which apparently always affect even logged-in users, as his reason for adding the precedence.
Perhaps a more intuitive solution would be to enable the anon only and no account creation options for username blocks, and just apply them to autoblocks? It's slightly less powerful, in that if someone from a shared IP made a bunch of sleeper accounts before getting blocked they could use those unless you blocked other users of the IP, but in such a (probably uncommon) case blocking the clones wouldn't be hard and would probably be desirable. Plus, not autoblocking preregistered users by default has the advantage of avoiding the autoblock in the first place, rather than allowing it to be lifted more easily.