Wikipedia:Administrators' noticeboard
Welcome — post issues of interest to administrators. |
---|
When you start a discussion about an editor, you must leave a notice on their talk page. Pinging is not enough. Sections inactive for over seven days are archived by Lowercase sigmabot III.(archives, search) |
Open tasks
[edit]V | May | Jun | Jul | Aug | Total |
---|---|---|---|---|---|
CfD | 0 | 0 | 0 | 10 | 10 |
TfD | 0 | 0 | 1 | 4 | 5 |
MfD | 0 | 0 | 0 | 2 | 2 |
FfD | 0 | 0 | 0 | 1 | 1 |
RfD | 0 | 0 | 4 | 81 | 85 |
AfD | 0 | 0 | 0 | 1 | 1 |
- 3 bot-reported usernames for administrator attention
- 9 user-reported usernames for administrator attention
- 4 bot-generated requests for intervention against vandalism
- 2 user-generated requests for intervention against vandalism
- 102 sockpuppet investigations
- 36 Candidates for speedy deletion
- 7 Fully protected edit requests
- 3 Candidates for history merging
- 0 requests for RD1 redaction
- 57 elapsed requested moves
- 2 Pages at move review
- 31 requested closures
- 143 requests for unblock
- 0 Wikipedians looking for help from administrators
- 23 Copyright problems
Pages recently put under extended-confirmed protection
[edit]Report
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Andrew Davidson's behavior at DYK
[edit]A couple of weeks ago, Andrew Davidson showed up at WT:DYK with Special:Diff/1231899272, in which he called a hook "nonsense" and the nominator "The main culprit". He implied that DYK was not "a respectable publication" and expressed a desire to "shame" DYK in order to "deter sloppy work". Since then, he's been posting reports on WP:ERRORS#Current DYK almost every day complaining about something. Some of his complaints are legitimate, some are not, but the overall tenor seems to be the shaming theme. Yesterday he wrote It's puzzling to me that others have difficulty in spotting such issues which leap out to me
.
Multiple people have requested that instead of waiting for the problems he spots to hit the main page, he could be providing a more valuable service by pointing out mistakes before they get published. Yesterday I requested on his talk page that he stop. In response he gave a long excuse why he's going to keep doing what he's doing, and took another dig at the DYK crew, calling out "careless oversights". He even saw fit to take a dig at how we organize the page we use for our internal discussions, asking "How hard is that?" with reference to his doing something his own way. I guess because he knows better what works for us than the people who work here every day?
All of this would normally not be enough to drag somebody to AN, but I see he's got a long history of this kind of disruptive behavior and is no stranger to WP:AN. In 2017, he avoided any official sanction but was chided for being disruptive at RfA. In 2020, he was warned about bad-faith editing and "advised to take seriously the feedback (and in some cases warnings) offered by many, particularly around personal attacks". In 2021, he was TBANNED from deletion discussions.
It seems inevitable that what's going on at DYK will end up here eventually, so I'm bringing it up now in the hopes of avoiding additional disruption. Nobody's denying that errors get made at DYK. I've certainly complained about my share. But Andrew needs to understand that just standing on the sidelines throwing darts at the people trying to get the work done isn't useful. Like so many parts of enwiki, DYK is understaffed and overworked. We don't need critics, we need more people helping to do the work. RoySmith (talk) 14:17, 14 August 2024 (UTC)
- If those responsible for creating DYK content aren't prepared to do the necessary work to get it right, why should anyone else feel obliged to fix it for them? AndyTheGrump (talk) 14:43, 14 August 2024 (UTC)
- Looking at the previous few days of ERRORS I don't see anything actionable. Pointing out issues at the forum for noting such errors isn't disruption: speaking as someone who has only infrequently dealt with the DYK system, it's byzantine and not a great place to browse discussions on hooks. I don't think his behavior counts as "standing on the sidelines" in this case (he is contributing, just not to the degree or in the venue you would prefer.)
- Andrew might be occasionally more pedantic about aspects of the criteria than the regulars at DYK, but I don't see how calling out facts about DYK's regular issues is disruptive on the face. It seems like the fact there isn't any sort of disincentive for posting sloppy or erroneous work to DYK is one of the problems with the process, and should probably be explored if improving the quality of what gets posted is the main goal. I'm not a fan of much of Andrew's conduct, but I don't think poor behavior in deletion discussions is really germane to this situation. Der Wohltemperierte Fuchs talk 15:29, 14 August 2024 (UTC)
- Waiting until the last moment to raise issues is a long-standing problem at DYK, and incredibly annoying. But I was rather surprized to see this complaint being initiated by a regular offender, though he doesn't wait until they are actually on MP. Pot and kettle? Johnbod (talk) 15:46, 14 August 2024 (UTC)
- Having problematic or plainly wrong DYK entries on the Main Page is a long-standing problem of DYK, and incredibly annoying. Today, Andrew Davidson raised a complaint about the island hook at WP:ERRORS. But that hook was only in the DYK since yesterday 16.29, earlier there was a different hook[1]. Doesn't give people much time to check these... Fram (talk) 16:05, 14 August 2024 (UTC)
- There are many excellent editors involved with DYK, both writing/nominating and reviewing/administrating but the structure and institution of DYK has perennially prioritised quantity over quality, which results in poor hooks and poor-quality articles repeatedly hitting the main page. And historically, DYK has failed to get its own house in order, leaving it to others to point out the problems. While I'm sure we would all appreciate it if Andrew was more constructive in his criticism, DYK is probably more of a net-negative than he is at this point. HJ Mitchell | Penny for your thoughts? 16:28, 14 August 2024 (UTC)
- It may be partially a time-on-task matter, rather than quantity, but with humans involved, mistakes, miscommunications, misunderstandings are going to happen, all the way until it roles off the page. Alanscottwalker (talk) 17:13, 14 August 2024 (UTC)
- Sure, but DYK is about filling sets regardless of whether the article is 1500 characters thrown together from a few marginally reliable gossip sites or 15,000 words built from days research using book sources, and the compulsory quid pro quo makes superficial reviews by people with no interest or knowledge of the subject a feature rather than a bug. And instead of requiring higher-quality articles, we just have an extremely complicated set of rules, additional rules, and supplementary rules. All because DYK is designed to keep the backlog down, not encourage quality. HJ Mitchell | Penny for your thoughts? 17:51, 14 August 2024 (UTC)
- Interesting, I wonder if anyone really involved in DYK would care to comment, with ways to address, it seems like there could be ways to address some of that (although since there is no real system to qualify writers, qualifying editors seems a real stretch) but 'better articles' might still be a point to go for. Alanscottwalker (talk) 18:26, 14 August 2024 (UTC)
- There are steps currently being taken to try to bring the focus away from pushing low-quality articles onto the main page. For example, we have started to "time-out" nominations that clearly aren't going anywhere and will cause nothing but controversy when actually on the main page. This may seem like a very small step, but it turns out that editors get rather unhappy at even the thought of their nominations not being accepted, and so we have to deal with the histrionics. ~~ AirshipJungleman29 (talk) 11:14, 15 August 2024 (UTC)
- This is an incorrect assessment of what is happening at DYK, and nothing will be fixed if this is problem is misdiagnosed like this. DYK is not about filling sets, nor is it designed to keep the backlog down. DYK regulars would be I'm sure extremely happy to have less sets and less work. Those are both symptoms of the core issue, which is that nominators don't like being rejected, and reviewers don't go out to upset people. Quite basic, people-focused issues (the same that cause trouble occasionally at GAN), rather than some apparent desire to push out sets. CMD (talk) 11:38, 15 August 2024 (UTC)
- Interesting, I wonder if anyone really involved in DYK would care to comment, with ways to address, it seems like there could be ways to address some of that (although since there is no real system to qualify writers, qualifying editors seems a real stretch) but 'better articles' might still be a point to go for. Alanscottwalker (talk) 18:26, 14 August 2024 (UTC)
- Sure, but DYK is about filling sets regardless of whether the article is 1500 characters thrown together from a few marginally reliable gossip sites or 15,000 words built from days research using book sources, and the compulsory quid pro quo makes superficial reviews by people with no interest or knowledge of the subject a feature rather than a bug. And instead of requiring higher-quality articles, we just have an extremely complicated set of rules, additional rules, and supplementary rules. All because DYK is designed to keep the backlog down, not encourage quality. HJ Mitchell | Penny for your thoughts? 17:51, 14 August 2024 (UTC)
- It may be partially a time-on-task matter, rather than quantity, but with humans involved, mistakes, miscommunications, misunderstandings are going to happen, all the way until it roles off the page. Alanscottwalker (talk) 17:13, 14 August 2024 (UTC)
- There are many excellent editors involved with DYK, both writing/nominating and reviewing/administrating but the structure and institution of DYK has perennially prioritised quantity over quality, which results in poor hooks and poor-quality articles repeatedly hitting the main page. And historically, DYK has failed to get its own house in order, leaving it to others to point out the problems. While I'm sure we would all appreciate it if Andrew was more constructive in his criticism, DYK is probably more of a net-negative than he is at this point. HJ Mitchell | Penny for your thoughts? 16:28, 14 August 2024 (UTC)
- Having problematic or plainly wrong DYK entries on the Main Page is a long-standing problem of DYK, and incredibly annoying. Today, Andrew Davidson raised a complaint about the island hook at WP:ERRORS. But that hook was only in the DYK since yesterday 16.29, earlier there was a different hook[1]. Doesn't give people much time to check these... Fram (talk) 16:05, 14 August 2024 (UTC)
- Well, just from watching over the years, volunteer editor-general for Main Page DYK is probably bound to happen. I suppose counseling him to tone it down (and telling him, we are almost all sometimes less than satisfied at what others do, here) might help, as such annoyance, particularly when strident, eventually might boomerang -- there are just more chances to eventually fall down when doing such an in-others-face critiquing role, over and over again. Alanscottwalker (talk) 16:18, 14 August 2024 (UTC)
- Andrew violated no rules, I'm afraid. Just a matter of manners at worst, which isn't actionable. BorgQueen (talk) 18:25, 14 August 2024 (UTC)
- When I was a kid, bad manners earned me an early bedtime without supper. But I guess that has gone out of style. RoySmith (talk) 19:33, 14 August 2024 (UTC)
- This all feels very similar to how Andrew interacts with ITN: raising a mixture of legitimate and illegitimate criticisms in what is almost certainly good faith but arguably the least helpful way possible; complaining that things should be done his preferred way - even when (sometimes multiple) consensuses have not supported his changes; and/or refusing to see if there is a consensus for his preferences. This in unquestionably annoying and has understandably pissed off multiple people, but fortunately or unfortunately (depending on your point of view) it rarely goes beyond annoying into actionable. — Preceding unsigned comment added by Thryduulf (talk • contribs) 19:18, 14 August 2024 (UTC)
- Echoing this, pretty much. Unfortunately par the course for Andrew, it's genuinely annoying behavior but unlike his behavior at AfDs it's not disruptive enough to sanction. The Kip (contribs) 19:56, 14 August 2024 (UTC)
- I have wondered why he seems to prefer checking sets that are already on the main page (i.e. working against the process) to checking sets that are yet to appear (i.e. working constructively with the process). It seems he likes to appear as a lone ranger figure—turning up, shooting a few bullets and one-liners, and abruptly departing. Works for the cameras, not so much for the well-being of the Wild West town (to continue this increasingly involved analogy). ~~ AirshipJungleman29 (talk) 11:20, 15 August 2024 (UTC)
- If one of the goals is overall improvement of DYK, with error frequency the primary metric for evaluating the process, surely noting problems that did make it to the main page is still a solid positive even if it's too late fix them individually? JoelleJay (talk) 18:18, 15 August 2024 (UTC)
- I don't think I've agreed with Andrew Davidson in any Wikipedia-space discussion ever, and yet somehow I don't see any problem at all with what he's been doing at DYK. In fact I think it's very important that if we're going to be gauging overall DYK process success by the frequency it has errors we should make sure that that percentage is actually accurate and not just a sampling of whichever hooks a knowledgeable passer-by happens to notice might be problematic during the narrow windows they run. I know there have been several occasions where I've seen an issue but then realized there were only a couple hours left or the slot had already passed and figured bringing it up wouldn't be appreciated. In retrospect I don't think that was correct; just because a hook can't be pulled anymore doesn't mean an error didn't make it to the main page, and it's still helpful to acknowledge that it happened. Also the first few times I noticed something I didn't even know where to comment...the nom on the talk page is already closed, and clicking on the DYK link in the talk page banner just takes you to the template page which is useless for anyone trying to find out what DYK is or where to discuss the hook somewhere other than a TP that is almost by definition going to have almost no one watching it... David is right about "Byzantine". JoelleJay (talk) 18:10, 15 August 2024 (UTC)
- I have long said, one of those "joking, but not really" sort of comments, that I avoid Front Page processes, preferring to stick to less contentious areas like arbitration enforcement. Personally I find DYK a really unpleasant process to go through precisely because of the tension on display in this discussion - and indeed this process once introduced an error into a hook I wrote which was just incredibly frustrating to have happen after jumping through the various hoops DYK requires. I have a great deal of sympathy and respect for the work Andrew, and others like him, who is doing his best to try and serve our readers by making sure that we are giving them accurate information and is investing real time, effort, and care to do this. I also have a great deal of sympathy for Roy, and others like him, who is also doing his best and who is doing so in a system that is designed to reduce errors with multiple steps and checks only to then still be criticized by someone who is making no effort to participate until it's "too late" despite the real time, effort, and care he has invested. Best, Barkeep49 (talk) 18:22, 15 August 2024 (UTC)
- Please note that I have participated in DYK in a variety of ways over the years. I have nominated over 100 articles, including articles created by other editors at outreach events. The nominations require QPQ reviews and so I've done lots of those too. And I've participated in DYK internal discussions over the years too. The only thing I've not gotten involved in is set-building and promotion of the queues. That's because it's quite a complex process and I don't have admin rights.
- So, the idea that I'm purely lurking outside the process waiting to pounce is mistaken. I had a DYK of my own on the main page recently (Doris "Lucki" Allen) and I have another one in the pipeline right now (Quintus Quincy Quigley). My activity at WP:ERRORS arises because I usually read the main page every morning and most of the DYK hooks are new to me as there are a lot of them. I like browsing them, take an interest in the ones that attract my attention and take it from there. Sometimes I thank; sometimes I give a barnstar; sometimes I report an error; sometimes I go down the rabbit-hole; and otherwise I just move on.
- Andrew🐉(talk) 19:40, 15 August 2024 (UTC)
- @Andrew Davidson, re: That's because it's quite a complex process and I don't have admin rights, you don't need admin rights to promote hooks to sets. With over 100 nominations, and the amount of time you spend scrutinizing DYK on the main page, you should have zero problem with the complexity. It's not rocket science, and there is always someone around to tell you what you've done wrong this time. Valereee (talk) 18:13, 17 August 2024 (UTC)
- Helping to build sets has been a great opportunity for me to learn. I'm not perfect at it, but the people at WT:DYK, and especially the admins promoting sets, have been very helpful, kind, and patient throughout the process. Hey man im josh (talk) 15:03, 18 August 2024 (UTC)
- @Andrew Davidson, re: That's because it's quite a complex process and I don't have admin rights, you don't need admin rights to promote hooks to sets. With over 100 nominations, and the amount of time you spend scrutinizing DYK on the main page, you should have zero problem with the complexity. It's not rocket science, and there is always someone around to tell you what you've done wrong this time. Valereee (talk) 18:13, 17 August 2024 (UTC)
- Roy and Andrew both agree that the error rate at DYK is too high. I would hope there would be a way for them to set aside differences and work together on solving that mutually-recognized problem. On the one hand, Roy, I don't think it's fair to expect Andrew to look at queues and preps and not the main page when there are still bona-fide main page errors several times per week. On the other hand, Andrew, pointing out main page errors doesn't help stop them from happening; there would be fewer main-page errors if we caught them in the queue or in the prep.
- As always, I think everyone should listen to me: the reason this is happening is because we are running too many hooks per day. We don't have the human resources needed to create and vet 9 hooks every day. If we cut the number of hooks like in half, the same number of volunteers could spend twice as much time on each one in the review, prep, and queue stages, significantly reducing the number of errors that hit the main page. In the simplest form: if we cut the number of hooks in half, the same amount of time Andrew spends each day reviewing the main page hooks could be spend reviewing the main page and the next queue. That's the real solution here. Levivich (talk) 00:07, 16 August 2024 (UTC)
- @Levivich May I quote you the next time somebody suggests we go to two sets per day because we need to churn through the backlog? RoySmith (talk) 00:18, 16 August 2024 (UTC)
- YES! And ping me so I can take them to ANI. :-D I remember this being raised/discussed at WT:DYK before I did the May and June error reports, and it seemed nobody at WT:DYK really wanted to seriously consider this. But I am convinced: one month of half as many hooks, and we can all watch the error rate shoot up from 93% to 99%. Levivich (talk) 00:26, 16 August 2024 (UTC)
- I sincerely hope we never have a month with an error rate of 99%. RoySmith (talk) 01:04, 16 August 2024 (UTC)
- I support the idea Levivich is proposing here. I think it would be helpful to 1) get consensus here or someone where else from a broader community to prioritize this so you're not quoting a single person but rather consensus and 2) for the DYK regulars to decide, broadly speaking, what hooks will be prioritized. I'm guessing this would default to First in, first out but I would suggest something that spread the wealth (in other words penalize the DYK writing regulars who might have multiple hooks in prep or who've recently had something run) would be a better method. Best, Barkeep49 (talk) 00:37, 16 August 2024 (UTC)
- For spreading the wealth, maybe a one-hook-per-nom-per-set rule? Levivich (talk) 00:42, 16 August 2024 (UTC)
- I would be fine with that partially. We would also need to figure out if it works the same way for editors who nominate articles started by non-DYK regulars or non-DYK editors in general. I say partially because it should be stricter than a one-hook-per-nom-per-set rule because a set typically already has one editor per hook per set. SL93 (talk) 01:20, 16 August 2024 (UTC)
- One-hook-per-nom-per-3-sets could work but it would be a pain to manage for prep builders, I imagine. Levivich (talk) 12:51, 16 August 2024 (UTC)
- As someone doing a bit of work in prep over the last couple months, it really would be. That's the biggest issue from my point of view. When building sets, I'm typically looking at Template:Did you know/Queue#Prep areas, placing good hooks in appropriate preps to balance out bios, sports, music, etc., I'm not usually opening an individual queue and never focused on who already had pages in another prep or queue. This idea would involve opening up at least five queues at a time, to see two forward and back, in case anything in a slot behind that prep area has been filled. Hey man im josh (talk) 15:11, 18 August 2024 (UTC)
- One-hook-per-nom-per-3-sets could work but it would be a pain to manage for prep builders, I imagine. Levivich (talk) 12:51, 16 August 2024 (UTC)
- I would be fine with that partially. We would also need to figure out if it works the same way for editors who nominate articles started by non-DYK regulars or non-DYK editors in general. I say partially because it should be stricter than a one-hook-per-nom-per-set rule because a set typically already has one editor per hook per set. SL93 (talk) 01:20, 16 August 2024 (UTC)
- I suspect people are too attached to WP:NOTPAPER. That's a great
essay(whoops, I just checked, it's a full fledged policy) when applied to all of mainspace. But when it comes to the front page sections, there really is a space limitation; the exact number of pixels DYK is allowed to consume is a little squishy, but basically we have to play nice with our space or the OTD folks will want to know why. So, as I've said many times on WT:DYK, if we have a fixed output rate and the input rate (i.e. nominations) is bigger, we need to find another way to make it all balance. Any freshman engineering student who has taken Control Theory 101 knows that. As does anybody who has ever confronted a toilet which is draining slower than it's filling. It's all the same math. But people get bent out of shape over the idea that we need to judge submissions on their merits and reject the ones that aren't as good as the others. RoySmith (talk) 01:28, 16 August 2024 (UTC)- People getting bent out of shape is why I suggested both of my ideas. A community consensus with a selection criteria that has at least some objectivity to it is going to be perceived as more fair by nomination writers. I do think it important to also remember the pride and importance nomination writers have in the DYK process so of course there is going to be disappointment at being turned down. Best, Barkeep49 (talk) 15:14, 16 August 2024 (UTC)
- For spreading the wealth, maybe a one-hook-per-nom-per-set rule? Levivich (talk) 00:42, 16 August 2024 (UTC)
- YES! And ping me so I can take them to ANI. :-D I remember this being raised/discussed at WT:DYK before I did the May and June error reports, and it seemed nobody at WT:DYK really wanted to seriously consider this. But I am convinced: one month of half as many hooks, and we can all watch the error rate shoot up from 93% to 99%. Levivich (talk) 00:26, 16 August 2024 (UTC)
- I don't "agree that the error rate at DYK is too high" because I don't think that we know what the error rate is. We don't know this because we don't measure or record it. For example, WP:ERRORS is a noticeboard that doesn't keep archives. Instead of keeping records and statistics, the culture at WP:ERRORS is to shut down and clear discussion and reports as quickly as possible. And also, as we see in this case, to shoot the messenger too.
- I keep a personal archive for my own interest and reference but this is quite haphazard as I don't patrol the main page systematically. From this, it seems that I've discussed about 80 DYKs at WP:ERRORS over about 8 years. This doesn't seem especially high -- it's certainly less than 1% of the total.
- Now DYK does put quite a lot of effort into statistics -- see WP:DYKSTATS. It systematically records the number of nominations made by editors (for the QPQ requirement) and it records the readership for hooks, which is the main metric and goal. We might do more but DYK is so high volume that some script and template work would be needed.
- Andrew🐉(talk) 06:40, 16 August 2024 (UTC)
- No, Andrew, this is not shooting the messenger. If you started with, "I see a problem, how can I help fix it?", you would have been welcomed with open arms. Instead, you started with "If DYK published regular corrections then the shame might be a useful check and balance, helping to deter sloppy work." You should take this as a life lesson: if you see a group of people who are volunteering their time to do a job, insulting them and holding them up for public shaming because they're not doing as good a job as you want, isn't the way to get them to do a better job. RoySmith (talk) 11:50, 16 August 2024 (UTC)
- Wikipedia talk:Did you know/Archive 200#DYK error rate. But if you don't think the error rate is too high, then fine, go work on something else. Levivich (talk) 12:54, 16 August 2024 (UTC)
- @Levivich May I quote you the next time somebody suggests we go to two sets per day because we need to churn through the backlog? RoySmith (talk) 00:18, 16 August 2024 (UTC)
- If I may butt in as someone who was very active at DYK and then stepped away for some of the reasons that have arisen above: the issue we circle back to in these discussions, the common thread across all the threads about sub-optimal behavior and structure, is the number of hooks DYK attempts to run. Fixing that means increasing the human resources we put into the problem, or reducing the number of hooks we run. Both these approaches have proved difficult; because we quickly run out of editors willing to do the review work, and because we are very reluctant as a community to approve fewer hooks. Until we change that, we're going to end up having these conversations (that give me a strong sense of deja vu); every so often. Vanamonde93 (talk) 01:46, 16 August 2024 (UTC)
- Like Vanamonde I've been very active at DYK and have more or less stepped away. IMO DYK is a problem that can't be solved because the people doing the work are vastly outnumbered by the people making the nominations, and almost all solutions require either (or both)
- More work from nominators
- Fewer approved nominations
- Both of these are unpopular with nominators. Which means we can't get consensus for any of them. Valereee (talk) 18:00, 17 August 2024 (UTC)
- If Andrew's waiting until items are already on MP, or about to appear, there may be a good reason: if you're really good a spotting errors (or potential errors requiring some research to check), every step you move upstream (in DYK's fairly porous checking process) to apply that talent rapidly increases the number of errors/potential errors you find yourself uncovering and calling out. It can be overwhelming. DYK has always had one or two people who fulfilled the role of last-moment checker, and thank goodness for them. But it's a very dispiriting role, and people fulfilling it can become sour, because you come to feel like too many people upstream are asleep at the switch. EEng 18:18, 17 August 2024 (UTC)
- Perhaps come up with metrics to require the DYK factoid to be central to the article. What you may lose in quirky can be made up for with more natural focus on a supportable central article factoid (by writer and editor), better streamlined articles, and also prevent having the reader be less likely to go, 'what a way to misrepresent a subject' or 'I can barely find that factoid' in the article. Alanscottwalker (talk) 14:20, 18 August 2024 (UTC)
- Strongly disagree. That the facts presented are odd or intriguing, so that the reader is drawn in, is DYK's great strength. The single thing that would most improve DYK quality would be to drop the ridiculous "newness" criterion: articles have tobe nominated within 14 (?) days of creation. That pretty much guarantees that inchoate, half-baked articles are will be shoveled onto the main page. EEng 13:26, 19 August 2024 (UTC)
- Well, to the extent it is some kind of "strength", that clickbait aspect has always been discordant and caused discord. Also, at least in the past there was no real way to judge interesting as a group, nor enforce it. At any rate, "central" is not a synonym for "uninteresting". (And a bit contrary to your assumption, it is more likely that most DYK articles are planned practically in full by their writer for the front page spot before it was written.) Alanscottwalker (talk) 13:32, 19 August 2024 (UTC)
- The clickbait criterion does cause issues, but "central" seems open to similar vagueness. What is central to Johann Joseph Dömling? (It would also create more entries overall, as we do get at least some articles rejected for lack of good hooks.) CMD (talk) 14:06, 19 August 2024 (UTC)
- That's why you come up with metrics, like naturally mentioned in the lead, or a paragraph, or type of fact. For example with Dömling, it might be something about their path breaking. Nor is my proposal about getting rid of 'interesting', its rather channeling it. -- Alanscottwalker (talk) 14:23, 19 August 2024 (UTC)
- The clickbait criterion does cause issues, but "central" seems open to similar vagueness. What is central to Johann Joseph Dömling? (It would also create more entries overall, as we do get at least some articles rejected for lack of good hooks.) CMD (talk) 14:06, 19 August 2024 (UTC)
- Well, to the extent it is some kind of "strength", that clickbait aspect has always been discordant and caused discord. Also, at least in the past there was no real way to judge interesting as a group, nor enforce it. At any rate, "central" is not a synonym for "uninteresting". (And a bit contrary to your assumption, it is more likely that most DYK articles are planned practically in full by their writer for the front page spot before it was written.) Alanscottwalker (talk) 13:32, 19 August 2024 (UTC)
- Strongly disagree. That the facts presented are odd or intriguing, so that the reader is drawn in, is DYK's great strength. The single thing that would most improve DYK quality would be to drop the ridiculous "newness" criterion: articles have tobe nominated within 14 (?) days of creation. That pretty much guarantees that inchoate, half-baked articles are will be shoveled onto the main page. EEng 13:26, 19 August 2024 (UTC)
- An important principle here is that being right isn't enough. Andrew Davidson and others aren't wrong that errors happen; errors do, and they should happen less. However, this doesn't justify being uncivil and disruptive about it. Some comments claim that this is just about 'manners' and that disrespect isn't actionable. But respect is one of Wikipedia's five pillars. If Andrew Davidson's treatment of other editors is disruptive, that is actionable under Wikipedia's policies and guidelines, which govern behavior as well as conduct. OP is right that Andrew Davidson could contribute without throwing in caustic digs at editors.OP also rightly notes that Andrew Davidson's complaints are of inconsistent legitimacy. Two of the more dubious "errors" he reported include arguing that a hook about a woman should've focused on her physical appearance instead of her actions and claiming that following the WP:EN naming convention guideline was a "gross error". While wanting things to be done
his own way
, to quote OP, is an understandably human desire, opinions like these aren't errors, and reporting them as if they are is unhelpful because doing so adds noise to pages and discussions, making it harder to see and talk about actual errors.I hope that Andrew Davidson will be willing to contribute this help with spotting errors while dispensing with disrespecting community members and claiming that non-errors are errors. Hydrangeans (she/her | talk | edits) 01:48, 20 August 2024 (UTC)
- I side with AD here as the net benefit to the community. There's a LOT of sloppy work on the main page. Levivich' suggestion should be given serious consideration. Buffs (talk) 15:42, 20 August 2024 (UTC)
Bot to inform temp users of expiry
[edit]I was requested to seek consensus at Wikipedia:Bots/Requests_for_approval/Leaderbot#Discussion. Basically, I'm working on a (global) bot that informs users when their temp permission (which would normally be the non-admin rights on Wikipedia) would expire in a week (giving these users enough time to re-apply), and wanted to ask if the English Wikipedia community would be fine with it. This will be opt-out (opt-in is possible if the community would rather have that), with the mechanism for that not yet decided. If there is something else I need to do, please let me know. Thanks in advance. Leaderboard (talk) 14:26, 15 August 2024 (UTC)
- Support in principle. I don't see an issue with it. voorts (talk/contributions) 17:19, 15 August 2024 (UTC)
- Support in principle. This seems useful and unproblematic, as long as opting out is simple and the ability to do so is clear (e.g. it should respect {{nobots}} templates). Thryduulf (talk) 18:38, 15 August 2024 (UTC)
- Support: As someone who grants a lot of trials for perms, I like it. It makes sense, and we have FireflyBot, which notifies users of drafts about to expire, which is a similar enough concept. Hey man im josh (talk) 18:46, 15 August 2024 (UTC)
- As someone who grants mostly temporary IPBE, I'd definitely want to see an opt-in/out option, based on the log entry and not the talk page. A reminder for IPBE is in many cases likely to be uninformative or confusing (some people don't even know they have it). To give another example of a potential issue, telling someone that their confirmed status is about to expire when they're autoconfirmed is going to be misleading. Not objecting at this stage, just suggesting things to think about. -- zzuuzz (talk) 19:07, 15 August 2024 (UTC)
- Similarly, any temporary permissions that form part of the admin toolkit granted to a non-admin who has become an admin in the meantime. Thryduulf (talk) 19:18, 15 August 2024 (UTC)
- I don't think that would be a problem, because my understanding is that the temp rights are removed when the user becomes an admin so there would be no "reminder" since the flag has been removed. Leaderboard (talk) 19:31, 15 August 2024 (UTC)
- Not automatically, a 'crat has to actually un-check the boxes. Doesn't always happen. Primefac (talk) 20:00, 15 August 2024 (UTC)
- I don't think that would be a problem, because my understanding is that the temp rights are removed when the user becomes an admin so there would be no "reminder" since the flag has been removed. Leaderboard (talk) 19:31, 15 August 2024 (UTC)
- The IPBE message could be customised for the flag that is to be removed (or excluded), and the confirmed flag can be excluded for reminding purposes. Leaderboard (talk) 19:30, 15 August 2024 (UTC)
- @Zzuuzz: and others, does this message make sense for you? Also: users can opt-out via a central page on Meta (example) - is that OK? (Note that the confirmed flag has been excluded) Leaderboard (talk) 17:13, 18 August 2024 (UTC)
- Looks good to me. voorts (talk/contributions) 21:27, 18 August 2024 (UTC)
- I would point out that trying to edit when logged-out is not a good method for determining if you need IPBE (unless you are competent at parsing block parameters). It would also be my preference not to have to list users on a page somewhere. -- zzuuzz (talk) 21:38, 18 August 2024 (UTC)
- @Zzuuzz: can you give an example on when you would give someone IPBE and not want them to be notified of expiry? As far as I'm aware, you do get an email when the right is granted, so I don't get the "some people don't even know they have it" part. Leaderboard (talk) 06:08, 19 August 2024 (UTC)
- I think you have to remember that most users are just occasionally writing about their favourite sports team, or breed of dog, or their local geography, etc, and don't really care about administrivia and how it's possible they can edit. I also suspect many users don't have email, and blue notifications, especially ones which appear trivial or incomprehensible, are easily ignored by many users. So it's sometimes the case that checkusers will hardblock whole ranges (or also just notice a hardblock) and then they'll grant a bunch of IPBE to users on the range so that no one notices any difference. The users didn't ask for it, and I do believe many don't notice or care about it. I'd rather not name specific recipients, but examples of people likely to get IPBE in this way are anyone on a Wikinger range, historically anyone in Ghana, and some people on some proxy ranges. It's also been granted in this way to people on individual IPs or common ranges such as T-Mobile, when the need arises. Notifying them about what has been performed behind the scenes is IMO just going to be confusing. It's not everyone; some I'm sure would appreciate the notification. -- zzuuzz (talk) 07:35, 19 August 2024 (UTC)
- @Zzuuzz: That's the tricky bit for me (as you say, "some I'm sure would appreciate the notification"). My opinion is that it's better if someone could help reword the message so that it captures the concerns you have. Having to check the logs is something I very much would rather not do since it would introduce additional complexity I doubt would be justified, and the reasoning for putting the opt-out on a central meta page is for scalability - the plan is for the bot to be global and I don't think it's reasonable for me to have to capture all wiki's local opt-out preferences (for example, there is no concept of exclusion-compliant bots on my homewiki). Does this make sense to you? OR I could just add ipbe to the list of flags the bot will ignore entirely if the community would rather prefer that. Leaderboard (talk) 07:51, 19 August 2024 (UTC)
- zzuuzz Ghana: did you throw out a random African country, or have we historically had issues with unintentional autoblocks for Ghanaian editors? I know this used to be a problem for Qatar, with all traffic running through a single IP address, but I don't remember any other countries with a comparable problem. Nyttend (talk) 07:53, 19 August 2024 (UTC)
- No, yes, Ghana. Things have eased recently with the retirement of proxy-bots, but for several years it was almost impossible to edit from Ghana without IPBE. Most of Ghana seems to go through about 2 IP ranges which are full of proxies and frequently blocked for this reason or another. Some other countries have approached the same level of proxy-blockage (eg Nigeria and Nepal) but none anywhere near as bad. Lots of people in Ghana have IPBE without any request or likely idea what it is. -- zzuuzz (talk) 08:17, 19 August 2024 (UTC)
- zzuuzz Ghana: did you throw out a random African country, or have we historically had issues with unintentional autoblocks for Ghanaian editors? I know this used to be a problem for Qatar, with all traffic running through a single IP address, but I don't remember any other countries with a comparable problem. Nyttend (talk) 07:53, 19 August 2024 (UTC)
- @Zzuuzz: That's the tricky bit for me (as you say, "some I'm sure would appreciate the notification"). My opinion is that it's better if someone could help reword the message so that it captures the concerns you have. Having to check the logs is something I very much would rather not do since it would introduce additional complexity I doubt would be justified, and the reasoning for putting the opt-out on a central meta page is for scalability - the plan is for the bot to be global and I don't think it's reasonable for me to have to capture all wiki's local opt-out preferences (for example, there is no concept of exclusion-compliant bots on my homewiki). Does this make sense to you? OR I could just add ipbe to the list of flags the bot will ignore entirely if the community would rather prefer that. Leaderboard (talk) 07:51, 19 August 2024 (UTC)
- I think you have to remember that most users are just occasionally writing about their favourite sports team, or breed of dog, or their local geography, etc, and don't really care about administrivia and how it's possible they can edit. I also suspect many users don't have email, and blue notifications, especially ones which appear trivial or incomprehensible, are easily ignored by many users. So it's sometimes the case that checkusers will hardblock whole ranges (or also just notice a hardblock) and then they'll grant a bunch of IPBE to users on the range so that no one notices any difference. The users didn't ask for it, and I do believe many don't notice or care about it. I'd rather not name specific recipients, but examples of people likely to get IPBE in this way are anyone on a Wikinger range, historically anyone in Ghana, and some people on some proxy ranges. It's also been granted in this way to people on individual IPs or common ranges such as T-Mobile, when the need arises. Notifying them about what has been performed behind the scenes is IMO just going to be confusing. It's not everyone; some I'm sure would appreciate the notification. -- zzuuzz (talk) 07:35, 19 August 2024 (UTC)
- @Zzuuzz: can you give an example on when you would give someone IPBE and not want them to be notified of expiry? As far as I'm aware, you do get an email when the right is granted, so I don't get the "some people don't even know they have it" part. Leaderboard (talk) 06:08, 19 August 2024 (UTC)
- Similarly, any temporary permissions that form part of the admin toolkit granted to a non-admin who has become an admin in the meantime. Thryduulf (talk) 19:18, 15 August 2024 (UTC)
- The bot is ready for local testing: Wikipedia:Bots/Requests for approval/Leaderbot. Leaderboard (talk) 09:20, 22 August 2024 (UTC)
DeletedContributions broken
[edit]If you're seeing strange things looking at deleted contributions today, the answer is that it's WP:THURSDAY. RoySmith (talk) 00:14, 16 August 2024 (UTC)
- @RoySmith: I'm still seeing "strange things" when I look at a user's deleted contributions. For example, I delete a page, I look at the deleted contributions of the author of the deleted page, and it doesn't show up. OTOH, I look at deleted contributions of other users and I see deleted contributions - whether they are all of them, no clue. I have great difficulty looking at Phabs. Can you summarize (1) what the status is, particularly whether anyone has gotten closer to diagnosing the problem; and (2) whether there is an ETA for fixing this? Thanks.--Bbb23 (talk) 15:20, 18 August 2024 (UTC)
- I only know as much as I can get from reading the phab ticket. If I understand the gerrit notes correctly, they've already got a fix, it's been tested, and merged back into the mainline code, so my guess is the fix will be deployed this Thursday. I expect @Pppery or @mszabo would be able to give you a better answer. RoySmith (talk) 15:46, 18 August 2024 (UTC)
- Yes, you understand correctly. If there's a really important need someone could backport the fix as early as Monday morning. * Pppery * it has begun... 15:48, 18 August 2024 (UTC)
- The fix has been backported now. WBrown (WMF) (talk) 12:23, 20 August 2024 (UTC)
- Yes, you understand correctly. If there's a really important need someone could backport the fix as early as Monday morning. * Pppery * it has begun... 15:48, 18 August 2024 (UTC)
- I only know as much as I can get from reading the phab ticket. If I understand the gerrit notes correctly, they've already got a fix, it's been tested, and merged back into the mainline code, so my guess is the fix will be deployed this Thursday. I expect @Pppery or @mszabo would be able to give you a better answer. RoySmith (talk) 15:46, 18 August 2024 (UTC)
Review of RfC close
[edit]The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
I am requesting a review of my RfC closure at RfC: Circumcision viewpoints. Prcc27 asked me to consider re-opening it, and I declined. Bon courage thinks it was a bad close and after discussion on my talk page, has indicated they believe the solution appears to be to ignore the close. So I am asking for a review of my closure. This is my initial response for my rationale for closing the existing discussion at the RfC. Thanks. Isaidnoway (talk) 09:49, 19 August 2024 (UTC)
My main concern is the willingness of Bon courage to ignore the process outlined in CLOSECHALLENGE. They knew the next step after the discussion on my talk page, was to bring a CLOSECHALLENGE here to AN. Instead, they had already edited the article to their preferred version, and then said "the solution appears to be to ignore the close and follow the WP:PAGs". And the question asked in the RfC is not the question as Bon courage describes it, and when the content was re-added to the article after the RfC closed, it was reliably sourced, and then two minutes later, it was immediately reverted by Bon courage. Do we allow editors to ignore CLOSECHALLENGE, ignore a RfC close, make a self-determination on how they think the RfC should have been closed and edit the article to their preferred version? If this is the community consensus, please let me know, and I won't close anymore RfCs. Thanks. Isaidnoway (talk) 20:43, 19 August 2024 (UTC)
Non-participants
[edit]- Yes, the position of the closer appears to be that WP:PAGs should not be considered by a closer unless they have been raised in the argument. However, since WP:CON is by definition "a process of compromise while following Wikipedia's policies and guidelines" relevant WP:PAGs need to be considered in determining consensus in a close, otherwise we'd have untenable situations like where (say) a small group of editors could agree to insert libel into Wikipedia, and a closer then saying that must be done "since nobody mentioned BLP". This is really a key difference between WP:CON and WP:LOCALCON. In this particular case the question was about some text in an article summary and whether it should/could be sourced and how it WP:SYNC'd with the detail article referenced. The issue in now moot since by doing a WP:SYNC anyway some equivalent text in included, apparently without objection.As a general rule, I think this trend of using RfCs to mandate text (and then finding sources) is not a desirable substitute for the normal editing process. Bon courage (talk) 10:48, 19 August 2024 (UTC)
- Is that what happened though? While the RFC didn't directly mention sources, in discussion the RfC on the circumcision page (Talk:Circumcision#Ethics in lead RfC) was mentioned as well as the Genital modification and mutilation page history [2]. Both locations seem to have several sources. Are any of the sources that supporters of the RfC wanted to use before your involvement, actually new or were they part of the circumcision RfC or already in the Genital modification and mutilation article or were used until removed? If it's the latter, then I don't see how you can claim RfC mandated text and sources were found later. Instead the RfC mandated text based on existing sources. I mean the RfC itself was structured poorly since people needed to go through either the edit history (which wasn't even directly linked) or check out the circumcision RfC etc to work out what sources were being used for the text. This might have reduced participant from uninvolved or less involved editors since those editors would see the text being proposed but need to hunt around to work out what sources allegedly support the text and so might not bother. So I'm by no means saying the RfC was perfect. But I'm unconvinced that the RfC was mandating text and then only finding sources, instead the sources were already there just not properly presented in the RfC. Nil Einne (talk) 08:50, 20 August 2024 (UTC)
- To put it a different way, the main difference between this RfC and a good one IMO were that RfC only had the proposed text but not the sources. The sources were elsewhere but not in the RfC itself. If it had the proposed text and the sources, this would IMO be much more likely a more normal completely fine RfC. In some cases there might be two (or more) different suggestions possibly with different wordings. That is something that should have been dealt with via BEFORE which I admit I'm not sure how well was done here. OTOH, in some cases it might simply be that one "side" feels this this text belongs with these sources and the other "side" feels the article is fine without that and so it is simple a dispute between include this text and its sources or don't. It does seem to me that at least before your involvement, the most were focused on either including that text and sources or not. Nil Einne (talk) 08:57, 20 August 2024 (UTC)
- The text is reasonable enough, as it turns out, but my concern about sources was that it seemed the tail was wagging the dog and they might not exist. The plan was apparently to use one particular source for this (doi:10.1353/ken.0.0279), but how one was meant to know that, beats me! You for example seem to think multiple-sources were in play. I've been operating a slimmed-down watchlist over much of summer so maybe missed some of the background to this which would help provide context? Agree a 'normal' RfC (proposing sourced text) would have raised no eyebrows. Bon courage (talk) 09:17, 20 August 2024 (UTC)
- (edit conflict) You're right that only one source was used initially but it seem Prcc27 felt this was enough. I'm not going to comment on whether it was but my main objection to your initial comment is you made it sound like what Prcc27 was doing was saying "we should have this text, I don't know what sources support it, but I'm sure we'll find some". Instead, it seems clear that what Prcc27 was doing was saying "we should have this text" which was earlier in the article with this one source supporting it. The latter part was unfortunately only implied in follow up discussion rather than directly presented in the RfC. So yes they failed to present the one source in the RfC which isn't a good thing. But they clearly had a source in mind since the text and source was in the article not long before the RfC started. I just don't see how there can be any dispute especially given the followup discussion within the RfC, that Prcc27's main desire was to return to the earlier version with the text and source (which was only a few days or so before the RfC started). So a poor RfC yeah, sure, but not one where the editor started out with a wording they wanted and felt they'd worry about sources later. I may have misunderstood, but my impression was Prcc27 was also saying if that one source isn't enough, there are additional sources in the circumcision RfC we could consider using. Again not ideal, even if you feel that one source is enough, it's IMO better to present the other sources which might be used in the RfC itself. OTOH since Prcc27 apparently felt that one source was enough, technically they could have just presented the RfC with the wording and that one source if they were fairly confident the community would agree. If others in the RfC suggested that one source wasn't enough, then it might be necessary to hunt for more sources hence why it's better to either present these additional sources from the getgo or at least try and have more discussion before the RfC to work out if that one source is enough. But it can be hard to work out if there will be objection to your single source or the problem might be you need more or better sourcing before you start an RfC depending on the circumstance. Nil Einne (talk) 09:41, 20 August 2024 (UTC)
- (edit conflict) Reading the RfC more carefully, it does seem the latter two editors were probably unaware of the existing sources which is unfortunate. However it seems unlikely the editor who started the RfC was unaware of the source they wanted to use, and I suspect the next one to comment was also aware. Ultimately all this seems to re-affirm my point. No question that the RfC was poorly structured since it didn't present the source to be used. But the point seems to have been to try restore recently removed text which did have one source which the editor felt was enough although they did link to another recent RfC on the related page where more sources were available if needed. The RfC should have been better structured so editors could easily see which source was suggest, and offer objections e.g. this one source isn't enough or is too old etc. I think more before might have helped especially in establishing whether there might be objection to that one source. OTOH, I'm also cognisant that it's hardly uncommon that editor can ask for comments and receive nothing useful until an RfC happens. But ultimately it doesn't seem to me that the RfC was trying to mandate text and then work out which source/s support it; instead it was just a poorly structured RfC where the one source to be used wasn't properly presented in the RfC. Nil Einne (talk) 09:20, 20 August 2024 (UTC)
- I agree, now, that in effect a reversion to a prior state was being asked for. But it didn't look like that at the time, with just text and no source presented. Hence I got the wrong end of the stick. Bon courage (talk) 11:20, 20 August 2024 (UTC)
- The text is reasonable enough, as it turns out, but my concern about sources was that it seemed the tail was wagging the dog and they might not exist. The plan was apparently to use one particular source for this (doi:10.1353/ken.0.0279), but how one was meant to know that, beats me! You for example seem to think multiple-sources were in play. I've been operating a slimmed-down watchlist over much of summer so maybe missed some of the background to this which would help provide context? Agree a 'normal' RfC (proposing sourced text) would have raised no eyebrows. Bon courage (talk) 09:17, 20 August 2024 (UTC)
- To put it a different way, the main difference between this RfC and a good one IMO were that RfC only had the proposed text but not the sources. The sources were elsewhere but not in the RfC itself. If it had the proposed text and the sources, this would IMO be much more likely a more normal completely fine RfC. In some cases there might be two (or more) different suggestions possibly with different wordings. That is something that should have been dealt with via BEFORE which I admit I'm not sure how well was done here. OTOH, in some cases it might simply be that one "side" feels this this text belongs with these sources and the other "side" feels the article is fine without that and so it is simple a dispute between include this text and its sources or don't. It does seem to me that at least before your involvement, the most were focused on either including that text and sources or not. Nil Einne (talk) 08:57, 20 August 2024 (UTC)
- Is that what happened though? While the RFC didn't directly mention sources, in discussion the RfC on the circumcision page (Talk:Circumcision#Ethics in lead RfC) was mentioned as well as the Genital modification and mutilation page history [2]. Both locations seem to have several sources. Are any of the sources that supporters of the RfC wanted to use before your involvement, actually new or were they part of the circumcision RfC or already in the Genital modification and mutilation article or were used until removed? If it's the latter, then I don't see how you can claim RfC mandated text and sources were found later. Instead the RfC mandated text based on existing sources. I mean the RfC itself was structured poorly since people needed to go through either the edit history (which wasn't even directly linked) or check out the circumcision RfC etc to work out what sources were being used for the text. This might have reduced participant from uninvolved or less involved editors since those editors would see the text being proposed but need to hunt around to work out what sources allegedly support the text and so might not bother. So I'm by no means saying the RfC was perfect. But I'm unconvinced that the RfC was mandating text and then only finding sources, instead the sources were already there just not properly presented in the RfC. Nil Einne (talk) 08:50, 20 August 2024 (UTC)
An RfC with four participants, three of whom said "yes", is being challenged, and I cannot tell on what basis. Bon courage has brought up a ton of paggies (WP:LOCALCON, WP:SYNC, WP:SS, WP:ARBGG etc)... but not given an explanation of what any of this stuff has to do with the RfC. It seems pretty simple to me. Here is a quick recap of the RfC: it's so short I can just put the entire thing here for reference.
Entire four-comment RfC
|
---|
There is a consensus to include the viewpoints of circumcision proponents and opponents in the article with the proposed wording. An editor also noted that reliable sources should be used to support the wording which is consistent with our policies and guidelines. Isaidnoway (talk) 17:37, 18 August 2024 (UTC)
Should the viewpoints of circumcision proponents and opponents be included in this article?
Prcc27 (talk) 17:53, 21 July 2024 (UTC)
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.
|
It's really straightforward -- the RfC asked if the thing should be included, four people responded, three said that the thing should be included, the closer said that there was consensus for the thing to be included. Now one (1) editor has decided that this is all a big misunderstanding and the consensus is actually to have the article say the opposite? It's true that a four-participant RfC is not some kind of invincible ironclad consensus, but for Pete's sake, what possible objection could there be to this closure? This just feels like an editor not liking the RfC close and deciding to throw random WP:UPPERCASE at the wall to see what sticks. jp×g🗯️ 02:05, 20 August 2024 (UTC)
Looking at the page in question, it looks like Bon courage just keeps on editing the article to say his own version, and then going to the talk page to demand that other people provide sources proving it wrong or else he will just keep adding it -- surely we have all been around long enough to know this is not how WP:BURDEN works. This feels somewhat tendentious to me. jp×g🗯️ 02:20, 20 August 2024 (UTC)
- The issue is that that is a summary section, meant to be summarizing the thing it points to. It shouldn't say "the opposite" of what the RfC proposed, it should just mirror the thing it's summarizing (which is not "the opposite" as it happens). The "random uppercase" things are WP:PAGs, and kind of matter. You can't have an RfC decide that, no matter what article A says, its summary must be fixed without regard to that; the WP:PAGs tell us that such material should be in WP:SYNC. My final edit is not really "my own version" but just excerpts from the articles-being-summarized, which as far as I know I did not write. Bon courage (talk) 02:27, 20 August 2024 (UTC)
- Withdraw
- It seems evident from subsequent editing that my intervention here is hindering rather than helping evolution of this article, so with apologies to all I shall put my tail between my legs and withdraw my objection to this RfC/close assuming that sources are used in such a way that WP:V is respected, and hoping the WP:SYNCing shall be improved as the article evolves. Bon courage (talk) 05:40, 20 August 2024 (UTC)
Participants
[edit]I originally supported a re-open of the RfC, because I felt BonCourage’s edits went against the RfC and their concerns were not brought up there either. And because it was still under 30 days since it started. However, I think the sync is sufficient, as long as the viewpoints of proponents and opponents are articulated in a neutral manner. Re-opening an RfC may no longer be needed. For the record, I think the closer closed the RfC correctly, based on the discussion made at the RfC. Prcc27 (talk) 17:10, 19 August 2024 (UTC)
- I also am concerned with Bon Courage’s actions. The wording I proposed at the RfC was actually a longstanding paragraph in the article. It had been there for several years (albeit the wording had been tweaked a little bit over the years). And it was reliably sourced as Isaidnoway noted. Bon Courage’s behavior does seem to be an example of a user taking ownership of an article, and unilaterally overturning an RfC. While I am not necessarily against the sync, I would like for an admin to determine how the RfC should be enforced. And maybe even give Bon Courage a formal warning for their disruptive behavior. Prcc27 (talk) 22:57, 19 August 2024 (UTC)
- The source was not part of the RfC, and a 2009 primary source is not great. You seemed to agree with this by then using a 'more recent' 2015 source.[4]. The only trouble then is that WP:V was not respected, and in fact the source you selected said pretty much the opposite of the text cited to it. Wikipedia simply cannot allow a WP:LOCALCON RfC to wave away the need to respect core policies like WP:V. This exemplifies the problem with having a RfC designed to 'enforce' text with the hope that sourcing can be found to support it, Bon courage (talk) 23:55, 19 August 2024 (UTC)
- This is just more obfuscation. The RfC was not
designed to 'enforce' text with the hope that sourcing can be found to support it
. The RfC was about re-adding the sourced text which had been in the article for at least the last ten years, and had been recently removed. This reply in the RfC, makes that abundantly clear; the RfC was about re-adding the sourced text which had a long standing consensus. In fact, the sourced text was in the article, when you edited the article in December 2019. So for ten years, five years, the sourced text had been in the article and you didn't complain. It was only when the sourced text was re-added after the RfC ended, and there was consensus to re-add it, you swooped in two minutes later and unilaterally decided the consensus from the RfC didn't matter. Isaidnoway (talk) 04:24, 20 August 2024 (UTC)- This is just wrong. As anybody can see the RfC has no "sourced text" and said nothing about "re-adding" text but was presented with no context and no source. How are editors meant to know about an old discussion on a Talk page archive? And how am I expected to recall some text in an article I edited 5 years ago? And 10 years ago a 2009 source would be a lot less dated than it is today. As to "enforcement" the OP of this section is talking about "how the RfC should be enforced" just above. PMID:25674955 does not support the RfC text and WP:V cannot just be ignored. Bon courage (talk) 04:48, 20 August 2024 (UTC)
- This is just more obfuscation. The RfC was not
- The source was not part of the RfC, and a 2009 primary source is not great. You seemed to agree with this by then using a 'more recent' 2015 source.[4]. The only trouble then is that WP:V was not respected, and in fact the source you selected said pretty much the opposite of the text cited to it. Wikipedia simply cannot allow a WP:LOCALCON RfC to wave away the need to respect core policies like WP:V. This exemplifies the problem with having a RfC designed to 'enforce' text with the hope that sourcing can be found to support it, Bon courage (talk) 23:55, 19 August 2024 (UTC)
The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
7 months back, admin Firefangledfeathers replaced my existing Rajput topic ban with a broader ban (that includes editing in India, Pakistan and Afghanistan related topics) after a discussion here. The primary reason cited for sanctions was the violation of existing Rajput Tban.
For last seven months, I edited pages which are unrelated to India, Pakistan and Afghanistan. I made 325+ edits including creation of 6 articles. My editing in the duration was quite peaceful and I didn't receive further sanctions. The more I edited, more I learnt further about Wikipedia guidelines. Today, I find myself much more competent in editing Wikipedia than before. I feel that I can constructively contribute in the areas to which I don't have access presently. Yesterday, I appealed to the banning admin's talk page but he advised me to appeal at WP:AN. So, I wish to appeal my TBAN here. I assure our community of following :
- I will keep adhering to my one-account restriction as I have been doing for last 7 months.
- Before adding any content, I will give more care to WP:DUE.
- I will try my level best to avoid edit warring. In accordance with the WP:BRD, I will discuss the matter first with fellow editors and take them into trust before making edits which can invite contentions.
Regards, Dympies (talk) 17:30, 19 August 2024 (UTC)
Comments by uninvolved editors (Dympies)
[edit]Per WP:CTOP, this appeal will succeed if "a clear consensus of uninvolved editors" supports it.
- Comment I'd be willing to grant another chance, but I'm hoping to hear more from editors who have worked with this user first. Also @Dympies: You've mentioned that you've made a number of good content contributions as well as created several articles. Are there any that you're especially proud of and would like us to take a look at? Being able to show off specific work that you've done is something that can give other editors confidence that you've put past mistakes behind you. The WordsmithTalk to me 19:50, 19 August 2024 (UTC)
- @ The Wordsmith: So far, since the topic ban, I have created Secularism in Taiwan, Secularism in Tajikistan, List of Afrikaners, Secularism in Azerbaijan, Tecno Pova 6 Pro, and Junichiro Hironaka. All of these articles can be expanded further. For example Junichiro Hironaka's entire episode with former Nissan's CEO Carlos Ghosn has to be mentioned yet.[5] Dympies (talk) 05:54, 20 August 2024 (UTC)
- Support per WP:ROPE as I don't see any issues with their recent contributions. They appear to be editing constructively in other areas. Ratnahastin (talk) 05:28, 20 August 2024 (UTC)
- Support There's a lot of signs that the editor is building productively. No issues outside the designated areas. Ahri Boy (talk) 12:59, 21 August 2024 (UTC)
- Support. Dympies has been editing constructively. voorts (talk/contributions) 19:53, 21 August 2024 (UTC)
Comments by involved editors (Dympies)
[edit]A quick procedural note: though I was the enforcing admin, the present TBAN was enacted via a consensus of admins at AE which included @Black Kite, The Wordsmith, and Firefly, with Abecedare expressing acceptance of the option. On the merits: I am neutral on this appeal, leaning toward accepting it based on a cursory review of the contributions since the TBAN was broadened. Firefangledfeathers (talk / contribs) 18:50, 19 August 2024 (UTC)
Disruptive unregistered user
[edit]User:2A00:8A60:C010:1:0:0:1:1016 has variously described me as a "mathematical crank" (in Talk:Axiomatic system (logic)) and "intellectually blind" (in their own talk page) for what they vaguely describe as "adding a bunch of false and misleading claims" to an article, but which I describe rather as replacing the article's tons of unsourced, unverifiable statements with content supported by, and sourced to, WP:RS. Thiagovscoelho (talk) 13:47, 20 August 2024 (UTC)
- /64 blocked by Isabelle Belato. -- Malcolmxl5 (talk) 23:08, 20 August 2024 (UTC)
- The IP seems to have reiterated the personal attack at their talk page, and I suspect that the IP 95.223.44.235, who has been talking at Talk:Hilbert_system, is a sockpuppet. (Investigation opened here.) Thiagovscoelho (talk) 20:41, 24 August 2024 (UTC)
User edit warring
[edit]The user @Bgsu98 keeps reverting edits on The Amazing Race Canada 10 stating that the episode name is not true when it says that on the show's website. They also put a talk page message on my page about me making harrasments to them abut living people (yes idk what that means either). Please block them for at least 24 hours (and hopefully more) as because they have a vendetta against me and as soon as I edit any genre article, 2 minutes later they take it down. Thank you. Jd101991 (talk) 15:44, 21 August 2024 (UTC)
- Okay, this user is posting unsourced spoiler information about the results of a reality television show which have not yet aired. Without a reliable source, that information is inappropriate. If someone could please instill in them the concept that fan sites and related spoiler sites are in fact not reliable sources for Wikipedia, that would be awesome. Bgsu98 (Talk) 15:48, 21 August 2024 (UTC)
- @Jd101991, you should not add speculation about the results of an unaired episode, even in hidden text. Schazjmd (talk) 15:49, 21 August 2024 (UTC)
- so then can you let me know why @Bgsu98 decided not to remove the province new brunswick in the first paragraph of the article? Of course i didn't write it, so they didn't remove it. If i put it there, they would've taken it down. Jd101991 (talk) 15:51, 21 August 2024 (UTC)
- This is, I just noticed, the wrong noticeboard. Bgsu98 (Talk) 15:52, 21 August 2024 (UTC)
- This isn't the right place to report edit warring. Please visit WP:ANEW for instructions/more info. Kcmastrpc (talk) 15:51, 21 August 2024 (UTC)
- I've blocked the OP for two weeks.--Bbb23 (talk) 15:55, 21 August 2024 (UTC)
- Thank you. Bgsu98 (Talk) 16:51, 21 August 2024 (UTC)
The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
I'm not saying it can't be there, but this really seems like a tawdry and unnecessary hook and I think it would be much wiser NOT to have this on the main page:
- "... that some LGBT people wear shorter nails on their middle and index fingers to allow for easier manual sex and to express a queer identity?"
Thoughts? Buffs (talk) 02:28, 22 August 2024 (UTC)
- To be clear, I'm not advocating for the article's removal. Buffs (talk) 02:39, 22 August 2024 (UTC)
- No changes. Just keep it retained. Ahri Boy (talk) 03:07, 22 August 2024 (UTC)
- WP:ERRORS is that way. And as hooks referencing human sexuality go, this is as far from "tawdry" as possible—an academically-worded description of the article's central topic. -- Tamzin[cetacean needed] (they|xe) 04:12, 22 August 2024 (UTC)
- I'd support a more children-friendly main page, but it's probably a matter for the pump. Levivich (talk) 05:02, 22 August 2024 (UTC)
- If we wanted to protect children from information, we should start with harmful things like war and violence, not lesbian sex. —Kusma (talk) 07:41, 22 August 2024 (UTC)
- I'm not looking to "protect children from information" and Levivich didn't make such an assertion either. Information about wars and violence is generally not harmful, but that depends on the graphic nature of descriptions or pictures. Information about sex is titillating, but generally considered a cheap/low-brow way to get attention and inappropriate in academic literature. I think we could do better as a community than cater to basal human instincts. But that doesn't mean my opinion has to carry the day. In this case it doesn't. Buffs (talk) 18:12, 22 August 2024 (UTC)
- If we wanted to protect children from information, we should start with harmful things like war and violence, not lesbian sex. —Kusma (talk) 07:41, 22 August 2024 (UTC)
- You linking to WP:NOTCENSORED while complaining about this hook being on the front page is very contradictory. We feature wars, murders, etc. on the front page frequently but this is where you draw the line? Also as Tamzin points out, this is far from "tawdry". ♠JCW555 (talk)♠ 05:07, 22 August 2024 (UTC)
- "DYK has issues with tasteless or clickbaiting hooks" Fram said it, not me. Clearly my opinion isn't in the majority on this one. I'll consider it resolved. Buffs (talk) 18:04, 22 August 2024 (UTC)
- DYK has issues with tasteless or clickbaiting hooks, but this seems to be a hook which is directly related to the topic. If you had complained about another original hookhere, which somehow got reviewed and promoted into the preparation areas before being changed, you would have had a good point. But the above, nah. Fram (talk) 07:43, 22 August 2024 (UTC)
Close review: Nikola Tesla's birthplace RfC
[edit]The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
I am requesting community review of my closure of an RFC on the specifics of the birthplace of Nikola Tesla (closing diff), which was recently challenged on my talk page by the IP address 93.141.181.3, who believes that the close did not sufficiently assess consensus (their original comments, my reply). As an IP, they cannot edit this page, so I am starting it on their behalf. ~~ AirshipJungleman29 (talk) 15:15, 22 August 2024 (UTC)
Involved
[edit]I was the one who opened the discussion. I accept the closure. I accept that RfC was a mess. I accept that I'm solely responsible for that from start to finish. Yes my RfC wasn't neutral nor brief, often incorrect, initially proposing outright plagiarism, and following none of WP:WRFC. I admit that I have then proceeded to spend nearly 8,500 words bludgeoning the discussion. Everything was correctly closed. I would just ask for one thing. ~~ AirshipJungleman29, can you just explicitly write the consensus on the other question editors have voted upon. Something like "The consensus on the 1st question is NO. The consensus on the second question is NO". Trimpops2 (talk) 16:48, 22 August 2024 (UTC)
- I randomly came across the RFC and commented there, all I'll say here is that the close doesn't surprise me. -- LCU ActivelyDisinterested «@» °∆t° 16:50, 22 August 2024 (UTC)
- Thank you. You are one of the major participants. I'm glad we agree. Only one IP has complaints, but he didn't contribute more than 0.1% so I don't see why this shouldn't be promptly closed. Trimpops2 (talk) 17:12, 22 August 2024 (UTC)
- Sure, I'll do that if others agree. ~~ AirshipJungleman29 (talk) 17:46, 22 August 2024 (UTC)
I thought the close was carefully considered and judged. The conclusion of "no consensus" effectively keeps the longstanding status quo, which has been stable for six years. The IP here is very likely block evasion by User:Bilseric who has been consistently disrupting the process while using IPs from Croatia. I am loathe to allow a blocked editor to demand a review, robbing the community of even more of their time. Binksternet (talk) 18:44, 22 August 2024 (UTC)
- Yes, I agree with Binksternet. But, ~~ AirshipJungleman29, can you also write in the consensus on the 1st question? Trimpops2 (talk) 18:54, 22 August 2024 (UTC)
- Another admin needs to seriously consider blocking this user Trimpops2, because they've first endlessly bludgeoned this discussion, despite numerous warnings, advocating for one weird POV, and are now posturing completely differently, for another weird POV, as if it was all some sort of a bizarre online game. This is as clear a case of not actually being here to build an encyclopedia as it gets. --Joy (talk) 22:01, 22 August 2024 (UTC)
because they've first endlessly bludgeoned this discussion
Yes, ~~ AirshipJungleman29 said that in the closure. I have already admitted my wrongdoing there.advocating for one weird POV
It was inapropriate to ignore numerous users who have tried to explain to me that Tesla has no connection to Croatia. My problem is that I was under influence of Croatian propaganda and I was confused by the statement that Tesla was born in Smiljan , present-day Croatia. I though that Tesla was born in Austrian Croatia, but as Binksternet has said, sourcesplace Tesla in Croatia only because that's what it is called today
. Tesla has no relation to Austrain Croatia. I didn't know that. Now when the consensus has been determined, I have accepted it. I admit it was a weird POV and I appologize.and are now posturing completely differently
I'm just agreeing with consensus and comments other editos have made in their responses to me.for another weird POV
It's not POV, it's the consensus. My problem here is that I found the article text confusing, but I have already accepted that article needs no change. Binksternet has provided an explanation why Croatia is mentione, because the sourcesplace Tesla in Croatia only because that's what it is called today
. Trimpops2 (talk) 22:50, 22 August 2024 (UTC)- Since you keep pinging me, can I inquire as to what inspired your sudden change of heart? ~~ AirshipJungleman29 (talk) 22:53, 22 August 2024 (UTC)
- It isn't sudden. I never intended to contest your closure. We aren't enemies here. At some point I realized that I need to listen what other longstanding editors are saying. You are completely uninvolved editor and your closure is against my stand. Let's see what other longstanding editors have said to me. Joy has just now said that I was
advocating for one weird POV
. He is Croatian and longstanding editor and admin. I'm sorry Joy. I accept that me pushing that Tesla was born in Austrian Croatia is a weird POV. Pincrete said that Tesla wasn'tborn in any variant of a political Croatia
. Binksternet, said thatMost of the literature about Tesla and his family de-emphasizes Croatia and instead underlines his Serbian heritage. So the idea of pushing more "Croatia" has no merit.
and Tesla biographiesplace Tesla in Croatia only because that's what it is called today. Croatian culture played very little role in Tesla's upbringing.
. Sadko, said thatTesla's relation to Croatia in any way, shape or form is almost non-existing
. Jalapeño is also Croatian as Joy, and he also voted against. I have to accept that both Croatian and Serbian editors are agreeing about this contested issue. This is good for Wikipedia. People have claimed for a long time that this article is a battleground between Croatian and Serbian editors. Sadko is Serbian. We have both Croatian and Serbian editors agree. I see that as positive. It's not an issue between Croats and Serbs. After your closure, and after I saw how many editors have tried to explain to me that I'm the own pushing Croatian propaganda. Chetvorno from the begginging have said that, but I didn't listen. Look how many editors tried to explain it to me. At some point I needed to accept that I'm the only one in the wrong here. I really don't contest your closure. I never planned to. There is one more thing , I did one wrongdoing today. I need to admitt that as well. I started a discussion to remove mentions of present-day Croatia from the article. I though that it might confuse readers like it confused me. I didn't think others who have disagreed with me in the RfC would complain now when I have accepted their stand. I already admitted in the discussion that I was wrong. The text can stand. It's only I that find it confusing , but as Binksternet explained, present-day Croatia is mentioned only because sourcesplace Tesla in Croatia only because that's what it is called today.
. As long as that is clear to the readers I don't have problems with mentioning present-day Croatia. As long as it's clear that Tesla has no connection to Austrian Croatia. Trimpops2 (talk) 23:22, 22 August 2024 (UTC)- I don't want to relitigate this, but nb that I said
wasn't born in any variant of a political Croatia
. Where he was born may well have/have had claims to have been culturally/historically Croatian, I was reliant on sources presented. I would also have said that he was born in Croatian Austria, rather than the other way round as you have it, since Austria was the ruling power. But mainly my reasoning was that the simplest/clearest way was simply to say "born in the (Croatian) Military Frontier" and leave it to interested readers to 'deconstruct' that anomalous entity if they wished to do so. Pincrete (talk) 05:16, 23 August 2024 (UTC)- Yes, thank you. I can now agree. Tesla wasn't borin in any variant of political Croatia. You have correctly pointed that out, I'm sorry I didn't listed to your arguments.
may well have/have had claims to have been culturally/historically Croatian
. This wasn't the topic that we discussed , but Binksternet and Sadko were very kind to explain thatTesla's relation to Croatia in any way, shape or form is almost non-existing
. I have also accepted that.I would also have said that he was born in Croatian Austria
Maybe there's some misunderstanding here. He wasn't born in Austrian Croatia (that is Kingdom of Croatia at that time). This is the consensus and, as Joy have correctly characterized it, weird POV coming only from my side, and you have in the next sentece said MF which is something completely unrelated to Austrian Croatia, as you have correctly explained in the RfC discussion. But putting aside all this, Pincrete, can you agree we can close this review? Trimpops2 (talk) 09:10, 23 August 2024 (UTC)- I don't have any reason to either agree or disagree. I wasn't even aware that there was a review until 'named'. Pincrete (talk) 10:37, 23 August 2024 (UTC)
- Yes, thank you. I can now agree. Tesla wasn't borin in any variant of political Croatia. You have correctly pointed that out, I'm sorry I didn't listed to your arguments.
- I don't want to relitigate this, but nb that I said
- Joy, if you want to block me, I really can't complain to much. Everything you said is true. I have been pushing a weird Croatian propaganda that Tesla was born in Croatia. I'm sorry I didn't listed to you and others who have tried to explain to me that Tesla has no connection to Croatia. If you start a report I will admit my wrongdoing there. At this point maybe it's time for me to bear consequences of POV pushing. Trimpops2 (talk) 23:31, 22 August 2024 (UTC)
- Again, no, you're distorting the argument into an argument ad absurdum. Please take a breather, because this is utterly pointless. --Joy (talk) 07:07, 23 August 2024 (UTC)
- I really don't have any objections to close this review. I have admitted I have been wrong and pushing weird POV, as you stated. I really don't know what else to do, so you would be satisfied. Can we just close this review and be done with it? I don't intend to ever argue that Tesla was born in Croatia and if someone comes to the discussion with such a claim, I will point out the consensus and explain that
Most of the literature about Tesla and his family de-emphasizes Croatia and instead underlines his Serbian heritage. So the idea of pushing more "Croatia" has no merit.
Trimpops2 (talk) 09:25, 23 August 2024 (UTC)
- I really don't have any objections to close this review. I have admitted I have been wrong and pushing weird POV, as you stated. I really don't know what else to do, so you would be satisfied. Can we just close this review and be done with it? I don't intend to ever argue that Tesla was born in Croatia and if someone comes to the discussion with such a claim, I will point out the consensus and explain that
- Again, no, you're distorting the argument into an argument ad absurdum. Please take a breather, because this is utterly pointless. --Joy (talk) 07:07, 23 August 2024 (UTC)
- It isn't sudden. I never intended to contest your closure. We aren't enemies here. At some point I realized that I need to listen what other longstanding editors are saying. You are completely uninvolved editor and your closure is against my stand. Let's see what other longstanding editors have said to me. Joy has just now said that I was
- Since you keep pinging me, can I inquire as to what inspired your sudden change of heart? ~~ AirshipJungleman29 (talk) 22:53, 22 August 2024 (UTC)
- Another admin needs to seriously consider blocking this user Trimpops2, because they've first endlessly bludgeoned this discussion, despite numerous warnings, advocating for one weird POV, and are now posturing completely differently, for another weird POV, as if it was all some sort of a bizarre online game. This is as clear a case of not actually being here to build an encyclopedia as it gets. --Joy (talk) 22:01, 22 August 2024 (UTC)
I apologize. I was brainwashed by propaganda in my own country. I can now accept that was the case and what others have stated in the discussion, that Tesla wasn't neither born or has any relation to Croatia. I'm sorry, I wasted all your time. It was hard to accept that I could be brainwashed. Wikipedia helped. Thank you for that. I can agree with the closure and I don't think this review is necessary. Trimpops2 (talk) 20:21, 22 August 2024 (UTC)
- I think ~~ AirshipJungleman29's close was well judged and absolutely correct. I have been an editor for about 10 years on Nikola Tesla and participated in several long RfCs on this single insignificant sentence about Tesla's nationality. I have never on WP seen the degree of POV pushing and nationalist extremism displayed by editors on this page. This mess of an RfC was typical.
- I have to say I find Trimpops2's 180° change of opinion above suspicious. After initiating this whole RfC and tendentiously pushing the Croatian POV and haranguing every opposing editor with walls of text, then when he loses, instantly changing his opinion and claiming to be "brainwashed" --- it really looks like a salvage operation to mitigate sanctions against him. At the least, his actions during this RfC indicate he is not able to regard this subject with a NPOV, and I think a topic ban should be considered. --ChetvornoTALK 08:56, 23 August 2024 (UTC)
- I see many of you think I should be banned. If you open a report, I will admit I have been POV pushing nationalistic propaganda. There's simply no avoiding that. Even the closing editor has called that out. Binksternet was very correct when he said on the talk page that my Croatian nationality has to be taken into consideration when determining consensus. I was offended, but now I see that was the right approach. We always need to take into consideration someone's nationality because they can be brainwashed as I was, and don't even realize. Even before Binksternet , you have correctly pointed out that I'm pushing nationalistic content, I should have listen to you, but now it's too late. Trimpops2 (talk) 09:21, 23 August 2024 (UTC)
- But, thank you for noticing 180 degree shift from what you and others have characterized as "weird POV" and "tendentiously pushing Croatian POV". I'm sorry it's suspicious, but at least I have done the shift and admitted that me pushing Tesla being born in Croatia is nothing but Croatian propaganda. Can we at least accept that we agree on that? Trimpops2 (talk) 09:33, 23 August 2024 (UTC)
Joy, Chetvorno, Binksternet you are calling for my ban. Would you like that I open a report against myself? I really am ashemed of POV pushing nationalistic propaganda and ignoring you all when you tried to explain to me. All 3 of you are editors with 10+ years on Wikipedia. I really can't ignore that 3 of such longstanding editos think that my actions are inexcusable and that I should be banned. If any of you 3 confirms I'll procede and create a report against myself. Trimpops2 (talk) 09:45, 23 August 2024 (UTC)
- This is just unfair. You are calling for my block and when I offer to create a report against myself, you ignore it. I couldn't have been more objective. I haven't challanged the consensus. I have accepted the result that Tesla wasn't born in 19th century Croatia. I have admitted my wrongdoing for pushing, as Joy called it, that weird POV. I don't think anyone ever has offered to create a report against themselves. I don't know what more I can do. At this point, if you want to create a report, please do, I won't do it myself. I will admit everything and let uninvolved editos decide whether I should be forever banned from Wikipedia. Trimpops2 (talk) 08:51, 24 August 2024 (UTC)
I would like this addressed. Thank you. I would like to point out that this review didn't address a single point of complaint. Several were made and not a single editor has addresed. Everyone just says I agree, but this isn't a proper way to have a review. Points should be addressed. We can't just say, yes I agree and neglect all the points. I will repeat what others have said in my own words. I hope that those points will be addressed in this closure.
The closure is improper. It states some very questinable things from the standpoint of objectivity. It states some claims which are easily proven as false. Most importantly, it provides zero explanation how the consensus was determined in the regard of addressing how the sources and various points in the RfC were considered when determining the consensus. It also has some very questionable actions by the closing editor which lack objectivity. The closing editor in the first part of the closing statement lists all things wrong with the RfC intro and with actions of various editors in the discussion. I'll circle back to that,because I wan't to address the most important thing. In the second paragraph it summerizes what the RfC is asking. Here we have one minor complaint. The closing admin claims that he had to sumerize the RfC questions which isn't true. Those are clearly stated. In the last paragraph the consensus is provided as "no consensus". The problem here is , and this can't be argues whether it is here or there as some other points later on could be argued. The problem is that the closing editor just says that there is no consensus. No sources were addressed, no points from RfC were addressed. Absolutely no explanation at all. The only thing that is said is that the RfC was ill-formed, which isn't correct, as I'll argue later and that he had difficulties because of POV pushing (here it was correctly pointed out that the responsibility of the closing editor is to sort out objective points vs POV pushing). The problem here is bigger, because this was pointed to the closing editor several times, and he still hasn't addressed this nor provided any explanation on how the sources and points were considered. This is still the main problem with this closure as no one yet has provided that explanation. We can't just close RfCs with "no consensus" explanation and refuse to provide explanation on points and sources.
Let's circle back to first paragraph. Several claims there are exaggerated to the point of being false. Several points are completely false.
Regarding whether RfC was brief. Guidelines say Outside of exceptional circumstances, the RfC question should not be longer than a few sentences.. The RfC isn't out of that boundaries. In the first sentence is mentions past discussion. In the sencond it mentiones the present article text that is pusposed to be changed. It then quotes 2 sources and it asks 2 questions. That's 6 senteces in total. This isn't outside the scope to call it "not brief". Certainly nothing to complain about and call it "not brief" to the point of being disruptive to the RfC discussion. Nobody actually from all editors in the discussion has complained it isn't brief. This was done only by the closing editor. It's more subjective whether 6 or 4 senteces would be the definition of "few", but as I said , nothing to complain about.
Regarding neutrality. The closing editor didn't provide any explanation in the closure to why the RfC isn't neutral. This isn't correct as this is a strong statement to make. When asked, he provided an example of how the RfC should have been formulated, which is exactly the same as the 2nd question of this RfC. Both his example and the RfC 2nd question perfectly follow the example from guiedelines Should the sentence [quote sentence here, with citations] be included in the History section of the article?. He was asked several times to explain how his sentence is neutral, but the one from RfC isn't. He still didn't address that. I think this is completely false to claim that RfC isn't neutral with such argument.
Claiming that RfC is often incorrect is exaggregation. It failed to mention that there was another previous discussion, but that was quickly corrected in the discussion. And yes, sources were known before. This were honest mistakes and swiftly corrected by other editors in the discussion. Nothing major that could be characterized as "often" and nothing what would swey the result of the RfC.
The closing editor claimed that there isn't a single bit of WP:WRFC that was followd. Here we have a major problem. We was challanged on that and he doubled down, and repreated that there really isn't a singe bit of WP:WRFC that was followd. This just lacks objectivity. I think WP:WRFC was followed, but since the editor dug himself into the claim that a single bit wasn't followed I will mention only this. The 2nd question is exactly of the format as suggested by guidelines Should the sentence [quote sentence here, with citations] be included in the History section of the article?. And All other things being equal, choose the question with the smallest number of possible answers. this was followed. Questions are of yes/no type. This is something we can't argue about whether it is there or not. This quidelines are proveably followed. This is just tip of the iceberg. Many others if not all of them were followed, and to make such a claim and dig into it, to claim that not a singel was followed, just shows the lack of objectivity.
The closing editor claimed sources were vaguely mentioned when asked about it he again dig himself into a strange statement that no-one...actually discussed them.. This is completely false as seem from the discussion. User ActivelyDisinterested had extensively discussed sources with Trimpops2 and IP 77. Others have also discussed sources. To claim that no one discussed them shows the lack of objectivity.95.168.116.29 (talk) 16:25, 24 August 2024 (UTC)
- All of these complaints were addressed on my talk page. Before whichever Croatian IPs (there sure seem to be a lot about) next pop up, perhaps they can read that? Or perhaps they can join this interesting discussion. ~~ AirshipJungleman29 (talk) 18:57, 24 August 2024 (UTC)
- But this simply isn't true that everything was answered. For instance You didn't explain the claim that not a single wp wrfc was followed. You said to go ahead any find any. And now when I have found, you say it's answered. Here agin a single exaple for your claim that everything was answered. Other things aren't answered as well. It isn't true that everything is answered 95.168.107.28 (talk) 19:35, 24 August 2024 (UTC)
- Haha. The Ip just said on my talk page that this is just like Monty Python The Argument Skit [6]. That's so funny. May I suggest a formal mediation on whether he has answered the question or not? :) "You can't just say no it isn't. Yes it is." This is so funny. Trimpops2 (talk) 19:50, 24 August 2024 (UTC)
- But he really didn't answer. What can I now do? How about you point where you have answered it? 95.168.107.28 (talk) 19:54, 24 August 2024 (UTC)
- I see he didn't. Now, I'm interested in how this will end. Trimpops2 (talk) 19:57, 24 August 2024 (UTC)
- But he really didn't answer. What can I now do? How about you point where you have answered it? 95.168.107.28 (talk) 19:54, 24 August 2024 (UTC)
- Oh, I see. You're arguing that if you conveniently forget about one of the RFC questions, you can argue that it was phrased in the simplest way possible. Fantastic argument. Yeah, I think I'm done assuming good faith here. Bye. ~~ AirshipJungleman29 (talk) 20:12, 24 August 2024 (UTC)
- Yes. That's how it works when you absolutely "dare" someone that there isn't a single one that was followed. But in fact, as I wrote , most if not everything is followed. There is absolutely no problems with wp wrfc. Your statement is false. Please address which ones weren't followed if you want to claim problems with wp wrfc. Also don't ignore other points I have made. You didn't address them all and some, like this one are completely false. You can't make such a closure and after such false explanation just withdraw yourself from the discussion. Your closure is improper and I want my points addressed.95.168.107.28 (talk) 20:24, 24 August 2024 (UTC) — Preceding unsigned comment added by Trimpops2 (talk • contribs)
- Haha. The Ip just said on my talk page that this is just like Monty Python The Argument Skit [6]. That's so funny. May I suggest a formal mediation on whether he has answered the question or not? :) "You can't just say no it isn't. Yes it is." This is so funny. Trimpops2 (talk) 19:50, 24 August 2024 (UTC)
- But this simply isn't true that everything was answered. For instance You didn't explain the claim that not a single wp wrfc was followed. You said to go ahead any find any. And now when I have found, you say it's answered. Here agin a single exaple for your claim that everything was answered. Other things aren't answered as well. It isn't true that everything is answered 95.168.107.28 (talk) 19:35, 24 August 2024 (UTC)
~~ AirshipJungleman29. I need to be objective. I'm sorry, but all points need to be addressed. If some don't have validity, an explanation should be provided to explain why. Claims against your closure were made, and you can't be objective and claim that you can choose which points have validity and which do not. You may be satisfied with your closure, and you have the right not to respond. However, that actions should be evaluated by uninvoved editors. And even if you have answered some of the points, uninvolved editors should also provide an opinion. You can't be the sole arbiter. This is a community project. Trimpops2 (talk) 22:08, 24 August 2024 (UTC)
- Then I refer you to the community. Your comments are getting increasingly tiresome; if this continues I will do what I noted in the close and take you to WP:AE. ~~ AirshipJungleman29 (talk) 22:18, 24 August 2024 (UTC)
- Yes, I agree, let's see what the community says. However, I have started to have serious doubts who's truly uninvolved and objective. I will not address why I said that in this post. I first want to see how the community will address the points.
Your comments are getting increasingly tiresome
Please, leave personal comments like this for yourself. At this point this is just inappropriate. I have personally found some things tiresome, but I have never complained. Deal with it. You chose to close this and if you don't want to address points of complaints to your closure, ok. I also refer this to the community. I do now know what WP:AE is. I will repeat. I'm not contesting the consensus. I didn't start the reveiw. I have accepted many things said about me. But at this points, if I'm not satisfied with the answers to the points I will respond. I have always claimed objectivity, and I'm calling your actions as not objective. Now, let's stop and see what the community says. I will poke the opinons of uninvolved editos as I have or anyone other has the full right to, without being threated of being banned. And I will seek for an appropriate board that can review all what has happened here. Wikipedia is a community project. Now let's see what the community says. I will participate, you as I understand you have chosen not to, you said that you stand by that you already say, and I will add that you also stand by what you have failed to say/address. Trimpops2 (talk) 22:36, 24 August 2024 (UTC)
- Yes, I agree, let's see what the community says. However, I have started to have serious doubts who's truly uninvolved and objective. I will not address why I said that in this post. I first want to see how the community will address the points.
- Enough. I've indefinitely blocked Trimipops2 for a variety of reasons.--Bbb23 (talk) 22:51, 24 August 2024 (UTC)
Uninvolved
[edit]- Endorse: I saw this sitting in CR for a while but didn't close it because, as @AirshipJungleman29 aptly stated, it
was a mess from start to finish.
There was no other way to close this discussion. voorts (talk/contributions) 18:58, 22 August 2024 (UTC)
- Once again, I apologize. I was brainwashed by Croatian propaganda. Trimpops2 (talk) 20:27, 22 August 2024 (UTC)
- voorts , I have started to change my opinion, promped by valid argument. Thus I'm asking you to address the points of complaint. Or not, this is your option, but lack of will also be evaluated. Thank you. Trimpops2 (talk) 22:47, 24 August 2024 (UTC)
- Once again, I apologize. I was brainwashed by Croatian propaganda. Trimpops2 (talk) 20:27, 22 August 2024 (UTC)
- Trimpops2 seems to be trolling at this point, and is an SPA in the Balkans/Eastern Europe contentious topic area. A block or TBAN may be necessary.
My first read of the discussion is that "no consensus" is a reasonable result; the complaints from the IP on AirshipJungleman's talk page are not reasonable. The alternative, once IP editors are discounted, would be a consensus against the proposed change (although not necessarily a consensus for the current text) -- which is functionally the same outcome. Walsh90210 (talk) 23:06, 23 August 2024 (UTC)
- It is unfounded to ask an explanation on how sources and arguments were weighted when determining consensus? 95.168.116.29 (talk) 16:30, 24 August 2024 (UTC)
- IP has said to the closing editor that he
provided no explanation on how sources were considered when determining consensus.
. Walsh90210 said that he has reviewed that and that this is unfounded thing to ask. What's not to understand there? Trimpops2 (talk) 18:35, 24 August 2024 (UTC)- I know that. I'm asking Walsh90210, why is this unfounded? I think it isn't. I think it's common practice95.168.107.28 (talk) 18:57, 24 August 2024 (UTC)
- IP has said to the closing editor that he
- It is unfounded to ask an explanation on how sources and arguments were weighted when determining consensus? 95.168.116.29 (talk) 16:30, 24 August 2024 (UTC)
- More block evasion, this time on an IP that has been blocked repeatedly as a proxy. Could a passing admin deals with this? -- LCU ActivelyDisinterested «@» °∆t° 20:02, 24 August 2024 (UTC)
- The latest 95.168.range IP has been blocked, I won't be surprised if they come back again. -- LCU ActivelyDisinterested «@» °∆t° 20:47, 24 August 2024 (UTC)
- More block evasion, this time on an IP that has been blocked repeatedly as a proxy. Could a passing admin deals with this? -- LCU ActivelyDisinterested «@» °∆t° 20:02, 24 August 2024 (UTC)
Again noting Trimpops2 blocked as NOTHERE (not by me) Doug Weller talk 10:06, 25 August 2024 (UTC) And Wikipedia:Sockpuppet investigations/Bilseric Doug Weller talk 16:48, 25 August 2024 (UTC)
Discussion
[edit]Thanks for your time. You'll need a lot of it for this RfC. ~~ AirshipJungleman29 (talk) 15:15, 22 August 2024 (UTC)
See this. [7]. i have no evidence but woikd not be surprised if the IP is the blocked disrupive editor there, Bilseric. Doug Weller talk 17:47, 22 August 2024 (UTC)
- Yes. I agree. We shouldn't waste community time. Trimpops2 (talk) 18:55, 22 August 2024 (UTC)
- Agree with Doug Weller. In addition to Bilseric siteblocked in May, there was also an earlier similarly tendentious editor on the page, Asdisis who was blocked for socking. All three could be the same.
- Here's a list of IPs that were started during the RfC or have only a few edits, are SPAs participating on the Croatian side:
- Either these are socks or someone has been doing some recruiting. Trimpops2, did you suggest to any others that they get involved in the RfC? --ChetvornoTALK 10:53, 23 August 2024 (UTC)
- I don't really know what's happening at User talk:Trimpops2#Tesla RfC review, but it appears to have something to do with this screed posted on my talk earlier. ~~ AirshipJungleman29 (talk) 19:43, 23 August 2024 (UTC)
After all these years are we still arguing about Tesla? What does it matter where he was born, and in what country it was at the time or is now? He was notable for what he did in later life, not for where he was born. The only people who could be interested in that are people with such small minds as to think that claiming he was born in a particular country somehow brings glory upon themselves. It does not. Normal people laugh at you when you behave in such a way. Phil Bridger (talk) 20:42, 24 August 2024 (UTC)
- Phil Bridger, this isn't about Tesla anymore. I don't suppose you have read everything carefully, but I'm affraid we have bigger problems here. Trimpops2 (talk) 21:59, 24 August 2024 (UTC)
- No, we have a much smaller potential problem. Whether an RFC that had no chance (because of your initial statement) of leading to a consensus should be closed as "no consensus" is a tiny issue in comparison. Phil Bridger (talk) 08:35, 25 August 2024 (UTC)
- Trimpops2 has been blocked as NOTHERE. Doug Weller talk 10:05, 25 August 2024 (UTC)
- No, we have a much smaller potential problem. Whether an RFC that had no chance (because of your initial statement) of leading to a consensus should be closed as "no consensus" is a tiny issue in comparison. Phil Bridger (talk) 08:35, 25 August 2024 (UTC)
Is reverting alleged OR from an FA exempt from the 3RR brightline?
[edit]In this AN3 report Black Kite ruled no violation because there were less than 4 reverts in 24 hours. Fair enough. But they went on to say the reported user wouldn't be sanctioned anyway because
this is a featured article and [the user who was reverted by the reported user] is trying to add unsourced original research to the lead paragraph ... That's just disruption and even though it isn't technically included in WP:3RRNO
and
3RR is a technical bright line, and that metric has to exist, but equally I don't think you'll find any admin that will block any user (regardless of whether they're an admin or not) for removing disruptive material from an article (especially a fairly high traffic featured article) unless there is some other problematic issue.
Is that right? On their talk page Black Kite said that was common sense. I've always assumed WP:EW's Claiming "My edits were right, so it wasn't edit warring" is not a valid defense
was taken literally but are there exceptions not stated in 3RRNO? Equally, I don't think the user adding the material was being disruptive merely by adding it. They might be wrong but not disruptive although they were edit warring as was the reported user. I'll notify Black Kite, the reported user (DrKay) and the reporter (John) of this thread - but I'm not looking to have anyone sanctioned or to change the outcome of the 3RR report - just clarification of admin practice in this area. Btw, just to be clear, I think Black Kite is a good admin and don't have any issues with them in that regard. I'm sure they acted in good faith. DeCausa (talk) 17:23, 22 August 2024 (UTC)
- Exempt? No. But 3RR isn't a rule that someone must be blocked for violating, just a point at which they can be blocked. It's still up to admin discretion whether blocking would be beneficial. There are quite a few times I've let technical 3RR violations slide with no action or a warning because the edits were obviously improving the article, or because blocking would be detrimental to the encyclopedia. (I have not looked through the edits from the report in question, so this is a general response to scenarios like this; I have no opinion on whether Black Kite's decision was correct.) —Ingenuity (t • c) 18:02, 22 August 2024 (UTC)
- Assuming your statements here are 100% factually correct:
- The user in question did violate 3RR; removing OR from a featured article is no exception.
- An admin who decides that a specific instance of a rule violation should be ignored is not out of line. Indeed, the admin may legitimately choose to ignore it if enforcing it would be bad for Wikipedia.
- Animal lover |666| 18:24, 22 August 2024 (UTC)
- Assuming your statements here are 100% factually correct:
The editor DrKay reverted was not following WP:BRD, which complicates this particular example. I think DrKay has the moral high ground here and it is hard to take the other editor's side. However it would be nice to see more respect for 3RR from DrKay; a third editor could have made the final revert and avoided some drama. Personally I am pretty self-aware of my revert count in situations like these and I like to see this self-awareness in others as well. –Novem Linguae (talk) 18:12, 22 August 2024 (UTC)- Actually, scratch that. The reverts are more than 24 hours apart. 3RR was not violated. It seems like there is no violation. Is this ANI just about Black Kite's statement? –Novem Linguae (talk) 18:16, 22 August 2024 (UTC)
I'm not looking to have anyone sanctioned or to change the outcome of the 3RR report - just clarification of admin practice in this area.
Levivich (talk) 18:22, 22 August 2024 (UTC)- It's not ANI and right at the beginning I highlighted it wasn't a breach of the bright line. It's what Black Kite said in relation to what should happen even if it was a breach of the bright line. DeCausa (talk) 18:29, 22 August 2024 (UTC)
- Actually, scratch that. The reverts are more than 24 hours apart. 3RR was not violated. It seems like there is no violation. Is this ANI just about Black Kite's statement? –Novem Linguae (talk) 18:16, 22 August 2024 (UTC)
- There's a decent chance I would warn or sanction users that violate 3RR, even if they're making a good-faith effort to keep original research out of a featured article. I took Black Kite's comments as his being transparent about how he exercises admin discretion. Please don't take it as a broader statement about policy enforcement. Firefangledfeathers (talk / contribs) 19:20, 22 August 2024 (UTC)
- Four reverts in just over 24 hours. Warning the other editor in the edit war with a templated message mentioning blocks (DrKay is an admin). No BLP, copyvio or WMF considerations. No participation in article talk on the matter. The edits were clearly not vandalism. If this translates to "no violation", and if this is due to the article's FA status, I feel guidance should be added to the relevant policy page to allow a community discussion. There is already a mention there about TFA. I made the AN3 report because I thought DrKay acted poorly, very poorly for an admin. I would not have wanted them to be blocked but I believe a warning would have been appropriate under my understanding of current policy. I am absolutely certain that all three (the two edit warriors and the admin who closed the AN3 report) acted in good faith and believed they were improving Wikipedia, but this is almost always the case in edit wars. Finally, using "common sense" as a rationale sounds tempting, but one editor's common sense may be another's utter nonsense. This is why we have policies, guidelines, and discussion pages. If editors are allowed to get away with blatantly edit-warring, what could be seen as using (implied) threat of admin tools in a content dispute, and failing to discuss in talk, on the basis that it's an FA, I think that's a shame. Edit warring is bad; it creates unneeded tension, reduces the chance of collaboration occurring, and deters editors from improving articles that may need it, in spite of once having been peer-reviewed. I am agnostic on the material they were edit-warring to include or remove, but discussion is the way to go, not this, I think. Thanks DeCausa for bringing this here. John (talk) 19:51, 22 August 2024 (UTC)
IMO the existing mention you raised "
Considerable leeway is also given to editors reverting to maintain the quality of a featured article while it appears on the Main Page.
" is already sufficient to make clear that while there isn't a formal exemption, editors are less likely to be blocked if they are "maintain(ing) the quality" of the FA while on the main page and we should not push this any further.While I agree with you that having gone through peer-review is no guarantee the older version is better, I think it's fair to say that combined with the fact there tends to be scrutiny on a TFA before it goes on the main page means that it's significantly more likely that the status quo ante is indeed better. And at the very least, it's better to keep it while discussion ensures while there is dispute.
Note I'm not saying this excuses edit warring but Wikipedia always has a weird mix of competing forces. On the one hand, we can all agree that edit warring is disruptive and bad. On the other hand, I think many would agree that editors shouldn't be able to have their preferred version as the main one just because they were more aggressive as edit warring yet it's likely to be the natural result.
And then, we can say that even if it doesn't seem right, most of the time it doesn't matter much if for a few hours, days or maybe weeks while the issue is resolved it doesn't matter much if the WP:WRONGVERSION gets to stay just because one side was more aggressive in their edit warring with the obvious exception of when there are clear policy backed reasons e.g. WP:BLP.
But if those don't apply, then with TFAs we get the more complicated case where there is actually a reason why it seems to matter a lot which wrongversion gets to stay in even the short space of hours namely the large number of visitors (I think in some cases even multiple years worth of average visitors in one day). And so if we circle back to my earlier point, since we have to chose a WRONGVERSION, while we don't want to encourage edit warring we should also consider that in absence of anything else, the status quo ante would seem to be greatly preferred as the WRONGVERSION.
Yet because we don't want to encourage edit warring, I don't think we should make this a formal exemption. Instead it's better to keep the current situation where admins might consider it, but it's not a guaranteed exemption.
WP:NOTBURO etc, our "rules" are normally flexible. 3RR is one of the closest to being a hard rule, but as others have said, even when there is a technical violation, there's still no "must block". And already we have the situation where outside of technical violations, there is no clear "rule" and what admins do varies depending on a lot of things. And likewise while it might be a bad thing, very many good editors occasionally get involved in what can be consider an edit war with editors using their judgment on whether they should revert even if there have already been multiple reverts by others and there's no clear exemption of policy reason why it must be their wrongversion.
Nil Einne (talk) 11:04, 23 August 2024 (UTC)
- BTW I said all the above without having looked at the content. Now that I have, I will say IMO this is not the sort of thing I feel was a good idea to violate 3RR over even considering this was TFA. However if anything that IMO adds to our current guidance being sufficient. I'd much rather we leave it fuzzy so editors think careful and decide yeah not worth it in a case like this. Also while we don't generally want admins caring about content, I think this is one such case where it's fine if admins do consider it and so again if our current fuzzy guidelines mean look at what's happening and decide, well there is no formal exemption here IMO but the attempted change was clearly very bad so I think I'll just leave it; or in this case they look and go um yeah okay it's TFA and that change is unsourced however it's not the most terrible thing that I'll let the 3RR violation slide. Nil Einne (talk) 11:16, 23 August 2024 (UTC)
- It wasn't TFA. John (talk) 12:30, 23 August 2024 (UTC)
- (edit conflict) Apologies, I made incorrect assumptions because of the apparent urgency of those involved. In that case, I agree with you the edit warring was a particularly poor showing especially coming from an admin and even more when we consider DrKay didn't open a thread. I've long criticised the childish "they started it" mentality where editors expect the other side to start a discussion. I'd note that IMO even if you feel your version is so obviously correct that that any editor will agree, and because of that or whatever you intend to edit war, I think many of us find it more compelling if you can show you at least tried to discuss and the other editor ignored it as I expect might have happened here. (Of course if both editors take part on the discussion but edit war, you're no better off. And no, comments in edit summaries and talk page warnings don't count as discussion.) And while technically it's still true that even a brightline violation wouldn't require a block, I'm not convinced it's right for an admin to not at least warn. That said, without a brightline violation, I'm not convinced many admins would block, more likely to just warn. So I guess I'd like DrKay and Black Kite to change their minds on how to handle these things in the future. But I'm not sure the efforts required is worth it. Nil Einne (talk) 16:03, 23 August 2024 (UTC)
- It wasn't TFA. John (talk) 12:30, 23 August 2024 (UTC)
- BTW I said all the above without having looked at the content. Now that I have, I will say IMO this is not the sort of thing I feel was a good idea to violate 3RR over even considering this was TFA. However if anything that IMO adds to our current guidance being sufficient. I'd much rather we leave it fuzzy so editors think careful and decide yeah not worth it in a case like this. Also while we don't generally want admins caring about content, I think this is one such case where it's fine if admins do consider it and so again if our current fuzzy guidelines mean look at what's happening and decide, well there is no formal exemption here IMO but the attempted change was clearly very bad so I think I'll just leave it; or in this case they look and go um yeah okay it's TFA and that change is unsourced however it's not the most terrible thing that I'll let the 3RR violation slide. Nil Einne (talk) 11:16, 23 August 2024 (UTC)
- I was thinking of
That language has been policy for a long time, and I think it's one of our core principles. If a policy no longer reflects how the community behaves, the policy ought to be changed, after a suitable consensus is achieved to do so. (descriptivist view) Or, admins ought to enforce the policies we have agreed to the best of their ability, without fear or favour. (prescriptivist view). This episode just doesn't seem right to me. John (talk) 15:45, 23 August 2024 (UTC)Even without a 3RR violation, an administrator may still act if they believe a user's behavior constitutes edit warring, and any user may report edit warring with or without 3RR being breached. The rule is not an entitlement to revert a page a specific number of times.
- Another example of Wikipedia verb conjugation.
- First person singular, present tense: I am "defending an FA against disruptive editing".
- Second person singular, present tense: You are "edit warring".
- It is always particularly annoying to me when an editor is actively edit warring, but feels it appropriate to leave their opponent an edit warring templated warning. DrKay's previous 4 blocks for edit warring were all more than 10 years ago, albeit all while an admin, so hopefully this is an aberration. --Floquenbeam (talk) 21:42, 22 August 2024 (UTC)
- Lol, I thought the name seemed familiar. DrKay blocked me for edit warring many years ago! So if anyone wants to assume I hold a grudge and this is an "involved" comment of some kind, feel free, but the fact is I'm just forgetful. --Floquenbeam (talk) 21:54, 22 August 2024 (UTC)
- To add to my opening post: I think that Black Kite jumped to some inappropriate assumptions that what DrKay was reverting was disruptive and OR. In summary, the content dispute was that the lead referred to the decolonisation of Africa during Elizabeth II's reign and what was being disputed was the addition of a reference to the decolonisation of Asia. As can be seen in the subsequent talk page discussion here, it's clearly an editorial judgment call as to whether it should be added - there are arguments for and against but it certainly wasn't disruptive or OR (or at least no more OR than the existing reference to African decolonisation.) I think this all goes to show the dangers of admin discretion/leeway to allow breaching 3RR when it supposedly "benefits" the article. Ther's a reason why 3RRNO is limited to obvious vandalism, copyvio and the other very specific siatuations. DeCausa (talk) 21:28, 23 August 2024 (UTC)
- This isn't a 3RR violation, so the bright line rule doesn't apply. If it WAS a 3RR violation, a block might be in order, but we should take into account if falls under the listed WP:EW exceptions:
- Reverting your own actions ("self-reverting").
- Reverting edits to pages in your own user space, as long as you are respecting the user page guidelines.
- Reverting actions performed by banned users in violation of a ban, and sockpuppets or meatpuppets of banned or blocked users.
- }Reverting obvious vandalism—edits that any well-intentioned user would agree constitute vandalism, such as page blanking and adding offensive language.
- Removal of clear copyright violations or content that unquestionably violates the non-free content policy (NFCC). What counts as exempt under NFCC can be controversial, and should be established as a violation first. Consider opening a deletion discussion at Wikipedia:Files for discussion instead of relying on this exemption.
- Removal of content that is clearly illegal under U.S. law, such as child pornography and links to pirated software.
- Removing contentious material that is libelous, biased, unsourced, or poorly sourced according to Wikipedia's biographies of living persons (BLP) policy. What counts as exempt under BLP can be controversial. Consider reporting to the BLP noticeboard instead of relying on this exemption.
- Reverting unambiguous spam, where the content would be eligible for page deletion under criterion G11 if it were a standalone page.
- Admins should also take into account if a person is protecting the Featured Article of the day. I was once briefly blocked due to a malicious report which failed to mention my "exact same 4 edits" were all to revert vandalism on a WP:TFA...in fact, that's why the policy exception is there. Buffs (talk) 05:12, 24 August 2024 (UTC)
- I've seen administrators ignore the 3Rs in a case like a featured article, especially if it's a recent featured article and not one from 10 years ago. But you talk of a 3R bright line... if you cross it the OR had also better be as bright as the sun with no wiggle room. Fyunck(click) (talk) 06:19, 24 August 2024 (UTC)
- Which, as DeCausa argues above, was not the case here. John (talk) 19:57, 24 August 2024 (UTC)
- I've seen administrators ignore the 3Rs in a case like a featured article, especially if it's a recent featured article and not one from 10 years ago. But you talk of a 3R bright line... if you cross it the OR had also better be as bright as the sun with no wiggle room. Fyunck(click) (talk) 06:19, 24 August 2024 (UTC)
- No line can be so bright as to compel any individual admin to act. Phil Bridger (talk) 21:23, 24 August 2024 (UTC)
Block/ban appeal - Cyber.Eyes.2005
[edit]As Cyber.Eyes.2005 (talk · contribs)'s appeal has been sitting for several weeks without a response, and given that they are considered a banned editor per WP:3X, I'm bringing the appeal here for community review. I have no opinion as to whether the appeal should be accepted but will note that I don't see any obvious evidence of recent block evasion.-- Ponyobons mots 20:28, 22 August 2024 (UTC)
Begin appeal:
Requesting an unblock/unban request through WP:SO. I sincerely apologize for the mistakes I made in the past and fully understand that my previous actions, which led me to be blocked, were against the community guidelines of Wikipedia. I have since taken the time to thoroughly review and understand Wikipedias policies and guidelines, and I assure that I have learned from my mistakes and will not repeat them. The reason I got blocked as my first account User:Cyber.Eyes.2005, was due to getting involved in edit warring on a few articles, especially Brokpa. This eventually led to me being indefinitely blocked as I got involved in sockpuppetry. I didn't know much about Wikipedias policies at that time, and this became the reason I repeatedly made mistakes. During the past months, I have been working on other Wikimedia projects and have been a constructive editor on Simple English Wikipedia and Wikidata and I've become well aware of how Wikipedia works, policies like not abusing multiple accounts and edit warring, and how to contribute positively here. Moving forward, I am committed to making constructive and valuable contributions to Wikipedia only. I sincerely apologize for my past behavior and looking back, I understand that I lacked the maturity to edit constructively. I assure you that those mistakes will not be repeated and that my contributions will only be constructive. I am sincere about contributing on this wikipedia as well and I hope the admins would give me a chance. – Cyber.Eyes2005Talk 19:37, 19 June 2024 (UTC)
They also included the following follow-up:
I am reaching out to appeal an unblock/unban request through the standard offer. I sincerely apologize for the mistakes I made in the past and fully understand that my previous actions, which led me to be blocked, were against the community guidelines of Wikipedia. I didn't know much about Wikipedias policies at that time, and this became the reason I repeatedly made mistakes. I have since taken the time to thoroughly review and understand Wikipedias policies and guidelines, and I assure that I have learned from my mistakes and will not repeat them.
Original block
My first account on Wikipedia, User:Cyber.Eyes.2005. Since I wasn't an experienced editor and didn't know much about Wikipedia policies, I became involved in edit warring on a few articles, especially this one, Brokpa with User:Aman.kumar.goel and got blocked. This eventually led to an indefinite block as I got involved in Sock puppetry, both of which were in violation of Wikipedia's policies and guidelines and I fully understand that.
Constructive editor
During the past months, I have been working on other Wikimedia projects and have been a constructive editor on Simple English Wikipedia, Wikidata and Urdu Wikipedia and I've become well aware of how Wikipedia works, policies like not abusing multiple accounts and edit warring, and how to contribute positively here. Moving forward, I am committed to making constructive and valuable contributions to Wikipedia only. I sincerely apologize for my past behaviour and looking back, I understand that I lacked the maturity to edit constructively. I assure you that those mistakes will not be repeated and that my contributions will only be constructive. I am sincere about contributing on this wikipedia as well and I hope the admins would give me a chance. If granted a second chance, I am committed to contributing responsibly and constructively to Wikipedia. I hope to be given the chance to demonstrate my dedication to being a positive contributor to this community. – Cyber.Eyes2005Talk 09:48, 21 August 2024 (UTC)
Support unblock. Extremely new editor at the time they were blocked. The blocks were two years ago. They appear to have made constructive contributions to other wikis in the interim. The unblock request shows some introspection and I think it's reasonable to give them another chance, with a one-account restriction and an updated CTOP IPA notice.Struck support. The diff provided by Lorstaking below concerns me. Cyber.Eyes.2005 could have responded to the specific issues that had been raised here without personal aggressiveness toward the other editor, but chose not to, and characterized statements about specific edits as personal attacks. That level of combativeness is not conducive to collaborative editing, especially in the IPA topic area. Schazjmd (talk) 21:56, 22 August 2024 (UTC)
- Sure, unblock. Ponyo says there's no reason to think they've still been socking, and the edits at Simple and at Wikidata seem like they're in good faith. Schazjmd's caveats seem wise, as well as letting CE know that they're going to probably be watched more closely for a while, so they should tread very carefully. --Floquenbeam (talk) 22:05, 22 August 2024 (UTC)
- I can see how this is trending, but for posterity, I guess I'll comment again: I could still support an unblock, but I think now I'd need to insist on some kind of IPA topic ban. I don't know if CE just wrote what they think we wanted to hear in their unblock request and their response to Ratnahastin is their "real" self, or if the unblock request was genuine but the response to Ratnahastin was made due to stress. But either way, that aggressive response, made by someone while they're appealing a community ban, was pretty self destructive. I still suspect most of the problem is in the IPA topic area, so I think there's still a decent chance they could productively edit other topic areas. Floquenbeam (talk) 17:18, 23 August 2024 (UTC)
Support unblockexactly per Schazjmd. Walsh90210 (talk) 23:15, 22 August 2024 (UTC)- The simplewiki diffs presented by Ratnahastin are slightly concerning, but not nearly concerning enough for me to stop supporting the unblock. Walsh90210 (talk) 02:17, 23 August 2024 (UTC)
- The diff from Lorstalking is very concerning; I think some topic-ban will be necessary with an unblock. Walsh90210 (talk) 15:06, 23 August 2024 (UTC)
- The simplewiki diffs presented by Ratnahastin are slightly concerning, but not nearly concerning enough for me to stop supporting the unblock. Walsh90210 (talk) 02:17, 23 August 2024 (UTC)
- Support unblock - this is what we want to see in people who ask about the Standard Offer. --RockstoneSend me a message! 01:07, 23 August 2024 (UTC)
- Oppose - One needs to have a look at the edits he has made on Simple Wiki and they are disruptive. For example, he claims here that only Eastern Pakistan falls under the Indian subcontinent when whole Pakistan falls under the regional term. Here, he is edit warring to remove the Indian origins of Mughal empire. He created "Ancient Pakistan" there, even after knowing that such a POV article does not exist on English Wiki either.[8] He created "Middle kingdoms of Pakistan" on Simple wiki when no such article exists on Wikipedia because the country Pakistan was itself created only in 1947. He created "Indian naming dispute" there and used a large number of Godi media sources (see NDTV, Firstpost, India Today, etc.) which are notorious for falsifying history to fit the narrative of the current ruling Modi's BJP government. These are just some examples. He would be topic banned or blocked if he made these edits on English Wikipedia. I cannot think of supporting unblock with a topic ban from South Asian topics because there are no other topics which he has edited so far. I would rather urge Cyber.eyes.2005 to fix the damage he has done to Simple Wiki. Ratnahastin (talk) 01:24, 23 August 2024 (UTC)
- Reply below carried over from User talk:Cyber.Eyes.2005 per request-- Ponyobons mots 16:17, 23 August 2024 (UTC)
– Cyber.Eyes2005Talk 09:30, 23 August 2024 (UTC)It's clear who is engaging in POV pushing here. None of the edits you linked to are disruptive; they are well-cited, sourced, and I have provided reasons for each in their respective edit summaries. Your interpretation of them seems to be biased here. If you believe any of these edits or pages are disruptive, please discuss this on my talk page on Simple English Wikipedia. The guidelines there are similar to those on English Wikipedia: a page exists there if it is notable and well-sourced. If an article doesn't exist on English Wikipedia, it doesn't automatically mean it is POVish or shouldn't exist at all as you claimed (
He created "Ancient Pakistan" there, even after knowing that such a POV article does not exist on English Wiki either.[11] He created "Middle kingdoms of Pakistan" on Simple wiki when no such article exists on Wikipedia because the country Pakistan was itself created only in 1947.
).
Your actions here appear to be WP:ATTACK, as seen in your comments on my talk page (Special:Diff/1241672518). Your statements about using"Godi media"
sources and"edit warring to remove the Indian origins of the Mughal Empire"
are infact WP:POV. The edit in question was even agreed upon by a Simple Wikipedia admin.
Additionally, you claim that I haven't edited other topics is incorrect. Out of the 113 articles I've created on Simple English Wikipedia, only about 21 are related to Pakistan. This yet seems to be another personal attack.
Note: I am genuinely committed to contributing constructively on this Wikipedia, just as I have done on other Wikimedia sites. My constructive contributions on Simple Wikipedia can be verified by the admins there, as it is the platform where I have been most active for the last year. I hope I can be given a second chance to contribute positively to this Wikipedia as well.
- Oppose - Per above. His disruption on Simple Wikipedia is simply too big to ignore. It refutes his claims of being "a constructive editor". Dympies (talk) 01:54, 23 August 2024 (UTC)
Weak support - Activity shows slow but growing signs of being productive. I urge Cyber to continue contributing elsewhere, even after the unblock. Ahri Boy (talk) 02:49, 23 August 2024 (UTC)Not for now. Retracting. Ahri Boy (talk) 17:12, 23 August 2024 (UTC)- Oppose per Ratnahastin. There appears to be a huge number of unwarranted and unjustifiable edits from this editor, aimed at proving that Pakistan did not came into existence in 1947 but has existed as a separate entity for thousands of years. Creation of Hellenic Pakistan by mispresenting Indo-Greek Kingdom is another evidence of that. It is also the first time I am hearing about a "Indo-Pak subcontinent".[9] Nxcrypto Message 03:06, 23 August 2024 (UTC)
- Oppose per Ratnahastin; as someone who has contributed extensively in the area of the so-called "Hellenic Pakistan", a formulation which I don't believe has ever been used in scholarship, I oppose this unblock as a preventative measure. ~~ AirshipJungleman29 (talk) 10:54, 23 August 2024 (UTC)
- Oppose - The battleground mentality as evident from their latest response is appalling. Lorstaking (talk) 11:57, 23 August 2024 (UTC)
- Oppose The appeal seems to say all the right things but in a non-specific, formulaic, unemotional and even impersonal way, much like an LLM's output. jpgordon's response to an April 2024 appeal included
I suggest you write your own request rather than relying on chatbots for any part of it
to which Cyber.Eyes.2005 replied, in part,The above request had some grammatical problems which I fixed through AI
. This appeal still does not seem to be in their own words. Also, they socked several times a months for months, repeatedly being blocked;I got involved in sockpuppetry. I didn't know much about Wikipedias policies at that time
, far from being a credible excuse, is an abnegation of personal responsibility. NebY (talk) 16:19, 23 August 2024 (UTC)
Block appeal - Solaire the knight
[edit]As the block appeal for Solaire the knight (talk · contribs) has been open for several weeks without closure, I've volunteered to bring it here for community review.-- Ponyobons mots 21:57, 22 August 2024 (UTC)
Begin appeal:
After additional consultations and conversations with administrators, I decided to submit an additional request, answering the necessary questions asked of me by the administrator Z1720.
- An edit warring is when users revert other people's edits, especially repeatedly, rather than trying to reach consensus within the project's rules (this is objectively bad and prohibited because edit warrning destroys constructive work on the article and turns it into battlefield between users). My actions were rightly defined as a edit warring, because instead of opening a topic in the discussion of the page and showing reasonedly, with authoritative sources, why I think my edits are correct and reaching consensus through mutual discussion, I simply canceled the edits of my opponents and appealed to them " morality and justice." In the future, If my edit is reverted, then I will refrain from such actions as destructive and create a thematic thread on the talk page to discuss the conflict that has arisen and how it can be resolved within the framework of the project rules. Once the discussion is over, I will need to ask a neutral administrator to summarize it in order to approve consensus and avoid new conflict due to different views on the outcome of the discussion.
- A reliable source is an authoritative source who and meets Wikipedia's requirements for authoritative resources and can confirm the information I add. For example, if I want to add a claim that a scene from a show has become a meme, I need a source that directly describes this meme and meets Wikipedia's requirements for authoritative sources on a given topic. If other users express doubts about this, then I should also initially create a topic on the discussion page, where convincingly demonstrate authority of the source or provide new authoritative sources, instead of using any emotional reverts. This can be done by showing that the source is considered authoritative in its field (for example, it is widely quoted and recognized as authoritative by other objectively authoritative sources), is not in the database of prohibited sources on Wikipedia itself, and is not engaged in the dissemination of unauthoritative or biased information such as conspiracy theories, etc.
- I accept your reproach. Instead of drawing conclusions from the warnings of administrators and other users, and correcting any identified problems in my actions, I simply began to argue and complain about other users, although the topic of discussion should have been my behavior, and not transferring blame to other users or or another links to “justice and morality.” Now I understand that in such situations I should have at least adjusted my behavior and discussed in a polite and reasonable tone how I could correct this in the future. As a last resort, consult with familiar users. But definitely don’t taking this as an attack or a challenge against me.
To sum up the above, I ask you to unblock me by demonstrating that I recognize and understand the problems voiced and leading to my blocking. In the future, I promise to resolve any conflicts through constructive dialogue with authoritative sources within the rules on the talk page, avoid any edit wars, and take warnings as an opportunity to stop and correct problems in my actions instead of reacting hostilely to them. I hope that I have adequately answered the questions asked of me and can expect the block to be lifted. But of course, if any additional questions arise for me, I can always answer them.Solaire the knight (talk) 19:00, 4 August 2024 (UTC)
- It seems like a reasonably self-aware unblock request, so I'd be ok with an unblock. If unblocked, STK needs to remember that their edits are going to be watched more carefully for a while, so they should tread very carefully. --Floquenbeam (talk) 22:13, 22 August 2024 (UTC)
- Support unblock, hesitantly. I'd have liked to have seen some edits on other projects while they were blocked to show they can collaborate (August 2023 to June 2024, no edits anywhere). Looking at their interactions here and on their talk page at ru.wp, Solaire the knight seems to have been easily provoked. But they seem to recognize that in their unblock request and indicate they plan to react differently going forward,
"definitely don’t taking this as an attack or a challenge against me"
. I hope they can adjust their approach to collaborative editing; their contribution history shows the potential for being a useful and productive editor. Schazjmd (talk) 22:49, 22 August 2024 (UTC) - I reviewed the first unblock request last year, and left a very detailed response on what Solaire needed to address in a future unblock request. I have no opinion on this, and instead endorse the community's consensus. I invite editors who are commenting on this to read my comments in the first unblock request and determine if this addresses those concerns. Z1720 (talk) 02:06, 23 August 2024 (UTC)
- Support unblock - STK seems to have good signs of activity. I hope STK will provide reliable sources when he returns. Ahri Boy (talk) 17:19, 23 August 2024 (UTC)
- Support. I think this editor has adequately addressed Z1720's concerns. voorts (talk/contributions) 01:11, 24 August 2024 (UTC)
Netherzone
[edit]- Netherzone (talk · contribs · deleted contribs · logs · filter log · block user · block log)
I object to actions of administrator Netherzone. I received on August 10, 2024 notification about deletion discussion of Trotter Museum-Gallery article which I wrote. We were discussing merit of this article with Netherzone. On August 16 he/she posted a "Managing a conflict of interest" on my talk page to the effect that "the nature of some of my edits suggests that you may have a Conflict of Interest with some of the subjects you edit or articles you have created" regarding articles that I wrote on Esther Bruton, Margaret Bruton, and Helen Bell Bruton. I explained that I wrote these articles because her biographer, who wrote a book about them, complained that they are excluded from the art history because they were women artists, and that Wikpedia doesn't have articles about them. She (Wendy van Wyck) even thanked me for this as documented on this page https://brutonsisters.blogspot.com/2023/11/new-discoveries-wikipedia-and-happy.html She wrote: "On another note, many times I have bemoaned the fact that the Bruton sisters don't have Wikipedia pages. It has always been my intention to remedy this situation, but I just learned that I've been beaten to it! Another individual -- who prefers to remain anonymous -- has written beautiful Wikipedia entries for Margaret, Esther, and Helen, as well as a page for The Peacemakers mural. As you know, Wikipedia pages are always a work in progress, and I will continue to monitor and update the Bruton pages as appropriate. It's wonderful that the Brutons -- who are so deserving of this level of attention -- are finally on Wikipedia!" Netherzone accepted this explanation (he wrote: Thank you for clarifying this.) but did not remove "Managing a conflict of interest" note from my page. Instead he/she escalated his objections to the effect that "Several of your articles including the ones on the three Bruton sisters contain unsourced claims (which may be original research), a promotional tone or euphemisms, and some of the photos do not seem to have appropriate licensing and are copyrighted to the original artists yet claimed as "own work". These statements are most probably not correct and even if they are, they are not "conflict of interest" related. Subsequently, when I asked for specifics, I received general instructions from Netherzone about copyright on Commons. I am, of course, familiar with them and tried to explain to him/her that some of Bruton's works were supported by the US Government and therefore are on public domain. There are other cases when art is on public domain - their mosaics on public building are most probably covered by freedom of panorama, but I could not get specifics from Netherzone of which images are my perceived "conflict of interest" so it is difficult for me to address his/hers concern; but for sure I do not have any conflict of interest here. Also, I feel uneasy about his/her action around this case. For example, soon after deletion discussion about "Trotter Museum" other discussions ensued (Bruton sisters, Ellen Hadden, Steve Hauk) as if through some concentrated effort. Also, I was asked by Netherzone me to review all my images on Commons and he/she started to enquire about my personal information on EN:WP. I would like that "Managing a conflict of interest" is removed from my page. Puncinus (talk) 00:51, 24 August 2024 (UTC)
- Netherzone has been nothing but polite and patient with you. There's no conspiracy because your article was deleted after a discussion that you bludgeoned. Additionally, it appears that Netherzone is not the only editor who has raised concerns with potential OR and sourcing issues. voorts (talk/contributions) 01:07, 24 August 2024 (UTC)
- Netherzone is not an administrator. There is nothing actionable about being advised of the conflict of interest policy (which is all the "Managing a conflict of interest" message is), being advised of copyright policy and similarly being asked to review your submissions to ensure they are compliant, or being asked if you operate more than 1 account (which is what I presume you mean by
started to enquire about my personal information
). You are not required to answer Netherzone regarding another account; if they (or any other editor) believe you may be using multiple accounts abusively they can submit an WP:SPI and that'll be handled appropriately. You do not need to ask others to remove the conflict of interest message from your talk page; you may remove it yourself. —Sirdog (talk) 01:22, 24 August 2024 (UTC)- Reviewing the user's talk page, Netherzone has been incredibly patient with this editor, who posted some of the more frustratingly obstructionist replies I've seen in a while, especially regarding copyright and needing things explained to the nth degree. [10] [11] [12] [13] [14] [15] [16] [17] [18] Daniel (talk) 02:13, 24 August 2024 (UTC)
- This should probably be closed as unactionable. Netherzone was incredibly patient. Other editors have also tried to help them understand. The OP is not listening, not comprehending and being unnecessarily obstructionist. --ARoseWolf 08:32, 24 August 2024 (UTC)
- Any of us may, at any time, be asked about WP:COI and/or WP:PAID. It is our common practice to accept a simple, clear and unequivocal answer, to AGF. The question is a polite question and is inoffensive. I concur with ARoseWolf that there is no action that needs to be taken. Decorum and politeness have reigned throughout, and I think that bringing this here was a simple good faith error by the OP, who was seeking more explanation than necessary. 🇺🇦 FiddleTimtrent FaddleTalk to me 🇺🇦 08:30, 25 August 2024 (UTC)
- Involved as AfD !voter, although one who was hoping to find a reason to retain it. NZ's behavior is not remotely of concern here. Puncinus, if you want it removed, you're welcome to do so as it's considered acknowledging. The only thing a user may not remove is a declined unblock notice. Please take the feedback on board as you continue editing as it's helpful when looking at the amount of coverage organizations require and how to best present that. Star Mississippi 19:02, 25 August 2024 (UTC)
Hello! Dear enwiki community
[edit]- I am saddened to inform you that BlackShadowG (talk · contribs) has passed away. In light of this, I kindly request the removal of their IPBE (IP Block Exemption) permissions.
- Thank you for your help.
- Sincerely, ASId.
ASid (talk) 11:55, 24 August 2024 (UTC)
- Sad news, but done. Nthep (talk) 12:22, 24 August 2024 (UTC)
- Condolences, comrade. Ahri Boy (talk) 16:26, 24 August 2024 (UTC)
POVPUSH removal of "Black"
[edit]- Task: Test for a no-insertion one-line removal of
/ ?[Bb]lack ?/
. Tag or only log articlespace edits by non-autoconfirmed editors. - Reason: Some instances of this subtle POVPUSH may remain undetected for a long time. An EF can produce a list to review.
- Diffs: [19] [20]
142.113.140.146 (talk) 01:24, 1 August 2024 (UTC)
Deferred to WP:RFPP, WP:AIV, and similar. The diffs provided are a singular IP, but that can be dealt with via blocks and protection. Generally the disruption should be somewhat widespread for a filter to have much effect here. EggRoll97 (talk) 06:04, 1 August 2024 (UTC)
- Here are more UCR diffs, all by different IPs: [21] [22] [23] [24].
- Those IPs did not edit more than 2 articles so WP:AIV would say "insufficiently warned". In the [25] that I caught, the page was over a year old so would not normally qualify for WP:RFPP, and it was undetected for half a month. Those edits were reverted by multiple editors with long edit histories. This hit-and-run disruption is attempting to hide the alteration of POV. A tagging EF will have the effect of revealing the full extent of the damage. 142.113.140.146 (talk) 06:33, 1 August 2024 (UTC)
- Moved here to WP:AN. No specific user so not WP:AIV. No specific page so not WP:RFPP. 142.113.140.146 (talk) 19:10, 24 August 2024 (UTC)
Flurry of move activity from my account
[edit]In the event anyone happened to notice a flurry of activity concerning moves and deletions from my account in the 60-90 minutes, I wanted to post to let the community know that I went to archive my talk page and accidentally moved all affiliated subpage talk pages to an incorrect title, then to an archive 24 title when I only meant to move my current talk page. Its the second time I've done this, but I do believe after a good hour of checking, deleting, and moving that I got everything back where its supposed to be. Sorry for any confusion or concern that may have caused. TomStar81 (Talk) 19:26, 24 August 2024 (UTC)
Possibility of cross wiki vandalism related to anime, manga and seiyu from ja:LTA:203, ja:LTA:TAROSU in near future
[edit]When I checked the protected log in Japanese Wikipedia, there’s a lots anime, manga and seiyu stuff gets indefinitely or long term protected (you can see it’s [log in Japanese Wikipedia]) due to excessive vandalism by long term abusers especially from ja:LTA:203, ja:LTA:TAROSU, ja:LTA:ISECHIKA and ja:LTA:Iccic.
I have concern about those LTA from Japanese Wikipedia might bring its vandalism into English Wikipedia as soon more and more articles gets indefinitely protected, however, they have policy related to these types of LTA, should we also adopt this policy if they bring its vandalism into English Wikipedia?
By the way, here is my translation of these policies in Japanese Wikipedia:
These criteria have been agreed upon in related incidents for protection.
- Article should placed on 3 years semi-protection if vandalism occurs after 1 year semi-protection is lifted
- Article should placed on indefinite semi protection if vandalism occurs after 3 year protection lifted
- From 2019 onwards, frequent semi-protection breakthroughs made by sock accounts, in which case extended semi-protection (Japanese version of ECP), officially operational from 2020, is required.
- If semi-protection for more than three years and vandalism still occurs after it is lifted, or if they break through the semi-protection by using sock accounts, they should be moved to ECP and the deadline re-set, or indefinite semi-protection is required.
AussieSurplus1510 (talk) 19:33, 24 August 2024 (UTC)
- If articles become targeted, we can protect them. We also already have a policy on article protection. NinjaRobotPirate (talk) 22:06, 24 August 2024 (UTC)
Broad vs. narrow TBAN closure at ANI
[edit]At WP:ANI#Proposal: Topic ban from GENSEX (Behaviour of JacktheBrown) (permalink), TarnishedPath proposed to topic ban JacktheBrown "from the GENSEX area, broadly construed"
. For background info, see the preceding section (§Behaviour of JacktheBrown, permalink) and the linked discussions and diffs.
After about five days of discussion amongst about 20 participants, Valereee closed the discussion with "Clear consensus for a topic ban from WP:GENSEX. No consensus for further restrictions."
Valereee made it clear—in her ban message at JTB's user talk page (see here and here), at the restrictions log, and in a follow-up discussion at her own user talk page (whole discussion link, permalink)—that the TBAN she implemented is not broadly construed.
My questions for the community are:
- Was there consensus for a broadly construed TBAN?
- If so, do admins have discretion to implement a ban that is narrower than the one that has consensus?
Many thanks for your consideration. It would help, I think, to format bolded !votes in Yes/No on 1, Yes/No on 2 format wherever possible. Firefangledfeathers (talk / contribs) 02:28, 25 August 2024 (UTC)
- Obviously I have my own take on this, but I'm hoping to hear outsider views first. On a procedural note, I've pinged the bare minimum of users here. I would appreciate a second opinion on whether we should ping the participants of the discussions at ANI, JTB's user talk, and V's user talk. For a related policy discussion, see WT:BAN#Can a topic ban from a ct area specifically exclude “broadly construed”?. Firefangledfeathers (talk / contribs) 02:28, 25 August 2024 (UTC)
- Regarding question 2 in the general case: administrators can enact an editing restriction only when authorized by policy, the community, or the arbitration committee (to whom the community has delegated authority). So if the scenario doesn't fall under these cases, administrators do not have discretion to create their own editing restriction; the community has to decide upon it (or the arbitration committee on its behalf).
- In this specific case, the behaviour in question is related to a designated contentious topic area, gender and sexuality. Thus administrators do have the authority to enact editing restrictions on their own initiative. But when using the authority granted to them via the contentious topic/discretionary sanctions system, they are acting independently of any ongoing community discussion, and so leave them open. (The community can choose to end the discussion if they consider the remedy to be adequate.) Since Valereee closed the discussion, and did not assert that that they were acting under the authority of the contentious topic designation, they did not have discretion to create their own version of the editing restriction to enact. isaacl (talk) 03:26, 25 August 2024 (UTC)
- I agree with isaccl's answer to question 2. Best, Barkeep49 (talk) 20:43, 25 August 2024 (UTC)
- 1 - Yes - There is no ambiguity in the community's response among those who supported, and those who supported did not question the language in the proposal, or comment that it shouldn't be broadly construed.
- 2 - No - WP:CBAN says When determining consensus, the closing administrator will assess the strength and quality of the arguments made. Valereee correctly notes that there is a "Clear consensus for a topic ban from WP:GENSEX". And since the proposal specifically says "broadly construed", they don't have discretion to override the community, and implement a ban that is narrower than the one that has consensus. Isaidnoway (talk) 03:33, 25 August 2024 (UTC)
- 1 - Yes, 2 - No (involved). There is no ambiguity that I proposed a broadly construed WP:TBAN and no editors !voting to support suggested anything less than that. In fact some suggested expanding the TBAN to all CTOPs. As per whether it's within an admin's discretion to vary from the community consensus, Isaidnoway and Isaacl make strong arguments that admins do not have that discretion. TarnishedPathtalk 06:19, 25 August 2024 (UTC)
- 1 - Yes, and 2 - Yes-ish. Yes, sysops do have discretion to interpret community consensus, and no, the consensus isn't constrained by how the original proposer framed the question. An outcome like this is sometimes within sysop discretion, depending on what's happened and the community's strength of feeling. In this case I do feel that it would be better if Valereee is willing to re-evaluate the discussion and put in a less narrow sanction.—S Marshall T/C 15:59, 25 August 2024 (UTC)
- 1. Yes; 2: No. The proposal was quite clear to be "broadly" construed, and no supporter went against this, making it clear consensus that the topic ban is broadly construed. And admins may not violate explicit consensus in this context (although when consensus is for no/less action, they can respond unilaterally to new behavior). Animal lover |666| 16:02, 25 August 2024 (UTC)
- I appreciate the discussion, FFF. I'm not going to weigh in here on the question. I closed the discussion as a clear consensus for a tban, and I certainly don't disagree that I may have used too much discretion. For what it's worth, as an admin I'd very much like to have this kind of discretion. But if I don't, I'll of course comply with what the community wants. Valereee (talk) 16:06, 25 August 2024 (UTC)
- 1: Yes; 2: No. The proposal was perfectly clear and not malformed; there was no room for misconstruing (!) what was under discussion. If an admin—as any editor—comes to a discussion and thinks the proposal is wrong, they should take their admin hat on and make an alternative proposal as an editor. Re-interpreting a consensus is a classic supervote; while admins may have—to a degree that should not be exaggerated—discretion to interpret community consensus, that does not mean changing it. Or, as happened here, picking and choosing the parts one wishes to implement. It may only have been two words out of 16, but they fundamentally change the community's decision and the nature of the discussion that led to the community reaching that conclusion. And that's not counting the danger of whether it sets any kind of precedent. SerialNumber54129 17:21, 25 August 2024 (UTC)
- I know Wikipedia loves the phrase "broadly construed", but what does it actually mean in this context? What edits would be allowed if this was narrowly construed but not if it was broadly construed? Phil Bridger (talk) 18:33, 25 August 2024 (UTC)
- Generally it seems helpful to stop tban'd editors from testing the edges of their topic ban, as any edge case can be considered to be covered by 'broadly construed'. Without it you end up with timesinks discussions about exactly what is or isn't covered.
- If the ban is narrowly construed then what is or isn't covered, is it only articles specifically about the topic or are sections covered, what about edits that only copyedit a sentence? This is all a waste of time, tbans are supposed to give editors a chance to edit outside the area of disagreement. 'Broadly construed' is just a term used to try and pre-empt such discussions -- LCU ActivelyDisinterested «@» °∆t° 19:15, 25 August 2024 (UTC)
- Based on that interpretation it seems that every topic ban should be "broadly construed". I think I agree. At least, if I was topic-banned, I would take it as being so. Phil Bridger (talk) 17:05, 26 August 2024 (UTC)
- Yes/No-ish (involved). While I think there is a level of admin discretion allowed, this wasn't one where it was needed as consensus among established editors was clear. There was no reason for the proposal not to be enacted as proposed & supported. That said, I don't find fault in this review nor of Valeree's close and the discussions leading us here. She has been trying to guide Jack to be a productive editor and closed it in a way that she thought reflected consensus as well as helped guide Jack's edits. I see no evidence she was deliberately closing it against consensus and this may be a gray area. I second Phil that I'm not sure broad/narrow is a thing in gen/sex. Star Mississippi 19:10, 25 August 2024 (UTC)
- N/A (tho you can consider this as
No/NoYes/No if you want): My reading of the cases that established discretionary sanctions/contentious topics in general is that it's not just the specific topic ban that is broadly construed, but rather the entire topic area. So for instance, if you look at abortion, American politics or alternative medicine, they all say that their topic areas are "broadly construed". To me that implies that any topic ban in those topic areas is always broadly construed and cannot be narrower.However, in the particular case of GENSEX it's lacking the "broadly construed" language that's present in other cases. So in this case I'd argue that the topic area itself is not broadly construed, because ArbCom could've and didn't include that language. (My suspicion for why is that since everyone has a gender and a sexuality, a broadly construed GENSEX topic ban could be argued to be basically equivalent to a site ban.) And since the topic area itself isn't broadly construed, support for a GENSEX topic ban is not broadly construed unless specifically called out as broadly construed, which nobody did.Loki (talk) 19:37, 25 August 2024 (UTC)- I think that's because the language is now part of WP:Contentious topics itself,
Unless otherwise specified, contentious topics are broadly construed; this contentious topics procedure applies to all pages broadly related to a topic, as well as parts of other pages that are related to the topic.
GENSEX doesn't contain language specifying that it opts out of being broadly construed. -- LCU ActivelyDisinterested «@» °∆t° 19:52, 25 August 2024 (UTC)- Ah, you're right. In that case you can consider this as ```Yes/No``` and I'll strike the parts of this that aren't relevant. Loki (talk) 19:55, 25 August 2024 (UTC)
- As I discussed at Wikipedia talk:Banning policy#Can a topic ban from a ct area specifically exclude “broadly construed”?, the standard set of restrictions described at Wikipedia:Contentious topics § Standard set includes
page bans (from the entire contentious topic, a subtopic, or specified pages within the topic)
. Thus admins are authorized to impose an editing restriction for a tailored subset of the designated contentious topic area. isaacl (talk) 22:28, 25 August 2024 (UTC)
- I think that's because the language is now part of WP:Contentious topics itself,
- Uninvolved comment Not involved in any way, I'm genuinely surprised at the WP:HOUNDING to drive away a user. There are already several overlapping thread on ANI, and now also this. If it would be a particularly problematic user, it might make sense. Looking at their edit history, I do see problems but nothing that would warrant this many threads. The user has already been tbanned. How about everyone leave them alone for a while and go on editing? Jeppiz (talk) 20:00, 25 August 2024 (UTC)
- This is not about a specific user. Doug Weller talk 20:02, 25 August 2024 (UTC)
- Yes/neutral with a however (involved) I did vote on the proposal so I guess I am involved, but I did not participate much in the thread. I have in the past answered questions from Jack, also. ActivelyDisinterested, and Barkeep49 had convinced me that Firefangledfeathers' reading of the wording is correct, which I consider unfortunate in this instance, since it will put a sword of Damocles above the head of a good-faith editor whose language skills are in question. I have seen very divergent applications of "broadly construed" and I do not think the editor can navigate this, particularly since they are now editing Russia/Ukraine topics, which is the topic area where I noted the differences of interpretation. But Isaaccl seems to think that a sanction can be tailored, which I think was a good idea in this case. So I am neutral on the interpretation of the rules. My vote in the thread was a ban from all contentious topics, and did not address "broadly construed", btw, although I did support the proposal as written. My concern at the time was Russia/Ukraine however. This editor in that topic area is just not going to end well, and since he has edited the article about the arrest of the Telegram CEO, he has not taken that concern on board. Bottom line, does he deserve a rope? If not, just indef him already. Going with "broadly construed" is going to give the same result, only with much more drama and wasted editor time. Elinruby (talk) 22:50, 25 August 2024 (UTC)
- @Elinruby: "...they are now editing Russia/Ukraine topics...", I actually no longer collaborate on topics regarding the Russia/Ukraine war (Pavel Durov isn't part of this topic). Excuse me for intruding into this discussion. JacktheBrown (talk) 23:12, 25 August 2024 (UTC)
- er, yes it would definitely be part of it under "broadly construed" in my opinion given Telegram's very extensive use for official statements in that war. Mind you, interpretations of "broadly construed" in Russia/Ukraine vary widely, as previously noted. I strongly suggest that someone give you very detailed instructions if this provision is added to your topic ban from GENSEX. And if you have any questions at all about whether something does or does not fall under "broadly construed" you should absolutely ask them, and ask them of whoever the enforcing admin is for the topic ban. I believe it is Valereee, but you need to ask her about this, as I do not want to steer you wrong. But let me emphasize this: although you have wound up at ANI before for asking questions, you need to ask any questions you have about this, because you definitely do not want to be at ANI for being mistaken about your
slippery slopetopic ban. Elinruby (talk) 23:58, 25 August 2024 (UTC)
- er, yes it would definitely be part of it under "broadly construed" in my opinion given Telegram's very extensive use for official statements in that war. Mind you, interpretations of "broadly construed" in Russia/Ukraine vary widely, as previously noted. I strongly suggest that someone give you very detailed instructions if this provision is added to your topic ban from GENSEX. And if you have any questions at all about whether something does or does not fall under "broadly construed" you should absolutely ask them, and ask them of whoever the enforcing admin is for the topic ban. I believe it is Valereee, but you need to ask her about this, as I do not want to steer you wrong. But let me emphasize this: although you have wound up at ANI before for asking questions, you need to ask any questions you have about this, because you definitely do not want to be at ANI for being mistaken about your
since it will put a sword of Damocles above the head of a good-faith editor whose language skills are in question
and therein lies the problem. Despite opening at least one thread, I don't think Jack actually means to be disruptive, he just is because there's too much nuance needed and he doesn't have the language skills. I think a topic ban from CTs was going to be more kind than where we ultimately end up. Star Mississippi 00:27, 26 August 2024 (UTC)- I agree. But also, there are problems with the "broadly construed" language and in my opinion this is a particularly bad use case for it. But I leave the question of whether omitting it is allowed to actual admins. I personally think that if it is not, then it should be, but this is not a policy-based argument and I do not claim that it is. Also, I did not look into what he was doing at the article I mentioned above exactly, but it looked like wikignoming with little potential for harm. And of course this is an academic discussion, since he currently has no restrictions in that topic area. But just saying.Elinruby (talk) 00:40, 26 August 2024 (UTC)
- The question here is not if narrowly construed TBANs are appropriate ever; nor is it if you, personally, would support it in this case. The only question is if the closing admin's actions are reasonable given the course the original discussion took. Animal lover |666| 09:40, 26 August 2024 (UTC)
- I agree. But also, there are problems with the "broadly construed" language and in my opinion this is a particularly bad use case for it. But I leave the question of whether omitting it is allowed to actual admins. I personally think that if it is not, then it should be, but this is not a policy-based argument and I do not claim that it is. Also, I did not look into what he was doing at the article I mentioned above exactly, but it looked like wikignoming with little potential for harm. And of course this is an academic discussion, since he currently has no restrictions in that topic area. But just saying.Elinruby (talk) 00:40, 26 August 2024 (UTC)
- My comments on the standard set of sanctions available for areas designated as contentious topics were specific to a scenario where an adminstrator is imposing a restriction on their own initiative. This does not mean that an evaluator of consensus for a community discussion is authorized to enact a remedy that was not discussed. isaacl (talk) 16:06, 26 August 2024 (UTC)
- @Elinruby: "...they are now editing Russia/Ukraine topics...", I actually no longer collaborate on topics regarding the Russia/Ukraine war (Pavel Durov isn't part of this topic). Excuse me for intruding into this discussion. JacktheBrown (talk) 23:12, 25 August 2024 (UTC)
- Yes/no, note I was involved. I also think it creates problems for the editor and Admins if there are no clear boundaries as to what can be edits. Doug Weller talk 09:46, 26 August 2024 (UTC)
- 1 Yes, 2 N/A, involved in RfC. And I'm going to reiterate my opinion that this editor does not belong in any CT area. I think that no matter how much you value your own style changes, when you are a proven time sink and start violating core policies like WP:DUE in CT areas enough should be enough. Might seem harsh, but I've seen this editor struggle for about a year and a half now and while I was hoping they would find their place as a genuine net positive editor, their recent contentious topics adventures have convinced me that's not going to happen anytime soon. TylerBurden (talk) 17:53, 26 August 2024 (UTC)
File:Little Esther Jones with dog-1930.jpg
[edit]The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.
File:Little Esther Jones with dog-1930.jpg is {{PD-US-not-renewed}}, according to c:Commons:Village pump/Copyright#Little Esther Jones with dog. Please undelete the original version, so that I can copy it to that project. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:06, 25 August 2024 (UTC)
- @Pigsonthewing: I've undeleted the original version. Isabelle Belato 🏳🌈 16:44, 25 August 2024 (UTC)
- @Isabelle Belato: Thank you. Now on commons, and can be deleted from here. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:18, 25 August 2024 (UTC)
IBAN being over
[edit]is my iban over? It was enacted for one year at User_talk:Therapyisgood/Archive_2#Interaction_ban as a result of this closure, but I'm not sure if there's a continuous editing requirement (I took July 2024 basically off). I won't mention who it's with in case it's not over yet. Therapyisgood (talk) 18:46, 25 August 2024 (UTC)
- Noting for community's sake that it is with @BeanieFan11 who I will notify. I understand why you did not. Star Mississippi 19:12, 25 August 2024 (UTC)
- Since I was pinged: No objection to the sanction being lifted. BeanieFan11 (talk) 19:31, 25 August 2024 (UTC)
- As closing admin, I was assuming calendar year. I don't think anyone in the discussion raised the possibility of counting "editing year" differently. --SarekOfVulcan (talk) 17:25, 26 August 2024 (UTC)
Talk:Leo Frank, User:Schlafly, and WP:IDHT
[edit]Hi, everyone. First, some background: Leo Frank was a Jewish factory superintendent in Georgia in the 1910s; he was convicted of the muder of Mary Phagan, a 13-year-old factory worker, pardoned by the Georgia governor, and then abducted from prison and lynched. Now, the modern historical consensus, as our article states, is that Frank's trial was a miscarriage of justice, and that he was in all likelihood innocent of the crime. These statements are well-sourced in the article. Nevertheless, the case has become a cause célèbre amongst Neo-Nazis, white supremacists, and the like in modern times, and so the talk page gets the predictable and pretty regular attention from SPAs/sockpuppets pushing this agenda, almost always with little-to-nothing in the way of sourcing, reliable or otherwise, to back their claims.
Then there is Schlafly. He doesn't actually start any discussions himself, but any time one of these new threads appears, Schlafly will generally be there to take up the call. This has been going on for over a year now. We started with Schlafly citing leofrank.org to support this viewpoint, a website run by "avowed white supremacists", among other delightful things (src). When confronted with reliable sources, he seemed to realize this, only to change his mind by way of impugning the motives of the reliable sources, pettifogging over the exact phraseing of the sources, and just general stonewalling. And also some just bizarre untruths in service of said pettifogging. Recently, he's started just saying "google it" in lieu of any reasonable defense. Most recently, he's moved on to casting doubts on the other editors' motives, rather than just the motives of the so-called "pro-Jewish" sources. When called on this, he merely deflects, rather than actually acknowledging anything. You'll notice that, throughout all of this, there is a 100% absence of any kind of reliable sourcing that supports his claims. I feel like we've reached the point where it's been firmly established as a conduct issue, and enough is enough.
So, in my mind, a partial block for User:Schlafly from the Leo Frank article and its talk page, where he has contributed a bunch of heat and exactly 0 light, would help reduce the problem down to dealing with the SPAs/socks themselves. On that note, some kind of general sanction setup and/or page restriction might be helpful, or even just an affirmation that editors and admins should be more proactive in shutting these threads down quickly before they get out of hand and spawn things like completely pointless RfCs that just wastes everyone's time and energy (along with the good old-fashioned blood libel, of course). But if there's no will for something like that, just removing the most consistent actor here will help. Writ Keeper ⚇♔ 20:17, 25 August 2024 (UTC)
- Support pblock from article/talk page for Schlafly. I've been involved on that talk page for a few years and agree with Writ Keeper's summary. There's been a repetitive pattern of an IP or new SPA opening a thread setting out arguments copied form the neo-Nazi websites referred to by Writ Keeper with Schlafly then chiming in WP:CPUSH-style with vague allegations questioning the consesnsus that Frank was wrongfully convicted. DeCausa (talk) 20:47, 25 August 2024 (UTC)
- Support topic ban from articles/talk related to Judaism, broadly construed. Editors (particularly Jewish editors) should not have to deal with this kind of historical revisionism. voorts (talk/contributions) 20:54, 25 August 2024 (UTC)
- Support a broad topic ban per voorts and the excellent evidence of a pattern of behaviour presented. FortunateSons (talk) 21:18, 25 August 2024 (UTC)
- User:Schlafly has acknowledged a number of times (example), that he is the far-right commentator Roger Schlafly, a scion of the late Phyllis Schlafly. Roger Schlafly's publicly stated opinions include that rising non-white birth rates in the U.S. are "not a good thing" and part of an attempt to "repopulate the country with non-whites" (cf. Great Replacement). He is also known for his promotion of the bizarre conspiracy theory that Albert Einstein stole many of his theories from gentiles. You can read enthusiastic praise from the neo-Nazi Occidental Observer here.I wrote an essay a while ago that was partly about how we don't block people just for thinking the wrong thing, and partly how linking oneself to an off-wiki hate figure is per se disruptive editing. In theory that might lead to hard calls if someone only edits about apolitical things, but in practice one finds that people who will out themselves as advocates of hatred will also let that ideology infuse their editing. That's obviously the case here. This is someone who has devoted his public life to fomenting hatred against Jews and other ethnic minorities, and does the same on-wiki. As I wrote in that essay,
So, support indefinite block. -- Tamzin[cetacean needed] (they|xe) 02:10, 26 August 2024 (UTC)In most cases of hate speech, [limited sanctions] will not be enough. A temporary block is unlikely to dissuade someone of deeply-held views. And a topic ban may help with content disruption, but will not make editors from the affected group comfortable around the editor in question. (After all, the average person from some targeted group does not only edit articles about that group.) So if someone is engaged in concerted hate speech, the proper remedy will usually be an indefinite block or siteban.
- Instead of responding here, Schlafly has decided to post this absolute banger to the article's talk page, with its attendant insinuation that any source who engages with the fact that this was a hate crime is themselves biased and unreliable. Anyway, just for the record, I finally put two and two together about this user's RL identity a few weeks ago, but haven't looked into it beyond their obvious connection to Phyllis Schlafly, and deliberately kept it out of my opening statement to try to stick to onwiki diffs and events as much as possible. I certainly wouldn't be opposed if a harsher sanction than a pblock gains consensus. Writ Keeper ⚇♔ 02:42, 26 August 2024 (UTC)
- Support indef per WP:NONAZIS, thanks to the evidence provided by Tamzin above. The Kip (contribs) 03:11, 26 August 2024 (UTC)
- And the further info below. The Kip (contribs) 07:27, 26 August 2024 (UTC)
- Go straight to ban. The editor may well not be who they claim to be, but there is no place for them here. While the concept of antisemitism has been debased to mean anything someone dislikes, this is the real thing and there is absolutely no place for it here. Daveosaurus (talk) 05:33, 26 August 2024 (UTC)
- I wouldn't be too worried about impersonation. At [26], Roger Schlafly writes that "There is only one" Roger Schlafly. The blogs he links there shed some further light on his views, by the way:
- "[Leo] Frank was a Jew fairly found guilty of raping and murdering a White girl, based largely on the testimony of Black witnesses. I think the point of the story is that Jews should not be held accountable by goys for crimes against goys." [27]
- "the notorious Jewish pervert and murderer Leo Frank" [28]
- "Let us review who runs the USA:President Joe Biden, kids married Jews, VP Kamala Harris, Jamaican-Hindoo, married to Jew, Sec. of State Anthony Blinken, Jew, Sec. of Treasury Janet Yellen, Jew, Sec. of Defense Lloyd Austin, Black, Attorney General Merrick Garland, Jew, Sec. of Homeland Security, Alejandro Mayorkas, Jew, Dir. of National Intelligence Avril Haines, Jew, Chainman of Council of Economic Advisors Jared Bernstein, Jew, Chief of Staff Jeff Zients, Jew, Senate Majority leader Chuck Schumer, Jew.All of the important departments are controlled by Jews." [29]
- I could go on, but I think the website's search function works plenty well on its own. -- Tamzin[cetacean needed] (they|xe) 06:52, 26 August 2024 (UTC)
- I wouldn't be too worried about impersonation. At [26], Roger Schlafly writes that "There is only one" Roger Schlafly. The blogs he links there shed some further light on his views, by the way:
- @Writ Keeper Off-topic, but you made me curious to look at this subject elsewhere:[30][31] Gråbergs Gråa Sång (talk) 11:06, 26 August 2024 (UTC)
There are times when administrators must act decisively and so I have indefinitely blocked Schlafly as not here to build this particular encyclopedia with its particular policies and guidelines that have resulted in Wikipedia being the #7 website worldwide in terms of pageviews. Other websites have far less stringent and far more biased standards and any editor blocked on Wikipedia is perfectly free to contribute to a website run by a family member, for example, including one that several years back was ranked #18,066 on the internet. Not sure what the 2024 ranking is but highly confident that it is nowhere near #8. Anyway, the blocked editor is free to post there or blog elsewhere, but not here. Cullen328 (talk) 08:10, 26 August 2024 (UTC)
- Good block, thank you. And thanks @Tamzin for the thorough work. FortunateSons (talk) 10:10, 26 August 2024 (UTC)
- Agreed, well within admin discretion, good block and another thanks to Tamzin. Isaidnoway (talk) 11:05, 26 August 2024 (UTC)
- Endorse would have done the same had you not gotten there first. The doubling down linked by Writ Keeper is the only clarity needed. Star Mississippi 11:37, 26 August 2024 (UTC)
- Good block; Schlafly (whoever they might be) has been aiding and abetting the venting of antisemitic deceit at Talk:Leo Frank with persistent WP:IDHT, trolling ("just google it"[32]) and inventions which might generously be described as prompted and eagerly embraced LLM hallucinations, wasting editors' time and effort, and deliberately harmful to the project of building the encyclopedia. Thanks to @Writ Keeper for putting in the work to bring this here. NebY (talk) 12:52, 26 August 2024 (UTC)
- @Cullen328 Just a minor note - the block log references ANI, while this is AN. The Kip (contribs) 15:31, 26 August 2024 (UTC)
- Echoing the thanks all around for this. --JBL (talk) 18:04, 26 August 2024 (UTC)
Battle of Ettangi
[edit]The article Battle of Ettangi should be linked to its Italian wiki it:Battaglia di Ettangi and French wiki fr:Bataille d'Ettangi counterparts, but I can't do it as it seems there is some bug there. Please someone look into this and if possible fix it. Thank you, noclador (talk) 10:24, 26 August 2024 (UTC)