SPECIAL:ABUSEFILTER HISTORY 846 ITEM 17095

You are viewing an old version of this filter. The statistics quoted are for the most recent version of the filter. • Return to this filter's history.

Filter parameters

Filter ID:	846
Description: (publicly viewable)
Statistics:	Of the last 195,815 actions, this filter has matched 9 (0%). On average, its run time is 0.17 ms, and it consumes 1 condition of the condition limit.
Conditions: ( documentation)	ip_in_range(user_name, "2607:fb90:0:0:0:0:0:0/32") \| ip_in_range(user_name, "142.234.0.0/16") \| ip_in_range(user_name, "172.58.0.0/16") ip_in_range(user_name, "2607:fb90:0:0:0:0:0:0/32") \| ip_in_range(user_name, "142.234.0.0/16") \| ip_in_range(user_name, "172.58.0.0/16")
Notes:	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 +hops --Coffee 02/04/2017
Flags:	Hide details of this filter from public view Enable this filter Mark as deleted
Filter last modified:	05:10, 3 April 2017 by Coffee ( talk \| contribs)
History:	View this filter's history
Tools:	Export this filter to another wiki {"data":{"rules":"ip_in_range(user_name, \"2607:fb90:0:0:0:0:0:0/32\") \|\r\nip_in_range(user_name, \"142.234.0.0/16\") \|\r\nip_in_range(user_name, \"172.58.0.0/16\")","name":"LTA tracking","comments":"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\r\n\r\nThis 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\r\n\r\n+hops --Coffee 02/04/2017","group":"default","actions":{"tag":["Possible disruption"]},"enabled":true,"deleted":false,"privacylevel":0,"global":false},"actions":{"tag":["Possible disruption"]}}

Actions to take when matched

Trigger actions only if the user trips a rate limit

Number of actions to allow:

Period of time (in seconds):

Group throttle by:

user

See the documentation on mediawiki.org.

Trigger these actions after giving the user a warning

System message to use for warning:

Page name of other message:

(without "MediaWiki:" prefix)

Prevent the user from performing the action in question

System message to use for disallowing:

Page name of other message:

(without "MediaWiki:" prefix)

Revoke the user's autoconfirmed status

Tag the edit in contributions lists and page histories

Tags to apply:

(see Wikipedia:Tags for use and formatting)

(please don't rename a tag here, see link above)

(one per line, no commas, publicly visible)

Possible disruption

You are viewing an old version of this filter. The statistics quoted are for the most recent version of the filter. • Return to this filter's history.

Retrieved from " /info/en/?search=Special:AbuseFilter/history/846/item/17095"

You are viewing an old version of this filter. The statistics quoted are for the most recent version of the filter. • Return to this filter's history.

Filter parameters

Filter ID:	846
Description: (publicly viewable)
Statistics:	Of the last 195,815 actions, this filter has matched 9 (0%). On average, its run time is 0.17 ms, and it consumes 1 condition of the condition limit.
Conditions: ( documentation)	ip_in_range(user_name, "2607:fb90:0:0:0:0:0:0/32") \| ip_in_range(user_name, "142.234.0.0/16") \| ip_in_range(user_name, "172.58.0.0/16") ip_in_range(user_name, "2607:fb90:0:0:0:0:0:0/32") \| ip_in_range(user_name, "142.234.0.0/16") \| ip_in_range(user_name, "172.58.0.0/16")
Notes:	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 +hops --Coffee 02/04/2017
Flags:	Hide details of this filter from public view Enable this filter Mark as deleted
Filter last modified:	05:10, 3 April 2017 by Coffee ( talk \| contribs)
History:	View this filter's history
Tools:	Export this filter to another wiki {"data":{"rules":"ip_in_range(user_name, \"2607:fb90:0:0:0:0:0:0/32\") \|\r\nip_in_range(user_name, \"142.234.0.0/16\") \|\r\nip_in_range(user_name, \"172.58.0.0/16\")","name":"LTA tracking","comments":"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\r\n\r\nThis 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\r\n\r\n+hops --Coffee 02/04/2017","group":"default","actions":{"tag":["Possible disruption"]},"enabled":true,"deleted":false,"privacylevel":0,"global":false},"actions":{"tag":["Possible disruption"]}}

Actions to take when matched

Trigger actions only if the user trips a rate limit

Number of actions to allow:

Period of time (in seconds):

Group throttle by:

user

See the documentation on mediawiki.org.

Trigger these actions after giving the user a warning

System message to use for warning:

Page name of other message:

(without "MediaWiki:" prefix)

Prevent the user from performing the action in question

System message to use for disallowing:

Page name of other message:

(without "MediaWiki:" prefix)

Revoke the user's autoconfirmed status

Tag the edit in contributions lists and page histories

Tags to apply:

(see Wikipedia:Tags for use and formatting)

(please don't rename a tag here, see link above)

(one per line, no commas, publicly visible)

Possible disruption

You are viewing an old version of this filter. The statistics quoted are for the most recent version of the filter. • Return to this filter's history.

Retrieved from " /info/en/?search=Special:AbuseFilter/history/846/item/17095"

Videos

Websites

Encyclopedia

Facebook