Jump to content

Wikipedia:Administrators' noticeboard: Difference between revisions

Page semi-protected
From Wikipedia, the free encyclopedia
Content deleted Content added
Line 88: Line 88:
:*Adding: Wow... I just looked at Dev0745's contributions. They are quite cheerfully editing [[The Kerala Story]] in violation of the ban they are unsuccessfully appealing here. I don't know what they thought the ban meant. Blocked for a week. [[User:Bishonen|Bishonen]] | [[User talk:Bishonen|tålk]] 08:12, 12 May 2023 (UTC).
:*Adding: Wow... I just looked at Dev0745's contributions. They are quite cheerfully editing [[The Kerala Story]] in violation of the ban they are unsuccessfully appealing here. I don't know what they thought the ban meant. Blocked for a week. [[User:Bishonen|Bishonen]] | [[User talk:Bishonen|tålk]] 08:12, 12 May 2023 (UTC).
*'''Endorse topic ban''' in light of the blatant violation today. [[User:Trainsandotherthings|Trainsandotherthings]] ([[User talk:Trainsandotherthings|talk]]) 15:32, 12 May 2023 (UTC)
*'''Endorse topic ban''' in light of the blatant violation today. [[User:Trainsandotherthings|Trainsandotherthings]] ([[User talk:Trainsandotherthings|talk]]) 15:32, 12 May 2023 (UTC)
*'''Endorse'''. Tamzin's rationale for applying this topic ban was well reasoned and detailed, and Dev0745 has been extended considerable leniency in the past - they already had a narrow focus topic ban and and a formal logged warning for the exact same issues with pov pushing and misrepresenting sources. If this editor thinks that it is acceptable to take a low quality, tabloid, source and misleadingly quote sentences out of context to support claims that the source specifically debunks they have no business editing in such contentious areas. [[Special:Contributions/192.76.8.84|192.76.8.84]] ([[User talk:192.76.8.84|talk]]) 16:30, 12 May 2023 (UTC)


== Inappropriate non-admin closure by [[User:FormalDude]] ==
== Inappropriate non-admin closure by [[User:FormalDude]] ==

Revision as of 16:30, 12 May 2023

    Welcome — post issues of interest to administrators.

    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 seven days are archived by Lowercase sigmabot III.(archivessearch)

    Open tasks

    XFD backlog
    V May Jun Jul Aug Total
    CfD 0 0 0 38 38
    TfD 0 0 1 4 5
    MfD 0 0 1 2 3
    FfD 0 0 0 3 3
    RfD 0 0 5 70 75
    AfD 0 0 0 0 0


    Pages recently put under extended-confirmed protection

    Report
    Pages recently put under extended confirmed protection (31 out of 8286 total) (Purge)
    Page Protected Expiry Type Summary Admin
    Template:Oclc 2024-08-23 17:59 indefinite edit,move High-risk template or module: 2500 transclusions (more info) MusikBot II
    Draft:Lyrra 2024-08-23 13:20 indefinite move Persistent disruptive editing from (auto)confirmed accounts UtherSRG
    DC Super Hero Girls 2024-08-22 19:52 indefinite move Move warring: per RFPP Daniel Case
    Hamas red triangle 2024-08-22 14:58 indefinite edit,move Arbitration enforcement; requested at WP:RfPP Isabelle Belato
    Millennium Dome 2024-08-22 13:15 2024-09-22 13:15 edit Persistent sock puppetry Goodnightmush
    Basem Al-Shayeb 2024-08-22 02:14 2024-09-05 02:14 edit,move Edit warring / content dispute Daniel Case
    Ian Anderson (soccer) 2024-08-21 21:20 indefinite create Repeatedly recreated, see Wikipedia:Articles for deletion/Ian Anderson (soccer) (3rd nomination) RL0919
    Emily A. Holmes 2024-08-21 21:10 2025-02-21 21:10 edit,move Contentious topics enforcement for WP:CT/BLP; requested at WP:RfPP Daniel Quinlan
    Korenevo, Korenevsky District, Kursk Oblast 2024-08-21 20:27 2025-08-21 20:27 edit,move WP:GS/RUSUKR ToBeFree
    Template:Fdate 2024-08-21 18:00 indefinite edit,move High-risk template or module: 2802 transclusions (more info) MusikBot II
    Palestinian suicide terrorism 2024-08-21 17:11 indefinite edit,move Arbitration enforcement ScottishFinnishRadish
    Draft:Rica Arnejo 2024-08-21 16:28 indefinite create Sock target Pppery
    Draft:Dsquares 2024-08-21 12:08 indefinite create Repeatedly recreated BusterD
    Pokkiri 2024-08-21 11:53 indefinite move Persistent block evasion Bishonen
    Draft:Kedarkheda 2024-08-21 03:06 2024-08-28 03:06 move Move warring Johnuniq
    Israeli support for Hamas 2024-08-21 02:56 indefinite edit,move Contentious topic restriction Johnuniq
    Pokrovsk, Ukraine 2024-08-20 19:48 indefinite edit,move Community sanctions enforcement: per RFPP and WP:RUSUKR Daniel Case
    Michael Lisovetsky 2024-08-20 18:38 indefinite create Re-salt Pppery
    Template:WP Athletics 2024-08-20 18:00 indefinite edit,move High-risk template or module: 3616 transclusions (more info) MusikBot II
    Dil Ko Tumse Pyaar Hua 2024-08-20 13:48 indefinite create Repeatedly recreated; requested at WP:RfPP Isabelle Belato
    Udukai 2024-08-20 11:46 2024-09-20 11:46 edit,move repeated hijacking to be an advertisement for something different than the original topic Bearcat
    Operation Hiram 2024-08-20 10:55 indefinite edit,move Arbitration enforcement ScottishFinnishRadish
    History of the chair 2024-08-20 09:21 2025-02-20 09:21 edit,move Persistent sockpuppetry Lectonar
    Jhanak 2024-08-20 06:14 indefinite move Addition of unsourced or poorly sourced content: please discuss on article talk Johnuniq
    South India 2024-08-20 04:27 indefinite edit,move Contentious topic restriction: WP:CT/IPA Johnuniq
    Israeli blockade of aid delivery to the Gaza Strip 2024-08-20 01:24 indefinite edit,move Contentious topic restriction: per RFPP and ARBPIA Daniel Case
    August 2024 Deir el-Balah attacks 2024-08-20 01:19 indefinite edit,move Contentious topic restriction: per RFPP and ARBPIA Daniel Case
    Third Battle of Khan Yunis 2024-08-20 01:11 indefinite edit,move Daniel Case
    Mike Lynch (businessman) 2024-08-20 00:59 indefinite edit,move Violations of the biographies of living persons policy: per RFPP Daniel Case
    Wikipedia talk:Administrators' noticeboard/Administrators' noticeboard/12 2024-08-20 00:54 indefinite create Repeatedly recreated TheresNoTime
    Nikki Hiltz 2024-08-19 22:59 indefinite move Misgendering; resumed after prior protection period Firefangledfeathers

    WP:SO unblock request from MrTallBoy

    MrTallBoy (talk · contribs · deleted contribs · nuke contribs · logs · filter log · block user · block log)

    Sorry for the multiple similar requests all, I was clearing through the backlog at CAT:UNB and there's another WP:SO unblock request. Pinging the blocking admin @Dreamy Jazz: for commentary. User admits to the sockpuppetry, claims to have waited the 6 months as requested with good behavior, and is asking to be unblocked. Any commentary one way or the other? --Jayron32 16:43, 5 May 2023 (UTC)[reply]

    @MrTallBoy, In order to evaluate this request, it would be helpful to me (but not required in any way) to see an example of what we could expect of you in unblocked. Do you have any examples of other wikis (wikimedia or otherwise) that you have constructively contributed to while you've been blocked? SQLQuery Me! 16:57, 5 May 2023 (UTC)[reply]
    MrTallBoy answered on his talk page. I have pasted his response below:

    Dear SQL, hope you are doing well. I do not have access to edit at WP:AN, so I choose to answer your question here as a right place. What you can expect from me in unblocked mode is the constructive edits, and to continue helping new editors with some editing trainings in my community on English Wikipedia.

    While I was blocked, with hundreds edits I constructively contributed to the following wikis:

    Thank you for your consideration.

    That's his response. --Jayron32 18:14, 5 May 2023 (UTC)[reply]
    @MrTallBoy, thank you for your response. It looks like you've been able to contribute constructively on other wikis while blocked here. I would support an unblock at this time with the note that I have not personally run a check to see if MrTallBoy has been socking recently. SQLQuery Me! 00:08, 7 May 2023 (UTC)[reply]
    • Most of those cross-wiki accounts were blocked by Yamla - I'd be interested to know from them whether there was evidence of socking on those projects, aside from the sockpuppetry over here. I'd also observe, perhaps uncharitably, that I doubt this user's competence to get involved in training new editors. Girth Summit (blether) 18:23, 5 May 2023 (UTC)[reply]
      Strike that - those accounts aren't blocked. A script I run is crossing through them, so I assumed they were all blocked, but I see that that's just because they're linked to the account that is blocked on this project. Girth Summit (blether) 10:50, 6 May 2023 (UTC) [reply]
    Back in November 2022 I was open to the idea of a conditional unblock that limited this user to use one account and to disclose any conflicts of interest. I think I would be supportive of such a conditional unblock (or even just an unblock under WP:SO) as long as the standard offer conditions have been met (most importantly number 1 of not editing for 6 months). Furthermore, it would be good to see no disruptive behaviour on other projects. Keeping this user to one account should help prevent the issues that led to this block, which is the abuse of multiple accounts.
    I don't have the time to do a full review of this, but will trust the judgement of the community and other admins to make a good decision. Dreamy Jazz talk to me | my contributions 10:41, 6 May 2023 (UTC)[reply]
    Based on the above responses, I have issued a conditional unblock per the conditions laid out by the blocking admin above. --Jayron32 14:14, 9 May 2023 (UTC)[reply]

    Removing Jimbo's ability to overturn ArbCom

    Hi all, please see this petition to amend the arbitration policy to remove Jimbo Wales's ability to overturn ArbCom decisions, which needs a 100 signatures as per the formal amendment process. Galobtter (talk) 18:27, 9 May 2023 (UTC)[reply]

    Review of Topic ban (Dev0745)

    Hello, recently I got topic banned from editing India, Pakistan and Afghanistan related articles by Tamzin after editing the article of Love jihad conspiracy theory. She topic banned me by citing reason of verifiability and synthesis. But I am not convinced by her argument as I think her argument is not apply to my edit as I have cited verifiable soures and it was not Synth. The sentence written by me was clearly mentioned in the article. My edit link is here [1]. Can anyone comment about the TBAN decision. Is it reasonable? Thanks Dev0745 (talk) 15:24, 11 May 2023 (UTC)[reply]

    • Endorse topic-ban As Tamzin explained at great length, among other issues, Dev0745 was adding content to the Love Jihad conspiracy theory article about accusations against an organization by selectively citing sources without mentioning that the very sources they cited also said that an official investigation "concluded its probe in October 2018 after it found no 'evidence of coercion' that could result in prosecution." which eliminated the raison d'etre for their edit. And now Dev0745 is selectively citing the reasons for the topic-ban by omitting "Misrepresentation by omission" even though Tamzin stated (in bold) that that was "the main factor in my decision to impose a TBAN". Abecedare (talk) 15:38, 11 May 2023 (UTC)[reply]
    • Endorse topic-ban This is your second such ban under the terms of WP:ARBIPA (after such a ban in 2020) so it shouldn't come as a shock to you. Furthermore, you were formally warned here only about half a year ago that you were to stop misusing source material in relation top topics related to WP:ARBIPA. There's no way you should have thought this came out of the blue here. You were edit warring, you were tendentiously editing an arbitrated topic (of which you were made well aware that the topic was under special scrutiny) and you pressed ahead regardless of these issues. The topic ban is fully appropriate in this case. --Jayron32 15:50, 11 May 2023 (UTC)[reply]
    • Endorse topic-ban. This was explained at length, and from the quick review I did the sanction is more than reasonable. ScottishFinnishRadish (talk) 16:50, 11 May 2023 (UTC)[reply]
    • Note Dev0745 is forum-shopping. They have already tried WP:AE, and then my talkpage when I closed that. Black Kite (talk) 17:56, 11 May 2023 (UTC)[reply]
      Let this discussion run. The more voices they hear telling them they were in the wrong, the more it might stick. --Jayron32 18:08, 11 May 2023 (UTC)[reply]
      I don't think it is quite forum shopping, since the AE appeal was malformed and didn't get a proper review (by multiple people). Galobtter (talk) 18:41, 11 May 2023 (UTC)[reply]
      Fair enough, though I closed it because I believed it to be fairly cut and dried. As you and Jayron say though, it may be better to let it run this time. Black Kite (talk) 18:44, 11 May 2023 (UTC)[reply]
    • Endorse topic ban - Admins have been too lenient against this user if anything otherwise this report should have resulted in a topic ban. Srijanx22 (talk) 21:36, 11 May 2023 (UTC)[reply]
    • Thanks for your comments. According her Misrepresentation by omission was reason for Topic ban. I never read it at any Wikipedia policy. But I think, the article Love Jihad conspiracy theory itself is article where many thinks are omitted in lead only mention hindu women and Christian women are omitted which is also a misrepresentation by omission. Thanks... Dev0745 (talk) 05:32, 12 May 2023 (UTC)[reply]
    • Endorse topic ban. Tamzin's ban was well phrased and then painstakingly explained further on request. It comes none too soon. Bishonen | tålk 07:59, 12 May 2023 (UTC).[reply]
    • Endorse topic ban in light of the blatant violation today. Trainsandotherthings (talk) 15:32, 12 May 2023 (UTC)[reply]
    • Endorse. Tamzin's rationale for applying this topic ban was well reasoned and detailed, and Dev0745 has been extended considerable leniency in the past - they already had a narrow focus topic ban and and a formal logged warning for the exact same issues with pov pushing and misrepresenting sources. If this editor thinks that it is acceptable to take a low quality, tabloid, source and misleadingly quote sentences out of context to support claims that the source specifically debunks they have no business editing in such contentious areas. 192.76.8.84 (talk) 16:30, 12 May 2023 (UTC)[reply]

    Inappropriate non-admin closure by User:FormalDude

    User:FormalDude closed this RfC in violation of WP:NACD, which states that non-admins should not close discussions involving "close calls or controversial decisions"; the survey was a perfect 10-10 split, and the proposed question regarded the characterization of a controversial Florida bill, ticking both boxes.

    Additionally, in my opinion, their edit history casts a bit of doubt on their impartiality, as it seems to suggest a social-liberal bias, which may conflict with this RfC.

    I left a message on the editor's talk page voicing my concern, but it appears to have been ignored. Oktayey (talk) 16:10, 11 May 2023 (UTC)[reply]

    • Overturn I can't see that being anything but a no-consensus close. It's both numerically close, and both sides make cogent arguments. Either overturn and reclose as "no-consensus" or just re-open it and leave it open longer to see if the discussion leans either way with further commentary. --Jayron32 16:20, 11 May 2023 (UTC)[reply]
    • Comment - WP:NACD is for deletion discussions. Any uninvolved editor in good standing can close a RfC, so I wouldn't call this a violation. I agree sometimes it's better for admins to close controversial things, but the close request asked for an experience closer, which could be an admin or could be an experienced user such as FormalDude. WikiVirusC(talk) 16:38, 11 May 2023 (UTC)[reply]
      An experienced closer is a bit different than an experienced user, in my view. An experienced closer should have a history of closing discussions, including some difficult and close RFCs, that have either not been challenged, or survived challenges. I'm not saying that isn't the case here, but it is different than simply being an experienced editor. ScottishFinnishRadish (talk) 16:49, 11 May 2023 (UTC)[reply]
      Their status as an non-admin played no role in my assessment above. I don't really care if they were an admin or not, the assessment of the close should be done on how the close was handled, not on who handled it. Ad hominem rationales are rarely useful, it doesn't really matter who they were; just if they closed it correctly. I don't believe they did here, I don't think the rationale represents a reasonable summary of the discussion. --Jayron32 17:26, 11 May 2023 (UTC)[reply]
      ScottishFinnishRadish but isn't there a catch-22 there? If an experienced closer is someone who "should have a history of closing discussions, including some difficult and close RFCs, that have either not been challenged, or survived challenges" then it's impossible for any non-admin to become an experienced closer since such editors would be effectively prohibited from taking the risk in the first place. Valenciano (talk) 19:44, 11 May 2023 (UTC)[reply]
      Luckily there is a very broad spectrum of closes to make, so one can work their way up through varying levels of difficulty and contentiousness. ScottishFinnishRadish (talk) 20:44, 11 May 2023 (UTC)[reply]
      I understand and agree with what you are saying. I was saying they could be an experienced editor, not that any experienced editor would be an experienced closer. Was bringing up the point of an experience closer being requested, to distance this situation from my early sentence that said any uninvolved editor could close a RfC. WikiVirusC(talk) 17:48, 11 May 2023 (UTC)[reply]
      That section of the article regards closing discussions broadly, not just deletion discussions. Both the terms "deletion discussions" and simply "discussions" are used, but the relevant part refers to "discussions" generally. Additionally, WP:BADNAC also says:
      "A non-admin closure is not appropriate [when] The outcome is a close call (especially where there are several valid outcomes) or likely to be controversial."
      Oktayey (talk) 17:46, 11 May 2023 (UTC)[reply]
      WP:BADNAC is an essay. If we didn't allow non-admins to close contentious RFCs nothing would ever get done. ScottishFinnishRadish (talk) 17:51, 11 May 2023 (UTC)[reply]
      Per ScottishFinnishRadish, those pages are meant to guide people before they make a decision to close a discussion, they are not supposed to be rules we enforce around this matter. Ultimately, every close should be assessed on the merits of the close itself, not on who closed it. The NAC page should inform closers, not reviewers. --Jayron32 18:07, 11 May 2023 (UTC)[reply]
      In WP:NACD, while the first sentence does use both deletion discussion and discussion. It is all in one sentence so I believe the latter discussion is still referring to deletion discussion. The last paragraph is completely about deletion discussions with same reasoning of deletion discussion being mentioned first before simply referring to it as discussion. Of the 6 bullet points in between, the majority are referring to deletion discussions directly, one is mentioning {{nac}} which is mostly used in AfD, and one is the OPs point of controversial/close calls. If people wanna say he violated an essay then so be it, I was stating they didn't violate WP:NACD. WikiVirusC(talk) 18:04, 11 May 2023 (UTC)[reply]
    • Endorse I would agree with the way it was closed, because consensus is not a vote count and the evidence that the Act is "commonly known as the Don't Say Gay Bill" given in the discussion is actually quite clear; indeed, I am having trouble working out how those who voted "B" could calculate it otherwise. But, yes, it should probably have been closed by an admin. Black Kite (talk) 17:41, 11 May 2023 (UTC)[reply]
      I will note that people voting the other way made equally as cogent arguments regarding the matter. Closers aren't supposed to decide which argument is correct, they are supposed to summarize the argument, discounting votes only if they are unreasonable, not merely that they disagree with them. If a closer wants to decide that they agree with one side more than the other, they should vote and let someone else close. --Jayron32 17:51, 11 May 2023 (UTC)[reply]
    • I'd disagree, to be honest. Most of the "B" !voters appear to be claiming that it's only the critics of the bill that call it that, which is clearly not the case, as a quick Google search will tell you straight away. Someone in the discussion said it should be "which critics and many others have called ...", but that wasn't an option. But in the end, I'm not sure it actually matters since A is the status quo wording anyway. Black Kite (talk) 18:29, 11 May 2023 (UTC)[reply]
    • That's actually not true, if you count, only the second and fourth "B" voter said so. The bulk of "B" voters had far more nuanced and multifaceted rationals that I don't want to mischaracterize, but which you can see cite multiple evidences and policies and guidelines and give multifaceted explanations around phrasing. I see lots of references to NPOV and TONE based arguments like WP:IMPARTIAL, either by directly linking it, or explaining it as such, and others which look at the quality of the sources and not just the number. It's clear that many of the B voters had carefully considered, well thought out, and well explained rationales, and were not as you just characterized them. Most, indeed, made no such argument as you claim they did. --Jayron32 18:51, 11 May 2023 (UTC)[reply]
      Even when B !voters cited TONE, NPOV, or IMPARTIAL, they did so because they claimed supporters do not call the bill by its shorthand, which other editors explained is not implied by option A in the first place, or they did so because they claimed that only critics called it by its nickname, which other editors demonstrated with RS is not true. ––FormalDude (talk) 20:47, 11 May 2023 (UTC)[reply]
    Once again, disagreeing with a rationale does not mean you have the right to invalidate that rationale. The closer has the right to disagree, but that means they lose the right to close; they have an opinion and should express that opinion through a vote, not a closing statement. A closing statement summarizes, it does not hold opinions. --Jayron32 11:07, 12 May 2023 (UTC)[reply]
    • Redo the close and thank the closer for their effort. It has an important impactful structural problem/ oxymoron in the first sentence. In Wikipedia "Slightly in favor of" is called "no consensus" and it calls "slightly in favor of" a wp:consensus. Sincerely, North8000 (talk) 18:01, 11 May 2023 (UTC)[reply]
    • Endorse: So, just by the split (which is not exactly "even" BTW, there were several "either" votes, which in this case I'd count towards consensus on either option) I would ordinarily be calling for this to be overturned and re-closed by an admin. The problem with just citing the split here, though, is the same as what Black Kite said, namely that consensus is not a vote. There's an exhaustive list of sources at the bottom of the page, and it's clear from that list that many very strong sources don't use the "critics" phrasing. Even a non-admin closer has the right (and in fact, the duty) to assess the relative strength of the arguments rather than just counting heads. And that obviously goes some distance towards whether or not the close was close or not. Loki (talk) 19:34, 11 May 2023 (UTC)[reply]
    • (involved) Overturn or make it no consensus. Both sides have strong arguments, sourcing, and analysis from a closers perspective and the !vote count is to close to look at that considerably. The thing about making it no consensus is it will de facto be A, but it would also leave the door open for any other alternative options to be considered, which I think would be helpful. Iamreallygoodatcheckers talk 19:41, 11 May 2023 (UTC)[reply]
    • (involved) Overturn I also left FormalDude a message about this close. See User_talk:FormalDude#Improper_closure_on_Talk:Florida_Parental_Rights_in_Education_Act. A big problem here is that User:FormalDude's edit history suggests a strong POV on American Politics. This user has 300 edits at Talk:Donald Trump, which is more than double the number he has at any other page.[2] The second most edits is at Talk:Andy Ngo, again a hot-button article that is heavily tied to partisan politics. Several other articles in his top ten edited talk pages fit the same description. Then he comes along and closes this RfC, which is also deeply tied to US partisan politics, and in particular to likely Presidential candidate Ron DeSantis. Notice also the deep involvement in the RfC here[3], on whether or not Jan. 6 should be classified as a terrorist attack. Having an opinion is one thing, but per [4], USER:FormalDude contributed 24 diffs to the RfC [under two different names for the RfC, as it was re-titled in the middle], arguing that Jan. 6 should be classified as a terrorist attack, i.e.[5] Obviously, everyone is entitled to their opinion about that question, but the edits do not suggest that USER:FormalDude is a neutral observer to US partisan politics. Adoring nanny (talk) 20:52, 11 May 2023 (UTC)[reply]
      Yes, I edit American politics. Someone who is not familiar with American politics is probably not best suited to handle such a closure. The outcome of the discussion to include "Category:Terrorist incidents in the United States in 2021" to January 6 United States Capitol attack ended up with consensus to include, which is what I supported. Not sure how that makes me non-neutral to U.S. politics (and I might add that that's from December 2021). You're acting like I have a history of going against consensus in American political topics, but I think a thorough search of our editing histories would reveal you are much more consistently at odds with consensuses in the topic area than I am. ––FormalDude (talk) 21:04, 11 May 2023 (UTC)[reply]
      I am not suited to such closures either. Hence I don't make them. Adoring nanny (talk) 21:18, 11 May 2023 (UTC)[reply]
      If you're not suited to close them, what makes you think you are suited to review the closures? ––FormalDude (talk) 21:25, 11 May 2023 (UTC)[reply]
      To the best of my knowledge, it is standard practice for involved editors to participate in closure reviews. I did note my involvement in my initial response. Obviously I won't close this discussion, either. Am I missing something? Adoring nanny (talk) 00:34, 12 May 2023 (UTC)[reply]
    • Endorse as it appears to be a good measure of the consensus of the discussion, admin or not is irrelevant. This challenge is just "I didn't like which way it went". Zaathras (talk) 21:00, 11 May 2023 (UTC)[reply]
    • Vacate - and issue a warning to all of the combatants in the American politics topic area, and based on the various noticeboard complaints and topic area contributions by and about FormalDude I think it is safe to consider him one of those combatants, to stay away from closing any discussions in the topic area. nableezy - 21:09, 11 May 2023 (UTC)[reply]
    • Overturn: I tend to agree with FormalDude's thinking but with such a basically an even split and reasoned arguments on both sides I can't see calling this one way or the other. If I had to pick a one or the other I would agree with the closing but I think it's just too far into the no-consensus category to close with a decision one way or the other.
      Springee (talk) 23:20, 11 May 2023 (UTC)[reply]
    • (Involved) Endorse - I've been going back and forth on whether I should comment here, as I challenged an earlier closure of this same RfC, on involved grounds. I'm still not sure if my comment here will help, or be seen as improper. In the case of the earlier closure, the editor who closed the discussion was one who had both contributed to the RfC and extensively edited both the article and talk page, and as a result their status with respect to involvement was clear. However for this closure, prior to closing the RfC FormalDude had never edited the article nor its talk page. Nor has he edited Ron DeSantis (and only one minor edit to DeSantis' talk page), Government of Florida or its talk page, Florida Legislature or its talk page, Florida Senate or its talk page, and Florida House of Representatives or its talk page. As far as I can tell, FormalDude is completely uninvolved with respect to Floridian politics.
      However, editors here are saying that FormalDude is involved, because of his broader contributions to the American politics content area as a whole. While I understand that involvement is typically considered broadly, are we really wanting to consider it this broadly? I worry that by construing it so broadly as to consider any/all edits elsewhere in the topic area, that experienced closers with background knowledge of the topic but who have not directly edited the article or closely related ones will be unable to close discussions such as the RfC we're discussing. Sideswipe9th (talk) 02:41, 12 May 2023 (UTC)[reply]
    • Endorse (uninvolved), largely per Sideswipe. This discussion involved two contentious topic areas; US Politics and Gender and Sexuality. Editing within these broad topic areas doesn't make an editor involved in specific disputes, and no evidence has been provided that FormalDude has edited in relation to this specific dispute. BilledMammal (talk) 02:45, 12 May 2023 (UTC)[reply]
    • overturn. there is no consensus. close it as no consensus. lettherebedarklight晚安 13:06, 12 May 2023 (UTC)[reply]

    Urgent Appeal to Reconsider My Account Block on Wikipedia: Unjustly Accused of Sock Puppetry

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


    Dear Wikipedia administrators,

    I am writing to appeal the decision to block my account on Wikipedia, as I have not received any response to my previous request for unblocking. In my previous request, I stated that I have been unfairly connected to Jebli18, a sock puppet account, and I have not engaged in any inappropriate behavior on Wikipedia. Despite providing evidence to support my claim, I have not received any response from the administrators.

    As a long-standing member of the Wikipedia community, I have always been dedicated to upholding the platform's guidelines and policies. My contributions have been recognized by the community, and I have received positive feedback from other users. I have contributed to Wikipedia with the utmost good faith, and it is disheartening to see that my account has been blocked based on a false accusation.

    I understand that Wikipedia administrators have a responsibility to maintain the platform's integrity and quality, but I firmly believe that my account has been unfairly blocked without sufficient evidence. I respectfully request that my account be unblocked so that I can continue to contribute constructively to the Wikipedia community.

    I am committed to following all of Wikipedia's guidelines and policies and contributing in a positive and constructive manner. I believe that my previous contributions demonstrate my commitment to the community and my desire to contribute to the collective knowledge base.

    I appreciate your time and consideration in this matter, and I look forward to a prompt response.

    Sincerely,

    @MoroccanEd

    Here is my previous request : MoroccanEd Request 103.117.254.8 (talk) 12:34, 12 May 2023 (UTC)[reply]

    You have an open request on your talk page. An admin will review and decide to unblock you there. RickinBaltimore (talk) 12:35, 12 May 2023 (UTC)[reply]
    They need more than a local unblock - at this point they're globally locked, and will be unable to log into that account. Girth Summit (blether) 13:05, 12 May 2023 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.