Jump to content

Wikipedia:Arbitration/Requests/Enforcement/Archive234

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Timotheus Canens (talk | contribs) at 20:14, 1 June 2018 (OneClickArchiver adding Waleswatcher). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Arbitration enforcement archives
1234567891011121314151617181920
2122232425262728293031323334353637383940
4142434445464748495051525354555657585960
6162636465666768697071727374757677787980
81828384858687888990919293949596979899100
101102103104105106107108109110111112113114115116117118119120
121122123124125126127128129130131132133134135136137138139140
141142143144145146147148149150151152153154155156157158159160
161162163164165166167168169170171172173174175176177178179180
181182183184185186187188189190191192193194195196197198199200
201202203204205206207208209210211212213214215216217218219220
221222223224225226227228229230231232233234235236237238239240
241242243244245246247248249250251252253254255256257258259260
261262263264265266267268269270271272273274275276277278279280
281282283284285286287288289290291292293294295296297298299300
301302303304305306307308309310311312313314315316317318319320
321322323324325326327328329330331332333334335336337338339340
341342343344345346347348349350351352353

SPECIFICO

Netoholic (talk · contribs) is warned not to use administrative boards to further disputes on Wikipedia. TonyBallioni (talk) 04:06, 24 May 2018 (UTC)[reply]
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 SPECIFICO

User who is submitting this request for enforcement
Netoholic (talk · contribs · deleted contribs · logs · filter log · block user · block log) 22:44, 22 May 2018 (UTC)[reply]
User against whom enforcement is requested
SPECIFICO (talk · contribs · deleted contribs · logs · filter log · block user · block log)

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

Sanction or remedy to be enforced
WP:ARBAPDS, specifically Discretionary sanctions guidelines involving decorum and expectation to follow guidelines such as WP:HOUNDING, WP:BLUDGEONING, WP:ASPERSIONS :
Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
  • 16:14 21 May - tag-team, snap-revert within 5 minutes, reverting my revert of a WP:BOLD removal of a well-cited section, with no intervening discussion on his part.
    • 16:17 post-revert reply to my talk page post.
  • 20:49 22 May - "copy edit" which substantially alters/revert the lead, an edit made shortly after I made a reply to someone else on the talk page about a compromise change to the lead at 20:26.
Diffs of previous relevant sanctions, if any
  1. 20 May 2018 warned by TonyBallioni (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) " reminding you of the behavioral standards expected of Wikipedia editors, and warning that not following them in the future will likely lead to sanctions."
If discretionary sanctions are requested, supply evidence that the user is aware of them (see WP:AC/DS#Awareness and alerts)
  • Previously given a discretionary sanction for conduct in the area of conflict on
  • Alerted about discretionary sanctions in the area of conflict in the last twelve months, see the system log linked to above.
  • Participated in an arbitration request or enforcement procedure about the area of conflict in the last twelve months, on numerous occasions
Additional comments by editor filing complaint

In just over two days since the close of an AE request I made regarding SPECIFICO (Wikipedia:Arbitration/Requests/Enforcement/Archive232#SPECIFICO) up to my notice on his talk page about this HOUNDING, he had made 36 edits total, at least 17 of those (47%) were spent reverting me, replying to my comments on talk pages, and mentioning me by name - often within moments - and never making overtures toward congeniality, but filled with insistent, WP:BATTLEGROUND "This is how it is" attitude. I'm sure he'll have some reasonable explanation for individual actions, and some were naturally part of mutual exchanges, but his overall focus on me and lack of effort to try other areas of work to avoid it is undeniable. This sort of activity was the case even before the other AE, also, but I've limited my diffs to after he received his logged warning to show a pattern of reprisal. When I brought this to his attention, he was dismissive, and instead continued to repeat a claim that I reverted a page move he did. After several times telling him he was mistaken, and even showing diff proof that it was someone else who moved it, SPECIFICO has not acknowledged his mistake. My feeling is that he is not adhering to the warning given, and is pursuing an effort designed to confound my interactions with other editors based on a mistaken belief in a perceived wrong that is provably incorrect. The prior logged warning seems to have fallen on deaf ears. -- Netoholic @ 22:44, 22 May 2018 (UTC)[reply]

I don't think this relates much with the User:Factchecker atyourservice AE going on, except perhaps as a concrete, time-limited example of SPECIFICO's style of BATTLEGROUND tactics. This is strictly covering SPECIFICO's behavior within 2 days of receiving a warning about expectations of behavior, which one would assume he would do everything to at least initially avoid such scrutiny. Yet, I detect no change in his approach, no remorse, and no acknowledgement of the problem. -- Netoholic @ 00:12, 23 May 2018 (UTC)[reply]

If I had to point to one action which I feel especially clear about his behavior, its the 20:49 22 May - "copy edit" above. I had reached an amicable solution with another editor, then SPECIFICO almost immediately crushed that section to dust under the misleading edit comment "copy edit". He didn't inform the talk page of his intentions. To my mind, it felt like he couldn't stand seeing any minor agreement or cooperation taking place, so he salted the earth. -- Netoholic @ 04:36, 23 May 2018 (UTC)[reply]

To editor Sandstein: - The section of my diffs labeled "Various" is included just to demonstrate my statement that 47% of his recent edits have been directed at me. Take for example this AfD, 4 editors have voted "Keep", but SPECIFICO has only directly replied to my vote comment. I do not reciprocate. I do not direct comments at him unless its a reply to something he said to me or mentioned me in. I keep quite busy across the project. In this same timespan I've created a new article of about 11k characters. I've continued my participation in WP:RM. But I do want to provide input on the main article the diffs are from, and when I do, I want to interact with a variety of other editors there. I do not deserve to be singled out by SPECIFICO and challenged on -everything-. When deciding on HOUNDING, ask yourself this:

  • When given the opportunity, does SPECIFICO specifically seek to interact with me over others? Yes.
  • When given the opportunity to do anything but interact with SPECIFICO, do I? Yes.

-- Netoholic @ 07:10, 23 May 2018 (UTC)[reply]

To any of the admins. You may close this at anytime. Though my intent was in good faith, based on the responses, I now know better when and how its appropriate to use the available conflict resolution venues. You can be assured I have no intent on using this one again regarding this editor. -- Netoholic @ 03:53, 24 May 2018 (UTC)[reply]

Notification of the user against whom enforcement is requested
given


Discussion concerning SPECIFICO

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 SPECIFICO

I think I responded adequately to Netoholic's concern before he filed this complaint. The thread is here [1] I was surprised then to see him file shortly thereafter. Please note that Netoholic's assertion that I failed to correct my error concerning his opposition to my page move is incorrect. As can be seen in the history log, I struck and corrected it 90 minutes before he filed this complaint (immediately after I checked the relevant diffs). That thread was his second visit to my talk page in the two days since his earlier AE complaint was closed. The first one is here [2] SPECIFICO talk 00:08, 23 May 2018 (UTC)[reply]

For the sake of completeness, in case editors review this file in the future and especially if they've not seen last week's similar complaint, I am providing this link to show the "user interactions" between me and Netoholic over the past 2 years. [3] As can be seen, in 10 of the 13 overlaps, Netoholic's edits followed mine. And one of those pages was Stefan Molyneux where he was violating the TBAN imposed by the community in 2014. Previously, he had appeared to be recruiting me to Molyneux' teachings. [4], for which he was blocked [5].

I don't think any IBAN is needed so long as the record is clear so that this matter need not be relitigated in the future. For my part, I think we can move on now. SPECIFICO talk

Statement by Objective3000

I suggest the filer read WP:PETARD and withdraw the complaint before it's too late. O3000 (talk) 23:03, 22 May 2018 (UTC)[reply]

Statement by Tryptofish

I've been editing in some of these topic areas recently (example), and I think that this filing should be understood as being in the same "series" as the one just above, about Factchecker-atyourservice. I can confirm that Specifico has been uncivil some of the time, but there's a lot of it going around. And there is some aspect of boomerang here. I don't know if AE can really handle it or whether there needs to be yet a third ArbCom case, but there probably do have to be a rather large number of topic bans. --Tryptofish (talk) 23:27, 22 May 2018 (UTC)[reply]

Statement by MrX

I have to agree with Objective3000 here. A gentle boomerang might be in order. From where I observe, it seems that Netoholic may be pursuing a grudge against SPECIFICO. For example, this comment is uncalled for. A similar comment directed at another editor: [6] Perhaps Netoholic should be reminded that Wikipedia is not a battleground.- MrX 🖋 23:31, 22 May 2018 (UTC)[reply]

Statement by Lionelt

Several behavioral policy violations have been lodged against SPECIFICO relating to the Political views article. Netoholic has presented 17 diffs in support of HOUNDING and BLUDGEONING allegations. While these edits look suspicious, it is difficult to determine if these edits are evidence of violations or merely the result of normal editing. Regarding the allegation of ASPERSIONS it does appear that SPECIFICO corrected the error. At this time I cannot recommend sanctions against SPECIFICO.

Some editors have suggested BOOMERANG against Netoholic. This is outrageous. It is unconscionable to threaten an editor in good standing with sanctions for bringing a issue to the attention of the community in good faith. With a limited admin corps we depend on editors to help control disruption and maintain civility and to attack these editors is counterproductive and a violation of AGF. BOOMERANG threats without conclusive evidence in the form of diffs should be treated as a personal attack WP:NPA "Accusations about personal behavior that lack evidence. Serious accusations require serious evidence. Evidence often takes the form of diffs and links presented on wiki." – Lionel(talk) 04:22, 23 May 2018 (UTC)[reply]

Statement by Moxy

It's discouraging to see lagitamate complaints so easily dismissed. What people are looking for here is dispute resolution or a rationale as to why.... not a slap in the face. Wikipedia has a behavioral problem and we expect our elected officials to to act and respond in a common sense manner.--Moxy (talk) 05:13, 23 May 2018 (UTC)[reply]

Statement by Geogene

I've read Netoholic's diffs. They establish that there's an ongoing content dispute, but fail to demonstrate any behavioral issue. No, if you want to see behavioral issues--Netoholic personalizing the dispute--see MrX's diffs. I wouldn't say that those are heinous, either, but they tend to raise doubts about Netoholic as a force for civility in the dispute.

I agree with Objective3000 and others that the question is whether this should close with a boomerang for Netoholic or not. That boomerang would probably be an informal warning from an admin about using AE for BATTLEGROUND ends. Geogene (talk) 05:27, 23 May 2018 (UTC)[reply]

Statement by JFG

Nothing to see here. All editors should be advised to cut the drama down a notch. — JFG talk 06:12, 23 May 2018 (UTC)[reply]

Statement by NorthBySouthBaranof

This is the second time in three days that Netoholic has attempted to have someone who has opposed their edits sanctioned through an administrative process; just the other day Netoholic filed an unfounded AN3RR case against me for reverting a block-evading sockpuppet on an article that Netoholic had neither edited nor engaged in any talk page discussion at any time, meaning the only reason for them to file the sanction request was to "punish" me for disagreeing with them on other articles. I suggest that Netoholic should engage those he perceives to be his "opponents" in good-faith discussion rather than poorly-supported and time-wasting sanctions requests. NorthBySouthBaranof (talk) 07:19, 23 May 2018 (UTC)[reply]

Statement by (username)

Result concerning SPECIFICO

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
  • This doesn't look actionable to me. The diffs presented here look by and large like the result of normal editing and discussing content issues. Certainly SPECIFICO expresses clear views about some of the questions at issue, but these views appear to relate to the content being discussed, rather than to other editors themselves. Sandstein 06:06, 23 May 2018 (UTC)[reply]
  • If there is any "hounding" going on, it's more likely this unsubstantiated report by Netoholic rather than any of the reported edits by SPECIFICO. I could see this being closed with a warning to Netoholic not to use the AE process in a battleground-like manner. Sandstein 06:09, 23 May 2018 (UTC)[reply]
  • I see nothing really actionable here. I see a content dispute, and the types of comments that typically accompany that on a politically-charged article, but nothing actionable. There's the start of BATTLEGROUND behavior all around, but not at a point where AE would need to be placed down, only cautioning all sides to watch themselves. --Masem (t) 14:04, 23 May 2018 (UTC)[reply]
  • I concur with Sandstein, and would support a logged warning not to abuse the AE process. TonyBallioni (talk) 14:25, 23 May 2018 (UTC)[reply]
  • Editors involved in this area need to consider if they really want an AP3 Arbcom case where the remedies could boil down to "a pox on both your houses". If not, all sides may want to keep that possibility in mind while reading over their talk page posts and requests for AE three times before clicking "Publish changes". --NeilN talk to me 14:35, 23 May 2018 (UTC)[reply]
  • This complaint is not in itself frivolous, but following so close on the last it might be thought to be so. The edits are not actionable. The complaint might be, at least in as much as an interaction ban may be worth considering. Guy (Help!) 14:38, 23 May 2018 (UTC)[reply]
  • Having clicked on every single diff presented by Netoholic, I agree with the consensus here that this request is unfounded and is not actionable. In the context described above by Sandstein, and in light of the fact that Netoholic has been blocked at least once previously for harassing SPECIFICO (scroll up near the top of this mammoth block log), I would support a logged warning to Netoholic about abusing administrative processes. MastCell Talk 00:15, 24 May 2018 (UTC)[reply]

Waleswatcher

No action but Waleswatcher advised to review the expectations for editing in this area. --NeilN talk to me 14:15, 25 May 2018 (UTC)[reply]
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 Waleswatcher

User who is submitting this request for enforcement
Springee (talk · contribs · deleted contribs · logs · filter log · block user · block log) 01:17, 22 May 2018 (UTC)[reply]
User against whom enforcement is requested
Waleswatcher (talk · contribs · deleted contribs · logs · filter log · block user · block log)

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

Sanction or remedy to be enforced
Wikipedia:Arbitration/Requests/Case/Gun_control :

Discretionary sanctions related to firearms articles. Link to DS warning on user page [[7]]

Talk pages showing DS notice Talk:AR-15_style_rifle

Talk:Colt_AR-15 - This page does not have a DS warning.

Relevant policies, guidelines wp:Disruptive editing, WP:consensus, in particular WP:NOCONSENSUS and wp:forumshop

With respect to disruptive editing,

1. Is tendentious: continues editing an article or group of articles in pursuit of a certain point for an extended time despite opposition from other editors. Tendentious editing does not consist only of adding material; some tendentious editors engage in disruptive deletions as well. An example is repeated deletion of reliable sources posted by other editors.

And

4. Does not engage in consensus building:
a. repeatedly disregards other editors' questions or requests for explanations concerning edits or objections to edits;
b. repeatedly disregards other editors' explanations for their edits.

And

5. Rejects or ignores community input: resists moderation and/or requests for comment, continuing to edit in pursuit of a certain point despite an opposing consensus from impartial editors.
Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

Disruptive editing via failure to follow WP:BRD

  1. Apr 5: The editor’s edits in the firearms space was a BRD failure involving a very significant reordering of the text of the AR-15 style rifle page [[8]] (Apr 5th). I restored the original order which was quickly reverted with a comment that I was the one who needed to get consensus to undo the bold change [[9]]
  2. Apr 28: Next edit war use of “assault weapon” [[10]] (28 Apr) during active talk page discussion [[11]]. Re-reverting text to a non-consensus version while the talk page is active isn’t Bold, it’s WP:RECKLESS.
  3. May 12: Active discussion regarding the article lead ["many"_in_lead] Editor makes wp:reckless change to lead (12 May)[[12]]. (18 May)I revert the change. Editor restores [[13]] Back and fourth (myself included) results in 3 day article lock. Talk page discussion still active. 34 hours after lock expires I restored the old stable text per WP:NOCON. Editor reverts claiming the article was stable for a week thus new consensus version.[[14]] Actually less than 6 days and the article was locked most of that time. WW's revert was reverted by another editor. ~2 days later WW restored their version claiming consensus based on an optimistic reading of consensus (20 May).[[15]] Most recently WW reverted an editor claiming another editor claimed consensus.
there is a consensus as per K.e.coffman above. It is you and other opposed editors that are being disruptive in preventing it from being implemented.[[16]]
  1. May 12: Adds material to a subsection of the article (12 May, same morning as above BRD failure). [[17]]. I revert. Editor restores without going to talk page[[18]]. Finally goes to talk page [[19]] Finally informal survey starts [[20]]. Survey results in 10:10 non-consensus. Editor refuses to accept no consensus. Threatens to make nearly identical changes to article.[[21]]
By the way, if we cannot reach a consensus in favor of my version (right now its 11-9 against, so doesn't look promising), I intend to simply copy the lead from AR-15 style rifle into this section, as per WP:SYNC.[[22]]
Unless there are actual substantive objections (beyond "that's not the way I want it"), I will go ahead and do that as per WP:SYNC. [[23]]
There's nothing disruptive about that. It would be standard WP:BRD - except that I'm announcing what I'm intending to do (and why) in advance so it can be discussed, which makes it more careful (and less bold) than wiki standard. Now, do you care to comment on substance, or are you going to continue to be tendentious? [[24]]
The editor was cautioned by another editor who generally agreed with Waleswatcher’s editorial POV [[25]]. Acting anyway is WP:TEND
After 20 editors just weighed in on the discussion, editor suggests a new RfC to get their way.
OK, thanks. In that case I'll start an RfC or village pump discussion on this specific question: [[26]]
Anyway, when I get around to it I will take this to a larger audience at the village pump, so there's not much point in continuing to discuss it here now.[[27]]
  1. May 16: Forumshoping. Against the advice of others an RfC at the Village Pump (not the article page) was created. It immediately closed down as wp:FORUMSHOP and being non-neutral (16 May).["AR-15_style_rifle"_of_the_article_"Colt_AR-15"_to_the_lead_of_its_parent_article], ["Should_the_section_Colt_AR-15#AR-15_style_rifle_be_a_copy_of_the_lead_of_AR-15_style_rifle"?]
  1. May 14: WP:CIVIL Quoting, thus highlighting a swype error and then refusing to allow a simple correction.[[28]] This got admin attention [[29]]. I believe this would be a violation of both Direct Rudeness (d)belittling and by highlighting an erroneous Swype correction and other uncivil behaviors (e)quoting another editor out of context ... to malign them
If discretionary sanctions are requested, supply evidence that the user is aware of them (see [[30]])
Notification of the user against whom enforcement is requested

User notification [[31]] Springee (talk) 01:19, 22 May 2018 (UTC)[reply]

Update

While Waleswatcher's behavior may not have crossed any deep red lines above the disruptive editing and failure to respect WP:CONSENSUS policies continues. Here WW asked an admin if the "stable" version of an article was one that was unchanged after being unlocked for less than 36 hours [[32]]. The question went unanswered so WW decided to violate WP:NOCONSENSUS by restoring the new version of the text. The edit summary was misleading. Yes, the text was discussed on the talk page but at 4:4 their is no consensus to change the lead. This change, especially after asking an admin for advice is WP:RECKLESS and disruptive. Springee (talk) 13:42, 23 May 2018 (UTC)[reply]


Discussion concerning Waleswatcher

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 Dlthewave

Point #1 requires context to fully understand. It consists of moving the "Use in crime and mass shootings" section from near the bottom of the article to near the top.

18:06 4 April 2018 by Waleswatcher re-ordered sections to reflect importance, general interest, and the content of the lede

18:56 4 April 2018 by Springee Undid revision 834303022 by Waleswatcher (talk) please get consensus first.

20:25 4 April 2018 by Waleswatcher Undid revision 834308982 by Springee (talk) "Getting consensus" is not necessary for an edit on wikipedia. Rather, you should get consensus to undo. Please do not start an edit war. Use in crime and mass shootings is obviously more important than the modularity of the rifle, as is born out by the fact that one is discussed in the lede and the other not.)

Please get consensus first - I'm not sure how Waleswatcher was supposed to respond to or discuss this, as Springee didn't raise any objections to the content. Waleswatcher's reply (via edit summary) isn't exactly helpful either, but it certainly doesn't look like Springee was engaging in BRD. This looks more like an attempt to require a talk page proposal before making an edit. –dlthewave 03:09, 22 May 2018 (UTC)[reply]

Statement by Mr rnddude

I am involved here, and I am also the individual who suggested this venue in preference to AN/I. If you're wondering why the venue move, feel free to do a Ctrl+F search of Archive 983 of AN/I for any one of Waleswatcher, Springee or anybody who has posted a comment at Talk:AR-15 style rifle or Talk:Colt AR-15. There's been a spot of bother, you might notice. I'm also editorially involved over at those two articles ... or rather became involved recently ... because I looked at AN/I.

I'll post a comment here on my observations of Waleswatcher first. There's a couple of things that are obvious to me from them: a) they are a newbie and b) they are engaging in a crusade (whether this is a serious pet issue, or just the result of push back I don't know or care to comment). I have personally stayed out of the actual articles, so will comment only on things said on the talk page.

I'll assume that the newbie comment will confuse some given the ostensible ten years of having an account, so to start, please keep this comment in mind: In my defense, it's not as though wiki policies and guidelines and venues and RfCs and VPPs and ANIs are so easy to navigate.... It flies directly in the face of numerous other comments "educating" the other involved editors on policies and guidelines ranging from consensus to summary style, but it's rather apparently true.
Let me expound on an example:
By the way, if we cannot reach a consensus in favor of my version (right now its 11-9 against, so doesn't look promising), I intend to simply copy the lead from AR-15 style rifle into this section, as per WP:SYNC. Their defence of this was that SYNC cannot be ignored, but they later changed their defence to There's nothing disruptive about that. It would be standard WP:BRD - except that I'm announcing what I'm intending to do (and why) in advance so it can be discussed, which makes it more careful (and less bold) than wiki standard. In the next breath they suggested that I was being tendentious: Now, do you care to comment on substance, or are you going to continue to be tendentious? I highlight all of this to make a simple statement: these are poor readings, understandings, and intended applications of any of the policies cited and also of others not brought up.
I'm also going to point out that they don't understand involved editing, and don't really care to consider the opposition in any detail: e.g. this comment which is, I suggest rather generously, an inadequate summary of the opposition comments. Of course, that is caused by their demands to satisfy, which are both annoying, and non-collaborative. It also results in the erroneous belief that what is actually disruptive editing, is either standard BRD or proper editing etiquette. Indeed, that much can be surmised from dlthewave's third diff which is moving onus onto those who disagree (or dispute).
Waleswatcher has also received a softly worded warning from NeilN for forum shopping for a discussion they started at the village pump. Refer to this thread at Talk:Colt AR-15.

This is a bit jumbled and quickly put together, but it should cover many of the issues that have arisen from Waleswatchers' participation. I'm not going to advocate anything in particular, but will suggest that Waleswatcher needs their course corrected soon (ASAP). I haven't commented on anyone else's behaviour yet, though I might soon enough. There's a couple things that have given me pause, but nothing comparable to the above. Mr rnddude (talk) 05:12, 22 May 2018 (UTC)[reply]

Sandstein would it suffice to point out that multi-party revert wars are a trend on AR-15 style rifle? Oshwah added admin protection to the article on May 13 to expire on May 16 after one set of edit-warring. A small edit-war broke out on May 18: First dispute Special:diff/841832337 and Special:diff/841835054, second dispute Special:diff/841843969, Special:diff/841856554 and Special:diff/841864230. Then the same dispute happened on May 20: Special:diff/842174926, Special:diff/842207275, Special:diff/842221331, Special:diff/842294023, and Special:diff/842364766. That's 10 reverts total, 8 of which are about one set of 938 bytes. Mr rnddude (talk) 12:01, 22 May 2018 (UTC)[reply]

Statement by (slaterstven)

Both the filer and the accused have been up before ANI for various issues (in relation to this subject area), I am not sure either party is any more innocent then the other.Slatersteven (talk) 12:05, 22 May 2018 (UTC)[reply]

Statement by Waleswatcher

I have to object to Springee’s notification for this. Last night I saw the alert "you have new messages", but looking at my talk page I didn't see any change, so I discounted it. Looking at my talk page history I now see what happened - Springee deleted their previous comment on my talk page, which was a notification of another complaint that they opened and then closed later, and replaced it with this nearly identical new notice.

The only reason I found this at all is I thought it was odd I was messaged but there was nothing there. Had anyone else posted on my talk page around the same time, I might never have noticed. Rather than deleting content on someone else's talk page, why not leave the old notification, or at least add a note saying what they had done? It's just another example of how Springee interacts with me (and maybe others).

I'll respond at length later. Waleswatcher (talk) 13:13, 22 May 2018 (UTC)[reply]


General comment - in the ten years I have edited wikipedia I have only rarely been involved in contentious pages like these, and I freely admit that I am not very familiar with the dispute resolution process. I think it’s a problem that there is such a complex thicket of guidelines, policies, etc. The resulting wikilawyering creates a formidable barrier for entry and it makes it easy for editors experienced in these venues to force out editors they don’t like. This is probably the wrong venue to discuss that (indicative of the problem - I have no idea what the right venue is) but I thought it was worth mentioning as it’s fully in play in these articles.

Regarding the principles I'm accused of violating:

1. Is tendentious: continues editing an article or group of articles in pursuit of a certain point for an extended time despite opposition from other editors. Tendentious editing does not consist only of adding material; some tendentious editors engage in disruptive deletions as well. An example is repeated deletion of reliable sources posted by other editors.

In my experience this describes many editors on these gun-related pages. In particular, it describes Springee. A look at their history shows that they have been "editing an article or group of articles in pursuit of a certain point for an extended time despite opposition from other editors" - where “extended time” is several years in their case. This includes the deletion of reliable sources posted by me and other editors, for instance here, here, and here.

As for me, I’ve been editing these articles since last month. I do in fact hold the opinion that some of these articles should contain more information regarding mass shootings than they certainly do, and there is clearly opposition to that view. When I first started looking at them, I was puzzled by the lack of information in that regard. I'm far from the only one, even the international media has noticed this: Also see this, where Springee is mentioned by name.

Next: 4. Does not engage in consensus building: a. repeatedly disregards other editors' questions or requests for explanations concerning edits or objections to edits; b. repeatedly disregards other editors' explanations for their edits.

I think it was my repeated requests for explanations that were disregarded, not the other way around. I tried to engage and find a compromise version but could hardly get any of the opposed editors to state what their objections were (in fairness, Springee was far from the worst in this). I do admit to feeling pretty frustrated by this attitude. Rather than discuss the content of my edits, their response was to revert because of lack of consensus, and then demand I achieve consensus before restoring the edit. But when trying to achieve consensus, most of the responses were complaints about BRD etc. rather than about the substance of the edit. As a result, every proposed edit devolved into a deadlock.

Added later: here's an example. Waleswatcher (talk) 14:49, 22 May 2018 (UTC)[reply]

5. Rejects or ignores community input: resists moderation and/or requests for comment, continuing to edit in pursuit of a certain point despite an opposing consensus from impartial editors.

See above. It seems to me I was the one requesting comments and being ignored.

I’m not going to respond to every specific point as this is already too long. I'll just make a few comments.

Regarding edit warring, note that Springee reverted AR-15 style rifle three times in 24 hours (06:28, May 12, 2018, 13:35, May 12, 2018, and 13:56, May 12, 2018). I am guilty of reverting twice that day. 72bikers brought an ANI complaint against me for those reverts, which was dismissed since it clearly didn't violate 3RR.

Regarding the forum shopping/VPP incident, I believed that the issue I (tried to) raise on VPP was sufficiently different that it merited a new discussion. The discussion on the talk page was regarding specific text I proposed to add to Colt AR-15#AR-15 style rifle, while on VPP the proposal was that that section be permanently WP:SYNCed to the lead of AR-15 style rifle, regardless of what was there or if it changed later. I thought (and still think) that would be a mechanism to help cut down on these disputes, since at least they could focus on AR-15 style rifle rather than both articles. I should have proposed that first, rather than proceeding as I did. I acknowledge I made a mess there, and I already apologized (and do so again now - I handled that incorrectly, sorry about that).

Regarding my “threats” to edit here: I said what I intended to do on the talk page (which was different from what we had been discussing, or at least I thought so - see above). I got a lot of opposition, I listened to it, and as a result I never made the edit.

Regarding the typo, Springee edited both their comment and my response. Editing my comment (and theirs after it was responded to) is a clear (if minor) violation of wiki's talk page guidelines WP:TPO (where it says "Never edit or move someone's comment to change its meaning, even on your own talk page.", bold in the original). It annoyed me because I did not recognize that it was a typo when I responded (“clear lake of support” read as a rather poetic if non-standard phrase, and I was in a rush). Their edit changed the flavor of my response and I didn't like that, so I reverted. Their next edit showed as a revert of my revert, so I reverted that too and put a warning regarding WP:TPO on Springee's user page (by the way I don’t think this is a big deal; I'm responding only because Springee raised the issue). Waleswatcher (talk) 13:53, 22 May 2018 (UTC)[reply]

One other comment: I did reach out to two admins for help on this here and here. Neither responded - which is totally understandable for any number of reasons, I'm not blaming them, just pointing out that I asked for guidance in how to handle these disputes before it came to this. Waleswatcher (talk) 14:03, 22 May 2018 (UTC)[reply]

Statement by (username)

Result concerning Waleswatcher

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
  • This is an underwhelming report. WP:BRD is not a community-adopted conduct policy or guideline and therefore, in my view, not something we can enforce here. The "lake"/"lack" issue is a minor matter that doesn't require arbitration enforcement. Unless this report is rewritten to indicate clearly which, if any, actual conduct guidelines or policies are violated, i wouldn't take action here. Sandstein 07:43, 22 May 2018 (UTC)[reply]