Misplaced Pages

:Arbitration/Requests/Enforcement: Difference between revisions - Misplaced Pages

Article snapshot taken from[REDACTED] with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages:Arbitration | Requests Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 07:24, 19 May 2009 editKevin (talk | contribs)17,588 edits →Abtract: blocked 1 month.← Previous edit Revision as of 08:04, 19 May 2009 edit undoBrandmeister (old) (talk | contribs)12,058 edits →Request concerning 76.93.86.242: present diffsNext edit →
Line 136: Line 136:
;Arbitration case whose sanctions are to be enforced: ] ;Arbitration case whose sanctions are to be enforced: ]
;Sanction or remedy that has been violated:] ;Sanction or remedy that has been violated:]
;] of edits that violate this sanction or remedy: , , , , ;] of edits that violate this sanction or remedy: , , , , , , ,
;Explanation ''how'' these edits violate the sanction or remedy at issue: A single-purpose IP, currently editwarring in ] ;Explanation ''how'' these edits violate the sanction or remedy at issue: A single-purpose IP, currently editwarring in ]
;Enforcement action requested (], ] or ]): Block or any other sanction at admin's discretion ;Enforcement action requested (], ] or ]): Block or any other sanction at admin's discretion

Revision as of 08:04, 19 May 2009

Shortcut

Requests for 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 informationShortcuts

Please use this page only to:

  • request administrative action against editors 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 previously alerted editors who engage 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 less 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.

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:

  1. ask the administrator who first made the contentious topic restrictions (the "enforcing administrator") to reconsider their original decision;
  2. request review at the arbitration enforcement noticeboard ("AE") or at the administrators' noticeboard ("AN"); and
  3. 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, or is no longer an administrator; 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:

  1. the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
  2. the action was not reasonably necessary to prevent damage or disruption when first imposed, or
  3. 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:

  1. the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
  2. the action represents an unreasonable exercise of administrative enforcement discretion, or
  3. compelling circumstances warrant the full Committee's action.
  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.
Appeals and administrator modifications of non-contentious topics 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:

  1. ask the enforcing administrator to reconsider their original decision;
  2. request review at the arbitration enforcement noticeboard ("AE") or at the administrators’ noticeboard ("AN"); and
  3. 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-en@wikimedia.org).
Modifications by administrators

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

  1. the explicit prior affirmative consent of the enforcing administrator; or
  2. 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:

  1. 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.
  2. 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.
  3. 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.
  4. 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 Misplaced Pages 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 Misplaced Pages 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
1234567891011121314151617181920
2122232425262728293031323334353637383940
4142434445464748495051525354555657585960
6162636465666768697071727374757677787980
81828384858687888990919293949596979899100
101102103104105106107108109110111112113114115116117118119120
121122123124125126127128129130131132133134135136137138139140
141142143144145146147148149150151152153154155156157158159160
161162163164165166167168169170171172173174175176177178179180
181182183184185186187188189190191192193194195196197198199200
201202203204205206207208209210211212213214215216217218219220
221222223224225226227228229230231232233234235236237238239240
241242243244245246247248249250251252253254255256257258259260
261262263264265266267268269270271272273274275276277278279280
281282283284285286287288289290291292293294295296297298299300
301302303304305306307308309310311312313314315316317318319320
321322323324325326327328329330331332333334335336337338339340
341342343344345346347

Abtract

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

Request concerning Abtract

User requesting enforcement
Casliber (talk · contribs) 20:42, 18 May 2009 (UTC)
It should be noted that Calsiber is a personal friend of Haines (see his user page) so presumably he is continuing Haines' bullying vendetta at his offline request. Abtract (talk) 06:32, 19 May 2009 (UTC)
User against whom enforcement is requested
Abtract (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Arbitration case whose sanctions are to be enforced
Misplaced Pages:Requests for arbitration/Alastair Haines
Sanction or remedy that has been violated
Diffs of edits that violate this sanction or remedy
http://en.wikipedia.org/search/?title=Gender_of_God&diff=290549704&oldid=290427190
Explanation how these edits violate the sanction or remedy at issue
interacting with Alastair Haines
Enforcement action requested (block, topic ban or other sanction)
as per case (lengthening block)
Additional comments
Notification of the user against whom enforcement is requested

Discussion concerning Abtract

Result concerning Abtract

Abtract has been blocked for one month by Kevin (talk · contribs).  Sandstein  07:19, 19 May 2009 (UTC)

(edit conflict) I have blocked for 1 month, being the maximum available in the remedy. The diff noted above was sufficient of itself, but the spectacular failure of good faith by Abtract above sealed the deal.

Jehochman noted at the time if Abtract's last block that discussion regarding a community ban would be in order at the next violation. I may start that discussion at WP:ANI if I have time. Kevin (talk) 07:23, 19 May 2009 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

ScienceApologist

Attention: This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.

Process note: Please don't archive this one just yet, thanks. ++Lar: t/c 00:53, 5 May 2009 (UTC)
Collapse boxes save space, but they impair usability by making searches cumbersome and breaking the table of contents. Just a thought. Short Brigade Harvester Boris (talk) 00:43, 18 May 2009 (UTC)
Extended content
The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

Request concerning ScienceApologist

User requesting enforcement
-- Levine2112 01:35, 1 May 2009 (UTC)
User against whom enforcement is requested
ScienceApologist (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Arbitration case whose sanctions are to be enforced
Misplaced Pages:Requests for arbitration/Fringe science
Sanction or remedy that has been violated
Misplaced Pages:Requests for arbitration/Fringe science#Log of blocks, bans, and restrictions
Diffs of edits that violate this sanction or remedy
Explanation how these edits violate the sanction or remedy at issue
User is banned for a period of three months, yet continues to make edits "anonymously" through an IP address (128.59.171.155).
Enforcement action requested (block, topic ban or other sanction)
Indef block.
Additional comments
This IP address seems highly likely to be ScienceApologist based on the following correlating evidence: . That said, perhaps a CheckUser is at least in order.
Notification of the user against whom enforcement is requested

Discussion concerning ScienceApologist

I don't think a checkuser is required, the evidence is compelling that this is SA. Kevin (talk) 02:39, 1 May 2009 (UTC)

  • Hi, I've just become aware of this thread (as his mentor it would have been nice to have gotten a heads up). Have emailed ScienceApologist and am seeking a checkuser. No word yet; this is the first it's come to my attention. Durova 03:04, 1 May 2009 (UTC)
  • (Sarcasm alert): Yes, the evidence is indeed compelling, since SA is ...NOT. Oddly enough, the IP has not been notified, but SA has received the notification. Whatever.... Maybe it is him (probably), and maybe it's not. Is there any more compelling evidence? If not, this may be enough. -- Brangifer (talk) 03:34, 1 May 2009 (UTC)
That is not the only evidence - this edit shows the IP signing as SA, on a page where SA would likely deal with it if it were someone else. Kevin (talk) 03:41, 1 May 2009 (UTC)
...but if he's already blocked, how would SA deal with it if it were someone else? CU may be in order, but AGF here, folks. It could well be someone trying to pull a JoeJob to make us think it's SA. rdfox 76 (talk) 04:19, 1 May 2009 (UTC)
The edits are at Wikisource, where SA is not blocked. Kevin (talk) 04:22, 1 May 2009 (UTC)
You're looking at additional comments rather than the diffs. Look a couple lines up. We're talking about Misplaced Pages edits. II | (t - c) 07:54, 1 May 2009 (UTC)
  • CU isn't going to tell us anything that we don't already know (), so I don't know why it would be necessary. The only edits which are worth being annoyed about are the last few on Quackwatch. Then again, a couple of these use improper capitalization which might suggest it's not SA, since he seems to understand proper English (although it is a quote, so it might have confused him). Plus the edit adds a bunch of rambling text, which isn't typical of SA. Anyway, seems hard to be sure that it is SA, even though the edits are to articles which he edits and come from his IP address. The edits aren't really disruptive or awfully characteristic of him so I'd be inclined to let it go. Err on the side of good faith and all that. II | (t - c) 07:54, 1 May 2009 (UTC)
  • I think we do need checkuser here, although it's not clear that the additional information will settle this case. We are talking about a dynamic IP I think there are obvious problems with the duck test in such high-profile cases, so we should be careful with it. --Hans Adler (talk) 11:58, 1 May 2009 (UTC)

Could we please stop bandying about irrelevant real life information? We have and need the IP and information related to it, that should be all that is necessary. It has been a while since I stalked ScienceApologist, but I do not recall ever seeing French military history, country music BLPs, or Hannah Montana ever pop up. Redshift has certainly benefited from ScienceApolologist, but that edit to remove a See also did not raise any red flags when it passed through my WatchList the other week. - 2/0 (formerly Eldereft) (cont.) 14:40, 1 May 2009 (UTC)

  • Two CU checks have been run on this and both said the results were very convincing. I was NOT one of those who ran the checks. — Rlevse • Talk • 19:03, 1 May 2009 (UTC)
This does not appear in the public record, does it? Hipocrite (talk) 19:04, 1 May 2009 (UTC)
I think we can take Rlevse's word for it. Jehochman 21:23, 1 May 2009 (UTC)
Measure twice cut once? If a CU was run, the checkuser should verify that in a public location. Unless IRC is a place where[REDACTED] business can take place? Hipocrite (talk) 22:04, 1 May 2009 (UTC)
I corroborate that a check was run by me, by request, and that I found it highly likely that the IP I was asked about is being used by SA. Hipocrite, your tone is not helpful. ++Lar: t/c 22:46, 1 May 2009 (UTC)

Section break

Note: Since the case remains open, I am moving this section's content out of the "result" and into the "discussion" section.  Sandstein  05:30, 2 May 2009 (UTC)

I am disappointed to see some of the regular pro-fringe advocates petitioning for sanctions against SA. This matter looks like something that belongs at WP:SPI, not here. Copy the evidence there, select code 'A', violation of arbitration sanctions, and let a Checkuser make a determination. Jehochman 14:06, 1 May 2009 (UTC)

I have redacted some personal info that was not needed to be posted here. Please don't restore that. This matter should be handled by a Checkuser. Jehochman 15:16, 1 May 2009 (UTC)
As checkuser has been run, and block evasion has been found, the customary result is an upgrade to indef. Since SA is currently blocked, I think we should have a community discussion first to decide what to do, rather than jumping to indef and having a discussion afterwards. Talk first then use tools. Does anybody object to an indefinite block? Jehochman 21:26, 1 May 2009 (UTC)
I think blocking the IP for the term of SA's block, or for 3 months (doing a "reset") would be a better approach. Unless we are ready to write SA off completely. Which I am not. Yet. ++Lar: t/c 22:48, 1 May 2009 (UTC)
That sounds like the Solomonic solution. -- Brangifer (talk) 00:06, 2 May 2009 (UTC)
Okay, Lar. Can you implement that? At minimum resetting the original block should be non-controversial. I remember last time you checked this. You're familiar with all the circumstances. Jehochman 00:44, 2 May 2009 (UTC)

Statement

I'm Columbia College student majoring in astrophysics. I edit Misplaced Pages all across campus. I am not "ScienceApologist". The guy with the account asked me to explain here. —Preceding unsigned comment added by 128.59.171.155 (talk) 23:01, 1 May 2009 (UTC)

I don't have Checkuser access so I have no good way to double check their results. Jehochman 00:54, 2 May 2009 (UTC)
Rechecked. I get the same CU result I got last time: "Strong correlation to ScienceApologist". Certainly there are other possible explanations, and I would defer to "Pattern of editing analysis" as appropriate but that's what CU tells me. ++Lar: t/c 01:22, 2 May 2009 (UTC)

Didn't want to comment further until making contact with ScienceApologist. Am aware of the strength of the technical checkuser evidence; until reaching him directly I considered it almost certain that he had made these edits himself. In which case of course that would not be defensible. He tells me the disputed edits were not his; that they came from a departmental Internet connection to which many people have access. This is a large university. It stands to reason that most of that department shares the same interests and POV; they would likely touch similar articles no matter whether they knew he edited or not. The best he could do in the short time since we made contact was to locate the individual and ask for a disclosure. I have asked him to follow up with confirmatory information from the IT department etc. Suppose in good faith that he has abided by the terms of his siteban and this arose for reasons outside his control very late in the semester (the university ends its spring term early) and at the beginning of a weekend. In all likelihood, followup will occur via email with potentially sensitive information. The reasonable thing is to let the Committee weigh the evidence and see whether they believe the good faith scenario is plausible. May we close this thread procedurally? The Committee is certainly aware of this and interested. It is unlikely that ScienceApologist can supply much more substantiation during the weekend. Durova 02:11, 2 May 2009 (UTC)

No comment on procedural closes. As for the rest, I'd want to hear from the IT department about their computer configuration before I was convinced it wasn't SA... but I suggest we block the range to anons, but not new account creations, for the duration of his ban, and just say, "sorry, there is disruptive editing coming from here, you will have to get an account" to any anon, and scrutinise new accounts created to see if they're editing problematically. ++Lar: t/c 03:16, 2 May 2009 (UTC)
I would like a procedural close or pause on this. If we gain a better understanding of the IP in question, we should have everything we need to make a decision. As this is about an IP address, there are privacy issues, so anyone with any sound technical information about the IP should privately send it to Lar, or to the committee. John Vandenberg 05:09, 2 May 2009 (UTC)

Result concerning ScienceApologist

This section is to be edited only by the administrator closing this request for arbitration enforcement. Use {{discussion top}} / {{discussion bottom}} to mark it as closed.

Lar and ArbCom will deal with it. Privacy issues preclude further investigation by the community. Jehochman 12:28, 2 May 2009 (UTC) Was there a resolution to this? The IP user seems to be editing again and it would be useful to let the community if the user was cleared to prevent additional reports. Ronnotel (talk) 14:45, 7 May 2009 (UTC)

Not yet. I've just nudged a few people... sorry for the delay. not quite sure what to do here. ++Lar: t/c 00:09, 8 May 2009 (UTC)
Uh - not sure I quite understand the difficulty here. We have what appears to be ongoing sock-puppetry from a banned user that has been doubly checkuser-confirmed. Against this, we have a self-serving statement from an anonymous IP address. I would think policy would indicate that we block the IP and make the ban indefinite. If evidence is forthcoming that supports the anon IP then these administrative actions can be reversed. At this point, shouldn't the burden of proof be on the anon IP and the banned user? Ronnotel (talk) 12:23, 8 May 2009 (UTC)
Please stop lobbying. You don't, and can't, have full information. Leave it to the Checkusers to decide. Jehochman 12:28, 8 May 2009 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

76.93.86.242

Attention: This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.

Request concerning 76.93.86.242

User requesting enforcement
brandспойт 20:38, 18 May 2009 (UTC)
User against whom enforcement is requested
76.93.86.242 (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Arbitration case whose sanctions are to be enforced
Misplaced Pages:Requests for arbitration/Armenia-Azerbaijan 2
Sanction or remedy that has been violated
Edit warring considered harmful
Diffs of edits that violate this sanction or remedy
, , , , , , , ethnic insult
Explanation how these edits violate the sanction or remedy at issue
A single-purpose IP, currently editwarring in We Are Our Mountains
Enforcement action requested (block, topic ban or other sanction)
Block or any other sanction at admin's discretion
Additional comments
Notification of the user against whom enforcement is requested

Discussion concerning 76.93.86.242

Result concerning 76.93.86.242

This section is to be edited only by the administrator closing this request for arbitration enforcement. Use {{discussion top}} / {{discussion bottom}} to mark it as closed.

Rehoboth Carpenter Family & related Carpenter pages

Resolved – Wrong forum.

Iwanafish, alias 125.199.58.121 and 160.244.140.202 refuses to communicate despite many entreaties to do so by several editors. See discusion page of Rehoboth Carpenter Family. Apparently this stems from some disagreement which he refuses to discuss. Iwanafish has repeatedly rolled back this and related articles to a previous version of his without discussion. He has used his Washington State IP and his Japan IP as an alias. He has been given many warnings regarding his behavior. I will admit I and another used the wrong warning format at first regarding his reversion from surveyed articles using wiki format and inline references back to his own format. We are now using the proper warning format. Any help in getting him to communicate or to stop his negative behavior would be appreciated. Jrcrin001 (talk) 07:17, 19 May 2009 (UTC)

This report does not belong on this page, which is dedicated to arbitration enforcement (see the advice at the top of the page). Such reports should be made to WP:ANI, preferably with helpful WP:DIFFs.  Sandstein  07:22, 19 May 2009 (UTC)
Misplaced Pages:Arbitration/Requests/Enforcement: Difference between revisions Add topic