Allow global whitelisting of IPs subject to global rangeblocks
Problem: Several requests for unblock cannot be handled in due time because of providers/tech depths of different organization mixing up networks which could legitimately edit the wikis with farms with open proxies, spam sources, etc. A quite common case are, also, private proxies on VPS or reverse proxies from different organizations hosted in third-party farms.
Proposed solution: create a Special:GlobalBlockWhitelist page where a global block can be revoked for a certain IP or subnet falling in a blocked range
Who would benefit: dozens of users caught by global blocks
The issue? Huge administrative overhead that stewards cannot bear. A quick example: a German free WiFi sharing project is routed through a series of proxies hosted in a bunch of blocked /16, an user asked us to be unblocked, so for each of these blocks I had to replace a single block with 15 blocks. Vituzzu (talk) 16:03, 22 January 2022 (UTC)[reply]
I don't think so in that specific case, but that was just a simple example. I've seen countless private VPS, someone sharing the office with LTAs, etc. Vituzzu (talk) 11:45, 26 January 2022 (UTC)[reply]
This seems like a generally useful and interesting challenge -- overlapping passlists + blocklists -- and a practical set of tasks that needs it. –SJtalk23:09, 23 January 2022 (UTC)[reply]
Support This is sometimes also an issue on wikis (like the Dutch Wikipedia) where smaller ranges are inadvertently caught in larger (local) range blocks (unfortunately, locally in our case). A possible extension (once this could be stable... ) could thus be considered. Daniuu (talk) 11:13, 29 January 2022 (UTC)[reply]