Wikipedia:Administrators' noticeboard/Archive348
Reporting two users for WP:Stalking, WP:Harassing, WP:Canvassing and WP:No personal attacks
editThe following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Good morning,
About one month ago Ermenrich reported me on the page of another user with whom they apparently collaborate frequently. They purposefully avoided to ping me in their report, where they apparently tried to start some kind of argument regarding my edits, though they themselves claimed they couldn't see anything overtly wrong with them (1).
Ever since we had more than one heated discussion, where they always tried to imply that I am some kind of nationalist, or, at any rate, that there was something wrong with my edits, which I assume they don't like for some reason (or maybe they don't like my username, I am not sure).
Meanwhile, I had a conversation with Borsoka at another page. They reported me at ANI, but the case ended in my favor, and I won the argument on the relative page. During our argument, Borsoka took the liberty of stalking my edits and join the other user on the other page against me (2). I would have expected Ermenrich, an experienced user, to say something in this regard. Instead, they joined Borsoka and literally declared themselves my personal stalker(s) (3).
Sure enough, they stalked me to another page, apparently reverting my edits just to revert something I did, just to "be against" (4). Again, I won the argument against them at that talk page (5). In this argument, I also reminded them of their stalking an harassing tendencies again (6).
This, however, did not stop them from stalking me yet again at Mundus (magister militum) (a page I was editing and watching), right after I had discussed this page with another user on another page, in a conversation where they had not been invited (7). At Mundus, they started removing well-sourced content, just because it claimed Turkic etymology for certain words, and also made their first direct accusations of nationalism and "pan-Turkism" (8).
Today, I opened Wikipedia and found that Ermenrich had again called up his friends at the Mundus talk page, perhaps in an attempt to finally win an argument against me (9). This alone qualifies for Wikipedia:Canvassing. But Ermenrich should learn that unless they assume good faith and use reason before criticizing, they will always lose their arguments.
But this latter action of them is not what caused me to open this case at ANI. Indeed, both Borsoka and Ermenrich finally openly accused me. They accused me of sock-pupettry this time (10), (11), 12).
Needless to say, I am not a sock puppeteer, and I am not a nationalist. My edits are in good faith, which these two users lack. They are earnestly harassing me now and I am tired. This is almost racism, because I can't find a reason for all this fury against me unless it's my username (n.b. Giray Altay is a Turkic name. By the way, geniuses, would a bad-faith Turkish nationalist choose a Turkish name?!?!). Ermenrich and Borsoka have already been proven wrong, but this has not stopped them from keep on stalking, harassing, and canvassing against me. EDIT forgot to mention Wikipedia:No personal attacks. Giray Altay (talk) 11:31, 8 December 2022 (UTC)
- This is a big nothing burger of a report: there is no rule I have to ping someone to discuss them on another users talk page if I’m concerned they may be a sock puppet (there isn’t even such a rule if I bring someone to WP:SPI). The OP has continually made accusations of various sorts against me since I first discussed my concerns at Erminwin’s talk page, posting long WP:WALLSOFTEXT.
- After that, I stopped the user from edit warring on a page I’ve been watching for years; I made an edit to a page removing something that was not added by the OP; I pinged two people who have previously edited a little remarked upon page for an opinion [1] [2] (one of whom the OP has previously asked about the page [3]), which I do not believe counts as canvassing.
I will provide diffs later, butthe OP seems to think that they can complain to remove scrutiny of their edits, which show suspicious knowledge of WP policy for a new user.—-Ermenrich (talk) 12:19, 8 December 2022 (UTC)- You focus on minor things, distorting them, and fail to address the chief causes of alarm!
- I have never said you had to ping me, but it would've been nice. That, however, gives the reader of this report a first glimpse into your prejudice, which is what is causing all this trouble. Instead on focusing on that, address Wikipedia:Stalking, Wikipedia:Harassment, Wikipedia:No personal attacks. How long will you keep on stalking and accusing me, reverting my edits on other pages just to be proven wrong? Can you see that yours is disruptive behavior?
- Second, you didn't think I was a sock puppet at first. In fact, you talked about nationalism (1). Whatever. It is clear you didn't assume good faith at all, and wanted to find something wrong against Giray Altay (cf. I thought I’d cleaned up this sort of misuse of etymology in articles for pan-Turkic purposes a long time ago).
- You jumped in at Odoacer against me, misunderstanding my edits, and reverting them without even clearly justifying your actions (I agree that you're edits were not improvements as they are overemphasizing the very disputed idea that Odoacer was a Hun. That's all I have to say 2). Eventually the matter was understood by the other editor involved (the one you jumped in to support just to try an recruit some Tag teammate maybe?), and settled, and your not-very-clear objections dropped. You did not help at all at Odoacer. The other editor did, as he /she, similarly to Erminwin, is interested in practical matters, in improving Wikipedia. You seem only interested in harassing me.
- You did not ping "two people", you pinged editors with whom you are well-acquainted and who supported you in the past (3, 4). This qualifies or WP:Canvassing.
- "which show suspicious knowledge of WP policy for a new user." Now you copy Borsoka (5) and make your second open, personal attack against me (6). Can you see how prejudiced you are against me? It's been more than a month that you put in your head that I am a nationalist, sock puppeteer or whatever (7). You and Borsoka wasted a lot of my time (which I could've spent writing/editing articles) and also the administrators'. Further, you caused me distress. And this is why I decided to come to ANI. Giray Altay (talk) 13:22, 8 December 2022 (UTC)
- You’ve presented no proof I’m stalking you and I’m not going to read this enormous WP:WALLOFTEXT to respond in detail to each of these wild accusations. You are the one who brought this to the admins, not me, so I obviously have not been “wasting their time.”
- It’s strange that you use my edit summary for removing something that was not added by you as proof I am prejudiced against you.—-Ermenrich (talk) 13:40, 8 December 2022 (UTC)
- For the evidence of stalking read here (1). I will not waste yet more time to repeat things to you.
- You forgot again to address harassing and personal attacks. Smart; considering what you did.
- You and Borsoka wasted my time by starting unnecessary, infinite discussions at Erminwin and Samuel Aba, where you argued without common sense, and sure enough lost your arguments. Borsoka took it further, by opening an uncalled for case at the admins (2) which was dismissed (3). You, OTOH, started disruptively editing articles and jump in arguments against me just to undo my edits or Turkic-related stuff on articles I'm working on (3), (4). Even though your objections were dropped at Odoacer, you continued with your tendentious editing ad Mundus, where you also canvassed (5).
- And beside this harassing, you made four personal attacks against me in just 24 h (6, 7, 8, 9), adding to the others done in the past month and a half.
- It’s strange that you use my edit summary for removing something that was not added by you as proof I am prejudiced against you. You edited Mundus, a page I had already edited and was watching (10) after declaring yourself my stalker (11), after expressing your concern regarding Turkic nationalism (12) and right after I had discussed Mundus at Erminwin, in a discussion to which you were not invited and did not participate (13). And sure enough in your edits you made some critic against Turks and expressed your concern regarding Pan-Turkism (14). Your edits at Mundus, in which you got rid of content supported by sources just because it claimed Turkic etymology for a name, look to have derived from your stalking practices and prejudice against Turks and Turkic-named users. Giray Altay (talk) 14:17, 8 December 2022 (UTC)
- It's clear from the above that Giray Altay doesnot understand what a personal attack is. Asking whether anyone finds Giray Altay reminiscent of a sock master on an editor's talk page is not a personal attack (diffs 6, 7) posting that something was likely originally added by sock-master user:WorldCreaterFighter that Giray Altay did not even add to the article is not a personal attack (8), and there is no personal attack in my reply to his accusations made here (9). I am confident that anyone who looks into the other diffs he has posted will find the same disconnect between what is alleged and what the evidence shows.--Ermenrich (talk) 15:34, 8 December 2022 (UTC)
- Personal attack is defined as: Abusive, defamatory, or derogatory phrases based on race, sex, gender identity, sexual orientation, age, religious or political beliefs, disability, ethnicity, nationality, etc.. Wiki's relative article also regards as personal attack: Accusations about personal behavior that lack evidence. Serious accusations require serious evidence, usually in the form of diffs and links. You implied I were a sockpupet and nationalist almost 2 months ago (1, 2), and now accused me of being a sock puppet master without any evidence whatsoever (3).
- And to reply to your previous question (just to lose some more time) the evidence of you stalking is here, you declared it yourself: Well, it seems obvious something's going on here. Any sock-like tendencies recognizable? Otherwise, I guess we should just keep an eye on them. And imperative edit summary of: key an eye on them (4).
- The evidence is in you popping up at Odoacer (5) right after I edited it (6), being the only editor out of 20,000 monthly viewers and 227 page watchers to jump in an argument against me at the talk page (7); the evidence is in you popping up at Mundus (8), which I had just previously edited (9), right after I raised the subject at Erminwin's, in a discussion to which you didn't take part and didn't concern you (10).
- And evidence for stalking against Borsoka is here, when they joined a discussion against me at Erminwin's. They did so during our heated discussion at another page (an argument which they lost, and out of which they started an ANI case that did not end in their favor). They had heretofore never edited on Erminwin's page, and the only possible way to get there was stalking (11). Giray Altay (talk) 16:17, 8 December 2022 (UTC)
- It's clear from the above that Giray Altay doesnot understand what a personal attack is. Asking whether anyone finds Giray Altay reminiscent of a sock master on an editor's talk page is not a personal attack (diffs 6, 7) posting that something was likely originally added by sock-master user:WorldCreaterFighter that Giray Altay did not even add to the article is not a personal attack (8), and there is no personal attack in my reply to his accusations made here (9). I am confident that anyone who looks into the other diffs he has posted will find the same disconnect between what is alleged and what the evidence shows.--Ermenrich (talk) 15:34, 8 December 2022 (UTC)
- "which show suspicious knowledge of WP policy for a new user." Now you copy Borsoka (5) and make your second open, personal attack against me (6). Can you see how prejudiced you are against me? It's been more than a month that you put in your head that I am a nationalist, sock puppeteer or whatever (7). You and Borsoka wasted a lot of my time (which I could've spent writing/editing articles) and also the administrators'. Further, you caused me distress. And this is why I decided to come to ANI. Giray Altay (talk) 13:22, 8 December 2022 (UTC)
- I am still convinced that Giray Altay is not a new editor. New editors are rarely able to quote texts from WP policies. Giray Altay's battle ground mentality is obvious: for them editors are winners or loosers, often with hidden agenda. I did not approach Erminwin on their talk page by chance. After entering into a conversation with Giray Altay, I was sure that other editors must have also concluded that Giray Altay was not here to build an encyclopedia. Borsoka (talk) 16:45, 8 December 2022 (UTC)
- It doesn't matter what the reason for stalking was. You stalked.
- I also have an opinion about you, but I don't stalk, and I keep it to myself, and if I really wanted to vent it, I would use diffs and do it properly. You two are making accusations out of the blue just because my username is Tukic (and maybe also because you lost one argument each against me, so maybe you are sore now). Because, what other reason could it be? All we know is that my username is Turkic, that Ermenrich does not find anything wrong with my edits (1), and that they dislike/are distrustful of Turks and/or have some Pan-Turkism fear complex (2).
- You should think before accusing editors, even if you do it implicitly. Just because I know Wikipedia's policies I am not a new editor? And, is not being a new editor intrinsically wrong? Do you realize that Wikipedia's policies articles are freely available online? Do you realize that people may edit as IP's for years and then create an account? Do you realize that sock puppetry is something done maliciously, but there are users who simply forget the password of their previous account and create another? Do you realize there are people who may change account for a number of reasons which do not have to be malicious?
- But regarding me, I don't even know about the policies, I am reading about them now, if you really want to know.
- Reading and knowing about Wiki's policies is not against any wiki rule. But harassing, tag teaming, stalking, canvassing, and personal attacks are.
EDIT: I may understand the concern about real socks and nationalistic or otherwise malicious editing, but when an editor tells you multiple times they are editing in good faith, and when you see and yourself admit there is nothing wrong with their edits, you have to stop stalking them, harassing them and making personal attacks against them. Giray Altay (talk) 17:04, 8 December 2022 (UTC)
- Obviously it would have been easier to form an opinion on this conflict if Giray Altay had provided a link to the ANI report by Borsoka that they (GA) say ended in their favour, instead of expecting admins to scrabble for it in the multitudinous archives using the lousy AN/ANI search function. I did try, but it was a waste of time. Hint to GA: it's not too late to provide that link now. If you want admins to pay attention to your report, you shouldn't make it so hard for them. But I will nevertheless give my impression of GA's case: no, discussing your possible sockhood on their own pages is not harassment, and if it was, it wouldn't be "almost racism", and you should be very careful with accusations of racism, whether "almost" or not. Also, Ermenrich saying, on another user's page, that "I guess we should just keep an eye on them" cannot be interpreted as "they literally declared themselves my personal stalker(s)", as you say in bold text above. Keeping an eye on a user one believes to be disruptive is allowed here, and is not defined as "stalking". Admins do it all the time. And I agree with Borsoka and Ermenrich that you show remarkable knowledge of some fairly subtle policy wrinkles for a user of less than two months' tenure. You must be a quick study. As for your repeated complaints that Ermenrich fails to assume good faith, that's pretty rich coming from someone who writes "you jumped in to support just to try and recruit some Tag teammate maybe?", with a link to the somewhat notorious Tag team essay. Your general attitude does seem to be battleground, and my general impression is not good. But I'm prepared to change my mind if you do supply the link I've asked for, and if it throws a better light on you than this report does. Bishonen | tålk 17:46, 8 December 2022 (UTC).
- @Bishonen:, I believe the OP is referring to this report at WP:AN3. It did not "end in their favor", the admin, Daniel Case posted:
I can see why tempers are frayed but this does not quite reach (IMO) the level of actionability here. Yet. I really suggest going to AN/I or, better yet, taking some other step like an RFC or noticeboard posting to bring knowledgeable editors in to resolve the underlying dispute about the validity of the sourcing. Without doing that, no actions of any kind against any editors are really going to resolve this.
.--Ermenrich (talk) 17:50, 8 December 2022 (UTC) - I did provide a link to the ANI report (1). but you must've missed it I guess.
- Though I (likely) mistakenly used the words "the case ended in my favor" at first, I later (before this reply of yours) corrected myself and stated that the case was dismissed (2),
- I didn't say it was racism. I said almost racism. Because, user says my edit are ok, then says they are afraid of Pan-Turkism and distrust Turkic users, and my username is Turkic; so well, you know...
- That they literally declared themselves my personal stalkers was humorous. Nonetheless, I did provide diffs attesting that stalking has actually happened (2; 3 and cf. 4 & 5). And that statement may or may not add to it.
- Keeping an eye on a user one believes to be disruptive is allowed here, you've gotta have some reason for this belief. They do not, by their own ammission. (6); and here we go back to wonder the whys and my username comes to mind again.
- I agree with Borsoka and Ermenrich that you show remarkable knowledge of some fairly subtle policy wrinkles for a user of less than two months' tenure. You must be a quick study What is the remarkable fairly subtle knowledge of fairly subtle policy wrinkles? Also: so? Is it a crime to be able to read? Can we go back to no personal attacks and no harassing?
- As for your repeated complaints that Ermenrich fails to assume good faith, that's pretty rich coming from someone who writes "you jumped in to support just to try and recruit some Tag teammate maybe?" Yes, I did say that that may be possible after two months this thing has been going on, this thing which they started, and after they pinged their own friends against me at another page (7).
- But I'm prepared to change my mind if you do supply the link I've asked for, and if it throws a better light on you than this report does if you think this report is bad for me and not for them you might also not argue at all in my favor. Actually, I ask you not to argue for me. Stay in this conversation on their side if you want. But not on mine. Thanks! Giray Altay (talk) 18:23, 8 December 2022 (UTC)
- Sorry but I have to agree with Borsoka and Bishonen. In the first few days of editing Giray Altay was using complex referencing(2nd day of editing)(3rd day of editing), made their own sandbox(6th day of editing), added infobox to an article(2nd day of editing) and introduced galleries of photos over multiple articles (6th day of editing).
- "I agree with Borsoka and Ermenrich that you show remarkable knowledge of some fairly subtle policy wrinkles for a user of less than two months' tenure. You must be a quick study What is the 'remarkable fairly subtle knowledge of fairly subtle policy wrinkles?" "Also: so? Is it a crime to be able to read? Can we go back to no personal attacks and no harassing?"
- Yeah, no. This is clearly, not a new user. --Kansas Bear (talk) 18:47, 8 December 2022 (UTC)
- Kansas Bear As I told Borsoka (1) there are just so many reason why I am able to use Wikipedia, and there are people who are quicker to learn. But this does not justify stalking, harassing, canvassing and personal attacks, and it does not justify you from disregarding the subject of this section and follow them in attempt of argument ad hominem. It doesn't have to be malicious, as those users (those same users who couldn't get it their own way in certain arguments) imply it to be. Also, that wasn't even their problem in the first place. They (actually you) are citing this now, after I complained about something (the subject of this section) which you haven't even attempted to address.
- @Bishonen:, I believe the OP is referring to this report at WP:AN3. It did not "end in their favor", the admin, Daniel Case posted:
- The fundamental problem, even more fundamental than Ermenrich's apparent prejudice and my ability to cite (well, I guess? Considering your comments) in Wikipedia, is that I am new user and they are older users. But neither this justifies such treatment.
- Yes, I missed the AN3 because you called it an ANI report, GA (causing me to waste my time with the ANI archives) and curiously you still do. Anyway, no, that discussion doesn't improve my impression. A detail: if you want to do yourself a favour, stop talking about users "tag teaming" against you, as I see you do repeatedly at the AN3 noticeboard also. It makes a very bad impression, and is the ultimate assumption of bad faith. As for "disregarding the subject of this section" and taking a critical look at your editing, GA, yes, that happens not infrequently at AN and ANI, and is quite appropriate. See WP:BOOMERANG. And criticizing your editing (not your person!) has absolutely zero to do with "ad hominem", what nonsense. Kansas Bear, thank you for your early diffs by GA, they're certainly striking. Bishonen | tålk 20:12, 8 December 2022 (UTC).
- Yes, I missed the AN3 because you called it an ANI report, GA (causing me to waste my time with the ANI archives), mistaking AN3 for ANI, something someone with remarkable knowledge of some fairly subtle policy wrinkles would do, right? By the way, you could've just asked instead of wasting time! You didn't find it: you asked me, I told you. Simple.
- I used "tag teaming" far less often than "harassing", "stalking" and "personal attacks", yet most people here seem reluctant to address those points.
- This is bad faith 1, 2, 3, and this is trying to be practical and work for Wikipedia: 4, 5; but though the users were involved in such kind of constructive conversation, they did not want to participate in them.
- An argument ad hominem is directed against a person (or the editor in this case). Kansas Bear, instead of addressing the issue at hand, joined the other user in an attack against my editing capacities, learning abilities, etc. They could've disagreed with my accusations of stalking, harassing, etc., but should've at least addressed the matter.
- The article WP:BOOMERANG is interesting, but it doesn't change the actions of the other users, and it does not worry me since I know I did nothing wrong. Giray Altay (talk) 20:37, 8 December 2022 (UTC)
- You do realize that you're violating the Law of holes, right? The impression you're giving gets worse and worse with every post you make. If you're lucky, someone will step in and close this discussion before it reaches WP:BOOMERANG proportions. If you're not lucky, it'll stay open, you'll keep on digging, and the end result with be a sanction for you. Beyond My Ken (talk) 23:15, 8 December 2022 (UTC)
- I don't know, I was hoping they would get a sanction or reprimand tbh. Not because I have anything against them. But because all I ever wanted was editing in peace, and I still want this; I met some editors willing to help or at least have a discussion on practical matters, but I also ran across these two editors, who did stalk me and made personal attacks, and I have provided enough diffs to prove that.
- While I can understand Ermenrich may have had some concern a priori in the beginning (because they explained the topic where I edited is subject to nationalist-minded editing and sock-puppetry), Borsoka really just jumped in after things didn't turn out how they wanted. Giray Altay (talk) 23:40, 8 December 2022 (UTC)
- You are obviously unable to understand other editors' motivations. WP is not a battle ground for all of us. Perhaps you should try to accept that other editors are not here to win, but to improve articles. That you wanted to refer to hundreds of pages in German and Hungarian anthologies of various studies and to books published more than a hundred years ago to verify a statement is still a fact. Borsoka (talk) 06:44, 9 December 2022 (UTC)
- No, the matter wasn't that I wanted to refer to hundreds of pages in German and Hungarian anthologies of various studies and to books published more than a hundred years ago. The problem was that you wanted to keep certain information out of the article (an important, subject-related passage from the famous Gesta Hunnorum et Hungarorum by Simon of Kéza). And, judging from the talk page, you attempted do it in the past as well.
- I initially published 4 valid sources to support my addition, but you rejected them with various excuses, including calling the commentary of a 21-st century scholar a primary source. Thus, I retrieved 9 sources to support the claim, and among them there was indeed a source "100 years old", and as soon as you saw it, you started using that as an excuse to keep the aforementioned information out of the article.
- I wasn't on battleground mentality, I wanted to reason with you but you kept rejecting that insertion for no apparent reason, criticizing the sources. Eventually, after the admins took notice of it, the content was finally included in the article.
- The very first words of the WP:Battleground article are: Wikipedia is not a place to hold grudges. However, this is what you did shortly after I begged to differ at Samuel Aba: 1 (n.b. following me to the page of another user, which Borsoka had never edited, to join two other users' conversation against me). So, imo, you should not mention WP.Battleground at all.Giray Altay (talk) 10:59, 9 December 2022 (UTC)
- You do realize that you're violating the Law of holes, right? The impression you're giving gets worse and worse with every post you make. If you're lucky, someone will step in and close this discussion before it reaches WP:BOOMERANG proportions. If you're not lucky, it'll stay open, you'll keep on digging, and the end result with be a sanction for you. Beyond My Ken (talk) 23:15, 8 December 2022 (UTC)
- Need I mention that “following me to the page of another user” to discuss someone’s edits is not stalking? You yourself appear to have followed me to Erminwin’s page originally to complain that I hadn’t pinging you to my discussion with another editor about your edits [4] (why would I?). When I a month later prevented you from reinstating your preferred version without first gaining consensus at Odoacer ([5], [6]), you immediately accused me of stalking and harassing you and acting in bad faith (plus some made up claim that I was reported to an administrator)[7] when I had been following the page for years and hadn’t even been the original one to revert your additions. It’s clear you do have a WP:battleground mentality when you make such (frankly) crazy accusations against someone.—-Ermenrich (talk) 12:41, 9 December 2022 (UTC)
- From Wp:Hounding:
- Hounding on Wikipedia (or "wikihounding") is the singling out of one or more editors, joining discussions on multiple pages or topics they may edit or multiple debates where they contribute, to repeatedly confront or inhibit their work. [...] Hounding usually involves following the target from place to place on Wikipedia.
- And check this 1. Borsoka never edited Erminwin's page before, but had just confronted me on another page.
- I already explained you that I saw your comment about me at Erminwin's because you didn't ping me at our discussion at the Huns, though I had asked you to do so 2. You didn't have to ping me of course (and in fact you never did even after I asked you). It was stupid to ask, and at the time I didn't have the Huns in my watchlist. I loaded your page from the google bar to check if you had replied, instead of the Huns' one, and there I saw your creation of Prolific new editor on Hunnic topics (2).
- I accused you of stalking at Odoacer, because you were the only editor out of over 200 page watchers to join the conversation with me and another user, and you did it against me, maybe, a priori, because in the end me and the other user resolved the misunderstanding, made up and worked together for the article (3). But you never contributed practically to this or any other conversation involving me. Only jumped in to undo my edits; claim I am some other user; etc.
- I had some reason to believe you didn't assume good faith with me, but I openly accused you only after this: 3, 4.
- I didn't accuse you of stalking me just at Odoacer, but also (and chiefly) at Mundus. (cf. 5 and right after 6, 7). But you still haven't addressed the latter. Giray Altay (talk) 14:24, 9 December 2022 (UTC)
- The fundamental problem, even more fundamental than Ermenrich's apparent prejudice and my ability to cite (well, I guess? Considering your comments) in Wikipedia, is that I am new user and they are older users. But neither this justifies such treatment.
- Other than a couple of side comments by Bish and Kansas Bear, there's nothing happening hear other than arguments started elsewhere spilling over into this discussion. I'm going to give this a few more hours to see if someone uninvolved in the initial dispute can propose some solutions we can enforce moving forward. If that doesn't happen, I'm going to close this discussion down, as it is not really generating any useful progress in fixing the dispute. I also don't think we need to hear any more from any of the disputants; if they comment I'll likely close it down even sooner. Let people who are uninvolved disentangle this mess. Otherwise, there's nothing useful going to come from this. --Jayron32 13:17, 9 December 2022 (UTC)
- Frankly I tried to wade through but the walls of text prevented me.
- @Giray Altay, you're very new. When you come to a noticeboard, you need to:
- Have a specific concern that you can back up with diffs provided in your first post
- Write as short as possible. No one wants to read long repetitive explanations. No one is even expected to. Writing shorter takes longer, but it's a skill worth developing if you want to get along here on Wikipedia.
- You also really need to understand policy a lot better than you currently appear to. From the skim I did, I think you're lucky someone hasn't blocked you for repeatedly making after being asked not to what seems like an awful lot of unsupported allegations and assumptions of bad faith. Valereee (talk) 14:39, 9 December 2022 (UTC)
- Conciseness is the greatest talent a person may have, and writing shorter does take longer. I absolutely need to develop this skill.
- I thought I had provided enough diffs; I guess I was wrong. Giray Altay (talk) 15:00, 9 December 2022 (UTC)
- It's not the number. We don't want more diffs, we want ones that really show the problem, accompanied by a ten-word description of the issue. Five great diffs are better than 10 iffy ones, and five good diffs should be sufficient for most concerns. Even one diff that doesn't actually show the problem can make someone who opens that diff first think, "This is nothing. I'm not going to bother with the rest."
- If I were you, I would request this be closed. It's not likely to go anywhere in this shape, it's just way too long, too many diffs added too late, and apparently diffs that don't actually show what they're supposed to show. Go edit somewhere noncontentious for a while, it's really hard to start out at contentious articles. Valereee (talk) 15:10, 9 December 2022 (UTC)
- The patience of administrators never ceases to amaze me.
- With regards to this filing, I do not see anything actionable at this point. I do believe there has been quite enough incivility here to go around but it is something that can be corrected by simply reminding the disputants that this is a community with people from all over the world making edits to this encyclopedia. We are expected to respect each other and assume good faith, even when we believe there is a violation of policy. Our administrators, as an extension of the community, show us this every day. They interact and sanction many tens of hundreds of user and IP accounts every day, protecting the encyclopedia from harm, yet they do not go to user talk pages to make accusations about editors with out providing clear and concise evidence. And they do not allow their personal feelings to rule their actions or read into every comment in an attempt to infer some slight that simply is not there.
- I understand @Giray Altay's feelings when being accused of being a sockpuppet on this project. It is one of if not the worst accusation that can be made about an editor here and can be considered a personal attack of the highest order. I understand their feeling about going to another talk page and seeing two or three editors, that have been reverting their edits, discussing them, regardless of merit. While not necessarily the case, I can see how the OP could misconstrue that as "tag-teaming". I also understand the perspective of @Ermenrich and @Borsoka's positions in the discussions. It can be frustrating to deal with some editors, especially those that dominate discussions and write walls of endless text. I believe this is a case of everyone involved, including the OP, contributing to this spiraling event by minor actions they took and things they said.
- A warning about civility and maintaining the assumption of good faith to all involved is all I see warranted at most. If @Ermenrich truly believes that @Giray Altay is a sockpuppet or master then they should open a SPI case and stop talking about it on other user talk pages. Likewise, @Giray Altay needs to stop accusing other editors of being racist, or some form of it, or tag-teaming against them. --ARoseWolf 15:15, 9 December 2022 (UTC)
- This topic appears to be dying out finally, but I'd like to say this in response to ARoseWolf's comments. While I certainly appreciate that someone might not like being discussed as being a sock puppet, as long as it is unclear who the master is, there's no way to file a report. I believe Kansas Bear has supplied some very convincing evidence that this is not a new user, but since no one can figure out who it is, the only way to advance is to discuss until someone figures something out. It's not like this is being discussed outside talk:Erminwin.--Ermenrich (talk) 14:17, 10 December 2022 (UTC)
- This is exactly the type of mentality that caused all this. You are in bad faith. You have put in your head that I am a Turkish nationalist, sock master or whatever, and now you are willing to waste yours and others time as well. But please do. I don't mind you do it at this point, just don't accuse me again at pages; go and open a report. All this happened even though I told you I am in good faith, told you I am not a sock puppet master, not a nationalist, not doing anything malicious. Even though none of my edits show signs of it (I know it must be so, since I am none of what you accuse me of, nor anything malicious).
- And even if I was a nationalist, a sock puppet master or whatever: it's like I told you: even if I was a Hungarian or Turkish or whatever nationalist, what do you care as long as the contributions are constructive? (1). Let any admin or viewer here look into my edits and see if they find something disruptive; something nationalist-minded, sock-puppet minded, etc.
- You never tried to discuss constructively; you never criticized or assessed my edits; you would ping me or reply to me (when you didn't try to hide it 2) only to make some insinuations against me as a Wikipedia user.
- You didn't just discuss me at other users' pages, you also made open insinuations at public articles (3)
- I believe Kansas Bear has supplied some very convincing evidence that this is not a new user, no they haven't. They provided evidence that I learned to use Wikipedia. They may be able to prove I learn quickly, but they would have to provide some statistics and diffs from other users to do that.
- And besides, it doesn't have to be malicious, you know. I believe that IP address-editors turned into users and people who create new accounts for no malicious reason are pretty common occurrences. Yet you have to use this to fuel your wrong belief that I am doing something wrong. No matter what it is. You don't even know yourself. Giray Altay (talk) 14:39, 10 December 2022 (UTC)
- This topic appears to be dying out finally, but I'd like to say this in response to ARoseWolf's comments. While I certainly appreciate that someone might not like being discussed as being a sock puppet, as long as it is unclear who the master is, there's no way to file a report. I believe Kansas Bear has supplied some very convincing evidence that this is not a new user, but since no one can figure out who it is, the only way to advance is to discuss until someone figures something out. It's not like this is being discussed outside talk:Erminwin.--Ermenrich (talk) 14:17, 10 December 2022 (UTC)
There are backlogs at WP:PERM in at least three sections/categories (AutoWikiBrowser, Page Mover, and Pending Changes Reviewer). Some additional eyes would be appreciated. For full disclosure, I do have a request there myself, but I excluded my own request in evaluating the backlogs. Taking Out The Trash (talk) 21:14, 9 December 2022 (UTC)
- Two of those three always have a backlog. They do not any more. Primefac (talk) 17:08, 10 December 2022 (UTC)
Blanking inactive LTA pages
editHello, I have been reviewing the subpages of Wikipedia:Long-term abuse, blanking and marking as historical LTA pages like this that have been inactive for years. The material is still available in history if there is a need for it. From what I have seen, it is an acceptable practice to blank inactive LTA pages so they won't continue to exist as a shrine giving recognition to long gone vandals from years ago. This search shows 30 pages blanked this way from 2018 onwards excluding the 5 or so I blanked today.
User:331dot asked me to post a notice about this since previously it was usually done by admins. I became interested in this task as it is somewhat related to MalnadachBot task 13 (approved following this) which is to blank warnings and other stale message from inactive IP talkpages. If there is no objections, I will continue with blanking and marking historical. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 10:38, 26 November 2022 (UTC)
- Looks good to me. Thanks for performing this type of maintenance tasks in general. ~ ToBeFree (talk) 11:39, 26 November 2022 (UTC)
- LGTM as well. I have no concerns. --TheSandDoctor Talk 18:09, 26 November 2022 (UTC)
Rescued from archive
editThe above may be OK, but is not ideal. The blanking of LTA pages should be done with visibility at WP:SPI. Ideally, clerking of LTA subpages should be done by accredited SPI clerks. If you are interested in clerking LTA subpages, why not get experienced and accredited at SPI? —SmokeyJoe (talk) 01:28, 4 December 2022 (UTC)
- As an SPI clerk, I have no interest in maintaining LTA subpages and don't particularly care about what happens to them. I suspect most other clerks and CUs feel the same way, which is why there is no policy or guideline about this. I wasn't aware we were accredited, by the way. How much do I have to pay to renew my SPI clerk license? Spicy (talk) 02:33, 4 December 2022 (UTC)
- Your accreditation, trainee and promotion, are recorded in the history of [[this page. It’s helpful to know that SPI clerks have no interest in WP:LTA and this supports the option to shut it down completely. SmokeyJoe (talk) 12:18, 4 December 2022 (UTC)
- LTA subpages have been occasionally helpful to identify some behavior, but I have no strong opinion on them. I think they should generally not be created in the first place, except in cases where it is useful to admins dealing with them. I have checked the list of LTA subpages marked as historical... none of them ring a bell, so I guess there are not relevant to current activity we see at SPI. MarioGom (talk) 09:00, 4 December 2022 (UTC)
- For transparency, here is a list of LTA pages I have blanked. I am not interested in becoming an SPI clerk for a one time sweep. LTA pages, unlike SPI archives, can be created by anyone, so I don't think editing it should be restricted only to them. Any editor in good standing should be able to edit LTA pages and blank inactive ones. It is questionable whether some of them should even exist. Take for example Wikipedia:Long-term abuse/貴花 which was recently created by someone in their very first edit. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 10:55, 4 December 2022 (UTC)
- The lack of interest in clerking LTA, beyond sporadic driveby blanking of its inappropriate content, is a reason to shut LTA down. The creation of a new LTA page by the drive-by SPA is another reason. It is quite concerning, was it created in a WP:game to harass? How would anyone know. If a user’s LTAbuse doesn’t involve any sock puppetry, then why not use their user_talk page? Shut down LTA. SmokeyJoe (talk) 12:25, 4 December 2022 (UTC)
- The disinterest of SPI clerks in LTA pages says nothing about the usefulness of these pages to the rest of us poor benighted souls who don't have advanced permissions and wish to find out about these people when we come across misbehavior. The pages are there for the community, not for the very small number of SPI clerks who, if they're not availing themselves of this information, are only hobbling themselves (and perhaps hurting valid SPI cases).As for the deletion of these pages, I don't understand the purpose - are we running out of storage space? I suggest that the pages already deleted be restored, and if a culling needs to take place, which I doubt, it be done by an admin with more experience. Beyond My Ken (talk) 18:29, 4 December 2022 (UTC)
- Yup, SPI clerks know a lot and stuff, and are good at finding out who to ask, but it's the other people in the trenches who usually know about this stuff. I've been seeing the blanking, and haven't seen anything to complain about. LTAs have a coloured history at MfD, so it may be worth consulting before MfDing any more of them. One of us competent rouge admins might just speedy it. I do think these pages should probably remain categorised under LTA, so we can properly clean them up at some point. Blank uncategorised pages are not a lot of good. -- zzuuzz (talk) 18:42, 4 December 2022 (UTC)
- When I first saw this come up in the original thread I thought exactly what BMK has written: what on earth is the benefit in blanking these pages? I assumed there's some issue that I was unaware of that everyone knew about, that meant that blanking these pages was a good thing. It seems blanking is (a) pointless (b) takes away potentially useful information from the community. I second BMK's suggestion pages already blanked be restored. DeCausa (talk) 18:59, 4 December 2022 (UTC)
- There is I think a persuasive argument that too many pages only serve to glorify or inspire copycats (see WP:DENY). I've seen several LTAs who literally run through the lists joe-jobbing as many old MOs as they can. These pages should be considered a working tool, and if they're no longer useful we may as well get rid. Sometimes vandals do actually go away. -- zzuuzz (talk) 19:07, 4 December 2022 (UTC)
- And sometimes they come back. Do joe-jobbers prefer MO's that appear dormant rather than active? That seems doubtful. Those all seem arguments for not having LTA pages at all rather than blanking older ones. There may be some validity for that but I'm very doubtful that they negate the usefulness of those pages on a day-to-day basis. DeCausa (talk) 19:15, 4 December 2022 (UTC)
- We should only keep pages which are useful, and some of them are useful. I'd encourage a look through the list which was blanked, and ask if they're still around. It's notable (to me at least) in all the ones which were skipped. It seems to have been a well-performed exercise. And yes, on a broad scale, we still get WoW and Grawp copycats to this day, along with some others. -- zzuuzz (talk) 19:23, 4 December 2022 (UTC)
- LTAs that fall in the category of often-copied should have a warning on them to look out for copycats and joe jobs - but it's not possible to disseminate such warnings if there's no page to put it on. Beyond My Ken (talk) 22:51, 4 December 2022 (UTC)
- We should only keep pages which are useful, and some of them are useful. I'd encourage a look through the list which was blanked, and ask if they're still around. It's notable (to me at least) in all the ones which were skipped. It seems to have been a well-performed exercise. And yes, on a broad scale, we still get WoW and Grawp copycats to this day, along with some others. -- zzuuzz (talk) 19:23, 4 December 2022 (UTC)
- And sometimes they come back. Do joe-jobbers prefer MO's that appear dormant rather than active? That seems doubtful. Those all seem arguments for not having LTA pages at all rather than blanking older ones. There may be some validity for that but I'm very doubtful that they negate the usefulness of those pages on a day-to-day basis. DeCausa (talk) 19:15, 4 December 2022 (UTC)
- There is I think a persuasive argument that too many pages only serve to glorify or inspire copycats (see WP:DENY). I've seen several LTAs who literally run through the lists joe-jobbing as many old MOs as they can. These pages should be considered a working tool, and if they're no longer useful we may as well get rid. Sometimes vandals do actually go away. -- zzuuzz (talk) 19:07, 4 December 2022 (UTC)
- When I first saw this come up in the original thread I thought exactly what BMK has written: what on earth is the benefit in blanking these pages? I assumed there's some issue that I was unaware of that everyone knew about, that meant that blanking these pages was a good thing. It seems blanking is (a) pointless (b) takes away potentially useful information from the community. I second BMK's suggestion pages already blanked be restored. DeCausa (talk) 18:59, 4 December 2022 (UTC)
- Yup, SPI clerks know a lot and stuff, and are good at finding out who to ask, but it's the other people in the trenches who usually know about this stuff. I've been seeing the blanking, and haven't seen anything to complain about. LTAs have a coloured history at MfD, so it may be worth consulting before MfDing any more of them. One of us competent rouge admins might just speedy it. I do think these pages should probably remain categorised under LTA, so we can properly clean them up at some point. Blank uncategorised pages are not a lot of good. -- zzuuzz (talk) 18:42, 4 December 2022 (UTC)
- The disinterest of SPI clerks in LTA pages says nothing about the usefulness of these pages to the rest of us poor benighted souls who don't have advanced permissions and wish to find out about these people when we come across misbehavior. The pages are there for the community, not for the very small number of SPI clerks who, if they're not availing themselves of this information, are only hobbling themselves (and perhaps hurting valid SPI cases).As for the deletion of these pages, I don't understand the purpose - are we running out of storage space? I suggest that the pages already deleted be restored, and if a culling needs to take place, which I doubt, it be done by an admin with more experience. Beyond My Ken (talk) 18:29, 4 December 2022 (UTC)
- The lack of interest in clerking LTA, beyond sporadic driveby blanking of its inappropriate content, is a reason to shut LTA down. The creation of a new LTA page by the drive-by SPA is another reason. It is quite concerning, was it created in a WP:game to harass? How would anyone know. If a user’s LTAbuse doesn’t involve any sock puppetry, then why not use their user_talk page? Shut down LTA. SmokeyJoe (talk) 12:25, 4 December 2022 (UTC)
- Yep. Just as a curious aside I can't quite get my head around Spicy's earlier comments that they (and none of the SPI clerks) have any interest in the LTA pages and, more surprisingly, the sarcasm around being "accredited" given what it says in Wikipedia:Sockpuppet investigations/SPI/Clerks. Could they clarify? DeCausa (talk) 00:38, 5 December 2022 (UTC)
- "Accredited" seems like a slightly pompous term for an informal volunteer position on a website. In case it's not clear, the point of my comment was that I don't agree with SmokeyJoe's idea that clerks/CUs should have authority over the community at large in regard to LTA pages. LTA pages were not a part of my clerk training and I'm not aware of any other clerk who uses them on more than a very occasional basis (in my experience, the SPI case archives are usually much more useful). That's all the more reason for these pages to be managed by the community. Spicy (talk) 01:47, 5 December 2022 (UTC)
- I have now reviewed all subpages, haven't blanked any that remotely look useful or active.
no page to put it on
is misleading, they are not deleted and removed completely, only blanked and can be restored if necessary. Of the two joe job targets mentioned above, Grawp is not blanked and Wikipedia:Long term abuse/Willy on Wheels was deleted 12 years ago and salted. The only MFD I have started is for a completely useless page Wikipedia:Miscellany for deletion/Wikipedia:Long-term abuse/Kiyanu Kim. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 04:15, 5 December 2022 (UTC)
- Yep. Just as a curious aside I can't quite get my head around Spicy's earlier comments that they (and none of the SPI clerks) have any interest in the LTA pages and, more surprisingly, the sarcasm around being "accredited" given what it says in Wikipedia:Sockpuppet investigations/SPI/Clerks. Could they clarify? DeCausa (talk) 00:38, 5 December 2022 (UTC)
- LTA is mostly a moribund process; the information there has mostly been subsumed by SPI reports. It feels like LTA was once a more active area of Wikipedia, but it has basically fallen into disuse as any purpose it served has been taken up by other processes. There's a few of the pages I use from time to time mostly for tagging block summaries so any reviewing admin will know the background (such as WP:LTA/VXFC), but otherwise I'd be mostly OK with merging and/or redirecting LTA pages to SPI pages, since that's where most of the active work in the area tends to happen. --Jayron32 14:38, 5 December 2022 (UTC)
- I've never known it to be a "process", since there was no desired immediate outcome to the creation of an LTA page. I've always seen it as informational and educational, for those editors interested in that corner of the community. Beyond My Ken (talk) 23:45, 5 December 2022 (UTC)
- The problem is that, in order to be such, it needs to be actively updated. Otherwise, it's just a memorial to trolls, something we don't do. If we're using the LTA pages and creating new ones and updating them on the regular as a community, then they serve a use beyond simply being a memorial to trolls. However, if we aren't, then it isn't a useful corner of Wikipedia, and whatever small purpose it is currently serving in terms of being "informational" and "educational" could also be served in a part of Wikipedia which is being updated regularly, such as SPI pages. Just as an example as to how moribund most LTA pages are; WP:LTA/VXFC, which is a banned user which has been active as recently as the past week and which has never not been active, has an LTA page which was last updated once in 2021, and 3 times in 2022. Being that it's only seen 4 substantive edits in basically 3 years, it's not really serving its purpose of tracking ongoing long-term abuse. It's just a memorial to VXFC. --Jayron32 13:01, 6 December 2022 (UTC)
- I agree, moribund, not functional, despite some wishful thinking. I think that virtually all long term abuse worth central tracking involves sockpuppettry or editing abusively while logged out while blocked, and so it has negligible scope outside SPI.
- WP:SPI in impressively professional-like and well functioning, and no one at SPI seems able to say that LTA has any known value. LTA is moribund, and we see it being a place of trolling. SmokeyJoe (talk) 21:59, 6 December 2022 (UTC)
- "we see it being a place of trolling" Who is "we"? Beyond My Ken (talk) 02:45, 7 December 2022 (UTC)
- Incidentally, "X is moribund, therefore delete it" is an interesting philosophy. Generally, if there are things on Wikipedia which need to be updated, we -- you know -- update them, we don't "tsk-tsk" and delete them. Beyond My Ken (talk) 02:50, 7 December 2022 (UTC)
- I don't believe I said we should remove all information entirely. I've said we should move the pages to relevant SPI pages, and house it there instead. It's redundant with SPI, and no one is using it. Imagining that some day, some time in the future, someone may use it is not a useful way to run things. We have a way to track long-term trolls that is currently being used many times per day. It's called SPI. Let's just merge the content of the LTA pages with the SPI pages, and get rid of the LTA process as historical. There are many things we used to do at Wikipedia that we have shut down and don't do anymore. That you claim such a thing is so novel as to be confusing to you is beyond-the-pale, given that you've been here as long as as have, if not longer. We shut things down at Wikipedia often enough. For example, Wikipedia:Requests for comment/User conduct, Wikipedia:Mediation Committee, Wikipedia:Association of Members' Advocates. All of these were shut down and marked "historical" or "closed" and we now direct users to other processes instead of trying to use them. My suggestion is we do the same with Wikipedia:Long-term abuse. We mark it historical, merge any relevant cases to SPI, etc. --Jayron32 17:51, 7 December 2022 (UTC)
- Marking something as ""historical" is not what was being discussed - at least, that's not how I understood it. It's deletion I'm opposed to. (About the same, incidentally, first edit with an account: 26 June 2005). Beyond My Ken (talk) 23:29, 8 December 2022 (UTC)
- Well, if you don't have a problem with what I proposed, why did you spend so much energy telling me I was wrong. If you have a problem with deletion, then find the person that proposed deletion and tell that person they are wrong. I proposed merging with SPI and marking LTA as historical. If that's not what you disagree with, then don't argue with me!!! --Jayron32 13:21, 9 December 2022 (UTC)
- Woah, hold on a bit. I'm allowed to disagree with you, I'm even allowed to disagree with what I thought you were saying, and I'm allowed to change directions once I understand what your argument actually is in fact, but chastising me for disagreeing with what the general thrust of the conversation was (exclusive of your contributions) doesn't seem very productive. I did misunderstand you, and I apologize for that. I'm certain if there was ever a real effort to deal with LTAs in connection with SPI you and I could probably agree on some procedure that preserved information in one form or another, but since it seems unlikely that that is going to happen, I don't see much point in expending energy over it. Beyond My Ken (talk) 22:54, 10 December 2022 (UTC)
- Well, if you don't have a problem with what I proposed, why did you spend so much energy telling me I was wrong. If you have a problem with deletion, then find the person that proposed deletion and tell that person they are wrong. I proposed merging with SPI and marking LTA as historical. If that's not what you disagree with, then don't argue with me!!! --Jayron32 13:21, 9 December 2022 (UTC)
- Marking something as ""historical" is not what was being discussed - at least, that's not how I understood it. It's deletion I'm opposed to. (About the same, incidentally, first edit with an account: 26 June 2005). Beyond My Ken (talk) 23:29, 8 December 2022 (UTC)
- I don't believe I said we should remove all information entirely. I've said we should move the pages to relevant SPI pages, and house it there instead. It's redundant with SPI, and no one is using it. Imagining that some day, some time in the future, someone may use it is not a useful way to run things. We have a way to track long-term trolls that is currently being used many times per day. It's called SPI. Let's just merge the content of the LTA pages with the SPI pages, and get rid of the LTA process as historical. There are many things we used to do at Wikipedia that we have shut down and don't do anymore. That you claim such a thing is so novel as to be confusing to you is beyond-the-pale, given that you've been here as long as as have, if not longer. We shut things down at Wikipedia often enough. For example, Wikipedia:Requests for comment/User conduct, Wikipedia:Mediation Committee, Wikipedia:Association of Members' Advocates. All of these were shut down and marked "historical" or "closed" and we now direct users to other processes instead of trying to use them. My suggestion is we do the same with Wikipedia:Long-term abuse. We mark it historical, merge any relevant cases to SPI, etc. --Jayron32 17:51, 7 December 2022 (UTC)
- The problem is both WP:DENY and WP:BEANS. If we really updated LTA pages with as much information as possible, it would become a troll memorial (a WP:DENY problem), and also a guide of trolling ideas and block evasion techniques (a WP:BEANS problem). That being said, some LTA pages of prolific sockmaster who have been active in recent years are sometimes useful. Not every day, but occasionally they are. MarioGom (talk) 17:21, 7 December 2022 (UTC)
- Prolific sockmaster? Why is not covered by SPI? SmokeyJoe (talk) 12:14, 10 December 2022 (UTC)
- DENY is not working well if it leads to regular editors losing useful info. The practice of not tagging sock accounts already leads to issues in gaining a good understanding of any particular case, deleting LTA pages would make that task even more inaccessible. CMD (talk) 13:10, 10 December 2022 (UTC)
- The problem is both WP:DENY and WP:BEANS. If we really updated LTA pages with as much information as possible, it would become a troll memorial (a WP:DENY problem), and also a guide of trolling ideas and block evasion techniques (a WP:BEANS problem). That being said, some LTA pages of prolific sockmaster who have been active in recent years are sometimes useful. Not every day, but occasionally they are. MarioGom (talk) 17:21, 7 December 2022 (UTC)
- The problem is that, in order to be such, it needs to be actively updated. Otherwise, it's just a memorial to trolls, something we don't do. If we're using the LTA pages and creating new ones and updating them on the regular as a community, then they serve a use beyond simply being a memorial to trolls. However, if we aren't, then it isn't a useful corner of Wikipedia, and whatever small purpose it is currently serving in terms of being "informational" and "educational" could also be served in a part of Wikipedia which is being updated regularly, such as SPI pages. Just as an example as to how moribund most LTA pages are; WP:LTA/VXFC, which is a banned user which has been active as recently as the past week and which has never not been active, has an LTA page which was last updated once in 2021, and 3 times in 2022. Being that it's only seen 4 substantive edits in basically 3 years, it's not really serving its purpose of tracking ongoing long-term abuse. It's just a memorial to VXFC. --Jayron32 13:01, 6 December 2022 (UTC)
Possible fake "Wikimedian In Residence" user accounts
editI have noticed the recent proliferation of a number of user accounts where the user self-describes as the "Wikimedian In Residence" at some institution, then lists a set of "interests"; what caught my eye is the repetition in form from these supposedly unrelated accounts, such as:
User:VidEwan: Hi, my name is Ewan and I work at the University of Edinburgh as the Wikimedian in Residence. I'm interested in writing articles about film, Scotland and the suffragettes.Resolved as ok. BD2412 T 14:39, 2 December 2022 (UTC)- User:Vaishnodevimandir: Hi, my name is Elly and I work at the University of Texas at Austin as the Wikimedian in Residence. I'm interested in writing articles about film, Scotland, Activists and the suffragettes.
- User:Skmagar1500: Hi my name is ewan and i study at the University of Edinburgh as the wikimedian in residence. I am intrested in writing articles about film,Scotland and the suffragettes.
- User:Fightersword: Hi, my name is Tom Peter and I work at the University of Edinburgh as the Wikimedian in Residence. I'm interested in writing articles about film, Scotland, Activists and the suffragettes.
- User:DonJovanie: Hi, my name is Don and I work at the University of San Diego as the Wikimedian in Residence. I'm interesting in writing articles about musician, film, and the suffragettes.
- User:Hiteshsagarjatav: Hi, my name is Hitesh Sagar Jatav. I am working at Bloomberg as the Wikimedian in Residence. I am interested to writing articles in technology, religion, music and India.
- User:Sayeedsam1234: Hi My Name Is Sahim Haneef And I Work At Digital Company As The Wikimedian In Residence I'm Interested In Writing Articles About Film, Graphic, Animation & Photoshop Tricks.
Unless there is some training program for Wikimedians In Residence that instructs editors to introduce themselves in this way, I think we're looking at some kind of account farm. Also, that's an unusual amount of interest in "the suffragettes". BD2412 T 15:42, 1 December 2022 (UTC)
- @Stinglehammer: As you appear to be (or have been) a legitimate Wikimedian in Residence at the University of Edinburgh, can you speak to the three accounts claiming that role above? Cheers! BD2412 T 15:48, 1 December 2022 (UTC)
- I ran a quick check (I have to run, so I can't do as much digging as I'd like to right now). Vaishnodevimandir and Fightersword are Confirmed to each other, and Vaishnodevimandir's creations look a lot like UPE. Blocked those two. --Blablubbs (talk) 15:59, 1 December 2022 (UTC)
- The others haven't edited in 2-4 years, so there's no rush in dealing with them. At this point, I'd guess they're 99% likely to be the same person (or using the same tactic). Good catch, BD2412. But what did you mean about a "recent proliferation"? All but the two blocked accounts are years old. --Floquenbeam (talk) 16:04, 1 December 2022 (UTC)
- First impression - the two new ones were the first two that I came across. BD2412 T 16:16, 1 December 2022 (UTC)
- Someone experienced in UPE might want to look at active editor User:Scoffworld, who has a few similarities of user page, and has recreated at least one article that shows up in the deleted contribs of one or two of the accounts above. Image in the article is claimed to have been taken by Scoffworld. I'll notify them after I save this edit. Floquenbeam (talk) 16:19, 1 December 2022 (UTC)
- Thanks for flagging this. My main account is User:Stinglehammer but I have other training accounts User:EMcAndrew and User:VidEwan for when I am creating video tutorials. So VidEwan is one of my accounts. I'll add some text to make that clearer. The other ones are interesting/problematic. During training, I do advise to add an introductory sentence of text to a) make sure we have content to turn the user page into a blue clickable link b) to provide transparency about someone's affiliations/motives for editing and any potential COI and c) I also demo how to create a short bullet pointed list of approx 2-3 things they are interested in editing about again for transparency. What's striking is that we have obviously written about Scotland and the Scottish suffragettes at the University of Edinburgh during my tenure to date and I do use my own userpage as a base exemplar. But they are instructed not to replicate but make their own. Clearly one or two here have just copied my base userpage too literally. which is obviously problematic. Can we ask them to remove clearly misleading/factually incorrect info or am I legitimated to edit these userpages in this case? not sure how active they are for instance and I don't want too many of these existing and causing confusion. Stinglehammer (talk) 17:01, 1 December 2022 (UTC)
- NB: looks like they are replicating what I demo in a 2018 video tutorial. I can mothball/archive that video tutorial if it is causing issues as we have newer video resources now which might be better in any case. Stinglehammer (talk) 17:09, 1 December 2022 (UTC)
- @Stinglehammer: Thanks for the clarification on that point. When I see a number of accounts created following a pattern such as this, my mind jumps to bots, an unfortunate effect of the times we live in. BD2412 T 14:41, 2 December 2022 (UTC)
- NB: looks like they are replicating what I demo in a 2018 video tutorial. I can mothball/archive that video tutorial if it is causing issues as we have newer video resources now which might be better in any case. Stinglehammer (talk) 17:09, 1 December 2022 (UTC)
- Having been a proper WiR in the past (Royal Society and Cancer Research UK), one problem is that there is no real control over the title. At WMUK some 10 years ago there were discussions about trying to at least assert an "official" status for the ones WMUK supported and usually paid (or the host institution or a charity did). But it was decided not to do this, so in effect anyone can claim the title - I don't think there is any legal restriction on doing so, just in terms of using the name. You can see from User:Pigsonthewing's (Andy Mabbett) user page that he has done a number of these, some paid some not, without asking anyone's permission first (and without causing significant problems afaik). Johnbod (talk) 17:20, 1 December 2022 (UTC)
My mistake, mixed up two people, apologies. Fram (talk) 14:26, 2 December 2022 (UTC) |
---|
The following discussion has been closed. Please do not modify it. |
|
While I'm still struggling to understand the difference between my Wikimedian residences and being "a proper WiR", I can state categorically that I have never claimed to be a Wikimedian in Residence at any institution without first gaining the appropriate permission to do so. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:51, 3 December 2022 (UTC)
- My recollection from when I was on the WMUK board is that we only heard of some of yours when you announced them. Who did you get "the appropriate permission" from? Johnbod (talk) 04:45, 7 December 2022 (UTC)
- The meta:Wikimedians in Residence Exchange Network is the peer to peer regulatory organization, to the extent that any standards exist. There are no formal processes there but sometimes organizations write in asking for guidance about whether a user is in good standing to be hired as a Wikimedian in Residence, or for information about recruiting one. The majority of active Wikimedians in Residence have participated in the activities of that organization, and it is the only organization with any standing to speak for the community. I posted notice of this on the talk page there. Bluerasberry (talk) 18:16, 9 December 2022 (UTC)
- WREN is not a regulatory organization, has no authority to act as a regulatory organization, and nor does its page on meta make any claims to that effect. On that page, the section "Mission and Goals" says in full:
"The Wikimedians in Residence Exchange Network advocates for Wikimedia community members in professional or volunteer roles at institutions.
. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:08, 11 December 2022 (UTC)
"Goals of the organization include defining and protecting the common elements of the Wikimedian in Residence role, creating a peer support network which invites new and experienced Wikimedians in Residence to find each other for collaboration, and to encourage a global professional environment which inspires institutions to offer appointments to persons to engage with Wikimedia projects."
- WREN is not a regulatory organization, has no authority to act as a regulatory organization, and nor does its page on meta make any claims to that effect. On that page, the section "Mission and Goals" says in full:
Topic Ban (User:Arif80s)
editAm I still topic banned. Arif80s (talk) 05:40, 5 December 2022 (UTC)
- Yes, unless you appealed it successfully (you would certainly know of the appeal, and should be able to find it, if this is the case). The discussion you linked to doesn't state the ban is temporary, which makes it indefinite (appealable, but forever unless successfully appealed). Your ban is also listed at Wikipedia:Editing restrictions Animal lover |666| 05:56, 5 December 2022 (UTC)
- Respected, I am not happy with this decision. In my view, this decision is contrary to Wikipedia's policies. This decision of the English Wikipedia will hurt the trust of users. Since we are from a country where most of its users do not have much understanding of the English Wikipedia's rules and policies, I am of the opinion that the English Wikipedia should not make such tough decisions and lift my ban soon as possible. thanks Arif80s (talk) 06:26, 5 December 2022 (UTC)
- What decision? Your indefinite topic ban is over 4.5 years old so it's well past time to get over any unhappiness with it. The fact that an indefinite topic ban lasts until it is successfully appealed is something that in some ways predates Wikipedia and isn't even really a 'decision' more a matter of definitions. I'd note that the 3 months minimum before any appeals is over 4 years past so you can appeal at anytime. However you will need to convince the community that 4.5 years later you now understand our policies and guidelines and whatever problems that got you topic banned are unlikely to reoccur. A good way to demostrate this to the community is simply via your editing. Again, it's been over 4.5 years. And the scope of your topic was very narrow, there was nothing stopping you creating well sourced and overall excellent articles that are basically FA quality, related to Pakistan or whatever, even with the topic ban in place. If you have done so, it would like make your appeal very simple. If you haven't, I'm not sure why the community is at fault for that, since your topic ban shouldn't have stopped you. Nil Einne (talk) 12:11, 5 December 2022 (UTC)
- P.S. For clarity I'm not saying you must write FAs for an appeal to succeed. I'm saying that it would definitely help, and more importantly although you seem to be presenting our restrictions on you as some make unfairness and loss to Wikipedia they are actually very limited. And they should not be stopping you making some of the best contributions any editor can make to Wikipedia even when it comes to your country. Indeed the loss to us from restricting you in that way even if it's no longer needed is surely very limited (which doesn't mean we should continue them if it's not) and the loss to you should really be seen that way too. Nil Einne (talk) 12:24, 5 December 2022 (UTC)
- It has certainly been long enough to allow an appeal. I'd recommend that you look over your behavior leading up to the ban, and write a convincing statement why the ban is no longer necessary. If it succeeds, then an admin will officially unban you. If it's unsuccessful, read the opposing comments and figure out how to fix your own behavior over the next few months to increase your chances of success next time. Animal lover |666| 14:01, 5 December 2022 (UTC)
- Did you take my opinion before making a decision? Don't you see the bias of the few users? Was it a big enough deal to ban on me and 3 other users?--Arif80s (talk) 06:12, 6 December 2022 (UTC)
- I didn't make the decision. It was made in the discussion you linked to. I'm simply following it. And 4 years after it was closed you can't claim the closure was incorrect. Animal lover |666| 06:57, 6 December 2022 (UTC)
- Thanks Animal lover. I am addressing to administrators of Eng Wiki not you. Arif80s (talk) 07:22, 6 December 2022 (UTC)
- This was not a decision of an individual admin (by the way, the closing admin left Wikipedia 4 months after that discussion). It was concensus of all the users who participated in that discussion. You will need to convince enough users to establish a consensus that it's no longer needed. Animal lover |666| 08:18, 6 December 2022 (UTC)
- Neither will I appeal nor will I work on the English wiki. You are reducing your users. Congratulations. Arif80s (talk) 10:19, 6 December 2022 (UTC)
- Given that you've made only a sporadic handful of edits in the years since that topic ban (including a couple after you said you would no longer work on the English Wikipedia), and just a few hundred before then, I expect we'll manage. What would genuinely "hurt the trust of users" would be to have policies we did not enforce. Editors are just as bound by Wikipedia's policies and rules as visitors to your own country are bound by those laws, however strange they may be to foreigners. (I don't expect, for example, that your country would waive its blasphemy laws for my benefit, however much the criminalization of blasphemy is a strange and deplorable concept to Americans.) Ravenswing 17:32, 11 December 2022 (UTC)
- Neither will I appeal nor will I work on the English wiki. You are reducing your users. Congratulations. Arif80s (talk) 10:19, 6 December 2022 (UTC)
- This was not a decision of an individual admin (by the way, the closing admin left Wikipedia 4 months after that discussion). It was concensus of all the users who participated in that discussion. You will need to convince enough users to establish a consensus that it's no longer needed. Animal lover |666| 08:18, 6 December 2022 (UTC)
- Thanks Animal lover. I am addressing to administrators of Eng Wiki not you. Arif80s (talk) 07:22, 6 December 2022 (UTC)
- I didn't make the decision. It was made in the discussion you linked to. I'm simply following it. And 4 years after it was closed you can't claim the closure was incorrect. Animal lover |666| 06:57, 6 December 2022 (UTC)
- Did you take my opinion before making a decision? Don't you see the bias of the few users? Was it a big enough deal to ban on me and 3 other users?--Arif80s (talk) 06:12, 6 December 2022 (UTC)
- It has certainly been long enough to allow an appeal. I'd recommend that you look over your behavior leading up to the ban, and write a convincing statement why the ban is no longer necessary. If it succeeds, then an admin will officially unban you. If it's unsuccessful, read the opposing comments and figure out how to fix your own behavior over the next few months to increase your chances of success next time. Animal lover |666| 14:01, 5 December 2022 (UTC)
- P.S. For clarity I'm not saying you must write FAs for an appeal to succeed. I'm saying that it would definitely help, and more importantly although you seem to be presenting our restrictions on you as some make unfairness and loss to Wikipedia they are actually very limited. And they should not be stopping you making some of the best contributions any editor can make to Wikipedia even when it comes to your country. Indeed the loss to us from restricting you in that way even if it's no longer needed is surely very limited (which doesn't mean we should continue them if it's not) and the loss to you should really be seen that way too. Nil Einne (talk) 12:24, 5 December 2022 (UTC)
- What decision? Your indefinite topic ban is over 4.5 years old so it's well past time to get over any unhappiness with it. The fact that an indefinite topic ban lasts until it is successfully appealed is something that in some ways predates Wikipedia and isn't even really a 'decision' more a matter of definitions. I'd note that the 3 months minimum before any appeals is over 4 years past so you can appeal at anytime. However you will need to convince the community that 4.5 years later you now understand our policies and guidelines and whatever problems that got you topic banned are unlikely to reoccur. A good way to demostrate this to the community is simply via your editing. Again, it's been over 4.5 years. And the scope of your topic was very narrow, there was nothing stopping you creating well sourced and overall excellent articles that are basically FA quality, related to Pakistan or whatever, even with the topic ban in place. If you have done so, it would like make your appeal very simple. If you haven't, I'm not sure why the community is at fault for that, since your topic ban shouldn't have stopped you. Nil Einne (talk) 12:11, 5 December 2022 (UTC)
- Respected, I am not happy with this decision. In my view, this decision is contrary to Wikipedia's policies. This decision of the English Wikipedia will hurt the trust of users. Since we are from a country where most of its users do not have much understanding of the English Wikipedia's rules and policies, I am of the opinion that the English Wikipedia should not make such tough decisions and lift my ban soon as possible. thanks Arif80s (talk) 06:26, 5 December 2022 (UTC)
Range block for mobile editor, vandalising NHL team pages
editA mobile editor with a 2604... 2605... range, has been messing with the owners section in the infoboxes of all 32 NHL team pages, for several months. Is a range block possible? or will attempting to get long term semi-protection of those 32 pages, be required. GoodDay (talk) 16:04, 13 December 2022 (UTC)
- Some diffs might help work out the ranges - or at least some links to the articles involved. (I'm afraid I don't know what the NHL is, or what the teams in it are called...). Girth Summit (blether) 18:55, 13 December 2022 (UTC)
- Yeah, you're going to have to help us here. I looked at 6 different NHL teams and only found 2607:FEA8:E99F:9610:0:0:0:0/64 which I have blocked for a year, and that's not a 2604 or 2605 IP. Black Kite (talk) 19:04, 13 December 2022 (UTC)
- I went a few months back through the history of the articles for the teams in the Western Conference (NHL) and found a few patterns. First, the cases I saw:
- 2605:B100:710:938E:F544:AB8A:8F80:37C8 (talk · contribs · WHOIS) (geolocates to Calgary), Chicago Blackhawks, 28 October adds Evander Kane
- 2604:3D09:6188:FB00:38DB:5863:2859:8D28 (talk · contribs · WHOIS) (Calgary), Calgary Flames, 30 October changes owner to Connor McDavid
- 2600:6C4A:7B7F:7CCD:DCAF:B441:EC29:6E70 (talk · contribs · WHOIS) (Denver), Dallas Stars, 31 October changes owner to Anthony Mantha
- 156.57.148.150 (talk · contribs · WHOIS) (Halifax), Vancouver Canucks, 11 November adds Mike Hoffman (I assume they meant this one), this was self-reverted a minute later
- 2600:1700:2DF0:1450:B9F5:785A:3D57:60A5 (talk · contribs · WHOIS) (Atlanta), Edmonton Oilers, 21 November changes owner to Andrei Svechnikov
- And then, Nashville Predators on 2 November, mostly changing the owner to Leon Draisaitl:
- 23.17.161.46 (talk · contribs · WHOIS) (St. Paul, Alberta) [8]
- 24.65.73.226 (talk · contribs · WHOIS) (Edmonton) [9]
- 68.150.98.76 (talk · contribs · WHOIS) (Edmonton) [10][11]
- 96.52.46.255 (talk · contribs · WHOIS) (Edmonton) [12][13]
- 204.83.140.89 (talk · contribs · WHOIS) (Regina) [14]
- 2605:8D80:461:F76B:DCD5:AFDD:D7DE:1DFC (talk · contribs · WHOIS) (Toronto) [15]
- And finally, 2604:3D09:7189:1E00:300B:A671:9889:D079 (talk · contribs · WHOIS) (Calgary) [16] on 13 December
- So, what's the point here? Well, these are all opposing players, so I guess the joke is that they "owned" the other team in the slang sense (see definition #5 here if you don't understand). Note how shortly before the vandalism, the team that the player is on beat the team whose page is modified (e.g. Oilers def. Predators on 1 November). From the diverse locations, teams/players affected, and timing, I'm guessing this is a group of friends or online community that is vandalizing these pages, not a single user. As for what to do about it...just whack-a-mole I guess. There are often IP editors making reasonable contributions and updates on sports team pages in general (including these NHL ones), so wholesale protection is probably not useful. Nashville Predators could have used a short semi on the 2nd, but it's probably not worthwhile at this point (although they did just play the Oilers again yesterday, so maybe). ansh.666 20:34, 13 December 2022 (UTC)
- The third definition of "own" applies even more that the fifth:
To defeat or embarrass; to overwhelm. I will own my enemies. If he wins, he will own you.
I am not a big team sports fan but I have a few professional sports teams on my watchlist, and have seen this pattern of vandalism three or four times previously. Not just hockey but basketball, NFL football and baseball as well. Team A beats Team B, and the vandal replaces the real owner of Team B with the star player of Team A. Now, sometimes wealthy pro athletes do buy teams. But it takes about 30 seconds on Google to verify that most of these so-called purchases are spurious. Cullen328 (talk) 01:55, 14 December 2022 (UTC)
- The third definition of "own" applies even more that the fifth:
Would permanent semi-protection of all 32 NHL team pages, be too drastic? GoodDay (talk) 04:51, 14 December 2022 (UTC)
- I do not think that is called for. Good faith IP editors frequently make productive improvements to professional sports team articles, and this specific problem is not limited to National Hockey League team articles. Maybe our brilliant edit filter coders can develop a filter that draws human attention to team ownership edits to professional sports teams. I do not have the technical expertise to evaluate whether this is possible. It is not a gigantic number of articles. There are 30 Major League Baseball teams, 30 National Basketball Association teams, 32 National Football League teams and 32 National Hockey League teams. So, only 124 articles are subject to this type of vandalism as identified so far. Most are in the United States but some are in Canada. Cullen328 (talk) 05:15, 14 December 2022 (UTC)
- Yeah, far too drastic. These are pretty heavily trafficked and watched pages, so this type of childish vandalism is caught and reverted quickly. There are far more useful IP edits than bad edits as well, so it would probably end up being pretty counterproductive. Also, obviously, there isn't an issue during the offseason (the NHL season started in October, and there wasn't anything from before that). ansh.666 10:12, 14 December 2022 (UTC)
Help needed rescuing edit filter false positives
editDue to a misconfigured edit filter, for 2 hours and 23 minutes we blocked most edits by new users containing the letter "j". I've been going through the hits, most of which are net-positive edits and should be restored, but it's slow going, and I was wondering if I could get some help. User:Suffusion of Yellow/effp-helper.js makes it just two clicks to proxy a filter-blocked edit, so with a few people we could clear this backlog quickly. Posting here as it's a private filter and thus only admins and edit filter helpers can do this. (Will cross-post to EFN.) -- Tamzin[cetacean needed] (she|they|xe) 05:46, 12 December 2022 (UTC)
- Made it through the first 150... so all of 16 minutes. It's tedious, but rescued a few full articles in the process! If anyone wants to pick up where I've left off, that'd be here. -- Tamzin[cetacean needed] (she|they|xe) 06:37, 12 December 2022 (UTC)
- This is a good opportunity to remind folks that it is not recommended to make changes to filters which are set to disallow without using the AbuseFilter's testing functionality or at least first dropping back to log-only temporarily. It's very easy to make a mistake :) Sam Walton (talk) 10:55, 12 December 2022 (UTC)
- I dropped a note at WP:EFN but there's a userscript to help do a FP check before saving. (Posting here too for more awareness, it's a useful script to have; I'd recommend it to all EFMs) ProcrastinatingReader (talk) 11:02, 12 December 2022 (UTC)
- Don't we have a page wherein are memorialized great feats of klutziness like the time someone deleted the Main Page? EEng 15:34, 12 December 2022 (UTC)
- @eeng: what, this one? lettherebedarklight晚安 15:37, 12 December 2022 (UTC)
- That is indeed the one. EEng 15:47, 12 December 2022 (UTC)
- @eeng: what, this one? lettherebedarklight晚安 15:37, 12 December 2022 (UTC)
- Don't we have a page wherein are memorialized great feats of klutziness like the time someone deleted the Main Page? EEng 15:34, 12 December 2022 (UTC)
- I dropped a note at WP:EFN but there's a userscript to help do a FP check before saving. (Posting here too for more awareness, it's a useful script to have; I'd recommend it to all EFMs) ProcrastinatingReader (talk) 11:02, 12 December 2022 (UTC)
- Sorry for the schadenfreude, but I can only chuckle at the WP:DDMP-level silliness of disallowing all edits with the letter "j". Brilliant. --Jayron32 16:20, 12 December 2022 (UTC)
- @ayron32: Don't Say Jay? -- Tamzin[cetacean needed] (she|they|xe) 17:02, 12 December 2022 (UTC)
- 😆--Jayron32 17:06, 12 December 2022 (UTC)
- Seems to me like it's time to dust off the old WP:STOCKS - if those responsible are in support, of course. casualdejekyll 17:49, 12 December 2022 (UTC)
- In the 21st century, people only go in the stocks with their consent. EEng 06:32, 14 December 2022 (UTC)
- Don't threaten me with a good time... --Jayron32 15:41, 14 December 2022 (UTC)
- In the 21st century, people only go in the stocks with their consent. EEng 06:32, 14 December 2022 (UTC)
- @ayron32: Don't Say Jay? -- Tamzin[cetacean needed] (she|they|xe) 17:02, 12 December 2022 (UTC)
Contentious topics procedure adopted
editThe Arbitration Committee has concluded the 2021-22 review of the contentious topics system (formerly known as discretionary sanctions), and its final decision is viewable at the revision process page. As part of the review process, the Arbitration Committee has resolved by motion that:
The above proposals that are supported by an absolute majority of unrecused active arbitrators are hereby enacted. The drafting arbitrators (CaptainEek, L235, and Wugapodes) are directed to take the actions necessary to bring the proposals enacted by this motion into effect, including by amending the procedures at WP:AC/P and WP:AC/DS. The authority granted to the drafting arbitrators by this motion expires one month after enactment.
The Arbitration Committee thanks all those who have participated in the 2021-22 discretionary sanctions review process and all who have helped bring it to a successful conclusion. This motion concludes the 2021-22 discretionary sanctions review process.
This motion initiates a one-month implementation period for the updates to the contentious topics system. The Arbitration Committee will announce when the initial implementation of the Committee's decision has concluded and the amendments made by the drafting arbitrators in accordance with the Committee's decision take effect. Any editors interested in the implementation process are invited to assist at the implementation talk page, and editors interested in updates may subscribe to the update list.
For the Arbitration Committee, KevinL (aka L235 · t · c) 21:42, 14 December 2022 (UTC)
- Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard § Contentious topics procedure adopted
- A "tl;dr" summary would be appropriate, please. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:30, 15 December 2022 (UTC)
Undeclared paid editing?
editI was mentioned in this tweet, apparently due to Commons deletion, but it looks like we have undeclared paid editing here. May be administrators more experienced in handling these issues could have a look. Ymblanter (talk) 06:52, 15 December 2022 (UTC)
- There may be undeclared COI (paid or unpaid) editing as well, but that tweet looks like it is talking about commissioning an artwork to be created and then complaining that it keeps getting taken down from commons as having inadequate permissions. If so, the permissions are a matter for commons rather than here and paying for an artwork is not problematic from our point of view. —David Eppstein (talk) 08:01, 15 December 2022 (UTC)
- I see, this makes sense. Thanks. Ymblanter (talk) 08:26, 15 December 2022 (UTC)
- Hmm, I thought Ymblanter was talking about this SPA, who seems to show a very determined interest in Connor Ratliff. Justlettersandnumbers (talk) 15:54, 15 December 2022 (UTC)
- Yes, I actually thought this is the same person as mentioned in the tweet. Ymblanter (talk) 15:59, 15 December 2022 (UTC)
- That's why I suggested there may be undeclared COI as well. —David Eppstein (talk) 17:19, 15 December 2022 (UTC)
- Yes, I actually thought this is the same person as mentioned in the tweet. Ymblanter (talk) 15:59, 15 December 2022 (UTC)
- Hmm, I thought Ymblanter was talking about this SPA, who seems to show a very determined interest in Connor Ratliff. Justlettersandnumbers (talk) 15:54, 15 December 2022 (UTC)
- I see, this makes sense. Thanks. Ymblanter (talk) 08:26, 15 December 2022 (UTC)
Range block or edit filter
editHi all - this concerns Wikipedia:Sockpuppet investigations/Leaves38, and Special:Contributions/2402:D000:811C:0:0:0:0:0/48. Long story short - this user is adding copyright violations in form of puffy content from a book at lots of different articles, mostly (but not exclusively) in the Sri Lanka subject area. They started out as User:Leaves38, but are now bouncing around the /48 IP range doing the same stuff. They've ignored my attempts to reach out to them on the account's talk page. I could put a range block in place, but the collateral would be non-zero. Is this something a clever person could do something about with an edit filter? Girth Summit (blether) 15:50, 14 December 2022 (UTC)
- I'd like to have another set of eyes look at the range before we make a decision, but when I look at it, I see a mix of editing that may be indicative of multiple users. It's pretty varied in subject area and style, and some of the edits don't appear to be from Leaves38, though others are. Can someone check my analysis? I'm not against blocking, but I also don't want to pull the trigger on the rangeblock if it's being used by constructive editors as well. --Jayron32 16:22, 14 December 2022 (UTC)
- This is what I mean about non-zero collateral. This has to be stopped, but there are other people using the range for sure - if a filter could catch it, without inconveniencing those people, I'd prefer that, but I'm not a big whizz on what filters can do. Girth Summit (blether) 23:13, 14 December 2022 (UTC)
- I'm in agreement that there's definitely editing by others than Leaves38 on the talk. I imagine that one could create a filter that checks to see if some any X-word-long string from the full text of the document was pasted into an article, but I feel like this probably would run into technical limitations (my understanding is that filters can only check so many conditions in one edit, and we wouldn't want it to check a large number like this . It might be better to outsource it to somethink akin to a special-purpose bot that's like XLinkBot that would check to see if any long strings from the source text were copied, and revert when an editor first introduces the copyvio to a page. This doesn't seem like it would be terrible to write in Python; my only concern would be about whether it's worth the community effort to have something like this go through RFBot if we're essentially dealing with a single user. — Red-tailed hawk (nest) 08:46, 15 December 2022 (UTC)
- In the absence of any alternative proposals, and with the issue continuing, I have blocked the range for two weeks. Girth Summit (blether) 13:09, 16 December 2022 (UTC)
- That's probably for the best. I just responded to a WP:RFPP situation related to this, and I think it was from the same range. Sometimes the unpleasant thing needs to be done. --Jayron32 13:28, 16 December 2022 (UTC)
Is it possible to restore the old delete article? Harry Kane is now the current joint top scorer for England with Wayne Rooney(List). I asked on WT:Football two days ago but got no response. So please, can anyone help? Provide an answer? Govvy (talk) 10:30, 14 December 2022 (UTC)
- The list is already in the article, so it sounds like the best way to deal with this is discuss the matter on Talk:Harry Kane and see if it's large enough to merit a page split. Primefac (talk) 13:39, 14 December 2022 (UTC)
- No discussion is needed. He is the current all time England scorer ([17]) which is grounds to have the article restored! Harry Kane page is 178,149bites page length, that alone makes a perfectly valid content fork. I never got peoples arguments for deletion at the last time. Still can an admin not restore the old page or not?? Govvy (talk) 15:13, 14 December 2022 (UTC)
- I don't see how we can overrule a well-attended deletion discussion without a discussion here, just because one editor thinks the topic is warranted. It may well be warranted now, but given that the majority of the AFD !voting was not based on him not being the top scorer (was mentioned, but not the predominate cause for deletion), there ought to be a discussion before recreating this. Hog Farm Talk 15:37, 14 December 2022 (UTC)
- No discussion is needed. He is the current all time England scorer ([17]) which is grounds to have the article restored! Harry Kane page is 178,149bites page length, that alone makes a perfectly valid content fork. I never got peoples arguments for deletion at the last time. Still can an admin not restore the old page or not?? Govvy (talk) 15:13, 14 December 2022 (UTC)
- @Govvy: There was consensus to delete the article at Wikipedia:Articles for deletion/List of international goals scored by Harry Kane. It should not be recreated unless and until you establish consensus to do so. --Jayron32 15:39, 14 December 2022 (UTC)
- Forgive me, but what you say is wrong, his record passes GNG, [18], ]https://www.nationalworld.com/sport/football/world-cup/who-has-scored-the-most-england-goals-where-is-harry-kane-in-the-all-time-highest-goal-scorers-leaderboard-3459648], [19], [20], [21]. I can go one, those are some of the top hits. No a discussion does not need to take place, if you want it to take place, that is just cat and mouse. Forgive me, but not one person has answered the question. Can an admin restore the article or not. It's a simple yes or no! :/ Govvy (talk) 16:00, 14 December 2022 (UTC)
- What I say is not wrong There was a discussion. It came to the conclusion to delete the article. You should not act unilaterally to recreate the article unless you establish consensus first. Everything else you might have to say here is irrelevant absent a new discussion to establish consensus to recreate it. I am an admin, and I am telling you that the article will not be recreated until after there is consensus established via a discussion. Not before. --Jayron32 16:24, 14 December 2022 (UTC)
- However, if the main problem mentioned at the AfD - that the topic had no reliable sources specifically about the topic - are addressed (which they will almost certainly be when he breaks the record) then any appeal should easily pass DRV. Black Kite (talk) 13:25, 15 December 2022 (UTC)
- It doesn't need to pass DRV for someone to just write a new article. Anything restored at DRV would need to be massively updated anyway, and since the "meat" of the information is already at the main article, might as well just start from there. If someone still thinks it is not worth having, they can nominate a second time at AFD. Primefac (talk) 13:43, 15 December 2022 (UTC)
- Well, except for a couple of things. 1) The original article shouldn't be restored because the prior AFD still applies unless consensus says it doesn't and 2) any re-creation of such a list would be eligible for WP:CSD#G4 if it were substantially similar to the original deleted list. Given the narrowness of the subject, I can't imagine that a list of such goals wouldn't be substantially similar to what was deleted. Which is why I advise against re-creating it unilaterally by anyone until after a new discussion is held to determine if there is the AFD consensus has been superseded by new information. That discussion needs to happen first, such a thing can't be unilaterally declared by one user. --Jayron32 13:32, 16 December 2022 (UTC)
- It doesn't need to pass DRV for someone to just write a new article. Anything restored at DRV would need to be massively updated anyway, and since the "meat" of the information is already at the main article, might as well just start from there. If someone still thinks it is not worth having, they can nominate a second time at AFD. Primefac (talk) 13:43, 15 December 2022 (UTC)
- However, if the main problem mentioned at the AfD - that the topic had no reliable sources specifically about the topic - are addressed (which they will almost certainly be when he breaks the record) then any appeal should easily pass DRV. Black Kite (talk) 13:25, 15 December 2022 (UTC)
- What I say is not wrong There was a discussion. It came to the conclusion to delete the article. You should not act unilaterally to recreate the article unless you establish consensus first. Everything else you might have to say here is irrelevant absent a new discussion to establish consensus to recreate it. I am an admin, and I am telling you that the article will not be recreated until after there is consensus established via a discussion. Not before. --Jayron32 16:24, 14 December 2022 (UTC)
- Forgive me, but what you say is wrong, his record passes GNG, [18], ]https://www.nationalworld.com/sport/football/world-cup/who-has-scored-the-most-england-goals-where-is-harry-kane-in-the-all-time-highest-goal-scorers-leaderboard-3459648], [19], [20], [21]. I can go one, those are some of the top hits. No a discussion does not need to take place, if you want it to take place, that is just cat and mouse. Forgive me, but not one person has answered the question. Can an admin restore the article or not. It's a simple yes or no! :/ Govvy (talk) 16:00, 14 December 2022 (UTC)
Birthdates of judges and justices under DAJSPA
editThis is probably too soon to be overly concerned, but information including the full date of birth of judges and justices may be illegal to publish online if the DAJSPA remains in the NDAA bill. As we publish this information on Wikipedia, is this something for us to be concerned about? I imagine that this portion of the law would be struck down for being overly broad. -- RockstoneSend me a message! 06:28, 16 December 2022 (UTC)
- There's a 100% chance this is enjoined by the courts. It's completely incompatible with first amendment protections. I wouldn't put any thought in to it at all. --WhoIs 127.0.0.1 ping/loopback 07:50, 16 December 2022 (UTC)
- This seems to be very USA focused. Is that a problem? What about the rest of the world? --Bduke (talk) 08:45, 16 December 2022 (UTC)
- Well, this bill is coming before the US Congress, so of course it is focussed on that country. We have a large number of editors in the US, and many articles on American judges, so it is still a potential problem even though the bill does not apply to the rest of us. Phil Bridger (talk) 08:56, 16 December 2022 (UTC)
- Last I checked the WP servers were in the US so US law applies to them. That may have changed in the last 10 years, so If I'm incorrect and its primary host is elsewhere then the (potential) law doesn't apply to the project at all. --WhoIs 127.0.0.1 ping/loopback 09:12, 16 December 2022 (UTC)
- The law (if it becomes law and if it's enforceable - both very big ifs) would apply to editors in the US wherever the servers happen to be. Phil Bridger (talk) 09:51, 16 December 2022 (UTC)
- Very true, but it wouldn't apply to a foreign project or create any sort of possible liability to project itself. It would be up to the users to maintain their own personal compliance like we do with Thailand's Lèse-majesté law. That said, I looked it up and 3 of the 5 servers the foundation uses are in the US: https://meta.wikimedia.org/wiki/Wikimedia_servers --WhoIs 127.0.0.1 ping/loopback 10:03, 16 December 2022 (UTC)
- The law (if it becomes law and if it's enforceable - both very big ifs) would apply to editors in the US wherever the servers happen to be. Phil Bridger (talk) 09:51, 16 December 2022 (UTC)
- Last I checked the WP servers were in the US so US law applies to them. That may have changed in the last 10 years, so If I'm incorrect and its primary host is elsewhere then the (potential) law doesn't apply to the project at all. --WhoIs 127.0.0.1 ping/loopback 09:12, 16 December 2022 (UTC)
- Well, this bill is coming before the US Congress, so of course it is focussed on that country. We have a large number of editors in the US, and many articles on American judges, so it is still a potential problem even though the bill does not apply to the rest of us. Phil Bridger (talk) 08:56, 16 December 2022 (UTC)
- This seems to be very USA focused. Is that a problem? What about the rest of the world? --Bduke (talk) 08:45, 16 December 2022 (UTC)
- Per the ongoing discussion of this topic at the Village Pump, Section 4(d) of that act states:
- (ii) EXCEPTIONS.—Clause (i) shall not apply to—
- (I) the display on the internet of the covered information of an at-risk individual or immediate family if the information is relevant to and displayed as part of a news story, commentary, editorial, or other speech on a matter of public concern;
- (II) covered information that the at-risk individual voluntarily publishes on the internet after the date of enactment of this Act; or
- (III) covered information received from a Federal Government source (or from an employee or agent of the Federal Government).
- (ii) EXCEPTIONS.—Clause (i) shall not apply to—
- Wikipedia coverage of judicial officers arguably constitutes "speech on a matter of public concern"; additionally, most information we have on federal judges originated as "information received from a Federal Government source", specifically scraped from the database of the Federal Judicial Center. Even if the FJC is required to remove that information, we have already received it. BD2412 T 14:24, 16 December 2022 (UTC)
Air Force One (film) needs some type of protection from sockpuppet
editThe article Air Force One (film) has been hit by a sockpuppet so many times and they have been blocked, but are evading bans to continue on that article, among other film articles as you will see on their contributions. I requested protection from Wikipedia:Requests for page protection in the past, but they didn't anything enough to help protect that article and I don't think pending change protection will be enough. Here is the evidence by page links and the sockpuppet in various sock accounts.
Page links: Air Force One (film) (edit | talk | history | links | watch | logs)
Sockpupput contributions:
Cartoon State (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Chalksergeant (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Funky Beckles (talk · contribs · deleted contribs · logs · filter log · block user · block log)
DrakeForce (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Colonel Reid Evans (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Please, find a way to protect that page from being vandalized by that sockpuppet. BattleshipMan (talk) 04:07, 16 December 2022 (UTC)
- I did a month of extended confirmed protection. If it continues, I can extend it. I'll also look into harsher range blocks. NinjaRobotPirate (talk) 09:07, 16 December 2022 (UTC)
- What a weird thing to spend your time sockpuppeting over. Canterbury Tail talk 14:49, 16 December 2022 (UTC)
- That's why I requested protection for it. That sockpuppet also did so in other film articles. BattleshipMan (talk) 18:06, 16 December 2022 (UTC)
- What a weird thing to spend your time sockpuppeting over. Canterbury Tail talk 14:49, 16 December 2022 (UTC)
Requesting additional admins to comment on problematic behavior
editThe following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
A recent ANI thread (Wikipedia:Administrators' noticeboard/Incidents#User:Deor incivility) appears to have a serious incivility issue coming from multiple otherwise-respected users. As an uninvolved user, I'm concerned about how it was handled and would like to request further input. Admin Deor was reported for saying you were just trying to be a shit
. User Levivich replied to the report saying things such as You are being a shit
and Please, stop being a shit
. Admin Drmies then closed the discussion without further comment. Was the OP being a "shit"? Maybe. But I would expect zero tolerance for conduct like this from any user, let alone admins, and I'm surprised and disappointed in the community to see this play out the way it did. Thebiguglyalien (talk) 17:58, 16 December 2022 (UTC)
- You are literally shit-stirring. Floquenbeam (talk) 18:02, 16 December 2022 (UTC)
- I would respectfully suggest that your expectations are not in line with Wikipedia's historical norms. Cheers. Dumuzid (talk) 18:03, 16 December 2022 (UTC)
- We don't block editors for cussing, within reason. You might want to read WP:SPADE too. Acroterion (talk) 18:06, 16 December 2022 (UTC)
- I don't want anyone to be blocked, I want users to abide by WP:CIVIL and to be nudged in the right direction when they don't. Toleration of incivility only results in the growth of incivility. Also, I prefer WP:NOSPADE whenever possible. Thebiguglyalien (talk) 18:10, 16 December 2022 (UTC)
- You're kidding, right. I'm going to move right along. "You're acting like a shit" is not worth ANY of this. You are welcome, of course, to start proceedings with ArbCom or report to the Ombudsperson. Drmies (talk) 18:17, 16 December 2022 (UTC)
- I don't want anyone to be blocked, I want users to abide by WP:CIVIL and to be nudged in the right direction when they don't. Toleration of incivility only results in the growth of incivility. Also, I prefer WP:NOSPADE whenever possible. Thebiguglyalien (talk) 18:10, 16 December 2022 (UTC)
Closure review of the RfC at Wikipedia talk:Biographies of living persons#RfC on Denials
editUser @Sideswipe9th has requested that I ask for a closure review of the discussion that I closed at Wikipedia talk:Biographies of living persons#RfC on Denials as they do not believe that the reasoning that I gave at User talk:Gusfriend#Closure of RfC on Denials was sufficient and it should be closed by an uninvolved administrator or someone intimately familiar with core content policies.
Apologies if I overstepped by closing the discussion. Gusfriend (talk) 10:41, 14 December 2022 (UTC)
- On you talk page you describe some additional comments you would have made if closing the discussion now. Can I suggest you amend the close with the those additional thoughts, as it will likely reduce any issues anyone might have with the result. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 19:57, 14 December 2022 (UTC)
- Endorse closure Regardless of the closing statement, the consensus in support of Option 1 in that discussion is clear and obvious. The closing statement was perhaps a bit badly worded but in the end it's a minor issue. If the closer wants to amend their statement to make it the rationale better, that's fine, but there's no need to negate the result as the end result is the same. Option 1 was the clear consensus choice. The rest is just window dressing. For future reference, closing statements should avoid mentioning vote counting, because someone who voted for a different outcome will go apoplectic and cry "zOMG! WP:NOTAVOTE!". Instead, weigh the relative arguments (and the number of people making and endorsing certain arguments is a major factor in assessing consensus) and avoid mentioning the counting of votes the way you did. --Jayron32 20:05, 14 December 2022 (UTC)
- Endorse closure The close, though succinct, clearly represents the consensus emergent in the RfC. If the additional comments from Gusfriend's Talk page are added to the closing statement (and I would strongly urge they not be added), it would be better to exclude the parenthetical
(including the sections WP:DUE and WP:FALSEBALANCE)
; there was significant argument in the RfC that FALSEBALANCE does not apply to allegations or assertions which have not been the focus ofcommonly accepted mainstream scholarship
. - Rotary Engine (was Ryk72) talk 21:21, 14 December 2022 (UTC)
- Thank you all for your comments which I will take on board for future closures. I will add a note to the closure notice pointing to this discussion. Gusfriend (talk) 22:47, 16 December 2022 (UTC)
Copyright question
editWould someone please take a look at the comments posted on Talk:Pope Pius XII by User:HistoryAndPoliticalAnalyst? I believe them to be copyright violations, and have redacted some and collapsed others, but I'm not certain that those are the correct actions to have taken. I redacted long excerpts of copyright material, and collapsed a series of short excerpts which individually might be acceptable, but which collectively seem to violate the copyright holder's rights.
I would appreciate someone more familiar with Wikipedia's copyright policies looking at the comments as posted and my actions in relation to them.
The user has also commented on Talk:Hitler's rise to power, and these might be worth looking at as well. Beyond My Ken (talk) 00:51, 17 December 2022 (UTC)
- Notified. Beyond My Ken (talk) 00:53, 17 December 2022 (UTC)
Possible threats made by this user
edit- Omni-Edition (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- https://en.wikipedia.org/wiki/Special:Contributions/Omni-Edition
- https://en.wikipedia.org/w/index.php?title=Morrigan_Aensland&oldid=1127860624
- https://en.wikipedia.org/w/index.php?title=Darkstalkers_(comics)&oldid=1124125214
- https://en.wikipedia.org/w/index.php?title=Udon_Entertainment&diff=next&oldid=1124125344
From a concern received from a user, I have found multiple counts of threats to other users left on the summary edit and their talk pages [22], [23] on the article Morrigan Aensland because they would not follow this user's point of view.
I am reporting this user for WP:THREAT, WP:NPOV, WP:ORIGINAL Layah50♪ ( 話して~! ) 03:42, 17 December 2022 (UTC)
- やれやれ。Blocked as NOTHERE EvergreenFir (talk) 06:14, 17 December 2022 (UTC)
- (EC) The editor has been blocked per WP:NOTHERE which is probably for the best. I'd note that while their edits were very problematic, I'd be reluctant to say they can reasonably be construed as making legal threats even considering the risk of a chilling effect. While they did sometimes leave some vague mentions of reporting people their talk page comment seems to make it clear they were just referring to reportings editors to "mods". So while demonstrating a common lack of understanding how Wikipedia works, I think it's fair to say when they said "report" it clearly wasn't a legal threat. Nil Einne (talk) 06:20, 17 December 2022 (UTC)
- Sorry if I was overreacting, but thank you! Layah50♪ ( 話して~! ) 06:47, 17 December 2022 (UTC)
- I had a discussion with this user. I'm not suprised that their editing career ended this way. Mako001 (C) (T) 🇺🇦 11:40, 17 December 2022 (UTC)
- Sorry if I was overreacting, but thank you! Layah50♪ ( 話して~! ) 06:47, 17 December 2022 (UTC)
User with multiple accounts and IPs disrupting Vietnamese articles
edit- Nurlac (talk · contribs · deleted contribs · nuke contribs · logs · filter log · block user · block log)
- Qiure (talk · contribs · deleted contribs · nuke contribs · logs · filter log · block user · block log)
- 2405:4802:1CD:D40:5D2A:A173:3282:A792 (talk · contribs · WHOIS)
- 2405:4802:1CD:D40:C518:5AD2:F112:B168 (talk · contribs · WHOIS)
All these accounts are involved in changing the name of the Vietnamese opera genre from "cải lương" to the fake term "cairoless", which has zero uses and mentions all over the internet. They do this simultaneously on wikicommons, wikidata and enwiki. This user also has been engaged in multiwiki vandalism on adding fake emblems and logos on Vietnamese articles. Each account is currently banned on wiki-commons and several other wikis or globally banned. Yesterday they've renamed the entire article about the genre to Cairoless and reworked its content, also added a YouTube video as a fake source, where the term is never mentioned. The whole thing looks like ongoing vandalism. Solidest (talk) 13:09, 15 December 2022 (UTC)
- @Solidest Accounts blocked for sock puppetry, both IPs blocked last month by [[User:NinjaRobotPirate]] what I don't understand is how the accounts were editing using globally locked IPS. Anyway, I suggest you revert them. Doug Weller talk 15:30, 15 December 2022 (UTC)
- @Doug Weller:, They keep vandalizing under a new IP with the same edits: 2405:4802:2e0:9fe0:a80c:aacf:c9c1:7c2b (talk · contribs · WHOIS). I guess it's worth protecting the article. Solidest (talk) 15:17, 17 December 2022 (UTC)
- @Solidest semi protected for a month. Doug Weller talk 15:43, 17 December 2022 (UTC)
45.8.146.215
editI reported 45.8.146.215 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) at AIV 45 minutes ago, but that report has apparently received no investigation. The IP is very rapidly removing {{portal}} templates, seemingly constructive wikilinks, and other content from a wide range of articles, currently focusing on the geography of the western United States. The IP's Talk page contains numerous warnings over the past 45 days, but the IP has made no effort to respond to any of them. Could someone take a look and see if the IPs edits appear to be constructive? While some appear to be so, or at least defensible, the vast majority do not. General Ization Talk 05:39, 13 December 2022 (UTC)
- I'm an admin but not an AIV watcher. I just happened to stumble across this IP editor via my watchlist. I'm combing through their edits now. They do have a lot of helpful edits (including sourced additions to articles using citation templates), but a lot of nonsense too. Among the nonsense, randomly removing portals from some articles, while adding them to others (with no apparent rhyme or reason as to which have the portals removed and which have the portals added), also removing redlinks. I'm tempted to block as they apparently have been warned adequately. But I'm also concerned this may be a bigger issue, like maybe a block evasion. This editor clearly knows their way around Wikipedia more than the average IP vandal. If anybody can clear up what's going on please advise.Dave (talk) 05:51, 13 December 2022 (UTC)
- I note that the IP stopped about the time that another editor started systematically reverting their edits, and appears now to have started again using IP 80.71.157.208 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) (with some overlap on the previous IP's edits). General Ization Talk 05:53, 13 December 2022 (UTC)
- Good catch, thank you. I didn't notice they switched IP's. So yeah they know how to game the system. I blocked the 80.x IP. Now we see how many more IP's they have at their disposal. Dave (talk) 05:57, 13 December 2022 (UTC)
- Noted. Saintstephen000 (talk)
- Since we seem to agree this is not your run-of-the-mill vandal, and my report at AIV had received no attention anyway, I removed it. Thanks for looking into it (and to @Saintstephen000 for reverting many of the IP's stranger edits). General Ization Talk 06:26, 13 December 2022 (UTC)
- The editor resumed the same mostly non-constructive editing pattern using the 45.x IP around 0217 EST and continued through around 0500 EST. General Ization Talk 18:11, 13 December 2022 (UTC)
- they are back at it, removing flags and creating frivolous categories. Saintstephen000 (talk)
- And also back to using 80.71.157.208 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) to make edits that fit the same pattern. General Ization Talk 20:07, 17 December 2022 (UTC)
- they are back at it, removing flags and creating frivolous categories. Saintstephen000 (talk)
- Good catch, thank you. I didn't notice they switched IP's. So yeah they know how to game the system. I blocked the 80.x IP. Now we see how many more IP's they have at their disposal. Dave (talk) 05:57, 13 December 2022 (UTC)
- I note that the IP stopped about the time that another editor started systematically reverting their edits, and appears now to have started again using IP 80.71.157.208 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) (with some overlap on the previous IP's edits). General Ization Talk 05:53, 13 December 2022 (UTC)
Twitter suspensions AfD
editThe following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Uh, a user just deleted half the comments at this AfD [24] and somehow they cannot be restored. What’s up?
Also, might wanna take some action here - Musk and others have been amplifying existence of this article/AfD on twitter and it’s likely to turn into a complete wreck. Volunteer Marek 21:15, 17 December 2022 (UTC)
Also relevant [25]. Volunteer Marek 21:20, 17 December 2022 (UTC)
- I'd be tempted to semi-protect it except that Musk and his fanboys would see it as proof that Wikipedia is controlled by the illuminati, or something. Black Kite (talk) 21:34, 17 December 2022 (UTC)
- I've no objections to the AFD being semi-protected. GoodDay (talk) 21:39, 17 December 2022 (UTC)
- Support. Who cares how they’ll see it? Volunteer Marek 21:46, 17 December 2022 (UTC)
- Sympathetic but oppose as all these issues resolve around censorship on the internet and sunlight is the best way to show Wikipedia does not censor. Could support re-factoring or some other method of making IPs/nee users less disruptive including directing their posts to a subpage so relevant comments can be moved back to main discussion. Also would welcome an RfC to make all AfDs semi so it's no longer an ad-hoc process that looks like it's disproportionately asked for everytime twitter comes up. Slywriter (talk) 21:57, 17 December 2022 (UTC)
- I disagree with the semi-protection to be honest, but not because it may be viewed as 'censorship', I give a rat's arse about that. There are of course a few nonconstructive additions such as [26], but I see a surprisingly high amount of !votes with actual rationales. The closing administrator can decide how to weigh each vote, but just because of its huge participation I don't believe it should be protected. Sockpuppetry accusations can be handled at the appropriate venues. I will however keep an eye on it for a bit, and have no issue with another administrator protecting it if it evolves into a shitstorm. DatGuyTalkContribs 22:03, 17 December 2022 (UTC)
- Okay, seems like I talked too soon. I've protected the AfD for a week. DatGuyTalkContribs 22:15, 17 December 2022 (UTC)
- Elon already found from last time just the other day that sending a swarm of his SPA followers at a discussion here is a great way to create the desired outcome because, for whatever reason, the closing admins don't completely dismiss all of the SPA statements in these discussions. He's just going to keep doing this over and over. SilverserenC 22:14, 17 December 2022 (UTC)
Also [27] [28] Volunteer Marek 22:19, 17 December 2022 (UTC)
Orphaned .js and .css pages in User space
editA few editors have taken on Wikipedia:Database reports/Ownerless pages in the user space recently, reducing the population of the report from about 1,500 to about 120 pages. Most of the remaining pages are .js and .css pages, which are actionable only by administrators. Having these pages on the report makes it less easy to see any remaining actual pages.
I can't really make sense of most of them, which appear maybe to be redirects that may or may not work. Many or most (or all?) of them appear to be connected to user renames.
Taking one specific example, User:Érico Júnior Wouters/CommonsHelper Labs.js does not have any incoming links in What links here (although with a .js file, I don't know if What links here really works to know if the page is being referenced), and the file exists at its new location. The page appears to be safe to delete, since there is no user to log in and load it.
Is there an admin here who would be willing to look at these pages and do something appropriate with them? Deleting or moving comes to mind, but there may be other options. Thanks for your time. – Jonesey95 (talk) 14:31, 16 December 2022 (UTC)
- I have linked this from WP:IANB. Some of them are double redirects from users who got renamed twice and need to retargeted. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 14:41, 16 December 2022 (UTC)
- They really shouldn't be "re-targeted", they should just be deleted or moved. — xaosflux Talk 16:39, 16 December 2022 (UTC)
- This kind of search might be more thorough than looking for links. This would hopefully catch things like
importScript('User:Érico Júnior Wouters/CommonsHelper Labs.js');
that may not have a proper backlink. –Novem Linguae (talk) 15:36, 16 December 2022 (UTC) - I will work on this. Izno (talk) 18:42, 16 December 2022 (UTC)
- I have cleared out the set that were trivial.
- These 3 remain as protected JavaScript 'redirects' (I understand why). Several users import them directly. We really should make a gadget that can provide a couple functions to move people to the supported name directly and/or consider moving Wikipedia:User scripts/Most imported scripts to gadgets. I can also myself make the edits which move people over and then delete the redirects. Xaosflux as the protector, though those requests and/or discussion of them might be better for IANB. Izno (talk) 19:59, 16 December 2022 (UTC)
- @Izno my protection was as an antispoof measure should someone register that old username, as a stop gap. The not-a-redirects probably should just be deleted; if Kaniivel wants to keep supporting these they could notify the people using the very out of date loads. It's possible for intadmins to go change everyone's imports, but I really don't love getting stuck with that sort of maintenance... — xaosflux Talk 20:41, 16 December 2022 (UTC)
- I deliberately didn't say why it was protected. ;)
- Should be able to get a list of the users using something of his (search + some processing in Notepad) and send a mass message telling users to update and then delete it in Soon time. That leaves us not significantly stuck with the maintenance.
- AWB run over them is also trivial, but whether users should know it has happened has some split in int admin corp.
- Or we can just delete and post in a reasonably central place it's deleted, but then the page has to be reprotected, which is lowest effort. Izno (talk) 21:47, 16 December 2022 (UTC)
- We can put an
alert()
on it saying HEY YOU - YOU HAVE A BROKEN SCRIPT, FIX IT BUDDY! :D — xaosflux Talk 22:03, 16 December 2022 (UTC) - @Izno: So long as other users are importing an orphaned script, it's probably best to keep it in exactly the format left over from a page move:
/* #REDIRECT */mw.loader.load("//en.wikipedia.org/w/index.php?title=THE_TARGET_PAGE\u0026action=raw\u0026ctype=text/javascript");
. If it's in that format, apparently it will be automatically protected by the software from editing by non-intadmins. For example, I just locked myself out of editing one of my own .js pages. But User:Cumbril/IPLabeller.js has an extra comment before the/* REDIRECT */
, so the automatic protection won't apply. This also means that deleting the script is a bad idea: even with full create-protection, there's nothing to stop a compromised admin from removing the protection, registering the account, and then recreating the script. Suffusion of Yellow (talk) 23:43, 16 December 2022 (UTC)- Huh. Wonder when that was added. Let me go remove that comment. Izno (talk) 23:56, 16 December 2022 (UTC)
- 2019 it would seem. Also, the RefConsolidator scripts should have
&
changed to\u0026
for this trick to work. Yes, it really is that fussy. You'll know you've got it right if visiting User:Cumbril/RefConsolidate.js actually takes you to User:Kaniivel/RefConsolidate.js. Here's the "is this a redirect?" check for JS pages. Suffusion of Yellow (talk) 00:24, 17 December 2022 (UTC)- Neat change. I'll look into it. Izno (talk) 01:17, 17 December 2022 (UTC)
- Those two are fixed now. Izno (talk) 06:52, 17 December 2022 (UTC)
- Neat change. I'll look into it. Izno (talk) 01:17, 17 December 2022 (UTC)
- 2019 it would seem. Also, the RefConsolidator scripts should have
So long as other users are importing an orphaned script ...
@Suffusion of Yellow @Xaosflux Note that it is not possible for anyone to import orphaned scripts. Try it - you get a 403. – SD0001 (talk) 09:02, 17 December 2022 (UTC)- @SD0001 thanks, that used to work...hmmm. Still the possibility that someone gets that name in the future; so perhaps we should delete it and also try to help people that have the import. Importing other people's personal scripts is a buyer beware situation of course! — xaosflux Talk 09:19, 17 December 2022 (UTC)
- Thank you all. The report looks a lot more sane now. – Jonesey95 (talk) 22:59, 17 December 2022 (UTC)
- @SD0001 thanks, that used to work...hmmm. Still the possibility that someone gets that name in the future; so perhaps we should delete it and also try to help people that have the import. Importing other people's personal scripts is a buyer beware situation of course! — xaosflux Talk 09:19, 17 December 2022 (UTC)
- Huh. Wonder when that was added. Let me go remove that comment. Izno (talk) 23:56, 16 December 2022 (UTC)
- We can put an
- @Izno my protection was as an antispoof measure should someone register that old username, as a stop gap. The not-a-redirects probably should just be deleted; if Kaniivel wants to keep supporting these they could notify the people using the very out of date loads. It's possible for intadmins to go change everyone's imports, but I really don't love getting stuck with that sort of maintenance... — xaosflux Talk 20:41, 16 December 2022 (UTC)
206.172.185.116 IP editor is blanking any reference to Syria with rare explanations and no sources to back his/her edits.
edit- 206.172.185.116 (talk · contribs · WHOIS)
206.172.185.116 IP editor is blanking/removing any reference to Syria in article after article with rare explanations and no sources to back his edit. This editor is not here to build an encyclopedia. Here are the diffs:
Over here the ip editor reverts 4 times after their initial edit, with one explanation, but with no source and questionable intent considering their previous edits: 7 I did not engage with the IP editor due to the clear bad faith displayed in their multiple and consistent edits. George Al-Shami (talk) 01:34, 18 December 2022 (UTC)
Redirecting Vita Zaverukha, taking it to AfD or what?
editThe article on Vita Zaverukha has been repeatedly transformed into a redirect to Aidar Battalion.
Originally there were both notability and WP:BLP concerns (02:14, 9 December 2022, 18:13, 10 December 2022, 19:17, 10 December 2022, 10:25, 11 December 2022) but then the article was significantly changed, new sources and content were added, and unsupported claims were removed: I restored the "new" article at 01:55, 12 December 2022 and this is latest version of it [29]. Nonetheless, the article continued to be deleted via redirect (07:16, 12 December 2022, 02:53, 13 December 2022, 05:05, 13 December 2022) while an IP address kept restoring it.
In the meantime, I've started a discussion on the talk page. Since the issues of poor sources and misrepresentation of sources were soon addressed and IMHO also solved, the discussion turned to notability. My doubt is that AfD should be the right forum to deal with notability rather than the talk page, where there are few editors and they inevitably are the usual EE regulars (my arguments here [30] and here, also on the issue of notability [31]).
Could you please tell us if that discussion should continue on the talk page, be moved to AfD or to an RfC?
I ping the involved editors @Volunteer Marek, GizzyCatBella, OsFish, and Mhorg:. Gitz (talk) (contribs) 13:15, 13 December 2022 (UTC)
- I'm afraid the foregoing isn't a neutral account. Not only is there still clearly no consensus on notability for the subject as an individual separate from a singular event, editors continue to express concerns with sourcing, directly citing BLP concerns. By the way, I am not an "EE regular" as far as I am aware, have never been under sanctions, and as far as I can see, other editors mentioned here aren't mentioned on the EE sanctions page just linked to. But put all that to one side, why not take this issue to WP:Biographies of living persons/Noticeboard if you want more eyes on it?OsFish (talk) 13:53, 13 December 2022 (UTC)
- I neither said nor implied that you or others had been sanctioned. I myself have never been sanctioned or warned. And I said that the issues with sources have been addressed and "IMHO also resolved" - you are free to disagree. I'm fine with moving this discussion to BLPN, AFD, RFC, or anywhere else really, but I'd like to know from the admins which is the best forum to discuss your notability concerns; I'd also like to see an end to these massive and unwarranted removals of text and sources via redirecting, which have recently occured also at Torture in Ukraine. I believe they are highly disruptive and I hope the admins can help. Gitz (talk) (contribs) 14:47, 13 December 2022 (UTC)
- @Gitz6666 - You restored the "new" article to this version which has errors and is lacking sound sources for WP:BLP article. I'm astonished that you believe this is okay. - GizzyCatBella🍁 14:59, 13 December 2022 (UTC)
- Yep, I belive it's okay. I noticed the issues with references and fixed them immediately, plus I made a bit of copy editing, so after a few minutes the article looked like this: [32] Gitz (talk) (contribs) 15:21, 13 December 2022 (UTC)
- @Gitz6666 - You restored the "new" article to this version which has errors and is lacking sound sources for WP:BLP article. I'm astonished that you believe this is okay. - GizzyCatBella🍁 14:59, 13 December 2022 (UTC)
- I neither said nor implied that you or others had been sanctioned. I myself have never been sanctioned or warned. And I said that the issues with sources have been addressed and "IMHO also resolved" - you are free to disagree. I'm fine with moving this discussion to BLPN, AFD, RFC, or anywhere else really, but I'd like to know from the admins which is the best forum to discuss your notability concerns; I'd also like to see an end to these massive and unwarranted removals of text and sources via redirecting, which have recently occured also at Torture in Ukraine. I believe they are highly disruptive and I hope the admins can help. Gitz (talk) (contribs) 14:47, 13 December 2022 (UTC)
- AFD is absolutely the right place to challenge the notability of a subject, especially when bold redirections have been challenged. Any editor who disagrees with the restorations should open that discussion instead of engaging in edit warring. Per WP:CONRED,
If a redirection is controversial, however, AfD may be an appropriate venue for discussing the change in addition to the article's talk page.
Iffy★Chat -- 14:20, 13 December 2022 (UTC)- BLP is not negotiable and BLP1E applies. We’re not going to host attack pages on non notable people (even if they’re the awful sort) and let them sit there for months while the circus, WP:SPA accounts and trolling and all that included, plays out at AfD. No consensus on BLPs defaults to “not include” for a good reason. Volunteer Marek 14:30, 13 December 2022 (UTC)
- Attack pages can be speedy deleted per WP:G10, and BLP violations can be removed even if only a stub remains in the article. What non-admins can't do is to use BLP as a sword to effectively delete a page without a clear consensus to do so. Iffy★Chat -- 14:43, 13 December 2022 (UTC)
- Which part of “BLP is non negotiable” are you confused about? We even have discretionary sanctions when it comes to BLPs for this very reason. She’s obviously a non notable person and the only reason this article exist(Ed) is because she’s a trope in online Russian propaganda. And you have it backwards when it comes to consensus required, as already pointed out. Volunteer Marek 14:46, 13 December 2022 (UTC)
- Attack pages can be speedy deleted per WP:G10, and BLP violations can be removed even if only a stub remains in the article. What non-admins can't do is to use BLP as a sword to effectively delete a page without a clear consensus to do so. Iffy★Chat -- 14:43, 13 December 2022 (UTC)
- BLP is not negotiable and BLP1E applies. We’re not going to host attack pages on non notable people (even if they’re the awful sort) and let them sit there for months while the circus, WP:SPA accounts and trolling and all that included, plays out at AfD. No consensus on BLPs defaults to “not include” for a good reason. Volunteer Marek 14:30, 13 December 2022 (UTC)
For what it's worth, I have move-protected Vita Zaverukha for now. Can be unprotected IF an article should be written about her. Lectonar (talk) 15:03, 13 December 2022 (UTC)
- Sorry but an article about her has already been written (and removed), this one: [33]. Gitz (talk) (contribs) 15:11, 13 December 2022 (UTC)
- I hope this edit (restoring the "new" version) is OK: [34]. Gitz (talk) (contribs) 15:16, 13 December 2022 (UTC)
- Oh my god. You know VERY WELL that “this edit” is NOT ok!!!! This is the BLP violating edit that has been reverted by multiple editors so you know 100% that you have no consensus to do this! This is a perfect illustration of your disruptive behavior and WP:IDIDNTHEARTHAT which you’ve displayed across a dozen articles in this topic area. Volunteer Marek 15:51, 13 December 2022 (UTC)
- I hope this edit (restoring the "new" version) is OK: [34]. Gitz (talk) (contribs) 15:16, 13 December 2022 (UTC)
- According to the sources that speak of this subject, in my opinion, notability has been achieved:
- International sources:
- NYTimes[35]
- Huffingtonpost[36]
- Radio Free Europe/Radio Liberty[37][38][39][40]
- Radio France Internationale[41]
- France 24[42]
- US Department - HUMAN RIGHTS REPORTS[43]
- Book "Insurgent Women: Female Combatants in Civil Wars" (scholarly source)[44]
- Bellingcat (mentions her in a photo, talking about the accusations made against her) [45]
- Open Democracy[46]
- Ukrainian sources:
- Hromadske, which is one of the most internationally known Ukrainian sources[47][48][49][50] [51]
- Ukrainian Independent Information Agency[52][53][54][55]
- Television Service of News[56][57]
- Espreso TV[58]
- Gazeta.ua[59]
- Obozrevatel[60][61]
- 20minut[62]
- LB[63]
- Fakty[64]
- Zaborona[65]
- 33kanal[66]
- 44ua[67]
- 24tv[68]
- Novynarnia[69][70]
- Vinnytsyanews[71][72]
- Dsnews[73]
- Antikor[74]
- KievVlast[75]
- Vikna[76][77]
- KievSegodnya[78]
- LvivskyPortal[79]
- Mhorg (talk) 15:11, 13 December 2022 (UTC)
- It’s already been pointed out (including by others) that most of these are regional “police blotter” kinds of sources. And the “international sources” are mostly passing mentions. For example *it’s already been pointed out to you* that the Bellingcat source is not at all about her and the only reason her name appears in it is because she happens to be in a photo that has a caption (that is the only mention of her in that source). Yet here you are, once again trying to pretend that this is significant coverage even after your attempts at misrepresentation have been pointed out. Volunteer Marek 16:03, 13 December 2022 (UTC)
- You are writing inaccuracies, there are few 'regional' sources, like "LvivskyPortal", "KievSegodnya", "KievVlast", "Vinnytsyanews", "20minut". All the others are national and well known sources.
- About Bellingcat, I specified precisely how it is cited. I ask you, please, to at least read the things I write, before accusing me of 'misrepresenting' something. Mhorg (talk) 16:35, 13 December 2022 (UTC)
- It’s already been pointed out (including by others) that most of these are regional “police blotter” kinds of sources. And the “international sources” are mostly passing mentions. For example *it’s already been pointed out to you* that the Bellingcat source is not at all about her and the only reason her name appears in it is because she happens to be in a photo that has a caption (that is the only mention of her in that source). Yet here you are, once again trying to pretend that this is significant coverage even after your attempts at misrepresentation have been pointed out. Volunteer Marek 16:03, 13 December 2022 (UTC)
@Lectonar:, I'm afraid, despite it being clear even from this discussion let alone the talkpage, that there is clearly no consensus that the subject is notable, user:Gitz6666 has just made this edit to restore the disputed BLP material. Despite this being the wrong forum to raise the original dispute, I wonder if that is in line with the spirit of your move protect.OsFish (talk) 15:28, 13 December 2022 (UTC)
- @Gitz6666 - @Lectonar protected the article and you move it back in 10 minutes? How is that possible? GizzyCatBella🍁 15:53, 13 December 2022 (UTC)
- Agree. You can’t get more WP:IDIDNTHEARTHAT and WP:GAME than that. This BLP violation has been reverted by at least three editors yet Gitz6666 waltzes in and restores the BLP vio in a middle of discussion about it. This would make it his,what, fourth, fifth? [80] [81] [82] [83] Attempt at restoring the BLP violations? Both BLP and EE are under discretionary sanctions. It’s time for a block here. Volunteer Marek 15:56, 13 December 2022 (UTC)
Quoting page 23 of this 2019 book by Georgetown University Press:
Other women appear to glorify their newfound ability to engage in violence. Vita Zaverukha stands out in this respect. The teenager became notorious in the Russian press for her cals to wipe out all of Ukraine's Russian-speaking population and for posting neo-Nazi propaganda...In November 2014 the magazine Elle France profile Zaverukha...she was arrested in MAy 2015 for her role in an armed robbery in Kyiv...after she was released on bail in January 2017, Zaverukha and her partner were attacked by fellow members of an ultranationalist group to which they belonged. In July 2017 both Zaverukha and her partner allegedly led an attack on transgender activists in Kyiv.
BLP1E? No way. She is definitely notable, having been profiled over multiple years by multiple RSes in multiple countries. The article still needs cleanup (it's good that DM is gone; there are still op-eds being cited), but AFD would be a waste of time, and I think her biography would be UNDUE if merged to any other article. She's 100% notable though, I can't believe I'm saying this but bold redirection as a backdoor to deletion is not OK. Take it to AFD if you want. Levivich (talk) 15:54, 13 December 2022 (UTC)
- She’s a neo Nazi. There are, unfortunately, not thousands of such people in all countries in the world. She posts on social media. There are hundreds of millions of people who do that. She was involved in an armed robbery. Again, millions of people commit armed robbery. She got beat up by her friends. Etc. There is absolutely nothing notable about this person, except that Russian propaganda have seized upon her existence as “proof” (sic) there are “neo Nazis in Ukraine”. If we had an article on every neo Nazi in Russia (or US for that matter) that posted stupid shit on social media and was involved in an armed robbery we would easily double the number of articles on Wikipedia. Gimme a break. There’s absolutely no freaking way this person - a teenager - is notable. What exactly is she notable for? Volunteer Marek 16:01, 13 December 2022 (UTC)
There are, unfortunately, not thousands of such people in all countries
– Presumably now what you meant. EEng 14:30, 16 December 2022 (UTC)- Yes typo. No "not". Volunteer Marek 03:04, 17 December 2022 (UTC)
- What is she notable for? "The teenager became notorious in the Russian press for her cals to wipe out all of Ukraine's Russian-speaking population and for posting neo-Nazi propaganda...In November 2014 the magazine Elle France profile Zaverukha...she was arrested in MAy 2015 for her role in an armed robbery in Kyiv...after she was released on bail in January 2017, Zaverukha and her partner were attacked by fellow members of an ultranationalist group to which they belonged. In July 2017 both Zaverukha and her partner allegedly led an attack on transgender activists in Kyiv." That's what she is notable for. Levivich (talk) 16:01, 13 December 2022 (UTC)
- ”became notorious in Russian press”, I.e. “became a Russian propaganda trope” does NOT actually make someone notable on English Wikipedia. Come on! I’m sorry but there’s no way I can believe that you’re making this claim in good faith. Volunteer Marek 16:06, 13 December 2022 (UTC)
- GCB now edit-warring to restore the redirect. Whatevs, the rest of the community can deal with it. Levivich (talk) 16:01, 13 December 2022 (UTC)
- @Levivich Stop moving it - the article is protected (glich?) - GizzyCatBella🍁 16:01, 13 December 2022 (UTC)
- VCM & GCB tag-team edit warring to push a POV... what else is new? Levivich (talk) 16:02, 13 December 2022 (UTC)
- (!) Watch what you are saying @Levivich - GizzyCatBella🍁 16:05, 13 December 2022 (UTC)
- Levivich showing up to a discussion that they’re not involved in just because VM or GCB are involved, just to throw WP:ASPERSIONS and pursue old grudges? What else is new? Wait. Didn’t you actually have an IBAN with Gizzy? Volunteer Marek 16:09, 13 December 2022 (UTC)
- (!) Watch what you are saying @Levivich - GizzyCatBella🍁 16:05, 13 December 2022 (UTC)
- VCM & GCB tag-team edit warring to push a POV... what else is new? Levivich (talk) 16:02, 13 December 2022 (UTC)
- The story is actually even more interesting that that, Levivich. The armed robbery in Kyiv was probably an attack on the policemen of thw Berkut, hated by many because they are held responsible for the violence against the Automaidan and the Euromaidan. The trial against her became a political event for Ukrainian far-right circles, with an MP handcuffing himself to her wrist, the Patriarch awarding her a medal (allegedly), and demonstrations and clashes with police near the courhouse. Since Zaverukha is young, beautiful and sexy, and liked to be photographed with a machine gun while giving the Nazi salute, she obviosulsy rose to fame both in Ukraine and Russia. To delete this article would be idiotic. Gitz (talk) (contribs) 16:17, 13 December 2022 (UTC)
- young, beautiful and sexy - @Gitz6666 please read WP:BLP yet again - GizzyCatBella🍁 16:24, 13 December 2022 (UTC)
- She didn’t “rise to fame” in Ukraine. She was mentioned in a couple regional sources in their crime reports because she, like millions of other people, committed an armed robbery. These regional sources include user generated content. Other than that she “rose to fame” in Russian online social media because they used her existence for propaganda purposes. Guess what? Just because pro-Russian trolls post about her on twitter and Reddit doesn’t mean we need to have an article about her. And it’s getting really tiresome watching some editors repeatedly take whatever the latest garbage that’s circulating on Putinist social media is and try to turn it into Wikipedia articles. Volunteer Marek 16:29, 13 December 2022 (UTC)
- The funny thing is that it's you who systematically monitor Putin's social media. I don't even know what these social media are, I never check them, and frankly I don't give a damn about them. Gitz (talk) (contribs) 16:34, 13 December 2022 (UTC)
Note - [84] - GizzyCatBella🍁 16:09, 13 December 2022 (UTC)
- Can we please take such arguments to the talkpage or another appropriate forum such as BLPN, not here. Levivich, it doesn't help to misrepresent the reasons why multiple editors have disputed notability, which are categorically NOT about whether her name has been mentioned in RS at all. When going to forums outside the talkpage, one should endeavour to represent both sides fairly. OsFish (talk) 16:11, 13 December 2022 (UTC)
- User:Lectonar said
I have move-protected Vita Zaverukha for now. Can be unprotected IF an article should be written about her
. We have an article about her. If you doubt her notability, please go to AfD and stop disrupting other editors' work. You have to realize that your concern about Russian propaganda being occasionally true is YOUR concern, not Wikipedia's policy; I, for one, never read Russian propaganda, have no idea what it says, and have no intention of checking it before deciding whether or not to publish something on Wikipedia. Gitz (talk) (contribs) 16:30, 13 December 2022 (UTC)- oh ok, so you didn’t get it from Russian propaganda. Sure. So… how DID you arrive at this article? Care to remind us? Oh, that’s right, you were WP:STALKing my edits [85] (wait, I’m sorry, you weren’t “stalking” my edit, you were just “checking (my) contributions” and “following (me)” to articles I recently edited. Volunteer Marek 16:43, 13 December 2022 (UTC)
- Gitz6666 - Please wait for additional comments from Lectonar, as far as I know, they move protected the article - please don’t move it until then. - GizzyCatBella🍁 16:35, 13 December 2022 (UTC)
- Absolutely. The phrase was IF it SHOULD. We are plainly in dispute about that. The strength of any one editor's conviction about how right they are is not how disputes are resolved.OsFish (talk) 16:39, 13 December 2022 (UTC)
- User:Lectonar said
Mysteriously, a very new account has turned up out of the blue to ignore the lack of consensus and reinstate the disputed BLP material.OsFish (talk) 17:37, 13 December 2022 (UTC)
- Fully protected aside from the above between established editors, the latest by Goodrover was clearly not in good faith and the move protections weren't helping with the redirect. I have reverted to the prior one and fully protected. If an admin feels consensus is reached in less than seven days, feel free to adjust the protection without consulting me. This is to stop the edit warring. Star Mississippi 17:42, 13 December 2022 (UTC)
- @Star Mississippi: Thanks. Would you (or another admin) mind doing a procedural nomination to AFD (through the protection), which is where we need to discuss if the article should be deleted, kept, redirected, etc.? Levivich (talk) 17:46, 13 December 2022 (UTC)
- Doing so right now @Levivich Star Mississippi 17:49, 13 December 2022 (UTC)
- Thanks! Levivich (talk) 17:50, 13 December 2022 (UTC)
- Doing so right now @Levivich Star Mississippi 17:49, 13 December 2022 (UTC)
- @Star Mississippi: Thanks. Would you (or another admin) mind doing a procedural nomination to AFD (through the protection), which is where we need to discuss if the article should be deleted, kept, redirected, etc.? Levivich (talk) 17:46, 13 December 2022 (UTC)
- Wikipedia:Articles for deletion/Vita Zaverukha no pings as there are so many involved I don't want to inadvertently miss someone. Assume all interested parties are watching this thread. Star Mississippi 17:54, 13 December 2022 (UTC)
- Comment Why has Gitz6666 not yet received a topic ban from this entire area? Black Kite (talk) 19:06, 13 December 2022 (UTC)
- Comment @Black Kite: because he is a talented and prolific obfuscator who keeps other editors busy trying to AGF as he contends straight-faced that "likes" on a YouTube video are proof of notability, that Viktor Medvedchuk has [nothing to do with media and NOTFORUM, and that speaking Ukrainian is mandatory for receiving health care there.
- Because he is always the one who files the
AN/Icomplaint:(for example [86][87] declarations on child rapeas "weapon of war" in War crimes in the 2022 Russian invasion of Ukraine -- much later: I should mention that while looking these up, I did see one 3RR case brought against Gitz by My Very best wishes) Then he creatively misunderstands what he is told, and when the thread inevitably erupts in outrage, the AN/I answer is always to go work it out on the talk page. There is , no working it out. Currently there is no agreement at Human rights in Ukraine on "what is Ukraine". All of the sources are fifty-page reports with no page number given, many of them from 2005, 2010, and 2007, ie before the uprising caused by those very human rights abuses.
- Because he is always the one who files the
- I am not in this particular (Vita Zaverukha) knife-fight, but I have been watching it while attempting to discuss at Human rights in Ukraine. I found this thread because I was expecting this complaint or something similar; Gitz had been suspiciously silent. It's an attempt to shoe-horn the text in question into a page about a regiment. I was considering whether to alert @Dennis Brown: that Mhorg is once again working on an attack page about a Ukrainian female. I decided that the prior round of *that* had been a month or so of my life that I will never get back, and that it was more important to try to protect Human rights in Ukraine from being used to make it seem that Russia's purported concern for the rights of Russian speakers seem well-founded. Gitz announced that he was no longer going to
readreply to my posts, which I am sure will do wonders for that whole working it out on the talk page thing; look how much it's done for us already!
- I am not in this particular (Vita Zaverukha) knife-fight, but I have been watching it while attempting to discuss at Human rights in Ukraine. I found this thread because I was expecting this complaint or something similar; Gitz had been suspiciously silent. It's an attempt to shoe-horn the text in question into a page about a regiment. I was considering whether to alert @Dennis Brown: that Mhorg is once again working on an attack page about a Ukrainian female. I decided that the prior round of *that* had been a month or so of my life that I will never get back, and that it was more important to try to protect Human rights in Ukraine from being used to make it seem that Russia's purported concern for the rights of Russian speakers seem well-founded. Gitz announced that he was no longer going to
- I realize that administrators are busy people... I get that, really. But so are most of the rest of us also, and we have fewer tools. Writing this plea for help probably will transform me into an involved editor, so be it. I may as well make it worth the aggravation: if English Wikipedia is to have any hope of an accurate and balanced portrayal of the current war in Ukraine, it needs to take disinformation very seriously and either begin enforcing its policies, or create a team of editors to follow certain editors around.
- I thought Mhorg should have gotten a stricter sanction at the time. He appears to have learned little about either RS or BLPs since then. I thought Gitz should also have been sanctioned, but here we are, and perhaps Gitz sincerely still believes that I have some crazy bias in favor of Ukraine, and that he needs to stand up for oligarchs, who knows. I would prefer to peacefully disappear into medieval French law or the formatting of articles on villages in Tamil Nadu or whatever. But here we are. I am mostly just tired. However I believe that truth is important. Oh and: there appears to be no particular basis for saying that human rights violations by one country in a different country should go in the "human rights in x" article for the country where they took place, that that is just how it is done, unfortunately. This was not a day well-spent.
- I realize that Gitz is an AE matter, but the dizzying array of problems with Gitz' determined effort to find and amplify a war crime or human rights violation that might have been, or [can be portrayed] as having been, committed by a Ukrainian simply doesn't fit in 500 words, and the last time we were there he was excused from this limit. Please send whiskey and trained psychiatrists. These two editors at a *minimum* need remedial coaching on the reliable sources policy, and there is no telling how much Wikipedia articles on this war could be improved if these geysers of misinformation] weren't wreaking whack-a-mole havoc ,all over the topic area, always mysteriously in ways that appear to support Russian propaganda. Elinruby (talk) 01:37, 14 December 2022 (UTC)
- If I may interpolate, so that the diffs are in one place for future reference. I just had this exchange where Gitz6666 butchers a source to make it say something it doesn't, then makes a bizarre accusation against me of wikistalking for questioning that and demands an apology, only to reveal that they knew all along about the content in the source about which they originally feigned complete innocence.. By the by, in that last comment they also reveal they had misused a source to make a stronger claim about the criminal evidence against the BLP topic than even that problematic source would support. A claim that may have had a material impact on the AFD.OsFish (talk) 02:36, 16 December 2022 (UTC)
- I realize that Gitz is an AE matter, but the dizzying array of problems with Gitz' determined effort to find and amplify a war crime or human rights violation that might have been, or [can be portrayed] as having been, committed by a Ukrainian simply doesn't fit in 500 words, and the last time we were there he was excused from this limit. Please send whiskey and trained psychiatrists. These two editors at a *minimum* need remedial coaching on the reliable sources policy, and there is no telling how much Wikipedia articles on this war could be improved if these geysers of misinformation] weren't wreaking whack-a-mole havoc ,all over the topic area, always mysteriously in ways that appear to support Russian propaganda. Elinruby (talk) 01:37, 14 December 2022 (UTC)
- Someone needs to look into that and Goodrover, who is obviously not a new account @OsFish also noted. Alas more than I have time for at the moment. Star Mississippi 19:15, 13 December 2022 (UTC)
- I would also like to nominate Just Prancing, who was showing up on talk pages to agree with Gitz, until I told Gitz to feel free to refrain from having the account sign in. Elinruby (talk) 01:37, 14 December 2022 (UTC)
- For the time being, and without prejudice against other actions, I've notified them of WP:GS/RUSUKR and WP:ARBEE; note that the former authorizes blocks as an enforcement mechanism for the extendedconfirmed restriction if necessary. -- Tamzin[cetacean needed] (she|they|xe) 20:21, 13 December 2022 (UTC)
- Note that BLP is also under discretionary sanctions [88]. Also, Gitz6666 just broke 1RR [89] [90] on related article Human rights in Ukraine. The 1RR was imposed on this article after Gitz6666's edit warring on original Torture in Ukraine article [91]. Gitz6666 has already been banned on Italian and Spanish Wikipedias [92] [93] for edit warring and block evasion. There was also an earlier proposal (in November) here on English Wikipedia of an twelve month topic ban for Gitz6666 for very similar reasons [94]. Volunteer Marek 22:40, 13 December 2022 (UTC)
- Ooops, almost forgot this part [95]. On top of the breaking of 1RR and other disruptive behavior Gitz6666 also wrote this recently: "
I could speculate that it's because your English sucks; or because you're an ignorant, or stupid persons, who is incampable of understanding an exclusive disjunction; or because you're are blinded by ideology and only interested in winning an argument
." It seems they think that by writing "I could speculate" right before a barrage of gross direct insults and personal attacks that somehow "protects" them or makes them immune from following WP:NPA. Volunteer Marek 22:55, 13 December 2022 (UTC)- Yes, I unadvertedly broke 1RR and immediately self-reverted when you pointed it to me [96]. I think you did at least twice as many reverts as I did at Torture in Ukraine, as anyone can see from the edit history. Since you draw attention to my blocks (not banned) on other wikiprojects, my explanations on this can be read on my useropage in the collapsable box "The history of my blocks on it.wiki and es.wiki". Regarding our recent exchanges at Human rights in Ukraine, the diff you shared should be read carefully [97]. Since you've been abusing me and other editors for months, always complaining about our bad faith, lies, dishonesty, deliberate misrepresentations of sources, I was instructing you on how painful it can be to be treated this way. I wasn't insulting you, but I was making a counterfactual reasoning ("how would you feel if I were to tell you this and that?") in order to elicit a spark of empathy, so that you would once and for all stop the behaviour that has made you famous in this community and that everyone, for some incomprehensible reason, willingly accepts. Gitz (talk) (contribs) 00:37, 14 December 2022 (UTC)
- @Black Kite, @Star Mississippi, @Tamzin: One of you (or some admin reading this) should consider indefing Goodrover (talk · contribs · deleted contribs · nuke contribs · logs · filter log · block user · block log) as an obvious LTA sock. Their 17 edits consist of: 10 edits, revert GCB within 1 hour at an article they've never edited before, 1 edit removing vandalism, revert GCB again, 1 edit avoiding a redirect, 1 edit removing vandalism, revert GCB within 2 hours at a different article they've never edited before, 1 edit adding a missing word. Too obvious. Levivich (talk) 20:54, 13 December 2022 (UTC)
- Thanks @Levivich. Declining to do this myself as my revert of Goodrover's edit before protecting the version @GizzyCatBella had reverted to (vs. protecting the "wrong" version) was already IAR/out of process and imagine a subsequent block would lead to unnecessary drama. Agree with your suggested course of action though. Star Mississippi 21:38, 13 December 2022 (UTC)
- For the time being, and without prejudice against other actions, I've notified them of WP:GS/RUSUKR and WP:ARBEE; note that the former authorizes blocks as an enforcement mechanism for the extendedconfirmed restriction if necessary. -- Tamzin[cetacean needed] (she|they|xe) 20:21, 13 December 2022 (UTC)
- @OsFish - This is (the same, as always) usual stocking me always around 🧐 - GizzyCatBella🍁 23:20, 13 December 2022 (UTC)
- Ah, I'd missed that. Blocked as NOTHERE/avoiding scrutiny, probably Icewhiz. -- Tamzin[cetacean needed] (she|they|xe) 00:26, 14 December 2022 (UTC)
- @Black Kite: This subject should probably be dealt with by ArbCom,
just like they dealt with WP:APL. Whatever the issues may be with Gitz's editing, they do not absolve anyone else. François Robere (talk) 13:50, 14 December 2022 (UTC)
- Of course. And of course all of this is happening on DS pages, but the last time AE was suggested Gitz took it as validation and filed a case there himself. "There is no appetite" there for his walls of text, so "anyone else" is left to deal with it. I am not sure why he edits as he does, but it is very consistent.
- I have diffed myself into incoherence above, but am willing to answer any questions. As a TL;DR I would point out that Gitz started this thread on this, the wrong noticeboard, with a somewhat aggressive header, and that that header now links to an AfD discussion where OsFish has made a heroic attempt to explain BLP to him. If not ArbCom then who? Elinruby (talk) 20:05, 14 December 2022 (UTC)
- Yes, ArbCom; perennial disputes, perennial disputants. But coherence is only half of it. Broadly speaking, I don't think there are admins who subscribe to the Russian narrative, not least because even if they were to fail to strictly follow a Western prism, the Sorkovian approach to the dissemination of dis/information is just so jarring, especially to the uninitiated. However, just because one side is mostly lying, doesn't mean the other side if only telling the truth (I hope that doesn't come as a revelation to anybody). Still, those admins who don't subscribe to every thing said by disputants who advance the Ukrainian narrative — well, it's sort of expected that a not insignificant group of editors will grind them down (if lucky, softly) until they do... do that. Or, more likely, until those admins just walk away because it gets too much.
- Whereas any admin who'd be inclined to just automatically side with those editors (advancing the Ukrainian narrative), they'd usually be cognizant enough to either be aware of the extent of their biases, or eventually they'd run into issues with Wikipedia:Independent sources. WP:GAME, etc., which would be difficult to ignore (because it isn't as one-sided as either side claims). Either way, admins have a limited mandate. The most a single admin could for hope is the ad-hoc committee that an WP:AE Results section represents. But ArbCom members have two mandates: WP:RFA + WP:ACE (I think all ACEs have had non-admins candidates, but it is my understanding that only admins have ever been elected as Arbs, feel free to collect me); and they have a fixed body; and-and after all, these are their Discretionary sanctions (or Counter-Terrorists, whatever). So now the secret is out! El_C 23:13, 14 December 2022 (UTC)
- You indented this under my question so it appears to be an attempt to either answer me or mock me; maybe both. I don't know what a "Ukrainian agenda" is and apart from a playmate I had when I was six, I have never spoken to any Ukranians. I think you're telling me that I am shouting at the sky, and I guess I am. I do apologize for that, even though I didn't start this dumpster fire on the wrong board, and am just here to say that this prolific editor starts these fires all over the topic area, constantly constantly constantly. I will go away now, but I want to mention first that my agenda is merely that I like the things we write in Wikipedia articles to reflect some version of the truth, and to be supported by reliable sources. I have no interest in running for admin, if that is what you are suggesting. I just had always thought that editing standards applied to all articles, DS or not. I stand corrected. It's a AE matter and they "have no appetite." EE is a sacrifice zone. Check. I will now cease from trying to alert someone to the dumpster fire. Peace out. If I am misunderstanding you, I am sorry and please feel free to post on my page. Elinruby (talk) 02:41, 15 December 2022 (UTC)
- Yes, you are misunderstanding me. These are very broad generalizations directed at all disputants. You yourself was not highlighted as far as your role in these overarching disputes (the extent of which I'm unsure of, anyway). Disputes, plural, not just whatever this particular thing here is (which I only skimmed). Anyway, you asked about ArbCom, I explained why that would be a yes. You mentioned issues with diff/summary coherence, which I'd largely attribute to this chaotic, structureless forum, and which is why I argue WP:AE / WP:RFAR are better for these matters. For my part, I explained why disputants had been receiving so little assistance (of significance). Assistance either from individual admins, like here at AN or ANI, or even a quorum of admins at the WP:AE board. And it doesn't have to be an AE matter — anyone is free to make it a community matter. I just have doubts decisive action will come from that avenue. But the option is there. The option of the AE board is there. The option of RfAR is there. How from all that we got to me somehow mocking you, or anyone, I'm at a loss. Also, when I mentioned RfA and mandate, that's from the admin perspective. Just like when I mention ArbCom's mandate and the ACE; their double mandate (RfAs + ACE). I realize it's all rather deep in the theory sauce, but how you went from any of that to me suggesting you run for admin... other things... truly the farthest thing from my mind. Again, my above treatise didn't especially concern you, its indent flow notwithstanding. El_C 04:20, 15 December 2022 (UTC)
- Yes,that is the problem with these walls of text; nobody reads them. Imagine what they do to discussion. The behavior has been to AE. They "have no appetite",and ANI has no time. I appreciate your clarification, of which I was notified at another project. Glad to hear that I was confused about why you were telling me this for the good reason that you weren't.
- Yes, you are misunderstanding me. These are very broad generalizations directed at all disputants. You yourself was not highlighted as far as your role in these overarching disputes (the extent of which I'm unsure of, anyway). Disputes, plural, not just whatever this particular thing here is (which I only skimmed). Anyway, you asked about ArbCom, I explained why that would be a yes. You mentioned issues with diff/summary coherence, which I'd largely attribute to this chaotic, structureless forum, and which is why I argue WP:AE / WP:RFAR are better for these matters. For my part, I explained why disputants had been receiving so little assistance (of significance). Assistance either from individual admins, like here at AN or ANI, or even a quorum of admins at the WP:AE board. And it doesn't have to be an AE matter — anyone is free to make it a community matter. I just have doubts decisive action will come from that avenue. But the option is there. The option of the AE board is there. The option of RfAR is there. How from all that we got to me somehow mocking you, or anyone, I'm at a loss. Also, when I mentioned RfA and mandate, that's from the admin perspective. Just like when I mention ArbCom's mandate and the ACE; their double mandate (RfAs + ACE). I realize it's all rather deep in the theory sauce, but how you went from any of that to me suggesting you run for admin... other things... truly the farthest thing from my mind. Again, my above treatise didn't especially concern you, its indent flow notwithstanding. El_C 04:20, 15 December 2022 (UTC)
- You indented this under my question so it appears to be an attempt to either answer me or mock me; maybe both. I don't know what a "Ukrainian agenda" is and apart from a playmate I had when I was six, I have never spoken to any Ukranians. I think you're telling me that I am shouting at the sky, and I guess I am. I do apologize for that, even though I didn't start this dumpster fire on the wrong board, and am just here to say that this prolific editor starts these fires all over the topic area, constantly constantly constantly. I will go away now, but I want to mention first that my agenda is merely that I like the things we write in Wikipedia articles to reflect some version of the truth, and to be supported by reliable sources. I have no interest in running for admin, if that is what you are suggesting. I just had always thought that editing standards applied to all articles, DS or not. I stand corrected. It's a AE matter and they "have no appetite." EE is a sacrifice zone. Check. I will now cease from trying to alert someone to the dumpster fire. Peace out. If I am misunderstanding you, I am sorry and please feel free to post on my page. Elinruby (talk) 02:41, 15 December 2022 (UTC)
- However.
- If English Wikipedia doesn't care that the dumpster is on fire, I guess I'll stop trying to put out the flames. I have no appetite either, never did, just thought it was.important. I was only ever here because of some silly notions I had about the truth. Ta for the answer, and thanks for all the fish. Elinruby (talk) 04:54, 15 December 2022 (UTC)
- The English Wikipedia is not a monolith, though. And in fairness, pretty much everyone views themselves as wanting to advance neutrality. But diametrically opposing sides exist nonetheless. These problems I point to are ingrained in every fraught topic area, ones covered by sanction regimes or not. But the Russian invasion of Ukraine facet of WP:ARBEE is probably the most acute of them all right now, because it's contemporaneous and because of its intensity and scale.
- As noted, this (here) forum available to the community is limited, since it's so susceptible to disorganization, text walls, etc. Which is why it is unlikely to accomplish anything beyond the simple WP:XC tenure mandated by WP:GS/RUSUKR. Which, don't get me wrong, goes a long way, but has little impact on veteran editors.
- Even the AE board, where admins might have the added benefit of a group (quorum), seems to have reached its limits wrt perennial problems in this area of the EE editing ecosystem. So what's left is a full case @WP:RFAR. But that's a major time investment which brings its own uncertainties (including not even making it passed the preliminaries). Still, for quelling the flames in a serious way, I can't think of anything else. But I'm open to ideas. El_C 06:25, 15 December 2022 (UTC)
- Wikipedia's procedural channels of dispute resolution are too obscure and intricate for me to have an opinion on how to proceed. I confess I have difficulty in following your discussion about RFA, ACE, RFAR: I simply get lost, sorry. I trust that you admins will find the most appropriate way, if there is an appropriate way, to sort this out. But from what little I understand, I point out the following:
you yourself was not highlighted
. No, Elinruby is by all means part of this dispute. In any proceedings aimed at addressing the EE controversy globally, Elinruby should have an appropriate standing as one of the main actors, who have made notable contributions to the discussion on Azov Regiment, Torture of Russian soldiers in Mala Rohan, Torture in Ukraine, Human rights in Ukraine, and to various AE, ANI and RSN discussions, such as this, Raping and killing a 1-year-old in Ukraine as alleged by Ukr. politician and reported by Daily Beast and Yahoo News, where we first met and interacted.- While globally addressing the EE controversies may be difficult or even impossible, time-consuming and probably unfair because of the various strongly felt POVs, I think that addressing individual behaviours by editors should be possible: e.g., Elinruby's repeated personal attacks on me, bordering on harassment, could be sanctioned immediately; Volunteer Marek's disruption and uncivility here and at Torture in Ukraine are quite apparent and could be sanctioned; and I myself inadvertently violated the 1RR rule yesterday on Human rights in Ukraine, and this is also sanctionable behaviour. So when we do something wrong in the EE area, and it happens quite often, admins could perhaps warn us and/or apply proportionate sanctions to de-escalate the conflict and establish boundaries.
- However, if we are to deal with this dispute globally, something must be very clear from the outset: I am not a Putin supporter. I have been saying both privately and publicly for at least 10 years that Putin is a dictator, and it would be ridiculous and unacceptable for me to be made out as a Russian sympathiser in this war. I have a deep interest in international law and human rights activism, and a commitment to NPOV as a core value of this encyclopaedia - that's all. From my point of view, the EE controversy stems from the fact that there are 3 or 4 users who cause disruption by engaging in nationalist editing and pursuing an anti-Russian agenda. I may be right, I may be wrong, but from my point of view this is the "global" issue of the EE area, and it affects the war in Ukraine only indirectly.
- Gitz (talk) (contribs) 11:25, 15 December 2022 (UTC)
- Gitz, this has happened like four time already. There's an ANI thread which you're involved in, either started by you or about you. In that thread there's multiple suggestions, including by uninvolved parties, of a topic ban for YOU [98] on account of your WP:TENDENTIOUS behavior and WP:IDIDNTHEARTHAT. Yet somehow what you get out of these discussions, reflected in your subsequent comments, is that you were in fact vindicated and the discussants actually were critical of those who disagree with you. Basically, the opposite of what you *should* get out of these discussions. Which, in a way, is a perfect illustration of... your WP:TENDENTIOUS behavior and WP:IDIDNTHEARTHAT.
- And seriously, trying to scaremonger about "nationalist editors pursuing an anti-Russian agenda" after everything that's happened in the past 10 months, since Russia invaded Ukraine, just sounds... sad. Volunteer Marek 03:11, 17 December 2022 (UTC)
- I agree with your last two sentences. Nobody here is going to do anything about that. Levivich (talk) 14:18, 15 December 2022 (UTC)
- Wikipedia's procedural channels of dispute resolution are too obscure and intricate for me to have an opinion on how to proceed. I confess I have difficulty in following your discussion about RFA, ACE, RFAR: I simply get lost, sorry. I trust that you admins will find the most appropriate way, if there is an appropriate way, to sort this out. But from what little I understand, I point out the following:
Well, few whose contributions generally oppose the Ukrainian narrative are pro-Putin. Supporting Putin outright would be as unpalatable as Polonium on the English Wikipedia. So, it's obviously not black and white. It is degrees on a continuum. Similarly to how at WP:APL, VM and GCB are not outright supporters of the revisionist narrative espoused by the Polish sate, but their edits still lend credence to its more nuanced, more subtle, more palatable components. This is not a new thing, not for EE, not for fraught topic areas, in general. Above all else, be realistic. Statements like: admins could perhaps warn us and/or apply proportionate sanctions to de-escalate the conflict and establish boundaries
, just seem unrealistic. Wikipedia arcane rules are indeed not easy to comprehend. Hopefully, what is contained in yesterday's announcement by ArbCom (see below: #Contentious topics procedure adopted) will help to alleviate in that in the long run.
But for now, if the two of you and others are serious in making meaningful progress, you could do so by... focusing. By largely avoiding various sidetracks. Because that is, has been, and always will be the Achilles' heel of this type of forum, with its free flowing threaded discussion and no character limit. Otherwise, like countless similar threads before it, this discussion will get too long, too drawn out, too convoluted for anyone except those already deeply involved and familiar with its intricacies. Which probably already happened. My view, then, is that now's the time to compile evidence, organize it coherently, so one could make a convincing argument to ArbCom that a major intervention is, in fact, not just due but overdue. El_C 14:14, 15 December 2022 (UTC)
- "is, in fact, not just due but overdue". Hmmm. Let's see. How many WP:AE reports have there been regarding Ukraine since the war started (i.e. past ten months). Let's see... ... ... twoooooo? That's all I can find. One, early was quickly and rightly resolved and the other one where you "concurred with me" ... not sure what happened there. Two AE reports in ten months is really nothing though.
- But you know what would help to NOT escalate the disputes? If outside editors, who are not editing in this topic area AT ALL, would stop showing up to these discussions and brining up irrelevancies from other contentious topic area (APL! APL! APL! <-- what purpose does that serve? And why did Francois Robere "pre-strike" it in some weird kind of WP:POINT) just to get their kicks in against editors whom they have long standing grudges against. I mean, that's like dictionary definition of WP:BATTLEGROUND.
- also, your characterization of my views on the Polish state "narrative" is completely off the mark, but oh well, whatever Volunteer Marek 03:59, 17 December 2022 (UTC)
- @Elinruby: If that's any consolation, I've been in your position more than once, and have received the same replies about a lack of "appetite" and "bandwidth" from that admin. Drinks on me if you're still involved in this TA this time next year. François Robere (talk) 14:09, 15 December 2022 (UTC)
- BTW for some reason, François Robere often writes topic area as "TA," which for some reason always takes me a while to parse as such. Now that's how you sidetrack (ST)! El_C 14:23, 15 December 2022 (UTC)
- I would've written WP:TA instead, but it's already taken by Wikipedia:WikiProject Textile Arts, and we don't deserve the kind of wholesome discussions they have there. François Robere (talk) 16:50, 15 December 2022 (UTC)
- I was surprised that no one snatched the WP:KURDS domain wpname before Arby's. Wikipedia:WikiProject EastEnders has WP:EE, so it's in good hands (probably). El_C 18:09, 15 December 2022 (UTC)
- I'm such a hopeless Westerner, every time I see "WP:KURDS", I think "WP:ANDWHEY". Levivich (talk) 18:31, 15 December 2022 (UTC)
- I was surprised that no one snatched the WP:KURDS domain wpname before Arby's. Wikipedia:WikiProject EastEnders has WP:EE, so it's in good hands (probably). El_C 18:09, 15 December 2022 (UTC)
- I would've written WP:TA instead, but it's already taken by Wikipedia:WikiProject Textile Arts, and we don't deserve the kind of wholesome discussions they have there. François Robere (talk) 16:50, 15 December 2022 (UTC)
- BTW for some reason, François Robere often writes topic area as "TA," which for some reason always takes me a while to parse as such. Now that's how you sidetrack (ST)! El_C 14:23, 15 December 2022 (UTC)
- Obviously, this is to be decided on AfD. Therefore, bringing this to WP:AN is an example of WP:BATTLE, in my opinion. Speaking on the matter of bias (and I am not accusing anyone of any bias here), this is complicated. Based on the peculiar nature of the regime, one could reasonably argue that Wikipedia:No Nazis should be applicable in that case, but this is not a position generally shared by WP administrators if I understand correctly. My very best wishes (talk) 12:13, 18 December 2022 (UTC)
- I don't understand what you mean. Should I have been the one to bring the article to AfD even though I don't want to delete it? Or should Volunteer Marek have done so, and refusing to bring it to AfD is an example of WP:BATTLE? I asked the admins what was the right way (talk page discussion, AfD or RfC) to resolve an editorial dispute. How can this be an example of BATTLE? Gitz (talk) (contribs) 12:27, 18 December 2022 (UTC)
- Might as well just wait for the AfD to conclude at this point. Selfstudier (talk) 12:49, 18 December 2022 (UTC)
Elizabeth of Luxembourg: Revision history
editPlease take a look at Elizabeth of Luxembourg. User:Super20020917 insists that she was not a monarch because other Wikipedia pages do not list her as a ruler, so this page should conform to those, despite the fact that I can provide published, recognized sources for the opposite statements, while they cannot. [1][2] [3] [4] Deamonpen (talk) 15:11, 18 December 2022 (UTC)
- This is a content dispute and should be discussed on Talk:Elizabeth of Luxembourg. I've protected the article for the time being. Mackensen (talk) 15:31, 18 December 2022 (UTC)
References
- ^ Dvořáková, Daniela (2021). Barbara of Cilli (1392-1451) : a Hungarian, Holy Roman, and Bohemian queen. Leiden. p. 181. ISBN 978-90-04-49916-4. Retrieved 13 December 2022.
The Hungarian estates had already elected him as king and Elizabeth as queen on 18 December in Bratislava. The election affected both spouses, who thus became equivalent rulers.
{{cite book}}
: CS1 maint: location missing publisher (link) - ^ Burkhardt, Julia (15 November 2022). "Albert II of Habsburg's Composite Monarchy (1437–39) and Its Significance for Central Europe". Unions and Divisions: 224–236. doi:10.4324/9781003199007-21.
As had previously been the case, Albert's wife Elizabeth (herself, of course, the legitimate crowned queen) acted as regent for her husband in his absence, taking care of governmental affairs along with the royal council. Several charters issued in the queen's name testify to her crucial role as an arbitrator in legal disputes, and to her involvement in waivers of tax liability or the enlargement of the realm's fortifications. Numerous towns and fortresses which she had received from Albert, predominantly in the northern part of Hungary, constituted her power base.
- ^ Andrássy (gróf), Gyula (1908). The Development of Hungarian Constitutional Liberty. K. Paul, Trench, Trübner. p. 173. Retrieved 18 December 2022.
King Albert left a widow , who had previously been crowned queen of Hungary . Upon her husband's death Queen Elizabeth's independent right to the crown revived , for a law of 1439 had declared that the crown belonged by right of birth not to the king but to the queen . The nobles did not question her right , but as a woman ruler might not prove strong enough , they were desirous of finding for her a consort to share her throne
- ^ Komjathy, Anthony Tihamer (1982). A Thousand Years of the Hungarian Art of War. Rákóczi Foundation. p. 26. ISBN 978-0-8191-6524-4. Retrieved 13 December 2022.
Although Queen Elizabeth was recognized as a co-ruler of Hungary. the nobles elected a new king in the person of Wladislaw V, King of Poland. Elizabeth. who was pregnant with Albrecht's child, could not prevent the coronation.
Review Anomie's mass rollback
editBackground for this I have been categorizing the past subtemplates of {{TFA title}} by year like this. To those who are not aware, the daily subtemplates of {{TFA title}} store the name of TFA of that day and is used to display an editnotice at the article when it is linked from the mainpage. My checks before going with this categorization task showed me that only the present and future subtemplates are of active use. Beyond 2 days after the TFA has come off the mainpage, they do not any function and gets abandoned. They are flagged as uncategorized templates and I was looking to take out this easy group. I have noincluded the categories as is normally done when categorizing templates, so that their functionality does not break on transclusion or substing.
I made approx. 2,100 edits between December 6 - 15 in several batches by carefully selecting pages. Yesterday Anomie mass rollbacked them and alleged that I am running an unauthorized bot and claimed that it was "breaking various uses of those pages" [99][100]. When asked for an example of a tool that was broken from my edits, they linked to this which involved a previous incident of a future template that was causing problem to TFA Protector Bot when someone had added a HTML comment. That is not relevant since all of my edits have been to past templates from 2010-16 and I was not adding any comment. When asked which tools use past templates, they refused to explain saying "I'm not going to play that game" [101].
As I have explained in my talkpage, I am prepared to do this from a bot account if necessary. I had not done so because I felt the number of pages involved did not need a bot and a lot of AWB users do edits of larger scale and with a faster edit rate than what I have. These were not completely undiscussed edits on my part, I had asked for temporary Template editor rigths explicitly for this purpose (link). I have looked further today and I cannot find evidence of any tools broken from my edits. What is troubling is that Anomie mass rollbacked 2,100 edits without discussing anything with me, as if was causing active harm and needed urgent rollback. This a serious misuse of rollback and refusing to discuss it is a failure of WP:ADMINACCT. I am requesting review from more admins on this. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 13:10, 17 December 2022 (UTC)
- The discussion seems to be happening in the appropriate location (your talk page). I don't see any benefit for the encyclopedia from your edits, and if there is a potential issue, rolling back quickly is the correct first response. If you want to do mass edits, you have to be prepared to defend them. —Kusma (talk) 13:35, 17 December 2022 (UTC)
- Why "if there is a potential issue, rolling back quickly is the correct first response", and where is that in policy? What does "If you want to do mass edits, you have to be prepared to defend them" mean and where is that in policy? I don't think our policies are so aggressive as to state that if there is a potential problem, edits should be rolled back quickly as a first response, nor that anyone needs to be prepared to "defend" their edits. Levivich (talk) 13:40, 17 December 2022 (UTC)
- This is WP:BRD. The bar to bold editing is higher for mass edits. I don't know whether this is in written policy, but this is how we treat mass editing in general. —Kusma (talk) 13:44, 17 December 2022 (UTC)
- @Kusma I am prepared to defend my edits, Anomie has explicitly refused to defend their's, which is why I have brought this here. They are refusing to follow the D part of BRD, which also involves their use of admin tools (mass rollback). ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 14:14, 17 December 2022 (UTC)
- So what is the point of your edits? They don't seem to do anything useful at all. If you have a grand plan what to do with these categories, please say what it is. If all you want is try to make sure that every page that happens to be in the template namespace is in some category, please stop, this is at best pointless, and arguably disruptive. Whether pages are in the Template or Wikipedia or Wikipedia talk namespace often has nothing to do with their function, just with what people fifteen years ago randomly wrote without much thought, so do not infer from that whether they need to be categorised or not. —Kusma (talk) 14:35, 17 December 2022 (UTC)
- Uncategorized templates appear in maintenance reports, my edits take out thousands of easy bits and unclutter them to make them more useful. I had vague plans to nominate these populated in categories for TFD later, since they are abandoned templates with no future use, something which WikiCleanerMan had brought up before. Putting them in a category would have made them for easy tracking, which is the whole point of categories. I am not adding categories to every single page in template namespace and nothing at all for WP and WT pages. If you are arguing that they are dsruptive, how exactly is it and what exactly does it disrupt? ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 14:56, 17 December 2022 (UTC)
- It leads to this pointless arguing? Seriously, the "unused templates" and "uncategorised templates" reports appear to do more harm than good. Being listed in such a maintenance report is not a problem. It just points out that there might be a problem (if you ask me, the problem with the template namespace is that it does not contain enough currently unused templates, as deleting templates breaks old versions of articles. We should have never started deleting harmless unused templates, but focus just on harmful ones). If you try to solve this non-problem by mass edits instead of just ignoring these pages on the maintenance report (or even better, change the maintenance report so it ignores these pages), well, you end up here. I don't understand why you would want to categorise subpages of a given page, as they are already neatly trackable by being subpages of that page. —Kusma (talk) 15:41, 17 December 2022 (UTC)
- (@Kusma: Without regard for the other topics under discussion, I just want to say in response to this:
if you ask me, the problem with the template namespace is that it does not contain enough currently unused templates, as deleting templates breaks old versions of articles. We should have never started deleting harmless unused templates, but focus just on harmful ones
A-fucking-men. Every time I view an olddddd revision of a page and see redlinked template invocations my blood pressure rises. It's not like deleting them saves server space or something, as the revisions exist forever. Better, if anything, to protect them in their last functional state and put a big notice at the top that they're deprecated. Maybe even add something to MediaWiki that can flag a template as unusable in current revisions so they can't accidentally be used for current work. Anyways, carry on. —Locke Cole • t • c 20:04, 17 December 2022 (UTC))
- (@Kusma: Without regard for the other topics under discussion, I just want to say in response to this:
- It leads to this pointless arguing? Seriously, the "unused templates" and "uncategorised templates" reports appear to do more harm than good. Being listed in such a maintenance report is not a problem. It just points out that there might be a problem (if you ask me, the problem with the template namespace is that it does not contain enough currently unused templates, as deleting templates breaks old versions of articles. We should have never started deleting harmless unused templates, but focus just on harmful ones). If you try to solve this non-problem by mass edits instead of just ignoring these pages on the maintenance report (or even better, change the maintenance report so it ignores these pages), well, you end up here. I don't understand why you would want to categorise subpages of a given page, as they are already neatly trackable by being subpages of that page. —Kusma (talk) 15:41, 17 December 2022 (UTC)
- (edit conflict) As far as I can tell from Special:Diff/1127691929 (and their reply just above), "try[ing] to make sure that every page that happens to be in the template namespace is in some category" is exactly what they're doing:
I have been picking them from uncategorized templates reports
. Although which report that it is not clear to me, since these don't appear on Wikipedia:Database reports/Uncategorized templates. They also pointed to Wikipedia:Database reports/Unused templates/36, which was apparently intentionally broken by a maintainer and there's now Wikipedia:Database reports/Unused templates (filtered) as a usable version of the broken report. Anomie⚔ 15:23, 17 December 2022 (UTC)
- Uncategorized templates appear in maintenance reports, my edits take out thousands of easy bits and unclutter them to make them more useful. I had vague plans to nominate these populated in categories for TFD later, since they are abandoned templates with no future use, something which WikiCleanerMan had brought up before. Putting them in a category would have made them for easy tracking, which is the whole point of categories. I am not adding categories to every single page in template namespace and nothing at all for WP and WT pages. If you are arguing that they are dsruptive, how exactly is it and what exactly does it disrupt? ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 14:56, 17 December 2022 (UTC)
- So what is the point of your edits? They don't seem to do anything useful at all. If you have a grand plan what to do with these categories, please say what it is. If all you want is try to make sure that every page that happens to be in the template namespace is in some category, please stop, this is at best pointless, and arguably disruptive. Whether pages are in the Template or Wikipedia or Wikipedia talk namespace often has nothing to do with their function, just with what people fifteen years ago randomly wrote without much thought, so do not infer from that whether they need to be categorised or not. —Kusma (talk) 14:35, 17 December 2022 (UTC)
- @Kusma I am prepared to defend my edits, Anomie has explicitly refused to defend their's, which is why I have brought this here. They are refusing to follow the D part of BRD, which also involves their use of admin tools (mass rollback). ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 14:14, 17 December 2022 (UTC)
- This is WP:BRD. The bar to bold editing is higher for mass edits. I don't know whether this is in written policy, but this is how we treat mass editing in general. —Kusma (talk) 13:44, 17 December 2022 (UTC)
- Why "if there is a potential issue, rolling back quickly is the correct first response", and where is that in policy? What does "If you want to do mass edits, you have to be prepared to defend them" mean and where is that in policy? I don't think our policies are so aggressive as to state that if there is a potential problem, edits should be rolled back quickly as a first response, nor that anyone needs to be prepared to "defend" their edits. Levivich (talk) 13:40, 17 December 2022 (UTC)
I'd appreciate it if Anomie (talk · contribs) could clarify here, on this page, what pages/tools ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ broke with their edits. That appears to be a specific disputed factual point and I don't understand what they mean by "not playing that game." If they made a mistake then that's fine, we all make mistakes, but letting the question go unanswered is clouding the issue. Mackensen (talk) 14:41, 17 December 2022 (UTC)
- I'm not playing the game of having to be aware of every possible Lua module and external tool to find one good enough to satisfy random demands. I already pointed to one example of breakage when one of these contained content other than the page title (which is how they've been since they started to be created in 2010), but that wasn't good enough for ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ because they hadn't gotten to today yet with their mass edits. Anomie⚔ 15:23, 17 December 2022 (UTC)
- To clarify then, your mass rollbacking was not based on actual breakage, but on the assumption that some module or tool somewhere would break? That's what you appear to be saying here, but that's not what you said to ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ. To be clear I think that's a facially reasonable position, though if no breakage had appeared over a ten-day period the edits were probably safe? Mackensen (talk) 15:33, 17 December 2022 (UTC)
- As I pointed out, at least one tool was broken when one of these pages had extraneous wikitext for a different reason. I don't find it particularly convincing to dismiss that example because it happened to be the current day's page at the time rather than a past one. And if for some reason we did want to change the format of these pages, it would be best to have a bot do them all, including all those going forward, rather than stopping at 2016 or some other past date. Similarly there's no reason to have arbitrary year categories in order to list these at TFD, as already proven by Wikipedia:Templates for discussion/Log/2019 March 9#Old Template:POTD_protected/YYYY-MM-DD templates for example (which, again, succeeds where ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ's stated plans fail in considering the future too, although in this case I'd !vote to oppose the TFD). Anomie⚔ 15:57, 17 December 2022 (UTC)
- So you have no evidence of anything that was broken from my edits and mass rollbacked them just because there might be something? You can't be bothered to see what my edits broke yet mass rollbacked them anyway. How is this not an egregious misuse of rollback? Asking for evidence of what was broken from my edits that you mass rollbacked is not a "random demand", it is basic WP:ADMINACCT. Noincludes do not interfere with Lua usages and nor does it disrupt any substed usage as the template doc says. Leaving things be beacuse it was always like that is not the wiki way of doing things. If you had asked me before rollbacking them, I would have told you I had no intention of adding categories to present and future templates. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 15:37, 17 December 2022 (UTC)
- Where in WP:ADMINACCT or anywhere else does it say I need to prove to your satisfaction that your specific edits broke something specific? And it seems to me that that makes your categorization project even more pointless, if it's not going to be done for future templates too. Anomie⚔ 15:44, 17 December 2022 (UTC)
- I don't get why you and Kusma are being so hostile to this editor, like he's a vandal or troll or something. Levivich (talk) 15:53, 17 December 2022 (UTC)
- You have used your admin tools to mass rollback over two thousand of my edits, without evidence it is breaking something. I am perfectly entitled to ask how my edits were causing problems and you have to justify why it needed mass rollback without any discussion. I was not going to categorize present and future templates on my own since I was aware from before doing this task that it was used by TFA protector bot and a modification to it was needed beforehand. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 16:03, 17 December 2022 (UTC)
- You seem to misunderstand WP:ADMINACCT, to be fair. You are free to criticise Anomie's actions and to ask him to explain himself; however, Anomie only has to respond civilly to queries, which, as far as I can see, he has done. Policy does not require him to persuade you or to continue debating the issue until you feel you have received a satisfactory answer. For my money, this thread should be closed and the discussion should be moved to a more appropriate venue, to see whether your edits are supported by consensus or not. Salvio 16:16, 17 December 2022 (UTC)
- Their justification has been, to paraphrase, "it broke something". By their own admission above, they have no evidence that my edits had actually broken anything when they decided to mass rollback. They have mass rollbacked 2 thousand edits without any evidence of problem. I have seen editors having their rollback perm revoked after a few misuse. And yet this is supposed to be okay just because they have responded civilly, that too after I brought this here? If a non admin rollbacks someone's 2 thousand edits giving the same reason of "it broke something but I can't be bothered to look what", are they not going to get blocked without hesitation? Please don't be so quick to close this thread. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 16:45, 17 December 2022 (UTC)
- @Salvio giuliano Well, I think we got a full explanation after Anomie was dragged to WP:AN and queried by multiple editors. It remains the case that the initial explanation was inaccurate, at best, and that the justification amounts to "because I felt like it." We can and should do better.
- @ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ there isn't much left to do here. You deserved a better explanation from the outset and you didn't get one, and I'm sorry about that. I suggest starting a discussion (not sure where, to be honest) to gain consensus for the changes you want to make. Mackensen (talk) 17:15, 17 December 2022 (UTC)
- You seem to misunderstand WP:ADMINACCT, to be fair. You are free to criticise Anomie's actions and to ask him to explain himself; however, Anomie only has to respond civilly to queries, which, as far as I can see, he has done. Policy does not require him to persuade you or to continue debating the issue until you feel you have received a satisfactory answer. For my money, this thread should be closed and the discussion should be moved to a more appropriate venue, to see whether your edits are supported by consensus or not. Salvio 16:16, 17 December 2022 (UTC)
- Where in WP:ADMINACCT or anywhere else does it say I need to prove to your satisfaction that your specific edits broke something specific? And it seems to me that that makes your categorization project even more pointless, if it's not going to be done for future templates too. Anomie⚔ 15:44, 17 December 2022 (UTC)
- To clarify then, your mass rollbacking was not based on actual breakage, but on the assumption that some module or tool somewhere would break? That's what you appear to be saying here, but that's not what you said to ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ. To be clear I think that's a facially reasonable position, though if no breakage had appeared over a ten-day period the edits were probably safe? Mackensen (talk) 15:33, 17 December 2022 (UTC)
- As the person who complained last time someone accidentally broke the TFA title templates because it broke TFA Protector Bot, I don't see anything wrong with Anomie's actions nor response. The whole point of these templates is that the entire wikitext is *just* the page title. Adding anything else, like was done here, is actively breaking the templates and is rollback worthy IMO. For those not aware, this discussion explains some of the uses of these templates, in addition to my bot and probably other tools out there.
- The fact that it took 10 days to notice resulting in 2000+ edits doesn't really change the fact that these edits were harmful in the first place. To me using template editor privileges in a way that requires such a mass rollback is a much larger issue.
- @Anomie: maybe we can add the Bot use warning in a group editnotice so people don't try to mess with these templates in the future? Legoktm (talk) 18:05, 17 December 2022 (UTC)
- Whether categories are desired for these pages or not, adding them shouldn't break bots. If a bot is incompatible with categories being added to a page, I'd say the bot needs to be fixed. We shouldn't be blaming users for not behaving in the way bots expect them to do. ~ ToBeFree (talk) 18:18, 17 December 2022 (UTC)
- @ToBeFree: That logic usually makes sense for normal pages, but that's not what is at issue here. These templates are explicitly for bots and other tools to get the page title of that day's TFA, nothing else. Humans are the ones who shouldn't be using these pages! If we want to discuss bots taking humans into account, I already took the time (building on MZ's work) to set up a separate database report that explicitly excludes these templates to better accommodate the humans that work on uncategorized templates. Legoktm (talk) 18:27, 17 December 2022 (UTC)
- I'm surprised you don't have a problem with the response. A block threat is a lousy way to start a discussion, and dismissing requests for explanation is a lousy way to conclude one. It doesn't actually matter if they were good or bad edits. Sure, bold edits can be reverted, but BRD isn't BR-block threat-refuse-to-D. Levivich (talk) 18:41, 17 December 2022 (UTC)
- You may want to read that again, as you seem to have completely misinterpreted Special:Diff/1127670633. The block warning was clearly in reference to the apparent running of an unauthorized bot, per WP:Bot policy which states
The operation of unapproved bots, or use of approved bots in ways outside their approved conditions of operation, is prohibited and may in some cases lead to blocking of the user account and possible sanctions for the operator.
Note that the edits were not reverted for being part of an unauthorized "bot" run, but for the fact that they broke the intended use of the templates as has already been described above. As for BRD, it's also not "BR-irrelevant-arguing". Anomie⚔ 19:39, 17 December 2022 (UTC)- A block threat is a lousy way to start a discussion about unauthorized bot-like editing. I'm not sure that 2000 edits over 10 days with AWB is bot-like editing, but still, is it a big ask not to open with a block threat? This would not have escalated if you had written something like this instead of talking about blocks and breaking things: "Hi. I reverted your edits to these templates because I think there is consensus to only have titles in these templates and nothing else." Levivich (talk) 20:21, 17 December 2022 (UTC)
- @Levivich: I don't think it's appropriate to make bold edits to pages that are 1) auto-template protected, 2) used in interface messages (editnotices), 3) control what adminbots do. Given all of those, it seems appropriate to exercise caution; so learning that it was done on such a mass scale seems incredibly reckless to me.
- I'm mostly confused by the actions taken, because there seem like much better options to have handled this. If you see a bot is creating pages that require manual cleanup, the first thing to do is ask the bot operator to fix the pages so they don't need to be cleaned up. That would've surfaced that adding a category is problematic and we would've avoided this. Or if the assertion is that it's OK to break the templates because they're unused (which seems to be the current argument), just follow the normal process for unused templates - nominate them for deletion. Legoktm (talk) 00:09, 18 December 2022 (UTC)
- None of what you've written is about the response. Levivich (talk) 00:15, 18 December 2022 (UTC)
- @Levivich: I thought it was implied but to be explicit, my impression is that the community generally takes a dim view of people causing disruption on a mass scale, especially when automation is used, hence the provisions in the bot policy. So, making that large scale of edits, that have no apparent justification, without discussing it first, saying that continuing to do so will result in a block doesn't seem out of line. (And I'd generally defer to Anomie on these kinds of matters anyways.) I personally would've not threatened a block simply because I have no intention of rollbacking 2000 edits; rather I would've told them to clean up their own mess.
- As retroactive justification, when I read comments like
I have spread ~2,100 edits in batches over 10 days, it is not an unauthorized bot
and citing the non-filtered database report, to me it shows a lack of understanding the bot policy (specifically WP:MEATBOT) and consideration whether making these edits was a good idea. Legoktm (talk) 00:47, 18 December 2022 (UTC)- A block threat is a lousy way to start a discussion, even if -- and I want to be absolutely clear here -- even if the other person did something blockable. I'm stunned that you or anyone else would have trouble with this rather simple concept. Don't start a conversation with a block threat, duh. Levivich (talk) 01:24, 18 December 2022 (UTC)
- At the risk of discussing too much of a hypothetical, is a block threat not appropriate if you actually intend to go through with it (should the disruption continue)? Compared to not issuing the threat, and then blocking, then getting complaints that you didn't properly warn them that a block was a possibility. Legoktm (talk) 01:38, 18 December 2022 (UTC)
- Obviously, a better sequence of events is: (1) ask the person politely and non-threateningly to stop, (2) only proceed to threaten if they refuse. 100.36.106.199 (talk) 02:11, 18 December 2022 (UTC)
- Yes, a block threat is appropriate when you actually intend to go through with it. Intending to go through with a block, however, is not appropriate at the beginning of a conversation. One shouldn't start a conversation by talking about blocks because that's aggressive and likely to prompt a defensive reaction rather than a cooperative one. "Don't go in hot and heavy," as the saying goes. Levivich (talk) 02:13, 18 December 2022 (UTC)
- My main issue with this is not the block warning, it is their use of mass rollback and refusal to discuss it, which left me with no choice but to bring this here. When I first saw the mass rollback, I thought "God I must have screwed up something epically if such a drastic action was needed". Only to get told here that they did not actually have evidence of anything broken and can't be bothered to look for it.
- Legoktm has said below that TFA protector bot does not use past templates and they had used it to generate a report which appear to have been by substing the templates, something which my edits would not break. I take responsibility for any mistakes I make and am open to learn from it. The crux of the matter is Has my addition of noincluded categories to pre-2016 templates broke anything badly enough that it needed urgent mass rollback?. Anomie's characterizing it as "random demand" and "irrelevant-arguing" is their attempt to deflect blame away from their mass rollback done without any care. If you are saying I have irresponsibly broken or harmed something or created a mess, at least have the decency to show what I have broken, coz I am yet to see anything that is broken or would break. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 07:04, 18 December 2022 (UTC)
- That's...not at all what I said. I was looking up that date's TFA title, then passing that wikitext to the API to load page history so I could easily look at diffs. Anyways, there seems to be a fundamental disconnect in understanding how the templates are supposed to be used. Legoktm (talk) 07:15, 18 December 2022 (UTC)
- @Legoktm I am not convinced that its usage in such a report necessitated urgent mass rollback, but thanks for giving an example of what could have been broken, something Anomie was too lazy to provide. Since this is not how most templates are used, it would be helpful to note that in the template doc, which only mentions that it can be substed. I think that if adding a noincluded category break a tool, it should ideally be fixed on the tool side, but that's a discussion for another place. I am okay with closing this discussion. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 13:33, 18 December 2022 (UTC)
- I run the bot that has put this data into the wiki in a particular format, for over 12 years now. There's no reason I should have to know what specifically makes use of the data to know that suddenly changing that format is likely to break some of them. But if it makes you feel better to cast aspersions like "lazy", I'll try to forgive it. Anomie⚔ 15:39, 18 December 2022 (UTC)
- @Legoktm I am not convinced that its usage in such a report necessitated urgent mass rollback, but thanks for giving an example of what could have been broken, something Anomie was too lazy to provide. Since this is not how most templates are used, it would be helpful to note that in the template doc, which only mentions that it can be substed. I think that if adding a noincluded category break a tool, it should ideally be fixed on the tool side, but that's a discussion for another place. I am okay with closing this discussion. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 13:33, 18 December 2022 (UTC)
- That's...not at all what I said. I was looking up that date's TFA title, then passing that wikitext to the API to load page history so I could easily look at diffs. Anyways, there seems to be a fundamental disconnect in understanding how the templates are supposed to be used. Legoktm (talk) 07:15, 18 December 2022 (UTC)
- Yes, a block threat is appropriate when you actually intend to go through with it. Intending to go through with a block, however, is not appropriate at the beginning of a conversation. One shouldn't start a conversation by talking about blocks because that's aggressive and likely to prompt a defensive reaction rather than a cooperative one. "Don't go in hot and heavy," as the saying goes. Levivich (talk) 02:13, 18 December 2022 (UTC)
- Obviously, a better sequence of events is: (1) ask the person politely and non-threateningly to stop, (2) only proceed to threaten if they refuse. 100.36.106.199 (talk) 02:11, 18 December 2022 (UTC)
- At the risk of discussing too much of a hypothetical, is a block threat not appropriate if you actually intend to go through with it (should the disruption continue)? Compared to not issuing the threat, and then blocking, then getting complaints that you didn't properly warn them that a block was a possibility. Legoktm (talk) 01:38, 18 December 2022 (UTC)
- A block threat is a lousy way to start a discussion, even if -- and I want to be absolutely clear here -- even if the other person did something blockable. I'm stunned that you or anyone else would have trouble with this rather simple concept. Don't start a conversation with a block threat, duh. Levivich (talk) 01:24, 18 December 2022 (UTC)
- None of what you've written is about the response. Levivich (talk) 00:15, 18 December 2022 (UTC)
- You may want to read that again, as you seem to have completely misinterpreted Special:Diff/1127670633. The block warning was clearly in reference to the apparent running of an unauthorized bot, per WP:Bot policy which states
- @Legoktm does TFA protector bot use past templates? All I have edited so far was from before 2016. Even you are saying "there are probably other tools out there" but don't know which one actually broke, yet it was rollback worthy!? ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 18:51, 17 December 2022 (UTC)
- @ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ: the automated routines don't, I was recently using old templates for the purposes of putting together this report. Anyways, like I said above, if you think they're unused, just nominate them for deletion instead of breaking them. Legoktm (talk) 00:13, 18 December 2022 (UTC)
- @Legoktm: The edit notice seems like a good idea to me, although Template:Bot use warning didn't seem quite right so I wrote a custom message. If anyone wants to discuss the wording, let's do that elsewhere. Anomie⚔ 19:45, 17 December 2022 (UTC)
- Whether categories are desired for these pages or not, adding them shouldn't break bots. If a bot is incompatible with categories being added to a page, I'd say the bot needs to be fixed. We shouldn't be blaming users for not behaving in the way bots expect them to do. ~ ToBeFree (talk) 18:18, 17 December 2022 (UTC)
Mass rev/delete script?
editIs there a script that will do a mass rev/delete of a user's contributions? Sort of like the mass delete script that will delete pages created by a user?--Bbb23 (talk) 18:17, 18 December 2022 (UTC)
- User:Writ Keeper/Scripts/massRevdel.js should do what you're looking for. There's also my fork of that script, which removes the suppression-related functionality but is otherwise identical. --Blablubbs (talk) 18:51, 18 December 2022 (UTC)
- I used yours, and after futzing with it a bit in my usual I-don't-know-what-I'm-doing way when it comes to scripts, it seems to have worked. Thanks!--Bbb23 (talk) 19:47, 18 December 2022 (UTC)
"I am Carla Payne - Wikipedia Moderator"
editI received an email stating:
I am Carla Payne - Wikipedia Moderator. I am based in San Francisco and provide my clients with Wikipedia creation and management services. In addition to that, I provide my services to some renowned personalities and companies.
I am a consultant for MediaWiki, and I understand the Wikipedia system and its workings. In addition, I am familiar with Wikipedia page approvals and ensure it will remain live.
All my clients are delighted with my services. So let's shake hands together to build and manage your wiki profile. Click here and submit the form, and then we can discuss it further.
Thanks,
Carla Payne
Wikipedia Moderator[Address redacted]
Obviously not legit, but how far down the rabbit hole should I chase this? I am particularly interested in their claim to be a "a consultant for MediaWiki". BD2412 T 18:41, 18 December 2022 (UTC)
- Sounds like the pitch was written by ChatGPT. In the past, folks have tried sleuthing these editors out - by playing along, asking them for article references, etc., but they’re just as likely to misrepresent their work as they are their credentials. –xenotalk 19:20, 18 December 2022 (UTC)
- I suppose clicking that link is just an invitation to get more spam emails anyway. BD2412 T 12:37, 19 December 2022 (UTC)
Racial bias (User:Ravenswing)
editNo administrative action required here. Let's keep it that way. The Blade of the Northern Lights (話して下さい) 17:05, 19 December 2022 (UTC) |
---|
The following discussion has been closed. Please do not modify it. |
Dear admins, I asked a question here that "Am I still topic banned?" During the discussion, User:Ravenswing said that Quote: "I expect we'll manage. What would genuinely "hurt the trust of users" would be to have policies we did not enforce. Editors are just as bound by Wikipedia's policies and rules as visitors to your own country are bound by those laws, however strange they may be to foreigners. (I don't expect, for example, that your country would waive its blasphemy laws for my benefit, however much the criminalization of blasphemy is a strange and deplorable concept to Americans.)"UQUOTE. It mirrors racial and national bias on Wikipedia. This user's comment is to make Pakistanis Muslims, appear as extremists, which is directly against fundamental human rights and religious freedom. Is this Wikipedia policy? I request Admins to take action against the user.Arif80s (talk) 05:09, 19 December 2022 (UTC)
|
Iranian Politics disruption continues
editThe Arbitration Committee has been made aware by the Wikimedia Foundation's disinformation team of continued disruption in the Iranian Politics (IRANPOL) topic area, which was subject to an ArbCom case last year. Additional measures to address this disruption may be forthcoming in the year ahead from the Arbitration Committee and/or the Wikimedia Foundation. For now, the Arbitration Committee is informing the community of this disruption in the hopes that more editors and administrators may wish to begin working in the IRANPOL topic area. Uninvolved administrators are also reminded that editor restrictions and page restrictions are available for use in the topic area. For the Arbitration Committee, Barkeep49 (talk) 17:15, 19 December 2022 (UTC)
A user keeps to undo my edits with no further explanations
editI really didn't wanted to come to this, I left a message on their talk section, but since they deleted it, I had no choice but to report.
User:WikiMaster2K15 keeps undoing my edits. For example, I edited the World of Stardom Championship, where I made equal space before any = sign to make it more comfortable for the editor to read, but they removed those spaces even when I explained why I'm asking not to remove. I also seen another user complained sbout it to them on their talk page at November.
Also, I use the sortname template on any championship reign section so it would able to organize it alphabetically, you can see the same on List of WWE Champions, but they removed it as well.
I do not asking for that user to be banned or removed, but I tried to voiced my frustration about this which they ignored. User talk:SeosiWrestling 03:38, 18 December 2022 (UTC)
- This doesn't appear to be the first time this user has removed spaces, been asked why by other users, and instead of responding they deleted the comments (and warning templates) from their talk page [104]. WikiMaster2K15 also consistently fails to use edit summaries, arguably uncivilly. ZsinjTalk 22:03, 18 December 2022 (UTC)
- Although WikiMaster2K15 has inappropriately removed spaces in the past, in the case of World of Stardom Championship SeosiWrestling is inappropriately adding spaces. As per WP:STYLEVAR don't add them to articles without spaces, and don't remove them from articles with spaces. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 15:47, 19 December 2022 (UTC)
- @ActivelyDisinterested How is that inappropriate? It's really uncomfortable to read them without spaces, otherwise it's very compressed and uneasy to the eye. SeosiWrestling (talk) 16:24, 19 December 2022 (UTC)
- Only in your opinion, it's not one that is held universally. The point of WP:STYLEVAR, and similarly WP:CITEVAR, is that there is no set way these things should be done. Arguing or edit warring over them only wastes community time. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 17:31, 19 December 2022 (UTC)
- @SeosiWrestling, take a look at Wikipedia:Cosmetic edit. That page is about terms primarily used for bots, but the principle is the same for human editors: edits solely to change wikitext rather than displayed text are minor edits of little value. It even calls out adding spaces on each side of = as unacceptable. Schazjmd (talk) 17:44, 19 December 2022 (UTC)
- So, if I'm marking it as an minor edit, would that be okay? SeosiWrestling (talk) 18:36, 19 December 2022 (UTC)
- @SeosiWrestling, you kind of overlooked the "of little value" and "unacceptable" parts there... Please note the comment by ActivelyDisinterestsed above:
don't add them to articles without spaces, and don't remove them from articles with spaces
Schazjmd (talk) 18:42, 19 December 2022 (UTC)- Understood. I mean, it's messing up my OCD, but I get it. With that being said, that person also deleted wrestlers on the reigns lists as I wrote them in Template:Sortname, therfore, they could be organized alphabetically afterwards. SeosiWrestling (talk) 19:24, 19 December 2022 (UTC)
- @SeosiWrestling, you kind of overlooked the "of little value" and "unacceptable" parts there... Please note the comment by ActivelyDisinterestsed above:
- So, if I'm marking it as an minor edit, would that be okay? SeosiWrestling (talk) 18:36, 19 December 2022 (UTC)
- @ActivelyDisinterested How is that inappropriate? It's really uncomfortable to read them without spaces, otherwise it's very compressed and uneasy to the eye. SeosiWrestling (talk) 16:24, 19 December 2022 (UTC)
- Although WikiMaster2K15 has inappropriately removed spaces in the past, in the case of World of Stardom Championship SeosiWrestling is inappropriately adding spaces. As per WP:STYLEVAR don't add them to articles without spaces, and don't remove them from articles with spaces. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 15:47, 19 December 2022 (UTC)
- P-blocked from article space for refusal to communicate. Literally does not appear to have ever posted to a talk page. The only edits they've made to their own talk appear to be to remove complaints from others. They just removed SPhilbrick's request on their talk for an explanation. No objection to anyone lifting this p-block once the editor communicates. Valereee (talk) 18:54, 19 December 2022 (UTC)
- Comment Not just removing spaces but WikiMaster2K15 also replaces and with ampersand; examples [105][106][107][108][109][110]. I guess WikiMaster2K15 is not familiar with MOS and how Wiki software/source works. Or per his edit summaries, WikiMaster2K15 just prefers and pov-pushes his desired style; ignoring both WP guidelines and other users' concerns. --Mann Mann (talk) 09:33, 20 December 2022 (UTC)
Retired editor SchroCat
editThe following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
SchroCat (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Sorry to bring this to light, but the editor in question just refuses to stop WP:ASPERSIONS against multiple users. This is a little confusing because SchroCat is a retired editor who is using multiple IPs to edit.
- SchroCat accused of Shibbolethink of stalking[111] and being unethical[112]. Even after Shibbolethink attempted to clarify the dispute in a GF manner SchroCat against made an accusation and went further by calling it gaslighting and disgusting.[113]
- At this stage I contacted Shibbolethink via TALK to warn them that SchroCat was a hostile editor. SchroCat was less than friendly towards me in the past, but I just let it go and moved on.
- This seemed to move things along, but a few days later SchroCat accused Shibbolethink of edit warring. [114] Then SchroCat went to InvadingInvader’s TALK and made accusations against myself, InvadingInvader, and EnPassant.[115] Again, I attempted to steer the editor away, but everything becomes a WP:BATTLEGROUND it seems.
Generally I would just this behavior go and move on, but this editor's actions on several articles are watching at the present is becoming an unnecessary distraction. Based on the editor's history this isn't the first time this type of behavior has been a problem. In light of the editor not listening to advice in GF I bring it here hoping that brings it to an end. Thanks! Nemov (talk) 21:14, 10 December 2022 (UTC)
- Either an editor has retired or hasn't, it can't be both. If SchroCat is behind the IPs? I wish he'd would stop continuing 'signed out' & officially un-retire. GoodDay (talk) 21:36, 10 December 2022 (UTC)
- No, User:GoodDay, you are mistaken. The editor cannot be determined to be in a retired or non-retired state, like the cat whose living or non-living state is indeterminate. Robert McClenon (talk) 01:43, 11 December 2022 (UTC)
- Sorry, I probably should have linked to where the user said they were SchroCat, but the identity wasn't in dispute. For example, the IP removed the notice from SchroCat's TALK. Nemov (talk) 21:40, 10 December 2022 (UTC)
- Yeah, the editor signs their comments as "The editor formally known as Schrocat and now editing under IPs" or something similar. — Shibbolethink (♔ ♕) 01:02, 11 December 2022 (UTC)
- Comments:
- 1. I'm not an expert in policy, but I'm getting a feeling that this could constitute as some form of sockpuppetry. I won't further entertain the feeling unless there is solid proof.
- 2. I would fully support the initial comment as a neutral testament of what happened.
- 3. To respond to GoodDay's initial comment, during an ongoing discussion on whether to include an infobox on Mackenzie Ziegler's article, the IP 2A00:23C7:2B86:9801:EC7C:7CCE:D2B2:CF59 opposed the idea and listed them as formerly being known as SchroCat. That's when Nemov first alerted me to SchroCat's history and the Infobox debate, and upon our discussion about the past, the IP 2A00:23C7:2B86:9801:F9F0:EEDB:4180:806C started accusing us of personal attacks left, right, and center. Based on their responses, though no verbatim admission has come from the latter IP, I have reason to believe that both IPs are SchroCat. InvadingInvader (userpage, talk) 21:37, 10 December 2022 (UTC)
- Could you provide the diffs of where I have “accused you of personal attacks left, right, and center”? 2A00:23C7:2B86:9801:65FE:FE8:B65C:3BC4 (talk) 21:54, 10 December 2022 (UTC)
- I've contacted SchroCat & asked him to either un-retire or stop continuing forward signed-out, if he's behind the IPs. We should also take caution, that it's not someone else claiming to be SchroCat, just to get him banned. GoodDay (talk) 21:43, 10 December 2022 (UTC)
- I neither need to un-retire, nor wish to. 2A00:23C7:2B86:9801:65FE:FE8:B65C:3BC4 (talk) 21:54, 10 December 2022 (UTC)
- If that's your attitude? then you're on your own. If you end up site-banned? so be it. GoodDay (talk) 22:02, 10 December 2022 (UTC)
- My attitude? As far as I am aware, that’s long-standing practice, given there are no policies or guidelines that say the opposite. I pop back in from time to time, which is acceptable, rather than “an attitude”. Cheers 2A00:23C7:2B86:9801:302F:5717:579F:6EE8 (talk) 22:10, 10 December 2022 (UTC)
- If that's your attitude? then you're on your own. If you end up site-banned? so be it. GoodDay (talk) 22:02, 10 December 2022 (UTC)
- I neither need to un-retire, nor wish to. 2A00:23C7:2B86:9801:65FE:FE8:B65C:3BC4 (talk) 21:54, 10 December 2022 (UTC)
- Yes, I said Shibbolethink was disgraceful. I stand by that. You don’t infer editors are delusional. For someone who purports to be a medical professional, that is a disgraceful statement to make.
- He called me delusional because I said he had stalked me between articles and harassed me by removing or moving my comments. He has:
- The stalking began after he claimed sources saying Rylance should be described as British American. (He shouldn't be – the sources even come close to backing that up). He stonewalled on the talk page, so an RfC is in progress. Since then, he has appeared after me at the following articles (some are obviously natural links, others are definitely not).
- List of awards and nominations received by Mark Rylance
- James Joyce
- Pyotr Ilyich Tchaikovsky
- Claude Debussy
- Moorgate Tube Crash
- Laurence Olivier
- The Shoes of the Fisherman (film) (I hadn't edited the article, but I had altered the link in the Olivier article)
- I have also received a series of posts on my talk page from him including veiled accusations. This was the one message he has dropped into the middle of the RFC, which is more than a little inappropriate. I am unable to leave a message on his talk page about this as it is semi-protected. He has also moved part of one of my comments (https://en.wikipedia.org/w/index.php?title=Talk:Laurence_Olivier&diff=1125987334&oldid=1125922063)? I reverted (https://en.wikipedia.org/w/index.php?title=Talk:Laurence_Olivier&diff=1126045730&oldid=1125987334) pointing out it was an answer to his previous comment, but he again moved it (https://en.wikipedia.org/w/index.php?title=Talk:Laurence_Olivier&diff=1126112389&oldid=1126078039). As to the comments on InvadingInvader‘s talk page. I have pointed out that they are hardly in good faith, and one of the accusations (from EnPassant, was untrue. 2A00:23C7:2B86:9801:65FE:FE8:B65C:3BC4 (talk) 21:54, 10 December 2022 (UTC)
- Every one of those talk pages has either an entirely benign reason, or my participation is completely unrelated to "stalking/HOUNDING", or otherwise unconnected to this user:
point by point rebuttal to accusation of HOUNDING
|
---|
|
- So how exactly would any of the above constitute WP:HOUNDING? Should I never edit articles the editor has ever touched? That would be a de facto SchroCat TBAN, something I would not be in favor of. I have no interest in interacting with or avoiding this user. I have no interest in checking each and every article for whether this /64 range has ever edited (especially since they occasionally edit with other ranges, how would I even know?) I have no interest in interacting with this user whenever possible, they have made doing so an extremely unpleasant experience. I care very little about the content of these disputes. I am happy to go with consensus in each and every case, and have said as much repeatedly.In response to any attempt to create consensus via compromise, or follow BRD, I have been met with numerous WP:ASPERSIONS and bad faith accusations:
Examples of this user violating talk page guidelines
|
---|
|
- I neglected to say above, as SchroCat and as other IPs, they have been blocked a total of FIVE (maybe six?) times for creating a battleground, for edit warring (on ArbCom of all places, with arbs!), and for sock-puppetry: [131] [132]. For many of the same behaviors I describe above.
- Add to this: the explicit WP:OWN behavior (this user is a filter placed upon every article they have ever edited, in which they will create controversy and edit war over minute changes such as adding spouses to an infobox), the WP:BATTLEGROUNDs they create (everyone is with them or against them, a friendly editor whose actions they like, or someone who harasses them). And so on.
- I am happy to provide diffs showing any of the above.
- As far as I can tell, this user edits on anonymous IPs partially because of their previous block log and history. Not to mention the ArbCom restriction that they must declare themselves when asked by Arbs. If anything, their behavior has become more brazenly standoffish since going full anon IP. And it's taken longer for admins to catch up with their many addresses given that behavior is stretched across different IPs (block evasion): [133] [134]. Why is this something the project is tolerating, given the past disruption? What does this user, in their current state and behavior, contribute to the project? — Shibbolethink (♔ ♕) 01:42, 11 December 2022 (UTC)
- This user has contributed a large body of very well written articles on interesting topics. These articles continue to have new readers which constitutes an ongoing contribution to the project. Mr Ernie (talk) 16:07, 12 December 2022 (UTC)
- Yep, and I commend them for those efforts and contributions. But that does not outweigh the sheer number of personal attacks and edit wars, the overall WP:OWN behavior, and general pattern of BATTLEGROUNDing, OWNership, and lack of collaboration from this editor. I encourage you to find an instance when this editor was able to collaborate with someone they disagreed with about a fundamental "preference" disagreement. I could not find a single one. — Shibbolethink (♔ ♕) 16:10, 12 December 2022 (UTC)
- This user has contributed a large body of very well written articles on interesting topics. These articles continue to have new readers which constitutes an ongoing contribution to the project. Mr Ernie (talk) 16:07, 12 December 2022 (UTC)
- I'm not sure there is anything further that admins can do about this. I can think of no sanction more severe than being condemned to spend your free time arguing against infoboxes as an IP editor. Levivich (talk) 22:35, 10 December 2022 (UTC)
- I don’t just to that. I occasionally make sure standards are kept on sourcing and that sources are no misrepresented while someone tries to crowbar petty nationalism onto an article. Then I get bored and go away do something useful with my life for a couple of months. - 86.162.16.154 (talk) 22:42, 10 December 2022 (UTC)
- Levivich. From this time onward, whoever the IPs (mobile or computer) are, they'll likely not be trusted again, going forward. GoodDay (talk) 22:52, 10 December 2022 (UTC)
- Assuming arguendo that the IPs are actually SchroCat, this is a fairly textbook example of evading scrutiny, given SchroCat's history in this area. If you're retired, retire, or scratch the Wikipedia itch in such a way that you're not noticed. If you're not retired, please log into your account so editors understand who they're working with. You can't have it both ways.
- If it's not SchroCat, arguing about infoboxes is a privilege (punishment?) that really ought to be reserved to logged-in editors. Mackensen (talk) 22:58, 10 December 2022 (UTC)
- Evading scrutiny? I signed my !votes using my name, so there is no evasion. I cannot log back in: my password was scrambled a couple of years ago and I have no wish to return to full time editing, just drop in. And no, discussions over things like IBs is for all users, registered and unregistered. 2A00:23C7:2B86:9801:6562:A1FC:F7F2:51BF (talk) 23:02, 10 December 2022 (UTC)
- There's still an email address associated with your account, which generally means the account is recoverable. You could also register a new account under a new name. Editing as a logged-out IP when your IP changes frequently (not your fault, but it's a fact) makes more work for the editors trying to work with you. You need to make a choice here. Mackensen (talk) 23:21, 10 December 2022 (UTC)
- I've made my choice, thanks. I will continue to return as an IP editor when I feel like editing. If there is a policy or guideline against that, please show it me and I'll adhere to it. If there isn't, then I will continue to edit as an IP, signing my old user name when appropriate. 2A00:23C7:2B86:9801:6562:A1FC:F7F2:51BF (talk) 23:28, 10 December 2022 (UTC)
- WP:LOUTSOCK? As everyone else has said: you can't retire and then continue to edit actively, especially not logged out in a way that people could be deceived into thinking you don't have an account. (Non-administrator comment) casualdejekyll 23:36, 10 December 2022 (UTC)
- Just as WP:NOTHERE admits more than one reading, so too does WP:LOUTSOCK. Just sayin'. EEng 05:47, 11 December 2022 (UTC)
- Loutsock? I don't edit under my old name, so Loutsock can't apply (my last edit as SchroCat was September 2020). As I have already said, when I occasionally return, and where appropriate (!votes in contentious areas, etc), I sign saying what my former account was so as not to be accused of evasion. 2A00:23C7:2B86:9801:6562:A1FC:F7F2:51BF (talk) 23:43, 10 December 2022 (UTC)
- One thing I'd like to note about WP:LOUTSOCK and whether or not this user will be an issue for the project moving forward: If this IS SchroCat, they have tried to have a (albeit hidden) WP:CLEANSTART at least twice [135] [136] and got a CU-block both times, as a result of their behavior. They have also tried to be vanished at least once, and had it reversed due to their behavior. [137]I would say it is absurd for the community to not see this logged out editing as yet another way to have their behavior less scrutinized. SchroCat seems to want their cake and to eat it too, to be anonymous, but also able to cite their "long history of FAs and GAs" as experience AND ALSO avoid the baggage of their many prior blocks and their current editing restriction. — Shibbolethink (♔ ♕) 14:12, 11 December 2022 (UTC)
- WP:LOUTSOCK? As everyone else has said: you can't retire and then continue to edit actively, especially not logged out in a way that people could be deceived into thinking you don't have an account. (Non-administrator comment) casualdejekyll 23:36, 10 December 2022 (UTC)
- I've made my choice, thanks. I will continue to return as an IP editor when I feel like editing. If there is a policy or guideline against that, please show it me and I'll adhere to it. If there isn't, then I will continue to edit as an IP, signing my old user name when appropriate. 2A00:23C7:2B86:9801:6562:A1FC:F7F2:51BF (talk) 23:28, 10 December 2022 (UTC)
- There's still an email address associated with your account, which generally means the account is recoverable. You could also register a new account under a new name. Editing as a logged-out IP when your IP changes frequently (not your fault, but it's a fact) makes more work for the editors trying to work with you. You need to make a choice here. Mackensen (talk) 23:21, 10 December 2022 (UTC)
- Evading scrutiny? I signed my !votes using my name, so there is no evasion. I cannot log back in: my password was scrambled a couple of years ago and I have no wish to return to full time editing, just drop in. And no, discussions over things like IBs is for all users, registered and unregistered. 2A00:23C7:2B86:9801:6562:A1FC:F7F2:51BF (talk) 23:02, 10 December 2022 (UTC)
- lmao Xx78900 (talk) 13:44, 13 December 2022 (UTC)
Would it be appropriate for a checkuser to comment on whether the IP editor may be SchroCat? (possibly not, as checkusers are usually loath to link an IP to an account for a range of good reasons concerning privacy). Nick-D (talk) 01:08, 11 December 2022 (UTC)
- There wouldn't even be any way to tell. The logs are purged every few months. NinjaRobotPirate (talk) 01:31, 11 December 2022 (UTC)
- We can infer certain traits from the CU log from past checks of the named account. We do normally avoid linking a named account to an IP, but SchroCat has self-disclosed right here, so he's waived the privacy to which he would otherwise be entitled. Because of this self-disclosure, I don't think it's necessary right now to run a check. I also don't think his motives are malicious, but if the community believes this to be disruptive, we can handle it through normal admin actions. Katietalk 02:06, 11 December 2022 (UTC)
- How do we know these IPs are the same person and that person is SchroCat? Also he was party to an AE or ARCA or something about infoboxes when he retired, so, there's that. Ritchie333, didn't you deal with this already once before? Levivich (talk) 02:44, 11 December 2022 (UTC)
- According to this, the only logged editing restriction I could find, "SchroCat is required to disclose any future alternative accounts either publicly or privately to the Arbitration Committee." Question is, are the IPs the person who now claims to be SchroCat is using "accounts" under this restriction, and have they been reporting them to ArbCom as required? The other possible concern is when SchroCat (if this is SchroCat) doesn't identify themselves as an IP, is that "avoiding scrutiny" of their editing per WP:SOCKPUPPETRY? Beyond My Ken (talk) 03:21, 11 December 2022 (UTC)
- Thanks, I didn't know about that. This ARCA is what I remembered. Levivich (talk) 04:28, 11 December 2022 (UTC)
- According to this, the only logged editing restriction I could find, "SchroCat is required to disclose any future alternative accounts either publicly or privately to the Arbitration Committee." Question is, are the IPs the person who now claims to be SchroCat is using "accounts" under this restriction, and have they been reporting them to ArbCom as required? The other possible concern is when SchroCat (if this is SchroCat) doesn't identify themselves as an IP, is that "avoiding scrutiny" of their editing per WP:SOCKPUPPETRY? Beyond My Ken (talk) 03:21, 11 December 2022 (UTC)
- How do we know these IPs are the same person and that person is SchroCat? Also he was party to an AE or ARCA or something about infoboxes when he retired, so, there's that. Ritchie333, didn't you deal with this already once before? Levivich (talk) 02:44, 11 December 2022 (UTC)
- We can infer certain traits from the CU log from past checks of the named account. We do normally avoid linking a named account to an IP, but SchroCat has self-disclosed right here, so he's waived the privacy to which he would otherwise be entitled. Because of this self-disclosure, I don't think it's necessary right now to run a check. I also don't think his motives are malicious, but if the community believes this to be disruptive, we can handle it through normal admin actions. Katietalk 02:06, 11 December 2022 (UTC)
- While the random IPs in multiple discussions are confusing, the real issue is the consistent behavior towards other editors. This has been a problem in the past and now is continuing post-retirement. I don't have objections to the editor leaving comments on articles as an IP editor, it's the comments towards other editors which need to stop. Nemov (talk) 02:33, 11 December 2022 (UTC)
- User:Gerda Arendt asked the candidates for ArbCom whether we still have infobox wars. Maybe the answer is that, due to quantum entanglement, we may or may not have infobox wars with an editor who may or may not be active. Robert McClenon (talk) 03:09, 11 December 2022 (UTC)
- As my name was mentioned: today is the last day to vote. There have been few discussions about infoboxes over 2021 and 2022. When I saw Laurence Olivier, however, I sadly noticed that the topic is still not at peace. After I asked in my survey, we had even more such discussions. - I don't understand the problem, because I strongly believe that a lead and an infobox can coexist in an article, serving different types of readers, - why was that ever a reason to fight? - I asked the arb candidates about ideas for peace, and they offered none. My simple approach: 1) every editor please stick to two comments per discussion. (Can anybody count how many comments the various IPs named SchroCat made in Laurence Olivier alone? On top of edit-warring over the new infobox.) 2) treat infoboxes just like other editing, in civility and respecting WP:BRD. Better ideas, anybody? --Gerda Arendt (talk) 09:43, 12 December 2022 (UTC)
- @Gerda:, don't worry too much about Infoboxes; that's only tangential to this topic. This thread is not about that, but about a possible community ban of an editor. You're welcome to opine in the #Survey section above, if you wish to. Mathglot (talk) 09:47, 12 December 2022 (UTC)
- Fix ping: @Gerda Arendt:. Mathglot (talk) 09:49, 12 December 2022 (UTC)
- I thought I opined clearly enough, but if not:
- I don't worry about infoboxes (at all). They come, and they come without me, I don't have to worry.
- It is SchroCat who worries too much about infoboxes, getting into trouble again and again over only this topic, instead of just accepting community consensus.
- I do not support banning a valuable content editor, when a topic ban or a two-comments-per-discussion restriction (best for all participants) would be enough to stop disruption.
- As expressed before, multiple times, I'd prefer if SchroCat would edit under the user name. --Gerda Arendt (talk) 11:15, 12 December 2022 (UTC)
- Gerda, your two posts preceding this one are disingenuous and a very selective reading of the origin of WP:BLUDGEONING in infobox discussions. Perhaps the reason this thread has not boomeranged on those editors is that other editors don't want to engage their behaviors, as they should land those editors in arb enforcement. And I'm not referring to SchroCat. SandyGeorgia (Talk) 14:50, 12 December 2022 (UTC)
- I thought I opined clearly enough, but if not:
- As my name was mentioned: today is the last day to vote. There have been few discussions about infoboxes over 2021 and 2022. When I saw Laurence Olivier, however, I sadly noticed that the topic is still not at peace. After I asked in my survey, we had even more such discussions. - I don't understand the problem, because I strongly believe that a lead and an infobox can coexist in an article, serving different types of readers, - why was that ever a reason to fight? - I asked the arb candidates about ideas for peace, and they offered none. My simple approach: 1) every editor please stick to two comments per discussion. (Can anybody count how many comments the various IPs named SchroCat made in Laurence Olivier alone? On top of edit-warring over the new infobox.) 2) treat infoboxes just like other editing, in civility and respecting WP:BRD. Better ideas, anybody? --Gerda Arendt (talk) 09:43, 12 December 2022 (UTC)
- User:Gerda Arendt asked the candidates for ArbCom whether we still have infobox wars. Maybe the answer is that, due to quantum entanglement, we may or may not have infobox wars with an editor who may or may not be active. Robert McClenon (talk) 03:09, 11 December 2022 (UTC)
- The people who oppose infoboxes are good content creators, not drive-by disruptors. Let them have their say without bitter argument. If the IP bothers you, ignore them. You don't have to counter everything the IP says. If you respond to them, they are entitled to reply. Post on this noticeboard if the IP is a problem after people stop arguing with them and stop fiddling with their comments. An editor can stop using their account and later post as an IP if they want—nothing nefarious is going on. Johnuniq (talk) 04:36, 11 December 2022 (UTC)
- This has zero to do with infoboxes. I can't be clearer about that. This is about a single editor who continues to accuse others repeatedly after being asked to stop. That is a problem. Accusing others of stalking, harassment, and lying isn't a simple content dispute. When an editor has been blocked for this behavior in the past and refuses to stop what other recourse is there? Nemov (talk) 05:11, 11 December 2022 (UTC)
- Pay no mind to the old he-wouldn't-be-such-a-jerk-if-people-didn't-bother-him-so-much defense. Frankly I'm surprised it took 12 hours to appear in this thread. Levivich (talk) 05:47, 11 December 2022 (UTC)
- It's a little troublesome that some editors seem unconcerned about this issue. This is a clear case of an edtior accusing others of lying, harassment, stalking, and gaslighting. WP:ASPERSIONS is very clear on this subject.
It is unacceptable for an editor to routinely accuse others of misbehavior without reasonable cause.
This is the routine for SchroCat. Nemov (talk) 15:28, 11 December 2022 (UTC)
- It's a little troublesome that some editors seem unconcerned about this issue. This is a clear case of an edtior accusing others of lying, harassment, stalking, and gaslighting. WP:ASPERSIONS is very clear on this subject.
- Pay no mind to the old he-wouldn't-be-such-a-jerk-if-people-didn't-bother-him-so-much defense. Frankly I'm surprised it took 12 hours to appear in this thread. Levivich (talk) 05:47, 11 December 2022 (UTC)
- This has zero to do with infoboxes. I can't be clearer about that. This is about a single editor who continues to accuse others repeatedly after being asked to stop. That is a problem. Accusing others of stalking, harassment, and lying isn't a simple content dispute. When an editor has been blocked for this behavior in the past and refuses to stop what other recourse is there? Nemov (talk) 05:11, 11 December 2022 (UTC)
- Don't think there's anything to do here. Yep, this is obnoxious; nope, doesn't seem to be against any of our policies (although we do need to verify when an IP claims to be a registered user; just saying "hey it's me" isn't sufficient). Requiring SchroCat return to their account won't actually solve anything. If his behavior becomes abusive, the next step is proposing an indef here, but there would need to be a lot more (and more egregious) evidence for that. History also tells us that proposals to sanction someone are least productive when filed by someone at the other end of an infobox battle, for better or worse. FWIW. — Rhododendrites talk \\ 14:14, 11 December 2022 (UTC)
- The current situation isn't great. SchroCat's user page says he's retired. His talk page was protected yesterday. An IP who is probably SchroCat, given his conduct, is signing himself as such but his IP keeps changing. This mode of editing has and will continue to cause confusion and create friction, even leaving aside that SchroCat's conduct toward other editors hasn't improved over the years. I don't see why the project has to sign up for more of this; we do get a choice after all. Mackensen (talk) 15:59, 11 December 2022 (UTC)
Today multiple IPs have edited the Moorgate tube crash page, reverting grammar improvements, and then going on to my talk page (where at least one of them admitted to being SC) and the article's talk page. This includes:
- 2A00:23C7:2B86:9801:6562:A1FC:F7F2:51BF (talk · contribs · deleted contribs · logs · filter log · block user · block log) (diffs: 1, 2)
- 2A00:23C7:2B86:9801:1930:3AE6:7605:784 (talk · contribs · deleted contribs · logs · filter log · block user · block log) (diffs: 3, 4, 5)
- 2A00:23C7:2B86:9801:DD88:3C8D:2FF1:1800 (talk · contribs · deleted contribs · logs · filter log · block user · block log) (diffs: 5, 6)
- 2A00:23C7:2B86:9801:B4FF:A37A:49BB:D5B4 (talk · contribs · deleted contribs · logs · filter log · block user · block log) (diffs: 6, 7
Is it worth launching an SPI regarding this? Mattdaviesfsic (talk) 16:40, 11 December 2022 (UTC)
- @DisillusionedBitterAndKnackered: and @Shibbolethink: have also had interactions with one or more of these, whether it be on the main page or the talk page. On my talk page there were signs of WP:OWN as well. Troublesome and tiring. Mattdaviesfsic (talk) 16:45, 11 December 2022 (UTC)
- These IPs are all from a single dynamic /64 IPv6 range (the first four groups of numbers are the same), meaning it's all one device, presumably one person, who claims to be SchroCat. No need for SPI here. There are other concerns but this is normal for a dynamic IPv6. Levivich (talk) 16:50, 11 December 2022 (UTC)
- Basically this is just more and more evidence this IP range tries to WP:OWN articles edited by User:SchroCat. Even very small changes by multiple users are reverted with various antagonistic edit summaries
rv stalker
,Care to give a reason? I did when I made the edit: it’s consistent with the rest of the article and not needed. It’s also the version that was present since it was made an FAC until an IP added the needless commas a month ago.
. They appear to have improved their language a bit since the opening of this AN discussion, but the actual OWN behavior of any and all edits reverted through this person as a "filter" is still the same. — Shibbolethink (♔ ♕) 16:51, 11 December 2022 (UTC)- After Shibbolethink reported these edits to ANEW, I have blocked 2A00:23C7:2B86:9801:0:0:0:0/64 (talk · contribs · WHOIS) for 48 hours for violating 3RR over things like whether to join two sentences with a semicolon and whether "London Underground" takes an article or not. Just thought you'd like to know. Daniel Case (talk) 04:24, 12 December 2022 (UTC)
- That’s just not true. I reverted the parts of your edit that were not an improvement to an FA, that is all. That’s not ownership, that’s having standards. 2A00:23C7:2B86:9801:1930:3AE6:7605:784 (talk) 16:57, 11 December 2022 (UTC)
- Its a dynamic IP that my system changes. That’s not something I control.
- It’s a misnomer to describe the edits as “grammar improvements”. They weren’t, which is why they were partially reverted. I have given my explanation of why on the talk page.
- It is untrue to say there are signs on OWN, as I explained quite clearly. - 2A00:23C7:2B86:9801:1930:3AE6:7605:784 (talk) 16:47, 11 December 2022 (UTC)
- Your IP address really changes 4 times in one day, between ones you have already used a few hours or minutes earlier? Really? Mattdaviesfsic (talk) 16:50, 11 December 2022 (UTC)
- This is pretty common for IP6. But also, SchroCat, what you're doing is exactly what WP:OWN is about. 100.36.106.199 (talk) 16:53, 11 December 2022 (UTC)
- Nope. Removing problematic or sub-standard edits isn’t ownership. 2A00:23C7:2B86:9801:1930:3AE6:7605:784 (talk) 16:58, 11 December 2022 (UTC)
- Have a read of WP:OWNBEHAVIOUR and get back to us, see what you think. You did say on my talk it was a page you had taken through FA... Mattdaviesfsic (talk) 17:00, 11 December 2022 (UTC)
- As far as I can tell, the IP range exhibits every single one of those behaviors. The thing is, they just cite WP:FAOWN to justify it. And, to be fair, to WP:STEELMAN, FAOWN does say:
Editors are asked to take particular care when editing a Featured article; it is considerate to discuss significant changes of text or images on the talk page first. Explaining civilly why sources and policies support a particular version of a featured article does not necessarily constitute ownership
. But extremely importantly, the language in this policy is:- a suggestion for courtesy, not a mandate
- Described as for significant changes
- Asking those FA editors to
[Explain] civilly why sources and policies support a particular version
to avoid "ownership" behavior
- This IP range reverts and "filters" even extremely small changes that are all about user "preference", not about policy, sources, MOS, or actual FA criteria. They have cited none of these four things to justify reversions here (or honestly, elsewhere). They have only cited that they are restoring the "version that went through FA review" or similar. AKA their preferred version that they claim to have created. That's not FAOWN, that's OWN. — Shibbolethink (♔ ♕) 17:07, 11 December 2022 (UTC)
- "Significant" may not be apparent to editors unfamiliar with all the sources, and can often involve only one word that introduces subtle inaccuracy. SandyGeorgia (Talk) 15:02, 12 December 2022 (UTC)
- I don't think this particular defense applies to comma splices, semicolons, and whether "London Underground" needs a definite article. Although I agree it is often true. — Shibbolethink (♔ ♕) 16:23, 14 December 2022 (UTC)
- "Significant" may not be apparent to editors unfamiliar with all the sources, and can often involve only one word that introduces subtle inaccuracy. SandyGeorgia (Talk) 15:02, 12 December 2022 (UTC)
- As far as I can tell, the IP range exhibits every single one of those behaviors. The thing is, they just cite WP:FAOWN to justify it. And, to be fair, to WP:STEELMAN, FAOWN does say:
- Have a read of WP:OWNBEHAVIOUR and get back to us, see what you think. You did say on my talk it was a page you had taken through FA... Mattdaviesfsic (talk) 17:00, 11 December 2022 (UTC)
- Nope. Removing problematic or sub-standard edits isn’t ownership. 2A00:23C7:2B86:9801:1930:3AE6:7605:784 (talk) 16:58, 11 December 2022 (UTC)
- This is pretty common for IP6. But also, SchroCat, what you're doing is exactly what WP:OWN is about. 100.36.106.199 (talk) 16:53, 11 December 2022 (UTC)
- Your IP address really changes 4 times in one day, between ones you have already used a few hours or minutes earlier? Really? Mattdaviesfsic (talk) 16:50, 11 December 2022 (UTC)
- Here are all the contribs from the 2A00:23C7:2B86:9801::0/64 IPv6 range (I think). You can see the claim of "occasionally" editting is a lark: in fact, SchroCat (or an IP claiming to be him) has been editing almost every day on this range. The last 500 edits go back to September; 1000 to May, when this range made its first edits. Before that, it was likely a different range. There is also at least one IPv4 range here claiming to be SchroCat, 86.162.16.0/24, which has made edits like this one a week ago and this one a year and a half ago. There are probably more ranges. Anyway, if someone wants to make a proposal to block these ranges, I'd support it, for any number of reasons: impersonation (we have no idea if this is really SchroCat), edit warring, evasion, incivility, ownership, or my favorite reason: to stop this poor soul from spending any more of his life arguing against infoboxes. Levivich (talk) 17:29, 11 December 2022 (UTC)
- Brilliant, except a large number of these aren’t me. I’m spinning through the list and while many of them are mine, a significant proportion are not. - 2A00:23C7:2B86:9801:1930:3AE6:7605:784 (talk) 18:01, 11 December 2022 (UTC)
- Housekeeping comment: IP 2A00: please follow WP:THREAD for your replies; your 18:01 response belongs at the same level as my 17:38 comment below, and just below it, if you are replying, as did I, to Levivich's 17:29 comment above. Going forward, please observe standard reply protocols. Thanks, Mathglot (talk) 18:06, 11 December 2022 (UTC)
- Brilliant, except a large number of these aren’t me. I’m spinning through the list and while many of them are mine, a significant proportion are not. - 2A00:23C7:2B86:9801:1930:3AE6:7605:784 (talk) 18:01, 11 December 2022 (UTC)
- Impressive research, thanks! I'm worried that launching some sort of proposal might take months' worth of diffs and IP addresses, not to mention the vast swathes of editors involved at any level!! Mattdaviesfsic (talk) 17:34, 11 December 2022 (UTC)
- Eh, I'll do it. I'm clearly involved, but I will try and word it as neutrally as possible (and am happy to incorporate any and all constructive criticism). I think it can be done here as easily as at ANI, anyone correct me if I'm wrong. And if this needs to be moved to ANI, I would be fine with that as well. — Shibbolethink (♔ ♕) 17:36, 11 December 2022 (UTC)
- You can just add a section below for the proposal so it's attached to this discussion. I'd support that. Nemov (talk) 17:41, 11 December 2022 (UTC)
- In the process :) — Shibbolethink (♔ ♕) 17:41, 11 December 2022 (UTC)
- You can just add a section below for the proposal so it's attached to this discussion. I'd support that. Nemov (talk) 17:41, 11 December 2022 (UTC)
- Eh, I'll do it. I'm clearly involved, but I will try and word it as neutrally as possible (and am happy to incorporate any and all constructive criticism). I think it can be done here as easily as at ANI, anyone correct me if I'm wrong. And if this needs to be moved to ANI, I would be fine with that as well. — Shibbolethink (♔ ♕) 17:36, 11 December 2022 (UTC)
- (Non-administrator comment) (edit conflict) I'd support it, too. Mathglot (talk) 17:38, 11 December 2022 (UTC)
Proposal: CBAN the person behind these IP ranges (and User:SchroCat) from editing the English Wikipedia
edit(AKA CBAN the person formerly known as, or claiming to be, User:SchroCat)
- 2A00:23C7:2B86:9801::0/64 (talk · contribs · deleted contribs · page moves · block user · block log)
- 86.162.16.0/24 (talk · contribs · deleted contribs · page moves · block user · block log)
- SchroCat (talk · contribs · deleted contribs · page moves · block user · block log)
This person should be indefCBAN'd for the following reasons:
all the reasons
|
---|
|
I would overall summarize the above as:
- A user who has had many chances to reform their behavior, and has been blocked many times for this exact behavioral pattern, is now doing it from a set of IP ranges.
- Many editors have, in good faith, encouraged them to return to their account and stand behind their contributions, but they have refused. Others still have felt confused about who this editor is, and if this counts as sock-puppetry. In essence, in policy, it may not. But more important is the intent, and conduct, of the person behind these IP addresses. Examining even the content they stand behind, it does not paint a good picture.
- I would say we should take this user at their word, and entertain the idea that they are SchroCat, and judge them based on this. If the real SchroCat disagrees, they should speak up. They can return to their passworded account at any time with a simple password reset.
- If the real SchroCat would please stand up, please stand up...
- Let's collapse the waveform and open the box...
And stop wasting everyone's time from this user's continuous disruption. Happy to provide any and all diffs as requested. Thanks.— Shibbolethink (♔ ♕) 18:32, 11 December 2022 (UTC) (converted to a CBAN proposal 18:58, 11 December 2022 (UTC), trimmed slightly for length 00:02, 12 December 2022 (UTC), added diffs 16:57, 12 December 2022 (UTC))
Survey
edit- Don't know if it's appropriate here, but just wanted to add here my support for the WP:CBAN proposal. Other editors - @Nemov:, @GoodDay:, @Robert McClenon:, @InvadingInvader:, @Levivich:, @Mackensen:, @Casualdejekyll:, @Nick-D:, @KrakatoaKatie:, @Beyond My Ken:, @Johnuniq:, @Rhododendrites:, @DisillusionedBitterAndKnackered: - may wish to comment specifically on this here as well. If this is SchroCat, congratulations to him for wasting the time of 15+ editors. Mattdaviesfsic (talk) 18:45, 11 December 2022 (UTC)
Responses to previous proposal
|
---|
|
- Support a CBAN of SchroCat per the above megathread. LEPRICAVARK (talk) 19:00, 11 December 2022 (UTC)
- Support as proposer.— Shibbolethink (♔ ♕) 19:08, 11 December 2022 (UTC)
- Support CBan - Given that SchroCat is essentially giving the community the middle finger (and if they weren't aware of it before, they must be after the comments in this thread), and their past incivility and socking, I think this is the best solution for the community, with the previous proposals (IP blocks and/or SC editing restriction) as second choices. Beyond My Ken (talk) 19:10, 11 December 2022 (UTC)
- Ban for "disrupt[ing] progress toward improving an article [and] building the encyclopedia...extend[ing] over a long time on many articles", and per WP:DISRUPTSIGNS 1 and 5, and for WP:NOTGETTINGIT. Mathglot (talk) 19:12, 11 December 2022 (UTC)
- Support a CBAN. This editor does not appear to be temperamentally suited for a collaborative project. This has been an issue in the past and the behavior has continued now as an IP editor. I'm disappointed by a few of my fellow editors who have decided that unfounded accusations of harassment and stalking are just a perfectly normal part of Wikipedia as long as you've produced quality content. In this case, the editor in question has been banned for unproductive behavior in the past and has received several second chances. To allow this to continue is a disgrace that should not stand. This kind of interpretation of Wikipedia guidelines is a cancer that should be carved out quickly and without prejudice. Defending and ignoring this behavior turns its nose at editors who argue in good faith and it makes a mockery of the entire project. Hopefully the closing editor will do the right thing recongize the double standard defense for what it is... weak. Nemov (talk) 19:17, 11 December 2022 (UTC)
- Support a CBAN for all the reasons mentioned. Doc James (talk · contribs · email) 19:26, 11 December 2022 (UTC)
- Totally support a community ban, for all the reasons which have been raised. As for comments to the effect of "if it is SchroCat..." I have looked at enough of the editing history to leave no doubt about it. JBW (talk) 19:39, 11 December 2022 (UTC)
- Support with the echoing of "SchroCat is wasting everyone's time here". casualdejekyll 19:51, 11 December 2022 (UTC)
- Support - This isn't easy for me, as myself, SchroCat & Cassianto often agreed on opposing the over-usage of infoboxes in bios. However, I came around to accept that they're going to eventually be added to all bios. I wish SchroCat hadn't chosen this topic, as the hill to die on. But, he can't continue on in the manner that's been shown (signed in 'or' signed out) in these infobox discussions. GoodDay (talk) 20:03, 11 December 2022 (UTC)
- This is tough. There's a very small number of people (now mostly retired/banned or otherwise inactive) that feel their high quality articles entitle them to be however patronizing or abusive as they wish, and find in requests for basic respect a form of persecution. I absolutely do think we should afford long-time productive contributors a lot of leeway, and do think we need more people focused on writing high-quality articles than we do people focused on, well, most other activities. But this is ultimately a collaborative project, and I've seen SchroCat hurl enough abuse at people that there was a time I would've supported a ban. Then he sorta-kinda "retired" a couple years ago and things have been quieter.
On one hand, if someone avoided accountability because of their FAs, and they stop producing FAs, there's less motivation to leap(Struck after Tim pointed out he's continued to contribute along these lines) While this logged out petulance is tiresome, I'm not convinced there's justification for a CBAN in there. This proposal for a CBAN starts out with a long list of accusations, but that list has very few diffs. I want to see bannable diffs from the time since his retirement. I feel myself wanting to support, but I know that it's based more on a years-old perception than on anything recent, and I'm not comfortable taking such a drastic step without a recent smoking gun. Soweak opposeuntil more (and more egregious) recent diffs are provided. — Rhododendrites talk \\ 20:11, 11 December 2022 (UTC)
- Oppose - I've clicked through most of the diffs that have been added to this thread now (thanks for adding them). So let me be clearer: the arguments that SchroCat has, since "retiring", violated sufficient behavioral policies/guidelines to merit a cban are unconvincing. It seems like half of the people don't like the way he argues, but haven't provided sufficient evidence that we typically expect to cban a long-time editor, and half of people just want him to unretire. In the latter case, what are we really even doing here? Nobody has provided evidence that his IP activity even violates any policies, and the fact that several people would ignore the rest if only he unretired his main account shows how flimsy the evidence of behavioral problems are.
Look, I feel weird being in this column. Like I said, there have been times that I've been appalled by things SchroCat has said, but that was years ago now. I'm just not comfortable issuing the most extreme sanction we have at our disposal based on the evidence that has been presented. Upgrading "weak oppose" to "oppose" for that reason.
Side point: Can we please just say "all articles get infoboxes" already? I mean, I don't actually care much, and know it won't happen because Wikipedians don't like firm rules, but that's clearly the direction we're headed by strength of numbers if nothing else. Our PAGs don't give any real guidance about when to use them, ultimately coming down to personal preference, so RfCs are basically votes, and the votes are tending to favor inclusion these days. I'm still in favor of primary contributors to articles deciding whether or not there's an infobox, and I've never understood why so many people care so much about them that they're willing to disregard the opinions people who dedicated so much of their time to the subject, or why it's so triggering to so many of those major contributors, but oh well. It'd be nice if we could find some clearer rules is all. — Rhododendrites talk \\ 21:12, 13 December 2022 (UTC)- @Rhododendrites: would you support an editing restriction for SchroCat to remain logged-in and edit under one account? — Shibbolethink (♔ ♕) 16:12, 14 December 2022 (UTC)
- Oppose - I've clicked through most of the diffs that have been added to this thread now (thanks for adding them). So let me be clearer: the arguments that SchroCat has, since "retiring", violated sufficient behavioral policies/guidelines to merit a cban are unconvincing. It seems like half of the people don't like the way he argues, but haven't provided sufficient evidence that we typically expect to cban a long-time editor, and half of people just want him to unretire. In the latter case, what are we really even doing here? Nobody has provided evidence that his IP activity even violates any policies, and the fact that several people would ignore the rest if only he unretired his main account shows how flimsy the evidence of behavioral problems are.
- Support per above. I think the behavior is egregious enough to support a cban,
but if this turns out not to be SchroCat, then my apologies to SchroCat. The IP ranges should be blocked for some appropriate period of time regardless of how the CBAN vote turns out. Levivich (talk) 21:37, 11 December 2022 (UTC)- Tim Riley has confirmed below that these IPs are in fact SchroCat, so that ends any doubt in my mind. Unequivocal support for using IPs to continue the infobox disputes, edit warring, incivility, and general battleground editing. Levivich (talk) 22:51, 11 December 2022 (UTC)
- Still support. Elsewhere in this thread, SchroCat is arguing that the use of {{ipvandal}} with his IP constitutes an WP:ASPERSION. That's exactly the kind of combative nonsense we would be better off without. Levivich (talk) 22:48, 14 December 2022 (UTC)
- I'm being accused of casting aspersions, and the individual accusing me is tagging me as a vandal, which is casting aspersions. I raised the point that it was misleading and the said (in summary) "I'm a little bemused by this, but I'll let it go". Hardly "combative nonsense", and I've thanked the editor for changing them to a replacement. Again, not "combative". People's mileage differs, I guess, but I think it's a bit of a stretch. - 2A00:23C7:2B86:9801:6562:A1FC:F7F2:51BF (talk) 23:12, 14 December 2022 (UTC)
- I think what isn’t getting across here is that your tone is a big part of the problem. No one likes working with you when your replies are combative. If you enter every slight disagreement as though the other person is (for example) trying to label you a “vandal” by using an extremely common template, then it escalates tensions. You are, in essence, assuming bad faith. Instead of the much more reasonable alternative, that I just went with the first template that came to mind. Your tone told me “I am painful to work with”. From the very beginning. — Shibbolethink (♔ ♕) 00:00, 15 December 2022 (UTC)
- My first comment about the templates was "
{{IPuser}} would be a better template to use: labelling my activity as "IP Vandal" is misleading.
" If you wish to see it that as "combative" or a problem of tone, that is entirely your prerogative: it was not how it was written, and perhaps it may be that if you assume an editor is writing in bad faith, that is how you will perceive it. Just a thought. I don't think continuing a thread on template selection is beneficial, so I will step away, but again, thank you for changing the template to an appropriate one. 2A00:23C7:2B86:9801:6562:A1FC:F7F2:51BF (talk) 00:21, 15 December 2022 (UTC)
- I'm being accused of casting aspersions, and the individual accusing me is tagging me as a vandal, which is casting aspersions. I raised the point that it was misleading and the said (in summary) "I'm a little bemused by this, but I'll let it go". Hardly "combative nonsense", and I've thanked the editor for changing them to a replacement. Again, not "combative". People's mileage differs, I guess, but I think it's a bit of a stretch. - 2A00:23C7:2B86:9801:6562:A1FC:F7F2:51BF (talk) 23:12, 14 December 2022 (UTC)
- Still support. Elsewhere in this thread, SchroCat is arguing that the use of {{ipvandal}} with his IP constitutes an WP:ASPERSION. That's exactly the kind of combative nonsense we would be better off without. Levivich (talk) 22:48, 14 December 2022 (UTC)
- Tim Riley has confirmed below that these IPs are in fact SchroCat, so that ends any doubt in my mind. Unequivocal support for using IPs to continue the infobox disputes, edit warring, incivility, and general battleground editing. Levivich (talk) 22:51, 11 December 2022 (UTC)
- Weak Support a community ban, primarily on account of personal attacks, and of avoiding scrutiny for the personal attacks by being logged out. The editor has become a net negative to the project after rage-quitting and then coming back anonymously. Robert McClenon (talk) 02:02, 12 December 2022 (UTC)
- This is a second choice if a clearly formulated restriction is proposed that prevents logged-out editing and prevents infobox-warring. Robert McClenon (talk) 17:15, 16 December 2022 (UTC)
- support, there’s no legitimate reason an established editor with a reputation like SchoCat has would be editing anonymously; they should be cbanned for repeated bad behavior and attempting to avoid scrutiny for such behavior. Dronebogus (talk) 02:31, 12 December 2022 (UTC)
- Support CBAN. It is a very sad fact of life that some people who are highly intelligent and very talented are either unable or unwilling to collaborate effectively and behave properly. The person who goes by SchroCat is another one of them who needs to be removed from this project. Cullen328 (talk) 03:14, 12 December 2022 (UTC)
- Support a CBAN of the IPs and SchroCat unless SchroCat can log into his/her/their account and confirm with a CheckUser that they aren't behind the range of IPs, or some other method of proving that the IPs claiming to be SchroCat wasn't that person. If the IPs can be proven to not be tied to SchroCat, then undo the ban. However, the ban should not be punitive but preventative, just like blocks. A community ban with blocks to enforce it would do what it could to prevent this in the future. InvadingInvader (userpage, talk) 03:30, 12 December 2022 (UTC)
- With respect to
unless SchroCat can log into his/her/their account and confirm with a CheckUser that they aren't behind the range of IPs
, WP:CHECKME is explicit that while[o]n some Wikimedia projects, an editor's IP addresses may be checked upon their request, typically to prove innocence against a sockpuppet allegation. Such checks are not allowed on the English Wikipedia and such requests will not be granted
(emphasis mine). — Red-tailed hawk (nest) 06:43, 12 December 2022 (UTC)
- With respect to
- Oppose. I try not to get involved in these matters but this just seems to me like a massive pile-on caused by two registered editors who thought their edits to the Moorgate article shouldn't be reverted. (Mostly, they should have been, because it was better before.) In other words, a content dispute. It's then been blown up into a huge thing about editing from an IP (which as we all know is illegal) that changes (which as we all know is technically impossible) and then just flinging as much as possible at him in the hope that some of it sticks. I can see the inevitable outcome here and I don't intend to participate further (don't ping me: I won't be interested) but I just wanted to register my view that something ludicrous and vengeful is taking place here and people are enjoying a proper oldschool Wikipedia lynching. Best wishes to all, DBaK (talk) 10:08, 12 December 2022 (UTC)
- Oppose. We wouldn't be having this conversation if it was about one account. What it boils down to is that established editors are biased against IPs and that it's mildly annoying that they have a dynamic IP. Their conduct is nowhere near the level that would rise to a community ban or even an indef block for a long-term registered editor. I won't defend the edit warring and incivility but I offer in mitigation that this bias leads editors to behave much more aggressively than they would with an account. Almost every editor with multiple FAs has been involved in an edit war or heated discussion to preserve the quality of an FA. That's because it takes weeks or months of researching and writing to get an article to that standard but seconds for somebody to make an edit without checking the source material. HJ Mitchell | Penny for your thoughts? 10:22, 12 December 2022 (UTC)
- Forget it as it cannot be implemented. Just give short blocks to IP that cause trouble. People that care can add the FAs to their own watch list to see if there are edit wars relating to them. Graeme Bartlett (talk) 11:03, 12 December 2022 (UTC)
- @Graeme Bartlett Though exceedingly rare, there is actually a precedent for community banning an IP user with a long pattern of incivillity and edit warring [174], enshrined into WP:CBAN. Of note, that was for an IP range blocked 15+ times before anyone bothered to talk about it. SchroCat has been blocked at least 7 times, with 3 more previously unreported edit wars that went unblocked as I describe below [175]. There’s probably more if we combine the edit histories from the various IP ranges [176]
[17]. There are also numerous personal attacks going unreported. They've also openly flouted these blocks in the past, e.g. instead of appealing a block, "Never mind ... time to reset the router
" [177] I would ask: how many blocks does it take for us to realize someone needs a CBAN? How many edit wars with the user failing to learn any lesson? No one should be above scrutiny. — Shibbolethink (♔ ♕) 16:13, 12 December 2022 (UTC)(strike range that very probably wasn't SchroCat) - It's not true that it cannot be implemented. A ban attaches to an individual person, not to an account, and a CBAN certainly can be implemented. What I think you meant to say, is that it wouldn't be 100% effective because of dynamic IPs. That may be true, but it is certainly not a reason for the community to throw up their hands and not issue a ban, if they believe that a ban is warranted. For one thing, without a ban, the SchroCat account could be used again, whereas with a ban, it could not. Mathglot (talk) 19:14, 12 December 2022 (UTC)
- @Graeme Bartlett Though exceedingly rare, there is actually a precedent for community banning an IP user with a long pattern of incivillity and edit warring [174], enshrined into WP:CBAN. Of note, that was for an IP range blocked 15+ times before anyone bothered to talk about it. SchroCat has been blocked at least 7 times, with 3 more previously unreported edit wars that went unblocked as I describe below [175]. There’s probably more if we combine the edit histories from the various IP ranges [176]
- Support, per nomination, with particular reference to the evasion of scrutiny. XAM2175 (T) 12:22, 12 December 2022 (UTC)
- Oppose, the "all the reasons" box contains insufficient proof to ban (just allegations). The diffs I have seen further up on the page mostly look like garden variety content/style disputes to me, and most of the IP edits referred to here are actually good. I am surprised to see this level of support for a CBAN for such a long time productive editor. I would very much prefer to see SchroCat editing from an account, but using IPs to edit isn't prohibited, and their behaviour doesn't look like socking. If a ban is desired, I would suggest to go through an ArbCom case and also consider alternative remedies; ANI isn't great at deliberatively finding solutions to problems. —Kusma (talk) 13:38, 12 December 2022 (UTC)
- It's nice to know an admin for Wikipedia thinks accusing other editors of stalking, harassment, and gaslighting is just a part "garden variety content disputes." Do we just throw out WP:ASPERSIONS if the editor is perceived as productive in other areas? Someone else raised this question, but if this behavior isn't considered violating ASPERSIONS then I'd love to know what would. Is there a sliding scale? If you have 4 FA articles can you violate other Wikipedia guidelines? Is there a double standard guideline for productive users? Nemov (talk) 13:51, 12 December 2022 (UTC)
- Productive users have the right to a fair trial. I find the evidence presented above confusing and generally unconvincing. —Kusma (talk) 15:00, 12 December 2022 (UTC)
- Are there specific points in my collapse box above that you find have insufficient evidence? (or perhaps the 1-2 you find most unsupported?) I would be happy to provide more diffs of their behavior, but there were honestly so many and so deep into the edit histories that it would take a long time for each and every point. I went ahead and added more diffs to that collapse box, let me know what you think. I am happy to do it for any particular point as requested, as I described in that comment. I completely respect your right to disagree in good faith in our interpretations of their behavior, but I want to at least know which ones you find unsupported. — Shibbolethink (♔ ♕) 16:16, 12 December 2022 (UTC)
- The "editing an archive" complaint is unfounded (SchroCat was editing the live talk page, later archived by moving). There is no evidence for "aspersions". The edit war at the London Underground thing doesn't have diffs. "Bludgeon" has no diffs either. Not convincing. —Kusma (talk) 17:59, 12 December 2022 (UTC)
- diffs on aspersions are up there, I think we are just disagreeing on interpretation, and that's fine. The edit war for London Underground is linked to the EWN report, here are the diffs: [178][179][180][181][182] and I think there's one more revert as described by Daniel Case above, but can't pinpoint it. Anyway clearly over 3RR.Re: archive editing, I didn't recognize the two as an edit history move, thanks for pointing that out, I see you are absolutely right. But this appears to be a pretty clear cut example: [183] Are you really saying that diff is from someone editing a talk page that was later archived?Here's the discussions the user BLUDGEONed/derailed imo: [184][185]. You'll notice I also commented a fair amount in those discussions, but mostly in response to attempts to besmirch my reputation and generally discount my opinion based on unfounded accusations. Hence, ASPERSIONS. I also attempted several times to get the user to move the offtopic discussions to their user talk to UNBLUDGEON the discussion, unsuccessfully, so I stopped trying. — Shibbolethink (♔ ♕) 18:13, 12 December 2022 (UTC)
- The Moorgate crash is a rather silly edit war over minor stylistic points (that might have looked different had the edits not come from an IP). You are right about the second archive, and I have no excuse for that (many recent archive edits are the result of "reply" being active on archives, something the developers need to fix by introducing a new magic word, but that doesn't seem to be the cause in your example). The infobox discussion is far longer than necessary, but the IP is essentially correct that being inside an infobox is not an excuse to have uncited information in a FA (and it now seems resolved by sourced information). As infoboxes are notoriously bad at nuance, any precise-looking information in there should be excellently sourced. Problematic edits? Yes, sure. Worth a ban? Not seeing it, sorry. —Kusma (talk) 22:12, 12 December 2022 (UTC)
- @Kusma: would you support an editing restriction for SchroCat to remain logged-in and edit under one account? — Shibbolethink (♔ ♕) 16:13, 14 December 2022 (UTC)
- If the changing IP addresses are the main issue here, then that could be a not unreasonable extension of the current restriction (and I haven't looked into the prehistory of that), but it would need to be carefully worded. Accidental logged out edits, especially if the user notices and owns up to them reasonably quickly, should not result in sanctions to avoid this becoming a "gotcha" remedy. —Kusma (talk) 16:45, 14 December 2022 (UTC)
- Kusma, please see this post, below. Thanks - 86.155.193.84 (talk) 17:22, 14 December 2022 (UTC)
- I would certainly welcome it if you come back with an account, whatever its name (if you can't get your old one back). I'm not sure formal restrictions are needed other than a reminder to abide by WP:LOUTSOCK should you ever edit without logging in. —Kusma (talk) 17:41, 14 December 2022 (UTC)
- Kusma, please see this post, below. Thanks - 86.155.193.84 (talk) 17:22, 14 December 2022 (UTC)
- If the changing IP addresses are the main issue here, then that could be a not unreasonable extension of the current restriction (and I haven't looked into the prehistory of that), but it would need to be carefully worded. Accidental logged out edits, especially if the user notices and owns up to them reasonably quickly, should not result in sanctions to avoid this becoming a "gotcha" remedy. —Kusma (talk) 16:45, 14 December 2022 (UTC)
- @Kusma: would you support an editing restriction for SchroCat to remain logged-in and edit under one account? — Shibbolethink (♔ ♕) 16:13, 14 December 2022 (UTC)
- The Moorgate crash is a rather silly edit war over minor stylistic points (that might have looked different had the edits not come from an IP). You are right about the second archive, and I have no excuse for that (many recent archive edits are the result of "reply" being active on archives, something the developers need to fix by introducing a new magic word, but that doesn't seem to be the cause in your example). The infobox discussion is far longer than necessary, but the IP is essentially correct that being inside an infobox is not an excuse to have uncited information in a FA (and it now seems resolved by sourced information). As infoboxes are notoriously bad at nuance, any precise-looking information in there should be excellently sourced. Problematic edits? Yes, sure. Worth a ban? Not seeing it, sorry. —Kusma (talk) 22:12, 12 December 2022 (UTC)
- diffs on aspersions are up there, I think we are just disagreeing on interpretation, and that's fine. The edit war for London Underground is linked to the EWN report, here are the diffs: [178][179][180][181][182] and I think there's one more revert as described by Daniel Case above, but can't pinpoint it. Anyway clearly over 3RR.Re: archive editing, I didn't recognize the two as an edit history move, thanks for pointing that out, I see you are absolutely right. But this appears to be a pretty clear cut example: [183] Are you really saying that diff is from someone editing a talk page that was later archived?Here's the discussions the user BLUDGEONed/derailed imo: [184][185]. You'll notice I also commented a fair amount in those discussions, but mostly in response to attempts to besmirch my reputation and generally discount my opinion based on unfounded accusations. Hence, ASPERSIONS. I also attempted several times to get the user to move the offtopic discussions to their user talk to UNBLUDGEON the discussion, unsuccessfully, so I stopped trying. — Shibbolethink (♔ ♕) 18:13, 12 December 2022 (UTC)
- The "editing an archive" complaint is unfounded (SchroCat was editing the live talk page, later archived by moving). There is no evidence for "aspersions". The edit war at the London Underground thing doesn't have diffs. "Bludgeon" has no diffs either. Not convincing. —Kusma (talk) 17:59, 12 December 2022 (UTC)
- Are there specific points in my collapse box above that you find have insufficient evidence? (or perhaps the 1-2 you find most unsupported?) I would be happy to provide more diffs of their behavior, but there were honestly so many and so deep into the edit histories that it would take a long time for each and every point. I went ahead and added more diffs to that collapse box, let me know what you think. I am happy to do it for any particular point as requested, as I described in that comment. I completely respect your right to disagree in good faith in our interpretations of their behavior, but I want to at least know which ones you find unsupported. — Shibbolethink (♔ ♕) 16:16, 12 December 2022 (UTC)
- Productive users have the right to a fair trial. I find the evidence presented above confusing and generally unconvincing. —Kusma (talk) 15:00, 12 December 2022 (UTC)
- It's nice to know an admin for Wikipedia thinks accusing other editors of stalking, harassment, and gaslighting is just a part "garden variety content disputes." Do we just throw out WP:ASPERSIONS if the editor is perceived as productive in other areas? Someone else raised this question, but if this behavior isn't considered violating ASPERSIONS then I'd love to know what would. Is there a sliding scale? If you have 4 FA articles can you violate other Wikipedia guidelines? Is there a double standard guideline for productive users? Nemov (talk) 13:51, 12 December 2022 (UTC)
- Support. It's unacceptable for a user, however prominent, to be evading scrutiny as an IP editor when (a) they are subject to editing restrictions, (b) having a history of socking, and (c) have a lengthy block log. I understand the mentality that leads to people bending over backwards for long-time productive editors but I can't agree with it. If SchroCat reassumes control over his account, as I believe he's capable of doing, I would reconsider. Mackensen (talk) 14:29, 12 December 2022 (UTC)
- Mackensen You are, of course, entitled to keep your !vote how you wish, but just to clarify that a. the only restriction I have ever had is over my account name; b. that's not accurate; and c; Errr.. yes, OK, you have a good point there: my log is not my proudest achievement at all. As I have posted below, I cannot re-open my account for technical reasons, but I am hoping that the WMF boffins will be able to rectify the issue. Once they do, I will edit only under that name in future. Thanks - 2A00:23C7:2B86:9801:1E8:2D44:8B40:EBA5 (talk) 12:57, 14 December 2022 (UTC)
- Thank you for your response. Given your undertaking to resume editing from a single account (hopefully your existing one), I withdraw my support for a ban. As I've said above, I think the nature of your editing as an IP unnecessarily exacerbated editing conflicts. I want to be clear on one other point: these conflicts would have existed regardless and they need to stop going forward. Several dozen editors are ready to ban you outright and probably still are, even though they think highly of your contributions. Most don't do this out of malice; they just don't think you're capable of editing productively in a collaborative environment, and we don't get to pick all of our collaborators here. Please consider this. Mackensen (talk) 13:04, 14 December 2022 (UTC)
- Mackensen You are, of course, entitled to keep your !vote how you wish, but just to clarify that a. the only restriction I have ever had is over my account name; b. that's not accurate; and c; Errr.. yes, OK, you have a good point there: my log is not my proudest achievement at all. As I have posted below, I cannot re-open my account for technical reasons, but I am hoping that the WMF boffins will be able to rectify the issue. Once they do, I will edit only under that name in future. Thanks - 2A00:23C7:2B86:9801:1E8:2D44:8B40:EBA5 (talk) 12:57, 14 December 2022 (UTC)
- Oppose as SchroCat is responsible for a lot of high quality article content that readers continue to benefit from, and I don't believe they should be thanked for that with a community ban. Many of the IP edits were improvements, and I see no need to prevent that from continuing. Mr Ernie (talk) 16:17, 12 December 2022 (UTC)
- So editors who produce quality content are above the law? Dronebogus (talk) 05:10, 13 December 2022 (UTC)
- Don't actually have an opinion here, but the principal is that we don't punish for wrong-doings, we restrict to prevent future damage. The question is: is the user-with his good and his bad-a net positive or negative? If he does more good than bad, a site CBAN is more harmful than helpful, although some more limited restriction may be appropriate. Animal lover |666| 17:43, 13 December 2022 (UTC)
- So editors who produce quality content are above the law? Dronebogus (talk) 05:10, 13 December 2022 (UTC)
- Comment. I don't know if I support a CBAN at this time since I haven't fully reviewed the evidence, but I completely think that the community is well within its rights to require the editor formerly known as SchroCat to make a new account and be limited to just using that for the future. A community-imposed one account restriction should seriously be considered alongside this one (separately). IP editing is a privilege, yes; but if SchroCat is going to be getting in these sorts of disputes then they might as well make an account so people can immediately know they are talking to the right person. –MJL ‐Talk‐☖ 16:50, 12 December 2022 (UTC)
- What I would tell you is that the editor has attempted WP:CLEANSTART twice before, and got banned both times [186] [187], and attempted to WP:VANISH once [188][189]., and had it reversed, all 3 due to this exact sort of misbehavior. They've been blocked at least seven times I can count across IP ranges and usernames [190][191][192]
[7][193][194][195] (I think actually more but it's such a complex history I have difficulty counting it all) All due to misbehavior similar to what is described in this report. They've also actually openly evaded those blocks in the past: [196][197] I don't think any more WP:ROPE is beneficial to the project in this case. (edited to remove ip range that very probably wasn't SchroCat 07:59, 13 December 2022 (UTC)) — Shibbolethink (♔ ♕) 17:10, 12 December 2022 (UTC)- @Shibbolethink: My suggestion is not meant strictly to be an alternative to the proposed sanction. It could very well be passed in addition to a CBAN, so that's why I suggested it be considered
separately
. –MJL ‐Talk‐☖ 03:39, 13 December 2022 (UTC)
- @Shibbolethink: My suggestion is not meant strictly to be an alternative to the proposed sanction. It could very well be passed in addition to a CBAN, so that's why I suggested it be considered
- What I would tell you is that the editor has attempted WP:CLEANSTART twice before, and got banned both times [186] [187], and attempted to WP:VANISH once [188][189]., and had it reversed, all 3 due to this exact sort of misbehavior. They've been blocked at least seven times I can count across IP ranges and usernames [190][191][192]
- Support The evidence is sufficient, clear and problematic, indeed it is part of a long-term pattern of regular problems. Alanscottwalker (talk) 17:37, 12 December 2022 (UTC)
- Support - per Mackensen. EnPassant♟♙ (talk) 18:33, 12 December 2022 (UTC)
- User currently blocked, for sockpuppetry, ironically. 77.249.149.237 (talk) 20:43, 15 December 2022 (UTC)
- Support, due to the continued drama. This ban makes it clear that IPs with SchroCat's MO aren't welcome and can indeed be blocked at first sight, as implored above. When you leave, you leave, you don't get to be Schrodinger's actual cat. IznoPublic (talk) 20:07, 12 December 2022 (UTC)
- At a minimum, I'd support MJL's idea of making the editor actually register a new account (or return to their old account) so that something can be done about tracking their incivility. While, yes, stewardship of an FA does mean that editors will occasionally get into disagreements with other editors and that sometimes those can get heated or become protracted, it's also quite possible to not turn those disagreements into some of the instances of incivility that have been highlighted here. The only reason I'm not totally on the CBAN wagon is that I'm not sure we CAN effectively CBAN someone who edits from a rotating IP address - but that shouldn't excuse the bad behavior on display here. Ealdgyth (talk) 21:00, 12 December 2022 (UTC)
Oppose this is a massive—and frankly, somewhat cruel—overreaction. I can't imagine a thread like this even close to developing if the user in question was a registered account; i.e., this is a continued bias against IPs. If SC continues to provide objectionable actions after this thread, I would consider something like this. Aza24 (talk) 21:04, 12 December 2022 (UTC)- Not willing to support or oppose this. Aza24 (talk) 22:14, 12 December 2022 (UTC)
- Oppose. SchroCat is a productive editor. The people who started this AN campaign often disagree with SchroCat at infobox discussions (including at least two current ones), and so they want to get him banned. -- Ssilvers (talk) 21:52, 12 December 2022 (UTC)
- That's why we seek community feedback, because it isn't up to the people who started this to ban him or not. And there is no policy anywhere on Wikipedia that gives an editor with a bannable pattern of behavior a get-out-of-jail-free card, just because they have umpty-zillion edits, and seventy-eleven FA's. If their behavior is bannable, then ban them; if it isn't, don't. Mathglot (talk) 01:43, 13 December 2022 (UTC)
Support.As someone who was a long term IP editor before making an account there is definitely a bias against IP editors, but please stop trying not make this case about that. There are many thousand of IP editors doing good constructive work without causing any controvesy. This is seemingly the second recent editor who has joined there ranks because it gives them anonymity to continue some personal grudge. That is not anti-IP bias, and their actions only make it harder for those IPs trying to edit in good faith. It is always bad to lose good writers, it's not something I am good at so I try to work to support those that are. But this is a cooperative project, and that sometimes means losing and dropping the hatchet. If you can't do that you will become more of a burden on the project than a bonus. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 22:41, 12 December 2022 (UTC)- Switch to oppose if an official restriction to one account (no logged out) editing with an official warning over behaviour is put in place. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 20:06, 14 December 2022 (UTC)
- ActivelyDisinterested Well, I’m back on my account and out of retirement, if that helps. Cheers - SchroCat (talk) 07:22, 16 December 2022 (UTC)
- Sorry for a slow reply. I hope it helps, go back to writing the articles that so many applaud you for. Let these arguments go, they don't help you or the project. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 17:17, 19 December 2022 (UTC)
- ActivelyDisinterested Well, I’m back on my account and out of retirement, if that helps. Cheers - SchroCat (talk) 07:22, 16 December 2022 (UTC)
- Oppose. Bans and blocks are meant to be preventative. As SchroCat has committed to editting logged in I feel it's appropriate to give them a chance to continue. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 17:24, 19 December 2022 (UTC)
- Switch to oppose if an official restriction to one account (no logged out) editing with an official warning over behaviour is put in place. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 20:06, 14 December 2022 (UTC)
- Oppose. overreaction per Aza24. Ceoil (talk) 22:44, 12 December 2022 (UTC)
- Support. After reading all the diffs and discussion, I agree with the characterizations of ASPERSIONS, OWN, edit warring, etc. and that, on aggregate, they well outweigh any positive contributions by this user. JoelleJay (talk) 00:41, 13 December 2022 (UTC)
- Oppose As a CBAN is effectively unenforceable in this capacity. Semi-protect/Extended Confirmation for the given pages and move on. Respectfully, this never should have taken this long. As for being "retired", might I suggest using {{Semi-retired}} instead? Even if he doesn't, nothing prevents him from coming back and there is no available sanction guideline/policy that enforces the notion that "retired persons may not edit"...that path is a red herring and unnecessary to even address. Buffs (talk) 04:35, 13 December 2022 (UTC)
- If this ban is approved, SchroCat would be banned. Future edits as an IP would be a violation of sock guidelines. That seems pretty enforceable to me. Nemov (talk) 04:42, 13 December 2022 (UTC)
- Support. SchroCat has been net negative for quite a long time, and all his FAs and GAs are negated by ownership, incivility, and overall disruption. His "retirement" was not in good faith but under a cloud of sanctions and restrictions. I'm not particularly concerned about enforcement – as with other long-time abusers, his future edits will be subject to RBI. No such user (talk) 09:05, 13 December 2022 (UTC)
- Oppose Using a cban to handle a noisy IP is ridiculous overreach. Writing 60 FAs does not earn you the right to be a jerk but if such a person has gone rogue something has gone wrong and a decent community would workaround the problem (with semi-protection or blocks) rather than crush one of a few giant contributors (SchroCat is #16 at Wikipedia:List of Wikipedians by featured article nominations). Johnuniq (talk) 09:36, 13 December 2022 (UTC)
- You seem to have immediately contradicted yourself (“FAs aren’t a jerk license but we should be lenient because he wrote a ton of FAs”) Dronebogus (talk) 12:27, 13 December 2022 (UTC)
- What’s gone “wrong” is that SchoCat is probably starting to think he’s WP:UNBLOCKABLE precisely because of this kind of special treatment Dronebogus (talk) 12:29, 13 December 2022 (UTC)
- "Starting to think"? Hahaha. Levivich (talk) 14:40, 14 December 2022 (UTC)
Writing 60 FAs does not earn you the right to be a jerk but...
- "but" doing a lot of heavy lifting here. Nemov (talk) 15:06, 14 December 2022 (UTC)
- It's disappointing to see that several of those commenting here are unable to understand a short statement. Regarding unblockable, that's a great meme but it's bullshit. Like many admins, I would block the IPs or SchroCat myself for a suitable period if needed. If SC repeatedly posted copyvios or BLP violations or outrageous attacks, an indef would be called for. However, SC has done none of those things! Johnuniq (talk) 01:33, 15 December 2022 (UTC)
- "Starting to think"? Hahaha. Levivich (talk) 14:40, 14 December 2022 (UTC)
- @Johnuniq: would you support an editing restriction for SchroCat to remain logged-in and edit under one account? — Shibbolethink (♔ ♕) 16:14, 14 December 2022 (UTC)
- Of course. The only reason SchroCat is posting from IPs is that they were collateral damage in the infobox wars. One day Wikipedia might be written by chatbot (see here) but until then we need to understand that not every great contributor can remain emotionless. Johnuniq (talk) 01:33, 15 December 2022 (UTC)
- Support IP hopping is difficult to police, but a CBAN will make it easier to deal with the disruptive behavior. There have been plenty of chances for SC to productively work with the community, but they are very much not interested. Der Wohltemperierte Fuchs talk 13:04, 13 December 2022 (UTC)
- Support AGF isn't a suicide pact. Schro was a very good editor, but these post "retirement" edits have exhausted the community's patience. Like a block, a retirement should apply to a person and not just an account. If he won't edit collaboratively, the community should retire him. Star Mississippi 17:20, 13 December 2022 (UTC)
- Support No one is bigger than the project. I do not care how many GA/FAs he wrote, the behavior warrants a ban at this point. SC has been given countless number of chances to work collectively and refuses to do so. To say "Oh but they wrote x number of GAs, we can't block/ban!" is exactly why we have WP:UNBLOCKABLES. RickinBaltimore (talk) 17:37, 13 December 2022 (UTC)
- Oppose. Per most of the opposes above, although both DBak and HJ Mitchell seem to strike to the heart of the matter and Kusma's logic seems irrefutable. (Not of course that such a thing ever stopped anyone from trying.) Gog the Mild (talk) 22:43, 13 December 2022 (UTC)
- Oppose I don't see any evidence of a persistent behavioral problem. It is relatively easy to cherry-pick isolated examples of conduct from an editor's contribution history that violate one policy or another. Looking at Moorgate tube crash I don't see any evidence of WP:OWN, just a content dispute over grammar and punctuation. Maybe the judgment of somebody who has guided ~60 articles through GA and FA reviews shouldn't be immediately discounted as WP:OWN? I also question how User:shibbolethink came to be at that article anyway? It seems like a bit of coincidence that a Pittsburgh med student would suddenly develop an interest in London Underground. I think sometimes SchroCat can come across as overly hostile and that perhaps alienates people from viewing his contributions objectively, but on the other hand he is the closest to an artist that Wikipedia has, and I guess he has the temperament of an artist too. If he is only semi-retired now then perhaps his user page should reflect that, but while Wikipedia is the encyclopedia anybody can edit (anonymously) then I don't see why this is a right that should be denied to SchroCat, simply on the grounds that he used to edit under an account. Betty Logan (talk) 02:36, 14 December 2022 (UTC)
but on the other hand he is the closest to an artist that Wikipedia has, and I guess he has the temperament of an artist too.
- Ah, the "temperament of an artist defense" for an editor with multiple blocks for bad behavior and continued hostility to others. Some of these arguments read like WP:FANCLUB. No wonder SchroCat has gotten away with this behavior for so long. Nemov (talk) 02:50, 14 December 2022 (UTC)
- As a rule of thumb, I think indefs and bans should be reserved for editors whose persistent poor behavior has proven detrimental to improving the encyclopedia, not for editors who have a substantial track record in improving the encyclopedia. I am not seeing much evidence of the former. Looking at the trajectory of this whole dispute, it seems to have sprung out of a RFC on one specific article which then proliferated to a bunch of others, and that wasn't really SchroCat's doing. Why is the other prominent party in this dispute being permitted to effectively "run the prosecution" and propose sanctions on SchroCat? Why hasn't User:shibbolethink been invited to explain how he suddenly ended up editing unrelated articles that SchroCat had recently edited? Betty Logan (talk) 04:22, 14 December 2022 (UTC)
Why hasn't User:shibbolethink been invited to explain how he suddenly ended up editing unrelated articles that SchroCat had recently edited?
I actually explained this in detail above. [198] — Shibbolethink (♔ ♕) 04:26, 14 December 2022 (UTC)- The point you're missing is that SchroCat could reasonably imagine that hounding was occurring. Sure, you have reasons that you developed an interest in the articles where SC happened to be involved in infobox disagreements and more, and SC should have assumed good faith and been less confrontational. However, a decent person would see that there was room for SC to feel under siege even if that belief was ill founded. When dealing with anti-science POV pushers, it is best to bulldoze them out of the way. That approach is not helpful when dealing with someone who is a top content producer and who is currently in trouble because certain articles are being picked off one-by-one due to the infobox wars. It looks like that battle is lost and that should be enough satisfaction for those who feel SchroCat was out of line. Johnuniq (talk) 04:40, 14 December 2022 (UTC)
While I can't speak for anyone else, I don't want to punish SchoCat in any way or give them their just desserts or care about getting "satisfaction" in any way. I would strongly oppose and support an instant siteban for anyone who is trying to add infoboxes or change articles to punish SchoCat for any past or current misbehaviour let alone disagreement. While I acknowledge people can easily fool themselves and also that people can do stuff without realising they are doing it, I think there's good reason to feel the vast majority of edits which are changing article SchoCat have nothing to do with any attempt to target SchoCat's contributions. There are many editors who do like infoboxes some of these may have some knowledge of the infobox wars, but even among those many of those may have very limited knowledge of the participants, their histories etc. They just think infoboxes are useful and when they find articles which lack them, they want to add them. (Likewise for any other particular preference of SchoCat that another editor may try to change.)
SchoCat continues to strongly dislike infoboxes which in itself is fine. This strong dislike causes somewhat understandable annoyance or perhaps even anger when people try to or do add infoboxes to articles they've significantly contributed to, again fairly understandable. However while we can have sympathy with how they feel, we should not have sympathy with inappropriate behaviour here on Wikipedia that results from this annoyance or anger, that's unacceptable. They need to learn to somehow deal with their annoyance or anger in a way that doesn't cause significant problems here such as walking way from the discussion, at least for a few days.
On a personal level, I generally find infoboxes useful, but care so little that I think the number of times I've expressed an opinion on whether an article should or should not have one is probably in the low single digits. So while I may technically disagree with SchoCat on infoboxes, I don't really care and there is no reason why I'd want to do anything whatsoever to get "satisfaction" over my disagreement with them on infoboxes. I'd further note there are many aspects of Wikipedia that I dislike as I think with nearly all editors here. Sometimes I do let my annoyance or anger out too far, but I do generally manage to force myself to walk away.
So the important question is, does an editor let their dislike of those aspects affect their editing here in ways that cause harm? If they do, and that harm reaches a level where it's too much, then we have to take action to protect Wikipedia, which may include banning the editor involved. We can try to encourage the editor to improve, but ultimately their reaches a point where we have to say, sorry we've given you enough chances.
Coming back to your comment, what would truly give me satisfaction is if SchoCat continues to edit productively here, continue to oppose infoboxes or other changes they disagree with in a reasonable fashion, and accepts the result of any community consensus for or against them. However a lot of that isn't on us as a community. And so if that isn't possible, then what gives me the least dissatifaction is dealing with situations that arise in the way that causes the less amount of harm.
Which in this case seems to be IMO restricting SchoCat to one account and blocking/banning them if they refuse to abide. I'm definitely not going to be happy if this closes with the ban enacted but I will be less unhappy than I would be if closes with the ban enacted. Although the problem isn't that extreme so the gulf between the two isn't as wide as it is in some other cases but it's still enough for me to support.
- The point you're missing is that SchroCat could reasonably imagine that hounding was occurring. Sure, you have reasons that you developed an interest in the articles where SC happened to be involved in infobox disagreements and more, and SC should have assumed good faith and been less confrontational. However, a decent person would see that there was room for SC to feel under siege even if that belief was ill founded. When dealing with anti-science POV pushers, it is best to bulldoze them out of the way. That approach is not helpful when dealing with someone who is a top content producer and who is currently in trouble because certain articles are being picked off one-by-one due to the infobox wars. It looks like that battle is lost and that should be enough satisfaction for those who feel SchroCat was out of line. Johnuniq (talk) 04:40, 14 December 2022 (UTC)
- As a rule of thumb, I think indefs and bans should be reserved for editors whose persistent poor behavior has proven detrimental to improving the encyclopedia, not for editors who have a substantial track record in improving the encyclopedia. I am not seeing much evidence of the former. Looking at the trajectory of this whole dispute, it seems to have sprung out of a RFC on one specific article which then proliferated to a bunch of others, and that wasn't really SchroCat's doing. Why is the other prominent party in this dispute being permitted to effectively "run the prosecution" and propose sanctions on SchroCat? Why hasn't User:shibbolethink been invited to explain how he suddenly ended up editing unrelated articles that SchroCat had recently edited? Betty Logan (talk) 04:22, 14 December 2022 (UTC)
- “Temperament of an artist” what a preposterous defense. It’s the post-#metoo era, artists (let alone Wikipedia editors) don’t even get that excuse to be jackasses. Dronebogus (talk) 05:41, 14 December 2022 (UTC)
Supportit's clear that SchoCat's usage of IPs has crossed over into the realm of evading scrutiny and so is in violation of our sockpuppetry policy. I'd note this isn't my main preference. I think it would be better to start off a one account restriction for SchoCat. They could return to their original account, or make a new one clearly associated with their old account if they wanted to. They could not edit from IPs. However this is the proposal we have and I acknowledge there's a fair chance it's pointless to try a one account restriction. It seems most likely either SchoCat would voluntarily give up on editing completely or they'd ignore the restriction and we'd just have basically the same result with a defacto ban since they continually violate their community imposed one account restriction. If SchoCat gives any indication they'd be willing to accept such a restriction, I'd no longer support this proposal. I'm unconvinced by a number of the opposes which give too much leeway to an editor just because of past contributions which even if those contributions have been highly positive is not something I support. At least one of the opposes comes from an editor who attacked the proposer track record without proper analysis, and frankly was what convinced me to take the time to look in to this. Nil Einne (talk) 05:54, 14 December 2022 (UTC)- Nil Einne Well, I’m back on my account, if that helps. And yes, the ‘restriction’ you refer to is how I behaved while I had an account (ie, I never logged out to edit as an IP and then logged back in again): that will, of course, be how I edit in the future. SchroCat (talk) 07:31, 16 December 2022 (UTC)
- Switch to oppose, provided SchroCat only edits from this account. SchroCat's behaviour has been problematic and unfortunately their comments make it unclear it's likely to improve. However it's borderline enough that I'm willing to give them one last chance when combined with the fact they can no longer escape the scrunity every regular editor is under by editing from frequently changing IPs. Perhaps we'll be back here in a few months, I hope not. To be clear, even without a formal community imposed one account restriction, I will continue any significant editing from IPs as enough to support a site ban since I consider it already well justified without the need to demonstrate any clear misbehaviour from these IPs. Nil Einne (talk) 10:38, 16 December 2022 (UTC)
- Oppose (as subject) I have had a couple of years trying to stay away, but have legitimately come back and edited as an IP from time to time. While editing occasionally as an IP was OK, my activity has been rising recently and it is clear from this thread that I cannot continue as an IP editor, regardless of any other decision is reached here. There are technical problems in re-accessing my account that I will have to get the WMF boffins to rectify, but the SchroCat account will (hopefully) return shortly. SchroCat, editing from - 2A00:23C7:2B86:9801:1E8:2D44:8B40:EBA5 (talk) 09:27, 14 December 2022 (UTC)
- Re-signing with re-accessed account. - SchroCat (talk) 06:31, 16 December 2022 (UTC)
- Oppose any sanction, per SchroCat's comment immediately above this one (and per other things which are hopefully now moot). SchroCat, it'll be good to see you back. Boing! said Zebedee (talk) 12:51, 14 December 2022 (UTC)
- PS: Is it only me who finds it amusingly appropriate that, due to technical issues, we can't tell whether the SchroCat account is alive or dead? Boing! said Zebedee (talk) 16:50, 14 December 2022 (UTC)
- Schrocat has been behaving badly, please stop being so buddy-buddy. People aren’t citing WP:FANCLUB baselessly, and making your personal biases obvious weakens your argument. We have talk pages for this. Dronebogus (talk) 03:19, 15 December 2022 (UTC)
- You really should have a read of WP:NPA and WP:BADGER, you know. Boing! said Zebedee (talk) 09:19, 15 December 2022 (UTC)
- That isn’t a personal attack. Dronebogus (talk) 11:25, 15 December 2022 (UTC)
- <Moved to user talk page> Boing! said Zebedee (talk) 12:12, 15 December 2022 (UTC)
- That isn’t a personal attack. Dronebogus (talk) 11:25, 15 December 2022 (UTC)
- You really should have a read of WP:NPA and WP:BADGER, you know. Boing! said Zebedee (talk) 09:19, 15 December 2022 (UTC)
- Oppose - I agree with Boing! said Zebedee. Welcome back, SchroCat.--🌈WaltCip-(talk) 13:12, 14 December 2022 (UTC)
- Sorry to break up the celebration but issue raised here is the editor and not the IP. Returning to SchroCat does nothing to address the years of problematic behavior and bans that have occurred. It just obfuscates the issue. Nemov (talk) 13:43, 14 December 2022 (UTC)
- The issue raised here has been SchroCat's IP edits, and "evading scrutiny" has been one of the major points. If SchroCat edits from an account again instead, this does the exact opposite of obfuscating issues. —Kusma (talk) 15:35, 14 December 2022 (UTC)
- Thanks for wikisplaining to me my own notice. I didn't bring this here because SchroCat was editing from an IP. Nemov (talk) 15:42, 14 December 2022 (UTC)
- You might not have done, but a lot of commentators in favour of sanctions have indeed focused on the IP aspect. So stopping editing from IPs is definitely relevant to the entirety of the dispute (even if not to your personal complaint). Boing! said Zebedee (talk) 15:54, 14 December 2022 (UTC)
- Thanks for wikisplaining to me my own notice. I didn't bring this here because SchroCat was editing from an IP. Nemov (talk) 15:42, 14 December 2022 (UTC)
- The issue raised here has been SchroCat's IP edits, and "evading scrutiny" has been one of the major points. If SchroCat edits from an account again instead, this does the exact opposite of obfuscating issues. —Kusma (talk) 15:35, 14 December 2022 (UTC)
- Sorry to break up the celebration but issue raised here is the editor and not the IP. Returning to SchroCat does nothing to address the years of problematic behavior and bans that have occurred. It just obfuscates the issue. Nemov (talk) 13:43, 14 December 2022 (UTC)
- Oppose -- I'd certainly prefer to see Schrocat editing under a named account again but cannot support a ban in the current circumstance either. Aside from the record of creating and maintaining high-quality content, I've had nothing but positive interactions with the editor, in any guise. I've also seen how the editor can put aside serious disagreements from the past and re-establish a cordial working relationship -- naturally it takes two to tango there... Wasting everybody's time? The subject didn't open this thread. The idea that Schrocat's defenders are nothing more than a fan club? Maybe the earlier suggestion of a lynch mob struck a nerve. Obviously a lot of people here are going to disagree with each other but I hope we can put enough trust in the closer to determine the key arguments themselves. Cheers, Ian Rose (talk) 15:48, 14 December 2022 (UTC)
- @Ian Rose: Would you support an editing restriction to stay logged-in and under one account? — Shibbolethink (♔ ♕) 16:11, 14 December 2022 (UTC)
- Rather pointless. I have never logged out of an account specifically to edit as an IP except; I gave up my account to leave before deciding to do some light occasional editing as an IP (which is a legitimate course to take). As to "one name" editing, you'll find ArbCom got there before you 2A00:23C7:2B86:9801:1E8:2D44:8B40:EBA5 (talk) 16:22, 14 December 2022 (UTC)
- So, wait, are you saying you would or wouldn't comply with such a restriction? Above, you said:
I cannot re-open my account for technical reasons, but I am hoping that the WMF boffins will be able to rectify the issue. Once they do, I will edit only under that name in future
. It sounds like you'd be okay with such a restriction. And, of course, you could always do so under a new account name even if you were unable to regain access to SchroCat. I think, as many others have pointed out here, there are other problems with your conduct which necessitate a CBAN. But this would help allay some concerns. — Shibbolethink (♔ ♕) 16:25, 14 December 2022 (UTC)- I'm glad to see that SchroCat commits to editing from their account if they can get access to it. But, of course, there's nothing preventing that from editing at any time from, for instance, "SchroCat2", "SchroCat too", "SchroCat again", "SchroCat returned", "SchroCat redux" or another other new account. Further, returning to editing from an account, while preferable, does not sove the problem of their behavior towrds other editors while editing as an IP. Beyond My Ken (talk) 20:33, 14 December 2022 (UTC)
- User:Beyond SchroCat is available. Levivich (talk) 20:36, 14 December 2022 (UTC)
- Somehow I doubt they'd be interested in that one. Beyond My Ken (talk) 20:38, 14 December 2022 (UTC)
- dibs Dumuzid (talk) 20:41, 14 December 2022 (UTC)
- User:Schrödinger's Cat exists, but only has two insubstantial edits 16 years ago, so could probably be usurped. Bishonen | tålk 22:52, 14 December 2022 (UTC).
- dibs Dumuzid (talk) 20:41, 14 December 2022 (UTC)
- Somehow I doubt they'd be interested in that one. Beyond My Ken (talk) 20:38, 14 December 2022 (UTC)
- User:Beyond SchroCat is available. Levivich (talk) 20:36, 14 December 2022 (UTC)
- I'm glad to see that SchroCat commits to editing from their account if they can get access to it. But, of course, there's nothing preventing that from editing at any time from, for instance, "SchroCat2", "SchroCat too", "SchroCat again", "SchroCat returned", "SchroCat redux" or another other new account. Further, returning to editing from an account, while preferable, does not sove the problem of their behavior towrds other editors while editing as an IP. Beyond My Ken (talk) 20:33, 14 December 2022 (UTC)
- "Light occasional editing", but you also claimed that you wrote an FA as an IP? Those aren't even in the same league. casualdejekyll 19:45, 15 December 2022 (UTC)
- In fairness, he only wrote it once, and digital files weigh nothing at all. (Pay no attention to the other hundreds of edits from the last six months.) Levivich (talk) 19:49, 15 December 2022 (UTC)
- So, wait, are you saying you would or wouldn't comply with such a restriction? Above, you said:
- Rather pointless. I have never logged out of an account specifically to edit as an IP except; I gave up my account to leave before deciding to do some light occasional editing as an IP (which is a legitimate course to take). As to "one name" editing, you'll find ArbCom got there before you 2A00:23C7:2B86:9801:1E8:2D44:8B40:EBA5 (talk) 16:22, 14 December 2022 (UTC)
- @Ian Rose: Would you support an editing restriction to stay logged-in and under one account? — Shibbolethink (♔ ♕) 16:11, 14 December 2022 (UTC)
- Oppose if and only if SchroCat returns to editing under a single account (as he has stated he will). I don't think there is enough here to warrant a CBAN, but certainly he should stop editing from IPs that have the effect of avoiding scrutiny, even if that isn't his intention.-- Pawnkingthree (talk) 16:57, 14 December 2022 (UTC)
- Oppose What a waste of time this is. I wish SchroCat would restore his account and return to editing here but it's up to him what he does.♦ Dr. Blofeld 17:18, 14 December 2022 (UTC)
- Oppose sanctions. I agree with Boing here, especially per ScroCat's unequivocal undertaking a little higher up in the thread to edit only from their own account once they're able to access it. Bishonen | tålk 18:07, 14 December 2022 (UTC).
- Just to point out the obvious, SchroCat returning to editing from their account does not solve the problem of their behavior towards other editors while they have been editing using IPs, which is really the core of this CBan proposal. Beyond My Ken (talk) 20:33, 14 December 2022 (UTC)
- Oppose per Boing, Dr. Blofield, Bishonen, et al. Jip Orlando (talk) 19:38, 14 December 2022 (UTC)
- Oppose site ban. I do see some of the behavior highlighted here as unfairly aggressive and unnecesssarily confrontational, but not to an extent that justifies banning "the person behind these IP ranges (and User:SchroCat) from editing the English Wikipedia". Nowhere near, not even close, in my view (I'll admit that it takes a lot for me to wish seeing a fellow editor site-banned. I believe this is the only site ban I've ever supported actively). ---Sluzzelin talk 21:12, 14 December 2022 (UTC)
SupposeSupport - Reading over the years of behavior issues it is clear they are a net negative. Them being logged out at the time really has no bearing on this situation, nor does them saying that they will only edit under their main account. That misses the large body of evidence against them, and frankly their statements here do nothing to alleviate the concerns brought up here. In fact if their only take away from this is they should not edit as an IP then they are completely missing the point. They have wasted the communities time enough. PackMecEng (talk) 01:14, 15 December 2022 (UTC)
- "Suppose"? is that mixture of "Support" & "Oppose"? GoodDay (talk) 01:30, 15 December 2022 (UTC)
- Ha, not so much. Thanks for the catch. PackMecEng (talk) 01:52, 15 December 2022 (UTC)
- "Suppose"? is that mixture of "Support" & "Oppose"? GoodDay (talk) 01:30, 15 December 2022 (UTC)
- Oppose per WP:PURPOSE, and the peer reviews, rfa noms, and articles i sampled. fiveby(zero) 01:58, 16 December 2022 (UTC)
- @Fiveby: I'm glad you did some research, but, may I ask, what do those things have to do with SchroCat's behavior which has been reported here and which is the reason for the existence of this CBan survey? Beyond My Ken (talk) 05:01, 16 December 2022 (UTC)
- I don't think that which has been reported here really warrants the existince of this CBan survey. I see in what i read a great deal of effort towards sticking up for article quality and doing so in a collaborative manner, and in the recent interactions there was still some effort at collaboration on content. Sometimes it is difficult to be a fan of Wikipedia, but for that work i read and wasn't aware of then sure sign me up for the "club". Really i just wanted to see if someone would write the Linnemann spade article and then you told me to vote. fiveby(zero) 07:45, 16 December 2022 (UTC)
- I'm sorry, I'm probably totally dense, but your "explanation" is totally imcomprehensible to me, and I suggest that if this proposal is ever closed, the closer should ignore your !vote as it has nothing whatsoever to do with policy, as far as I can see. Beyond My Ken (talk) 10:24, 16 December 2022 (UTC)
- Comment A lot of opposes above seem to suggest there is no issue editing as an IP. In many cases that is true, but to have an IP claim to be an account is problematic, and especially problematic when it is from an account which has declared themselves retired and thus is unlikely to log in to confirm. Imitation and joe job opportunities abound, so declaring yourself retired and then editing from IPs should be considered deeply disruptive and not a legitimate use of IP editing. CMD (talk) 11:34, 16 December 2022 (UTC)
- Oppose per Boing. I'm not seeing anything here that warrants an AN thread. Blocking a highly productive editor simply does our Wikipedia readers a disservice. –Davey2010Talk 16:53, 16 December 2022 (UTC)
- Oppose. SchroCat has logged in/found their password, so that's one problem out of the way. They were and still are a productive editor, and while I am no fan of editing while logged out, we're making too much out of it. We should close this and move on, and future ... disturbances can be handled on a case by case basis. Drmies (talk) 22:02, 16 December 2022 (UTC)
- Oppose ban SchroCat is a great editor, and I believe he's here to build an encyclopedia. As it appears that he's returned to his old account, I oppose a CBAN if he pledges to avoid IP edits. ~ HAL333 01:48, 17 December 2022 (UTC)
Discussion re: proposal
edit- Pinging @Ritchie333, @Bradv, @GoldenRing, @Euryalus, @Bbb23, @Mike V, @Doc James, @MSGJ, @HJ Mitchell, @Lord Roem, @King of Hearts, @JBW as current/former admins who were previously involved in some of these blocks/unblocks. — Shibbolethink (♔ ♕) 18:51, 11 December 2022 (UTC) Pinging other users/admins involved in prior disputes/blocks/unblocks/appeals from the various ranges listed above: @Black Kite, @Serial Number 54129, @Sro23, @Blablubbs, @El C, @RoySmith, @A. C. Santacruz @Firefangledfeathers @Ceoil @George Ho @Spicy @DatGuy because I'm honestly not actually 100% those past ranges (not included in this report but mentioned: [199][200]
[17]) are this user (although I suspect they are) and would like input from the original folks involved in those disputes/admin actions/SPIs.— Shibbolethink (♔ ♕) 17:37, 12 December 2022 (UTC) (edited to remove range that probably wasn't SchroCat)
Whilst making no comment on the rights and wrongs of the arguments in relation to this block proposal, assuming it is SchroCat surely a CBAN would be preferred if action is felt to be required here rather than a block, which would be ineffective as the user could make a fair argument that they're eligible to clean start as they're not subject to any active community sanctions/active blocks on their primary account? Whilst I won't actively support as I've not got enough familiarity with the wider situation here, I just think that considering they've attempted clean starts before a block without accompanying ban would be sending the wrong message, if the community does support this proposal. Mike1901 (talk) 18:54, 11 December 2022 (UTC)
- Agreed, I've converted to a CBAN proposal — Shibbolethink (♔ ♕) 18:57, 11 December 2022 (UTC)
I need undisputed proof, that the IPs are SchroCat & not somebody impersonating him, to get his registered account banned. GoodDay (talk) 19:36, 11 December 2022 (UTC)
- See my talk page. Says it all really. Mattdaviesfsic (talk) 19:38, 11 December 2022 (UTC)
- If someone has gone to all this trouble to impersonate SchroCat to get him banned it will be one of the most amazing things I've seen on Wikipedia. Nemov (talk) 19:39, 11 December 2022 (UTC)
- Regrettable, that he's letting himself be destroyed :( GoodDay (talk) 20:05, 11 December 2022 (UTC)
- If it weren't SchroCat, all they'd really need to do to get that USERNAME unbanned would be to start a community unban request with a CU privately verifying that they do not have a long history of editing in that IP range while logged in to the account. As far as I know, there's only a prohibition on publicly connecting users and IPs, not differentiating them. CU's please correct me if I'm wrong on this. I don't think there's any precedent on that, or I don't know of any, but I don't think that automatically extends to saying, in effect, "this user is not those IPs". Importantly, as @KrakatoaKatie describes above, the IP range has waived the right to being identified as "not SchroCat" by claiming all the time that they are SchroCat. — Shibbolethink (♔ ♕) 20:10, 11 December 2022 (UTC)
- I think there's a way to get Wikipedia administrators to wipe clean your password, so you can create a new one & sign in. GoodDay (talk) 20:13, 11 December 2022 (UTC)
- I do not believe that is the case. Beyond My Ken (talk) 23:09, 11 December 2022 (UTC)
- I think, as User:Mackensen said, SchroCat can actually reset the password since they very likely have access to the email address connected to the account (and probably get emails every time we mention them, come to think of it). All of this is somewhat moot since the IP ranges have said they edit anonymously intentionally, and see nothing wrong with it. — Shibbolethink (♔ ♕) 23:11, 11 December 2022 (UTC)
- I do not believe that is the case. Beyond My Ken (talk) 23:09, 11 December 2022 (UTC)
Though it had no effect on my decision to support a CB. Any editor (signed in or not) isn't going to impress me anymore, with their FA/GA, this A or that A record boasting. GoodDay (talk) 20:17, 11 December 2022 (UTC)
@Rhododendrites:Then he sorta-kinda "retired" a couple years ago and things have been quieter
I understand your hesitance here. I hate CBANs. I have personally maybe proposed one I can think of, and participated in one or two others. It's drastic. It should be done only with great care and attention paid to not misfiring or causing collateral damage.I think what really swayed me towards writing this as a proposal (and supporting it) was Levivich's stats showing this IP range has been basically editing every single day since May 2022. In a way other folks who have dealt with SC before have said is exactly SchroCat's modus operandi. And on other ranges prior to that even, if we went deep into the histories of these articles. My thinking here is: It's probably been quiet because no one's been paying attention to what IPs are doing, because that's basically how it always works on Wikipedia. No one has been connecting the dots, or starting RFCs that SchroCat hated enough to start concerted efforts to harass other users. In effect, it's quiet because they were skating by as anonymous IPs. But, as in most things around here, it is your opinion and I respect it (and your right to disagree) greatly. — Shibbolethink (♔ ♕) 20:16, 11 December 2022 (UTC)
- I'm not convinced that editing from an IP (through which he identifies his registered account) is grounds for a cban. I'm not even convinced it's against any of our policies. What would the difference be if he lost his password instead of retired, then started editing from an IP? Like I said, it comes off as petulant, but CBANs are too much for petulance. I'd want to see more and/or more egregious evidence of problems from those IPs -- evidence that deeply problematic abusive behavior didn't actually stop when he "retired". That there might've been problems but people weren't paying attention isn't IMO sufficient (speculation, after all). — Rhododendrites talk \\ 20:23, 11 December 2022 (UTC)
- (edit conflict) Rhododendrites, you should note that while a list of edits from an IP range has been produced, these are certainly not all me. They are from users of BT in London. Yes, a number are mine (especially over the last couple of weeks), but a significant portion are not me.It used to be that if an editor inferred another editor was delusional, that would lead to sanctions on the person making that personal attack. Nowadays, it seems that is no longer the case. Some changes are rather sad. - 2A00:23C7:2B86:9801:799C:B97D:4044:790A (talk) 20:30, 11 December 2022 (UTC)
- It's entirely up to you to edit from an IP. The identity of the person/people making edits is not our problem, in all honesty. The attitude of the problem editor is. That's the point of this proposal. Mattdaviesfsic (talk) 20:33, 11 December 2022 (UTC)
- You missed the point, but never mind. 2A00:23C7:2B86:9801:799C:B97D:4044:790A (talk) 20:43, 11 December 2022 (UTC)
- Which of the example diffs of disruptive editing in this proposal are not your edits? Levivich (talk) 20:40, 11 December 2022 (UTC)
- Your blanket search of edits undertaken under an IP range. There’s a hefty proportion that are not mine. 2A00:23C7:2B86:9801:799C:B97D:4044:790A (talk) 20:43, 11 December 2022 (UTC)
- Doesn't really answer the question. Any in particular? Mattdaviesfsic (talk) 20:48, 11 December 2022 (UTC)
- Your blanket search of edits undertaken under an IP range. There’s a hefty proportion that are not mine. 2A00:23C7:2B86:9801:799C:B97D:4044:790A (talk) 20:43, 11 December 2022 (UTC)
- It's entirely up to you to edit from an IP. The identity of the person/people making edits is not our problem, in all honesty. The attitude of the problem editor is. That's the point of this proposal. Mattdaviesfsic (talk) 20:33, 11 December 2022 (UTC)
- I guess what I'd ask is: how many edit wars and bitter disputes with various people would it take? Just looking back in the IP history, the user self-identifies either before or after engaging in several edit wars on articles near and dear to SchroCat's heart. (see below "9800" for example) This is a long-standing thing that has run under the radar given the fact that it's all IPs and nobody noticed. — Shibbolethink (♔ ♕) 21:18, 11 December 2022 (UTC)
- I'd ask two questions in return, Shibbolethink. Why do you feel that expending so much time and energy (over 200 edits so far) to get an editor banned is beneficial to the encyclopaedia, and why do you bother editing here when your interest is clearly not in adding sourced content to the encyclopaedia? What would we stand to lose from you if you were banned? HJ Mitchell | Penny for your thoughts? 22:11, 12 December 2022 (UTC)
- Harry, that's saying the quiet part out loud, and I generally don't advise doing that. Mackensen (talk) 22:49, 12 December 2022 (UTC)
- I'd say it's worse than that. Call it shooting the messenger. Call it a deliberate attempt to create a chilling affect. Whatever anyone wants to call it, it's unacceptable coming from anyone, let alone an admin. LEPRICAVARK (talk) 23:06, 12 December 2022 (UTC)
- I call it bullying or attempted character assassination. It's ugly and inappropriate for anyone anywhere, but especially for an admin on an admin noticeboard. Levivich (talk) 00:46, 13 December 2022 (UTC)
- I'd say it's worse than that. Call it shooting the messenger. Call it a deliberate attempt to create a chilling affect. Whatever anyone wants to call it, it's unacceptable coming from anyone, let alone an admin. LEPRICAVARK (talk) 23:06, 12 December 2022 (UTC)
- @HJ Mitchell: happy to answer your Qs:
Why do you feel that expending so much time and energy (over 200 edits so far) to get an editor banned is beneficial to the encyclopaedia
Hi, I answer this in extreme detail below: [201]. Part of it, btw, is that I make lots and lots of tiny edits, instead of few large edits. So edit number is probably not the best way to examine my contributions in general. But that's beside the point. I did put a lot of work into this. You're right, and I don't apologize for that. More than anything, this user has spent the last year as an anon getting into bitter heated disputes, preventing others from changing any of their favorite articles in various minor ways, and contributing some to the project. They have made a lot fewer actual FAs/GAs etc than in the past, they admit this below. But I don't think their conduct was be totally fine even if they had created 1000s of FAs. It doesn't excuse their behavior.why do you bother editing here when your interest is clearly not in adding sourced content to the encyclopaedia?
If you believe I'm WP:NOTHERE, feel free to bring me to ANI/AE/AN, I'll happily respond in that instance. Until then, please don't cast unnecessary WP:ASPERSIONS or personally attack me, thanks.What would we stand to lose from you if you were banned?
My behavior isn't at issue, here. It also isn't one or the other. It's not as though banning me would somehow make SchroCat start collaborating and being a great person to interact with. As I say below, I only wrote this proposal because many other editors have taken issue with SchroCat's behavior. That's why they've gotten blocked like 7 times I can count (probably more, if we count the ranges who are also probably that user that I detail below, getting up to 10 or 11 times). I'd like to point out, I have never gotten blocked, not once, in 8 years. It's truly not hard to not get blocked. SchroCat has not just made zero effort to avoid getting blocked, they have actually gotten worse over time. You should examine the net total of the ways SchroCat affects the project and its collaborative culture, the ways they prevent others from editing articles in any way, etc. It's not as though I'm the only one concerned here. Thanks. — Shibbolethink (♔ ♕) 22:51, 12 December 2022 (UTC)- You, a non-admin (who spends very little time in the mainspace) have made more edits to the admin's noticeboard in the last 48 hours than I (an admin) have in the last five years which is an unusual dedication to getting one person banned. And if you think anything I wrote was a personal attack or an aspersion then you are everything that is wrong with this thread and you have no business editing the project space. Go and research and write an FA. Spend two months having your thousands of words picked apart only to have somebody who learnt everything they know about the subject from your article tell you you did it wrong. Then tell me that doesn't frustrate you just a little bit and you didn't have to take a deep breath before responding. HJ Mitchell | Penny for your thoughts? 23:19, 12 December 2022 (UTC)
Spend two months having your thousands of words picked apart only to have somebody who learnt everything they know about the subject from your article tell you you did it wrong.
I spend most of my time on wiki editing medical articles, especially infectious disease stuff (an area I have a PhD in), so yes, I understand how frustrating it can be to have non-experts tell you you're wrong, or you need better cites, or your phrasing is incorrect, when you literally have spent years of your life researching something in extreme detail. I've also done this with my patients, with whom I've had long conversations about vaccines and other such things. I've had patients tell me I'm a government shill, that I must be "gay for Fauci", that I drink children's blood. I've had patients tell me I must be getting paid by pharma to get them to take their diabetes medication. But you know what? I still manage somehow to not raise my voice with them, and convince them to do the things that keep them alive. That's also one terrible thing about peer review in academia, that people who are really experts in something totally different in your field tell you how you're wrong over and over again and you have to figure out how to please them. Trust me, I know the feeling you're describing.But, you know what? I somehow manage to edit here without calling other people names, saying they stalk me, WP:OWNing articles, or edit warring, and again, I manage to do it without getting blocked. I don't even think it's that bad for users to slip up and get blocked sometimes. But 10 or 11 times? And getting in several other unnoticed edit wars? I also tend to give a lot of leeway to long term contributors who are dealing with disruptive editors. I absolutely think that's a fair thing to do. It's easy to get exasperated in such situations. But eventually, there's a point where it's unacceptable. — Shibbolethink (♔ ♕) 23:23, 12 December 2022 (UTC)Go and research and write
JoelleJay (talk) 04:26, 13 December 2022 (UTC)an FAa journal article. Spendtwo>8 months having your thousands of words picked apart only to havesomebodya reviewer who learnt everything they know about the subject from your article tell you you did it wrong.- Precisely. You've spent months or years working on something. You have an emotional attachment to it. Now imagine your reviewer is me, somebody with no scientific background, and I'm adamant that your placement of a comma is wrong, for example. But from your perspective it reads fine as it is and my change alters the meaning of a crucial sentence. You would be a little bit annoyed. That, of course, would not excuse you losing your temper but you would be entitled to some sympathy if somebody then proposed to ban you. HJ Mitchell | Penny for your thoughts? 17:44, 13 December 2022 (UTC)
- Considering you posted
What would we stand to lose from you if you were banned?
to Shibbolethink earlier, that's quite the double-standard on your part. You're expending a lot of effort to intimidate and excoriate a user here, when you yourself admit you rarely spend time on this board. It does not reflect well on you. — The Hand That Feeds You:Bite 20:29, 13 December 2022 (UTC) - My comment was simply pointing out how ridiculous it is to suggest that someone who has published multiple biomedical papers in high-profile journals needs to go through the FA process to understand the frustrations of peer review. Not that you would need to have any writing experience to empathize with someone who was threatened with a ban merely for being grumpy occasionally about others changing wording on their FAs. But that's also obviously not a faithful digest of the conflict here. JoelleJay (talk) 00:27, 14 December 2022 (UTC)
- In reality, if someone became abusive with a reviewer of an academic journal, I'm fairly sure there's a good chance they would be banned from making any submissions to the journal, possibly for a very long time. If they continued to be abusive years later, they'd find themselves in even deeper trouble, possibly under investigation from any institutions they worked for or are associated with. They'd have receive very little sympathy from anyone involved. Any other authors of the original paper, even if they also felt the criticism was unfair would likely be extremely pissed off at this person way more than they were with the reviewer. There's a fair chance they'd never work with them again. I don't think comparing the situation here to academic review of a journal submission is particularly comparable even if this does show how silly User:HJ Mitchell's comparison is. Nil Einne (talk) 05:40, 14 December 2022 (UTC)
- Considering you posted
- Precisely. You've spent months or years working on something. You have an emotional attachment to it. Now imagine your reviewer is me, somebody with no scientific background, and I'm adamant that your placement of a comma is wrong, for example. But from your perspective it reads fine as it is and my change alters the meaning of a crucial sentence. You would be a little bit annoyed. That, of course, would not excuse you losing your temper but you would be entitled to some sympathy if somebody then proposed to ban you. HJ Mitchell | Penny for your thoughts? 17:44, 13 December 2022 (UTC)
- This is shockingly condescending, bad-faith, and intentionally chilling. Can another admin please deal with this appalling behavior? 67.80.122.184 (talk) 01:10, 13 December 2022 (UTC)
- I guess I am
everything that is wrong with this thread and [] have no business editing the project space
. Good to know where I stand, at least. Dumuzid (talk) 02:06, 13 December 2022 (UTC)- Likewise. I guess it's okay to make personal attacks as long as you do so in the context of insulting people for daring to think you had previously made personal attacks. But it's hardly surprising to see a user with a lot of FAs belittling someone who doesn't meet his standards. LEPRICAVARK (talk) 03:24, 13 December 2022 (UTC)
- @HJ Mitchell: FWIW I've edited with Shibbolethink in the past and at that time primarily saw them in the mainspace, with a good understanding of sources and immensely helpful in resolving intricate content disputes on medical content. Not that any of this is really relevant to the discussion IMO, but I'm not sure your analysis on Shibbolethink's editing contributions is accurate. ProcrastinatingReader (talk) 21:09, 13 December 2022 (UTC)
- Yeah I've seen Shibbolethink around a lot and they are very helpful and an incredible asset to Wikipedia including mainspace. I have not seen
anymany such contributions from HJ Mitchell. I strongly suspect HJ Mitchell does contribute incredibly productively probably way more than me, but if I was to go solely by my own experience HJ Mitchell does not contributive productively but Shibbolethink does. This is why we should be very wary about casting aspertions on another editor's track record without careful analysis of said track record. Nil Einne (talk) 05:40, 14 December 2022 (UTC)- Sorry a poor wording on my part. I said any, should have said many. I've seen HJ Mitchell occasionally. I can't recall exactly where or what they were doing but I'm sure most of those I did see were were productive and either in mainspace or related directly to mainspace. However it still pales significantly by comparison with the productive edits I've seen from Shibbolethink as others have said especially for medical content and for past nearly 3 years now this has often meant COVID-19 related stuff. Again I'm not intending to compare their respective histories since I have not done any analysis. I'm just illustrating with it's a terrible idea to make such comparisons without having done a proper analysis. As further illustrated by the several editors who have defended Shibbolethink's editing history in response to HJ Mitchell's indeed ill-conveived and evidence free accusation. Nil Einne (talk) 06:48, 14 December 2022 (UTC)
- Yeah I've seen Shibbolethink around a lot and they are very helpful and an incredible asset to Wikipedia including mainspace. I have not seen
- You, a non-admin (who spends very little time in the mainspace) have made more edits to the admin's noticeboard in the last 48 hours than I (an admin) have in the last five years which is an unusual dedication to getting one person banned. And if you think anything I wrote was a personal attack or an aspersion then you are everything that is wrong with this thread and you have no business editing the project space. Go and research and write an FA. Spend two months having your thousands of words picked apart only to have somebody who learnt everything they know about the subject from your article tell you you did it wrong. Then tell me that doesn't frustrate you just a little bit and you didn't have to take a deep breath before responding. HJ Mitchell | Penny for your thoughts? 23:19, 12 December 2022 (UTC)
- What an appalling, ill-conceived, evidence-free accusation by HJ Mitchell about a top WP:MEDRS editor with an impeccable record, clean block log, 500 mainspace edits in the last two weeks, 10k article edits in the last twelve months, and a highly respected contributor at the WP:WikiProject Medicine board. What have you been smoking, to get this so wrong?
- The only way I can account for your comments, coming from a respected admin, is that you've been a bit over-subscribed (I get it), you assumed there must be some he-said, she-said, or some balance needed, and you thought providing some pushback on what seemed too lopsided a tally with too few admins involved to establish some "balance" would be a good idea. Unfortunately, you didn't do your homework.
- I can tell you why they have 200 edits here: it's because like any scientist, once Shibbolethink decides to participate in some piece of research, then they are all in: doing all the research, exposing all the data, and being completely transparent about data that either supports or challenges any prior impression they may have had, as well as entertaining any well-founded comments about data or methodology.
- Finally their 200 edits are not "to get an editor banned", but rather to lay out the data to the community, like any scientist publishing a paper for their peers, and let the paper stand or fall on its own merits. Like any author of a published scientific paper, this doesn't preclude the author from drawing a conclusion when the data merits, and they have done so, perfectly in line with scientific publishing, here intended for the community audience at WP:ANI to read and either ignore, thumbs-up, or thumbs-down.
- If you knew the first thing about Shibbolethink, or had spent minimal effort (say, a dilettante-sized scoop, not a scientist-size in-depth one) looking into his contributions and history, you would have discovered this for yourself. It's regrettable that you did not. Mathglot (talk) 03:39, 13 December 2022 (UTC)
- I have mot levelled any accusations. You clearly haven't read what I wrote. The rest of your comment is simply playing with semantics. One of the accusations levelled against SchroCat is that he has a persecution complex. Another is that he is bludgeoning discussions. I would think I was being harassed if somebody put that much time and effort into arguing with me on talk pages and advocating banning me on a noticeboard; most reasonable people would. And if this isn't a textbook case of bludgeoning then I've been discussing and sdminning wrong for the best part of a decade and a half. HJ Mitchell | Penny for your thoughts? 08:32, 13 December 2022 (UTC)
- But does he care about feeling harassed? SchroCat made those damaging/"Battleground" edits well before people noticed/brought it here. As Beyond My Ken says,
SchroCat is essentially giving the community the middle finger
. That's what this boils down to, not if he actually cares (which he very clearly doesn't). Mattdaviesfsic (talk) 08:44, 13 December 2022 (UTC)
- But does he care about feeling harassed? SchroCat made those damaging/"Battleground" edits well before people noticed/brought it here. As Beyond My Ken says,
- I have mot levelled any accusations. You clearly haven't read what I wrote. The rest of your comment is simply playing with semantics. One of the accusations levelled against SchroCat is that he has a persecution complex. Another is that he is bludgeoning discussions. I would think I was being harassed if somebody put that much time and effort into arguing with me on talk pages and advocating banning me on a noticeboard; most reasonable people would. And if this isn't a textbook case of bludgeoning then I've been discussing and sdminning wrong for the best part of a decade and a half. HJ Mitchell | Penny for your thoughts? 08:32, 13 December 2022 (UTC)
- Harry, that's saying the quiet part out loud, and I generally don't advise doing that. Mackensen (talk) 22:49, 12 December 2022 (UTC)
- I'd ask two questions in return, Shibbolethink. Why do you feel that expending so much time and energy (over 200 edits so far) to get an editor banned is beneficial to the encyclopaedia, and why do you bother editing here when your interest is clearly not in adding sourced content to the encyclopaedia? What would we stand to lose from you if you were banned? HJ Mitchell | Penny for your thoughts? 22:11, 12 December 2022 (UTC)
- (edit conflict) Rhododendrites, you should note that while a list of edits from an IP range has been produced, these are certainly not all me. They are from users of BT in London. Yes, a number are mine (especially over the last couple of weeks), but a significant portion are not me.It used to be that if an editor inferred another editor was delusional, that would lead to sanctions on the person making that personal attack. Nowadays, it seems that is no longer the case. Some changes are rather sad. - 2A00:23C7:2B86:9801:799C:B97D:4044:790A (talk) 20:30, 11 December 2022 (UTC)
- The editors who began (in concert) this AN action against SchroCat often disagree with him at infobox disputes (including at least two current ones), and so they wish to get him banned. -- Ssilvers (talk) 21:53, 12 December 2022 (UTC)
- Do you have any evidence that this is some kind of coordinated hit? LEPRICAVARK (talk) 22:03, 12 December 2022 (UTC)
- I would tell you, @Ssilvers, I actually actively tried to discourage other users from bringing this here to AN [202], for exactly this reason. It becomes a giant cluster-F, and people question you every other way, assume you're acting in bad faith, etc. I'm quite certain my behavior will be hyper-examined with a magnifying glass for months after this, by SchroCat's advocates. I hate bringing things to AN/ANI. I tried to discourage this because I wanted it to be a better case. But if it's here, I'm not going to hold back. And it turns out lots of other people have problems with this person's behavior, and it's a pretty clear cut situation all things considered. So I'm glad they did. — Shibbolethink (♔ ♕) 23:00, 12 December 2022 (UTC)
Other ranges not included in this proposal to keep an eye on moving forward
edit2A00:23C7:2B86:9800
2A00:23C7:2B86:9800:0:0:0:0/64 (talk · contribs · deleted contribs · page moves · block user · block log)
I noticed there's an extremely close range just outside of this /64 that has some problematic behavior similar to what's described here:
- disagreements with anyone who wanted to fix comma splices or unclear phrasings over at Talk:Moorgate tube crash (see here) and this edit war over "theories" vs "hypotheses": [203][204][205][206][207]
- not following BRD for others attempting to improve the style at Operation Mincemeat [208][209] [210]
- personal attacks, not following BRD while telling others to follow BRD [211]
- calling good faith edits vandalism [212]
- edit warring to keep out good faith edits and editors concerned about the length of a lead [213][214][215][216][217]
- edit warring to keep preferred version of infobox at Fight Club [218] [219] [220] [221] [222] and then aggressively blanking attempts to talk about it [223]
This "9800" range edits right up until May 2022, which is when @Levivich identified this current "9801" /64 as starting. I don't think we should include it here, because, as mentioned, it hasn't done anything since May and I think we should minimize any and all collateral damage. But I would emphasize: it's important to keep an eye on these similar ranges. — Shibbolethink (♔ ♕) 20:44, 11 December 2022 (UTC) (edited 23:35, 11 December 2022 (UTC) only to add missing links and fix typos, not for any significant changes to arguments or content thereof)
2A00:23C7:2B89:BE00
2A00:23C7:2B89:BE00:0:0:0:0/64 (talk · contribs · deleted contribs · page moves · block user · block log)
This range has a very similar style to SchroCat, but I'm not 100% it's all them. They do have a pretty long block history, though, escalating up to 6 months in June 2021 for disruptive editing. They also frequent many of the same places, e.g. Ken "Snakehips" Johnson, ARCA, User talk:SchroCat, Wikipedia:In the news and Wikipedia:In the news/Candidates. As I said above, I don't think we should block these ranges, given the age of the contribs, and our interest in reducing collateral damage. But I think we need to keep an eye on them. Especially since SchroCat has admitted in the past that they reset their router, etc. to game blocks. [224][225]— Shibbolethink (♔ ♕) 17:48, 12 December 2022 (UTC)
Probably not SchroCat
|
---|
2001:4451:8124:4900 2001:4451:8124:4900:0:0:0:0/64 (talk · contribs · deleted contribs · page moves · block user · block log) This one as well, very few edits, but edited User talk:SchroCat and has a /32 block stretching ALREADY into March 2023. Unclear if connected to SchroCat, though, since a /32 is way way way more addresses than the previously mentioned /64, and it doesn't look like the /64 was involved in the /32 block. I think this is probably a different person (looks to be a pro-trump troll) who was harassing SchroCat. I leave these particular things up to the admins.— Shibbolethink (♔ ♕) 17:48, 12 December 2022 (UTC) |
86.155.193.0/24
86.155.193.0/24 (talk · contribs · deleted contribs · page moves · block user · block log)
Contributions from SchroCat in the above thread.— Shibbolethink (♔ ♕) 19:08, 14 December 2022 (UTC)
Probably not SchroCat given that the telecom is Sky
|
---|
2A02:C7C:A400:EF00/60 2A02:C7C:A400:EF00:0:0:0:0/60 (talk · contribs · deleted contribs · page moves · block user · block log)
|
requeset to use a different userlinks template
|
---|
|
digression re: above-board connections to User:Tim riley as an IRL friend; Tim riley confirms the IP ranges are indeed User:SchroCat
|
---|
|
On a point of accuracy, the former SchroCat has to my certain knowledge at least one new FA to add to his impressive total since he renounced his user-name. It was something we had worked on together and I took successfully to FAC in July. I think it would be barmy of Wikipedia to prevent further such FAs because some users have a gripe against our colleague. Tim riley talk 00:05, 12 December 2022 (UTC)
- Oh yes, I’d forgotten about that one! According to Beyond My Ken, I’ve been “too busy edit warring, attacking other editors”, etc to do anything like that, but this is AN, where anything goes. Anyway, I’m on leave from tomorrow morning, so TTFN. - 2A00:23C7:2B86:9801:6486:7533:98F3:7C9F (talk) 00:10, 12 December 2022 (UTC)
- Editors who are excellent content creators, such as yourself, get a lot of behavioral leeway. Maybe it shouldn't be that way, maybe it's appropriate, but we're not going to settle that here. Instead, we're wrestling with the question of whether you have finally reached the limit which the community is willing to put up with, even for an editor of your quality. You've been here a long time, as have I, and we've both seen excellent content editors push the envelope until the community finally banned them or they got indeffed by an admin. That's where we are now, and your appeals to your excellence as a content creator are really beside the point. I don't see anyone here denying the quality of your career output, they're protesting about the lack of quality in your behavior, which you've done nothing to explain or excuse, just outright denied that it happened. That simply won't fly, the evidence is there and it won't go away. Beyond My Ken (talk) 00:29, 12 December 2022 (UTC)
BTW, FWIW, this says that the SchroCat account created 89 articles excluding redirects, and that 24 of them are Featured Lists, 9 of them are Good Articles, and 1 is an FA. The rest are a mixture of everything from stubs up to Bs. This is the editor that Tim riley called "one of Wikipedia's most eminent editors ... [who] he has contributed so many FAs...", an "impressive total"? Beyond My Ken (talk) 00:51, 12 December 2022 (UTC)- Two different automated processes give vastly different numbers. See the IP's comment below.
- Before anyone jumps to make the comparison, no, none of the 232 undeleted articles I've created ([233],[234]) are FAs, and only one is a GA - but, then, I don't go around extolling my own virtues as a content creator. Beyond My Ken (talk) 00:58, 12 December 2022 (UTC)
- 9 GAs is nothing to scoff at, but it's also not an excuse for their behavior and Tim riley et al. seem to think it is. casualdejekyll 00:54, 12 December 2022 (UTC)
- Wikipedia:List_of_Wikipedians_by_featured_article_nominations: 58 FAs as SchroCat, 2 as The Bounder, one as an IP. I lost count of the number of GAs. 2A00:23C7:2B86:9801:6486:7533:98F3:7C9F (talk) 01:01, 12 December 2022 (UTC)
- Oh, and 47 FLs. Added 2A00:23C7:2B86:9801:6486:7533:98F3:7C9F (talk) 01:07, 12 December 2022 (UTC)
- I also have a bunch of FPs and an FT, which I’d forgotten, plus some DYKs and ITNs - I probably have more ITNs as an IP than I had as a regular editor, but these are all small change things really. Added 2A00:23C7:2B86:9801:6486:7533:98F3:7C9F (talk) 01:25, 12 December 2022 (UTC)
- 60 FAs is both nothing to scoff at and also not an excuse for the behavior. It could be 1000 FAs and I'd say the same thing. casualdejekyll 01:03, 12 December 2022 (UTC)
- I never claimed it was: I’m just correcting the misleading figures put out. 2A00:23C7:2B86:9801:6486:7533:98F3:7C9F (talk) 01:07, 12 December 2022 (UTC)
- Two different automated processes give vastly different results, so I've struck-through my comment above, since its accuracy is suspect. Beyond My Ken (talk) 02:01, 12 December 2022 (UTC)
- But I also note that the two processes are measuring different things. The stats I posted above are for articles created by SchroCat. The stats cited by SchroCat-as-IP (at least some of them) are for articles nominated for FA/GA by SchroCat and accepted.But, of course, Casualdejekyll is completely correct that the issue here is not the quality of SchroCat's content editing, but the quality of their behavior, especially as -- only partly identified -- IPs. Beyond My Ken (talk) 03:51, 12 December 2022 (UTC)
- I'm not sure what you're getting at, BMK. "Nominate" is one of those terms we use to diminish the value of our contributions on Wikipedia. Nominating an FA is not like nominating at RfA, for example, where you say your piece and back off. Nominatiors at FAC are expected to be major contributors to the article and must be familiar with the source material. In practice that means reading just about every word written on your chosen subject and becoming an expert on it. That's why FAs are so rare and why their writers should be given a lot of deference. Or should be if we're truly about writing an encyclopaedia. I'd be happy to mentor anyone reading this who wants to put the effort in to get their first FA. HJ Mitchell | Penny for your thoughts? 21:26, 12 December 2022 (UTC)
- I'm simply pointing out that the stats I originally cited were for article which were created by SchroCat, and the status they are currently in, while the stats cited by SchroCat are for article they actually brought to FA etc. and were accepted. I think that his stats are the more relevant ones, which is why I struck-through mine. Beyond My Ken (talk) 22:32, 12 December 2022 (UTC)
- I'm not sure what you're getting at, BMK. "Nominate" is one of those terms we use to diminish the value of our contributions on Wikipedia. Nominating an FA is not like nominating at RfA, for example, where you say your piece and back off. Nominatiors at FAC are expected to be major contributors to the article and must be familiar with the source material. In practice that means reading just about every word written on your chosen subject and becoming an expert on it. That's why FAs are so rare and why their writers should be given a lot of deference. Or should be if we're truly about writing an encyclopaedia. I'd be happy to mentor anyone reading this who wants to put the effort in to get their first FA. HJ Mitchell | Penny for your thoughts? 21:26, 12 December 2022 (UTC)
- But I also note that the two processes are measuring different things. The stats I posted above are for articles created by SchroCat. The stats cited by SchroCat-as-IP (at least some of them) are for articles nominated for FA/GA by SchroCat and accepted.But, of course, Casualdejekyll is completely correct that the issue here is not the quality of SchroCat's content editing, but the quality of their behavior, especially as -- only partly identified -- IPs. Beyond My Ken (talk) 03:51, 12 December 2022 (UTC)
- Two different automated processes give vastly different results, so I've struck-through my comment above, since its accuracy is suspect. Beyond My Ken (talk) 02:01, 12 December 2022 (UTC)
- I never claimed it was: I’m just correcting the misleading figures put out. 2A00:23C7:2B86:9801:6486:7533:98F3:7C9F (talk) 01:07, 12 December 2022 (UTC)
- 60 FAs is both nothing to scoff at and also not an excuse for the behavior. It could be 1000 FAs and I'd say the same thing. casualdejekyll 01:03, 12 December 2022 (UTC)
- Two different automated processes give vastly different numbers. See the IP's comment below.
- Editors who are excellent content creators, such as yourself, get a lot of behavioral leeway. Maybe it shouldn't be that way, maybe it's appropriate, but we're not going to settle that here. Instead, we're wrestling with the question of whether you have finally reached the limit which the community is willing to put up with, even for an editor of your quality. You've been here a long time, as have I, and we've both seen excellent content editors push the envelope until the community finally banned them or they got indeffed by an admin. That's where we are now, and your appeals to your excellence as a content creator are really beside the point. I don't see anyone here denying the quality of your career output, they're protesting about the lack of quality in your behavior, which you've done nothing to explain or excuse, just outright denied that it happened. That simply won't fly, the evidence is there and it won't go away. Beyond My Ken (talk) 00:29, 12 December 2022 (UTC)
- The editors who began (in concert) this AN action against SchroCat often disagree with him at infobox disputes (including at least two current ones), and so they wish to get him banned. -- Ssilvers (talk) 21:53, 12 December 2022 (UTC)
- I brought this here and have disagreed with you in the past. I don't want you banned. You seem to be a fine editor who is capable of giving your opinion without casting WP:ASPERSIONS. Do you have a specific defense of SchroCat's long history of accusing other editors of harassments, gaslighting, and stalking? This isn't a content dispute and I would hope an editor of your experience would recognize the difference. Thanks! Nemov (talk) 22:08, 12 December 2022 (UTC)
- Ssilvers wrote:
[They].. disagree with him [about infoboxes] and so they wish to get him banned.[emphasis added]
- Really? That is an accusation of bad faith retaliation on the part of those editors. If that is what you are alleging, then that is a serious matter, and you should raise this separately in a new section at ANI against the editors who brought this AN action against SchroCat, along with your evidence of same. If I misread you, and that is *not* what you meant, or if you've changed your mind, then you should indicate your disavowal of your previous statement by redacting it using <s>
strikeout type</s> to indicate the part that you recant. In blunter terms: put up, or shut up. Mathglot (talk) 02:51, 13 December 2022 (UTC)
A topic-ban from anything to do with adding/deleting infoboxes, might be another alternative. GoodDay (talk) 19:55, 14 December 2022 (UTC)
Ignoring approach
editIn the event that SchroCat & his IPs are not c-banned? There's another way to deal with his behaviour when it's deemed problematic, in infobox discussions. Ignore his posts & notify a closing RFC editor, to do the same. Denying recognition, has its advantages. GoodDay (talk) 21:37, 13 December 2022 (UTC)
- There are plenty of IP editors who make fine GF arguments. I'm not sure how we're supposed to carve out a problem users who uses multiple IPs. This behavior is just going to continue to cause problems. Probably more so if he's able to avoid getting banned this time. Who would want to raise the issue again after this? I'm kind of stunned that people are defending it. Nemov (talk) 21:50, 13 December 2022 (UTC)
- If I'm understanding many editors here, identifying SC's IPs isn't overly difficult. GoodDay (talk) 21:53, 13 December 2022 (UTC)
- Sure, if someone looks it up, but 6 months from now on some random discussion, newer editors (especially if they're not familiar with this case) won't know the identity of the IP user. Nemov (talk) 21:59, 13 December 2022 (UTC)
- Well, yes and no. Most sockpuppets/returning editors get caught because they can't help themselves--favorite articles/disputes, rhetorical style, users they don't like. I don't doubt there are banned users editing productively because they stopped doing the thing that got them banned and no one noticed them. The issue is that the way SchroCat edits creates conflict, whether anyone links that disruptive behavior to the main account or not. All the rhetoric from his supporters above doesn't change that fact, and doesn't offer a sustainable path forward. Mackensen (talk) 03:16, 14 December 2022 (UTC)
- If I'm understanding many editors here, identifying SC's IPs isn't overly difficult. GoodDay (talk) 21:53, 13 December 2022 (UTC)
- I would say, if the user is not CBANned, the correct approach would be to wait. See if this experience had any beneficial effect on the user, and attempt to collaborate as we always should in this project. If the user continues to be disruptive, display OWNership, cast ASPERSIONS, throw personal attacks, and edit war, or resumes this behavior in time, then the approach would be to go to WP:AE (if in infoboxes or another similar DS notice area), or return here to AN/ANI and show the behavior has not changed. Long-term abusers are given a lot of lattitude on this project, but there is a length, a pattern, and an unrepentance for which this community trust is no longer extended.And aside from that, it's still true that basically 2/3 of respondents believe the user should be CBANned. It hasn't been closed yet. — Shibbolethink (♔ ♕) 16:45, 14 December 2022 (UTC)
I'll give SchroCat or whoever's behind the IPs, some credit. They're smart enough not to annoy me, at those infobox keep/delete discussions. GoodDay (talk) 17:56, 15 December 2022 (UTC)
- Do you talk about anything else? 2A02:C7C:A400:EF00:3DE9:3F2:337:22BD (talk) 18:38, 15 December 2022 (UTC)
- Don't even (including here) try it. At best, you'll merely entertain me. GoodDay (talk) 18:40, 15 December 2022 (UTC)
Fan Club
editI guess I was unaware that SchroCat had a WP:FANCLUB willing to simply ignore his problematic behavior and also celebrating his returning. Embarrassing really, but I want to make it clear my issue here wasn't that he was editing as an IP user. His return to the original account doesn't solve a problem. The problem was the editor's behavior towards other editors. It doesn't matter that his edits are coming from an IP, the problem are the edits. SchroCat doesn't get a "get out jail free" care because they made unfounded accusations from an IP. Editors need to quit obfuscating the issue. SchroCat is a hostile editor who continually makes unfounded accusations towards other editors. That's all you need to know and the evidence in the edit history is overwhelming.
The editors blaming other editors for this behavior are disappointing. Favoritism blinds the ability to see clearly and that's it certainly happening after reviewing some of the arguments here. — Preceding unsigned comment added by Nemov (talk • contribs) 13:34, 14 December 2022 (UTC)
- Maybe there are "fans" who would excuse absolutely anything (and maybe a couple long-term grudges for whom the recent stuff doesn't even matter), but I suspect most of the rest of us who don't support a ban simply don't agree with you that there's enough justification for one. That doesn't mean SchroCat has been a model of prosocial behavior, but that we're being asked to assess whether we should issue the strongest sanction at our disposal, and the evidence just isn't sufficient. Wording of "WP:FANCLUB" aside, yes we absolutely do -- and should -- weigh contributions to the project when determining something like a CBAN. There are times that the same 5 edits that gets a brand new user indeffed are outweighed by 50,000 preceding good edits. The challenge is figuring out where that line is, and the reality is it varies by person. You don't have to be a fan of SchroCat to be a fan of high-quality article work, and to have a subjectively high bar for sanctions that would stop someone from producing that work. It's frustrating when people skirt the lines of acceptability for a long time, but thankfully it doesn't happen all that often. I wouldn't blame anyone for feeling like the bar for problems is too high when it comes to FA writers. There have been times I've felt that way myself, including, as I said above, with SchroCat. In this case, however, looking I think we're solidly on the "oppose" side of that line.
- Beyond that, there's also the extent to which infobox disputes are so fraught. There are people who view bad behavior coming out of those discussions in a different light because of the dynamics in play. I wish infoboxes weren't so triggering to SchroCat, et al., and I wish we didn't have people so quick to disregard the opinions of those who put hundreds of hours into building out articles when it comes to how best to present the information. Yes, you could reframe that and say "per WP:OWN, devoting you blood, sweat, and tears to a single article doesn't mean I shouldn't be able to drop in and have just as much influence in an RfC", and in many cases I'd agree. The issue is, with many cases we're dealing with things like NPOV, V, NOR, and other policies where consensus can be based on application/interpretation of policy. With infoboxes, there is no real policy guidance, and it's just personal preference in the guise of "what I think helps readers" or "why I think they make sense in X domain but not Y". For something that's about personal preference, surely you can see that someone who labored for a subject might be bothered by the fact that some people go from article to article contributing nothing to an article except to argue about an infobox when there's no policy-based rationale? Again, not saying people shouldn't be allowed to have a say, but I don't find it hard to empathize, or to understand why some see behavioral issues arising from infobox disputes in a different light. YMMV. — Rhododendrites talk \\ 15:50, 14 December 2022 (UTC)
- This isn't about infoboxes and I wish editors would quit hiding their bias behind this nebulous argument. This is an editor with a long history of hostility and an editor who continues to do it without fear from punishment because editors like yourself just make excuses for the behavior.
- We don't own anything on this project. Our job is simply to improve it with the help of the community. When you endorse an editor who doesn't respect other editors you in turn endorse disrespectful behavior. Nemov (talk) 16:03, 14 December 2022 (UTC)
- You seem to be falling into the same kind of behavior you're accusing SchroCat of, making accusations of bias and "fan clubs" and masking bad intentions using "nebulous arguments" and "endorsing disrespectful behavior" when I'm doing nothing of the sort. I don't have to endorse disrespectful behavior to decide that it's not disrespectful enough for a ban. A look through my editing history would reveal many times that I've been critical of people defending bad behavior just because of FAs. The difference is, in those cases, the behavior was worse. You're making accusations based on what you think my motivation is, when the reality is you just haven't made as good a case as you think you have. IMO. — Rhododendrites talk \\ 16:32, 14 December 2022 (UTC)
- My conscious is clear on this subject and I'm simply pointing out what should be obvious. As you admitted, SchroCat hasn't
been a model of prosocial behavior
. When a user has been banned in the past for this behavior and the behavior continues then it's on the editor to either acknowledge a long term problem or ignore it. It seems like you've made your choice. I don't know what your motivation is, but Wikipedia isn't a WP:BATTLEGROUND. WP:ASPERSIONS cannot be any clearer....It is unacceptable for an editor to routinely accuse others of misbehavior without reasonable cause.
If you can convince yourself SchroCat doesn't routinely do this then we're at an impasse. Nemov (talk) 16:58, 14 December 2022 (UTC)- Just FYI, I have never been banned. - 86.155.193.84 (talk) 17:20, 14 December 2022 (UTC)
- My mistake. I meant you've been blocked with cause 5-9 times? It's a chore combing through the wreckage. Nemov (talk) 17:57, 14 December 2022 (UTC)
- A block is not a ban. Please keep that in mind especially when you are citing WP:ASPERSIONS. You do little good for your case when you're not even sure of the accuracy of the facts you are citing. 🌈WaltCip-(talk) 18:07, 14 December 2022 (UTC)
- I already said "my mistake" but I appreciate your feedback. Nemov (talk) 18:21, 14 December 2022 (UTC)
- A block is not a ban. Please keep that in mind especially when you are citing WP:ASPERSIONS. You do little good for your case when you're not even sure of the accuracy of the facts you are citing. 🌈WaltCip-(talk) 18:07, 14 December 2022 (UTC)
- My mistake. I meant you've been blocked with cause 5-9 times? It's a chore combing through the wreckage. Nemov (talk) 17:57, 14 December 2022 (UTC)
- Just FYI, I have never been banned. - 86.155.193.84 (talk) 17:20, 14 December 2022 (UTC)
- My conscious is clear on this subject and I'm simply pointing out what should be obvious. As you admitted, SchroCat hasn't
- You seem to be falling into the same kind of behavior you're accusing SchroCat of, making accusations of bias and "fan clubs" and masking bad intentions using "nebulous arguments" and "endorsing disrespectful behavior" when I'm doing nothing of the sort. I don't have to endorse disrespectful behavior to decide that it's not disrespectful enough for a ban. A look through my editing history would reveal many times that I've been critical of people defending bad behavior just because of FAs. The difference is, in those cases, the behavior was worse. You're making accusations based on what you think my motivation is, when the reality is you just haven't made as good a case as you think you have. IMO. — Rhododendrites talk \\ 16:32, 14 December 2022 (UTC)
- Every one of these threads is Lynch Mob v. Fan Club. I believe those are the names of the WMF's softball teams. Levivich (talk) 16:00, 14 December 2022 (UTC)
- Hey, I'm just trying to use the softball field to play fetch with my dog. — Rhododendrites talk \\ 16:32, 14 December 2022 (UTC)
- Put me in coach! I'm ready to play! Jip Orlando (talk) 19:35, 14 December 2022 (UTC)
- Is this the equivalent of an Army–Navy Game? Dronebogus (talk) 03:13, 15 December 2022 (UTC)
Collapsing sideshow featuring thoroughly disruptive IP who is apparently *not* SchroCat. Beyond My Ken (talk) 23:23, 15 December 2022 (UTC)
|
---|
|
Suggestion
editUnproductive section that won't lead anywhere. Consensus will be evaluated by the closer. ProcrastinatingReader (talk) 21:11, 13 December 2022 (UTC) | ||
---|---|---|
The following discussion has been closed. Please do not modify it. | ||
Does WP:TLDR or WP:DRAMA apply here? Or, perhaps, SchroCat would like to WP:VANISH? My suggestion is to close this entire thread with a WP:NOCONSENSUS rationale – S. Rich (talk) 05:22, 12 December 2022 (UTC)
|
Arbcom & infoboxes
editIf I recall correctly. Arbcom made a ruling on how editors should behave at infobox discussions. GoodDay (talk) 04:09, 13 December 2022 (UTC)
- Here. Standard discretionary sanctions were authorized, and editors were "reminded to maintain decorum and civility when engaged in discussions about infoboxes, and to not turn discussions about a single article's infobox into a discussion about infoboxes in general." The committee also recommended further community discussion re; infoboxes. Specific remedies addressed to SchroCat did not pass. Beyond My Ken (talk) 04:17, 13 December 2022 (UTC)
- Specific remedies addressed to SchroCat did not pass
- He does have an edit restriction to disclose future accounts, to ArbCom. [236]
- The finding "
SchroCat has historically exhibited battleground behavior around the addition of infoboxes
" failed 6-to-5 with at least one of the opposed votes (a vanished arb) saying:Conduct [from 2016] is relevant when establishing a pattern.
" - another noted "
SchroCat seems to have consciously stepped back from infobox debates for the past 18 months
"
- — Shibbolethink (♔ ♕) 07:47, 13 December 2022 (UTC)
- Specific remedies addressed to SchroCat did not pass
- There was also this amendment request at ARCA, which didn;t result in any action being taken. Beyond My Ken (talk) 04:19, 13 December 2022 (UTC)
- As the person who filed that request, what got me mad at the time, and frankly gets me upset again reading that ARCA now, was JzG's decision to overrule 3 admin and Newyorkbrad's idea that a single administrator deciding to not levy a sanction deserved deference. As one of the original drafters of the DS reform about to pass you can draw a straight line from that ARCA to the fact that this won't be allowed going forward. The fact that it was about Schrocat, Cass, etc was incidental to me. The choice of Cass and Schrocat to retire did have some bearing on the ARCA's outcome but I think it's important to realize how much of that discussion was not about Cass, Schrocat, any of hte other editors, or infoboxes. Best, Barkeep49 (talk) 16:15, 13 December 2022 (UTC)
- I asked Bishonen about DS for IP? I understand the reply as WP:AE is possible also for IPs. --Gerda Arendt (talk) 13:39, 13 December 2022 (UTC)
- adding: now that it isn't even IPs any more: arbitration enforcement (AE) is horrible, as I watched and experienced, but it's less horrible than banning, so: could the AE route be pursued before banning is considered. Or any other means to get to comments in discussions that don't hurt other editors? --Gerda Arendt (talk) 09:21, 16 December 2022 (UTC)
- I don’t want Schro to edit from IPs because he has used them to dodge scrutiny, and I think a lot of people agree. As long as that gets done somehow I’m happy. Dronebogus (talk) 13:34, 16 December 2022 (UTC)
- adding: now that it isn't even IPs any more: arbitration enforcement (AE) is horrible, as I watched and experienced, but it's less horrible than banning, so: could the AE route be pursued before banning is considered. Or any other means to get to comments in discussions that don't hurt other editors? --Gerda Arendt (talk) 09:21, 16 December 2022 (UTC)
London Beer flood
editI’m having a problem with another editor who does not log in and edits by IP address, which I consider suspect, why do this if you are a reliable editor? He stated in our Talk:London_Beer_Flood#Mass_of_beer conversation that he is “the editor formally known as SchroCat, editing as 2A00:23C7:2B86:9801:710B:FCB:E462:EC60”. Note there is no profile or Talk page for this editor.
I read this article and realized from my knowledge of physics regarding density and the volume of the litre that the mass of water quoted was not only incorrect, but off by a factor of about 18. Despite his insisting it is my own original research, it is not, it is a scientific fact of density and volume, easily noticeable by anyone who knows the Metric system. I’m amazed no one at Wikipedia noticed this error prior to naming it one of the best articles produced. Getting this error corrected has been difficult, the other editor decided the mass was important when it was incorrect, but now I have a source and it’s been corrected, the mass of the beer is no longer important.
I’ve also edited the article because it was missing metric units contrary to [[MOS:UNIT]. This has been reverted a number of time with the other units hidden “in a citation”. Readers outside the UK may know of Imperial Gallons but the rest of the planet may or may not, and as per the MOS it should be “visibly” included. Readers in the USA may assume their gallon is the same imperial Gallon. The SI unit and US Gallons should be visible without checking citations.
As mentioned in an email with the author of the book used in this article, the vat contained the equivalent of a number of barrels which was a unit used in the 1800’s, these barrels contained 32 ale gallons or 38 imperial gallons, the physical size of the barrel did not change. wp:Reference English brewery cask units. I emailed the author of the book used as a reference in this article (attached).
It seems no amount of additional information will persuade this editor to accept the figure I gave for the mass of beer in the flood or the inclusion of units other than Imperial Gallons, which are not even used in the United Kingdom except in conversation.
Email from author of book used as reference: Avi8tor (talk) 09:27, 15 December 2022 (UTC)
- Avi8tor, just wanted to ping you to let you know that there is a larger thread about SchroCat and I have folded it in to that. I also had to remove a few weird bits of text that got added in (see Special:Diff/1127546933), so please make sure your original message is still largely intact without any major disruption (it was just a few stray headers and AN notices). Primefac (talk) 09:47, 15 December 2022 (UTC)
- Why is this being brought up here, rather than discussed on the talk page (which hasn't been touched for two weeks)? This noticeboard doesn't adjudicate on content questions. Girth Summit (blether) 09:58, 15 December 2022 (UTC)
- For what it's worth I did not notice the time stamps, so if this just needs hatting/removal feel free; my actions were mainly to keep related threads together. Primefac (talk) 10:06, 15 December 2022 (UTC)
- @Avi8tor: I see you have been in discussion at Talk:London Beer Flood but it's all over the place. When you return there, please make a new section with a proposal to change specific text. It would be preferable to stick to one issue at a time and the question of whether the stated volume is accurate is obviously important and should be addressed first. I work on {{convert}} and have seen the issue of historical units being a problem many times. It needs calm investigation, not administrative action although I will watch the article for a while. Johnuniq (talk) 10:12, 15 December 2022 (UTC)
- Thanks for the input. I've been getting nowhere with the editor using an IP address (SchroCat) who keeps reverting what I add and has been accusing me of Original research which it is not. I ended up writing to the Author of the book used as a reference in this article, but could not see how to attach a pdf of the email with addresses redacted. I will do as you suggest. Avi8tor (talk) 11:43, 16 December 2022 (UTC)
- For what it's worth on the specific point of the placement of conversions, MOS:CONVERSIONS is the direct shortcut to the guideline specifying inline conversion in all but a handful of types of article. XAM2175 (T) 12:23, 15 December 2022 (UTC)
Let's get back to the proposal
editJust a reminder to all that there's a serious Proposal being considered in which the Wikipedia community is deciding whether or not to ban a long-time editor from contributing here. That's a serious matter in this context, but it's spawned a lot of side discussions and other distractions. Can we please get our focus back to where it belongs, on the ongoing survey? Beyond My Ken (talk) 02:02, 16 December 2022 (UTC)
- The Cat came back. GoodDay (talk) 06:46, 16 December 2022 (UTC)
Sad
editLevivich made an astute comment above, about "Lynch Mob v. Fan Club", which I think encapsulates the problems of this forum. So often I see the supporters of a sanction seeing the opposers as a fan club, and the opponents seeing the supporters as a lynch mob (not necessarily using those words, but along those lines). Usually, both sides of a dispute have valid arguments, and the fan club/lynch mob polarisation is nothing more than hyperbole. It serves only to generate heat, and no light. Yes, someone can behave badly, and yes, sometimes a ban is justified. But there are often valid arguments that the most severe sanction we can impose is not necessary. The real world is rarely black and white, but mostly consists of various shades of compromise. The whole approach of hurling mud at one's opponents, and making accusations about their motives and biases, is greatly facilitated by this faceless online medium. And I just wish people would stop and think whether they'd say the same things, make the same accusations, to the same people in real life, face to face. I know it's an impossible dream, but I'd love to see this community moving back closer to one in which we all respect each other's rights to disagree, even strongly, without feeling the need to attack, insult and demean in response. Wouldn't that be lovely? Boing! said Zebedee (talk) 08:55, 16 December 2022 (UTC)
- If this is a general lament about what happens at AN all too often, then I agree with you; however at the same time, that would mean that your musing is O/T for this discussion, and this subsection should be collapsed before it goes any further. If, on the other hand, you believe that that is what is happening now in this discussion in a way that's potentially relevant for the outcome, then you'd need to address why you view it like that *this* time, and not before. Or, were the nine or ten previous blocks all "wins" for the "lynch mob", each time? Mathglot (talk) 09:13, 16 December 2022 (UTC)
- Re: "Or, were the nine or ten previous blocks all "wins" for the "lynch mob", each time?" - way to completely miss the point, while providing an example of it. My point is that there should be no thinking of "lynch mob" or "fan club" (or winning or losing, as that's not what it's supposed to be about), because those are damaging hyperbole, and I don't think of either camp in that way. It only serves to dehumanise those who disagree with us, and it's anathema to civil discussion. Boing! said Zebedee (talk) 09:40, 16 December 2022 (UTC)
- PS: Yes, I do think this is relevant to this specific case. Not in the sense that it's likely to change the Yes/No outcome, but more that I hope that if we think more kindly of those with whom we disagree, we might achieve a more understanding consensus. Boing! said Zebedee (talk) 09:50, 16 December 2022 (UTC)
- (edit conflict × 2) Your point was crystally clear; you repeated it in S3, S4, S7, and everything else supported it. Way to miss the quotation marks around wins and lynch mob, though. And I still agree with you, and it's still O/T, and it should still be collapsed. If you insist on agreeing with me repeatedly, I must warn you I will take you to WP:Agreement resolution forum for stern action. Mathglot (talk) 09:53, 16 December 2022 (UTC)
- Fair enough. But to head off the risk of too much agreement, I don't think it's O/T and should be collapsed. I posted it in the hope that people on both sides of this specific discussion might see some value in cooling the confrontational approach. Boing! said Zebedee (talk) 10:04, 16 December 2022 (UTC)
- (edit conflict × 2) Your point was crystally clear; you repeated it in S3, S4, S7, and everything else supported it. Way to miss the quotation marks around wins and lynch mob, though. And I still agree with you, and it's still O/T, and it should still be collapsed. If you insist on agreeing with me repeatedly, I must warn you I will take you to WP:Agreement resolution forum for stern action. Mathglot (talk) 09:53, 16 December 2022 (UTC)
- I couldn't possibly agree with this any more if I tried. I would also hurry to suggest that if it's not too much to ask, perhaps we could all benefit from making a choice to deescalate, disengage, walk away, whatever you want to call it. At this point, the current state of the discussion is not producing anything beneficial, unless one considers mass sanctions a benefit for an online encyclopedia somehow. --🌈WaltCip-(talk) 15:23, 16 December 2022 (UTC)
- @Nemov:. Please don't do this again. You have a very clear position in this disagreement, and you do not have the right to decide that people opposing you should be shut down. If this is to be collapsed, leave it to someone who has not taken a side in the discussion and who can judge it impartially. Boing! said Zebedee (talk) 15:42, 16 December 2022 (UTC)
- I collapsed it not because I disagreed with your sentiment. It's not on topic and further clutters this already cluttered topic. Nemov (talk) 16:05, 16 December 2022 (UTC)
- That's your opinion, and I have clarified why I think it is relevant. As one who has expressed a clear position in the discussion in opposition to mine, you are absolutely not the one to judge and should not try to impose your opinion on the rest of us. Is that not blindlingly obvious to anyone who cares about open discussion and consensus? Boing! said Zebedee (talk) 16:12, 16 December 2022 (UTC)
- I collapsed it not because I disagreed with your sentiment. It's not on topic and further clutters this already cluttered topic. Nemov (talk) 16:05, 16 December 2022 (UTC)
- Beyond My Ken was on the right path with the flood the zone observation. Nemov (talk) 16:37, 16 December 2022 (UTC)
Alternate Proposal?
editIt appears that many members are unwilling to move forward with a CBAN,but acknowledge the problematic behavior of the editor. Moving back to the original account does nothing to address the established history of problems from this editor. Is there an alternative solution? A topic ban perhaps? I'm not sure that would work either since there appears to be WP:BATTLEGROUND behavior everywhere this editor goes. I'm open to suggestions, but it would be an appalling result if he simply carries on from the original account after this long discussion. Nemov (talk) 14:33, 16 December 2022 (UTC)
- My view is that getting the focus back to editing only from their registered account will help focus SchroCat more on the project and on better behaviour. It's very different between using your known account and editing logged out - it brings easier scrutiny, for one thing. Wouldn't it be nice to have an old contributor back, having put a period of perhaps slight bitterness behind them? Punishment for past deeds is not a thing here, and we should only consider how we might improve the future. And I think having SchroCat back, with a committment to only using their logged-in account, is worth trying. Boing! said Zebedee (talk) 15:47, 16 December 2022 (UTC)a am
- PS: I'll just add that I think someone who has produced multiple FAs and GAs, and who has made huge content contributions to the encyclopedia, is worth the extra effort to keep them here and contributing. Does that mean I'm biased towards those who create content above those who do very little of that and mainly frequent the drama boards? Hell, yes! I'd rate a contributor like SchroCat as far more valuable to the project than someone who has never worked on a single GA or FA, and has less than a third of their edits in article space. (And before anyone thinks I'm attacking them, those are my statistics.) Boing! said Zebedee (talk) 16:01, 16 December 2022 (UTC)
- For what it’s worth, I have never logged out just to comment or edit. And “
appalling
? Really? 95 to 98 per cent of my life on WP is stress free, enjoyable, collaborative and positive. What people often forget, as they paint me as the bad guy, is that it takes two to tango. - This thread, for example, started because I was stopping a BLP violation by someone misrepresenting sources. Standing up for that article (not one I have edited much) led to this thread. If you think that is “appalling” and something to trigger a ban or a block is something upon which we will have to disagree. SchroCat (talk) 16:12, 16 December 2022 (UTC)
- For what it’s worth, I have never logged out just to comment or edit. And “
- @Nemov: If the community isn't going to c-ban, so be it. I have proposed a t-ban from anything to do with adding/deleting infoboxes from bios. Ain't gonna lose sleep over it, should it not be adopted. GoodDay (talk) 16:17, 16 December 2022 (UTC)
- Comment - I have downgraded my previous !vote for a site-ban to Weak Support as a second choice, and am waiting for the formulation of a clearly worded alternate proposal that addresses both logged-out editing and infoboxes. Robert McClenon (talk) 17:19, 16 December 2022 (UTC)
- The community ban proposal is not going to make it. Someone uninvolved should close it. Ponyo, are you around? I don't think you've had dealings with SchroCat or fought over infoboxes; this could be the biggest AN thread you ever closed! GoodDay, I can't see your t-ban tree in this c-ban forest, but if someone does close the community ban proposal (which, if it isn't 50/50, is certainly not 70/30--with a stern note about logged-out editing), and perhaps the entire thing as "having run its course" (in part because SchroCat has logged in), that would be something to put up separately in a new thread. Right now there is probably too much in here to discuss that properly and with some distance, and I think discussing a topic ban from infoboxes is a perfectly reasonable proposition. Drmies (talk) 22:14, 16 December 2022 (UTC)
- Although I've never had any involvement with the dreaded infobox wars of yore, I tend to shy away from adminning contentious discussions as this leaves me wholly uninvolved should my checkuser bits be needed in those same contentious areas. It's also why I avoid WP:AE and Arb cases. Plus I'm very very lazy. -- Ponyobons mots 22:23, 16 December 2022 (UTC)
- I brought this here and I'm fine with withdrawing since it's a stalemate. It's disappointing that the many members of the community have no issue with WP:ASPERSIONS. I'm not interested in a topic ban for infobox stuff. This was never about infoboxes and that discussion is running its natural course. SchroCat isn't winning any minds with his behavior there and those comments are easy enough to ignore. I brought this here because of how he was communicating with other editors. If the community won't do anything about it there's nothing left to discuss. Thanks for everyone's commentary. Nemov (talk) 22:42, 16 December 2022 (UTC)
- I would tell you this is one situation where mandating logged in editing may be a justified sanction. Because otherwise SchroCat could just decide next week to log out again and we'd be right back where we started. It would erode the community's trust of course, but the hill to climb would be still quite high to do anything about it. And we have quite a few users here (support and oppose) who would support such a targeted sanction. That's something that would not be possible if you withdraw. — Shibbolethink (♔ ♕) 16:19, 17 December 2022 (UTC)
- (edit conflict)I dare say the only sanction which logically follows this thread IMO is for the logged out user who is not SchroCat. The other person has not connected their other on-wiki identity, seems to have appeared only to snipe and create chaos, and has run afoul of at least a couple bulletpoints of WP:ILLEGIT. And if, perchance, they happen to be someone whose main account is under an arbcom-issued "infobox probation", all the worse (this thread in no small part stemming from infobox discussions, and an active sanction making one ineligible for a WP:CLEANSTART). ...Not that we need a separate thread about it. Any admin might be inclined to simply look into the matter and take action if merited. As for this proposal, I'm not inclined to support a tban on infoboxes. Fix the guidance about infoboxes to be about something other than personal preference, and people won't resent others imposing their personal preference at lots of articles they've never edited before. — Rhododendrites talk \\ 22:43, 16 December 2022 (UTC)
Reporting EchidnaLives for harassment on Charley Pride page.
editThe following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
He keeps reverting the page, forcing me to keep un-reverting it. I added in his work on Tom Sawyer (musical) under his work for another motion picture. I also linked to the appropriate Wikipedia articles about the film itself as well as the featured song in question. I've warned him to quit harassing me and he wants to be a hardhead. I told him I'd be reporting his conduct to Administration for a Level Three warning over the Level Two warning he gave me. Now I'm doing what I told him I would do. Hopefully administration can tell him to go bother somebody else like they always do. 104.218.36.228 (talk) 12:28, 21 December 2022 (UTC)
- The only harassment I am seeing is from you, who threatened EchindaLives for WP:3RR when they made 1 edit. Also, as it was clearly stated, you do not have a source to cite your edit. They were completely correct to remove your edit. RickinBaltimore (talk) 12:34, 21 December 2022 (UTC)
- Thanks @RickinBaltimore. This is absolutely ridiculous. For more context, see User talk:EchidnaLives#Charley Pride. I have not reverted 3RR. I haven't even come close. I have not harassed this user. I have simply reverted an unreferenced addition. Looking at the user's contributions, they have a history of similar things, accusing people of harassment and breaking 3RR when they haven't, threatening to involve administrators and always saying "Thanks for playing". This seems like a WP:CIR issue. echidnaLives - talk - edits 12:37, 21 December 2022 (UTC)
- So he behaves in a passive-aggressive fashion forcing ME to trip the rule. Fine. You want to escalate this to ARBCOM you just forced the action.
- You also notice that everytime I report somebody to higher administration, the additions to the article(s) in question remain as I put them. 104.218.36.228 (talk) 12:43, 21 December 2022 (UTC)
- I have not forced you to trip the rule. You have made 1 revert on the page. 3RR is for when somebody reverts more than 3 times. echidnaLives - talk - edits 12:47, 21 December 2022 (UTC)
- ARBCOM will laugh this off, to be blunt. You made 1 edit, it was reverted. No one broke 3RR. What I am starting to see however is a WP:CIR problem. RickinBaltimore (talk) 12:49, 21 December 2022 (UTC)
- Like I said: We'll wait for ARBCOM to chime in.
- ``Calling someone incompetent is a personal attack and is not helpful.
- ``Sanctions such as blocks and bans are always considered a last resort where all other avenues of correcting problems have been tried and have failed.
- Especially when said bans and blocks just force people to disconnect their router and get a new IP address or use VPN or any number of other workarounds the same as the e.g. gamers do when they get banned off a platform.
- ``Before bringing an issue to the incidents noticeboard or another similar venue, you should have exhausted all reasonable attempts to communicate with the user and correct their behavior.
- Unless it's the other person that needs corrected in which case that is not sound advice.
- ``Use their talk page, explain things to them, and demonstrate how to do things correctly.
- And watch when they take offense to being ``recited at (knowledgebase entries, policy quotations etc) as if they were a prerecorded message or an errant bit of code and escalate to higher authorities when doing so.
- ``On rare occasions, however, after a pattern of behavior has been well established and a user shows they are unlikely to do things correctly, a block, topic ban, or full ban may be the only solutions that minimize disruption to the encyclopedia.
- After which as previously reported, either the block gets reversed by a higher authority or the user gets a new IP address, a new ISP, uses a VPN or any one of a hundred other workarounds.
- As the late Stephen Sondheim wrote: ``I'm still here. 104.218.36.228 (talk) 12:56, 21 December 2022 (UTC)
- Suggesting that you will use a VPN or get a new IP if you a blocked is not helping your case. echidnaLives - talk - edits 12:59, 21 December 2022 (UTC)
- I have not forced you to trip the rule. You have made 1 revert on the page. 3RR is for when somebody reverts more than 3 times. echidnaLives - talk - edits 12:47, 21 December 2022 (UTC)
Musk BLP concern
editThe following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I am concerned about the way the "polarizing" label is applied in Wikivoice to Elon Musk in the lead of his biography. There are discussions in the TP and BLPN on whether it is due in the lead, and editors have highlighted WP:BLP and MOS:LEAD as pertinent policies. I don't have a strong opinion on the matter, but I don't think Musk should be labeled as a "polarizing figure" in Wikipedia's voice in the lead when it is based on a few articles that mention the term in passing, especially given only one of these sources is cited in the article's main body.
When I twice restored Anythingyouwant's attempt to attribute the claim [237] [238], and explained my position on the talk page [239] [240], HAL333 replied "yeah that's just your opinion man" [241], twice reverted me [242] [243] and posted an edit warring warning on my talk page threatening to also post on this noticeboard [244]. I take HAL333's warning serious since they have reported me here before [245].
I would appreciate some policy guidance on whether the disputed unattributed claim should remain in the lead of article while the discussion in the TP and BLPN is ongoing, and may still escalate to an RFC. IntrepidContributor (talk) 14:15, 22 December 2022 (UTC)
- @IntrepidContributor this is not the place for policy advice. BLPN was the right place to go, as well as the TP. Don't edit war, follow consensus. Doug Weller talk 14:56, 22 December 2022 (UTC)
- @Doug Weller: this noticeboard is in fact the right place for policy guidance on how editors should conduct themselves during a content dispute while BLPN is for getting feedback on the content in dispute. If you or other administrators are not interested in providing the requested guidance, I will request it from ARBCOM citing your reluctance here. The issue of whether the content should be included while the dispute is ongoing has already been discussed in the relevant venues. IntrepidContributor (talk) 15:26, 22 December 2022 (UTC)
- Wrong venue, and could be seen to be noticeboard spamming. Stick to BLPN, that's the correct place. Black Kite (talk) 15:08, 22 December 2022 (UTC)
Blocked to edit Jesse Palter
editHi there - I am trying to amend that Jesse Palter was born in Detroit MI, not China, and for someone reason it is saying I am blocked. Please advise. Musiclova11 (talk) 03:32, 22 December 2022 (UTC)
- I don't see an obvious reason why you couldn't - what message did you get when you tried? I've removed the comment, which was added by an IP back in March. Acroterion (talk) 03:37, 22 December 2022 (UTC)
ClydeFranklin: Self-requested removal of rollbacker
editI highly doubt this is the right place (please enlighten me!) but the admin who gave me rollbacker (Malinaccier) hasn't edited in 2 months so I'd probably get no response requesting on their talk page. Anyways, I haven't been (and don't plan on being) active with rollbacker, so I would like it removed. Please retain my reviewer and extendedconfirmed rights as I am (somewhat) active with them. Thank you, Clyde!Franklin! 04:00, 22 December 2022 (UTC)
- @ClydeFranklin: Done, thanks for being sensible and requesting removal And if you find yourself more active again in the future, please feel free to re-request the right — TheresNoTime (talk • they/them) 04:03, 22 December 2022 (UTC)
2023 Arbitration Committee
editThe Arbitration Committee welcomes the following new and returning arbitrators following their election by the community. The two-year terms of these arbitrators formally begin on 1 January 2023:
- Barkeep49 (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- CaptainEek (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- GeneralNotability (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- Guerillero (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- L235 (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- Moneytrees (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- Primefac (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- SilkTork (talk · contribs · deleted contribs · logs · filter log · block user · block log)
All incoming arbitrators have elected to receive the checkuser and oversight permissions.
The Committee will make a further announcement about outgoing arbitrators before the 2023 Committee takes office.
For the Arbitration Committee, Barkeep49 (talk) 22:21, 22 December 2022 (UTC)
RMCD bot
editI'm not sure if this the appropriate venue for this, but the comment that was left on the bot's talk page doesn't seem to attract the needed attention. Basically, RMCD bot keeps removing the link to a move's discussion. I haven't checked if it's doing the same thing elsewhere and I have no idea whether this is intentional (though I doubt it). Could someone please check that it's working properly? Thanks. M.Bitton (talk) 18:42, 23 December 2022 (UTC)
- Looks like GIGO to me. I've adjusted the talk page section title to not contain {{anchor}}, let's see if the bot fixes things now. Anomie⚔ 18:49, 23 December 2022 (UTC)
- Strangely, that was added recently to fix some broken links. Anyway, it's fixed now. Thanks. M.Bitton (talk) 19:12, 23 December 2022 (UTC)
Could someone please create the page File:071R01.jpg with the following content: {{Featured picture|Wire bonding}}. Regards, Armbrust The Homunculus 10:32, 24 December 2022 (UTC)
- Done (the file was affected by the title blacklist) ~ ToBeFree (talk) 12:04, 24 December 2022 (UTC)
IP range that needs blocking, need help in determining extent of range
edit[246]Contributions are full of antisemitic rants in Russian but I'd like another Admin to check to see what range should be blocked. Thanks. Doug Weller talk 09:36, 24 December 2022 (UTC)
- Doug Weller, I plugged some of them into this tool, which threw up 2a00:1370:8180::/42, don't know if that's the best fit possible. Justlettersandnumbers (talk) 10:37, 24 December 2022 (UTC)
- @JustlettersandnumbersThe problem is that both ranges would catch some innocent editors with ok edits, but the antisemitic rants are really bad. I just deleted some more. Doug Weller talk 14:30, 24 December 2022 (UTC)
- Indeed, Doug Weller, there would be some fallout from blocking either of those ranges; I suppose the question is whether or not that's justifiable in the circumstances. Anyway, as a first step I've blocked 2A00:1370:81A6:0:0:0:0:0/48 for a year (turns out that range was previously blocked by El C, and started up again almost as soon as that block expired). I'm really not clever at this stuff, but if you see more of the same unpleasant nonsense I'll willingly attempt to identify blockable ranges. Regards, Justlettersandnumbers (talk) 16:43, 24 December 2022 (UTC)
- @Justlettersandnumbers Thanks for doing the heavy lifting here. Doug Weller talk 16:45, 24 December 2022 (UTC)
- Indeed, Doug Weller, there would be some fallout from blocking either of those ranges; I suppose the question is whether or not that's justifiable in the circumstances. Anyway, as a first step I've blocked 2A00:1370:81A6:0:0:0:0:0/48 for a year (turns out that range was previously blocked by El C, and started up again almost as soon as that block expired). I'm really not clever at this stuff, but if you see more of the same unpleasant nonsense I'll willingly attempt to identify blockable ranges. Regards, Justlettersandnumbers (talk) 16:43, 24 December 2022 (UTC)
- @JustlettersandnumbersThe problem is that both ranges would catch some innocent editors with ok edits, but the antisemitic rants are really bad. I just deleted some more. Doug Weller talk 14:30, 24 December 2022 (UTC)
Change to the Checkuser team
editFollowing a request to the Committee, the CheckUser permissions of Ivanvector (talk · contribs) have been restored.
For the Arbitration Committee, Primefac (talk) 17:48, 24 December 2022 (UTC)
A review into the status of the Jamie Campbell Bower page
editThe page Jamie Campbell Bower has been semi-protected a few times in 2022 but only temporarily, but I still think there should be a review into why this page still has pending edits which has been the case since 2013, which is a rare thing on Wikipedia, the administrator who added this pending edits is also not on Wikipedia anymore. 78.150.91.150 (talk) 03:20, 25 December 2022 (UTC)
- I've reset pending changes for that article, and added it to my watchlist, per WP:TRYUNPROT. For future reference, these queries can also be made at requests for reduction in protection level — TheresNoTime (talk • they/them) 04:07, 25 December 2022 (UTC)
- For clear-up, the pending changes were instituted due to a barely-confirmed relationship with his co-star Lily Collins (sourced by a listicle and our old friends at the Daily Mail, but I'm removing that), but now that she's married to someone else completely, that doesn't justify the protection any longer. Nate • (chatter) 22:45, 25 December 2022 (UTC)
A5 has been deprecated
editAfter discussion, WP:A5 (transwiki'd articles) has been repealed as a CSD after it was used a total of 8 times in the past year (7 of which would have been eligible under another CSD). If you are not one of the *checks notes* two admins who have used this CSD in the past year, you can probably ignore this message. HouseBlastertalk 03:44, 27 December 2022 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Not sure what's happening here, but there seems to be coordination between multiple accounts to publish this seemingly undisclosed paid work of a draft. Could an admin look into this? LilianaUwU (talk / contribs) 09:49, 27 December 2022 (UTC)
- Discussion Needed Master Editz Delhi (talk) 09:51, 27 December 2022 (UTC)
- It is not the time we need to fight each. We can stand together to make the article fit for Wikipedia. Please coperate Master Editz Delhi (talk) 10:07, 27 December 2022 (UTC)
- The draft has been moved to article space and back to draft space three times. The COI template has been removed six times. There are issues here. Adakiko (talk)
Verbal abuse
editThe following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Editors verbally abusing other editors after they have made what they consider to be a considered, productive and rational contribution. Calling such a contribution a "talk page rant" is pejorative. Page : Sponsianus, Edit History Advancingreturns (talk) 20:24, 27 December 2022 (UTC)
- Could you supply a diff for that? Phil Bridger (talk) 20:48, 27 December 2022 (UTC)
https://en.wikipedia.org/w/index.php?title=Sponsianus&diff=prev&oldid=1129919795
- And this editor carries the status of "Veteran Editor III" Advancingreturns (talk) 21:06, 27 December 2022 (UTC)
- "Talk page rant" is not a policy violation. It is a criticism of your style of communicating. Cullen328 (talk) 21:11, 27 December 2022 (UTC)
- It is abusive. It contravenes both the letter and spirit of Civility. I do not rant. I write considered, informed and rational contributions. Rant is derogatory. Advancingreturns (talk) 21:14, 27 December 2022 (UTC)
- It seems like you want us to do something, but none of us responding to you think it's abusive. So your options are to either keep complaining until you find someone who agrees with you, or just let it go and get back to work. But I agree with Cullen - it's not abusive. If you think it's abusive and no one else does, that seems like a valuable opportunity for introspection. --Golbez (talk) 21:19, 27 December 2022 (UTC)
- Where I come the word "rant" doesn't necessarily carry the negative connotation that it seems to for you. I can't say that I disagree with the use of that word in this case. It's not a personal criticism that is actionable here. Cullen328 is correct. 331dot (talk) 21:21, 27 December 2022 (UTC)
- Please include me among those who do not think there is anything for us to do here. Be mindful, however, that you are currently engaged in an edit war and that's blockable. Please follow WP:DISPUTE. Salvio 21:23, 27 December 2022 (UTC)
- You should consider writing shorter posts on Talk:Sponsianus. Mackensen (talk) 21:29, 27 December 2022 (UTC)
- OP partial blocked. 331dot (talk) 21:34, 27 December 2022 (UTC)
- It is abusive. It contravenes both the letter and spirit of Civility. I do not rant. I write considered, informed and rational contributions. Rant is derogatory. Advancingreturns (talk) 21:14, 27 December 2022 (UTC)
- "Talk page rant" is not a policy violation. It is a criticism of your style of communicating. Cullen328 (talk) 21:11, 27 December 2022 (UTC)
- And this editor carries the status of "Veteran Editor III" Advancingreturns (talk) 21:06, 27 December 2022 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Since Salvio pblocked OP, they have become increasingly uncivil, describing users who disagree with them as a "cabal", "abusive characters who are on an online power trip in order to placate their low self-esteem and inferiority complex", and "abusers". Can we extend the pblock to cover talk:Sponsianus, please? Caeciliusinhorto (talk) 23:53, 27 December 2022 (UTC)
- (And, on a point of order, do I need to notify Advancingreturns about this proposal or are they considered aware of this discussion as they initially opened it?) Caeciliusinhorto (talk) 23:57, 27 December 2022 (UTC)
- LOL. No need to notify me. I've seen it. None of these are "uncivil". You only have to look at some of the replies to my contributions on the talk page to see why I have used these terms : "ranter" (which is offensive to many regardless of what others assert), "walls of meaningless text", "poor English" (a total falsification, I am a published author), etc. And by the way, who is this "they"? Personally, I find your 'request' for me to be blocked from the talk page somewhat creepy (as in obsequious). Pass me the sick bag. Don't worry. I won't be bothering you again. I can see that there is no defence to being mobbed by a cohort of editors all with Latin usernames. Like a Budgerigar in a tree full of sparrows. 'Consensus', by the way, does not necessarily mean 'correct' or 'logical'. History itself is the main witness to that. Consensus can often mean abject ignorance and stupidity. Wikipedia is the dictatorship of the consensus regardless. Advancingreturns (talk) 01:44, 28 December 2022 (UTC)
- Advancingreturns, you are recapitulating unpersuasive arguments that experienced editors have heard hundreds of times over many years. The fact of the matter is that WP:CONSENSUS is the decision making technique that has allowed Wikipedia to be a top ten website worldwide for many years, and #1 by far in originally written educational content. Feel free to mock us and deride our editorial processes as you wish. Feel free to contribute instead to a website ranked #742,863. But if you want to contribute to this website, you need to adjust your attitude toward collaboration instead of confrontation with your fellow editors. Cullen328 (talk) 08:13, 28 December 2022 (UTC)
- As for your unsubstantiated claim of being a "published author", that is the weakest possible Argument from authority that I can possibly imagine. Even if we knew what they were, we do not care in any way, shape or form about whatever works you may or not have had published. In the 21st century, publication is a matter of a mouse click. Cullen328 (talk) 08:22, 28 December 2022 (UTC)
- Not only that, but being a published author doesn't mean that you'd never make a language error. I mean, there are plenty of major authors with dyslexia (John Irving springs to mind), and even an author who has complete command of the language will still need an editor or at the very least a proof reader. That being said, it would maybe have been less of a provocation if Caeciliusinhorto had simply pointed out the fact that "claim of" is unidiomatic, or even skipped that argument entirely, focusing on the more relevant semantic difference between "claim" and "evidence". None of this is an excuse for AR's personal attacks, though. --bonadea contributions talk 10:56, 28 December 2022 (UTC)
- LOL. They are my arguments whether you like them or not and I will assert them. I see that 'thought control' is part of the work of Admins on this site. You have not addressed my complaints with balance, proportion and all due impartiality. I am labelled an 'edit warrior' for reverting what I consider to be incorrect but the cohort of editors with Latin usernames on the page in question can be 'edit warriors' without any consequence from the likes of you people. The page does not have a neutral POV. It is the 'baby' of a group of editors who *want to believe* that Sponsianus was a real historical figure. You only have to look at their own talk and user pages to see that. Some are even supposing that Sponsianus was the possible victim of Damnatio Memoriae (again without any evidence) or that there were writers in Antiquity which referred to him but their writings have been lost. A spurious way of proceeding and a way of proceeding which informs their editing of the page in question. I am a published author and my English has enabled me to write a 500 page book on politics, economics and history. You may wish to question or doubt that as you wish. My book was published by a well known publisher. I mentioned it to give an indication that my English is not as poor as one editor may wish to assert. I have never met such a smug group of people as yourselves online. The self-satisfaction and conceit is absolutely breathtaking. You have no reserve, no respect, no humility, no consideration for anybody else's work except your own. Pure arrogance. Patronising and patriarchal beyond measure. Telling people to "change their attitude", good grief, how patronising is that? It reminds me of my schooldays when I was 'carpeted' by the Headteacher. What you call 'Consensus' effectively becomes a form of online bullying for those who refuse to fall in line with it. And that is part of the flaw in Wikipedia as evidenced by the content of many of its pages. Consensus does not necessarily mean 'correct', 'logical', 'reasonable' and precluding the existence of cabals and cliques in their construction of their pages. As Admins, you seem to completely ignore the real possibility of the latter. But then again, you are a clique yourselves so that is understandable. Advancingreturns (talk) 11:35, 28 December 2022 (UTC)
- As for your unsubstantiated claim of being a "published author", that is the weakest possible Argument from authority that I can possibly imagine. Even if we knew what they were, we do not care in any way, shape or form about whatever works you may or not have had published. In the 21st century, publication is a matter of a mouse click. Cullen328 (talk) 08:22, 28 December 2022 (UTC)
- Advancingreturns, you are recapitulating unpersuasive arguments that experienced editors have heard hundreds of times over many years. The fact of the matter is that WP:CONSENSUS is the decision making technique that has allowed Wikipedia to be a top ten website worldwide for many years, and #1 by far in originally written educational content. Feel free to mock us and deride our editorial processes as you wish. Feel free to contribute instead to a website ranked #742,863. But if you want to contribute to this website, you need to adjust your attitude toward collaboration instead of confrontation with your fellow editors. Cullen328 (talk) 08:13, 28 December 2022 (UTC)
- I think we need to extend the block sitewide and TPA revoke, the user is obviously not interested in collaborating, continuing to double down on his continued attacks on other editors. Lavalizard101 (talk) 11:58, 28 December 2022 (UTC)
- LOL. This BBC piece explains why many do not wish to be part of Wikipedia and why many newcomers do not stick around. You lot are the worst club of control freaks I have encountered online. You leave no room for dissent whatsoever. It is truly dictatorial. Do as you wish. You behave like a malevolent online ruling class which accepts no opposition or conflict. Who on earth wants to work in such an atmosphere? https://www.bbc.co.uk/news/technology-28426674 Advancingreturns (talk) 12:22, 28 December 2022 (UTC)
- And try addressing what I have written in my post rather than behaving like a robotic functionary without any human engagement with other people's work. "Alienating" is the word. It is like trying to communicate with a soulless machine. Advancingreturns (talk) 12:27, 28 December 2022 (UTC)
- You lot, control freaks etc. see what I mean, I am an uninvolved editor and you're first response to an uninvolved editors response is to immediately jump into personal attacks, cabal accusations and incivility. Thereby solidifying the need for block extending and TPA revoke. Lavalizard101 (talk) 12:34, 28 December 2022 (UTC)
- LOL. No need to notify me. I've seen it. None of these are "uncivil". You only have to look at some of the replies to my contributions on the talk page to see why I have used these terms : "ranter" (which is offensive to many regardless of what others assert), "walls of meaningless text", "poor English" (a total falsification, I am a published author), etc. And by the way, who is this "they"? Personally, I find your 'request' for me to be blocked from the talk page somewhat creepy (as in obsequious). Pass me the sick bag. Don't worry. I won't be bothering you again. I can see that there is no defence to being mobbed by a cohort of editors all with Latin usernames. Like a Budgerigar in a tree full of sparrows. 'Consensus', by the way, does not necessarily mean 'correct' or 'logical'. History itself is the main witness to that. Consensus can often mean abject ignorance and stupidity. Wikipedia is the dictatorship of the consensus regardless. Advancingreturns (talk) 01:44, 28 December 2022 (UTC)
- TPA revoked by Yamla not even five minutes later for continuing the blanking on their talk page. What even was the goal with the blanking, that just led to him being indef blocked. Lavalizard101 (talk) 12:43, 28 December 2022 (UTC)
Unacceptable username
editThe following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Please say Kalogeropoulos to block the user Gamwthnmanasou in el.wikipedia. --2A02:85F:F584:9554:5CA9:9623:8222:9FBC (talk) 19:57, 27 December 2022 (UTC)
- You'll have to talk at the people at el.wikipedia about that. --Golbez (talk) 21:14, 27 December 2022 (UTC)
- Neutral comment (this is Greek for 'goddamn it' for those trying to figure it out; no account on en.wiki at this time) Nate • (chatter) 22:51, 27 December 2022 (UTC)
- If this user creates an account on this wiki, such an account can be dealt with by this Wikipedia's administrators. His account on Greek Wikipedia must be dealt with there. I don't know any Greek, but based on the interwiki of this page I would ask at el:Βικιπαίδεια:Σημειωματάριο διαχειριστών. Animal lover |666| 11:13, 28 December 2022 (UTC)
- I'd just like to point out that the name is more vulgar than that; it's Greeklish: Gamwthnmanasou->Gamw thn mana sou->γαμώ την μάνα σου="I'm fucking your mom." It can be used as a generic expletive but the literal meaning is just as common. Winthrop23 (talk) 06:16, 29 December 2022 (UTC)
- No one here said the username is okay. We said there's nothing that English Wikipedia can do to users on Greek Wikipedia. It's the admins there you need to talk to. Animal lover |666| 16:38, 29 December 2022 (UTC)
- Neutral comment (this is Greek for 'goddamn it' for those trying to figure it out; no account on en.wiki at this time) Nate • (chatter) 22:51, 27 December 2022 (UTC)
Coffee News is copied from an advertisement
editHello Wikipedia administrators. The Wikipedia page on Coffee News copies directly from https://www.coffeenews.com/about/. I think the page is an advertisement in disguise. Can an administrator delete the page? Lobster from Maine (talk) 01:42, 30 December 2022 (UTC)
- I have reverted the edits to the non-advertisement version. Thank you for letting us know. ... discospinster talk 01:44, 30 December 2022 (UTC)
- Fyi, sent to AfD as the restored text is still problematic. Slywriter (talk) 02:06, 30 December 2022 (UTC)
Outgoing members of the 2022 Arbitration Committee
editThe Arbitration Committee thanks our outgoing colleagues whose terms end on 31 December 2022:
- BDD (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- Bradv (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- Donald Albury (talk · contribs · deleted contribs · logs · filter log · block user · block log)
- Maxim (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Outgoing arbitrators are eligible to retain the CheckUser and Oversight permissions, remain active on cases accepted before their term ended, and to remain subscribed to the functionaries' and arbitration clerks' mailing lists following their term on the committee. To that effect:
- Stewards are requested to remove the permission(s) noted from the following outgoing arbitrators, who did not elect to retain CheckUser or Oversight access, after 31 December 2022:
- CheckUser: BDD, Bradv, Maxim, Donald Albury
- Oversight: BDD, Bradv, Maxim, Donald Albury
- Outgoing arbitrators are eligible to remain active on cases opened before their term ended if they wish. Whether or not outgoing arbitrators will remain active on any ongoing case(s) will be noted on the proposed decision talk page of affected case(s).
- Maxim and Donald Albury will be unsubscribed from the functionaries' mailing list at their request.
- BDD, Maxim, and Donald Albury will be unsubscribed from the arbitration clerks' mailing list at their request.
For the Arbitration Committee, KevinL (aka L235 · t · c) 20:32, 30 December 2022 (UTC)
Hi, Since this file is free, it can be moved to Commons, but I can't do it, it says "Can't import file because at least one of its file revisions is hidden." Thanks for your help, Yann (talk) 21:45, 30 December 2022 (UTC)
- @Yann: Done I've undeleted that file revision. Legoktm (talk) 21:51, 30 December 2022 (UTC)
Hall & Oates
editWould an administrator mind watching Hall & Oates for a bit just in case a "move war" ends up happening? This started out as WP:THQ#Hall & Oates where it was pointed out to the OP that moving the page had been previously discussed before and a consensus for such has never been established. There are also a number of declined move requests related to this currently visible on the article's talk page. Since the page move is almost certainly contentious, a more formal consensus should be established via a RM discussion per WP:PCM. -- Marchjuly (talk) 22:41, 30 December 2022 (UTC)
- I have placed extended confirmed move protection on the article for two weeks. Repeated moving against clear talk page consensus is not permitted. Consensus can change but unilateral moving in a situation like this is not acceptable. Cullen328 (talk) 00:10, 31 December 2022 (UTC)
- Thank you Cullen328. -- Marchjuly (talk) 07:37, 31 December 2022 (UTC)
- You are welcome, Marchjuly. Check out my Twitter page for my real feelings about this content dispute. Oh, no, I shut down my rarely used Twitter page a month or so ago. Oh, well. Cullen328 (talk) 08:15, 31 December 2022 (UTC)
- Thank you Cullen328. -- Marchjuly (talk) 07:37, 31 December 2022 (UTC)
Name of suspect added to "2022 pregnancy of a 10-year-old in Ohio"
editCan someone please remove the name of the suspect from 2022 pregnancy of a 10-year-old in Ohio? --Jax 0677 (talk) 01:32, 24 December 2022 (UTC)
- I'm looking for it, can you give me a diff? Valereee (talk) 02:05, 24 December 2022 (UTC)
- Valereee, Special:Diff/1129185740 -Not added, so much as it's part of the hyperlink for sources added. Think FireFangled removed from live article. Slywriter (talk) 03:42, 24 December 2022 (UTC)
- Should the name of the suspect not be removed entirely from the history if the suspect is not otherwise famous, nor has the suspect been convicted? --Jax 0677 (talk) 10:23, 24 December 2022 (UTC)
- So it's just that the name is being used as part of the hyperlink so that it's visible if you hover over the link and then check the URL? I don't think that's a blp vio. Clicking on the link takes you to the source. Valereee (talk) 12:45, 24 December 2022 (UTC)
- Reply - Would this not defeat the purpose of concealing the identity of the suspect per WP:BLPCRIME? --Jax 0677 (talk) 14:04, 24 December 2022 (UTC)
- Well, for me, we don't conceal it. We don't try to make sure the letters that form the name appear nowhere in Wikipedia including in URLs for sources. We just don't include it in the article, and we remove it if we see it. Possibly revdel'ing, although I kind of feel like that's not usually necessary unless there's been something egregious added along with the name.
- IMO we don't need to avoid using sources that use a suspect's name in a headline, which often means it's part of the URL. We just don't identify them ourselves in the article without a conviction. But if you think that's too lax an interpretation, maybe discuss at BLPN? Valereee (talk) 14:28, 24 December 2022 (UTC)
- Reply - I have started a discussion about this at WP:BLPN. --Jax 0677 (talk) 14:02, 27 December 2022 (UTC)
- Reply - Would this not defeat the purpose of concealing the identity of the suspect per WP:BLPCRIME? --Jax 0677 (talk) 14:04, 24 December 2022 (UTC)
- So it's just that the name is being used as part of the hyperlink so that it's visible if you hover over the link and then check the URL? I don't think that's a blp vio. Clicking on the link takes you to the source. Valereee (talk) 12:45, 24 December 2022 (UTC)
- Should the name of the suspect not be removed entirely from the history if the suspect is not otherwise famous, nor has the suspect been convicted? --Jax 0677 (talk) 10:23, 24 December 2022 (UTC)
- Valereee, Special:Diff/1129185740 -Not added, so much as it's part of the hyperlink for sources added. Think FireFangled removed from live article. Slywriter (talk) 03:42, 24 December 2022 (UTC)
Admin with expertise in Korean history requested
editThere is an open unblock request at User talk:Judication that includes a list of very detailed proposed edits relating to various Korean history projects. I'm concerned by the general "I will report to the front lines of a fringe history battleground" tenor of the edits, but on the chance that all of these proposed edits are in fact much-needed corrections to a pseudohistory quagmire, it would be good if someone with some familiarity with Goguryeo, Balhae, Gojoseon and Hanbok could take a look. signed, Rosguill talk 03:13, 30 December 2022 (UTC)
- I don't know Korean history. However, I have looked at the unblock request, and it looks to me like an attempt to confuse the jury (the Wikipedia community). I agree with User:Rosguill that a review by someone familiar with Korean history would be helpful. In my opinion, it need not be an admin. Only an admin can unblock, but an editor with a subject matter background can say that there is merit to the request, or, more likely, that there isn't merit to the request. I agree that the overall tone of the request is worrisome, and it should be read cautiously. Robert McClenon (talk) 08:29, 30 December 2022 (UTC)
- Blocked as a sock puppet of VeryGoodBoy by Bbb23. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 19:16, 30 December 2022 (UTC)
- Yes, this editor was blocked, but this is an unblock request. Phil Bridger (talk) 19:35, 30 December 2022 (UTC)
- much embarrassment, please ignore me -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 13:02, 31 December 2022 (UTC)
- Yes, this editor was blocked, but this is an unblock request. Phil Bridger (talk) 19:35, 30 December 2022 (UTC)
- Blocked as a sock puppet of VeryGoodBoy by Bbb23. -- LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 19:16, 30 December 2022 (UTC)
- I don't know Korean history. However, I have looked at the unblock request, and it looks to me like an attempt to confuse the jury (the Wikipedia community). I agree with User:Rosguill that a review by someone familiar with Korean history would be helpful. In my opinion, it need not be an admin. Only an admin can unblock, but an editor with a subject matter background can say that there is merit to the request, or, more likely, that there isn't merit to the request. I agree that the overall tone of the request is worrisome, and it should be read cautiously. Robert McClenon (talk) 08:29, 30 December 2022 (UTC)
JJMC89 bot deleted the Bangladesh Football Federation logo from their National Team pages (both men & women)
editHello Wikipedia administrators, I seek your highly serious attention to the matter that JJMC89 bot ( https://en.m.wikipedia.org/w/index.php?title=User:JJMC89_bot&action=view ) deleted the official Bangladesh Football Federation logo from their all National Football Team pages including under 17, under 20, under 23 & national teams (both men & women).
Reason showing: Removed WP:NFCC violation(s). No valid non-free use rationale for this page. See WP:NFC#Implementation. Questions? Ask here.
Why am I disobeying this? - Because every national football team is showing their respective National football Federation to represent your country except Bangladesh (the reason I am appealing for) - I neither made any changes to that image nor re-uploaded. I just put a line (Bangladesh Football Federation.svg) on the Badge section of the template of all Bangladesh National Football Team pages including under 17, under 20, under 23 & national teams. - THE MOST IMPORTANT POINT, this exact same picture is currently using on Bengali Wikipedia Bangladesh national football team pages including under 17, under 20, under 23 and the national teams (both men and women). — Preceding unsigned comment added by HridoyKundu (talk • contribs) 19:52, 31 December 2022 (UTC)
Please revert the action of that bot.
Because that image represents Bangladesh national football teams and gives better understanding to the audience. — Preceding unsigned comment added by HridoyKundu (talk • contribs) 19:39, 31 December 2022 (UTC)
- The logo was removed from the articles following this discussion. You then re-added the logo to the article. GiantSnowman 19:54, 31 December 2022 (UTC)
- Wikipedia is a freely licensed encyclopedia. As such, the use of non-free content should be minimized. In this case, the use of the logo for the teams is not allowed. See WP:NFC#UUI, item number 17. In the case of this logo, the use in the article about the federation is acceptable, but the usage in the any of the various team articles is not as these are the "child entities" noted in item 17. -- Whpq (talk) 01:15, 1 January 2023 (UTC)
Intentional vandalism by a user
editIf you observe this user Rasnaboy User:Rasnaboy
He or She intentionally undo all the updated or cited Tamil or Tamils or Tamil Nadu related articles back to its old description.
Possibly a user from North India with rivalry mindset.
For example take a look at Early Cholas page. you will have some idea..
Need some moderation please. 1.38.104.185 (talk) 08:09, 2 January 2023 (UTC)
- Content dispute. Use his talk page or article talk page.
- Also read WP:NOTVAND to know what is not vandalism. Capitals00 (talk) 10:31, 2 January 2023 (UTC)
Lublin Airport
editAfternoon Dublin Airport was protected earlier because of an edit war with an ip address. Potentially the same IP editor is now reverting changes at Lublin Airport. Might need an eye on it; I'm wary of entering 3RR territory against an IP address. Thanks doktorb wordsdeeds 15:38, 2 January 2023 (UTC)
- Looks like WP:LTA/BKFIP, both here and at Dublin Airport. IP blocked 72 hours; nothing to worry about as far as 3RR. Complex/Rational 16:42, 2 January 2023 (UTC)
- Thanks. I'm always jumpy when reversions happen. doktorb wordsdeeds 17:00, 2 January 2023 (UTC)
Please review my block
editThe following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I recently imposed a 1 hour block on User:Moops. They have been putting Happy New Years banners on hundreds (maybe thousands) of user talk pages at a high rate. As fast as 4 or 5 per minute. I'm assuming they're using some sort of bot or at least some semi-automated process like AWB. Blocking them seemed like the most expeditious way to stop the disruption. If anybody thinks my block was unsound, let me know and/or just go ahead and unblock them. -- RoySmith (talk) 17:37, 2 January 2023 (UTC)
- Endorsed Reasonable action. I'll just copy and paste what I left on Moops' talk page:
Endorsing RoySmith's action. I generally expect people doing this (leaving seasons' greetings and such) to have some form of relation or correspondence established with the users they are leaving notices for. Simply hitting every user in the top 1000 is disruptive.
-- ferret (talk) 17:42, 2 January 2023 (UTC)- Though I agree a warning first would have been better. -- ferret (talk) 18:15, 2 January 2023 (UTC)
- TY for that. That is ALL that I would have needed! — Moops ⋠T⋡ 18:21, 2 January 2023 (UTC)
- Though I agree a warning first would have been better. -- ferret (talk) 18:15, 2 January 2023 (UTC)
- It looks like you already offered on their talk page to unblock them if they agreed to stop, which they have, so I suggest you lift the block. Why did you not message the user and ask them to stop rather than going straight for a block? - Kingpin13 (talk) 17:42, 2 January 2023 (UTC)
- I went to a block first becaused of the high rate of speed this was happening. I see that they've offered to stop, but they followed that up with
Also, I would like to continue sending these happy new years banners, if only for the rest of today
, so unclear what their intentions really are. -- RoySmith (talk) 17:47, 2 January 2023 (UTC)- Not an admin, but, despite the 'rate of speed' I still think you could have asked Moops to stop before blocking. Looking at their list of contributions, they stopped in between posting (admittedly a lot of) New Years banners, in order to respond to thank you messsages and/or New Years greetings they were receiving in return. Moops pointed out that having a block in their otherwise non-existent block log was stressful to them. They should have had the chance to respond to and reflect on a warning of some kind. (I'm of two minds whether the mass-posting of New Years banners was disruptive or not; a number of recipients did seem to appreciate this cup of kindness, yet). ---Sluzzelin talk 17:52, 2 January 2023 (UTC)
- Absolutely agree with Sluzzelin that a talk page message should have been your first port of call despite the speed of editing. I don't agree with indiscriminately spamming the top x number of editors with seasonal messages, but let's be honest, the amount of "disruption" caused by that (which could have been avoided with a simple talk page message / warning) is not in proportion to the level of upset you have caused now with a completely unnecessary block. The user has made it quite clear on their talk page that they are willing to stop if necessary for an unblock, which is the terms that you proposed. - Kingpin13 (talk) 17:56, 2 January 2023 (UTC)
- Not an admin, but, despite the 'rate of speed' I still think you could have asked Moops to stop before blocking. Looking at their list of contributions, they stopped in between posting (admittedly a lot of) New Years banners, in order to respond to thank you messsages and/or New Years greetings they were receiving in return. Moops pointed out that having a block in their otherwise non-existent block log was stressful to them. They should have had the chance to respond to and reflect on a warning of some kind. (I'm of two minds whether the mass-posting of New Years banners was disruptive or not; a number of recipients did seem to appreciate this cup of kindness, yet). ---Sluzzelin talk 17:52, 2 January 2023 (UTC)
- I went to a block first becaused of the high rate of speed this was happening. I see that they've offered to stop, but they followed that up with
- Endorse for the reasons outlined on Moops's talk page. A short block was reasonable to get across the seriousness of the situation and halt the disruption given the scale and speed of the edits. There was no bad faith on Moops's part, just a bad idea with good intent. HJ Mitchell | Penny for your thoughts? 17:58, 2 January 2023 (UTC)
- By the way, I do see the argument being made against the block. I agree that a block of any significant duration (even 12 or 24 hours) would have been a massive overreaction but a very short block was reasonable. HJ Mitchell | Penny for your thoughts? 18:15, 2 January 2023 (UTC)
- Again, a warning would have been sufficient. Entirely and wholly would have abided by that. I am not here to be disruptive and not one single person had complained prior to me sending a 'Happy New Years' to RoySmith. Hopefully this can be a learning experience for us all. — Moops ⋠T⋡ 18:22, 2 January 2023 (UTC)
the seriousness of the situation
😂 Tewdar 18:40, 2 January 2023 (UTC)- I still don't think Moops realises they were doing anything wrong, despite mass spamming people. Secretlondon (talk) 18:50, 2 January 2023 (UTC)
- Yeah, all my bleddy relatives were mass spamming me with Christmas cards again this year. Very wrong indeed. 🙄 Tewdar 18:53, 2 January 2023 (UTC)
- I am asking the community here at large Secretlondon, and I am not about to restart anything without a clear "go-ahead" to proceed. I respect warnings just as much as blocks, and would have just liked to have seen a warning prior to being outright blocked, as that is now FOREVER in my "block log"... :( — Moops ⋠T⋡ 19:10, 2 January 2023 (UTC)
- By the way, I do see the argument being made against the block. I agree that a block of any significant duration (even 12 or 24 hours) would have been a massive overreaction but a very short block was reasonable. HJ Mitchell | Penny for your thoughts? 18:15, 2 January 2023 (UTC)
- Mmmm...oops. Should have asked them to stop before blocking. What was the harm to the encyclopedia that would have come from the delay? Five or ten more Happy New Years postings? It's not like a mainspace vandalism spree, it's not like they're sending death threats out. Just talk to the editor first, before you press the button. I sympathize with the complaint that you messed up a clean block log for not a very good reason. Levivich (talk) 17:58, 2 January 2023 (UTC)
- I strongly disagree with the block. In my view the New Year's greetings did not warrant blocking at all, as I don't believe they were in any way disruptive, and certainly not without a warning. Newyorkbrad (talk) 17:59, 2 January 2023 (UTC)
- Oppose Block - I agree the welcomes were excessive, but it was premature to escalate to a block, especially over something that was only vaguely irritating and wasn't particularly damaging anything. Sergecross73 msg me 18:02, 2 January 2023 (UTC)
- Oppose block. Discussing the matter with Moops should have been the first step. Cullen328 (talk) 18:08, 2 January 2023 (UTC)
- It looks fairly draconian to block without discussion under these circumstances... Salvio 18:11, 2 January 2023 (UTC)
- TY. I think it would have been nice to have simply received a warning at the worst first. I would have respected it, just as I HAVE stopped now until I can get clear 'go-ahead' that I could proceed WITHOUT RISK of being blocked AGAIN! :) — Moops ⋠T⋡ 19:08, 2 January 2023 (UTC)
- Oppose block - 4 or 5 a minute could easily be achieved manually. Opening a few dozen tabs then new topic, ctrl-v, enter, ctrl-tab, repeat could do a dozen a minute. EvergreenFir (talk) 18:15, 2 January 2023 (UTC)
- That is precisely correct. I am not a technical person and have no idea how to create or use a bot. :) — Moops ⋠T⋡ 18:23, 2 January 2023 (UTC)
- And your many tabs option is new to me as well, but I'd be careful not to start up with that or anything similar unless I know with certainty that I am not going to get blocked for sending more 'Happy New Year' greetings! — Moops ⋠T⋡ 19:07, 2 January 2023 (UTC)
- That is precisely correct. I am not a technical person and have no idea how to create or use a bot. :) — Moops ⋠T⋡ 18:23, 2 January 2023 (UTC)
- Oppose block - you could have asked them to stop first. Black Kite (talk) 18:19, 2 January 2023 (UTC)
- Please unblock so they can send me a Happy New Year message. ☹️ Tewdar 18:24, 2 January 2023 (UTC)
- You got yours coming! :) — Moops ⋠T⋡ 18:32, 2 January 2023 (UTC)
- Thanks Moops, Happy New Year! 😁👍 Tewdar 18:38, 2 January 2023 (UTC)
- You got yours coming! :) — Moops ⋠T⋡ 18:32, 2 January 2023 (UTC)
- Oppose block - A classic case of WP:AGF not being extended to
long timeregular editors. Discussion should have come first. It is a warped idea where a New Years Greeting is considered "disruptive" editing. Yes, it may have been a case of WP:EDITCOUNTITIS but where is the harm to the project. MarnetteD|Talk 18:27, 2 January 2023 (UTC) - It's essential we stop editors being nice to too many other editors. If we let Moops get away with wishing lots of us a Happy New Year, whatever next? Editors saying "well done" when someone reverts vandalism? People offering to help fix reference errors? An atmosphere of mutual support and respect? Wikipedia's core value of being a bunch of miserable cunts will be eroded, perhaps irreversibly. DuncanHill (talk) 18:29, 2 January 2023 (UTC)
- You are spot on DuncanHill It is a thin edge of the wedge on a slippery slope situation that would inevitably lead to the awarding of barnstars - shudder. MarnetteD|Talk 18:46, 2 January 2023 (UTC)
- :)
- — Moops ⋠T⋡ 18:32, 2 January 2023 (UTC)
- For the first time ever, this year I had the temerity to send out so-called "New Year's Greetings and good wishes" to certain editors, some of whom I do not know well. I had no idea what an egregious faux-pas I was committing, and the risk I was running. Next year I shall revert to grumpy silence, to better fit the holiday spirit on these boards. Mr Serjeant Buzfuz (talk) 22:00, 2 January 2023 (UTC)
- I'll come down on the side of there should have been a warning before the block. I also think that we, as a project, are not very good at dealing with editors who mean well, but who make large numbers of repetitive edits at a high speed. I have no idea whether this is the case here, but I think that often these are editors who are on the autism spectrum, and who are very good at editing quickly (and often are very helpful in doing so). I don't have a solution to offer, other than WP:AGF, in both directions. --Tryptofish (talk) 19:10, 2 January 2023 (UTC)
- Warning before the block? Definitely. But making assumptions about the possible neurodivergence of other editors? Swing and a miss. GiantSnowman 19:12, 2 January 2023 (UTC)
- No. That was accurate actually. :) — Moops ⋠T⋡ 19:13, 2 January 2023 (UTC)
- Which is possibly why it is so, SO distressing to me that I have this block on my 'block log' now too....... I really work hard to just do right, and it is most distressing to me that this admin couldn't have just warned me first. I would have then stopped, discussed, and only resumed upon hearing that it would be okay to do so. Asbergers by the way. So not as bad as it could be I gather, and they no longer call it that any more. I gather it is just blended into the larger 'spectrum'. TY — Moops ⋠T⋡ 19:15, 2 January 2023 (UTC)
- GiantSnowman, you seem to have missed where I said "I have no idea whether this is the case here". Moops, feel free to take a look at my own block log. I know exactly how you feel right now, from personal experience, but I can promise you, from personal experience, that this is very much recoverable. --Tryptofish (talk) 19:21, 2 January 2023 (UTC)
- I sure hope so. I mainly hope it does not interfere with an outstanding request that I have in for 'New Pages Reviewer' rights. I have participated in many AfD's, and feel that I am a good candidate to earn that perm, but a single block can throw you back MONTHS I have seen with other editors applications sometimes....... :( — Moops ⋠T⋡ 19:22, 2 January 2023 (UTC)
- I totally sympathize with your misgivings about the newly-splotched clean sheet, and for that reason alone, blocks should never be handed out lightly. There is another way of seeing it though. Having a block, in this case, means you showed initiative without first having checked out all the rules and policies and then playing it safe. I still have a clean block log, but that just makes me a boring goody two shoes; your reputation, on the other hand, has become more colorful and wilder. ---Sluzzelin talk 19:24, 2 January 2023 (UTC)
- Perhaps more to the point, it can indicate that one has gained empathy for what other editors who have been blocked feel like. If that empathy is used well, it can be evidence of being trustworthy. --Tryptofish (talk) 19:36, 2 January 2023 (UTC)
- I can only hope that you are right in that reasoning. Makes sense to me, but I do not know if everyone will see it that way, namely everyone with the power to grant rights/perms etc. TY again... :) — Moops ⋠T⋡ 19:47, 2 January 2023 (UTC)
- Perhaps more to the point, it can indicate that one has gained empathy for what other editors who have been blocked feel like. If that empathy is used well, it can be evidence of being trustworthy. --Tryptofish (talk) 19:36, 2 January 2023 (UTC)
- Haha, I suppose that is a nice and positive 'spin' on the situation. It is still mostly distressing to me, as I always was very proud of that 'reputation' of being 'block-free', but alas, it is a scar that is apparently irreversible... :-/ — Moops ⋠T⋡ 19:26, 2 January 2023 (UTC)
- For what it's worth: [247]. I encourage other editors to consider following my lead. --Tryptofish (talk) 19:31, 2 January 2023 (UTC)
- That was incredibly kind of you. I do hope it is taken into consideration. TY very, very kindly. :) — Moops ⋠T⋡ 19:34, 2 January 2023 (UTC)
- For what it's worth: [247]. I encourage other editors to consider following my lead. --Tryptofish (talk) 19:31, 2 January 2023 (UTC)
- I totally sympathize with your misgivings about the newly-splotched clean sheet, and for that reason alone, blocks should never be handed out lightly. There is another way of seeing it though. Having a block, in this case, means you showed initiative without first having checked out all the rules and policies and then playing it safe. I still have a clean block log, but that just makes me a boring goody two shoes; your reputation, on the other hand, has become more colorful and wilder. ---Sluzzelin talk 19:24, 2 January 2023 (UTC)
- I sure hope so. I mainly hope it does not interfere with an outstanding request that I have in for 'New Pages Reviewer' rights. I have participated in many AfD's, and feel that I am a good candidate to earn that perm, but a single block can throw you back MONTHS I have seen with other editors applications sometimes....... :( — Moops ⋠T⋡ 19:22, 2 January 2023 (UTC)
- GiantSnowman, you seem to have missed where I said "I have no idea whether this is the case here". Moops, feel free to take a look at my own block log. I know exactly how you feel right now, from personal experience, but I can promise you, from personal experience, that this is very much recoverable. --Tryptofish (talk) 19:21, 2 January 2023 (UTC)
- Which is possibly why it is so, SO distressing to me that I have this block on my 'block log' now too....... I really work hard to just do right, and it is most distressing to me that this admin couldn't have just warned me first. I would have then stopped, discussed, and only resumed upon hearing that it would be okay to do so. Asbergers by the way. So not as bad as it could be I gather, and they no longer call it that any more. I gather it is just blended into the larger 'spectrum'. TY — Moops ⋠T⋡ 19:15, 2 January 2023 (UTC)
- No. That was accurate actually. :) — Moops ⋠T⋡ 19:13, 2 January 2023 (UTC)
- Warning before the block? Definitely. But making assumptions about the possible neurodivergence of other editors? Swing and a miss. GiantSnowman 19:12, 2 January 2023 (UTC)
- Comment - I didn't feel disrupted, by Moops' HAPPY NEW YEAR message. GoodDay (talk) 19:18, 2 January 2023 (UTC)
- TY GoodDay, I am glad that I was able to spread some joy while I was before that I was blocked! I do hope to be able to continue sending some of these at least throughout the rest of this first week of the new year, but I will NOT do so unless I can get RoySmith to agree that it is not disruptive and that I will not be blocked again. Once I have that assurance, I will continue, through January 5th or 6th, and then I would be done for my greetings for 2023. That is my stated plan, and I would not proceed without the blessing of the community. :) — Moops ⋠T⋡ 19:25, 2 January 2023 (UTC)
- Then let the record show, despite my stated being 'of two minds' above (probably playing it safe, as per above too) that I have looked at the reactions by recipients of your cups of kindness, and have come to the conclusion that it was not disruptive, and that you should be allowed to continue. Floquenbeam makes a good point regarding User:MediaWiki message delivery who notifies everyone without being kind. ---Sluzzelin talk 19:50, 2 January 2023 (UTC)
- I appreciate that. I'd love to continue, at least for a short while. This isn't a life long pursuit, its just the new year and I was feeling happy and wanted to share that with the most productive editors that I could find! :-D — Moops ⋠T⋡ 19:53, 2 January 2023 (UTC)
- Then let the record show, despite my stated being 'of two minds' above (probably playing it safe, as per above too) that I have looked at the reactions by recipients of your cups of kindness, and have come to the conclusion that it was not disruptive, and that you should be allowed to continue. Floquenbeam makes a good point regarding User:MediaWiki message delivery who notifies everyone without being kind. ---Sluzzelin talk 19:50, 2 January 2023 (UTC)
- TY GoodDay, I am glad that I was able to spread some joy while I was before that I was blocked! I do hope to be able to continue sending some of these at least throughout the rest of this first week of the new year, but I will NOT do so unless I can get RoySmith to agree that it is not disruptive and that I will not be blocked again. Once I have that assurance, I will continue, through January 5th or 6th, and then I would be done for my greetings for 2023. That is my stated plan, and I would not proceed without the blessing of the community. :) — Moops ⋠T⋡ 19:25, 2 January 2023 (UTC)
- Didn't look like an unauthorised bot, so should not have been blocked without prior warning and explanation. I'm not actually sure what the blockworthy offence was here. —Kusma (talk) 19:25, 2 January 2023 (UTC)
- Personally, per NYB, I don't really think the banners were "disruptive" in any way. However, for some reason - possibly a world-wide deficit of peace on earth and goodwill towards man now that the holidays are over - there seems to be a consensus here that it was mildly disruptive. (Apparently, while it is vital to spam every talk page once a year about ArbCom elections, it is disruptive to once a year let people know they're valued). While I'm sad that there's an apparent consensus that something needed to be done, I'm glad that at least there's also a consensus that the instablock was an over-reaction. I'm going to offer Moops the option of an additional 1-second block to point to this consensus that the block was unnecessary, if he wants. Though if it was me, I wouldn't take that option, at least we can make it available. As someone who's been away from WP for a few weeks, I have to admit seeing this block at the top of my watchlist when I opened WP back up makes me slightly sad, and slightly less interested in keeping the WP tab open. --Floquenbeam (talk) 19:35, 2 January 2023 (UTC)
- Floquenbeam, if it were possible to remove the block from my block log, that is something that I would be very interested in. However an additional 1-second block does not seem to have value to me. Instead I wish that when unblocked, the original admin that blocked me would have mentioned the block as unnecessary. That would have perhaps have been of more value, but I do not know. I'll need to defer to the expertise of editors like yourself and other more senior editors. Part of my effort was intended to try and get to know some of the most productive editors of all time better, and spread joy to them, and in turn learn from them. I think the biggest issue was that I did this TOO QUICKLY, and thus appeared to look like a bot to RoySmith. I WOULD like to continue though, if approved by Roy and others, since I think 99.99% of people that received this greeting did NOT view it as disruptive, but were actually mostly glad and thanked me in various ways for thinking of them. :) — Moops ⋠T⋡ 19:41, 2 January 2023 (UTC)
- My advice would be to limit it to users you actually know. That way, there would be a rationale for who gets the messages, and that puts it more in keeping with the cultural norms around here and makes it less likely that you would annoy anyone. As for revising block logs, that's been discussed many times before, and it's just not going to happen. --Tryptofish (talk) 19:44, 2 January 2023 (UTC)
- Ugh, would be good if they eventually fell off too. Like after 3 years of no block activity, it automatically is deleted from your history. It feels like I am an 'felon' now with a 'permanent record', and even if it was for a mostly harmless 'offense'—or none at all depending on whom you ask above—it is still in my 'permanent record'... :(
- Thanks for everyone helping to cheer me up regarding this. It sure ruined my day in an awful way for a bit. I care way too much about this encyclopedia I guess, and I was just super excited for what we can build together in 2023. :) — Moops ⋠T⋡ 19:49, 2 January 2023 (UTC)
- My advice would be to limit it to users you actually know. That way, there would be a rationale for who gets the messages, and that puts it more in keeping with the cultural norms around here and makes it less likely that you would annoy anyone. As for revising block logs, that's been discussed many times before, and it's just not going to happen. --Tryptofish (talk) 19:44, 2 January 2023 (UTC)
- Floquenbeam, if it were possible to remove the block from my block log, that is something that I would be very interested in. However an additional 1-second block does not seem to have value to me. Instead I wish that when unblocked, the original admin that blocked me would have mentioned the block as unnecessary. That would have perhaps have been of more value, but I do not know. I'll need to defer to the expertise of editors like yourself and other more senior editors. Part of my effort was intended to try and get to know some of the most productive editors of all time better, and spread joy to them, and in turn learn from them. I think the biggest issue was that I did this TOO QUICKLY, and thus appeared to look like a bot to RoySmith. I WOULD like to continue though, if approved by Roy and others, since I think 99.99% of people that received this greeting did NOT view it as disruptive, but were actually mostly glad and thanked me in various ways for thinking of them. :) — Moops ⋠T⋡ 19:41, 2 January 2023 (UTC)
Oppose block. As an editor since 2005, and a former administrator, I would like to state that while I do find the practice of sending such greetings to several thousand editors with whom one has not previously interacted to be rather remarkable, and while I'm assuming that RoySmith was acting in good faith at the time, I don't think Moops should've been blocked for these, at least not without a warning, even if RoySmith thought at the time that Moops was using a bot. Thank you again for trying to spread some cheer, Moops. Have a safe and productive New Year. :-) Nightscream (talk) 19:54, 2 January 2023 (UTC)
- Thank you very much. I am without a doubt a bit of an odd duck, and can edit very, very fast... that said, I have no technical expertise of which to speak of and cannot use a bot even if I tried. I'd like to continue to spread joy with these messages if possible, but I'd like for RoySmith to state that he would not block me if I were to continue first, that way I do not incur TWO BLOCKS in a short period of time. I am distressed enough about ONE! :( — Moops ⋠T⋡ 19:58, 2 January 2023 (UTC)
- My dear Moops, we are all odd ducks, each of us in our own way ;-) Boing! said Zebedee (talk) 21:38, 2 January 2023 (UTC)
- TY very much again for the reassurance and kind words. Feel free to chime in on the Teahouse discussion I started around next steps. I'd love to be able to resume what I started, but I will NOT do so until there is consensus on that approval being granted—that way I am not blocked a SECOND time. I will abstain from sending 'Happy New Years' greetings until that is given, or if it is not clear that I can proceed, then I will simply leave the remainder of my list un-greeted for the New Year, sadly. :( — Moops ⋠T⋡ 21:46, 2 January 2023 (UTC)
- My dear Moops, we are all odd ducks, each of us in our own way ;-) Boing! said Zebedee (talk) 21:38, 2 January 2023 (UTC)
- Oh dear, what a terrible block. Is this what Wikipedia administration has come to? Clamping down on people trying to spread a bit of good cheer at the end of a truly shitty year, without even a word of attempted discussion first, and spoiling an otherwise clean block log? Moops, you have done absolutely nothing wrong, and I thank you for the bit of New Year kindness you showed me. The block is a disgrace, but nobody worth any respect will hold it against you. Boing! said Zebedee (talk) 21:24, 2 January 2023 (UTC)
- Your words are incredibly kind, and much appreciated. 2022 was indeed very shitty for me as well, as I had some personal trauma that I had to get past in a BIG way. That said, was delighted to have found in February of 2022 this great outlet of editing the encyclopedia and helping as best I could in what have been, until now, considered non-disruptive ways. Had I been warned too, I would have stopped sending these 'Happy New Year' greetings right away, but I was not. Is that standard practice? — Moops ⋠T⋡ 21:30, 2 January 2023 (UTC)
- No, it most definitely is not supposed to be standard practice! Boing! said Zebedee (talk) 21:42, 2 January 2023 (UTC)
- OK. TY — Moops ⋠T⋡ 21:44, 2 January 2023 (UTC)
- No, it most definitely is not supposed to be standard practice! Boing! said Zebedee (talk) 21:42, 2 January 2023 (UTC)
- Your words are incredibly kind, and much appreciated. 2022 was indeed very shitty for me as well, as I had some personal trauma that I had to get past in a BIG way. That said, was delighted to have found in February of 2022 this great outlet of editing the encyclopedia and helping as best I could in what have been, until now, considered non-disruptive ways. Had I been warned too, I would have stopped sending these 'Happy New Year' greetings right away, but I was not. Is that standard practice? — Moops ⋠T⋡ 21:30, 2 January 2023 (UTC)
- Bad block Per Nickscream and Zebedee. It's a shame that a clean block record has now been tarnished when RoySmith could have just sent Moops a message. Labelling it "disruption" is a bit tenuous. — Czello 21:35, 2 January 2023 (UTC)
- I do not want to now be accused of WP:CANVASSING, but I will just let everyone know that I am looking to now form consensus on whether or not I can continue over here at the Teahouse. Please contribute your voice. TY — Moops ⋠T⋡ 21:37, 2 January 2023 (UTC)
- To be clear. I also exercise caution as to whom I send a 'Happy New Year' too, and it is not simply 'everyone', but rather those editors that I deemed were most productive over these past years, and many of them by the rank of their edit counts. Though if an editor was 'retired', blocked, or otherwise inactive, they would likely not receive a 'Happy New Year' from me. My intention was, and is not, in any way, meant to be "disruptive editing" and I am still greatly distressed over having my perfect no-block record now tarnished with a dirty looking block as a result.
- I'd love to finish sending these to my list of some of the most productive editors if at all possible, I had not had even a single editor complain, until RoySmith, at which point it was too late. Since RoySmith did not warn me and simply reflexively blocked my account for an hour (though he promptly realized where the will of the community was and then unblocked me within minutes of having been blocked). TY — Moops ⋠T⋡ 21:43, 2 January 2023 (UTC)
- I've already said both here and at the Teahouse that I recommend against sending the messages to everyone who meets some criterion based upon edit counts, and instead focus on editors where you've had a personal (on-wiki) interaction. I know that one editor whose talk page is on my watchlist reverted the message, so there were at least a few editors who didn't want the messages. That's not at all in the same category as disruption, but it's a good reason to use some restraint. --Tryptofish (talk) 21:58, 2 January 2023 (UTC)
- I do not want to now be accused of WP:CANVASSING, but I will just let everyone know that I am looking to now form consensus on whether or not I can continue over here at the Teahouse. Please contribute your voice. TY — Moops ⋠T⋡ 21:37, 2 January 2023 (UTC)
- I want to make one other observation, lest this discussion go too far the other way. I do think that RoySmith was correct to initiate a block review here, implicitly recognizing that it might have been a mistake. We can be understanding, in both directions. --Tryptofish (talk) 22:04, 2 January 2023 (UTC)
- Oppose block, this block was a huge overreaction, IMO, especially when it was issued without any warning. Huldra (talk) 22:14, 2 January 2023 (UTC) PS: And a Happy New Year to all of you, too 😊
- Agree that action was needed but a warning with a requirement for a quick response should have been step 1. But thanks for doing what you thought was correct and needed and asking for a review of it. North8000 (talk) 22:27, 2 January 2023 (UTC)
- It doesn't seem that Moops was doing anything that was actually disruptive, so I'd say no action of any kind was warranted. That said, Roy is a good admin who deserves some credit for bringing this here, so let's not pile on him too harshly. LEPRICAVARK (talk) 22:39, 2 January 2023 (UTC)
Massive off-wiki campaign aimed at disrupting Wikipedia
editThe following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I noticed this Turkish-language Reddit link.[248]. It seems a massive off-wiki campaign has been initiated by Turkish-language speakers to create more disruption in the cesspool known as WP:AA2 and WP:KURDS. As the posts/comments were in Turkish, they were translated using Google tranlate:
- "The first spark was ignited in order to correct and organize the unfounded claims we have seen on Wikipedia recently. r/turkviki was established. Let's get organized from there."[249]
- "Friends, this subreddit was founded on the termination of unfounded claims made on Wikipedia. Our aim is to put an end to the unfounded allegations made on Wikipedia, the propaganda activities targeting our country and nation, to express the truth and correct the mistakes."[250]
- "we need a larger audience, salaried employees of wikipedia, and I don't know how effective we can be against the current Turkish hatred"[251]
- "Turkish Wikipedia Community Discord server. Friends, I left the link below if you would like to join the works that started before us."[252]
- "Friends, let's start with the liberation war first and let there be a spark of salvation for us from the lies in Wikipedia."[253]
- "First of all, we must explain why this claim [Armenian genocide] is not true. For example, instead of the 1.5 million people they said, there were actually 1.1 million Armenians living in the Ottoman Empire. There is no article about genocide against Armenians in the Treaty of Mudros Sevres or Lausanne. Until 1948, the United Nations and the League of Nations before it never defined a crime called genocide, and if you eat pizza and eat pizza in the future is a war crime, they cannot hold you guilty for what you did in the past. You can write that the deportation was carried out by the Union and Terraki and that the remaining Unionists completely severed their ties with the party at the Sivas congress, and the Parliament was against what the Committee of Union and Terraki did. In addition, we must reveal the evils committed by Armenians in the public opinion, instead of the crimes they have committed, the terrorist attacks of ASALA in Europe will be the best examples."[254]
- "Ottoman archives of the period are available on this site: Devletarsivleri.gov.tr (<cant post the entire link due to blockquote error>) It is enough for someone to translate it into Turkish for us to understand. then we edit the page on the wiki."[255]
- "The first thing that needs to be changed is the name. Then we will add the villages and towns burned by the Armenians. The number of people killed by Armenians is not specified. We should add them too. Let's diversify the missing parts as comments. Good luck with."[256]
- "A patrol is here! hello, i am zemxer from turkish wikipedia. As I'm on patrol on Turkish Wikipedia, I try to help new users as much as possible. You know, there is an approval system for the contributions made in Turkish Wikipedia, and I am one of the patrol friends who approve these contributions. I can help users and groups who want to contribute to Wikipedia and who want to make these contributions in an impartial framework. good wikis"[257]
So this group of people 1) clearly state their intention to spread Turkish government propaganda at Eng.Wikipedia disproven by the rest of the world 2) They receive support from users at the Turkish Wikipedia. Posting it here at AN as suggested by several administrators. You might be interested in this: @Rosguill: @Buidhe: @Bbb23: @Seraphimblade: @Black Kite: @Deepfriedokra: @Johnuniq: @HistoryofIran: @Dennis Brown: @Drmies: @El C: @Khirurg: @Kansas Bear: @Cplakidas: - LouisAragon (talk) 12:03, 15 October 2022 (UTC)
- Noting this is still ongoing, see Vahakn Dadrian and its abuse log. DatGuyTalkContribs 15:36, 11 November 2022 (UTC)
- Same here Second Perso-Turkic War, where a stream of new accounts are making nationalistic edits. I am also still occasionally reporting new socks, just see the now larger SPI archive of one the discord members for example (Wikipedia:Sockpuppet investigations/Beyoglou/Archive). --HistoryofIran (talk) 21:45, 16 December 2022 (UTC)
The discord server
editWhen looking at the members of their discord, I noticed a person named "Berk". He has a portrait of Ulugh Beg as his discord profile picture, the very same added by one of our own Wikipedians, BerkBerk68, here [258]. In other words, they must be the same person. BerkBerk seems to have a prominent role there, as he has published the rules of the discord. This is not the first time user:BerkBerk has participated in off-wiki canvassing through Discord, see for example these two posts back in July 2021, where user:BerkBerk tried to recruit an admin to his "14 people" discord, which was apparently focused on editing the Syrian Civil War and 2020 Nagorno-Karabakh War. [259]-[260]- LouisAragon (talk) 12:03, 15 October 2022 (UTC)
- Note the date 27-06-2022 at Discord:[261] Seems there's a triad involving editors at the Turkish wiki, off-wiki people, and editors at Eng.Wiki. - LouisAragon (talk) 12:03, 15 October 2022 (UTC)
- @LouisAragon, this report may have all kinds of merit, but doesn't the "The discord server" bit inch into WP:OUTING? Gråbergs Gråa Sång (talk) 13:15, 15 October 2022 (UTC)
- Berk#2835 is me, and that community has permission from authorities of Turkish Wikipedia, and it is not interested in English Wikipedia editing. Many experienced/authorized Turkish-language editors are in that group, furthermore I am not the owner of that server. I undertake all the mistakes done by me at "discord" one year ago. BerkBerk68 13:18, 15 October 2022 (UTC)
- Why am I not surprised to see you engaging in this kind of stuff again. Not interested in English Wikipedia editing? What is this you have written under Planlama ("Planning") then? Google Translate "Users will be divided into 2 main sectors as English and Turkish Writers. It is obligatory to make a total of 100 edits, 60 from one sector and 40 from another sector, on behalf of users who want to participate in both. When the new week is started, the number of edits between sectors (60-40) may change." I did write a similar report about BerkBerk to ArbCom sometime ago, though I am still awaiting an update. --HistoryofIran (talk) 13:26, 15 October 2022 (UTC)
- I invite administrators to the discord server to prove that there is not any single edit provoked by me in english wikipedia, everything asked will be translated by me, and for any kind of distrust, access to server logs (+ProBot for deleted messages) will be given. BerkBerk68 13:35, 15 October 2022 (UTC)
- The discord link here just got deleted [262] (including the user who posted it) and the discord is now gone. Something you and co. trying to hide? Fortunately I took pictures of BerkBerk's "Planning" list before hand. Would it violate WP:OUTING to post it here? --HistoryofIran (talk) 13:39, 15 October 2022 (UTC)
- that text is not written by me, the person who writed it wanted me to post it (I understand the reason now), the planning list is already posted and I have opposed the things going on reddit on that server aswell. BerkBerk68 13:42, 15 October 2022 (UTC)
- Kutlug Şad — 13.10.2022 O zaman r/Turkviki başlı başına canlı kuklacılık ("Then r/Turkviki is completely meatpuppet") Berk (me) — 13.10.2022 Öyle zaten ("it is, already") Kutlug Şad also posts a screenshot showing him posting a nationalistic comment, calling reddit users to the discord and asks me about it, I told him "don't". BerkBerk68 13:44, 15 October 2022 (UTC)
- again, all logs and messages will be opened for Administrators. I have never motivated anyone to make any edits on English Wikipedia on that server. BerkBerk68 13:45, 15 October 2022 (UTC)
- So.. you wrote for the sake of someone else? Honestly, your excuses bore me. Prepare to make more, as this is not even scrapping the barrel. As I said, I also have that huge ArbCom report of you. Not to mention you have been called out for nationalistic editing or similiar by other users than me. Let's not forget my previous ANI report of you either. --HistoryofIran (talk) 13:45, 15 October 2022 (UTC)
- I have found messages of the owner sending me the text in order to publish it on server at 27.06.2022. since "discord screenshots" can't be used here, I will post it when its necessary. BerkBerk68 16:39, 22 October 2022 (UTC)
- I strongly urge you (both) to only send any personal data like that to ArbCom — posting screenshots/text or anything that someone could argue is personal data will, at the very least, cause drama. The back and forth here is unlikely to resolve the issue, given that it appears to depend on this private evidence. — TheresNoTime (talk • they/them) 17:49, 22 October 2022 (UTC)
- I have found messages of the owner sending me the text in order to publish it on server at 27.06.2022. since "discord screenshots" can't be used here, I will post it when its necessary. BerkBerk68 16:39, 22 October 2022 (UTC)
- So.. you wrote for the sake of someone else? Honestly, your excuses bore me. Prepare to make more, as this is not even scrapping the barrel. As I said, I also have that huge ArbCom report of you. Not to mention you have been called out for nationalistic editing or similiar by other users than me. Let's not forget my previous ANI report of you either. --HistoryofIran (talk) 13:45, 15 October 2022 (UTC)
- its not just me, but also another experienced editor pings 2 other editors including me, asking if that would be "meatpuppet". and I respond: "it would absolutely be called that because it is". messages at 13.10.2022 proves that I am blaming that subreddit. BerkBerk68 13:50, 15 October 2022 (UTC)
- again, all logs and messages will be opened for Administrators. I have never motivated anyone to make any edits on English Wikipedia on that server. BerkBerk68 13:45, 15 October 2022 (UTC)
- Kutlug Şad — 13.10.2022 O zaman r/Turkviki başlı başına canlı kuklacılık ("Then r/Turkviki is completely meatpuppet") Berk (me) — 13.10.2022 Öyle zaten ("it is, already") Kutlug Şad also posts a screenshot showing him posting a nationalistic comment, calling reddit users to the discord and asks me about it, I told him "don't". BerkBerk68 13:44, 15 October 2022 (UTC)
- @HistoryofIran Per Wikipedia:Village pump (policy)/Archive 169#Discord logs Posting discord logs on wiki is oversightable. Email them to arbcom. 192.76.8.81 (talk) 13:46, 15 October 2022 (UTC)
- I see. The issue is that it (respectfully) takes too long if I message ArbCom. They still haven't updated me regarding the ArbCom report of Berkberk, which I sent two months ago. --HistoryofIran (talk) 13:49, 15 October 2022 (UTC)
- @HistoryofIran: If you believe there's action that ArbCom can take, I'd suggest starting a case request — just ensure you keep the right side of WP:OUTING etc, and (re-)email the committee the private evidence — TheresNoTime (talk • they/them) 18:02, 21 October 2022 (UTC)
- I see. The issue is that it (respectfully) takes too long if I message ArbCom. They still haven't updated me regarding the ArbCom report of Berkberk, which I sent two months ago. --HistoryofIran (talk) 13:49, 15 October 2022 (UTC)
- that text is not written by me, the person who writed it wanted me to post it (I understand the reason now), the planning list is already posted and I have opposed the things going on reddit on that server aswell. BerkBerk68 13:42, 15 October 2022 (UTC)
- The discord link here just got deleted [262] (including the user who posted it) and the discord is now gone. Something you and co. trying to hide? Fortunately I took pictures of BerkBerk's "Planning" list before hand. Would it violate WP:OUTING to post it here? --HistoryofIran (talk) 13:39, 15 October 2022 (UTC)
- I invite administrators to the discord server to prove that there is not any single edit provoked by me in english wikipedia, everything asked will be translated by me, and for any kind of distrust, access to server logs (+ProBot for deleted messages) will be given. BerkBerk68 13:35, 15 October 2022 (UTC)
- Why am I not surprised to see you engaging in this kind of stuff again. Not interested in English Wikipedia editing? What is this you have written under Planlama ("Planning") then? Google Translate "Users will be divided into 2 main sectors as English and Turkish Writers. It is obligatory to make a total of 100 edits, 60 from one sector and 40 from another sector, on behalf of users who want to participate in both. When the new week is started, the number of edits between sectors (60-40) may change." I did write a similar report about BerkBerk to ArbCom sometime ago, though I am still awaiting an update. --HistoryofIran (talk) 13:26, 15 October 2022 (UTC)
- Based on the evidence already provided in this thread regarding how this Discord group has been advertised and coordinated on Reddit, specifically taking issue with content on en.wiki, I don't buy the claim that this is unrelated to en.wiki editing. Frankly, the rhetoric surrounding this group online is WP:RGW and vitriolic enough that I would have serious concerns about them even operating as a group on tr.wiki; there may be a case for starting a discussion on Metawiki. signed, Rosguill talk 16:39, 15 October 2022 (UTC)
- You are openly invited to the aforementioned group to see the proofs of my opposition on the subreddit. messages there are clearly showing that individuals wanted to support the subreddit and to invite reddit users while experienced editors including me opposed that. it would also prove the fact that I have never encouraged/supported anyone to edit on english wikipedia. BerkBerk68 18:01, 15 October 2022 (UTC)
- Could you more clearly explain what the purpose of this Discord group is? Setting aside your specific participation, what is the purpose of the group, and why has it been promoted on reddit forums in the highly combative manner detailed by LouisAragon in the first part of this discussion? signed, Rosguill talk 22:07, 15 October 2022 (UTC)
- The fact that both the Discord and Reddit sub-forum are now private makes BerkBerk's claim even less believable. I also still have that screenshot of his "Planning" message if an admin is interested. --HistoryofIran (talk) 17:52, 21 October 2022 (UTC)
- Actually, according to this post from 9 days ago, the privating the subreddit was something planned in advance, so. That's on me. ~StyyxTalk? 23:24, 21 October 2022 (UTC)
- Ah, glad to see. Some users think that I am managing a whole reddit group despite I have opposed that group days ago. BerkBerk68 15:29, 22 October 2022 (UTC)
- Actually, according to this post from 9 days ago, the privating the subreddit was something planned in advance, so. That's on me. ~StyyxTalk? 23:24, 21 October 2022 (UTC)
- promotions were made by different users and multiple experienced users including me thought that it would be meatpuppetry and opposed that (as it could be seen on the server messages including the meatpuppet expression). The general thought of the community is that Turkish community on Wikipedia have been regressed a lot due to the disgusting decision of Turkish government on blocking Wikipedia, and therefore source interpretation has changed a lot, which I totally agree with that. BerkBerk68 15:27, 22 October 2022 (UTC)
Turkish community on Wikipedia have been regressed a lot due to the disgusting decision of Turkish government on blocking Wikipedia, and therefore source interpretation has changed a lot, which I totally agree with that
, this does not allay concerns that the discord is operating as a POV-pushing platform. Additionally, your position in this thread is that there is a subset of people involved with the discord that have been publicizing it improperly, against your advice and against the intent of the server in the first place, would be a lot more convincing if you identified the black-hat editors misusing the discord so that we could investigate and address their malfeasance. signed, Rosguill talk 15:39, 22 October 2022 (UTC)- ofcourse, the user that I have warned about this situation is Kutlug Şad as I explained above. BerkBerk68 16:23, 22 October 2022 (UTC)
- The fact that both the Discord and Reddit sub-forum are now private makes BerkBerk's claim even less believable. I also still have that screenshot of his "Planning" message if an admin is interested. --HistoryofIran (talk) 17:52, 21 October 2022 (UTC)
- Could you more clearly explain what the purpose of this Discord group is? Setting aside your specific participation, what is the purpose of the group, and why has it been promoted on reddit forums in the highly combative manner detailed by LouisAragon in the first part of this discussion? signed, Rosguill talk 22:07, 15 October 2022 (UTC)
- You are openly invited to the aforementioned group to see the proofs of my opposition on the subreddit. messages there are clearly showing that individuals wanted to support the subreddit and to invite reddit users while experienced editors including me opposed that. it would also prove the fact that I have never encouraged/supported anyone to edit on english wikipedia. BerkBerk68 18:01, 15 October 2022 (UTC)
There's some POV editing happening right now at Karapapakhs, who were renamed to "Karapapakhs Turks" by some IPs and a new account. Drmies (talk) 21:05, 15 October 2022 (UTC)
- Have seen a large increase in dubious editing on Turkic history-related articles recently. I asked for a sockpuppet investigation into one because I thought edits were too similar. However, accounts coordinating off-wiki could very possibly be another solution. ~~ AirshipJ29 (talk) 00:17, 17 October 2022 (UTC)
- Two brand new users are currently engaging in POV editing at Seljuk Empire, attempting to remove 7k sourced information through edit warring. This is not good. --HistoryofIran (talk) 15:44, 24 October 2022 (UTC)
Aaand r/Turkviki has been made private by its moderators.~StyyxTalk? 17:07, 18 October 2022 (UTC)- My screenshot of BerkBerk's "Planning" comment also shows a certain user (who has the role of "Yönetici", meaning "Executive"), that is User:Beyoglou. A notorious xenophobic pan-nationalist and sock (Wikipedia:Sockpuppet investigations/Beyoglou/Archive), whom BerkBerk has claimed that he has "no relation to" [263] and has tried to defend [264]. Yet they are in the same discord, curious. Not to mention some of Beyoglou's socks have come to the aid of BerkBerk several times. Again, I have all kinds of proof to back this up, but WP:OUTING is not making this easy. I would prefer to send this to an admin who would be willing to make a quick judgement of this, rather than ArbCom. Though if I have no choice, I will send it to the latter. This connects rather too well with my current ArbCom report of BerkBerk. --HistoryofIran (talk) 12:12, 25 October 2022 (UTC)
- Individual administrators aren't allowed to act on non-public evidence. It has to be ArbCom for something like this. – Joe (talk) 12:14, 25 October 2022 (UTC)
- Thanks, I have sent it all to ArbCom and asked them about an update regarding my other report. However, I do think some sort of action or actions needs to be taken here, as this is very concerning. We can't just sit idle. --HistoryofIran (talk) 14:09, 27 October 2022 (UTC)
- Individual administrators aren't allowed to act on non-public evidence. It has to be ArbCom for something like this. – Joe (talk) 12:14, 25 October 2022 (UTC)
- I've gone ahead and blocked BerkBerk68. If y'all have a clue as to other editors I should block based on this matter, ping me. CaptainEek Edits Ho Cap'n!⚓ 19:31, 27 October 2022 (UTC)
- Was that an action based on private evidence (as you mention on the user's talk page) provided to ArbCom? If so, we can assume this was a block made in your capacity as an arbitrator (given that you wouldn't have access to that private evidence were you not one), and not a "standard functionary" — correct? — TheresNoTime (talk • they/them) 20:30, 27 October 2022 (UTC)
- @TheresNoTime Ya know, that is a good question. I'm not 100% sure of that answer? I don't think it can be a block in my capacity as an Arb, because individual Arbs can't place blocks. An ArbCom block is by its nature a block by the committee and we only place them after a vote. So I think it must be a block in my capacity as an individual func. I asked that question of another Arb before I blocked, since I too wondered that, and they were also of the opinion that I could use the info ArbCom had been emailed to make an individual block. We do that from time to time with other matters: we get emailed something that really doesn't need the whole committee to waste its time on it, so one of us will just do it as an individual admin action. CaptainEek Edits Ho Cap'n!⚓ 08:15, 28 October 2022 (UTC)
- An individual admin action based on private evidence that no other admin/functionary (other than those on the committee) can verify/review? Doesn't that sound incredibly close to a recent discussion.. perhaps the community needs to be consulted on if they're happy for these actions to take place. I'm certainly not, and would expect our arbs to use a bit of common sense. — TheresNoTime (talk • they/them) 08:18, 28 October 2022 (UTC)
- I read that RfC as saying that individual admins couldn't make those blocks, but individual CU/OS could, or of course ArbCom. So unless I've misinterpreted that RfC, I don't see how taking the action as an individual CU is an issue? CaptainEek Edits Ho Cap'n!⚓ 08:27, 28 October 2022 (UTC)
- I thought the whole point with allowing that was private evidence was available for review by those with relevant access (i.e., all functionaries can review the private evidence which led to an action being taken)? Seeing as all functionaries are unable to review this evidence, and this wasn't an action by an arbitrator, all I can see is that you've decided to make a block based off of this thread. Perhaps that's warranted, I don't particularly care, but I definitely do care about ArbCom making somewhat secret decisions but enacting them in their private capacity. Whom do we hold accountable, the committee or the arb? How can we review an unblock request in this case? Do we contact the committee, or you? Why didn't ArbCom forward this evidence to the checkuser list when it decided it as an entity didn't want to do anything with it? These are worrying questions, and the community deserves transparency in how often this happens. — TheresNoTime (talk • they/them) 08:39, 28 October 2022 (UTC)
- I read that RfC as saying that individual admins couldn't make those blocks, but individual CU/OS could, or of course ArbCom. So unless I've misinterpreted that RfC, I don't see how taking the action as an individual CU is an issue? CaptainEek Edits Ho Cap'n!⚓ 08:27, 28 October 2022 (UTC)
- An individual admin action based on private evidence that no other admin/functionary (other than those on the committee) can verify/review? Doesn't that sound incredibly close to a recent discussion.. perhaps the community needs to be consulted on if they're happy for these actions to take place. I'm certainly not, and would expect our arbs to use a bit of common sense. — TheresNoTime (talk • they/them) 08:18, 28 October 2022 (UTC)
- @TheresNoTime Ya know, that is a good question. I'm not 100% sure of that answer? I don't think it can be a block in my capacity as an Arb, because individual Arbs can't place blocks. An ArbCom block is by its nature a block by the committee and we only place them after a vote. So I think it must be a block in my capacity as an individual func. I asked that question of another Arb before I blocked, since I too wondered that, and they were also of the opinion that I could use the info ArbCom had been emailed to make an individual block. We do that from time to time with other matters: we get emailed something that really doesn't need the whole committee to waste its time on it, so one of us will just do it as an individual admin action. CaptainEek Edits Ho Cap'n!⚓ 08:15, 28 October 2022 (UTC)
- Was that an action based on private evidence (as you mention on the user's talk page) provided to ArbCom? If so, we can assume this was a block made in your capacity as an arbitrator (given that you wouldn't have access to that private evidence were you not one), and not a "standard functionary" — correct? — TheresNoTime (talk • they/them) 20:30, 27 October 2022 (UTC)
- I disagree, so have opened a dedicated thread below. Thanks. — TheresNoTime (talk • they/them) 08:52, 28 October 2022 (UTC)
- Thanks, CaptainEek. I will soon make a (probably unpopular) proposal here on how we can deal with this massive off-Wiki campaign, I would appreciate to hear what you all think of it. We shouldn't take this matter lightly one bit imo. Before the Reddit got private, there were like 400 members. --HistoryofIran (talk) 23:02, 28 October 2022 (UTC)
:"I believe this all goes back to the current massive off-wiki campaign aimed at disrupting Wikipedia, which Beyoglou plays a leading part in."There is a massive witchhunt going against a lot of person has nothing to do with our so called "massive discord group". I don't even know any of the banned user excluding my sockpuppet "Crasyy". But as I said they try to accuse all vandals and newcomers on Turkish-topics of being meat puppet and related to our "pan-nationalist" group and block them. It's a concerning situation when it comes to newcomer users who try to edit Turkey related topics. when some of the users that making witch hunt against us notice these newcomers, will try to ban them with accusation of relating to us. Is creating Wikipedia-related community and editing Wikipedia illegal according to policies? Absouletly not. But when it comes to some idiotic teenagers in reddit that has nothing related to us, they made our discord group "Pan-Nationalistic", "Xenophobic". 95.70.214.41 (talk) 14:19, 10 November 2022 (UTC)For example under this comment a user named "Nyhtar" says "They are even disrupting article not related to WP:KURDS". A random vandal changes "Russian" with Kurdish and accused to be in one of these groups.@TheresNoTime:@CaptainEek: and other users who involved. 95.70.214.41 (talk) 14:35, 10 November 2022 (UTC)<--- blocked sock of User:Beyoglou
- (Writing so thread doesn't get archived tomorrow). --HistoryofIran (talk) 19:35, 5 December 2022 (UTC)
- Ditto. --HistoryofIran (talk) 02:04, 24 December 2022 (UTC)
- (Writing so thread doesn't get archived tomorrow). --HistoryofIran (talk) 19:35, 5 December 2022 (UTC)
Proposal
edit- Proposal: WP:ARBECR (which includes a 500edits/30days restriction) over WP:AA2 and WP:KURDS articles.
As LouisAragon rightly put it, the WP:AA2 and WP:KURDS is a cesspool, and it's not going to get better anytime soon, especially with these massive off-wiki campaigns. In my 10 years on this site, the vast majority of IPs and brand new users in this area have been WP:NOTHERE, often ending up getting indeffed for pov editing and/or egregious attacks. It's also too easy for these troublemakers to sock nowadays, it's almost laughable. For example, see this long SPI archive [265] of the notorious sock Aydın memmedov2000, which doesn't even show all of their socks, there are even more of this person here [266]. Sadly that's just one of many cases. It would alleviate so much time and stress on Wikipedia if we implemented at least some sort of restriction in this area. --HistoryofIran (talk) 00:30, 1 November 2022 (UTC)
- I concur with HistoryofIran that there are too many LTAs in WP:AA2 (I can't speak for WP:KURDS) and that something needs to be done to address this. Aside from the LTA HistoryofIran mentioned above, there are 2 additional LTAs (1 & 2) whose socks I must report at least once or twice each month. It's extremely rare for a new account or IP in AA2 to make a helpful edit; instead, 99% of the time, they only do so to vandalise or promote a POV. I think the requirement of 500 edits and 30 days (which could possibly be lowered to 200-300 edits and 15 days) is a good idea to address this problem, so I support it. — Golden call me maybe? 10:44, 1 November 2022 (UTC)
- Support Yes, for both. There's so much disruption in these areas, I'm surprised we don't already have a good enough restriction on them. Nythar (💬-🎃) 22:39, 1 November 2022 (UTC)
- Support applying WP:ARBECR to AA2 and KURDS. Levivich (talk) 16:27, 3 November 2022 (UTC)
- Support something needs to be done concerning the flood of IPs and sockpuppets. The AA2 area is continuously being disrupted by the socks of Aydın memmedov2000, Beyoglou, Steverci. And a listing of disruption for the last 3 yrs: 2022 disruption 2021 disruption, 2020 disruption. I think this says it all. --Kansas Bear (talk) 18:45, 6 November 2022 (UTC)
- If anyone needs further evidence, check out the
8910 reverts by an IP at the Orontid dynasty. --Kansas Bear (talk) 03:31, 13 November 2022 (UTC)
- If anyone needs further evidence, check out the
- Support Clearly something needs to be done here. Hemiauchenia (talk) 17:53, 7 November 2022 (UTC)
- Support Surely something must need to be done about this disruption. --Magnatyrannus (talk | contribs) 22:22, 7 November 2022 (UTC)
- Support Very sensible proposal to reduce the disruption. Khirurg (talk) 23:59, 7 November 2022 (UTC)
- Support Long, long overdue. - LouisAragon (talk) 15:30, 10 November 2022 (UTC)
- Support the disruption is only ever going to grow, and it's already at unsustainable levels. ~~ AirshipJungleman29 (talk) 19:44, 10 November 2022 (UTC)
- Support Even though this won't stop them, it will certainly hinder their disruptive activity. Demetrios1993 (talk) 21:08, 10 November 2022 (UTC)
- Support Clearly there is almost no good activity by IPs and plenty of autoconfirmed socks. This is probably the most effective remedy. ‡ The Night Watch ω (talk) 19:01, 11 November 2022 (UTC)
- @HistoryofIran: I have no opinion on the proposal but would suggest replacing "500edits/30days restriction" with "extended-confirmed restriction" – WP:ECR was carefully drafted specifically to address the nuances of applying a topic-wide 500/30 restriction. Best KevinL (aka L235 · t · c) 19:56, 11 November 2022 (UTC)
- I see, so it's more or less the same as my proposal, but also takes cares of other details related to it. Thanks, I have slightly reworded my proposal. --HistoryofIran (talk) 23:31, 11 November 2022 (UTC)
- Support, this is a good idea considering what I've seen when patrolling vandalism. LilianaUwU (talk / contribs) 23:35, 11 November 2022 (UTC)
- Support, Disruptive IPs and socks are becoming a big nuisance for the AA2 area, with experienced editors spending significant time protecting the articles from the never-ending flow of IPs, socks, and new accounts, when they could be spending it more efficiently. Yes, it will affect new editors who have good intentions, however, I believe it is better for them if they do not begin their editing in intense editing areas such as AA2. So, I fully support proposed initiative. A b r v a g l (PingMe) 06:18, 13 November 2022 (UTC)
- Support, but only for ethnic or political topics in this area. Under the current scope of AA2, an article about an Armenian railroad would be covered by the sanctions, but ECP would be counterproductive unless the railroad has a significant role in an ethnic conflict, or a non-ECP user has repeatedly added ethnic fanaticism to the article. –LaundryPizza03 (dc̄) 10:53, 13 November 2022 (UTC)
- Support per constant disruption/vandalism by IPs on AA2 topic area. – Olympian loquere 06:23, 15 November 2022 (UTC)
- Query I'm not against applying WP:ARBECR, but it seems to me this is an ArbCom-level restriction that needs to be applied, not one that we can do via WP:AN based on its phrasing. I support its implementation, but there appear to be some bureaucratic hurdles we should clarify. Buffs (talk) 22:02, 16 November 2022 (UTC)
- Wikipedia:General sanctions#Community sanctions says the community can impose any general sanctions it wants, and can (and has) made its general sanctions identical in substance to sanctions imposed under ArbCom's procedures. That's if it wishes to, of course; the community is "not bound by Arbitration Committee procedures and guidelines" when imposing these general sanctions. Best, KevinL (aka L235 · t · c) 22:58, 16 November 2022 (UTC)
- This overwhelming support surely is more than enough for the WP:ARBECR to be implemented? --HistoryofIran (talk) 21:10, 19 November 2022 (UTC)
- Only if you're brave enough for the WP:ARCA template, which no one is. Otherwise, it'll probably have to be set up (i.e. split) into something like WP:ARBEE → WP:GS/RUSUKR. HTH. El_C 23:03, 19 November 2022 (UTC)
- @El C: I'm sorry, but I'm not sure I understand. Are there even more steps required to go through with this? Weren't we only supposed to vote for it? --HistoryofIran (talk) 23:02, 20 November 2022 (UTC)
- @El C: I understood this proposal to be for establishing ECR as a community-imposed general sanction. That would not require ArbCom action, if I'm understanding correctly. @HistoryofIran: I recommend posting at Wikipedia:Closure requests. Best, KevinL (aka L235 · t · c) 23:04, 20 November 2022 (UTC)
- I'm not sure why you'd think that, Kevin, when the proposal plainly says:
WP:ARBECR [...] over WP:AA2 and WP:KURDS
. Now, asking the Committee at ARCA to consider doing that, as is the intent here, ought to be relatively straight forward when such overwhelming consensus has been gathered. Had I not been so lazy (I mean, the ARCA template isn't that hard) and likewise anyone else bothering, RUSUKR probably would have passed by motion as +ARBEE. The overall trend has been to streamline (subsume), like with WP:GS/COVID19 → WP:ARBCOVID; WP:GS/IPAK → WP:ARBPAK; WP:GS/IRANPOL → WP:ARBIRP; and so on. - To me, personally, it's more or less all the same (even when inelegant), but beyond that, I think it would make sense to have something along the line of clerks assisting users, who, like in this instance, were able to accomplish community consensus for their proposal to add/adjust an existing ArbCom sanctions regimes. To help them file the paperwork, as it were. Because the less of an access ceiling, the better, I'm sure you'd agree. And all of this as we are in flux. El_C 01:54, 21 November 2022 (UTC)
- The confusion about this proposal may be my fault. Before my comment here, the proposal was for "500edits/30days restriction over" the articles. I suggested changing it to WP:ECR, which describes more nuances and implementing rules. My thought was that the community would implement the restriction itself, not that it would ask ArbCom to do so. Best, KevinL (aka L235 · t · c) 14:55, 21 November 2022 (UTC)
- Sorry, I'm not following. What I quoted (the proposal: WP:ARBECR [...] over WP:AA2 and WP:KURDS) was from Nov 1; your comment to whch you link is from Nov 11. The two Arbcom sanctions regimes mentioned in the proposal, WP:AA2 and WP:KURDS, are ones that many of the users supporting the proposal are already accustomed to (to whichever extent). What would be the benefit of adding a third sanctions regime, except this time making it WP:GS instead of WP:ACDS? Would it not make more sense to just amend AA2/KURDS, instead of overcomplicating everything with a new log, new alerts and page notices, new thing to remember? Thwink about it! El_C 16:42, 21 November 2022 (UTC)
- Sorry guys, but I am even more lost now. Is there a tutorial somewhere for dummies that I can follow? I wanna proceed as soon as possible, especially since the numbers of socks are slowly ramping up. --HistoryofIran (talk) 23:23, 21 November 2022 (UTC)
- That's exactly what I've been trying to work towards in my comments above (and elsewhere), HistoryofIran. I wish Kevin would have addressed my point about this
access ceiling
. Oh well, maybe next time. El_C 23:28, 21 November 2022 (UTC)
- That's exactly what I've been trying to work towards in my comments above (and elsewhere), HistoryofIran. I wish Kevin would have addressed my point about this
- El C, the original proposal was for a 500 edits/30 days restriction, as seen in this diff provided by Kevin. This was overwritten later, following Kevin's comment. Can we please get the administrative and bureaucratic eccentricities out of the way, and have some sort of action on the problem? ~~ AirshipJungleman29 (talk) 12:56, 22 November 2022 (UTC)
- I'm not preventing you from doing anything, least of all read what I had written. El_C 13:36, 22 November 2022 (UTC)
- Sorry guys, but I am even more lost now. Is there a tutorial somewhere for dummies that I can follow? I wanna proceed as soon as possible, especially since the numbers of socks are slowly ramping up. --HistoryofIran (talk) 23:23, 21 November 2022 (UTC)
- Sorry, I'm not following. What I quoted (the proposal: WP:ARBECR [...] over WP:AA2 and WP:KURDS) was from Nov 1; your comment to whch you link is from Nov 11. The two Arbcom sanctions regimes mentioned in the proposal, WP:AA2 and WP:KURDS, are ones that many of the users supporting the proposal are already accustomed to (to whichever extent). What would be the benefit of adding a third sanctions regime, except this time making it WP:GS instead of WP:ACDS? Would it not make more sense to just amend AA2/KURDS, instead of overcomplicating everything with a new log, new alerts and page notices, new thing to remember? Thwink about it! El_C 16:42, 21 November 2022 (UTC)
- The confusion about this proposal may be my fault. Before my comment here, the proposal was for "500edits/30days restriction over" the articles. I suggested changing it to WP:ECR, which describes more nuances and implementing rules. My thought was that the community would implement the restriction itself, not that it would ask ArbCom to do so. Best, KevinL (aka L235 · t · c) 14:55, 21 November 2022 (UTC)
- I'm not sure why you'd think that, Kevin, when the proposal plainly says:
- @El C: I understood this proposal to be for establishing ECR as a community-imposed general sanction. That would not require ArbCom action, if I'm understanding correctly. @HistoryofIran: I recommend posting at Wikipedia:Closure requests. Best, KevinL (aka L235 · t · c) 23:04, 20 November 2022 (UTC)
- @El C: I'm sorry, but I'm not sure I understand. Are there even more steps required to go through with this? Weren't we only supposed to vote for it? --HistoryofIran (talk) 23:02, 20 November 2022 (UTC)
- Only if you're brave enough for the WP:ARCA template, which no one is. Otherwise, it'll probably have to be set up (i.e. split) into something like WP:ARBEE → WP:GS/RUSUKR. HTH. El_C 23:03, 19 November 2022 (UTC)
- Support because of constant sockpuppeting. ZaniGiovanni (talk) 11:32, 21 November 2022 (UTC)
- Oppose even though I know that this isn't going to have an effect. When I created what would become ECP in 2015, it was meant to be a last-ditch creative effort to stop the highest-level of disruption on the project. I feel that this proposal rolls it out to a far too broad array of articles while lesser remedies have yet to be tried. --Guerillero Parlez Moi 20:55, 26 November 2022 (UTC)
- Oppose per Guerillero and my comments at WP:ARCA. ProcrastinatingReader (talk) 22:27, 26 November 2022 (UTC)
- Support. Nominator has given definitive proof that too many IPs and accounts have disrupted Kurdish-related articles for many years. Some personal experience at Southern Kurdish. ~~lol1VNIO🎌 (I made a mistake? talk to me) 07:50, 29 November 2022 (UTC)
- Potential oppose, potential support - I am reticent to support an automatic major restriction on such a scale as the entire (amended as of 2013) AA2 scope. I'm aware, of course, of the gaming risk, but I don't think we'd ever endorse such an action were there (say) a dispute nexus between the US and UK. I would support this restriction on the conflict between the two countries (broadly construed, by all means), but opppose a restriction on the individual countries and their topics. Nosebagbear (talk) 10:27, 29 November 2022 (UTC)
- Oppose applying restrictions on the entire AA2 scope, per statistics below. Undecided on narrower restrictions, and restrictions on WP:KURDS. BilledMammal (talk) 02:25, 30 November 2022 (UTC)
- Oppose general ECP. When we're ECPing an area, we should be doing so only if it is a narrowly-tailored way to prevent future disruption. The arguments above note that the locus of the disruption is threefold: the first is that there are a number of disruptive IPs, the second is that there is general problems newer editors and the third is that there is socking going on. For the first issue, semi-protection would solve this quite easily; we don't need ECP to protect a topic area from disruptive IP editors. For the second, if the concern is new (canvassed) editors, then ECP isn't required to weed them out; semi-protection would likely serve as enough of a barrier to disruption that people would not be able to enter the topic spontaneously and begin to disrupt articles. For the third case, I do not see substantial evidence that long-term persistent sockmasters are deterred by ECP requirements; IceWhiz, NoCal100, and יניב הורון all still sock in the Israeli-Palestinian conflict area, and frankly I don't see why this is going to be different. That being said, semi-protection would well-address most forms of disruption in this area, and I might be able to get behind a 1-year semi-protection in the area. To paraphrase El_C's close of this 2021 discussion, I'm not seeing the reasons for why ECP should supersede a testing-the-waters semi-protection in this topic area, especially when the majority of the complaints are about IP editors doing the disruption. — Red-tailed hawk (nest) 06:17, 30 November 2022 (UTC)
- Oppose I can see the merits of both arguments. I think semi-protection is likely the better option; if the socks are that determined, they'll simply stick around for the 30 days/500 edit requirements before starting again. Semi-protection works best in my mind and tends to prevent these "hit and run" vandalism efforts where they only change a few words here and there rather than substantially blanking/re-writing sections in an article. Oaktree b (talk) 19:57, 6 December 2022 (UTC)
- Support – I trust the rationale and evidence provided by numerous experienced editors in these topic areas. Aza24 (talk) 09:44, 12 December 2022 (UTC)
- Support Eurasian and Turkic-related topics have long been subjected to disruption by IPs and new users, often socks or meat puppets with agendas. This will help prevent that.--Ermenrich (talk) 19:23, 16 December 2022 (UTC)
subjected to disruption by IPs and new users
then so would semi-protection? ProcrastinatingReader (talk) 08:25, 27 December 2022 (UTC)
- Neutral - As stated here on ARCA, I'd rather have a general sanction for all of Turkey. EvergreenFir (talk) 22:26, 16 December 2022 (UTC)
- Comment for Kurds - I would have been supportive of the proposal if it was done back in 2019-2021 when the disruption was constant at WP:Kurds. However, there hasn't been much disruption in recent months from my observation, only isolated incidents. Semsûrî (talk) 13:02, 18 December 2022 (UTC)
- Support Armenia/Azerbaijan for a limited time and Kurds for a more extended period of time. I agree with the reasons presented by other editors and support a time-limited ECP period. My preferred ECP range is a bit broader than Nosebagbear's idea: Sanction the conflict related pages and try to stay away from more cultural or non-conflict related stuff, but also ECP the main country articles since we're probably gonna get some trolls who edit something along the lines of "Armenia is a d*ck country" or fulfilling Godwin's law when it comes to Erdogan and the Kurds after being autoconfirmed. The stats below show that for me, we have too many Non EC but AC editors vandalizing...ideally we should see around 17-ish% for all categories for only semi. Since the Kurds are likely to be a much more prolonged issue given the additional involvement that particular conflict has within the Syrian Civil War, I support longer sanctions for that field, but given that Armenia and Azerbaijan (as of writing) are not as active in their fighting or anger at least right now, I'm more inclined to cut that ECP short a bit earlier. InvadingInvader (userpage, talk) 05:32, 27 December 2022 (UTC)
- Support but the Greece and Cyprus topic areas should be
monitoredincluded too. There was a recent disruption in these topic areas, where Turkish agenda accounts editwarred at Aegean dispute and Cyprus–Turkey maritime zones dispute, resulting to their indefinite blocks. This happens at a time when there are a growing number of international media [267][268][269][270][271] reporting that the ruling nationalist government of Turkey is actively adopting an extremely hostile rhetoric against these neighboring countries.
- Considering that the common people in Turkey are lacking an unhindered access to third-party independent media and more calm voices (all the media in the country are either under intense pressure or the control of the government [272]), it is inevitable for Wikipedia to see a surge in WP:MEATPUPPETRY incidents in topic areas related to Turkey, not only about its Eastern and South Eastern fronts (Armenians and Kurds respectively) but also its South Western and Western fronts (Cuprus and Greece), since it is a well-established fact that politics can drive people into WP:RIGHTINGGREATWRONGS and WP:PROMO when they deem that the Project's neutral viewpoint differs noticeably from the nationalist narrative promoted by their government. Edit: the admin EvergreenFir's proposal for a general sanction for all of Turkey should be considered as more effective than my own idea about monitoring. --- ❖ SilentResident ❖ (talk ✉ | contribs ✎) 01:48, 2 January 2023 (UTC)
At ARCA
editMight as well do myself, or it probably just won't happen. I requested ArbCom to amend WP:AA2 and WP:KURDS by motion per the #Proposal. See: WP:ARCA#Long title. El_C 22:49, 23 November 2022 (UTC)
- I've listed this at WP:CENT in case that helps move things forward. Levivich (talk) 21:48, 28 November 2022 (UTC)
- I've requested a closure of this thread to the community discussion in my capacity as an individual editor. –MJL ‐Talk‐☖ 20:17, 26 December 2022 (UTC)
Statistics
editIP editors were reverted:
- 65% of the time on articles related to Armenia and Azerbaijan
- 44% of the time on articles related to Armenia or Azerbaijan
- 57% of the time on articles related to Kurds
- 40% of the time on articles related to American politics
- 28% of the time on all articles
Non-AC editors were reverted
- 64% of the time on articles related to Armenia and Azerbaijan
- 49% of the time on articles related to Armenia or Azerbaijan
- 63% of the time on articles related to Kurds
- 53% of the time on articles related to American politics
- 37% of the time on all articles
Non-EC editors were reverted
- 47% of the time on articles related to Armenia and Azerbaijan
- 33% of the time on articles related to Armenia or Azerbaijan
- 42% of the time on articles related to Kurds
- 27% of the time on articles related to American politics
- 17% of the time on all articles
Non-EC but AC editors were reverted
- 44% of the time on articles related to Armenia and Azerbaijan
- 30% of the time on articles related to Armenia or Azerbaijan
- 38% of the time on articles related to Kurds
- 23% of the time on articles related to American politics
- 13% of the time on all articles
All editors were reverted
- 23% of the time on articles related to Armenia and Azerbaijan
- 15% of the time on articles related to Armenia or Azerbaijan
- 26% of the time on articles related to Kurds
- 14% of the time on articles related to American politics
- 10% of the time on all articles
Articles were determined by looking at articles within the scope of the relevant wikiprojects; WP:WikiProject Armenia, WP:WikiProject Azerbaijan, and WP:WikiProject Kurdistan. BilledMammal (talk) 14:24, 29 November 2022 (UTC)
- This is useful. Can you clarify if "non-EC" editors includes IP/non-confirmed editors? If so, can you give statistics for non-EC editors who are autoconfirmed?
- For comparion, could we get the revert rate in non-ECR hot-bed topics like American Politics?
- Did you do this programmatically or did you select a sample of articles? (Enterprisey out of interest, could your revert script from WP:RESPONDER-RFC be used for this kind of analysis?) ProcSock (talk) 01:51, 30 November 2022 (UTC)
- "non-EC" editors include non-confirmed editors, but not IP editors. I've added the requested statistics, as well as few others. I've also attempted to include the revert rate in AP2, but I'm not certain I have properly identified the area; I used Category:American_politics_task_force_articles and it includes articles on American politics not covered by AP2 (the AP2 template is only used on a ~200 articles, so isn't useful here).
- I did this with Quarry; see Edit count Armenia or Azerbaijan articles, Edit count American politics articles, Edit count Kurdistan articles, Edit count Armenia and Azerbaijan articles, and Reversions by editor. Reversion by editor only looks at November 2022; the rest look at all of 2022. They also don't account for the increase in edit count since making the relevant edits; if an editor has EC now, it assumes they had it when they made the edit. BilledMammal (talk) 02:22, 30 November 2022 (UTC)
Disruption extending to Greece / Cyprus topic areas?
editToday we have been witnessing some Turkish POV disruption by pro-Turkish IPs and WP:SPA in a number of articles of the Greece / Cyprus topic area, particularly: Aegean dispute, Cyprus–Turkey maritime zones dispute and this AN discussion here was brought to my attention now, and I felt it might be helpful to inform you, albeit I am not 100% certain if the disruption in the Greece/Cyprus topic areas relates (or if it relates at all) to the disruption you have been witnessing in Armenia/Azerbaijan/Kurds topic areas by pro-Turkish IPs/SPA accounts. Well, due to today's disruption, one of the two articles had to be locked today by admins, [273] while the other article's disruption ended up at the ANI: [274]. If you believe they are related, then I would welcome any feedback. Good day. --- ❖ SilentResident ❖ (talk ✉ | contribs ✎) 21:29, 31 December 2022 (UTC)
- Update: Turns out that the account I pointed to, above, is simply another WP:SOCK account and today it got blocked infinitely by the admins [275]. This comes shortly after another Turkish POV-pushing sock account causing the same kind of disruption at Aegean dispute too being blocked [276] for disruption across the Kurds topic area (they edited the Aegean dispute around the same time as the present discussion here at the AN was going on). I'm leaving this as a note here since it definitely relates to the large number of Turkish POV-pushing accounts affecting the stability of Wikipedia, across multiple topic areas. Good day. --- ❖ SilentResident ❖ (talk ✉ | contribs ✎) 12:24, 1 January 2023 (UTC)
- Meh. I’ve got a good part of the Cyprus-related controversial articles on my watchlist (as I’m essentially the only Cypriot extended-confirmed regular I guess?) and I’m yet to see a general trend for POV pushing out of the ordinary. Turkish invasion of Cyprus, for example, is an old favourite of the POV-pushers but is yet to see any unusual activity. Believe me when I say that if the Turkish trolls decide to come for Wikipedia’s Cyprus articles in an organised fashion, we’ll know by that article. An examination of the history of Cyprus–Turkey maritime zones dispute shows some disruption by a sock in the past few days but likewise pro-Greek POV-pushing earlier in the year. I’d say that the general trend is that the level of disruption in the Cyprus topic area is improving, definitely it’s nowhere as bad as I remember it a decade ago. If there are issues, they are with specific articles, and topic area-wide restrictions would clearly be disproportionate and counterproductive. I would vehemently oppose ECR restrictions, and in particular a 500/30 restriction. I suspect this applies to the overall Greek/Turkish topic area. —GGT (talk) 01:03, 3 January 2023 (UTC)
Proposed motion for amendment to Arbitration procedures: Closing Clarification and Amendment Requests
editThe Arbitration Committee is considering a motion to add an additional route for closing clarification and amendment requests in certain circumstances. Comments are welcomed in the relevant section. For the Committee, firefly ( t · c ) 22:09, 3 January 2023 (UTC)
Name of suspect in discussion
editAt this discussion, the name of the suspect should be permanently deleted. --Jax 0677 (talk) 00:01, 4 January 2023 (UTC)
- Here as well. --Jax 0677 (talk) 08:55, 4 January 2023 (UTC)
- Why? WP:BLPTALK is intentionally very narrow (
Contentious material about living persons that is unsourced or poorly sourced and not related to making content choices should be removed, deleted, or oversighted, as appropriate
if you want chapter and verse); since talk pages aren't indexed, we recognize there are legitimate grounds for discussing material even when it's material that we conclude shouldn't be included in articles. If you want something oversighted, you need to convince an oversighter to do so following the appropriate process, not by Striesanding it at a high-traffic noticeboard. ‑ Iridescent 15:50, 4 January 2023 (UTC)- Ooo-ooo-ooo-ooo-ooo-ooo-ooo-ooo-ooo-ooo-ooo[Humour]For the record, this situation was already well on its way to being known by everyone. It's even on The Unmentionable Site. casualdejekyll 20:22, 4 January 2023 (UTC)
- Why? WP:BLPTALK is intentionally very narrow (
- This is already on two message boards, it doesn't need to be on a third. Let consensus form in one place, especially the first link where some well reasoned points are being exchanged. Star Mississippi 17:15, 4 January 2023 (UTC)
Examples of serious Google Knowledge Graph mistakes?
editCan anyone supply me with examples where Google Knowledge Graphs have made any extremely serious errors based on taking wrong data or images from Wikipedia articles? I vaguely remember a case a few years ago where a briefly-vandalised article was used by Google to assemble seriously flawed information about a person, and there being an urgent need to report and fix it - but I cannot recollect any details.
I do remember thinking that on such extremely rare cases it could have been helpful to have a more direct route for administrators to communicate quickly with Google (or indeed other companies who are incorrectly using our data which could seriously embarass or defame people), rather than simply relying on the 'Feedback' link below each Knowledge graph. .
This request follows a recent conversation I had with a staff member at Google on this subject, who asked for some examples - and I couldn't think of any details offhand. I'd welcome replies either here (or by email if it helps avoid the Streisand effect.) Thanks, Nick Moyes (talk) 17:25, 3 January 2023 (UTC)
- The most well-known case of this is WP:CALIPH, where Google searches for "current caliph of islam" misinterpret Ahmadiyya Caliphate to display Mirza Masroor Ahmad as the caliph. – dudhhr talk contribs (he/they) 17:50, 3 January 2023 (UTC)
- The Google Knowledge graph is dynamically generated in complex ways that depend on the subject, the time, the location of the reader, etc. etc. When it makes errors, those errors aren't ephemeral and aren't preserved in a specific document unless a third party documents it directly. It's basically an AI algorithm that scrapes the web and attempts to create a summary of the subject in real time. That's not going to lend itself to a permanent record of any errors, much less a canonical list of errors one could comb through. Like many things at Google, how it is generated is a "trade secret" and quite opaque. --Jayron32 18:56, 3 January 2023 (UTC)
- One that comes up a lot is when Google confuses two people with the same name, and uses data from person A's social media or personal website to illustrate text ripped off from the Wikipedia page on person B with the same name (or vice versa). Here's a quick example but it comes up fairly regularly. ‑ Iridescent 18:58, 3 January 2023 (UTC)
- I've personally dealt with several instances of Google confusing people with criminals, through them mismatching the image and the description. They can usually be found reported at the Help Desk. I'm not going to look them up, but searching for knowledge graph at BLPN or HD or Teahouse should bring up numerous examples. To be fair, IME Google often appears to have been quite prompt in responding to the feedback button, but that may be circumstantial. -- zzuuzz (talk) 05:24, 5 January 2023 (UTC)
- I seem to remember this being in the news once: Google blames Wikipedia for linking California GOP to Nazism. It was just some vandalism that stayed in Knowledge Graph for a while. Somehow made it all the way to Kevin McCarthy's ire. Endwise (talk) 11:19, 5 January 2023 (UTC)
The rapid reversions by USER:John Yunshire
editUSER:John Yunshire has already been warned about their rapid fire reverting, they deleted these warnings off their talkpage. But I think this user needs to have the rules explained to them again. They seem to be on a wholesale reversion crusade edits.146.199.128.158 (talk) 14:08, 5 January 2023 (UTC)
- You have failed to notify the user, which is required, and you have not provided any diffs of the user's alleged misconduct.--Bbb23 (talk) 14:23, 5 January 2023 (UTC)
- I also do not see evidence John Yunshire has been warned by anyone recently. @John Yunshire - for the record, although there is no rule explicitly against deleting warnings off your talk page that I personally know of (I could be wrong), it is generally considered good form to let them be archived like other messages. casualdejekyll 14:47, 5 January 2023 (UTC)
- Deletion of warnings is acknowledgement that you read. I see no good form or otherwise of removing them vs archiving.
- Also this should be closed. I looked at 2 edits both were vandal reversion and proper so stopped looking. Slywriter (talk) 15:06, 5 January 2023 (UTC)
- Archiving makes it much easier to take past warnings into account when looking at conduct of an editor is needed. casualdejekyll 15:20, 5 January 2023 (UTC)
Hi, Not many sources, and subject to paid editing by Lupsei27, who was advised on Commons to disclore his COI. Yann (talk) 16:57, 5 January 2023 (UTC)
- Warned to declare status here, will wait to see if they need pblock from page. Star Mississippi 21:47, 5 January 2023 (UTC)
Administrators' newsletter – January 2023
editNews and updates for administrators from the past month (December 2022).
- Speedy deletion criterion A5 (transwikied articles) has been repealed following an unopposed proposal.
- Following the 2022 Arbitration Committee elections, the following editors have been appointed to the Arbitration Committee: Barkeep49, CaptainEek, GeneralNotability, Guerillero, L235, Moneytrees, Primefac, SilkTork.
- The 2021-22 Discretionary Sanctions Review has concluded with many changes to the discretionary sanctions procedure including a change of the name to "contentious topics". The changes are being implemented over the coming month.
- The arbitration case Stephen has been closed.
- Voting for the Sound Logo has closed and the winner is expected to be announced February to April 2023.
- Tech tip: You can view information about IP addresses in a centralised location using bullseye which won the Newcomer award in the recent Coolest Tool Awards.
Circumcision related close
editCould I get a sanity-check on this recent close by TryKid at Circumcision and HIV? (Full disclosure: I disagree with it). In adducing a slight numerical advantage, and an incidental point about WP:FRINGE, can consensus really be declared? Bon courage (talk) 16:30, 1 January 2023 (UTC)
- Seems like a misunderstanding of WP:NOTAVOTE. I would probably have closed as no consensus since no arguments appear to have been particularly persuasive and it mostly consisted of roughly equal proportions of users talking past each other and many many of the "full version" comments were essentially "what they said". — Shibbolethink (♔ ♕) 00:25, 2 January 2023 (UTC)
- As a bot-summoned respondent to that discussion, I'm gonna have to agree: a 5:6 !vote ratio and these particular facts cannot possibly justify the finding of consensus the closer arrived at in this case: the respondents were clearly highly divided, on an issue that was nuanced and in a contentious topic area. Even requesting a close in those circumstances was a questionable call, since the only possible reasonable outcome would have been "no consensus"; rather, the RfC should have been relisted with the hope that a second wave of input from FRS respondents might lead to an actual consensus of at least some significant weight, and that's probably what ought to be happen now.
- And, meaning no offense, but the closer really needs to re-read the applicable policies on closing, and better familiarize themselves with the burden of weight that the community expects of WP:CONSENSUS determinations before they act further in the capacity of a closer, especially in divisive topic areas: I trust this was an error made from a good faith misunderstanding of what a proper threshhold of consensus looks like, but at the same time, this wasn't even close to being justified. SnowRise let's rap 02:07, 2 January 2023 (UTC)
- I'd have closed as NC. I can't tell what the status quo is, but there's clearly consensus for some form of inclusion, so if the status quo is no mention then I'd say the RfC permits the shorter summary at least. ProcrastinatingReader (talk) 10:30, 2 January 2023 (UTC)
- It seems some editors in an earlier section did object to the inclusion of the paragraph at all; but not in the RfC. The shorter version was the status quo at the time I closed the discussion, and also at least when it was started. I considered closing as either "full version" or no consensus, but ultimately it seemed to me that the main arguments against the full version—WP:UNDUE, WP:WEIGHT, WP:FRINGE were not convincing enough for a few other commenters or for me to close as no consensus. regards, TryKid [dubious – discuss] 12:58, 2 January 2023 (UTC)
- I think it's sound to consider the discussion by-argument, but I'm not sure how you reached the conclusion that these arguments (WP:UNDUE, WP:WEIGHT, WP:FRINGE) were not convincing enough. After they were first made by SnowRise, 3 editors were convinced by them, and 3 editors were not, so a cursory glance would suggest to me that there was no consensus on the relevance/strength of these points? ProcrastinatingReader (talk) 13:29, 2 January 2023 (UTC)
- Well, aside from the six new commenters, there was also a disagreeing reply from the person who started the RfC and wrote the first !vote. I can see how it could be contentious, but it still left me leaning towards a close in favour of the full version. TryKid [dubious – discuss] 14:30, 2 January 2023 (UTC)
- @TryKid: how are you evaluating this discussion here at WP:AN? Are you detecting that your fellow editors think your close a good one? Bon courage (talk) 14:36, 2 January 2023 (UTC)
- No, I don't. Some amount of disagreement is natural and expected; what the close should be is not always very clear and these decisions can be subjective to a large degree. While I see others disagree with the close, I don't think I see anyone considering it specially bad; but if an administrator or editor considers it egregious enough to overturn it expressly, I wouldn't object to it. TryKid [dubious – discuss] 21:39, 2 January 2023 (UTC)
- Cool, I have accordingly undone the close. In general in situations where it is "not very clear", closes should be left to admins, per WP:BADNAC. Bon courage (talk) 04:21, 4 January 2023 (UTC)
- TryKid, I wrote my original comments above in a hurry, and I realize now that I failed to note that even if the close was in error it was clearly a goodfaith error, so I'd like to make sure to stipulate that now. That said, I'd like to respond, purely for the purpose of clarity to why I think your reasoning (as you've outlined above) deviates from community consensus and best practice on closes.
- No, I don't. Some amount of disagreement is natural and expected; what the close should be is not always very clear and these decisions can be subjective to a large degree. While I see others disagree with the close, I don't think I see anyone considering it specially bad; but if an administrator or editor considers it egregious enough to overturn it expressly, I wouldn't object to it. TryKid [dubious – discuss] 21:39, 2 January 2023 (UTC)
- @TryKid: how are you evaluating this discussion here at WP:AN? Are you detecting that your fellow editors think your close a good one? Bon courage (talk) 14:36, 2 January 2023 (UTC)
- Well, aside from the six new commenters, there was also a disagreeing reply from the person who started the RfC and wrote the first !vote. I can see how it could be contentious, but it still left me leaning towards a close in favour of the full version. TryKid [dubious – discuss] 14:30, 2 January 2023 (UTC)
- I think it's sound to consider the discussion by-argument, but I'm not sure how you reached the conclusion that these arguments (WP:UNDUE, WP:WEIGHT, WP:FRINGE) were not convincing enough. After they were first made by SnowRise, 3 editors were convinced by them, and 3 editors were not, so a cursory glance would suggest to me that there was no consensus on the relevance/strength of these points? ProcrastinatingReader (talk) 13:29, 2 January 2023 (UTC)
- It seems some editors in an earlier section did object to the inclusion of the paragraph at all; but not in the RfC. The shorter version was the status quo at the time I closed the discussion, and also at least when it was started. I considered closing as either "full version" or no consensus, but ultimately it seemed to me that the main arguments against the full version—WP:UNDUE, WP:WEIGHT, WP:FRINGE were not convincing enough for a few other commenters or for me to close as no consensus. regards, TryKid [dubious – discuss] 12:58, 2 January 2023 (UTC)
- First, when you state that you dismissed the value of certain !votes because you did not find them compelling, you are, in my opinion, failing to understand the distinction between what is expected when you lodge your own opinion and what you are meant to be doing as the closer--that is, summarizing the existing positions and their rough levels of support among the participants of the consensus discussion. While it is true that our policies on closures do present a narrow kind of permissiveness to the closer in discarding perspectives that are not well-rooted in policy and broad community consensus, in practice 1) that kind of discretion is almost never invoked to find a consensus when positions among participants are so close to evenly split, 2) when it is invoked, it would be case of perspectives that are just wildly out of alignment with policy, not these kinds of reasonable differences of editorial perspective, and 3) as others here have noted, such a nuanced and out-on-a-limb close that essentially nullifies the participation of experienced community members expressing views that are plainly an egregiously contrary to policy should be reserved to an admin, if anyone. In other words, the NOTAVOTE principle is a pragmatic carve out that the community has chosen to preserve for rare cases of large numbers of inexperienced editors !voting blatantly against policy, but in practice it is just no applied to cases of close calls on a nuanced and reasonably-disagreed-upon topics being discussed by your average collection of editors/community members, and doing so will usually be perceived as a WP:SUPERVOTE, rather than a fair close.
- Similarly, when you suggest the close might as well be for the interpretation that you endorsed, because the default to the status quo in the case of a "no consensus" result would be the same. But this also conflates important procedural considerations. I tend to agree with you that the status quo version here is almost certainly the longer version, and that for the present time, the content is going to stay the same regardless of whether the result was "include (the longer version)" or "no consensus". And honestly, I have no objection to the outcome in that respect: that's just how we approach deadlocks on this project, and it's a reasonable, pragmatic way of dealing with presently unresolved content determinations. However, how a contested discussion is closed has a lot of knock-on effects under our policies and best practices for resolving disputes.
- To identify just one important factor, whether a discussion is closed as "no consensus" or with endorsement for one of the argued-for perspectives determines how quickly the regular editors on a given article (and the community in general) are likely to entertain the next effort to discuss and gain consensus on that topic. If there is an identified consensus result, most editors will want discussion to stay dormant for a while, even most experienced editors who supported another perspective, and trying to re-litigate the issue immediately can be considered WP:DISRUPTIVE. If, on the other hand, the result is "no consensus", continuing discussion can usually resume after a relatively brief break. Even then, I don't advise the next wave of debate begin again immediately in most circumstances, but at least if the issue remains undetermined by a genuine consensus, parties don't have to be worried about being described as being tendentious if they chose to bring the issue to the fore again sooner rather than later.
- Now these aren't the only reasons to use an abundance of caution with endorsing one position over another in a close call in a close, but they are the more salient points. I hope the observations come across as more informative than patronizing, but regardless, I think they are essential nuances that have to be considered when doing a close on closely-disputed issue in a contentious area. Indeed, my best advice is just to leave such calls to a mop, but of course I understand that most experienced editors will dip their toes into making a few such close calls in some community capacity at some juncture. SnowRise let's rap 03:22, 6 January 2023 (UTC)
@Snow Rise:“Even requesting a close in those circumstances was a questionable call.” I would like to point out, that the !vote margin narrowed *after* I requested a close. “No consensus” was not as clear when I made my initial request for closure. Prcc27 (talk) 05:20, 4 January 2023 (UTC)
@ProcrastinatingReader: Determining which version is the “status quo” may be difficult. The longer version had been on the Wikipedia article for several years, but the shorter version was recently added, and was on the article prior to the rfc, after a couple users expressed opposition to the long version. Prcc27 (talk) 06:31, 4 January 2023 (UTC)