Your source looks fine, but I am here inclined to let someone else deal with the work of creating the article; this week I already had one guy on the internet post a giant angry screed under my real name, on account of my opening a thread on a noticeboard tangentially related to another thread that mentioned a right-wing politician earlier this week. In that case, the administration of the message board was kind enough to hide the thread from public view after a couple days of arguing, but I do not currently feel like futzing around and finding out in re creating a page with the title "glownigger". jp×g🗯️21:56, 11 May 2024 (UTC)[reply]
Hi, please can an administrator create a redirect from Deji Olatunji to KSI#ComedyShortsGamer, as an {{R from relative}}? The title is protected in two separate ways (matching an entry on the title blacklist and also being individually salted); however, there is information regarding him at this anchor in the article, and an RFD discussion for Comedy Shorts Gamer (entertainer) was recently closed askeep based on this.
The block reason was "WP:ECR violations, canvassing and, (vile) personal attacks", but the reason for TPA removal is unstated and appears to be along the lines of "just... just too frustrating to deal with". No additional ECR violations, canvassing, or personal attacks happened after the block. They just kept ignoring advice and saying and doing clueless things. Normally I'd say that TPA removal was a bit bitey, and favor restoring it, but in this particular case... I'd probably have gotten frustrated too. After seeing the UTRS request, I don't have high hopes for an unblock. They just don't seem to be understanding anything. Maybe if one admin took time, and other admins and editors left it alone, some progress could be made. But who would be up for doing that with this editor, and how would you even keep kibitzers out? What area would this editor even want to edit until they became extended confirmed? Floquenbeam (talk) 20:08, 9 May 2024 (UTC)[reply]
I have no objections if people want to restore talk page access. I strongly oppose unblocking, though. Egregious personal attacks, blaming others, etc. Reading through the UTRS request, I don't even see Peace Love10 retracting their personal attack. They appear to believe it was accurate albeit rude, they just accept that if they make another such attack, they'd be blocked again. I don't believe this user would be a net positive. Again, though, no objections if people want to restore talk page access. Note that ScottishFinnishRadish is the original blocking admin. --Yamla (talk) 20:20, 9 May 2024 (UTC)[reply]
Restoring TPA, at least temporarily, is probably okay, but reading the UTRS appeal, I think it may be pointless. I wouldn't unblock based on that appeal. Seems to be a lack of clue, and a lack of effort. Dennis Brown - 2¢11:22, 12 May 2024 (UTC)[reply]
Annnnnd as user claims to need a translator to edit in English, I advised them to edit in a language for which the do not need a translator. As I already recused due to my inability to be objective, it would be best if someone else decide on bringing over what we've got or closing with the sandard offer. Best.-- Deepfriedokra (talk) 11:49, 12 May 2024 (UTC)[reply]
I'm not saying the egregious attacks don't exist, but it's hard to assess when they are all blocked from view. Likewise, the talk page appears to be filled with "Wait, what did I do?" kinds of comments. While that is common for people who are disruptive, it's also common for noobs. I'm not at all interested in unblocking without a clear rationale, but I'd also like to know more details. I understand redacting some things, but I find it unrealistic for "us commoners" to make an intelligent decision without the facts. Could we at least be vague about what was said? "removed profane remarks about another user IAW WP:BLP" or "redacted libelous remarks about user:ABC"?
Sorry for the confusion. I could have been clearer. I needed more admins to look at that ticket and make a decision. Then I saw where they were using a translator which misstated what they were trying to say, and that's why they were in the mess they're in. Which mooted the whole question. -- Deepfriedokra (talk) 19:51, 13 May 2024 (UTC)[reply]
I have declined Peace Love10's unblock request on the basis of their stated lack of English proficiency, although I did tell them that I would copy a future appeal to AE if they are able to constructively edit a different language Wikipedia. As such, there isn't any reason to reinstate their talk page access at this time. Jake Wartenberg (talk) 18:44, 13 May 2024 (UTC)[reply]
This user is known for creating badly spelled "warning templates" and editing articles related to Windows. In addition, they keep evading their block by making sockpuppets; feels like there's a new one every business day. Does this warrant a ban and/or an LTA case? thetechie@enwiki: ~/talk/$23:14, 13 May 2024 (UTC)[reply]
Ban is probably warranted per WP:3X, but there would probably need to be lots and lots of sockpuppets with systematic abuse going on for a while to warrant an LTA case (think something like this or this). Not saying it's impossible, but only make an LTA case as a last resort. —Matrix(!) {user - talk? - uselesscontributions} 15:58, 14 May 2024 (UTC)[reply]
I agree that this is a weird closure that should be left to a more experienced editor. It should therefore be overturned. (Disclaimer: I'm involved in the discussion.) LilianaUwU(talk / contributions)04:20, 11 May 2024 (UTC)[reply]
Reopen, Uninvolved editor: Charcoal feather's closure looks premature - the fact they edit conflicted proves that they did not wait for the discussion to run its full course. There were still new comments coming in that could have influenced the decision. The fact that they're an "inexperienced" editor (I wouldn't class 700 edits as inexperienced but ok) doesn't really matter much to be honest, but the closure should have only been done after few or no new meaningful comments were coming in (especially for such a divided discussion). —Matrix(!) {user - talk? - uselesscontributions} 16:31, 11 May 2024 (UTC)[reply]
Facepalm I read all the comments in the discussion with the month "April" as "May"... reevaluating my position with the new information, the closure actually looks fine, I see a rough consensus (13 to 10) for present tense and I doubt the consensus would have changed much more with extra time. I don't see anything that contravenes WP:RFCCLOSE. Endorse, —Matrix(!) {user - talk? - uselesscontributions} 17:00, 11 May 2024 (UTC)[reply]
13/10 is more in the "no consensus" range. Absent a detailed closing statement/rationale for weighing some comments differently than others, the closure seems bad. Jake Wartenberg (talk) 21:10, 13 May 2024 (UTC)[reply]
IMO the closure looks OK. At most one might argue that it borders on "no consensus". But if contested, this is not the right venue. North8000 (talk) 21:23, 13 May 2024 (UTC)[reply]
Hi, I am user:Lazy-restless ban ID: #17, I want to be unblocked and agree to follow what authority commands me to do. What should I do to be unblocked, please help me. See my contribution, previously I did a lot of good edits and created a number of good articles and templates. I want to contribute more. I believe that I can do a lot of good positive conteibution to wikipedia. 202.134.10.131 (talk) 17:15, 14 May 2024 (UTC)[reply]
Firstly, don't use any IPs or users as sockpuppets (as you have done here) to edit on the English Wikipedia for 6 months, then you can follow WP:SO to potentially get unblocked. —Matrix(!) {user - talk? - uselesscontributions} 17:27, 14 May 2024 (UTC)[reply]
I find it mildly humorous that you lifted the languagebeen treading very close to a full block from the discussion of your own partial block. Also, you have failed to notify the user in question as required in the large red box at the top of this page. Also, two edits you don't agree with, one three days ago and the other a month ago, doesn't seem like it it needs administrative intervention. Just Step Sidewaysfrom this world ..... today19:33, 14 May 2024 (UTC)[reply]
Requesting to Protect page Wikipedia Page - Kailash Hospital
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Recently someone with the user name @2409:40d0:37:1091:244c:44ff:fe74:7d64 edited out wikipedia page - Kailash Hospital by changing founder name from Dr. Mahesh Sharma to Gujjar. So I request you to kindly apply semi protection on this wikipage so that new user can't edit or vandalism this page. Shubh84 (talk) 10:41, 15 May 2024 (UTC)[reply]
Shubh84 Page protection is requested at WP:RFPP. One edit is not necessarily enough to warrant protection, there must be a demonstratable, ongoing problem with vandalism or disruption to warrant protection, especially if less broad measures like warnings and blocks of users themselves are ineffective. 331dot (talk) 10:43, 15 May 2024 (UTC)[reply]
user: 2409:40d0:37:1091:244c:44ff:fe74:7d64, did changed founder name in infobox in Kailash Hospital's Wikipedia page, also remove name from content body of the article. This user also make another changes in their founder's wikipedia page as well Dr. Mahesh Shama infobox, by adding abusive word "randi" or "rand" in spouse name & in children name. If you search these words meaning in country like India you will find out how much abusive these words.
No, that might be evidence to block the IP, but not protecting the article from editing, which could affect legitimate editors. 331dot (talk) 11:12, 15 May 2024 (UTC)[reply]
Pages aren't normally protected because of a single instance of vandalism; it only happens when there's long-term disruption. Also page protection requests should go to WP:RPP (though, again, it'd get declined for this reason). — Czello(music)10:43, 15 May 2024 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Reasoning: The following is copied and modified from my post at Chetsford's talk page. I think that Chetsford's close was generally correct, but I think that this aspect is an incorrect assessment of consensus:A few editors suggested that, regardless of outcome, it should not be used for WP:BLPs. No direct reasoning was presented for that, however, some indirect reference to our policies could be divined within the greater context of the remarks of those editors and these suggestions were not really rebutted. I searched the RfC and "BLP" was used six times in the discussion. Only two of those mentions are in relation to the reliability of the source, and as Chetsford noted, neither provided anydirect reasoning:
In addition, based on some of the past statements linked, a use for BLP or politicised situations within the fog or war would be very reckless at best.
Yeah, I have very little faith in their editorial review which go beyond WP:BIAS and regularly WP:Fringe. At best, they really shouldn’t be used for anything related to BLP, Russia and Israel, at worst (and IMO this part is most likely) a full depreciation may be in order.
The onlyindirect reference to policy is to BIAS (as FRINGE is a guideline), and Chetsford discounted that argument in another part of the close. I can't reallydivine[] what other policies these editors may or may not have been thinking about. I'm not sure whatpast statements the first commenter is thinking about, and without more reasoning, I wouldn't say that this single argument is strong enough to establish a consensus that Mondoweiss should not be used for BLPs just because nobody happened to rebut it in a long discussion. voorts (talk/contributions) 02:17, 16 April 2024 (UTC)[reply]
Uninvolved
Endorse closeAmend While the specifics of BLPs weren't addressed in-depth, it's a reasonable addendum for clarity. They can be used but people should be careful with each individual article...not sure why that's not a blanket statement for every source on Wikipedia. For example, the NYT has published some egregious "journalism", but that doesn't mean it's always wrong on the basic facts. Every source should be evaluated for accuracy on its merits. If I say "Person AB said in an op-ed '<insert quote here'" and then cite it, there's very little reason to doubt that statement is true, but quoting it for purposes of establishing it as something that's true is inappropriate without additional verification. Buffs (talk) 14:26, 17 April 2024 (UTC)[reply]
Amended: This sounds like a WPian hearing what they want to hear. There isn't a need to add additional steps beyond what we normally do if people are going to abuse that to exclude the contributions of others. I'd prefer to keep it as-is, but I certainly can see that point. Buffs (talk) 16:22, 18 April 2024 (UTC)[reply]
Amend Remove the BLP clarification: 1) Regardless of the sources' reliability, we always them with great caution for biographies of living people. 2) No valid reason was given for why Mondoweiss should be treated differently from the other RS. 3) Such an unneeded clarification can easily be misconstrued to mean that Mondoweiss shouldn't be used for BLP. Just this week, one of the RfC participants used the close statement to claim thatwe should avoid using Mondoweiss for BLP. Obviously, it ended up in RSN again. M.Bitton (talk) 16:30, 17 April 2024 (UTC)[reply]
Amend to remove the statement about BLPs. If only two editors made an unsupported assertion and nobody else discussed it, then it isn't a valid part of the consensus. I'm all for interpreting arguments to try and pull a consensus out of the flames where it isn't obvious, but "divining within the greater context" in this manner is a left-field supervote and should be removed. The rest of the closure is reasonable. The WordsmithTalk to me18:19, 17 April 2024 (UTC)[reply]
Amend per M.Bitton and Wordsmith. We already treat BLP with caution, and this issue was not discussed enough to reach consensus. If needed, a new discussion on how to use MW with regard to BLP can be made. Meanwhile, I’m wary of using the ‘average’ value of 2.6 to conclude that option 3 should be reached. Note that since option 2 is essentially the middle ground, option 1 and 3 have the same weight, but option 4 has twice the weight of option 1 when skewing option 2. This doesn’t seem very fair, and then rounding 2.6 to 3 because of this is increasing the unfairness, leading to essentially 13 editors overruling 21 editors. starship.paint (RUN)03:05, 23 April 2024 (UTC)[reply]
Two minor points of clarification: I have zero problem with amending per above and, while I can't -- objectively -- read the RfC that way, I would personally be glad to see this outcome. That said, I am concerned that some editors are reading the aggressive and misinformed arguments of two relatively new editors on the "anti-" MW side who have attempted, very poorly, to summarize my close and assuming those summaries accurately represent the close. The only closing statements I wrote are this one and this explanatory comment, both of which are much more modest than the way in which two editors are summarizing them to make sweeping changes across multiple articles. To avoid the further spread of this misinformation, I would ask, as a personal favor, that editors attempting to describe my close (regardless of where you land on it) reflect only on the source material, and not the apocrypha it's spawned. To wit:
"I’m wary of using the ‘average’ value of 2.6" The "average" of 2.6 was never used for anything (and, yes, I realize the incidental appearance of this meaningless number in the close has been fixated upon by the aforementioned editors to make major changes to articles). As per the text of the close rationale, the number 2.6 was simply noted as "indicative but not definitive as per WP:NOTAVOTE" and then immediately discarded as "not clearly learning toward either option" before the narrative analysis began.
"to conclude that option 3 should be reached" The RfC close reached no such conclusion in any dimension of time or space; in this reality or any parallel reality that the mind of man can conceive or imagine. It stated that no "consensus as to its underlying reliability" emerged which, if anything at all, was a "2" close (but, actually, no consensus).
To summarize, this was a "no consensus" close with a relatively modest (and not proscriptive) BLP corollary described by Buffs in this first (now stricken) comment. The fact my loquacious reasoning, intended to promote transparency, instead provided an opening to wedge in battleground behavior is beyond both my control and mandate (RfC closers are not RfC enforcers). Chetsford (talk) 23:58, 23 April 2024 (UTC)[reply]
@Chetsford: - perhaps there has been a misunderstanding, you quoted from me, but I was not referring to your RfC close. I was referring to the below analysis by FortunateSons. I apologise for my vagueness having caused confusion. starship.paint (RUN)08:54, 24 April 2024 (UTC)[reply]
Involved
I've archived my discussion with Voorts here for ease of review (versus diffs). For what it's worth, considering the contentious topic area involved, I am in full agreement with Voorts that review of the close is appropriate. Chetsford (talk) 07:06, 16 April 2024 (UTC)[reply]
Amend close to read "and that it should either not be used at all — or used with great caution for biographies of living people." I don't think that the relative silence on the issue should have been construed as agreement with the two editors raising that specific, there was a lot else going on in the discussion besides that, especially since one of those editors appears to have construed the close as a license to remove citations for BLPs. Selfstudier (talk) 15:33, 17 April 2024 (UTC)[reply]
Amend close to 3 (Gunrel), optionally clarify the statement about BLP requirements per the qualifiers suggested by Chetsfordper the arguments made by @Chess and @BilledMammal, which were not sufficiently addressed; also using the votes as an indicator. Acknowledging that I advanced the BLP arguments poorly (and thanking @Chetsford for his generally accurate deciphering of what I meant), I would suggest the following, in the spirit of his comment made here, @Bobfrombrockleyhere and as a compromise: used with great caution for biographies of living (and recently deceased) people, and not to be used in cases of (a) for statements that, if proved false, would be legally defamatory; (b) for extraordinary claims (c) for analytical statements about the person; (d) for quotes and facts the accuracy of which is contested by RS or the subject him/herself. In addition and as a partial clarification, perhaps e) should be content marked as activism and similar would be appropriate. FortunateSons (talk) 08:25, 18 April 2024 (UTC)[reply]
You're going to need to bolster your opinion more than "we should do what I want", when support for #2 had ~6.5:1 support over yours. This is not the place to relitigate this RfC, IMHO. Buffs (talk) 16:30, 18 April 2024 (UTC)[reply]
I‘m pretty sure you’re off on the math, as I voted 4 (which obviously endorses 3 over 2). That option obviously does not have consensus (and just for the sake of clarity, removal of problematic BLP uses is not backdoor deprecation, the overwhelming majority of MW uses are non-BLP or unproblematic). The straight vote count (as stated by Chetsford) has the average at 2.6, and of the counted votes, 14 votes included at least 3 (including 2 or 3), while 21 did not, of which an overwhelming amount were 3 or lower (please check my math).
I was unaware that we are not supposed to reference specific points when requesting a reassessment of the outcome, and have struck that part, except in context of the phrasing to avoid (light) plagiarism. Thanks for making me aware, this is one of my first contributions to such a noticeboard :) FortunateSons (talk) 17:20, 18 April 2024 (UTC)[reply]
When giving a list of options (1. Action A 2. Action B 3. Action C 4. Action D and 5. Action E), saying "the average is 2.6 so we should choose option 3" is a horrible misunderstanding of statistics. You are heavily weighting all other actions other than #1 (Example, 20 people !vote 1, 2 people !vote 2, and 3 people !vote 5, the "average" is 2 despite an overwhelming preponderance of people !voting 1...in other words, a 5 is worth 5x a 1). Rounding up only further exacerbates the issue. Buffs (talk) 16:38, 19 April 2024 (UTC)[reply]
Second attempt at a more policy-compliant argument, please correct me if this one is also wrong:
The relevant arguments regarding BLP usage were not addressed, and similar arguments where not fully rebuffed in general; therefore, the section regarding BLP should remain as is, or be alternatively clarified while remaining in the spirit of discussion and close.
Regarding the status of the entire source, I believe that the arguments made by those voting for „higher than 2“ should have led to a close of 3, and respectfully request that it is amended (as well). FortunateSons (talk) 17:31, 18 April 2024 (UTC)[reply]
Amend per The Wordsmith. My own views on the source aside, the issue of BLP use was barely discussed - there was no consensus on it one way or another, so to assert one in the closure seems odd. TheKip19:38, 23 April 2024 (UTC)[reply]
I don't object to the amendment that is being proposed here, because I think it goes without saying that any source where there are serious reliability concerns should be used with extreme caution in BLPs, especially where content is potentially defamatory. While no consensus was reached, given that 15 out of 36 !votes (I think) were for an option higher than 2 and only one editor considered option 1, this is obviously a source with serious reliability concerns. My only worry is that editors will take this amendment as permission not to use extreme caution with the source on BLPs or, worse, that this source has somehow been cleared for use in BLPs, so I hope that editors supporting this amendment will be vigilant in ensuring that we do not use this poor source inappropriately in BLPs. BobFromBrockley (talk) 11:00, 30 April 2024 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Discussion was only open for two days and it involved a DYK BLP complaint and AndyTheGrump's uncivil remarks referring to DYK editors as idiots. There were two simultaneous unrelated threads about ATG's incivility at ANI but discussion in this thread was not concluded. In fact just hours ago the thread was active. I think the JSS close was involved because of their critical offline commentary and appearance of a friendship with ATG on an offline site that refers to DYK as a clusterfuck.
JSS and ATG are both very involved in criticism of DYK offline in fact JSS posted there minutes ago.
I think there is more than just the appearance of a conflict and cutting off an active discussion is not a good idea. I believe that the thread should be allowed to continue and the JSS close should be backed out. Lightburst (talk) 00:31, 15 May 2024 (UTC)[reply]
if you are going to claim 'critical offline commentary' as evidence, please provide the necessary link. I don't have the faintest idea what you are referring to, making it rather difficult to respond... AndyTheGrump (talk) 00:35, 15 May 2024 (UTC)[reply]
Oh Jesus. There was clearly no consensus for a block, nor was any coming. Belonging to the same forum doesn't trigger being involved or mean there's some deeper alliance or I wouldn't have warned Andy that I was going to block him if it happened again. ScottishFinnishRadish (talk) 01:12, 15 May 2024 (UTC)[reply]
ScottishFinnishRadish In my experience we do not close threads that are very active with editor participation. It only serves to create the appearance of a conflict when the closer and the subject of the thread are yucking it up about the DYK clusterfuck on WO. Nobody needs to pretend they do not know how to find that rubbish. Lightburst (talk) 01:22, 15 May 2024 (UTC)[reply]
For the record, I haven't posted anything on the WPO forum for over a month. Not in the clusterfuck thread, not anywhere. Still, never mind facts if they are going to get in the way of a good honest witch-hunt... AndyTheGrump (talk) 01:37, 15 May 2024 (UTC)[reply]
There is no witch hunt. JSS/Beeblebrox said this at WO,Andy is usually only this rude when he also happens to be editorially correct. Consenesus is not on his side here, clearly, so now that factor is out the window and a number of folks have pretty clearly been waiting for the opportunity. Well the community was cut off by JSS. My own experience at ANI lasted for two weeks, yours was less than two days. WP:DUCK comes to mind. Lightburst (talk) 01:50, 15 May 2024 (UTC)[reply]
If you are unsure if something is a duck or not, you could always see if it floats. A very old technique, useful in other circumstances too, I believe... AndyTheGrump (talk) 02:09, 15 May 2024 (UTC)[reply]
I'm objecting to allegations entirely unaccompanied by the 'links and diffs' noted as a requirement at the top of this page. I was under the impression that failure to provide such links was considered potentially sanctionable, even when the charge seems to be heresy. Or sharing opinions with somebody about something. Which is what the 'reasoning' behind this thread amounts to. AndyTheGrump (talk) 02:04, 15 May 2024 (UTC)[reply]
I favored a block, but time passed and there wasn't consensus for it. I don't object to the closure, especially given continuing discussion of the actual issue. Mackensen(talk)01:48, 15 May 2024 (UTC)[reply]
The close didn't tell everyone to shut up, it pointed to where a discussion on the merits is already taking place, in the DYK space, which seems appropriate. As for being chummy on WPO, I don't know that agreeing sometimes is chummy. I post there sometimes as well, many admins and editors do, often when someone makes a false claim about them. That doesn't mean much of anything and it certainly doesn't trigger WP:involved. The only reason to continue the discussion at ANI was if there was a snowball's chance that Andy was going to get sanctioned, or there was more evidence, or something was going to be implemented or change somehow. There was a failed poll for a block, there was much discussion, but nothing more was likely to come of it, and Andy saw that many people found him to be too rude. Another day or five wouldn't have made a difference. At that point, moving to focus on the DYK merits isn't unreasonable and likely a good idea if the goal is to solve the issues at DYK. Not every ANI discussion results in sanctions, or clean understandings, or even a desirable outcome. Dennis Brown - 2¢03:22, 15 May 2024 (UTC)[reply]
Thanks for the explanation of how ANI works for Andy. It was not so easy for me or many others. You saidAndy saw that many people found him to be too rude... seriously? That was new information for him? He called me and my colleagues idiots and when everyone begged him to walk it back he refused. As you know, often there are other proposals started when one fails at ANI but JSS arrested the process. I will take a break now DB, I do not have enough street cred for ANI or AN. Lightburst (talk) 03:50, 15 May 2024 (UTC)[reply]
It's not about street cred, it's about realistic expectations. Once you see it's not going anywhere, you're just beating a dead horse.. Farmer Brown - 2¢ (alt: Dennis Brown) 05:15, 15 May 2024 (UTC)[reply]
Once again, two more editors' real names are posted on that site for no reason other than they disagreed with the regulars of that site. JSS since you had so much to say on that site about this ANI thread before you closed it, are you now going to say something to your friends there about it this time, or will you stay quiet like you did the previous times? Is this the fifth time I've complained to you about the exact same thing, or the tenth or twentieth? Each time it's a different editor being harassed, I've lost count now.
To all of you who tolerate this, who chit chat regularly with the people that harass editors you disagree with by posting their RL info publicly online, are you going to wait until one of those freaks shows up at one of our doorsteps before you realize what fire you're playing with over there? Levivich (talk) 13:53, 15 May 2024 (UTC)[reply]
I closed the section on blocking Andy for 24 hours because it seemed clear that was not going to happen, there was neither a consensus to do so nor ongoing disruption of the same type coming from Andy. I closed the thread on DYK because it was not an active discussion any more, the most recent timestamp at that time being 2 days old, and discussion had moved elsewhere. I don't see anyone buying Lightburst's argument that these actions were somehow a violation of WP:INVOLVED, so I feel like we're done here. I'm not interested in having the "WPO is evil and you are evil for particpating there" argument. Just Step Sidewaysfrom this world ..... today16:42, 15 May 2024 (UTC)[reply]
I do not think I could be confused for someone with a lot of sympathy for WPO, but that thread about Andy wasn't going to go anywhere. We don't don't really have a way to deal with "light incivility" by experienced users beyond people getting their objections out of their system at ANI and perhaps closing with an umpteenth tsk-tsk. For the record, I do agree that JSS is involved with regard to AndyTheGrump. The two aren't just two people who happen to use the same website -- they're two of the most active users on a site about Wikipedia. This board would (and should) lose its collective mind if one of the most active members of, say, a Wikimedia chapter jumped in to close a discussion about another of the most active members of that chapter. But the fact that JSS was involved doesn't make it the wrong closure -- we typically allow for a little leeway for relatively uncontroversial involved actions. I think that applies here. — Rhododendritestalk \\ 17:15, 15 May 2024 (UTC)[reply]
I backed out the closure. SN prematurely closed a discussion about premature closures. After they ripped DYK for a BLP issue that they helped cause by asking for a negative hook. You cannot make this up. Lightburst (talk) 18:27, 15 May 2024 (UTC)[reply]
@Lightburst: I'll be reverting your revert, of course. Basically, if you want to accuse me of being INVOLVED, in your usual misunderstanding of the most basic policies and guidelines, then you need to buck up or ship out. I understand you need validation, but it should not be at other editors' expense: not just the parties you have tried to incriminate, but those whose time you continue to waste with this foolish posturing.The only irony here, LB, is calling on "the professionals"; you wouldn't know professionalism if it poked you in the eye. ——Serial Number 5412918:33, 15 May 2024 (UTC)[reply]
You're involved because you're a regular poster there, including posting in the thread over there about this thread here. Don't throw your lot in with the crowd over there, SN, you're better than that. Levivich (talk) 18:36, 15 May 2024 (UTC)[reply]
@ScottishFinnishRadish: you are proving to me everyday why my oppose at your RFA was spot on. Nice of you to shit on my concern with your Onlyfans bullshit and a sarcastic image. Maybe go work on your shitflow diagram and take it to FA. Lightburst (talk) 18:56, 15 May 2024 (UTC)[reply]
During the development of Shooting of Robert Fico, @Lukt64 emptied its contents and pasted it into their redirect Attempted assassination of Robert Fico which is now the focus of editing. It appears to be undiscussed whereas the user claims it was discussed. @Zzuuzz is the editor that has been reverting my edits to restore the original title and its history.
Far as I know, a copy+paste move isn't part of proper editing (then again I did it), so I'm requesting it to be transferred over to the old title without another admin running into conflict with me while the article is still in early development stage. Dora the Axe-plorer (explore) 20:54, 15 May 2024 (UTC)[reply]
I'm not going to have the time today, or possibly tomorrow, to deal with this, so I defer everything to other admins :) I've already placed an attribution template on Talk:Attempted assassination of Robert Fico if you want some details. I see some scope for a round-robin and histmerge, before another move, if that's what's deemed appropriate. Or some variation... And someone needs to keep telling people to stop copypasting. -- zzuuzz(talk)21:00, 15 May 2024 (UTC)[reply]
I understand the clean up now is probably going to be messy considering the copy + pasted article has over 160 revisions already. Kindly requesting further admin inputs Dora the Axe-plorer (explore) 21:38, 15 May 2024 (UTC)[reply]
Pinging some recently active admins if I can get them on board, apologies and thank you in advance for putting up with this if you will. I'm not optimistic about what can be done, but better to ask the experienced @Bearcat @Cbl62 @PFHLai @SuperMarioMan @Wbm1058 @Liz
Thanks. The earlier, parallel history is now in the page history of the 2024 Fico assessination attempt redirect. – wbm1058 (talk) 23:01, 15 May 2024 (UTC)[reply]
Second opinion appreciated
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
...on User talk:GoneWithThePuffery, where I just dropped a "final warning" for harassment. Puffery has a habit of making things personal already, as their edit history shows, and when they got falsely accused of socking (see Wikipedia:Sockpuppet investigations/GoneWithThePuffery) and Talk:Snell's law, they kind of exploded. I don't know about "unbelievable muppet" and "piss off very quickly"--muppet isn't much of an insult, and "fuck off" isn't blockable so "piss off" wouldn't be either, but please see what I just reverted on Talk:Snell's law: that's just over the top. The editor is likely right about content (I agree with them so they must be right), and they're highly educated and smart, but their attitude is not yet right for a collaborative project. All that to say, eh, I hope my "final warning" isn't too much. Drmies (talk) 23:33, 14 May 2024 (UTC)[reply]
I have been in communication with that user on my user talk page. In my most recent comment, I gave them some blunt advice: if they aren't on their best behaviour toward other editors, they might find themselves blocked. I also put a similar reminder to all editors to focus on content and not contributors. And I hope the dogs are okay and the bears stay away, but as far as that talk page goes, the proverbial horse is long gone.(And I "wintered over" near Chicago with a dachshund. I had to shovel snow for dogs to go outside to take care of business, and the house didn't have a doggie door, so I had to go out with them too.) —C.Fred (talk) 01:11, 15 May 2024 (UTC)[reply]
@Drmies, @C.Fred, @ScottishFinnishRadish, I see here a pattern that I saw so many times earlier on Wikipedia: other users misbehaving and then complaining after they receive a retort. The matter is very simple: I made some perfectly sensible edits on the page of Snell's law and after that an edit war broke out where I had no part in at all. When I went to the page after a week or so, I saw that all my edits had been reverted. On the talk page I asked why, and immediately I was accused of "evading a block" (I wasn't even blocked...), "sock puppetry" and "not contributing to Wikipedia". When one of the users unjustly accused me of sock puppetry on my talk page, I told him to "piss off". And now I'm getting the warning? This is the world upside down!
@Drmies, it's really absurd what you are doing here. You know perfectly well what happened and which users are to blame for this situation. You talk about harassment. Seriously, what are you talking about? This guy came to my talk page, to accuse me of something I didn't do, and now I'm harassing someone? You must be joking. There are now two users specifically on the page of Snell's law, who are consistently engaged in uncivil behavior and are avoiding any form of discussion. But that's apparently no problem? GoneWithThePuffery (talk) 14:05, 15 May 2024 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
User Vif12vf disruptive edits
Could someone please have a look at the nonsensical reversions of user Vif12vf? For example, he keeps on adding content about Nuevo Movimiento al Socialismo on the page of Movimiento al Socialismo (Argentina), even though these are different parties. The Spanish Wikipedia makes this very clear (https://es.wikipedia.org/wiki/Nuevo_Movimiento_al_Socialismo). Further, he continues with removing content in the lead of the page of the Socialist Workers' Party (Argentina), even though the sources are given in the text, its four national deputies are well known, and the infobox states that the party has four national deputies as well. And so on and so forth.
Expansions with content from other-language versions of wikipedia still has to be accompanied with the actual sources used, and wikipedia itself cannot be used as a source! Vif12vf/Tiberius (talk) 16:43, 16 May 2024 (UTC)[reply]
@Floquenbeam If you are referring to the notion from MAS, then this is the case with most of that stub, which generally speaking hardly appears to be notable enough to have an article in the first place! Vif12vf/Tiberius (talk) 16:50, 16 May 2024 (UTC)[reply]
I'm referring to the fact that you edit-warred to keep an unsourced sentence in the article, while demanding that the IP editor provide a source to remove it. Not really how it works. Also, your first revert you treated like the IP was vandalising, when they clearly provided a reason. You've had a previous 3 month block for edit warring a few years ago, and sweveral edit warring blocks in the past. Were I you, I would take accusations of edit warring seriously, and back away from the edge, before you find yourself banned, or with a 1RR limitation, or something. The talk page is open, as is AFD. What is not open is to disregard a good faith editor because they are editing with an IP, and edit warring. Floquenbeam (talk) 16:57, 16 May 2024 (UTC)[reply]
At this point, I would suggest adding a {{dubious}} tag there, too, and open a section of that talk page. It takes about 1 minute. 2 if you're plodding like me. When there is no obvious-to-everyone right or wrong version, we usually default to the status quo ante until it's discussed. The discussion doesn't need to be long and protracted, we just need to see if there's a consensus for one or the other. Or, optimally, one of you actually changes the other's mind. Floquenbeam (talk) 17:29, 16 May 2024 (UTC)[reply]
My advice would be to just let it go for a day. Technically you'd be at 3 reverts on that page too. Don't risk an edit warring block just when things seem to be cooling down. Also, a final note, the use of "vandalism" to describe edits that you disagree with, but were intended to be good edits, is really a red flag to many people. Don't risk derailing a discussion by calling someone who annoys you a vandal. It backfires every time. Floquenbeam (talk) 17:44, 16 May 2024 (UTC)[reply]
Understand. I thought that Vif12vf had misunderstood or something, but then he began to spam my IP-page with warnings and began demanding sources for the removal of one unsourced sentence (as you also have noted above). That doesn't makes sense at all. Maybe this doesn't constitute vandalism but it's disingenuous and disruptive. Anyway, I won't add back the names. I leave that task to someone else.2001:2020:311:BED5:484C:45C:2286:85D5 (talk) 17:59, 16 May 2024 (UTC)[reply]
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
If I see correctly, the last discussion about this situation was archived without close and without action at Wikipedia:Administrators'_noticeboard/Archive326#Block_review_:_Linas in 2020. The user is indefinitely blocked and still openly actively editing as 67.198.37.16 (talk·contribs·WHOIS), proudly displaying their editing history on their talk page (diff).
I initially placed a long-duration block evasion block, but looking at the previous discussion (and I might have overlooked newer ones) and the interactions on their user talk page, I'm left without a strong desire for blocking, and mostly baffled.
The easiest way out of the situation would be unblocking the account in case there's consensus for doing so, I guess.
Support unblocking "If a rule prevents you from improving Wikipedia, ignore it." The IP has contributed positively for 9 years now. Call me crazy, but maybe it's time to stop pretending that the person behind it is up to no good. 78.28.44.127 (talk) 11:11, 16 May 2024 (UTC)[reply]
Unblock This is a silly situation, either they should be unblocked or the IP should be blocked for much longer period. Established editors evading a block or scrutiny by not logging in is a major reason editing as an IP can be so difficult. Having scrubbed back through their talk page edits the issue of personal attacks and harassment doesn't appear to have been an issue recently, and if they return to their old ways the account and the IP can be appropriately blocked. -- LCU ActivelyDisinterested«@» °∆t°12:18, 16 May 2024 (UTC)[reply]
An IAR unblock would have near-zero cost, and a decent upside. The old, rouge Floquenbeam would have just unblocked, but the more cowardly new Floquenbeam will just comment instead, and leave it for someone else. If they've been blocked for 12 years, another 12 hours won't hurt. --Floquenbeam (talk) 14:49, 16 May 2024 (UTC)[reply]
Absolutely unblock; that 2020 (3rd-party) appeal reached a pretty clear consensus, and it's a shame it never got acted upon. I don't even think it's a matter of rope anymore; the original block was rather spurious, to say the least. ——Serial Number 5412915:01, 16 May 2024 (UTC)[reply]
Oppose unblock - during the previous third-party appeal that was imposed on them without their consent (User talk:67.198.37.16#Ask forgiveness), they claimed that bureaucrats told them to edit anonymously while their account was blocked (!), while simultaneously claiming that the account wasn't theirs, and when that was not gaining traction (because they obviously are evading a block) they switched to saying that the block had expired (it had not) and repeatedly insulted the admin that tried to explain what "indefinite" means. After they were shown that the account was definitely still blocked and also shown the policies against block evasion and personal attacks, they changed their strategy to simply say loudly that they were breaking no rules, and accused everyone who did not agree of lying and being "in cahoots" with one another for sinister motives, including at least one editor who had been supporting them, just because they were admins and because "bureaucrats are the layer above WP admins" (they're not). This was all in response to someone having posted a link to the AN unblock discussion which up to that point had been rather strongly supporting unblocking them. This user has an extreme persecution complex which is not compatible with editing a collaborative project where fellow editors will challenge your work from time to time. This block-evading IP should be blocked, and should continue to be blocked each time they come back, until they make a proper unblock request acknowledging their poor behaviour.
For the record I am in favour of an IAR interpretation of unblocking editors in mistaken cases of inadvertent block evasion, or where a blocked user has managed a history of productive contributions in spite of a block for a one-time incident and where the behaviour has not continued. This is not one of those situations. A user whose response to being told they're breaking the rules is to state that the rules don't exist should not be editing here. Ivanvector (Talk/Edits) 15:19, 16 May 2024 (UTC)[reply]
Unblock As far as I can tell the only current active complaint is that Linas won't recant. I understand the desire to make sure editors actually understand the rules before lifting a block, but I don't think that's the issue here. This just looks like insistence on a performative self-abasement. That's just icky. --Trovatore (talk) 00:34, 17 May 2024 (UTC)[reply]
Comment Since opinion here wasn't unanimous, I think this discussion should have been open for at least 24 hours before action was taken. Yes, I'm kind of a closet bureaucrat (small "b"). LizRead!Talk!02:36, 17 May 2024 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Deletion procedure for draft articles created in violation of arbitration remedies
Mattythewhite has consistently been changing the Brighton and Hove Albion manager section from vacant to Roberto De Zerbi even though a citation from the official Brighton and Hove Albion website announcing Roberto De Zerbi is leaving has been added Brightonandhovewinnerz (talk) 20:32, 18 May 2024 (UTC)[reply]
@Brightonandhovewinnerz: You must notify an editor when you start a discussion about them. I have done that for you. Administrators don't adjudicate content disputes. Discuss it on the article's talk page and don't engage in an edit war. RudolfRed (talk) 21:13, 18 May 2024 (UTC)[reply]
He's leaving effectively after the Manchester United match on Sunday, that's why Mattythewhite and Struway2 have restored it to have De Zerbi as the manager on the article. Having it as vacant is factually incorrect. Iggy (Swan) (Contribs) 21:14, 18 May 2024 (UTC)[reply]
User:MisterHarrington
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Why is this at WP:AN rather than WP:ANI, why are you not providing diffs of the breaches of WP:ENGVAR that you're complaining about, and why are you representing the erroneous change from "inquiry" to "enquiry" as a change from British to American English? NebY (talk) 15:07, 18 May 2024 (UTC)[reply]
Your message comes across as a bit abrasive. I'm relatively new to the bureaucratic side of Wikipedia. I brought this here because I felt the user's editing pattern could benefit from being reviewed by an administrator. I find the various different noticeboards a bit confusing, though. I was not aware I needed to provide all of the diffs for the WP:ENGVAR breaches. I'm busy working on an article at the moment but I will look through the user contributions later and provide diffs for problematic edits. As for "inquiry" to "enquiry", we call these inquiries in the UK and I am not familiar with every variant of English (I don't think I specifically mentioned American English, but I could be wrong); I assumed given the other warnings for WP:ENGVAR this was another violation. Adam Blacktalk • contributions16:05, 18 May 2024 (UTC)[reply]
WP:ANI, as stated at the top of this page, is the place for intractable behavior problems and as stated in that page's header,provide diffs. You're asking administrators to take action; what you assumed because you've seen warnings is not a valid basis for action. As toI don't think I specifically mentioned American English, your original posting here includesMisterHarrington has reverted @Soni's latest reversion of his needless change from British to American English at Lucy Letby after receiving another warning. "Enquiry"[173] is not American English. How many actual cases of MisterHarrington needlessly changing from BrEng to AmEng are there? NebY (talk) 16:20, 18 May 2024 (UTC)[reply]
Adam Black, rather than getting bogged down in a meta-discussion about what mechanism is the appropriate one to raise this issue, why don't you close this and re-raise it in WP:ANI as suggested above? Right now the discussion is centered on where the discussion should be rather than the editing behavior (or behaviour!) that needs to be addressed; closing out and restarting will probably be more productive. TJRC (talk) 02:54, 19 May 2024 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Account being sold
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
It has come to my attention here that User:Sachinsewa, a veteran Wikipedia editor, may potentially be selling their account. This could be a hot spot for vandals/trolls using an account with lots of edits to get away with something bad. Can WMF do anything about this, and/or could admins block this account to prevent this account from going in the wrong hands? Courtesy ping: Saqib for telling me about this. thetechie@enwiki: ~/talk/$18:05, 19 May 2024 (UTC)[reply]
CentralAuth generally also includes the glock reason (in this case, cross-wiki promotion). With that said... the stats given on that page don't sync with Sachinsewa's account details. So this is almost certainly a scam. —Jéské Courianov^_^vthreadscritiques18:12, 19 May 2024 (UTC)[reply]
Yeah, they claim 4K+ edits on enwiki alone but on enwiki they have only 14. Scam, and I'm guessing that's why no one has fallen for it. Oh well. Closing. thetechie@enwiki: ~/talk/$18:23, 19 May 2024 (UTC)[reply]
Re-opening discussion as intervention may be necessary after all. Check the user ID shown in the first screenshot. Querying the public Wikipedia database shows this ID is tied to User:UA3 and not User:Sachinsewa. This user has 4,043 edits, which matches what is being claimed in the ad. See [174] for the query. Adam Blacktalk • contributions18:29, 19 May 2024 (UTC)[reply]
Took the words right out of my muzzle, and answered the question I was going to ask, to boot. Based on what my popups say, UA3's inactive (last edit ca. 2 years ago). If Sachinsewa's trying to sell off UA3's account, my thinking is he's either running a scam or he's compromised UA3 (and thus knows/could give up the account's password). —Jéské Courianov^_^vthreadscritiques18:33, 19 May 2024 (UTC)[reply]
Possibly. But unless there's strong behavioural evidence, that can't be proven. (It couldn't be proven technically even at the time, either; Sachinsewa was glocked a year before UA3 went on sabbatical and hadn't edited en.wp for ten years at the time of the glock.) —Jéské Courianov^_^vthreadscritiques18:44, 19 May 2024 (UTC)[reply]
This thread can safely be re-closed. First, the for sale link is from 2022, still no edits 2 years after it went on sale. Second, anyone stupid enough to pay $1500 for an "aged" account with only 4k edits will have CIR issues that will be easy to spot. Floquenbeam (talk) 18:51, 19 May 2024 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.