Wikipedia:Administrators' noticeboard

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by El C (talk | contribs) at 18:22, 29 September 2022 (→‎Standard offer - JGabbard: ugh, missed one :(). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

    Welcome – post issues of interest to administrators.
    Shortcuts

    When you start a discussion about an editor, you must leave a notice on their talk page. Pinging is not enough.

    You may use {{subst:AN-notice}} ~~~~ to do so.

    Sections inactive for over three days are archived by Lowercase sigmabot III.(archives, search)

    Open tasks

    XFD backlog
    V Feb Mar Apr May Total
    CfD 0 0 18 17 35
    TfD 0 0 0 5 5
    MfD 0 0 0 3 3
    FfD 0 0 0 0 0
    RfD 0 0 10 57 67
    AfD 0 0 0 15 15

    Pages recently put under extended-confirmed protection

    Report
    Pages recently put under extended confirmed protection (21 out of 7765 total) (Purge)
    Page Protected Expiry Type Summary Admin
    Viraj Mithani 2024-05-21 03:01 indefinite create Repeatedly recreated JPxG
    Talk:Sexual and gender-based violence in the 2023 Hamas-led attack on Israel 2024-05-21 01:18 2024-05-28 01:18 edit,move Arbitration enforcement ScottishFinnishRadish
    Draft:Roopsha Dasguupta 2024-05-20 21:26 2029-05-20 21:26 create Repeatedly recreated Yamla
    Gaza floating pier 2024-05-20 17:36 indefinite edit,move Arbitration enforcement ScottishFinnishRadish
    Science Bee 2024-05-20 15:26 2027-05-20 15:26 create Repeatedly recreated Rosguill
    Wikipedia:Golden Diamond Timeless Watch 2024-05-20 06:54 2024-05-23 06:54 create Repeatedly recreated Liz
    Screams Before Silence 2024-05-20 04:56 indefinite edit,move Contentious topic restriction: per RFPP and ARBPIA Daniel Case
    Tyson Fury vs Oleksandr Usyk 2024-05-20 03:49 indefinite edit,move Persistent vandalism: per RFPP Daniel Case
    Atom Eve 2024-05-20 02:53 2024-08-20 02:53 edit,move Persistent sock puppetry NinjaRobotPirate
    Ebrahim Raisi 2024-05-19 22:02 indefinite edit,move Arbitration enforcement: WP:ARBIRP; upgrade to WP:ECP, 2024 Varzaqan helicopter crash-related; aiming for the short term (remind me) El C
    2024 Varzaqan helicopter crash 2024-05-19 21:15 2024-06-19 21:15 edit Contentious topic restriction Ymblanter
    Koli rebellion and piracy 2024-05-19 21:08 indefinite edit,move Persistent sock puppetry Spicy
    Khirbet Zanuta 2024-05-19 12:15 indefinite edit,move Contentious topic restriction: WP:A/I/PIA ToBeFree
    Poppay Ki Wedding 2024-05-18 20:42 2025-05-18 20:42 create Repeatedly recreated: request at WP:RFPP Ymblanter
    Joseph Sam Williams 2024-05-18 11:59 2024-05-22 11:59 move Persistent sock puppetry; requested at WP:RfPP Robertsky
    2024 University of Amsterdam pro-Palestinian campus occupation 2024-05-18 06:32 indefinite edit,move Contentious topic restriction: per RFPP and ARBPIA Daniel Case
    Edcel Greco Lagman 2024-05-18 03:31 2024-07-18 03:31 edit,move Persistent disruptive editing: Removal of sourced content, per a complaint at WP:ANI EdJohnston
    User:DatBot/Filter reporter/Run 2024-05-17 21:34 indefinite edit,move Persistent vandalism: request at WP:RFPP Ymblanter
    User talk:BabcocksRhodeIsland1700s 2024-05-17 16:17 2024-05-24 16:17 move Don't move your User talk page except by a Renamer Liz
    User:MayNard Keith Batiste, Jr 2024-05-17 15:29 2024-05-31 15:29 create Repeatedly recreated Liz
    Komail Anam 2024-05-17 13:36 2024-11-17 13:36 edit,move Edit warring / content dispute, per WP:Articles_for_deletion/Komail_Anam OwenX

    Block evader

    Indeffed. (non-admin closure) dudhhr talk contribs (he/they) 19:33, 25 September 2022 (UTC)[reply]

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


    Special:Contributions/Pickle troll 188.226.73.30 (talk) 07:45, 24 September 2022 (UTC)[reply]

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

    a user delete important source from University of Munich in order to delete the article as without sources.

    Article improperly moved into mainspace deleted, user needs to work on draft. We can do nothing here about a user from another project if they are not editing here. Black Kite (talk) 23:24, 24 September 2022 (UTC)[reply]

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

    I would like your attention please.

    The user at at the music article josef vitzthum deletes constantly a source from a German university in order to delete the article. At her profile, it clearly the political or nationalistic interest, against European free thought and against of record important music historic events.

    please pay attention on that source. Of course many things are unknown yet, but that's why there is encyclopedia. To bring to the people free information as a title, composer, historical info about the piece and performance. It is not possible, from a user to delete a source about composer and then to indicate as not enough academic.

    The principal source is the manuscript from 19th century, and secondary sources are the academic articles with DOI.

    Thank you for your time, MaxLux8 (talk) 22:34, 24 September 2022 (UTC)[reply]

    You have linked a user for the Greek-language Wikipedia. This is an English-language administrators' noticeboard, and has no authority there. AndyTheGrump (talk) 22:42, 24 September 2022 (UTC)[reply]
    Although the editor did create a draft here (Draft:Adagio e Rondo - Josef Vitzthum) which was rejected three times, and then created it in mainspace anyway (Adagio e Rondo (Josef Vitzthum: 1815-1884) ‎). Since Vizthum does not have an article here, I suspect it probably fails WP:CSD#A9 as well as any other notability guidelines. Can anyone see any reason why I shouldn't just delete it? Black Kite (talk) 22:48, 24 September 2022 (UTC)[reply]
    No obvious reason not to delete it that I can see. The new article has the same issues as the draft, and copying it to mainspace didn't make them go away. MaxLux8 needs to work on the draft, and convince people that the subject meets notability criteria. With better sourcing, and evidence that anyone beyond the rediscoverer and performer of this long-lost oboe piece consider it 'crucial'. Or even worthy of comment. AndyTheGrump (talk) 23:16, 24 September 2022 (UTC)[reply]
    I've deleted it - and the four(!) redirects to it. Black Kite (talk) 23:24, 24 September 2022 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Unban request from CheatCodes4ever

    CheatCodes4ever (talk · contribs · deleted contribs · page moves · block user · block log)

    Was originally blocked as WP:NOTHERE and WP:CIR per this ANI discussion, and has been blocked for socking, and lost talk page access more than once. A repeat checkuser will be useful. (Yamla found no socking in June.) Has requested unblocking at UTRS appeal #62686, and I have restored the ability to edit here for the unban request. User will be able to respond directly to concerns here. I have copied the request over from UTRS below.

    Alright, I am trying my block appeal again. Note that due to a small character maximum in this text box, I am going to have to ask that administrators reviewing this and anyone else reading this read my previous unblock requests to hear other parts of the story. I would rewrite the whole thing again but I cannot, so I will do this instead.

    Basically, I got blocked from Wikipedia for not being here to build an encyclopedia and abuse of multiple accounts. As I mentioned, abuse of multiple accounts is already covered in previous requests, though I will get onto the NOTHERE reasoning. I was community banned due to my issues with adding sources to pages and creating articles for non-notable subjects. Users had also given me advice before about this, however I did not take the advice very well, which led users to believe I was not here to build an encyclopedia. As for the addition of content without sources, I often forgot to add sources, which was why I often forgot to add them.

    Also, for the record regarding sources that I do use but should not, I do now know that I should not use stores as sources as they are considered original research. As for creating articles on non-notable topics, I now understand the general notability guideline (WP:GNG), as the rule is that a topic is presumed to be notable if it has recieved significant coverage from reliable sources that are independent of the subject:

    1. "Presumed" means that significant coverage in reliable sources, creates an assumption, not a guarantee, that a subject merits its own article. This means that meeting this policy does not mean it definitely deserves its own article, but that it is assumed that it does.
    2. "Significant coverage" addresses the topic directly and in detail, so that no original research is needed to extract the content. This means that the topic is covered significantly and is not just mentioned trivially (ex. a long paragraph about something is signficant coverage, but solely mentioning a topic is not).
    3. "Reliable" means that the sources need editorial integrity to allow verifiable evaluation of notability, per the reliable source guideline. This means that sources must have fact-checking by editors and must not be self-published.
    4. "Sources" should be secondary sources, as those provide the most objective evidence of notability. This means that sources are needed to make something notable, and these sources should be secondary sources.
    5. "Independent of the subject" excludes works published by the article's subject or someone affiliated with it. This means that things like advertisements, announcements by the subject or someone affiliated, or anything else that is made by someone who is affiliated with the subject.
    Also, I will say for the record, I no longer believe that kappaphobia is a notable topic for Wikipedia, as the source I used was anonymous and was also not reliable for medical information. As for not listening to advice, I will say two things regarding that: 1. Until late 2019, I did not read my messages on my talk page. Although I did see some of them through notifications, most of them I ignored, because I did not use talk back then. 2. When I did eventually start reading my talk page messages, although I did read the advice, I admittingly never really took it very seriously. I did read one policy when it was shown to me, though that's about it. Also, as for not using my talk page to appeal my block, I apologise for doing that, but I was asking questions that I thought I might have needed to know before I could appeal. Anyway, in conclusion, I would like to be unblocked from Wikipedia.

    carried from utrs. -- Deepfriedokra (talk) 23:05, 24 September 2022 (UTC)[reply]

    I still see no evidence of block evasion recently, based on checkuser data. --Yamla (talk) 13:26, 25 September 2022 (UTC)[reply]
    I thank you. -- Deepfriedokra (talk) 14:50, 25 September 2022 (UTC)[reply]
    Well, I suppose I'll start this off, since it's been three days. @CheatCodes4ever: While your ban appeal, to me, seems to cover all the main points to be unbanned (and indicates to me that you have read the guidelines you admitted you previously did not), I'm curious what your plans are should it happen. What sort of topics do you want to contribute to should you be unblocked? FrederalBacon (talk) 22:55, 27 September 2022 (UTC)[reply]
    I'm not really sure what topics to which I'll contribute, I'll probably contribute to all kinds, but it will probably mainly be music, film, television, and maybe even games. As I said though, I'll probably end up contributing to all kinds of topics. CheatCodes4ever (talk) 20:50, 28 September 2022 (UTC)[reply]

    AfD shrunken text fix requested

    Unclosed small tag was closed. — xaosflux Talk 16:01, 25 September 2022 (UTC)[reply]

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

    On Wikipedia:Articles for deletion/Log/2022 September 24, many entries at the bottom of the page are in small text. Can this be fixed? — Ceso femmuin mbolgaig mbung, mellohi! (投稿) 15:26, 25 September 2022 (UTC)[reply]

    Done. DanCherek (talk) 15:31, 25 September 2022 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Staxringold restoration of permissions

    The Wikimedia Foundation has determined that Staxringold (talk · contribs) is back in control of his account. The Arbitration Committee has corresponded with Staxringold and, based on all available information, is assured that he will follow appropriate personal security practices in the future. The Committee therefore restores his administrative access.

    The Arbitration Committee is of the view that additional clarity about the Committee's return-of-adminship practices relating to account security is necessary. The Committee therefore invites interested community members to comment on relevant motion.

    Support: Barkeep49, CaptainEek, Enterprisey, L235, Maxim, Primefac, Worm That Turned, Wugapodes

    Oppose: Cabayi, Donald Albury, Izno

    For the Arbitration Committee, Maxim(talk) 17:40, 26 September 2022 (UTC)[reply]

    Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard § Staxringold restoration of permissions

    Checkuser needed

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

    Would someone with access to the checkuser tool be willing to email me? I filed this a while back but while disruption is ongoing, it hasn't moved forward. An admin moved it out of the Checkuser Requests, with instructions to contact someone through email if I want it run. EnPassant♟♙ (talk) 21:13, 26 September 2022 (UTC)[reply]

    Checkusers will not publicly disclose the connection between a user and an IP address per the privacy policy. We will also not disclose it to you via email, since you have not signed the relevant NDAs. Furthermore, I don't see any checkuser likely running that check since it would likely fall afoul of the checkuser policy. Cheers. Reaper Eternal (talk) 21:19, 26 September 2022 (UTC)[reply]
    Did you read the CU's comment at the SPI where I was specifically told to email a CU privately? I don't want anything disclosed to me, I wanted to provide evidence so someone can do something about ongoing disruption. EnPassant♟♙ (talk) 00:34, 27 September 2022 (UTC)[reply]
    Why are you bringing this here? If you haven't yet e-mailed a CheckUser, then do so.--Bbb23 (talk) 00:38, 27 September 2022 (UTC)[reply]
    I don't know any checkusers... which is why I asked for one of them to email me. EnPassant♟♙ (talk) 03:25, 27 September 2022 (UTC)[reply]
    I've lost interest in trying to help resolve this situation at this point, so I'll just close the discussion. EnPassant♟♙ (talk) 03:27, 27 September 2022 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.
    • @EnPassant: You can find a list of checkusers at WP:CONTACTCU. Sometimes when you're at a loss of what to do when it comes to Wikipedia, searching by adding WP: to what you want to find out (e.g. WP:CHECKUSER) often leads you to a page containing such information. -- Marchjuly (talk) 03:41, 27 September 2022 (UTC)[reply]

    User:Ford489 db-g7 deletions

    About a year ago, User:Ford489 was indefblocked for sockpuppetry. On the way out, he tagged 37 articles he had written for speedy deletion as {{db-g7}}. Looking at the articles themselves, they seem fine to me, and I would be inclined to undelete these. Is there any reason not to? BD2412 T 00:09, 27 September 2022 (UTC)[reply]

    • On further inspection, some (but not all) of these were nominated for deletion as being non-notable; others are clearly notable (a couple of regional governors, for example). The speedy tagging circumvented deletion discussions that were occurring. BD2412 T 00:18, 27 September 2022 (UTC)[reply]
    • I was the one who filed the sockpuppetry case at the time, and boy was Ford489 prolific after their first sock ban in 2015. They were dead-set on making their entire lineage represented on en-wiki, and went fairly undercover for six years. After I filed at SPI in late 2021 (see Wikipedia:Sockpuppet_investigations/2636z/Archive), I went through a series of G5s since their article creations were made in circumvention of their ban, and excluded from the speedy deletion process all articles that could have qualified for WP:NPOL at the time. However, worth noting that 95% of the sources in the articles are primary, passing mentions, or no mentions at all of the subject in question. So if one chooses to restore the 37 articles (or any of the G5'd articles), I'd caution to take a deep look at the sources. Pilaz (talk) 00:39, 27 September 2022 (UTC)[reply]

    Circumcision

    Appealing to the community's collective memory: who was the editor who got into hot water for their editing on articles dealing with circumcision? Beyond My Ken (talk) 01:36, 27 September 2022 (UTC)[reply]

    Are you thinking of Stix1776? I handed down an indefinite topic ban for edits to circumcision, partly based on oversighted material. Why do you ask? The Blade of the Northern Lights (話して下さい) 02:18, 27 September 2022 (UTC)[reply]
    ? Wikipedia:Administrators' noticeboard/IncidentArchive826#Hans Adler and Circumcision ? Bon courage might know who you're thinking of. SandyGeorgia (Talk) 02:28, 27 September 2022 (UTC)[reply]
    Circumcision? I've heard of a WikiGnome but never a WikiMohel! On a serious note are you perhaps thinking about User:HRS395 or their sock Sugarcube73? Horse Eye's Back (talk) 02:43, 27 September 2022 (UTC)[reply]
    Thanks for the suggestions. I think it was this editor I was thinking of. Beyond My Ken (talk) 05:13, 27 September 2022 (UTC)[reply]
    Now that's a deep cut. See what I did there? BD2412 T 05:39, 27 September 2022 (UTC)[reply]

    Standard offer - JGabbard

    There is a consensus against accepting this appeal signed, Rosguill talk 18:18, 29 September 2022 (UTC)[reply]

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

    JGabbard (talk · contribs)

    Wikipedia:Administrators' noticeboard/IncidentArchive1096#JGabbard spreading white genocide conspiracy theory on South African farm attacks article

    JGabbard was indefinitely blocked by Star Mississippi back in April for highly offensive remarks on a talk page, which were considered excessively disruptive and worthy of a block after review at ANI. He has recently filed a request apologising for his conduct and realising it was completely inappropriate, and a look back through his history brings back plenty of constructive and good faith edits to suggest they could be a net positive for the project. Although they didn't explicitly cite it, I think this is a reasonable application of the Standard offer; it's not quite six months since the block, but close enough to see if there is a community consensus to unblock. Furthermore, it might be appropriate to add a South Africa or politics-related topic ban of some sort as a condition of unblocking - not sure exactly what, though. Your thoughts, please. Ritchie333 (talk) (cont) 16:38, 27 September 2022 (UTC)[reply]

    Thanks @Ritchie333. The name didn't ring any bells and it looks as if I blocked as a result of Wikipedia:Administrators' noticeboard/IncidentArchive1096#JGabbard spreading white genocide conspiracy theory on South African farm attacks article. A scan of their contributions such as this make me think if unblocked, there would at least need to be a topic ban from South Africa since they do not appear able to edit neutrally in the area. Courtesy headsup to @Barkeep49 as they enacted a topic ban per Wikipedia:Administrators'_noticeboard/IncidentArchive1036#Anti-vax_campaign. At the moment I don't have a chance to take a deep dive so will AGF on Ritchie's assessment of a net positive and not take a position on the unblock. Happy to roll with any consensus that develops here. Star Mississippi 16:48, 27 September 2022 (UTC)[reply]
    ETA, oppose I still haven't had the chance to look through their edits, but the cases made here are more than compelling. While JGabbard appears able to edit productively in music areas, editing is a privilege, not a right. I'm sure there are others who can work in music without the baggage and noticeboard time sinks that come with his editing since there's no technical way to ensure they only edit in music areas. Star Mississippi 13:14, 29 September 2022 (UTC)[reply]
    • Oppose Isn't a net positive racist an oxymoron? I don't think anyone who holds those beliefs and thinks it's appropriate to espouse those racist views on wiki should be allowed to edit here, full stop. I realize this is a hardline stance, but I care more about editors who are exposed this type of nonsense then the person who holds those racist tropesValeince (talk) 16:52, 27 September 2022 (UTC)[reply]
    • No. I guess I could elaborate further if anyone just can't figure out why, but otherwise this unblock request is just a time sink for all the collaborative, fact-based, non-racist editors out there. I will assume Ritchie's "net positive" comment was just poor wording. --Floquenbeam (talk) 17:14, 27 September 2022 (UTC)[reply]
      I only did a shallow dive of edits, and noticed they'd been around for a while and edited some music articles, hence they could be a net positive, but if other editors have had time to investigate further and found even more problems, obviously not. Ritchie333 (talk) (cont) 21:27, 27 September 2022 (UTC)[reply]
    • Oppose per WP:NONAZIS. NightHeron (talk) 17:55, 27 September 2022 (UTC)[reply]
    • Support, but only if it's accompanied by a strict topic ban from anything relating to race. —VersaceSpace 🌃 18:02, 27 September 2022 (UTC)[reply]
    On second thought, I oppose. —VersaceSpace 🌃 18:33, 27 September 2022 (UTC)[reply]
    • Question Assuming we let them back with topic bans related to the following topics: vaccination, conspiracy theorists, COVID-19, race, South Africa, and politics, all broadly construed - what areas would they want to edit in? I do see that the majority of their constructive edits are to music related areas. Is there anything else they would want to edit? Moreover, a musician's race can provide important context to their music. Would the community have a problem with them discussing such topics in relevant articles? ~ ONUnicorn(Talk|Contribs)problem solving 18:12, 27 September 2022 (UTC)[reply]
    • Comment I was about to post the following but ec'd with the above post. It's along the same lines: I'm not sure a S.Africa/race TBAN covers it. Looking through his editing before his indef, he seems to have a very substantial track record on music. That appears to be his main interest. As far as I can tell that doesn't appear to be problematic and seems to have been very worthwhile. He seems to have a secondary interest in radical evangelical denominations. That looked ok'ish, although having a tendency to write as though he was composing a spiritual meditation, but I did notice the odd anti-Catholic tirade as here. One might couple that with his user page citing Ian Paisley as a hero. As well as the South Africa comments there's his Covid/Anti-Vax/conpiracy theorists TBAN here. It looks to me he's an asset when he's working music but anywhere else he's prone to tendentious soap-boxing. Is a TBAN from everything except music a thing? I haven't seen something like that before but that would make him a positive. DeCausa (talk) 18:20, 27 September 2022 (UTC)[reply]
      @ONUnicorn, VersaceSpace, and DeCausa: I'm worried that music, the topic that he really loves to edit, may also address what he is topic-banned from and that he might game the topic ban, intentional or not. Any music about race and politics, like White Riot, lately? Oh wait, there have been songs about race, like rap songs about it. (Well, there are classic rap songs, but I'm unsure whether he would consider them "classics".) BTW, he and I had content disputes, but it's mostly about cover arts and other editions lacking such. George Ho (talk) 18:26, 27 September 2022 (UTC)[reply]
      Yep, that's a problem, although if he were TBAN'd from race too he wouldn't be able to edit when those issues came up. Clearly this is moot in light of the number of opposes anyway. I'm comfortable with that if the assessment is that there's a risk that he would again express views that are abhorrent on WP or that they would drive his editing. I'm not so comfortable if it's because he has those abhorrent views whether or not expressed and whether or not they drive his editing. DeCausa (talk) 19:46, 27 September 2022 (UTC)[reply]
    • Oppose Other editors shouldn't have to work with this editor. Galobtter (pingó mió) 18:22, 27 September 2022 (UTC)[reply]
    • Oppose – if you need that many TBANs, then you've stopped being a "net positive", whatever that means nowadays. ♠JCW555 (talk)♠ 18:25, 27 September 2022 (UTC)[reply]
    • Oppose This editor has been disruptive regarding American politics, alternative medicine, vaccines, COVID-19, conspiracy theorists, Roman Catholicism, race and South Africa. Did I miss any? Cullen328 (talk) 18:41, 27 September 2022 (UTC)[reply]
    • Oppose Any benefit their music edits would bring would be outweighed by all the other baggage.-- Pawnkingthree (talk) 18:45, 27 September 2022 (UTC)[reply]
    • Oppose per Floquenbeam. The apology is extremely limited in scope and detail and sounds incredibly perfunctory. The issue was not limited to the inflammatory talk-page posts that were the proximate cause of his indefinite block. He had a long history of disruption and his editing was fundamentally at odds with our core mission to provide accurate, honest, reliably sourced information to readers. Here he expressed contempt for foundational site policy; I don't see any reason to think he'll stop trying to undermine clearly reliable sources based on his personal agenda. He was previously topic-banned for pushing anti-vaccinationism. I don't know how many red flags this community needs before deciding not to sacrifice more of its contributors' time and goodwill, but this is well over my personal threshold. MastCell Talk 19:02, 27 September 2022 (UTC)[reply]
    • Nope I see a short apology that doesn't even remotely address the seriousness of their talkpage soapboxing, but instead appears to promise to better source their "inflammatory sociopolitical comments" in the future. Between that, and the fact that they were really pushing the limits of their conspiracy theorist TBAN before they were blocked, indicates further issues ahead, to me. FrederalBacon (talk) 21:46, 27 September 2022 (UTC)[reply]
    • Comment - If you'll promise to not push your political views anywheres on the project? I'll agree to your reinstatement. GoodDay (talk) 21:53, 27 September 2022 (UTC)[reply]
    • Oppose. The very definition of WP:NOTCOMPATIBLE. The notion that the terminally intolerant should somehow be tolerated if they behave —they won't, they never do— has seen a rise in popularity in recent years, though thankfully, not on Wikipedia so much. I find the tendency toward that kind of acceptance highly disturbing. It should be resisted firmly. Needless to say, the pseudoscience is a further compounding factor, but since in one way or another it provides the basis for that sort of mindset, it's a moot point. El_C 04:41, 28 September 2022 (UTC)[reply]
    • I have in the past had positive interactions with JGabbard, and I know they are capable of doing good work on our music articles, so part of me wanted to support giving them another chance, but I had not previously recognised the full range of subjects they had previously been disruptive in. I had also not realised that this was someone who lists Tommy Robinson (activist) as a hero on their user page (scroll to the bottom). He lists Robinson, a white supremacist with convictions for violence and fraud, amongst the 'courageous watchdogs' he admires. That was the final straw for me - oppose. Girth Summit (blether) 06:06, 28 September 2022 (UTC)[reply]
    • Unblock with appropriate TBANs - Apparently, this editor can be productive in some areas since they have 50k edits, and there’s no harm when they edit the areas they aren’t disruptive in. I don’t see why STANDARDOFFER wouldn’t apply here, but I think an unblock here should be JGabbards final chance for a long time. Iamreallygoodatcheckerst@lk 16:13, 28 September 2022 (UTC)[reply]
      @GoodDay and Iamreallygoodatcheckers: I don't know. In the past, he declared his own sexuality and his own ancestry. Also, he declared to be "highly against Nazism". Ironically, his involvement in non-music topic was what got him blocked indefinitely. George Ho (talk) 16:53, 28 September 2022 (UTC)[reply]
      I just figured. If JGabbard did get reinstated, he'd be under heavy scrutiny. One mess up & re-banned. GoodDay (talk) 21:25, 28 September 2022 (UTC)[reply]
      There's nothing ironic about that situation. If he had stuck to music, and kept away from politics, he'd still be editing. However, attempts to get him to do just that have been made before. Despite a TBan from conspiracy theories, he still felt free to let rip harmful bile about the South African government which, while I'm sure he believed what he wrote, was nevertheless racist conspiracy theory nonsense. And, as I mentioned above, he felt free to voice his support for Tommy Robinson (activist) on his user page - seriously, follow that link and see who we're talking about. I'm fine with having a plurality of views on this project, but we're literally talking about someone who expresses support for convicted a violent neo-fascist. Surely that's a hard 'no'? Girth Summit (blether) 21:28, 28 September 2022 (UTC)[reply]
    • Support. Admittedly, I'm primarily voting because I dislike how many people have opposed solely because of his politics, so if the closer wants to consider this a "moral support" vote and basically ignore it, I suppose I can't really complain. I find the trend for things of this kind to devolve into "I don't want you here because I am uncomfortable with your political views" to be disconcerting; I'm sure a great many people here would find my political views quite disconcerting, too, I just have had the good sense never to talk about them here. I don't feel like I have a good sense for whether or not he'd be a problem, given how brief his unblock request was; given the circumstances, I am inclined to AGF, provided he is willing to accept TBans on race and maybe some other topics as a condition. —Compassionate727 (T·C) 23:58, 28 September 2022 (UTC)[reply]
      Being racist isn't politics. Neither is being a conspiracy nut. You tell us on your user page you area christian fundamentalist, here you tell us that having abhorent views of our fellow humans is just another political position which you happen to also hold. That you believe very similar things about various groups of people you have told us as well. Way too normalised this sort of pure bigotry on Wiki. But that is how it has been for years now. Bottom line, there is no hate like christian love. 85.16.40.253 (talk) 00:38, 29 September 2022 (UTC)[reply]
      It was politics for the Dixiecrats... EvergreenFir (talk) 01:32, 29 September 2022 (UTC)[reply]
      Fair enough. Anti-semitism was politics for the NSDAP as well. There are examples where basic human rights and dignity were politicsed all over history. With predictable outcomes. I for one have no taste to return to anything even adjacent to that. Normalisation of bigotry just is a dangerous step to take. 85.16.40.253 (talk) 01:48, 29 September 2022 (UTC)[reply]
      Wait a moment here. This is only your second post (indeed second edit ever) to Wikipedia. Why have you suddenly chosen this discussion, to participate in? GoodDay (talk) 01:51, 29 September 2022 (UTC)[reply]
      I have a variable IP adress perhaps? Nothing i can do about that (other than making an account obviously, which i chose not to do), new IP every day and with that zero contribs, usually. I am not new, never claimed to be and i just don't want to make an account even after a decade of lurking and some gnomish edits here and there. As well as sometimes commenting here, or at ITN or where ever i feel like it really. 85.16.40.253 (talk) 02:01, 29 September 2022 (UTC)[reply]
      Politics is just the government of human society: pretty much everything is political. I obviously wouldn't describe my own political views as "abhorrent," and I try to avoid having strong opinions on many of the most politically salient topics, as I feel investment in politics often distracts from (when it doesn't directly undermine) true, pious religion (as you yourself have observed, given your cynical remarks concerning "Christian love"). FWIW at this point in this discussion, I certainly don't agree with JGabbard's views of race, COVID-19 vaccines, or probably anything else (not that I have scrutinized his far-flung commentaries especially closely), but I know from experience that many people would find my views on other topics, such as contraception and scientific naturalism, similarly backwards. Yet nothing will ever become of it, because I know what the house biases are and I avoid substantially engaging with topics where I would be unable to conform. JGabbard could learn to do this, too (whether he would is another question; it seems the community is unwilling to find out). So the oft-touted position that racists/fascists/etc. are incompatible with the project because they are racists/fascists/etc., and not because they are unable or unwilling to suspend their worldviews and engage collaboratively, makes me nervous. —Compassionate727 (T·C) 11:49, 29 September 2022 (UTC)[reply]
      Compassionate727, I think you're missing the point about racist beliefs, in the sense that they fundamentally concern immutable characteristics. So, following that, I could join your Christian community by adopting your set of beliefs regardless of my background; and likewise, you could do the same by joining my community by adopting socialist beliefs, regardless of your background. That we are unlikely to want to do that is really an aside to that salient principle, that it's possible (and in fact it happens in a myriad of ways).
      By contrast, I could never join a an overtly racist group. To them, I'll always be subhuman, often to the point of needing to be destroyed, and there is absolutely nothing I could ever do about that. Since, again, the tautology here is that my innate traits are, well, innate and unchangeable (i.e. it just is not possible for one to alter their ethnicity, skin colour, etc.). El_C 17:17, 29 September 2022 (UTC)[reply]
      @El C: Oh boy, we are getting so far off-topic here. I'd really just wanted to complain about how I felt like everyone was latching onto all of the detestable things he has said and entirely ignoring his promise to not do that going forward. Clearly analogizing was the wrong way to go about that. Absolutely, I recognize that racism is especially bad because it focuses on immutable traits that have nothing to do with anything, and Tamzin's essay makes a worthwhile point when contending that hateful views are uniquely, even inherently disruptive. And we both agree that viewing someone as subhuman is hateful, and that someone who is unwilling to edit Wikipedia without insinuating that some people are subhuman doesn't have a place here. But what about other things that are maybe hateful but maybe just disagreeable? For example, do blacks who work for police departments express hatred for blacks? I imagine we would both say no, but some people in the US did argue this in the 1960s. And then we could have a whole discussion about what constitutes hatred to unravel what exactly distinguishes the one from the other, but that probably wouldn't be very fruitful, so I hope we don't do that. I just hope you can appreciate that saying that some people don't belong in the community because they are hateful without specifying as a corollary that they are also disprutive makes me nervous. —Compassionate727 (T·C) 18:04, 29 September 2022 (UTC)[reply]
      Compassionate727, I guess what I'm getting at is that I don't think I, for example, should be expected to collaborate with people who I know view me as subhuman (speaking generally, not about JGabbard, specifically), regardless if their editorial work in itself is disruptive. Speaking for myself, I've always been open to collaboration, and also friendship, with folks who I might disagree with on the fundamentals — but not that. And, in fact, if you go to the bottom of my talk page you'll see threads that primarily feature three people: a deer hunter (*wink*), a conservative, and a devout Christian. All three of whom I consider friends. El_C 18:16, 29 September 2022 (UTC)[reply]
    • Oppose per Girth Summit. Andre🚐 00:00, 29 September 2022 (UTC)[reply]
    • Oppose - We should not be encouraging this user's Games Done Quick Wikipedia all DS regimes% speedrun. —Jéské Couriano v^_^v a little blue Bori 01:34, 29 September 2022 (UTC)[reply]
    • Oppose. There is a debate sometimes about the hypothetical "polite bigot". The essay WP:NONAZIS takes the position that such a person should be blocked. An essay I wrote, Wikipedia:Hate is disruptive, concurs in part and dissents in part, opining that such a person should be allowed to edit if they never let on what their views are, while also concluding that this disagreement is largely theoretical, as, in practice, people with such views tend to be outspoken about them. As here: The number of userboxen on JGabbard's userpage, many of them about politics, tells you everything you need to know about his willingness to be the "polite bigot" who keeps to himself and keeps his politics off-wiki. Or if that doesn't convince one, one can see where I first got to know JGabbard, an MfD in which he vigorously defended his decision to refer to himself as a "citizen" of a breakaway state built on enslaving Black people, using both ahistorical fallacies and righteous indignation to justify his position.
      I see no reason to trust that JGabbard has suddenly learned how to not be disruptive when it comes to his fringe views, after years of not getting it. And, like others, I see no reason that editors should have to collaborate with someone who has behaved in this manner.
      By the way, @Girth Summit: I also took note of an entry on JGabbard's list of heroes, namely Francis Schaeffer. When I was in high school, I had the opportunity to spend a few hours in a small seminar led by his son Frank. Frank has said and written a fair bit on the views his father espoused—most memorably, calling for the overthrow of the U.S. government for allowing abortion. -- Tamzin[cetacean needed] (she|they|xe) 12:25, 29 September 2022 (UTC)[reply]
    • Oppose Anti-vax nonsense (including making articles incorrect and then trying to defend it), racism per the original block, and as a bonus espousing a violent racist criminal as one of their heroes on their userpage? Sounds like exactly the type of editor we should be welcoming back with open arms. I don't think. Black Kite (talk) 13:49, 29 September 2022 (UTC)[reply]
    • I'd close this as no dice, but I had a pretty extensive conflict with this user way back when, so one might argue I'm not the most neutral person. I'll just go with oppose, per Cullen, per Black Kit, per Tamzin, per common sense, etc. Drmies (talk) 17:31, 29 September 2022 (UTC)[reply]
      Yes, WP:SNOW clearly applies. Someone please close this. —Compassionate727 (T·C) 18:05, 29 September 2022 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Resumption of edit war by User:Marrew

    Strong evidence of an edit war is easily found at User talk:Marrew, including a 24 hour block and a 1 month block. The edits go against the consensus expressed at Talk:International System of Units#RfC on entries in tables. This edit resumes the edit war. I recommend a community ban. Jc3s5h (talk) 02:14, 28 September 2022 (UTC)[reply]

    I am also concerned by this resumption of this edit war, despite two blocks so far. Xxanthippe (talk) 02:57, 28 September 2022 (UTC).[reply]
    Now blocked indefinitely by Bbb23. That outcome was basically guaranteed, I'm afraid. --Yamla (talk) 17:16, 29 September 2022 (UTC)[reply]

    Can someone revert this serial vandal on a mission?

    IP blocked. Well-wishers can post to Doug's Talk page.--Bbb23 (talk) 17:03, 28 September 2022 (UTC)[reply]

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

    https://en.wikipedia.org/wiki/Special:Contributions/123.215.23.150 In hospital slowly recovering from painful liver cancer surgery successfully Doug Weller talk 16:19, 28 September 2022 (UTC)[reply]

    Here's hoping for a successful and complete recovery, and I will double check. Cheers. Dumuzid (talk) 16:21, 28 September 2022 (UTC)[reply]
     Done. Feel better soon. DatGuyTalkContribs 16:21, 28 September 2022 (UTC)[reply]
    I hope you mean the surgery was successful, not just the recovery. – Muboshgu (talk) 16:37, 28 September 2022 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Just a small FYI and reminder for my fellow administrators...

    Remember that if you must hide a user creation log using revision deletion (or suppression for users with Oversight and in situations that warrant it), you must redact both the "action and target" and the "performer's username/IP address" in order for that particular log and its information to be fully hidden from the public (or hidden from non-oversighters in the case of suppression). Otherwise, if you only redact the "performer's username/IP address" and leave the "action and target" visible to the public, the user creation log entry will still be fully visible and viewable to the public via the API. If anyone has any questions, please let me know (please ping me if you respond to me in this discussion) and I'll be happy to answer them. :-) Cheers - ~Oshwah~(talk) (contribs) 02:36, 29 September 2022 (UTC)[reply]

    @Oshwah:I think you should place a note at the top of the user creation log. Animal lover |666| 13:30, 29 September 2022 (UTC)[reply]
    Hi Animal lover 666! I appreciate your response and suggestion, but I don't think that it's necessary. The content on the user creation log page text is currently worded towards an audience who may need information as to what this log is, what inappropriate usernames are, and how to address any inappropriate usernames that are found. I don't want it to be worded toward administrators, who make up a very small percentage of the total audience who would read that log page text.
    However, I'm completely open to hearing from anyone who disagrees and thinks that this may be a good idea. If the directions were at the bottom of the text and very brief, ...Sure? Maybe. :-) Something like:
    "Administrators: If you must hide a user creation log using revision deletion, you must redact both the "action and target" and the "performer's username/IP address" in order for that particular log and its information to be fully hidden from the public."
    This I'd potentially be open to if other users provide input, since it's brief, to-the-point, and doesn't go unnecessarily into depth. Again, I don't think that it's something that we need to add there, but I always keep an open mind. ;-) ~Oshwah~(talk) (contribs) 13:42, 29 September 2022 (UTC)[reply]
    I personally think this is not good advice. If you only redact the user creation log, the username still persists at Special:ListUsers, as well as in CentralAuth, all the dropdowns, and probably elsewhere. I mainly use deletion on the newuser log to stop people reporting the usernames, and to stop the immediate source of offence. If you're doing anything to the extent that you have to worry about the API, you should probably do a proper job and get the username suppressed instead. Advising people to half a job but properly is less than ideal. -- zzuuzz (talk) 13:57, 29 September 2022 (UTC)[reply]
    Zzuuzz - I agree to an extent. I never like doing "half-jobs", but in cases where suppression isn't the solution (and going off your reasoning, it will never be, since suppressing the username along with an indefinite block doesn't also hide it from Special:ListUsers, etc - only global suppression does this, IIRC), I think that the ability and (sometimes) the need to redact usernames from the user creation log is necessary, and doing this properly means that it's not visible publicly using any means. I know that redaction of anything in this log won't hide the username from every single location, but to say that this is a reason why we shouldn't act in our best judgment when the situation calls for it is like saying that we shouldn't try and limit any disruption or damage at all simply because it can be found elsewhere if one were to really look. The ideal ideal solution? We should be able to fully redact or suppress a username locally and in all locations. That's the real fix, but we don't have that right now. We can only control what we can control. :-) ~Oshwah~(talk) (contribs) 14:16, 29 September 2022 (UTC)[reply]
    Well, that's great but I stand by my comments. BTW local suppression on its own does hide the user from Special:ListUsers and the dropdowns (locally). These days I have no idea why any oversighters would locally suppress an account. There should be a big well-oiled pipeline to the stewards. -- zzuuzz (talk) 14:26, 29 September 2022 (UTC)[reply]
    Zzuuzz - No worries; I think that it's safe to say that you know me well, and hence you know that I'm always happy to hear from you and that I welcome your input, feedback, and comments - except if they disagree with me! I'm kidding ;-), but moving on... Okay, that's interesting to hear that bit about username suppression from you... I'll have to test that again. From what I remember from testing awhile back, I thought that username suppression (when the option is ticked when indefinitely blocking an account) only executed a script that suppressed the username from all logs and edit revision histories, etc and put it in the block log as a suppression action. It was akin to having to manually find and suppress each and every log and revision, and was more like a convenience thing than something that did more than I described. You very well could be right; thanks for the information. Anyways, I'm digressing... lol. All I wanted to state when I started this discussion was that, in the event that redacting (or suppressing) a user creation log is necessary and needs to be done manually to that log, that hiding both the "action and target" and the "performer's username/IP address" is needed so that the log was fully hidden from view and from all methods and instances - nothing more. :-) Thanks again for the input, and please don't be a stranger if you wish to discuss your thoughts any further. My door is always open. ~Oshwah~(talk) (contribs) 14:53, 29 September 2022 (UTC)[reply]

    Close review requested in AP / BLP article

    I am requesting a close review of a recent RfC at Hunter Biden laptop controversy. The RfC is here.

    The closer refers to having counted !votes and does not indicate that they fully considered the participants’ supporting arguments and concerns or whether there is a valid consensus in the poll. The close does not appear to have fully addressed the significant BLP and sourcing issues, the level of consensus required to change the status quo text, and the discussion of the content of the sources cited in the discussion. Several such issues were raised by the participants who posted more than brief “yes” or “no” responses to support their !votes with reasoning that went beyond merely counting the number of source citations.

    The closing text is brief in light of the complexity and controversy raised by the RfC question. After the close, some editors interpreted the result as having decided only the RfC question as stated -- whether to use the word “alleged”. Others cited the close of the RfC as a basis to oppose broader wording that was consistent with the close and not synonymous with “alleged”. Such an interpretation was beyond the scope of the RfC statement discussion, and the !vote arguments and policy issues that might support such an alternative interpretation were not addressed in the closing statement. SPECIFICO talk 13:47, 29 September 2022 (UTC)[reply]

    Comments from uninvolved editors (Laptop controversy)

    • This needs to be re-closed by an uninvolved admin/editor experienced in closure, I think. The fact that it was closed by someone who on their talk page describes themselves as a fundamentalist evangelist Christian is one thing, but the fact that poor rationales do not appear to have been discounted (GoodDay's is meaningless and Madame Necker's is simply an opinion about the whole affair; we'll ignore the fact that MN is a new account who has already racked up five different DS notices on their talk page). Black Kite (talk) 14:05, 29 September 2022 (UTC)[reply]
      Your comment about the closer's stated religious beliefs does not seem appropriate or relevant. I think it is possible to evaluate the close without making it personal. Mr Ernie (talk) 14:22, 29 September 2022 (UTC)[reply]
      Yeah that's pretty messed up BK. The quote on the userpage is "I am a very fundamentalist (in the historic sense of the term) Christian evangelical." What does that have to do with Hunter Biden's laptop? I assume you're suggesting that because many (most?) Christian evangelical voters vote Republican, therefore a Christian evangelical has some kind of bias or COI that should prevent them from closing an RfC about some AP2 political issue? Does your logic apply to closers who have the atheist userbox on their userpage? Because atheists tend to vote Democrat, does that also disqualify them? By this logic, nobody would be able to close anything in AP2. I'm quite shocked to see the suggestion that a closer's religious beliefs are a reason to revert their close, especially when it's a non-religious topic. I think you should strike that. Levivich (talk) 18:17, 29 September 2022 (UTC)[reply]
    • I was actually about to start a closing draft when I saw on my watchlist that it had been closed. My initial reading was that it was too close a call to find any sort of consensus for either option, specially due to the raised NPOV and BLP issues. Isabelle 🏴‍☠️ 15:08, 29 September 2022 (UTC)[reply]
    • Endorse. Though numerically the vote was close, with the "No's" being in the majority by only a few votes, I agree the closer properly weighted the votes based on the quality of arguments and application of policy, in particular WP:NPOV. Some editors thought we should use "alleged", other thought not, but then everyone started compiling sources, and as the "no" voters pointed out, the sources were almost unanimous in not using "alleged". WP:NPOV means we summarize those sources--i.e., we don't say alleged because they don't say alleged. The "Yes" voters did not rebut this in any way (e.g., by showing sources predominantly using "alleged"; not just one or two sources; and not from 2 years ago, but current). So, if most editors agree that most sources do not use alleged, then that's consensus to not use alleged. I don't see any error here, it's the proper application of WP:NOTAVOTE. Levivich (talk) 16:04, 29 September 2022 (UTC)[reply]
    • It doesn't seem like a great close. I'm particularly looking at Some editors asserted that the ownership is still unclear but largely failed to support this with reliable sources, while editors opposing the adjective produced a plethora of recent RS that did not doubt the connection, which simply doesn't line up with the quotes from sources produced in the RfC. There were a few more "no"s than "yes"s, but there were also more inexperienced/new editors saying "no" and more poor arguments on the "no" side (although not by much). The later comment by the closer extending the RfC about "alleged" to apply to qualifying the belonging in any way is an overreach. I'm not saying there was consensus for the "yes" side, either, though. We have sources that appear pretty split on this, in terms of the language they use, and both sides have arguments backed by policy. I suppose I'd be inclined to err on the side of BLP, but that's my own $0.02. Although I don't think anyone would love the idea of a repeat RfC, it might be more effective to provide a set of options for wording and/or do a more thorough analysis of the sourcing apart from the RfC, along with weighting by how recent the sources are. i.e. what is the consensus of sources published since June (arbitrarily)? — Rhododendrites talk \\ 16:44, 29 September 2022 (UTC)[reply]
      Are we looking at the same sources? That sounds sarcastic, but I am genuinely seeking clarification, as among the sources cited in the RfC, I count three sources that consistently use language like "alleged" and "purportedly" (all from April or earlier), eleven that pointedly omit such language, and a couple that use "alleged" when describing what earlier sources said about the laptop but omit that language when speaking about it themselves (as well as a couple whose constructions are too ambiguous to confidently parse). Where is the disconnect in what we are perceiving? —Compassionate727 (T·C) 17:17, 29 September 2022 (UTC)[reply]
      There is a section, "sources" which lists several bulletpoints. In order of whether they use/describe some qualification of ownership: no, yes [here and elsewhere, there is ownership/verification attributed to the emails, but not the laptop], yes, yes, yes, no, yes, sorta [for the first part, but again regarding emails], no, no, [quote from someone who funded the effort, not the publication], yes [again separating laptop from emails], no, yes [sorta], no [but the sentence isn't about this], yes, yes, [someone "yelling about Hunter Biden's laptop" isn't a statement about authenticity], yes, [doesn't address it], mostly no [attempts to rely on inference from the title]. While it's entirely possible to come to different conclusions about the consensus among those sources, it's hardly one side failing to support their argument and the other producing a plethora of sources. — Rhododendrites talk \\ 17:52, 29 September 2022 (UTC)[reply]
    • Vacate for a more experienced closer to re-close. With US politics, it's not enough that the close is right; it has to be seen to be right, so we leave closes that touch on US politics to the wizened and elderly who enjoy the fullest confidence of the community.—S Marshall T/C 17:22, 29 September 2022 (UTC)[reply]
    • Probably a WP:BADNAC, but the close is correct anyway. Nearly every comment saying yes is a WP:TRUTH vote, that we dont really know if it is or it isnt. Those votes should be given less weight when there are users providing numerous reliable sources that state as a fact what those users dispute to be a fact without any sources that likewise dispute it. The numbers may say no consensus, but as ever this isnt a vote and the strength of the arguments for "no" were much stronger than those for "yes". Id have closed it as a consensus for no as well. nableezy - 17:42, 29 September 2022 (UTC)[reply]
    • Endorse close Well thought out and justified through and through. These objections regarding experience or the users religion (really?) are incredibly superficial. Arkon (talk) 17:59, 29 September 2022 (UTC)[reply]

    Comments from involved editors (Laptop controversy)

    • Overturn to no consensus. To put this in WP:CLOSECHALLENGE language: "the closure was not a reasonable summation of the discussion". C727's closure depends heavily on his assessment that "Some editors asserted that the ownership is still unclear but largely failed to support this with reliable sources, while editors opposing the adjective produced a plethora of recent RS that did not doubt the connection." This is untrue, as participants on both sides were equally likely to make no explicit reference to sources, and it's safe to assume everyone was responding either to the sources already in the article or in the list posted in the RfC.
      I inquired about this issue at C727's user talk page (here), and C727 said "I found that many of the earliest sources provided in that list used some kind of qualification, but that by the end of April, most sources were consistently describing the laptop as Biden's, without qualification" and then "Given how pronounced the trend was and how recent sources exert a controlling influence, I considered that sufficient."
      I see this as clear evidence of a WP:SUPERVOTE. The trend analysis C727 is using as the basis of his closure was not presented by the RfC participants, nor did anyone reference WP:AGEMATTERS, the policy C727 linked in that last quote. Firefangledfeathers (talk / contribs) 14:34, 29 September 2022 (UTC)[reply]
    • I would welcome a review from an experienced closer in order to solidify the consensus. There have already been attempts to circumvent the close by messing with the descriptor. What sticks out to me in the RFC is that the sourcing presented came overwhelmingly from the "No" !voters, which the closer noted. Mr Ernie (talk) 14:37, 29 September 2022 (UTC)[reply]
      Talk:Hunter Biden laptop controversy#Sources Here is a link to the section in the RFC listing the sourcing that many of the No votes seem to base their vote on. Mr Ernie (talk) 14:43, 29 September 2022 (UTC)[reply]
      And Yes votes. Firefangledfeathers (talk / contribs) 14:44, 29 September 2022 (UTC)[reply]
    • To be more honest than I feel comfortable being, it feels to me like SPECIFICO is forum-shopping because he didn't like the result. Shortly after I closed the RfC saying there was a consensus against stating that the laptop is "alleged to have belonged" to Biden, SPECIFICO added that it is "believed to have belonged" to him, which Mr Ernie reverted; at that point, SPECIFICO reached out to me via email thanking me for my closure and asking me to weigh in on the issue (there was no indication that SPECIFICO felt anything about my closure was incorrect); I did, explaining why I felt the arguments against using "alleged" also covered "believed" or any similar weasle-ish words, at which point he attempted to downplay it as "an after-the-fact personal opinion" rather than the clarification of the closure that he had requested. Now that several other editors have agreed that SPECIFICO's new wording contradicts the consensus I found, he's here seeking to overturn it.
    Between my various comments, I believe I have adequately explained why I found the consensus I did and don't intend to engage extensively with this unless people have questions. But to summarize one last time, for the benefit of uninvolved persons: pretty much every source cited in the discussion was provided in a list mid-discussion; many of them, including pretty much all of the most recent sources, described the laptop as Biden's without qualification. A majority of editors agreed that there is no longer any dispute in the RS that the laptop is Biden's; whether they explicitly mentioned Adoring nanny and his list or not is immaterial, I think it is clear from reading the comments that they are aware of it, and it would be foolish to say that they need to say exactly the right things for their intent to be relevant in shaping the consensus. Likewise, WP:AGEMATTERS was clearly on at least some participants' minds (see e.g. Thriley's reference to "current" sources), even if nobody explicitly linked to it (and it is relevant regardless). I likewise took into account the way the discussion unfolded; while in total, 11 people supported using "alleged" and 14 opposed, the ratio of support to oppose votes swung heavily in favor of the opposers as more and more sources were added to the list. For example, after Guest2625's large addition on September 1, three people voted for using alleged and six against; nobody would question that a two-thirds majority is a solid consensus without a compelling policy reason. And given the large number of RS produced in favor of directly stating the laptop is Biden's, I don't think BLP is a highly salient issue (BLP is not a license to ignore sources), especially when it only indirectly implicates Biden, given the ongoing controversy over the authenticity of the documents.
    I'm willing to admit when I screw closes up (I have done that here before), but I don't see any compelling reason to believe this is one of them. —Compassionate727 (T·C) 16:06, 29 September 2022 (UTC)[reply]
    • This misrepresents my email to the closer, in which I followed what I believe to be best practices to first approach the closer with a concern before formally requesting a close review. Compassionate, as I think is now clear, thanking you for your effort was not an endorsement of your conclusion. SPECIFICO talk 16:27, 29 September 2022 (UTC)[reply]
      Thing is, Specifico, your edit on Sep 28 at 12:46 adding "believed to have", with the edit summary more direct representation of status, consistent with RfC, shows that at that time, you were fine with the close of the RfC, and were even making an edit consistent with that close. No close challenge from you at that time. It was only after the discussions at the article talk page and ANEW (last post: 2:40 Sep 29) (both of which you participated in) resulted in the reversion of "believed to have" on the basis that it was against the RfC closure, that you then filed this close review (at 13:47 on Sep 29). It looks to me like you didn't have a problem with the close if you could change "alleged" to "believed to have" (i.e., if you could ignore the result with crafty wordsmithing)... only after that was shut down did you seem to raise issues with the close itself. In my view, this seriously undermines your argument. Levivich (talk) 16:37, 29 September 2022 (UTC)[reply]
      Evidently, and even if it were, it would be reasonable for you to change your mind about my closure after discovering that it was broader than you had thought. I mention the email because 1) it seems to fit within what a pattern of back-peddling here and, more importantly, 2) I had wondered even when I first saw the email why you had reached out to me privately concerning such a public matter as on-wiki consensus, instead of using my talk page. Given everything that has happened since, I wonder if it was so that it wouldn't be obvious to everyone else that you had asked for my input (and implicitly assented that I held a bit of authority on that issue) in case that turned against you, which seems like an oddly underhanded way of seeking clarification of consensus, but a rather natural one if you had been planning to challenge an unfavorable finding the entire time. I find myself struggling to articulate that there was anything truly improper about it, yet the level of cynicism I see there discomforts me. —Compassionate727 (T·C) 16:59, 29 September 2022 (UTC)[reply]
    • One admin already reviewed this RFC case and determined that the closer was correct in their assessment of consensus on the WP:ANE case, and also opined on the article's talk page that the subsequent edits were out of line based on the RFC. I guess you're looking for a second admin's opinion, then? PhotogenicScientist (talk) 16:14, 29 September 2022 (UTC)[reply]
    • I'd like to see a challenge or a review of this close and whether it was a WP:SUPERVOTE. Andre🚐 16:19, 29 September 2022 (UTC)[reply]

    Conrad Bennette Tillard

    I am being harassed by someone named Glane23 that keeps taking accurate well documented factual biographical information material off of my page. 24.46.216.128 (talk) 15:09, 29 September 2022 (UTC)[reply]

    "my page". Which page would that be? The one you're blocked from? -- Malcolmxl5 (talk) 15:21, 29 September 2022 (UTC)[reply]
    There is no substance to your complaint. I see you edit warring with multiple editors at Conrad Tillard where Glane23 has made ONE revert. -- Malcolmxl5 (talk) 15:26, 29 September 2022 (UTC)[reply]

    Geonotice request

    Information icon There is a geonotice request at Wikipedia:Geonotice#Wikiconference:2022/Submissions. Would one of you administrators please attend to it as you are able? Peaceray (talk) 17:30, 29 September 2022 (UTC)[reply]

    Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Administrators%27_noticeboard&oldid=1113094579"