Quite often when doing events, we often have to do multiple different IP ranges. It'd be useful if you didn't have to do multiple different overrides for one event
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T202759 Ease the bottleneck in wiki account creation at in-person events | |||
| Open | None | T27000 Deploy ThrottleOverride extension to Wikimedia wikis | |||
| Open | None | T174816 Allow more than 1 IP range in a throttle |
Event Timeline
Comment Actions
Having the backend store multiple entries into the database and thus applying multiple throttles at once isn't hard. A textbox with "one range per line" for the target field would do for just that, inserting one db entry for each target.
But those entries (after saving) cannot be related to each other in the current schema. Would we want to track exemptions that were created together (e.g. to change them all at once, delete them together etc.)? That needs changes to the current db schema as well as thoughts about the UI of ThrottleOverrideList.