Wikipedia:Requests for checkuser/Case/Amazonfire

Source: Wikipedia, the free encyclopedia.

Amazonfire

  • Code letter: C, E, F
  • Supporting evidence:

These articles are constant subjects of tendentious editing instead of engaging in discussion. I suspect some user(s) is(are) using sockpuppetry to avoid 3RR violation like the below examples. The ip addresses are all from the article. Note that user Amazonfire created his account about 10 months ago with just one log, and then suddenly reappeared here as just begun blindly reverting. This report holds the very recent cases and related in partial to Wikipedia:Requests for checkuser/Case/KoreanShoriSenyou which is on hold. I wish this endless disruption would be stopped in near future.

  • 1st Possible 3RR violation with sock
1st revert 06:56, 15 January 2008 by Amazonfire
2nd revert 10:20, 15 January 2008 by 219.66.44.142
3rd revert 16:23, 15 January 2008 Amazonfire
4th revert 17:25, 15 January 2008 by Amazonfire
08:59, 17 January 2008 by 219.66.47.183
  • 2nd Possible 3RR violation with sock
2007-12-05T09:02:09 by 61.209.168.24 (odn.ad.jp)
2007-12-05T11:29:01 by Blue011011
2007-12-05T16:37:32 by 211.3.113.201 (odn.ad.jp)
s2007-12-05T22:03:08 by Blue011011
  • Possible 3rr violation with sock
pre revert 16:29, 7 January 2008 by 219.66.42.176
1st revert 20:29, 7 January 2008 by Amazonfire
2nd revert 16:59, 8 January 2008 by 219.66.41.150
3rd revert 17:16, 8 January 2008 by 219.66.41.150
4th revert 17:24, 8 January 2008 by 219.66.41.150
5th revert 17:42, 8 January 2008 by 219.66.41.150
6th revert 08:59, 9 January 2008 by 43.244.133.167
  • Possible 3rr violation with sock
1st revert 02:34, 14 January 2008 by Jusenkyoguide
2nd revert 18:37, 16 January 2008 by Jusenkyoguide
3rd revert 19:54, 16 January 2008 by Kusunose
4th revert 21:01, 16 January 2008 by Jusenkyoguide
  • Possible 3rr violation with sock
1st revert 20:36, 16 January 2008 by Jusenkyoguide
2nd revert 21:03, 16 January 2008 by Jusenkyoguide
3rd revert 21:11, 16 January 2008 by Jusenkyoguide
4th revert 21:27, 16 January 2008 by Kusunose
  • Possible 3rr violation with sock

note. 211.3.114.239 is a sock of 219.66.40.104 and 219.66.45.131 who vandalised and evaded their block sanction.

1st revet 08:52, 19 January 2008 by 211.3.114.239
2nd revet 12:57, 19 January 2008 by 211.3.114.239
3rd revet 00:45, 20 January 2008 by Amazonfie
4th revet 01:13, 20 January 2008 by Amazonfie
5th revet 01:42, 20 January 2008 by Amazonfie
6th revet 10:02, 20 January 2008 by Orchis29
1st revert 09:43, 22 January 2008 by 124.87.134.96
2nd revert 10:44, 22 January 2008 by Amazonfire
3rd revert 10:57, 22 January 2008 by Amazonfire
4th revert 11:15, 22 January 2008 by Amazonfire
5th revert 11:24, 22 January 2008 by Amazonfire

--

talk) 17:11, 18 January 2008 (UTC)[reply
]

    • Endroit and John Smith's are totally Red X Unrelated. Thatcher 03:26, 24 January 2008 (UTC)[reply]
    • Question: The differs I provide as evidence mainly focus on Amazonefire and the odn anons of which are banned for 3RR violations and block evasions. And why don't you say about whether the others are unrelated to Amazonfire or to each other?--
      talk) 03:35, 24 January 2008 (UTC)[reply
      ]
All I can really tell is that they are all in Japan and they all use the same giant ISP, but that's like looking at a bunch of suspects in the US who all use AOL. There is something about Orchis29 and Azukimonaka that lets me say "possible"; but for all the rest the technical evidence is not helpful. As someone famously said, Checkuser is not magic wiki pixie dust. The style of contributions is your best evidence here. Thatcher 03:41, 24 January 2008 (UTC)[reply]
I know that Japan has more than 40 ip network after collecting the disruptive odn user's ips. Same misspellings and passages on edit summaries are not enough to prove anything? And are you saying that the listed users are all using
talk) 03:45, 24 January 2008 (UTC)[reply
]
I saw some checkuser said several times that they can clearly see what computer and browser types and even index numbers of computers due to distinctive features of editors here. And are they all using one computer and one browser? --
talk) 04:01, 24 January 2008 (UTC)[reply
]
I'm not going to say anything more specific about the technical evidence. I also have not looked at contributions (similar misspellings, edit summaries, or the like). Checkuser is a technical means for finding sockpuppets that is independent of analysis of contributions. Sometimes checkuser can support a behavioral comparison, sometimes it indicates a connection when people do not expect it, and sometimes it is simply not helpful one way or the other. It sounds like you need to find an administrator to review your non-technical (behavioral) evidence and take action if they agree with you. Thatcher 08:11, 24 January 2008 (UTC)[reply]
I'm not a seeking an administrator to agree with all of my opinion on some of the listed disruptive editors. I'm tired of getting their same (especially ip users) mockery and personal attack and blind reverting or addting without verifiable proof. (I've kept hearing 'Korean theif who steels Japanese and Chinese culture' or 'uneducated Korean' something like that) I believed checkuser system is a fastest way to confirm their same behavioral pattern by checking ip and hosts. --
talk) 10:06, 24 January 2008 (UTC)[reply
]



For the record of a related case, another extensive check user of

and been checked.

A check user case including

User:Appletrees has been also submitted to Wikipedia:Requests for checkuser/Case/AirFrance358.--Jjok (talk) 18:55, 26 January 2008 (UTC)[reply
]

 Clerk note: Per request of checkuser, please see also this case too. -JodyB talk 16:15, 1 February 2008 (UTC)[reply]