[Foundation-l] Global blocking needs to be halted for now

[Alex]

Birgitte SB wrote:
> 
> --- On Sun, 9/14/08, Alex <mrzmanwiki at gmail.com> wrote:
> 
>> From: Alex <mrzmanwiki at gmail.com>
>> Subject: Re: [Foundation-l] Global blocking needs to be halted for now
>> To: "Wikimedia Foundation Mailing List" <foundation-l at lists.wikimedia.org>
>> Date: Sunday, September 14, 2008, 11:32 AM
>> David Gerard wrote:
>>> 2008/9/14 Birgitte SB <birgitte_sb at yahoo.com>:
>>>
>>>> BTW I love how looking at the global block list
>> all the reasons are in english shorthand with no links. 
>> Wasn't it said during the discussion of enabling this
>> feature that the block reason would have links to a help
>> page in multiple languages for all the non-english speakers
>> that are being blocked.
>>>
>>> {{sofixit}}
>>>
>>> The answer to the original question is, of course,
>> ipblockexempt on a
>>> per-user basis - this is precisely what ipblockexempt
>> is for. This is
>>> achieved by filing a bug on bugzilla.mediawiki.org
>> with a link to
>>> community discussion supporting it, and pinging the
>> devs as needed.
>>> i.e., it's another {{sofixit}}
>>>
>>>
>>> - d.
> 
> I could fix the issue for en.WS, but that is a bit shortsighted don't you think?  This is an issue affecting all wikis not just en.WS.  And I doubt many people blocked elsewhere can give admins information on how the issue was fixed for them on en.WP like this guy did for me.  Why was this feature rolled out without sending information on how to handle such problems to the village pumps?
> 
> And how can I fix what other people choose to put in their block logs?? There should be a link to a help page that is helpful to non-English people in the blocking reason.  The blocking reason and blocking admin name are the only unique information on the "You do not have permission page".
> 
>  
>> Isn't this what [[Special:GlobalBlockWhitelist]] is
>> for? If a global
>> block is causing problems on one project, it can be locally
>> disabled and
>> more targeted blocks, or softblocks, put in place if
>> necessary.
>>
> 
> DerHexter forwarded this problem to the stewards mailing list.  They did nothing to help this guy so he asked me to unblock him locally.  I unblocked the IP locally as that was all I could do.  If there is a global solution people are denying it in practice for some reason that I don't know.
> 
> Birgitte SB
> 
> 

Its a local problem, so global solutions are limited. Better explanation
of what to do, localized into every language would help, but its not a
solution. A global ipblockexempt group could be created, or
ipblockexempt could be made a usergroup on every project, assignable by
admins, or by stewards until a local policy is made.


-- 
Alex (w:en:User:Mr.Z-man)