|
|
| This temporary filter will log a *lot* of edits, most of which totally innocent and not requiring action. There has been a lot of disruption on a number of namespaces from this range, and an easier way of logging it has been requested by a number of admins and counter-vandalism patrollers. The performance implications of this filter should be minimal --TheresNoTime 22/03/2017 | | This temporary filter will log a *lot* of edits, most of which totally innocent and not requiring action. There has been a lot of disruption on a number of namespaces from this range, and an easier way of logging it has been requested by a number of admins and counter-vandalism patrollers. The performance implications of this filter should be minimal --TheresNoTime 22/03/2017 |
|
| |
|
| This range edits infrequently enough (about 1,000 edits over 4 days) that a tag in the history, to ensure other editors know the prevalence of abuse from this range, seems like a net positive for administration without a major impact to the server load. We'll see how this goes... --Coffee 26/03/2017 | | This range edits infrequently enough (about 1,000 edits over 4 days) that a tag in the history, to ensure other editors know the prevalence of abuse from this range, seems like a net positive for administration without a major impact to the server load. We'll see how this goes... --Coffee 26/03/2017 |
|
| |
|
| +hops --Coffee 02/04/2017 | | +hops --Coffee 02/04/2017 |
| +hop --Coffee 04/04/2017 | | +hop --Coffee 04/04/2017 |
|
| |
|
| At this point you're consuming at least 4 conditions when accounts edit, so adding `user_age == 0` to reduce to 1 condition for those users ~MA 2017-04-04 | | At this point you're consuming at least 4 conditions when accounts edit, so adding `user_age == 0` to reduce to 1 condition for those users ~MA 2017-04-04 |
| | |
| | Remove one blocked range ~ Rob 4/5 |