Talk:WikiProject on open proxies/Archives/2006

Documentation

• For help on open proxies, see Help:Blocked.

How to update chapter pages

To update the project page of a chapter, perform the following steps:

1. Prepare
   1. Make sure that no IP addresses are listed at the local project. If there are, clear the backlog and move them to the Meta-Project first.
2. Update
   1. Copy everything below "<!-- Copy below this line for interwiki updates -->".
   2. Paste the text over everything below "<!-- Paste below this line in interwiki updates -->".
   3. Remove the "Unblock" section, which should only be on the Meta-Wiki.
   4. Remove the link to the current page from the "Chapters" section.
   5. Remove listed IPs that were copied.
   6. Remove the "Block status" field in the table.

usage?

I see no open proxies... whats up? --Cool Cat^Talk|@ 02:45, 13 March 2006 (UTC)

Sorry for the delay in responding; I'm not very active on the Meta-Wiki yet. The main page is used to coordinate scans of open proxies. There's a comprehensive blacklist of open proxies at Meta:WikiProject on open proxies/Blacklist, linked to from the "Subpages" section on the main page. IPs that are blocked on all projects are occassionally moved to an archive. // Pathoschild 21:43, 24 March 2006 (UTC)

Open proxy lists from en-wp

The following two open proxy lists were removed from the en-Wikipedia chapter in the last update. They should be scanned and integrated into the blacklist at some point.

• Ilmari Karonen
• Kelly Martin

// Pathoschild (^talk/_map) 15:27, 18 April 2006 (UTC)

Open proxies used in HuWiki

Hi, I've just blocked the following addresses as open proxies in HuWiki:

• 218.158.114.22
• 203.236.16.0/24

I didn't find information on whether there is a wikimedia server farm wide blocklist and where is it, and what's in it and where to report new open proxies. Can someone point me to a page with more information on this?

Thanks, Nyenyec 16:09, 26 May 2006 (UTC)

My IP is on the list, but is not an open proxy

My IP – 209.236.231.253 – is on the list, but is definitely not an open proxy. It appears that User:Naconkantari added it [1], though I'm not sure why. 209.236.231.253 03:05, 30 May 2006 (UTC)

I've removed it. I don't remember how it got there, though. It appears that your IP was not blocked on any other projects and is not currently blocked on en.wiki. Naconkantari 03:12, 30 May 2006 (UTC)

I think I remember, lol [2] – but you got the wrong IP. The proxy IP is 207.150.184.42. Sorry for the mixup ;-) 209.236.231.253 03:16, 30 May 2006 (UTC)

I would like to add 80.171.71.231 as an IP, that is not a open proxy, it is an dial-up IP (Or should all dial up IPs be blocked?).

Please delete, no longer relevant.

Thanks!

Brian

TOR exit nodes

I'd offer to help, as a TOR user, except I'm concerned any IPs I gave you people might be hardblocked instead of softblocked. Sooo... I guess there really isn't a point to this message. Armedblowfish (talk) 22:45, 23 October 2006 (UTC)

Okay. —[admin] Pathoschild 23:17, 23 October 2006 (UTC)

No offense. Just sort of thinking on paper... or bits.... Armedblowfish (talk) 23:57, 23 October 2006 (UTC)

None taken. I'm progressively expanding the block template to automatically fill out the form in that manner. When I have time to finish it, it will soft-block Tor exit nodes for one month. I'll compile a new list of Tor exit nodes every month and reblock, which will keep us up to date while automatically lifting blocks on closed nodes. —[admin] Pathoschild 01:41, 24 October 2006 (UTC)

Indefinite blocking

What is the reason for indefinitely blocking? These IPs are going to change at some point, and someone is going to have to take the time to unblock them all. Why not block for 1 year or 3 years? Centrx 23:32, 28 October 2006 (UTC)

Recent changes to the templates make this easy to do, if there is support for this. The problem with temporary blocking is that userpages will need to be untagged when the block is lifted, unless we stop tagging them. It must also be noted that many open proxies will remain open, so open proxies will automatically become re-exploitable after the given period.

I'm working on a detailed database interface to track and manage blocked proxies across all projects; the blacklist and category are rigid, non-scalable, and (in the case of the category) easily abused. I could integrate a search for temporarily blocked proxies that will be lifted soon, which will let us recheck them and extend the block if necessary. —[admin] Pathoschild 17:10, 29 October 2006 (UTC)

If this checks blocked open proxies to see if they are still open proxies, then time-limited blocks wouldn't be necessary—but that assumes this tool is implemented and is still running after 3 years. Centrx 06:16, 2 November 2006 (UTC)

The database is being actively developed at ProxyDB (since it's being developed, don't be surprised if you see errors when following that link). The database will be regularly backed up, so that even if it goes down I or another user can host it elsewhere. However, it doesn't scan proxies itself, since that's a complex task that cannot be done automatically without falsely determining that many open proxies are closed. —[admin] Pathoschild 21:21, 2 November 2006 (UTC)

To follow up, I haven't found a single one that is still an open proxy in the batch blocked on June 2004. One set, for example, was a wi-fi service at truck stops offered by a company that discontinued all service. This was only 2.5 years ago. I already checked all the ones before that time and none of them were still open proxies either. Indefinitely blocking proxies really just makes work, and the "policy" does more harm than good with people blocking Tor nodes on dynamic IPs that will have changed in a week, let alone a 3 years. —Centrx→talk • 07:03, 15 November 2006 (UTC)