Wikipedia:Requests for checkuser/Case/Versace11
(Redirected from Wikipedia:Requests for checkuser/Case/24.205.234.250)
The following discussion is preserved as an archive of a Request for checkuser. Please do not modify it.
request links: main • edit • links • history • watch Filed: 20:43, 21 June 2008 (UTC) |
- Versace11 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki) (Diff: 12)
- 12) (Diff:
- 12) (Diff:
- 12) (Diff:
- 12) (Diff:
- 12) (Diff:
- 12) (Diff:
- Code letter: C
- Two had blocks for disruptive editing, one for vandalism, a third for personal attacks, one had no block, and another two are now blocked as proxy.
- Supporting evidence:
- All POV pushing and/or edit warring on Superpower, Great power, Potential superpower and United States.
- All pushing a misleading source (see here) added diffs at first section for evidence.
- Network achieved getting Superpower and Great power on full protection.
- Superpower • history • Look for: User:24.180.3.127 • User:Versace11 • User:24.180.3.127 • User:24.176.166.135
- Great power• history • Look for: User:24.205.234.250 (3RR ended with 24h block)
- There is another 3RR report against User:24.205.234.250 for Talk:United States (history)
- User:69.239.171.174 and User:66.17.49.165 were used to continue edit war when User:24.205.234.250 had block
- Also see suspected sock puppets for another full report. And additional ANI.
Additional information needed I'm not sure of what you're looking for here, you obviously have the contributors IPs already? :) -- lucasbfr talk 21:00, 22 June 2008 (UTC)
- I think he wants to get someone to ban Versace11 for repeated disruption. Perhaps that can be done without running the checkuser test; the evidence seems fairly strong already. Yechiel (Shalom) 01:20, 23 June 2008 (UTC)
- It would help if the connection between the IPs and the account is confirmed. Species8473 (talk) 01:44, 23 June 2008 (UTC)
- This editor, 24.205.234.250, seems to be bad news. He has just received a one-week block at 3RR, but he seems endlessly inventive in terms of mischief. The recent 3RR case is here. The 3RR case also contains a pointer to an ANI discussion. Two editors who were reverting with him got blocked indef as open proxies by ST47 though I understand that WP:OP has not yet confirmed those findings. A very detailed SSP report, which includes more accounts than are listed here, exists at [1]. However any additional info that checkuser might find would help to solve the puzzle. EdJohnston (talk) 20:16, 23 June 2008 (UTC)
- I think he wants to get someone to ban Versace11 for repeated disruption. Perhaps that can be done without running the checkuser test; the evidence seems fairly strong already. Yechiel (Shalom) 01:20, 23 June 2008 (UTC)
Confirmed that Versace11 is editing while logged out;
Confirmed that he is using the 24.x.x.x numbers. The other numbers can not be ruled in or out but seem
Possible based on geography. Thatcher 18:06, 25 June 2008 (UTC)
request links: main • edit • links • history • watch Filed: 04:51, 25 May 2008 (UTC) |
- Versace11 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- G:
- Supporting evidence: Similar disruptive edits to superpower and potential superpowers articles. First made edits without signing-in to these articles and when these pages were semi-protected, started using the concerned username. --AI009 (talk) 04:51, 25 May 2008 (UTC)
Clerk note: The IP only edited on May 23 and Versace11 is currently blocked for 31 hours for disruption on that article. -- lucasbfr talk 11:46, 27 May 2008 (UTC)
Declined as obvious. You can update and relist the request if, for example, you request a block for a 3RR violation and he protests innocence. Thatcher 04:05, 30 May 2008 (UTC)
The above discussion is preserved as an archive of the Request for checkuser. Please do not modify it.
Subsequent requests related to this user should be made above, in a new section.
Subsequent requests related to this user should be made above, in a new section.