Wikipedia:Requests for checkuser/Case/Zeumic
From Wikipedia, the free encyclopedia
[edit] Zeumic
| main edit links history watch Filed: 20:11, 25 March 2008 (UTC) |
- Zeumic (talk • contribs • logs • block user • block log • checkuser)
- Wikifactsright (talk • contribs • logs • block user • block log • checkuser)
- Code letter: G
- Supporting evidence:
A particularly disruptive and accusative user has surfaced on the Geoffrey Edelsten article, as well as on Talk:Geoffrey Edelsten and other venues in an attempt to have any negative content of the page removed. He has been blocked today for 3RR and had engaged in considerable forum shopping, and is wasting a considerable amount of community time. Based on the very similar content being introduced to the article by Zeumic on the same article late last year (I would link diffs but they're deleted ones - see Special:DeletedContributions/Zeumic, there's under 15), and the fact both seem to be exclusively dedicated to this article, I believe there is a reasonable possibility that these users are the same and think this check is warranted. Orderinchaos 20:11, 25 March 2008 (UTC)
Additional information needed As Zeumic is not currently editing, I am inclined to decline. Assuming it is true, how would this change your approach to the editor? What would you/could you do if it was confirmed that you can't do otherwise? Thatcher 20:52, 25 March 2008 (UTC)
- Zeumic (Edelsten's web development and promotions company [1] [2]) had a confirmed conflict of interest with regards to the article. If the two users are in fact the same person, it would be possible to deal with the new user's contributions using the conflict of interest guideline. Orderinchaos 22:31, 25 March 2008 (UTC)
Confirmed. Thatcher 04:13, 26 March 2008 (UTC)
- Both blocked per OTRS Ticket # 2008032810002283 for the length of that ticket (if it successfully resolves, I will lift the block). I think we all know what that implies. ⇒SWATJester Son of the Defender 13:24, 28 March 2008 (UTC)
Subsequent requests related to this user should be made above, in a new section.

