Jump to content

Wikipedia:Requests for checkuser/Case/YINever

From Wikipedia, the free encyclopedia
The following discussion is preserved as an archive of a Request for checkuser. Please do not modify it.

YINever

[edit]

User:YINever has been edit warring with User:PatCheng and many other editors over the article The Epoch Times. I suspect that User:YINever has many sockpuppets if you look at the history of The Epoch Times article. Also look at User:YINever's contributions. It is clear the editors listed above are all new users. User:YINever is a likely sockpuppet of User:Freereader, User:Web spy killer, User:65.33.167.138, and User:141.153.74.246. RevolverOcelotX 03:00, 5 June 2006 (UTC)[reply]

There is no evidence of policy violation here, so no rationale for a check other than a hunch. This is a retaliatory request and an abuse of the system. For clarity's sake, I have used the latter IP but have nothing to do with the first three. YINever 03:04, 5 June 2006 (UTC)[reply]
YINever, you have CLEARLY reverted the article The Epoch Times with your IP address after you were at the limit of breaking the 3RR rule. See here: [1]. Your editing patterns are extremely similar if, not identical, to the other 3 accounts. They are all fairly new accounts and all have engaged in an edit war at the The Epoch Times article. --RevolverOcelotX 03:09, 5 June 2006 (UTC)[reply]
A simple web WHOIS lookup reveals that the latter two IPs are registered under different services, in different states, from different states. Considering I use the latter, that would be a rather remarkable technical feat for an unskilled user like myself. Simply stated, there is no merit to this claim and it is simply leveled to water down the initial RFCU below and distract attention from it. --TJive 03:19, 5 June 2006 (UTC)[reply]
I have also added the User:TJive as a possible sockpuppet of User:YINever because he has admitted to having an account called "YINever". See here: [2] where User:TJive says "where my primary account is "YINever"" on the talk page of User talk:Blnguyen. --RevolverOcelotX 03:33, 5 June 2006 (UTC)[reply]
I recently filed a check user request that was declined (see below). I listed.
TJive then claimed he was posting under 141.153.74.246. Now it appears that YINever is claiming to post from 141.153.74.246. I believe it is possible that YINever and 141.153.74.246 are TJive. I am totally confused, but hope this adds some facts. Some of the discussion was deleted by Voice of All here[3]. I think the issue of Nobs01 was used to distract attention from the multiple accounts being used for edit warring.--Cberlet 03:40, 5 June 2006 (UTC)[reply]

Here is further evidence where User:YINever has ADMITTED to being a sockpuppet of User:TJive. [4]. I hope it is now clear to the administrators that User:YINever is a sockpuppet of User:TJive and possibly other accounts/IPs on the list. --RevolverOcelotX 03:44, 5 June 2006 (UTC)[reply]

Can the clerk assist in this matter, please? I never denied having two accounts, and it has nothing to do with the original charge, which remains nothing but fishing on the part of this user. Now that he has retroactively inserted TJive it makes it appear as if my original denial pertains to that account rather than the ones he started with. No evidence was put forth (per the declined Cberlet RFCU) that either is violating policy, alone or in tandem, so the matter is irrelevant. YINever 03:48, 5 June 2006 (UTC)[reply]
User:YINever has used his sockpuppets to break the 3RR. Here is evidence of him ADMITTING[5] to being a sockpuppet of User:TJive. I also suspect the other accounts/IPs are also his sockpuppets. User:YINever is in violation of 3RR by using his sockpuppets. --RevolverOcelotX 03:52, 5 June 2006 (UTC)[reply]

Can you point to where TJive and YINever have together conspired to break 3RR? No, you can not, because such an event does not exist. You are attempting to blur the issues. This report did not concern TJive. It concerned four other accounts, one of which is an IP I used. Do you have any evidence that I have broken policy? No you have not. Do you have any evidence that I am the originally asserted users? No you do not. This is a sloppy attempt to fish, no better than the first, and should be seen for that. YINever 03:56, 5 June 2006 (UTC)[reply]

This concerns the issue because RFCU is to show ALL the sockpuppets of User:YINever. And it is clear that TJive is already a sockpuppet of YINever. And here is where suspected sockpuppet of User:YINever, violated the 3RR. [6] I suspect the other accounts/IP are also sockpuppets of User:YINever. --RevolverOcelotX 04:12, 5 June 2006 (UTC)[reply]
Can a administrator check to see if those accounts/IPs are the sockpuppet of User:YINever? --RevolverOcelotX 04:29, 5 June 2006 (UTC)[reply]

 Clerk note: Having two accounts is discouraged but not prohibited, unless they edit disruptively together. TJive has not edited The Epoch Times. A checkuser request to see if YINever has used additional accounts (such as Freereader or Web Spy Killer) will be performed at the discretion of one of the admins with checkuser permission, but it may take a couple of days. (All the clerks can do is keep things tidy.) This is not the right place for an extended discussion. Thanks. Thatcher131 04:34, 5 June 2006 (UTC)[reply]

 Inconclusive This seems to be a fishing expedition, but without much in the way of live bait. Freereader and Webspykiller are the same user, but there is no connection that I can see between TJive/YINever. Thatcher131 is correct; sockpuppetry in itself, while discouraged, is permitted provided that the streams don't cross. Mackensen (talk) 12:26, 5 June 2006 (UTC)[reply]

The above discussion is preserved as an archive of the Request for checkuser. Please do not modify it.
Subsequent requests related to this user should be made below, in a new section.


If you are creating a new request about this user, don't forget to edit this section and add
{{Wikipedia:Requests for checkuser/Case/YINever}}
The previous request (shown above), and this box, will be automatically hidden on Requests for checkuser (it will still appear here).