Target dates: Opened 6 March 2024 • Evidence closes 20 March 2024 • Workshop closes 27 March 2024 • Proposed decision to be posted by 3 April 2024
Scope: The intersection of managing conflict of interest editing with the harassment (outing) policy, in the frame of the conduct of the named parties.
Public evidence is preferred whenever possible; private evidence is allowed (arbcom-en-bwikimedia.org).
Case clerks: Firefly ( Talk) & Amortias ( Talk) Drafting arbitrators: Aoidh ( Talk) & Barkeep49 ( Talk) & Maxim ( Talk)
Wikipedia Arbitration |
---|
|
Track related changes |
I note that the case scope includes the intersection of managing conflict of interest editing with the harassment (outing) policy
, and that several Arbs commented on the case request page that they wish that editors would be more inclined to email the Committee instead of just assuming that ArbCom already knows.
The
COI guideline refers editors to the
outing policy as taking precedence, and the latter says in part: Nothing in this policy prohibits the
emailing of personal information about editors to individual administrators,
functionaries, or arbitrators, or to the Wikimedia Foundation
. In context, please note that emailing ArbCom is not currently emphasized, and editors are likely to look elsewhere instead. It is also in terms of "nothing prohibits", rather than the importance of reporting. The
paid editing page likewise only refers to emailing Checkusers or a "paid" email address, with no mention of ArbCom.
Circa 2015–16, the community held very extensive discussions on how to report COI editing, and there are walls of text in the harassment policy talk page archives. But for a tl;dr, I want to point ArbCom to this 2016 discussion: [1], which I think gets at what is most relevant now. I see (with a bit of embarrassment, now) myself and multiple other editors saying that emailing ArbCom sounds like a bad idea; there are also then-members of ArbCom saying that ArbCom doesn't have the resources to deal with private evidence of COI/paid editing. (There's also discussion of a failed proposal to set up a mailing list of functionaries, to whom private evidence would be emailed. The failed proposal is here: [2], and the RfC rejecting it is here: [3].)
WMF posted their position here: [4], and the community discussed it here: [5].
This case should be informed by this history, and this is a good time to reevaluate it for present-day needs. Since ArbCom sets its own policies and procedures, this case may be an opportunity for ArbCom to take, for itself, a more active role as someone to contact with private information about COI/paid editing. -- Tryptofish ( talk) 21:09, 6 March 2024 (UTC)
"Paid editing" is how we usually refer to edits made for or with financial compensation; what the
Terms of Use call paid contributions
. It is perhaps an unfortunate choice of words, because people sometimes take them at face value and assume it refers to only literally being paid to make an edit. However, the relevant policies make it clear that they are intended to apply to any contribution where there is a financial conflict of interest
present. From
Wikipedia:Paid-contribution disclosure § Additional notes on who must disclose (emphasis added to this and subsequent quotes):
Users who are compensated for any publicity efforts related to the subject of their Wikipedia contributions are deemed to be paid editors, regardless of whether they were compensated specifically to edit Wikipedia.
And Wikipedia:Conflict of interest § Paid editing:
Being paid to contribute to Wikipedia is one form of financial COI; it places the paid editor in a conflict between their employer's goals and Wikipedia's goals. [...] More generally, an editor has a financial conflict of interest whenever they write about a topic with which they have a close financial relationship.
This isn't the place to get into why the policies are worded in this way. Suffice to say, the basic principle, set out in
Wikipedia:Conflict of interest § COI is not simply bias, is that COI is not just a problem of quid-pro-quo advocacy, but of a tendency to bias that we assume exists when [an editors] roles and relationships conflict
.
As specifically stated in Wikipedia:Conflict of interest § Paid editing:
[A close financial relationship] includes being an owner, employee, contractor, investor or other stakeholder.
Immediately after defining edits with a financial conflict of interest as a form of "paid editing", Wikipedia:Conflict of interest § Paid editing goes on to say:
The Wikimedia Foundation requires that all paid editing be disclosed.
Community consensus clearly forbids the use of admin tools as part of paid editing:
Administrator tools may not be used as part of any paid editing activity, except as a Wikipedian-in-Residence, or when the payment is made by the Wikimedia Foundation or an affiliate of the WMF.
— Wikipedia:Administrators § Misuse of administrative tools
If you are an administrator, you must not use administrative tools for any paid-editing activity (except when related to work as a Wikipedian-in-residence, or as someone paid by the Wikimedia Foundation or an affiliate).
— Wikipedia:Conflict of interest § Paid editing
Administrators making paid edits are subject to the same disclosure requirements as all other users, and are not permitted to use special privileges for paid editing.
— Wikipedia:Paid-contribution disclosure § Administrators
Historically such actions, if substantiated, have led to a removal of tools by the Arbitration Committee (see e.g. Wikipedia:Arbitration/Requests/Case/Conduct of Mister Wiki editors § Salvidrim! desysopped).
In the case request, some suggested that Nihonjoe may have fallen afoul of changing (i.e. tightening) community expectations regarding the scope and management of COIs. This is not the case:
no editor can be an administrator or bureaucrat and a paid advocate at the same time. The bright-line rule was instituted in 2018, following a RfC requested by ArbCom.
To claim that any kind of COI automatically means "paid editing" is a can of worms you don't want to open. For example, I've worked in the UV industry for decades, and when making edits in that area, I had a disclaimer on my user page. Some of my work here included uploading example images of items that had the brand of the company I worked for. (example: [9]) Did it benefit the company? Probably not but some may argue it does. It provided an example image of a common product that was readily available to me, rather than me buying an outside product to photograph. The majority of my related uploads were not company branded. The goal was to expand the articles, provide examples and I managed the COI by not adding the company name, nor slanting my edits to make them look better, nor adding images just to upload the company logo. I am considered expert in the field, so the articles benefited from the work, the company did not directly benefit. But it is still a (then declared) COI. Saying any COI is paid editing would automatically disqualify me from having the admin bit, as true "paid editing" has a clear consensus to be incompatible with adminship, and would have far reaching, damaging effect here.
This means that a professor that makes an edit about the university they teach at is a paid editor, because that university pays his salary, so he can not continue to hold the admin bit. You can't just carve out exceptions for professors over us lowly businessmen, after all, a job is a job, and making edits relating to your source of income the same. Some universities are FOR PROFIT, after all. What if the professor makes edits related to their FIELD, but their university is known as the only university studying that field? Isn't that a COI similar to mine, where it may incidentally promote their university? They indirectly benefit, so if COI is the same as paid editing, they must hand in the admin bit. COI is a fuzzy line, not a clear cut thing, and it is more common than most think. It is also manageable.
Most everyone has a COI of some kind, because most of us have jobs or affiliations that create the conflict of interest. Whether you belong to a social club (Lions Club, Optimists Club, etc), work at any job with any level of expertise, or a barista at Starbucks, any edits you make to either the company or related articles are a conflict. How we manage those conflicts is what matters. This is NOT the same thing as plain speak "paid editing" as a traditional 3rd party contractor, nor is it the same as working for XYZ, Inc. and part of your job title includes managing social media and thus making edits on Wikipedia (paid but in between "contractor" and "simple COI", as the damage is limited in scope) If you decree that a simple COI is the same as paid editing, you are going to need to desysop a lot of people, including me. Many have minor COI and don't think to declare because it isn't abused, but you will see cases popping up if you overreach here.
Note, this doesn't speak to the merits of this particular case, which I am not privy to all the details of, as most is private. I just don't want to see Arb shoot itself in the foot by declaring "COI == Paid editing". If anything, it needs to clarify that they are not the same for the purpose of adminship. Dennis Brown - 2¢ 01:11, 8 March 2024 (UTC)
In 2008, while Nihonjoe was an admin, he inserted text about the above named company into the Provo, Utah article [10]. An editor later removed that information from the article, saying it seemed like advertising and non-neutral [11]. Nihonjoe reverted that editor within hours [12].
The same editor who tried to remove the information then raised concerns about the HWS article on that talk page [13] and would express concerns that someone with ties to the company had contributed to the article [14]. Nihonjoe's response was that "any article about a company is going to be somewhat promotional" [15] and then he turned up at the user's talk page to accuse that other editor of having a blatant POV [16].
At Wikipedia:Articles for deletion/Aquaveo in February, Nihonjoe said simply that the article in question was about "one of many topics I find interesting" and asked for the page to be userfied, without admitting he worked for the company in question [17]. He would later accuse the editor who nominated the page for deletion of harassment [18]. (Nihonjoe would later change his tune and admit he only began working on the article after he started working for the company [19])
Nihonjoe in February denied having any conflict of interest with Butler [20]. After some prodding by members of this committee while the case was pending, Nihonjoe listed D. J. Butler as one of several articles for which he has a conflict of interest -- see User:Nihonjoe/Contribs/Intro -- because he "published a collection of his short fiction."
Nihonjoe has gotten both the Butler article and the now deleted Aquaveo article on the main page through WP:DYI. See Template:Did_you_know_nominations/D._J._Butler and Template:Did you know nominations/Aquaveo. Neither of those are listed at User:Nihonjoe/DYK.
-- Jessintime ( talk) 15:07, 8 March 2024 (UTC)
The D. J. Butler article was first edited by me in 2019, two years before I had any COI regarding that subject (I published a collection of their work in July 2021, and they had a story they donated for a charity anthology published in February 2021). It's not uncommon for me to submit a DYK for article I create or greatly expand, either. Them not being listed at User:Nihonjoe/DYK is likely just an oversight and completely irrelevant.
The Aquaveo article has already been discussed elsewhere, and I see no need to rehash things here.
The Heritage Internet Technologies entry on the Provo, Utah page followed the same format as other entries there (a link to the article and an explanation of why the company was notable, supported by reliable sources), and all of the information in that paragraph was supported by the included article from Inc., which is considered a very reliable source for business information. ··· 日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 18:10, 8 March 2024 (UTC)
would have a COI now due to publishing work [he has] done, but not when they were created.
Considering Nihonjoe has identified the relevant publishing work as having taken place in 2021, his 2022 edits were therefore done with an (at the time undeclared) COI. AddWitty NameHere 20:20, 8 March 2024 (UTC)
Representing evidence of now-(rightly) blocked sock. Interesting points in the chronology are raised, unfortunately questioning much of the accepted chronology, and probably require further investigation in the context of the broader narrative. ——Serial Number 54129 21:45, 8 March 2024 (UTC)
In 2010 Nihonjoe wrote a draft article for Action Target which he has only recently declared was done while he was a temporary employee. [21] Per that declaration he seems to think he now has "no COI" for his subsequent edits, since he had left that role by the time he moved it into mainspace (also in 2010 [22]). What he doesn't mention is that no other person edited that article before he moved it, and it was written as a draft in his personal user space.
In 2014 Nihonjoe reverted a user named "Action Target" trying to remove a small amount of content from Action Target [23] that was essentially the same as that which was in the article when Nihonjoe wrote it as a draft. In doing so he advised them "Please especially take note of our conflict of interest guideline. As you are likely directly related to the company in question (given your username), it is generally recommended that you do not directly edit the article." [24]
In 2017 when the user returned and self identified as an employee of Action Target seeking Nihonjoe's input regarding updating the company logo (which Nihonjoe had originally uploaded), Nihonjoe soft blocked them for a username violation. [25]
With the benefit of hindsight only, it is hard to see how Nihonjoe thought he was acting in the best interests of Wikipedia by continuing to edit articles only he knew he had written while having a direct financial conflict of interest.
Articles he knew at the time had never been reviewed by anyone who knew he had written them with a COI. Which observers would certainly not have thought was the situation as they were seeing it. Not given his status and given he was happily giving advice to new users with a suspected or declared conflict, as he reverted their edits to content he had written with an actual and active COI of equal significance.
It is hard to draw any firm conclusions as to intent, given Nihonjoe's very limited public statements on these matters, but given the need for trusted users to be accountable and transparent and the fact COI is about appearances as much as it is proveable intent or even effect, that is in itself surely a cause for concern.
Action Johnson (
talk) 15:50, 8 March 2024 (UTC)
The former identified by e.g. Trypotofish, the latter by e.g. Fram. All of them are, of course, severe breaches of policy, guideline, terms of use, and etiquette, to say the least, on Nihonjoe's part. But what is worse for the project and its members is the breach of trust. Nihonjope has lied to people, either outrightly or by omission. Poor lack of candour from a holder of permissions; needs examination. ——Serial Number 54129 17:57, 12 March 2024 (UTC)
still waiting for a confirmation source, but he just passed away according to several well-known authors, protecting to prevent vandalism. There was no recent history of vandalism [26].
revert application of full protection per WP:PREEMPTIVE...I can't think of any other deaths that were full protected, and not sure why this would be any different (no recent history of abuse).
DanCherek ( talk) 21:50, 8 March 2024 (UTC)
Persistent disruptive editing: Slow edit war happening. Take it to the talk page and come to a consensus rather than arguing via edit summary..
DanCherek ( talk) 21:50, 8 March 2024 (UTC)
It is rather ridiculous that we still have to pretend that Nihonjoe's real life identity is off-limits here, making it much harder to have a practical discussion of his COI edits, where editors (not just passive ArbCom members) may have a meaningful discussion, elaborating (or contradicting) claims made by others. Worse, people can continue to proclaim that we should be very careful and vigilant about outing, for the sake of their privacy, safety, family...
In reality, Nihonjoe has edited about things very close to his life and work for at least 15 years, with many COI and PAID issues, and at least from time to time in a problematic manner. But we are not allowed to mention his name, company, publications. So I can't link to his own Wikidata creations of entries for his supposed real name, own company, other employees of the company, publications from the company, and people they published. Because, well, despite the few reluctant COI declarations, they haven't outright stated that they are that person, so we should pretend that it is some dangerous secret (well, I guess it is a somewhat dangerous secret for them, it would be quite embarassing if people found out that they were giving themselves glowing reviews on review sites with the nihonjoe handle I guess). Which also makes it impossible to provide evidence in public that e.g. already in 2018, the year before Nihonjoe created the DJ Butler article, they called Butler their "good friend" elsewhere.
His incomplete User:Nihonjoe/Contribs/Intro COI declarations seem to indicate a lack of knowledge, even now, of what COI editing is, with the weird repeated insistence on whether they created an article or not, as if that change the nature of the COI in any way.
Missing, for example, is an online wiki where they are an admin, and where they have not only used it often as a source here, but insisted in a discussion that it is a reliable source (contrary to the own claims of the site) without as far as I can see disclosing his COI while doing this. There is quite a big difference between "as a neutral observer, I consider this a reliable source" or "as a major contributor and admin to this source, I consider it to be reliable". But even though they use the same handle there as here, I may not link to it, as, you guessed it, that would presumably be outing somehow, and a blockable offense. Fram ( talk) 14:59, 11 March 2024 (UTC)
Oh well, no reason to be coy about it. Nihonjoe brought Brandon Sanderson, BYU alumnus, to GA status, in part by adding numerous citations to the Internet Speculative Fiction Database [30]. The ISFDB is a wiki, see their general disclaimer. The information on Brandon Sanderson, which Nihonjoe used to turn the page into a GA, was verified on the ISFDB during the same period by an admin named ... nihonjoe [31]. Now, I have no way to know if they are the same or not. Would be quite an unhappy coincidence if not. But if they are the same, then there isn't much outing involved if they use the same username and adds links to the site. And if this is considered outing, then our outing policy truly needs adjustments. Oh, and the above mentioned discussion about the reliability of the ISFDB is at Talk:Dan Wells (author)#cns and bsns. An article about a Mormon and BYU alumnus of course, extensively edited by BYU editors (see my new section below), and where Nihonjoe has a direct COI (not declared at the time, declared now on his user page). Fram ( talk) 10:33, 12 March 2024 (UTC)
Apart from instances mentioned by others, and ignoring perhaps barely acceptable protections like at Takao Yaguchi, where an IP had dared to format references differently, there also is what seems to be much more obvious misuse at Japanese archipelago. In June 2021, an editor removed the claim that part of the Japanese archipelago was Russian [32]. Half a year later, another editor adjusted the text as well to align with this [33]. Months later, Nihonjoe reverted the June 2021 edit [34], but was reverted a week later by an IP [35] with an edit summary showing that this was not some vandal edit, but part of an ongoing content dispute. So, the next day Nihonjoe reverts again [36] and then protected the page in their preferred version [37] because of "persistent vandalism", depsite there being no evidence of vandalism or persistence (two edits and editors nearly a year apart?). And sure enough, the "vandalism" was reinstated by yet another GF editor [38] and remains in the article as of now. It may deserve a talk page discussion, but it isn't or wasn't any kind of vandalism or protect-worthy. Fram ( talk) 14:59, 11 March 2024 (UTC)
The more I (and others) look into it, the more clear it becomes that beyond the individual problems of Nihonjoe and his COI/PAID editing, we seem to have an issue with a walled garden of Mormon editors associated with the Brigham Young University (BYU), the Harold B. Lee Library of that university, the Association for Mormon Letters and its AML Awards. Some of the editors involved (those openly associating with Wikipedia:GLAM/Harold B. Lee Library and with (BYU) in their user name) at least do some effort to abide by the WP:PAID rules, although even those are e.g. very reluctant to post COI notices on article talk pages. Others, like Nihonjoe, Thmazing, or P_Makoto, seem to do everything they can to disguise the association and pose as editors without a COI. At Wikipedia:Village pump (miscellaneous)/Archive 77#Wikipedia in Residence: is this a way around conflict of interest rules? a number of issues have been raised. One can also see e.g. Wikipedia:Articles for deletion/Brandon Dayton where Thmazing votes keeps without disclosing his clear COI, or Template:Did you know nominations/Coriantumr (Last Jaredite King) where P-Makoto gives the article a pass without indicating any COI they may have (it later got rejected by a uninvolved editor). Later discussions at Talk:Coriantumr (son of Omer) are also of the same variety. Or when Nihonjoe edits and Rachel Helps reviews to get an article to pass GA (about an artist whose masterpiece hangs in the BYU, of course) at Talk:William Bliss Baker/GA1. Other editors have expressed concerns about the promo nature of the articles, DYKs and GAs from the BYU editors, see e.g. Talk:Orson Scott Card/GA1. See also the Dan Wells issues highlighted in an above section. This is just from a cursory glance through some pages, I guess more examples can easily be found. Fram ( talk) 10:33, 12 March 2024 (UTC)
I'll not elaborate on how Primefac was using their admin and oversight tools in an involved way in the build-up to this case, I guess that bit is well-known by now.
12 March, at 10.33, I posted about a discussion at the Village Pump as part of my evidence [39]. 4 hours later Primefac suddenly turns up at that discussion to oversight posts "outing" an editor [40], a part of the "walled garden" my evidence talked about (please note that the bits they redacted were not posted by me). Primefac, as a party to the case (because of involved actions no less) was probably the least appropriate person to perform these actions.
Discussion followed at User talk:Horse Eye's Back/Archives/2024/March#Comments directed at other users where Primefac claimed not to be involved in the ongoing case despite being one of the only four named parties(!), claimed not to have noticed that the posts they suppressed had to do with BYU ("I somehow missed the original BYU connection.") and that they hadn't seen the post I made at the case.
Even if one believes all this to be true, they were after that discussion clearly aware that this all tied in to the case they are a party to (for involved actions). Nevertheless, they again felt the need to be the one to pull the trigger [41]. (the above was sent privately to ArbCom yesterday, with some more private elements: Primefac has since again oversighted things in that and related discussions). Fram ( talk) 08:14, 14 March 2024 (UTC)
I don't know if this is the right place or if it's particularly germane to bring this up, but given Fram's expansion of his evidence to include PAID/COI editing by other AML-affiliated editors, I want to note that I emailed ArbCom about this in mid-January. This was the report I was referring to in my prelim statement (arbs can repost my email if they want). I don't know what the normal timeframe is for these reports to be discussed and actioned by the committee, but perhaps some of the drama and outing could have been avoided if ArbCom had put out some public statement that they would be looking/had already looked into allegations of COI editing among LDS (or some other appropriately vague descriptor) editors so that those of us who were aware of it could know it already had ArbCom's attention. I think that would have made it less likely that the problem would escalate into on-wiki conflicts so quickly. JoelleJay ( talk) 23:23, 13 March 2024 (UTC)
Nihonjoe appears to have a history of using their "admin presence" to intimidate other editors and to run interference for a paid editor with whom they had an undisclosed COI.
On December 2020 SlimVirgin (dec.) went to User talk:Rachel Helps (BYU) to discuss concerns around "COI and PAID." But it wasn't Rachel Helps who responded, it was Nihonjoe immediately steps in with a full throated defense of Rachel Helps [42] without disclosing a COI. These concerns were then dismissed by Barkeep49 [43] with what is in hindsight a great deal of naiveté. Nihonjoe then continues, making claims like "As I've pointed out before, Rachel has no dog in this fight." which we now know in hindsight are false and given their inside knowledge Nihonjoe would have known was was false at the time. Slimvirgin, Nihonjoe, Barkeep49, and Rachel Helps sparred over this for a few days before Rachel Helps put an end to the discussion by declaring that she was "Resigning" [44] rendering the discussion more or less moot. In hindsight SlimVirgin was right. This resignation was apparently temporary, Rachel Helps unresigned five months later [45]... By which time SlimVirgin was conveniently incapacitated so unable to raise any objection. Part of me suspects that if SlimVirgin's illness had not progressed this issue would have been addressed before I ever came across it.
In December 2022 COI and PAID concerns were again raised on User talk:Rachel Helps (BYU) (by yours truly), again Nihonjoe stepped in to strongly defend Rachel Helps (BYU) with comments like "You're beginning to sound like a witch hunter here." [46] without disclosing a COI. They also appeared to deliver an administrative warning against "harassment." In hindsight we know that the concerns raised were legitimate. They made statements like "She's a model editor with a very long track record of excellent edits." without declaring a COI. In hindsight we know that such claims were false, Helps was never a model editor and their entire track record is littered with bad edits. Nihonjoe would have been in a position to know that such claims were false, they would have been aware of Rachel Helps (BYU)'s undisclosed COI editing. That to me looks like they were actively covering up issues they knew existed and which directly involved them. Nihonjoe does not appear to habitually gatekeep user talk pages, User talk:Rachel Helps (BYU) has the second most edits of any besides his own. At the time I wondered what made Rachel special, why did she get a Admin bodyguard? Well now we know, so what are we going to do about it? Its not an abuse of tools but its definitely an abuse of the trust the community placed in them. Horse Eye's Back ( talk) 16:29, 14 March 2024 (UTC)
I have also submitted private evidence to @ Primefac: in a related discussion, I trust that if there is anything relevant to this case which the committee was not already aware of that they have passed it on. Horse Eye's Back ( talk) 16:29, 14 March 2024 (UTC)
All of the recent relevant discussions of COI (like this one at AN prior to this case and this one that's ongoing at ANI) indicate that some members of the community feel that any editing in the presence of a COI is inherently problematic, while others feel that editing in the presence of a COI is only problematic if there is a substantive problem with the edits being made (e.g., see Piotrus' statement). For many people (perhaps especially in the first group), these feelings are quite strong. One thing the discussion at AN illustrates is the lack of an obvious compromise position between those two views, and the inability for many people with one view to understand or appreciate the other view. -- JBL ( talk) 19:50, 17 March 2024 (UTC)
Both a plain reading of the text of the COI policy quoted by Joe Roe and basic common sense indicate that a key conclusion of his evidence (the relevant policies [on paid editing] ... are intended to apply to any contribution where there is a "financial conflict of interest" present
) is entirely wrong: the evidence here is the exact text he quotes, which directly contradicts the conclusion by unambiguously drawing a distinction between paid editing and editing with a financial conflict of interest. ArbCom should reject any reading of policy that suggests that a distinction being drawn between X and Y, and a statement that X is a special case of Y, actually means that X and Y are the same; and therefore should also reject any conclusions that are based on this line of reasoning. --
JBL (
talk) 19:50, 17 March 2024 (UTC)
Following several evidence submissions above; following the ANI thread titled "Follow up from VPM" ( live, permalink) and other project page discussions; following several WPO threads — there is a broader issue pertaining to some BYU-affiliated editors. This primarily concerns them failing to either disclose their WP:COI, and do so fully, as well as once the disclosures have been provided, to actually adhere to the COI and/or WP:PAID rules.
BYU also stands in contrast to conventional academic institutions in that there is no academic freedom — because religion is compulsory, an expressed requirement for both work and study. Which, in my view, does not represent freedom of religion but the tyranny of religion. This problem is further compounded when aspects for-or-against that religion, it being the LDS Church, are soft-promoted ( WP:PROMO) by COI-violating, BYU-affiliated editors. My position is that, regardless if the community addresses this, ARBCOM should strive towards more holistic coverage.
I am strongly against Risker's position that seemingly opens the door for WP:OUTING to be used as a device to evade and avoid scrutiny of COI-violating editing by COI-violating editors. I especially disliked the hyperbole about safety in this particular instance, since it does not involve a contentious topic, so it's highly doubtful there are fanatics out there to whom any of this might serve as a call to action (be it hydrology or LDS-driven, which to credit the latter, little violence is attributed to in the modern age).
Private evidence is all well and good—if it gets a proper review, at least—but I also think that, within reason, one ought to take some responsibility when COI editing. OUTING should not be a cure-all or loophole that facilitates COI (and/or PAID) violations. Especially when it concerns habitual violators. Needless to say, this issue has made this case especially challenging to navigate.
While arbitrator Primefac has rightly apologized and recused—though not from additional LDSuppression actions—I believe that arbitrator Firefly should also recuse ( Yngvadottir's evidence)
Arbitrators ToBeFree and HJ Mitchell should also consider recusing since their comments in the original (Kashmiri) AN thread appeared reflexively supportive of Nihonjoe, despite evidence that even-at-the-time was highly concerning. In contrast to arbitrator Moneytrees who, from the outset, treated the subject matter with the seriousness that it deserves (evidence mostly suppressed).
Obviously there will be no such recusals, but I doubt I am the only who thinks this. Critically, there is a loss of confidence which is not insignificant, and one which, in my view, extends to much of the remaining committee. El_C 07:47, 19 March 2024 (UTC)
The Foundation's own guidance on the subject specifically suggests that OUTING concerns cannot be used to avoid COI disclosures:
We also think that some degree of transparency in investigations helps the communities do a better job combating undisclosed [editing ...] It's also important to remember that WP:OUTING can't be used as a way to avoid the disclosure requirements in the Terms of Use.
(It's worth noting that ArbCom published essentially their own dissent on the broad strokes of the Foundation's view, which brings us to now.)
As presented in evidence above, the attitude by the Committee when informed of the COI was not to do anything or at best maybe give a quiet word to Nihonjoe, in which case the more broad COI problems would not have surfaced; and arbitrators specifically tried to shut down any discussion on wiki without even a promise to investigate privately. Without the potentially-outing post on-wiki, Nihonjoe would still be editing without any of the disclosures he has since fessed up to. The very real damage of a user with advanced permissions would continue; meanwhile, there's no actual evidence this "doxxing", if it can be considered such, came with external harms.
This is just the latest in a long series of situations where it took outside, public pressure for the Committee or functionaries to take corrective action, from Laura Hale to Qworty to Tenebrae. Fundamentally if Wikipedians are expected to abide by OUTING without regard to the fact that COI editors use it as a screen to avoid scrutiny, the private channels to report said editing need to actually result in action, and judging by Moneytree's comments on the case request that cannot be expected in the present climate. Der Wohltemperierte Fuchs talk 22:50, 19 March 2024 (UTC)
before using the last evidence template, please make a copy for the next person
Place argument and diffs which support your assertion; for example, your first assertion might be "So-and-so engages in edit warring", which should be the title of this section. Here you would show specific edits to specific articles which show So-and-so engaging in edit warring.
Below is a partial list of diffs which were shared as part of private evidence. February 19, 2016 February 19, 2016 October 28, 2019 August 25 2023 March 5 2024
Links that would have directly or indirectly OUTED any editors are omitted from this list. Barkeep49 ( talk) 03:10, 21 March 2024 (UTC)
Target dates: Opened 6 March 2024 • Evidence closes 20 March 2024 • Workshop closes 27 March 2024 • Proposed decision to be posted by 3 April 2024
Scope: The intersection of managing conflict of interest editing with the harassment (outing) policy, in the frame of the conduct of the named parties.
Public evidence is preferred whenever possible; private evidence is allowed (arbcom-en-bwikimedia.org).
Case clerks: Firefly ( Talk) & Amortias ( Talk) Drafting arbitrators: Aoidh ( Talk) & Barkeep49 ( Talk) & Maxim ( Talk)
Wikipedia Arbitration |
---|
|
Track related changes |
I note that the case scope includes the intersection of managing conflict of interest editing with the harassment (outing) policy
, and that several Arbs commented on the case request page that they wish that editors would be more inclined to email the Committee instead of just assuming that ArbCom already knows.
The
COI guideline refers editors to the
outing policy as taking precedence, and the latter says in part: Nothing in this policy prohibits the
emailing of personal information about editors to individual administrators,
functionaries, or arbitrators, or to the Wikimedia Foundation
. In context, please note that emailing ArbCom is not currently emphasized, and editors are likely to look elsewhere instead. It is also in terms of "nothing prohibits", rather than the importance of reporting. The
paid editing page likewise only refers to emailing Checkusers or a "paid" email address, with no mention of ArbCom.
Circa 2015–16, the community held very extensive discussions on how to report COI editing, and there are walls of text in the harassment policy talk page archives. But for a tl;dr, I want to point ArbCom to this 2016 discussion: [1], which I think gets at what is most relevant now. I see (with a bit of embarrassment, now) myself and multiple other editors saying that emailing ArbCom sounds like a bad idea; there are also then-members of ArbCom saying that ArbCom doesn't have the resources to deal with private evidence of COI/paid editing. (There's also discussion of a failed proposal to set up a mailing list of functionaries, to whom private evidence would be emailed. The failed proposal is here: [2], and the RfC rejecting it is here: [3].)
WMF posted their position here: [4], and the community discussed it here: [5].
This case should be informed by this history, and this is a good time to reevaluate it for present-day needs. Since ArbCom sets its own policies and procedures, this case may be an opportunity for ArbCom to take, for itself, a more active role as someone to contact with private information about COI/paid editing. -- Tryptofish ( talk) 21:09, 6 March 2024 (UTC)
"Paid editing" is how we usually refer to edits made for or with financial compensation; what the
Terms of Use call paid contributions
. It is perhaps an unfortunate choice of words, because people sometimes take them at face value and assume it refers to only literally being paid to make an edit. However, the relevant policies make it clear that they are intended to apply to any contribution where there is a financial conflict of interest
present. From
Wikipedia:Paid-contribution disclosure § Additional notes on who must disclose (emphasis added to this and subsequent quotes):
Users who are compensated for any publicity efforts related to the subject of their Wikipedia contributions are deemed to be paid editors, regardless of whether they were compensated specifically to edit Wikipedia.
And Wikipedia:Conflict of interest § Paid editing:
Being paid to contribute to Wikipedia is one form of financial COI; it places the paid editor in a conflict between their employer's goals and Wikipedia's goals. [...] More generally, an editor has a financial conflict of interest whenever they write about a topic with which they have a close financial relationship.
This isn't the place to get into why the policies are worded in this way. Suffice to say, the basic principle, set out in
Wikipedia:Conflict of interest § COI is not simply bias, is that COI is not just a problem of quid-pro-quo advocacy, but of a tendency to bias that we assume exists when [an editors] roles and relationships conflict
.
As specifically stated in Wikipedia:Conflict of interest § Paid editing:
[A close financial relationship] includes being an owner, employee, contractor, investor or other stakeholder.
Immediately after defining edits with a financial conflict of interest as a form of "paid editing", Wikipedia:Conflict of interest § Paid editing goes on to say:
The Wikimedia Foundation requires that all paid editing be disclosed.
Community consensus clearly forbids the use of admin tools as part of paid editing:
Administrator tools may not be used as part of any paid editing activity, except as a Wikipedian-in-Residence, or when the payment is made by the Wikimedia Foundation or an affiliate of the WMF.
— Wikipedia:Administrators § Misuse of administrative tools
If you are an administrator, you must not use administrative tools for any paid-editing activity (except when related to work as a Wikipedian-in-residence, or as someone paid by the Wikimedia Foundation or an affiliate).
— Wikipedia:Conflict of interest § Paid editing
Administrators making paid edits are subject to the same disclosure requirements as all other users, and are not permitted to use special privileges for paid editing.
— Wikipedia:Paid-contribution disclosure § Administrators
Historically such actions, if substantiated, have led to a removal of tools by the Arbitration Committee (see e.g. Wikipedia:Arbitration/Requests/Case/Conduct of Mister Wiki editors § Salvidrim! desysopped).
In the case request, some suggested that Nihonjoe may have fallen afoul of changing (i.e. tightening) community expectations regarding the scope and management of COIs. This is not the case:
no editor can be an administrator or bureaucrat and a paid advocate at the same time. The bright-line rule was instituted in 2018, following a RfC requested by ArbCom.
To claim that any kind of COI automatically means "paid editing" is a can of worms you don't want to open. For example, I've worked in the UV industry for decades, and when making edits in that area, I had a disclaimer on my user page. Some of my work here included uploading example images of items that had the brand of the company I worked for. (example: [9]) Did it benefit the company? Probably not but some may argue it does. It provided an example image of a common product that was readily available to me, rather than me buying an outside product to photograph. The majority of my related uploads were not company branded. The goal was to expand the articles, provide examples and I managed the COI by not adding the company name, nor slanting my edits to make them look better, nor adding images just to upload the company logo. I am considered expert in the field, so the articles benefited from the work, the company did not directly benefit. But it is still a (then declared) COI. Saying any COI is paid editing would automatically disqualify me from having the admin bit, as true "paid editing" has a clear consensus to be incompatible with adminship, and would have far reaching, damaging effect here.
This means that a professor that makes an edit about the university they teach at is a paid editor, because that university pays his salary, so he can not continue to hold the admin bit. You can't just carve out exceptions for professors over us lowly businessmen, after all, a job is a job, and making edits relating to your source of income the same. Some universities are FOR PROFIT, after all. What if the professor makes edits related to their FIELD, but their university is known as the only university studying that field? Isn't that a COI similar to mine, where it may incidentally promote their university? They indirectly benefit, so if COI is the same as paid editing, they must hand in the admin bit. COI is a fuzzy line, not a clear cut thing, and it is more common than most think. It is also manageable.
Most everyone has a COI of some kind, because most of us have jobs or affiliations that create the conflict of interest. Whether you belong to a social club (Lions Club, Optimists Club, etc), work at any job with any level of expertise, or a barista at Starbucks, any edits you make to either the company or related articles are a conflict. How we manage those conflicts is what matters. This is NOT the same thing as plain speak "paid editing" as a traditional 3rd party contractor, nor is it the same as working for XYZ, Inc. and part of your job title includes managing social media and thus making edits on Wikipedia (paid but in between "contractor" and "simple COI", as the damage is limited in scope) If you decree that a simple COI is the same as paid editing, you are going to need to desysop a lot of people, including me. Many have minor COI and don't think to declare because it isn't abused, but you will see cases popping up if you overreach here.
Note, this doesn't speak to the merits of this particular case, which I am not privy to all the details of, as most is private. I just don't want to see Arb shoot itself in the foot by declaring "COI == Paid editing". If anything, it needs to clarify that they are not the same for the purpose of adminship. Dennis Brown - 2¢ 01:11, 8 March 2024 (UTC)
In 2008, while Nihonjoe was an admin, he inserted text about the above named company into the Provo, Utah article [10]. An editor later removed that information from the article, saying it seemed like advertising and non-neutral [11]. Nihonjoe reverted that editor within hours [12].
The same editor who tried to remove the information then raised concerns about the HWS article on that talk page [13] and would express concerns that someone with ties to the company had contributed to the article [14]. Nihonjoe's response was that "any article about a company is going to be somewhat promotional" [15] and then he turned up at the user's talk page to accuse that other editor of having a blatant POV [16].
At Wikipedia:Articles for deletion/Aquaveo in February, Nihonjoe said simply that the article in question was about "one of many topics I find interesting" and asked for the page to be userfied, without admitting he worked for the company in question [17]. He would later accuse the editor who nominated the page for deletion of harassment [18]. (Nihonjoe would later change his tune and admit he only began working on the article after he started working for the company [19])
Nihonjoe in February denied having any conflict of interest with Butler [20]. After some prodding by members of this committee while the case was pending, Nihonjoe listed D. J. Butler as one of several articles for which he has a conflict of interest -- see User:Nihonjoe/Contribs/Intro -- because he "published a collection of his short fiction."
Nihonjoe has gotten both the Butler article and the now deleted Aquaveo article on the main page through WP:DYI. See Template:Did_you_know_nominations/D._J._Butler and Template:Did you know nominations/Aquaveo. Neither of those are listed at User:Nihonjoe/DYK.
-- Jessintime ( talk) 15:07, 8 March 2024 (UTC)
The D. J. Butler article was first edited by me in 2019, two years before I had any COI regarding that subject (I published a collection of their work in July 2021, and they had a story they donated for a charity anthology published in February 2021). It's not uncommon for me to submit a DYK for article I create or greatly expand, either. Them not being listed at User:Nihonjoe/DYK is likely just an oversight and completely irrelevant.
The Aquaveo article has already been discussed elsewhere, and I see no need to rehash things here.
The Heritage Internet Technologies entry on the Provo, Utah page followed the same format as other entries there (a link to the article and an explanation of why the company was notable, supported by reliable sources), and all of the information in that paragraph was supported by the included article from Inc., which is considered a very reliable source for business information. ··· 日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 18:10, 8 March 2024 (UTC)
would have a COI now due to publishing work [he has] done, but not when they were created.
Considering Nihonjoe has identified the relevant publishing work as having taken place in 2021, his 2022 edits were therefore done with an (at the time undeclared) COI. AddWitty NameHere 20:20, 8 March 2024 (UTC)
Representing evidence of now-(rightly) blocked sock. Interesting points in the chronology are raised, unfortunately questioning much of the accepted chronology, and probably require further investigation in the context of the broader narrative. ——Serial Number 54129 21:45, 8 March 2024 (UTC)
In 2010 Nihonjoe wrote a draft article for Action Target which he has only recently declared was done while he was a temporary employee. [21] Per that declaration he seems to think he now has "no COI" for his subsequent edits, since he had left that role by the time he moved it into mainspace (also in 2010 [22]). What he doesn't mention is that no other person edited that article before he moved it, and it was written as a draft in his personal user space.
In 2014 Nihonjoe reverted a user named "Action Target" trying to remove a small amount of content from Action Target [23] that was essentially the same as that which was in the article when Nihonjoe wrote it as a draft. In doing so he advised them "Please especially take note of our conflict of interest guideline. As you are likely directly related to the company in question (given your username), it is generally recommended that you do not directly edit the article." [24]
In 2017 when the user returned and self identified as an employee of Action Target seeking Nihonjoe's input regarding updating the company logo (which Nihonjoe had originally uploaded), Nihonjoe soft blocked them for a username violation. [25]
With the benefit of hindsight only, it is hard to see how Nihonjoe thought he was acting in the best interests of Wikipedia by continuing to edit articles only he knew he had written while having a direct financial conflict of interest.
Articles he knew at the time had never been reviewed by anyone who knew he had written them with a COI. Which observers would certainly not have thought was the situation as they were seeing it. Not given his status and given he was happily giving advice to new users with a suspected or declared conflict, as he reverted their edits to content he had written with an actual and active COI of equal significance.
It is hard to draw any firm conclusions as to intent, given Nihonjoe's very limited public statements on these matters, but given the need for trusted users to be accountable and transparent and the fact COI is about appearances as much as it is proveable intent or even effect, that is in itself surely a cause for concern.
Action Johnson (
talk) 15:50, 8 March 2024 (UTC)
The former identified by e.g. Trypotofish, the latter by e.g. Fram. All of them are, of course, severe breaches of policy, guideline, terms of use, and etiquette, to say the least, on Nihonjoe's part. But what is worse for the project and its members is the breach of trust. Nihonjope has lied to people, either outrightly or by omission. Poor lack of candour from a holder of permissions; needs examination. ——Serial Number 54129 17:57, 12 March 2024 (UTC)
still waiting for a confirmation source, but he just passed away according to several well-known authors, protecting to prevent vandalism. There was no recent history of vandalism [26].
revert application of full protection per WP:PREEMPTIVE...I can't think of any other deaths that were full protected, and not sure why this would be any different (no recent history of abuse).
DanCherek ( talk) 21:50, 8 March 2024 (UTC)
Persistent disruptive editing: Slow edit war happening. Take it to the talk page and come to a consensus rather than arguing via edit summary..
DanCherek ( talk) 21:50, 8 March 2024 (UTC)
It is rather ridiculous that we still have to pretend that Nihonjoe's real life identity is off-limits here, making it much harder to have a practical discussion of his COI edits, where editors (not just passive ArbCom members) may have a meaningful discussion, elaborating (or contradicting) claims made by others. Worse, people can continue to proclaim that we should be very careful and vigilant about outing, for the sake of their privacy, safety, family...
In reality, Nihonjoe has edited about things very close to his life and work for at least 15 years, with many COI and PAID issues, and at least from time to time in a problematic manner. But we are not allowed to mention his name, company, publications. So I can't link to his own Wikidata creations of entries for his supposed real name, own company, other employees of the company, publications from the company, and people they published. Because, well, despite the few reluctant COI declarations, they haven't outright stated that they are that person, so we should pretend that it is some dangerous secret (well, I guess it is a somewhat dangerous secret for them, it would be quite embarassing if people found out that they were giving themselves glowing reviews on review sites with the nihonjoe handle I guess). Which also makes it impossible to provide evidence in public that e.g. already in 2018, the year before Nihonjoe created the DJ Butler article, they called Butler their "good friend" elsewhere.
His incomplete User:Nihonjoe/Contribs/Intro COI declarations seem to indicate a lack of knowledge, even now, of what COI editing is, with the weird repeated insistence on whether they created an article or not, as if that change the nature of the COI in any way.
Missing, for example, is an online wiki where they are an admin, and where they have not only used it often as a source here, but insisted in a discussion that it is a reliable source (contrary to the own claims of the site) without as far as I can see disclosing his COI while doing this. There is quite a big difference between "as a neutral observer, I consider this a reliable source" or "as a major contributor and admin to this source, I consider it to be reliable". But even though they use the same handle there as here, I may not link to it, as, you guessed it, that would presumably be outing somehow, and a blockable offense. Fram ( talk) 14:59, 11 March 2024 (UTC)
Oh well, no reason to be coy about it. Nihonjoe brought Brandon Sanderson, BYU alumnus, to GA status, in part by adding numerous citations to the Internet Speculative Fiction Database [30]. The ISFDB is a wiki, see their general disclaimer. The information on Brandon Sanderson, which Nihonjoe used to turn the page into a GA, was verified on the ISFDB during the same period by an admin named ... nihonjoe [31]. Now, I have no way to know if they are the same or not. Would be quite an unhappy coincidence if not. But if they are the same, then there isn't much outing involved if they use the same username and adds links to the site. And if this is considered outing, then our outing policy truly needs adjustments. Oh, and the above mentioned discussion about the reliability of the ISFDB is at Talk:Dan Wells (author)#cns and bsns. An article about a Mormon and BYU alumnus of course, extensively edited by BYU editors (see my new section below), and where Nihonjoe has a direct COI (not declared at the time, declared now on his user page). Fram ( talk) 10:33, 12 March 2024 (UTC)
Apart from instances mentioned by others, and ignoring perhaps barely acceptable protections like at Takao Yaguchi, where an IP had dared to format references differently, there also is what seems to be much more obvious misuse at Japanese archipelago. In June 2021, an editor removed the claim that part of the Japanese archipelago was Russian [32]. Half a year later, another editor adjusted the text as well to align with this [33]. Months later, Nihonjoe reverted the June 2021 edit [34], but was reverted a week later by an IP [35] with an edit summary showing that this was not some vandal edit, but part of an ongoing content dispute. So, the next day Nihonjoe reverts again [36] and then protected the page in their preferred version [37] because of "persistent vandalism", depsite there being no evidence of vandalism or persistence (two edits and editors nearly a year apart?). And sure enough, the "vandalism" was reinstated by yet another GF editor [38] and remains in the article as of now. It may deserve a talk page discussion, but it isn't or wasn't any kind of vandalism or protect-worthy. Fram ( talk) 14:59, 11 March 2024 (UTC)
The more I (and others) look into it, the more clear it becomes that beyond the individual problems of Nihonjoe and his COI/PAID editing, we seem to have an issue with a walled garden of Mormon editors associated with the Brigham Young University (BYU), the Harold B. Lee Library of that university, the Association for Mormon Letters and its AML Awards. Some of the editors involved (those openly associating with Wikipedia:GLAM/Harold B. Lee Library and with (BYU) in their user name) at least do some effort to abide by the WP:PAID rules, although even those are e.g. very reluctant to post COI notices on article talk pages. Others, like Nihonjoe, Thmazing, or P_Makoto, seem to do everything they can to disguise the association and pose as editors without a COI. At Wikipedia:Village pump (miscellaneous)/Archive 77#Wikipedia in Residence: is this a way around conflict of interest rules? a number of issues have been raised. One can also see e.g. Wikipedia:Articles for deletion/Brandon Dayton where Thmazing votes keeps without disclosing his clear COI, or Template:Did you know nominations/Coriantumr (Last Jaredite King) where P-Makoto gives the article a pass without indicating any COI they may have (it later got rejected by a uninvolved editor). Later discussions at Talk:Coriantumr (son of Omer) are also of the same variety. Or when Nihonjoe edits and Rachel Helps reviews to get an article to pass GA (about an artist whose masterpiece hangs in the BYU, of course) at Talk:William Bliss Baker/GA1. Other editors have expressed concerns about the promo nature of the articles, DYKs and GAs from the BYU editors, see e.g. Talk:Orson Scott Card/GA1. See also the Dan Wells issues highlighted in an above section. This is just from a cursory glance through some pages, I guess more examples can easily be found. Fram ( talk) 10:33, 12 March 2024 (UTC)
I'll not elaborate on how Primefac was using their admin and oversight tools in an involved way in the build-up to this case, I guess that bit is well-known by now.
12 March, at 10.33, I posted about a discussion at the Village Pump as part of my evidence [39]. 4 hours later Primefac suddenly turns up at that discussion to oversight posts "outing" an editor [40], a part of the "walled garden" my evidence talked about (please note that the bits they redacted were not posted by me). Primefac, as a party to the case (because of involved actions no less) was probably the least appropriate person to perform these actions.
Discussion followed at User talk:Horse Eye's Back/Archives/2024/March#Comments directed at other users where Primefac claimed not to be involved in the ongoing case despite being one of the only four named parties(!), claimed not to have noticed that the posts they suppressed had to do with BYU ("I somehow missed the original BYU connection.") and that they hadn't seen the post I made at the case.
Even if one believes all this to be true, they were after that discussion clearly aware that this all tied in to the case they are a party to (for involved actions). Nevertheless, they again felt the need to be the one to pull the trigger [41]. (the above was sent privately to ArbCom yesterday, with some more private elements: Primefac has since again oversighted things in that and related discussions). Fram ( talk) 08:14, 14 March 2024 (UTC)
I don't know if this is the right place or if it's particularly germane to bring this up, but given Fram's expansion of his evidence to include PAID/COI editing by other AML-affiliated editors, I want to note that I emailed ArbCom about this in mid-January. This was the report I was referring to in my prelim statement (arbs can repost my email if they want). I don't know what the normal timeframe is for these reports to be discussed and actioned by the committee, but perhaps some of the drama and outing could have been avoided if ArbCom had put out some public statement that they would be looking/had already looked into allegations of COI editing among LDS (or some other appropriately vague descriptor) editors so that those of us who were aware of it could know it already had ArbCom's attention. I think that would have made it less likely that the problem would escalate into on-wiki conflicts so quickly. JoelleJay ( talk) 23:23, 13 March 2024 (UTC)
Nihonjoe appears to have a history of using their "admin presence" to intimidate other editors and to run interference for a paid editor with whom they had an undisclosed COI.
On December 2020 SlimVirgin (dec.) went to User talk:Rachel Helps (BYU) to discuss concerns around "COI and PAID." But it wasn't Rachel Helps who responded, it was Nihonjoe immediately steps in with a full throated defense of Rachel Helps [42] without disclosing a COI. These concerns were then dismissed by Barkeep49 [43] with what is in hindsight a great deal of naiveté. Nihonjoe then continues, making claims like "As I've pointed out before, Rachel has no dog in this fight." which we now know in hindsight are false and given their inside knowledge Nihonjoe would have known was was false at the time. Slimvirgin, Nihonjoe, Barkeep49, and Rachel Helps sparred over this for a few days before Rachel Helps put an end to the discussion by declaring that she was "Resigning" [44] rendering the discussion more or less moot. In hindsight SlimVirgin was right. This resignation was apparently temporary, Rachel Helps unresigned five months later [45]... By which time SlimVirgin was conveniently incapacitated so unable to raise any objection. Part of me suspects that if SlimVirgin's illness had not progressed this issue would have been addressed before I ever came across it.
In December 2022 COI and PAID concerns were again raised on User talk:Rachel Helps (BYU) (by yours truly), again Nihonjoe stepped in to strongly defend Rachel Helps (BYU) with comments like "You're beginning to sound like a witch hunter here." [46] without disclosing a COI. They also appeared to deliver an administrative warning against "harassment." In hindsight we know that the concerns raised were legitimate. They made statements like "She's a model editor with a very long track record of excellent edits." without declaring a COI. In hindsight we know that such claims were false, Helps was never a model editor and their entire track record is littered with bad edits. Nihonjoe would have been in a position to know that such claims were false, they would have been aware of Rachel Helps (BYU)'s undisclosed COI editing. That to me looks like they were actively covering up issues they knew existed and which directly involved them. Nihonjoe does not appear to habitually gatekeep user talk pages, User talk:Rachel Helps (BYU) has the second most edits of any besides his own. At the time I wondered what made Rachel special, why did she get a Admin bodyguard? Well now we know, so what are we going to do about it? Its not an abuse of tools but its definitely an abuse of the trust the community placed in them. Horse Eye's Back ( talk) 16:29, 14 March 2024 (UTC)
I have also submitted private evidence to @ Primefac: in a related discussion, I trust that if there is anything relevant to this case which the committee was not already aware of that they have passed it on. Horse Eye's Back ( talk) 16:29, 14 March 2024 (UTC)
All of the recent relevant discussions of COI (like this one at AN prior to this case and this one that's ongoing at ANI) indicate that some members of the community feel that any editing in the presence of a COI is inherently problematic, while others feel that editing in the presence of a COI is only problematic if there is a substantive problem with the edits being made (e.g., see Piotrus' statement). For many people (perhaps especially in the first group), these feelings are quite strong. One thing the discussion at AN illustrates is the lack of an obvious compromise position between those two views, and the inability for many people with one view to understand or appreciate the other view. -- JBL ( talk) 19:50, 17 March 2024 (UTC)
Both a plain reading of the text of the COI policy quoted by Joe Roe and basic common sense indicate that a key conclusion of his evidence (the relevant policies [on paid editing] ... are intended to apply to any contribution where there is a "financial conflict of interest" present
) is entirely wrong: the evidence here is the exact text he quotes, which directly contradicts the conclusion by unambiguously drawing a distinction between paid editing and editing with a financial conflict of interest. ArbCom should reject any reading of policy that suggests that a distinction being drawn between X and Y, and a statement that X is a special case of Y, actually means that X and Y are the same; and therefore should also reject any conclusions that are based on this line of reasoning. --
JBL (
talk) 19:50, 17 March 2024 (UTC)
Following several evidence submissions above; following the ANI thread titled "Follow up from VPM" ( live, permalink) and other project page discussions; following several WPO threads — there is a broader issue pertaining to some BYU-affiliated editors. This primarily concerns them failing to either disclose their WP:COI, and do so fully, as well as once the disclosures have been provided, to actually adhere to the COI and/or WP:PAID rules.
BYU also stands in contrast to conventional academic institutions in that there is no academic freedom — because religion is compulsory, an expressed requirement for both work and study. Which, in my view, does not represent freedom of religion but the tyranny of religion. This problem is further compounded when aspects for-or-against that religion, it being the LDS Church, are soft-promoted ( WP:PROMO) by COI-violating, BYU-affiliated editors. My position is that, regardless if the community addresses this, ARBCOM should strive towards more holistic coverage.
I am strongly against Risker's position that seemingly opens the door for WP:OUTING to be used as a device to evade and avoid scrutiny of COI-violating editing by COI-violating editors. I especially disliked the hyperbole about safety in this particular instance, since it does not involve a contentious topic, so it's highly doubtful there are fanatics out there to whom any of this might serve as a call to action (be it hydrology or LDS-driven, which to credit the latter, little violence is attributed to in the modern age).
Private evidence is all well and good—if it gets a proper review, at least—but I also think that, within reason, one ought to take some responsibility when COI editing. OUTING should not be a cure-all or loophole that facilitates COI (and/or PAID) violations. Especially when it concerns habitual violators. Needless to say, this issue has made this case especially challenging to navigate.
While arbitrator Primefac has rightly apologized and recused—though not from additional LDSuppression actions—I believe that arbitrator Firefly should also recuse ( Yngvadottir's evidence)
Arbitrators ToBeFree and HJ Mitchell should also consider recusing since their comments in the original (Kashmiri) AN thread appeared reflexively supportive of Nihonjoe, despite evidence that even-at-the-time was highly concerning. In contrast to arbitrator Moneytrees who, from the outset, treated the subject matter with the seriousness that it deserves (evidence mostly suppressed).
Obviously there will be no such recusals, but I doubt I am the only who thinks this. Critically, there is a loss of confidence which is not insignificant, and one which, in my view, extends to much of the remaining committee. El_C 07:47, 19 March 2024 (UTC)
The Foundation's own guidance on the subject specifically suggests that OUTING concerns cannot be used to avoid COI disclosures:
We also think that some degree of transparency in investigations helps the communities do a better job combating undisclosed [editing ...] It's also important to remember that WP:OUTING can't be used as a way to avoid the disclosure requirements in the Terms of Use.
(It's worth noting that ArbCom published essentially their own dissent on the broad strokes of the Foundation's view, which brings us to now.)
As presented in evidence above, the attitude by the Committee when informed of the COI was not to do anything or at best maybe give a quiet word to Nihonjoe, in which case the more broad COI problems would not have surfaced; and arbitrators specifically tried to shut down any discussion on wiki without even a promise to investigate privately. Without the potentially-outing post on-wiki, Nihonjoe would still be editing without any of the disclosures he has since fessed up to. The very real damage of a user with advanced permissions would continue; meanwhile, there's no actual evidence this "doxxing", if it can be considered such, came with external harms.
This is just the latest in a long series of situations where it took outside, public pressure for the Committee or functionaries to take corrective action, from Laura Hale to Qworty to Tenebrae. Fundamentally if Wikipedians are expected to abide by OUTING without regard to the fact that COI editors use it as a screen to avoid scrutiny, the private channels to report said editing need to actually result in action, and judging by Moneytree's comments on the case request that cannot be expected in the present climate. Der Wohltemperierte Fuchs talk 22:50, 19 March 2024 (UTC)
before using the last evidence template, please make a copy for the next person
Place argument and diffs which support your assertion; for example, your first assertion might be "So-and-so engages in edit warring", which should be the title of this section. Here you would show specific edits to specific articles which show So-and-so engaging in edit warring.
Below is a partial list of diffs which were shared as part of private evidence. February 19, 2016 February 19, 2016 October 28, 2019 August 25 2023 March 5 2024
Links that would have directly or indirectly OUTED any editors are omitted from this list. Barkeep49 ( talk) 03:10, 21 March 2024 (UTC)