Wikipedia:Sockpuppet investigations/Reid62/Archive

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

The user has logged out to engage in edit-warring, and to circumvent the three-revert rule at the Halimah Yacob article. 118.189.63.127 (talk) 00:30, 19 July 2017 (UTC)

Evidence: the user has performed the following reverts across the various IPs to their benefit, circumventing the three-revert rule policy:            118.189.63.127 (talk) 18:50, 19 July 2017 (UTC)


 * Please move this page to the WP space. Thanks. Regards, 118.189.63.127 (talk) 00:30, 19 July 2017 (UTC)

Requesting for CheckUser. While User:Reid62 is currently blocked, the IP address 202.156.181.76 is still engaging in disruptive editing and may be evading a block. --202.172.56.4 (talk) 13:35, 28 July 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''


 * I'm just going to make a statement rather than move this myself: CheckUser cannot make a connection with IPs directly. Most cases that are allowed to be checked by someone with those tools involve more than one registered user. This case appears to me more like a behavioural case than an actual sockpuppetry case, and if I was a CheckUser/clerk (which I am not), I would decline a request.
 * For these reasons, I cannot request CheckUser. Despite this, I see this as more of a behavioural case rather than a sock case. The IPs aren't exactly in the same location. WHOIS gives me different locations across a single city-state, though it doesn't necessarily mean it's the same user making the actions. If they were actual users instead, it would be a case of meat-puppetry, but since they're IPs, this isn't the case. jd22292 (Jalen D. Folf) (talk) 04:21, 19 July 2017 (UTC)
 * Wikipedia's sock puppetry policy seems to consider "Circumventing policies or sanctions" and "Editing logged out to mislead" as a form of sock puppetry, and these are what I'm reporting the user for. The user performed 10 reverts over a 24 hour period (12 over 25 hours), has been warned multiple times for edit warring across his User and IP addresses, and has refused to engage with the other editors on the article's Talk page. 118.189.63.127 (talk) 18:40, 19 July 2017 (UTC)
 * I've checked the article. It seems a consensus was reached on the Talk page and the edit war has ceased for now. At this point, a CheckUser would just mark this report as . jd22292 (Jalen D. Folf) (talk) 02:39, 21 July 2017 (UTC)
 * While User:Reid62 seems to be blocked, 202.156.181.76 is once again active on the Halimah Yacob page. --202.172.56.4 (talk) 18:08, 26 July 2017 (UTC)
 * I have sent the page over to WP:RPP for review. Reid62 has been blocked by administrator in the meantime. jd22292 (Jalen D. Folf) (talk) 18:25, 26 July 2017 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * Moved from talk page per edit-request, without comment on the validity of the report itself.  Salvidrim!   ·  &#9993;  03:52, 19 July 2017 (UTC)
 * I've blocked for WP:NLT . Amortias (T)(C) 14:33, 29 July 2017 (UTC)
 * I imposed semiprotection at Halimah Yacob per an edit warring complaint on 26 July. There was a war between a 202.172.* IP and a 202.156.* IP that went up to seven reverts each. It would not come as a complete surprise if the 202.172.* (as well as User:Rachel Lucy) is being operated by User:Reid62, and that the 202.156.* IP by User:YewGotUp. Reid62 is currently blocked indefinitely for legal threats by User:Amortias per their comment above. I am hoping that one or more of these editors will wake up and smell the policies. If not, another option is to put Halimah Yacob under extended confirmed protection. The same IPs could be branching out to revert war at other Singapore-related articles which might suggest the need for some rangeblocks in the future. EdJohnston (talk) 15:14, 29 July 2017 (UTC)
 * Yes, the 202.156.* 202.172.* IP edits are mine. I understand and acknowledge the 3RR policy and will try to avoid doing so in the future. I have no issue with the page being put under extended semi-protection. --YewGotUp (talk) 15:20, 29 July 2017 (UTC)
 * Edited some part of my earlier message to clarify that 202.172.* is mine, not 202.156.*. I was confused by EdJohnston's comment, which alleged that 202.172.* was being operated by User:Rachel Lucy, and that the other IP by myself. Note that the final comment under the Submitter's comments were signed by 202.172.*. --YewGotUp (talk) 22:37, 2 August 2017 (UTC)


 * Account blocked, IP's are stale. Closing. Sro23 (talk) 18:30, 2 August 2017 (UTC)

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

The user is once again edit warring while logged out, and has been blocked for 48 hours. Note that the IP's two alleged users Reid62 and Rachel Lucy have been blocked indefinitely, and it is likely that the IP's action would constitute block evasion. I would like to keep this investigation open in the off-chance any new socks are created. YewGotUp (talk) 23:16, 2 August 2017 (UTC)
 * The IP in question has recently been active and disruptively editing the Yusof Ishak article:     (the edit message for this last one goes against WP:CIVIL) --YewGotUp (talk) 14:29, 7 August 2017 (UTC)
 * A recently created user User:Richard Mile has just edited the Halimah Yacob article with the same points as User:Reid62 and User:Rachel Lucy. --YewGotUp (talk) 17:58, 7 August 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Clerk, CheckUser, and/or patrolling admin comments

 * . There's a lot of undesirable activity surrounding Singapore political articles, but I'll let a fellow CU handle this in light of Singapore's current political climate. - Mailer Diablo 19:25, 7 August 2017 (UTC)
 * - Katietalk 21:17, 7 August 2017 (UTC)
 * ✅ plus . I don't see any other obvious sleepers. . Additional rangeblocks are difficult but not impossible, so if it gets out of hand let me know. Blocked, tagged, closing. Katietalk 21:27, 7 August 2017 (UTC)