Wikipedia:Administrative action review

Administrative action review (XRV/AARV) determines whether use of the administrator tools or other advanced permissions is consistent with Wikipedia's policies and guidelines. Any action (or set of related actions) involving a tool not available to all confirmed editors—except those covered by another, more specific review process—may be submitted here for community review. The purpose of an administrative review discussion is to reach a consensus on whether a specific action was appropriate, not to assign blame. It is not the place to request comment on an editor's general conduct, to seek retribution or removal of an editor's advanced permissions, or to quibble about technicalities.

To request an administrative action review, please first read the "Purpose" section to make sure that your particular concerns are within the proper scope. Then, follow the instructions below.


Purpose

Administrative action review may be used to request review of:

  1. an administrator action
  2. an action using an advanced permission

Administrative action review should not be used:

  1. to request an appeal or review of an action with a dedicated review process
    For review of page deletions or review of deletion discussion closures, use Wikipedia:Deletion review (DRV)
    For review of page move discussion closures, use Wikipedia:Move review (MRV)
  2. to ask to remove a user's permissions:
    Permissions granted at WP:PERM may be revoked by an administrator consistent with the guidelines for that permission.
    Repeated or egregious misuse of permissions may form the basis of an administrators' noticeboard or incidents noticeboard report, or a request for arbitration, as appropriate.
  3. to argue technicalities and nuances (about what the optimal action would have been, for example), outside of an argument that the action was inconsistent with policy.
  4. to ask for a review of arbitration enforcement actions. Such reviews must be done at arbitration enforcement noticeboard ("AE"), at the administrators' noticeboard ("AN"), or directly to the Arbitration Committee at the amendment requests page ("ARCA").
  5. for urgent incidents and chronic, intractable behavioural problems; use Wikipedia:Administrators' noticeboard/Incidents ("ANI") instead
  6. for serious, entrenched or persistent disputes and cases of rule-breaking; use Wikipedia:Arbitration ("ArbCom") instead
  7. for a block marked with any variation of {{CheckUser block}}, {{OversightBlock}}, or {{ArbComBlock}}; Contact the Arbitration Committee instead
  8. to attack other editors, cast aspersions, or make accusations of bias. Such requests may be speedily closed.
Instructions
Initiating a review
  1. Before listing a review request, try to resolve the matter by discussing it with the performer of the action.
  2. Start a new discussion by clicking the button below and filling in the preloaded template (or use {{subst:XRV}} directly)
  3. Notify the performer of the action of the discussion.
    You must leave a notice on the editor's talk page. You may use {{subst:XRV-notice}} for this purpose.
    Use of the notification system is not sufficient.

Start a new discussion

Participating in a discussion

Any editor in good standing may request a review or participate in discussing an action being reviewed. Participation is voluntary. The goal of the discussion is to determine whether the action is consistent with Wikipedia's policies. Contributions that are off-topic may be removed by any uninvolved administrator. You may choose to lead your comment with a bold and bulleted endorse or not endorsed/overturn, though any helpful comment is welcome. Please add new comments at the bottom of the discussion.

Closing a review

Reviews can be closed by any uninvolved administrator after there has been sufficient discussion and either a consensus has been reached, or it is clear that no consensus will be reached. Do not rush to close a review: while there is no fixed minimum time, it is expected that most good faith requests for review will remain open for at least a few days.

The closer should summarize the consensus reached in the discussion and clearly state whether the action is endorsed, not endorsed, or if there is no consensus.

After a review

Any follow-up outcomes of a review are deferred to existing processes. Individual actions can be reversed by any editor with sufficient permissions. Permissions granted at WP:PERM may be revoked by an administrator.

Closed reviews will be automatically archived after a period of time. Do not archive reviews that have not been formally closed.

October 2026 partial block by Iseult

The following discussion 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.


Diffs/logs:
User: Iseult (talk · contribs · logs) (prior discussion)
No active editor should be partially blocked from a page they have not edited in over a month, per WP:BLOCKPOL, specifically WP:PREVENTATIVE. Nor should an active editor be partially blocked from an entire namespace they haven't edited in over a month. On October 30, User:Iseult partially blocked User:Rehman from mainspace, despite User:Rehman not having edited mainspace since September 28 , over a month prior, although they did edit other namespaces in October.
This partial block happened during WP:AI noticeboard/Rehman, which was started on October 27. Rehman was responsive and active in that discussion, and did not edit mainspace during the discussion (nor for a month prior). Nobody has accused Rehman of using AI since the AINB discussion started.
At 16:53 Oct 29, Iseult asked Rehman questions in the AINB thread. About 10 hours later, without a reply from Rehman and during which time Rehman did not edit, Iseult partially blocked Rehman from mainspace, at 02:50 Oct. 30. This partial block has been cited as the grounds for a recall at WP:Administrator recall/Rehman.
This is not a semi-active or inactive user; Rehman made a couple hundred edits in September and October. There was no ongoing disruption that required a partial block; the user had not edited mainspace in over a month, did not repeat the complained-of conduct, was responsive to the AINB thread, and made commitments to adjust their editing going forward. Also, asking a user a question and then blocking without waiting for a response is almost always poor form. Since there was no ongoing disruption to prevent, this block was outside WP:BLOCKPOL, and should be not endorsed. Levivich (talk) 18:46, 1 November 2026 (UTC)
  • Not endorsed/overturn Bad block per above. I'd been thinking, "this seems punitive and not preventative."-- Deepfriedokra (talk) 18:52, 1 November 2026 (UTC)
  • Endorse initial block, but overturn now weird vote. I’m aware. I think there was sufficient cause for an admin to issue a block: there was previous admitted AI usage and some of the articles did have trigger words for LLM usage, which we now know is based on using copilot to copy edit in an offline (likely enterprise) version of MS Word. I severely struggle with the idea that someone should be namespace blocked from all of article space for using a tool which a reasonable person could believe falls within the policy that saysp Editors are permitted to use LLMs to suggest corrections to their own writing, and to incorporate them after human review, especially when upon sourcing review at AINB it appears that editor is familiar with the sourcing and did verify them. I am personally of the belief that admins should be willing to proactively unblock in situations like this where they’ve issued a good faith block, their assumptions were not entirely born out, and the blocked party is actively engaging. I’m not an LLM fan by any means, but I also have enough experience with copilot being pushed for the review of even professional level writing, that I can very easily see what happened here and a block from article editing is not a proportionate response now that we have more information. TonyBallioni (talk) 19:12, 1 November 2026 (UTC)
    I am fully on board with lifting a block when an editor has committed to changing their approach, as Rehman seems to have done. That is not the same as overturning a block, which implies the basis for the block was incorrect when placed. Indeed Rehman's own words suggest it was not: they were under a misapprehension as to the nature of the tool they were using. Vanamonde93 (talk) 19:19, 1 November 2026 (UTC)
    I’m aware, but I also don’t think there’s evidence they used it non-compliantly. From what I can make out of the AINB it was used for copy editing and all the sources verify. There were reasonable grounds to make the block, but I am struggling to see an actual recent policy violation. I’m not really sure where you’d classify “initial block was in good faith and on reasonable grounds, but the admin appears to have been factually mistaken as to if there was an ongoing policy violation.” I do think the fact that, based on what we’ve seen at AINB Iseult was wrong in his assumptions of ongoing use outside of policy, there should be some sort of record of that for fairness to Rehman. I would actually support a total ban on LLM use, but that is not what existing policy is, and the narrative that Rehman committed to no longer violating policy misses the fact that outside the initial use which he has stopped, there doesn’t actually appear to have been a policy violation as the policy is currently written, unless I’m completely misreading AINB. That is relevant here. TonyBallioni (talk) 19:30, 1 November 2026 (UTC)
    The Copilot assistance appears to have gone beyond basic copyediting. As Kowal2701 pointed out at AINB, the three September articles included failures of source/text integrity, which is the kind of error that is often generated by using text suggested by LLMs. Dclemens1971 (talk) 19:36, 1 November 2026 (UTC)
    You’re omitting the rest of the conversation . TonyBallioni (talk) 19:43, 1 November 2026 (UTC)
    Just because it has been brought up again below, I would disagree with the assertion that there's no evidence they used AI non-compliantly. Rehman's self-admitted usage of Copilot goes beyond exceptions for basic copyediting provided by NOLLM. Even without the admission, the stylistic evidence presented at AINB is strongly indicative of AI use beyond basic copyediting, and I don't think anyone at AINB has disagreed with that. I think it is now clear that Rehman has not used AI beyond copyediting in general, that they have not intentionally deceived anyone, and that they have engaged in good faith the entire time, but the fact that it is now appropriate to unblock them does not retroactively render their earlier edits compliant with NOLLM. Kisseran (talk) 22:19, 1 November 2026 (UTC)
  • Endorse. It is standard protocol at AINB that when an editor has been warned about LLM use, and then uses LLMs after a warning, to be blocked from mainspace to prevent further disruption while cleanup efforts continue. Rehman was warned in June, then made edits in September that had WP:AISIGNS. Rehman denied that they used any LLMs in September (those 3 articles were fully written by myself). Multiple editors concurred at AINB that this answer was not likely to be true, and lo and behold, the editor was indeed using an LLM (Copilot). A mainspace block while we figure out the extent of LLM-assisted contributions and prevent further disruption to the project is standard here, and the only difference between Rehman and other editors reviewed at AINB is that Rehman is an admin. An admin should be held to a higher standard, not a lower standard. But Iseult's block is holding Rehman to the same standard we use elsewhere at AINB. Finally, this block has no bearing on the recall effort, which was initiated by a different user, and bringing up the recall effort as an objection to Iseult's valid block is inappropriate. The blocked editor has not requested unblock and can do so at any time. Dclemens1971 (talk) 19:16, 1 November 2026 (UTC)
    IMO, if that's standard protocol, it should change. AINB doesn't get to ignore WP:PREVENTATIVE, per WP:LOCALCONSENSUS. Levivich (talk) 19:22, 1 November 2026 (UTC)
    Such a block is indeed preventative. An editor editing with LLMs can create a lot of content in a short amount of time that takes volunteers much longer to review and clean up. We don't full-indef, we pblock from mainspace pending further discussion. Editors thus blocked can continue to contribute with edit requests and submitting drafts, which allows them to demonstrate that they are no longer using LLMs in a disruptive way. Dclemens1971 (talk) 19:28, 1 November 2026 (UTC)
    What you are describing is directly contradictory to WP:PREVENTATIVE. By your logic, we should pblock everyone from mainspace who has violated policy. We should pblock from mainspace everyone who edit wars to ensure they no longer edit war anywhere. We should indef everyone who is uncivil to make sure they aren't uncivil anywhere again. Etc. But that's not how blocking policy works. If someone is not editing mainspace for a month and is responding to the noticeboard thread, there is literally no reason to think they're suddenly going to make disruptive edits to mainspace again. And this is especially true where, as Tony points out, the editor hasn't even actually violated any policy in the first place. Levivich (talk) 19:34, 1 November 2026 (UTC)
    Copilot is an LLM, Rehman acknowledged using it, and Rehman has not addressed the multiple failures of source-text integrity in the Copilot-assisted edits that are unlikely to be the result of simply using Copilot for spell and grammar checks.
    As for LLM-related block, I suggest spending some time working at AINB or on LLM cleanup to see how LLM-assisted editing creates substantially more cleanup work for our volunteer community. I believe the current pblocking practice is preventative and well within community expectations for editors who have used LLMs after being warned. Dclemens1971 (talk) 19:41, 1 November 2026 (UTC)
    This sort of touches on another issue: what do we do in cases akin to WP:ANIFLU? We sometimes get it where someone who's continued to use LLMs past warnings goes inactive, then returns months later to make some more LLM edits, then goes inactive again, and nobody notices at the time, rinse and repeat (ofc if that happens several times then a block gets made, but it's time-consuming and there's the possibility the edits don't get noticed at all). Blatant ANIFLU is usually met with a mainspace block, but WP:PREVENTATIVE says blocks are only to prevent "imminent disruption"; there's no guarantee they'll return, but if they do they're likely to continue the same behaviour. Imo mainspace blocks that get lifted after a simple promise to change their behaviour are a good measure even if there's some inactivity prior to filing, but this is very out of step w community norms (and despite what people say below, these blocks don't get made at AINB) Kowal2701 (talk, contribs) 12:27, 2 November 2026 (UTC)
  • Endorse. An arbitrary timeframe does not determine whether a block is punitive or preventative. The relevant consideration is whether the administrator placing the block could reasonably believe that it was necessary to prevent future disruption. At the time the block was placed, the discussion at AINB had multiple editors agreeing that Rehman had continued to use LLMs past their previous warnings and notices for it, over multiple articles, over several months; and, when questioned about it, had (in the most charitable reading) continued serious misconceptions about what constitutes acceptable LLM usage. There had been no recognition of error and undertaking to change, and given the repetition of AI usage post-dating the previous warnings, an explicit commitment to change is the minimum needed. As such the block was well-within discretion.
    There is also quite some irony in Levivich's complaint that Rehman was given insufficient time to respond, given that he posted to Iseult's talk page at 21:02, and posted here about 22 hours later, during which time Iseult made four edits, three directly related to queries about Rehman and one in response to a ping. Vanamonde93 (talk) 19:19, 1 November 2026 (UTC)
    I don't think it's reasonable to believe that a mainspace block is necessary to prevent disruption when the editor hasn't edited mainspace in over a month. There is literally no reason to believe that they will make non-policy-compliant mainspace edits if the editor has made no mainspace edits at all for a month. As to the irony, I did what Iseult didn't do, which was wait for a response until the other editor returned to editing. If four edits was not enough, should I have waited until there were 8? 12? That seems "arbitrary"... Levivich (talk) 19:25, 1 November 2026 (UTC)
    No, you should have waited until Iseult had replied, or they had indicated they were turning to other matters. It's not the number of their edits that concerns me, it's that they were clearly spending their available time addressing the same matter you were complaining about. Vanamonde93 (talk) 19:36, 1 November 2026 (UTC)
    I don't think that's reasonable. They clearly were not interested in addressing my complaint about the block or others' complaints about the block at both AINB and the recall petition. Their only comment on it was Special:Diff/1383060581 AFAIK. That they were addressing the AINB thread without addressing the block is what demonstrated to me that they weren't interested in discussing the block. In that case, there's no reason to wait. Levivich (talk) 20:06, 1 November 2026 (UTC)
  • Endorse. A preventative block is a block that prevents disruption that an admin believes is likely to occur. A punitive block is one where the disruption is in the past, we have no reason to believe that it is likely to recur, and an admin blocks anyway. In this specific case, the admin had no reason to believe the disruption would not recur, since the admin had continued the behaviour past prior warnings, and did not (and perhaps still does not) understand the issue at hand. If the editor had immediately appealed this block (something they still have not done), I do not believe I would have unblocked, let alone overturned the block, which is what we are being asked to do here. In solidarity, asilvering (talk) 19:45, 1 November 2026 (UTC)
  • Not endorsed. This was not a preventative block, and if AINB admins are making these sorts of blocks as a matter of routine then they need to stop forthwith. There was absolutely no reason to believe that Rehman would violate the AI policy when they had not done so at any previous point during the discussion. When an editor is engaging with the discussion and not engaging in the allegedly disruptive content then there is nothing preventative about a block. That AI use is involved does not change any of that, no matter how much anybody dislikes AI nor whether there are or are not good reasons for that dislike. We are here to build and encyclopaedia, we do not encourage editors to follow our policies when admins blatantly disregard policies themselves. Thryduulf (talk) 19:50, 1 November 2026 (UTC)
  • Endorse initial block but unblock now I agree with TonyBallioni above; the block was reasonable at the time it was made but has been overtaken by events and no longer serves a preventative purpose. * Pppery * it has begun... 19:56, 1 November 2026 (UTC)
  • Not endorsed/overturn There was an ongoing discussion at AINB at which Rehman was putting forward not unreasonable answers and explanations for the questions asked of them. IMO the block was too hasty and not preventative given their lack of mainspace editing. Number 57 20:00, 1 November 2026 (UTC)
  • Endorse The block is completely in line with how AINB blocks are handled. If the editor in question is viewed as not fully disclosing their AI usage after repeated prompting, they typically get an indefinite article-space block as WP:PREVENTATIVE until the editor admits the full extent of AI-usage and commits to not using AI for future edits. That's what happened here, and regardless of whether Rehman is unblocked very shortly or not, nothing was out of line with the previous block. EaglesFan37 (talk) 20:08, 1 November 2026 (UTC)
    • To be very clear; what you’re calling for is not existing en.wiki policy, which does not forbid all LLM use. As I mentioned in my comment, there’s currently no evidence of recent policy violations based on the AINB discussion. TonyBallioni (talk) 21:41, 1 November 2026 (UTC)
      I know that WP:NOLLM does not forbid all AI usage. I should have said impermissible AI usage in my comment. That's my fault. EaglesFan37 (talk) 21:55, 1 November 2026 (UTC)
      • And again; there’s zero evidence of recent impermissible use based on the current discussion. I would support an RfC making what occurred a policy violation, but that’s not how it’s currently written. TonyBallioni (talk) 22:04, 1 November 2026 (UTC)
      The blocking policy, per the recent RFC, does allow for admins to block in cases of persistent usage of large language models though. GreenLipstickLesbian💌🧸 21:56, 1 November 2026 (UTC)
  • Endorse. When an editor is found to have submitted LLM-generated edits, and the editor responds without acknowledging the full extent of their LLM use when the issue is raised, the editor is highly likely to continue using LLMs in violation of the applicable policies and guidelines, and a block is warranted to prevent further LLM misuse. In this particular case, Rehman later said that they did not know Microsoft Copilot was an AI tool when they were using it for their edits, and we are already in the process of re-evaluating the block at Wikipedia:AI noticeboard/Rehman in light of this newly presented information. However, Iseult's block was justified based on the information available at the time it was placed. — Newslinger talk 20:39, 1 November 2026 (UTC)
  • Endorse I think AINB reasonably concluded that AI usage was not going to stop based on what was posted. A partial block was the appropriate scope. I think there's some version of an appeal that could be made which would support an immeadiate unblocking, but that appeal should actually be made by ARehman rather than conjured by an admin. Best, Barkeep49 (talk) 20:43, 1 November 2026 (UTC)
  • Overturn Per WP:BLOCKP: "Blocks should be used to...prevent imminent or continuing damage and disruption to Wikipedia...deter the continuation of present, disruptive behavior..." Nobody can reasonably argue this block met that criteria. As noted above, arguing that similar blocks are routine for AINB is a matter of serious concern - not something that excuses or justifies this block. I know that editors at AINB are extremely aggressive in their anti-AI enforcement but local consensus cannot override our blocking policy. AusLondonder (talk) 21:20, 1 November 2026 (UTC)
Overturn. This was not a justified block; if we have a new AINB-only practice that we do bad blocks, then we should stop doing that. jp×g🗯️ 21:38, 1 November 2026 (UTC)
  • Comment Was there reasonable suspicion Rehman was using AI inappropriately before, and that such usage would continue? Yes--at least as far as what I saw in the DRV. Has it now been brought to enough people's attention that any further issues that might arise will be dealt with swiftly? Probably also yes. Jclemens (talk) 21:57, 1 November 2026 (UTC)
Endorse if an editor spent months adding copyvio to articles, and had been repeatedly warned, and repeatedly (in good faith, but erroneously) denied that what they were adding was copyvio, admins should not be expected to wait until their next edits which all evidence suggested would by copyvio, until blocking them. Replace copyvio with LLM. Blocks are cheap and easy to overturn, and in this case it even looks like they should probably be unblocked. 1brianm7 (talk) 22:04, 1 November 2026 (UTC)
Endorse – I think Barkeep and asilvering described the situation best at the RECALL. An indefinite block is not infinite. This is a case of WP:SUPERMARIO.

The editor in question had been warned for AI use in the months previous, and their responses at AINB were found to be inadequate. If there had been no prior warnings or discussion, I agree this block would be very strange. But a block under these circumstances is quite normal. The only thing that makes this abnormal is that administrators can usually expect to be insulated by the WP:SUPERMARIO effect. I do not think it is right that admins can expect this special treatment.
— User:Asilvering 18:21, 31 October 2026 (UTC)

The violations occurred over a long period of time from an editor who only edits sporadically, there was reason to believe that the concerns were not being addressed given the assessment made of Rehman's denials, and the block was indefinite to reflect that it was unknown how long a block might be needed to prevent future disruption.
— User:Barkeep49 18:31, 31 October 2026 (UTC)

FaviFake (talk) 23:00, 1 November 2026 (UTC)
  • Administrative action review should not be used: [...] to request an appeal or review of an action with a dedicated review process

    Is not the block appeal process the dedicated review process? Izno (talk) 23:01, 1 November 2026 (UTC)
    An unblock request is an appeal process but not a review process: ultimately it is a single administrator deciding to grant the unblock as being no longer necessary or incorrect on the merits, and the request itself is not a consensus-based process usually. Other admin actions, like page moves and deletions, do in fact have dedicated consensus-based review processes. Vanamonde93 (talk) 23:13, 1 November 2026 (UTC)
    I don't think it is. An appeal can be accepted for two reasons (broadly speaking): the admin errered or the admin was correct and assurances have been given such that the block is no longer necessary. And all of that happens by a single administrator rather than the community in almost all situations. For both lacking clear feedback to the admin who has performed the action (blocking) and the lack of a community consensus (vs an individual) the appeals process in not the dedicated review process in my mind. Best, Barkeep49 (talk) 23:14, 1 November 2026 (UTC)
Endorse. The block was indeed preventative as the editor in question continued to introduce LLM generated edits after prior warning. Katzrockso (talk) 23:04, 1 November 2026 (UTC)
Endorse, in addition to the arguments Favifake notes, as was shown later in the discussion, even after the block the p-blocked editor was unaware that they were using AI tools in some cases. It was a very perceptive preventative action. CMD (talk) 23:51, 1 November 2026 (UTC)
Comment: as I said at the RECALL, my thinking was described by Barkeep and asilvering. Favifake has very helpfully copied their comments here. In solidarity, Iseult Δx talk to me 00:14, 2 November 2026 (UTC)
Endorse the action as it was made at the time. This seems like an acceptable use of a preventative block and in line with how admins deal with users suspected of persistent disallowed LLM use. As someone else put it eloquently above, if the user had instead been adding persistent copyvios to articles, they would also be indef blocked - it doesn't matter if it were an admin doing it. That being said, the user has committed not to using LLM, so I would also say that there is a basis to consider an unblock. This is not the same as overturning the block, which would imply that the block wasn't justified in the first place (and I don't agree that it's unjustified). – Epicgenius (talk) 00:21, 2 November 2026 (UTC)
How can someone be "persistently" doing something that they haven't done in over a month? Levivich (talk) 00:53, 2 November 2026 (UTC)
LLM use is prohibited for article writing on Wikipedia. If this were something like spamming links, would it be acceptable if I were to be told not to spam, then keep surreptitiously doing it anyway, then stop for a month without assuring anyone that the spamming would stop? Additionally, as I said, there is a good basis to unblock right now, as no disruption is currently happening, even though I agreed with the original action. – Epicgenius (talk) 02:02, 2 November 2026 (UTC)
Why ask the wrong question ("would it be acceptable")? The right question is "should you be partially blocked from mainspace for spam you added over a month ago if you haven't added any spam since and were responding to the noticeboard discussion about the spamming?" And the answer is no, of course not. We never do this, I guess except lately at AINB. I challenge anyone to produce even one example of someone blocked for something they did 30+ days prior while actively engaging in a noticeboard discussion about it. I predict no such examples like this will be produced. Go ahead, endorsers who say this is normal: make me eat my words. Levivich (talk) 02:07, 2 November 2026 (UTC)
A quick skim of open CCI cases finds an editor who responded to a request. The editor was given a time-limited three-month block after it was realized that they had previously been blocked and warned for the behavior, but seemed to have some understanding of the issue from the response. They waited out the three-month block, returned to their ways, were indefinitely blocked, and have turned to sockpuppetry. 1brianm7 (talk) 03:09, 2 November 2026 (UTC)
That person edited mainspace less than a day before being blocked. How can you think that's even close to this case? How do you miss "30+ days prior" in bold in what I wrote? That's the whole point of this block challenge: 30 days! Levivich (talk) 03:13, 2 November 2026 (UTC)
You're missing a critical part here: "while engaging in a noticeboard discussion and denying they had been spamming" would be more closely analogous. In solidarity, asilvering (talk) 03:12, 2 November 2026 (UTC)
Yeaaahhh but not exactly. How is it that we know they used copilot? Because they told us so. That's not really denying using the tool; that's not understanding that tool was banned, which is reasonable for the reasons Tony has written about. And even still: let's see an example of someone blocked for something they did 30+ days ago while actively engaging in a noticeboard discussion even if they denied violating policy. Levivich (talk) 03:16, 2 November 2026 (UTC)
Overturn, it looks punitive rather than preventative to me. - Donald Albury 01:05, 2 November 2026 (UTC)
  • This is my understanding of the situation for both parties: Rehman used dedicated LLMs months ago, and was warned for it. Then, the timeline diverges: Rehman continued using Copilot (through another app), while not knowing it is also a LLM tool. From Rehman's perspective, they've changed their behaviour and are complying with the LLM guidelines. From Iseult's perspective, this is a warned user continuing the behaviour they were warned for. Thus, the block is understandable in meaning to prevent persistent LLM misuse, in denial.
    This quagmire wouldn't have come to pass if the Copilot misunderstanding was clarified earlier. Regardless, there is some fault here with both users – Rehman should keep themselves up-to-date with Wikipedia's guidelines, doubly so when editing sporadically, and triply so for LLM usage they were explicitly warned for, where WP:LLM's first note mentions LLM models "such as... Copilot". Per contra, I am not a fan of Iseult requesting a response from Rehman, but then investigating further and blocking without waiting for that response, especially since Rehman had already been engaging with users in AINB.
    This appears oxymoronic, but I believe the block is a reasonable one that should not have been made. Since Rehman was actively engaging in AINB and not editing mainspace, even without the post hoc knowledge of the Copilot confusion, the block was unnecessary at the moment. If, after completing the discussion, at the conclusion of the AINB case it is clear that Rehman is unable to adhere to the LLM guidelines, then they should be sanctioned, but not before that. If AINB's current workflow sanctions users while reasonable communication is ongoing, it should be changed. DatGuyTalkContribs 01:29, 2 November 2026 (UTC)
  • Reasonable-ish but lift now - I understand the block if Iseult thought Rehman was about to edit mainspace. They had already stopped editing mainspace long before the AINB report, so it's time to lift the block as it's not preventing anything. Star Mississippi 01:37, 2 November 2026 (UTC)
  • Endorse I am pro AI. But it is limited, and cannot meet our content policies yet. When it is used outside of policy it can quickly overwhelm our human content reviewers. I hope that this block does not have to last long, but the behavior needs to be remedied. HighInBC Need help? Just ask. 02:33, 2 November 2026 (UTC)
  • Reasonable block but lift now - It is no longer preventative. THEZDRX (User) | (Contact) 06:26, 2 November 2026 (UTC)
  • I have lifted the partial block following an unblock request by Rehman. While I have commented above, this was an individual admin action following an unblock request and recent input from Rehman subsequent to the block, and is not a statement either way on the original action under discussion here. CMD (talk) 07:55, 2 November 2026 (UTC)
  • Not endorsed in this case the *scope* of the block is punitive and far exceeds the consequences of the infraction. Those supporting this seem to be advocating that the level of infraction is irrelevant. Regards, --Goldsztajn (talk) 09:00, 2 November 2026 (UTC)
    What do you mean by the scope? The fact that it was a main space block? Katzrockso (talk) 13:11, 2 November 2026 (UTC)
    The punishment did not fit the crime. At this point, it's irrelevant to debate if a different block should have been applied. This was a completely disproporationate sanction and one made in error as there was no indication of immanent need for preventative action. There's a sort of thoughtcrime attitude afoot here. Regards, Goldsztajn (talk) 13:42, 5 November 2026 (UTC)
  • Endorse Apparent persistent LLM use is reasonable grounds for an article-space block. --SarekOfVulcan (talk) 14:53, 2 November 2026 (UTC)
    Except they weren't persistently using LLMs. They had previously used LLMs and were actively engaging with the discussion and not using LLMs while doing so. Thryduulf (talk) 15:13, 2 November 2026 (UTC)
  • Endorse - Reasonable action given the circumstances. There was no evidence that the disruption would not have continued the next time mainspace was edited. I also support CMD's lifting of the block now that there is evidence against potential continued disruption. mdm.bla 18:13, 2 November 2026 (UTC)
  • Not endorsed There was absolutely no reason to assume Rehman would continue using AI based on the noticeboard discussion he was participating in. Issuing a block in this scenario is a massive temperature raising escalation without fixing anything, and could have undermined the diplomatic resolution editors were working at when it was issued. Parabolist (talk) 18:40, 2 November 2026 (UTC)
  • Endorse per FaviFake referencing Asilvering and Barkeep49. If an editor has been warned for using AI, remains unsure on PAG, and whether they are using AI, a mainspace block is purely preventative to avoid any further unintended use of AI. Also endorsing the unblock since the matter of AI use has since been resolved. CNCin solidarity (talk) 21:16, 2 November 2026 (UTC)
  • Endorse but it's probably time to lift it. Preventing problems with a block is often a guessing game, you look at the likelihood of the actions being repeated and you have to use your best judgement. There is no hard rule preventing a block just because they have temporarily stopped editing in an area while the issue is debated. In this case, it wasn't clear they got the message about using AI. A block wasn't required but it falls within reasonable admin discretion to use the tools for this purpose. Dennis Brown - 2¢ 22:33, 2 November 2026 (UTC)
    @Dennis Brown (and anyone else who commented in the last 20 or so hours), just FYI, the block has already been lifted. Accessedgrant (Epicgenius mobile alt) (talk) 05:28, 3 November 2026 (UTC)
  • Endorse, echoing the points articulated by Dclemens1971, Vanamonde93, asilvering, Newslinger, etc etc... Placing this block in context, reading the AINB discussion in full, this block was a reasonable short-term preventative measure given what we now know was a major misunderstanding on Rehman's part. Even good faith use of LLMs in mainspace can result in a massive cleanup burden, and this block was clearly intended to prevent any further disruption while discussions proceeded. I think this review request jumped the gun - initiating this review while the AINB discussion was active and before Rehman responded to the block was unnecessary and seems more like a scolding than a productive step towards settling this matter. I'll note that Rehman handled this with grace and is now unblocked. Ethmostigmus 🌿 (talk | contribs) 06:42, 3 November 2026 (UTC)
    Which part of the ANIB discussion indicated that Rehman would continue with this editing during the discussion? That's the baffling thing here. He hadn't been editing for some time, was not editing this way during the discussion, and was responsive and graceful during the discussion. Where was any amount of evidence whatsoever that he would've flaunted the discussion and added more AI material before it resolved? Parabolist (talk) 09:09, 3 November 2026 (UTC)
  • Endorse. The argument that this was not preventative holds no water. This editor was likely using AI for over two years (see Iseult's comment when the block was placed and Rehman's reply ; I'm guessing "after covid" means the burst of edits in January 2024). Rehman regularly spends months or years away from the project (xtools monthly edit counts) and described their own recent contributions as "started editing is shorts bursts" [sic]. They also had a history of not adequately responding to warnings about AI use. With this track-record, there was a clear possibility of them disappearing for months or years to come back and start editing again, still without understanding that using AI to write articles is not allowed. This block prevented that possibility; it was preventative. The block has now been appealed and Rehman unblocked by an uninvolved admin, which is not the same as "overturning" the original correct block. Toadspike [Talk] 10:23, 3 November 2026 (UTC)
    To answer @Parabolist's question to Ethmostigmus: Rehman's most recent reply at AINB before Iseult's block cited their responses in June to warnings by Gnomingstuff and Gurkubondinn as examples of their transparency. The reply at AINB and the two responses cited repeatedly emphasize how they only used AI "to rephrase/restructure articles" and that they checked everything manually. This does not show an adequate understanding of WP:LLM, which has prohibited anything beyond basic copyediting since at least since March 2026 . When an editor reiterates the same misunderstanding over four months, that is not evidence that their behavior will improve, it is the opposite. Whether the editor is "responsive and graceful" is irrelevant their capacity to continue causing harm to the project. Toadspike [Talk] 10:50, 3 November 2026 (UTC)
    "Rehman regularly spends months or years away from the project (xtools monthly edit counts)" What in the world are you talking about?? That chart does not show any months or years spent away from the project. Man, people just make stuff up. Just say anything to justify this. Levivich (talk) 14:34, 3 November 2026 (UTC)
    In 2022, Rehman only made one edit, and that was this edit to their userpage. From March 2022 to August 2023 they made no edits at all; their next edit after their February 2022 edit was this September 2023 edit to their userpage. They also made no edits May-September 2024, May 2025, July 2025, February of this year, and May of this year. (All of this can be seen by simply scrolling down to the bottom of the monthly edit counts.) SuperPianoMan9167 (talk) 16:11, 3 November 2026 (UTC)
    Please retract your erroneous WP:ASPERSIONS, @Toadspike didn't make anything up. Katzrockso (talk) 16:55, 3 November 2026 (UTC)
    I must speak a different language where that isn't described as "regularly spends months or years away from the project". Similarly, in the English I speak, something that doesn't happen for a month isn't called "persistent" and something that's never happened before isn't called "routine." Also, "aspersion" is the most overused damn word on this website, and in my English, it doesn't mean "something I disagree with." In my English, when a policy says "a block should be used to prevent imminent or continuing damage and disruption to Wikipedia; deter the continuation of present, disruptive behavior," but for some people, something that hasn't happened for a month is "imminent," "continuing," and "present." Also, blocking someone who is actively engaging in a noticeboard discussion apparently helps "encourage a more productive, congenial editing style within community norms." Whatever.
    Here's my takeaway from this:
    • If you making disruptive edits every day, you need to be blocked to stop the disruptive edits. If you haven't made a disruptive edit in over a month, you also need to be blocked because you might make one again at any time.
    • If you are ignoring discussion, you need to be blocked, because we have no way to know if you're going to continue the disruption. If you are engaging in discussion, you also need to be blocked because we have no way to know if you're going to continue the disruption.
    • If you make many edits every day and some of them are disruptive, you need to be blocked to stop the disruptive edits. If you make too few edits, or made too few edits in the past, you need to be blocked to stop the disruptive edits.
    • If policy says only to block to stop "imminent," "continuing," and "present" disruption, that also means you should block to stop something that hasn't happened in over a month.
    No matter what you do, "that's a paddlin'," but it's not a punitive paddling, it's a preventative paddling. Got it. Levivich (talk) 17:36, 3 November 2026 (UTC)
    So if being inactive for months at a time isn't "regularly spends months or years away from the project" in your view, then what is? Please explain.
    Also I highly doubt this block would have been contested at all if the target of the block was not an admin, especially given that said admin is currently facing recall. SuperPianoMan9167 (talk) 17:50, 3 November 2026 (UTC)
    The "s" after a word means it's a plural. And "regularly" means "happens a lot" not "has happened in the past." Someone who has edited in every single year in the past 18 years straight does not regularly take years away from the project. Someone who took a year off, years ago, is not someone who regularly takes years off. And even aside from the semantics, good block because they have taken months off from editing in the past, even though they've been editing every month for the last six months? Like as if we can't trust someone who has taken a month off at some point in the past? Are you kidding me?
    This guy did exactly what we want everyone to do: stop making the disruptive edits and engage in the discussion about it. Still gets blocked! "It's preventative!"
    You can't semantics your way around the fact that our policy says blocks should be used to stop "imminent," "continuing," "present" disruption, and you can't semantics your way around saying that something that hasn't happened in over a month is imminent, continuing, or present.
    Here's a question: what could Rehman have possibly done differently after the AINB started to not get blocked? Can anyone think of even one thing?
    And anyone who suggests that I am circling wagons around admins is a joker. I am the guy who spent years campaigning for XRV, RECALL, etc. I started this not to protect an admin but to protect the rest of us from admins, from being blocked for something we did a month ago even when we haven't done it again, while in the middle of a noticeboard discussion about it with the blocking admin. Get real with your facts and accusations. Levivich (talk) 18:02, 3 November 2026 (UTC)

    And "regularly" means "happens a lot" not "has happened in the past."

    No, the adverb "regularly" means "in a regular manner". ‑‑gurkubondinn 18:11, 3 November 2026 (UTC)
    lol, and, pray tell, what does the adjective "regular" mean? Levivich (talk) 18:13, 3 November 2026 (UTC)
    Something that happens in a repeated manner. You're looking for "frequent" or "often". I'm not here to argue about word definitions (and won't engage with this any further because that wasn't the point), the only reason that I pointed that out was because you'd said that you must speak a different language and were commenting on what sort of English other people spoke. ‑‑gurkubondinn 18:24, 3 November 2026 (UTC)
    Nah, I was looking for the actual definition of the word, which is "recurring, attending, or functioning at fixed, uniform, or normal intervals," according to Webster. Levivich (talk) 18:36, 3 November 2026 (UTC)
    One of the reasons why I think this block would not have been contested if the target were not an admin is that people don't post to a high-visibility noticeboard when a non-admin gets blocked, and so most editors would be unaware of the block's existence. SuperPianoMan9167 (talk) 18:40, 3 November 2026 (UTC)
    That might be true: I'm not sure I would have been aware of it had it not been for the AN post. But can 100% guarantee I would have asked for this block review regardless of whether the person blocked was an admin or not.
    I was initially worried that other blocks like this were flying under the radar. But I now think this is the first time in Wikipedia's history that someone has been blocked for something they did 30+ days ago while engaging in a noticeboard discussion about it, mostly because nobody has been able to come up with another example. I think this may be the first time in Wikipedia's history this has happened. Thus I don't think any comparisons can be made, but I'm sure in my case and I'm pretty sure in the case of other critics of the block, it's not the user being an admin that matters, it's the 30-days-and-engaging part that matters. Levivich (talk) 18:49, 3 November 2026 (UTC)
    Which is how cultures, like that which according to some currently exists at AINB, can develop. Many editors have attempted to justify this block as preventative, but not a single one has done so. I'm not normally one to agree with Levivch, but on this occasion they are correct. I'd be surprised if this was the first time this had ever happened, although I have not looked for previous examples. It is definitely unusual in that the recipient was an admin though. Thryduulf (talk) 18:51, 3 November 2026 (UTC)
    Clarifying that my "I'd be surprised" comment above is referring to blocks for 30-day-old actions not agreeing with Levivich (that is rare, but I don't think it's a first!) Thryduulf (talk) 19:17, 3 November 2026 (UTC)
    I'm not an admin and am involved, but the way I perceived it was that they'd continued to use LLMs past a warning, their responses weren't making sense/lining up w the evidence, so the block was more like "lock the door, nobody's getting out till we get this resolved", rather than potentially letting the discussion peter out unresolved (and it was successful in that sense). But given no-one else appears to see it like that, I'm probably wrong. The big problem was that a recall was made, predicated on the block, without understanding its context (though tbf to Robert, they raised it on AN and nobody pushed back on it for 24hrs, by which time it was climbing up the page into obscurity) Kowal2701 (talk, contribs) 21:43, 3 November 2026 (UTC)
    Not understanding something is possibly the worst justification for using recall that I've seen. I'm still not seeing how what you've descirbed makes the block preventative? They were engaging at the noticeboard, like they had been for a while without engaging in the disputed behaviour, had been asked a question and then a couple of hours later, before they'd had a chance to reply, they were blocked. Had the block come before they engaged in the discussion I could see an argument that it was preventative, had they indicated they were going to disengage or continue as they were then again it would be preventative, but it was none of those things. Thryduulf (talk) 21:48, 3 November 2026 (UTC)
    They'd already promised to not misuse LLMs at the time of the first warning, but continued to do so, which when combined with how the responses at AINB weren't lining up w the evidence makes a decent case for it being preventative imo. Kowal2701 (talk, contribs) 21:55, 3 November 2026 (UTC)
    The evidence is that they genuinely believed they had kept their promise. The responses at AINB weren't "lining up with the evidence" because they had a different understanding of the questions to those asking them. The AINB regulars seem to expect everybody to have the exact same understanding of all the issues around AI, to have the same knowledge of what is and isn't AI that they do, and have the exact same opinion about AI as they do, despite the world not working that way. Thryduulf (talk) 15:52, 4 November 2026 (UTC)
    I don't think that's the case, the expectation is just that people know when they are using an LLM and will be upfront about that when asked, I don't recall any instances where someone was baffled upon learning of NOLLM and was under the impression the tech was perfectly reliable, for the most part it's just underestimating the issues or irresponsibility. Ofc that runs into issues on the rare occasion where people use something like Grammarly or CoPilot which are notoriously deceptive wrt being LLM-powered, but there's also irresponsibility there because people can still see what the tool is actually doing (i.e. turning sentences into slop or introducing source-text discrepancies) Kowal2701 (talk, contribs) 16:06, 4 November 2026 (UTC)
    You said it: the problem with "the expectation is just that people know when they are using an LLM" is that "people use something like Grammarly or CoPilot which are notoriously deceptive wrt being LLM-powered." You said called that a "rare occasion," and up until now, I agree, but I think it will be less and less rare in the future (see today's discussion at VPP about Edge). In this case, we have someone who was honest and upfront about using Copilot but didn't realize the Copilot use violated WP:NOLLM. As LLM and other AI tech becomes more and more integrated into all sorts of everyday software like web browsers and word processors, it will be harder and harder for anyone to know whether or not their software uses AI. It's one of the reasons that "thou shall not use AI" is an impossible expectation. And it's not what the guideline says anyway: it says do not use LLM to "generate or rewrite article content" (not the clearest standard), and it allows using LLM to check your spelling or grammar. Now the hole in that that's big enough to drive a truck through is that if you use Grammarly or Copilot to check your grammar and it suggests a change to a sentence and you adopt that change, you are arguably using LLM to "rewrite article content." Somehow this community in its infinite wisdom has decided to create a guideline with the giant hole in it. But people are going to use spellcheck and grammar tools that are widely available, and if those tools use LLM, Wikipedia is just going to have to allow that, because prohibiting it is both unenforceable and counterproductive. What we have here is a guy used Copilot to check grammar/spelling month ago and didn't realize this was (arguably) a violation of the guideline (I don't think it was actually) and committed to stop using it anyway but he still got blocked, as you also said, to "lock the door" just in case while the issue was being investigated (which I don't think is policy compliant but I guess I'm in the minority on that). Levivich (talk) 16:56, 4 November 2026 (UTC)
    Re the growing integration of LLM-powered copyeditors: we'll just have to see how things develop, but the content quality problems they cause will still be an issue. They're not banned, just discouraged, lots of people use them responsibly. More guidance wrt them will probably be necessary, I've been meaning to make WP:SPELL more useful/updated Kowal2701 (talk, contribs) 17:09, 4 November 2026 (UTC)
    @Levivich, Rehman himself said "I was away during and after covid" at AINB. I didn't "make up" this wording. Toadspike [Talk] 09:57, 4 November 2026 (UTC)
    "I was away during and after covid" does not mean "regularly spends months or years away from the project" (why do you make me type out this obviousness?) and it's nothing short of ridiculousness to suggest that because someone has a year gap in an 18 year history, or doesn't edit every single month of the year, that means it's "With this track-record, there was a clear possibility of them disappearing for months or years to come back and start editing again". Your judgment of Rehman is absolutely ridiculous, to the point of being insulting. "Clear possibility" isn't event the standard under WP:PREVENTATIVE. Why can't you just be honest and say "no there was no imminent, continuing, or present disruption, so the block didn't meet the standard of WP:PREVENTATIVE"? Ugh. Say it. Be honest: Not continuing. Not present. Not imminent. Admit it. And btw, taking a month or even year off from editing is not "disappearing." You should be apologizing instead of doubling down. It is unacceptable to suggest that someone is untrustworthy because they take wikibreaks. Levivich (talk) 15:13, 4 November 2026 (UTC)
    I don't like it being an inherent point against somebody that they aren't logging in every single day; people have lives that take place outside of this website... jp×g🗯️ 23:05, 5 November 2026 (UTC)
    +1 Goldsztajn (talk) 20:23, 6 November 2026 (UTC)
    I also strongly agree with this. Thryduulf (talk) 20:25, 6 November 2026 (UTC)
  • Not endorsed/Overturn Seems to be a pretty blatant and obvious violation of WP:PREVENTATIVE. If the editor hasn't edited mainspace in over a month and is actively involved in the discussion board about their activity, then there is no mainspace editing you're preventing by applying such a block. The claim of theoretical mainspace editing by the editor is unjustified and seems self-serving as an argument. The fact that there are multiple WP:AINB admins above claiming that this is standard practice for the noticeboard is highly concerning. It sounds like an open admission to willful and repeated violations of PREVENTATIVE by the admins in that area of work. I am distinctly reminded of the issue of rampant misuse of U5 speedy deletions by admins that resulted in the community repealing that category and making more explicit U6 and U7 groups to curtail admin abuse of speedy deletion. SilverserenC 22:58, 4 November 2026 (UTC)
  • I think most admins who have made blocks have realized in retrospect that a particular block they made maybe did not meet the 'least restrictive possible' ideal. Iseult, FWIW: when you're dealing with a clearly well-intentioned editor who just doesn't seem to get it yet, a good option is to leave them a note on their talk asking them not to (edit in main space, or whatever) until you were satisfied they understood. If after you'd made that request they'd edited in main space without respecting that request, that's evidence they aren't clearly well-intentioned, and the pblock probably wouldn't have been controversial. Valereee (talk) 18:35, 5 November 2026 (UTC)
  • Endorse This was clearly preventative, any user who is demonstrating confusion about policy and has repeatedly violated WP:LLM should be blocked until they show they understand it. It seems to me that there is no way anybody would have challenged the validity of the block if Rehman wasn't an administrator. Leaves something of a bad taste in the mouth to be honest.Boynamedsue (talk) 06:40, 6 November 2026 (UTC)
    I would have challenged the block if Rehman wasn't an admin and knew about it and multiple other people above have said exactly the same thing. We do not and should not block users because the violated a policy in the past, that's punitive not preventative. If they were continuing to violate a guideline or refusing to engage then you might have an argument, but they were actively engaging at AINB so that they did understand why their reading of the guideline was different. Thryduulf (talk) 12:19, 6 November 2026 (UTC)
    Bns, this was brought here by Levivich, who does not as far as I can recall have any history as an apologist for admins. Valereee (talk) 13:47, 6 November 2026 (UTC)
    Indeed rather the opposite. Levivich is arguably the most vocal editor when it comes to calling out admins when they make mistakes. Thryduulf (talk) 15:02, 6 November 2026 (UTC)
    Phew! For a minute there I was worried I was losing my rep.
    When an admin blocks another admin, if you endorse it, you're covering for an admin. If you don't endorse it, you're covering for an admin. Everyone on this page is covering for admins and it just won't stop! 🙃 Levivich (talk) 00:56, 7 November 2026 (UTC)
    (I know, I know, offtopic) And folks who aren't commenting on the block obviously don't give a fig about admin conduct, so they are covering too... Jo-Jo Eumerus (talk) 09:02, 7 November 2026 (UTC)
    "Levivich is arguably the most vocal editor" ... to be fair(er), I'd say vigilant. Regards, Goldsztajn (talk) 06:09, 8 November 2026 (UTC)
  • Comment. In five months at AINB I have heard other regulars say multiple times "There's no use asking for a block, they haven't edited mainspace in a month." And when we have asked for such a block admins have repeatedly refused. We have occasionally begged for one when the user's pattern was long absences followed by large LLM dumps; I don't recall that we have ever gotten it. As far as I know, AINB had not requested admin intervention on the Rehman case. I think it is therefore unfair to consider this block an expression of AINB praxis or culture.
I can't quite resolve to Overturn; but I wouldn't have done this myself as it violates what I understood to be accepted practice. M kuhner (talk) 22:42, 6 November 2026 (UTC)
To clarify: wouldn't have asked an admin to do it, as I am not an admin myself and of course cannot block anyone. M kuhner (talk) 00:09, 7 November 2026 (UTC)
  • Overturn or Disapprove The endorsers here are doing Iseult no favors. If Iseult had some belief they were preventing something, they were either mistaken or unreasonable. It is not reasonable to think the user was editing main space, when they were not for over a month, let alone editing it in a certain way. This disapproval is what holding admins to account should look like. Iseult was wrong and they should re-think, before it gets worse, and they lose so much trust, it is unrecoverable. Read carefully the above, especially if it stings. Someone above mentioned what you should have done instead of reaching for the block - do that. Also, the idea that there is walled-garden blocking regime at some noticeboard is absolutely terrible for the project. Alanscottwalker (talk) 23:45, 6 November 2026 (UTC)
    Also, the idea that there is walled-garden blocking regime at some noticeboard is absolutely terrible for the project I agree the idea is terrible, because it isn't true Kowal2701 (talk, contribs) 00:06, 7 November 2026 (UTC)
    Well then don't have people suggest it is. Alanscottwalker (talk) 00:20, 7 November 2026 (UTC)
Overturn this is a very, very odd block and I don't think there's any reasonable reason for it to have been done. Jishara (please ping upon response) (talk) 01:05, 7 November 2026 (UTC)
@Jishara (& others commenting overturn; noting that voting to overturn a block and to disendorse a block are slightly different things) note that Rehman has already been unblocked for a few days now, unblock request here. Ethmostigmus 🌿 (talk | contribs) 02:21, 7 November 2026 (UTC)
I don't think it's particularly necessary or helpful to get bogged down in semantics. It's fairly obvious what people mean (whether it's a good or bad block) even if their words aren't perfectly aligned with the current situation. Left guide (talk) 02:25, 7 November 2026 (UTC)
I'm not arguing semantics, I'm just letting folks who are just joining the discussion now know that Rehman is unblocked, given that not everyone has been present for (or cares to read) the whole discussion. Ethmostigmus 🌿 (talk | contribs) 02:29, 7 November 2026 (UTC)
Overturn is a functional equivalent to not endorse. If responses were unblock there might be some confusion, but I can't see that with the current situation. ScottishFinnishRadish (talk) 02:34, 7 November 2026 (UTC)
(Handy online thesauri suggest "baffle", "censure", "condemn", "denounce", "disparage", "protest", "reject", "repel", "repudiate", "thwart", and "unauthorize". —Cryptic 02:47, 7 November 2026 (UTC))
I think anyone bolding a !vote to "baffle" is likely to do just that. Thryduulf (talk) 03:36, 7 November 2026 (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.

Oct 2026 unblock decline by Deepfriedokra