Jump to content

User:Jéské Couriano/ArbCaseSum/24-present

From Wikipedia, the free encyclopedia

How to read the sections

[edit]
  • Decided: The calendar date (in UTC) when the case was decided. If the case did not reach a decision, it will be Closed instead. If the case involved an administrator "retiring", it will be "Deopped" instead.
  • Abbrev.: A shorthand abbreviation of the casename. See ArbCaseAbv for more details.
  • Type: The type of case it is:
  • Admin: A case centred around the conduct of one or more administrators.
  • Dispute: A case that examines an intractible dispute between two or more editors directly.
  • Editor: A case about the (non-administrative) misconduct of an editor.
  • Functionary: A case centred around misuse of Suppressor or Checkuser permissions.
  • Omnibus: A case about misconduct in a topic area writ large.
  • Other: Any case that doesn't fall into one of the categories above.
  • Scope: The overall scope of the case.
  • CT?: An indication of whether or not a case includes or included a discretionary sanctions or contentious topic remedy.
  • Remedy name: The name of the remedy (or a description of it, for earlier cases which did not have sectioned remedies).
  • Remedy (in modern terms): Basically my best attempt to explain, in plain English and modern understanding, what the remedy means.
  • If this section has a coloured background, the colour indicates its status or origin:
  • Yellow (#FFFF00) is a temporary injunction issued mid-case.
  • Blue (#00BFFF) is a post-close amendment or motion.
  • Red (#CD5C5C) is a remedy that has since been rescinded or otherwise is wholly reliant on previous remedies that are themselves rescinded.
  • Green (#32CD32) is a remedy whose wording was amended post-close, either due to an amendment/motion or due to changes in process (such as Discretionary Sanctions to Contentious Topic).
  • Brown (#D2691E) is suspended or in abeyence, usually as part of a period where a remedy has been appealed.
  • Amended/Enacted: If a remedy was added or amended post-close, this will be the calendar date (in UTC) when the remedy was modified or took effect.
  • Rescinded: If a remedy was terminated, this will be the calendar date (in UTC) when the remedy was ended.
  • Enforceable?: Indicates whether a given remedy can be invoked at WP:AE. Any remedy that predates April 2006 and was not still in force by then predates AE entirely.
  • Sup/Opp/Abs/Rcs: The vote totals for a remedy (Support, Oppose, Abstain, Recused).

Any case that has been courtesy-blanked or closed without action will be given a very brief description and nothing further.

2024

[edit]
  • Decided: Apr. 13, 2024
  • Abbrev.: COI
  • Type: Admin/Editor
  • Scope: Nihonjoe's undisclosed conflicts of interest and actions taken to further it and a related block on Fram for posting personally-identifying information
  • CT?: No
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
New VRT queue established The paid-en-wp mailing list (used exclusively by Checkusers to investigate conflict of interest matters) is wound down. In its place, a new Volunteer Responce Team queue is created, staffed by functionaries (Checkusers/Suppressors) and administrators who have signed the same privacy documents and undergone an appointment process similar to what functionaries have. Any cases from the queue, particularly credible [conflict-of-interest reports] involving an administrator, may be referred to ArbCom at the discretion of those answering the queue. N/A 11 0 0 2
Fram admonished Fram is admonished for exposing personally-identifying information repeatedly and told in no uncertain terms the next time he does so will be grounds for a summary Arbitration siteban. No 6 5 0 2
Nihonjoe: removal of permissions Nihonjoe's administrator and bureaucrat rights are revoked. He may only regain them through new successful Requests for Adminship/Bureaucratship. N/A 10 0 0 2

Sri Lanka

[edit]
  • Closed: Apr. 20, 2024 (motion)
  • Abbrev.: SrL

(Case resolved via motion in lieu of a full case; no case page exists. Sri Lanka is declared a contentious topic.)

Mzajac

[edit]
  • Deopped: May 07, 2024

(Case closed with a desysop after a three-month abeyance period due to Mzajac quitting Wikipedia to evade the Arbitration.)

  • Decided: May 24, 2024
  • Abbrev.: VZP
  • Type: Dispute
  • Scope: NoonIcarus' and WMrapids's fighting in the Venezuelan politics topic area
  • CT?: No
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
WMrapids banned WMrapids, who was Checkuser-blocked during the case, is indefinitely sitebanned. They may appeal this annually. Yes 8 1 0 0
WMrapids topic banned Assuming they're ever unbanned, WMrapids is indefinitely topic-banned from the Venezuelan politics topic area, broadly construed. They may appeal this annually. Yes 8 0 1 0
Interaction ban NoonIcarus and WMrapids are indefinitely under a mutual interaction ban. Either party may appeal this annually.
(The main point of this remedy is to force NoonIcarus to stop taking shots at WMrapids.)
Yes 10 0 0 0
  • Decided: Sep. 13, 2024
  • Abbrev.: HE
  • Type: Editor
  • Scope: Off-wiki canvassing and harassment campaigns around elections articles
  • CT?: Close - current (Remedy)
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Contentious Topic (with sunset) Provided the person being sanctioned has been alerted to the existence of this remedy, any administrator may summarily sanction a user who disrupts articles and discussions about concluded national and subnational elections (hence "the HE area") as they see fit. Any sanctions or warnings issued this way (both directly and consequentially) must be logged on the case page/centralised log and can only be appealed to WP:Arbitration/Requests/Enforcement or to ArbCom directly. (See WP:Contentious topics for more details.) This remedy will automatically lapse if, starting on Jan. 1 2026, it has not been invoked for a two-year period. Yes 5 3 0 0
Election Twitter reminded The Xitter group known as Election Twitter is told they cannot force changes to articles by angry mob; they have to get consensus for their changes and go thru content dispute resolution like everyone else. No 8 0 0 0
Talleyrand6 (site ban) Talleyrand6 - who had been indefinitely blocked prior to the case and had their block confirmed by ArbCom - has that block converted to a de jure Arbitration siteban. They may appeal this annually. Yes 8 0 0 0
Anonymousioss (topic ban) Assuming they are ever unbanned, Anonymousioss is indefinitely topic-banned from the HE area. They may appeal this annually once their siteban has been dispensed with. Yes 7 0 0 0
Anonymousioss (site ban) Anonymousioss is indefinitely sitebanned. They may appeal this annually. Yes 5 3 0 0
CroatiaElects (topic ban) Assuming they are ever unbanned, CroatiaElects is indefinitely topic-banned from the HE area. They may appeal this annually once their siteban has been dispensed with. Yes 7 0 0 0
CroatiaElects (site ban) CroatiaElects is indefinitely sitebanned. They may appeal this annually. Yes 6 1 0 0
DemocraticLuntz (topic ban) DemocraticLuntz is indefinitely topic-banned from the HE area. They may appeal this annually. Yes 5 1 1 0
Mcleanm302 (topic ban) Assuming they are ever unbanned, Mcleanm302 is indefinitely topic-banned from the HE area. They may appeal this annually once their siteban has been dispensed with. Yes 6 0 0 0
Mcleanm302 (site ban) Mcleanm302 is indefinitely sitebanned. They may appeal this annually. Yes 6 0 0 0
Remedy name Remedy (in modern terms) Enforceable? Sup Opp Abs Rcs
Contentious topic (Yasuke) Provided the person being sanctioned has been alerted to the existence of this remedy, any administrator may summarily sanction a user who disrupts articles and discussions about Yasuke and his samurai status (hence the "YSK area") as they see fit. Any sanctions or warnings issued this way (both directly and consequentially) must be logged on the case page/centralised log and can only be appealed to WP:Arbitration/Requests/Enforcement or to ArbCom directly. This remedy will automatically lapse if, starting on Jan. 1 2026, it has not been invoked for a two-year period. Yes 8 0 1 0
Yasuke 1RR restriction For the next year, all editors on Yasuke are under 1RR, independent of any discretionary sanctions levied under the contentious topic. Yes 9 0 0 0
Eirikr (topic ban) Eirikr is indefinitely banned from the YSK area. They may appeal this annually. Yes 9 0 0 0
Symphony Regalia (topic ban) Symphony Regalia " " " " " ". " " " " ". One Arbitrator voting for the ban noted Symphony Regalia had already been banned from GS, and another commented that issues in multiple contentious topics is by itself grounds for further, more sitebanny, sanctions. Yes 9 0 0 0
J2UDY7r00CRjH (topic ban) J2UDY7r00CRjH " " " " " " ". " " " " ". Yes 9 0 0 0
Yvan Part (topic ban) Yvan Part " " " " " " ". " " " " ". Yes 9 0 0 0
Gitz6666 (warned) Gitz6666 is warned that if they continue their misbehaviour, they will attract stiffer sanctions as a consequence. No 8 0 1 0
Interaction ban (one-way) Elinruby is indefinitely under a one-way interaction ban from Gitz6666. They may appeal this annually. Yes 7 0 2 0
Case renamed The committee directs the clerks to rename the case to Yasuke [from "Backlash to diversity and inclusion"].
The Arbitrators initially began the case as a means of looking to expand GG's (now GS's) contentious topic authorisation, as the right-wing diversity, equity, and inclusion backlash was seen as an expansion/complement to the sex-based GamerGate. All evidence provided, however, was laser-focused on the situation at Yasuke, giving them nothing to work with when it comes to expanding the GS CT. A last-minute attempt at including a second contentious topic designation for diversity and inclusion as it related to video games failed at the 11th hour (4/5/0/0).
N/A 7 1 1 0