From Wikipedia, the free encyclopedia


LOCK177

LOCK177 ( talk + · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log· investigate · cuwiki)

20 January 2024

Suspected sockpuppets

Please check this user. Both user's editing behavior like same/duckling. Ariandi Lie Let's talk 17:25, 20 January 2024 (UTC) reply

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



30 January 2024

Suspected sockpuppets

All three of the registered accounts are already blocked - the first two based on behaviour, and the latter primarily for a username violation. The IP address (currently unblocked) has made identical edits to that of already-blocked AHTEURAME - compare e.g. [1] & [2], [3] & [4].

Regarding the accounts, I'm filing to request CheckUser to check for sleeper accounts (as sleepers were found in an archived case), in addition to the fact that the evidence against Sockuptery may not be sufficient to tie it to LOCK177 on its own - it seems suspicious that an account with that username edited an article ( BeIN Sports) frequently targeted by LOCK177 socks over the past few weeks (after previously remaining dormant since June 2022); however, I'm not sure that this is sufficient in and of itself for a finding of sockpuppetry from this master. (To be clear, I understand that no CU comment can be made regarding the IP).

If there are any queries, or if I've filed anything poorly, then please let me know. All the best, ‍—‍ a smart kitten[ meow 23:20, 30 January 2024 (UTC) reply

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

  • AHTEURAME and SAKAMATABAKU are  Confirmed to each other and  Highly likely to the master,  No sleepers immediately visible. Sockuptery is using proxies which is not something the master and socks have done. As they're already indeffed, I'm not going to spend too much time thinking about what sock drawer they might belong to. no No comment with respect to IP address(es) but the IP linked in the SPI has not edited in several days so a block for any reason would not be worthwhile at this point. Spicy ( talk) 14:22, 1 February 2024 (UTC) reply

21 February 2024

Suspected sockpuppets

Similar behaviour to other socks & to the master - addition of unsourced content, with a large article overlap to the master & confirmed socks: overlap with LOCK177, overlap with ABAHKORUPSI, overlap with LUI116X, overlap with AHTEURAME, overlap with SAKAMATABAKU. In addition, the username is in a similar format to other accounts operated by this user.

Requesting CheckUser for sleepers. I'd also ask that semiprotection is considered for the frequently targeted articles. All the best, ‍—‍ a smart kitten[ meow 15:34, 21 February 2024 (UTC) reply

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

Incredibly  Likely, but no sleepers turn up. Courcelles ( talk) 16:47, 21 February 2024 (UTC) reply

Spoke too soon, I need to add REYX24 ( talk + · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log· investigate · cuwiki). Courcelles ( talk) 16:49, 21 February 2024 (UTC) reply
Blocked, tagged, reverted, semi-protected a few. Case closed. Courcelles ( talk) 16:51, 21 February 2024 (UTC) reply

22 February 2024

Suspected sockpuppets

Similar all caps username, only three edits so far diff 1, diff 2 and diff 3 were to restore the version by another sockpuppet of them, KIRACHI000. User3749 ( talk) 09:20, 22 February 2024 (UTC) reply

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


04 March 2024

Suspected sockpuppets

Similar all-caps username, large article overlap. Has restored edits made by previous sockpuppets, see e.g Special:Diff/1209526167/1211764206, Special:Diff/1209526653/1211765331 ‍—‍ a smart kitten[ meow 10:42, 4 March 2024 (UTC) reply

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


21 April 2024

Suspected sockpuppets

CheckUser  Confirmed, filing for the record. Callanecc ( talkcontribslogs) 09:49, 21 April 2024 (UTC) reply

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


From Wikipedia, the free encyclopedia


LOCK177

LOCK177 ( talk + · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log· investigate · cuwiki)

20 January 2024

Suspected sockpuppets

Please check this user. Both user's editing behavior like same/duckling. Ariandi Lie Let's talk 17:25, 20 January 2024 (UTC) reply

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



30 January 2024

Suspected sockpuppets

All three of the registered accounts are already blocked - the first two based on behaviour, and the latter primarily for a username violation. The IP address (currently unblocked) has made identical edits to that of already-blocked AHTEURAME - compare e.g. [1] & [2], [3] & [4].

Regarding the accounts, I'm filing to request CheckUser to check for sleeper accounts (as sleepers were found in an archived case), in addition to the fact that the evidence against Sockuptery may not be sufficient to tie it to LOCK177 on its own - it seems suspicious that an account with that username edited an article ( BeIN Sports) frequently targeted by LOCK177 socks over the past few weeks (after previously remaining dormant since June 2022); however, I'm not sure that this is sufficient in and of itself for a finding of sockpuppetry from this master. (To be clear, I understand that no CU comment can be made regarding the IP).

If there are any queries, or if I've filed anything poorly, then please let me know. All the best, ‍—‍ a smart kitten[ meow 23:20, 30 January 2024 (UTC) reply

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

  • AHTEURAME and SAKAMATABAKU are  Confirmed to each other and  Highly likely to the master,  No sleepers immediately visible. Sockuptery is using proxies which is not something the master and socks have done. As they're already indeffed, I'm not going to spend too much time thinking about what sock drawer they might belong to. no No comment with respect to IP address(es) but the IP linked in the SPI has not edited in several days so a block for any reason would not be worthwhile at this point. Spicy ( talk) 14:22, 1 February 2024 (UTC) reply

21 February 2024

Suspected sockpuppets

Similar behaviour to other socks & to the master - addition of unsourced content, with a large article overlap to the master & confirmed socks: overlap with LOCK177, overlap with ABAHKORUPSI, overlap with LUI116X, overlap with AHTEURAME, overlap with SAKAMATABAKU. In addition, the username is in a similar format to other accounts operated by this user.

Requesting CheckUser for sleepers. I'd also ask that semiprotection is considered for the frequently targeted articles. All the best, ‍—‍ a smart kitten[ meow 15:34, 21 February 2024 (UTC) reply

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

Incredibly  Likely, but no sleepers turn up. Courcelles ( talk) 16:47, 21 February 2024 (UTC) reply

Spoke too soon, I need to add REYX24 ( talk + · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log· investigate · cuwiki). Courcelles ( talk) 16:49, 21 February 2024 (UTC) reply
Blocked, tagged, reverted, semi-protected a few. Case closed. Courcelles ( talk) 16:51, 21 February 2024 (UTC) reply

22 February 2024

Suspected sockpuppets

Similar all caps username, only three edits so far diff 1, diff 2 and diff 3 were to restore the version by another sockpuppet of them, KIRACHI000. User3749 ( talk) 09:20, 22 February 2024 (UTC) reply

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


04 March 2024

Suspected sockpuppets

Similar all-caps username, large article overlap. Has restored edits made by previous sockpuppets, see e.g Special:Diff/1209526167/1211764206, Special:Diff/1209526653/1211765331 ‍—‍ a smart kitten[ meow 10:42, 4 March 2024 (UTC) reply

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


21 April 2024

Suspected sockpuppets

CheckUser  Confirmed, filing for the record. Callanecc ( talkcontribslogs) 09:49, 21 April 2024 (UTC) reply

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



Videos

Youtube | Vimeo | Bing

Websites

Google | Yahoo | Bing

Encyclopedia

Google | Yahoo | Bing

Facebook