Wikipedia:Arbitration/Requests/Enforcement

Click here to add a new enforcement request
For appeals: create a new section and use the template {{Arbitration enforcement appeal}}
See also: Logged AE sanctions

Important information

Shortcuts

Please use this page only to:

request administrative action against an editor violating a remedy (not merely a principle) or an injunction in an Arbitration Committee decision, or a contentious topic restriction imposed by an administrator,
request contentious topic restrictions against a previously alerted editor who engages in misconduct in a topic area designated as a contentious topic,
request page restrictions (e.g. revert restrictions) on pages that are being disrupted in topic areas designated as contentious topics, or
appeal arbitration enforcement actions (including contentious topic restrictions) to uninvolved administrators.

For all other problems, including content disagreements or the enforcement of community-imposed sanctions, please use the other fora described in the dispute resolution process. To appeal Arbitration Committee decisions, please use the clarification and amendment noticeboard.

Only autoconfirmed users may file enforcement requests here; requests filed by IPs or accounts less than four days old or with fewer than 10 edits will be removed. All users are welcome to comment on requests except where doing so would violate an active restriction (such as an extended-confirmed restriction). If you make an enforcement request or comment on a request, your own conduct may be examined as well, and you may be sanctioned for it. Enforcement requests and statements in response to them may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. (Word Count Tool) Statements must be made in separate sections. Non-compliant contributions may be removed or shortened by administrators. Disruptive contributions such as personal attacks, or groundless or vexatious complaints, may result in blocks or other sanctions.

The scope of a discussion is limited to the conduct of two parties: the filer and the user being reported. If additional editors are to be reported, separate AE reports must be opened for each. AE admins may waive this rule if the particular issue warrants doing so.

To make an enforcement request, click on the link above this box and supply all required information. Incomplete requests may be ignored. Requests reporting diffs older than one week may be declined as stale. To appeal a contentious topic restriction or other enforcement decision, please create a new section and use the template {{Arbitration enforcement appeal}}.

Appeals and administrator modifications of contentious topics restrictions

The Arbitration Committee procedures relating to modifications of contentious topic restrictions state the following:

All contentious topic restrictions (and logged warnings) may be appealed. Only the restricted editor may appeal an editor restriction. Any editor may appeal a page restriction.

The appeal process has three possible stages. An editor appealing a restriction may:

ask the administrator who first made the contentious topic restrictions (the "enforcing administrator") to reconsider their original decision;
request review at the arbitration enforcement noticeboard ("AE") or at the administrators' noticeboard ("AN"); and
submit a request for amendment ("ARCA"). If the editor is blocked, the appeal may be made by email.

Appeals submitted at AE or AN must be submitted using the applicable template.

A rough consensus of administrators at AE or editors at AN may specify a period of up to one year during which no appeals (other than an appeal to ARCA) may be submitted.

Changing or revoking a contentious topic restriction

An administrator may only modify or revoke a contentious topic restriction if a formal appeal is successful or if one of the following exceptions applies:

The administrator who originally imposed the contentious topic restriction (the "enforcing administrator") affirmatively consents to the change,^[a] or is no longer an administrator;^[b] or
The contentious topic restriction was imposed (or last renewed) more than a year ago and:
- the restriction was imposed by a single administrator, or
- the restriction was an indefinite block.

A formal appeal is successful only if one of the following agrees with revoking or changing the contentious topic restriction:

a clear consensus of uninvolved administrators at AE,
a clear consensus of uninvolved editors at AN,
a majority of the Arbitration Committee, acting through a motion at ARCA.

Any administrator who revokes or changes a contentious topic restriction out of process (i.e. without the above conditions being met) may, at the discretion of the Arbitration Committee, be desysopped.

Standard of review
On community review

Uninvolved administrators at the arbitration enforcement noticeboard ("AE") and uninvolved editors at the administrators' noticeboard ("AN") should revoke or modify a contentious topic restriction on appeal if:

the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
the action was not reasonably necessary to prevent damage or disruption when first imposed, or
the action is no longer reasonably necessary to prevent damage or disruption.

On Arbitration Committee review

Arbitrators hearing an appeal at a request for amendment ("ARCA") will generally overturn a contentious topic restriction only if:

the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
the action represents an unreasonable exercise of administrative enforcement discretion, or
compelling circumstances warrant the full Committee's action.

^ The administrator may indicate consent at any time before, during, or after imposition of the restriction.
^ This criterion does not apply if the original action was imposed as a result of rough consensus at the arbitration enforcement noticeboard, as there would be no single enforcing administrator.

Appeals and administrator modifications of other arbcom sanctions

The Arbitration Committee procedures relating to modifications and appeals state:

Appeals by sanctioned editors

Appeals may be made only by the editor under sanction and only for a currently active sanction. Requests for modification of page restrictions may be made by any editor. The process has three possible stages (see "Important notes" below). The editor may:

ask the enforcing administrator to reconsider their original decision;
request review at the arbitration enforcement noticeboard ("AE") or at the administrators’ noticeboard ("AN"); and
submit a request for amendment at the amendment requests page ("ARCA"). If the editor is blocked, the appeal may be made by email through Special:EmailUser/Arbitration Committee (or, if email access is revoked, to arbcom-enwikimedia.org).

Modifications by administrators

No administrator may modify or remove a sanction placed by another administrator without:

the explicit prior affirmative consent of the enforcing administrator; or
prior affirmative agreement for the modification at (a) AE or (b) AN or (c) ARCA (see "Important notes" below).

Administrators modifying sanctions out of process may at the discretion of the committee be desysopped.

Nothing in this section prevents an administrator from replacing an existing sanction issued by another administrator with a new sanction if fresh misconduct has taken place after the existing sanction was applied.

Administrators are free to modify sanctions placed by former administrators – that is, editors who do not have the administrator permission enabled (due to a temporary or permanent relinquishment or desysop) – without regard to the requirements of this section. If an administrator modifies a sanction placed by a former administrator, the administrator who made the modification becomes the "enforcing administrator". If a former administrator regains the tools, the provisions of this section again apply to their unmodified enforcement actions.

Important notes:

For a request to succeed, either

(i) the clear and substantial consensus of (a) uninvolved administrators at AE or (b) uninvolved editors at AN or

(ii) a passing motion of arbitrators at ARCA

is required. If consensus at AE or AN is unclear, the status quo prevails.

While asking the enforcing administrator and seeking reviews at AN or AE are not mandatory prior to seeking a decision from the committee, once the committee has reviewed a request, further substantive review at any forum is barred. The sole exception is editors under an active sanction who may still request an easing or removal of the sanction on the grounds that said sanction is no longer needed, but such requests may only be made once every six months, or whatever longer period the committee may specify.
These provisions apply only to contentious topic restrictions placed by administrators and to blocks placed by administrators to enforce arbitration case decisions. They do not apply to sanctions directly authorized by the committee, and enacted either by arbitrators or by arbitration clerks, or to special functionary blocks of whatever nature.
All actions designated as arbitration enforcement actions, including those alleged to be out of process or against existing policy, must first be appealed following arbitration enforcement procedures to establish if such enforcement is inappropriate before the action may be reversed or formally discussed at another venue.

Information for administrators processing requests

Thank you for participating in this area. AE works best if there are a variety of admins bringing their expertise to each case. There is no expectation to comment on every case, and the Arbitration Committee (ArbCom) thanks all admins for whatever time they can give.

A couple of reminders:

Before commenting, please familiarise yourself with the referenced ArbCom case. Please also read all the evidence (including diffs) presented in the AE request.
When a request widens to include editors beyond the initial request, these editors must be notified and the notifications recorded in the same way as for the initial editor against whom sanctions were requested. Where some part of the outcome is clear, a partial close may be implemented and noted as "Result concerning X".
Enforcement measures in arbitration cases should be construed liberally to protect Wikipedia and keep it running efficiently. Some of the behaviour described in an enforcement request might not be restricted by ArbCom. However, it may violate other Wikipedia policies and guidelines; you may use administrative discretion to resolve it.
More than one side in a dispute may have ArbCom conduct rulings applicable to them. Please ensure these are investigated.

Closing a thread:

Once an issue is resolved, enclose it between {{hat}} and {{hab}} tags. A bot should archive it in 7 days.
Please consider referring the case to ARCA if the outcome is a recommendation to do so or the issue regards administrator conduct.
You can use the templates {{uw-aeblock}} (for blocks) or {{AE sanction}} (for other contentious topic restrictions) to give notice of sanctions on user talk pages.
Please log sanctions in the Arbitration enforcement log.

Thanks again for helping. If you have any questions, please post on the talk page.

Arbitration enforcement archives

1	2	3	4	5	6	7	8	9	10	11	12	13	14	15	16	17	18	19	20
21	22	23	24	25	26	27	28	29	30	31	32	33	34	35	36	37	38	39	40
41	42	43	44	45	46	47	48	49	50	51	52	53	54	55	56	57	58	59	60
61	62	63	64	65	66	67	68	69	70	71	72	73	74	75	76	77	78	79	80
81	82	83	84	85	86	87	88	89	90	91	92	93	94	95	96	97	98	99	100
101	102	103	104	105	106	107	108	109	110	111	112	113	114	115	116	117	118	119	120
121	122	123	124	125	126	127	128	129	130	131	132	133	134	135	136	137	138	139	140
141	142	143	144	145	146	147	148	149	150	151	152	153	154	155	156	157	158	159	160
161	162	163	164	165	166	167	168	169	170	171	172	173	174	175	176	177	178	179	180
181	182	183	184	185	186	187	188	189	190	191	192	193	194	195	196	197	198	199	200
201	202	203	204	205	206	207	208	209	210	211	212	213	214	215	216	217	218	219	220
221	222	223	224	225	226	227	228	229	230	231	232	233	234	235	236	237	238	239	240
241	242	243	244	245	246	247	248	249	250	251	252	253	254	255	256	257	258	259	260
261	262	263	264	265	266	267	268	269	270	271	272	273	274	275	276	277	278	279	280
281	282	283	284	285	286	287	288	289	290	291	292	293	294	295	296	297	298	299	300
301	302	303	304	305	306	307	308	309	310	311	312	313	314	315	316	317	318	319	320
321	322	323	324	325	326	327	328	329	330	331	332	333	334	335	336	337	338	339	340
341	342	343	344	345	346	347	348	349	350	351	352

Shirshore

Shirshore has been blocked for socking. The next block will probably be indef --Guerillero ^{Parlez Moi} 14:21, 10 May 2022 (UTC)[reply]

The following discussion has been closed. Please do not modify it.

This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.
Requests may not exceed 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

Request concerning Shirshore

User who is submitting this request for enforcement: Kzl55 (talk · contribs · deleted contribs · logs · filter log · block user · block log) 18:55, 5 May 2022 (UTC)[reply]

User against whom enforcement is requested: Shirshore (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced: Wikipedia:Arbitration/Requests/Case/Horn_of_Africa#Final_decision

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

13 April 2022 Shirshore circumventing previous topic ban on Horn of Africa articles using confirmed sock JohnnyPilger the day after TBAN was confirmed. In this example by blanking a section on an article.
15 April 2022 Confirmed Shireshore sock JohnnyPilger continues to edit on Horn of Africa articles evading their TBAN.
21 April 2022 More blanking of sections using confirmed sock JohnnyPilger.

Diffs of previous relevant sanctions, if any

12 April 2022 Shirshore indefinitely topic banned from Horn of Africa.

If discretionary sanctions are requested, supply evidence that the user is aware of them (see WP:AC/DS#Awareness and alerts)

Previously given a discretionary sanction for conduct in the area of conflict on 12 April 2022 by Ymblanter (talk · contribs · blocks · protections · deletions · page moves · rights · RfA).

Additional comments by editor filing complaint

Following the topic ban of Shirshore last month due to disruptive editing. They have activated sleeper socking account JohnnyPilger (first registered June 2021) to evade the TBAN and continue editing on Horn of Africa articles, including disruptive blanking of sections as seen in the examples linked above. I have filed an SPI which confirmed their socking, but the closing admin gave a lenient 1 week sanctions. And although the closing admin gave a justification for leniency that would be completely understandable in normal circumstances, in my opinion their decision was limited to the socking activity and did not address the evasion of TBAN and general sanctions, which is why I'm filing this report. Shirshore is clearly not here to build an encyclopedia, they immediately attempted to circumvent their topic ban using a sleeper account that they've already prepared a year ago. As such I believe a WP:NOTHERE ban justified in this case. More information can be found in the SPI filing Wikipedia:Sockpuppet_investigations/Shirshore. Best regards --Kzl55 (talk) 18:55, 5 May 2022 (UTC)[reply]

Notification of the user against whom enforcement is requested

[1]

Discussion concerning Shirshore

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by Shirshore

Statement by (username)

Result concerning Shirshore

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

I don't think there's anything in particular that we need to do here: the sock has been indef blocked and the master blocked for the socking. Callanecc (talk • contribs • logs) 04:07, 10 May 2022 (UTC)[reply]

Dyldyl9

Dyldyl9 has been indefinitely blocked as a normal admin action --Guerillero ^{Parlez Moi} 14:25, 10 May 2022 (UTC)[reply]

The following discussion has been closed. Please do not modify it.

This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.
Requests may not exceed 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

Request concerning Dyldyl9

User who is submitting this request for enforcement: Sideswipe9th (talk · contribs · deleted contribs · logs · filter log · block user · block log) 23:11, 7 May 2022 (UTC)[reply]

User against whom enforcement is requested: Dyldyl9 (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced: Wikipedia:Arbitration/Requests/Case/American_politics_2 and Wikipedia:Arbitration/Requests/Case/Gender_and_sexuality

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

[2] Dyldyl9 refers to teachers in Florida, teaching age appropriate gender and sexuality lessons, as groomers.
[3] Dyldyl9 refers to people reposted on Libs of TikTok as paedophiles, and teachers as groomers.
[4] Dyldyl9 calls into question the 2021 United States Capitol attack, and downplays the severity of it by likening it to protests that occured during the 2017 inauguration.
[5] Dyldyl9 adds unsourced information, alleging a journalist released the home and business address of the creator of Libs of TikTok.
[6] Dyldyl9 removes content that has discussed repeatedly on the Libs of TikTok talk page, and has strong consensus based on what sources say about the account.
[7] Dyldyl9 engages in a mild personal attack against either myself or Praxidicae.

Diffs of previous relevant sanctions, if any

[8] Dyldyl9 was blocked for 72 hours, for an edit war involving diffs 4 and 5.

If discretionary sanctions are requested, supply evidence that the user is aware of them (see WP:AC/DS#Awareness and alerts)

Additional comments by editor filing complaint

There are two more diffs I'd like to include, as they demonstrate this behaviour over a substantial period of time, unfortunately they occurred prior to receiving the d/s notices. Although the editor is currently blocked for 72 hours for edit warring, their conduct is below that expected of in a discretionary sanctions topic area, and I suspect this behaviour will continue once the block expires. I don't know if this conduct has reached a level requiring a topic ban, if it has not would a formal warning be appropriate? Also if it's inappropriate to file while the editor is currently blocked for edit warring, I'll happily withdraw it and refile once the block expires. Sideswipe9th (talk) 23:11, 7 May 2022 (UTC)[reply]

Notification of the user against whom enforcement is requested

notification of this request

Discussion concerning Dyldyl9

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by Dyldyl9

Statement by (username)

Result concerning Dyldyl9

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

Looking at the editing so far I'm leaning more towards an indef NOTHERE block rather than a topic ban. Thoughts from others? Callanecc (talk • contribs • logs) 04:11, 10 May 2022 (UTC)[reply]
I agree with the NOTHERE recommendation. I took a look at Dyldyl9's contributions and they are largely accusations of bias in various articles. Not helpful and not here. --RegentsPark (comment) 14:10, 10 May 2022 (UTC)[reply]

SPECIFICO

This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.
Requests may not exceed 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

Request concerning SPECIFICO

User who is submitting this request for enforcement: Mhawk10 (talk · contribs · deleted contribs · logs · filter log · block user · block log) 02:48, 10 May 2022 (UTC)[reply]

User against whom enforcement is requested: SPECIFICO (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced: Wikipedia:Arbitration/Requests/Case/American politics 2#Discretionary sanctions (1992 cutoff)

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

8 May 2022 Baseless accusations of "meatpuppetry"
8 May 2022 Reiterating baseless accusations of "meatpupperty" and falsely accusing me of violating discretionary sanctions
9 May 2022 Using an article talk page to falsely and baselessly accuse me of violating discretionary sanctions

Diffs of previous relevant sanctions, if any

14 September 2014 User:SPECIFICO is warned that any such anti-community behaviour may lead to a site ban
3 June 2018 SPECIFICO knows very well that rewording or attempting to summarize what may be existing content can be quite contentious and edit warring to retain this rewording or new summary is in no way "reverting to longstanding stable content". This was the second time in just over two days where SPECIFICO incorrectly claimed to be reverting to longstanding content or content that had consensus.^[1]^[2] That's two strikes. A third strike involving an article covered by discretionary sanctions will likely mean sanctions will be imposed (internal links transformed to notes for template reasons).
Previously given a logged warning for conduct in the area of conflict on 9 April 2020 by Seraphimblade (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) with the note that SPECIFICO is reminded that talk pages are for discussing article content, not contributors, and warned that continuing to make personal comments about other editors on article talk pages may result in sanctions.

Notes

If discretionary sanctions are requested, supply evidence that the user is aware of them (see WP:AC/DS#Awareness and alerts)

The user issued a discretionary sanction warning on the topic within the past twelve months on 17 August 2021

Additional comments by editor filing complaint

To provide context to the above, I have repeatedly asked the user to retract their accusations of meatpuppetry and they've refused to do so. This all spurred from my response to a request on WP:RFCLOSE in which I closed a discussion on the article talk page. SPECIFICO has repeatedly made false allegations that I am acting as a meatpuppet of Iamreallygoodatcheckers, refused to strike that characterization or apologize, and then baselessly made allegations on an article talk page that I violated discretionary sanctions by editing a page to which they clearly do not apply. It's frankly uncivil at this point and, while I am someone who generally enjoys wading through discussions and writing closing summaries of complex RfCs, this sort of uncivil behavior towards an uninvolved closer that stems from a content dispute in which SPECIFICO is a party has driven me here to request that the user be given a final warning on civility and casting aspersions in the WP:AP2 topic area.

Notification of the user against whom enforcement is requested

02:49, 10 May 2022

Discussion concerning SPECIFICO

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by SPECIFICO

Statement by User:Iamreallygoodatcheckers

I have been interacting with SPECIFICO for some time now (mainly at Talk:Donald Trump), and while much of it has been fine, I have definitely experienced some of SPECIFCO's uncivil behavior. I've usually tried to give them the benefit of the doubt and just ignore it, but their uncivil behavior has in fact caused me some deal of anxiety and frustration, which has created a toxic environment in areas surrounding American politics.

The following comments concern this discussion: User talk:Iamreallygoodatcheckers/Archive 2#WP:NPA at Trump talk. On March 4th they left an accusation on my talk page with no sort of evidence, such as diffs, accusing me of violation WP:NPA. I responded saying that I had done not such thing. In that same thread, Mr Ernie warned them about providing unevidenced allegations. SPECIFICO made no response to mine or Ernies comments. On March 6th, SPECFICO accused me of WP:Casting aspersions, this time providing this diff. [9] Now this is a response I had made on the Trump talk page after SPECIFICO had accused me of WP:SEALION, a redirect to WP:Civil POV pushing, here. [10] With this diff SPECIFICO, says that I casted aspersions and assuring the links (WP:SEALION and WP:Civil POV pushing) are not the same. Now these links very much are the same, just click them if you don't believe me. I and Mr. Ernie again told them to stop with the behavior and that SEALION is the same as Civil POV pushing. SPECIFICO only admitted they were wrong about SEALION and Civil POV pushing after Valjean explained to them that they did in fact cite WP:SEALION against me. However, SPECICIO continued to say that "the problem remained," and that I was sealioning from their understanding. They did not provide any evidence to back these allegations, a fact that is pointed out by Ernie in the discussion. I never have received any form of apology or comment striking (after my request) for SPECICO's false allegations against me of NPA. Relevant diffs: [11] [12] [13] [14] [15] [16]

SPECICO has done this to me again just this week on my talk page (see User talk:Iamreallygoodatcheckers#WP:TE at Donald Trump). They accuse me with no evidence of any kind with WP:TE and "overly-insistent and POV editing at AP and BLP articles." They say they are "unlikely to do the work to document" my behavior, which I see as justification on their behalf of providing zero evidence. They also say my behavior is "worthy of a topic ban" in their view. I tell them to please stop with their behavior and that it's caused me stress and created a toxic environment. I have yet to receive any response from them. As detailed above by Mhawk, they have also accused me and Mhawk of meatpuppetting together, an allegation with no evidence. All this is WP:Casting aspersions and potentially WP:HOUND. Relevant diffs: [17] [18]

Iamreallygoodatcheckers (talk) 03:54, 10 May 2022 (UTC)[reply]

Statement by Mr Ernie

SPECIFICO violated DS at Julian Assange, another politically charged article, a few weeks ago. There is a section on their talk page with the details of that here. What I want to highlight is one of the reverts ([19]), removed content that was decided by RFC consensus just a few weeks ago, with SPECIFICO's participation. Note the RFC was required in part due to SPECIFICO's removal of the content before the RFC. Read the edit summary in the removal after RFC consensus - "NOTNEWS - not a significant fact about Assange No ongoing coverage in his life story." This is a sneaky move to remove content they simply just don't like, and SPECIFICO didn't seem interested to explain it in the linked discussion on their talk page. I don't think another final warning will do any good here - just check the sanction log. In addition to what the OP linked, SPECIFICO received a short topic ban from Joe Biden in 2020, a short topic ban from Julian Assange in 2020, a reminder and a warning in 2018, "Anti-Filibuster, Courtesy in reporting, No personal comments, and Thicker skin sanctions" in 2018, a restriction in 2017, and a warning in 2017. A standard AmPol2 topic ban should do, and I'll support the removal of it when SPECIFICO simply agrees to edit more collaboratively. Mr Ernie (talk) 15:46, 10 May 2022 (UTC)[reply]

Statement by Sideswipe9th (SPECIFICO)

I don't have much to add, only that I believe this ds/alert issued by SPECIFICO could be construed as reactive to the content dispute between SPECIFICO and Mhawk10. Also from what I can tell, the 1RR/24-hour BRD page restriction point is erroneous with respect to Talk:Donald Trump, as having checked the enforcement log entry that sanction only applies (as far as I can see) to the main article and not the associated article talk pages. From what I've seen elsewhere in the enforcement log, when an article and its talk page is subject to sanctions there is usually some text like Article Name and its associated talk page which is absent in this log entry. Sideswipe9th (talk) 22:01, 10 May 2022 (UTC)[reply]

Statement by (username)

Result concerning SPECIFICO

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

Beyond what Mr Ernie and Mhawk10 mentioned, SPECIFICO was sanctioned in Austrian economics and mentioned in Interactions at GGTF (both in 2014). It is clear to me that the only path forward is an indef topic ban from AP. --Guerillero ^{Parlez Moi} 17:08, 10 May 2022 (UTC)[reply]

Arbitration request on the Harry Styles Wikipedia page

I would like to make a formal request for arbitration on a requested edit to Harry Style’s Wikipedia page. His personal life section includes a reference to a largely unsubstantiated, fan theory relationship with Olivia Wilde. I would ask that the evidence that I have presented in the Talk section to at least have the Personal Life section revised to say that the relation between Styles and this other person is rumored.

Thank you,

[1] The administrator may indicate consent at any time before, during, or after imposition of the restriction.

[2] This criterion does not apply if the original action was imposed as a result of rough consensus at the arbitration enforcement noticeboard, as there would be no single enforcing administrator.

[3] ttps://en.wikipedia.org/w/index.php?title=Donald_Trump&diff=843502722&oldid=843501405

[4] ttps://en.wikipedia.org/w/index.php?title=User_talk:SPECIFICO&diff=843504249&oldid=843437894

[a]

[b]

[1]

[2]

v t e Noticeboards
Wikipedia's centralized discussion, request, and help venues. For a listing of ongoing discussions and current requests, see the dashboard. For a related set of forums which do not function as noticeboards see formal review processes.
General	Administrators Main Incidents Bots Bureaucrats Centralized discussion Closure requests Education Interface admins Main Page errors Open proxies VRT Oversight User permissions
Articles, content	Biographies of living persons Copyrights Questions on media Problems Dispute resolution External links Fringe theories Neutral point of view Original research Pending changes Reliable sources Resource requests Scalable vector graphics Spam Blacklist Whitelist Style Titleblacklist Translation
Page handling	History merges Mergers Splits Moves Protection Importation XfD Articles Redirects Categories Templates Files Miscellany Undeletion
User conduct	Conflict of interest Contributor copyright Edit warring and 3RR Sanctions Personal restrictions General sanctions Contentious topics Sockpuppets Usernames (Requests for comment) Vandalism
Other	Arbitration Committee noticeboard Requests Enforcement Edit filters Requested False positives Questions Help desk Teahouse Reference desk New articles Requests for comment Village pump Policy Technical Proposals Idea lab WMF Miscellaneous WikiProject proposals Discussions for discussion
Category:Wikipedia noticeboards