Hello, I recently contributed several seperate edits to the 4chan /pol/ page and my several contributions were totally reverted by another user despite lack of justification. The arbitrary reversion of rule abiding content in its totality (specific example: the reversion of a properly cited claim that the site has been called "wildly offensive" in by a reputable outlet) clearly represents bad-faith vandalism and now that user is accusing me of starting an edit war, which is not my intention. I simply request that my contributions be respected and if a portion of my contribution violates some rule then we can work from there, but there is no reason for me to be entirely excluded from the page. Can I have a dispute resolution here? Thank you. Gkoogz (talk) 11:25, 17 May 2022 (UTC)
(edit conflict) @Gkoogz: This is a noticeboard for administrative action, not dispute resolution. You may want to pursue WP:Requests for comment to get broader input, but Talk:/pol/ shows, at this time, clear consensus against your contributions. That said, a quick look at the article's history shows that you have flirted with a brightline violation of the three revert rule, and your claim of reverting vandalism falls short, so you don't qualify for that exception. —C.Fred (talk) 11:48, 17 May 2022 (UTC)
<ec>::I've blocked indef. In their short career they've made a practice of treating disagreement as vandalism, and haven't responded to warnings, brushing them off and coming to ANI with the same attacks on those who disagree. I see no sign that this will change. They are welcome to craft an appropriate unblock request to change our minds. Acroterion(talk)11:54, 17 May 2022 (UTC)
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.
Disruptive editing/vandalism
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.
User in question has already been reported at AIV and report remains up, but has been unactioned for a few hours now as the user continues their same disruptive edits/vandalism. They are continuing the same disruptive editing/vandalism from previous IPs 2001:EE0:40C1:CA9C:0:0:0:0/64 and 123.16.202.191, and was previously blocked on the range as well. Should be a quick/clear indef block, as it's very evident they are WP:NOTHERE. Thanks in advance. Magitroopa (talk) 05:52, 17 May 2022 (UTC)
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.
This IP needs blocking, dedicated solely to vandalism. As they have some knowledge of wikipedia jargon, I would imagine they have other IP's going, if anyone fancies doing some detective work.
What makes you say they have knowledge of Wikipedia jargon? I see four edits, none of which were particularly constructive, but none are using any jargon. GirthSummit (blether)15:27, 15 May 2022 (UTC)
Sorry, yes. I misunderstood the edit summaries as something the user was typing, my bad. All the edits are clear vandalism though. The nicknames applied to these individuals do not exist and are insulting. Boynamedsue (talk) 16:13, 15 May 2022 (UTC)
The edit from today was pretty silly - probably a reference to this interview. The previous edits were from weeks ago - there isn't really anything urgent that needs addressing, but if they keep doing it you can report to AIV. GirthSummit (blether)16:50, 15 May 2022 (UTC)
Three IP ranges in Western Canada have been genre-warring in music articles and making other disruptive edits for a few months now.[234] They keep edit warring at Beautiful Eyes and Fast & Furious. There's an obvious problem with WP:CIR,[235] and they haven't communicated via Talk pages except to make unclear edit requests[236][237][238][239] which are never revisited to continue a conversation. The disruption is annoying but not outright vandalism. Binksternet (talk) 04:04, 14 May 2022 (UTC)
I looked through the ranges I only see one warning by you a month ago. Looks like they are mostly fiddling with things a good faith way but maybe not always helpful way. I don't really see enough explanations of guidelines/warnings for any action. Galobtter (pingó mió) 22:03, 15 May 2022 (UTC)
BoMadsen88
BoMadsen88 has been conducting an ongoing harassment campaign against me, with the most recent case being here. As you can see, the account does this via Talk pages that I frequent: Special:Contributions/BoMadsen88. There was an ANI raised about the account previously and the following was stated: "Other than that I don't think there's need for blocks or bans provided that the harassment stops. signed, Rosguill."
Please do tell me how I am harassing you. Did I contact you? I am pointing out what might potentially be a very big problem. With your edit history and behaviour there is unfortunately a very great risk of a strong COI. This has to be addressed asap. BoMadsen88 (talk) 18:56, 20 April 2022 (UTC)
BoMadsen88, please don't use article talk pages to post conduct reports, those belong on a conduct board such as this one. Beyond that, QRep2020, this report provides a poor summary. You don't link to WP:DIFFs but rather to entire discussion threads. You're expecting quite a bit from a reviewer here in that sense (WP:VOLUNTARY). And maybe someone will do it (delve deep), but if this thread goes stale, that'd probably be the reason why. Also, I don't know what you expect us to tell from linking BoMadsen88 contribs. At a glance, they just seem to be an Elon Musk WP:SPA. El_C19:30, 20 April 2022 (UTC)
What may also need addressing 'asap' is your continued use of an article talk page to engage in the harassment of a contributor, after being formally warned to stop. AndyTheGrump (talk) 19:22, 20 April 2022 (UTC)
BoMadsen88 sitewide block converted to a p-block, the exact same one as QRep2020's. See my notes at the unblock request. While it doesn't negate some of the problems mentioned above, I'm inclined to give them the option of participating in this thread. El_C21:40, 20 April 2022 (UTC)
Look at their edit history. Their "purpose" was to get me banned and, hey, they did it. Only a matter before they come to my Talk page and gloat again. QRep2020 (talk) 21:47, 20 April 2022 (UTC)
El_C Hello, as stated above my sitewide block has been converted to a p-block for the Elon Musk Article only. However, this should be removed as well.
I was banned because of “conducting an ongoing harassment campaign against QRep2020” (Qreps2020 quote). But the only thing I did was pointing out my observation that the behaviour of was QRep2020 had been very problematic. QRep2020 has now been p-blocked by the exact same reasons that my work and research unraveled. It is therefore fair to say that QRep2020s problematic behaviour has only been uncovered and stopped now thanks to my observations and persistence. The reason that I have was p-blocked in the first place is now not valid anymore.
I only tried to make one of the most visited articles on Wikipedia less biased because of very problematic behavior I had witnessed for a long time. I accomplished that and I believe that is what every good Wikipedia editor should strive to do - don’t you too?
QRep2020 had a lot of edits on Elon Musk which gave him an authority on the page - this meant that other Wikipedia editors did not dare push the matter whenever anyone tried to point out the obviously biased sections in the article. And there has been many editors throughout the last 2 years that has tried in vain to make the article less negatively biased - each and every time QRep2020 has immediately shot the attempts down.
I am sorry I had to post my observations on the Elon Musk page, but I did not know where else to go. That will not happen again. BoMadsen88 (talk) 09:06, 22 April 2022 (UTC)
The same applies to QRep2020. Their top ten most edited articles are all Musk and Tesla related. This editor's purpose here on Wikipedia seems to be to make Musk and his businesses look as bad as possible. Cullen328 (talk) 19:50, 20 April 2022 (UTC)
Well shit, so the good and the bad. Symmetry? I'm gonna re-open that ANI thread and refactor this, as they might need to be shown the door, too. El_C19:53, 20 April 2022 (UTC)
This is absurd. If you look at my edits, they are not all negative. I've contributed 10 entries of my own. Please do no feed into this castigation. QRep2020 (talk) 19:59, 20 April 2022 (UTC)
QRep2020, if by "entries" you mean articles, isn't it true that all the articles that you have created are related to Elon Musk and Tesla? Isn't it true that in the past 24 hours, you supported keeping the poorly referenced quote calling Musk a "total and complete pathological sociopath" in the article? Do you deny that your main activity on Wikipedia is to add negative content about Musk? Cullen328 (talk) 20:24, 20 April 2022 (UTC)
Yes, I deny it. Hindenberg Research has nothing to do with Musk. I've contributed extensively to the Fraud "article" (I was a little upset when I replied before and used the wrong word) and to the Trevor Milton article. Ken Klippenstein rubbed up against Musk but he is important reporter in his own right - same goes for Lora Kolodny. I can be obsessive sometimes, yes, but I always try to follow the rules. QRep2020 (talk) 21:02, 20 April 2022 (UTC)
QRep2020, Hindenburg Research is an aggressive short selling operation involved with the electric vehicle sector, and Tesla is the market leader. You also wrote and are the main author of TSLAQ, an aggressive short selling operation focused on criticizing Musk and Tesla. Cullen328 (talk) 21:48, 20 April 2022 (UTC)
Based on my limited interactions with QRep2020 I think they are a good faith editor who clearly has an interest in Musk/Tesla but also tries to follow the rules. Springee (talk) 19:59, 20 April 2022 (UTC)
Perhaps QRep2020 should be advised (not instructed, advised...) that expanding their editing to a broader range of topics might be of benefit. It should make claims of SPA editing seem less credible, and maybe help build a sense of perspective. As fascinating/annoying Musk is, he isn't the centre of the universe (yet ), and I'm sure QRep2020 can find other topics of interest, if editing Wikipedia is their thing (which it need not be...) AndyTheGrump (talk) 20:23, 20 April 2022 (UTC) Strike that, per El_C below - I'd missed that. AndyTheGrump (talk) 20:27, 20 April 2022 (UTC)
On closer review, I've p-blocked QRep2020 indef from Elon Musk and Talk:Elon Musk (see block notice). There are so many other topics to write about besides just negatively, about Elon Musk and his companies. Too many red flags, like, in the edit (diff) about and header titled"total and complete pathological sociopath" (link) and the one that states[E]veryone in Tesla is in an abusive relationship with Elon (diff — quoting WIRED, but still). And these are just edits from April 18 and April 20, respectively! El_C20:25, 20 April 2022 (UTC)
My initial impression is that this block was too hasty. The "sociopathy" language went through a whole RfC and was present in the Good article pass version. Speaking of which, QRep appears to be one of the two main shepherds of the article through the GA process. There's been a lot of critical coverage of Musk over the past two years in reliable sources. I can't say I've reviewed QRep's editing pattern enough to say if they've outpaced the RS or not. I can say they've been quick to accept consensus and admit an error. I wouldn't be surprised if a warning sufficed to stem even the perception of disruptive editing. Firefangledfeathers (talk / contribs) 20:44, 20 April 2022 (UTC)
If it's just negative material, though, isn't it more wolf than shepherd? I realize there are a lot cheerleaders, too, but is doing the opposite really any better? I'll keep an open mind, though, sure. El_C21:01, 20 April 2022 (UTC)
It wasn't all negative material. It's a balancing act. I have stayed out of plenty of matters concerning Elon Musk that I could have "fomented" if I wanted to turn the article into a hit piece.
Look, I got heated these past few days because I discovered people talking about me offfsite. And I shouldn't have focused on the stupid line about sociopathy - I just saw people coming out of the woodwork and was reactionary. I am a grownup, I can admit that.
Yeah, I saw the protection request yesterday, which I declined (RfPP diff), and which is partly why this thread peeked my interest. In any case, these are only two pages you are restricted from, out of millions and millions. Indefinite does not necessarily mean infinite, but could just be undetermined length. El_C21:16, 20 April 2022 (UTC)
Yes, but that one page and its Talk page are visited by hundreds of thousands of people each day, that is why balance is so important. And yes I stepped over the line, like I said, but when the subject of the article tells people to modify the said, there is a constant need to maintain some semblance of critical ratio.
I would also like to point out the irony here that, regardless of what I am "answering to" here, I do not deserve to be libeled on a Talk page that is viewed by said thousands and now I cannot even answer to it because I elected not to give into a baser instinct. Given my status, can someone please remove the BoMadsen88 text from the Elon Musk Talk page about me. QRep2020 (talk) 21:28, 20 April 2022 (UTC)
Elon Musk can say whatever (he can maybe even buy Twatter to make sure that it's his hivemind friend), but the fact is, as I mentioned in my decline of the RfPP request, that most of the users involved in recent disputes were extended confirmed, so it's unlikely they came from unReaddit. El_C21:49, 20 April 2022 (UTC)
Agree with Firefangledfeathers; I believe the block should be lifted, with encouragement for the editor to spend a little less time editing Musk-related articles and a little more time editing other articles. BilledMammal (talk) 00:41, 26 April 2022 (UTC)
Uh, new comments go at the bottom. Weird placement. Had I not looked at the revision history in passing, I'd have not seen it. Anyway, I'm not unblocking either user. They both can appeal their block in the usual way. Appeals which I'm unlikely to comment on, either way (because because). El_C01:29, 26 April 2022 (UTC)
Just chiming in to add that I also believe QRep2020 is a good faith editor and valuable contributor to the project. When I started editing a few years back, all articles on Wikipedia related to Musk were extremely biased and promotional, failing to mention almost all of the well-documented criticism and controversies surrounding Musk and his companies. The number of trolls who still to this day try to change Musk's article to call him a business magnet is indicative of the "reality distortion field" surrounding Musk[240][241][242], and QRep has been one of the few active contributors pushing back to maintain neutrality. So while they may have been overly zealous at times, and a warning could certainly be warranted, I believe that the block was premature as they have made a very valuable contribution by providing some much needed balance in this subject area. Stonkaments (talk) 23:21, 20 April 2022 (UTC)
As noted on QRep2020's talk page, they should probably substantively address the possible WP:COI raised by Cullen328 (diff), who unlike me fumbling about, actually seems to have done his research. El_C02:06, 21 April 2022 (UTC)
Firefangledfeathers, I have not had the opportunity to read those more recent links so will respond based on what I knew at the time. I have seen no evidence of a clearcut conflict of interest though I am aware that some editors have accused this editor of being a Tesla short seller. I literally have no idea and even no hunch whether or not this is true. But following my criticism, they posted a denial on their user page. What I do know that this is a highly skilled SPA editor who seems to think that Elon Musk is a "very bad person" and is determined to use Wikipedia as a platform to negatively impact Musk's reputation. In the spirit of full disclosure, speaking personally, I think that Musk is a bizarre person who has received a lot of legitimate criticism. I am not a fan. He is obviously also a highly successful person with major accomplishments. He can deploy a troll army to have the Wikipedia biography say that he is a "magnet" instead of a "magnate" and I have opposed such baloney when it has come to my attention. But what I see is that this is an editor who by all evidence is here only to add content that reflects negatively on this living person and his businesses. Yes, there are a lot of negatives about Musk. But accounts focused on praising or discrediting Musk are equally disruptive. The Neutral point of view is a core content policy and editors who are here to push a negative point of view about a living person are inherently disruptive even if they try, on the surface, to comply with policies and guidelines. Contrition when an editor is sanctioned should be evaluated with a certain degree of skepticism, and the "I blew my stack" defense is not too persuasive, unless accompanied by persuasive assurances thst the disruption will not resume. Cullen328 (talk) 03:30, 21 April 2022 (UTC)
Thanks for responding. I was mostly asking for clarification on COI, but I also appreciate your thoughts on the SPA-ness of it all. My angle is: could we have prompted similar levels of contrition and (hopefully soon to come) assurances against future disruption with a warning or temp block (though I know El C is allergic). I've said my piece, and I'd like to leave space for the opinions of others. So, I'd appreciate your contemplative thought on the matter, but please don't feel compelled to reply. Firefangledfeathers (talk / contribs) 03:54, 21 April 2022 (UTC)
I was planning to take a few days off of Wikipedia before appealing and making assurances, but I do not want to invite a COI over my head too so I will say the following in hopes that it shows where my mind is at the moment:
Though I do not agree that I have exercised a "special purpose" here on Wikipedia - often narrow, yes, but not exclusive - I have no doubt grown obsessive about getting in front of what I came to perceive as a bend in the encyclopedia towards promoting Musk and his endeavors. In recognizing this, I promise to reread NPOV immediately during my small break from the site and assure that, if granted clemency, I will not make any updates to Elon Musk for a period of a month and will not push for any changes via discussions on Talk:Elon Musk as well. I also promise to not make any updates on other Musk-related articles during this time besides reverting obvious acts of vandalism or disruptive editing as a way of forcing myself to try and upend these assumptions I have cemented. Finally, I will force myself to spend time contributing to relatively distant topics on Wikipedia like @El C hinted at and will figure out a way to record any such non-Musk related updates I make on my Talk page as a testament to what I am doing to fix my behaviors.
It is difficult to assume good faith with your statement given that youdo not agree that I have exercised a "special purpose" here on Wikipedia, given that your past 1,000 edits (dating back to April 2021) exclusively deal with Tesla and Elon Musk-related articles. Obsessive is one way to put it. --PerpetuityGrat (talk) 17:50, 21 April 2022 (UTC)
Really? You're going to flat out lie about your edit history now? See for yourself: here and here. You're really going to still maintain that you are not obsessed with Tesla-Musk-related articles? What a farce. --PerpetuityGrat (talk) 20:30, 21 April 2022 (UTC)
I found two whole edits out of your previous 1,000 edits, my bad. 998995 edits out of your past 1,000 edits pertain to Musk in some shape or form pretty much constitutes exclusivity. --PerpetuityGrat (talk) 21:11, 21 April 2022 (UTC)
I'm not sure El_C. Maybe SPA-like activity coupled with the letter Q is enough to say "this is a clear COI"? I think the COIN discussion came to no consensus on that point. QRep2020 clearly denies having a COI and has an explanation for their username. I get some real "small world" vibes from the cast of characters there, that's for sure. Firefangledfeathers (talk / contribs) 02:55, 21 April 2022 (UTC)
Sorry, I'm not sure I follow, Firefangledfeathers (RE: "cast of characters"). But just to clear things up: I am Q. Tremble before my stromzezes. El_C03:09, 21 April 2022 (UTC)
Oh, there was a serious part: I dunno, at a gleence, it seems like it had fairly limited participation, either way. Not sure what prompted what by whom when. Mind you, like with the ANI report that QRep2020 provided in their OP, I see HAL's sig and my eyes sort of glaze over. No offense to him, nice guy and good content editor, and hopefully he returns to the project soon, but I just find it visually jarring. Damn, I'm terrible. El_C03:58, 21 April 2022 (UTC)
It is always either amusing or disconcerting to see such highly experienced editors stray so far from the substance of the matter being discussed. Is that the norm these days? Cullen328 (talk) 05:13, 21 April 2022 (UTC)
@Cullen328: for my part at least, notwithstanding the undoubtedly excessive levity (though hopefully not too tone deaf), I hope you know that I always give serious comments, from you or anyone, serious consideration. El_C13:33, 21 April 2022 (UTC)
Perhaps a reasonable compromise is QRep2020 agrees that no more than 50% of their meaningful edits will be on Musk related topics. By meaningful I mean things other than minor edits/contributions/spelling corrections etc. My concern here is that, so long as the editor stays within the rules, I don't see a clear issue with an editor having only a narrow interest. It's OK to argue that some content is DUE etc so long as an editor is also willing to accept when consensus doesn't go their way.
This block is warranted. There's a pretty big difference between "having only a narrow interest" and fixating on adding negative information. The latter falls into WP:SPA and WP:NOTHERE. Honestly I think QRep2020 is nice enough, but the editing behavior is clearly problematic. It has been problematic since COIN, and in fact has only gotten worse. --Elephanthunter (talk) 16:18, 21 April 2022 (UTC)
The COI thread linked above resulted in no consensus and was from over a year ago. Does anyone have any new evidence of COI to present?
Being an SPA is not against policy. Adding negative information to articles is also not against policy. Can anybody post three diffs of "bad" edits by QRep2020? Because I'm not seeing the problem here, other than someone editing a lot about a particular topic, which isn't unusual at all.
Are we within WP:OUTING policy to link any Wikipedia editors to those Reddit threads about QRep2020? Because if so, that's a real problem that needs to be addressed. And if not, then it should go to arbcom via private evidence rather than be raised here on-wiki at ANI. Levivich19:11, 21 April 2022 (UTC)
For what it's worth: A quick review of that WWW site indicates that people are not attempting to attach an identity or any personal information to the Wikipedia account, and are referring to it by the account name. Wikipedia:Linking to external harassment and Wikipedia:Harassment#Off-wiki harassment do apply, and the account-holder has said "Look, I got heated these past few days because I discovered people talking about me offfsite.", though, so I think that people should be cautious about this. I think that great caution should also be exercised in trying to link the Reddit accounts to Wikipedia accounts, to the extent of not doing it, not least because it appears that the Reddit accounts are just trying to take credit for what someone else did. "We" did this? There's no evidence there of their actually doing anything. It wouldn't be the first time in the history of the world that people have indulged in empty bragging. ☺ Uncle G (talk) 20:55, 21 April 2022 (UTC)
https://en.wikipedia.org/wiki/Talk:Tesla,_Inc./Archive_2#Founders Certain users (QRep2020) involved in biographies policy violations participated in the conversation. I propose a new conversation about the founders of Tesla. A lawsuit settlement agreed to by Eberhard and Tesla in September 2009 allows all five – Eberhard, Tarpenning, Wright, Musk, and Straubel – to call themselves co-founders. --JShark (talk) 04:55, 28 April 2022 (UTC)
This, and your edits to Tesla, Inc. come close to WP:GRAVEDANCING -Behaving as though a consensus is no longer valid simply because a blocked or banned editor contributed to it. Whilst consensus can change, the simple act of blocking does not change it - if you wish to overturn the previous consensus then further input should be sought. If you want to overturn the consensus, then open a discussion, but the status of QRep2020 is not relevant. BilledMammal (talk) 05:09, 28 April 2022 (UTC)
QRep2020 isn't even being "blocked" in the usual sense, which further invalidate JShark's argument. I have fear that this ANI thread is becoming (or have been per off-wiki Reddit posts) a place for people hate and love Musk clash together, and I hope some administrator would lose this asap. CactiStaccingCrane (talk) 05:28, 28 April 2022 (UTC)
Support partial block. The last few edits include [246][247][248][249][250][251]. Actually they don't include that, those are literally the last few edits (no cherry picking). A single purpose account whose sole objective is to add negative information to a BLP should not be editing that BLP. Good block. Aircorn(talk)08:50, 1 May 2022 (UTC)
You linked to six edits in reverse chronological order, let's look at them each.
Sixth edit (Apr 16 21:41) was re-reverting a bold edit that was made at 07:41, reverted by another editor at 09:29, and reinstated by the first editor at 18:51; it was a good edit per WP:BRD and WP:MANDY
Fourth edit (Apr 17 19:57) was reverting a bold removal made at 17:25; the phrase that QRep restored with the revert, "stances and highly publicized controversial statements", had been in the article for at least on year prior in the form "stances and highly publicized controversies" (that's as far back as I looked); good edit
Third edit (Apr 18) is the edit I talked about above, that was per an RFC result, and also was in the Good Article version of the article (the first edit C linked to in the comment above at 20:25, 20 April 2022); it's also a good edit, because it's backed by an RFC
Its not about whether the edits are good or acceptable. It is the simple fact that every edit is negative to a BLP. Taken as a whole this is someone whose only intention is to add negative content about Elon Musk, not to actively contribute to making the encylopaedia better. Aircorn(talk)10:13, 7 May 2022 (UTC)
It's exactly about whether the edits are good. A group of good edits, taken together, are not a bad thing. It's not all negative (not all of those six were negative), there's a lot of negativity in the sourcing, and correcting constant whitewashing means introducing negative content. It's just how it is. Did you read the Slate article from a couple days ago about this by the way? It explains this. Let me quote a part for you:As the user Warbayx put it, “literally 1/4 of Musk’s front page is dedicated to criticism, how can anyone think this is unbiased and fair?” To which the user PraiseVedic replied, “I would say that more than 1/4 of the coverage Musk receives in the media is critical of him, so if anything Wikipedia is under-criticizing him, if that’s a thing.” Anyway, six negative edits on one day is not a lot. I've added a lot more negative stuff about people on this website than that. You know all my edits about the police are negative, for example. Because I edit articles about police brutality. It's inherent. If you edit about Musk or Putin or Johnny Depp or many other high profile people, it's gonna be a lot of negative. Levivich13:33, 7 May 2022 (UTC)
Its not though. The only difference I see with this case and StuartYeates a month or so ago is that we don't have the smoking gun of a linked twitter account telling us of their intentions. If anything this is way worse from an onwiki behaviour point of view as Stuart worked on multiple other topics and BLPs without much problem whereas here we have a SPA with one very clear intention. Again if your only reason for being here is to add negative comments to a BLP (which is not refuted and should not matter who the BLP is) then you shouldn't be editing here. You do a lot of other things, including mostly adding good commentary here, so your situations don't compare. Aircorn(talk)08:00, 9 May 2022 (UTC)
But they're not only adding negative comments to a BLP. Look, of the six edits you posted, only one--the First edit--was adding negative content...
The second edit is not negative content, it's just neutral wordsmithing. Also, it's implementing a talk page discussion started by, and with the participation of, editors other than QRep. There is no way we can call that "QRep adding negative content to a BLP"; it's multiple editors figuring out how to say something neutrally, which we call "consensus". Implementing consensus (or attempting to) is not "adding negative content to a BLP".
The third edit was restoring negative content that had been removed against an RFC, and that had been there since the GA. Restoring longstanding negative content is not "adding" negative content.
The fourth edit also did not involve negative content, just wordsmithing. Also, it was restoring longstanding language. So it's not "adding" anything.
The fifth edit was adding negative content, but it's following talk page discussion, and the suggestion to add the content was made by an editor other than QRep (and other editors agreed). It's not fair to pin that on Qrep as "adding negative content" when they're not the impetus for it, they're just taking the crack at writing it up after a talk page discussion.
The sixth edit wasn't adding negative content, it was re-removing overly-positive content recently added by someone else, that was already reverted by someone else. That's not "adding" anything either.
Implementing talk page consensus, reverting promotional language, restoring longstanding language changed against or without consensus... none of these things is "adding negative content to a BLP". These are all things we should be encouraging editors to do. I think of these six edits, five are good edits that we want people to be making. That's not something to sanction someone over. Levivich01:46, 10 May 2022 (UTC)
The block has been removed. Appreciate the votes of confidence, everyone. I believe this discussion can be archived now. QRep2020 (talk) 23:07, 15 May 2022 (UTC)
User:Palow s coba11 / another unresponsive mobile editor
The only time that you can see notifications on mobile is when about to edit. Hopefully they see it then. RHF 19 (talk) 19:55, 15 May 2022 (UTC)
What rubbish, I always see all notifications on my mobile device. Oh, yeah, I virtually always use desktop mode. 😁
Clearly good faith, so I've left them further advice, hopefully they actually read that (and everything else on their talkpage). Mako001 (C) (T) 🇺🇦 03:19, 16 May 2022 (UTC)
Wikidellhi, PRODding Jain articles under BLPPROD and removing AFD tags
Hello. Long time since I've been at ANI, but this one does not fit into AN3, AIV, or other noticeboards. Apparently, this user had been PRODding articles about Jain groups under BLPPROD, which I quickly dePRODded procedurally, as they were not BLPs. They had also removed an AfD tag here, which I promptly reverted as well. They had also left some rather inappropriate warnings here. I am seeing a couple of constructive edits coming from this user, but they had already been blocked for edit warring. Thanks, and I hope to get some feedback. — 3PPYB6 — TALK — CONTRIBS — 16:31, 15 May 2022 (UTC)
He has already got site block and the user is still engaged in adding unreferenced material [[252]], he also gave inappropriate warnings when in fact it was him who was edit warring just to add word "Jat" there. And for this wrong prod it looks like some kind of revenge based editing against me. Just see he added BLPPROD on an unrelated article where it is not applicable [[253]]. He also removed AfD tag from an article. I think there is a case of WP:CIR, and all this is happening after facing recent ban for edit warring.RS6784 (talk) 05:32, 16 May 2022 (UTC)
The user is also continuously directing personal attacks on other editors, just see here [[254]], here again putting personal attacks- [[255]]. Now just see here [[256]] the editor created a new page- duplicate version of the one Khokhar page where he had been banned for edit warring. This is open case of WP:CFORKRS6784 (talk) 07:16, 16 May 2022 (UTC)
I've blocked indefinitely as it's clear that the user is not here to build an encyclopaedia but rather promote an agenda. —SpacemanSpiff07:46, 16 May 2022 (UTC)
I don't believe there is an SPI on this one. Users are just using my LTA data. Several previously blocked users are listed in User:Meters/Frank Mortenson LTA#Accounts. The behaviour is a bit odd, since the intent is usually to promote Frank Mortenson, but as I wrote, a Tele2 Lithuania IP with a focus on Frank Mortenson is unlikely to be anyone else. Meters (talk) 00:00, 16 May 2022 (UTC)
Meters, the socks kept using an article from a Medium columnist that just posts derogatory, false claims about Frank Mortenson, like he's being investigated by the CIA, he's a white supremacist, involved with the KKK, guilty of terrorism, so I'm surprised that the former IPs and accounts were promoting him because it looked like online harassment to me. But we have less to worry about now that there is an edit filter. I have to learn not to try to make sense of the behavior of sockpuppets. LizRead!Talk!04:33, 16 May 2022 (UTC)
Yup, I don't know if this is the same LTA or two different ones. It may be that the edit filter is working so well that they have had to switch to negative mentions just to keep him on Wikipedia. I'm not going to worry about it as long as we keep quickly whacking them. I've added the SPI and new (to me) behaviour to the report so others can see it. Thanks all. Meters (talk) 07:46, 16 May 2022 (UTC)
User:68.132.133.66
Clearly NOTHERE. This account has been indentified as an open proxy. It was warned for vandalism in June and December 2018, May 2019, as well as in January 2021. Then, in October 2021, it was blocked and recieved 8 warnings. It was then globally block as an open proxy for 6 months. Within 3 days of being unblocked, it was blocked for 3 months. There has been only one contribution by this user that is not obvious vandalism. Starship SN20 (talk) 13:13, 15 May 2022 (UTC)
Looks like a bog-standard fiber-optic business connection, possibly a school, rather than an open proxy. Regardless, it has been blocked for three months for vandalism, the latest in a series of escalating blocks, and that is sufficient for now. --Malcolmxl5 (talk) 17:07, 15 May 2022 (UTC)
These users seem to be WP:SOCKS of each other. They edit the same pages and the same topics, give each other barnstars, and have the same user page design. Could someone investigate this, and block the accounts if they are connected. I'm only posting here and not at WP:SPI because my account hasn't been autoconfirmed yet. Thanks, --எ (talk) 15:20, 16 May 2022 (UTC) (originally at 04:39, 16 May 2022 (UTC))
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.
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:Partygnome1234
I indeffed this user as WP:NOTHERE when he/she re-added unsourced negative content to Toll Brothers after this final warning. However, he/she quickly reverted that edit, and had also (unknown to me) left a reply to my warning that made my block look WP:INVOLVED, so I've undone it. Would someone else like to take it over if that seems appropriate? Note: please see the filter log. Thank you, Justlettersandnumbers (talk) 20:59, 16 May 2022 (UTC)
Respected Sirs, It has come to my attention that the article Neal Communities has been continually bombarded with promotional material. In recent months User:Bobrien12 has added un-encyclopedic material including using the company's website as the sole source for several facts and figures as well as attributions etc. He admitted in this revision [257] that he was an employee of the company in question. He takes his ladle and continues to serve up a dark stain on the name of the Free Encyclopedia. I am a new editor and I am not really very familiar with procedure. I hope that the proper authorities can rectify this matter. Technicalrestrictions01 (talk) 18:04, 16 May 2022 (UTC)
But these are very few. Having gone through around two dozen of them I think only two or three were correct. Others and I have already reverted many them, but many more remain. I believe the edits were made in good faith, but because of their sheer number I would suggest they be reverted using mass-rollback.
The original discussion about these edits was started on the Languages Wikiproject talk page. In this matter I have contacted Fastily, an admin, here. He refused to do the rollback but directed me here. There might be some other places where this has been discussed which I am not aware of.
This is a very simple case, and as I commented at the WPLANG thread, it can just be fixed with a mass rollback of the 150 or so as of yet unreverted edits in this filtered contributions list. All it takes is someone with the rollback userright and the willingness to click a few buttons using User:Writ Keeper/Scripts/massRollback. No further action needs to be taken, as the editor has stopped those fixes and it doesn't seem like they're going to restart.I would like to add that the correct edits are even fewer than might seem: example 6 above is presented as a correct fix, but it's not: "sackness" there is not a typo for "sickness" but an incorrect word for 'sacking'. – Uanfala (talk) 15:06, 16 May 2022 (UTC)
I see that after the rollbacks performed by Qwerfjkl and Elmidae, as well as by some smaller-scale manual fixes by a number of other editors, the offending edits have been reverted. As far as I'm concerned, this has been resolved and there's nothing else to do. – Uanfala (talk) 22:04, 16 May 2022 (UTC)
I recently removed the full name of UFC fighter Tony Ferguson from his article because it's not used in any independent media sources whatsoever. The source used to include it is independent research via a commission document. Per WP:BLP, this is a no-no because it constitutes WP:DOX. We need to err on the side of NOT including personally identifiable information on Wikipedia unless it is already widely available, and by all accounts, the only reason his is available via a Google search at all is its presence on his page.
When making this deletion, I explained my rationale on the talk page, Talk:Tony Ferguson.
I am bringing this to ANI attention because I take BLP extremely seriously with a lot more scrutiny than a typical Wikipedia article, which is precisely what WP prescribes. I am in general concerned that User:Cassiopeia may have something of a WP:BATTLEGROUND mentality on his edits to MMA articles, often gatekeeping the contributions of neophytes like myself, but I wish to assume good faith on that matter and await a greater rationale for why he decided to call me a vandal after reading WP:BLP. --Sorry sir, that's classified information (talk) 02:12, 14 May 2022 (UTC)
The overwhelming majority of news sources don't include the full legal name of their subjects, but those legal names are nonetheless valid inclusions in articles about them -- and indeed, are routine -- even in many cases where the subjects themselves would devoutly love to suppress the information. This particular case scarcely involves someone seeking to avoid publicity, or unwarranted digging. This is someone actively participating in professional sports, and the source in question is a publicly available government document issued in support of that endeavor. (It's a freaking scoresheet, for pity's sake.)Furthermore, WP:DOX absolutely, positively does not apply here: it's intended to protect the anonymity of Wikipedia editors, not of BLP subjects, and the only guidance there dealing with non-editors is "Content and sourcing that comply with the biographies of living persons policy do not violate this policy; neither do discussions about sources and authors of sources, unless comments about persons are gratuitous to determining source quality." Finally, I'm missing the diff where you talk this over with Cassiopeia before dashing straight to ANI to complain; might you provide it, please? Ravenswing 02:35, 14 May 2022 (UTC)
Just to note, 'twas me who reverted the removal and restored his name. Cass only restored the current ranking that you reverted, which could be what prompted the warning template being issued. That aside, I completely agree with Ravenswing. Media sources probably don't publish his full name because, why would they? Not all that relevant, but the guy has "Anthony Armand" tattood on his arm. I think it's safe to presume he's not trying to hide his full name. – 2.O.Boxing02:58, 14 May 2022 (UTC)
Come to that, a simple GNews search for "Anthony Armand Ferguson Padilla" turns up articles on CNN and in the Kenyan and Indonesian press; elapsed time, less than it took me to type this response. Ravenswing 05:19, 14 May 2022 (UTC)
Sorry sir, that's classified information See below
The warning was for the edit you removed the source ranking info see here here-1. I am one of the counter vandalism trainers in Wikipedia and it is my work to warns editors who make disruptive, vandalism, promotion, copyvio, NPOV, adding unsourced, spam and etc edits.
DOX has nothing to do with BLP. Pls understand the guidelines.
The full name is support by independent, reliable sourced content.
I am not the one who reverted or restored the full name info but other editor - see here-2. Pls check carefully next time before state the wrong fact. So I have no idea why the ANI is for.
Pls note if any disagreement, then go to the article talk page and "invite the involved" editor and discuss is "extensively and lengthy and you can also invite other experienced editors to comment who know a lot about the subject". If after all the above, and still distributive then an ANI can be raised for ANI is the last resort and not without discussion then go to ANI. You have not event ping me and any discussion of the issue and straight went to ANI and this is not how thing work. Thus, pls understand the the procedures. In Wikipedia, editors should discuss the issues in hand on the article talk page and not run to ANI for every issue. I have about 200K edits and have
Finally I am an experienced MMA editor in Wikipedia, and I am here to help. Do raise any questions or seek any assistance if you may. Cassiopeiatalk09:33, 14 May 2022 (UTC)
I thought WP:DOX applied to other editors? As far as I'm aware Ferguson does not edit wikipedia (if you've seen his twitter you can probably figure out why.) ♡RAFAEL♡(talk)20:53, 14 May 2022 (UTC)
As a BLPN regular, I have a fairly different perspective from most others here. While User:Sorry sir, that's classified information may have used the wrong policy and came to the wrong board (they should have raised this at WP:BLP/N rather than here), their actions quite correct and it's User:Squared.Circle.Boxing and User:Cassiopeia who at least initially edited completed inappropriate. Per WP:BLPPRIMARY and to a lesser extent WP:BLPNAME we do not rely on primary sources no matter if they are government issued or part of some competition to support someone's name. We require that the name is published in reliable secondary sources. Until and unless someone adds such a source, it is appropriate to remove the name. It does not matter whether we have reason to think the person is trying to intentionally conceal their name. In the absence of sources it's not our concern. In particular, it does not matter whether editors think like User:Ravenswing that it's basic information. No suitable sources then no name, period. You can yell until you're blue that it's basic information but if it's basic information then it should be trivially for you to find suitable soures. Perhaps the OP could have done WP:BEFORE but if you regularly edit BLPs you come across a lot of these terribly sourced names all the time, and sadly a lot of experienced seems to think it's acceptable when it isn't. Knowing jack shit about MMA, I would have no idea whether this is one of those large number of cases where the name isn't available in reliable secondary sources and so should not be included or it is it's just that editors seem to think it's acceptable to source it to crappy "official" sources and myself would likely have just removed it if an editor brought it to BLPN and fought to keep it out until an editor acceptably sourced it. It's good that this eventually happened but it should not have taken an ANI thread for that to happen. If you're fighting to keep a living person's personal information an an article you should be the one finding the sources, not the editor you are reverting. Nil Einne (talk) 06:50, 15 May 2022 (UTC)
I should clarify it's possible in some cases evidence that the subject is trying to conceal their name or not trying to conceal their name may be relevant. But this is only likely in certain cases, such as when there are very few sources covering. It doesn't matter when there are no reliable secondary sources, nor if a lot of them. Also thinking about this more IMO this is serious enough that I'm hoping we get rapid correction from the editors concerned since if we don't, I could see a BLP topic ban in order. For that reason, I've given discretionary sanctions alerts to the two editors involved, as well as to Ravenswings who while not involved expressed some extremely concerning views here which as I said are not at all in accordance with BLP policy. It may be that Ravenswings thinks such things but fortunately does not involve themselves on adding or keeping real names in articles so it's not an issue and if so I apologise. But it seemed better to be safe than sorry, if these editors do exhibit non BLP compliant editing in the future, it would be easier to deal with under DS rather than needing a community ban IMO. Nil Einne (talk) 07:17, 15 May 2022 (UTC)
Nil Einne I am NOT the one who revert the info, pls check the article history page and read the comment on this discussion first prior messaged on BLP DS alert me on my talk page.[
Both user Sorry sir, that's classified information and Nil Einne didnt check the article history log and jumped into ANI immaturely on me. Please check first or come to my talk page or article talk page (ping pls) and discuss prior this uncall for ANI..[User:Cassiopeia| Cassiopeia]] talk23:25, 15 May 2022 (UTC)
@Cassiopeia: I was aware you were not the one who reverted the OP. However you were the one who falsely accused the OP of vandalism. [258] I don't know why the OP reverted your attempt at updating the scoring information [259] but it's clear from their edits that they were primarily trying to deal with a BLP violation they had identified. The most likely reason considering your edit was the most recent one at the time is as a new editor, they were trying to work out how to fix the article an edited an old version or used the undo button not understanding that the BLP violation had been there for a while. Whatever the case, it was inappropriate for you to accuse the OP of vandalism since despite their mistake, their edit was constructive since they were dealing with a BLP violation which is far more serious than some dumb ranking update. The fact you did not revert them dealing with the BLP violation is no excuse for you to falsely accuse them of vandalism. You then come to this thread after the OP had already explained what they were trying to do and given enough information that any editor with knowledge of BLP should have recognised they were dealing with a BLP violation. But instead of apologising to the OP for your false accusation of vandalism and for not noticing or dealing with the BLP violation yourself earlier, and thanking them for identifying a BLP violation, you defend your actions. You said that "The full name is support by independent, reliable sourced content" but while this may be true now, there were no inline citations for the full real name at the time which was what the OP was trying to deal with. Lacking such inline cites for the alleged full real name of a living person is simply not acceptable and is an urgent BLP problem that needs to be dealt with as the OP did. Any editor who wishes to add such information (back or initially) needs to be adding such inline cites, not just claiming they exist. And while you falsely accused the OP of vandalism, at no stage did you warn the editor who added back the BLP violation. You boast how you're an expert on MMA articles. I know very little about MMA, but I know enough to recognise that a large number of people involved are living people. Therefore if you're an expert on MMA related articles you need to also need to have good familiarity with BLP. So you should be recognising BLP violations more easily than the OP not the other way around. But instead it's clear you've failed to recognise this BLP violation and came here and faulted the OP when the only made a few minor mistakes in particular accidentally reverting your ranking update, identifying the wrong policy and coming to ANI instead of BLP. But these are all minor issues compared to the fact you and two others appeared to think it was perfectly fine for our article to have a BLP violation just because the sources probably existed somewhere but had not yet been found at the time. So yes my BLP DS alert was entirely appropriate as was my earlier comment. To put it a different way, if you're going to be "I am an experienced MMA editor" who is "I am here to help", then you need to either familiarise yourself with BLP, or stop editing MMA articles there's no two ways about it. To be clear, I've avoided calling this a serious BLP violation since it seems clear sufficient sources exist to allow inclusion of the name. However it was a very obvious and all too common one that could have easily been a serious BLP violation. Any editor with basic familiarity with BLP needs to recognise that sourcing an alleged real or full name to a scoring sheet or some other primary source is not acceptable in any way and that these are the sort of problems which can easily be serious BLP violation if acceptable sourcing doesn't exist. Actually there is just one case at BLPN which was dealt with by oversight. Nil Einne (talk) 13:00, 16 May 2022 (UTC)
Nil Einne I suggest you again, to read the whole message on this threat to understand why I place the warning on editor page prior jumping into conclusion. I didnt revert, an you place a BLD DR on my talk page which is a false accusation. Please do "read" and check first prior all this uncall for message and misunderstanding. This whole ANI on my was the editor didnt check carefully on the history log and assuming of what happened, and you did the same here. To state I am an experienced MMA editor and provide assistance to the editor who is new to Wikipedia/mma article editing is a "friendly" toward the new editor and this is the way we try to help other editors in Wikipedia - you read too much into what I said and misunderstand the point. Cassiopeiatalk23:28, 16 May 2022 (UTC)
This is mostly offtopic ANI, but since the discussion is here, just a brief explanation of why this is the sort of thing which editors who regularly edit BLPs need to recognise as a problem. There are some areas and cases where it's very common for pseudonyms to be maintained with no reliable secondary sources using the real or full name of this person. One obvious area is with actors in adult films. Some editors insist on trying to add real names, using atrocious sourcing like trademark documents or other legal document, something that is completely unacceptable. To be clear, while that may be the most common area, by no means is it exclusive, there was a case I dealt with in 2021 of a singer who only discloses (part of?) her given name where editors were trying to add the full name based on ASCAP records and sheet music. And very recently, there's a case at BLPN which I wasn't involved in but where oversight got involved. Note that in this case the name is said to be in one possibly reliable secondary source, although the article on the person does mention a conviction so in some ways it's more severe but ultimately that doesn't affect whether it's a problem. Anyone who spots such problems with real or full names that are not acceptably sourced should be fixing them, either by finding sufficient reliable secondary sourcing or if there's none probably requesting revdeletion or maybe even suppression/oversight. At the very least, removing the info until it's dealt with is appropriate. It may be in MMA it's very rare that the full and/or real name is not in reliable secondary sources. If you know that but the sourcing is a problem then you still need to either fix it by finding those sources or remove it until someone does. Nil Einne (talk) 13:55, 16 May 2022 (UTC)
[265] Attempted to make the Persian connection less certain by adding his own word "probable"
[266] Removed sourced info by a high quality source from De Gruyter, dismissing its author as a "nationalist who denies ancient sources should not be given a platform on Wikipedia"
[267] Removed sourced info which mentions the Iranian origin of the name Tigranes
The editor has continuously ignored any suggestions I have made to look at WP:NTOUR, and is being disruptive on tour articles as well as adding unsourced material. He has been using multiple IP addresses previously, and has been doing this for almost a whole year. An example was changing venues on the End of the Road World Tour despite there being sources that they were not playing at the venues he changed them to, using the excuse that "he wants them to play there in open air venues". I suspect that this is vandalism as well as not taking WP:CRYSTAL into consideration when adding additional dates that never happened but said was "predicted" despite no sources showing that it happened. He would also revert non-notable articles that had been redirected before, for the sake that he wants to "keep it".
I will point out one more thing before I leave it here, that under the IP 187.87.77.43 (talk·contribs·deleted contribs·filter log·WHOIS·RDNS·RBLs·http·block user·block log), he was placing tour tables into album articles which are supposed to go in its own article. I had reverted them as it was disruptive, and the IP began to add them back, using personal attacks towards me and a few other editors in the edit summary. As stated before, this has been going on for almost a year. HorrorLover555 (talk) 19:30, 16 May 2022 (UTC)
@HorrorLover555 I blocked for block evasion. I don't think there's much that can be done about the IPs unless they are recently active. If you see this editor again you should be able to report to WP:AIV for obvious block evasion, just link to the previous account and a couple edits for WP:DUCK. Galobtter (pingó mió) 02:30, 17 May 2022 (UTC)
Page move user right revoked after good-faith RM close
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.
Admin @El C: revoked my page move user right after my close of an RM at Ukrainian Insurgent Army war against Russian occupation (link to the RM see also User_talk:Vpab15#Page_move_user_right_revoked). I thought there was a consensus that "Russian" should be removed from the title so I chose one of the many options that corrected that. But even if the close was really bad (which I don't think it was), removing the user right for one mistake seems like a huge overreaction and totally disproportionate. To be clear, the revocation was done without any kind of discussion with me about the close. Honestly, if any mistake when editing will be harshly punished, I don't think I want to bother contributing. To sum up, I'd like to have my user right reinstated and I think admins shouldn't punish other editors for good faith edits without giving them a chance to correct or explain themselves. Vpab15 (talk) 21:28, 30 April 2022 (UTC)
It wasn't a punishment, it was to prevent future disruption (AEL diff). And I'm also not sure it's just one mistake, as they claim, seeing as pretty much the only discussion threads displayed on Vpab15's talk page right now are about contesting their closures. This user did not make a substantive effort to show that they understand the reasons for why it was a bad close and provide assurances against repeating it (here). They don't seem to understand what a WP:SUPERVOTE is, still. Which displays a fundamental misunderstanding on their part, one which I continue to argue needs to be sufficiently addressed if they are to be given back this use right (which used to be part of the admin toolkit, lest we forget). El_C21:56, 30 April 2022 (UTC)
I realize this might be confusing, but I didn't invoke WP:ACDS for that sanction, but rather for the protection actions (diff). I just made a note of it in the log because it was an integral part of related events. Basically, this was a WP:CIR revocation. I had no idea whether your editing at WP:ARBEE/WP:APL is problematic (I still don't). Did the fact that it was a contested ARBEE/APL page (and currently at AfD) exacerbate the problem? Sure, but it wasn't about the topic area, specifically. And again, you didn't inquire about any of that till now. El_C22:22, 30 April 2022 (UTC)
I see. Any misunderstanding is my fault because I didn't inquire. On the other hand you can revoke someone's user right without giving them a proper explanation. Very reasonable. Vpab15 (talk) 22:33, 30 April 2022 (UTC)
No, I still don't understand it. Neither WP:BADNAC nor WP:SUPERVOTE mention anything about revoking someone's user rights. WP:SUPERVOTE explicitly saysIf you believe that a closure reflects the closer's own opinion instead of consensus, civilly ask the closer to revert their closure and !vote by their preferences. Vpab15 (talk) 23:09, 30 April 2022 (UTC)
Anyway, if any admin thinks you should have your page mover user right restored, well, I think it'd be a mistake, but I won't stand in the way. Needless to say, I'm concerned about non-page mover -related closes if this is the approach and your threshold of understanding of WP:CLOSE overall. El_C23:20, 30 April 2022 (UTC)
Criterion #1 mentions a pattern of controversial moves. The revocation was done in response to a single move, so I don't think it applies. Vpab15 (talk) 23:28, 30 April 2022 (UTC)
Right, but then I saw your talk page where prior to me posting, displayed 2 of 3 threads that contested your closes/moves. And you still haven't demonstrated that you understand the problem with the move/close I overturned. You've basically just been arguing procedure about the revocation, but you've said nothing about why it was problematic, what you'd do differently next time. It's a wrongheaded approach which, I'm sorry to say, does not inspire confidence. El_C23:51, 30 April 2022 (UTC)
Yes, I am arguing that the procedure to revoke the user right hasn't been followed. If so, I don't understand why it is not restored. Aren't we supposed to follow the procedures that are in place? Regarding the other contested closes in my talk page, I am happy to provide more info if needed. One of them was taken to a move review that was endorsed, so hardy a smoking gun. In any case, if there is a pattern of bad closes (which I strongly reject), the investigation into them should have been done before the revocation, not after. Vpab15 (talk) 12:08, 2 May 2022 (UTC)
but then I saw your talk page where prior to me posting, displayed 2 of 3 threads that contested your closes/moves on the other hand, only one of those (George I) was actually taken to MRV, and in that case Vpab's closure was endorsed by the community. Colin M (talk) 18:19, 2 May 2022 (UTC)
I think El_C's log entry is really confusing; it mentions four separate actions 1) overturning close, 2) revoking page mover privileges, 3) ECP, and 4) move protect. They added that to Arbitration enforcement log without qualifying which actions were normal admin actions and which were AE actions. Any editor could reasonably assume that the log message was treating all actions as discretionary sanctions. If it is true that the first two actions were normal admin actions, they should amend DSLOG as soon as possible. Politrukki (talk) 13:05, 6 May 2022 (UTC)
This won't be a popular thing to say, but El C's made more than one mistake and no one removed any of his perms. Removing page mover over one bad close (or even three bad closes) seems overly harsh, and punitive, since removing page mover won't prevent future bad closes (you don't need the perm to close an RM). If there were to be a sanction, a TBAN from closing RMs would make more sense, and there are useful things one can do with page mover other than closing RMs. But I think we should respond to bad closes with education/advice rather than removing perms or other sanctions, at least as a first step. Levivich18:30, 2 May 2022 (UTC)
(Not unpopular --> (in response to Levivich’s comment). I believe regular editors are cautious and detour criticizing an editor with more powers over them. Anyway, here is my humble opinion. So prompt removal of rights was a very bad administrative decision even if the action of the closer was a mistake (was it?) (sorry El C, people make errors in their judgements, yes, you too.) - GizzyCatBella🍁18:50, 2 May 2022 (UTC)
El C, I'm not sure this was the best way to handle this. If you think the close was bad, I think it would have been better to go through the established WP:MRV process. If you think there's a systematic problem of Vpab not having the competence to close RM discussions, maybe you could open a discussion to see if there would be community consensus for a topic-ban against them performing RM closures? Removing their page mover right doesn't actually prevent them from continuing to do RM non-admin closes - they can always close a discussion and then list the move at WP:RMT. If this were a truly clueless editor jumping in to RM closure and making an obvious mess of it, then unilaterally overturning their close would be reasonable, but this was a good faith closure by an editor who has been closing RMs for a couple years. (And I say this as an editor who has challenged Vpab's closures in the past, even taking one to MRV.) Colin M (talk) 18:30, 2 May 2022 (UTC)
I'm dealing with a medical emergency, so for expediency, I'll just quote myself:Anyway, if any admin thinks you should have your page mover user right restored, well, I think it'd be a mistake, but I won't stand in the way. Needless to say, I'm concerned about non-page mover -related closes if this is the approach and your threshold of understanding of WP:CLOSE overall. Thanks. El_C20:31, 2 May 2022 (UTC)
Messy situation that could have been handled better perhaps, but ultimately it’s a terrible close that does not even begin to explain its conclusion and instead appears to rely on an articulated personal view that the move is “fixing a problem”. Per WP:RMNAC, an NAC should normally only be done in cases of a clear consensus which not even the closer claimed existed here. Even if such closes were allowed, there would still need to be a very thorough written articulation of how the consensus was interpreted, not just a simple declaration that the move is beneficial. I sympathize with the user and I’m willing to AGF, but competence issues with assessing consensus in the RM area is quite simply usually going to be disqualifying for what is one of the most restrictive user rights on the project. I would not regrant here personally. ~Swarm~{sting}09:52, 3 May 2022 (UTC)
You've also made more than one mistake and no one pulled your PERMs. Arguing that the close was bad is straw manning: no one is arguing that the close was good. Did you want to address whether (1) this is a pattern or one time thing, or (2) why would we remove PM for a bad close, or (3) why we would remove PM for one bad close?Anybody here want to make an argument for why one bad close should result in PM revocation? Like how does that prevent bad closes in the future? Or that it wasn't just one bad close?Should an admin who makes a single bad AFD close be desysoped? Should we remove rollbacker for a single misuse of rollback? If the answer is no, then... I'm openly annoyed that the question is even needing to be asked here. Levivich14:48, 3 May 2022 (UTC)
One argument would be that all it takes is convincing an admin that you'll use the right responsibly in the future to regain it. An admin would have to re-run for RFA, which is clearly a whole thing. In this situation, likely all it would take is an honest "I understand how that close and move was a mistake. In the future I will be much more careful." ScottishFinnishRadish (talk) 14:50, 3 May 2022 (UTC)
When we make one mistake with a PERM, we need to convince an admin that we won't make a second mistake, in order to regain the PERM? Levivich14:51, 3 May 2022 (UTC)
Depends on the severity of the mistake, and the consensus around it. I'm just saying that comparing getting page mover or rollbacker pulled to being desysopped is apples to bananas. ScottishFinnishRadish (talk) 14:55, 3 May 2022 (UTC)
I went into this totally agreeing with you, I nothing short of shocked and outraged that an admin would revoke a perm over a disputed close. I was actually upset, and I shouldn’t have been. Looking into it, I think it’s actually an uncontentious revoke and I 100% agree with it. Discretionarily revoking a perm is a very aggressive, unpleasant action, and no admin does it lightly, but in this case, I genuinely don’t see how there was any alternative. When it comes to subjective close challenges, I’m usually pretty defensive of the closer’s discretion. But here the close wasn’t some sort of mistake, it’s either incompetence or willful misconduct. Framing this in the most favorable light, a page mover is demonstrating that they are not familiar with important policies and procedures in the area of page moving. This is quite simply incompatible with possessing the PM right. ~Swarm~{sting}21:10, 4 May 2022 (UTC)
The reasons for revocation of page mover right are clearly stated at WP:PMRR and it is obvious that a single good-faith mistake is not enough reason. I must also say that I find the lack of civility by two admins quite shocking. Things could have been said much more respectfully. It was really not necessary to repeatedly call me incompetent. Vpab15 (talk) 21:46, 4 May 2022 (UTC)
Per PMRR, the very first sentence, the permission can be revoked for “misconduct”, also I would argue that the issue lies within the purview of #4 anyways; a formal closure performed in your capacity as a page mover, so-designated in the closure statement itself, identifying as a highly experienced and thoroughly-vetted expert in this field. I would further argue that you have demonstrated that you do not satisfy the granting guidelines to begin with and thus a revocation is a procedural matter. I would further argue that none of that matters, per WP:COMMONSENSE, WP:NOTBUREAU, and WP:IAR, we operate based on common sense above all and this is supported by my common sense. I’m sorry if you feel offended, that is sincerely not my intent, but you asked for uninvolved users to investigate and this is my conclusion as an uninvolved admin. IMO you’re not in a position to ask to be coddled, you are the one who betrayed the trust an admin placed in you. ~Swarm~{sting}23:48, 4 May 2022 (UTC)
PMRR #4 says one reason for revocation is:The editor used the permission to gain the upper hand in disputes. It says nothing about competence. Can a single page move be considered participating in a dispute, let alone trying to gain the upper hand? I think the accusation is unsubstantiated and violates AGF. I also think it is very problematic we are still discussing the reason for the revocation. It should have been made clear from the beginning. Vpab15 (talk) 08:17, 5 May 2022 (UTC)
This would be done under criteria 1, failure to determine consensus, or the catch all "misconduct" clause, criteria 4 is unrelated to the issues with your moves. Looking through a few of your other closures there does seem to be a repeating problem with failing to establish consensus properly. This RM [270] in another discretionary sanctions area (Israel-Palestine) is very unsatisfactory IMO, it should have been closed no-consensus. I don't see how that could have been closed as "moving to a more neutral name" when multiple participants expressed concerns that the proposed name was just swapping one POV for another. This closure of a RM here (overturned at move review) [271] is also extremely problematic. I don't see how that discussion could have been read as any kind of consensus at all let alone a "Clear consensus". From just a few days ago we have this closure [272]. Gender and sexuality is another controversial topic area under discretionary sanctions. When closing a discussion where two options are being debated along with the relative merits of COMMONNAME vs up to date terminology I would expect to see a more detailed rationale than "x has more support". 163.1.15.238 (talk) 13:51, 5 May 2022 (UTC)
Multiple users have questioned whether this is in the best interest of the project, so I don't think this appeal to WP:COMMONSENSE/WP:NOTBUREAU holds up. Last month the RM backlog reached an all-time high. I don't think we should be pushing willing editors away from closing RMs unless a) There's clear consensus that their closes are doing more harm than good (considered as a whole - not just focusing on one bad close). b) Other less harsh options have been considered (e.g. mentoring, guiding the editor toward less controversial closes). Colin M (talk) 22:59, 5 May 2022 (UTC)
Good news then, the user is not banned from RMs and may continue to participate there. I am not arguing in support of a TBAN from RM, I am simply explaining why I would not regrant PM at this time. ~Swarm~{sting}05:34, 6 May 2022 (UTC)
You're using the word "participate" but we're talking about closes. Vpab can not only continue to participate, they can continue to close RMs. That's why removing the page mover right doesn't prevent bad RM closes. Levivich14:37, 6 May 2022 (UTC)
Yes, that’s exactly what I meant. Revoking PM does not even do anything to address the user’s participation in RM. It is a bare minimum intervention, and thus I view it as quite lenient, particularly with the caveat that any admin who sees fit can reinstate it without any further discussion. ~Swarm~{sting}01:46, 8 May 2022 (UTC)
You think I made an unforgivable mistake closing the RM in question. It was so bad my PM right had to be revoked immediately and totally out of process. You also see no problem if I continue closing RMs. How does that make any sense? Vpab15 (talk) 12:54, 8 May 2022 (UTC)
Swarm has explained what was wrong with Vpab15's close. But I think removing page mover right was overreaction that makes very little sense in the context. If Vpabl15 would have been asked to temporarily stop closing (controversial) RM's, would they have said no? I don't think so. There was no immediate threat that could not have been resolved with discussion. As Levivich and Colin M argued, if Vpab15's close was so utterly incompetent that page move right had to immediately revoked, why should we allow Vpab15 to continue closing move discussions? I have not seen evidence for topic-banning from move discussions.El_C admonishes Vpab15 for omitting in-depth closing summary. I do think that the RM Vpab15 was sanctioned for should have been closed as "no consensus". However, El_C's summary does not specifically explain how that result was arrived, i.e. they are guilty of what they are accusing Vpab15 of.El_C should refrain from using CIR as a blunt instrument and remember what CIR does not mean. Even if Vpab15's rights were not to be restored now, we should provide them a path to regain the PM right, unless we think they are a lost cause, which is not the case here. Politrukki (talk) 14:11, 6 May 2022 (UTC)
I agree, in addition to the removal of the page mover right, and the logging of it as an AE action, one of the stranger aspects of this is El C's closing statement which admonishes Vpab withContested moves usually should have fairly in-depth closing summaries, but then goes on to close the RM with this as the closing summary:Either way, no consensus and back to the status quo ante, for now., and that's it, nothing else. In addition, C gives a substantive opinion on the title (I don't have an intimate familiarity with the historiography, but probably Soviet should supplant Russian if the current title is kept (?). Or maybe there's a better a title, I dunno.), which is a !vote. The close also references the essayWP:BADNAC, but doesn't mention the one applicable to RMs, which is WP:RMNAC. C full-move-protected the page, which is also an overreaction after one bad move. Finally, it ends with a reference to 500/30, which doesn't apply to this article. There are more mistakes in El C's actions than in Vpab's actions here. Despite numerous mistakes, nobody is suggesting removing any perms from El C. Levivich14:42, 6 May 2022 (UTC)
With regards to your comment about 500/30, discretionary sanctions are Byzantine. Ukrainian Insurgent Army war against Russian occupation might be considered under Antisemitism in Poland topic. The talk page has Antisemitism in Poland warning template because it was added by GizzyCatBella on 27 April, right before Vpab15's close. Standard discretionary sanctions are not authorised for Antisemitism in Poland specifically, but it's a subtopic that falls under EE (standard DS). EE does not have 500/30 remedy, but Antisemitism in Poland does, see WP:APL50030.I don't think we have discretionary sanctions specifically for Byzantine Empire as of yet, but it might or might not fall under EE. Politrukki (talk) 16:14, 6 May 2022 (UTC)
I'm not seeing how a discussion about the title of the article "Ukrainian Insurgent Army war against Russian occupation" could possibly be considered part of the topic area "Antisemitism in Poland", even if the article mentions antisemitism in Poland. (It definitely falls under "Eastern Europe", but as you say, EE doesn't have a 500/30 restriction.) Levivich16:39, 6 May 2022 (UTC)
That's not true. The Second Polish Republic did not exist when Ukraine Insurgent Army was created in 1942. Also, in 1941, Nazis put Stepan Bandera in a Nazi concentration camp. So no, Bandera was not UPA leader. The UPA was a militia who fought against Russian/Soviet occupation from 1942-1960. WWII was over in 1945, not 1960. So the 500/30 does not apply. It was erroneously added, unilaterally (with no discussion), and it should be removed BetsyRMadison (talk) 17:44, 10 May 2022 (UTC)
@Levivich: I agree with you, the 500/30 does not apply to "Ukrainian Insurgent Army war against Russian Occupation." I feel it was erroneously applied to that article & it should be removed. Best regards, BetsyRMadison (talk) 17:08, 10 May 2022 (UTC)
This is a misunderstanding. 30/500 protection can be applied as an AE measure under standard discretionary sanctions, anywhere in the Eastern Europe topic area. ~Swarm~{sting}06:04, 14 May 2022 (UTC)
Good faith is not particularly relevant. This is about an action done to prevent a non-admin from making further controversial page moves. As such, Vpab15 should first acknowledge the error, as nobody here has asserted that the contested page move was correct. Second, Vpab15 should explain how their approach will improve. Third, they should politely ask for their permission to be restored. It may be best to let the dust settle and think about this for a while before going through these steps. The current discussion is unlikely to convince an uninvolved admin to restore Vpab15's permissions. JehochmanTalk13:00, 10 May 2022 (UTC)
This is about an action done to prevent a non-admin from making further controversial page moves. An action that should not be done after one bad page move. One bad page move out of how many bad page moves? What's the error rate? And why the hell would this editor ask for the permission to be restored, or ever want to help us with moves or anything else, after being treated like this? Man you old timer admins are really myopic sometimes. Levivich13:38, 10 May 2022 (UTC)
I am not an admin. If somebody does something troublesome, it's just fine to stop them from repeating the error. This is the definition of "preventative." We are not passing judgement on the editor or their whole history. We are saying, "This was a mistake, please stop and address it before you continue." Had the editor acknowledged the error (or even acknowledged that they might have made an error), I don't think the permission would have been revoked. JehochmanTalk15:04, 10 May 2022 (UTC)
If what you describe actually happened, nobody would be complaining about it. What actually happened is that El C never talked to the user before revoking their perms. See User talk:Vpab15/Archive 1#Page move user right revoked. There was no opportunity to acknowledge the error prior to the permission being revoked. In fact, the OP says this:To be clear, the revocation was done without any kind of discussion with me about the close. So what you're saying just isn't factually accurate.
Note also that this user is not in any prevented from closing RMs. So this doesn't in any way address or prevent bad RM closes, as has been stated repeatedly in this thread. That's why people are saying it was a bad call: there was no prior communication, no warning given, and the action taken is not preventative and doesn't address the actual problem. The problem isn't a mis-use of page mover perms, it's a bad closing statement. Levivich15:22, 10 May 2022 (UTC)
Folks, what I witnessed around here is that regular editors (in general) rather avoid voicing negative comments about administrators. Those who dare are very few. I don't think I have to explain to you why. So you folks, who are in a position of power, please appreciate this constructive criticism, particularly Levivich's, reflect on it and restore the rights revoked due to a poor administrative decision. - GizzyCatBella🍁16:19, 10 May 2022 (UTC)
As I've said before, I appreciate El C's committed admin work in contentious topic areas, but I think this was a series of poor administrative decisions. Some comments:
Mistakes are acceptable for any user right holder. Unilateral revocation is only really acceptable for misuse, gross incompetence, or for inactivity/procedural reasons. For PMR, WP:PMRR outlines 7 criteria for unilateral admin removal without notice or process, and none are met here.
Page mover, as with all other non-admin user rights, is a technical user right. Closing discussions is not a technical task, thus is not within the scope of WP:Page mover, and the editor remains able to close any RM discussion which means the preventative purpose of the revocation is unclear.
Except in limited circumstances, I don't feel it's appropriate to unilaterally overturn closes. As an ACDS action, I think the admin should be able to justify why the unilateral overturning of a close provides a stabilising impact in a contentious topic area, and why it outweighs any concerns of due process (WP:CLOSECHALLENGE/WP:MRV) not being followed. There are a lot of good reasons we have these processes. I cannot see any reasons for avoiding process, or any reason why this move was destabilising in the topic area.
I don't find the close to be a gross error. I think the discussion does show consensus for the nominator's concern regarding the presence of "Russian" in the title, though not a consensus for the proposed title, with disagreement on a suitable alternative title. I would not personally have moved and instead suggested future discussion, but I've seen cases where a move is allowed to a 'better title' with future moves suggested to stabilise on the ideal title. Overall, I think the close is sufficiently within reason to deserve a MRV discussion.
I hope El C (or another admin) restores the page mover user right to Vpab15. Aside from the substantive issues, I'm concerned of the effect sanctioning mistakes has on editor retention. We're a volunteer community that needs good editors, including RM closers where we often have backlogs. Sanctions are not conducive to editor retention, and should be a last resort to prevent disruption to the project where other means fail or are reasonably likely to fail. ProcrastinatingReader (talk) 20:55, 10 May 2022 (UTC)
Re point 2: You are technically right, but in practice lack of Page Mover right precludes you from closing most RMs. A good deal of redirects are nowadays salted for one reason or another (WP:Redirect categorization being the main culprit) so, if you cannot execute pageswap, you must ask someone else to do it for you, which becomes nuisance for everyone soon enough. Substantially, I agree it was a bad removal by El C, and unfortunately, I begin to see a pattern of rushed and overaggressive actions by him, where a simple quiet talk or would do the job better and with much less drama. No such user (talk) 07:14, 13 May 2022 (UTC)
Agree that this was a pretty bad removal and that the right should be restored. Was it a bad closure? Sure, but this is simply not a justified response. Elli (talk | contribs) 00:56, 13 May 2022 (UTC)
Since there are two open threads at WPO that highlight this matter right now, meTa it's better that I provide an updated summary. I recognize that many participants in this thread feel the revocation was a mistake. But Swarm, a PERM regular with 700 actions to my 30, had said above that though originally he wasnothing short of shocked and outraged that an admin would revoke a perm over a disputed close, once he looked beyond its surface, he100% agree[d] with it. He even said that hegenuinely [didn't] see how there was any alternative. As well, above, IP editor 163.1.15.238 has provided other troubling examples.
In my view, a bad close and subsequent move of a contested EE/APL page while it's being challenged at AfD (which is how I found out about this, GCB ping'd me to the AfD at which point I noticed its title didn't match the article) is quite a serious lapse. But, again, any admin is free to reverse my revocation. Re-applying at WP:PERM is also an option, if that doesn't happen. The venue doesn't matter. All it would take is for one admin to feel confident Vpab15 should have the PM right back (presumably, with Vpab15 providing some substance, but maybe not).
I'm certainly not gonna hold any ill will toward any admin who might re-grant it (truly), but I'm just not comfortable reversing myself right now, even with all the pressure. Referring to 163.1.15.238's evidence again, I'm concerned for bad closes/moves going unchallenged due to inertia. That said, multiple people above said that I should slow down, so upon reflation (no pressure!), I'm trying to take that on-board. El_C20:02, 13 May 2022 (UTC)
Countless times on this very page, users are told that when a number of experienced editors are telling them that they are making a mistake then they should correct that mistake, regardless of what they may "know" is right. I don't think anyone has told you to "slow down", I think you've been, quite directly, asked to correct your mistake. Primergrey (talk) 02:45, 14 May 2022 (UTC)
I'll restore the page mover rights. One mistake in closing a discussion is not enough to unilaterally revoke per WP:PMRR, and there's enough agreement above that this wasn't a good revocation.
I'll also go out on a limb and say that I don't think the close by Vpab15 is actually bad. It's a very poorly argued discussion overall, but a couple of the opposition !votes don't make any sense and most of the "oppose" !votes seem to be about whether the article is about actions against Poland too, which is kind of irrelevant to the Russian vs Soviet question that the requested move is mostly about. Honestly, I could see myself very well closing that discussion in a similar way (but maybe better explained), since the people who actually argued Russian vs Soviet mostly agreed on Soviet. But the discussion in unclear enough that NC is also valid.
I definitely don't think El C should've unilaterally overturned the discussion, either. There's no policy that NACs can be unilaterally overturned in general. Galobtter (pingó mió) 03:53, 14 May 2022 (UTC)
IMO It’s been established that the user doesn’t satisfy the granting guidelines. None of my arguments that the right should not be reinstated have been refuted, and yet you’re arbitrarily regranting extremely powerful tools to a user who has demonstrated problematic conduct in the area of specialization. Over what, a procedural technicality that the criteria for revocation were not satisfied verbatim? Galobtter, I feel you betray the best interests of the community here. ~Swarm~{sting}06:13, 14 May 2022 (UTC)
Nowhere in Wikipedia do we we do anything without giving a user a warning or a chance to improve their behavior. Instantly revoking a user right for a good faith, not unreasonable (as I explained) close is not how Wikipedia should work. That's what I mean by WP:PMRR not being met - I don't care that much about the technicalities but thought I'd refer to the relevant guideline, since it does bolster the case for re-granting.
As far as I can tell, your main argument is about violating WP:RMNAC, but that part of WP:RMNAC doesn't actually reflect community practice anymore (as ProcrastinatingReadernotes). Even 4 years ago when I was an active NAC closing WP:RMs I made many close-call NACs and no one had any problem as I long as I explained myself properly, so I don't see how we can fault Vpab15 for making the NAC close. Your other argument is about the close being bad, which as I explained above, I don't quite agree with even if I do think it wasn't the best explained.
I think you also overstate the powers of page mover, and Vpab15 has not actually abused any of the page mover technical powers. So what harm do you think Vpab15 would do with the page mover rights now that they have them? Make controversial closes? As many people have pointed out, that's something they can do regardless of having the right. They were never told to stop making controversial closes, which would be the first step if that's the issue.
I also don't see how you can say I betray the best interests of the community if most of the community that has expressed an opinion above think the revocation was not good. Galobtter (pingó mió) 01:24, 15 May 2022 (UTC)
Swarm, that's a lot of bullshit.it’s been established that the user doesn’t satisfy the granting guidelines – who has "established" it?User who has demonstrated problematic conduct in the area of specialization – Vpab15 has closed many requested moves in the past [273], without issues that I remember; or are you actually referring to El C? As Galobtter pointed out, the close by Vpab15 was actually reasonable and within the spirit of WP:NOGOODOPTIONS guideline. I feel the urge to defend a user who, like myself, has took upon themselves to work upon perennial RM backlog (WT:RM#Size of RM backlog over time), investing their time and energy into a largely thankless job, only to be yelled at by unhappy RM participants, or have their essential perms removed by a rogue passing admin. And you're actually ill-informed about WP:RMNAC: page movers have basically took upon themselves the job of closing Requested Moves, the area which sees very little admin input, and they need more support and less pontification like this.All closures of requested moves are subject to being taken to review at WP:Move review (WP:MR), but the mere fact that the closer was not an admin is never sufficient reason to reverse a closure. Indeed, many high-profile, controversial move requests have been closed as NACs, taken to WP:MRV, and affirmed there.No such user (talk) 08:46, 16 May 2022 (UTC)
Nonsense. I’ve done nothing but provide the most objective analysis I could, based on written guidelines and longstanding norms. My arguments were multiple, thorough, and not refuted, my concerns have not been addressed at all, nor any sort of convincing rationale established for re-granting the user right. That’s fine, we all disagree with each other all the time. Now I am simply documenting my strong dissent for the record, in case there are any further issues and we need to revisit this in the future, and I hope it won’t be necessary. Doesn’t change the facts, and the fact is that there are numerous problems here which would be disqualifying for PM for any other user. ~Swarm~{sting}13:18, 16 May 2022 (UTC)
Using the word "fact" to describe a minority opinion doesn't make the opinion any more persuasive. Levivich13:45, 16 May 2022 (UTC)
Anyone who actually knows me would know that, without a doubt, I would never use the word “fact” to describe even the strongest opinion. I use the term “fact” to describe objective facts, nothing more. ~Swarm~{sting}05:23, 18 May 2022 (UTC)
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.