Wikipedia talk:Sockpuppet investigations/Archive 4

Archive 1

Archive 2

Archive 3

Archive 4

Archive 5

Archive 6

→

Archive 10

Return of the dreadful user Part Dos

Hi there. 66.61.87.219 is apparently back. They've started up again with the same edits and summaries "sonit". The IP was previosuly blocked as a sock of Sleepydre (see case file). Given this user's past history is this something that I need to refile at SPI or do I have to watch their contribs and take it to ANI? Thanks for the help, §hep^Talk 22:14, 6 March 2009 (UTC)

Nevermind, got him blocked. §hep^Talk 18:55, 7 March 2009 (UTC)

IP sock puppets

I'm not sure if I'm in the right place to report a sock puppet, if I'm not please move this to the proper place.

• 4.227.109.176 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) - IP vandalism, possible WP:sock puppet of 4.227.106.12, vandalism of BabyFirstTV. Both IP's are changing the year the network was founded from 2003 (clearly stated on the channel's official site and referenced with an inline citation) to 1982 (obviously untrue, no reference cited) without explanation. Please block both IP's. TomCat4680 (talk) 11:29, 10 March 2009 (UTC)

Hi there. Please see the instructions at the top of WP:SPI, and file a case page. This is so the case can be archived for record keeping. Thanks, PeterSymonds (talk) 15:38, 10 March 2009 (UTC)

Instructions in case a case already was investigated and new socks appear

I'm not knowledgeable in SPI matters and so I was quite confused when I came across User talk:Gonzonoir#Help request. I would like to ask someone here to answer this user's question if possible. Generally speaking, I think it would be a great idea if someone were to add detailed instructions to WP:SPI as to what to do in case someone suspects an user to use new socks after the previous case was closed. Regards SoWhy 10:47, 13 March 2009 (UTC)

There are two possible scenarios;

1. Additional socks when a case is open (or indeed when it is "pending close" - Just add the extra socks to the case, and leave a note in the case that you have done so.
2. Additional socks after a case is archived - File a new case using the buttons.

Anybody care to pretty that up as nice instructions? Mayalld (talk) 11:41, 13 March 2009 (UTC)

Just to add that we DON'T use case numbers. All cases are filed under the name of the potential master account, and the bot archives as required. Mayalld (talk) 11:42, 13 March 2009 (UTC)

It should work exactly the same as creating a fresh page, the only difference is that the bot removes the case and sends it to its own article. So in other words, the same process applies, whether a fresh case, or an old one. I'll look more into it, and hopefully post soon. Synergy 19:56, 13 March 2009 (UTC)

Help needed to file a Sockpuppetry Report

Can some one help me to file a report regarind the banned User:Kuntan ?. Here are the suspected sockpuppets of User: Kuntan, Anonymous User with IP address 59.91.253.113, 59.91.253.110, 59.91.254.63, 59.91.254.38, 59.91.253.112, 59.91.253.70, 59.91.253.225, 59.91.254.94, 59.91.254.8. He was silent for some months now and again sprang up suddenly. One another editor emailed me and told that he is one Mr. P. Krishnakumar from a city called Calicut in Kerala. This man is involved in serious mutilation of a particular wikipage of SUCI. His personal vengance to the party is evident from him edits for the last 2 years. He is also using abusive language on this editor and others. One of this puppet IP is already banned. Please help.--Radhakrishnansk (talk) 15:27, 14 March 2009 (UTC)

A new puppet User: 59.91.253.27. He is again abusing other editors--Radhakrishnansk (talk) 16:45, 14 March 2009 (UTC)

Go to Wikipedia:SPI#Instructions for instructions on creating a new case. Understand that providing diffs of the behavior that makes you suspect socks will result in faster case processing. —— nixeagle^{email me} 16:49, 14 March 2009 (UTC)

Stale cases

I just saw stale cases get added... could someone explain to me how that category works? Plus could someone explain to me how attending to "stale" cases is any more important then attending to any one part of the backlog? —— nixeagle^{email me} 02:53, 12 March 2009 (UTC)

At present, it doesn't seem to work! call it an experiment that didn't work out as I hoped. The idea was that it would flag up any case that hadn't seen any action in 24 hours. Ah well, back to the drawing board! Mayalld (talk) 15:07, 12 March 2009 (UTC)

If you guys want this, I *can* have the bot identify cases without edits after X days and keep an updated list. That list would likely be more useful then what is there anyway. (Also note that old cases and cases without an edit to them in a while are *always* at the bottom of the bot's list on WP:SPI. Whenever an edit is done to the case, the case gets moved to the top of the list. —— nixeagle^{email me} 15:48, 12 March 2009 (UTC)

As I see it, there are two categories of "Stale" cases;

• Cases that have been open for some extended (2 weeks?) period of time, without resolution.
• Cases that haven't been edited in some shorter (3 days?) period of time, and which don't seem to be moving forward.

In terms of passing admins, cases that have been open for weeks, but which are still active don't need somebody to take them on. Cases that have stagnated do.

The stale cases thing works by comparing the current time to the last saved time, and categorises as stale if more than 3 days have passed. Unfortunately, a null edit is needed to make it work (must be truly null otherwise it updates the time stamp). I null edited everything this morning, and we have over 20 cases where nobody has commented in the last 3 days. If this categorisation is useful, it might be useful to have the bot null edit cases daily to categorise them. For now, I'll use AWB from time to time to do the null edits. Mayalld (talk) 12:00, 13 March 2009 (UTC)

Interesting really to be honest its the cases that have been open forever that matter the most, we really ought to attempt to close those. (All of the really old ones just need someone to take 30 minutes to close them). Also so you know, another way to tell which cases have not been modified in a while is just to look at the order of the bot's list in the open cases section. Cases at the top are new/modified recently and the ones at the bottom are old/not modified in a while. —— nixeagle^{email me} 15:45, 13 March 2009 (UTC)]

Also IMHO our problem right now is not people knowing which cases are old or anything like that. Our problem is simply being backlogged and not having very many admins interested in reviewing caess. That means work on the process itself should be focusing towards making the directions clear and advertising that we need help in places where admins might be hanging around. —— nixeagle^{email me} 15:49, 13 March 2009 (UTC)

I agree. Cases that have been around a long time are equally problematic. We can see those (as you say) from the order of the queue. However, cases don't get shifted around in the queue as they are modified. If I put a note on the oldest case, it won't jump to the top. Also, it appears that those admins who are patrolling seldom look at the CU declined queue. Should we merge the CU not required and CU declined queues? Mayalld (talk) 16:21, 13 March 2009 (UTC)

Mayalid they do get shifted around the queue if they are modified (I think, if not I can make a small change to the bot to have it shift them), go try it :) Don't forget to purge too. —— nixeagle^{email me} 16:51, 14 March 2009 (UTC)

Just remember that some cases might be there, awaiting arb com decisions (and this will obviously take quite a bit of time, usually). There should be some type of marker drawn up, to show why its still sitting there. Another reason, is when the a CU states that it will in fact, take some time to process. Synergy 19:52, 13 March 2009 (UTC)