Misplaced Pages

:Administrators' noticeboard: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 00:57, 17 March 2023 view sourceRosguill (talk | contribs)Autopatrolled, Administrators144,204 edits Block review: WikiWikiWayne: closingTag: 2017 wikitext editor← Previous edit Latest revision as of 20:08, 9 January 2025 view source Rsjaffe (talk | contribs)Administrators55,921 edits Permissions Removal: ReplyTag: Reply 
Line 1: Line 1:
{{pp-vandalism|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(3d) |algo = old(7d)
|counter = 350 |counter = 368
|archive = Misplaced Pages:Administrators' noticeboard/Archive%(counter)d |archive = Misplaced Pages:Administrators' noticeboard/Archive%(counter)d
|maxarchivesize = 700K |maxarchivesize = 700K
Line 7: Line 8:
|minthreadstoarchive = 1 |minthreadstoarchive = 1
|minthreadsleft = 0 |minthreadsleft = 0
}}{{User:HBC Archive Indexerbot/OptIn
|target=Misplaced Pages:Administrators' noticeboard/Archive index
|mask=Misplaced Pages:Administrators' noticeboard/Archive<#>
|leading_zeros=0
|indexhere=no
}}{{short description|Notices of interest to administrators}}{{Misplaced Pages:Administrators' noticeboard/Header}}</noinclude><!--S }}{{short description|Notices of interest to administrators}}{{Misplaced Pages:Administrators' noticeboard/Header}}</noinclude><!--S
{{User:ClueBot III/ArchiveThis {{User:ClueBot III/ArchiveThis
Line 34: Line 30:
<noinclude>{{Centralized discussion|float=left|compact=very}} <noinclude>{{Centralized discussion|float=left|compact=very}}
{{Administrators' noticeboard archives}} {{Administrators' noticeboard archives}}
{{Clear}}
<div style="clear:left"></div>
{{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 ==
== Pages recently put under ] ==
{{collapse top|bg=#F0F2F5|Report}}
{{User:MusikBot/ECPMonitor/Report}}
{{collapse bottom}}


The following is copied from ] on behalf of {{u|Sander.v.Ginkel}}:
== Moving forward: Deferring GENSEX cases to AE ==
{{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.
<!-- ] 20:01, 8 April 2023 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1680984070}}
{{RFC|policy|rfcid=EDA3AE2}}
Should the community encourage or require ] cases to be brought at ], or make no change? 18:26, 4 March 2023 (UTC)


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 ].
Potential encouragement ("soft") and requirement ("hard") wordings are given below; these are not the only wordings that could be used.
* '''Soft''': Something like {{xt|Reports primarily involving ] are '''usually best-suited to ]''' (AE), except when the matter is very straightforward or when AE is unavailable for procedural reasons (for instance, a requested sanction exceeds ], or a party against whom sanctions are sought is not ]). Beyond these two exceptions, any uninvolved administrator may, at their discretion and at any time, close an AN or AN/I discussion in this topic area in favor of review at AE; if the filer would not be able to start the thread, the admin should do so for them.}}
* '''Hard''': Something like {{xt|Reports primarily involving ], other than truly unambiguous disruption, '''should be filed at ]''' (AE) unless there is a procedural reason that AE would not be suitable (for instance, a requested sanction exceeds ], or a party against whom sanctions are sought is not ]). Any uninvolved editor may speedily close a thread brought in contravention of this rule, directing the filer to AE; if the filer would not be able to start the thread, the closer should do so for them}}
<span class="nowrap"> <span style="font-family:courier">-- ]</span><sup>]'']</sup> (she&#124;they&#124;xe)</span> 18:26, 4 March 2023 (UTC) <small>] as part of converting to RfC. RfC preface added 19:19, 4 March 2023 (UTC)]</small>


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 ].}}
* '''Nom statement''' <small></small>: So, whatever the outcome of the above, it's clear that the thread was a shitshow. And the Newimpartial thread was a shitshow. In fact every GENSEX thread I can recall at AN(I) since I resumed editing 2 years ago has been a shitshow, apart from slam-dunk "new user using slurs"–type reports.{{pb}}We have a venue for this. It is called ]. It avoids basically all of the BS we see in these kinds of contentious threads. The vast majority of AN(I) GENSEX discussions fall within concurrent AE jurisdiction, especially now that ] has loosened the definition of sanction awareness. There is no reason that we need to continue hearing these cases at AN(I) if we don't want to... and does anyone actually want to?{{pb}}I've had this idea bouncing around my head the past week and it's just seemed more and more reasonable as things have progressed, especially as we've seen difficulties in finding admins willing to close these threads. Thoughts? <span class="nowrap"> <span style="font-family:courier">-- ]</span><sup>]'']</sup> (she&#124;they&#124;xe)</span> 18:26, 4 March 2023 (UTC)
] (]) 18:12, 15 December 2024 (UTC)
* I would oppose, as I dislike the precedent this would set - AE and ArbCom are there to supplement, not replace, the self-management of the broader community. ] (]) 18:32, 4 March 2023 (UTC)
*: I would also suggest that you convert this to an ], as editors have begun to !vote on it. ] (]) 18:39, 4 March 2023 (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.&nbsp;... 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">&#91;]]</sup> <small>(])</small> 18:33, 15 December 2024 (UTC)
*::I mean this completely sincerely: if someone in the community thinks the community can self-manage a topic area that is under CT, I would encourage them to go to ] and to ask us to revoke the Contentious Topic designation for that topic area. We should not have the extraordinary grant of power, which is ArbCom delegating its broad authority directly to admins, is the community can handle it. I have repeatedly supported ways to eliminate areas from the CT/DS designation or to narrow their scope (see AP2) precisely because I think the community should handle what it can. So if something is a designated CT it means to me that the community isn't, at this time, able to self-manage that topic area and if the community actually is able to self-manage we need to restore the area to normal rules for admins and editors. ] (]) 18:49, 4 March 2023 (UTC) Edit: I should note I was making a general point here about any given CT. I think there are reasons to do and not to do this proposal of Tamzin's so am not expressing an opinion on that. Merely responding to Billed Mammal's thinking of how CT exists with-in dispute resolution. ] (]) 18:58, 4 March 2023 (UTC)
*'''Support''' per above.] (]) 18:37, 15 December 2024 (UTC)
*:::I might do that for some of the more obscure CT's, but to clarify my point here wasn't that I think that the community can fully self-manage this topic area, but that the community can partially self-manage every topic area that is under CT, and I don't want to set the precedent that they can't. ] (]) 19:08, 4 March 2023 (UTC)
*:Endorse one account proviso. ] (]) 20:28, 15 December 2024 (UTC)
*:::This goes back to . I appreciate your viewpoint that the community has failed to manage disputes in areas formally identified as contentious topics. Nonetheless, I think the arbitration enforcement system will be overloaded if every dispute is just passed up the chain automatically. I think editors need to exercise judgement and continue to try to handle issues at the lowest level possible. ] (]) 22:57, 5 March 2023 (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 ]. —&nbsp;]&nbsp;] 20:16, 15 December 2024 (UTC)
*'''Support hard''' - The Newimpartial and Tranarchist threads were among the worst things I've seen on this site when it comes to wiki drama. No need to have such a thing when AE can do it cleaner and more efficiently. I also believe this would lead to better results for everyone involved since we won't have involved users contributing, which undermines the integrity of consensus imo. ]<sup>]</sup> 18:35, 4 March 2023 (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. &spades;]&spades; ] 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;">—]&nbsp;<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)


== Spider-Man: Beyond the Spider-Verse - draft article about a future film seems to be a long-term draft ==
:My reservations that an admin panel at AE cannot handle certain types of disruption that require topic familiarity that skirts the edge of what we consider ] aside, I'm somewhat in favour of the hard proposal, but either could work for me.
:The biggest technical hurdle I see for making AE the primary/sole noticeboard for this would be the requirement that AE requires autoconfirmed before you can post a thread without it being removed. That obviously rules out editors with less than 10 edits over 4 days, but also rules out IP editors. If this does go ahead, a common sense exception for ] might need to be made so that any uninvolved editor/admin, at their discretion can move/re-post the thread at AE on behalf of the non-autoconfirmed editor, with the checks and balances that the editor moving the discussion takes some responsibility for the move. ] (]) 18:36, 4 March 2023 (UTC)
::{{re|Sideswipe9th}} In my mind, the AE autoconfirmed requirement would fall under "unavailable for procedural reasons". So would clear lack of awareness or requests for sanctions that exceed AE's powers (most notably sitebans). If that should be clearer in either proposed wording, I'm happy to clarify. <span class="nowrap"> <span style="font-family:courier">-- ]</span><sup>]'']</sup> (she&#124;they&#124;xe)</span> 18:39, 4 March 2023 (UTC)
:::Aah yeah. If you do follow through with BilledMammal's suggestion above of converting this to an RfC, I would suggest clarifying that in the wording before making it a RfC. Otherwise, unless this side discussion becomes a monster thread of its own, it's probably fine just being clarified in these replies for now. ] (]) 18:48, 4 March 2023 (UTC)
*'''<ins>Weak</ins> Oppose'''. <s>There are cases when reports can involve multiple issues. If only one of those issues is editing in GENSEX, it should not be the case that we are more or less requiring this sort of stuff to be sent to ]. {{tq|Reports involving ] are usually best-suited to Arbitration enforcement}} is overly broad, even in the soft version.</s>{{pb}}] can also be really difficult when trying to demonstrate issues that draw evidence from a large number of diffs (there's a hard cap on 20 diffs). I agree that ] has problems when it comes to these sorts of disputes inasmuch as it draws a lot of tangentially involved people to these discussions, but I do think that the filer should be able to elect to go to ] if they think that the open-ended format of the noticeboard will allow them to communicate their concerns more clearly to the community. — ]&nbsp;<sub>]</sub> 18:48, 4 March 2023 (UTC)
*:In light of Tamzin's amending of the RfC prompt above, I'm amending my !vote for relevance. I still don't like the phrasing {{tq|close an AN or AN/I discussion in this topic area}} (I'd prefer something like {{purple|close an AN or AN/I discussion about disputes <u>primarily</u> involving conduct in ]}} so as to be extremely explicit regarding when admins can and cannot close ANI discussions), so I remain weakly opposed at this time. — ]&nbsp;<sub>]</sub> 19:10, 4 March 2023 (UTC)
*For what its worth, as I read through the thread, I did think "much of this would have been avoided had this been transferred to, or originally filed at, AE." ] <sup>]</sup>] 18:49, 4 March 2023 (UTC)
*'''<del>Support</del><del>, undecided on variant</del>.''' It's a CT for a reason; using CT procedures for a CT is a nobrainer. ■&nbsp;∃&nbsp;]&nbsp;⇔&nbsp;∃&nbsp;]&nbsp;''';''' 18:54, 4 March 2023 (UTC)
*:'''Question:''' if this is becoming an RfC, where is the text actually proposed to be added? ■&nbsp;∃&nbsp;]&nbsp;⇔&nbsp;∃&nbsp;]&nbsp;''';''' 18:57, 4 March 2023 (UTC)
*::I imagine this could work as a standard community-authorized general sanction. It doesn't need to go into policy anywhere. — ]&nbsp;<sub>]</sub> 18:59, 4 March 2023 (UTC)
*:::Why would it be a general sanction? Why is it not just a noticeboard procedural rule along the liens of "you must notify someone you're reporting"? Best, ] (]) 19:34, 4 March 2023 (UTC)
*:Specifically, <del>support the '''soft''' variant</del>. "Truly unambiguous" bothers me on the harder variant, thinking of cases like the recent {{noping|Scapulus}}, who was handled swiftly at ANI, but where some editors did see it fit to show up later to complain about freeze peach. Clearly this was addressed well at ANI, but "truly unambiguous" is at least not unambiguous in this case. ■&nbsp;∃&nbsp;]&nbsp;⇔&nbsp;∃&nbsp;]&nbsp;''';''' 19:18, 4 March 2023 (UTC)
*::I wrestled a lot with that wording (and the closer can always take note of general support for one option or the other, but not for some specific wording, and implement accordingly). But to explain my reasoning, the core challenge is that there have been a lot of cases—both with editors seen as anti-trans and those seen as pro-trans—where someone has felt "Surely this is blatant disruption, easy indef", and it's turned into days or weeks of nonsense. So I acknowledge that "truly unambiguous" is really strong wording, but it's the best shorthand I could think of for "Disruption that you, ideally as an experienced user familiar with what is and isn't considered disruptive in GENSEX, know will lead to a summary indef." ] would, of course, continue to govern either of these options, and AE would always have its inherent authority to reject a case, thereby making itself procedurally unavailable and allowing AN(I) to proceed. <span class="nowrap"> <span style="font-family:courier">-- ]</span><sup>]'']</sup> (she&#124;they&#124;xe)</span> 19:42, 4 March 2023 (UTC)
*::SnowRise brings up another point I didn't notice, that according to the hard option, ''any'' uninvolved editor could close a thread they deem should be at AE. I think this is an exceptionally bad idea. This means that even in a case where admins are unanimous that some behaviour is unacceptable, any sufficiently out-of-touch editor could declare a case not unambiguous enough and complicate the process excessively. ■&nbsp;∃&nbsp;]&nbsp;⇔&nbsp;∃&nbsp;]&nbsp;''';''' 20:05, 4 March 2023 (UTC)
*:Update after further reflection: I think both variants risk curtailing the community's ability to self-govern and adapt by consensus in this area. I do think the idea has merit but allowing a move to be forced by either an individual admin or any editor is harmful, and I fear leaving everything up to AE admins could threaten our ability to respond flexibly to various kinds of disruption. I definitely agree that threads about more long-standing editors turn into huge messes on ANI and probably would do better at AE, but I don't think either of these proposals is the right way. ■&nbsp;∃&nbsp;]&nbsp;⇔&nbsp;∃&nbsp;]&nbsp;''';''' 21:29, 16 March 2023 (UTC)
*'''Support hard''' As I mentioned above, ({{tq|... it appears that is now simple for editors with a certain POV ... to remove other editors who oppose them from contentious areas without using the correct venue, which would be AE}}) when these discussions end up with the community they turn into the inevitable shitshows that this one and the NewImpartial one have been. We simply need to remove them from this arena, because otherwise the next one will be exactly the same. ] 18:56, 4 March 2023 (UTC)
* '''Converted to RfC''' per comments above, with '''some tweaks to wording''' per {{re|Sideswipe9th|Red-tailed hawk|p=.}} More generally, I stress that the wording above is just two ideas of how to do this. <span class="nowrap"> <span style="font-family:courier">-- ]</span><sup>]'']</sup> (she&#124;they&#124;xe)</span> 19:01, 4 March 2023 (UTC)
*'''Support''' with a preference for the '''hard''' variant, as I think the future will be like the past. I can appreciate the potential problem that a report can cross over multiple issues, but experience leads me to think that the most disaster-prone issue within such a report will dominate. A report that includes both a GENSEX issue and, say, edit-warring over ] will become a trainwreck over the former. ] (]) 19:10, 4 March 2023 (UTC)
*'''Comment''' I don't know what the solution is. This topic is one of several prime candidates for ], ], ], ], ], ], ] and ]. I don't like advocacy editing, but equally well we may need a balance of editors who have strong POVs to bring in-depth knowledge to controversial articles. It can't be allowed to be beneficial to ] and gang up on opponents or we will get more SPAs and non-autoconfirmed users pig piling on culture war enemies. From what I have seen the normal ANI process works pretty well, and the admins manage to separate behavioral issues from content. The whole !vote thing is problematic because as we see a big deal is made of distilling it down to numbers rather than the much-touted abstract "consensus". Whatever the solution, I think this topic and a few others like it stand to test Misplaced Pages's processes for dealing with problem editors. ] (]) 19:12, 4 March 2023 (UTC)
* '''Immensely strong oppose.''' First off, this is a procedurally invalid proposal, even with the addition of the RfC tag: enforceable rules regarding disruption (particularly those with such broad implications for arresting disruption across a vast swath of articles) cannot be made by the admin regulars of AN alone, supplemented merely by the editors already involved in this singular dispute and a handful of others brought in by a FRS notice. If you want create binding guidelines on this project, you need to use the ] process: identify the ] you want to alter (or suggest a new standalone policy namespace), and then host a discussion on that policy's talk page with a notice at VPP, or just host the discussion at the Village Pump to begin. AN is absolutely not the right (indeed, is arguably the worst) forum to be suggesting new policy. If this should go further rather than being swiftly shot down, the discussion needs to be moved.


I have not come across a situation like ] before. Maybe this is fairly common and I have just missed it.
:Second, putting aside the procedural considerations, I think the proposal (good faith though it obviously is) is a non-starter on its merits as well. Mind you, I think the present case giving rise to this proposal probably is an instance of a case that arguably should have gone to AE. But creating a mandate that all behavioural concerns arising out of GENSEX topics go to AE, aside from being inconsistent with how we handle every other ] (our new handle for discretionary sanctions for those unfamiliar) issue, is clearly an unworkable proposition under our current community schema for arresting disruptive behaviour--and the particular wording proposed here (in both variants) only further invites confusion and difficulty. Without meaning offense to Tamzin, it's the worst kind of rule cruft where the community clearly needs some degree of flexibility and redundancy. While I do believe that CTOP should be invoked more liberally in edge cases to bring matters to AE (as a more streamlined process less amenable to pile-on by biased/involved parties) ANI has an absolutely vital role in allowing the community to review and correct long-term behavioural concerns in a way that this overbroad proposal would clearly and significantly abrogate, for limited gain.


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.
:Under this suggestion, any behavioural issue imputing the GENSEX topic area would be effectively stripped out of the hands of the broader community to impose CBANs or otherwise address disruption, and those decisions held in reserve for editors with a high level of permissions at AE. While I reiterate that this would actually be a good thing in a non-trivial number of cases, as we should use AE more extensively than we do for CTOP issues, a firm requirement directing all disruption involving GENSEX to AE is clearly overkill that would significantly reduce the broader community's ability to adjudicate longterm issues and otherwise jam-up our ability to effectively arrest disruption. Further, encouraging rank and file editors to start closing down ANI discussions that touch upon certain topic areas (in a way that would currently be treated as clear disruption itself) would be ripe for abuse: anybody who's spent any degree of time at ANI can predict just how flexible a vast number of editors will be with judging themselves as "uninvolved" in the dispute: the technical excuse that they didn't participate in the immediate dispute would still permits editors who are heavily involved in the issues in general (or who have beef with the filer, or are regular defenders of someone who comes to ANI again and again) to thwart oversight by invoking this rule.


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.
:Honestly, I could go on for quite a while: there are so many potential knock-on effects to this proposal which would needlessly complicate addressing user conduct in this topic area, and so many ways that it's one-size-fits-all approach does not connect with our current otherwise context-sensitive (and somewhat overlapping, as a good thing) remit of different forums for addressing disruption. But the overarching concern is that it drastically reduces the community's options for little practical gain, pulls oversight for determinations that ultimately should fall into the broader community's hands on occasion, and would introduce all kinds of opportunities for gamesmanship (ostensibly the very thing it comes to address). I just think it's a very poorly considered proposal. But again, if nothing else, it needs to be considered by the community at large in an appropriate forum, which AN decidedly is not. '']]'' 19:55, 4 March 2023 (UTC)
::I don't really understand your procedural objection, Snow Rise. This proposes rules that would apply <em>only to WP:AN and WP:AN/I</em>. There's not even any change in how AE would operate, other than possibly getting more GENSEX cases than before. This is a vastly less impactful change than, say, placing ] under an extendedconfirmed restriction, which was handled by a simple thread at AN/I. I don't even think an RfC was strictly required here, but I'm following the path of least resistance.{{pb}}As to the various negative effects you're worried about, I guess I'll focus on one thing you've said: {{tqq|ANI has an absolutely vital role in allowing the community to review and correct long-term behavioural concerns}}. Can you point to evidence of this actually being the case in the GENSEX area? In GENSEX AN/I threads I've been involved in, even when there's been some ultimate consensus, I really can't think of any that I would say show healthy self-governance. This strongly negative view of AN/I's handling of GENSEX issues is shared by, as of this comment, every commenter in this thread who substantially edits in the topic area, including ones who often sharply differ on content matters. <span class="nowrap"> <span style="font-family:courier">-- ]</span><sup>]'']</sup> (she&#124;they&#124;xe)</span> 20:10, 4 March 2023 (UTC)
:::Hi Tamzin: I'm going to divide my responses between two posts, since these are semi-discrete issues, in order to faciliate any response and further discussion that may result:


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.
::*Regarding the procedural/placement issue, the mere fact that this change would pertain to how ANI operates hardly means that it will impact only the regular (mostly admin) editors at AN--let alone that it would only be of interest to this highly select segment of the community. This change would impact a vast number of editors working accross countless articles who may have recourse to bring behavioural concerns to the community at ANI. For that matter, considering almost every single hypothetical future thread that this proposal would seek to invalidate would typically have landed at ANI, rather than AN, placing it here rarifies the air even further, in terms of the regular editors who are likely to see it based on it's placement.


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?
:::This is clearly not an "AN/I only" issue: it very obviously touches upon fundamental authority, consensus process of, and decision making generally reserved to the community at large (as opposed to the administrative corps in particular) and the proposal would heavily impact the community's ability to address long-term disruption in a particular topic area, relative to how literally all others operate. Such a discussion should take place in a cnetralized and highly visible community space, not just within site of a handful of admins, those already connected to a singular dispute, and handful of others pulled in via a typical FRS. At an absolute '''''<u>minimum</u>''''' you should make a posting a notice about this discussion at the village Pump and making sure the discussion is on the ] ticker. And frankly, I just strongly recommend you move the entire discussion to VP itself. Otherwise, even if you get a consensus for the proposal here, you are just begging for an uproar afterwards, with accusations of an admin power grab, however good faith the intention here. I mean, if nothing else, what is the good-faith, community-respectful argument ''against'' moving this to a place where the community at large is more likely to be able to be aware of and weigh in on it? '']]'' 21:53, 4 March 2023 (UTC)
::::On the proposal impacting on the "community's ability to address long-term disruption in a particular topic area", how would you respond to the point raised above by {{noping|Barkeep49}} that I'd like to build upon in the next paragraph. Not sure if this should be a reply to your first or second point however, if you feel that it's better answered in response to the second, feel free to move this comment as a reply to your second point.
::::Because prior disruption in this content area has required significant ], and ] is to operate on {{tq|serious conduct disputes the community has been unable to resolve}}, has the community already not demonstrated a significant inability to address long-term disruption in this content area? ] (]) 22:06, 4 March 2023 (UTC)
:::::No, with all due respect to Barkeep, that is a conclusion I believe is unsupported by compelling evidence, and certainly not one I am aware of ever having been endorsed by the community or by ArbCom in particular. ] are not labelled as such because the community has a laisez-faire attitude towards them or has fundamentally failed to try to address them, or is per se incapable of doing so. Rather these are topics that are inherently divisive in the broader social systems of our societies at large, and thus such biases and conflicts are simply more easily imported into this project when topics are discussed/edit upon here, relative to some others, for completely obvious reasons. None of that militates for the conclusion that the broader community and our long-established rules and processes do not have a central role to play in addressing a heightened level of disruption in such areas--either as a general matter or, certainly, in terms of an express point of community consensus that has ever been adopted on this project. When we say "contentious topic" we mean "contentious topic", not "a topic the general community does not have a role in regulating". That's a massive non-sequitor and leap in logic, in my opinion.


<small>'''Edit:'''</small> Anyone got any thoughts on the concept of having a draft article for a film that doesn't meet ]?
:::::CTOP (and DS before it) exists merely to grant relaxed use of certain tools in areas where rapid response to disruption is more likely to be needed, not to declare the rest of the community as irrelevant to such a fundamental function: if anything, the existence of a CTOP determination for a particular topic increases the likelihood the broader community may have to occasionally intervene directly concerning disruption connected with that topic, not that it should be forbidden access to it's normal role in that process: that's an incredibly counter-intuitive read on the purpose of CTOP in my opinion, and certainly not captured anywhere in the policy pages that describe those processes.


] (]) 00:39, 29 December 2024 (UTC)
:::::And again, I say this while being broadly supportive of an hierarchy and an important division of labor running adjacent to the community->admin corps->ArbCom->WMF ladder. But this particular proposal would take a particular topic area and isolate it more or less entirely from established non-admin community tools and norms for expressing consensus on problematic behaviour, and taking consensus action accordingly. I just don't see how that can be justified on the mere basis that this is a highly divisive subject matter: so are countless other topics, including (by definition) every other ] subject. Are we going to follow suit for each of those topic areas and essentially hand the entirety of our decision-making apparatus on behavioural issues surrounding contentious topics to the administrative corps alone? I very much hope not: I think it would be an immensely detrimental development in the history of this project. Regardless, such a massive change to the status-quo with such significant impacts upon how we conduct this project and hold eachother accountable to community standards absolutely must be discussed with the fullest possible involvement of the community at large, not just here in the hallowed halls of AN. '']]'' 23:37, 4 March 2023 (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. ]]<sup>]</sup> 00:43, 29 December 2024 (UTC)
::::::On the conclusion from Barkeep I've built upon, the Arbitration policy that I linked to before, and was ratified by the community, does pretty clearly state that the Committee's remit is to handle content areas that {{tq|the community has been unable to resolve}}.
::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)
::::::{{tq|WP:Contentious topics are not labelled as such because the community has a laisez-faire attitude towards them or has fundamentally failed to try to address them,...Rather these are topics that are inherently divisive in the broader social systems of our societies at large, and thus such biases and conflicts are simply more easily imported into this project when topics are discussed/edit upon here}} Those two things aren't necessarily separate. Yes some of the CTOP topics are inherently divisive in broader social systems off-wiki, but because of that many of them are also topics that the community has historically had an inability to address. Some exceptions to this apply, for example while the ] is a CTOP area, outside of Shakespearean scholars and literary historians it's not really a topic that's divisive in a broader social context. As would the very Misplaced Pages specific ] and ] areas.
:::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)
::::::Let me put it to you another way. If was the community who had ], even if ultimately the end result of the AE and wider discretionary powers for admins is the same, that would have been a clear demonstration that the community was able to handle disruption. However because this required an ArbCom case to be put in place, that alone is a pretty strong indicator to me that this is a content area that the community, for whatever reason, is unable to handle. ] (]) 00:46, 5 March 2023 (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)
::::::I think I've left myself open to being misconstrued by not being as clear as I could and should have been and so that has happened in this discussion. What I have said is that the community cannot self-manage Contentious Topics. If the community were self-sufficient and able to self-manage it would be inappropriate for it to be an ArbCom designated Contentious Topic. On the whole I am of the firm belief that this community is incredibly capable of handling large and thorny problems of both content (which is obviously out of bounds for ArbCom) and conduct. Because of this I think some members of the community will sometimes think that Contentious Topic is just a shortcut to make life easier - in this case I saw it in Billed Mammal's stating that ArbCom is supplementing the community in Contentious Topics. It goes beyond that. In a designated Contentious Topic there are going to be significant shortcomings in the community's abilities to self-manage. But being unable to self-manage does not mean the community finds itself helpless in managing a Contentious Topic. Hence my edited comment that there are reasons to do and not to do this proposal, which I continue to have no real opinion on. ] (]) 00:52, 5 March 2023 (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)
:::::::Thank you for the clarification, Barkeep: your observations described in those terms, my own perspective substantially overlaps with yours. {{u|Sideswipe9th}} my response also touches upon your last post, but I'm doubling up here in responding to Barkeep to avoid redundancy. Let us assume for the moment that a CTOp being invoked in a topic area is a tacit statement that the community has been unable to handle issues in a topic area with the usual tools. I think the reality is quite a bit more complicated than that, but let's take that for granted in the present discussion so we can move on to more central points. Because the more critical/dispositive consideration here is that the increased tools that CTOP authorizes are meant to '''''<u>supplement</u>''''' existing administrative and community actions, not '''''<u>replace</u>''''' them. Even if we assume that any time ArbCom authorizes CTOP in a given area, it comes inherent with the message that the community is not getting the job done with typical methods, that is still a non-sequitor with the conclusion that ArbCom has declared that the rst of the community is not to take its own actions to arrest disruption in that area, where and when it can (be it at ANI or wherever). Not only does that conclusion not follow from the given premise, but we have a massive body of processes where the community clearly does regularly restrain problematic editors in CTOP/historical DS through processes taking place outside of AE. And this parallel activity has been undertaken as long as DS/CTOP have existed.
::::::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. ] (] &#124; ]) 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&apos;_noticeboard" class="FTTCmt"> —&nbsp;] (]) 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)
:::::::So the end result remains the same: a finding of CTOP in no way forestalls the broader community from exercising it's own prerogative to implement TBANs or other CBANs (to take just one example of what the community is permitted to do in CTOP areas). Surely if the contrary was the case, we would have adjusted the relevant policies on CBANs to reflect this fact years ago. CTOP merely authorizes the use of advanced tools to block or otherwise restrain problematic actors a little faster, and makes ] an option for reporting and getting a faster administrative response. What CTOP clearly does ''not'' do is forbid the community at large from also using its own discretion <u>in conjunction with</u> these liberalized tools, as it can (and does) use such community decisions/CBANs parallel to regular administrative blocks, in any other topic area where disruption arises. Again, that would be an absurd conclusion: why would we want the community to be ''less'' proactive in responding to areas of heightened disruption? Clearly we want (or at least entertain the occasional need for) increased use of CBANs ''alongside'' the use of CTOP/1RR blocks and AE filings. Insofar as CTOP/DS language has ever said "DS/CTOP is meant for areas where the community is having trouble keeping the disruption in check", it is for the purpose of explaining the need for looser standards for when warnings, blocks, and other preventative administrative actions can take place--not for the purposes of saying "these issues can now only be addressed at AE". If it were the latter, then countless of our policies and much of the history community bans would read completely differently. '']]'' 01:59, 5 March 2023 (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)
::::::::What I think this very fair analysis of Contentious Topics misses out on is that certain editors/discussions are, themselves, signals that the community is unable to handle something. This is why not only can admin act sooner and sanction with more severity than they can outside a CT topic area (what SR focuses on) but also can act with first mover advantage and knowing that their actions are less likely to be overturned on formal appeal because of the higher than normal requirements. ] (]) 03:09, 5 March 2023 (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)
* {{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 ]. &ndash;&#8239;]&nbsp;<small>(])</small> 12:04, 1 January 2025 (UTC)
**Thank you. ] (]) 15:01, 1 January 2025 (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)
::*As to the substantive arguments, you may very well be correct that regulars in the GENSEX space consider ANI an intractable travesty: while my background and editorial interests in both biopsychology and human rights semi-frequently bring me into contact with existing disputes in this topic area, I don't engage with the area with the regularity of such editors. However, a few thoughts as to that: first off, that is not exactly a rare perspective about ANI's complications, issues, and the general caliber of discussion there from editors in...oh, I don't know, let's say every single topic area under the sun. That low opinion of what can happen at ANI (unavodiable to a certain extent by virtue of the fact that it specializes in intractable disputes) does not automatically invalidate the role that space serves or the necessity for preserving the ability for concerned community members to bring issues there for the community's consideration.
: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)


== 43.249.196.179 (again) ==
:::So I would say the onus is upon you as the party proposing such a massive carve-out to explain why this one topic area should deviate so drastically from how our policies and procedures operate for every other topic. I mean, have you even considered the fact that your proposal would essentially make it impossible for any disruptive party in the GENSEX area to hereafter ever receive a CBAN from that area (or the project in general) as a result of their conduct? That's a pretty humongous abrogation of the community's inherent purview as it has historically existed on this project--and yet also just one of several such outsized implications of the proposal. Is GENSEX so much more inherently disruptive an area so as to seize the entirety of all such determinations from the community at large, even when compared against other DS/CTOP topics? I just don't think so. The community needs to be able to weight in on longterm abuse regardless of the topic area, and your proposal would instead shift that role entirely to just those admins participating at AE. That's incredibly problematic to me, for more reasons than I can begin to list here.


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)
:::For that matter, putting aside for the moment how extensively this proposal would usurp the broader community's role in preventing disruption in this area, and hamstring our ability to respond to longterm abuse, I am equally, if not more, concerned about the impacts upon the interests of the reported parties. For all the issues inherent to ANI, it does permit for more shades of grey to enter the discourse than does AE. Taking TT's case as an example, some of us were compelled to modulate our recommendations based on the nitty-gritty details and context of the dispute. Let's remember that the responding admin at AE has a fundamentally different role from the closer of an ANI thread. At ANI the closer must, to some degree, take stock of any ameliorating factors which gained significant support among respondents, because they are finding a community consensus in the discussion. At AE, the admin's role is much more that of the party actually ''making'' the determination in the first instance, based on the information provided by involved parties. That's a fundamental difference that effectively narrows the decision making from a group (which can, in the aggregate, often reach a more nuanced and reasonable conclusion that balances competing interests) to a single person, who is more likely to act in a very black and white (or at least far more idiosyncratic) fashion.
:] 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)
:::Again, sometimes that is precisely what we want, for the sake of efficiency and fairness. But often we want the broader community weighing in, in complicated or nuanced cases with competing community interests, and creating a blanket rule that would just completely pull that decision making into the authority of a increasingly smaller subset of the community is a bad direction to take, and even more questionable when you consider that the proposal is that we do it for a given topic area on the justification that "it gets ugly at ANI sometimes when we discuss this subject matter", because 1) what topic would that not apply to? and 2) sometimes the areas with the most contention behind them are the ones we want the community at large to be able to dig into, to avoid oversimplifcation in the handling of those disputes. '']]'' 21:53, 4 March 2023 (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 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)
::You are looking at two different IP addresses. Getting things right is important. ] (]) 07:53, 1 January 2025 (UTC)


== Incivility at ] ==
*'''Moral support''' - I'm generally in favor of making ANI operate more like AE (read: get rid of threaded discussions between the OP and accused party), and thus for as long as AN/I continues to not look like that, I'd generally support delegating more to AE over ANI. But, I do agree with Snow that there's procedural issues with raising this proposal here (at least as anything other than testing the waters), and beyond that would be more in favor of a proposal that cuts down on threaded discussion at ANI rather than just delegating work away from there in a piecemeal fashion. <sub>signed, </sub>] <sup>]</sup> 20:11, 4 March 2023 (UTC)
*:Reading through the proposal again, I guess my above reasoning puts me in the '''soft''' camp? But I don't think we need more guidance for this topic area so much as modest changes to how ANI operates, and for as long as ANI continues to be a free-for-all, AE will be a preferable forum for addressing pretty much any conduct dispute that it has authority to address. <sub>signed, </sub>] <sup>]</sup> 20:22, 4 March 2023 (UTC)
*:There's a fine line between accused having an opportunity/obligation to respond to their accusers and the potential for accusations of ]ing and the current format makes it hard to tell which is happening. Very much agreed with you @]. ] (]) 22:13, 4 March 2023 (UTC)
*'''Oppose''' I don't believe this is something we need to formalize. However, a few times in this saga I've said that it would be a good idea for the closing admins to ''suggest'' that future incidents of this type might be better suited for AE. I still stand by that. I suppose this is similar to the Soft version above, but less formal. We can make a recommendation, but we don't need to make the process so rigid by reducing out flexibility to handle new situations at the most appropriate place. <span style="font-family:Courier New;font-size:3">]</span><sup>]</sup> 22:21, 4 March 2023 (UTC)
*'''Support, preferring hard''' This case has pretty conclusively proven that in a controversial topic area it's possible to remove an opponent who has not actually done anything wrong just by showing up to ANI. Needless to say, this is bad. So I support any reform that would fix this situation, including this one. ] (]) 01:27, 5 March 2023 (UTC)
::{{tq|who has not actually done anything wrong}} - hmm, seems like a questionable summary to say the least. <span style="font-family:Palatino">]</span> <sup>]</sup> 01:47, 5 March 2023 (UTC)
*'''Strong oppose''', this is a completely inappropriate carveout of one topic area, basically making ]s impossible for that topic. That is unprecedented and disempowers the community. It is not the place of a few people on AN and a few people unhappy with the recent closes to give/take that away. And the idea that AE is inherently superior to ANI is questionable. The limits there make it hard to document a ''pattern'' of misconduct; and without a pattern, it's easy and common for bad behavior to be handwaved away as though it is an isolated incident, or just sour grapes from transphobes or whatever. <span style="font-family:Palatino">]</span> <sup>]</sup> 01:36, 5 March 2023 (UTC)
*:{{re|Crossroads}} CBANs are beyond AE's authority and would thus obviously not be covered by this. <span class="nowrap"> <span style="font-family:courier">-- ]</span><sup>]'']</sup> (she&#124;they&#124;xe)</span> 02:08, 5 March 2023 (UTC)
*::That is not at all obvious, and besides, then why propose this? It was two CBAN discussions that sparked this idea in the first place, and is motivating some of the votes. A technicality of "the discussion has to be explicitly for a CBAN from the get-go" would make it much harder for problems to be addressed because it's not common for one editor to have all that evidence personally and know that it is that severe. <span style="font-family:Palatino">]</span> <sup>]</sup> 02:14, 5 March 2023 (UTC)
*::CBANS are pretty much exclusively a product of ANI discussions, so if you create a rule which prevents the community from bringing disruption attached to a given topic area to ANI, you effectively are creating a situation where a CBAN can never be applied to a user who has proven disruptive in that area. So, yes, your proposal very much removes CBANS (or similar actions taken as an expression of community will) as an option in ''any'' case of disruption that took place in the GENSEX topic area. Indeed, under your proposal, even an LTA or a suspected sock of a previously CBANned editor couldn't be brought to ANI to be dealt with if the disruption touched upon GENSEX editing. I honestly don't wish to be rude, Tamzin, so I hope you will forgive how stridently I am about to word this, but the fact that you didn't recognize this extremely obvious result of the proposal suggests you made it without due consideration for its very broad and numerous impacts. '']]'' 02:19, 5 March 2023 (UTC)
*:::Well, there are two possibilities here. One is that I didn't consider the possible negative outcomes. The other is that you're wrong about those negative outcomes being remotely likely. Unsurprisingly, just as you tend to think your analysis is correct, I tend to think mine is. Perhaps after ~15kB of reiterating your parade of horribles that will come to pass if we so much as discourage these discussions, now would be a good time to step back and let others decide how valid your concerns are. <span class="nowrap"> <span style="font-family:courier">-- ]</span><sup>]'']</sup> (she&#124;they&#124;xe)</span> 02:37, 5 March 2023 (UTC)
*::::Tamzin I'm fairly sure I've seen you a lot around AN/ANI so I'm fairly surprised that you're so unfamiliar with how CBANS work. While some CBANs start from the get go as someone reporting some behaviour problem an proposing a CBAN, I'd say most CBANs do not work like that. Instead they start of with someone reporting some misbehaviour. Others than may report more misbehaviour. Sometimes the OP responds extremely poorly as well. Eventually someone decides their behaviour is bad enough and proposes a CBAN. The community discussions/!vote this and we hopefully come to a consensus. Even better if it is an uncontentious consensus although sadly that isn't always the case. The organic nature of CBAN discussions means that saying this proposal excludes CBANs simply makes no sense. How can a proposal exclude CBANs when we have no idea if a CBAN may result until we've discussed? ] (]) 02:49, 5 March 2023 (UTC)
*:::::{{re|Nil Einne}} I'm well aware of how CBANs work. I'm also well aware that there has not been consensus to CBAN someone for edits primarily relating to GENSEX since... Since when? I can't think of a time in recent memory, and I can think of one particular case where a CBAN proposal failed despite strong evidence of systemic discrimination against trans editors. If someone gets TBANned at AE from GENSEX, and continues to disrupt in other realms, then AN/I can still handle it, probably much less dramatically. "User:Example was indef TBANned from GENSEX last month at AE. They have since made comments X, Y, and Z regarding abortion. This user is clearly NOTHERE and further sanctions re in order" has a much better chance at AN/I than "User:Example has been saying A, B, C in this dispute about trans pronouns and D, E, F in this thread on gender dysphoria and also unrelatedly X, Y, Z about abortion". <!-- Template:Unsigned --><small class="autosigned">—&nbsp;Preceding ] comment added by ] (] • ]) </small> 03:10, 5 March 2023 (UTC)
*::::Look, I don't want to get in a cycle of counter-criticisms with you, especially because I can recognize that your proposal is a goodfaith response to seeing one too many trainwrecks in this area that could have driven away a valuable contributor (thankfully, from the above, it seems we have avoided that outcome with TheTranarchist). However, I will say that the vast majority of the "15kb" you reference is a necessary response to your hand-waving away observations about some pretty major consequences of your proposed course of action--which I would not describe as a "parade of horribles" but rather a series of results that would be direct consequences of that policy were it implemented, and which (far from being hypothetical or hyperbole), would be automatic and inevitable outcomes.


@] 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)
:::::As Nil Einne, Crossroads and myself have already explained, almost all CBANs result from discussions where they were not suggested at the outset, and your personal recollections and feelings about their necessity not withstanding, there's no good reason to believe the community might not need to CBAN someone in this area from time to time, and no argument for stripping that option from the community's potential responses to disruption. Considering we just had two such CBANS of the sort that you describe as uncommon in one day, and considering there have been numerous other GENSEX TBANS implemented at ANI over the years, clearly the need for such tools is not as super rare as you suggest. And frankly, anti-trans sentiment is a reason why we should be concerned to preserve this option, not toss it away, because it's equally (if not more) likely that the next person we need to indefinitely remove from GENSEX editing will be a problem user aligned ''against'' trans rights.


:This looks to me like it's covered by ]. ] ] 02:18, 2 January 2025 (UTC)
:::::And even as regards that rare exception where a CBAN proposal is a part of the initial complaint, that actually highlights another can-of-worms knock-on effect that would result from the framework you are advancing here. Because as soon as people adjust to this new dynamic, here's exactly what is going to happen: every single time that an editor with an ounce of ] in them at the moment wants to bring what they perceive to be disruption in the GENSEX area to ANI, they are simply going to include a request for a CBAN in their filing, because that will become the most obvious way for them to get past the arbitrary "must be an issue that AE cannot address" threshold that is a part of your model. And I fail to see how forcing every complaint filed at ANI over GENSEX disruption to start out with the posture of a proposed CBAN is going to make the resulting discussions ''less'' inflamed. '']]'' 07:52, 5 March 2023 (UTC)
*'''Comment''': Just spitballing. What about a system in which CT issues are still reported at ANI, but they can be forwarded to AE if it's determined that there was disruptive behavior? This would theoretically retain the benefits of the discussion format, but it would end the discussion before the thousands of words dedicated to arguing about whether sanctions are warranted and what sanctions are applicable. Of course, this system would not address the legitimate concerns raised by Crossroads above. I also think that any solution should involve reform that allows for topics to be delisted from CT more easily per Barkeep49. ] <small>(])</small> 01:59, 5 March 2023 (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 {{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. ]&thinsp;] 02:47, 2 January 2025 (UTC)
::{{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)
*:Puts the cart before the horse. If "it's determined that there was disruptive behavior" then a conclusion has already been reached and an appropriate sanction or warning can issue. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 05:48, 5 March 2023 (UTC)
:This seems entirely unnecessary. ] (]) 03:13, 2 January 2025 (UTC)
*'''Oppose''' Having watched AE proceedings over the years, I am quite confused on why anyone would see that as an improvement in venue. In fact the ability for a single admin to supervote by design, has been a detriment to the encyclopedia in my opinion. ] (]) 02:02, 5 March 2023 (UTC)
::Can you elaborate on which aspect of {{tq|this}} you are referring to that you believe is unnecessary? ]&thinsp;] 03:55, 2 January 2025 (UTC)
*'''oppose'''. this is ]. ]] 03:02, 5 March 2023 (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)
*<p>'''Oppose''' in a number of ANI cases involving an DS area, I have suggested that it might be simpler to take things to ARE. Indeed in a number of cases where someone was not formally aware, I've given alerts as a result of an ANI cases and if the problems were minor enough I've suggested perhaps it would be easier to just leave things be for now and take it to ARE if it repeats. I haven't done so since it changed to CT mostly because it's just something I do where I happen to see a case where this might help. In other words, I fully support the idea that often it is better for areas well covered by CT to be simply handled by CT rather than going through normal community discussion. </p><p>However I'd oppose trying to force cases must be treated as CT without very strong evidence that this is the best for the community. And to be clear this includes the soft variant as it also include a degree of force. </p><p>As noted above, there are numerous possible consequences for this e.g. how we handle cban or other sanctions that aren't something CT can impose. Note also that CBANs technically include topic bans even from CT areas. While I am personally not fussed whether an editor is subject to a community topic ban or a CT one, there is always going to be editors who feel a community ones is better since it will require a community consensus to remove. (After all, we even had community site ban of an editor because the community was concerned about an earlier arbcom decision to unban the editor.) There's also how this affect cases that might be better for the community to handle since they are more complicated than the simpler disruption in a certain topic area CT handles best. </p><p>I'd even more oppose it for any specific CT area (instead of all CT areas) without strong evidence there's a reason to treat these as special areas. I'm far from convinced that the two reason cases resulted in this are the worst we've seen at ANI. And concerns over people trying to get rid of opponents covers pretty much all CT areas and frankly anything contentious which isn't CT. E.g. the notability/ARS wars. </p><p>Most importantly though, IMO this is simply a bad idea at this time. To some extent there is an aspect of hard cases make bad law here. But more importantly, emotions are clearly still running high over those two recent cases. I don't think it likely holding this discussion at this time is going to improve that or ensure we make a good decision. Instead we get comments like "{{tqi|who has not actually done anything wrong}}". Clearly quite a few members of the community do not agree with that for one or both of those editors. This includes many who are not opponents. While a discussion like this is always likely to be contentious and may get controversial comments, the best outcome and least disruption and harm to the community will come if we hold it when editors aren't already affected by two recent controversial cases, cases which resulted in this proposal. Fanning the flames when emotions are still so high is not going to benefit the community. </p><p>To be clear, I'm not suggesting any editor involved in this proposal ill motivations, I have no doubt they're genuinely trying to improve Misplaced Pages and fix a problem that they feel was highlighted by recent cases. However having good motivations doesn't stop an editor making bad decisions and I feel that's clearly the case here. (Actually part of the reason why they have made such a bad decision is precisely why we should not be doing this. Perhaps they weren't able to see what they may have seen when if it wasn't so soon after those two cases namely that it was a terrible idea to discuss this right at this moment.) </p><p>] (]) 03:28, 5 March 2023 (UTC)</p>
::::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)
*'''Oppose''' per most of the above, especially SnowRise. Not going to repeat it all. I do think that an "ARBGENSEX2" case is ultimately inevitable, but it will be after the community has failed to be able to resolve the problem without having to defer to ArbCom. And that time is not upon us yet. I agree also especially with Crossroads in observing that AE is not a good venue for establishing long-term patterns of disruption, only short-term "outbursts", because of its strict limits. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 05:46, 5 March 2023 (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. ]&thinsp;] 06:18, 2 January 2025 (UTC)
*'''Oppose''' - While I recognize that Tamzin's suggestion is entirely a good faith effort to deal with a pressing problem, I believe that SnowRise's analysis of the results that would occur if this were put into effect to be more accurate and representative of the general history of AN and AN/I. Community discussion can result in a CBAN, which requires that the community overturn it. It is therefore a more powerful sanction then an admin-imposed AE indef, which -- like every other admn-imposed sanction -- can be overturned at any time by any individual admin (for whatever reason). We should not lose the potential use of CBANS as an option. ] (]) 08:32, 5 March 2023 (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)
*:{{replyto|Beyond My Ken}} I'm fairly sure you're wrong about CT sanctions as alluded to by ] and maybe others above. As documented at ], these can't simply be overturned at any time by an individual admin for any reason. That can only happen when it's an indef and was imposed by a single admin and it's been more than a year or the imposing admin is no longer an admin. Otherwise if the imposing admin agrees (including when imposing the sanction) but note this sort of means it's not overturned solely by any admin. Oh and if it's imposed by a single admin, they (but only they) can change or remove it themselves without needing to ask anyone. Maybe more importantly a case which makes it to AE will often result in discussion before sanction is imposed by rough consensus of admins in which case none of this applies and it needs to be appealed either at AE or AN or by arbcom. To be clear, this is only for sanctions imposed under CT. I believe in some cases an admin will just quickly impose a sanction as an ordinary admin action rather than under CT and AE will decide to just leave it at that. (And as noted to some extent even if it is imposed under CT, if by a single admin which I think is another possible outcome of an AE report, this admin could allow it to be treated like a regular sanction and overturned by any admin by saying so when imposing it.) ] (]) 09:03, 5 March 2023 (UTC)
::::Also, as a note, this isn't ANI... - ] <sub>]</sub> 07:09, 2 January 2025 (UTC)
*::I may be confused about that, I'm not certain, but it *is* certain that if all GENSEX issues are required to be settled at AE, then a CBAN is out of the question, and I still consider a CBAN to be a more powerful sanction, because it comes from the community at large. It may be more cumbersome to *reach* a consensus to CBAN, but the direct consensus of the community is, to my mind, a stronger action. ] (]) 11:31, 5 March 2023 (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.
*'''Oppose'''As a general principle leave it to us on the ground to thrash things out. The existing structure can take care of those fairly rare times we can't.] (]) 10:08, 5 March 2023 (UTC)
: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)
*'''Oppose''' - I appreciate Tamzin making an effort to find a way to improve our resolution of disputes and to avoid having difficult mega-threads like these two ANIs we just had. However, I am among those who does ''not'' believe that AE is better at resolving disputes than ANI (although I do believe in some cases we should make some ANI threads more formal, like AE, to e.g. reduce bludgeoning). I also don't think AN is the right place to decide structural changes to ANI; that should be at the pump; the Administrator's Noticeboard is not an appropriate place for any RFC in my view. Discussions here will attract attention from administrators, and RFCs might bring in FRS, but that's still not a pool representative of the overall community. Ironically, my procedural objection is rooted in the same principle as my substantive objection: fundamentally, if you reduce the pool of decision-makers from "everyone" to "administrators", you don't end up with a better decision. ] (]) 15:34, 5 March 2023 (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)
*:Apparently we're ]. ] (]) 21:45, 5 March 2023 (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)
*::So much for that. Closed promptly with "It is debatable whether ... that would be a matter for AE". <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 23:32, 5 March 2023 (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)
* '''Neutral''' on the soft proposal, though I think it should be worded to encompass all CT areas, '''oppose''' the hard version. I do think AE is a better venue for most CT-related conduct disputes, and I hope our admins feel empowered to strongly suggest that newly filed ANI reports be moved to AE when possible. I would be fine with admins closing such discussions and directing the OPs to AE, though I think all it should take to reopen them is the OP saying "no, I definitely want this to stay at ANI". I oppose the hard proposal as GENSEX doesn't need this treatment over other CT areas, and because I agree with those that are concerned about missing out on some ANI-specific potential remedies. ] (] / ]) 19:27, 5 March 2023 (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)
* '''Note:''' I've placed a notice of this discussion at ] and listed it on the ] ticker: these issues and the proposed solution have implications far too broad to be considered by just those of us here. '']]'' 22:27, 5 March 2023 (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)
*'''Oppose''' - My lead reasoning will remain that our community members are intended to be able to pick their forum, depending on what they think can work best (I suspect GENSEX regulars are likely aware of the options). I oppose revoking that choice. There are more personal reasons someone might have this reason (e.g. So long as I continue to find complex discussions harder to understand in separated discussion than ANI rambling but more continuous format (while many are fiercely the opposite); or someone preferring to have an area settled by the general editing base than a small subset of admins), that encourage them to prefer one format over another. In terms of proposer's request to find alternate solutions, then I believe they may be best off indicating what the most problematic factors are, then mitigations to those can be advised, which may well more be in execution than mechanics. Time? Length of reading? Both no doubt come with negatives, but the flipside is both indicate significant numbers of editors trying to find a solution and struggling. A shift to AE may well resolve on those two aspects, but at the issue of cutting the people participating, or the views & evidence given. In which case, it's not a solution, but a tradeoff. We deal with tradeoffs all the time, but for any tradeoff, the proposal should be noting the negatives that arise and why we should accept their cost. I do not believe those costs are sufficiently covered here, with either option. ] (]) 00:09, 6 March 2023 (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)
*I've been a bit conflicted on this but I think I'm coming down on the side of weakly supporting the soft version of this proposal.—]&nbsp;<small>]/]</small> 08:33, 6 March 2023 (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)
* '''Oppose'''. It is my firm belief that this proposal would not have been made if it had been any other topic area. Gensex editors should not be treated any differently from other editors that wind up at ANI. Gensex editors are not special and exceptional. Misplaced Pages is not here to coddle any editors, regardless of their editing experience and editor level. Gensex editors must follow the same Misplaced Pages community policies that affect non-gensex editors, and if one of them pushes an envelope too far, he/she/they must face the same action and consequences faced by editors who have engaged in similar behavior in non-gensex articles. ANI is where issues regarding a user's conduct need to be discussed and determined. ] ]. <span style="font-family:Papyrus; color:black">Ol' homo.</span> 12:02, 6 March 2023 (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)
* '''Oppose'''. For the same reason I opposed making ANI more like AE, there is a need for a place to report issue that has no bar of entry. No matter how low that bar can be made. Maybe taking discussions to AE is a good idea, and could be suggested once a report has been made, but there shouldn't be any formal direction on the matter. -- LCU ''']''' <small>''∆]∆'' °]°</small> 15:31, 6 March 2023 (UTC)
:::::::WP:MOS says: {{tq|If any contradiction arises, this page has precedence.}}
* '''Strong oppose hard, neutral on soft''' - AE is too bureaucratic. Allowing an admin to move a discussion to AE puts the bureaucratic responsibility to the admin, not the (possibly new) user who wants to file a complaint. ] ] 16:56, 6 March 2023 (UTC)
:::::::WP:AT, which follows MOS says: {{tq|Generally, article titles are based on what the subject is called in reliable sources.}}
* '''Neutral to support on hard, support on soft''' - I know this sounds vague, but in this case, any solution is better than no solution. The way I see it, most GENSEX editors have it ''significantly '' harder on virtually every level and WP might not be well equipped to handle all of it with its existing administrative structures. @] I hope this will not come off as if I am rushing through the nuances of this proposal; rather, I am trying to say that this is one of those cases where, in principle, I'll support attempts to lessen the burden on GENSEX editors, even if those are not "perfect" by WP standards. I'll add that to VP discussion. And I really think some editors in ANI should take ] to heart. ]] 19:10, 6 March 2023 (UTC)
:::::::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)
* '''Oppose'''. Cases from all other topic areas can be brought here (can't they?). I don't see how it is helpful to make an exception for GENSEX. Editors should not be curtailed from raising important issues so that the most people can see them. ] (]) 02:27, 7 March 2023 (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)
*'''Oppose'''. Does not seem appropriate; cases should be filed where appropriate as appropriate. ] (]) 14:59, 10 March 2023 (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)
*'''Oppose''' I don't see even from the previous ANI threads that GENSEX topics are unique in a manner that would make AE the only appropriate venue, especially since AE tends to languish in my experience from lack of input. If there's thoughts that ANI itself could be restructured to address issues, that's worth talking about (BilledMammal's suggestions etc.) But I don't actually see how this solves any problem. ] <sup><small>]</small></sup> 15:21, 10 March 2023 (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)
*'''Oppose''' Actively trying to reduce community involvement in banning people for their problematic behaviour is counter to the core consensus-based approach to community management. ] (]) 12:09, 15 March 2023 (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)
:::::::::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)
=== A plea: Propose a better solution ===
I don't think I have ever felt truly desperate on Misplaced Pages before. I have not come here trying to offer a magic bullet to this problem. I have presented two drafts of solutions to a problem that is '''making a highly sensitive topic area unsafe to edit in'''. Most people who edit GENSEX have been neutral to supportive of this proposal. It has largely been the "AN(I) regulars" here saying no, we have to continue to stew in this mess—a kind of mess that, no doubt, AN(I) regulars are used to, else they wouldn't be AN(I) regulars. The people in this topic area do not edit so they can have <em>month-long dramaboard threads</em>. We edit because we see issues in Misplaced Pages's <em>woefully inadequate</em> coverage of gender issues. Inhumane treatment of BLP subjects. Coverage of sociological subjects that is sourced to Tumblr blogs rather than academic papers. <em></em> All to push both pro- and anti-trans narratives, sometimes in the same sentence.


:Agreed. An admin got involved and simply continued off-topic discussion. ] (]) 21:33, 4 January 2025 (UTC)
So I'm begging y'all, please. As a fellow editor. As someone who has poured her heart into writing two GAs in this topic area. This is a request for comment. I am requesting y'all's comments: Propose a better solution. Propose something that does not drive away editors from a topic area desperately in need of them. I still think my ideas work fine or would only nned slight tweaks—in particular "soft", which may oppose !votes haven't really addressed—but if you disagree, I get it. That's how consensus works. But there is a massive problem here. I don't think anyone familiar with the facts disputes that. If you won't support either these solutions, then something else. Please. <span class="nowrap"> <span style="font-family:courier">-- ]</span><sup>]'']</sup> (she&#124;they&#124;xe)</span> 23:18, 5 March 2023 (UTC)
*'''Warn both to drop the stick''', otherwise, no action at this point. ] (]) 15:57, 8 January 2025 (UTC)
:The same sort of plea could be made about every ] subject area. There's nothing magically special about this one. What you have boils down to a complaint about how ] operates, and we all have complaints about how ANI operates, but there isn't a clear consensus on how to improve it. "Carve my preferred topic out of ANI" isn't a solution, and an RfC predicated on that idea isn't going to be the vehicle by which we arrive at ANI reform. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 23:44, 5 March 2023 (UTC)
*:'''''Hands ] two ]''''' You want to hand them out, or me? ] (]) 16:32, 9 January 2025 (UTC)
::I edit in quite a few CTOP areas. I am not aware of another one that routinely triggers weekslong battles of this sort at AN/I. But if your response to a request for a better proposal is "I acknowledge a systemic problem, oppose a solution, and have no better solution to offer," all right, noted. <span class="nowrap"> <span style="font-family:courier">-- ]</span><sup>]'']</sup> (she&#124;they&#124;xe)</span> 00:30, 6 March 2023 (UTC)
:::Instead of engaging in a petty straw-man argument, try reading what I wrote more carefully. To spell it out: This proposal is basically a poisoned well. If you want to propose ANI reform, do it in a clean proposal in an appropriate venue and there may be enough other editors fed up with ANI for the same reasons to support some changes. (Comment length/frequency limitations are a pretty commonly suggested idea, so that's a likely starting point.) <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 00:57, 6 March 2023 (UTC)
:{{peanut}} <small>I may be overusing this template, but I really want to make clear that I'm a newbie here. I don't mean to be a bother.</small> In my lowly opinion, the first substantive community response to a new editor's behavioral issue should ''not'' be a vicious, humiliating, overlong, utterly unsympathetic ANI case. And if you're just going to hand out a TBAN anyway, you might as well make it policy to slap an editing restriction on anyone with more than one warning in the GENSEX topic area. It would eliminate a lot of the pointless bureaucracy.{{pb}}In my lowly opinion, an ounce of prevention is worth a pound of cure. (Metric friends may substitute '28 grams' and '0.45 kilogram'. {{tind|j}}) If the ] program were reasonably effective I wager you wouldn't find even half as many {{tq|chronic, intractable}} behavioral problems in this area. You can try to whip GENSEX into shape all you like, but do you really think that increasing sanctions will entice new users to come edit the area? (''I'' certainly am not enticed. Thank god I stay on the refdesks.) If the broader community were more ''proactive'' and less ''reactive'' in responding to flawed editing, things would surely not escalate so rapidly.{{pb}}In any case I don't really have a concrete suggestion. I would greatly like to see increased collegiality between old and new editors with a more developed mentorship program. But anything that gets the community to act ''before'' things have escalated to a TBAN is a better solution than what exists presently. Stop ''punishing'' people when you veterans haven't even figured out how to solve the underlying problem. In the meantime (I know my comment is unrealistic), I think AE is probably a better place than ANI for things like this. But maybe it would be best to introduce an "AE mode" for use at ANI, so discussions could be more structured yet not as limited in scope and jurisdiction. Just a thought.{{pb}}I don't mean to be impolite with this comment, just impassioned. If I've been incivil, let me know and I'll strike it. ] (]) 00:14, 6 March 2023 (UTC)
::I'd be all for a radical restructuring of AN/I—perhaps limiting it into actual <em>incidents</em> and creating a separate ] without threaded discussion—but that seems even less likely to happen than fixing the handling of GENSEX discussions. <span class="nowrap"> <span style="font-family:courier">-- ]</span><sup>]'']</sup> (she&#124;they&#124;xe)</span> 00:31, 6 March 2023 (UTC)
::Shells-shells, topic bans are not "punishment", they are protection of the project from recurrent disruption. I don't know what you think AE does, but go observe it for a while, and you'll see that it largely hands out topic bans (and blocks). It is unlikely that either of the GENSEX editors recently sanctioned at ANI would not have been sanctioned at AE. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 01:05, 6 March 2023 (UTC)
:::I have read ], yes, which is why I specifically used the word {{tq|''punishing''}}. With the exception of its first sentence—I would rather say {{tq|bans ''should not be'' "punishment"}}—I completely agree with your comment. ] (]) 01:40, 6 March 2023 (UTC)
:::{{tq|Shells-shells, topic bans are not "punishment", they are protection of the project from recurrent disruption.}}
:::They are both. It's meant to be protective, but it's absolutely a "you did something wrong and now we're taking away your ability to edit here" punishment. &mdash; <b>]:<sup>]</sup></b> 19:17, 6 March 2023 (UTC)
::Well, I do think there are some issues with that framing: it's really the low hanging fruit/Wikipedia equivalent of a politician's baby kiss to say ANI is ugly and that we wish the process of dispute resolution could be more collegial--and less dispiriting for newcomers in particular. But nobody is excited when a dispute or issue grows to the point that it lands at ANI, let alone when a CBAN has to be issued, and when I check in at ANI, I fairly regularly see people doing their best to make the process (borrowing upon your wording here) as un-vicious, un-humiliating, and sympathetic as they can, ''in the circumstances''. But let's have a dose of realism and pay at least lip service to some important constraints here: sometimes there are values and priorities of our community and methodology (for providing reliable, neutral, factually-accurate material to serve the needs of our readers) that have to take precedence over encouraging the editing of every contributor, in every area, all the time.


== Request removal of PMR/Rollback ==
::That important caveat said, my overall thoughts are that you've identified a fruitful area here--indeed, maybe one of the few areas that actual stands a chance of improving the situation in question, as it stands. I think you are very much correct that more effort at the front-end, when onboarding volunteers, could pay immense dividends in the long run, in terms of decreased disruption, acrimony, and need to re-set editorial conduct when problematic patterns have already been formed. As you say, mentorship in one form or another is surely an under-exploited potential tool. I think there's a cognitive bias at work here that is not at all uncommon to institutions of governance: we are fixated with and dissuaded by the upfront costs, failing to rationally apply a longterm analysis.
{{atop
| result = Flags removed ]<sub>]<sub>]</sub></sub> (]/]) 22:52, 2 January 2025 (UTC)
}}


Hi, lately, I haven't been using my page-mover and rollback rights that often and I don't feel returning to the activity anytime soon. Can any admin remove these flags from my account. I relatively happen to support in file-renaming areas these days and have also decided to put in some efforts in this month's NPP backlog. So these rights should stay. Thank you. <small><sub><span style="color:SteelBlue;">Regards, </span></sub></small>] ] 10:19, 2 January 2025 (UTC)
::On the other hand, I am not surprised that "adopt-a-user" has failed to catch on: what a patronizing choice of title for such a program. I imagine it has an especially discouraging impact on precisely the type of editors we are talking about here and would most like to reach with such a scheme: those who come here specifically to edit in CTOP areas: some of those editors would be just simply battleground and avoidant of the idea of the need for guidance by nature and others, as a consequence of what their communities have historically had to deal with, are justifiably sensitive to implied condescension. Anyway, that last point is a nitpick observation. I agree the mentorship angle is something this community needs to invest in. Not just to ameliorate the issues being contemplated here today, but for purposes of editor retention and community unity/harmonized outlook.'']]'' 01:55, 6 March 2023 (UTC)
:{{done}}. ] (]) 10:25, 2 January 2025 (UTC)
:::I may simply be naïve, but I don't think ANI is really as bad as people say. It seems to work pretty well as an ad hoc tribunal, or as a grand jury. But once in a while it gets acrimonious, and the ''last'' people who should be subjected to an acrimonious ANI thread are new users. In fact I think there's far too much bureaucracy facing new users anyway (even excepting ANI), but that criticism is also {{tq|low hanging fruit}}. There ought to be better options, with lower stakes, in the first place.{{pb}}I agree completely with your second and third paragraphs. It would be wonderful for a mentorship culture to develop here, and 'Adopt-a-user' may well need a rebranding. ] (]) 03:12, 6 March 2023 (UTC)
{{abot}}
:Throwing this out there: ArbCom. We pay them to deal with problems that are, well, <strong>really</strong> bad. We haven't actually tried this yet; ] is not a "real" case.<span id="HouseBlaster:1678062426246:WikipediaFTTCLNAdministrators&apos;_noticeboard" class="FTTCmt"> ]]<sup>]</sup> 00:27, 6 March 2023 (UTC)</span>
::I've said before that I think a GENSEX2 case is ultimately inevitable, but why do you think an ArbCom proceeding would be preferable? It would ultimately take several months, dig even deeper into various individuals' editing habits, and probably result in more sanctions, on more editors, that are harder to appeal. Few things drive editors away from a topic area better and faster than ] attention. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 01:05, 6 March 2023 (UTC)
:::I don't know that I would agree that such a case would be ''per se'' a bad thing: if it gets to the point that ArbCom forms a case, presumably it will be a situation where there are at least potentially bad actors needing scrutiny--which would not be a happy occasion but would surely be better than their hiding their heads in the sand. That said, it would all come down to the particulars whether it would be a positive development in the aggregate.


== Insults, personal attacks and reverts of academic material ==
:::Those caveats made, I agree with your central point: I don't see how such a case would really remedy the systemic issues being contemplated here. For all its overriding authority, ArbComs remedies in a situation like this are rather limited. They can make a subject CTOP (and this one already is), they can sanction individual editors, sometimes they publically hold harmless someone who got pulled into a dispute through no disruptive fault of their own, and they can take steps to protect individuals from harassment. All vital work, such as it goes, but making substantial changes to our community structures and processes, at least in this context, is largely outside of their remit. To the extent we want to reform ANI or any of our other community processes, it's just not something we can pass to their shoulders. The buck stops here. '']]'' 01:19, 6 March 2023 (UTC)
{{atop|1=This appears to be done. - ] <sub>]</sub> 05:51, 7 January 2025 (UTC)}}
::::It depends what the issue is? If the issue is certain editors who cannot behave in the topic area, but the issue becomes too obfuscated in ANI discussions for the community at large to get involved, then ArbCom would be a good venue to deal with it. DS I don't think dealt with these problems too well either, and ArbCom directly does I think. ] (]) 13:07, 8 March 2023 (UTC)
* {{la|Naomi Seibt}}
:Sorry T. I do feel bad about opposing one of your remedies without proposing an alternative. The thing I keep hoping for in GENSEX is a group of three to five admins that hang around. It's the main difference I see between GENSEX and American Politics or Pseudoscience. The early intervention of an admin warning is little seen in GENSEX. I'm looking for things like "If you continue to bludgeon discussions/to misgender the article subject/to rely on evidently unreliable sources/to skirt the bounds of civility, I will block you." They'll have been witness to the patterns of editing that might eventually prove to have been problematic. The only other suggestion I have is stricter enforcement and clerking at AE. If we're counting on that as the good option, let's tune it up.{{pb}} Though I do think there are deep problems in GENSEX, I don't share the view that it's at the top of the CT/general sanctions problem pile. Within the past year, we've had knock-down-drag-outs tied to Armenia-Azerbaijan, Russia-Ukraine, AmPol, and Palestine-Israel. ] (] / ]) 00:59, 6 March 2023 (UTC)
After reverting that included references to peer-reviewed papers in academic journals, @] posted the following on the Naomi Seibt talk page: ".". ] (]) 12:05, 2 January 2025 (UTC)
:Yes, why haven't you done that? --] (]) 12:07, 2 January 2025 (UTC)
:Article in question is a ] x3. The initial reverts of the IP's edits were for ], since the IP included all the material in question in the lead with no mention in the body of the article. Does {{u|FMSky}} need ] for using the term "trash analyses"? Maybe. However, the IP's actions lean into the ] category, and that may call for either direct sanctions against the anonymous editor or protection/sanctions on the article in question. —''']''' (]) 12:09, 2 January 2025 (UTC)
::{{tq|Does FMSky need trouted for using the term "trash analyses"?}} How else would you describe the IPs additon of "In May 2020, she reiterated her dismissal of investigative evidence by endorsing" --] (]) 12:11, 2 January 2025 (UTC)
:::You deleted all academic sources that claim that she is far-right, including other sources that have nothing to do with ]. ] (]) 12:14, 2 January 2025 (UTC)
::::Which also indicates that you were more focused on reverting information you don't agree with, without first discussing it in the talk page. ] (]) 12:15, 2 January 2025 (UTC)
:::::Edit: . ] (]) 12:15, 2 January 2025 (UTC)
::::::Put your new content into the body of the article instead of the lead. The lead is a summary of the body --] (]) 12:16, 2 January 2025 (UTC)
:::::::Done. Now it’s a summary. ] (]) 12:20, 2 January 2025 (UTC)
::::::::User continues to stuff the lead with info not found anywhere else . A block or article lock would be appreciated --] (]) 12:24, 2 January 2025 (UTC)
:::::::::I will proceed with covering the whole lead in the rest of the page. Give me an hour or two. ] (]) 13:20, 2 January 2025 (UTC)
::::::::::Start with the body. Do the lede last. And work at article talk to make sure you have consensus before making major changes, especially to the lede. ] (]) 13:22, 2 January 2025 (UTC)
:::::::::The IP has come up with a more than sufficient number of reliable sources to back up the far right assertions (etc). However, the lead is not the place to stuff them: they should be in the body, and the lead should reflect that content. <b>]<small> + ] + ]</small></b> 14:25, 2 January 2025 (UTC)
* Not only is there a pattern of IP editors inserting large chunks of information to the intro about her right-wing ties, but I also see from 21 December that seemed to be at the start of the pattern, and that's from now-blocked user {{userlinks|FederalElection}}. At the least, that's a mitigating factor to excuse FMSky's heavy-handed reaction to these latest edits. At the most, it's grounds to revert the addition until a (new, civil, content-related) discussion at the talk page generates consensus to include it and/or protect the page—and that protection might need logged as CTOP enforcement. —''']''' (]) 12:23, 2 January 2025 (UTC)
*:You are consistently reverting edits that can be fully backed by reliable peer reviewed articles. You are refusing to acknowledge the scholarly literature. If any of you wanted to politely contribute to the article, you would not remove such sources. It’s not just the “chunk of information”, as you like to refer to it, but the constant removal of content you personally don’t agree with. Asking for the article to be locked is an effort to block others to edit, when the information provided is reliable. The bias extends to your plea to excuse FMSky’s insults. ] (]) 12:27, 2 January 2025 (UTC)
*::IP - from what FMSky is saying above it looks like the issue is that you're attempting to put material in the lede which is not elaborated upon within the body of the article. This is a manual of style issue. Maybe consider working at article talk to find an appropriate place within the article for your sources. ] (]) 13:13, 2 January 2025 (UTC)
*::Tread lightly, IP. Trying to link policy-based edits to personal bias is wading back into WP:ACCUSATIONOFMALICE. You will need to present strong evidence to back such accusations up. —''']''' (]) 13:16, 2 January 2025 (UTC)
*::I'll add that ] requires consensus before restoring material removed "on good-faith BLP objections". Even if the information was in the body, ] concerns arise with pretty much anything added to the lead. So if an editor feels material doesn't belong in the lead of a BLP, it's entirely reasonable to ask for there to be consensus before it's added back. ] (]) 09:50, 4 January 2025 (UTC)


I think everything's been said that needs to be said here. As long as ] now complies with the request to add the content to the body of the article before adding any summary to the lead, all users engage on the talk page, I don't think any admin action is necessary. ]] 13:37, 2 January 2025 (UTC)
:If there were no sanctions imposed, would you be making your proposal or this plea? ] (]) 01:23, 6 March 2023 (UTC)
{{abot}}
::Two out of three sanctions proposals went "my way", including one that I literally proposed, and the third one I only weakly opposed, so... <span class="nowrap"> <span style="font-family:courier">-- ]</span><sup>]'']</sup> (she&#124;they&#124;xe)</span> 01:46, 6 March 2023 (UTC)
:::That doesn't feel like an answer. There was literally nothing different in these reports than the thousands of reports before it, other than the accused throwing out so many bytes of text without reprimand. If your concern is separate from the results, you may want to wait and propose in isolation. I think divorcing your concern from the results may be helpful to your cause. ] (]) 01:55, 6 March 2023 (UTC)
::::I have not framed this thread as an objection to the outcome of the TT thread. I've framed it as what it is: about that thread, and several others, being "shitshow"s. <span class="nowrap"> <span style="font-family:courier">-- ]</span><sup>]'']</sup> (she&#124;they&#124;xe)</span> 02:00, 6 March 2023 (UTC)
::Tamzin here is clearly frustrated with the manner in which ] operates generally in these sorts of cases, and I don't think that this is purely some reaction to being dissatisfied with a single closing statement. She is being extremely candid in this thread, and, while I disagree with her proposal above, I do share her sentiment that there are certain topics and situations where ANI is not capable of handling disputes without consuming an inordinate amount of community time in exchange for ''at most'' marginal benefit to the community. She's being sincere here regarding her motives, and I don't think it drives the conversation forward to insinuate otherwise. — ]&nbsp;<sub>]</sub> 05:13, 6 March 2023 (UTC)
:For three months, trial structured discussion at ANI:
:#ANI reports are to be titled using the format "Editor name(s), topic area(s), type(s) of disruption". For example "BilledMammal, Platypus, Disruptive cite-tagging"
:#Editors wishing to make a statement on the report should create a fourth level section (====) titled using the format "Statement by editor name". There is no word or diff limit, but editors are advised that the longer it is the less likely it is to be read.
:#Editors may edit their statement as required; ] are waived, and editors making replies are advised to quote any relevant sections.
:#Editors may reply to no more than five statements; there are no limits to the number of replies they may make to those statements. Editors may additionally reply to any statement that discusses their behavior. Replies should not introduce new information, and should instead seek to clarify or discuss the information raised in the editors statement.
:#Statements should remain closely related to the initial topic raised. If additional behavioral issues need to be raised, including behavioral issues related to the editor who opened the discussion, editors should create a third level section (===) using the same format of "Editor name(s), topic area(s), type(s) of disruption".
:#To propose community sanctions, editors should create a fourth level section (====) titled "Proposed sanctions on Editor name(s)".
:#Editors !voting on community sanctions proposals should keep their !vote concise and reference their statement for more detailed arguments and evidence. Editors may not reply to other editors community sanction !votes.
:The intent of this suggestion is to keep discussions on topic, to prevent bludgeoning and impenetrable walls of text, and to try to introduce a level of neutrality into the opening of the discussions. It also attempts to keep things less structured and limited than AE, as I don't believe that level of structure is appropriate here.
:Issues I see are that the structure will be excessive for some discussions (for example, ] - although I do believe the proposed title format of "Polish IP range, Weedkiller (album), edit warring" would be more informative than the existing title), that it will make boomerangs more difficult, and that the structure will be difficult for editors to enforce. However, if editors are interested in attempting to apply structure to ANI, I hope that making a proposal - even an awful one - will at least spark a discussion on what that structure could look like. ] (]) 02:24, 6 March 2023 (UTC)


== Appeal of topic ban from 2018 ==
::Bill, I know it's a big ask, but I think a rudimentary mock-up in a sandbox might be helpful here: perhaps it's just me, but I am having a bit of difficulty visualizing the overarching format of how these pieces fit together. '']]'' 03:09, 6 March 2023 (UTC)
{{atop|There is consensus to remove this topic ban reached as part of an unblock. Closer's note: as a contentious topic if disruption were to happen again any uninvolved administrator could reimplement the topic ban. ] (]) 18:28, 3 January 2025 (UTC)}}
:::{{ping|Snow Rise}} See ]; I hope it manages to make it more clear. ] (]) 03:37, 6 March 2023 (UTC)
In January 2018 (I believe), I was topic banned from editing articles related to ] due to a number of idiotic edits that violated BLP. The UTRS ticket for this I believe is . In the time since then, I have demonstrated that I can edit Misplaced Pages constructively (I have 80,350 edits, a large number of which will be on BLP and BLP-related topics), and so I am requesting for this topic ban to be revoked. Whilst I do not plan to make large edits on Donald Trump articles, I would like to have the ability to edit articles on current US events from time to time e.g. to comment on them at ] where Trump-related article nominations often appear. Please could you consider removal of this editing restriction? Courtesy ping to {{U|Alex Shih}} who implemented the topic ban in the first place . ]] (]) 12:24, 2 January 2025 (UTC)
::::Definitely helps. Was close to what I had in mind when I originally !voted "Let ArbCom (or delegate) sort it out in a more structured way" because of the mess of accusations and counter-accusations threaded together. ] (]) 08:07, 6 March 2023 (UTC)
:For what it's worth, Alex Shih was removed as an administrator in 2019 and has not edited since August, 2022. ] (]) 17:29, 2 January 2025 (UTC)
:::::Reading sectioned discussion is always a massive pain to try and understand any lengthy discussion - I've never seen a good explanation of how to easily read replies and replies to replies in a smooth fashion in such a discussion, as well as seeing how the discussion tone in general changes as it runs. So on that basis alone, I'd be against any such trial - but especially as a general ANI structure. I believe points 1, 4, 6 do have serious potential value to them, and point 5 could be used in certain circumstances/categories of discussion, although I'd like to see a clarification on how it worked with threads that raised multiple behavioural issues initially. Would each need its own section? ] (]) 16:54, 8 March 2023 (UTC)
:First Law of Misplaced Pages Reform: Calls to reform a page, made on the page to be reformed, will result in no reforms. ] (]) 06:48, 6 March 2023 (UTC) :I'd generally support this. Joseph's topic ban from ITN/C and related pages was lifted more than a year ago, and there haven't been any problems in that area, so I have some optimism that this topic ban is also no longer needed. --] (]) 17:49, 2 January 2025 (UTC)
::I'm a little concerned that after the big mess in 2018 they still managed to get themselves blocked again in 2022. But, yeah, as Floq says, they seem to have moved past that and have a year's worth of productive editing now. They also seem to understand what got them in trouble in the first place, so I'll cautiously endorse lifting the TBAN. It needs to be understood, however, that with this much history if there's more problems I don't expect there will be much willingness to extend any more ]. ] ] 21:10, 2 January 2025 (UTC)
:I've started a discussion at ] to workshop a possible proposal. I feel that keeping it separate from this discussion may help keep it focused. ] (]) 12:37, 6 March 2023 (UTC)
:::Endorse lifting TBAN per above. ] (]) 23:44, 2 January 2025 (UTC)
:::Endorse removal of topic ban. ] <sub>(] / ])</sub> 02:09, 3 January 2025 (UTC)
:::Endorse removal of topic ban per ]. ] (]) 02:27, 3 January 2025 (UTC)
{{abot}}


== User:SpiralWidget vandalizing pages ==
== Closure Request: V22 RFC ==
{{atop|1=Given , it appears the OP has withdrawn their complaint. - ] <sub>]</sub> 21:58, 3 January 2025 (UTC)}}
<!-- ] 15:07, 16 March 2023 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1678979255}}
<s>I am reporting User:SpiralWidget for repeated vandalism on articles I have created or contributed to. Below is the evidence of their disruptive behavior:
{{Resolved|Closed by Isabelle Belato and Ingenuity. ] ] 15:23, 16 March 2023 (UTC)}}
The RFC at ] is overdue for a close. A request made at ] has been sitting for several weeks now, and it would be helpful if some brave soul(s) would attempt the close. Experienced closers are recommended, as with ~3000 edits it is one of the largest RfCs ever conducted on enwiki (second place by my count behind ]). Given the complexity and importance, it has been suggested that a panel of admins volunteer to close it collectively.


=== Evidence ===
Regards, <span style="font-family:Courier New;font-size:3">]</span><sup>]</sup> 01:31, 8 March 2023 (UTC)
1. – User:SpiralWidget removed sourced content and replaced it with false information. – This is when SpiralWidget first began vandalizing my contributions. He falsely alleged that simply creating a wikipedia article was to influence an election, and even posted a link to a ballotpedia page about an election in 2026 to encourage sabotaging the article. The reason this is concerning, is because the page is general information about Moliere Dimanche, an artist, a prison reform activist, and a litigant who accomplished a presidential case law and wrote a book. Nothing in the page promotes anything election related, and as can be seen in the link, SpiralWidget did not base the reason on anything other than unwarranted suspicions.


2.
:Might be best for someone to hat the discussion while a closer or closers are found - I took a look at the page history and it looks like another ~15 comments were added yesterday which continues to make the job even more laborious. ] (]) 11:10, 8 March 2023 (UTC)
– In this instance, SpiralWidget removed information from a discussion with Professor Tim Gilmore about Dimanche's high school teacher Mrs. Callahan, and a very effective way she helped students in. English class. Mrs. Callahan would give students key words from the play Caesar, and have them use them in an essay writing contest that was timed. Dimanche excelled at this and became an outstanding student in Mrs. Callahan's class. SpiralWidget took an issue that is not even contentious and used it to sabotage the article. It is sabotage because Caesar is a play that was actually written by Shakespeare. I don't think any reasonable person would find that as contentious because it was in an English class in high school, and Caesar is just one part of the lessons on Shakespeare. That's like if the interview was about Frankenstein, and the article stated that Dimanche excelled in studying Mary Shelley. It was unnecessary harassment.


3.
:May I urge that this be closed as soon as possible? Discussion is devolving into attacks. I get that this is a mammoth RFC, and that a good many people have weighed in and are inelligible to close it, but this has become an open sore, and leaving this as an open sore on our encyclopedia is not a good thing. ] (]) 18:52, 13 March 2023 (UTC)
– In this instance, SpiralWidget moved a redirect page to drafts after the article was pointed to a different article using Dimanche's full name instead of his nickname. His reason was so that there could be a discussion, but Misplaced Pages's guidance on this clearly states that a formal discussion is not necessary for redirects, and Misplaced Pages's deletion policy discourages deleting duplicate pages. It even encourages editors to delete entire text and replacing it with redirects. Yet, again, SpiralWidget took it upon himself to allege political motivations, and none of it is true.


4.
:As I said on RFCLOSE, I am uninvolved and can be part of a panel close if needed. Multiple people have expressed that they would like an administrator to help close, so if any admin could volunteer that would be great. &mdash;&nbsp;]&nbsp;(]&nbsp;&bull;&nbsp;]) 00:17, 14 March 2023 (UTC)
- After SpiralWidget did that, he then nominated ] for deletion, again alleging that it had something to do with an election for governor in 2026. This is not true. The article talks about Dimanche's humble upbringing, his time spent in prison, his efforts in local politics in Orlando, his art, and a case law he helped accomplish in the 11th Circuit that set precedent regarding the ]. And even if it did, Misplaced Pages has many candidates for office. Misplaced Pages even displays election results, gains by party affiliation, laws introduced, and many other accolades. This is what makes me believe SpiralWidget has some type of animus for Mr. Dimanche, because he constantly makes an issue out of the election, when the article does not focus on that at all.
:Isabelle Belato has come to the task! ] (]) 19:01, 14 March 2023 (UTC)


5.
== 33 AfDs in 3 minutes ==
- The vandalism didn't stop there. SpiralWidget then went to ] and nominated that page for deletion as well. Why, because Dimanche was a part of that case. He lied and said that the case was not notable, before asserting that it only made Dimanche look good. This is ridiculous and appears to be hateful. This is a case law, meaning it is not something Dimanche had control over at all. Also, the "Precedential Status" of the law is "Precedential". The case has been cited by judges all across the nation to resolve an additional 178 federal cases. To put that in perspective, ] was cited 2,341 times in resolving federal cases since 1973. This is approximately 46 citations per year. Since ] was passed it averages about 20 citations a year. So for SpiralWidget to lie and say that the case is not notable, when clearly, the judge of this country would state otherwise is nothing more than vandalism. Additionally, Misplaced Pages already found all of the related laws and indexed them accordingly.

] (]) is vandalizing my pages if they even mention Dimanche, and he is doing harm to genuine, good faith editing. I believe the articles about Dimanche are necessary and important because his prison experience is well documented, and his art is unusual. Renown scholars like Tim Gilmore and Nicole Fleetwood have given thoughtful analysis to his art, and the art is widely recognized. I don't think these articles should be nominated for deletion, and I would request that they be taken out of that nomination, and SpiralWidget be prohibited from further editing on the subject of Dimanche.

6. List affected articles: ], ], etc.

=== Context ===
- This behavior has been recurring since SpiralWidget used the ballotpedia link the first time and persists today.
- I believe this violates Misplaced Pages’s policies and discourages editors from adding to Misplaced Pages.

I have notified the user on their talk page using ==Notice of noticeboard discussion==
] There is currently a discussion at ] regarding an issue with which you may have been involved. Thank you.<!--Template:Discussion notice--><!--Template:AN-notice-->. I kindly request administrative intervention to address this issue.

] (]) 18:36, 2 January 2025 (UTC)</s>

:First, you need to read and understand the definition of "vandalism" in ]. Next, you are not allowed to remove properly placed AfD notices until the AfD has been properly closed. I do not see anything improper in Spiralwidget's edits that you linked. I would advise you to drop this complaint and read over our ] before resuming editing. ] 18:47, 2 January 2025 (UTC)
::Thank you for your feedback. I understand that I should not remove AfD notices before they are officially closed, and I will follow the proper procedures moving forward. I will also review WP:Vandalism more thoroughly to ensure I’m taking the correct steps in addressing any inappropriate edits. I appreciate your advice and will proceed accordingly. ] (]) 18:54, 2 January 2025 (UTC)
:Hi! I feel like I need to weigh in here on my perspective.
:*I was reviewing articles on ] back in September (EDIT: Turns out it was November. Seems like longer ago.) and stumbled upon ], which had been submitted by NovembersHeartbeat (Diff1 in the list above). I then found that he was running for Governor of Florida in 2026, and added a comment on the article pointing this out for future reviewers (as I did not feel strongly about the subject, and I am not so familiar with ], which was the main claim of notability).
:*Following this, NovembersHeartbeat responded here https://en.wikipedia.org/search/?title=Draft%3AMoe_Dimanche&diff=1256694716&oldid=1256642401 and accused me of election interference.
:*I then commented on ] because I felt I needed to respond to this. NovembersHeartbeat then responded negatively, but eventually I decided to leave the issue and bookmark ] on my watchlist in order to follow the conversation from then on.
:*On 2 January, earlier today, I opened my Watchlist to see that ] had been moved to mainspace by NovembersHeartbeat. I then pressed the "revert" button, which I wrongly assumed would revert the article to draftspace. Turns out, this was not possible because NovembersHeartbeat had NOT published Moe Dimanche as an article; instead, he had made a new article, ], with a new name, in order to get past the AfC process (which was not going well for Dimanche at all...); as a result, the attempted reversion did not work at all. I then decided that, although I believe I was entitled to go for speedy deletion, I would nominate the article for deletion (I still have ] concerns and I don't think he passes ]) and also nominate ], which has also been created by NovembersHeartbeat recently.
:*In addition, I would like to question whether there is ] going on here. I think a pertinent recent example that looks suspicious to me is the upload of the image https://commons.wikimedia.org/File:Moliere_dimanche.png which was uploaded at 03:26, 1 January 2025 (i.e. 22:26 on 31 December Florida time) by user https://commons.wikimedia.org/User:Moe_Dimanche, who I am assuming is the subject himself in the flesh. This was then added to the article in this edit by NovembersHeartbeat https://en.wikipedia.org/search/?title=Moliere_Dimanche&oldid=1266552816 on 04:40, 1 January 2025 (23:40 on 31 December Florida time). This is only slightly over an hour after the file itself was uploaded, at a time when most people were at a New Years Eve party. I am not making accusations here, but I am concerned that Dimanche is having communication with NovembersHeartbeat. Either that, or NovembersHeartbeat is indulging in ]... Would NovembersHeartbeat like to comment on this? ] (]) 19:05, 2 January 2025 (UTC)
::Well, I was advised to drop the complaint, but if you still want answers, I don't mind telling you as I have told you before, I do not have any conflicts of interest. Your whole approach to this topic just seems personal. Even here, the content of the article is not in question, the facts are not in question, you just seem to believe that I am the subject. I made this complaint because I feel like what you are doing is harassment, and you might know the subject yourself or have some type of rivalry against him. I thought Misplaced Pages had a mechanism to prevent that, and I was wrong. I don't know what else to tell you. ] (]) 19:22, 2 January 2025 (UTC)
:I checked diff 2 in the complaint, and Spiralwidget is correct: the source does not support the text. Spiralwidget was justified in removing it. ]&nbsp;] 22:08, 2 January 2025 (UTC)
::"Mrs. Callahan would give students key words from the play Caesar, and have them use them in an essay writing contest that was timed. Dimanche excelled at this" is from NovHeartbeats, but none of this is in the source. How does November know so much about how these assignments worked? Was November in the classroom, or is November using sources the rest of us can't see? ] (]) 23:53, 2 January 2025 (UTC)
:::The exact text from the source is {{quote|"And I had a really good English class back at West Orange High School in Orlando. Ms. Callahan. I couldn’t wait to get to her class. She’d give us a certain amount of time to write a story with keywords from a play we were reading, like Julius Caesar."}} The source says exactly what you just quoted. ] (]) 00:02, 3 January 2025 (UTC)
::::The source says nothing about whether he was good in the class ("excelled") nor does it say "he enjoyed studying Shakespeare". ]&nbsp;] 00:25, 3 January 2025 (UTC)
::::The source doesn't mention any contests as you seem to know about. And its an interview of Moliere, with two single line questions asked by the interviewer. It definitely doesn't support anything except Moliere saying he had a favorite class, which isn't encyclopedic. ] (]) 00:37, 3 January 2025 (UTC)

This is discussion is turning into a content dispute, which doesn't belong here. There's a bit of ] going on but right now I don't see a need for admin intervention for either editor. ]] 15:31, 3 January 2025 (UTC)

While there is a content dispute in play here, I think behavior is a problem as well...but it's largely by the OP. Remarks like " is vandalizing '''my''' pages" ('''emphasis''' added). {{ping|NovembersHeartbeat}}, I would strongly advise that you read ], ], ], and ]. These aren't your pages. Anyone can edit them. If you have a disagreement, then bring it to the talk page. What you are describing as vandalism, is normal editing and disagreement; I would encourage you to ] as they are inherently hostile when unsubstantiated. This is a normal part of the collaborative editing process. If you don't, your complaints will not only be ignored, but ]. I understand that people may feel that some subjects aren't notable to get their own page and nominations for deletion can feel personal. I've weighed in for inclusion on the subject. Try not to take it personally. ] (]) 19:36, 3 January 2025 (UTC)
{{abot}}

== Repeated tool abuse by ] ==
{{atop|Not tool abuse. The IPv6 editor should discuss this with FlightTime, not ANI ] ] 06:45, 3 January 2025 (UTC)}}
I have been working on the article ] with a view to possibly improving it to featured article status at some point in the future. At this point, the edits are mostly restructuring to bring the article into a shape that can then be further developed, depending what it still needs when that first step is done. {{U|FlightTime}} took exception to some edit I made between 22nd and 23rd of December , without clarifying exactly which edit they thought was problematic. We had , and . At that point, I believed we had cleared the air, and the situation would not repeat itself.

However, today, they of mine, all in one go, again without any explanation of which edit(s) they felt were problematic. Thus, they make it impossible to discuss or remedy what they felt was the problem. In my opinion, this constitutes tool abuse, and if they cannot improve their communication with IP users and ideally use the tools in a more targeted way, this is a problem for the community.

Thank you for your time and consideration, and any help in getting to a more constructive collaboration on this article.

] (]) 00:53, 3 January 2025 (UTC)

: This is not tool abuse, you are being reverted with reasons, and you should discuss the matter with FlightTime. ] (]) 00:58, 3 January 2025 (UTC)
:I'm not sure what you mean {{tq|without any explanation}} as his clearly documents his reason as {{tq|Reverted good faith edits by 2A02:8071:184:4E80:0:0:0:EAC0 (talk): Unsourced, unexplained content removal, unsourced OR}}. Please note that he did assume good faith (not maliciousness), and that he appears at first glance correct that you were removing content without reason, and adding unsourced and/or original research to the article, which is not permitted. Please use the article talk page at: ] or talk to the editor directly on their talk page at ] and work on building consensus instead of readding the same or similar content to the article. ]&thinsp;] 01:12, 3 January 2025 (UTC)
::Again, which are the pieces that you are now objecting to? We are talking about 17 edits, so please be specific! Thank you. ] (]) 06:19, 3 January 2025 (UTC)
{{abot}}

== Emoji redirect ==
{{atop|👌 - ] <sub>]</sub> 05:33, 3 January 2025 (UTC)}}
Was trying to create ] as a redirect to ]; the film does not actually have a title and was represented in posters by the ] aka the ]. Apparently the emojis are on a blacklist, it would be great if someone can create this rd, thanks. ] (]) 01:35, 3 January 2025 (UTC)

:{{Done}}. ]<sub>]<sub>]</sub></sub> (]/]) 01:48, 3 January 2025 (UTC)
{{abot}}

== Topic ban appeal ==

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)

: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)
::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)
:::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)
::::Found it. ]. ] <sup>(]) (])</sup> 04:35, 4 January 2025 (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)
*'''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)

== Request to Fix Redirect Title: Camden stewart ==
{{atop|1=Looks like this is done. - ] <sub>]</sub> 18:39, 4 January 2025 (UTC)}}
Hi, I need help correcting the capitalisation of the redirect "Camden stewart" to "Camden Stewart" as the surname is improperly lowercase. I cannot make the change myself because redirects require admin intervention for title corrections. Could an admin please assist? Thank you! ] (]) 05:19, 3 January 2025 (UTC)

:How many redirects are you making? I see a lot of activity today. —&nbsp;]&nbsp;] 05:25, 3 January 2025 (UTC)
::Thanks for your response! I’m just setting up a few redirects to make it easier for people to find Camdenmusique's article, like ''Camden Stewart'' or ''Camden Music''. Let me know if anything needs adjusting, appreciate your help!" ] (]) 05:30, 3 January 2025 (UTC)
:@]: I have moved the article to draftspace at ]. If you have a ] with Camden Bonsu-Stewart (which I suspect that you may since you are ] and you ] his professional headshot), you must declare it ]. You should also not republish the article until it has been reviewed by an experienced editor at ]. ] (]/]) 05:30, 3 January 2025 (UTC)
::Thank you for your feedback! ] (]) 08:09, 3 January 2025 (UTC)
{{abot}}

== Andra Febrian report ==
"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">—&nbsp;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 ===
:: <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)

== Proposal to vacate ECR remedy of Armenia and Azerbaijan ==
{{atop|1=Already closed. - ] <sub>]</sub> 01:36, 4 January 2025 (UTC)}}
There is a proposal to vacate the ECR remedy of ] at {{slink|Misplaced Pages:Village pump (proposals)|Remove Armenia-Azerbaijan general community sanctions}}. ] (]/]) 00:53, 4 January 2025 (UTC)
{{abot}}

== Cannot draftify page ==
{{atop|1=Done. - ] <sub>]</sub> 18:38, 4 January 2025 (UTC)}}
I tried to draftify ] but a draft exists with the same name (and same content before I blanked it). Could an admin delete the draft so I can draftify the article? {{User:TheTechie/pp}} <span style="font-family:monospace; font-weight: bold"> <span style="color:ForestGreen;font-size:15px"> ]</span> (<span style="color:#324c80">she/they</span> {{pipe}} ]) </span> 00:59, 4 January 2025 (UTC)
:{{done}} {{ping|TheTechie}} ] has been deleted. — ] <sup>]</sup> 01:26, 4 January 2025 (UTC)
{{abot}}

== Remove PCR flag ==
{{atop|1=Flag run down. - ] <sub>]</sub> 18:38, 4 January 2025 (UTC)}}
Can an admin remove my Pending changes reviewer flag as I have not used it recently. Thanks <span style="font-family:monospace;font-weight:bold">]:&lt;]&gt;</span> 06:26, 4 January 2025 (UTC)
:Done. ] (]) 06:40, 4 January 2025 (UTC)
{{abot}}

== "The Testifier" report ==
{{Moved discussion to|Misplaced Pages:Administrators' noticeboard/Incidents#"The Testifier" report| ] (]/]) 18:06, 4 January 2025 (UTC)}}

== Problem with creating user talk page ==
{{atop {{atop
| result = CU blocked as sock by {{noping|Spicy}}. ] (]/]) 01:10, 5 January 2025 (UTC)
| status =
| result = Discussions closed, <s>OP</S> apologized. <span style="font-family:Calibri; font-weight:bold;">] ]</span> 01:37, 14 March 2023 (UTC) '''Edit''' it was of course the original AfD nominator, not the OP of this post. Apologies for confusion, sloppy phrasing. <span style="font-family:Calibri; font-weight:bold;">] ]</span> 13:22, 14 March 2023 (UTC)
}} }}


Hello, I'd like to get some help to create the talk page of user {{user|BFDIisNOTnotable}} to warn them against ] with {{tlsp|uw-ewsoft}} or a similar notice. Trying to create the page gives a notice that "bfdi" is in the title blacklist. I wonder how the user was allowed to create the account today, given that from what I can see, the blacklist should also affect usernames...? I obviously can't notify the user of this AN post on their talk page. ]&nbsp;(]) 14:01, 4 January 2025 (UTC)


:I have created the talk page. No idea why 'BFDI' is on the blacklist, and if so, why a user name by that was allowed - that's something for cleverer heads than mine... ]] 14:13, 4 January 2025 (UTC)
::I think it stands for "Battle for Dream Island". See ]. ] (]) 14:25, 4 January 2025 (UTC)
:::Ah, I wondered if it was linked to ]. ]] 14:32, 4 January 2025 (UTC)
::::As to the technical reason that the username could be created, the reason is that accounts are not actually created on this wiki. They are created globally. As a result, us blacklisting anything can't prevent account creation. ] ] 18:09, 4 January 2025 (UTC)
:::::This particular account was ]. ] (]) 01:04, 5 January 2025 (UTC)
{{abot}}


== Administrators' newsletter – January 2025 ==
If I counted correctly, {{User5|User=Dawid2009}} started 33 AfD discussions in 3 minutes, probably using a bot, copy-pasting the same rationale, not notifying relevant editors, and obviously not performing any ]. His targets are wives/partners of footballers and the rationale is "''She is famous because of relationship with her parthner. Apart from that what is her independet notablity? For now article is quite poorly sourced''", when in many cases the articles have decent sourcing, the subjects were notable before and beyond their engagement to footballers and are even more notable than their counterparts (eg. ] has a prominent 20 years career on Italian television and is certainly not notable for her relationship with ], or ] is better known than her husband, who in fact is the subject of articles titled . I was going to vote "Speedy Keep" on any of them as disruptive, but I really think they should be speedy closed on procedural grounds. ] 09:11, 13 March 2023 (UTC)
:They also didn't add the AfD template to any of the articles they nominated. ■&nbsp;∃&nbsp;]&nbsp;⇔&nbsp;∃&nbsp;]&nbsp;''';''' 11:05, 13 March 2023 (UTC)


] from the past month (December 2024).
I've speedy closed the lot as disruptive AfDs where clearly no ] at all was done, and in many cases the article wasn't even read apparently. None of them had any delete votes, a lot had keep votes with evidence of notability, and the few articles I spotchecked also were about notable persons in their own right. ] (]) 11:41, 13 March 2023 (UTC)


<div style="display: flex; flex-wrap: wrap">
:Good call. '''''] ]<small style="COLOR:#313F33"> and the soapdish</small>''''' 11:52, 13 March 2023 (UTC)
<div style="flex: 1 0 20em">
:Thanks {{u|Fram}}—I was going to do it myself, but I think you have to be auto- or extended-confirmed to use the Script. And I gulped at closing 33 AfDs manually! ] 13:21, 13 March 2023 (UTC)
::I did it manually :-) ] (]) 13:27, 13 March 2023 (UTC)


] '''Administrator changes'''
I would like to sorry for that incident. I will never do again so non-patient and fast approach. I have did it after revievind massviews from the category:Association footballers' wives and girlfriends too fast and have choosen articles with bit few references. Most articles I nominated to improve them but I had not any bad faith in that to be honest. Next time I will be more careful. Sorry for disturbing time of some editors and not clear view at afd now.... but it was too fast accident from my side, not understand me very wrong, I regret. ] (]) 13:39, 13 March 2023 (UTC)
:] ]
:Nice work Fram. Bots should never be used to open a series of AfDs or the like, too much chance of things like this occurring. ] (]) 13:42, 13 March 2023 (UTC)
:] {{hlist|class=inline
:(after edit conflict) No great harm done, but just remember that women can be just as notable as (or more notable than) their male partners. ] (]) 13:45, 13 March 2023 (UTC)
|]
|]
}}
:] {{hlist|class=inline
|]
|]
|]
|]
|]
|]
|]
}}

] '''CheckUser changes'''
:] {{hlist|class=inline
|]
|]
|]
|]
|]
}}
:] ]
:] ]

</div>
<div style="flex: 1 0 20em">
]

] '''Oversight changes'''
:] {{hlist|class=inline
|]
|]
|]
|]
|]
}}
:] ]

</div>
</div>

] '''Guideline and policy news'''
* Following ], ] was adopted as a ].
* A ] is open to discuss whether admins should be advised to warn users rather than issue no-warning blocks to those who have posted promotional content outside of article space.
] '''Technical news'''
* The Nuke feature also now ] to the userpage of the user whose pages were deleted, and to the pages which were not selected for deletion, after page deletions are queued. This enables easier follow-up admin-actions.

] '''Arbitration'''
* Following the ], the following editors have been elected to the Arbitration Committee: {{noping|CaptainEek}}, {{noping|Daniel}}, {{noping|Elli}}, {{noping|KrakatoaKatie}}, {{noping|Liz}}, {{noping|Primefac}}, {{noping|ScottishFinnishRadish}}, {{noping|Theleekycauldron}}, {{noping|Worm That Turned}}.

] '''Miscellaneous'''
* A ] is happening in January 2025 to reduce the number of unreviewed articles and redirects in the ]. ]

----
{{center|{{flatlist|
* ]
* ]
* ]
}}}}
<!--
-->{{center|1=<small>Sent by ] (]) 15:46, 5 January 2025 (UTC)</small>}}
<!-- Message sent by User:DreamRimmer@enwiki using the list at https://en.wikipedia.org/search/?title=Misplaced Pages:Administrators%27_newsletter/Subscribe&oldid=1266956718 -->

== user:Uwappa: refusal to engage with WP:BRD process, unfounded allegation of ] violation, unfounded vandalism allegation ==
{{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)}}
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.

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 ].

'''Diffs:''' ''(all timestamps UTC. NB that I am in England => UTC+00:00, Uwappa is in Australia => UTC+10:00 ) ''
* : 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''

* Uwappa reinstates their counter-reversion of the template.
* 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.

---
* 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)

: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)
::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 ]

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 ], ], ] 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)
:::::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)
: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)
::I did not make a legal threat. ] (]) 08:33, 6 January 2025 (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)
:::{{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)
::::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)


: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)

* 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)
*: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)
* 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=]}}.
:* Suggestion: Add the following calculator to ]:

{{calculator|id=edits|type=number|steps=1|size=3|default=3|min=0}}
{{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)
::* 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.
: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)
{{ab}}
*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)

== An inappropriate template being added to many pages ==
*{{userlinks|Oct13}}

A user is adding the "mortal sin" template to a large number of articles where it doesn't belong . I've reverted 3 of them that were added to the articles I have watchlisted. Could someone who knows how to do massive reverts take care of the others? Thanks. ] (]) 11:51, 6 January 2025 (UTC)

:Discussion at ]. ] (]) 12:07, 6 January 2025 (UTC)
:I've reverted the addition of the template. <b>]</b> (] • ] • ]) 12:13, 6 January 2025 (UTC)
:The template as been deleted per ]. <b>]</b> (] • ] • ]) 12:35, 6 January 2025 (UTC)

A look through this editor's talk page shows that there is a wider issue with their editing about religion. Regarding this specific issue they have done something quite similar before (see ]) along with a number of articles they've written moved to draftspace and that have been nominated for deletion. Their contibution history also shows a significant portion of edits having been reverted. Before suggesting any action I'm keen to hear from {{u|Oct13}} on this. <b>]</b> (] • ] • ]) 12:35, 6 January 2025 (UTC)

:Btw, the last time Oct13 has ever edited a noticeboard was on June 6 2020. The last 2 times they edited a talk page were on February 17 2022 and April 15 2020. ] <sup>(]) (])</sup> 17:40, 6 January 2025 (UTC)
::It also looks like the main thing they have done on their own talk pages in the last seven or eight years is to just repeatedly blank it. We may have a ] situation here. ] ] 01:45, 7 January 2025 (UTC)
This editor's editing looks to consist largely of making inappropriate edits, "sourced" if at all to unreliable sources, and perhaps in hopes that if enough of that is done, a few will slip by. As we're unlikely to hear from them, I'd be in favor of indefinitely blocking them, at the very least until they meaningfully engage regarding the problems with their editing. ] <small><sup>]</sup></small> 01:55, 8 January 2025 (UTC)

:I second that. As we wait here, they continue to edit, and all have been reverted. Perhaps an articlespace block until we get a satisfactory response?—&nbsp;]&nbsp;] 03:23, 8 January 2025 (UTC)
::I've blocked them indefinitely from mainspace. ] <small><sup>]</sup></small> 05:36, 8 January 2025 (UTC)
::Liz invited them to reply here. Let’s keep this open for now and see if the user responds, now that regular editing of articles is blocked.—&nbsp;]&nbsp;] 15:11, 8 January 2025 (UTC)

== Ottawahitech, requesting an appeal on their talk page restriction ==
{{atop|1=User wants to use Misplaced Pages as a social network. ]. - ] <sub>]</sub> 22:05, 6 January 2025 (UTC)}}
Hello, I find that {{user|Ottawahitech}} has opened an appeal about their talk page restriction.


As I have told the blocking admin, whom I am not pinging at their request, I do not wish to appeal my block. Before I was blocked at the discretion of Beeblebrox/Just Step Sideways I made about 75,000 "edits" to the English Misplaced Pages, and have continued contributing to other Wikimedia projects since my Block in 2017. I enjoy my recent volunteer activity more than I did my activity here, and do not ask for a complete unblock. However, I would still like to be able to communicate with fellow wikipedia editors and request the removal of the restrictions that have been imposed on my user-talk.<br>
Notice to the admin handling this request: Just to let you know I am a very infrequent visitor to the English Misplaced Pages, and as such there is no urgency in acting on this request. Thanks in advance, Ottawahitech (talk) 23:26, 4 January 2025 (UTC)

I'd copy them here. Though in my opinion, the restriction just came along commonly as the indef block. Hoping someone may like to review that. ] 15:09, 6 January 2025 (UTC)

:This might be better at ]. — ] (]) 15:12, 6 January 2025 (UTC)
::Moved per request] 15:13, 6 January 2025 (UTC)
:::What was Ottawahitech blocked for to begin with? My understanding is something to do with bad page creation attempts and / or edit warring at article talk. Is this correct? Has Ottawahitech demonstrated that they understand what they did was wrong? Because they appear to have been indeffed in 2017 and indefinite doesn't mean forever. If they've shown recognition of what led to their block and have committed not to repeat their mistakes then I'd be inclined to say this looks like a reasonable request. ] (]) 15:22, 6 January 2025 (UTC)
::::Their previous block seemed a little bit like ] block, and I'm, auch, due to my interaction with them on another project, I'm inclining a not unblock. ] 15:29, 6 January 2025 (UTC)
:@]: why did you post this here? I didn't see Ottawa make a request for this to go to AN. Additionally, blocked means blocked. We don't let blocked editors use their talk page to shoot the shit with other editors. If Ottawa wants to chat with old friends, they can email each other. ] (]/]) 15:47, 6 January 2025 (UTC)
::I agree that we should decline this request. We're here to write an encyclopedia, not run a chat board. If Ottawahitech is interested in the social aspects of wikipedia, they should pursue other communication channels. Perhaps the ] is what they're looking for. ] ] 20:38, 6 January 2025 (UTC)
:::Argh. I came here for an entirely different reason, but I am unsurprised to see the persistent ] behavior of this user continues on.
:::I blocked them in 2017 for persistent failure to abide by basic content policies, mainly being very experienced but still regularly creating pages that qualified for speedy deletion. I believe there was a discussion somewhere that led to it but I seem to have failed to note it in the block log. What I do recall is that they did not participate in that discussion.
:::Several months later another admin revoked talk pages access because they were using the page to chat, and to ask other users to proxy for them, while not addressing the block.
:::Four years later they contacted me via another WMF site and I did them the courtesy of re-instating their talk page for purposes of appealing their block. They then indicated they didn't want to do that, they just wanted talk page access back.
:::And that's still all they want. They don't ''want'' to rejoin this community as an editor. There's no point to even discussing this except to consider the possibility of re-revoking TP access to avoid further time wasting nonsense like this. ] ] 21:22, 6 January 2025 (UTC)
FTR, ] that led to the block of Ottawahitech. --'']'' <small>] ]</small> 21:58, 6 January 2025 (UTC)
{{abot}} {{abot}}


== ] backlog doin' great ==
== Self-requesting community review of revision deletion ==


I know I ruffled some feathers with the way I approached this last month, but I'm pleased to report that as of this writing there are less than twenty pending unblock requests, many of those being CU blocks. Not that long ago the daily average was closer to eighty. I certainly did not do this alone, in fact I was ill for a week there and did basically nothing. Quite a number of admins and others pitched in in various ways over the past few weeks to move things along.
I just revision-deleted 122 revisions of ] going back to 2009 under RD1 due to about half of the article being a copyright violation from and . While normally we don't nuke that long of a span of article history for copyvios, I felt that the massive scope of the situation warranted it. Have placed a message on the article's talk page to explain the removal/deletion and have left a copyvio warning for the editor who added the material, as they are still semi-active. Given the extensive amount of revision deletion I did, I would appreciate an informal community review of the scope of the RD1. Thanks! ] <sub> '']''</sub> 16:46, 13 March 2023 (UTC)


That's great, but we should not get complacent, as that was what led to the backlog being so bad before. Thanks to everyone who helped get it to where it is now. I would again encourage any and all admins to pitch in whatever they can to keep this manageable. Any substantive review of an unblock request helps. Thanks again to ''everyone'' who helped make this suck a little less. ] ] 21:32, 6 January 2025 (UTC)
:@] “{{tq| While normally we don't nuke that long of a span of article history for copyvios, I felt that the massive scope of the situation warranted it.}}” Reluctance to do revdels like this has only very recently become “practice”— it’s not actually based in any policy, more just how some admins feel right now. They were done for years previously with no issues. As far as that revdel goes I’d say it’s very safely in discretion; I’ve revdeled much more going back much longer. ]] 16:54, 13 March 2023 (UTC)
::Speaking only in general, I'll echo Money that we might decline to do certain RD for Streisand reasons and where it'll have such a huge impact on the article history. But the alternative of leaving blatant copyright violations in the history doesn't strike me as much of an alternative. Best, ] (]) 18:22, 13 March 2023 (UTC)
:Given the extent of the copyrighted material introduced in the article, the decision to apply revision deletion is well justified. -- ] (]) 17:24, 13 March 2023 (UTC)
:Looks like a solid use of RevDel here. No issues I can see. Deleting that much history is never what we hope for, but often necessary. <span style="font-family:Courier New;font-size:3">]</span><sup>]</sup> 17:35, 13 March 2023 (UTC)
:The ] says "{{xt|Administrators hold discretion on the appropriateness of revision deletion for each case.}}" so what you did was perfectly within policy. Given that appears to be plagiarism of an offline source, it's no wonder it sat around for years. ] ] ] 19:21, 13 March 2023 (UTC)
:Is there any point to these self-requested community reviews? The very fact that review has been requested indicates that the action was almost certainly correct. The actions that are questionable are those that are kept under the radar. ] (]) 19:31, 13 March 2023 (UTC)
::{{tq|Is there any point to these self-requested community reviews?}} Appears to this editor as an admin looking to demonstrate transparency and accountability. Also demonstrates behviour to be modelled; if you're uncertain, it's ok to ask, rather than default to self-confidence. As method, it's a {{thumbs up}} for me. Regards, ] (]) 22:23, 13 March 2023 (UTC)
::Personally, I think so. The community should encourage a collaborative environment where editors feel free to discuss actions they've taken and openly discuss pros and cons. ] (]) 00:48, 15 March 2023 (UTC)
:It's unfortunate that this was necessary, but nonetheless, it was necessary. We certainly should not be leaving copyright violations in article history. ] <small><sup>]</sup></small> 00:43, 14 March 2023 (UTC)
:{{Peanut}} I can understand your sentiment a bit, I once got a bit suspicious of an article and reported it and watched edits going back to ~2010 get stripped away (article was very low visibility). But at the end of the day, the point of cleaning up copyvios is to keep Misplaced Pages a law abiding website (or as law abiding as you can with editors leaking the addresses of whoever they're mad at at the moment), so with that in mind, you did your job well and used the tool properly, even if it nuked a lot of the page. ] ] 16:32, 14 March 2023 (UTC)


== Call for mentors ==
== ANI thread titled Japanese help needed ==


There's a discussion at ] about extending the mentorship module to all new accounts. Presently, all new accounts are ''assigned'' a mentor, but only half of them receive the module that allows them to send questions to that mentor directly from the newcomer homepage. We'd like to extend the module access to ''all'' new accounts, but we're a bit short of the "ideal" number of mentors to do so - we're looking to get about 30 more. Posting here because the experienced users who haunt this noticeboard are likely to make good mentors. Basically the only requirement is "not jerk, has clue", with a side of "you should be someone who logs in frequently enough that your mentees won't feel ignored". Most of the questions you get are very easy to resolve. Some are harder. Every so often you get something actually fun. -- ] (]) 23:31, 6 January 2025 (UTC)
It no longer needs Japanese-speaking help, as the translations have been confirmed to be awful.
:I signed up sometime last year, and I'd guesstimate that I've received questions from maybe 10% of the accounts I'm assigned to mentor. So far (knock on wood) it hasn't been onerous at all. (Hoping that will encourage more editors to give it a try.) ]&nbsp;] 23:37, 6 January 2025 (UTC)
:Just signed up. I had played with the idea before, but given there are well over a hundred mentors and I don't hear much about it, I assumed it wasn't terribly active or in need of more people. ] (]) 03:40, 7 January 2025 (UTC)
::I've noticed I'm getting fewer questions, which I assume is because more mentors have signed up over time but the number of new accounts receiving the module has remained constant (it's a rare mentee who comes back and asks multiple questions over time). So it's true in a way that it didn't really need more people. I expect that you'll notice a significant boost when it goes to 100% and then a gradual decline again. -- ] (]) 14:31, 7 January 2025 (UTC)
:Time to add an option for three time the number of mentees assigned. ] (]) 07:01, 7 January 2025 (UTC)
::Seconding this, I wouldn't be opposed to taking over more mentees if there is a need for it until we get more mentors. ] (] · ]) 22:20, 8 January 2025 (UTC)
:::Agreed, though the max number of mentees per page might want to be increased to 50 from 25. ''']]''' 00:15, 9 January 2025 (UTC)
:I signed up a week ago, and only got a single question asked of me. How many people are using the newcomer dashboard? There, I have found, aren't many users signing up and editing per day, per ListUsers, so I can't imagine there are very many people using the mentorship at all.
:I'd be curious to see what automatically assigning mentors would do to retention rates (maybe that's written somewhere). ''']]''' 17:49, 7 January 2025 (UTC)
::I've been "twice as many" assigned for quite awhile now (I think I was one of the first mentors when the program even launched) and I'd say it's not atypical to only get ten or so queries a month. You can look through my talk page archives if you want a more accurate number (also note that sometimes I revert mentee questions if they're obvious spam). ] ] 04:40, 8 January 2025 (UTC)
:::I just counted and it looks like I've had 156 questions since February 2022. ] ] 04:56, 8 January 2025 (UTC)


==Discussion at ]==
As I understand it, this is the situation: {{u|Dekimasu}} has asked for a closer. The problem extends beyond Japanese, according to several other editors. The editor in question has promised to fix their work but to my (inexpert) eye their example of good work that they have done is nearly impenetrable. I myself am only involved to the extent that I clean up some different messes at ] but the ever-increasing backlog there doesn't need another prolific producer of automated translation, and the erroneous Chat GPT articles probably will just go straight into main space unnoticed if nothing is done. ] (]) 01:34, 14 March 2023 (UTC)
]&nbsp;You are invited to join the discussion at ]. –] <small>(])</small> 10:16, 7 January 2025 (UTC)<!-- ] -->


== Kansascitt1225 ban appeal ==
:{{done}}, I've closed the discussion. ] (]) 06:55, 15 March 2023 (UTC)


I am posting the following appeal on behalf of {{user21|Kansascitt1225}}, who is considered banned by the community per ]:
== Close needed ==
{{Resolved|Closed by Isabelle Belato and Ingenuity. ] ] 15:23, 16 March 2023 (UTC)}}
Hello. The big discussion ] has been open for a long time and there has been a request at ] for the discussion to be closed for almost a month. This discussion really needs to be closed. ]<sup>]</sup> 03:19, 14 March 2023 (UTC)
:I spent half an hour drawing up a closing rationale. Then I realised I'd opposed at the RfC so had to bin the whole lot. If anyone wants to take my notes, drop me a line. ] ] ] 18:17, 14 March 2023 (UTC)
::I've marked the RFC as doing. If you want to email me what you wrote down, {{u|Ritchie333}}, I'd appreciate it. ] <small><sup>]</sup></small> 18:52, 14 March 2023 (UTC)
:::{{re|Isabelle Belato}} thank you for having the courage to tackle this close! :) ]<sup>]</sup> 19:57, 14 March 2023 (UTC)
::::And, likewise, have the courage to subsequently watch the WMF override the entire discussion whichever way it falls, and impose it as an Office Action... 😄 ] 20:35, 14 March 2023 (UTC)
:::::🙃. ] <small><sup>]</sup></small> 21:15, 14 March 2023 (UTC)
:::::Perhaps not the WMF, but I guess we can keep this section open for a closure challenge. Independently of what the closure says. ] (]) 21:32, 14 March 2023 (UTC)
::::::I intend to challenge the closure regardless of what it says.{{jk}} ] <small>(])</small> 04:08, 15 March 2023 (UTC)
:::Thank you, Isabelle! ] (]) 16:19, 15 March 2023 (UTC)
::::{{ping|Isabelle Belato}} {{u|Ingenuity}} previously expressed interest in helping close this as well. Could you two work together on the close? Thanks! ] (]) 16:29, 15 March 2023 (UTC)


(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)
== User is adding unsourced information and reverting talk page messages in a purely disruptive manner ==


{{reflist-talk}} ] (]/]) 21:22, 7 January 2025 (UTC)
In opposition to ] and ] (as well as ]), {{Vandal|BrickMaster02}} has been adding unsourced information, reverting my edits, and removing . Note that in the particular page ('']''), there is an explicit third opinion to not add unsourced information, which he keeps on doing. ―]<span style="color:red">❤]☮]☺]☯</span> 22:40, 14 March 2023 (UTC)
* '''(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)
*'''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)
*: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)
*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)
*:{{tq|Is my maths just bad or is January 2019 not six years ago rather than five?}} ssssshhh. -- ] (]) 18:02, 8 January 2025 (UTC)


== Heritage Foundation ==
:I said that I would move it to another article, heck I would've even added reliable sources. But you reverted the edits, and blame me for doing it. Also, haven't you been banned indefinitely four times for disruptive editing, like you have? If you want me to add citations, I will, but don't go THIS FAR by adding me to a report when I didn't do much "vandalism". ] (]) 22:44, 14 March 2023 (UTC)
::"Also, haven't you been banned indefinitely four times for disruptive editing, like you have?" This doesn't make sense. Please don't add unsourced information to Misplaced Pages or remove talk post messages. ―]<span style="color:red">❤]☮]☺]☯</span> 22:51, 14 March 2023 (UTC)
:Note that he has also made a and falsely claimed that I "won't let him talk". ―]<span style="color:red">❤]☮]☺]☯</span> 22:46, 14 March 2023 (UTC)
::But you didn't. In case you didn't read my reply, which you seemingly didn't because you're spamming these threads, you said and I quote "Please do no add unsourced information to any article, particularly this one." Had you said something like "Can you explain why you reverted my edit?" or mentioned it on the article's talk page, this whole thing would've been over. ] (]) 22:49, 14 March 2023 (UTC)
:::I asked you on your talk page if you had read ] and ]. You removed the thread without responding. This is not a forum for you to litigate with me endlessly, so I'm not going to engage this. I hope the admins see your behavior here. ―]<span style="color:red">❤]☮]☺]☯</span> 22:52, 14 March 2023 (UTC)
::::I already reinstated your edits. If the admins do see this, then I deeply and sincerely apologize. And I absolutely mean it. I just wish we could've avoided the "drama" and I always ruin everything. No one likes me on this website, and whenever I try to make a useful contribution, I get verbally crucified. I know I have a lot to change about my behavior, and I doubt anyone will forgive me, but I want to let everyone know that I regret all of my actions on here. ] (]) 22:56, 14 March 2023 (UTC)


There is a discussion at ] that may be of interest to those who watch this noticeboard, especially if you edit in the PIA topic area. ] ] 04:12, 8 January 2025 (UTC)
== ]’s closing of a discussion ==


== Deleted contributions request ==
{{u|Jasper Deng}} recently closed ] as an non-admin, uninvolved closure. In the , Jasper Deng singled me out saying me stating a neutrally worded RfC was “inappropriate and disruptive”. Per ], the closing comment sure be neutrally worded. In the discussion, there was previously no mention of the discussion being disruptive or inappropriate. I then attempted to work the situation out on Jasper Deng’s talk page in ]. My request for the comment to be made more neutrally worded (with support from myself, the RfC starter on the closure) was met twice with no. Based on their , “{{tq|{{no ping|Elijahandskip}} In light of ], this is inappropriate and disruptive. At the least, this is the wrong forum; such a change would have to be projectwide and discussed at ]. We will not be using the NHC-made maps.}}”, I highly suspect this user should not have closed the discussion as they appear to be biased and refusing to stay neutral in their closing remarks. The comment sounds more like something you would see in a RfC comment, not a closing discussion remark. In closing discussions, one person should not be singled out under any condition, let alone being pinged in the closing remarks.
{{atop|Done and dusted. Good work all. - ] <sub>]</sub> 06:11, 8 January 2025 (UTC)}}
I'm currently leading an investigation at the English Wikibooks into poorly attributed page importations from the 2000s (decade). One page I discovered was ], which was allegedly imported from an enwiki page called ], but this page does not appear to have ever existed. It looks like this page was deleted at VFD in 2004, but there is no deletion log entry, so I can't find the original page to re-import to Wikibooks. Its talk page provides a page history for this enwiki article, which includes an anonymous editor whose IP address is {{IPvandal|62.200.132.17}}. If the privacy policy allows it, I would like to know the titles of the pages that this user edited in their three deleted contributions (I don't need the content, just the titles). ]<sub>]<sub>]</sub></sub> (]/]) 05:08, 8 January 2025 (UTC)


:{{ping|JJPMaster}} The only deleted contributions from that IP are to the deleted article you linked above and garden variety vandalism of a redirect saying that "this is junk". If you're looking for poorly attributed page importations, this specific IP would be a dead end on that front. ] ] 05:15, 8 January 2025 (UTC)
As such, I request the closure to be overturned and request a new person to close the discussion (As noted on Jasper Deng’s talk page, I support the closure of the discussion). Jasper Deng also appears to not have any idea about how to properly close discussions, so a potential warning or topic-ban from closing discussions should be considered until they can properly show that they understand how to stay neutral in closing discussions. ] (]) 01:22, 15 March 2023 (UTC)
::@]: Nope, that's actually all I needed to know&mdash;I really just needed this information to verify the page title. Could this page be undeleted in my userspace so I can complete the proper import and merge? ]<sub>]<sub>]</sub></sub> (]/]) 05:19, 8 January 2025 (UTC)
:::{{ping|JJPMaster}} Done at ]. I've never done something like this before so let me know if I messed up. I removed for VfD nomination template in case that screwed with bots or whatever. Let me know if there's anything else I can do to help. ] ] 05:27, 8 January 2025 (UTC)
::::@]: The import and merge are {{done}}. Please delete the page now. ]<sub>]<sub>]</sub></sub> (]/]) 05:30, 8 January 2025 (UTC)
:::::{{ping|JJPMaster}} I've deleted the page. ] ] 05:31, 8 January 2025 (UTC)
The reason you couldn't find it in the deletion log is because logs . This page was deleted ]. —] 06:36, 8 January 2025 (UTC)
{{abot}}


== ] behavior (or 'very' slow learner) from ] ==
*'''Important Extra Note''': Discussion was originally started at ], but was noted to have been placed at the wrong venue due to it involving an RfC. This is an exact copy/paste of the discussion starting message on that page, as directed by an admin. ] (]) 01:22, 15 March 2023 (UTC)
{{atop|result=Editor hasn't edited in a week, feel free to reopen should disruption continue if they return. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 03:09, 9 January 2025 (UTC)}}
*'''Comment'''. From what I can gather, this is a dispute among the members of the same project about an article within the scope of that project that implicates a possible ]-type conflict of consensuses where on one side there is the outcome the project-wide RfC (involving a template with a pre-collapsed portion of the caption), and on the other there are ] and ]. This should have been addressed in a dialogue about: (1) whether objectively there is a discrepancy; (2) how to resolve the ostensible discrepancy, probably within ]. Has there been a significant discussion about the appropriateness of collapsing? The underlying cause for this appearing on a noticeboard is how the RfC starter ]: "no consensus", "works fine", "no reason to change" (ignoring the stated reason). So maybe something needs to be done to help these editors move along, and ANI definitely didn't seem like the right environment for that. But I'm not sure if I'm correct on all the facts; I prefer not making any further comments in this discussion. —] 02:20, 15 March 2023 (UTC)
]'s talk page has got some history. It would seem they have a habit of AfCing articles on rappers and sports teams, failing them, and then making them anyway, such as with ] which is currently at ] and looks like it deserves a PROD. They've been repeatedly informed to include sources and citations but seem to fail to do so. But my ] allegation comes from at the AfD where they blanked the page, seemingly in an attempt to obstruct the AfD process. Does this behavior warrant administrator action beyond a stern talking-to? ] (]) 10:10, 8 January 2025 (UTC)
::Partially correct. The main reason I brought this to the noticeboard wasn’t more of the ] issue (as I didn’t even think of that at the time), but the improper closure of the RfC and borderline personal attacks through a non-neutrally worded closure. The ] is an issue, especially since it was used to justify closing the discussion pre-maturely. <em>The closing comment was more of an actually !vote rather than a closing comment.</em> That was why it was brought to the noticeboard. Somewhat a stem off of ], which was the justification for the closure. So I see two interlaced problems: the ] closure ideology and the use of the RfC closure as a way to “get back” at what the person calls a “disruptive” editor. ] (]) 02:34, 15 March 2023 (UTC)
:Sure, a long talk page, but not a single non-templated notice as far as I can tell (though I might have missed one). I think a kind word would suffice, at least to start out with. ] (]) 10:27, 8 January 2025 (UTC)
*This is getting out of hand. What do we need to do in order to curb these ongoing incidents? Is it now necessary, as {{u|Robert McClenon}} suggested, to declare that weather and tropical cyclones in particular are ]?--''']'''-''<small>(])</small>'' 12:31, 15 March 2023 (UTC)
::I generally concur, however, this user (a.k.a. ]) doesn't seem to be interested in talking to anyone about his actions. ] (]) 21:06, 8 January 2025 (UTC)
*:Some topics are ] because they have ] because they are regions of the world that have been historical battlegrounds where people have died. Tropical storms also tragically cause human deaths. Does that in turn mean that tropical storms are subjects of battleground editing? ] (]) 15:18, 15 March 2023 (UTC)
*::I don't think in this case it is because of people who have died, but for some reason the Wikiprojects around weather-related topics seem to have become a hotbed of ]ership, ] issues and off-wiki canvassing to an extent I haven't seen since ] in the ancient times. The latest big dust-up is at ] (I know you're aware of this, I'm more summarizing to give context for people who may not be). Contentious Topics, Discretionary Sanctions and General Sanctions are typically declared not because the topic itself is contentious, but because there are repeated user conduct disputes that the normal tools the community has are unable to break. The ], for example, hasn't killed anybody as far as I know but is still designated a Contentious Topic. While AE wouldn't be adept at dealing with off-wiki coordination due to the private nature of evidence, it might not be a bad idea for AE to get a crack at handling the conduct disputes. Perhaps it could be folded in with ] to cover "weather, storms and climate change" by motion in the same way that ] was created. Community-level General Sanctions could also be another option. Additionally, it might be a good idea to hold a Community-wide RFC to discuss CONLEVEL and the role of WikiProjects versus local talkpages in determining consensus, since it might need to be updated or clarified. <span style="font-family:Courier New;font-size:3">]</span><sup>]</sup> 16:29, 15 March 2023 (UTC)
*::::] - I was being sarcastic about the deaths. But, in my opinion, there are at least two classes of ]. There are those that are contentious because of ], because the subject matter is inherently contentious, and those that are contentious because one or more editors are just stubborn. And you know that I was aware of an ArbCom case in which I provided evidence. ] (]) 18:49, 15 March 2023 (UTC)
*:::::Exactly I saw that you had posted evidence on the case, so I made a note indicating that my summary was more for other editors who hadn't seen the history. And noted on the sarcasm, it can sometimes be hard to pick up on in a place like this. <span style="font-family:Courier New;font-size:3">]</span><sup>]</sup> 19:37, 15 March 2023 (UTC)
*:::Yes. ] (]) 18:49, 15 March 2023 (UTC)
*::::At the moment, the biggest problem with the Weather/Tropical Cyclone projects at is that we have just updated the general colour scheme, which is/was expected to cause a lot of disruption, as this is a big and major change that several people who use our maps don't like and want RV'd but were needed for us to meet Misplaced Pages's standards around accessibility criteria. I will note that during the various discussions surrounding the colours, an RFC was held that went over the in detail and noone brought up using the NHC maps. Probably because it creates problems around what maps to use in other basins, where we are not able to use maps from the RSMC/TCWC for various reasons, including them not being generated or being allowed on Misplaced Pages for copyright reasons.] (]) 20:03, 15 March 2023 (UTC)
*:::::That seems odd. Per the closing remarks in the RfC I started about NHC maps, Jasper Deng eluded to it already being discussed, saying “{{tq|We will not be using the NHC-made maps}}” while calling the discussion, “{{tq|innapropriate and disruptive}}”. But on the noticeboard discussion, you point blank just said it was never brought up? So what, ] and ] are legit major issued right now. Jasper Deng solely closed an RfC, speaking for the WikiProject as a whole, for a discussion that had not taken place before. That right there seems to be enough grounds to support a topic ban from closing discussions. Jasper Deng has edited Misplaced Pages for a long time (over 14 years), and clearly has an understanding of the rules and processes on Misplaced Pages. What is everyone’s thoughts on the topic-ban proposed? ] (]) 20:23, 15 March 2023 (UTC)
:::::::{{re|Elijahandskip}} My best advise for this whole issue, ]. - <span style="font-family:Trebuchet MS">] <small>(])</small></span> 20:50, 15 March 2023 (UTC)
:::::::{{ping|Elijahandskip}} I feel that you are overreacting here and trying to open Pandoras Box just for the sake of opening it here, as it almost certainly has been discussed somewhere on Wiki over the last 20 years, but I only looked at the Colour RFC, rather than the 50+ archives of WPTC/WPWX. If it hasn't its probably because its obvious that it would cause problems with what maps to use in other basins, where we are not able to use maps from the RSMC/TCWC/JTWC becasue they are not generated or allowed on Misplaced Pages because of copyright.] (]) 21:04, 15 March 2023 (UTC)
::::Definitely. I'm frustrated with the way WikiProject has become, and I think a community solution to handle this WikiProject (or making weather a contentious topic) is urgently needed to put a stop the drama that had consumed the WikiProject for some years, maybe ever since 2016-17. ] (]) 07:24, 16 March 2023 (UTC)


*I note the topic is already mentioned on ]. That should be enough to give the participants cause to think about what people in general think about their obsession. ] (]) 21:39, 15 March 2023 (UTC) Left a warning and note on his user talk page. Hopefully he engages. If such behavior continues, a block may be necessary to get his attention and drive the collaborative process. While I support such a block, it should ONLY be used to stop such disruptive behavior if it continues. Once that ceases and he's willing to collaboratively edit, such a block should be lifted post haste! ] (]) 21:12, 8 January 2025 (UTC)
{{abot}}
*:LOL. ] (]) 07:24, 16 March 2023 (UTC)


== Confusion about two articles that may be covering the same person ==
*'''Comment''' – I will say that it is ''highly'' embarrassing to have yet another noticeboard incident out of this Wikiproject, and it is sad that this project is quickly becoming known to many editors as one of the biggest problem areas across the whole encyclopedia. ] (]) 22:40, 15 March 2023 (UTC)
*:It's making weather-interested users to look bad by this point. ] (]) 07:24, 16 March 2023 (UTC)


The pages are ] and ]. Can an administrator please find the correct name and merge them, if they are the same person? ] (]) 22:14, 8 January 2025 (UTC)
== Block review: WikiWikiWayne ==

{{atop|Block endorsed as lenient, closing this before WikiWikiWayne manages to talk their way into a longer block. <sub>signed, </sub>] <sup>]</sup> 00:57, 17 March 2023 (UTC)}}
:Are they the same person? The date of birth (for ]) is the same in the text (without a source here), but in the infobox (added by an IP without a source: ]) it's different... <s>Honestly, I feel it would be easier to just give up on this one,</s> it was created by a sock-puppeteer (albeit on their original account, though they edited it with multiple socks too, seemingly all reverted), <s>it's quite possibly a waste of time.</s>
{{userlinks|WikiWikiWayne}}
:That said I didn't actually investigate what is salvageable about the content - just reverted the last 2 edits by an IP. &ndash; ] (]) (]) 22:45, 8 January 2025 (UTC) *edited: 05:10, 9 January 2025 (UTC)
I blocked WikiWikiWayne for 48 hours yesterday for a 3RR violation on ]. I was pinged to offer a third opinion on a dispute that had broken out there, which I did. WWW did not engage in the discussion after an initial reply. When he reinstated his contested change a third time, I left him a and he stopped editing. I assumed that was the end of the matter but a little over an hour later he reverted again (without commenting on WT:Drafts or his talk page), his fourth revert in about two and a half hours, so I blocked him. WWW has indicated that he doesn't trust the {{tl|unblock}} process but is accusing me of bullying him. I don't think further one-to-one discussion is going to get either of us to see the other's side, so I think it's best if I hand it off and open a community review. ] &#124; ] 12:00, 15 March 2023 (UTC)
::], this seems like a valid inquiry, why would it be considered a "waste of time"? I don't know what you mean by "giving up on this one" when it's a matter of investigating whether we have a duplicate article here. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 02:23, 9 January 2025 (UTC)
:I just revoked TPA because of the user's latest screed. My revocation was simultaneous with the opening of this thead. As an aside, I endorse HJ's block.--] (]) 12:07, 15 March 2023 (UTC)
::@] - WWW is lucky you didn't also extend the block for that tantrum. Yeesh ] ] 13:15, 15 March 2023 (UTC) ::I'm not sure why you seem to be attempting to discourage people looking into this. Seems like something that would be both possible, and important, to do. Or at the very least, attempt. ] ] 02:58, 9 January 2025 (UTC)
:::Fair enough, I shouldn't be discouraging. I was thinking this might be a ] kind of situation (for the second linked article), due to the amount of socking and unsourced edits, and the article already existing if it's the same person, as opposed to merging them - but you are both right that it's always worth checking.
:::Sometimes post-block conduct can trigger an extension of the block, e.g., if the user is blocked for personal attacks and continues to make them after the block, but in the case of hissy fits and attacks against the blocking admin, I think revocation of TPA is sufficient. That said, if the user doesn't move on after their block expires, a longer block should be considered.--] (]) 13:21, 15 March 2023 (UTC)
:::I'll just cross out that part of the comment. &ndash; ] (]) (]) 05:09, 9 January 2025 (UTC)
::::I suppose you're right @]! I do think the editor knew that the talk page comments were too much and would likely draw more scrutiny, not sure why they did that though. ] (]) 13:24, 15 March 2023 (UTC)
:I don't think this is an admin thing, it's a content issue; shouldn't it be discussed on one of the talk pages, possibly with a ], instead of here? ]] 08:55, 9 January 2025 (UTC)
:::::For what it's worth, I'm not fazed by the comments directed at me and I don't think extending the block would be helpful or necessary. Long-term editors are often upset at being blocked. It's one of the reasons we prefer discussion and warnings first. I'm surprised at how badly WWW responded to a short block for a clear 3RR violation but it's human to get upset and lash out. We shouldn't hold it against someone. ] &#124; ] 16:39, 15 March 2023 (UTC)

:Good, lenient block. Have a feeling it will get longer, unfortunately. <span style="font-family:Calibri; font-weight:bold;">] ]</span> 12:26, 15 March 2023 (UTC)
== Non-EC editor editing ARBPIA, broadly construed. ==
::Hi SM. Well, that crystal ball was fogged up. The three of us stopped reverting my single small edit before the block. The block prevented no harm to the ] essay. Also, 24 hours or less is the guideline for a first time 3RR block. And, I had 2 net reverts, but I'm not going to bloviate in this spot about the details. Thanks. No biggie. Take care. Cheers! <code>&#123;&#123;u&#124;]&#125;&#125;&nbsp;{]}</code> 00:05, 17 March 2023 (UTC)

:An editor is not entitled to three reverts. The prohibition is against ''edit warring'', and a fourth revert is considered prima facie evidence of edit warring, not the beginning of it. Which is to say, "good block", and that I have little sympathy for someone who tries to get unblocked from edit warring by counting reverts and accusing the blocking admin of bullying. ] (]) 12:45, 15 March 2023 (UTC)
This is intended as a "heads-up", asking for admin eyes, and letting admins know what I have done. I noticed edits by {{userlinks|OnuJones}} to ] and ], removing mentions of Palestine or changing Palestine to Israel. I have undone the edits. I have placed welcome/warning templates on their usertalk page, as advised when I asked recently on AN about a similar situation. The account in question was created on 4 December 2020, made two edits on that day, and then nothing until the three edits on the 7th January this year that caught my eye. I shall forthwith add <nowiki>{{subst:AN-notice}}~~~~</nowiki> to their usertalk page. ] (]) 23:41, 8 January 2025 (UTC)
::Courcelles. Yes, you're right. 3RR, if counted correctly, is a bright line breach. Any warring is actionable or scrutable. Fortunately, in this case, the three of us were reverting in good faith (or inadvertently), and we were discussing when available. Take care. Thanks. Cheers! <code>&#123;&#123;u&#124;]&#125;&#125;&nbsp;{]}</code> 00:10, 17 March 2023 (UTC)

:Please forgive this editor. This is so incredibly, incredibly, sad. —] 12:56, 15 March 2023 (UTC)
::The editor accused the blocking admin of misconduct after clearly violating 3RR, forgiveness isn't necessary and this isn't a place to discuss forgiveness. ] (]) 12:57, 15 March 2023 (UTC) :I don't think this really needs admin attention. Your CTOP notice suffices. If they continue making those kinds of edits, you can go to AE or ANI. ] (]/]) 23:47, 8 January 2025 (UTC)
::I might have to reread the ARBPIA restrictions because these two edits are about incidents around World War I. I'm not sure they are covered by ARBPIA restrictions which I tend to remember are about contemporary events. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 02:19, 9 January 2025 (UTC)
:I'm not an admin but I had watched this whole thing play out and agree that the editor certainly deserved a block for violating 3RR. I think the block should be upheld, and arguably extended due to the comments they made on their talk page. ] (]) 12:59, 15 March 2023 (UTC)
:::I think the concern is that while the ''articles'' aren't ARBPIA per se, the ''edits'' ({{tqq|changing Palestine to Israel}} ) are clearly ARBPIA-motivated, as it were. (Even leaving aside the historical inaccuracy in that Israel didn't exist at the time!) - ] <sub>]</sub> 03:16, 9 January 2025 (UTC)
::There was no 3RR or warring by any of us 3 reverting editors. This block never should have happened, but that's water under the bridge. Things moved very quickly, and you could not possibly have seen the whole thing, as I did not, and HP did not, plus there is a lot of IRC chatter in these blocking matters. Nobody has the whole picture. No worries. Take care. Cheers! <code>&#123;&#123;u&#124;]&#125;&#125;&nbsp;{]}</code> 00:55, 17 March 2023 (UTC)
:Good block. Perhaps too lenient if anything. ] ] 13:11, 15 March 2023 (UTC) ::::I would consider the edits to be within the realm of ] ]. '']''<sup>]</sup> 03:41, 9 January 2025 (UTC)
:::::Those kinds of transparently false Palestine to Israel or Israel to Palestine edits should result in a block without warning and without any red tape in my view. They know what they are doing. People who edit in the topic area shouldn't have to waste their time on these obvious ] accounts. ] (]) 03:56, 9 January 2025 (UTC)
::EvergreenFir. Do I rub you wrong, or do most of your replies all over to everybody assume bad faith, and expanded punishment? I'm asking. Sincerely. I don't follow you, so I don't know. I will listen.
:::I guess I didn't make my meaning all that clear. Editors should not post to AN every time they warn a brand new account about a CTOP. It's a waste of everyone's time. ] (]/]) 15:29, 9 January 2025 (UTC)
::But, every time you comment in my vicinity its veiled bitterness, and I feel picked on. Let me know if that's just your norm, so I won't mistake it for a personal targeted bias against me. Words hurt. But, maybe I am misunderstanding.
::When the admin guideline is 24 or less if guilty, why do you feel 48 was lenient? Thanks. Take care. <code>&#123;&#123;u&#124;]&#125;&#125;&nbsp;{]}</code> 00:49, 17 March 2023 (UTC) ::::{{re|Voorts}} It's not a brand new account, but presumably you didn't waste any of your time by actually reading my post. ] (]) 18:47, 9 January 2025 (UTC)
:::::I misstated that this was a new account, but an account with five edits that hasn't edited since before you warned them isn't really something that needs an AN thread. I apologize for my tone. ] (]/]) 19:25, 9 January 2025 (UTC)
:Huh. ] ] would be the last place I'd go to in order to appeal or critique an admin decision. I think the block was a good one, and per {{noping|Bbb23}}, is an appropriate amount since occasional blocklash is to be expected. I sympathize with Alalch's desires for... sympathy. But a line on improper conduct needs to be drawn somewhere. --''']'''-''<small>(])</small>'' 13:26, 15 March 2023 (UTC)

::Hey, thanks. Yes, Fisking format with all caps as the speaker delimiter. All caps is a very old school Fisk reply delimiter (circa 1994), but it came across as shouting, which I did not intend. Sorry. I went back to edit to sentence case, but my talk page, and everywhere was locked down. When I get home, I'll sentence case it, and remove any other unintended inferences. Give me a few hours. Thanks. Cheers! <code>&#123;&#123;u&#124;]&#125;&#125;&nbsp;{]}</code> 23:38, 16 March 2023 (UTC)
== Hide this racist edit. ==
*Because of an e-mail WWW sent me (they have been e-mailing others as well), I have disabled e-mail access.--] (]) 13:52, 15 March 2023 (UTC)

*:'''*sigh*''' I had hoped this could resolved by just waiting out the block but I anticipate that they won't be too cordial after their block expires. ] (]) 13:55, 15 March 2023 (UTC)
{{atop|Different project, nothing for en.wikipedia.org admins to do. OP was pointed in the right direction. --] (]) 11:27, 9 January 2025 (UTC)}}
*::Philipnelson99. I play off my audience. Take care. Cheers. <code>&#123;&#123;u&#124;]&#125;&#125;&nbsp;{]}</code> 00:39, 17 March 2023 (UTC)
Hide the racist edit summary. It says bad words and it is stereotyping Romani people.
*:Hi, no worries. You blocked me from all communication avenues on the Wiki. Our instructions are to email the blocking admin since we can't use other means. I sent a fairly flaccid email to HP Mitchell about his block requesting an unblock. He did not reply by email. My email to you got no reply either. It just got me locked down. I only asked you to open me up to reply here at AN, if I recall correctly, plus a quick timeline and some facts. The emails were per that instruction. I mentioned that when I emailed you. Take care. Cheers! <code>&#123;&#123;u&#124;]&#125;&#125;&nbsp;{]}</code> 23:46, 16 March 2023 (UTC)

*Good block, support talk page access removal. As an aside, I know it's ''de rigueur'' to throw around the terms "bullying" and "gaslighting" these days, but I find it's most often used flippantly on Misplaced Pages whenever an editor is told something they don't want to hear. Such baseless accusations of bullying take away from the real instances where individuals really do need support. If you're crying "bully!" when you're correctly criticised for your edits, you really really don't know what the word means. -- ]<sup>]</sup> 15:55, 15 March 2023 (UTC)
https://rmy.wikipedia.org/Uzalutno:Contribuții/178.115.130.246 ] (]) 08:52, 9 January 2025 (UTC)
*:I think I said I felt bullied, as my block did not comport with the admin block guidelines for first offenders. I will defend my two net reverts elsewhere. Take care. Cheers! <code>&#123;&#123;u&#124;]&#125;&#125;&nbsp;{]}</code> 23:49, 16 March 2023 (UTC)

*Very clearly a good block: ] is a ''bright line'' policy and WWW indisputably stepped over it. It's a clear violation of the rule, although the policy is also clear that the bright line need not be crossed for an editor to be blocked for edit warring. Also, in their third revert at 16:14 they inserted "please stop edit warring while we are discussing" into the article instead of into the edit summary, which they admitted on their talk page was a mouse-click error, but in their next revert at 17:22 they restored that text again. That's a good indication to me that they weren't bothering to look at the text they were reverting, they were just hammering the undo button to prevent anyone else making any change. I can accept that that was a heat-of-the-moment mistake, but it's exactly the sort of mistake that we have 3RR to deter. Good block; I might not have made the block longer after the talk page outburst, but I absolutely would have when they still kept carrying on by email. ] (<sup>]</sup>/<sub>]</sub>) 16:24, 15 March 2023 (UTC)
:That's on the Romani Misplaced Pages, we only deal with the English one here. You'll need to raise that with the admins on that project. ]] 08:57, 9 January 2025 (UTC)
*:Greetings. I only had two net reverts, but I won't bludgeon you about the details. There were 3 reverting editors, and we were working it out, or making reparations before the block. It looked uglier than it was. Whoop, whoop! Take care. Cheers. <code>&#123;&#123;u&#124;]&#125;&#125;&nbsp;{]}</code> 23:53, 16 March 2023 (UTC)
:Please refer to ], if there are no active RMYWP admins available. ] (]) 11:26, 9 January 2025 (UTC)
*A couple of things. WikiWikiWayne is the editor formerly known as {{u|Checkingfax}}, who I think {{u|Cullen328}} knows in real life, and recognises him as a well-meaning editor who is occasionally disruptive by over-enthusiasm. The most obvious question I have is '''why was WWW not partially blocked from ] instead of the entire site'''? If there's evidence that we suspected WWW was highly likely to disrupt ''other'' pages, then fine, but I can't obviously see that from their contributions. {{u|Alalch E.}} appeared to be edit-warring just as much on that page as WWW, at first glance, but I'll give them the benefit of the doubt that they were simply reverting to ''established'' consensus while discussing the issue.
:As things currently stand, I think the block and TP removal should stand as WWW clearly needs to calm down a bit before attempting to edit again; I just think with a bit more tact and diplomacy (plus a use of the tool designed to stop the problems a site block can give us) we could have managed things a bit better and maybe avoided the meltdown a bit. ] ] ] 17:04, 15 March 2023 (UTC)
::I was not aware until now that these two accounts are the same person, but yes, I know this person in real life and {{u|Ritchie333}}'s description is accurate. Wayne has been kind to me and my familily. Accordingly, I will not say anything more about this specific situation except to say that it saddens me. I do endorse Ritchie's recommendation that judicious use of page blocks is often a better solution than site blocks, especially when dealing with a long term productive editor. ] (]) 17:22, 15 March 2023 (UTC)
:::When someone blasts straight through 3RR like that, without participating in an ongoing discussion and after a very clear warning, it is suggestive to me of a broader problem that a partial block would only displace. And judging by the reaction to the block, my guess is we'd be discussing a partial block in at least five different venues until it was eventually converted to a full block, probably for a lot more than 48 hours, and we'd be no closer to reaching a conclusion at WT:Drafts. ] &#124; ] 19:05, 15 March 2023 (UTC)
::::HP Mitchell. I bristle when you say the three reverting editors did not discuss this. We did. Others did too. I have told you about the discussions. Old tapes are toxic here. The 3 of us were working it out, raggedly, but we were circling around to a conclusion when you threw gasoline on things with:
::::*Unseen warning
::::*Double-sized block (48 vs 24 or less)
::::*Not replying to my email
::::*Missing both ANIs
::::*Starting this AN
::::*Flipping out over a small fix on an Essay
::::*Letting others lockdown all my communication and damage control avenues
::::That being said, you had some softness and suggestions here and there and I acknowledge and truly appreciate it. And, if I had seen your buried warning... Take care. Peace. Cheers! <code>&#123;&#123;u&#124;]&#125;&#125;&nbsp;{]}</code> 00:37, 17 March 2023 (UTC)
:::: * <code>&#123;&#123;u&#124;]&#125;&#125;&nbsp;{]}</code> 00:37, 17 March 2023 (UTC)
::Hey, I could nitpick some details, but your reply is super on spot, and thoughtful. More later. Take care. Thanks. Cheers! <code>&#123;&#123;u&#124;]&#125;&#125;&nbsp;{]}</code> 23:56, 16 March 2023 (UTC)
*'''Endorse good, lenient block and subsequent actions to stop disruption'' We can only hope {{ping|WikiWikiWayne}} calms down and learns from this experience, though I doubt he does. Most of the edit warriors I've seen feel justified in their actions and are not amenable to reason.] (]) 21:16, 15 March 2023 (UTC)
*:Deepfriedokra. It was not intended to be as ugly as it looks. As for lenient, no, I got 48, and the guideline is 24 or less for a first-timer. I'm not going to die on this hill or cry over spilled milk, so no worries. A lot of mistakes were made, by everybody, but in good faith. The reverts and fixes were done before the block. Also, I recall in my revert edit summary that I suggested that the words be changed, and not reverted. I had 2 net reverts, maybe 7 total between the three of us that were involved, but we were discussing it, as were others, HP just missed it, as he missed the ANIs, and he was an editor on the Essay. None of us meant to war. There's more. Not gonna bore you. Yup. Take care. Cheers! <code>&#123;&#123;u&#124;]&#125;&#125;&nbsp;{]}</code> 00:24, 17 March 2023 (UTC)
{{abot}} {{abot}}


== Admin prohibits to delete copyright links ==
== Wikimania 2023 Welcoming Program Submissions ==
{{Atop|This has nothing to do with the English Misplaced Pages.--] (]) 14:57, 9 January 2025 (UTC)}}

In the following topic: Admin refuses to delete the following links that violate Copyright policies (links to pirated websites):


*
]
*


Refers to "Community discussion", when the latest discussion about the page contents happened on 2008 and simple google is available to see which links are pirated and which are not. ] (]) 14:56, 9 January 2025 (UTC)
<section begin="wikimania-program-submissions"/>]Do you want to host an in-person or virtual session at Wikimania 2023? Maybe a hands-on workshop, a lively discussion, a fun performance, a catchy poster, or a memorable lightning talk? ]. The event will have dedicated hybrid blocks, so virtual submissions and pre-recorded content are also welcome. If you have any questions, please join us at an upcoming conversation on March 12 or 19, or reach out by email at wikimania@wikimedia.org or on Telegram. More information on-wiki.<section end="wikimania-program-submissions"/>
{{Abot}}
<!-- Message sent by User:CKoerner (WMF)@metawiki using the list at https://meta.wikimedia.org/search/?title=Distribution_list/Global_message_delivery&oldid=24390465 --><!-- Template:Unsigned --><small class="autosigned">—&nbsp;Preceding ] comment added by ] (] • ]) 15:44, 13 March 2023 (UTC)</small>


== 96.230.143.43 ==
== Bruno Rene Vargas – topic ban violation ==


This user is a frequent vandal on the page ]. I am requesting a block. ] (]) 16:34, 9 January 2025 (UTC)
{{Ping|Bruno Rene Vargas}} is topic banned from moving pages. {{Ping|Dreamy Jazz}} and {{Ping|Cullen328}} have previously blocked him for violations as articulated ] and ]. He has again breached the spirit of the block. ] was created by an IP editor on the 14th, and a couple of hours later, (he has recently returned to Misplaced Pages and has been getting older deleted draftworks restored despite if they were earlier recreated by someone else). His time away has not prompted a change in his edit behaviors. ] 20:43, 15 March 2023 (UTC)
:Well, hopefully they give me a permanent and indefinite blockade just like in the Spanish Misplaced Pages. I'm tired of trying to contribute here and then being persecuted by users like you who know how to point out other people's mistakes but can't recognize their own. I retired for two years, I tried to start editing here again but I see that this will never change. Now if I withdraw permanently and I myself ask for my definitive block, thank you very much. ] ] 20:49, 15 March 2023 (UTC)
::I don't wish to have to keep having conflict here, but the persistent editing tactics you have been previously been blocked over makes it hard to. You left for a period of time, yes, but you essentially just kept doing what was the cause of many an editors frustrations. We wouldn't be here if that stopped but it unfortunately has not. ] 20:53, 15 March 2023 (UTC)
:::Well, the one who requested that editions that contributed little or nothing to the draft that I create years ago be recovered was you, and you did that only so that I also did not appear as the creator of the article just because you were not satisfied with the decision that I take the administrator. In addition, you are the one who spends time looking at my edition history and looking for the slightest error on my part to come and report it. But now I don't care exactly about the decision that is made here, I myself ask again that they block me permanently so as not to return even from here at a time in case I want to return. I, Bruno Rene Vargas, request my permanent block on the day of the date. ] ] 21:03, 15 March 2023 (UTC)
::::This thread is about the Untitled Quentin Tarantino film draft edits. ] 21:05, 15 March 2023 (UTC)
:::::What do you think about this 🖕🏽? ] ] 21:08, 15 March 2023 (UTC)
::::::Don't you two have some sort of interaction ban? You've been at each other at ANI and elsewhere for so many years i can't believe that's not in place. ] (]) 21:11, 15 March 2023 (UTC)
:::::::One was discussed but never came to fruition. I think he had either left the site for a period of time or the matter died down. ] 21:20, 15 March 2023 (UTC)
* Without looking into the topic ban itself, I've blocked Bruno Rene Vargas for 48 hours for the above comment. ] <small><sup>]</sup></small> 21:14, 15 March 2023 (UTC)
*:@] See the ] ] (]) 22:47, 15 March 2023 (UTC)
*I would have been willing to remind Bruno Rene Vargas that he has a topic ban and that he must not violate it moving forward. A simple, "oh, OK," might have sufficed. However, the explosively inappropriate response here leaves me cold. Perhaps extending the block to one week as a firmer reminder of the topic ban and of the conduct issues is needed. The IBAN between Rusted AutoParts and Vargas is needed as well. Assuming Vargas does not wind up indeffed.] (]) 01:41, 16 March 2023 (UTC)
*:It looks like per this users page, ] has permanently retired. I’m assuming a heat of the moment retirement. ] (]) 09:51, 16 March 2023 (UTC)
*::<s>Well, we may as well just unblock him and get on with our day.</s> Yes, retirement after a sanction is most often regarded as an effort to avoid further sanctions by making other users think that the disruption has stopped for good. However, Wiki-retirement is not binding in any sense, and some editors will claim to be "fully retired" while still participating in discussions or article editing. In this case, it's likely an off-shoot of ].--''']'''-''<small>(])</small>'' 12:08, 16 March 2023 (UTC)
*:::I have to fully agree. Perhaps an indef block as a going away present? When they are willing to participate in a civil manner, we could consider unblocking. ] (]) 16:10, 16 March 2023 (UTC)
*I've made it an indef block, rationale (and path to lifting it) explained on the user's talk page. ] (]) 17:55, 16 March 2023 (UTC)


:Blocked. In the future, please use ]. <b>]</b><sup>]</sup>/<sub>]</sub> 16:37, 9 January 2025 (UTC)
== ] ==
::Ah, very sorry. ] (]) 17:39, 9 January 2025 (UTC)


== StoneX Group Inc. ==
The ] passed away last year and I don't know where else to take this. Is there a reason this IP is blocked indefinitely? I thought it was standard practice not to block IP addresses forever. ] (]) 02:35, 16 March 2023 (UTC)
:Standard practice has evolved over the years. I've lifted the block. Honestly, I don't expect it to last that way for very long, but hopefully the next one won't be indef. -- ] <sup>]</sup> 02:49, 16 March 2023 (UTC)
::Why is it that so much vandalism comes from schools? ] (]) 03:12, 16 March 2023 (UTC)
:::A lot of people with a lot of time. ] (]) 07:25, 16 March 2023 (UTC)
::::And students are paired 1 to 1 with devices and use Google (which feeds to enwp) to look up stuff. Pair that with teachers being very overwhelmed and not able to monitor everything students do on those devices, and what we get is sort of inevitable. ] (]) 14:29, 16 March 2023 (UTC)
:::::I usually like to put it down as "a bored schoolkid", altho school IPs don't only vandalize, it's just that usually they do because you can have thousands of kids on 1 IP (or 1 range of IPs). ― ]]<sub title="Discord Username" style="margin-left:-22q;">Blaze&nbsp;Wolf#6545</sub> 14:39, 16 March 2023 (UTC)
::::::I'm actually a teacher, so have experienced daily the struggle of keeping children on task and not doing... other things. I often fail at this goal... ] (]) 18:07, 16 March 2023 (UTC)
:::::On another note, I've added the Shared IP template to the talk page. You'd think that by the time they get to college they would stop vandalizing Misplaced Pages. Guess not. ― ]]<sub title="Discord Username" style="margin-left:-22q;">Blaze&nbsp;Wolf#6545</sub> 14:45, 16 March 2023 (UTC)
::::::The problem is every year, a fresh batch of bored people go into the computer lab and experiment. ] (]) 18:05, 16 March 2023 (UTC)
:::::::{{yo|Courcelles}} I know what you mean. Even in adult classes for work, the mind sometimes wanders. Boredom sets in . . . . ] (]) 18:13, 16 March 2023 (UTC)
::::::::Other things are fine. We all need "brain breaks". We just want those not to be destructive to other's property or peace. Either in the physical classroom or cyberspace. ] (]) 18:22, 16 March 2023 (UTC)
::::::::We will never be free of this. — <span style="letter-spacing:-1pt;font-family:'Rockwell', serif;">''']™'''</span> 18:19, 10789 September 1993 (UTC)


I’m concerned about the page at ]
== Topic-banned ==
{{userlinks|Товболатов}}


There are disclosed COI paid edits but the main problem I’m highlighting here is that the subject company appears to see that they have ownership of the page to the extent of adding obviously inappropriate stuff, see my most recent edit to remove it. I’m not sure of the correct procedure and was wondering if an admin could possibly have a polite word with those editors? Thanks. ] (]) 17:06, 9 January 2025 (UTC)
Hello, my violation of ] in several articles, especially this Feb 16th edit (], ], ], ], ], ], ], ]) ]. I did not know. In the future, I promise not to do this and not break the rules. Please reconsider the topic limit. ] (]) 14:22, 16 March 2023 (UTC)


== Permissions Removal ==
:@] Tagging you as you are the admin who placed the restriction. ~ '']''<sup>(]&#124;])</sup><small>]</small> 15:08, 16 March 2023 (UTC)
::I have a few concerns here. One is that I stand by my prior assessment that copy-pasting the same block of contentious text across half a dozen articles as part of a prior dispute with another editor is clearly tendentious editing, to such a degree that simply saying that they didn't know it wasn't OK stretches the boundaries of AGF, especially as it came after days of informal warnings for a variety of different bad behaviors (see ] among other archived discussions). I further have a concern that Товболатов's English skills may not be sufficient to contribute to contentious topic areas, as their participation thus far (up to and including this request) shows clear signs of relying on machine translation to participate here, and has led to significant communication difficulties in resolving discussions with other editors. Meanwhile, their editing history to other topics since the ban is practically non-existent, giving the impression that their intent is to continue to be a ] in a contentious topic area, rather than to build an encyclopedia. Finally, there is also an unresolved ] where a CU has found some evidence of sockpuppetry but it has yet to be closed. <sub>signed, </sub>] <sup>]</sup> 15:23, 16 March 2023 (UTC)


*'''Endorse and maintain Topic Ban'''. I see no indication the TBAN is no longer needed.] (]) 18:09, 16 March 2023 (UTC) Hello, please remove my rollback and pending changes review permissions. Rollback is redundant because I have global rollback and I do not use the reviewer rights enough to warrant keeping them. Thank you! ] (]) 20:03, 9 January 2025 (UTC)


:Done. Thank you. —&nbsp;]&nbsp;] 20:08, 9 January 2025 (UTC)
**Thanks for the reply, I don't want to edit in contentious topics. ] It's not me. --] (]) 18:34, 16 March 2023 (UTC)
Well, I understand, but I will say one thing if I had a goal to argue, I would not create a doll. And I would have done as they do, changed the ip-address and provider and continued to edit. A new participant cannot immediately rule well on controversial topics. But I won't do this. ]. I'm sorry, but I couldn't resist saying this.--] (]) 20:00, 16 March 2023 (UTC)

Latest revision as of 20:08, 9 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
    Welcome — post issues of interest to administrators. Shortcuts

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

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

    Sections inactive for over seven days are archived by Lowercase sigmabot III.(archivessearch)

    Start a new discussion

    Open tasks

    Centralized discussion
    Noticeboard archives
    Administrators' (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)
    1156 1157 1158 1159 1160 1161 1162 1163 1164 1165
    1166 1167 1168 1169 1170 1171 1172 1173 1174 1175
    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
    XFD backlog
    V Oct Nov Dec Jan Total
    CfD 0 0 22 20 42
    TfD 0 0 0 1 1
    MfD 0 0 0 0 0
    FfD 0 0 7 5 12
    RfD 0 0 39 10 49
    AfD 0 0 0 0 0


    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:

      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.

      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)
    • 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)
    • 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)
    • 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)
      See . Extraordinary Writ (talk) 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. ♠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 to make constructive content would indicate that the 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)
      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 on mass-creating non-notable stubs. BeanieFan11 (talk) 21:18, 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)

    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)
    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)

    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)

    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)

    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)
    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)
    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)
    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)

    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)
    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)
    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 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. @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)
    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)
    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)
    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)
    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 stated 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. Aviationwikiflight (talk) 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. - 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)

    Request removal of PMR/Rollback

    Flags removed JJPMaster (she/they) 22:52, 2 January 2025 (UTC)

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


    Hi, lately, I haven't been using my page-mover and rollback rights that often and I don't feel returning to the activity anytime soon. Can any admin remove these flags from my account. I relatively happen to support in file-renaming areas these days and have also decided to put in some efforts in this month's NPP backlog. So these rights should stay. Thank you. Regards, Aafi 10:19, 2 January 2025 (UTC)

     Done. Primefac (talk) 10:25, 2 January 2025 (UTC)
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Insults, personal attacks and reverts of academic material

    This appears to be done. - The Bushranger One ping only 05:51, 7 January 2025 (UTC)

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


    After reverting multiple edits that included references to peer-reviewed papers in academic journals, @FMSky posted the following on the Naomi Seibt talk page: "Put your trash analyses in the appropriate section(s) and stop flooding the lead with citations.". 62.74.35.238 (talk) 12:05, 2 January 2025 (UTC)

    Yes, why haven't you done that? --FMSky (talk) 12:07, 2 January 2025 (UTC)
    Article in question is a contentious topic x3. The initial reverts of the IP's edits were for WP:LEADFOLLOWSBODY, since the IP included all the material in question in the lead with no mention in the body of the article. Does FMSky need trouted for using the term "trash analyses"? Maybe. However, the IP's actions lean into the WP:ACCUSATIONOFMALICE category, and that may call for either direct sanctions against the anonymous editor or protection/sanctions on the article in question. —C.Fred (talk) 12:09, 2 January 2025 (UTC)
    Does FMSky need trouted for using the term "trash analyses"? How else would you describe the IPs additon of "In May 2020, she reiterated her dismissal of investigative evidence by endorsing" --FMSky (talk) 12:11, 2 January 2025 (UTC)
    You deleted all academic sources that claim that she is far-right, including other sources that have nothing to do with WP:ACCUSATIONOFMALICE. 62.74.35.238 (talk) 12:14, 2 January 2025 (UTC)
    Which also indicates that you were more focused on reverting information you don't agree with, without first discussing it in the talk page. 62.74.35.238 (talk) 12:15, 2 January 2025 (UTC)
    Edit: also doubled down. 62.74.35.238 (talk) 12:15, 2 January 2025 (UTC)
    Put your new content into the body of the article instead of the lead. The lead is a summary of the body --FMSky (talk) 12:16, 2 January 2025 (UTC)
    Done. Now it’s a summary. 62.74.35.238 (talk) 12:20, 2 January 2025 (UTC)
    User continues to stuff the lead with info not found anywhere else 1. A block or article lock would be appreciated --FMSky (talk) 12:24, 2 January 2025 (UTC)
    I will proceed with covering the whole lead in the rest of the page. Give me an hour or two. 80.149.170.8 (talk) 13:20, 2 January 2025 (UTC)
    Start with the body. Do the lede last. And work at article talk to make sure you have consensus before making major changes, especially to the lede. Simonm223 (talk) 13:22, 2 January 2025 (UTC)
    The IP has come up with a more than sufficient number of reliable sources to back up the far right assertions (etc). However, the lead is not the place to stuff them: they should be in the body, and the lead should reflect that content. Esowteric + Talk + Breadcrumbs 14:25, 2 January 2025 (UTC)
    • Not only is there a pattern of IP editors inserting large chunks of information to the intro about her right-wing ties, but I also see this edit from 21 December that seemed to be at the start of the pattern, and that's from now-blocked user FederalElection (talk · contribs · deleted contribs · logs · filter log · block user · block log). At the least, that's a mitigating factor to excuse FMSky's heavy-handed reaction to these latest edits. At the most, it's grounds to revert the addition until a (new, civil, content-related) discussion at the talk page generates consensus to include it and/or protect the page—and that protection might need logged as CTOP enforcement. —C.Fred (talk) 12:23, 2 January 2025 (UTC)
      You are consistently reverting edits that can be fully backed by reliable peer reviewed articles. You are refusing to acknowledge the scholarly literature. If any of you wanted to politely contribute to the article, you would not remove such sources. It’s not just the “chunk of information”, as you like to refer to it, but the constant removal of content you personally don’t agree with. Asking for the article to be locked is an effort to block others to edit, when the information provided is reliable. The bias extends to your plea to excuse FMSky’s insults. 62.74.35.238 (talk) 12:27, 2 January 2025 (UTC)
      IP - from what FMSky is saying above it looks like the issue is that you're attempting to put material in the lede which is not elaborated upon within the body of the article. This is a manual of style issue. Maybe consider working at article talk to find an appropriate place within the article for your sources. Simonm223 (talk) 13:13, 2 January 2025 (UTC)
      Tread lightly, IP. Trying to link policy-based edits to personal bias is wading back into WP:ACCUSATIONOFMALICE. You will need to present strong evidence to back such accusations up. —C.Fred (talk) 13:16, 2 January 2025 (UTC)
      I'll add that WP:BLPRESTORE requires consensus before restoring material removed "on good-faith BLP objections". Even if the information was in the body, wp:undue concerns arise with pretty much anything added to the lead. So if an editor feels material doesn't belong in the lead of a BLP, it's entirely reasonable to ask for there to be consensus before it's added back. Nil Einne (talk) 09:50, 4 January 2025 (UTC)

    I think everything's been said that needs to be said here. As long as 62.74.35.238 now complies with the request to add the content to the body of the article before adding any summary to the lead, all users engage on the talk page, I don't think any admin action is necessary. WaggersTALK 13:37, 2 January 2025 (UTC)

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

    Appeal of topic ban from 2018

    There is consensus to remove this topic ban reached as part of an unblock. Closer's note: as a contentious topic if disruption were to happen again any uninvolved administrator could reimplement the topic ban. Barkeep49 (talk) 18:28, 3 January 2025 (UTC)

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


    In January 2018 (I believe), I was topic banned from editing articles related to Donald Trump due to a number of idiotic edits that violated BLP. The UTRS ticket for this I believe is here. In the time since then, I have demonstrated that I can edit Misplaced Pages constructively (I have 80,350 edits, a large number of which will be on BLP and BLP-related topics), and so I am requesting for this topic ban to be revoked. Whilst I do not plan to make large edits on Donald Trump articles, I would like to have the ability to edit articles on current US events from time to time e.g. to comment on them at WP:ITNC where Trump-related article nominations often appear. Please could you consider removal of this editing restriction? Courtesy ping to Alex Shih who implemented the topic ban in the first place . Joseph2302 (talk) 12:24, 2 January 2025 (UTC)

    For what it's worth, Alex Shih was removed as an administrator in 2019 and has not edited since August, 2022. Cullen328 (talk) 17:29, 2 January 2025 (UTC)
    I'd generally support this. Joseph's topic ban from ITN/C and related pages was lifted more than a year ago, and there haven't been any problems in that area, so I have some optimism that this topic ban is also no longer needed. --Floquenbeam (talk) 17:49, 2 January 2025 (UTC)
    I'm a little concerned that after the big mess in 2018 they still managed to get themselves blocked again in 2022. But, yeah, as Floq says, they seem to have moved past that and have a year's worth of productive editing now. They also seem to understand what got them in trouble in the first place, so I'll cautiously endorse lifting the TBAN. It needs to be understood, however, that with this much history if there's more problems I don't expect there will be much willingness to extend any more WP:AGF. RoySmith (talk) 21:10, 2 January 2025 (UTC)
    Endorse lifting TBAN per above. -- Deepfriedokra (talk) 23:44, 2 January 2025 (UTC)
    Endorse removal of topic ban. 78.26 (spin me / revolutions) 02:09, 3 January 2025 (UTC)
    Endorse removal of topic ban per Misplaced Pages:One last chance. Cullen328 (talk) 02:27, 3 January 2025 (UTC)
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    User:SpiralWidget vandalizing pages

    Given this, it appears the OP has withdrawn their complaint. - The Bushranger One ping only 21:58, 3 January 2025 (UTC)

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


    I am reporting User:SpiralWidget for repeated vandalism on articles I have created or contributed to. Below is the evidence of their disruptive behavior:

    Evidence

    1. Diff 1 – User:SpiralWidget removed sourced content and replaced it with false information. – This is when SpiralWidget first began vandalizing my contributions. He falsely alleged that simply creating a wikipedia article was to influence an election, and even posted a link to a ballotpedia page about an election in 2026 to encourage sabotaging the article. The reason this is concerning, is because the page is general information about Moliere Dimanche, an artist, a prison reform activist, and a litigant who accomplished a presidential case law and wrote a book. Nothing in the page promotes anything election related, and as can be seen in the link, SpiralWidget did not base the reason on anything other than unwarranted suspicions.

    2. Diff 2 – In this instance, SpiralWidget removed information from a discussion with Professor Tim Gilmore about Dimanche's high school teacher Mrs. Callahan, and a very effective way she helped students in. English class. Mrs. Callahan would give students key words from the play Caesar, and have them use them in an essay writing contest that was timed. Dimanche excelled at this and became an outstanding student in Mrs. Callahan's class. SpiralWidget took an issue that is not even contentious and used it to sabotage the article. It is sabotage because Caesar is a play that was actually written by Shakespeare. I don't think any reasonable person would find that as contentious because it was in an English class in high school, and Caesar is just one part of the lessons on Shakespeare. That's like if the interview was about Frankenstein, and the article stated that Dimanche excelled in studying Mary Shelley. It was unnecessary harassment.

    3. Diff 3 – In this instance, SpiralWidget moved a redirect page to drafts after the article was pointed to a different article using Dimanche's full name instead of his nickname. His reason was so that there could be a discussion, but Misplaced Pages's guidance on this clearly states that a formal discussion is not necessary for redirects, and Misplaced Pages's deletion policy discourages deleting duplicate pages. It even encourages editors to delete entire text and replacing it with redirects. Yet, again, SpiralWidget took it upon himself to allege political motivations, and none of it is true.

    4. Diff 4 - After SpiralWidget did that, he then nominated Moliere Dimanche for deletion, again alleging that it had something to do with an election for governor in 2026. This is not true. The article talks about Dimanche's humble upbringing, his time spent in prison, his efforts in local politics in Orlando, his art, and a case law he helped accomplish in the 11th Circuit that set precedent regarding the Prison Litigation Reform Act. And even if it did, Misplaced Pages has many candidates for office. Misplaced Pages even displays election results, gains by party affiliation, laws introduced, and many other accolades. This is what makes me believe SpiralWidget has some type of animus for Mr. Dimanche, because he constantly makes an issue out of the election, when the article does not focus on that at all.

    5. Diff 5 - The vandalism didn't stop there. SpiralWidget then went to Dimanche v. Brown and nominated that page for deletion as well. Why, because Dimanche was a part of that case. He lied and said that the case was not notable, before asserting that it only made Dimanche look good. This is ridiculous and appears to be hateful. This is a case law, meaning it is not something Dimanche had control over at all. Also, the "Precedential Status" of the law is "Precedential". The case has been cited by judges all across the nation to resolve an additional 178 federal cases. To put that in perspective, Roe v. Wade was cited 2,341 times in resolving federal cases since 1973. This is approximately 46 citations per year. Since Dimanche v. Brown was passed it averages about 20 citations a year. So for SpiralWidget to lie and say that the case is not notable, when clearly, the judge of this country would state otherwise is nothing more than vandalism. Additionally, Misplaced Pages already found all of the related laws and indexed them accordingly.

    Spiralwidget (talk) is vandalizing my pages if they even mention Dimanche, and he is doing harm to genuine, good faith editing. I believe the articles about Dimanche are necessary and important because his prison experience is well documented, and his art is unusual. Renown scholars like Tim Gilmore and Nicole Fleetwood have given thoughtful analysis to his art, and the art is widely recognized. I don't think these articles should be nominated for deletion, and I would request that they be taken out of that nomination, and SpiralWidget be prohibited from further editing on the subject of Dimanche.

    6. List affected articles: Moliere Dimanche, Dimanche v. Brown, etc.

    Context

    - This behavior has been recurring since SpiralWidget used the ballotpedia link the first time and persists today. - I believe this violates Misplaced Pages’s policies and discourages editors from adding to Misplaced Pages.

    I have notified the user on their talk page using ==Notice of noticeboard discussion== Information icon There is currently a discussion at Misplaced Pages:Administrators' noticeboard regarding an issue with which you may have been involved. Thank you.. I kindly request administrative intervention to address this issue.

    NovembersHeartbeat (talk) 18:36, 2 January 2025 (UTC)

    First, you need to read and understand the definition of "vandalism" in WP:Vandalism. Next, you are not allowed to remove properly placed AfD notices until the AfD has been properly closed. I do not see anything improper in Spiralwidget's edits that you linked. I would advise you to drop this complaint and read over our policies and guidelines before resuming editing. Donald Albury 18:47, 2 January 2025 (UTC)
    Thank you for your feedback. I understand that I should not remove AfD notices before they are officially closed, and I will follow the proper procedures moving forward. I will also review WP:Vandalism more thoroughly to ensure I’m taking the correct steps in addressing any inappropriate edits. I appreciate your advice and will proceed accordingly. NovembersHeartbeat (talk) 18:54, 2 January 2025 (UTC)
    Hi! I feel like I need to weigh in here on my perspective.
    • I was reviewing articles on WP:AFC back in September (EDIT: Turns out it was November. Seems like longer ago.) and stumbled upon Draft: Moe Dimanche, which had been submitted by NovembersHeartbeat (Diff1 in the list above). I then found that he was running for Governor of Florida in 2026, and added a comment on the article pointing this out for future reviewers (as I did not feel strongly about the subject, and I am not so familiar with WP:ARTIST, which was the main claim of notability).
    • Following this, NovembersHeartbeat responded here https://en.wikipedia.org/search/?title=Draft%3AMoe_Dimanche&diff=1256694716&oldid=1256642401 and accused me of election interference.
    • I then commented on User talk:NovembersHeartbeat because I felt I needed to respond to this. NovembersHeartbeat then responded negatively, but eventually I decided to leave the issue and bookmark Draft:Moe Dimanche on my watchlist in order to follow the conversation from then on.
    • On 2 January, earlier today, I opened my Watchlist to see that Draft:Moe Dimanche had been moved to mainspace by NovembersHeartbeat. I then pressed the "revert" button, which I wrongly assumed would revert the article to draftspace. Turns out, this was not possible because NovembersHeartbeat had NOT published Moe Dimanche as an article; instead, he had made a new article, Moliere Dimanche, with a new name, in order to get past the AfC process (which was not going well for Dimanche at all...); as a result, the attempted reversion did not work at all. I then decided that, although I believe I was entitled to go for speedy deletion, I would nominate the article for deletion (I still have WP:COI concerns and I don't think he passes WP:GNG) and also nominate Dimanche v. Brown, which has also been created by NovembersHeartbeat recently.
    • In addition, I would like to question whether there is WP:COI going on here. I think a pertinent recent example that looks suspicious to me is the upload of the image https://commons.wikimedia.org/File:Moliere_dimanche.png which was uploaded at 03:26, 1 January 2025 (i.e. 22:26 on 31 December Florida time) by user https://commons.wikimedia.org/User:Moe_Dimanche, who I am assuming is the subject himself in the flesh. This was then added to the article in this edit by NovembersHeartbeat https://en.wikipedia.org/search/?title=Moliere_Dimanche&oldid=1266552816 on 04:40, 1 January 2025 (23:40 on 31 December Florida time). This is only slightly over an hour after the file itself was uploaded, at a time when most people were at a New Years Eve party. I am not making accusations here, but I am concerned that Dimanche is having communication with NovembersHeartbeat. Either that, or NovembersHeartbeat is indulging in WP:SOCK... Would NovembersHeartbeat like to comment on this? Spiralwidget (talk) 19:05, 2 January 2025 (UTC)
    Well, I was advised to drop the complaint, but if you still want answers, I don't mind telling you as I have told you before, I do not have any conflicts of interest. Your whole approach to this topic just seems personal. Even here, the content of the article is not in question, the facts are not in question, you just seem to believe that I am the subject. I made this complaint because I feel like what you are doing is harassment, and you might know the subject yourself or have some type of rivalry against him. I thought Misplaced Pages had a mechanism to prevent that, and I was wrong. I don't know what else to tell you. NovembersHeartbeat (talk) 19:22, 2 January 2025 (UTC)
    I checked diff 2 in the complaint, and Spiralwidget is correct: the source does not support the text. Spiralwidget was justified in removing it. Schazjmd (talk) 22:08, 2 January 2025 (UTC)
    "Mrs. Callahan would give students key words from the play Caesar, and have them use them in an essay writing contest that was timed. Dimanche excelled at this" is from NovHeartbeats, but none of this is in the source. How does November know so much about how these assignments worked? Was November in the classroom, or is November using sources the rest of us can't see? 74.254.224.67 (talk) 23:53, 2 January 2025 (UTC)
    The exact text from the source is

    "And I had a really good English class back at West Orange High School in Orlando. Ms. Callahan. I couldn’t wait to get to her class. She’d give us a certain amount of time to write a story with keywords from a play we were reading, like Julius Caesar."

    The source says exactly what you just quoted. NovembersHeartbeat (talk) 00:02, 3 January 2025 (UTC)
    The source says nothing about whether he was good in the class ("excelled") nor does it say "he enjoyed studying Shakespeare". Schazjmd (talk) 00:25, 3 January 2025 (UTC)
    The source doesn't mention any contests as you seem to know about. And its an interview of Moliere, with two single line questions asked by the interviewer. It definitely doesn't support anything except Moliere saying he had a favorite class, which isn't encyclopedic. 74.254.224.67 (talk) 00:37, 3 January 2025 (UTC)

    This is discussion is turning into a content dispute, which doesn't belong here. There's a bit of WP:OUCH going on but right now I don't see a need for admin intervention for either editor. WaggersTALK 15:31, 3 January 2025 (UTC)

    While there is a content dispute in play here, I think behavior is a problem as well...but it's largely by the OP. Remarks like " is vandalizing my pages" (emphasis added). @NovembersHeartbeat:, I would strongly advise that you read WP:OWN, WP:BRD, WP:VANDALISM, and WP:ANYONE. These aren't your pages. Anyone can edit them. If you have a disagreement, then bring it to the talk page. What you are describing as vandalism, is normal editing and disagreement; I would encourage you to strike such remarks as they are inherently hostile when unsubstantiated. This is a normal part of the collaborative editing process. If you don't, your complaints will not only be ignored, but may be to your own detriment. I understand that people may feel that some subjects aren't notable to get their own page and nominations for deletion can feel personal. I've weighed in for inclusion on the subject. Try not to take it personally. Buffs (talk) 19:36, 3 January 2025 (UTC)

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

    Repeated tool abuse by User:FlightTime

    Not tool abuse. The IPv6 editor should discuss this with FlightTime, not ANI EvergreenFir (talk) 06:45, 3 January 2025 (UTC)

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


    I have been working on the article Fender Stratocaster with a view to possibly improving it to featured article status at some point in the future. At this point, the edits are mostly restructuring to bring the article into a shape that can then be further developed, depending what it still needs when that first step is done. FlightTime took exception to some edit I made between 22nd and 23rd of December and reverted four edits, without clarifying exactly which edit they thought was problematic. We had a conversation about it, and they reverted themselves. At that point, I believed we had cleared the air, and the situation would not repeat itself.

    However, today, they reverted 17 edits of mine, all in one go, again without any explanation of which edit(s) they felt were problematic. Thus, they make it impossible to discuss or remedy what they felt was the problem. In my opinion, this constitutes tool abuse, and if they cannot improve their communication with IP users and ideally use the tools in a more targeted way, this is a problem for the community.

    Thank you for your time and consideration, and any help in getting to a more constructive collaboration on this article.

    2A02:8071:184:4E80:0:0:0:EAC0 (talk) 00:53, 3 January 2025 (UTC)

    This is not tool abuse, you are being reverted with reasons, and you should discuss the matter with FlightTime. PhilKnight (talk) 00:58, 3 January 2025 (UTC)
    I'm not sure what you mean without any explanation as his edit summary clearly documents his reason as Reverted good faith edits by 2A02:8071:184:4E80:0:0:0:EAC0 (talk): Unsourced, unexplained content removal, unsourced OR. Please note that he did assume good faith (not maliciousness), and that he appears at first glance correct that you were removing content without reason, and adding unsourced and/or original research to the article, which is not permitted. Please use the article talk page at: Talk:Fender Stratocaster or talk to the editor directly on their talk page at User talk:FlightTime and work on building consensus instead of readding the same or similar content to the article. TiggerJay(talk) 01:12, 3 January 2025 (UTC)
    Again, which are the pieces that you are now objecting to? We are talking about 17 edits, so please be specific! Thank you. 2A02:8071:184:4E80:0:0:0:EAC0 (talk) 06:19, 3 January 2025 (UTC)
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Emoji redirect

    👌 - The Bushranger One ping only 05:33, 3 January 2025 (UTC)

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


    Was trying to create 👌 (film) as a redirect to Super (2010 Indian film); the film does not actually have a title and was represented in posters by the Vitarka Mudrā aka the OK gesture. Apparently the emojis are on a blacklist, it would be great if someone can create this rd, thanks. Gotitbro (talk) 01:35, 3 January 2025 (UTC)

     Done. JJPMaster (she/they) 01:48, 3 January 2025 (UTC)
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Topic ban appeal

    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)
    • 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)
    • 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)
    • 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)
    • 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)

    Request to Fix Redirect Title: Camden stewart

    Looks like this is done. - The Bushranger One ping only 18:39, 4 January 2025 (UTC)

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


    Hi, I need help correcting the capitalisation of the redirect "Camden stewart" to "Camden Stewart" as the surname is improperly lowercase. I cannot make the change myself because redirects require admin intervention for title corrections. Could an admin please assist? Thank you! GD234 (talk) 05:19, 3 January 2025 (UTC)

    How many redirects are you making? I see a lot of activity today. — rsjaffe 🗣️ 05:25, 3 January 2025 (UTC)
    Thanks for your response! I’m just setting up a few redirects to make it easier for people to find Camdenmusique's article, like Camden Stewart or Camden Music. Let me know if anything needs adjusting, appreciate your help!" GD234 (talk) 05:30, 3 January 2025 (UTC)
    @GD234: I have moved the article to draftspace at Draft:Camdenmusique. If you have a conflict of interest with Camden Bonsu-Stewart (which I suspect that you may since you are interested in ensuring that the article is indexed on Google and you uploaded his professional headshot), you must declare it following these instructions. You should also not republish the article until it has been reviewed by an experienced editor at articles for creation. voorts (talk/contributions) 05:30, 3 January 2025 (UTC)
    Thank you for your feedback! GD234 (talk) 08:09, 3 January 2025 (UTC)
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Andra Febrian report

    "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)
    @The Bushranger - Quack quack? Blue Sonnet (talk) 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. 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)

    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)

    Proposal to vacate ECR remedy of Armenia and Azerbaijan

    Already closed. - The Bushranger One ping only 01:36, 4 January 2025 (UTC)

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


    There is a proposal to vacate the ECR remedy of WP:GS/AA at Misplaced Pages:Village pump (proposals) § Remove Armenia-Azerbaijan general community sanctions. voorts (talk/contributions) 00:53, 4 January 2025 (UTC)

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

    Cannot draftify page

    Done. - The Bushranger One ping only 18:38, 4 January 2025 (UTC)

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


    I tried to draftify Wuliangbao_Pagoda but a draft exists with the same name (and same content before I blanked it). Could an admin delete the draft so I can draftify the article? If you reply here, please ping me. Thanks, TheTechie@enwiki (she/they | talk) 00:59, 4 January 2025 (UTC)

     Done @TheTechie: Draft:Wuliangbao Pagoda has been deleted. — xaosflux 01:26, 4 January 2025 (UTC)
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Remove PCR flag

    Flag run down. - The Bushranger One ping only 18:38, 4 January 2025 (UTC)

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


    Can an admin remove my Pending changes reviewer flag as I have not used it recently. Thanks ~/Bunnypranav:<ping> 06:26, 4 January 2025 (UTC)

    Done. Extraordinary Writ (talk) 06:40, 4 January 2025 (UTC)
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    "The Testifier" report

    Moved to Misplaced Pages:Administrators' noticeboard/Incidents § "The Testifier" report – voorts (talk/contributions) 18:06, 4 January 2025 (UTC)

    Problem with creating user talk page

    CU blocked as sock by Spicy. voorts (talk/contributions) 01:10, 5 January 2025 (UTC)

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


    Hello, I'd like to get some help to create the talk page of user BFDIisNOTnotable (talk · contribs) to warn them against edit warring with {{subst:uw-ewsoft}} or a similar notice. Trying to create the page gives a notice that "bfdi" is in the title blacklist. I wonder how the user was allowed to create the account today, given that from what I can see, the blacklist should also affect usernames...? I obviously can't notify the user of this AN post on their talk page. ObserveOwl (talk) 14:01, 4 January 2025 (UTC)

    I have created the talk page. No idea why 'BFDI' is on the blacklist, and if so, why a user name by that was allowed - that's something for cleverer heads than mine... GiantSnowman 14:13, 4 January 2025 (UTC)
    I think it stands for "Battle for Dream Island". See WP:BFDI. Phil Bridger (talk) 14:25, 4 January 2025 (UTC)
    Ah, I wondered if it was linked to Bundesbeauftragter für den Datenschutz und die Informationsfreiheit. GiantSnowman 14:32, 4 January 2025 (UTC)
    As to the technical reason that the username could be created, the reason is that accounts are not actually created on this wiki. They are created globally. As a result, us blacklisting anything can't prevent account creation. Animal lover |666| 18:09, 4 January 2025 (UTC)
    This particular account was definitely created on this wiki. Graham87 (talk) 01:04, 5 January 2025 (UTC)
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Administrators' newsletter – January 2025

    News and updates for administrators from the past month (December 2024).

    Administrator changes

    added Sennecaster
    readded
    removed

    CheckUser changes

    added
    readded Worm That Turned
    removed Ferret

    Oversight changes

    added
    readded Worm That Turned

    Guideline and policy news

    Technical news

    • The Nuke feature also now provides links to the userpage of the user whose pages were deleted, and to the pages which were not selected for deletion, after page deletions are queued. This enables easier follow-up admin-actions.

    Arbitration

    Miscellaneous


    Sent by MediaWiki message delivery (talk) 15:46, 5 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 )

    ---

    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)

    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)
    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)


    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)
    • 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)

    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)

    • 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:

    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)
    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)
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    An inappropriate template being added to many pages

    A user is adding the "mortal sin" template to a large number of articles where it doesn't belong . I've reverted 3 of them that were added to the articles I have watchlisted. Could someone who knows how to do massive reverts take care of the others? Thanks. NightHeron (talk) 11:51, 6 January 2025 (UTC)

    Discussion at Misplaced Pages:Templates_for_discussion/Log/2025_January_6#Template:Mortal_sin_in_the_Catholic_Church. Gråbergs Gråa Sång (talk) 12:07, 6 January 2025 (UTC)
    I've reverted the addition of the template. Callanecc (talkcontribslogs) 12:13, 6 January 2025 (UTC)
    The template as been deleted per WP:G4. Callanecc (talkcontribslogs) 12:35, 6 January 2025 (UTC)

    A look through this editor's talk page shows that there is a wider issue with their editing about religion. Regarding this specific issue they have done something quite similar before (see Template:Mortal Sins According To The Catholic Church) along with a number of articles they've written moved to draftspace and that have been nominated for deletion. Their contibution history also shows a significant portion of edits having been reverted. Before suggesting any action I'm keen to hear from Oct13 on this. Callanecc (talkcontribslogs) 12:35, 6 January 2025 (UTC)

    Btw, the last time Oct13 has ever edited a noticeboard was on June 6 2020. The last 2 times they edited a talk page were on February 17 2022 and April 15 2020. Tarlby 17:40, 6 January 2025 (UTC)
    It also looks like the main thing they have done on their own talk pages in the last seven or eight years is to just repeatedly blank it. We may have a RADAR situation here. Beeblebrox 01:45, 7 January 2025 (UTC)

    This editor's editing looks to consist largely of making inappropriate edits, "sourced" if at all to unreliable sources, and perhaps in hopes that if enough of that is done, a few will slip by. As we're unlikely to hear from them, I'd be in favor of indefinitely blocking them, at the very least until they meaningfully engage regarding the problems with their editing. Seraphimblade 01:55, 8 January 2025 (UTC)

    I second that. As we wait here, they continue to edit, and all have been reverted. Perhaps an articlespace block until we get a satisfactory response?— rsjaffe 🗣️ 03:23, 8 January 2025 (UTC)
    I've blocked them indefinitely from mainspace. Seraphimblade 05:36, 8 January 2025 (UTC)
    Liz invited them to reply here. Let’s keep this open for now and see if the user responds, now that regular editing of articles is blocked.— rsjaffe 🗣️ 15:11, 8 January 2025 (UTC)

    Ottawahitech, requesting an appeal on their talk page restriction

    User wants to use Misplaced Pages as a social network. Misplaced Pages is not a social network. - The Bushranger One ping only 22:05, 6 January 2025 (UTC)

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


    Hello, I find that Ottawahitech (talk · contribs) has opened an appeal about their talk page restriction.


    As I have told the blocking admin, whom I am not pinging at their request, I do not wish to appeal my block. Before I was blocked at the discretion of Beeblebrox/Just Step Sideways I made about 75,000 "edits" to the English Misplaced Pages, and have continued contributing to other Wikimedia projects since my Block in 2017. I enjoy my recent volunteer activity more than I did my activity here, and do not ask for a complete unblock. However, I would still like to be able to communicate with fellow wikipedia editors and request the removal of the restrictions that have been imposed on my user-talk.
    Notice to the admin handling this request: Just to let you know I am a very infrequent visitor to the English Misplaced Pages, and as such there is no urgency in acting on this request. Thanks in advance, Ottawahitech (talk) 23:26, 4 January 2025 (UTC)

    I'd copy them here. Though in my opinion, the restriction just came along commonly as the indef block. Hoping someone may like to review that. -Lemonaka 15:09, 6 January 2025 (UTC)

    This might be better at WP:AN. — Malcolmxl5 (talk) 15:12, 6 January 2025 (UTC)
    Moved per request-Lemonaka 15:13, 6 January 2025 (UTC)
    What was Ottawahitech blocked for to begin with? My understanding is something to do with bad page creation attempts and / or edit warring at article talk. Is this correct? Has Ottawahitech demonstrated that they understand what they did was wrong? Because they appear to have been indeffed in 2017 and indefinite doesn't mean forever. If they've shown recognition of what led to their block and have committed not to repeat their mistakes then I'd be inclined to say this looks like a reasonable request. Simonm223 (talk) 15:22, 6 January 2025 (UTC)
    Their previous block seemed a little bit like WP:CIR block, and I'm, auch, due to my interaction with them on another project, I'm inclining a not unblock. -Lemonaka 15:29, 6 January 2025 (UTC)
    @Lemonaka: why did you post this here? I didn't see Ottawa make a request for this to go to AN. Additionally, blocked means blocked. We don't let blocked editors use their talk page to shoot the shit with other editors. If Ottawa wants to chat with old friends, they can email each other. voorts (talk/contributions) 15:47, 6 January 2025 (UTC)
    I agree that we should decline this request. We're here to write an encyclopedia, not run a chat board. If Ottawahitech is interested in the social aspects of wikipedia, they should pursue other communication channels. Perhaps the Wikimedia Community Discord Server is what they're looking for. RoySmith (talk) 20:38, 6 January 2025 (UTC)
    Argh. I came here for an entirely different reason, but I am unsurprised to see the persistent IDHT behavior of this user continues on.
    I blocked them in 2017 for persistent failure to abide by basic content policies, mainly being very experienced but still regularly creating pages that qualified for speedy deletion. I believe there was a discussion somewhere that led to it but I seem to have failed to note it in the block log. What I do recall is that they did not participate in that discussion.
    Several months later another admin revoked talk pages access because they were using the page to chat, and to ask other users to proxy for them, while not addressing the block.
    Four years later they contacted me via another WMF site and I did them the courtesy of re-instating their talk page for purposes of appealing their block. They then indicated they didn't want to do that, they just wanted talk page access back.
    And that's still all they want. They don't want to rejoin this community as an editor. There's no point to even discussing this except to consider the possibility of re-revoking TP access to avoid further time wasting nonsense like this. Beeblebrox 21:22, 6 January 2025 (UTC)

    FTR, here is the ANI discussion that led to the block of Ottawahitech. --bonadea contributions talk 21:58, 6 January 2025 (UTC)

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

    RFU backlog doin' great

    I know I ruffled some feathers with the way I approached this last month, but I'm pleased to report that as of this writing there are less than twenty pending unblock requests, many of those being CU blocks. Not that long ago the daily average was closer to eighty. I certainly did not do this alone, in fact I was ill for a week there and did basically nothing. Quite a number of admins and others pitched in in various ways over the past few weeks to move things along.

    That's great, but we should not get complacent, as that was what led to the backlog being so bad before. Thanks to everyone who helped get it to where it is now. I would again encourage any and all admins to pitch in whatever they can to keep this manageable. Any substantive review of an unblock request helps. Thanks again to everyone who helped make this suck a little less. Beeblebrox 21:32, 6 January 2025 (UTC)

    Call for mentors

    There's a discussion at Misplaced Pages talk:Growth Team features/Mentor list about extending the mentorship module to all new accounts. Presently, all new accounts are assigned a mentor, but only half of them receive the module that allows them to send questions to that mentor directly from the newcomer homepage. We'd like to extend the module access to all new accounts, but we're a bit short of the "ideal" number of mentors to do so - we're looking to get about 30 more. Posting here because the experienced users who haunt this noticeboard are likely to make good mentors. Basically the only requirement is "not jerk, has clue", with a side of "you should be someone who logs in frequently enough that your mentees won't feel ignored". Most of the questions you get are very easy to resolve. Some are harder. Every so often you get something actually fun. -- asilvering (talk) 23:31, 6 January 2025 (UTC)

    I signed up sometime last year, and I'd guesstimate that I've received questions from maybe 10% of the accounts I'm assigned to mentor. So far (knock on wood) it hasn't been onerous at all. (Hoping that will encourage more editors to give it a try.) Schazjmd (talk) 23:37, 6 January 2025 (UTC)
    Just signed up. I had played with the idea before, but given there are well over a hundred mentors and I don't hear much about it, I assumed it wasn't terribly active or in need of more people. Thebiguglyalien (talk) 03:40, 7 January 2025 (UTC)
    I've noticed I'm getting fewer questions, which I assume is because more mentors have signed up over time but the number of new accounts receiving the module has remained constant (it's a rare mentee who comes back and asks multiple questions over time). So it's true in a way that it didn't really need more people. I expect that you'll notice a significant boost when it goes to 100% and then a gradual decline again. -- asilvering (talk) 14:31, 7 January 2025 (UTC)
    Time to add an option for three time the number of mentees assigned. Nobody (talk) 07:01, 7 January 2025 (UTC)
    Seconding this, I wouldn't be opposed to taking over more mentees if there is a need for it until we get more mentors. Chaotic Enby (talk · contribs) 22:20, 8 January 2025 (UTC)
    Agreed, though the max number of mentees per page might want to be increased to 50 from 25. JayCubby 00:15, 9 January 2025 (UTC)
    I signed up a week ago, and only got a single question asked of me. How many people are using the newcomer dashboard? There, I have found, aren't many users signing up and editing per day, per ListUsers, so I can't imagine there are very many people using the mentorship at all.
    I'd be curious to see what automatically assigning mentors would do to retention rates (maybe that's written somewhere). JayCubby 17:49, 7 January 2025 (UTC)
    I've been "twice as many" assigned for quite awhile now (I think I was one of the first mentors when the program even launched) and I'd say it's not atypical to only get ten or so queries a month. You can look through my talk page archives if you want a more accurate number (also note that sometimes I revert mentee questions if they're obvious spam). Clovermoss🍀 (talk) 04:40, 8 January 2025 (UTC)
    I just counted and it looks like I've had 156 questions since February 2022. Clovermoss🍀 (talk) 04:56, 8 January 2025 (UTC)

    Discussion at Misplaced Pages:Requests for adminship/2024 review/Phase II/Administrator elections

     You are invited to join the discussion at Misplaced Pages:Requests for adminship/2024 review/Phase II/Administrator elections. –Novem Linguae (talk) 10:16, 7 January 2025 (UTC)

    Kansascitt1225 ban appeal

    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

    1. 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)

    voorts (talk/contributions) 21:22, 7 January 2025 (UTC)

    Heritage Foundation

    There is a discussion at Misplaced Pages:Village pump (miscellaneous)#Heritage Foundation intending to "identify and target" editors that may be of interest to those who watch this noticeboard, especially if you edit in the PIA topic area. Clovermoss🍀 (talk) 04:12, 8 January 2025 (UTC)

    Deleted contributions request

    Done and dusted. Good work all. - The Bushranger One ping only 06:11, 8 January 2025 (UTC)

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


    I'm currently leading an investigation at the English Wikibooks into poorly attributed page importations from the 2000s (decade). One page I discovered was Thick Sand Motorcycling, which was allegedly imported from an enwiki page called How-to/Motorcycling, but this page does not appear to have ever existed. It looks like this page was deleted at VFD in 2004, but there is no deletion log entry, so I can't find the original page to re-import to Wikibooks. Its talk page provides a page history for this enwiki article, which includes an anonymous editor whose IP address is 62.200.132.17 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log). If the privacy policy allows it, I would like to know the titles of the pages that this user edited in their three deleted contributions (I don't need the content, just the titles). JJPMaster (she/they) 05:08, 8 January 2025 (UTC)

    @JJPMaster: The only deleted contributions from that IP are to the deleted article you linked above and garden variety vandalism of a redirect saying that "this is junk". If you're looking for poorly attributed page importations, this specific IP would be a dead end on that front. Clovermoss🍀 (talk) 05:15, 8 January 2025 (UTC)
    @Clovermoss: Nope, that's actually all I needed to know—I really just needed this information to verify the page title. Could this page be undeleted in my userspace so I can complete the proper import and merge? JJPMaster (she/they) 05:19, 8 January 2025 (UTC)
    @JJPMaster: Done at User:JJPMaster/How-to/Motorcycling. I've never done something like this before so let me know if I messed up. I removed for VfD nomination template in case that screwed with bots or whatever. Let me know if there's anything else I can do to help. Clovermoss🍀 (talk) 05:27, 8 January 2025 (UTC)
    @Clovermoss: The import and merge are  Done. Please delete the page now. JJPMaster (she/they) 05:30, 8 January 2025 (UTC)
    @JJPMaster: I've deleted the page. Clovermoss🍀 (talk) 05:31, 8 January 2025 (UTC)

    The reason you couldn't find it in the deletion log is because logs didn't exist in their current form until 23 December 2004. This page was deleted about a month before that. —Cryptic 06:36, 8 January 2025 (UTC)

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

    WP:NOTHERE behavior (or 'very' slow learner) from User: Astronomical17

    Editor hasn't edited in a week, feel free to reopen should disruption continue if they return. Liz 03:09, 9 January 2025 (UTC)

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


    User:Astronomical17's talk page has got some history. It would seem they have a habit of AfCing articles on rappers and sports teams, failing them, and then making them anyway, such as with Devstacks which is currently at WP:AfD and looks like it deserves a PROD. They've been repeatedly informed to include sources and citations but seem to fail to do so. But my WP:NOTHERE allegation comes from this diff at the AfD where they blanked the page, seemingly in an attempt to obstruct the AfD process. Does this behavior warrant administrator action beyond a stern talking-to? guninvalid (talk) 10:10, 8 January 2025 (UTC)

    Sure, a long talk page, but not a single non-templated notice as far as I can tell (though I might have missed one). I think a kind word would suffice, at least to start out with. Primefac (talk) 10:27, 8 January 2025 (UTC)
    I generally concur, however, this user (a.k.a. User:Cyanxbl) doesn't seem to be interested in talking to anyone about his actions. Buffs (talk) 21:06, 8 January 2025 (UTC)

    Left a warning and note on his user talk page. Hopefully he engages. If such behavior continues, a block may be necessary to get his attention and drive the collaborative process. While I support such a block, it should ONLY be used to stop such disruptive behavior if it continues. Once that ceases and he's willing to collaboratively edit, such a block should be lifted post haste! Buffs (talk) 21:12, 8 January 2025 (UTC)

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

    Confusion about two articles that may be covering the same person

    The pages are Chaudhry Sher Ali Khan and Chaudhary Sher Ali. Can an administrator please find the correct name and merge them, if they are the same person? 71.202.215.54 (talk) 22:14, 8 January 2025 (UTC)

    Are they the same person? The date of birth (for Chaudhary Sher Ali) is the same in the text (without a source here), but in the infobox (added by an IP without a source: diff) it's different... Honestly, I feel it would be easier to just give up on this one, it was created by a sock-puppeteer (albeit on their original account, though they edited it with multiple socks too, seemingly all reverted), it's quite possibly a waste of time.
    That said I didn't actually investigate what is salvageable about the content - just reverted the last 2 edits by an IP. – 2804:F1...96:BB60 (::/32) (talk) 22:45, 8 January 2025 (UTC) *edited: 05:10, 9 January 2025 (UTC)
    Special:Contribs/2804:F14::/32, this seems like a valid inquiry, why would it be considered a "waste of time"? I don't know what you mean by "giving up on this one" when it's a matter of investigating whether we have a duplicate article here. Liz 02:23, 9 January 2025 (UTC)
    I'm not sure why you seem to be attempting to discourage people looking into this. Seems like something that would be both possible, and important, to do. Or at the very least, attempt. Sergecross73 msg me 02:58, 9 January 2025 (UTC)
    Fair enough, I shouldn't be discouraging. I was thinking this might be a WP:TNT kind of situation (for the second linked article), due to the amount of socking and unsourced edits, and the article already existing if it's the same person, as opposed to merging them - but you are both right that it's always worth checking.
    I'll just cross out that part of the comment. – 2804:F1...96:BB60 (::/32) (talk) 05:09, 9 January 2025 (UTC)
    I don't think this is an admin thing, it's a content issue; shouldn't it be discussed on one of the talk pages, possibly with a proposed merge, instead of here? WaggersTALK 08:55, 9 January 2025 (UTC)

    Non-EC editor editing ARBPIA, broadly construed.

    This is intended as a "heads-up", asking for admin eyes, and letting admins know what I have done. I noticed edits by OnuJones (talk · contribs · deleted contribs · logs · filter log · block user · block log) to 57th Infantry Regiment (Ottoman Empire) and Sinai and Palestine campaign, removing mentions of Palestine or changing Palestine to Israel. I have undone the edits. I have placed welcome/warning templates on their usertalk page, as advised when I asked recently on AN about a similar situation. The account in question was created on 4 December 2020, made two edits on that day, and then nothing until the three edits on the 7th January this year that caught my eye. I shall forthwith add {{subst:AN-notice}}~~~~ to their usertalk page. DuncanHill (talk) 23:41, 8 January 2025 (UTC)

    I don't think this really needs admin attention. Your CTOP notice suffices. If they continue making those kinds of edits, you can go to AE or ANI. voorts (talk/contributions) 23:47, 8 January 2025 (UTC)
    I might have to reread the ARBPIA restrictions because these two edits are about incidents around World War I. I'm not sure they are covered by ARBPIA restrictions which I tend to remember are about contemporary events. Liz 02:19, 9 January 2025 (UTC)
    I think the concern is that while the articles aren't ARBPIA per se, the edits (changing Palestine to Israel ) are clearly ARBPIA-motivated, as it were. (Even leaving aside the historical inaccuracy in that Israel didn't exist at the time!) - The Bushranger One ping only 03:16, 9 January 2025 (UTC)
    I would consider the edits to be within the realm of WP:ARBPIA broadly construed. TarnishedPath 03:41, 9 January 2025 (UTC)
    Those kinds of transparently false Palestine to Israel or Israel to Palestine edits should result in a block without warning and without any red tape in my view. They know what they are doing. People who edit in the topic area shouldn't have to waste their time on these obvious WP:NOTHERE accounts. Sean.hoyland (talk) 03:56, 9 January 2025 (UTC)
    I guess I didn't make my meaning all that clear. Editors should not post to AN every time they warn a brand new account about a CTOP. It's a waste of everyone's time. voorts (talk/contributions) 15:29, 9 January 2025 (UTC)
    @Voorts: It's not a brand new account, but presumably you didn't waste any of your time by actually reading my post. DuncanHill (talk) 18:47, 9 January 2025 (UTC)
    I misstated that this was a new account, but an account with five edits that hasn't edited since before you warned them isn't really something that needs an AN thread. I apologize for my tone. voorts (talk/contributions) 19:25, 9 January 2025 (UTC)

    Hide this racist edit.

    Different project, nothing for en.wikipedia.org admins to do. OP was pointed in the right direction. --Yamla (talk) 11:27, 9 January 2025 (UTC)

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


    Hide the racist edit summary. It says bad words and it is stereotyping Romani people.

    https://rmy.wikipedia.org/Uzalutno:Contribuții/178.115.130.246 200.80.186.184 (talk) 08:52, 9 January 2025 (UTC)

    That's on the Romani Misplaced Pages, we only deal with the English one here. You'll need to raise that with the admins on that project. WaggersTALK 08:57, 9 January 2025 (UTC)
    Please refer to m:SRM, if there are no active RMYWP admins available. Ahri Boy (talk) 11:26, 9 January 2025 (UTC)
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Admin prohibits to delete copyright links

    This has nothing to do with the English Misplaced Pages.--Bbb23 (talk) 14:57, 9 January 2025 (UTC)

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


    In the following topic: MU Online Admin Egilus refuses to delete the following links that violate Copyright policies (links to pirated websites):

    Refers to "Community discussion", when the latest discussion about the page contents happened on 2008 and simple google is available to see which links are pirated and which are not. Nebraska Ivan (talk) 14:56, 9 January 2025 (UTC)

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

    96.230.143.43

    This user is a frequent vandal on the page Devils Tower. I am requesting a block. Drdr150 (talk) 16:34, 9 January 2025 (UTC)

    Blocked. In the future, please use WP:AIV. Jauerback/dude. 16:37, 9 January 2025 (UTC)
    Ah, very sorry. Drdr150 (talk) 17:39, 9 January 2025 (UTC)

    StoneX Group Inc.

    I’m concerned about the page at StoneX Group Inc.

    There are disclosed COI paid edits but the main problem I’m highlighting here is that the subject company appears to see that they have ownership of the page to the extent of adding obviously inappropriate stuff, see my most recent edit to remove it. I’m not sure of the correct procedure and was wondering if an admin could possibly have a polite word with those editors? Thanks. JMWt (talk) 17:06, 9 January 2025 (UTC)

    Permissions Removal

    Hello, please remove my rollback and pending changes review permissions. Rollback is redundant because I have global rollback and I do not use the reviewer rights enough to warrant keeping them. Thank you! Ternera (talk) 20:03, 9 January 2025 (UTC)

    Done. Thank you. — rsjaffe 🗣️ 20:08, 9 January 2025 (UTC)
    Category: