Wikipedia:Requests for checkuser/Case/SUVx

''The following discussion is preserved as an archive of a Request for checkuser. Please do not modify it .''

SUVx



 * Code letter: G


 * Supporting evidence: There is trouble at, a battle over the lead, where there is an appearance that a swarm of single purpose accounts are all editing towards the same goal. The following diffs indicate a strong possibility of WP:SOCK or WP:MEAT, given that all these editors suddenly show up at the same place, at the same time, arguing for the same thing: sympathetic treatment of a fringe view.
 * SUVx:
 * FooWarrior
 * WakeUpPoindexter
 * This matter was originally reported at WP:ANI, which is how I became aware of it. Jehochman Talk 00:35, 16 June 2008 (UTC)


 * They all appear to be ❌, though it's difficult to know as they have all used open proxies at some time. is highly  to be, though -  A l is o n  ❤ 01:01, 16 June 2008 (UTC)
 * The pre-test probability that these are Davkal-related was pretty high, and the use of open proxies is part of his MO. They look like a fairly clear-cut swarm of sock/meatpuppets created to influence a specific debate; the contribs are not those of truly new users; and given that and the checkuser evidence (use of proxies, technical ties between at least one account and Davkal) I've blocked them. MastCell Talk 16:17, 16 June 2008 (UTC)


 * I found one more: . Alison, please check it. Jehochman Talk 16:23, 16 June 2008 (UTC)
 * (edit conflict) Great minds think alike - just spotted that one and blocked it as matching the pattern of the others to a T. MastCell Talk 16:24, 16 June 2008 (UTC)
 * ✅ - A l is o n  ❤ 21:19, 16 June 2008 (UTC)


 * Two more for Alison. Jehochman Talk 23:56, 16 June 2008 (UTC)


 * ✅ - A l is o n  ❤ 00:23, 17 June 2008 (UTC)


 * One more. Jehochman Talk 14:52, 17 June 2008 (UTC)
 * - A l is o n  ❤ 20:56, 17 June 2008 (UTC)
 * - A l is o n  ❤ 20:56, 17 June 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.''