Operator: Nakon
Automatic or Manually Assisted: Supervised automatic.
Programming Language(s): PHP
Function Summary: The bot will hardblock IP address of Tor exit nodes, per m:No open proxies, for a pre-determined amount of time (currently six months).
Edit period(s) (e.g. Continuous, daily, one time run): Daily
Already has a bot flag (Y/N): N
Function Details: The bot is designed to block a list of IP addresses that are determined to be Tor exit nodes. The addresses are exit nodes, retrieved from the TorStatus page, which is linked from torproject.org's documentation page. The bot will check each of the addresses listed in the CSV file against the Tor node checker on the toolserver [1]. If an IP address is listed in the block file and is reported as an exit node by the toolserver, it is hardblocked with account creation disabled. A log of all blocks is recorded after each batch for later analysis. The bot does not block registered user accounts nor perform any other administrative functions. Blocks placed by the bot will not be indefinite, as proxies close over time. I am also an administrator on this project and on Meta. Nakon 04:34, 4 May 2008 (UTC) reply
Redundant to a software feature. — Werdna talk 05:04, 4 May 2008 (UTC) reply
I added it years ago, but nobody's ever bothered to enable it for blocking tor. MediaWiki has inbuilt support for blocking users listed in DNS blacklist. Numerous providers offer DNS blacklists including Tor exit nodes. — Werdna talk 05:09, 4 May 2008 (UTC) reply
Correct me if I'm wrong, but wasn't User:TawkerbotTorA supposed to do the same thing (but the RfA failed)? — paranomia (formerly tim.bounceback) a door? 14:44, 4 May 2008 (UTC) reply
Of your 17 trial blocks, [2] [3] [4] [5] [6] are already stale. Many Tor nodes use dynamic IPs. How do you intend to avoid this? -- uǝʌǝs ʎʇɹoɟ ʇs(st47) 14:47, 4 May 2008 (UTC) reply
There does seem to be a community consensus against adminbots. Can you explain what special measures you will take to run an adminbot? AKAF ( talk) 09:01, 5 May 2008 (UTC) reply
This kind of admin bot, in particular, isn't going to get consensus support from the community. It would only get my support if there is a way for TOR node operators to get an exemption by showing that they have restricted editing access to Wikipedia through their node. TOR is not inherently evil, it's just that the way it interacts with editing Wikipedia is problematic. rspeer / ɹəədsɹ 06:46, 6 May 2008 (UTC) reply
I maintain that this is best implemented in MediaWiki. If the existing measures are inadequate, I will write an extension to specifically target Tor nodes. — Werdna talk 09:50, 6 May 2008 (UTC) reply
Extension is half-written. Currently liasing with tor as to maintaining a comprehensive, accurate list, and tor nodes will be treated as if they were blocked with account creation disabled. Should be live within a few weeks. I don't see any scope for this bot. I will not decline, as I have a conflict of interest. — Werdna talk 13:28, 19 May 2008 (UTC) reply
Operator: Nakon
Automatic or Manually Assisted: Supervised automatic.
Programming Language(s): PHP
Function Summary: The bot will hardblock IP address of Tor exit nodes, per m:No open proxies, for a pre-determined amount of time (currently six months).
Edit period(s) (e.g. Continuous, daily, one time run): Daily
Already has a bot flag (Y/N): N
Function Details: The bot is designed to block a list of IP addresses that are determined to be Tor exit nodes. The addresses are exit nodes, retrieved from the TorStatus page, which is linked from torproject.org's documentation page. The bot will check each of the addresses listed in the CSV file against the Tor node checker on the toolserver [1]. If an IP address is listed in the block file and is reported as an exit node by the toolserver, it is hardblocked with account creation disabled. A log of all blocks is recorded after each batch for later analysis. The bot does not block registered user accounts nor perform any other administrative functions. Blocks placed by the bot will not be indefinite, as proxies close over time. I am also an administrator on this project and on Meta. Nakon 04:34, 4 May 2008 (UTC) reply
Redundant to a software feature. — Werdna talk 05:04, 4 May 2008 (UTC) reply
I added it years ago, but nobody's ever bothered to enable it for blocking tor. MediaWiki has inbuilt support for blocking users listed in DNS blacklist. Numerous providers offer DNS blacklists including Tor exit nodes. — Werdna talk 05:09, 4 May 2008 (UTC) reply
Correct me if I'm wrong, but wasn't User:TawkerbotTorA supposed to do the same thing (but the RfA failed)? — paranomia (formerly tim.bounceback) a door? 14:44, 4 May 2008 (UTC) reply
Of your 17 trial blocks, [2] [3] [4] [5] [6] are already stale. Many Tor nodes use dynamic IPs. How do you intend to avoid this? -- uǝʌǝs ʎʇɹoɟ ʇs(st47) 14:47, 4 May 2008 (UTC) reply
There does seem to be a community consensus against adminbots. Can you explain what special measures you will take to run an adminbot? AKAF ( talk) 09:01, 5 May 2008 (UTC) reply
This kind of admin bot, in particular, isn't going to get consensus support from the community. It would only get my support if there is a way for TOR node operators to get an exemption by showing that they have restricted editing access to Wikipedia through their node. TOR is not inherently evil, it's just that the way it interacts with editing Wikipedia is problematic. rspeer / ɹəədsɹ 06:46, 6 May 2008 (UTC) reply
I maintain that this is best implemented in MediaWiki. If the existing measures are inadequate, I will write an extension to specifically target Tor nodes. — Werdna talk 09:50, 6 May 2008 (UTC) reply
Extension is half-written. Currently liasing with tor as to maintaining a comprehensive, accurate list, and tor nodes will be treated as if they were blocked with account creation disabled. Should be live within a few weeks. I don't see any scope for this bot. I will not decline, as I have a conflict of interest. — Werdna talk 13:28, 19 May 2008 (UTC) reply