Wikipedia:Arbitration/Requests/Enforcement

From Wikipedia, the free encyclopedia



Wuerzele

Blocked for 1 week for TBAN violations. GoldenRing (talk) 09:21, 18 August 2017 (UTC)
The following discussion has been closed. Please do not modify it.

This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.
Requests may not exceed 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

Request concerning Wuerzele

User who is submitting this request for enforcement 
Kingofaces43 (talk · contribs · deleted contribs · logs · edit filter log · block user · block log) 19:52, 13 August 2017 (UTC)
User against whom enforcement is requested 
Wuerzele (talk · contribs · deleted contribs · logs · edit filter log · block user · block log)

Search DS alerts: in user talk history • in system log

Sanction or remedy to be enforced
Wikipedia:Arbitration/Requests/Case/Genetically_modified_organisms#Wuerzele_topic_banned :
Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it 
  1. Aug 3 Editing article within topic ban.
  2. Aug 3 Edit warring previous content back after seeing their content was removed (with the edit summary notice).
  3. Aug 11 Combative talk page comments after WP:GOODFAITH reminder of ban rather than coming straight here.
Diffs of previous relevant sanctions, if any 
  1. Sept 2015 Blocked by Bbb23 for edit warring in GMO topics
  2. Dec 2015 Topic-banned in GMO and pesticide topics by ArbCom
If discretionary sanctions are requested, supply evidence that the user is aware of them (see WP:AC/DS#Awareness and alerts)
  • Mentioned by name in the Arbitration Committee's Final Decision linked to above.
Additional comments by editor filing complaint 

This is a bit of an odd case. Wuerzele was one of the more problematic editors in GMO and pesticide topics, and was topic-banned in the initial ArbCom case. They violated their topic ban awhile ago, but that AE was closed by EdJohnston because Wuerezele immediately stopped editing for a few days once the report was made and didn't respond to the AE. The close also included a note that the case could be reopened if Wuerzele returned and issues were still coming up.

The diffs above are another set of topic ban violations. They came to Fipronil, an insecticide page which unambiguously falls within the topic ban, and started making edits. I reverted reminding them that they are topic banned, only to have them edit war the content they inserted back in. I also left a reminder at their talk page about the topic ban and that I was assuming they had forgotten rather than me filing an AE case (probably should have come here instead due to the edit warring in retrospect instead of the good faith assumption).

At this point, they stop editing for a few days immediately after they were called out on their topic ban again, just like the previous AE, so no case was filed until this weekend when they responded to my talk page notice rather vehemently (rather than deleting it due to their ban as I pointed out). I originally was going to let this slide as I mentioned on their talk page, but Wuerzele was topic banned in large part due to battleground behavior focused towards myself and a few others in the topic that's rearing its head in their comments. We also have a trend of Wuerzele avoiding administrative action by not editing for a few days after a topic ban violation, so I figured even if an admin wants to call this stale, it's better to have a continued record for future reference with the last AE in mind. Kingofaces43 (talk) 19:52, 13 August 2017 (UTC)

Just a note Drmies on the WP:NOBAN related comment, but that specifically excludes administrative notices due to noticeboards, etc. I made it clear to Wuerzele they would have been getting an AE notice instead if I hadn't initially gone the good-faith route and renotified them of their topic ban just in case. The complaint at the talk page is rather silly in that sense given the then other option, but that kind of battleground escalation is why the topic ban was put in place. Had I posted more than what I did, that definitely would have gone outside the spirit of WP:NOBAN. Kingofaces43 (talk) 05:21, 15 August 2017 (UTC)
Drmies, I didn't intend my reply above as interpreting you had a quarrel with my notification, so sorry if it came across that way. I was more so just clarifying the situation on that notification since you brought it up. Situations like that have history of being taken out of context by others in this topic if not clarified (thankfully things have settled for the most part though). Kingofaces43 (talk) 21:36, 15 August 2017 (UTC)
Notification of the user against whom enforcement is requested 

[1]

Discussion concerning Wuerzele

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by Wuerzele

Statement by Doc James

They have been an abrasive editor.[2] They have been involved with edit warring [3]. I feel this is a wider concern than just the breach of their restriction. Doc James (talk · contribs · email) 20:35, 13 August 2017 (UTC)

Result concerning Wuerzele

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
  • These look like pretty obvious tban violations to me. @Wuerzele: do you have any explanation for these edits? GoldenRing (talk) 09:21, 14 August 2017 (UTC)
    • How long do we leave this open for? According to X!, this user is usually very active on Sundays and weekdays ([4]) yet they've disappeared since Saturday, when all this blew up. It's looking increasingly like a duck-and-dive to avoid sanctions. @Wuerzele: If we don't hear back in 48 hours from now, at least with some idea when you'll be able to respond fully, I intend to take action on this. GoldenRing (talk) 09:21, 15 August 2017 (UTC)
    • If anyone else wants to act, they're free to do so. For the minute, I don't see a problem letting this sit another day so long as they don't resume editing elsewhere. I agree that if there's no response then we're in for a longish block. GoldenRing (talk) 13:20, 16 August 2017 (UTC)
  • I agree with GoldenRing. I might could let that talk page comment slide--perhaps they did ban Kingofaces from their talk page, and on one's own talk page one typically gets some leeway, but a topic ban violation is a topic ban violation. Wuerzele, much will depend on your answer here. Drmies (talk) 16:30, 14 August 2017 (UTC)
    • GoldenRing, do it. As far as I'm concerned 24 hours is enough. Drmies (talk) 15:06, 15 August 2017 (UTC)
    • Kingofaces, I think you misunderstood me: I have no quarrel with you or your notification; my point was about their response. Please note, BTW, how cleverly I let us have our cake and eat it too. :) We do need Wuerzele to respond quickly or things will end up poorly for them. Drmies (talk) 15:23, 15 August 2017 (UTC)
  • I don't think it even needs a response. These are obvious TBAN violations, and Wuerzele's response was basically "if you don't like it, go to AE". I would be looking at quite a significant block here. Black Kite (talk) 21:41, 15 August 2017 (UTC)
  • Since Wuerzele is banned from both GM organisms and agricultural chemicals generally, their edits of Fipronil violate the ban. There don't seem to be any extenuating circumstances, and Wuerzele's absence from this discussion doesn't count in their favor. So I would support a one-week block for violating the TBAN. EdJohnston (talk) 02:18, 18 August 2017 (UTC)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Arbitration/Requests/Enforcement&oldid=796800999"
This content was retrieved from Wikipedia : http://en.wikipedia.org/wiki/Wikipedia:Arbitration/Requests/Enforcement
This page is based on the copyrighted Wikipedia article "Wikipedia:Arbitration/Requests/Enforcement"; it is used under the Creative Commons Attribution-ShareAlike 3.0 Unported License (CC-BY-SA). You may redistribute it, verbatim or modified, providing that you comply with the terms of the CC-BY-SA