Jump to content

Wikipedia:Administrators' noticeboard/Incidents

From Wikipedia, the free encyclopedia
    Administrators' noticeboard/Incidents

    This page is for urgent incidents or chronic, intractable behavioral problems.

    When starting a discussion about an editor, you must leave a notice on their talk page; pinging is not enough.
    You may use {{subst:ANI-notice}} ~~~~ 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 are archived automatically by Lowercase sigmabot III. Editors unable to edit here are sent to the /Non-autoconfirmed posts subpage. (archivessearch)

    Disruptive editing and WP:TALKNO by User:AnonMoos

    [edit]

    The main issue with this editor at the moment is disruptive editing based on continuous abuse of WP:TALKNO and failure to get the point. Issues began when this editor removed 5000+ bytes of sourced material. They did it again and again and again.

    Instead of starting a discussion on the talk page of the article, the user came to my talk page to let me know of their opinion of my contributions. When I started a discussion on the talk page of the relevant article, the user edited my signature and changed the heading of the discussion I started according to their POV. When I let them know that this was highly inappropriate according to WP:TALKNO, both in that discussion and on their talk page, they responded on my talk page stating ever since the stupid Wikipedia Dec. 2019 encryption protocol upgrade, to able to edit or view Wikipedia at all from my home computer, I have to use an indirect method which involves a non-fully-Unicode-compliant tool. I couldn't even really see your signature that way, and so didn't know to try to avoid changing it, which I had never heard of. In any case, they kept reverting the content supported by the reliable source, they also kept attempting to apply their POV to the discussion heading again and again and again. I finally explained that I had sought a third opinion and that they should refrain from changing the heading again in order to preserve the integrity of the link, and they went ahead and changed it again anyway. — Preceding unsigned comment added by إيان (talkcontribs) 15:20, 17 December 2024 (UTC)[reply]

    The other user in this case is User:AnonMoos? This looks like a content dispute over whether the article is on the English version of a German-Arabic dictionary or the dictionary itself. Secretlondon (talk) 15:47, 17 December 2024 (UTC)[reply]
    Yes the is indeed about User:AnonMoos. I see the content dispute as stemming from the fundamental conduct issue, which has manifested itself most egregiously with insisting on violating WP:TALKNO repeatedly even after I explained that I had sought a third opinion and that they should refrain from changing the heading again in order to preserve the integrity of the link, after which they went ahead and changed it again anyway. إيان (talk) 16:00, 17 December 2024 (UTC)[reply]
    The heading dispute is between a date heading, and a descriptive heading? that's not really reformulating your entry. Secretlondon (talk) 17:44, 17 December 2024 (UTC)[reply]
    It's a conduct issue. إيان (talk) 19:58, 17 December 2024 (UTC)[reply]
    But what conduct issue? TALKNO doesn't forbid changing headings. In fact the wider guideline makes it clear it's perfectly acceptable "Because threads are shared by multiple editors (regardless of how many have posted so far), no one, including the original poster, "owns" a talk page discussion or its heading. It is generally acceptable to change headings when a better heading is appropriate, e.g., one more accurately describing the content of the discussion or the issue discussed, less one-sided, more appropriate for accessibility reasons, etc. Whenever a change is likely to be controversial, avoid disputes by discussing a heading change with the editor who started the thread, if possible. It can also sometimes be appropriate to merge entire sections under one heading (often preserving the later one as a subheading) if their discussions are redundant." To be blunt, if you don't want editors changing the headings of sections you start, don't use such terrible headings. I definitely recommend you stay away from ANI since changing headings is quite common here. Nil Einne (talk) 06:25, 18 December 2024 (UTC)[reply]
    Actually I missed the signature issue. That's far more concerning unfortunately lost IMO partly because you concentrated on silly stuff. Nil Einne (talk) 06:29, 18 December 2024 (UTC)[reply]
    ‎إيان: I suggest you stop messing around with the section heading since it's a distraction which could easily lead to you being blocked. But if AnonMoos changes your signature again, report it and only that without silliness about section headings, mentioning that they've been warned about it before if needed. Nil Einne (talk) 06:50, 18 December 2024 (UTC)[reply]

    I wrote a long and detailed explanation on his user talk page as to why the date-only header is basically useless in that context, but he's still for some peculiar reason fanatically determined to keep changing it back. Frankly, I've basically run out of good-faith reasons that make any sense -- except of course, his apparently unshakable belief that he has certain talk-page "rights", which according to Wikipedia guidelines he does not in fact have (outside of his own personal user talk page)... AnonMoos (talk) 23:10, 17 December 2024 (UTC)[reply]

    @AnonMoos: I don't see a problem with changing the heading but why on earth did you change their signature multiple times [1] [2]? That is indeed a clear violation of WP:TPOC since the signature was perfectly valid per WP:NLS. In fact your change was far worse since it changed a perfectly valid signature which would take other editors to the contributor's talk page and user page into an invalid one which lead no where. If you're using some sort of plugin which does that, it's your responsibility to manage it better so it doesn't do that ever again especially if you're going to edit talk pages where it might be common. If you're doing that intentionally, I suggest you cut it out or expect to be indeffed. Nil Einne (talk) 06:48, 18 December 2024 (UTC)[reply]
    User:AnonMoos, this is not good to see. Don't rewrite or reformat other editor's signatures. There is no reason to be doing this unless you are trying to provoke the other editor. Liz Read! Talk! 07:51, 18 December 2024 (UTC)[reply]
    For what it's worth, AnonMoos stated earlier that the changing of the signature was a unintentional technical issue, due to his use of some "non-standard tool" in accessing the internet [3]. This seems plausible, as similar apparently unintentional changes to non-Ascii character data have happened in edits of his before (e.g. [4]). But if he knew of this issue, it's rather disappointing he let it happen again some days later [5]. Equally disappointing is the extremely aggressive rhetoric and acerbic tone with which he has been escalating this essentially harmless, good-faith content dispute from the beginning. Fut.Perf. 10:25, 18 December 2024 (UTC)[reply]
    I just can't fathom what tool they're using to get around the HTTPS requirement to edit Wikipedia securely. — The Hand That Feeds You:Bite 17:42, 18 December 2024 (UTC)[reply]
    Should be impossible as it's required to even access the site in the first place according to WP:SECLakesideMinersCome Talk To Me! 16:41, 19 December 2024 (UTC)[reply]
    Looking at his talk page it's been going back to at least 2011[6]LakesideMinersCome Talk To Me! 16:17, 19 December 2024 (UTC)[reply]
    Guys, I do not deliberately set out to modify signatures, and when it happens, I am not usually aware of doing so. As I've already explained before in several places, since the December 2019 encryption protocol upgrade (NOT 2011!), the only way I can edit (or view) Wikipedia at all from home is by an indirect method which is not fully Unicode-compliant. To change this, I would have to get a completely different type of Internet connection, which would permanently disconnect my older computer, which I still use almost every day.
    Meanwhile, this thread has been set up so I can't add a comment to it from home without affecting Unicode characters, so I was unable to reply here for 36 hours or so. If I'm silent in the future, it will be for the same reason. AnonMoos (talk) 01:14, 21 December 2024 (UTC)[reply]
    Wikipedia uses Unicode characters (UTF-8 encoding). Anyone who cannot edit without corrupting such characters should not edit. Johnuniq (talk) 03:47, 21 December 2024 (UTC)[reply]
    Whatever, -- I was using them perfectly fine until December 2019, and still use them perfectly fine on public WiFi, but in December 2019 a requirement was imposed that you can't access Wikipedia at all unless you can handle encryption algorithms and protocols that weren't introduced until the mid-2010s. I have a 2012 web browser on my home computer that handles UTF-8 just fine, but 2012 simply wasn't good enough for the Wikipedia developers -- you had to have software that was almost up to date as of 2019, or you would be abruptly totally cut off. If you can drag up the relevant archive of Village Pump Technical, I and others complained at the time, but our concerns were not listened to or considered in any way. The basic attitude of the developers was that if you weren't running almost up-to-date software, then screw you, and if your computer is not capable of running almost up-to-date software, then double screw you! The change was announced for January 2020, but was actually implemented in mid-December 2019, apparently because they were so eager and anxious to start excluding people. It wasn't one of Wikipedia's finer moments. Since that time, I have had to use an indirect method to access Wikipedia from my home computer, and I don't feel particularly guilty about it (other people's obnoxious behaviors in 2019 have done away with most of the guilt I might feel)... AnonMoos (talk) 20:59, 21 December 2024 (UTC)[reply]
    ...HTTPS was created in 1994, and became an official specification in 2000, not "mid-2010s". I'm not sure what 2012 web browser you're using, but if it's not able to handle HTTPS not being able to access Wikipedia with it is the least of your browsing concerns, given that 85-95% of the World Wide Web defaults to it now. Also I hate to think of how many security holes your ancient computer has. I'm going to be honest: with a brower setup that old it isn't safe for you to be on the web at all, and the security hole that lets you access Wikipedia without using a secure connection should be fixed, because that is not working as intended and is - as mentioned - a security hole. - The Bushranger One ping only 00:18, 22 December 2024 (UTC)[reply]
    You unfortunately don't know what you're talking about. New ENCRYPTION ALGORITHM AND PROTOCOL METHODS have been introduced within HTTPS from time to time. I was using HTTPS perfectly happily until December 2019, when the developers arbitrarily ENCRYPTION ALGORITHM AND PROTOCOL REQUIREMENTS. AnonMoos (talk) 00:57, 24 December 2024 (UTC)[reply]
    And even leaving that aside, as Johnuniq mentions - if you can't edit without corrupting Unicode characters, and by your own admission you don't know when it happens, you shouldn't be editing. - The Bushranger One ping only 00:20, 22 December 2024 (UTC)[reply]
    This is probably a reference to when Wikipedia started requiring TLS 1.2 (because earlier versions were deprecated). Anyone who was/is still on Windows XP at that point couldn't connect any more. MrOllie (talk) 01:29, 22 December 2024 (UTC)[reply]
    I'm not talking about when the update happening, I'm talking about how you have known about this issue, and have been getting complainants about it since 2011and are still not taking any steps to do anything about it. What kind of internet connection would not support your PC? What on earth are you even using? Dial-Up? Because that still is supported by even Windows 10. LakesideMinersCome Talk To Me! 02:59, 23 December 2024 (UTC)[reply]

    :::Also, how did you see me saying "this has happened since 2011" as me saying that the update happened in 2011? Can you clarify. LakesideMinersCome Talk To Me! 03:07, 23 December 2024 (UTC) [reply]

    The problem didn't start in 2011, and I have no idea what you're referring to when you mention 2011. The problem started in December 2019 when the developers arbitrarily imposed new ENCRYPTION ALGORITHM AND PROTOCOL REQUIREMENTS... AnonMoos (talk) 00:57, 24 December 2024 (UTC)[reply]
    Apologies. I was extremely tired when I wrote both above. I have striken the date parts. Rest of my comments still stand. LakesideMinersCome Talk To Me! 01:06, 24 December 2024 (UTC)[reply]

    None of this matters

    [edit]

    I don't care what tool this guy uses or what his excuse is. If he can't edit without screwing up people's sigs, then he must not edit. AnonMoos shouls consider himself on notice now that if one of his edits messes stuff up one more time, he'll be blocked until he can give assurance that he's come into the 21st century. EEng 18:05, 23 December 2024 (UTC)[reply]

    That's nice -- and also totally inaccurate. I was in the 21st century, and using 2012 tools, up until December 2019, when the developers pitchforked me backwards by arbitrarily imposing HTTPS ENCRYPTION ALGORITHM AND PROTOCOL REQUIREMENTS which my home computer hardware is not able to run. Notice that I had no problem complying with character-set handling -- the problem is with arbitrary ENCRYPTION ALGORITHM AND PROTOCOL REQUIREMENTS. AnonMoos (talk) 00:48, 24 December 2024 (UTC)[reply]
    The century imagery is irrelevant. You have been warned. EEng 03:14, 24 December 2024 (UTC)[reply]
    That was six years ago, which is IMO about 3-4 years too long to keep using it as an excuse. Technology changes over time, so whatever this non-standard thing you think you need to do to edit here, it may be time to make a choice. Zaathras (talk) 00:56, 24 December 2024 (UTC)[reply]
    As I said, to fix the problem, I would have to get a completely different type of Internet connection which would permanently disconnect my old computer, which I still use almost every single day. I would basically have to change my workflow and overall habits/methods of working because of an arbitrary decision by Wikipedia developers about encryption protocol updates. Anyway, when editing through public WiFi, I'm 100% Unicode compliant, and by exercising a little prudence, I can also avoid most problems when working from home. If I was constantly mangling Unicode right and left, there would have been a chorus of complaints long before now. But occasionally I can't anticipate a problem... AnonMoos (talk) 01:06, 24 December 2024 (UTC)[reply]
    And just to say for the third time: you're out of chances. "Occassionally" is too often. Once more is too often. And if and when that happens, your attitude of entitlement displayed here will pretty much ensure an indefinite block. EEng 03:14, 24 December 2024 (UTC)[reply]
    Think it's time to draft up a formal proposal at this point? LakesideMinersCome Talk To Me! 18:29, 24 December 2024 (UTC)[reply]
    I don't think that's necessary. The key isn't formally deciding the criterion for blocking (because that's obvious to everyone) but rather detecting the next incident. Best way to do that for everyone gathered here to watchlist User talk:AnonMoos. Sooner or later, futher trouble will show up there. EEng 21:31, 24 December 2024 (UTC)[reply]
    If you have DSL or even DialUp. That still works with modern machines. LakesideMinersCome Talk To Me! 01:08, 24 December 2024 (UTC)[reply]
    Heck, I am on DSL (and have been since, if I recall right, 2008). I have no idea what sort of ancient Internet connection AnonMoos is claiming to be using, but it's clearly one that was already obsolete before this change he's still up in arms about six years later was made. - The Bushranger One ping only 05:44, 24 December 2024 (UTC)[reply]
    Not to mention it would STILL be supported these days. It's literally right there when you click wifi/network settings in Windows 10. LakesideMinersCome Talk To Me! 18:20, 24 December 2024 (UTC)[reply]
    • The response by AnonMoos to feedback about this problem is bizarre. I don't really care what the excuse or the history behind it. If you are unwilling to edit Wikipedia using tools that work in 2024 then you should stop editing. The behavior is completely unnecessary and it seems like you don't understand the disruption. Nemov (talk) 14:45, 24 December 2024 (UTC)[reply]
    • AnonMoos hasn't really explained in any detail what their technical limitations are. They don't have to, but we can't really give advice otherwise. If as others have suggested their computer can't negotiate TLS 1.2, I'm surprised that they're able to use any websites at all from that computer. Requiring TLS 1.2 is not controversial; Wikipedia wasn't doing anything unusual in dropping TLS 1.0/1.1 around that time. Mackensen (talk) 15:02, 24 December 2024 (UTC)[reply]
    • If it's that much of a problem for his computer, go and buy a new computer. It would certainly be better than whining about how Wikipedia broke his ability to edit without screwing things up for other users.Insanityclown1 (talk) 07:06, 25 December 2024 (UTC)[reply]
    Meh. None of this matters. Signatures sometimes get accidentally fucked up. This is an encyclopedia, not a forum, and this signature thing is not a real disruption to the creation of encyclopedic content. Zanahary 07:21, 25 December 2024 (UTC)[reply]
    While true, it's still a violation of WP:TPO, and if it's accidentally changing characters in signatures, who knows what else it might be doing that isn't getting caught or reported? - The Bushranger One ping only 07:27, 25 December 2024 (UTC)[reply]
    It is safe to assume there more than a few of the editors taking part in this discussion have years and decades of technological experience under their belts, myself included. I do not think The Accused is straight-up lying about the technical hurdle, but clinging to the "I refuse to change my system of operation, therefore it's Wikipedia's fault for (6 years ago) making the change!" excuse is the real problem here - this is at the heart a behavioral discussion, not a technical one. Consistently violating the norms of the community is indeed a real disruption to the creation of encyclopedic content. Zaathras (talk) 16:29, 25 December 2024 (UTC)[reply]
    It's not inherently about the signatures. It's that he's stubbornly insisting on using an outdated system that introduces errors into other content. — The Hand That Feeds You:Bite 17:40, 25 December 2024 (UTC)[reply]
    agree on this. Incidental changing of signayures due to the tech issue is not a small problem itself but that clearly has potential to impact a much wider range of mainspace content. I have a hard time believing that there is not a browser that supports https and can run on a decade old computer (something like Opera even). Claiming inability to switch or upgrade needs to be explained in detail or otherwise this has potential to be a bigger problem. Masem (t) 17:55, 25 December 2024 (UTC)[reply]

    Disruptive editing by User talk:185.146.112.192

    [edit]

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


    The User talk:185.146.112.192 is engaging in disrupte editing. Neither does this IP provide sources and is POV pushing. And this IP has been warned multiple times for this on his/her talk page.

    Moroike (talk) 20:52, 18 December 2024 (UTC)[reply]

    @Moroike: It looks like you both are edit warring on Kichik Bazar Mosque.[7][8][9][10] That's not particularly helpful, so you should try to have a discussion on the article talk page as to whether you should include the Talysh language name for the article in the lead/infobox. –MJLTalk 20:33, 19 December 2024 (UTC)[reply]
    MJL why and how did you pick out that one article over the many this IP has made recent changes to? The IP has been making disputed edits for months and has been reverted by a number of editors, not just Moroike. CMD (talk) 01:10, 22 December 2024 (UTC)[reply]
    @CMD: I am not suggesting that the IP editor isn't being disruptive, but my point is that Moroike isn't making the situation better (using the example of that one article). You can see this by looking at their last 50 contributions where they have mostly just reverted this editor without using a summary. –MJLTalk 18:02, 23 December 2024 (UTC)[reply]
    The IP's edits were removed a total of 13 times on the page regarding the capital city of Azerbaijan, Baku. You can't let him continue engaging in further edit wars with other users besides Moroike, can you? Nuritae331 (talk) 17:24, 23 December 2024 (UTC)[reply]

    Since this IP user won't stop and is stonewalling, either he/should be temporarily blocked, or all the pages he is POV pushing without sources, should be semi-protected, so that only registered users can edit them. Moroike (talk) 21:37, 23 December 2024 (UTC)[reply]

    After he/she was blocked for 24 hours, this IP created an account as User talk:Ibish Agayev in order to evade the block and has resumed his/her POV pushing. Moroike (talk) 16:51, 24 December 2024 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Creating the need to make 400,000 unnecessary edits

    [edit]

    Can we please dp something about editors who make unnecessary changes to widely-used modules, and then need to change 400,000 talk pages to get the same result we had before the change? Thanks to this change from last week, which removed the parameter "living" from the bannershell, we now have more than 400,000 pages in Category:Pages using WikiProject banner shell with unknown parameters. After the "cleanup" by User:Tom.Reding (and perhaps others), we will have the exact same result as we had last week, no new functionality, no new categories, no improvement at all, but a lot of flooded watchlists.

    I tried to get him to stop at User talk:Tom.Reding#Cosmetic edits, to no avail. This isn't the first time, as you can see from that discussion. Fram (talk) 14:57, 20 December 2024 (UTC)[reply]

    If you want to discuss {{WikiProject banner shell}}, you should do so at Template talk:WikiProject banner shell.
    As for the size of the category, I have no plans to empty it, and was only going to update a few hundred more categories and templates.   ~ Tom.Reding (talkdgaf)  15:02, 20 December 2024 (UTC)[reply]
    You made nearly 2000 of such edits in the last few hours, and when asked to stop pointed me to a category with 400,000 entries. I have no way to know how many more you planned now or in future runs. Starting a discussion at the module would hardly stop you. Fram (talk) 15:10, 20 December 2024 (UTC)[reply]
    "when asked to stop pointed me to a category with 400,000 entries": incorrect. Since you wrongly thought I was making cosmetic edits, i.e. "no change in output or categories", the category was to inform you that they are not cosmetic.
    Regarding a BRFA for the bulk of the category, that's looking more likely since the category appears to be neglected.   ~ Tom.Reding (talkdgaf)  15:29, 20 December 2024 (UTC)[reply]
    Unnecessary removing a synonym and then making thousands of edits to remove the hidden cat created by that unnecessary change is not really any better than making cosmetic edits, the end result is that nothing has changed for the affected pages at all. Fram (talk) 15:33, 20 December 2024 (UTC)[reply]
    Not unnecessary. The Lua code is very complex and removing the need the support various settings makes the code both easier to read and maintain. As always, editors that don't want to see these edits can hide these by hiding the tag "talk banner shell conversion". Gonnym (talk) 12:32, 22 December 2024 (UTC)[reply]
    It doesn´t look as if the specific code to have these synonyms was very complicated though, the argument that in some cases two synonyms were used on one page with conflicting values was more convincing. And the edits I complained about did not have that tag, so no, even if people knew about hiding that tag, it wouldn't have helped here at all. Fram (talk) 16:04, 22 December 2024 (UTC)[reply]
    This was discussed in detail on Template talk:WikiProject banner shell. Ideally these edits would be done by an approved bot so they do not appear on people's watchlists. The main benefit is to merge the |blp= and |living= parameters. When both are in use, we find they often get conflicting values because one gets updated and the other does not. — Martin (MSGJ · talk) 17:25, 20 December 2024 (UTC)[reply]
    Isn't it more logical to first have a bot cleanup the unwanted parameter, then remove it from the template, and only then start populating the cat with the somehow remaining or since added instances? In any case, this is a typical bot task and shouldn't be done with massive AWB runs. Fram (talk) 17:39, 20 December 2024 (UTC)[reply]
    Yes, probably. But we have this mechanism already set up and I assumed Cewbot would deal with these as part of its normal activities. Happy to look at other options - maybe discuss on template talk? — Martin (MSGJ · talk) 18:23, 20 December 2024 (UTC)[reply]
    I don't know what this is about, but if the OP is correct, it is totally absurd to edit 400,000 talk pages for a tweak. Discussing at a template talk page monitored by those focused on the template would simply hide the issue. Johnuniq (talk) 03:53, 21 December 2024 (UTC)[reply]
    Edits like these should always be bots, so they can be filtered from watchlists. There are numerous other editors who have recently engaged in the mass additional of categories to articles which I had to ask them to stop as my watchlist was flooded. GiantSnowman 13:02, 22 December 2024 (UTC)[reply]
    Hiding bot edits from watchlists is not a viable option for many editors, since it also hides any non-bot edits that predate the bot edit (phab:T11790, 2007, unassigned). Users AnomieBOT, Cluebot III, Lowercase sigmabot III, Citation bot, et al edit with such high frequency that hiding their edits leads to an unacceptable proportion of watchlist items not appearing. (Also, Citation bot's edits should usually be reviewed, since it has a non-negligible error rate and its activators typically don't review its output, exceptions noted.)
    The code for maintaining two aliases for one parameter cannot possibly be so complex as to warrant a half million edits. If one of the two "must" undergo deprecation, bundle it into Cewbot's task. If the values don't match, have the banner shell template populate a mismatch category.
    In general, if a decision is made to start treating as an error some phenomenon that has previously not been a problem, and that decision generates a maintenance category with tens or hundreds of thousands of members, it is a bad decision and the characterisation of the phenomenon as "erroneous" should be reversed.
    At minimum, any newly instanced maintenance task scoped to over a hundred thousand pages should come before the community for approval at a central venue. Folly Mox (talk) 15:19, 25 December 2024 (UTC)[reply]
    Also, like, if only one of |blp= and |living= gets updated, shouldn't the net result be pretty obvious? Valid updates should really only go one direction. Folly Mox (talk) 15:24, 25 December 2024 (UTC)[reply]
    Meanwhile, the category has grown to over 800,000 pages. Perhaps next time an RfC to determine whether creating such a large cleanup task is warranted, would be better? Fram (talk) 16:34, 24 December 2024 (UTC)[reply]
    @Fram: this is logical. We should also make it a policy (or at least a guideline), something along the lines "if change would lead to edits/updating more than XYZ pages, a consensus should be achieved on a venue with a lot of visibility". Like Silver seren mentioned above, sometimes a formal consensus/discussion takes place, but it happens on obscure talk pages. —usernamekiran (talk) 14:01, 25 December 2024 (UTC)[reply]

    User:ZanderAlbatraz1145 Civility and Content #2

    [edit]

    This user has engaged in a lengthy display of disruption. Namely through incessant incivility I have noticed they were previously reported for.

    Instances such as ordering IP editors to stop editing articles, hostilely chastising them, making personal attacks in edit summary on several occasions, etc. Users such as @Waxworker: and @Jon698: can speak to their experiences, I'll outline mine.

    On December 10, I noticed on the article Luca Guadagnino's unrealized projects page several additions were made that didn't adhere to the article's purpose. Zander restored these with an introductory summary rife with bad faith assertions about my intelligence and asserting they'd engage in edit war behavior. For the most part there was an attempt to discuss the issue we had, but ultimately did not see eye to eye. I asserted I'd be escalating the issue to garner more substantive dialogue around it, Zander's response includes a needless "bite me". I made some attempts at engaging the topic at the article's talk page, in addition to WikiProject Film, it was over a week that saw no input. I would go on to state that (at the time) in two days, I would restore the page to it's status quo. I would do so, asking it not to be reverted. Zander reverted anyway, and after another terse interaction, I moved to nominate the article for deletion, finding with the conflicting views of what Unrealized meant, it was too open ended and led to these lists being essentially trivia. Since then, Zander has elected to take an antagonistic approach towards me, making swipes they openly admit add nothing to the discussion threads they're added to, and now that I am putting said comments behind collapsable tables for being offtopic, Zander is now doing the editing equivalent of mockingly repeating me, with edits such as this and this.

    This editor displays no interest in conducting themselves cordially or cooperatively on this website. Rusted AutoParts 23:20, 20 December 2024 (UTC)[reply]

    I've given them a warning for canvassing: [11] [12] [13] - The Bushranger One ping only 04:08, 23 December 2024 (UTC)[reply]
    And more personal attacks here - The Bushranger One ping only 05:36, 23 December 2024 (UTC)[reply]
    And they appear to be continuing editing while ignoring here. - The Bushranger One ping only 05:39, 24 December 2024 (UTC)[reply]
    This feels par for the course for Zander frankly. As noted with the bit about Zander reverting after an explicit edit summary saying not to and there being two days worth of me saying that edit would be made and they made no objections until the move was made. They disengaged from discussion but only re-engaged when the situation changed to their disliking. Rusted AutoParts 02:07, 25 December 2024 (UTC)[reply]

    User:Glenn103

    [edit]

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


    Glenn103 (talk · contribs · deleted contribs · logs · filter log · block user · block log) has been mass creating unsourced stubs about Cyrillic letters, most of which have been draftified. They've also disruptively edited in the past, such as: [14][15][16] '''[[User:CanonNi]]''' (talkcontribs) 01:41, 23 December 2024 (UTC)[reply]

    Most of these pages don't even make any sense (eg.: Draft:Yery with tilde). The user also ignores any notice about his articles being moved to draftspace by simply recreating duplicates of them (eg.: Draft:Tse with caron & Tse with caron). Immediate action may be needed. Est. 2021 (talk · contribs) 07:38, 23 December 2024 (UTC)[reply]
    Given a uw-create4im with directions to come here, let's see what happens. - The Bushranger One ping only 08:00, 23 December 2024 (UTC)[reply]
    They've continued editing, this time adding infoboxes to the articles, so I don't think the warning worked... '''[[User:CanonNi]]''' (talkcontribs) 08:10, 23 December 2024 (UTC)[reply]
    I have blocked them from article space and page moves, and will leave note on talk page to come here. — rsjaffe 🗣️ 15:33, 23 December 2024 (UTC)[reply]

    Honestly, this almost feels like trolling. Their basic procedure seems to be: pick a random Cyrillic letter. Combine it with a random diacritic. Write a short stub on the combination, saying effectively "this letter combination is not used anywhere." The occasional historical mentions ("this combination was used in such-and-such obscure Siberian language") are completely unsourced, of course. (Everything is unsourced.) Oddwood (talk) 04:43, 24 December 2024 (UTC)[reply]

    Excuse me for detracting from the report, but this was your 4th edit, your last edit was in January 2016... how have you found yourself here of all places?
    I mean you might have a point, but wow. – 2804:F1...57:88CF (::/32) (talk) 04:57, 24 December 2024 (UTC)[reply]

    Similar behavior to PickleMan500 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log· investigate · cuwiki) and other socks puppeted by Abrown1019 (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log· investigate · cuwiki), which also made tons of drafts on Cyrillic characters that cited few sources (and none with in-depth coverage). Most drafts have been WP:G5'd, of course, so only those with admin perms can verify the deleted contribs. Since these socks have been banned (WP:3X), I haven't notified them of this discussion. Rotideypoc41352 (talk · contribs) 17:08, 24 December 2024 (UTC)[reply]

    Good catch, and looking at the contribution histories it  Looks like a duck to me. Changing the block to indef as a sock accordingly. - The Bushranger One ping only 07:22, 25 December 2024 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    North Korean involvement in Russian-Ukraine war discussion

    [edit]

    The inclusion of North Korea as a belligerent in the infobox for the "Russian invasion of Ukraine" article has been a point of extensive and protracted discussion since September. A formal Request for Comment (RfC) on this matter ran for several weeks and was closed with a clear consensus to include North Korea as a combatant based on reliable sources and expert analysis. However, despite the closure, the discussion has continued unabated across multiple threads, with certain editors repeatedly rehashing resolved points and questioning the validity of reliable sources, leading to significant disruption.

    Key Points:

    1. Prolonged Discussions and RfC Closure:
      • The RfC on North Korea's inclusion was conducted thoroughly, with a wide range of arguments presented by both sides.
      • The closing administrator, S Marshall, determined there was a clear consensus to include North Korea as a belligerent based on reliable sources and the strength of arguments.
      • The close explicitly allowed for reevaluation if new battlefield events or sources emerged, but no substantial new evidence has invalidated the prior consensus.
    2. Ongoing Disruption:
      • Despite the RfC's resolution, the same arguments are being repeated across multiple threads, often by the same editors.
      • This behavior includes undermining reliable sources, misrepresenting their content, and insisting on a higher standard of verification (e.g., requiring firsthand evidence of North Korean combat, which is unreasonable given the context).
    3. Reliable Sources Confirming North Korean Involvement:
      • Multiple reputable outlets, including the BBC, Reuters, and Pentagon statements, confirm North Korean military involvement and casualties in the conflict.
      • Experts from institutions like Chatham House and RUSI have explicitly stated North Korea's role in combat, aligning with the community's decision.
    4. Impact on the Community:
      • The continued disruption consumes editor time and resources, detracting from the article's improvement.
      • These actions disregard Wikipedia's consensus-building principles and guidelines for resolving disputes. This dispute has been ongoing for months, with multiple threads being opened and closed on the same topic.

    Request for Administrative Action:

    I respectfully request that administrators address the following issues:

    1. Enforce the consensus reached in the closed RfC, as no new evidence significantly alters the previous conclusions.
    2. Discourage editors from rehashing resolved discussions, particularly when arguments have been repeatedly addressed and dismissed.
    3. Consider imposing a topic ban or other appropriate measures on editors who persist in disrupting the article with repetitive or bad-faith arguments.

    This matter has been discussed exhaustively, and it is essential to prioritize Wikipedia's goals of maintaining a high-quality, well-sourced, and consensus-driven encyclopedia. Thank you for your attention to this matter. UPDATE: I just noticed that North Korea was removed as a belligerent and added to the 'supported by' section, completely violating the consensus. Rc2barrington (talk) 08:48, 23 December 2024 (UTC)[reply]

    Since this report isn't really about an incident and your request is directed towards admins, I think this complaint would be better placed at WP:AN rather than ANI. It will also need more specifics, which articles, which edits, which editors. You'll need to provide that. I also question whether or not these are content standards that the community can't handle on their own. Liz Read! Talk! 09:50, 23 December 2024 (UTC)[reply]
    I was going to post it at WP:AN but it said: "This noticeboard is for issues affecting administrators generally – announcements, notifications, information, and other matters of general administrator interest.
    If your post is about a specific problem you have (a dispute, user, help request, or other narrow issue needing an administrator), you should post it at the Administrators' noticeboard for incidents (ANI) instead. Thank you."
    I posted it on ANI beecause my specific problem was this dispute Rc2barrington (talk) 12:07, 23 December 2024 (UTC)[reply]
    The original post in this thread appears to resemble LLM output. GPTzero confirms this impression, rating text as "99% probability AI generated". Using AI to generate ANI submissions is highly inappropriate. Axad12 (talk) 18:01, 23 December 2024 (UTC)[reply]
    Even when a message appears to be AI-generated, I think it is worth considering whether or not it is pointing out an actual problem. I think editors might be ignoring the results of an RFC, I just don't think asking for administrators to monitor a subject area, without identifying specific articles, is a feasible solution. It does seem like, possibly, a point that could come up in a complaint at AE regarding the Ukraine CTOP area. Liz Read! Talk! 19:55, 23 December 2024 (UTC)[reply]
    I had a peek and it's a messy RfC and, as is generally the case with a messy RfC had a very involved closure message which seems to reflect that the closer felt constrained by the framing of the RfC. I didn't see any immediate indication in the edit history that anyone had tried to implement the RfC result and been rebuffed (although I might have missed it). So there's some smoke here but, I think, not a ton of fire. Simonm223 (talk) 20:21, 23 December 2024 (UTC)[reply]
    Liz, I don't disagree but I'm not at all convinced that use of AI is a positive contribution to CTOP areas. Axad12 (talk) 20:27, 23 December 2024 (UTC)[reply]
    It was written with AI assistance. Not all AI. ai detectors aren’t considered reliable, because you can put the U.S. constitution through one and it says 100% AI generated. Regardless, whether it’s AI or not has nothing to do with the topic. It’s just that there’a been so many discussions and when I checked the info box it said ‘supported by”, violating the consensus of the RFC Rc2barrington (talk) 12:45, 24 December 2024 (UTC)[reply]
    you can put the U.S. constitution through one and it says 100% AI generated – Well, I just put it through GPTzero and got 97% human. Might be best if you don't just make up random "evidence". EEng 17:25, 25 December 2024 (UTC)[reply]
    I think the underlying issue here is that if you use AI to generate text which looks like obvious AI output then readers will wonder "does the end user even have sufficient English to understand what the AI has generated for them?" and "did the end user understand the material prior to deciding to employ AI?". Thus if a user is fluent in English, as you obviously are, it will always be better to communicate in your own voice.
    At the end of the day, a user making a valid point in their own voice is generally speaking going to be taken more seriously than a user employing LLM output.
    There are plenty of other reasons for users not to employ AI (see the recent thread here [17] for extensive coverage) but the argument above seems like a good practical reason for fluent English speakers to always prefer using their own voice.
    You will see from the recent thread that many users here are vehemently against AI use. Axad12 (talk) 15:46, 24 December 2024 (UTC)[reply]
    I understood the material very well, its not like I just used 100% AI out of nowhere. I know the context. I have been involved in this discussion since September. Rc2barrington (talk) 16:43, 24 December 2024 (UTC)[reply]
    It's a respect thing. It's disrespectful of other editors to make them read chatbot output rather than your words. Simonm223 (talk) 16:49, 24 December 2024 (UTC)[reply]
    External videos
    video icon Rc2barrington's appearance on Jeopardy
    Rc2barrington's user page says This user believes in the bright future AI and robotics will bring, so there's probably no point in arguing here. However, I simply observe that in any kind of discussion where you're trying to convince other people, don't use a method that aggravates a significant number of readers (probably a significant majority of readers). It really is that simple. Axad12 (talk) 19:11, 24 December 2024 (UTC)[reply]

    Putting the use of LLM aside, however you compose your message you should comply with the basics of ANI. This includes not making allegations without supplying evidence. This would normally be in the form of diffs but in this case just links might be fine. But User:Rc2barrington has provided none.

    Probably because this is because their initial complaint appears to be unsupported by what's actually happening. They claimed "Despite the RfC's resolution, the same arguments are being repeated across multiple threads, often by the same editor". But where is this? I visited the talk page, and what I see is here Talk:Russian invasion of Ukraine#Post RFC discussion there was a request for clarification from the closer, something which is perfectly reasonably and which the closer followed up on. The OP then offered an interjection which frankly seemed unnecessary. There was then a very brief forumish discussion. To be clear, AFAICT no one in the follow up discussion was suggesting any changes to the article. So while it wasn't he most helpful thing as with any forumish discussion; it's hardly causing that much disruption especially since it seems to have quickly ended and also cannot be called "the same arguments" since there was no argument. No one in that discussion was actually suggesting changing the article.

    Then there is Talk:Russian invasion of Ukraine#North Korea RFC aftermath discussion. There was again some forumish discussion in this thread which again isn't helpful but wasn't that long. But there was also discussion about other things like the name of the article and whether to restructure it. To be clear, this isn't something which was resolve in the RfC. In fact, the closer specifically mention possible future issues in a non close comment.

    Next we see Talk:Russian invasion of Ukraine#Follow up to the previous discussion (Request for comment, can we add North Korea as a belligerent?). Again the main focus of the discussion is in how to handle stuff which wasn't dealt with in the RfC. There is a total of 2 short comments in that thread which were disputing the RfC which is unfortunate but hardly something to worry ANI about.

    Next there is Talk:Russian invasion of Ukraine#Can we add a Supported by section for Ukraine in the infobox?. DPRK was briefly mentioned there but only in relation to a suggestion to change the infobox for other countries. No part of that discussion can IMO be said to be disputing the DPRK RfC. Next we have Talk:Russian invasion of Ukraine#Remove Belarus from the infobox. Again DPRK was briefly mention but only in relation to other countries. No part of that discussion can be said to be disputing the RfC. AFAICT, the only threads or comments removed from the talk page since the closure of the RfC was by automated archival. The only threads which seem to be post close are on Talk:Russian invasion of Ukraine/Archive 20 and none of them seem to deal with North Korea.

    So at least on the article talk page I don't see what the OP has said is happening. The tiny amount of challenging of the RfC is definitely not something ANI needs to worry about. Even the other forumish or otherwise unproductive comments aren't at a level that IMO warrants any action IMO. If this is happening somewhere else, this is even more reason why the OP needed to provide us some evidence rather than a long comment without anything concrete, however they composed it.

    Nil Einne (talk) 10:15, 25 December 2024 (UTC)[reply]

    Concern About a New Contributor

    [edit]

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


    Kriji Sehamati (talk · contribs · deleted contribs · logs · filter log · block user · block log)

    Dear Wikipedians,

    I hope you’re doing well. I wanted to inform you about a new contributor @Kriji Sehamati, despite lacking experience, has repeatedly attempted to vandalize multiple articles. These articles were properly aligned with Wikipedia’s guidelines and reviewed by experienced contributors, but he/she seemed unwilling to understand or respect their adherence to the policies.

    I believe your experience could help address this situation effectively.

    Looking forward to your advice on how to proceed.

    Thankyou! 𝒮-𝒜𝓊𝓇𝒶 15:21, 23 December 2024 (UTC)[reply]

    "Vandalize" is a very loaded word here with a specific meaning. As far as I can tell, what they've done is nominate 4 articles for deletion, and your response has been to accuse them of vandalism, ignoring dispute resolution procedures and making personal attacks – none of which I can see at a glance through their contributions.
    Perhaps if you supplied evidence of this behaviour, someone would be able to help? If your issue is that they've nominated 4 articles of which you are a major contributor and are doing so by going through your contributions in order to find articles to nominate for deletion with specious reasons, then this board would be the place to come. If not, then making your arguments for keeping the articles on the AfDs in question would be your best bet.
    By the way [18] [19] [20] [21] is forum shopping. Stop that. 81.2.123.64 (talk) 16:06, 23 December 2024 (UTC)[reply]
    (ec) This is an odd one. As S-Aura failed to provide diffs, I looked at Kriji Sehamati's contribution history. New account (9 Dec) began editing today, created two drafts and made a bunch of edits to those. Then began adding COI tags to articles S-Aura wrote, nominated those articles for deletion, and then left a possible UPE template on S-Aura's talk page. Really seems to be something weird going on here between those two. (In addition to opening this ANI thread, S-Aura asked for help with basically the same message on the talk pages of Ipigott, Ryan shell, CFA, and BusterD, and S-Aura opened same complaint at AN.) Schazjmd (talk) 16:06, 23 December 2024 (UTC)[reply]
    I am concerned that User:Kriji_Sehamati’s actions, including unjustified deletion nominations and spamming, are disruptive and violate Wikipedia’s guidelines.
    She seems to lack understanding of basic Wikipedia guidelines, particularly those related WP:GNG and WP:NPOL. 𝒮-𝒜𝓊𝓇𝒶 16:40, 23 December 2024 (UTC)[reply]
    You were asked to provide diffs. You did, almost, here but then reverted yourself. Those diffs (well, the ones before those diffs) are just the other user nominating articles for deletion (which is allowed) or tagging them for what they believe to be conflict of interest edits (which is also allowed).
    Please provide some actual evidence that the other user is engaging in chronic, intractable behaviour, rather than just not editing how you would like them to. 81.2.123.64 (talk) 17:21, 23 December 2024 (UTC)[reply]
    Here are some diffs highlighting her problematic edits. However, I believe that many of her contributions may be in violation of Wikipedia’s guidelines. It appears she has specifically targeted me and added the COI tag multiple times to the same page. I would appreciate it if you could review her actions more thoroughly:
    [22]
    [23]
    [24]
    [25]
    and many more
    Thankyou! 𝒮-𝒜𝓊𝓇𝒶 17:33, 23 December 2024 (UTC)[reply]
    We wouldn't generally treat an AfD as vandalism. Simonm223 (talk) 17:39, 23 December 2024 (UTC)[reply]
    I understand your point about AfDs not generally being treated as vandalism. However, I noticed that the major contribution history of the user seems suspicious. 𝒮-𝒜𝓊𝓇𝒶 17:42, 23 December 2024 (UTC)[reply]
    Not from where anybody else is standing so far. I get that you're upset to have four articles of yours nominated for deletion, and if you have any evidence at all that you are being deliberately targeted by the other editor, then people will very much act on that. Please provide it. 81.2.123.64 (talk) 17:58, 23 December 2024 (UTC)[reply]
    I am here to contribute and edit articles in accordance with Wikipedia’s guidelines. However, today a new user targeted me and falsely blamed me for actions that are not accurate. I believe this is unfair and not in line with the collaborative nature of the platform. 𝒮-𝒜𝓊𝓇𝒶 18:04, 23 December 2024 (UTC)[reply]
    Please provide evidence of this. 81.2.123.64 (talk) 18:06, 23 December 2024 (UTC)[reply]
    Please check! [26] 𝒮-𝒜𝓊𝓇𝒶 18:07, 23 December 2024 (UTC)[reply]
    The articles that have been nominated for deletion discussion have been reviewed by experienced contributors. These discussions involve articles about judges and lawyers, under WP:NPOL, a valid criterion according to Wikipedia’s guidelines. Therefore, the deletion decision was made after carefully reviewing these articles. 𝒮-𝒜𝓊𝓇𝒶 18:11, 23 December 2024 (UTC)[reply]
    Honestly it looks like this user, rightly or wrongly, believes you have a conflict of interest and are acting on the basis of that assumption. I would suggest, if you don't have a CoI, talking to them about this and maybe asking why they've come to this conclusion. Simonm223 (talk) 18:10, 23 December 2024 (UTC)[reply]
    They have just started targeting my contributions, and I tried to inform her about the situation. However, she is acting as if she knows everything about Wikipedia and is dismissing my concerns. 𝒮-𝒜𝓊𝓇𝒶 18:15, 23 December 2024 (UTC)[reply]
    @Kriji Sehamati: hasn't edited since their AfD spree earlier today, let's wait and see what their response here is when they return to editing. Schazjmd (talk) 18:16, 23 December 2024 (UTC)[reply]
    • We need to stop focusing on the OP's calling this vandalism; it is not. I've changed the header to reflect that. That said, the new user's edits are problematic and merit scrutiny. As for the UPE stuff, I've removed that post from the OP's Talk page; it's nonsensical coming from a new user and does not merit a response.--Bbb23 (talk) 18:42, 23 December 2024 (UTC)[reply]
    • It is, of course, not vandalism to nominate articles for AFD discussions as long as a legitimate deletion rationale is provided and the article hasn't just been discussed at a recent AFD. However, I don't think it's a good sign when a brand new editor claims to understand all of Wikipedia policies and whose first actions are to nominate articles at AFDs. They are almost never an actual new editor, especially when they know how to even set up an AFD or are familiar with using Twinkle on their first day of editing. Liz Read! Talk! 19:34, 23 December 2024 (UTC)[reply]
      It seems that she is not new to Wikipedia and might be operating multiple accounts. It appears she has an issue with one of my contributions, as she created her account just 15 days ago, yet she already has a good understanding of tools like Twinkle and AfD procedures. This level of familiarity suggests prior experience on the platform. I am now requesting her account to be blocked as I am completely disturbed by her repeated allegations and disruptive behavior. 𝒮-𝒜𝓊𝓇𝒶 11:32, 24 December 2024 (UTC)[reply]
      I am now genuinely confused—if all my contributions are not good, then why am I even here? Were the experienced editors who reviewed and approved these pages also mistaken? A newcomer, who joined just recently, is now disrupting and questioning the validity of all the work that has been carefully reviewed and maintained by experienced contributors. This situation is deeply discouraging. 𝒮-𝒜𝓊𝓇𝒶 11:58, 24 December 2024 (UTC)[reply]
      Please resolve this situation—either block her for her disruptive behavior. How can i continue working under such constant targeting and stress ? 𝒮-𝒜𝓊𝓇𝒶 12:00, 24 December 2024 (UTC)[reply]
      User:S-Aura, you seem to be making unsupported personal attacks against User:Kriji Sehamati. You should provide specific evidence of wrongdoing, including diffs, or your arguments here will fall on deaf ears (and bring consequences for you). Meanwhile, as a filer on ANI, you have brought all your own edits to close scrutiny by the community. You may have to face that smart people disagree, and this is how we sort disagreements out on English Wikipedia. You are not required to edit, but we encourage you to do so. Nobody is going to block Kriji Sehamati at this point, because you've given us no reason to do so. BusterD (talk) 12:01, 24 December 2024 (UTC)[reply]
      Meanwhile, in the last few minutes S-Aura has disruptively created a second thread about this exact issue on this same board, which was reverted by another editor. This is intentional disruption. BusterD (talk) 12:07, 24 December 2024 (UTC)[reply]
      As to the question "Why am I here?", poets and artists have been trying to answer this question for eons. Epistemology is outside the scope of this board, but there are articles about it. Show up to edit if you want to, but expect disagreement from time to time. (That's actually a sound answer to any epistemology question as well.) BusterD (talk) 12:16, 24 December 2024 (UTC)[reply]
      Dear @BusterD,
      It means I have been proven wrong, and that user’s contributions have been more focused on me, which is quite insufficient to catch someone’s lie that she is pretending to be new, when in fact she is old.
      Also, I am not against AfD; I am simply expressing my opinion. 𝒮-𝒜𝓊𝓇𝒶 13:12, 24 December 2024 (UTC)[reply]
      Could you please rephrase your point here? I don't understand. While it's okay to be suspicious that this editor is somehow socking or doing something else deceptive due to the familiarity, it seems unacceptable to deliberately accuse them of such repeatedly without firmer evidence. Remsense ‥  13:19, 24 December 2024 (UTC)[reply]
      Dear @Remsense,
      I am not engaged in paid activities on Wikipedia, and she claimed that I am connected with the subject, who is a judge, lawyer, etc. You all should understand that this is not a trivial matter; justice is a very respected position. Making such allegations can escalate court cases. I would like to remind you of the Wikipedia vs. ANI case. 𝒮-𝒜𝓊𝓇𝒶 13:24, 24 December 2024 (UTC)[reply]
      One thing you need to understand immediately is you should never make another post that sounds vaguely like a legal threat, as you've just done above. Seriously. That intonation is seriously not helping us decide who's right or wrong here. Remsense ‥  13:27, 24 December 2024 (UTC)[reply]
      Okay! 𝒮-𝒜𝓊𝓇𝒶 13:35, 24 December 2024 (UTC)[reply]
      I will caution you that this is tiptoeing right up to the edge of WP:NLT and you'd be advised to avoid making legal threats. Simonm223 (talk) 13:28, 24 December 2024 (UTC)[reply]
      Dear @Simonm223,
      I am merely showing that she can potentially do something inappropriate. I am following the guidelines and not making any legal threats. 𝒮-𝒜𝓊𝓇𝒶 13:31, 24 December 2024 (UTC)[reply]
      Accusing another editor of potentially making legal threats is not much better, when there is no concrete evidence that they would do so. Being interested in articles about judges does not suffice. Remsense ‥  13:32, 24 December 2024 (UTC)[reply]
      The page of Justice Subramonium Prasad, who had conducted over the Wikipedia vs. ANI court hearing, was also created by me. 𝒮-𝒜𝓊𝓇𝒶 13:28, 24 December 2024 (UTC)[reply]
      State plainly what the implication you are making here is, because what I'm hearing is "I'm familiar with people who have hit Wikipedia with a mallet in court before, and I can make sure it happens again". Remsense ‥  13:30, 24 December 2024 (UTC)[reply]
      This is becoming a rabbit hole. I urge you not to pursue the rabbit further. BusterD (talk) 13:33, 24 December 2024 (UTC)[reply]
      Good call, I'll retract the above. Remsense ‥  13:34, 24 December 2024 (UTC)[reply]
      No, that is not what I am implying. 𝒮-𝒜𝓊𝓇𝒶 13:33, 24 December 2024 (UTC)[reply]
      No one has said your contributions are not good. However, it should be noted that a draft being accepted at AfC or a new page having been patrolled does not guarantee greater scrutiny would not result in a valid AfD nomination. That said, echoing others here it's clear something problematic is up with this user's behavior. Remsense ‥  12:02, 24 December 2024 (UTC)[reply]
      You can't both criticize someone for lack[ing] understanding of basic Wikipedia guidelines, particularly those related WP:GNG and WP:NPOL, and then argue that she is too familiar with the platform to be a newcomer for knowing how to file an AfD. I wouldn't be surprised if most people here knew how to file an AfD before knowing all 14 notability guidelines by heart. Chaotic Enby (talk · contribs) 12:59, 24 December 2024 (UTC)[reply]
      There are detailed instructions on filing an AfD that can be found by googling "how can I get a Wikipedia page deleted" - if somebody had some personal reason for wanting to have pages removed it doesn't strain credibility to think that's why they created a WP account and that they just followed the very clear instructions on the appropriate pages.
      In fact that might explain why some of the AfD filings were reasonable and some were, on their face, incorrectly filed. If you looked up the AfD process but not criteria that is the likely outcome. That's why I find the "new user files AfDs must be a sock" idea here somewhat uncompelling. Simonm223 (talk) 13:04, 24 December 2024 (UTC)[reply]
    • I believe we're entering boomerang territory at this point. Opinions? BusterD (talk) 13:35, 24 December 2024 (UTC)[reply]
      I think OP is upset that a cluster of their articles were put up at AfD. This in itself is understandable, but while there's reason to think there might be mischief by Kriji Sehamati, we don't have any real evidence of it. We either need the OP to make it clearer what misconduct, if any, has occurred, or they need to drop the stick. Remsense ‥  13:37, 24 December 2024 (UTC)[reply]
      The OP has been intentionally disruptive (by creating a new ANI thread which was reverted), and this thread is going nowhere. IMHO, there's nothing ANI can do here. Everything I'm reading about should be resolved at the page talk and user talk level, in my opinion. The AfDs are underway. If dispute resolution is needed, fine. Nobody is harming S-Aura. S-Aura can't come crying to ANI (or four random user talk pages like mine) anytime someone merely disagrees with them. BusterD (talk) 14:08, 24 December 2024 (UTC)[reply]
      I'd have said close with trout for all if not for creating the second thread at AN/I. Based on that I'd say the OP should be formally cautioned against such antics in the future. Simonm223 (talk) 14:10, 24 December 2024 (UTC)[reply]
      I should have added that I largely hold with Remsense in their position. BusterD (talk) 14:15, 24 December 2024 (UTC)[reply]
      User:Kriji Sehamati‬ is definitely a sock puppet on Wikipedia, but we don’t have any evidence because understanding Wikipedia’s AfD process so quickly can be a bit challenging. I have no problem with AfD regarding my contributions, and it’s a good thing that experienced contributors are giving their feedback. If you believe that the kriji is 100% correct and her activity is not suspicious, then this discussion should be closed. 𝒮-𝒜𝓊𝓇𝒶 14:27, 24 December 2024 (UTC)[reply]
      You need to stop insisting this is definitely the case if you don't have any evidence for it, period. Remsense ‥  14:28, 24 December 2024 (UTC)[reply]
      S-Aura, how did you make the determination User:Kriji Sehamati‬ is definitely a sock puppet on Wikipedia? Please share your process. That's a personal attack, and requires proof to prevent you from being in violation of WP:NOPERSONALATTACKS. I've looked at the AfDs and they seem reasonable to me. When you've provided strong sources the article is being kept. So far the jury is out on the others. Both of you seem to be writing articles about obscure living persons who wouldn't normally (by my cursory reading) have a Wikipedia article about them because reliable sourcing is not readily found. When I see that, I must suspect COI or undeclared unpaid editing here, but nobody's admitting to it. BusterD (talk) 15:05, 24 December 2024 (UTC)[reply]
      S-Aura's continuing to issue personal attacks makes it more difficult for us to just close this (without some form of consequence for the editor making unproven personal attacks after they've been warned repeatedly). BusterD (talk) 15:08, 24 December 2024 (UTC)[reply]
      I have made a level-four user talk page warning for the personal attack. FYI. We've been very nice about this up 'til now, but we need to stop being so kind. Doing foolish things has real world consequences. BusterD (talk) 15:17, 24 December 2024 (UTC)[reply]
    • Both editors' apparent use of AI is certainly disruptive. If it continues, it should lead to blocks. C F A 15:10, 24 December 2024 (UTC)[reply]
      No personal hate intended, but I just found this and thought it would be worth checking.[27] 𝒮-𝒜𝓊𝓇𝒶 16:49, 24 December 2024 (UTC)[reply]
      It would be nice if you could explain the significance for those who do not speak Hausa. Remsense ‥  16:51, 24 December 2024 (UTC)[reply]
      She had made contributions to pages in other languages a few months ago. I am attaching her contributions link.[28] 𝒮-𝒜𝓊𝓇𝒶 16:59, 24 December 2024 (UTC)[reply]
      How does this constitute evidence of sockpuppetry if we aren't to know what exactly happened? There's a reason we don't just automatically block anybody who is blocked on another language wiki, and I looked through the edits some and didn't find anything outrageous that made it past the language barrier. Remsense ‥  17:01, 24 December 2024 (UTC)[reply]
      I agree that it’s important to ensure we have solid evidence before making conclusions. I appreciate your perspective on not automatically blocking users based on blocks from other language wikis. 𝒮-𝒜𝓊𝓇𝒶 17:17, 24 December 2024 (UTC)[reply]
      Please don't reply to me or others using ChatGPT. It is flat-out rude. Remsense ‥  17:18, 24 December 2024 (UTC)[reply]
    • Support BOOMERANG - I've been uninvoled and have mainly just been watching the back-and-forths, but the personal attacks and VESTED mindset, such as "questioning the validity of all the work that has been carefully reviewed and maintained by experienced contributors", concerns me. Not sure for how long, but I don't think anything longer than a months is appropriate given the circumstances. EF5 15:47, 24 December 2024 (UTC)[reply]
    • This whole thread, but especially the 16:49, 24 December 2024 (UTC) comment, feels like the OP is just throwing literally everything at the wall to see what sticks. But, worse, what is being thrown at the wall lacks any significant body of evidence to support. I note that a personal attack warning has been given for the continued unfounded accusations being presented, which I think is a good move. I don't support a block at this point, although if I was the OP I would withdraw this complaint and/or drop the stick and walk away from this topic as a matter of urgency to avoid continuing to make the situation worse. Daniel (talk) 17:41, 24 December 2024 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Darkwarriorblake making aspersions

    [edit]

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


    Postscript: Ah, someone just close this, I don't care any more.  — Hex talk 22:56, 23 December 2024 (UTC)[reply]


    I'm posting here after a particularly underwhelming interaction with an editor in the form of edit summaries. I'll need to provide the context of a brief content dispute which hopefully won't take too long and then get to the point. I'm not asking for anyone to take my side in the dispute.

    Trading Places is a widely acclaimed comedy film from 1983, which is also widely acknowledged to have problematic elements by modern standards, including a scene in which the villain of the piece, stuck in a gorilla costume, is locked in a cage with a real gorilla, which is implied to sexually penetrate him without his consent.

    The article states that G. Gordon Liddy demurred being cast in the role upon finding that out. The citation for this claim is a listicle on Indiewire, which contains the sentence

    Reportedly, Liddy was on board until he got to the part where Beeks becomes a gorilla’s mate.

    Reportedly by whom is not mentioned, let alone is there a direct quotation from Liddy. Plus as can be seen the words "becomes a gorilla's mate" are linked to a very poor quality, hand-held video of the scene in question playing on a television. This alone should be enough to raise serious questions about the use of this "source" in a featured article.

    The content dispute began when I changed it like this (diff) with the comment Don't mince words; the interaction between Beeks and the gorilla is rape played for laughs:

    Liddy was interested in the offer until he learned that Beeks becomes the romantic partner of a gorilla.
    +
    Liddy was interested in the offer until he learned that Beeks is raped by a gorilla.

    This was reverted (diff) by Darkwarriorblake with the comment not what the source says.

    After thinking about it a moment I came to the conclusion described above about the quality of the source, and decided that it was better out than in, which is what I should have done in the first place.(diff)

    ...was offered the role of corrupt official Clarence Beeks. Liddy was interested in the offer until he learned that Beeks becomes the romantic partner of a gorilla. Paul Gleason took the role;...
    +
    ...was offered the role of corrupt official Clarence Beeks with Paul Gleason eventually taking the role;...

    My accompanying comment was (a) That was the source's voice, not Liddy's. It's called a euphemism. Demonstrable by how it links to a clip of the scene in which a man is raped by a gorilla. (b) Source says "reportedly" for this claim, without evidence. Poor quality source. Removing claim

    That was reverted by Darkwarriorblake (diff) with the comment Nothing wrong with Indiewire as a source, if there is I'd raise it at Wikipedia:Reliable sources. Until then, there's a talk page for you to use per WP:BRD. Your comments sound agenda driven and therefore not Neutral.

    This is where the reason for me to raise this at this board begins, because that's solidly an example of casting aspersions. It came on top of a revert which reintroduced a claim cited to a rumor in a blog post into a featured article, but that's really not my concern, because if the champions of the featured article process have decided that it's somehow acceptable for our "best" content then I'm just going to move on to something else rather than argue.

    There's one final back and forth which was enough to motivate me to post here. First, I reverted that revert ([29], my only time using the actual "Undo" button today), with this comment: a good source doesn't say "reportedly" (ie, spread a rumor), it specifies the origin of a fact. My only "agenda" is with a crap listicle being used as a reference, regardless of who published it. Take it to talk if you want to argue for the continued inclusion of a trash ref in a featured article, or source the claim properly yourself.

    This was reverted - again - by Darkwarriorblake (diff) with the comment How are you an admin? "rape played for laughs" is an agenda, this went through FA as is so WP:STATUSQUO and WP:BRD apply. You must go to the talk page, not I. I don't know if you're going through a bad time or something but this isn't how an admin should be acting or communicating with others, up to and including WP:EDITWARRING

    At this point it's gone firmly into the realm of knee-jerk reversions, because if Darkwarriorblake took the time to read the article which they've reverting changes to for years (is this ownership? Kind of feels that way), they would get down to the critical reassessment section. Which says "some critics have praised the film while highlighting elements that they believe aged poorly, including racial language, the use of blackface, and the implied rape of Beeks by a gorilla", cited to articles in four major publications. Or, you know, even search Google for "Trading Places gorilla rape".

    So anyhow regardless of whether the Indiewire source is deemed suitable or not, I'm just wondering what the feeling here is about someone making goofy assertions on the record that another editor has "an agenda" (what agenda could it be?) and may not be emotionally stable, which really doesn't feel like assuming good faith at all.  — Hex talk 20:03, 23 December 2024 (UTC)[reply]

    Hrrm, this seems a bit excessive.
    • I've added a second source for the claim. Really this should've been the first option rather than removing the content.
    • The first summary was, as stated, "Don't mince words; the interaction between Beeks and the gorilla is rape played for laughs". "Rape played for laughs" is a loaded comment and not something said in the article or the source text, so it's a personal opinion, it's not neutral, it's agenda-driven.
    • When this was reverted, the editor just removed the content entirely claiming IndieWire was unreliable. There is, as far as I'm aware, nothing wrong with Indiewire. I've since found a second source, the Telegraph, which is reliable per Wikipedia:Reliable sources/Perennial sources.
    • The editor ignored WP: BRD when raised, and as an admin they should adhere to policy.
    • The editor states that they are an admin on their page. Assuming this is true, the aggressiveness of their edits, hyper focus on the single area, and use of words like "crap listicle" seemed out of line with what I, personally, would expect from an admin on Wikipedia, certainly someone who has been so for nearly two decades. Perhaps the edit summary wasn't the place to have that discussion but, as stated, they weren't adhering to WP: BRD to start a discussion, and in the interim the article needed putting back to the status quo.
    • I find accusations of OWNERSHIP often tend to come when people don't get their way. Which is fine. I have plenty of reversions on the page for people adding unsourced content and there are plenty of changes as well. I find someone removing sourced content and me putting the sourced content back to not really be something you can fling ownership at.
    • Within the context of the film, Beeks does become the romantic partner of the gorilla, it seemed more appropriate and encylcopedic text than just saying 'rape', and neither source I've added says that either.
    • Anyways, my edit history shows I'm a massive contributor and helper and it's nearly Xmas, and I don't feel like engaging with this any further, good luck Hex. Darkwarriorblake (talk) 20:27, 23 December 2024 (UTC)[reply]
    Of course you don't, having ignored the actual matter of your conduct that I'm raising here. Your comments about the content of the article are irrelevant.  — Hex talk 20:43, 23 December 2024 (UTC)[reply]
    • Hex's position is not wholly supported, although in the entire issue, their toolset is irrelevant. There was no incivility on either part, and an all-out edit war seems to have been averted.
      Fundamentally the change Hex wanted to make was pure OR; rape may have been intimated—or, as Hex themself admits, implied—but its never overtly stated and is a wholly loaded term. This is the interpretation of an editor, not of secondary sources. If there is a pron=blem with Indywire as a source—currently used in 1000s of articles—take it to WP:RSN. If it's disputed that it's a high quality source per WP:FA?, then take it to WT:FAC. Accusations of OWNership are as unhelpful—and as much an aspersion—as accusations of agenda-led editing. In fact, for OWNership, Hex should read the relevant policy: here, it is WP:FAOWN, which not only allows for careful stewardship of featured material, but requires significant changes to the consensus version to be discussed on talk; I don't suppose there's any suggestion that introducing rape—particularly "played for laughs"—wouldn't be a significant addition.
      Really though, this is an overblown content dispute which should have started with one revert each, and ended on the talk page. --SerialNumber54129A New Face in Hell 21:10, 23 December 2024 (UTC)[reply]
      "Never overtly stated... 'played for laughs' [would] be a significant addition" - here's an interview with John Landis, the director.

      One of the executives was deeply appalled by a man being sexually molested by a gorilla. And I said you know, it's a joke and it goes by very quickly. But the first preview was very successful and it all went away. [Laughs]

      Feel free to amend the article on that basis. I'm certainly not interested in spending any more time on it.  — Hex talk 22:48, 23 December 2024 (UTC)[reply]

    Followup

    [edit]

    I just want to say that, now that we've had an ANI thread on the subjeect of Gordon Liddy's feelings about portraying the romantic partner of a gorilla, I can die happy.

    While we're on the subject, our article on Liddy recites that Prior to his departure from the FBI in 1962, Liddy sought admission to various bars. I'm curious to know whether this is meant to imply that Liddy had a drinking problem, and whether this could have had any bearing on the whole gorilla romantic partner situation. EEng

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

    User Stationmanagerskidrow removing information on Radio Skid Row page

    [edit]

    User:Stationmanagerskidrow is repeatedly removing information about a recent incident involving a Jewish DJ at their station. They say that it is incorrect information, even though it is sourced. The name also states clearly that this is a company account. Lastly, they have continued this behavior even after being warned on their talk page. Pyramids09 (talk) 03:07, 24 December 2024 (UTC)[reply]

    User is now editing using User:159.196.168.116 Pyramids09 (talk) 03:34, 24 December 2024 (UTC)[reply]
    This is a content dispute and the article is being actively edited by many different editors. However, no discussion about the disagreements has occurred on the article talk page which is where this discussion should be happening. Liz Read! Talk! 04:37, 24 December 2024 (UTC)[reply]

    That article probably should be speedied as an A7 for not containing any assertions of notability; which obscures that Stationmanagerskidrow appears to have been edit warring on it with an undisclosed COI, and presumably was WP:LOUTSOCKing as this IP, and if so violated 3RR as well. It's probably best for me not to take administrative action here tonight as I won't be around later/tomorrow to deal with any followups, but something should be done here beyond just saying "take it to the talk page." SWATJester Shoot Blues, Tell VileRat! 06:22, 24 December 2024 (UTC)[reply]

    The page was longer, but sourced (all but?) soley to the station's site and it's been trimmed down to what it is now. Given the repeated edit-warring by IPs I've semi-protected the page for two days for now. - The Bushranger One ping only 07:59, 24 December 2024 (UTC)[reply]
    WP:USERNAME and WP:COI message added here. I'm just about to make myself thoroughly WP:INVOLVED by seeing what I can do about the Radio Skid Row article. Shirt58 (talk) 🦘 09:11, 24 December 2024 (UTC)[reply]

    Insults

    [edit]

    I'd like to report an incident related to this discussion. A person under IP already accused me of being "obsessed". Now someone (possibly the same person) suggests that I may need psychiatric help. Please also see this comment. I guess we can always agree to disagree with other people, but this is going a bit too far. Thank you. Psychloppos (talk) 09:30, 24 December 2024 (UTC)[reply]

    Hello, Psychloppos. What action are you seeking to happen here? Liz Read! Talk! 09:42, 24 December 2024 (UTC)[reply]
    I have no idea which actions are warranted here. Maybe an admin could leave a message to this IP and this registered user and remind them that they should assume good faith ? It would also be nice to remind them about Wikipedia:Civility and Wikipedia:No personal attacks. Saying that I am "fuelled by an unhealthy obsession" or questioning my sanity do not seem to respect those guidelines. Psychloppos (talk) 09:52, 24 December 2024 (UTC)[reply]
    Normally this starts with warnings on the user's Talk page, but it seems you two have already hashed that out. So unless this account does it again, there's no further action to be taken. — The Hand That Feeds You:Bite 18:25, 25 December 2024 (UTC)[reply]
    FYI, following this, I have made this sockpuppet investigation request. Psychloppos (talk) 13:48, 26 December 2024 (UTC)[reply]
    Of note, Hazar Sam has now accused Psychloppos of engaging in defamatory edits, which smacks of a WP:LEGAL violation. — The Hand That Feeds You:Bite 18:09, 26 December 2024 (UTC)[reply]
    And their response to being warned about that was to flounce. - The Bushranger One ping only 23:46, 26 December 2024 (UTC)[reply]

    Request for Review of Neutrality and Repeated Actions

    [edit]

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


    Dear admin, I hope this message finds you well. I am writing to express my concern regarding Psycholoppos, who has repeatedly applied the neutrality dispute tag to content related to Randa Kassis. Despite previous clarifications, these actions suggest a potential bias, which could undermine the objectivity and integrity of the platform.

    I kindly request that you review this matter and take appropriate steps to ensure that all users adhere to neutrality standards. If possible, I would also appreciate guidance on how to address such situations constructively in the future.

    Thank you for your attention to this issue. Please feel free to reach out if further clarification is needed. Hazar HS (talk) 17:45, 24 December 2024 (UTC)[reply]

    @Hazar Sam, whether the NPOV tag is needed or not should first be discussed on the article's talk page. Also, see the large notice at the top of this page: you are required to notify the editor you are reporting. Schazjmd (talk) 17:53, 24 December 2024 (UTC)[reply]
    The editor is also called Psychloppos, not Psycholoppos. I have notified them for the OP. – 2804:F1...26:F77C (::/32) (talk) 17:59, 24 December 2024 (UTC)[reply]
    I wouldn't give a chatbot-written thread the time of day. HS, we have less tolerance for AI-written arguments than the American court system. —Jéské Couriano v^_^v threads critiques 18:05, 24 December 2024 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Nlkyair012 and LLM chatbots

    [edit]

    This editor has been constantly using AI chatbots to respond and write messages.[30][31][32][33] They are a single purpose account for glorifying the Kamaria Ahir caste using unreliable WP:RAJ era sources, I and several other experienced editors have taken time and effort to respond to their endless queries and WP:SEALIONING generated using ChatGPT. They have posted AI generated walls of text on multiple noticeboards such as WP:RSN [34] and WP:DRN [35] and including here [36], accusing me of vandalism.

    Despite my repeated requests [37][38] and even a final warning[39] to them (including a request by @ActivelyDisinterested:[40]) they are still continuing to do it.[41][42] Their messages are repeating the same argument again and again and are frankly just hallucinations that bring up fictitious guidelines or misrepresent the existing ones. Several editors have told them that Raj era sources are not reliable yet they continue to ask for more evidence on why that is the case based on AI generated claims of supposed academic value or neutrality. This is getting very disruptive and taking up valuable contributor time to respond to their endless AI responses which take a few seconds to generate. I have alerted them about WP:GSCASTE and WP:ARBIPA, I would appreciate it if someone could enforce a restriction on this user from at minimum caste area. - Ratnahastin (talk) 13:07, 24 December 2024 (UTC)[reply]

    Hello @Ratnahastin,
    To start with I should admit that I am sorry for all the inconvenience that I may have caused as a result of my actions. It was never my intention to take people’s time or skew the conversation in a certain way. I appreciate the core idea to contribute the thoughts to the Wiki and share it borne in mind the overall rules and policies of this program.
    I understand your fears about the AI utilities you have mentioned on your site. Even when I was using AI for the grammar check or, for instance, to elaborate on some point in the text, I saw to my mismanagement that over the process we probably confused the readers and repeated the same information and thoughts, which I would never wish to happen again. From now on I will ensure that in the future the input which I provide to wikipedia fits the Wikipedia standard and is more personal. I will also not write walls of text and will not make assertations that do not have substantiated evidence in sources.
    As for subjects that concern the Raj and the sources from this period and the discussions we have had it seems that I have gone too far in demanding clarification for the same thing. That being the case, with the understanding that the consensus will be acknowledged, I shall not be inclined to reopen this discussion unless new substantiated evidence is produced. I don’t want to prolong the conversation or bring any more stress.
    I will strive to learn from my experience to be more productive in my interactions going forward. If there are other limitations or additional rules to which I have to stick to, I will receive them with pleasure.
    In the same respect, let me specially apologize for the inconvenience and thank all of you for bearing with us. That was why I wanted to remind all of us that we can and should keep collectively improving Wikipedia as a resource. Nlkyair012 13:31, 24 December 2024 (UTC)[reply]
    This comment also has a typical LLM feel and contains meaningless statements such as "I understand your fears about the AI utilities you have mentioned on your site" and differs substantially from your usual (non-AI) writing style, although GPTzero said this is human input. - Ratnahastin (talk) 13:38, 24 December 2024 (UTC)[reply]
    It seems human in that it contains some composition and grammar errors that I don’t think an LLM would produce. Zanahary 13:56, 24 December 2024 (UTC)[reply]
    Thanks for the reply sir, I can't explain how frustrated I'm feeling from this morning which this user made me experience Nlkyair012 14:02, 24 December 2024 (UTC)[reply]
    The time when I messaged Vikram banafar I was casual not formal and second of all your saying doesn't prove anything "and differs substantially from your usual (non-AI) writing style" that's a straight up false accusation and utter nonsensical point and 3rd point being that GPTzero stated that this is a human input then that's an human input end of the question. Nlkyair012 14:01, 24 December 2024 (UTC)[reply]
    No it's really not the end of the story if GPTZero says "likely human". In fact I'd actively discourage people depending on tools like GPTZero in favour of their human senses which are better at detecting LLM outputs than yet another computer program. And, frankly, what you're hearing from people here is we'd rather your casual, human, flaws-and-all style of writing over ChatGPT output "formal" report templates. They are doing the opposite of what you're looking for and have become disruptive. Simonm223 (talk) 14:05, 24 December 2024 (UTC)[reply]
    Man you still wanna do this? @Zanahary also says this doesn't seems AI generated to him and he used his actual "Human senses" to lean that way Nlkyair012 14:10, 24 December 2024 (UTC)[reply]
    Admitting that you have used AI for writing your comments[43][44] and then saying that you have not used AI is not going to help your case. - Ratnahastin (talk) 14:36, 24 December 2024 (UTC)[reply]
    You know what I think this is getting to the WP:NOTHERE point. Having to tell somebody to have the basic respect of other editors to not subject them to text-walls of chatGPT garbage over and over again is a disruptive distraction from what we should all be doing. Simonm223 (talk) 14:38, 24 December 2024 (UTC)[reply]
    This ain't getting anywhere Nlkyair012 14:59, 24 December 2024 (UTC)[reply]
    I really don't understand the problem. Cuz I literally also said many where that yes I used AI but for expanding and grammar correction Nlkyair012 14:54, 24 December 2024 (UTC)[reply]
    If this combative approach is your "casual" style, perhaps your use of AI and its over the top politeness was an attempt to mask it. In any case, I think you are not here for building an encyclopaedia but for caste glorification given your obsession with a certain sub-caste. - Ratnahastin (talk) 14:33, 24 December 2024 (UTC)[reply]
    im not obsessed with a certain subcaste but am sure is obsessed with British Raj sources. Nlkyair012 14:56, 24 December 2024 (UTC)[reply]
    I don't think that's better. Shovel Shenanigans (talk) 15:44, 24 December 2024 (UTC)[reply]
    If we just temporarily put aside the AI-generated comments, can Nlkyair012 accept the view of experienced editors on Raj era sources and not push any viewpoint on a particulary caste? Because, to be honest, editors who have done this in the past usually end up indefinitely blocked. There is a low tolderance here for "caste warriors". Liz Read! Talk! 19:27, 24 December 2024 (UTC)[reply]

    Potential vandal trying to start edit war on the page for Frisch's.

    [edit]

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


    This user keeps using IP addresses in order to revert creditable information about who makes their tartar sauce. Please look into this user. IP Addresses used were 67.80.16.30, 66.117.211.82, and 216.24.107.180. — Preceding unsigned comment added by JrStudios The Wikipedian (talkcontribs) 15:17, 24 December 2024 (UTC)[reply]

    Courtesy link Frisch's. Knitsey (talk) 17:02, 24 December 2024 (UTC)[reply]
    This sounds a lot like the same edit warrer I dealt with on Redbox, down to the false accusations of vandalism, removal of sourced information, and apparent use of proxies (all the IPs geolocate to different places). I wouldn't be surprised if this is the same person. I've asked RFPP to intervene. wizzito | say hello! 21:05, 24 December 2024 (UTC)[reply]
    NVM, checked MaxMind for geolocation and they all are in the same general area. wizzito | say hello! 21:08, 24 December 2024 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    User:Nadeem asghar khan inaccurate edit summaries

    [edit]

    All but 2 of user's edit summaries are "Fixed Typo" when they are in fact partially updating statistical information on the page. Have left multiple messages/warnings on TP, with no response. Spike 'em (talk) 16:03, 24 December 2024 (UTC)[reply]

    Lil Dicky Semi-Protection

    [edit]

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


    Lil Dicky was semi-protected back in 2019. Now that five years have passed, could the semi-protection be lifted? 174.93.89.27 (talk) 16:25, 24 December 2024 (UTC)[reply]

    Ask at WP:RFPP EvergreenFir (talk) 16:28, 24 December 2024 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Disruptive behavior from IP

    [edit]

    For the past month, 24.206.65.142 (talk · contribs · WHOIS) has been attempting to add misleading information to Boeing 777, specifically trying to use the unofficial "777-200LRF" designation beyond first mention in the relevant section and passing it off as official ([45], [46], [47], [48], [49], [50], [51], [52], [53], [54], [55]). Their behavior died down for a few weeks, but restarted several days ago ([56], [57]), including baseless claims that Fnlayson is "okay with it". They have been asked numerous times on their talk page to either stop or provide evidence of official use of the designation, but they have failed to do so and have continued their disruption. - ZLEA T\C 19:51, 24 December 2024 (UTC)[reply]

    I forgot to mention that this user has used at least two other IPs; 24.206.75.140 (talk · contribs · WHOIS) and 24.206.65.150 (talk · contribs · WHOIS). 24.206.65.142 is the most recent to cause disruption. - ZLEA T\C 20:10, 24 December 2024 (UTC)[reply]

    "777-200LRF" is not misleading, some cargo airlines do use that designation. Today I reverted to a previous version that User:Fnlayson was okay with [58][59]. I feel that User:ZLEA is going overboard with charges of misinformation and disruptive editing. 24.206.65.142 (talk) 19:59, 24 December 2024 (UTC)[reply]
    It is misleading to remove any mentions of it being unofficial. Boeing has never made a "777-200LRF", no aftermarket conversion has ever been offered under that name, nor has the FAA or any other regulatory agency ever certified such an aircraft. To pass such a designation off as official is by definition misleading and misinformation. Likewise, to continuously do so after you have been told to stop by multiple people and falsely claiming that others support your arguments is by definition disruptive. - ZLEA T\C 20:06, 24 December 2024 (UTC)[reply]
    Of note is the fact that this is not the first time the IP has claimed to have Fnlayson's support. They have been told before by Fnlayson not to assume support without a specific statement, yet it seems they've also ignored that. - ZLEA T\C 20:23, 24 December 2024 (UTC)[reply]
    Its not misinformation as here are the sources which use "777-200LRF"[60][61], including GE Capital Aviation [62](the engine supplier for most Boeing 777) and Leeham News [63] (to avoid confusion with the upcoming 777-8F). 24.206.65.142 (talk) 21:06, 24 December 2024 (UTC)[reply]
    I have asked you for sources from either Boeing or the FAA, yet you still either refuse to do so or (more likely) cannot because they don't exist. Only Boeing and the FAA can designate factory-built Boeing aircraft. Airlines and misinformed news websites have no authority to do so, and any alternative names they use are purely unofficial and should not have anything more than a single brief mention in the appropriate article section. Your failure or refusal to get that after numerous people have told you is disruptive. - ZLEA T\C 22:14, 24 December 2024 (UTC)[reply]
    None of those are reliable sources suitable for sustaining the edit you want to make. #1 would only support that airline claiming to have that kind of plane. #2 is a model manufacturer, and #3 is a blog. — The Hand That Feeds You:Bite 18:37, 25 December 2024 (UTC)[reply]
    Relevant range is 24.206.64.0/20 (block range · block log (global) · WHOIS (partial)), in case somebody needs it. wizzito | say hello! 21:02, 24 December 2024 (UTC)[reply]

    Rude and unfestive language in my talk page

    [edit]

    My esteemed editor collegue Marcus Markup just left this rude message on my talk page, on Christmas Day no less. Not really in the spirit of the season, I'd say. Considering that he was sagaciously advising me on the importance of tact and etiquette in the very same thread, he should be held to the same standard. Vector legacy (2010) (talk) 17:54, 25 December 2024 (UTC)[reply]

    Vector legacy (2010) and Marcus Markup, you both should stop that childish behavior and disengage from one another. Cullen328 (talk) 18:10, 25 December 2024 (UTC)[reply]
    Uh, “suck a bag of dicks” seems a cut above anything childish in VL2010’s conduct. Zanahary 08:05, 26 December 2024 (UTC)[reply]
    True, and given a warning accordingly - but Vector legacy's user page is also...interesting. - The Bushranger One ping only 09:31, 26 December 2024 (UTC)[reply]
    Vector Legacy's comments in that discussion are clearly poking the bear, both should be warned. On top of that, Vector has broken the 3RR rule with these 4 reverts: [64], [65], [66], [67]. They acknowledge in the edit summary of the 4th that they know of the 3RR rule and that their first edit was a revert. The last revert in particular, effectively saying "haha, you can't make any more reverts because you've already made 3" when the user themselves has made 4, is really not smart nor constructive/collaborative. Valenciano (talk) 10:12, 26 December 2024 (UTC)[reply]
    I'm normally a stickler for civility, but frankly in this case I actually think Vector legacy (2010) is the bigger problem. Marcus's Markup comment is something they can hopefully easily learn not to do and could have been an extremely unfortunate one-off in a bad situation. By comparison it seems that Vector legacy (2010) is treating editing here as a game where they win edit wars rather than collaborate constructively. I have little hope this is an attitude easily changed so a WP:NOTHERE block might be justified soon. Nil Einne (talk) Nil Einne (talk) 12:25, 26 December 2024 (UTC)[reply]
    (edit conflict) Yes. The idea of WP:3RR is that the protagonists should discuss things on the article talk page before that point is reached, not to use it as a stick to beat other editors with. I note that Vector legacy (2010)'s user page admits to a lot of edit warring, and it discloses a WP:BATTLEGROUND attitude. Phil Bridger (talk) 12:31, 26 December 2024 (UTC)[reply]
    I think that it is safe to say that both these editors are skating on thin ice. Cullen328 (talk) 17:02, 26 December 2024 (UTC)[reply]
    To that point, Vector legacy (2010)'s userpage consists of a tally of "EDIT WARS WON". I doubt this is serious, but the optics of it, combined with the above 3RR vio + bragging about the other party being on the line, is not good. ―"Ghost of Dan Gurney" (hihi) 18:01, 26 December 2024 (UTC)[reply]
    I've nominated that userpage at MFD as it's purely disruptive. - The Bushranger One ping only 23:42, 26 December 2024 (UTC)[reply]

    User:Ryancasey93

    [edit]

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


    Over at Talk:Anti-Barney humor, a user by the name of Ryancasey93 requested that their YouTube channel be cited in a passage about them ([68]) that was added by TheLennyGriffinFan1994 ([69]). The talk page discussion was removed by AntiDionysius as being promotional in nature. Ryancasey93 then decided to make an edit request to cite their channel, which was declined by LizardJr8, who then proceeded to remove the passage as being unsourced.

    I then brought up concerns with WP:GNG and WP:COI with Ryancasey93, who then proceeded to respond in a needlessly confrontational and hostile manner, creating a chain of replies and pinging me and LizardJr8. Ryancasey93 then proceeded to go off on a tangent where they said we were "very rude and belittling" to them, told us they sent an email complaint against us, called us "the most cynical, dismissive, greedy, narcissistic, and ungrateful people I ever met in my entire life", accused us of discriminating against Autistic people (I am autistic myself, for the record), and called us "assholes".

    Simply put, I feel as if Ryancasey93 does not have the emotional stability required to contribute to Wikipedia, having violated WP:NPA, WP:ASPERSIONS, and WP:PROMOTION, and a block may be needed. The Grand Delusion(Send a message) 19:47, 25 December 2024 (UTC)[reply]

    I just logged on while digesting turkey, and was alerted of the pings and this report. I don't really appreciate the messages from the user (I'm on the spectrum too, FWIW) but I think @Tamzin gave a good response, highlighting the need for secondary reliable sources. I should have done that better when I removed the unsourced information. I would like to see if there is any further activity from the user before getting into a block discussion. LizardJr8 (talk) 21:10, 25 December 2024 (UTC)[reply]
    Looks like they've been blocked for 31 hours by Cullen328. The Grand Delusion(Send a message) 23:15, 25 December 2024 (UTC)[reply]
    Yes, that last comment was unacceptable in several ways. Cullen328 (talk) 00:57, 26 December 2024 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    User:24.187.28.171

    [edit]

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


    IP has been blocked before for previous infractions. Now, they continue to perform persistent disruptive edits contradicting the Manual of Style, either by deliberately introducing contradictions or undoing edits that resolve the issue. The user has also violated WP:DOB at Huntley (singer), though that remains unresolved for some reason. The IP has done all of this despite a backlog of warnings dating back to 2023. — Preceding unsigned comment added by EdrianJustine (talkcontribs) 22:48, 25 December 2024 (UTC)[reply]

    @EdrianJustine: could you please provide specific diffs? voorts (talk/contributions) 23:23, 25 December 2024 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Incivility, aspersions, WP:NOTHERE from Cokeandbread

    [edit]

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


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

    Cokeandbread is a few-month-old account whose area of greatest focus has been creating (and defending) two promotional pages for social media influencer-types: Jimmy Rex and Hammy TV. Cokeandbread has refused (diff) to answer good-faith questions (diff, diff) about whether they are operating as a paid editor (responding to one of them with Don't threaten me) and posted a copyvio to Commons (diff). Despite warnings (diff), the editor has been engaging in bludgeoning/disruptive behavior at the Jimmy Rex AfD (bludgeoning and attempting to !vote multiple times (diff, ) and has made uncivil remarks to other editors (diff, diff, diff), while demanding respect in the other direction. Recently, Cokeandbread posted the following on their user page: The way some people in AfD discussions move, you just know some people commenting are under demonic influence. Stay away from me and mine. (diff). Despite another warning (diff), which Cokeandbread removed when blanking their talk page (diff), this aspersion is still up. If we're at the point where an editor is accusing other editors of being demonically influenced, I think we're well into WP:NOTHERE territory. Given the lack of response to non-admin warnings and requests, I'd ask for admin intervention here. Dclemens1971 (talk) 23:34, 25 December 2024 (UTC)[reply]

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

    Disruptive editing by Dngmin

    [edit]

    The main issue with this editor at the moment is disruptive editing based on continuous abuse of Byeon Woo-seok. Issues began when this editor 1500+ bytes of sourced material. He did it again and again and again for past few days, thus creating a lot of work for others to undo.

    Since october the user received warning for blocked from editing. Please help to block the user. Puchicatos (talk) 04:19, 26 December 2024 (UTC)[reply]

    I'm assuming the mention of diffs and @PhilKnight: was a cut and paste failure? [70] - The Bushranger One ping only 07:00, 26 December 2024 (UTC)[reply]
    Yes it is. Puchicatos (talk) 16:14, 26 December 2024 (UTC)[reply]

    New user creating a lot of new pages

    [edit]

    I am not confident I understand what 4Gramtops is up to. They created 50+ new pages in their userspace. I have not a clue what they are meant to accomplish outside of testing. It just seems strange for a user with so few edits. There was no forthcoming response to my talk page messages trying to get an explanation (which I know they've seen since they used my heading as a new subpage title)

    On a related note, they have also created this epilepsy nightmare. It's possible I'm just overthinking a simple troll here.MJLTalk 07:35, 26 December 2024 (UTC)[reply]

    Gaming the system for permissions? - The Bushranger One ping only 09:28, 26 December 2024 (UTC)[reply]
    Given Special:PrefixIndex/User:4Gramtops/, I find it likeliest they're trying to learn Lua by using their userspace as a testing environment. Harmless but technically U5. Folly Mox (talk) 11:54, 26 December 2024 (UTC)[reply]
    Might not even be U5 if the purpose of trying to learn Lua is to develop the expertise to work on Lua modules for Wikipedia. —David Eppstein (talk) 19:39, 26 December 2024 (UTC)[reply]
    I already suggested they use Test 2 Wikipedia for that purpose. It'd lead to a lot less clutter. I do find that either way they should probably say what they're trying to do. No one can help them if they don't communicate. –MJLTalk 20:55, 26 December 2024 (UTC)[reply]

    Undoing my blocks due to collateral damage

    [edit]

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


    Hello, could an admin undo these blocks that I made? Blocks like these seem to have caused way more collateral damage than they're worth, per this message on an IP talk page (about a block I undid in October when I still had adminship) and this message on my talk page. Thanks! Graham87 (talk) 10:31, 26 December 2024 (UTC)[reply]

    Ah, I've just done some checking, and it seems like, as ever, there's a template with unblock links. So here goes::

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

    Persistent unsourced changes by IP

    [edit]

    2001:999:500:8D52:753A:9BD7:9D61:823B (talk · contribs · (/64) · deleted contribs · filter log · WHOIS · RBLs · http · block user · block log)

    [71], [72], [73], [74], [75], etc.

    Note that another IP in the same /64 range (2001:999:500:8D52:8065:5651:5389:18E (talk · contribs · (/64) · deleted contribs · filter log · WHOIS · RBLs · http · block user · block log)) was blocked for the same reasons less than a week ago. BilletsMauves€500 19:16, 26 December 2024 (UTC)[reply]

    197-Countryballs-World

    [edit]

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


    So far, 197-Countryballs-World (talk · contribs) has made categories, started drafts, and attempted edits to articles, all of which make it clear they presently view Wikipedia a bit like their personal playground where they can build some sort of confused, redundant atlas. They have not responded whatsoever to talk messages, their categories at CfD, or their unsourced additions to live articles being reverted. If they can hear us, it seems they need to be gotten a hold of if they want to be a positive contributor—but it seems likely that they can't hear us. Remsense ‥  19:19, 26 December 2024 (UTC)[reply]

    (NAC) Based on their username, I can reasonably confer that their edits likely pertain to the Countryball Fandom. Just a note, as I know we've historically had issues with Fandom editors crossing into Wikipedia. Feel free to remove if this message is innapropriate for ANI. :) EF5 20:23, 26 December 2024 (UTC)[reply]
    Aye. Mostly, they seem young. Remsense ‥  20:27, 26 December 2024 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Disruptive editing and ongoing vandalism by User:Caabdirisaq1

    [edit]

    I have warned @Caabdirisaq1 multiple times in his talk page with no avail. He consistently vandalises articles by adding images unrelated to them such as Ahmed Girri Bin Hussein Al Somali , Matan ibn Uthman Al Somali and Garad Hirabu Goita Tedros Al Somali . I have been trying to revert the changes made and explained that they were of orientalist paintings of Arab bedouins. Replayerr (talk) 21:28, 26 December 2024 (UTC)[reply]

    These edits adding these images may not rise to the level of vandalism but they seem pretty disruptive to me. Adolph Schreyer was a 19th century painter well known for portraying horses and horsemen, and he traveled to to Turkey, Egypt, Syria, and what is now Algeria. He also painted horses and horsemen in a European context. I know nothing about his work other than what the Wikipedia article says or the file pages for the various public domain images on Commons say. If the image file says something like "two Arab horsemen" and the painting was created 150 years ago, then adding that image to the biography of someone who lived 500 years ago with zero evidence connecting that specific painting to that specific individual 350 years earlier is disruptive and unacceptable. So, maybe I am missing something and maybe there is a Catalogue raisonné for this artist that identifies these paintings as representing figures of the Adal Sultanate. But lacking that sort of solid evidence (which should be reflected in the Commons file pages), then adding these images is a violation of the No original research policy, in my opinion. Cullen328 (talk) 04:09, 27 December 2024 (UTC)[reply]

    Please revoke TPA from MarkDiBelloBiographer

    [edit]

    Misuse of talk page after being blocked. Still promotion the same person. -Lemonaka 03:40, 27 December 2024 (UTC)[reply]

    What exactly is the problem? She said that she wants to create a Wikipedia page for her friend as a Christmas gift. She got blocked, and now she's complaining that she doesn't understand how Wikipedia works. If you don't want to explain how Wikipedia works, why not just stop looking at the page? NinjaRobotPirate (talk) 03:52, 27 December 2024 (UTC)[reply]

    I offered to write about him and did for 3 long days as a gift and you guys disbelieved everything, none of which I put was false! It's all on the web, in papers, or other media, or pictures and on his websites

    Anyways Mark and I were both fans of and he thinks it's a valuable resource for people I'm just sorry you're so negative and inaccurate about me and him

    I believe this is not the good try after getting block. -Lemonaka 03:58, 27 December 2024 (UTC)[reply]

    User:KairosJames

    [edit]

    This user's additions of unsourced content to biographical articles (not any living persons that I've seen, or I'd have gone to BLP) have been reverted many times, with several warnings. They've made no response on any talk page. Assuming they actually are getting these facts from some kind of source, I would think they could be a constructive editor, but they at the very least need to become aware of our citing standards in my opinion. -- Fyrael (talk) 04:36, 27 December 2024 (UTC)[reply]