| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T170574 Actions other than `edit` cannot be retrospectively tested in AbuseFilter | |||
| Open | None | T170577 Action `block` cannot be tested in AbuseFilter | |||
| Open | None | T170578 A trigger for action `block` should be implemented in AbuseFilter |
Event Timeline
Comment Actions
Random idea for an assignee: AbuseFilter can execute block as well, don't let it check itself.
Comment Actions
I guess the most natural way to filter blocks would be to use the BlockIp hook. My only doubt is, for what page should we compute variables? Special:Block, I guess? It shouldn't be too hard to implement it, but I agree with low priority (or even lowest), given that filtering block is IMHO highly unusual.