Revision as of 09:36, 31 October 2024 view sourceMatticusmadness (talk | contribs)Extended confirmed users3,139 edits →Lifting my limited topic ban and my mentorship: Give him some ROPE, I think he’ll build a bridge.Tags: Mobile edit Mobile web edit Advanced mobile edit Reply← Previous edit | Latest revision as of 23:12, 17 January 2025 view source Buffs (talk | contribs)Extended confirmed users, Pending changes reviewers, Rollbackers27,494 edits →Sander.v.Ginkel unblock request: oppose | ||
Line 1: | Line 1: | ||
{{pp-sock|small=yes}} | |||
<noinclude><!-- Inside the noinclude, because this page is transcluded. -->{{User:MiszaBot/config | <noinclude><!-- Inside the noinclude, because this page is transcluded. -->{{User:MiszaBot/config | ||
|algo = old(7d) | |algo = old(7d) | ||
|counter = |
|counter = 368 | ||
|archive = Misplaced Pages:Administrators' noticeboard/Archive%(counter)d | |archive = Misplaced Pages:Administrators' noticeboard/Archive%(counter)d | ||
|maxarchivesize = 700K | |maxarchivesize = 700K | ||
Line 31: | Line 32: | ||
{{Clear}} | {{Clear}} | ||
{{Admin tasks}} | {{Admin tasks}} | ||
__TOC__ | |||
</noinclude><!--Here because there's a bug in mobile, please don't remove--> | </noinclude><!--Here because there's a bug in mobile, please don't remove--> | ||
== |
== Sander.v.Ginkel unblock request == | ||
{{atop|There is a (weak) consensus here to unblock, but nearly every editor has noted that there is a short amount of ] and any future issues will lead to a re-imposition of the block by any administrator. ] (]) 22:46, 25 October 2024 (UTC)}} | |||
{{userlinks|ThecentreCZ}} | |||
The following is copied from ] on behalf of {{u|Sander.v.Ginkel}}: | |||
Copied from their user talk page: | |||
{{tqb|I have made serious mistakes. I regret it and say sorry for it. I fully understand why I have been blocked. My biggest mistake that I copied-pasted content from articles to other articles, that led to a BLP violation. I have also misused other accounts as suckpuppets: ] and ] (note that the two other accounts –- ] and ] -- at ] was not me. ) In addition, my work was too focused on quantity, rather than quality. I apologize to those who had to do some cleaning up for me. | |||
Whay do I want to come back? And do I deserve it? I can show that I can make constructive content. I made some edits and created pages under the IP address 82.174.61.58, that was not allowed; and was blocked. It is not good that I made edits under an IP address, but I appreciated that some users (], ], ]) stated they liked the content I created and/or that they offer the opportunity to have me back (see at ]). I made the same mistakes on the Dutch Misplaced Pages (where I misused the same accounts). At this Misplaced Pages I bot back my account and I am editing the Wikipeida I’m also editing at simple.wikipedia.org (see ]). I have created over 900 pages (see ]), (1 page being deleted). I like to create articles from historic work on old sources, for instance ], ], ], ] or the event ] that is barely mentioned at the English ]. Around 100 pages have been (literally) copied to the English Misplaced Pages by several users. I'm also editing Wikidata, see ] and ]. | |||
{{tq|Hello, I would like to ask administrator to put forward my request to the Administrators' noticeboard for unblock, according to WP:Standard offer. I have been contributing to other Wikimedia projects meanwhile as is recommended for users at unblock requests. <br><br> I would like to acknowledge my misconducts and mistakes like of inproper citations, especially that I did considered List of banned political parties and also other instances of lists as Stand-alone list, because I didn't take in consideration that there is also column which contains ideologies and year of occurance and I did not given proper citation in my first edits. I then reverted the edit more than once which let to the editor to report it as an incident there. Sadly, I didn't get a chance to properly repond to the most of the instances discussed and apologize again in the Administrators' noticeboard/Incidents, because I was blocked for a period of month on the same day that the incidents were raised, on 15 March 2024, and I couldn't respond anymore. Factically it was somehow connected to the instance of incident of other blocked user, who probably used his account for singe-issue editing, but he also did other benefitial contributions to Misplaced Pages so I just presented my concerns there. In the case of disruptive editing and and insults, I would like to say that I will no longer edit contentious topics and use such language I used. I would like to apologize for about 3 vulgar words in the last 5 years I used, which could have been rightfully taken as insults and about 8 edit disputes, where I wrongly accused someone of something they have not ment. I agree that vulgar-insulting words are unacceptable and it was proper reason for blocking. It was very bad of me, but as of my editing I many times got into situation that people removed sourced information and it is not always easy to keep cool thinking and distuinguish proper and inproper editing, as I did many sourced corrections in about 10,000 edits I've made. In the matter of what I will be participating in the future, as I created about 80 articles in the past on English Misplaced Pages, I will continue to create only sourced articles with proper information and I will not participate in any disputes and in disagreements in such disproportionate language I did in the past. Thank you. ThecentreCZ (talk) 16:48, 14 October 2024 (UTC)}} | |||
However, as I have learned from it, I will never use multiple accounts anymore and adding controversial content without doing a proper fact-check. I will always listen to users, be constructive and be friendly. I will make sure you will not regret giving me my account back. I would like to work under the account ].}} | |||
] (]) 18:12, 15 December 2024 (UTC) | |||
:'''Support unbanning and unblocking''' per ]. ] (]/]) 18:31, 15 December 2024 (UTC) | |||
* Quoting my SPI comment ]: {{tq2|I was torn on this. The IP does not seem to be creating the sort of low-quality BLP stubs that SportsOlympic was. If this were "just" a case of ''block'' evasion, I'm not sure I could justify a block of the IP as ] of any disruption, and would be inclined to either ignore it or block but offer a non-] unblock to the main account. However, Sander.v.Ginkel is ''banned'', and under the SportsOlympic account has caused significant disruption just six months ago. Evading a ban is an inherent harm, as it undercuts the community's ability to self-govern. Furthermore, it would be unfair to the community to allow someone to contribute content, particularly in a DS area as much of the IP's recent edits have been, without the community being on-notice of their history of significant content issues. (And there is still troubling content like ].) I thus feel I would be defying the mandate the community has given me as an admin if I did anything but block here. ... FWIW, Sander, I could see myself supporting an ] unban down the line, although I'd recommend a year away rather than six months.}}That sentiment is what I eventually wrote down at ], which mentions the same principles being relevant in unban discussions. And now that this is before the community, with even more time having passed, I have no problem unbanning: The post-ban edits, while problematic in that they were sockpuppetry, do show evidence that Sander has learned from his mistakes, and thus a ban no longer serves a preventative purpose. Looking back at the one hesitation I mentioned above, I think my concern was that it was an ] violation that seemed credulous of a pro-Russian narrative; but if there's no evidence of that being part of any POV-pushing, then I don't see it as an obstacle to unbanning. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 18:33, 15 December 2024 (UTC) | |||
*'''Support''' per above.] (]) 18:37, 15 December 2024 (UTC) | |||
*:Endorse one account proviso. ] (]) 20:28, 15 December 2024 (UTC) | |||
*I'm a little bit concerned by the sockpuppetry returning earlier this year: ]. However, that is over 6 months ago. I would '''Support''' with the obvious proviso that the user be limited to 1 account and that IP editing may be scrutinized for evidence of ]. — ] ] 20:16, 15 December 2024 (UTC) | |||
*'''Support''' with provisions per above. Worth keeping a close eye on, but they ''seem'' to have understood the problems with their behavior and improved upon it. ] ] <span style="color:#C8102E;"><small><sup>(])</sup></small></span> 07:07, 16 December 2024 (UTC) | |||
*'''Support''' I've previously spoken in favor of the subject as well. ] (]) 09:15, 16 December 2024 (UTC) | |||
*'''Oppose'''. "My biggest mistake that I copied-pasted content from articles to other articles, that led to a BLP violation. " That wasn't the biggest mistake by far. You made extremely negative claims about sportspeople based on internet rumors. Apart from this, the first article I checked on simple, , is way too close paraphrasing of the source. has very sloppy writing, "He started his business alone 1980 built so his horse stable "Hexagon" in Schore. " is just nonsense. Copyvio/close paraphrasing seems to be a recurring problem, has e.g. "Zwaanswijk is regarded as one of the most respected post-World War II visual artists of Haarlem and his work had a profound influence on the local art scene." where the source has "Piet Zwaanswijk was een van de meest gerespecteerde na-oorlogse beeldend kunstenaars van Haarlem. Zijn werk had een diepe invloed op de lokale kunstscene". I don't get the impression that the earlier issues have disappeared. ] (]) 11:45, 16 December 2024 (UTC) | |||
*'''Support''' User seems to have recognized what he <!-- before someone complains about my use of the gender-neutral he, this user is male per what they've configured settings to be --> did wrong, has edited constructively off enwiki. ''']]''' 18:52, 17 December 2024 (UTC) | |||
*<s>'''Weak Support''', the crux of the issue was three-fold: creation of low-quality sports stubs (including what Fram said), persistent IDHT when asked to fix them, and sockpuppetry. I recall I identified the SportsOlympic sock in a tangential ANI thread a couple of years ago. It appears he has edited constructively elsewhere. I would like to see a commitment to one-account-only and a commitment respond civilly and collaboratively when criticized. ] (]) 15:45, 18 December 2024 (UTC)</s> | |||
:*'''Oppose''', I am convinced by the further discussion below that S.v.G is not a net positive at this time. ] (]) 14:11, 24 December 2024 (UTC) | |||
* '''Support'''. Completely support an unblock; see my comment ] when his IP was blocked in April. ] (]) 17:25, 18 December 2024 (UTC) | |||
*'''Oppose'''. Sander and his socks created literally thousands of poorly-written and/or potentially-copyvio pages on (very frequently) non-notable sports topics. I don't see evidence in his Simple Wiki contribs that his writing has improved, and for someone with his history of non-notable subject choices I would want to see ''clear'' evidence that these creations are supported by WP:SUSTAINED, non-routine, IRS SIGCOV. Articles like may well be on notable competitions, but with content like {{tq|On 20 March the Women's Fencing Club gave an assaut, in honor of the visit of the Dutch team. As seen as an exceptional, mr. de Vos was a the only man allowed to visit the women's club.}}, and all sources being from 20 or 21 March 1911, we can be confident that verifying and rewriting the mangled translations and searching for continued coverage will be a huge pain for other editors. And going from the en.wp AfD participation I'd also anticipate the same combativeness and time wasted explaining P&Gs to him in that area as well. Given the volume of his creations, I don't think it is fair to foist all the extra work that would come with overturning the ban onto other editors without a much more thorough evaluation of his Simple Wiki contribution quality. ] (]) 02:34, 19 December 2024 (UTC) | |||
* Currently '''oppose'''; open to a change of view if some explanation and assurances are given with regard to the points Fram raises. There is no point in unblocking a problematic editor if it appears that they may well continue to cause issues for the community ~ ''']'''<sup>''']''']</sup> 12:59, 19 December 2024 (UTC) | |||
* '''Support''' but keep an eye on contributions off ENWP. ] (]) 17:11, 23 December 2024 (UTC) | |||
*:{{yo|Ahri Boy }} Not sure we are concerned with contribs off ENWP. ] (]) 18:27, 23 December 2024 (UTC) | |||
*::He might appeal on Commons later if the appeal here is successful, so there would be a cooldown before doing there. ] (]) 01:15, 24 December 2024 (UTC) | |||
*'''Oppose''' per Fram on close paraphrasing, JoelleJay on sourcing/writing quality, and my own observations on English-language proficiency (I see very recent sentences like "]"). At an absolute minimum I would need a restriction on article creation (to prevent the low-quality mass creation issues from recurring), but these issues would be a problem in other areas too. I think continuing to contribute to simple-wiki and nl-wiki would be the best way forward. ] (]) 01:34, 24 December 2024 (UTC) | |||
*:He was once blocked on NLWP for the same sockpuppetry as here before. I don't even know that he may be offered SO there. ] (]) 10:16, 24 December 2024 (UTC) | |||
*::See . ] (]) 10:22, 24 December 2024 (UTC) | |||
*'''Oppose'''. Like Fram, JoelleJay, and Extraordinary Writ, I have concerns about their competence with regards to copyright, notability, and simple prose writing. I think an unblock is likely to create a timesink for the community, who will be forced to tie one eye up watching both of his hands. ♠]♠ ] 08:41, 24 December 2024 (UTC) | |||
* Come on – it's been nearly ''seven years'' since the ban – why can't we give another chance? His articles from when he was an IP seemed quite good (and much different from stubs which seem to have been the problem), from what I remember (although they've since been G5'd). ] (]) 16:35, 24 December 2024 (UTC) | |||
*:S.v.G. needs to be reevaluated. He needs to clarify that the purpose of return is genuine, constructive, and one account only. He hasn't made any contributions to Commons because he was blocked. ] (]) 19:55, 24 December 2024 (UTC) | |||
*:: I think saying that {{tq|I will never use multiple accounts anymore}} and that he wants to {{tq|make constructive content}} would indicate that {{tq|the purpose of return is genuine, constructive, and one account only.}} ] (]) 19:59, 24 December 2024 (UTC) | |||
*:::For the meantime, he should stay at Simple and NLWP for another six months to make sure no suspicions will be made before appealing under SO. ] (]) 20:07, 24 December 2024 (UTC) | |||
*:But it's only been three years since he was mass-creating non-notable stubs with BLP violations and bludgeoning AfDs with his SportsOlympic sock. He then edited extensively as an IP, got banned for 18 months, restarted within two weeks of that ban ending, and made another 1000+ edits until his latest IP ban in spring 2024. After which he immediately invoked the (laxer) equivalent of the SO on nl.wp... ] (]) 21:07, 24 December 2024 (UTC) | |||
*:: And he admits that he was {{tq|too focused on quantity, rather than quality}}, apologized repeatedly, and his creations as an IP showed that he was no longer focused on {{tq|mass-creating non-notable stubs}}. ] (]) 21:18, 24 December 2024 (UTC) | |||
*'''Support''' With the above mentioned provisions. Seems like a genuine, good faith, attempt to ]. <span style="font-family: Trebuchet MS;">'''] ]'''</span> 04:44, 25 December 2024 (UTC) | |||
*'''Support''' - Like a lot of behavioral issues on this site, I think it all stems back to the general public seeing this site as an all-inclusive encyclopedia and some users here seeing the site as a celebrity encyclopedia. If the user becomes a problem, action can be taken again. Let's see how it goes. ] (]) 20:03, 25 December 2024 (UTC) | |||
*'''Oppose''' per Fram and PMC. <span style="white-space: nowrap;">—] <sup>(]·])</sup></span> 18:52, 29 December 2024 (UTC) | |||
*'''Question''': Is SvG the same person as {{U|Slowking4}}? There has been an odd connection between the two in the past; I think it was first noted by ]. ☆ <span style="white-space:nowrap;font-family: Papyrus">]</span> (]) 22:58, 29 December 2024 (UTC) | |||
**No. ] (]) 23:01, 29 December 2024 (UTC) | |||
*'''Support'''. This appears to be a good-faith attempt at a return, and looking through the commentary here I don't see evidence to suggest continuing the ban and block are preventative. - ] <sub>]</sub> 23:44, 4 January 2025 (UTC) | |||
*'''Oppose''' basically per ], particularly the evidence that their MASSCREATE/socking/evading behaviour was carrying on as recently as spring 2024. If/When they return, it should be with the requirement that all their articles have to go through AFC and that they won't get ] without a substantive discussion (i.e., no automatic conferring of autopatrolled - they have to request it and disclose why this restriction is in place when doing so). ] (]) 16:46, 8 January 2025 (UTC) | |||
*It does look like a good-faith desire to return and work on Misplaced Pages. And I would just want to add that Misplaced Pages needs such a fruitful article creator. Especially since ] was severely trimmed several years ago, and probably thousands of sportspeople articles have since been deleted.<br />'''Support'''. (I am not an admin, so I am not sure I can vote. I can see some non-admins voting, but I'm still not sure.) --] (]) 14:26, 10 January 2025 (UTC) | |||
*'''Conditional support unblock''' (non-admin vote- if I'm not allowed to vote then please just unbold this vote): add editing restriction for them to use ] for article creation, and this restriction can be reviewed in 6-12 months if their article creation has been good. Their article mass creation required one of the largest cleanup jobs I have seen on here, and we certainly wouldn't want the same mass-created quasi-notable articles created again. ]] (]) 17:05, 10 January 2025 (UTC) | |||
*'''Support''' I can't repeat what Beaniefan11 say enough: "Come on – it's been nearly ''seven years'' since the ban – why can't we give another chance? And he admits that he was {{tq|too focused on quantity, rather than quality}}, apologized repeatedly, and his creations as an IP showed that he was no longer focused on {{tq|mass-creating non-notable stubs}}." This should assuage any doubt in the mind of the reviewing administrator. ] (]) 15:01, 13 January 2025 (UTC) | |||
*'''Oppose''' Claims of "It's been seven years!" fall on deaf ears when you find out he's been socking all along and as recently as a year ago. Fram and PMC have good points as well. Show some restraint and understanding of your block and ] is yours. ] (]) 23:11, 17 January 2025 (UTC) | |||
== Spider-Man: Beyond the Spider-Verse - draft article about a future film seems to be a long-term draft == | |||
I have not come across a situation like ] before. Maybe this is fairly common and I have just missed it. | |||
]. <sub>signed, </sub>] <sup>]</sup> 17:32, 17 October 2024 (UTC) | |||
It is a draft article about a film that can not have an article, per ]. I think the idea is that there is some valuable content there and it would be a shame to delete it when it seems likely that the film will enter final animation and voice recording in the next year or so. | |||
*That is a pretty messed up discussion, and past. Still, I'm inclined to accept this with the understanding that there will be a short WP:rope for future incivility, and a low threshold for refusing to source content. For me, the saving grace is you also have a history of creating worthwhile articles. I don't care if your mind is "politically incorrect", however, I do mind when it comes out in your interactions with others here, which is disruptive. Honestly, that is why you got the indef block; not the sourcing; it was the comments re: autism/retard, and by community standards, it was a perfectly valid block. Editors here have a very low tolerance for that stuff, even when it is said in jest/hyperbole/as slang. '''If''' you can restrain yourself, then I'm fine with an unblock. My guess is that not everyone would agree, but we aren't here to punish "wrongthink" (as a lot of people use terms in RL that wouldn't be acceptable in this public forum). We do need to enforce a reasonable level of civility which this clearly breached, in order to build an encyclopedia. ] - ] 07:39, 18 October 2024 (UTC) | |||
*It's fine to unblock TCCZ, but certain restrictions might apply. Insulting other editors is a huge mistake, TCCZ. I consider '''weak support''' for the unblocking. I hope TCCZ will not repeat the same mistake he did before. ] (]) 08:52, 19 October 2024 (UTC) | |||
*'''Support unblocking''' as editor seems to understand why they were blocked and that what they did was wrong. It must be understood that such unblock is on pain of swift redoing should further offences occur, but let's at least give a chance here. ] (]) 15:21, 19 October 2024 (UTC) | |||
*'''Comment''' I'll leave an opinion on this soon but just want to point out the ] that got them indeffed. It's important to understand what this user had actually done that resulted in them getting blocked. ] <span style="font-size:small">(] • ])</span> 16:53, 21 October 2024 (UTC) | |||
**I'm unsure why the user is mentioning the amount of uncivil comments they've left over the years. They certainly deserved an indefinite block for their actions but considering that they seemed to have apologised for that and have promised to not do it anymore, I agree with Dennis Brown on giving them ] to see if they have improved their behavior. ] <span style="font-size:small">(] • ])</span> 18:23, 22 October 2024 (UTC) | |||
::Rosguill had already posted this above, so I'm assuming everyone opining had already read through. ] - ] 02:48, 22 October 2024 (UTC) | |||
:'''Weak Support:''' If this is admins-only, then delete this and notify me on my talk page. If not, then I'll input my opinion. | |||
:The user seems like he's apologized for what he's done, and I think WP:ROPE applies. I say that we give him a second chance, but if he makes any edits in bad faith, he gets hit with a block. ] (]) 09:42, 25 October 2024 (UTC) | |||
*'''Weak support''' I'm fine with the arguments per Dennis Brown. Short rope...make the best of it. ] (]) 20:16, 25 October 2024 (UTC) | |||
{{abot}} | |||
The problem is that it is attracting the sort of speculative edits from IPs that we want to avoid. Both on the draft and the talk page. | |||
== IBAN appeal == | |||
I became aware of this because there is a request at ] to EC-protect the talk page. But it makes me think we should have some kind of protection for the draft too. But I can see arguments for weaker than ECP (speculation is just by IPs) and for stronger... like... why are people editing it anyway? Maybe there are reasons I am not aware of. | |||
I would like to request an appeal of the two-way involuntary interaction ban between myself and {{u|MaranoFan}}. It was imposed by the community a year ago . The conflict originated in the context of nomination pages like FAC. I wouldn't interact with them at those types of venues in the future anyways, and I don't see why replying to one another in a WikiProject discussion or something similarly low-stakes would lead to further conflict. To my knowledge there have been no violations of the IBAN in the year since it was active. I genuinely believe it has served its purpose; let's move on. ] (]) 04:50, 18 October 2024 (UTC) | |||
Is anyone more familiar with how we got here? Anyone got any arguments for or against applying semi, EC or full protection to the draft and its talk page? | |||
*'''Weak support''' - As long as those two people are moving on for a long, it is not useful to let IBAN in place. ] (]) 07:07, 18 October 2024 (UTC) | |||
*'''Oppose''' - The IBAN discussion was reopened and reinstated after being closed once, because some thought it was also necessary to prevent drama on noticeboards and stop the wastage of community time. The fact that this has not been acknowledged in the opening statement looks to me like dodging blame and does not instill me with confidence that that behavior would be avoided. I would have appreciated <s>being reached out to through email or</s> something else but, alas, ANI has been taken as the venue directly without reaching out to <s>me or</s> any individual admin to waste less community time. IBAN remains necessary.--'']]'' 07:19, 18 October 2024 (UTC) | |||
:Since my participation on the Carey article has been brought up, it is related to efforts to save it from losing FA status (I stumbled upon the FARC since while I was doing research for ]). I started helping there because the comments there were not being engaged with. Authorship is looked at to determine major contributors, and Heartfox's shows up as 2.8% which doesn't really qualify (even I have 1.1%). Anyways, on the topic of the IBAN itself, since there is no admission of wrongdoing and they feel the necessity to assert that their original escalation to ANI was "valid", it is absolutely still necessary.--'']]'' 01:05, 20 October 2024 (UTC) | |||
::MaranoFan, I said above that "I genuinely believe it has served its purpose". This was me saying I am acknowledging my responsibility; ie the IBAN had a purpose. The second ANI was unquestionably valid as it led to the exact thing I suggested and this was later affirmed at AN, so it was not a waste of time even though I understand your point of view. MaranoFan, you are one of the rare people on Misplaced Pages who actually improve the project by writing quality articles. I respect you more than 99% of other editors and wish we could move past this era. Sincerely, ] (]) 02:49, 20 October 2024 (UTC) | |||
*:{{tq|I would have appreciated being reached out to through email or something else but, alas, ANI has been taken as the venue directly without reaching out to me}} I don't think this is a reasonable expectation (without comment on the merits of your other thoughts), because it would be a ''de facto'' breach of the IBAN. We don't expect IBAN appeals to be preceded by an IBAN violation. ] (]) 14:16, 18 October 2024 (UTC) | |||
*'''Oppose'''. I don't know all the history of this, but it doesn't seem wise to lift an IBAN if one of the parties objects. We've got 6,898,024 articles; surely there's enough room for both parties to find stuff they're interested in without having to be editing the same pages. ] ] 17:11, 19 October 2024 (UTC) | |||
*:Well right now anytime I edit ] in the future, which is an article to which I am one of the top-ten authors and is one of my top-ten most-edited articles, I have to go back to the 30 edits MaranoFan made yesterday every time and ensure I don't change anything that they happened to add or get potentially blocked for IBAN violations. This is very discouraging to my activity on Misplaced Pages. ] (]) 19:37, 19 October 2024 (UTC) | |||
*::So it seems like the solution there is to ] both of you from that article. ] ] 20:23, 19 October 2024 (UTC) | |||
*:::There's no history of edit warring or content disputes so that seems completely excessive. Both users are members at ], so "We've got 6,898,024 articles" doesn't apply here. The IBAN is preventing improvements to articles when both editors have to tread over eggshells when editing even though the IBAN had nothing to do with content. MaranoFan should be able to fix a typo or a misplaced link in an article I wrote so articles can be improved, and vice versa. To continue an IBAN in part because I opened a valid ANI thread over a year ago and because I am appealing the IBAN to the community instead of an individual admin (which is not even the process?) is unjustified. ] (]) 22:18, 19 October 2024 (UTC) | |||
*:::What would that accomplish? ] (]) 02:55, 21 October 2024 (UTC) | |||
*'''Support''' Let's give such interactions a chance. It's been a year and he seems to have learned his lesson. We can always re-enable the iban. ] (]) 17:12, 21 October 2024 (UTC) | |||
<small>'''Edit:'''</small> Anyone got any thoughts on the concept of having a draft article for a film that doesn't meet ]? | |||
:*I would like to see recent evidence where either of the two users have violated the IBAN, otherwise I '''support''' this request. <span style="font-family:Monospace;color:black">>>> ].]</span> 16:43, 22 October 2024 (UTC) | |||
::*Come on, guys. Heartfox said he would in the future"]] in November 2022 and ended up starting two ANI threads about me after that. They also ] "someone so insecure in real life or online, it is low-key scary. Due to their insecurity they see everything I do as a form of competition against them and go to FAC coordinator and Did You Know talk pages to spew nonsense about how I am trying to 'take them out'", which they were just allowed to get away with even though I had been blocked at the time. After the IBAN had formally been enacted, they ], a mere 15 minutes after I was having a heated argument there and took the opposite side. They have also gone to ] a mere few days after I reviewed it, to "agree" with two of my comments ("I would agree that ''People's Daily'' does not seem to be a high-quality source", "I would agree that claiming "crisper and warmer" to be a paraphrase when it also happens to be verbatim from one of the citations attributed to the consensus is problematic") but making sure to indicate that they did not agree the work had to be done outside the FAC process. Anyways, this is my last comment here. All I am saying is, they have some trouble staying away from me and it is well documented.--'']]'' 18:36, 22 October 2024 (UTC) | |||
*'''Support''' per MaranoFan's diffs. When the person on the other side of the ban opposes it because of violations, and the best evidence is (1) several diffs before the ban was imposed, and (2) one diff afterward, which doesn't show signs of "interaction", then (3) I suspect that there's no violation, or otherwise actual diffs probably would have been found. After a year without violations, ] I suppose; as Buffs says, we can always reimpose it if needed. ] (]) 10:17, 25 October 2024 (UTC) | |||
*'''Support'''. I can understand from where these concerns of MaranoFan are coming from. Unfortunately, MaranoFan has faced a lot of harrassment and it was really difficult for Misplaced Pages community to provide her with a pleasant environment where she could edit productively. However, this appeal is sincere and should be accepted. ] (]) 10:39, 25 October 2024 (UTC) | |||
*'''Support''' accepting appeal request, with the additional statement that it can be reimposed with a quick consensus should issues reoccur. I second Nyttend's comments immediately above me. ] (]) 22:50, 25 October 2024 (UTC) | |||
] (]) 00:39, 29 December 2024 (UTC) | |||
== Murders of Abigail Williams and Liberty German == | |||
:As far as I'm aware, articles on films are allowed so long as principal photography has occurred (principal animation in this case, I guess?). That has clearly happened for this film, even if they are having to scrap and re-write things. And notability is certainly not in question, so having an article is fully within the policy rules. If there are harmful edits happening, then semi-protection seems like a normal response. ]]<sup>]</sup> 00:43, 29 December 2024 (UTC) | |||
::People say that on the draft's talk page every so often and get rebuffed. Maybe you can be more persuasive, but the general argument is the existing animation was created for "Spider-Man: Across The Spider-Verse" before it was split into two films and no "final animation" has begun on this film. ] (]) 01:03, 29 December 2024 (UTC) | |||
:::Are they basing that claim on any reliable source as evidence? Since what exists in that draft currently with reliable sources clearly indicates work has started. ]]<sup>]</sup> 01:11, 29 December 2024 (UTC) | |||
::::Hi. I'm the editor who has requested the protection for this draft. Per ], final animation or voice recording are the requirement to move a film draft to the mainspace. Final animation is different from standard reels being produced, which as sourced, is currently what this film has produced while no voice recording has occurred. It seems to still be very early in development, and much of the earlier work when this was the second part was reportedly scrapped (as sourced in the draft). I do not believe the mainspace viability ought to be discussed here as that is more for the draft. As for the protection request, it appears to be the same person making these disruptive comments which have become unnecessarily excessive and are detracting from the content of the draft itself. I requested protection (initially as ECP though semi works for the talk) because these comments have not benefitted any actual constructive progress and have largely ranged from the IPs attempting to enforce their own opinions about the delays and trying to remove sources they don't like, which has been ongoing since the end of October. As a draft, not many other editors are editing this, so it becomes quite unrelenting and tiresome to deal with these repeated disruptions. Glad to see this has garnered more attention. ] (]) 01:20, 29 December 2024 (UTC) | |||
:::::{{tqq|Per WP:NFF, final animation or voice recording are the requirement to move a film draft to the mainspace}} ...I'm ''pretty sure'' that BtSV meets ] already, regardless of the state of production, and ''that'' should be the main factor. - ] <sub>]</sub> 03:49, 29 December 2024 (UTC) | |||
::::::I have no problem with the draft being moved, this is just not the normal route to do so and typically NFF is followed for film articles, but I digress. I do caution that this article {{em|could}} be susceptible to further unconstructive comments in the mainspace, but that is a price I'm willing to handle. I can make the move as needed, no worries, I am primarily concerned about these type of comments continuing and if any protection is necessary to prevent or temporarily postpone them from continuing. ] (]) 05:18, 29 December 2024 (UTC) | |||
:There doesn't appear to be enough disruption to the draft page to justify protection at this point. Draft talk definitely should get semi-protection. ] (]/]) 00:45, 29 December 2024 (UTC) | |||
::Really? That seems excessive for a few FOURMy IP comments (likely from the same person). If they continue with it, block the IP, maybe. Protecting talk pages should really be a last resort. ] (] | ]) 00:58, 29 December 2024 (UTC) | |||
:Some people overly use NFF to block any film article that has not confirmed start to production, which is really a bad black/white approach. ''Most'' films prior to production are not notable or may not even happen when they are first hinted at, and thus it is absolutely appropriate to use NFF to hold back on a standalone until production starts. But then you have some exceptional cases like this (the 3rd of the animated Spider-Man movies that have earned a massive amount of money and praise, with a lot of attention already given to the film even before production) as well as my own experience with ] which deals with a film that has numerous delays and other incidents that its still nowhere close to production, but its journey that way is readily sourced. NFF should not be used to block creation of articles on films that have this much detail about the work that is otherwise suitable by notability guidelines. For this specific article on the Spider-man film, I see no reason why it could not be in main space at this point as to avoid the whole draft problem.<span id="Masem:1735450356365:WikipediaFTTCLNAdministrators'_noticeboard" class="FTTCmt"> — ] (]) 05:32, 29 December 2024 (UTC)</span> | |||
::Yeah, there is a point to be made that even if this final film somehow never finished production, it would still be notable because of the coverage of its attempted production history. There's several films (and video games, among other cultural apocrypha) that meet that notability requirement, even without ever actually having been completed and released to the public. ]]<sup>]</sup> 05:36, 29 December 2024 (UTC) | |||
:::Indeed, a number of aborted films projects are notable exactly ''because'' they wound up in ]. ] is a film about my personal favorite never-got-made film. ] ] 02:59, 30 December 2024 (UTC) | |||
Noting here that Trailblazer101 moved the article from draft space to main space at 22:44, based on the discussion here and ]. I have not seen any objections to that move since it was done. I have not seen any more speculative or forumy edits recently. There is a good chance they will come back, but if they come back in a serious number the article and/or talk page can be given an appropriate level of protection at that point, or, if the responsible IPs/accounts can be blocked. I think it is probably time to close this discussion. ] (]) 10:56, 30 December 2024 (UTC) | |||
The name of the suspect at ] needs to be suppressed once again. --] (]) 00:21, 19 October 2024 (UTC) | |||
:The IP has made three unconstructive and uncivil comments on the talk today (see , and they show no signs of stopping. ] (]) 18:03, 31 December 2024 (UTC) | |||
:Or maybe a new RfC needs to be held on the issue? Taking a quick look at the article, the trial is now underway, so it's going to be attracting fresh attention from casual editors. The circumstances of a year and a half ago regarding the individual are different (beyond just arrested and charged), so it might be worth revisiting, even if just to reaffirm there is no consensus to include. ] (]) 01:00, 19 October 2024 (UTC) | |||
::I have blocked that IP. I note that it is possible that some of the other IPs could be the same users and so will block other IPs and/or apply semi-protection if this continues (or encourage others to do the same if I am away from my computer). ] (]) 11:51, 1 January 2025 (UTC) | |||
:This is really a disconnect of ] that I haven't known how to even begin addressing until now. For this case, we have the following in the article: {{tq|and on October 31, was charged with two counts of murder.}} - properly sourced to that names the suspect. It is absolutely absurd that we must avoid naming the suspect on Misplaced Pages even when it's named in a source that we link to in the same sentence. BLP is a '''very''' necessary policy. However, it should not prevent naming someone as a suspect when they are named in reliable sources. Currently, BLP states the following: {{tq|editors must seriously consider not including material—in any article—that suggests the person has committed or is accused of having committed a crime, unless a conviction has been secured for that crime.}} This should be changed to "not including material - in any article - that suggests the person ''has committed'' a crime". Reporting on accusations should not be subject to BLP so long as those accusations are sourced. The fact someone was charged with a crime is almost always due, even if they were not convicted of that crime. Being charged with a crime does not imply guilt.{{pb}}In other words, I agree with Grandpallama above - if there is a prior consensus that the name of the suspect is inappropriate... there needs ot be serious reconsideration of that issue and of whether it's a BLP issue to begin with. This is a high profile crime and the suspect's name is linked to from the citation at the end of the sentence. Surpressing it here does fuck all for preventing it when it's literally one link click away (or are we claiming we don't encourage readers to use our citations to verify the information we present?). -bɜ:ʳkənhɪmez | ] | ] 01:09, 19 October 2024 (UTC) | |||
* {{tq|Anyone got any thoughts on the concept of having a draft article for a film that doesn't meet WP:NFF?}} Using draftspace to incubate articles on subjects that are not yet notable but almost certainly will be—unreleased films, upcoming elections, sports events, the next in an "X by year" series, and so on—is a common practice and has been as long as I can remember. As such it's listed at ]. – ] <small>(])</small> 12:04, 1 January 2025 (UTC) | |||
::The rationale behind BLPCRIME is that we shouldn't name ], particularly criminal defendants, who did not choose their status. Reliable sources naming someone is one thing, but I believe that we have an ethical duty to avoid creating a permanent record—one that affects how search engines, AI chatbots, etc. present information—for someone who might be innocent. ] (]/]) 01:22, 19 October 2024 (UTC) | |||
**Thank you. ] (]) 15:01, 1 January 2025 (UTC) | |||
:::That's a perfectly reasonable take, and I don't know that I have a position on inclusion vs. exclusion. But I ''do'' question relying on RfC results for a situation that is different now than it was in April 2023. Separately, I see the RfC resulted in no consensus for inclusion, but I'm not sure how that leapt to "edits must be suppressed". ] (]) 01:28, 19 October 2024 (UTC) | |||
:::See, I'd support that... but the problem is that no other source has this sort of policy. When charges are first announced, sure, they will wait for an actual indictment before they report a name. But I cannot think of a source that has a similar policy.{{pb}}The concern over presenting an indicted/charged person as a criminal is real. That is solved through requiring the prose be accurate. It is not our problem if an AI chat bot uses Misplaced Pages to hallucinate that someone was a criminal. It's not the fault of the news organization for reporting that someone was charged with a crime and that information is misused. -bɜ:ʳkənhɪmez | ] | ] 04:52, 19 October 2024 (UTC) | |||
::::If editors want a wider RfC on BLP policy perhaps at ] there could be merit for that I guess. I don't see what purpose an RfC on naming the suspect will serve at this time. The trial is set to end by November 15th. With an existing RfC even if it was no consensus, and considering the BLP importance it seems to me ending any RfC early with a new consensus is questionable no matter how clear any initial consensus seems to be. Meaning the RfC should run for at least a full 30 days before we can name the suspect. And this is a jury trial meaning that barring very very long jury deliberations we should have a result within 1-2 weeks of the trial ending. So at best starting an RfC now, we might be naming the person 1 week before the situation is likely to change significantly with either an acquittal or conviction. While it's always possible there will be a hung jury or some other kind of mistrial, I think better to just wait those 6 weeks or so and see what the situation is then and then do an RfC. Further if things have significantly changed, there will be much more reason why it might be reasonable to end the RfC early if consensus seems clear. ] (]) 15:38, 19 October 2024 (UTC) | |||
:::::For now, we should suppress the edits, then repost the name only if there is a conviction. --] (]) 19:40, 19 October 2024 (UTC) | |||
:::::I agree that an RfC would be worthless at this point due to the time constraints and with the majority of the points above (aside from the need to supress a name that is covered in the majority of reliable sources and citations in the article. Seems rather drastic to leap to the need to supress when the name is widely published). | |||
:::::And at this point, is the guy even a 'low profile person' anymore, where BLPCRIME is concerned? Looking over the old edits of some of the people who had a hand in actually making that policy, , , and even though he didn't have a hand in making the policy all seemed to think that a high profile crime could make someone a high profile person. | |||
:::::There is also the fact that the subjects attorneys pushed for his name to be released a while back 'in the hopes it would bring tips ' or similar. A followed by a , and later a to get his name out there. | |||
:::::Are we not supposed to take into account what a subject wants in terms of inclusion/exclusion? Jimmy said yes years ago , ARBCOM said to of our edits for BLPs, WMF stated we should be , especially in articles of ephemeral or marginal interest. | |||
:::::I could understand waiting for a resolution to the trial to follow a strict following of the ] of BLPCRIME, but if the subject/his attorneys wanted his name out prior to the trial to help him, it seems like waiting for a conviction before considering what they want goes against the above paragraph. It is essentially saying a policy put in place to protect someones reputation from false accusations holds more power than what the subject wants, which seems wrong on so many levels. | |||
:::::] (]) 17:04, 20 October 2024 (UTC) | |||
::{{outdent|3}} While I agree that there may be cases where defendants who have not been convicted yet may want to publicize their names—such as in cases of civil disobedience, public ransoms, or acts of terror—I do not believe that this is one of those cases. The comments at the pressers were pretty bare bones and the press release expressly states: "We do not want to try this case in the media and we intend to adhere to the Indiana Rules of Professional Conduct that provide guidance on pretrial publicity." The spirit of BLP is that we shouldn't publicize the name of a a person who hasn't inserted themselves into the press, and a limited press conference, press release telling journalists to buzz off, and a fundraiser page do not, in my view, meet that threshold. ] (]/]) 17:17, 20 October 2024 (UTC) | |||
:::The original edit that sparked this discussion I believe was by me; I added the name to the 'trial' infobox parameter and added the name of the trial further down with just the last name of the defendant since I thought MOS/LAW was the guideline to follow when legal things were being discussed. It was pointed out to me later that this is incorrect, and it's only relevant for legal articles. That is what Jax ran across and I believe wants supressed for whatever reason. | |||
:::My intention was to try to update the article a bit and add a subsection later about the Indiana Supreme Court ruling that involved the suspect in this case, which is under a different case name and ended with the Judges issuing a new ruling about when a suspects court appointed counsel can be removed, since it was notable and widely covered at the time (and essentially set a new case law for them, I think ). Are we not allowed to list trial names now because it can be seen as a BLPCRIME violation? | |||
:::] (]) 19:03, 20 October 2024 (UTC) | |||
::::These decisions are very fact-specific. This case is in the States but we write policy for the globe; I don't think we ought to publish the names of the accused in cases that geolocate to Russia or China, for example. I think we have the right rules and wouldn't encourage an attempt to change them. We have a presumption against publishing the names of unconvicted people. Talk page consensus could overrule that presumption in individual cases and I wouldn't object if that happened here. Even though the name is published in reliable sources, this is at heart an ethical judgement we're making, so a reliable source is a minimum threshold to start a discussion, but not a mandate to publish the name.—] <small>]/]</small> 10:31, 24 October 2024 (UTC) | |||
I think it makes sense to archive all threads in ]. They are all either forumy or else asking when the page can be moved to article space, which is no longer relevant since it is in article space. ] (]) 20:06, 3 January 2025 (UTC) | |||
== ] Procedural RfC Closure == | |||
:I've updated the archive bot on that talk age to act on 1 month old threads. Should get rid of half of the ones on there when it runs next and the rest will follow soon enough. I've always thought 6 months was way too long of a default archive policy. ]]<sup>]</sup> 20:11, 3 January 2025 (UTC) | |||
::Yeah, I've always felt 90 days is sufficient for default archival purposes. If no one has contributed to a discussion in three months, it's a dead discussion. — <b>]:<sup>]</sup></b> 18:41, 10 January 2025 (UTC) | |||
== 43.249.196.179 (again) == | |||
The RfC on ] appeared to me to be malformed and unanswerable so I proposed a procedural close. There is no dispute properly demonstrated at the RfC and the editor who began the process has not clarified the situation at all. The RfC asks editors to answer {{tq|Is the lede for this article basically OK (except for maybe some minor tweaks)? or is it Not OK and needs some major changes?}} without making any mention of what the basis for the question is, what the disputed nature of the content is, and seemingly without having actually undertaken any attempt to ] themselves as they haven't edited the article at all except to revert the edit of another editor after they began the RfC {{special:Diff/1251948920}}. The discussions the editor who started the RfC refer editors to read for context in regards to the RfC are long, meandering, and full of sarcasm and mostly seem to center on fixing a DYK Hook that has since passed. Is the lead "OK" or "Not OK" is an overly broad question due to ], and this opinion has been shared by other editors on the RfC itself. The creator of the RfC has insisted twice now that I take my motion for a Procedural Close of the RfC to the Admin Noticeboard {{special:diff/1251937669}}, so, here I am. <b>]</b> 01:40, 19 October 2024 (UTC) | |||
See their previous thread here, ]. Continuing to disrupt and remove categories without explanation, decided to after restoring edits without any talk page discussion, and has now moved onto and by removing categories without said user's permission, calling my reversions 'vindicitive' and now considering me their personal 'nemesis' because they don't understand why they're being reverted. <span style="font-family: Roboto;">''']''' <span style="color:#00008B">•</span> <small>''(])''</small></span> 21:16, 31 December 2024 (UTC) | |||
:Involved, but as far as I know the ship sails for a procedural close once this many people have responded substantively to the RFC question. ''']'''<span style="border:2px solid #073642;background:rgb(255,156,0);background:linear-gradient(90deg, rgba(255,156,0,1) 0%, rgba(147,0,255,1) 45%, rgba(4,123,134,1) 87%);">]</span> 02:05, 19 October 2024 (UTC) | |||
:] is not familiar with some of the WP policies and guidelines especially ] and ]. Also, his obfuscated username is somewhat fustration and is not conducive to efficient editing. ] (]) 21:21, 31 December 2024 (UTC) | |||
:]: Editing user pages has no 'hard policy' prohibition, as this is a wiki. 'End of discussion', seriously? Also see ]. Then, ] is a container category, which clearly says it should only contain subcategories. Even I don't understand why they're being reverted. -- ] <sup>]</sup> 22:08, 31 December 2024 (UTC) | |||
::] seems to be unaware of many of the WP polices and guidelines. ] (]) 08:03, 3 January 2025 (UTC) | |||
:::I've been here nineteen years so obviously I do and I apologize if as mentioned I'm more aggressive about userspace being in control of the user themselves. That said I'm no longer engaging with you or any of your edits as you're now ] and trying to troll some kind of response out of me (and doing the same for Liz, who has the patience of a saint), which you won't get. Understand our guidelines or get blocked. If anyone uninvolved would like to close this, please do so. <span style="font-family: Roboto;">''']''' <span style="color:#00008B">•</span> <small>''(])''</small></span> 17:16, 3 January 2025 (UTC) | |||
::::Length of time on WP is not a measure of how familiar an editor is with policy and guidelines. Your previous comments show that you are unfamiliar with some of them, but to be fair, it is impossible to know all of them. There are a lot of editors that do not know a lot of the policies and guidelines. THere are content disputes and corrections and reverts happening all the time because of inexperienced editors. | |||
::::I am not trolling. I just want WP to be much better than it currently is. ] (]) 19:50, 3 January 2025 (UTC) | |||
::Adressing that final point, I have ] about ] to either remove the ] banner tag or give special sanction to empty user pages from that main category. ] (]) 21:08, 3 January 2025 (UTC) | |||
:::Category:Wikipedians is at a level of the hierarchy that there should be nothing in it, which is why it is a container category. The contents of it have been added by editors who do not understand how WP works and do not realise that it is a container category. You proposal is not needed. ] (]) 22:07, 3 January 2025 (UTC) | |||
:'''Comment''': ] was cited in ] (a sandbox used for drafting a larger edit needing discussion, where categories were copied along with the rest of the article's content). (] is mentioned explicitly in that guideline.) ] (]) 02:49, 1 January 2025 (UTC) | |||
::Whatever the case, user sandbox space is sacred and unless you have permission to edit there, you don't touch them, that's an unwritten rule. Mathglot certainly . That's the main issue here and if I was wrong on the cats so be it, but they should not be playing in sandboxes they shouldn't be in. <span style="font-family: Roboto;">''']''' <span style="color:#00008B">•</span> <small>''(])''</small></span> 02:54, 1 January 2025 (UTC) | |||
::: Just to clarify: I have no qualms about others making improvements to pages in my users space—which belong to the community and are not "mine"—as long as they are improvements. That said, IP's edits in my userspace look like vandalism to me. ] (]) 03:04, 1 January 2025 (UTC) | |||
:::User namespace is not "sacred". And if there is an unwrittten rule then it is not a rule that needed to be adhered to. Also ]. To be a good editor it is important to be familiar with policis and guidelines. ] (]) 08:03, 1 January 2025 (UTC) | |||
:It was not a "gravedance". I was pointing out to you that other editors dont agree with you edits. ] (]) 09:15, 1 January 2025 (UTC) | |||
I only just noticed this AN discussion, after placing ] at User talk:43.249.196.179 about vandalizing a Draft template in my user space. Their edits seem somehow to be related to categories, but near as I can guess from their edit summary ], they also had some inscrutable complaint about me using my userspace as "social media". Maybe interested parties here will understand what they are talking about, because I certainly don't. As of this point, I cannot tell if they are well-meaning, but highly misinformed and uncomprehending, or if they are simply trolling everyone. I suspect the latter, but am willing to be proved wrong, especially if enceforth they stick to ] and ], instead of ignoring advice given previously and ]. ] (]) 03:00, 1 January 2025 (UTC) | |||
:The RfC does not satisfy the requirement of having a clear-cut well-posed question. Since no specific issue is raised in the RfC, nobody knows what things are actually relevant to it and the discussion is wandering all over the place. Basically it says "I don't like the lead, do you agree?" An uninvolved administrator should close this RfC (whether as procedural or "no consensus" doesn't matter), with the understanding that a properly posed replacement can be opened. While I'm at it, someone should examine the behavior of the RfC poser ] who asserts that the editors of the page are . ]<sup><small>]</small></sup> 03:05, 19 October 2024 (UTC) | |||
: Okay, now I am sure: see ] at my Talk page, quickly reverted by {{u|Remsense}} while I was in the process of reverting it. This is clearly intentional, malicious, vandalism, as well as retaliation. Therefore, I propose an '''indefinite block''' on {{user|43.249.196.179}} as it is a vandalism-only account. ] (]) 03:13, 1 January 2025 (UTC) | |||
::I don't find the word antisemites in that diff, did you mean a different one? And as far as the RFC question, "Is the lede for this article basically OK (except for maybe some minor tweaks)? or is it Not OK and needs some major changes?" Seems clear enough to me, it's not specific about article text changes but it appears to be a question to which you can answer one way or another and then as a result, will determine to either change or not, the lead. ''']'''<span style="border:2px solid #073642;background:rgb(255,156,0);background:linear-gradient(90deg, rgba(255,156,0,1) 0%, rgba(147,0,255,1) 45%, rgba(4,123,134,1) 87%);">]</span> 03:09, 19 October 2024 (UTC) | |||
::I haven't looked into this editor's edits but we don't indefinitely block IP editors as the IP account can easily be assigned to a different user. But they can receive longtime blocks on the order of months or years. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 04:33, 1 January 2025 (UTC) | |||
:::The word is not there, but the implication is. {{tq|"Myths like this omit any mention of African-American may demonstrate an African-American resistance to modernization which may have contributed to a culture of backwardness and poverty among African-Americans in the South" and whatnot. Can probably find a historian who said that if we dig enough. Want to go edit that article? Won't get far will you.}} The hypothetical the editor is presenting here implies bigotry in response to the other editor saying {{tq|all the bolded words you mentioned (and all the issues you raise elsewhere) appear basically verbatim in the sources - fully quoted in the citations - in the references section}}. <b>]</b> 03:51, 19 October 2024 (UTC) | |||
::You are looking at two different IP addresses. Getting things right is important. ] (]) 07:53, 1 January 2025 (UTC) | |||
::::Well, but ''that is different thread.'' We are talking about the RfC. Maybe I'm an asshole. Maybe my motives for starting the RfC were bad. I don't think that that matters enough to close down the RfC if it is otherwise OK. ] (]) 04:16, 19 October 2024 (UTC) | |||
:::Honestly, whether that was a Joe Job or not, your behavior is indistinguishable from trolling & deserves a block. — <b>]:<sup>]</sup></b> 18:45, 10 January 2025 (UTC) | |||
== Incivility at ] == | |||
::::Anyway... I didn't insist on anything, but I did say "step up or pipe down". The editor decided to step up, xir perfect right, so here we are. I tend long-winded, so here goes. Skip it if you want. | |||
@] and to a lesser extent @] have been bickering in the talk page for a while now, and the reply chains are so long that they go off my phone's screen. DEB in particular has been noticeably passive aggressive in their comments, such as at me, at AWF, and at ]. Is this actionable? ] (]) 01:57, 2 January 2025 (UTC) | |||
::::So... at least three editors at least asked for a procedural close as malformed -- a nonsensical question, a question from which no actual benefit could come, and so on. That's enough that you have to pay attention, yes. I opened a separate thread to discuss it, at ] and there's more material there. | |||
:This looks to me like it's covered by ]. ] ] 02:18, 2 January 2025 (UTC) | |||
::::I wrote the RfC. It is: | |||
:I have yet to dig through the very length discussions, but on the surface I can say that I'm glad to see it not turning into much of an edit war in the article itself, and remaining mostly on the talk page. Infact the only person who breached 2R's was someone you didn't mention, and interestingly was never warned, but I placed a soft warning on their talk page. As far as the specific diffs provided, I don't see anything in there which is all that problematic, unless you're deeply intrenched in the issue. I would proffer is that if someone says, in it's entirety {{tq|I am stating a fact.}} and you take offence to that, then you might need to back away from the discussion for a few days. ] ] 02:47, 2 January 2025 (UTC) | |||
::::{{talkquote|Is the lede for this article basically '''OK''' (except for maybe some minor tweaks)? or is it '''Not OK''' and needs some major changes?}} | |||
::{{tq|"...then you might need to back away from the discussion for a few days".}} You're probably right about that. ] (]) 02:58, 2 January 2025 (UTC) | |||
::::In all this, I haven't yet seen any suggestions for what should be written there instead. I have asked. | |||
:This seems entirely unnecessary. ] (]) 03:13, 2 January 2025 (UTC) | |||
::Can you elaborate on which aspect of {{tq|this}} you are referring to that you believe is unnecessary? ] ] 03:55, 2 January 2025 (UTC) | |||
:::By this, I mean bringing the issue to ANI. If I owe anyone an apology, I stand ready to give it, but @] hasn't really been involved in the discussion until very recently and has already escalated it here. ] (]) 03:59, 2 January 2025 (UTC) | |||
::::It doesn't matter how much someone has been involved in a discussion. If there's misconduct that's not clearly going to get resolved on its own (which I'm not confident saying either way here), then it's a public service, even a responsibility, for an editor to report it. ] (]) 05:58, 2 January 2025 (UTC) | |||
::::@] you can see my initial assessment of the situation above. However, I will say uninvolved editors are welcome to bring valid concerns to ANI. It is often far more helpful when someone outside of the situation brings it up here as it ends up being far more neutral. I also would suggest that you might also be too involved right now and need to back away for a few days. The biggest reason is that I believe you read right past Animal lover's and my response which ''basically didn't find you doing anything wrong''. I suggest that a cooling off period might be good for you as well. Not because you're currently doing anything wrong (because that conversation would look quite different), but rather that you're likely too invested in this topic right now to see rationally and objectively. ] ] 06:18, 2 January 2025 (UTC) | |||
:::::It was not my intent to ignore those assessments, and I understand what you've said as far as uninvolved editors raising such issues (real or perceived). ] (]) 19:26, 2 January 2025 (UTC) | |||
::::Also, as a note, this isn't ANI... - ] <sub>]</sub> 07:09, 2 January 2025 (UTC) | |||
:Infact I don't know why such a simple infobox change discussion will resulted in endless arguments. And it happened in mutiple pages, like this ], this ], and now this Azerbaijan Airlines crash case there. And I'm afraid there would be other arguements in previous pages. | |||
:But to be honest, I think I also have some responsibilities on this endless situation: I have known what to do to deal with such major changes, but I didn't really take any action. ] (]) 07:14, 2 January 2025 (UTC) | |||
::The whole "Accident vs Crash" thing has been going on for a while now. It pretty much goes nowhere every time. DEB gives a whole bunch of reasons why "accident" should be avoided, AWF gives a whole bunch of reasons why "accident" is perfectly fine, and it all repeats with every new ] article. I just recommended on DEB's talk page that they try to seek a wider consensus to break this endless cycle, because I for one am tired of seeing the same arguments over and over again with no progress. - ] <sub>]</sub><span style="color:#6B8E23">\</span><sup>]</sup> 08:02, 2 January 2025 (UTC) | |||
:::Infact you can check the talkpage I provided, you will find such arguments have happened on mutiple pages. ] (]) 08:09, 2 January 2025 (UTC) | |||
::::Since the regular editors in this topic area have proven that they are unable to resolve this utterly trivial terminology dispute among themselves, perhaps the best solution might be to topic ban every consistent advocate of "accident" and to topic ban every consistent advocate of "crash" from all articles about airplane mishaps, and let entirely uninvolved editors make a reasonable decision. Because endless bickering among entrenched advocates is disruptive. Topic bans could then be lifted on editors who explicitly agree to ] and drop the terminology issue forever. ] (]) 08:25, 2 January 2025 (UTC) | |||
:::::It's less "unable to resolve" and more "Dreameditsbrooklyn argues that using 'accident' is original research because the sources use 'crash'" and I wish I was joking. Your modest proposal probably ''would'' get some kind of result though! - ] <sub>]</sub> 08:27, 2 January 2025 (UTC) | |||
:::::Infact I have already suggested to delete this controversial value ], since it have not much actural use to show, and mostly have the same contents with the "Summary" value. And ironically, it has showed the available value on the doc page, but the example they showed on simply violate it! But since then nobody really talk about it yet. ] (]) 08:34, 2 January 2025 (UTC) | |||
:::::As someone who has consistently been on the side "accident is fine" of this argument (there really isn't an "accident/crash" binary here, just whether "accident" is original research), I think that's a bit extreme. I laid out a ] on DEB's talk page, which should hopefully help resolve the issue once and for all without the need for more drastic measures. - ] <sub>]</sub><span style="color:#6B8E23">\</span><sup>]</sup> 09:20, 2 January 2025 (UTC) | |||
:::::Respectfully, the descriptions aren't trivial. A "crash" describes what happened. An "accident" implies someone made a mistake with no real culpability. An "incident" implies some sort of interaction or series of events. I have no specific dog in this fight and I don't believe I've voiced any significant opinion on the matter here or elsewhere, but such a description is not trivial when we are trying to be ] in our descriptions. In this particular case, it very much appears that the act was deliberate and the airliner was acceptable collateral damage (in their opinion). At a minimum, it's disputed. As such, "accident" isn't appropriate as it is at least alleged to be a deliberate act or negligence. "Incident" or "crash" would be more neutral. If we say "accident" it implies no one should be blamed and fails ]. ] (]) 22:22, 2 January 2025 (UTC) | |||
::::::] (the context of aviation has been from at least one discussion on the matter). We could go over whether "accident" actually implies no culpability in the context of aviation all day, but this is not the place to do it. As I stated numerous times, we need to formally establish a project-wide consensus about this, and ] is a good place to start. As for this discussion, I think it can be closed as the issue in question is very minor. - ] <sub>]</sub><span style="color:#6B8E23">\</span><sup>]</sup> 22:42, 2 January 2025 (UTC) | |||
:::::::WP:MOS says: {{tq|If any contradiction arises, this page has precedence.}} | |||
:::::::WP:AT, which follows MOS says: {{tq|Generally, article titles are based on what the subject is called in reliable sources.}} | |||
:::::::The very broad majority of RS call this a crash. Why, in this case, doesn't this apply? Because some editors disagree? I am honestly asking. I don't see a policy which overrules MOS here. Also, I'll hold off on any new discussions on this until things have concluded here and at the article talk page, where the same editor who started this discussion opened an RfC on the topic. ] (]) 22:58, 2 January 2025 (UTC) | |||
::::::::I will not continue this off-topic discussion here. If the same perceived problem is happening across multiple ] articles, then the discussion needs to be moved there to finally end the cycle and come to a consensus. - ] <sub>]</sub><span style="color:#6B8E23">\</span><sup>]</sup> 23:06, 2 January 2025 (UTC) | |||
:::::::::I'm not sure WP:AATF is the correct venue to continue the discussion for a number of reasons, which I will spare going into here. ] (]) 23:14, 2 January 2025 (UTC) | |||
::::::::::{{tqq|The very broad majority of RS call this a crash. Why, in this case, doesn't this apply?}} Because ] don't need to "follow the sources", and insisting that they do is ]. - ] <sub>]</sub> 01:38, 4 January 2025 (UTC) | |||
:::::::::::Others have rejected this as the venue to hold this debate, and I will too. I suggest you follow your own advice and drop the stick, at least for now. ] (]) 02:06, 4 January 2025 (UTC) | |||
::::::{{tqq|An "accident" implies someone made a mistake with no real culpability}} No, it does not. The International Civil Aviation Organization, which is somewhat of an authority on the matter, defines an 'aircraft accident' as {{tqq|Accident. An occurrence associated with the operation of an aircraft ..., in which: a) a person is fatally or seriously injured b) the aircraft sustains damage or structural failure c) the aircraft is missing or is completely inaccessible}}. Notice what isn't there - anything about mistakes or culapbility. {{ping|Buffs}} "Accident" is the official internationally recognized term for this sort of occurance, and is entirely neutral in use. Note that "incident" has a very specific term in aviation which is "an occurrence, other than an accident, associated with the operation of an aircraft that affects or could affect the safety of operation." {{ping|Dreameditsbrooklyn}} I'd suggest you ] and stop pushing this ] ]. - ] <sub>]</sub> 23:51, 2 January 2025 (UTC) | |||
:::::::Why do you think this jargon use should take precedence over the common meaning of the word? The word "accident" can be used in (at least) two senses, one of which involves a lack of intention -- the fact that the ICAO (who?) says that they use the word "accident" in only one of these senses isn't somehow magically binding on everyone else who uses the word in the context of aviation. Given the choice between a word with two ambiguous senses, one of which inappropriate, and a word that has only one relevant sense, it's obvious that the latter word will be clearer, isn't it? ] (]) 04:12, 3 January 2025 (UTC) | |||
::::::::]. The people whose job it is to establish these things for aviation. It's not the use of one word for the other that I have a problem with. It's the argument that, somehow, using "accident" constitutes original research ''when in fact it is the correct terminology'' - and in fact some of the suggested alternatives are explicitly ''incorrect'' terminology - is the problem. And no, its not "magically binding", but ] in the context of aviation is to refer to ''any'' crash as an "aviation accident", just like how if somebody deliberately rear-ends you in road rage it's still a "car accident" - it isn't ]. - ] <sub>]</sub> 09:25, 3 January 2025 (UTC) | |||
:::::::::Do you think there was a car accident in New Orleans a few days ago? When you appeal to an organization like ICAO for what the meaning of a common word is, you are by definition using jargon. ] (]) 17:58, 3 January 2025 (UTC) | |||
::::::::::When you appeal to an expert for the meaning of a word in the context of what it's being used in, that's common sense. - ] <sub>]</sub> 21:59, 3 January 2025 (UTC) | |||
:::::::::::It’s the very definition of the word jargon! No wonder people are finding you impossible to deal with. ] (]) 18:57, 4 January 2025 (UTC) | |||
::::::::::::]. — <b>]:<sup>]</sup></b> 18:50, 10 January 2025 (UTC) | |||
:::::::::What is "an occurrence, other than an accident..." if "accident" includes "incidents"? Definition you're claiming here doesn't make a lot of sense. ] (]) 19:03, 3 January 2025 (UTC) | |||
::::::::::Accident =/= incident, which I believed was clear. - ] <sub>]</sub> 21:59, 3 January 2025 (UTC) | |||
:::::::::::Incident includes accidents AND intentional acts. ] (]) 18:34, 4 January 2025 (UTC) | |||
::::::::::::Not , but this probably ''is'' something best not continued here I reckon. - ] <sub>]</sub> 18:40, 4 January 2025 (UTC) | |||
::::::I did not bring this up to ] to litigate whether to use "crash" or "accident". If you would like to litigate that, I have started a RfC on the Talk page. I brought this here to ask the admins to discuss whether <u>DEB's and AWF's behavior</u> is worth pursuing administrator action. ] (]) 01:09, 3 January 2025 (UTC) | |||
:::::Since you think this is an "utterly trivial terminology dispute" should I tag you in the RFC at WP:RS when I make it, or not? I don't wish to bother you if it's not important to you. ] (]) 22:31, 3 January 2025 (UTC) | |||
:I know this discussion is about conduct, not about the disagreement which prompted it, but I'll note that the other user named here and who has not responded has since changed instances of the word 'crash' to accident on other entries and has also since been of violating 3RR on the very entry which prompted this discussion. I've agreed to confine any further conversations to the talk page until a consensus is reached, wherever that may be. ] (]) 02:46, 3 January 2025 (UTC) | |||
::On the very entry for a completely different reason regarding the use of the Aviation Safety Network but I concede that whilst I was within the limits of 3RR, it probably shouldn't have gotten to that point in the first place. {{Tq|... since changed several instances of the word 'crash' to accident on other entries}} – The only changes made were either related to a change within the infobox to stay consistent with ] as the occurrence type on the aforementioned article stated {{Tq|Airliner crash}}, or related to changes regarding short descriptions since they were changed to be phrased in a way that is not usually done. It's not like I removed every single mention of the word ''crash'' and replaced it with ''accident''. But back to the main topic, I'm willing to drop the issue as long as it's not an problem to use ''accident'' in articles relating to aviation. ] (]) 03:40, 3 January 2025 (UTC) | |||
Can we close this? The current discussion has next to nothing to do with the original issue and is best continued somewhere else. - ] <sub>]</sub><span style="color:#6B8E23">\</span><sup>]</sup> 19:03, 4 January 2025 (UTC) | |||
::::My reasoning for starting the RfC was this: | |||
::::*The article lede is very poor -- POV, and way overly negative in my opinion. I can back that up with good evidence (doesn't prove I'm right, granted). Ofc that is the personal opinion of one person, yes. | |||
::::*The matter involves Israel, and the Jewish people generally. People are having really really really strong feelings these days about Israel and Palestine, both ways. Let's not pretend this isn't so. It's a data point. | |||
::::*In the local discussion, there were some editors -- two or three -- who were defending this (bad IMO) lede super strongly. I wasn't going to get anywhere (I believe that, on grounds of being required to assume good faith and to be civil, I'm not allowed to say if I think that this was because of emotional and political factors rather than ice-cold NPOV scholarship, . | |||
::::*Yup, I did get sarcastic in an earlier thread. Within bounds I think, but definitely not my best moment. (I have strong feelings too! But mainly that this is the sort of thing that is going to lose us Michigan). But anyway ''that's a different thread''. In the RfC itself I haven't been too involved and have not yet "voted". | |||
::::*So the reason I started the RfC was to get more eyes on the matter. Eyes backing me up? Hope so -- I'm human. But whatever happens, it is what it is. IMO the RfC itself is neutral and I did not canvass. | |||
::::*I offered a general big-picture RfC because it's a very fraught, emotional question, we want to go step by step. If the consensus is "OK", we're done. If it is "Not OK", we can move on to another discussion on how to fix it. I did not want to start off with "Should we have the current, or this version I have provided?" cos I thought that would bog down into "Neither. say such-and-so" "No, say so-and-such" etc. If I'm wrong, may I please have some suggestions of what the RfC should say, instead and we can start a new one I guess. | |||
:Agreed. An admin got involved and simply continued off-topic discussion. ] (]) 21:33, 4 January 2025 (UTC) | |||
::::I think that some these requests for procedural close are political. That is my personal opinion. You decide. In fairness, the first person to request a procedural close was summoned by bot, and thought the RfC was terrible and was mad about it. So there is that. | |||
*'''Warn both to drop the stick''', otherwise, no action at this point. ] (]) 15:57, 8 January 2025 (UTC) | |||
*:'''''Hands ] two ]''''' You want to hand them out, or me? ] (]) 16:32, 9 January 2025 (UTC) | |||
== Topic ban appeal == | |||
::::But still... a number of editors are engaged in the RfC discussion to possible useful effect, so I think a shutdown is too late and would be not excellent. ] (]) 04:25, 19 October 2024 (UTC) | |||
{{atop | |||
:::::{{tq|I didn't insist on anything}} | |||
| result = There is consensus against lifting the topic ban at this time. DesertInfo is advised to find areas where they are willing to edit to show a better history prior to revisiting the topic ban in the future. ] ] 15:07, 12 January 2025 (UTC) | |||
}} | |||
::::::You are not my puppet, colleague. I mean I offered the option to pipe down (I did not say shut up). and of course you always have the option to roll your eyes and mutter "what a jerk" or whatever and move on. God knows I do that often enough. ] (]) 07:10, 19 October 2024 (UTC) | |||
Hello, I have a topic ban that is approaching one year old on "undiscussed moves, move discussions, deletion discussions, and racial issues broadly construed (including topics associated with the Confederate States of America)". I would like an opportunity to contribute to these topics again. I have been fairly inactive since then but I have edited a few articles without issue. Thank you. ] (]) 04:36, 3 January 2025 (UTC) | |||
Two editors seem to have missed it so I'll quote from the Herostratus' diff to show that the accusation of antisemitism is there explicitly.<br/>{{tq|"The editors we are dealing with here are clever. They are not going to use material that is not well sourced. That would be stupid. So they are clever, so what? Have you not heard of cherry picking. Have you not heard of spin, of propaganda. The Devil can quote scripture.}} {{tq|So, the material is not anti-''Israeli'', itn is anti-''Semetic''."}} So, once the subject has been established as the editors of the article, and they are described as engaging in spin and propaganda, it is said that the material they wrote is antisemitic. In my opinion, a charge of antisemitism against other editors (except on a behavioral noticeboard with strong supporting evidence) should merit an immediate indef. ]<sup><small>]</small></sup> 04:30, 19 October 2024 (UTC) | |||
:I'll kick off by asking the standard two questions: (1) please explain in your own words why you were topic banned; (2) do you have anything to say to convince everyone those same issues won't occur again? ]] 14:01, 3 January 2025 (UTC) | |||
:An accusation of antisemitism combined with comparing editors to {{tq|The Devil}}? Yeah, a pretty clear case of ]. ] (] | ] | ]) 05:13, 19 October 2024 (UTC) | |||
::I was topic banned for not assuming good faith and making an allegation that someone was using a sockpuppet when I was unable to provide substantial evidence. The topic ban was appealable after 3 months but I stepped away for almost a year. I am ready to discuss these topics respectfully and understand the importance of patience and communication. ANI should be a last resort. ] (]) 18:29, 3 January 2025 (UTC) | |||
::] opened an RfC while showing with long and tortuous personal harangues that they have not troubled themselves with reading the sources. It was also clear that the quip about editors being 'clever' was a disingenuous shot at the putative ulterior motives driving those who actually have read the sources and aided in the composition of the article, a point unambiguously underlined later by the crack:' the material is not anti-Israeli, it is anti-Semetic.' That misspelling always puts me on my guard, since it crops up frequently as, for me, an index of quarrelsomeness uninformed by any serious reading. No fuss was made, but I will note that when , - precisely because of my own sensitivities about generalizing about Jews (a premise of antisemitism that all Jews are involved whenever one or another does this or that) - Herostratus , after waiting 5 days, just as this report opened. That is deeply ironical. In context, Herostratus is insinuating those who support the article are motivated by antisemitic feelings, and, with his restoring the usage 'by Jews' I considered potentially coloured by the kind of imprecision that plays to antisemitic feelings, telling me he thinks editors like me are perhaps both anti-'''semetic''' and 'philosemitic'. This is on a par with the vexatious incoherence of most of the things written on that talk page.] (]) 06:50, 19 October 2024 (UTC) | |||
:::Can you provide a link to the discussion where this topic ban was imposed? Thank you. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 04:05, 4 January 2025 (UTC) | |||
:::None. Of. This. Has. Anything. To. Do. With. The. Question. At. Hand. Which quashing the RfC or not. If you want to want to have a conversation at ] on grounds that I have made false accusations of anti-semitism, OK, do that. That's a different conversation.. ] (]) 07:16, 19 October 2024 (UTC) | |||
::::Found it. ]. ] <sup>(]) (])</sup> 04:35, 4 January 2025 (UTC) | |||
<- So much inane timewasting trolling. The malformed RfC should be shut down regardless of how many patient people participated. The editor should be made to go away. It would be an act of kindness. ] ] (]) 08:08, 19 October 2024 (UTC) | |||
:::::Thank you. That is helpful to have. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 07:19, 4 January 2025 (UTC) | |||
:* I '''support lifting the ban.''' DI's talk page makes for interesting reading, it shows quite a remarkable change in attitude over a period of a few years, and I believe that's genuine. ]] 08:58, 6 January 2025 (UTC) | |||
* '''Oppose lifting the topic ban''' I think being warned for making edits that violating a topic ban, then being almost completely inactive for six months, and then coming back and asking for it to be lifted and that passing sets a horrible example. ] ] 06:31, 7 January 2025 (UTC) | |||
*:It seemed like a good idea to step away from the site for a time. I was receptive to the warning, even though it was not from an admin, and stopped editing in that area entirely. These are the edits in question: I just forgot that I had to appeal the topic ban here first and haven't gotten around to it until now. It should be noted that the first edit merely restored a previous RFC that had been ignored and the last two were minor changes to articles that have since been restored. | |||
*:I have never made a different account or tried to dishonestly avoid the topic ban and I never will. All I ask is that you ] and give me a chance to show that I can contribute collaboratively and have matured. ] (]) 21:51, 7 January 2025 (UTC) | |||
* Only 106 edits since unblocking (including the unblocking), of which includes apparently no edits to article talkpages, which is where a lot of the issues emerged. There's not much to really evaluate change. ] (]) 07:24, 7 January 2025 (UTC) | |||
*:I have largely avoided getting involved in article talk pages in order to avoid violating the topic ban. If I were to get involved in these topics to demonstrate change, it would be in violation of the topic ban. Seems like a catch-22. ] (]) 20:51, 7 January 2025 (UTC) | |||
*::There are literally millions of articles and talk pages not covered by your topic ban. You are expected to demonstrate change there. Why on earth do you think this makes it a catch-22 situation?!? --] (]) 22:06, 7 January 2025 (UTC) | |||
*:::I have made plenty of edits to articles like ], ], ], and ] in the meantime without issue, there was no need to discuss it on the talk page. I have tried to make clear edit summaries and contribute to the encyclopedia. ] (]) 22:45, 7 January 2025 (UTC) | |||
* '''Oppose lifting the topic ban'''. As per Chipmunkdavis, there have been very few edits since the unblock in February 2024. Although DesertInfo says "I have made plenty of edits", I just don't see enough here to justify lifting the topic ban. I'll also note that at least some of these edits came close to violating the topic ban (see ] for example). --] (]) 23:02, 7 January 2025 (UTC) | |||
* '''Oppose at this time''' I appreciate that you walked away rather than risk violating the ban. that shows some recognition of the issue and willingness to try and do something about it. However, what we would want to see would be a decent track record of editing over a sustained period without any hint of violating the ban, and you are just not there yet. ] ] 23:15, 7 January 2025 (UTC) | |||
*:I have edited multiple articles without issue. I don't understand why I would edit articles I'm not interested in/knowledgeable about. I don't want to add useless info or talk page comments for the sake of adding it. I have tried to contribute to articles I know something about. The topic ban is very broad and could reasonably be argued to cover most history/politics subjects. | |||
*:I made a genuine mistake half a year ago that was not egregious and did not violate the topic ban, only coming close. When reminded of the topic ban, I stopped immediately. The topic ban was appealable after 3 months. I was told to step away from editing entirely for a long period of time and I did: | |||
*:This ban has been in place been in place since 2022, over 3 years. A lot has changed and I have matured greatly. ] (]) 23:36, 7 January 2025 (UTC) | |||
*::The topic ban is not so broad as to cut off most of en.wiki. Aside from the move and deletion restrictions, which are technical and do not restrict editing from any particular page, the topic ban is just "racial issues broadly construed". Do you really feel that this covers every article you are either interested in or knowledgeable about? Do you really feel you can't participate in talkpages without infringing on this? ] (]) 01:50, 8 January 2025 (UTC) | |||
*:::I would like to participate in move and deletion discussions. I contributed a lot to ] and I would like to update some place names through move requests. I haven't had issues in that area since 2022. ] (]) 05:24, 12 January 2025 (UTC) | |||
*'''Comment''' - I'd say {{tq|"racial issues broadly construed"}} is actually pretty broad given how much of history/geography is touched by it. I'd also say they do appear to have made an effort to improve, though I'd still like to see more. ] (]) 16:03, 8 January 2025 (UTC) | |||
*'''Oppose''' I want to see some real world effort working collaboratively somewhere else on wp, not just a six month gap waiting it, off wikipedia. There is no evidence here that there has been a change. '''<span style="text-shadow:7px 7px 8px black; font-family:Papyrus">]<sup>]</sup></span>''' 08:26, 11 January 2025 (UTC) | |||
{{abot}} | |||
== Andra Febrian report == | |||
Procedurally closed or not, this RFC is going absolutely nowhere, an unfocused mess.] (]) 08:21, 19 October 2024 (UTC) | |||
{{atop | |||
| result = HiLux duck has been blocked, and no further action is needed here. ] ] 15:10, 12 January 2025 (UTC) | |||
}} | |||
"Andra Febrian" is disrupting many edits, I have seen many deleted edits by this user, and I would like to report the user for causing many ]s. The edits unreasonably reverted by this user is very disruptive to me, as I only intend for useful contributions. The user has: | |||
- caused many edit wars <br/> | |||
- deleted citations along with deleting correct claims <br/> | |||
- not been cooperative (wikipedia's ]) on many pages that good-] edits have occurred on <br/> | |||
- not explained deletions of citations in a way that other users have been made upset. <br/> | |||
I request that the user is warned. | |||
] <!--Template:Undated--><small class="autosigned">— Preceding ] comment added 22:13, 3 January 2025 (UTC)</small> | |||
:First: the notice at the top of the page clearly says to place new sections at the bottom of the page, which I have now done for you. Second: you need to provide ] for the edits you are complaining about. Third, you were supposed to notify Andra Febrian per the instructions at the top of the page. Another user has done so for you. - ] 00:06, 4 January 2025 (UTC) | |||
:@]: please sign your comments using <nowiki>~~~~</nowiki>, which will add a timestamp. Additionally, I reverted your edits to ] and to ] because you are changing information in articles without citing ]. You must cite sources when you add or change information in articles. ] (]/]) 00:20, 4 January 2025 (UTC) | |||
::] just filed a new complaint at ANEW and made the exact same mistakes as they did here. I advised them to stop posting complaints on noticeboards until they can follow the instructions. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 07:18, 4 January 2025 (UTC) | |||
:::FWIW, I have a feeling that HiLux Duck is a sockpuppet of ], but I am holding back until they give themselves enough rope to hang. Same obsession with defining overall lengths for various car classifications and edit warring at length over them. <span style="background:#ff0000;font-family:Times New Roman;">]]</span> 00:55, 6 January 2025 (UTC) | |||
::::I'm always impressed when editors can recall editing habits of editors that were blocked years ago. I guess I lack the longterm memory to keep track of sockpuppet habits. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 04:14, 6 January 2025 (UTC) | |||
:::::{{ping|Liz}} MrDavr actually got under my skin at one point; otherwise I probably wouldn't have noticed. Thanks, <span style="background:#ff0000;font-family:Times New Roman;">]]</span> 02:04, 7 January 2025 (UTC) | |||
:::::Looking into this {{duck}} (a HiLux ]?) because yeah, this is ''exactly'' the same editing pattern. Same username pattern as a number of MrDavr socks too (car names/variations thereof - ]). - ] <sub>]</sub> 09:49, 6 January 2025 (UTC) | |||
::::::@] - ] (]) 15:23, 6 January 2025 (UTC) | |||
::::Most likely yes, I knew that the his editing patterns matched an old blocked user but didn't remember the name. ] (]) 16:14, 6 January 2025 (UTC) | |||
::::::::It's also interesting to note that HiLux duck's user page claims they've been on Misplaced Pages since 2019, and having compared edits more extensively I've seen enough and gone ahead and blocked per ]. - ] <sub>]</sub> 20:20, 6 January 2025 (UTC) | |||
=== Mr.Choppers warning request === | |||
In case anyone is as confused as I was: the African-American bit is comparing this article to ]. Nobody's suggesting that African Americans need to be mentioned in ]. ] (]) 21:42, 21 October 2024 (UTC) | |||
:: <small> This was (again) posted at the top instead of the bottom; it seems like it is not really a separate issue. ] (]) 01:54, 7 January 2025 (UTC)</small> | |||
User:Mr.Choppers has not followed the ] rules because: <br/> | |||
'''-''' calling me a "nuisance" because of own ] supporting others in ] that have nothing to do with the user. ] ] <br/> | |||
'''-''' responded fairly aggressively to another user (me) without me being aggressive back or starting this edit war <br/> | |||
'''-''' note that he also called me a "sockpuppet of a banned user" without reliable clarification, also biased on that <br/> | |||
'''-''' also note the user had not informed me and used aggression to support own claims. <br/> | |||
<br/> | |||
I would like to inform that this user has unnecessarily used aggression and claimed things not there. Kind regards, ] (]) 2:29, 6 January 2025 (GMT+12) | |||
:Missed this because it was at the top. Very unlikely to have merit and is moot now, given the block. - ] <sub>]</sub> 02:24, 7 January 2025 (UTC) | |||
{{abot}} | |||
== user:Uwappa: refusal to engage with WP:BRD process, unfounded allegation of ] violation, unfounded vandalism allegation == | |||
===Honestly just shoot me, maybe=== | |||
{{archive top|result=I have indefinitely blocked Uwappa per ]. Whilst the legal threat pointed out by multiple editors may be very vague, it certainly is designed to have a chilling effect, and Uwappa has confirmed this with addition to the section. Quite apart from that, we have persistent edit-warring, meritless claims of vandalism against others, and there is a limit to which an editor who thinks all of this is a big joke can be allowed to waste everybody else's time. They can explain themselves in an unblock request if they so desire. ] 22:57, 6 January 2025 (UTC)}} | |||
It's too late to procedurally close the RfC now. It'll age out on soon enough. Yeah it was badly written, but too many people have engaged anyway. | |||
repost from archive: | |||
The content disagreement behind this report is trivial in the overall scope of Misplaced Pages (although the articles affected are subject to ]), but the editor behaviour is not. My reason to bring this case to ANI is that ] rejects some basic principles of the project: ] means that a bold edit may be reverted to the '']'' and goes on to say {{tq|don't restore your bold edit, don't ] to this part of the page, don't engage in ], and don't start any of the larger ] processes. Talk to that one person until the two of you have reached an agreement.}} Despite having been reminded about BRD after their first immediate counter-revert, they responded to the reversion to the ''sqa'' with another counter-revert and, after another editor reinstated the ''sqa'', counter-reverted again. At no stage did they attempt to engage in BRD discussion. Both I and the other editor attempted to engage with them at their talk page: Uwappa characterises my explanation as a personal attack. On another page, Uwappa reverted an edit where I suppressed the questioned <s>material</s> template, declaring it "vandalism" in the edit summary. I recognise the rubric at BRD that says {{tq|BRD is optional, but complying with ''']''' and ''']''' is mandatory}} but Uwappa has done neither. | |||
BUT | |||
I consider my escalating this to ANI to be a failure of negotiating skill on my part but, while Uwappa refuses to engage, I am left with no choice. Allowing a few days for logic to intervene has not been fruitful. With great reluctance, because Uwappa has made valuable contributions, I have to ask that they be blocked until they acknowledge and commit to respect the principles that underlie BRD, ] and ]. | |||
I don't know if topic bans are imposed her as they are are ], but really there is maybe some editor behavior to consider, I don't know, just raising the question. Maybe just my behavior, fine, I hereby turn myself in. | |||
'''Diffs:''' ''(all timestamps UTC. NB that I am in England => UTC+00:00, Uwappa is in Australia => UTC+10:00 ) '' | |||
If I should be topic banned, fine, if that's the decision (I never engage in this subject anyway, I don't care much about it per se, it's stressful and people feel really strongly about it and its hard work, I just came to that article because of a hook, and honestly if you want to put me out of my misery it'd be a kindness). If other editors should be topic banned, I don't know, that'd be up to you. I am not suggesting it as that is not my remit. Maybe nobody here should be topic banned, or maybe everybody here and their dog should be topic banned on the principle of "you made me get up and come down there". | |||
* : Uwappa replaces {{tl|Body roundness index}} with a substantially changed new version | |||
* : JMF (me) reverts to the previous version, with edit summary "sorry but this version is not ready for release. I will explain at talk page." | |||
* : JMF opens ] at template talk page (and leaves notifications at the talk pages of the articles that invoke the template). | |||
* : Uwappa responds minimally at template talk page. {{midsize|] ]}} | |||
* : Uwappa counter-reverts to their new version of the template, no edit summary. | |||
* JMF reverts the counter reversion with edit summary "see WP:BRD: when BRD is invoked, the status quo ante must persist until consensus is reached" | |||
* : Uwappa counter-reverts the template again, no edit summary. | |||
* : at ], JMF advises Uwappa of the BRD convention. | |||
* : {{u|Zefr}} contributes to BRD debate. | |||
* : At Uwappa's talk page, JMF notifies Uwappa of edit-warring using {{tl|uw-editwar}} with edit summary "I advise strongly that you self-revert immediately, otherwise I shall have no choice but to escalate." | |||
* At ], JMF comments out invocation of the template, with edit summary "use of template suspended pending dispute resolution . See talk page." | |||
** (a series of reverts and counter reverts follow, in which Uwappa alleges vandalism by JMF. Neither party breaks 3RR.) | |||
* At their talk page, Uwappa rejects the request to self-revert and invites escalation. Edit summary: "go for it". | |||
* ] reverts the counter-reversion of the template to re-establish ''sqa'' | |||
So IMO what happened is this: | |||
* Uwappa reinstates their counter-reversion of the template. | |||
A lot of these editors are really really mad at me because of my behavior in the immediately ''preceding threads'', ] and ]. Then I made an RfC. Yeah the RfC was poor, but still, asking for a procedural close ''so'' vociferously was just a proxy for being mad at me generally. That is my personal view of what is going on here. | |||
* Uwappa contributes to the BRD discussion only to say "See also ] for escalation in progress.". | |||
* JMF reverts to ''sqa'' again, with edit summary " rv to consensus version, pending BRD discussion. That is now also a WP:3RR violation." {{midsize|My 3RR challenge was not valid as reversion was outside the 24-hour window.}} | |||
* At Uwappa's talk page, JMF advises Uwappa to take a break from editing. | |||
* At their talk page, Uwappa alleges ] violation. I will leave it to others to decide whether the allegation has merit. | |||
--- | |||
Hey, people get emotional, its a emotional subject, it's understandable. And I was not at my best in those threads. No wonder they're mad at me! And it is entirely in the purview of the admin corps to consider larger factors like this, up to an including behavior going back to the Eisenhower Administration, and fine. | |||
* At Uwappa's talk page, JMF suggests that we let the status quo stand and we all walk away without escalating to ANI. | |||
* Uwappa replies to refuse de-escalation. | |||
As of 11:48 (UTC) on 30/12, the live version of the template is the one that has consensus support. --] (]) 11:59, 30 December 2024 (UTC) | |||
My defense -- we are talking about ] and ] now -- is basically | |||
#Yup I lost my head and was sarcastic and didactic and maybe prolix and (if you say) disruptive in places, my bad. | |||
#I pride myself on at least ''trying'' to be an ice-cold NPOV editor. I make a point of occasionally looking at articles of people I despise and who are not generally popular here (] etc.) and trying to make them more fair if they're not. I do feel kind of strongly ''any'' POV. But I keep my head. | |||
#But not here. I think that the POV I saw here was just really red flag egregious and . I'm not sure if any people agree all that strongly. But believe I am right anyway. I formed my own opinion about various other things, which I will now keep to myself. So yeh I lost my head a bit. | |||
#Some of the statements and implications I made I can demonstrate to some level of satisfaction, some relate to other editors' internal feelings and motives etc. and can't be proven. Doesn't mean I don't regret making some of them. I do. Doesn't mean some of them weren't prolix, inflammatory and counterproductive. They were. Doesn't mean some of them were unkind. They were. As to whether or not I thought they were nevertheless correct or still do... I'd best keep that to myself I guess. I'm not going to lie to you.] (]) 00:56, 24 October 2024 (UTC) | |||
:Well, Uwappa hasn't edited on the project in 12 hours so it's pretty sage to assume they haven't seen this complaint yet. I'd like to hear their response and whether or not they are willing to collaborate before passing any judgment. Very through presentation of the dispute, easy to follow, so thank you for that. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 20:04, 30 December 2024 (UTC) | |||
== Fake news websites == | |||
::Yes, that is why I felt it important to make clear that our time zones are very widely spaced, which makes collaboration difficult in the best of circumstances. When they do see it, I would expect they will take some time offline to polish their response before posting it{{snd}} and consequently it is likely to be as long again before I respond. ] (]) 20:35, 30 December 2024 (UTC) | |||
Reposted above from archive, see ] | |||
*{{LinkSummary|zaobaodaily.com}} | |||
*{{LinkSummary|singaporeinfomap.com}} | |||
*{{LinkSummary|Singaporeera.com}} | |||
*{{LinkSummary|Singdaotimes.com}} | |||
*{{LinkSummary|Todayinsg.com}} | |||
*{{LinkSummary|Lioncitylife.com}} | |||
*{{LinkSummary|Singapuranow.com}} | |||
*{{LinkSummary|Voasg.com}} | |||
*{{LinkSummary|Singdaopr.com}} | |||
*{{LinkSummary|Alamak.io}} | |||
Singapore government just had this ten websites blocked for "potential hostile information campaign", stating that these websites are using domains either resembles legitimate news websites (i.e. zaobao.sg vs zaobaodaily.com) or gives an appearance that they have a connection to Singapore; content are AI-generated; gives an appearance that certain sentiments are an reflection of Singapore's public and/or government. | |||
JMF suggested to add the following bit from my talk page: | |||
* News: https://www.channelnewsasia.com/singapore/mha-imda-websites-hostile-information-campaign-foreign-interference-fica-4692746 | |||
*Press release: https://www.imda.gov.sg/resources/press-releases-factsheets-and-speeches/press-releases/2024/ten-inauthentic-websites-blocked | |||
* Annex containing the ten websites: https://www.imda.gov.sg/-/media/imda/files/news-and-events/media-room/media-releases/2024/10/ten-inauthentic-websites-blocked/annex-b-list-of-websites.pdf | |||
::::You escaped sanction because there were too many more egregious cases in the pipeline and it is a first offence. ANI does not adjudicate on content disputes, only on behaviour and compliance with fundamental principles. The evidence against you was really unarguable; I have seen quite a few cases and I know how they play out: if it had reached a conclusion, you would have been blocked until you acknowledged that you had gotten carried away in the heat of the moment, that you understand and accept ], ], ] and ], and that from now on you commit to respecting them. I strongly advise that you take the message anyway. --] (]) 12:47, 5 January 2025 (UTC) | |||
While my first instinct is to put these sites onto the spam blacklist, given that Singapore does engage in censorship practices that include blocking websites for not following ] orders/directives (among other reasons/laws), I would like second opinions before doing so. Out of the ten, one (alamak.io) has been used as a source for two articles on English Misplaced Pages. ] (]) 10:21, 22 October 2024 (UTC) | |||
:::::Mate, sorry I was late for the escalation party. End of the year was a madhouse here, both in business and with social activities. | |||
:::::I was very happy you did escalate and will be happy to reply now that I have spare time available for WP. My business legal department is pretty exited about it, like a kid in a candy store, can't wait to put its teeth in WP rules and regulations. | |||
:::::Would you like me to repost your escalation? ] (]) 12:52, 5 January 2025 (UTC) | |||
::::::I strongly advise that you read ] before you write another line. ] (]) 15:27, 5 January 2025 (UTC) | |||
{{od}} | |||
I am so sorry I was late to join this party. End of the year was a bit too hectic, did not leave much spare time for fun activities like WP. | |||
] What would you like me to do now? ] (]) 04:54, 6 January 2025 (UTC) | |||
* We generally only put websites onto the spam blacklist if they are actually being used for spamming. If the issue is unreliability (and frankly I wouldn't trust the Singaporean government on "internet reliability"), then you probably want ]. ] 10:33, 22 October 2024 (UTC) | |||
:It was not clear on your talk page, and it's even less clear here since you did not repost your response to JMF's last line there. You do explicitly retract the apparent legal threat that was made? - ] <sub>]</sub> 08:22, 6 January 2025 (UTC) | |||
*:{{tq| I wouldn't trust the Singaporean government on "internet reliability"}} heh. indeed. RSN does seem to be the right direction. ] (]) 10:53, 22 October 2024 (UTC) | |||
::I did not make a legal threat. ] (]) 08:33, 6 January 2025 (UTC) | |||
*::Concur that the spam blacklist is not the right place -- but don't we have a hoax noticeboard or something like that? Or had at one point? ]] <small><sup>Shoot Blues, Tell VileRat!</sup></small> 23:33, 22 October 2024 (UTC) | |||
:::@]: your reference to your "business legal team" could certainly be construed as a veiled one, at the very least. You are being asked to clarify by either confirming or retracting this. -- ] (]) 08:37, 6 January 2025 (UTC) | |||
*:::I don't think there is a hoax noticeboard (but I could be wrong about that!) – RSN does discuss hoax websites of various kinds, though. Discussions there sometimes lead to blacklisting (though usually only if a site has already been used as a source), but more importantly, a lot of editors experienced in evaluating hoaxes frequent that board. --'']'' <small>] ]</small> 09:11, 23 October 2024 (UTC) | |||
:::{{tqq|My business legal department is pretty exited about it, like a kid in a candy store, can't wait to put its teeth in WP rules and regulations.}} is either a legal threat or indistinguishable from one. - ] <sub>]</sub> 09:33, 6 January 2025 (UTC) | |||
*:::] is probably the closest we have to a hoax noticeboard, but it's more for dealing with content from pseudoscience/crank sources. — <b>]:<sup>]</sup></b> 22:42, 24 October 2024 (UTC) | |||
::::No it is not a legal threat. It is about <b>"WP rules and regulations"</b>, not about law. | |||
::::* To who would this be a threat? | |||
::::* Which law? | |||
::::* In which country? | |||
::::] (]) 09:57, 6 January 2025 (UTC) | |||
:::::Why would a legal department be involved? — ] (]) 12:02, 6 January 2025 (UTC) | |||
:::::It certainly looks like a legal threat. ] (]) 14:24, 6 January 2025 (UTC) | |||
:::::@]. Why would a legal department be involved? — ] (]) 17:14, 6 January 2025 (UTC) | |||
::::::Wow, I am glad you asked. | |||
::::::* to have a bit of fun, take a break from the normal, pretty serious work. It will be like kids in a candy store. | |||
::::::* It will be fun for me too. I can't wait to get going with this once the pandemonium calms down. | |||
::::::* The accusation "user:Uwappa: refusal to engage" is utterly wrong. | |||
::::::] (]) 22:47, 6 January 2025 (UTC) | |||
:::::::I'm not at all experienced in the legal world, but I don't think any professional legal team that you're paying money towards would ever be excited to save you from a website "like kids in a candy store". ] <sup>(]) (])</sup> 22:53, 6 January 2025 (UTC) | |||
:::::Why would a legal department be excited about you being reported on Misplaced Pages unless you're planning to use them in some way? ] <sup>(]) (])</sup> 17:14, 6 January 2025 (UTC) | |||
::::::I suspect, from context, that Uwappa was trying to suggest they would have assistance of a professional team in interrogating rules and regulations. But "I have the spend to wikilawyer this more than you can" isn't really all that much better than an outright legal threat. Between that and what surprises me is that they're not blocked yet frankly. ] (]) 17:23, 6 January 2025 (UTC) | |||
==Arbitration enforcement action appeal by IdanST== | |||
{{atop|Appeal overwhelmingly declined. ] (]) 22:44, 25 October 2024 (UTC)}} | |||
<small>''Procedural notes: The rules governing arbitration enforcement appeals are found ]. According to the procedures, a "clear and substantial consensus of uninvolved editors" is required to overturn an arbitration enforcement action.''</small> | |||
:and just to throw some more fuel on the bushfire, you have just accused me twice more of vandalism., . --] (]) 12:13, 6 January 2025 (UTC) | |||
<small>''To help determine any such consensus, involved editors may make brief statements in separate sections. Other editors may comment below. Editors are normally considered involved if they are in a current dispute with the sanctioning or sanctioned editor, or have taken part in disputes (if any) related to the contested enforcement action. Administrators having taken administrative actions are not normally considered involved for this reason alone (see ]).''</small> | |||
* I would say that for Uwappa to read this AN filing, reply to it (including something which could ''well'' be taken as a legal threat), and ''then'' immediately go back and the template for the fifth time (with an edit-summary of "Revert vandalism again", no less) shows a serious lack of self-awareness of the situation. ] 12:46, 6 January 2025 (UTC) | |||
; Appealing user : {{userlinks|IdanST}} | |||
*:Putting aside the possible legal threat, if Uwappa's business legal department is involved it seems likely to be a cause of ] or at least a ] which really should have been declared which doesn't seem to have happened. This also means Uwappa shouldn't be editing the article directly. ] (]) 14:06, 6 January 2025 (UTC) | |||
*::It’s hard to see a paid or COI element to the behaviour at {{tl|Body roundness index}}. — ] (]) 14:13, 6 January 2025 (UTC) | |||
*:::It is fairly weird, but I can't see any reason a business legal department would have any interest unless the editor's activity relates to their business activity. ] (]) 14:27, 6 January 2025 (UTC) | |||
*::::I expect it’s just empty talk to get an upper hand in the dispute. — ] (]) 14:37, 6 January 2025 (UTC) | |||
*::::: Indeed. It is night where Uwappa is now, but my inclination is to see what reaction there is when they restart editing. If it is another revert or a lack of discussion, a block (or at least a prtial block) is indicated. ] 15:05, 6 January 2025 (UTC) | |||
*::::::], how do you know where I am? Are you spying on me, disclosing personal information? | |||
*::::::* Anybody in the room who ]? | |||
*::::::* Reverted vandalism 3rd time in 24 hours. Anybody curious about what the vandalism is? | |||
*::::::* Anybody in the room that wonders why I had to do the repost? Isn't that odd in combination with "user:Uwappa: refusal to engage with WP:BRD process"? Did anybody read ]? | |||
*::::::* Did anybody read ] and ]? | |||
*::::::* Did anybody spot any incompleteness in the accusations? | |||
*::::::* Anybody interested in my to answers to the accusations? | |||
*::::::] (]) 16:59, 6 January 2025 (UTC) | |||
::::::::* JMF above said you were in Australia and I had no reason to disbelieve him. If you aren't, it's irrelevant really, I was just pointing out that you may not edit for a few hours. No-one here is required to answer your questions, but I will; the point was that you invoked something that could be a legal threat {{tq|My business legal department is pretty exited about it ... can't wait to put its teeth in WP rules and regulations.}} You say that isn't a legal threat, well fine, but you haven't explained what it ''was''. Meanwhile, you're ''still'' edit-warring on the template and claiming that other's edits are vandalism, which they clearly aren't, which is why you can no longer edit it. Have I missed anything? ] 17:51, 6 January 2025 (UTC) | |||
::::::::* Again, that was either a legal threat or actions indistinguishable from a legal threat in an attempt to cause a ]. When called on it you have continually ] instead of straight-up saying "no, that was not a legal threat and I am not involving any legal actions in this". So to make it very clear: you need to clearly state that or be blocked per ]. - ] <sub>]</sub> 20:31, 6 January 2025 (UTC) | |||
And just to add to the excitement, Uwappa has just repeated their allegation of vandalism against me and reverted to their preferred version of the template for the ''sixth'' time. (Their edit note adds ''3rd time in 24 hours'': are they boasting of a 3RR vio? {{u|Zefr}} undid their fourth attempt, I undid their fifth attempt, but possibly they misread the sequence.) --] (]) 17:41, 6 January 2025 (UTC) | |||
; Sanction being appealed : One month block by {{user|ScottishFinnishRadish}} for repeated ECR violations | |||
* Yes, I noticed. I have pblocked them indefinitely from the template, and reverted that edit myself so that no-one else is required to violate 3RR. ] 17:51, 6 January 2025 (UTC) | |||
:* Ha ha ha, this is beyond ridiculous. {{Blockquote|text=An editor must not perform {{strong|more}} than three reverts on a single page whether involving the same or different material—within a {{strong|24-hour period}}.|source=]}}. | |||
; Administrator imposing the sanction : {{admin|ScottishFinnishRadish}} | |||
:* Suggestion: Add the following calculator to ]: | |||
{{calculator|id=edits|type=number|steps=1|size=3|default=3|min=0}} | |||
; Notification of that administrator : I'm aware. ] (]) 12:56, 22 October 2024 (UTC) | |||
{{calculator-hideifzero|formula=ifless(edits,3)|starthidden=1|is less than three.}} | |||
{{calculator-hideifzero|formula=ifequal(edits,3)|is equal to three.}} | |||
{{calculator-hideifzero|formula=ifgreater(edits,3)|starthidden=1|is more than three.}} | |||
:* ] (]) 22:30, 6 January 2025 (UTC) | |||
===Statement by IdanST=== | |||
::* From ]; {{tq|Even without a 3RR violation, an administrator may still act if they believe a user's behavior constitutes edit warring}}. Which this quite obviously does, especially as you've reverted ''twice'' whilst this report was ongoing. Frankly, you're quite fortunate it was only a partial block. ] 22:41, 6 January 2025 (UTC) | |||
:To admins, please ] Uwappa from further work on the calculator template for the body roundness index and waist-to-height ratio, and from further editing and talk page input on those articles. Uwappa has done admirable extensive work, but the simple calculator is finished and sufficient as it is. Uwappa has created voluminous ]/] talk page discussions for articles with under 50 watchers and few talk page discussants; few editors would read through those long posts, and few are engaged. | |||
''I believe my ban is unjustified for the following reasons: 1.'' one is clearly an edit request under ] Section A.1. - pointing out that ] "source" is a LIE. Maariv '''NEVER''' reported on this lie, the source is in fact Al Jazeera which has been proven to have lied in this instance, as shown ]. 2. is not an incivility nor breaking the rules, it's allowed under ]. 3. is a warning before taking actions, like reporting, for blatant violations of ] and ]. I understand now that I should have reported the user instead of leaving a notice on their talk page, as it seems that discussing and warning is discouraged, and direct reporting and banning are preferred. | |||
:In recent edits on templates, Uwappa reverts changes to the basic template as "vandalism". No, what we're saying is "leave it alone, take a rest, and come back in a few years when more clinical research is completed." ] (]) 18:21, 6 January 2025 (UTC) | |||
:] (]) 10:37, 22 October 2024 (UTC) | |||
{{ab}} | |||
::I want to clarify that I appealed the first block. | |||
*This was closed, but...Uwappa's reply to their block was . Suggest revoking TPA. {{ping|Black Kite}} - ] <sub>]</sub> 06:15, 8 January 2025 (UTC) | |||
**. I've revoked TPA. - ] <sub>]</sub> 06:59, 13 January 2025 (UTC) | |||
== Kansascitt1225 ban appeal == | |||
===Statement by ScottishFinnishRadish (IdanST appeal)=== | |||
{{atop green|result=Appeal successful. There were some murmurings requesting a topic ban from Kansas, but nothing approaching consensus. Of course, ] would be well-advised to be careful not to go back to the behaviors that led to a block in the first place. But in the meantime, welcome back. <b>]]</b> (] • he/they) 19:59, 15 January 2025 (UTC)}} | |||
First block for a week was based on , , and which are all clear ECR violations. Their talk page access was pulled by {{u|Doug Weller}}. When the block expired their first edits were , , and , which are also clear ECR violations. They continued with personal attacks on their talk page and again had their talk page access removed. Oh, and the Simple English Misplaced Pages page on barnstars doesn't have much weight on en.wiki. ] (]) 13:54, 22 October 2024 (UTC) | |||
I am posting the following appeal on behalf of {{user21|Kansascitt1225}}, who is considered banned by the community per ]: | |||
(keeping it short for WP:TLDR) Hi Misplaced Pages community, it has been over 1 year since I edited on Misplaced Pages without evading my block or breaking community rules. I would like to be given another chance to edit. I realized that my blocking was due to my behavior of creating multiple accounts and using them on the same page and creating issues during a disagreement. I was younger then and am now able to communicate more effectively with others. I intend to respect community rules and not be disruptive to the community. I was upset years ago when I mentioned Kansas City’s urban decay and it was reverted as false and I improperly reacted in a disruptive way that violated the community rules. The mistake I made which caused the disruptive behavior was that I genuinely thought people were reverting my edits due to the racist past of this county and keeping out blacks and having a dislike for the county. I also thought suburbs always had more single family housing and less jobs than cities. In this part of the United States a suburb means something different than what it means in other parts of the world and is more of a political term for other municipalities which caught me off guard and wasn’t what I grew up thinking a suburb was.<ref>{{cite web|url=https://slate.com/business/2015/05/urban-density-nearly-half-of-america-s-biggest-cities-look-like-giant-suburbs.html}}</ref> Some of these suburbs have lower single family housing rates and higher population density and this specific county has more jobs than the “major city” (referenced in previous unblock request if interested). This doesn’t excuse my behavior but shows why I was confused and I should have properly addressed it in the talk pages instead of edit warring or creating accounts. After my initial blocking, I made edits trying to improve the project thinking that would help my case when it actually does the opposite because I was bypassing my block which got me community banned to due the automatic 3 strikes rule. I have not since bypassed my block. I’m interested in car related things as well as cities and populations of the United States and want to improve these articles using good strong references. Thanks for reading. ] (]) 04:46, 27 December 2024 (UTC) | |||
===Statement by Doug Weller (IdanST appeal)=== | |||
IdanST says that was an edit request under WP:ECR Section A.1. which it clearly is not, just a statement that something is a lie. is a personal attack on ScottishFinnishRadish. Yet more attacks ] ] 15:15, 22 October 2024 (UTC) | |||
{{reflist-talk}} ] (]/]) 21:22, 7 January 2025 (UTC) | |||
===Statement by (involved editor 1)=== | |||
* '''(mildly involved) Support'''. I gave feedback on an earlier version of their ban appeal. This is five years since the initial block. Five years and many, many socks, and many, many arguments. But with no recent ban evasion and a commitment to communicate better, I think it's time to give a second chance. -- ] (]) 21:42, 7 January 2025 (UTC) | |||
*'''Support''' per asilvering and ]. ] (]/]) 21:44, 7 January 2025 (UTC) | |||
===Statement by (involved editor 2)=== | |||
*'''Support'''. Five years is a long time. Willing to trust for a second chance.] (]) 21:49, 7 January 2025 (UTC) | |||
* Ideally I'd want to see some indication that they don't intend to ] as the issue seems to be rather ideological in nature and I don't see that addressed in the appeal. I also don't love the failure to understand a lot of issues around their block/conduct and their inability to effectively communicate ] and on their ]. ] (]) 00:00, 8 January 2025 (UTC) | |||
===Discussion among uninvolved editors about the appeal by IdanST === | |||
*:Would a topic ban from Kansas-related topics help? This was floated as a bare minimum two or so years ago. -- ] (]) 00:32, 8 January 2025 (UTC) | |||
*:I'm not that concerned by the RGW issue. Their communication on this appeal has been clear, they responded to my feedback regarding their unblock request, and they've indicated they'll not edit war and seek consensus for their edits. ] (]/]) 00:46, 8 January 2025 (UTC) | |||
<!-- When closing this request (once there is a consensus) use {{hat|Result}} / {{hab}} if at AE, or an archive/discussion box template if on AN, inform the user on their talk page and note it in the contentious topics log below where their sanctions is logged. --> | |||
*Is my maths just bad or is January 2019 not six years ago rather than five? In any event it's been a long time since they tried to evade. I'm leaning toward giving a second chance but I'd really like them to understand that walls of text are not a good way to communicate, that they need to post in paragraphs, and that Misplaced Pages is not a place for righting great wrongs. ] (]) 16:27, 8 January 2025 (UTC) | |||
*I may be a simple Wikipedian farmer of minor corrections and !votes, but a few things confuse me. | |||
*:{{tq|Is my maths just bad or is January 2019 not six years ago rather than five?}} ssssshhh. -- ] (]) 18:02, 8 January 2025 (UTC) | |||
*#Why aren't these pages under ECR protection? It seems that this is a simple solution to the problem | |||
*:] from KC:{{tq2|Yes I can write in paragraphs and list different ideas in separate paragraphs instead of a giant run on sentence.{{pb}}I wasn’t trying to right great wrongs but noticed the contrast of the definition of ] on Misplaced Pages and these communities being described as suburban (meanwhile some of these suburbs verifiably having lower residential to job ratio than the city and also a higher overall population density with some suburbs gaining population during the day due to commuters coming into them). This is essentially why on my case page It says I feel as tho something had to be “fixed”. I thought my edits were being removed simply because people didn’t like this place or some of its past so I felt as tho I was simply being purposefully misled which caused me to not follow proper civility.{{pb}}I just wanted to clarify that these places weren’t only residential and were major employment areas that they sometimes have a lower percentage of single family homes. This to me was always the opposite of what suburban meant, atleast what I learned during grade school and what it says on Misplaced Pages. That’s where the confusion came from. Kansascitt1225 (talk) 06:17, 13 January 2025 (UTC)}} ] (]/]) 02:19, 15 January 2025 (UTC) | |||
*#Some of these cited by SFR and Doug seem to fall under ], not "clear ECR violations". We need to be a little more precise if we're going to ban/block people. Those alone are worthy of a block given previous interactions. | |||
*'''Support''' Six years is a long time, and they have shown growth. I do not think what is actually happening here is ], instead they ] and things went downhill from there. I think ] of {{tq|Jackson county being THE central county of the metropolitan area}} (which Misplaced Pages deems urban) {{tq|when you can see in the census reference here there are actually 6 central counties}} (which Misplaced Pages deems suburban) is reasonable. I researched it, but found the concerns are inconsistent with ] page which provides the definition that {{tq|An urban area is a human settlement with a high population density and an infrastructure of built environment. This is the core of a metropolitan statistical area in the United States, if it contains a population of more than 50,000.}} An urban area is the most urban area compared to its surroundings, even though its surroundings are quite dense. I hope this helps. ] (]) 22:54, 12 January 2025 (UTC) | |||
:] (]) 15:35, 22 October 2024 (UTC) | |||
*:I add that their concerns that suburban designation misleads people seem to have merit. It is not the suburban designation that misleads people though, but the definition of suburban itself on the ] article seems to be misleading. I know this is not a place to discuss content, but discuss conduct. But some insight into content can help resolve problems. ] (]) 11:56, 13 January 2025 (UTC) | |||
::Non-EC editors are allowed to make edit requests on the talk pages. Generally, article talk pages aren't ECP unless there is enough disruption to necessitate it. ] (]) 15:41, 22 October 2024 (UTC) | |||
:::These do not appear to be edit requests, but personal attacks. That they were on an ARBPIA talk page seems immaterial. ] (]) 16:58, 23 October 2024 (UTC) | |||
::A personal attack explicitly and particularly related to an ECR topic area, such as {{tq|Your Constant Lies ...regarding Israel and Arab–Israeli conflict}}, is surely a clear two-fer. ] (]) 18:39, 22 October 2024 (UTC) | |||
:::YMMV, I suppose. NPA seems to be reason enough for a block without additional justification. If anything, such behavior there should be grounds for ADDITIONAL measures ] (]) 17:00, 23 October 2024 (UTC) | |||
*Nothing about this appeal gives me confidence that this editor will be a net positive with respect to ARBPIA content. ] (]) 15:38, 22 October 2024 (UTC) | |||
* This edit is clearly note an edit request and the editor had been previously warned, I would oppose the appeal. -- <small>LCU</small> ''']''' <small>''«]» °]°''</small> 15:41, 22 October 2024 (UTC) | |||
*IdanST chooses to defend only three of their edits, and their very first defence demonstrates the appropriateness of the current block. was clearly not a request, let alone an ] under WP:ECR Section A.1, and that IdanST claims that it was, and makes no attempt to suggest their editing will improve, shows that this block and maybe more will be needed until they understand and accept the various limitations and restrictions on their editing. ] (]) 19:09, 22 October 2024 (UTC) | |||
*The appeal should be declined for the reasons set out by ScottishFinnishRadish. Additionally, the polemical style of the appeal and the appellant's personal attacks and their mischaracterization of their edits indicate that the appellant should be topic-banned from the Arab-Israeli conflict as unsuited to collaborative work. <small><span style="border:1px solid black;padding:1px;">]</span></small> 19:16, 22 October 2024 (UTC) | |||
*:I don't think a topic ban would be effective as the existing extended-confirmed restriction is being ignored. ] (]) 19:23, 22 October 2024 (UTC) | |||
{{abot}} | {{abot}} | ||
== ftools is back! == | |||
== 2024 Hezbollah headquarters strike == | |||
I am proud to announce that I have become the new maintainer of Fastily's <code>ftools</code>, which is live ]. And yes, this includes the IP range calculator! ]<sub>]<sub>]</sub></sub> (]/]) 23:12, 9 January 2025 (UTC) | |||
The article ] has a move request at ]. It has started on September 27 and should have been open for just a week; we're almost in a full month. The last vote was made on October 7. I know that this is a controversial topic, even reached with arbitration remedies, but ''someone'' should close it (although non-admin closures may be valid, it may be better if an admin closes it, considering the controversial nature of the topic). ] (]) 16:49, 23 October 2024 (UTC) | |||
:{{ |
:{{like}} -] (]) 23:15, 9 January 2025 (UTC) | ||
:Note: {{no ping|DreamRimmer}} is now also a maintainer. ]<sub>]<sub>]</sub></sub> (]/]) 15:47, 10 January 2025 (UTC) | |||
:My congratulations/condolences. ] (]) 15:49, 11 January 2025 (UTC) | |||
:So, will ftools be renamed or not? Congratulations. ] (]) 02:32, 14 January 2025 (UTC) | |||
== WDBZ == | |||
== Block appeal for ] == | |||
] was made on 24.09. Today 24.10 they made 500 edits to their talk page like this . They then got the "extendedconfirmed" user group because they were created 30 days ago and made 500 edits. Could an admin remove this group please? ] (]) 07:38, 24 October 2024 (UTC) | |||
{{atop | |||
:They are now ] and it looks like a "MidAtlanticBaby" puppet. They should be blocked. ] (]) 07:43, 24 October 2024 (UTC) | |||
| status = unblock denied | |||
::Blocked. ] (]) 07:59, 24 October 2024 (UTC) | |||
::: ] Could you block ? This account was created on the same date and is doing the same thing now of ramping up edits. ] (]) 08:01, 24 October 2024 (UTC) | |||
::::@] got there before me. Any CU around who can do a sweep for sleepers? ] (]) 08:06, 24 October 2024 (UTC) | |||
:::::I've had a look. Those familiar with the matter will know that that might not portend much. Informed by my magic goggles, I've also preemptively removed TPA from the 2nd account. -- ] <sup>]</sup> 09:17, 24 October 2024 (UTC) | |||
::::::Thank you all for your help. ] (]) 10:09, 24 October 2024 (UTC) | |||
| result = AKG has withdrawn the request. In any case, I see too many misgivings even on the "support" side to consider an unblock at this time. ] (]) 02:33, 11 January 2025 (UTC) | |||
== Administrator Elections: Voting phase == | |||
}} | |||
I am bringing a somewhat unusual unblock request here for broader community input. {{u|Aman.kumar.goel}} has been blocked for more than a year for sockpuppetry (see ]). As you can see in the unblock request at ], they have agreed to a one-account restriction as an unblock condition, and there is no CU-confirmed evidence of recent sockpuppetry. However, {{u|Ivanvector}}, who made that check, is skeptical and has declined to support an unblock. A topic ban from ] and ] were floated as additional possible conditions, but no agreement was reached, and Aman.kumar.goel has requested that their unblock request be considered by the wider community. Their statement is as follows: | |||
<div style="border: 5px solid #ABCDEF ; padding:10px 15px"> | |||
<div style="padding: 0 0 0.5em; vertical-align: middle; font-size:130%"> '''] | <span style="font-size:85%">Voting phase</span>''' | |||
</div> | |||
<div style="display:flex; align-items:center;"> | |||
<div> | |||
The voting phase of the October 2024 administrator elections has started and continues until 23:59 31st October 2024 UTC. You can participate in the voting phase at ]. | |||
:I was blocked for sockpuppetry. There was no doubt throughout the discussion over that. I have agreed to a one-account restriction. However, during the unblock request, a topic ban on me was proposed from ] (WP:ARBPIA) and also from ] (WP:ARBIPA). Though no proper evidence was provided to substantiate such proposals. | |||
As a reminder, the schedule of the election is: | |||
*October 25–31 - SecurePoll voting phase | |||
*November 1–? - Scrutineering phase | |||
:While the proposal to topic ban me from WP:ARBPIA does not make any sense because I haven't even edited that area, I would nevertheless reject the proposed topic ban from WP:ARBIPA with explanation because in this area I have been significantly active. | |||
In the voting phase, the candidate subpages will close to public questions and discussion, and everyone ] will have a week to use the ] software to vote, which uses a ]. You can see who voted, but not who they voted for. Please note that the vote tallies cannot be made public until after voting has ended and as such, it will not be possible for you to see an individual candidate's tally during the election. The ] are different from those at RFA. | |||
:My edits on WP:ARBIPA were clearly net-positive, and they fixed the long-term problems that were otherwise overlooked for a long time. You can find the deletion of a number of non-notable pro-Hindutva articles, creation of SPIs of future LTAs, and multiple DYKs. That said, the idea to topic ban me achieves nothing good. Black Kite himself said "{{tq|The edits aren't the issue here, it's socking in the IPA area that is.}}". However, for the offense of sockpuppetry, I have already agreed to one-account restriction and spent over 1 year blocked. | |||
Once voting concludes, we will begin the scrutineering phase, which will last for an indeterminate amount of time, perhaps a week or two. Once everything is certified, the results will be posted on the ]. In order to be granted adminship, a candidate must have received at least 70.0% support, calculated as Support / (Support + Oppose). As this is a vote and not a consensus, there are no ] ("crat chats"). | |||
:Once unblocked, I would like to improve drafts such as ] and ]. Looking forward to positive feedback. ''']''' <sup>('']'')</sup> 00:51, 10 January 2025 (UTC) | |||
Any questions or issues can be asked on the ]. Thank you for your participation. Happy electing. | |||
</div> | |||
<div>]</div> | |||
</div> | |||
<div style="font-size:85%; padding-top:15px;"> | |||
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please ].</div> | |||
</div> | |||
] (]) 00:30, 25 October 2024 (UTC) | |||
<!-- Message sent by User:Robertsky@enwiki using the list at https://en.wikipedia.org/search/?title=Misplaced Pages:Administrator_elections/Newsletter_list&oldid=1253182481 --> | |||
] (]) 01:23, 10 January 2025 (UTC) | |||
== Arbitration committee 2024 election: nominations to start on November 3 == | |||
*'''Support unblock without TBANs and with single account restriction.'''] (]) 01:43, 10 January 2025 (UTC) | |||
*'''Support''' as requested. The request is sincere. Having edited a fair amount of articles where I discovered this editor's edits, I found his edits thoroughly productive and that is absolutely uncommon in this area. ] <small><small>]</small></small> 01:44, 10 January 2025 (UTC) | |||
The nomination period for the ] will start on November 3. If there is someone you'd like to see run, or if you want to know someone else's plans before making your own decision, I encourage you to talk to them now, well in advance of the election. For more information about the work involved with serving on the committee, see the ] page. ] (]) 01:50, 25 October 2024 (UTC) | |||
:* '''Comment''' "Support as requested" sounds like a canvassed vote, did you mean it in a different way? ] 08:48, 10 January 2025 (UTC) | |||
:*:You need to re-check. , AKG posted a "request" for "unblock". By "as requested" , I meant how AKG requested himself to be unblocked, that is without any topic bans. Also, see ]. ] <small><small>]</small></small> 11:05, 10 January 2025 (UTC) | |||
:::* I did AGF, otherwise my sentence would not have included the second clause. I understand what you mean ''now'' but I did not from the original posting. ] 15:25, 10 January 2025 (UTC) | |||
*Aman.kumar.goel's explanation for the relationship with Editorkamran is {{tq|we knew each other in real life, and we used the same internet and the same system sometime, and also helped each other at times with Misplaced Pages editing}}, but Ivanvector says the CU data indicates {{tq|someone who had been carefully using two or probably more accounts for quite some time and going to lengths to obscure the connection, but made a mistake just one time that exposed them}}. I don't know who's right, but this is a CU block, so if Aman.kumar.goel stands by his answer, I'd be uncomfortable unblocking unless another CU has a different interpretation of what happened. ] (]) 01:55, 10 January 2025 (UTC) | |||
*:@], ] from AKG copied over:{{tq2|Hope you will check my statement above where I explained, "{{tq|However, upon reading further following the block, I realised that what I did was a violation of WP:SOCK because the use of both these accounts was prohibited by the policy, especially WP:SHARE and WP:MEAT.}}" That means the CU finding does not really challenge my admission because I don't deny using multiple accounts. The only thing I happened to clarify was that the two accounts belonged to two different persons before they were used by the same person, which is me. That's why, in my unblock request (for ]), I have also cited the edits of Editorkamran account as part of my edits into this area. Aman Kumar Goel (Talk) 02:43, 10 January 2025 (UTC)}} ] (]/]) 02:46, 10 January 2025 (UTC) | |||
*::All I know about this case is what I can glean by reading the private case notes, which do indeed support what Ivanvector has said. But given that AKG has admitted (on their talk page) to using the Editorkamran account, that's all kind of moot. I'd still like to hear Ivan's latest opinion on this, and I've also pinged off-wiki another CU who is familiar with this case, but my personal feeling is that we should draw a line in the sand and accept the unblock request with the single account restriction, no ARBPIA/IPA/API/TLA restriction, and an understanding that AKG's account at the bank of AGF is empty. ] ] 03:05, 10 January 2025 (UTC) | |||
*:::Oh, the other thing I wanted to mention is that on unblock requests, we're often left wondering what the user plans to work on if unblocked. In this case, they've specified two extant drafts they want to complete, both of which look like they have the potential to be useful articles. So that's a plus. ] ] 03:22, 10 January 2025 (UTC) | |||
*::Am I the only one to feel that their earlier statements, even if they did mention ] would not reasonably be understood to an admission that they did eventually user the Editorkamran account? Especially with all that comment about "we used the same internet and the same system sometime" etc? To my read the earlier statement gives the impression that they each account was only ever used by one person even if they did communicate and coordinate their editing at times. It's only most recently that I feel they've finally made it clear they it wasn't simply a matter of communication and coordination but rather that did use the other account directly. This also leads to the obvious question. How could any editor actually think it's okay for them to use some other editor's account just because it primarily belongs to another editor? Whether you consider it ]ing or whatever, you should not need any real experience to know it's unacceptable and definitely any editor with AKG's experience should know that. Note that I'm not suggesting that an editor who did what AKG did can never be unblocked, definitely they can be. But IMO there are good reasons to call into question whether the editor is ready for an unblock when they seem to have been so dishonest in their unblock request. In other words, if said something like 'yes I did X, I knew it was wrong and should not have done it, I promise not to do it again' rather than what they actually said, I'd be much more inclined to consider an unblock. ] (]) 10:14, 10 January 2025 (UTC) | |||
*:For what it's worth: I'm the other CU mentioned by Roy. I had run the initial checks and written some contemporaneous notes. I agree with {{u|Ivanvector}}'s assessment at the talk page appeal; there was a concerted, long-term effort to obfuscate the connection between these accounts, which doesn't really fit with the ] that they only realised they were doing something wrong after the fact. Whether a second individual ''also'' had access to either account at times can't really be retroactively assessed with any certainty, but it also seems immaterial to the finding of socking. --] (]) 17:39, 10 January 2025 (UTC) | |||
*'''Support''' with 1 account restriction. A prolific editor with no recurring issues. Understands where he was wrong. ] (]) 03:04, 10 January 2025 (UTC) | |||
*'''Support''': I have edited in South Asian-related topics and have run across some edits made by User:Aman.kumar.goel. Of these, I have seen several constructive edits made by him that have overall improved Misplaced Pages. Additionally, being blocked for one year is enough of a penance, which I'm sure has given him time to reflect. In view of this, I support his request in good faith. I hope this helps. With regards, ]<sup>]</sup> 03:49, 10 January 2025 (UTC) | |||
*'''Support''' with one account restriction and no topic restriction. We need competent editors working in the India topic area, as long as they follow policies and guidelines. The editor should be aware that ] applies here. ] (]) 05:17, 10 January 2025 (UTC) | |||
*'''Oppose'''. I warned AKG ] for tag-team editing with Srijanx22, after many instances of one showing up to a content dispute the other was in to back them up. AKG didn't understand then what the issue was. He didn't understand it when he was blocked for socking with Editorkamran. He doesn't seem to understand it now. The semantics of sockpuppetry vs. "just" meatpuppetry are uncompelling. We indeed need more competent editors in the India topic area. We are not going to get closer to that by letting in someone who has shown willingness to serially manipulate interactions in that topic area, who managed to evade detection for years, who continued doing so after a first warning, and whose explanation is, apparently, unpersuasive to CUs who have reviewed the evidence. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 06:51, 10 January 2025 (UTC) | |||
*:It has been sufficiently confirmed throughout these years that the false allegation of tag teaming was indeed false. Do you see me in any of the events that have been mentioned so far in this unblock request? You don't. It is disappointing to see you bringing up your misleading observation you made when you weren't even an admin. You did not even ping me. Oh, and don't ask me how I got here because I watch this noticeboard and have edited it before.] (]) 07:52, 10 January 2025 (UTC) | |||
*::I'm glad that you heeded my warning and stopped tag-teaming with AKG. AKG, however, continued to manipulate consensus in the topic area, which is what he got indeffed for. I didn't ping you because I'm not making any comment on your fitness as an editor; I just wanted to be clear that that 2021 report was separate from the Editorkamran case. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 08:13, 10 January 2025 (UTC) | |||
*:::To quote what I had said then, "{{blue|I am comfortable with ignoring your 'warning' since it lacks policy backing.}}" I said that because no tag teaming on my part ever happened in the first place and the time has proven me correct. I would reiterate that you are supposed to ping the editor whose behavior is being discussed. In this case, you had to. ] (]) 09:10, 10 January 2025 (UTC) | |||
*:::: Actually, the SPI makes it clear that there ''were'' multiple examples of you reverting to the same version as AKG in rapid succession, whether you were co-ordinating off-wiki with AKG or not. As well as those, I could add ] on 1st December 2020 and 21st February 2021 and ] on 19 April 2020. So please give it a rest with the denials and instead ensure that it doesn't happen in the future if AKG is unblocked. ] 11:00, 10 January 2025 (UTC) | |||
*:::::That's totally superficial. I have also edited both of these popular articles and so have many others I can count on my fingers. ] (]) 16:10, 10 January 2025 (UTC) | |||
*:::::: Yes, but that's not the point; have you reverted to a version also reverted to by AKG within < 24h on multiple occasions? I suspect not. ] 18:59, 10 January 2025 (UTC) | |||
*'''Support''' per NxCrypto and RoySmith. I don't see any issue with unblocking right away. The presence of this editor is a net-benefit for this area. ] (]) 07:14, 10 January 2025 (UTC) | |||
*'''Comment''' If unblocked, I would like to see AKG stay away from ]. There were a number of times - I count at least nine times between 2020 and 2023 - that they opened cases here trying to get editors on the "opposing" side blocked, and I don't think continuing this is a good idea. I also note that they were very active at SPI cases involving other editors in ARBIPA, which is another sign of BATTLEGROUND behaviour. ] 08:46, 10 January 2025 (UTC) | |||
*:That, and the refusal to accept TBANs, gives me bad vibes. | |||
*:I also don't think that agreeing to use only one account is much of a concession, that's kind of a given, but I guess it's at least better than ''not'' agreeing to it. -- ] (]) 08:56, 10 January 2025 (UTC) | |||
*:: Yes, this is also my concern. I would have ''thought'' that we would expect an editor banned for socking in a CTOP to at least demonstrate their ability to collaborate well ''outside'' that CTOP before being allowed to edit it. I can understand the Support !votes above from other editors who generally edit from the same POV as AKG, but I'm still not thinking this is a brilliant idea. ] 11:15, 10 January 2025 (UTC) | |||
*:::What is that "same POV as AKG"? It is certainly not their fault that you are assuming bad faith. ] (]) 16:12, 10 January 2025 (UTC) | |||
*:::: I don't need to AGF when the evidence is quite plain, as with the editor I mentioned above where I pointed out their tag-teaming issues. ] 19:02, 10 January 2025 (UTC) | |||
*'''Oppose'''. This user edits via proxy with IPBE, and the breadth and depth of the deception shown at that SPI is considerable. Now they're back with a semi-plausible explanation, and I don't buy it. And the one-account restriction is more challenging to police with a proxy/IPBE setup.—] <small>]/]</small> 09:27, 10 January 2025 (UTC) | |||
:*If he has agreed to one account restriction and this socking episode makes him ineligible for any future IPBE right, so what's wrong in allowing him back in since he has already served a year of block? Unless you are suggesting we completely ban those who have engaged in sock puppetry altogether, which is unrealistic. ] (]) 11:08, 10 January 2025 (UTC) | |||
::*What's wrong in allowing him back is everything Ivanvector says in that SPI. Please read it carefully and then re-read AKG's unblock request with a critical eye.—] <small>]/]</small> 12:38, 10 January 2025 (UTC) | |||
*'''Oppose'''. I would support unblocking with an ARBIPA topic ban (which could be appealed later when AKG has proved they can edit well outside that area). But since AKG will not accept that TBAN I can only Oppose at the moment. ] 11:17, 10 January 2025 (UTC) | |||
*'''Support''' - The request is convincing and to-the-point. Those opposing are seemingly forgetting that it has been more than a year since this editor has been blocked. ] (]) 12:33, 10 January 2025 (UTC) | |||
*'''Support''' per above without any topic ban. It is totally unreasonable to seek punishment over the same offense even after WP:SO has been sufficiently met. ] (]) 12:59, 10 January 2025 (UTC) | |||
*:It is not at all unusual for editors seeking an unblock to be required to accept a topic ban as a precondition to that unblock. are are recent examples from this noticeboard. ] (]) 15:04, 10 January 2025 (UTC) | |||
*::Whilst I don't support the topic ban, it would not be done as ''punishment'', but as a measure reducing the likelihood of further disruption. ] (]) 16:07, 10 January 2025 (UTC) | |||
*::Caeciliusinhorto-public not good to compare community banned editors with this case. ] (]) 16:13, 10 January 2025 (UTC) | |||
*'''Support''' per {{u|Ivanvector}}: i.e. dependent on {{blue|a topic ban from WP:ARBIPA and WP:ARBPIA and a single-account restriction}}. This will deal with the meat of the issue, while WP:ROPE should take care of the crust. ]'']''] 13:09, 10 January 2025 (UTC) | |||
*'''Oppose''' I find myself agreeing with {{U|Black Kite}} - if they are willing to come back with a topic ban that'd be one thing. Without it I'm concerned we'll just end up back at AN/I, SPI or AE again. ] (]) 13:42, 10 January 2025 (UTC) | |||
*:I will tentatively change my position to support provided it includes the topic ban. ] (]) 18:09, 10 January 2025 (UTC) | |||
*'''Oppose''' While I appreciate that brevity is required in unblock requests and people have different ways of writing stuff, as I noted above I feel the original unblock request was at a minimum intentionally evasive if not even misleading on whether Aman.kumar.goel had used the Editorkamran account directly. While they've now made it clear that they did so, the fact this only happened after editor questioned their story compared to the CU view makes me question whether it's because they didn't realise they were unclear or instead because they realised their evasiveness wasn't working. If they were evasive in their recent unblock request, this makes it very hard to trust Aman.kumar.goel. Further, even if Akg wasn't being evasive, it's very unclear why an editor with their experience didn't realise what they were doing was wrong until recently. I was originally willing to accept with a topic ban but frankly I'm now not even sure that's enough, but it's moot anyway. If this fails, I'd suggest on their next appeal Aman.kumar.goel ensures what they're telling us is clear from the get go. ] (]) 15:42, 10 January 2025 (UTC) | |||
*'''Support''' without topic ban. Sockpuppetry was the sole concern for the indefinite block. There is no evidence of any disruptive edits, as such the idea of topic ban makes zero sense. ] (]) 15:47, 10 January 2025 (UTC) | |||
*'''Oppose''' per Black Kite. Any unblock that doesn't involve a restriction on AKG's original area of disruption will simply allow for further disruption. ] ] <span style="color:#C8102E;"><small><sup>(])</sup></small></span> 16:13, 10 January 2025 (UTC) | |||
*:Not at all. Very recently, several editors editing this subject and socked were unblocked recently without any topic bans, including one more editor who was banned per 3x. ] <small><small>]</small></small> 16:23, 10 January 2025 (UTC) | |||
*'''Oppose''' per Nil Einne. Being "intentionally evasive if not even misleading" during this unblock request and previously makes it very hard for me to trust this user. I'm glad they owned up to their outright sockpuppetry with Editorkamran and had they done so from the beginning of the request, I'd have considered supporting the request, provided they accepted the topic ban(s) suggested (so as to increase the odds of their future success). --] (]) 16:25, 10 January 2025 (UTC) | |||
*'''Oppose''' unless an ARBIPA TBAN is applied. AKG's edits have not always been a positive: their approach to contentious matters has often been needlessly aggressive, and they haven't always been able to engage constructively with users and sources they disagree with. In that context sockpuppetry is more than "just" sockpuppetry. Some examples: , , , , , , and (These are discussions, not diffs, but I believe the context is needed to demonstrate the pattern I see). ] (]) 16:55, 10 January 2025 (UTC) | |||
*:<s>I would tentatively '''support''' with the TBAN they have now agreed to.</s> I have no opinion on whether a PIA ban is needed: if they have edited in that area I haven't seen it. I was considering suggesting a ban from bring others to AE/AN/ANI, but perhaps some rope is appropriate there. In any case they should be aware that they are on thin ice. I would also note that under no circumstances should they be given IPBE in the foreseeable future. ] (]) 18:02, 10 January 2025 (UTC) I'm sorry to vacillate like this, but based on comments by Ivanvector and Girth Summit I simply cannot support <small>(NB: while I am a CU, I am obviously not acting as a CU in this case)</small>. Despite our past disagreements I had been willing to give AKG another chance, but that was based on the assumption that they were being fully forthcoming, and based on the comments of CUs familiar with this situation, it doesn't appear that they have come clean. Put me down as a neutral, I suppose, though I remain opposed absent a TBAN. ] (]) 22:49, 10 January 2025 (UTC) | |||
*'''Oppose''': Per Vanamonde, Tamzin, and Black Kite. It's telling that they won't accept a TBAN from my point of view. They were disruptive prior to their block and, as much as I want to assume good faith, I feel strongly that their refusal signals their intent to immediate jump into said area. There's also the concern that they may end up chasing other editors away from the site if they continue their aggressive behaviour and approach, which frankly I expect based on the lengths they went to in the past and the TBAN issue. I think this user was a net negative, chased people away from those areas, and made it more difficult for others to get involved with. Unblocking this user would end up leading to editor time wasted and would be a further net negative. ] (]) 17:13, 10 January 2025 (UTC) | |||
*:Noting that I still oppose the unblock, even though they accepted the condition about a TBAN. I agree with Girth Summit that this seems to just be someone saying whatever they think will convince people to unblock them. I also firmly believe that allowing them back onto the project will be a net negative. ] (]) 20:12, 10 January 2025 (UTC) | |||
*'''Comment''' Aman.kumar.goel has requested this comment to be posted here from their talkpage: | |||
{{Talkquote|After seeing a number of editors, some of whom I respect, are supporting my unblock but only with a topic ban from ], I would like to accept the topic ban from the said area. Ping {{u|Yamla}}, {{u|The Kip}}, {{u|Black Kite}}, {{u|Caeciliusinhorto-public}}, {{u|Simonm223}} and {{u|Vanamonde93}}. Thanks ''']''' <sup>('']'')</sup> 17:08, 10 January 2025 (UTC)}} | |||
- ] (]) 17:46, 10 January 2025 (UTC) | |||
:Would they also consent to the ] topic ban? Because my understanding is that the ask was for both. ] (]) 17:47, 10 January 2025 (UTC) | |||
== Internal Error when opening ] == | |||
:: I don't believe the PIA issue is a problem, only the IPA one. ] 18:57, 10 January 2025 (UTC) | |||
*'''Oppose''' an unblock based on this request. When I'm looking at an unblock request, I try to get a sense of whether someone is actually coming clean and saying 'I did this thing, I recognise that was out of order and I undertake that I won't do it again', or something along those lines. In this case, I don't see that. In their unblock request of 10 December 2024 (just a month ago), AKG seems still to be saying that they were not using multiple accounts - their argument seems to be that they accept there was a violation of ] and ], but the two accounts were used by two different people from the same device. They have since swung round to acknowledging that they were in fact using the Editorkamram account, but are saying that they thought that was OK since the account really belonged to somebody else and they only used it from time to time. I'm afraid I simply don't believe that story, and I don't know what to think about their shifting narratives - I get the sense of someone saying whatever they think will convince people to unblock them, changing their story when it becomes apparent that it's not working, and failing to actually come clean about what they did and why they did it. If I don't trust someone in what they are saying in their unblock appeal, I don't trust them to abide by a one-account restriction - so, yeah, I don't think we can accept this request. Do some self-reflection, come back in six months with a frank and believable unblock request. ]] 18:35, 10 January 2025 (UTC) | |||
*'''Support'''. Seeing that AKG has agreed to the proposed IPA topic ban, the unblocking would be fine now. See no other issues. ] (]) 19:00, 10 January 2025 (UTC) | |||
*'''Support''' based on the comments from RoySmith and agree with their point that the AGF tank is gone for A.K.G. Any issues beyond a minor oops with their editing should be an immediate indef. No warnings, no "one last chance". That bridge was crossed, burned, torn down and barriers put up to block it from being rebuilt. ''']''' (]) 19:24, 10 January 2025 (UTC) | |||
::I hope A.K.G recognizes that is a last chance for them, and returning quickly to a contentious topic could be challenging for them to stay cool, engage in discussions but not disruption and that there will be enhanced scrutiny on their edits and willingness to take concerns to an admin board. They can't edit as they did before. ''']''' (]) 19:34, 10 January 2025 (UTC) | |||
*'''Oppose''' - I gave my reasons on the talk page; I don't trust this user. ] (<sup>]</sup>/<sub>]</sub>) 20:20, 10 January 2025 (UTC) | |||
*:Also I should point out that I was not involved whatsoever in the checks that led to this block; my comments on the talk page refer to emails I remember reading a year earlier on the private checkuser mailing list, which does not archive. I did check in relation to their unblock request recently and in my opinion that check was inconclusive; I elaborated on their user talk at the time. The result gives me pause because they had been using multiple accounts and evading checkuser for quite a long time before being blocked, while editing in one of our longest-designated contentious topics, one that's known to be very badly impacted by sockpuppetry and state-sanctioned disinformation campaigns. I suggested a topic ban from India-Pakistan for reasons that I think are already obvious from previous comments in this thread, and from Israel-Palestine because of something I thought I read on their talk page about a dispute in that topic, but I can't find that now and so I have to say I was probably out of line to have suggested it. But on the whole, I do not support unblocking, even with the proposed restriction. ] (<sup>]</sup>/<sub>]</sub>) 20:43, 10 January 2025 (UTC) | |||
*Very, very '''weak support''' on unblocking here with a one-account and indefinite IPA topic ban restriction. I found my engagement with the editor at their talk page today to be somewhere between obstructionist and disingenuous — and from reading the comments above, others have got similar vibes from different comments earlier in this process regarding the sockpuppetry and willingness to accept a topic ban condition. As Ravensfire notes above, the assume good faith tank is just about empty here — which means any non-trivial lapse or return to suboptimal behaviours is going to end up with a pretty swift reblock. I am very sympathetic to the number of very experienced editors above saying that this editor is a time sink and a net negative, and while I don't necessarily disagree based on what I've seen at their talk page and the evidence presented here, I think it's worth trying here one more time — armed with account and topic ban restrictions, and a pretty clear sentiment from a number of admins commenting (both on the support and oppose sides) that any issues upon resuming editing will be handled swiftly. ] (]) 22:31, 10 January 2025 (UTC) | |||
*'''Support, but''' only with IPA topic ban, 1-account restriction, no VPN use, and no IPBE. That should allow us to be able to detect recidivism and limit potential damage. — ] ] 22:55, 10 January 2025 (UTC) | |||
*'''Oppose''' per Black Kite, Tamzin, S Marshall, Girth Summit, and Ivanvector. ''']'''<span style="border:2px solid #073642;background:rgb(255,156,0);background:linear-gradient(90deg, rgba(255,156,0,1) 0%, rgba(147,0,255,1) 45%, rgba(4,123,134,1) 87%);">]</span> 23:04, 10 January 2025 (UTC) | |||
*'''Oppose''', agreeing with a number of editors above. I don't know if the two drafts, for Indian companies, would fall under ]. Unfortunately, the editor does not seem trustworthy. ]] 23:36, 10 January 2025 (UTC) | |||
*'''Support''' - At the end of the day, the ] has been followed by this user for a long time. Don't see anything wrong with providing one more chance. ] (]) 23:42, 10 January 2025 (UTC) | |||
*'''Oppose''' per comments of Blablubbs, Tamzin, etc. If they are unblocked, they should be under an India--Pakistan CTOP topic ban. --] (]) 00:07, 11 January 2025 (UTC) | |||
* '''Oppose'''. The CheckUser evidence of overt sock puppetry (not meat puppetry) is pretty strong, and the repeated denials, which seem to get walked back over time, make this user seem untrustworthy. ] (]) 00:28, 11 January 2025 (UTC) | |||
*'''Support''' - Noting the opposes above, AKG has nevertheless agreed with a topic ban inline with many of the opposes. It shows he is willing to minimize any possible concerns and that is a good sign. ] (]) 00:51, 11 January 2025 (UTC) | |||
*'''Oppose''' calling socking the sole issue is a red herring when there was disruption in addition, but the socking alone merited the block so they didn't need to be blocked for both. I think accepting the t-ban is more telling us what he thinks we want to hear, vs. awareness of why AKG shouldn't edit there. I do not think an unblock would be productive. ] ] 01:36, 11 January 2025 (UTC) | |||
{{abot}} | |||
== Import request == | |||
Is anyone else having issues with the notifications? | |||
{{atop | |||
I'm getting: | |||
| result = A list without citations or an indication that it meets ] is not going to be imported here. ] (]/]) 18:00, 12 January 2025 (UTC) | |||
}} | |||
Can you import, ] from simple Misplaced Pages. I created the page there.<span id="Cactusisme:1736493543617:WikipediaFTTCLNAdministrators'_noticeboard" class="FTTCmt"> — ] <sup>]</sup> <sup>]</sup> 07:19, 10 January 2025 (UTC)</span> | |||
<code>2024-10-25 05:06:40: Fatal exception of type "InvalidArgumentException"</code> | |||
:I suppose you mean , which you ''didn't'' create at all though, and which is completely unsuitable for enwiki as it stands, being unsourced and lacking all indication of notability. ] (]) 09:09, 10 January 2025 (UTC) | |||
::Well, they create the page. ]<sub>]<sub>]</sub></sub> (]/]) 15:18, 10 January 2025 (UTC) | |||
::], oh, okay<span id="Cactusisme:1736586978195:WikipediaFTTCLNAdministrators'_noticeboard" class="FTTCmt"> — ] <sup>]</sup> <sup>]</sup> 09:16, 11 January 2025 (UTC)</span> | |||
{{abot}} | |||
== Arbitration motion regarding coordinating arbitrators == | |||
when I try to go to ] and if I open the top notification window it just shows "no notifications"? ] (]) 05:09, 25 October 2024 (UTC) | |||
:Try ] if nobody here has an answer maybe :3 <b style="font-family:Monospace">-- ] (])</b> 06:31, 25 October 2024 (UTC) | |||
::Seems to have resolved itself overnight. Thanks. ] (]) 14:21, 25 October 2024 (UTC) | |||
The Arbitration Committee has resolved by ] that: | |||
== Deletion of my user account AKS.9955 == | |||
{{ivmbox|1= | |||
Dear Admin, I have been an active user of Misplaced Pages since past several years. I do not wish to continue being on this site, and owing to personal attacks and privacy concerns, I request that my user account be deleted / made indivisible (you decide best way). I wish you all the very best. Thanks and have a good day.''']]''' 05:26, 25 October 2024 (UTC) | |||
The ] are amended by adding the following section: | |||
<blockquote> | |||
; Coordinating arbitrators | |||
The Arbitration Committee shall, from time to time, designate one or more arbitrators to serve as the Committee's coordinating arbitrators. | |||
Coordinating arbitrators shall be responsible for assisting the Committee in the routine administration and organization of its mailing list and non-public work in a similar manner as the existing ] assist in the administration of the Committee's on-wiki work. | |||
:Courtesy link to ]. Sincerely, <s>James Bond</s> ] (]) 05:31, 25 October 2024 (UTC) | |||
::Also, if any administrators reading this wish to read the thread and make a decision concerning ARK.9955's autopatrolled and NPR rights, that would be most appreciated. But for a TL;DR version - AKS.9955 has had a financial stake in the airlines ] and ], created those articles, and failed to disclose that they had a COI regarding them during creation/deletion discussions. The sourcing in the TezJet article is likely poor enough for autopatrolled to be pulled on that basis alone (the article is cited almost entirely to Planespotter's and the company(AKS.9955)'s own website.) Glancing through their reveals a host of similarly-sourced articles, such as ], ], ]. Which isn't the end of the world- and AKS.9955, this doesn't need to be the end of your time on Misplaced Pages. You're clearly passionate about the project - you just need to be whole lot more forthcoming when it comes to declaring when you have a connection to an article subject, and you can't when they bring that up. | |||
::For the sake of anybody watching, the some of the personal attacks I'm referring to can be read below: | |||
:::{{tq|All these '''James Bonds''' getting a high after pointing out a ''COI'' I think Misplaced Pages has reached a point where it is no longer possible to contribute constructively without some sore losers sitting in their basements and preaching the world how things work.}} (emphasis original) | |||
:: ] (]) 19:29, 25 October 2024 (UTC) | |||
:See ]. It is not possible to have an account deleted and ''vanish'' is only partially effective. ] (]) 05:47, 25 October 2024 (UTC) | |||
::Also, courtesy vanishing would be clearly rejected in this case because this user is being scrutinized for sanctions. <span style="font-family:'forte'">] <b>(])</b></span> 07:25, 25 October 2024 (UTC) | |||
*I've removed all advanced rights/tools. See log for details. ] - ] 00:16, 26 October 2024 (UTC) | |||
::I have no issue if they want to ], although they need to point to the two discussions when doing so, so the Steward may make a determination as to the fitness. I don't see any other sanction that is likely. My removal of rights wasn't a sanction as much as it was because he wants to vanish, combined with the fact that they don't seem to have the skills to use the tools properly. As for avoiding scrutiny, that would be more of an issue if they come back. Some may see it differently, but ultimately, it is up to the Steward (or Global Renamer, per policy) to decide. ] - ] 07:11, 28 October 2024 (UTC) | |||
The specific responsibilities of coordinating arbitrators shall include: | |||
== 24.43.82.89 == | |||
* Acknowledging the receipt of correspondence and assigning tracking identifiers to pending requests and other matters; | |||
* Tracking the status of pending matters and providing regular updates and reminders on the status of the Committee's off-wiki work to arbitrators; | |||
* Reminding members of the Committee to vote or otherwise take action in pending matters; | |||
* Organizing related correspondence into case files; and | |||
* Performing similar routine administrative and clerical functions. | |||
A coordinating arbitrator may, but is not required to, state an intention to abstain on some or all matters before the Committee without being listed as an "inactive" arbitrator. | |||
This user has made many unconstructive edits, which seem very immature. I'm going to presume that they're a school IP, but either way, they should get hit with a ban hammer ] (]) 09:38, 25 October 2024 (UTC) | |||
</blockquote> | |||
:See also the edit filter. Blocked for a week. Thank you for reporting, ], but for another time, it's better to take such cases to ]. ] | ] 12:45, 25 October 2024 (UTC). | |||
}} | |||
For the Arbitration Committee, ] ] 23:48, 10 January 2025 (UTC) | |||
== Disruptive editor via multiple ip addresses (I think) == | |||
: Discuss this at: '''{{slink|Misplaced Pages talk:Arbitration Committee/Noticeboard|Arbitration motion regarding coordinating arbitrators}}'''<!-- ] (]) 23:49, 10 January 2025 (UTC) --><!--Template:hes--> | |||
== Backlog == | |||
For the last few days I’ve had to deal with an anonymous user, possibly the same person across multiple ip addresses. Here’s the most recent ip address: ]. Here are the other ip addresses that I suspect are the same person: ], ]. | |||
] <span style="display:inline-flex;rotate:-15deg;color:darkblue">''']'''</span><span style="display:inline-flex;rotate:15deg;color:darkblue">]</span> 19:38, 11 January 2025 (UTC) | |||
This user keeps making repeated disruptive edits on the same pages, plus similar disruptive edit on other pages. | |||
== Requesting review of SPI == | |||
I’m hoping that something can be done about this user and their disruptive editing. ] (]) 19:03, 25 October 2024 (UTC) | |||
{{Atop|No need to have brought this here.--] (]) 23:15, 11 January 2025 (UTC)}} | |||
I recently filed an ]; any admin/checkuser eyes would be appreciated. Thank you! ] (] • ]) 22:43, 11 January 2025 (UTC) | |||
:The chances that this is the same user are very high. All IPs come from a small town in Poland. Block them. Full support from me ] (]) 21:32, 25 October 2024 (UTC) | |||
:CUs and SPI clerks are very aware of which SPIs need attention. Please trust that we will get to the one you posted. Asking for input at AN isn't very helpful unless your SPI is much more urgent than usual. ] (]) 23:09, 11 January 2025 (UTC) | |||
:The anonymous user, under the ip address ], is still making disruptive edits. ] (]) 19:06, 26 October 2024 (UTC) | |||
{{Abot}} | |||
::The anonymous user, under the ip address ], is still making disruptive edits despite having a huge warning against them. ] (]) 20:00, 28 October 2024 (UTC) | |||
:Diffs of their being a pest, please. Not everyone is going to dig through the entire contribs history of multiple IPs. The easier you make a mop’s job, the more likely one swings the banhammer. ] ] ] 12:13, 27 October 2024 (UTC) | |||
== IPBE for AWB account == | |||
== Query re possible clean start for a blocked user who hasn't edited in 14 years == | |||
{{atop|status=Done|1=Done. - ] <sub>]</sub> 05:02, 12 January 2025 (UTC)}} | |||
Hi. I'm performing a task using {{user|CanonNiAWB}}, but the edits aren't editing since I'm using a VPN. I already have IP block exemptions on this account, so could it also be granted to that? Thanks. <span style="white-space:nowrap"><span style="font-family:monospace">'''<nowiki>''']<nowiki>]]'''</nowiki>'''</span> (] • ])</span> 02:32, 12 January 2025 (UTC) | |||
:Done. ] (]) 02:40, 12 January 2025 (UTC) | |||
::Thanks. <span style="white-space:nowrap"><span style="font-family:monospace">'''<nowiki>''']<nowiki>]]'''</nowiki>'''</span> (] • ])</span> 02:46, 12 January 2025 (UTC) | |||
{{abot}} | |||
== Content removal, POV pushing, edit warring == | |||
Hi admins and friends, once again, I don't know if this is the best forum for this question so redirect me if it isn't. I came across a {{tnull|helpme}} request from @] who wanted to appeal a block on his old account @], which he can't log in to because he's lost the password and email address. Given that the block was imposed 14 years ago and he apparently hasn't tried to edit in the interim, would he be a candidate for a ]? If so, would it be enough to declare this on both user pages? Or does the 14-year-old block prevent a clean start? ''']''' <small>(''she/her'' · ] · ] · ])</small> 23:44, 25 October 2024 (UTC) | |||
{{atop | |||
| result = Please use ] rather than creating new ones. ] ] 15:14, 12 January 2025 (UTC) | |||
}} | |||
@] removing content and POV pushing here and is currently edit warring ] (]) 10:52, 12 January 2025 (UTC) | |||
:{{nacmt}} Well, technically it wouldn't be a clean start because those don't apply to people who have active sanctions (including blocks), but this is a fairly normal place for an unblock request, and if they were literally only blocked because of one day of vandalism 14 years ago I wouldn't expect there would be any issue with one. ] (] • ]) 00:58, 26 October 2024 (UTC) | |||
: |
:This looks like the same complaint as ]. Let's centralise discussion there. I note that ] is also empty. ] (]) 11:19, 12 January 2025 (UTC) | ||
{{abot}} | |||
::: That would be sock puppetry. ] (]) 01:22, 26 October 2024 (UTC) | |||
:I can only speak as one member of the community, but I have no issue whatsoever with this user participating with the new account, and I certainly don't think TheAmazingCoffeeMan should be forced to jump through too many hoops simply for trying to do this properly instead of quietly editing. If we have to ] this, then I suppose they can just post a quick unblock request wherever an admin sees fit? ] (]) 01:38, 26 October 2024 (UTC) | |||
::I tend to agree, although it would've been better if they'd just not said anything about the old account, it looks a fairly ruitine block and would likely merit a ] unblock, which I will just go aherad and do so as to put the matter to rest. ] ] 02:04, 26 October 2024 (UTC) | |||
:::I will, as I do every time one of these threads pops up, plug my user essay ]. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 02:07, 26 October 2024 (UTC) | |||
::::Nice.I appreciate an essay that is blunt and honest about the sausage factory. ] ] 03:00, 26 October 2024 (UTC) | |||
::::Just thinking out loud, Taz, is it worth linking ] in second bullet point {{tq|If there is a history of sockpuppetry, it is not particularly extensive or disruptive}}? Excessive SPIs on the same menace tend to equal LTAs, in my experience, but hey, you’ve been Misplaced Pages-ing a lot more than I have, so I can be wrong. ] ] ] 12:11, 27 October 2024 (UTC) | |||
:::::I think that would narrow my meaning more than I intend. There's lots of socking that falls short of LTA but would definitely disqualify someone from the benefits of this unwritten rule. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 16:04, 27 October 2024 (UTC) | |||
===More input?=== | |||
*It was brought up on ] that when this user filed an unblock request, they admitted to a few other socks, and one of them was blocked as a sock of a long-gone vandal with a large sockfarm. It's a fair concern and I asked TheAmazingCoffeeMan to address it. Here is their response: | |||
{{tq|I looked through the sock puppet investigations archive for Alexcas11, and I read some about the editing patterns of the sock puppet accounts alongside the IP addresses used, and I can say those accounts (besides RoyalRumble24) don't belong to me. I also looked at the IP addresses used, and I can safely say none of them track to my location (I live in the United States, but that's as specific as I'll get). Moreover, the account Alexcas11 and its sock puppets appear to have been active and subsequently blocked before I even started vandalizing Misplaced Pages and got blocked for it. Additionally, the way I went about vandalizing articles mostly involved falsifying dates, and the only article about a made-up topic I ever created was an imagined 2011 remake of Home Alone. All the other articles deemed inappropriate for inclusion I wrote as RoyalRumble24 were about people deemed ineligible for Misplaced Pages's notability criteria.}} | |||
:I would take this as a "no" to the question of if they were the person operating the account, and it is still my inclination to just ] and see what happens, but thought I'd run it by this board in case others feel differently. ] ] 05:36, 29 October 2024 (UTC) | |||
:: If there are no other issues, I'd go for it. --] 12:24, 29 October 2024 (UTC) | |||
== Tulsi (unblock request) == | |||
== CheckUser and conflict of interest VRT consultations, October 2024 == | |||
{{atop green|User unblocked. ] 12:25, 16 January 2025 (UTC)}} | |||
* {{userlinks|Tulsi}} | |||
* Blocked (indef) on 3 April 2024 (9 months ago) by ] during an AN thread (]) for undisclosed paid editing | |||
* Subsequent unblock request was also considered at AN before being declined (]) | |||
Tulsi has now submitted an unblock request which I am copying: | |||
The Arbitration Committee has received applications for ] and ] access and has reviewed them in consultation with the ]. The Community is invited to evaluate the candidacies and comment at ] and ] until the end of 1 November 2024 (UTC). | |||
{{talk quote block|Dear Sysops, | |||
On behalf of the Committee, ] (]) 02:57, 26 October 2024 (UTC) | |||
: Discuss this at: '''{{slink|Misplaced Pages talk:Arbitration Committee/Noticeboard|CheckUser and conflict of interest VRT consultations, October 2024}}'''<!-- ] (]) 02:57, 26 October 2024 (UTC) --><!--Template:hes--> | |||
I sincerely apologize for my past actions, which were problematic and deceptive. I fully understand the concerns raised, and I deeply regret my involvement. On April 3, 2024, my account was blocked by Rosguill in relation to undisclosed paid editing associated with the {{section link|Misplaced Pages:Administrators' noticeboard/Archive361|DIVINE and Tulsi: COI/UPE/quid-pro-quo editing, association with threats and harassment}}. However, I want to clarify that my involvement in these matters was minimal, with only minor interactions in the past. I have never written articles for payment, and I do not support paid editing. | |||
== Administrator recall policy adopted == | |||
The issues in question occurred ], prior to the block. At that time, I admitted my conflict of interest (COI) and disclosed it on the relevant article talk pages. Following discussions, my global and local rights were removed, but the block was not enforced until two years later. Many of the articles in question were deleted, so I did not find it necessary to disclose anything further. Moving forward, I have no intention of creating or editing COI-related articles. However, if I am ever in a situation where I am required to contribute to such an article, I will ensure full disclosure on the article talk page and submit it for review, as I did with the article ]. | |||
After ], ] is now a policy. The procedure is as adopted by the ]. Some questions remain, which may be discussed at the policy's talk page. <b style="font-family:Monospace">-- ] (])</b> 16:03, 26 October 2024 (UTC) | |||
While I respect Rosguill’s decision to impose a block after the two-year gap, I understand that a block serves to prevent disruption rather than punish. I have learned valuable lessons from this experience, and my contributions over the past two years reflect this growth. In this time, I have created , all without any undisclosed paid editing or COI involvement. Additionally, I have contributed to patrolling, as seen in the ] and ]s, and I have reported several violations on WP:UAA. | |||
:Thank you for your well-reasoned and diplomatic close of this discussion. ] (]/]) 16:15, 26 October 2024 (UTC) | |||
::This is a surprise to me. How many attempts to do this over the years have failed? This will take some mental readjustment. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 08:14, 27 October 2024 (UTC) | |||
:::I had no idea this was going on either, as I don't remember seeing any notices. On paper, it looks interesting, but I haven't examined it close enough to have an opinion yet. ] - ] 08:17, 27 October 2024 (UTC) | |||
::::{{tq| I had no idea this was going on either,}} Ditto. Where was this promoted? ] ] ] 10:52, 27 October 2024 (UTC) | |||
:::::It was borne out of one of many proposals at ]. I don't think there was any mention of "recall" on ] until after the conclusion of RFA2024 Phase I, by which point it had ''already been decided'' that the community wanted a recall process. The Phase II discussion (to hash out specifics) treated the Phase I consensus as immutable – wrongly, in my view, given my point about T:CD. The drive to create WP:AR should have been spun out of RFA2024 at the first stage and linked separately to get broader input, given the far-reaching potential of this process. Had that happened, the Phase I and II consensuses might have been very different. That RFA2024 has succeeded in producing a desysopping-style policy where other attempts failed is due to the fact that the Phase I recall proposal was a ] and inadequately publicised. ] (]) 11:52, 27 October 2024 (UTC) | |||
::::::I echo the sentiments above - this should have been ''much'' more widely advertised. ]] 11:54, 27 October 2024 (UTC) | |||
::::The whole RfA 2024 review process, including this aspect of it, was notified to virtually all noticeboards, T:CENT, watchpage notices, discussed in ''The Signpost'', etc. If you missed that there was a discussion about reforming the RfA process and adopting recall, it's not because there was a lack of notice. ] (]/]) 13:24, 27 October 2024 (UTC) | |||
:::::The above would suggest otherwise. ]] 13:28, 27 October 2024 (UTC) | |||
::::::Copying @]'s list ] that was just closed:{{pb}}{{tq2|1=Regarding notifications about the second phase of discussion: a was posted, the , and a ] (there was also a link present in the ]). A was sent to what I believe is a .}}{{pb}}Unless by lack of notice you mean that a courier didn't personally deliver a letter to you informing you of these discussions, I'm not sure how much more notice was needed. ] (]/]) 13:33, 27 October 2024 (UTC) | |||
:::::{{outdent|1}} Also, this very RfC that was just closed was at the very least ]. So it's frankly flat-out untrue that none of these discussions were advertised. ] (]/]) 13:38, 27 October 2024 (UTC) | |||
::::::I don't see anyone claiming that "none of these discussions were advertised". What I see, based on the links, is that there was no centralized notification ''specifically about'' the new AR process until Phase I of WP:RFA2024 was over and it had already been decided there would be such a process. It seems no one realised its implications during Phase I and acted to make them clear to the wider community. AR is ''big'' – right next door to a ] process, and arguably the biggest change to administrator policy since ] was introduced. The proposal for a whole new policy shouldn't have been packaged in a round of RFA reform ideas, because that will have limited the Phase I discussion to regular RFA reformers and WT:RFA commentators. So in terms of procedure and notifications, there were mistakes. ] (]) 16:53, 27 October 2024 (UTC) | |||
:::::Well, that's tricky. The RFA 2024 review process was sprawling, with many discussions over many months. People have a limited amount of time to follow all of that. I was aware that such discussions were taking place. I was not aware that there was a specific policy proposal to adopt recall, though in general I'm not opposed to the idea. Whether the policy actually enjoys ] will be determined the first time it's used. ] ] 15:37, 27 October 2024 (UTC) | |||
::::::It does have consensus, with the phase 2 RFC and then this recent RFC confirmed it. Both pretty well advertised and attended. ] (]) 15:59, 27 October 2024 (UTC) | |||
::::I came across this very messy RfC by accident when it was almost over. Only 25 EC names on a petition are needed to force an admin to jump through hoops and they don't have to give reasons. There is no provision for anyone to object to the petition (even if the admin did none of things they are charged with). In particular, the admin cannot formally respond to the petition. So: write some polemic about an admin you don't like and advertise it in a few places. Some of the 25 names will come from people who have been sanctioned by the admin and didn't like it, and the rest from people who never heard of the admin before but are disturbed by the allegations. Then the admin has to go through an onerous re-admission process. <!-- Template:Unsigned --><small class="autosigned">— Preceding ] comment added by ] (] • ]) 13:29, 27 October 2024 (UTC)</small> | |||
:::::There is nothing prohibiting an admin from responding. ] (]/]) 13:36, 27 October 2024 (UTC) | |||
:::::I've been aware of this proposal from the beginning, but chose not to participate in the second phase. While I am a bit uneasy about some of the details, I think we need to see how it goes. If the process is used abusively, or turns out to be disruptive for the community, we can take steps to fix it. ] 14:43, 27 October 2024 (UTC) | |||
::::::I agree with Donald. We might learn from early uses of the procedure that changes are required, and that's fine. Being a policy does not mean it's set in stone. ] | ] 15:49, 27 October 2024 (UTC) | |||
:::::::This is more or less my thinking as well, if it does turn out to be a vector for abuse I am confident that the community will address that. ] (]) 18:55, 28 October 2024 (UTC) | |||
:::::::I'm for the process, even as I expect it to fail ''in it's current form''. It is open for abuse and I expect that we see petitions for all the usual suspects so disliked by sockpuppets, LTAs, and POV pushers. But what they will show is how to reform the process. | |||
:::::::Some form of admin recall has been asked for for years, and each attempt to try and implement something has failed to even make it this far. There comes a point where you just implement something, anything, and see how to make it work as you go. -- <small>LCU</small> ''']''' <small>''«]» °]°''</small> 19:16, 28 October 2024 (UTC) | |||
::::: The very limited number of responses to the RfC does appear to suggest it was poorly advertised. Unless I'm missing something, one place it doesn't appear to have been properly advertised is, ironically, here (it does appear as a single line in the Admin Newsletter, but that's easy to miss) which one would have expected to be the ''first'' place for notification. ] 15:21, 27 October 2024 (UTC) | |||
:::::Zero0000, I agree. Also, if the first attempt at a petition fails, not to worry – the filer just needs to wait six months, then try again. And all it takes to start a petition, leaving Admin X or Y in limbo for the next 30-40 days, is one person deciding that Admin X or Y "has lost the trust of the community". ] (]) 17:06, 27 October 2024 (UTC) | |||
I acknowledge that I was not fully familiar with Misplaced Pages's policies in the past, but I have since taken the time to understand them better. I have been an active and committed user since October 2014, with significant contributions across various Wikimedia projects. I have also served as a sysop on Wikimedia Commons, Meta-Wiki, MediaWiki, and the Maithili and Nepali Wikipedias. | |||
:Will be interesting to see how it pans out. ] (]) 15:31, 27 October 2024 (UTC) | |||
*I continue to be surprised 1) that this RFDA-in-all-but-name process originated from attempts to reform '''''RFA''''', the exact opposite; and 2) why a lot people seem to regard this new process as no big deal. It's a well of negativity that makes Misplaced Pages as a whole an even more negative place. I pity whichever sysop has to run the gauntlet first, because the specifics at WP:AR look pretty shaky to me. ] (]) 16:53, 27 October 2024 (UTC) | |||
::Well, that didn't take long... ] (]) 20:48, 27 October 2024 (UTC) | |||
*I would like to humbly advise any editors with concerns about the suitability of the process through which this policy was adopted to refer to the RfC linked in my first post, which was dedicated to that matter. It resulted in a consensus that the process was sufficient and no further ratification step is required. <b style="font-family:Monospace">-- ] (])</b> 17:15, 27 October 2024 (UTC) | |||
I am requesting an unblock because I am fully committed to abiding by all the established policies moving forward, and I am eager to contribute here in a constructive manner. Please kindly allow me a second chance. | |||
:A petition has been started (see ]). Any minor issues that arise will hopefully be resolved through the course of the next month. To those claiming it didn't have enough advertisement, I'll reiterate what's been said above: the third RFC was posted on CENT and sought to address that question. ] 18:59, 27 October 2024 (UTC) | |||
* How did this policy sneak into effect with something like 25 votes? That's ridiculous. ] (]) 03:06, 28 October 2024 (UTC) | |||
Thank you for your consideration. I humbly request your reconsideration and the restoration of the editing privileges on my account on English Misplaced Pages. | |||
A look at the example ] shows how we are doing so far. There are 5 "signatures" in favor of recall, some accompanied by to-and-fro with other editors. There are also 15–16 editors (hard to count) who oppose the recall. However, under this policy '''opposition to the recall doesn't count at all''', so those 15–16 editors are wasting their finger muscles. I'm wondering what other formal decision processes we have on Misplaced Pages for which only opinions in one direction are considered significant. ]<sup><small>]</small></sup> 04:40, 28 October 2024 (UTC) | |||
* I think it would have been better to do administrator recall as a trial period, with an expiration date of some kind. This is how some of the other big changes in WP:RFA2024 were handled, such as administrator elections and 2 days of no voting at RFA. {{pb}} Also, wasn't the goal of RFA2024 to make everything related to adminship less toxic so we could attract more admins? Making admins go through 30 days of drama for incidents that are too minor for arbcom doesn't seem like a great way to reduce toxicity... –] <small>(])</small> 08:35, 28 October 2024 (UTC) | |||
*:<p>IMO it's complicated. I think it's well recognised especially by non-admins is that one reason why RfA is such a problem is because adminship is generally a wikilife-long thing with it very very hard for admins to lose the tools. And it's also historically been basically impossible to even sanction an admin the way an ordinary editor would be. While there's some aspect of ] involved, the nature of adminship has generally meant admins are protected from any real sanction until and unless they lose their tools. </p><p>So while admins are supposed to demonstrate a higher level of commitment to our policies and guidelines and be less likely to make personal attacks, edit war etc; and many do, there's been a feeling that some don't and yet have never really been properly challenged over it in part because they are admins. I.E. they're getting away with stuff it's really unlikely a regular editor would get away with. And when it comes to questionable use of the tools, it has to be extremely egregious for anything to happen although an ordinary editor similar misusing something (whether tools or just general editing) would long ago have been stopped from doing that. </p><p>Things have changed a bit in recent years with arbcom seeming to be more willing to take cases and perhaps more willing to remove the tools, and even just more willing to take cases has meant some it's been easier to lose the tools since admins have either formally resigned them or effectively done so by leaving Misplaced Pages rather than participate in the case. Also there's at least one high profile case where an admin was cbanned without regard for the tools. </p><p>Still I think many of us plebs still regard admins as having a special level of protection that normal editors don't and therefore we treat RfAs as a much bigger deal than they arguably need to be. I.E. Yes adminship might just be a few tools, but you pretty much get to get keep those tools unless you misuse them very very badly, and you also get to do stuff few other editors would even putting aside the tools. </p><p>So while making it easier to remove admins does have the unfortunate effect of "increasing toxicity" when we have these recalls, there's a hope it will make adminship less of a big deal and make RfAs less toxic since we don't have to be so worried about the consequences of making a wrong decision. Whether it will be better or worse in the long run with recalls, I don't know. Note I say this as someone who can I think count on one hand or at least two hands the number of RfAs they've participated in but who did support recalls in the first RfC. </p><p>] (]) 09:32, 28 October 2024 (UTC)</p> | |||
*::P.S. In fairness, I will also acknowledge that admins generally also have to put up with abuse that isn't so accepted when directed at us plebs. ] (]) 09:35, 28 October 2024 (UTC) | |||
*<p>As someone who IIRC supported recalls in the first RfC and didn't participate in the second or drafting of the rules and didn't really participate in the final one I do feel that this has been way messier than it should have been. In particular, whatever was said in the first and second, I'm unconvinced it was ever wise to treat this as a policy that could go into effect without a final confirmation RfC especially without a formal trial period. I always expected there would be a final confirmation RfC with a specific developed policy in place. </p><p>And I don't feel the final RfC was really that since at least at the beginning the details still weren't quite sorted and it wasn't even really worded as "This is our policy on recalls, should we go ahead with recalls with this specific policy? As always on Misplaced Pages changes are always possible, but this should be considered the policy which will be implemented if you support it." or something along those lines. Instead it was IMO fairly unclear that the final RfC was even going to be a final RfC or IMO even what the third RfC was hoping to establish. </p><p>For further clarity, I was aware of that final RfC but I didn't participate in part because I felt it a mess. I expected even with that RfC we'd still have to end up with yet another confirmation RfC once the tinkering finished, and I expressed concern that it was therefore a waste of time early on (to the editor who started it). I did watch it slightly and was aware it seemed to be developing into a final RfC before it closed but I still didn't participate in part because I didn't care but also because I was still unsure if it would really be the final RfC given the messy start and low participation. I can't help thinking there were others who read about it and saw how messy it was at the start and thought, we'll we're never going to get a consensus for recalls from this so not worth my time. I'll wait until the final RfC when everything is clear. </p><p>I'm not saying the closer was wrong, but I do think the whole process was way messier than it should have been and this is probably part of why we're we are now without editors surprised we actually have a policy for recalls now in place. </p><p>And I have to say, it's unclear to me if this is even definitely resolved. The first recall, the admin doesn't seem to be challenging the process. But what happens if an admin does especially when the first recall petition succeeds? Have the bureaucrats even said they will remove adminship since they accept that there has been clear consensus for this? <small>I do think those supporting the first recall have done the process no favours either but that's more of an aside.</small> </p><p>] (]) 09:27, 28 October 2024 (UTC)</p> | |||
*:In my opinion, there's just a lot of hiccups coming from way too many sources that have made this process messy. In an ideal world, I'd like the third RFC on Village Pump amended to my wording choice too. But unlike the ideal world, Misplaced Pages often has "Everyone wants this discussion but nobody wants to start it" happening. While it was not my preferred 3rd RFC, I respect Barkeep for starting the RFC when he did. And for better or worse, nobody else amended it or tried to establish a need for 4th RFC after that. | |||
*:A running theme I am noticing in a lot of this thread is people were personally not aware of this process. I don't think consensus can wait for everyone like that. That way, we keep relitigating things over and over in the name of ]. | |||
*:I completely agree that Recall should not be considered unchangably set in stone, and there's been more messiness during the process than any of us would like. I just also believe that the central idea still has value (even if many details differed from my preference). And I hope community members attempt to fix the process in whatever direction they prefer, instead of shuttering the entire process prematurely. ] (]) 12:03, 28 October 2024 (UTC) | |||
*::I think many people (myself included) were waiting for the talk page discussions to reach a settled proposed text before starting a clear and final "do you want this?" RfC, but this was cut off by BK's RfC. – ] <small>(])</small> 19:22, 28 October 2024 (UTC) | |||
*So as the person who closed the phase I discussion (that found consensus to develop ''some form'' of recall procedure) and followed everything since with increasing exasperation, I will just say that this is a shining example of how '''not''' to build consensus for a new process. The discussions were convoluted, bureaucratic and under-advertised at every step of the way. At no point was the community clearly asked "do you want to adopt <specific proposal> as a policy?" and yet, now we apparently have a new policy with a specific procedure. I hope we can draw a line under it and move forward with normal, open, consensus-based improvements to the new process. – ] <small>(])</small> 11:11, 28 October 2024 (UTC) | |||
*:Under advertised? They were on CENT, in the admin newsletter, at the pump, and on a watchlist notice. And the third RFC was the point at which the community was asked "so you want this as a policy." That third RFC was at the pump, on CENT, and in the admin newsletter. Can we not spread misinformation about "under-advertised"? What more advertisement could we possibly have done? Come on. ] (]) 14:15, 28 October 2024 (UTC) | |||
*::{{tq|And the third RFC was the point at which the community was asked "so you want this as a policy"}} – it should have been, but the question actually posed was not "do you want this as a policy?" but the utterly bizarre "is there already a consensus for this?". This is to my knowledge the first time we've ever used an RfC to (re)close another RfC and the result was predictably chaotic. Most people did not really understand what was being asked and those that did understandably didn't take time to read the sprawling preceding discussions to understand why the consensus was under question. And now somehow we have a "policy" out of this mess. That by the way is what I mean by under-advertised (not unadvertised): these discussions were mentioned, but the questions were posed in such a weird, orthogonal way that many people did not understand that the result would be a new administrator recall policy. – ] <small>(])</small> 18:13, 28 October 2024 (UTC) | |||
*::I don't think it's possible to make ''any'' major change to Misplaced Pages without people complaining that it was underadvertised. Fair enough to call the discussions convoluted and bureaucratic, but they certainly weren't ''hidden''. -- ] (]) 18:38, 28 October 2024 (UTC) | |||
*::{{tq|the third RFC was the point at which the community was asked "so you want this as a policy."}} Wasn't the third RFC a close challenge type RFC rather than a fresh polling of consensus? I thought it was a close challenge type RFC, so I did not participate in it. I feel like in a close challenge type RFC I am supposed to read the old RFC and make a judgment about whether the closer got it right or not, and there is no opportunity to inject my own opinion about the issues at hand. The exact third RFC question was {{tq|Is there consensus to have administrator recall based on the consensus reached during Misplaced Pages:Requests for adminship/2024 review?}} –] <small>(])</small> 18:52, 28 October 2024 (UTC) | |||
*:::Closer here. The way I viewed it was neither as a "do we want this" RfC or a close challenge RfC, but a "do we need another RfC" RfC. Personally, I would not be surprised if, after choosing to not participate in a "do we need another RfC" RfC in favour of waiting for the next RfC, the noes prevail and we don't have another RfC. RfC RfC RfC RfC RfC. <b style="font-family:Monospace">-- ] (])</b> 18:56, 28 October 2024 (UTC) | |||
*::::<p>FWIW as someone who views the third/final RfC in a, I think, similar way to Novem Linguae I can accept that by not participating in the RfC I risked the outcome being what it was and so it's not something I can really complain about although I do feel it's fine to comment on how I feel the process has been a mess. </p><p>My view is undoubtedly affected by the fact I did and do support a recall process so that was also part of the reason I didn't care. Also I had read it again perhaps a week or two before closing so I did recognise that despite my misgivings, it was looking like this could be interpreted as a final RfC resulting in implementation. (I did see the suggestion by the Barkeep it could be closed, but I felt it had been too long for it to be a good idea especially with the level of support.) So I can understand why those for which neither of these apply might be much more unsettled by what happened with the third/final RfC. </p><p>One thing I didn't maybe make clear in my lengthy above statement. My initial and main concern was that we'd actually get a non consensus or even consensus against and then opponents will say well that's it let's end this no point going further, and supporters would say that's not fair the RfC was partly based on an incomplete still be worked on draft. </p><p>While this wasn't what happened part of my concerns IMO still plays out but in a different way. Given how messy this has been, there is a risky it's all going to just fall through and recall will be destined to be something that became 'tried that, never again'. Or alternatively as a I highlighted above, when an admin recalled actually opposes the process it's all going to break apart and either end up at arbcom or with some nasty mess if they aren't de-admined due to uncertainty by bureaucrats. </p><p>However you can also say I'm part of the problem, I supported recalls in the first RfC but didn't care enough to actual helped draft a procedure or anything like that. And while part of the reason is because I don't care that much, I recognise that if we don't have a good procedure it's more likely to fall apart because others especially potentially affected admins will care. </p><p>] (]) 11:50, 29 October 2024 (UTC)</p> | |||
* I'm thinking about proposing some changes in light of what's going down at Graham's petition. First of all, 30 days is just way too long. Should be shortened to 10, maybe 7 or 14 days. Second, maybe there should be some 'crat ability to implement a SNOW close for especially spurious petitions. Anyone have thoughts on that? Probably going to propose those at the village pump later today. ] (] • she/her) 15:19, 28 October 2024 (UTC) | |||
**There is a related thread at ]. ~~ ] (]) 15:22, 28 October 2024 (UTC) | |||
**:If it's going to be retained - and at this early stage I see no benefit to it at all - then it needs to work significantly better. ]] 19:12, 28 October 2024 (UTC) | |||
Sincerely, | |||
== Need help to open page with contentious name *igger rock - historic cemetery in Quebec == | |||
] ] 14:39, 10 January 2025 (UTC)}} | |||
Having had discussions with the blocking admin, we would like to seek community comments on the unblock request. | |||
Hello, I have been directed here after trying to create an article with horrible name, but is necessary to use as this is what the place is referred to as. The current populations are rewriting the history of this place. It needs to be entered into Misplaced Pages to protect many people's research and work and also chronicle the Black lives lived here as well as hold space for the 300 free Black ppl that were dispersed and disappeared: | |||
Tulsi was blocked after UPE allegations that had been outstanding for around 2 years essentially caught up with them. They have now attested to having never edited for pay, which was the question they originally failed to answer twice (], ]), leading to the block. In the unblock request, they give a sincere undertaking not to engage in any more UPE. | |||
https://www.lapresse.ca/actualites/201610/01/01-5026419-la-reconnaissance-de-nigger-rock-comme-site-historique-demandee.php | |||
They have created several dozen articles about Nepalese politicians but these seem to be innocuous. I have identified only a handful of articles where Tulsi could have edited for pay. Given the amount of other contributions Tulsi has made, it would be appropriate to give the benefit of the doubt. ] 15:14, 12 January 2025 (UTC) | |||
thank you | |||
*I cannot find the link for "A related meta-wiki discussion". <span>]]</span> 15:35, 12 January 2025 (UTC) | |||
**I've deleted those words. I had decided not to include them in my post, but accidentally left them in. For interest, the discussion was this one: ]. ] 15:38, 12 January 2025 (UTC) | |||
*'''Support''' per ]. I will AGF that Tulsi will keep his promise not to engage in any COI editing going forward. ] (]/]) 16:07, 12 January 2025 (UTC) | |||
* '''Question''': We are all volunteers here, so the applicant's comment {{tq|if I am ever in a situation where I am '''required''' to contribute to such an article}} (emphasis mine) is worrisome within the context of UPE/COI. Could they, or someone else for that matter, provide some clarification? ] (]) 19:57, 12 January 2025 (UTC) | |||
*: I assume "required" is just poor phrasing and refers to circumstances similar to ] provided in the same sentence you quote. In any event, the second part of the sentence states {{tq|<em>I will ensure full disclosure on the article talk page and submit it for review</em>}} (emphasis added). That promise is enough for me. ] (]/]) 21:00, 12 January 2025 (UTC) | |||
*'''Support''', we should generally give a second chance to users who have greatly and fundamentally changed in several months. Given that the user acknowledged the block and promised not to engage in undisclosed paid editing, not to mention that the user is trusted elsewhere, I see no reason to oppose. ] (]) 20:48, 12 January 2025 (UTC) | |||
*'''Support''' I believe in their ability to address any concern in the future, given that they served as a sysop on Wikimedia Commons, Meta-Wiki, MediaWiki, and the Maithili and Nepali Wikipedias. ] (]) 21:44, 12 January 2025 (UTC) | |||
:'''Support''' A second chance promises that Tulsi will not do highly undisclosed paid editing. I may partially support a topic ban on Nepalese politics against Tulsi. ] (]) 05:56, 13 January 2025 (UTC) | |||
*'''Support''' Make the most of the second chance ] (]) 23:05, 14 January 2025 (UTC) | |||
*'''Support''' I had already been kind of watcxhing the discussion on their talk page over the last few days, and agree with an SO unblock. ] ] 23:34, 14 January 2025 (UTC) | |||
{{abot}} | |||
== ] == | |||
] (]) 17:49, 26 October 2024 (UTC) | |||
{{atop|1=Snow in the forecast. - ] <sub>]</sub> 22:08, 13 January 2025 (UTC)}} | |||
I can't believe this article's AfD is still up and not closed as a ] keep. The nominator has acknowledged his mistake out of ignorance. He was in middle school when the subject first became notable, and never heard of him. If the media, or God forbid, Social Media, discovers this nomination, it will do great harm to the reputation of the Misplaced Pages community as being collectively ignorant or ''much, much worse''. I used to be an administrator, and would have closed this as keep. Please do something! ] (]) 16:22, 13 January 2025 (UTC) | |||
:Anybody can close an AfD as SNOW keep. That's the whole point of SNOW. ] (]/]) 16:25, 13 January 2025 (UTC) | |||
== Problem moving a page == | |||
::Snowed by me. — ] ] 16:35, 13 January 2025 (UTC) | |||
:::Thank you!!! ] (]) 16:38, 13 January 2025 (UTC) | |||
{{abot}} | |||
== Request for Administrator Review of Repeatedly Declined Draft: Ario Nahavandi == | |||
Hello, I would like to request moving the page ] to it’s official name Danapur Cantonment. Due to system restrictions I am unable to do it myself. ] (]) 06:35, 27 October 2024 (UTC) | |||
{{atop|1=]. - ] <sub>]</sub> 03:25, 15 January 2025 (UTC)}} | |||
Dear Administrators, | |||
I am writing to request your assistance regarding my draft, ], which has been repeatedly declined over the past year despite my adherence to Misplaced Pages’s guidelines. | |||
:] would be the right venue for this. ] (]) 06:42, 27 October 2024 (UTC) | |||
::I moved it. Seems like there is a history of it moving from Danapur to Dinapur, though. Might warrant a full RM? ''''']''''' <sup>(] / ])</sup> 10:11, 27 October 2024 (UTC) | |||
Over the course of several months, I have worked diligently to gather reliable, published, and independent sources, including magazine articles and other credible publications, that meet Misplaced Pages’s notability criteria. My most recent submission was declined in less than an hour—a timeframe that strongly suggests it was not even reviewed carefully or thoroughly. | |||
== Vile racism allowed to remain for 12 hours == | |||
This is particularly frustrating as I see numerous approved articles on Misplaced Pages that cite sources far less reliable or even completely broken. In contrast, my article contains verifiable references that adhere strictly to Misplaced Pages’s policies. This inconsistency feels unfair and raises concerns about bias in the review process. | |||
racism allowed to remain in place for 12 hours. Suggest revdel. ] (]) 13:20, 27 October 2024 (UTC) | |||
I have followed all guidelines in good faith and cannot accept decisions that appear to be based on personal opinion rather than policy. It feels as though my article is being subjected to an unjust standard, especially when compared to articles that seem to bypass scrutiny. I genuinely wonder if this process is influenced by factors beyond content quality, as I have no means to “pay” for an article to be published, unlike some others. | |||
:{{done}} - any future instances can be requested via ], to avoid links of offensive material being inadvertently seen more widely. ]] 13:30, 27 October 2024 (UTC) | |||
::Thanks, yes I did want to make the point though how concerning it is that such material remained in place for 12 hours. Surprised as well it wasn't picked up by an edit filter or tagged as potential vandalism. ] (]) 13:56, 27 October 2024 (UTC) | |||
:::It's always going to be difficult for an automated tool to pick up stuff like that when the article already contains racism, slurs and other fruity language. That is, it's easy to pick up but hard to distinguish everything else. That's why we have humans. Thanks for your vigilance. -- ] <sup>]</sup> 14:54, 27 October 2024 (UTC) | |||
I kindly request that an administrator reviews my draft with impartiality and provides clear, actionable feedback. Otherwise, I am truly exhausted by the repeated rejections and dismissals with no valid reasoning. | |||
== An accusation that I'm not quite sure what to do about == | |||
To provide context, here are some of the sources I included: | |||
{{userlinks|2001:B07:6461:80A1:E15F:7BB3:50B5:FA8}} | |||
• https://www.nationaldiversityawards.co.uk/awards-2024/nominations/ario-nahavandi/ | |||
Hello. This is my first time posting to these boards, so I hope I'm doing it properly. I considered putting this at ], but it didn't seem like it fit the descriptor of {{tq|'''urgent''' incident or '''chronic, intractable''' behavioral problem}}. | |||
• Taurus Magazine (2024-11-19). "Ario Nahavandi". Taurus Magazine. 88: 7 – via www.magcloud.com | |||
So, about a week ago, ] a lengthy comment at ], questioning how the information specifically concerning post-2017 events was being presented. I would then ] | |||
• 6x Magazine (2024-11-22). "Ario Nahavandi; The Persian Icon". 6X Magazine. 432: 6–7 – via www.magcloud.com | |||
Some time later, the IP linked above left ]. Now I'm not quite sure of the context they're referring to, and so I'm not sure exactly who they lobbed this accusation at, but I originally interpreted it, as I don't think is unreasonable to do, as directed towards me. I gave them the benefit of the doubt, and so asked them, both ] as well as ], to clarify. | |||
Thank you for your time and consideration xx | |||
Given they ''didn't'' clarify, I think it's a very inappropriate comment to leave. However, since it's technically not necessarily directed towards me, I'm not sure if I can cite NPA or the like. So that's why I'd like to ask administrators' opinions on this, and whether their comment should be struck (since, after a full week, they have not done so themselves). I wouldn't normally care this much about personal attacks, real or hypothetical, but an implication such as the one they left there is a serious one, and I will not tolerate it when it is baselessly targeted at me. | |||
] (]) 23:47, 14 January 2025 (UTC) | |||
:Welcome to the admin noticeboards. I've proper-removed it from the history. -- ] <sup>]</sup> 16:54, 27 October 2024 (UTC) | |||
::Thank you, much appreciated! ] (]) 17:49, 27 October 2024 (UTC) | |||
:Administrators cannot override draft declines, and in fact the administrator toolset ]. —] ] <sup><small>] ]</small></sup> 23:51, 14 January 2025 (UTC) | |||
== My involvement with ARBPIA == | |||
::So who can I turn to for help? If administrators cannot assist in overriding the draft declines, to whom can I escalate this issue? I am deeply concerned that my article has been repeatedly declined without proper consideration of the sources I’ve provided. These sources are reliable, published, and fully comply with Misplaced Pages’s guidelines, yet they continue to be dismissed without even being properly reviewed. | |||
::It’s becoming clear that the rejection process isn’t being carried out fairly. I can’t help but feel that my article is being judged based on factors other than content quality, especially when I see articles approved with far less solid references. | |||
::I understand that the review process is based on policy, but when it seems clear that my draft isn’t being given the attention it deserves, I need to know where I can seek help to ensure fairness. | |||
::I kindly ask for your guidance—if administrators cannot intervene, who can I turn to for proper support in getting this article reviewed fairly? | |||
::Thank you for your time. ] (]) 00:08, 15 January 2025 (UTC) | |||
:::]. This is where you appeal problems with submissions of drafts. You should read the ] and ] carefully. ] (]) 00:20, 15 January 2025 (UTC) | |||
:::{{ping|Lanak20}} I actually ]. They're all malformed at best and unusable at worst. ] —] ] <sup><small>] ]</small></sup> 00:20, 15 January 2025 (UTC) | |||
*I've blocked the OP as a spam-advertising-only account. I should add that it's pretty obvious they've used other accounts to promote this person, I believe most recently as of last October.--] (]) 00:25, 15 January 2025 (UTC) | |||
{{abot}} | |||
== Your Friendly Neighborhood Sociologist Edit Restriction Appeal == | |||
{{u|Nableezy}} recently ] that I not close any more discussions relating to the Arab-Israeli conflict, broadly construed, citing my engagement with the content. The only example he provided was my starting ], although I'm sure we can both think of a handful of others. (I know I've participated in one other discussion involving Al-Jazeera's reliability, made ] to ], and made a handful of prose edits to ]; I've probably made a few other edits in the area, but I don't remember any.) I don't think this constitutes a reasonable basis to assert involvement with the whole topic area and said as much; Nableezy responded simply that he would raise the issue here (or somewhere similar) when I next close a discussion in the area. I'd rather not have that threat hanging over my head, so I'll ask for wider community input now. <span style="white-space: nowrap;">—] <sup>(]·])</sup></span> 17:43, 27 October 2024 (UTC) | |||
{{atop green|Unanimous consent after 36 hours to lift the restriction. ] (]) 14:25, 16 January 2025 (UTC)}} | |||
A bit over a year ago, with near unanimous support, I appealed a TBAN from GENSEX - receiving in its place the following sanctions {{tq|1RR restriction in both the GENSEX and AMPOL topics; is limited to 0RR on articles for organizations/activists who are affiliated with anti-transgender activism or gender-critical feminism, broadly construed; and has a PBAN from Kellie-Jay Keen-Minshull.}} Previous discussions are linked there. I am now requesting that my restrictions be dropped entirely because I have grown considerably as an editor, both since my initial TBAN when I'd just turned 19 and since the appeal. | |||
I translated ] (having originally wrote it on eswiki during my TBAN) and made it my first GA. I uploaded multiple colorized photographs of transgender historical figures to commons I improved ] and wrote articles for famous trans activists ] and ]. I also cleared up serious BLP violations at ] and rewrote the article. I also helped expand ] and wrote ]. I improved ] and ]. I improved ]. I rewrote and considerably expanded ] as well as ]. I expanded the article on the ]. I wrote the article on the 1970 semi-governmental report '']''. I expanded the articles on ] and ]. I rewrote ] to follow ] and use systematic reviews instead of primary studies. '''Most proudly''', I wrote ] and took it to GA - this is particularly relevant as a key part of the original TBAN discussion was whether my commitment to removing misinformation from Misplaced Pages was a case of either ] or following ] and ]. | |||
:Have to say I am not impressed about that thread at RSN. Nor was I terribly enthused about your deciding to open yourself, . | |||
:There are plenty of discussions elsewhere, perhaps best to pass on the AI related ones. ] (]) 17:51, 27 October 2024 (UTC) | |||
:I'm not generally a big fan of broadly construing involvement across entire topic areas, at least for RfC closers. ] itself speaks of disputes and not of topic areas. I'm also generally of the opinion that closures should be evaluated on their merits and not factors concerning the closer's person. As long as you don't close discussions on <em>questions</em> on which you have commented before, I don't think there is a problem. Otherwise, we'd be disqualifying closers for some unreasonably vague feeling they may be biased more than anything else. Speaking from experience, I've closed a few PIA RfCs with no complaints so far, even though looking at my user page it should not be difficult to infer what general opinions I hold on that topic. <b style="font-family:Monospace">-- ] (])</b> 17:56, 27 October 2024 (UTC) | |||
:It’s not a threat, but until it’s an issue I don’t plan on engaging in this here. But if there are future closes by an involved editor I’ll try to demonstrate that their closes have historically shown a propensity for taking a certain consistent position in favor of one bias that aligns with the arguments they’ve made in content related discussions. ''']''' - 18:07, 27 October 2024 (UTC) | |||
::{{tq|taking a certain consistent position in favor of one bias that aligns with the arguments they’ve made in content related discussions}} – Is there any way to determine whether this applies that isn't just casting aspersions? ] (]) 18:49, 27 October 2024 (UTC) | |||
:::By going through the closes and the content related edits? That is a general statement about any involved editor, so I don’t know how that could possibly be "casting aspersions". ''']''' - 18:56, 27 October 2024 (UTC) | |||
::::This sounds like you're withholding evidence against Compassionate727 until such time that it suits you, while simultaneously attempting to pressure them into behaving how you'd like them to. Please just lay it out now like they've asked; how is Compassionate727 ]? ―<span style="background:#368ec9;border:solid 2px;border-radius:5px"> ''''']''''' </span> 19:47, 27 October 2024 (UTC) | |||
:::::Nableezy has indicated that they do not presently think there is an issue, and that they therefore prefer not to engage with this question. So why are you actively trying to stir up conflict? If you have input on Compassionate's query, by all means give it, but don't stir shit for the sake of shit-stirring. --] (]) 20:04, 27 October 2024 (UTC) | |||
:::::I saw what I felt like to be the latest example of Compassionate727 showing that they have both contributed to content, and have a position in that content, and to closing discussions in the topic. I have previously asked editors that I have varying feelings about, including ones I think highly of, to not close discussions in the topic area when I feel they have crossed the threshold into "editor". So I politely asked that they no longer close discussions. They declined. As there presently isn’t an issue, and I didn’t intend to spend my Sunday afternoon digging up the diffs from past closes and positions that I think disqualifies them from playing the closer role, that’s the end of it as far as I’m concerned. If and when there is an issue then I’ll spend that time. But right now I’m going back to the game I’d rather focus on. ]. ''']''' - 21:02, 27 October 2024 (UTC) | |||
:Editors closing discussions they haven't been involved in should be fine, it's difficult enough finding editors who will close RFCs. If an editor has made, or makes, bad closes that ''show'' their bias then it should be brought up here. But I'm against discouraging editors from making closes simply because they may have a bias, as there is no editor without bias. -- <small>LCU</small> ''']''' <small>''«]» °]°''</small> 20:58, 27 October 2024 (UTC) | |||
:agree with maddy and activelydisinterested that until more evidence shows up, we should not consider every editor automatically involved because they had some prior engagement with the topic. | |||
:also think we have ways to deal with bad closures anyways. ] (]) 22:39, 27 October 2024 (UTC) | |||
:: "Editors closing discussions they haven't been involved in should be fine" is much too weak and allows for easy abuse. At a minimum, it should be "Editors closing discussions unrelated to topics they have been involved in should be fine". ]<sup><small>]</small></sup> 02:46, 28 October 2024 (UTC) | |||
:::This presupposes that the close will be bad or biased, and that an editor with bias can never make a neutral close. -- <small>LCU</small> ''']''' <small>''«]» °]°''</small> 10:40, 28 October 2024 (UTC) | |||
:::: Correct, it presupposes that some things might happen that for sure will actually happen. Under your proposal, someone with a strong POV about an RfC could just refrain from participating and instead close it to their preference. This would subvert the whole idea of an RfC. ]<sup><small>]</small></sup> 11:25, 28 October 2024 (UTC) | |||
:::::It supposes that editors with a bias (all of them) would only ever make closes in favour of their biases. Past events do not back this up. There have absolutely been ''instances'' were editors sat out RFC and then closed them as per their preference, they were overturned using the pre-existing procedures for doing so. Acting in that way isn't just a bias or POV but deliberate and malicious. So you point is correct if you expect editors with a bias or POV to behave maliciously. -- <small>LCU</small> ''']''' <small>''«]» °]°''</small> 12:17, 28 October 2024 (UTC) | |||
:::::: Most bad closes are not overturned. In ] there are always lots of socks, off-wiki coordination, and other stuff going on. We can't stop it, but we can try to mitigate the damage by adopting policies that reduce it. One example is to have a strict policy on involvement, for both administrators and ordinary editors. ]<sup><small>]</small></sup> 12:52, 28 October 2024 (UTC) | |||
:::::::If closes are not overturned how are you judging that they are bad closes? ] is one way and ] is another. Assuming good faith, even from those we disagree with, is generally the best way. The idea that INVOLVED is as broad as you interpret it isn't universally accepted. If you have a proposal for definitely making it that broad you should make it. -- <small>LCU</small> ''']''' <small>''«]» °]°''</small> 12:59, 28 October 2024 (UTC) | |||
:::::::: Most socks are not detected and hardly any off-wiki coordination is suppressed. It's nothing to do with agreeing or disagreeing. If everybody behaved properly all the time, we wouldn't need rules. But they don't. You are also incorrect that editors with bias would only apply that bias to a close if they were being deliberately malicious. Bias doesn't work that way. People with bias believe they are being even-handed when they aren't. ]<sup><small>]</small></sup> 13:14, 28 October 2024 (UTC) | |||
:::::::::And the rules are what they are, if you have a proposal to change them you should make it. Separately as I said all editors have bias, the believe that bias alone would always make a close bad would therefore mean that no editor could make a close. -- <small>LCU</small> ''']''' <small>''«]» °]°''</small> 17:03, 28 October 2024 (UTC) | |||
::::::::FWIW, my view is that AGF is not generally the best way, it is generally the worst way, maybe one of Misplaced Pages's most counterproductive policies when applied to the PIA topic area. And the notion that "universally accepted" things will be optimal solutions for PIA is going to be wrong in most cases. I think starting ] should constitute a reasonable basis to assert involvement with the whole topic area. I think this is probably the kind of simple strictness that a test for 'involvement' in the topic area should have. In my view, efforts should be made to minimize or eliminate faith-based assumptions about anything or anyone in the topic area. Good or bad faith-based assumptions about any account that does anything in the topic are equally bad, especially when it comes to things that people are very bad at doing in an environment like PIA like modeling intent or trying to predict future behavior. Regardless, any system used in PIA, even a very strict involvement test, will be gamed by someone at some point. ] (]) 13:21, 28 October 2024 (UTC) | |||
:::::::::You can decide to not follow ] it is only a guideline, I think that is a mistake that only adds to mistrust of Misplaced Pages. -- <small>LCU</small> ''']''' <small>''«]» °]°''</small> 17:07, 28 October 2024 (UTC) | |||
:::::::::Can't disagree more with this anti-wiki sentiment. AGF is a key pillar. ''']'''<span style="border:2px solid #073642;background:rgb(255,156,0);background:linear-gradient(90deg, rgba(255,156,0,1) 0%, rgba(147,0,255,1) 45%, rgba(4,123,134,1) 87%);">]</span> 20:55, 28 October 2024 (UTC) | |||
:::::::::::Come on man, it's not an anti-wiki sentiment. It is a pro-wiki sentiment. It is an anti-overconfidence, pro-rationality sentiment. I already use an assume nothing approach because the error rate is lower than an assume something approach when interacting with actors in the topic area. It works fine, it reduces the chance of conflict with both familiar and unfamiliar accounts. It means I don't have to think about intent, pro-this or anti-that categorization or pay any attention to the biased voice in my brain feeding me disinformation and pattern matching nonsense. It keeps my eye on the ball, what people actually say and do, not what the stack of unreliable heuristics in my dopey primate brain make up to model a person. The fact is that there is already mistrust. Denying that is just silly and will result in errors. AGF is largely inauthentic theater in PIA, one more thing that is exploited and weaponized by partisan actors. I think AGF can work well and be useful when editors already have a lot of information about each other and become overconfident about their theory of mind abilities, after they have had many, many interactions, as a reminder that while you may think you know this person, and you think they are up to no good, you should think about the counterfactuals and consider that there is a decent chance that you are wrong because you are not as smart as you think. ] (]) 03:51, 29 October 2024 (UTC) | |||
::::::::::::That's not what AGF is. AGF is the idea that when you meet an unknown editor you should try to charitably interpret their actions to put them in the best light. It doesn't mean discard rationality or ignore evidence. It means that in the absence of evidence to the contrary, you should not jump to negative conclusions. I really shouldn't have to explain AGF to an editor with over 30k edits since 2007. {{Tq|AGF is largely inauthentic theater in PIA}} If true, explains a lot of the problem. ''']'''<span style="border:2px solid #073642;background:rgb(255,156,0);background:linear-gradient(90deg, rgba(255,156,0,1) 0%, rgba(147,0,255,1) 45%, rgba(4,123,134,1) 87%);">]</span> 04:02, 29 October 2024 (UTC) | |||
:::::::::::::This might be an example of overconfidence and the errors we make when modeling other people. Of course, I know what AGF says, including that its scope is not limited to unknown actors. And obviously as an editor with over 30k edits since 2007, I've had the opportunity to observe thousands of instances of the actual features and effects of rule as it is deployed in the field by editors and admins in a very diverse set of contexts. There is misalignment, as usual. I prefer an empirical approach when it comes to understanding what Misplaced Pages's rules mean to people and how they work in practice. The inauthentic theater feature is just one of several inauthenticity related features of the PIA system. Inauthentic civility is another (something I support by the way, not because I care about civility, but because it increases the signal to noise ratio of discussions). ] (]) 04:50, 29 October 2024 (UTC) | |||
::::::::::::::Signal to noise ratio of discussions is a good heuristic. But AGF is more than inauthentic theater. And yes, it's not limited to unknown actors, but there are limits of good faith. Ironically, the example you gave of modelling a person you know well is when I think it's hardest to AGF. If you already understand where someone is coming from it will heavily color your expectations because you do have a model of that person. You do also need to AGF someone you know, but there will necessarily be a conflict in situations of dispute with someone you already know or, especially, when you have people who have made mistakes known to you or disagreements that are on a low burn. Regardless, though, the purpose of AGF as a ceremonial aspect of communication is related to the concept of ] and there is a rational reason for this. Now, we don't have thoughtcrimes. You can privately suspect that every new motivated account that seems somewhat good at doing stuff is a sock even though you might rationally know that Misplaced Pages is a website used by thousands of people and is frequently visited by entirely new users. Just don't say it in public when you're forming that suspicion because it's a violation of good faith and once that cracks and we allow bad faith in, it poisons the discourse. You can still collect evidence and find a sock and maybe be right a lot of the time, or maybe the system isn't giving you good feedback about whether you are right or wrong. Still, AGF means you should default to assuming good faith at least in public because to do otherwise is insulting due to its insinuation of low expectation and making a negative conclusion about someone based on where they seem to be coming from before they've even done anything wrong. ''']'''<span style="border:2px solid #073642;background:rgb(255,156,0);background:linear-gradient(90deg, rgba(255,156,0,1) 0%, rgba(147,0,255,1) 45%, rgba(4,123,134,1) 87%);">]</span> 04:58, 29 October 2024 (UTC) | |||
*If small edits make an editor involved, we should follow that. If they don't, they don't. This standard has been unevenly applied. I previously accused someone of being involved based on small edits, and there was not a consensus that they were involved. I'm not sure what the precedent should be, but we should apply it consistently and not haphazardly. ''']'''<span style="border:2px solid #073642;background:rgb(255,156,0);background:linear-gradient(90deg, rgba(255,156,0,1) 0%, rgba(147,0,255,1) 45%, rgba(4,123,134,1) 87%);">]</span> 20:54, 28 October 2024 (UTC) | |||
I believe the restrictions impair my ability to edit productively. I generally edit with 1RR regardless of sanctions. With 0RR, as Red-tailed hawk noted at my previous appeal "they can wind up restricting the sorts of partial reverts that are often a healthy part of the ordinary editing process." With 0RR, I am unable to engage in the BRD cycle properly and always second-guessing whether a partial edit to a recent edit counts as a revert or not. It also prevents me reverting drive-by SPA/IP povpushing. I don't plan to ever edit KJK's article again, but I believe that my record of neutral constructive editing shows the PBAN is no longer preventative or necessary. In the highly unlikely event I ever see a reason to edit it in future, I know my edits would be subject to heightened scrutiny which I'd welcome. | |||
==An administrator recall petition for ] has been initiated== | |||
] There is currently a petition at ] for Graham87 to initiate a re-request for adminship (RRfA). If the petition reaches 25 supports from ] users, an RRfA is required for {{pronoun|Graham87|obj}} to maintain {{pronoun|Graham87|pos}} toolkit. For further information, please consult the ]. | |||
<!--Template: Admin recall notice/AN--> | |||
I request that anyone wanting to comment keeps discussion on the petition and its talk. ] 18:56, 27 October 2024 (UTC) | |||
:Noting that this petition has been withdrawn/closed. ] (]) 16:02, 28 October 2024 (UTC) | |||
::I've reopened, since there were more signatures than the OP. Besides, we need to let the procedure run, so we know if we need to fix it.--] 17:14, 28 October 2024 (UTC) | |||
:::As much as I dislike the ugliness going on there, and totally apreciate the OP trying to acknowledge the obvious, the close was out of process. | |||
:::There's clearly some issues with this process that need fixing, or at least clarification, I think we can all see that. The thirty-days-to-certify aspect in particular needs adressing, but also the fact that a petition to open a recall process was being treated like the process itself, and there's really nobody with any clear authority to address issues as they arise. ] ] 17:38, 28 October 2024 (UTC) | |||
:I do wonder if we should even have Discussion sections in these petitions. Since it just causes a lot of fighting and arguing. When the whole point of the petition is are there 25 established editors that indicate lack of confidence in the person as an admin. It's basically just a binary question in that regard. ]]<sup>]</sup> 17:42, 28 October 2024 (UTC) | |||
:After about a day, I have several takeaways about the recall process in general based on the discussion so far: | |||
:* There should be a process to snow close petitions. It's clear that barring some major bombshell, nothing will come of this one. Withdrawal was likely the correct response, but it's ]'d back into existence. | |||
:* Several people didn't comment on the actual issue at hand. Graham87 spent years blocking newbie accounts that had made only minor mistakes and frequently told them some variation of "you are not welcome here". This was written off as being kind of mean every once in a while. It seems several participants didn't bother to read the ANI discussions. | |||
:* A huge swelling of admins immediately came out to oppose. Almost all of the early opposition that built up inertia against the petition was from admins. I can't help but think there's a perverse incentive here from several admins who expect to see themselves at the other end of this. | |||
:* Some people used the petition as a place to express general displeasure with the process. Several people failed to participate in multiple widely advertised discussions and then took out their frustration with ] behavior. | |||
:* It would help if there were a baseline "arguments to avoid". A few examples: | |||
:** Appealing to due process implies that being an administrator is a right or an entitlement. Someone should only be an admin if they maintain the trust of the community, so arguments about whether it's fair to the admin aren't helpful. The admin serves the community, not the other way around. | |||
:** Since the point of recall is for long-term patterns where no individual problem rises to Arbcom, it's not reasonable to argue that "if this was serious it would be taken to Arbcom". | |||
:** Similarly, "this was discussed at ANI" should be a ''prerequisite'' to recall, not an argument against it. | |||
:] (]) 18:56, 28 October 2024 (UTC) | |||
* I was under the impression that RFA2024 was meant to make the admin process less toxic. It seems odd, then, that we've introduced a process that makes de-adminship ''more'' toxic. Some people don't seem to understand there's a human being on the other end of this shambles. ] 19:13, 28 October 2024 (UTC) | |||
* I'm completely confused on the whole process. What is it? People just have a place to voice support for the petition and others can provide feedback. What's the result supposed to be? A !vote if enough people sign on (like many petitions)? Are they de-admined immediately? Who decides? What's the threshold? Seems pretty vague to me. ] (]) 21:27, 28 October 2024 (UTC) | |||
*:] holds the answers to all of your questions. <b style="font-family:Monospace">-- ] (])</b> 21:29, 28 October 2024 (UTC) | |||
*::Actually, it doesn't. | |||
*::{{tq|A petition is closed after thirty days. If it gains at least twenty-five valid signatures within that period, the administrator is required to make a re-request for adminship or be a candidate in an administrator election.}} | |||
*::It doesn't state that the WPian is desysoped, it just says that they are required to make a re-request for adminship. If it fails, are they desysoped? While it's ongoing, do they retain the tools. It also doesn't define what the options are for an outcome. Can they just be suspended for a while? Etc. ] (]) 04:32, 29 October 2024 (UTC) | |||
*:::The page says that if they do not start the re-request for adminship within a reasonable timeframe, {{tq| may remove the administrator privileges at their discretion}}. Implicitly, then, the recalled admin retains the bit until either they choose not to RRfA or have their RRfA rejected. It also says that if the admin passes the RRfA they retain the bit; therefore if they do not pass they do not retain the bit. | |||
*:::Given the page says nothing about suspensions then no, this process does not allow for a suspension of the rights. ] (]) 12:56, 29 October 2024 (UTC) | |||
* Anyone interested in this process more generally should probably watchlist ]. ] ] 14:14, 29 October 2024 (UTC) | |||
I appreciate your consideration. My best regards, ] (]) 01:02, 15 January 2025 (UTC) | |||
== (possible, but not assured) Hoaxes == | |||
:'''Support.''' ] (]/]) 01:25, 15 January 2025 (UTC) | |||
{{atop | |||
:'''Support'''. Based on YFNS's activity since the original tban, I don't see any reason to believe that restrictions are necessary going forward. ] (]) 06:34, 15 January 2025 (UTC) | |||
:'''Support'''. Welcome back comrade. ] (]) 06:56, 15 January 2025 (UTC) | |||
}} | |||
:'''Support''' based on their editing activity between TBAN and last year, as well as between the sanctions and now. Good work, and a great example of how this restorative process is ''supposed'' to work. May you inspire other misguided people to a path of restoration. ] ] 08:27, 15 January 2025 (UTC) | |||
:'''Snow Support''' ] (]) 14:15, 15 January 2025 (UTC) | |||
At the risk of getting recalled, I've raised attention of this matter at ] (see: ]), however, this may benefit from someone with more experience addressing ]s than me. (I'm not even entirely certain these are hoaxes and want to tread carefully out of concern for making a new editor's first experience at WP an extremely negative one. However, I just get the gut sense this is one of those occasional attempts to make a demonstration about WP. More likely than not, I'm mistaken and have done a shoddy job at source verification.) Thanks, in advance. ] (]) 03:29, 28 October 2024 (UTC) | |||
: |
:'''Strong support'''. To me YNFS comes across as a very responsible editor and I believe these restrictions are no longer warranted. ] (]) 16:09, 15 January 2025 (UTC) | ||
:'''Support''' I remember the original ban happening due in large part to canvassing on twitter, the fact that any restrictions remained in place thereafter strikes me as a deep miscarriage of justice. ] (]) 23:26, 15 January 2025 (UTC) | |||
'''Query''' Does your reference to BRD mean that you undertake to follow it in the future? ] (]) 14:17, 15 January 2025 (UTC) | |||
:'''Enthusiastic support''' YFNS is a perfect model of an editor who is an asset to Misplaced Pages. ] (]) 15:17, 15 January 2025 (UTC) | |||
:'''Support''' A well worded appeal, worth giving another chance. — <b>]:<sup>]</sup></b> 18:20, 15 January 2025 (UTC) | |||
*'''Support''' This is a convincing and sincere appeal. ] (]) 00:22, 16 January 2025 (UTC) | |||
*'''Support''', Welcome. ~] ] <sup>「] / ]」</sup> 02:33, 16 January 2025 (UTC) | |||
*'''Support''' as they have convincingly demonstrated change. '']''<sup>]</sup> 02:53, 16 January 2025 (UTC) | |||
*'''Support''' I supported and still support the original restrictions, and the later now appealed restrictions. I think YFNS's case has shown that an editor can come back from the brink successfully and am happy that happened. ] (]) 04:00, 16 January 2025 (UTC) | |||
{{abot}} | {{abot}} | ||
== Copyvio Problem == | |||
== User Report: Niasoh - Repeated Vandalism and Harassment == | |||
Hey all, I believe that these three diff should be redacted as copy vio's, thanks. There are several sentences which are directly lifted from the sources. Some one more experienced should likely have a look through the revision I restored as well. I didn't spot anything, but I may have missed something. | |||
] (]) 22:35, 15 January 2025 (UTC) | |||
:To be clear, I don't think that @] is really at any fault here. | |||
:Right off the bat, I see that you have been ], breaking the ] on the first article you edited. Please read ] and understand what is and is not vandalism before you start throwing accusations around. ] 12:33, 28 October 2024 (UTC) | |||
: |
:] (]) 22:37, 15 January 2025 (UTC) | ||
::@] please see {{tl|copyvio-revdel}} on how to tag copyvios for attention. ] (]) 08:04, 16 January 2025 (UTC) | |||
::I went with DE, but yes all would apply. NoorBD is now '''INDEFfed'''. ] ] 17:50, 28 October 2024 (UTC) | |||
== CheckUser access for administrator election scrutineers == | |||
== Lardlegwarmers block appeal == | |||
The Arbitration Committee has been informed that, following a request from an English Misplaced Pages editor, Stewards {{user|Johannnes89}}, {{user|EPIC}}, and {{user|Yahya}} have ] to serve as scrutineers for the ] being held this month using SecurePoll. The Committee notes that SecurePoll election scrutineers often use local CheckUser permissions in order to fully perform their functions. | |||
{{atop | |||
| result = Essentially unanimous consensus to not unblock. ] ] 15:53, 17 January 2025 (UTC) | |||
}} | |||
* {{userlinks|Lardlegwarmers}} | |||
The Arbitration Committee has been unable to locate community discussions that establish consensus for appointing Stewards from outside the English Misplaced Pages to serve as CheckUsers for this purpose, which would bypass the Committee's ] for functionary appointments in ordinary circumstances. | |||
I blocked Lardlegwarmers yesterday for one week for a violation of ] from COVID-19. This was about ], although I subsequently noticed ] as well. LLW has asked me to copy their appeal here. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 03:00, 16 January 2025 (UTC) | |||
=== Statement from Lardlegwarmers === | |||
I have only been very active editing Misplaced Pages for about one month, even though my account is older. I was blocked for pushing a minority POV in the talk page for Covid-19 Lab Leak Theory, which I understand. For context, this issue wouldn't have even come up at ANI except that there was this very old account making borderline uncivil comments constantly, and I took them to ANI myself and it boomeranged. One thing that I learned from that experience is that Misplaced Pages's culture sort of revolves around social dynamics and politics, which can overshadow fairness and consistency in rule enforcement, and that I am probably not going to be the one to fix it.<ref>]</ref> Anyways, in my defense, I didn't learn until later that my attempt to reason things out like grownups was not allowed; my edits were in good faith and I was really just attempting to talk it out with the other editors who did not agree with me. But I understand that the norm in this space is to walk away if there isn't any uptake of my ideas or take it to dispute resolution instead of continuing to try to convince people. The current ban is for making a comment on an AE thread, not a Covid-19 article. I was on the page for a totally unrelated reason and noticed that a user I recognized from the Covid thread was being discussed. My comment was mostly about user behavior and reflecting on the underlying dispute itself, not Covid-19. Also, on my user page I quoted ] discussing his view on Misplaced Pages's approach to Covid-19 , which I'd assumed was permitted because it's my own user page and it's really a comment about the state of Misplaced Pages as a whole. The admin who blocked me, @], blanked it from my user page. If the community won't let me keep that quote on my user page, then fine, we'll leave it removed, but I wish they would have just asked me to remove it and described why instead of editing my user page. A block for this stuff seems harsh. Thanks. | |||
{{talk reflist}} | |||
=== Statement from Tamzin === | |||
Excerpting my comment on their talkpage:{{tq2|Usually we only warn someone on their first topic ban violation. However, in your case, the fact that both violations occurred within hours of the ban being imposed, and that they were belligerent rants treating Misplaced Pages as a battleground, made me judge that a short block would more clearly communicate just how far you are from what is considered acceptable conduct. Even if you didn't understand that the ban applied outside articles, you should have understood that the community found your editing about COVID disruptive, which should have been reason enough to not make those edits.}} <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 03:00, 16 January 2025 (UTC) | |||
=== Discussion among uninvolved editors === | |||
*This is clearly a topic ban violation - and it came less than a day after it was imposed. Even if assuming in good faith that they didn't know it was a topic ban violation, their unblock request shows not only that they don't understand what they did wrong, but they attempt to justify it with statements such as {{tq|Anyways, in my defense, I didn't learn until later that my attempt to reason things out like grownups was not allowed}} which is borderline a personal attack (veiled insult that others weren't being grownups); {{tq|which can overshadow fairness and consistency in rule enforcement}} which is confirming they still don't understand why they were topic banned nor why they were blocked for violating it; and quoting Larry Sanger's ] promoting comments on their userpage after their topic ban. To summarize, I have no confidence that the user understands what they did wrong, and I would go so far as to say the user attempting to skirt the edges of their topic ban and supporting another user trying to promote fringe theories on Misplaced Pages merits an indefinite community ban. TLDR: '''Oppose unblock''' and ultimately would support indefinite ban due to the flagrant violation, lack of understanding, and no belief that after the 7 days is up they will not go straight back to trying to ]. I won't be the one to propose that, however. -bɜ:ʳkənhɪmez | ] | ] 03:10, 16 January 2025 (UTC) | |||
*I don't see how an unblock is possible when Lardlegwarmers clearly still doesn't understand what a broadly construed topic ban means. To be clear, there's no need to ask the "community" whether you can keep your topic ban violation. The only hope for you to be able to obey it is if you are able to decide yourself, especially after you've been told by an admin. While we do try to educate instead of just blocking, the "community" isn't here to help you understand the limits of your topic ban. ] (]) 04:01, 16 January 2025 (UTC) | |||
*:Should clarify that despite what I said above, I'd weakly oppose extending the topic <del>ban</del> <ins>block</ins> to indefinite at this time. While I'm not hopeful Lardlegwarmers is going to be able to obey it given what they've said, I think it's fine to give them rope after the <del>ban</del> <ins>block</ins> expires and apply normal escalating blocks. Since we're already here, perhaps this will somehow help them understand that yes the community requires you to apply it broadly on anything to do with COVID-19 throughout Misplaced Pages. They should consider this very short rope though and notably the next time they feel they need to ask the community whether they're violating their topic ban when they are, it might be the last time. ] (]) 20:38, 16 January 2025 (UTC) | |||
*::Sorry mixed up ban and block above twice, now fixed. ] (]) 01:45, 17 January 2025 (UTC) | |||
*'''Oppose unblock''' as the user looks to have no intention of following Misplaced Pages guidelines with their request. It is only a week and will give a change to think about how to change. ] (]) 04:13, 16 January 2025 (UTC) | |||
*'''Oppose unblock'''. It truly takes some ] to cite a Signpost piece authored by the admin who blocked you to support the proposition that you're being railroaded. '''Weak support for an indef''' because that's what Lardlegwarmers seems to be speedrunning. ] (]/]) 04:30, 16 January 2025 (UTC) | |||
*'''Oppose unblock'''. The topic ban was on ''the topic of COVID-19, broadly construed'', not ''the topic of COVID-19 directly in articlespace''. And the topic ban was violated, not just within less than a day, but ''within three hours'' of it being imposed. On top of that the unblock request could be a case study for ]. I won't call for an indef ], but when the block expires Lardlegwarmers should bear in mind that any further violations of the topic ban will be their last. - ] <sub>]</sub> 10:10, 16 January 2025 (UTC) | |||
*'''No unblock''' - Basically per Lardlegwarmers: they don't appear to understand why they've been blocked. An indefinite block seems very likely in this editor's future and we certainly should consider cutting out the middle-man and just skipping to it, but I'd like to give them at least some chance here to understand why they were blocked. ] (]) 10:12, 16 January 2025 (UTC) | |||
* '''Oppose unblock''' - While I usually support giving editors ] to demonstrate improvement, this case warrants a longer wait. The user acknowledges pushing a minority POV and failing to disengage per ] norms, but their justification suggests a lack of understanding or acceptance of policies like ], ], and ]. Their off-topic comment in an AE thread, despite knowing the sensitivity of such spaces, and the policy-violating content on their user page, further reflect ongoing disruption. I recommend they take time to reflect and gain a better grasp of Misplaced Pages's collaborative culture before requesting an unblock again. ] • ] ⚽ 11:31, 16 January 2025 (UTC) | |||
* '''Oppose unblock'''. I agree that absent change from this user an indefinite block is likely. For their benefit, if you're the subject of a topic ban, broadly construed, about COVID-19, you need to be editing in an entirely different topic area. Think of something that you're interested in--television shows, football, English gardens, science fiction books? Take a week and think on it. ] ] 11:42, 16 January 2025 (UTC) | |||
*'''Oppose unblock.''' What is there left to say? This conduct feels like appellant's purpose is use Misplaced Pages as a battleground and to soapbox their views rather than to build the encyclopedia-- to remake Misplaced Pages as they think it should be. My feeling is that a week won't be nearly enough. The railroad comment is appallingly full of not understanding that their conduct is not acceptable in a collaborative project. ] (]) 12:28, 16 January 2025 (UTC) | |||
*:PS: What Tamzin said in her statement above. ] (]) 12:33, 16 January 2025 (UTC) | |||
*::Whilst I don't believe user will be able to change their approach, I feel an indef would be premature for now. We should give them a chance to mend their ways. ] (]) 12:44, 17 January 2025 (UTC) | |||
*An account that ] is topic banned, violates that topic ban immediately, and posts a ] unblock request that thoroughly ]. Whoever closes this should be considering indef, not an unblock. — <samp>] <sup style="font-size:80%;">]</sup></samp> \\ 13:57, 16 January 2025 (UTC) | |||
*:Indeed. ] (]) 14:55, 16 January 2025 (UTC) | |||
*'''Oppose unblock''' this specific response {{tq| Misplaced Pages's culture sort of revolves around social dynamics and politics, which can overshadow fairness and consistency in rule enforcement}} is indicative of their viewpoints and why they're not ready to contribute. They continue, {{tq|my attempt to reason things out like grownups was not allowed}}. These demonstrate that they still do not get it, and rather project their self-perspective is that they are actually a victim of people who are abusing the rules against them. . I proffer that this is going to be a consistent problem until they acknowledge that they were violating policy. Zero indication that they know how to positively contribute, just perhaps a vague inference that they'll avoid getting in trouble -- because -- we'll I'm not entirely sure they've communicated what they will do differently, but rather simply say that {{tq|a block for this stuff seems harsh.}} ] ] 15:12, 16 January 2025 (UTC) | |||
*:Notwithstanding the harsh situation I presented above, to be clear I '''oppose indef''' for now. A new user should have the opportunity to overcome early (while significant) setbacks, which is what TBANs are designed to encourage. I am encouraged by things like YFNS corrective behavior in a prior AN discussion, and can only be hopeful and AGF that might apply to LLW here. We need more passionate, subject matter experts, as contributors to this project, but they ''absolutely must contribute positively'' and following established PGs. ] ] 16:34, 16 January 2025 (UTC) | |||
*'''Oppose unblock''' and support an indef. I am pretty confident in saying that this is where we will be heading after this block ends. ] (]) 15:20, 16 January 2025 (UTC) | |||
*'''Oppose unblock''', clear violations of the topic ban. Don't oppose indef, but I'd like to at least give him the chance to figure out exactly what we expect going forward. --] 15:52, 16 January 2025 (UTC) | |||
*'''Support block, oppose unblock, oppose indef''' - this is a topic-banned newbie's first violation, in the heat of the moment after the restriction was imposed. Tamzin's block was the appropriate response. The unblock request is wholly inadequate, but jumping straight to indef for this sort of violation is a pretty extreme overreach. If they go back to violating their sanction after this block expires, ''then'' let's talk community ban, but they should be given the opportunity to edit constructively while respecting the restriction. ] (<sup>]</sup>/<sub>]</sub>) 16:07, 16 January 2025 (UTC) | |||
*'''Oppose unblock, oppose indef...however...''' I am sympathetic to their point of view and their general "right" (we don't really have rights here on WP) to post their opinion on a subject, even one as contentious as COVID-19. I think the blanking of the user page is a step too far. We shouldn't be in the business of deleting negative opinions about Misplaced Pages; while the statement was in reference to COVID-19, it doesn't mention it within the claim and is more a critique of Misplaced Pages at large and mass media than its relation to COVID. I would let the statement on their user page stand/restore it. Larry Sanger's statement is not a ], it is a reasonable ''opinion''. There were loads of statements/claims about COVID/its origin/mandates/treatment/vaccines that, despite their widespread implementations and presentation as "the science", later turned out to be misleading or untested conjecture (examples: no studies on masking effectiveness with a large population vs the coronavirus, 6 foot spacing, lying to the American public about wearing masks because health care professionals needed them more, lab leak theory, military connections to the Wuhan Institute, US funding of WI, etc). '''HOWEVER''', civil discourse ''is'' essential. That means that discussions about COVID were fraught with battlegrounds and bludgeoning. As such, we have additional restrictions for COVID discussions and other contentious topics and LLW needs to follow them. LLW did not do so and has shown a consistent flaunting of these restrictions and a weeklong block is a reasonable start. In summary, the quote isn't unreasonable to leave on their user page (give them that latitude), but a weeklong block for the other behavior should stand. ] (]) 16:15, 16 January 2025 (UTC) | |||
*:They added two comments to their userpage. Both were critical of Misplaced Pages. One was also critical of ] and other aspects of the US government's COVID response. I removed the latter. It doesn't matter whether Sanger's opinion is fringe or not; what matters is that he was talking about COVID. I would be quite the hypocrite to remove something from someone's userpage just for criticizing Misplaced Pages, as I have a fair bit of that on my own userpage. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 17:02, 16 January 2025 (UTC) | |||
*::There's some pretty big overlap there in criticism of Fauci and how it is handled on Misplaced Pages. Again, I don't feel THAT is a significant violation of COVID editing restrictions (beyond the fact that they did it despite such an editing restriction). Anyone can completely skip over it if they wish. {{ping|Tamzin}} playing devil's advocate for a moment, what if I published the same thing on my user page? Would it be ok? Would it be ok if I posted it on LLW's user page (as long as LLW was ok with it, of course)? I realize we're getting in the weeds of a "what-if..." but if so, what's the substantive difference between me putting it on a user page and LLW doing the same? ] (]) 17:19, 16 January 2025 (UTC) | |||
*:::If you posted it to your userpage, it would be fine (although not that constructive), because you are not topic-banned from COVID. If you posted it to their userpage, that would be ] for a banned editor, since I'd struggle to believe you have an independent reason to think that particular quote belongs on that particular page. {{PB}} If you really want to fight the removal from the userpage, feel free to create a subsection here, but I stand by the removal. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 17:29, 16 January 2025 (UTC) | |||
*::::I'm not fighting the removal per se. Just wondering where the boundaries are and if it's wise to have such a boundary. ] (]) 17:55, 16 January 2025 (UTC) | |||
*:::::The boundary is ]. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 19:17, 16 January 2025 (UTC) | |||
*:::Buffs: In the ''realm of hypothetical'' I would presume that if that quote had been on LLW user page for a long time, in a sea of content, pre-existing AN, then it ''might even still be up today.'' However, on the other hand, to post that after the TBAN was imposed is nothing other than what can be seen as ''abject defiance'' to the ban. But beyond that, it simply violates plain language of the ban, as it applies to {{tq|all pages (not only articles) broadly related to the topic}}, so I proffer that Tamzin is clearly in the right here. To your charged statement about ''if you were to post the same thing'' to your user page, prior to your statement here and presuming you were not under a TBAN, it would ''not be questioned'' one iota. However, as a response to this discussion, it could be construed (but not technically violating) the principles of ] and I would caution against it. Moreover, you reinstating it on LLW talk page would be a far closer in the proximity of violating PROXYING. ] ] 18:49, 16 January 2025 (UTC) | |||
*::::The fact that the comment only came after the topic ban is key here. I'm fairly sure I've seen several cases where there's something on an editor's user page which is covered by a topic ban but which no one has said or done anything about because it was there from before the topic ban. In fact I'm fairly sure I even remember a case where someone asked specifically if they could modify or remove something on their user page which related to their talk page which was technically under the topic ban (probably gensex). I think this was allowed especially since it related to their personal life rather than some comment on something, although they were told just this once is best. There might have even been a case where an editor wanted to do some more editing or formatting of something under their topic ban and was either denied or told only this once. IIRC, there was also an editor who was happy to be able to finally change someone on their userpage covered by their topic ban once it was lifted. A topic ban is a topic ban. I'd note that if someone makes an extremely constructive edit to an article that is not covered by ] we still treat this as a topic ban violation, although it's something much more beneficial for the project than an editor being able to repost random ramblings about Misplaced Pages they want to share. ] (]) 20:31, 16 January 2025 (UTC) | |||
*'''Oppose unblock, oppose indef''' - The topic ban violation was clear cut. Let's hope Lardlegwarmers will read a bit about how to avoid topic ban violations, or else indef block is not too far for them. ] (]) 16:19, 16 January 2025 (UTC) | |||
*'''Oppose unblock, extend block indefinitely''' - Lardle should try to demonstrate good behavior on another wiki for six months before asking for a SO. Let's hope that this user should handle contentious topics carefully in the future. ] (]) 18:35, 16 January 2025 (UTC) | |||
*'''Oppose unblock''' but no reason to indef, a block has already been imposed. If the user continues to violate the TBAN, than a longer block might be warranted. ''']]''' 02:43, 17 January 2025 (UTC) | |||
=== Comments from involved editors === | |||
Nonetheless, the Committee has decided to appoint the three Steward volunteers as English Misplaced Pages CheckUsers for the duration of the election in order to facilitate the election process. In future cases, the Committee will request a showing of affirmative community consensus for selecting scrutineers from among Stewards outside the English Misplaced Pages before granting such access outside of the ordinary procedure. | |||
* Going to open a new subsection here since I've made comments to ] two weeks ago. I wish I could say I was surprised that this ended in tears but that would be untrue (though I did have some hopes the comment a month ago indicating they were aware pro-fringe POV-pushing was sactionable was a signal they were intending to modify their behaviour). As bɜ:ʳkənhɪmez points out, making thinly veiled attacks is not exactly the type of thing looked favourably upon in an unblock request. Nor is making polemical statements on one's user page, whether within the scope of the ban or not, likely to convince the community of one's inclination and ability to ]. Lardlegwarmers, if you do really want to return to editing, especially if you want to appeal your topic ban in 6 months or a year, I would strongly advise reading ] and following the advice there, especially ]. Complaining about Hob's conduct won't help you here, because the block (and it's a rather short one) and ban are about you, not Hob. Given your comment that {{tq|apparently two wrongs make a right}}, I had hoped that you were already also considering your own behaviour, but I would like to make it very clear: taking the role of one of the "wrongs" to address someone else's "borderline uncivil" behaviour is ]. Whether Hob crosses the line is on them, but what you do is entirely on you. ] (] • ]) 07:16, 16 January 2025 (UTC) | |||
* As I was involved in the discussion to topic ban LLW I think I count as an involved editor. With that said I would discourage an early lifting of this block, which seems appropriate considering that LLW's response to the topic ban was to immediately violate the topic ban. ] (]) 13:54, 16 January 2025 (UTC) | |||
*:Also, perhaps LLW wasn't aware of this, but people who aren't uninvolved administrators aren't generally supposed to put comments into the "results" section of an AE filing. ] (]) 13:57, 16 January 2025 (UTC) | |||
* I was there.. Three thousand ye-- No. More like one, two days ago. I seriously believe Lard Leg Warmers is one of two situations: '''1:''' ] and unable to understand the concepts of medical science as if they were a Facebook mother invested in "essential oils" and "holistic medicine" rather than trusting medical and scientific experts; '''2:''' ] and simply f<s>**</s>king with us for no good reason and leading us around, and around, and around, and around, and around the bend because they get a rise out of it. Either way, my advice: don't get led around the bend, '''advise indef block''' for either ] or ]. <span style="text-shadow: #E9967A 0em 0em 1em;">]]</span> 16:38, 16 January 2025 (UTC) | |||
::], those kinds of personal assumptions about their character are unnecessary to this discussion. Instead of speculation on who they are elsewhere, let's just focus on their behavior on Misplaced Pages. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 06:45, 17 January 2025 (UTC) | |||
*Lardlegwarmers' statement clearly shows that they have learned little from the sanction. They should demonstrate such before there is any lifting. ] (]) 18:55, 16 January 2025 (UTC) | |||
{{abot}} | |||
== Usage of 'Notable people' vis-a-vis 'Notable person' in section headers == | |||
Accordingly, the Arbitration Committee grants temporary English Misplaced Pages CheckUser permissions to Stewards Johannnes89, EPIC, and Yahya, solely for the purpose of their acting as scrutineers in the ongoing administrator elections. | |||
{{atop | |||
| result = This is not an administrative issue. ] (]/]) 20:56, 16 January 2025 (UTC) | |||
}} | |||
In the course of editing numerous articles, I have come across the header featuring 'notable people' when there is only one person and have therefore modified the grammar. | |||
For the Arbitration Committee, ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 14:57, 28 October 2024 (UTC) | |||
: Discuss this at: '''{{slink|Misplaced Pages talk:Arbitration Committee/Noticeboard|CheckUser access for administrator election scrutineers}}'''<!-- ] (]) 14:57, 28 October 2024 (UTC) --><!--Template:hes--> | |||
I recently had another editor come behind me and revert one such edit on the grounds that things have always been done this way, regardless of the number of notables for a given locale, which makes little sense to me. Is this really policy? ] (]) 16:45, 16 January 2025 (UTC) | |||
== Is WP:RECALL a policy? == | |||
:This seems like a question for ], not ] as it doesn't involve administrator actions. AN isn't a general Help forum for questions about editing. You could even try asking at ] or the Help Desk. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 19:00, 16 January 2025 (UTC) | |||
{{abot}} | |||
== Reporting Administrator Abuse == | |||
In her otherwise decent close of ], {{u|Maddy from Celeste}} specified that {{tq|Misplaced Pages:Administrator recall shall be marked as a policy}} and then . The problem is that the RfC did not ask if the page should be upgraded to a policy nor did anyone in the discussion subsequently propose it, making this aspect of the close a ]. This perhaps happened because Maddy mistook the discussion for a change to an existing policy ({{tq|On the English Misplaced Pages, there are no formal requirements for policy '''changes''' this RfC is a valid way of figuring out where we want to set the threshold for this particular policy '''amendment'''}}) and/or, as they acknowledged when I ], because they forgot that we have an ]. Nevertheless Maddy has said that {{tq|given the significant developments these last two days, do not feel comfortable making any unilateral changes at this point}}. | |||
{{Atop|I'm going to do the OP a favor and close this with no action against them. Essentially, the OP's misbehavior was pointed out by Acalamari and the OP is trying to present it as Acalamri's misbehavior. If another administrator thinks sanctions against the OP are warranted, that's up to them.--] (]) 23:56, 16 January 2025 (UTC)}} | |||
] is abusing his moderator powers in order to post unconstructive comments on talk pages, specifically when we were talking about if we should delete the US 2028 election or not, he said "that Drumpf supporters want there to be no more elections so they can remain in power forever doesn't mean we adhere to their delusions by deleting articles here". This is clearly unconstructive, and treating the talk page as a forum. I didn't know he was a moderator when I was removing his comment, and now he left all of these messages on my page and is saying I'm the real vandal here. ] (]) 22:48, 16 January 2025 (UTC) | |||
So as a partial challenge of that close, I'm asking: is ] a policy page? – ] <small>(])</small> 19:14, 28 October 2024 (UTC) | |||
:You are misrepresenting what I wrote. I refer to my comments ]. <b style="font-family:Monospace">-- ] (])</b> 19:20, 28 October 2024 (UTC) | |||
::<small>Ah, the third (for now) active discussion about RECALL live at AN - shows that it's totally not a controversial idea at all! ]] 19:23, 28 October 2024 (UTC) </small> | |||
:::<small>I am currently running a pool on when RECALL will be brought to ArbCom. Squares are filling up fast. Contact me for information on how to bet, and how to send me the money for safekeeping in the mean time. ] (]) 19:29, 28 October 2024 (UTC) </small> | |||
*Per ], "Policies have wide acceptance among editors". It seems clear to me that this is not the case with this recall process. <small><span style="border:1px solid black;padding:1px;">]</span></small> 19:40, 28 October 2024 (UTC) | |||
*There's probably no one who argued more strongly than me against making this trainwreck into a policy. But Maddy correctly read the consensus as saying that this should be adopted and put into effect (and not simply as a trial). So if the community has reached a consensus to put something into effect, that can lead to a desysop, I cannot see how that would be anything other than a policy. If other editors are just now waking up to the fact that they should have joined me in speaking up earlier, well, it's too late now. At some point, we will have to have an RfC to revoke this policy, but for the time being, it's a policy. --] (]) 20:00, 28 October 2024 (UTC) | |||
*:{{tq|This should be adopted and put into effect}} – I agree with that, it's the "policy" designation that seems unwarranted, given the lack of an explicit proposal to adopt it as one. I want to avoid on the one hand watering down the definition of a policy as those guidelines and processes which have the highest level of consensus on the project (because come on, this is clearly not that!) and on the other making it harder to improve the current process through normal editing and consensus-building. Pretty much everyone seems to agree that this process needs amendment, but usually the way to make non-trivial amendments to a policy is through an RfC, and pretty much everyone also agrees that we don't want more RfCs on this... – ] <small>(])</small> 20:06, 28 October 2024 (UTC) | |||
*::I see that distinction as wikilawyering. --] (]) 20:10, 28 October 2024 (UTC) | |||
*:::We would have done if we had been aware of it! (see previous section re:lack of notice). ]] 20:42, 28 October 2024 (UTC) | |||
*::::Yeah, that's an issue. But the people who pushed this through insisted that they did everything required in order to publicize the discussions, and they have a point. --] (]) 20:48, 28 October 2024 (UTC) | |||
*Does it matter if it's a policy vs. a procedure? Is RFA a policy? ~~ ] (]) 20:07, 28 October 2024 (UTC) | |||
*:Yes, in practice it's considerably harder to change a page tagged as a policy; and nope. – ] <small>(])</small> 20:33, 28 October 2024 (UTC) | |||
*As a process (or policy) it's far from ready, as the Graham87 petition and all the various discussions around the project-space are showing. It's not a case of ironing out small details; the very fundamentals are being questioned and challenged. More workshopping is needed. WP:AR should be returned to draft policy status and discussion centralised on its talk page. ] (]) 20:11, 28 October 2024 (UTC) | |||
*:What parts are far from ready? What aspects of admin recall that haven't already been discussed during phases I and II of the RfA 2024 discussion and subsequently still need to be hashed out? ] (]/]) 21:24, 28 October 2024 (UTC) | |||
*::Well, within the last 48 hours alone, questions posed on WT:AR have included timing of petition closures, the structure of the petition page and naming of its sections, the maximum runtime for petitions, early closure rules (or lack thereof), and the applicability of ] (now at WP:VPP). Valid, key questions. I think a large part of why they're being asked now is because up until now, no one had much idea of how the policy/process would actually work in practice. As currently presented, the content of WP:AR feels scant, hardly a solid foundation for launching petitions. And the attempted early close and subsequent re-opening of the Graham87 petition further damage the process's credibility. ] (]) 22:42, 28 October 2024 (UTC) | |||
*"]". This policy/procedure does not have that level of support, as has been evident over the past 48 hours. Per SuperMarioMan above, this policy/procedure should be temporarily put on hold and then workshopped extensively to make it better. ] (]) 20:17, 28 October 2024 (UTC) | |||
*:Agree with this take, assuming it can even be made better, which I'm not sold on. ]] <small><sup>Shoot Blues, Tell VileRat!</sup></small> 22:06, 28 October 2024 (UTC) | |||
*: Opposition largely seems to be coming from admins, which makes sense but is hardly representative of editors at large. I would advise admins to take a step back and accept the wider community's opinion here. ] (]) 20:46, 28 October 2024 (UTC) | |||
*::I kind of have to agree? I know it's a surprise that the policy made it through but it appears to have done so on a legitimate basis? To those folks challenging the close, is there any example of irregularity or a flawed read of consensus? ''']'''<span style="border:2px solid #073642;background:rgb(255,156,0);background:linear-gradient(90deg, rgba(255,156,0,1) 0%, rgba(147,0,255,1) 45%, rgba(4,123,134,1) 87%);">]</span> 20:52, 28 October 2024 (UTC) | |||
*::While it is true that because this involves admins and thus admins shouldn't try to discourage the process, it still is a matter that this recall process will need to be managed by admins and thus has to confirm within the framework of other processes across the board, and that's where the debate seems to be happening, that as currently written and executed, it leaves a lot of missteps that need to be addressed with the help of admins to make sure the process is able to actually work. I don't see this as admins opposing any recall process, just that this one does not have the rigor thst admins experienced in P&G writing can bring to tighten it up and avoid the pitfalls happening now.<span id="Masem:1730208787611:WikipediaFTTCLNAdministrators'_noticeboard" class="FTTCmt"> — ] (]) 13:33, 29 October 2024 (UTC)</span> | |||
*No, process not policy. The original proposal didn't include listing it as a policy, most of the !voters didn't opine on whether it should be a policy, and similar pages like ] are not policies. The policy is ], which links to ]. That's all we need. — <samp>] <sup style="font-size:80%;">]</sup></samp> \\ 20:59, 28 October 2024 (UTC)<br/>Adding: This isn't to say it shouldn't have the same "force" as ]. And regarding notice, being an RfC at VPP and linked from CENT checks enough boxes. IMO the RfC was presented in a confusing way (consensus-for-consensus with a handful of lengthy, fragmented discussions summarized in the background section), but that might just be me, and neither I nor others adequately objected on "this is confusing" grounds to constitute a real obstacle to consensus forming. — <samp>] <sup style="font-size:80%;">]</sup></samp> \\ 13:16, 29 October 2024 (UTC) | |||
*:+1 to both of these comments by Rhododendrites. -- ] (]) 19:04, 29 October 2024 (UTC) | |||
* Who's going to be the first non-admin blocked for the lèse-majesté of seeking to recall an admin, per this policy? ] (]) 21:02, 28 October 2024 (UTC) | |||
*For those editors who say that they didn't know that this was being discussed, I expressed my concerns to {{u|theleekycauldron}}, the admin who oversaw the process, months ago, and you can see that discussion here: ]. Here's a link to a discussion where I tried to get a better process for deciding whether or not it would be policy: ]. At that time, I think editors really were looking to conduct the decision process more carefully. But that got short-circuited by the RfC here: ], which established the present consensus (however one wants to characterize that). You will see me arguing strenuously, but to little effect, that this was going to go badly. I and others argued that it was premature to hold that RfC, but {{u|Barkeep49}} insisted that the time was right. That discussion was at Village pump (policy), and was advertised on CENT, so I really do think editors ''should'' have been aware of this earlier. --] (]) 21:11, 28 October 2024 (UTC) | |||
** CENT is a bit useless, though. If it had been advertised via a watchlist notice I think there would have been far more participation. ] 21:17, 28 October 2024 (UTC) | |||
**:CENT is at the top of this page, right under "Open tasks". Why do we put a useless box at the top of AN and other noticeboards? ] (]/]) 21:21, 28 October 2024 (UTC) | |||
**:* Except it isn't very visible, because the AN templates at the top and the TOC pushes it way down below the fold. I tend to notice Watchlist and Sitenotice messages, but not CENT ones. It would probably be useful to transclude CENT to watchlists. ] 21:34, 28 October 2024 (UTC) | |||
**:*:{{+1}} to adding it to the top of watchlists (or at least someone creating a userscript that does that). ] (]/]) 21:36, 28 October 2024 (UTC) | |||
*:I was aware of RFC3 thanks to T:CENT, but the wording of the question in RFC3 was confusing to me, and led me not to comment. I thought it wanted me to read an old RFC and summarize what the consensus was in that, rather than coming to a fresh consensus. –] <small>(])</small> 06:07, 29 October 2024 (UTC) | |||
*I believe Maddy's closure was appropriate. However, the first application of the policy left a lot to be desired. I would like to see the normal editing called out in the close to refine the policy become a lot more vigorous as a result. In particular, we need to decide if petitions are allowed to devolve into a RRFA prequel (in which case 30 days is ridiculous) or if they are not (in which case stricter guidance on commentary and discussion is sorely missing).] (]) 21:45, 28 October 2024 (UTC) | |||
*'''Comment''': If editors believe that admin recall should not have the force of policy, at this point there are two options as I see it: ] of the RfC or start a new RfC seeking to strip admin recall of its status. Demanding that the policy status of admin recall be immediately stripped and that it be sent back to the drawing board is not how we establish and maintain consensus. ] (]/]) 22:20, 28 October 2024 (UTC) | |||
*:That's what this is. A close review. – ] <small>(])</small> 07:35, 29 October 2024 (UTC) | |||
*::If only people read a little past the heading before commenting. <b style="font-family:Monospace">-- ] (])</b> 08:50, 29 October 2024 (UTC) | |||
*:::Oops. My bad. {{self trout}}. ] (]/]) 17:28, 29 October 2024 (UTC) | |||
*] is pretty clear that {{tq|Consensus among a limited group of editors, at one place and time, cannot override community consensus on a wider scale.}} It's overwhelmingly clear from the response to the recall attempt on Graham that there's not actually a favorable community consensus on a wider scale than the couple of dozen editors who happened to respond to that not-particularly well-publicized RFC. Instead of demanding that we force through a bad process, perhaps consider that the original close was not reflective of what the broader community actually feels about this. ]] <small><sup>Shoot Blues, Tell VileRat!</sup></small> 22:33, 28 October 2024 (UTC) | |||
*:You're conflating two different things; I oppose the recall attempt but generally support the process, even though it's not perfect. (I haven't reviewed the discussion and don't have an opinion on the policy or not question yet.) ] (]) 23:45, 28 October 2024 (UTC) | |||
*::As someone who also opposes the specific recall, I'll add my much more noncommittal +1 to that. I don't really care too much about the specifics of the process and I'm supportive of considering it much more fluid and amendable than typical until a few months and/or recall petitions have passed, but I am overall supportive of having {{em|a}} process even if it's one that needs to be worked on (and even if I do believe we have another community initiated process that's sufficient, albeit only as a side effect and with likely a much higher... "activation energy", so to speak). ] (] • ]) 06:06, 29 October 2024 (UTC) | |||
*:This (and a bunch of other comments here) seem to be a back-channel way to revert the consensus process rather than any of the official ways to revert an RFC. Everyone agrees that this has been an incredibly rocky start for the process, other people are trying to fix it. But a bunch of editors suddenly complaining about the process, no matter how respected, does not suddenly revert consensus. In these three threads, editors who have concerns about this project are (rightfully) way more likely to comment now than the editors who already agree with calling it a policy. I encourage the former to follow the proper way instead of claiming lack of consensus without proof. ] (]) 02:45, 29 October 2024 (UTC) | |||
*:It was well advertised, I was aware of it but didn't comment or read much of it. If a well-publicised well-attended RfC closed less than a week ago is 'limited consensus at one place and time' then I have no clue what the wider community consensus ever could be. | |||
*:If you didn't participate in an RfC for whatever reason and disagree with the result there are ways to go about it, citing CONLEVEL isn't one of them. ] (]) 05:52, 29 October 2024 (UTC) | |||
*The distinction between policy and procedure in this case may well be worth diggin into, but the idea that this has to stop because "admins didn't know about it" is the fault of those admins, as it was on CENT and in the last issue of the admin newsletter, and the overall RFA 2024 process has been going on for.... I dunno feels like forever. I didn't think it would pass, and I think this first attempt at using it has thrown some serious issues with it into the public eye, but this wasn't snuck in any back door. ] ] 02:25, 29 October 2024 (UTC) | |||
*Yes, it is policy and enjoys consensus. The whole process was well advertised and had a lot of participation. Could it of been more? Sure, but it was sufficient. There are things that can be worked out with the process as shown, but there is no question that there is consensus to have a process. So basically, since this is a close review, '''Endorse''' the close. ] (]) 13:16, 29 October 2024 (UTC) | |||
*The policy modified is primarily ], ] is really just the procedures for how to follow the policy. — ] <sup>]</sup> 13:31, 29 October 2024 (UTC) | |||
* Fourth time is the charm huh? '''Yes''', it is a policy. How many times do we need to ask this question before we accept it as such? <span style="border-radius:9em;padding:0 7px;background:#000000">] ]</span> 13:54, 29 October 2024 (UTC) | |||
*:This question has not been asked before. Please read the top of the section if you have not already. – ] <small>(])</small> 18:44, 29 October 2024 (UTC) | |||
*On the actual question Joe is asking, namely "should ] have a {{t|policy}} tag, my response is that I don't especially care one way or the other; the tag at the top of the page doesn't change what actually matters, which is that the process has teeth (i.e. if an RRFA is failed, a bureaucrat ''will'' actually desysop the admin in question). But since at least Joe cares, sure, remove the tag, it was never authorized to be there. ] 14:43, 29 October 2024 (UTC) | |||
*Maddy's close was correct. I happen to think it's more process than policy because it's a process Admin X goes through to keep or lose their Admin flag. It's not a policy because there's no clear X/Y outcome. It's petition pass/fail, RRFA pass/fail. As both of those are subjective, it is not a policy situation. However it is a policy in that (using the current example) Graham cannot close Diletantte's petition because they filed it per the framework established. It has bugs as any new process does. Let it run and sort it out before the next. Disclosure, current petition opposer but not involved in RFCs as far as I can recall ] ] 15:39, 29 October 2024 (UTC) | |||
*Is ] a policy? No. Is ] a policy? No. Is ] a policy? Also no. ] (]) 15:43, 29 October 2024 (UTC) | |||
:So there's two things here. | |||
:Yes, admin recall is a policy: it has wide acceptance ("]") and was thoroughly vetted by the community. Three separate RFCs over the course of a year, with over 100 editors participating, advertised at the Village Pump, AN, CENT, the Admin Newsletter, user talk page notices, and watchlist notices. If that doesn't count as thorough vetting and wide acceptance, then nothing will. Admin recall is a standard that must be followed (subject to IAR)--bureaucrats ''shall'' desysop following a successful recall--so it's not like a guideline or essay. And anyway, the mechanism by which advanced permissions like sysop are added and removed obviously must be done by policy and not by any lower level of consensus. The reason ] should have a {{t|policy}} tag is because it's the page that documents the policy. To the extent this is a close review (I'm not sure about that), '''endorse''' and (involved). ] (]) 16:32, 29 October 2024 (UTC) | |||
:* First, TopVat19sEver, you removed other users comments from a talk page (not allowed). A user voicing their opinion is '''not''' vandalism, not in the slightest. If you have a problem with what another user has said on the talkpage, rather than ] (which is only allowed in very specific situations), you should bring it for discussion at an appropriate noticeboard, or preferably ask them to change their own comment. | |||
:'''No, it's not a policy''' This is blatantly obvious. The RfC that was concluded indicating it is a policy did ''NOT'' include any mention whatsoever of asking if it should be policy. None. Nada. Zip. Nothing. In fact, several people who commented on the RfC noted that details of the policy still needed to be hashed out. The fact is, there was no vote to make this policy. ], I appreciate the effort you put into making this close, but this close is a mistake in making this a policy. The question was whether the recall process has consensus, NOT if the recall process should be policy. --] (]) 18:30, 29 October 2024 (UTC) | |||
:* Second, Acalamari, could you please refrain from calling people "Drumpf supporters" and ] on the reasons for nominating an article for deletion? While you're entitled to your opinions, that's borderline (at best) ], especially when you call them "delusional". | |||
* I don't really mind whether the contents of ] are moved into ] instead, but that particular sub-section I think has the status of a procedural policy. I also don't feel all policies have the same barrier to change, if that's the main concern. Changing a fundamental part of ] requires a very different level of consensus compared to a policy with 15 talk page watchers. There are things with admin recall that will likely need tweaking; I think reasonably advertised talk page discussion has the ability to make such change. Re procedure: I don't think procedural policies need an explicit vote to that effect. Many current procedural policies didn't, eg AFAICT ] was promoted after {{u|xaosflux}} felt it shouldn't be tagged as an essay, and nobody objected. Ditto with ] per .{{pb}}Ultimately, ] details procedure on a process that many in the community likely care about the details of, and said thing is built up by defined rules approved by consensus, as opposed to fuzzy conventions built up over time by trial-and-error. I think these are the some of the hallmarks of procedural policy. ] (]) 23:11, 29 October 2024 (UTC) | |||
:If both users agree to accept what they did wrong here and move forward, I don't think any further action is necessary. -bɜ:ʳkənhɪmez | ] | ] 22:53, 16 January 2025 (UTC) | |||
*:{{tq|WP:File mover was promoted after xaosflux noticed felt it shouldn't be tagged as an essay, and nobody objected}}. ] appears to still be an essay. If you read the box at the top of the page carefully, I don't think it's claiming to be a policy or guideline. Instead, someone wrote a custom ombox that seems to be rather unclear, instead of using the standard {{t|Information page}} tag. –] <small>(])</small> 04:32, 30 October 2024 (UTC) | |||
::Ok, I'm newer to Misplaced Pages, I understand what you are saying, my train of thought was, "this comment looks like vandalism, vandalism on Misplaced Pages is removed, therefore remove". I didn't know that they don't do that for talk pages. Thank you my friend. ] (]) 22:59, 16 January 2025 (UTC) | |||
*::It's categorised under ] and listed at ]. In any case, there's ] and these are just the first two I checked. ] (]) 07:12, 30 October 2024 (UTC) | |||
:::Vandalism has a '''very''' specific definition on Misplaced Pages - see ] for more information on what is not vandalism. Merely calling people names and/or being uncivil, while against the rules, is '''not''' vandalism. There are proper processes for handling other rule violations (such as asking someone to edit their own comments, or asking a noticeboard for help) such as those, but they are decidedly '''not''' vandalism. -bɜ:ʳkənhɪmez | ] | ] 23:01, 16 January 2025 (UTC) | |||
*::I suspect all the userright procedural policies fall under the same bucket. The RfC behind them usually just asked if such a userright should be created / unbundled. The creation of a procedural policy page was either done by a single editor, or said by the closer to be done as in ], but was not the RfC question explicitly, and until the closer mentioned it, nobody else did afaict. My point being, I suspect very few of the current procedural policies had explicit confirmation votes. ] (]) 07:17, 30 October 2024 (UTC) | |||
::::Ok thank you for telling me ] (]) 23:02, 16 January 2025 (UTC) | |||
*:::I've started ] to work on fixing these odd pages that have a policy category but no policy template and little original talk page discussion about promoting them to policies. –] <small>(])</small> 21:43, 30 October 2024 (UTC) | |||
:Where are the ]? ] (]) 22:54, 16 January 2025 (UTC) | |||
*It's a rule, but it's not ready to be policy yet. Let the procedure evolve into a more final form and let the naysayers finish processing their defeat. Then hold a RfC about promoting it to policy.—] <small>]/]</small> 16:43, 30 October 2024 (UTC) | |||
*This is a baseless complaint. Ater not editing for months, the OP refactored an AfD that was closed last November. Acalamari rightly warned them for doing that.--] (]) 22:56, 16 January 2025 (UTC) | |||
*:I agree, but at the same time, I think TV19E has a right to be unhappy that Acalamari, an administrator and bureaucrat, was able to cast aspersions and call people names without it being called out at the time as far as I can see. They went about it the wrong way (removing the comment), but that doesn't mean there isn't room for discussion of that comment. -bɜ:ʳkənhɪmez | ] | ] 22:58, 16 January 2025 (UTC) | |||
*::Nope. First, it doesn't rise to the level required of this noticeboard, and, second, it's not at all timely.--] (]) 23:01, 16 January 2025 (UTC) | |||
*:::To be blunt, Acalamari didn't even tell the editor when they ''initially'' reverted back in November (while the discussion was open) where they could discuss further/report if they felt the comment was not appropriate. I'm not suggesting sanctions against Acalamari at all. But to tell a new editor "someone broke the rules and since you didn't report it in the proper way at the time because nobody told you how, they're allowed to break the rules" is clear ]. I think all that's necessary is an apology from Acalamari - TV19E has already explained that they were mistaken as to it being vanadalism. -bɜ:ʳkənhɪmez | ] | ] 23:03, 16 January 2025 (UTC) | |||
*:I didn't edit for a few months because I have to do other things. I was just scrolling around I don't even remember what I was doing and I saw he put it back, I didn't know he was a mod, and it also said you can't edit archived talk pages, which he did, so I reverted his edit. ] (]) 23:03, 16 January 2025 (UTC) | |||
*::That's not true. You modified a closed AfD. Acalamari rightly reverted your edit of an archived discussion.--] (]) 23:06, 16 January 2025 (UTC) | |||
*:::I just said, he is the one who modified a closed AfD, which is not allowed, then I reverted it not knowing he is a moderator ] (]) 23:08, 16 January 2025 (UTC) | |||
*::::He didn't modify a closed AfD. His comment was readded while the discussion was still open, because you removed it in violation of ]. -bɜ:ʳkənhɪmez | ] | ] 23:09, 16 January 2025 (UTC) | |||
*:::::Oh okay this is my mistake then I thought it was after the AfD was closed my bad ] (]) 23:11, 16 January 2025 (UTC) | |||
*:::::Wait hold on, I just looked at it again. He added back his comment after the result was SNOW. On the page when he re added it, it said do not edit the page. ] (]) 23:16, 16 January 2025 (UTC) | |||
*::::::You removed Acalamari's comment as vandalism with the edit summary "subhanAllah". You had ''no right'' to do that. Acalamari restored it, which even though the AfD was closed, they had the right to do in the circumstances.--] (]) 23:27, 16 January 2025 (UTC) | |||
*:::::https://en.wikipedia.org/search/?title=Misplaced Pages:Articles_for_deletion/2028_United_States_presidential_election_(3rd_nomination)&oldid=1257014612 Take a look, this is his edit. When he re added his comment, on the page in red it said '''Do not edit the page''' ] (]) 23:18, 16 January 2025 (UTC) | |||
*::::::The comment never should've been removed in the first place. It's within the spirit of the rules to readd a comment that you improperly removed, even if the discussion had been closed in the meantime. -bɜ:ʳkənhɪmez | ] | ] 23:32, 16 January 2025 (UTC) | |||
*{{ec}} There's no admin abuse here as no admin tools have been used. In case you missed ''"The following discussion is an archived debate of the proposed deletion of the article below"'' with the bright red ''"Please do not modify it"'' at that AfD, I'll repeat the instructions here - don't modify archived discussions.-- ]<sup>]</sup> 22:57, 16 January 2025 (UTC) | |||
*:I was saying Admin abuse because of the fact that he is able to keep his comment on the page when even if he is violating the rules. I'm not a moderator so I can't do anything about. Now I just learned from that guy that they don't remove comments even if its vandalism, now I know. But thats why I reported it here you know. ] (]) 23:01, 16 January 2025 (UTC) | |||
*:He is the one who edited the closed AfD. This was one of the reason why I reverted his edit. ] (]) 23:10, 16 January 2025 (UTC) | |||
*It's very hard to work out what's happening without the presence of diffs. ] (]) 23:02, 16 January 2025 (UTC) | |||
:*{{tq|without the presence of diffs}}. But Ponyo and I have contributed, so you're in the presence of greatness; isn't that better than diffs? :p --] (]) 23:08, 16 January 2025 (UTC) | |||
:*:* ''Tiggerjay is bowing down in great humility before such greatness never before seen in this universe. '' Now.... where is the trout? ] ] 23:24, 16 January 2025 (UTC) | |||
:*:Who am I to disagree with the Jedi? ] (]) 23:52, 16 January 2025 (UTC) | |||
*Okay, I've looked into this. And...surprise surprise, TopVat19sEver was the one who ''origially removed Aclamari's !vote while the AfD was still open'' . Yes, about a day after the AfD was closed, Aclamari reverted this removal , which ''is'' technically "editing a closed AfD" but I would say they were ] to revert a ]. And now, suddenly, today, two months later, as their first edit ''after'' having done that improper removal, TopVat19sEver goes back to the AfD and removes Aclamari's !vote ''again'' , which Aclamari - entirely rightfully - reverted , and then TopVat19sEver comes here to cry "admin abuse", when no administrative abilities were used ''at all'' in this whole mess. Could Aclamari have used more moderate language in their initial !vote? Yeah maybe, but it was no ''violation'' at all, and the only thing needed here is a ] or at least a {{tl|trout}} for TopVat19sEver. - ] <sub>]</sub> 23:27, 16 January 2025 (UTC) | |||
*Leaving aside the questions of whether it has consensus or not (I personally think the final version of the procedure should have been put to an up or down discussion rather than having a weird RfC to determine if a previous RfC had consensus, which would’ve avoided the issues we have now), I don’t see how we can ask crats to desysop admins under this procedure without it having the force of policy. ] (]) 20:34, 30 October 2024 (UTC) | |||
{{Abot}} | |||
*:That's a very good, and important, point. If, hypothetically, an admin has a petition that reaches the required number, and either refuses to engage in a new RfA or fails to pass it, there could be a real question as to whether any bureaucrat has the authority to take action. --] (]) 20:46, 30 October 2024 (UTC) | |||
:::Given that the RfC wasn't worded to ask to make it policy, the answer is no. There is no policy that supports a bureaucrat having the authority to remove the flag based on this procedure. --] (]) 20:51, 30 October 2024 (UTC) | |||
::::It's a nonsense! ]] 21:30, 30 October 2024 (UTC) | |||
:::::I've ]. ] (]) 21:32, 30 October 2024 (UTC) | |||
::I guess that will be up to the crats. One of their roles is to provide a final sanity check on sysops/desysops, so I don't think it's a bad thing to allow them some discretion during the first few runs of this new process. – ] <small>(])</small> 07:02, 31 October 2024 (UTC) | |||
== Ban appeal from Rathfelder == | |||
*'''Remove the "policy" designation''' I think that the close was a pretty good one for it's narrow scope in the chain of events that led to this, albeit requiring some expert derivation because the question was not clearly in the RFC making it what I would call an edge case regarding being the right close. But in the big picture (including that chain of events), a high impact policy should be something which had every sentence in it carefully reviewed, has been optimized, and has had wide advertisement/participation to adopt it, and where considering it to be policy a clear part of the question. IMO none or hardly none of those criteria has been satisfied. Further, the initial general decision (in essence saying that there shall be a recall process) was only the starting point of what should have been a thorough process that included all of the above and which in my opinion it wasn't and didn't include all of the above. Let's just take a little extra time to do all of the above instead of having this cloud eternally hanging over the recall process. Sincerely, <b style="color: #0000cc;">''North8000''</b> (]) 21:32, 30 October 2024 (UTC) | |||
The ship has been launched, so let it sail for a whole year. Than review it. ] (]) 21:38, 30 October 2024 (UTC) | |||
:Fingers crossed there's an iceberg soon... ]] 21:53, 30 October 2024 (UTC) | |||
::I think the current petition could well be described that way. --] (]) 22:30, 30 October 2024 (UTC) | |||
::: What an interesting mixed metaphor ... ] ] 03:41, 31 October 2024 (UTC) | |||
* {{userlinks|Rathfelder}} | |||
== A question from a very active editor == | |||
* ] for sockpuppetry, vote-stacking and undisclosed COI writing of a BLP attack page | |||
* ] declined by the community | |||
* ] not submitted for review by the community for not complying with ] | |||
Rathfelder has submitted the following ban appeal on their talk page and asked me to copy it here: | |||
What should I do if I just-so-happen to be someone who is mildly-to-very famous, and/or is siblings with someone like that? Like, ultra-famous? | |||
{{tqb|I realise that what I did was wrong - more wrong than I thought it was at the time. The circumstances which led me to edit pages where I was conflicted are not likely to recur. I accept that I was wrong to create sockpuppets and I apologise. I was involved in a dispute with my employers and it was very wrong of me to use Misplaced Pages as part of that. I did that really because I was trying to defend the work I had done for the Socialist Health Association for the previous 20 years. I did a lot of edits on that page, but they were, until the last few, about the history of the organisation, mostly adding to its list of distinguished members - largely before I was involved with it, and mostly before I was born. They were not at all controversial. I was unfairly sacked and my opponents started using Misplaced Pages against me. The row got into the media. I accept that I should not have done that. I should have resisted the temptation to use Misplaced Pages in the dispute.<br> | |||
I have spent 2 years working on Simple English and Wikimedia. I have not set up any sockpuppets or edited anything where I had conflicts. I plan to continue with Wikimedia, as there is plenty there to keep me busy, but I would like to be able, in particular, to add pictures to articles - now I have found my way round the enormous Wikimedia resource. I also sometimes come across articles in English wikipedia which need amendment.}} ] (] · ]) 17:02, 17 January 2025 (UTC) | |||
*'''Conditional support''' - If there's been no socking ''during'' the ban. ] (]) 17:05, 17 January 2025 (UTC) | |||
I've helped with plenty of stuff on ] before, but I have no idea how to proceed in this scenario. I trust that people will know that I am telling the truth about this, as I have over 15,000 edits on this site. | |||
*'''Question''' during the January 2024 unblock request Rathfelder said they would be willing to accept a restriction on editing articles related to BLPs or healthcare orgs. Are they still willing to accept those edit restrictions if they are un-banned? Furthermore, in January 2024 there was, at the time, no evidence of any further socking. Can we confirm that good behaviour has continued? ] (]) 17:17, 17 January 2025 (UTC) | |||
*'''Support''' They have been a very productive contributor at the Simple English Misplaced Pages, and it has definitely been long enough for the ]. ] (]) 21:33, 17 January 2025 (UTC) | |||
== Appealing April 4 2024, indefinite WP:CUP ban and indefinite 1-nomination GAN limit == | |||
Can my publicist make disclosed COI edits on my behalf (using their own account- not mine)? | |||
{{atopr | |||
| result = Consensus to lift this ban will not develop. ] (]/]) 22:02, 17 January 2025 (UTC) | |||
}} | |||
At ], I was instructed by closer ] that I could appeal these in a year and it has been 9.5 months. I am appealing because the CUP entry deadline is traditionally January 31. See ] through ]. This year the ] verbiage says "The competition will begin on 1 January 2025 and signups will continue throughout the year". I am just noticing the new language as I am putting this appeal in. Nonetheless, I am requesting time off for good behavior on the ban.-] <small>(] / ] / ] / ] / ])</small> 18:52, 17 January 2025 (UTC) | |||
How do I verify to administrators that I am who I say I am? I don't really want this username to become publicly tied to me, for the sole and only reason that legions of fans might descend upon my talk page, wreaking havok. | |||
:'''Oppose''' The utter cluelessness of this appeal is more than enough reason not to do this. I was going to write more but decided that coaching you on how to be less clueless is not in the project's best interest. You've been here long enough that you should be able to see for yourself how terrible this appeal is. ] ] 19:02, 17 January 2025 (UTC) | |||
Again, I'm not going to say who I am. | |||
:'''Oppose''' and recommend we disallow any further appeals for another year. I'm concerned otherwise we'll just be back here in April. --] (]) 19:14, 17 January 2025 (UTC) | |||
:'''Oppose for now''' It's pretty clear that most people in that discussion were supporting an indef ban from the Cup, not an 8-month ban. This appeal doesn't address people's concerns with Tony's editing relating to the Cup, so should be denied. --] 19:16, 17 January 2025 (UTC) | |||
: '''Oppose''' The original discussion wasn't linked, it can be found ]. At that place it is very clear that {{tq|here is almost unanimous support for an indefinite ban on participation in the WikiCup}}, so, no, this appeal should not be passed. It is, honestly, astonishing that TonyTheTiger has been here very nearly two decades but hasn't taken on board the way the community works ~ ''']'''<sup>''']''']</sup> 19:20, 17 January 2025 (UTC) | |||
:'''Oppose''' for no rational that they understand why they were banned or what even led to their ban, and rather simply a sentiment of "I really want to participate". Please understand that '''your ban was indefinite''', so the one year appeal opportunity is your potential opportunity "time off for good behavior". ] ] 19:24, 17 January 2025 (UTC) | |||
:'''Oppose'''. Appealing early on the basis that you won't be able to sign up to do the thing you were banned from doing is certainly a unique take. ♠]♠ ] 21:03, 17 January 2025 (UTC) | |||
{{abot}} | |||
==Requesting info== | |||
Not asking on anyone else's behalf, by the way. | |||
{{atop | |||
| result = {{u|Steve Quinn}} is {{itrout|trouted}} for bringing this to AN. ] (]/]) 21:58, 17 January 2025 (UTC) | |||
}} | |||
Hello. I have come across several image files and the U.S. Gov. PD licensing seems to be incorrect. Four of these images and possibly another one could be copyright violations - if I can figure out how to find this type of information on their websites. However, since I am unable to find that information at this moment, I am wondering which group of Misplaced Pages editors work on this sort of thing so that maybe I can get some help with this. I will post the files here for information purposes. Also, there may be more copyright violations by this particular editor who seems to have a propensity for downloading image files. Below are the files: | |||
# ] | |||
# ] | |||
# ] | |||
# ] | |||
# ] | |||
Further comment: The above TN file - File:AppalachianTN.jpg - is covered by the TN.GOV "linking policy" and can be found . So this Misplaced Pages image file is still not licensed appropriately, although I have no idea what the correct Misplaced Pages licensing would be. | |||
I will notify the editor who downloaded these files that I have opened a discussion here. Well, now that I have taken it this far, the editor in question is: {{userlinks|Brian.S.W}}. However, the above image files might be too stale to be considered for any action. I leave that up to the Admins. If you look on their talk page, they have previously been blocked for copyright violations. ---] (]) 20:59, 17 January 2025 (UTC) | |||
Live long and prosper. <span style="font-family:Courier;background-color:#000000">]]</span> 22:25, 28 October 2024 (UTC) | |||
:Your editing and the editing of someone you hire relating to you as a person outside of Misplaced Pages are two separate things, in my view. As long as the two never cross paths, there's no reason you need to dox yourself to anyone. ] (]/]) 22:29, 28 October 2024 (UTC) | |||
:(edit conflict) The easiest approach is for you to simply not perform any edits in your conflict of interest. Then, there's no need for you to disclose. Your publicist, on their own account, could disclose (]) their own conflict and simply not mention your account. For example, let's say you are ] (for example, you obviously aren't). Don't edit ], don't edit about your family or your movies or anything else for which you have a conflict. Your publicist discloses that they are Liv Tyler's publicist, without mentioning TheAwesomeHwyh at all. They are then free to edit within the normal bounds (which, frankly, means they probably should only be ''suggesting'' edits on article talk pages, making clear it's a COI edit request). If you want to be extra careful, ensure you and your publicist don't communicate over Misplaced Pages (and... why on earth would you) and don't connect from the same IP address (]). You may wish to '''privately''' disclose your own conflict to ] (others will correct me if I'm pointing you in the wrong direction there), noting your publicist's account too and indicating you'll avoid COI edits. Now, you can validate that you are Liv Tyler (for example). We sometimes require that when people pick a username of a famous person. But, I don't think that's something you want or need to do here. Far better to keep this account anonymous and simply avoid the whole mess, yes? --] (]) 22:38, 28 October 2024 (UTC) | |||
::Those are precisely my thoughts, stated much more thoroughly. ] (]/]) 22:39, 28 October 2024 (UTC) | |||
:::Thanks. I won't even mention this account to my publicist. <span style="font-family:Courier;background-color:#000000">]]</span> 22:45, 28 October 2024 (UTC) | |||
::::Liv, can you get me tickets to the Captain America:Brave New World premiere? ]] <small><sup>Shoot Blues, Tell VileRat!</sup></small> 23:41, 28 October 2024 (UTC) | |||
:::::{{u|TheAwesomeHwyh}}, a potential pitfall of your plan is ]. You can orient your publicist to Misplaced Pages’s policies and guidelines, and let them know that you would like the Misplaced Pages article about you to be improved. You need to emphasize to the publicist that they must make the ]. But if you give them a specific list of things you want added, removed or changed, then that would be a policy violation, so be cautious. ] (]) 00:42, 29 October 2024 (UTC) | |||
:::{{outdent|2}} {{tq|if you give them a specific list of things you want added, removed or changed, then that would be a policy violation, so be cautious.}} Meatpuppetry is defined as having another editor make the same arguments as you in a content debate; it is unrelated to hiring a paid editor. Generally, when you hire someone to write for you, you tell them what you want and they try to do it. For example, ] could decide to hire a paid editor and instruct that editor to propose a much shorter version of the controversies section that downplays all allegations. That paid editor could then draft a new section and attempt to argue that it's actually more ] and ] than the current article version. Meatpuppetry would be if MrBeast proposes those changes himself and then secretly persuades 100 established editors to support him in an RfC. The former follows our COI policy, the latter does not. ] (]/]) 01:19, 29 October 2024 (UTC) | |||
::::I'd agree. If there's no deceptive or disruptive use, I don't think it should be considered an issue. To be honest, as long as their main account avoids the same topic area or any projectspace discussions (except those that directly affect the account), my reading of the socking policy (not that I have any particular expertise in this regard) is that they are even permitted (even if it's not necessarily recommended) to create a separate account under their real name (though, the policy comes at it from the opposite direction, where the main account is under the real name and the alternate is a pseudonym). The security of said alternate accounts of course, is the editor's individual responsibility. ] (] • ]) 06:28, 29 October 2024 (UTC) | |||
::"{{tq|don't connect from the same IP address}}" -- I thought checkusers can only access data from actual edits made through an account? Not from just logging in. ] (]'''-''']) 00:49, 29 October 2024 (UTC) | |||
:::{{replyto|Nythar}} ]. For better or worse, this whole situation will remind too many people of the ]. At least, compared to that account's first edit, we know for a fact that the OP is not a ]. :-) ] (]) 03:08, 29 October 2024 (UTC) | |||
::::There's nothing at all similar to Lourdes and any comparisons should be dismissed out of hand. Hwyh did the right thing asking and there's literally no policy that prohibits an existing editor from hiring a paid editor to do things that they can't because they have a COI. That's the whole point of the COI policy. If a famous person wants to edit Misplaced Pages unrelated to their own life, they should be allowed to do so without creating a real name alt and making their own COI edits. ] (]/]) 11:49, 29 October 2024 (UTC) | |||
:::::Thanks, all! Due to the fact that there seems to be a bit of controversy as to how to proceed with this, I decided that I will disclose that this is my account, eventually. I'm waiting for something important to happen in real life (which still might not happen) before I disclose this. | |||
:::::I also have a separate, slight conflict of interest with basically everything to do with the LISP programming language. I actually recently acquired one of the companies that used to make ] software so I felt like I should disclose that. That's a separate ], though. | |||
:::::I will also disclose that I used to edit under ] as I had briefly forgotten the password to TheAwesomeHwyh. I no longer go by "Charlotte", though. | |||
:::::Second star to the right, and straight on 'till morning! <span style="font-family:Courier;background-color:#000000">]]</span> 18:29, 29 October 2024 (UTC) | |||
::::::I probably won't post any more comments on this thread as I actually haven't asked my publicist if they're okay with me posting this stuff on this public noticeboard. Whoops... | |||
::::::Ad astra per aspera. <span style="font-family:Courier;background-color:#000000">]]</span> 18:38, 29 October 2024 (UTC) | |||
:::Also, there is an established system of verification of famous people mentioned under the ]. Verification in this case is done by sending an email to the ] (VRT) and quoting the resulting ticket number if needed. ] (]) 03:18, 29 October 2024 (UTC) | |||
:As you can see they've already been tagged for a deletion discussion yesterday, so there is no need to have a difference notice board also working on it. ] ] 21:21, 17 January 2025 (UTC) | |||
== Disruptive IP == | |||
{{abot}} | |||
Can an administrator please block the IP address ]; has been repeatedly adding false information to the articles of different animated series, seems to be mostly targeting '']'', adding a fake season 3 and characters and guest stars who have not appeared at all. ] (]) 01:20, 29 October 2024 (UTC) | |||
:That's {{user|71.172.48.193}}. I don't see any discussion on the issue. Please try to engage with the IP (and see "you must leave a notice on their talk page" above). An admin such as myself has no knowledge of the topic and the IP has to have an opportunity to explain their edits. ] (]) 02:47, 29 October 2024 (UTC) | |||
== Unmerge my enwiki account from global == | |||
Please switch all of my rights (extended confirmed, reviewer, comfirmed user) into the account {{u|TienMinh-mun6xnChing}}, I'm no longer use this main account for contributing, thanks. ] (]) 11:34, 29 October 2024 (UTC) | |||
:This will not "unmerge" anything (we don't do that), but sure I've moved your account flags. — ] <sup>]</sup> 13:35, 29 October 2024 (UTC) | |||
== unblock request == | |||
I made an edit request that conformed to the WP template and guidelines. Multiple users vandalized my edit request by deleting it. I was blocked for reverting that vandalism. | |||
I know the rules of edit requests and I understand and respect why they are what they are. ] (]) 18:10, 29 October 2024 (UTC) | |||
:This matter is being dealt with at the editor's talk page. ] (]) 18:23, 29 October 2024 (UTC) | |||
== Request for a general look-in on ] == | |||
Posting here to suggest an admin take a look at ]. Looks to be spiralling into various policy infractions and misuse of the page as a forum. ] (]) 19:38, 29 October 2024 (UTC) | |||
:I collapsed an unconstructive thread. – ] (]) 19:51, 29 October 2024 (UTC) | |||
:@] any particular things you want to highlight? There's a lot to read there ] ] 19:53, 29 October 2024 (UTC) | |||
::@] to me skimming through it I got a general sense it was devolving into Not A Forum discussions more about their views on the comedian and cancel culture rather than actually discussing the article proper. ] (]) 19:57, 29 October 2024 (UTC) | |||
:::@] if asked to be more specific I'd say the dispute over the neutrality of the lead seems to have in particular descended into people's views on the comedian and their brand of humour rather than the actual neutrality of the lead. ] (]) 20:03, 29 October 2024 (UTC) | |||
::::This is what we've experienced on the talk pages of Trump and RFK Jr. for long beyond my recollection. It will likely continue for Hinchcliffe until his 15 minutes from the MSG rally are up. We can observe and interject when things get too far FORUM-y. – ] (]) 21:14, 29 October 2024 (UTC) | |||
:::::] has also come close to ] with a number of editors who definitely have never participated in AfD, but this seems to be status quo for '''any''' American politics article or discussion lately (those of you moderating and closing these discussions right now; you're doing good work). <span style="font-family: Roboto;">''']''' <span style="color:#00008B">•</span> <small>''(])''</small></span> 23:43, 29 October 2024 (UTC) | |||
== Authenticity regarding citation needed spam. == | |||
Hello there. | |||
I've discovered ] seems to have a knack for contributing on many articles () where instead of contributing constructively or providing sources, the user finds any paragraph that contains a statement without a source, and marks it as {cn}. That'd be constructive and helpful, were it not done to the extent the user is doing it. There's a balanced argument of 'is this constructive editing' that, judging on their talk page, I am not the only one questioning. | |||
This is a sticky situation that peaks my interest. Does this classify as disruptive editing, or is {cn} working as intended to bother people into providing sources for their statements? <span style="color: #4169E1">'''Synorem'''</span> (]) 01:33, 30 October 2024 (UTC) | |||
:In this case talking to the IP editor appears to be working. In the general case, I believe indiscriminately adding cn's can easily be disruptive, even for completely unreferenced material. The tag is only helpful if applied sparingly to indicate an absolute requirement for an inline source to comply with referencing policy, ie "for any material challenged or likely to be challenged, and for all quotations". ] <small>(])</small> 01:50, 30 October 2024 (UTC) | |||
:Conversely, the most constructive way to object to a {{tl|cn}} tag is to add a source. That way everybody wins. – ] <small>(])</small> 08:24, 30 October 2024 (UTC) | |||
:::Counter-conversely, it's far better to add a source than a cn tag. Cn is for where the contested statement is doubtful or controversial and the disputing editor has made a good faith effort to source it, can't, but also can't justify removing the contested statement. Those should be rare circumstances. Adding cn tags indiscriminately is a low-effort way to contribute and it's a smash-and-grab raid on our volunteer time because it fills already-unmanageably-large queues with low-priority tasks.—] <small>]/]</small> 11:43, 30 October 2024 (UTC) | |||
:@], thanks so much for bringing this up and asking, rather than just dumping some warning templates on their talk page and leaving! It looks like you've found a motivated new editor who loves Misplaced Pages and wanted to do whatever they could to help. The best kind! Now we just need to do what we can to keep them. :) -- ] (]) 15:58, 30 October 2024 (UTC) | |||
== AIV backlog == | |||
Hi. There's a heavy backlog at ]. ] <sup>(])</sup> <sub>(])</sub> 07:51, 30 October 2024 (UTC) | |||
== Lifting my limited topic ban and my mentorship == | |||
I, {{IP|Davidbena}}, after successfully appealing my ] Topic ban on 16 May 2023, was appointed a mentor to counsel and assist me in my edits in the ARBPIA area (see ). After editing under this capacity for more than a year, I wish now to appeal my long-standing limited topic ban that was made some years earlier (which you can see ). Having the liimited ban lifted will enable me to return to editing in the ARBPIA area without limitations. | |||
For a record of my past offenses, here is a list of former discussions which ended in either a block or a topic-ban: | |||
# "frivolous ANI report" | |||
# (topic ban) | |||
#: topic ban lifted | |||
# (new topic ban). | |||
#: appeal to rescind the ban was unsuccessful | |||
# (placed under narrow topic ban) | |||
# (one-month block for canvassing) | |||
# (broad topic ban), which ban was lifted on 16 May 2023 (as shown ) when I was assigned a mentor in the ARBPIA area, but leaving in place my narrow topic ban. | |||
I am fully aware that my history of punitive measures taken against me by the community was started by my own short-sightedness in being quick to jump to judgment against my fellow co-editors in the ARBPIA area, whom I accused at first of "stalking". These accusations, as they later came to show, were proven inaccurate. I have since worked with the same editors on improving a number of articles in the ARBPIA area. Moreover, I am now fully aware that ''all edits'' made by the general consensus of ''all editors'', especially of those holding different political views and who belong to different political spectrums, contribute to the overall uncensored preservation of history and of general knowledge. This is my honest view. I have worked in the past year with Misplaced Pages editor ] who has opened my eyes to this realization, even though we hold different political views. I assure my fellow Misplaced Pages editors and those here arbitrating this case that I will continue to consult the views of others before posting a controversial edit in the ARBPIA area. | |||
For the record, my statement to the Misplaced Pages editor, ] (see ), who has borne with me patiently throughout all my shortcomings and my personal attacks has been this: "I have since learned that every person who contributes anything in this world, especially on Misplaced Pages, is on a special mission sent by God. It doesn't matter who we are, or what religion or ethnicity we belong to. In Israeli/Palestinian issues, it is all one continuous history, interlocked. That is my honest view. I appreciate your work in the Palestinian issues, just as I appreciate my own work in Israeli history, both old and new. Everything has its place. I have learnt on Misplaced Pages to appreciate other views and to be more open to them, even when I disagree. I will not force my own view upon others. That much I can assure you" (End Quote). The same assurances I give to those who arbitrate my case. Be well.] (]) 01:17, 31 October 2024 (UTC) | |||
:'''Support''' per David and ] on Nableezy's talk. ] (]/]) 01:59, 31 October 2024 (UTC) | |||
:'''Support''' ''']'''<span style="border:2px solid #073642;background:rgb(255,156,0);background:linear-gradient(90deg, rgba(255,156,0,1) 0%, rgba(147,0,255,1) 45%, rgba(4,123,134,1) 87%);">]</span> 02:02, 31 October 2024 (UTC) | |||
:'''Support''' ] <sup>(])</sup> <sub>(])</sub> 08:54, 31 October 2024 (UTC) | |||
:'''Support''': Nableezy’s cool with it, as per the linked from Voorts. {{tq| was started by my own short-sightedness in being quick to jump to judgment against my fellow co-editors in the ARBPIA area}} gives me a ''“is he a hothead?”'' pause for thought. (Not saying I think he is. I haven’t run into Bena outside of this ANI Report), but that’s all it gave. Pause. No actual concern that can be pieced together. If Aspersions are the worst worry, but not even a worry, then that’s easy for the Arbs to reinstate if my pause turns out justified. ] should be given. ] ] ] 09:36, 31 October 2024 (UTC) | |||
== User:NormalTADC == | |||
They are working towards making a long list of articles on non-notable topics to do with characters from mini-games in Roblox They have already moved their first rejected draft into the main space at ] and have another rejected draft draft at ] where they are currently warring over the rejection notice. I think they may just need a 24 block until they have some time to read the policies and guidelines. I would have tagged the first article as A7 but unfortunately I don't think it actually fits into that criteria and felt an AFD is a waste of time on such a obvious throw away. ] <sup>(])</sup>/<sub>(])</sub> 02:12, 31 October 2024 (UTC) | |||
:I just ran across this a few minutes ago. I would support the words of McMatter above, as both these articles are problematic to say the least. ] (]) 02:20, 31 October 2024 (UTC) | |||
:@], I've given them a 24-hour timeout, but please note that you were also edit-warring. It is inappropriate to put a ] tag back on after it has been removed, even if it was the article creator who removed it. -- ] (]) 02:29, 31 October 2024 (UTC) | |||
::Yea I did over step a bit, I apologize I was more undoing it to also restore the maintenance templates they kept removing I should have just restored them but we would still be at the same place as we are now. ] <sup>(])</sup>/<sub>(])</sub> 02:32, 31 October 2024 (UTC) | |||
:::No worries, and sorry, my message came out a little colder than I intended it to. Next time this happens to you (and it will, that's AfC for you), you can go to ] with it. -- ] (]) 02:35, 31 October 2024 (UTC) | |||
:FYI once a PROD tag is removed – for any (or no) reason – it has to go through AfD. Repeatedly readding it isn't helping. <span style=white-space:nowrap;>] <span style="background-color:#e6e6fa;padding:2px 5px;border-radius:5px;font-family:Arial black">]</span></span> 02:30, 31 October 2024 (UTC) | |||
== RFPP backlog == | |||
There's a major backlog over at ]. Could someone look into that? <span style="color:Purple">''' - '''</span>]<span style="color:Purple">'''. '''</span><sub>]</sub> 06:27, 31 October 2024 (UTC) |
Latest revision as of 23:12, 17 January 2025
Notices of interest to administrators
Noticeboards | |
---|---|
Misplaced Pages's centralized discussion, request, and help venues. For a listing of ongoing discussions and current requests, see the dashboard. For a related set of forums which do not function as noticeboards see formal review processes. | |
General | |
Articles, content | |
Page handling | |
User conduct | |
Other | |
Category:Misplaced Pages noticeboards |
- For urgent incidents and chronic, intractable behavioral problems, use Misplaced Pages:Administrators' noticeboard/Incidents.
- To request review of an administrator's action or other use of advanced permissions, use Misplaced Pages:Administrative action review
- If you are new, try the Teahouse instead.
- Do not report breaches of personal information on this highly visible page – instead, follow the instructions on Misplaced Pages:Requests for oversight.
- For administrative backlogs add
{{Admin backlog}}
to the backlogged page; post here only if urgent. - Do not post requests for page protection, deletion requests, or block requests here.
- Just want an admin? Contact a recently active admin directly.
- If you want to challenge the closure of a request for comment, use
{{RfC closure review}}
When you start a discussion about an editor, you must leave a notice on their talk page. Pinging is not enough.
You may use {{subst:AN-notice}} ~~~~
to do so.
Sections inactive for over seven days are archived by Lowercase sigmabot III.(archives, search)
Start a new discussionOpen tasks
Centralized discussionAdministrators' (archives, search) | |||||||||
---|---|---|---|---|---|---|---|---|---|
349 | 350 | 351 | 352 | 353 | 354 | 355 | 356 | 357 | 358 |
359 | 360 | 361 | 362 | 363 | 364 | 365 | 366 | 367 | 368 |
Incidents (archives, search) | |||||||||
1157 | 1158 | 1159 | 1160 | 1161 | 1162 | 1163 | 1164 | 1165 | 1166 |
1167 | 1168 | 1169 | 1170 | 1171 | 1172 | 1173 | 1174 | 1175 | 1176 |
Edit-warring/3RR (archives, search) | |||||||||
472 | 473 | 474 | 475 | 476 | 477 | 478 | 479 | 480 | 481 |
482 | 483 | 484 | 485 | 486 | 487 | 488 | 489 | 490 | 491 |
Arbitration enforcement (archives) | |||||||||
328 | 329 | 330 | 331 | 332 | 333 | 334 | 335 | 336 | 337 |
338 | 339 | 340 | 341 | 342 | 343 | 344 | 345 | 346 | 347 |
Other links | |||||||||
V | Oct | Nov | Dec | Jan | Total |
---|---|---|---|---|---|
CfD | 0 | 0 | 3 | 29 | 32 |
TfD | 0 | 0 | 0 | 2 | 2 |
MfD | 0 | 0 | 0 | 11 | 11 |
FfD | 0 | 0 | 5 | 18 | 23 |
RfD | 0 | 0 | 3 | 48 | 51 |
AfD | 0 | 0 | 0 | 0 | 0 |
- 0 bot-reported usernames for administrator attention
- 3 user-reported usernames for administrator attention
- 3 bot-generated requests for intervention against vandalism
- 1 user-generated requests for intervention against vandalism
- 40 sockpuppet investigations
- 50 Candidates for speedy deletion
- 2 Fully protected edit requests
- 0 Candidates for history merging
- 1 requests for RD1 redaction
- 96 elapsed requested moves
- 1 Pages at move review
- 20 requested closures
- 16 requests for unblock
- 0 Wikipedians looking for help from administrators
- 13 Copyright problems
Sander.v.Ginkel unblock request
The following is copied from User talk:Sander.v.Ginkel#Unblock_request on behalf of Sander.v.Ginkel:
I have made serious mistakes. I regret it and say sorry for it. I fully understand why I have been blocked. My biggest mistake that I copied-pasted content from articles to other articles, that led to a BLP violation. I have also misused other accounts as suckpuppets: User:SportsOlympic and User:MFriedman (note that the two other accounts –- User:Dilliedillie and User:Vaintrain -- at Category:Misplaced Pages sockpuppets of Sander.v.Ginkel was not me. ) In addition, my work was too focused on quantity, rather than quality. I apologize to those who had to do some cleaning up for me.
Whay do I want to come back? And do I deserve it? I can show that I can make constructive content. I made some edits and created pages under the IP address 82.174.61.58, that was not allowed; and was blocked. It is not good that I made edits under an IP address, but I appreciated that some users (User:Tamzin, User:Xoak, User:Ingenuity) stated they liked the content I created and/or that they offer the opportunity to have me back (see at Misplaced Pages:Sockpuppet investigations/Sander.v.Ginkel/Archive). I made the same mistakes on the Dutch Misplaced Pages (where I misused the same accounts). At this Misplaced Pages I bot back my account and I am editing the Wikipeida I’m also editing at simple.wikipedia.org (see User:SportsOlympic). I have created over 900 pages (see here), (1 page being deleted). I like to create articles from historic work on old sources, for instance simple:Annie van de Blankevoort, simple:1928 Belgium–Netherlands women's athletics competition, simple:Julia Beelaerts van Blokland, simple:Esther Bekkers-Lopes Cardozo or the event simple:Water polo at the 1922 Women's Olympiad that is barely mentioned at the English 1922 Women's Olympiad. Around 100 pages have been (literally) copied to the English Misplaced Pages by several users. I'm also editing Wikidata, see here and here when I forgot to log in.
However, as I have learned from it, I will never use multiple accounts anymore and adding controversial content without doing a proper fact-check. I will always listen to users, be constructive and be friendly. I will make sure you will not regret giving me my account back. I would like to work under the account user:SportsOlympic.
Significa liberdade (she/her) (talk) 18:12, 15 December 2024 (UTC)
- Support unbanning and unblocking per WP:SO. voorts (talk/contributions) 18:31, 15 December 2024 (UTC)
- Quoting my SPI comment in 2022:
That sentiment is what I eventually wrote down at User:Tamzin/Adverse possession unblock, which mentions the same principles being relevant in unban discussions. And now that this is before the community, with even more time having passed, I have no problem unbanning: The post-ban edits, while problematic in that they were sockpuppetry, do show evidence that Sander has learned from his mistakes, and thus a ban no longer serves a preventative purpose. Looking back at the one hesitation I mentioned above, I think my concern was that it was an ECR violation that seemed credulous of a pro-Russian narrative; but if there's no evidence of that being part of any POV-pushing, then I don't see it as an obstacle to unbanning. -- Tamzin (they|xe|🤷) 18:33, 15 December 2024 (UTC)I was torn on this. The IP does not seem to be creating the sort of low-quality BLP stubs that SportsOlympic was. If this were "just" a case of block evasion, I'm not sure I could justify a block of the IP as preventative of any disruption, and would be inclined to either ignore it or block but offer a non-OFFER unblock to the main account. However, Sander.v.Ginkel is banned, and under the SportsOlympic account has caused significant disruption just six months ago. Evading a ban is an inherent harm, as it undercuts the community's ability to self-govern. Furthermore, it would be unfair to the community to allow someone to contribute content, particularly in a DS area as much of the IP's recent edits have been, without the community being on-notice of their history of significant content issues. (And there is still troubling content like Draft:Krupets.) I thus feel I would be defying the mandate the community has given me as an admin if I did anything but block here. ... FWIW, Sander, I could see myself supporting an OFFER unban down the line, although I'd recommend a year away rather than six months.
- Support per above.-- Deepfriedokra (talk) 18:37, 15 December 2024 (UTC)
- Endorse one account proviso. -- Deepfriedokra (talk) 20:28, 15 December 2024 (UTC)
- I'm a little bit concerned by the sockpuppetry returning earlier this year: Misplaced Pages:Sockpuppet investigations/Sander.v.Ginkel/Archive#18 April 2024. However, that is over 6 months ago. I would Support with the obvious proviso that the user be limited to 1 account and that IP editing may be scrutinized for evidence of WP:LOUTSOCK. — rsjaffe 🗣️ 20:16, 15 December 2024 (UTC)
- Support with provisions per above. Worth keeping a close eye on, but they seem to have understood the problems with their behavior and improved upon it. The Kip 07:07, 16 December 2024 (UTC)
- Support I've previously spoken in favor of the subject as well. X (talk) 09:15, 16 December 2024 (UTC)
- Oppose. "My biggest mistake that I copied-pasted content from articles to other articles, that led to a BLP violation. " That wasn't the biggest mistake by far. You made extremely negative claims about sportspeople based on internet rumors. Apart from this, the first article I checked on simple, , is way too close paraphrasing of the source. This has very sloppy writing, "He started his business alone 1980 built so his horse stable "Hexagon" in Schore. " is just nonsense. Copyvio/close paraphrasing seems to be a recurring problem, this has e.g. "Zwaanswijk is regarded as one of the most respected post-World War II visual artists of Haarlem and his work had a profound influence on the local art scene." where the source has "Piet Zwaanswijk was een van de meest gerespecteerde na-oorlogse beeldend kunstenaars van Haarlem. Zijn werk had een diepe invloed op de lokale kunstscene". I don't get the impression that the earlier issues have disappeared. Fram (talk) 11:45, 16 December 2024 (UTC)
- Support User seems to have recognized what he did wrong, has edited constructively off enwiki. JayCubby 18:52, 17 December 2024 (UTC)
Weak Support, the crux of the issue was three-fold: creation of low-quality sports stubs (including what Fram said), persistent IDHT when asked to fix them, and sockpuppetry. I recall I identified the SportsOlympic sock in a tangential ANI thread a couple of years ago. It appears he has edited constructively elsewhere. I would like to see a commitment to one-account-only and a commitment respond civilly and collaboratively when criticized. Jip Orlando (talk) 15:45, 18 December 2024 (UTC)
- Oppose, I am convinced by the further discussion below that S.v.G is not a net positive at this time. Jip Orlando (talk) 14:11, 24 December 2024 (UTC)
- Support. Completely support an unblock; see my comment here when his IP was blocked in April. BeanieFan11 (talk) 17:25, 18 December 2024 (UTC)
- Oppose. Sander and his socks created literally thousands of poorly-written and/or potentially-copyvio pages on (very frequently) non-notable sports topics. I don't see evidence in his Simple Wiki contribs that his writing has improved, and for someone with his history of non-notable subject choices I would want to see clear evidence that these creations are supported by WP:SUSTAINED, non-routine, IRS SIGCOV. Articles like this may well be on notable competitions, but with content like
On 20 March the Women's Fencing Club gave an assaut, in honor of the visit of the Dutch team. As seen as an exceptional, mr. de Vos was a the only man allowed to visit the women's club.
, and all sources being from 20 or 21 March 1911, we can be confident that verifying and rewriting the mangled translations and searching for continued coverage will be a huge pain for other editors. And going from the most recent en.wp AfD participation I'd also anticipate the same combativeness and time wasted explaining P&Gs to him in that area as well. Given the volume of his creations, I don't think it is fair to foist all the extra work that would come with overturning the ban onto other editors without a much more thorough evaluation of his Simple Wiki contribution quality. JoelleJay (talk) 02:34, 19 December 2024 (UTC) - Currently oppose; open to a change of view if some explanation and assurances are given with regard to the points Fram raises. There is no point in unblocking a problematic editor if it appears that they may well continue to cause issues for the community ~ Lindsay 12:59, 19 December 2024 (UTC)
- Support but keep an eye on contributions off ENWP. Ahri Boy (talk) 17:11, 23 December 2024 (UTC)
- @Ahri Boy: Not sure we are concerned with contribs off ENWP. -- Deepfriedokra (talk) 18:27, 23 December 2024 (UTC)
- He might appeal on Commons later if the appeal here is successful, so there would be a cooldown before doing there. Ahri Boy (talk) 01:15, 24 December 2024 (UTC)
- @Ahri Boy: Not sure we are concerned with contribs off ENWP. -- Deepfriedokra (talk) 18:27, 23 December 2024 (UTC)
- Oppose per Fram on close paraphrasing, JoelleJay on sourcing/writing quality, and my own observations on English-language proficiency (I see very recent sentences like "Next as working for magazines he also contributed to book"). At an absolute minimum I would need a restriction on article creation (to prevent the low-quality mass creation issues from recurring), but these issues would be a problem in other areas too. I think continuing to contribute to simple-wiki and nl-wiki would be the best way forward. Extraordinary Writ (talk) 01:34, 24 December 2024 (UTC)
- He was once blocked on NLWP for the same sockpuppetry as here before. I don't even know that he may be offered SO there. Ahri Boy (talk) 10:16, 24 December 2024 (UTC)
- Oppose. Like Fram, JoelleJay, and Extraordinary Writ, I have concerns about their competence with regards to copyright, notability, and simple prose writing. I think an unblock is likely to create a timesink for the community, who will be forced to tie one eye up watching both of his hands. ♠PMC♠ (talk) 08:41, 24 December 2024 (UTC)
- Come on – it's been nearly seven years since the ban – why can't we give another chance? His articles from when he was an IP seemed quite good (and much different from stubs which seem to have been the problem), from what I remember (although they've since been G5'd). BeanieFan11 (talk) 16:35, 24 December 2024 (UTC)
- S.v.G. needs to be reevaluated. He needs to clarify that the purpose of return is genuine, constructive, and one account only. He hasn't made any contributions to Commons because he was blocked. Ahri Boy (talk) 19:55, 24 December 2024 (UTC)
- I think saying that
I will never use multiple accounts anymore
and that he wants tomake constructive content
would indicate thatthe purpose of return is genuine, constructive, and one account only.
BeanieFan11 (talk) 19:59, 24 December 2024 (UTC)- For the meantime, he should stay at Simple and NLWP for another six months to make sure no suspicions will be made before appealing under SO. Ahri Boy (talk) 20:07, 24 December 2024 (UTC)
- I think saying that
- But it's only been three years since he was mass-creating non-notable stubs with BLP violations and bludgeoning AfDs with his SportsOlympic sock. He then edited extensively as an IP, got banned for 18 months, restarted within two weeks of that ban ending, and made another 1000+ edits until his latest IP ban in spring 2024. After which he immediately invoked the (laxer) equivalent of the SO on nl.wp... JoelleJay (talk) 21:07, 24 December 2024 (UTC)
- And he admits that he was
too focused on quantity, rather than quality
, apologized repeatedly, and his creations as an IP showed that he was no longer focused onmass-creating non-notable stubs
. BeanieFan11 (talk) 21:18, 24 December 2024 (UTC)
- And he admits that he was
- S.v.G. needs to be reevaluated. He needs to clarify that the purpose of return is genuine, constructive, and one account only. He hasn't made any contributions to Commons because he was blocked. Ahri Boy (talk) 19:55, 24 December 2024 (UTC)
- Support With the above mentioned provisions. Seems like a genuine, good faith, attempt to start over. Frank Anchor 04:44, 25 December 2024 (UTC)
- Support - Like a lot of behavioral issues on this site, I think it all stems back to the general public seeing this site as an all-inclusive encyclopedia and some users here seeing the site as a celebrity encyclopedia. If the user becomes a problem, action can be taken again. Let's see how it goes. KatoKungLee (talk) 20:03, 25 December 2024 (UTC)
- Oppose per Fram and PMC. —Compassionate727 18:52, 29 December 2024 (UTC)
- Question: Is SvG the same person as Slowking4? There has been an odd connection between the two in the past; I think it was first noted by Dirk Beetstra. ☆ Bri (talk) 22:58, 29 December 2024 (UTC)
- Support. This appears to be a good-faith attempt at a return, and looking through the commentary here I don't see evidence to suggest continuing the ban and block are preventative. - The Bushranger One ping only 23:44, 4 January 2025 (UTC)
- Oppose basically per JoelleJay, particularly the evidence that their MASSCREATE/socking/evading behaviour was carrying on as recently as spring 2024. If/When they return, it should be with the requirement that all their articles have to go through AFC and that they won't get WP:AUTOPATROLLED without a substantive discussion (i.e., no automatic conferring of autopatrolled - they have to request it and disclose why this restriction is in place when doing so). FOARP (talk) 16:46, 8 January 2025 (UTC)
- It does look like a good-faith desire to return and work on Misplaced Pages. And I would just want to add that Misplaced Pages needs such a fruitful article creator. Especially since WP:NSPORT was severely trimmed several years ago, and probably thousands of sportspeople articles have since been deleted.
Support. (I am not an admin, so I am not sure I can vote. I can see some non-admins voting, but I'm still not sure.) --Moscow Connection (talk) 14:26, 10 January 2025 (UTC) - Conditional support unblock (non-admin vote- if I'm not allowed to vote then please just unbold this vote): add editing restriction for them to use WP:AFC for article creation, and this restriction can be reviewed in 6-12 months if their article creation has been good. Their article mass creation required one of the largest cleanup jobs I have seen on here, and we certainly wouldn't want the same mass-created quasi-notable articles created again. Joseph2302 (talk) 17:05, 10 January 2025 (UTC)
- Support I can't repeat what Beaniefan11 say enough: "Come on – it's been nearly seven years since the ban – why can't we give another chance? And he admits that he was
too focused on quantity, rather than quality
, apologized repeatedly, and his creations as an IP showed that he was no longer focused onmass-creating non-notable stubs
." This should assuage any doubt in the mind of the reviewing administrator. Kenneth Kho (talk) 15:01, 13 January 2025 (UTC) - Oppose Claims of "It's been seven years!" fall on deaf ears when you find out he's been socking all along and as recently as a year ago. Fram and PMC have good points as well. Show some restraint and understanding of your block and WP:SO is yours. Buffs (talk) 23:11, 17 January 2025 (UTC)
Spider-Man: Beyond the Spider-Verse - draft article about a future film seems to be a long-term draft
I have not come across a situation like Draft:Spider-Man: Beyond the Spider-Verse before. Maybe this is fairly common and I have just missed it.
It is a draft article about a film that can not have an article, per WP:NFF. I think the idea is that there is some valuable content there and it would be a shame to delete it when it seems likely that the film will enter final animation and voice recording in the next year or so.
The problem is that it is attracting the sort of speculative edits from IPs that we want to avoid. Both on the draft and the talk page.
I became aware of this because there is a request at WP:RPPI to EC-protect the talk page. But it makes me think we should have some kind of protection for the draft too. But I can see arguments for weaker than ECP (speculation is just by IPs) and for stronger... like... why are people editing it anyway? Maybe there are reasons I am not aware of.
Is anyone more familiar with how we got here? Anyone got any arguments for or against applying semi, EC or full protection to the draft and its talk page?
Edit: Anyone got any thoughts on the concept of having a draft article for a film that doesn't meet WP:NFF?
Yaris678 (talk) 00:39, 29 December 2024 (UTC)
- As far as I'm aware, articles on films are allowed so long as principal photography has occurred (principal animation in this case, I guess?). That has clearly happened for this film, even if they are having to scrap and re-write things. And notability is certainly not in question, so having an article is fully within the policy rules. If there are harmful edits happening, then semi-protection seems like a normal response. Silverseren 00:43, 29 December 2024 (UTC)
- People say that on the draft's talk page every so often and get rebuffed. Maybe you can be more persuasive, but the general argument is the existing animation was created for "Spider-Man: Across The Spider-Verse" before it was split into two films and no "final animation" has begun on this film. Yaris678 (talk) 01:03, 29 December 2024 (UTC)
- Are they basing that claim on any reliable source as evidence? Since what exists in that draft currently with reliable sources clearly indicates work has started. Silverseren 01:11, 29 December 2024 (UTC)
- Hi. I'm the editor who has requested the protection for this draft. Per WP:NFF, final animation or voice recording are the requirement to move a film draft to the mainspace. Final animation is different from standard reels being produced, which as sourced, is currently what this film has produced while no voice recording has occurred. It seems to still be very early in development, and much of the earlier work when this was the second part was reportedly scrapped (as sourced in the draft). I do not believe the mainspace viability ought to be discussed here as that is more for the draft. As for the protection request, it appears to be the same person making these disruptive comments which have become unnecessarily excessive and are detracting from the content of the draft itself. I requested protection (initially as ECP though semi works for the talk) because these comments have not benefitted any actual constructive progress and have largely ranged from the IPs attempting to enforce their own opinions about the delays and trying to remove sources they don't like, which has been ongoing since the end of October. As a draft, not many other editors are editing this, so it becomes quite unrelenting and tiresome to deal with these repeated disruptions. Glad to see this has garnered more attention. Trailblazer101 (talk) 01:20, 29 December 2024 (UTC)
Per WP:NFF, final animation or voice recording are the requirement to move a film draft to the mainspace
...I'm pretty sure that BtSV meets WP:GNG already, regardless of the state of production, and that should be the main factor. - The Bushranger One ping only 03:49, 29 December 2024 (UTC)- I have no problem with the draft being moved, this is just not the normal route to do so and typically NFF is followed for film articles, but I digress. I do caution that this article could be susceptible to further unconstructive comments in the mainspace, but that is a price I'm willing to handle. I can make the move as needed, no worries, I am primarily concerned about these type of comments continuing and if any protection is necessary to prevent or temporarily postpone them from continuing. Trailblazer101 (talk) 05:18, 29 December 2024 (UTC)
- Hi. I'm the editor who has requested the protection for this draft. Per WP:NFF, final animation or voice recording are the requirement to move a film draft to the mainspace. Final animation is different from standard reels being produced, which as sourced, is currently what this film has produced while no voice recording has occurred. It seems to still be very early in development, and much of the earlier work when this was the second part was reportedly scrapped (as sourced in the draft). I do not believe the mainspace viability ought to be discussed here as that is more for the draft. As for the protection request, it appears to be the same person making these disruptive comments which have become unnecessarily excessive and are detracting from the content of the draft itself. I requested protection (initially as ECP though semi works for the talk) because these comments have not benefitted any actual constructive progress and have largely ranged from the IPs attempting to enforce their own opinions about the delays and trying to remove sources they don't like, which has been ongoing since the end of October. As a draft, not many other editors are editing this, so it becomes quite unrelenting and tiresome to deal with these repeated disruptions. Glad to see this has garnered more attention. Trailblazer101 (talk) 01:20, 29 December 2024 (UTC)
- Are they basing that claim on any reliable source as evidence? Since what exists in that draft currently with reliable sources clearly indicates work has started. Silverseren 01:11, 29 December 2024 (UTC)
- People say that on the draft's talk page every so often and get rebuffed. Maybe you can be more persuasive, but the general argument is the existing animation was created for "Spider-Man: Across The Spider-Verse" before it was split into two films and no "final animation" has begun on this film. Yaris678 (talk) 01:03, 29 December 2024 (UTC)
- There doesn't appear to be enough disruption to the draft page to justify protection at this point. Draft talk definitely should get semi-protection. voorts (talk/contributions) 00:45, 29 December 2024 (UTC)
- Really? That seems excessive for a few FOURMy IP comments (likely from the same person). If they continue with it, block the IP, maybe. Protecting talk pages should really be a last resort. Elli (talk | contribs) 00:58, 29 December 2024 (UTC)
- Some people overly use NFF to block any film article that has not confirmed start to production, which is really a bad black/white approach. Most films prior to production are not notable or may not even happen when they are first hinted at, and thus it is absolutely appropriate to use NFF to hold back on a standalone until production starts. But then you have some exceptional cases like this (the 3rd of the animated Spider-Man movies that have earned a massive amount of money and praise, with a lot of attention already given to the film even before production) as well as my own experience with Akira (planned film) which deals with a film that has numerous delays and other incidents that its still nowhere close to production, but its journey that way is readily sourced. NFF should not be used to block creation of articles on films that have this much detail about the work that is otherwise suitable by notability guidelines. For this specific article on the Spider-man film, I see no reason why it could not be in main space at this point as to avoid the whole draft problem. — Masem (t) 05:32, 29 December 2024 (UTC)
- Yeah, there is a point to be made that even if this final film somehow never finished production, it would still be notable because of the coverage of its attempted production history. There's several films (and video games, among other cultural apocrypha) that meet that notability requirement, even without ever actually having been completed and released to the public. Silverseren 05:36, 29 December 2024 (UTC)
- Indeed, a number of aborted films projects are notable exactly because they wound up in development hell. Jodorowsky's Dune is a film about my personal favorite never-got-made film. El Beeblerino 02:59, 30 December 2024 (UTC)
- Yeah, there is a point to be made that even if this final film somehow never finished production, it would still be notable because of the coverage of its attempted production history. There's several films (and video games, among other cultural apocrypha) that meet that notability requirement, even without ever actually having been completed and released to the public. Silverseren 05:36, 29 December 2024 (UTC)
Noting here that Trailblazer101 moved the article from draft space to main space at 22:44, based on the discussion here and WP:GNG. I have not seen any objections to that move since it was done. I have not seen any more speculative or forumy edits recently. There is a good chance they will come back, but if they come back in a serious number the article and/or talk page can be given an appropriate level of protection at that point, or, if the responsible IPs/accounts can be blocked. I think it is probably time to close this discussion. Yaris678 (talk) 10:56, 30 December 2024 (UTC)
- The IP has made three unconstructive and uncivil comments on the talk today (see this diff, and they show no signs of stopping. Trailblazer101 (talk) 18:03, 31 December 2024 (UTC)
- I have blocked that IP. I note that it is possible that some of the other IPs could be the same users and so will block other IPs and/or apply semi-protection if this continues (or encourage others to do the same if I am away from my computer). Yaris678 (talk) 11:51, 1 January 2025 (UTC)
Anyone got any thoughts on the concept of having a draft article for a film that doesn't meet WP:NFF?
Using draftspace to incubate articles on subjects that are not yet notable but almost certainly will be—unreleased films, upcoming elections, sports events, the next in an "X by year" series, and so on—is a common practice and has been as long as I can remember. As such it's listed at WP:DRAFTREASON. – Joe (talk) 12:04, 1 January 2025 (UTC)- Thank you. Yaris678 (talk) 15:01, 1 January 2025 (UTC)
I think it makes sense to archive all threads in Talk:Spider-Man: Beyond the Spider-Verse. They are all either forumy or else asking when the page can be moved to article space, which is no longer relevant since it is in article space. Yaris678 (talk) 20:06, 3 January 2025 (UTC)
- I've updated the archive bot on that talk age to act on 1 month old threads. Should get rid of half of the ones on there when it runs next and the rest will follow soon enough. I've always thought 6 months was way too long of a default archive policy. Silverseren 20:11, 3 January 2025 (UTC)
- Yeah, I've always felt 90 days is sufficient for default archival purposes. If no one has contributed to a discussion in three months, it's a dead discussion. — The Hand That Feeds You: 18:41, 10 January 2025 (UTC)
43.249.196.179 (again)
See their previous thread here, Misplaced Pages:Administrators' noticeboard/IncidentArchive1174#User:Augmented Seventh. Continuing to disrupt and remove categories without explanation, decided to gravedance on my page after restoring edits without any talk page discussion, and has now moved onto disrupting user sandboxes and user pages by removing categories without said user's permission, calling my reversions 'vindicitive' and now considering me their personal 'nemesis' because they don't understand why they're being reverted. Nate • (chatter) 21:16, 31 December 2024 (UTC)
- User:MrSchimpf is not familiar with some of the WP policies and guidelines especially WP:UOWN and WP:CAT. Also, his obfuscated username is somewhat fustration and is not conducive to efficient editing. 43.249.196.179 (talk) 21:21, 31 December 2024 (UTC)
- Special:Diff/1266485663: Editing user pages has no 'hard policy' prohibition, as this is a wiki. 'End of discussion', seriously? Also see WP:NOBAN. Then, Category:Wikipedians is a container category, which clearly says it should only contain subcategories. Even I don't understand why they're being reverted. -- zzuuzz 22:08, 31 December 2024 (UTC)
- User:MrSchimpf seems to be unaware of many of the WP polices and guidelines. 43.249.196.179 (talk) 08:03, 3 January 2025 (UTC)
- I've been here nineteen years so obviously I do and I apologize if as mentioned I'm more aggressive about userspace being in control of the user themselves. That said I'm no longer engaging with you or any of your edits as you're now refusing to drop the stick and trying to troll some kind of response out of me (and doing the same for Liz, who has the patience of a saint), which you won't get. Understand our guidelines or get blocked. If anyone uninvolved would like to close this, please do so. Nate • (chatter) 17:16, 3 January 2025 (UTC)
- Length of time on WP is not a measure of how familiar an editor is with policy and guidelines. Your previous comments show that you are unfamiliar with some of them, but to be fair, it is impossible to know all of them. There are a lot of editors that do not know a lot of the policies and guidelines. THere are content disputes and corrections and reverts happening all the time because of inexperienced editors.
- I am not trolling. I just want WP to be much better than it currently is. 43.249.196.179 (talk) 19:50, 3 January 2025 (UTC)
- I've been here nineteen years so obviously I do and I apologize if as mentioned I'm more aggressive about userspace being in control of the user themselves. That said I'm no longer engaging with you or any of your edits as you're now refusing to drop the stick and trying to troll some kind of response out of me (and doing the same for Liz, who has the patience of a saint), which you won't get. Understand our guidelines or get blocked. If anyone uninvolved would like to close this, please do so. Nate • (chatter) 17:16, 3 January 2025 (UTC)
- Adressing that final point, I have made a proposal about Category:Wikipedians to either remove the container banner tag or give special sanction to empty user pages from that main category. Tule-hog (talk) 21:08, 3 January 2025 (UTC)
- Category:Wikipedians is at a level of the hierarchy that there should be nothing in it, which is why it is a container category. The contents of it have been added by editors who do not understand how WP works and do not realise that it is a container category. You proposal is not needed. 43.249.196.179 (talk) 22:07, 3 January 2025 (UTC)
- User:MrSchimpf seems to be unaware of many of the WP polices and guidelines. 43.249.196.179 (talk) 08:03, 3 January 2025 (UTC)
- Comment: WP:USERNOCAT was cited in this edit (a sandbox used for drafting a larger edit needing discussion, where categories were copied along with the rest of the article's content). (Category:Wikipedians is mentioned explicitly in that guideline.) Tule-hog (talk) 02:49, 1 January 2025 (UTC)
- Whatever the case, user sandbox space is sacred and unless you have permission to edit there, you don't touch them, that's an unwritten rule. Mathglot certainly didn't appreciate it. That's the main issue here and if I was wrong on the cats so be it, but they should not be playing in sandboxes they shouldn't be in. Nate • (chatter) 02:54, 1 January 2025 (UTC)
- Just to clarify: I have no qualms about others making improvements to pages in my users space—which belong to the community and are not "mine"—as long as they are improvements. That said, IP's edits in my userspace look like vandalism to me. Mathglot (talk) 03:04, 1 January 2025 (UTC)
- User namespace is not "sacred". And if there is an unwrittten rule then it is not a rule that needed to be adhered to. Also WP:BOLD. To be a good editor it is important to be familiar with policis and guidelines. 43.249.196.179 (talk) 08:03, 1 January 2025 (UTC)
- Whatever the case, user sandbox space is sacred and unless you have permission to edit there, you don't touch them, that's an unwritten rule. Mathglot certainly didn't appreciate it. That's the main issue here and if I was wrong on the cats so be it, but they should not be playing in sandboxes they shouldn't be in. Nate • (chatter) 02:54, 1 January 2025 (UTC)
- It was not a "gravedance". I was pointing out to you that other editors dont agree with you edits. 43.249.196.179 (talk) 09:15, 1 January 2025 (UTC)
I only just noticed this AN discussion, after placing this warning at User talk:43.249.196.179 about vandalizing a Draft template in my user space. Their edits seem somehow to be related to categories, but near as I can guess from their edit summary here, they also had some inscrutable complaint about me using my userspace as "social media". Maybe interested parties here will understand what they are talking about, because I certainly don't. As of this point, I cannot tell if they are well-meaning, but highly misinformed and uncomprehending, or if they are simply trolling everyone. I suspect the latter, but am willing to be proved wrong, especially if enceforth they stick to guidelines and talk things out, instead of ignoring advice given previously and edit-warring. Mathglot (talk) 03:00, 1 January 2025 (UTC)
- Okay, now I am sure: see this edit at my Talk page, quickly reverted by Remsense while I was in the process of reverting it. This is clearly intentional, malicious, vandalism, as well as retaliation. Therefore, I propose an indefinite block on 43.249.196.179 (talk · contribs) as it is a vandalism-only account. Mathglot (talk) 03:13, 1 January 2025 (UTC)
- I haven't looked into this editor's edits but we don't indefinitely block IP editors as the IP account can easily be assigned to a different user. But they can receive longtime blocks on the order of months or years. Liz 04:33, 1 January 2025 (UTC)
- You are looking at two different IP addresses. Getting things right is important. 43.249.196.179 (talk) 07:53, 1 January 2025 (UTC)
- Honestly, whether that was a Joe Job or not, your behavior is indistinguishable from trolling & deserves a block. — The Hand That Feeds You: 18:45, 10 January 2025 (UTC)
Incivility at Talk:Azerbaijan Airlines Flight 8243
@Dreameditsbrooklyn and to a lesser extent @Aviationwikiflight have been bickering in the talk page for a while now, and the reply chains are so long that they go off my phone's screen. DEB in particular has been noticeably passive aggressive in their comments, such as these diffs at me, this diff at AWF, and this diff at User:Awdqmb. Is this actionable? guninvalid (talk) 01:57, 2 January 2025 (UTC)
- This looks to me like it's covered by WP:ARBEE. Animal lover |666| 02:18, 2 January 2025 (UTC)
- I have yet to dig through the very length discussions, but on the surface I can say that I'm glad to see it not turning into much of an edit war in the article itself, and remaining mostly on the talk page. Infact the only person who breached 2R's was someone you didn't mention, and interestingly was never warned, but I placed a soft warning on their talk page. As far as the specific diffs provided, I don't see anything in there which is all that problematic, unless you're deeply intrenched in the issue. I would proffer is that if someone says, in it's entirety
I am stating a fact.
and you take offence to that, then you might need to back away from the discussion for a few days. TiggerJay (talk) 02:47, 2 January 2025 (UTC)"...then you might need to back away from the discussion for a few days".
You're probably right about that. guninvalid (talk) 02:58, 2 January 2025 (UTC)
- This seems entirely unnecessary. Dreameditsbrooklyn (talk) 03:13, 2 January 2025 (UTC)
- Can you elaborate on which aspect of
this
you are referring to that you believe is unnecessary? TiggerJay (talk) 03:55, 2 January 2025 (UTC)- By this, I mean bringing the issue to ANI. If I owe anyone an apology, I stand ready to give it, but @Guninvalid hasn't really been involved in the discussion until very recently and has already escalated it here. Dreameditsbrooklyn (talk) 03:59, 2 January 2025 (UTC)
- It doesn't matter how much someone has been involved in a discussion. If there's misconduct that's not clearly going to get resolved on its own (which I'm not confident saying either way here), then it's a public service, even a responsibility, for an editor to report it. Thebiguglyalien (talk) 05:58, 2 January 2025 (UTC)
- @Dreameditsbrooklyn you can see my initial assessment of the situation above. However, I will say uninvolved editors are welcome to bring valid concerns to ANI. It is often far more helpful when someone outside of the situation brings it up here as it ends up being far more neutral. I also would suggest that you might also be too involved right now and need to back away for a few days. The biggest reason is that I believe you read right past Animal lover's and my response which basically didn't find you doing anything wrong. I suggest that a cooling off period might be good for you as well. Not because you're currently doing anything wrong (because that conversation would look quite different), but rather that you're likely too invested in this topic right now to see rationally and objectively. TiggerJay (talk) 06:18, 2 January 2025 (UTC)
- It was not my intent to ignore those assessments, and I understand what you've said as far as uninvolved editors raising such issues (real or perceived). Dreameditsbrooklyn (talk) 19:26, 2 January 2025 (UTC)
- Also, as a note, this isn't ANI... - The Bushranger One ping only 07:09, 2 January 2025 (UTC)
- By this, I mean bringing the issue to ANI. If I owe anyone an apology, I stand ready to give it, but @Guninvalid hasn't really been involved in the discussion until very recently and has already escalated it here. Dreameditsbrooklyn (talk) 03:59, 2 January 2025 (UTC)
- Can you elaborate on which aspect of
- Infact I don't know why such a simple infobox change discussion will resulted in endless arguments. And it happened in mutiple pages, like this Voepass crash case, this Swiftair crash case, and now this Azerbaijan Airlines crash case there. And I'm afraid there would be other arguements in previous pages.
- But to be honest, I think I also have some responsibilities on this endless situation: I have known what to do to deal with such major changes, but I didn't really take any action. Awdqmb (talk) 07:14, 2 January 2025 (UTC)
- The whole "Accident vs Crash" thing has been going on for a while now. It pretty much goes nowhere every time. DEB gives a whole bunch of reasons why "accident" should be avoided, AWF gives a whole bunch of reasons why "accident" is perfectly fine, and it all repeats with every new WP:AIRCRASH article. I just recommended on DEB's talk page that they try to seek a wider consensus to break this endless cycle, because I for one am tired of seeing the same arguments over and over again with no progress. - ZLEA T\ 08:02, 2 January 2025 (UTC)
- Infact you can check the talkpage I provided, you will find such arguments have happened on mutiple pages. Awdqmb (talk) 08:09, 2 January 2025 (UTC)
- Since the regular editors in this topic area have proven that they are unable to resolve this utterly trivial terminology dispute among themselves, perhaps the best solution might be to topic ban every consistent advocate of "accident" and to topic ban every consistent advocate of "crash" from all articles about airplane mishaps, and let entirely uninvolved editors make a reasonable decision. Because endless bickering among entrenched advocates is disruptive. Topic bans could then be lifted on editors who explicitly agree to stop beating a dead horse and drop the terminology issue forever. Cullen328 (talk) 08:25, 2 January 2025 (UTC)
- It's less "unable to resolve" and more "Dreameditsbrooklyn argues that using 'accident' is original research because the sources use 'crash'" and I wish I was joking. Your modest proposal probably would get some kind of result though! - The Bushranger One ping only 08:27, 2 January 2025 (UTC)
- Infact I have already suggested to delete this controversial value on the talkpage of the template, since it have not much actural use to show, and mostly have the same contents with the "Summary" value. And ironically, it has showed the available value on the doc page, but the example they showed on simply violate it! But since then nobody really talk about it yet. Awdqmb (talk) 08:34, 2 January 2025 (UTC)
- As someone who has consistently been on the side "accident is fine" of this argument (there really isn't an "accident/crash" binary here, just whether "accident" is original research), I think that's a bit extreme. I laid out a plan to seek wider consensus on DEB's talk page, which should hopefully help resolve the issue once and for all without the need for more drastic measures. - ZLEA T\ 09:20, 2 January 2025 (UTC)
- Respectfully, the descriptions aren't trivial. A "crash" describes what happened. An "accident" implies someone made a mistake with no real culpability. An "incident" implies some sort of interaction or series of events. I have no specific dog in this fight and I don't believe I've voiced any significant opinion on the matter here or elsewhere, but such a description is not trivial when we are trying to be neutral in our descriptions. In this particular case, it very much appears that the act was deliberate and the airliner was acceptable collateral damage (in their opinion). At a minimum, it's disputed. As such, "accident" isn't appropriate as it is at least alleged to be a deliberate act or negligence. "Incident" or "crash" would be more neutral. If we say "accident" it implies no one should be blamed and fails WP:Neutral. Buffs (talk) 22:22, 2 January 2025 (UTC)
- If only it were that simple (the context of aviation has been explicitly excluded from at least one discussion on the matter). We could go over whether "accident" actually implies no culpability in the context of aviation all day, but this is not the place to do it. As I stated numerous times, we need to formally establish a project-wide consensus about this, and WT:AATF is a good place to start. As for this discussion, I think it can be closed as the issue in question is very minor. - ZLEA T\ 22:42, 2 January 2025 (UTC)
- WP:MOS says:
If any contradiction arises, this page has precedence.
- WP:AT, which follows MOS says:
Generally, article titles are based on what the subject is called in reliable sources.
- The very broad majority of RS call this a crash. Why, in this case, doesn't this apply? Because some editors disagree? I am honestly asking. I don't see a policy which overrules MOS here. Also, I'll hold off on any new discussions on this until things have concluded here and at the article talk page, where the same editor who started this discussion opened an RfC on the topic. Dreameditsbrooklyn (talk) 22:58, 2 January 2025 (UTC)
- I will not continue this off-topic discussion here. If the same perceived problem is happening across multiple WT:AATF articles, then the discussion needs to be moved there to finally end the cycle and come to a consensus. - ZLEA T\ 23:06, 2 January 2025 (UTC)
- I'm not sure WP:AATF is the correct venue to continue the discussion for a number of reasons, which I will spare going into here. Dreameditsbrooklyn (talk) 23:14, 2 January 2025 (UTC)
The very broad majority of RS call this a crash. Why, in this case, doesn't this apply?
Because simple issues of phraseology don't need to "follow the sources", and insisting that they do is WP:WIKILAWYERING. - The Bushranger One ping only 01:38, 4 January 2025 (UTC)- Others have rejected this as the venue to hold this debate, and I will too. I suggest you follow your own advice and drop the stick, at least for now. Dreameditsbrooklyn (talk) 02:06, 4 January 2025 (UTC)
- I'm not sure WP:AATF is the correct venue to continue the discussion for a number of reasons, which I will spare going into here. Dreameditsbrooklyn (talk) 23:14, 2 January 2025 (UTC)
- I will not continue this off-topic discussion here. If the same perceived problem is happening across multiple WT:AATF articles, then the discussion needs to be moved there to finally end the cycle and come to a consensus. - ZLEA T\ 23:06, 2 January 2025 (UTC)
- WP:MOS says:
An "accident" implies someone made a mistake with no real culpability
No, it does not. The International Civil Aviation Organization, which is somewhat of an authority on the matter, defines an 'aircraft accident' asAccident. An occurrence associated with the operation of an aircraft ..., in which: a) a person is fatally or seriously injured b) the aircraft sustains damage or structural failure c) the aircraft is missing or is completely inaccessible
. Notice what isn't there - anything about mistakes or culapbility. @Buffs: "Accident" is the official internationally recognized term for this sort of occurance, and is entirely neutral in use. Note that "incident" has a very specific term in aviation which is "an occurrence, other than an accident, associated with the operation of an aircraft that affects or could affect the safety of operation." @Dreameditsbrooklyn: I'd suggest you drop the stick and stop pushing this personal intrepretation. - The Bushranger One ping only 23:51, 2 January 2025 (UTC)- Why do you think this jargon use should take precedence over the common meaning of the word? The word "accident" can be used in (at least) two senses, one of which involves a lack of intention -- the fact that the ICAO (who?) says that they use the word "accident" in only one of these senses isn't somehow magically binding on everyone else who uses the word in the context of aviation. Given the choice between a word with two ambiguous senses, one of which inappropriate, and a word that has only one relevant sense, it's obvious that the latter word will be clearer, isn't it? 50.224.79.68 (talk) 04:12, 3 January 2025 (UTC)
- International Civil Aviation Organization. The people whose job it is to establish these things for aviation. It's not the use of one word for the other that I have a problem with. It's the argument that, somehow, using "accident" constitutes original research when in fact it is the correct terminology - and in fact some of the suggested alternatives are explicitly incorrect terminology - is the problem. And no, its not "magically binding", but common useage in the context of aviation is to refer to any crash as an "aviation accident", just like how if somebody deliberately rear-ends you in road rage it's still a "car accident" - it isn't WP:JARGON. - The Bushranger One ping only 09:25, 3 January 2025 (UTC)
- Do you think there was a car accident in New Orleans a few days ago? When you appeal to an organization like ICAO for what the meaning of a common word is, you are by definition using jargon. 2600:1700:47F8:800F:0:0:0:1BF7 (talk) 17:58, 3 January 2025 (UTC)
- When you appeal to an expert for the meaning of a word in the context of what it's being used in, that's common sense. - The Bushranger One ping only 21:59, 3 January 2025 (UTC)
- It’s the very definition of the word jargon! No wonder people are finding you impossible to deal with. 108.169.132.163 (talk) 18:57, 4 January 2025 (UTC)
- When you appeal to an expert for the meaning of a word in the context of what it's being used in, that's common sense. - The Bushranger One ping only 21:59, 3 January 2025 (UTC)
- What is "an occurrence, other than an accident..." if "accident" includes "incidents"? Definition you're claiming here doesn't make a lot of sense. Buffs (talk) 19:03, 3 January 2025 (UTC)
- Accident =/= incident, which I believed was clear. - The Bushranger One ping only 21:59, 3 January 2025 (UTC)
- Incident includes accidents AND intentional acts. Buffs (talk) 18:34, 4 January 2025 (UTC)
- Not according to the ICAO definition, but this probably is something best not continued here I reckon. - The Bushranger One ping only 18:40, 4 January 2025 (UTC)
- Incident includes accidents AND intentional acts. Buffs (talk) 18:34, 4 January 2025 (UTC)
- Accident =/= incident, which I believed was clear. - The Bushranger One ping only 21:59, 3 January 2025 (UTC)
- Do you think there was a car accident in New Orleans a few days ago? When you appeal to an organization like ICAO for what the meaning of a common word is, you are by definition using jargon. 2600:1700:47F8:800F:0:0:0:1BF7 (talk) 17:58, 3 January 2025 (UTC)
- International Civil Aviation Organization. The people whose job it is to establish these things for aviation. It's not the use of one word for the other that I have a problem with. It's the argument that, somehow, using "accident" constitutes original research when in fact it is the correct terminology - and in fact some of the suggested alternatives are explicitly incorrect terminology - is the problem. And no, its not "magically binding", but common useage in the context of aviation is to refer to any crash as an "aviation accident", just like how if somebody deliberately rear-ends you in road rage it's still a "car accident" - it isn't WP:JARGON. - The Bushranger One ping only 09:25, 3 January 2025 (UTC)
- Why do you think this jargon use should take precedence over the common meaning of the word? The word "accident" can be used in (at least) two senses, one of which involves a lack of intention -- the fact that the ICAO (who?) says that they use the word "accident" in only one of these senses isn't somehow magically binding on everyone else who uses the word in the context of aviation. Given the choice between a word with two ambiguous senses, one of which inappropriate, and a word that has only one relevant sense, it's obvious that the latter word will be clearer, isn't it? 50.224.79.68 (talk) 04:12, 3 January 2025 (UTC)
- I did not bring this up to WP:AN to litigate whether to use "crash" or "accident". If you would like to litigate that, I have started a RfC on the Talk page. I brought this here to ask the admins to discuss whether DEB's and AWF's behavior is worth pursuing administrator action. guninvalid (talk) 01:09, 3 January 2025 (UTC)
- If only it were that simple (the context of aviation has been explicitly excluded from at least one discussion on the matter). We could go over whether "accident" actually implies no culpability in the context of aviation all day, but this is not the place to do it. As I stated numerous times, we need to formally establish a project-wide consensus about this, and WT:AATF is a good place to start. As for this discussion, I think it can be closed as the issue in question is very minor. - ZLEA T\ 22:42, 2 January 2025 (UTC)
- Since you think this is an "utterly trivial terminology dispute" should I tag you in the RFC at WP:RS when I make it, or not? I don't wish to bother you if it's not important to you. Dreameditsbrooklyn (talk) 22:31, 3 January 2025 (UTC)
- Since the regular editors in this topic area have proven that they are unable to resolve this utterly trivial terminology dispute among themselves, perhaps the best solution might be to topic ban every consistent advocate of "accident" and to topic ban every consistent advocate of "crash" from all articles about airplane mishaps, and let entirely uninvolved editors make a reasonable decision. Because endless bickering among entrenched advocates is disruptive. Topic bans could then be lifted on editors who explicitly agree to stop beating a dead horse and drop the terminology issue forever. Cullen328 (talk) 08:25, 2 January 2025 (UTC)
- Infact you can check the talkpage I provided, you will find such arguments have happened on mutiple pages. Awdqmb (talk) 08:09, 2 January 2025 (UTC)
- The whole "Accident vs Crash" thing has been going on for a while now. It pretty much goes nowhere every time. DEB gives a whole bunch of reasons why "accident" should be avoided, AWF gives a whole bunch of reasons why "accident" is perfectly fine, and it all repeats with every new WP:AIRCRASH article. I just recommended on DEB's talk page that they try to seek a wider consensus to break this endless cycle, because I for one am tired of seeing the same arguments over and over again with no progress. - ZLEA T\ 08:02, 2 January 2025 (UTC)
- I know this discussion is about conduct, not about the disagreement which prompted it, but I'll note that the other user named here and who has not responded has since changed several instances of the word 'crash' to accident on other entries and has also since been accused of violating 3RR on the very entry which prompted this discussion. I've agreed to confine any further conversations to the talk page until a consensus is reached, wherever that may be. Dreameditsbrooklyn (talk) 02:46, 3 January 2025 (UTC)
- On the very entry for a completely different reason regarding the use of the Aviation Safety Network but I concede that whilst I was within the limits of 3RR, it probably shouldn't have gotten to that point in the first place.
... since changed several instances of the word 'crash' to accident on other entries
– The only changes made were either related to a change within the infobox to stay consistent with Template:Infobox aircraft occurrence as the occurrence type on the aforementioned article statedAirliner crash
, or related to changes regarding short descriptions since they were changed to be phrased in a way that is not usually done. It's not like I removed every single mention of the word crash and replaced it with accident. But back to the main topic, I'm willing to drop the issue as long as it's not an problem to use accident in articles relating to aviation. Aviationwikiflight (talk) 03:40, 3 January 2025 (UTC)
- On the very entry for a completely different reason regarding the use of the Aviation Safety Network but I concede that whilst I was within the limits of 3RR, it probably shouldn't have gotten to that point in the first place.
Can we close this? The current discussion has next to nothing to do with the original issue and is best continued somewhere else. - ZLEA T\ 19:03, 4 January 2025 (UTC)
- Agreed. An admin got involved and simply continued off-topic discussion. guninvalid (talk) 21:33, 4 January 2025 (UTC)
- Warn both to drop the stick, otherwise, no action at this point. FOARP (talk) 15:57, 8 January 2025 (UTC)
- Hands FOARP two trouts You want to hand them out, or me? Buffs (talk) 16:32, 9 January 2025 (UTC)
Topic ban appeal
There is consensus against lifting the topic ban at this time. DesertInfo is advised to find areas where they are willing to edit to show a better history prior to revisiting the topic ban in the future. Star Mississippi 15:07, 12 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
Hello, I have a topic ban that is approaching one year old on "undiscussed moves, move discussions, deletion discussions, and racial issues broadly construed (including topics associated with the Confederate States of America)". I would like an opportunity to contribute to these topics again. I have been fairly inactive since then but I have edited a few articles without issue. Thank you. DesertInfo (talk) 04:36, 3 January 2025 (UTC)
- I'll kick off by asking the standard two questions: (1) please explain in your own words why you were topic banned; (2) do you have anything to say to convince everyone those same issues won't occur again? WaggersTALK 14:01, 3 January 2025 (UTC)
- I was topic banned for not assuming good faith and making an allegation that someone was using a sockpuppet when I was unable to provide substantial evidence. The topic ban was appealable after 3 months but I stepped away for almost a year. I am ready to discuss these topics respectfully and understand the importance of patience and communication. ANI should be a last resort. DesertInfo (talk) 18:29, 3 January 2025 (UTC)
- Can you provide a link to the discussion where this topic ban was imposed? Thank you. Liz 04:05, 4 January 2025 (UTC)
- Found it. Misplaced Pages:Administrators' noticeboard/IncidentArchive1097#Desertambition's hostile edit history. Tarlby 04:35, 4 January 2025 (UTC)
- Thank you. That is helpful to have. Liz 07:19, 4 January 2025 (UTC)
- Found it. Misplaced Pages:Administrators' noticeboard/IncidentArchive1097#Desertambition's hostile edit history. Tarlby 04:35, 4 January 2025 (UTC)
- Can you provide a link to the discussion where this topic ban was imposed? Thank you. Liz 04:05, 4 January 2025 (UTC)
- I support lifting the ban. DI's talk page makes for interesting reading, it shows quite a remarkable change in attitude over a period of a few years, and I believe that's genuine. WaggersTALK 08:58, 6 January 2025 (UTC)
- I was topic banned for not assuming good faith and making an allegation that someone was using a sockpuppet when I was unable to provide substantial evidence. The topic ban was appealable after 3 months but I stepped away for almost a year. I am ready to discuss these topics respectfully and understand the importance of patience and communication. ANI should be a last resort. DesertInfo (talk) 18:29, 3 January 2025 (UTC)
- Oppose lifting the topic ban I think being warned for making edits that violating a topic ban, then being almost completely inactive for six months, and then coming back and asking for it to be lifted and that passing sets a horrible example. * Pppery * it has begun... 06:31, 7 January 2025 (UTC)
- It seemed like a good idea to step away from the site for a time. I was receptive to the warning, even though it was not from an admin, and stopped editing in that area entirely. These are the edits in question: I just forgot that I had to appeal the topic ban here first and haven't gotten around to it until now. It should be noted that the first edit merely restored a previous RFC that had been ignored and the last two were minor changes to articles that have since been restored.
- I have never made a different account or tried to dishonestly avoid the topic ban and I never will. All I ask is that you WP:AGF and give me a chance to show that I can contribute collaboratively and have matured. DesertInfo (talk) 21:51, 7 January 2025 (UTC)
- Only 106 edits since unblocking (including the unblocking), of which includes apparently no edits to article talkpages, which is where a lot of the issues emerged. There's not much to really evaluate change. CMD (talk) 07:24, 7 January 2025 (UTC)
- I have largely avoided getting involved in article talk pages in order to avoid violating the topic ban. If I were to get involved in these topics to demonstrate change, it would be in violation of the topic ban. Seems like a catch-22. DesertInfo (talk) 20:51, 7 January 2025 (UTC)
- There are literally millions of articles and talk pages not covered by your topic ban. You are expected to demonstrate change there. Why on earth do you think this makes it a catch-22 situation?!? --Yamla (talk) 22:06, 7 January 2025 (UTC)
- I have made plenty of edits to articles like Caribbean Basin, List of current detainees at Guantanamo Bay, Venezuelan Caribbean, and List of archipelagos in the meantime without issue, there was no need to discuss it on the talk page. I have tried to make clear edit summaries and contribute to the encyclopedia. DesertInfo (talk) 22:45, 7 January 2025 (UTC)
- There are literally millions of articles and talk pages not covered by your topic ban. You are expected to demonstrate change there. Why on earth do you think this makes it a catch-22 situation?!? --Yamla (talk) 22:06, 7 January 2025 (UTC)
- I have largely avoided getting involved in article talk pages in order to avoid violating the topic ban. If I were to get involved in these topics to demonstrate change, it would be in violation of the topic ban. Seems like a catch-22. DesertInfo (talk) 20:51, 7 January 2025 (UTC)
- Oppose lifting the topic ban. As per Chipmunkdavis, there have been very few edits since the unblock in February 2024. Although DesertInfo says "I have made plenty of edits", I just don't see enough here to justify lifting the topic ban. I'll also note that at least some of these edits came close to violating the topic ban (see User_talk:DesertInfo#Topic_ban for example). --Yamla (talk) 23:02, 7 January 2025 (UTC)
- Oppose at this time I appreciate that you walked away rather than risk violating the ban. that shows some recognition of the issue and willingness to try and do something about it. However, what we would want to see would be a decent track record of editing over a sustained period without any hint of violating the ban, and you are just not there yet. Beeblebrox 23:15, 7 January 2025 (UTC)
- I have edited multiple articles without issue. I don't understand why I would edit articles I'm not interested in/knowledgeable about. I don't want to add useless info or talk page comments for the sake of adding it. I have tried to contribute to articles I know something about. The topic ban is very broad and could reasonably be argued to cover most history/politics subjects.
- I made a genuine mistake half a year ago that was not egregious and did not violate the topic ban, only coming close. When reminded of the topic ban, I stopped immediately. The topic ban was appealable after 3 months. I was told to step away from editing entirely for a long period of time and I did:
- This ban has been in place been in place since 2022, over 3 years. A lot has changed and I have matured greatly. DesertInfo (talk) 23:36, 7 January 2025 (UTC)
- The topic ban is not so broad as to cut off most of en.wiki. Aside from the move and deletion restrictions, which are technical and do not restrict editing from any particular page, the topic ban is just "racial issues broadly construed". Do you really feel that this covers every article you are either interested in or knowledgeable about? Do you really feel you can't participate in talkpages without infringing on this? CMD (talk) 01:50, 8 January 2025 (UTC)
- I would like to participate in move and deletion discussions. I contributed a lot to List of renamed places in South Africa and I would like to update some place names through move requests. I haven't had issues in that area since 2022. DesertInfo (talk) 05:24, 12 January 2025 (UTC)
- The topic ban is not so broad as to cut off most of en.wiki. Aside from the move and deletion restrictions, which are technical and do not restrict editing from any particular page, the topic ban is just "racial issues broadly construed". Do you really feel that this covers every article you are either interested in or knowledgeable about? Do you really feel you can't participate in talkpages without infringing on this? CMD (talk) 01:50, 8 January 2025 (UTC)
- Comment - I'd say
"racial issues broadly construed"
is actually pretty broad given how much of history/geography is touched by it. I'd also say they do appear to have made an effort to improve, though I'd still like to see more. FOARP (talk) 16:03, 8 January 2025 (UTC) - Oppose I want to see some real world effort working collaboratively somewhere else on wp, not just a six month gap waiting it, off wikipedia. There is no evidence here that there has been a change. scope_creep 08:26, 11 January 2025 (UTC)
Andra Febrian report
HiLux duck has been blocked, and no further action is needed here. Star Mississippi 15:10, 12 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
"Andra Febrian" is disrupting many edits, I have seen many deleted edits by this user, and I would like to report the user for causing many edit wars. The edits unreasonably reverted by this user is very disruptive to me, as I only intend for useful contributions. The user has:
- caused many edit wars
- deleted citations along with deleting correct claims
- not been cooperative (wikipedia's Editing policy) on many pages that good-intended edits have occurred on
- not explained deletions of citations in a way that other users have been made upset.
I request that the user is warned.
HiLux duck — Preceding undated comment added 22:13, 3 January 2025 (UTC)
- First: the notice at the top of the page clearly says to place new sections at the bottom of the page, which I have now done for you. Second: you need to provide diffs for the edits you are complaining about. Third, you were supposed to notify Andra Febrian per the instructions at the top of the page. Another user has done so for you. - Donald Albury 00:06, 4 January 2025 (UTC)
- @HiLux duck: please sign your comments using ~~~~, which will add a timestamp. Additionally, I reverted your edits to Peugeot 3008 and to Exeed because you are changing information in articles without citing reliable sources. You must cite sources when you add or change information in articles. voorts (talk/contributions) 00:20, 4 January 2025 (UTC)
- HiLux duck just filed a new complaint at ANEW and made the exact same mistakes as they did here. I advised them to stop posting complaints on noticeboards until they can follow the instructions. Liz 07:18, 4 January 2025 (UTC)
- FWIW, I have a feeling that HiLux Duck is a sockpuppet of MrDavr, but I am holding back until they give themselves enough rope to hang. Same obsession with defining overall lengths for various car classifications and edit warring at length over them. Mr.choppers | ✎ 00:55, 6 January 2025 (UTC)
- I'm always impressed when editors can recall editing habits of editors that were blocked years ago. I guess I lack the longterm memory to keep track of sockpuppet habits. Liz 04:14, 6 January 2025 (UTC)
- @Liz: MrDavr actually got under my skin at one point; otherwise I probably wouldn't have noticed. Thanks, Mr.choppers | ✎ 02:04, 7 January 2025 (UTC)
- Looking into this Looks like a duck to me (a HiLux WP:Duck?) because yeah, this is exactly the same editing pattern. Same username pattern as a number of MrDavr socks too (car names/variations thereof - Toyota Hilux). - The Bushranger One ping only 09:49, 6 January 2025 (UTC)
- Most likely yes, I knew that the his editing patterns matched an old blocked user but didn't remember the name. Alawadhi3000 (talk) 16:14, 6 January 2025 (UTC)
- It's also interesting to note that HiLux duck's user page claims they've been on Misplaced Pages since 2019, and having compared edits more extensively I've seen enough and gone ahead and blocked per WP:DUCK. - The Bushranger One ping only 20:20, 6 January 2025 (UTC)
- I'm always impressed when editors can recall editing habits of editors that were blocked years ago. I guess I lack the longterm memory to keep track of sockpuppet habits. Liz 04:14, 6 January 2025 (UTC)
- FWIW, I have a feeling that HiLux Duck is a sockpuppet of MrDavr, but I am holding back until they give themselves enough rope to hang. Same obsession with defining overall lengths for various car classifications and edit warring at length over them. Mr.choppers | ✎ 00:55, 6 January 2025 (UTC)
- HiLux duck just filed a new complaint at ANEW and made the exact same mistakes as they did here. I advised them to stop posting complaints on noticeboards until they can follow the instructions. Liz 07:18, 4 January 2025 (UTC)
Mr.Choppers warning request
- This was (again) posted at the top instead of the bottom; it seems like it is not really a separate issue. 100.36.106.199 (talk) 01:54, 7 January 2025 (UTC)
User:Mr.Choppers has not followed the WP:Civility rules because:
- calling me a "nuisance" because of own bias supporting others in edit wars that have nothing to do with the user. (WP:Civility) (WP:Civility (second violation this user has performed))
- responded fairly aggressively to another user (me) without me being aggressive back or starting this edit war
- note that he also called me a "sockpuppet of a banned user" without reliable clarification, also biased on that
- also note the user had not informed me and used aggression to support own claims.
I would like to inform that this user has unnecessarily used aggression and claimed things not there. Kind regards, HiLux duck (talk) 2:29, 6 January 2025 (GMT+12)
- Missed this because it was at the top. Very unlikely to have merit and is moot now, given the block. - The Bushranger One ping only 02:24, 7 January 2025 (UTC)
user:Uwappa: refusal to engage with WP:BRD process, unfounded allegation of WP:NPA violation, unfounded vandalism allegation
I have indefinitely blocked Uwappa per WP:NLT. Whilst the legal threat pointed out by multiple editors may be very vague, it certainly is designed to have a chilling effect, and Uwappa has confirmed this with this addition to the section. Quite apart from that, we have persistent edit-warring, meritless claims of vandalism against others, and there is a limit to which an editor who thinks all of this is a big joke can be allowed to waste everybody else's time. They can explain themselves in an unblock request if they so desire. Black Kite (talk) 22:57, 6 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
repost from archive:
The content disagreement behind this report is trivial in the overall scope of Misplaced Pages (although the articles affected are subject to WP:MEDRS), but the editor behaviour is not. My reason to bring this case to ANI is that user:Uwappa rejects some basic principles of the project: WP:BRD means that a bold edit may be reverted to the status quo ante and goes on to say don't restore your bold edit, don't make a different edit to this part of the page, don't engage in back-and-forth reverting, and don't start any of the larger dispute resolution processes. Talk to that one person until the two of you have reached an agreement.
Despite having been reminded about BRD after their first immediate counter-revert, they responded to the reversion to the sqa with another counter-revert and, after another editor reinstated the sqa, counter-reverted again. At no stage did they attempt to engage in BRD discussion. Both I and the other editor attempted to engage with them at their talk page: Uwappa characterises my explanation as a personal attack. On another page, Uwappa reverted an edit where I suppressed the questioned material template, declaring it "vandalism" in the edit summary. I recognise the rubric at BRD that says BRD is optional, but complying with Misplaced Pages:Editing policy § Talking and editing and Misplaced Pages:Edit war is mandatory
but Uwappa has done neither.
I consider my escalating this to ANI to be a failure of negotiating skill on my part but, while Uwappa refuses to engage, I am left with no choice. Allowing a few days for logic to intervene has not been fruitful. With great reluctance, because Uwappa has made valuable contributions, I have to ask that they be blocked until they acknowledge and commit to respect the principles that underlie BRD, WP:CONSENSUS and WP:OWN.
Diffs: (all timestamps UTC. NB that I am in England => UTC+00:00, Uwappa is in Australia => UTC+10:00 )
- 11:10 (UTC), 25 December 2024: Uwappa replaces {{Body roundness index}} with a substantially changed new version
- 13:39, 25 December 2024: JMF (me) reverts to the previous version, with edit summary "sorry but this version is not ready for release. I will explain at talk page."
- 13:55, 25 December 2024: JMF opens Template talk:Body roundness index#Proposed version 4 is a step too far, reverted for further discussion at template talk page (and leaves notifications at the talk pages of the articles that invoke the template).
- 14:08, 25 December 2024: Uwappa responds minimally at template talk page.
- 14:27, 25 December 2024: Uwappa counter-reverts to their new version of the template, no edit summary.
- 14:39, 25 December 2024 JMF reverts the counter reversion with edit summary "see WP:BRD: when BRD is invoked, the status quo ante must persist until consensus is reached"
- 14:45, 25 December 2024: Uwappa counter-reverts the template again, no edit summary.
- 14:45, 25 December 2024: at User talk:Uwappa#Bold, revert, discuss, JMF advises Uwappa of the BRD convention.
- 17:38, 25 December 2024: Zefr contributes to BRD debate.
- 17:53, 25 December 2024: At Uwappa's talk page, JMF notifies Uwappa of edit-warring using {{uw-editwar}} with edit summary "I advise strongly that you self-revert immediately, otherwise I shall have no choice but to escalate."
- 19:50, 25 December 2024 At Waist-to-height ratio, JMF comments out invocation of the template, with edit summary "use of template suspended pending dispute resolution . See talk page."
- (a series of reverts and counter reverts follow, in which Uwappa alleges vandalism by JMF. Neither party breaks 3RR.)
- 20:23, 25 December 2024 At their talk page, Uwappa rejects the request to self-revert and invites escalation. Edit summary: "go for it".
- 16:19, 26 December 2024 user:Zefr reverts the counter-reversion of the template to re-establish sqa
- 09:57, 27 December 2024 Uwappa reinstates their counter-reversion of the template.
- 09:59, 27 December 2024 Uwappa contributes to the BRD discussion only to say "See also User_talk:Uwappa#Edit_warring for escalation in progress.".
- 11:05, 27 December 2024 JMF reverts to sqa again, with edit summary " rv to consensus version, pending BRD discussion. That is now also a WP:3RR violation." My 3RR challenge was not valid as reversion was outside the 24-hour window.
- 11:26, 27 December 2024 At Uwappa's talk page, JMF advises Uwappa to take a break from editing.
- 13:04, 27 December 2024 At their talk page, Uwappa alleges WP:NPA violation. I will leave it to others to decide whether the allegation has merit.
---
- 10:51, 29 December 2024 At Uwappa's talk page, JMF suggests that we let the status quo stand and we all walk away without escalating to ANI.
- 14:17, 29 December 2024 Uwappa replies to refuse de-escalation.
As of 11:48 (UTC) on 30/12, the live version of the template is the one that has consensus support. --𝕁𝕄𝔽 (talk) 11:59, 30 December 2024 (UTC)
- Well, Uwappa hasn't edited on the project in 12 hours so it's pretty sage to assume they haven't seen this complaint yet. I'd like to hear their response and whether or not they are willing to collaborate before passing any judgment. Very through presentation of the dispute, easy to follow, so thank you for that. Liz 20:04, 30 December 2024 (UTC)
- Yes, that is why I felt it important to make clear that our time zones are very widely spaced, which makes collaboration difficult in the best of circumstances. When they do see it, I would expect they will take some time offline to polish their response before posting it – and consequently it is likely to be as long again before I respond. 𝕁𝕄𝔽 (talk) 20:35, 30 December 2024 (UTC)
Reposted above from archive, see User_talk:Uwappa#c-JMF-20250105190300-Uwappa-20250105161700
JMF suggested to add the following bit from my talk page:
- You escaped sanction because there were too many more egregious cases in the pipeline and it is a first offence. ANI does not adjudicate on content disputes, only on behaviour and compliance with fundamental principles. The evidence against you was really unarguable; I have seen quite a few cases and I know how they play out: if it had reached a conclusion, you would have been blocked until you acknowledged that you had gotten carried away in the heat of the moment, that you understand and accept WP:EPTALK, WP:EW, WP:CONSENSUS and WP:OWN, and that from now on you commit to respecting them. I strongly advise that you take the message anyway. --𝕁𝕄𝔽 (talk) 12:47, 5 January 2025 (UTC)
- Mate, sorry I was late for the escalation party. End of the year was a madhouse here, both in business and with social activities.
- I was very happy you did escalate and will be happy to reply now that I have spare time available for WP. My business legal department is pretty exited about it, like a kid in a candy store, can't wait to put its teeth in WP rules and regulations.
- Would you like me to repost your escalation? Uwappa (talk) 12:52, 5 January 2025 (UTC)
- I strongly advise that you read Misplaced Pages:No legal threats before you write another line. 𝕁𝕄𝔽 (talk) 15:27, 5 January 2025 (UTC)
- You escaped sanction because there were too many more egregious cases in the pipeline and it is a first offence. ANI does not adjudicate on content disputes, only on behaviour and compliance with fundamental principles. The evidence against you was really unarguable; I have seen quite a few cases and I know how they play out: if it had reached a conclusion, you would have been blocked until you acknowledged that you had gotten carried away in the heat of the moment, that you understand and accept WP:EPTALK, WP:EW, WP:CONSENSUS and WP:OWN, and that from now on you commit to respecting them. I strongly advise that you take the message anyway. --𝕁𝕄𝔽 (talk) 12:47, 5 January 2025 (UTC)
I am so sorry I was late to join this party. End of the year was a bit too hectic, did not leave much spare time for fun activities like WP.
user:Liz What would you like me to do now? Uwappa (talk) 04:54, 6 January 2025 (UTC)
- It was not clear on your talk page, and it's even less clear here since you did not repost your response to JMF's last line there. You do explicitly retract the apparent legal threat that was made? - The Bushranger One ping only 08:22, 6 January 2025 (UTC)
- I did not make a legal threat. Uwappa (talk) 08:33, 6 January 2025 (UTC)
- @Uwappa: your reference to your "business legal team" could certainly be construed as a veiled one, at the very least. You are being asked to clarify by either confirming or retracting this. -- DoubleGrazing (talk) 08:37, 6 January 2025 (UTC)
My business legal department is pretty exited about it, like a kid in a candy store, can't wait to put its teeth in WP rules and regulations.
is either a legal threat or indistinguishable from one. - The Bushranger One ping only 09:33, 6 January 2025 (UTC)- No it is not a legal threat. It is about "WP rules and regulations", not about law.
- To who would this be a threat?
- Which law?
- In which country?
- Uwappa (talk) 09:57, 6 January 2025 (UTC)
- Why would a legal department be involved? — Malcolmxl5 (talk) 12:02, 6 January 2025 (UTC)
- It certainly looks like a legal threat. M.Bitton (talk) 14:24, 6 January 2025 (UTC)
- @Uwappa. Why would a legal department be involved? — Malcolmxl5 (talk) 17:14, 6 January 2025 (UTC)
- Wow, I am glad you asked.
- to have a bit of fun, take a break from the normal, pretty serious work. It will be like kids in a candy store.
- It will be fun for me too. I can't wait to get going with this once the pandemonium calms down.
- The accusation "user:Uwappa: refusal to engage" is utterly wrong.
- Uwappa (talk) 22:47, 6 January 2025 (UTC)
- I'm not at all experienced in the legal world, but I don't think any professional legal team that you're paying money towards would ever be excited to save you from a website "like kids in a candy store". Tarlby 22:53, 6 January 2025 (UTC)
- Wow, I am glad you asked.
- Why would a legal department be excited about you being reported on Misplaced Pages unless you're planning to use them in some way? Tarlby 17:14, 6 January 2025 (UTC)
- I suspect, from context, that Uwappa was trying to suggest they would have assistance of a professional team in interrogating rules and regulations. But "I have the spend to wikilawyer this more than you can" isn't really all that much better than an outright legal threat. Between that and this edit what surprises me is that they're not blocked yet frankly. Simonm223 (talk) 17:23, 6 January 2025 (UTC)
- No it is not a legal threat. It is about "WP rules and regulations", not about law.
- I did not make a legal threat. Uwappa (talk) 08:33, 6 January 2025 (UTC)
- and just to throw some more fuel on the bushfire, you have just accused me twice more of vandalism.03:01, 6 January 2025 (UTC), 08:03, 6 January 2025 (UTC). --𝕁𝕄𝔽 (talk) 12:13, 6 January 2025 (UTC)
- I would say that for Uwappa to read this AN filing, reply to it (including something which could well be taken as a legal threat), and then immediately go back and revert the template for the fifth time (with an edit-summary of "Revert vandalism again", no less) shows a serious lack of self-awareness of the situation. Black Kite (talk) 12:46, 6 January 2025 (UTC)
- Putting aside the possible legal threat, if Uwappa's business legal department is involved it seems likely to be a cause of WP:PAID or at least a WP:COI which really should have been declared which doesn't seem to have happened. This also means Uwappa shouldn't be editing the article directly. Nil Einne (talk) 14:06, 6 January 2025 (UTC)
- It’s hard to see a paid or COI element to the behaviour at {{Body roundness index}}. — Malcolmxl5 (talk) 14:13, 6 January 2025 (UTC)
- It is fairly weird, but I can't see any reason a business legal department would have any interest unless the editor's activity relates to their business activity. Nil Einne (talk) 14:27, 6 January 2025 (UTC)
- I expect it’s just empty talk to get an upper hand in the dispute. — Malcolmxl5 (talk) 14:37, 6 January 2025 (UTC)
- Indeed. It is night where Uwappa is now, but my inclination is to see what reaction there is when they restart editing. If it is another revert or a lack of discussion, a block (or at least a prtial block) is indicated. Black Kite (talk) 15:05, 6 January 2025 (UTC)
- Black_Kite, how do you know where I am? Are you spying on me, disclosing personal information?
- Anybody in the room who can answer my 3 questions?
- Reverted vandalism 3rd time in 24 hours. Anybody curious about what the vandalism is?
- Anybody in the room that wonders why I had to do the repost? Isn't that odd in combination with "user:Uwappa: refusal to engage with WP:BRD process"? Did anybody read my reasons for being late to this party?
- Did anybody read User_talk:Uwappa#Bold,_revert,_discuss and User_talk:Uwappa#Notice_of_reference_to_ANI?
- Did anybody spot any incompleteness in the accusations?
- Anybody interested in my to answers to the accusations?
- Uwappa (talk) 16:59, 6 January 2025 (UTC)
- Black_Kite, how do you know where I am? Are you spying on me, disclosing personal information?
- Indeed. It is night where Uwappa is now, but my inclination is to see what reaction there is when they restart editing. If it is another revert or a lack of discussion, a block (or at least a prtial block) is indicated. Black Kite (talk) 15:05, 6 January 2025 (UTC)
- I expect it’s just empty talk to get an upper hand in the dispute. — Malcolmxl5 (talk) 14:37, 6 January 2025 (UTC)
- It is fairly weird, but I can't see any reason a business legal department would have any interest unless the editor's activity relates to their business activity. Nil Einne (talk) 14:27, 6 January 2025 (UTC)
- It’s hard to see a paid or COI element to the behaviour at {{Body roundness index}}. — Malcolmxl5 (talk) 14:13, 6 January 2025 (UTC)
- Putting aside the possible legal threat, if Uwappa's business legal department is involved it seems likely to be a cause of WP:PAID or at least a WP:COI which really should have been declared which doesn't seem to have happened. This also means Uwappa shouldn't be editing the article directly. Nil Einne (talk) 14:06, 6 January 2025 (UTC)
- JMF above said you were in Australia and I had no reason to disbelieve him. If you aren't, it's irrelevant really, I was just pointing out that you may not edit for a few hours. No-one here is required to answer your questions, but I will; the point was that you invoked something that could be a legal threat
My business legal department is pretty exited about it ... can't wait to put its teeth in WP rules and regulations.
You say that isn't a legal threat, well fine, but you haven't explained what it was. Meanwhile, you're still edit-warring on the template and claiming that other's edits are vandalism, which they clearly aren't, which is why you can no longer edit it. Have I missed anything? Black Kite (talk) 17:51, 6 January 2025 (UTC) - Again, that was either a legal threat or actions indistinguishable from a legal threat in an attempt to cause a chilling effect. When called on it you have continually Wikilawyered instead of straight-up saying "no, that was not a legal threat and I am not involving any legal actions in this". So to make it very clear: you need to clearly state that or be blocked per WP:NLT. - The Bushranger One ping only 20:31, 6 January 2025 (UTC)
- JMF above said you were in Australia and I had no reason to disbelieve him. If you aren't, it's irrelevant really, I was just pointing out that you may not edit for a few hours. No-one here is required to answer your questions, but I will; the point was that you invoked something that could be a legal threat
And just to add to the excitement, Uwappa has just repeated their allegation of vandalism against me and reverted to their preferred version of the template for the sixth time.16:26, 6 January 2025 (UTC) (Their edit note adds 3rd time in 24 hours: are they boasting of a 3RR vio? Zefr undid their fourth attempt, I undid their fifth attempt, but possibly they misread the sequence.) --𝕁𝕄𝔽 (talk) 17:41, 6 January 2025 (UTC)
- Yes, I noticed. I have pblocked them indefinitely from the template, and reverted that edit myself so that no-one else is required to violate 3RR. Black Kite (talk) 17:51, 6 January 2025 (UTC)
- Ha ha ha, this is beyond ridiculous.
.An editor must not perform more than three reverts on a single page whether involving the same or different material—within a 24-hour period.
— WP:Edit_warring#The_three-revert_rule - Suggestion: Add the following calculator to WP:3RR:
- Ha ha ha, this is beyond ridiculous.
3 is less than three. is equal to three. is more than three.
-
- From WP:EW;
Even without a 3RR violation, an administrator may still act if they believe a user's behavior constitutes edit warring
. Which this quite obviously does, especially as you've reverted twice whilst this report was ongoing. Frankly, you're quite fortunate it was only a partial block. Black Kite (talk) 22:41, 6 January 2025 (UTC)
- From WP:EW;
- To admins, please WP:ABAN Uwappa from further work on the calculator template for the body roundness index and waist-to-height ratio, and from further editing and talk page input on those articles. Uwappa has done admirable extensive work, but the simple calculator is finished and sufficient as it is. Uwappa has created voluminous WP:TLDR/WP:WALLOFTEXT talk page discussions for articles with under 50 watchers and few talk page discussants; few editors would read through those long posts, and few are engaged.
- In recent edits on templates, Uwappa reverts changes to the basic template as "vandalism". No, what we're saying is "leave it alone, take a rest, and come back in a few years when more clinical research is completed." Zefr (talk) 18:21, 6 January 2025 (UTC)
- This was closed, but...Uwappa's reply to their block was explictly a legal threat. Suggest revoking TPA. @Black Kite: - The Bushranger One ping only 06:15, 8 January 2025 (UTC)
Kansascitt1225 ban appeal
Appeal successful. There were some murmurings requesting a topic ban from Kansas, but nothing approaching consensus. Of course, Kansascitt1225 would be well-advised to be careful not to go back to the behaviors that led to a block in the first place. But in the meantime, welcome back. HouseBlaster (talk • he/they) 19:59, 15 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
I am posting the following appeal on behalf of Kansascitt1225 (talk · contribs · deleted contribs · page moves · block user · logs · block log · arb · rfc · lta · SPI · cuwiki), who is considered banned by the community per WP:3X:
(keeping it short for WP:TLDR) Hi Misplaced Pages community, it has been over 1 year since I edited on Misplaced Pages without evading my block or breaking community rules. I would like to be given another chance to edit. I realized that my blocking was due to my behavior of creating multiple accounts and using them on the same page and creating issues during a disagreement. I was younger then and am now able to communicate more effectively with others. I intend to respect community rules and not be disruptive to the community. I was upset years ago when I mentioned Kansas City’s urban decay and it was reverted as false and I improperly reacted in a disruptive way that violated the community rules. The mistake I made which caused the disruptive behavior was that I genuinely thought people were reverting my edits due to the racist past of this county and keeping out blacks and having a dislike for the county. I also thought suburbs always had more single family housing and less jobs than cities. In this part of the United States a suburb means something different than what it means in other parts of the world and is more of a political term for other municipalities which caught me off guard and wasn’t what I grew up thinking a suburb was. Some of these suburbs have lower single family housing rates and higher population density and this specific county has more jobs than the “major city” (referenced in previous unblock request if interested). This doesn’t excuse my behavior but shows why I was confused and I should have properly addressed it in the talk pages instead of edit warring or creating accounts. After my initial blocking, I made edits trying to improve the project thinking that would help my case when it actually does the opposite because I was bypassing my block which got me community banned to due the automatic 3 strikes rule. I have not since bypassed my block. I’m interested in car related things as well as cities and populations of the United States and want to improve these articles using good strong references. Thanks for reading. Kansascitt1225 (talk) 04:46, 27 December 2024 (UTC)
References
- https://slate.com/business/2015/05/urban-density-nearly-half-of-america-s-biggest-cities-look-like-giant-suburbs.html.
{{cite web}}
: Missing or empty|title=
(help)
- (mildly involved) Support. I gave feedback on an earlier version of their ban appeal. This is five years since the initial block. Five years and many, many socks, and many, many arguments. But with no recent ban evasion and a commitment to communicate better, I think it's time to give a second chance. -- asilvering (talk) 21:42, 7 January 2025 (UTC)
- Support per asilvering and WP:SO. voorts (talk/contributions) 21:44, 7 January 2025 (UTC)
- Support. Five years is a long time. Willing to trust for a second chance.-- Deepfriedokra (talk) 21:49, 7 January 2025 (UTC)
- Ideally I'd want to see some indication that they don't intend to right great wrongs as the issue seems to be rather ideological in nature and I don't see that addressed in the appeal. I also don't love the failure to understand a lot of issues around their block/conduct and their inability to effectively communicate on their talk page and on their unblock request from November. Thebiguglyalien (talk) 00:00, 8 January 2025 (UTC)
- Would a topic ban from Kansas-related topics help? This was floated as a bare minimum two or so years ago. -- asilvering (talk) 00:32, 8 January 2025 (UTC)
- I'm not that concerned by the RGW issue. Their communication on this appeal has been clear, they responded to my feedback regarding their unblock request, and they've indicated they'll not edit war and seek consensus for their edits. voorts (talk/contributions) 00:46, 8 January 2025 (UTC)
- Is my maths just bad or is January 2019 not six years ago rather than five? In any event it's been a long time since they tried to evade. I'm leaning toward giving a second chance but I'd really like them to understand that walls of text are not a good way to communicate, that they need to post in paragraphs, and that Misplaced Pages is not a place for righting great wrongs. FOARP (talk) 16:27, 8 January 2025 (UTC)
Is my maths just bad or is January 2019 not six years ago rather than five?
ssssshhh. -- asilvering (talk) 18:02, 8 January 2025 (UTC)- Response from KC:
voorts (talk/contributions) 02:19, 15 January 2025 (UTC)Yes I can write in paragraphs and list different ideas in separate paragraphs instead of a giant run on sentence.
I wasn’t trying to right great wrongs but noticed the contrast of the definition of suburban on Misplaced Pages and these communities being described as suburban (meanwhile some of these suburbs verifiably having lower residential to job ratio than the city and also a higher overall population density with some suburbs gaining population during the day due to commuters coming into them). This is essentially why on my case page It says I feel as tho something had to be “fixed”. I thought my edits were being removed simply because people didn’t like this place or some of its past so I felt as tho I was simply being purposefully misled which caused me to not follow proper civility.
I just wanted to clarify that these places weren’t only residential and were major employment areas that they sometimes have a lower percentage of single family homes. This to me was always the opposite of what suburban meant, atleast what I learned during grade school and what it says on Misplaced Pages. That’s where the confusion came from. Kansascitt1225 (talk) 06:17, 13 January 2025 (UTC)
- Support Six years is a long time, and they have shown growth. I do not think what is actually happening here is righting great wrongs, instead they assumed bad faith and things went downhill from there. I think their concerns of
Jackson county being THE central county of the metropolitan area
(which Misplaced Pages deems urban)when you can see in the census reference here there are actually 6 central counties
(which Misplaced Pages deems suburban) is reasonable. I researched it, but found the concerns are inconsistent with urban area page which provides the definition thatAn urban area is a human settlement with a high population density and an infrastructure of built environment. This is the core of a metropolitan statistical area in the United States, if it contains a population of more than 50,000.
An urban area is the most urban area compared to its surroundings, even though its surroundings are quite dense. I hope this helps. Kenneth Kho (talk) 22:54, 12 January 2025 (UTC)- I add that their concerns that suburban designation misleads people seem to have merit. It is not the suburban designation that misleads people though, but the definition of suburban itself on the suburban article seems to be misleading. I know this is not a place to discuss content, but discuss conduct. But some insight into content can help resolve problems. Kenneth Kho (talk) 11:56, 13 January 2025 (UTC)
ftools is back!
I am proud to announce that I have become the new maintainer of Fastily's ftools
, which is live here. And yes, this includes the IP range calculator! JJPMaster (she/they) 23:12, 9 January 2025 (UTC)
- Like -Ad Orientem (talk) 23:15, 9 January 2025 (UTC)
- Note: DreamRimmer is now also a maintainer. JJPMaster (she/they) 15:47, 10 January 2025 (UTC)
- My congratulations/condolences. Buffs (talk) 15:49, 11 January 2025 (UTC)
- So, will ftools be renamed or not? Congratulations. Ahri Boy (talk) 02:32, 14 January 2025 (UTC)
Block appeal for User:Aman.kumar.goel
UNBLOCK DENIED AKG has withdrawn the request. In any case, I see too many misgivings even on the "support" side to consider an unblock at this time. asilvering (talk) 02:33, 11 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
I am bringing a somewhat unusual unblock request here for broader community input. Aman.kumar.goel has been blocked for more than a year for sockpuppetry (see Misplaced Pages:Sockpuppet investigations/Aman.kumar.goel/Archive). As you can see in the unblock request at User talk:Aman.kumar.goel#Unblock request, they have agreed to a one-account restriction as an unblock condition, and there is no CU-confirmed evidence of recent sockpuppetry. However, Ivanvector, who made that check, is skeptical and has declined to support an unblock. A topic ban from WP:ARBPIA and WP:ARBIPA were floated as additional possible conditions, but no agreement was reached, and Aman.kumar.goel has requested that their unblock request be considered by the wider community. Their statement is as follows:
- I was blocked for sockpuppetry. There was no doubt throughout the discussion over that. I have agreed to a one-account restriction. However, during the unblock request, a topic ban on me was proposed from Israel-Palestine (WP:ARBPIA) and also from Afghanistan, Pakistan and India (WP:ARBIPA). Though no proper evidence was provided to substantiate such proposals.
- While the proposal to topic ban me from WP:ARBPIA does not make any sense because I haven't even edited that area, I would nevertheless reject the proposed topic ban from WP:ARBIPA with explanation because in this area I have been significantly active.
- My edits on WP:ARBIPA were clearly net-positive, and they fixed the long-term problems that were otherwise overlooked for a long time. You can find the deletion of a number of non-notable pro-Hindutva articles, creation of SPIs of future LTAs, and multiple DYKs. That said, the idea to topic ban me achieves nothing good. Black Kite himself said "
The edits aren't the issue here, it's socking in the IPA area that is.
". However, for the offense of sockpuppetry, I have already agreed to one-account restriction and spent over 1 year blocked.
- Once unblocked, I would like to improve drafts such as Draft:Aeroin Spacetech and Draft:Omspace Rocket and Exploration. Looking forward to positive feedback. Aman Kumar Goel 00:51, 10 January 2025 (UTC)
asilvering (talk) 01:23, 10 January 2025 (UTC)
- Support unblock without TBANs and with single account restriction.-- Deepfriedokra (talk) 01:43, 10 January 2025 (UTC)
- Support as requested. The request is sincere. Having edited a fair amount of articles where I discovered this editor's edits, I found his edits thoroughly productive and that is absolutely uncommon in this area. Nxcrypto Message 01:44, 10 January 2025 (UTC)
- Comment "Support as requested" sounds like a canvassed vote, did you mean it in a different way? Black Kite (talk) 08:48, 10 January 2025 (UTC)
- You need to re-check. Here, AKG posted a "request" for "unblock". By "as requested" , I meant how AKG requested himself to be unblocked, that is without any topic bans. Also, see WP:AGF. Nxcrypto Message 11:05, 10 January 2025 (UTC)
- I did AGF, otherwise my sentence would not have included the second clause. I understand what you mean now but I did not from the original posting. Black Kite (talk) 15:25, 10 January 2025 (UTC)
- Comment "Support as requested" sounds like a canvassed vote, did you mean it in a different way? Black Kite (talk) 08:48, 10 January 2025 (UTC)
- Aman.kumar.goel's explanation for the relationship with Editorkamran is
we knew each other in real life, and we used the same internet and the same system sometime, and also helped each other at times with Misplaced Pages editing
, but Ivanvector says the CU data indicatessomeone who had been carefully using two or probably more accounts for quite some time and going to lengths to obscure the connection, but made a mistake just one time that exposed them
. I don't know who's right, but this is a CU block, so if Aman.kumar.goel stands by his answer, I'd be uncomfortable unblocking unless another CU has a different interpretation of what happened. Extraordinary Writ (talk) 01:55, 10 January 2025 (UTC)- @Extraordinary Writ, response from AKG copied over:
voorts (talk/contributions) 02:46, 10 January 2025 (UTC)Hope you will check my statement above where I explained, "
However, upon reading further following the block, I realised that what I did was a violation of WP:SOCK because the use of both these accounts was prohibited by the policy, especially WP:SHARE and WP:MEAT.
" That means the CU finding does not really challenge my admission because I don't deny using multiple accounts. The only thing I happened to clarify was that the two accounts belonged to two different persons before they were used by the same person, which is me. That's why, in my unblock request (for WP:AN), I have also cited the edits of Editorkamran account as part of my edits into this area. Aman Kumar Goel (Talk) 02:43, 10 January 2025 (UTC)- All I know about this case is what I can glean by reading the private case notes, which do indeed support what Ivanvector has said. But given that AKG has admitted (on their talk page) to using the Editorkamran account, that's all kind of moot. I'd still like to hear Ivan's latest opinion on this, and I've also pinged off-wiki another CU who is familiar with this case, but my personal feeling is that we should draw a line in the sand and accept the unblock request with the single account restriction, no ARBPIA/IPA/API/TLA restriction, and an understanding that AKG's account at the bank of AGF is empty. RoySmith (talk) 03:05, 10 January 2025 (UTC)
- Oh, the other thing I wanted to mention is that on unblock requests, we're often left wondering what the user plans to work on if unblocked. In this case, they've specified two extant drafts they want to complete, both of which look like they have the potential to be useful articles. So that's a plus. RoySmith (talk) 03:22, 10 January 2025 (UTC)
- Am I the only one to feel that their earlier statements, even if they did mention WP:SHARE would not reasonably be understood to an admission that they did eventually user the Editorkamran account? Especially with all that comment about "we used the same internet and the same system sometime" etc? To my read the earlier statement gives the impression that they each account was only ever used by one person even if they did communicate and coordinate their editing at times. It's only most recently that I feel they've finally made it clear they it wasn't simply a matter of communication and coordination but rather that did use the other account directly. This also leads to the obvious question. How could any editor actually think it's okay for them to use some other editor's account just because it primarily belongs to another editor? Whether you consider it WP:SOCKing or whatever, you should not need any real experience to know it's unacceptable and definitely any editor with AKG's experience should know that. Note that I'm not suggesting that an editor who did what AKG did can never be unblocked, definitely they can be. But IMO there are good reasons to call into question whether the editor is ready for an unblock when they seem to have been so dishonest in their unblock request. In other words, if said something like 'yes I did X, I knew it was wrong and should not have done it, I promise not to do it again' rather than what they actually said, I'd be much more inclined to consider an unblock. Nil Einne (talk) 10:14, 10 January 2025 (UTC)
- All I know about this case is what I can glean by reading the private case notes, which do indeed support what Ivanvector has said. But given that AKG has admitted (on their talk page) to using the Editorkamran account, that's all kind of moot. I'd still like to hear Ivan's latest opinion on this, and I've also pinged off-wiki another CU who is familiar with this case, but my personal feeling is that we should draw a line in the sand and accept the unblock request with the single account restriction, no ARBPIA/IPA/API/TLA restriction, and an understanding that AKG's account at the bank of AGF is empty. RoySmith (talk) 03:05, 10 January 2025 (UTC)
- For what it's worth: I'm the other CU mentioned by Roy. I had run the initial checks and written some contemporaneous notes. I agree with Ivanvector's assessment at the talk page appeal; there was a concerted, long-term effort to obfuscate the connection between these accounts, which doesn't really fit with the assertion that they only realised they were doing something wrong after the fact. Whether a second individual also had access to either account at times can't really be retroactively assessed with any certainty, but it also seems immaterial to the finding of socking. --Blablubbs (talk) 17:39, 10 January 2025 (UTC)
- @Extraordinary Writ, response from AKG copied over:
- Support with 1 account restriction. A prolific editor with no recurring issues. Understands where he was wrong. Capitals00 (talk) 03:04, 10 January 2025 (UTC)
- Support: I have edited in South Asian-related topics and have run across some edits made by User:Aman.kumar.goel. Of these, I have seen several constructive edits made by him that have overall improved Misplaced Pages. Additionally, being blocked for one year is enough of a penance, which I'm sure has given him time to reflect. In view of this, I support his request in good faith. I hope this helps. With regards, Anupam 03:49, 10 January 2025 (UTC)
- Support with one account restriction and no topic restriction. We need competent editors working in the India topic area, as long as they follow policies and guidelines. The editor should be aware that Misplaced Pages:One last chance applies here. Cullen328 (talk) 05:17, 10 January 2025 (UTC)
- Oppose. I warned AKG in October 2021 for tag-team editing with Srijanx22, after many instances of one showing up to a content dispute the other was in to back them up. AKG didn't understand then what the issue was. He didn't understand it when he was blocked for socking with Editorkamran. He doesn't seem to understand it now. The semantics of sockpuppetry vs. "just" meatpuppetry are uncompelling. We indeed need more competent editors in the India topic area. We are not going to get closer to that by letting in someone who has shown willingness to serially manipulate interactions in that topic area, who managed to evade detection for years, who continued doing so after a first warning, and whose explanation is, apparently, unpersuasive to CUs who have reviewed the evidence. -- Tamzin (they|xe|🤷) 06:51, 10 January 2025 (UTC)
- It has been sufficiently confirmed throughout these years that the false allegation of tag teaming was indeed false. Do you see me in any of the events that have been mentioned so far in this unblock request? You don't. It is disappointing to see you bringing up your misleading observation you made when you weren't even an admin. You did not even ping me. Oh, and don't ask me how I got here because I watch this noticeboard and have edited it before.Srijanx22 (talk) 07:52, 10 January 2025 (UTC)
- I'm glad that you heeded my warning and stopped tag-teaming with AKG. AKG, however, continued to manipulate consensus in the topic area, which is what he got indeffed for. I didn't ping you because I'm not making any comment on your fitness as an editor; I just wanted to be clear that that 2021 report was separate from the Editorkamran case. -- Tamzin (they|xe|🤷) 08:13, 10 January 2025 (UTC)
- To quote what I had said then, "I am comfortable with ignoring your 'warning' since it lacks policy backing." I said that because no tag teaming on my part ever happened in the first place and the time has proven me correct. I would reiterate that you are supposed to ping the editor whose behavior is being discussed. In this case, you had to. Srijanx22 (talk) 09:10, 10 January 2025 (UTC)
- Actually, the SPI makes it clear that there were multiple examples of you reverting to the same version as AKG in rapid succession, whether you were co-ordinating off-wiki with AKG or not. As well as those, I could add 2020–2021 China–India skirmishes on 1st December 2020 and 21st February 2021 and Violence against Christians in India on 19 April 2020. So please give it a rest with the denials and instead ensure that it doesn't happen in the future if AKG is unblocked. Black Kite (talk) 11:00, 10 January 2025 (UTC)
- That's totally superficial. I have also edited both of these popular articles and so have many others I can count on my fingers. Capitals00 (talk) 16:10, 10 January 2025 (UTC)
- Yes, but that's not the point; have you reverted to a version also reverted to by AKG within < 24h on multiple occasions? I suspect not. Black Kite (talk) 18:59, 10 January 2025 (UTC)
- That's totally superficial. I have also edited both of these popular articles and so have many others I can count on my fingers. Capitals00 (talk) 16:10, 10 January 2025 (UTC)
- Actually, the SPI makes it clear that there were multiple examples of you reverting to the same version as AKG in rapid succession, whether you were co-ordinating off-wiki with AKG or not. As well as those, I could add 2020–2021 China–India skirmishes on 1st December 2020 and 21st February 2021 and Violence against Christians in India on 19 April 2020. So please give it a rest with the denials and instead ensure that it doesn't happen in the future if AKG is unblocked. Black Kite (talk) 11:00, 10 January 2025 (UTC)
- To quote what I had said then, "I am comfortable with ignoring your 'warning' since it lacks policy backing." I said that because no tag teaming on my part ever happened in the first place and the time has proven me correct. I would reiterate that you are supposed to ping the editor whose behavior is being discussed. In this case, you had to. Srijanx22 (talk) 09:10, 10 January 2025 (UTC)
- I'm glad that you heeded my warning and stopped tag-teaming with AKG. AKG, however, continued to manipulate consensus in the topic area, which is what he got indeffed for. I didn't ping you because I'm not making any comment on your fitness as an editor; I just wanted to be clear that that 2021 report was separate from the Editorkamran case. -- Tamzin (they|xe|🤷) 08:13, 10 January 2025 (UTC)
- It has been sufficiently confirmed throughout these years that the false allegation of tag teaming was indeed false. Do you see me in any of the events that have been mentioned so far in this unblock request? You don't. It is disappointing to see you bringing up your misleading observation you made when you weren't even an admin. You did not even ping me. Oh, and don't ask me how I got here because I watch this noticeboard and have edited it before.Srijanx22 (talk) 07:52, 10 January 2025 (UTC)
- Support per NxCrypto and RoySmith. I don't see any issue with unblocking right away. The presence of this editor is a net-benefit for this area. Koshuri Sultan (talk) 07:14, 10 January 2025 (UTC)
- Comment If unblocked, I would like to see AKG stay away from arbitration enforcement. There were a number of times - I count at least nine times between 2020 and 2023 - that they opened cases here trying to get editors on the "opposing" side blocked, and I don't think continuing this is a good idea. I also note that they were very active at SPI cases involving other editors in ARBIPA, which is another sign of BATTLEGROUND behaviour. Black Kite (talk) 08:46, 10 January 2025 (UTC)
- That, and the refusal to accept TBANs, gives me bad vibes.
- I also don't think that agreeing to use only one account is much of a concession, that's kind of a given, but I guess it's at least better than not agreeing to it. -- DoubleGrazing (talk) 08:56, 10 January 2025 (UTC)
- Yes, this is also my concern. I would have thought that we would expect an editor banned for socking in a CTOP to at least demonstrate their ability to collaborate well outside that CTOP before being allowed to edit it. I can understand the Support !votes above from other editors who generally edit from the same POV as AKG, but I'm still not thinking this is a brilliant idea. Black Kite (talk) 11:15, 10 January 2025 (UTC)
- What is that "same POV as AKG"? It is certainly not their fault that you are assuming bad faith. Capitals00 (talk) 16:12, 10 January 2025 (UTC)
- I don't need to AGF when the evidence is quite plain, as with the editor I mentioned above where I pointed out their tag-teaming issues. Black Kite (talk) 19:02, 10 January 2025 (UTC)
- What is that "same POV as AKG"? It is certainly not their fault that you are assuming bad faith. Capitals00 (talk) 16:12, 10 January 2025 (UTC)
- Yes, this is also my concern. I would have thought that we would expect an editor banned for socking in a CTOP to at least demonstrate their ability to collaborate well outside that CTOP before being allowed to edit it. I can understand the Support !votes above from other editors who generally edit from the same POV as AKG, but I'm still not thinking this is a brilliant idea. Black Kite (talk) 11:15, 10 January 2025 (UTC)
- Oppose. This user edits via proxy with IPBE, and the breadth and depth of the deception shown at that SPI is considerable. Now they're back with a semi-plausible explanation, and I don't buy it. And the one-account restriction is more challenging to police with a proxy/IPBE setup.—S Marshall T/C 09:27, 10 January 2025 (UTC)
- If he has agreed to one account restriction and this socking episode makes him ineligible for any future IPBE right, so what's wrong in allowing him back in since he has already served a year of block? Unless you are suggesting we completely ban those who have engaged in sock puppetry altogether, which is unrealistic. ArvindPalaskar (talk) 11:08, 10 January 2025 (UTC)
- What's wrong in allowing him back is everything Ivanvector says in that SPI. Please read it carefully and then re-read AKG's unblock request with a critical eye.—S Marshall T/C 12:38, 10 January 2025 (UTC)
- Oppose. I would support unblocking with an ARBIPA topic ban (which could be appealed later when AKG has proved they can edit well outside that area). But since AKG will not accept that TBAN I can only Oppose at the moment. Black Kite (talk) 11:17, 10 January 2025 (UTC)
- Support - The request is convincing and to-the-point. Those opposing are seemingly forgetting that it has been more than a year since this editor has been blocked. Azuredivay (talk) 12:33, 10 January 2025 (UTC)
- Support per above without any topic ban. It is totally unreasonable to seek punishment over the same offense even after WP:SO has been sufficiently met. Lorstaking (talk) 12:59, 10 January 2025 (UTC)
- It is not at all unusual for editors seeking an unblock to be required to accept a topic ban as a precondition to that unblock. Here are two are recent examples from this noticeboard. Caeciliusinhorto-public (talk) 15:04, 10 January 2025 (UTC)
- Whilst I don't support the topic ban, it would not be done as punishment, but as a measure reducing the likelihood of further disruption. -- Deepfriedokra (talk) 16:07, 10 January 2025 (UTC)
- Caeciliusinhorto-public not good to compare community banned editors with this case. Capitals00 (talk) 16:13, 10 January 2025 (UTC)
- It is not at all unusual for editors seeking an unblock to be required to accept a topic ban as a precondition to that unblock. Here are two are recent examples from this noticeboard. Caeciliusinhorto-public (talk) 15:04, 10 January 2025 (UTC)
- Support per Ivanvector: i.e. dependent on a topic ban from WP:ARBIPA and WP:ARBPIA and a single-account restriction. This will deal with the meat of the issue, while WP:ROPE should take care of the crust. SerialNumber54129 13:09, 10 January 2025 (UTC)
- Oppose I find myself agreeing with Black Kite - if they are willing to come back with a topic ban that'd be one thing. Without it I'm concerned we'll just end up back at AN/I, SPI or AE again. Simonm223 (talk) 13:42, 10 January 2025 (UTC)
- I will tentatively change my position to support provided it includes the topic ban. Simonm223 (talk) 18:09, 10 January 2025 (UTC)
- Oppose While I appreciate that brevity is required in unblock requests and people have different ways of writing stuff, as I noted above I feel the original unblock request was at a minimum intentionally evasive if not even misleading on whether Aman.kumar.goel had used the Editorkamran account directly. While they've now made it clear that they did so, the fact this only happened after editor questioned their story compared to the CU view makes me question whether it's because they didn't realise they were unclear or instead because they realised their evasiveness wasn't working. If they were evasive in their recent unblock request, this makes it very hard to trust Aman.kumar.goel. Further, even if Akg wasn't being evasive, it's very unclear why an editor with their experience didn't realise what they were doing was wrong until recently. I was originally willing to accept with a topic ban but frankly I'm now not even sure that's enough, but it's moot anyway. If this fails, I'd suggest on their next appeal Aman.kumar.goel ensures what they're telling us is clear from the get go. Nil Einne (talk) 15:42, 10 January 2025 (UTC)
- Support without topic ban. Sockpuppetry was the sole concern for the indefinite block. There is no evidence of any disruptive edits, as such the idea of topic ban makes zero sense. Abhishek0831996 (talk) 15:47, 10 January 2025 (UTC)
- Oppose per Black Kite. Any unblock that doesn't involve a restriction on AKG's original area of disruption will simply allow for further disruption. The Kip 16:13, 10 January 2025 (UTC)
- Not at all. Very recently, several editors editing this subject and socked were unblocked recently without any topic bans, including one more editor who was banned per 3x. Nxcrypto Message 16:23, 10 January 2025 (UTC)
- Oppose per Nil Einne. Being "intentionally evasive if not even misleading" during this unblock request and previously makes it very hard for me to trust this user. I'm glad they owned up to their outright sockpuppetry with Editorkamran and had they done so from the beginning of the request, I'd have considered supporting the request, provided they accepted the topic ban(s) suggested (so as to increase the odds of their future success). --Yamla (talk) 16:25, 10 January 2025 (UTC)
- Oppose unless an ARBIPA TBAN is applied. AKG's edits have not always been a positive: their approach to contentious matters has often been needlessly aggressive, and they haven't always been able to engage constructively with users and sources they disagree with. In that context sockpuppetry is more than "just" sockpuppetry. Some examples: , , , , , , and (These are discussions, not diffs, but I believe the context is needed to demonstrate the pattern I see). Vanamonde93 (talk) 16:55, 10 January 2025 (UTC)
I would tentatively support with the TBAN they have now agreed to.I have no opinion on whether a PIA ban is needed: if they have edited in that area I haven't seen it. I was considering suggesting a ban from bring others to AE/AN/ANI, but perhaps some rope is appropriate there. In any case they should be aware that they are on thin ice. I would also note that under no circumstances should they be given IPBE in the foreseeable future. Vanamonde93 (talk) 18:02, 10 January 2025 (UTC) I'm sorry to vacillate like this, but based on comments by Ivanvector and Girth Summit I simply cannot support (NB: while I am a CU, I am obviously not acting as a CU in this case). Despite our past disagreements I had been willing to give AKG another chance, but that was based on the assumption that they were being fully forthcoming, and based on the comments of CUs familiar with this situation, it doesn't appear that they have come clean. Put me down as a neutral, I suppose, though I remain opposed absent a TBAN. Vanamonde93 (talk) 22:49, 10 January 2025 (UTC)
- Oppose: Per Vanamonde, Tamzin, and Black Kite. It's telling that they won't accept a TBAN from my point of view. They were disruptive prior to their block and, as much as I want to assume good faith, I feel strongly that their refusal signals their intent to immediate jump into said area. There's also the concern that they may end up chasing other editors away from the site if they continue their aggressive behaviour and approach, which frankly I expect based on the lengths they went to in the past and the TBAN issue. I think this user was a net negative, chased people away from those areas, and made it more difficult for others to get involved with. Unblocking this user would end up leading to editor time wasted and would be a further net negative. Hey man im josh (talk) 17:13, 10 January 2025 (UTC)
- Noting that I still oppose the unblock, even though they accepted the condition about a TBAN. I agree with Girth Summit that this seems to just be someone saying whatever they think will convince people to unblock them. I also firmly believe that allowing them back onto the project will be a net negative. Hey man im josh (talk) 20:12, 10 January 2025 (UTC)
- Comment Aman.kumar.goel has requested this comment to be posted here from their talkpage:
After seeing a number of editors, some of whom I respect, are supporting my unblock but only with a topic ban from WP:ARBIPA, I would like to accept the topic ban from the said area. Ping Yamla, The Kip, Black Kite, Caeciliusinhorto-public, Simonm223 and Vanamonde93. Thanks Aman Kumar Goel 17:08, 10 January 2025 (UTC)
- Ratnahastin (talk) 17:46, 10 January 2025 (UTC)
- Would they also consent to the WP:ARBPIA topic ban? Because my understanding is that the ask was for both. Simonm223 (talk) 17:47, 10 January 2025 (UTC)
- I don't believe the PIA issue is a problem, only the IPA one. Black Kite (talk) 18:57, 10 January 2025 (UTC)
- Oppose an unblock based on this request. When I'm looking at an unblock request, I try to get a sense of whether someone is actually coming clean and saying 'I did this thing, I recognise that was out of order and I undertake that I won't do it again', or something along those lines. In this case, I don't see that. In their unblock request of 10 December 2024 (just a month ago), AKG seems still to be saying that they were not using multiple accounts - their argument seems to be that they accept there was a violation of WP:MEAT and WP:SHARE, but the two accounts were used by two different people from the same device. They have since swung round to acknowledging that they were in fact using the Editorkamram account, but are saying that they thought that was OK since the account really belonged to somebody else and they only used it from time to time. I'm afraid I simply don't believe that story, and I don't know what to think about their shifting narratives - I get the sense of someone saying whatever they think will convince people to unblock them, changing their story when it becomes apparent that it's not working, and failing to actually come clean about what they did and why they did it. If I don't trust someone in what they are saying in their unblock appeal, I don't trust them to abide by a one-account restriction - so, yeah, I don't think we can accept this request. Do some self-reflection, come back in six months with a frank and believable unblock request. Girth Summit (blether) 18:35, 10 January 2025 (UTC)
- Support. Seeing that AKG has agreed to the proposed IPA topic ban, the unblocking would be fine now. See no other issues. ArvindPalaskar (talk) 19:00, 10 January 2025 (UTC)
- Support based on the comments from RoySmith and agree with their point that the AGF tank is gone for A.K.G. Any issues beyond a minor oops with their editing should be an immediate indef. No warnings, no "one last chance". That bridge was crossed, burned, torn down and barriers put up to block it from being rebuilt. Ravensfire (talk) 19:24, 10 January 2025 (UTC)
- I hope A.K.G recognizes that is a last chance for them, and returning quickly to a contentious topic could be challenging for them to stay cool, engage in discussions but not disruption and that there will be enhanced scrutiny on their edits and willingness to take concerns to an admin board. They can't edit as they did before. Ravensfire (talk) 19:34, 10 January 2025 (UTC)
- Oppose - I gave my reasons on the talk page; I don't trust this user. Ivanvector (/Edits) 20:20, 10 January 2025 (UTC)
- Also I should point out that I was not involved whatsoever in the checks that led to this block; my comments on the talk page refer to emails I remember reading a year earlier on the private checkuser mailing list, which does not archive. I did check in relation to their unblock request recently and in my opinion that check was inconclusive; I elaborated on their user talk at the time. The result gives me pause because they had been using multiple accounts and evading checkuser for quite a long time before being blocked, while editing in one of our longest-designated contentious topics, one that's known to be very badly impacted by sockpuppetry and state-sanctioned disinformation campaigns. I suggested a topic ban from India-Pakistan for reasons that I think are already obvious from previous comments in this thread, and from Israel-Palestine because of something I thought I read on their talk page about a dispute in that topic, but I can't find that now and so I have to say I was probably out of line to have suggested it. But on the whole, I do not support unblocking, even with the proposed restriction. Ivanvector (/Edits) 20:43, 10 January 2025 (UTC)
- Very, very weak support on unblocking here with a one-account and indefinite IPA topic ban restriction. I found my engagement with the editor at their talk page today to be somewhere between obstructionist and disingenuous — and from reading the comments above, others have got similar vibes from different comments earlier in this process regarding the sockpuppetry and willingness to accept a topic ban condition. As Ravensfire notes above, the assume good faith tank is just about empty here — which means any non-trivial lapse or return to suboptimal behaviours is going to end up with a pretty swift reblock. I am very sympathetic to the number of very experienced editors above saying that this editor is a time sink and a net negative, and while I don't necessarily disagree based on what I've seen at their talk page and the evidence presented here, I think it's worth trying here one more time — armed with account and topic ban restrictions, and a pretty clear sentiment from a number of admins commenting (both on the support and oppose sides) that any issues upon resuming editing will be handled swiftly. Daniel (talk) 22:31, 10 January 2025 (UTC)
- Support, but only with IPA topic ban, 1-account restriction, no VPN use, and no IPBE. That should allow us to be able to detect recidivism and limit potential damage. — rsjaffe 🗣️ 22:55, 10 January 2025 (UTC)
- Oppose per Black Kite, Tamzin, S Marshall, Girth Summit, and Ivanvector. Andre🚐 23:04, 10 January 2025 (UTC)
- Oppose, agreeing with a number of editors above. I don't know if the two drafts, for Indian companies, would fall under WP:ARBIPA. Unfortunately, the editor does not seem trustworthy. Miniapolis 23:36, 10 January 2025 (UTC)
- Support - At the end of the day, the standard offer has been followed by this user for a long time. Don't see anything wrong with providing one more chance. Dympies (talk) 23:42, 10 January 2025 (UTC)
- Oppose per comments of Blablubbs, Tamzin, etc. If they are unblocked, they should be under an India--Pakistan CTOP topic ban. --JBL (talk) 00:07, 11 January 2025 (UTC)
- Oppose. The CheckUser evidence of overt sock puppetry (not meat puppetry) is pretty strong, and the repeated denials, which seem to get walked back over time, make this user seem untrustworthy. NinjaRobotPirate (talk) 00:28, 11 January 2025 (UTC)
- Support - Noting the opposes above, AKG has nevertheless agreed with a topic ban inline with many of the opposes. It shows he is willing to minimize any possible concerns and that is a good sign. Shankargb (talk) 00:51, 11 January 2025 (UTC)
- Oppose calling socking the sole issue is a red herring when there was disruption in addition, but the socking alone merited the block so they didn't need to be blocked for both. I think accepting the t-ban is more telling us what he thinks we want to hear, vs. awareness of why AKG shouldn't edit there. I do not think an unblock would be productive. Star Mississippi 01:36, 11 January 2025 (UTC)
Import request
A list without citations or an indication that it meets WP:NLIST is not going to be imported here. voorts (talk/contributions) 18:00, 12 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
Can you import, List of characters in brawl stars from simple Misplaced Pages. I created the page there. — Cactus🌵 07:19, 10 January 2025 (UTC)
- I suppose you mean this page, which you didn't create at all though, and which is completely unsuitable for enwiki as it stands, being unsourced and lacking all indication of notability. Fram (talk) 09:09, 10 January 2025 (UTC)
- Well, they did create the page. JJPMaster (she/they) 15:18, 10 January 2025 (UTC)
- Fram, oh, okay — Cactus🌵 09:16, 11 January 2025 (UTC)
Arbitration motion regarding coordinating arbitrators
The Arbitration Committee has resolved by motion that:
The Arbitration Committee's procedures are amended by adding the following section:
- Coordinating arbitrators
The Arbitration Committee shall, from time to time, designate one or more arbitrators to serve as the Committee's coordinating arbitrators.
Coordinating arbitrators shall be responsible for assisting the Committee in the routine administration and organization of its mailing list and non-public work in a similar manner as the existing arbitration clerks assist in the administration of the Committee's on-wiki work.
The specific responsibilities of coordinating arbitrators shall include:
- Acknowledging the receipt of correspondence and assigning tracking identifiers to pending requests and other matters;
- Tracking the status of pending matters and providing regular updates and reminders on the status of the Committee's off-wiki work to arbitrators;
- Reminding members of the Committee to vote or otherwise take action in pending matters;
- Organizing related correspondence into case files; and
- Performing similar routine administrative and clerical functions.
A coordinating arbitrator may, but is not required to, state an intention to abstain on some or all matters before the Committee without being listed as an "inactive" arbitrator.
For the Arbitration Committee, SilverLocust 💬 23:48, 10 January 2025 (UTC)
- Discuss this at: Misplaced Pages talk:Arbitration Committee/Noticeboard § Arbitration motion regarding coordinating arbitrators
Backlog
Misplaced Pages:Requests for page protection/Increase Moxy🍁 19:38, 11 January 2025 (UTC)
Requesting review of SPI
No need to have brought this here.--Bbb23 (talk) 23:15, 11 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
I recently filed an SPI for Xselant; any admin/checkuser eyes would be appreciated. Thank you! XtraJovial (talk • contribs) 22:43, 11 January 2025 (UTC)
- CUs and SPI clerks are very aware of which SPIs need attention. Please trust that we will get to the one you posted. Asking for input at AN isn't very helpful unless your SPI is much more urgent than usual. Vanamonde93 (talk) 23:09, 11 January 2025 (UTC)
IPBE for AWB account
DONE Done. - The Bushranger One ping only 05:02, 12 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
Hi. I'm performing a task using CanonNiAWB (talk · contribs), but the edits aren't editing since I'm using a VPN. I already have IP block exemptions on this account, so could it also be granted to that? Thanks. ''']''' (talk • contribs) 02:32, 12 January 2025 (UTC)
- Done. Extraordinary Writ (talk) 02:40, 12 January 2025 (UTC)
- Thanks. ''']''' (talk • contribs) 02:46, 12 January 2025 (UTC)
Content removal, POV pushing, edit warring
Please use the existing thread rather than creating new ones. Star Mississippi 15:14, 12 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
@Taha Danesh removing content and POV pushing here and is currently edit warring Montblamc1 (talk) 10:52, 12 January 2025 (UTC)
- This looks like the same complaint as Misplaced Pages:Administrators' noticeboard/Incidents#Report on Disputed Edits and Insults. Let's centralise discussion there. I note that Talk:Mohammed Ridha al-Sistani is also empty. Phil Bridger (talk) 11:19, 12 January 2025 (UTC)
Tulsi (unblock request)
User unblocked. arcticocean ■ 12:25, 16 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
- Tulsi (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- Blocked (indef) on 3 April 2024 (9 months ago) by Rosguill during an AN thread (archived thread) for undisclosed paid editing
- Subsequent unblock request was also considered at AN before being declined (archived thread)
Tulsi has now submitted an unblock request which I am copying:
Dear Sysops,
I sincerely apologize for my past actions, which were problematic and deceptive. I fully understand the concerns raised, and I deeply regret my involvement. On April 3, 2024, my account was blocked by Rosguill in relation to undisclosed paid editing associated with the Misplaced Pages:Administrators' noticeboard/Archive361 § DIVINE and Tulsi: COI/UPE/quid-pro-quo editing, association with threats and harassment. However, I want to clarify that my involvement in these matters was minimal, with only minor interactions in the past. I have never written articles for payment, and I do not support paid editing.
The issues in question occurred in 2020 or 2021, prior to the block. At that time, I admitted my conflict of interest (COI) and disclosed it on the relevant article talk pages. Following discussions, my global and local rights were removed, but the block was not enforced until two years later. Many of the articles in question were deleted, so I did not find it necessary to disclose anything further. Moving forward, I have no intention of creating or editing COI-related articles. However, if I am ever in a situation where I am required to contribute to such an article, I will ensure full disclosure on the article talk page and submit it for review, as I did with the article Talk:Ghero.
While I respect Rosguill’s decision to impose a block after the two-year gap, I understand that a block serves to prevent disruption rather than punish. I have learned valuable lessons from this experience, and my contributions over the past two years reflect this growth. In this time, I have created over 80 articles, all without any undisclosed paid editing or COI involvement. Additionally, I have contributed to patrolling, as seen in the Twinkle and Draftify logs, and I have reported several violations on WP:UAA.
I acknowledge that I was not fully familiar with Misplaced Pages's policies in the past, but I have since taken the time to understand them better. I have been an active and committed user since October 2014, with significant contributions across various Wikimedia projects. I have also served as a sysop on Wikimedia Commons, Meta-Wiki, MediaWiki, and the Maithili and Nepali Wikipedias.
I am requesting an unblock because I am fully committed to abiding by all the established policies moving forward, and I am eager to contribute here in a constructive manner. Please kindly allow me a second chance.
Thank you for your consideration. I humbly request your reconsideration and the restoration of the editing privileges on my account on English Misplaced Pages.
Sincerely,
Having had discussions with the blocking admin, we would like to seek community comments on the unblock request.
Tulsi was blocked after UPE allegations that had been outstanding for around 2 years essentially caught up with them. They have now attested to having never edited for pay, which was the question they originally failed to answer twice (first thread, second thread), leading to the block. In the unblock request, they give a sincere undertaking not to engage in any more UPE.
They have created several dozen articles about Nepalese politicians but these seem to be innocuous. I have identified only a handful of articles where Tulsi could have edited for pay. Given the amount of other contributions Tulsi has made, it would be appropriate to give the benefit of the doubt. arcticocean ■ 15:14, 12 January 2025 (UTC)
- I cannot find the link for "A related meta-wiki discussion". killer bee 15:35, 12 January 2025 (UTC)
- I've deleted those words. I had decided not to include them in my post, but accidentally left them in. For interest, the discussion was this one: m:Requests for comment/Tulsi advanced permissions and UPE. arcticocean ■ 15:38, 12 January 2025 (UTC)
- Support per WP:SO. I will AGF that Tulsi will keep his promise not to engage in any COI editing going forward. voorts (talk/contributions) 16:07, 12 January 2025 (UTC)
- Question: We are all volunteers here, so the applicant's comment
if I am ever in a situation where I am required to contribute to such an article
(emphasis mine) is worrisome within the context of UPE/COI. Could they, or someone else for that matter, provide some clarification? JoJo Anthrax (talk) 19:57, 12 January 2025 (UTC)- I assume "required" is just poor phrasing and refers to circumstances similar to the example provided in the same sentence you quote. In any event, the second part of the sentence states
I will ensure full disclosure on the article talk page and submit it for review
(emphasis added). That promise is enough for me. voorts (talk/contributions) 21:00, 12 January 2025 (UTC)
- I assume "required" is just poor phrasing and refers to circumstances similar to the example provided in the same sentence you quote. In any event, the second part of the sentence states
- Support, we should generally give a second chance to users who have greatly and fundamentally changed in several months. Given that the user acknowledged the block and promised not to engage in undisclosed paid editing, not to mention that the user is trusted elsewhere, I see no reason to oppose. ToadetteEdit (talk) 20:48, 12 January 2025 (UTC)
- Support I believe in their ability to address any concern in the future, given that they served as a sysop on Wikimedia Commons, Meta-Wiki, MediaWiki, and the Maithili and Nepali Wikipedias. Kenneth Kho (talk) 21:44, 12 January 2025 (UTC)
- Support A second chance promises that Tulsi will not do highly undisclosed paid editing. I may partially support a topic ban on Nepalese politics against Tulsi. Ahri Boy (talk) 05:56, 13 January 2025 (UTC)
- Support Make the most of the second chance Buffs (talk) 23:05, 14 January 2025 (UTC)
- Support I had already been kind of watcxhing the discussion on their talk page over the last few days, and agree with an SO unblock. Beeblebrox 23:34, 14 January 2025 (UTC)
Abner Louima
Snow in the forecast. - The Bushranger One ping only 22:08, 13 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
I can't believe this article's AfD is still up and not closed as a WP:SNOW keep. The nominator has acknowledged his mistake out of ignorance. He was in middle school when the subject first became notable, and never heard of him. If the media, or God forbid, Social Media, discovers this nomination, it will do great harm to the reputation of the Misplaced Pages community as being collectively ignorant or much, much worse. I used to be an administrator, and would have closed this as keep. Please do something! Bearian (talk) 16:22, 13 January 2025 (UTC)
- Anybody can close an AfD as SNOW keep. That's the whole point of SNOW. voorts (talk/contributions) 16:25, 13 January 2025 (UTC)
- Snowed by me. — rsjaffe 🗣️ 16:35, 13 January 2025 (UTC)
- Thank you!!! Bearian (talk) 16:38, 13 January 2025 (UTC)
- Snowed by me. — rsjaffe 🗣️ 16:35, 13 January 2025 (UTC)
Request for Administrator Review of Repeatedly Declined Draft: Ario Nahavandi
Spam, spam, glorious spam. - The Bushranger One ping only 03:25, 15 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
Dear Administrators,
I am writing to request your assistance regarding my draft, Draft:Ario Nahavandi, which has been repeatedly declined over the past year despite my adherence to Misplaced Pages’s guidelines.
Over the course of several months, I have worked diligently to gather reliable, published, and independent sources, including magazine articles and other credible publications, that meet Misplaced Pages’s notability criteria. My most recent submission was declined in less than an hour—a timeframe that strongly suggests it was not even reviewed carefully or thoroughly.
This is particularly frustrating as I see numerous approved articles on Misplaced Pages that cite sources far less reliable or even completely broken. In contrast, my article contains verifiable references that adhere strictly to Misplaced Pages’s policies. This inconsistency feels unfair and raises concerns about bias in the review process.
I have followed all guidelines in good faith and cannot accept decisions that appear to be based on personal opinion rather than policy. It feels as though my article is being subjected to an unjust standard, especially when compared to articles that seem to bypass scrutiny. I genuinely wonder if this process is influenced by factors beyond content quality, as I have no means to “pay” for an article to be published, unlike some others.
I kindly request that an administrator reviews my draft with impartiality and provides clear, actionable feedback. Otherwise, I am truly exhausted by the repeated rejections and dismissals with no valid reasoning.
To provide context, here are some of the sources I included:
• https://www.nationaldiversityawards.co.uk/awards-2024/nominations/ario-nahavandi/
• Taurus Magazine (2024-11-19). "Ario Nahavandi". Taurus Magazine. 88: 7 – via www.magcloud.com
• 6x Magazine (2024-11-22). "Ario Nahavandi; The Persian Icon". 6X Magazine. 432: 6–7 – via www.magcloud.com
Thank you for your time and consideration xx
Lanak20 (talk) 23:47, 14 January 2025 (UTC)
- Administrators cannot override draft declines, and in fact the administrator toolset cannot be used to force content decisions. —Jéské Couriano v^_^v 23:51, 14 January 2025 (UTC)
- So who can I turn to for help? If administrators cannot assist in overriding the draft declines, to whom can I escalate this issue? I am deeply concerned that my article has been repeatedly declined without proper consideration of the sources I’ve provided. These sources are reliable, published, and fully comply with Misplaced Pages’s guidelines, yet they continue to be dismissed without even being properly reviewed.
- It’s becoming clear that the rejection process isn’t being carried out fairly. I can’t help but feel that my article is being judged based on factors other than content quality, especially when I see articles approved with far less solid references.
- I understand that the review process is based on policy, but when it seems clear that my draft isn’t being given the attention it deserves, I need to know where I can seek help to ensure fairness.
- I kindly ask for your guidance—if administrators cannot intervene, who can I turn to for proper support in getting this article reviewed fairly?
- Thank you for your time. Lanak20 (talk) 00:08, 15 January 2025 (UTC)
- WP:TEA. This is where you appeal problems with submissions of drafts. You should read the WP:NPEOPLE and WP:BLP carefully. Ahri Boy (talk) 00:20, 15 January 2025 (UTC)
- @Lanak20: I actually just went over your sources. They're all malformed at best and unusable at worst. What is your connexion to Nahavandi? —Jéské Couriano v^_^v 00:20, 15 January 2025 (UTC)
- I've blocked the OP as a spam-advertising-only account. I should add that it's pretty obvious they've used other accounts to promote this person, I believe most recently as of last October.--Bbb23 (talk) 00:25, 15 January 2025 (UTC)
Your Friendly Neighborhood Sociologist Edit Restriction Appeal
Unanimous consent after 36 hours to lift the restriction. Primefac (talk) 14:25, 16 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
A bit over a year ago, with near unanimous support, I appealed a TBAN from GENSEX - receiving in its place the following sanctions 1RR restriction in both the GENSEX and AMPOL topics; is limited to 0RR on articles for organizations/activists who are affiliated with anti-transgender activism or gender-critical feminism, broadly construed; and has a PBAN from Kellie-Jay Keen-Minshull.
Previous discussions are linked there. I am now requesting that my restrictions be dropped entirely because I have grown considerably as an editor, both since my initial TBAN when I'd just turned 19 and since the appeal.
I translated Transgender history in Brazil (having originally wrote it on eswiki during my TBAN) and made it my first GA. I uploaded multiple colorized photographs of transgender historical figures to commons I improved LGBTQ rights in New York and wrote articles for famous trans activists Cecilia Gentili and Carol Riddell. I also cleared up serious BLP violations at Aimee Knight and rewrote the article. I also helped expand Trans Kids Deserve Better and wrote Bayswater Support Group. I improved Rapid-onset gender dysphoria controversy and conversion therapy. I improved gender dysphoria in children. I rewrote and considerably expanded WPATH as well as Gender Identity Development Service. I expanded the article on the Cass Review. I wrote the article on the 1970 semi-governmental report Evaluation of Transsexual Surgery. I expanded the articles on Stephen B. Levine and Kenneth Zucker. I rewrote Detransition to follow WP:MEDRS and use systematic reviews instead of primary studies. Most proudly, I wrote Transgender health care misinformation and took it to GA - this is particularly relevant as a key part of the original TBAN discussion was whether my commitment to removing misinformation from Misplaced Pages was a case of either WP:RGW or following WP:NPOV and WP:FRINGE.
I believe the restrictions impair my ability to edit productively. I generally edit with 1RR regardless of sanctions. With 0RR, as Red-tailed hawk noted at my previous appeal "they can wind up restricting the sorts of partial reverts that are often a healthy part of the ordinary editing process." With 0RR, I am unable to engage in the BRD cycle properly and always second-guessing whether a partial edit to a recent edit counts as a revert or not. It also prevents me reverting drive-by SPA/IP povpushing. I don't plan to ever edit KJK's article again, but I believe that my record of neutral constructive editing shows the PBAN is no longer preventative or necessary. In the highly unlikely event I ever see a reason to edit it in future, I know my edits would be subject to heightened scrutiny which I'd welcome.
I appreciate your consideration. My best regards, Your Friendly Neighborhood Sociologist ⚧ Ⓐ (talk) 01:02, 15 January 2025 (UTC)
- Support. voorts (talk/contributions) 01:25, 15 January 2025 (UTC)
- Support. Based on YFNS's activity since the original tban, I don't see any reason to believe that restrictions are necessary going forward. Thebiguglyalien (talk) 06:34, 15 January 2025 (UTC)
- Support. Welcome back comrade. Ahri Boy (talk) 06:56, 15 January 2025 (UTC)
- Support based on their editing activity between TBAN and last year, as well as between the sanctions and now. Good work, and a great example of how this restorative process is supposed to work. May you inspire other misguided people to a path of restoration. TiggerJay (talk) 08:27, 15 January 2025 (UTC)
- Snow Support Kenneth Kho (talk) 14:15, 15 January 2025 (UTC)
- Strong support. To me YNFS comes across as a very responsible editor and I believe these restrictions are no longer warranted. HenrikHolen (talk) 16:09, 15 January 2025 (UTC)
- Support I remember the original ban happening due in large part to canvassing on twitter, the fact that any restrictions remained in place thereafter strikes me as a deep miscarriage of justice. Snokalok (talk) 23:26, 15 January 2025 (UTC)
Query Does your reference to BRD mean that you undertake to follow it in the future? Sweet6970 (talk) 14:17, 15 January 2025 (UTC)
- Enthusiastic support YFNS is a perfect model of an editor who is an asset to Misplaced Pages. Simonm223 (talk) 15:17, 15 January 2025 (UTC)
- Support A well worded appeal, worth giving another chance. — The Hand That Feeds You: 18:20, 15 January 2025 (UTC)
- Support This is a convincing and sincere appeal. Cullen328 (talk) 00:22, 16 January 2025 (UTC)
- Support, Welcome. ~🌀 Ampil 02:33, 16 January 2025 (UTC)
- Support as they have convincingly demonstrated change. TarnishedPath 02:53, 16 January 2025 (UTC)
- Support I supported and still support the original restrictions, and the later now appealed restrictions. I think YFNS's case has shown that an editor can come back from the brink successfully and am happy that happened. Nil Einne (talk) 04:00, 16 January 2025 (UTC)
Copyvio Problem
Hey all, I believe that these three diff should be redacted as copy vio's, thanks. There are several sentences which are directly lifted from the sources. Some one more experienced should likely have a look through the revision I restored as well. I didn't spot anything, but I may have missed something.
Kingsmasher678 (talk) 22:35, 15 January 2025 (UTC)
- To be clear, I don't think that @YatesTucker00090 is really at any fault here.
- Kingsmasher678 (talk) 22:37, 15 January 2025 (UTC)
- @Kingsmasher678 please see {{copyvio-revdel}} on how to tag copyvios for attention. Nthep (talk) 08:04, 16 January 2025 (UTC)
Lardlegwarmers block appeal
Essentially unanimous consensus to not unblock. RoySmith (talk) 15:53, 17 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
- Lardlegwarmers (talk · contribs · deleted contribs · logs · filter log · block user · block log)
I blocked Lardlegwarmers yesterday for one week for a violation of their community topic ban from COVID-19. This was about this edit, although I subsequently noticed this one as well. LLW has asked me to copy their appeal here. -- Tamzin (they|xe|🤷) 03:00, 16 January 2025 (UTC)
Statement from Lardlegwarmers
I have only been very active editing Misplaced Pages for about one month, even though my account is older. I was blocked for pushing a minority POV in the talk page for Covid-19 Lab Leak Theory, which I understand. For context, this issue wouldn't have even come up at ANI except that there was this very old account making borderline uncivil comments constantly, and I took them to ANI myself and it boomeranged. One thing that I learned from that experience is that Misplaced Pages's culture sort of revolves around social dynamics and politics, which can overshadow fairness and consistency in rule enforcement, and that I am probably not going to be the one to fix it. Anyways, in my defense, I didn't learn until later that my attempt to reason things out like grownups was not allowed; my edits were in good faith and I was really just attempting to talk it out with the other editors who did not agree with me. But I understand that the norm in this space is to walk away if there isn't any uptake of my ideas or take it to dispute resolution instead of continuing to try to convince people. The current ban is for making a comment on an AE thread, not a Covid-19 article. I was on the page for a totally unrelated reason and noticed that a user I recognized from the Covid thread was being discussed. My comment was mostly about user behavior and reflecting on the underlying dispute itself, not Covid-19. Also, on my user page I quoted Larry Sanger discussing his view on Misplaced Pages's approach to Covid-19 , which I'd assumed was permitted because it's my own user page and it's really a comment about the state of Misplaced Pages as a whole. The admin who blocked me, @Tamzin, blanked it from my user page. If the community won't let me keep that quote on my user page, then fine, we'll leave it removed, but I wish they would have just asked me to remove it and described why instead of editing my user page. A block for this stuff seems harsh. Thanks.
References
Statement from Tamzin
Excerpting my comment on their talkpage:-- Tamzin (they|xe|🤷) 03:00, 16 January 2025 (UTC)Usually we only warn someone on their first topic ban violation. However, in your case, the fact that both violations occurred within hours of the ban being imposed, and that they were belligerent rants treating Misplaced Pages as a battleground, made me judge that a short block would more clearly communicate just how far you are from what is considered acceptable conduct. Even if you didn't understand that the ban applied outside articles, you should have understood that the community found your editing about COVID disruptive, which should have been reason enough to not make those edits.
Discussion among uninvolved editors
- This is clearly a topic ban violation - and it came less than a day after it was imposed. Even if assuming in good faith that they didn't know it was a topic ban violation, their unblock request shows not only that they don't understand what they did wrong, but they attempt to justify it with statements such as
Anyways, in my defense, I didn't learn until later that my attempt to reason things out like grownups was not allowed
which is borderline a personal attack (veiled insult that others weren't being grownups);which can overshadow fairness and consistency in rule enforcement
which is confirming they still don't understand why they were topic banned nor why they were blocked for violating it; and quoting Larry Sanger's fringe theory promoting comments on their userpage after their topic ban. To summarize, I have no confidence that the user understands what they did wrong, and I would go so far as to say the user attempting to skirt the edges of their topic ban and supporting another user trying to promote fringe theories on Misplaced Pages merits an indefinite community ban. TLDR: Oppose unblock and ultimately would support indefinite ban due to the flagrant violation, lack of understanding, and no belief that after the 7 days is up they will not go straight back to trying to right what they percieve as a great wrong. I won't be the one to propose that, however. -bɜ:ʳkənhɪmez | me | talk to me! 03:10, 16 January 2025 (UTC) - I don't see how an unblock is possible when Lardlegwarmers clearly still doesn't understand what a broadly construed topic ban means. To be clear, there's no need to ask the "community" whether you can keep your topic ban violation. The only hope for you to be able to obey it is if you are able to decide yourself, especially after you've been told by an admin. While we do try to educate instead of just blocking, the "community" isn't here to help you understand the limits of your topic ban. Nil Einne (talk) 04:01, 16 January 2025 (UTC)
- Should clarify that despite what I said above, I'd weakly oppose extending the topic
banblock to indefinite at this time. While I'm not hopeful Lardlegwarmers is going to be able to obey it given what they've said, I think it's fine to give them rope after thebanblock expires and apply normal escalating blocks. Since we're already here, perhaps this will somehow help them understand that yes the community requires you to apply it broadly on anything to do with COVID-19 throughout Misplaced Pages. They should consider this very short rope though and notably the next time they feel they need to ask the community whether they're violating their topic ban when they are, it might be the last time. Nil Einne (talk) 20:38, 16 January 2025 (UTC)- Sorry mixed up ban and block above twice, now fixed. Nil Einne (talk) 01:45, 17 January 2025 (UTC)
- Should clarify that despite what I said above, I'd weakly oppose extending the topic
- Oppose unblock as the user looks to have no intention of following Misplaced Pages guidelines with their request. It is only a week and will give a change to think about how to change. Graeme Bartlett (talk) 04:13, 16 January 2025 (UTC)
- Oppose unblock. It truly takes some chutzpah to cite a Signpost piece authored by the admin who blocked you to support the proposition that you're being railroaded. Weak support for an indef because that's what Lardlegwarmers seems to be speedrunning. voorts (talk/contributions) 04:30, 16 January 2025 (UTC)
- Oppose unblock. The topic ban was on the topic of COVID-19, broadly construed, not the topic of COVID-19 directly in articlespace. And the topic ban was violated, not just within less than a day, but within three hours of it being imposed. On top of that the unblock request could be a case study for WP:NOTTHEM. I won't call for an indef yet, but when the block expires Lardlegwarmers should bear in mind that any further violations of the topic ban will be their last. - The Bushranger One ping only 10:10, 16 January 2025 (UTC)
- No unblock - Basically per Lardlegwarmers: they don't appear to understand why they've been blocked. An indefinite block seems very likely in this editor's future and we certainly should consider cutting out the middle-man and just skipping to it, but I'd like to give them at least some chance here to understand why they were blocked. FOARP (talk) 10:12, 16 January 2025 (UTC)
- Oppose unblock - While I usually support giving editors WP:ROPE to demonstrate improvement, this case warrants a longer wait. The user acknowledges pushing a minority POV and failing to disengage per WP:DISPUTE norms, but their justification suggests a lack of understanding or acceptance of policies like WP:NPOV, WP:CIVIL, and WP:NOTHERE. Their off-topic comment in an AE thread, despite knowing the sensitivity of such spaces, and the policy-violating content on their user page, further reflect ongoing disruption. I recommend they take time to reflect and gain a better grasp of Misplaced Pages's collaborative culture before requesting an unblock again. Footballnerd2007 • talk ⚽ 11:31, 16 January 2025 (UTC)
- Oppose unblock. I agree that absent change from this user an indefinite block is likely. For their benefit, if you're the subject of a topic ban, broadly construed, about COVID-19, you need to be editing in an entirely different topic area. Think of something that you're interested in--television shows, football, English gardens, science fiction books? Take a week and think on it. Mackensen (talk) 11:42, 16 January 2025 (UTC)
- Oppose unblock. What is there left to say? This conduct feels like appellant's purpose is use Misplaced Pages as a battleground and to soapbox their views rather than to build the encyclopedia-- to remake Misplaced Pages as they think it should be. My feeling is that a week won't be nearly enough. The railroad comment is appallingly full of not understanding that their conduct is not acceptable in a collaborative project. -- Deepfriedokra (talk) 12:28, 16 January 2025 (UTC)
- PS: What Tamzin said in her statement above. -- Deepfriedokra (talk) 12:33, 16 January 2025 (UTC)
- Whilst I don't believe user will be able to change their approach, I feel an indef would be premature for now. We should give them a chance to mend their ways. -- Deepfriedokra (talk) 12:44, 17 January 2025 (UTC)
- PS: What Tamzin said in her statement above. -- Deepfriedokra (talk) 12:33, 16 January 2025 (UTC)
- An account that exists only to push a particular POV across several articles is topic banned, violates that topic ban immediately, and posts a battlegroundy unblock request that thoroughly misses the point. Whoever closes this should be considering indef, not an unblock. — Rhododendrites \\ 13:57, 16 January 2025 (UTC)
- Indeed. -- Deepfriedokra (talk) 14:55, 16 January 2025 (UTC)
- Oppose unblock this specific response
Misplaced Pages's culture sort of revolves around social dynamics and politics, which can overshadow fairness and consistency in rule enforcement
is indicative of their viewpoints and why they're not ready to contribute. They continue,my attempt to reason things out like grownups was not allowed
. These demonstrate that they still do not get it, and rather project their self-perspective is that they are actually a victim of people who are abusing the rules against them. . I proffer that this is going to be a consistent problem until they acknowledge that they were violating policy. Zero indication that they know how to positively contribute, just perhaps a vague inference that they'll avoid getting in trouble -- because -- we'll I'm not entirely sure they've communicated what they will do differently, but rather simply say thata block for this stuff seems harsh.
TiggerJay (talk) 15:12, 16 January 2025 (UTC)- Notwithstanding the harsh situation I presented above, to be clear I oppose indef for now. A new user should have the opportunity to overcome early (while significant) setbacks, which is what TBANs are designed to encourage. I am encouraged by things like YFNS corrective behavior in a prior AN discussion, and can only be hopeful and AGF that might apply to LLW here. We need more passionate, subject matter experts, as contributors to this project, but they absolutely must contribute positively and following established PGs. TiggerJay (talk) 16:34, 16 January 2025 (UTC)
- Oppose unblock and support an indef. I am pretty confident in saying that this is where we will be heading after this block ends. RickinBaltimore (talk) 15:20, 16 January 2025 (UTC)
- Oppose unblock, clear violations of the topic ban. Don't oppose indef, but I'd like to at least give him the chance to figure out exactly what we expect going forward. --SarekOfVulcan (talk) 15:52, 16 January 2025 (UTC)
- Support block, oppose unblock, oppose indef - this is a topic-banned newbie's first violation, in the heat of the moment after the restriction was imposed. Tamzin's block was the appropriate response. The unblock request is wholly inadequate, but jumping straight to indef for this sort of violation is a pretty extreme overreach. If they go back to violating their sanction after this block expires, then let's talk community ban, but they should be given the opportunity to edit constructively while respecting the restriction. Ivanvector (/Edits) 16:07, 16 January 2025 (UTC)
- Oppose unblock, oppose indef...however... I am sympathetic to their point of view and their general "right" (we don't really have rights here on WP) to post their opinion on a subject, even one as contentious as COVID-19. I think the blanking of the user page is a step too far. We shouldn't be in the business of deleting negative opinions about Misplaced Pages; while the statement was in reference to COVID-19, it doesn't mention it within the claim and is more a critique of Misplaced Pages at large and mass media than its relation to COVID. I would let the statement on their user page stand/restore it. Larry Sanger's statement is not a fringe theory, it is a reasonable opinion. There were loads of statements/claims about COVID/its origin/mandates/treatment/vaccines that, despite their widespread implementations and presentation as "the science", later turned out to be misleading or untested conjecture (examples: no studies on masking effectiveness with a large population vs the coronavirus, 6 foot spacing, lying to the American public about wearing masks because health care professionals needed them more, lab leak theory, military connections to the Wuhan Institute, US funding of WI, etc). HOWEVER, civil discourse is essential. That means that discussions about COVID were fraught with battlegrounds and bludgeoning. As such, we have additional restrictions for COVID discussions and other contentious topics and LLW needs to follow them. LLW did not do so and has shown a consistent flaunting of these restrictions and a weeklong block is a reasonable start. In summary, the quote isn't unreasonable to leave on their user page (give them that latitude), but a weeklong block for the other behavior should stand. Buffs (talk) 16:15, 16 January 2025 (UTC)
- They added two comments to their userpage. Both were critical of Misplaced Pages. One was also critical of Anthony Fauci and other aspects of the US government's COVID response. I removed the latter. It doesn't matter whether Sanger's opinion is fringe or not; what matters is that he was talking about COVID. I would be quite the hypocrite to remove something from someone's userpage just for criticizing Misplaced Pages, as I have a fair bit of that on my own userpage. -- Tamzin (they|xe|🤷) 17:02, 16 January 2025 (UTC)
- There's some pretty big overlap there in criticism of Fauci and how it is handled on Misplaced Pages. Again, I don't feel THAT is a significant violation of COVID editing restrictions (beyond the fact that they did it despite such an editing restriction). Anyone can completely skip over it if they wish. @Tamzin: playing devil's advocate for a moment, what if I published the same thing on my user page? Would it be ok? Would it be ok if I posted it on LLW's user page (as long as LLW was ok with it, of course)? I realize we're getting in the weeds of a "what-if..." but if so, what's the substantive difference between me putting it on a user page and LLW doing the same? Buffs (talk) 17:19, 16 January 2025 (UTC)
- If you posted it to your userpage, it would be fine (although not that constructive), because you are not topic-banned from COVID. If you posted it to their userpage, that would be WP:PROXYING for a banned editor, since I'd struggle to believe you have an independent reason to think that particular quote belongs on that particular page. If you really want to fight the removal from the userpage, feel free to create a subsection here, but I stand by the removal. -- Tamzin (they|xe|🤷) 17:29, 16 January 2025 (UTC)
- I'm not fighting the removal per se. Just wondering where the boundaries are and if it's wise to have such a boundary. Buffs (talk) 17:55, 16 January 2025 (UTC)
- The boundary is WP:TBAN. -- Tamzin (they|xe|🤷) 19:17, 16 January 2025 (UTC)
- I'm not fighting the removal per se. Just wondering where the boundaries are and if it's wise to have such a boundary. Buffs (talk) 17:55, 16 January 2025 (UTC)
- Buffs: In the realm of hypothetical I would presume that if that quote had been on LLW user page for a long time, in a sea of content, pre-existing AN, then it might even still be up today. However, on the other hand, to post that after the TBAN was imposed is nothing other than what can be seen as abject defiance to the ban. But beyond that, it simply violates plain language of the ban, as it applies to
all pages (not only articles) broadly related to the topic
, so I proffer that Tamzin is clearly in the right here. To your charged statement about if you were to post the same thing to your user page, prior to your statement here and presuming you were not under a TBAN, it would not be questioned one iota. However, as a response to this discussion, it could be construed (but not technically violating) the principles of WP:PROXYING and I would caution against it. Moreover, you reinstating it on LLW talk page would be a far closer in the proximity of violating PROXYING. TiggerJay (talk) 18:49, 16 January 2025 (UTC)- The fact that the comment only came after the topic ban is key here. I'm fairly sure I've seen several cases where there's something on an editor's user page which is covered by a topic ban but which no one has said or done anything about because it was there from before the topic ban. In fact I'm fairly sure I even remember a case where someone asked specifically if they could modify or remove something on their user page which related to their talk page which was technically under the topic ban (probably gensex). I think this was allowed especially since it related to their personal life rather than some comment on something, although they were told just this once is best. There might have even been a case where an editor wanted to do some more editing or formatting of something under their topic ban and was either denied or told only this once. IIRC, there was also an editor who was happy to be able to finally change someone on their userpage covered by their topic ban once it was lifted. A topic ban is a topic ban. I'd note that if someone makes an extremely constructive edit to an article that is not covered by WP:BANEX we still treat this as a topic ban violation, although it's something much more beneficial for the project than an editor being able to repost random ramblings about Misplaced Pages they want to share. Nil Einne (talk) 20:31, 16 January 2025 (UTC)
- If you posted it to your userpage, it would be fine (although not that constructive), because you are not topic-banned from COVID. If you posted it to their userpage, that would be WP:PROXYING for a banned editor, since I'd struggle to believe you have an independent reason to think that particular quote belongs on that particular page. If you really want to fight the removal from the userpage, feel free to create a subsection here, but I stand by the removal. -- Tamzin (they|xe|🤷) 17:29, 16 January 2025 (UTC)
- There's some pretty big overlap there in criticism of Fauci and how it is handled on Misplaced Pages. Again, I don't feel THAT is a significant violation of COVID editing restrictions (beyond the fact that they did it despite such an editing restriction). Anyone can completely skip over it if they wish. @Tamzin: playing devil's advocate for a moment, what if I published the same thing on my user page? Would it be ok? Would it be ok if I posted it on LLW's user page (as long as LLW was ok with it, of course)? I realize we're getting in the weeds of a "what-if..." but if so, what's the substantive difference between me putting it on a user page and LLW doing the same? Buffs (talk) 17:19, 16 January 2025 (UTC)
- They added two comments to their userpage. Both were critical of Misplaced Pages. One was also critical of Anthony Fauci and other aspects of the US government's COVID response. I removed the latter. It doesn't matter whether Sanger's opinion is fringe or not; what matters is that he was talking about COVID. I would be quite the hypocrite to remove something from someone's userpage just for criticizing Misplaced Pages, as I have a fair bit of that on my own userpage. -- Tamzin (they|xe|🤷) 17:02, 16 January 2025 (UTC)
- Oppose unblock, oppose indef - The topic ban violation was clear cut. Let's hope Lardlegwarmers will read a bit about how to avoid topic ban violations, or else indef block is not too far for them. Lorstaking (talk) 16:19, 16 January 2025 (UTC)
- Oppose unblock, extend block indefinitely - Lardle should try to demonstrate good behavior on another wiki for six months before asking for a SO. Let's hope that this user should handle contentious topics carefully in the future. Ahri Boy (talk) 18:35, 16 January 2025 (UTC)
- Oppose unblock but no reason to indef, a block has already been imposed. If the user continues to violate the TBAN, than a longer block might be warranted. JayCubby 02:43, 17 January 2025 (UTC)
Comments from involved editors
- Going to open a new subsection here since I've made comments to Talk:COVID-19 lab leak theory two weeks ago. I wish I could say I was surprised that this ended in tears but that would be untrue (though I did have some hopes the comment a month ago indicating they were aware pro-fringe POV-pushing was sactionable was a signal they were intending to modify their behaviour). As bɜ:ʳkənhɪmez points out, making thinly veiled attacks is not exactly the type of thing looked favourably upon in an unblock request. Nor is making polemical statements on one's user page, whether within the scope of the ban or not, likely to convince the community of one's inclination and ability to be a productive editor. Lardlegwarmers, if you do really want to return to editing, especially if you want to appeal your topic ban in 6 months or a year, I would strongly advise reading Misplaced Pages:Guide to appealing blocks and following the advice there, especially WP:NOTTHEM. Complaining about Hob's conduct won't help you here, because the block (and it's a rather short one) and ban are about you, not Hob. Given your comment that
apparently two wrongs make a right
, I had hoped that you were already also considering your own behaviour, but I would like to make it very clear: taking the role of one of the "wrongs" to address someone else's "borderline uncivil" behaviour is not itself considered acceptable behaviour. Whether Hob crosses the line is on them, but what you do is entirely on you. Alpha3031 (t • c) 07:16, 16 January 2025 (UTC) - As I was involved in the discussion to topic ban LLW I think I count as an involved editor. With that said I would discourage an early lifting of this block, which seems appropriate considering that LLW's response to the topic ban was to immediately violate the topic ban. Simonm223 (talk) 13:54, 16 January 2025 (UTC)
- Also, perhaps LLW wasn't aware of this, but people who aren't uninvolved administrators aren't generally supposed to put comments into the "results" section of an AE filing. Simonm223 (talk) 13:57, 16 January 2025 (UTC)
- I was there.. Three thousand ye-- No. More like one, two days ago. I seriously believe Lard Leg Warmers is one of two situations: 1: WP:CIR and unable to understand the concepts of medical science as if they were a Facebook mother invested in "essential oils" and "holistic medicine" rather than trusting medical and scientific experts; 2: WP:NOTHERE and simply f
**king with us for no good reason and leading us around, and around, and around, and around, and around the bend because they get a rise out of it. Either way, my advice: don't get led around the bend, advise indef block for either WP:CIR or WP:NOTHERE. BarntToust 16:38, 16 January 2025 (UTC)
- BarntToust, those kinds of personal assumptions about their character are unnecessary to this discussion. Instead of speculation on who they are elsewhere, let's just focus on their behavior on Misplaced Pages. Liz 06:45, 17 January 2025 (UTC)
- Lardlegwarmers' statement clearly shows that they have learned little from the sanction. They should demonstrate such before there is any lifting. O3000, Ret. (talk) 18:55, 16 January 2025 (UTC)
Usage of 'Notable people' vis-a-vis 'Notable person' in section headers
This is not an administrative issue. voorts (talk/contributions) 20:56, 16 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
In the course of editing numerous articles, I have come across the header featuring 'notable people' when there is only one person and have therefore modified the grammar.
I recently had another editor come behind me and revert one such edit on the grounds that things have always been done this way, regardless of the number of notables for a given locale, which makes little sense to me. Is this really policy? Hushpuckena (talk) 16:45, 16 January 2025 (UTC)
- This seems like a question for WP:MOS, not WP:AN as it doesn't involve administrator actions. AN isn't a general Help forum for questions about editing. You could even try asking at the Teahouse or the Help Desk. Liz 19:00, 16 January 2025 (UTC)
Reporting Administrator Abuse
I'm going to do the OP a favor and close this with no action against them. Essentially, the OP's misbehavior was pointed out by Acalamari and the OP is trying to present it as Acalamri's misbehavior. If another administrator thinks sanctions against the OP are warranted, that's up to them.--Bbb23 (talk) 23:56, 16 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
User:Acalamari is abusing his moderator powers in order to post unconstructive comments on talk pages, specifically when we were talking about if we should delete the US 2028 election or not, he said "that Drumpf supporters want there to be no more elections so they can remain in power forever doesn't mean we adhere to their delusions by deleting articles here". This is clearly unconstructive, and treating the talk page as a forum. I didn't know he was a moderator when I was removing his comment, and now he left all of these messages on my page and is saying I'm the real vandal here. TopVat19sEver (talk) 22:48, 16 January 2025 (UTC)
- So there's two things here.
- First, TopVat19sEver, you removed other users comments from a talk page (not allowed). A user voicing their opinion is not vandalism, not in the slightest. If you have a problem with what another user has said on the talkpage, rather than removing their comment (which is only allowed in very specific situations), you should bring it for discussion at an appropriate noticeboard, or preferably ask them to change their own comment.
- Second, Acalamari, could you please refrain from calling people "Drumpf supporters" and casting aspersions on the reasons for nominating an article for deletion? While you're entitled to your opinions, that's borderline (at best) incivility, especially when you call them "delusional".
- If both users agree to accept what they did wrong here and move forward, I don't think any further action is necessary. -bɜ:ʳkənhɪmez | me | talk to me! 22:53, 16 January 2025 (UTC)
- Ok, I'm newer to Misplaced Pages, I understand what you are saying, my train of thought was, "this comment looks like vandalism, vandalism on Misplaced Pages is removed, therefore remove". I didn't know that they don't do that for talk pages. Thank you my friend. TopVat19sEver (talk) 22:59, 16 January 2025 (UTC)
- Vandalism has a very specific definition on Misplaced Pages - see this page for more information on what is not vandalism. Merely calling people names and/or being uncivil, while against the rules, is not vandalism. There are proper processes for handling other rule violations (such as asking someone to edit their own comments, or asking a noticeboard for help) such as those, but they are decidedly not vandalism. -bɜ:ʳkənhɪmez | me | talk to me! 23:01, 16 January 2025 (UTC)
- Ok thank you for telling me TopVat19sEver (talk) 23:02, 16 January 2025 (UTC)
- Vandalism has a very specific definition on Misplaced Pages - see this page for more information on what is not vandalism. Merely calling people names and/or being uncivil, while against the rules, is not vandalism. There are proper processes for handling other rule violations (such as asking someone to edit their own comments, or asking a noticeboard for help) such as those, but they are decidedly not vandalism. -bɜ:ʳkənhɪmez | me | talk to me! 23:01, 16 January 2025 (UTC)
- Ok, I'm newer to Misplaced Pages, I understand what you are saying, my train of thought was, "this comment looks like vandalism, vandalism on Misplaced Pages is removed, therefore remove". I didn't know that they don't do that for talk pages. Thank you my friend. TopVat19sEver (talk) 22:59, 16 January 2025 (UTC)
- Where are the diffs? M.Bitton (talk) 22:54, 16 January 2025 (UTC)
- This is a baseless complaint. Ater not editing for months, the OP refactored an AfD that was closed last November. Acalamari rightly warned them for doing that.--Bbb23 (talk) 22:56, 16 January 2025 (UTC)
- I agree, but at the same time, I think TV19E has a right to be unhappy that Acalamari, an administrator and bureaucrat, was able to cast aspersions and call people names without it being called out at the time as far as I can see. They went about it the wrong way (removing the comment), but that doesn't mean there isn't room for discussion of that comment. -bɜ:ʳkənhɪmez | me | talk to me! 22:58, 16 January 2025 (UTC)
- Nope. First, it doesn't rise to the level required of this noticeboard, and, second, it's not at all timely.--Bbb23 (talk) 23:01, 16 January 2025 (UTC)
- To be blunt, Acalamari didn't even tell the editor when they initially reverted back in November (while the discussion was open) where they could discuss further/report if they felt the comment was not appropriate. I'm not suggesting sanctions against Acalamari at all. But to tell a new editor "someone broke the rules and since you didn't report it in the proper way at the time because nobody told you how, they're allowed to break the rules" is clear biting the newbies. I think all that's necessary is an apology from Acalamari - TV19E has already explained that they were mistaken as to it being vanadalism. -bɜ:ʳkənhɪmez | me | talk to me! 23:03, 16 January 2025 (UTC)
- Nope. First, it doesn't rise to the level required of this noticeboard, and, second, it's not at all timely.--Bbb23 (talk) 23:01, 16 January 2025 (UTC)
- I didn't edit for a few months because I have to do other things. I was just scrolling around I don't even remember what I was doing and I saw he put it back, I didn't know he was a mod, and it also said you can't edit archived talk pages, which he did, so I reverted his edit. TopVat19sEver (talk) 23:03, 16 January 2025 (UTC)
- That's not true. You modified a closed AfD. Acalamari rightly reverted your edit of an archived discussion.--Bbb23 (talk) 23:06, 16 January 2025 (UTC)
- I just said, he is the one who modified a closed AfD, which is not allowed, then I reverted it not knowing he is a moderator TopVat19sEver (talk) 23:08, 16 January 2025 (UTC)
- He didn't modify a closed AfD. His comment was readded while the discussion was still open, because you removed it in violation of the very few circumstances where you are allowed to remove another editor's comment. -bɜ:ʳkənhɪmez | me | talk to me! 23:09, 16 January 2025 (UTC)
- Oh okay this is my mistake then I thought it was after the AfD was closed my bad TopVat19sEver (talk) 23:11, 16 January 2025 (UTC)
- Wait hold on, I just looked at it again. He added back his comment after the result was SNOW. On the page when he re added it, it said do not edit the page. TopVat19sEver (talk) 23:16, 16 January 2025 (UTC)
- You removed Acalamari's comment as vandalism with the edit summary "subhanAllah". You had no right to do that. Acalamari restored it, which even though the AfD was closed, they had the right to do in the circumstances.--Bbb23 (talk) 23:27, 16 January 2025 (UTC)
- https://en.wikipedia.org/search/?title=Misplaced Pages:Articles_for_deletion/2028_United_States_presidential_election_(3rd_nomination)&oldid=1257014612 Take a look, this is his edit. When he re added his comment, on the page in red it said Do not edit the page TopVat19sEver (talk) 23:18, 16 January 2025 (UTC)
- The comment never should've been removed in the first place. It's within the spirit of the rules to readd a comment that you improperly removed, even if the discussion had been closed in the meantime. -bɜ:ʳkənhɪmez | me | talk to me! 23:32, 16 January 2025 (UTC)
- He didn't modify a closed AfD. His comment was readded while the discussion was still open, because you removed it in violation of the very few circumstances where you are allowed to remove another editor's comment. -bɜ:ʳkənhɪmez | me | talk to me! 23:09, 16 January 2025 (UTC)
- I just said, he is the one who modified a closed AfD, which is not allowed, then I reverted it not knowing he is a moderator TopVat19sEver (talk) 23:08, 16 January 2025 (UTC)
- That's not true. You modified a closed AfD. Acalamari rightly reverted your edit of an archived discussion.--Bbb23 (talk) 23:06, 16 January 2025 (UTC)
- I agree, but at the same time, I think TV19E has a right to be unhappy that Acalamari, an administrator and bureaucrat, was able to cast aspersions and call people names without it being called out at the time as far as I can see. They went about it the wrong way (removing the comment), but that doesn't mean there isn't room for discussion of that comment. -bɜ:ʳkənhɪmez | me | talk to me! 22:58, 16 January 2025 (UTC)
- (edit conflict) There's no admin abuse here as no admin tools have been used. In case you missed "The following discussion is an archived debate of the proposed deletion of the article below" with the bright red "Please do not modify it" at that AfD, I'll repeat the instructions here - don't modify archived discussions.-- Ponyo 22:57, 16 January 2025 (UTC)
- I was saying Admin abuse because of the fact that he is able to keep his comment on the page when even if he is violating the rules. I'm not a moderator so I can't do anything about. Now I just learned from that guy that they don't remove comments even if its vandalism, now I know. But thats why I reported it here you know. TopVat19sEver (talk) 23:01, 16 January 2025 (UTC)
- He is the one who edited the closed AfD. This was one of the reason why I reverted his edit. TopVat19sEver (talk) 23:10, 16 January 2025 (UTC)
- It's very hard to work out what's happening without the presence of diffs. M.Bitton (talk) 23:02, 16 January 2025 (UTC)
without the presence of diffs
. But Ponyo and I have contributed, so you're in the presence of greatness; isn't that better than diffs? :p --Bbb23 (talk) 23:08, 16 January 2025 (UTC)- Tiggerjay is bowing down in great humility before such greatness never before seen in this universe. Now.... where is the trout? TiggerJay (talk) 23:24, 16 January 2025 (UTC)
- Who am I to disagree with the Jedi? M.Bitton (talk) 23:52, 16 January 2025 (UTC)
- Okay, I've looked into this. And...surprise surprise, TopVat19sEver was the one who origially removed Aclamari's !vote while the AfD was still open . Yes, about a day after the AfD was closed, Aclamari reverted this removal , which is technically "editing a closed AfD" but I would say they were entirely within their rights to revert a bad removal. And now, suddenly, today, two months later, as their first edit after having done that improper removal, TopVat19sEver goes back to the AfD and removes Aclamari's !vote again , which Aclamari - entirely rightfully - reverted , and then TopVat19sEver comes here to cry "admin abuse", when no administrative abilities were used at all in this whole mess. Could Aclamari have used more moderate language in their initial !vote? Yeah maybe, but it was no violation at all, and the only thing needed here is a WP:BOOMERANG or at least a {{trout}} for TopVat19sEver. - The Bushranger One ping only 23:27, 16 January 2025 (UTC)
Ban appeal from Rathfelder
- Rathfelder (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- Community banned in November 2022 for sockpuppetry, vote-stacking and undisclosed COI writing of a BLP attack page
- Appeal in January 2023 declined by the community
- Second appeal in October 2023 not submitted for review by the community for not complying with WP:GAB
Rathfelder has submitted the following ban appeal on their talk page and asked me to copy it here:
I realise that what I did was wrong - more wrong than I thought it was at the time. The circumstances which led me to edit pages where I was conflicted are not likely to recur. I accept that I was wrong to create sockpuppets and I apologise. I was involved in a dispute with my employers and it was very wrong of me to use Misplaced Pages as part of that. I did that really because I was trying to defend the work I had done for the Socialist Health Association for the previous 20 years. I did a lot of edits on that page, but they were, until the last few, about the history of the organisation, mostly adding to its list of distinguished members - largely before I was involved with it, and mostly before I was born. They were not at all controversial. I was unfairly sacked and my opponents started using Misplaced Pages against me. The row got into the media. I accept that I should not have done that. I should have resisted the temptation to use Misplaced Pages in the dispute.
I have spent 2 years working on Simple English and Wikimedia. I have not set up any sockpuppets or edited anything where I had conflicts. I plan to continue with Wikimedia, as there is plenty there to keep me busy, but I would like to be able, in particular, to add pictures to articles - now I have found my way round the enormous Wikimedia resource. I also sometimes come across articles in English wikipedia which need amendment.
Chaotic Enby (talk · contribs) 17:02, 17 January 2025 (UTC)
- Conditional support - If there's been no socking during the ban. GoodDay (talk) 17:05, 17 January 2025 (UTC)
- Question during the January 2024 unblock request Rathfelder said they would be willing to accept a restriction on editing articles related to BLPs or healthcare orgs. Are they still willing to accept those edit restrictions if they are un-banned? Furthermore, in January 2024 there was, at the time, no evidence of any further socking. Can we confirm that good behaviour has continued? Simonm223 (talk) 17:17, 17 January 2025 (UTC)
- Support They have been a very productive contributor at the Simple English Misplaced Pages, and it has definitely been long enough for the standard offer. QuicoleJR (talk) 21:33, 17 January 2025 (UTC)
Appealing April 4 2024, indefinite WP:CUP ban and indefinite 1-nomination GAN limit
Consensus to lift this ban will not develop. voorts (talk/contributions) 22:02, 17 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
At User_talk:TonyTheTiger#Topic_bans, I was instructed by closer User:Ingenuity that I could appeal these in a year and it has been 9.5 months. I am appealing because the CUP entry deadline is traditionally January 31. See Misplaced Pages:WikiCup/2020 signups through Misplaced Pages:WikiCup/2024 signups. This year the Misplaced Pages:WikiCup/2025 signups verbiage says "The competition will begin on 1 January 2025 and signups will continue throughout the year". I am just noticing the new language as I am putting this appeal in. Nonetheless, I am requesting time off for good behavior on the ban.-TonyTheTiger (T / C / WP:FOUR / WP:CHICAGO / WP:WAWARD) 18:52, 17 January 2025 (UTC)
- Oppose The utter cluelessness of this appeal is more than enough reason not to do this. I was going to write more but decided that coaching you on how to be less clueless is not in the project's best interest. You've been here long enough that you should be able to see for yourself how terrible this appeal is. Beeblebrox 19:02, 17 January 2025 (UTC)
- Oppose and recommend we disallow any further appeals for another year. I'm concerned otherwise we'll just be back here in April. --Yamla (talk) 19:14, 17 January 2025 (UTC)
- Oppose for now It's pretty clear that most people in that discussion were supporting an indef ban from the Cup, not an 8-month ban. This appeal doesn't address people's concerns with Tony's editing relating to the Cup, so should be denied. --SarekOfVulcan (talk) 19:16, 17 January 2025 (UTC)
- Oppose The original discussion wasn't linked, it can be found here. At that place it is very clear that
here is almost unanimous support for an indefinite ban on participation in the WikiCup
, so, no, this appeal should not be passed. It is, honestly, astonishing that TonyTheTiger has been here very nearly two decades but hasn't taken on board the way the community works ~ Lindsay 19:20, 17 January 2025 (UTC) - Oppose for no rational that they understand why they were banned or what even led to their ban, and rather simply a sentiment of "I really want to participate". Please understand that your ban was indefinite, so the one year appeal opportunity is your potential opportunity "time off for good behavior". TiggerJay (talk) 19:24, 17 January 2025 (UTC)
- Oppose. Appealing early on the basis that you won't be able to sign up to do the thing you were banned from doing is certainly a unique take. ♠PMC♠ (talk) 21:03, 17 January 2025 (UTC)
Requesting info
Steve Quinn is trouted for bringing this to AN. voorts (talk/contributions) 21:58, 17 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
Hello. I have come across several image files and the U.S. Gov. PD licensing seems to be incorrect. Four of these images and possibly another one could be copyright violations - if I can figure out how to find this type of information on their websites. However, since I am unable to find that information at this moment, I am wondering which group of Misplaced Pages editors work on this sort of thing so that maybe I can get some help with this. I will post the files here for information purposes. Also, there may be more copyright violations by this particular editor who seems to have a propensity for downloading image files. Below are the files:
- File:AL-Cattlemen-2022-approved-passenger-768x376.jpg
- File:AL-Ducks-Unlimited-2022-768x370.jpg
- File:AmateurRadAZ.jpg
- File:AppalachianTN.jpg
- File:Acplate.jpg
Further comment: The above TN file - File:AppalachianTN.jpg - is covered by the TN.GOV "linking policy" and can be found here. So this Misplaced Pages image file is still not licensed appropriately, although I have no idea what the correct Misplaced Pages licensing would be.
I will notify the editor who downloaded these files that I have opened a discussion here. Well, now that I have taken it this far, the editor in question is: Brian.S.W (talk · contribs · deleted contribs · logs · filter log · block user · block log). However, the above image files might be too stale to be considered for any action. I leave that up to the Admins. If you look on their talk page, they have previously been blocked for copyright violations. ---Steve Quinn (talk) 20:59, 17 January 2025 (UTC)
- As you can see they've already been tagged for a deletion discussion yesterday, so there is no need to have a difference notice board also working on it. TiggerJay (talk) 21:21, 17 January 2025 (UTC)