Revision as of 03:26, 20 June 2024 view sourceThe Wordsmith (talk | contribs)Edit filter managers, Autopatrolled, Administrators15,541 edits →Contested RfC non-admin partial close: closing discussion, I re-closed the RFC and endorsed the original result← Previous edit | Latest revision as of 23:12, 17 January 2025 view source Buffs (talk | contribs)Extended confirmed users, Pending changes reviewers, Rollbackers27,494 edits →Sander.v.Ginkel unblock request: oppose | ||
Line 1: | Line 1: | ||
{{pp-sock|small=yes}} | |||
<noinclude><!-- Inside the noinclude, because this page is transcluded. -->{{User:MiszaBot/config | <noinclude><!-- Inside the noinclude, because this page is transcluded. -->{{User:MiszaBot/config | ||
|algo = old( |
|algo = old(7d) | ||
|counter = |
|counter = 368 | ||
|archive = Misplaced Pages:Administrators' noticeboard/Archive%(counter)d | |archive = Misplaced Pages:Administrators' noticeboard/Archive%(counter)d | ||
|maxarchivesize = 700K | |maxarchivesize = 700K | ||
Line 31: | Line 32: | ||
{{Clear}} | {{Clear}} | ||
{{Admin tasks}} | {{Admin tasks}} | ||
__TOC__ | |||
</noinclude><!--Here because there's a bug in mobile, please don't remove--> | </noinclude><!--Here because there's a bug in mobile, please don't remove--> | ||
== Sander.v.Ginkel unblock request == | |||
== Pages recently put under ] == | |||
{{collapse top|bg=#F0F2F5|Report}} | |||
{{User:MusikBot/ECPMonitor/Report}} | |||
{{collapse bottom}} | |||
== A user has requested removal of talk page content at ] == | |||
The following is copied from ] on behalf of {{u|Sander.v.Ginkel}}: | |||
A dispute over whether to include a deceased person in ], and with what details, resulted in edit-warring (see May 14 in the edit history), blocking and, in one case, an eventual indef for one user. Some of the content on the talk page has already been struck but an editor claiming to be a relative of the deceased person has that all comments about the person be deleted. This would (presumably?) require striking of much of the content of ] and some of ]. It might be necessary to pin a notice to ensure the person is not mentioned again or included in the article, though how this could be done without the person's name beats me, unless it is possible to flag the name for bot detection. Cheers, ] <sup>(] ])</sup> 02:52, 15 June 2024 (UTC) | |||
{{tqb|I have made serious mistakes. I regret it and say sorry for it. I fully understand why I have been blocked. My biggest mistake that I copied-pasted content from articles to other articles, that led to a BLP violation. I have also misused other accounts as suckpuppets: ] and ] (note that the two other accounts –- ] and ] -- at ] was not me. ) In addition, my work was too focused on quantity, rather than quality. I apologize to those who had to do some cleaning up for me. | |||
Whay do I want to come back? And do I deserve it? I can show that I can make constructive content. I made some edits and created pages under the IP address 82.174.61.58, that was not allowed; and was blocked. It is not good that I made edits under an IP address, but I appreciated that some users (], ], ]) stated they liked the content I created and/or that they offer the opportunity to have me back (see at ]). I made the same mistakes on the Dutch Misplaced Pages (where I misused the same accounts). At this Misplaced Pages I bot back my account and I am editing the Wikipeida I’m also editing at simple.wikipedia.org (see ]). I have created over 900 pages (see ]), (1 page being deleted). I like to create articles from historic work on old sources, for instance ], ], ], ] or the event ] that is barely mentioned at the English ]. Around 100 pages have been (literally) copied to the English Misplaced Pages by several users. I'm also editing Wikidata, see ] and ]. | |||
:This just looks like reliable sources. The person claiming to be family says we have the dob wrong. Where did we get the dob? We only use published sources. ] (]) 05:06, 15 June 2024 (UTC) | |||
::The dispute was over which of 2 equally reliable sources should be used as they had conflicting information. The solution, agreed by consensus, is to omit the person until such time as the sources agree. The relative wishes all reference to the individual removed. I was under the impression that could be done under a privacy policy (not that I can find an appropriate policy). If there are no grounds under policy for the material to be removed from the talk page (and in future, from preventing their relation from being included in the article), could an admin explain that to the user? ] <sup>(] ])</sup> 07:43, 15 June 2024 (UTC) | |||
:::You and I both have been going at this topic for more than a decade now, and still I sometimes find discussions that take ] to a new level. Given that the two sources in question have vastly different details about this marginally-notable-at-best person, and that these are the ''only'' two sources for a topic that has a well-documented history of fraudulent claims, there's no reason Misplaced Pages should be propagating this. I also, incidentally, note a lot of threats being bandied about on the talkpage, people making them need to stop it ''immediately''. ] (]) 17:42, 15 June 2024 (UTC) | |||
::::Maybe it would better if we tried to be an encyclopedia based on notable topics, rather than the ''Guinness Book of Records''. ] (]) 19:37, 15 June 2024 (UTC) | |||
:::::Alas, there seems to be some disagreement among users as to what "notable" means. ] 20:58, 15 June 2024 (UTC) | |||
::::::I feel like I'm missing something here. The discussion appears to center around a disagreement between sources, and someone claiming to be the descendant of the person written about in those sources is asking us to delete the entire conversation because it is insulting to her ancestor? Is that right? Because if it is I don't see any grounds for being upset at Misplaced Pages about it. ] ] 21:50, 15 June 2024 (UTC) | |||
:::::::Greetings, I asked to delete all inappropriate comments about my grandpa Ilie Ciocan. Later, I deleted my comments because I listed my contact email there so I was worried because it is publicly available. Namely, on the page talking about the oldest people, various comments and arguments appeared where users argued about whether to add or delete grandfather from the list. My family is appalled after reading these comments, a friend of mine sent me a link to this site. I requested the deletion of all comments where my grandfather is mentioned, because I think he did not deserve to have this type of public discussion about his age. As for publicly available sources, there is no disagreement about the date of birth, the confirms that he was born on May 28, 1913, as well as the . Anyway, it doesn't matter to us if he's on the list or not, it's important to us that all comments about him are deleted, it's unacceptable and we feel upset about it, it's humiliating for my sister and I who for over a decade we take care of him, it is very difficult for us, but we will not give up on him. You can see my comment in the change history. https://en.m.wikipedia.org/search/?title=Talk:Oldest_people&diff=prev&oldid=1229004322 | |||
:::::::Sincerely, Camelia Ciocan, Ilie Ciocan's youngest granddaughter ] (]) 06:34, 16 June 2024 (UTC) | |||
::::::::A number of revisions have already been suppressed (if you look in the edit history, the revisions which are doubly stricken are suppressed). These cannot be seen by anyone other than a very small group of trusted editors. Are there still comments present which you regard as problematic? Simply not liking a comment is not grounds for its removal. I have admittedly only taken a cursory glance through the thread but I don't notice anything libelous or otherwise problematic. If you think any content is libelous, your best option would probably be to contact the oversight team (see ]) with the diff links of the comments you think require suppression, or contact Wikimedia (see ]) detailing your concerns. You could post what content you want removed here, but this is a high-traffic noticeboard and the content in question is likely to be seen by yet more people (for example, I would never have come across the comments in question if it hadn't been posted about here). ] <sup>] • ]</sup> 07:49, 16 June 2024 (UTC) | |||
:::::::::@] I'm one of the small group of oversighters and also, as mentioned above, familiar with this topic area. If there's any other concerning material still visible and/or if anything that's been removed is reposted, you can send me an e-mail and I'll remove it. ] (]) 02:48, 19 June 2024 (UTC) | |||
However, as I have learned from it, I will never use multiple accounts anymore and adding controversial content without doing a proper fact-check. I will always listen to users, be constructive and be friendly. I will make sure you will not regret giving me my account back. I would like to work under the account ].}} | |||
== Block review ] == | |||
] (]) 18:12, 15 December 2024 (UTC) | |||
:'''Support unbanning and unblocking''' per ]. ] (]/]) 18:31, 15 December 2024 (UTC) | |||
* Quoting my SPI comment ]: {{tq2|I was torn on this. The IP does not seem to be creating the sort of low-quality BLP stubs that SportsOlympic was. If this were "just" a case of ''block'' evasion, I'm not sure I could justify a block of the IP as ] of any disruption, and would be inclined to either ignore it or block but offer a non-] unblock to the main account. However, Sander.v.Ginkel is ''banned'', and under the SportsOlympic account has caused significant disruption just six months ago. Evading a ban is an inherent harm, as it undercuts the community's ability to self-govern. Furthermore, it would be unfair to the community to allow someone to contribute content, particularly in a DS area as much of the IP's recent edits have been, without the community being on-notice of their history of significant content issues. (And there is still troubling content like ].) I thus feel I would be defying the mandate the community has given me as an admin if I did anything but block here. ... FWIW, Sander, I could see myself supporting an ] unban down the line, although I'd recommend a year away rather than six months.}}That sentiment is what I eventually wrote down at ], which mentions the same principles being relevant in unban discussions. And now that this is before the community, with even more time having passed, I have no problem unbanning: The post-ban edits, while problematic in that they were sockpuppetry, do show evidence that Sander has learned from his mistakes, and thus a ban no longer serves a preventative purpose. Looking back at the one hesitation I mentioned above, I think my concern was that it was an ] violation that seemed credulous of a pro-Russian narrative; but if there's no evidence of that being part of any POV-pushing, then I don't see it as an obstacle to unbanning. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 18:33, 15 December 2024 (UTC) | |||
*'''Support''' per above.] (]) 18:37, 15 December 2024 (UTC) | |||
*:Endorse one account proviso. ] (]) 20:28, 15 December 2024 (UTC) | |||
*I'm a little bit concerned by the sockpuppetry returning earlier this year: ]. However, that is over 6 months ago. I would '''Support''' with the obvious proviso that the user be limited to 1 account and that IP editing may be scrutinized for evidence of ]. — ] ] 20:16, 15 December 2024 (UTC) | |||
*'''Support''' with provisions per above. Worth keeping a close eye on, but they ''seem'' to have understood the problems with their behavior and improved upon it. ] ] <span style="color:#C8102E;"><small><sup>(])</sup></small></span> 07:07, 16 December 2024 (UTC) | |||
*'''Support''' I've previously spoken in favor of the subject as well. ] (]) 09:15, 16 December 2024 (UTC) | |||
*'''Oppose'''. "My biggest mistake that I copied-pasted content from articles to other articles, that led to a BLP violation. " That wasn't the biggest mistake by far. You made extremely negative claims about sportspeople based on internet rumors. Apart from this, the first article I checked on simple, , is way too close paraphrasing of the source. has very sloppy writing, "He started his business alone 1980 built so his horse stable "Hexagon" in Schore. " is just nonsense. Copyvio/close paraphrasing seems to be a recurring problem, has e.g. "Zwaanswijk is regarded as one of the most respected post-World War II visual artists of Haarlem and his work had a profound influence on the local art scene." where the source has "Piet Zwaanswijk was een van de meest gerespecteerde na-oorlogse beeldend kunstenaars van Haarlem. Zijn werk had een diepe invloed op de lokale kunstscene". I don't get the impression that the earlier issues have disappeared. ] (]) 11:45, 16 December 2024 (UTC) | |||
*'''Support''' User seems to have recognized what he <!-- before someone complains about my use of the gender-neutral he, this user is male per what they've configured settings to be --> did wrong, has edited constructively off enwiki. ''']]''' 18:52, 17 December 2024 (UTC) | |||
*<s>'''Weak Support''', the crux of the issue was three-fold: creation of low-quality sports stubs (including what Fram said), persistent IDHT when asked to fix them, and sockpuppetry. I recall I identified the SportsOlympic sock in a tangential ANI thread a couple of years ago. It appears he has edited constructively elsewhere. I would like to see a commitment to one-account-only and a commitment respond civilly and collaboratively when criticized. ] (]) 15:45, 18 December 2024 (UTC)</s> | |||
:*'''Oppose''', I am convinced by the further discussion below that S.v.G is not a net positive at this time. ] (]) 14:11, 24 December 2024 (UTC) | |||
* '''Support'''. Completely support an unblock; see my comment ] when his IP was blocked in April. ] (]) 17:25, 18 December 2024 (UTC) | |||
*'''Oppose'''. Sander and his socks created literally thousands of poorly-written and/or potentially-copyvio pages on (very frequently) non-notable sports topics. I don't see evidence in his Simple Wiki contribs that his writing has improved, and for someone with his history of non-notable subject choices I would want to see ''clear'' evidence that these creations are supported by WP:SUSTAINED, non-routine, IRS SIGCOV. Articles like may well be on notable competitions, but with content like {{tq|On 20 March the Women's Fencing Club gave an assaut, in honor of the visit of the Dutch team. As seen as an exceptional, mr. de Vos was a the only man allowed to visit the women's club.}}, and all sources being from 20 or 21 March 1911, we can be confident that verifying and rewriting the mangled translations and searching for continued coverage will be a huge pain for other editors. And going from the en.wp AfD participation I'd also anticipate the same combativeness and time wasted explaining P&Gs to him in that area as well. Given the volume of his creations, I don't think it is fair to foist all the extra work that would come with overturning the ban onto other editors without a much more thorough evaluation of his Simple Wiki contribution quality. ] (]) 02:34, 19 December 2024 (UTC) | |||
* Currently '''oppose'''; open to a change of view if some explanation and assurances are given with regard to the points Fram raises. There is no point in unblocking a problematic editor if it appears that they may well continue to cause issues for the community ~ ''']'''<sup>''']''']</sup> 12:59, 19 December 2024 (UTC) | |||
* '''Support''' but keep an eye on contributions off ENWP. ] (]) 17:11, 23 December 2024 (UTC) | |||
*:{{yo|Ahri Boy }} Not sure we are concerned with contribs off ENWP. ] (]) 18:27, 23 December 2024 (UTC) | |||
*::He might appeal on Commons later if the appeal here is successful, so there would be a cooldown before doing there. ] (]) 01:15, 24 December 2024 (UTC) | |||
*'''Oppose''' per Fram on close paraphrasing, JoelleJay on sourcing/writing quality, and my own observations on English-language proficiency (I see very recent sentences like "]"). At an absolute minimum I would need a restriction on article creation (to prevent the low-quality mass creation issues from recurring), but these issues would be a problem in other areas too. I think continuing to contribute to simple-wiki and nl-wiki would be the best way forward. ] (]) 01:34, 24 December 2024 (UTC) | |||
*:He was once blocked on NLWP for the same sockpuppetry as here before. I don't even know that he may be offered SO there. ] (]) 10:16, 24 December 2024 (UTC) | |||
*::See . ] (]) 10:22, 24 December 2024 (UTC) | |||
*'''Oppose'''. Like Fram, JoelleJay, and Extraordinary Writ, I have concerns about their competence with regards to copyright, notability, and simple prose writing. I think an unblock is likely to create a timesink for the community, who will be forced to tie one eye up watching both of his hands. ♠]♠ ] 08:41, 24 December 2024 (UTC) | |||
* Come on – it's been nearly ''seven years'' since the ban – why can't we give another chance? His articles from when he was an IP seemed quite good (and much different from stubs which seem to have been the problem), from what I remember (although they've since been G5'd). ] (]) 16:35, 24 December 2024 (UTC) | |||
*:S.v.G. needs to be reevaluated. He needs to clarify that the purpose of return is genuine, constructive, and one account only. He hasn't made any contributions to Commons because he was blocked. ] (]) 19:55, 24 December 2024 (UTC) | |||
*:: I think saying that {{tq|I will never use multiple accounts anymore}} and that he wants to {{tq|make constructive content}} would indicate that {{tq|the purpose of return is genuine, constructive, and one account only.}} ] (]) 19:59, 24 December 2024 (UTC) | |||
*:::For the meantime, he should stay at Simple and NLWP for another six months to make sure no suspicions will be made before appealing under SO. ] (]) 20:07, 24 December 2024 (UTC) | |||
*:But it's only been three years since he was mass-creating non-notable stubs with BLP violations and bludgeoning AfDs with his SportsOlympic sock. He then edited extensively as an IP, got banned for 18 months, restarted within two weeks of that ban ending, and made another 1000+ edits until his latest IP ban in spring 2024. After which he immediately invoked the (laxer) equivalent of the SO on nl.wp... ] (]) 21:07, 24 December 2024 (UTC) | |||
*:: And he admits that he was {{tq|too focused on quantity, rather than quality}}, apologized repeatedly, and his creations as an IP showed that he was no longer focused on {{tq|mass-creating non-notable stubs}}. ] (]) 21:18, 24 December 2024 (UTC) | |||
*'''Support''' With the above mentioned provisions. Seems like a genuine, good faith, attempt to ]. <span style="font-family: Trebuchet MS;">'''] ]'''</span> 04:44, 25 December 2024 (UTC) | |||
*'''Support''' - Like a lot of behavioral issues on this site, I think it all stems back to the general public seeing this site as an all-inclusive encyclopedia and some users here seeing the site as a celebrity encyclopedia. If the user becomes a problem, action can be taken again. Let's see how it goes. ] (]) 20:03, 25 December 2024 (UTC) | |||
*'''Oppose''' per Fram and PMC. <span style="white-space: nowrap;">—] <sup>(]·])</sup></span> 18:52, 29 December 2024 (UTC) | |||
*'''Question''': Is SvG the same person as {{U|Slowking4}}? There has been an odd connection between the two in the past; I think it was first noted by ]. ☆ <span style="white-space:nowrap;font-family: Papyrus">]</span> (]) 22:58, 29 December 2024 (UTC) | |||
**No. ] (]) 23:01, 29 December 2024 (UTC) | |||
*'''Support'''. This appears to be a good-faith attempt at a return, and looking through the commentary here I don't see evidence to suggest continuing the ban and block are preventative. - ] <sub>]</sub> 23:44, 4 January 2025 (UTC) | |||
*'''Oppose''' basically per ], particularly the evidence that their MASSCREATE/socking/evading behaviour was carrying on as recently as spring 2024. If/When they return, it should be with the requirement that all their articles have to go through AFC and that they won't get ] without a substantive discussion (i.e., no automatic conferring of autopatrolled - they have to request it and disclose why this restriction is in place when doing so). ] (]) 16:46, 8 January 2025 (UTC) | |||
*It does look like a good-faith desire to return and work on Misplaced Pages. And I would just want to add that Misplaced Pages needs such a fruitful article creator. Especially since ] was severely trimmed several years ago, and probably thousands of sportspeople articles have since been deleted.<br />'''Support'''. (I am not an admin, so I am not sure I can vote. I can see some non-admins voting, but I'm still not sure.) --] (]) 14:26, 10 January 2025 (UTC) | |||
*'''Conditional support unblock''' (non-admin vote- if I'm not allowed to vote then please just unbold this vote): add editing restriction for them to use ] for article creation, and this restriction can be reviewed in 6-12 months if their article creation has been good. Their article mass creation required one of the largest cleanup jobs I have seen on here, and we certainly wouldn't want the same mass-created quasi-notable articles created again. ]] (]) 17:05, 10 January 2025 (UTC) | |||
*'''Support''' I can't repeat what Beaniefan11 say enough: "Come on – it's been nearly ''seven years'' since the ban – why can't we give another chance? And he admits that he was {{tq|too focused on quantity, rather than quality}}, apologized repeatedly, and his creations as an IP showed that he was no longer focused on {{tq|mass-creating non-notable stubs}}." This should assuage any doubt in the mind of the reviewing administrator. ] (]) 15:01, 13 January 2025 (UTC) | |||
*'''Oppose''' Claims of "It's been seven years!" fall on deaf ears when you find out he's been socking all along and as recently as a year ago. Fram and PMC have good points as well. Show some restraint and understanding of your block and ] is yours. ] (]) 23:11, 17 January 2025 (UTC) | |||
== Spider-Man: Beyond the Spider-Verse - draft article about a future film seems to be a long-term draft == | |||
{{userlinks|Jamiesonandy}} | |||
I have not come across a situation like ] before. Maybe this is fairly common and I have just missed it. | |||
Blocking admin: {{adminlinks|Orangemike}} | |||
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. | |||
The blocked user is clearly an elderly person who misunderstands what Misplaced Pages is. It was explained to him at the help desk, and he stopped editing. '''Ten hours later''', Mike indef blocked him. I feel like this is far from the first time I have seen Mike come late to a situation and substitute his own judgement for that of others who already adressed the situation. ] ] 21:36, 15 June 2024 (UTC) | |||
:'''Egregiously bad block''' What the hell? Not a single warning on the user's talk page, not a note from the admin prior to jumping to a block, and an indef block at that? For a newbie who seems confused and needs some direction? Have we forgotten ] and ]? I daresay I hope {{u|Orangemike}} is able to defend their actions, because I'm not seeing any reason they should be blocked indefinitely for a few questions on the Teahouse and Help Desk (two places designed for people to ask for..wait for it...help!). Not to mention, Orangemike mentions the editor being "belligerent" in the block reason, which I see absolutely zero evidence of, and the rest of their block reason of ] seems to be a ''very'' unsubstantiated position to take. ] <sup>(]) </sup> 22:39, 15 June 2024 (UTC) | |||
::The belligerency was when he '''demanded''', ''I asked a question; '''where is your answer?''''' The guy was just not getting it, was using both the Teahouse and Help Desk as general information sources for UK banking questions, and clearly was not going to accept that this was not the place to seek help on this question. <!-- Template:Unsigned --><small class="autosigned">— Preceding ] comment added by ] (] • ]) </small> | |||
: It wasn't just one out of place question. It was several on both the Teahouse and the Help Desk, and it didn't seem like the user was ready to give up asking. ] (]) 23:27, 15 June 2024 (UTC) | |||
:Definitely not a good block. I've taken a look at a number of Orangemike's NOTHERE blocks (I didn't look at others), and there were a number of very bad blocks: | |||
:* ], one-edit no warning block | |||
:* ], another one-edit no warning block | |||
:* ], user who stopped editing after warning, blocked more than a day later | |||
:* ], no warnings whatsoever; is not a good deletion either | |||
:Nearly half of the blocks I looked at were like this. Orangemike ''really'' needs to stop doing these no-to-little-warning blocks. —] (] • ]) 23:52, 15 June 2024 (UTC) | |||
:::If my colleagues really feel that I'm being quick on the trigger, I will accept your collective judgement and take my trouting like a ''mensch''; but I genuinely doubt that any one of these accounts had any intention of contributing to our project in the way that somebody like Sideways does every day. Two spamming accounts with spammy usernames, one poop joke, one racial epithet username, and our confused British gentleman who thinks we can put him in contact with a bank account dead for over half a century...... --] | ] 00:37, 16 June 2024 (UTC) | |||
::::I haven't looked into any of your blocks and so have no opinion whether or not you have acted appropriately, but I would say that the fact that you {{tq|genuinely doubt that any one of these accounts had any intention of contributing to our project}} does not override Misplaced Pages policy, specifically the policy on blocking. The intention behind Misplaced Pages was to create an encyclopaedia that anyone can edit. Policies which temporarily (even indefinite blocks shouldn't be considered permanent) remove an individual's ability to contribute to the project exist only to limit damage and disruption to the project and should generally be considered a last resort, not the first tool you pull out. I am not and have never been an administrator on this or any other Wikimedia project, but I have been an administrator or bureaucrat on multiple MediaWiki installations through my work and can tell you from experience that biting the newcomers in such a way may temporarily put a stop to vandalism or disruption but long-term only harms the project. ] <sup>] • ]</sup> 02:08, 16 June 2024 (UTC) | |||
::None of these 4 blocks make any sense, and while I think Mike's explanations are genuine, this is a base breach of the blocking policy, and at least a couple of those user's blocks are concerning. The first, for ], based on the contributions looks like they need to be redirected to a different language content project (Google tells me it's Georgian?). The second user, ], just needs an extra dose of the introduction to Misplaced Pages, not a block for heaven's sake. The third user, ], based on their contributions just seems like they need some help getting started, something the Growth Tools like mentorship are supposed to help with. Finally, the fourth user, ], is the only one I'll say should probably be blocked, but not for ]. If anything they should have been blocked for a UPOL violation, but not for their contributions or whether they are HERE or not. To be quite honest though, their edits are just to their user page then a question to their mentor. Of those edits to their userpage, they didn't seem to have any malicious intent either. In ''addition'', they appear to have responded to the block notice, stating they would {{tqq|learn from it}}, which isn't typically a trait associated with blocks for ]. On just a closing note as well, the deletion, unless something else had been added that was horridly obscene other than the page creation with "Woo!", I would say that's a violation of ] and the deletion policy in general. Based on the API result , there doesn't appear to be any other edits to the page, though. Just out of curiosity, {{u|Ingenuity}}, would you (or of course any other administrator) be able to confirm if there's still a deleted revision on ]? If there is, I wonder if it would be possible to restore that revision, as it doesn't appear to be a proper use of the deletion tool. ] <sup>(]) </sup> 01:12, 16 June 2024 (UTC) | |||
:::I remember encountering {{user|Mrpoopbenji}} through ], and discovered that all of their edits were created by a ]. Ther sandbox was deleted for this reason. –] (]]) 17:55, 16 June 2024 (UTC) | |||
:::Someone with a username that's slang for "white nigger" needs only a swift kick in the ass out the door. I'd have blocked on sight as well. As to the others: one is an obvious username violation, with another the text being in Georgian is the least of the problems given it was an obvious attempt to hijack an article with blatant spam about an entirely unrelated subject, and the last was as flagrant a case of ] as it gets. ] (]) 06:10, 19 June 2024 (UTC) | |||
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. | |||
* Just wanted to point out that the blocked editor did not stop editing once it was pointed out (not only on ], which they may have not seen, but also on Jun 14th at , , at , and at ) that wikipedia, including the Help desk and Teahouse, was not an appropriate place for their query. Rather, 20 minutes after that last response, the editor reposted the question asking for legal/financial advice . Secondly, while the editor said that they had "" at least this account seemed to be dedicated to a single purpose that was not that of ]. Finally, as {{u|Girth Summit}} on this page a short while back, albeit in a different context, one motivation for applying an indef block is to get assurance from the blocked editor that the problematic behavior will not be repeated. | |||
:Hence, while I understand that the Jamiesonandy block was still a judgement call, and that it is natural to feel sympathy for a senior citizen in distress, I can also see Orangemike's thinking in applying the NOTHERE block. Cheers. ] (]) 01:39, 16 June 2024 (UTC) | |||
*'''Comment''' I've noticed for years that Orangemike is quick to block, often without any talk page warnings but I generally have trusted their judgment. I'd ask them to ease up on the trigger finger and try communicating with an editor before laying down the ban hammer first. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 03:34, 16 June 2024 (UTC) | |||
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. | |||
:Generally speaking, in my view, a NOTHERE indef block is admissible (although not necessary) if none of the user's edits indicate an ability or intent to improve our articles. This seems to be the case here. It's then up to the user to convince us, in an unblock request, that they are indeed able and willing to edit constructively. <small><span style="border:1px solid black;padding:1px;">]</span></small> 08:27, 16 June 2024 (UTC) | |||
:A quick show of hands: y'all ''do'' realize that the "reason" you fill in at ] isn't just for the entry in the block log, but is ''shown to the user every time they try to edit'', yes? ] (]) 22:22, 16 June 2024 (UTC) | |||
Is anyone more familiar with how we got here? Anyone got any arguments for or against applying semi, EC or full protection to the draft and its talk page? | |||
*The thing here for me is that the Teahouse and the Help Desk are exactly where we want users to go when they are lost or confused as to the purpose of Misplaced Pages. I don't think anyone is defending this users actual edits, but he hadn't posted anything in many hours and the situation seemed to have settled itself when Mike just indef blocked out of nowhere. Mike, like myself, has contributed for many years at ] Personally, I don't even think most of the thousands of accounts I've blocked at UAA were here in bad faith, they, like this person, just didn't get it and tried to use Misplaced Pages in ways it isn't intended to be used. So, they use an ] and write upa draft article on said organization, and the usual response is that we delete the draft and ''soft'' block the user, explicitly allowing them to just start a new account and try to edit within the rules. Looking at some of Mike's blocks, he treats "being lost and confused on help forums" the same way most admins treat "actively disrupting article space." I just don't think being clueless in WP space is what NOTHERE hard indef blocks are for, it is for people who come here to push the ''content'' to suit their own needs, not for people who ask deeply misguided questions. ] ] 18:31, 17 June 2024 (UTC) | |||
*:I'd add that if you look at the language at ] there's a lot of wording like "''long-term history...Extreme lack of interest in working constructively...Major conflicts of attitude, concerning Misplaced Pages-related activity...''" and so on. It doesn't say anything aboout "asks clueless questions at help forums, because help forums are there, at least in part, to help clueless users get some clue. ] ] 20:57, 17 June 2024 (UTC) | |||
*::I get that in general, but this particular account was going well beyond that. I count 4 separate instances of being told, in various ways, that Misplaced Pages is not a forum for handling personal bank squabbles that date back to something from 1950s British probate court (!); to respond to said warnings with ] tells me that, in a very literal sense, this user was not here to ''build an encyclopedia''. I'm American and even ''I'' could point out that a solicitor, not an online community devoted to building an encyclopedia, would be who to ask these questions. ] (]) 06:35, 19 June 2024 (UTC) | |||
<small>'''Edit:'''</small> Anyone got any thoughts on the concept of having a draft article for a film that doesn't meet ]? | |||
== Page == | |||
] (]) 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. ]]<sup>]</sup> 00:43, 29 December 2024 (UTC) | |||
::People say that on the draft's talk page every so often and get rebuffed. Maybe you can be more persuasive, but the general argument is the existing animation was created for "Spider-Man: Across The Spider-Verse" before it was split into two films and no "final animation" has begun on this film. ] (]) 01:03, 29 December 2024 (UTC) | |||
:::Are they basing that claim on any reliable source as evidence? Since what exists in that draft currently with reliable sources clearly indicates work has started. ]]<sup>]</sup> 01:11, 29 December 2024 (UTC) | |||
::::Hi. I'm the editor who has requested the protection for this draft. Per ], final animation or voice recording are the requirement to move a film draft to the mainspace. Final animation is different from standard reels being produced, which as sourced, is currently what this film has produced while no voice recording has occurred. It seems to still be very early in development, and much of the earlier work when this was the second part was reportedly scrapped (as sourced in the draft). I do not believe the mainspace viability ought to be discussed here as that is more for the draft. As for the protection request, it appears to be the same person making these disruptive comments which have become unnecessarily excessive and are detracting from the content of the draft itself. I requested protection (initially as ECP though semi works for the talk) because these comments have not benefitted any actual constructive progress and have largely ranged from the IPs attempting to enforce their own opinions about the delays and trying to remove sources they don't like, which has been ongoing since the end of October. As a draft, not many other editors are editing this, so it becomes quite unrelenting and tiresome to deal with these repeated disruptions. Glad to see this has garnered more attention. ] (]) 01:20, 29 December 2024 (UTC) | |||
:::::{{tqq|Per WP:NFF, final animation or voice recording are the requirement to move a film draft to the mainspace}} ...I'm ''pretty sure'' that BtSV meets ] already, regardless of the state of production, and ''that'' should be the main factor. - ] <sub>]</sub> 03:49, 29 December 2024 (UTC) | |||
::::::I have no problem with the draft being moved, this is just not the normal route to do so and typically NFF is followed for film articles, but I digress. I do caution that this article {{em|could}} be susceptible to further unconstructive comments in the mainspace, but that is a price I'm willing to handle. I can make the move as needed, no worries, I am primarily concerned about these type of comments continuing and if any protection is necessary to prevent or temporarily postpone them from continuing. ] (]) 05:18, 29 December 2024 (UTC) | |||
:There doesn't appear to be enough disruption to the draft page to justify protection at this point. Draft talk definitely should get semi-protection. ] (]/]) 00:45, 29 December 2024 (UTC) | |||
::Really? That seems excessive for a few FOURMy IP comments (likely from the same person). If they continue with it, block the IP, maybe. Protecting talk pages should really be a last resort. ] (] | ]) 00:58, 29 December 2024 (UTC) | |||
:Some people overly use NFF to block any film article that has not confirmed start to production, which is really a bad black/white approach. ''Most'' films prior to production are not notable or may not even happen when they are first hinted at, and thus it is absolutely appropriate to use NFF to hold back on a standalone until production starts. But then you have some exceptional cases like this (the 3rd of the animated Spider-Man movies that have earned a massive amount of money and praise, with a lot of attention already given to the film even before production) as well as my own experience with ] which deals with a film that has numerous delays and other incidents that its still nowhere close to production, but its journey that way is readily sourced. NFF should not be used to block creation of articles on films that have this much detail about the work that is otherwise suitable by notability guidelines. For this specific article on the Spider-man film, I see no reason why it could not be in main space at this point as to avoid the whole draft problem.<span id="Masem:1735450356365:WikipediaFTTCLNAdministrators'_noticeboard" class="FTTCmt"> — ] (]) 05:32, 29 December 2024 (UTC)</span> | |||
::Yeah, there is a point to be made that even if this final film somehow never finished production, it would still be notable because of the coverage of its attempted production history. There's several films (and video games, among other cultural apocrypha) that meet that notability requirement, even without ever actually having been completed and released to the public. ]]<sup>]</sup> 05:36, 29 December 2024 (UTC) | |||
:::Indeed, a number of aborted films projects are notable exactly ''because'' they wound up in ]. ] is a film about my personal favorite never-got-made film. ] ] 02:59, 30 December 2024 (UTC) | |||
Noting here that Trailblazer101 moved the article from draft space to main space at 22:44, based on the discussion here and ]. I have not seen any objections to that move since it was done. I have not seen any more speculative or forumy edits recently. There is a good chance they will come back, but if they come back in a serious number the article and/or talk page can be given an appropriate level of protection at that point, or, if the responsible IPs/accounts can be blocked. I think it is probably time to close this discussion. ] (]) 10:56, 30 December 2024 (UTC) | |||
:{{nacmt}} I see an ] that began on May 30 with heavy involvement from this user and from {{user|زكرياء نوير}}, where all sides are making unsourced changes to statistics. Actually, almost all of the statistics on this page are unsourced. –] (]]) 17:44, 16 June 2024 (UTC) | |||
:The IP has made three unconstructive and uncivil comments on the talk today (see , and they show no signs of stopping. ] (]) 18:03, 31 December 2024 (UTC) | |||
::Currently the page is good now, someone deletes the numbers every time, it should be closed ] (]) 17:56, 16 June 2024 (UTC) | |||
:: |
::I have blocked that IP. I note that it is possible that some of the other IPs could be the same users and so will block other IPs and/or apply semi-protection if this continues (or encourage others to do the same if I am away from my computer). ] (]) 11:51, 1 January 2025 (UTC) | ||
* {{tq|Anyone got any thoughts on the concept of having a draft article for a film that doesn't meet WP:NFF?}} Using draftspace to incubate articles on subjects that are not yet notable but almost certainly will be—unreleased films, upcoming elections, sports events, the next in an "X by year" series, and so on—is a common practice and has been as long as I can remember. As such it's listed at ]. – ] <small>(])</small> 12:04, 1 January 2025 (UTC) | |||
:::Do not UNDER ANY CIRCUMSTANCES edit another contributors' post like this. ] (]) 18:12, 16 June 2024 (UTC) | |||
**Thank you. ] (]) 15:01, 1 January 2025 (UTC) | |||
::::The user زكرياء_نوير posted the following under ]: {{tq|Yes, there is sabotage every time the page has to be closed}}. So both users are accusing the other of vandalism, and that's even worse than the lack of sourcing. –] (]]) 18:12, 16 June 2024 (UTC) | |||
::::Like accidentally editing the template they intended to copy to edit their own comment? That's what it looks like. – ] (]) 19:59, 16 June 2024 (UTC) | |||
I think it makes sense to archive all threads in ]. They are all either forumy or else asking when the page can be moved to article space, which is no longer relevant since it is in article space. ] (]) 20:06, 3 January 2025 (UTC) | |||
:I've updated the archive bot on that talk age to act on 1 month old threads. Should get rid of half of the ones on there when it runs next and the rest will follow soon enough. I've always thought 6 months was way too long of a default archive policy. ]]<sup>]</sup> 20:11, 3 January 2025 (UTC) | |||
::Yeah, I've always felt 90 days is sufficient for default archival purposes. If no one has contributed to a discussion in three months, it's a dead discussion. — <b>]:<sup>]</sup></b> 18:41, 10 January 2025 (UTC) | |||
== 43.249.196.179 (again) == | |||
== troll at ] == | |||
{{Atop|The IP is now blocked.--] (]) 14:47, 17 June 2024 (UTC)}} | |||
This person verbally attacked me, but I was clearly discussing this in a friendly manner, and I did not attack back. I remained friendly from beginning to end. ] 🇨🇳❤️ <span style="font-size:smaller;">(])</span> 04:43, 17 June 2024 (UTC) | |||
See their previous thread here, ]. Continuing to disrupt and remove categories without explanation, decided to after restoring edits without any talk page discussion, and has now moved onto and by removing categories without said user's permission, calling my reversions 'vindicitive' and now considering me their personal 'nemesis' because they don't understand why they're being reverted. <span style="font-family: Roboto;">''']''' <span style="color:#00008B">•</span> <small>''(])''</small></span> 21:16, 31 December 2024 (UTC) | |||
:First, you are required to notify the editor about this discussion. I have done that for you. Second, yes, I agree is definitely a personal attack, and is worthy of a block.]] 05:29, 17 June 2024 (UTC) | |||
:] is not familiar with some of the WP policies and guidelines especially ] and ]. Also, his obfuscated username is somewhat fustration and is not conducive to efficient editing. ] (]) 21:21, 31 December 2024 (UTC) | |||
:]: Editing user pages has no 'hard policy' prohibition, as this is a wiki. 'End of discussion', seriously? Also see ]. Then, ] is a container category, which clearly says it should only contain subcategories. Even I don't understand why they're being reverted. -- ] <sup>]</sup> 22:08, 31 December 2024 (UTC) | |||
::] seems to be unaware of many of the WP polices and guidelines. ] (]) 08:03, 3 January 2025 (UTC) | |||
:::I've been here nineteen years so obviously I do and I apologize if as mentioned I'm more aggressive about userspace being in control of the user themselves. That said I'm no longer engaging with you or any of your edits as you're now ] and trying to troll some kind of response out of me (and doing the same for Liz, who has the patience of a saint), which you won't get. Understand our guidelines or get blocked. If anyone uninvolved would like to close this, please do so. <span style="font-family: Roboto;">''']''' <span style="color:#00008B">•</span> <small>''(])''</small></span> 17:16, 3 January 2025 (UTC) | |||
::::Length of time on WP is not a measure of how familiar an editor is with policy and guidelines. Your previous comments show that you are unfamiliar with some of them, but to be fair, it is impossible to know all of them. There are a lot of editors that do not know a lot of the policies and guidelines. THere are content disputes and corrections and reverts happening all the time because of inexperienced editors. | |||
::::I am not trolling. I just want WP to be much better than it currently is. ] (]) 19:50, 3 January 2025 (UTC) | |||
::Adressing that final point, I have ] about ] to either remove the ] banner tag or give special sanction to empty user pages from that main category. ] (]) 21:08, 3 January 2025 (UTC) | |||
:::Category:Wikipedians is at a level of the hierarchy that there should be nothing in it, which is why it is a container category. The contents of it have been added by editors who do not understand how WP works and do not realise that it is a container category. You proposal is not needed. ] (]) 22:07, 3 January 2025 (UTC) | |||
:'''Comment''': ] was cited in ] (a sandbox used for drafting a larger edit needing discussion, where categories were copied along with the rest of the article's content). (] is mentioned explicitly in that guideline.) ] (]) 02:49, 1 January 2025 (UTC) | |||
::Whatever the case, user sandbox space is sacred and unless you have permission to edit there, you don't touch them, that's an unwritten rule. Mathglot certainly . That's the main issue here and if I was wrong on the cats so be it, but they should not be playing in sandboxes they shouldn't be in. <span style="font-family: Roboto;">''']''' <span style="color:#00008B">•</span> <small>''(])''</small></span> 02:54, 1 January 2025 (UTC) | |||
::: Just to clarify: I have no qualms about others making improvements to pages in my users space—which belong to the community and are not "mine"—as long as they are improvements. That said, IP's edits in my userspace look like vandalism to me. ] (]) 03:04, 1 January 2025 (UTC) | |||
:::User namespace is not "sacred". And if there is an unwrittten rule then it is not a rule that needed to be adhered to. Also ]. To be a good editor it is important to be familiar with policis and guidelines. ] (]) 08:03, 1 January 2025 (UTC) | |||
:It was not a "gravedance". I was pointing out to you that other editors dont agree with you edits. ] (]) 09:15, 1 January 2025 (UTC) | |||
I only just noticed this AN discussion, after placing ] at User talk:43.249.196.179 about vandalizing a Draft template in my user space. Their edits seem somehow to be related to categories, but near as I can guess from their edit summary ], they also had some inscrutable complaint about me using my userspace as "social media". Maybe interested parties here will understand what they are talking about, because I certainly don't. As of this point, I cannot tell if they are well-meaning, but highly misinformed and uncomprehending, or if they are simply trolling everyone. I suspect the latter, but am willing to be proved wrong, especially if enceforth they stick to ] and ], instead of ignoring advice given previously and ]. ] (]) 03:00, 1 January 2025 (UTC) | |||
: 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) | |||
:::Honestly, whether that was a Joe Job or not, your behavior is indistinguishable from trolling & deserves a block. — <b>]:<sup>]</sup></b> 18:45, 10 January 2025 (UTC) | |||
== Incivility at ] == | |||
@] 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) | |||
:This looks to me like it's covered by ]. ] ] 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 {{tq|I am stating a fact.}} and you take offence to that, then you might need to back away from the discussion for a few days. ] ] 02:47, 2 January 2025 (UTC) | |||
::{{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) | |||
:This seems entirely unnecessary. ] (]) 03:13, 2 January 2025 (UTC) | |||
::Can you elaborate on which aspect of {{tq|this}} you are referring to that you believe is unnecessary? ] ] 03:55, 2 January 2025 (UTC) | |||
:::By this, I mean bringing the issue to ANI. If I owe anyone an apology, I stand ready to give it, but @] hasn't really been involved in the discussion until very recently and has already escalated it here. ] (]) 03:59, 2 January 2025 (UTC) | |||
::::It doesn't matter how much someone has been involved in a discussion. If there's misconduct that's not clearly going to get resolved on its own (which I'm not confident saying either way here), then it's a public service, even a responsibility, for an editor to report it. ] (]) 05:58, 2 January 2025 (UTC) | |||
::::@] you can see my initial assessment of the situation above. However, I will say uninvolved editors are welcome to bring valid concerns to ANI. It is often far more helpful when someone outside of the situation brings it up here as it ends up being far more neutral. I also would suggest that you might also be too involved right now and need to back away for a few days. The biggest reason is that I believe you read right past Animal lover's and my response which ''basically didn't find you doing anything wrong''. I suggest that a cooling off period might be good for you as well. Not because you're currently doing anything wrong (because that conversation would look quite different), but rather that you're likely too invested in this topic right now to see rationally and objectively. ] ] 06:18, 2 January 2025 (UTC) | |||
:::::It was not my intent to ignore those assessments, and I understand what you've said as far as uninvolved editors raising such issues (real or perceived). ] (]) 19:26, 2 January 2025 (UTC) | |||
::::Also, as a note, this isn't ANI... - ] <sub>]</sub> 07:09, 2 January 2025 (UTC) | |||
:Infact I don't know why such a simple infobox change discussion will resulted in endless arguments. And it happened in mutiple pages, like this ], this ], and now this Azerbaijan Airlines crash case there. And I'm afraid there would be other arguements in previous pages. | |||
:But to be honest, I think I also have some responsibilities on this endless situation: I have known what to do to deal with such major changes, but I didn't really take any action. ] (]) 07:14, 2 January 2025 (UTC) | |||
::The whole "Accident vs Crash" thing has been going on for a while now. It pretty much goes nowhere every time. DEB gives a whole bunch of reasons why "accident" should be avoided, AWF gives a whole bunch of reasons why "accident" is perfectly fine, and it all repeats with every new ] article. I just recommended on DEB's talk page that they try to seek a wider consensus to break this endless cycle, because I for one am tired of seeing the same arguments over and over again with no progress. - ] <sub>]</sub><span style="color:#6B8E23">\</span><sup>]</sup> 08:02, 2 January 2025 (UTC) | |||
:::Infact you can check the talkpage I provided, you will find such arguments have happened on mutiple pages. ] (]) 08:09, 2 January 2025 (UTC) | |||
::::Since the regular editors in this topic area have proven that they are unable to resolve this utterly trivial terminology dispute among themselves, perhaps the best solution might be to topic ban every consistent advocate of "accident" and to topic ban every consistent advocate of "crash" from all articles about airplane mishaps, and let entirely uninvolved editors make a reasonable decision. Because endless bickering among entrenched advocates is disruptive. Topic bans could then be lifted on editors who explicitly agree to ] and drop the terminology issue forever. ] (]) 08:25, 2 January 2025 (UTC) | |||
:::::It's less "unable to resolve" and more "Dreameditsbrooklyn argues that using 'accident' is original research because the sources use 'crash'" and I wish I was joking. Your modest proposal probably ''would'' get some kind of result though! - ] <sub>]</sub> 08:27, 2 January 2025 (UTC) | |||
:::::Infact I have already suggested to delete this controversial value ], since it have not much actural use to show, and mostly have the same contents with the "Summary" value. And ironically, it has showed the available value on the doc page, but the example they showed on simply violate it! But since then nobody really talk about it yet. ] (]) 08:34, 2 January 2025 (UTC) | |||
:::::As someone who has consistently been on the side "accident is fine" of this argument (there really isn't an "accident/crash" binary here, just whether "accident" is original research), I think that's a bit extreme. I laid out a ] on DEB's talk page, which should hopefully help resolve the issue once and for all without the need for more drastic measures. - ] <sub>]</sub><span style="color:#6B8E23">\</span><sup>]</sup> 09:20, 2 January 2025 (UTC) | |||
:::::Respectfully, the descriptions aren't trivial. A "crash" describes what happened. An "accident" implies someone made a mistake with no real culpability. An "incident" implies some sort of interaction or series of events. I have no specific dog in this fight and I don't believe I've voiced any significant opinion on the matter here or elsewhere, but such a description is not trivial when we are trying to be ] in our descriptions. In this particular case, it very much appears that the act was deliberate and the airliner was acceptable collateral damage (in their opinion). At a minimum, it's disputed. As such, "accident" isn't appropriate as it is at least alleged to be a deliberate act or negligence. "Incident" or "crash" would be more neutral. If we say "accident" it implies no one should be blamed and fails ]. ] (]) 22:22, 2 January 2025 (UTC) | |||
::::::] (the context of aviation has been from at least one discussion on the matter). We could go over whether "accident" actually implies no culpability in the context of aviation all day, but this is not the place to do it. As I stated numerous times, we need to formally establish a project-wide consensus about this, and ] is a good place to start. As for this discussion, I think it can be closed as the issue in question is very minor. - ] <sub>]</sub><span style="color:#6B8E23">\</span><sup>]</sup> 22:42, 2 January 2025 (UTC) | |||
:::::::WP:MOS says: {{tq|If any contradiction arises, this page has precedence.}} | |||
:::::::WP:AT, which follows MOS says: {{tq|Generally, article titles are based on what the subject is called in reliable sources.}} | |||
:::::::The very broad majority of RS call this a crash. Why, in this case, doesn't this apply? Because some editors disagree? I am honestly asking. I don't see a policy which overrules MOS here. Also, I'll hold off on any new discussions on this until things have concluded here and at the article talk page, where the same editor who started this discussion opened an RfC on the topic. ] (]) 22:58, 2 January 2025 (UTC) | |||
::::::::I will not continue this off-topic discussion here. If the same perceived problem is happening across multiple ] articles, then the discussion needs to be moved there to finally end the cycle and come to a consensus. - ] <sub>]</sub><span style="color:#6B8E23">\</span><sup>]</sup> 23:06, 2 January 2025 (UTC) | |||
:::::::::I'm not sure WP:AATF is the correct venue to continue the discussion for a number of reasons, which I will spare going into here. ] (]) 23:14, 2 January 2025 (UTC) | |||
::::::::::{{tqq|The very broad majority of RS call this a crash. Why, in this case, doesn't this apply?}} Because ] don't need to "follow the sources", and insisting that they do is ]. - ] <sub>]</sub> 01:38, 4 January 2025 (UTC) | |||
:::::::::::Others have rejected this as the venue to hold this debate, and I will too. I suggest you follow your own advice and drop the stick, at least for now. ] (]) 02:06, 4 January 2025 (UTC) | |||
::::::{{tqq|An "accident" implies someone made a mistake with no real culpability}} No, it does not. The International Civil Aviation Organization, which is somewhat of an authority on the matter, defines an 'aircraft accident' as {{tqq|Accident. An occurrence associated with the operation of an aircraft ..., in which: a) a person is fatally or seriously injured b) the aircraft sustains damage or structural failure c) the aircraft is missing or is completely inaccessible}}. Notice what isn't there - anything about mistakes or culapbility. {{ping|Buffs}} "Accident" is the official internationally recognized term for this sort of occurance, and is entirely neutral in use. Note that "incident" has a very specific term in aviation which is "an occurrence, other than an accident, associated with the operation of an aircraft that affects or could affect the safety of operation." {{ping|Dreameditsbrooklyn}} I'd suggest you ] and stop pushing this ] ]. - ] <sub>]</sub> 23:51, 2 January 2025 (UTC) | |||
:::::::Why do you think this jargon use should take precedence over the common meaning of the word? The word "accident" can be used in (at least) two senses, one of which involves a lack of intention -- the fact that the ICAO (who?) says that they use the word "accident" in only one of these senses isn't somehow magically binding on everyone else who uses the word in the context of aviation. Given the choice between a word with two ambiguous senses, one of which inappropriate, and a word that has only one relevant sense, it's obvious that the latter word will be clearer, isn't it? ] (]) 04:12, 3 January 2025 (UTC) | |||
::::::::]. The people whose job it is to establish these things for aviation. It's not the use of one word for the other that I have a problem with. It's the argument that, somehow, using "accident" constitutes original research ''when in fact it is the correct terminology'' - and in fact some of the suggested alternatives are explicitly ''incorrect'' terminology - is the problem. And no, its not "magically binding", but ] in the context of aviation is to refer to ''any'' crash as an "aviation accident", just like how if somebody deliberately rear-ends you in road rage it's still a "car accident" - it isn't ]. - ] <sub>]</sub> 09:25, 3 January 2025 (UTC) | |||
:::::::::Do you think there was a car accident in New Orleans a few days ago? When you appeal to an organization like ICAO for what the meaning of a common word is, you are by definition using jargon. ] (]) 17:58, 3 January 2025 (UTC) | |||
::::::::::When you appeal to an expert for the meaning of a word in the context of what it's being used in, that's common sense. - ] <sub>]</sub> 21:59, 3 January 2025 (UTC) | |||
:::::::::::It’s the very definition of the word jargon! No wonder people are finding you impossible to deal with. ] (]) 18:57, 4 January 2025 (UTC) | |||
::::::::::::]. — <b>]:<sup>]</sup></b> 18:50, 10 January 2025 (UTC) | |||
:::::::::What is "an occurrence, other than an accident..." if "accident" includes "incidents"? Definition you're claiming here doesn't make a lot of sense. ] (]) 19:03, 3 January 2025 (UTC) | |||
::::::::::Accident =/= incident, which I believed was clear. - ] <sub>]</sub> 21:59, 3 January 2025 (UTC) | |||
:::::::::::Incident includes accidents AND intentional acts. ] (]) 18:34, 4 January 2025 (UTC) | |||
::::::::::::Not , but this probably ''is'' something best not continued here I reckon. - ] <sub>]</sub> 18:40, 4 January 2025 (UTC) | |||
::::::I did not bring this up to ] to litigate whether to use "crash" or "accident". If you would like to litigate that, I have started a RfC on the Talk page. I brought this here to ask the admins to discuss whether <u>DEB's and AWF's behavior</u> is worth pursuing administrator action. ] (]) 01:09, 3 January 2025 (UTC) | |||
:::::Since you think this is an "utterly trivial terminology dispute" should I tag you in the RFC at WP:RS when I make it, or not? I don't wish to bother you if it's not important to you. ] (]) 22:31, 3 January 2025 (UTC) | |||
:I know this discussion is about conduct, not about the disagreement which prompted it, but I'll note that the other user named here and who has not responded has since changed instances of the word 'crash' to accident on other entries and has also since been of violating 3RR on the very entry which prompted this discussion. I've agreed to confine any further conversations to the talk page until a consensus is reached, wherever that may be. ] (]) 02:46, 3 January 2025 (UTC) | |||
::On the very entry for a completely different reason regarding the use of the Aviation Safety Network but I concede that whilst I was within the limits of 3RR, it probably shouldn't have gotten to that point in the first place. {{Tq|... since changed several instances of the word 'crash' to accident on other entries}} – The only changes made were either related to a change within the infobox to stay consistent with ] as the occurrence type on the aforementioned article stated {{Tq|Airliner crash}}, or related to changes regarding short descriptions since they were changed to be phrased in a way that is not usually done. It's not like I removed every single mention of the word ''crash'' and replaced it with ''accident''. But back to the main topic, I'm willing to drop the issue as long as it's not an problem to use ''accident'' in articles relating to aviation. ] (]) 03:40, 3 January 2025 (UTC) | |||
Can we close this? The current discussion has next to nothing to do with the original issue and is best continued somewhere else. - ] <sub>]</sub><span style="color:#6B8E23">\</span><sup>]</sup> 19:03, 4 January 2025 (UTC) | |||
:Agreed. An admin got involved and simply continued off-topic discussion. ] (]) 21:33, 4 January 2025 (UTC) | |||
*'''Warn both to drop the stick''', otherwise, no action at this point. ] (]) 15:57, 8 January 2025 (UTC) | |||
*:'''''Hands ] two ]''''' You want to hand them out, or me? ] (]) 16:32, 9 January 2025 (UTC) | |||
== Topic ban appeal == | |||
{{atop | |||
| result = There is consensus against lifting the topic ban at this time. DesertInfo is advised to find areas where they are willing to edit to show a better history prior to revisiting the topic ban in the future. ] ] 15:07, 12 January 2025 (UTC) | |||
}} | |||
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) | |||
*:::I would like to participate in move and deletion discussions. I contributed a lot to ] and I would like to update some place names through move requests. I haven't had issues in that area since 2022. ] (]) 05:24, 12 January 2025 (UTC) | |||
*'''Comment''' - I'd say {{tq|"racial issues broadly construed"}} is actually pretty broad given how much of history/geography is touched by it. I'd also say they do appear to have made an effort to improve, though I'd still like to see more. ] (]) 16:03, 8 January 2025 (UTC) | |||
*'''Oppose''' I want to see some real world effort working collaboratively somewhere else on wp, not just a six month gap waiting it, off wikipedia. There is no evidence here that there has been a change. '''<span style="text-shadow:7px 7px 8px black; font-family:Papyrus">]<sup>]</sup></span>''' 08:26, 11 January 2025 (UTC) | |||
{{abot}} | |||
== Andra Febrian report == | |||
{{atop | |||
| result = HiLux duck has been blocked, and no further action is needed here. ] ] 15:10, 12 January 2025 (UTC) | |||
}} | |||
"Andra Febrian" is disrupting many edits, I have seen many deleted edits by this user, and I would like to report the user for causing many ]s. The edits unreasonably reverted by this user is very disruptive to me, as I only intend for useful contributions. The user has: | |||
- caused many edit wars <br/> | |||
- deleted citations along with deleting correct claims <br/> | |||
- not been cooperative (wikipedia's ]) on many pages that good-] edits have occurred on <br/> | |||
- not explained deletions of citations in a way that other users have been made upset. <br/> | |||
I request that the user is warned. | |||
] <!--Template:Undated--><small class="autosigned">— Preceding ] comment added 22:13, 3 January 2025 (UTC)</small> | |||
:First: the notice at the top of the page clearly says to place new sections at the bottom of the page, which I have now done for you. Second: you need to provide ] for the edits you are complaining about. Third, you were supposed to notify Andra Febrian per the instructions at the top of the page. Another user has done so for you. - ] 00:06, 4 January 2025 (UTC) | |||
:@]: please sign your comments using <nowiki>~~~~</nowiki>, which will add a timestamp. Additionally, I reverted your edits to ] and to ] because you are changing information in articles without citing ]. You must cite sources when you add or change information in articles. ] (]/]) 00:20, 4 January 2025 (UTC) | |||
::] just filed a new complaint at ANEW and made the exact same mistakes as they did here. I advised them to stop posting complaints on noticeboards until they can follow the instructions. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 07:18, 4 January 2025 (UTC) | |||
:::FWIW, I have a feeling that HiLux Duck is a sockpuppet of ], but I am holding back until they give themselves enough rope to hang. Same obsession with defining overall lengths for various car classifications and edit warring at length over them. <span style="background:#ff0000;font-family:Times New Roman;">]]</span> 00:55, 6 January 2025 (UTC) | |||
::::I'm always impressed when editors can recall editing habits of editors that were blocked years ago. I guess I lack the longterm memory to keep track of sockpuppet habits. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 04:14, 6 January 2025 (UTC) | |||
:::::{{ping|Liz}} MrDavr actually got under my skin at one point; otherwise I probably wouldn't have noticed. Thanks, <span style="background:#ff0000;font-family:Times New Roman;">]]</span> 02:04, 7 January 2025 (UTC) | |||
:::::Looking into this {{duck}} (a HiLux ]?) because yeah, this is ''exactly'' the same editing pattern. Same username pattern as a number of MrDavr socks too (car names/variations thereof - ]). - ] <sub>]</sub> 09:49, 6 January 2025 (UTC) | |||
::::::@] - ] (]) 15:23, 6 January 2025 (UTC) | |||
::::Most likely yes, I knew that the his editing patterns matched an old blocked user but didn't remember the name. ] (]) 16:14, 6 January 2025 (UTC) | |||
::::::::It's also interesting to note that HiLux duck's user page claims they've been on Misplaced Pages since 2019, and having compared edits more extensively I've seen enough and gone ahead and blocked per ]. - ] <sub>]</sub> 20:20, 6 January 2025 (UTC) | |||
=== Mr.Choppers warning request === | |||
:: <small> This was (again) posted at the top instead of the bottom; it seems like it is not really a separate issue. ] (]) 01:54, 7 January 2025 (UTC)</small> | |||
User:Mr.Choppers has not followed the ] rules because: <br/> | |||
'''-''' calling me a "nuisance" because of own ] supporting others in ] that have nothing to do with the user. ] ] <br/> | |||
'''-''' responded fairly aggressively to another user (me) without me being aggressive back or starting this edit war <br/> | |||
'''-''' note that he also called me a "sockpuppet of a banned user" without reliable clarification, also biased on that <br/> | |||
'''-''' also note the user had not informed me and used aggression to support own claims. <br/> | |||
<br/> | |||
I would like to inform that this user has unnecessarily used aggression and claimed things not there. Kind regards, ] (]) 2:29, 6 January 2025 (GMT+12) | |||
:Missed this because it was at the top. Very unlikely to have merit and is moot now, given the block. - ] <sub>]</sub> 02:24, 7 January 2025 (UTC) | |||
{{abot}} | |||
== user:Uwappa: refusal to engage with WP:BRD process, unfounded allegation of ] violation, unfounded vandalism allegation == | |||
{{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) | |||
**. I've revoked TPA. - ] <sub>]</sub> 06:59, 13 January 2025 (UTC) | |||
== Kansascitt1225 ban appeal == | |||
{{atop green|result=Appeal successful. There were some murmurings requesting a topic ban from Kansas, but nothing approaching consensus. Of course, ] would be well-advised to be careful not to go back to the behaviors that led to a block in the first place. But in the meantime, welcome back. <b>]]</b> (] • he/they) 19:59, 15 January 2025 (UTC)}} | |||
I am posting the following appeal on behalf of {{user21|Kansascitt1225}}, who is considered banned by the community per ]: | |||
(keeping it short for WP:TLDR) Hi Misplaced Pages community, it has been over 1 year since I edited on Misplaced Pages without evading my block or breaking community rules. I would like to be given another chance to edit. I realized that my blocking was due to my behavior of creating multiple accounts and using them on the same page and creating issues during a disagreement. I was younger then and am now able to communicate more effectively with others. I intend to respect community rules and not be disruptive to the community. I was upset years ago when I mentioned Kansas City’s urban decay and it was reverted as false and I improperly reacted in a disruptive way that violated the community rules. The mistake I made which caused the disruptive behavior was that I genuinely thought people were reverting my edits due to the racist past of this county and keeping out blacks and having a dislike for the county. I also thought suburbs always had more single family housing and less jobs than cities. In this part of the United States a suburb means something different than what it means in other parts of the world and is more of a political term for other municipalities which caught me off guard and wasn’t what I grew up thinking a suburb was.<ref>{{cite web|url=https://slate.com/business/2015/05/urban-density-nearly-half-of-america-s-biggest-cities-look-like-giant-suburbs.html}}</ref> Some of these suburbs have lower single family housing rates and higher population density and this specific county has more jobs than the “major city” (referenced in previous unblock request if interested). This doesn’t excuse my behavior but shows why I was confused and I should have properly addressed it in the talk pages instead of edit warring or creating accounts. After my initial blocking, I made edits trying to improve the project thinking that would help my case when it actually does the opposite because I was bypassing my block which got me community banned to due the automatic 3 strikes rule. I have not since bypassed my block. I’m interested in car related things as well as cities and populations of the United States and want to improve these articles using good strong references. Thanks for reading. ] (]) 04:46, 27 December 2024 (UTC) | |||
{{reflist-talk}} ] (]/]) 21:22, 7 January 2025 (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) | |||
*:] from KC:{{tq2|Yes I can write in paragraphs and list different ideas in separate paragraphs instead of a giant run on sentence.{{pb}}I wasn’t trying to right great wrongs but noticed the contrast of the definition of ] on Misplaced Pages and these communities being described as suburban (meanwhile some of these suburbs verifiably having lower residential to job ratio than the city and also a higher overall population density with some suburbs gaining population during the day due to commuters coming into them). This is essentially why on my case page It says I feel as tho something had to be “fixed”. I thought my edits were being removed simply because people didn’t like this place or some of its past so I felt as tho I was simply being purposefully misled which caused me to not follow proper civility.{{pb}}I just wanted to clarify that these places weren’t only residential and were major employment areas that they sometimes have a lower percentage of single family homes. This to me was always the opposite of what suburban meant, atleast what I learned during grade school and what it says on Misplaced Pages. That’s where the confusion came from. Kansascitt1225 (talk) 06:17, 13 January 2025 (UTC)}} ] (]/]) 02:19, 15 January 2025 (UTC) | |||
*'''Support''' Six years is a long time, and they have shown growth. I do not think what is actually happening here is ], instead they ] and things went downhill from there. I think ] of {{tq|Jackson county being THE central county of the metropolitan area}} (which Misplaced Pages deems urban) {{tq|when you can see in the census reference here there are actually 6 central counties}} (which Misplaced Pages deems suburban) is reasonable. I researched it, but found the concerns are inconsistent with ] page which provides the definition that {{tq|An urban area is a human settlement with a high population density and an infrastructure of built environment. This is the core of a metropolitan statistical area in the United States, if it contains a population of more than 50,000.}} An urban area is the most urban area compared to its surroundings, even though its surroundings are quite dense. I hope this helps. ] (]) 22:54, 12 January 2025 (UTC) | |||
*:I add that their concerns that suburban designation misleads people seem to have merit. It is not the suburban designation that misleads people though, but the definition of suburban itself on the ] article seems to be misleading. I know this is not a place to discuss content, but discuss conduct. But some insight into content can help resolve problems. ] (]) 11:56, 13 January 2025 (UTC) | |||
{{abot}} | |||
== ftools is back! == | |||
I am proud to announce that I have become the new maintainer of Fastily's <code>ftools</code>, which is live ]. And yes, this includes the IP range calculator! ]<sub>]<sub>]</sub></sub> (]/]) 23:12, 9 January 2025 (UTC) | |||
:{{like}} -] (]) 23:15, 9 January 2025 (UTC) | |||
:Note: {{no ping|DreamRimmer}} is now also a maintainer. ]<sub>]<sub>]</sub></sub> (]/]) 15:47, 10 January 2025 (UTC) | |||
:My congratulations/condolences. ] (]) 15:49, 11 January 2025 (UTC) | |||
:So, will ftools be renamed or not? Congratulations. ] (]) 02:32, 14 January 2025 (UTC) | |||
== Block appeal for ] == | |||
{{atop | |||
| status = unblock denied | |||
| result = AKG has withdrawn the request. In any case, I see too many misgivings even on the "support" side to consider an unblock at this time. ] (]) 02:33, 11 January 2025 (UTC) | |||
}} | |||
I am bringing a somewhat unusual unblock request here for broader community input. {{u|Aman.kumar.goel}} has been blocked for more than a year for sockpuppetry (see ]). As you can see in the unblock request at ], they have agreed to a one-account restriction as an unblock condition, and there is no CU-confirmed evidence of recent sockpuppetry. However, {{u|Ivanvector}}, who made that check, is skeptical and has declined to support an unblock. A topic ban from ] and ] were floated as additional possible conditions, but no agreement was reached, and Aman.kumar.goel has requested that their unblock request be considered by the wider community. Their statement is as follows: | |||
:I was blocked for sockpuppetry. There was no doubt throughout the discussion over that. I have agreed to a one-account restriction. However, during the unblock request, a topic ban on me was proposed from ] (WP:ARBPIA) and also from ] (WP:ARBIPA). Though no proper evidence was provided to substantiate such proposals. | |||
:While the proposal to topic ban me from WP:ARBPIA does not make any sense because I haven't even edited that area, I would nevertheless reject the proposed topic ban from WP:ARBIPA with explanation because in this area I have been significantly active. | |||
:My edits on WP:ARBIPA were clearly net-positive, and they fixed the long-term problems that were otherwise overlooked for a long time. You can find the deletion of a number of non-notable pro-Hindutva articles, creation of SPIs of future LTAs, and multiple DYKs. That said, the idea to topic ban me achieves nothing good. Black Kite himself said "{{tq|The edits aren't the issue here, it's socking in the IPA area that is.}}". However, for the offense of sockpuppetry, I have already agreed to one-account restriction and spent over 1 year blocked. | |||
:Once unblocked, I would like to improve drafts such as ] and ]. Looking forward to positive feedback. ''']''' <sup>('']'')</sup> 00:51, 10 January 2025 (UTC) | |||
] (]) 01:23, 10 January 2025 (UTC) | |||
*'''Support unblock without TBANs and with single account restriction.'''] (]) 01:43, 10 January 2025 (UTC) | |||
*'''Support''' as requested. The request is sincere. Having edited a fair amount of articles where I discovered this editor's edits, I found his edits thoroughly productive and that is absolutely uncommon in this area. ] <small><small>]</small></small> 01:44, 10 January 2025 (UTC) | |||
:* '''Comment''' "Support as requested" sounds like a canvassed vote, did you mean it in a different way? ] 08:48, 10 January 2025 (UTC) | |||
:*:You need to re-check. , AKG posted a "request" for "unblock". By "as requested" , I meant how AKG requested himself to be unblocked, that is without any topic bans. Also, see ]. ] <small><small>]</small></small> 11:05, 10 January 2025 (UTC) | |||
:::* I did AGF, otherwise my sentence would not have included the second clause. I understand what you mean ''now'' but I did not from the original posting. ] 15:25, 10 January 2025 (UTC) | |||
*Aman.kumar.goel's explanation for the relationship with Editorkamran is {{tq|we knew each other in real life, and we used the same internet and the same system sometime, and also helped each other at times with Misplaced Pages editing}}, but Ivanvector says the CU data indicates {{tq|someone who had been carefully using two or probably more accounts for quite some time and going to lengths to obscure the connection, but made a mistake just one time that exposed them}}. I don't know who's right, but this is a CU block, so if Aman.kumar.goel stands by his answer, I'd be uncomfortable unblocking unless another CU has a different interpretation of what happened. ] (]) 01:55, 10 January 2025 (UTC) | |||
*:@], ] from AKG copied over:{{tq2|Hope you will check my statement above where I explained, "{{tq|However, upon reading further following the block, I realised that what I did was a violation of WP:SOCK because the use of both these accounts was prohibited by the policy, especially WP:SHARE and WP:MEAT.}}" That means the CU finding does not really challenge my admission because I don't deny using multiple accounts. The only thing I happened to clarify was that the two accounts belonged to two different persons before they were used by the same person, which is me. That's why, in my unblock request (for ]), I have also cited the edits of Editorkamran account as part of my edits into this area. Aman Kumar Goel (Talk) 02:43, 10 January 2025 (UTC)}} ] (]/]) 02:46, 10 January 2025 (UTC) | |||
*::All I know about this case is what I can glean by reading the private case notes, which do indeed support what Ivanvector has said. But given that AKG has admitted (on their talk page) to using the Editorkamran account, that's all kind of moot. I'd still like to hear Ivan's latest opinion on this, and I've also pinged off-wiki another CU who is familiar with this case, but my personal feeling is that we should draw a line in the sand and accept the unblock request with the single account restriction, no ARBPIA/IPA/API/TLA restriction, and an understanding that AKG's account at the bank of AGF is empty. ] ] 03:05, 10 January 2025 (UTC) | |||
*:::Oh, the other thing I wanted to mention is that on unblock requests, we're often left wondering what the user plans to work on if unblocked. In this case, they've specified two extant drafts they want to complete, both of which look like they have the potential to be useful articles. So that's a plus. ] ] 03:22, 10 January 2025 (UTC) | |||
*::Am I the only one to feel that their earlier statements, even if they did mention ] would not reasonably be understood to an admission that they did eventually user the Editorkamran account? Especially with all that comment about "we used the same internet and the same system sometime" etc? To my read the earlier statement gives the impression that they each account was only ever used by one person even if they did communicate and coordinate their editing at times. It's only most recently that I feel they've finally made it clear they it wasn't simply a matter of communication and coordination but rather that did use the other account directly. This also leads to the obvious question. How could any editor actually think it's okay for them to use some other editor's account just because it primarily belongs to another editor? Whether you consider it ]ing or whatever, you should not need any real experience to know it's unacceptable and definitely any editor with AKG's experience should know that. Note that I'm not suggesting that an editor who did what AKG did can never be unblocked, definitely they can be. But IMO there are good reasons to call into question whether the editor is ready for an unblock when they seem to have been so dishonest in their unblock request. In other words, if said something like 'yes I did X, I knew it was wrong and should not have done it, I promise not to do it again' rather than what they actually said, I'd be much more inclined to consider an unblock. ] (]) 10:14, 10 January 2025 (UTC) | |||
*:For what it's worth: I'm the other CU mentioned by Roy. I had run the initial checks and written some contemporaneous notes. I agree with {{u|Ivanvector}}'s assessment at the talk page appeal; there was a concerted, long-term effort to obfuscate the connection between these accounts, which doesn't really fit with the ] that they only realised they were doing something wrong after the fact. Whether a second individual ''also'' had access to either account at times can't really be retroactively assessed with any certainty, but it also seems immaterial to the finding of socking. --] (]) 17:39, 10 January 2025 (UTC) | |||
*'''Support''' with 1 account restriction. A prolific editor with no recurring issues. Understands where he was wrong. ] (]) 03:04, 10 January 2025 (UTC) | |||
*'''Support''': I have edited in South Asian-related topics and have run across some edits made by User:Aman.kumar.goel. Of these, I have seen several constructive edits made by him that have overall improved Misplaced Pages. Additionally, being blocked for one year is enough of a penance, which I'm sure has given him time to reflect. In view of this, I support his request in good faith. I hope this helps. With regards, ]<sup>]</sup> 03:49, 10 January 2025 (UTC) | |||
*'''Support''' with one account restriction and no topic restriction. We need competent editors working in the India topic area, as long as they follow policies and guidelines. The editor should be aware that ] applies here. ] (]) 05:17, 10 January 2025 (UTC) | |||
*'''Oppose'''. I warned AKG ] for tag-team editing with Srijanx22, after many instances of one showing up to a content dispute the other was in to back them up. AKG didn't understand then what the issue was. He didn't understand it when he was blocked for socking with Editorkamran. He doesn't seem to understand it now. The semantics of sockpuppetry vs. "just" meatpuppetry are uncompelling. We indeed need more competent editors in the India topic area. We are not going to get closer to that by letting in someone who has shown willingness to serially manipulate interactions in that topic area, who managed to evade detection for years, who continued doing so after a first warning, and whose explanation is, apparently, unpersuasive to CUs who have reviewed the evidence. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 06:51, 10 January 2025 (UTC) | |||
*:It has been sufficiently confirmed throughout these years that the false allegation of tag teaming was indeed false. Do you see me in any of the events that have been mentioned so far in this unblock request? You don't. It is disappointing to see you bringing up your misleading observation you made when you weren't even an admin. You did not even ping me. Oh, and don't ask me how I got here because I watch this noticeboard and have edited it before.] (]) 07:52, 10 January 2025 (UTC) | |||
*::I'm glad that you heeded my warning and stopped tag-teaming with AKG. AKG, however, continued to manipulate consensus in the topic area, which is what he got indeffed for. I didn't ping you because I'm not making any comment on your fitness as an editor; I just wanted to be clear that that 2021 report was separate from the Editorkamran case. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 08:13, 10 January 2025 (UTC) | |||
*:::To quote what I had said then, "{{blue|I am comfortable with ignoring your 'warning' since it lacks policy backing.}}" I said that because no tag teaming on my part ever happened in the first place and the time has proven me correct. I would reiterate that you are supposed to ping the editor whose behavior is being discussed. In this case, you had to. ] (]) 09:10, 10 January 2025 (UTC) | |||
*:::: Actually, the SPI makes it clear that there ''were'' multiple examples of you reverting to the same version as AKG in rapid succession, whether you were co-ordinating off-wiki with AKG or not. As well as those, I could add ] on 1st December 2020 and 21st February 2021 and ] on 19 April 2020. So please give it a rest with the denials and instead ensure that it doesn't happen in the future if AKG is unblocked. ] 11:00, 10 January 2025 (UTC) | |||
*:::::That's totally superficial. I have also edited both of these popular articles and so have many others I can count on my fingers. ] (]) 16:10, 10 January 2025 (UTC) | |||
*:::::: Yes, but that's not the point; have you reverted to a version also reverted to by AKG within < 24h on multiple occasions? I suspect not. ] 18:59, 10 January 2025 (UTC) | |||
*'''Support''' per NxCrypto and RoySmith. I don't see any issue with unblocking right away. The presence of this editor is a net-benefit for this area. ] (]) 07:14, 10 January 2025 (UTC) | |||
*'''Comment''' If unblocked, I would like to see AKG stay away from ]. There were a number of times - I count at least nine times between 2020 and 2023 - that they opened cases here trying to get editors on the "opposing" side blocked, and I don't think continuing this is a good idea. I also note that they were very active at SPI cases involving other editors in ARBIPA, which is another sign of BATTLEGROUND behaviour. ] 08:46, 10 January 2025 (UTC) | |||
*:That, and the refusal to accept TBANs, gives me bad vibes. | |||
*:I also don't think that agreeing to use only one account is much of a concession, that's kind of a given, but I guess it's at least better than ''not'' agreeing to it. -- ] (]) 08:56, 10 January 2025 (UTC) | |||
*:: Yes, this is also my concern. I would have ''thought'' that we would expect an editor banned for socking in a CTOP to at least demonstrate their ability to collaborate well ''outside'' that CTOP before being allowed to edit it. I can understand the Support !votes above from other editors who generally edit from the same POV as AKG, but I'm still not thinking this is a brilliant idea. ] 11:15, 10 January 2025 (UTC) | |||
*:::What is that "same POV as AKG"? It is certainly not their fault that you are assuming bad faith. ] (]) 16:12, 10 January 2025 (UTC) | |||
*:::: I don't need to AGF when the evidence is quite plain, as with the editor I mentioned above where I pointed out their tag-teaming issues. ] 19:02, 10 January 2025 (UTC) | |||
*'''Oppose'''. This user edits via proxy with IPBE, and the breadth and depth of the deception shown at that SPI is considerable. Now they're back with a semi-plausible explanation, and I don't buy it. And the one-account restriction is more challenging to police with a proxy/IPBE setup.—] <small>]/]</small> 09:27, 10 January 2025 (UTC) | |||
:*If he has agreed to one account restriction and this socking episode makes him ineligible for any future IPBE right, so what's wrong in allowing him back in since he has already served a year of block? Unless you are suggesting we completely ban those who have engaged in sock puppetry altogether, which is unrealistic. ] (]) 11:08, 10 January 2025 (UTC) | |||
::*What's wrong in allowing him back is everything Ivanvector says in that SPI. Please read it carefully and then re-read AKG's unblock request with a critical eye.—] <small>]/]</small> 12:38, 10 January 2025 (UTC) | |||
*'''Oppose'''. I would support unblocking with an ARBIPA topic ban (which could be appealed later when AKG has proved they can edit well outside that area). But since AKG will not accept that TBAN I can only Oppose at the moment. ] 11:17, 10 January 2025 (UTC) | |||
*'''Support''' - The request is convincing and to-the-point. Those opposing are seemingly forgetting that it has been more than a year since this editor has been blocked. ] (]) 12:33, 10 January 2025 (UTC) | |||
*'''Support''' per above without any topic ban. It is totally unreasonable to seek punishment over the same offense even after WP:SO has been sufficiently met. ] (]) 12:59, 10 January 2025 (UTC) | |||
*:It is not at all unusual for editors seeking an unblock to be required to accept a topic ban as a precondition to that unblock. are are recent examples from this noticeboard. ] (]) 15:04, 10 January 2025 (UTC) | |||
*::Whilst I don't support the topic ban, it would not be done as ''punishment'', but as a measure reducing the likelihood of further disruption. ] (]) 16:07, 10 January 2025 (UTC) | |||
*::Caeciliusinhorto-public not good to compare community banned editors with this case. ] (]) 16:13, 10 January 2025 (UTC) | |||
*'''Support''' per {{u|Ivanvector}}: i.e. dependent on {{blue|a topic ban from WP:ARBIPA and WP:ARBPIA and a single-account restriction}}. This will deal with the meat of the issue, while WP:ROPE should take care of the crust. ]'']''] 13:09, 10 January 2025 (UTC) | |||
*'''Oppose''' I find myself agreeing with {{U|Black Kite}} - if they are willing to come back with a topic ban that'd be one thing. Without it I'm concerned we'll just end up back at AN/I, SPI or AE again. ] (]) 13:42, 10 January 2025 (UTC) | |||
*:I will tentatively change my position to support provided it includes the topic ban. ] (]) 18:09, 10 January 2025 (UTC) | |||
*'''Oppose''' While I appreciate that brevity is required in unblock requests and people have different ways of writing stuff, as I noted above I feel the original unblock request was at a minimum intentionally evasive if not even misleading on whether Aman.kumar.goel had used the Editorkamran account directly. While they've now made it clear that they did so, the fact this only happened after editor questioned their story compared to the CU view makes me question whether it's because they didn't realise they were unclear or instead because they realised their evasiveness wasn't working. If they were evasive in their recent unblock request, this makes it very hard to trust Aman.kumar.goel. Further, even if Akg wasn't being evasive, it's very unclear why an editor with their experience didn't realise what they were doing was wrong until recently. I was originally willing to accept with a topic ban but frankly I'm now not even sure that's enough, but it's moot anyway. If this fails, I'd suggest on their next appeal Aman.kumar.goel ensures what they're telling us is clear from the get go. ] (]) 15:42, 10 January 2025 (UTC) | |||
*'''Support''' without topic ban. Sockpuppetry was the sole concern for the indefinite block. There is no evidence of any disruptive edits, as such the idea of topic ban makes zero sense. ] (]) 15:47, 10 January 2025 (UTC) | |||
*'''Oppose''' per Black Kite. Any unblock that doesn't involve a restriction on AKG's original area of disruption will simply allow for further disruption. ] ] <span style="color:#C8102E;"><small><sup>(])</sup></small></span> 16:13, 10 January 2025 (UTC) | |||
*:Not at all. Very recently, several editors editing this subject and socked were unblocked recently without any topic bans, including one more editor who was banned per 3x. ] <small><small>]</small></small> 16:23, 10 January 2025 (UTC) | |||
*'''Oppose''' per Nil Einne. Being "intentionally evasive if not even misleading" during this unblock request and previously makes it very hard for me to trust this user. I'm glad they owned up to their outright sockpuppetry with Editorkamran and had they done so from the beginning of the request, I'd have considered supporting the request, provided they accepted the topic ban(s) suggested (so as to increase the odds of their future success). --] (]) 16:25, 10 January 2025 (UTC) | |||
*'''Oppose''' unless an ARBIPA TBAN is applied. AKG's edits have not always been a positive: their approach to contentious matters has often been needlessly aggressive, and they haven't always been able to engage constructively with users and sources they disagree with. In that context sockpuppetry is more than "just" sockpuppetry. Some examples: , , , , , , and (These are discussions, not diffs, but I believe the context is needed to demonstrate the pattern I see). ] (]) 16:55, 10 January 2025 (UTC) | |||
*:<s>I would tentatively '''support''' with the TBAN they have now agreed to.</s> I have no opinion on whether a PIA ban is needed: if they have edited in that area I haven't seen it. I was considering suggesting a ban from bring others to AE/AN/ANI, but perhaps some rope is appropriate there. In any case they should be aware that they are on thin ice. I would also note that under no circumstances should they be given IPBE in the foreseeable future. ] (]) 18:02, 10 January 2025 (UTC) I'm sorry to vacillate like this, but based on comments by Ivanvector and Girth Summit I simply cannot support <small>(NB: while I am a CU, I am obviously not acting as a CU in this case)</small>. Despite our past disagreements I had been willing to give AKG another chance, but that was based on the assumption that they were being fully forthcoming, and based on the comments of CUs familiar with this situation, it doesn't appear that they have come clean. Put me down as a neutral, I suppose, though I remain opposed absent a TBAN. ] (]) 22:49, 10 January 2025 (UTC) | |||
*'''Oppose''': Per Vanamonde, Tamzin, and Black Kite. It's telling that they won't accept a TBAN from my point of view. They were disruptive prior to their block and, as much as I want to assume good faith, I feel strongly that their refusal signals their intent to immediate jump into said area. There's also the concern that they may end up chasing other editors away from the site if they continue their aggressive behaviour and approach, which frankly I expect based on the lengths they went to in the past and the TBAN issue. I think this user was a net negative, chased people away from those areas, and made it more difficult for others to get involved with. Unblocking this user would end up leading to editor time wasted and would be a further net negative. ] (]) 17:13, 10 January 2025 (UTC) | |||
*:Noting that I still oppose the unblock, even though they accepted the condition about a TBAN. I agree with Girth Summit that this seems to just be someone saying whatever they think will convince people to unblock them. I also firmly believe that allowing them back onto the project will be a net negative. ] (]) 20:12, 10 January 2025 (UTC) | |||
*'''Comment''' Aman.kumar.goel has requested this comment to be posted here from their talkpage: | |||
{{Talkquote|After seeing a number of editors, some of whom I respect, are supporting my unblock but only with a topic ban from ], I would like to accept the topic ban from the said area. Ping {{u|Yamla}}, {{u|The Kip}}, {{u|Black Kite}}, {{u|Caeciliusinhorto-public}}, {{u|Simonm223}} and {{u|Vanamonde93}}. Thanks ''']''' <sup>('']'')</sup> 17:08, 10 January 2025 (UTC)}} | |||
- ] (]) 17:46, 10 January 2025 (UTC) | |||
:Would they also consent to the ] topic ban? Because my understanding is that the ask was for both. ] (]) 17:47, 10 January 2025 (UTC) | |||
:: I don't believe the PIA issue is a problem, only the IPA one. ] 18:57, 10 January 2025 (UTC) | |||
*'''Oppose''' an unblock based on this request. When I'm looking at an unblock request, I try to get a sense of whether someone is actually coming clean and saying 'I did this thing, I recognise that was out of order and I undertake that I won't do it again', or something along those lines. In this case, I don't see that. In their unblock request of 10 December 2024 (just a month ago), AKG seems still to be saying that they were not using multiple accounts - their argument seems to be that they accept there was a violation of ] and ], but the two accounts were used by two different people from the same device. They have since swung round to acknowledging that they were in fact using the Editorkamram account, but are saying that they thought that was OK since the account really belonged to somebody else and they only used it from time to time. I'm afraid I simply don't believe that story, and I don't know what to think about their shifting narratives - I get the sense of someone saying whatever they think will convince people to unblock them, changing their story when it becomes apparent that it's not working, and failing to actually come clean about what they did and why they did it. If I don't trust someone in what they are saying in their unblock appeal, I don't trust them to abide by a one-account restriction - so, yeah, I don't think we can accept this request. Do some self-reflection, come back in six months with a frank and believable unblock request. ]] 18:35, 10 January 2025 (UTC) | |||
*'''Support'''. Seeing that AKG has agreed to the proposed IPA topic ban, the unblocking would be fine now. See no other issues. ] (]) 19:00, 10 January 2025 (UTC) | |||
*'''Support''' based on the comments from RoySmith and agree with their point that the AGF tank is gone for A.K.G. Any issues beyond a minor oops with their editing should be an immediate indef. No warnings, no "one last chance". That bridge was crossed, burned, torn down and barriers put up to block it from being rebuilt. ''']''' (]) 19:24, 10 January 2025 (UTC) | |||
::I hope A.K.G recognizes that is a last chance for them, and returning quickly to a contentious topic could be challenging for them to stay cool, engage in discussions but not disruption and that there will be enhanced scrutiny on their edits and willingness to take concerns to an admin board. They can't edit as they did before. ''']''' (]) 19:34, 10 January 2025 (UTC) | |||
*'''Oppose''' - I gave my reasons on the talk page; I don't trust this user. ] (<sup>]</sup>/<sub>]</sub>) 20:20, 10 January 2025 (UTC) | |||
*:Also I should point out that I was not involved whatsoever in the checks that led to this block; my comments on the talk page refer to emails I remember reading a year earlier on the private checkuser mailing list, which does not archive. I did check in relation to their unblock request recently and in my opinion that check was inconclusive; I elaborated on their user talk at the time. The result gives me pause because they had been using multiple accounts and evading checkuser for quite a long time before being blocked, while editing in one of our longest-designated contentious topics, one that's known to be very badly impacted by sockpuppetry and state-sanctioned disinformation campaigns. I suggested a topic ban from India-Pakistan for reasons that I think are already obvious from previous comments in this thread, and from Israel-Palestine because of something I thought I read on their talk page about a dispute in that topic, but I can't find that now and so I have to say I was probably out of line to have suggested it. But on the whole, I do not support unblocking, even with the proposed restriction. ] (<sup>]</sup>/<sub>]</sub>) 20:43, 10 January 2025 (UTC) | |||
*Very, very '''weak support''' on unblocking here with a one-account and indefinite IPA topic ban restriction. I found my engagement with the editor at their talk page today to be somewhere between obstructionist and disingenuous — and from reading the comments above, others have got similar vibes from different comments earlier in this process regarding the sockpuppetry and willingness to accept a topic ban condition. As Ravensfire notes above, the assume good faith tank is just about empty here — which means any non-trivial lapse or return to suboptimal behaviours is going to end up with a pretty swift reblock. I am very sympathetic to the number of very experienced editors above saying that this editor is a time sink and a net negative, and while I don't necessarily disagree based on what I've seen at their talk page and the evidence presented here, I think it's worth trying here one more time — armed with account and topic ban restrictions, and a pretty clear sentiment from a number of admins commenting (both on the support and oppose sides) that any issues upon resuming editing will be handled swiftly. ] (]) 22:31, 10 January 2025 (UTC) | |||
*'''Support, but''' only with IPA topic ban, 1-account restriction, no VPN use, and no IPBE. That should allow us to be able to detect recidivism and limit potential damage. — ] ] 22:55, 10 January 2025 (UTC) | |||
*'''Oppose''' per Black Kite, Tamzin, S Marshall, Girth Summit, and Ivanvector. ''']'''<span style="border:2px solid #073642;background:rgb(255,156,0);background:linear-gradient(90deg, rgba(255,156,0,1) 0%, rgba(147,0,255,1) 45%, rgba(4,123,134,1) 87%);">]</span> 23:04, 10 January 2025 (UTC) | |||
*'''Oppose''', agreeing with a number of editors above. I don't know if the two drafts, for Indian companies, would fall under ]. Unfortunately, the editor does not seem trustworthy. ]] 23:36, 10 January 2025 (UTC) | |||
*'''Support''' - At the end of the day, the ] has been followed by this user for a long time. Don't see anything wrong with providing one more chance. ] (]) 23:42, 10 January 2025 (UTC) | |||
*'''Oppose''' per comments of Blablubbs, Tamzin, etc. If they are unblocked, they should be under an India--Pakistan CTOP topic ban. --] (]) 00:07, 11 January 2025 (UTC) | |||
* '''Oppose'''. The CheckUser evidence of overt sock puppetry (not meat puppetry) is pretty strong, and the repeated denials, which seem to get walked back over time, make this user seem untrustworthy. ] (]) 00:28, 11 January 2025 (UTC) | |||
*'''Support''' - Noting the opposes above, AKG has nevertheless agreed with a topic ban inline with many of the opposes. It shows he is willing to minimize any possible concerns and that is a good sign. ] (]) 00:51, 11 January 2025 (UTC) | |||
*'''Oppose''' calling socking the sole issue is a red herring when there was disruption in addition, but the socking alone merited the block so they didn't need to be blocked for both. I think accepting the t-ban is more telling us what he thinks we want to hear, vs. awareness of why AKG shouldn't edit there. I do not think an unblock would be productive. ] ] 01:36, 11 January 2025 (UTC) | |||
{{abot}} | |||
== Import request == | |||
{{atop | |||
| result = A list without citations or an indication that it meets ] is not going to be imported here. ] (]/]) 18:00, 12 January 2025 (UTC) | |||
}} | |||
Can you import, ] from simple Misplaced Pages. I created the page there.<span id="Cactusisme:1736493543617:WikipediaFTTCLNAdministrators'_noticeboard" class="FTTCmt"> — ] <sup>]</sup> <sup>]</sup> 07:19, 10 January 2025 (UTC)</span> | |||
:I suppose you mean , which you ''didn't'' create at all though, and which is completely unsuitable for enwiki as it stands, being unsourced and lacking all indication of notability. ] (]) 09:09, 10 January 2025 (UTC) | |||
::Well, they create the page. ]<sub>]<sub>]</sub></sub> (]/]) 15:18, 10 January 2025 (UTC) | |||
::], oh, okay<span id="Cactusisme:1736586978195:WikipediaFTTCLNAdministrators'_noticeboard" class="FTTCmt"> — ] <sup>]</sup> <sup>]</sup> 09:16, 11 January 2025 (UTC)</span> | |||
{{abot}} | |||
== Arbitration motion regarding coordinating arbitrators == | |||
The Arbitration Committee has resolved by ] that: | |||
{{ivmbox|1= | |||
The ] are amended by adding the following section: | |||
<blockquote> | |||
; Coordinating arbitrators | |||
The Arbitration Committee shall, from time to time, designate one or more arbitrators to serve as the Committee's coordinating arbitrators. | |||
Coordinating arbitrators shall be responsible for assisting the Committee in the routine administration and organization of its mailing list and non-public work in a similar manner as the existing ] assist in the administration of the Committee's on-wiki work. | |||
The specific responsibilities of coordinating arbitrators shall include: | |||
* Acknowledging the receipt of correspondence and assigning tracking identifiers to pending requests and other matters; | |||
* Tracking the status of pending matters and providing regular updates and reminders on the status of the Committee's off-wiki work to arbitrators; | |||
* Reminding members of the Committee to vote or otherwise take action in pending matters; | |||
* Organizing related correspondence into case files; and | |||
* Performing similar routine administrative and clerical functions. | |||
A coordinating arbitrator may, but is not required to, state an intention to abstain on some or all matters before the Committee without being listed as an "inactive" arbitrator. | |||
</blockquote> | |||
}} | |||
For the Arbitration Committee, ] ] 23:48, 10 January 2025 (UTC) | |||
: Discuss this at: '''{{slink|Misplaced Pages talk:Arbitration Committee/Noticeboard|Arbitration motion regarding coordinating arbitrators}}'''<!-- ] (]) 23:49, 10 January 2025 (UTC) --><!--Template:hes--> | |||
== Backlog == | |||
] <span style="display:inline-flex;rotate:-15deg;color:darkblue">''']'''</span><span style="display:inline-flex;rotate:15deg;color:darkblue">]</span> 19:38, 11 January 2025 (UTC) | |||
== Requesting review of SPI == | |||
{{Atop|No need to have brought this here.--] (]) 23:15, 11 January 2025 (UTC)}} | |||
I recently filed an ]; any admin/checkuser eyes would be appreciated. Thank you! ] (] • ]) 22:43, 11 January 2025 (UTC) | |||
:CUs and SPI clerks are very aware of which SPIs need attention. Please trust that we will get to the one you posted. Asking for input at AN isn't very helpful unless your SPI is much more urgent than usual. ] (]) 23:09, 11 January 2025 (UTC) | |||
{{Abot}} | {{Abot}} | ||
== IPBE for AWB account == | |||
== RFC at RSN desperately needs to be closed == | |||
{{atop|status=Done|1=Done. - ] <sub>]</sub> 05:02, 12 January 2025 (UTC)}} | |||
Hi. I'm performing a task using {{user|CanonNiAWB}}, but the edits aren't editing since I'm using a VPN. I already have IP block exemptions on this account, so could it also be granted to that? Thanks. <span style="white-space:nowrap"><span style="font-family:monospace">'''<nowiki>''']<nowiki>]]'''</nowiki>'''</span> (] • ])</span> 02:32, 12 January 2025 (UTC) | |||
:Done. ] (]) 02:40, 12 January 2025 (UTC) | |||
::Thanks. <span style="white-space:nowrap"><span style="font-family:monospace">'''<nowiki>''']<nowiki>]]'''</nowiki>'''</span> (] • ])</span> 02:46, 12 January 2025 (UTC) | |||
{{abot}} | |||
== Content removal, POV pushing, edit warring == | |||
] has been droning on forever and is literally causing the RSN, an already high-activity page, to slow down and malfunction. The discussion has become stagnant and bloated and needs an uninvolved closer badly just because it’s making it difficult to actually use the noticeboard. ] (]) 19:45, 17 June 2024 (UTC) | |||
{{atop | |||
| result = Please use ] rather than creating new ones. ] ] 15:14, 12 January 2025 (UTC) | |||
}} | |||
@] removing content and POV pushing here and is currently edit warring ] (]) 10:52, 12 January 2025 (UTC) | |||
:Would you say that its droning is... bogus? | |||
:This looks like the same complaint as ]. Let's centralise discussion there. I note that ] is also empty. ] (]) 11:19, 12 January 2025 (UTC) | |||
:Sorry, I'll see myself out. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 21:53, 17 June 2024 (UTC) | |||
{{abot}} | |||
::<nowiki>*</nowiki>finger pistols* | |||
::(But seriously, it's been months now. And it's not like any section of it is ''that'' complex. If you really feel it's necessary, assemble a three-person team or something, but clearly it needs to be closed.) ] (]) 18:37, 18 June 2024 (UTC) | |||
:::I'll pay extra cabal dues this month if someone can get it done. -- <small>LCU</small> ''']''' <small>''«]» °]°''</small> 18:49, 18 June 2024 (UTC) | |||
:I pity whoever has to close that cesspit of an RFC. The sheer ''amount'' alone, my gosh. ] <sup>(]) </sup> 21:14, 18 June 2024 (UTC) | |||
::It'll probably be worthwhile closing it to new comments while the "lucky" volunteer reads and assesses. It's exceedingly unlikely at this point that anybody who hasn't said anything will say something that hasn't been said already. ] (]) 01:19, 19 June 2024 (UTC) | |||
== Tulsi (unblock request) == | |||
== Request for review of Draft:Hassan Nisar Haripur == | |||
{{atop green|User unblocked. ] 12:25, 16 January 2025 (UTC)}} | |||
* {{userlinks|Tulsi}} | |||
* Blocked (indef) on 3 April 2024 (9 months ago) by ] during an AN thread (]) for undisclosed paid editing | |||
* Subsequent unblock request was also considered at AN before being declined (]) | |||
Tulsi has now submitted an unblock request which I am copying: | |||
A request for review of the draft article for Hassan Nisar Haripur, an award-winning Pakistani entrepreneur, YouTuber, and philanthropist, is being made. Despite meeting Misplaced Pages's notability guidelines, the article has been rejected multiple times by Saqib. | |||
{{talk quote block|Dear Sysops, | |||
Hassan Nisar Haripur's achievements and coverage in reputable sources demonstrate notability: | |||
I sincerely apologize for my past actions, which were problematic and deceptive. I fully understand the concerns raised, and I deeply regret my involvement. On April 3, 2024, my account was blocked by Rosguill in relation to undisclosed paid editing associated with the {{section link|Misplaced Pages:Administrators' noticeboard/Archive361|DIVINE and Tulsi: COI/UPE/quid-pro-quo editing, association with threats and harassment}}. However, I want to clarify that my involvement in these matters was minimal, with only minor interactions in the past. I have never written articles for payment, and I do not support paid editing. | |||
- Award-winning entrepreneur (references: ] ]) | |||
The issues in question occurred ], prior to the block. At that time, I admitted my conflict of interest (COI) and disclosed it on the relevant article talk pages. Following discussions, my global and local rights were removed, but the block was not enforced until two years later. Many of the articles in question were deleted, so I did not find it necessary to disclose anything further. Moving forward, I have no intention of creating or editing COI-related articles. However, if I am ever in a situation where I am required to contribute to such an article, I will ensure full disclosure on the article talk page and submit it for review, as I did with the article ]. | |||
- Featured in top Pakistani publications, including The Dawn and The Tribune (references: ) | |||
While I respect Rosguill’s decision to impose a block after the two-year gap, I understand that a block serves to prevent disruption rather than punish. I have learned valuable lessons from this experience, and my contributions over the past two years reflect this growth. In this time, I have created , all without any undisclosed paid editing or COI involvement. Additionally, I have contributed to patrolling, as seen in the ] and ]s, and I have reported several violations on WP:UAA. | |||
Misplaced Pages's policy on award-winning individuals states that they are eligible for a Misplaced Pages page (]) . | |||
I acknowledge that I was not fully familiar with Misplaced Pages's policies in the past, but I have since taken the time to understand them better. I have been an active and committed user since October 2014, with significant contributions across various Wikimedia projects. I have also served as a sysop on Wikimedia Commons, Meta-Wiki, MediaWiki, and the Maithili and Nepali Wikipedias. | |||
High-quality sources have been provided to support the article's notability, but Saqib has consistently rejected the draft. A review of the article is requested to assess whether it meets the necessary criteria for inclusion on Misplaced Pages. | |||
I am requesting an unblock because I am fully committed to abiding by all the established policies moving forward, and I am eager to contribute here in a constructive manner. Please kindly allow me a second chance. | |||
Please review the draft article and references to ensure a fair evaluation. ] (]) 08:34, 18 June 2024 (UTC) | |||
:Not sure why you are posting this here, ] has been declined three times and now rejected, the topic is simply not ]. ] (]) 08:56, 18 June 2024 (UTC) | |||
::And it is not correct that {{tq| Saqib has consistently rejected the draft}}. Three '''different''' editors declined the draft, and then Saqib rejected it after looking for more sources. ] (]) 09:01, 18 June 2024 (UTC) | |||
:::While the draft's notability is still disputed, the clarification provides context to the review process. However, the core concern remains: the draft's notability is evident, yet it has been rejected. A reevaluation of the article's notability, considering the reliable sources and Misplaced Pages's policies, is still requested. ] (]) 09:06, 18 June 2024 (UTC) | |||
::::It has already been looked at four times, by three different editors. And again, this is not something that should be on the admin board. ] (]) 09:09, 18 June 2024 (UTC) | |||
::Forgot ot include that Saqib was one of the three who rejected it. ] (]) 09:04, 18 June 2024 (UTC) | |||
::The post was made here to request a review of the draft article's rejection, as the decision seems inconsistent with Misplaced Pages's notability guidelines. The repeated rejections despite the provision of high-quality sources, including award recognition and coverage in top Pakistani publications, raise concerns about the fairness of the review process. | |||
::The statement "the topic is simply not notable" is subjective and contradicts the evidence provided. Notability is determined by the presence of credible sources, which have been abundantly provided in this case. A reevaluation of the article's notability, considering the reliable sources and Misplaced Pages's policies, is requested. | |||
::A more detailed explanation of the rejection, beyond a simple statement, would be appreciated. Additionally, a review of the article by a different editor, without the assumption that the topic is not notable, is requested. ] (]) 09:02, 18 June 2024 (UTC) | |||
:No evidence of notability has been provided. Bonadea -- a fourth editor -- went painstakingly through the sources too, found none of them to contribute to making the article subject meet GNG, and I don't see any I'd dispute. This is not a suitable article for English Misplaced Pages. And this is a very poor forum for this as well; administrators are editors entrusted with advanced tools by the community, not content supervotes. In any case, the explanation of the rejection was thoroughly explained, completed with the aforementioned source analysis, and the primary issue appears to be that you don't like the explanations, not that they are improper. You should drop ]. ] (]) 16:04, 18 June 2024 (UTC) | |||
I was supposed to be informed about this discussion on my tp. --] (] I ]) 10:18, 18 June 2024 (UTC) | |||
:OP has shown us consistent COI editing, chatbot-generated communication, resistance to attempts at instilling a clue on two different boards, and this ]. Even in the unlikely event that they’re not socking, they’re clearly ] and should be blocked accordingly before they waste more editors’ time. --] ] 12:40, 18 June 2024 (UTC) | |||
Thank you for your consideration. I humbly request your reconsideration and the restoration of the editing privileges on my account on English Misplaced Pages. | |||
*I have blocked both {{user|Uohabacasu}} and {{user|Thekhyberboypk}}, who seemed to be acting in concert along with IPs {{User|39.41.131.130}}, {{User|39.41.180.193}} and {{User|39.41.181.140}} to promote a YouTube personality on wikipedia, and ignoring feedback. Will leave the possible speedying of the drafts ], ], and ] to other admins more familiar with the standards applied in draftspace. ] (]) 18:29, 18 June 2024 (UTC) | |||
Sincerely, | |||
== ] and dynamic IP's == | |||
] ] 14:39, 10 January 2025 (UTC)}} | |||
Having had discussions with the blocking admin, we would like to seek community comments on the unblock request. | |||
Quite recently I noticed this on the Starlink website after hearing about "dynamic IP's" from this discussion. Considering these IP's do not flag as proxy's, are they a issue in regards to Sockpuppets? ] (]) 11:23, 18 June 2024 (UTC) | |||
:Generally speaking, Starlink is not so different to any other mobile ISP, of which there are plenty, or for that matter most non-mobile ISPs. There are lots who rotate IPs very rapidly (as some editor pointed out in that discussion, switching ISPs is not actually a dynamic IP issue). As an added bonus, Starlink provides a list of their IP ranges per geolocation, for example in Atlanta, GA. Is there a sockpuppetry or PROJSOCK issue in this case? Probably. Is Starlink the issue, probably not. -- ] <sup>]</sup> 12:42, 18 June 2024 (UTC) | |||
Tulsi was blocked after UPE allegations that had been outstanding for around 2 years essentially caught up with them. They have now attested to having never edited for pay, which was the question they originally failed to answer twice (], ]), leading to the block. In the unblock request, they give a sincere undertaking not to engage in any more UPE. | |||
== RfC at ] == | |||
They have created several dozen articles about Nepalese politicians but these seem to be innocuous. I have identified only a handful of articles where Tulsi could have edited for pay. Given the amount of other contributions Tulsi has made, it would be appropriate to give the benefit of the doubt. ] 15:14, 12 January 2025 (UTC) | |||
Hi, is my conduct on ] appropriate? I'm trying to purge the dysfunction from the rfc I did but I'm struggling to gauge whether it's appropriate to have another topic on redesigning it for relisting. I don't plan on engaging in a relisting ] (]) 14:37, 18 June 2024 (UTC) | |||
*I cannot find the link for "A related meta-wiki discussion". <span>]]</span> 15:35, 12 January 2025 (UTC) | |||
**I've deleted those words. I had decided not to include them in my post, but accidentally left them in. For interest, the discussion was this one: ]. ] 15:38, 12 January 2025 (UTC) | |||
::], ], and ]. I'm trying to rectify the dysfunction partly caused by me. When I made the initial edit per ] I received successive personal attacks which made me defensive and combative, affecting my conduct in the rfc. Multiple editors then derailed the rfc with some valid points and I'm trying to address those so it can be relisted for further input. ] (]) 21:55, 18 June 2024 (UTC) | |||
*'''Support''' per ]. I will AGF that Tulsi will keep his promise not to engage in any COI editing going forward. ] (]/]) 16:07, 12 January 2025 (UTC) | |||
* '''Question''': We are all volunteers here, so the applicant's comment {{tq|if I am ever in a situation where I am '''required''' to contribute to such an article}} (emphasis mine) is worrisome within the context of UPE/COI. Could they, or someone else for that matter, provide some clarification? ] (]) 19:57, 12 January 2025 (UTC) | |||
*: I assume "required" is just poor phrasing and refers to circumstances similar to ] provided in the same sentence you quote. In any event, the second part of the sentence states {{tq|<em>I will ensure full disclosure on the article talk page and submit it for review</em>}} (emphasis added). That promise is enough for me. ] (]/]) 21:00, 12 January 2025 (UTC) | |||
*'''Support''', we should generally give a second chance to users who have greatly and fundamentally changed in several months. Given that the user acknowledged the block and promised not to engage in undisclosed paid editing, not to mention that the user is trusted elsewhere, I see no reason to oppose. ] (]) 20:48, 12 January 2025 (UTC) | |||
*'''Support''' I believe in their ability to address any concern in the future, given that they served as a sysop on Wikimedia Commons, Meta-Wiki, MediaWiki, and the Maithili and Nepali Wikipedias. ] (]) 21:44, 12 January 2025 (UTC) | |||
:'''Support''' A second chance promises that Tulsi will not do highly undisclosed paid editing. I may partially support a topic ban on Nepalese politics against Tulsi. ] (]) 05:56, 13 January 2025 (UTC) | |||
== EXTRA EYEs on AIV and Recent Changes please == | |||
*'''Support''' Make the most of the second chance ] (]) 23:05, 14 January 2025 (UTC) | |||
*'''Support''' I had already been kind of watcxhing the discussion on their talk page over the last few days, and agree with an SO unblock. ] ] 23:34, 14 January 2025 (UTC) | |||
{{abot}} | |||
== ] == | |||
There is a racist troll running amok. I have blocked them twice. They create new accounts and make rapid fire edits to random pages with vile edit summaries that require individual revdeling. Any help appreciated. -] (]) 17:33, 18 June 2024 (UTC) | |||
{{atop|1=Snow in the forecast. - ] <sub>]</sub> 22:08, 13 January 2025 (UTC)}} | |||
I can't believe this article's AfD is still up and not closed as a ] keep. The nominator has acknowledged his mistake out of ignorance. He was in middle school when the subject first became notable, and never heard of him. If the media, or God forbid, Social Media, discovers this nomination, it will do great harm to the reputation of the Misplaced Pages community as being collectively ignorant or ''much, much worse''. I used to be an administrator, and would have closed this as keep. Please do something! ] (]) 16:22, 13 January 2025 (UTC) | |||
:Anybody can close an AfD as SNOW keep. That's the whole point of SNOW. ] (]/]) 16:25, 13 January 2025 (UTC) | |||
== Contested RfC non-admin partial close == | |||
::Snowed by me. — ] ] 16:35, 13 January 2025 (UTC) | |||
{{archive top|1=This RFC was probably not a good candidate for a NAC due to the inherent controversy of this issue. That said, the closure itself was a decent one if a little short on explanation. The question of involved-ness doesn't seem to be a compelling one. That said, the primary argument here among editors was that a non-admin closed part of the RfC. To avoid all doubt, I've re-closed it with an expanded rationale and endorsed the original result. {{U|TrangaBellam}} is commended for her efforts in sorting through those arguments and finding a consensus; no reasonable administrator could have done differently. | |||
:::Thank you!!! ] (]) 16:38, 13 January 2025 (UTC) | |||
{{abot}} | |||
== Request for Administrator Review of Repeatedly Declined Draft: Ario Nahavandi == | |||
{{atop|1=]. - ] <sub>]</sub> 03:25, 15 January 2025 (UTC)}} | |||
Dear Administrators, | |||
I am writing to request your assistance regarding my draft, ], which has been repeatedly declined over the past year despite my adherence to Misplaced Pages’s guidelines. | |||
I'm also going to look through the rest of the RFC to determine if there is any consensus in the other parts, since ''someone'' needs to grab the third rail. I'm not 100% committed to closing them, so if anyone is already working on it they're free to do so. <span style="font-family:Papyrus, Courier New">]</span><sup><span style="font-family:Papyrus"><small>'']''</small></span></sup> 03:26, 20 June 2024 (UTC)}} | |||
Over the course of several months, I have worked diligently to gather reliable, published, and independent sources, including magazine articles and other credible publications, that meet Misplaced Pages’s notability criteria. My most recent submission was declined in less than an hour—a timeframe that strongly suggests it was not even reviewed carefully or thoroughly. | |||
{{ombox | |||
|text = '''Please note''' that this discussion falls under ] restrictions, and is thus only open to logged-in editors with ]. | |||
This is particularly frustrating as I see numerous approved articles on Misplaced Pages that cite sources far less reliable or even completely broken. In contrast, my article contains verifiable references that adhere strictly to Misplaced Pages’s policies. This inconsistency feels unfair and raises concerns about bias in the review process. | |||
I have followed all guidelines in good faith and cannot accept decisions that appear to be based on personal opinion rather than policy. It feels as though my article is being subjected to an unjust standard, especially when compared to articles that seem to bypass scrutiny. I genuinely wonder if this process is influenced by factors beyond content quality, as I have no means to “pay” for an article to be published, unlike some others. | |||
I kindly request that an administrator reviews my draft with impartiality and provides clear, actionable feedback. Otherwise, I am truly exhausted by the repeated rejections and dismissals with no valid reasoning. | |||
To provide context, here are some of the sources I included: | |||
• https://www.nationaldiversityawards.co.uk/awards-2024/nominations/ario-nahavandi/ | |||
• Taurus Magazine (2024-11-19). "Ario Nahavandi". Taurus Magazine. 88: 7 – via www.magcloud.com | |||
• 6x Magazine (2024-11-22). "Ario Nahavandi; The Persian Icon". 6X Magazine. 432: 6–7 – via www.magcloud.com | |||
Thank you for your time and consideration xx | |||
] (]) 23:47, 14 January 2025 (UTC) | |||
:Administrators cannot override draft declines, and in fact the administrator toolset ]. —] ] <sup><small>] ]</small></sup> 23:51, 14 January 2025 (UTC) | |||
::So who can I turn to for help? If administrators cannot assist in overriding the draft declines, to whom can I escalate this issue? I am deeply concerned that my article has been repeatedly declined without proper consideration of the sources I’ve provided. These sources are reliable, published, and fully comply with Misplaced Pages’s guidelines, yet they continue to be dismissed without even being properly reviewed. | |||
::It’s becoming clear that the rejection process isn’t being carried out fairly. I can’t help but feel that my article is being judged based on factors other than content quality, especially when I see articles approved with far less solid references. | |||
::I understand that the review process is based on policy, but when it seems clear that my draft isn’t being given the attention it deserves, I need to know where I can seek help to ensure fairness. | |||
::I kindly ask for your guidance—if administrators cannot intervene, who can I turn to for proper support in getting this article reviewed fairly? | |||
::Thank you for your time. ] (]) 00:08, 15 January 2025 (UTC) | |||
:::]. This is where you appeal problems with submissions of drafts. You should read the ] and ] carefully. ] (]) 00:20, 15 January 2025 (UTC) | |||
:::{{ping|Lanak20}} I actually ]. They're all malformed at best and unusable at worst. ] —] ] <sup><small>] ]</small></sup> 00:20, 15 January 2025 (UTC) | |||
*I've blocked the OP as a spam-advertising-only account. I should add that it's pretty obvious they've used other accounts to promote this person, I believe most recently as of last October.--] (]) 00:25, 15 January 2025 (UTC) | |||
{{abot}} | |||
== Your Friendly Neighborhood Sociologist Edit Restriction Appeal == | |||
{{atop green|Unanimous consent after 36 hours to lift the restriction. ] (]) 14:25, 16 January 2025 (UTC)}} | |||
A bit over a year ago, with near unanimous support, I appealed a TBAN from GENSEX - receiving in its place the following sanctions {{tq|1RR restriction in both the GENSEX and AMPOL topics; is limited to 0RR on articles for organizations/activists who are affiliated with anti-transgender activism or gender-critical feminism, broadly construed; and has a PBAN from Kellie-Jay Keen-Minshull.}} Previous discussions are linked there. I am now requesting that my restrictions be dropped entirely because I have grown considerably as an editor, both since my initial TBAN when I'd just turned 19 and since the appeal. | |||
I translated ] (having originally wrote it on eswiki during my TBAN) and made it my first GA. I uploaded multiple colorized photographs of transgender historical figures to commons I improved ] and wrote articles for famous trans activists ] and ]. I also cleared up serious BLP violations at ] and rewrote the article. I also helped expand ] and wrote ]. I improved ] and ]. I improved ]. I rewrote and considerably expanded ] as well as ]. I expanded the article on the ]. I wrote the article on the 1970 semi-governmental report '']''. I expanded the articles on ] and ]. I rewrote ] to follow ] and use systematic reviews instead of primary studies. '''Most proudly''', I wrote ] and took it to GA - this is particularly relevant as a key part of the original TBAN discussion was whether my commitment to removing misinformation from Misplaced Pages was a case of either ] or following ] and ]. | |||
I believe the restrictions impair my ability to edit productively. I generally edit with 1RR regardless of sanctions. With 0RR, as Red-tailed hawk noted at my previous appeal "they can wind up restricting the sorts of partial reverts that are often a healthy part of the ordinary editing process." With 0RR, I am unable to engage in the BRD cycle properly and always second-guessing whether a partial edit to a recent edit counts as a revert or not. It also prevents me reverting drive-by SPA/IP povpushing. I don't plan to ever edit KJK's article again, but I believe that my record of neutral constructive editing shows the PBAN is no longer preventative or necessary. In the highly unlikely event I ever see a reason to edit it in future, I know my edits would be subject to heightened scrutiny which I'd welcome. | |||
I appreciate your consideration. My best regards, ] (]) 01:02, 15 January 2025 (UTC) | |||
:'''Support.''' ] (]/]) 01:25, 15 January 2025 (UTC) | |||
:'''Support'''. Based on YFNS's activity since the original tban, I don't see any reason to believe that restrictions are necessary going forward. ] (]) 06:34, 15 January 2025 (UTC) | |||
:'''Support'''. Welcome back comrade. ] (]) 06:56, 15 January 2025 (UTC) | |||
:'''Support''' based on their editing activity between TBAN and last year, as well as between the sanctions and now. Good work, and a great example of how this restorative process is ''supposed'' to work. May you inspire other misguided people to a path of restoration. ] ] 08:27, 15 January 2025 (UTC) | |||
:'''Snow Support''' ] (]) 14:15, 15 January 2025 (UTC) | |||
:'''Strong support'''. To me YNFS comes across as a very responsible editor and I believe these restrictions are no longer warranted. ] (]) 16:09, 15 January 2025 (UTC) | |||
:'''Support''' I remember the original ban happening due in large part to canvassing on twitter, the fact that any restrictions remained in place thereafter strikes me as a deep miscarriage of justice. ] (]) 23:26, 15 January 2025 (UTC) | |||
'''Query''' Does your reference to BRD mean that you undertake to follow it in the future? ] (]) 14:17, 15 January 2025 (UTC) | |||
:'''Enthusiastic support''' YFNS is a perfect model of an editor who is an asset to Misplaced Pages. ] (]) 15:17, 15 January 2025 (UTC) | |||
:'''Support''' A well worded appeal, worth giving another chance. — <b>]:<sup>]</sup></b> 18:20, 15 January 2025 (UTC) | |||
*'''Support''' This is a convincing and sincere appeal. ] (]) 00:22, 16 January 2025 (UTC) | |||
*'''Support''', Welcome. ~] ] <sup>「] / ]」</sup> 02:33, 16 January 2025 (UTC) | |||
*'''Support''' as they have convincingly demonstrated change. '']''<sup>]</sup> 02:53, 16 January 2025 (UTC) | |||
*'''Support''' I supported and still support the original restrictions, and the later now appealed restrictions. I think YFNS's case has shown that an editor can come back from the brink successfully and am happy that happened. ] (]) 04:00, 16 January 2025 (UTC) | |||
{{abot}} | |||
== Copyvio Problem == | |||
Hey all, I believe that these three diff should be redacted as copy vio's, thanks. There are several sentences which are directly lifted from the sources. Some one more experienced should likely have a look through the revision I restored as well. I didn't spot anything, but I may have missed something. | |||
] (]) 22:35, 15 January 2025 (UTC) | |||
:To be clear, I don't think that @] is really at any fault here. | |||
:] (]) 22:37, 15 January 2025 (UTC) | |||
::@] please see {{tl|copyvio-revdel}} on how to tag copyvios for attention. ] (]) 08:04, 16 January 2025 (UTC) | |||
== Lardlegwarmers block appeal == | |||
{{atop | |||
| result = Essentially unanimous consensus to not unblock. ] ] 15:53, 17 January 2025 (UTC) | |||
}} | }} | ||
* {{userlinks|Lardlegwarmers}} | |||
] has been partly (as in, only a part of it) closed by ], with the summary: {{tq|I see a consensus for '''Option 3'''}} {{tq|— going by the numbers (roughly, 3:1) as well as the relative strength of arguments — and note that most of the participants were okay-ish with deprecation too.}} | |||
I blocked Lardlegwarmers yesterday for one week for a violation of ] from COVID-19. This was about ], although I subsequently noticed ] as well. LLW has asked me to copy their appeal here. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 03:00, 16 January 2025 (UTC) | |||
=== Statement from Lardlegwarmers === | |||
I have only been very active editing Misplaced Pages for about one month, even though my account is older. I was blocked for pushing a minority POV in the talk page for Covid-19 Lab Leak Theory, which I understand. For context, this issue wouldn't have even come up at ANI except that there was this very old account making borderline uncivil comments constantly, and I took them to ANI myself and it boomeranged. One thing that I learned from that experience is that Misplaced Pages's culture sort of revolves around social dynamics and politics, which can overshadow fairness and consistency in rule enforcement, and that I am probably not going to be the one to fix it.<ref>]</ref> Anyways, in my defense, I didn't learn until later that my attempt to reason things out like grownups was not allowed; my edits were in good faith and I was really just attempting to talk it out with the other editors who did not agree with me. But I understand that the norm in this space is to walk away if there isn't any uptake of my ideas or take it to dispute resolution instead of continuing to try to convince people. The current ban is for making a comment on an AE thread, not a Covid-19 article. I was on the page for a totally unrelated reason and noticed that a user I recognized from the Covid thread was being discussed. My comment was mostly about user behavior and reflecting on the underlying dispute itself, not Covid-19. Also, on my user page I quoted ] discussing his view on Misplaced Pages's approach to Covid-19 , which I'd assumed was permitted because it's my own user page and it's really a comment about the state of Misplaced Pages as a whole. The admin who blocked me, @], blanked it from my user page. If the community won't let me keep that quote on my user page, then fine, we'll leave it removed, but I wish they would have just asked me to remove it and described why instead of editing my user page. A block for this stuff seems harsh. Thanks. | |||
{{talk reflist}} | |||
=== Statement from Tamzin === | |||
Excerpting my comment on their talkpage:{{tq2|Usually we only warn someone on their first topic ban violation. However, in your case, the fact that both violations occurred within hours of the ban being imposed, and that they were belligerent rants treating Misplaced Pages as a battleground, made me judge that a short block would more clearly communicate just how far you are from what is considered acceptable conduct. Even if you didn't understand that the ban applied outside articles, you should have understood that the community found your editing about COVID disruptive, which should have been reason enough to not make those edits.}} <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 03:00, 16 January 2025 (UTC) | |||
=== Discussion among uninvolved editors === | |||
*This is clearly a topic ban violation - and it came less than a day after it was imposed. Even if assuming in good faith that they didn't know it was a topic ban violation, their unblock request shows not only that they don't understand what they did wrong, but they attempt to justify it with statements such as {{tq|Anyways, in my defense, I didn't learn until later that my attempt to reason things out like grownups was not allowed}} which is borderline a personal attack (veiled insult that others weren't being grownups); {{tq|which can overshadow fairness and consistency in rule enforcement}} which is confirming they still don't understand why they were topic banned nor why they were blocked for violating it; and quoting Larry Sanger's ] promoting comments on their userpage after their topic ban. To summarize, I have no confidence that the user understands what they did wrong, and I would go so far as to say the user attempting to skirt the edges of their topic ban and supporting another user trying to promote fringe theories on Misplaced Pages merits an indefinite community ban. TLDR: '''Oppose unblock''' and ultimately would support indefinite ban due to the flagrant violation, lack of understanding, and no belief that after the 7 days is up they will not go straight back to trying to ]. I won't be the one to propose that, however. -bɜ:ʳkənhɪmez | ] | ] 03:10, 16 January 2025 (UTC) | |||
*I don't see how an unblock is possible when Lardlegwarmers clearly still doesn't understand what a broadly construed topic ban means. To be clear, there's no need to ask the "community" whether you can keep your topic ban violation. The only hope for you to be able to obey it is if you are able to decide yourself, especially after you've been told by an admin. While we do try to educate instead of just blocking, the "community" isn't here to help you understand the limits of your topic ban. ] (]) 04:01, 16 January 2025 (UTC) | |||
*:Should clarify that despite what I said above, I'd weakly oppose extending the topic <del>ban</del> <ins>block</ins> to indefinite at this time. While I'm not hopeful Lardlegwarmers is going to be able to obey it given what they've said, I think it's fine to give them rope after the <del>ban</del> <ins>block</ins> expires and apply normal escalating blocks. Since we're already here, perhaps this will somehow help them understand that yes the community requires you to apply it broadly on anything to do with COVID-19 throughout Misplaced Pages. They should consider this very short rope though and notably the next time they feel they need to ask the community whether they're violating their topic ban when they are, it might be the last time. ] (]) 20:38, 16 January 2025 (UTC) | |||
*::Sorry mixed up ban and block above twice, now fixed. ] (]) 01:45, 17 January 2025 (UTC) | |||
*'''Oppose unblock''' as the user looks to have no intention of following Misplaced Pages guidelines with their request. It is only a week and will give a change to think about how to change. ] (]) 04:13, 16 January 2025 (UTC) | |||
*'''Oppose unblock'''. It truly takes some ] to cite a Signpost piece authored by the admin who blocked you to support the proposition that you're being railroaded. '''Weak support for an indef''' because that's what Lardlegwarmers seems to be speedrunning. ] (]/]) 04:30, 16 January 2025 (UTC) | |||
*'''Oppose unblock'''. The topic ban was on ''the topic of COVID-19, broadly construed'', not ''the topic of COVID-19 directly in articlespace''. And the topic ban was violated, not just within less than a day, but ''within three hours'' of it being imposed. On top of that the unblock request could be a case study for ]. I won't call for an indef ], but when the block expires Lardlegwarmers should bear in mind that any further violations of the topic ban will be their last. - ] <sub>]</sub> 10:10, 16 January 2025 (UTC) | |||
*'''No unblock''' - Basically per Lardlegwarmers: they don't appear to understand why they've been blocked. An indefinite block seems very likely in this editor's future and we certainly should consider cutting out the middle-man and just skipping to it, but I'd like to give them at least some chance here to understand why they were blocked. ] (]) 10:12, 16 January 2025 (UTC) | |||
* '''Oppose unblock''' - While I usually support giving editors ] to demonstrate improvement, this case warrants a longer wait. The user acknowledges pushing a minority POV and failing to disengage per ] norms, but their justification suggests a lack of understanding or acceptance of policies like ], ], and ]. Their off-topic comment in an AE thread, despite knowing the sensitivity of such spaces, and the policy-violating content on their user page, further reflect ongoing disruption. I recommend they take time to reflect and gain a better grasp of Misplaced Pages's collaborative culture before requesting an unblock again. ] • ] ⚽ 11:31, 16 January 2025 (UTC) | |||
* '''Oppose unblock'''. I agree that absent change from this user an indefinite block is likely. For their benefit, if you're the subject of a topic ban, broadly construed, about COVID-19, you need to be editing in an entirely different topic area. Think of something that you're interested in--television shows, football, English gardens, science fiction books? Take a week and think on it. ] ] 11:42, 16 January 2025 (UTC) | |||
*'''Oppose unblock.''' What is there left to say? This conduct feels like appellant's purpose is use Misplaced Pages as a battleground and to soapbox their views rather than to build the encyclopedia-- to remake Misplaced Pages as they think it should be. My feeling is that a week won't be nearly enough. The railroad comment is appallingly full of not understanding that their conduct is not acceptable in a collaborative project. ] (]) 12:28, 16 January 2025 (UTC) | |||
*:PS: What Tamzin said in her statement above. ] (]) 12:33, 16 January 2025 (UTC) | |||
*::Whilst I don't believe user will be able to change their approach, I feel an indef would be premature for now. We should give them a chance to mend their ways. ] (]) 12:44, 17 January 2025 (UTC) | |||
*An account that ] is topic banned, violates that topic ban immediately, and posts a ] unblock request that thoroughly ]. Whoever closes this should be considering indef, not an unblock. — <samp>] <sup style="font-size:80%;">]</sup></samp> \\ 13:57, 16 January 2025 (UTC) | |||
*:Indeed. ] (]) 14:55, 16 January 2025 (UTC) | |||
*'''Oppose unblock''' this specific response {{tq| Misplaced Pages's culture sort of revolves around social dynamics and politics, which can overshadow fairness and consistency in rule enforcement}} is indicative of their viewpoints and why they're not ready to contribute. They continue, {{tq|my attempt to reason things out like grownups was not allowed}}. These demonstrate that they still do not get it, and rather project their self-perspective is that they are actually a victim of people who are abusing the rules against them. . I proffer that this is going to be a consistent problem until they acknowledge that they were violating policy. Zero indication that they know how to positively contribute, just perhaps a vague inference that they'll avoid getting in trouble -- because -- we'll I'm not entirely sure they've communicated what they will do differently, but rather simply say that {{tq|a block for this stuff seems harsh.}} ] ] 15:12, 16 January 2025 (UTC) | |||
*:Notwithstanding the harsh situation I presented above, to be clear I '''oppose indef''' for now. A new user should have the opportunity to overcome early (while significant) setbacks, which is what TBANs are designed to encourage. I am encouraged by things like YFNS corrective behavior in a prior AN discussion, and can only be hopeful and AGF that might apply to LLW here. We need more passionate, subject matter experts, as contributors to this project, but they ''absolutely must contribute positively'' and following established PGs. ] ] 16:34, 16 January 2025 (UTC) | |||
*'''Oppose unblock''' and support an indef. I am pretty confident in saying that this is where we will be heading after this block ends. ] (]) 15:20, 16 January 2025 (UTC) | |||
*'''Oppose unblock''', clear violations of the topic ban. Don't oppose indef, but I'd like to at least give him the chance to figure out exactly what we expect going forward. --] 15:52, 16 January 2025 (UTC) | |||
*'''Support block, oppose unblock, oppose indef''' - this is a topic-banned newbie's first violation, in the heat of the moment after the restriction was imposed. Tamzin's block was the appropriate response. The unblock request is wholly inadequate, but jumping straight to indef for this sort of violation is a pretty extreme overreach. If they go back to violating their sanction after this block expires, ''then'' let's talk community ban, but they should be given the opportunity to edit constructively while respecting the restriction. ] (<sup>]</sup>/<sub>]</sub>) 16:07, 16 January 2025 (UTC) | |||
*'''Oppose unblock, oppose indef...however...''' I am sympathetic to their point of view and their general "right" (we don't really have rights here on WP) to post their opinion on a subject, even one as contentious as COVID-19. I think the blanking of the user page is a step too far. We shouldn't be in the business of deleting negative opinions about Misplaced Pages; while the statement was in reference to COVID-19, it doesn't mention it within the claim and is more a critique of Misplaced Pages at large and mass media than its relation to COVID. I would let the statement on their user page stand/restore it. Larry Sanger's statement is not a ], it is a reasonable ''opinion''. There were loads of statements/claims about COVID/its origin/mandates/treatment/vaccines that, despite their widespread implementations and presentation as "the science", later turned out to be misleading or untested conjecture (examples: no studies on masking effectiveness with a large population vs the coronavirus, 6 foot spacing, lying to the American public about wearing masks because health care professionals needed them more, lab leak theory, military connections to the Wuhan Institute, US funding of WI, etc). '''HOWEVER''', civil discourse ''is'' essential. That means that discussions about COVID were fraught with battlegrounds and bludgeoning. As such, we have additional restrictions for COVID discussions and other contentious topics and LLW needs to follow them. LLW did not do so and has shown a consistent flaunting of these restrictions and a weeklong block is a reasonable start. In summary, the quote isn't unreasonable to leave on their user page (give them that latitude), but a weeklong block for the other behavior should stand. ] (]) 16:15, 16 January 2025 (UTC) | |||
*:They added two comments to their userpage. Both were critical of Misplaced Pages. One was also critical of ] and other aspects of the US government's COVID response. I removed the latter. It doesn't matter whether Sanger's opinion is fringe or not; what matters is that he was talking about COVID. I would be quite the hypocrite to remove something from someone's userpage just for criticizing Misplaced Pages, as I have a fair bit of that on my own userpage. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 17:02, 16 January 2025 (UTC) | |||
*::There's some pretty big overlap there in criticism of Fauci and how it is handled on Misplaced Pages. Again, I don't feel THAT is a significant violation of COVID editing restrictions (beyond the fact that they did it despite such an editing restriction). Anyone can completely skip over it if they wish. {{ping|Tamzin}} playing devil's advocate for a moment, what if I published the same thing on my user page? Would it be ok? Would it be ok if I posted it on LLW's user page (as long as LLW was ok with it, of course)? I realize we're getting in the weeds of a "what-if..." but if so, what's the substantive difference between me putting it on a user page and LLW doing the same? ] (]) 17:19, 16 January 2025 (UTC) | |||
*:::If you posted it to your userpage, it would be fine (although not that constructive), because you are not topic-banned from COVID. If you posted it to their userpage, that would be ] for a banned editor, since I'd struggle to believe you have an independent reason to think that particular quote belongs on that particular page. {{PB}} If you really want to fight the removal from the userpage, feel free to create a subsection here, but I stand by the removal. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 17:29, 16 January 2025 (UTC) | |||
*::::I'm not fighting the removal per se. Just wondering where the boundaries are and if it's wise to have such a boundary. ] (]) 17:55, 16 January 2025 (UTC) | |||
*:::::The boundary is ]. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 19:17, 16 January 2025 (UTC) | |||
*:::Buffs: In the ''realm of hypothetical'' I would presume that if that quote had been on LLW user page for a long time, in a sea of content, pre-existing AN, then it ''might even still be up today.'' However, on the other hand, to post that after the TBAN was imposed is nothing other than what can be seen as ''abject defiance'' to the ban. But beyond that, it simply violates plain language of the ban, as it applies to {{tq|all pages (not only articles) broadly related to the topic}}, so I proffer that Tamzin is clearly in the right here. To your charged statement about ''if you were to post the same thing'' to your user page, prior to your statement here and presuming you were not under a TBAN, it would ''not be questioned'' one iota. However, as a response to this discussion, it could be construed (but not technically violating) the principles of ] and I would caution against it. Moreover, you reinstating it on LLW talk page would be a far closer in the proximity of violating PROXYING. ] ] 18:49, 16 January 2025 (UTC) | |||
*::::The fact that the comment only came after the topic ban is key here. I'm fairly sure I've seen several cases where there's something on an editor's user page which is covered by a topic ban but which no one has said or done anything about because it was there from before the topic ban. In fact I'm fairly sure I even remember a case where someone asked specifically if they could modify or remove something on their user page which related to their talk page which was technically under the topic ban (probably gensex). I think this was allowed especially since it related to their personal life rather than some comment on something, although they were told just this once is best. There might have even been a case where an editor wanted to do some more editing or formatting of something under their topic ban and was either denied or told only this once. IIRC, there was also an editor who was happy to be able to finally change someone on their userpage covered by their topic ban once it was lifted. A topic ban is a topic ban. I'd note that if someone makes an extremely constructive edit to an article that is not covered by ] we still treat this as a topic ban violation, although it's something much more beneficial for the project than an editor being able to repost random ramblings about Misplaced Pages they want to share. ] (]) 20:31, 16 January 2025 (UTC) | |||
*'''Oppose unblock, oppose indef''' - The topic ban violation was clear cut. Let's hope Lardlegwarmers will read a bit about how to avoid topic ban violations, or else indef block is not too far for them. ] (]) 16:19, 16 January 2025 (UTC) | |||
*'''Oppose unblock, extend block indefinitely''' - Lardle should try to demonstrate good behavior on another wiki for six months before asking for a SO. Let's hope that this user should handle contentious topics carefully in the future. ] (]) 18:35, 16 January 2025 (UTC) | |||
*'''Oppose unblock''' but no reason to indef, a block has already been imposed. If the user continues to violate the TBAN, than a longer block might be warranted. ''']]''' 02:43, 17 January 2025 (UTC) | |||
=== Comments from involved editors === | |||
] ] to say that they oughtn't have closed, since their Talk Page is decorated with a quote by ] (a participant in the RfC, who voted in alignment with Tranga's close), which includes: {{tq|...I sympathise with the silenced underdog in so many conflicts, be they Aboriginals or Palestinians or Tibetans. This as far as I am aware does not translate into being uncomfortable with my country of origins, or antisemitic, or hostile to Chinese. ...}}. Tranga disagreed; ] and ] agreed and asked Tranga to revert; Tranga declined. | |||
* Going to open a new subsection here since I've made comments to ] two weeks ago. I wish I could say I was surprised that this ended in tears but that would be untrue (though I did have some hopes the comment a month ago indicating they were aware pro-fringe POV-pushing was sactionable was a signal they were intending to modify their behaviour). As bɜ:ʳkənhɪmez points out, making thinly veiled attacks is not exactly the type of thing looked favourably upon in an unblock request. Nor is making polemical statements on one's user page, whether within the scope of the ban or not, likely to convince the community of one's inclination and ability to ]. Lardlegwarmers, if you do really want to return to editing, especially if you want to appeal your topic ban in 6 months or a year, I would strongly advise reading ] and following the advice there, especially ]. Complaining about Hob's conduct won't help you here, because the block (and it's a rather short one) and ban are about you, not Hob. Given your comment that {{tq|apparently two wrongs make a right}}, I had hoped that you were already also considering your own behaviour, but I would like to make it very clear: taking the role of one of the "wrongs" to address someone else's "borderline uncivil" behaviour is ]. Whether Hob crosses the line is on them, but what you do is entirely on you. ] (] • ]) 07:16, 16 January 2025 (UTC) | |||
* As I was involved in the discussion to topic ban LLW I think I count as an involved editor. With that said I would discourage an early lifting of this block, which seems appropriate considering that LLW's response to the topic ban was to immediately violate the topic ban. ] (]) 13:54, 16 January 2025 (UTC) | |||
*:Also, perhaps LLW wasn't aware of this, but people who aren't uninvolved administrators aren't generally supposed to put comments into the "results" section of an AE filing. ] (]) 13:57, 16 January 2025 (UTC) | |||
* I was there.. Three thousand ye-- No. More like one, two days ago. I seriously believe Lard Leg Warmers is one of two situations: '''1:''' ] and unable to understand the concepts of medical science as if they were a Facebook mother invested in "essential oils" and "holistic medicine" rather than trusting medical and scientific experts; '''2:''' ] and simply f<s>**</s>king with us for no good reason and leading us around, and around, and around, and around, and around the bend because they get a rise out of it. Either way, my advice: don't get led around the bend, '''advise indef block''' for either ] or ]. <span style="text-shadow: #E9967A 0em 0em 1em;">]]</span> 16:38, 16 January 2025 (UTC) | |||
::], those kinds of personal assumptions about their character are unnecessary to this discussion. Instead of speculation on who they are elsewhere, let's just focus on their behavior on Misplaced Pages. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 06:45, 17 January 2025 (UTC) | |||
*Lardlegwarmers' statement clearly shows that they have learned little from the sanction. They should demonstrate such before there is any lifting. ] (]) 18:55, 16 January 2025 (UTC) | |||
{{abot}} | |||
== Usage of 'Notable people' vis-a-vis 'Notable person' in section headers == | |||
Back at RSN, ] , writing that an RfC should not be partially closed, that this RfC is so long and big that it should be closed by an admin, and that {{tq|the provided justification (just a head count) was doubtful.}}. ] took place before being hatted by ], who directed towards AN. | |||
{{atop | |||
| result = This is not an administrative issue. ] (]/]) 20:56, 16 January 2025 (UTC) | |||
}} | |||
In the course of editing numerous articles, I have come across the header featuring 'notable people' when there is only one person and have therefore modified the grammar. | |||
I hope this post is not malformed—I've never posted here before. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 21:37, 18 June 2024 (UTC) | |||
:Ah, and ] on FortunateSons' Talk. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 21:40, 18 June 2024 (UTC) | |||
I recently had another editor come behind me and revert one such edit on the grounds that things have always been done this way, regardless of the number of notables for a given locale, which makes little sense to me. Is this really policy? ] (]) 16:45, 16 January 2025 (UTC) | |||
=== Participants === | |||
:This seems like a question for ], not ] as it doesn't involve administrator actions. AN isn't a general Help forum for questions about editing. You could even try asking at ] or the Help Desk. <span style="font-family:Papyrus; color:#800080;">]</span> <sup style="font-family: Times New Roman; color: #006400;">] ]</sup> 19:00, 16 January 2025 (UTC) | |||
{{abot}} | |||
*'''Overturn''', per ]. If you are partisan about the conflict to the extent that you feel you need to have quotes expressing that partisanship on your user talk page then you are too partisan to be closing RFC’s about the conflict. ] (]) 21:40, 18 June 2024 (UTC) | |||
*'''Overturn''', in line with the arguments made in the discussions. This is a controversial and significant RfC in a contentious area, and the non-admin closer has a quote by one of the participants about the topic area on top of his talk page. Even if one were to excluding the issues with a partial close (acknowledging that the RfC is quite long), the style of closure (including the heavy reliance on !vote count) is not even close to appropriate in this area, and the closer being an experienced editor ] Close should be reverted <small>and closer trouted</small>. ] (]) 22:08, 18 June 2024 (UTC) | |||
*:In line with BADNAC Nr. 2, it is my belief that exclusively an admin closure would be appropriate here. ] (]) 22:11, 18 June 2024 (UTC) | |||
* '''Endorse'''. The spirit of ] would discourage us from overturning an ] on mere technicality (and a technicality that is a stretch since TrangaBellam did not participate in the RFC) and with limited sense that the outcome could be different. As TrangaBellam observed in ] (), {{tq|There is no way that the discussion could have been closed differently by someone else, short of supervoting}}. Additionally, OP calls TrangaBellam's closure reason {{tq|just a headcount}} but this is a misrepresentation. The full closure reads, {{tq|I see a consensus for Option 3 — going by the numbers (roughly, 3:1) ''as well as the relative strength of arguments'' — and note that most of the participants were okay-ish with deprecation too}} (italics added). ] (] | ] | ]) 22:32, 18 June 2024 (UTC) | |||
*'''Endorse''' - why would anyone waste time asking for this to be re-closed? It's 3:1 for pete's sake. Make an argument for why this was anything other than an "option 3" close, and then maybe you have reason to challenge. Otherwise, you're literally wasting other volunteers' time by asking someone else to make the same edit that Tranga made (an Option 3 close). ] (]) 22:44, 18 June 2024 (UTC) | |||
{{ctop|Request all involved editors to take a step back and let this close review not devolve into a unreadable mess as the RFC did. ] (]) 00:46, 19 June 2024 (UTC)}} | |||
*:I don't think vote count should matter here—the policy-based substance of the votes is what needs to be taken into account. A number of option 3 and 4 votes were just criticism of the ADL as an actor, without bearing on its reliability in reporting fact. A sensitive closer would need to look carefully at the arguments made, and certainly provide a better summary than a rough ratio of votes and a simple declaration of "I weighed the arguments". <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 23:28, 18 June 2024 (UTC) | |||
*::@]: I'm going to put you on the spot here, apologies but I'm gonna do it. Be honest with us: before you made this close challenge, did you re-read the entire RFC from top to bottom? ] (]) 23:34, 18 June 2024 (UTC) | |||
*:::Of course not—really I was just bringing a scattered discussion that had been repeatedly pointed to AN over here. But I did look through long, detailed votes for 3/4, and I do believe a lot of them fail to make policy-based arguments, and instead just explain why the ADL is a bad organization (but not an unreliable source). In general I don't like vote count as a major consideration in determinations of consensus, since votes often come with poor or no policy-based rationale. In an RfC as big as this one, a closer who says "The ratio's big; the arguments win" is, considering my reading of the arguments made, not good enough. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 23:38, 18 June 2024 (UTC) | |||
*::::No of course not, because who has time for that? Just Part 1 is 17,300+ words; at an average reading speed of 200wpm, that's damn near an hour and a half of reading. You didn't volunteer an hour and a half of your time to read that thing, but what you want is an hour and a half of someone else's time (more than that, really, to close), ''after'' somebody already spent that 90+ min. | |||
*::::And why are you asking for someone else to spend 90+ min on this? Because maybe, ''maybe'', the weighing of arguments would result in a no consensus? Don't you think ''you'' should first spend the 90 min to determine if that's likely, ''before'' asking someone else to do so? And in fact, it's more than one person spending 90+ min, because editors now have to spend time on this close review. And of course, nobody who is voting here (myself included) is going to spend 90 min reading this before they vote on whether to overturn it or not. | |||
*::::So you're really raising a ''purely procedural'' objection to this giant RFC, not a substantive one. You have no idea whatsoever if a "no consensus" outcome is even plausible because you haven't read the whole thing (at least lately). This is why I think this challenge is a waste of time. Hours of editor time will be spent on what is very, very, very, ''very'' unlikely to be anything but an "option 3" result. | |||
*::::Can you think of a time when dozens of editors voted in an RFC, it was 3:1, and the minority prevailed? Or it was even no consensus? I can't. | |||
*::::I count 50 votes in Part 1. If it's a 3:1 ratio, that's like 36:12. So we'd need to discount like 20 votes in order for it to be no consensus. Can you point to 20 votes that should be discounted? Can you list 10? | |||
*::::I really feel like, before you ask other people to do this much work, you need to do the work. Read the thing. Identify 10 or 20 bad votes. ''Then'' decide whether to challenge. ] (]) 23:52, 18 June 2024 (UTC) | |||
*:::::{{tqb|Can you point to 20 votes that should be discounted? Can you list 10?}} | |||
*:::::Considering ] and ], yes; most votes for option 3 simply say it is biased; too pro-Israeli or too willing to equate criticism of Israel with antisemitism. Some of these !votes did include sources to support their views - but as these sources only said that it is biased, not unreliable, that doesn't increase the weight their !vote should be given when ]. ] (]) 00:02, 19 June 2024 (UTC) | |||
*::::::Equating criticism of Israel with antisemitism, or equating anti-Zionism with antisemitism, isn't bias, it's unreliability (because criticism of Israel and anti-Zionism are factually not antisemitism). Everyone who said that made an argument for unreliability (which, I think, is most). It's like: if you say the sun rises in the West, that's not bias, it's unreliability. ] (]) 00:05, 19 June 2024 (UTC) | |||
*:::::::{{tq|because criticism of Israel and anti-Zionism are factually not antisemitism}} It is possible for criticism of Israel to be both criticism of Israel and antisemitic; it is possible for a statement to be both anti-Zionist and antisemitic. I don't think this is controversial? | |||
*:::::::Whether a specific criticism of Israel or a specific anti-Zionist statement is antisemitic can be controversial, but it is largely a matter of opinion; there isn't a single objective definition of antisemitism by which we can decide if a source is right or wrong. Instead, as ] tells us, we consider all reliable sources - including those that we consider too quick to label something antisemitism ''and'' too slow, and decide if the label is ] to include in the specific case under consideration. ] (]) 00:17, 19 June 2024 (UTC) | |||
*::::::::Of course it's possible for something to be criticism of Israel or anti-Zionist and also antisemitic. And it's possible for something to be the former and not the latter. As many editors pointed out in the discussion, the ADL equates ''all'' criticism of Israel and anti-Zionism with antisemitism. This was backed up by sources in the discussion making this exact point, as well as sources from the ADL making this exact point. And that's what makes ADL unreliable, not just biased, in the view of a 3:1 majority. ] (]) 00:19, 19 June 2024 (UTC) | |||
*:::::::The ADL has certainly never said "criticism of israel and antisemitism are the same thing", and that's not something being alleged about them. Their "equating" would be better described as "evaluating anti-Zionism to be antisemitic", which is a subjective assessment—as valid (and subject to criticism) as any in the messy realm of bigotry and discourse, and not a matter of fact or definition.{{pb}}I wouldn't consider someone unreliable on facts relating to, say, women and sex, just because they'd evaluated marriage to be a sexist institution. They're not compromising their factual reliability by pushing the untruth that misogyny and marriage are literally equivalent (and thus misidentifying marriage as misogyny): they're only putting forth their POV that marriage is generally misogynistic. That's what, per voters favoring a GUNREL/deprecation designation, the ADL does with anti-Zionism and antisemitism. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 00:36, 19 June 2024 (UTC) | |||
*::::::::Evaluating anti-Zionism to be antisemitic is ''not'' a subjective assessment. Anti-Zionism ''is not the same thing as'' antisemitism, period. For example, Jewish anti-Zionists are ''not'' antisemitic. Holocaust survivor anti-Zionists are ''not'' antisemitic. ''Period.'' This is why the ADL's reputation for reliability has plummeted in recent years: because they are saying that anti-Zionism is antisemitism, and they call Jewish anti-Zionist groups antisemitic. ] (]) 00:43, 19 June 2024 (UTC) | |||
*:::::I'm not convinced that 90 minutes were spent, judging by the one-sentence summary.{{pb}}I do have some idea of whether a no consensus result is likely, because I've read the longest votes, which are broadly cited by the people not providing original rationales, and I think the 3/4 votes are largely not policy-based.{{pb}}{{tqb|Can you think of a time when dozens of editors voted in an RFC, it was 3:1, and the minority prevailed?}}I'm a new editor here—I opened this account as a child, but didn't begin getting involved with editing until about a year ago. So I don't know. I hope the answer is yes! Bad arguments may sometimes overwhelm, and I hope a closing admin would put policy first and not consider the popularity of arguments not rooted in WP policy.{{pb}}I may look through and count bad votes, but I might not, because I think even just on procedural grounds, an RFC with over 700 comments need a sensitive admin reviewer who will provide a detailed summary of the discussion. But I thank you for your feedback (earnestly). <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 00:05, 19 June 2024 (UTC) | |||
*::::::There is nothing about admins that makes them better closers than non-admins. ] is an essay, whereas ] is that a NAC cannot be overturned simply because it's a NAC (read, for example, ], ], ], and see how they all explicitly state that non-admins can close discussions just like admins). | |||
*::::::I haven't been around that long -- 5 years -- but I've never seen a 3:1 go the other way when there are dozens of editors participating (it's different if there are only 4 editors participating and it ends up 3:1). | |||
*::::::And I AGF that Tranga spent the time reading the whole thing before closing it, even if she only wrote a short summary. If you challenged this on the grounds that the arguments need to be summarized better in the closing statement, I'd support that. | |||
*::::::Thank you for being a good sport about me getting all huffy :-) ] (]) 00:17, 19 June 2024 (UTC) | |||
*:::::::] wasn't 3:1 - closer to 2:1 - but given that 150 more editors supported rolling back than opposed it I would suggest the result to not rollback would be similar to the result with a higher ratio but lower !vote count. ] (]) 00:22, 19 June 2024 (UTC) | |||
*::::::::Touche! That is a "big" overturn. I'm still not ''technically'' wrong, though :-D But surely you'd agree it's extraordinarily rare for a majority in a well-attended discussion to be overturned, and V22 is probably the most extreme counterexample, I still can't think of another one (although admittedly my memory is not very good as you've just proven). ] (]) 00:25, 19 June 2024 (UTC) | |||
*:::::::::It is very rare, though I believe less so in areas where editors are more likely to !vote based on their personal opinion - whether because it is a matter of personal opinion, such as the format of the website, or because the topic area is highly contentious in the real world. | |||
*:::::::::I'm pretty sure I've seen other examples but I can't think of any off the top of my head, and I don't have time to look right now - if I get the chance before the appeal closes I will (and if I don't, I might look later and post on your talk page if I find anything, solely to satisfy my curiosity and because I think the discussions would make interesting reading). ] (]) 00:33, 19 June 2024 (UTC) | |||
*::::::::::<small>Meanwhile I will not embarrass myself by blindly claiming that there are no other examples {{lol}} ] (]) 00:40, 19 June 2024 (UTC)</small> | |||
*::::::A few bad votes for options 3 and 4 which are or contain criticisms of things other than the reliability of the ADL's reporting:{{pb}} | |||
:::::::#{{tq|Its CEO publicly comparing the pro-Palestine protestors wearing keffiyeh with Nazis wearing swastika armbands as well as mispresenting all pro-Palestine protestors as "wanting all zionists dead" demonstrates its skewed views and manipulative presentation on the IP topic and thus highly unreliable.}} | |||
:::::::#{{tq|After AIPAC, the ADL is the primary propagandist for Israel in the United States. All of its pronouncements regarding Israel are based on the advocacy role it has adopted and not based on an unbiased analysis of the facts.}} | |||
:::::::#{{tq|because as discussed earlier, it is partisan pro-Israel advocacy group which has historically been engaged in espionage and defamation campaign against pro-Palestinian activists, and its broadened definition of antisemitism. Their reliability on the topic has been put into question by the Guardian and the Nation, both RS per WP. Attribution is required for any claim; and for controversial claims, probably best not to be used at all.}} | |||
:::::::#{{tq|Option 4 The ADL has consistently misidentified critics of Israel as anti-Semitic, has proven credulous to disinformation that supports Israel and has experienced negative reputational outcomes from its engagement on the topic. It should not be used as a source as it is thoroughly unreliable.}} (I consider this one to not be about reliability because it just expresses a difference in opinion with the ADL's subjective evaluations of critics' sentiments—not an error of fact. Certainly the ADL would never be used to state in Wikivoice that a critic of Israel is an antisemite.) | |||
:::::::#{{tq|The ADL has consistently called for laws and measures that consider as possible examples of connivance with terrorism significant movements which protest in solidarity with an occupied people, i.e. Palestinians. It does this because its agenda tends to collapse core distinctions between demonstrating on behalf of human rights (in Israel/Palestine) and anti-Semitism defined as anti-Zionist disavowels of the legitimacy of Israel as a state. In its practice, advocacy for Palestinian human rights should be subject to criminalization. (Alice Speri, How the ADL's Anti-Palestinian Advoacy Helped Shape U.S. Terror laws, The Intercept 21 February 2024)<br>For its director Jonathan Greenblatt, opposition to Israel/anti-Zionism (by which he appears to mean criticism of Israel’s human rights record) is intrinsically ‘antisemitic’. His position was so extreme that even ADL staff protested at the equation of critics of Israel with those white supremicists groups which the ADL has distinguished itself in exposing. (Jonathan Guyer, Tom Perkins, Anti-Defamation League staff decry ‘dishonest’ campaign against Israel critics The Guardian 5 January 2024).<br>(Justin) Sadowsky (of the Council on American–Islamic Relations), who is Jewish, characterizes some of ADL’s actions as part of a pattern of deliberate intimidation to make it “very difficult for Palestinians to talk in a forthright way about what’s going on”, (Wilfred Chan ‘The Palestine exception’: why pro-Palestinian voices are suppressed in the US The Guardian 1 November 2023). And they do distort information, because their lists of antisemitic incidents do not discriminate between normal protests and serious incidents of antisemitic behaviour. Spitting on Christian priests in Jerusalem is commonplace and the ADL has protested the practice regularly, but, if that is noteworthy for them, the same cannot be said for protesting extreme human rights violations by Israel against Palestinians, which are endemic and yet, it appears, not noteworthy.}} | |||
:::::::#{{tq|Option 4 the simple fact is that ADL is an aggressively pro-Israel organization which considers even questioning the legitimacy of Israel (a very young state founded under circumstances that are extremely dubious to day the least) makes it inherently biased. I’m not trying to wade into the “let’s use Misplaced Pages as a proxy to argue about Israel/Palestine” fight but the rough equivalent would be an Afrikaner advocacy group saying questioning the legitimacy of European colonization in South Africa is racist.}} | |||
:::::::#{{tq|it's a pro-Israeli lobbying group, not scholarship or journalism, and equates criticism of Israel or anti-Zionism with antisemitism ...}} Later comment responding to the fact that the advocacy group the SPLC is a reliable source: {{tq|The ADL very explicitly lobbies on behalf of Israeli (foreign) interests.}} | |||
:::::::#{{tq|The sources clearly demonstrate a severe bias in matters AI/IP, inclusive of weaponizing charges of antisemitism for political purposes in this area.}} | |||
:::::::#{{tq|The ADL has shown itself to be far too pro-Israel in their ongoing war against Hamas and have used their platform to attack people who have protested against Israel's actions. They are at the forefront of groups who try to equate even the slightest criticism of Israel's policies with anti-semitism. They also have recently been providing incidents of anti-semitism without evidence. An article they released recently conflated anti Israel protests on last weekend as being exclusively protests praising the actions of Hamas and included descriptions of signs yet did not provide photographic evidence of the more inflammatory signs they alleged to have seen. They have also called Jewish activists who do not support Zionism or Israel's policies as anti-semitic or useful idiots for anti-semites such as when they said that Jewish Voice for Peace was " its Jewish identity to shield the anti-Israel movement from allegations of anti-Semitism and provide it with a greater degree of legitimacy and credibility." Additionally, they've repeatedly denied that American police officers travel to Israel to train in spite of the fact the ADL themselves have routinely paid for these very programs that they deny. Since October 7th, they've increasingly squandered their credibility as an authority on racism and hate in support of an increasingly unpopular foreign conflict that the international community has grown to condemn, even among governments that have supported Israel such as the United States.}}This one explicitly states that the ADL has fucked its credibility as an authority on racism and hate—not the I/P conflict. | |||
:::::::#{{tq|ADL is an explicitly biased pro-Israel advocacy group and its claims are not at all reliable regarding Israel-Palestine conflict. I'd support deprecating this source if some editor can demonstrate that this group promotes zionist or republican/neo-con conspiracy theories.}} | |||
:::::::#{{tq|Option 3, very clearly a strongly pro-Israel biased organization, shouldn't be used as a source.}} | |||
:::::::{{pb}}There's a theme here of "the ADL as an organization suuuuucks", and even "the ADL is biased", in the absence of "the ADL's factual reliability as a source suuuuuucks". Many of these comments, including others which included links to supposed inaccuracies, were criticized by other participant editors as not pertaining to the I/P subject area and not supporting unreliability, only bias. One editor voted 3 and acknowledged {{tq|Obviously it is a highly WP:BIASED source on that and could never be used on the topic without attribution, but that alone wouldn't make it unreliable}}, and then proceeded to cite three sources that are all about the ADL's handling of facts about antisemitism, and not about the Israeli/Palestinian conflict. Someone pointed out: {{tq|Almost none of the comments above actually relate to ADL's claims about I/P but rather to its claims about antisemitism, the topic of the survey below.}}{{pb}}A lot of these rationales were then cited by later voters. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 00:29, 19 June 2024 (UTC) | |||
*:::::::* mispresenting all pro-Palestine protestors as "wanting all zionists dead" | |||
*:::::::* has historically been engaged in espionage and defamation campaign against pro-Palestinian activists, and its broadened definition of antisemitism. Their reliability on the topic has been put into question by the Guardian and the Nation | |||
*:::::::* consistently misidentified critics of Israel as anti-Semitic, has proven credulous to disinformation that supports Israel and has experienced negative reputational outcomes from its engagement on the topic | |||
*:::::::* tends to collapse core distinctions between demonstrating on behalf of human rights (in Israel/Palestine) and anti-Semitism defined as anti-Zionist disavowels of the legitimacy of Israel as a state | |||
*:::::::* For its director Jonathan Greenblatt, opposition to Israel/anti-Zionism (by which he appears to mean criticism of Israel’s human rights record) is intrinsically ‘antisemitic’. His position was so extreme that even ADL staff protested at the equation of critics of Israel with those white supremicists groups which the ADL has distinguished itself in exposing ... And they do distort information, because their lists of antisemitic incidents do not discriminate between normal protests and serious incidents of antisemitic behaviour | |||
*:::::::* it's a pro-Israeli lobbying group, not scholarship or journalism, and equates criticism of Israel or anti-Zionism with antisemitism (''hey, I recognize that one! :-P'') | |||
*:::::::* They are at the forefront of groups who try to equate even the slightest criticism of Israel's policies with anti-semitism. They also have recently been providing incidents of anti-semitism without evidence. An article they released recently conflated anti Israel protests on last weekend as being exclusively protests praising the actions of Hamas and included descriptions of signs yet did not provide photographic evidence of the more inflammatory signs they alleged to have seen. They have also called Jewish activists who do not support Zionism or Israel's policies as anti-semitic or useful idiots for anti-semites ... they've repeatedly denied that American police officers travel to Israel to train in spite of the fact the ADL themselves have routinely paid for these very programs that they deny | |||
*:::::::* its claims are not at all reliable regarding Israel-Palestine conflict | |||
*:::::::I see the above quotes as being policy-based arguments, rooted in ], addressing reliability, not bias. ] (]) 00:38, 19 June 2024 (UTC) | |||
*::::::::See my above comment on the factualness of assessments of antisemitism. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 00:40, 19 June 2024 (UTC) | |||
*:::::::::And again, a lot of these comments make no argument about unreliability in the Israel/Palestine topic area. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 00:43, 19 June 2024 (UTC) | |||
*::::::::::Literally every single bullet point has the word "Israel" or "Palestine" in it. Anti-Zionism is about Israel/Palestine because Zionism is about Israel in Palestine. ] (]) 00:45, 19 June 2024 (UTC) | |||
{{cbot}} | |||
*'''Endorse''' - A user page should have little to no bearing on the outcome of the RfC, and the closure was non-controversial (in the sense that the margin of support for the decision was very clear). An admin closure would almost certainly come to the same decision, as Levivich said, and this contestation doesn't provide any argument that the outcome should have been different. The consensus was overwhelmingly in favor of option 3. As an aside, I have noticed a pattern of users in this topic area relying on userpages to get others into trouble. I don't want to cast aspersions, and I am trying to avoid any generalizing or unfair statements. I know that @], who makes a userpage based argument here, was involved in a similar effort to contest the content on @]'s userpage, which was ultimately put forth as an argument in a later procedure which saw them topic banned. I know that this was not the first time an editor has been dragged to one noticeboard or another over pro-Palestinian sentiment on their userpage. As someone who likes having a userpage, and likes reading the userpages of others, I worry about the chilling effect these efforts have on Wikipedians' self-expression, which is a fascinating and valuable part of the editing and community experience of the website in my opinion. ] (]) 23:10, 18 June 2024 (UTC) | |||
*'''Endorse and overturn'''. I agree with the closure, and I agree that the closure represents consensus, but for a discussion as gigantic and heavily controversial as this one, in the interest of propriety it should be closed by somebody who is beyond question uninvolved; as much as the tripartite panel closes can be groan-inducing, this seems like a good case for one. <b style="font-family: monospace; color:#E35BD8">]×]]</b> 23:57, 18 June 2024 (UTC) | |||
*:concur ] (]) 15:55, 19 June 2024 (UTC) | |||
*:To be clear: for the sake of avoiding silly bureaucratic pissantery, it should not be overturned until such a time as the aforementioned knight(s) in shining armor are willing to make a formal close with proper bells/whistles/hoohas -- since people seem to overwhelmingly agree with the fact of the close itself. <b style="font-family: monospace; color:#E35BD8">]×]]</b> 21:43, 19 June 2024 (UTC) | |||
*'''Close the entire RfC, rather than a section by uninvolved administrator(s)'''. I think this should be an admin closure per guidelines #2, i.e. "The outcome is a close call ... or likely to be controversial." Saying that ] was a "generally unreliable source" is controversial. Commenting on the closure itself, the 3:1 description was fair, but the "strength of the argument" was not. To say that the source was generally unreliable, one should show it was not just biased, but publish incorrect information on a regular basis. I believe this is not at all the case for this source ''after looking at the entire discussion''. That's why I think this RfC should not be closed "by parts". ] (]) 02:55, 19 June 2024 (UTC) | |||
*:Please do not misrepresent the close; it held the source to be "generally unreliable" for a narrow topic area than for everything under the Sun. ] (]) 05:47, 19 June 2024 (UTC) | |||
*::I know that some discussions end up with the conclusion that source X frequently publish misinformation in one subject area, but not in others. I think in all such cases the source ''as a whole'' should be regarded as unreliable. If they are liars, they can not be trusted. If this is not a reputable organization, then it just is not. However, in this case I did not see examples proving that they are liars. Of course I may be wrong. Hence we are having the community discussion that needs to be properly closed. ] (]) 13:41, 19 June 2024 (UTC) | |||
*:::Plenty of sources are reliable for some things but not others. Consider ], highly respected as a linguist, but with rather controversial political views. ] (]) 15:16, 19 June 2024 (UTC) | |||
*::I think we need to prohibit closing RfCs "by parts", as a matter of policy. ] (]) 14:24, 19 June 2024 (UTC) | |||
*:::It's not "by parts", it's 3 RFC's and was set up that way from the start "editors expressed concerns regarding the ADL's current status as a generally reliable source in several topic areas. I'm breaking these topic areas into different RFCs, as I believe there's a reasonable chance they might have different outcomes." ] (]) 15:16, 19 June 2024 (UTC) | |||
*::::So you believe that issues of Israel-Palestine conflict, antisemitism and hate symbols can be separated? No, of course not. ] (]) 15:43, 19 June 2024 (UTC) | |||
*:::::It's not a question of what I believe, I am referring to the way the RFCs were set up, months ago, which no-one objected to at all until now, when the result turned up something people didn't like. Let's face it, looking at this filing, it is a group of option "1" voters, disputing a pretty clear cut result, with any grounds that might work. Personally, I don't mind if it is reclosed, the result will be the same, even if there are more words. ] (]) 15:53, 19 June 2024 (UTC) | |||
*:::::@] multiple commenters have expressed different opinions in the different RFCs, so very clearly people ''do'' believe the three can be separated. ] (]) 15:56, 19 June 2024 (UTC) | |||
*::::::Well, this is just a matter of simple logic and fact. The are numerous subjects and publications that simultaneously belong to all three or two of the mentioned categories (the conflict, and antisemitism and hate). And of course they are closely connected. Here is a random example . Yes, someone set up the RfC in such way. But it was ''wrong set up'' and a reason to say this is '''an incorrectly framed RfC'''. This has noting to do with anyone liking or disliking the outcome. I voted "2" in all parts of the RfC, but I am very much comfortable with any outcome. ] (]) 19:05, 19 June 2024 (UTC) | |||
*'''Endorse:''' This RFC needed closing, and if a piecemeal approach is the way it occurs, so be it. The close was sound and perfectly adequately reasoned. As has been noted elsewhere in the subsequent discussion, closing it any other way would have required a supervote. The closer was meanwhile not an involved participant by any standard reading of the guidelines. Never before have I seen the notion applied whereby "having an editorial compadre in the discussion" qualifies as being involved. Given how many Misplaced Pages editors are well familiar with each other, that would be a ridiculous bar to apply across the project (and this is probably why it doesn't exist). ] (]) 05:09, 19 June 2024 (UTC) | |||
*'''Endorse''' This was a difficult decision on a contentious RfC but clearly closed in GF and within the bounds of reason. ] (]) 05:36, 19 June 2024 (UTC) | |||
*'''Endorse''' The coverage of the ADL is obviously vary varied (anti-Zionism vs. other content vs. hate speech database) and it is unsound to group them altogether and put coverage advocating against genuine (albeit from, in my opinion, a flawed organization) and horrifying manifestations of antisemitism in the same category as ideological drivel used to racism-jacket those who oppose what is credibly accused as a settler colonial state formed on ethnic cleansing that is currently committing genocide. Furthermore, the RfC has obviously gone on far too long and should be closed at this point, even if it is broken apart. ] (]) 05:41, 19 June 2024 (UTC) | |||
*'''Endorse (as closer)''' - To repeat what I wrote at my t/p, {{tq|3 of 4 participants were convinced that Option 3, at the very least, was necessary. There is no way that the discussion could have been closed differently by someone else, short of supervoting.}} Now, I can append a paragraph on why, notwithstanding the numbers, the argument offered by the numerically superior side carried the day but I doubt it would have convinced anyone to not relitigate it. ] (]) 05:53, 19 June 2024 (UTC) | |||
*'''Overturn''' - The extensive engagement and presence of an admin in the RFC (who was doing far more nuanced analysis of both the arguments and the players than a mere headcount) should have been sign enough that *any* non-admin editor (most especially one with clear and public ] concerns) should not have thought it appropriate to step in and take charge on closure matters after an admin (with clear and established track record in the topic space), had studied the arguments extensively, and did not feel there were clear grounds to close in this way. If there were grounds to close on headcount alone (which usually there aren't) it would have been closed by the admin on those grounds - and it wasn't. In fact, the admin did not consider any consensus to have been found in the RFC, ] The closing non-admin, non-involved editor's sudden arrival and action in the discussion, lack of adherence and deference to existing and active admin assessment and recommended guidelines, and ] reeks of a bad faith hijacking of a process that clearly (and was clearly communicated) should only have been overseen to its conclusion by an uninvolved admin. ] (]) 14:27, 19 June 2024 (UTC) | |||
*:@]: Perhaps I am misreading, but it appears you are openly accusing TB of bad faith, in rather obvious violation of ]. ] (]) 16:15, 19 June 2024 (UTC) | |||
*::My statement has been revised for further clarity, and in line with evidentiary concern that there may have been violation ] in the closure process and subsequent appeal process/discussion. ] (]) 17:12, 19 June 2024 (UTC) | |||
*:Just like determining the direction of a close, overturning one requires valid, policy arguments. The many editors here who are opining that an Admin should have closed this discussion are enunciating value preferences, not policy. Admins have no special closing rights and our ] clearly states {{xt|"any uninvolved editor may close most of them – not just admins"}}, reserving closing for Admins only in cases where it's been requested by some party ({{xt|"if you want to request closure by an uninvolved administrator"}}), something that did not happen here. Whether ] is uninvolved or not (I believe they are) is probably a valid source of debate here. However, the idea that they may or may not be an Admin is irrelevant to an analysis of whether the close was handled properly and is an expression of a value preference that would have been properly addressed pre-close, not post-close. ] (]) 17:22, 19 June 2024 (UTC) | |||
*'''Endorse''' This RfC has been sat in ] for over a month, and no admin had stepped forward to close it. So while I agree with the arguments that an admin should have closed it, or a group of partipants, not one person stepped forward to do so (despite suggestions for the latter); hence Part 1 was eventually closed by a non-admin. Despite the initially short and inadequate summary for the close, I still believe it represented the consensus of the discussion. Notably the summary has been expanded and further explains how the consensus was reached, in order to justify the closure. The fact the user in question has quoted a participant in the RfC is far from evidence of WP:INVOLVED, and there has been no evidence provided (that I'm aware of) that the user was involved in the dispute. If evidence were provided, I'd likely change my opinion. I'm otherwise certain that this closure would have ended up at ANI, if the result was GUNREL, simply for different reasons. ] (]) 16:23, 19 June 2024 (UTC) | |||
::If no one wants to close this RfC, this is fine an understandable. Then let's just archive it and let this matter remain undecided. This is frequently happens with other RfC. ] (]) 19:24, 19 June 2024 (UTC) | |||
:::That's not how ] works. It can be archived, but would still end up being closed. ] (]) 19:46, 19 June 2024 (UTC) | |||
*'''Utter waste of time''' - they were/are not WP:INVOLVED, but more importantly I see almost nobody is claiming that this would not be (re-)closed as a 3. Unless you think that an overturn would come with a different result, and I personally think it beyond obvious that it will not, this is a complete waste of time and space. But if yall want to waste the time then I suppose I cant come up with words wise enough to convince you not to. But there is a very obvious consensus for 3, and overturning it will only result in spending more time to end up with the same result. ''']''' - 19:47, 19 June 2024 (UTC) | |||
*'''Reluctant endorse''', or '''endorse and overturn''' - For INVOLVED reasons I'm not a fan of the user in question closing it themselves, but the editor consensus is fairly obvious and I feel as though overturning it only to re-close would be a waste of time and effort. Suggest leaving it up to admin discretion, however - I concur with Jxpg above. ] ] <span style="color:#C8102E;"><small><sup>(])</sup></small></span> 20:32, 19 June 2024 (UTC) | |||
* '''Endorse''' both because I'm not convinced the "INVOLVED" argument holds water (I broadly agree with what Iskandar323 above and Newimpartial below have said), and because NOTBURO, if most people here seem to acknowledge there's no other way it could've been closed without the closer impermissibly supervoting. ] (]) 21:35, 19 June 2024 (UTC) | |||
*'''Endorse'''. Firstly, admins are not special and have no magical ability to be better closers than non-admins - indeed many non-admins are better closers of discussions than many admins. Secondly I remain completely unconvinced by the arguments that TB was INVOLVED. The closer read the discussion (which more than the OP here has done), summarised the close (not ideally at first, but adequately and subsequently improved) and arrived at the consensus that pretty much every neutral party agrees was the right one. ] (]) 22:21, 19 June 2024 (UTC) | |||
*'''Endorse'''-ish, basically per {{u|Black Kite}} below: in a vacuum, I'm not a huge fan of this closure. Ideally I would have preferred a totally uninvolved admin or a panel of such admins close all three sections. However, the consensus in section 1 is extremely clear, and this RFC has stayed open for months without closure. If we vacate the close, whoever closes it is going to close it the same way (because there's no other reasonable way to close Section 1, it's an overwhelmingly clear consensus), and it's likely going to take months to do, which temporarily restores a status quo that there's an overwhelming consensus against. So I don't see a dedication to procedure to be worth it here. (But if whoever closes the other two sections wants to take over the section 1 close, I wouldn't be opposed to that.) ] (]) 01:35, 20 June 2024 (UTC) | |||
== Reporting Administrator Abuse == | |||
=== Non-participants === | |||
{{Atop|I'm going to do the OP a favor and close this with no action against them. Essentially, the OP's misbehavior was pointed out by Acalamari and the OP is trying to present it as Acalamri's misbehavior. If another administrator thinks sanctions against the OP are warranted, that's up to them.--] (]) 23:56, 16 January 2025 (UTC)}} | |||
{{ombox | |||
|text = '''Please note''' that this discussion falls under ] restrictions, and is thus only open to logged-in editors with ]. | |||
] is abusing his moderator powers in order to post unconstructive comments on talk pages, specifically when we were talking about if we should delete the US 2028 election or not, he said "that Drumpf supporters want there to be no more elections so they can remain in power forever doesn't mean we adhere to their delusions by deleting articles here". This is clearly unconstructive, and treating the talk page as a forum. I didn't know he was a moderator when I was removing his comment, and now he left all of these messages on my page and is saying I'm the real vandal here. ] (]) 22:48, 16 January 2025 (UTC) | |||
:So there's two things here. | |||
:* First, TopVat19sEver, you removed other users comments from a talk page (not allowed). A user voicing their opinion is '''not''' vandalism, not in the slightest. If you have a problem with what another user has said on the talkpage, rather than ] (which is only allowed in very specific situations), you should bring it for discussion at an appropriate noticeboard, or preferably ask them to change their own comment. | |||
:* Second, Acalamari, could you please refrain from calling people "Drumpf supporters" and ] on the reasons for nominating an article for deletion? While you're entitled to your opinions, that's borderline (at best) ], especially when you call them "delusional". | |||
:If both users agree to accept what they did wrong here and move forward, I don't think any further action is necessary. -bɜ:ʳkənhɪmez | ] | ] 22:53, 16 January 2025 (UTC) | |||
::Ok, I'm newer to Misplaced Pages, I understand what you are saying, my train of thought was, "this comment looks like vandalism, vandalism on Misplaced Pages is removed, therefore remove". I didn't know that they don't do that for talk pages. Thank you my friend. ] (]) 22:59, 16 January 2025 (UTC) | |||
:::Vandalism has a '''very''' specific definition on Misplaced Pages - see ] for more information on what is not vandalism. Merely calling people names and/or being uncivil, while against the rules, is '''not''' vandalism. There are proper processes for handling other rule violations (such as asking someone to edit their own comments, or asking a noticeboard for help) such as those, but they are decidedly '''not''' vandalism. -bɜ:ʳkənhɪmez | ] | ] 23:01, 16 January 2025 (UTC) | |||
::::Ok thank you for telling me ] (]) 23:02, 16 January 2025 (UTC) | |||
:Where are the ]? ] (]) 22:54, 16 January 2025 (UTC) | |||
*This is a baseless complaint. Ater not editing for months, the OP refactored an AfD that was closed last November. Acalamari rightly warned them for doing that.--] (]) 22:56, 16 January 2025 (UTC) | |||
*:I agree, but at the same time, I think TV19E has a right to be unhappy that Acalamari, an administrator and bureaucrat, was able to cast aspersions and call people names without it being called out at the time as far as I can see. They went about it the wrong way (removing the comment), but that doesn't mean there isn't room for discussion of that comment. -bɜ:ʳkənhɪmez | ] | ] 22:58, 16 January 2025 (UTC) | |||
*::Nope. First, it doesn't rise to the level required of this noticeboard, and, second, it's not at all timely.--] (]) 23:01, 16 January 2025 (UTC) | |||
*:::To be blunt, Acalamari didn't even tell the editor when they ''initially'' reverted back in November (while the discussion was open) where they could discuss further/report if they felt the comment was not appropriate. I'm not suggesting sanctions against Acalamari at all. But to tell a new editor "someone broke the rules and since you didn't report it in the proper way at the time because nobody told you how, they're allowed to break the rules" is clear ]. I think all that's necessary is an apology from Acalamari - TV19E has already explained that they were mistaken as to it being vanadalism. -bɜ:ʳkənhɪmez | ] | ] 23:03, 16 January 2025 (UTC) | |||
*:I didn't edit for a few months because I have to do other things. I was just scrolling around I don't even remember what I was doing and I saw he put it back, I didn't know he was a mod, and it also said you can't edit archived talk pages, which he did, so I reverted his edit. ] (]) 23:03, 16 January 2025 (UTC) | |||
*::That's not true. You modified a closed AfD. Acalamari rightly reverted your edit of an archived discussion.--] (]) 23:06, 16 January 2025 (UTC) | |||
*:::I just said, he is the one who modified a closed AfD, which is not allowed, then I reverted it not knowing he is a moderator ] (]) 23:08, 16 January 2025 (UTC) | |||
*::::He didn't modify a closed AfD. His comment was readded while the discussion was still open, because you removed it in violation of ]. -bɜ:ʳkənhɪmez | ] | ] 23:09, 16 January 2025 (UTC) | |||
*:::::Oh okay this is my mistake then I thought it was after the AfD was closed my bad ] (]) 23:11, 16 January 2025 (UTC) | |||
*:::::Wait hold on, I just looked at it again. He added back his comment after the result was SNOW. On the page when he re added it, it said do not edit the page. ] (]) 23:16, 16 January 2025 (UTC) | |||
*::::::You removed Acalamari's comment as vandalism with the edit summary "subhanAllah". You had ''no right'' to do that. Acalamari restored it, which even though the AfD was closed, they had the right to do in the circumstances.--] (]) 23:27, 16 January 2025 (UTC) | |||
*:::::https://en.wikipedia.org/search/?title=Misplaced Pages:Articles_for_deletion/2028_United_States_presidential_election_(3rd_nomination)&oldid=1257014612 Take a look, this is his edit. When he re added his comment, on the page in red it said '''Do not edit the page''' ] (]) 23:18, 16 January 2025 (UTC) | |||
*::::::The comment never should've been removed in the first place. It's within the spirit of the rules to readd a comment that you improperly removed, even if the discussion had been closed in the meantime. -bɜ:ʳkənhɪmez | ] | ] 23:32, 16 January 2025 (UTC) | |||
*{{ec}} There's no admin abuse here as no admin tools have been used. In case you missed ''"The following discussion is an archived debate of the proposed deletion of the article below"'' with the bright red ''"Please do not modify it"'' at that AfD, I'll repeat the instructions here - don't modify archived discussions.-- ]<sup>]</sup> 22:57, 16 January 2025 (UTC) | |||
*:I was saying Admin abuse because of the fact that he is able to keep his comment on the page when even if he is violating the rules. I'm not a moderator so I can't do anything about. Now I just learned from that guy that they don't remove comments even if its vandalism, now I know. But thats why I reported it here you know. ] (]) 23:01, 16 January 2025 (UTC) | |||
*:He is the one who edited the closed AfD. This was one of the reason why I reverted his edit. ] (]) 23:10, 16 January 2025 (UTC) | |||
*It's very hard to work out what's happening without the presence of diffs. ] (]) 23:02, 16 January 2025 (UTC) | |||
:*{{tq|without the presence of diffs}}. But Ponyo and I have contributed, so you're in the presence of greatness; isn't that better than diffs? :p --] (]) 23:08, 16 January 2025 (UTC) | |||
:*:* ''Tiggerjay is bowing down in great humility before such greatness never before seen in this universe. '' Now.... where is the trout? ] ] 23:24, 16 January 2025 (UTC) | |||
:*:Who am I to disagree with the Jedi? ] (]) 23:52, 16 January 2025 (UTC) | |||
*Okay, I've looked into this. And...surprise surprise, TopVat19sEver was the one who ''origially removed Aclamari's !vote while the AfD was still open'' . Yes, about a day after the AfD was closed, Aclamari reverted this removal , which ''is'' technically "editing a closed AfD" but I would say they were ] to revert a ]. And now, suddenly, today, two months later, as their first edit ''after'' having done that improper removal, TopVat19sEver goes back to the AfD and removes Aclamari's !vote ''again'' , which Aclamari - entirely rightfully - reverted , and then TopVat19sEver comes here to cry "admin abuse", when no administrative abilities were used ''at all'' in this whole mess. Could Aclamari have used more moderate language in their initial !vote? Yeah maybe, but it was no ''violation'' at all, and the only thing needed here is a ] or at least a {{tl|trout}} for TopVat19sEver. - ] <sub>]</sub> 23:27, 16 January 2025 (UTC) | |||
{{Abot}} | |||
== Ban appeal from Rathfelder == | |||
* {{userlinks|Rathfelder}} | |||
* ] for sockpuppetry, vote-stacking and undisclosed COI writing of a BLP attack page | |||
* ] declined by the community | |||
* ] not submitted for review by the community for not complying with ] | |||
Rathfelder has submitted the following ban appeal on their talk page and asked me to copy it here: | |||
{{tqb|I realise that what I did was wrong - more wrong than I thought it was at the time. The circumstances which led me to edit pages where I was conflicted are not likely to recur. I accept that I was wrong to create sockpuppets and I apologise. I was involved in a dispute with my employers and it was very wrong of me to use Misplaced Pages as part of that. I did that really because I was trying to defend the work I had done for the Socialist Health Association for the previous 20 years. I did a lot of edits on that page, but they were, until the last few, about the history of the organisation, mostly adding to its list of distinguished members - largely before I was involved with it, and mostly before I was born. They were not at all controversial. I was unfairly sacked and my opponents started using Misplaced Pages against me. The row got into the media. I accept that I should not have done that. I should have resisted the temptation to use Misplaced Pages in the dispute.<br> | |||
I have spent 2 years working on Simple English and Wikimedia. I have not set up any sockpuppets or edited anything where I had conflicts. I plan to continue with Wikimedia, as there is plenty there to keep me busy, but I would like to be able, in particular, to add pictures to articles - now I have found my way round the enormous Wikimedia resource. I also sometimes come across articles in English wikipedia which need amendment.}} ] (] · ]) 17:02, 17 January 2025 (UTC) | |||
*'''Conditional support''' - If there's been no socking ''during'' the ban. ] (]) 17:05, 17 January 2025 (UTC) | |||
*'''Question''' during the January 2024 unblock request Rathfelder said they would be willing to accept a restriction on editing articles related to BLPs or healthcare orgs. Are they still willing to accept those edit restrictions if they are un-banned? Furthermore, in January 2024 there was, at the time, no evidence of any further socking. Can we confirm that good behaviour has continued? ] (]) 17:17, 17 January 2025 (UTC) | |||
*'''Support''' They have been a very productive contributor at the Simple English Misplaced Pages, and it has definitely been long enough for the ]. ] (]) 21:33, 17 January 2025 (UTC) | |||
== Appealing April 4 2024, indefinite WP:CUP ban and indefinite 1-nomination GAN limit == | |||
{{atopr | |||
| result = Consensus to lift this ban will not develop. ] (]/]) 22:02, 17 January 2025 (UTC) | |||
}} | }} | ||
:'''Overturn'''. I agree that this is such a long and potentially impactful RfC that it'd better be closed by an admin—and I echo ]'s assessment here that an editor who has partisan quotes about an RfC's topic area (especially a quote from one of the RfC's participants) is just not the right person to close the RfC in question. I don't know if partial closes ever happen, but I've never seen one before, and I'm not a fan—it'll certainly have an impact on the unclosed discussions and their outcomes. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 21:44, 18 June 2024 (UTC) | |||
::Seriously? The very point of creating three RfCs was to allow the possibility of different resolutions to be reached on different aspects and, that you have never seen one before, please consult ]. ] (]) 05:44, 19 June 2024 (UTC) | |||
:::Yeah man, seriously. I'd never seen one and I think it was a bad idea. I'm not saying that's your fault, and if it's moot then it's moot—my stance on the close still stands, considering the scale of the RfC, your apparent passionate POV on the topic, your one-sentence summary, and my reading of how that discussion went. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 05:56, 19 June 2024 (UTC) | |||
::::Perhaps then, you can present me with a multiple-part-RfC whose components were closed by the same admin/non-admin/panel simultaneously? And, no, I do not have a "passionate POV" on the topic. As to "your reading of the discussion", you claimed to Levivich about "ofcourse" not having read the entire discussion; so, yeah. In any case, feel free to have the last word. ] (]) 06:02, 19 June 2024 (UTC) | |||
:::::Don't talk to me like that. I brought points raised by several editors to the appropriate venue, where a number of editors are taking the stance that your close ought to be overturned. We're not all bad-faith actors who deserve to have such limp jabs thrown our way as {{tq|feel free to have the last word}}. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 06:07, 19 June 2024 (UTC) | |||
* '''Overturn'''. I didn't participate in the RFC (and aren't an admin myself) but anything that long and controversial should be closed by an admin (barring a WP:SNOW case which is clearly not relevant here). Full stop. This is especially the case for radioactively controversial topics that editors have strong views on to avoid them becoming polls of "Which side of this conflict rallies the most supporters". ] (]) 22:33, 18 June 2024 (UTC) | |||
* '''Endorse''' This is pointless. No one would've closed it differently, and it has been open for ''two months,'' for gods sake. The idea that expressing SYMPATHY for Palestinians somehow makes you unfit to close such a landslide RFC is frankly ludicrous. This is bureaucracy for the sake of bureaucracy and the only way someone should overturn this is if they commit to closing it themselves. If not, we're just admitting why no one is stepping up to make this obvious close. ] (]) 23:13, 18 June 2024 (UTC) | |||
*:{{tq|1=we're just admitting why no one is stepping up to make this obvious close}}<br>I am missing the implication here. Why is that? <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 23:23, 18 June 2024 (UTC) | |||
*::Because so many of the closes in this topic area are subject to tedious bureaucratic objections. ] (]) 23:31, 18 June 2024 (UTC) | |||
*:::Gotcha, thanks. I have a feeling that an uninvolved admin providing a detailed summary in their close wouldn't have their close brought to any noticeboard, but I don't know for sure. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 23:33, 18 June 2024 (UTC) | |||
*::::Maybe we could get a panel of admins, then? They could set up a discussion, take a week or two because of their different time zones, and then we could get the same close, but we would've wasted hours and hours of editor time in the process. ] (]) 23:54, 18 June 2024 (UTC) | |||
*:::::Or we can just get one uninvolved admin to do the herculean task of sensitively reviewing this gigantic RfC and providing a detailed summary to explain the consensus to the community and how it was reached—something that nobody, including this non-admin closer, has done yet. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 00:06, 19 June 2024 (UTC) | |||
*::::::So are you claiming they didn't read the discussion, didn't read the discussion "sensitively" (What does this mean?), or didn't provide enough detail? Because if it's just the latter, why aren't you simply asking them to just flesh out the close? You started this discussion claiming that the problem was that they were less qualified to close this discussion than an admin (Why?), but all of your replies since then have made it clear that your issue with the close is actually that you think they chose the wrong option. You need to pick a lane, here. ] (]) 00:59, 19 June 2024 (UTC) | |||
*:::::::I ask you, with love in the air, to please be a little more chill with me.{{pb}}I brought this here because it had been raised in three separate places, and directed twice to AN. My opening comment is just a summary of events and quotes from other editors with none of my own input. {{pb}}My personal view is that the RfC was not apparently well-read enough by the closer, who wrote a one-sentence, totally non-specific summary citing a rough vote ratio and made no acknowledgement of the most prominent counterarguments to the apparent consensus vote, which is that a lot of them had nothing to do with reliability in the Israel/Palestine topic area, but were instead related to the topic of antisemitism. This may be due to the closer's bias on the topic, as the original complainants have raised. I don't care so much about that; I care about votes being satisfactorily read for policy-based substance and treated with apparent care, which in this case (I think) they were not. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 01:07, 19 June 2024 (UTC) | |||
*:::::::{{reply|Parabolist}} If {{u|Zanahary}} ''is'' claiming that TB didn't read the discussion, then that's no more ] to {{u|Levivich}}, that Zanahary had also not re/read the discussion before opening it up for ''further'' discussion here *facepalm* ...in other news, I guess WP:BLUDGEON might also make them profitable reading. ] 13:19, 19 June 2024 (UTC) | |||
*::::::::For the record, I read the entire I/P discussion after ] encouraged me to do so. You can scroll up to the hatted discussion between us to see a more in-depth discussion of votes I found problematic. I am now, though, unsubscribing from this discussion, in which I've made myself heard and there's clearly no shortage of opinions to take it to its end. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 19:10, 19 June 2024 (UTC) | |||
* '''Overturn''' The responsibility of closing an RFC in such a sensitive, controversial area should be done by an admin, ideally one with a great deal of experience closing RFCs. It's not pointless bureaucracy; the more people respect a process, the more people will respect the result, which is something necessary on this topic. If only the end results of the process, not the justice of the process, mattered, then there would be no reason to care about insults, harassment, etc. beyond their impact to the content. I'm not in favor of a trout for the closer, not even a minnow; they made the closure in good faith, I just think it was unwise. ] (]) 23:28, 18 June 2024 (UTC) | |||
* '''Overturn''', per others here (especially CoffeeCrumbs). But also because there were many !votes for option 1 (or rarely 2) that expressed the fact that no evidence of unreliability has actually been presented, which I broadly agree with - the evidence that ''was'' presented was evidence of ''bias'' - but we're yet again dealing with the question "does bias = reliability" on RS/N right now for the Telegraph. And it seems that the consensus on WP still is, as evidenced by that discussion, that bias does not equate to unreliable. A closure by an uninvolved, experienced administrator which adequately takes into account the fact that at least a significant minority (if not majority) of option 3 !votes were based on the users' opinions rather than verified proof of deliberate inaccuracies in their reporting would be merited for such a controversial topic. -bɜ:ʳkənhɪmez (]/]) 23:37, 18 June 2024 (UTC) | |||
*:The close has been updated since my comment. It still is insufficient, and in fact it continues the “vote counting” that plagued the original close. It then interjects the closer’s personal opinion over whether the rebuttals are sufficient to show bias rather than unreliability. This makes the close even more of a supervote than it was before. And this is exactly why contentious closes should be done by an editor who reads the whole discussion and can concisely summarize the points in the discussion, rather than someone looking for an “easy” close based on the numbers. -bɜ:ʳkənhɪmez (]/]) 19:37, 19 June 2024 (UTC) | |||
* '''Endorse''' largely per Parabolist and Levivich. I'd first like to emphasize the point that there is nothing magical in and of itself about an admin close. No disrespect to any admins, but I have no doubt that there is some subset of experienced non-admins who are 'better' closers than some subset of admins. Still, I understand that there's a certain value to the optics. Beyond that, while Misplaced Pages is not a court of law, I find an analogy here irresistible: in common law systems, procedural problems generally do not constitute reversible error unless some prejudice can be shown to a litigant. That's what I see here. It's difficult to see how a reasonable closer (admin or not) would come to a substantially different conclusion. Was it wrong for TrangaBellam to close? No, I don't think so. Was it suboptimal? Yes, I would say it was. But Misplaced Pages does not demand perfection--the crooked timber of humanity, and so on. I do not doubt Zanahary's good faith, and I honestly don't mean this as a criticism, but this feels a bit like a relitigation rather than a challenge to the close. As ever, reasonable minds can certainly differ. Cheers to one and all. ] (]) 00:42, 19 June 2024 (UTC) | |||
*:Rerunning a legal process due to some marginal procedural error can be prohibitively costly and overall terrible and inhumane, while reclosing this RfC in specific is either a trivial expenditure of community resorces if the close was materially fine or it is simply needed regardless of cost if the error is not procedural and is in fact material. So it should just be done, since people are complaining now, and they're doing an acceptable job complaining frankly. There's a perception. Path of least resistance is quickly vacating. —] 01:15, 19 June 2024 (UTC) | |||
*::That's a fair point, but I guess I have an innate bias against the elevation of form over substance. As such, we will simply have to agree to disagree, though I certainly won't make a fuss. Cheers. ] (]) 02:49, 19 June 2024 (UTC) | |||
* '''Vacate'''. This RfC should be closed by ''an administrator who is at the same time an editor who seems less involved'', and if the close challenged here was a correct finding of a relatively obvious consensus, as claimed by some, it will be especially easy for a less-involved-seeming administrator to close it, meaning that the expediture of volunteer resources will be especially low and worth it, because avoiding this sensitive RfC remaining closed for perpetuity by a closer who is not such a great editor to close due to a perception of being involved is worth said very low cost of reclosing, and if the close was not a correct finding of consensus, then the outcome needs to be different, and an average admin is a bit more likely to find consensus correctly than an average non-admin and to deliver an appropriate closing statement, as needed. I recognize that per ], a {{tq|non-admin close of an RfC should not be overturned if the only reason is that the closer was not an admin}}, but the closer not being an admin is not the "only reason" as said reason is compounded by there existing a perception of them being involved so my recommendation is consistent with the spirit of ]: {{tq|Generally, if you want to request closure by an uninvolved administrator, it's expected that the discussion will have already been open at least a week, and that the subject is particularly contentious or the outcome is unclear.}} (The subject is inherently particularly contentious; some editors are subsequently requesting a close by an uninvolved administrator as they have concerns about the close by the not-fully-uninvolved-seeming non-administrator). Worth the extra bother. Vacating and reclosing shouldn't be seen as a big deal.—] 01:04, 19 June 2024 (UTC) | |||
*'''Vacate''' I like Alalch E.'s term here. Looking at the numbers suggests 3 is the correct answer but the analysis of the arguments was extremely superficial. It's not just about the answer, it's about the process as well. It should be followed. ] (]) 01:48, 19 June 2024 (UTC) | |||
*'''Overturn''' Having a good process is important (regardless of whether or not the decision was correct) and this wasn't such. <b style="color: #0000cc;">''North8000''</b> (]) 03:05, 19 June 2024 (UTC) | |||
*'''Endorse''' Per ] statement above. The vote and arguments in favor were strong. A profile quote in no manner outweighs the clear consensus reached through the discussion. ] (]) 04:36, 19 June 2024 (UTC) | |||
*'''Closing statement too short'''. The RfC, according to my device, is approximately 600 million scrolls long. It was closed with a statement of thirty-three words. What did people say? What were the arguments made? I don't have an opinion on the propriety or practicality of the close, but the ''quality'' of the close is very poor. ] (]) 06:09, 19 June 2024 (UTC) | |||
*:Just fwiw, this was a three-part-RfC, only the first of which was closed. As to the content of the RfC: multiple editors presented multiple evidences of ADL's unreliability on the topic; most of the participants were convinced by this evidence but a minority claimed that atleast some of the evidence — if not all — can be, at worst, re-classed under "bias" (which I didn't find convincing, even ignoring the numerical strength) and hence cannot be perceived as grounds for unreliability. Nothing more, nothing less. Now, appended to the RfC close. Thanks, ] (]) 06:13, 19 June 2024 (UTC) | |||
*'''Overturn''' This is basically equivalent to the Fox News RfC, due to its political contentiousness. It cannot merely be judged based on numbers alone. It needs to be closed by (preferably a panel) of non-partisan administrators. As the person who originally opened the first ADL RfC, I don't have a strong enough opinion about whether the result was correct, but the justification is way too short. ] (]) 09:17, 19 June 2024 (UTC) | |||
*'''Endorse''', but only because I can't see that anyone else would have closed it any differently. Such a contentious RfC ''should'' have been closed by an admin, and it ''should'' have been closed by someone who couldn't be accused of bias in the CTOP area. It was a poor idea for TB to close it; but the actual result is correct. ] 11:01, 19 June 2024 (UTC) | |||
*'''Endorse''' per NOTBURO, there's no point in wasting time reopening the discussion in orde for it to be reclosed the same way (which is all that would happen); policy does not allow for closers to be dictated by parties external to the project; and while the topic may be controversial, the discussion was not. ] 11:26, 19 June 2024 (UTC) | |||
*'''Endorse''' The claim that quoting someone previously that has since participated in an RFC makes someone involved is like claiming someone is best friends with Kevin Bacon. It's such a long reach as to be patently nonsensical. Also, admins have no special powers with regards to closing RFCs. It's expected that we have a good understanding of policy and are trusted by the community, but a decent RFC closure is a decent RFC closure whether and admin makes it or not.--v/r - ]] 13:38, 19 June 2024 (UTC) | |||
*'''Overturn''' such an important, high-visibility action, which has already received widespread media attention, should be carried out by an uninvolved administrator, not an involved non-administrator. ] (]) 14:24, 19 June 2024 (UTC) | |||
*:What makes TrangaBellam involved? ] (]) 14:31, 19 June 2024 (UTC) | |||
*::The talk page quote is more than sufficient to disqualify this particular non-admin. If it was okay for him to close the discussion, then it would have been ok for me to close it. I didn't participate in the RSN discussion, and until today I never edited the ADL article and I don't have statements on my user page evincing a point of view on the subject area. Something quite this contentious requires a nonpartisan administrator if we're going to kick sand in the face of a reputable civil rights organization. ] (]) 14:49, 19 June 2024 (UTC) | |||
*:::{{tq|if we're going to kick sand in the face of a reputable civil rights organization}} and of course this quote doesn't make you involved at all, right? ] (]) 15:08, 19 June 2024 (UTC) | |||
*::::Exactly. That quote would be sufficient. Thank you for proving my point. ] (]) 15:14, 19 June 2024 (UTC) | |||
*:::::What part of ] are you referencing here? I'd happily change my endorse if any evidence was provided of the closure being involved in the dispute, past or current conflicts with involved editors, or disputes on related topics. Per policy, simply having a ''perceived bias'' is not enough to accuse someone of being involved. ] (]) 16:48, 19 June 2024 (UTC) | |||
*::::::{{tq|disputes ... about which they have strong feelings.}} | |||
*::::::Personally, I believe that you have strong feelings about a dispute if you feel the need to say you support one side of the dispute at the top of your user talk page. ] (]) 17:12, 19 June 2024 (UTC) | |||
*:::::::And not just because one has !voted option 1, lol. ] (]) 17:16, 19 June 2024 (UTC) | |||
*:::::::I suspected this would come up, as it's easily misinterpretable, the ] is: {{tq|"In general, editors should not act as administrators in disputes in which they have been involved. '''This is because''' involved administrators may be, or appear to be, incapable of making objective decisions in disputes to which they have been a party or about which they have strong feelings."}} (emphasis added). Quite clearly the "strong feelings" is in reference to editors involved in disputes, not in reference to closures generally. You still need to provide evidence that the closure is involved in a related dispute, and I'm still patiently waiting for that. Your personal opinion that having strong feelings is involvement is not WP policy. ] (]) 17:22, 19 June 2024 (UTC) | |||
*:::::::: I disagree; I interpret it as saying that having strong feelings on a topic makes an editor involved. | |||
*:::::::: Personally, it doesn't make sense to me otherwise. Consider an editor who has a user box saying "This user believes marriage is only between a man and a woman", but has never edited articles related to ]. Should they be closing RfC's related to homosexuality? | |||
*:::::::: Of course not, because the community would have no faith that they would make {{tq|objective decisions}} - even though they haven't been involved in the specific disputes. ] (]) 17:28, 19 June 2024 (UTC) | |||
*:::::::::That's not what the text says. It says that ''if'' you ''are'' involved, objectively, it can create perceptions of XYZ. It's not a generic filter for bias, because all editors have ubiquitous personal biases, whether conscious or subconscious. ] (]) 18:40, 19 June 2024 (UTC) | |||
*:::::::::Saying one has sympathy for the Tibetans and the Palestinians does not demonstrate strong feelings related to the ADL or the Israeli Palestinian conflict. That’s just silly. ''']''' - 02:10, 20 June 2024 (UTC) | |||
*:::Yes, it technically would have been ok for you to close it. Based on your statement, you ''might'' have wanted to recuse yourself from it if you felt too close to it, but based on feels more than policy – just as some have suggested that TB ''might'' have wanted to stay away from it (but not that they ''should'' have done, per policy). As it stands, TB did nothing wrong and by most estimations closed in the only way possible. So there's nothing obviously wrong with the close, and even if there were, there's a strong clamour that the close is correct (so ] comes heavily into play). ] (]) 16:06, 19 June 2024 (UTC) | |||
*::::It's never BURO to vacate+reclose by an uninvolved admin when a perception that the non-admin is insufficiently uninvolved exists, because reclosing (not rerunning the process) is cheap: if the consensus is obvious the effort is a trivial one, and if the consensus is not obvious it's highly justified and worth it that someone less involved-seeming and more trusted as a closer closes instead. When there are real gains, it isn't BURO territory. —] 16:23, 19 June 2024 (UTC) | |||
*:::::Except the closer here simply wasn't involved (by the standard definition) – the "perception" is one of perceived bias, or in other words the presumption that the closer was sufficiently compromised by bias that they couldn't close correctly – an assertion that is solely bad faith and otherwise unsupported. ] (]) 16:36, 19 June 2024 (UTC) | |||
*'''Vacate + have someone else close it''' Zanahary's concerns and Coretheapple's remarks sum things up nicely and no need to repeat. Someone else needs to close it, not a partisan. I recognize it may not change the outcome and while I acknowledge the ratio of those who want to mark them as generally unreliable, I highly question their logic and evidence. Someone uninvolved needs to take the time to read this stuff and assess how valid the claims are. Such a downgrade will have major political and social implications and will likely be featured prominently in national news. I urge people to slow down and make an unquestionable decision. Personally I think the ADL oversteps its bounds, but I think the criticism that they changed their methodology and came up with new numbers isn't nefarious as some people are claiming ("They changed their numbers from 310% to 176%!!!"). That's what reliable sources do when they change methodology. They update their numbers. Much of the other evidence is practically leftist propaganda and/or "Trump is bad!" logic. ] (]) 15:54, 19 June 2024 (UTC) | |||
*:Describing someone having a quote saying you have sympathy for the oppressed people of the world as a "partisan" is baffling to me. ] (]) 19:20, 19 June 2024 (UTC) | |||
*::Describing "I sympathise with the silenced underdog in so many conflicts, be they Aboriginals or Palestinians..." as just "sympathy for the oppressed people" is not an accurate characterization. It presupposes | |||
*::#The Palestinians are actually oppressed. The Palestinians in Gaza have been given billions in international aid and still struggle to form an effective government/local control that doesn't squander the money on creating a state bent on the destruction of their neighbor rather than helping their people. | |||
*::#They are silenced at all. They seem to be rather well-voiced at every level. | |||
*::#That such sympathy is warranted. | |||
*::That this is the crux of the discussion and/or is germane to the discussion (ARBPIA applies), the person closing this shouldn't be someone so prominently advocating against Israeli/Jewish interests. There is an inherent conflict of interest there. ] (]) 21:05, 19 June 2024 (UTC) | |||
*:::While I don't consider the statement quoted by the closer to indicate INVOLVED status (see my !vote below), I think the following definitely does: | |||
*:::{{Talk quote|The Palestinians in Gaza have been given billions in international aid and still struggle to form an effective government/local control that doesn't squander the money on creating a state bent on the destruction of their neighbor rather than helping their people.}} | |||
*:::Whatever the line is between "not really INVOLVED" and "too INVOLVED", I think it runs somewhere between an expression of sympathy for a national, ethnic or religious category, and blaming that whole category of people for the actions (presented without context) of their quasi-governments. Buff's statement (the latter kind) is the equivalent of holding "Jews" or "Zonists" responsible for the foreign policy of rhe state of Israel, but enwiki has pretty reliably demonstrated that the latter is ''well'' over the line. ] (]) 21:16, 19 June 2024 (UTC) | |||
*The '''discussion just really sucked'''. Both sides were talking past each other, !votes were functioning more as flag-planting than actual attempts to substantively engage with the question, lots of "gotcha" links were thrown around with little sign of anyone attempting to perform a neutral survey of the evidence. Under these circumstances I don't think it makes much sense to be talking about whether to endorse or overturn any sort of close: the most honest conclusion a closer could draw is "the community has collectively proven it lacks the capacity to properly answer the question at this time". – ]''']''' ] 16:14, 19 June 2024 (UTC) | |||
*:Then call for a reclose and if it happens, see if the new closer agrees with you. Fwiw, I wouldn't agree. ] (]) 16:26, 19 June 2024 (UTC) | |||
*::No point calling for a reclose if the discussion itself is awful. Garbage in, garbage out. – ]''']''' ] 00:41, 20 June 2024 (UTC) | |||
*'''Vacate''' and have a panel of 3 admins re-assess and re-close it. This is more about the procedure than the outcome in my view. ] ] 17:21, 19 June 2024 (UTC) | |||
*:I think that's the ideal solution. This needs to be a bulletproof decision, unless of course we don't want it to be. That's the choice here. We can do the right thing or we can tell critics of this decision that all our fantastic procedures were followed and that's all we really care about. ] (]) 17:37, 19 June 2024 (UTC) | |||
*:Another thing to take into consideration is the impact of having three respected, truly uninvolved admins making the same decision. People who are hopping with joy over this outcome should think about that. ] (]) 18:38, 19 June 2024 (UTC) | |||
*:Thank you for volunteering. ] (]) 19:40, 19 June 2024 (UTC) | |||
*::I assume that wasn't directed at me! I am not an admin. But your general point is not incorrect. Admins have tended to avoid this subject area. ] (]) 19:59, 19 June 2024 (UTC) | |||
*'''Vacate''' Agree this is more about procedure than outcome. Just because a RFC is sitting at ] for a long time doesn't mean we throw procedure out the window. It probably just means it's going to need an experienced closer to review it. ] (]) 17:54, 19 June 2024 (UTC) | |||
*'''Overturn'''. The closer ]. ] (]) 19:44, 19 June 2024 (UTC) | |||
*:And, what's the insinuation, here? To the best of my knowledge, I have put in a couple of RfC votes (maybe a comment or two, even?) but that's my involvement with IPA at best. ] (]) 19:48, 19 June 2024 (UTC) | |||
*::I realize that was a "per" !vote from half a year ago, but it seems like too much involvement in a content dispute to close an RFC in the same area about the reliability of a source. ] (]) 20:32, 19 June 2024 (UTC) | |||
*'''Endorse''', primarily per ] - the correct option was found to have consensus, and the arguments for a "procedural" overturn are against the spirit of the project; the most likely impact of an overturn would be a "chilling effect" on NACs, and an emboldening of editors to seek "procedural" overturning of closes because they ]. Misplaced Pages needs more NACs of obvious consensus results, not fewer. | |||
:I would also point out that editors who think {{tq|..I sympathise with the silenced underdog in so many conflicts, be they Aboriginals or Palestinians or Tibetans}} is evidence of bias do not seem to be to be reflecting what the INVOLVED principle actually means. I can't imagine that we would be having this discussion if the passage quoted were along the lines of "..I sympathise with the silenced underdog in so many conflicts, such as victims of antisemitism" - but yet, here we are. As I have seen in other discussions within ARBPIA, this seems to be a deployment of ] about bias to contest an outcome that some editors find distasteful. | |||
:Also, in passing, I find the argument that a discussion with a clear outcome requires a nuanced closure because of <s>BLUDGEONING</s> complex argumentation from the discussion's participants to be, once again, against the spirit of a project. To vacate the close citing this ground would only encourage additional <s>BLUDGEONING</s> unproductive pseudo-dialogue in future RfCs. ] (]) 20:03, 19 June 2024 (UTC) | |||
:: The "chilling effect" on NACs is a feature, not a bug, for discussions like this. They absolutely shouldn't be closed by non-admins and we shouldn't be encouraging that, lest we just invite more giant discussions overflowing to AN/ANI from the "losing" side. The whole point of these RFCs is to generate a strong consensus that is respected and has legitimacy, even in the eyes of those who disagree, so that they respect the decision and don't challenge it (like happened here!). If you think the outcome was that clear, prove it by letting an uninvolved admin close it. I also find it boggling to claim the result was "obvious" here in such a trainwreck. One side is claiming that some of the votes should be discounted as essentially cheerleading their "side" in a dispute without engaging with the topic at hand. Maybe that's true, maybe that isn't, but assessing that claim in a manner that is respected requires an admin, maybe even a panel of admins. This is a YESBURO situation even if you agree with the result of the current close, because a future close will be stronger and more respected if it comes from an unimpeachable source. ] (]) 21:45, 19 June 2024 (UTC) | |||
*'''Overturn''' - a sensitive RfC like this should only be closed by an uninvolved admin. ] (]) 20:22, 19 June 2024 (UTC) | |||
*'''Vacate''' while I sympathize with concerns about excessive bureaucracy, I think the community needs to take a hardline against controversial non-admin closes. While I'm not fully convinced that we can concretely say that TrangaBellam was INVOLVED, it would have been better for the discussion to be closed by someone else. So let's have someone else do it. ] (]) 21:37, 19 June 2024 (UTC) | |||
*'''Endorse'''. So it appears that the closer did highlight some comments from known ARBPIA participants that could reasonably be seen as biased. Closure like that will absolutely benefit from longer rationale, because anyone looking at it should more or less understand the "why" of the decision and main arguments. I tend to be verbose in RfC closures so that if I'm an ass, at least everyone sees it, but it's me. I guess at least two hallmarks of ] are here: probable involvement and controversy. However, BADNAC is part of an essay. We are not a court of law. It isn't like recusal must be automatic, though it is desired. | |||
:Now the thing is that this closure would have been appealed no matter what, even if a panel were to summarise it. In discussions of this size and degree of controversy, it's inevitable. Because closing RFCs is largely an admin thing, one would expect ], so here we are, grilling TB at RfC closure review. I guess that's more than enough scrutiny, so that's one reason against using technicalities to overturn. | |||
:Now ] asks people to point out what's wrong with the closure. It seems , and a lot of voices to overturn do not say they would have closed it otherwise, or say how the summation did not reflect consensus, or which argument should have carried more weight. Sure, if the problem with likely INVOLVED closes in edgy cases persists then TrangaBellam should have some talking to, including RfC closure bans or ArbCom intervention, as INVOLVED is policy. However, the overall result is correct as far as the discussion is concerned, so it's a pass for me. INVOLVED is meant to prevent biased closures, and maybe the closer was biased but the closure wasn't, which I think is all that matters for CLOSECHALLENGE purposes. | |||
:They attempted an enormously difficult task, their explanation should have been more detailed. But they did OK. ] (]) 22:12, 19 June 2024 (UTC) | |||
*'''Endorse''' Seriously? This isn't a ] (despite us having "bureaucrats"). Just because a close was performed by a non-admin does not mean it is any less respectable or any less legitimate. Anyone arguing that a non-admin close is less of a close because the closer doesn't have the all-fanciful admin bit, needs to re-read ]. It's almost shameful that having the admin toys is considered an endorsement of ones opinion. There's plenty of admins who were given the tools in the olden days and just kept them up to now, but they were only ever put through RFA with a few people, when adminship was actually seen as the lack of a big deal that it should be seen as today. Maybe we need to step back on how we see admins as some god-like figures, and see them more as humans, just like every editor on this platform. ] <sup>(]) </sup> 22:36, 19 June 2024 (UTC) | |||
*:That is a great speech about the all-fanciful admin bit, can you do one about the all-fanciful admin-and-also-not-having-quotes-on-your-talk-page-about-how-you-think-one-of-the-sides-is-right bit? <b style="font-family: monospace; color:#E35BD8">]×]]</b> 23:16, 19 June 2024 (UTC) | |||
*::It does no such thing, and I feel like I'm going insane with people saying this. The actual quote is the most mild sentiment imaginable. Is Tranga now disqualified from closing RFCs about Tibet, or Aboriginal issues? ] (]) 02:48, 20 June 2024 (UTC) | |||
:'''Vacate''' This is far to controversial an RFC for a non-admin close. If it the decision is not seen as having come from somebody uninvolved (even if they actually aren't INVOLVED in a literal sense) then it leaves room for endless Wikilawyering about how strong a consensus was every time the topic comes up. ] ☞️ ] 22:39, 19 June 2024 (UTC) | |||
*'''Endorse''' good close, INVOLVED argument not convincing, no admin is magically going to produce a better one just because they've gone through an RfA. ] (]) 22:50, 19 June 2024 (UTC) | |||
*'''Endorse''' per NOTBURO. I share Newimpartial’s impression of FUD; I can’t speak to anyone’s motives but I object to undermining a close other than on the basis that it was wrongly concluded. ] (]) 01:12, 20 June 2024 (UTC) | |||
{{archive bottom}} | |||
=== Warning of meatpuppetry === | |||
Potential meatpuppets incoming: --] (]) 07:34, 19 June 2024 (UTC) | |||
* This discussion falls under ARBPIA, so any comments from non-ECR accounts or IPs can be removed. ] 11:02, 19 June 2024 (UTC) | |||
*:It would be useful (and minimally bitey) to put a template or other note at the top of this discussion noting that fact. ] (]) 11:17, 19 June 2024 (UTC) | |||
::* Good idea. Done. ] 11:34, 19 June 2024 (UTC) | |||
At ], I was instructed by closer ] that I could appeal these in a year and it has been 9.5 months. I am appealing because the CUP entry deadline is traditionally January 31. See ] through ]. This year the ] verbiage says "The competition will begin on 1 January 2025 and signups will continue throughout the year". I am just noticing the new language as I am putting this appeal in. Nonetheless, I am requesting time off for good behavior on the ban.-] <small>(] / ] / ] / ] / ])</small> 18:52, 17 January 2025 (UTC) | |||
== A quick job for someone? == | |||
:'''Oppose''' The utter cluelessness of this appeal is more than enough reason not to do this. I was going to write more but decided that coaching you on how to be less clueless is not in the project's best interest. You've been here long enough that you should be able to see for yourself how terrible this appeal is. ] ] 19:02, 17 January 2025 (UTC) | |||
:'''Oppose''' and recommend we disallow any further appeals for another year. I'm concerned otherwise we'll just be back here in April. --] (]) 19:14, 17 January 2025 (UTC) | |||
:'''Oppose for now''' It's pretty clear that most people in that discussion were supporting an indef ban from the Cup, not an 8-month ban. This appeal doesn't address people's concerns with Tony's editing relating to the Cup, so should be denied. --] 19:16, 17 January 2025 (UTC) | |||
: '''Oppose''' The original discussion wasn't linked, it can be found ]. At that place it is very clear that {{tq|here is almost unanimous support for an indefinite ban on participation in the WikiCup}}, so, no, this appeal should not be passed. It is, honestly, astonishing that TonyTheTiger has been here very nearly two decades but hasn't taken on board the way the community works ~ ''']'''<sup>''']''']</sup> 19:20, 17 January 2025 (UTC) | |||
:'''Oppose''' for no rational that they understand why they were banned or what even led to their ban, and rather simply a sentiment of "I really want to participate". Please understand that '''your ban was indefinite''', so the one year appeal opportunity is your potential opportunity "time off for good behavior". ] ] 19:24, 17 January 2025 (UTC) | |||
:'''Oppose'''. Appealing early on the basis that you won't be able to sign up to do the thing you were banned from doing is certainly a unique take. ♠]♠ ] 21:03, 17 January 2025 (UTC) | |||
{{abot}} | |||
==Requesting info== | |||
{{atop | |||
| result = {{u|Steve Quinn}} is {{itrout|trouted}} for bringing this to AN. ] (]/]) 21:58, 17 January 2025 (UTC) | |||
}} | |||
Hello. I have come across several image files and the U.S. Gov. PD licensing seems to be incorrect. Four of these images and possibly another one could be copyright violations - if I can figure out how to find this type of information on their websites. However, since I am unable to find that information at this moment, I am wondering which group of Misplaced Pages editors work on this sort of thing so that maybe I can get some help with this. I will post the files here for information purposes. Also, there may be more copyright violations by this particular editor who seems to have a propensity for downloading image files. Below are the files: | |||
# ] | |||
# ] | |||
# ] | |||
# ] | |||
# ] | |||
Further comment: The above TN file - File:AppalachianTN.jpg - is covered by the TN.GOV "linking policy" and can be found . So this Misplaced Pages image file is still not licensed appropriately, although I have no idea what the correct Misplaced Pages licensing would be. | |||
I will notify the editor who downloaded these files that I have opened a discussion here. Well, now that I have taken it this far, the editor in question is: {{userlinks|Brian.S.W}}. However, the above image files might be too stale to be considered for any action. I leave that up to the Admins. If you look on their talk page, they have previously been blocked for copyright violations. ---] (]) 20:59, 17 January 2025 (UTC) | |||
At ], the entry under June 15 for ] has been marked ready for over two and a half ''days'' now, even while other stories have been posted. I can't post it myself as I nominated it. Could someone do the honours? Thanks, ] 10:36, 19 June 2024 (UTC) | |||
:As you can see they've already been tagged for a deletion discussion yesterday, so there is no need to have a difference notice board also working on it. ] ] 21:21, 17 January 2025 (UTC) | |||
:{{done}} ]] 10:47, 19 June 2024 (UTC) | |||
{{abot}} | |||
:: Thanks. ] 11:16, 19 June 2024 (UTC) |
Latest revision as of 23:12, 17 January 2025
Notices of interest to administrators
Noticeboards | |
---|---|
Misplaced Pages's centralized discussion, request, and help venues. For a listing of ongoing discussions and current requests, see the dashboard. For a related set of forums which do not function as noticeboards see formal review processes. | |
General | |
Articles, content | |
Page handling | |
User conduct | |
Other | |
Category:Misplaced Pages noticeboards |
- For urgent incidents and chronic, intractable behavioral problems, use Misplaced Pages:Administrators' noticeboard/Incidents.
- To request review of an administrator's action or other use of advanced permissions, use Misplaced Pages:Administrative action review
- If you are new, try the Teahouse instead.
- Do not report breaches of personal information on this highly visible page – instead, follow the instructions on Misplaced Pages:Requests for oversight.
- For administrative backlogs add
{{Admin backlog}}
to the backlogged page; post here only if urgent. - Do not post requests for page protection, deletion requests, or block requests here.
- Just want an admin? Contact a recently active admin directly.
- If you want to challenge the closure of a request for comment, use
{{RfC closure review}}
When you start a discussion about an editor, you must leave a notice on their talk page. Pinging is not enough.
You may use {{subst:AN-notice}} ~~~~
to do so.
Sections inactive for over seven days are archived by Lowercase sigmabot III.(archives, search)
Start a new discussionOpen tasks
Centralized discussionAdministrators' (archives, search) | |||||||||
---|---|---|---|---|---|---|---|---|---|
349 | 350 | 351 | 352 | 353 | 354 | 355 | 356 | 357 | 358 |
359 | 360 | 361 | 362 | 363 | 364 | 365 | 366 | 367 | 368 |
Incidents (archives, search) | |||||||||
1157 | 1158 | 1159 | 1160 | 1161 | 1162 | 1163 | 1164 | 1165 | 1166 |
1167 | 1168 | 1169 | 1170 | 1171 | 1172 | 1173 | 1174 | 1175 | 1176 |
Edit-warring/3RR (archives, search) | |||||||||
472 | 473 | 474 | 475 | 476 | 477 | 478 | 479 | 480 | 481 |
482 | 483 | 484 | 485 | 486 | 487 | 488 | 489 | 490 | 491 |
Arbitration enforcement (archives) | |||||||||
328 | 329 | 330 | 331 | 332 | 333 | 334 | 335 | 336 | 337 |
338 | 339 | 340 | 341 | 342 | 343 | 344 | 345 | 346 | 347 |
Other links | |||||||||
V | Oct | Nov | Dec | Jan | Total |
---|---|---|---|---|---|
CfD | 0 | 0 | 3 | 29 | 32 |
TfD | 0 | 0 | 0 | 2 | 2 |
MfD | 0 | 0 | 0 | 11 | 11 |
FfD | 0 | 0 | 5 | 18 | 23 |
RfD | 0 | 0 | 3 | 48 | 51 |
AfD | 0 | 0 | 0 | 0 | 0 |
- 0 bot-reported usernames for administrator attention
- 2 user-reported usernames for administrator attention
- 3 bot-generated requests for intervention against vandalism
- 1 user-generated requests for intervention against vandalism
- 40 sockpuppet investigations
- 54 Candidates for speedy deletion
- 2 Fully protected edit requests
- 0 Candidates for history merging
- 1 requests for RD1 redaction
- 96 elapsed requested moves
- 1 Pages at move review
- 20 requested closures
- 16 requests for unblock
- 0 Wikipedians looking for help from administrators
- 13 Copyright problems
Sander.v.Ginkel unblock request
The following is copied from User talk:Sander.v.Ginkel#Unblock_request on behalf of Sander.v.Ginkel:
I have made serious mistakes. I regret it and say sorry for it. I fully understand why I have been blocked. My biggest mistake that I copied-pasted content from articles to other articles, that led to a BLP violation. I have also misused other accounts as suckpuppets: User:SportsOlympic and User:MFriedman (note that the two other accounts –- User:Dilliedillie and User:Vaintrain -- at Category:Misplaced Pages sockpuppets of Sander.v.Ginkel was not me. ) In addition, my work was too focused on quantity, rather than quality. I apologize to those who had to do some cleaning up for me.
Whay do I want to come back? And do I deserve it? I can show that I can make constructive content. I made some edits and created pages under the IP address 82.174.61.58, that was not allowed; and was blocked. It is not good that I made edits under an IP address, but I appreciated that some users (User:Tamzin, User:Xoak, User:Ingenuity) stated they liked the content I created and/or that they offer the opportunity to have me back (see at Misplaced Pages:Sockpuppet investigations/Sander.v.Ginkel/Archive). I made the same mistakes on the Dutch Misplaced Pages (where I misused the same accounts). At this Misplaced Pages I bot back my account and I am editing the Wikipeida I’m also editing at simple.wikipedia.org (see User:SportsOlympic). I have created over 900 pages (see here), (1 page being deleted). I like to create articles from historic work on old sources, for instance simple:Annie van de Blankevoort, simple:1928 Belgium–Netherlands women's athletics competition, simple:Julia Beelaerts van Blokland, simple:Esther Bekkers-Lopes Cardozo or the event simple:Water polo at the 1922 Women's Olympiad that is barely mentioned at the English 1922 Women's Olympiad. Around 100 pages have been (literally) copied to the English Misplaced Pages by several users. I'm also editing Wikidata, see here and here when I forgot to log in.
However, as I have learned from it, I will never use multiple accounts anymore and adding controversial content without doing a proper fact-check. I will always listen to users, be constructive and be friendly. I will make sure you will not regret giving me my account back. I would like to work under the account user:SportsOlympic.
Significa liberdade (she/her) (talk) 18:12, 15 December 2024 (UTC)
- Support unbanning and unblocking per WP:SO. voorts (talk/contributions) 18:31, 15 December 2024 (UTC)
- Quoting my SPI comment in 2022:
That sentiment is what I eventually wrote down at User:Tamzin/Adverse possession unblock, which mentions the same principles being relevant in unban discussions. And now that this is before the community, with even more time having passed, I have no problem unbanning: The post-ban edits, while problematic in that they were sockpuppetry, do show evidence that Sander has learned from his mistakes, and thus a ban no longer serves a preventative purpose. Looking back at the one hesitation I mentioned above, I think my concern was that it was an ECR violation that seemed credulous of a pro-Russian narrative; but if there's no evidence of that being part of any POV-pushing, then I don't see it as an obstacle to unbanning. -- Tamzin (they|xe|🤷) 18:33, 15 December 2024 (UTC)I was torn on this. The IP does not seem to be creating the sort of low-quality BLP stubs that SportsOlympic was. If this were "just" a case of block evasion, I'm not sure I could justify a block of the IP as preventative of any disruption, and would be inclined to either ignore it or block but offer a non-OFFER unblock to the main account. However, Sander.v.Ginkel is banned, and under the SportsOlympic account has caused significant disruption just six months ago. Evading a ban is an inherent harm, as it undercuts the community's ability to self-govern. Furthermore, it would be unfair to the community to allow someone to contribute content, particularly in a DS area as much of the IP's recent edits have been, without the community being on-notice of their history of significant content issues. (And there is still troubling content like Draft:Krupets.) I thus feel I would be defying the mandate the community has given me as an admin if I did anything but block here. ... FWIW, Sander, I could see myself supporting an OFFER unban down the line, although I'd recommend a year away rather than six months.
- Support per above.-- Deepfriedokra (talk) 18:37, 15 December 2024 (UTC)
- Endorse one account proviso. -- Deepfriedokra (talk) 20:28, 15 December 2024 (UTC)
- I'm a little bit concerned by the sockpuppetry returning earlier this year: Misplaced Pages:Sockpuppet investigations/Sander.v.Ginkel/Archive#18 April 2024. However, that is over 6 months ago. I would Support with the obvious proviso that the user be limited to 1 account and that IP editing may be scrutinized for evidence of WP:LOUTSOCK. — rsjaffe 🗣️ 20:16, 15 December 2024 (UTC)
- Support with provisions per above. Worth keeping a close eye on, but they seem to have understood the problems with their behavior and improved upon it. The Kip 07:07, 16 December 2024 (UTC)
- Support I've previously spoken in favor of the subject as well. X (talk) 09:15, 16 December 2024 (UTC)
- Oppose. "My biggest mistake that I copied-pasted content from articles to other articles, that led to a BLP violation. " That wasn't the biggest mistake by far. You made extremely negative claims about sportspeople based on internet rumors. Apart from this, the first article I checked on simple, , is way too close paraphrasing of the source. This has very sloppy writing, "He started his business alone 1980 built so his horse stable "Hexagon" in Schore. " is just nonsense. Copyvio/close paraphrasing seems to be a recurring problem, this has e.g. "Zwaanswijk is regarded as one of the most respected post-World War II visual artists of Haarlem and his work had a profound influence on the local art scene." where the source has "Piet Zwaanswijk was een van de meest gerespecteerde na-oorlogse beeldend kunstenaars van Haarlem. Zijn werk had een diepe invloed op de lokale kunstscene". I don't get the impression that the earlier issues have disappeared. Fram (talk) 11:45, 16 December 2024 (UTC)
- Support User seems to have recognized what he did wrong, has edited constructively off enwiki. JayCubby 18:52, 17 December 2024 (UTC)
Weak Support, the crux of the issue was three-fold: creation of low-quality sports stubs (including what Fram said), persistent IDHT when asked to fix them, and sockpuppetry. I recall I identified the SportsOlympic sock in a tangential ANI thread a couple of years ago. It appears he has edited constructively elsewhere. I would like to see a commitment to one-account-only and a commitment respond civilly and collaboratively when criticized. Jip Orlando (talk) 15:45, 18 December 2024 (UTC)
- Oppose, I am convinced by the further discussion below that S.v.G is not a net positive at this time. Jip Orlando (talk) 14:11, 24 December 2024 (UTC)
- Support. Completely support an unblock; see my comment here when his IP was blocked in April. BeanieFan11 (talk) 17:25, 18 December 2024 (UTC)
- Oppose. Sander and his socks created literally thousands of poorly-written and/or potentially-copyvio pages on (very frequently) non-notable sports topics. I don't see evidence in his Simple Wiki contribs that his writing has improved, and for someone with his history of non-notable subject choices I would want to see clear evidence that these creations are supported by WP:SUSTAINED, non-routine, IRS SIGCOV. Articles like this may well be on notable competitions, but with content like
On 20 March the Women's Fencing Club gave an assaut, in honor of the visit of the Dutch team. As seen as an exceptional, mr. de Vos was a the only man allowed to visit the women's club.
, and all sources being from 20 or 21 March 1911, we can be confident that verifying and rewriting the mangled translations and searching for continued coverage will be a huge pain for other editors. And going from the most recent en.wp AfD participation I'd also anticipate the same combativeness and time wasted explaining P&Gs to him in that area as well. Given the volume of his creations, I don't think it is fair to foist all the extra work that would come with overturning the ban onto other editors without a much more thorough evaluation of his Simple Wiki contribution quality. JoelleJay (talk) 02:34, 19 December 2024 (UTC) - Currently oppose; open to a change of view if some explanation and assurances are given with regard to the points Fram raises. There is no point in unblocking a problematic editor if it appears that they may well continue to cause issues for the community ~ Lindsay 12:59, 19 December 2024 (UTC)
- Support but keep an eye on contributions off ENWP. Ahri Boy (talk) 17:11, 23 December 2024 (UTC)
- @Ahri Boy: Not sure we are concerned with contribs off ENWP. -- Deepfriedokra (talk) 18:27, 23 December 2024 (UTC)
- He might appeal on Commons later if the appeal here is successful, so there would be a cooldown before doing there. Ahri Boy (talk) 01:15, 24 December 2024 (UTC)
- @Ahri Boy: Not sure we are concerned with contribs off ENWP. -- Deepfriedokra (talk) 18:27, 23 December 2024 (UTC)
- Oppose per Fram on close paraphrasing, JoelleJay on sourcing/writing quality, and my own observations on English-language proficiency (I see very recent sentences like "Next as working for magazines he also contributed to book"). At an absolute minimum I would need a restriction on article creation (to prevent the low-quality mass creation issues from recurring), but these issues would be a problem in other areas too. I think continuing to contribute to simple-wiki and nl-wiki would be the best way forward. Extraordinary Writ (talk) 01:34, 24 December 2024 (UTC)
- He was once blocked on NLWP for the same sockpuppetry as here before. I don't even know that he may be offered SO there. Ahri Boy (talk) 10:16, 24 December 2024 (UTC)
- Oppose. Like Fram, JoelleJay, and Extraordinary Writ, I have concerns about their competence with regards to copyright, notability, and simple prose writing. I think an unblock is likely to create a timesink for the community, who will be forced to tie one eye up watching both of his hands. ♠PMC♠ (talk) 08:41, 24 December 2024 (UTC)
- Come on – it's been nearly seven years since the ban – why can't we give another chance? His articles from when he was an IP seemed quite good (and much different from stubs which seem to have been the problem), from what I remember (although they've since been G5'd). BeanieFan11 (talk) 16:35, 24 December 2024 (UTC)
- S.v.G. needs to be reevaluated. He needs to clarify that the purpose of return is genuine, constructive, and one account only. He hasn't made any contributions to Commons because he was blocked. Ahri Boy (talk) 19:55, 24 December 2024 (UTC)
- I think saying that
I will never use multiple accounts anymore
and that he wants tomake constructive content
would indicate thatthe purpose of return is genuine, constructive, and one account only.
BeanieFan11 (talk) 19:59, 24 December 2024 (UTC)- For the meantime, he should stay at Simple and NLWP for another six months to make sure no suspicions will be made before appealing under SO. Ahri Boy (talk) 20:07, 24 December 2024 (UTC)
- I think saying that
- But it's only been three years since he was mass-creating non-notable stubs with BLP violations and bludgeoning AfDs with his SportsOlympic sock. He then edited extensively as an IP, got banned for 18 months, restarted within two weeks of that ban ending, and made another 1000+ edits until his latest IP ban in spring 2024. After which he immediately invoked the (laxer) equivalent of the SO on nl.wp... JoelleJay (talk) 21:07, 24 December 2024 (UTC)
- And he admits that he was
too focused on quantity, rather than quality
, apologized repeatedly, and his creations as an IP showed that he was no longer focused onmass-creating non-notable stubs
. BeanieFan11 (talk) 21:18, 24 December 2024 (UTC)
- And he admits that he was
- S.v.G. needs to be reevaluated. He needs to clarify that the purpose of return is genuine, constructive, and one account only. He hasn't made any contributions to Commons because he was blocked. Ahri Boy (talk) 19:55, 24 December 2024 (UTC)
- Support With the above mentioned provisions. Seems like a genuine, good faith, attempt to start over. Frank Anchor 04:44, 25 December 2024 (UTC)
- Support - Like a lot of behavioral issues on this site, I think it all stems back to the general public seeing this site as an all-inclusive encyclopedia and some users here seeing the site as a celebrity encyclopedia. If the user becomes a problem, action can be taken again. Let's see how it goes. KatoKungLee (talk) 20:03, 25 December 2024 (UTC)
- Oppose per Fram and PMC. —Compassionate727 18:52, 29 December 2024 (UTC)
- Question: Is SvG the same person as Slowking4? There has been an odd connection between the two in the past; I think it was first noted by Dirk Beetstra. ☆ Bri (talk) 22:58, 29 December 2024 (UTC)
- Support. This appears to be a good-faith attempt at a return, and looking through the commentary here I don't see evidence to suggest continuing the ban and block are preventative. - The Bushranger One ping only 23:44, 4 January 2025 (UTC)
- Oppose basically per JoelleJay, particularly the evidence that their MASSCREATE/socking/evading behaviour was carrying on as recently as spring 2024. If/When they return, it should be with the requirement that all their articles have to go through AFC and that they won't get WP:AUTOPATROLLED without a substantive discussion (i.e., no automatic conferring of autopatrolled - they have to request it and disclose why this restriction is in place when doing so). FOARP (talk) 16:46, 8 January 2025 (UTC)
- It does look like a good-faith desire to return and work on Misplaced Pages. And I would just want to add that Misplaced Pages needs such a fruitful article creator. Especially since WP:NSPORT was severely trimmed several years ago, and probably thousands of sportspeople articles have since been deleted.
Support. (I am not an admin, so I am not sure I can vote. I can see some non-admins voting, but I'm still not sure.) --Moscow Connection (talk) 14:26, 10 January 2025 (UTC) - Conditional support unblock (non-admin vote- if I'm not allowed to vote then please just unbold this vote): add editing restriction for them to use WP:AFC for article creation, and this restriction can be reviewed in 6-12 months if their article creation has been good. Their article mass creation required one of the largest cleanup jobs I have seen on here, and we certainly wouldn't want the same mass-created quasi-notable articles created again. Joseph2302 (talk) 17:05, 10 January 2025 (UTC)
- Support I can't repeat what Beaniefan11 say enough: "Come on – it's been nearly seven years since the ban – why can't we give another chance? And he admits that he was
too focused on quantity, rather than quality
, apologized repeatedly, and his creations as an IP showed that he was no longer focused onmass-creating non-notable stubs
." This should assuage any doubt in the mind of the reviewing administrator. Kenneth Kho (talk) 15:01, 13 January 2025 (UTC) - Oppose Claims of "It's been seven years!" fall on deaf ears when you find out he's been socking all along and as recently as a year ago. Fram and PMC have good points as well. Show some restraint and understanding of your block and WP:SO is yours. Buffs (talk) 23:11, 17 January 2025 (UTC)
Spider-Man: Beyond the Spider-Verse - draft article about a future film seems to be a long-term draft
I have not come across a situation like Draft:Spider-Man: Beyond the Spider-Verse before. Maybe this is fairly common and I have just missed it.
It is a draft article about a film that can not have an article, per WP:NFF. I think the idea is that there is some valuable content there and it would be a shame to delete it when it seems likely that the film will enter final animation and voice recording in the next year or so.
The problem is that it is attracting the sort of speculative edits from IPs that we want to avoid. Both on the draft and the talk page.
I became aware of this because there is a request at WP:RPPI to EC-protect the talk page. But it makes me think we should have some kind of protection for the draft too. But I can see arguments for weaker than ECP (speculation is just by IPs) and for stronger... like... why are people editing it anyway? Maybe there are reasons I am not aware of.
Is anyone more familiar with how we got here? Anyone got any arguments for or against applying semi, EC or full protection to the draft and its talk page?
Edit: Anyone got any thoughts on the concept of having a draft article for a film that doesn't meet WP:NFF?
Yaris678 (talk) 00:39, 29 December 2024 (UTC)
- As far as I'm aware, articles on films are allowed so long as principal photography has occurred (principal animation in this case, I guess?). That has clearly happened for this film, even if they are having to scrap and re-write things. And notability is certainly not in question, so having an article is fully within the policy rules. If there are harmful edits happening, then semi-protection seems like a normal response. Silverseren 00:43, 29 December 2024 (UTC)
- People say that on the draft's talk page every so often and get rebuffed. Maybe you can be more persuasive, but the general argument is the existing animation was created for "Spider-Man: Across The Spider-Verse" before it was split into two films and no "final animation" has begun on this film. Yaris678 (talk) 01:03, 29 December 2024 (UTC)
- Are they basing that claim on any reliable source as evidence? Since what exists in that draft currently with reliable sources clearly indicates work has started. Silverseren 01:11, 29 December 2024 (UTC)
- Hi. I'm the editor who has requested the protection for this draft. Per WP:NFF, final animation or voice recording are the requirement to move a film draft to the mainspace. Final animation is different from standard reels being produced, which as sourced, is currently what this film has produced while no voice recording has occurred. It seems to still be very early in development, and much of the earlier work when this was the second part was reportedly scrapped (as sourced in the draft). I do not believe the mainspace viability ought to be discussed here as that is more for the draft. As for the protection request, it appears to be the same person making these disruptive comments which have become unnecessarily excessive and are detracting from the content of the draft itself. I requested protection (initially as ECP though semi works for the talk) because these comments have not benefitted any actual constructive progress and have largely ranged from the IPs attempting to enforce their own opinions about the delays and trying to remove sources they don't like, which has been ongoing since the end of October. As a draft, not many other editors are editing this, so it becomes quite unrelenting and tiresome to deal with these repeated disruptions. Glad to see this has garnered more attention. Trailblazer101 (talk) 01:20, 29 December 2024 (UTC)
Per WP:NFF, final animation or voice recording are the requirement to move a film draft to the mainspace
...I'm pretty sure that BtSV meets WP:GNG already, regardless of the state of production, and that should be the main factor. - The Bushranger One ping only 03:49, 29 December 2024 (UTC)- I have no problem with the draft being moved, this is just not the normal route to do so and typically NFF is followed for film articles, but I digress. I do caution that this article could be susceptible to further unconstructive comments in the mainspace, but that is a price I'm willing to handle. I can make the move as needed, no worries, I am primarily concerned about these type of comments continuing and if any protection is necessary to prevent or temporarily postpone them from continuing. Trailblazer101 (talk) 05:18, 29 December 2024 (UTC)
- Hi. I'm the editor who has requested the protection for this draft. Per WP:NFF, final animation or voice recording are the requirement to move a film draft to the mainspace. Final animation is different from standard reels being produced, which as sourced, is currently what this film has produced while no voice recording has occurred. It seems to still be very early in development, and much of the earlier work when this was the second part was reportedly scrapped (as sourced in the draft). I do not believe the mainspace viability ought to be discussed here as that is more for the draft. As for the protection request, it appears to be the same person making these disruptive comments which have become unnecessarily excessive and are detracting from the content of the draft itself. I requested protection (initially as ECP though semi works for the talk) because these comments have not benefitted any actual constructive progress and have largely ranged from the IPs attempting to enforce their own opinions about the delays and trying to remove sources they don't like, which has been ongoing since the end of October. As a draft, not many other editors are editing this, so it becomes quite unrelenting and tiresome to deal with these repeated disruptions. Glad to see this has garnered more attention. Trailblazer101 (talk) 01:20, 29 December 2024 (UTC)
- Are they basing that claim on any reliable source as evidence? Since what exists in that draft currently with reliable sources clearly indicates work has started. Silverseren 01:11, 29 December 2024 (UTC)
- People say that on the draft's talk page every so often and get rebuffed. Maybe you can be more persuasive, but the general argument is the existing animation was created for "Spider-Man: Across The Spider-Verse" before it was split into two films and no "final animation" has begun on this film. Yaris678 (talk) 01:03, 29 December 2024 (UTC)
- There doesn't appear to be enough disruption to the draft page to justify protection at this point. Draft talk definitely should get semi-protection. voorts (talk/contributions) 00:45, 29 December 2024 (UTC)
- Really? That seems excessive for a few FOURMy IP comments (likely from the same person). If they continue with it, block the IP, maybe. Protecting talk pages should really be a last resort. Elli (talk | contribs) 00:58, 29 December 2024 (UTC)
- Some people overly use NFF to block any film article that has not confirmed start to production, which is really a bad black/white approach. Most films prior to production are not notable or may not even happen when they are first hinted at, and thus it is absolutely appropriate to use NFF to hold back on a standalone until production starts. But then you have some exceptional cases like this (the 3rd of the animated Spider-Man movies that have earned a massive amount of money and praise, with a lot of attention already given to the film even before production) as well as my own experience with Akira (planned film) which deals with a film that has numerous delays and other incidents that its still nowhere close to production, but its journey that way is readily sourced. NFF should not be used to block creation of articles on films that have this much detail about the work that is otherwise suitable by notability guidelines. For this specific article on the Spider-man film, I see no reason why it could not be in main space at this point as to avoid the whole draft problem. — Masem (t) 05:32, 29 December 2024 (UTC)
- Yeah, there is a point to be made that even if this final film somehow never finished production, it would still be notable because of the coverage of its attempted production history. There's several films (and video games, among other cultural apocrypha) that meet that notability requirement, even without ever actually having been completed and released to the public. Silverseren 05:36, 29 December 2024 (UTC)
- Indeed, a number of aborted films projects are notable exactly because they wound up in development hell. Jodorowsky's Dune is a film about my personal favorite never-got-made film. El Beeblerino 02:59, 30 December 2024 (UTC)
- Yeah, there is a point to be made that even if this final film somehow never finished production, it would still be notable because of the coverage of its attempted production history. There's several films (and video games, among other cultural apocrypha) that meet that notability requirement, even without ever actually having been completed and released to the public. Silverseren 05:36, 29 December 2024 (UTC)
Noting here that Trailblazer101 moved the article from draft space to main space at 22:44, based on the discussion here and WP:GNG. I have not seen any objections to that move since it was done. I have not seen any more speculative or forumy edits recently. There is a good chance they will come back, but if they come back in a serious number the article and/or talk page can be given an appropriate level of protection at that point, or, if the responsible IPs/accounts can be blocked. I think it is probably time to close this discussion. Yaris678 (talk) 10:56, 30 December 2024 (UTC)
- The IP has made three unconstructive and uncivil comments on the talk today (see this diff, and they show no signs of stopping. Trailblazer101 (talk) 18:03, 31 December 2024 (UTC)
- I have blocked that IP. I note that it is possible that some of the other IPs could be the same users and so will block other IPs and/or apply semi-protection if this continues (or encourage others to do the same if I am away from my computer). Yaris678 (talk) 11:51, 1 January 2025 (UTC)
Anyone got any thoughts on the concept of having a draft article for a film that doesn't meet WP:NFF?
Using draftspace to incubate articles on subjects that are not yet notable but almost certainly will be—unreleased films, upcoming elections, sports events, the next in an "X by year" series, and so on—is a common practice and has been as long as I can remember. As such it's listed at WP:DRAFTREASON. – Joe (talk) 12:04, 1 January 2025 (UTC)- Thank you. Yaris678 (talk) 15:01, 1 January 2025 (UTC)
I think it makes sense to archive all threads in Talk:Spider-Man: Beyond the Spider-Verse. They are all either forumy or else asking when the page can be moved to article space, which is no longer relevant since it is in article space. Yaris678 (talk) 20:06, 3 January 2025 (UTC)
- I've updated the archive bot on that talk age to act on 1 month old threads. Should get rid of half of the ones on there when it runs next and the rest will follow soon enough. I've always thought 6 months was way too long of a default archive policy. Silverseren 20:11, 3 January 2025 (UTC)
- Yeah, I've always felt 90 days is sufficient for default archival purposes. If no one has contributed to a discussion in three months, it's a dead discussion. — The Hand That Feeds You: 18:41, 10 January 2025 (UTC)
43.249.196.179 (again)
See their previous thread here, Misplaced Pages:Administrators' noticeboard/IncidentArchive1174#User:Augmented Seventh. Continuing to disrupt and remove categories without explanation, decided to gravedance on my page after restoring edits without any talk page discussion, and has now moved onto disrupting user sandboxes and user pages by removing categories without said user's permission, calling my reversions 'vindicitive' and now considering me their personal 'nemesis' because they don't understand why they're being reverted. Nate • (chatter) 21:16, 31 December 2024 (UTC)
- User:MrSchimpf is not familiar with some of the WP policies and guidelines especially WP:UOWN and WP:CAT. Also, his obfuscated username is somewhat fustration and is not conducive to efficient editing. 43.249.196.179 (talk) 21:21, 31 December 2024 (UTC)
- Special:Diff/1266485663: Editing user pages has no 'hard policy' prohibition, as this is a wiki. 'End of discussion', seriously? Also see WP:NOBAN. Then, Category:Wikipedians is a container category, which clearly says it should only contain subcategories. Even I don't understand why they're being reverted. -- zzuuzz 22:08, 31 December 2024 (UTC)
- User:MrSchimpf seems to be unaware of many of the WP polices and guidelines. 43.249.196.179 (talk) 08:03, 3 January 2025 (UTC)
- I've been here nineteen years so obviously I do and I apologize if as mentioned I'm more aggressive about userspace being in control of the user themselves. That said I'm no longer engaging with you or any of your edits as you're now refusing to drop the stick and trying to troll some kind of response out of me (and doing the same for Liz, who has the patience of a saint), which you won't get. Understand our guidelines or get blocked. If anyone uninvolved would like to close this, please do so. Nate • (chatter) 17:16, 3 January 2025 (UTC)
- Length of time on WP is not a measure of how familiar an editor is with policy and guidelines. Your previous comments show that you are unfamiliar with some of them, but to be fair, it is impossible to know all of them. There are a lot of editors that do not know a lot of the policies and guidelines. THere are content disputes and corrections and reverts happening all the time because of inexperienced editors.
- I am not trolling. I just want WP to be much better than it currently is. 43.249.196.179 (talk) 19:50, 3 January 2025 (UTC)
- I've been here nineteen years so obviously I do and I apologize if as mentioned I'm more aggressive about userspace being in control of the user themselves. That said I'm no longer engaging with you or any of your edits as you're now refusing to drop the stick and trying to troll some kind of response out of me (and doing the same for Liz, who has the patience of a saint), which you won't get. Understand our guidelines or get blocked. If anyone uninvolved would like to close this, please do so. Nate • (chatter) 17:16, 3 January 2025 (UTC)
- Adressing that final point, I have made a proposal about Category:Wikipedians to either remove the container banner tag or give special sanction to empty user pages from that main category. Tule-hog (talk) 21:08, 3 January 2025 (UTC)
- Category:Wikipedians is at a level of the hierarchy that there should be nothing in it, which is why it is a container category. The contents of it have been added by editors who do not understand how WP works and do not realise that it is a container category. You proposal is not needed. 43.249.196.179 (talk) 22:07, 3 January 2025 (UTC)
- User:MrSchimpf seems to be unaware of many of the WP polices and guidelines. 43.249.196.179 (talk) 08:03, 3 January 2025 (UTC)
- Comment: WP:USERNOCAT was cited in this edit (a sandbox used for drafting a larger edit needing discussion, where categories were copied along with the rest of the article's content). (Category:Wikipedians is mentioned explicitly in that guideline.) Tule-hog (talk) 02:49, 1 January 2025 (UTC)
- Whatever the case, user sandbox space is sacred and unless you have permission to edit there, you don't touch them, that's an unwritten rule. Mathglot certainly didn't appreciate it. That's the main issue here and if I was wrong on the cats so be it, but they should not be playing in sandboxes they shouldn't be in. Nate • (chatter) 02:54, 1 January 2025 (UTC)
- Just to clarify: I have no qualms about others making improvements to pages in my users space—which belong to the community and are not "mine"—as long as they are improvements. That said, IP's edits in my userspace look like vandalism to me. Mathglot (talk) 03:04, 1 January 2025 (UTC)
- User namespace is not "sacred". And if there is an unwrittten rule then it is not a rule that needed to be adhered to. Also WP:BOLD. To be a good editor it is important to be familiar with policis and guidelines. 43.249.196.179 (talk) 08:03, 1 January 2025 (UTC)
- Whatever the case, user sandbox space is sacred and unless you have permission to edit there, you don't touch them, that's an unwritten rule. Mathglot certainly didn't appreciate it. That's the main issue here and if I was wrong on the cats so be it, but they should not be playing in sandboxes they shouldn't be in. Nate • (chatter) 02:54, 1 January 2025 (UTC)
- It was not a "gravedance". I was pointing out to you that other editors dont agree with you edits. 43.249.196.179 (talk) 09:15, 1 January 2025 (UTC)
I only just noticed this AN discussion, after placing this warning at User talk:43.249.196.179 about vandalizing a Draft template in my user space. Their edits seem somehow to be related to categories, but near as I can guess from their edit summary here, they also had some inscrutable complaint about me using my userspace as "social media". Maybe interested parties here will understand what they are talking about, because I certainly don't. As of this point, I cannot tell if they are well-meaning, but highly misinformed and uncomprehending, or if they are simply trolling everyone. I suspect the latter, but am willing to be proved wrong, especially if enceforth they stick to guidelines and talk things out, instead of ignoring advice given previously and edit-warring. Mathglot (talk) 03:00, 1 January 2025 (UTC)
- Okay, now I am sure: see this edit at my Talk page, quickly reverted by Remsense while I was in the process of reverting it. This is clearly intentional, malicious, vandalism, as well as retaliation. Therefore, I propose an indefinite block on 43.249.196.179 (talk · contribs) as it is a vandalism-only account. Mathglot (talk) 03:13, 1 January 2025 (UTC)
- I haven't looked into this editor's edits but we don't indefinitely block IP editors as the IP account can easily be assigned to a different user. But they can receive longtime blocks on the order of months or years. Liz 04:33, 1 January 2025 (UTC)
- You are looking at two different IP addresses. Getting things right is important. 43.249.196.179 (talk) 07:53, 1 January 2025 (UTC)
- Honestly, whether that was a Joe Job or not, your behavior is indistinguishable from trolling & deserves a block. — The Hand That Feeds You: 18:45, 10 January 2025 (UTC)
Incivility at Talk:Azerbaijan Airlines Flight 8243
@Dreameditsbrooklyn and to a lesser extent @Aviationwikiflight have been bickering in the talk page for a while now, and the reply chains are so long that they go off my phone's screen. DEB in particular has been noticeably passive aggressive in their comments, such as these diffs at me, this diff at AWF, and this diff at User:Awdqmb. Is this actionable? guninvalid (talk) 01:57, 2 January 2025 (UTC)
- This looks to me like it's covered by WP:ARBEE. Animal lover |666| 02:18, 2 January 2025 (UTC)
- I have yet to dig through the very length discussions, but on the surface I can say that I'm glad to see it not turning into much of an edit war in the article itself, and remaining mostly on the talk page. Infact the only person who breached 2R's was someone you didn't mention, and interestingly was never warned, but I placed a soft warning on their talk page. As far as the specific diffs provided, I don't see anything in there which is all that problematic, unless you're deeply intrenched in the issue. I would proffer is that if someone says, in it's entirety
I am stating a fact.
and you take offence to that, then you might need to back away from the discussion for a few days. TiggerJay (talk) 02:47, 2 January 2025 (UTC)"...then you might need to back away from the discussion for a few days".
You're probably right about that. guninvalid (talk) 02:58, 2 January 2025 (UTC)
- This seems entirely unnecessary. Dreameditsbrooklyn (talk) 03:13, 2 January 2025 (UTC)
- Can you elaborate on which aspect of
this
you are referring to that you believe is unnecessary? TiggerJay (talk) 03:55, 2 January 2025 (UTC)- By this, I mean bringing the issue to ANI. If I owe anyone an apology, I stand ready to give it, but @Guninvalid hasn't really been involved in the discussion until very recently and has already escalated it here. Dreameditsbrooklyn (talk) 03:59, 2 January 2025 (UTC)
- It doesn't matter how much someone has been involved in a discussion. If there's misconduct that's not clearly going to get resolved on its own (which I'm not confident saying either way here), then it's a public service, even a responsibility, for an editor to report it. Thebiguglyalien (talk) 05:58, 2 January 2025 (UTC)
- @Dreameditsbrooklyn you can see my initial assessment of the situation above. However, I will say uninvolved editors are welcome to bring valid concerns to ANI. It is often far more helpful when someone outside of the situation brings it up here as it ends up being far more neutral. I also would suggest that you might also be too involved right now and need to back away for a few days. The biggest reason is that I believe you read right past Animal lover's and my response which basically didn't find you doing anything wrong. I suggest that a cooling off period might be good for you as well. Not because you're currently doing anything wrong (because that conversation would look quite different), but rather that you're likely too invested in this topic right now to see rationally and objectively. TiggerJay (talk) 06:18, 2 January 2025 (UTC)
- It was not my intent to ignore those assessments, and I understand what you've said as far as uninvolved editors raising such issues (real or perceived). Dreameditsbrooklyn (talk) 19:26, 2 January 2025 (UTC)
- Also, as a note, this isn't ANI... - The Bushranger One ping only 07:09, 2 January 2025 (UTC)
- By this, I mean bringing the issue to ANI. If I owe anyone an apology, I stand ready to give it, but @Guninvalid hasn't really been involved in the discussion until very recently and has already escalated it here. Dreameditsbrooklyn (talk) 03:59, 2 January 2025 (UTC)
- Can you elaborate on which aspect of
- Infact I don't know why such a simple infobox change discussion will resulted in endless arguments. And it happened in mutiple pages, like this Voepass crash case, this Swiftair crash case, and now this Azerbaijan Airlines crash case there. And I'm afraid there would be other arguements in previous pages.
- But to be honest, I think I also have some responsibilities on this endless situation: I have known what to do to deal with such major changes, but I didn't really take any action. Awdqmb (talk) 07:14, 2 January 2025 (UTC)
- The whole "Accident vs Crash" thing has been going on for a while now. It pretty much goes nowhere every time. DEB gives a whole bunch of reasons why "accident" should be avoided, AWF gives a whole bunch of reasons why "accident" is perfectly fine, and it all repeats with every new WP:AIRCRASH article. I just recommended on DEB's talk page that they try to seek a wider consensus to break this endless cycle, because I for one am tired of seeing the same arguments over and over again with no progress. - ZLEA T\ 08:02, 2 January 2025 (UTC)
- Infact you can check the talkpage I provided, you will find such arguments have happened on mutiple pages. Awdqmb (talk) 08:09, 2 January 2025 (UTC)
- Since the regular editors in this topic area have proven that they are unable to resolve this utterly trivial terminology dispute among themselves, perhaps the best solution might be to topic ban every consistent advocate of "accident" and to topic ban every consistent advocate of "crash" from all articles about airplane mishaps, and let entirely uninvolved editors make a reasonable decision. Because endless bickering among entrenched advocates is disruptive. Topic bans could then be lifted on editors who explicitly agree to stop beating a dead horse and drop the terminology issue forever. Cullen328 (talk) 08:25, 2 January 2025 (UTC)
- It's less "unable to resolve" and more "Dreameditsbrooklyn argues that using 'accident' is original research because the sources use 'crash'" and I wish I was joking. Your modest proposal probably would get some kind of result though! - The Bushranger One ping only 08:27, 2 January 2025 (UTC)
- Infact I have already suggested to delete this controversial value on the talkpage of the template, since it have not much actural use to show, and mostly have the same contents with the "Summary" value. And ironically, it has showed the available value on the doc page, but the example they showed on simply violate it! But since then nobody really talk about it yet. Awdqmb (talk) 08:34, 2 January 2025 (UTC)
- As someone who has consistently been on the side "accident is fine" of this argument (there really isn't an "accident/crash" binary here, just whether "accident" is original research), I think that's a bit extreme. I laid out a plan to seek wider consensus on DEB's talk page, which should hopefully help resolve the issue once and for all without the need for more drastic measures. - ZLEA T\ 09:20, 2 January 2025 (UTC)
- Respectfully, the descriptions aren't trivial. A "crash" describes what happened. An "accident" implies someone made a mistake with no real culpability. An "incident" implies some sort of interaction or series of events. I have no specific dog in this fight and I don't believe I've voiced any significant opinion on the matter here or elsewhere, but such a description is not trivial when we are trying to be neutral in our descriptions. In this particular case, it very much appears that the act was deliberate and the airliner was acceptable collateral damage (in their opinion). At a minimum, it's disputed. As such, "accident" isn't appropriate as it is at least alleged to be a deliberate act or negligence. "Incident" or "crash" would be more neutral. If we say "accident" it implies no one should be blamed and fails WP:Neutral. Buffs (talk) 22:22, 2 January 2025 (UTC)
- If only it were that simple (the context of aviation has been explicitly excluded from at least one discussion on the matter). We could go over whether "accident" actually implies no culpability in the context of aviation all day, but this is not the place to do it. As I stated numerous times, we need to formally establish a project-wide consensus about this, and WT:AATF is a good place to start. As for this discussion, I think it can be closed as the issue in question is very minor. - ZLEA T\ 22:42, 2 January 2025 (UTC)
- WP:MOS says:
If any contradiction arises, this page has precedence.
- WP:AT, which follows MOS says:
Generally, article titles are based on what the subject is called in reliable sources.
- The very broad majority of RS call this a crash. Why, in this case, doesn't this apply? Because some editors disagree? I am honestly asking. I don't see a policy which overrules MOS here. Also, I'll hold off on any new discussions on this until things have concluded here and at the article talk page, where the same editor who started this discussion opened an RfC on the topic. Dreameditsbrooklyn (talk) 22:58, 2 January 2025 (UTC)
- I will not continue this off-topic discussion here. If the same perceived problem is happening across multiple WT:AATF articles, then the discussion needs to be moved there to finally end the cycle and come to a consensus. - ZLEA T\ 23:06, 2 January 2025 (UTC)
- I'm not sure WP:AATF is the correct venue to continue the discussion for a number of reasons, which I will spare going into here. Dreameditsbrooklyn (talk) 23:14, 2 January 2025 (UTC)
The very broad majority of RS call this a crash. Why, in this case, doesn't this apply?
Because simple issues of phraseology don't need to "follow the sources", and insisting that they do is WP:WIKILAWYERING. - The Bushranger One ping only 01:38, 4 January 2025 (UTC)- Others have rejected this as the venue to hold this debate, and I will too. I suggest you follow your own advice and drop the stick, at least for now. Dreameditsbrooklyn (talk) 02:06, 4 January 2025 (UTC)
- I'm not sure WP:AATF is the correct venue to continue the discussion for a number of reasons, which I will spare going into here. Dreameditsbrooklyn (talk) 23:14, 2 January 2025 (UTC)
- I will not continue this off-topic discussion here. If the same perceived problem is happening across multiple WT:AATF articles, then the discussion needs to be moved there to finally end the cycle and come to a consensus. - ZLEA T\ 23:06, 2 January 2025 (UTC)
- WP:MOS says:
An "accident" implies someone made a mistake with no real culpability
No, it does not. The International Civil Aviation Organization, which is somewhat of an authority on the matter, defines an 'aircraft accident' asAccident. An occurrence associated with the operation of an aircraft ..., in which: a) a person is fatally or seriously injured b) the aircraft sustains damage or structural failure c) the aircraft is missing or is completely inaccessible
. Notice what isn't there - anything about mistakes or culapbility. @Buffs: "Accident" is the official internationally recognized term for this sort of occurance, and is entirely neutral in use. Note that "incident" has a very specific term in aviation which is "an occurrence, other than an accident, associated with the operation of an aircraft that affects or could affect the safety of operation." @Dreameditsbrooklyn: I'd suggest you drop the stick and stop pushing this personal intrepretation. - The Bushranger One ping only 23:51, 2 January 2025 (UTC)- Why do you think this jargon use should take precedence over the common meaning of the word? The word "accident" can be used in (at least) two senses, one of which involves a lack of intention -- the fact that the ICAO (who?) says that they use the word "accident" in only one of these senses isn't somehow magically binding on everyone else who uses the word in the context of aviation. Given the choice between a word with two ambiguous senses, one of which inappropriate, and a word that has only one relevant sense, it's obvious that the latter word will be clearer, isn't it? 50.224.79.68 (talk) 04:12, 3 January 2025 (UTC)
- International Civil Aviation Organization. The people whose job it is to establish these things for aviation. It's not the use of one word for the other that I have a problem with. It's the argument that, somehow, using "accident" constitutes original research when in fact it is the correct terminology - and in fact some of the suggested alternatives are explicitly incorrect terminology - is the problem. And no, its not "magically binding", but common useage in the context of aviation is to refer to any crash as an "aviation accident", just like how if somebody deliberately rear-ends you in road rage it's still a "car accident" - it isn't WP:JARGON. - The Bushranger One ping only 09:25, 3 January 2025 (UTC)
- Do you think there was a car accident in New Orleans a few days ago? When you appeal to an organization like ICAO for what the meaning of a common word is, you are by definition using jargon. 2600:1700:47F8:800F:0:0:0:1BF7 (talk) 17:58, 3 January 2025 (UTC)
- When you appeal to an expert for the meaning of a word in the context of what it's being used in, that's common sense. - The Bushranger One ping only 21:59, 3 January 2025 (UTC)
- It’s the very definition of the word jargon! No wonder people are finding you impossible to deal with. 108.169.132.163 (talk) 18:57, 4 January 2025 (UTC)
- When you appeal to an expert for the meaning of a word in the context of what it's being used in, that's common sense. - The Bushranger One ping only 21:59, 3 January 2025 (UTC)
- What is "an occurrence, other than an accident..." if "accident" includes "incidents"? Definition you're claiming here doesn't make a lot of sense. Buffs (talk) 19:03, 3 January 2025 (UTC)
- Accident =/= incident, which I believed was clear. - The Bushranger One ping only 21:59, 3 January 2025 (UTC)
- Incident includes accidents AND intentional acts. Buffs (talk) 18:34, 4 January 2025 (UTC)
- Not according to the ICAO definition, but this probably is something best not continued here I reckon. - The Bushranger One ping only 18:40, 4 January 2025 (UTC)
- Incident includes accidents AND intentional acts. Buffs (talk) 18:34, 4 January 2025 (UTC)
- Accident =/= incident, which I believed was clear. - The Bushranger One ping only 21:59, 3 January 2025 (UTC)
- Do you think there was a car accident in New Orleans a few days ago? When you appeal to an organization like ICAO for what the meaning of a common word is, you are by definition using jargon. 2600:1700:47F8:800F:0:0:0:1BF7 (talk) 17:58, 3 January 2025 (UTC)
- International Civil Aviation Organization. The people whose job it is to establish these things for aviation. It's not the use of one word for the other that I have a problem with. It's the argument that, somehow, using "accident" constitutes original research when in fact it is the correct terminology - and in fact some of the suggested alternatives are explicitly incorrect terminology - is the problem. And no, its not "magically binding", but common useage in the context of aviation is to refer to any crash as an "aviation accident", just like how if somebody deliberately rear-ends you in road rage it's still a "car accident" - it isn't WP:JARGON. - The Bushranger One ping only 09:25, 3 January 2025 (UTC)
- Why do you think this jargon use should take precedence over the common meaning of the word? The word "accident" can be used in (at least) two senses, one of which involves a lack of intention -- the fact that the ICAO (who?) says that they use the word "accident" in only one of these senses isn't somehow magically binding on everyone else who uses the word in the context of aviation. Given the choice between a word with two ambiguous senses, one of which inappropriate, and a word that has only one relevant sense, it's obvious that the latter word will be clearer, isn't it? 50.224.79.68 (talk) 04:12, 3 January 2025 (UTC)
- I did not bring this up to WP:AN to litigate whether to use "crash" or "accident". If you would like to litigate that, I have started a RfC on the Talk page. I brought this here to ask the admins to discuss whether DEB's and AWF's behavior is worth pursuing administrator action. guninvalid (talk) 01:09, 3 January 2025 (UTC)
- If only it were that simple (the context of aviation has been explicitly excluded from at least one discussion on the matter). We could go over whether "accident" actually implies no culpability in the context of aviation all day, but this is not the place to do it. As I stated numerous times, we need to formally establish a project-wide consensus about this, and WT:AATF is a good place to start. As for this discussion, I think it can be closed as the issue in question is very minor. - ZLEA T\ 22:42, 2 January 2025 (UTC)
- Since you think this is an "utterly trivial terminology dispute" should I tag you in the RFC at WP:RS when I make it, or not? I don't wish to bother you if it's not important to you. Dreameditsbrooklyn (talk) 22:31, 3 January 2025 (UTC)
- Since the regular editors in this topic area have proven that they are unable to resolve this utterly trivial terminology dispute among themselves, perhaps the best solution might be to topic ban every consistent advocate of "accident" and to topic ban every consistent advocate of "crash" from all articles about airplane mishaps, and let entirely uninvolved editors make a reasonable decision. Because endless bickering among entrenched advocates is disruptive. Topic bans could then be lifted on editors who explicitly agree to stop beating a dead horse and drop the terminology issue forever. Cullen328 (talk) 08:25, 2 January 2025 (UTC)
- Infact you can check the talkpage I provided, you will find such arguments have happened on mutiple pages. Awdqmb (talk) 08:09, 2 January 2025 (UTC)
- The whole "Accident vs Crash" thing has been going on for a while now. It pretty much goes nowhere every time. DEB gives a whole bunch of reasons why "accident" should be avoided, AWF gives a whole bunch of reasons why "accident" is perfectly fine, and it all repeats with every new WP:AIRCRASH article. I just recommended on DEB's talk page that they try to seek a wider consensus to break this endless cycle, because I for one am tired of seeing the same arguments over and over again with no progress. - ZLEA T\ 08:02, 2 January 2025 (UTC)
- I know this discussion is about conduct, not about the disagreement which prompted it, but I'll note that the other user named here and who has not responded has since changed several instances of the word 'crash' to accident on other entries and has also since been accused of violating 3RR on the very entry which prompted this discussion. I've agreed to confine any further conversations to the talk page until a consensus is reached, wherever that may be. Dreameditsbrooklyn (talk) 02:46, 3 January 2025 (UTC)
- On the very entry for a completely different reason regarding the use of the Aviation Safety Network but I concede that whilst I was within the limits of 3RR, it probably shouldn't have gotten to that point in the first place.
... since changed several instances of the word 'crash' to accident on other entries
– The only changes made were either related to a change within the infobox to stay consistent with Template:Infobox aircraft occurrence as the occurrence type on the aforementioned article statedAirliner crash
, or related to changes regarding short descriptions since they were changed to be phrased in a way that is not usually done. It's not like I removed every single mention of the word crash and replaced it with accident. But back to the main topic, I'm willing to drop the issue as long as it's not an problem to use accident in articles relating to aviation. Aviationwikiflight (talk) 03:40, 3 January 2025 (UTC)
- On the very entry for a completely different reason regarding the use of the Aviation Safety Network but I concede that whilst I was within the limits of 3RR, it probably shouldn't have gotten to that point in the first place.
Can we close this? The current discussion has next to nothing to do with the original issue and is best continued somewhere else. - ZLEA T\ 19:03, 4 January 2025 (UTC)
- Agreed. An admin got involved and simply continued off-topic discussion. guninvalid (talk) 21:33, 4 January 2025 (UTC)
- Warn both to drop the stick, otherwise, no action at this point. FOARP (talk) 15:57, 8 January 2025 (UTC)
- Hands FOARP two trouts You want to hand them out, or me? Buffs (talk) 16:32, 9 January 2025 (UTC)
Topic ban appeal
There is consensus against lifting the topic ban at this time. DesertInfo is advised to find areas where they are willing to edit to show a better history prior to revisiting the topic ban in the future. Star Mississippi 15:07, 12 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
Hello, I have a topic ban that is approaching one year old on "undiscussed moves, move discussions, deletion discussions, and racial issues broadly construed (including topics associated with the Confederate States of America)". I would like an opportunity to contribute to these topics again. I have been fairly inactive since then but I have edited a few articles without issue. Thank you. DesertInfo (talk) 04:36, 3 January 2025 (UTC)
- I'll kick off by asking the standard two questions: (1) please explain in your own words why you were topic banned; (2) do you have anything to say to convince everyone those same issues won't occur again? WaggersTALK 14:01, 3 January 2025 (UTC)
- I was topic banned for not assuming good faith and making an allegation that someone was using a sockpuppet when I was unable to provide substantial evidence. The topic ban was appealable after 3 months but I stepped away for almost a year. I am ready to discuss these topics respectfully and understand the importance of patience and communication. ANI should be a last resort. DesertInfo (talk) 18:29, 3 January 2025 (UTC)
- Can you provide a link to the discussion where this topic ban was imposed? Thank you. Liz 04:05, 4 January 2025 (UTC)
- Found it. Misplaced Pages:Administrators' noticeboard/IncidentArchive1097#Desertambition's hostile edit history. Tarlby 04:35, 4 January 2025 (UTC)
- Thank you. That is helpful to have. Liz 07:19, 4 January 2025 (UTC)
- Found it. Misplaced Pages:Administrators' noticeboard/IncidentArchive1097#Desertambition's hostile edit history. Tarlby 04:35, 4 January 2025 (UTC)
- Can you provide a link to the discussion where this topic ban was imposed? Thank you. Liz 04:05, 4 January 2025 (UTC)
- I support lifting the ban. DI's talk page makes for interesting reading, it shows quite a remarkable change in attitude over a period of a few years, and I believe that's genuine. WaggersTALK 08:58, 6 January 2025 (UTC)
- I was topic banned for not assuming good faith and making an allegation that someone was using a sockpuppet when I was unable to provide substantial evidence. The topic ban was appealable after 3 months but I stepped away for almost a year. I am ready to discuss these topics respectfully and understand the importance of patience and communication. ANI should be a last resort. DesertInfo (talk) 18:29, 3 January 2025 (UTC)
- Oppose lifting the topic ban I think being warned for making edits that violating a topic ban, then being almost completely inactive for six months, and then coming back and asking for it to be lifted and that passing sets a horrible example. * Pppery * it has begun... 06:31, 7 January 2025 (UTC)
- It seemed like a good idea to step away from the site for a time. I was receptive to the warning, even though it was not from an admin, and stopped editing in that area entirely. These are the edits in question: I just forgot that I had to appeal the topic ban here first and haven't gotten around to it until now. It should be noted that the first edit merely restored a previous RFC that had been ignored and the last two were minor changes to articles that have since been restored.
- I have never made a different account or tried to dishonestly avoid the topic ban and I never will. All I ask is that you WP:AGF and give me a chance to show that I can contribute collaboratively and have matured. DesertInfo (talk) 21:51, 7 January 2025 (UTC)
- Only 106 edits since unblocking (including the unblocking), of which includes apparently no edits to article talkpages, which is where a lot of the issues emerged. There's not much to really evaluate change. CMD (talk) 07:24, 7 January 2025 (UTC)
- I have largely avoided getting involved in article talk pages in order to avoid violating the topic ban. If I were to get involved in these topics to demonstrate change, it would be in violation of the topic ban. Seems like a catch-22. DesertInfo (talk) 20:51, 7 January 2025 (UTC)
- There are literally millions of articles and talk pages not covered by your topic ban. You are expected to demonstrate change there. Why on earth do you think this makes it a catch-22 situation?!? --Yamla (talk) 22:06, 7 January 2025 (UTC)
- I have made plenty of edits to articles like Caribbean Basin, List of current detainees at Guantanamo Bay, Venezuelan Caribbean, and List of archipelagos in the meantime without issue, there was no need to discuss it on the talk page. I have tried to make clear edit summaries and contribute to the encyclopedia. DesertInfo (talk) 22:45, 7 January 2025 (UTC)
- There are literally millions of articles and talk pages not covered by your topic ban. You are expected to demonstrate change there. Why on earth do you think this makes it a catch-22 situation?!? --Yamla (talk) 22:06, 7 January 2025 (UTC)
- I have largely avoided getting involved in article talk pages in order to avoid violating the topic ban. If I were to get involved in these topics to demonstrate change, it would be in violation of the topic ban. Seems like a catch-22. DesertInfo (talk) 20:51, 7 January 2025 (UTC)
- Oppose lifting the topic ban. As per Chipmunkdavis, there have been very few edits since the unblock in February 2024. Although DesertInfo says "I have made plenty of edits", I just don't see enough here to justify lifting the topic ban. I'll also note that at least some of these edits came close to violating the topic ban (see User_talk:DesertInfo#Topic_ban for example). --Yamla (talk) 23:02, 7 January 2025 (UTC)
- Oppose at this time I appreciate that you walked away rather than risk violating the ban. that shows some recognition of the issue and willingness to try and do something about it. However, what we would want to see would be a decent track record of editing over a sustained period without any hint of violating the ban, and you are just not there yet. Beeblebrox 23:15, 7 January 2025 (UTC)
- I have edited multiple articles without issue. I don't understand why I would edit articles I'm not interested in/knowledgeable about. I don't want to add useless info or talk page comments for the sake of adding it. I have tried to contribute to articles I know something about. The topic ban is very broad and could reasonably be argued to cover most history/politics subjects.
- I made a genuine mistake half a year ago that was not egregious and did not violate the topic ban, only coming close. When reminded of the topic ban, I stopped immediately. The topic ban was appealable after 3 months. I was told to step away from editing entirely for a long period of time and I did:
- This ban has been in place been in place since 2022, over 3 years. A lot has changed and I have matured greatly. DesertInfo (talk) 23:36, 7 January 2025 (UTC)
- The topic ban is not so broad as to cut off most of en.wiki. Aside from the move and deletion restrictions, which are technical and do not restrict editing from any particular page, the topic ban is just "racial issues broadly construed". Do you really feel that this covers every article you are either interested in or knowledgeable about? Do you really feel you can't participate in talkpages without infringing on this? CMD (talk) 01:50, 8 January 2025 (UTC)
- I would like to participate in move and deletion discussions. I contributed a lot to List of renamed places in South Africa and I would like to update some place names through move requests. I haven't had issues in that area since 2022. DesertInfo (talk) 05:24, 12 January 2025 (UTC)
- The topic ban is not so broad as to cut off most of en.wiki. Aside from the move and deletion restrictions, which are technical and do not restrict editing from any particular page, the topic ban is just "racial issues broadly construed". Do you really feel that this covers every article you are either interested in or knowledgeable about? Do you really feel you can't participate in talkpages without infringing on this? CMD (talk) 01:50, 8 January 2025 (UTC)
- Comment - I'd say
"racial issues broadly construed"
is actually pretty broad given how much of history/geography is touched by it. I'd also say they do appear to have made an effort to improve, though I'd still like to see more. FOARP (talk) 16:03, 8 January 2025 (UTC) - Oppose I want to see some real world effort working collaboratively somewhere else on wp, not just a six month gap waiting it, off wikipedia. There is no evidence here that there has been a change. scope_creep 08:26, 11 January 2025 (UTC)
Andra Febrian report
HiLux duck has been blocked, and no further action is needed here. Star Mississippi 15:10, 12 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
"Andra Febrian" is disrupting many edits, I have seen many deleted edits by this user, and I would like to report the user for causing many edit wars. The edits unreasonably reverted by this user is very disruptive to me, as I only intend for useful contributions. The user has:
- caused many edit wars
- deleted citations along with deleting correct claims
- not been cooperative (wikipedia's Editing policy) on many pages that good-intended edits have occurred on
- not explained deletions of citations in a way that other users have been made upset.
I request that the user is warned.
HiLux duck — Preceding undated comment added 22:13, 3 January 2025 (UTC)
- First: the notice at the top of the page clearly says to place new sections at the bottom of the page, which I have now done for you. Second: you need to provide diffs for the edits you are complaining about. Third, you were supposed to notify Andra Febrian per the instructions at the top of the page. Another user has done so for you. - Donald Albury 00:06, 4 January 2025 (UTC)
- @HiLux duck: please sign your comments using ~~~~, which will add a timestamp. Additionally, I reverted your edits to Peugeot 3008 and to Exeed because you are changing information in articles without citing reliable sources. You must cite sources when you add or change information in articles. voorts (talk/contributions) 00:20, 4 January 2025 (UTC)
- HiLux duck just filed a new complaint at ANEW and made the exact same mistakes as they did here. I advised them to stop posting complaints on noticeboards until they can follow the instructions. Liz 07:18, 4 January 2025 (UTC)
- FWIW, I have a feeling that HiLux Duck is a sockpuppet of MrDavr, but I am holding back until they give themselves enough rope to hang. Same obsession with defining overall lengths for various car classifications and edit warring at length over them. Mr.choppers | ✎ 00:55, 6 January 2025 (UTC)
- I'm always impressed when editors can recall editing habits of editors that were blocked years ago. I guess I lack the longterm memory to keep track of sockpuppet habits. Liz 04:14, 6 January 2025 (UTC)
- @Liz: MrDavr actually got under my skin at one point; otherwise I probably wouldn't have noticed. Thanks, Mr.choppers | ✎ 02:04, 7 January 2025 (UTC)
- Looking into this Looks like a duck to me (a HiLux WP:Duck?) because yeah, this is exactly the same editing pattern. Same username pattern as a number of MrDavr socks too (car names/variations thereof - Toyota Hilux). - The Bushranger One ping only 09:49, 6 January 2025 (UTC)
- Most likely yes, I knew that the his editing patterns matched an old blocked user but didn't remember the name. Alawadhi3000 (talk) 16:14, 6 January 2025 (UTC)
- It's also interesting to note that HiLux duck's user page claims they've been on Misplaced Pages since 2019, and having compared edits more extensively I've seen enough and gone ahead and blocked per WP:DUCK. - The Bushranger One ping only 20:20, 6 January 2025 (UTC)
- I'm always impressed when editors can recall editing habits of editors that were blocked years ago. I guess I lack the longterm memory to keep track of sockpuppet habits. Liz 04:14, 6 January 2025 (UTC)
- FWIW, I have a feeling that HiLux Duck is a sockpuppet of MrDavr, but I am holding back until they give themselves enough rope to hang. Same obsession with defining overall lengths for various car classifications and edit warring at length over them. Mr.choppers | ✎ 00:55, 6 January 2025 (UTC)
- HiLux duck just filed a new complaint at ANEW and made the exact same mistakes as they did here. I advised them to stop posting complaints on noticeboards until they can follow the instructions. Liz 07:18, 4 January 2025 (UTC)
Mr.Choppers warning request
- This was (again) posted at the top instead of the bottom; it seems like it is not really a separate issue. 100.36.106.199 (talk) 01:54, 7 January 2025 (UTC)
User:Mr.Choppers has not followed the WP:Civility rules because:
- calling me a "nuisance" because of own bias supporting others in edit wars that have nothing to do with the user. (WP:Civility) (WP:Civility (second violation this user has performed))
- responded fairly aggressively to another user (me) without me being aggressive back or starting this edit war
- note that he also called me a "sockpuppet of a banned user" without reliable clarification, also biased on that
- also note the user had not informed me and used aggression to support own claims.
I would like to inform that this user has unnecessarily used aggression and claimed things not there. Kind regards, HiLux duck (talk) 2:29, 6 January 2025 (GMT+12)
- Missed this because it was at the top. Very unlikely to have merit and is moot now, given the block. - The Bushranger One ping only 02:24, 7 January 2025 (UTC)
user:Uwappa: refusal to engage with WP:BRD process, unfounded allegation of WP:NPA violation, unfounded vandalism allegation
I have indefinitely blocked Uwappa per WP:NLT. Whilst the legal threat pointed out by multiple editors may be very vague, it certainly is designed to have a chilling effect, and Uwappa has confirmed this with this addition to the section. Quite apart from that, we have persistent edit-warring, meritless claims of vandalism against others, and there is a limit to which an editor who thinks all of this is a big joke can be allowed to waste everybody else's time. They can explain themselves in an unblock request if they so desire. Black Kite (talk) 22:57, 6 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
repost from archive:
The content disagreement behind this report is trivial in the overall scope of Misplaced Pages (although the articles affected are subject to WP:MEDRS), but the editor behaviour is not. My reason to bring this case to ANI is that user:Uwappa rejects some basic principles of the project: WP:BRD means that a bold edit may be reverted to the status quo ante and goes on to say don't restore your bold edit, don't make a different edit to this part of the page, don't engage in back-and-forth reverting, and don't start any of the larger dispute resolution processes. Talk to that one person until the two of you have reached an agreement.
Despite having been reminded about BRD after their first immediate counter-revert, they responded to the reversion to the sqa with another counter-revert and, after another editor reinstated the sqa, counter-reverted again. At no stage did they attempt to engage in BRD discussion. Both I and the other editor attempted to engage with them at their talk page: Uwappa characterises my explanation as a personal attack. On another page, Uwappa reverted an edit where I suppressed the questioned material template, declaring it "vandalism" in the edit summary. I recognise the rubric at BRD that says BRD is optional, but complying with Misplaced Pages:Editing policy § Talking and editing and Misplaced Pages:Edit war is mandatory
but Uwappa has done neither.
I consider my escalating this to ANI to be a failure of negotiating skill on my part but, while Uwappa refuses to engage, I am left with no choice. Allowing a few days for logic to intervene has not been fruitful. With great reluctance, because Uwappa has made valuable contributions, I have to ask that they be blocked until they acknowledge and commit to respect the principles that underlie BRD, WP:CONSENSUS and WP:OWN.
Diffs: (all timestamps UTC. NB that I am in England => UTC+00:00, Uwappa is in Australia => UTC+10:00 )
- 11:10 (UTC), 25 December 2024: Uwappa replaces {{Body roundness index}} with a substantially changed new version
- 13:39, 25 December 2024: JMF (me) reverts to the previous version, with edit summary "sorry but this version is not ready for release. I will explain at talk page."
- 13:55, 25 December 2024: JMF opens Template talk:Body roundness index#Proposed version 4 is a step too far, reverted for further discussion at template talk page (and leaves notifications at the talk pages of the articles that invoke the template).
- 14:08, 25 December 2024: Uwappa responds minimally at template talk page.
- 14:27, 25 December 2024: Uwappa counter-reverts to their new version of the template, no edit summary.
- 14:39, 25 December 2024 JMF reverts the counter reversion with edit summary "see WP:BRD: when BRD is invoked, the status quo ante must persist until consensus is reached"
- 14:45, 25 December 2024: Uwappa counter-reverts the template again, no edit summary.
- 14:45, 25 December 2024: at User talk:Uwappa#Bold, revert, discuss, JMF advises Uwappa of the BRD convention.
- 17:38, 25 December 2024: Zefr contributes to BRD debate.
- 17:53, 25 December 2024: At Uwappa's talk page, JMF notifies Uwappa of edit-warring using {{uw-editwar}} with edit summary "I advise strongly that you self-revert immediately, otherwise I shall have no choice but to escalate."
- 19:50, 25 December 2024 At Waist-to-height ratio, JMF comments out invocation of the template, with edit summary "use of template suspended pending dispute resolution . See talk page."
- (a series of reverts and counter reverts follow, in which Uwappa alleges vandalism by JMF. Neither party breaks 3RR.)
- 20:23, 25 December 2024 At their talk page, Uwappa rejects the request to self-revert and invites escalation. Edit summary: "go for it".
- 16:19, 26 December 2024 user:Zefr reverts the counter-reversion of the template to re-establish sqa
- 09:57, 27 December 2024 Uwappa reinstates their counter-reversion of the template.
- 09:59, 27 December 2024 Uwappa contributes to the BRD discussion only to say "See also User_talk:Uwappa#Edit_warring for escalation in progress.".
- 11:05, 27 December 2024 JMF reverts to sqa again, with edit summary " rv to consensus version, pending BRD discussion. That is now also a WP:3RR violation." My 3RR challenge was not valid as reversion was outside the 24-hour window.
- 11:26, 27 December 2024 At Uwappa's talk page, JMF advises Uwappa to take a break from editing.
- 13:04, 27 December 2024 At their talk page, Uwappa alleges WP:NPA violation. I will leave it to others to decide whether the allegation has merit.
---
- 10:51, 29 December 2024 At Uwappa's talk page, JMF suggests that we let the status quo stand and we all walk away without escalating to ANI.
- 14:17, 29 December 2024 Uwappa replies to refuse de-escalation.
As of 11:48 (UTC) on 30/12, the live version of the template is the one that has consensus support. --𝕁𝕄𝔽 (talk) 11:59, 30 December 2024 (UTC)
- Well, Uwappa hasn't edited on the project in 12 hours so it's pretty sage to assume they haven't seen this complaint yet. I'd like to hear their response and whether or not they are willing to collaborate before passing any judgment. Very through presentation of the dispute, easy to follow, so thank you for that. Liz 20:04, 30 December 2024 (UTC)
- Yes, that is why I felt it important to make clear that our time zones are very widely spaced, which makes collaboration difficult in the best of circumstances. When they do see it, I would expect they will take some time offline to polish their response before posting it – and consequently it is likely to be as long again before I respond. 𝕁𝕄𝔽 (talk) 20:35, 30 December 2024 (UTC)
Reposted above from archive, see User_talk:Uwappa#c-JMF-20250105190300-Uwappa-20250105161700
JMF suggested to add the following bit from my talk page:
- You escaped sanction because there were too many more egregious cases in the pipeline and it is a first offence. ANI does not adjudicate on content disputes, only on behaviour and compliance with fundamental principles. The evidence against you was really unarguable; I have seen quite a few cases and I know how they play out: if it had reached a conclusion, you would have been blocked until you acknowledged that you had gotten carried away in the heat of the moment, that you understand and accept WP:EPTALK, WP:EW, WP:CONSENSUS and WP:OWN, and that from now on you commit to respecting them. I strongly advise that you take the message anyway. --𝕁𝕄𝔽 (talk) 12:47, 5 January 2025 (UTC)
- Mate, sorry I was late for the escalation party. End of the year was a madhouse here, both in business and with social activities.
- I was very happy you did escalate and will be happy to reply now that I have spare time available for WP. My business legal department is pretty exited about it, like a kid in a candy store, can't wait to put its teeth in WP rules and regulations.
- Would you like me to repost your escalation? Uwappa (talk) 12:52, 5 January 2025 (UTC)
- I strongly advise that you read Misplaced Pages:No legal threats before you write another line. 𝕁𝕄𝔽 (talk) 15:27, 5 January 2025 (UTC)
- You escaped sanction because there were too many more egregious cases in the pipeline and it is a first offence. ANI does not adjudicate on content disputes, only on behaviour and compliance with fundamental principles. The evidence against you was really unarguable; I have seen quite a few cases and I know how they play out: if it had reached a conclusion, you would have been blocked until you acknowledged that you had gotten carried away in the heat of the moment, that you understand and accept WP:EPTALK, WP:EW, WP:CONSENSUS and WP:OWN, and that from now on you commit to respecting them. I strongly advise that you take the message anyway. --𝕁𝕄𝔽 (talk) 12:47, 5 January 2025 (UTC)
I am so sorry I was late to join this party. End of the year was a bit too hectic, did not leave much spare time for fun activities like WP.
user:Liz What would you like me to do now? Uwappa (talk) 04:54, 6 January 2025 (UTC)
- It was not clear on your talk page, and it's even less clear here since you did not repost your response to JMF's last line there. You do explicitly retract the apparent legal threat that was made? - The Bushranger One ping only 08:22, 6 January 2025 (UTC)
- I did not make a legal threat. Uwappa (talk) 08:33, 6 January 2025 (UTC)
- @Uwappa: your reference to your "business legal team" could certainly be construed as a veiled one, at the very least. You are being asked to clarify by either confirming or retracting this. -- DoubleGrazing (talk) 08:37, 6 January 2025 (UTC)
My business legal department is pretty exited about it, like a kid in a candy store, can't wait to put its teeth in WP rules and regulations.
is either a legal threat or indistinguishable from one. - The Bushranger One ping only 09:33, 6 January 2025 (UTC)- No it is not a legal threat. It is about "WP rules and regulations", not about law.
- To who would this be a threat?
- Which law?
- In which country?
- Uwappa (talk) 09:57, 6 January 2025 (UTC)
- Why would a legal department be involved? — Malcolmxl5 (talk) 12:02, 6 January 2025 (UTC)
- It certainly looks like a legal threat. M.Bitton (talk) 14:24, 6 January 2025 (UTC)
- @Uwappa. Why would a legal department be involved? — Malcolmxl5 (talk) 17:14, 6 January 2025 (UTC)
- Wow, I am glad you asked.
- to have a bit of fun, take a break from the normal, pretty serious work. It will be like kids in a candy store.
- It will be fun for me too. I can't wait to get going with this once the pandemonium calms down.
- The accusation "user:Uwappa: refusal to engage" is utterly wrong.
- Uwappa (talk) 22:47, 6 January 2025 (UTC)
- I'm not at all experienced in the legal world, but I don't think any professional legal team that you're paying money towards would ever be excited to save you from a website "like kids in a candy store". Tarlby 22:53, 6 January 2025 (UTC)
- Wow, I am glad you asked.
- Why would a legal department be excited about you being reported on Misplaced Pages unless you're planning to use them in some way? Tarlby 17:14, 6 January 2025 (UTC)
- I suspect, from context, that Uwappa was trying to suggest they would have assistance of a professional team in interrogating rules and regulations. But "I have the spend to wikilawyer this more than you can" isn't really all that much better than an outright legal threat. Between that and this edit what surprises me is that they're not blocked yet frankly. Simonm223 (talk) 17:23, 6 January 2025 (UTC)
- No it is not a legal threat. It is about "WP rules and regulations", not about law.
- I did not make a legal threat. Uwappa (talk) 08:33, 6 January 2025 (UTC)
- and just to throw some more fuel on the bushfire, you have just accused me twice more of vandalism.03:01, 6 January 2025 (UTC), 08:03, 6 January 2025 (UTC). --𝕁𝕄𝔽 (talk) 12:13, 6 January 2025 (UTC)
- I would say that for Uwappa to read this AN filing, reply to it (including something which could well be taken as a legal threat), and then immediately go back and revert the template for the fifth time (with an edit-summary of "Revert vandalism again", no less) shows a serious lack of self-awareness of the situation. Black Kite (talk) 12:46, 6 January 2025 (UTC)
- Putting aside the possible legal threat, if Uwappa's business legal department is involved it seems likely to be a cause of WP:PAID or at least a WP:COI which really should have been declared which doesn't seem to have happened. This also means Uwappa shouldn't be editing the article directly. Nil Einne (talk) 14:06, 6 January 2025 (UTC)
- It’s hard to see a paid or COI element to the behaviour at {{Body roundness index}}. — Malcolmxl5 (talk) 14:13, 6 January 2025 (UTC)
- It is fairly weird, but I can't see any reason a business legal department would have any interest unless the editor's activity relates to their business activity. Nil Einne (talk) 14:27, 6 January 2025 (UTC)
- I expect it’s just empty talk to get an upper hand in the dispute. — Malcolmxl5 (talk) 14:37, 6 January 2025 (UTC)
- Indeed. It is night where Uwappa is now, but my inclination is to see what reaction there is when they restart editing. If it is another revert or a lack of discussion, a block (or at least a prtial block) is indicated. Black Kite (talk) 15:05, 6 January 2025 (UTC)
- Black_Kite, how do you know where I am? Are you spying on me, disclosing personal information?
- Anybody in the room who can answer my 3 questions?
- Reverted vandalism 3rd time in 24 hours. Anybody curious about what the vandalism is?
- Anybody in the room that wonders why I had to do the repost? Isn't that odd in combination with "user:Uwappa: refusal to engage with WP:BRD process"? Did anybody read my reasons for being late to this party?
- Did anybody read User_talk:Uwappa#Bold,_revert,_discuss and User_talk:Uwappa#Notice_of_reference_to_ANI?
- Did anybody spot any incompleteness in the accusations?
- Anybody interested in my to answers to the accusations?
- Uwappa (talk) 16:59, 6 January 2025 (UTC)
- Black_Kite, how do you know where I am? Are you spying on me, disclosing personal information?
- Indeed. It is night where Uwappa is now, but my inclination is to see what reaction there is when they restart editing. If it is another revert or a lack of discussion, a block (or at least a prtial block) is indicated. Black Kite (talk) 15:05, 6 January 2025 (UTC)
- I expect it’s just empty talk to get an upper hand in the dispute. — Malcolmxl5 (talk) 14:37, 6 January 2025 (UTC)
- It is fairly weird, but I can't see any reason a business legal department would have any interest unless the editor's activity relates to their business activity. Nil Einne (talk) 14:27, 6 January 2025 (UTC)
- It’s hard to see a paid or COI element to the behaviour at {{Body roundness index}}. — Malcolmxl5 (talk) 14:13, 6 January 2025 (UTC)
- Putting aside the possible legal threat, if Uwappa's business legal department is involved it seems likely to be a cause of WP:PAID or at least a WP:COI which really should have been declared which doesn't seem to have happened. This also means Uwappa shouldn't be editing the article directly. Nil Einne (talk) 14:06, 6 January 2025 (UTC)
- JMF above said you were in Australia and I had no reason to disbelieve him. If you aren't, it's irrelevant really, I was just pointing out that you may not edit for a few hours. No-one here is required to answer your questions, but I will; the point was that you invoked something that could be a legal threat
My business legal department is pretty exited about it ... can't wait to put its teeth in WP rules and regulations.
You say that isn't a legal threat, well fine, but you haven't explained what it was. Meanwhile, you're still edit-warring on the template and claiming that other's edits are vandalism, which they clearly aren't, which is why you can no longer edit it. Have I missed anything? Black Kite (talk) 17:51, 6 January 2025 (UTC) - Again, that was either a legal threat or actions indistinguishable from a legal threat in an attempt to cause a chilling effect. When called on it you have continually Wikilawyered instead of straight-up saying "no, that was not a legal threat and I am not involving any legal actions in this". So to make it very clear: you need to clearly state that or be blocked per WP:NLT. - The Bushranger One ping only 20:31, 6 January 2025 (UTC)
- JMF above said you were in Australia and I had no reason to disbelieve him. If you aren't, it's irrelevant really, I was just pointing out that you may not edit for a few hours. No-one here is required to answer your questions, but I will; the point was that you invoked something that could be a legal threat
And just to add to the excitement, Uwappa has just repeated their allegation of vandalism against me and reverted to their preferred version of the template for the sixth time.16:26, 6 January 2025 (UTC) (Their edit note adds 3rd time in 24 hours: are they boasting of a 3RR vio? Zefr undid their fourth attempt, I undid their fifth attempt, but possibly they misread the sequence.) --𝕁𝕄𝔽 (talk) 17:41, 6 January 2025 (UTC)
- Yes, I noticed. I have pblocked them indefinitely from the template, and reverted that edit myself so that no-one else is required to violate 3RR. Black Kite (talk) 17:51, 6 January 2025 (UTC)
- Ha ha ha, this is beyond ridiculous.
.An editor must not perform more than three reverts on a single page whether involving the same or different material—within a 24-hour period.
— WP:Edit_warring#The_three-revert_rule - Suggestion: Add the following calculator to WP:3RR:
- Ha ha ha, this is beyond ridiculous.
3 is less than three. is equal to three. is more than three.
-
- From WP:EW;
Even without a 3RR violation, an administrator may still act if they believe a user's behavior constitutes edit warring
. Which this quite obviously does, especially as you've reverted twice whilst this report was ongoing. Frankly, you're quite fortunate it was only a partial block. Black Kite (talk) 22:41, 6 January 2025 (UTC)
- From WP:EW;
- To admins, please WP:ABAN Uwappa from further work on the calculator template for the body roundness index and waist-to-height ratio, and from further editing and talk page input on those articles. Uwappa has done admirable extensive work, but the simple calculator is finished and sufficient as it is. Uwappa has created voluminous WP:TLDR/WP:WALLOFTEXT talk page discussions for articles with under 50 watchers and few talk page discussants; few editors would read through those long posts, and few are engaged.
- In recent edits on templates, Uwappa reverts changes to the basic template as "vandalism". No, what we're saying is "leave it alone, take a rest, and come back in a few years when more clinical research is completed." Zefr (talk) 18:21, 6 January 2025 (UTC)
- This was closed, but...Uwappa's reply to their block was explictly a legal threat. Suggest revoking TPA. @Black Kite: - The Bushranger One ping only 06:15, 8 January 2025 (UTC)
Kansascitt1225 ban appeal
Appeal successful. There were some murmurings requesting a topic ban from Kansas, but nothing approaching consensus. Of course, Kansascitt1225 would be well-advised to be careful not to go back to the behaviors that led to a block in the first place. But in the meantime, welcome back. HouseBlaster (talk • he/they) 19:59, 15 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
I am posting the following appeal on behalf of Kansascitt1225 (talk · contribs · deleted contribs · page moves · block user · logs · block log · arb · rfc · lta · SPI · cuwiki), who is considered banned by the community per WP:3X:
(keeping it short for WP:TLDR) Hi Misplaced Pages community, it has been over 1 year since I edited on Misplaced Pages without evading my block or breaking community rules. I would like to be given another chance to edit. I realized that my blocking was due to my behavior of creating multiple accounts and using them on the same page and creating issues during a disagreement. I was younger then and am now able to communicate more effectively with others. I intend to respect community rules and not be disruptive to the community. I was upset years ago when I mentioned Kansas City’s urban decay and it was reverted as false and I improperly reacted in a disruptive way that violated the community rules. The mistake I made which caused the disruptive behavior was that I genuinely thought people were reverting my edits due to the racist past of this county and keeping out blacks and having a dislike for the county. I also thought suburbs always had more single family housing and less jobs than cities. In this part of the United States a suburb means something different than what it means in other parts of the world and is more of a political term for other municipalities which caught me off guard and wasn’t what I grew up thinking a suburb was. Some of these suburbs have lower single family housing rates and higher population density and this specific county has more jobs than the “major city” (referenced in previous unblock request if interested). This doesn’t excuse my behavior but shows why I was confused and I should have properly addressed it in the talk pages instead of edit warring or creating accounts. After my initial blocking, I made edits trying to improve the project thinking that would help my case when it actually does the opposite because I was bypassing my block which got me community banned to due the automatic 3 strikes rule. I have not since bypassed my block. I’m interested in car related things as well as cities and populations of the United States and want to improve these articles using good strong references. Thanks for reading. Kansascitt1225 (talk) 04:46, 27 December 2024 (UTC)
References
- https://slate.com/business/2015/05/urban-density-nearly-half-of-america-s-biggest-cities-look-like-giant-suburbs.html.
{{cite web}}
: Missing or empty|title=
(help)
- (mildly involved) Support. I gave feedback on an earlier version of their ban appeal. This is five years since the initial block. Five years and many, many socks, and many, many arguments. But with no recent ban evasion and a commitment to communicate better, I think it's time to give a second chance. -- asilvering (talk) 21:42, 7 January 2025 (UTC)
- Support per asilvering and WP:SO. voorts (talk/contributions) 21:44, 7 January 2025 (UTC)
- Support. Five years is a long time. Willing to trust for a second chance.-- Deepfriedokra (talk) 21:49, 7 January 2025 (UTC)
- Ideally I'd want to see some indication that they don't intend to right great wrongs as the issue seems to be rather ideological in nature and I don't see that addressed in the appeal. I also don't love the failure to understand a lot of issues around their block/conduct and their inability to effectively communicate on their talk page and on their unblock request from November. Thebiguglyalien (talk) 00:00, 8 January 2025 (UTC)
- Would a topic ban from Kansas-related topics help? This was floated as a bare minimum two or so years ago. -- asilvering (talk) 00:32, 8 January 2025 (UTC)
- I'm not that concerned by the RGW issue. Their communication on this appeal has been clear, they responded to my feedback regarding their unblock request, and they've indicated they'll not edit war and seek consensus for their edits. voorts (talk/contributions) 00:46, 8 January 2025 (UTC)
- Is my maths just bad or is January 2019 not six years ago rather than five? In any event it's been a long time since they tried to evade. I'm leaning toward giving a second chance but I'd really like them to understand that walls of text are not a good way to communicate, that they need to post in paragraphs, and that Misplaced Pages is not a place for righting great wrongs. FOARP (talk) 16:27, 8 January 2025 (UTC)
Is my maths just bad or is January 2019 not six years ago rather than five?
ssssshhh. -- asilvering (talk) 18:02, 8 January 2025 (UTC)- Response from KC:
voorts (talk/contributions) 02:19, 15 January 2025 (UTC)Yes I can write in paragraphs and list different ideas in separate paragraphs instead of a giant run on sentence.
I wasn’t trying to right great wrongs but noticed the contrast of the definition of suburban on Misplaced Pages and these communities being described as suburban (meanwhile some of these suburbs verifiably having lower residential to job ratio than the city and also a higher overall population density with some suburbs gaining population during the day due to commuters coming into them). This is essentially why on my case page It says I feel as tho something had to be “fixed”. I thought my edits were being removed simply because people didn’t like this place or some of its past so I felt as tho I was simply being purposefully misled which caused me to not follow proper civility.
I just wanted to clarify that these places weren’t only residential and were major employment areas that they sometimes have a lower percentage of single family homes. This to me was always the opposite of what suburban meant, atleast what I learned during grade school and what it says on Misplaced Pages. That’s where the confusion came from. Kansascitt1225 (talk) 06:17, 13 January 2025 (UTC)
- Support Six years is a long time, and they have shown growth. I do not think what is actually happening here is righting great wrongs, instead they assumed bad faith and things went downhill from there. I think their concerns of
Jackson county being THE central county of the metropolitan area
(which Misplaced Pages deems urban)when you can see in the census reference here there are actually 6 central counties
(which Misplaced Pages deems suburban) is reasonable. I researched it, but found the concerns are inconsistent with urban area page which provides the definition thatAn urban area is a human settlement with a high population density and an infrastructure of built environment. This is the core of a metropolitan statistical area in the United States, if it contains a population of more than 50,000.
An urban area is the most urban area compared to its surroundings, even though its surroundings are quite dense. I hope this helps. Kenneth Kho (talk) 22:54, 12 January 2025 (UTC)- I add that their concerns that suburban designation misleads people seem to have merit. It is not the suburban designation that misleads people though, but the definition of suburban itself on the suburban article seems to be misleading. I know this is not a place to discuss content, but discuss conduct. But some insight into content can help resolve problems. Kenneth Kho (talk) 11:56, 13 January 2025 (UTC)
ftools is back!
I am proud to announce that I have become the new maintainer of Fastily's ftools
, which is live here. And yes, this includes the IP range calculator! JJPMaster (she/they) 23:12, 9 January 2025 (UTC)
- Like -Ad Orientem (talk) 23:15, 9 January 2025 (UTC)
- Note: DreamRimmer is now also a maintainer. JJPMaster (she/they) 15:47, 10 January 2025 (UTC)
- My congratulations/condolences. Buffs (talk) 15:49, 11 January 2025 (UTC)
- So, will ftools be renamed or not? Congratulations. Ahri Boy (talk) 02:32, 14 January 2025 (UTC)
Block appeal for User:Aman.kumar.goel
UNBLOCK DENIED AKG has withdrawn the request. In any case, I see too many misgivings even on the "support" side to consider an unblock at this time. asilvering (talk) 02:33, 11 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
I am bringing a somewhat unusual unblock request here for broader community input. Aman.kumar.goel has been blocked for more than a year for sockpuppetry (see Misplaced Pages:Sockpuppet investigations/Aman.kumar.goel/Archive). As you can see in the unblock request at User talk:Aman.kumar.goel#Unblock request, they have agreed to a one-account restriction as an unblock condition, and there is no CU-confirmed evidence of recent sockpuppetry. However, Ivanvector, who made that check, is skeptical and has declined to support an unblock. A topic ban from WP:ARBPIA and WP:ARBIPA were floated as additional possible conditions, but no agreement was reached, and Aman.kumar.goel has requested that their unblock request be considered by the wider community. Their statement is as follows:
- I was blocked for sockpuppetry. There was no doubt throughout the discussion over that. I have agreed to a one-account restriction. However, during the unblock request, a topic ban on me was proposed from Israel-Palestine (WP:ARBPIA) and also from Afghanistan, Pakistan and India (WP:ARBIPA). Though no proper evidence was provided to substantiate such proposals.
- While the proposal to topic ban me from WP:ARBPIA does not make any sense because I haven't even edited that area, I would nevertheless reject the proposed topic ban from WP:ARBIPA with explanation because in this area I have been significantly active.
- My edits on WP:ARBIPA were clearly net-positive, and they fixed the long-term problems that were otherwise overlooked for a long time. You can find the deletion of a number of non-notable pro-Hindutva articles, creation of SPIs of future LTAs, and multiple DYKs. That said, the idea to topic ban me achieves nothing good. Black Kite himself said "
The edits aren't the issue here, it's socking in the IPA area that is.
". However, for the offense of sockpuppetry, I have already agreed to one-account restriction and spent over 1 year blocked.
- Once unblocked, I would like to improve drafts such as Draft:Aeroin Spacetech and Draft:Omspace Rocket and Exploration. Looking forward to positive feedback. Aman Kumar Goel 00:51, 10 January 2025 (UTC)
asilvering (talk) 01:23, 10 January 2025 (UTC)
- Support unblock without TBANs and with single account restriction.-- Deepfriedokra (talk) 01:43, 10 January 2025 (UTC)
- Support as requested. The request is sincere. Having edited a fair amount of articles where I discovered this editor's edits, I found his edits thoroughly productive and that is absolutely uncommon in this area. Nxcrypto Message 01:44, 10 January 2025 (UTC)
- Comment "Support as requested" sounds like a canvassed vote, did you mean it in a different way? Black Kite (talk) 08:48, 10 January 2025 (UTC)
- You need to re-check. Here, AKG posted a "request" for "unblock". By "as requested" , I meant how AKG requested himself to be unblocked, that is without any topic bans. Also, see WP:AGF. Nxcrypto Message 11:05, 10 January 2025 (UTC)
- I did AGF, otherwise my sentence would not have included the second clause. I understand what you mean now but I did not from the original posting. Black Kite (talk) 15:25, 10 January 2025 (UTC)
- Comment "Support as requested" sounds like a canvassed vote, did you mean it in a different way? Black Kite (talk) 08:48, 10 January 2025 (UTC)
- Aman.kumar.goel's explanation for the relationship with Editorkamran is
we knew each other in real life, and we used the same internet and the same system sometime, and also helped each other at times with Misplaced Pages editing
, but Ivanvector says the CU data indicatessomeone who had been carefully using two or probably more accounts for quite some time and going to lengths to obscure the connection, but made a mistake just one time that exposed them
. I don't know who's right, but this is a CU block, so if Aman.kumar.goel stands by his answer, I'd be uncomfortable unblocking unless another CU has a different interpretation of what happened. Extraordinary Writ (talk) 01:55, 10 January 2025 (UTC)- @Extraordinary Writ, response from AKG copied over:
voorts (talk/contributions) 02:46, 10 January 2025 (UTC)Hope you will check my statement above where I explained, "
However, upon reading further following the block, I realised that what I did was a violation of WP:SOCK because the use of both these accounts was prohibited by the policy, especially WP:SHARE and WP:MEAT.
" That means the CU finding does not really challenge my admission because I don't deny using multiple accounts. The only thing I happened to clarify was that the two accounts belonged to two different persons before they were used by the same person, which is me. That's why, in my unblock request (for WP:AN), I have also cited the edits of Editorkamran account as part of my edits into this area. Aman Kumar Goel (Talk) 02:43, 10 January 2025 (UTC)- All I know about this case is what I can glean by reading the private case notes, which do indeed support what Ivanvector has said. But given that AKG has admitted (on their talk page) to using the Editorkamran account, that's all kind of moot. I'd still like to hear Ivan's latest opinion on this, and I've also pinged off-wiki another CU who is familiar with this case, but my personal feeling is that we should draw a line in the sand and accept the unblock request with the single account restriction, no ARBPIA/IPA/API/TLA restriction, and an understanding that AKG's account at the bank of AGF is empty. RoySmith (talk) 03:05, 10 January 2025 (UTC)
- Oh, the other thing I wanted to mention is that on unblock requests, we're often left wondering what the user plans to work on if unblocked. In this case, they've specified two extant drafts they want to complete, both of which look like they have the potential to be useful articles. So that's a plus. RoySmith (talk) 03:22, 10 January 2025 (UTC)
- Am I the only one to feel that their earlier statements, even if they did mention WP:SHARE would not reasonably be understood to an admission that they did eventually user the Editorkamran account? Especially with all that comment about "we used the same internet and the same system sometime" etc? To my read the earlier statement gives the impression that they each account was only ever used by one person even if they did communicate and coordinate their editing at times. It's only most recently that I feel they've finally made it clear they it wasn't simply a matter of communication and coordination but rather that did use the other account directly. This also leads to the obvious question. How could any editor actually think it's okay for them to use some other editor's account just because it primarily belongs to another editor? Whether you consider it WP:SOCKing or whatever, you should not need any real experience to know it's unacceptable and definitely any editor with AKG's experience should know that. Note that I'm not suggesting that an editor who did what AKG did can never be unblocked, definitely they can be. But IMO there are good reasons to call into question whether the editor is ready for an unblock when they seem to have been so dishonest in their unblock request. In other words, if said something like 'yes I did X, I knew it was wrong and should not have done it, I promise not to do it again' rather than what they actually said, I'd be much more inclined to consider an unblock. Nil Einne (talk) 10:14, 10 January 2025 (UTC)
- All I know about this case is what I can glean by reading the private case notes, which do indeed support what Ivanvector has said. But given that AKG has admitted (on their talk page) to using the Editorkamran account, that's all kind of moot. I'd still like to hear Ivan's latest opinion on this, and I've also pinged off-wiki another CU who is familiar with this case, but my personal feeling is that we should draw a line in the sand and accept the unblock request with the single account restriction, no ARBPIA/IPA/API/TLA restriction, and an understanding that AKG's account at the bank of AGF is empty. RoySmith (talk) 03:05, 10 January 2025 (UTC)
- For what it's worth: I'm the other CU mentioned by Roy. I had run the initial checks and written some contemporaneous notes. I agree with Ivanvector's assessment at the talk page appeal; there was a concerted, long-term effort to obfuscate the connection between these accounts, which doesn't really fit with the assertion that they only realised they were doing something wrong after the fact. Whether a second individual also had access to either account at times can't really be retroactively assessed with any certainty, but it also seems immaterial to the finding of socking. --Blablubbs (talk) 17:39, 10 January 2025 (UTC)
- @Extraordinary Writ, response from AKG copied over:
- Support with 1 account restriction. A prolific editor with no recurring issues. Understands where he was wrong. Capitals00 (talk) 03:04, 10 January 2025 (UTC)
- Support: I have edited in South Asian-related topics and have run across some edits made by User:Aman.kumar.goel. Of these, I have seen several constructive edits made by him that have overall improved Misplaced Pages. Additionally, being blocked for one year is enough of a penance, which I'm sure has given him time to reflect. In view of this, I support his request in good faith. I hope this helps. With regards, Anupam 03:49, 10 January 2025 (UTC)
- Support with one account restriction and no topic restriction. We need competent editors working in the India topic area, as long as they follow policies and guidelines. The editor should be aware that Misplaced Pages:One last chance applies here. Cullen328 (talk) 05:17, 10 January 2025 (UTC)
- Oppose. I warned AKG in October 2021 for tag-team editing with Srijanx22, after many instances of one showing up to a content dispute the other was in to back them up. AKG didn't understand then what the issue was. He didn't understand it when he was blocked for socking with Editorkamran. He doesn't seem to understand it now. The semantics of sockpuppetry vs. "just" meatpuppetry are uncompelling. We indeed need more competent editors in the India topic area. We are not going to get closer to that by letting in someone who has shown willingness to serially manipulate interactions in that topic area, who managed to evade detection for years, who continued doing so after a first warning, and whose explanation is, apparently, unpersuasive to CUs who have reviewed the evidence. -- Tamzin (they|xe|🤷) 06:51, 10 January 2025 (UTC)
- It has been sufficiently confirmed throughout these years that the false allegation of tag teaming was indeed false. Do you see me in any of the events that have been mentioned so far in this unblock request? You don't. It is disappointing to see you bringing up your misleading observation you made when you weren't even an admin. You did not even ping me. Oh, and don't ask me how I got here because I watch this noticeboard and have edited it before.Srijanx22 (talk) 07:52, 10 January 2025 (UTC)
- I'm glad that you heeded my warning and stopped tag-teaming with AKG. AKG, however, continued to manipulate consensus in the topic area, which is what he got indeffed for. I didn't ping you because I'm not making any comment on your fitness as an editor; I just wanted to be clear that that 2021 report was separate from the Editorkamran case. -- Tamzin (they|xe|🤷) 08:13, 10 January 2025 (UTC)
- To quote what I had said then, "I am comfortable with ignoring your 'warning' since it lacks policy backing." I said that because no tag teaming on my part ever happened in the first place and the time has proven me correct. I would reiterate that you are supposed to ping the editor whose behavior is being discussed. In this case, you had to. Srijanx22 (talk) 09:10, 10 January 2025 (UTC)
- Actually, the SPI makes it clear that there were multiple examples of you reverting to the same version as AKG in rapid succession, whether you were co-ordinating off-wiki with AKG or not. As well as those, I could add 2020–2021 China–India skirmishes on 1st December 2020 and 21st February 2021 and Violence against Christians in India on 19 April 2020. So please give it a rest with the denials and instead ensure that it doesn't happen in the future if AKG is unblocked. Black Kite (talk) 11:00, 10 January 2025 (UTC)
- That's totally superficial. I have also edited both of these popular articles and so have many others I can count on my fingers. Capitals00 (talk) 16:10, 10 January 2025 (UTC)
- Yes, but that's not the point; have you reverted to a version also reverted to by AKG within < 24h on multiple occasions? I suspect not. Black Kite (talk) 18:59, 10 January 2025 (UTC)
- That's totally superficial. I have also edited both of these popular articles and so have many others I can count on my fingers. Capitals00 (talk) 16:10, 10 January 2025 (UTC)
- Actually, the SPI makes it clear that there were multiple examples of you reverting to the same version as AKG in rapid succession, whether you were co-ordinating off-wiki with AKG or not. As well as those, I could add 2020–2021 China–India skirmishes on 1st December 2020 and 21st February 2021 and Violence against Christians in India on 19 April 2020. So please give it a rest with the denials and instead ensure that it doesn't happen in the future if AKG is unblocked. Black Kite (talk) 11:00, 10 January 2025 (UTC)
- To quote what I had said then, "I am comfortable with ignoring your 'warning' since it lacks policy backing." I said that because no tag teaming on my part ever happened in the first place and the time has proven me correct. I would reiterate that you are supposed to ping the editor whose behavior is being discussed. In this case, you had to. Srijanx22 (talk) 09:10, 10 January 2025 (UTC)
- I'm glad that you heeded my warning and stopped tag-teaming with AKG. AKG, however, continued to manipulate consensus in the topic area, which is what he got indeffed for. I didn't ping you because I'm not making any comment on your fitness as an editor; I just wanted to be clear that that 2021 report was separate from the Editorkamran case. -- Tamzin (they|xe|🤷) 08:13, 10 January 2025 (UTC)
- It has been sufficiently confirmed throughout these years that the false allegation of tag teaming was indeed false. Do you see me in any of the events that have been mentioned so far in this unblock request? You don't. It is disappointing to see you bringing up your misleading observation you made when you weren't even an admin. You did not even ping me. Oh, and don't ask me how I got here because I watch this noticeboard and have edited it before.Srijanx22 (talk) 07:52, 10 January 2025 (UTC)
- Support per NxCrypto and RoySmith. I don't see any issue with unblocking right away. The presence of this editor is a net-benefit for this area. Koshuri Sultan (talk) 07:14, 10 January 2025 (UTC)
- Comment If unblocked, I would like to see AKG stay away from arbitration enforcement. There were a number of times - I count at least nine times between 2020 and 2023 - that they opened cases here trying to get editors on the "opposing" side blocked, and I don't think continuing this is a good idea. I also note that they were very active at SPI cases involving other editors in ARBIPA, which is another sign of BATTLEGROUND behaviour. Black Kite (talk) 08:46, 10 January 2025 (UTC)
- That, and the refusal to accept TBANs, gives me bad vibes.
- I also don't think that agreeing to use only one account is much of a concession, that's kind of a given, but I guess it's at least better than not agreeing to it. -- DoubleGrazing (talk) 08:56, 10 January 2025 (UTC)
- Yes, this is also my concern. I would have thought that we would expect an editor banned for socking in a CTOP to at least demonstrate their ability to collaborate well outside that CTOP before being allowed to edit it. I can understand the Support !votes above from other editors who generally edit from the same POV as AKG, but I'm still not thinking this is a brilliant idea. Black Kite (talk) 11:15, 10 January 2025 (UTC)
- What is that "same POV as AKG"? It is certainly not their fault that you are assuming bad faith. Capitals00 (talk) 16:12, 10 January 2025 (UTC)
- I don't need to AGF when the evidence is quite plain, as with the editor I mentioned above where I pointed out their tag-teaming issues. Black Kite (talk) 19:02, 10 January 2025 (UTC)
- What is that "same POV as AKG"? It is certainly not their fault that you are assuming bad faith. Capitals00 (talk) 16:12, 10 January 2025 (UTC)
- Yes, this is also my concern. I would have thought that we would expect an editor banned for socking in a CTOP to at least demonstrate their ability to collaborate well outside that CTOP before being allowed to edit it. I can understand the Support !votes above from other editors who generally edit from the same POV as AKG, but I'm still not thinking this is a brilliant idea. Black Kite (talk) 11:15, 10 January 2025 (UTC)
- Oppose. This user edits via proxy with IPBE, and the breadth and depth of the deception shown at that SPI is considerable. Now they're back with a semi-plausible explanation, and I don't buy it. And the one-account restriction is more challenging to police with a proxy/IPBE setup.—S Marshall T/C 09:27, 10 January 2025 (UTC)
- If he has agreed to one account restriction and this socking episode makes him ineligible for any future IPBE right, so what's wrong in allowing him back in since he has already served a year of block? Unless you are suggesting we completely ban those who have engaged in sock puppetry altogether, which is unrealistic. ArvindPalaskar (talk) 11:08, 10 January 2025 (UTC)
- What's wrong in allowing him back is everything Ivanvector says in that SPI. Please read it carefully and then re-read AKG's unblock request with a critical eye.—S Marshall T/C 12:38, 10 January 2025 (UTC)
- Oppose. I would support unblocking with an ARBIPA topic ban (which could be appealed later when AKG has proved they can edit well outside that area). But since AKG will not accept that TBAN I can only Oppose at the moment. Black Kite (talk) 11:17, 10 January 2025 (UTC)
- Support - The request is convincing and to-the-point. Those opposing are seemingly forgetting that it has been more than a year since this editor has been blocked. Azuredivay (talk) 12:33, 10 January 2025 (UTC)
- Support per above without any topic ban. It is totally unreasonable to seek punishment over the same offense even after WP:SO has been sufficiently met. Lorstaking (talk) 12:59, 10 January 2025 (UTC)
- It is not at all unusual for editors seeking an unblock to be required to accept a topic ban as a precondition to that unblock. Here are two are recent examples from this noticeboard. Caeciliusinhorto-public (talk) 15:04, 10 January 2025 (UTC)
- Whilst I don't support the topic ban, it would not be done as punishment, but as a measure reducing the likelihood of further disruption. -- Deepfriedokra (talk) 16:07, 10 January 2025 (UTC)
- Caeciliusinhorto-public not good to compare community banned editors with this case. Capitals00 (talk) 16:13, 10 January 2025 (UTC)
- It is not at all unusual for editors seeking an unblock to be required to accept a topic ban as a precondition to that unblock. Here are two are recent examples from this noticeboard. Caeciliusinhorto-public (talk) 15:04, 10 January 2025 (UTC)
- Support per Ivanvector: i.e. dependent on a topic ban from WP:ARBIPA and WP:ARBPIA and a single-account restriction. This will deal with the meat of the issue, while WP:ROPE should take care of the crust. SerialNumber54129 13:09, 10 January 2025 (UTC)
- Oppose I find myself agreeing with Black Kite - if they are willing to come back with a topic ban that'd be one thing. Without it I'm concerned we'll just end up back at AN/I, SPI or AE again. Simonm223 (talk) 13:42, 10 January 2025 (UTC)
- I will tentatively change my position to support provided it includes the topic ban. Simonm223 (talk) 18:09, 10 January 2025 (UTC)
- Oppose While I appreciate that brevity is required in unblock requests and people have different ways of writing stuff, as I noted above I feel the original unblock request was at a minimum intentionally evasive if not even misleading on whether Aman.kumar.goel had used the Editorkamran account directly. While they've now made it clear that they did so, the fact this only happened after editor questioned their story compared to the CU view makes me question whether it's because they didn't realise they were unclear or instead because they realised their evasiveness wasn't working. If they were evasive in their recent unblock request, this makes it very hard to trust Aman.kumar.goel. Further, even if Akg wasn't being evasive, it's very unclear why an editor with their experience didn't realise what they were doing was wrong until recently. I was originally willing to accept with a topic ban but frankly I'm now not even sure that's enough, but it's moot anyway. If this fails, I'd suggest on their next appeal Aman.kumar.goel ensures what they're telling us is clear from the get go. Nil Einne (talk) 15:42, 10 January 2025 (UTC)
- Support without topic ban. Sockpuppetry was the sole concern for the indefinite block. There is no evidence of any disruptive edits, as such the idea of topic ban makes zero sense. Abhishek0831996 (talk) 15:47, 10 January 2025 (UTC)
- Oppose per Black Kite. Any unblock that doesn't involve a restriction on AKG's original area of disruption will simply allow for further disruption. The Kip 16:13, 10 January 2025 (UTC)
- Not at all. Very recently, several editors editing this subject and socked were unblocked recently without any topic bans, including one more editor who was banned per 3x. Nxcrypto Message 16:23, 10 January 2025 (UTC)
- Oppose per Nil Einne. Being "intentionally evasive if not even misleading" during this unblock request and previously makes it very hard for me to trust this user. I'm glad they owned up to their outright sockpuppetry with Editorkamran and had they done so from the beginning of the request, I'd have considered supporting the request, provided they accepted the topic ban(s) suggested (so as to increase the odds of their future success). --Yamla (talk) 16:25, 10 January 2025 (UTC)
- Oppose unless an ARBIPA TBAN is applied. AKG's edits have not always been a positive: their approach to contentious matters has often been needlessly aggressive, and they haven't always been able to engage constructively with users and sources they disagree with. In that context sockpuppetry is more than "just" sockpuppetry. Some examples: , , , , , , and (These are discussions, not diffs, but I believe the context is needed to demonstrate the pattern I see). Vanamonde93 (talk) 16:55, 10 January 2025 (UTC)
I would tentatively support with the TBAN they have now agreed to.I have no opinion on whether a PIA ban is needed: if they have edited in that area I haven't seen it. I was considering suggesting a ban from bring others to AE/AN/ANI, but perhaps some rope is appropriate there. In any case they should be aware that they are on thin ice. I would also note that under no circumstances should they be given IPBE in the foreseeable future. Vanamonde93 (talk) 18:02, 10 January 2025 (UTC) I'm sorry to vacillate like this, but based on comments by Ivanvector and Girth Summit I simply cannot support (NB: while I am a CU, I am obviously not acting as a CU in this case). Despite our past disagreements I had been willing to give AKG another chance, but that was based on the assumption that they were being fully forthcoming, and based on the comments of CUs familiar with this situation, it doesn't appear that they have come clean. Put me down as a neutral, I suppose, though I remain opposed absent a TBAN. Vanamonde93 (talk) 22:49, 10 January 2025 (UTC)
- Oppose: Per Vanamonde, Tamzin, and Black Kite. It's telling that they won't accept a TBAN from my point of view. They were disruptive prior to their block and, as much as I want to assume good faith, I feel strongly that their refusal signals their intent to immediate jump into said area. There's also the concern that they may end up chasing other editors away from the site if they continue their aggressive behaviour and approach, which frankly I expect based on the lengths they went to in the past and the TBAN issue. I think this user was a net negative, chased people away from those areas, and made it more difficult for others to get involved with. Unblocking this user would end up leading to editor time wasted and would be a further net negative. Hey man im josh (talk) 17:13, 10 January 2025 (UTC)
- Noting that I still oppose the unblock, even though they accepted the condition about a TBAN. I agree with Girth Summit that this seems to just be someone saying whatever they think will convince people to unblock them. I also firmly believe that allowing them back onto the project will be a net negative. Hey man im josh (talk) 20:12, 10 January 2025 (UTC)
- Comment Aman.kumar.goel has requested this comment to be posted here from their talkpage:
After seeing a number of editors, some of whom I respect, are supporting my unblock but only with a topic ban from WP:ARBIPA, I would like to accept the topic ban from the said area. Ping Yamla, The Kip, Black Kite, Caeciliusinhorto-public, Simonm223 and Vanamonde93. Thanks Aman Kumar Goel 17:08, 10 January 2025 (UTC)
- Ratnahastin (talk) 17:46, 10 January 2025 (UTC)
- Would they also consent to the WP:ARBPIA topic ban? Because my understanding is that the ask was for both. Simonm223 (talk) 17:47, 10 January 2025 (UTC)
- I don't believe the PIA issue is a problem, only the IPA one. Black Kite (talk) 18:57, 10 January 2025 (UTC)
- Oppose an unblock based on this request. When I'm looking at an unblock request, I try to get a sense of whether someone is actually coming clean and saying 'I did this thing, I recognise that was out of order and I undertake that I won't do it again', or something along those lines. In this case, I don't see that. In their unblock request of 10 December 2024 (just a month ago), AKG seems still to be saying that they were not using multiple accounts - their argument seems to be that they accept there was a violation of WP:MEAT and WP:SHARE, but the two accounts were used by two different people from the same device. They have since swung round to acknowledging that they were in fact using the Editorkamram account, but are saying that they thought that was OK since the account really belonged to somebody else and they only used it from time to time. I'm afraid I simply don't believe that story, and I don't know what to think about their shifting narratives - I get the sense of someone saying whatever they think will convince people to unblock them, changing their story when it becomes apparent that it's not working, and failing to actually come clean about what they did and why they did it. If I don't trust someone in what they are saying in their unblock appeal, I don't trust them to abide by a one-account restriction - so, yeah, I don't think we can accept this request. Do some self-reflection, come back in six months with a frank and believable unblock request. Girth Summit (blether) 18:35, 10 January 2025 (UTC)
- Support. Seeing that AKG has agreed to the proposed IPA topic ban, the unblocking would be fine now. See no other issues. ArvindPalaskar (talk) 19:00, 10 January 2025 (UTC)
- Support based on the comments from RoySmith and agree with their point that the AGF tank is gone for A.K.G. Any issues beyond a minor oops with their editing should be an immediate indef. No warnings, no "one last chance". That bridge was crossed, burned, torn down and barriers put up to block it from being rebuilt. Ravensfire (talk) 19:24, 10 January 2025 (UTC)
- I hope A.K.G recognizes that is a last chance for them, and returning quickly to a contentious topic could be challenging for them to stay cool, engage in discussions but not disruption and that there will be enhanced scrutiny on their edits and willingness to take concerns to an admin board. They can't edit as they did before. Ravensfire (talk) 19:34, 10 January 2025 (UTC)
- Oppose - I gave my reasons on the talk page; I don't trust this user. Ivanvector (/Edits) 20:20, 10 January 2025 (UTC)
- Also I should point out that I was not involved whatsoever in the checks that led to this block; my comments on the talk page refer to emails I remember reading a year earlier on the private checkuser mailing list, which does not archive. I did check in relation to their unblock request recently and in my opinion that check was inconclusive; I elaborated on their user talk at the time. The result gives me pause because they had been using multiple accounts and evading checkuser for quite a long time before being blocked, while editing in one of our longest-designated contentious topics, one that's known to be very badly impacted by sockpuppetry and state-sanctioned disinformation campaigns. I suggested a topic ban from India-Pakistan for reasons that I think are already obvious from previous comments in this thread, and from Israel-Palestine because of something I thought I read on their talk page about a dispute in that topic, but I can't find that now and so I have to say I was probably out of line to have suggested it. But on the whole, I do not support unblocking, even with the proposed restriction. Ivanvector (/Edits) 20:43, 10 January 2025 (UTC)
- Very, very weak support on unblocking here with a one-account and indefinite IPA topic ban restriction. I found my engagement with the editor at their talk page today to be somewhere between obstructionist and disingenuous — and from reading the comments above, others have got similar vibes from different comments earlier in this process regarding the sockpuppetry and willingness to accept a topic ban condition. As Ravensfire notes above, the assume good faith tank is just about empty here — which means any non-trivial lapse or return to suboptimal behaviours is going to end up with a pretty swift reblock. I am very sympathetic to the number of very experienced editors above saying that this editor is a time sink and a net negative, and while I don't necessarily disagree based on what I've seen at their talk page and the evidence presented here, I think it's worth trying here one more time — armed with account and topic ban restrictions, and a pretty clear sentiment from a number of admins commenting (both on the support and oppose sides) that any issues upon resuming editing will be handled swiftly. Daniel (talk) 22:31, 10 January 2025 (UTC)
- Support, but only with IPA topic ban, 1-account restriction, no VPN use, and no IPBE. That should allow us to be able to detect recidivism and limit potential damage. — rsjaffe 🗣️ 22:55, 10 January 2025 (UTC)
- Oppose per Black Kite, Tamzin, S Marshall, Girth Summit, and Ivanvector. Andre🚐 23:04, 10 January 2025 (UTC)
- Oppose, agreeing with a number of editors above. I don't know if the two drafts, for Indian companies, would fall under WP:ARBIPA. Unfortunately, the editor does not seem trustworthy. Miniapolis 23:36, 10 January 2025 (UTC)
- Support - At the end of the day, the standard offer has been followed by this user for a long time. Don't see anything wrong with providing one more chance. Dympies (talk) 23:42, 10 January 2025 (UTC)
- Oppose per comments of Blablubbs, Tamzin, etc. If they are unblocked, they should be under an India--Pakistan CTOP topic ban. --JBL (talk) 00:07, 11 January 2025 (UTC)
- Oppose. The CheckUser evidence of overt sock puppetry (not meat puppetry) is pretty strong, and the repeated denials, which seem to get walked back over time, make this user seem untrustworthy. NinjaRobotPirate (talk) 00:28, 11 January 2025 (UTC)
- Support - Noting the opposes above, AKG has nevertheless agreed with a topic ban inline with many of the opposes. It shows he is willing to minimize any possible concerns and that is a good sign. Shankargb (talk) 00:51, 11 January 2025 (UTC)
- Oppose calling socking the sole issue is a red herring when there was disruption in addition, but the socking alone merited the block so they didn't need to be blocked for both. I think accepting the t-ban is more telling us what he thinks we want to hear, vs. awareness of why AKG shouldn't edit there. I do not think an unblock would be productive. Star Mississippi 01:36, 11 January 2025 (UTC)
Import request
A list without citations or an indication that it meets WP:NLIST is not going to be imported here. voorts (talk/contributions) 18:00, 12 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
Can you import, List of characters in brawl stars from simple Misplaced Pages. I created the page there. — Cactus🌵 07:19, 10 January 2025 (UTC)
- I suppose you mean this page, which you didn't create at all though, and which is completely unsuitable for enwiki as it stands, being unsourced and lacking all indication of notability. Fram (talk) 09:09, 10 January 2025 (UTC)
- Well, they did create the page. JJPMaster (she/they) 15:18, 10 January 2025 (UTC)
- Fram, oh, okay — Cactus🌵 09:16, 11 January 2025 (UTC)
Arbitration motion regarding coordinating arbitrators
The Arbitration Committee has resolved by motion that:
The Arbitration Committee's procedures are amended by adding the following section:
- Coordinating arbitrators
The Arbitration Committee shall, from time to time, designate one or more arbitrators to serve as the Committee's coordinating arbitrators.
Coordinating arbitrators shall be responsible for assisting the Committee in the routine administration and organization of its mailing list and non-public work in a similar manner as the existing arbitration clerks assist in the administration of the Committee's on-wiki work.
The specific responsibilities of coordinating arbitrators shall include:
- Acknowledging the receipt of correspondence and assigning tracking identifiers to pending requests and other matters;
- Tracking the status of pending matters and providing regular updates and reminders on the status of the Committee's off-wiki work to arbitrators;
- Reminding members of the Committee to vote or otherwise take action in pending matters;
- Organizing related correspondence into case files; and
- Performing similar routine administrative and clerical functions.
A coordinating arbitrator may, but is not required to, state an intention to abstain on some or all matters before the Committee without being listed as an "inactive" arbitrator.
For the Arbitration Committee, SilverLocust 💬 23:48, 10 January 2025 (UTC)
- Discuss this at: Misplaced Pages talk:Arbitration Committee/Noticeboard § Arbitration motion regarding coordinating arbitrators
Backlog
Misplaced Pages:Requests for page protection/Increase Moxy🍁 19:38, 11 January 2025 (UTC)
Requesting review of SPI
No need to have brought this here.--Bbb23 (talk) 23:15, 11 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
I recently filed an SPI for Xselant; any admin/checkuser eyes would be appreciated. Thank you! XtraJovial (talk • contribs) 22:43, 11 January 2025 (UTC)
- CUs and SPI clerks are very aware of which SPIs need attention. Please trust that we will get to the one you posted. Asking for input at AN isn't very helpful unless your SPI is much more urgent than usual. Vanamonde93 (talk) 23:09, 11 January 2025 (UTC)
IPBE for AWB account
DONE Done. - The Bushranger One ping only 05:02, 12 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
Hi. I'm performing a task using CanonNiAWB (talk · contribs), but the edits aren't editing since I'm using a VPN. I already have IP block exemptions on this account, so could it also be granted to that? Thanks. ''']''' (talk • contribs) 02:32, 12 January 2025 (UTC)
- Done. Extraordinary Writ (talk) 02:40, 12 January 2025 (UTC)
- Thanks. ''']''' (talk • contribs) 02:46, 12 January 2025 (UTC)
Content removal, POV pushing, edit warring
Please use the existing thread rather than creating new ones. Star Mississippi 15:14, 12 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
@Taha Danesh removing content and POV pushing here and is currently edit warring Montblamc1 (talk) 10:52, 12 January 2025 (UTC)
- This looks like the same complaint as Misplaced Pages:Administrators' noticeboard/Incidents#Report on Disputed Edits and Insults. Let's centralise discussion there. I note that Talk:Mohammed Ridha al-Sistani is also empty. Phil Bridger (talk) 11:19, 12 January 2025 (UTC)
Tulsi (unblock request)
User unblocked. arcticocean ■ 12:25, 16 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
- Tulsi (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- Blocked (indef) on 3 April 2024 (9 months ago) by Rosguill during an AN thread (archived thread) for undisclosed paid editing
- Subsequent unblock request was also considered at AN before being declined (archived thread)
Tulsi has now submitted an unblock request which I am copying:
Dear Sysops,
I sincerely apologize for my past actions, which were problematic and deceptive. I fully understand the concerns raised, and I deeply regret my involvement. On April 3, 2024, my account was blocked by Rosguill in relation to undisclosed paid editing associated with the Misplaced Pages:Administrators' noticeboard/Archive361 § DIVINE and Tulsi: COI/UPE/quid-pro-quo editing, association with threats and harassment. However, I want to clarify that my involvement in these matters was minimal, with only minor interactions in the past. I have never written articles for payment, and I do not support paid editing.
The issues in question occurred in 2020 or 2021, prior to the block. At that time, I admitted my conflict of interest (COI) and disclosed it on the relevant article talk pages. Following discussions, my global and local rights were removed, but the block was not enforced until two years later. Many of the articles in question were deleted, so I did not find it necessary to disclose anything further. Moving forward, I have no intention of creating or editing COI-related articles. However, if I am ever in a situation where I am required to contribute to such an article, I will ensure full disclosure on the article talk page and submit it for review, as I did with the article Talk:Ghero.
While I respect Rosguill’s decision to impose a block after the two-year gap, I understand that a block serves to prevent disruption rather than punish. I have learned valuable lessons from this experience, and my contributions over the past two years reflect this growth. In this time, I have created over 80 articles, all without any undisclosed paid editing or COI involvement. Additionally, I have contributed to patrolling, as seen in the Twinkle and Draftify logs, and I have reported several violations on WP:UAA.
I acknowledge that I was not fully familiar with Misplaced Pages's policies in the past, but I have since taken the time to understand them better. I have been an active and committed user since October 2014, with significant contributions across various Wikimedia projects. I have also served as a sysop on Wikimedia Commons, Meta-Wiki, MediaWiki, and the Maithili and Nepali Wikipedias.
I am requesting an unblock because I am fully committed to abiding by all the established policies moving forward, and I am eager to contribute here in a constructive manner. Please kindly allow me a second chance.
Thank you for your consideration. I humbly request your reconsideration and the restoration of the editing privileges on my account on English Misplaced Pages.
Sincerely,
Having had discussions with the blocking admin, we would like to seek community comments on the unblock request.
Tulsi was blocked after UPE allegations that had been outstanding for around 2 years essentially caught up with them. They have now attested to having never edited for pay, which was the question they originally failed to answer twice (first thread, second thread), leading to the block. In the unblock request, they give a sincere undertaking not to engage in any more UPE.
They have created several dozen articles about Nepalese politicians but these seem to be innocuous. I have identified only a handful of articles where Tulsi could have edited for pay. Given the amount of other contributions Tulsi has made, it would be appropriate to give the benefit of the doubt. arcticocean ■ 15:14, 12 January 2025 (UTC)
- I cannot find the link for "A related meta-wiki discussion". killer bee 15:35, 12 January 2025 (UTC)
- I've deleted those words. I had decided not to include them in my post, but accidentally left them in. For interest, the discussion was this one: m:Requests for comment/Tulsi advanced permissions and UPE. arcticocean ■ 15:38, 12 January 2025 (UTC)
- Support per WP:SO. I will AGF that Tulsi will keep his promise not to engage in any COI editing going forward. voorts (talk/contributions) 16:07, 12 January 2025 (UTC)
- Question: We are all volunteers here, so the applicant's comment
if I am ever in a situation where I am required to contribute to such an article
(emphasis mine) is worrisome within the context of UPE/COI. Could they, or someone else for that matter, provide some clarification? JoJo Anthrax (talk) 19:57, 12 January 2025 (UTC)- I assume "required" is just poor phrasing and refers to circumstances similar to the example provided in the same sentence you quote. In any event, the second part of the sentence states
I will ensure full disclosure on the article talk page and submit it for review
(emphasis added). That promise is enough for me. voorts (talk/contributions) 21:00, 12 January 2025 (UTC)
- I assume "required" is just poor phrasing and refers to circumstances similar to the example provided in the same sentence you quote. In any event, the second part of the sentence states
- Support, we should generally give a second chance to users who have greatly and fundamentally changed in several months. Given that the user acknowledged the block and promised not to engage in undisclosed paid editing, not to mention that the user is trusted elsewhere, I see no reason to oppose. ToadetteEdit (talk) 20:48, 12 January 2025 (UTC)
- Support I believe in their ability to address any concern in the future, given that they served as a sysop on Wikimedia Commons, Meta-Wiki, MediaWiki, and the Maithili and Nepali Wikipedias. Kenneth Kho (talk) 21:44, 12 January 2025 (UTC)
- Support A second chance promises that Tulsi will not do highly undisclosed paid editing. I may partially support a topic ban on Nepalese politics against Tulsi. Ahri Boy (talk) 05:56, 13 January 2025 (UTC)
- Support Make the most of the second chance Buffs (talk) 23:05, 14 January 2025 (UTC)
- Support I had already been kind of watcxhing the discussion on their talk page over the last few days, and agree with an SO unblock. Beeblebrox 23:34, 14 January 2025 (UTC)
Abner Louima
Snow in the forecast. - The Bushranger One ping only 22:08, 13 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
I can't believe this article's AfD is still up and not closed as a WP:SNOW keep. The nominator has acknowledged his mistake out of ignorance. He was in middle school when the subject first became notable, and never heard of him. If the media, or God forbid, Social Media, discovers this nomination, it will do great harm to the reputation of the Misplaced Pages community as being collectively ignorant or much, much worse. I used to be an administrator, and would have closed this as keep. Please do something! Bearian (talk) 16:22, 13 January 2025 (UTC)
- Anybody can close an AfD as SNOW keep. That's the whole point of SNOW. voorts (talk/contributions) 16:25, 13 January 2025 (UTC)
- Snowed by me. — rsjaffe 🗣️ 16:35, 13 January 2025 (UTC)
- Thank you!!! Bearian (talk) 16:38, 13 January 2025 (UTC)
- Snowed by me. — rsjaffe 🗣️ 16:35, 13 January 2025 (UTC)
Request for Administrator Review of Repeatedly Declined Draft: Ario Nahavandi
Spam, spam, glorious spam. - The Bushranger One ping only 03:25, 15 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
Dear Administrators,
I am writing to request your assistance regarding my draft, Draft:Ario Nahavandi, which has been repeatedly declined over the past year despite my adherence to Misplaced Pages’s guidelines.
Over the course of several months, I have worked diligently to gather reliable, published, and independent sources, including magazine articles and other credible publications, that meet Misplaced Pages’s notability criteria. My most recent submission was declined in less than an hour—a timeframe that strongly suggests it was not even reviewed carefully or thoroughly.
This is particularly frustrating as I see numerous approved articles on Misplaced Pages that cite sources far less reliable or even completely broken. In contrast, my article contains verifiable references that adhere strictly to Misplaced Pages’s policies. This inconsistency feels unfair and raises concerns about bias in the review process.
I have followed all guidelines in good faith and cannot accept decisions that appear to be based on personal opinion rather than policy. It feels as though my article is being subjected to an unjust standard, especially when compared to articles that seem to bypass scrutiny. I genuinely wonder if this process is influenced by factors beyond content quality, as I have no means to “pay” for an article to be published, unlike some others.
I kindly request that an administrator reviews my draft with impartiality and provides clear, actionable feedback. Otherwise, I am truly exhausted by the repeated rejections and dismissals with no valid reasoning.
To provide context, here are some of the sources I included:
• https://www.nationaldiversityawards.co.uk/awards-2024/nominations/ario-nahavandi/
• Taurus Magazine (2024-11-19). "Ario Nahavandi". Taurus Magazine. 88: 7 – via www.magcloud.com
• 6x Magazine (2024-11-22). "Ario Nahavandi; The Persian Icon". 6X Magazine. 432: 6–7 – via www.magcloud.com
Thank you for your time and consideration xx
Lanak20 (talk) 23:47, 14 January 2025 (UTC)
- Administrators cannot override draft declines, and in fact the administrator toolset cannot be used to force content decisions. —Jéské Couriano v^_^v 23:51, 14 January 2025 (UTC)
- So who can I turn to for help? If administrators cannot assist in overriding the draft declines, to whom can I escalate this issue? I am deeply concerned that my article has been repeatedly declined without proper consideration of the sources I’ve provided. These sources are reliable, published, and fully comply with Misplaced Pages’s guidelines, yet they continue to be dismissed without even being properly reviewed.
- It’s becoming clear that the rejection process isn’t being carried out fairly. I can’t help but feel that my article is being judged based on factors other than content quality, especially when I see articles approved with far less solid references.
- I understand that the review process is based on policy, but when it seems clear that my draft isn’t being given the attention it deserves, I need to know where I can seek help to ensure fairness.
- I kindly ask for your guidance—if administrators cannot intervene, who can I turn to for proper support in getting this article reviewed fairly?
- Thank you for your time. Lanak20 (talk) 00:08, 15 January 2025 (UTC)
- WP:TEA. This is where you appeal problems with submissions of drafts. You should read the WP:NPEOPLE and WP:BLP carefully. Ahri Boy (talk) 00:20, 15 January 2025 (UTC)
- @Lanak20: I actually just went over your sources. They're all malformed at best and unusable at worst. What is your connexion to Nahavandi? —Jéské Couriano v^_^v 00:20, 15 January 2025 (UTC)
- I've blocked the OP as a spam-advertising-only account. I should add that it's pretty obvious they've used other accounts to promote this person, I believe most recently as of last October.--Bbb23 (talk) 00:25, 15 January 2025 (UTC)
Your Friendly Neighborhood Sociologist Edit Restriction Appeal
Unanimous consent after 36 hours to lift the restriction. Primefac (talk) 14:25, 16 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
A bit over a year ago, with near unanimous support, I appealed a TBAN from GENSEX - receiving in its place the following sanctions 1RR restriction in both the GENSEX and AMPOL topics; is limited to 0RR on articles for organizations/activists who are affiliated with anti-transgender activism or gender-critical feminism, broadly construed; and has a PBAN from Kellie-Jay Keen-Minshull.
Previous discussions are linked there. I am now requesting that my restrictions be dropped entirely because I have grown considerably as an editor, both since my initial TBAN when I'd just turned 19 and since the appeal.
I translated Transgender history in Brazil (having originally wrote it on eswiki during my TBAN) and made it my first GA. I uploaded multiple colorized photographs of transgender historical figures to commons I improved LGBTQ rights in New York and wrote articles for famous trans activists Cecilia Gentili and Carol Riddell. I also cleared up serious BLP violations at Aimee Knight and rewrote the article. I also helped expand Trans Kids Deserve Better and wrote Bayswater Support Group. I improved Rapid-onset gender dysphoria controversy and conversion therapy. I improved gender dysphoria in children. I rewrote and considerably expanded WPATH as well as Gender Identity Development Service. I expanded the article on the Cass Review. I wrote the article on the 1970 semi-governmental report Evaluation of Transsexual Surgery. I expanded the articles on Stephen B. Levine and Kenneth Zucker. I rewrote Detransition to follow WP:MEDRS and use systematic reviews instead of primary studies. Most proudly, I wrote Transgender health care misinformation and took it to GA - this is particularly relevant as a key part of the original TBAN discussion was whether my commitment to removing misinformation from Misplaced Pages was a case of either WP:RGW or following WP:NPOV and WP:FRINGE.
I believe the restrictions impair my ability to edit productively. I generally edit with 1RR regardless of sanctions. With 0RR, as Red-tailed hawk noted at my previous appeal "they can wind up restricting the sorts of partial reverts that are often a healthy part of the ordinary editing process." With 0RR, I am unable to engage in the BRD cycle properly and always second-guessing whether a partial edit to a recent edit counts as a revert or not. It also prevents me reverting drive-by SPA/IP povpushing. I don't plan to ever edit KJK's article again, but I believe that my record of neutral constructive editing shows the PBAN is no longer preventative or necessary. In the highly unlikely event I ever see a reason to edit it in future, I know my edits would be subject to heightened scrutiny which I'd welcome.
I appreciate your consideration. My best regards, Your Friendly Neighborhood Sociologist ⚧ Ⓐ (talk) 01:02, 15 January 2025 (UTC)
- Support. voorts (talk/contributions) 01:25, 15 January 2025 (UTC)
- Support. Based on YFNS's activity since the original tban, I don't see any reason to believe that restrictions are necessary going forward. Thebiguglyalien (talk) 06:34, 15 January 2025 (UTC)
- Support. Welcome back comrade. Ahri Boy (talk) 06:56, 15 January 2025 (UTC)
- Support based on their editing activity between TBAN and last year, as well as between the sanctions and now. Good work, and a great example of how this restorative process is supposed to work. May you inspire other misguided people to a path of restoration. TiggerJay (talk) 08:27, 15 January 2025 (UTC)
- Snow Support Kenneth Kho (talk) 14:15, 15 January 2025 (UTC)
- Strong support. To me YNFS comes across as a very responsible editor and I believe these restrictions are no longer warranted. HenrikHolen (talk) 16:09, 15 January 2025 (UTC)
- Support I remember the original ban happening due in large part to canvassing on twitter, the fact that any restrictions remained in place thereafter strikes me as a deep miscarriage of justice. Snokalok (talk) 23:26, 15 January 2025 (UTC)
Query Does your reference to BRD mean that you undertake to follow it in the future? Sweet6970 (talk) 14:17, 15 January 2025 (UTC)
- Enthusiastic support YFNS is a perfect model of an editor who is an asset to Misplaced Pages. Simonm223 (talk) 15:17, 15 January 2025 (UTC)
- Support A well worded appeal, worth giving another chance. — The Hand That Feeds You: 18:20, 15 January 2025 (UTC)
- Support This is a convincing and sincere appeal. Cullen328 (talk) 00:22, 16 January 2025 (UTC)
- Support, Welcome. ~🌀 Ampil 02:33, 16 January 2025 (UTC)
- Support as they have convincingly demonstrated change. TarnishedPath 02:53, 16 January 2025 (UTC)
- Support I supported and still support the original restrictions, and the later now appealed restrictions. I think YFNS's case has shown that an editor can come back from the brink successfully and am happy that happened. Nil Einne (talk) 04:00, 16 January 2025 (UTC)
Copyvio Problem
Hey all, I believe that these three diff should be redacted as copy vio's, thanks. There are several sentences which are directly lifted from the sources. Some one more experienced should likely have a look through the revision I restored as well. I didn't spot anything, but I may have missed something.
Kingsmasher678 (talk) 22:35, 15 January 2025 (UTC)
- To be clear, I don't think that @YatesTucker00090 is really at any fault here.
- Kingsmasher678 (talk) 22:37, 15 January 2025 (UTC)
- @Kingsmasher678 please see {{copyvio-revdel}} on how to tag copyvios for attention. Nthep (talk) 08:04, 16 January 2025 (UTC)
Lardlegwarmers block appeal
Essentially unanimous consensus to not unblock. RoySmith (talk) 15:53, 17 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
- Lardlegwarmers (talk · contribs · deleted contribs · logs · filter log · block user · block log)
I blocked Lardlegwarmers yesterday for one week for a violation of their community topic ban from COVID-19. This was about this edit, although I subsequently noticed this one as well. LLW has asked me to copy their appeal here. -- Tamzin (they|xe|🤷) 03:00, 16 January 2025 (UTC)
Statement from Lardlegwarmers
I have only been very active editing Misplaced Pages for about one month, even though my account is older. I was blocked for pushing a minority POV in the talk page for Covid-19 Lab Leak Theory, which I understand. For context, this issue wouldn't have even come up at ANI except that there was this very old account making borderline uncivil comments constantly, and I took them to ANI myself and it boomeranged. One thing that I learned from that experience is that Misplaced Pages's culture sort of revolves around social dynamics and politics, which can overshadow fairness and consistency in rule enforcement, and that I am probably not going to be the one to fix it. Anyways, in my defense, I didn't learn until later that my attempt to reason things out like grownups was not allowed; my edits were in good faith and I was really just attempting to talk it out with the other editors who did not agree with me. But I understand that the norm in this space is to walk away if there isn't any uptake of my ideas or take it to dispute resolution instead of continuing to try to convince people. The current ban is for making a comment on an AE thread, not a Covid-19 article. I was on the page for a totally unrelated reason and noticed that a user I recognized from the Covid thread was being discussed. My comment was mostly about user behavior and reflecting on the underlying dispute itself, not Covid-19. Also, on my user page I quoted Larry Sanger discussing his view on Misplaced Pages's approach to Covid-19 , which I'd assumed was permitted because it's my own user page and it's really a comment about the state of Misplaced Pages as a whole. The admin who blocked me, @Tamzin, blanked it from my user page. If the community won't let me keep that quote on my user page, then fine, we'll leave it removed, but I wish they would have just asked me to remove it and described why instead of editing my user page. A block for this stuff seems harsh. Thanks.
References
Statement from Tamzin
Excerpting my comment on their talkpage:-- Tamzin (they|xe|🤷) 03:00, 16 January 2025 (UTC)Usually we only warn someone on their first topic ban violation. However, in your case, the fact that both violations occurred within hours of the ban being imposed, and that they were belligerent rants treating Misplaced Pages as a battleground, made me judge that a short block would more clearly communicate just how far you are from what is considered acceptable conduct. Even if you didn't understand that the ban applied outside articles, you should have understood that the community found your editing about COVID disruptive, which should have been reason enough to not make those edits.
Discussion among uninvolved editors
- This is clearly a topic ban violation - and it came less than a day after it was imposed. Even if assuming in good faith that they didn't know it was a topic ban violation, their unblock request shows not only that they don't understand what they did wrong, but they attempt to justify it with statements such as
Anyways, in my defense, I didn't learn until later that my attempt to reason things out like grownups was not allowed
which is borderline a personal attack (veiled insult that others weren't being grownups);which can overshadow fairness and consistency in rule enforcement
which is confirming they still don't understand why they were topic banned nor why they were blocked for violating it; and quoting Larry Sanger's fringe theory promoting comments on their userpage after their topic ban. To summarize, I have no confidence that the user understands what they did wrong, and I would go so far as to say the user attempting to skirt the edges of their topic ban and supporting another user trying to promote fringe theories on Misplaced Pages merits an indefinite community ban. TLDR: Oppose unblock and ultimately would support indefinite ban due to the flagrant violation, lack of understanding, and no belief that after the 7 days is up they will not go straight back to trying to right what they percieve as a great wrong. I won't be the one to propose that, however. -bɜ:ʳkənhɪmez | me | talk to me! 03:10, 16 January 2025 (UTC) - I don't see how an unblock is possible when Lardlegwarmers clearly still doesn't understand what a broadly construed topic ban means. To be clear, there's no need to ask the "community" whether you can keep your topic ban violation. The only hope for you to be able to obey it is if you are able to decide yourself, especially after you've been told by an admin. While we do try to educate instead of just blocking, the "community" isn't here to help you understand the limits of your topic ban. Nil Einne (talk) 04:01, 16 January 2025 (UTC)
- Should clarify that despite what I said above, I'd weakly oppose extending the topic
banblock to indefinite at this time. While I'm not hopeful Lardlegwarmers is going to be able to obey it given what they've said, I think it's fine to give them rope after thebanblock expires and apply normal escalating blocks. Since we're already here, perhaps this will somehow help them understand that yes the community requires you to apply it broadly on anything to do with COVID-19 throughout Misplaced Pages. They should consider this very short rope though and notably the next time they feel they need to ask the community whether they're violating their topic ban when they are, it might be the last time. Nil Einne (talk) 20:38, 16 January 2025 (UTC)- Sorry mixed up ban and block above twice, now fixed. Nil Einne (talk) 01:45, 17 January 2025 (UTC)
- Should clarify that despite what I said above, I'd weakly oppose extending the topic
- Oppose unblock as the user looks to have no intention of following Misplaced Pages guidelines with their request. It is only a week and will give a change to think about how to change. Graeme Bartlett (talk) 04:13, 16 January 2025 (UTC)
- Oppose unblock. It truly takes some chutzpah to cite a Signpost piece authored by the admin who blocked you to support the proposition that you're being railroaded. Weak support for an indef because that's what Lardlegwarmers seems to be speedrunning. voorts (talk/contributions) 04:30, 16 January 2025 (UTC)
- Oppose unblock. The topic ban was on the topic of COVID-19, broadly construed, not the topic of COVID-19 directly in articlespace. And the topic ban was violated, not just within less than a day, but within three hours of it being imposed. On top of that the unblock request could be a case study for WP:NOTTHEM. I won't call for an indef yet, but when the block expires Lardlegwarmers should bear in mind that any further violations of the topic ban will be their last. - The Bushranger One ping only 10:10, 16 January 2025 (UTC)
- No unblock - Basically per Lardlegwarmers: they don't appear to understand why they've been blocked. An indefinite block seems very likely in this editor's future and we certainly should consider cutting out the middle-man and just skipping to it, but I'd like to give them at least some chance here to understand why they were blocked. FOARP (talk) 10:12, 16 January 2025 (UTC)
- Oppose unblock - While I usually support giving editors WP:ROPE to demonstrate improvement, this case warrants a longer wait. The user acknowledges pushing a minority POV and failing to disengage per WP:DISPUTE norms, but their justification suggests a lack of understanding or acceptance of policies like WP:NPOV, WP:CIVIL, and WP:NOTHERE. Their off-topic comment in an AE thread, despite knowing the sensitivity of such spaces, and the policy-violating content on their user page, further reflect ongoing disruption. I recommend they take time to reflect and gain a better grasp of Misplaced Pages's collaborative culture before requesting an unblock again. Footballnerd2007 • talk ⚽ 11:31, 16 January 2025 (UTC)
- Oppose unblock. I agree that absent change from this user an indefinite block is likely. For their benefit, if you're the subject of a topic ban, broadly construed, about COVID-19, you need to be editing in an entirely different topic area. Think of something that you're interested in--television shows, football, English gardens, science fiction books? Take a week and think on it. Mackensen (talk) 11:42, 16 January 2025 (UTC)
- Oppose unblock. What is there left to say? This conduct feels like appellant's purpose is use Misplaced Pages as a battleground and to soapbox their views rather than to build the encyclopedia-- to remake Misplaced Pages as they think it should be. My feeling is that a week won't be nearly enough. The railroad comment is appallingly full of not understanding that their conduct is not acceptable in a collaborative project. -- Deepfriedokra (talk) 12:28, 16 January 2025 (UTC)
- PS: What Tamzin said in her statement above. -- Deepfriedokra (talk) 12:33, 16 January 2025 (UTC)
- Whilst I don't believe user will be able to change their approach, I feel an indef would be premature for now. We should give them a chance to mend their ways. -- Deepfriedokra (talk) 12:44, 17 January 2025 (UTC)
- PS: What Tamzin said in her statement above. -- Deepfriedokra (talk) 12:33, 16 January 2025 (UTC)
- An account that exists only to push a particular POV across several articles is topic banned, violates that topic ban immediately, and posts a battlegroundy unblock request that thoroughly misses the point. Whoever closes this should be considering indef, not an unblock. — Rhododendrites \\ 13:57, 16 January 2025 (UTC)
- Indeed. -- Deepfriedokra (talk) 14:55, 16 January 2025 (UTC)
- Oppose unblock this specific response
Misplaced Pages's culture sort of revolves around social dynamics and politics, which can overshadow fairness and consistency in rule enforcement
is indicative of their viewpoints and why they're not ready to contribute. They continue,my attempt to reason things out like grownups was not allowed
. These demonstrate that they still do not get it, and rather project their self-perspective is that they are actually a victim of people who are abusing the rules against them. . I proffer that this is going to be a consistent problem until they acknowledge that they were violating policy. Zero indication that they know how to positively contribute, just perhaps a vague inference that they'll avoid getting in trouble -- because -- we'll I'm not entirely sure they've communicated what they will do differently, but rather simply say thata block for this stuff seems harsh.
TiggerJay (talk) 15:12, 16 January 2025 (UTC)- Notwithstanding the harsh situation I presented above, to be clear I oppose indef for now. A new user should have the opportunity to overcome early (while significant) setbacks, which is what TBANs are designed to encourage. I am encouraged by things like YFNS corrective behavior in a prior AN discussion, and can only be hopeful and AGF that might apply to LLW here. We need more passionate, subject matter experts, as contributors to this project, but they absolutely must contribute positively and following established PGs. TiggerJay (talk) 16:34, 16 January 2025 (UTC)
- Oppose unblock and support an indef. I am pretty confident in saying that this is where we will be heading after this block ends. RickinBaltimore (talk) 15:20, 16 January 2025 (UTC)
- Oppose unblock, clear violations of the topic ban. Don't oppose indef, but I'd like to at least give him the chance to figure out exactly what we expect going forward. --SarekOfVulcan (talk) 15:52, 16 January 2025 (UTC)
- Support block, oppose unblock, oppose indef - this is a topic-banned newbie's first violation, in the heat of the moment after the restriction was imposed. Tamzin's block was the appropriate response. The unblock request is wholly inadequate, but jumping straight to indef for this sort of violation is a pretty extreme overreach. If they go back to violating their sanction after this block expires, then let's talk community ban, but they should be given the opportunity to edit constructively while respecting the restriction. Ivanvector (/Edits) 16:07, 16 January 2025 (UTC)
- Oppose unblock, oppose indef...however... I am sympathetic to their point of view and their general "right" (we don't really have rights here on WP) to post their opinion on a subject, even one as contentious as COVID-19. I think the blanking of the user page is a step too far. We shouldn't be in the business of deleting negative opinions about Misplaced Pages; while the statement was in reference to COVID-19, it doesn't mention it within the claim and is more a critique of Misplaced Pages at large and mass media than its relation to COVID. I would let the statement on their user page stand/restore it. Larry Sanger's statement is not a fringe theory, it is a reasonable opinion. There were loads of statements/claims about COVID/its origin/mandates/treatment/vaccines that, despite their widespread implementations and presentation as "the science", later turned out to be misleading or untested conjecture (examples: no studies on masking effectiveness with a large population vs the coronavirus, 6 foot spacing, lying to the American public about wearing masks because health care professionals needed them more, lab leak theory, military connections to the Wuhan Institute, US funding of WI, etc). HOWEVER, civil discourse is essential. That means that discussions about COVID were fraught with battlegrounds and bludgeoning. As such, we have additional restrictions for COVID discussions and other contentious topics and LLW needs to follow them. LLW did not do so and has shown a consistent flaunting of these restrictions and a weeklong block is a reasonable start. In summary, the quote isn't unreasonable to leave on their user page (give them that latitude), but a weeklong block for the other behavior should stand. Buffs (talk) 16:15, 16 January 2025 (UTC)
- They added two comments to their userpage. Both were critical of Misplaced Pages. One was also critical of Anthony Fauci and other aspects of the US government's COVID response. I removed the latter. It doesn't matter whether Sanger's opinion is fringe or not; what matters is that he was talking about COVID. I would be quite the hypocrite to remove something from someone's userpage just for criticizing Misplaced Pages, as I have a fair bit of that on my own userpage. -- Tamzin (they|xe|🤷) 17:02, 16 January 2025 (UTC)
- There's some pretty big overlap there in criticism of Fauci and how it is handled on Misplaced Pages. Again, I don't feel THAT is a significant violation of COVID editing restrictions (beyond the fact that they did it despite such an editing restriction). Anyone can completely skip over it if they wish. @Tamzin: playing devil's advocate for a moment, what if I published the same thing on my user page? Would it be ok? Would it be ok if I posted it on LLW's user page (as long as LLW was ok with it, of course)? I realize we're getting in the weeds of a "what-if..." but if so, what's the substantive difference between me putting it on a user page and LLW doing the same? Buffs (talk) 17:19, 16 January 2025 (UTC)
- If you posted it to your userpage, it would be fine (although not that constructive), because you are not topic-banned from COVID. If you posted it to their userpage, that would be WP:PROXYING for a banned editor, since I'd struggle to believe you have an independent reason to think that particular quote belongs on that particular page. If you really want to fight the removal from the userpage, feel free to create a subsection here, but I stand by the removal. -- Tamzin (they|xe|🤷) 17:29, 16 January 2025 (UTC)
- I'm not fighting the removal per se. Just wondering where the boundaries are and if it's wise to have such a boundary. Buffs (talk) 17:55, 16 January 2025 (UTC)
- The boundary is WP:TBAN. -- Tamzin (they|xe|🤷) 19:17, 16 January 2025 (UTC)
- I'm not fighting the removal per se. Just wondering where the boundaries are and if it's wise to have such a boundary. Buffs (talk) 17:55, 16 January 2025 (UTC)
- Buffs: In the realm of hypothetical I would presume that if that quote had been on LLW user page for a long time, in a sea of content, pre-existing AN, then it might even still be up today. However, on the other hand, to post that after the TBAN was imposed is nothing other than what can be seen as abject defiance to the ban. But beyond that, it simply violates plain language of the ban, as it applies to
all pages (not only articles) broadly related to the topic
, so I proffer that Tamzin is clearly in the right here. To your charged statement about if you were to post the same thing to your user page, prior to your statement here and presuming you were not under a TBAN, it would not be questioned one iota. However, as a response to this discussion, it could be construed (but not technically violating) the principles of WP:PROXYING and I would caution against it. Moreover, you reinstating it on LLW talk page would be a far closer in the proximity of violating PROXYING. TiggerJay (talk) 18:49, 16 January 2025 (UTC)- The fact that the comment only came after the topic ban is key here. I'm fairly sure I've seen several cases where there's something on an editor's user page which is covered by a topic ban but which no one has said or done anything about because it was there from before the topic ban. In fact I'm fairly sure I even remember a case where someone asked specifically if they could modify or remove something on their user page which related to their talk page which was technically under the topic ban (probably gensex). I think this was allowed especially since it related to their personal life rather than some comment on something, although they were told just this once is best. There might have even been a case where an editor wanted to do some more editing or formatting of something under their topic ban and was either denied or told only this once. IIRC, there was also an editor who was happy to be able to finally change someone on their userpage covered by their topic ban once it was lifted. A topic ban is a topic ban. I'd note that if someone makes an extremely constructive edit to an article that is not covered by WP:BANEX we still treat this as a topic ban violation, although it's something much more beneficial for the project than an editor being able to repost random ramblings about Misplaced Pages they want to share. Nil Einne (talk) 20:31, 16 January 2025 (UTC)
- If you posted it to your userpage, it would be fine (although not that constructive), because you are not topic-banned from COVID. If you posted it to their userpage, that would be WP:PROXYING for a banned editor, since I'd struggle to believe you have an independent reason to think that particular quote belongs on that particular page. If you really want to fight the removal from the userpage, feel free to create a subsection here, but I stand by the removal. -- Tamzin (they|xe|🤷) 17:29, 16 January 2025 (UTC)
- There's some pretty big overlap there in criticism of Fauci and how it is handled on Misplaced Pages. Again, I don't feel THAT is a significant violation of COVID editing restrictions (beyond the fact that they did it despite such an editing restriction). Anyone can completely skip over it if they wish. @Tamzin: playing devil's advocate for a moment, what if I published the same thing on my user page? Would it be ok? Would it be ok if I posted it on LLW's user page (as long as LLW was ok with it, of course)? I realize we're getting in the weeds of a "what-if..." but if so, what's the substantive difference between me putting it on a user page and LLW doing the same? Buffs (talk) 17:19, 16 January 2025 (UTC)
- They added two comments to their userpage. Both were critical of Misplaced Pages. One was also critical of Anthony Fauci and other aspects of the US government's COVID response. I removed the latter. It doesn't matter whether Sanger's opinion is fringe or not; what matters is that he was talking about COVID. I would be quite the hypocrite to remove something from someone's userpage just for criticizing Misplaced Pages, as I have a fair bit of that on my own userpage. -- Tamzin (they|xe|🤷) 17:02, 16 January 2025 (UTC)
- Oppose unblock, oppose indef - The topic ban violation was clear cut. Let's hope Lardlegwarmers will read a bit about how to avoid topic ban violations, or else indef block is not too far for them. Lorstaking (talk) 16:19, 16 January 2025 (UTC)
- Oppose unblock, extend block indefinitely - Lardle should try to demonstrate good behavior on another wiki for six months before asking for a SO. Let's hope that this user should handle contentious topics carefully in the future. Ahri Boy (talk) 18:35, 16 January 2025 (UTC)
- Oppose unblock but no reason to indef, a block has already been imposed. If the user continues to violate the TBAN, than a longer block might be warranted. JayCubby 02:43, 17 January 2025 (UTC)
Comments from involved editors
- Going to open a new subsection here since I've made comments to Talk:COVID-19 lab leak theory two weeks ago. I wish I could say I was surprised that this ended in tears but that would be untrue (though I did have some hopes the comment a month ago indicating they were aware pro-fringe POV-pushing was sactionable was a signal they were intending to modify their behaviour). As bɜ:ʳkənhɪmez points out, making thinly veiled attacks is not exactly the type of thing looked favourably upon in an unblock request. Nor is making polemical statements on one's user page, whether within the scope of the ban or not, likely to convince the community of one's inclination and ability to be a productive editor. Lardlegwarmers, if you do really want to return to editing, especially if you want to appeal your topic ban in 6 months or a year, I would strongly advise reading Misplaced Pages:Guide to appealing blocks and following the advice there, especially WP:NOTTHEM. Complaining about Hob's conduct won't help you here, because the block (and it's a rather short one) and ban are about you, not Hob. Given your comment that
apparently two wrongs make a right
, I had hoped that you were already also considering your own behaviour, but I would like to make it very clear: taking the role of one of the "wrongs" to address someone else's "borderline uncivil" behaviour is not itself considered acceptable behaviour. Whether Hob crosses the line is on them, but what you do is entirely on you. Alpha3031 (t • c) 07:16, 16 January 2025 (UTC) - As I was involved in the discussion to topic ban LLW I think I count as an involved editor. With that said I would discourage an early lifting of this block, which seems appropriate considering that LLW's response to the topic ban was to immediately violate the topic ban. Simonm223 (talk) 13:54, 16 January 2025 (UTC)
- Also, perhaps LLW wasn't aware of this, but people who aren't uninvolved administrators aren't generally supposed to put comments into the "results" section of an AE filing. Simonm223 (talk) 13:57, 16 January 2025 (UTC)
- I was there.. Three thousand ye-- No. More like one, two days ago. I seriously believe Lard Leg Warmers is one of two situations: 1: WP:CIR and unable to understand the concepts of medical science as if they were a Facebook mother invested in "essential oils" and "holistic medicine" rather than trusting medical and scientific experts; 2: WP:NOTHERE and simply f
**king with us for no good reason and leading us around, and around, and around, and around, and around the bend because they get a rise out of it. Either way, my advice: don't get led around the bend, advise indef block for either WP:CIR or WP:NOTHERE. BarntToust 16:38, 16 January 2025 (UTC)
- BarntToust, those kinds of personal assumptions about their character are unnecessary to this discussion. Instead of speculation on who they are elsewhere, let's just focus on their behavior on Misplaced Pages. Liz 06:45, 17 January 2025 (UTC)
- Lardlegwarmers' statement clearly shows that they have learned little from the sanction. They should demonstrate such before there is any lifting. O3000, Ret. (talk) 18:55, 16 January 2025 (UTC)
Usage of 'Notable people' vis-a-vis 'Notable person' in section headers
This is not an administrative issue. voorts (talk/contributions) 20:56, 16 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
In the course of editing numerous articles, I have come across the header featuring 'notable people' when there is only one person and have therefore modified the grammar.
I recently had another editor come behind me and revert one such edit on the grounds that things have always been done this way, regardless of the number of notables for a given locale, which makes little sense to me. Is this really policy? Hushpuckena (talk) 16:45, 16 January 2025 (UTC)
- This seems like a question for WP:MOS, not WP:AN as it doesn't involve administrator actions. AN isn't a general Help forum for questions about editing. You could even try asking at the Teahouse or the Help Desk. Liz 19:00, 16 January 2025 (UTC)
Reporting Administrator Abuse
I'm going to do the OP a favor and close this with no action against them. Essentially, the OP's misbehavior was pointed out by Acalamari and the OP is trying to present it as Acalamri's misbehavior. If another administrator thinks sanctions against the OP are warranted, that's up to them.--Bbb23 (talk) 23:56, 16 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
User:Acalamari is abusing his moderator powers in order to post unconstructive comments on talk pages, specifically when we were talking about if we should delete the US 2028 election or not, he said "that Drumpf supporters want there to be no more elections so they can remain in power forever doesn't mean we adhere to their delusions by deleting articles here". This is clearly unconstructive, and treating the talk page as a forum. I didn't know he was a moderator when I was removing his comment, and now he left all of these messages on my page and is saying I'm the real vandal here. TopVat19sEver (talk) 22:48, 16 January 2025 (UTC)
- So there's two things here.
- First, TopVat19sEver, you removed other users comments from a talk page (not allowed). A user voicing their opinion is not vandalism, not in the slightest. If you have a problem with what another user has said on the talkpage, rather than removing their comment (which is only allowed in very specific situations), you should bring it for discussion at an appropriate noticeboard, or preferably ask them to change their own comment.
- Second, Acalamari, could you please refrain from calling people "Drumpf supporters" and casting aspersions on the reasons for nominating an article for deletion? While you're entitled to your opinions, that's borderline (at best) incivility, especially when you call them "delusional".
- If both users agree to accept what they did wrong here and move forward, I don't think any further action is necessary. -bɜ:ʳkənhɪmez | me | talk to me! 22:53, 16 January 2025 (UTC)
- Ok, I'm newer to Misplaced Pages, I understand what you are saying, my train of thought was, "this comment looks like vandalism, vandalism on Misplaced Pages is removed, therefore remove". I didn't know that they don't do that for talk pages. Thank you my friend. TopVat19sEver (talk) 22:59, 16 January 2025 (UTC)
- Vandalism has a very specific definition on Misplaced Pages - see this page for more information on what is not vandalism. Merely calling people names and/or being uncivil, while against the rules, is not vandalism. There are proper processes for handling other rule violations (such as asking someone to edit their own comments, or asking a noticeboard for help) such as those, but they are decidedly not vandalism. -bɜ:ʳkənhɪmez | me | talk to me! 23:01, 16 January 2025 (UTC)
- Ok thank you for telling me TopVat19sEver (talk) 23:02, 16 January 2025 (UTC)
- Vandalism has a very specific definition on Misplaced Pages - see this page for more information on what is not vandalism. Merely calling people names and/or being uncivil, while against the rules, is not vandalism. There are proper processes for handling other rule violations (such as asking someone to edit their own comments, or asking a noticeboard for help) such as those, but they are decidedly not vandalism. -bɜ:ʳkənhɪmez | me | talk to me! 23:01, 16 January 2025 (UTC)
- Ok, I'm newer to Misplaced Pages, I understand what you are saying, my train of thought was, "this comment looks like vandalism, vandalism on Misplaced Pages is removed, therefore remove". I didn't know that they don't do that for talk pages. Thank you my friend. TopVat19sEver (talk) 22:59, 16 January 2025 (UTC)
- Where are the diffs? M.Bitton (talk) 22:54, 16 January 2025 (UTC)
- This is a baseless complaint. Ater not editing for months, the OP refactored an AfD that was closed last November. Acalamari rightly warned them for doing that.--Bbb23 (talk) 22:56, 16 January 2025 (UTC)
- I agree, but at the same time, I think TV19E has a right to be unhappy that Acalamari, an administrator and bureaucrat, was able to cast aspersions and call people names without it being called out at the time as far as I can see. They went about it the wrong way (removing the comment), but that doesn't mean there isn't room for discussion of that comment. -bɜ:ʳkənhɪmez | me | talk to me! 22:58, 16 January 2025 (UTC)
- Nope. First, it doesn't rise to the level required of this noticeboard, and, second, it's not at all timely.--Bbb23 (talk) 23:01, 16 January 2025 (UTC)
- To be blunt, Acalamari didn't even tell the editor when they initially reverted back in November (while the discussion was open) where they could discuss further/report if they felt the comment was not appropriate. I'm not suggesting sanctions against Acalamari at all. But to tell a new editor "someone broke the rules and since you didn't report it in the proper way at the time because nobody told you how, they're allowed to break the rules" is clear biting the newbies. I think all that's necessary is an apology from Acalamari - TV19E has already explained that they were mistaken as to it being vanadalism. -bɜ:ʳkənhɪmez | me | talk to me! 23:03, 16 January 2025 (UTC)
- Nope. First, it doesn't rise to the level required of this noticeboard, and, second, it's not at all timely.--Bbb23 (talk) 23:01, 16 January 2025 (UTC)
- I didn't edit for a few months because I have to do other things. I was just scrolling around I don't even remember what I was doing and I saw he put it back, I didn't know he was a mod, and it also said you can't edit archived talk pages, which he did, so I reverted his edit. TopVat19sEver (talk) 23:03, 16 January 2025 (UTC)
- That's not true. You modified a closed AfD. Acalamari rightly reverted your edit of an archived discussion.--Bbb23 (talk) 23:06, 16 January 2025 (UTC)
- I just said, he is the one who modified a closed AfD, which is not allowed, then I reverted it not knowing he is a moderator TopVat19sEver (talk) 23:08, 16 January 2025 (UTC)
- He didn't modify a closed AfD. His comment was readded while the discussion was still open, because you removed it in violation of the very few circumstances where you are allowed to remove another editor's comment. -bɜ:ʳkənhɪmez | me | talk to me! 23:09, 16 January 2025 (UTC)
- Oh okay this is my mistake then I thought it was after the AfD was closed my bad TopVat19sEver (talk) 23:11, 16 January 2025 (UTC)
- Wait hold on, I just looked at it again. He added back his comment after the result was SNOW. On the page when he re added it, it said do not edit the page. TopVat19sEver (talk) 23:16, 16 January 2025 (UTC)
- You removed Acalamari's comment as vandalism with the edit summary "subhanAllah". You had no right to do that. Acalamari restored it, which even though the AfD was closed, they had the right to do in the circumstances.--Bbb23 (talk) 23:27, 16 January 2025 (UTC)
- https://en.wikipedia.org/search/?title=Misplaced Pages:Articles_for_deletion/2028_United_States_presidential_election_(3rd_nomination)&oldid=1257014612 Take a look, this is his edit. When he re added his comment, on the page in red it said Do not edit the page TopVat19sEver (talk) 23:18, 16 January 2025 (UTC)
- The comment never should've been removed in the first place. It's within the spirit of the rules to readd a comment that you improperly removed, even if the discussion had been closed in the meantime. -bɜ:ʳkənhɪmez | me | talk to me! 23:32, 16 January 2025 (UTC)
- He didn't modify a closed AfD. His comment was readded while the discussion was still open, because you removed it in violation of the very few circumstances where you are allowed to remove another editor's comment. -bɜ:ʳkənhɪmez | me | talk to me! 23:09, 16 January 2025 (UTC)
- I just said, he is the one who modified a closed AfD, which is not allowed, then I reverted it not knowing he is a moderator TopVat19sEver (talk) 23:08, 16 January 2025 (UTC)
- That's not true. You modified a closed AfD. Acalamari rightly reverted your edit of an archived discussion.--Bbb23 (talk) 23:06, 16 January 2025 (UTC)
- I agree, but at the same time, I think TV19E has a right to be unhappy that Acalamari, an administrator and bureaucrat, was able to cast aspersions and call people names without it being called out at the time as far as I can see. They went about it the wrong way (removing the comment), but that doesn't mean there isn't room for discussion of that comment. -bɜ:ʳkənhɪmez | me | talk to me! 22:58, 16 January 2025 (UTC)
- (edit conflict) There's no admin abuse here as no admin tools have been used. In case you missed "The following discussion is an archived debate of the proposed deletion of the article below" with the bright red "Please do not modify it" at that AfD, I'll repeat the instructions here - don't modify archived discussions.-- Ponyo 22:57, 16 January 2025 (UTC)
- I was saying Admin abuse because of the fact that he is able to keep his comment on the page when even if he is violating the rules. I'm not a moderator so I can't do anything about. Now I just learned from that guy that they don't remove comments even if its vandalism, now I know. But thats why I reported it here you know. TopVat19sEver (talk) 23:01, 16 January 2025 (UTC)
- He is the one who edited the closed AfD. This was one of the reason why I reverted his edit. TopVat19sEver (talk) 23:10, 16 January 2025 (UTC)
- It's very hard to work out what's happening without the presence of diffs. M.Bitton (talk) 23:02, 16 January 2025 (UTC)
without the presence of diffs
. But Ponyo and I have contributed, so you're in the presence of greatness; isn't that better than diffs? :p --Bbb23 (talk) 23:08, 16 January 2025 (UTC)- Tiggerjay is bowing down in great humility before such greatness never before seen in this universe. Now.... where is the trout? TiggerJay (talk) 23:24, 16 January 2025 (UTC)
- Who am I to disagree with the Jedi? M.Bitton (talk) 23:52, 16 January 2025 (UTC)
- Okay, I've looked into this. And...surprise surprise, TopVat19sEver was the one who origially removed Aclamari's !vote while the AfD was still open . Yes, about a day after the AfD was closed, Aclamari reverted this removal , which is technically "editing a closed AfD" but I would say they were entirely within their rights to revert a bad removal. And now, suddenly, today, two months later, as their first edit after having done that improper removal, TopVat19sEver goes back to the AfD and removes Aclamari's !vote again , which Aclamari - entirely rightfully - reverted , and then TopVat19sEver comes here to cry "admin abuse", when no administrative abilities were used at all in this whole mess. Could Aclamari have used more moderate language in their initial !vote? Yeah maybe, but it was no violation at all, and the only thing needed here is a WP:BOOMERANG or at least a {{trout}} for TopVat19sEver. - The Bushranger One ping only 23:27, 16 January 2025 (UTC)
Ban appeal from Rathfelder
- Rathfelder (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- Community banned in November 2022 for sockpuppetry, vote-stacking and undisclosed COI writing of a BLP attack page
- Appeal in January 2023 declined by the community
- Second appeal in October 2023 not submitted for review by the community for not complying with WP:GAB
Rathfelder has submitted the following ban appeal on their talk page and asked me to copy it here:
I realise that what I did was wrong - more wrong than I thought it was at the time. The circumstances which led me to edit pages where I was conflicted are not likely to recur. I accept that I was wrong to create sockpuppets and I apologise. I was involved in a dispute with my employers and it was very wrong of me to use Misplaced Pages as part of that. I did that really because I was trying to defend the work I had done for the Socialist Health Association for the previous 20 years. I did a lot of edits on that page, but they were, until the last few, about the history of the organisation, mostly adding to its list of distinguished members - largely before I was involved with it, and mostly before I was born. They were not at all controversial. I was unfairly sacked and my opponents started using Misplaced Pages against me. The row got into the media. I accept that I should not have done that. I should have resisted the temptation to use Misplaced Pages in the dispute.
I have spent 2 years working on Simple English and Wikimedia. I have not set up any sockpuppets or edited anything where I had conflicts. I plan to continue with Wikimedia, as there is plenty there to keep me busy, but I would like to be able, in particular, to add pictures to articles - now I have found my way round the enormous Wikimedia resource. I also sometimes come across articles in English wikipedia which need amendment.
Chaotic Enby (talk · contribs) 17:02, 17 January 2025 (UTC)
- Conditional support - If there's been no socking during the ban. GoodDay (talk) 17:05, 17 January 2025 (UTC)
- Question during the January 2024 unblock request Rathfelder said they would be willing to accept a restriction on editing articles related to BLPs or healthcare orgs. Are they still willing to accept those edit restrictions if they are un-banned? Furthermore, in January 2024 there was, at the time, no evidence of any further socking. Can we confirm that good behaviour has continued? Simonm223 (talk) 17:17, 17 January 2025 (UTC)
- Support They have been a very productive contributor at the Simple English Misplaced Pages, and it has definitely been long enough for the standard offer. QuicoleJR (talk) 21:33, 17 January 2025 (UTC)
Appealing April 4 2024, indefinite WP:CUP ban and indefinite 1-nomination GAN limit
Consensus to lift this ban will not develop. voorts (talk/contributions) 22:02, 17 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
At User_talk:TonyTheTiger#Topic_bans, I was instructed by closer User:Ingenuity that I could appeal these in a year and it has been 9.5 months. I am appealing because the CUP entry deadline is traditionally January 31. See Misplaced Pages:WikiCup/2020 signups through Misplaced Pages:WikiCup/2024 signups. This year the Misplaced Pages:WikiCup/2025 signups verbiage says "The competition will begin on 1 January 2025 and signups will continue throughout the year". I am just noticing the new language as I am putting this appeal in. Nonetheless, I am requesting time off for good behavior on the ban.-TonyTheTiger (T / C / WP:FOUR / WP:CHICAGO / WP:WAWARD) 18:52, 17 January 2025 (UTC)
- Oppose The utter cluelessness of this appeal is more than enough reason not to do this. I was going to write more but decided that coaching you on how to be less clueless is not in the project's best interest. You've been here long enough that you should be able to see for yourself how terrible this appeal is. Beeblebrox 19:02, 17 January 2025 (UTC)
- Oppose and recommend we disallow any further appeals for another year. I'm concerned otherwise we'll just be back here in April. --Yamla (talk) 19:14, 17 January 2025 (UTC)
- Oppose for now It's pretty clear that most people in that discussion were supporting an indef ban from the Cup, not an 8-month ban. This appeal doesn't address people's concerns with Tony's editing relating to the Cup, so should be denied. --SarekOfVulcan (talk) 19:16, 17 January 2025 (UTC)
- Oppose The original discussion wasn't linked, it can be found here. At that place it is very clear that
here is almost unanimous support for an indefinite ban on participation in the WikiCup
, so, no, this appeal should not be passed. It is, honestly, astonishing that TonyTheTiger has been here very nearly two decades but hasn't taken on board the way the community works ~ Lindsay 19:20, 17 January 2025 (UTC) - Oppose for no rational that they understand why they were banned or what even led to their ban, and rather simply a sentiment of "I really want to participate". Please understand that your ban was indefinite, so the one year appeal opportunity is your potential opportunity "time off for good behavior". TiggerJay (talk) 19:24, 17 January 2025 (UTC)
- Oppose. Appealing early on the basis that you won't be able to sign up to do the thing you were banned from doing is certainly a unique take. ♠PMC♠ (talk) 21:03, 17 January 2025 (UTC)
Requesting info
Steve Quinn is trouted for bringing this to AN. voorts (talk/contributions) 21:58, 17 January 2025 (UTC)The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
Hello. I have come across several image files and the U.S. Gov. PD licensing seems to be incorrect. Four of these images and possibly another one could be copyright violations - if I can figure out how to find this type of information on their websites. However, since I am unable to find that information at this moment, I am wondering which group of Misplaced Pages editors work on this sort of thing so that maybe I can get some help with this. I will post the files here for information purposes. Also, there may be more copyright violations by this particular editor who seems to have a propensity for downloading image files. Below are the files:
- File:AL-Cattlemen-2022-approved-passenger-768x376.jpg
- File:AL-Ducks-Unlimited-2022-768x370.jpg
- File:AmateurRadAZ.jpg
- File:AppalachianTN.jpg
- File:Acplate.jpg
Further comment: The above TN file - File:AppalachianTN.jpg - is covered by the TN.GOV "linking policy" and can be found here. So this Misplaced Pages image file is still not licensed appropriately, although I have no idea what the correct Misplaced Pages licensing would be.
I will notify the editor who downloaded these files that I have opened a discussion here. Well, now that I have taken it this far, the editor in question is: Brian.S.W (talk · contribs · deleted contribs · logs · filter log · block user · block log). However, the above image files might be too stale to be considered for any action. I leave that up to the Admins. If you look on their talk page, they have previously been blocked for copyright violations. ---Steve Quinn (talk) 20:59, 17 January 2025 (UTC)
- As you can see they've already been tagged for a deletion discussion yesterday, so there is no need to have a difference notice board also working on it. TiggerJay (talk) 21:21, 17 January 2025 (UTC)