Revision as of 00:50, 16 September 2012 editTimotheus Canens (talk | contribs)Edit filter managers, Administrators38,438 edits Marking case as closed← Previous edit | Revision as of 13:54, 16 September 2012 edit undoEEng (talk | contribs)Edit filter helpers, Autopatrolled, Extended confirmed users, New page reviewers, Pending changes reviewers, Template editors97,995 edits →Comments by other users: correction for the record re prior sockpuppetry casesNext edit → | ||
Line 26: | Line 26: | ||
It's been clear for at least 6 months that Ryoung122 switches to this IP when editing in his banned area, but sometimes forgets to log in when posting outside the banned area. | It's been clear for at least 6 months that Ryoung122 switches to this IP when editing in his banned area, but sometimes forgets to log in when posting outside the banned area. | ||
*In posts of any length Ryoung122's style of writing as well as argumentation is unmistakable. A striking example (for those familiar with his fingerprints) is here . | *In posts of any length Ryoung122's style of writing as well as argumentation is unmistakable. A striking example (for those familiar with his fingerprints) is here . | ||
*Other the low-hanging fruit here , including a particularly obvious example in which, on a talk page with no posts at all for 4 years, the IP and Ryoung122 both suddenly arrive to post |
*Other the low-hanging fruit here , including a particularly obvious example in which, on a talk page with no posts at all for 4 years, the IP and Ryoung122 both suddenly arrive to post within 3 minutes of each other, on the same narrow aspect of the article subject. | ||
* Ryoung122 has a substantial history of chronic sockpuppetry, and has violated his topic ban (under his own username) numerous times, if intermittently. | * Ryoung122 <del>has a substantial history of chronic sockpuppetry, and</del><small>''''</small> has violated his topic ban (under his own username) numerous times, if intermittently. | ||
** A few examples: | ** A few examples: | ||
** Here he excuses one of his violations with, "The ban was for an 'indefinite' time period, not forever" -- and in the same post continues the ban-violating discussion! | ** Here he excuses one of his violations with, "The ban was for an 'indefinite' time period, not forever" -- and in the same post continues the ban-violating discussion! | ||
I'm not sure a checkuser is needed -- the quacking is deafening. ] (]) 23:41, 15 September 2012 (UTC) | I'm not sure a checkuser is needed -- the quacking is deafening. ] (]) 23:41, 15 September 2012 (UTC) | ||
::::<small>On reviewing the record my words above, ''substantial history of chronic sockpuppetry'', turn out to be an exaggeration -- previous sockpuppetry cases have been somewhat ambiguous. Just wanted to correct that for the record. ] (]) 13:54, 16 September 2012 (UTC)</small> | |||
======<span style="font-size:150%">Clerk, CheckUser, and/or patrolling admin comments</span>====== | ======<span style="font-size:150%">Clerk, CheckUser, and/or patrolling admin comments</span>====== |
Revision as of 13:54, 16 September 2012
Ryoung122
Ryoung122 (talk · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)
Populated account categories: suspected
For archived investigations, see Misplaced Pages:Sockpuppet investigations/Ryoung122/Archive.
Prior SSP or RFCU cases may exist for this user:
15 September 2012
– This SPI case is closed and will be archived shortly by an SPI clerk or checkuser.
- Suspected sockpuppets
- Ryoung122 (talk · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)
- 69.15.219.71 (talk · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
- User compare report Auto-generated every hour.
- User:Ryoung122 was topic banned from longevity-related articles a year and a half ago
- He was warned for breaking his topic ban before, and his response suggests that he felt his ban should no longer be in force
- 92% of the ip's last 50 edits have been to longevity-related articles, as are many, many before them
- The IP's edit summaries and general tone suggest the same sort of tendentious editing that got User:Ryoung122 to arbitration committee in the first place: this is the best example but, unless you've dealt with the user over an extended period of time, it's difficult to put into tone into context
- ip is based in the state of Georgia, as is User:Ryoung122 per his user page as well as his public profile on the internet
Thus I am requesting CheckUser because I believe that Ryoung122 is using this IP address to evade his topic ban. Canadian Paul 19:12, 15 September 2012 (UTC)
Comments by other users
Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
It's been clear for at least 6 months that Ryoung122 switches to this IP when editing in his banned area, but sometimes forgets to log in when posting outside the banned area.
- In posts of any length Ryoung122's style of writing as well as argumentation is unmistakable. A striking example (for those familiar with his fingerprints) is here .
- Other the low-hanging fruit here , including a particularly obvious example in which, on a talk page with no posts at all for 4 years, the IP and Ryoung122 both suddenly arrive to post within 3 minutes of each other, on the same narrow aspect of the article subject.
- Ryoung122
has a substantial history of chronic sockpuppetry, andhas violated his topic ban (under his own username) numerous times, if intermittently.
I'm not sure a checkuser is needed -- the quacking is deafening. EEng (talk) 23:41, 15 September 2012 (UTC)
- On reviewing the record my words above, substantial history of chronic sockpuppetry, turn out to be an exaggeration -- previous sockpuppetry cases have been somewhat ambiguous. Just wanted to correct that for the record. EEng (talk) 13:54, 16 September 2012 (UTC)
Clerk, CheckUser, and/or patrolling admin comments
Clerk endorsed - with any results to be sent to arbcom for action. T. Canens (talk) 23:46, 15 September 2012 (UTC)- On second thought, Clerk declined as obvious (see, e.g., ). T. Canens (talk) 00:48, 16 September 2012 (UTC)
- Master indeffed, IP blocked for a year since it seems fairly static. T. Canens (talk) 00:50, 16 September 2012 (UTC)
Categories: