Home
•
Search
•
Translate
Editing filter 846 (see also a
graph
of recent actions)
Filter parameters
Filter ID:
846
Description:
(publicly viewable)
Filter hits:
82,099 hits
Statistics:
Of the last 37,013 actions, this filter has matched 3 (0.01%). On average, its run time is 0.3 ms, and it consumes 1.5 conditions of the condition limit.
Conditions:
(
documentation
)
ip_in_ranges(user_name, "2607:fb90:0:0:0:0:0:0/32", "172.58.0.0/16")
ip_in_ranges(user_name, "2607:fb90:0:0:0:0:0:0/32", "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 +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 Remove two blocked ranges ~ Rob 4/5 Noted that 89.198.161.213 performed edits that are the same as an IP that hit this filter. Beetstra, March 23, 2020 Use ip_in_ranges() --Suffusion of Yellow 19:40 31 May 2022
Flags:
Hide details of this filter from public view
Enable this filter
Mark as deleted
Filter last modified:
19:40, 31 May 2022
by
Suffusion of Yellow
(
talk
|
contribs
)
History:
View this filter's history
Tools:
Export this filter to another wiki
{"data":{"rules":"ip_in_ranges(user_name, \"2607:fb90:0:0:0:0:0:0/32\", \"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\r\n+hop --Coffee 04/04/2017\r\n\r\nAt 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\r\n\r\nRemove two blocked ranges ~ Rob 4/5\r\n\r\nNoted that 89.198.161.213 performed edits that are the same as an IP that hit this filter. Beetstra, March 23, 2020\r\n\r\nUse ip_in_ranges() --Suffusion of Yellow 19:40 31 May 2022","group":"default","actions":{"tag":["Possible disruption"]},"enabled":true,"deleted":false,"hidden":false,"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:
abusefilter-warning
Other message
Page name of other message:
(without "MediaWiki:" prefix)
Show/Hide preview of selected message
Prevent the user from performing the action in question
System message to use for disallowing:
abusefilter-disallowed
Other message
Page name of other message:
(without "MediaWiki:" prefix)
Show/Hide preview of selected message
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
Editing filter 846 (see also a
graph
of recent actions)
Filter parameters
Filter ID:
846
Description:
(publicly viewable)
Filter hits:
82,099 hits
Statistics:
Of the last 37,013 actions, this filter has matched 3 (0.01%). On average, its run time is 0.3 ms, and it consumes 1.5 conditions of the condition limit.
Conditions:
(
documentation
)
ip_in_ranges(user_name, "2607:fb90:0:0:0:0:0:0/32", "172.58.0.0/16")
ip_in_ranges(user_name, "2607:fb90:0:0:0:0:0:0/32", "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 +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 Remove two blocked ranges ~ Rob 4/5 Noted that 89.198.161.213 performed edits that are the same as an IP that hit this filter. Beetstra, March 23, 2020 Use ip_in_ranges() --Suffusion of Yellow 19:40 31 May 2022
Flags:
Hide details of this filter from public view
Enable this filter
Mark as deleted
Filter last modified:
19:40, 31 May 2022
by
Suffusion of Yellow
(
talk
|
contribs
)
History:
View this filter's history
Tools:
Export this filter to another wiki
{"data":{"rules":"ip_in_ranges(user_name, \"2607:fb90:0:0:0:0:0:0/32\", \"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\r\n+hop --Coffee 04/04/2017\r\n\r\nAt 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\r\n\r\nRemove two blocked ranges ~ Rob 4/5\r\n\r\nNoted that 89.198.161.213 performed edits that are the same as an IP that hit this filter. Beetstra, March 23, 2020\r\n\r\nUse ip_in_ranges() --Suffusion of Yellow 19:40 31 May 2022","group":"default","actions":{"tag":["Possible disruption"]},"enabled":true,"deleted":false,"hidden":false,"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:
abusefilter-warning
Other message
Page name of other message:
(without "MediaWiki:" prefix)
Show/Hide preview of selected message
Prevent the user from performing the action in question
System message to use for disallowing:
abusefilter-disallowed
Other message
Page name of other message:
(without "MediaWiki:" prefix)
Show/Hide preview of selected message
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
Videos
Youtube
|
Vimeo
|
Bing
Websites
Google
|
Yahoo
|
Bing
Encyclopedia
Google
|
Yahoo
|
Bing
Facebook
Top Of Page
Home
•
Search
•
Translate
©
CSE