Universal Code of Conduct/Coordinating Committee/Cases/2026/Systemic failure to enforce UCoC on Wikidata - structural capture of enforcement channels

This case is declined. If you have comments or a request to have it reopened, post a comment on the talk page.

U4C member alert: @U4C: Barkeep49, Borschts, BRPever, Civvì, Denis Barthel, EggRoll97, EPIC, Ferien, Ghilt, Luke081515, PBradley-WMF, Superzerocool, Toadspike, ToprakM, Torque, 기나ㅏㄴ. Johnnytelles (talk) 00:17, 23 July 2026 (UTC)

---

Johnnytelles

Description of the problem - (Johnnytelles)

This case was referred to the U4C by WMF Trust & Safety (ticket #154174, Kevin Peterson, 2026-07-22), who indicated this committee as the appropriate channel for UCoC violations where local administrators are unable or unwilling to act. It is not a re-filing of a previously resolved matter.

This case documents a systemic pattern in which all available local enforcement channels were captured by actors with direct conflicts of interest, making it structurally impossible to obtain impartial review through local mechanisms.

Three related cases have been filed separately with the U4C and should be read in conjunction with this case:

• Case 1 — Bureaucrat intimidation (Ymblanter)
• Case 2 — Tool abuse and concealed COI (Bovlb)
• Case 3 — Deletion COI and self-evaluation (Yamato Shiya)

4a — Closure of all noticeboard threads by actor with COI

Three consecutive threads opened by the complainant on the Administrators' noticeboard — each documenting deletions by Yamato Shiya — were closed by Bovlb:

• diff=2517548209 — "Some of my Wikidata items were deleted" — closed 2026-07-14T23:14Z — reason: "posted this complaint in at least three places"
• diff=2518639447 — "RFU: Q139762124 et al." — closed 2026-07-17T13:13Z — redirected to Project chat, later dismissed as "conspiracies"
• diff=2520919447 — "Request for undeletion of related Wikidata items (Q135455276 et al.)" — section header removed 2026-07-22T04:00Z — edit summary: "rm empty section"

Bovlb has a documented conflict of interest with Yamato Shiya (Case 2). The three closures are without substantive review of the deletion merits in any case.

4b — Project chat: dismissal by bureaucrat as "conspiracies"

Bovlb's second closure (diff=2518639447) redirected the complainant to the Project chat as the designated venue. In that thread, Lymantria (bureaucrat) responded to independent editor Yirba's citation of WD:Introduction and characterized the complainant's documented evidence as:

"not look for not existing conspiracies" — Lymantria, 10:03, 20 July 2026

diff=2520132063

The documented evidence included: deletion log entries, ISSN International Centre records, GARUDA indexation (Indonesian Ministry of Education), 30 published articles, and 364+ archived noticeboard sections where the same pattern appears. Lymantria addressed none of these in her response.

4c — Rights request channel: intimidation by bureaucrat

Ymblanter (bureaucrat) evaluated the complainant's rollbacker flag request on 2026-07-22 while the complainant was actively documenting administrator misconduct. His evaluation:

"The point is not whether the criterion applies or not, the point is that you can not be trusted with this flag." — Ymblanter, 12:25, 22 July 2026

The rollbacker criterion does not include trustworthiness in disputes with administrators. The stated basis for refusal was extrinsic to the flag's purpose and was applied exclusively in the context of the complainant's complaints against other administrators.

On 2026-07-16, Ymblanter had already characterized the same documentation as a "crusade" and threatened "swift indefinite block" — diff=2518606305 — in the Administrators' noticeboard.

4d — Mutual protection network: timeline

{

Previous attempts at a solution - (Johnnytelles)

WMF Trust & Safety (ticket #154174, 2026-07-22) indicated the U4C as the appropriate channel after all local channels were exhausted.

Applicable precedents:

• Hebrew Wikipedia (2025): the U4C accepted a case where a systemic pattern of administrators protecting each other made local resolution impossible. Cases/Systemic_failure_in_enforcing_the_code_of_conduct_in_Hebrew_Wikipedia
• Spanish Wikipedia (2025): the U4C investigated "abuse of administrative tools... abuse of power" by admins with undisclosed conflicts of interest operating as a network. Cases/2025/Situation_in_Spanish_Wikipedia

Suggested solutions - (Johnnytelles)

1. Investigation of the network pattern documented above as a systemic UCoC §3.2 violation, in conjunction with Cases 1–3. 2. Assessment of whether the bureaucrat tools held by Ymblanter and Lymantria were used in conformity with UCoC §4 (enforcement responsibilities). 3. Review of the procedural closures by Bovlb for conformity with WD:AN standards.

Diffs and links:

1. diff=2518606305 — Ymblanter: "crusade" / "swift indefinite block"
2. anchor — Ymblanter: "you can not be trusted with this flag"
3. diff=2517548209 — Bovlb closes AN thread 1
4. diff=2518639447 — Bovlb closes AN thread 2 → redirects to Project chat
5. diff=2520919447 — Bovlb removes AN thread 3 header
6. diff=2520132063 — Lymantria: "not look for not existing conspiracies"
7. WMF Trust & Safety ticket #154174 (Kevin Peterson, 2026-07-22) — referral to U4C

— Johnnytelles (talk) 00:17, 23 July 2026 (UTC)

Lymantria

Previous attempts at a solution - Lymantria

The quoted words were part of a paragraph and were meant to play down bigger words that were used, to de-escalate. I reacted to a part of discussion short before my reaction:

I have already opened a thread on the administrators' noticeboard. However, because Bovlb is an administrator, no action was taken. Predictably, some users claimed I was in the wrong; administrator noticeboards across the Wikimedia movement consistently protect sysops at all costs, even when their actions conflict with community consensus and policy.

— Rodrigo Tetsuo Argenton

I thought that the stylistic similarity of my reaction was clear - and intentionally exaggerated - after which I asked to calm down:

Consistently across the Wikimedia movement some users who see their work deleted try to blow this up to an example of the huge and dishonest way the system of admins neglects community consensus. Luckily it is rather rare at Wikidata. Let's keep it that way and discuss matters, disagree at times, but not look for not existing conspiracies.

— Lymantria

Clearly my phrasing could have been better, pointing to protecting each other at all cost in stead of pointing to neglecting community consensus. It is clear from the reaction by Rodrigo Tetsuo Argenton to my paragraph, that he interpreted it differently:

Furthermore, dismissing documented procedural concerns as a "conspiracy theory" is a convenient rhetorical device, but it does not change the facts. It is not a conspiracy to point out that an unapproved essay (Wikidata:Self-promotion) was used as the functional basis for expedited mass deletions without a standard RfD process. That is a documented procedural bypass.

— Rodrigo Tetsuo Argenton

I thought it best to leave it there and not escalate further. Discussion on how to deal with the difficult notability criteria at Wikidata is fine, although I am a bit suprised by the style the discussion is held in the thread at hand. --Lymantria (talk) 06:43, 23 July 2026 (UTC)

Suggested solutions - Lymantria

Let me clarify that my hinting to conspiracy was not aimed at the discussion on the use of Bovlb's essay and/or template. --Lymantria (talk) 06:47, 23 July 2026 (UTC)

Sorry, but how and why have you made this about yourself and me?

Your intervention in the original discussion was unnecessarily aggressive and dismissive towards me. You explicitly characterised what I had said as a “conspiracy theory”. You cannot reasonably dismiss someone’s statement in those terms and then present yourself here as though their negative reaction were somehow unexpected, or as though you had merely been making an innocent attempt to de-escalate the discussion.

You now say that your intention was to “de-escalate” and that you chose to “leave it there and not escalate further”. Yet you have since brought my name, my comments, and your interpretation of my reaction into a formal dispute-resolution process in which I am not a party.

I find that particularly difficult to reconcile with your claim that you were trying to de-escalate. You dismissed what I said as a conspiracy theory, received a reasonably foreseeable negative response, and are now retrospectively reframing that exchange whilst involving me in an entirely separate case.

I also genuinely do not understand how any of this constitutes a “previous attempt at a solution”. What you have written here is not an attempt to resolve the matter described in this case. It is a retrospective explanation and defence of your own conduct, using me and my reaction as part of that defence.

I did not file this case, I am not a party to it, and I see no reason why I should have been brought into your response at all. By doing so, you are not resolving anything. You are making matters worse by dragging me into a dispute that is not mine.

Please leave me out of this. Rodrigo Tetsuo Argenton (talk) 15:09, 23 July 2026 (UTC)

Other feedback

For people who are not parties, the following rules apply:

• Comments/replies may not be longer than 500 words and may not include more than 25 diffs/links. The U4C may, if asked, grant additional words or diffs/links.
• Comments/replies are permitted only in your own section.
• Contributions that do not help clarify the matter can be removed.
• All accusations and claims must be supported with diffs/links.

Discussion between the involved parties and the U4C members

Only the involved parties and U4C members may edit in this section.

U4C decision

Only U4C members may edit in this section.

Decline votes

• No evidence of UCoC violations. Closing duplicate discussion sections (or, in one case, just removing a header with no discussion) is not a UCoC violation. The full quote is "Let's keep it that way and discuss matters, disagree at times, but not look for not existing conspiracies", which is not uncivil and is directed at "us" (in "Let's") and therefore not a personal attack. I believe I have addressed the rest at the other case requests. Toadspike [Talk] 02:26, 23 July 2026 (UTC)
• There are not UCoC violations here. An entire section of your complaint is just a bracket and nothing else. It's fairly clear the actual substance of what you wrote amounts to petty disputes you have caused, of which the admins at Wikidata have responded with more than enough patience. EggRoll97 (talk) 05:06, 23 July 2026 (UTC)
• EPIC (talk) 06:40, 23 July 2026 (UTC)
• I don't see a UCoC violation here. And especially, no evidence of systemic failure was presented in any of the 4 case requests. --Ghilt (talk) 07:20, 23 July 2026 (UTC)
• Per Toadspike and EggRoll above. Borschts ^Talk 07:25, 23 July 2026 (UTC)
• I have read all four requests. I agree with Toadspike on the substance of this case. Four separate requests with some overlap becomes disruptive. Barkeep49 (talk) 09:05, 23 July 2026 (UTC)
• I see no demonstrable UCoC violations in these reports. --Torque (scrivimi!) 12:56, 23 July 2026 (UTC)

Motions

U4C members may propose motions to resolve the case or as a temporary measure during the case.

Updates

This section is used only by U4C members and official designees (including WMF staff who support the U4C) to provide updates about the request.

• We have received this request. On behalf of the U4C, Toadspike [Talk] 02:15, 23 July 2026 (UTC)
• With 7 members voting to decline the case and 1 inactive member, the case is declined. EPIC (talk) 18:06, 23 July 2026 (UTC)