@@ -41,24 +41,12 @@ or with an array of start/end IP addresses:
41
41
These two are equivalent, but the former is a bit faster, and easier to read.
42
42
The latter is convenient if your range is difficult to express using a netmask.
43
43
44
- ### Transparency
45
-
46
- If you end up running an anon bot we would love to document the IP address
47
- ranges you use for transparency purposes. Please add just the ranges
48
- stanza of your onfig file to the ` conf ` directory. Name the file using your
49
- Twitter account, e.g. for congressedits:
50
-
51
- conf/congressedits.json
52
-
53
- You can use a service like [ ARIN Online] ( http://whois.arin.net/ui ) to look up
54
- IP address ranges by organization name.
55
-
56
44
If you would like your configuration file to reference the IP addresses in
57
45
the external file just use the filename. So instead of:
58
46
59
47
``` javascript
60
48
{
61
- " nick" : " congressedits " ,
49
+ " nick" : " anon1234 " ,
62
50
" accounts" : [
63
51
{
64
52
" consumer_key" : " " ,
@@ -67,9 +55,8 @@ the external file just use the filename. So instead of:
67
55
" access_token_secret" : " " ,
68
56
" template" : " {{page}} Wikipedia article edited anonymously from {{name}} {{&url}}" ,
69
57
" ranges" : {
70
- " US House of Representatives" : [
71
- [" 143.231.0.0" , " 143.231.255.255" ],
72
- [" 74.119.128.0" , " 74.119.131.255" ]
58
+ " Home Network" : [
59
+ [" 192.168.1.1" , " 192.168.255.255" ]
73
60
]
74
61
}
75
62
}
@@ -81,15 +68,15 @@ you would have:
81
68
82
69
``` javascript
83
70
{
84
- " nick" : " congressedits " ,
71
+ " nick" : " anon1234 " ,
85
72
" accounts" : [
86
73
{
87
74
" consumer_key" : " " ,
88
75
" consumer_secret" : " " ,
89
76
" access_token" : " " ,
90
77
" access_token_secret" : " " ,
91
78
" template" : " {{page}} Wikipedia article edited anonymously from {{name}} {{&url}}" ,
92
- " ranges" : " conf/congressedits .json"
79
+ " ranges" : " ranges .json"
93
80
}
94
81
]
95
82
}
0 commit comments