Wikipedia:Requests for checkuser/Case/LossIsNotMore
LossIsNotMore - 7
request links: main • edit • links • history • watch |
- Biochem67 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- E.Meany (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Code letter: F
Comment
- Proven socks of James Salsman are subject to immediate indefinite block; see Category:Wikipedia sockpuppets of Nrcprm2026.
- Biochem67 was flagged by User:ScienceApologist as a potential sock of James, based on topical similarity in edit history. [1]
- E.Meany has made a suspiciously knowledgeable objection at Talk:Ron Paul. [2]
- In both cases the evidence is only suggestive, not probative, so CU is indicated.
- Please expedite, and see if any other socks turn up. Thank you! John J. Bulten (talk) 15:54, 21 November 2007 (UTC)
- Please explicitly state the block master. This case is called "LossIsNotMore", and you refer to both "James Salsman" and "Nrcprm2026" in your post. In addition, please explicitly link to the block log of the sockmaster, as instructed at the table at the top of WP:RFCU. --Deskana (talk) 18:24, 22 November 2007 (UTC)
- Pardon me, I'll learn it. The block master is User:Nrcprm2026. The block log is [3]. User:LossIsNotMore is a frequently named proven sock. User:Squee23 and User:Publicola are recent proven socks. Is there anything amiss? John J. Bulten (talk) 00:15, 23 November 2007 (UTC)
- Please explicitly state the block master. This case is called "LossIsNotMore", and you refer to both "James Salsman" and "Nrcprm2026" in your post. In addition, please explicitly link to the block log of the sockmaster, as instructed at the table at the top of WP:RFCU. --Deskana (talk) 18:24, 22 November 2007 (UTC)
Confirmed - plus other probable socks;
- Wind75 (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- 1conti1tosi1rovere1paganini1 (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- LKirkby (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- Spc303 (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Clerk note: all blocked and tagged, the probs as suspected. Moving to completed section. — Rlevse • Talk • 22:23, 23 November 2007 (UTC)
LossIsNotMore - 6
request links: main • edit • links • history • watch Filed: 23:59, 26 June 2007 (UTC) |
- BenB4 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki) indefinitely blocked 9/28 by Moreschi
- JLeclerc (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Starkrm (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Acct4 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki) indefinitely blocked 10/3 by Tariqabjotu
- Pdilla (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- 1of3 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki) indefinitely blocked 10/18 by Morven
- Squee23 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Dlabtot (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Code letter: B, F(RfAr probation)
I would wager to say that James has many, many accounts and they will continue popping up for the foreseeable future. It makes sense to check these out anyways. He said the following to me in an email: "The worst thing I did, from my perspective, was to unify my watchlist and not wait a full month for checkuser records to go stale.".
Obviously, he understands how to game the system now, and it might be worth while to log his IP and keep a record of it, instead of getting rid of it after the checkuser.
There needs to be a better way to deal with him, and admins really need to keep a better eye on the articles he edits. Torturous Devastating Cudgel 03:03, 16 October 2007 (UTC)
- 100% agreement with T.D. Cudgel! See my request.
- I think the evidence is sufficient in the cases of 1of3 and 209.77.205.2 without CU, but let's please get a couple admins to keep a watch out for this crittur. John J. Bulten 15:33, 17 October 2007 (UTC) refactored by John J. Bulten 17:44, 1 November 2007 (UTC)
(unindent) :I identified User:Acct4 as a sock of User:BenB4 back at the end of September and notified [User:TDC|Torturous Devastating Cudgel]] of this. There is another sock not in the list above, not that it is terribly important, since it was an SPA sacrificed to attempt to get me sanctioned, that would be P-j-t-a. User:Acct4 was trivial to identify by the articles edited; User:Acct4 was created just before User:BenB4 was blocked, and simply continued editing the same articles. P-j-t-a was likewise easy to identify. Since when does a newly registered user, as their only two actions, warn me and file a 3RR report? That's not proof, it is merely a big red flag waving that this is *probably* a sock or meat puppet, like 99.9%. Ah, yes, and the 3RR report had a typographical error in it, which was fixed 2 hours later by User:Acct4, see Special:Contributions/Acct4. Oops! The red flag waving had User:Acct4 on it in big letters. In any case, this is a known liberal creator of sock puppets, and watching articles known to be of interest to him for suspicious edits isn't "fishing" in any reprehensible sense. Nobody should be blocked on suspicion. However, the damage a sock can do is mostly to new users, so we should indeed be careful to avoid or ameliorate it. A new user gets fired up about an article, puts several hours into editing it, and comes back the next day and all the work has gone missing. The new user does not necessarily know how to figure out what happened, I'd wager that most new users don't know what History does. And so they go away with the impression that Wikipedia is controlled by somebody who does not like what they would contribute, and that it is all a waste of time. But if "we" are watching articles, and take pains to support new users who are massively reverted (even if it was legitimate to revert, but I'm not talking about vandalism, merely an inappropriate edit by a new user), then we can avoid most of the damage. When User:BenB4 reverted material he did not like, he did not put it on the Talk page, and his reasons, if he stated any, would often be of a kind to confound new users, and he certainly did not attempt to help the new user to understand the guidelines and work within them. We should not depend on administrators to do the work of identifying sock puppets, and if we do it, i.e., the general user community, we will, I'm sure, make mistakes. But if administrators, in particular, treat suspected socks with courtesy, there will be little problem from these mistakes. What I found in my own process, though, was that it was extraordinarily difficult to get anything done about what I had found. I now know better how to proceed, but I have had to figure it out piecemeal. I was given patronizing advice about "Assume Good Faith," which would have been fine if I did not already assume that unless there was overwhelming evidence to the contrary. Administrators are overworked and underfed. Underfed administrators will, I'm sure, get cranky and they must make snap decisions. This can be fixed, actually. --Abd 19:13, 1 November 2007 (UTC)
Thanks to User:Morven for indef-blocking 1of3. I think Starkrm definitely needs indef block CU, and Pdilla and JLeclerc and the IPs need CU. John J. Bulten 17:43, 18 October 2007 (UTC)
- What's the main account here? Please make this clear. --Deskana (talk) 08:39, 27 October 2007 (UTC)
- The main account is James S, but since that has gone stale, I put BenB4 up as well, as he was recently confirmed as a James' socukpuupet. Torturous Devastating Cudgel 14:15, 27 October 2007 (UTC)
- Deskana, I'd appreciate it if you could add Squee23 to the mix, which looks like a new puppet of somebody. And since 209.77.205.2 is now the active account making James-type edits, and both it and Squee23 are editing the fundraising template, I think I know who too. I'll probably make a new SSP request, which may show up here. John J. Bulten 16:22, 29 October 2007 (UTC)
- Also added Dlabtot. John J. Bulten 02:54, 31 October 2007 (UTC)
- While awaiting the checkuser, I've also posted a clarifying response. John J. Bulten 15:42, 31 October 2007 (UTC)
- Without more evidence, this looks like fishing to me. This is added to by the fact that the two IPs you've provided resolve to two different locations; it's highly unlikely the same person is editing from both locations, and checkuser probably couldn't establish that as a fact even if it was the case. Please provide additional evidence linking the accounts together, in diff form with sections for each account, and linking them to the banned editor in question. --Deskana (talk) 01:35, 1 November 2007 (UTC)
- (Heaving sigh) OK, will throw something together. I'd appreciate it if TDC (and perhaps Starkrm) would handle the evidence pertaining to uranium while I do the political evidence. Sorry to throw this back, but I am regulating myself away from too much more accusation. John J. Bulten 17:44, 1 November 2007 (UTC)
- Without more evidence, this looks like fishing to me. This is added to by the fact that the two IPs you've provided resolve to two different locations; it's highly unlikely the same person is editing from both locations, and checkuser probably couldn't establish that as a fact even if it was the case. Please provide additional evidence linking the accounts together, in diff form with sections for each account, and linking them to the banned editor in question. --Deskana (talk) 01:35, 1 November 2007 (UTC)
- The main account is James S, but since that has gone stale, I put BenB4 up as well, as he was recently confirmed as a James' socukpuupet. Torturous Devastating Cudgel 14:15, 27 October 2007 (UTC)
- 209.77.205.2
9 diffs appear here. Also: 209.77.205.2 [4], BenB4 [5], Squee23 [6].
- 66.56.206.68
13 diffs appear here.
- Dlabtot
4 diffs appear here. Also: 209.77.205.2 [7], Dlabtot [8]. BenB4 has made 14 Stossel-related edits. This account has protested the accusation somewhat.
- Squee23
8 diffs appear here. See also 209 above. These are the most conclusive of the set IMHO.
- Starkrm
4 diffs appear here. This account has protested the accusation believably.
John J. Bulten 19:42, 1 November 2007 (UTC)
Confirmed Becongito = Squee23 = CME94 = Publicola = Lots of other accounts blocked socks. Other accounts unrelated. --Deskana (talk) 11:14, 3 November 2007 (UTC)
- But are you are not even the slightest bit suspicious that Starkm is not a sockpuppet of James Salsman? Did you take into account the nature of the edits to Depleted Uranium? Torturous Devastating Cudgel 13:00, 3 November 2007 (UTC)
- Dlabtot is not a sockpuppet of James Salsman?
- Unrelated means unrelated. The case is closed. --Deskana (talk) 13:24, 3 November 2007 (UTC)
- Dlabtot is not a sockpuppet of James Salsman?
request links: main • edit • links • history • watch Filed: 15:15, 27 September 2007 (UTC) |
- Nrcprm2026 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- LossIsNotMore (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- BenB4 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Code letter: B (RfAr probation)
I hope I am not going out on a limb here, but BenB4 has been making the same edits and arguments, nearly verbatim, on the Depleted Uranium article. After a little bit of digging, I have found that James Salsman and BenB4 have a few too many shared interests, and this is what made me suspicious of possible sockpuupetry: Shared Edits on Speciation, Gulf War syndrome, Nutrition Plug-in hybrid, Iraqi insurgency, Battery electric vehicle, Iraq War, Uranium, Nutrition, Art.Net, Wrongful execution, Capital punishment, Global Warming, Uranium and Depleted Uranium. The diversity and sheer number of articles that both James and BenB4 have spent time editing seem to be to much of a coincidence. Torturous Devastating Cudgel 15:15, 27 September 2007 (UTC)
Clerk note: this case was not filed properly, it didn't have the template invocation that it should have, I have added it. But I'm not a clerk so if I did it wrong, some clerk needs to fix it. :) ++Lar: t/c 01:29, 28 September 2007 (UTC)
Results:
Stale for Nrcprm2026 and LossIsNotMore... but see WP:DUCK... at this point IP evidence is no longer needed.
Confirmed that BenB4 == Clerkbird == Starcare
- Keep an eye on Kevster2 please, possible sleeper.
- And please fill the template out right, ok? :)
++Lar: t/c 01:56, 28 September 2007 (UTC)
- On the stale IP ... I screwed up a while back when listing these all as LossIsNotMore (an admitted sock of Nrcprm2026), when I should have listed all cases as Nrcprm2026 (the puppeteer). With all the time here, I dont understand why I fudge all these templates up. Amazing that James has been able to get away as BenB4 for so long. Torturous Devastating Cudgel 02:44, 28 September 2007 (UTC)
- No worries on the template, mostly I'm teasing all and sundry, especially those lazy clerks :). But just look at any other case to see how it should look, or read the doc for {{rfcu}}. As for the case name... since previous cases tied Clerkbird and Starcare to Nrcprm2026 etc, the chain is sound, these are very likely/certainly all the same guy. As for getting away with things like BenB4 did, we tend to let sockpuppets slide as long as they behave themselves and don't give away their identity by reverting to old edit patterns, old damaging behaviours. (and I'm personally fine with that...) The sleeper I refer to has no edits at all yet. ++Lar: t/c 13:18, 28 September 2007 (UTC)
- Thank you. I appreciate that, and have not decided whether I will continue on the path of WP:IAR. The fact remains that TDC has, for example, called a number of reports used to support his position on Talk:Depleted uranium peer-reviewed when they are not. And edited the article in the corresponding inaccurate way. WP:IAR is very clear. When the truth is being played so fast and loose, I do not see the downside of using socks to try to point out what other editors have neither the time nor inclination to. Now that it is down to the point of where I will probably be banned indefinitely, I must ask, what incentive is there to follow the arbitrators' rules when that would be essentially be a violation of WP:IAR? I don't see any. ←BenB4 14:45, 28 September 2007 (UTC)
- Much like the US Constitution, WP:IAR is not a suicide pact, and arbitration rulings are binding on all users of the English Wikipedia. We must have some enforceable order, or the whole project will implode. Crockspot 22:47, 28 September 2007 (UTC)
- Thank you. I appreciate that, and have not decided whether I will continue on the path of WP:IAR. The fact remains that TDC has, for example, called a number of reports used to support his position on Talk:Depleted uranium peer-reviewed when they are not. And edited the article in the corresponding inaccurate way. WP:IAR is very clear. When the truth is being played so fast and loose, I do not see the downside of using socks to try to point out what other editors have neither the time nor inclination to. Now that it is down to the point of where I will probably be banned indefinitely, I must ask, what incentive is there to follow the arbitrators' rules when that would be essentially be a violation of WP:IAR? I don't see any. ←BenB4 14:45, 28 September 2007 (UTC)
- No worries on the template, mostly I'm teasing all and sundry, especially those lazy clerks :). But just look at any other case to see how it should look, or read the doc for {{rfcu}}. As for the case name... since previous cases tied Clerkbird and Starcare to Nrcprm2026 etc, the chain is sound, these are very likely/certainly all the same guy. As for getting away with things like BenB4 did, we tend to let sockpuppets slide as long as they behave themselves and don't give away their identity by reverting to old edit patterns, old damaging behaviours. (and I'm personally fine with that...) The sleeper I refer to has no edits at all yet. ++Lar: t/c 13:18, 28 September 2007 (UTC)
- On the stale IP ... I screwed up a while back when listing these all as LossIsNotMore (an admitted sock of Nrcprm2026), when I should have listed all cases as Nrcprm2026 (the puppeteer). With all the time here, I dont understand why I fudge all these templates up. Amazing that James has been able to get away as BenB4 for so long. Torturous Devastating Cudgel 02:44, 28 September 2007 (UTC)
LossIsNotMore - 4
request links: main • edit • links • history • watch Filed: 23:59, 26 June 2007 (UTC) |
- Nrcprm2026 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- LossIsNotMore (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Clerkbird (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Starcare (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Code letter: B (RfAr probation)
Another Nrcprm2026 SPA for evading his edit ban. Follows the standard editing habits of his other SPA socks, create an account, make an edit to user page, user talk page and then to the article. Torturous Devastating Cudgel 17:56, 18 September 2007 (UTC)
Likely. Voice-of-All 03:03, 19 September 2007 (UTC)
LossIsNotMore - 3
request links: main • edit • links • history • watch Filed: 23:59, 26 June 2007 (UTC) |
- Nrcprm2026 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- LossIsNotMore (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Rtt71 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- GVWilson (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Code letter: B (RfAr probation)
Another Nrcprm2026 SPA for evading his edit ban. Torturous Devastating Cudgel 14:40, 26 June 2007 (UTC)
Likely. Nrcprm2026 = Rtt71 = LossIsNotMore. GVWilson's edits are stale Also, see LossIsNotMore's contribs along with [9]. Voice-of-All 19:37, 4 July 2007 (UTC
LossIsNotMore - 2
- LossIsNotMore (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Nrcprm2026 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
Editing as IP’s and one registered account on Depleted Uranium
- Physbang (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Black Omega (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- ActiniumBlue (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- -Alex- (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Code letter: B (RfAr probation)
James Salsman has once again used an IP to edit an article he is banned from editing. This is not the first time he has done this (prior Checkuser) and he might have even been able to get away with it had I found a peculiar edit by one of the anons. It seems that the anon was correcting James’ spelling mistake [10]. Physbang's first edit was also a correction on one of James' previous posts. [11] Torturous Devastating Cudgel 18:02, 15 November 2006 (UTC)
- All likely
Unrelated. I did find this violation [12], but it's old. Dmcdevit·t 03:42, 18 November 2006 (UTC)
Clerk note: The edit you flagged by 75.35.112.95 (talk · contribs) is a SWBell dsl address. So is 75.18.207.177 (talk · contribs) listed above. (75.18.207.177 (talk · contribs) is Qwest in Denver) If 75.35 was James S/LossIsNotMore, isn't it reasonable to conclude that the edits from 75.18 were likely his as well? Second, if the named accounts were not from SW Bell, is it possible to check them as open proxies, given Mackensen's findings in the non-transcluded section of the page below? Thatcher131 03:57, 18 November 2006 (UTC)
- You're right about those IPs, I only looked at the accounts. Of course, it's the same ISP with dynamic IPs (and no actual overlap in specific IP) so based on the IP evidence I can't really say it's more than
Possible. It's likely the behavior makes the violation obvious though. Dmcdevit·t 02:34, 19 November 2006 (UTC)
- You're right about those IPs, I only looked at the accounts. Of course, it's the same ISP with dynamic IPs (and no actual overlap in specific IP) so based on the IP evidence I can't really say it's more than
Accused note: Firstly, thank you for clearing me as much as you have so far. I logged in today for the first time in a week to see all this, all very familiar, except this time it's substantially better than it usually is. Also, about that so-called open proxy in Plano, Texas which Mackensen apparently said Peter Cheung was editing from is actually part of a DSL pool. Are there any known instances of open proxy servers existing in dynamic DHCP pools? Would someone please look back into that?! Thank you. LossIsNotMore 23:32, 18 November 2006 (UTC)
- Open proxies can definitely exist in DHCP pools. It just makes them harder to block. Zetawoof(ζ) 04:23, 19 November 2006 (UTC)
LossIsNotMore
- LossIsNotMore (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Peter Cheung (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
Admin Nandesuka and others have accused Peter Cheung, who was editing as 69.228.65.174, of being me, James Salsman, User:LossIsNotMore (formerly User:Nrcprm2026) concerning edits on Depleted uranium which I am prevented by ArbCom sanctions from editing. [13] [14] [15]. So, as I have been accused of violating ArbCom sanctions, and Peter Cheung has been accused of being a sockpuppet of mine in doing so, please CheckUser to clear us both from these accusations. LossIsNotMore 17:45, 14 August 2006 (UTC)
- I don’t know if James recruited this guy or if he is using a proxy server or what, but several facts have to be taken into consideration here:
- Depleted Uranium this is the first article Peter Cheung has edited
- Peter Cheung is attempting to add the same discredited information, verbatim, that James Salsman was
- Peter Cheung's second edit was an explanation on his talk page that he was not James Salsman and this could be verified by looking at his IP
- Peter Cheung found and utilized the survey tool a bit too quickly
- Neither of these editors have made contributions within the same time frame
- James Salsman cannot drop this debate.
- Torturous Devastating Cudgel 18:31, 14 August 2006 (UTC)
- There was an AP article on depleted uranium which came out over the weekend and appeared in hundreds of newspapers. There are a lot more new users than just Peter Cheung editing that article today and yesterday. LossIsNotMore 18:54, 14 August 2006 (UTC)
Well, this is interesting. "Peter Cheung" is editing from an open proxy, and based on IP evidence I'd say it's pretty likely that if you aren't him you certainly know who he is. No matter. The proxy is blocked indefinitely. Mackensen (talk) 22:07, 14 August 2006 (UTC)
- Also, why in the world is James Salslman editing article space related to uranium trioxide, when there is an Arbcom decision forbidding him from doing so? Nandesuka 04:47, 16 August 2006 (UTC)
Nrcprm2026
- Nrcprm2026 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- Gayrights (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
James Salsman has been editing Depelted Uranium articles in violation of 1.1 of his arbitration ruling, through the use of various IP addresses, and sockpuppets.
Please investigate. Torturous Devastating Cudgel 13:44, 8 June 2006 (UTC)
Clerk note: Could you provide some diffs of the suspected violations? --Srikeit (Talk | Email) 14:18, 8 June 2006 (UTC)
- JamesS was prohibited form editing articles haveing anything to do with depleted uranium following his arbcom ruling. Some examples are: [16], [17], and [18]. Torturous Devastating Cudgel 14:26, 8 June 2006 (UTC)
Inconclusive. Nrcprm2026 hasn't edited since May 1, too far back to check. The IPs listed are all from SBC/PacBell, while Gayrights is on a completely different ISP. Unless there is a record from the Arbitration Case or a previous checkuser of Nrcprm2026's IPs, there's no way to check this one. Essjay (Talk • Connect) 18:23, 8 June 2006 (UTC)
- Fortunately, Nrcprm2026 did make a few edits from an IP, an example. Torturous Devastating Cudgel 18:41, 8 June 2006 (UTC) and later signed them
- I think you misunderstood what I linked to. The above links are from edits Nrcprm2026 made several moths ago while not logged in, edits he later signed. I provided it as a point of reference. Torturous Devastating Cudgel 20:32, 8 June 2006 (UTC)
Note: In that case, there really is no need for checkuser; just report it on WP:AN/AE with a layout of the evidence. Essjay (Talk • Connect) 20:26, 8 June 2006 (UTC)
- I figured this was just a formality because the IP's were not exactly the same. Are, you saying then that although the IP's are not the same, that it is indeed the same user, Nrcprm2026? Please see above. Torturous Devastating Cudgel 20:29, 8 June 2006 (UTC)
The IPs are all in the same range, and it is dynamic (PPPOX pool). Therefore the IPs are likely one person. I don't have checkuser, so I can't tell you about the registered users. Prodego talk 20:59, 8 June 2006 (UTC)
- 71.141.107.41 is in SBC's PPPOX pool "Rback36.SNFCCA" (71.141.96.0 - 71.141.127.255 60) while those 71.132 addresses are all in PPPOX pool "-bras16.pltnca" (71.132.128.0 - 71.132.143.255). SBC is a huge ISP, so it shouldn't be difficult for admins with checkuser to see whether those two blocks share users. 69.228.65.171 00:46, 10 June 2006 (UTC)
Note: This is no longer a matter for checkuser. There is no way, based on the information available in the database, for me to confirm that the IPs are related to the user. The job of checkusers is to report on suspected sockpuppets based on the evidence available by checkuser; we are not default sockpuppet investigators, and do not handle cases that don't require checkuser. I've already reported that checkuser is inconclusive, if you want someone to look at edits by similar IPs that claimed to be the user and conclude that the IPs in question are him, then take it to the Administrators Noticeboard and ask someone to look into it. Essjay (Talk • Connect) 01:58, 10 June 2006 (UTC)
BSb recently added a comment to Wikipedia:Requests_for_arbitration#Depleted_uranium_and_related_articles in support of Nrcprm2026. Since this is the users *only* edit [19] she is obviously a sock of someone; the obvious possibility is Nrcprm2026. William M. Connolley 16:28, 5 March 2006 (UTC)
- AOL user. Nothing we can do, given the AOL megaproxy behaviour. Nrcprm2026 has never used AOL in the period I can check.Matthew Brown (Morven) (T:C) 09:23, 6 March 2006 (UTC)
- Hey ho. Thanks for checking! William M. Connolley 17:58, 6 March 2006 (UTC)
Subsequent requests related to this user should be made above, in a new section.