From Wikipedia, the free encyclopedia


Janagewen

Janagewen ( talk + · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log· investigate · cuwiki)
29 December 2014
Suspected sockpuppets

Another user, Password Saeba Ryo, was blocked after confessing to being a sock of Janagewen. This account popped up and immediately nominated User:Password Saeba Ryo for deletion; their only edits that are not related to that MfD are to Template talk:.NET Framework where they blanked a discussion involving Password Saeba Ryo and Janagewen, and to Talk:Physical Address Extension, which has also been edited by Janagewen. The three users also make similar language errors and express themselves in the exact same way. bonadea contributions talk 15:49, 29 December 2014 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

  • Concur. I was about to report this one myself. Remover remover (RR)'s first contrib (2014-12-29T02:44, ref RR's history) was just two days after Janagewen's previous sock Password Saeba Ryo (PSR) got an indef block (2014-12-27T00:04, PSR's indef block notice). Despite his new status, RR appears very familiar with the other contributors to various talk pages edited by PSR ( [1], [2], [3], [4]). RR's sole interest on WP appears to be PSR's contributions to various talk pages. PSR admitted to being Janagewan and professed to creating PSR simply to ~"finish up incomplete discussions" ( both claims supported here). RR somehow thinks that removing PSR's user pages (and the blocked-as-SP notice) will be conducive to retaining PSR's other talk page contributions and subsequent discussion ( [5], [6]. I can't imagine anybody having such an interest other than Janagewen himself. Furthermore, RR's phraseology, illogic, attitudes toward editors who disagree, and mercurial emotions (example: [7]) are strongly reminiscent of Janagewen's. Jeh ( talk) 19:02, 29 December 2014 (UTC) reply
  • Concur. Same idiosyncrasies. First edit after signup is Revision #640074237 in Template talk:.NET Framework version history. (Janagewen never could let this go.) Please pay attention to whose messages he removes. Second and third edits are in Talk:Physical Address Extension. (Janagewen's second obsession.) Now, the forth edit is actually an unblocked request for User:Password Saeba Ryo! Actually, please look at the history of that page at the last edits. See how persistent he is? See how Claw of Slime has proclaimed: "You (User:Remover remover) are not User:Password Saeba Ryo." (But I beg to differ. He is.) Continuing down his contribution list, we see communicating with the same old editors (Codename Lisa, Dsimic, Jeh) but how would have know us? What list or category would give incentive to a new user to engage in communication with exactly the same users? This person act like Janagewen and talks like Janagewen. Best regards, Codename Lisa ( talk) 21:29, 29 December 2014 (UTC) reply
  • The reason to block user account Janagewen is extremely ridiculous! So what about this text entry written mostly by editors who misleading readers for explanation of 52 bits and PAE, .net framework template? What another ridiculous article I found on Wikipedia.org. To Protect the reputation of the entire Wikipedia.org, I should stop this at once! Remover remover ( talk) 00:32, 30 December 2014 (UTC) reply
Clerk, CheckUser, and/or patrolling admin comments

 Likely. Also, please comment in sections, not at the top of the report. Courcelles 00:41, 30 December 2014 (UTC) reply


23 January 2015
Suspected sockpuppets


User:Computerfaner and User:Janagewen have made similar disruptive edits to the village pump on Chinese wikipedia ( [9] [10]), and both of them have been blocked on Chinese wikipedia due to sockpuppetry ( [11] [12]). 218.81.14.78 ( talk) 07:59, 23 January 2015 (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

05 February 2015
Suspected sockpuppets


Janagewen was indef-blocked on 22 Nov 2014 and since then has employed many sockpuppets, some IPs (see list at bottom of page here) and some registered nicknames. Some, but not all, of the latter were mentioned in this old SPI.

Here we have a similar-patterned nickname, used to edit Edit Physical address extension (a longtime favorite target of Janagewen) to delete a sentence that Janagewen had complained about previously (but was subsequently edited to clarify wording per Jan.'s complaint). On the talk page for that article, dismissed my explanation of Jan.'s complaint, calling my explanation "nonsense". Also made a pointy and wrong to the x86-64 page. Jeh ( talk) 03:03, 5 February 2015 (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

07 February 2015
Suspected sockpuppets


[13] Antigng ( talk) 08:15, 7 February 2015 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

I am from china mainland, my English is not good. So sorry! Starvisionstar ( talk) 10:30, 7 February 2015 (UTC) reply
  • Concur. Hi. After an initial communication in User talk:Codename Lisa § .net framework template, this user has dropped all pretenses: His English suddenly got a lot better and became exactly like that of the sock master. His tone suddenly became hostile. And let's not forget that this socks is engaged in the exact same activities. Also, if this person was from China mainland as he claims, he would not dream of asking anyone to download no less than 7 OSes, each worth a DVD size. Janagewen wouldn't have needed to make so many sockpuppets if only he contacted WP:BASC, apologized, promised not to repeat his past, resorted to using some form of source to back his claims and didn't lie about being a compiler writer for 70 years.
Best regards,
Codename Lisa ( talk) 05:37, 8 February 2015 (UTC) reply
Codename Lisa, who is a compiler writer for 70 years? What is BASC? All of your words remind me of a fact that you are really a teenager, a lovely teenager, so cute! I am so thankful for your words here. I speak British English rather than American English. So I might not understand you thoroughly. No matter I would be blocked or not, I just wish you, this little girl, Codename Lisa, everything goes well and have a good day! Starvisionstar ( talk) 07:05, 8 February 2015 (UTC) reply
  • Concur. He was already blocked but... it appears from SVS's comments at the PAE talk page that he's admitting he's Janagewen. Logic: SVS is a brand new username, but he's mad at me "for what I did to his account". I'm pretty sure the only accounts I've reported for anything recently have been sockpuppets of Janagewen. Jeh ( talk) 23:38, 8 February 2015 (UTC) reply
Seriously, I wish you, Jeh, do not make disruptive to the talk page of PAE, I found you change the name of the same sections over much! Something you explain does really mislead. Please stop! This user account has been locked as I know. So just ignore this user account and close it! — Preceding unsigned comment added by 95.85.50.138 ( talk) 00:09, 9 February 2015 (UTC) reply
Clerk, CheckUser, and/or patrolling admin comments
Blocked the sock (just for the block log record, since they were already globally locked). Also blocked Special:Contribs/95.85.50.138 per WP:DUCK. Note that the sock account was checkuserblocked on simplewiki. Tagged. Closing. Jackmcbarn ( talk) 03:44, 9 February 2015 (UTC) reply

11 February 2015
Suspected sockpuppets


this edit to Physical Address Extension, using Jan.'s trademark accusation of "misleading". Also a purely disruptive/argumentative to the talk page, again with Jan.'s signature all over it, and subsequent reverts of its deletion. Jan. promises there to use "Hide my IP" software to avoid further detection and blocking - clearly an unrepentant sockmaster. Jeh ( talk) 07:48, 11 February 2015 (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

11 February 2015
Suspected sockpuppets


This 3RR report, in which he tries to get me blocked for 3RR violation for reverting his edits. Similar wording and patterns of behavior, obsession with PAE article and with me. Jeh ( talk) 19:14, 11 February 2015 (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


11 February 2015
Suspected sockpuppets


Yet another IP, used to follow up to the 3RR complaint. [14] Jeh ( talk) 23:29, 11 February 2015 (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

15 February 2015
Suspected sockpuppets

New IP socks on Template talk:.NET Framework version history, Talk:X86-64 and User talk:Janagewen -- Claw of Slime ( talk) 04:09, 15 February 2015 (UTC) reply

Comments by other users

Maybe the entire range 221.9.23.0/16 should be blocked.-- Antigng ( talk) 12:41, 15 February 2015 (UTC) reply

This is Janagewen, lock all my IP addresses please. user:Barras know all my IP segments. Please ask him for detail information! Thank you! 221.9.24.116 ( talk) 13:05, 15 February 2015 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

24 February 2015
Suspected sockpuppets

Besides this one, I added one more to the Feb. 15 section above. -- Brangifer ( talk) 16:10, 24 February 2015 (UTC) reply

Comments by other users
Clerk, CheckUser, and/or patrolling admin comments

08 June 2015
Suspected sockpuppets


See User talk:Antigng. Antigng ( talk) 08:51, 8 June 2015 (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

27 August 2015

Suspected sockpuppets

Obvious sock blocked in zhwiki. Request indef block. GZWDer ( talk) 08:25, 27 August 2015 (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


29 August 2015

Suspected sockpuppets


Obvious sock of Janagewen "Neubenuzter" appeared on my talk page to harass me yet again and was subsequently blocked. Shortly after, this IP shows up and corrects "Janagewen's" name in a long-dormant thread at x86-64: diff. IP geolocates to China just like most of J.'s other IP socks. Jeh ( talk) 11:44, 29 August 2015 (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


02 September 2015

Suspected sockpuppets


[21]. User:GoldenQR seems to be another sockpuppet of User:Janagewen. Antigng ( talk) 01:35, 2 September 2015 (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


08 September 2015

Suspected sockpuppets


[22] Antigng ( talk) 09:44, 8 September 2015 (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

  •  Additional information needed - @ Antigng: In order to facilitate and expedite your request, please provide diffs to support your case. Please give two or more diffs meeting the following format:
  1. At least one diff is from the sockmaster (or an account already blocked as a confirmed sockpuppet of the sockmaster), showing the behaviour characteristic of the sockmaster.
  2. At least one diff per suspected sockpuppet, showing the suspected sockpuppet emulating the behaviour of the sockmaster given in the first diff.
  3. In situations where it is not immediately obvious from the diffs what the characteristic behaviour is, a short explanation must be provided. Around one sentence is enough for this. Vanjagenije (talk) 21:09, 8 September 2015 (UTC) reply

17 September 2015

Suspected sockpuppets


IP .216 admitted here that they are serial sockmaster Janagewen. Janagewen and his socks have long been making a series of fiddly edits, usually with quirky edit comments, to X86 (history). This pattern has lately been continued by .216. A few hours after .216 posted the note claiming to be Janagewen, IP .58 takes up the baton at X86. IP .58 geolocates to the same city in China as .216 just like many of the other IPs already identified as Janagewen's socks. Jeh ( talk) 02:33, 17 September 2015 (UTC) reply

Added: New IP .66 edited [[X86]: diff Same sort of quirky, folksy edit summary. Geolocates to same city. Jeh ( talk) 11:54, 17 September 2015 (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

Blows smoke off block button.-- Jezebel's Ponyo bons mots 23:08, 17 September 2015 (UTC) reply
Got the next one: 221.9.21.1 ;)  ·  Salvidrim! ·  23:20, 17 September 2015 (UTC) reply

18 September 2015

Suspected sockpuppets


"CopperQA" posted ( (diff)) to talk page of Physical Address Extension, a long-time Janagewen obsession, with yet more repetitions of the same nitpicking complaints. Username "CopperQA" is of the same pattern as SilverRQ and GoldenQR, previously identified as Janagewen socks (see SPI archive for 2015-09-09). Jeh ( talk) 23:51, 18 September 2015 (UTC) Jeh ( talk) 23:51, 18 September 2015 (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 September 2015

Suspected sockpuppets


[23] [24],similar edits. Antigng ( talk) 06:38, 21 September 2015 (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


28 September 2015

Suspected sockpuppets


This new subsection (diff) to talk:Physical Address Extension, one of Janagewen's long-time hobby-horses, complaining yet again about a point of wording with which he disagrees. In that post he notes that he's gone off to AMD's forums and posted a question about it. Turns out he's "signed" the post there as "Aaron Janagewen".

Also, tried to get the PAE page protected "while we find out what's right". Same ol' same ol' PAE obsession. Jeh ( talk) 15:15, 28 September 2015 (UTC) Jeh ( talk) 15:32, 28 September 2015 (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


02 October 2015

Suspected sockpuppets


Editor EhietGeht pops up at Talk:X86-64#Paging_and_x86-64 and continues with the "discussion" started by one of Janagewen's IPsocks, telling me that my replies thereto are out of bounds as they are "speculation". (This after I'd already noted that WP does not publish speculation.) No need for elaborate diffs here, just look at the signatures and time stamps in the most recent entries in that section.
Editor has made no edits other than to that talk page - continuing Janagewen's fascination with x64 address translation issues.
This is a much less obvious case than the previous Janagewen socks I've reported. EhietGeht did begin by using a distinctly unusual style of formatting their replies ( here and here), using hrules to delineate previous replies and not signing their posts. (I waited a while for signbot to get to it, but it didn't, so I added the sigs manually based on the edit history and corrected the formatting.) I put the standard "tildes" notice template on their talk page, with an additional note about hrules, and their subsequent replies have been formatted normally. The unique style may have been an attempt to look different from Janagewen's usual entries, or this may be a genuinely new editor. But the coincidence of timing (picking up the thread immediately after yet another Janagewen IPsock was blocked), and the continued attempt to get me to stop objecting to Janagewen's incessant attempts to "correct" the x64 and PAE pages, is tough to ignore. Jeh ( talk) 23:51, 2 October 2015 (UTC) Jeh ( talk) 23:51, 2 October 2015 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Never sort anyone else to my user account! This EhietGeht is not me! I am the real Janagewen! 221.9.21.69 ( talk) 04:01, 3 October 2015 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

 Confirmed, blocked, tagged, closing.-- Bbb23 ( talk) 01:18, 3 October 2015 (UTC) reply



03 October 2015

Suspected sockpuppets


And, as usual, after a named sock is blocked, Janagewen complains on my talk page. IP geolocates to the same city as most of Jan's other IPs. Jeh ( talk) 03:43, 3 October 2015 (UTC) reply

And now edits this very report to indicate that it is, in fact, Janagewen. Or claims to be. Jeh ( talk) 04:05, 3 October 2015 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

This is the definitively Janagewen! For this ridiculous policy, I do believe it would eventually ruin the Wikipedia.org for those stupid and woodenhead liars! 221.9.21.69 ( talk) 04:03, 3 October 2015 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments



03 October 2015

Suspected sockpuppets


...and yet more abuse heaped upon my talk page. By the way, if anyone has any better suggestions for handling this, I'd be glad to read it. This isn't working. The sock available has a very large number of IP addresses available and I expect we can't rangeblock his entire ISP... Jeh ( talk) 07:30, 3 October 2015 (UTC) Jeh ( talk) 07:30, 3 October 2015 (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


12th October, 2015


Those are IP addresses that I used to make discussions on talk page of Computer program and X86-64, with the name Aaron J.. 175.19.64.142 ( talk) 07:43, 12 October 2015 (UTC) reply


14 October 2015

Suspected sockpuppets


Editing with tag line Aaron J, a self-admitted alias of longtime serial sockmaster Janagewen: diff , diff Jeh ( talk) 06:19, 14 October 2015 (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


15 October 2015

Suspected sockpuppets
[25], [26] (Compare with [27], [28] an [29] by socks already reported) -- Guy Macon ( talk) 14:49, 15 October 2015 (UTC) reply
In looking over the history of this particular sockpuppeteer I noticed that he keeps coming back to previous edits, adding to them, striking sections, responding to the threads they generate, etc. In order to discourage this behavior I WP:BOLDLY removed all comments with the distinctive signature of he block-evading sockpuppets per WP:DENY on the four pages where he has been posting. [30] [31] [32] [33] -- Guy Macon ( talk) 15:36, 15 October 2015 (UTC) reply
User:AussieLegend partially disagrees. [34] He has a point, but the result still leaves the sockpuppeteer with previous edits to come back to. AussieLegend is clearly correct about our policy, which I already knew, thus my invoking WP:BOLD and thus inviting a WP:BRD revert. Is this a case where we should WP:IAR? I am inclined to wait until the sockpuppeteer comes back to one of those edits first, even though the repeated checking will be a fair amount of work for me to do. -- Guy Macon ( talk) 15:47, 15 October 2015 (UTC) reply
I concur. btw, 3RR doesn't apply when the deletion you're making is of an abusive editor's edits, particularly not a multiple sockmaster. Any new IP edit to talk pages of the articles frequently visited by Janagewen needs to be looked at carefully before responding. The default should be "do not engage" at minimum, with WP:RBI and WP:DENY as soon as a reasonable SP case is made. I of course have been among the "engagers". It is tempting (esp since I'm an instructor in the field) to engage as sometimes J. has decent ideas (although very often confusingly expresed) that are worth discussing. But all too often J. goes back to the unconstructive behavior that got him his permanent block. No more second chances from me. Jeh ( talk) 16:12, 15 October 2015 (UTC) reply
Thanks for pinging me. Policy clearly supports removal of all posts made by a block-evading editor, but you need to be careful when deleting such posts that they don't remove context, which removal did at Talk:Windows XP. One of my own posts was also removed, which is what initially prompted my actions there. Removing posts made by an editor before they were blocked isn't supported, and it does little to stop vandals. It's something we see in the TV project all the time unfortunately. The best action is to delete new posts on sight, and even that doesn't always work. WP:DENY is only an essay, it's not even a guideline and it's certainly not policy. It also doesn't say to remove all posts made by a troublesome editor. -- AussieLegend ( ) 16:32, 15 October 2015 (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


17 October 2015

Suspected sockpuppets


Created an MFD ( diff) for my special watchlist, which does include pages edited by Janagewen and his confirmed former socks. Given J's aggressive SP'ing and wikistalking of me... Who else would do that? Jeh ( talk) 20:10, 17 October 2015 (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


19 October 2015

Suspected sockpuppets


more standard Janagewen abuse heaped upon my talk page ( [35], [36]), and on Talk:Physical Address Extension [37] . I never saw anyone so intent on digging themselves deeper and deeper into a hole of their own making. See also WP:IDIDNTHEARTHAT. Jeh ( talk) 01:57, 19 October 2015 (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


19 October 2015

Suspected sockpuppets

More of the same stuff at my user page. Could both it and my talk page be semi-protected for a week or so? Thanks. Jeh ( talk) 05:32, 19 October 2015 (UTC) reply

Also, a bizarre attempt to accuse me of being the master of three of his socks! Wikipedia:Sockpuppet investigations/Jeh Jeh ( talk) 05:45, 19 October 2015 (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

 Confirmed, blocked, and tagged. IP blocked one month. Jeh, I semi-protected your userpage for one week and extended the existing protection on your Talk page to one week. Particularly on your userpage, there's no reason why the protection couldn't be much longer if you wish. All you have to do is ask. Closing.-- Bbb23 ( talk) 13:53, 19 October 2015 (UTC) reply


24 October 2015

Suspected sockpuppets


Attempting to MFD an unrelated SPI I'd filed, this after "Aaron J", a previous nickname (though not account name) used by Janagewen, made an unconstructive comment to it. Edits ( [38], [39], [40]) to Front-side bus, a past Janagewen obsession. Typical Janagewen-like reaction ("Fuck off xxxxs!") when reverted by ClueBot. Jeh ( talk) 00:06, 24 October 2015 (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

 Confirmed, blocked, tagged, closing.-- Bbb23 ( talk) 00:24, 24 October 2015 (UTC) reply


25 October 2015

Suspected sockpuppets


Edits to Computer program ( diff), Front-side bus ( [41] [42] [43] diffs) - common Janagewen dead-horse points and comments (e.g. "misleading') in edit summaries. Made a copy of one of my ancient sandbox pages for some unknown reason (unknown, that is, other than Janagewen's long-term obsession with me). Wrote ( diff) to Denniss's talk page after D. reverted, attempting fake "German" (I guess) "accent", but IP geolocates to the same place as every other one of Janagewen's IP socks. Jeh ( talk) 04:23, 25 October 2015 (UTC) Jeh ( talk) 04:23, 25 October 2015 (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


11 November 2015

Suspected sockpuppets


Typical petty harrassment of me on my talk page, on my user page, and at Janagewen's old hobby-horse talk:Physical Address Extension. Jeh ( talk) 06:14, 11 November 2015 (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


12 November 2015

Suspected sockpuppets


Editing talk page of former confirmed sock here. Self-admitted here. Jeh ( talk) 13:03, 12 November 2015 (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


13 November 2015

Suspected sockpuppets


Self-admitted here. Another of the typical silly harrassment attempts, trying to get one of my user pages speedy deleted, here. Harrassment of Guy Harris here and here. etc. Jeh ( talk) 02:31, 13 November 2015 (UTC) Jeh ( talk) 02:31, 13 November 2015 (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

Blocked 72 hours, closing.-- Bbb23 ( talk) 05:40, 13 November 2015 (UTC) reply


13 November 2015

Suspected sockpuppets

See [44]. WP:DUCK General Ization Talk 02:57, 13 November 2015 (UTC) reply

More typical Janagewen harrassment. Edits my user page [45], tries to restore Janagewen's previously-deleted abuse on my talk page [46], silly attempt to close his own SPI [47]. Jeh ( talk) 03:01, 13 November 2015 (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

Already blocked, closing.-- Bbb23 ( talk) 05:42, 13 November 2015 (UTC) reply


13 November 2015

Suspected sockpuppets

See edits. WP:DUCK General Ization Talk 03:15, 13 November 2015 (UTC) reply

Once user:jeh also misspelled my name like this, so this user account should also been locked and blocked. Janagewan ( talk) 03:18, 13 November 2015 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

This user account should be blocked and locked. Janagawen ( talk) 03:16, 13 November 2015 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

 Confirmed, blocked, tagged, closing.-- Bbb23 ( talk) 05:39, 13 November 2015 (UTC) reply


17 November 2015

Suspected sockpuppets


The username seems a very unlikely coincidence, and the edits are to restore previous talk page edits by another sock of the same user removed per WP:Deny [48] Meters ( talk) 00:40, 17 November 2015 (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

Blocked and tagged based on behavior. Closing.-- Bbb23 ( talk) 00:58, 17 November 2015 (UTC) reply


19 November 2015

Suspected sockpuppets

Creates page User:Jeh/removed to continue harassment of User:Jeh. WP:DUCK General Ization Talk 05:55, 19 November 2015 (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 December 2015

Suspected sockpuppets


Posts to talk:Physical Address Extension (a longtime Janagewen obsession) regarding OS X (a recent Janagewen interest) here, and to talk:x64 (ditto) here. Both show typical Janagewen phrasing, manner, and approach. These two brief posts would not be much evidence for a previously-unheard-of sock case. But given Janagewen's long-term abuse, including his long insistence on arguing forever over these articles, and his recent involvement with the OS X article and talk page, a checkuser is justified. Jeh ( talk) 08:28, 4 December 2015 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

We do not care about who this user really is, but this user account, as least as I know at this moment, there is not any abusive edit made by this account. So we have the strong will to get this user back to improve Wikipedia! So please wiki administrators declined this sock puppet inspection, and unblock this user account, please! — Preceding unsigned comment added by 103.1.149.90 ( talk) 09:51, 5 December 2015 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments


30 November 2015

Suspected sockpuppets


A new account was created immediately following the banning of old one. It then reverts the deletion of the old account's content three days apart, and proceeds to continue to robotically reinsert the same (and same type of) additional content, which are mostly aimless essays. [49] [50] Just glance at the very short and blatant contribution history where @ Guy Harris: also says he thinks this is a sockpuppet. Thank you. — Smuckola (talk) 05:16, 30 November 2015 (UTC) reply

The user is spreading defiantly anti-SPI and nonsensical rhetoric through their whole contribution history. — Smuckola (talk) 12:28, 1 December 2015 (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


02 December 2015

Suspected sockpuppets

[51] [52] [53] [54] This is the latest in a series of attacks from a multitude of IP addresses, as he stated was his strategy. — Smuckola (talk) 07:51, 2 December 2015 (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


03 December 2015

Suspected sockpuppets


He's just reinserting the babbling he's done using his past IP addresses. Just childish stalking. [55] Smuckola (talk) 13:28, 3 December 2015 (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


05 December 2015

Suspected sockpuppets


Restored his comments (they'd been RBI'd) at Talk:Physical Address Extension ( diff) and talk:x86 ( diff), followed by ridiculous attempt at my talk page ( diff) to warn me against further reports and WP:RBI actions. He's now using a proxy from Canada, but the subject and verbiage patterns are completely transparent. Jeh ( talk) 06:49, 5 December 2015 (UTC) reply

And more of the same at my talk page. diffs Jeh ( talk) 09:39, 5 December 2015 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Well, we do not expect any wikipedian to inspect other's IP without permission! So I suggest to cancel this inspection! — Preceding unsigned comment added by 103.1.149.90 ( talk) 09:29, 5 December 2015 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments


05 December 2015

Suspected sockpuppets

Yet another sockpuppet. As a bonus, there's the mutilation of an admin's warnings on his old sockpuppet. [56] Also can you please possibly report them to their ISPs? I think I heard they were using Verizon and Qwest, across IPv4 and IPv6. The admin in question, has the research on this. They are committing mass ban evasion, wikistalking and harassment and personal attacks, refactoring of other people's talk pages, disruptive editing, deleting of admins' orders. These have all been specifically reported in conjunction with this We talk about Mac OS X which is in turn a sockpuppet of another sockmaster.— Smuckola (talk) 13:53, 5 December 2015 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

The user behind the IP 75.162.205.14 ( talk · contribs · deleted contribs · logs · filter log · block user · block log) (and many others) is not, as far as I can tell, associated with Janagewen or with Janagewen's "We talk about..." socks. The subject areas are different and the writing style is very different. Jeh ( talk) 07:37, 6 December 2015 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments


09 December 2015

Suspected sockpuppets

The user replaced some previously removed content, which had been removed because they were a sockpuppet. [57] Smuckola (talk) 16:37, 9 December 2015 (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


December 10th, 2015

Suspected sockpuppets

I am completely tired of making any contribution towards Wikipedia.org. So I report myself here, and please this user account again! Thank you! Pier Toll ( talk) 07:41, 10 December 2015 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Confession on this page — Smuckola (talk) 12:47, 10 December 2015 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments


18 December 2015

Suspected sockpuppets


Hi guys. I'm seeing confirmed behavioral evidence here. This is a 7 day old account that immediately edits the same PC technological subjects and launches the same delusional and nonsensical personal attack, to me, on the same article as before. While claiming to have been watching me for some time. [58] All using the same badly broken and nonsensical English. He dug up deleted content from a Talk page[ [59] where this sock had been previously reverted. [60]@ Ohnoitsjamie: I guess I'd ask for a checkuser but anyone familiar with this guy knows what to do. — Smuckola (talk) 23:48, 18 December 2015 (UTC) — Smuckola (talk) 23:48, 18 December 2015 (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


22 December 2015

Suspected sockpuppets


self-admitted here. Geolocate is consistent with Janagewen's previous IP socks.

In addition to blocking please semi-protect the pages edited by the IP. Thank you. Jeh ( talk) 05:53, 22 December 2015 (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


26 December 2015

Suspected sockpuppets

Undoing of your actions against his previous sockpuppet. — Smuckola (talk) 04:53, 26 December 2015 (UTC) reply

previously blocked IPsock - this IP. Also note the personal attack below which is characteristic of this editor and their many socks. -- bonadea contributions talk 11:26, 26 December 2015 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.


@ Smuckola:, what such a poor English expression! Do I need find something more to prove how poor your English is?

Clerk, CheckUser, and/or patrolling admin comments

  •  Additional information needed - @ Smuckola: In order to facilitate and expedite your request, please provide diffs to support your case. Please give two or more diffs meeting the following format:
  1. At least one diff is from the sockmaster (or an account already blocked as a confirmed sockpuppet of the sockmaster), showing the behaviour characteristic of the sockmaster.
  2. At least one diff per suspected sockpuppet, showing the suspected sockpuppet emulating the behaviour of the sockmaster given in the first diff.
  3. In situations where it is not immediately obvious from the diffs what the characteristic behaviour is, a short explanation must be provided. Around one sentence is enough for this. Vanjagenije (talk) 11:21, 26 December 2015 (UTC) reply

27 December 2015

Suspected sockpuppets

Smuckola
(talk) 
00:16, 27 December 2015 (UTC)
reply

Same. [61] Smuckola (talk) 00:19, 27 December 2015 (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


27 December 2015

Suspected sockpuppets

Smuckola
(talk) 
08:34, 27 December 2015 (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


07 January 2016

Suspected sockpuppets

[62] Smuckola (talk) 08:28, 7 January 2016 (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


20 January 2016

Suspected sockpuppets


Self-admitted with these edits. Also, subject matter (x86) and crude language are typical of Janagewen. Jeh ( talk) 06:28, 20 January 2016 (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


24 January 2016

Suspected sockpuppets


Who else would revert my WP:DENY-based deletion of Janagewen's IP sock's previous abusive comments to talk:x86? Or follow me to David L. Jones and make a typically clumsy attempt to CSD that article? Jeh ( talk) 10:30, 24 January 2016 (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


27 January 2016

Suspected sockpuppets


In this round of sockpuppetry Janagewen goes back to one of his hobby-horses, x64 page table formats and x64 architecture in general. He:

  • deletes a talk page comment of mine at talk:x86-64
  • restores a large number of changes at talk:x86-64 made by IPs signing as "Aaron J", previously deleted as these were confirmed socks of Janagewen
  • "fixes" the "version" wording at PAE that he has argued against for so long
  • deletes a perfectly valid reference from the PAE page

There are also revisits to two other Janagewen favorites, at Front-side bus and OS X. Jeh ( talk) 01:18, 27 January 2016 (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


29 January 2016

Suspected sockpuppets

Re-instatement of edits made by previously blocked sock, Sensorite ( talk + · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log· investigate · cuwiki). New account, no contributions to clearly indicate WP:HERE, one contribution which may be WP:PERSONAL. Murph9000 ( talk) 00:13, 29 January 2016 (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


22 February 2016

Suspected sockpuppets


self-admitted here, at one of J.'s favorite hobby-horses. geolocate info is consistent with J's previous IPs. Jeh ( talk) 08:36, 22 February 2016 (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


23 February 2016

Suspected sockpuppets


Standard Janagewen abusive nickname and harrassment. https://en.wikipedia.org/?title=Talk:Physical_Address_Extension&oldid=prev&diff=706434897 Jeh ( talk) 09:00, 23 February 2016 (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



24 February 2016

Suspected sockpuppets

See this edit at User talk:Jeh. Continuing harassment. General Ization Talk 03:14, 24 February 2016 (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


27 February 2016

Suspected sockpuppets


Yet another attempt to add the very same comment at the talk:Physical Address Extension page. Jeh ( talk) 04:15, 27 February 2016 (UTC) Jeh ( talk) 04:15, 27 February 2016 (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


07 July 2016

Suspected sockpuppets


Similar comment style at talk:x86 and talk:OS X. (For more details about the "comment style", please PM.) But I have to say that this is just an impression at this point. I'm not seeing a duck, but I'm hearing quacks from somewhere and there are footprints that could have been made by a duck. Jeh ( talk) 19:20, 7 July 2016 (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

 Confirmed, blocked, tagged, closing.-- Bbb23 ( talk) 19:57, 7 July 2016 (UTC) reply


17 July 2016

Suspected sockpuppets


Same favorite topics ( x86, OS X, 3GB barrier), language choices (details privately on request from an admin), opinions, confusions, and target choices (me) as on many other occasions. Jeh ( talk) 07:44, 17 July 2016 (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

 Confirmed, blocked, tagged, closing.-- Bbb23 ( talk) 17:03, 17 July 2016 (UTC) reply


16 August 2016

Suspected sockpuppets


WP:DUCK based on this edit - NQ (talk) 05:46, 16 August 2016 (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 September 2016

Suspected sockpuppets

Self-admitted here on my talk page. Edited article talk page here, no signature of any sort, but with a standard old Janagewen topic and taunt. IP geolocates to Changchun, China, just like most of Jan.'s other IP socks. Jeh ( talk) 10:49, 30 September 2016 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Yeah, I love to hear the words from Jeh, who acts like a lady! But I am not so sure whether she looks charming or not! But anyway, show my polite to her, this very person. Aaron Janagewen 221.9.16.71 ( talk) 12:51, 30 September 2016 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments


09 October 2016

Suspected sockpuppets

Self-admitted here for .246, here for .5, and here for .160. Same hobby-horse topics, x86, Template talk:.NET Framework version history, etc. Same language patterns and style of interaction. All three IPs geolocate to Changchun China, just like all of J.'s previous IPs. Jeh ( talk) 04:40, 9 October 2016 (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

 Blocked and tagged Going to close now-- 5 albert square ( talk) 05:08, 9 October 2016 (UTC) reply


10 October 2016

Suspected sockpuppets

More abusive editing at talk:x86. Copied a huge table (to which he's spent much time adding disputed material) from the article into the talk page - with self-admission of identity at the end of the copied material, here. IP geolocates to same city in China as nearly all of the others. Jeh ( talk) 03:28, 10 October 2016 (UTC) reply

@ Jeh:, if you dislike China, well, just do something actually rather than set troubles to me, alright! Is there any word saying that Chinese or user in China could not edit Wikipedia? Where the hell do you come from? America or United States of America? Let me see your IPs, can you expose your IPs to the readers? Oh, no, you dare not! Because you are totally a liar! Everything you mentioned on wiki prove it! Let us take a look at the articles you are involved, especially for x86, PAE, x64 and so forth, how can I say you are someone hired by Microsoft. If so, why not let us know your name? China, china, china, ..., enough! Over-enough, I am so tired of China and Chinese, do not repeat it that lot! Are you Chinese? Or why are you so interested in it? Are the fucked woman by you are Chinese, which made you really have passion on that thing too?! Oh, I wanted let you know I dislike those two phases over much! Stop mentioning that anymore! If you want to block me, just write my name, then my IP or user name would be blocked! Simple and easy! --- Aaron Janagewen, (can you spell my name? ) 119.53.104.217 ( talk) 04:59, 10 October 2016 (UTC) reply
I have nothing at all against China, Chinese, or people in China who are not Chinese. It is simply a fact that nearly all of your past IPs geolocate to the city of Changchun - and so does this one. So it's evidence. Not that we need it because you self-admitted. In deference to your preference, though, in the future I will simply write "...to the same city" rather than using the city and/or country name. Jeh ( talk) 05:33, 10 October 2016 (UTC) reply
To clerks: I made an error in filing this - it should be under Janagewen rather than janagewen. Sorry. Jeh ( talk) 06:52, 10 October 2016 (UTC) reply
 Done. Vanjagenije (talk) 13:06, 10 October 2016 (UTC) reply
RESPONSE TO Jeh, you are just a nothing! Who would care who or what you are against? It is all up to you to against anything you want to. But after all you are just a nothing! Sorry, meaningless! China is China, Changchun is Changchun, people native to those places are themselves. But Aaron Janagewen is just Aaron Janagewen, never have any relationship with both of them. The only thing Aaron Janagewen appreciate is British culture and English, this greatest language. So please never mention China and/or Changchun when you call my name or point to me, OK! You do not have to show your excuses here, meaningless. What's more, you are welcome to report me and/or block me indirectly, I do appreciate your behaviour, and I show my greatest disappointment to you, this person, not only the name Jeh. But stopping repeating those annoy phrases to the things related with me, alright? Are you able to understand/comprehend my words here? If the next time, I use the IPs from United States, would you please refer me to America and American people? Funny! --- Aaron Janagewen

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



11 October 2016

Suspected sockpuppets

Still trying to force his way onto x86, at about the same time of day. IP geolocates to the same city/country as yesterday's. Jeh ( talk) 06:40, 11 October 2016 (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


12 October 2016

Suspected sockpuppets


Janagewen's old tricks of trying to speedy delete one of my user pages, other harassment. Account created shortly after x86 (another Janagewen hobby-horse) was semi-protected after vandalism by Janagewen's IP socks. Username obviously refers to me, which is a no-no, and something Janagewen has done before in response to his socks being reported, found and blocked. Jeh ( talk) 03:21, 12 October 2016 (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


12 October 2016

Suspected sockpuppets

Self-admitted here in a comment to the preceding SPI. Jeh ( talk) 05:07, 12 October 2016 (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



12 October 2016

Suspected sockpuppets

Another typical Janagewen pattern of making bizarre comments to his own SP cases after the previous report was filed, then self-reverted, before previous report was closed. Also followed up on previous IP's comments re edits to x86 and its talk page here, then self-reverted. Similarity of IPs and geolocation with previous cases. Jeh ( talk) 19:34, 12 October 2016 (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



13 October 2016

Suspected sockpuppets

Created yet another subpage in my userspace, then edited it, both as "Jehcantasshale", then edited again as the IP, with harassing content and edit summaries. Jeh ( talk) 01:24, 13 October 2016 (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


19 October 2016

Suspected sockpuppets

Editing at talk:x86 again, self-admitted identity here. Jeh ( talk) 10:42, 19 October 2016 (UTC) Jeh ( talk) 10:42, 19 October 2016 (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 October 2016

Suspected sockpuppets

Further editing at talk:x86, with self-admission, here and here. Jeh ( talk) 04:03, 21 October 2016 (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


28 October 2016

Suspected sockpuppets

Same sort of profanity, etc., at talk:x86 ( diff diff diff), and talk:Windows XP ( diff), self-admitted at the latter three. Geolocation info goes to same city as Jan.'s previous IPs. Jeh ( talk) 04:25, 28 October 2016 (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


29 October 2016

Suspected sockpuppets


diff - still more tendentious arguing about interpretation of terminology at talk:Physical Address Extension. The argument advanced there is essentially the same, using some of the same wording (as well as some Janagewen's same stylistic markers), as appeared here in August 2015. The August 2015 entries were written by CopperQA ( talk · contribs · deleted contribs · logs · filter log · block user · block log), later found to be yet another Janagewen sock. Jeh ( talk) 04:34, 29 October 2016 (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 October 2016

Suspected sockpuppets

reverted deletion of previous Janagewen sock's material at Physical Address Extension: diff). Also posted new specious arguments at talk:x86 ( diff), one of Janagewen's favorite topics. Geolocation is consistent with Janagewen's previous IP socks. Jeh ( talk) 05:22, 30 October 2016 (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


14 November 2016

Suspected sockpuppets

Typical Janagewen pattern: Retaliatory revert of my edit here (he reverts many of my edits, apparently for no reason other than that I made them), plus yet another misguided argument about nomenclature at talk:x86-64, here. IP geolocates to the same place as almost all of Janagewen's other IP socks. Jeh ( talk) 09:08, 14 November 2016 (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


13 April 2017

Suspected sockpuppets

Self-admitted in this edit (see the signature "Aaron Janagewen"). I like his contribution to this discussion but also think he should respect the block placed against him. Jasper Deng (talk) 18:35, 13 April 2017 (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



14 April 2017

Suspected sockpuppets

See [63]. General Ization Talk 03:04, 14 April 2017 (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



16 April 2017

Suspected sockpuppets

More quacking like a previous sock; seems like 221.9.0.0/19 is consistently being used here. @ 221.9.21.196: Unfortunately, WP:BANNEDMEANSBANNED. Jasper Deng (talk) 17:02, 16 April 2017 (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


01 May 2017

Suspected sockpuppets

(These comments are for the first three IPs listed; see addition below)
These edits: [64], [65], and [66] look benign enough, but the accompanying talk page edit here has all the usual Janagewen footprints: a) geolocation of IP to the same city in China as practically all of Jan's other IPs; b) these IPs are in the same /19 group as many other of Jan's IPs (119.53.96.0/19, third number between 96 and 127); c) kneejerk supporting people who disagree with me in content disputes on articles re Windows (see for example here and here), also his removed edit to User talk:PastieFace of 2017-04-14T02:52:47; d) other traits that will be familiar to those who have dealt with Jan. before, not excepting calling my edits "nothing" at every opportunity. (If the reviewing admin is unfamiliar with Jan., please review Jan's SP archive... or defer to an admin who is. Thanks!) Jeh ( talk) 05:36, 1 May 2017 (UTC) reply

See also the flood of offpoint attempts at distraction ("why did you do x?" when x is not the subject of discussion), slightly-faulty English (e.g. "compressible" instead of "comprehensible"), and "do not edit" order here. All common Janagewen patterns. Jeh ( talk) 20:51, 1 May 2017 (UTC) reply

Added 05 May: Two IPs in 221.9, edits (showing edit-warring) here, this time with an apparently abusive edit comment, here, and here. These two are from another block of IPs commonly seen in Janagewen's SPI archive, 221.9.0.0/19 , third number between 0 and 31). Jeh ( talk) 01:34, 6 May 2017 (UTC) reply

Also 05 May: And one more: 221.9.14.211, diffs here and here and here, again showing edit-warring.

Suggest blocking 221.9.0.0/19 and 119.53.96.0/19 for a time. It's been done before. Jeh ( talk) 03:26, 6 May 2017 (UTC) reply

Added 06 May: Continued discussion on Talk:x86-64, including the usual rants against Jeh, from another 119.53 IP, in a discussion started by a 221.9 IP also responsible for multiple reversions on x86-64. Guy Harris ( talk) 23:24, 6 May 2017 (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


11 May 2017

Suspected sockpuppets

Edits to talk:x86 here, here, and here. Same Janagewen hobby-horse (~"x64 is not / is an extension to x86"), also "this article is all wrong", standard Janagewen word-salad. IPs are in the same /19 block (119.53.96.1) as Jan's other 119.53 socks. Jeh ( talk) 02:46, 11 May 2017 (UTC) Jeh ( talk) 02:46, 11 May 2017 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

And more from 221.9.21.45, including his usual desperate pleas to stop disagreeing with him. Guy Harris ( talk) 01:51, 13 May 2017 (UTC) reply

Note that 221.9.21.45 is from another block of IPs commonly seen in Janagewen's SPI archive, 221.9.0.0/19 , third number between 0 and 31. Jeh ( talk) 02:31, 13 May 2017 (UTC) reply

And [ https://en.wikipedia.org/?title=X86-64&type=revision&diff=780116066&oldid=780115382 another edit that probably spewed obscenities in the edit summary, Janagawen-style. Guy Harris ( talk) 03:30, 13 May 2017 (UTC) reply

No, it was an attempted WP:OUTING. Also Janagewen style (recently, anyway). Jeh ( talk) 05:23, 13 May 2017 (UTC) reply

Yeah, they are just me, definitely, Janagewen! Thank you for promoting! 221.9.15.78 ( talk) 00:42, 18 May 2017 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments


15 May 2017

Suspected sockpuppets

Same old Janagewen prattle here and here. And another attempted outing here. Edit-warring in mainspace here and here. Same subject areas as before (x86 and x64 processors), same two /19 IP groups, same city in China as many of Janagewen's other IPs.

Added another IP, 119.53.115.198. Series of edit-war edits, the last one here, including yet another attempted outing (since oversighted).

These two /19 IP groups are being used for long-term abuse, not just SP but now attempted outing, and should be blocked for an extended period. Jeh ( talk) 12:06, 15 May 2017 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Yeah, they are just me, definitely, Janagewen! Thank you for promoting! 221.9.15.78 ( talk) 00:43, 18 May 2017 (UTC) reply


Clerk, CheckUser, and/or patrolling admin comments


16 May 2017

Suspected sockpuppets

Begging for removing protection at x86-64 since his edit-warring attempts there under other IPs (previously reported above) have been continuously rejected by three different editors. Then proposed a silly "vote" at talk:x86-64 ( [67], [68], [69]). i.e. persistent edit-warring.

Same two IP ranges as before, same geolocation to same town in China. Jeh ( talk) 15:48, 16 May 2017 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Yeah, they are just me, definitely, Janagewen! Thank you for promoting! But please do not get to close to me, Jeh, I do not know you! China? Why the hell you mention it all the time? You love the chicks there? Come and get, please! If you are interested in Chinese, I would make you disappointed! Once again, I am not interested in your stupid training company, and please keep enough distance! 221.9.15.78 ( talk) 00:47, 18 May 2017 (UTC) reply


Clerk, CheckUser, and/or patrolling admin comments


17 May 2017

Suspected sockpuppets

Same subject area, IP /19 group, and location in China as most of Janagewen's other socks. Now he's moved on to spurious and unjustified CSDs here and here. Jeh ( talk) 09:57, 17 May 2017 (UTC) reply

During these recent period of a large backlog of SP reports, Janagewen the LT sockmaster has been making merry at his old haunts. Now he's attempted to restore his version of the large "feature history" table at x86 ( diff of four revisions) despite the fact that he self-admitted adding OR to it and despite consensus for the current version. Jeh ( talk) 15:57, 17 May 2017 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

And he then proceeds to request that IA-32 be merged into x86 by... simply redirecting it to x86, rather than putting up a merge request. Guy Harris ( talk) 18:36, 17 May 2017 (UTC) reply

221.9.15.78, same /19 range, from which came a rant on my talk page - and, not surprisingly, he seems to spend more energy attacking Jeh than me. Guy Harris ( talk) 00:34, 18 May 2017 (UTC) reply

Thank you, guys! Thank you for promoting me here! Yeah, that is the definitely Aaron Janagewen. Once again, I thank you for reporting me continuously for recording all my efforts on Wikipedia.org. I am also very glad that you show your losing position when failed in that argument with me, and then report me and advertise to this land! 221.9.15.78 ( talk) 00:51, 18 May 2017 (UTC) reply

Another one from 119.53.108.167 - the usual sort of rant, although he only alludes to Jeh in passing in this one. Guy Harris ( talk) 03:07, 18 May 2017 (UTC) reply

And another from 119.53.109.106 - harassment on my talk page. Jeh ( talk) 05:16, 18 May 2017 (UTC) reply
IP mentioned above (119.53.109.106) has been blocked for harassment. ~Oshwah~ (talk) (contribs) 06:22, 18 May 2017 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments


25 May 2017

Suspected sockpuppets

Edit-warring (prior to page being SP'd) yet again at x86-64 here, here, and here.
Yet more pointless harping on obscure points of terminology re x64 processors here.
Revert of my edit here (likely harassment, as Janagewen has never shown interest in phone connectors before).
IPs geolocate identically to Janagewen's previous IPs. Requesting a rangeblock. Jeh ( talk) 11:51, 25 May 2017 (UTC) Jeh ( talk) 11:51, 25 May 2017 (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


26 May 2017

Suspected sockpuppets


as .96, standard Janagewen-style pointless arguing here and here. Then filed an abusive AIV report here (since oversighted). IP .96 was blocked by @ Ponyo:.
As .43, further pointless arguing here.
As before, geolocation and IP range info are consistent with Janagewen's previous confirmed IPs. Jeh ( talk) 02:52, 26 May 2017 (UTC) Jeh ( talk) 02:52, 26 May 2017 (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



27 May 2017

Suspected sockpuppets

Edit-warring at Instruction set architecture ( history). IPs geolocate to same place as almost all of Janagewen's other IP socks, language and topic area are consistent. Jeh ( talk) 01:51, 27 May 2017 (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

All blocked, closing. GAB gab 16:47, 29 May 2017 (UTC) reply

27 May 2017

Suspected sockpuppets

More pointless arguing about x86 terminology here. Jeh ( talk) 10:00, 27 May 2017 (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

Blocked, closing. GAB gab 16:47, 29 May 2017 (UTC) reply

28 May 2017

Suspected sockpuppets

Having been blocked by semi-prot from edit-warring at Instruction set architecture, Janagewen has now switched to Comparison of instruction set architectures. Made one undiscussed and very significant change, in defiance of already-established consensus at Instruction set architecture, x86, and others, here as .177.
was reverted with "please discuss", but re-reverted here, here, here, and as .41, here, and here.
Five reverts in slightly under two hours.
Now as .203, three more reverts here, here, and here.
Also, as .43, highly abusive personal attacks left here at Guy Harris's talk page, again consistent language with Janagewen.
As .7, ridiculous "but I'm the victim here!" ANI report here, followed by more silliness on the same page.
As .204, harassment at my talk page here, followed by an attempted outing as .155 here (since oversighted).
IPs are in the same 221.9.1.1/19 (third number between 0 and 31) and 119.53.96.0/19 (third number between 96 and 127) ranges and geolocate to the same city in China as almost all of Jan's other IPs.
I have been told that it is not reasonable to block these entire ranges due to "collateral damage" but I have reason to believe that nobody else from 119.53 or 221.9 (/16, not just the /19 ranges) has edited WP for the last few days. Can't we just try it and see if anyone complains? Jeh ( talk) 02:17, 28 May 2017 (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

Everyone's blocked, closing. GAB gab 16:48, 29 May 2017 (UTC) reply

10 June 2017

Suspected sockpuppets

Janagewen is back with a different IP range than the two recently used and blocked, but 175.19.64.1/something has appeared in his SPI history in the past. Again, same city in China, same topics, same hobby-horses, same peculiar choices of English wording and phraseology (details will be provided privately upon request). Edit-warring at x86, attempting to restore his previous against-consensus version, here, heree, here, and (so far) here. Typical near-incomprehensible prattle at talk:x64 here, here, here, Jeh ( talk) 10:56, 10 June 2017 (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


18 June 2017

Suspected sockpuppets

Janagewen is back with another IP in his new range (previously 175.19.66.153). Pattern is entirely consistent with the immediately previous report.

In short, still very much WP:NOTHERE, and still abusing his indef blocks. Jeh ( talk) 04:55, 18 June 2017 (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



18 June 2017

Suspected sockpuppets

And he's back with yet another IP in the same range, at three of the same pages previously reported, reverting to the material he added previously, while blocked:

Is it time for a narrow rangeblock? So far (recently) we have 175.19.66.47, .153, and this one, .130. Jeh ( talk) 10:31, 18 June 2017 (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



20 June 2017

Suspected sockpuppets

Kneejerk reverts of previous removals of its edits:

Of course, this geolocates to the same town in China as almost all of Janagewen's previous IPs.

Recent 175.19 IPs used by Janagewen:

SP investigators: Please help implement the "B" in WP:RBI. Thank you. Jeh ( talk) 15:19, 20 June 2017 (UTC) Jeh ( talk) 15:19, 20 June 2017 (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


24 July 2017

Suspected sockpuppets

Janagewen is back at his same old haunts and one new one.

This IP is within the same /24 block as many previously-blocked Janagewen socks. (see this recent archived case). Looks like the rangeblock expired and needs to be reinstated? Jeh ( talk) 23:15, 24 July 2017 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

(This is a comment to the comment below by GAB) Since Janagewen apparently has access to a very wide range of IPs (as can be seen by his SP archive history), only rangeblocks have been effective against her or him. Jeh ( talk) 01:08, 25 July 2017 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments



25 July 2017

Suspected sockpuppets

And indeed, a new rangeblock is clearly required...

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


26 October 2017

Suspected sockpuppets

Pointless wikitwiddling at x86-64, completely consistent with Janagewen's many socks' past unwanted attention to this article, for example here. IP is very close to many IPs in Jan's SPI archive, and geolocates to the same town and the same ISP. Looks like one of the rangeblocks needs to be either widened or renewed. Jeh ( talk) 04:58, 26 October 2017 (UTC) reply

edit - added: And, of course, he edit-wars (diff) to insist on his change. That too is classic Janagewen. Jeh ( talk) 08:58, 26 October 2017 (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


15 June 2018

Suspected sockpuppets

IP in same range as before, same ISP, same city of origin, same hobby-horses: Talk:Instruction set architecture ( diff), Comparison of instruction set architectures ( diff), Talk:x86 ( diff). There would be nothing particularly wrong with the talk page edits, but the change to Comparison of instruction set architectures is against long-standing consensus, and anyway (of course) indef-blocked people are not allowed to edit at all, regardless of the merits of their edits. Looks like the IP rangeblock needs to be renewed. Jeh ( talk) 09:21, 15 June 2018 (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



20 June 2018

Suspected sockpuppets

Diff at Yuki Hsu. See the other recent history of that page for the other IPs. New topic area, but same old Janagewen language in the edit summary. The 119.53 rangeblock needs to be renewed. Jeh ( talk) 02:51, 20 June 2018 (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


02 October 2018

Suspected sockpuppets

Self-admitted in this diff. These are IPs in one of several ranges used by long-time indef-blocked user:Janagewen. (See previous SPI archive for the history.) Each range has been blocked in the past. The block on this range has apparently expired recently and so Janagewen is of course back. Janagewen's indef block has, of course, not expired, and blocked users aren't allowed to edit. So here we have unpermitted editing and edit-warring at talk:x86: diff, diff, diff, diff, diff, etc.

Suggest reinstating the block on this range for a year - or longer. Thank you. Jeh ( talk) 08:51, 2 October 2018 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

As Jeh mentioned, the above IP is being very disruptive on Talk:X86. They keep constantly demanding to have their contributions removed from the article, even after we've mentioned that doing so is not going to happen. — AfroThundr ( u · t · c) 15:14, 2 October 2018 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

THANK YOU. Jeh ( talk) 17:35, 2 October 2018 (UTC) reply

06 March 2020

Suspected sockpuppets

Edits, obsessed with promoting his notion of what "x86-64" means, with no supporting evidence, from an IP address in China. See, for example, https://en.wikipedia.org/?title=X86&diff=prev&oldid=944010092, and repeated reversions of my changes. Guy Harris ( talk) 03:07, 6 March 2020 (UTC) reply

See also the tone of his comments on the talk page, such as this one and https://en.wikipedia.org/?title=Talk%3AX86&type=revision&diff=944164742&oldid=944159019 this one]. Guy Harris ( talk) 07:13, 6 March 2020 (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