Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Contents
Current events
Random article
About Wikipedia
Contact us
Donate
Contribute
Help
Learn to edit
Community portal
Recent changes
Upload file
Languages
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Viewing filter 846: LTA tracking
Help
Home
Recent filter changes
Examine past edits
Edit filter log
English
Tools
Tools
move to sidebar
hide
Actions
General
Upload file
Special pages
Printable version
Get shortened URL
Download QR code
In other projects
Appearance
move to sidebar
hide
Editing filter 846 (see also a
graph
of recent actions)
Filter parameters
Filter ID:
846
Description:
(publicly viewable)
Filter hits:
83,413 hits
Statistics:
Of the last 191,891 actions, this filter has matched 3 (0%). On average, its run time is 0.17 ms, and it consumes 1 condition 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
I understand that details of this filter will be hidden from users who cannot see [https://www.mediawiki.org/wiki/Extension:AbuseFilter/Rules_format#Protected_variables protected variables]
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,"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:
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
Require the user to complete a CAPTCHA in order to proceed with the action. Users with permission to skip a CAPTCHA are exempt.