Content deleted Content added

Inline

Revision as of 10:28, 8 January 2019

Main case page (Talk) — Evidence (Talk) — Workshop (Talk) — Proposed decision (Talk)

Case clerk: TBD Drafting arbitrator: TBD

Purpose of the workshop

Arbitration case pages exist to assist the Arbitration Committee in arriving at fair, well-informed decisions. The case Workshop exists so that parties to the case, other interested members of the community, and members of the Arbitration Committee can post possible components of the final decision for review and comment by others. Components proposed here may be general principles of site policy and procedure, findings of fact about the dispute, remedies to resolve the dispute, and arrangements for remedy enforcement. These are the four types of proposals that can be included in committee final decisions. There are also sections for analysis of /Evidence, and for general discussion of the case. Any user may edit this workshop page; please sign all posts and proposals. Arbitrators will place components they wish to propose be adopted into the final decision on the /Proposed decision page. Only Arbitrators and clerks may edit that page, for voting, clarification as well as implementation purposes.

Expected standards of behavior

You are required to act with appropriate decorum during this case. While grievances must often be aired during a case, you are expected to air them without being incivil or engaging in personal attacks, and to respond calmly to allegations against you.
Accusations of misbehaviour posted in this case must be proven with clear evidence (and otherwise not made at all).

Consequences of inappropriate behavior

Editors who conduct themselves inappropriately during a case may be sanctioned by an arbitrator or clerk, without warning.
Sanctions issued by arbitrators or clerks may include being banned from particular case pages or from further participation in the case.
Editors who ignore sanctions issued by arbitrators or clerks may be blocked from editing.
Behavior during a case may also be considered by the committee in arriving at a final decision.

Motions and requests by the parties

Proposed temporary injunctions

Questions to the parties

Arbitrators may ask questions of the parties in this section.

Analysis of evidence

Place here items of evidence (with diffs) and detailed analysis

GiantSnowman use of rollback

GiantSnowman used the rollback tool to revert edits that should not have been reverted:

verbatim

#	Date	Instances	User reverted
1A	03 December 2018	25	Jamieroot11 (talk · contribs)
1B	27 November 2018	41	Cipow (talk · contribs)
1C	29 November 2018	26	Davidstockholm (talk · contribs)
1D	04 December 2018	416	Veryproicelandic (talk · contribs)

The conduct exhibited in 1) breached our Editing policy:

verbatim

Instead of removing article content that is poorly presented, consider cleaning up the writing, formatting or sourcing on the spot, or tagging it as necessary
— WP:EDIT#Try to fix problems

Users are not expected to undo edits without being sure they are problematic.

Sports biographies are plagued by hoax updates (see evidence by Iridescent). Administrators are justified in paying increased attention to these topic areas, and indeed regarding unverified information with a healthy degree of skepticism.
No misconduct was exhibited in the below evidence submissions:

verbatim

#	Evidence by	User reverted	Notes
4A	Fram	Footballinbelgium (talk · contribs)

I have stopped reviewing specific instances of rollback (or mass rollback) by GiantSnowman, because the pattern seems clear enough to be getting on with. I may update further beyond 1D and 4A at a later time. AGK ■ 13:54, 3 January 2019 (UTC)[reply]

Comment by Arbitrators:

Analysis posted; comments welcome. AGK ■ 13:54, 3 January 2019 (UTC)[reply]

Comment by parties:

Any reason you don't put the name of whoever provided the evidence with the bits of evidence you believe to be correct, but you do put the name of the person adding the evidence with the one bit you believe to be incorrect (without providing any justification to either?). Seems a bit strange. The vast majority of edits by Fotballinbelgium in that rollbacked streak were correct and sourced, a few seem to have been mistakes though. Are one or two mistakes amnog many correct edits justification for rollback? Fram (talk) 09:59, 4 January 2019 (UTC)[reply]

Comment by others:

@AGK: Do not forget GS rollback against WR227 Hhkohh (talk) 14:02, 3 January 2019 (UTC)[reply]

GiantSnowman comprehension of conduct concerns

Initially, GiantSnowman's position was that reverting valid additions to the encyclopedia is acceptable in the course of reverting unacceptable edits:

verbatim

I acknowledge that I have previously used the massrollback script to revert editors, and that has sometimes caught up good faith edits and editors. However my use of rollback is allowed by #5 of WP:ROLLBACKUSE
— User:GiantSnowman
— Wikipedia:Arbitration/Requests/Case/GiantSnowman/Evidence#Rollback

Later, GiantSnowman departed from that position and accepted the concerns:

verbatim

I've already acknowledged that my use of mass rollback was inappropriate in relation to a few users, although (again) at the time I thought it was all kosher and inline with WP:ROLLBACKUSE
— User:GiantSnowman
— Wikipedia:Arbitration/Requests/Case/GiantSnowman/Evidence#Proving a negative

Elaborating on this departure, GiantSnowman demonstrated a misunderstanding of the concerns as being about mass rollbacking – rather than rollbacking as such:

verbatim

Yes, there will be many examples of me using mass rollback and reverting good faith edits […] such as addition of unsourced content about BLPs which turned out to be correct or good-faith removals of infoboxes […] I thought that such use was allowed per #5 of WP:ROLLBACKUSE. I was told at ANI it was not, I apologised and self-reverted, I stopped using it, and I uninstalled the script. Are there ongoing problems? No.
— User:GiantSnowman
— Wikipedia:Arbitration/Requests/Case/GiantSnowman/Evidence#Response to UninvitedCompany

GiantSnowman has consequently addressed concerns about rollbacking strictly as assisted by the massRollback.js script. However, the concerns more broadly related to all use by GiantSnowman of the rollback permission.

I will deal with the "regular" rollback tool in a further section. AGK ■ 16:12, 3 January 2019 (UTC)[reply]

Comment by Arbitrators:

Analysis posted; comments welcome. AGK ■ 16:12, 3 January 2019 (UTC)[reply]

There have been concerns raised, for example by Dweller [1], that it is not so much the tool that is the concern but the actual reverts - that due care and diligence appears to be lacking when GiantSnowman reverts (regardless of how he reverts), such as this revert of me [2] while I was still actively editing, and when the source for the reverted information was present in the article and was supporting the same information in the infobox (that the player had appeared 27 times and scored one goal for a club). SilkTork (talk) 10:27, 8 January 2019 (UTC)[reply]

Comment by parties:

His conduct concerns are also about vandalism warnings and blocks for good faith, constructive edits. Fram (talk) 10:00, 4 January 2019 (UTC)[reply]

And, as can be seen in my evidence, your second point is inaccurate, he even blocked an editor for a good edit during this case, and his comments about other blocks show no change in approach or understanding for most of the problems, only for the mass rollback when a formal sanction seemed imminent. Fram (talk) 10:42, 5 January 2019 (UTC)[reply]

Comment by others:

If an admin is repeatedly lack of comprehension, he cannot become an excellent admin Hhkohh (talk) 07:10, 4 January 2019 (UTC)[reply]

GiantSnowman motivation for reverts

(A) Since this case opened

Since the commencement of this case, GiantSnowman has constrained his reverting to edits about a sports personality, team, or club.
GiantSnowman tends to revert changes or updates to a point of fact, usually in an {{infobox}}. Edits reverted by GiantSnowman include unverified changes to:
- number of appearances
- whether they are signed or a free agent
- number of goals scored
In most cases, the user failed to provide a citation or allow for verification. On Wikipedia, readers must be able to check the information in an article is not falsified, misremembered, or estimated. Any statement "whose verifiability is challenged or likely to be challenged" must reference a reliable, published source (WP:V#Responsibility for providing citations).

(B) Prior to this case opening

Prior to the commencement of this case, GiantSnowman frequently reverted edits to topics other than sports.
Reverting unverified changes about a sports personality is defendable conduct. Wikipedia policy is clear: encyclopedia content must be verifiably accurate.
However, GiantSnowman's edits have not been confined to reverting unverified edits to sports pages. GiantSnowman has also reverted edits to non-sports pages. Many, but not all, of these reverts were collateral damage from the mass rollback script.
It does not escape the committee's notice that users remain on "best behaviour" while at arbitration. Several essays in the userspace, indeed, recommend doing so. The committee will not necessarily give less weight to GiantSnowman's conduct prior to this case (versus conduct after the case was opened).

Regarding the last sentence in B6 – how many reverts were "deliberate" rollbacks, rather than collateral damage from massRollback.js? AGK ■ 17:00, 3 January 2019 (UTC)[reply]

Comment by Arbitrators:

Analysis prepared; comments welcome. AGK ■ 17:00, 3 January 2019 (UTC)[reply]

@GS, I've edited this analysis section for clarity (it was unclearly worded). The point was that you've reverted on non-sports pages; eg [3]. AGK ■ 19:45, 3 January 2019 (UTC)[reply]

Comment by parties:

@AGK: - I'm interested how you have come to the conclusion that "Since the commencement of this case, GiantSnowman has constrained his reverting to edits about a minor sports personality, team, or club [...] Prior to the commencement of this case, GiantSnowman frequently reverted edits to topics other than sports personalities"? I edit in the same area I always have, as far as I am aware...perhaps you could kindly clarify? Giant Snowman 19:02, 3 January 2019 (UTC)[reply]

Yes, I have - though the edit you highlighted was part of a mass rollback revert (hence why I have suggested use of the script and use of 'normal' rollback are considered separately). I noticed the editor in question removing infoboxes from footballer articles. Giant Snowman 20:45, 3 January 2019 (UTC)[reply]

@AGK and UninvitedCompany: and, as I have already explained on the Evidence page (and talk page!), that was the reversion of a sock per WP:BLOCKEVASION/WP:DENY. Rollback is allowed for that per #4 of WP:ROLLBACKUSE. Giant Snowman 17:20, 4 January 2019 (UTC)[reply]

Comment by others:

@AGK: - I had placed this example in evidence where, after the commencement of the case, GiantSnowman reverted a change that included an inline citation to a valid source that, upon review, appeared to support the edit that was reverted. This was a manual revert, not one using the mass rollback tool. GiantSnowman claimed it is justified, post hoc, on the case pages, based on WP:SOCK, but I don't believe there's any material evidence that suggests that the reverted content was anything other than a good-faith edit. Please consider updating your analysis. Uninvited Company 17:14, 4 January 2019 (UTC)[reply]

GiantSnowman use of blocks

In the last three months (since 1 October), GS has blocked about 29 editors (excluding sock blocks, which I haven't looked at). While a fair number of those were justified and uncontroversial, at least 6 of those were incorrect blocks. This includes one block made during this case (User:107.77.173.7). Fram (talk) 10:55, 5 January 2019 (UTC)[reply]

GS continues to defend these blocks, e.g. his 3 month block of User:WR227, who added sourced facts to 25 articles, but forgot to include the source (named in the edit summary) to the article in one instance. For the block of User:121.212.176.113, they stated "In the edit highlighted by Fram, the IP was seemingly changing sourced content. It was fair to revert and view as vandalism." This was the edit in question, which changed an incorrect statement and thus improved the article. For the block made during the case, they stated " I simply saw an editor making a large number of vandalism edits and warnings in a very short period of time continue to edit in that way. Would any other admin acted in any other way? I doubt it. GiantSnowman 13:34, 20 December 2018 (UTC)". As I already explained, they didn't continue to edit in that way, they continued to edit, but now in a constructive manner, but were blocked anyway. Fram (talk) 11:07, 5 January 2019 (UTC)[reply]

Comment by Arbitrators:

Comment by parties:

Do you want to define 'incorrect' blocks please? Giant Snowman 11:03, 5 January 2019 (UTC)[reply]

WR227 was overturned. User:107.77.173.7 made one edit, which was correct and constructive, between the final warning and your block. User:121.212.176.113 made a correction, but you blindly considered it to be vandalism and blockworthy without checking. The others were similar, with you focusing on minor formatting errors instead of appreciating the constructive, factual nature of their efforts. Fram (talk) 11:10, 5 January 2019 (UTC)[reply]

WR227 was initially upheld; but were any of the others overturned? You still have not defined 'incorrect'. 107.77.173.7 was warned multiple times by numerous editors and continued to edit disruptively. It was not a 'correction', it was the addition of unsourced content (after many warnings for vandalism) that appeared to be vandalism but later turned out to be factual. Giant Snowman 11:18, 5 January 2019 (UTC)[reply]

This is not "the addition of unsourced content", the source is directly behind the figure. The number in the infobox was wrong (didn't match the source given), he changed it to the number from the source immediately following it, so it is very strange to hear you describe this as "not a 'correction', it was the addition of unsourced content". They could hardly have added the same source twice after the same fact? Anyway, an "incorrect" block is a block which should never have been made, a block where the edits you blocked for didn't warrant a block. Fram (talk) 11:52, 5 January 2019 (UTC)[reply]

Apologies, getting the IPs mixed up. 121.212.176.113 changed what appeared to be sourced content with no explanation. Yes, on the face of it, it looked like vandalism. I am sure any other editor patrolling the change, seeing that, would have done the same. Giant Snowman 13:08, 5 January 2019 (UTC)[reply]

Comment by others:

GiantSnowman response to concerns

In a number of documented cases leading up to 4 December 2018, GiantSnowman wrongly reverted other editors.^[a]
On 4 December 2018, GiantSnowman reverted ≈ 500 edits by Veryproicelandic. GiantSnowman's reasons for reverting were incorrect; and because massRollback.js was used, many edits unrelated to the stated basis for reverting were also reverted (eg vote in a PM at Talk:Animal bite^[b]).
A number of editors expressed concerns in the community ANI thread about these reverts.
On 5 December, GiantSnowman accepted those concerns, saying I'll be more careful in future.
On 6 December, GiantSnowman mass-reverted more edits by another user that should not have been reverted.^[c]
Concerns were then raised by several more users.
On 9 December, GiantSnowman accepted these further concerns.
Around three hours later on 9 December, GiantSnowman mass-reverted more edits that should not have been reverted.
Further concerns were raised about GiantSnowman's actions.
On 10 December, GiantSnowman uninstalled the massRollback.js user script.
On 20 December, GiantSnowman incorrectly reverted an edit by 107.77.173.7. A non-IP editor later re-added the content, which stuck.^[d]

^ Evidence by Fram § GiantSnowman misused rollback
^ Evidence presented by Bellezzasolo § Further to UninvitedCompany
^ Evidence by Fish and karate, "Despite all these…" → "…valid edits"
^ Evidence by Fram § During this evidence phase

Posted: AGK ■ 11:50, 5 January 2019 (UTC)[reply]

Comment by Arbitrators:

Analysis drafted; comments welcome. AGK ■ 11:50, 5 January 2019 (UTC)[reply]

@GiantSnowman: Based on evidence so far, you have a higher incidence of out-of-process reverting than a typical administrator or rollbacker. Looking past your past use of the rollback function, the evidence seems also to raise questions about WP:ADMINACCT. I do not know if the committee could be reassured or convinced that you are sufficiently responsive to community concerns. Editing out of step with policy and not solving concerns may mean you no longer meet the requirements imposed by the Wikipedia community on its administrators. That you've uninstalled the massRollback.js script might not allay this problem, because it is fundamental. Could we hear your comments? AGK ■ 12:04, 5 January 2019 (UTC)[reply]

(Decisions have assuredly not already been made. This is just an analysis of evidence section – where we try to understand what the evidence is telling us.) My question was about reacting/responding/remedying community concerns – rather than just replying. And it had already been established that these rollbacks weren't permissible, right? Why did it appear to take 3 tries before you fully took on board the community's concerns? AGK ■ 13:17, 5 January 2019 (UTC)[reply]

Comment by parties:

To be as succint as possible - yes I used mass rollback on editors who I thought were being disruptive. Some were repeatedly adding unsourced content; some were remoing infoboxes; some had a history of incorrect stats updates. I thought those rollbacks were in-line with #5 of WP:ROLLBACKUSE. I now know they were not (though nobody has yet explained what #5 of ROLLBACKUSE is therefore actually for). Those mass rollbacks included inappropriate rollback of good edits, including talk page posts - such is the nature of the script. Everything I did/have done has been, I thought at the time, in line with policy. Will it happen again? No. Has it happened since? Not that I'm aware of (other than the 20 December on-off anomaly, which is debatable).

Saying I have not responded to community concerns is grossly unfair. I engaged with the ANI thread fully, and am engaging fully with this case. I have responded to questions, queries, and concerns. I don't know what else you want/need me to do. It seems like a decision has already been made and nothing I say or do can change that. What a wonderful process. Giant Snowman 13:05, 5 January 2019 (UTC)[reply]

There was the spate of reverts that were rollbacked on 4 December, after which I said I'll be more careful. The 4 Dec edits, in hindsight, were clear good faith edits, even if not fully constructive, supported by edit summaries. I was wrong to roll them back; I self-reverted and apologised (the editor accepted by apology btw). The ones on 6th edit I still think were OK, and at the ANI thread other admins supported them. It was only after the rollbacks on 9 December (an IP adding unsourced content to hundreds of BLPs with no explanation) were criticised that it clicked. That's when I uninstalled the script, and have not enggaged in that type of editing since (so saying I have not listened/taken on board is unfair. I have, even if it took a bit longer than it perhaps should have). But as I said, nobody has yet explained when #5 of ROLLBACKUSE actually applies, that's what caused confusion for me. "To revert widespread edits (by a misguided editor or malfunctioning bot) unhelpful to the encyclopedia" - I view(ed) mass addition of unsourced content about BLPs as unhelful to Wikipedia. Is that wrong as well? If so, you need to change/clarify WP:BLP and WP:BURDEN. Giant Snowman 13:27, 5 January 2019 (UTC)[reply]

Response to Valenciano - yes, fair point, and that is why (as I've said in my evidence) I am now making more of an effort to verify information if I can. However, that doesn't mean that the obligation is on the person adding information to adequately source it, and in my long experience here it is very rare for editors to do that in a separate edit. How long are we expected to wait for a source to be added? Giant Snowman 17:59, 6 January 2019 (UTC)[reply]

Comment by others:

GS, you've repeatedly cited WP:BURDEN as justification for your edits and now say it should be clarified. I did just that for you ([4]) but you ignored me. This is the relevant part: "editors may object if you remove material without giving them time to provide references; consider adding a citation needed tag as an interim step. When tagging or removing material for lacking an inline citation, please state your concern that it may not be possible to find a published reliable source for the content, and therefore it may not be verifiable. If you think the material is verifiable, you are encouraged to provide an inline citation yourself before considering whether to remove or tag it."

That makes it clear that BURDEN is not a sledgehammer with which to bludgeon new editors who are likely to be unfamiliar with our ways. So contrary to what you believe, you are only following part of BURDEN, while ignoring the latter part, which strongly encourages a less adversarial approach than you've taken. You haven't followed that part of burden at all despite users asking you for years why you don't. If you had, a lot of this drama would've been avoided. Valenciano (talk) 17:48, 6 January 2019 (UTC)[reply]

Template

Comment by Arbitrators:

Comment by parties:

Comment by others:

Template

Comment by Arbitrators:

Comment by parties:

Comment by others:

Proposed final decision

Proposals by Robert McClenon

Proposed Principles

Purpose of Wikipedia

The purpose of Wikipedia is to create a high-quality, free-content online encyclopedia. This is best achieved in an atmosphere of collegiality, camaraderie, and mutual respect among contributors. Use of the site for other purposes, such as advocacy or propaganda, the furtherance of outside conflicts, publishing or promoting original research, and political or ideological struggle, is prohibited.

Comment by Arbitrators:

@MrX: That's a common question. The answer, at least from my point of view, is that arbitration decisions are often read by less experienced editors, or outsides, who may be interested in the topic-area involved with the case, but aren't as familiar with Wikipedia and its arbitration procedures as all of us are. For the benefit of those readers, it's sometimes helpful to lead off the decision with some basics such as reminder of what our project is all about. In a case like this one, where most people interested in the case are experienced editors with tens of thousands of edits, it may be less needful to open the decision this way. Newyorkbrad (talk) 22:48, 5 January 2019 (UTC)[reply]

Where a case involves the community's concerns regarding a user's "collegiality, camaraderie, and mutual respect", then it seems appropriate to note that such things are regarded as important. Part of the discussion is that the hectic nature of the football topic is such that editors in that field may consider it more important to revert fast and disregard being collegiate and respectful. At the heart of this case is a dilemma: is it more important that football stats are seen to be right or that editors and articles are treated with respect? This case can be considered to be about the fine tuning of such a dilemma. When are users/admins allowed to act without regard to "collegiality, camaraderie, and mutual respect"? Part of the justification for reverting quickly and without due diligence is that WP:BLPSOURCE allows such behaviour. SilkTork (talk) 02:41, 8 January 2019 (UTC)[reply]

Comment by parties:

Comment by others:

I've never understood the need to restate such fundamental principles in every Arbcom case. - Mr X 🖋 23:17, 4 January 2019 (UTC)[reply]

Vigilante Administration

It is undesirable for an administrator repeatedly to take action against the same editor, especially if that editor is not a focus of other administrators or of attention at a conduct forum. For an administrator to repeatedly act against an editor, rather than asking the opinions of other administrators at WP:AN, WP:ANI, or Arbitration Enforcement, gives the appearance of acting as prosecutor and judge, vigilante administration. ~~It the appearance of justice is not present, justice is not present.~~ The Wikipedia community expects administrators not only to act reasonably but for their actions to be visibly reasonable and free of involvement.

Comment by Arbitrators:

There is a point here, but the heading and wording are unnecessarily inflammatory. Newyorkbrad (talk) 09:10, 3 January 2019 (UTC)[reply]

Indeed. Administrators aren't policemen (or judges or executioners) and "justice" is not relevant to encyclopaedia-writing. @Robert I see what you're getting at but if you want this to be taken constructively I suggest you reword it with reference to established community norms. – Joe (talk) 15:06, 3 January 2019 (UTC)[reply]

This is so inappropriately worded that it cannot be used. Any point being made is lost in the inflammatory language. SilkTork (talk) 02:45, 8 January 2019 (UTC)[reply]

Comment by parties:

Comment by others:

The sort of behavior by administrators that I am describing, which is the way some editors perceive the behavior of Giant Snowman, really is perceived as vigilante administration, and so really does violate the established norms of the community. — Preceding unsigned comment added by Robert McClenon (talk • contribs) 21:06, 3 January 2019 (UTC)[reply]

Administrators and Non-Admin Privileges

Any privilege that is given to non-administrators on a trust basis and to administrators automatically may be restricted from use by an administrator by topic-banning the administrator from using the capability. Misuse of such a privilege by an administrator can be dealt with by a warning, by topic-banning the use of the privilege, or by removal of administrator status.

Comment by Arbitrators:

Is there actually any consensus or precedent for such a topic ban? The opposing argument would be that if an admin can't be trusted with one part of the admin tools, they can't be trusted with any of it. – Joe (talk) 15:08, 3 January 2019 (UTC)[reply]

I agree with Joe's point. If we are at the point of removing any Admin tool, even one that non-Administrators can be given, we're should be considering removing all of them. Admins have to be fully trusted, not partly trusted, and an Admin who has been forbidden to use a tool is only partly trust. Doug Weller talk 15:23, 4 January 2019 (UTC)[reply]

Admins certainly get topic- and interaction-banned from time to time. I'm not sure why we'd automatically think about it differently if the "topic" is a technical mechanism rather than a social behavior. As for the idea of "fully trusted", I don't know how many admins I'd trust to edit a module... Opabinia regalis (talk) 09:33, 6 January 2019 (UTC)[reply]

Comment by parties:

Comment by others:

Theoretically, but in my observation, just about every time the community tries to resolve an WP:ADMIN issue, the discussion is shut down, often with the circular reasoning that the community is not able to resolve the WP:ADMIN issue. The result is that the issues are either escalated to Arbcom, or unresolved.

I disagree that individual admin tools should not be removed or restricted. If a regular editor misuses rollback, we remove that permission. We don't demote them all the way back to unconfirmed. I see no reason why it should be different for admins. If anything, the trust instilled in admins means that they should be more likely to honor any such restriction. - Mr X 🖋 23:29, 4 January 2019 (UTC)[reply]

I believe there have historically been some examples of admins under restrictions or mentorship. Wasn't Everyking trying to get some restriction lifted for like, forever (eventually succeeding)? I don't have any problem with the idea in principle, if the admin is generally good but has problems in a specific area. I don't know if that describes GS though. 173.228.123.166 (talk) 08:17, 5 January 2019 (UTC)[reply]

Rollback

While the Rollback capability is a privilege that is automatically given to administrators, it is also given to non-administrators on a trust basis.

Comment by Arbitrators:

Comment by parties:

Comment by others:

It might be worth emphasising that both administrators and non-administrators receive their tools—of whatever quality—on the basis of trust, whether at RfA or PERM. ——SerialNumber54129 14:07, 3 January 2019 (UTC)[reply]

Particularly in the case of the admin toolset (the others don't have so many different functions bundled), it's not so much a matter of trust that the editor can use the tool, it's a matter of trust that the editor knows their limits. I have the technical ability to perform all kind of weird shit, but I've never once clicked on Special:ChangeContentModel as no matter how often people explain it to me, I've never quite understood what Special:ChangeContentModel does and I've no doubt I'd mess it up if I tried. The question one needs to be asking—and the question we ask ourselves at WP:PERM every time someone applies—isn't "can this editor be trusted with rollback?" but "can this editor be trusted not to use rollback inappropriately provided it's made clear what is and isn't acceptable?". ‑ Iridescent 21:44, 3 January 2019 (UTC)[reply]

Administrators and Admin-Only Privileges

Any privilege that is never given to non-administrators and is always given to administrators, such as the block privilege, is considered an inseparable part of the administrative functionality. Misuse of any such privilege by an administrator can be dealt with by a warning or by removal of administrator status.

Comment by Arbitrators:

Comment by parties:

Comment by others:

No I don't believe this, there's no technical way to turn off a function but nothing is wrong with restricting an admin from using it. Admins were technically able to self-unblock til recently even though they were prohibited by policy from doing so. 173.228.123.166 (talk) 08:20, 5 January 2019 (UTC)[reply]

Just note we have disabled self-unblock fiction. So I disagree with IP Hhkohh (talk) 09:04, 5 January 2019 (UTC)[reply]

Alternate Remedies

When existing remedies are not effective at maintaining the integrity of the encyclopedia against disruption, the Arbitration Committee may devise new remedies to maintain the integrity of the encyclopedia.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Unregistered Editing

Wikipedia has always been an encyclopedia that anyone can edit, with or without registering an account. However, the maintenance of the integrity of the encyclopedia is even more important than the preservation of the privilege of unregistered editors to edit. The privilege of unregistered editors to edit may be abridged or suspended when necessary to prevent disruption.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Proposed Findings of Fact

Association Football

Association football, the most widely played and most publicized sport in the world, has been the subject of contentious and disruptive editing including the insertion and reverting of unsourced data. This contentious editing in turn has resulted in vigilante administration.

Comment by Arbitrators:

There is ongoing discussion regarding this matter on the Evidence pages. I don't think convincing evidence has yet been put forward to establish that the football topic receives so much more disruptive editing in comparison to other areas of Wikipedia that it justifies a more aggressive stance. However, if there is sufficient evidence to indicate that the football topic does get disproportionately more serious disruptive edits than average, then that would be a mitigating factor to consider. I'm not convinced yet that stats on a player's height or number of appearances is a serious matter for BLP concerns. SilkTork (talk) 03:03, 8 January 2019 (UTC)[reply]

Comment by parties:

Comment by others:

My preference would be to leave football out of the equation. Any admin should demonstrate competency and trust, regardless of the topic area. If an admin is heavily involved in editing a topic area, best practice would seem to be to avoid admining in that topic area.- Mr X 🖋 23:33, 4 January 2019 (UTC)[reply]

Association Football and Unregistered Editors

The disruption of articles on association football and association football players has been largely by unregistered editors and has been characterized as drive-by disruption.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Giant Snowman and WRL227

Giant Snowman employed vigilante administration against some aggressive editors in the area of association football, including but not limited to WRL227.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Disruption by Unregistered Editors

ArbCom discretionary sanctions, as currently applied, are not likely to be an effective remedy to prevent disruption of the encyclopedia by unregistered editors. A modified protection regime is needed for the purpose.

Comment by Arbitrators:

I'm coming around to the idea that a major contributing factor to this case is that people are spread too thin over a topic area that is difficult to maintain, and have developed bad habits or resorted to extreme measures in trying to keep up. I agree that DS is unlikely to be of much practical use given the pattern of problem edits. However, I'm not seeing what kind of "modified protection regime" would be more effective. ~~What did you have in mind?~~ Never mind, I missed that you had a separate proposal defining your idea. That doesn't seem likely to be of much use either, at least from the sampling of the editing patterns we've seen here - if the topic area needs frequent updates, and those updates are often performed by inexperienced editors, then semiprotection seems likely to make the articles rapidly out of date. Pending-changes seems like a better fit, and yet even more prone to encouraging reverts/rejected edits. Opabinia regalis (talk) 09:50, 6 January 2019 (UTC)[reply]

I'm still pondering on that issue. I'm not yet convinced we have adequate evidence that bios are more numerous in football than in other areas such as politics. Nor that that there are fewer active interested editors to monitor the situation, given that WP:Football appears to have one of the largest active groups of members. I'm also aware that much disruption that spills over into dispute resolution arenas concerns politics, ethnicity, religion, and countries rather than football. While I'm hearing the arguments about how hectic it can be in the football topic, this seems to be mainly about the orderly manner in which minor statistics are updated rather than anything serious enough to invoke BLP. WP:Football members themselves seem a bit divided on this issue, with a number that feel that reverts shouldn't be made without first checking if the edit is accurate. In short, while there may be more than one WP:Footy member who behaves as GS does, this is not a widespread pattern, so I'm not yet convinced that the topic area itself is a sufficient rationale for abandoning due diligence. SilkTork (talk) 03:22, 8 January 2019 (UTC)[reply]

Comment by parties:

Comment by others:

I don't think there should be a modified protection regime. A modified deletion regime might be better if you get my drift. Looking at the football player article categories, the member counts add up to something like 150,000, though that's possibly not the actual article count since there may be overlap between those. Either way it's an awful lot, and most of the articles appear to be content-free stubs and about players who come nowhere near meeting GNG.

I don't mind marginal-notability articles in principle (as long as they're not promotional), but if we've got a situation where the football wikiproject can't maintain them while still living up Wikipedia's usual AGF and civility standards, then maybe we shouldn't have those articles. Wikidata might be a better home for the info in them. 173.228.123.166 (talk) 05:16, 5 January 2019 (UTC)[reply]

Just for the record, the total number of football biographies as of yesterday was 112,994. The full list isn't uploadable as it's over the page size limit, but I can mail it to anyone who wants to verify the number. ‑ Iridescent 09:01, 5 January 2019 (UTC)[reply]

The number of articles with {{Infobox football biography}} is 158,811 so I'm thinking that's an underestimate. Galobtter (pingó mió) 09:16, 5 January 2019 (UTC)[reply]

My number is the total of all the subcategories of Category:Association football players by nationality with duplicates omitted, which is probably more accurate. The transclusion count for {{infobox football biography}} includes user pages and drafts. The basic point—that the number is too high for Wikipedia's 3300 active editors to monitor in any great detail—is the same either way. ‑ Iridescent 09:23, 5 January 2019 (UTC)[reply]

Yeah, I know the transclusion count includes drafts and sandbox, which is why I used a hastemplate search of articles (linked in my comment). I think not every footballer has been categorized by nationality yet, which is why that is an underestimate (though I get that the point is the same either way). Galobtter (pingó mió) 09:38, 5 January 2019 (UTC)[reply]

Thanks Iridescent. Do you have a way to check how many of the 112,994 soccer biographies are BLP? It sounds like possibly 5% of all the BLP's on Wikipedia are basically data pages about otherwise non-notable soccer players. That doesn't seem healthy. Re the 3300 active editors: I get that this is a collaborative project and we all help each other out by editing outside our primary areas at times, but it's supposed to be somewhat reciprocal. If the football project members are outsourcing their maintenance workload on everyone else while not taking on similar maintenance work on non-football articles, that imbalance needs addressing. 173.228.123.166 (talk) 00:28, 6 January 2019 (UTC)[reply]

hastemplate:"Infobox football biography" incategory:"Living people" won't be entirely accurate, but it gives a count of 137,912. ‑ Iridescent 09:02, 6 January 2019 (UTC)[reply]

Proposed Remedies

Discretionary Sanctions

ArbCom discretionary sanctions are ordered for the subject area of association football, narrowly defined (sensu stricto).

Comment by Arbitrators:

Will this be of use against drive-by IP editing in the area? DS is good for keeping invested contributors in line, because it sets behavioral expectations and allows for immediate consequences. I'm not sure it'll have the same effect on an IP editor who doesn't plan on sticking around and doesn't care that they've been topic-banned from footy for a month. ♠PMC♠ (talk) 06:26, 3 January 2019 (UTC)[reply]

I'm not saying this would necessarily be helpful either, but discretionary sanctions can be applied on a by-page as well as by-editor basis (e.g. placing a given page or topic under 1RR). But if we decide to consider this type of approach—again, I'm not saying we should—I think we would first want to make the football (soccer) editing community aware that it's under discussion. Newyorkbrad (talk) 15:38, 3 January 2019 (UTC)[reply]

This seems to specific an issue to warrant DS. If we do consider it we should certainly notify any relevant wikiprojects, and soon. Doug Weller talk 15:26, 4 January 2019 (UTC)[reply]

Do we have evidence of significant disruption in the topic? What's been brought before us is one admin who edits without due diligence and a rationale that this is because appearance and goal statistics are updated so frequently that he doesn't have time to check the veracity of the edits, so prefers to revert. Other WP:Footy members may also do this, but not all. Indeed, in discussion with WP:Football, there are a number who disagree with GiantSnowman's approach. I don't think we are getting edit wars between established editors so much as established editors reverting IP and newbie editors, some of whom never return, while others return and get blocked for being disruptive. SilkTork (talk) 03:32, 8 January 2019 (UTC)[reply]

Comment by parties:

Seems strange in this case. The case is about an admin who has been overeager in applying the existing tools. How would giving admins an additional, stronger tool resolve the problem raised here? This would seem to make the problem potentially worse, not better. The issue that brought us here is rollback, vandal warnings, and blocks of good faith editors for good faith, constructive edits. How do DS apply? Fram (talk) 16:53, 4 January 2019 (UTC)[reply]

Comment by others:

Question: Would any of the following be a violation of DS? 1) Changing an infobox or table parameter (like incrementing "games played") without providing an inline source, if a source (like Soccerway) is already cited elsewhere in the article; 2) Same without providing a link to Soccerway in the edit summary or any edit summary at all; 3) Not updating the "last updated" time stamp. Levivich (talk) 05:12, 3 January 2019 (UTC)[reply]

This would be quite useless. DS is useful when there are disputes between established contributors. It is essentially impossible to enforce DS against IPs and drive by editors. Galobtter (pingó mió) 14:22, 3 January 2019 (UTC)[reply]

I don't think it is really possible to enforce 1RR against IPs (by the time you give DS alerts and warnings and take them to AE, they would already have stopped editing), so that 1RR and page restrictions can be applied to articles would not make DS useful here in my view. Galobtter (pingó mió) 17:01, 3 January 2019 (UTC)[reply]

Agreed that DS would not be helpful here. TonyBallioni (talk) 14:41, 4 January 2019 (UTC)[reply]

To User:Fram - The DS were/are proposed to permit other admins to deal with the disruption without the need for vigilante administration. In response to comments, I have proposed an alternate remedy regime. The objective is to provide a disciplined approach to the drive-by editors so that the excuse for vigilante administration is removed. Discussion of how to do this can continue. Robert McClenon (talk) 20:35, 4 January 2019 (UTC)[reply]

God, please no more labyrinthine discretionary sanctions. There is a single admin involved here, who may or may not possess the will or skill to continue in an admin role; or who may simply struggle with judgement in a specific topic area; or who may have an attitudinal issue concerning the use of rollback (or any of a number of other possibilities). The solution is not to turn a huge topic area into a bureaucracy that hinders our mission. - Mr X 🖋 23:40, 4 January 2019 (UTC)[reply]

Not serious and only one person so no need Hhkohh (talk) 08:55, 5 January 2019 (UTC)[reply]

Special Protection Regime

When ordered by the Arbitration Committee or by the Wikipedia community, semi-protection may be applied indefinitely, on a page-by-page basis, to pages that have been subject to disruption by unregistered or new editors.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Bad idea. This is supposed to be an encyclopedia that anyone can edit. We protect pages that are under serious edit warring or vandal attack but shouldn't give special protection to huge swaths of articles that aren't individually under attack. It would be interesting to check into the origin and history of the articles and I might try to do that. 173.228.123.166 (talk) 05:21, 5 January 2019 (UTC)[reply]

Disagree with this idea. Just normal WP:RPP is OK to me Hhkohh (talk) 08:59, 5 January 2019 (UTC)[reply]

Semi-Protection of Association Football Pages

Article pages on association football and association football players may, as needed, be indefinitely semi-protected to prevent disruption by disruption by unregistered editors (drive-by disruption).

Comment by Arbitrators:

Comment by parties:

Comment by others:

GS and Rollback

Giant Snowman has repeatedly misused the rollback privilege, and is topic-banned from use of rollback.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Why not proposed admin rights removal?

Could be more specific duration? Hhkohh (talk) 04:55, 3 January 2019 (UTC)[reply]

Proposals by User:Hhkohh

Proposed principles

Rollback

1.1) Administrators who persistently misuse rollback may have their administrator access revoked

1.2) The rollback tool should not usually be used to perform any revert which ought ordinarily to be explained, such as a revert of a good-faith content edit, nor should it be used in content disputes

Comment by Arbitrators:

Comment by parties:

Comment by others:

BLP

2) We must get the article right. Be very firm about the use of high-quality sources. All quotations and any material challenged or likely to be challenged must be supported by an inline citation to a reliable, published source. Contentious material about living persons (or, in some cases, recently deceased) that is unsourced or poorly sourced—whether the material is negative, positive, neutral, or just questionable—should be removed immediately and without waiting for discussion. Users who persistently or egregiously violate this policy may be blocked from editing.

Comment by Arbitrators:

I disagree with 173.228.123.166 that insisting on high-quality sources is a violation of NPOV. NPOV is about the presentation of information in an unbiased manner, it isn't a mandate that we must "use all the sources that aren't completely crap". High standards can help maintain NPOV by ensuring that what we present is an accurate reflection of the accepted information in a given area. WP:MEDRS is a good example of a WikiProject/topic area with a strict standard for sources that helps maintain NPOV by excluding biased or unreliable sources that could be used to tilt articles towards POV. Maybe it's time to develop WP:FOOTYRS? ♠PMC♠ (talk) 14:18, 5 January 2019 (UTC)[reply]

Comment by parties:

Comment by others:

"Be firm about the use of high-quality sources" is imho contrary to Wikipedia's fundamental NPOV principle, which says use all the sources that aren't completely crap. Per WP:WEIGHT the high quality sources get more extensive coverage than the lower quality ones, but we're supposed to give an overview of everything. For this soccer stuff it's almost irrelevant anyway since the articles are almost content-free. By the way is there a known significant pattern of Transfermarkt being wrong? 173.228.123.166 (talk) 08:25, 5 January 2019 (UTC)[reply]

For why is Transfermarkt unreliable? See these discussions Hhkohh (talk) 08:51, 5 January 2019 (UTC)[reply]

GiantSnowman mostly revert soccer articles so I disagree with you Hhkohh (talk) 08:53, 5 January 2019 (UTC)[reply]

CIR

3) A person should be able to collaborate with other editors, defend their editing when asked to do so, and be willing to abide by consensus

Comment by Arbitrators:

Comment by parties:

Comment by others:

Meatbot

4) No matter the method, the disruptive editing must stop or the user may end up blocked or desysopped

Comment by Arbitrators:

Comment by parties:

Comment by others:

Unblock request

5) A declined unblock request is not regarded as an endorsed block

Comment by Arbitrators:

Comment by parties:

Comment by others:

This proposal is pointed to block WR227 issue Hhkohh (talk) 06:32, 4 January 2019 (UTC)[reply]

Except it kinda is... TonyBallioni (talk) 14:42, 4 January 2019 (UTC)[reply]

Involved admin

6) Editors should not act as administrators in disputed cases in which they have been involved

Comment by Arbitrators:

Comment by parties:

Comment by others:

Proposed findings of fact

Misunderstandings

1) GiantSnowman admitted misunderstanding other editors. (See his own evidence section)

Comment by Arbitrators:

Comment by parties:

Comment by others:

Warning templates abused

2)Although Transfermarkt is unreliable per WP:RS discussion outcome. GiantSnowman seems not tell IP about transfermarkt. Instead he rollback then just placed a warning template on IP talk page.(See:Wikipedia:Arbitration/Requests/Case/GiantSnowman/Evidence#GiantSnowman uses vandal warnings for non-vandal edits)

Comment by Arbitrators:

Comment by parties:

Comment by others:

NAK? Robert McClenon (talk) 21:55, 3 January 2019 (UTC)[reply]

Adjusted Hhkohh (talk) 06:24, 4 January 2019 (UTC)[reply]

Mass rollback script

3) GiantSnowman installed mass rollback script before December 10.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Proposed remedies

Note: All remedies that refer to a period of time, for example to a ban of X months or a revert parole of Y months, are to run concurrently unless otherwise stated.

Admin right removal

1) For conduct unbecoming an administrator, GiantSnowman is desysopped. They may regain administrator tools at any time via a successful RfA.

Comment by Arbitrators:

Comment by parties:

Comment by others:

1.1) GiantSnowman topic ban from rollback. (only if his admin rights is remained)

Comment by Arbitrators:

Comment by parties:

Comment by others:

1.2) GiantSnowman warn that he should use rollback correctly. (only if his admin rights is remained)

Comment by Arbitrators:

Comment by parties:

Comment by others:

Rollback permission

2) GiantSnowman may request rollback via community consensus. (only if his admin rights is removed)

Comment by Arbitrators:

Comment by parties:

Comment by others:

Since this case rests upon the claim that admins are treated better than non-admins, this would certainly be deeply ironic...requiring an admin to have a community consensus to gain a right that a non-admin merely has to ask for. ——SerialNumber54129 17:07, 3 January 2019 (UTC)[reply]

Thanks. Adjusted. Hhkohh (talk) 17:18, 3 January 2019 (UTC)[reply]

3) GiantSnowman cannot request rollback permission in 6 months. (only if his admin rights is removed)

Comment by Arbitrators:

Comment by parties:

Comment by others:

GiantSnowman is warned

4) GiantSnowman is warned that he blindly reverted good-faith edits

Comment by Arbitrators:

Comment by parties:

Comment by others:

1RR restriction

5a) GiantSnowman is restricted 1RR in article namespace indefinitely except the normal exception due to repeated clueless revert.

Comment by Arbitrators:

Comment by parties:

Comment by others:

This remedy would normally apply to incorrigible edit warriors. The evidence doesn't support such a restriction. - Mr X 🖋 13:43, 5 January 2019 (UTC)[reply]

MrX, I do not think so. Although GiantSnowman sometimes revert obvious vandalism, but per enough evidence, I think we should 1RR Hhkohh (talk) 14:17, 5 January 2019 (UTC)[reply]

5b) GiantSnowman is restricted 1RR except user namespace indefinitely except the normal exception due to repeated clueless revert.

Comment by Arbitrators:

Comment by parties:

Comment by others:

This remedy would normally apply to incorrigible edit warriors. The evidence doesn't support such a restriction. - Mr X 🖋 13:43, 5 January 2019 (UTC)[reply]

5c) GiantSnowman is restricted 1RR in related footy article indefinitely except the normal exception due to repeated clueless revert.

Comment by Arbitrators:

Comment by parties:

Comment by others:

5d) GiantSnowman is restricted 1RR in all related footy edits indefinitely except the normal exception due to repeated clueless revert.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Block for one week

6) GiantSnowman block 1 week for his disruptive rollback and CIR issue

Comment by Arbitrators:

Comment by parties:

Not helpful. Fram (talk) 16:48, 4 January 2019 (UTC)[reply]

Comment by others:

What problem is this supposed to solve? This is Wikipedia, not Vindictopedia. Or are you thinking that somehow something fundamental will change in seven days? ‑ Iridescent 21:50, 3 January 2019 (UTC)[reply]

Iridescent, per WP:MEATBOT: No matter the method, the disruptive editing must stop or the user may end up blocked. GiantSnowman use mass rollback script and result in disruptive editing. Hhkohh (talk) 00:57, 4 January 2019 (UTC)[reply]

No, that's not how it works and not what that line of the bot policy means. Blocks are preventative, not punitive; the only circumstance where blocking is ever appropriate it to prevent continued disruption. Since GS no longer has access to the script in question, then by definition a block isn't going to prevent it being used again. ‑ Iridescent 16:01, 4 January 2019 (UTC)[reply]

This might have been useful as some point, but certainly not now. - Mr X 🖋 13:35, 5 January 2019 (UTC)[reply]

Topic-ban from editing footy articles or discussion

7) Due to GiantSnowman cluelessly reverting, GiantSnowman is topic-banned from editing footy articles or discussion for one month

Comment by Arbitrators:

Comment by parties:

Comment by others:

I don't believe the evidence supports such a sanction and I'm pretty sure this would be a net loss for Wikipedia.- Mr X 🖋 13:37, 5 January 2019 (UTC)[reply]

I do not recommend but... Hhkohh (talk) 14:08, 5 January 2019 (UTC)[reply]

I have added duration now Hhkohh (talk) 14:13, 5 January 2019 (UTC)[reply]

Editors are reminded

8) We should remove unsourced content from articles especially BLP with a good reason.

Comment by Arbitrators:

Comment by parties:

Comment by others:

I seldom edited BLP articles, cheers Hhkohh (talk) 18:00, 3 January 2019 (UTC)[reply]

9) Any questions about footy are welcomed to ask/discuss in WT:FOOTY

Comment by Arbitrators:

Comment by parties:

Comment by others:

I usually work on football articles Hhkohh (talk) 18:16, 3 January 2019 (UTC)[reply]

10) WikiProjects cannot override community policy

Comment by Arbitrators:

Comment by parties:

Comment by others:

Proposed enforcement

Proposals by User:Galobtter

Proposed principles

Tool misuse

1) Administrators are expected to use their tools responsibly. Misuse of even parts of the toolset may be grounds for removal of the whole because it damages the trust of the community in the ability of an administrator to use their tools responsibly.

Comment by Arbitrators:

This seems an important fundamental principle. Doug Weller talk 15:29, 4 January 2019 (UTC)[reply]

Yes. SilkTork (talk) 03:35, 8 January 2019 (UTC)[reply]

Comment by parties:

Comment by others:

This is fine as a principle or a restatement of policy, but as I've said elsewhere, misusing one tool should not necessarily result in desysopping if a less harsh solution will work. Trust of the community is also damaged when the efforts of the community to resolve WP:ADMIN issues are thwarted by admins shutting down discussions or making chilling threats of sanctions. (I have not yet presented the evidence but most of it is know by the participants anyway).- Mr X 🖋 12:49, 5 January 2019 (UTC)[reply]

Administrators and rollback

2) As rollback is part of the administrative toolset, misuse of rollback can be grounds for desysopping.

Comment by Arbitrators:

Yes, misuse of any of the tools can be grounds for desysopping. Though, as always, degree of misuse and mitigating factors are taken into consideration. SilkTork (talk) 03:37, 8 January 2019 (UTC)[reply]

Comment by parties:

Comment by others:

Involved

3) Administrators are expected to not generally use their tools in disputes in which they are involved. This includes not blocking editors with which they have a dispute.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Non-obvious reversions

4) Reverting edits that are unsourced but are not vandalism or otherwise clearly violating policy constitutes involvement in a dispute.

Comment by Arbitrators:

Comment by parties:

Comment by others:

BLP policy

5) What constitutes a violation of BLP policy can be controversial. The BLP policy mandates removal of contentious material about living persons that is unsourced. However, it does not mandate removal of all unsourced material about living persons.

Comment by Arbitrators:

Comment by parties:

Comment by others:

There is, at best, an ambiguous consensus on what exactly "contentious" means: can it only be judged after the fact (where eg., people vote their feelings, 'contentious/not contentious') , or is any edit that is contended (eg., reverted), contentious. This probably goes back to an unclear consensus on what exactly "challenged" means (ie. does a revert mean it is challenged under WP:V). And WP:V does, of course, strongly come down on the side of sourced content (not unsourced content). As a matter of process, V is relatively clear, if unsourced content is removed, it should not be returned without an inline cite. --Alanscottwalker (talk) 13:47, 4 January 2019 (UTC)[reply]

Anything that could possibly be read as a loosening of the latitude we give users to remove content from BLPs should not be adopted as a principle. Additionally, this seems to be at odds with WP:V, which requires that everything be verifiable Yes, we don't enforce it as much as we should, but adopting a principle that basically says "some unsourced content in BLPs is okay!" isn't a good idea on either ground. This also seems to run foul of WP:ONUS and Wikipedia:Requests_for_arbitration/Editing_of_Biographies_of_Living_Persons#Biographies_of_living_persons: once content has been challenged it should stay removed until there is a source and consensus. I know a literal reading of this isn't technically in violation of any of this, but it is borderline enough on enough key areas that I don't think passing it is a good idea. TonyBallioni (talk) 14:50, 4 January 2019 (UTC)[reply]

I agree with Tony here. Specifically, policy prohibits the insertion of any factually incorrect statement into articles:

When reverting edits, care should be taken not to reinstate material that may be in violation of such core policies as neutrality, verifiability, and biographies of living persons.

That policy has teeth - see Wikipedia:Arbitration/Requests/Case/Winhunter for an example of what happens to administrators who disregard it. A side note on that - Lankiveil, who was a clerk (I didn't know till today that he is deceased) said "the case was brought by an LTA". The filer, Barts1a, was certainly subsequently banned, but was never accused of "long-term abuse". Administrators with chips on their shoulders will attempt to get the Community to ban editors who have never been warned (policy states editors are site-banned only as a last resort) and they do that when other administrators have commented that the editors have done nothing to merit a warning, let alone a block. Such attempts are doomed to failure, because prior warning is a prerequisite for a ban and policy unequivocally states that a ban may only be imposed via a consensus of editors who are not involved in the underlying dispute. Another policy safeguard is that Long-term abuse pages require approval by someone other than the administrator who drafted them. Some administrators purport to approve them themselves, with the result that they do not come forward for review by the reviewers as they drop out of the relevant category. Clerks should not describe editors as "LTA" because an administrator with a grudge has self-approved an LTA page. These can generally be spotted because the accusations are not supported by diffs. 150.143.48.35 (talk) 17:49, 5 January 2019 (UTC)[reply]

Courtesy link to previous discussions:

Another way of recognising grudge-bearing administrators is that when challenged they don't own up but double down. A technique they use to conceal their abuse is "creative archiving", which Moonriddengirl identified and highlighted as long ago as 10 July 2011 [5]. This was discussed with Opabinia. See Special:Permalink/873178407#Fred Bauder and others. The old Committee never got to grips with this problem. Perhaps the new one can.

Mass rollback

6) Rollback, whether used through a script or not, should not be used to indiscriminately or en masse revert edits that may be a mixture of constructive and unconstructive. It should only be used to revert edits that are clearly unhelpful.

Comment by Arbitrators:

Comment by parties:

Comment by others:

This would basically ban all use of mass rollback outside of a INeverCry type vandal adding the same thing to multiple articles. There are cases of LTAs and sockmasters where this would be less than ideal. TonyBallioni (talk) 14:52, 4 January 2019 (UTC)[reply]

I think edits that are violations of a ban would be counted as "unconstructive" though I do see that it could be clearer (certainly, the intention here isn't to prevent mass reversions of banned users evading a block, but to rather to be a principle that expresses that GiantSnowman's mass rollback's were inapproppiate because they caught up both constructive and nonconstructive edits) Galobtter (pingó mió) 15:09, 4 January 2019 (UTC)[reply]

Yeah, but people already get pissy when a clerk or CU mass rollbacks a sock with an SPI a mile long because we didn't catch that they corrected a typo in an article. I think stating the principles around the use of mass rollback as a positive rather than a negative would be ideal. TonyBallioni (talk) 15:12, 4 January 2019 (UTC)[reply]

If this principle is adopted into the final decision, it should incorporate an exception for edits from blocked and banned users, so that it synchronizes with policy.- Mr X 🖋 12:57, 5 January 2019 (UTC)[reply]

Proposed findings of fact

Use of rollback by GiantSnowman

1) GiantSnowman repeatedly used rollback inappropriately even after assurances that they would use it more carefully. (GiantSnowman misused rollback, GiantSnowman paid lip service to concerns, Evidence presented by UninvitedCompany, GiantSnowman use of rollback)

Comment by Arbitrators:

Comment by parties:

Comment by others:

Use of the block tool by GiantSnowman

2) GiantSnowman both reverted edits on the grounds of lack of sourcing and blocked the editors responsible for the edits. The edits may have had problems with sourcing, but were not vandalism, and the editors were clearly acting in good faith. (WR227, GiantSnowman blocks constructive editors)

Comment by Arbitrators:

Comment by parties:

I do not yet have an opinion on whether the rollback/blocks were appropriate, but the logic here should be that the rollback and the block are just one administrative action. If we follow the logic of your proposed decision, it follows that if GS first blocked the user and then rolled back their edits, the whole sequence of action were fine, and now, since they first rolled back the edits and then blocked the editor, it is not fine. It can be fine or not fine, but it should not depend on the sequence in which the block and the rollback were executed, as soon as both have been made within a reasonable timespan (not a month apart).--Ymblanter (talk) 15:51, 3 January 2019 (UTC)[reply]

Comment by others:

Ymblanter, that's definitely true. I reworded it to be closer to my intended meaning. TBH, I expect in the actual proposed decision if there is anything like this that the finding be for specific instances (like WR227). Galobtter (pingó mió) 16:00, 3 January 2019 (UTC)[reply]

Proposed remedies

Note: All remedies that refer to a period of time, for example to a ban of X months or a revert parole of Y months, are to run concurrently unless otherwise stated.

GiantSnowman is desysopped

1) For misuse of rollback and the blocking tool, GiantSnowman is desysopped. They may regain the administrative tools after a successful request for adminship.

Comment by Arbitrators:

@TonyBallioni: You know, sometimes someone links to something I said ages ago and I look at it and think "now what exactly was I smoking when I posted that?" But this time I still agree with myself, sorry :) Removing someone's user rights is an exercise of power - pretty much by definition. That doesn't mean no one should do it; it means they should be careful about it, much more so than in that linked case. (In any event, I'm just one member of a big group, I don't think I have the power to kill a wiki-process with one comment - and let's face it, if I did have that power I wouldn't be wasting it on PERM. I'm coming for you, ANI..... ) Opabinia regalis (talk) 10:19, 6 January 2019 (UTC)[reply]

Comment by parties:

84.219.252.47 - I have not blocked any editors for adding sourced content, and no evidence has been presented that shows me doing that. Giant Snowman 10:10, 8 January 2019 (UTC)[reply]

2A02:C7F:9E12:8F00:6C51:14D8:1B23:F46C (talk · contribs · WHOIS) is a sock and was reverted and blocked per WP:BLOCKEVASION/WP:DENY. Let me re-phrase - have I blocked any constructive/good faith editors for adding sourced content? Giant Snowman 10:25, 8 January 2019 (UTC)[reply]

Comment by others:

Same as mine Hhkohh (talk) 16:52, 3 January 2019 (UTC)[reply]

I’m sure I’m going to get flack for saying this or accused of protecting an admin when I’d have yanked rollback from a non-admin, but I don’t think this is appropriate in this case. We are not talking about someone who has been repeatedly warned and who was frequently at noticeboards for bad conduct, but someone who apparently had been doing this for years, who never had it brought up to them, and who had blocks reviewed by other admins that were upheld. Before yanking rollback from a non-admin we at least give them a warning, and if it’s possible they misunderstood, multiple. In large part because of statements from current members of this committee (I’m calling out Opabinia regalis for this comment which essentially killed “easy come easy go” as a standard for PERM by making it clear ArbCom did not view it that way.)

In short, what we are seeing here is the exact opposite of the Super Mario problem: admins are exceptionally unlikely to yank PERMS without a user all but creating enough disruption to be verging on a lengthy block, and even then only after sufficient handholding as to why it shouldn’t be used that way. Now we are talking about desysoping someone for what amounts to abuse of one of the lowest admin rights? It’s not like everyone else where he can just reapply at PERM.

Re: blocking, I’ve looked at the blocks here. I agree most of them are dumb. At the same time, they are not nearly as bad as blocks that regularly occur at AIV that this committee will never review because no one is going to file a case over a 6 month block of an IP for adding poop to an article or the like. TonyBallioni (talk) 14:17, 4 January 2019 (UTC)[reply]

GiantSnowman was indeed repeatedly warned about their rollback usage yet persisted (even after assurances that they would change their use of mass rollback they continued misusing it), though indeed that was over a week or so rather than years. I'm certain their rollback rights would've been removed by now had they been a non-admin and that it is among the "lowest admin rights" does not make it better; that would make it worse in my view - as I said before during the case request, if you can't trust someone to rollback, you can't trust them to block, because deciding what does or does not merit reversion is a very similar question to whether an editor is being unconstructive enough to be blocked.

I agree that had issues been raised in the past, that would strengthen the case for removal of adminship. But I don't think there needs to be an "other admins are worse" sort of comparison here (and at-least that 6 month IP block would not drive away a constructive editor); I think it is important to make it easier for admins to be held accountable for good faith issues that simply demonstrate that they shouldn't be an admin. IMO, if GiantSnowman is simply "admonished", we will be back here relatively soon if they do continue to use their tools, and I don't see any other solution beyond either an admonishment or desysopping - all a rollback ban would do is slow their ability to revert things, and preventing them from reverting would be pretty unworkable (plus cause them to retire anyhow per their comments) and would be such a statement on their ability that it'd be clear that they shouldn't have the tools. Galobtter (pingó mió) 14:50, 4 January 2019 (UTC)[reply]

Honestly, if they had their rollback rights removed it would likely be the admin removing them facing an ArbCom case or an AN thread because of how hard it is to remove unbundled rights. Easy come easy go is not at all reality. Removing rollback from an established non-admin editor who is a major force on a wikiproject is all but impossible socially, and the rights would likely have been restored either via consensus or unilateral admin action at PERM. TonyBallioni (talk) 14:54, 4 January 2019 (UTC)[reply]

The question is: why should it be that way? Your comment is a reflection of the deeply ingrained culture in which we expect admins to be treated differently that other editors. It would be interesting to see if anyone could point to a similar case as this, where an admin's use of a tool was restricted, and then restored as in one of the scenarios in your comment. - Mr X 🖋 13:58, 5 January 2019 (UTC)[reply]

MrX, I think the point I was trying to make was that thanks to ArbCom having views similar to the ones I linked to by Opabinia regalis, what is being said here is that admins should be held to a significantly higher standard than basically any other user with regards to rollback. There’s obviously good reasons to hold admins to a higher standard, but desysoping for something that would be socially impossible to revoke as a non-admin seems a bit odd to me. At the same time, I’m very sympathetic to the trust issues raised by some arbs.

OR: I pretty much disagree with you as a rule (see your support in my RfA :p) but I think that FoF in the Rubin case plus your comment were especially harmful to the way PEEM operates. It basically ratified a culture where the unbundled rights were seen as a Big Deal (tm), and contributed to a very negative trend where PERM has become stricter in granting because removing user rights is so difficult. The relationship to this case being, you and other arbs have helped to create a culture where the minor rights can basically be abused with impunity, and while I would love to see that changed and have ArbCom walk back from your position, doing it by desysoping seem over the top. TonyBallioni (talk) 16:04, 6 January 2019 (UTC)[reply]

I don't really feel OR is to blame for that shift in culture; to me, she was describing the situation as it already existed in practice, rather than making policy by fiat. I can testify that the "you removed my relatively trivial userright, this is a breach of my Wikipedia Human Rights and I'm immediately going to go to IRC to try to round up an angry mob!" mentality was around long before 2017. Someone can probably plot a nice little chart showing how the rise and subsequent levelling-off of "sense of entitlement among editors" closely correlates with the decline and levelling off in "number of active editors". See also the shedloads of material written about the decline of "support per no big deal" at RFA once the perception that it was hard to desysop admins gained widespread currency. ‑ Iridescent 16:23, 6 January 2019 (UTC)[reply]

True, I’ll agree with that, I was just pointing out one of the most “official” comments that basically sanctioned that view of user rights as a fundamental human right never to be infringed upon. OR somewhat unfairly catches flak from me for it, well, because I’m sure as she’ll admit, she’s one of the more vocal arbs and is very diffable. Anyway, my larger point remains: if GS were a non-admin who did this and you or I were to have removed rollback, it likely would have caused a shitstorm with equally as loud cries of admin abuse as is happening in this case. TonyBallioni (talk) 16:32, 6 January 2019 (UTC)[reply]

These are all good points, including Opabinia regalis' comments from 2017. But isn't it far less socially stigmatizing to restrict an admin's use of a single tool than to desysop them entirely? I don't doubt that it could create more drama, but it shouldn't. We have somehow managed to elevate admins to a class of editors who are untouchable, unless it's Arbcom doing the touching.- Mr X 🖋 17:04, 6 January 2019 (UTC)[reply]

If GS loses rights here, it will be with the agreement of at least ten arbitrators and input from numerous other editors over a period of weeks. Socially and functionally, that is a very different standard to an individual administrator removing a PERM right. There the outrage is fuelled by the perception that it is an arbitrary decision without "due process". If we want to return accountability to the unbundled rights, we should think about an XfD-like process whereby they can be reviewed and revoked by multiple editors.

The more pertinent point I took from TB's comment is that we don't want to jump on people for their "first offence". For me this case will hinge on how GS responded to criticism of his approach and whether there really was a pattern of repeated complaints and continued misuse. – Joe (talk) 17:56, 6 January 2019 (UTC)[reply]

The only way this solves the problem is if it so offends GS that he leaves the project entirely - and if that's the goal, he should be banned explicitly. The blocks don't rise to the level of a desysopping, and to the IPs and new users he's been rolling back, rollback is entirely indistinguishable from undo-with-default-summary. He'll still be able to do that; even anons can. —Cryptic 09:47, 8 January 2019 (UTC)[reply]

I'm sorry but he's been blocking users for making correct and sourced edits, while defending doing so and showing absolutely no indication that he's going to stop blocking people for making correct and sourced edits. How does that NOT rise to the level where it's at the very least a consideration for you? And we're not even talking about collateral damage in mass rollback, but manual rollback and blocking, and claiming to have manually reviewed the edit in question and simply defending it with that it "appeared" to be vandalism, even though the source did certainly have that data... A source that it was GS himself that added I might add so couldn't possibly have been a case of claiming it was due to unreliable source. So the problem isn't so much reverting alone, the problem as I see it, is the reverting while claiming it being vandalism and the blocking that is the main issue. So while desysop would not solve his ability to undo edits, it would solve the blocks and would take the edge of his templating (even if it doesn't prevent them either) of users that are making correct edits. It would also send the message that the community doesn't accept that it's correct to revert edits that are correct, though that might be possible using lesser methods but to not even consider it seems baffling to me.84.219.252.47 (talk) 10:05, 8 January 2019 (UTC)[reply]

Sorry GS but you have. And it would be in evidence, if clerks had actually posted evidence mailed to them but they're seemingly as slow on that as they are in reposting legacypac's evidence from the clerks page, seeing as how that's what they're demanding from IP editors. You can however see the evidence talkpage discussion regarding 2A02:C7F:9E12:8F00:6C51:14D8:1B23:F46C which you blocked, and every single edit they made, was correct and properly sourced. And that's just one of many examples. (I've mailed in 8 different ones, all of which you've blocked after making only correct and sourced edits).84.219.252.47 (talk) 10:22, 8 January 2019 (UTC)[reply]

You say it's a sock... But you have provided no evidence for that and there's no SPI saying it. All there is is that you say it's a sock of someoneone, and that's it. But even if true, it doesn't change the fact that you have indeed blocked a user that has only made correct and sourced edits.84.219.252.47 (talk) 10:28, 8 January 2019 (UTC)[reply]

GiantSnowman is cautioned

2) GiantSnowman is cautioned not to indiscriminately revert edits or aggressively revert and warn good faith editors.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Editors are reminded

3) Editors are reminded that what is considered reasonable removals or reversions under the BLP policy is often controversial. Editors are asked not to engage in significantly stricter enforcement of the BLP policy than what the consensus of the community deems acceptable.

Comment by Arbitrators:

Comment by parties:

Comment by others:

I'm not too big of fan of having a remedy essentially against people enforcing BLP; but I put this here because I think it is reasonable to remind editors that the BLP policy is not a cudgel to get one's way in any dispute nor is it an excuse to engage in whatever reversions one wants. This could just be a reminder for GiantSnowman. Galobtter (pingó mió) 15:41, 3 January 2019 (UTC)[reply]

Very problematic:

Importance and application of the BLP policy (2)

1.1) There is widespread agreement in the Wikipedia community regarding the importance of the biographies of living persons policy. The policy has been adopted and since its inception repeatedly expanded and strengthened by the community. In addition, the Arbitration Committee has previously reaffirmed the values expressed through that policy. Fundamental values and practices concerning biographical content has been emphasised in a resolution of the Wikimedia Foundation Board of Trustees and were also expanded and strengthened. If an editor wishes to restore content removed in good faith under the policy, the burden of proof is on those who wish to retain, restore, or undelete the disputed material. Restoring the original content without significant change requires consensus.[6]

-- Alanscottwalker (talk) 14:47, 4 January 2019 (UTC)[reply]

Yeah, actually I'll just scratch that. While in practice BLP is far less rigorously enforced (anyone who did try to remove lots of content from many pages for merely being unsourced would quickly be reverted and told not to) unless in the case of contentious content, and this is meant to be a narrow reminder, the implications here would probably send us in the wrong direction regarding BLP. Galobtter (pingó mió) 15:07, 4 January 2019 (UTC)[reply]

Proposals by User:UninvitedCompany

Proposed principles

WikiProjects cannot override community policy

1) Wikipedia:Consensus, a policy, states that "Consensus among a limited group of editors, at one place and time, cannot override community consensus on a wider scale. For instance, unless they can convince the broader community that such action is right, participants in a WikiProject cannot decide that some generally accepted policy or guideline does not apply to articles within its scope."

Comment by Arbitrators:

@UninvitedCompany: Has a WikiProject influenced this case? I only recall from the background material a couple of passing references to internal projects, and none seemed to indicate projects controlling article content in a relevant way. (I could have missed something.) AGK ■ 23:52, 3 January 2019 (UTC)[reply]

There have been assertions that WP:FOOTY defines certain edits (like updates to statistics without a simultaneous change to the as-of date) as vandalism and encourages the reversion of such edits. There has been the (possibly implicit) claim that the volume of anonymous low-quality edits to WP:FOOTY articles is so great that the only way it can be handled is through liberal use of reverts and blocks and economic use of WP:AGF, WP:BITE, etc. If this is true, I think the root of the matter is that the presumptive inclusion criteria in this subject area are too broad. In addition, I think that some information belongs in a place like WikiData that is better equipped to handle data that is inherently structured and inherently time-series. I would much rather see those changes than have WP:FOOTY become the thin end of a wedge that separates Wikipedia from its core values. Uninvited Company 00:48, 4 January 2019 (UTC)[reply]

Comment by parties:

Comment by others:

Technically true, although it's more nuanced than this and Arbcom almost certainly shouldn't be giving a black-and-white statement like this their imprimatur. Since the participants in WikiProject topic are generally the people best qualified to comment on that topic, a strong consensus from a project for or against a particular course of action shouldn't lightly be disregarded even if broader consensus is in the other direction. Some things, like naming conventions, can quite literally be the result of years of discussion to reach a consensus, and it's entirely understandable that people get irritated when a bunch of people with little interest in the topic in question declare that their consensus outweighs those of the people who actually edit the articles in question and are familiar with the subject and consequently the project just needs to suck it up. (I can give a near-limitless stack of real life examples should anyone doubt that this happens, although I'm sure you're all well aware of the most high profile cases.) ‑ Iridescent 22:44, 3 January 2019 (UTC)[reply]

Agree. The difference between WP:FOOTYN and WP:NFOOTY is an example Hhkohh (talk) 00:51, 4 January 2019 (UTC)[reply]

Closing discussions

2) Wikipedia:Closing discussions discourages editors from closing discussions too soon. Premature closure of discussions undermines the emergence of a genuine consensus.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Administrators

3) Wikipedia:Administrators, a policy, states: "Administrators are expected to lead by example and to behave in a respectful, civil manner in their interactions with others.... Administrators should strive to model appropriate standards of courtesy and civility to other editors."

Comment by Arbitrators:

Comment by parties:

Comment by others:

Proposals by 173.228.123.166

Proposed principles

TBD

Proposed findings of fact

Proposed remedies

Note: All remedies that refer to a period of time, for example to a ban of X months or a revert parole of Y months, are to run concurrently unless otherwise stated.

GiantSnowman restricted (1RR)

1) GiantSnowman is prohibited from making more than one revert to any page in any 24-hour period, excluding pages in his own userspace. The usual exceptions do not apply.

Comment by Arbitrators:

Comment by parties:

Comment by others:

From Wikipedia:Arbitration/Requests/Case/Kww_and_The_Rambling_Man/Proposed_decision#Kww_restricted_(1RR). 173.228.123.166 (talk) 08:51, 5 January 2019 (UTC)[reply]

GiantSnowman restricted (3RR)

2) GiantSnowman is prohibited from making more than 3 total reverts to Wikipedia mainspace, project-wide, in any 24-hour period. The usual exceptions do not apply.

Comment by Arbitrators:

Comment by parties:

Comment by others:

I don't know if this has been done before but we should do it a lot. Overzealous reverters do immense harm to the project, and very little good. I left out the "own userspace" exemption since that's not mainspace anyway. 173.228.123.166 (talk) 08:51, 5 January 2019 (UTC)[reply]

Too serious. Major opposition to me Hhkohh (talk) 09:41, 5 January 2019 (UTC)[reply]

Proposals by Fram

Proposed findings of fact

Too many of GiantSnowmans recent blocks were incorrect, and his replies show no understanding of why these blocks were problematic.

Proposed remedies

Note: All remedies that refer to a period of time, for example to a ban of X months or a revert parole of Y months, are to run concurrently unless otherwise stated.

GiantSnowman desysopped

1) The admin status of GS is revoked. They can reapply through RFA.

Comment by Arbitrators:

Procedural note: This proposal is already being proposed under Galobtter's proposals above. Let's keep the discussion in one place there just for simplicity. Newyorkbrad (talk) 16:55, 7 January 2019 (UTC)[reply]

Comment by parties:

Comment by others:

General discussion

Comment by Arbitrators:

Comment by parties:

Comment by others:

[1] Evidence by Fram § GiantSnowman misused rollback

[2] Evidence presented by Bellezzasolo § Further to UninvitedCompany

[3] Evidence by Fish and karate, "Despite all these…" → "…valid edits"

[4] Evidence by Fram § During this evidence phase

[a]

[b]

[c]

[d]

@@ Line 948: / Line 948: @@
 :::I'm sorry but he's been blocking users for making correct and sourced edits, while defending doing so and showing absolutely no indication that he's going to stop blocking people for making correct and sourced edits. How does that NOT rise to the level where it's at the very least a consideration for you? And we're not even talking about collateral damage in mass rollback, but manual rollback and blocking, and claiming to have manually reviewed the edit in question and simply defending it with that it "appeared" to be vandalism, even though the source did certainly have that data... A source that it was GS himself that added I might add so couldn't possibly have been a case of claiming it was due to unreliable source. So the problem isn't so much reverting alone, the problem as I see it, is the reverting while claiming it being vandalism and the blocking that is the main issue. So while desysop would not solve his ability to undo edits, it would solve the blocks and would take the edge of his templating (even if it doesn't prevent them either) of users that are making correct edits. It would also send the message that the community doesn't accept that it's correct to revert edits that are correct, though that might be possible using lesser methods but to not even consider it seems baffling to me.[[Special:Contributions/84.219.252.47|84.219.252.47]] ([[User talk:84.219.252.47|talk]]) 10:05, 8 January 2019 (UTC)
 :::Sorry GS but you have. And it would be in evidence, if clerks had actually posted evidence mailed to them but they're seemingly as slow on that as they are in reposting legacypac's evidence from the clerks page, seeing as how that's what they're demanding from IP editors. You can however see the evidence talkpage discussion regarding 2A02:C7F:9E12:8F00:6C51:14D8:1B23:F46C which you blocked, and every single edit they made, was correct and properly sourced. And that's just one of many examples. (I've mailed in 8 different ones, all of which you've blocked after making only correct and sourced edits).[[Special:Contributions/84.219.252.47|84.219.252.47]] ([[User talk:84.219.252.47|talk]]) 10:22, 8 January 2019 (UTC)
+:::You say it's a sock... But you have provided no evidence for that and there's no SPI saying it. All there is is that you say it's a sock of someoneone, and that's it. But even if true, it doesn't change the fact that you have indeed blocked a user that has only made correct and sourced edits.[[Special:Contributions/84.219.252.47|84.219.252.47]] ([[User talk:84.219.252.47|talk]]) 10:28, 8 January 2019 (UTC)
 ====GiantSnowman is cautioned====