Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

Wikipedia:Administrators' noticeboard/Incidents

From Wikipedia, the free encyclopedia
<Wikipedia:Administrators' noticeboard
Noticeboard for reporting incidents to administrators
Wikipedia's centralizeddiscussion, request, and help venues. For a listing of ongoing discussions and current requests, see thedashboard. For a related set of forums which do not function as noticeboards seeformal review processes.
General
Articles,
content
Page handling
User conduct
Other
    Administrators' noticeboard/Incidents

    This page is forurgent incidents andchronic, intractable behavioral problems.

    When starting a discussion about an editor, youmust leave a notice on their talk page;pinging isnot enough.

    You may use{{subst:ANI-notice|thread=}} ~~~~ to do so.

    Closed discussions are usually not archived for at least 24 hours. Routine matters might be archived more quickly; complex or controversial matters should remain longer. Sections inactive for 72 hours arearchived automatically byLowercase sigmabot III. Editors unable to edit here are sent to the/Non-autoconfirmed posts subpage.(archivessearch)

    Start a new discussion
    Centralized discussion
    Noticeboard archives
    Administrators'(archives,search)
    357358359360361362363364365366
    367368369370371372373374375376
    Incidents(archives,search)
    1190119111921193119411951196119711981199
    1200120112021203120412051206120712081209
    Edit-warring/3RR(archives,search)
    483484485486487488489490491492
    493494495496497498499500501502
    Arbitration enforcement(archives)
    343344345346347348349350351352
    353354355356357358359360361362
    Other links

    Bad-faith edits from Horse Eye's Back... again

    [edit]

    Horse Eye's Back (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log)

    Back in July,Horse Eye's Back (talk ·contribs) wasbrought to ANI for a pattern of bad-faith editing. User@Salvio giuliano: closed the discussion as a "final warning".

    My encounters with HEB began in July 2025 when theytaggedU.S. Route 131 with{{primary sources}}, then went on a tirade across various Michigan highway articles with similar tags. This included both of the discussions seenhere, where@LilianaUwU: called out HEB for drive-by tagging; HEB claimed the tags were "self obvious" and didn't need a discussion.

    Further down the page, they also challenged my removal of their{{More citations needed section}} from the exit list. Again,U.S. Route 131 is a featured article. I have never seen a highway article require citations at the junction list, unless it's for cases like an exit being removed or added or, in the case of this particular highway, a recent rename of a crossroad. When I asked what needed to be cited, they respondedliterally everything else andI've never seen anyone cite a road. When I pointed out the incredulity of their argument, and questioned what citations would satisfy their needs, they just shrugged it off withThats not my problem. There is no special standard for this unless I am mistaken... That it can't be done without OR is not an excuse for OR. This alone is absurd, but it goes way deeper.

    OnInterstate 275 (Michigan), also an FA, they put the same tags on. Inthe discussion, where they continued to dodge the question and claim the tags were "self obvious" and didn't need clarification. This just led to more circular arguments before I gave up.

    By my count, HEB tagged about 20-30 Michigan highway articles (every single one of which is GA- or FA- class) for{{primary sources}} in July 2025, all of which have since been removed.

    All of this fed into HEB's claims that maps are primary sources and should not be used in highway articles to verify things such as highway alignment. They tagged multiple Michigan highways, almost all FA- or GA-class, with{{primary sources}} and/or{{notability}}, not once touching discusison pages unless another editor such as myself stepped in first. From what I witnessed, all other editors (see LillianaUwU's edits too on U.S. 131) were met with the same responses: confrontational badgering or ignorance.

    On July 15,another editor (@Guerreroast:) called out HEB for their tagging, where HEB claimed that the previous GA nominations were improperly done, and that "five years ago" the community decided maps are primary sources. I was unable to find what discussion this was in reference to.@The ed17: joined the discussion and likewise claimed HEB should gather consensus before mass drive-by tagging articles, to which HEB tried to pull the old "I am rubber, you are glue" argument by sayingIf you are not willing to have a discussion of each edit then aren't you the one doing drive by editing? I also joined this discussion by pointing out again the frivolity of their "primary sources" argument, which led to the same waffle about "you can cite a map" even though they had previously claimed doing so at all is OR of a primary source. They then tried to go after Ed17 again with the same "no, YOU're the one mass drive-by editing!" argument.

    AtWikipedia:Requests for comment/Using maps as sources, unless I am misreading this extremely long discussion, it seems there is a consensus that maps are being used appropriately as sources on highway articles and there are no concerns with original research, synthesis of ideas, or other impropriety as a source.

    In the past couple days, HEB returned toreinstate a drive-by{{primary sources}} tag I removed, andreinstate one at the GA-classM-218 (Michigan highway) around the timeJustARandomSquid (talk ·contribs) filed a GAR for similar "are maps OR?" concerns as HEB. Naturally, HEB has tried to weaponize this as proof they were right, although as far as I can tell, JustARandomSquid is acting in good faith and was unaware of HEB's concerns.

    Since then, they have:

    1. Repeatedly gone around and reinstated tags that got removed. When Ipolitely asked them to stop, I was met with the same haranguing and bad-faith arguments as usual.
    2. Randomly jumped into the M-218 GAR with[Using maps as a source] isn't valid in any of those Featured Articles either, those all predate the modern standard... So none of those actually meet the good or featured article criteria, hence their reassessment. If you could list those dozens of articles it would help us clean up this mess quicker.
    3. Further claiming in the M-218 GAR thatA majority of editors agreed with me in community discussions. The way you want to use maps is in fact OR. Please seeWikipedia:Requests for comment/Using maps as sources which established the standing consenus on the issue. As I understand it, the RFC in question says the opposite: that using maps as a source in an article on a highway is perfectly acceptable
    4. Pinged methree times onTalk:M-65 (Michigan highway), asking me to explain my tag removal
    5. Pinged me, The ed17, and@Imzadi1979: onTalk:F-41 (Michigan county highway), asking us to explain our tag reomvals (note: F-41 was put through GAR for these concerns but ultimately kept as a GA, indicating there are no obvious issues with sourcing here)
    6. Posted on my talk page, claiming thatyou don't appear to be trying to get consensus for the disputed content you want to include, whatever that means
    7. Reverted The ed17's removal of dubious drive-by tags
    8. And of course, started athread onWP:RSN regarding whether or not maps are a primary source. Since this thread has started, HEB has posted overfifty times in response to other editors. Some of the highlights:
      • I find such tags useful because they let me know about an issue without having to analyse dozens or hundreds of sources. I'm not aware of any negative impact that such a tag could have, what am I supposed to be weighing the beneficial impact of a valid tag against if there is no harm? So far the only argument made against the tags is that they are inaccurate because DOT maps aren't primary sources... Hence this discussion, its a bit of a chicken and egg issue after all...
      • So the DOT source is not primary, secondary, or tertiary its not a source at all?
      • If the article is based largely on primary sources then the use of primary sources is excessive... But it can still be problematic even when the article is not largely based on them.
      • When I pointed out the "not my problem" quip on U.S. 131, they somehow thought I was referring toa discusison from 2007 in which neither one of us was involved; a clear bad-faith whataboutism argument if I've ever seen one. They also claimed to not know what I was talking about because I didn't use the word "primary", which is blatantWP:IDHT if I've ever seen it.
      • A claim that the editor in the M-218 GAR invalidated my argument that almost no one agrees with HEB's assessment
      • A claim that I was approacing HEB with "hostility" and telling them to "shut up and go away" when all I said wasdrop the damn stick and walk away from the dead horse.

    Again, HEB has responded in their own threadfifty times since beginning it, making the same whataboutism, bad faith, and otherwise confrontational unhelpful edits since I first crossed their path in July.

    The last ANI had only one passing mention of HEB's issues with highway articles, which might be why nothing came of it. But the issues here are extremely obvious:WP:TEND,WP:IDHT,WP:SEALION,WP:BLUDGEON... shall I continue?

    It's clear that HEB has been a problematic editor for some time, but I feel like focusing on one problem at a time will help to address their edits and prevent the headaches they're causing other editors such as myself.

    My proposal would be to initiate a topic ban against HEB, preventing either all edits to highway articles, or at least preventing addition of maintenance tags to them (comparable to Jax 0677's topic ban against maintenance templates).Ten Pound Hammer(What did I screw up now?)20:25, 6 December 2025 (UTC)[reply]

    'A claim that the editor in the M-218 GAR invalidated my argument that almost no one agrees with HEB's assessment' I mean, that's not particularly egregious? But yeah, FWIW, I was acting in good faith, I'm genuinely not amazed by the way these articles are sourced, but of course that's outside the scope of ANI. If there's consensus that these maps is ok, effectively edit-warring with maintenance tags is not acceptable. Sorry for contributing to this can of worms, I guess.
    P.S. You forgot to close a wikilink.JustARandomSquid (talk)20:38, 6 December 2025 (UTC)[reply]
    @JustARandomSquid: Don't worry, you didn't do anything wrong. This is strictly about Horse Eye's Back's behavior.Ten Pound Hammer(What did I screw up now?)20:40, 6 December 2025 (UTC)[reply]
    These days there are only a few editors I can think of on Wikipedia who are inevitably a drain on the patience of anyone else participating in a discussion with them, but whom the community has been unable to get its act together and ban. When I started editing, this sort were ubiquitous, but thankfully we've mostly all agreed that people who are chronically impossible to deal with should find other hobbies, because the cost on editor resources from others having to argue with them and burning out in frustration is greater than whatever benefit they provide. I don't really understand why an exception has been made for HEB several times over now—unlike some past unblockables like Eric Corbett or BrownHairedGirl, they don't strike me as someone who brings anything irreplaceable to the table—but if that "final warning" for "a pattern of incivility and uncollegial behaviour" is to mean anything, there's only one way for this to go. --Tamzin[cetacean needed](they|xe|🤷)20:43, 6 December 2025 (UTC)[reply]
    I am in general agreement with Tamzin about this matter and think it is worth remembering the specific wording of the late August warning:there is consensus that Horse Eye's Back has engaged in a pattern of incivility and uncollegial behaviour. Therefore, further instances of subpar conduct on their part should lead to escalating blocks. The continuation of the "incivility and uncollegial behavior" is well-documented in the diffs presented above. From my perspective, the issue now is how long a block ought to last. I think that disregarding a clear warning, failing to course correct, and immediately continuing the problematic behavior pattern is aserious problem. I recommend a one month block with a warning that block lengths will double each time if the misconduct continues, and that an indefinite block is very possible.Cullen328 (talk)21:12, 6 December 2025 (UTC)[reply]
    It's actually troubling that this isn't an indef, which would require discussion instead of waiting it out. It's a problem that we'd consider it something that should get lengthier time-limited blocks on each further behavior issue. With most editors, it would be an indef from the start.Valereee (talk)22:26, 6 December 2025 (UTC)[reply]
    The road editors forked. Y? –EEng
    Yknot? --Tryptofish
    I can't really emphasize enough howthis discussion starting a few comments in (and in particularthis post from me) exemplify how conversations can go with HEB. They're aggressive and overwhelming. You will feel defensive and badgered, and you may have to explain (in triplicate) our basic editing policies and practices for some reason. It is legitimatelyexhausting to engage with HEB.
    HEB knows that these are issues; for example, about two years ago, they said that they'd take concerns "to heart". Since then, they'vebeen admonished andgiven a final warning over their behavior.Star Mississippi's block is long overdue, in my opinion, and I don't have much faith that HEB is capable of channeling their energy into more collegial editing after it lifts. I hope I'm proven wrong.Ed [talk] [OMT]04:17, 7 December 2025 (UTC)[reply]
    I don't immediately see what is wrong in that discussion you linked. Is there a specific comment where you think things went awry? It looks like HEB is trying to discuss content and specific concerns with individual articles, which seems constructive to me. (t ·c)buIdhe16:17, 7 December 2025 (UTC)[reply]
    @Buidhe: The discussion I linked was prominently featured in the OP, which led to HEB being blocked. With respect, I'm not the only one to have seen issues in it. HEB often ostensibly focuses on content in their talk page posts, but they create disruption in other ways.This comment in particular outlines the concerns that I had there.Ed [talk] [OMT]17:32, 10 December 2025 (UTC)[reply]
    To my reading, you're in the wrong in that discussion. You're essentially filibustering the use of maintenance tags and trying to impose WikiProjectWP:OWNership on articles.Thebiguglyalien (talk)🛸17:44, 10 December 2025 (UTC)[reply]
    To the contrary, on those two points I used the R in BRD (to remove inappropriate maintenance tags) and suggested that editors active in the topic area would be useful in a centralized discussion.Ed [talk] [OMT]17:49, 10 December 2025 (UTC)[reply]
    Like others above I think that HEB's bad edits are in a wide range of topics, so I don't see that point of banning from only one of them. For example what topic ban could preventthis example of assuming bad faith, after I had the temerity to ask for abbreviations to be expanded?Phil Bridger (talk)09:56, 7 December 2025 (UTC)[reply]
    Because I feel like previous efforts to discuss the matter got bogged down by everyone pulling in a different direction, which is often how discussions go anymore if anyone discusses anything at all. And by focusing on just the ones I was privy to, I feel like we got a bit more momentum.Ten Pound Hammer(What did I screw up now?)16:27, 7 December 2025 (UTC)[reply]
    That seems like a reasonable response. I suppose banning from one topic is better that banning from none, although I would prefer to see a general ban come out of this.Phil Bridger (talk)20:43, 8 December 2025 (UTC)[reply]
     Comment: I just want to state that the way maps and spatial data are handled on Wikipedia is pretty problematic in my opinion. The roads issues here are silly, a valid reliable source is a valid reliable source, however broadly the way we handle the discussion of spatial information and the creation of maps on Wikipedia likely needs serious review. I believe the road issue is broadly an issue of the policy not being broad enough to give a clear way to handle the question of citing "where" something is, without relying on OR or Synthesis. There are a lot of places on Wikipedia where we aren't even using a reliable map as the source for where something is, including many of the locator maps on the pages for countries. This has caused problems with updating maps, deciding on which set of borders to use, and the lack of a clear MOS for maps has lead to massive swaths that the most polite literature would describe as "misleading." I regularly use Wikipedia maps in my introductionGIS class as examples of whatnot to do by having students dissect them based on the current weeks reading, it should not be easy for people with three weeks of training to roast a map here. I hope this discussion and others can eventually lead to this being addressed.GeogSage (⚔Chat?⚔)21:32, 7 December 2025 (UTC)[reply]
    Why keep knowledge secret and known only to an elite? Why not help democratize the knowledge needed to make good maps on Wikipedia?Viriditas (talk)00:34, 8 December 2025 (UTC)[reply]
    Folks, ANI is for discussing edit conduct, not for discussing wider policy/practice. Please continue this discussion at a more appropriate venue likethe Village Pump.Toadspike[Talk]00:42, 8 December 2025 (UTC)[reply]

    Here because of the previous AN/I issue. There is continual, incessant low-level incivility here...occasionally sufficiently severe enough to be noticed, but never (until just now) reaching levels requiring active intervention. HEB has been allowed enough rope to rig a clipper ship. I just don't know how many more capable, well-meaning, and polite editors need to be scorched before it becomes obvious enough to us that the community must take more serious long-term action. I would support an indefinite block, or, indeed, a CBAN, until this editor demonstrates that they clearly understand, and in the future eschew, the problems they are, deliberately, causing.Hiobazard (talk/contribs)18:14, 7 December 2025 (UTC)[reply]

    I'm partially-involved with respect to HEB (but not regarding any specific incidents mentioned in this thread; see e.g. our interactions atWP:RSN#Flightconnections, Flightradar24 and FlightsFrom - reliable to verify airline routes? and I know I've also been less than impressed with his behaviour in other discussions (but I can't bring the specifics immediately to mind), but I think there is a clear consensus here forsome action. What I'm not seeing is a clear consensus forwhat action. Personally I don't think a simple topic ban is going to be effective as I almost never edit articles related to US roads and so the behaviour with which people have issues is clearly not restricted to just that area. I'm reluctant to recommend full site bans, but given the evidence here and in previous times he's been brought to the attention of noticeboards, I'm unable to articulate a clear reason to oppose one here.Thryduulf (talk)21:02, 7 December 2025 (UTC)[reply]
    I'm with you. I'm currently involved in a content/policy dispute with HEB and am thus reluctant to comment on specific actions. But I feel some action must be taken. Several editors (including below) have pointed out that the last warning was final and the behavior has not changed.Toadspike[Talk]00:31, 8 December 2025 (UTC)[reply]
    Same boat. Have had more than one dispute with HEB in the past, I've avoided them since, and otherwise hadenough to say in the previous ANI to not need to repeat that here. Tamzin sums it up well at the beginning and the block by Star Mississippi has somewhat restored my faith in the system for now.CNC (talk)22:37, 8 December 2025 (UTC)[reply]

    In the ANI thread from August, linked at the top of this thread, that led to the "final" warning, I expressed the concerns I have had with HEB, and I provided a bunch of specific diffs, which anyone interested can find there. The consensus there was for a "final" warning, not some lesser sort of warning. I hope that "final" means something here on Wikipedia, and I'm not a fan of serial, successive, final warnings. Looking at his talk page, it doesn't look to me like he understands other editors' concerns or is serious about changing. I don't think this is about any particular topic area. If someone wants to propose a site ban, I'll support it. --Tryptofish (talk)21:12, 7 December 2025 (UTC)[reply]

    Also would support. At a certain point an editor, no matter how much good-faith they may have in their contributions to the project, becomes a time-sink when it comes to dealing with other editors, and HEB has long since, unfortunately, become that. -The BushrangerOne ping only22:21, 7 December 2025 (UTC)[reply]

    I was one of the people who believed that the next incident involving HEB should be a cban. I'm not convinced this is that next incident. To me, this looks like the latest in a long string of efforts by editors in the roads and highways topic area to play by their own rules and bully their way into getting what they want. I believe that HEB should have taken this to a different venue or handed it off to the broader community to discuss, but it's hard for me to say with confidence that he's the problem here.Thebiguglyalien (talk)🛸02:38, 8 December 2025 (UTC)[reply]

    Saying that roads editorsplay by their own rules and bully their way into getting what they want is a personal attack, or very close to it.LilianaUwU(talk /contributions)05:04, 8 December 2025 (UTC)[reply]

    Proposal: Indefinite block + standard offer for HEB

    [edit]
    This is a bit of a complicated discussion to determine consensus. I have taken it in two parts.
    First, there is very clear consensus that the community desires an indefinite sanction. Some opposition to additional sanctions developed as the discussion went on, although even a few of the comments labelled "oppose" are endorsements of lesser indefinite sanctions such as a topic ban. The comments stating opposition to additional sanctions, and very few opposed to thecurrent block, were significantly in the minority.
    Next, there is the question ofwhich sanction the community desires. There was early discussion about our confusing approach to "indefinite blocks placed by the community", and I appreciate that many commenters wrote out exactly what they intended to support with respect to Thryduulf'sfriendly amendment. There are a number of comments supporting a plain community ban, as well as several supporting the indefinite block proposal as second choice to a community ban. They are contrasted with several comments supporting either the original indefinite block proposal or a ban with Thryduulf's conditions, which are functionally the same. The straight count of bolded comments between these two groups is very nearly equal.
    Overall, I find that there is consensus for the original indefinite block proposal, and insufficient support to convert to a straight community ban. Therefore, by consensus of the community,Horse Eye's Back is indefinitely blocked, and may appeal via the usual process and per the conditions of thestandard offer.
    --Ivanvector (Talk/Edits)20:30, 12 December 2025 (UTC)Note: An editor has expressed a concern thatIvanvector (talkcontribs) has beencanvassed to this discussion. (diff)[reply]

    The following discussion is closed.Please do not modify it. No further edits should be made to this discussion.


    There is clear consensus that HEB has acted in an uncivil manner, crossing a line that the prior "final warning" meant to be inviolable. There seems to also be early consensus that a significant block or ban is the appropriate response. The last AN/I discussion dangled and dawdled and moldered, but the one true takeaway was: "final." I do think that a CBAN is a tiny bit too much, though. Six months (+) is a good chunk of time to make adjustments, and make changes; the standard offer's requirements ofclearly understanding the problems, and clearly guaranteeing not to compound those problems in the future means that failure to communicate is failure to be unblocked...which also seems to be consensus, or close to it, so far. I think anything less makes a travesty of all the effort put forth in the most recent AN/I decision.Hiobazard (talk/contribs)22:23, 8 December 2025 (UTC)[reply]

    Support - I was about to comment suggesting a CBAN. Not being involved in the August discussion but having seen it at the time, the fact is afinal warning has to be exactly that. If there had been at least a year between that and another good-grounds filing then I'd argue that it's enough time to have another issue without a block, but the fact is it's been less than four months. This is exactly thechronic behaviour that ANI should be blocking over.Rambling Rambler (talk)22:26, 8 December 2025 (UTC)[reply]
    Support - I guess I should formalize this as proposer. I would also support a CBAN if that is preferred, but somewhat reluctantly.— Precedingunsigned comment added byHiobazard (talkcontribs)22:31, 8 December 2025 (UTC)[reply]
    An indefinite block placed by community consensusis aCBAN, even if you say it isn't.Editors who are indefinitely blocked by community consensus, or remain indefinitely blocked after due consideration by the community, are considered "banned by the Wikipedia community".Toadspike[Talk]22:37, 8 December 2025 (UTC)[reply]
    That is a subtle difference (to me) that I, of course, overlooked. I guess if the community decides, administrator discretion no longer applies. My goal would be a 6-month hiatus, with a 'standard offer' way out if proper behavior is promised and lived-up-to. Does anyone have a suggestion that would fit with that, or are we looking at a CBAN as the only realistic option?Hiobazard (talk/contribs)23:36, 8 December 2025 (UTC)[reply]
    If there is an explicit consensus at the time of the block that a single admin may unblock when certain conditions are met, then, if those conditions are met, a single admin may unblock. In this case the proposed conditions are those listed atWikipedia:Standard offer, explicitly includingclearly understanding the problems, and clearly guaranteeing not to compound those problems in the future and the understanding thatfailure to communicate is failure to be unblocked. The block would technically be a cban, but it would be a cban that can, by explicit consensus, be overturned by a single administrator.Thryduulf (talk)00:02, 9 December 2025 (UTC)[reply]
    • Support indef, wth conditions as detailed by Thryduulf. As I mentioned above, HEB has become a community time sink. Editors who become time sinks for the community are, no matter how much good faith their contributions are made with,not compatible with a collaborative project. -The BushrangerOne ping only00:05, 9 December 2025 (UTC)[reply]
    • Support as second choice to an outright ban. As proposed, this would work as Thryduulf has described, and I realize that this is what Hiobazard initially intended, but I disagree with it. I'll support this, as better than nothing, but I would prefer the more rigorous kind of consensus needed to appeal a community site ban, instead of what could be a single admin's decision. --Tryptofish (talk)00:30, 9 December 2025 (UTC)[reply]
    • Support as second choice to CBAN. HEB habitually wastes the community’s time, they have been warned and chosen not to heed that warning.~2025-39355-07 (talk) 00:49, 9 December 2025 (UTC)This editor appears to have made 1 (one) contribution to en.wp. (This one.) -- SashiRolls 🌿 · 🍥02:19, 9 December 2025 (UTC)[reply]
      @SashiRolls: you have no way to know that. I expect the truth is quite the opposite since a new editor is unlikely to know about ANI.~2025-39621-83 (talk)18:02, 9 December 2025 (UTC)[reply]
      And there was me thinking that we had a dress code discouraging the wearing ofloud socks to flash mob actions with weighty consequences. You should both feel free to log in to your accounts. -- SashiRolls 🌿 · 🍥19:39, 9 December 2025 (UTC)[reply]
      @SashiRolls these areWP:Temporary accounts. Edit counts reflect contributions only from the current browser on the current device and begin from the most recent of 30 days ago or the last time cookies were cleared (which, especially on shared machines, can be every time the browser is closed and/or the user logs out).Thryduulf (talk)22:44, 9 December 2025 (UTC)[reply]
    • Support indef I reported only on the road and highway related content as it was the only time they crossed my path, and I felt bringing up anything else would cause the discussion to lose focus. I'm glad to see that wasn't the case here and that there is a degree of consensus. I think the fact that their problematic edits extend beyond roads and highways is enough to warrant a total block and not just a topic ban.Ten Pound Hammer(What did I screw up now?)03:35, 9 December 2025 (UTC)[reply]
    • Support indef The number of times I check ANI for an issue not related to HEB and then find a post about HEB is alarmingly high.Qiushufang (talk)04:18, 9 December 2025 (UTC)[reply]
    • Support. Per Thryduulf, this technically is still a CBAN, just a CBAN that optionally delegates the unban conditions—essentially inverse discretionary sanctions. I'm not sure I see that special-casing as necessary here, but I also don't see it as likely to cause much harm, so, support with or without. --Tamzin[cetacean needed](they|xe|🤷)14:24, 9 December 2025 (UTC)[reply]
    • Support CBAN. I'm not involved in this particular dispute, nor the previous, but I've had opinions in both in case that makes me involved. I'm otherwise not seeing the need for tailored conditions, this looks like a straightforward case that can follow the usual proceedings. We don't need to be adding any potential leverage for former unblockables here, nor do I think a CBAN is too much. I haven't read why it would be overkill, only why it'd be unclear to oppose. Feel free to enlighten me if I missed something.CNC (talk)15:04, 9 December 2025 (UTC)[reply]
    • Support CBAN with Thryduulf's conditions. Hopefully a long break can allow them to reflect in the behavior. We have wasted so much time giving HEB so many chances, and as it's been the community's time wasted it should be the community who determines if they are allowed back.
    LakesideMinersCome Talk To Me!18:13, 9 December 2025 (UTC)[reply]
    Oppose HEB is a voice of reason in a sea of religionists. People are sad because bad.~2025-39334-84 (talk) 06:57, 10 December 2025 (UTC)Strikingproxy vote.Toadspike[Talk]09:19, 11 December 2025 (UTC)[reply]
    • Support If you are an ANI lurker forat least six months you'll see that they've been brought to the 'boards before. And if you simply trawl the archives, you can easily see several incidents that HEB has engaged in. HEB is simply a combinedWP:UNBLOCKABLES and a professional tight-rope walker, incivil but barely not enough to indef for. Also the last sentence above oppose vote seems to be a personal attack? Idk. ~212.70~~2025-31733-18 (talk)13:29, 10 December 2025 (UTC)[reply]
    Support CBAN HEB has been here back in either June or July, and I agree with the temporary account above me, HEB is seriously a issue here, betweenWP:UNBLOCKABLES and the TA's comparison to a tightrope, I agree with all of the supports above me.shane(talk to me if you want!)13:35, 10 December 2025 (UTC)[reply]
    • Oppose as written. HEB is currently blocked for thirty days, so at the very least, they should be given the opportunity to formulate a reasonable and rational unblock request that addresses the issues raised, andif they are unblocked, then what, we indef them anyway — sorry for your bad luck mate — looks like coal for you this Christmas. This proposal includes the "standard offer", shouldn't they be afforded that same offer with the thirty day block.—Isaidnoway(talk)17:00, 10 December 2025 (UTC)[reply]
      Given the filibustering on their talk page, which includes even moreWP:IDHT than before ("what did I do wrong? Please list it out for me" --(Personal attack removed), I already did that in this very ANI and on your talk page! Multiple times!) I don't think they're capable of forming an unblock request. I honestly think they should have talk page rights revoked, too.Ten Pound Hammer(What did I screw up now?)17:04, 10 December 2025 (UTC)[reply]
      HEB was blocked by a single admin based on the evidence brought into this discussion. This discussion is essentially determining whether that block should have been longer in the first place.Ed [talk] [OMT]17:47, 10 December 2025 (UTC)[reply]
    • Support CBAN Per TA, He's an issue.
    Tankishguy17:25, 10 December 2025 (UTC)[reply]
    • Support community ban per my comments above as well as comments I've made in previous ANIs. As I've said, I don't have much faith that HEB is capable of channeling their energy into more collegial editing. That's why my preference is for a community ban, where any appeals would be held on WP:AN for our discussion. The indef block+standard offer proposed in the OP is a distant second for me.Ed [talk] [OMT]17:47, 10 December 2025 (UTC)[reply]
    • Oppose CBAN, overturn block -- Let's go through the evidence:
      • The first discussion linked in the OP isTalk:U.S. Route 131/Archive 1#Exit list 2. I don't see any problem with HEB's conduct there. There is no incivility, bludgeoning, etc., and to boot, they're right on the content dispute IMO.
      • The thread right above that isTalk:U.S. Route 131/Archive 1#Primary source overuse, wherein LilianaUwU saysYou're just pissed that road editors dared fight back against your disruptive drive-by tagging. Now, let me guess, you're gonna go tag Québec now that I've raised a stink like you did with the other editors' respective states? TPH writes in the OP that this iswhere @LilianaUwU: called out HEB for drive-by tagging;. So to be clear, this isnot incivility, this is "calling out," and it's OK, but HEB's responses were uncivil? I "call out" BS on that accusation.
      • Next isTalk:Interstate 275 (Michigan)/Archive 1#Primary sources. This is where Ten Pound Hammer starts the thread withHorse Eye's Back (talk · contribs) has been slathering Michigan road articles... So it's TPH who is being uncivil and personalizing the debate, not HEB? I don't think so. It's TPH who is being unreasonable in that discussion.
      • User talk:Horse Eye's Back#Primary sources, where TPH says in the OP here that they "politely asked them to stop". "Politely" means writingit seems you are desperately trying to WP:BLUDGEON a position. I don't think that's polite. I don't see any problem with HEB's comments in this discussion, either.
      • User talk:Horse Eye's Back/Archives/2025/July#Michigan Highways -- no incivility, no bludgeoning, no problems whatsoever here.
      • Talk:M-65 (Michigan highway)#Primary source overuse -- in this one, TPH doesn't even respond to HEB's two comments. Again, no incivility, no bludgeoning, trying to discuss the content dispute but TPH doesn't respond. The problem here isn't HEB, it's TPH.
      • Talk:F-41 (Michigan county highway)#Primary and notability -- no incivility, no bludgeoning, no problems here, either.
      • Then there is the RSN thread,Wikipedia:Reliable sources/Noticeboard#Are department of transportation maps primary sources about roads?, which HEB started specifically in response to TPH's request for a centralized discussion. I don't see any incivility from HEB here, maybe I missed something. Slight bit of bludgeoning--I count 30 comments from HEB, the next-most-frequent is 18 comments from TPH--but making 12 more comments than the next guy isn't ANI-worthy IMO, and you'd expect the editor who opens a discussion to frequently comment in that discussion. Also, a lot of these are replies to replies.
      • The ed17 points toUser talk:Horse Eye's Back/Archives/2025/July#Michigan Highways, but like buidhe above, I don't see any problems from HEB here. Buidhe asked Ed for clarification but he hasn't responded, although he has voted to support the CBAN.
      • Given the above, I don't understand why Star blocked HEB, and I think Star's refusal to specifically identify examples of incivility atUser talk:Horse Eye's Back#December 2025 is anWP:ADMINACCT failure.
      • The last ANI,Wikipedia:Administrators' noticeboard/IncidentArchive1198#Propose yellow card for HEB, contrary to the close, wasnot for a "final" warning. "Final" wasn't in the proposal, and it wasn't in the vast majority of the support votes. It was "just" a warning. The word "final" was something the closer added. HEB objected to the "final" atUser talk:Horse Eye's Back/Archives/2025/September#ANI Discussion, where they pointed out that the "final" will be used against him in the future, and lo and behold, in the second sentence of this OP mentions "final warning"...
      • At the last ANI, I complained that the CBAN proposal was made by an IP. This time it's an editor with less than 600 edits. Among those 600 edits are 4 CBAN votes (1,2,3,4, the 4th being for an indef of HEB at the last ANI), plus some other sanction votes. Totally kosher...
      • A lot of the comments here are blatant "I've never liked this editor"-type comments. I don't understand why this community condones such things.
      • I also don't agree with going from formal warning to CBAN with nothing in between. Not even trying to let the month-long block expire and seeing if there is improvement.
      • Overall, I see HEB doing the right thing, which is making bold edits, tagging articles that don't comply with policies and guidelines, and then trying to engage in discussion about them. This looks to me like "he disagrees with us in a content dispute, CBAN him!". I don't see any policy violations here at all. Maybe there is something in here that I've missed, but I see no problematic behavior by HEB in the discussions listed above.Levivich (talk)19:03, 10 December 2025 (UTC)[reply]
        • Going through your argument point-by-point, most of the points you make, before coming to the previous ANI discussion, are arguments that HEB is actually correct about the maps/roads issue. Reading that, I immediately flashed back to the ArbCom case in which you argued that "being rightis enough". Also, a lot of what you argue is that TPH was worse, which is a straight-upWP:2WRONGS ploy. Then you come to the warning coming out of the previous ANI thread. You didn't like the consensus there, but that doesn't get you to argue that we should treat it as if it was something less than what it was. --Tryptofish (talk)00:31, 11 December 2025 (UTC)[reply]
    • Support CBAN, per TenPoundHammer and others.BeanieFan11 (talk)19:27, 10 December 2025 (UTC)[reply]
    • Oppose further sanctions while HEB is blocked. I felt uncomfortable about the speed with which this took off, and became more so when I noticed the OP had so few contributions (after they thanked me for my comments above). I've looked through HEB's contributions a bit tonight and haven't found anything banworthy, generally finding them to be quite reasonable. I did notice that they'd made over 1000 edits to ANI, which to me is just crazy: this is a surefire way to make enemies fast if you're not a paragon of diplomacy. I agree with those above (Levivich and Isaidnoway in particular ... or even Cullen328 in the previous section) who have suggested taking things one step at a time. If HEB returns, I will leave them a message suggesting they self-impose an ANI ban. I may be wrong about HEB (Tamzin, in particular, makes me wonder), but I don't think this sort of mad rush to delete a user marked for deletion is healthy at all. A warning and a single block (that I still haven't seen justified) in five years. Before that, 2 short blocks with their previous account. As for the current block, if it's unjust it should be lifted (for the record), but taking a one-month break from ANI and en.wp is never a bad idea. The comment Levivich highlights from LilianaUwU above, and the use that is being made of it here, is troubling. -- SashiRolls 🌿 · 🍥20:18, 10 December 2025 (UTC)[reply]
    • Oppose further sanctions per @User:SashiRolls. I think we are too quick to ban active editors.GeogSage (⚔Chat?⚔)20:34, 10 December 2025 (UTC)[reply]
    • Oppose CBAN from what I've seen, it doesn't seem to be merited at this time. (t ·c)buIdhe21:05, 10 December 2025 (UTC)[reply]
    • Support CBAN. I've actually agreed with HEB's substantive points on multiple occasions, and have found their persistence beneficial in a few instances of (what I perceived as) POV-pushing by their interlocutors in various other topics over years of editing. But upon reflection, I think thatWP:OWB#3 captures the essence of the overall problem here:One who sometimes makes good edits, but endlessly bickers, threatens, insults, whines, and is eventually banned, will have taken hundreds of hours from other users who would have better spent that time building the encyclopedia. I've seen too many editors over the years write comments like "I stopped editing in this area because of HEB". It's true that HEB aims at some deserving targets sometimes. But HEB needs to find a way to participate that doesn't involve exhausting other editors with demands to satisfy whatever impulses burn in HEB's heart at that moment. They can start with a convincing unban appeal down the line, one in which they make their own lists of what they could have done differently and better, without demanding that other editors do that work for them. I hope they succeed.Indignant Flamingo (talk)21:19, 10 December 2025 (UTC)[reply]
    • Oppose further sanctions at this point. I don't often agree with Levivich, but I think they have summarised the situation well here.Black Kite (talk)21:25, 10 December 2025 (UTC)[reply]
    • Support:LilianaUwU sums it up: We've been here before, we'll be here again. HEB has a consistent record of bludgeoning and wikilawyering, masquerading as faux-civility, over the years; the fillibuster raised in their favor is unconvincing since precisely the same attitude is being displayed on their talk as was under discussionbefore when this thread was opened. Not listening to, not hearing, not respecting the community's views. It seems difficult to argue that the current block isn't preventative when if they weren't blocked, precisely the same bludgeoning/wikilawyering would be convolutingthis discussion rather than that on their talk. The SO would be useful for both them and the project.Fortuna,imperatrix21:57, 10 December 2025 (UTC)[reply]
    • Oppose further sanctions per Levivich and SashiRolls. The worst thing I can say about HEB here (at least based on the evidence) is that he chose a weird hill to die on WRT maps as primary sources, and can verge on BLUDGEONing at times. But he at least grounds them in policy and does not resort to personal attacks. As for the ANI issue, I've no objections to a self-imposed ANI ban, should he decide to do this.MiasmaEternal21:50, 10 December 2025 (UTC)[reply]
    • Support CBAN: per the evidence presented and previous interactions with HEB, it is clear that they are an immense drain on volunteer time and resources and do not wish to contribute in a constructive and collaborative manner. I see now issue with some of their concerns about sourcing and notability, but indiscriminately tagging articles in targeted batches—a tactic designed to overwhelm users and bully them into submission—is unacceptable. The community needs to draw a clear line in the sand unless we want to bleed away more experienced and motivated contributors.SounderBruce23:20, 10 December 2025 (UTC)[reply]
    • Support existing block,Oppose CBAN, largely per my rationale during the August discussion where I proposed the warning that was adopted. I had also supported a one-month block at the time. Levivich is correct as far as my own intentions are concerned; I considered the "yellow card" a formal warning, not a final one. I did expect that we'd be back here, because HEB can't help himself. As I'm fairly sure I've said about HEB, and certainly about other editors,being right is not enough.Mackensen(talk)23:31, 10 December 2025 (UTC)[reply]
    • Support ban with the conditions described above. I've thought long and hard about this, but what has tipped me over the balance is a combination of two things:
      • The last time they were brought to AI the warning they got was explicitly final and that seems to have been understood by those supporting. I strongly believe that a final warning should indeed mean final, every time. Multiple "final" warnings is one of the ways to end up with an unblockable.
      • HEB's conduct on his talk page during this ban. They have chosen not to engage productively but to continue much of the same behaviour that resulted in the block in the first place. When you have been blocked and your net contribution to the encyclopaedia is being examined at ANI, that is the time to be on your absolute best behaviour. If this is an example of HEB's best behaviour then they are not a good fit for a collaborative online encyclopaedia, if this isnot their best behaviour then what on earth do we need to do before we see that, and why should we have to put in that much effort and energy to get it when other editors who make at least equally valuable contributions to the project don't require that of us?Thryduulf (talk)23:51, 10 December 2025 (UTC)[reply]
    • Comment the one-month block obviously has to stand. The problem is tendentious behavior in response to feedback; Levivich's link to HEB arguing that a "yellow card" is only a formal warning and not a final warning is a perfect example of the problematic behavior. That behavior has continued, in the diffs and in the response to this ANI thread on his talk page.
      As far as this being a "CBAN" versus an indef block versus just the one-month block ... the behavior does not seem egregious enough to justify a permanent ban. The intent of the CBAN here seems to be "require a statement rather than just letting him wait out a block". I don't think demands for a properly-formatted apology in six months are helpful; my vote would be for a 1-3 month block. I have no idea if a TBAN from "roads" would help going forward.~2025-35132-06 (talk)04:45, 11 December 2025 (UTC)[reply]
    • Oppose: When HEB was brought here last time and given a final warning, that warning was for incivility. Per Levivich's analysis I don't see any of that.TarnishedPathtalk04:55, 11 December 2025 (UTC)[reply]
      Perthe close, it was not just for incivility but alsouncollegial behaviour, noting thatfurther instances of subpar conduct on their part should lead to escalating blocks. In reality the bar was set quite low for a block hence that has already happened. But what baffles me is that at no point does it seem HEB considers "maybe I shouldn't do this since it'll likely piss people off and I'm on a final warning and all that, even though I'm certain I'm right", instead they either appear a) determined to test the limit of what they can and can't get way with, or b) lack the self-awareness required when working collaboratively with others. The present issue is thatthey remain convinced that they are right, and thus theyshouldn't be blocked for being so abundantly correct, very much echoing thefinal warning nonsensical discussion from before. Practising that mentality is inherently disruptive to the project and other editors if not obvious, regardless of if they have reigned in some incivility in the process. For example a user makes a bunch of controversial bold move and were given a final warning about it, you'd expect them to actually think twice before making a bold move incase it'd be controversial to do so right? Ie have some self-awareness, given it's compulsory here. If editors are unable to gain that quality after several years, and numerous editors trying to get through to them, I honestly don't know how else we are supposed to cope with such disruption. Hence the point of a CBAN is thus far from punitive, it's specifically trying to solve this inherent problem by requiring an understanding, one that others are convinced of rather than any single admin, before returning to editing. The alternative is expecting an understanding to magically appear in the near future, as this has been tried before with the warning that didn't function as intended.CNC (talk)15:42, 11 December 2025 (UTC)[reply]
    • Support acommunity ban after reading HEB's talk page and seeing how they have justcontinued digging. They were given a formal warning that was agreed to be a final warning. Then they were blocked for a month, and have continued in a way that would often result in pulling talk page access. They had a post-final warning in the form of the month block. Enough is enough.Robert McClenon (talk)09:11, 11 December 2025 (UTC)[reply]
      On that TP, Cullen mentions HEB's blocks as HEJack without being aware that it was for interaction withthis policy-violating sockpuppet. I think it was important for HEBack to make it clear that both of their previous blocks were explicitly related to this "faux nez". There are some who say "one must turn the other cheek" when being baited by sockpuppet (as Cullen does say when HEB pointed out the context, presumably based on theessay abouttwo wrongs not making a wright). The requirement of such saintly behaviour towards aggressive sockpuppeteers is, in practice, primarily applied to "blockables" in my experience. Users with coffers full of social capital (i.e. the unblockables) tend to be offered a lot more leeway... -- SashiRolls 🌿 · 🍥14:43, 11 December 2025 (UTC)[reply]
      I mentioned a previous block only because Horse Eye's Back incorrectly claimed that they had never been blocked. Otherwise I would not have brought it up. There is no expectation of "saintly behaviour" from anyone, but everyone knows or ought to know that misconduct by another editor does not justify misconduct by the editor under discussion here. As for "social capital", that comes from collaborative, productive contributions to the project, including refraining from constant bickering.Cullen328 (talk)19:51, 11 December 2025 (UTC)[reply]
    • Support when is enough enough?EF514:54, 11 December 2025 (UTC)[reply]
    • Comment This thread is a prime example of the tight-rope walking that can be seen above. At least three people think more sanctions would be too excessive. Where's the line? This kind of behavior is what even some users were indeffed/banned for. HEB seems to be an exception. HEB however is not irreplaceable.— Precedingunsigned comment added by~2025-31733-18 (talk)16:51, 11 December 2025 (UTC)[reply]
    • Support - agree with TA above. A younger accountwould get blocked for this. I don't blame any admins for not blocking them earlier, but it needs to be done.WP:SEALION,WP:IDONTGETIT.win8x (talk)16:59, 11 December 2025 (UTC)[reply]
    • Oppose I'm not familiar with HEB's history but his behaviour in this incident doesn't seem worthy of an indefinite block to me. He already has a month long block, I'd much rather give an editor a chance to improve following a long block as opposed to making the ban a community ban.Traumnovelle (talk)18:46, 12 December 2025 (UTC)[reply]
    • Further comment: win8x is correct that HEB is engaging insealioning. The whole thing is a mess. Just look at this part:

    The better question is whether the use is excessive given the subject matter, and whether the tag actually helps facilitate improvement of the article. GMG 18:41, 4 December 2025 (UTC)

    ~24 of the ~30 citations in the article are to the Michigan Department of Transportation. I've seen excessive defined two ways... Either the majority of sources being primary or the majority of content being sourced to a primary source (both have support in P+G and are the same answer much of the time anyways), this would seem to fall under both majority of sources and majority of content. If tags don't facilitate improvement of articles they shouldn't exist, this is a tag for just this situation and it has community endorsement. Horse Eye's Back (talk) 19:55, 4 December 2025 (UTC)
    If tags don't facilitate improvement of articles they shouldn't exist, this is a tag for just this situation and it has community endorsement. That's not responsive to the question asked. A tag can be useful in one context and not useful in another. The latter case doesn't invalidate the tag altogether, just the as-applied use case. WP:PRIMARY isn't a blanket ban on primary sources. The policy section enumerates seven different criteria for evaluating when to use primary sources. It's not clear which of these you think are relevant to this article. Point 3 would seem to be directly relevant: A primary source may be used on Wikipedia only to make straightforward, descriptive statements of facts that can be verified by any educated person with access to the primary source but without further, specialized knowledge.. Point 5 is also relevant: Do not base an entire article on primary sources, and be cautious about basing large passages on them. If DOT sources are primary then that's in play. Is caution warranted? What's the actual concern? Mackensen (talk) 21:14, 4 December 2025 (UTC)
    I find such tags useful because they let me know about an issue without having to analyse dozens or hundreds of sources. I'm not aware of any negative impact that such a tag could have, what am I supposed to be weighing the beneficial impact of a valid tag against if there is no harm? So far the only argument made against the tags is that they are inaccurate because DOT maps aren't primary sources... Hence this discussion, its a bit of a chicken and egg issue after all... Horse Eye's Back (talk) 21:27, 4 December 2025 (UTC)
    Tags are placed because a problem has been identified and needs to be addressed. They also serve as a warning to readers that the article may have issues. As discussed, relying on primary sources is not, by itself, a problem. Whether the DOT sources are primary or not is something of a side issue, because even assuming that they are you haven't indicated what the actual problem is, or the expected beneficial impact. Mackensen (talk) 22:06, 4 December 2025 (UTC)

    And there are probably a bunch of other examples... Also, this section has anWP:ILIKEIT argument (even thoughWP:ILIKEIT is technically XfD stuff this still applies in spirit) ofI find such tags useful because they let me know about an issue without having to analyse dozens or hundreds of sources.~2025-31733-18 (talk)20:26, 12 December 2025 (UTC)[reply]

    The discussion above is closed.Please do not modify it. No further edits should be made to this discussion.

    Close review: Horse Eye's Back

    [edit]

    Horse Eye's Back has complained ([1]) that I aminvolved owing to acomment I made in aWP:RSN discussion that they started, which is related to the highway article citation issue which kicked off the complaint here. I am therefore requesting a review of the close above.Ivanvector (Talk/Edits)23:26, 12 December 2025 (UTC)[reply]

    It's worth noting that HEB did not request a close review, only Ivanvector seems to want one. Yes, there is some degree of involvement (especially given the tone of your comments in the cited thread). No, you did not particularly faithfully describe the opposers argument about jumping straight from a warning to the nuclear option bypassing escalating blocks. Finally, no, it's unlikely any other admin would have closed it differently at the time you closed it. I would not endorse opening this review as it's just going to lead IMO to more unnecessary heat / bad blood without any possibility of changing anything. :) -- SashiRolls 🌿 · 🍥23:59, 12 December 2025 (UTC)[reply]
    To be fair, Ivanvector had no choice but to request a review. No comment on the rest.M.Bitton (talk)00:03, 13 December 2025 (UTC)[reply]
    • Involved endorse Speaking as someoneactually involved, having !voted above, if Iwasn't involved, I would likely have closed it in exactly the same way Ivanvector did, and I suspect any other reasonable adminstrator would have done the same. In addition I'd argue that claiming that that RSN comment makes Ivanvector 'involved' in this discussion isexactly the sort of behavior from HEB that led to this sanction being imposed in the first place. -The BushrangerOne ping only00:05, 13 December 2025 (UTC)[reply]
    • Endorse close - WP:INVOLVED is typically for admins who have previously issued sanctions or who have been involved in protracted disagreements, so it doesn't apply here. Additionally, after having a cursory look at the discussion, I don't see any fatal flaws and it appears to be a reasonable summary and within admin discretion. It doesn't matter if another closer would have worded it differently, only that the close was reasonable and within norms.Dennis Brown -00:10, 13 December 2025 (UTC)[reply]
    • Endorse, with the caveat thatI am very much on a "side" in the discussion that was closed. I've looked at the RSN discussion, and there is nothing that I can detect that would make Ivan a "partisan" with a dog in the fight there. It's just a comment from someone contributing to a content noticeboard. I agree with Dennis that the close was reasonable, and I see nothing wrong with how Ivan handled the discussion at HEB's talk page. --Tryptofish (talk)00:53, 13 December 2025 (UTC)[reply]
    • Involved endorse as admin who applied the one-month block. Nothing that followed my block indicated the disruption wouldn't resume when the block ended because HEB does not understand or believe their actions are problematic. The community feels otherwise, and Ivan's close reflects that. I think the decision to have it explicitlynot be a CBAn was a good one.StarMississippi02:33, 13 December 2025 (UTC)[reply]
    • Involved endorse as the administrator who recommended a one month block. I refrained from speaking for or against stronger sanctions but the community discussed the matter and has spoken. Ivanvector has done a very good job of analyzing and summarizing the discussion and its consensus.Cullen328 (talk)07:08, 13 December 2025 (UTC)[reply]
    • Endorse I did not vote this time around, but I'm the person who last brought HEB to ANI. It's going to be tough to find an editor who has never interacted with HEB, with how vast their contributions seem to be. There is clearly a consensus to block HEB, and the close is not inappropriate IMO.jolielover♥talk07:37, 13 December 2025 (UTC)[reply]

    *Endorse there was over 2:1 support for a ban, and the thread was opened for 5 days already.Traumnovelle (talk) 07:54, 13 December 2025 (UTC) Withdrawing in light of other persuasive arguments.Traumnovelle (talk)03:04, 16 December 2025 (UTC)[reply]

    • Uninvolved endorse more wikilawyering from a guy who likes to wikilawyer. No surprise there, and no surprise that there's nothing of substance behind it.~~ AirshipJungleman29 (talk)13:04, 13 December 2025 (UTC)[reply]
    • Oppose close. I'm utterly uninvolved: I did not comment in the previous discussions about HEB's behaviour and I'm not involved in the underlying content disputes about maintenance tags/highway articles. Besides, HEB previously supported a topic ban against me[2], so they are certainly not my best pal. That said, I'd like to point out the following.
      1. Ivanvector was indeed involved in a content dispute with HEB, which makes a close review appropriate in principle.
      2. Their close is detailed and well-reasoned, yet they rightly acknowledge thatThis is a bit of a complicated discussion to determine consensus. Roughly one third of the comments (10 out of 30, by my count) expressed opposition to additional sanctions, which is a significant minority.
      3. Two thirds supported either a CBAN or an indef block + SO. However, Ten Pound Hammer's initial proposal of a topic ban on maintenance tags and highway articles was not discussed in depth. If I'm not mistaken, only three editors explicitly rejected it, while one or two endorsed it. While the previous ANI thread focused on civility, here I mainly see issues with bludgeoning and POV-pushing: it's not at all clear that HEB's behaviour with respect to civility has not improved, or that a topic ban would not suffice to prevent disruption. At least, I don't see a clear consensus in the discussion that excludes this.
      4. HEB is a productive and experienced editor, and blocking them from the whole site should be a last-resort remedy: one to be adopted only when it's clear that nothing else will work.
        So I think we should reopen the discussion to see if editors can reach a consensus on an intermediate course (tban, possibly also a civility restriction?), or if the community will instead confirm/strengthen its support for harsher measures.Gitz (talk) (contribs)14:52, 13 December 2025 (UTC)[reply]
    • Endorse closure, I feel there is no conflict of interest here perWP:INVOLVED, and the community consensus was clear on what to be done with HEB. To claim that Ivanvector was "involved" because of one stray comment is absurd.Ten Pound Hammer(What did I screw up now?)14:56, 13 December 2025 (UTC)[reply]
    • Comment: I won't make a bolded opinion here; as proposer, that seems inappropriate. I am pleased, however, that this process seemed to go as well as could possibly be expected. Many very experienced editors worked very hard to make sure this thread was open, fair, and civil. In fact, the graceful way in which this proceeded was, to me, a helpful counterpoint to the unfortunate behavior which we have been addressing.Hiobazard (talk/contribs)16:43, 13 December 2025 (UTC)[reply]
    • Endorse close (involved). Commenting editorially does not make one involved; it was a comment on sourcing, not a contributor. If IV had advocated against HEB personally in the discussion, it might be different. They didn't, and it isn't. It was also not the "dispute" that WP:INVOLVED is predicated on; that's important. As such, the caveat within WP:INVOLVED applies—thatany reasonable administrator would have probably come to the same conclusion—as it is realistically impossible to read the consensus above (pace Gitz's "sizable minority") to any other conclusion than that IV came to.Fortuna,imperatrix18:32, 13 December 2025 (UTC)[reply]
    • Abstain - (neither endorse nor disendorse) - (not involved whatsoever). There's a clear majority of opinion in this discussion that considers HEB disruptive. I'm less of the view that there's a clear weight of evidence substantiating *all* the accusations levelled warranting the doubling down of sanction (from a one month ban to an indefinite block). A very detailed rebuttal of the evidence was presented and 49 hours later the discussion was closed. There was no significant, elaborated counter to that presented. I accept that there is a context here where ensuring a long drawn out process does not occur - but the substantial shift in views expressed once the rebuttal was presented is stark and another 24-48 hours might well have allowed further response to that rebuttal. Given HEB was already under a one month ban, I can see not unreasonable grounds for a claim that it was a hasty closure. Regards, --Goldsztajn (talk)23:36, 13 December 2025 (UTC)[reply]
    • Involved endorse as the anonymous IP who proposed the indefinite block in August. I abstained from !voting this go around since my previous proposal derailed the conversation due to coming from someone without an account and that may have contributed to HEB not being blocked then.~2025-40588-39 (talk)23:37, 13 December 2025 (UTC)[reply]
    • Involved dyspepsia. Since two editors are now complaining that my response to the so-called "very detailed rebuttal" was insufficiently "significant" or "elaborated", I figure I'm entitled to bite back. There's a lot in this entire ANI discussion that demonstrates all the ways that ANI is toxic. We have a clear consensus, although it was not unanimous. It's also clear to anyone who wants to be reasonable that the close was procedurally correct, even if the result does not enjoy unanimous support. Apparently, some editors would like this discussion to go on even longer, because, hey, you never know if something new thrown at the wall will stick. For those who consider the discussion here too quick, brief, and superficial, let me suggest that they open a case at ArbCom. But please let's let the rest of us move on. --Tryptofish (talk)00:52, 14 December 2025 (UTC)[reply]
    Polemic content not related to independent review of close.Dennis Brown -
    This comment of yours illustrates why the above discussion is a broken process. We can't expect of any closer to discard poorly-reasoned comments like yours and only consider well-reasoned comments, can we?AwerDiWeGo (talk)01:04, 14 December 2025 (UTC)[reply]
    Well, golly gee whiz, and I thoughtyour comments were the poorly-reasoned ones. --Tryptofish (talk)01:09, 14 December 2025 (UTC)[reply]
    I didn't even make any attempt at a reasoned comment. I deliberately avoided to include any reasoning in my comment. So my comment was neither well reasoned nor poorly reasoned; I just stated what I think without elaborating or attempting to reason. It's not worth it to try to reason here. Anyhow, you again just illustrated why this is a broken process; I'm hesitating at labeling this as mob rule because I'm not even sure what "mob rule" means in English.AwerDiWeGo (talk)01:20, 14 December 2025 (UTC)[reply]
    @AwerDiWeGo @Tryptofish you've both made your points. Can any further back and forth move elsewhere so as not to derail the thread? Thanks!StarMississippi01:22, 14 December 2025 (UTC)[reply]
    • Involved overturn and let someone else close it. Someone involved (if only one comment) in the underlying issue brought to this noticeboard shouldn't be deciding consensus on a questionable indef block proposal. And in my view, I don't see HEB's question about being involved as a complaint, but rather an inquiry.—Isaidnoway(talk)15:43, 14 December 2025 (UTC)[reply]
    • Endorse. HEB's misbehavior and our reliable sourcing policy are not the same issue. Conflating such remote matters would only make enforcing our policies more difficult.Compassionate727 (T·C)17:23, 14 December 2025 (UTC)[reply]
    • Uninvolved Overturn - Levivich's analysis raises some serious questions about the accusations as well as the conduct of other editors. I think this new development deserves more time to discuss, and I think we also need to look at the bigger picture. This looks like it might be a case of editors in a certain topic area enforcing their own standards as if they are policy and accusing anyone who disagrees of incivility while being uncivil themselves. Stumbling upon this discussion, I find it very concerning that nobody seems to be able to point out exactly what HEB has done wrong and yet HEB is being further criticized for asking for a clear explanation. –dlthewave18:15, 14 December 2025 (UTC)[reply]
      • Taking a closer look at TPH's evidence, it's clear that they're (intentionally or not) misrepresenting the evidence. A central premise of their argument is"AtWikipedia:Requests for comment/Using maps as sources, unless I am misreading this extremely long discussion, it seems there is a consensus that maps are being used appropriately as sources on highway articles and there are no concerns with original research, synthesis of ideas, or other impropriety as a source." However, they seem to be overlooking the fact that there is consensusagainst Proposal 2b,"Satellite layers (i.e. on Google Maps) can be used to reference statements about elements such as ground cover that can easily be verified", and nothing in that RfC says that there areno concerns about OR or SYNTH. Their two prime examples,Interstate 275 (Michigan) andU.S. Route 131 both have extensive route descriptions that seem to be largely based on Google Maps satellite imagery. Examples include"In the city of Romulus, I-275 begins to take on a more suburban character when it passes the southwestern boundary of the Detroit Metropolitan Wayne County Airport" (How would one even quantify that?);"North of this area US 131 crosses the Kalamazoo River and runs past the US 131 Raceway Park, a dragstrip close to the M-222 interchange near Martin" (How are we deciding which landmarks are significant?);"the northbound carriageway crosses over, then back under, the southbound lanes, forcing traffic through this stretch to briefly drive on the left (Again, who decided that this short crossover stretch within an interchange on a divided highway is significant?) along with a fairly lengthy description of a discrepancy in the length of I-275 between the Federal Highway Administration, Michigan DOT and various mapping services that no secondary source seems to have seen fit to cover. None of these statements comply with the RfC and it seems entirely reasonable to tag them as overly reliant on primary sources, since maps are still primary sources and should be treated as such. These route descriptions would be considered poorly-sourced cruft that failsWP:DUE if they hadn't somehow become standard practice within this fairly isolated topic area. Additionally, FA and GA articles are not exampt from scrutiny. It seems that we have aWP:OWN issue with folks trying to shut down HEB's attempts to bring these articles into compliance with our P&Gs which understandably led to frustration on HEB's part. Sure, there can be reasonable disagreement over these points, but to characterize HEB's tagging as "bad faith" and insist that certain article sections don't need citations is beyond the pale. At the very least I think that a warning/reminder is in order for TPH. –dlthewave04:38, 15 December 2025 (UTC)[reply]
        Thumbs up icon Thank you for pointing this out. And I'd also point out that an admin had already blocked HEB for 30 days, so why the escalation to an indef just 2 days later, what was the urgency in needing to elevate this. Seems to be punitive to me, because with the 30 day block, HEB was alreadyprevented from furtherdisruptive editing.—Isaidnoway(talk)06:32, 15 December 2025 (UTC)[reply]
        This is best litigated somewhere else, not ANI.~2025-31733-18 (talk)11:51, 15 December 2025 (UTC)[reply]
        Yes, this is best decided somewhere else, but TPH decided to bring it to ANI so here we are. Since their complaint is centered on the idea that HEB's tags were incorrect and maps were used properly in all cases, it's entirely appropriate to evaluate the accuracy of those claims here. –dlthewave17:28, 15 December 2025 (UTC)[reply]
    • Overturn. And again I'll rely on another editor's comment (which is very convenient when communicating in a foreign language):I find it very concerning that nobody seems to be able to point out exactly what HEB has done wrong and yet HEB is being further criticized for asking for a clear explanation. Thank youDlthewave for making it easier for me.AwerDiWeGo (talk)19:27, 14 December 2025 (UTC)[reply]
      Section moved from above, by same user, confusing to be in two sections.Dennis Brown -
      • Comment. I agree withGoldsztajn:A very detailed rebuttal of the evidence was presented ... There was no significant, elaborated counter to that presented. It's not pleasant to venture here, so thank you Goldsztajn for making it easier for me. I'll add that the above looks like a broken process for deciding blocks or bans in a case like this one, but would prefer not to elaborate on why I think so (this place is scary).AwerDiWeGo (talk)00:08, 14 December 2025 (UTC)[reply]
        "looks like a broken process…prefer not to elaborate". Please either contribute in a way that helps further the discussion or just don't comment at all. Below you say "hesitating at labeling this as mob rule because I’m not even sure what 'mob rule' means": why even mention it at all then?~2025-40643-89 (talk)07:22, 14 December 2025 (UTC)[reply]
        I did not elaborate, but highlighted a comment by another editor that makes one of the main points. Any elaboration of an argument here is subject to others labeling it as "bickering", linking to some essay or policy about whatever just for the sake of it, or considered as further proof that whatever sanction was imposed was well imposed (like the comments in the above discussion that point to what HEB continued writing in their talk page; those comments in particular, made byTenPoundHammer andRobert McClenon and~2025-35132-06, should be discarded by the closer, in my opinion, because they look much like nothing more than hate comments).AwerDiWeGo (talk)11:40, 14 December 2025 (UTC)[reply]
    • Endorse close, as that was a fairly small involvement on Ivan's part, andeven HEB doesn't dispute the content of the close. --SarekOfVulcan (talk)22:52, 14 December 2025 (UTC)[reply]
    • Involved overturn - First, I disagree quite strongly withCommenting editorially does not make one involved. Of course it does;WP:INVOLVED is about not acting as an admin in a topic areas where you participate as an editor. So, someone who regularly edits roads articles can't act as an uninvolved admin in a roads-related sanction discussion.Ivan's RSN comment, alone, is enough to trigger WP:INVOLVED: he is taking a position in a content dispute that is the opposite of HEB's position--in a thread started by HEB. And not only does Ivan take a position, but he saysCleanup-tagging a highway article because it relies on the highway authority's publications isnonsense..., italics in the original. He called HEB's actions "nonsense." That's WP:INVOLVED.
      Of course that's not the only example! Ivan is a frequent roads editor, who createdCanada Highways Act. He also created many of the articles listed inList of Prince Edward Island provincial highways, likePrince Edward Island Route 6,Prince Edward Island Route 7,Prince Edward Island Route 8, and more. Then there'sOld Princetown Road. A quick search of talk pages finds more roads content edits, like:this,this,this,this,this,this,this,this,this,this... and more recently,this from six moths ago.
      Ivan is an active editor of road articles, and don't get me wrong, that's great, we are all grateful for his contributions over many years. But, sorry, it means Ivan can't act as an admin in the topic of roads.Particularly when he's disagreed with HEB in the content dispute that is the basis of the CBAN proposal (the RSN thread).
      Aside from WP:INVOLVED, I don't see any weighing of arguments in the closing statement; in fact, every paragraph seems to just count heads, talking about how many or how few editors supported or opposed particular positions; this is contraWP:NOTAVOTE. I hope in the close ofthis review, the closer weighs arguments, because some of the !votes above say absolutely nothing about WP:INVOLVED, and some !votes directly contradict the plain language of WP:INVOLVED.
      Finally, I think it's pretty weak to blame HEB for "wikilawyering" because he correctly identifies Ivan as WP:INVOLVED. Blame Ivan, not HEB, for the time spent on this close review, which could have been saved if Ivan had just self-reverted his close.Levivich (talk)23:00, 14 December 2025 (UTC)[reply]
      AlsoWP:CANVASSed - I just noticed in re-reading the RSN thread that Ivan was not only WP:INVOLVED, but was also canvassed to this ANI thread by TPH inthis comment, where TPH pinged four editors to tell them about this ANI thread, all of whom expressed an opinion in the RSN thread that contradicted HEB. Credit to three out of four of those editors, who didnot come and vote on the proposal. The fourth editor, Ivan, closed it. Come on, @Ivanvector: surely you can concede that you (1) have created articles and made edits in the topic of roads/highways, (2) said in the RSN thread that HEB's actions were "nonsense," and (3) were WP:CANVASSed to this ANI thread by TPH's comment. These are three indisputable facts, are they not?Levivich (talk)00:02, 16 December 2025 (UTC)[reply]
      Interesting to see that so many comments have been posted in that discussion even after HEB was blocked. I just counted about 70 comments after HEB was blocked, with people still disagreeing and arguing back and forth even though the blocked HEB wasn't there any more. Isn't that contradictory with the idea that HEB was the problem?AwerDiWeGo (talk)00:38, 16 December 2025 (UTC)[reply]
      The comments in the discussion above make it clear that RSN was only the proximate cause for a block... and it should be no surprise that a kicked hornet's nest keeps stinging even after the kicker runs away.Ed [talk] [OMT]15:41, 16 December 2025 (UTC)[reply]
      Thanks to Ivan for the forthright response below.Levivich (talk)18:24, 16 December 2025 (UTC)[reply]
    • Endorse because overturning would beneedlessly bureaucratic. I doubt another admin would have closed differently.However, waiting for a less involved closer would not have gone amiss. It's incumbent on admins to avoid even the appearance of impropriety in contentious actions. —Rutebega (talk)05:41, 15 December 2025 (UTC)[reply]
      I don't think it is fair to characterise the concerns raised regarding the close, in particular the options for sanctioning, as "needlessly bureaucratic". Regards,Goldsztajn (talk)12:18, 15 December 2025 (UTC)[reply]
    • Endorse (involved): Agree with Rutebega above. Even if this was reopened I'm betting someone else will close it as "narrow consensus" or something.~2025-31733-18 (talk)11:56, 15 December 2025 (UTC)[reply]
    • Endorse(Not involved): I don't necessarily agree with the indefiniteness of the block, I would have preferred escalating blocks, but that isn't the question being asked. I don't see how any other admin could look at the discussion and come to another conclusion. Reversing would be pointlessWP:BUREAUCRACY. --Mike 🗩13:46, 15 December 2025 (UTC)[reply]
    • Endorse, with maybe a trout for User:Ivanvector: yes, Ivanvector may have been 'WP:INVOLVED' in closing the discussion and blocking User:Horse Eye's Back. But, it seems very likely that overturning this and letting an uninvolved another admin close the thread is going to be ultimately a waste of time and effort, as User:Horse Eye's Back would (almost certainly) still end up getting blocked indefinitely anyway. In other words, the outcome would very likely still not change.
      I'll just add a quick, but quite important note to my message: there is an LTA, that appears to be either BKFIP or some imitator of them, who occassionally goes after and reverts edits made by User:Horse Eye's Back, often with the edit summary "remove horseshit", "Revert ban evasion WP: BKFIP", "revert incompetent fuckwit" or some variation of them. So if anyone out there is watching edits on articles that HEB has edited and they see reverts from an anon or new account with one of those edit summaries, absolutely revert it, even if it means restoring an edit made by another blocked editor. Regards, — AP 499D25(talk)14:22, 15 December 2025 (UTC)[reply]
    • Uninvolved Overturn.WP:INVOLVED is clear that "In general, editors should not act as administrators in disputes in which they have been involved." Commenting ona BLP the RSN noticeboard involving the blocked editor is a dispute they were involved in so the close should be overturned and an uninvolved admin close the discussion.GothicGolem29(Talk)16:21, 15 December 2025 (UTC)[reply]
    • Closer's comment - in case anyone gets the impression I'm ignoring this discussion, I'm not; I've been following closely but purposely not commenting so as to not unduly influence the outcome, but I think we're past that. I was aware of having made a drive-by comment in the RSN discussion about a sourcing issue but didn't think anyone could possibly believe that made me involved with respect to the editor who opened the discussion. HEB and I have barely interacted at all other than incidentally on noticeboards like this one, despite both being prolific roads editors (which was also news to me: the common element in the articles that have been itemized here is that they are topics in places where I live or have lived, not [exclusively] that they are roads). I don't remember having been pinged here, I have been dealing with a cross-wiki ping vandal lately and had to go back six pages in my notifications to find it, but it's there and marked read, and diffs don't lie anyways.
      But it's notmy point of view that matters:WP:INVOLVED is about avoiding theperception of bias, and with the evidence all laid out here it is abundantly clear that I crossed a line with respect to that policy. The community needs to be able to trust that discussion closes accurately and neutrally summarize the discussion and are free of bias, especially someone facing a site ban; I failed in that respect, and someone else should re-close.
      But having already demonstrated that my judgement here is flawed, I should not be the one to determine whether that means reopening/relisting the discussion, whether that relisted discussion should be re-closed immediately or listed for some time for additional comments, whether the close is sound despite my involvement, whether HEB's block should be reset to 30 days pending an outcome, whether a new discussion should be started, or someone even suggested taking the whole thing to Arbcom. Whoever closes this close review should determine on the basis of consensus here what we do next, and that won't be me.Ivanvector (Talk/Edits)14:14, 16 December 2025 (UTC)[reply]
      • It's unfortunate that some editors above have now successfully thrown as much as they can at a metaphorical dartboard, no matter its usefulness or relevance, in the hope that something will stick and magically create a sense of impropriety. I want to especially highlight the questionable assertions made byLevivich that INVOLVED here covers anyone who has worked in the roads topic area.
        First off, even a cursory look shows that Ivan dabbles in roads as part of a broader interest in Canadian topics—yes, dabbling, as a road isn't in their top 10 most-edited articles and Levivich had to reach backover ten years for their list of evidence. (I too would look like an active editor on a topic of your choosing if you looked back at the last decade.)
        But on the broader point, context matters. I am not automatically involved when I use my admin tools on something/someone in the general topic of military history, even though that has been my primary focus area for 17+ years. If Levivich's interpretation had consensus, admins would be actively avoiding all content work. But it doesn't, and for that you can see e.g.Dennis Brown's comment above for how INVOLVED actually works in practice.Ed [talk] [OMT]15:40, 16 December 2025 (UTC)[reply]
        I personally feel like Levivich, Silverseren, and dlthewave have ramped up their tendentiousness in the course of this discussion.Ten Pound Hammer(What did I screw up now?)16:14, 16 December 2025 (UTC)[reply]
        I think Levivich is a staunch defender of HEB, every time they are in the same discussion they seem to be on the same side~2025-31733-18 (talk)16:32, 16 December 2025 (UTC)[reply]

    Uninvolved endorse - I don't buy the notion that drive-by comments or activities from 10 years prior make a strongWP:WIKILAWYERING case over the intricacate technicalities ofWP:INVOLVED. If this meets the threshold of INVOLVED, it would be easy to waste everyone's time with endless review nonsense in the future based of someone else clicking "Oldest" on someone's contributions page. Such behaviour seems tenditious and should be discouraged, not encouraged. The close was correct on the merits and I expect that another closer would close the same way. ―"Ghost of Dan Gurney"(hihi)17:18, 16 December 2025 (UTC)[reply]

    TenPoundHammer's conduct

    [edit]

    Levivich raises several concerns about TPH's conduct in the events leading up to this including language like"Horse Eye's Back (talk · contribs) has been slathering Michigan road articles", and we have"then went on a tirade across various Michigan highway articles" right here in this ANI filing. More concerning is this unambiguous example of canvassing editors to this discussion:

    • 13:29 6 December 2025 -"@MjolnirPants:, @GreenMeansGo:, @Ivanvector:, @CapitalSasha:: Please see also Wikipedia:Administrators'_noticeboard/Incidents#Bad-faith_edits_from_Horse_Eye's_Back_(talk_·_contribs)..._again. - Unambiguous canvassing atWP:RSN.

    At the very least, a formal warning about canvassing is in order, and I think their overall behaviour deserves the same scrutiny as HEB's. –dlthewave02:58, 16 December 2025 (UTC)[reply]

    I'vedone the required courtesy of notifying TPH of this thread.Ed [talk] [OMT]03:38, 16 December 2025 (UTC)[reply]
    What I see is me neutrally informing related parties of a similar thread, which seems to fall under theEditors who have participated in previous discussions on the same topic (or closely related topics) clause ofWP:APPNOTE. I also do not appreciate dlthewave'stemplating of the regulars here. Nor do I find "slathering" or "went on a tirade" particularly egregious, but if someone is indeed upset by my word choice, then I do apologize and will try to rein it in.Ten Pound Hammer(What did I screw up now?)03:51, 16 December 2025 (UTC)[reply]
    It seems contradictory that you think Ivan is a "related party" and has "participated in previous discussions on the same topic (or closely related topics)" but "there is no conflict of interest here per WP:INVOLVED".Levivich (talk)04:45, 16 December 2025 (UTC)[reply]
    To repeat a question which was asked in that thread but never answered: Why those four? –dlthewave04:51, 16 December 2025 (UTC)[reply]
    That does seem to be an important question, since there were multiple others editors already involved in that RSN discussion, including multiple top level comments that were not included in the pinging in that edit. It appears those selected were chosen due to what their likely stance would be in this discussion.SilverserenC05:02, 16 December 2025 (UTC)[reply]
    I chose them because they were the first four names I saw, simple as that.Ten Pound Hammer(What did I screw up now?)15:23, 16 December 2025 (UTC)[reply]
    TenPoundHammer, can you explain these removals of HEB's comments in two articles' talk pages:[3] and[4]? By "explain" I mean "explain", not what you wrote in the edit summaries of those removals (edit summary one:rv pedantry from indef'd user; edit summary 2:Rv polemic edits), which don't explain anything... less so if one reads the deleted comments. --AwerDiWeGo (talk)08:11, 16 December 2025 (UTC)[reply]
    The reason for removal is obvious—the comments are pedantic demands for attention from a now-banned user. Restoring them leaves unresolved sections on article talk pages and is pointless.Johnuniq (talk)08:30, 16 December 2025 (UTC)[reply]
    Can I then strike the word "obvious" from your reply, dear admin, because the reason for striking it is obvious?AwerDiWeGo (talk)08:48, 16 December 2025 (UTC)[reply]
    I don't see any justification for deleting HEB's comments. HEB was not violating a block or ban when they commented (perWikipedia:Talk page guidelines#sockvote) and their deleted comments were notgibberish, test edits, harmful or prohibited material perWP:TALKOFFTOPIC. In particular, it's difficult to dispute HEB's comment thatThe highway travels through wooded terrain along its routing (recently removed) is not supported bythis source. This kind of behaviour together with TPH's edit summaries may be indicative of an aggressive approach to editing.Gitz (talk) (contribs)14:10, 16 December 2025 (UTC)[reply]
    Most of the comments I removed were HEB haranguing me and/or other editors with the same demanding bad-faith arguments that most other editors agree are the kind of behavior that led to his ban. If there was some wheat in the chaff, then I didn't find it worth keeping, but if other editors think I went too far, then I'll let them stand.Ten Pound Hammer(What did I screw up now?)15:31, 16 December 2025 (UTC)[reply]
    How benevolent of you to let the chaff stand.AwerDiWeGo (talk)21:18, 16 December 2025 (UTC)[reply]
    • I hatted this section and was (improperly) reverted by AwerDiWeGo. This has nothing to do with the administrative close review, which is why I hatted it as it is a new claim, in the wrong place. I will leave it to others to handle.Dennis Brown -12:14, 16 December 2025 (UTC)[reply]
    I'm not really impressed by TPH's conduct either. Perhaps they should take a deep breath and try not to get worked up enough about highway maps to makea statement implying that the opposing view is insane.JustARandomSquid (talk)16:59, 16 December 2025 (UTC)[reply]
    I would dismiss this as a retaliatory attempt at a "gotcha" by overturn !voters in the above review, weak on the merits, done without the required notification and irrelevant to said close review, and hope that an uninvolved admin re-hats this. ―"Ghost of Dan Gurney"(hihi)17:26, 16 December 2025 (UTC)[reply]
    I would not.Above I read about a kicker and a hornet's nest. Who is the kicker in your analogy@The ed17:? The original poster at ANI, i.e. Ten Pound Hammer? HEB? And, perhaps more importantly, which of your colleagues are the hornets in your analogy? -- SashiRolls 🌿 · 🍥19:29, 16 December 2025 (UTC)[reply]
    In context, is it not clear that both I and the previous commenters are referring to HEB and/or the RSN discussion? The topic of maps as sources is full of strong opinions on all sides, hence the hornet's nest analogy. It could have also been expressed as the can of worms remaining open even after HEB's block.Ed [talk] [OMT]19:52, 16 December 2025 (UTC)[reply]
    So HEB is guilty of bringing up a topic that others find worth discussing. Maybe that's the clear explanation that I and other editors have been asking for: "All of you beware of bringing up topics that others find worth discussing."AwerDiWeGo (talk)20:47, 16 December 2025 (UTC)[reply]
    That is a completely incorrect reading of what I wrote. That's a surprise to see from a person who I know read the entire back and forth becauseI was responding to your own comment. I'll repeat that conversation here. You said:
    Interesting to see that so many comments have been posted in that discussion even after HEB was blocked. I just counted about 70 comments after HEB was blocked, with people still disagreeing and arguing back and forth even though the blocked HEB wasn't there any more. Isn't that contradictory with the idea that HEB was the problem?
    I said:
    The comments in the discussion above make it clear that RSN was only the proximate cause for a block... and it should be no surprise that a kicked hornet's nest keeps stinging even after the kicker runs away.
    In that context, I can't at all see how you'd get the notion that I'm warning people against bringing up controversial topics. What I said was obviously specific to the ideas that HEB was blocked only for their recent edits on RSN + that HEB is not a problem just because the content discussion continued after his block. In the future, please do not twist my words.Ed [talk] [OMT]21:04, 16 December 2025 (UTC)[reply]
    I'll reword my previous comment then: Why is it being so difficult to have any of you answer (in an intelligible manner) the question: What did HEB do that was so wrong as to merit the sanctions they got?AwerDiWeGo (talk)21:27, 16 December 2025 (UTC)[reply]

    Abuse of LLM by Paleorthodox

    [edit]

    Paleorthodox usesWP:LLM. They have claimed on their own talk page that they check everything they write ([5]). Yet atBiblical archaeology I found a hallucinated source, a piece of hallucinated information (there might be more, though), and booksWP:CITED without any page numbers or quotes.

    The point is not having them sanctioned, but someone checking their past edits.

    This source is hallucinated:Schiffman, Lawrence H. (2019). "The Significance of the Dead Sea Scrolls".Journal of Jewish Studies.70 (2):195–210.doi:10.18647/3413/JJS-2019. Introduced here:[6].

    This claim is hallucinated:Israel Finkelstein and Neil Asher Silberman argue that archaeological evidence often contradicts the traditional biblical chronology, especially regarding the patriarchs, Exodus, and conquest of Canaan. In reality, IF and NAS say those events never happened, not that those were wrongly dated.

    AlsoWP:NPOV issues: glossing over the fact that much of the Bible got debunked by archaeology.tgeorgescu (talk)23:44, 7 December 2025 (UTC)[reply]

    @Tgeorgescu I feel bad, I saw your post on their talk page (which is on my watchlist) and was going to message you about opening a case at AINB. I can help you with that. Although admins should expect we will probably be back here soon given that this user has continued to seriously misuse LLMs past my conversation with them a month ago, and alsoSpecial:Diff/1320364851NicheSports (talk)00:44, 8 December 2025 (UTC)[reply]
    Timing is a key aspect of comedy:
    06:38, 4 November 2025**Lake Erie Jackals**,Collectively, these franchises reflect Erie's deep connection to the sport, from grassroots high school tournaments like the Burger King Classic to the city’s evolving presence in professional and semi-professional basketball.
    06:50, 4 November 2025 – A question from NicheSports:do you do any review of the LLM outputs?
    06:52, 4 November 2025 – A response:Yes, I do actually read what I post and edit accordingly.
    07:13, 4 November 2025Taken together, Erie’s professional and amateur football history showcases both its enduring passion for the sport and its capacity to produce athletes who succeed at higher levels. The city’s combination of competitive semi-professional play, strong high school programs, and collegiate participation ensures that football remains a year-round fixture in Erie’s sports identity.fifteen thousand two hundred twenty four (talk)01:06, 8 December 2025 (UTC)[reply]
    Here ([7]) Dever's harsh denial that the Conquest of Canaan happened, Collins' confirmation of Dever's view, and IF and NAS' denial that the Conquest and the Exodus happened, all got replaced with a more pro-Bible POV (getting the stuff about traditional chronology mentioned above). Correction: Collins commenting about Dever already disappeared at[8]. And also did Lüdemann, which makes the POV-pushing obvious: Paleorthodox was censoring the mainstream academic views from the article.tgeorgescu (talk)01:26, 8 December 2025 (UTC)[reply]
    No comment on specifics of claims in the first diff, but the prose fails to impress and is what I would expect of LLM output:
    collapsed quotes
    • Modern scholars pursue questions like: ... followed by a bulleted list of unsupported questions.
    • The discovery of the Dead Sea Scrolls in 1947–1956 further galvanized interest. These texts provided unprecedented insight into Jewish sectarianism, biblical transmission, and Second Temple Judaism. They bridged archaeology and textual studies, showing how ancient manuscripts could emerge from archaeological contexts.
    • Albright's belief in a historical core to the biblical narratives influenced generations of archaeologists. He emphasized linking textual evidence to archaeological data, seeking harmony between the Bible and the spade.
    • **Jewish interpretation** ... **Christian theology** ... **Islamic understanding**
    fifteen thousand two hundred twenty four (talk)01:33, 8 December 2025 (UTC)[reply]
    Yup, an article which took archaeologicalWP:SCHOLARSHIP seriously was transformed into pro-Bible smooth talk.tgeorgescu (talk)01:37, 8 December 2025 (UTC)[reply]
    This comment only means you're a skeptic who favors anti-Bible smooth talk with a major bias against conservative scholarship. Sounds like a major POV violation.Paleorthodox (talk)14:19, 12 December 2025 (UTC)[reply]
    "The model of "biblical archaeology" has collapsed. Twenty-first century biblical archaeology is often conducted by international teams sponsored by universities and government institutions such as the Israel Antiquities Authority. Volunteers are recruited to participate in excavations conducted by a staff of professionals. Practitioners are making increasing efforts to relate the results of one excavation to others nearby in an attempt to create an ever-widening, increasingly detailed overview of the ancient history and culture of each region. Recent rapid advances in technology have facilitated more scientifically precise measurements in dozens of related fields, as well as more timely and more broadly disseminated reports.
    A non-LLM user wrote this paragraph very poorly, especially in passive voice. Neither do the statements represent the source material. Moreover, writing like this is intended to censor conservative scholarship.Paleorthodox (talk)14:35, 12 December 2025 (UTC)[reply]
    writing like this is intended to censor conservative scholarship[9]
    This comment only means you're a skeptic who favors anti-Bible smooth talk with a major bias against conservative scholarship[10]
    Then the admins have the duty to explain that context to casual users. Instead, they power-trip and act like the Inquisition.[11]
    I want this bullying and false accusations in bad faith to stop[12]
    This is a mix of a clear failure toassume good faith and abattleground mentality.fifteen thousand two hundred twenty four (talk)15:03, 12 December 2025 (UTC)[reply]
    These statements bytgeorgescu are in extremely bad faith and his battleground mentality:
    "Glossing over the fact that much of the Bible got debunked by archaeology."
    "Timing is a key aspect of comedy."Paleorthodox (talk)06:32, 13 December 2025 (UTC)[reply]
    I am the one who saidTiming is a key aspect of comedy, not tgeorgescu. That other quote does not demonstrate a failure to assume good faith, nor a battleground mentality.fifteen thousand two hundred twenty four (talk)07:16, 13 December 2025 (UTC)[reply]
    Restoring the last stable version is allowed. It does not mean that I've checked everything written there by others.
    "Claiming that historical criticism is passé may suggest to some that conservative biblical scholarship has won the “battle” against historical criticism and is now finally vindicated. This may sound appealing in popular circles, but it is not true in academia." Peter Enns[13].tgeorgescu (talk)04:57, 13 December 2025 (UTC)[reply]
    • Indef immediately, no questions asked. Hopeless. AI must be destroyed.EEng10:28, 9 December 2025 (UTC)[reply]
      Yes, including non-generative AI. In fact, microelectronics really have caused us nothing but grief since they were invented.Duly signed,WaltClipper-(talk)12:52, 10 December 2025 (UTC)[reply]
      Are you nostalgic for punch cards? Maybe you want to edit by mail? How would Wikipedia work without microelectronics?/s~2025-31733-18 (talk)13:24, 10 December 2025 (UTC)[reply]
      In fact yes, Iam nostalgic for punch cards. And a lot of things are done quite effectively by mail e.g. chess.EEng19:15, 11 December 2025 (UTC)[reply]
      I agree that Artificial Intelligence shouldn't be used to create Wikipedia content, but what does poor Alan have to do with it? And why must he be destroyed?Phil Bridger (talk)20:06, 11 December 2025 (UTC)[reply]
      Maybenongenerative Al is one of those sadincels we keep hearing about.EEng15:42, 12 December 2025 (UTC)[reply]
      Maybe it cancall you Betty.Ivanvector (Talk/Edits)19:31, 12 December 2025 (UTC)[reply]
    • Blocked indefinitely from article namespace.Ivanvector (Talk/Edits)13:37, 10 December 2025 (UTC)[reply]
      This block is extremely unfair. Is there an actual Wikipedia policy about LLMs, because all I see is bias against new technology. I thought I checked all the sources, and the hallucinated one was an honest mistake. All I see here is a rush to block people who use AI out of an outdated idea of "creativity."Paleorthodox (talk)14:14, 12 December 2025 (UTC)[reply]
      Wikipedia:Writing articles with large language models. Hope this helps. •a frantic turtle 🐢14:18, 12 December 2025 (UTC)[reply]
      Okay, I should have been given a warning instead of everyone acting like I committed a crime and blocking me. That's unfair.Paleorthodox (talk)14:22, 12 December 2025 (UTC)[reply]
      Blocks are supposed to be preventative, not punitive, so if you commit not to use an LLM to write article content, and especially sources (which LLMs seem to have a particular problem with), then you should not be blocked.Phil Bridger (talk)14:51, 12 December 2025 (UTC)[reply]
      (edit conflict) You're blocked from contributing to articles because your contributions were pushing anon-neutral point of view, and were supported by citations to sources that do not exist. The block is to protect Wikipedia from the damage you were causing; you would have been blocked whether you used an LLM content generator or if you had written these contributions entirely unassisted. Your subsequent comments about skepticism and favouring conservative scholarship don't suggest to me that your POV has anything to do with having an LLM write for you, and doesn't inspire confidence that you would be able to contribute constructively if you were unblocked, but seeWP:UNBLOCK for your options.Ivanvector (Talk/Edits)14:53, 12 December 2025 (UTC)[reply]
      Imagine LLMs don't exist. Any editor copying and pasting content into Wikipedia without performing adequate review and correction, as evident fromWP:V and prose issues, is engaging in disruptive editing. I would expect an editor of your tenure to recognize this.fifteen thousand two hundred twenty four (talk)14:54, 12 December 2025 (UTC)[reply]
      When I wrote my previous comment I assumed that you were blocked just for using an LLM. I now see that there was more to it than that.Phil Bridger (talk)14:58, 12 December 2025 (UTC)[reply]
      No, I was blocked for using an LLM. They simply didn't like that I used a conservative viewpoint. They even pointed out that the source wasn't actually hallucinated, and they could have simply made the correction.Paleorthodox (talk)06:19, 13 December 2025 (UTC)[reply]
      Wrong, that source did exist and should have been corrected. Instead, you claimed it was hallucinated instead of cited incorrectly. When the article makes left-leaning, heavily biased statements like, "The model of biblical archaeology has collapsed," this is certainly not neutral POV. That statement flattens a whole page of research into a nonsensical statement.Paleorthodox (talk)06:24, 13 December 2025 (UTC)[reply]
      Maybe it hasn't collapsedamong evangelicals and fundamentalists. In the mainstream academia, it did. Name any Ivy League university, name any US state university, they will agree.
      Citing a conservative scholar is allowed, denying that big chunks of the Bible have been debunked is not. This is all about being in touch with the reality of mainstream archaeology.
      this is certainly not neutral POV—I can assure you that according toWP:GEVAL, the two POVs are by no means symmetrical. What has been excavated from the earth produces a profound asymmetry: we're biased for real, objective evidence.tgeorgescu (talk)07:56, 13 December 2025 (UTC)[reply]
      Paleorthodox, I am the administrator who blocked you. When I wrote above that "you would have been blocked whether you used an LLM content generator or if you had written these contributions entirely unassisted", that is, in fact, what you were blocked for. Notbecause you used a large language model, buthow you used it.
      You've written that the hallucinated source above was not hallucinated, that it exists and only the citation needs to be corrected. The doi link in the citation is to the same journal, but a different issue of that journal and a different article entirely, a book review ofThe Cambridge History of Jewish American Literature. The citation you provided indicates a volume and issue number of that journal, so I looked upits index, and the article you cited does not exist in that issue. In fact, as far asI can tell, whileLawrence Schiffman is a noted expert in the Dead Sea Scrolls, he has never published any article in theJournal of Jewish Studies. Your LLM produced content that fit your prompt, and theninvented a citation which superficially appeared from its author and title that itwould support the point of view it generated, when in fact on even a cursory review it is obvious that the sourcedoes not exist. If youwere reviewing your LLM's generated content then youwould have noticed, so you either didn't review, or you did review and published the content anyway. I'm not sure which is worse.
      You are blocked because you submitted unverifiable content to Wikipedia in support of your own point of view cited to a source that does not exist, and you remain blocked becauseyou are still defending your inappropriate submission.Ivanvector (Talk/Edits)13:07, 13 December 2025 (UTC)[reply]
      @Paleorthodox: The root of the complaint is that there is a big difference betweennot knowing whatWP:CHOPSY teach, and purposefully deleting whatWP:CHOPSY teach.tgeorgescu (talk)08:35, 15 December 2025 (UTC)[reply]
      I thought I reviewed everything, but I clearly missed this citation. I wasn't even aware there was a discussion about this until you blocked me. I recant the hallucinated citation. However, when @Tgeorgescu claims that biblical archaeology is irrelevant and misrepresents the field and conservative scholarship, that is merely his subjective bias and should have zero bearing on me staying blocked.Paleorthodox (talk)17:38, 15 December 2025 (UTC)[reply]
      No, you merely have an atheistic bias toward anything to do with religion and nearly everything you claimed is demonstrably false. Yale University, for example, studies biblical archaeology in various fields:https://archaia.yale.edu/about. Just admit that you are wrong. There is no such thing as a CHOSPY test beyond Wikipedia, and many Wikipedians abuse this test to silence material they simply don't want to see. It's entirely subjective.Paleorthodox (talk)17:26, 15 December 2025 (UTC)[reply]
      Okay, sayWP:BESTSOURCES instead ofWP:CHOPSY: there is no excuse from deleting the best sources from the article. E.g. I don't like the POV of that Kaiser guy, but I did not remove him from the article.
      "Modern archaeology contradicts big chunks of the Bible" is not an atheistic POV. It's the reality of what has been excavated from the earth. And I'm not atheist. And of course the intellectually bankrupt apologetics industry engages indenialism: they simply don't like the facts uncovered by archaeology. So, Wikipedia does not cater to apologetics.
      Many Bible professors, who are Christians, will admit that the Bible has all sorts of mistakes in it. There is nothing inherently anti-Christian in that admission.
      And the Google search forsite:archaia.yale.edu bible does not offer much.tgeorgescu (talk)04:20, 16 December 2025 (UTC)[reply]
    • Endorse block. Paleorthodox has indeed misused an LLM to introduce inadequately reviewed content (including hallucinated content) into articles, and an unblock should only be considered if Paleorthodox agrees to the followingunblock conditions: a prohibition against using LLMs to edit Wikipedia, and atopic ban frombiblical studies,broadly construed. — Newslinger talk21:30, 15 December 2025 (UTC)[reply]

    R3YBOl is banned on three Wiki projects, socking, racial slurs (N word), constant sourcing problems

    [edit]

    I wasn't really sure if I should take this to the Incidents page because most of the worst offending behavior seems to have ended earlier this year in March whenUser:R3YBOl called another user@Moha7817: the N word and was banned for socking on the Arabic Wiki project. The initial reason this came up again is because I recently ran into somecontent dispute issues with R3YBOl where I asked for third party dispute resolution. Theytold me to wait a couple of weeks untilChristmas Eve before commencing dispute resolution so they could finish their test prep irl, but in the meantime they wouldstill continue to edit by reverting IPs. I'm not saying that this reason is impossible but a cursory glance at their edit history told me R3YBOl edited on a near daily basis and the content dispute in question was a page they were quite familiar with and had been working on for months. That combined with the tendentious behavior I had spotted made me very skeptical of their intention and resulted in a deep dive into a rabbit hole of this user's history.

    What I found out about R3YBOl is that they are already banned on three Wiki projects. There's aMeta wiki global ban request (15 August 2025) for socking, racial slurs (N word), lying about language proficiency, misuse of sources (inconsistency and OR), anti-Kurdish bias, trigger happy claiming others are socks and making SPI requests (especially against Kurds) as well as article deletion requests (also against Kurds), and POVPUSH on Persian Wiki. This seems to be in line with what I've seen of R3YBOl's edit history. They seem to be in constant conflict with Persian and Kurdish editors.Idris Shirazi (talk ·contribs)pointed out that at one point R3YBOl made a draft for an article calledThree_Whom_God_Should_Not_Have_Created:_Persians,_Jews_and_Flies, which from my understanding is a historical text. But in the context of their biases, seems a bit on point.

    At the time of the global ban request, one of the reasons brought up against their ban was that they weren't banned ontwo or more wikis yet, but this is only true for R3YBOl and not the account which was identified as thesockmaster on Arabic wiki, translated asAbu Khashm Al-Sandous (ابا خشم السندوس). They are also registered asUser:ابا خشم السندوس on EN Wiki. They arebanned on Arabic Wiki, Egyptian Arabic Wiki, and Wikimedia commons. The English account wasreported on Incidents in March 2025 by@كريم أحمد: but since R3YBOl was older, it was dismissed.

    They were firstbanned on Egyptian Arabic Wiki on 19 January 2025 for no particular reason stated even though they only had one edit so maybe this points to an even longer history of problems prior. Idk what this kind of ban implies. On Wikimedia Commons they werebanned for socking on 31 January 2025. On Arabic Wiki there are11 confirmed accounts, 6 of which were spotted aiding their main account intalk discussion and banned for socking on 13 February 2025.

    R3YBOl was later found as a sock andbanned on 1 March 2025 with 3 or 4 other socks. Their last edit on Arabic Wiki was on 8 February 2025 calling@Moha7817: awhite n*gger, before which they had already called themn*gger on 2 December 2024, andMr. Krabs (pejorative for miserly, cheap) on 29 December 2024. In hindsight, I wonder if the Mr. Krabs comment was a reference to Jews but I'm not familiar with Arabic slang.

    All of this makes me incredibly skeptical of engaging with this user. I initially wasn't going to go to ANI due to most of the major issues being several months old, butUser:Kansas Bear recommended I do so.

    While these bans happened months ago, what I find concerning now is that R3YBOl has not really changed from their original mindset that led to their conflicts with other uses and quick ban. They are still highly biased regarding events concerning Arabs in particular, and are not abovecitation stacking with an assortment of low quality and Arabic sources toprove a point. I go into further details about R3YBOl's consistent willingness to useWP:FRINGE sources in thearticle talk].

    The major difference between now and then is that they are less prone to immediate edit warring and has mostly switched to tendentiousWP:Civil POV pushing. Initially they justPOVPUSH without sources but then they switched to adding sources, just really bad ones or ones with dubious statements on subjects that they are clearly biased on. The sources are very Islam-centric and biased towards the Arab POV. I want to make clear that the issue here is not adding different perspectives, but that R3YBOl will always go out of their way to find for any statement from any source no matter the quality to push an Arab biased perspective. You can see this early on in their edit summaries back inDecember 2024. Sometimes they are lazy and just copy from the text word for word. Often they make small changes like remove a word like Persian and claim a certain person was Arab or change a conflict infobox to alter force sizes or participants with dubious and outdated sources or no sources. They will often apologize (or not) and then revert to problematic sourcing or undue belief in dubious statementsagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain, andagain,

    It is not as if they do not understand how reliable sourcing work. They have beenexplained tomorethanadequatelyseveraltimesbymultipleusers.

    The problem with their editing is that they have a persistent motive to aggrandize events related to Arabs while attacking any opposite elements, mainly Persians/Kurds. I think their stance on Iranians, Kurds, and anybody in a conflict with Arabs can probably be summed up by the following edits:[14][15][16][17][18]

    Also note that R3YBOl is their earliest and possibly main account. They were insulting people and socking on Arabic Wiki while concurrently editing on EN Wiki. I don't know if anything will come of this, which was why I was initially reluctant to take this to ANI, but at least this will go on record for any further discussions regarding this user.Qiushufang (talk)03:53, 9 December 2025 (UTC)[reply]

    @Qiushufang Our issue was from a content dispute and now it's been taken to ANI? I already told you that we will resolve our dispute in the DRN as soon as I get free again and I explained that I am busy.R3YBOl was later found as a sock and banned on 1 March 2025 with 3 or 4 other socks the sock master is not me and if it's acceptable, I request a checkuser to make sure if I am them or not.They will often apologize (or not) and then revert to problematic sourcing or undue belief in dubious statements are you bringing up situations that happened 7-9 months ago? how is this even validthat at one point R3YBOl made a draft for an article called Three_Whom_God_Should_Not_Have_Created:_Persians,_Jews_and_Flies, which from my understanding is a historical text. But in the context of their biases, seems a bit on pointthis article exists in different Wikipedia platforms and it talks about a pamphlet, I lost motivation in editing that draft, Which I even forgot about it.There's a Meta wiki global ban request (15 August 2025) for socking, racial slurs (N word), lying about language proficiency, misuse of sources (inconsistency and OR), anti-Kurdish bias,the user who requested global ban against me, has a long history of racism and vandalism in different Wikipedia platforms. they were once banned for displaying an anti-Arab userbox "This user hates the arabs and wants them to be annihilated" on Ckb Wikipedia, which even the admins banned them for several days for that. they go by the name User:Average kurd. Average kurd claimed that I don't know kurdish (which is supposed that I lied about knowing kurdish) yet I took all of these information from their talk page archive. Average kurd was not someone who was doing anything other than trolling on English Wikipedia.[19][20][21][22] they even cursed at the admins when they were trying to get them unblocked, and the admins can see this in their deleted contributions.[23] they also sent me a full threat on Ckb Wikipedia, the message was written in kurdish and arabic.[24] It was unnecessary for such a person to request a global ban for me and it was already declined.[25] regarding the sources that I cited, you reverted the non-arabic sources (from citation number 40 to 48 were removed for no reason; the sources there are all made by historians who have specialization in the field of history) if you were concerned about these low quality arabic sources, why did you not remove them and keep the English ones that were written by historians such asClifford Edmund Bosworth? I also noticed that you started a new talk page section inBattle of Talas, which it was aWP:WALLOFTEXT of casting aspersions against me and calling out my sources as low quality sources.. how is a source from Iranica supposed to be a low quality source? or a source from Encyclopedia of Islam also supposed to be a low quality source? regarding resolving our dispute in the DRN, I already explained for you the reasons and told you that I am busy. It is true that I talked about reverting some unconstructive edits made by unregistered accounts, but you can notice that since our last discussion, I haven't edited anything.R3YBOl(🌲)06:26, 9 December 2025 (UTC)[reply]
    I took this to ANIbecause your behavioral issues go back months if not the entire year.WP:ASPERSION only applies when you are accusingmisbehavior without evidence. That is not the case here. Similar issues reappearing atBattle of Talas were repeated months ago despite so many explanations by multiple users is actually an indication that it is probablyless useful to continue further dialogue, not more. Why am I supposed towaste time talking to you aboutWP:AGEMATTERS when somebody already did the exact same thing back inMarch? Your predilection for stacking citations needlessly was also mentioned back inMarch, although in the case at Talas, it was obviously to POVPUSH proof that it is the "majority opinion". You have a clear preference for instating force numbers and battle article results to favor the Arab side using low quality sources or dubious statements ([26][27][28][29][30][31][32]) that has extended to the present day.
    These are behavioral issues with your editing and not related to any single misuse of a source and would not be fixed if we went to dispute resolution. I have already spentenough words describing issues that just turned out to be things multiple other users have explained to you.
    I also don't feel too enthused about discussing things with someone who would go out of their way to call someone "n*gger", "white n*gger", and "Mr. Krabs". If you are not a sock, then your behavior makes even less sense , because that would mean you randomly went to some other person's account and racially harassed them by calling themcalled them n*gger,white n*gger, and asked them if they would rather be "yellow, black, or pink?" You hadzero interactions with them beforehand and they responded to your comments with aquestion mark. A day after your harassment, the sockmaster accountasked the user you harassed not to revert their edits, so I can at least see why you would be seen as a sock if it truly isn't true. But I am skeptical about that too. You werebanned a month after your last edit on the same day as another sockSalafi, which usually indicates that admin found additional evidence linking to you or judged the behavioral clues sufficient for a ban. Either way, I thought the past history and current behavioral problems were sufficient for at least a post to put this on record.Qiushufang (talk)09:25, 9 December 2025 (UTC)[reply]
    The account that is called "Salafi" isn't mine and "Salafi" refers toSalafism. I don't even belong to and Salafism is literally the opposite of my religion sect. feel free to open an SPI investigation and ask for checkuser to check if I am the sock master or not.R3YBOl(🌲)09:48, 9 December 2025 (UTC)[reply]
    • Support CBAN do we not haveno tolerance for the N-word on wikipedia?
    Tankishguy14:04, 9 December 2025 (UTC)[reply]
    I do support, and I do deal with zero tolerance for racial and gender slurs. However have they used any such slurs on the English Wikipedia? Maybe I missed them.Canterbury Tailtalk14:30, 9 December 2025 (UTC)[reply]
    No, this is only on Arabic Wiki. Here are the relevant diffs ([33][34][35]). They said some other stuff including quoting a certain Abu Shawqi and asking the user it was direct at whether they would rather be yellow, black, or pink. As far as I can tell R3YBOl had no prior interactions with the user who was insulted. I haven't seen them doing the same on EN Wiki but they have a POV bias in line with a nationalist bent, which was part of what made me suspicious about their intentions after running into a second content dispute issue on the same page.Qiushufang (talk)14:40, 9 December 2025 (UTC)[reply]
    bias in line with a nationalist bent is it just because I cited an old source made me nationalist? or I cited too many sources made me look bad? I don't understand since when citing was something bad to do? I was planning to clean up everything by just resolving the issue in the DRN but I explained myself that I am busy in these weeks. You were complaining about me citing low quality arabic sources meanwhile you removed all the english sources that I cited regarding the article and I still have no idea how are they supposed to be arabic sources when the sources are literally in English and written by non-Arabian historians.R3YBOl(🌲)14:46, 9 December 2025 (UTC)[reply]
    I've already given my reasons above why I am skeptical about your claims of ignorance. Multiple users on at leastnine separate occasions have explained to you how reliable sourcing works includingdubious statements in a dozen long comments. It is eitherWP:COMPETENCE issues or feigned ignorance. Seeing your past history makes me lean towards deliberate denial of understanding.Qiushufang (talk)15:00, 9 December 2025 (UTC)[reply]
    However have they used any such slurs on the English Wikipedia? Maybe I missed them I would like to answer you myself, No I never used any slurs in English Wikipedia because I respect the encyclopedia. I wasn't banned for the slurs but for sockpuppeting in arabic Wikipedia but the sockpuppeting accusations is false and I myself would like to ask for a checkuser on my account and the sock master's account, whenever I have a dispute with an editor, they bring up arabic Wikipedia's situation.. I would rather choose to have a clean start and abandon this account because this is getting frustrating. I have been accused of being anti-kurd, and that's because I was involved in some ANI discussion that got some nationalist editors banned, one of those editors is Average kurd, who literally have shown their hatred to arabs in their own Wikipedia profile.[36], they added two different quotes about some person had said this (Ibn Khaldun):
    1. Wherever Arabs settle, destruction follows. When Arabs are hungry, they steal; when they are satiated, they commit immoral acts.
    2. If you get arabized, you will be destroyed
    and so many other sock masters that I used to report their socks and file SPIs against their socks, brought up the slurs of arabic Wikipedia where even admins told them that they don't deal with this here.R3YBOl(🌲)14:42, 9 December 2025 (UTC)[reply]
    Checkusers won't doself-requests (at least on enwiki).Tenshi! (Talk page)14:46, 9 December 2025 (UTC)[reply]
    Checkusers won't do self-requests (at least on enwiki) Alright, then how can I prove that I am not related to that sock master? I have filed over 30 SPIs and I know how it is frustrating to report socks. If I get blocked, I won't ever create any other account to start a new series of sockpuppeting.R3YBOl(🌲)14:52, 9 December 2025 (UTC)[reply]
    courtesyOshwah ping for his opinionTankishguy14:06, 9 December 2025 (UTC)[reply]
    Support CBAN - There is no time for R3YBOI to respond further. We should push for CBAN based on hisWP:BATTLEGROUND behavior in other projects. Zero tolerance for slurs directed against everyone.Ahri Boy (talk)15:04, 9 December 2025 (UTC)[reply]
    @HurricaneZeta pingTankishguy15:30, 9 December 2025 (UTC)[reply]
    Tankishguy, is there a particular reason you are pinging other users to this discussion? Are they related to this dispute in some way?45dogs (they/them)(talk page)15:34, 9 December 2025 (UTC)[reply]
    from what they told me on and off-wiki, they like to be notified of possibly important AN or AN/I casesTankishguy15:38, 9 December 2025 (UTC)[reply]
    @Tankishguy, that is extremely obvious canvassing. You've also pinged Oshwah, for no reason as far as I can tell. Please stop pinging people to unrelated discussions. I would strongly suggest that you avoid user conduct discussions entirely and focus on regular editing. --asilvering (talk)16:30, 9 December 2025 (UTC)[reply]
    he probably pinged Oshwah because ofthis𐩣𐩫𐩧𐩨 Abo Yemen (𓃵)16:38, 9 December 2025 (UTC)[reply]
    That is the AGF version of it. But there isthis, so I don't think its a one time issue.45dogs (they/them)(talk page)16:51, 9 December 2025 (UTC)[reply]
    he would have told me if that was canvassing. i only ever meant to broaden consensus, not canvass.WP:CANVASS says
    "In general, it is perfectly acceptable to notify other editors of ongoing discussions, provided that it be done with the intent to improve the quality of the discussion by broadening participation to more fully achieveconsensus."
    "Canvassing is notification done with the intention of influencing the outcome of a discussion in a particular way, and is considered inappropriate. This is because it compromises the normalconsensus decision-making process, and therefore is generally considereddisruptive behavior." If you ping me here again, I willnot respond, but note I will haveseen the notification. this caused me too much trouble, and I will move on now.Tankishguy21:51, 9 December 2025 (UTC)[reply]
    Sorry but I really don’t want to be pinged for discussions I’m completely unrelated to, especially on ANI.HurricaneZetaC17:13, 9 December 2025 (UTC)[reply]
    I do think pushing for a CBAN for content on other Wikimedia projects, where most people can't read the context without translation tools, is strange.45dogs (they/them)(talk page)15:33, 9 December 2025 (UTC)[reply]
    I do think that this report isWP:HOUNDING by Qiushufang𐩣𐩫𐩧𐩨 Abo Yemen (𓃵)15:44, 9 December 2025 (UTC)[reply]
    I don't think so.---Wikaviani(talk)(contribs)21:42, 9 December 2025 (UTC)[reply]
    Some of their edits since their ban on other Wiki projects echo the same racially based POV, although to a lesser degree, especially related to Persians/Kurds. See how they emphasize Arabs defeating Persians or try to delegitimize Kurds[37][38]. Idk what the Wiki policy is on racial slurs on different Wiki projects, but that wasn't the only reason for this ANI, and it has certainly affected my ability to trust them. There is after all a global ban request on R3YBOI and many of the problems described there mirror my interactions with R3YBOI.Qiushufang (talk)15:50, 9 December 2025 (UTC)[reply]
    although to a lesser degree, especially related to Persians/Kurds. See how they emphasize Arabs defeating Persians or try to delegitimize Kurds regarding the addition I added to theBattle of Nahavand,I already justified this edit to a different user, and I explained my intention was only shortening, it wasn't an improvement anyways because I violatedMOS:VICTORY and added I dots in the result parameters. As for "delegitimizing Kurds" that's not true, you brought a resolved discussion here, and I don't know how that is even supposed to be counted as "anti-Kurds". User:Ilamxan threatened to report me for removing parts that were not supported by the sources (the article was about a religious sect that was founded inLalish; the majority of sources mentioned that it was founded Lalish but not in "Kurdistan") I don't know how this is supposed to delegitimize the Kurds, the same editor even violatedWP:OWN by saying "The page is full of citations that mention Kurdistan. Touch it again and I will report you" andwas blocked for two days for personal attacks against me. Nothing to do with delegitimizing Kurds.R3YBOl(🌲)16:16, 9 December 2025 (UTC)[reply]
    R3YBOl, from what I see in the page you linked,User:Wikavianidid not accept your justification for that edit, and rightfully so. This is another problem where you seem to think and portray your explanations as sufficient and others should accept it. Another instance of this is where you made it sound like I agreed with you to dispute resolution at a later date you had set. I very muchmade it clear that was not the case.Qiushufang (talk)16:40, 9 December 2025 (UTC)[reply]
    Actually reading further into the comment you made, it makes me even more frustrated, because you consistently expect other users to extend goodwill towards youdespite your persistent editing behavior problems. A comment likeYou could have asked me nicely to re-write it for neutrality. is ridiculous. That's what you should have done from the beginning. What's ironic is that you even accuse Wikiaviani of thinking you are settling a "score between the arabs and the persians", to which they basically said as much about your editing history, so you are obviously aware of how others view you. Again, I am 100% sure now that you are not ignorant of your behavior.Qiushufang (talk)16:58, 9 December 2025 (UTC)[reply]
    I am not ignorant of my behavior, When I cited some non-english sources regarding the article.. I immediately translated what they said, Which indeed was a wrong thing to do. I initially thought non-English sources would be fine if I just translated and put them directly, but when I faced an issue like that with Wikaviani, I realized that I should paraphrase and represent it every source in the most neutral way possible. I paraphrased what Wikaviani had concerns about anyways.R3YBOl(🌲)17:10, 9 December 2025 (UTC)[reply]
    If you are not ignorant of your behavior and recognize that you should represent every source in the most neutral way possible, why do you need constantreminders andharanguing by other users to do it? What good is being aware of something when you do the same thing again and again? Is this aWP:COMPETENCE issue?Qiushufang (talk)17:36, 9 December 2025 (UTC)[reply]
    Oppose CBAN - He did not do any of his previous mistakes on the ar-wiki on here, and there is no proof for R3YBOl engaging inWP:SOCK on the English wiki. There is no reason for us to ban him for not doing anything on here𐩣𐩫𐩧𐩨 Abo Yemen (𓃵)15:36, 9 December 2025 (UTC)[reply]
    Oppose CBAN: I am failing to (a) see the objectionable actions R3YBOl may have done onthis wiki; and (b) to understand since when we became traffic cops for offenses purportedly committed elsewhere. I realize that lynch mob mentality often takes hold on the drama boards, but this is way too far. What's next, are we going to get doxxing teams demanding cbans because of what people have been getting up to in real life? We are not the damn thought police here. Ravenswing17:03, 9 December 2025 (UTC)[reply]
    Oppose CBAN - Barring evidence some of that behaviour has been imported to the English-language Wikipedia (evidence which is noticeably lacking here, especially as R3YBOI is defending their behaviour on this project here) a community ban is not warranted. As a reminder, different Wikipediae have different cultures, standards, and practices, and behaviours that might get someone sanctioned on one project may not be problematic on another,especially if said behaviour is not repeated on the second project. —Jéské Courianov^_^vthreadscritiques17:44, 9 December 2025 (UTC)[reply]
    Oppose CBAN per above. SeeWP:What happens on other wikis stays on other wikis; R3YBOI hasn't made any of those mistakes here. Also, sockpuppet accusations belong inWP:SPI. A block on Arabic Wikipedia for alleged sockpuppetry is not sufficient evidence.Skitash (talk)17:49, 9 December 2025 (UTC)[reply]
    Weak oppose cban same as skitash, need more diffs of this wiki.
    but the severity of issues on other wikis suggest we should not be lenient if issues do show upUser:Bluethricecreamman(Talk·Contribs)17:52, 9 December 2025 (UTC)[reply]
    Strong Oppose CBAN I have to agree with the above opposers as I also cannot see any wrongdoing on this wiki at all, other projects have different rules, and other projects dont have to follow one projects rules, due to them being in different languages and with different editors and different perspective on here. (I agree with Jeske)
    If there was proof of any wrongdoing by R3YBOI on this wiki, my vote would have been different, but it is a oppose to the community ban, As @Abo Yemen said,There is no reason for us to ban him for not doing anything on here.shane(talk to me if you want!)17:49, 9 December 2025 (UTC)[reply]
    Oppose CBAN per above and perWikipedia:What happens on other wikis stays on other wikis. Similar accusations had already been made against them in the past and there was no problem with it.[39]Kajmer05 (talk)18:11, 9 December 2025 (UTC)[reply]
    Oppose CBAN They have rightly been punished on those other wikis if they did do what you claim that they did (I can not read Persian or Arabic). It seems that they might have learned from that as they haven't done these things on English wikipedia. This ANI report was also after a content dispute, so I think this may be unnecessary escalation and made in the heat of the moment.User:Easternsaharareview this01:52, 12 December 2025 (UTC)[reply]
    Oppose CBAN The evidence presented does not meet the threshold required underWP:CBAN, and the conduct described does not justify the most severe sanction available to the community. Most incidents cited occurred months ago and have not recurred on the English Wikipedia, sanction decisions must be based on current on-project behavior seeWP:What happens on other wikis stays on other wikis. The present issues concern content and sourcing disputes, which should be handled through established processes such asWP:DRN,WP:RSN, or anRFC, rather than ANI. No recent diffs demonstrate ongoing harassment, edit-warring, or disruptive conduct on EN-wiki sufficient to warrant a ban. As the criteria for a CBAN are not met and no current disruptive pattern has been demonstrated, a sitewide ban is unwarranted, and I therefore strongly oppose.Heraklios18:49, 13 December 2025 (UTC)[reply]

    Comment : Unfortunately, R3YBOI seems to have some kind of agenda when it comes to Arab-Iranian topics. Edits likethese ones where R3YBOI completely wisrepresents what the source says, or[40] and many others are often made as part of a pro Arab agenda. I would go for a TBAN (on Arab-Iranian topics) broadly construed rather than a CBAN.---Wikaviani(talk)(contribs)21:25, 9 December 2025 (UTC)[reply]

    I don't see how any of those sourced edits (with quotes in the citations) would constitute a "pro Arab agenda." Moreover, ANI concerns behavioral issues and not content disputes.Skitash (talk)21:40, 9 December 2025 (UTC)[reply]
    Behavioural misconducts, like blatant misrepresentation of what a source says in order to push a POV (like a so-called "Arab victory" during a so-called "second phase" of the campaign that Shapur II mounted against Arabs) are legit here, at ANI. If you are really interested by this matter, go ahead and dig a little bit to find where exactly Jawad Ali (the source cited by R3BOI) says that Arab tribes defeated Shapur II's forces during the camapign led by the latter ... This is only one example among many others.---Wikaviani(talk)(contribs)21:44, 9 December 2025 (UTC)[reply]
    If your argument isGo ahead and dig a little bit then you don't have an argument, plain and simple. The onus is on you to back up your own claims. —Jéské Courianov^_^vthreadscritiques21:55, 9 December 2025 (UTC)[reply]
    This was a pretty strange comment for the least, I cannot read the source for you. Read what the source says (in Arabic, so that I used a translator to understand what it says) and you will get me.---Wikaviani(talk)(contribs)22:03, 9 December 2025 (UTC)[reply]
    I'm also weirded out by how much onus is put on other users to prove that R3YBOI is correctly translating Arabic. This is the EN Wiki and prefersWP:NONENG sources anyways. In cases where the sources are primarily in Arabic or Arabic sources are particularly more valuable for providing insight or reliability, this could perhaps be understandable, but neither was the case atBattle of Talas where R3YBOl initially based their entire argument off ofArabic sources. Moreover, themain purpose when you look at the statements which they wish toinclude are simply aggrandizement and puffery for the Arab side rather than correctly representing a perspective according toWP:NEUTRAL. They are not abovemisrepresenting andremoving pre-existing sourced statements to do that either. So when that was pointed pout, they started tocitation stack English sources, many of which are subject to obvious problems likeWP:AGEMATTERS as well as a slew ofother problems, including only briefly mentioning the subject article, covering it in the most surface level way possible. I would also argue that many of these English sources written from the Arabic Islamic perspective will have some bias in that direction and R3YBOI habituallychooses to take those statements provided by these sources at face value and privileges them over other sources, which is a problem.Qiushufang (talk)01:56, 10 December 2025 (UTC)[reply]
    Edits like these ones where R3YBOI completely wisrepresents what the source says, The diff you provided was my first time citing sources ever and I wasn't familiar with doing that which I don't know how is that supposed to be an argument against me. In the beginning of my career in editing, before knowing about the difference of primary and secondary sources, I used websites such asAl-Maktaba al-Shamela to take sources and cite them (I later managed to find out that Shamela's books are composed mostly of primary sources and rarely any secondary reliable sources are available) I didn't misrepresent any source. I just cited according to what the source said, which you and I discussed *Jawad Ali*. (Jawad Ali cited al tabari's claim where the arabian tribes fought shapur II 38 years after his campaign against them. months after our discussion, I found out myself that different historians dismissed Tabari's claims and some of them called it dubious).R3YBOl(🌲)22:29, 9 December 2025 (UTC)[reply]

    Harassment and vandalism

    [edit]

    Favre1fan93 (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log)
    Gonnym (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log)
    DMacks (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log)
    To prevent a lot of back/forward dicussion, I point to:User talk:rsjaffe#Harassment and vandalism. There was a six hour editing war between the three users and myself while I was trying to archive my talk page.Included threats from the respective users.
    Sindsuser:rsjaffe told me to bring this toWP:ANI (see the discussion) I ask you to intervene. subst:ANI will be placed on the users talk pages. Thank you for reading.Harold Foppele (talk)18:58, 9 December 2025 (UTC)[reply]

    You edited another person's comment, cut half of it up and left part of it (and in the beginning also attributed it to two editors (seethis version). You do notWP:OWN your talk page and you cannot edit other people's comments perWP:TALKNO, which I told you. You are allowed to remove the complete discussion altogether, but not edit it.Gonnym (talk)19:05, 9 December 2025 (UTC)[reply]
    To clarify what I told @Harold Foppele, here is it in whole:I'm not seeing harassment. The comment about removing parts of other people's comments is referring to the policy about what you can and can't do with your talk page. If you are unhappy with how they discussed things with you, you should discuss this with them directly--such as on their talk page or yours. If, after that, you still feel there is ongoing harassment, you can refer the issue toWP:ANI, but that could backfire on you if others agree that you weren't being harassed. — rsjaffe 🗣️19:11, 9 December 2025 (UTC)[reply]
    If you paid attention you would have seen that I was busy archiving the page. But it took SIX hours berofre you stopped. The three of you worked as a team.Harold Foppele (talk)19:18, 9 December 2025 (UTC)[reply]
    The edited comment is still there.Gonnym (talk)19:22, 9 December 2025 (UTC)[reply]
    What comment are you talking about?Harold Foppele (talk)19:25, 9 December 2025 (UTC)[reply]
    The text at the start of the page which reads:
    Since you have made at least 10 edits over more than four days, you can now create articles yourself without posting a request. However, you may continue submitting work to Articles for creation if you prefer.If you have any questions, you are welcome to ask at the help desk.Thanks again, and happy editing! Bryan MacKinnon (talk) 06:06, 8 September 2025 (UTC)
    is part of the comment which looked originally likethis by Bryanmackinnon. You cannot edit their comment. --Gonnym (talk)19:46, 9 December 2025 (UTC)[reply]
    I see more than two hours elapsed between when you made an edit to your talkpage (12:51) and when Gonnym made their first edit to it (15:21), and they clearly explained in the edit-summary why they did it. You then called that "vandalism", despite the action not corresponding to anything onWP:VAND, but instead their summary specifically corresponding to something a different guideline instructs you not to do (though they did not link to that guideline until a later edit). My first edit related to the archiving work was 15 minutes after you had made any edits to the talkpage and to be more specific about one certain detail of your action that was problematic (given Gonnym had already stated the problem with your action, I merely stated that I was trying to fix it in a different way, hoping it might be more palatable to your desire to remove some chunks). That timeline does not seem like others were interfering in an on-going multi-edit session. The fact that several individuals recognized your edits were against standards and tried to get you back on track does not make us a "team".DMacks (talk)19:39, 9 December 2025 (UTC)[reply]
    A lot of assumptions of bad faith from Harold Foppele here. Reading the page history, it's quite clear that all the disruption onUser talk:Harold Foppele is coming from Harold Foppele, who ignores all the information supplied to them by the three users they list. There should perhaps be a boomerang... but first I will ask Harold Foppele: did youever read the page history? If not, why not? And if you did read it, why did you ignore all the information in its edit summaries, including from an admin (User:DMacks)? If you can give reasonable answers to these questions, I will recommend closure of this thread; but if you can't, I'm afraid I must recommend a boomerang.Bishonen |tålk20:25, 9 December 2025 (UTC).[reply]
    PS, rsjaffe didn't "tell" you to bring it to ANI. After telling you they themselves weren't seeing harassment, they said "you can refer the issue to WP:ANI, but that could backfire on you if others agree that you weren't being harassed". That was a warning. It would have been smart to heed it.Bishonen |tålk20:32, 9 December 2025 (UTC).[reply]
    And the advice was to do something else before even thinking about going to ANI, which at least as it pertains to me does not appear to have happened.DMacks (talk)21:03, 9 December 2025 (UTC)[reply]
    @Bishonen I looked up as many relevant items that i could find and I add them in times order:
    #1 Revision as of 15:44, 11 September 2025
    #2 Revision as of 13:46, 2 October 2025
    #3 Revision as of 19:09, 2 October 2025
    #4 Revision as of 05:41, 7 October 2025
    #5 Latest revision as of 22:38, 8 December 2025
    curprev 17:39, 8 December 2025 DMacks talk contribs 4,472 bytes −23 →top: remove bogus signature (I think this is what User:Gonnym was seeing?) undothank Tag: Reverted

    Is this correct? So the whole issue was that the top part of an (AfC?) template was lost during editing. I actually have a few questions:
    * How diduser:Gonnym end up in my talk page, I'm probably the least important editor at Wilipedia.
    * Why couldn’t he simply point the problem out to me?
    * Why did a second editor step in? Did the first call the second?
    * Why is the remark of 17:39 fromUser:DMacks : →top: remove bogus signature (I think this is what User:Gonnym was seeing?)

    At the top there was this:User:Rambley you can still find that in archive. So it seems thatUser:DMacks was also confused. And than everyone wonders why I got confused.
    I left my talk page unchanged. The missing top is in the Archive page, and after the smoke clears I'll restore it back to my talk page. The page looks even better then. I hope I made clear what i ment. I’m curious about the answers. ThanksHarold Foppele (talk)23:20, 9 December 2025 (UTC)[reply]
    So,User:Frost told you in September that your blanking of the pageWikipedia:Articles for deletion/Open-system formulations in quantum computing., an AfD for a page written by you, was against Wikipedia's principles. Unpromisingly, you replied "STOP INTERFERING", in the first diff you provide above. Now, Wikipedia is a place where people constantly "interfere", in the sense of telling (especially new) users when they violate our policies and guidelines. You are obviously deeply uncomfortable with this, but it's how things are done here. I see a number of people already telling you this on your page: "sorry but you are fundamentally not understanding what Wikipedia is for, what Wikipedia articles are about and what they are not", "Long-term agenda inconsistent with building an encyclopedia", "Your approach to editing is simply not aligned with Wikipedia", "Wikipedia is not a place to present new ideas, your own thinking or any similar analysis of an issue or problem. Only material that has already been presented and supported by multiple, independent sources is allowed." I don't understand why you are offering the other diffs above (the latest one isn't even from your talkpage, but from its archive) — I don't know what they're supposed to illustrate.
    For the questions in your post, I don't know how Gonnym found your page. People read around, and follow links to pages that interest them. Gonnym'svery first post on your page restores a comment fromUser:Bryanmackinnon andexplains why in the edit summary. Is there anything in that edit summary that you don't understand, or why do you make such an intemperate reply, reverting Gonnym and accusing them of vandalism? I simply don't understand it. Gonnymmakes another attempt to restore the full comment, with anextremely clear explanatory edit summary:You are not allowed to edit other people's comments, seeWP:TPNO. Since you want part of the comment, I'm restoring the full comment. Do not remove parts of it again. There's even a reference to a guideline! And yourevert them even more intemperately. These actions of yours are the main reason why I asked you above if you have even read the page history (including Gonnym's edit summaries). It still looks like you haven't. Shrug. I'm afraid I must agree with the several users on your page who say, in frustration, things like "Your approach to editing is simply not aligned with Wikipedia". Why do you respond to Gonnym with tantrums instead of taking what they say on board? Why do you keep responding to all attempts to explain with "Stop editing my user page" — not just Gonnym but also DMacks, an admin? Why do you revert everybody and accuse them of "vandalism"? (Here's your revert of Favre1fan93, who has made the same point as Gonnym.) I'm sorry, but after all the attempts by others to explain, it looks to me like you're not a good fit for Wikipedia. If you change your attitude, you still could be, but it's not looking promising.Bishonen |tålk06:12, 10 December 2025 (UTC).[reply]

    おはようございます。@Bishonen I see that you are +sysop for over 20 years, that you have been blocked 3 times and that you are Japanese. I am here for 11 years, blocked 1 time (current) and have been to Tokyo a few times. There I learned the true meaning of politeness. Anyway, I find it regrettable that you do not letGonnym speak for himself and bring up matters in this discussion that have nothing to do with it. The incident with the “blank page” arose because I, being fed up with the discussion, decided to delete the article. That was a mistake, albeit unintentional. When the page was suddenly restored, I became irritated. It was only afterwards that I read that this was not the intended action.
    I propose that my questions, which are still open and which you have not addressed, be answered. ReadingDMacks comment, I now understand that he did not understand it either, but you overlook this.
    My point is still valid: Why couldn’tGonnym simply have made me aware of it, instead of editing the page? In fact, he changed my edit. I would still like a response from the parties involved to my questions. In my view, the questions are legitimate.
    I look forward to your reply.Kind regards, じゃねHarold Foppele (talk)08:07, 10 December 2025 (UTC)[reply]
    To answer some of the questions. Your page appeared on a list of pages withWP:Lint errors. Regarding the questionwhy couldn’t Gonnym simply have made me aware of it, instead of editing the page?, you know how they say, "hindsight is 20/20"?, well you've still not corrected your improper editing ofsomeone else's comment on your page, even though I'm pretty sure I myself have said so already 5 times, including here in this discussion.Gonnym (talk)08:25, 10 December 2025 (UTC)[reply]
    Your answer makes clear that you did not read my text. QuoteI left my talk page unchanged. The missing top is in the Archive page, and after the smoke clears I'll restore it back to my talk page., so, after the discussion is closed, I restore it. "hindsight is 20/20?" has nothing to do with it. Simply point the user to it and at the same time educate a user about theWP:lint. Some of them might never have heard of it. I like to point to:Wikipedia:Talk page guidelinesIt is not necessary to bring talk pages to publishing standards, so there is no need to copy edit others' posts. Doing so can be irritating.Harold Foppele (talk)09:01, 10 December 2025 (UTC)[reply]
    I understand that you need me to be literal, what I meant by "hindsight is 20/20?, well [...]" is that in this scenario, I don't believe that even if I would have posted a talk page massage it would have helped. Lets just recap, after all the information you got, from me, from at least two admins, from other editors. With links to several talk page guidelines, includingWP:OWN andWP:TPO, you've still left the problematic comment.and after the smoke clears I'll restore it back to my talk page - no, do it now.It is not yours to edit and decide when to restore. You should have never done it the first place. And finally, even now when I gave you a link toWP:Linter which is completely irrelevant to this discussion, you try and wikilayer and sayIt is not necessary to bring talk pages to publishing standards, so there is no need to copy edit others' posts. Doing so can be irritating (in all bold font), when there are multiple discussions about lint fixing in talk pages. I understand you might want those links also, but I'm really sorry, but my time is precious and I'm not here to educate you anymore. Please restore or remove the edited comment already.Gonnym (talk)10:53, 10 December 2025 (UTC)[reply]
    I look very much forward to your explanation as to what in the merry hell Bishonen's length of tenure as an admin, her block log or her ethnicity has to do with anything here. Do you truly think, Harold Foppele, that irrelevantad hominem attacks help your cause in the least degree? Ravenswing14:10, 10 December 2025 (UTC)[reply]
    What in the merry hell? As far as I know, its he not she. Abusive ad hominem? To my opinion no one is attacked. <besides me maybe> ? It should be a discussion.Harold Foppele (talk)16:09, 10 December 2025 (UTC)[reply]
    Don't put words in my mouth or assume motive to my actions. At the time I tried to help clean up your small mistake, the talkpage looked likethis. The first section is (part of) a message from Bryan MacKinnon, as signed by him. But then there is a signature from Rambley, a remnant from when you removed his message but not the sig of it. That's obviously a minor problem, but it's obviously a falsification of the record to indicate that Rambley signed Bryan's message. So I simply removed the stray sig.DMacks (talk)16:33, 10 December 2025 (UTC)[reply]
    The signature I put there as a reminder. Nothing else. There was no other text needed. Indeed it was a small mistake. Blewn out of proportions. What I copied was your own text and nothing else.Harold Foppele (talk)16:54, 10 December 2025 (UTC)[reply]


    Outdent Aquote talk pagemassageunquote as you wrote would be so much nicer, and would ofcourse have helped. Multiple discussions about lint fixing in talk pages, i never saw one. You assume that a simple user knows and read them. In the 11 years that I'm at Wikipedia I never saw them. No, your precious time is not to educate anyone. I consider my talk page frozen, so that we dont have a moving target, until a consensus is reached, I assume that will be done by @Bishonen. I hope the remaining rwo questions also receive an answer.Harold Foppele (talk)11:31, 10 December 2025 (UTC)[reply]

    • After skimming and reading the diffs of this discussion, by summing it up, it appears that Harold Foppele can't distinguish fromwhatis vandalism, andwhat isnot vandalism, and with ownership issues on their talk page, and has confused their own talk page for their user page, seeing they have inappropriately accused of vandalism, such as the diffs that were also provided above:[41],[42],[43], and in the title of this thread, and inrsjaffe's talk page, and have evidence-free accused the 3 reported users of teaming and harrassing, which areaspersions and sets a bad light for the OP. I recommend a (lenient) boomerang at this point, seeingthey don't seem to listen to advice, and hasn't provided diffs for actual misconduct of the three reported users. AndIncluded threats from the respective users is without evidence from the OP.Codename ADtalk16:42, 10 December 2025 (UTC)[reply]

    Sinds the only way that I can explain my irritation is to point tothis WV section It describes a three person, long action ending in the statement byLdm1954:

    I have decided that I cannot ask professional physicists to repair pages on wikiversity, so I amwithdrawing my block request. You can contact me on Wikipedia if you want to know more; I will not respond on wikiversity.

    Since, to my feeling, what happened here on WP was more or less the same kind of action, I reacted the way I did. However, the three Wikipedians involved in the edit war on WP seem to have acted in good faith, as it looks now. In that case, I can only apologize for the misunderstanding, and by explaining it, perhaps gain some understanding in return. Yet I still stand by my remark that a simple message on my talk page would have prevented a lot of problems.I hope this can close the discussion.Harold Foppele (talk)19:20, 10 December 2025 (UTC)[reply]
    Not sure I understand the reference to the thread at Wikiversity which, if you look it up, ends with an unsigned and obscure comment. But I do see above an apology from Harold Foppele to the three people he has repeatedly and unreasonably accused of harassment and vandalism. That's good. Perhaps this thread can be closed? Harold Foppele wasblocked from page creation six days ago, a strong restriction which has probably affected his temper, and which may be sufficient in itself. What do the people most affected,Favre1fan93,Gonnym, andDMacks, think?Bishonen |tålk10:06, 11 December 2025 (UTC).[reply]
    Allow me to give some clarification:Ldm1954 created the unsigned and obscure comment.See this created Revision as of 04:11, 7 December 2025 it is not something I invented. So that event was more or less the same as what seemed to be happening in the present case.Harold Foppele (talk)11:02, 11 December 2025 (UTC)[reply]
    I'm fine letting this matter drop, with apology accepted as it pertains to me.DMacks (talk)12:47, 11 December 2025 (UTC)[reply]
    I'm in full support ofCodename AD's assessment above and their recommendation. -Favre1fan93 (talk)14:39, 11 December 2025 (UTC)[reply]
    Before I voted on an AfD of a page that @Harold Foppele created here on WP, which I suspected was generated with anWP:LLM because it was entirely unscientific nonsense that had nothing to do with the citations he was using, I wanted to see if there were other such issues. That led me to WV, where I noted the same such issue. I brought it to the attention of the other editors dealing with the AfD and the page creation ban, seeking to understand if something could be done cross-wiki. HF then proceeded to repeatedly accuse Ldm and I of being the same person, or of engaging in some kind of conspiracy against him. Ldm ultimately decided that WV was in need ofWP:TNT so we abandoned trying to address the AI-generated disinformation that HF was creating there. If anything, his behavior on WV and here should give a pretty clear indication of his pattern of editing and conduct toward other users in all future reports of him or by him.Revolving Doormat (talk)02:33, 14 December 2025 (UTC)[reply]

    I shall no longer take part in this discussion. The fact that you show up in this discussion in the same way as you did at WV speaks for itself.Harold Foppele (talk)09:32, 14 December 2025 (UTC)[reply]

    HF, I was looking for something and it led me here, and I opted to comment because once again, you are castingWP:Aspersions upon myself, Ldm, and some third party:It describes a three person, long action ending in the statement by Ldm1954. The fact that you didn't ping me in this discussion despite doing so is quite emblematic of your behavior cross-wiki.Revolving Doormat (talk)09:47, 14 December 2025 (UTC)[reply]

    WP:NOTHERE, begging for restoration of fancruft edits

    [edit]

    I'm in a bit of debate with another "editor",User:Themus3600, onTalk:Royal Rumble match as I removed numerous fancruft edits onRoyal Rumble match that were obviously against Wikipedia policy.

    I use the term "editor" very loosely, as the entire contributions of this user has been begging me specifically to restore them in quite a rude manner, as you can see if you take one glance at the user'scontributions page

    ObviouslyWP:NOTHERE,WP:UNCIVIL, and apersonal attack as I was hilariously referred to as "autism".Lemonademan22 (talk)00:25, 10 December 2025 (UTC)[reply]

    I never said you had autism i was talking about me~2025-39474-96 (talk)00:27, 10 December 2025 (UTC)[reply]
    @Lemonademan22 When placing a report at ANI, it's important you provide specific diffs showing the problematic behaviour. Admins don't want to trawl through a reported editor's contribution history to try to find what you're complaining about.(Non-administrator comment)Athanelar (talk)01:07, 10 December 2025 (UTC)[reply]
    Hi i did nothing wrong i never called him autistic i was talking about myself and he was rude to me 1stThemus3600 (talk)01:15, 10 December 2025 (UTC)[reply]
    Yes, you've said that multiple times, including directly below here. Don't worry, people will see that and take it into account, there's no need to keep repeating yourself.Athanelar (talk)01:16, 10 December 2025 (UTC)[reply]
    Thank you this is making me very upset. I'm sorry for repeating myselfThemus3600 (talk)01:18, 10 December 2025 (UTC)[reply]
    There's no need to apologise. Now that the matter is here, admins and uninvolved editors will look at the whole situation from the outside and will be able to clarify things. I understand wanting to explain yourself, and for what it's worth, I absolutely think Lemonademan's conduct with you was inappropriate.Athanelar (talk)01:28, 10 December 2025 (UTC)[reply]
    My conduct? I'm here to BUILD an encyclopedia, not harass other editors over bringing some fancruft stuff back that is completely opposite to Wikipedia and what it stands for. I'm the one making a difference and contributing my time and energy into my preferred projects, this user's whole existence on Wikipedia is dedicated to asking me to restore a load of edits that go against Wikipedia!Lemonademan22 (talk)17:22, 10 December 2025 (UTC)[reply]
    I'll direct you to'Being right isn't enough.' Civility is mandatory even if you have the 'high ground' in a debate.Athanelar (talk)17:26, 10 December 2025 (UTC)[reply]
    @Athanelar You're right, I shouldn't have been this blunt.Lemonademan22 (talk)13:03, 13 December 2025 (UTC)[reply]
    The way you spoke to me its not on and you accused me of callling you autistic which i never did. I asked a simple thing and you got rude with me.Themus3600 (talk)17:27, 10 December 2025 (UTC)[reply]
    @Themus3600 In the interest of not turning this ANI thread into another venue of argument between you and @Lemonademan22, I would advise you refrain from responding to them here (and the same goes for you, Lemonademan); we already have all the information on the situation, there's no need for the two of you to repeat the same argument here. Let uninvolved editors settle the matter.Athanelar (talk)17:30, 10 December 2025 (UTC)[reply]
    Im sorry wont happen againThemus3600 (talk)17:34, 10 December 2025 (UTC)[reply]
    No need to apologise, you didn't do something 'wrong,' I'm just trying to keep the discussion here on track.Athanelar (talk)17:38, 10 December 2025 (UTC)[reply]
    Also @Lemonademan22 I just looked at the page history for the page you are referring to and it appears multiple editors have tried to do an identical edit and you just revert it, so seemingly multiple editors agree that these things should be changed, but you revert it back, so it's borderline edit warring/page ownership.SuperCode111 (talk)01:20, 10 December 2025 (UTC)[reply]
    @Lemonademan22 After looking at your talk page, it is clear that you have caused incidents similar to this in the past...
    User Talk:Lemonademan22#February 2025
    User Talk:Lemonademan22#May 2025
    and this one, which is also aboutWP:FANCRUFT and is a very similar situation; reverting despite community consensus against you...
    User Talk:Lemonademan22#Slow-mo edit wars
    and your current edits look like a slow mo edit war as well...SuperCode111 (talk)01:52, 10 December 2025 (UTC)[reply]
    All times have been completely different topics, articles, and contexts. I'm just very passionate about the project.Lemonademan22 (talk)17:25, 10 December 2025 (UTC)[reply]

    A lie

    [edit]

    Hi i just want to clear something about a user @Lemonademan22‬ i was never rude to him he was rude to me i just asked him to bring some stats back and he accused me of being rude to him. Then i mentioned i had autism and he thought i meant he did which i never said as i was referring to myself. I was never harassing him.Themus3600 (talk)00:56, 10 December 2025 (UTC)[reply]

    (Non-administrator comment)WP:AGF on this user as the reported commentdoes look like what themus claims is true, but the confusing English ended up offending Lemonademan22. I am raisingWP:BITE concerns becausethis comment against a newcomer with ~10 edits at the time is just plain hostile. There are definitely better, friendlier ways to explainWP:FANCRUFT to a newcomer.AlphaBetaGamma (Talk/report any mistakes here)01:23, 10 December 2025 (UTC)[reply]
    I concur entirely. The misunderstanding is perfectly understandable, but Lemonademan has made 0 attempts to be civil or patient with this obviously very new (and clearly very upset) editor.Athanelar (talk)01:27, 10 December 2025 (UTC)[reply]
    Thank you i appreciate your kind wordsThemus3600 (talk)01:30, 10 December 2025 (UTC)[reply]
    "bring them back stop deleting them" (my own talk page)
    "Bring back the stats for the royal rumble matches like whos got th mkst eliminations and who entered the most. Someone delted it"
    "well bring it back"
    "They were not against policy they 100 percent correct. And stop lying about 2018 they have been there way longer then that you cant just get rid of it. And you dont even work for Wikipedia so stop arguing with me and being rude with someone that is autismm."
    I probably shouldn't of fought fire with fire, but I think we were both pretty uncivil. In hindsight at least. Though, I think using a serious mental disorder such as autism to win a dispute is quite disgusting, or at the very least, ethically questionable.
    I will accept I should get consensus, though no one is willing to offer any consensus, and since my edits reflect Wikipedia policy I figured I was in the right in this case.Lemonademan22 (talk)17:35, 10 December 2025 (UTC)[reply]
    This is a new editor who will naturally already have no understanding of Wikipedia procedure, compounded by their autism which they have disclosed.
    You were not necessarily obligated to get consensus, as where material is disputed theonus to gain consensus is on the person seeking to include or restore material, not the person seeking to remove it. In any case, ANI is not interested in litigating the content dispute here, only the conduct issues; both the alleged misconduct on Themus' part, and the misconduct others have alleged against you.
    Your very first response to Themus (who at the time was commenting on a TA) was to call the stats unencyclopedic fancruft unfit for Wikipedia without really explaining 'why,' and when they again pushed for their reinclusion, your response was;
    the "stats" as you call them were garbage dopamine addicting junk that are completely opposite as to the encyclopedic nature of Wikipedia, go look on a fan wiki for them, there's plenty out there, Wikipedia is not the place for such unencyclopedic content
    To which they said, abridged;The stats were facts[...]they were there for 20 years[...]people like reading then
    The whole thing could've been solved at this point if you had explained that whether the stats were true or old or popular had nothing to do with whether they're encyclopedic, and that they're not fit for inclusion based on x policy or y guideline, instead you again only repeated that they'rea load of garbage unencylopedic nonsense that are against Wikipedia's policy (an entirely useless statement for someone new to Wikipedia who has no idea what our policies are or what makes something 'unencyclopedic') and on top of that you sprinkled in an OWNy attitude withand they will not be returning.
    Now, I'm not an admin, but I'm somewhat confident in saying that this whole thing can be amicably resolved and closed without any need for admin intervention if you can acknowledge where your conduct went wrong here and that you won't do it again; after which point I think Themus will be suitably satisfied in order to do the same.(Non-administrator comment)Athanelar (talk)17:47, 10 December 2025 (UTC)[reply]
    Yes, on reflection, speaking in wikivoice to someone not familiar with Wikipedia standards is quite useless, and I should have done that. I think the autism part (I myself am on the spectrum; a fact I don't paticularly love disclosing) is not important as compentancy is a must on Wikipedia, perWP:COMPETENCE, and if one's mental capacity cannot develop compentant editing standards, what's the alternative? Allow it? That's surely counter intuitive.
    I'm sure my contemporary meant no harm, but I was just a bit ticked off with the blunt begging, at least that's how I percieved it. And when I said"and they will not be returning." yes I should obtain consensus, but my argument was that since it's unencyclopedic, why should they come back? If that makes sense.Lemonademan22 (talk)13:09, 13 December 2025 (UTC)[reply]

    Boomerang back to OP?

    [edit]

    I'm not sure how big theWP:BOOMERANG is, but I find no merit in anyone sanctioning Themus3600 unless they continue fancruft-related problems (which I hope will never continue based on their response). In fact, Supercode111 seems to have discovered a pattern of other issues in 2025. (At least 3 edit warring-related issues per Supercode111's diffs above)AlphaBetaGamma (Talk/report any mistakes here)03:53, 10 December 2025 (UTC)[reply]

    I definitely don't agree with Lemonademan22's conduct throughout this. They have shown signs ofWP:BITE andWP:OWN. However, this page has so many irrelevant stats, lack of citations, and several users trying to add FANCRUFT to it that I'm surprised it isn't at least semi-protected to prevent further disruption. Might I recommend that route, so that users can suggest stats with relevant sources rather than obvious edit wars that have persisted since May 2025?Conyo14 (talk)23:25, 10 December 2025 (UTC)[reply]
    If you want to suggest that the page be protected, the venue for that isWP:RPP/IAthanelar (talk)23:28, 10 December 2025 (UTC)[reply]
    I am aware, but would like other's thoughts.Conyo14 (talk)23:30, 10 December 2025 (UTC)[reply]
    Sent to RfPP.AlphaBetaGamma (Talk/report any mistakes here)02:33, 11 December 2025 (UTC)[reply]
    This report is going nowhere positive for anyone, and a semiprot will filter out future fancrufts (hopefully). I'm sure someone uninvolved will close this down when the protection happens. If Lemonademan repeats this again and gets taped to an ANI thread in the future, please do not ping me.AlphaBetaGamma (Talk/report any mistakes here)03:11, 11 December 2025 (UTC)[reply]

    Ignoring consensus - disruptive editing

    [edit]
    Editors can continue to discuss this issue atTalk:Cat food.voorts (talk/contributions)00:19, 14 December 2025 (UTC)[reply]

    The following discussion is closed.Please do not modify it. No further edits should be made to this discussion.



    User:Traumnovelle (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log)

    Editor @Traumnovelle continues to revert changes despite consensus reached on the talk page by 3 (if not 4) others, and makes clear on their talk page that they would continue.

    This is about a change on the Cat Food article. After the initial revert (which is fine) this was raised onTalk:Cat Food (note that the current talk page has TurboSuperA+'s comment in the wrong spot for some reason, but with the correct timestamp)

    Edits/Reverts

    • Revert against two editors' views on the talk page[44]
    • Revert against three editors[45]
    • Re-added slightly altered content to other part of the page, against four editors[46]
    • Reverted compromise attempt including citation needed and partial removal instead of full[47]
    • Indicates they will continue to revert on their talk page[48]

    The consensus is that the particular claims should be removed or re-sourced, because the current citation used refers to dogs, which is not appropriate to make claims about cats.— Precedingunsigned comment added bySklabb (talkcontribs)22:16, 11 December 2025 (UTC)[reply]

    I think you meant to linkTalk:Cat food.voorts (talk/contributions)22:29, 11 December 2025 (UTC)[reply]
    @Traumnovelle, I really don't want to block you for slow-motion edit warring over cat food of all things. I would tell you to go seek consensus for your edits, but after reading the article talk page discussion, it appears that you are in fact incorrect about what these sources say. Please drop the stick.voorts (talk/contributions)22:35, 11 December 2025 (UTC)[reply]
    I see this as a complicated source issue for which @Traumnovelle is in the minority. The source is ambiguous and there are some source reliability concerns. If @Traumnovelle wants to continue advocating for their view, the best thing to do is to look at the options available atWP:DR. Warring on the page is not an acceptable way of solving this: we provide formal processes to handle complicated disagreements like this one. — rsjaffe 🗣️00:37, 12 December 2025 (UTC)[reply]
    I did not say I would revert again, I just said I was not okay with removing the content after Sklabb said that he assumed I was okay/approved of the change due to my lack of reply.
    I contacted the author of the chapter and he confirmed the chapter is about small animals generally not specifically dogs. I am willing to forward said email to the Arbitration Committee if anyone wishes for an independent party to verify this claim.Traumnovelle (talk)06:17, 12 December 2025 (UTC)[reply]
    Ok, that leaves room for a simple solution to all this. Do I understand correctly that you will not revert again if I make the change according to the consensus?Sklabb (talk)22:33, 12 December 2025 (UTC)[reply]
    The source in question is page 196 in the bookApplied Veterinary Clinical Nutrition. The chapter is "Nutritional Management of Orthopedic Diseases" by Herman Hazewinkel. Traumnovelle is correct that this chapter contains coverage of both cats and dogs, however, if you read pages 195 and 196 anyone can see that the material cited (including the puppies chart on page 195) and the references on page 196 are on dogs specifically. I have uploaded a photograph of the content in question (page 196) so everyone can see it,here. As you can see the page is talking about dogs (beagles, miniature poodles, great Danes, growing dogs etc), there is not asingle mention of cats in the text on page 196. This can easily be verified if you check out the sources in the bibliography. For example, the Mack and Kienzle paper is on Bernese Mountain Dog-puppies[49], Great Danes[50] and Great Dane pups[51]. Traumnovelle has argued on the talk-page that this page covers both cats and dogs, then why not mention cats? Why only dogs? If the page is about cats, then why is Hazewinkel citing studies on Bernese Mountain Dog-puppies and Great Danes? Why did he not cite specific studies on cats for his text?
    These sources are the inspiration of the material that Traumnovelle added to the article about calcium deficiency. As stated on the talk-page this to me looks likeWP:OR as the sources Hazewinkel was using were on dogs and there is no specific mention of cats and calcium deficiency. As for contacting Herman Hazewinkel; I think upon investigation he would admit that pages 195 and 196 of his chapter are on dogs. It is not in question that his chapter is about small animals generally so it would be a waste of time to email the Arbitration Committee about the chapter. We are not disputing or questioning the chapter, we are only disputing using page 196 for cats.Veg Historian (talk)12:35, 13 December 2025 (UTC)[reply]
    Linking to a copyright violation is not helpful when the material can be viewed via the Wikipedia Library.Traumnovelle (talk)19:30, 13 December 2025 (UTC)[reply]
    FYI @TraumnovelleSklabb (talk)15:09, 13 December 2025 (UTC)[reply]
    The discussion above is closed.Please do not modify it. No further edits should be made to this discussion.

    User CounterpointStitch

    [edit]
    Seems like this has been addressed. Editors are reminded to work together in good faith to seek consensus before escalating disputes to ANI.voorts (talk/contributions)00:18, 14 December 2025 (UTC)[reply]

    The following discussion is closed.Please do not modify it. No further edits should be made to this discussion.


    CounterpointStitch is being disruptive onTrial of Michael Jackson,Michael Jackson, andFBI files on Michael Jackson. They're also being disruptive on the main Michael Jackson page talk page. Let us keep in mind that disruptive editing is not limited to just article articles but the talk page as well.

    So far, they have broken all of the following rules:

    1Is tendentious: continues editing an article or group of articles in pursuit of a certain point for an extended time despite opposition from other editors. Tendentious editors not only add material; some engage in disruptive deletions as well, e.g. repeatedly removing reliable sources posted by other editors. 2Is unwilling or unable to satisfy Wikipedia:Verifiability; fails to cite sources, cites unencyclopedic sources, misrepresents reliable sources, or performs original research. 3Engages in "disruptive cite-tagging"; adds unjustified{{citation needed}} or{{more citations needed}} tags to an article when the content tagged is already sourced; uses such tags to suggest that properly sourced article content is problematic. 4Fails to engage in consensus building:

    Arepeatedly disregards other editors' questions or requests for explanations concerning edits or objections to edits;
    Brepeatedly disregards other editors' explanations for their edits.

    5Fails to recognize, rejects, or ignores community input: resists moderation and/or requests for comment, continuing to edit in pursuit of a certain point despite an opposing consensus from impartial editors.

    Their account was created on 28 November 2025, and they immediatelytargeted Michael Jackson-related articles to push a point view (POV).Israell (talk)23:02, 11 December 2025 (UTC)[reply]

    You have not provided any diffs.voorts (talk/contributions)23:25, 11 December 2025 (UTC)[reply]
    @Voorts: Instances of:

    Removing sources and adding content without consensus being gained.[52]

    Adding citation to already sourced material.[53]

    Making up rules and starting a dispute resolution while an RFC is ongoing.[54]

    Israell (talk)23:48, 11 December 2025 (UTC)[reply]

    A reminder that Michael Jackson isa community-designated contentious topic. -The BushrangerOne ping only01:23, 12 December 2025 (UTC)[reply]
    Also... I’m also concerned that there may be ongoing canvassing efforts and this editor could be the result or the reason for this effort. Below you will find many examples of this canvassing.
    Here is a recent comment of canvassing for the ongoing RFC on Trial of Michael Jackson:[55].
    Other discussions about Wikipedia include taking over Wikipedia, and attacking editors who have been editing for years. Their behavior is similar in language to what is happening now.
    here
    here
    here
    here
    here
    here
    here
    here
    here
    here
    More complaints here, but about Grokipedia[56].Israell (talk)03:04, 12 December 2025 (UTC)[reply]
    (non admin comment) @Israell I have some points about the diffs you gave:
    Diff [390] directed to an error page.
    Diff [391] seemed to have removed a section that contained "by whom?", which I think could justify removing a section.
    For Diff [392] you wrote this wasAdding citation to already sourced material, and the source that was there says "<ref name="autogenerated1"/>", what does that mean? Also why is it wrong to add another citation to an already sourced material, which can make a claim stronger, especially around contentious topics?
    Wikieditor662 (talk)03:44, 12 December 2025 (UTC)[reply]
    @Wikieditor662: I've just verified all the diffs; I saw no error page.Israell (talk)03:56, 13 December 2025 (UTC)[reply]
    I checked and the error page is gone. But I still have these other points/questions that I posted for the first two diffs of the current version of your original message.Wikieditor662 (talk)21:57, 13 December 2025 (UTC)[reply]
    Unfortunately, I am not surprised to see this report. CounterpointStitch made a request atDRN (as was mentioned by the OP), atWikipedia:Dispute_resolution_noticeboard#Trial_of_Michael_Jackson. They had, two days earlier, started an RFC,[57] to remove the categoryCategory:False_allegations_of_sex_crimes from the article. It appears that there was then edit-warring over the category, and then CounterpointStitch opened the DRN. DRN does not handle a dispute that is also being considered by another noticeboard or another dispute resolution mechanism, including RFC. Opening a DRN when there already is an RFC in progress appears to beforum shopping. Perhaps CounterpointStitch was in a hurry and did not want to wait for the RFC to conclude, butin Wikipedia, there is no deadline. Maybe they can explain why they tried to replace the RFC with a DRN.Robert McClenon (talk)04:35, 12 December 2025 (UTC)[reply]
    They're a new editor. I wouldn't expect them to know the arcane rules of DRN before opening a request there. That RfC is also a shitshow, so I can see why someone would seek help elsewhere.voorts (talk/contributions)13:35, 12 December 2025 (UTC)[reply]
    I see that they are a new editor, and I don't expect them to know that they can't open a case at DRN. But I wasn't surprised to see this report come here toWP:ANI. They did make a mess by trying to use the RFC to remove the category from the article when the RFC still needed to run for another 28 or 29 days.Robert McClenon (talk)19:53, 12 December 2025 (UTC)[reply]
    I do have a question now. What is the proper procedure for deciding whether an article belongs in a category? Is an RFC the proper procedure for that? If so, I assume that it should be allowed to run for a month.Robert McClenon (talk)19:53, 12 December 2025 (UTC)[reply]
    RfCs can be used for any content dispute, including whether an article should be in a category. In this case, I think the RFC should be restarted with clear sections for !votes and discussion separated out and enforced.voorts (talk/contributions)22:41, 12 December 2025 (UTC)[reply]

    Restarting the RFC

    [edit]

    I think that I have restarted the RFC, as per the advice fromUser:Voorts, and will check in the near future to see if the text has changed in the lists of RFCs. Thank you,User:Voorts.Robert McClenon (talk)02:30, 13 December 2025 (UTC)[reply]

    It appears that my restarting of the RFC has been successful, and the revised wording of the question now appears in the lists of RFCs.Robert McClenon (talk)03:55, 13 December 2025 (UTC)[reply]
    Is there any other administrative or quasi-administrative action needed, or should this item be closed?Robert McClenon (talk)03:55, 13 December 2025 (UTC)[reply]
    Unrelated but i think Michael Jackson's pages should all get indefinite edit protection, we cannot allow them to stay open anymore as it's clear it becomes a target for edit warringNever17 (talk)07:10, 13 December 2025 (UTC)[reply]
    If you meanextended-confirmed protection, I agree. If you mean admin protection, I disagree. If you meansemiprotection, I agree but think it may be inadequate.Robert McClenon (talk)18:51, 13 December 2025 (UTC)[reply]
    I have ECP'dTrial of Michael Jackson underWP:GS/MJ for a week. I don't see sufficient disruption onFBI files on Michael Jackson orMichael Jackson to merit ECP, IMHO. -The BushrangerOne ping only19:28, 13 December 2025 (UTC)[reply]
    The discussion above is closed.Please do not modify it. No further edits should be made to this discussion.

    Temp account ~2025-31243-86 rapid submission of unsourced Drafts

    [edit]
    BLOCKED
    TA indefinitely blocked from draft space by Yamla. All draft creations have been deleted.(non-admin closure)Chess enjoyer (talk)05:04, 13 December 2025 (UTC)[reply]
    Block later upgraded to full indefinite by Toadspike.Chess enjoyer (talk)08:44, 16 December 2025 (UTC)[reply]

    The following discussion is closed.Please do not modify it. No further edits should be made to this discussion.


    Can we get a block on Draftspace for @~2025-31243-86 who in the span of thirty minutes as submitted 12 drafts for review via AfC, all unsourced.

    Since late November they have edited, likely via a shared IP, another 30 submitted drafts which are also all unsourced.qcne(talk)15:46, 12 December 2025 (UTC)[reply]

    12, and counting upwards rapidly!qcne(talk)15:48, 12 December 2025 (UTC)[reply]
    Done, as a regular admin action. Any admin is free to lift the block if convinced the nonsense will stop. --Yamla (talk)15:51, 12 December 2025 (UTC)[reply]
    I believe this is anLTA, and the drafts can be nuked under G5. –bradv15:58, 12 December 2025 (UTC)[reply]
    Cheers, with G5 them.qcne(talk)16:01, 12 December 2025 (UTC)[reply]
    I think I just got them. Spot checking for any I missedStarMississippi16:29, 12 December 2025 (UTC)[reply]
    The discussion above is closed.Please do not modify it. No further edits should be made to this discussion.

    Nikki Benz day of birth

    [edit]
    NOT THE PLACE FOR A POLICY CONVERSATION
    The issue on the article is resolved. Any editors interested in addressing or changing the policy should have that discussion in a more appropriate forum.StarMississippi13:38, 16 December 2025 (UTC)[reply]

    The following discussion is closed.Please do not modify it. No further edits should be made to this discussion.


    User @Sangdeboeuf has been condescending and authoritarian in his discussion on the talk page of Nikki Benz, regarding her day of birth. The titular subject has posted numerous times over the years (including 2025) on her official social media channels that her birthday is December 11. I tried numerous times to cite this in the article, but @Sangdeboeuf continues to revert and then bombard with excessive use of Wikipedia terminology, to promote arguments about "privacy" and protection of living persons, and to intimidate good faith edits that do not comply to a rigid system of rules. Please see talk page, for my counter arguments. In the end as I have said to the user, I know for a fact that December 11 is the birthdate, and that won't change, but to obstinately refuse its inclusion based on an attitude of superiority and rules that are thrown around to show authority is very disturbing to me. I am disappointed that there would be wikipedia editors that conduct themselves like this.~2025-39885-95 (talk)18:19, 12 December 2025 (UTC)[reply]

    WP:1AM dispute atNikki Benz (edit |talk |history |protect |delete |links |watch |logs |views) See the article history for the three separate users who have reverted the anonymous user. This user edit-warred repeatedly in violation ofWP:BLPRESTORE (diffdiffdiffdiffdiff) even after a warning (permalink), showing a complete disregard for WP'spresumption in favor of privacy for living subjects, including ridiculing the very idea of protecting the subject's privacy (diff). Not this user's first rodeo, judging by theirWP:CANVASSING on the article talk page (diff). TypicalWP:NOTHERE behavior IMO. —Sangdeboeuf (talk)18:34, 12 December 2025 (UTC)edited 19:04, 12 December 2025 (UTC)[reply]
    And again you use your condescending tone. The subject has publicly provided her birth date numerous times on verified social media, thus giving her consent.
    I don't need validation from this "court of justice" to know that the behaviour exhibited here is wrong, nonsensical, and authoritarian. Again sweet dreams to you at night, for having "protected the privacy" of this person. Bravo.~2025-39885-95 (talk)18:54, 12 December 2025 (UTC)[reply]
    This is a content dispute that is turning into a behavioral problem.Sangdeboeuf, there is a section of theBLP policy that can be found atWP:DOB that saysA verified social media account of an article subject saying about themselves something along the lines of "today is my 50th birthday" may fall under self-published sources for purposes of reporting a full date of birth. It may be usable if there is no reason to doubt it. What is the reason for doubt in this case?Cullen328 (talk)20:22, 12 December 2025 (UTC)[reply]
    Benz did not post her full date of birth (or birthday plus age) on eitherFacebook orInstagram. As I stated on the article talk page,Unless Benz has shared her full date of birth including the year, then putting all that info on Wikipedia only helps potential stalkers. Once again, this is aWP:1AM dispute, so go ahead and askBabysharkboss2 andPlasticwonder their reasons for reverting as well. —Sangdeboeuf (talk)20:42, 12 December 2025 (UTC)[reply]
    ButSangdeboeuf, you stated above that this was a privacy issue related to BLP policy. If the birthday is stated repeatedly in a verified social media account, thenthere is no privacy issue or BLP policy issue. You may argue that the birthday without year of birth is non-encyclopedic, but that is not a BLP policy issue. An argument built on an incorrect interpretation of policy is invalid. Are you willing to withdraw your assertion that there is a violation of BLP policy here?Cullen328 (talk)20:43, 12 December 2025 (UTC)[reply]
    How is there no privacy issue when the subject has notshared her full date of birth? And since when do admins decide whether an argument about content is correct or not? —Sangdeboeuf (talk)20:51, 12 December 2025 (UTC)[reply]
    Sangdeboeuf, I did not say that I am right because I am an administrator. I did not even mention that I am an administrator. I just expressed my informed opinion based on lots of BLP editing going back 16 years that your characterization of this as a BLP privacy policy issue is a gigantic stretch and that I disagree with it. I am asking you to do a more convincing job justifying your position.Cullen328 (talk)21:41, 12 December 2025 (UTC)[reply]
    We all have our opinions, but my objection to the material was still in good faith. Anonymous violatedWP:BLPRESTORE by re-adding it without consensus. —Sangdeboeuf (talk)22:49, 12 December 2025 (UTC)[reply]
    Your original objection was in good faith, yes. Your ongoing stonewalling is not. Yes, we've heard your opinion, several times over now. Rather more than that is needed to establish consensus on the issue. Ravenswing01:48, 13 December 2025 (UTC)[reply]
    Discussion is notWP:STONEWALLING. The burden to achieve consensus is on the person wishing toinclude the material. SeeWP:ONUS andWP:BLPRESTORE. —Sangdeboeuf (talk)08:49, 13 December 2025 (UTC)[reply]
    Apparently explicitly stating your birth date on literal social media isn't enough to stop it being a privacy issue when mentioned on Wikipedia. If there really is a violation of a policy here, it would beWP:V notWP:BLP. Also, admins can have opinions on disputes, but their arguements should be treated like any other editor. Their arguments usually aren't somehow on another level compared to non-admins.~2025-31733-18 (talk)21:00, 12 December 2025 (UTC)[reply]
    A birthday is not a birth date. —Sangdeboeuf (talk)22:42, 12 December 2025 (UTC)[reply]
    That seems pedantic? A birthday also a birthdate?~2025-31733-18 (talk)05:30, 13 December 2025 (UTC)[reply]
    Full date of birth for BLP purposes means the day, month, andyear. SeeWP:DOB. —Sangdeboeuf (talk)09:09, 13 December 2025 (UTC)[reply]
    Reading that I could only gander that this is a source issue not a BLPVIO issue in of itself?~2025-31733-18 (talk)10:48, 13 December 2025 (UTC)[reply]
    Maybe the temporary account user would get more support for their addition if someone asked the subject of the article on social media to include their year of birth in their next birthday post, and/or asked the subject if their are fine with the inclusion of that kind of information in the Wikipedia article on them.Nakonana (talk)10:57, 13 December 2025 (UTC)[reply]
    This is about your behavior, which has been subpar.~2025-40335-27 (talk)21:36, 12 December 2025 (UTC)[reply]
    Thank you for your input. I just cannot rationalize how putting "Benz was born on December 11" is controversial, when she states it herself.~2025-39885-95 (talk)20:52, 12 December 2025 (UTC)[reply]
    The discussion above is closed.Please do not modify it. No further edits should be made to this discussion.

    Disruptive editing by User:Sca

    [edit]

    User:Sca is engaging in persistent disruptive editing onWikipedia:Featured picture candidates. This includes tendentiously dismissing nominations as "promotional" and describinghistorically significant images as "old news".Here he engages in personal attacks and admits to "trolling" with tendentious comments.JJARichardson (talk)02:10, 13 December 2025 (UTC)[reply]

    @Sca was already indefinitely blocked fromWikipedia:In the news/Candidates for disruption. He is definitely being disruptive on the featured picture candidates, but due to the page by page nature of the featured picture candidates, it cannot be blocked by, for instance, blocking "Wikipedia:Featured picture candidates/*", which would be ideal. Therefore, I have blocked him from the Wikipedia namespace for 31 hours to stop the disruption. If disruption recurs, the next block could be significantly longer. — rsjaffe 🗣️03:14, 13 December 2025 (UTC)[reply]
    • I would support some sort of long-term block from FPC. This user is routinely disruptive in that area, as outlined by the opener, and I'm honestly surprised they weren't brought here earlier.EF504:42, 13 December 2025 (UTC)[reply]
    Note that, since @Sca cannot post here, he has posted aresponse on his user talk page. — rsjaffe 🗣️16:28, 13 December 2025 (UTC)[reply]
    In response to @Sca's appeal: the politicized personal attack made against a Russian-speaking user (calling him "comrade" in Ukrainian) is what prompted me to alert the admins. The disruptive and meritless objections to featured picture nominations as "old news" or "promotional", irrelevant to nomination criteria, has been going on for longer.JJARichardson (talk)17:15, 13 December 2025 (UTC)[reply]
    • Per JJARichardson above "has been going on for longer" . . . . I second that and support atopic ban from FPC. I was active at FPC from 2015 to early 2025. I and another editor:diff1diff2 had called for Sca's topic ban from FPC, but not formally in an actionable forum. Here is another editor expressing frustration:diff3. His jokes and comments can be frustrating and can easily be interpreted as trolling:diff4.Bammesk (talk)22:30, 13 December 2025 (UTC)[reply]

    Continued unsourced additions after continued warnings

    [edit]

    The following discussion is closed.Please do not modify it. No further edits should be made to this discussion.


    User:LeaveMeAlone12345, has continued adding unsourced speculation and unreliable sources toTiffany Stratton andMyles Borne. After me, and editorUser:NJZombie, have told them numerous times on theirtalk page about this matter and in edit summary.

    Tiffany Stratton -[58]

    Myles Borne -[59][60][61][62]

    Talk page -[63][64][65]Lemonademan22 (talk)13:02, 13 December 2025 (UTC)[reply]


    I mean, there's several other Wiki pages that use Instagram as a source. In Stratton's case, she deleted all videos and photos of Ludwig Kaiser. Kaiser has been seen holding hands with another woman in recent months. They clearly are not together. You don't need to be a genius to figure that out. My other solution was just to remove that they were dating altogether, because it's not an accurate statement. As for Myles Borne, he is dating Vaquer, so obviously he's atleast separated from his wife. Not everything needs to be a public statement.— Precedingunsigned comment added byLeaveMeAlone12345 (talkcontribs)13:28, 13 December 2025 (UTC)[reply]

    This is an encyclopedia, not TMZ. Thingsvery much do requirea statement of some sort. •a frantic turtle 🐢13:40, 13 December 2025 (UTC)[reply]
    But not every single page does have credible sources is my point. So why not just remove the personal life section for these two pages since there is so much back and forth? I'm not the only one reverting this edit. Also, no one goes to Wiki for factual information lol. Everyone knows anyone can edit and you have to actually research elsewhere.LeaveMeAlone12345 (talk)14:15, 13 December 2025 (UTC)[reply]
    Also can't the statement be - deleting all photos/memories of the relationship + posting photos of a new partner? It doesn't always have to be words.LeaveMeAlone12345 (talk)14:20, 13 December 2025 (UTC)[reply]
    The key phrase here is "figure that out". This shows that you are engaged inoriginal research. We don't do that here.
    What concerns me more is that your account is fairly new but within a couple of days you were editing in quite an experienced way, making requests for page protection reduction and usingTemplate:Cite web correctly, albeit with an inappropriate source. So, I have to ask, is this your first Wikipedia account? Does its name tell a story? Have you tried this before and had a frustrating experience? --DanielRigal (talk)13:43, 13 December 2025 (UTC)[reply]
    There's also the fact this is aWP:BLP issue, and adding tabloid gossip is a big no-no.
    This seems to have been ongoing for around a month, so I suspect aWP:CIR/WP:NOTHERE issue.Rambling Rambler (talk)14:19, 13 December 2025 (UTC)[reply]
    Again - the statement shouldn't have to be words.... I'm leaving the pages as is. I don't see the point in arguing this further.LeaveMeAlone12345 (talk)14:22, 13 December 2025 (UTC)[reply]
    Something doesn't have to be words, but it has to be something expressively saidby the source, not what you have chosen to interpret from the source.Rambling Rambler (talk)14:24, 13 December 2025 (UTC)[reply]
    Last question/comment - what if someone, doesn't make any public statement but it's clear they are not with an ex, and on Wiki it says "so and so has been dating so and so since whatever date" - do you leave that? No. That's false information. You may never get a public statement, so why keep it? Someone shouldn't have to make a statement, they may just want to move on and that's fine. By posting photos, consistently, and using certain language can be the statement.LeaveMeAlone12345 (talk)14:28, 13 December 2025 (UTC)[reply]
    We can rest assured that someone, somewhere, will publish something about a celebrity break-up at some point and we can then cite it. We are willing to wait for that as we're an encyclopedia, not The Hollywood Reporter. •a frantic turtle 🐢14:31, 13 December 2025 (UTC)[reply]
    and on Wiki it says "so and so has been dating so and so since whatever date" - do you leave that? No.
    The answer isyes. Wikipedia is led by reporting in reliable secondary sources and where appropriate primary sources.Wikipedia is not a newspaper.Rambling Rambler (talk)14:32, 13 December 2025 (UTC)[reply]
    that's not very good journalism. Since there's speculation, I'd just remove it. Not our business anyway to know who they're dating.LeaveMeAlone12345 (talk)14:37, 13 December 2025 (UTC)[reply]
    It doesn't matter if it's "good journalism" or not, as we're an encyclopedia, not a newspaper – a point that is proving surprisingly hard to get across to you. •a frantic turtle 🐢14:43, 13 December 2025 (UTC)[reply]
    Nope, not hard at all. Just trying to argue a different perspective that's not surprisingly hard for you to understand. Anyway, leaving the discussion here, as well as the pages now that misinformation can be here.LeaveMeAlone12345 (talk)14:46, 13 December 2025 (UTC)[reply]
    Let me direct you toWP:SYNTH. We are expressly forbidden from inferring conclusions based on information in separate sources. There is no room here for your interpretation of info in the sources. We write down what the sources say and only what the sources say.Athanelar (talk)16:18, 13 December 2025 (UTC)[reply]
    Got it. Thanks.LeaveMeAlone12345 (talk)16:21, 13 December 2025 (UTC)[reply]
    The username, no lol - plus is editing a page that difficult? I don't consider myself an experienced Wiki editor/contributor by any means.LeaveMeAlone12345 (talk)14:19, 13 December 2025 (UTC)[reply]
    Yes. We figured that one out for ourselves. Ravenswing17:32, 13 December 2025 (UTC)[reply]
    Suggest an indef onWP:RGW/WP:CIR grounds (resolved by SM's p-block)- From the reported account's own comments it's pretty clear they don't seem to understand what Wikipedia is for and believe we're in the business of speculating on the personal lives of celebs. I find it doubtful they'll improve given this basic inability to accept this after around a month of failing to appreciate this.Rambling Rambler (talk)14:46, 13 December 2025 (UTC)[reply]
    +1a frantic turtle 🐢14:49, 13 December 2025 (UTC)[reply]
    I'd prefer a regular indef, but if one isn't forthcoming, I don't see any way around this. This same behavior can be seen on birthdates they change, and if LeaveMeAlone is simply going to refuse to accept Wikipedia's sourcing policies, they have to be removed from mainspace at a minimum.CoffeeCrumbs (talk)15:11, 13 December 2025 (UTC)[reply]
    I'm not refusing...I'm just not editing anymore. It is what it is.LeaveMeAlone12345 (talk)15:12, 13 December 2025 (UTC)[reply]
    It wasn't quite clear exactlywhat you would be refraining from editing. The first priority is protecting the encyclopedia, and forWP:BLP articles, the scrutiny is the highest.CoffeeCrumbs (talk)17:32, 13 December 2025 (UTC)[reply]
    Star Mississippi's p-block should do the trick for now. Perhaps this editor can learn that we operate by consensus here, and that their personal approval is not required for us to operate. Ravenswing17:20, 13 December 2025 (UTC)[reply]
    Agreed.Rambling Rambler (talk)17:34, 13 December 2025 (UTC)[reply]
    Yep. •a frantic turtle 🐢17:38, 13 December 2025 (UTC)[reply]
    With the partial block, I think there's not much else to do here.CoffeeCrumbs (talk)17:31, 13 December 2025 (UTC)[reply]
    The discussion above is closed.Please do not modify it. No further edits should be made to this discussion.

    PolitickingAnalysis

    [edit]

    PolitickingAnalysis (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log)

    PolitickingAnalysis is an SPA which is solely interested in inserting negative coverage onZack Polanski (a BLP). They have ignored my attempts to drawWP:CRITS to their attention. Another user has also noted that the material they are trying to insert is already covered in the article. They have reverted to restore their poor content three times within 24 hours. The argumentative edit summaries show that they are aware that they have been reverted and why. The user name suggests that they are here to do analysis, which is to sayoriginal research, and I think this all adds up toWP:NOTHERE. --DanielRigal (talk)21:54, 13 December 2025 (UTC)[reply]

    Note: Disruption is ongoing. Latest diff wasthis where the edit summary says in part"I will not be budged" which is indicative of a battleground mentality. --DanielRigal (talk)22:52, 13 December 2025 (UTC)[reply]

    DanielRigal, the above information is simply untrue and anyone can see the edits and I’m glad as they can make their own unbiased opinion. I have not presented any negative opinion here, I am in support of Polanski but have not made my edit positive either. Anyone can see the last edit I made was just a heading, which separates a summary of part of his career in “early life” as it is not part of his early life, but part of his career and I think this is very important to note. You are reverting to a less evolved article. I’m not sure what you have against my editing, suggesting you don’t like it because you saw it initially as I was negative, but when I worded it exactly how you approve of it, you still come up with another excuse to undo again and again and then have the nerve to report it here. Please take another look now you are more informed.PolitickingAnalysis (talk)22:57, 13 December 2025 (UTC)[reply]

    @PolitickingAnalysis: Other editors have objected to the content you added. If you want it to be in the article, you will need to seekconsensus for your change on the article talk page. You have now been blocked by @Rsjaffe foredit warring. If you continue to try to reimpose your edits after your block expires, you will be blocked again.voorts (talk/contributions)23:01, 13 December 2025 (UTC)[reply]
    Privately messaged, see here for the message the:
    “have no idea what you’re talking about” - voortsPolitickingAnalysis (talk)23:23, 13 December 2025 (UTC)[reply]
    You didn't privately message me. You left public posts on my talk page. Seehere for full context. Stopassuming bad faith about other editors.voorts (talk/contributions)23:24, 13 December 2025 (UTC)[reply]
    They are nowposting borderline personal attacks on my User Talk page and I regret to say that I think that a stronger sanction may be required. --DanielRigal (talk)

    Just to be clear, there are no “borderline personal attacks” and that allegation is preposterous. Anyone is clear to see this and I am sure of how they will see it. I was simply asking you a question about your issue with me. Just because you don’t like the question doesn't mean it is a personal attack that is genuinely laughable.PolitickingAnalysis (talk)23:25, 13 December 2025 (UTC)[reply]

    @PolitickingAnalysis:, your comment on DanielRigal's talk pagehere,Is that why you are doing this? Because you are so pro-Polanski you are trying to protect him?, isn't just a borderline personal attack, itabsolutely IS a personal attack. It's explicitlycasting aspersions on the reasons someone made edits, instead of commenting on the edits themselves. -The BushrangerOne ping only03:49, 14 December 2025 (UTC)[reply]
    • Checkuser comment - I saw the discussion on voorts' talk page and wondered why a three-hours-old account would be bothering an uninvolved administrator with this sort of complaint. They are Technicallyindistinguishable to a number of older accounts, but I'm hesitant to name them because their older accounts have never edited anything remotely related to this topic. The one that seems to be the main account was under fire recently (within the last week) for inappropriate LLM use, but is not blocked. Their IP range is under a softblock but I can't determine if that is related or not. So I'll just ask:@PolitickingAnalysis: why did you create this account for these edits, instead of using one of your existing accounts?Ivanvector (Talk/Edits)00:03, 14 December 2025 (UTC)[reply]
      I'm hesitant to name them because their older accounts have never edited anything remotely related to this topic, Given that they were just dinged for inappropriate LLM use, and now they've created a new account to edit war over negative content in a BLP about a politician, I think the accounts should be publicly linked and blocked.voorts (talk/contributions)00:13, 14 December 2025 (UTC)[reply]
      Well that's sort of the problem I have here. PolitickingAnalysis doesn't seem to be editing with an LLM, and their other accounts have not been sanctioned or even warned for the sort of disruptive BLP editing that we're talking about here. The other accounts mostly edit topics related to European sports, not anything similar to Australian politics at all. Users are allowed to use multiple accounts, including for segregating editing in different topics, as long as they're not doing it purposely toavoid scrutiny or appear to be more than one person in consensus-finding activities, and as far as I can tell they aren't. A case could be made forWP:GHBH but I don't think we're quite there. That's why I've landed on just asking them what they're doing. If they choose to heed the advice here and start editing constructively, or just abandon this account and don't get into trouble with their others, then I would be outing the other accounts they might have good reason for keeping private without a good reason. On the other hand if PolitickingAnalysis does end up with a site block, or evades their block with one of their other accounts, then I absolutely will revealand blockall of their alts. They can take this comment as they see fit.Ivanvector (Talk/Edits)01:25, 14 December 2025 (UTC)[reply]
      Just to clarify, Polanski is a British politician. So if the European sports you are talking about were from England, that could be the connection.Esolo5002 (talk)06:35, 14 December 2025 (UTC)[reply]
      Might be a bit missing the wood from the trees, here. CheckUser or not it's clearly aWP:NOTHERE account so just block them.Rambling Rambler (talk)13:40, 14 December 2025 (UTC)[reply]

    Magician Abby

    [edit]

    Earlier this year I made anANI report concerningMagician Abby (talk ·contribs)'s edits toPennywise, which resulted in Abby saying they would get amentor on their talk page. I'm sad to say that not only have they failed to get the mentor they said they would get, but their problematic editing has not stopped either. First off, he removed an entire talk page section's worth of comments atTalk:Pennywise where other editors had commented (diff), and then were warned for it by Sundayclose. Then some time later they lost access to their account and, instead of recovering it via resetting the password,made a new one and posted a message to me on my talk page about it. Fair enough, especially since he made it clear it was him.

    Then, under the new account, he got into edit warring atBanu Fazara demonstrating an inability or unwillingness to discuss the article on its talk page, and only explained his edits whenNotJamestack (talk ·contribs) sent him a user warning about it at his talk page. It's clear to me that he has not actually taken the time to read and understand the guidelines such asWP:OR despite the warnings about them being plastered all over his talk pages. This is exemplified atUser talk:Magician Abby#Original research whereJoyous! (talk ·contribs) explained to him what original research was, and I pointed out that Abby and I had already talked about it atUser talk:Magician Abby#It (character). Abby clearly did not learn his lesson after Sundayclose's warning, as heonce again deleted an entire talk page section worth of comments, some of which were not his. (This is regardless of any bans/blocks faced by the TA whose comments were deleted. Not sure if I should revert Abby's deletion because they were evading a block, but thought it should be noted here nonetheless.)

    After thinking it over and analyzing the combined number of user warnings on both Abby's pages, I'm thinking that although he is trying to make good edits, he's unintentionally running our collective patience thin. (I'm pretty sure there's an essay on that somewhere but I can't remember what its name was).

    Don't get me wrong, Abby is clearly making good faith edits (some of which were kept, even). But I think a failure to understand our guidelines, expectations and policies is wearing our community's patience thin, and I'd like for something to be done about this since the mentor didn't work.

    @Sundayclose,Joyous!,NotJamestack,BusterD, andR Prazeres: tagging you all as people who have had discussions with him in the past who may want to weigh in on this.— Precedingunsigned comment added byGommeh (talkcontribs)23:27, 13 December 2025 (UTC)[reply]

    Just to clarify for everyone, there seem to be two accounts involved here from the same person (correct me if I'm wrong):Magician Abby andMagicien Abby. Judging bythis comment, the editor seems to have lost the previous account, but it's probably worth providing links for both accounts at the top of this thread.R Prazeres (talk)00:35, 14 December 2025 (UTC)[reply]
    That said, I've only encountered this user today so I'm not well placed to evaluate their whole editing history. Their most recent edits were non-constructive as they involved mass unexplained changes to multipleOttoman sultan articles, particularly by replacing infobox images, in some cases reverting a previous editor's more careful and constructive edits (e.g.[66],[67]) or making various other unexplained changes/deletions ([68],[69]).R Prazeres (talk)00:46, 14 December 2025 (UTC)[reply]
    Update:This certainly suggests they're not planning on being collaborative. They also responded to Gommeh in particular with "I don't remember you who are" ([70]) even though, as I mentioned above, their very first edit was on Gommeh's talk page ([71]). These reactions alone lookWP:NOTHERE to me.R Prazeres (talk)17:28, 14 December 2025 (UTC)[reply]
    Agreed, they seem to be pushing their own interpretations of things and then putting them into the articles without regard for consensus or what sources say, as they have done atPennywise and as evidenced ontheir talk page. After multiple discussions with them, they seemed to not care enough to learn what our guidelines say in those regards (WP:OR in particular).Gommeh 📖   🎮21:51, 14 December 2025 (UTC)[reply]
    I've explained what OR is, but I don't see evidence from their editing that they've really internalized it. The contributions I've seen suggest that if they believe something to be true, then it is. I found[72] particularly bothersome, as it wiped a discussion on anarticle talk page, not just their own user talk.Joyous!Noise!04:48, 15 December 2025 (UTC)[reply]
    This isn't the first time Abby did that either, seediff. As mentioned before, they were warned about this exact type of behavior and clearly didn't care enough to not do it again.Gommeh 📖   🎮05:59, 15 December 2025 (UTC)[reply]

    GiantSnowman cosmetic edits

    [edit]

    I've now warnedGiantSnowman (talk ·contribs) at least twice now about making semi-automatedcomsetic edits to articles:User talk:GiantSnowman/2025#Edit to Kathleen O'Melia andUser talk:GiantSnowman/2025#Cosmetic edits; I also remember raising this at a recent ANI thread about GS that I can't find. Yet it continues:Special:Diff/1313884803/1327221927.voorts (talk/contributions)23:30, 13 December 2025 (UTC)[reply]

    Beginning in a few hours, GS will be on vacation. Just noting, so people know it's unlikely GS will be responding here. Perhaps re-raise this when they return? --Hammersoft (talk)23:42, 13 December 2025 (UTC)[reply]
    The vacation notice says he'll be back tomorrow, not that he's leaving tomorrow.voorts (talk/contributions)23:47, 13 December 2025 (UTC)[reply]
    Ah, right. I saw heavy activity today from them so I assumed (and read too fast) the 14 meant beginning. --Hammersoft (talk)23:53, 13 December 2025 (UTC)[reply]
    (edit conflict) Is GS still under the restriction banning cosmetic edits? The only sanction I see logged atWP:EDR is an Arbcom sanction banning reverting without an edit summary and blocking an editor who hasn't been appropriately warned, and anadmonishment (but not a restriction) from a laundry list of things which didnot include cosmetic edits. I'm also pretty sure I remember GS being restricted from cosmetic edits, but that's not in the log. Maybe we should also have a log of restrictions that have been rescinded, just for things like this.Ivanvector (Talk/Edits)00:16, 14 December 2025 (UTC)[reply]
    @Voorts: I'm guessing the thread you referenced in your initial comment (but weren't able to find) wasWikipedia:Administrators' noticeboard/IncidentArchive1199#User:GiantSnowman mass-changing "committed suicide" including in quotes, against consensus?Daniel (talk)03:06, 14 December 2025 (UTC)[reply]
    Yes.voorts (talk/contributions)15:27, 14 December 2025 (UTC)[reply]
    The documentation forTemplate:Use mdy dates specifically states that the|date= parameter is "The month and year that the article was last checked for inconsistent date formatting." An edit likeSpecial:Diff/1313884803/1327221927 is therefore appropriate if the article was checked and no inconsistencies were found. ANI is not the place to change how the template works. See alsoWikipedia talk:Bot policy/Archive 29#Systematic mass edits to hidden category dates, where much the same discussion was had two years ago (at another place that wasn't the right place to change how the template works).Anomie00:14, 14 December 2025 (UTC)[reply]
    What is even the point of checking articles for consistent date formatting? This seems like a holdover from ancient days, before the citation templates automatically converted the formatting based on which use dates template was in place. —David Eppstein (talk)00:44, 14 December 2025 (UTC)[reply]
    Dates outside of citation templates may still need checking.Anomie00:59, 14 December 2025 (UTC)[reply]
    The citation templates automatically convert? Then why do I stillvery frequently come across citations with "2025-12-14" date format? Is there a setting I need to fix?Ivanvector (Talk/Edits)01:28, 14 December 2025 (UTC)[reply]
    My understanding is that if the article has a{{Use DMY dates}} or similar template then any dates in citation templatesshould display in the specified format if the template code recognises them as a date in a place it is expecting a date. It does change the wiki code in any way and it will not impact the display of the date in titles, quotes, etc.Thryduulf (talk)02:38, 14 December 2025 (UTC)[reply]
    @Thryduulf: did you mean "doesnot change the wiki code"?Narky Blert (talk)03:26, 14 December 2025 (UTC)[reply]
    I did, yes. Whoops!Thryduulf (talk)09:47, 14 December 2025 (UTC)[reply]
    Hey you're right, they do! Learned something new today (well, yesterday I guess). I also didn't know we can build a template that changes its appearance based on the presence of other templates on the page.Ivanvector (Talk/Edits)13:36, 14 December 2025 (UTC)[reply]
    The citation templates can in fact be set to convert datesinto the numeric format, or to convert some of the dates (the access-dates and archive-dates) into that format while leaving the rest long. It is one of the standard date formats that we allow. —David Eppstein (talk)02:55, 15 December 2025 (UTC)[reply]
    @Anomie:, unfortunately, you left out part of the documentation fromTemplate:Use mdy dates which negates your statement. The entire bit that you quoted the first part of reads:The parameter...is intended to track the most recent month and year in which an editor or bot checked the article for inconsistent date formattingand, if any inconsistencies were found, fixed them to comply with this template's date formatting preference (emphasis added). If a more recent check than the previously-listed date had no inconsistencies found that needed to be changed, the date shouldnot be updated. -The BushrangerOne ping only03:42, 14 December 2025 (UTC)[reply]
    I noticed that they appear to be usingone of the scripts. Using it will automatically change the template even i nothing else was changed. I use the same script but I only use it in combination with other edits.CambridgeBayWeather (#1 deranged),Uqaqtuq (talk),Huliva04:41, 14 December 2025 (UTC)[reply]
    That doesn't negate Anomie's statement. It instructs that if inconsistencies were found to fix them; but does not say not to update the template if the check didn't return any inconsistencies.Mr rnddude (talk)06:54, 14 December 2025 (UTC)[reply]
    That's how I read it too: the requirement is to fix any found, but finding any is not required to update the date. And besides that, I was looking at the TemplateData, which says in fullThe month and year that the article was last checked for inconsistent date formatting. May use "{{subst:DATE}}" template instead with no confusing extra clause.Anomie14:05, 14 December 2025 (UTC)[reply]
    This is obviously an (&&(||)) statement, not an &&.~2025-40832-95 (talk)03:20, 15 December 2025 (UTC)[reply]
    Edits like these are annoying and contrary toMOS:DATERET:Special:Diff/1324127980.
    I would like to stop having to clean up after editors using scripts to make useless edits, not least because I have to go and look up the stupid fix every time and that's not easy to do when I've editing on my tablet.GreenLipstickLesbian💌🧸08:29, 14 December 2025 (UTC)[reply]
    To my readingWikipedia:Manual of Style/Dates and numbers#Retaining existing format does not apply to yyyy-mm-dd dates but is saying don't change dd-mm-yy to mm-dd-yy 0and vice versa. As to being useless that's something else but look at reference 13 onMuriel Hannah ""Native scenes specialty of outstanding artist"'. Fairbanks Daily News-Miner.December 3, 1958. p. 100. Retrieved2025-09-26 – via Newspapers.com." is somewhat jarring. And theway it looked before the GiantSnowman edit was even worse. While they may be cosmetic they aren't really uselessCambridgeBayWeather (#1 deranged),Uqaqtuq (talk),Huliva08:56, 14 December 2025 (UTC)[reply]
    PerMOS:DATE yyyy-mm-dd is perfectly fine in places like templates, so yes, changing it by script without regard for context is a DATERET issue. I agree with GLL.PARAKANYAA (talk)19:05, 14 December 2025 (UTC)[reply]
    @CambridgeBayWeather The fact that editors find dates written in a format they're unfamiliar with "jarring" iswhy we have DATERET. As Parankayaa says, that date format is fine in templates, especially given that they automatically format themselves. If you'd like to pressure the media wiki developers to make the retrieved parameter also format according to the date tag, then you may go and do that.GreenLipstickLesbian💌🧸23:45, 14 December 2025 (UTC)[reply]
    I see you missed the point. I am very familiar with all three types of writing dates. Canada use both the US and British format and my job involves the yyyy-mm-dd format, and is the one I use in day-to-day life, so it;s not that one type is jarring. What is jarring is that there are two different types used in the same reference. It should be consistent. As you point outWikipedia:Manual of Style/Dates and numbers#Retaining existing format covers this where it says "If an article has evolved using predominantly one date format, this format should be used throughout the article, unless there are reasons for changing it based on the topic's strong ties to a particular English-speaking country, or consensus on the article's talk page." Also on Wikipedia:Manual of Style/Dates and numbers in the section "Access and archive dates" ( it allows for all three date type and does not prevent two different types in a reference. However, I merly pointed out that it looks jarring or, if you prefer, odd.CambridgeBayWeather (#1 deranged),Uqaqtuq (talk),Huliva04:18, 15 December 2025 (UTC)[reply]
    @CambridgeBayWeather And I see you missed mine. And, given you said "worse", while pointing to a revision where all the reference date formats wereconsistent, I'm not entirely sure I understand what you can possibly find objectionableotherthan the YYYY-MM-DD format. Can you explain?GreenLipstickLesbian💌🧸04:32, 15 December 2025 (UTC)[reply]
    Yes, because the reference date formats were not consistent. Going back to Wikipedia:Manual of Style/Dates and numbers in the section "Publication dates" just above the "Access and archive dates", again unlinkable. The full line says "Publication dates in an article's citationsshould all use the same format, which may be:" (my bolding) and then gives the choices. Looking atthis which is the same I linked above, references numbered 3, 8, 20, and 29 use the US format and the others use yyyy-mm-dd. So based on the MOS it does require fixing. The should all be US or all be yyyy-mm-dd.CambridgeBayWeather (#1 deranged),Uqaqtuq (talk),Huliva05:24, 15 December 2025 (UTC)[reply]
    If 4 out of 30 references use a date format and all 26 over use the exact same one, then it should be obvious to anybody actually reading the page which citation format was intended. I'm sorry that the four references bothered you so much; if you'd like to fix them to YYYY-MM-DD in the current version,you are more than welcome to.GreenLipstickLesbian💌🧸05:35, 15 December 2025 (UTC)[reply]
    GiantSnowman tried that following the line(but all-numeric date formats other than yyyy-mm-dd must still be avoided). and here we are.CambridgeBayWeather (#1 deranged),Uqaqtuq (talk),Huliva06:32, 15 December 2025 (UTC)[reply]
    If he tried to change all the reference dates to YYYY-MM-DD, he did a spectacularly bad job at it...GreenLipstickLesbian💌🧸06:36, 15 December 2025 (UTC)[reply]
    Because according to Wikipedia:Manual of Style/Dates and numbers he didn't have too and it expressly says under "Consistency":
    • Publication dates in an article's citations should all use the same format, which may be:
      • the format used in the article body text,
      • an abbreviated format from the"Acceptable date formats" table, provided the day and month elements are in the same order as in dates in the article body
      • the format expected in thecitation style being used (but all-numeric date formats other thanyyyy-mm-dd must still be avoided).
    So he was following the MOS and above you are telling me to do exactly the same thing. And it of course conflicts with other things that Wikipedia says and comes down to which has more authority / precedenceWikipedia:Manual of Style/Dates and numbers orWikipedia:Citing sources.CambridgeBayWeather (#1 deranged),Uqaqtuq (talk),Huliva07:08, 15 December 2025 (UTC)[reply]
    YYYY-MM-DD is a date formatexplicitly allowed in citations, as per the text you yourself are quoting. The citation style used in the templaates was overwhelmingly YYYY-MM-DD. And GS knows that he wasn't meant to change it away from this- he was explicitly told this at the last AN/I thread.[73]GreenLipstickLesbian💌🧸07:14, 15 December 2025 (UTC)[reply]
    My apologies. You're right. I completely misread that line.CambridgeBayWeather (#1 deranged),Uqaqtuq (talk),Huliva08:43, 15 December 2025 (UTC)[reply]
    @CambridgeBayWeather No worries, and sorry you had to witness my brain short circuiting! (real talk, you can pry YYYY-MM-DD out of my lifeless hands, I grew up in an British household in an immigrant & Alaska Native community. It's, like, the only version of a date formatting I can use consistently at this point )GreenLipstickLesbian💌🧸09:01, 15 December 2025 (UTC)[reply]
    Similar. I immigrated to Canada from the UK and everybody in the house but me is Inuk. I only use yyyy-mm-dd except for the horrendous format onNav Canada forms which uses yymmddhhmm.CambridgeBayWeather (#1 deranged),Uqaqtuq (talk),Huliva09:37, 15 December 2025 (UTC)[reply]
    Thescript documentation seems to suggest it will still mess with the wikicode of publication dates in refs despite cs1-dates=ly. It feels like a hangover from the time before citation templates would auto-format dates.REAL_MOUSE_IRLtalk21:09, 14 December 2025 (UTC)[reply]
    In which case the script needs changing so as to not overwrite cs1-dates=ly.GiantSnowman17:55, 15 December 2025 (UTC)[reply]
    I think that this should be a broader discussion and that the TBAN proposal won't address the underlying issue, however if you continue to use a script that you know misbehaves you should be paying close attention to its output. This specific problem with YYYY-MM-DD dates has been raised and acknowledged before[74].REAL_MOUSE_IRLtalk22:36, 15 December 2025 (UTC)[reply]

    How lovely for Voorts to start this thread when 1) I am not really online and 2) without recently discussing with me first. As I have said previously, my interpretation of the template documentation (and supported by e.g. Anomie and Mr rnddude here, and others elsewhere) is that edits likethis are permitted. If the community agrees otherwise, then I will obviously not make such edits in the future. Just because you find something annoying is not a reason to drag me to ANI.GiantSnowman09:22, 14 December 2025 (UTC)[reply]

    Also as was flagged by somebody at a previous discussion, this is notWP:COSMETICBOT, this is "the "administration of the encyclopedia", such as the maintenance of hidden categories used to track maintenance backlogs".GiantSnowman09:34, 14 December 2025 (UTC)[reply]
    I didn't see your vacation thing until after I posted this at ANI. I also didn't think another post on your talk page would have changed anything.voorts (talk/contributions)15:19, 14 December 2025 (UTC)[reply]
    Voorts hasalready raised this issueon GS's talk page.Fortuna,imperatrix19:20, 14 December 2025 (UTC)[reply]
    Yes, 2 months ago - and they never replied to my response.GiantSnowman19:36, 14 December 2025 (UTC)[reply]
    Noting that GS gave Voorts a non-response 2 months ago.Fortuna,imperatrix20:17, 14 December 2025 (UTC)[reply]
    No, it wasn't. Stop ABFing.GiantSnowman20:44, 14 December 2025 (UTC)[reply]
    How lovely for Voorts to start this thread when ...: ABFingmax out.Fortuna,imperatrix20:50, 14 December 2025 (UTC)[reply]
    Respectfully, what would you say if you were on holiday and had barely edited and a ANI thread had been started about you?GiantSnowman17:56, 15 December 2025 (UTC)[reply]
    That's why I stopped advertising (on en.wp) whenever I'm on vacation or travelling for work because someone could start an ANI or admin recall against me in my absence and without ability to properly defend. Sorry that someone tried to "vacation snipe" you, GiantSnowman.OhanaUnitedTalk page19:32, 16 December 2025 (UTC)[reply]
    Your response was to again deny there was an issue. I didn't see the point in arguing further.voorts (talk/contributions)20:17, 14 December 2025 (UTC)[reply]
    "I didn't see the point in arguing further, so I waited 2 months then brought you to ANI in order to argue further".GiantSnowman20:45, 14 December 2025 (UTC)[reply]
    I didn't come here to argue. I saw the edit in my watchlist, and I came here to make a report.voorts (talk/contributions)20:47, 14 December 2025 (UTC)[reply]
    Sorry but that's embarrassingly disingenuous.GiantSnowman20:51, 14 December 2025 (UTC)[reply]
    The only thing I've now argued about with you is whether I intended to argue with you. In my view, your edits are in contravention of COSMETICBOT, as I've stated in the past. If I'm wrong, the community will say so.voorts (talk/contributions)21:02, 14 December 2025 (UTC)[reply]
    If I'm wrong, the community will say so. Since you asked, and with myBAG hat on: An edit such asSpecial:Diff/1313884803/1327221927 is not in violation ofWP:COSMETICBOT, as it qualifies as substantive per the "administration of the encyclopedia" bullet. Edits that combine such a change along with some cosmetic changes (such as changing of YYYY-MM-DD dates to another format where the cite templates will auto-reformat them) are also not in violation ofWP:COSMETICBOT, as they include a substantive change along with the cosmetic changes. Whether or not those date changes contraveneWP:DATERET or are allowed byMOS:DATEUNIFY does not affectWP:COSMETICBOT.Anomie23:00, 14 December 2025 (UTC)[reply]
    • As I said in that September ANI thread.I don't think we need, at this time, an explicitprohibition of use of automated tools by GS, but they should bear in mind that "once is an accident, twice coincidence, but three times is a pattern" and this isat least, that I am aware of the second time - theymust take more care with the use of automated editing tools, because a third recurrence will likely see a sanction proposed with regards to automated tool useage. GS is continuing to make these pointless, or nearly pointless, cosmetic edits, with no sign of taking on board any of the concerns the community has raised with them onat least three occasions; I actually wrote this up yesterday but tabled it in hopes of a constructive response from GS. My hopes were low but they have been met by theespecially combative reponses above, and thus that time has come. I formally propose thatGiantSnowman be topic-banned from using automated or semi-automated tools, including but not limited to scripts, to perform edits on Wikipedia. -The BushrangerOne ping only21:06, 14 December 2025 (UTC)[reply]
      I have already said that "If the community agrees otherwise, then I will obviously not make such edits in the future". However, nobody has actually explainedwhy these edits contradict COSMETICBOT, whereas a number of editorshave explained why they do not. Furthermore, where is the evidence that my use of such script(s) is disruptive and merits a topic ban?GiantSnowman21:14, 14 December 2025 (UTC)[reply]
      Also the proposed topic ban is ridiculously wide. If it passes, I cannot use e.g. Refill/Autoed/Hotcat etc.?GiantSnowman21:18, 14 December 2025 (UTC)[reply]
      Support topic ban, I am not satisfied with User:GiantSnowman's responses to the accusations of useless semi-automated edits above. — AP 499D25(talk)10:22, 15 December 2025 (UTC)[reply]
    • If someone proposes to change the documentation of the date format templates to be clearer that updating the date without making any changes is not a useful edit, please ping me so I can support it. The defense of these edits is always bizarre to me. —Rhododendritestalk \\22:42, 14 December 2025 (UTC)[reply]
      If the purpose of the date change is to indicate to others going through the "review date formatting" backlog that the page has been checked and doesn't need to be checked again for a while, it may in fact be a useful edit. Whether there's a "better" way to accomplish that would be a matter to discuss with people who work that backlog.Anomie23:09, 14 December 2025 (UTC)[reply]
      Yes, nobody on the 'useless' side has explainedwhy.GiantSnowman17:56, 15 December 2025 (UTC)[reply]
      I explained why both times on your talk page.voorts (talk/contributions)18:02, 15 December 2025 (UTC)[reply]
      No, you have not. You just say "you're violating COSMETICBOT" and leave it at that - me and others here have already explained why COSMECTICBOT does not apply (or, at least, we think it doesn't), which just seems to fall on deaf ears.GiantSnowman18:12, 15 December 2025 (UTC)[reply]
      • First time I discussed this issue with you:I was referring to the edits to the citations, which are cosmetic edits since it didn't change any displayed text. MOS:DATE and MOS:DATEUNIFY also say the format YYYY-MM-DD is acceptable for use in citations.
      • Second time:I've previously advised that cosmetic edits like this are not helpful and violate WP:COSMETICBOT. It's much easier to consistently type in YYYY-MM-DD instead of MMMM DD, YYYY, and existing styles should be retained. Edits like this, which clog up editors' watchlists, are even less useful. While I appreciate that you want to clean up articles appearing on the main page, there are better ways to go about doing that.
      voorts (talk/contributions)20:40, 15 December 2025 (UTC)[reply]
      Changes that are typically considered substantive [...] such as the "administration of the encyclopedia", such as the maintenance of hidden categories.GiantSnowman20:44, 15 December 2025 (UTC)[reply]
    • I thought what Rhododendrites described was already true / common sense, but if there needs to be an RFC or something to affirm the obvious, let's do it. Updating the dates on maintenance templates is real churn on editor attention for no discernible benefit, and is an unhelpful cosmetic edit. Alternatively, if this can just be acclaimed by consensus, let's do it, but in the interim stop any of these types of edits.SnowFire (talk)05:54, 15 December 2025 (UTC)[reply]
      I have already said that if there is consensus that such edits should not be made (and I do not think ANI is the place for that discussion), I will not make these edits.GiantSnowman17:57, 15 December 2025 (UTC)[reply]
      To me this reads as "Yes, there needs to be an RFC to affirm the obvious, because otherwise I will keep doing it". But perhaps I am misreading. Was that your intention? —David Eppstein (talk)00:19, 16 December 2025 (UTC)[reply]
      I think his intention was 'I want crystal clear consensus on whether modifying dateformats in templates are an issue, rather than conflicting opinions'.~2025-31733-18 (talk)17:59, 16 December 2025 (UTC)[reply]
      Bingo.GiantSnowman18:12, 16 December 2025 (UTC)[reply]
    • How many indefinte restrictions does one admin need, I wonder. A topic ban or any other restriction imposed here would merely augment GS'sarbcom-imposed restrictions on their use of the rollback and blocking tool. (Logged.)Fortuna,imperatrix17:40, 15 December 2025 (UTC)[reply]
    • Molehill. Respectfully. —Rutebega (talk)22:53, 15 December 2025 (UTC)[reply]
    • I agree with Rutebega, this seems blown out of proportion to me. The first example given is of GS thanking Voorts for correcting him and the second was GS seeking clarification on what the consensus is around this practice which was not responded to. I think it would have made more sense to warn him and/or respond to all of his inquiries rather than institute a sanction against him.Gjb0zWxOb (talk)17:22, 16 December 2025 (UTC)[reply]
      He thanked me the first time then repeated it. The second time he basically asserted there was no issue despite my explaining the issue. I also haven't asked for a sanction here. I merely reported the issue. I'd be happy if GS said "sure, I'll stop". Surely there are better ways an editor of GS's experience can spend their time than patrolling the front page to run unnecessary "audits" that don't actually improve content.voorts (talk/contributions)17:33, 16 December 2025 (UTC)[reply]
      Your opinion that these are "unnecessary audits" is not supported by others here, or COSMETICBOT, or the template documentation itself etc. If it annoys you so much - when I tidy up 5-15 articles per day on the main page - simply ignore me.GiantSnowman18:16, 16 December 2025 (UTC)[reply]
      Your edit toAddie Viola Smith didn't tidy up anything. It changed the date in a single template and did nothing else.voorts (talk/contributions)18:28, 16 December 2025 (UTC)[reply]
      We are going round in circles. This has already been explained by me, and others.GiantSnowman18:32, 16 December 2025 (UTC)[reply]
    • Agree with Rutebega and Gjb0zWxOb. We are approachingWP:BIKESHED territory.OhanaUnitedTalk page19:23, 16 December 2025 (UTC)[reply]

    Personal attacks, sockpuppeting, and harassment by Iosif77

    [edit]

    The following discussion is closed.Please do not modify it. No further edits should be made to this discussion.


    Earlier this week,Iosif77 (talk ·contribs) made ahighly controversial and misleading undiscussed page move atRussian intervention in the Syrian civil war. In their summary for their page move, Iosif77 falsely claimed that it was because Russia occupied Syria without anyWP:RS. They were warned bySkitash (talk ·contribs) over their controversial act, but they proceeded to make a more controversial and unsurprisingly undiscussedpage move atBa'athist Syria that was in violation ofWP:UNDUE andWP:NPOV. I warned them, but they proceeded to say"Choosing a euphemism like "baathist syria" neither reflects the English language terminology consistently used to refer to the assad regime over these past 14 years, nor respects the Arabic language origin of the term (نظام الاسد) among Syrians and Arabs as a whole that was subsequently picked up by English language reporters, especially before ~2015.". They again proceeded to defend their controversial, POV-pushing act that they even mentioned that they falsely claimed that Skitash,Abo Yemen (talk ·contribs), and I were"dogpiling" Iosif77 and pointing fingers at Iosif77 and also said in aWP:PA, that everyone editing Syrian-related articles should have their privileges removed and sanctioned (see link above) for"none of you exhibited the responsibilities entrusted upon you to prevent abuse of Wikipedias Syria pages by assadist trolls, bots and lone wolf sympathizers" in another PA. When I realized it was indeed a PA, Iosif77 told me to"go fuck yourself", another PA. Since then, I've warned them toWP:DROPTHESTICK and back from the horse carcass before anything gets worse. Keep in mind Iosif77 is asockpuppeteer (confirmed byasilvering (talk ·contribs)) and was blocked for one week instead of a usual indefinite block sockpuppeteers would receive. They also said"all the bans i keep getting in response is to prevent the assad regime from becoming a "lost cause" myth", which is suspicion of further socking (asThe Bushranger (talk ·contribs) pointed out.)Freedoxm (talk·contribs)07:57, 14 December 2025 (UTC)[reply]

    I agree with the OP. Iosif77 is exhibitingWP:NOTHERE andWP:RGW behavior by boldly moving articles at will without consulting other editors. The persistent personal attacks act as further evidence of their uncollaborative approach to editing.[75] Since Iosif77 was previously blocked indefinitely on their sockmaster account for the exact same behavior,[76] then surely their actions may warrant a longer block on this sock account of theirs.Skitash (talk)13:17, 14 December 2025 (UTC)[reply]
    The discussion above is closed.Please do not modify it. No further edits should be made to this discussion.

    RollingInHisGrave

    [edit]

    Samantha Fulnecky essay controversy. For those who don’t wanna click, it’s about the recent story of the trans instructor getting removed for giving a bad essay written by a Christian girl a zero.

    Anyway, I posted and properly cited an update to the story sayingFollowing the protests, the university removed another instructor who had excused their students to attend, with the university saying that said instructor had committed "viewpoint discrimination” directly quoting the university’s statement as provided by the source.[77] Subsequent edits changed the wording toThe university removed another instructor who had excused their students to attend the protests, as it had determined that the instructor had not extended that opportunity to students wishing to demonstrate in support of an opposing view.[78] which is not how I would’ve written it, but I didn’t really have a problem with it, it was just a stylistic difference - and so I didn’t revert it.

    Nonetheless, RollingInHisGrave (RIHG) took what I believe to be personal exception to my initial edit, and began pressing me on my talk page about why I made that edit and why I should understand that the new edit was better;[79]while my stance was that there’s nothing wrong with directly quoting an organization’s statement, and that given the topic matter, it’s better to quote them than give the extra credence of wikivoice; but again, I didn’t revert, because I was still perfectly fine with Bridget’s edit. We have different editorial philosophies, but that’s the entire point of a collaborative project; so we had an abstract debate on FALSEBALANCE and BLUESKY. I still thought my edit was a reasonable update to events, but I didn’t find the subsequent edit unreasonable, and I wasn’t challenging it; and that was largely why I wasn’t presenting a more serious defense or case for my initial edit because, why would I? I’m not reverting or challenging on talk, we’re just having a convo he saw fit to start.

    He took that quite poorly, I’d say, and began telling me that he wanted to escalate this to NPOVN and told me to put together mystrongest justification for writing the original text as you did without an explanation of the university's position[80] (again, I directly quoted the uni's position) and at that point I’d decided this had gone on long enough given that this wasn’t even a content dispute, nothing had been reverted or challenged, and I was under no obligation to personally SATISFY him. So I tried letting him know gently by saying thatI honestly don't feel strongly enough about it to go that far.[81]

    His response began withDisappointing that we find ourselves at this impasse (what impasse? Because I hadn’t agreed with him yet?), threatened tofollow you around reviewing your edits for NPOV, and ended withYou obviously have very strong opinions in this subject-area, and it, or something else has compromized the reading of emphasis you take from sources. What do you propose I should do from here?[82]

    I told him I didn’t see any need for action, and that his threat of following me around over this would be textbook hounding given that he was very clearly doing this because I simply didn't agree with him.

    He wouldn’t hear it, and said that he wanted to still escalate this becauseyou haven't indicated to me that you see anything wrong with it in the first place, so I have no assurance that you won't continue to make more edits doing the same thing, unless I agreed tomake edits along the lines of the second rather than the first from now on, at which point I responded by just citing WP:SATISFY directly.[83][84]

    Perhaps I’m just more tense because I have to deal with the one IP hounding with the stated goal of getting me banned,[85] that half the admins probably know about by now, but can I get an IBAN on this guy? I don’t know what his problem is or why he can’t just take agree to disagree for an answer, but I’d kindly like not to have an additional hound.Snokalok (talk)15:08, 14 December 2025 (UTC)[reply]

    Link to discussion:User talk:Snokalok#NPOV at Samantha Fulnecky
    Hi Snokalok, sorry this has come about at a stressful time for you with the IP hounding. As I said on your usertalk page, my issue is with your general editing in this area, and the particular example I raised was meant to be illustrative of the broader pattern, as I saw it as misleading and as written in a way to reduce the university's credibility, failingWP:OPPONENT, due to a connection you drew that no reputable sources were drawing. I believed the specific example was misleading asthe university removed another instructor who had excused their students to attend, with the university saying that said instructor had committed "viewpoint discrimination" would or could lead the reader to believe the act of excusing students to attend was the alleged viewpoint discrimination, when it was actually the alleged failure of the instructor to extend the same opportunity to students wanting to attend a counter-protest.
    Since we hadn't come to a mutually satisfactory understanding of NPOV, and I still believed you would be making edits in a non-neutral manner, I said I had been hoping for a good resolution, and thatI don't want to follow you around reviewing your edits for NPOV based on my understanding, that will suck for both of us, which in my reading ofWP:HOUNDING is permitted. I also clarified when you said this would be harassment that I believed it was permitted, andif it was causing you undue distress I would have a responsibility to seek other avenues. My references to escalation have been to the escalating dispute resolution process (two editors,3O,DRN,NPOV noticeboard,RfC etc) to resolve the question of whether your edits do have any issues with neutrality, so you didn't just have to take my word for it and so I could see if I was correctly understanding NPOV.Rollinginhisgrave (talk |edits)15:40, 14 December 2025 (UTC)[reply]
    Right, and I'm going to repeat mate: I have no obligation to satisfy you. Drop the stick.Snokalok (talk)18:05, 14 December 2025 (UTC)[reply]
    Well for the record, whenI repeat mate, I do my best to satisfy -- especially if I failed to do so on the first mating.EEng10:25, 15 December 2025 (UTC)[reply]
    "my issue is with your general editing in this area, and the particular example I raised was meant to be illustrative of the broader pattern" @Rollinginhisgrave if you are going to make accusations of misconduct,you need to provide evidence, especially on this noticeboard. —Rutebega (talk)06:43, 15 December 2025 (UTC)[reply]
    I provide several instances in the linked discussion where I feel Snokalok's editing is not neutral. I would prefer not to litigate that question here; I would like the issue to be worked through the dispute resolution processes rather than a conduct review board which has sanctions as its primary remedy.Rollinginhisgrave (talk |edits)11:30, 15 December 2025 (UTC)[reply]
    If the discussion you are referring to is atUser talk:Snokalok#NPOV at Samantha Fulnecky then I do not see any other instances besides the single mainspace edit Snokalok describes above. It's possible I simply missed them, or they have been removed. If you aren't seeking sanctions, and Snokalok isn't contesting your edit, it seems pertinent to ask what exactly you hope to achieve through dispute resolution. —Rutebega (talk)22:45, 15 December 2025 (UTC)[reply]
    You aren't the WikiPolice, and it is neither your responsibility nor your right to badger an editor into agreeing with you because you don't feel they can uphold NPOV. If you're concerned about Snokalok's ability to contribute productively to the encyclopedia, then you make a report here, you don't surreptitiously threaten to hound their edits in search of perceived NPOV violations.Athanelar (talk)15:13, 15 December 2025 (UTC)[reply]
    I read throughUser_talk:Snokalok#NPOV_at_Samantha_Fulnecky. Rollinginhisgrave is patiently and civilly trying to explain the neutrality issues that they observed in your edit, and they explain why:NPOV can be a difficult and contestable policy, and part of why I am continuing here is because I see two, bad outcomes of stopping the conversation prematurely. In the first, you continue to edit in a way that I view as pushing a POV. In the second, I am misunderstanding the policy, and I go forth making edits based on those misunderstandings, failing to adhere in my own ways. If you read the above and take issue, I'm happy to hear from the perspective of a third-party or a noticeboard. They also explainedI raised this edit as representative of your general editing pattern. I thought it would be particularly demonstrative, because it not only failed what is laid out at Wikipedia:Neutral point of view#Balancing different views, but it also did not accurately reflect the source. You didn't revert the edit (thankyou), but you haven't indicated to me that you see anything wrong with it in the first place, so I have no assurance that you won't continue to make more edits doing the same thing. Also, I have been sincere in my description of my motives. If I am acting based on a misapprehension of NPOV, it is also a bad outcome if I go forward writing articles and editing based on it.
    What I see in that thread is one editor with a NPOV concern trying to communicatewhy they think it's a problem, and the other editor doesn't see it as non-neutral and doesn't think there's a problem, but I don't see any conduct or behavior that needs administrator action. Continuing with thedispute resolution steps that Rollinginhisgrave mentioned is the best path forward.Schazjmd (talk)18:02, 14 December 2025 (UTC)[reply]
    I also don't see this is as a problem, having concerns over points of view is perfectly normal on Wikipedia. Especially since RIHG mentioned going through dispute resolution I don't see why the admins would need to get involved in this. I've had a few conversations with RIHG as well in the past, and from what I can recall they have been pretty understanding, polite and civil even towards people who disagree with them. If RIHG has concerns over someone's edits that can't be resolved through normal discussion alone, that's what the dispute resolution processes mentioned above are for. ANI isn't one of them.Gommeh 📖   🎮21:43, 14 December 2025 (UTC)[reply]
    If two longtime editors are saying it, then fair enough I guess. I imagine that, in the midst of the very intense harassment I've been under (just look at my contribs and see how many are sock reverts, RfPP, ANI diff additions, or AIV reports), having him come on my talk and make a whole thing about how quoting instead of wikivoice was bad enough that he wasn't going to leave me alone until I agreed probably set me enough on edge to where when the notion of following me around wiki was raised in the same way the IP does, it pushed me to go straight here. That said, I do maintain that I am not obligated to satisfy him here. If he doesn't like the use of direct quotations over wikivoice, it's not my obligation to change my writing style to satisfy him.Snokalok (talk)23:57, 14 December 2025 (UTC)[reply]
    @Snokalok, I don't think quote vs. wikivoice was the point of that discussion. Maybe take some time to get some space from it then go back later and read it again.Schazjmd (talk)00:12, 15 December 2025 (UTC)[reply]
    I've disabled personal pings because a certain individual keeps making new temps and spam pinging me from their talk pages, so, yeah. See example here.[86] But I saw this through my watchlist, so I shall respond. I think that if the best example one can come up with in the wider writing of the Samantha Fulnecky article (which is the only article I believe we've ever collabed on, and which he mentioned in his initial comment) is that I used a direct quote from the uni's statement instead of explaining in wikivoice, then that feels like it's on the level of statistical noise. Again, I appreciate perhaps an attempt to educate as an academic matter, but at a certain point as I said in my initial post here, it feels like he's just refusing to take agree to disagree for an answer; and I confess, I do not see how escalation would tremendously even apply here given that, again, there's no content or proposed page direction being disputed and thus, no real reason to engage? I was perfectly fine with keeping the second edit, there is no dispute to resolve beyond him taking umbrage and me holding personal disagreement.Snokalok (talk)00:22, 15 December 2025 (UTC)[reply]
    How I would have handled it is just refusing to answer after at most 1 or 2 replies and telling him more firmly to take a hike. You know you can ban people from your talk page, right? It's so weird that editors would be willing to waste so much time arguing over a matter that's not even disputed. (t ·c)buIdhe03:59, 15 December 2025 (UTC)[reply]
    After reading through the discussion I come away with the same impression as @Schazjmd. I also however agree with @Rutebega that evidence needs to be presented more succinctly of a general pattern before @Rollinginhisgrave's persistence on this matter is justified.
    I also note it was Schazjmd who reciprocated every reply on their talk page, sent the last message in the discussion on their talk page, and brought this to ANI, so I don't find the narrative that they are facing a potential hounding very convincing. If Rolling does provide evidence for a general pattern, I really hope this discussion can be steered toward dispute resolution processes, as I think sanctions are very overblown until we actually have consensus on who is right or wrong content wise, and until we at least have more than one relatively civil talk page discussion to go on.IAWW (talk)13:18, 16 December 2025 (UTC)[reply]
    @Rutebega and @It is a wonderful world, I'll leave some things I saw that contributed to my perception that Snokalok was POV pushing.
    • Most sources framed the Samantha Fulnecky incident as a dispute between whether the grade was influenced by religious discrimination or was merited. Most did not not make determination of which was correct, which NPOV requires us to follow (describe disputes, do not engage them). The articleas written by Snokalok engaged the dispute, putting in wikivoice that the essay received its gradefor failure to respond to the assignment or to cite any empirical evidence in a scientific class.
    • That version omitted facts in the lead that did not support such a perspective. In wikivoice, it said that the article was failed for not citing empirical evidence, while the Oklahoman, which the version cited, reported that this was not a requirement. Multiple sources emphasized the instructor's comment that she found elements offensive, which was central to questions of whether the essay was being marked down for the content of speech, but this was also not included.
    • Due to the above and how the essay is summarized, coming away from the lead I have no real understanding of why Fulnecky is characterizing this as religious discrimination. I get the impression that Fulnecky is simply acting irrationally and has no justifications beyond "that's religious discrimination". There is no apparent attempt atwriting for the opponent.
    • The background section in Snokalok's version framed the incident in large part as part of an effort toban transgender people from working as teachers. This wasa minority framing in sources, espoused by a subset that were primarily those writing from a left/liberal perspective. Sources framing issues differently is fine: the Guardian may frame war coverage more heavily around humanitarian issues and the Wall Street Journal around trade consequences, but relying heavily in wikivoice on the perspective of one when it is not shared by most sources, and when such sources are expressly ideologically opposed to a party in a dispute is a failure to adhere to NPOV (WP:BALASP,WP:BIASED).
    • After seeing the above, I saw Snokalokadd text sayingFollowing the protests, the university removed another instructor who had excused their students to attend, with the university saying that said instructor had committed "viewpoint discrimination”. This again does not convey a rationale, and the reader gets the impression that the university is sanctioning instructors for excusing students to attend protests and bizarrely justifying it with reference to "viewpoint discrimination". Editors make mistakes while representing sources, but this is only happening with Snokalok in one POV direction. When discussing this edit with Snokalok, a rationale was provided: this was an articleabout the university openly siding with the alt-right to a wild and un-pretextable degree, and she avoided explaining the university's full rationale to keep the statementmore in line with the rest of the article by only referencing "pretext". This to my eye is blatant POV pushing. No reputable source mentions the alt-right, but here, Snokalok was saying she was writing the article based on personal perceptions that this was part of a pattern related to the ideology, diminishing POVs, and justifying it underWP:BLUESKY.
    Rollinginhisgrave (talk |edits)14:12, 16 December 2025 (UTC)[reply]
    The article as written by Snokalok engaged the dispute, putting in wikivoice that the essay received its grade for failure to respond to the assignment or to cite any empirical evidence in a scientific class.
    Okay two things here first off. 1. The article as written by Snokalok was an early start-class version simply to get the ball rolling. You do not see, anywhere on the page, me fighting editors the restore anything resembling that version, so saying that this is POV pushing doesn't really work. 2. The article as written by Snokalok directly quotes the feedback in the body, the same as it did for the U of Oklahoma later on.In grading the paper, Curth emphasized in feedback comments that the failing grade Fulnecky received was not based on her personal beliefs, but because the paper “does not answer the questions for this assignment, contradicts itself, heavily uses personal ideology over empirical evidence in a scientific class, and is at times offensive” Quotation marks.
    while the Oklahoman, which the version cited, reported that this was not a requirement. The article as written by Snokalok does *not* cite the Oklahoman, a quick look at the ref section shows NYT, USA Today, Huffpo, Pinknews, The Independent, Them, Advocate, and Salon. So that's not correct, but also it's a college paper. Citation being required in college papers falls firmly under academic common knowledge.
    There is no apparent attempt at writing for the opponent. The version as written by Snokalok dedicated an entire paragraph to Fulnecky's essay content, quoting it extensively as well as including source analysis of the essay, such as saying that it didn't quote any specific scriupture (Huffpo), and without answering the assignment's questions (Advocate), before quoting the essay as the sources do (USA Today, The Independent) Beyond that, I'm sorry that I didn't write any part of the article on why Christian fundamentalism is actually good and correct?
    The background section in Snokalok's version framed the incident in large part as part of an effort to ban transgender people from working as teachers. This was a minority framing in sources, espoused by a subset that were primarily those writing from a left/liberal perspective. So you agree it was backed by sources. Biased sources are allowed, per WP:ALLOWEDBIAS, and again, you don't see me locked in an edit dispute with anyone, so, maybe instead of vagueposting about it and threatening to hound my edits you could actually go on talk and try to change it? Kinda like the way you did here, where it didn't really convince anyone.[87]
    No reputable source mentions the alt-right, but here, Snokalok was saying she was writing the article based on personal perceptions that this was part of a pattern related to the ideology Sorry, are you trying to say that this is *not* very clearly an article about the far right? Should we go on all of the articles about the shoah and add "Some scholars have called the Nazis 'far right' and 'racist'?" And lastly, as you might recall, I was not composing a serious defense in that usertalk thread because again, there's no edit being disputed. You're just taking umbrage with the very idea that someone could have non-neutral thoughts.Snokalok (talk)16:31, 16 December 2025 (UTC)[reply]
    Apologies for the mistake on citingThe Oklahoman. I see Pinknews, which you did cite does include the claim on empirical evidence not being a requirement, but it is less prominent so was perhaps missed.Rollinginhisgrave (talk |edits)16:44, 16 December 2025 (UTC)[reply]
    It's okay, we all make mistakes. I would still say nonetheless that most sources don't include it, so it's not unreasonable to have not added it in. You can add it if you want, I won't take issue with that, but it's not something that has to be.Snokalok (talk)17:17, 16 December 2025 (UTC)[reply]
    My main issue here was putting in wikivoice that the article received its grade for not citing empirical evidence when sources said that was not a requirement, which I believe is an unambiguous issue and I fixed it when I first came to the article. Whether to put it in the lead is more debatable, and I agree it is not unreasonable to have not added it in.Rollinginhisgrave (talk |edits)17:31, 16 December 2025 (UTC)[reply]
    Right okay, you fixed it, I didn't challenge it to my memory, that should've been the end of it. Granted, I didn't need to engage when you went to my talk page, and honestly it probably didn't help anything for me to, but lesson learned.
    Also though, it's a college paper. In what world does the requirement for citation need to be made explicit? They start enforcing that in elementary school.Snokalok (talk)18:00, 16 December 2025 (UTC)[reply]
    Yes, I haven't had any issues with you trying to keep edits in once they have been identified as having POV issues. If this were a one or two-off where you made an edit and I changed it, it would have been the end of it and me trying to engage you in discussion on your talk page would have been probably unreasonable, especially in any concerted manner. My issue is, and has consistently been, that you are making multiple edits which need to be cleaned up for POV issues, all in the same direction. It should not be the responsibility of others in the community to clean up NPOV issues you are introducing, and I do not find the idea that POV issues in early versions of articles are excusable at all compelling.
    As I am writing this, I seeyou have just made another edit in GENSEX toAnti-transgender movement in the United Kingdom, addingIn March 2025,University of Sussex was fined £585,000 over its transgender and nonbinary equality policy, with the fine being issued because the policy forbade "transphobic abuse, harassment or bullying", stated that university curricula should not "rely on or reinforce stereotypical assumptions about trans people", that course materials should "positively represent trans people and trans lives", and that "transphobic propaganda [would] not be tolerated". The text you are summarizing saysIn March, the Office for Students (OfS) issued a record £585,000 fine to the University of Sussex, stating that the university’s trans and non-binary equality policy created a “chilling effect” and “placed constraints on freedom of speech and academic freedom”.
    The OfS objected to four statements in particular: that university curricula should not “rely on or reinforce stereotypical assumptions about trans people”; that “transphobic abuse, harassment or bullying” would result in disciplinary action; that course materials should “positively represent trans people and trans lives”; and that “transphobic propaganda [would] not be tolerated”. The regulator said at the time that the policy had the potential for “staff and students to self-censor and not speak about or express certain lawful views”.
    Again, you are not explaining the positions of those outside of your POV. The motives of the university are clear (protection of trans people), but the regulator's opaque, or implicitly just read as simple "anti-transgender sentiment" from the article's opening. This is not describing the dispute, and it is not writing for the opponent.Rollinginhisgrave (talk |edits)20:17, 16 December 2025 (UTC)[reply]

    Bondi Beach

    [edit]

    The following discussion is closed.Please do not modify it. No further edits should be made to this discussion.


    Disruptive TA atTalk: 2025 Bondi Beach shooting

    [edit]

    ~2025-40571-87 (talk ·contribs) has done nothing but cast aspersions and makeWP:FORUM andWP:NPA slurs despite warnings on a serious BLP Crime issue[88][89][90][91].Borgenland (talk)15:53, 14 December 2025 (UTC)[reply]

    cry to jimmy wales about it~2025-40571-87 (talk)15:57, 14 December 2025 (UTC)[reply]
    Indeffed.Ivanvector (Talk/Edits)15:59, 14 December 2025 (UTC)[reply]

    Attention needed at2025 Bondi Beach shooting page protection

    [edit]

    Hi, can the page protection requests for the above please be looked at as a matter of urgency given the backlog at RFPP. Both the article and talk page are seeing frequent BLP violations from TA and low-edit accounts regarding alleged names and motives.Rambling Rambler (talk)17:41, 14 December 2025 (UTC)[reply]

    Done by @Favonian
    I'm loathe to also protect the Talk since @Ivanvector got the TA, but will if needed. (also going to merge these two)StarMississippi18:26, 14 December 2025 (UTC)[reply]
    @Star Mississippi the issue is that it probably needs ECP for the article because of it being related toWP:CT/A-I and just general repeated BLP violations from low edit accounts emerging from dormancy just to post breaking news as we see with high-profile shootings.Rambling Rambler (talk)18:30, 14 December 2025 (UTC)[reply]
    I've done so now @Rambling Rambler and slightly extended the block as I don't think things will be settled within three days, although happy to be wrong and have it lifted sooner.StarMississippi18:33, 14 December 2025 (UTC)[reply]
    That'd be nice but doubtful. Similar to Charlie Kirk we're in the fantastic period of "the article doesn't say the name, so I'm going to post it 50,000 times to be an arse about it".Rambling Rambler (talk)18:35, 14 December 2025 (UTC)[reply]
    The discussion above is closed.Please do not modify it. No further edits should be made to this discussion.

    Silohpso

    [edit]
    Blockjacks and protectionjacks in service. -The BushrangerOne ping only00:36, 15 December 2025 (UTC)[reply]

    The following discussion is closed.Please do not modify it. No further edits should be made to this discussion.


    Silohpso (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log)

    User continually insulting others during discussion, doubling down even after multiple warnings from other users. Seetalk page warning for more context. Made a racialized "we wuz" crack[92]. Doubled down on it here:[93]. Also side note, theTalk:Soyjak.party page is a mess and likely being brigaded (lot of junk comments have been removed already), may need a temporary lock.grapesurgeon (talk)19:47, 14 December 2025 (UTC)[reply]

    Tagging users who previously interacted with Silohpso:@MetalBreaksAndBends:@Babysharkboss2:@Skywatcher68:@Augmented Seventh:. Feel free to tag more, this was just based on a quick scan.grapesurgeon (talk)21:31, 14 December 2025 (UTC)[reply]
    To address the topic generally: online group sociopathic behavior is an emotional sickness that thrives on being noticed for maladaptive social behavior; every kilobyte spent addressing individual boorish behavior is then worn as a vice-signaling badge by both the individual and their validation group.
    As with all editors who use insular jargon with which to insult other collaborative editors, I take a position of zero tolerance.Augmented Seventh (talk)21:52, 14 December 2025 (UTC)[reply]
    Using an argument which is not far removed from conspiracy theorist rhetoric does little more than make one look ridiculous.   –Skywatcher68 (talk)21:55, 14 December 2025 (UTC)[reply]
    Only in the eyes of non-members of the "validation group". Just block.Phil Bridger (talk)22:37, 14 December 2025 (UTC)[reply]
    I'd addUser:~2025-40402-89 in theWP:NOTHERE category due to this diffhttps://en.wikipedia.org/w/index.php?title=User_talk:~2025-39704-27&diff=prev&oldid=1327326768 (possibly canvassed)~2025-30597-01 (talk)21:32, 14 December 2025 (UTC)[reply]
    one more:
    User:~2025-40640-85, with this edithttps://en.wikipedia.org/wiki/Soyjak.party?diff=prev&oldid=1327534752~2025-30597-01 (talk)21:52, 14 December 2025 (UTC)[reply]
    I have indef'dSilohpso and~2025-40402-89 as NOTHERE primarily due to comments they have made directed at other editors and the community. I have not extended that to the other TA at this point as their comments haven't been so clearly antagonistic. But there's obviously co-ordination going on.Mfield (Oi!)22:38, 14 December 2025 (UTC)[reply]
    wouldn'tUser:~2025-40640-85 fitWP:NOTHERE in the "Major or irreconcilable conflict of attitude or intention" because they're part of a far right reactionary imageboard?~2025-30597-01 (talk)00:16, 15 December 2025 (UTC)[reply]
    It's likely a throw away TA anyway, I have just semi protected the talk page for a short period also, so they won't be posting there anymore, and I'll keep an eye on it when the protection expires.Mfield (Oi!)00:19, 15 December 2025 (UTC)[reply]
    that's a good idea, thanks! (also how did you reply so quickly?)~2025-30597-01 (talk)00:23, 15 December 2025 (UTC)[reply]
    @Closedsrc: brought up an interesting idea on the soyjak talk. If the sockpuppets/meatpuppets don't behave after the current protection expires, perhaps put pending changes protection on the article?   –Skywatcher68 (talk)00:28, 15 December 2025 (UTC)[reply]
    Certainly an option, although it can just result in a flood of nonsense edits to decline instead, so it's not necessarily a good idea on an article that's being targeted vs one that otherwise stable and just gets the occasional drive by nonsense edit, I'd lean toward extending the semi protection if the current disruption blows up again immediately.Mfield (Oi!)00:34, 15 December 2025 (UTC)[reply]
    The discussion above is closed.Please do not modify it. No further edits should be made to this discussion.

    Brigading, Bias, and Revert Abusing on the MAK article by Skitash and M.Bitton

    [edit]

    M.Bitton (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log) andSkitash (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log) are reverting all changes that don't aligned with the Algerian government position onMovement for the Self-Determination of Kabylie.

    On 15 March 2023, M.Bitton dismissed a user by stating "I don't have to prove the opposite of your baseless assertion. Please don't ping me again."

    When AmLaw100Professor and Electro Hiddens, were also dismissed. Pencilceaser123 and Monsieur Patillo, who is a prolific French Wikipedia contributor, detailed why calling the organisation anti-Arab is an ACCUSATION of the Algerian state against it and not a position attributed to it in French media, Skitash proceeded to ignore the comment.

    All actions by the movement are classified as terrorist activity and my request to introduce a POV tag was dismissed despite all discussions since 2023 pointing to a need for it.

    I hope this can be solved as it is sad that the article is being held hostage.

    This pattern of behaviour is repeated in other articles related to Berbers and Morocco.— Precedingunsigned comment added byDaseyn (talkcontribs)23:02, 14 December 2025 (UTC)[reply]

    • (I'm only replying because they quoted something I said) The OP (who is clearly assuming bad faith) is referring to a comment I made in March 2023 (a reply to a disruptive editor/confirmed sock who laterstarted a RfC that didn't go their way). The rest of this hollow report (about content dispute) doesn't deserve a reply.M.Bitton (talk)23:32, 14 December 2025 (UTC)[reply]
    After my comment,they added more to their hollow report. I'm done here.M.Bitton (talk)23:52, 14 December 2025 (UTC)[reply]
    Isnt this stale?shane(talk to me if you want!)00:03, 15 December 2025 (UTC)[reply]
    This is stale.shane(talk to me if you want!)00:03, 15 December 2025 (UTC)[reply]

    Skitash and Bitton's behavior to prevent conflict resolution through intended mechanisms (WP:3O) and (WP:WIKIHOUNDING)

    [edit]

    Is it possible to call Skitash to order, having twice violated the following:[94][95]:Third opinions must be neutral. If you have had dealings with the article or with the editors involved in the dispute that would bias your response, do not offer a third opinion on that dispute.. Skitash is not among the users who volunteer to provide a third opinion[96].

    • Likewise here Skitash removes all other sources from eminent specialists (Camps, Berber Encyclopedia...) initially under the pretext of a bad translation, then to replace it with information (sourced from a guide on Libya)...[97]. It removes the appropriate content instead of simply adding the part it finds relevant (WP:PRESERVE).

    As for Mr. Bitton :

    • he is again engaging in POV-pushing in the articleKabyles hadra where he invents a WP:OR (claiming the term is a 19th-century French invention) and refuses to justify it with a page or citation. This claim was challenged on the talk page, and a request was made for a specific citation (page number or source). No source was provided, and the claim was maintained. The arrival of Skitash prevents any other opinion, and this duo behaves likeWP:OWN


    For both :

    • The usual practice of removing all Berber language designations from place names in Algeria[98]... the recent example is the province of Sétif. It should be noted that this has been a constant since 2022...[99] with the same modus operandi: 1) request the source; 2) when it is provided, telling that the Berber language is dismissed as UNDUE and insignificant compared to Arabic, which is allowed to be used...

    This behavior amounts toWP:POV-pushing,WP:WIKIHOUNDING,WP:HARASS, and prevents any consensus by remaining isolated with these two contributors, who stifle any outside opinion from offering a neutral perspective. It is absolutely impossible to develop even the simplest page on Berber culture because these two editors preemptively initiate conflicts. A quick look aten:Kabylia (compared to its French equivalent) is enough to demonstrate this. I try to avoid these two contributors as much as possible, but they are clearly following me and my contributions through my history, prevent any resolution of editorial conflicts, and want to take away the pleasure of editing from others.I'm not talking about content, but about behavior.Monsieur Patillo (talk)00:11, 15 December 2025 (UTC)[reply]

    This is the third report Monsieur Patillo has filed against me in a month,[100][101] all over the same content disputes. Every single one has been closed as not a matter for ANI, and Monsieur Patillo hasclearly been told to "not continue to use ANI to address content concerns" yet here we are again. This tells me they'reWP:FORUMSHOPPING and repetitively raising the same issue to try force their edits.
    As for 3O, they keep prematurely opening 3O requests claiming a "two-editor deadlock" without awaiting further input from other editors, thentry "nullify" my opinion when I weigh in as the third editor they were looking for. An uninvolved editor has repeatedly told them that they're not entitled to be satisfied in this regard.[102][103]
    "they are clearly following me" Nonsense. Editing the same North African articles (that were on my watchlist long before the OP edited them) doesn't mean I'm "following" anyone. I'm editing my topic of interest, and reverting unhelpful changes isn't hounding. I'm not going to address the details of those edit disputes as ANI isn't the right venue and they're all subject to debate and tied to existingRfCs or policies and guidelines.Skitash (talk)00:40, 15 December 2025 (UTC)[reply]
    This report is based on new information regarding Bitton's behavior (who, when questioned about his sources, deliberately chose not to answer; he has previously been sanctioned for POV-pushing) and the use of conflict resolution mechanisms, rather than the underlying content conflicts.
    Specifically, my concern relates to the use of the WP:3O process in a context where an editor who had previously contributed to the article and was in conflict with the same editors provided, or effectively closed, a third-party review, contrary to the requirement that third-party reviews must be submitted by uninvolved editors. This use of the WP:3O process had the effect of shutting down the discussion and preventing any neutral external input and improvement of the situation.
    Furthermore, a mechanism for monitoring my activities is indeed in place. For example, how can it be explained that Skitash, who almost never provides outside opinions and is not registered as a contributor, nevertheless manages to provide two opinions in one week on a different editorial, one on Bitton and the other on me. How can we explain that recently created articles are the target of disruptive changes? This is aWP:BATTLEFIELD type behavior.Monsieur Patillo (talk)01:08, 15 December 2025 (UTC)[reply]
    refuses to justify it with a page or citation as I explained: the source is based on what the French claimed in the 19th century (Étienne Carette, etc, with the usualKabyle myth stereotypes/racism to boot).
    The arrival of Skitash I thank them for answering the question that you refused to answer. The author that you cited to make a baseless claim about present-day Algeria and Tunisia was an administrator during the colonial period. The real question is why would you such a source and then refuse to answer the question about who the author is and what their credentials are?
    the recent example is the province of Sétif you were asked to explain how you extracted theWP:OR from an image. Where in that image does it says that the inscription name in Tifinagh is Kabyle and since when is Kabyle a written language with any official status in Algeria (asyou claimed in your edit summary)?
    Since the battleground behaviour continues, I will pingToBeFree, the admin who unblocked you with formal restrictions (which as I understand them, include not calling someone a POV pusher).M.Bitton (talk)01:11, 15 December 2025 (UTC)[reply]
    (ToBeFree blinks.)01:22, 15 December 2025 (UTC)[reply]
    Without formal restrictions, that was. With expectations. There seems to be a proposal below enforcing them.~ ToBeFree (talk)01:24, 15 December 2025 (UTC)[reply]
    My bad (I misread it).M.Bitton (talk)01:28, 15 December 2025 (UTC)[reply]

    One Way IBan

    [edit]
    • It is clear that Monsieur Patillo will not heed feedback advising them that this is not a matter for ANI. As such, propose a one way IBan preventing MP from interacting with Skitash who, as noted above, has not been found to be in the wrong. This is probably the only option short of an indefinite block to make it clear to MP that their behavior is inappropriate and disruptive.StarMississippi01:03, 15 December 2025 (UTC)[reply]
      support as proposer. Enough is enoughStarMississippi01:04, 15 December 2025 (UTC)[reply]
      I still support, but am aware it may not be as clear cut as I first thought. I'll revisit tomorrow if needed.StarMississippi01:52, 15 December 2025 (UTC)[reply]
      I am not a vandal or a contentious user. I have already improved numerous articles on other projects[104][105]. I have also created articles here. I submitted ANI (and I realize it might have been excessive) because I felt harassed by the type of behavior described. But I don't have a personal dispute (my use of WP:30 is precisely to prevent this, hence my feeling of injustice). I regret if my request seemed excessive. My only request is to be able to improve the articles on the Berber world.Monsieur Patillo (talk)02:01, 15 December 2025 (UTC)[reply]
      Support they were warned about bringing this back to ANI. Three times is too many times to make such a mistake.LuniZunie(talk)01:07, 15 December 2025 (UTC)[reply]
      They have not only deleted Berber related content but M. Bittons has made racist remarks about Berbers, he has messaged[image link redacted byasilvering (talk) 01:34, 15 December 2025 (UTC)] This is deeply troubling normalisation of racism.Daseyn (talk)01:12, 15 December 2025 (UTC)[reply]
      I'm sorry, but I understood the warning was for editorial reasons. If this bothers ANI, I wasn't aware of it, and in good faith, it was a procedural matter (I tried all possible conflict resolution methods). I can withdraw my request and won't bother the administrators again. This will be the last time... I only want to contribute to improving articles on North African culture and don't want any trouble (nor was I aware that this ANI would cause so much trouble for the administrators).Monsieur Patillo (talk)01:13, 15 December 2025 (UTC)[reply]
      I also ask that you take into account that I have avoided any publishing wars...Monsieur Patillo (talk)01:15, 15 December 2025 (UTC)[reply]
      @Star Mississippi, there is some clear merit to the case if, as the initial post suggests, Skitash has responded to a request for a 3O in disputes where one of the two editors was M.Bitton, or vice-versa. --asilvering (talk)01:18, 15 December 2025 (UTC)[reply]
      I agree with asilvering.Andre🚐01:28, 15 December 2025 (UTC)[reply]
      Actually, it was done twice. I went through 3O precisely to avoid personalizing the arguments and to get a neutral reviewer...Monsieur Patillo (talk)01:30, 15 December 2025 (UTC)[reply]
      I do think that if Skitash is removing a listing on 3O saying "involves 3 editors" but previously it had been between Patillo and Bitton, that is a misuse of the 3O as Skitash is not neutral. They could participate but removing the listing on 3O is inappropriate if it was a 2 editor dispute when added.Andre🚐01:58, 15 December 2025 (UTC)[reply]
      The issue is that Monsieur Patillo often prematurely resorts to 3O without allowing other editors the chance to weigh in. E.g., byrequesting 3O just over an hour after theystarted the talk page discussion onTalk:Kabyles hadra, they are essentially attempting to declare my expected comment "non-neutral" and invalid of acting as a third opinion, which I'd argue is misusing the 3O system which is meant for actual two-editor stalemates. This explains why they previously approached another editor explaining why my opinion "doesn't count"[106] instead of responding to my argument.Skitash (talk)02:17, 15 December 2025 (UTC)[reply]
      Since unfounded accusations are being leveled against me again, let me clarify. The articleKabyles hadra is a new and still orphaned article. There's little reason for other people to stumble upon it spontaneously (recent article, few redirects...), so I'm looking for neutral opinions...
      • The WP:30 rule allows for broadening the debate without personalizing it, with a neutral and unbiased contributor (which Skitash is not, contrary to the recommendationsWikipedia:Third_opinion#Providing_third_opinions).
      • Misrepresentation of sources is an issue of editor behavior, not the editorial content itself. I've summarized everything on the article's talk page[107]. In this case, the claim “invented by the French” is not supported by Kitouni (2013, pp. 10–14); relevant excerpts are provided in the diffs for verification. I explained everything in detail and took some time to post the excerpts. Kitouni doesn't say that the French invented the term Kabyle hadara, but rather that they ignored it and adopted (not invented) the term Kbail (not Kabyle hadara) to designate any settled mountain dweller (p. 14). It's even stated that the term hadara was ignored (p. 14).
      • You can therefore see the behavior of Mr. Bitton, who was repeatedly contacted to obtain the passage without receiving a response[108][109][110], and that of Skitash (who presents himself as a French speaker) who used the WP:30 mechanism to defend a viewpoint deemed unjustifiable by the source... My request doesn't concern the editorial content (I'm not asking the administrators to agree or disagree with me) but rather the behavior that violates the founding principles (Verifiability and Consensus).
      Monsieur Patillo (talk)11:47, 15 December 2025 (UTC)[reply]
      "There's little reason for other people to stumble upon it spontaneously" Could it not be because you've been linking your new article across tons of articles on my watchlist?
      "WP:30 rule allows for broadening the debate without personalizing it" Again, I think you're missing the whole point of 3O entirely. Its lede clearly states that 3O "is a means to request an outside opinion in a content or sourcing disagreement between two editors. When two editors do not agree, either editor may list a discussion here to seek a third opinion."
      "Misrepresentation of sources is an issue of editor behavior" That's not true at all. M.Bitton absolutely has a point that all the sources you're citing are relying on what 19th century French colonizers have said. What I'd consider source misinterpretation is putting the entire article in present tense as if these colonial claims are current fact. Again, all of this concerns content disputes and you've been warned multiple times against dragging it to ANI.
      "who presents himself as a French speaker" Very persistent baseless jab from you. I don't refer to you as "(presents himself as an English-speaker)" whenever you forget to translate your comments to English.[111][112]Skitash (talk)16:03, 15 December 2025 (UTC)[reply]
      I'm fine to modify. I just think there needs to be a better solution than a recurring thread @Asilvering. (I think the MBitton/Daseyn issue is separate, but if that should be reopened, feel free).StarMississippi01:39, 15 December 2025 (UTC)[reply]
      @Star Mississippi, I have no intention of investigating that myself, in case something similar eventually winds its way to arbcom. I just wanted to make sure you hadn't missed that part, as I am in general concerned about how inexperienced editors have trouble having their concerns taken seriously when reporting experienced editors. --asilvering (talk)01:47, 15 December 2025 (UTC)[reply]
      Please, I have never violated a 3RR. I was simply asking that when I make a 3O, a neutral contributor respond. I will no longer use ANI.Monsieur Patillo (talk)01:51, 15 December 2025 (UTC)[reply]
      Support: Monsieur Patillo has repeatedly brought content disputes to ANI despite having been warned against it. They're also beenindeffed previously for persistently personalizing content disputes.Skitash (talk)01:20, 15 December 2025 (UTC)[reply]
      Why don't you talk about this too, which is entirely part of the case:[113]?Monsieur Patillo (talk)01:35, 15 December 2025 (UTC)[reply]
      SeeLaw of holes.Dennis Brown -01:59, 15 December 2025 (UTC)[reply]
    • Support - Those reports are getting ridiculous at this point𐩣𐩫𐩧𐩨 Abo Yemen (𓃵)15:19, 15 December 2025 (UTC)[reply]
    • Support. Monsieur Patillo keeps bringing content disputes to ANI despite being told not too so a one way IBAN is needed to prevent this.GothicGolem29(Talk)16:14, 15 December 2025 (UTC)[reply]
    • Support - this is clearly absurd and this ANI is the result ofWP:NOTHERE behavior by Monsieur Patillo.Freedoxm (talk·contribs)03:24, 16 December 2025 (UTC)[reply]

    Daseyn allegations

    [edit]

    Edit warring in slow motion

    [edit]

    Slow, but relentless, edit warring atMaccabean Revolt.tgeorgescu (talk)02:11, 15 December 2025 (UTC)[reply]

    They tried to get a discussion going on the talk page, ayear and a half ago. No one responded. Why don't you discuss this content disagreement with them? — rsjaffe 🗣️02:29, 15 December 2025 (UTC)[reply]
    @Rsjaffe: They have been answered, including at their own talk page. They have the view that leather armor does not exist. Well, that'sWP:OR. It does not trump citingWP:RS.tgeorgescu (talk)03:29, 15 December 2025 (UTC)[reply]
    Diffs, please. — rsjaffe 🗣️04:59, 15 December 2025 (UTC)[reply]
    @Rsjaffe:[117],[118],[119].tgeorgescu (talk)05:26, 15 December 2025 (UTC)[reply]
    @Rsjaffe: Why are you saying that "no one responded"? This is false. Look atTalk:Maccabean_Revolt#Leather_armor?. I even went and pasted a substantial excerpt of a serious scholarly source. There was no responsefrom Pudiok. Many of Pudiok's removals also lacked edit summaries and also ignored the detailed explanations in reverter's edit summaries. (That said, I agree that this was a poorly prepared ANI statement - tgeorgescu, please do not make others do the research, include the diffs and a summary in the first report.)
    Note that this may be a widerWP:CIR issue, as this editor's contributions elsewhere also do not appear to be reliable, e.g. atSlavery in Poland. But I will ping@Aciram: for more on this.SnowFire (talk)
    Well, the usual complaint is that I speak too much.tgeorgescu (talk)08:28, 15 December 2025 (UTC)[reply]
    My mistake. For some bizarre reason, all I saw was the first post in that thread when I opened the talk page. I have pblocked @Pudiok from that page for unsourced edits, and further action will await further diffs and discussion.
    Diffs do help. I had to do my own research to figure out what was behind your complaint, and obviously missed some big things doing so.
    Diffs are not equivalent to "speaking too much". — rsjaffe 🗣️11:45, 15 December 2025 (UTC)[reply]

    Editing to make maps appear in thousands of articles, against a previous RfC conclusion

    [edit]

    In 2020,Wugapodes closedan RfC, finding that "mapframes should not be on by default". Later on, Joy started to add mapframe support to various infoboxes, but violated this rfc conclusion by making the maps appear by default. Did she try to find out if a majority of editors who use these templates wanted the automatic feature? Or try to get a new consensus from the broader Wikipedia community? No she just started doing it, in theory that it would help readers, even though the one case where I noticed it, it was the opposite of helpful.

    I didn't remember this prior rfc when I brought the issue up on the village pump, whereuninvolved editors were unanimous in disapproving of how Joy's edits made the mapframes appear into many articles.

    I wouldn't have come here if there was some indication that Joy was willing to listen when other editors disagreed and change her approach, but that doesn't seem to be the case.

    Templates are heavily restricted from editing precisely because they have wide implications when edited and comparatively few watchers who could notice a change. I do not think that someone who has this attitude towards consensus should be trusted with template editor permissions. (t ·c)buIdhe03:50, 15 December 2025 (UTC)[reply]

    The 2020 question had a lack of consensus, so the status quo (off by default) was the outcome. It wasn't a positive consensus in favor of being off by default, and that's my mistake for bolding that part of the rationale rather than the no consensus part. 5 years later, I don't think this is a strong enough RfC to base decisions on. A lot of the off-by-default rationales are based on facts that are no longer true about Wikidata. For example,RexxS (among others) raised issues with Wikidata changes not showing up on local watchlists. At the time, that was a big problem for quality control and a vector for subtle, yet highly visible vandalism. That has since been fixed, and it would be enough for me to close this differently had it taken place today. The other major topic of discussion was whether these default maps would be generally useful for historical subjects, andJoe Roe's rationale seemed to influence the discussion on that point toward default on. Add in the couple "leave it to each individual infobox" comments, and I don't think that close is particularly binding on us now. Too much has changed.
    On the behavioral issue, it does look like Joy is still trying to be constructive.On 8 December in the template talk discussion they proposed a specific default in response to the discussion and got little feedback.A few hours ago (14 Dec) at the village pump Joy proposed further configuration options to try and synthesize the feedback in that discussion. Despite the amount of back-and-forth this past week, Joy is still trying to productively chart a path forward when other editors have been dropping out. I don't think there's anything worth immediate sanctions, but hopefully more editors take a look and some kind of consensus can be reached on what to do.Wug·a·po·des04:50, 15 December 2025 (UTC)[reply]
    I don't see a problem with support being added but changing it to be auto enabled is worth aWP:TROUT. I don't see a broad enough pattern of disruption to warrant any sanctions, at least not yet.DarmaniLink (talk)06:39, 15 December 2025 (UTC)[reply]
    First of all, I am listening! I have engaged you about this specific question and a variety of other questions. I'm not trying to do anything beyondWP:CAUTIOUS. You can also see how I documented specific measures of caution atWikipedia:Mapframe maps in infoboxes#Process. (Don't have a specific diff, it's inside[120])
    I do not really make them appear by default, rather, what I did was under the premise that they still require 1) that a coordinates field is present in the infobox and 2) that there are no other maps in there and 3) that there's no indication of controversy about maps in each infobox's template talk page and history and 4) that it passes the common sense test - such as that geographical information is relevant as opposed to weird in each infobox.
    So in a lot of cases it did start showing up, but in a lot of cases it did not. It's a far, far more limited and gradual deployment than a site-wide default to on, which would have been the thing that RFC outcome would not support - to my best understanding. In case of the civilian attack infobox, all I found wasTemplate talk:Infobox civilian attack/Archive 1#Location map, so I proceeded while explicitly excluding all instances where that map was present. Wherever the coord template was outside of the infobox, it wouldn't render, and wherever I found faulty values inside cooordinates parameters I'd fix them.
    Thinking about this now, I double-checked a bit, and got a bit of whiplash, because I think we've actually stumbled on a fresh issue withModule:Infobox mapframe that I wasn't aware of. The civilian attack infobox doesn't specify|mapframe-wikidata=, yet it rendered a point from Wikidata in that infamous Namibian case. I was under the impression that I had caused this behavior by specifying the parameter, so I analyzed that situation from that perspective, but actually I didn't. @Hike395 did one of the recent logic changes at the Infobox mapframe module inadvertently enable Wikidata by default?
    Anyway, back to the general process issue. With all these changes, which added probably thousands of useful map thumbnails and links (and likewise didnot add thousands more), I've encountered numerous technical and editorial issues which I've tried my best to address. In turn, two weeks ago I've brought up a summary atWikipedia talk:Manual of Style/Infoboxes#styles of showing geographical location in infoboxes. Sadly, there's been little interest.
    I don't think this project is being disruptive, because for my part I'm doing my best to do my due diligence, fix the various bugs, stop and listen to people like yourself and try to improve things. It's not meant to piss people off, on the contrary. You have to notice how I did not object to yourpartial revert at Infobox civilian attack. That's a perfectly normalWP:BRD revert - you think the change was too bold, but even if I disagree, I am not going to do anything other than discuss it.
    As it happens, I didn't proceed with adding mapframe support to any other infoboxes recently as we've been having these discussions, both because it's time-consuming and hard by default, and also because I've recently spent a lot of time discussing it (in addition to doing other things).
    On a more philosophical note, it's actually been refreshing to be able to talk about it more, because in most other cases nobody really noticed, which is sort of sad. I do maintain hope that readers have on the whole noticed and it's helped people. For comparison, over the years, I have been adding manual mapframe=yes etc to a variety of bigger settlement infoboxes, whose articles probably have more readership than the infoboxes where I've been adding this to recently, but there's never been a whole lot of feedback. So it was mostly toiling away, and I have to say I am genuinely thankful to yourself and others for this recent swell of activity, even if it means me coping with negative feedback :) I'm sorry that I did annoy you too much on the whole.
    Also, not a she, but a he :) --Joy (talk)12:06, 15 December 2025 (UTC)[reply]
    I understand you are at least replying but there seems to be a general unwillingness for accept that many editors don't support these sweeping changes, and the wall of text strategy is not helping. (t ·c)buIdhe14:20, 15 December 2025 (UTC)[reply]
    I don't know, there seems to be only a handful of us, while the reader views are in the thousands and millions, so it's hard to figure out if we're representative either way.
    I'm aware I can be overly verbose. It's not an attempt to be annoying, rather, I wouldn't like it if anyone thought I was doing stuff based on just vibes, so I try to explain and work out various elaborate scenarios. --Joy (talk)14:33, 15 December 2025 (UTC)[reply]
    BTW, one of the reasons why I assumed we just enabled Wikidata there is that I've seen it done elsewhere. For example,museum infoboxes have been doing that according to very bland local consensus, for two years now. That's potentially up to four thousand museum articles where Wikidata coordinates could be showing implicitly (11,820 -7,767 = 4,053), and nobody's reported any problems. So when I seeroughly half as many civilian attack articles in a similar situation, that's why I'm not very alarmed. But that's the extent of the nonchalance - I'm not trying to be insensitive to complaints, rather I'm trying to understand them in context. --Joy (talk)10:46, 16 December 2025 (UTC)[reply]
    It’s almost like museums are places that are trying to encourage public access or something…~2025-41131-63 (talk)13:02, 16 December 2025 (UTC)[reply]
    Exactly. Likewise, I think that a location of a civilian attack is something the typical reader benefits from illustrating. --Joy (talk)15:32, 16 December 2025 (UTC)[reply]
    Anything to reduce the use of those giant maps in infoboxes is appreciated. Few are of any use, and on most or many articles they take up an undue amount of space for little useful real information in return.Randy Kryn (talk)15:37, 16 December 2025 (UTC)[reply]
    Which ones are the giant ones, the static ones? With mapframes, the common infobox thumbnail sizes are something like 250x250 pixels. --Joy (talk)15:40, 16 December 2025 (UTC)[reply]
    The infobox maps usually point to, a state?, a country, etc. Kind of like the use of map coordinates on pages for someone trying to find the Washington Mounument. You know it when you see it, doesn't have to be mapped out.Randy Kryn (talk)15:45, 16 December 2025 (UTC)[reply]
    What do you think would be a good default location description for a typical civilian attack article? How much assistance does the average reader need to placeRussell Street,Cienaga, or theLa Belle disco? --Joy (talk)18:31, 16 December 2025 (UTC)[reply]

    User:1RightSider – repeated personal attacks and disruptive conduct

    [edit]

    I am requesting administrator attention regarding repeated personal attacks and disruptive behavior by User:1RightSider in the context of an editorial dispute atBolzano.

    Instead of focusing on content, the user has repeatedly used edit summaries to make accusations against me, including claims of "nationalistic edits", "discrimination", "bias", and "harassment", without providing diffs or evidence. These comments were made in article edit summaries, not on talk pages, and are not related to describing edits.

    Relevant diffs:

    • diff link 1 – accusation of “nationalistic edits” and “discrimination”
    • diff link 2 – allegation of harassment and instruction not to post on their talk page
    • diff link 3 – repeated personal commentary in edit summaries

    This behavior appears to violateWP:NPA,WP:CIVIL, andWP:AGF. It has also disrupted attempts at dispute resolution, including ignoring the outcome of a DRN closure that explicitly allowed me to edit boldly.

    I am no longer engaging directly with the user and am requesting administrator guidance to restore a civil, policy-based editing environment.

    --Simoncik84 (talk)10:37, 15 December 2025 (UTC)[reply]

    Please don't use an AI to formulate an ANI complaint. Among other things, you've statedThese comments [...] are not related to describing edits and then the first diff you link is you complaining about them describing your edits as nationalistic; so evidently theyare describing your edits.
    Please reformulate this complaint inyour own words and add it as a reply. Nobody here wants to engage with whatever your chatbot thinks the problem is, we want to hear whatyou think the problem is.Athanelar (talk)11:07, 15 December 2025 (UTC)[reply]
    I think that I should clarify what I said.User:Simoncik84 filed twoDRN requests aboutBolzano withUser:1RightSider as the other editor. 1RightSider didn't answer either of them. The filing editor didn't notify the other editor of the first filing, and didn't notify them four days after I said that notification was required, so I closed the dispute. The second time, they did provide proper notice, and 1RightSider still did not respond. Since participation in DRN is voluntary, I closed the dispute as declined, and said that Simoncik84 could edit the articleboldly, but should discuss on the article talk page if there were objections to their edits. That wasWikipedia:Dispute_resolution_noticeboard/Archive_266#Bolzano. I now see that 1RightSider is only discussing via edit summaries, which is not real discussion. I was willing to try to mediate, but it seems that we have one editor who only communicates in edit summaries, and another editor who appears to be usingartificial intelligence to complain about communicating only in edit summaries.Robert McClenon (talk)22:37, 15 December 2025 (UTC)[reply]
    Thanks for the comments. I understand the concern and I'll explain the situation in my own words. The underlying issue is an editorial disagreement about whether "Bozen" qualifies as a bolded alternative name in the lead of the Bolzano article under MOS:BOLDALTNAMES. My position has consistently been that the sources provided do not demonstrate sufficient English-language usage to justify bolding, and I raised this on the article talk page in policy-based terms. What brings this here is not the content dispute itself, but how the discussion has broken down. After extended talk-page discussion and two attempts at DRN (where participation by the other editor did not occur) the disagreement has continued through article edits accompanied by edit summaries that attribute motives to me, for example describing my edits as "nationalistic", "biased" or "harassment"). My concern is that substantive editorial disagreement about sourcing and MOS compliance has been replaced by characterizations of editor intent, often made in edit summaries rather than on the article talk page, where they could be discussed or addressed. This makes it difficult to resolve the issue constructively. I am willing to continue discussing the question of "Bozen" on the article talk page, to follow consensus, or to pursue appropriate content dispute resolution. What I am seeking here is guidance on how to proceed when a policy-based editorial dispute escalates into personal accusations and discussion no longer takes place on the talk page.Simoncik84 (talk)11:17, 16 December 2025 (UTC)[reply]
    You wrote this reply with AI as well. Good lord.Athanelar (talk)11:30, 16 December 2025 (UTC)[reply]
    I'll explain the situation in my own words ... said a chatbot. I'm unimpressed and unpersuaded.Narky Blert (talk)15:39, 16 December 2025 (UTC)[reply]
    AI slop neither maintains nor improves Wikipedia.Narky Blert (talk)18:17, 16 December 2025 (UTC)[reply]
    IAR in terms ofblocking the user. It would be IAR to block the user by sole reason of LLM or that reason just obfuscated with DE and CIR.~2025-31733-18 (talk)19:54, 16 December 2025 (UTC)[reply]
    It's generally agreed upon (WP:LLMCOMM) that continuing to use AI for user-to-user communication, especially after being told to stop, is a CIR issue. I don't think sanctions would be unwarranted here.Athanelar (talk)18:51, 16 December 2025 (UTC)[reply]

    Anti-immigrant POV pusher won't leave me alone

    [edit]

    A few days ago this user out of pretty much nowhere started reminding people posting automated notices onKoavf's talk page that they are banned, and when replying to a notice I left about a redirect discussion also tacked on along rant about Justin Trudeau's immigration policies, a talking point of Canadian far-right groups. Iadvised them that I was removing part of their message that was a BLP violation and that Wikipedia talk pages are not a forum for political debates. They then decided to expand on and defend their ranton my talk page, blaming immigrants for all of their personal problems and insisting that I must also be experiencing the same issues due to immigration because I am also Canadian. Iadvised them somewhat more pointedly that Wikipedia is not a soapbox for political advocacy, and to stop bothering people with these comments. I do seem to be the only one they've selected for this, though.

    Today I woke up tothirteen notifications from additional messages this person posted on my talk page, all buildingthis new rant still complaining about immigrants. As far as I can tell I have never interacted with this person before, and generally don't edit any topics where someone would be coming at me with political hot takes like this. They also don't seem to have an interest in editing this topic, they seem to be mostly interested in Egyptology. The one exception is that I have been active in discussions on the articleremigration, which is now also starting to be pushed by western Canadian far-right groups, and so I can't get past feeling as though this is targeted political harassment.

    I would like this person banned from interacting with me, and propose that they be topic-banned from content about immigration on Wikipedia.Ivanvector (Talk/Edits)13:23, 15 December 2025 (UTC)[reply]

    I'm not sure why you thought it was a good idea to continue doing the same thing here.Athanelar (talk)15:02, 15 December 2025 (UTC)[reply]
    • Comment: Isaid in my message: "This is my last message to you. If you had even seen my userpage, you will have noticed that "I AM an Immigrant who was born in Malaysia." My parents and our family legally immigrated to Canada in 1989 under PM Mulroney but too many immigrants who come in a short period of time drives everyone's wages down and pushes housing prices or rents up which JT never considered. I used to work at the Langley, BC Real Canadian Superstore or "Loblaws" in Metro Vancouver between 1998 to 2008 when all the cashiers positions were manned by young women--who got many long hours and a good salary--but today most of them have been automated out of a job by self serving machines. So, what are young women supposed to do today to even earn money or afford a condo? I thought I could have a conversation with a fellow Canadian in PEI...on the cost of living and low wages...but I was wrong. I am sorry. It is my mistake."
    • Ivanvectorsays wants to ban me from interacting with him...and I have already said I will do so. He is likely doing well financially as an accountant but most Canadians are struggling financially in 2025. Hopefully, he and his family will be able to afford a home or even food in the future. Everyone in the world says that Canada is a beautiful country but I don't think they read this Recent December 2025Global News.ca article which saysthat nearly 25% of people in the Province of British Columbia, Canada--where I live in Metro Vancouver--have to go to Food Banks just to feed their family even with "full-time jobs" due to rising food and housing prices. Can you imagine the crushing stigma of using a food bank to feed your children? People can barely afford to feed their families today in Canada let alone afford a home or shelter. As for immigration, I told Ivanvector that I am an immigrant from Malaysia. If he wants me to be topic banned from talking abut immigration on wikipedia--even though I am an immigrant--that is fine with me.Canada is a beautiful country to visit, but if you stay here, you face the risk of homelessness or barely being able to feed your family, let alone having to save enough or any funds for retirement. This problem affects all of Canada and not just British Columbia. Thank You for your time, --Leoboudv (talk)14:28, 15 December 2025 (UTC)[reply]
    • What was the context where, per the commentary you provided in the edit, on seeing another user was from Canada, you thought it appropriate to provide a paragraph complaining about housing prices and providing your opinion on who was to personally blame for such? --Cdjp1 (talk)14:44, 15 December 2025 (UTC)[reply]
    • DearCdjp1,
    • On December 14, 2025 I made this comment on Ivanvector'stalkpage:
    "Dear User Ivanvector,

    You were correct to "edit" my comments on Koavf's talkpage but unless you own a home, townhome or condo which you bought perhaps 15 or 20 years ago, many Canadians are facing an impossible housing situation sadly. If you see this 2025 rates.ca article:https://rates.ca/resources/how-much-money-do-you-need-to-buy-home-canada , it clearly says that a single homebuyer must earn $255,000 to even get a stress tested loan for a single family home in Metro Vancouver whereas in Metro Toronto, its $232,000. Halifax is a bit cheaper at $129,000 but the problem is anyone who earns an income that high faces an income tax rate of about 45-50+% in Canada.

    I presently work as a real estate appraiser in Metro Vancouver and had to take a rear photo of a brand new high rise condo in August 2025...and sadly, there [were] 3-4 homeless people sleeping on the ground near the area where I had to take the photo inSurrey, BC within Metro Vancouver...which was in front of a neighbouring low rise condo. Most people cannot afford to buy single family homes today in Metro Vancouver and it was never this bad under PMHarper orChretien who kept immigration at between 250,000 to 310,000 a year. Townhomes and Condos are not cheap either today...not including strata. Inflation has impacted real estate prices. Both PM Chretien and Harper kept a reasonable and stable volume of immigrants to Canada until JT decided to increase it to almost 500,000 a year until Canadians had a backlash to his policiesas the BBC reported here. The price boom happened with investor speculation on condos and with JT dramatically increasing immigration rates. So, JT--in his last year in power--finally cut immigration rates throughout Canada which has resulted in falling rents...but the problem is with inflation after covid, food and housing has stayed so much more expensive. I remember in the 1990s that some left wing activists in BC who did not like Walmart Canada expanding into their city or municipality complained about "the high cost of low prices" but today everything is expensive...and many people go to Dollarama or Costco--which incidentally is a US company for more value--just to get more value or to survive the hit to their wallet. Few people can afford to eat the recommended healthy Italian or Greek diet of olives and fresh vegetables which are quite expensive...."

    • JT refers to the former Canadian Prime MinisterJustin Trudeau and my source about the impact of high rates of immigration to Canada comes from this late October 2024BBC source As an aside, I have Never edited a single wikipedia page on immigration at all and feel a topic ban on immigration is illogical for a subject I never edited. I have always said I was born in Malaysia even in myCommons account in the 1970s and 1980s. In 2017, I visited Malaysia and took a few photoshere of the streets of KL andhere andhere Unfortunately, I did not correct the camera metadata in 2 of the photos...but the street photo has a sign which says 19-22 October 2016. Best, --Leoboudv (talk)15:14, 15 December 2025 (UTC)[reply]
      This doesn't really help, as this is just continuing the discussion that your brought up ex-nihilo. --Cdjp1 (talk)15:43, 15 December 2025 (UTC)[reply]
    • Whether Leoboudv is an immigrant or not should have no bearing on our decision to place interaction or topic bans on her. That decision should be based solely on her actions, which per Ivanvector have persistently violatedWP:NOTFORUM. She seemed to have understood this above ("I thought I could have a conversation with a fellow Canadian in PEI...on the cost of living and low wages...but I was wrong. I am sorry. It is my mistake."), but then went on to post another paragraph of off-topic ranting. As such, Isupport a one-way interaction ban between Leoboudv and Ivanvector, though what we really need is for Leoboudv to understand that discussions on Wikipedia are for discussing Wikipedia and nothing else. Ioppose a tban, as I see no evidence that she edits disruptively in that topic area.Toadspike[Talk]14:45, 15 December 2025 (UTC)[reply]

    I wish to reiterate One Final Time that I have NOT edited on any racist immigration topics on wikipedia. Instead, I was highlighting theEconomic impact of sudden Legal mass immigration to Canada with increased housing and food costs and the increased demand at food banks--not to the US or any other country. Secondly, I have strongly ANTI-racist views from my days at University. If I had racist views, I would not have posted thisabsolutely clear edit about Musk's racist Grokipedia project or his vile praise ofHolocause denier David Irving. Today Trump wants US immigration to treat white South Africans as refugees...which is total BS. A Topic Ban on immigration for me is meaningless as I have never mentioned or broached the subject. I don't even do disruptive editing to wikipedia articles. So, a ban between contact between me andIvanvector is right but not a topic ban. Thank You and Goodnight to you all, --Leoboudv (talk)17:21, 15 December 2025 (UTC)[reply]

    @Leoboudv: Wikipedia isn't a forum for your musings on immigration, immigrants (good or bad), or real estate, and certainly not for rambling discussions of the impact of immigration on real estate, either in Canada or anywhere else. "as he brought in too many immigrants into Canada" certainly looks like anti-immigrant soapboxing. That you chose to continue to post your commentaries here at ANI *twice* doesn't convince us that you understand the problem with your conduct. Leave Ivanvector alone. If you persist in posting commentaries, you will face additional editing restrictions. Just stop.Acroterion(talk)18:02, 15 December 2025 (UTC)[reply]
    • I would like to apologize to Ivanvector for the tone and passion of my messages. I will never ever contact him again in any capacity. I did not know he even existed before seeing his automatically generated message onKoavf's talk page. I have NEVER edited any articles on immigration in my 20 year history on wikipedia (anyone can check if they wish) and I am sorry that my behaviour led to this ANI. ThanksUser:Acroterion for your advice....to stop digging when one is in a hole. Kind Regards, --Leoboudv (talk)09:05, 16 December 2025 (UTC)[reply]

    Editor overlinking, using odd link format, with cryptic edit summary "#STEMART"

    [edit]

    Noila'snancy1 (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log)

    This editor is on a spree of overlinking, linking common words such as "musician" and countries such as "Nigeria" and to some dab pages, and has not responded to two posts on their talk page but is continuinng to edit at a rate of an article every couple of minutes.

    They are using an odd format for their links: adding [[w: Egypt|Egypt]] rather than [[Egypt]].

    And their edit summary is always #STEMART, which makes me concerned that there might be some sort of project or competition aiming at linking as many terms as possible regardless of whether they should be linked - I searched en.wiki "all namespaces" but couldn't find this hashtag mentioned.

    They've edited five more pages since I last looked, the most recent being another link to a dab page. Please stop them until they have at least read their talk page.PamD13:44, 15 December 2025 (UTC)[reply]

    #STEMART →meta: Event:Wikipedia Edit-a-thon Challenge.ltbdl (skirt)13:48, 15 December 2025 (UTC)[reply]
    Thanks, @Ltbdl, that explains. But it looks as if this challenge should have put more effort into ensuring that editors learned about editing before letting them loose trying to "improve" articles.PamD15:47, 15 December 2025 (UTC)[reply]
    Not particularly promising, but also you posted your first note for them at 13:25, they stopped editing at 13:43, and it is currently 13:52. Give them some time to respond. They have responded to other messages on their talk page so this doesn't seem to be a case of a user ignoring warnings, not yet anyway.Ivanvector (Talk/Edits)13:53, 15 December 2025 (UTC)[reply]
    If you are on a break from the contest, just explain what you did, Noila. Be aware of what those edit summaries you made. That contest is not aspeedrun contest, don't rush.Ahri Boy (talk)14:23, 15 December 2025 (UTC)[reply]
    Also, I informed everyone who reads the event's talk page on Meta to participate in the discussion.Ahri Boy (talk)14:40, 15 December 2025 (UTC)[reply]

    I just did a cleanup run on those w: links. --SarekOfVulcan (talk)17:31, 15 December 2025 (UTC)[reply]

    Well they have given up on the links, but have now moved on to adding infoboxes to Egyptian BLPs. The ones that I've checked have added unsourced information (usually someone's citizenship) and sometimes information that contradicts references in the article. I have warned them to be more careful, but they did not respond to the earlier message, so we may indeed be heading in the direction of a block. I have advised the talk page of the editathon.Ivanvector (Talk/Edits)18:55, 15 December 2025 (UTC)[reply]
    I have seen multiple edits marked #STEMART on my watchlist, adding infoboxes. Most werebad infoboxes that gave highly inaccurate summaries of article content (e.g. listing a single non-current employer as the only employer; claiming citizenship in countries that the subject was associated with but for which citizenship had not been established). The ones I saw were all byUser:BigDareLibrary, notUser:Noila'snancy1, presumably part of the same editathon. —David Eppstein (talk)19:05, 15 December 2025 (UTC)[reply]
    I had a feeling there would be other accounts. We may need an edit filter temporarily to catch edits from this apparently poorly-planned editathon.Ivanvector (Talk/Edits)19:10, 15 December 2025 (UTC)[reply]
    The project page on meta, linked above, includes a list of particpants and their achievements (you need to click "expand". Yes, BigDareLibrary is there.PamD20:44, 15 December 2025 (UTC)[reply]

    User:Jabji CIR & refusal to DROPTHESTICK

    [edit]

    Jabji (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log)

    Vivian Dsena (edit |talk |history |links |watch |logs)

    Disclaimer that I'm not super familiar with the drama about the article itself. What I do know is I came across this editor asking how to reduce page protection on the article Vivian Dsena at the helpdesk (WP:HD#How to reduce protection from Wikipedia) where they were pointed toWP:RFPP and proceeded to evidently not understand that simple instruction, hence my CIR concern.

    It's also there that I learned the whole reason Vivian Dsena is a protected page to begin with is due to an ANI complaint aboutthis very editor's conduct which led to the page getting a 3 month ECP. See the thread 'Vivian Dsena 2' atthis ANI archive

    This editor has been warned numerous times on their talk page and taken to ANI twice, and proceeds to obviously demonstrate 0 understanding of the issue by asking how they can get the page protection reduced so that they can return to their previous behaviour; and, to boot, demonstrates an inability to follow a single link relevant to their query.

    I think it's inevitable they're going to return to editing Vivian Dsena as soon as the ECP is up, so they should at least be pblocked from there; but given the warnings on their talk page about other articles, maybe a broader tban (Indian public figures?)/siteblock is necessary until they demonstrate some understanding of the issues with their editing.Athanelar (talk)16:26, 15 December 2025 (UTC)[reply]

    Courtesy ping:Ravensfire who made the previous ANI report.Athanelar (talk)16:27, 15 December 2025 (UTC)[reply]
    Support pblock at the minimum. AGF I just don't think this editor understands our policies, and they've never once communicated via a Talkpage.qcne(talk)16:38, 15 December 2025 (UTC)[reply]
    Looks like aWP:CIR issue to me, in addition to all the other issues. If Jabji is still incapable of understanding why the article is protected after all this time, I can see no reason to think they are actually capable of contributing usefully to any other article. a pblock will just move the problem somewhere else. An indef block seems a more sensible option.AndyTheGrump (talk)17:14, 15 December 2025 (UTC)[reply]
    Pblocked fromVivian Dsena. No opinion onWP:CIR issue at this time. — rsjaffe 🗣️18:19, 15 December 2025 (UTC)[reply]
    Thank you! My belief is there's either some extreme fanboi editing or some really badWP:UPE PR work from Jabji. They have been able to use the talk page after ECP and still are, but they haven't taken advantage of that.Ravensfire (talk)19:35, 15 December 2025 (UTC)[reply]

    Byron Comp 3, again

    [edit]

    Byron Comp 3 waspreviously reported here for persistent additions of unsourced content, and were subsequently pblocked from mainspace for a few days. Theyused sockpuppets to evade their pblock, but the master account was never blocked for some reason. Byron Comp 3 returned a few days ago and continues to add unsourced content ([121],[122],[123]), again, with no signs of communication. Can we please get a longer block to stop this disruption? Thank you so much,ChildrenWillListen (🐄 talk,🫘 contribs)17:19, 15 December 2025 (UTC)[reply]

    I have blockedUser:Byron Comp 3 indefinitely from article space for failure to provide sources to support their additions and complete lack of communication regarding issues raised about their problematic editing. I have also informed them of how they can get the block lifted. I'm not closing this thread right away as they may wish to respond to this thread. --Hammersoft (talk)18:57, 15 December 2025 (UTC)[reply]

    BrianH123 is NOTHERE

    [edit]
    HATER BOUNCED

    The following discussion is closed.Please do not modify it. No further edits should be made to this discussion.


    Out of an abundance of caution, I am posting here instead of blocking directly to ensure I am not off base. I believe that BrianH123 isWP:NOTHERE (or, better put, "no longer here"). Their edits over the past two years have been mostly trolling-esque talk page comments, some of which appear to be anti-Muslim:

    Had these edits been a few amongst a number of constructive edits, I would have concluded "net positive" and moved on. But these are 11 of the 15 total edits the user has made in the past 18 months. As such, I suggest that BrianH123 be blocked as NOTHERE.EvergreenFir(talk)19:37, 15 December 2025 (UTC)[reply]

    After a perusal of their edits, I would includethis comment in the pattern of edits, where they arefrankly shocked that such an article manages to exist on Wikipedia. The article is the1947 Rawalpindi massacres where the Muslim National Guard massacred Hindus and Sikhs in Punjab province. --Cdjp1 (talk)22:04, 15 December 2025 (UTC)[reply]

    Would anyone here oppose a topic ban for anything related to Muslims, islam or terrorism? --Trade (talk)22:42, 15 December 2025 (UTC)[reply]

    Hate is disruptive. Indef for DE, in my opinion.Athanelar (talk)23:31, 15 December 2025 (UTC)[reply]
    I'veblocked as NOTHERE. DE also would have worked. I think a topic ban is too kind in this case.StarMississippi00:03, 16 December 2025 (UTC)[reply]
    The discussion above is closed.Please do not modify it. No further edits should be made to this discussion.

    User:Des_Vallee personal attacks and disruptive editing

    [edit]

    SummaryDes Vallee (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log)

    There was a prior dispute regarding the articleJay Jones and the reported user made a personal attack over edits to the lede. The user later made an edit that they agreed with the lede. I made several edits at a later date and the user mass reverts with notes only on one edit. I revert back adding that each revert needs its own reason to avoid edit warring. I then leave a message on their talk page about it. The user then goes on to add a tag which gets changed to an undue weight tag. I revert because there has been no discussion on this. We have a back and forth discussion on my talk page, despite saying this was not a subject for their talk page. I add back the only sentence that was removed from the lede that the user added. User still adds back the notice. The notice summary say there was a discussion on the talk page despite there being a consensus and the user agreeing to the lede

    edit: updated after visiting the user's discussion and also the flowery language they use to describe it as a personal attack was not shared by the other editors

    The fact that there was a personal attack, then a mass revert, and a notice without talk is just disruptive. My impression is that this is over some sort of pride and control. I just want to be able to talk and have consensus without unnecessary escalation.

    Details This is the order of events:The reported user made at least one personal attack towards me on first contact, contrary toWP:NPA.

    The reported user performed a mass revert affecting multiple edits, escalating the dispute rather than following theWP:BRD cycle.

    An undue weight template was added to the article without initiating or participating in talk page discussion, contrary to consensus-based editing expectations underWP:CONSENSUS and even an edit stating agreement with lede

    When this was pointed out, the reported user claimed that the issue had already been discussed and that consensus was reached; however, no such discussion or consensus exists on the article’s talk page. This is related to the prior discussions

    Prior attempts at resolution

    The discussion mention.

    Requested actionAdministrative review of the reported behavior, guidance to the editor regarding civility and consensus-based editing, and any remedies deemed appropriate by the reviewing administrator.

    Relevant diffs

    Contentcreator (talk)22:46, 15 December 2025 (UTC)[reply]

    This is a content dispute brought to ANI. And it's incorrect completely,I have been involved extensively on the talk page, there have been numerous editors who have brought up the issues raised on the lede on the talk, such a comments months ago such asThe lead is a summary of the article. A summary by definition leaves out a great many details, 'very important' or not, relative to the most important primary detail that is summarized there. Secondary details are inserted in the article body. I made a single revert to 5 edits I disagreed which was promptly reverted at which point I didn't revert it I only added a template to the article as there was an active dispute. And when there is an active dispute a template article is positive for that, it was then removed as this user claimed there was no dispute or discussion when there clearly is a dispute and clearly a discussion.Des Vallee (talk)23:00, 15 December 2025 (UTC)[reply]
    Inever claimed a consensus for the lede was reached, I stated there was no consensus for the lede and there was currently a dispute and discussion on the article, the entire point of dispute tags.Des Vallee (talk)23:03, 15 December 2025 (UTC)[reply]
    prior as again you felt it is fine in the past but now there is no consensus
    "After consideration I think the current lede is fine, withdraw nomination"
    https://en.wikipedia.org/w/index.php?title=Talk:Jay_Jones&diff=prev&oldid=1320714866Contentcreator (talk)23:26, 15 December 2025 (UTC)[reply]
    on the topic that you linked it isn't over undue weight and one other person ignores the consensus of prior discussions to which you agreedContentcreator (talk)23:32, 15 December 2025 (UTC)[reply]
    No one Is going against concensus that person is simply stating there concerns with multiple others on that article. You can also change your mind in a dispute. Changing your mind is allowed.Des Vallee (talk)00:08, 16 December 2025 (UTC)[reply]
    Again you are at best conflating issues with "language" vs undue weight assuming the view has changed. You are just ignoring process and procedure creating disruptive and edit warring. Nothing aligns with what you are saying, you just goal post change
    • You describe a personal attack "ContentCreator you have no clue what Wikipedia is" as such, "the previous only thing I commented on was you misunderstand how Wikipedia works".
    • You continue to conflate policy citing rules for removal maintenance ignoring that we never discussed this.
    • You pretend there was no consensus when we had a whole separate section dedicated to this to which you agreed to and was not about undue weight
    • You tell me that your talk page isn't the place to discuss; then proceed to go to my talk page to discuss the same thing
    Contentcreator (talk)00:47, 16 December 2025 (UTC)[reply]
    I posted on the talk long before the template was added that "the lede currently focused way to much on text messages" There is no concensus on the page, 3 editors supported the lede, including a blocked sock. Many others found issue with the lede. I stated going to a talk page is not a place to discuss content, I went to your talk to talk about you removing a dispute tag.Des Vallee (talk)01:09, 16 December 2025 (UTC)[reply]
    Please supply diffs and evidence to support your claims.Contentcreator (talk)01:48, 16 December 2025 (UTC)[reply]
    ok so I stopped counting at 3 but Bob PhD, Anastrophe, me. Who is the blocked sock?Contentcreator (talk)04:40, 16 December 2025 (UTC)[reply]
    @Des Vallee:This edit is unnecessary incivility, and it is not accurate to say that you made a single revert, you've violatedWP:3RR atJay Jones within the last few hours, and have history of blocks related to incivility and edit warring, particularly in thehistorical elections contentious topic area.This comment statingedit warring occurs once an edit have been reinstated and then reverted 6 times. is an extremely inaccurate description ofWikipedia:Edit warring and is contradicted by the edit warring policy. I'm wondering if perhaps a topic ban is necessary here. -Aoidh (talk)00:25, 16 December 2025 (UTC)[reply]
    I have specifically not made any reverts to the article. I apologize for that edit summary I should not have stated it, it was made over a week after this request was made. After there was a revert I only added a template for a discussion on the talk. I am active in that field of editing and I have thousands of edits relating to the vast majority extremely constructive. I don't understand why this is being taken seriously when I am engaged in the talk page, and not making any reverts to the page.Des Vallee (talk)00:32, 16 December 2025 (UTC)[reply]

    I am so glad that apology comes in reply to someone else calling you out and not to me. You had the chance to clarify hours ago and instead you respond with, "the previous only thing I commented on was you misunderstand how Wikipedia works". On this, "it was made over a week after this request was made" and then the next interaction on this page was to mass revert which is an action usually only taken for vandalism.Contentcreator (talk)02:12, 16 December 2025 (UTC)[reply]

    It seems I miscounted one edit as a revert so it's not a brightline 3RR violation, but you are unambiguously edit warring. You do not need to hit "Undo"for it to be a revert, and you have made three reverts on 15 December: at14:52 (revertingSpecial:Diff/1327208507/1327496831),20:23 (revertingSpecial:Diff/1327707248), and21:02 (revertingSpecial:Diff/1327711687), plus two more reverts in last few days. -Aoidh (talk)00:41, 16 December 2025 (UTC)[reply]

    On the subject of this edit warring, mass reverts are when I posted an edit warring response to the user's talk page. Unless you have evidence of Vandalism this is by name discourage to prevent edit warring. When in context with me being a previous editor on this page and with past person attack, I think it constitutes edit warring.Contentcreator (talk)00:59, 16 December 2025 (UTC)[reply]
    I specifically stopped making any reverts afterwards, I left a discussion template on the article for that exact reason. The content which is currently on the article was readded by "Contentcreator." Why should that be taken seriously when I stopped reverting left the article as is and just added a template, so I still don't understand why on earth this is being taken seriously.Des Vallee (talk)01:03, 16 December 2025 (UTC)[reply]
    "Unless you have evidence of Vandalism this is by name discourage to prevent edit warring. When in context with me being a previous editor on this page and with past person attack"
    Why did you do it in the first place?Contentcreator (talk)01:46, 16 December 2025 (UTC)[reply]
    Popping in to share my alarm at one of DV’scomments during the dispute. In the same way that I can’t see any reasonable justification to say that the lead is mostly about the texting scandal, I can’t find any reasonable justification for DV’s description of theMark Robinson lead. The third of three equal length paragraphs in that lead says
    Near the end of his term, Robinson won the Republican nomination for governor. His campaign was checkered by a history of incendiary and controversial statements, including about abortion, Adolf Hitler, the LGBTQ community, women's rights, civil rights, and Jews. Robinson was also linked to extremist comments on an online pornography forum during his campaign.After losing the election to Democratic state attorney general Josh Stein, Robinson announced his retirement from politics.
    I’m baffled with how different DV’s experience reading that paragraph seems to be from my experience reading that paragraph. Based on this comment alone, I have reservations about their ability to contribute to AmPol.Mikewem (talk)01:10, 16 December 2025 (UTC)[reply]
    Specifically talking about DV’s words:Mark Robinson who's political scandals were exceptionally more important in the race is detailed by a single sentenceRobinson was also linked to extremist comments on an online pornography forum during his campaign, here we give it a full paragraph.Mikewem (talk)01:12, 16 December 2025 (UTC)[reply]
    Those are multiple salcandals linked in a single sentence. It would be like including an entire paragraph about every scandal, instead they are a single sentence in the lede.Des Vallee (talk)01:15, 16 December 2025 (UTC)[reply]
    In Robinson?? My eyes show two sentences. I’m looking right at it. There’s the word Jews, then a period, and then the word Robinson. 2 sentences, numerous scandals. In Jones, there are 2 scandals in one sentence, linked by a comma.Mikewem (talk)01:25, 16 December 2025 (UTC)[reply]
    To clarify: according to my eyes, we do give Robinson a full paragraph, and Robinson and Jones’ third paragraphs are of comparable length and comparable weight and both end with non-scandal content.Mikewem (talk)01:15, 16 December 2025 (UTC)[reply]
    That's to 5 scandals though all of which are in passing detail, and the scandals aren't even the focus on the article, he is AG-elect and a congressman.Des Vallee (talk)01:24, 16 December 2025 (UTC)[reply]
    I don't understand how you can compare the two, one gives a passing mention of the scandals. Another provides extreme details that aren't needed for an understanding of the article.Des Vallee (talk)01:26, 16 December 2025 (UTC)[reply]
    You are the one who introduced a comparison of the two, in your comment which I started with. And now you are saying “I don't understand how you can compare the two”. Based on this alone, I can fully see how CC came to be frustrated. I support a topic ban (final word from me, barring new activity outside this thread).Mikewem (talk)01:33, 16 December 2025 (UTC)[reply]
    You keep providing vague references expecting people to not check you or take it at face value.Contentcreator (talk)01:56, 16 December 2025 (UTC)[reply]
    Is your claim that the body of the Jones article does not proportionally dedicate many words to the texting scandal?? I find that claim inexplicably baffling.Mikewem (talk)01:28, 16 December 2025 (UTC)[reply]
    @Contentcreator: just chiming in one last time to note that this has become aWP:WALLOFTEXT (I guess I didn’t exactly help with that). I do see some issues here, and I would like the admins to take a look. I would beseech you not to add any additional text.Mikewem (talk)07:13, 16 December 2025 (UTC)[reply]
    Or maybe they’veflounced, seemingly again.[129]Mikewem (talk)07:21, 16 December 2025 (UTC)[reply]

    Over 6 individuals on the talk state the same thing. I guess you also have reservations about them to but I find that absurd.Des Vallee (talk)02:14, 16 December 2025 (UTC)[reply]

    Diffs?Contentcreator (talk)02:24, 16 December 2025 (UTC)[reply]
    Not sure if it is 6 but overall this seems to be more just conflating without context to justify not following process , otherwise, why wouldn't you have brought that up before when you responded with a link about someone complaining about wording not undue weight.
    There is a continued developing credibility problem
    • You said you didn't make a personal attack and said that all you said was that I misunderstood how wikipedia work
    • You then apologize for in reply to someone who brings up the edit
    • You keep pretending that the mass revert isn't a problem because you didn't re-revert despite mass-reverts policy are only supposed to be used in rare cases like vandalism. Not to revert an editor that you have had experience with on that page.
      • Even after the later point being brought up you continue to re-iterate that you don't understand why it is a problem
    • You say there was never a consensus despite you having agreed to the lede then say you had changed your mind
    • You constantly pretend that the notice reasons were brought up on talk page despite due weight not being mentioned
    • You make vague references to justify your actions but supply no edits to back it up
    • You keep trying to change the into something you can defend i.e mass-revert
    Contentcreator (talk)02:55, 16 December 2025 (UTC)[reply]
    I could have phrased the first statement better, the wording I used was wrong. I can bring up needing know more about Wikipedia differently and I should have, that however is a single instance from over a month ago so I do not understand why that would be used for anything. No the "mass revert" as you keep calling does it break any policy! I disagreed with all five of your edits, all of them you can revert them, and reverting broke no policy. No I do not understand why reverting a single new edits a usually normal process on Wikipedia is being described like this.
    There was no consensus, you removed edits detailing Jone's early life and then readded them, are you "breaking consensus?" People are allowed to change their mind on what they want in an article, you did multiple times in the article. This is just false. There is no consensus on the article's lede, no discussion ended with majority or consensus on how the lede should be written. You keep claiming there is consensus without even linking it to any discussions. Going through the talk page shows no discussion ended in consensus on the lede.
    You constantly pretend that the notice reasons were brought up on talk page despite due weight not being mentioned makes me so confused as to why this is being taken seriously because it's wrong! It's just objectively wrong on so many levels, I wrote on the talk pageBiographies are supposed to be a full description of a person's life, and the lede is supposed a full description of a person's life. At the current moment, half of the lede is dedicated to texting scandals, and a single sentence is dedicated his life prior to being involved in politics. This is not how ledes are supposed to be written. I don't understand how you can look at this, written previously to the dispute, and state that undue weight was not mentioned on the talk! It's like saying up is down and people agreeing with you. It's just false.
    I do not understand why this is being taken seriously.Des Vallee (talk)06:58, 16 December 2025 (UTC)[reply]
    I am going to follow @Mikewem and not respond to this with another wall of text. I have said all I needed to.Contentcreator (talk)15:38, 16 December 2025 (UTC)[reply]

    Re: [Repeated personal attacks stemming from a now-closed content dispute discussion] - Unresolved Concerns

    [edit]

    Buggi (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log)

    So, I'm continuing a posting on here that was just archived (Wikipedia:Administrators' noticeboard/IncidentArchive1209#Repeated personal attacks stemming from a now-closed content dispute discussion) due to no action having been taken on it recently. The involved participants were tagged in the original posting, so I don't know whether or not they need to be tagged in this continuance.

    The resolution that I am seeking is for the user in question, Buggi, to be given an edit block site-wide for however long an administrator deems necessary, due to the possibility that the user may repeat the actions they took against me (engaging in personal attacks) towards other editors, or even towards administrators, in the future when they are given a warning about violating Wikipedia policy/guidelines. The user has yet to apologize for their actions against me, and have yet to show they won't engage in the same behavior in the future.ClarkKentWannabe (talk)00:30, 16 December 2025 (UTC)[reply]

    As an FYI, the proper course of action would be to unarchive it and post it back here rather than opening a new thread.~2025-40848-05 (talk)02:58, 16 December 2025 (UTC)[reply]
    No action is likely to be taken by an admin without some diffs illustrating what the problem is here, especially imposing a site-wide block.LizRead!Talk!03:10, 16 December 2025 (UTC)[reply]
    Well, based off the next bit of information I get from ~2025-40848-05, I'll make the appropriate change here.ClarkKentWannabe (talk)03:45, 16 December 2025 (UTC)[reply]
    Well, the thing is, when I saw that the original discussion was archived, I wasn't sure what to do. So, the first thought that came to mind was to ask both Google's AI & ChatGPT what to do, and it suggested what I ended up doing.
    So then, you're simply saying what to do is:
    • remove the original discussion from the archive,
    • then remove this section from ANI,
    • and then repost the original discussion here?
    ClarkKentWannabe (talk)03:44, 16 December 2025 (UTC)[reply]
    1)Don't take advice from LLMs when working on Wikipedia. LLMs have been shown to do poorly with providing policy interpretations and have a lot of junk inputs: garbage in -> garbage out.
    2) I read the original thread and understand why it wasn't acted upon. It was unfocused and verbose. Please, please don't restore it.
    3) Can you state briefly, and with diffs, what the problem is?
    4) According to policy (Wikipedia:Civility#Apologising: It's OK to say sorry) you cannot demand an apology. Read that section for more information. — rsjaffe 🗣️04:21, 16 December 2025 (UTC)[reply]
    Well then, if you read the original now-archived thread (as you claim), I laid out the details of the problem in my very first posting in that thread.

    But, just to reiterate here for you:
    In violation of Wikipedia policy on personal attacks (Wikipedia:No personal attacks), a user, Buggi, engaged in personal attacks against me (not just twice in an public discussion I started on the "Major film studios" talk page -here &here, but then a third time on their own talk page -here; FYI: I posted two warnings on Buggi's talk page about engaging in personal attacks, to which they demanded that I leave them alone, giving the implication that they doesn't care about abiding by policies governing user behavior on here). After the third violation, I figured it was best to post at ANI in order to get the situation taken care of. And, in my first posting in that now-archived thread, I provided diffs to all three personal attacks, the same diffs I've linked to here.

    And, nowhere in the first posting here did I ever actually outright state anything along the lines of "I want an apology", "Give me an apology", etc. (referencing Wikipedia's policy on apologies); what I stated was that Buggi had yet to apologize for their actions, which, to me, indicates they have no remorse for doing so, and also indicates they would likely engage in that same action again in the same, or similar, situation in the future against either another editor, or even an administrator, which is why I'm asking for some kind of edit block to their account; as far as the length of said possible edit block, I would leave that up to the discretion of whatever administrator that decides to take such action. Buggi has put forth nothing that would imply, on their part, that they wouldn't repeat the offending behavior in question in the future towards someone else on here should they ever receive future warnings about their behavior on here.ClarkKentWannabe (talk)04:59, 16 December 2025 (UTC)[reply]
    What exactly are the personal attacks? Three short sentences will do. —Malcolmxl5 (talk)09:46, 16 December 2025 (UTC)[reply]
    OK.
    The personal attacks that violate WP:NOPA (specifically: "Accusations about personal behavior that lack evidence."):
    1) From Buggi, Dec. 5, 2025 at 09:15:I don't understand your obsession with this. (First diff linked to)
    2) Also from Buggi, Dec. 5, 2025 at 17:00:The issue with this discussion is that one side wants the article to be legible and convey knowledge in the most efficient way, and the other side exercises endless discussion, invokes policies and constantly threatens to go to the administration to get their way at the expense of a reader. Which also seems to be a pattern across other articles. (Second diff linked to)
    3) And, finally, from Buggi, Dec. 9, 2025 at 23:29:I said go away. If the content suffers because of a user's visible pattern of suddenly dropping into an article where they had not contributed much to, and trying to force their opinion on some obscure issue, I'm going to point this out. (Third & final diff linked to).
    And, to reiterate, Buggi has shown no remorse in the actions they took, which implies they'd have no problem engaging in such actions again in the future against another editor, or even an administrator, should they be given warnings in the future about their behavior on here. And, it is because of that implication that I believe they deserve an edit block, in order to let them know that such behavior will not be tolerated on here. And, such discipline would show them what's likely to happen again, if not for a longer period of time the second time around, in the future should they ever repeat the offending behavior again.ClarkKentWannabe (talk)10:27, 16 December 2025 (UTC)[reply]
    I don’t see anything actionable there and suggest you let go of this and move on. —Malcolmxl5 (talk)11:02, 16 December 2025 (UTC)[reply]
    I can't speak for rsjaffe, but frankly those don't particularly seem like personal attacks to me; they're fairly transparently focused on quality of content.
    Secondly, even if we accept that thet are; blocks are preventative, not punitive. We don't block people to 'discipline' them or 'let them know' something 'isn't acceptable,' we do so to prevent ongoing disruption to the encyclopedia. If there is no reason to think that there will be ongoing disruption, then there's no reason to block.Athanelar (talk)11:03, 16 December 2025 (UTC)[reply]
    WP:Forgive and forget is important for editing here, isolated cases of incivility happen, people have bad days, and in my experience at least, if someone's snarky to you, often there's a grain of merit that can be taken constructivelyKowal2701 (talk)13:28, 16 December 2025 (UTC)[reply]
    I suggest you readWikipedia:No personal attacks#First offenses and isolated incidents. Escalating is not a good course of action to take when you are unhappy with a person's behavior, unless it is serious, which this is not. That section of the policy has good advice on how to handle this and how to de-escalate such a conflict. Escalating with warning templates as you did is not a good way to handle this unless it is severe.
    And I just noticed that you failed to notify @Buggi of your report this time. It is mandatory to do so. Please do so ASAP. — rsjaffe 🗣️20:06, 16 December 2025 (UTC)[reply]

    Laqy-peenu

    [edit]

    It is with regret that I must bring a good faith contributor to ANI.Laqy-peenu (talk ·contribs) has been editing on and off for some number of years, and unfortunately despite multiple attempts to communicate with them over their talk page over said number of years, the majority of edits have not been helpful. With over a thousand contribs, I do not have a good estimate of the proportion of their edits which have/need to be reverted and/or put into draftspace and eventually deleted, but I am quite certain it's above 50%. Most concerningly, the majority of their edits are in the areas of barely notable BLPs (some amounts of BLP1E?) and highly technical physics articles, which makes the subtle errors they introduce difficult to catch and, in the former case, quite bad if we don't catch it. The user has also displayed a lack of communication in both the TP and edit summaries, with the majority of edit summaries being boilerplate and their TP responses generally of negligible substance. In summary,WP:Communication is required andWP:Competence is required.

    Detailed diffs:

    Pointless refbombing of a low traffic page, which user haspreviously broken even after beingrevertedmultiple times

    Creation ofprobably notable topic in mainspace, which was first draftified by me because it looked like the beginning of a textbook, then revdel'd because it actually was the beginning of a textbook

    Anotherdraftified mainspace creation which is completely incomprehensible to anyone who hasn't taken third-year GR (though I promise that it's actually not patent nonsense)

    An example ofsubtle error introduced in one of user's article creations

    page creation which was BLPPROD'd immediately and required three hours of volunteer cleanup to bring the article to a readable state

    Yet anothersubtle error (Among other things, the equation is missing a term)

    Example of editing in BLP (minor BLP, no less) that was immediately reverted

    etc. Those interested in a more detailed overview and stale examples may examine the edit history of said user.

    I hesitated in whether to bring this ANI report, but sinceattempting to communicate with the user, the user has done nothing but create said copyvio, andanother user has supported ANI action, so here we are.Fermiboson (talk)10:18, 16 December 2025 (UTC)[reply]

    Adding that I'm not necessarily demanding sanctions. Honestly, more than anything I want some more pairs of eyes to look over all of their contribs to fix anything that needs to be fixed which I might not know how to...Fermiboson (talk)10:21, 16 December 2025 (UTC)[reply]
    I definitely support this report. If you balance the contributions against the sheer amount of effort put in by other editors to clean up their efforts, then Laqy-peenu is a drain on Wikipedia not a net contributor. Such effort might actually be worth it - everyone needs the opportunity to grow/improve - but the lack of communication and apparent inability to learn from mistakes is a serious issue.10mmsocket (talk)10:25, 16 December 2025 (UTC)[reply]
    Draft:Modified Tolman - Oppenheimer - Volkoff Limit looks likeWP:SYNTH of various unrelated modifications to theTolman-Oppenheimer-Volkoff equation. I thinkGW190425 comes up a lot in the literature as one component is in themass gap between neutron stars and black holes. –LaundryPizza03 (d)13:15, 16 December 2025 (UTC)[reply]
    No wait, that wasGW190814. But 190425 seems familiar from somewhere... I'll just recruit fromWT:PHYS, and in my opinion, this user needs either a pblock from article and draft space or a topic ban from physics. –LaundryPizza03 (d)13:19, 16 December 2025 (UTC)[reply]
    GW190425 is an interesting event – it was the second binary neutron star merger (or possibly first black hole–neutron star merger) detected with gravitational waves; see[130]. It's notable, but the mangled stub article we have on it is not useful.Wham2001 (talk)13:32, 16 December 2025 (UTC)[reply]
    Aye, I have flagged it as{{expert needed}} and corrected a few errors I could immediately identify, including an incorrect date (2019 April 19 instead of April 25). It is apparent that the user did not do a comprehensive enough analysis of the literature, often taking reported results as uncontested facts. –LaundryPizza03 (d)13:56, 16 December 2025 (UTC)[reply]
    Ah, I've forgot about that one - yes, the article also originally stated that it's a neutron star merger when the literature is explicitly about the fact that it seems too big to be one, another example of subtle errors introduced.Fermiboson (talk)14:18, 16 December 2025 (UTC)[reply]
    User hasedited after this report.Fermiboson (talk)14:26, 16 December 2025 (UTC)[reply]
    They are clearly ignoring your comments on their talk page, they responded to a new comment posted on their page todayAjheindel (talk)14:31, 16 December 2025 (UTC)[reply]
    I think your report is too nice.This is just garbage. And it is the rule, not the exception. I have reviewed this user's contributions, and although positive contributions do exist, they are few. Couple that with the absolute refusal to communicate, and a block is richly deserved.Tercer (talk)14:40, 16 December 2025 (UTC)[reply]
    I have seen and commented on some of the users pages/edits as part ofWP:NPP. I think there is strong enough evidence with both the inappropriate edits, lack of communication and the creation of inappropriate pages that this is a case ofWP:NOTHERE. I think an indef block is appropriate (which they can of course appeal). Perhaps they will then pay attention and change their ways.Ldm1954 (talk)14:43, 16 December 2025 (UTC)[reply]
    Additional Comment. According to their user page they areA. B. R. Hazarika. I have just nominated that for deletion, it is self-promo with many claims that are dubious. (I don't understand how that page did not get bounced at NPP.) This reinforces my opinion that the editor should be blocked forWP:NOTHERE.Ldm1954 (talk)15:24, 16 December 2025 (UTC)[reply]
    I think that's quite enough of that. Indefinitely blocked.The Blade of the Northern Lights (話して下さい)15:54, 16 December 2025 (UTC)[reply]
    Just adding that there is copyvio in at least one of their articles - the 'design' section ofJackson Oswalt, now removed inthis diff. I'll dredge through the others in probably a few hours, if no one else gets there first.Meadowlark (talk)17:33, 16 December 2025 (UTC)[reply]
    Also if you look at edits where he adds sources, he tends to add an excess of sources, including many which are notWP:RS (etsy and stack exchanges for example). It seems he googles a topic and just adds as many as he can. I will try to go through and fix anymore of those I see.Ajheindel (talk)17:47, 16 December 2025 (UTC)[reply]
    Are you satisfied with our cleanup ofGW190425? –LaundryPizza03 (d)17:54, 16 December 2025 (UTC)[reply]
    Do you think[131] constitues aWP:RS? Looks to me like a blog post. Otherwise looks fine to me.Ajheindel (talk)18:03, 16 December 2025 (UTC)[reply]
    Probably, all instances can be replaced byAbbott et al. (2020). –LaundryPizza03 (d)18:06, 16 December 2025 (UTC)[reply]
    I seejohnjbarton already changed it, I was looking at an older revision. Definitely much improved now.Ajheindel (talk)18:13, 16 December 2025 (UTC)[reply]

    Sira Aspera

    [edit]

    Second time reportingSira Aspera (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log) due to their disruptive editing and now in this casesource falsification and vandalism, i do hope now administrators will take necessary measures. The pages that have been vandalised are

    Just andisclamer when previous report was made on user, they made no attempts to engage in conversation.~2025-41020-07 (talk)13:43, 16 December 2025 (UTC)[reply]

    Diffs?Tankishguy15:09, 16 December 2025 (UTC)[reply]
    ...Tankishguy17:38, 16 December 2025 (UTC)[reply]

    1RR vio by Rambling Rambler at2025 Bondi Beach shooting

    [edit]

    Rambling Rambler (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log) violated 1RRhere, having previously reverted the same material minutes earlier in 3 successsive edits[132][133][134]. The material is unambiguously not BLP exempt and there is overwhelming consensus on the Talk page to include it.

    The page is protected byWikipedia:GS/SCW&ISIL

    Talk:2025 Bondi Beach shooting has a 1RR warning banner which serves as notice that Rambler is aware of the CT.Mikewem (talk)18:52, 16 December 2025 (UTC)[reply]

    Noting that the 1RR remedy in the ISIL GS does not require noticeMikewem (talk)18:57, 16 December 2025 (UTC)[reply]
    The tragic events of the Bondi Beach shooting currently represent one of the most fraught BLP issues on the site given what has occurred, and therefore I have been diligent in explaining why said reverts have taken place. Since the creation of the article there have been repeated and frequent introductions of BLP issues including the repeated introduction of names regarding people alleged to have carried out or intervened, including various ones that have since likely been shown to be false in reporting. Some of this is still going on today days later.
    Given the repeated issue that introducing one name is leading to other editors to introduce further names that are in conflict with various and differing parts of BLP, I have undertaken to do my best establish strong community consensus for which individuals should be identified by name across the article as a whole to resolve the various issues by opening an RfC (which the filer themselves has taken part in) given there are still conflicting views on what is appropriate to include. I have undertaken my approach following other sadly recent events of a similar nature, such as the Assassination of Charlie Kirk, where an RfC was used as a way to establish how BLP would be considered for the events of the article when names are being carried widely in RS and until such a point names would remain removed.
    I have explained to multiple people who feel strongly towards one outcome that they shouldn't be deciding to unilaterally implement their preferred outcome of this RfC, and that if they believe the outcome to be aWP:SNOW then they are very welcome to make a close request. Given this is a contentious topic area an unofficial closure and implementation doesn't appear advised perWP:RFCCLOSE.Rambling Rambler (talk)19:03, 16 December 2025 (UTC)[reply]
    The question may be withdrawn by the poster (e.g., if the community's response became obvious very quickly). – waiting around for an obvious close or asking other editors to request isn't the only end game. Closure is fairly flexible. Why the determination to ignore the obvious snow?Iskandar323 (talk)19:09, 16 December 2025 (UTC)[reply]
    It's not about "obviously ignoring it", Given I've been removing the material that I believe to be violating BLP under an exemption for it, I personally do not find it appropriate for me to be demanding an early closure and therefore making a statement on what the outcome should be which is also why I haven't voted in the RfC.
    I have expressed to multiple editors that if they feel strongly it's a SNOW situation then they are welcome to file a close request for that reason.Rambling Rambler (talk)19:25, 16 December 2025 (UTC)[reply]
    It is to be noted that in the exception it states "What counts as exempt under BLP can be controversial. Consider reporting to the BLP noticeboard instead of relying on this exemption." and a few lines lower it states, "When in doubt, do not revert." I understand that there was a large amount of disinfo earlier on, but multiple reliable sources and the Australian PM have vouched for his identity. I do not doubt that you wish to make the article better, but i implore you to better consider the viewpoints of your fellow humans on the other side of the screen.MetalBreaksAndBends (talk)19:37, 16 December 2025 (UTC)[reply]
    @MetalBreaksAndBends I am intending to consider the viewpoints of other people, that's exactly why I opened an RfC to engage a much wider audience than simply informal fragmented comments across multiple talk page sections and there is clearly disagreement in that RfC even if one outcome is currently more likely than others.
    There is zero harm in waiting for that RfC to close whether after seven days or if someone makes an early close request.Rambling Rambler (talk)19:45, 16 December 2025 (UTC)[reply]
    RR selectively deleted deceased victims’ names. I find that inexcusable and approaching NOTHEREMikewem (talk)19:11, 16 December 2025 (UTC)[reply]
    As I explained to you on the the talk page, I removed the names of a sadly deceased couple who attempted to intervene because BLP also applies to the recently deceased and there is quite possibly public domain footage of them being fatally wounded while intervening. I felt an abundance of caution was best until the RfC closed on how BLP was to be applied to the article, and that only removing the surviving intervening bystander's name while leaving those who had died undertaking similar actions would be a double-standard application of BLP.Rambling Rambler (talk)19:20, 16 December 2025 (UTC)[reply]
    And yet no qualms with all the names in2025 Bondi Beach shooting#Victims.Mikewem (talk)19:26, 16 December 2025 (UTC)[reply]
    I've just stated why I believe those to be different under BLP compared to the deceased couple I did remove.Rambling Rambler (talk)19:32, 16 December 2025 (UTC)[reply]
    It feels like you've definitely come up with your own set of made-up distinctions.Iskandar323 (talk)19:44, 16 December 2025 (UTC)[reply]
    Once again in relation to this issue you're seeming to assume bad faith on my part.[135]
    All I have tried to do is stick to BLP and best practice as I understand it. I've engaged repeatedly on the article to get appropriate protections and designations given the sensitive nature[136][137] and I've opened an RfC[138] to allow as many people to contribute to how we should deal with the delicate BLP situation that such an event comes with.
    What I do not understand is why this has been filed as though I'm for some reason trying to get in the way when anyone who feels certain there's obvious consensus at an RfC that opened just over 24 hours ago could file a close request for that RfC.Rambling Rambler (talk)19:59, 16 December 2025 (UTC)[reply]
    It's pretty normal to leave out the names of non-public figures in cases like these. If I were involved in editing that page I'd be arguing for a more narrow list of named names.Guettarda (talk)21:23, 16 December 2025 (UTC)[reply]
    I don't believe this warrants ANI action. I feelWP:3RRBLP exemption applies, andRambling Rambler was acting in good faith to diligently enforce BLP policy until consensus formed in an ongoing RfC to include the names.Apfelmaische (talk)20:54, 16 December 2025 (UTC)[reply]

    User:Ritchy Dube

    [edit]

    I'm reluctantly bringing this case to ask that either an uninvolved admin or the community consider whether further sanctions are necessary.

    User:Ritchy Dube was blocked for COI editing, thenunblocked with a block on article space.

    He continued to spam user pages and wasblocked from User pages.

    Unfortunately, he's beenassuming bad faith andattack other editors, responding even after they (and I)explicitly ask him to stop posting. You can see various warnings on his Talk page and pleas for him to stop.

    His sole focus seems to be on getting variousdrafts on his work accepted, but whenever anyone raises concerns over any issues with formatting, sourcing etc., his replies will typically mention his expertise andquestion the ability of the person who raised those concerns.

    He obviously cares a lot about his work, but that seems to be clouding his judgement when it comes to the goodwill of other editors. This has resulted in a default battleground attack response, such asthis one from yesterday where he explicitly said he doesn't want feedback from specific editors & admins and will get his draft published no matter what. I don't want to make this lengthy, but I feel this excerpt from the last diff is important:

    [You] have all put blocks and created delays unecessarily on my notable, fantastic, well-sourced and neutral page because of drum roll . . . . . . . . editor bias.You cite COI, poor sourcing, lacl of notability and when that nonsense failed, you revert to false accusation of inappropriate use of namespaces. Face the facts, these tactics smell of petty cyber bullying by a group of like-minded haters.Here is how it will go. I will get my latest draft reviewed, approved and moved to the mainspace. Period.

    I don't think it's possible for him to edit neutrally, considering his passion for his work.

    Finally, whilst writing this post, I receivedthis personal attack questioning whether I had the ability to read.

    I'm kindly asking for some support on what to do with this editor, as his behaviour hasn't changed since being blocked and the influx of replies and attacks on the abilities of other editors isn't how Wikipedia should be.Blue Sonnet (talk)20:59, 16 December 2025 (UTC)[reply]

    Blocked indefinitely afteryet another personal attack following your report. Thelast chance saloon doesn't serve free refills.ChaoticEnby (talk ·contribs)21:21, 16 December 2025 (UTC)[reply]
    Thank you! I'm off to scrub my Talk page.Blue Sonnet (talk)21:23, 16 December 2025 (UTC)[reply]

    user:Pktlaurence reported by Zackmann08

    [edit]

    Pktlaurence (talk ·contribs ·deleted contribs ·logs ·filter log ·block user ·block log)

    User has been repeatedly editing in a very disruptive manner onMing Dynasty Zheng family.

    • Repeatedly moving the page to an inapproriate name[139] &[140]
    • Repeatedly breaking templates and violating MOS[141] &[142] (note that the 2nd one was a revert of my correction of their first breaking of the page).

    Note thatmultiple warnings on their talk page have gone unanswered and ignored (WP:ENGAGE).

    For the record I got myself blocked from editing a page for edit warring while trying to revert what appeared to be obvious vandalism. Rather then getting into trouble again, I am coming here asking thatPktlaurence be sanctioned for their actions.

    Please note that this user hasmultiple previous blocks for thisexact behavior (edit warring and inappropriate page moves) and has been warned MANY times about this issue.Zackmann (Talk to me/What I been doing)21:19, 16 December 2025 (UTC)[reply]

    Gently nudging you both to discuss it onTalk:Zheng clique, or request athird opinion, as these will be much more productive than templated warnings or edit-warring. At this stage, bringing the dispute to ANI is a bit of a "hydrogen bomb vs coughing baby" situation, don't you think?ChaoticEnby (talk ·contribs)21:36, 16 December 2025 (UTC)[reply]
    If it wasn't for this users extensive history with this exact problem, and their failure to engage AT ALL, I wouldn't be here.Zackmann (Talk to me/What I been doing)21:38, 16 December 2025 (UTC)[reply]
    Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Administrators%27_noticeboard/Incidents&oldid=1327918326"
    Category:
    Hidden categories:

    [8]ページ先頭

    ©2009-2025 Movatter.jp