User talk:Nlu/archive12

Murong Chui

hi, just asking is this the character you were looking for? "缺" "quē" meaning to be short of, lacking, or a gap/deficit. Abstrakt 00:11, 18 February 2006 (UTC)[reply]

No. The character that Murong Chui had is far rarer, although it does have the same derivation as 缺 -- it shares the same right radical, but the left side is 垂 (which was part of the reason why Murong Jun later chnaged Que to Chui). --Nlu (talk) 02:04, 18 February 2006 (UTC)[reply]

from Talk: Main Page

AOL blocks of almost 2 hours?

applied to anyone who complains about their ip range being blindly blocked for 75 minutes?--205.188.116.138 19:30, 18 February 2006 (UTC)[reply]

Well, the nature of the ip system means that the same user can use different ips and so it becomes hard to pinpoint the offenders and block them Yellowmellow45 19:36, 18 February 2006 (UTC)[reply]

Hello, Nlu. The above came from Talk:Main Page. (I'll remove it from that talk page.) I thought you may want to handle this yourself. Take care. -- PFHLai 20:22, 18 February 2006 (UTC)[reply]

Thanks. Basically, I don't believe it warranted a further response. --Nlu (talk) 20:44, 18 February 2006 (UTC)[reply]

OF course not, when a user politly reminds you that you've blocked over a 3rd of AOL users for no reason, the only possible response is to range block AOL for an absurd period of time--64.12.116.71 21:11, 18 February 2006 (UTC)[reply]

It was a 24-bit address block -- nowhere close to a third of AOL addresses. Of course, facts don't matter with vandals anyway. --Nlu (talk) 21:15, 18 February 2006 (UTC)[reply]

AOL only operates 3 IP ranges, 64.x.x.x, 152.x.x.x, and 205.x.x.x, blocking one of those ranges leaves 1/3rd of AOL users blocked, your logic only works if you honetly think has AOL control over all ranges from 1.0.0.0 through to 255.255.255.255, also would you also please stop making generic personal attacks against random AOL users--64.12.116.71 21:18, 18 February 2006 (UTC)[reply]

Note:I am AOL, and I am 172.x.x.x. Ian13/talk 21:21, 18 February 2006 (UTC)[reply]

Specifically, these are AOL address ranges:

AOL IP Ranges

64.12.0.0/16 64.12.0.0 – 64.12.255.255 1)
149.174.0.0/16 149.174.0.0 – 149.174.255.255
152.163.0.0/16 152.163.0.0 – 152.163.255.255 2)
172.128.0.0/10 172.128.0.0 - 172.216.255.255<--Non-portable-DSL-AOL-range
172.192.0.0/12<--Non-portable-DSL-AOL-range
172.208.0.0/13<--Non-portable-DSL-AOL-range
172.216.0.0/16<--Non-portable-DSL-AOL-range
195.93.0.0/17 195.93.0.0 – 195.93.127.255<--Non-US-AOL IP range
198.81.0.0/19 198.81.0.0 – 198.81.31.255<--Non-US-AOL IP range
202.67.64.0/18 202.67.64.0 – 202.67.127.255<--Non-US-AOL IP range
205.188.0.0/16 205.188.0.0 – 205.188.255.255 3)
207.200.64.0/18 207.200.64.0 – 207.200.127.255<--Non-US-AOL IP range

I didn't block 64.x.x.x; I blocked 64.12.116.x -- a very small subset of the range -- and as indicated above, it's false that AOL only operates 3 IP ranges. I blocked, at most, less than .01% of all AOL addresses, clearly all coming from the same dialup pool. Don't twist facts. But I guess that's what vandals do. --Nlu (talk) 21:20, 18 February 2006 (UTC)[reply]

True, if you count all the non-portable DSL ranges, and the AOL canada ranges, and the EU ranges, you only blocked 1/3rd of all AOL users in the United States--64.12.116.71 21:25, 18 February 2006 (UTC)[reply]
- Note: He blocked a small subnet (with a max 255 users) 64.12.116.x of USA AOL. Ian13/talk 21:29, 18 February 2006 (UTC)[reply]
  - Note: Multiple AOL users are assigned to the same ip address at the same time, like it says on the tempalte--64.12.116.71 21:32, 18 February 2006 (UTC)[reply]

Even assuming arguendo all you are saying is true, it's still not 1/3 -- since I blocked 64.12.116.x -- 1/256 of 64.12.x.x. But I guess you can't do math. One more false accusation out of you and you're going back into the block. --Nlu (talk) 21:27, 18 February 2006 (UTC)[reply]

This is ridiculous, if you want to range block a third of AOL, I can't stop you, the other administrators who are use AOL tend to get annoyed, but I can't do anything about it--64.12.116.71 21:34, 18 February 2006 (UTC)[reply]

It's still not a third (as I've pointed out multiple times) even if all you are saying is, arguendo, true; it's 1/768. Since you have not held off on an assertion that has been demonstrated to be false, you've been blocked for another 75 minutes. Enjoy your break. --Nlu (talk) 21:37, 18 February 2006 (UTC)[reply]

Ignoring the fact that you're blocking someone for disagreeing with you on a talk page, there's also another problem, it is a third, the only argument you've made is that it's not really a third, because if AOL users really wanted to avoid a block they could travel to canada, and use AOL-canada's IP ranges, it's an insane argument--64.12.116.71 21:45, 18 February 2006 (UTC)[reply]

What part of "64.12.116.x is 1/256 of 64.112.x.x" do you not understand? Of course, I don't believe you don't really not understand it; you're choosing to misrepresent the facts. --Nlu (talk) 21:47, 18 February 2006 (UTC)[reply]

For the record, I'm still right, and that's still a terrible reason to level a range block--205.188.117.8 22:11, 18 February 2006 (UTC)[reply]

AOL

AOL is a unique provider; not only do their IPs shift for every page load, but even if a person remains static on a page (say, loads a page and spends twenty minutes working through it before loading it again) their IP will change after 15 minutes. That is why AOL blocks are limited to 15 minutes; it's almost impossible to hit the person you are trying to get: By the time you click block, they are already on another IP, and even if you manage to hit them before they switch, they will switch within 15 minutes, guaranteed. I unblocked because another user was hit with the block; that's evidence the IP you blocked is no longer being used by the person you are trying to block. Essjay ^{Talk • Contact} 21:49, 18 February 2006 (UTC)[reply]

The person is keep coming back with the same IP (see above). --Nlu (talk) 21:50, 18 February 2006 (UTC)[reply]

And -- since the block went back in, the person has been quiet. --Nlu (talk) 21:52, 18 February 2006 (UTC)[reply]

Based on what I've observed the last two months, I must say I don't believe any more that AOL IPs change every time you reload the browser, since so many vandals have vandalized many pages from the same IP, at least in the same session. I find it far more likely that an IP is assigned to a dialin user, and then unassigned when that user hangs up. This would explain why vandals come back as different IPs the next time (say, a couple hours later or a couple days later), but vandalize from the same account during the same session; they hadn't hung up. The behavior of the user above corroborates, I think. --Nlu (talk) 21:57, 18 February 2006 (UTC)[reply]

That's fine, but it's patent nonsense, and you're blocking an entire range because you don't "believe" in sharedips--205.188.117.8 22:01, 18 February 2006 (UTC)[reply]

Aol ips change with every page they load because they're not assigned per-user, they're assigned per-page--205.188.117.8 22:02, 18 February 2006 (UTC)[reply]

I believe in shared IPs alright; that's why I add {{sharedip}} with abandon.

However, in this case, it was clear that this person is continuing to post from the IP way past the 15 minute behavior described above. --Nlu (talk) 22:04, 18 February 2006 (UTC)[reply]

Again, that's because the "15 minute window" thing is essentially made up to avoid long, drawn out incidents like this one, when dealing with CS challenged individuals, AOL blocks are pointless, and they do change with each page they load, the "15 minute window" just isn't the reason they do--205.188.117.8 22:09, 18 February 2006 (UTC)[reply]

And? Note how you yourself are coming back with the same IP, even though you've obviously reloaded the page a number of times. Again, I believe that the IP is now shared based on your dialin session, and by blocking for 75 minutes rather than 15, I am hoping to at least force the vandal to hand up and dial back in, which takes time and slows down the vandalism significantly. --Nlu (talk) 22:11, 18 February 2006 (UTC)[reply]

And, as a corollary, try hang up and dialing back in. Until you do, I don't think you'll get a different IP. --Nlu (talk) 22:14, 18 February 2006 (UTC)[reply]

How can I hang up, I'm using a wifi connection, again, that doesn't make any sense, this isn't a dialup range, and yes of course I have a different ip on other pages, watch Talk:hat, I'll add the word hello, then rvert the changes, then come back here--205.188.117.8 22:17, 18 February 2006 (UTC)[reply]

[1], and yet, on this page I still have the same IP, convinced?--205.188.117.8 22:19, 18 February 2006 (UTC)[reply]

What is the nature of your Wifi connection? It still has to be connecting to a wireless router that connects to AOL in a given way -- dialup or DSL or a higher speed connection. You can't directly wirelessly connect to AOL, since AOL doesn't operate WiFi entry points. --Nlu (talk) 22:20, 18 February 2006 (UTC)[reply]

Broadband/DSL, and if you think I'm actually walking upstairs and logging off of an "always on" connection just to make some kind of point, then you've under estimated my laziness--205.188.117.8 22:22, 18 February 2006 (UTC)[reply]

Now, as I was saying prior to an edit confict, the ip I was given while editing the "talk:hat" page, was 205.188.117.13, and had edited the page List of characters from King of Fighters a few days ago, I will now edit that page myself, and I will be given the same IP, will then come back here, and be given my origional ip back again--205.188.117.8 22:24, 18 February 2006 (UTC)[reply]

as promised, now do you understand why AOL range blocks affect an odd number of users?--205.188.117.8 22:27, 18 February 2006 (UTC)[reply]

I'll edit a different page, if you wish, how about Talk:bat, one ip here, one ip there--205.188.117.8 22:27, 18 February 2006 (UTC)[reply]

same thing happens, and yet, same ip here, so either I'm clairvoyant, or I actually know what I'm talking about--205.188.117.8 22:29, 18 February 2006 (UTC)[reply]

And back to the origional point, if you had the choice of either explaining/demonstrating all of that to every single wikipedia administrator, or, making up some thing about "15 minute ip windows" that was easy to swallow, yet technically incorrect, which would you choose?--205.188.117.8 22:32, 18 February 2006 (UTC)[reply]

[I don't know], I've never been given a 149.anything, and I pretty much cycle through the big 3(205, 152, and 64) just about every day, maybe that range is non-portable?--205.188.117.8 22:42, 18 February 2006 (UTC)[reply]

Well, I think you've actually demonstrated that a block may be effective -- in that the vandal might not be able to come back to the page he/she vandalized -- but obviously, collateral damage is the issue and that is known already. In the case of the vandal I was chasing this morning, however, he/she was roving through a variety of IPs in that subnet. --Nlu (talk) 22:49, 18 February 2006 (UTC)[reply]

That is an interesting point, you could probably stop someone from editing a given page, as long as you keep in mind that you're not blocking the vandal per say, rather you're blocking AOL users, a large number of them, from editing that page, for the length of the block, as well as any other pages that AOL has assinged that specific ip to,

but in theory, yes, you could stop all AOL access to a given page by looking in it's history, and finding the 3 specific IP addresses AOL has assigned to that page, would completly eliminate the need for range blocks, since whenever they come back to that page, they'll be hit with a block--205.188.117.8 22:55, 18 February 2006 (UTC)[reply]

which is why AOL auotblocks are such a PITA, all a blocked RU has to do is edit a half a dozen pages with AOL, and they've blocked all AOL users from editing the same page for the next 24 hours--205.188.117.8 22:57, 18 February 2006 (UTC)[reply]

and another problem, this leaves most AOL users wide open for impersonation, for instance this mess, has to have been created by more than one person, unless this page was edited by someone with a compulsion for self-reverts--205.188.117.8 23:01, 18 February 2006 (UTC)[reply]

And a final point, using the [edit] button will not only allow you to have a different ip on the same page, it will actually assign you, in some cases, a different ip for each section of each article, that is retained every time you edit that one section--205.188.117.8 23:03, 18 February 2006 (UTC)[reply]

If you still think the "15 minute window" is an unreasonable white lie, then perhaps we should subst: your user page into the AOL template --205.188.117.8 23:04, 18 February 2006 (UTC)[reply]

would you mind

If I copied the content from the last two topics, to a subpage /AOL, and linked to there from template talk:AOL? might actually be a better explanation than the template itself--205.188.117.8 23:11, 18 February 2006 (UTC)[reply]

...and per that page, a list of all wikipedia users currently flagged with template:AOL,

64.12.112.186       spider-mtc-tb121.proxy.aol.com.          Country: UNITED STATES (US)    City: (Unknown city)          
64.12.116.5         cache-mtc-aa01.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.6         cache-mtc-aa02.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.7         cache-mtc-aa03.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.8         cache-mtc-aa04.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.9         cache-mtc-aa05.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.10        cache-mtc-aa06.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.11        cache-mtc-aa07.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.13        cache-mtc-aa09.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.14        cache-mtc-aa10.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.65        cache-mtc-ab01.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.67        cache-mtc-ab03.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.68        cache-mtc-ab04.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.69        cache-mtc-ab05.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.72        cache-mtc-ab08.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.74        cache-mtc-ab10.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.130       cache-mtc-ac01.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.131       cache-mtc-ac02.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.132       cache-mtc-ac03.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.133       cache-mtc-ac04.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.135       cache-mtc-ac06.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.136       cache-mtc-ac07.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.138       cache-mtc-ac09.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.139       cache-mtc-ac10.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.195       cache-mtc-ad01.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.196       cache-mtc-ad02.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.197       cache-mtc-ad03.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.198       cache-mtc-ad04.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.199       cache-mtc-ad05.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.201       cache-mtc-ad07.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.203       cache-mtc-ad09.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.116.204       cache-mtc-ad10.proxy.aol.com.            Country: UNITED STATES (US)    City: Elizabethtown, PA       
64.12.117.5         cache-mtc-ae01.proxy.aol.com.            Country: UNITED STATES (US)    City: Milwaukee, WI           
64.12.117.6         cache-mtc-ae02.proxy.aol.com.            Country: UNITED STATES (US)    City: Milwaukee, WI           
64.12.117.7         cache-mtc-ae03.proxy.aol.com.            Country: UNITED STATES (US)    City: Milwaukee, WI           
64.12.117.8         cache-mtc-ae04.proxy.aol.com.            Country: UNITED STATES (US)    City: Milwaukee, WI           
64.12.117.9         cache-mtc-ae05.proxy.aol.com.            Country: UNITED STATES (US)    City: Milwaukee, WI           
64.12.117.11        cache-mtc-ae07.proxy.aol.com.            Country: UNITED STATES (US)    City: Milwaukee, WI           
64.12.117.12        cache-mtc-ae08.proxy.aol.com.            Country: UNITED STATES (US)    City: Milwaukee, WI           
64.12.117.13        cache-mtc-ae09.proxy.aol.com.            Country: UNITED STATES (US)    City: Milwaukee, WI           
64.12.117.14        cache-mtc-ae10.proxy.aol.com.            Country: UNITED STATES (US)    City: Milwaukee, WI           
64.12.117.15        cache-mtc-ae11.proxy.aol.com.            Country: UNITED STATES (US)    City: Milwaukee, WI           
64.12.117.16        cache-mtc-ae12.proxy.aol.com.            Country: UNITED STATES (US)    City: Milwaukee, WI           
64.12.117.18        cache-mtc-ae14.proxy.aol.com.            Country: UNITED STATES (US)    City: Milwaukee, WI           
64.12.117.19        cache-mtc-ae15.proxy.aol.com.            Country: UNITED STATES (US)    City: Milwaukee, WI                   
152.163.100.5       cache-rtc-aa01.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.7       cache-rtc-aa03.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.8       cache-rtc-aa04.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.10      cache-rtc-aa06.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.11      cache-rtc-aa07.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.12      cache-rtc-aa08.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.67      cache-rtc-ab03.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.69      cache-rtc-ab05.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.72      cache-rtc-ab08.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.131     cache-rtc-ac02.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.134     cache-rtc-ac05.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.136     cache-rtc-ac07.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.138     cache-rtc-ac09.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.196     cache-rtc-ad02.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.197     cache-rtc-ad03.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.199     cache-rtc-ad05.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.100.200     cache-rtc-ad06.proxy.aol.com.            Country: UNITED STATES (US)    City: Columbus, OH            
152.163.101.5       cache-rtc-ae01.proxy.aol.com.            Country: UNITED STATES (US)    City: Woonsocket, RI          
152.163.101.6       cache-rtc-ae02.proxy.aol.com.            Country: UNITED STATES (US)    City: Woonsocket, RI          
152.163.101.7       cache-rtc-ae03.proxy.aol.com.            Country: UNITED STATES (US)    City: Woonsocket, RI          
152.163.101.8       cache-rtc-ae04.proxy.aol.com.            Country: UNITED STATES (US)    City: Woonsocket, RI          
152.163.101.10      cache-rtc-ae06.proxy.aol.com.            Country: UNITED STATES (US)    City: Woonsocket, RI          
152.163.101.11      cache-rtc-ae07.proxy.aol.com.            Country: UNITED STATES (US)    City: Woonsocket, RI          
152.163.101.12      cache-rtc-ae08.proxy.aol.com.            Country: UNITED STATES (US)    City: Woonsocket, RI          
152.163.101.13      cache-rtc-ae09.proxy.aol.com.            Country: UNITED STATES (US)    City: Woonsocket, RI          
152.163.101.14      cache-rtc-ae10.proxy.aol.com.            Country: UNITED STATES (US)    City: Woonsocket, RI          
172.140.60.31       AC8C3C1F.ipt.aol.com.                    Country: UNITED STATES (US)    City: (Unknown city)          
172.141.55.83       AC8D3753.ipt.aol.com.                    Country: UNITED STATES (US)    City: (Unknown city)          
172.147.127.192     AC937FC0.ipt.aol.com.                    Country: UNITED STATES (US)    City: (Unknown city)          
172.154.252.158     AC9AFC9E.ipt.aol.com.                    Country: UNITED STATES (US)    City: (Unknown city)          
172.156.166.149     AC9CA695.ipt.aol.com.                    Country: UNITED STATES (US)    City: Atlanta, GA             
172.166.132.40      ACA68428.ipt.aol.com.                    Country: UNITED STATES (US)    City: (Unknown city)          
172.166.159.19      ACA69F13.ipt.aol.com.                    Country: UNITED STATES (US)    City: (Unknown city)          
172.188.227.80      ACBCE350.ipt.aol.com.                    Country: UNITED STATES (US)    City: (Unknown city)          
172.197.22.251      ACC516FB.ipt.aol.com.                    Country: UNITED STATES (US)    City: (Unknown city)          
172.198.8.59        ACC6083B.ipt.aol.com.                    Country: UNITED STATES (US)    City: Anaheim, CA             
172.212.113.115     ACD47173.ipt.aol.com.                    Country: (Unknown Country?) (XX) City: (Unknown City?)         
195.93.21.40        cache-los-ab08.proxy.aol.com.            Country: UNITED KINGDOM (UK)   City: Sudbury                 
195.93.21.68        cache-los-ac04.proxy.aol.com.            Country: UNITED KINGDOM (UK)   City: Sudbury                 
195.93.21.104       cache-los-ad08.proxy.aol.com.            Country: UNITED KINGDOM (UK)   City: Sudbury                 
198.81.26.39        None                                     Country: UNITED STATES (US)    City: APPLE VALLEY, CA        
198.81.26.41        None                                     Country: UNITED STATES (US)    City: APPLE VALLEY, CA        
205.188.116.6       cache-dtc-aa02.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.7       cache-dtc-aa03.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.8       cache-dtc-aa04.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.9       cache-dtc-aa05.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.11      cache-dtc-aa07.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.12      cache-dtc-aa08.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.13      cache-dtc-aa09.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.14      cache-dtc-aa10.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.65      cache-dtc-ab01.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.66      cache-dtc-ab02.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.67      cache-dtc-ab03.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.68      cache-dtc-ab04.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.69      cache-dtc-ab05.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.70      cache-dtc-ab06.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.71      cache-dtc-ab07.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.72      cache-dtc-ab08.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.74      cache-dtc-ab10.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.130     cache-dtc-ac01.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.131     cache-dtc-ac02.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.132     cache-dtc-ac03.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.133     cache-dtc-ac04.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.135     cache-dtc-ac06.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.136     cache-dtc-ac07.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.137     cache-dtc-ac08.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.138     cache-dtc-ac09.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.139     cache-dtc-ac10.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.171     None                                     Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.195     cache-dtc-ad01.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.196     cache-dtc-ad02.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.197     cache-dtc-ad03.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.201     cache-dtc-ad07.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.202     cache-dtc-ad08.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.203     cache-dtc-ad09.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.116.204     cache-dtc-ad10.proxy.aol.com.            Country: UNITED STATES (US)    City: Reading, PA             
205.188.117.6       cache-dtc-ae02.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
205.188.117.7       cache-dtc-ae03.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
205.188.117.10      cache-dtc-ae06.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
205.188.117.12      cache-dtc-ae08.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
205.188.117.13      cache-dtc-ae09.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
205.188.117.14      cache-dtc-ae10.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
205.188.117.65      cache-dtc-af01.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
205.188.117.66      cache-dtc-af02.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
205.188.117.67      cache-dtc-af03.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
205.188.117.69      cache-dtc-af05.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
205.188.117.70      cache-dtc-af06.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
205.188.117.71      cache-dtc-af07.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
205.188.117.72      cache-dtc-af08.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
205.188.117.73      cache-dtc-af09.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
205.188.117.74      cache-dtc-af10.proxy.aol.com.            Country: UNITED STATES (US)    City: ALEXANDRIA, LA          
207.200.116.65      cache-ntc-ab01.proxy.aol.com.            Country: UNITED STATES (US)    City: Farmington, NM          
207.200.116.139     cache-ntc-ac10.proxy.aol.com.            Country: UNITED STATES (US)    City: Farmington, NM          
207.200.116.200     cache-ntc-ad06.proxy.aol.com.            Country: UNITED STATES (US)    City: Farmington, NM

which means that blocking all of 64, would have actually come pretty close to blocking a third of all documented AOL users on wikipedia, give or take--205.188.117.8 23:17, 18 February 2006 (UTC)[reply]

No, I don't mind that. --Nlu (talk) 00:05, 19 February 2006 (UTC)[reply]

Vandalism

Thank you for reverting the sillyness on my talk page. Seems the same edit returns with different IP's. Is it possible to prevent my page from being molested on a daily basis? Nomen Nescio 05:19, 19 February 2006 (UTC)[reply]

No, not really, unless you request it be protected, which is usually not worth it to do, in my opinion. --Nlu (talk) 05:35, 19 February 2006 (UTC)[reply]

Too bad I can't be an admin for my own page. Then I could protect and unprotect it myself when I need to. Can't help but think that it is VinnyCee trying to make point. Let's see what happens. Thanks.

Nomen Nescio 11:16, 19 February 2006 (UTC)[reply]

Thank you once again. Somebody really likes me. This must be VinnyCee who is using different IP's to make a point. Boring.

Nomen Nescio 07:28, 20 February 2006 (UTC)[reply]

Could be, but there's no way to get conclusive evidence; not even a CheckUser would help. --Nlu (talk) 07:30, 20 February 2006 (UTC)[reply]

I noticed you blocked 67.72.98.82. That actually does not make sense: Some of the edits of 67.72.98.82 are actually mine. This IP address is one of the IPs that is assigned by the ISP provider; therefore blocking it doesn't do any good: next time the perpetrator dials in he may get a different IP address assigned. JdH 16:03, 20 February 2006 (UTC)[reply]

Image

Is it OK to transfer a image of a USMC DI to my User page ? Martial Law 10:00, 19 February 2006 (UTC)[reply]

Someone threw it out of Wikipedia:Boot camp. Martial Law 10:01, 19 February 2006 (UTC)[reply]

That depends on whether the image is public domain or fair use or not. If it's copyrighted, it won't work no matter where you place it unless you can successfully assert fair use. --Nlu (talk) 15:41, 19 February 2006 (UTC)[reply]

It was a US Marine Sgt. bellowing at USMC recruits, and it is in the public domain. Just being cautious. Martial Law 04:08, 20 February 2006 (UTC) :)[reply]

Dylan's Birthdate

I noticed your Rv, and it reminded me of something I've always meant to point out. On the cover of the book that comes with The Bootleg Series Vol 1-3, there's a photo of his passport that shows his date of birth as the 11th and not the 24th. Do you think that the State Department made a mistake, or has he been lying about his birthdate? I'd be interested to know what you make of this. Cheers, Lion King 17:02, 19 February 2006 (UTC)[reply]

Well, it's that sources I can find all say May 24, and since the anon does not give a source, I reverted him/her. If you believe that May 11 is reliable, please go ahead and change it and discuss it on the talk page. --Nlu (talk) 21:24, 19 February 2006 (UTC)[reply]

Not taking issue with your Rv, I would have done the same. I've seen a copy of his birth certificate, says the 24th. Just wanted to know if there was any way a mistake could occour on a U.S. passport. Maybe it's a fake and it's just one more example of one of his "hidden" visual jokes. Lion King 22:01, 19 February 2006 (UTC)[reply]

Could be a fake, or could be that he put down the wrong date, either accidentally or not. Back several decades ago the government didn't check things as carefully. --Nlu (talk) 22:24, 19 February 2006 (UTC)[reply]

Thanks for your time, I suppose someone will have to bell him on his radio show and ask him! cheers, be lucky, Lion King 22:34, 19 February 2006 (UTC)[reply]

Wikipedia rules

Can I ask for some advise? I am having a discussion on what can and cannot be used on Wikipedia. Several editors want to dismiss certain information claiming it is not supported or that it is biased. As I see it, in controversial issues there is always bias, but we must try and present all views so that readers can be informed on the existing views surrounding that subject. All I want to know is: can information be used from sources that are said to be POV?

For more details you can look here. Thank you.-- Nomen Nescio 16:38, 19 February 2006 (UTC)[reply]

I can't review it right now, but this is my thought: sources that are POV can be used, but the information that come from them have to be carefully examined for POVness, and that POVness should be removed; the NPOV facts can go in. --Nlu (talk) 16:44, 19 February 2006 (UTC)[reply]

Thanks for the comment. At this time even the facts are disputed. Sadly the RfC elicits hardly any response. Anyway, on the bright side, I noticed you had some fun with new personal attacks by VinnyCee? At least, I would be surprised if it was somebody else. Thanks for correcting.

Nomen Nescio 00:08, 22 February 2006 (UTC)[reply]

2004 New Hampshire General Court Election

Well, it depends on your definition of under construction. It's definately nowhere near done, but I doubt i'll have enough time to get it done anytime soon, the tables are a bitch to do. Karm a fist 23:30, 19 February 2006 (UTC)[reply]

Please consider.

You have given me a warning and please apologize me for what I have done. But please consider monitoring the article "Fimu"; it is the nickname I use over the internet and someone called "Japa" has kept changing it to gross and bad things such as anal masturbation and such (I would have to rechange it for something else afterwards everytime - check log). I would kindly ask you, moderation team, to enforce this monitoring over this "Thread", otherwise I will have to take measures myself (it is a public webpage and I can't really let something that I use to identify myself being denigrated - for he spams the link all over the place.) —Preceding unsigned comment added by 200.139.161.36 (talk • contribs)

and just to remind u. you're the one who told me i'm allowed to post controversial images on my talk page without endorsing them —Preceding unsigned comment added by Freestyle.king (talk • contribs)

I don't get your point. I didn't remove the image. --Nlu (talk) 05:33, 20 February 2006 (UTC)[reply]

..

ok fine...my bad. but why exactly is your reason for blockin me?? i didn't even sign on o and please reply to me on my talk page.--Freestyle.king 05:53, 20 February 2006 (UTC) well i still can't see nothin wrong with my comment. i simply told him that his picture is insulting the people in Taiwan and the president. is theresomethin wrong with it???--Freestyle.king 06:25, 20 February 2006 (UTC)[reply]

I've already explained: he already informed you he didn't agree with the man's message. And don't presume to speak for the people in Taiwan. --Nlu (talk) 06:28, 20 February 2006 (UTC)[reply]

And, oh, I can tell exactly what edits you made. Every user's contributions is visible by clicking on "user contributions" from his/her user page or user talk page, so don't think I can't tell what you edited. --Nlu (talk) 06:28, 20 February 2006 (UTC)[reply]

i know you can, but all i'm sayin is jiang himself already warned me so there was no need for you to block me. plus you were the one who told me to assume he didn't agree wif the man and i'm wonderin how you will feel if some dude on the net who happens to be a admin has a picture on his talk page sayin "your country"=shame?--Freestyle.king 06:37, 20 February 2006 (UTC) and by da way, you're not allow to edit jiang's talk page —Preceding unsigned comment added by Freestyle.king (talk • contribs) [reply]

Nonsense. I've already given you more patience than you deserved. For this latest nonsense you are getting blocked again. --Nlu (talk) 06:39, 20 February 2006 (UTC)[reply]

WS

Hi, Here is a vote related to Western Sahara. Neutrality of WP is dying, please save it! Daryou 07:48, 20 February 2006 (UTC)[reply]

User talk:12.210.1.200

He's asked for three admins to look at the case and make a decision; so I wanted to know if you would like to look at the case. He promised ME he would never vandalize again, I don't like it when people come back on their promises; he deserves a permanent ban. As I said I am going to ask three admins: you, User:Flockmeal, and User:Antandrus.--Holocron 15:15, 20 February 2006 (UTC)[reply]

We don't permanently block anonymous IPs (except open proxies), so we won't do that. Since I've made my ruling before, I am not going to change it; nothing has changed. --Nlu (talk) 18:11, 20 February 2006 (UTC)[reply]

Police State

Good call! [2] Cheers, The Minist e r of War ^(Peace) 21:51, 20 February 2006 (UTC)[reply]

Thanks. --Nlu (talk) 21:52, 20 February 2006 (UTC)[reply]