herbythyme wrote:

I confess I took this a fairly straightforward. The issue has been solved for en wp with admins able to allow BlockExempt. Any chance this could get done for Commons so that we can control some of the hard core vandals better? Cheers

cometstyles wrote:

it has also been implemented successfully on Meta too, no need to delay this request :)

herbythyme wrote:

Yes - given the Commons request was in sometime before the Meta one some action on this would be appreciated/appropriate.

Thanks

herbythyme wrote:

Can I ask nicely why - given the same thing has been done for Meta - this has not been done for Commons yet?

Thanks

bugs wrote:

I'm sure jeluf just overlooked it... *makes some noise so that JeLuF sees it the next time he does shell/root requests*

lar wrote:

Bump. (I know, bumps are bad form but this should be an easy tweak, right?... Commons could REALLY use this. Thanks!)

herbythyme wrote:

I have had an email from an en wp user who has block exempt there who wishes to edit on Commons (they are on Grawp's range).

Can we get something done about this please.

cometstyles wrote:

I asked brion to personally look into this today and he said he might do it soon.. *fingers crossed*

herbythyme wrote:

User:Suntag is unable to create an account on Commons because he edits from Grawp's range. They have blockexempt on en wp

herbythyme wrote:

User:Slakr requires blockexempt on Commons. The range they edit from requires blocking per cross project CU issues. I have block exempted them on Meta.

bastique.bz wrote:

I would like to add that often there are open proxies and TOR nodes that are blocked on Commons that are in use by contributors in blocked areas like China (sometimes) and Iran (sometimes) and elsewhere.

Done.