Jump to content

Wikipedia:Arbitration/Requests/Clarification and Amendment: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Line 76: Line 76:
::{{ping|SoWhy}} It should be the job of ArbCom to demonstrate the correct usage, rather than reinforce common misconceptions (thus promoting further confusion on this matter), and your comments are therefore not befitting your status as a member of the committee. You might consider reading the [[User:RGloucester/Sanctions|history of sanctions on Wikipedia as written by myself]], or perhaps consulting the creator of the term 'general sanctions' himself, former committee member [[User:Kirill Lokshin|Kirill Lokshin]]. In either case, I would advise that you refrain from making such mistakes in future. [[User:RGloucester|<span style="font-family:Monotype Corsiva;font-size:12pt;color:#000000">RGloucester </span>]] — [[User talk:RGloucester|☎]] 14:19, 4 August 2021 (UTC)
::{{ping|SoWhy}} It should be the job of ArbCom to demonstrate the correct usage, rather than reinforce common misconceptions (thus promoting further confusion on this matter), and your comments are therefore not befitting your status as a member of the committee. You might consider reading the [[User:RGloucester/Sanctions|history of sanctions on Wikipedia as written by myself]], or perhaps consulting the creator of the term 'general sanctions' himself, former committee member [[User:Kirill Lokshin|Kirill Lokshin]]. In either case, I would advise that you refrain from making such mistakes in future. [[User:RGloucester|<span style="font-family:Monotype Corsiva;font-size:12pt;color:#000000">RGloucester </span>]] — [[User talk:RGloucester|☎]] 14:19, 4 August 2021 (UTC)
:::{{ping|SoWhy}} Your continued reference to the 500/30 rule as a 'DS' is indeed a mistake, and a grave one coming from a committee member. Committee-authorised DS are governed by [[Wikipedia:Arbitration Committee/Discretionary sanctions]], a policy maintained by the committee itself. You might notice that none of the rules mentioned in the AC/DS policy page apply to the 500/30 rule as it is implemented anywhere. The most obvious example of this is that no alert is required to enforce a 500/30 rules, unlike for DS. It's simply a flat rule, like a page restriction. If you, as a committee member, are not even aware of how your own policies work, can you really be fit to adjudicate these matters? I wonder. This matter is relevant in this case, because the confusion that caused this unnecessary incident of stress for a number of veteran editors was directly caused by the failure on the part of ArbCom to establish consistent rules and use a consistent terminology than everyone can understand. Continuing to be obstinate, insisting that 500/30 is a 'DS', despite all evidence to the contrary, is really nothing more than appalling. [[User:RGloucester|<span style="font-family:Monotype Corsiva;font-size:12pt;color:#000000">RGloucester </span>]] — [[User talk:RGloucester|☎]] 15:23, 4 August 2021 (UTC)
:::{{ping|SoWhy}} Your continued reference to the 500/30 rule as a 'DS' is indeed a mistake, and a grave one coming from a committee member. Committee-authorised DS are governed by [[Wikipedia:Arbitration Committee/Discretionary sanctions]], a policy maintained by the committee itself. You might notice that none of the rules mentioned in the AC/DS policy page apply to the 500/30 rule as it is implemented anywhere. The most obvious example of this is that no alert is required to enforce a 500/30 rules, unlike for DS. It's simply a flat rule, like a page restriction. If you, as a committee member, are not even aware of how your own policies work, can you really be fit to adjudicate these matters? I wonder. This matter is relevant in this case, because the confusion that caused this unnecessary incident of stress for a number of veteran editors was directly caused by the failure on the part of ArbCom to establish consistent rules and use a consistent terminology than everyone can understand. Continuing to be obstinate, insisting that 500/30 is a 'DS', despite all evidence to the contrary, is really nothing more than appalling. [[User:RGloucester|<span style="font-family:Monotype Corsiva;font-size:12pt;color:#000000">RGloucester </span>]] — [[User talk:RGloucester|☎]] 15:23, 4 August 2021 (UTC)

=== Statement by François Robere ===

If ArbCom wishes to maintain its relevancy and keep the Wikipedia community active and vibrant, it needs to stop dealing in minutae and start putting its foot down. APL is bleeding editors and admins, people complain about their blood pressure and mental health (!), vandalism is an almost daily occurrence, and you're arguing about ''namespaces''? What are you, the [[IETF]]? There are so many things that you could do to fix this, and instead you're putting your finger in the dike. [[User:François Robere|François Robere]] ([[User talk:François Robere|talk]]) 16:24, 4 August 2021 (UTC)


=== Statement by {other-editor} ===
=== Statement by {other-editor} ===

Revision as of 16:24, 4 August 2021

Requests for clarification and amendment

Clarification request: Antisemitism in Poland

Initiated by Wugapodes at 02:21, 4 August 2021 (UTC)[reply]

Case or decision affected
Antisemitism in Poland arbitration case (t) (ev / t) (w / t) (pd / t)

List of any users involved or directly affected, and confirmation that all are aware of the request:

Confirmation that all parties are aware of the request

Statement by Wugapodes

The 30/500 remedy of the antisemitism in Poland case is unclear on whether it applies to namespaces beyond (Article). The decision states that non-EC editors are prohibited from editing articles and further states that non-EC editors may use the Talk: namespace to discuss improvements. However, this differs from the other 30/500 scheme imposed by ARBPIA. In that topic area, editors are prohibited from editing content and editing talk pages is listed as an explicit exception to the general prohibition in all namespaces. This inconsistency between the two has led to confusion among administrators and editors. The Volunteer Marek and GizzyCatBella reverted a non-EC editor who was editing antisemitism in Poland content in project space. The editors stated that those reverts were not edit warring as they enforced the 30/500 restriction which they believe applied to all namespaces. Ymblanter blocked them both on the basis of the remedy text, believing that the 30/500 remedy applied only to mainspace. Clarification on this point would help avoid future miscommunications and conflict.

Statement by Ymblanter

I am under understanding that if the arbitration decision says "article" and not "page" it means "article" and not "page". Which makes perfect sense to me because for example talk pages should not be included in any case, and concerning Wikipedia namespace, the pages there do not obey the same policies as the articles, for example WP:V or WP:N do not apply to the same extent. It is of course up to ArbCom to modify the wording if they wish to do so.

To correct the original statement, GCB reverted a long-standing editor; VM first edit was a revert of a long-standing editor (although the edit they were reverting stood on the page for about two years); the other three reverts were indeed of a non-extended-confirmed editor.

What we also need is to clarify, similarly to PIA situation, is whether new accounts may edit articles which are not primarily related to antisemitism in Poland but contain some pieces or even sentences related to antisemitism in Poland. My proposal would be to state that new accounts are not allowed to make any edits to any articles if the edit is related to antisemitism in Poland, but I believe it is not currently stated clearly in the remedy.--Ymblanter (talk) 05:24, 4 August 2021 (UTC)[reply]

Note that I discussed the above interpretation of the remedy with VM after I blocked them (it was then called wikilawyering), and also in the ANI thred where it was completely ignored.--Ymblanter (talk) 09:38, 4 August 2021 (UTC)[reply]

Statement by Volunteer Marek

In addition to the wording at ARBPIA, the WP:GS page which references the general 30/500 rule also says "content". Full text for completeness [1]:

Under the 30/500 rule, all IP editors, and accounts with fewer than 500 edits and with less than 30 days' tenure are prohibited from editing content within a given area of conflict. It can be enforced through the use of extended confirmed protection (ECP) or other methods, including page protection, reverts, blocks, the use of pending changes, and appropriate edit filters. Reverts made solely to enforce the 30/500 rule are not considered edit warring. Editors who are not eligible to be extended-confirmed may use the Talk: namespace to post constructive comments and make edit requests related to articles within the topic area, provided they are not disruptive. Talk pages where disruption occurs may be managed by any of the methods noted above. This exception does not apply to other internal project discussions such as AfDs, WikiProjects, RfCs, noticeboard discussions, etc. Editors who are not eligible to be extended-confirmed may not create new articles, but administrators may exercise discretion when deciding how to enforce these remedies on article creations.

I bolded the parts where there's some difference. This means that the restriction on non-confirmed users editing "AfDs, WikiProjects, RfCs, noticeboard discussions" are EVEN MORE stringent than regular articles and article talk pages. One recurring problem since this amendment was put in place is of masses of sock puppet showing up to RfCs and brigading them. And making exceptions for RfCs does create a loophole - a friend of a banned user creates an RfC, then the banned user swarms the RfC with socks and it's really a lot of effort to file SPIs on all of them.

Of course, aligning the Poland-specific restriction with WP:GS and ARBPIA would also eliminate the sort of confusion that led to the recent drama. Volunteer Marek 02:34, 4 August 2021 (UTC)[reply]

Statement by GizzyCatBella

- Unquestionably I would urge to include:

AfDs, WikiProjects, RfCs, and noticeboard discussions

due to enormous sock puppet activity in these sectors. - GizzyCatBella🍁 03:58, 4 August 2021 (UTC)[reply]

This is a great example since it just happens as we speak.[2]. Brand new account, reactivated after 2 years of inactivity, shows up in support of the banned user's entry. Please note that this is a daily occurrence in this topic area. - GizzyCatBella🍁 10:54, 4 August 2021 (UTC) And of course, there is a correlation in other articles between the short-lived account and the banned user[3] but who has the energy to file an SPI report every day? - GizzyCatBella🍁 11:08, 4 August 2021 (UTC)[reply]

Statement by Zero0000

The current rules for ARBPIA are working pretty well, so replicating them here would be a safe and effective option. Zerotalk 03:13, 4 August 2021 (UTC)[reply]

Statement by Levivich

I also think there is no real reason to dice it up so finely as to distinguish between pages and articles, which we usually don't do for topic restrictions (like 50/300 in PIA, TBANs, etc.). So I'd support an amendment to change "articles" to "pages". There's the wrinkle about content (portions of pages, such as is the case for the page in question here), but I think the best policy is to say non-EC editors can make edit requests on article talk pages and otherwise can't participate anywhere else. Levivich 03:29, 4 August 2021 (UTC)[reply]

Statement by Lepricavark

I agree with Levi that there's no need to "dice it up." If unexperienced editors and socks are a major problem on these articles, they aren't likely to be a net positive in the other namespaces. LEPRICAVARK (talk) 04:12, 4 August 2021 (UTC)[reply]

Statement by Piotrus

On one hand I am hesitant to deny 'free speech' to anyone, on the other I can confirm that Icewhiz's associated LTAs have been active in some non-article spaces. This started already in 2019 with Wikipedia:Articles for deletion/About the Civilization of Death (an AFD of a rant written by Icewhiz; just look at it - almost all 'votes' are crossed out, socks everywhere). This pattern continues in AfDs, RfCs and like in this TA - above normal numbers of SPAs, IPs, and like are a norm. However, per my 'free speech' concerns, I'd suggest not removing them, but instead, votes by such accounts should be clearly labeled in some fashion. Maybe revise the cited remedy to note that votes and comments by such editors in this topic area should be considered as having less weight than those of normal editors, and encourage usage of templates such as {{Single-purpose account}}. {{csp}}, {{csm}}, {{Afdnewuser}} and like. Could also consider creating a new template to be used in this topic area instead of the new linked, linking to the revised remedy. --Piotr Konieczny aka Prokonsul Piotrus| reply here 04:37, 4 August 2021 (UTC)[reply]

Statement by ProcrastinatingReader

Since the WP:GS page has been brought up a few times now at ANI and in SoWhy's comment: that text was only meant to be descriptive of what ArbCom's general remedies are. It was taken from the ARBPIA remedy, I believe. You can parse it for this context by taking "articles related to the history of Jews and antisemitism" to be the "given area of conflict". Otherwise, that text has no enforcement basis at all. There are three 500/30s authorised here:

  • In Israel-Palestine, with this definition
  • In Antisemitism in Poland, with this definition
  • For conflicts between India and Pakistan, with this definition

There exists no authorisation that uses the informational text at WP:GS. (I proposed removing it last year to avoid confusion but that didn't gain consensus.)

As for the scope of the remedy, I feel like it's little things like this that makes the general sanctions regimes appear complicated. This is the only one of three authorisations to limit to "mainspace". I think extending the scope for simplicity's sake is worth it alone, given that the covered content in other namespaces is almost certainly very low (both relatively and absolutely). The collateral damage will also be insignificant compared to the collateral damage already caused by having this restriction in mainspace.

I do believe VM thought in good faith it applied to the given page, given that all other remedies are across all namespaces, and a plausible explanation is that ArbCom made the common error of using "articles" and "pages" as synonyms. It's very much possible the distinction wasn't even noticed on a first read - I certainly didn't notice it on my first read, but then again I just skimmed over it as I presumed it was identical to the boilerplate text elsewhere. ProcrastinatingReader (talk) 09:27, 4 August 2021 (UTC)[reply]

Statement by RGloucester

  • @SoWhy: Just a point of clarification, but you seem confused about the meaning of the terms 'general sanctions' and 'discretionary sanctions'. General sanctions are a broad class of remedies that can be imposed by either ArbCom or the community. The reason they are called 'general' is because they apply to a whole topic area, rather than specific editors. Discretionary sanctions are a specific type of general sanction (other types include revert restrictions and article probation). The 500/30 rule is most patently not a 'discretionary sanction', but a type of general sanction. Discretionary sanctions have very specific rules, as described at WP:AC/DS. In any case, I agree that the text at the information page is in no way binding on ArbCom, and should be clarified to reflect the possibility of specific implementation in specific cases. RGloucester 12:46, 4 August 2021 (UTC)[reply]
@SoWhy: It should be the job of ArbCom to demonstrate the correct usage, rather than reinforce common misconceptions (thus promoting further confusion on this matter), and your comments are therefore not befitting your status as a member of the committee. You might consider reading the history of sanctions on Wikipedia as written by myself, or perhaps consulting the creator of the term 'general sanctions' himself, former committee member Kirill Lokshin. In either case, I would advise that you refrain from making such mistakes in future. RGloucester 14:19, 4 August 2021 (UTC)[reply]
@SoWhy: Your continued reference to the 500/30 rule as a 'DS' is indeed a mistake, and a grave one coming from a committee member. Committee-authorised DS are governed by Wikipedia:Arbitration Committee/Discretionary sanctions, a policy maintained by the committee itself. You might notice that none of the rules mentioned in the AC/DS policy page apply to the 500/30 rule as it is implemented anywhere. The most obvious example of this is that no alert is required to enforce a 500/30 rules, unlike for DS. It's simply a flat rule, like a page restriction. If you, as a committee member, are not even aware of how your own policies work, can you really be fit to adjudicate these matters? I wonder. This matter is relevant in this case, because the confusion that caused this unnecessary incident of stress for a number of veteran editors was directly caused by the failure on the part of ArbCom to establish consistent rules and use a consistent terminology than everyone can understand. Continuing to be obstinate, insisting that 500/30 is a 'DS', despite all evidence to the contrary, is really nothing more than appalling. RGloucester 15:23, 4 August 2021 (UTC)[reply]

Statement by François Robere

If ArbCom wishes to maintain its relevancy and keep the Wikipedia community active and vibrant, it needs to stop dealing in minutae and start putting its foot down. APL is bleeding editors and admins, people complain about their blood pressure and mental health (!), vandalism is an almost daily occurrence, and you're arguing about namespaces? What are you, the IETF? There are so many things that you could do to fix this, and instead you're putting your finger in the dike. François Robere (talk) 16:24, 4 August 2021 (UTC)[reply]

Statement by {other-editor}

Other editors are free to make relevant comments on this request as necessary. Comments here should opine whether and how the Committee should clarify or amend the decision or provide additional information.

Antisemitism in Poland: Clerk notes

This area is used for notes by the clerks (including clerk recusals).

Antisemitism in Poland: Arbitrator views and discussion

  • Could someone post a link to the page history in question? Thanks, Barkeep49 (talk) 02:42, 4 August 2021 (UTC)[reply]
    In reading through the ANI I found the link to the page history in question: Wikipedia:List of hoaxes on Wikipedia. Barkeep49 (talk) 02:55, 4 August 2021 (UTC)[reply]
    • I think SoWhy does an excellent job of laying out why the DS applies only to articles at the moment. I will think more on whether I would support a change. That said, as there has now been activity about the underlying issue not only at the project page but the article itself since this request has been underway I would strongly suggest all editors, but in particular Levivich, Piotrus, and Volunteer Marek continue their discussion on the Wikipedia hoax talk page rather than continuing to edit (war) about this. Barkeep49 (talk) 12:38, 4 August 2021 (UTC)[reply]
  • Unless there have been previous interpretations to the contrary, I would hold that the Antisemitism in Poland remedy as it stands now only applies to mainspace. ("articles" means mainspace unless the context demands a different interpretation.) However, I'm quite open to modifying the remedy. Best, KevinL (aka L235 · t · c) 04:22, 4 August 2021 (UTC)[reply]
  • I'm of the same opinion as Kevin. The remedy is quite clear, it's referring to articles only - and I believe from the votes there was a bit of reluctance at the time to put in a 30/500 restriction at all, so it makes sense that the committee wished it to be as narrow as possible. I'd prefer not to extend it, for similar reasons, but if there are still issues happening regularly in the project space, I'd be open to modification. WormTT(talk) 08:22, 4 August 2021 (UTC)[reply]
  • When the restriction was passed, NYB (with whom I agreed) reluctantly supported the specific wording out of necessity. The wording was deliberately chosen to only apply to the mainspace. That other cases imposed other DS on other areas is of no relevance. Hence there is nothing to clarify beyond the clear wording of the motion. If a change is required, that can be requested but it needs to be a different request with proof that further restrictions are warranted. For the purposes of this request however, I would argue that Ymblanter acted within their rights to block VM and GCB since the claimed edit-warring exception did not apply to the page in question (VM even quoted the remedy's text verbatim when justifying their revert [4]). Pointing to the wording in WP:GS does not mitigate this fact since we are not talking about community imposed general sanctions but ArbCom imposed discretionary sanctions. Even if, a more restrictive remedy would imho always be override a more general policy page. Otherwise, there would be no way for ArbCom to tailor remedies to specific circumstances. Regards SoWhy 08:43, 4 August 2021 (UTC)[reply]
    @RGloucester: I agree the terms are a bit confusing. GS is usually used to refer to community imposed sanctions while ArbCom imposed sanctions are usually only referred to as DS. The recent example of WP:GS/COVID-19 and the discussion at Wikipedia:Arbitration/Requests/Case/COVID-19 comes to mind, especially the point that "general sanctions are hereby rescinded and are replaced by standard discretionary sanctions" in the motion at WP:COVIDDS. As the discussion about that case request and the motions reveals, most people use "GS" to mean community sanctions, not all sanctions. Regards SoWhy 13:00, 4 August 2021 (UTC)[reply]
    @RGloucester: Usage of terms can change over time. That Kirill had a certain idea when he created the page 14 years ago(!) does not mean that the term still has the same meaning today nor that he has some kind of "power" to define what the term means today. As I pointed out, a significant number of people nowadays see general sanctions as a synonym for community-approved sanctions (which is why for example templates like {{subst:Gs/alert}} use the abbreviation "Gs" despite explicitly only applying for community-sanctions). I don't think any further discussion of "mistakes" in usage is helpful though. I see your point that this has led to some confusion in general, however, I don't see any of that applying in this specific case where the language of the DS in question was clear and the question whether DS are a part of GS or something separate is not of any relevance afaics. Regards SoWhy 15:04, 4 August 2021 (UTC)[reply]