Wikipedia:Administrators' noticeboard

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by TonyBallioni (talk | contribs) at 03:51, 3 January 2023 (→‎Massive off-wiki campaign aimed at disrupting Wikipedia: close). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Welcome to the administrators' noticeboard

This page is for posting information and issues of interest to administrators.

  • It is rarely appropriate for inexperienced users to open new threads here – for the "Incidents" noticeboard, click here.
  • Do not report breaches of privacy, inappropriate posting of personal information, outing, etc. on this highly visible page – instead click here.
  • For administrative backlogs add {{Admin backlog}} to the backlogged page; post here only if urgent.
  • Do not post requests for page protection, deletion requests, or block requests here.

When you start a discussion about an editor, you must leave a notice on the editor's talk page.

The use of ping or the notification system is not sufficient for this purpose.

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

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

Open tasks

XFD backlog
V Dec Jan Feb Mar Total
CfD 0 0 3 74 77
TfD 0 0 0 1 1
MfD 0 0 0 0 0
FfD 0 0 0 0 0
RfD 0 0 0 27 27
AfD 0 0 0 0 0

Pages recently put under extended-confirmed protection

Pages recently put under extended confirmed protection (24 out of 4274 total) (Purge)
Page Protected Expiry Type Summary Admin
Israel 2023-03-30 14:46 indefinite edit Restore indef ECP DatGuy
Draft:Sir Studios 2023-03-30 11:02 2023-04-06 11:02 create Repeatedly recreated The JPS
Lionel Messi 2023-03-29 23:04 indefinite edit Back to ECP (which it was previously); too much disruption Black Kite
User talk:KnowIG 2023-03-29 20:49 indefinite edit,move Per request Courcelles
Draft:Anjum Lucknowi 2023-03-29 20:09 indefinite create Repeatedly recreated Dreamy Jazz
Mohamed Al-Agha 2023-03-29 18:53 indefinite create Recently deleted BLP Salvio giuliano
Frank E. Weiss 2023-03-29 18:43 indefinite create Recently deleted BLP Salvio giuliano
Draft talk:Me 2023-03-29 05:13 indefinite create Repeatedly recreated Liz
Abdul rahman muhammad hamdan 2023-03-29 03:06 2023-04-01 03:06 create Repeatedly recreated Liz
Abdul rahman muhammad hamadan 2023-03-29 03:03 2023-04-01 03:03 create Repeatedly recreated Liz
Abdul Rahman Muhammadn Hamdan 2023-03-29 03:03 2023-04-01 03:03 create Repeatedly recreated Liz
Amritpal Singh 2023-03-28 00:36 2023-04-28 00:36 edit disruptive editing resumed soon after prior ECP expired WP:CT/IPA Abecedare
2023 Covenant School shooting 2023-03-27 20:42 2023-04-03 19:51 edit adding a time limit to the move protection can't hurt ToBeFree
Covenant School shooting 2023-03-27 20:30 2023-04-03 19:51 edit Violations of the biographies of living persons policy Muboshgu
Template:Efn-lr 2023-03-27 17:59 indefinite edit,move High-risk template or module: 2501 transclusions (more info) MusikBot II
📚 2023-03-27 17:47 indefinite edit,move Persistent vandalism HJ Mitchell
🪅 2023-03-27 17:41 indefinite edit,move Persistent vandalism Courcelles
📿 2023-03-27 17:40 indefinite edit Persistent vandalism: no regular need for this to be edited HJ Mitchell
Team Umizoomi 2023-03-27 17:18 2023-04-03 17:18 edit Persistent sock puppetry with access level gaming rendering autoconfirmed protection fruitless DatGuy
H:ECON 2023-03-27 15:34 indefinite edit someone managed to spam this shortcut! No need for it to be edited on a regular basis. HJ Mitchell
Kyrgyz Khanate 2023-03-27 03:19 indefinite create Sockpuppet magnet, dozens of sockpuppets have edited this article Liz
Rohan Gunaratna 2023-03-27 03:19 indefinite edit,move Violations of the biographies of living persons policy: per RFPP Daniel Case
Turkish alphabet 2023-03-27 03:04 2023-04-17 03:02 edit,move Persistent disruptive editing: going to ECP per request Daniel Case
Talk:Team Umizoomi 2023-03-26 21:51 2023-04-05 21:50 edit,move Materialscientist

Massive off-wiki campaign aimed at disrupting Wikipedia

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

I noticed this Turkish-language Reddit link.[1]. 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."[2]
  • "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."[3]
  • "we need a larger audience, salaried employees of wikipedia, and I don't know how effective we can be against the current Turkish hatred"[4]
  • "Turkish Wikipedia Community Discord server. Friends, I left the link below if you would like to join the works that started before us."[5]
  • "Friends, let's start with the liberation war first and let there be a spark of salvation for us from the lies in Wikipedia."[6]
  • "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."[7]
  • "Ottoman archives of the period are available on this site: (<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."[8]
  • "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."[9]
  • "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"[10]

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)Reply[reply]

Noting this is still ongoing, see Vahakn Dadrian and its abuse log. DatGuyTalkContribs 15:36, 11 November 2022 (UTC)Reply[reply]
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)Reply[reply]

The discord server

When 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 [11]. 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. [12]-[13]- LouisAragon (talk) 12:03, 15 October 2022 (UTC)Reply[reply]

Note the date 27-06-2022 at Discord:[14] 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)Reply[reply]
@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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
The discord link here just got deleted [15] (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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
@HistoryofIran Per Wikipedia:Village pump (policy)/Archive 169#Discord logs Posting discord logs on wiki is oversightable. Email them to arbcom. (talk) 13:46, 15 October 2022 (UTC)Reply[reply]
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)Reply[reply]
@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)Reply[reply]
  • 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, I don't buy the claim that this is unrelated to 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; there may be a case for starting a discussion on Metawiki. signed, Rosguill talk 16:39, 15 October 2022 (UTC)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    ofcourse, the user that I have warned about this situation is Kutlug Şad as I explained above. BerkBerk68 16:23, 22 October 2022 (UTC)Reply[reply]

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)Reply[reply]

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)Reply[reply]
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)Reply[reply]
  • Aaand r/Turkviki has been made private by its moderators. ~StyyxTalk? 17:07, 18 October 2022 (UTC)Reply[reply]
  • 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" [16] and has tried to defend [17]. 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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    @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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
While I see your concern, I'm not sure it's a major issue. Let's say that someone emails ArbCom an UpWork profile and says "so and so is a paid editor." Technically it's private evidence. But it would not be worth the time of the committee for all 15 members to deliberate and vote on blocking an obvious paid editor. So an individual Arb can just block said obvious paid editor without needing to make it an ArbCom block. It would be no different if say someone had emailed just me, and not ArbCom. In either case, the block I make is as an individual CU. The appeal is not difficult: the CU looking into unblocking just emails the blocking CU (pretty standard procedure) and asks what the basis for the block was. The blocking CU sends over the UpWork profile, and all is well. This case here is but a variation on that theme. CaptainEek Edits Ho Cap'n! 08:49, 28 October 2022 (UTC)Reply[reply]
I disagree, so have opened a dedicated thread below. Thanks. — TheresNoTime (talk • they/them) 08:52, 28 October 2022 (UTC)Reply[reply]
  • 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)Reply[reply]
  • :"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". (talk) 14:19, 10 November 2022 (UTC) Reply[reply]
    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.
    @CaptainEek: and other users who involved. (talk) 14:35, 10 November 2022 (UTC) <--- blocked sock of User:BeyoglouReply[reply]
(Writing so thread doesn't get archived tomorrow). --HistoryofIran (talk) 19:35, 5 December 2022 (UTC)Reply[reply]
Ditto. --HistoryofIran (talk) 02:04, 24 December 2022 (UTC)Reply[reply]


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 [18] of the notorious sock Aydın memmedov2000, which doesn't even show all of their socks, there are even more of this person here [19]. 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)Reply[reply]

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)Reply[reply]
  • 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)Reply[reply]
    Take a look at this edit I reverted just now. They're even disrupting article not related to WP:KURDS. Let's at least ECP articles directly related to that topic area. — Nythar (💬-🎃) 22:53, 1 November 2022 (UTC)Reply[reply]
  • Support applying WP:ARBECR to AA2 and KURDS. Levivich (talk) 16:27, 3 November 2022 (UTC)Reply[reply]
  • 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)Reply[reply]
    If anyone needs further evidence, check out the 8 9 10 reverts by an IP at the Orontid dynasty. --Kansas Bear (talk) 03:31, 13 November 2022 (UTC)Reply[reply]
  • Support Clearly something needs to be done here. Hemiauchenia (talk) 17:53, 7 November 2022 (UTC)Reply[reply]
  • Support Surely something must need to be done about this disruption. --Magnatyrannus (talk | contribs) 22:22, 7 November 2022 (UTC)Reply[reply]
  • Support Very sensible proposal to reduce the disruption. Khirurg (talk) 23:59, 7 November 2022 (UTC)Reply[reply]
  • Support Long, long overdue. - LouisAragon (talk) 15:30, 10 November 2022 (UTC)Reply[reply]
  • Support the disruption is only ever going to grow, and it's already at unsustainable levels. ~~ AirshipJungleman29 (talk) 19:44, 10 November 2022 (UTC)Reply[reply]
  • Support Even though this won't stop them, it will certainly hinder their disruptive activity. Demetrios1993 (talk) 21:08, 10 November 2022 (UTC)Reply[reply]
  • 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)Reply[reply]
  • @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)Reply[reply]
    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)Reply[reply]
  • Support, this is a good idea considering what I've seen when patrolling vandalism. LilianaUwU (talk / contribs) 23:35, 11 November 2022 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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 (d) 10:53, 13 November 2022 (UTC)Reply[reply]
  • Support per constant disruption/vandalism by IPs on AA2 topic area. – Olympian loquere 06:23, 15 November 2022 (UTC)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
  • This overwhelming support surely is more than enough for the WP:ARBECR to be implemented? --HistoryofIran (talk) 21:10, 19 November 2022 (UTC)Reply[reply]
    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:ARBEEWP:GS/RUSUKR. HTH. El_C 23:03, 19 November 2022 (UTC)Reply[reply]
    @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)Reply[reply]
    @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)Reply[reply]
    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/COVID19WP:ARBCOVID; WP:GS/IPAKWP:ARBPAK; WP:GS/IRANPOLWP: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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    I'm not preventing you from doing anything, least of all read what I had written. El_C 13:36, 22 November 2022 (UTC)Reply[reply]
  • Support because of constant sockpuppeting. ZaniGiovanni (talk) 11:32, 21 November 2022 (UTC)Reply[reply]
  • 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)Reply[reply]
  • Oppose per Guerillero and my comments at WP:ARCA. ProcrastinatingReader (talk) 22:27, 26 November 2022 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
  • Support – I trust the rationale and evidence provided by numerous experienced editors in these topic areas. Aza24 (talk) 09:44, 12 December 2022 (UTC)Reply[reply]
  • 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)Reply[reply]
    subjected to disruption by IPs and new users then so would semi-protection? ProcrastinatingReader (talk) 08:25, 27 December 2022 (UTC)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Support but the Greece and Cyprus topic areas should be monitored included 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 [20][21][22][23][24] 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 [25]), 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)Reply[reply]


Might 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)Reply[reply]

I've listed this at WP:CENT in case that helps move things forward. Levivich (talk) 21:48, 28 November 2022 (UTC)Reply[reply]
I've requested a closure of this thread to the community discussion in my capacity as an individual editor. –MJLTalk 20:17, 26 December 2022 (UTC)Reply[reply]


IP 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)Reply[reply]

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)Reply[reply]
"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)Reply[reply]

Disruption extending to Greece / Cyprus topic areas?

Today 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, [26] while the other article's disruption ended up at the ANI: [27]. If you believe they are related, then I would welcome any feedback. Good day. --- SilentResident (talk ✉ | contribs ✎) 21:29, 31 December 2022 (UTC)Reply[reply]

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 [28]. This comes shortly after another Turkish POV-pushing sock account causing the same kind of disruption at Aegean dispute too being blocked [29] 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)Reply[reply]
  • 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)Reply[reply]
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Name of suspect added to "2022 pregnancy of a 10-year-old in Ohio"

Can 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)Reply[reply]

I'm looking for it, can you give me a diff? Valereee (talk) 02:05, 24 December 2022 (UTC)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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[reply]
  • 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)Reply[reply]
    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[reply]

SashiRolls requests a !ban

To whom it may concern:

Hello. I was banned from en.wp back in the summer of 2020 ( § ) after an ill-conceived tussle with El C about a temporary block from the Edward Colston page. At the time, it was suggested I come back in six months. When I did, I didn't stick out my appeal until the end. Since then, I've waited about two years to ask again, to be sure that any trace of annoyance had disappeared, at least on my end.

In the time I've been away, I've made roughly 5000 contributions to non-en.wp wmf projects:

I've also made minor edits to other projects ranging from haitian to latin.

The disruption to my en.wp contributions also gave me the chance to do some work on my own mediawiki for which I sincerely thank all those involved. I've also worked a bit on the French version of one of the last en.wp articles I created before I left. It's about the Gère river. (fr | en)

It will probably come up that I frequent WPO. Since joining over there in Dec. 2016, I've never to my knowledge caused any serious problems, nor have I ever been thrown out, which suggests I may not be such a bad egg as all that. Here and there things I've said there or that have happened to me have led to changes at en.wp (in articles, policy) or have caused an occasional ripple.

I would say that what I've learned is that things on wiki go fast. Too fast. What starts out at as a minor thing can quickly be escalated into something that wastes a lot of time and leads to disrupted work. Sometimes, as I mentioned above, disruption can be productive, but most of the time it isn't, and it's better to always strive to deescalate. I'm not here to test boundaries. I know I can't edit GMOs, Am-Pol or WP:AE. Best practice will be to keep away from those who might tend to rile me up. I do think that the past two years of on-wiki production at data, commons, fr.wp show that I'm able to colloborate, as well as contribute.

The immediate impetus to this request was a request for file-mover tools at Commons, during which my en.wp ban was brought up as a reason to be circumspect. So, it seemed to me like perhaps the time has come to resolve this.

How about we get out the calumet and agree to peacefully co-exist? :)

SashiRolls (talk) 14:12, 24 December 2022 (UTC)Reply[reply]

Copied from c:Special:PermaLink/719472438 per utrs:67199 — JJMC89(T·C) 01:07, 25 December 2022 (UTC)Reply[reply]

  • First! 👍 P.S. I think I was first in the last appeal, too. But I can't immediately find it. Whatever I said then, though, still. El_C 01:48, 25 December 2022 (UTC)Reply[reply]
    Special:PermaLink/1000836596#Ban_removal_request_of_SashiRolls. (talk) 08:29, 25 December 2022 (UTC) Fixed link, pretty sure this is where it should be pointing. Primefac (talk) 13:56, 25 December 2022 (UTC)Reply[reply]
    Is everyone else seeing that red gg+ button in the mobile thingy? It takes you to your notifications for some reason! El_C 21:58, 25 December 2022 (UTC)Reply[reply]
    You seem to be referring to the notifications icon. Everyone logged in on mobile should see it and should go to their notifications when they click on it, as has been the case for ?~8 years. However not everyone will have 99+ "unread" notifications so their number will vary. The colour will also vary depending on whether the mobile site considers there are new notifications, somewhat akin to the desktop site but their newness is handled different. Nil Einne (talk) 23:23, 26 December 2022 (UTC)Reply[reply]
  • Hm. I find myself looking at [30] in an inability to personally desire the described person's return to a community I'm a part of. A request for an "agree[ment] to peacefully co-exist" sounds as if the community had denied this opportunity to you. That's probably not correct. They threw you out because you weren't able to do so. ~ ToBeFree (talk) 17:48, 25 December 2022 (UTC)Reply[reply]
  • I find it concerning that the request doesn't contain a single hint of acceptance of responsibility for any behavior that led to the ban. Schazjmd (talk) 18:06, 25 December 2022 (UTC)Reply[reply]
    Reply to @Schazjmd:: some expansions on text included in my appeal with more straightforwardly mea culpa formulations
    ill-conceived tussle
    I shouldn't have done it.
    things on wiki go fast. Too fast.
    I should have known that, recognized my limitations, and acted with more kindness. I apologize.
    I know I can't edit XYZ
    I had problems there before, so I won't be going back.
    keep away from those who might rile me up
    I can be riled up. This is one of my limitations. I am here on the projects to build an encyclopedia and must not let myself get distracted by that limitation.
    it's better to strive to deescalate
    I shouldn't have escalated with El Commandante, he's a good egg. Or with anyone else, whether big-, middle-, mixed-, or little-endian. I will strive, again, for kindness and calm.
    I am able to collaborate.
    I gave some people reason to wonder about this.
    Revisiting the specific disputes and the snark that, in part, got me thrown out, or the modifications to policy that resulted from it, strikes me as being mostly a bad idea. Other than my sincere apologies to anyone I offended and the analysis of my errors above, I don't know what good resassing the past will do. Except to remind me, I guess, that I shouldn't be snarky.
    Wiki moves fast. Being bold in a land full of complicated templates means that things break when you forget a pipe, a field, a tilda, a closing </spanner>, or put a semi-colon where the parser expected a colon. You can usually fix things with patience though.
    Proposal: 3-month review at AN, renewable. I would accept having a parole officer. If anyone is willing to keep an eye on me, I hereby promise you it will be very boring as far as PvP-drama goes.
    SashiRolls (talk) 22:17, 25 December 2022 (UTC) Copied from c:Special:PermaLink/719762216 — JJMC89(T·C) 05:04, 26 December 2022 (UTC)Reply[reply]
    I'm not sure how big of a requirement 'accepting responsibility' is. The only thing that's required is that problematic behaviour not repeat. People aren't really required to drop their pride and accept wrongdoing, or even to honestly feel that they acted improperly; they only need to convince that the same behaviour won't resume. ProcrastinatingReader (talk) 22:12, 26 December 2022 (UTC)Reply[reply]
    You raise an interesting point. Strictly speaking, that's true, in that future conduct is, indeed, what matters. As I see it, this isn't about policing thought, but rather it's about the confidence that the community can have in the request. It's all too easy to promise that one will stay away from trouble, so it becomes important for the community to have some insight into how credible such promises are. When the unban request contains a well thought out acknowledgement of what the past concerns were, that enhances confidence. But when, as I believe is the case here, the request seems to deflect any suggestion of personal responsibility (and this has been a pattern over numerous previous appeals by this user), then it becomes reasonable for editors to be skeptical. --Tryptofish (talk) 22:27, 26 December 2022 (UTC)Reply[reply]
    That's a really good point. Part of an appeal is demonstrating there is no longer a WP:PREVENTATIVE need for the sanction. Deflecting, not acknowledging, etc. behavior issues that led to the ban, is usually an indication that preventative sanctions are still needed for the future. It's not a matter of penance with your hat in hand begging for mercy, etc. KoA (talk) 22:43, 26 December 2022 (UTC)Reply[reply]
    ProcrastinatingReader says above: People aren't really required to drop their pride and accept wrongdoing, or even to honestly feel that they acted improperly; they only need to convince that the same behaviour won't resume
    I agree wit this and also with what Tryptofish says in reply: Strictly speaking, that's true, in that future conduct is, indeed, what matters.
    The only thing we need to determine here, as a community, is whether we think SashiRolls will act like this again, within any stone's throw of reasonable likelihood. Bans aren't punitive, yada yada. I think this person has waited a long enough time, in proportion to the initial infraction, that we can be reasonable sure they won't disrupt the project again. And all we risk is coming back here to reinstate a ban.
    To help guarantee that, I agree with GizzyCatBella on Conditional Support with a 1-way IBAN with Volunteer Marek and a TBAN from Russia and Eastern Europe (including Poland). These particular sub-sanctions can be revisited in time, when and if the user shows themselves capable of behaving appropriately on wiki. — Shibbolethink ( ) 15:13, 30 December 2022 (UTC)Reply[reply]
    Obviously, I appreciate that you agree with what I said, but I've been thinking about it, and I want to clarify what I meant, because the way that you quoted me gives my quote a meaning slightly different than what I intended. I'm not looking for policing thought, as I said, but in evaluating what to expect from future conduct, I believe it's entirely fair to look at how an appeal is framed. And the opening appeal strikes me as being like I'm really not such a bad person, and I hope that WP will realize that now. Subsequent promises have been worded much better, but, after so many prior bans and appeals, it feels to me like this has been coached. In the end, it looks to me like editors who support the appeal are persuaded by the work on other projects and editors who oppose are persuaded by the long history of repeated harassment and sanction violations, and someone with a paygrade higher than mine will have to figure out what the consensus is. --Tryptofish (talk) 20:18, 31 December 2022 (UTC)Reply[reply]
  • Oppose. As someone who was frequently the target of unpleasantness from this user, I feel very strongly that this is not something where the community should give the benefit of the doubt and give another chance, but instead it is something where it is entirely the responsibility of the user to demonstrate, without coaching, that they truly understand their own responsibility for the ban and that they have a clear idea of how to become a net positive. This is all the more important because this was made very, very clear by the community in all of the previous unban requests. What I see above is, instead, something like I'm really not so bad and I hope that WP will agree with me about that. That's not OK. (Also, I look at WPO from time to time, and what I see there is this user posting stuff that's just kind of strange, and the other WPO people ignoring it and talking around it. When you get to the point where WPO people treat you with WP:DENY, it's time to look for another hobby.) --Tryptofish (talk) 18:29, 25 December 2022 (UTC)Reply[reply]
Off-topic sniping
  • But imagine the personal growth if you, for your part, were willing to drop this near decade-long grudge. It'll be an XMAS miracle! El_C 21:58, 25 December 2022 (UTC)Reply[reply]
    Victim blaming at its finest. Floquenbeam (talk) 02:50, 26 December 2022 (UTC)Reply[reply]
    Gaslighting at its finest. El_C 04:16, 26 December 2022 (UTC)Reply[reply]
    Anyway, beyond the drama of Floq going out of his way to be unpleasant to me, which is par for the course — I, being the admin who had originally imposed an WP:IBAN (poorly-formed, but still) on both Sashi and Trypto back in 2017, feel that I am in the position to say that it isn't in fact one-sided, one victim. The argument could be made that it is, sure, but incendiary statements, like the one above where Floq accuses me of "victim blaming"... How does that help? Or, for that matter, how does Trypto's closing ("WP:DENY," etc.) sentence help? And I happen to also be speaking as the 'victim' featured in the original ban (Sashi's CBAN), of which I was not in favour of back then, either. Either way, much could be said for forgiveness, of letting go of grievances (real or perceived). It really is good for the spirit. El_C 06:56, 26 December 2022 (UTC)Reply[reply]
    El C, this is beneath you. WP:2WRONGS. Maybe you could have some personal growth in your relationship with Floq, but any life advice you have for me has nothing to do with the merits of the unban request. --Tryptofish (talk) 18:00, 26 December 2022 (UTC)Reply[reply]
    Tryptofish: El C, this is beneath you. Also Tryptofish: When you get to the point where WPO people treat you with WP:DENY, it's time to look for another hobby. El_C 18:46, 26 December 2022 (UTC)Reply[reply]
    If anyone wonders why I raised the issue of WPO, it was because SashiRolls brought it up first, as one of the reasons for lifting the ban. --Tryptofish (talk) 18:50, 26 December 2022 (UTC)Reply[reply]
    WP:DENY, etc., is the issue, still. Not the WPO, per se. I'm surprised I still need to point that out. Oh well, hopefully, I spelled it out enough now. El_C 19:03, 26 December 2022 (UTC)Reply[reply]
    The issue is whether or not there is merit to the unban request. And I've already pointed out WP:2WRONGS. --Tryptofish (talk) 19:07, 26 December 2022 (UTC)Reply[reply]
    Within the scope of that issue is you telling someone who productively contributes to several Wikimedia projects to look for another hobby, on the basis of WP:DENY. If you think replying with WP:2WRONGS suffices; if you support Floq's attack on me, for having "victim blamed" you — Okay. I still think forgiveness is good for the spirit. If you dislike that life advise, feel free to ignore it. But hopefully, others find value in that maxim, so it wasn't said for naught. See ya. El_C 19:28, 26 December 2022 (UTC)Reply[reply]
    Yes, I support and appreciate what Floq said to you. --Tryptofish (talk) 19:33, 26 December 2022 (UTC)Reply[reply]
    So much venom, yikes. El_C 19:44, 26 December 2022 (UTC)Reply[reply]
  • Point of information. (Sashi, I see you still don't have talk page access here, but I assume you're watching here and that if you respond on Commons or Meta or some other place, someone with more gravitas than I will copy it over.) The disputes that led to your being banned were off my radar or before my time. I'm doubly ill-equipped to express an opinion since despite defensive Latin and adequate French, I frequently can't follow what you post at WO, and just had to look up calumet. I quite understand that you're more concerned these days with editing at Commons and (ugh) Wikidata, and that may continue to be the case even if your ban here is vacated; I note your statement above about avoiding problem areas and editors with whom you have had disputes; and I understand you're subject to various topic restrictions ... but I'd like to see what you say in response to a simple question: what kind of editing do you envisage doing here on en.wikipedia if the ban is ended? Yngvadottir (talk) 02:19, 26 December 2022 (UTC)Reply[reply]
    I’ve restored talk page for the duration of the appeal, so they can answer your (and others’) questions. Floquenbeam (talk) 03:13, 26 December 2022 (UTC)Reply[reply]
    Reply to @Yngvadottir:
    Hi again! First off, happy Yule tidings!
    You are right to assume that I would not be very likely to abandon fr.wp, commons, and data to become an exclusive en.wp editor. One of the things I most appreciated about this time while blocked is that it convinced me to dare to edit fr.wp (French is not my native language.) I've found people to be very helpful and forgiving over there concerning gender mistakes and grammar matters.
    The coverage in English Wikipedia of the area where I live is not very good. I talked about this a bit over at WPO, mentioning some problems with Anne-Sophie Pic's bio over here. They got fixed. (Thanks, again!)
    Chances are very good that I will find pages to improve about French cities, mountains, regions, and river valleys (the Gère valley and the Rhône valley in particular). I see that a few of my photos were added to the Vienne page while I was gone, for example. There being no page for the ViaRhôna at all I could probably create one... :)
    As a jazz fan, I may occasionally also be able to translate information about local artists, e.g. Camille Bertault or Naïssam Jalal.
    If I get particularly ambitious I could translate some of the truly excellent work Zythème has done describing Rabelais' Book Four and its critical reception. (no page on en.wp)
    In short, there is no shortage of gaps in the English-language encyclopedia's coverage of Francophone letters, geography, and culture. I believe this would probably be my primary mission, with music and linguistics as likely other areas of interest. (I wrote a short article about Pierre Vernet, for example, before leaving en.wp. I see that the English article on en:Antoine Culioli could use some significant work.)
    And you know, as an active reader, things are always coming up. One of my favorite recent reads was John McWhorter's ("English is not normal"). Maybe there's something of value to pull out of such articles.
    Outside of the high-pressure topics that Iridescent pointed out at the time I'd been working on, I had little trouble. Even on some pages where potential for heated disagreement was high (e.g. Yellow vests movement, Algerian / Haitian / Sudanese protests) I luckily managed not to have too many problems at all. So, really as long as I stay away from AmPol and GMO, I think it's pretty likely there shouldn't be any problems... that said, I'll probably avoid much of anything likely to stir up great passion.
    This is a first look at your question. I also like smoothing translations, working on page layout, cleaning up references, and trying to find new ones when needed, e.g. one quick example --> Ken Burns does not even mention Theo Croker, much less source the entire first en.wp paragraph of his early life. These are the sorts of things I find on a regular basis. I could fix some of them (though not all of them) if unbanned.
    SashiRolls (talk) 04:35, 26 December 2022 (UTC) Copied from c:Special:PermaLink/719815580 — JJMC89(T·C) 05:06, 26 December 2022 (UTC)Reply[reply]
  • Support - It's no secret I think the ban was a mistake, but in any case, Sashi's productive contribs to other projects for years demonstrates the ban is no longer preventing anything except productive contribs. Levivich (talk) 06:02, 26 December 2022 (UTC)Reply[reply]
  • Oppose - So first let me say that I have stayed out of all the Sashi blocks, unblock requests, reblocks, appeals, reappears, denials of appeals, provisional unblocking, unprovisional block reinstatements and what have you. Last I recall interacting with them was when they were, I think, in between their indef blocks, and it seems they sought me out to, um, “edit alongside me”. It was not a constructive experience. Other than that, since their last blockin’ I guess they were busy at other wikis but I don’t follow those so can’t comment. I have however been engaged by Sashi over at Wikipediocracy, one may even say, “relentlessly”. If I comment there, or if someone comments about me there or even if someone writes a word that starts with a “V” on something completely unrelated there, Sashi is sure to show up there and post their latest insights and gleaned revelations they’ve acquired about my person. Usually something somewhere between “pointlessly petty” to “aggressively nasty”, all with the usual side of esoteric bizzarness. To put it transparently and curtly - judging by their behavior THERE, there’s no way in hell they’ve “reformed” or are ready to come back to editing HERE. Volunteer Marek 06:28, 26 December 2022 (UTC)Reply[reply]
  • Support - I opposed the ban, partly because I think malice was being attributed where I'm sure there wasn't any. SashiRolls is, in my view, someone who has been afflicted with too much enthusiasm and too little patience in subject areas that pushed his buttons. If he can keep away from such topics, then I think the project could welcome back a positive contributor here. The edits to other projects while banned here convince me that can happen. Boing! said Zebedee (talk) 11:04, 26 December 2022 (UTC)Reply[reply]
  • Oppose from my oppose rationale from the last appeal: SashiRolls was unblocked in November 2018, with "considerable skepticism of unblocking" and subsequently racked up five blocks in less than two years (two of which were undone by the blocking admin), plus four other sanctions, until the ban was reimposed in June 2020. It's clear that unblock was a mistake which wasted plenty of time from constructive editors.. There's a high chance the ban would have to be reimposed if it was lifted. Giving yet another last chance to banned editors is not an effective use of editor time. Hut 8.5 11:47, 26 December 2022 (UTC)Reply[reply]
  • Oppose (on hold see below) - per Hut 8.5. - GizzyCatBella🍁 14:29, 26 December 2022 (UTC)Reply[reply]
    @SashiRolls You wrote --> Best practice will be to keep away from those who might tend to rile me up. Who are those? - GizzyCatBella🍁 19:08, 26 December 2022 (UTC)Reply[reply]
    (@SashiRolls - please respond on your talk page) - GizzyCatBella🍁 19:09, 26 December 2022 (UTC)Reply[reply]
    I would be steering well-wide of anything even remotely to do with the war in Ukraine, in addition to the other Arbitration Enforcement areas alluded to above (I forget the acronyms for them all, but in general I'm not interested...). I did not come here with a calumet to battle or to say mean things about people. I came because I see en.wp's coverage of the francophone world could use work. Best to you GCB, -- SashiRolls 🌿 · 🍥 19:31, 26 December 2022 (UTC)Reply[reply]
    @GizzyCatBella: Copied from Special:Diff/1129711020MJLTalk 19:46, 26 December 2022 (UTC)Reply[reply]
    [31] - GizzyCatBella🍁 20:19, 26 December 2022 (UTC)Reply[reply]
  • Conditional Support - only under the condition of additional one-way IBAN with Volunteer_Marek (see --> [32]) and a Topic Ban from editing articles related to Russia and Eastern Europe (including Poland). (If all these conditions aren't met, then consider my voice as Oppose) - GizzyCatBella🍁 22:11, 27 December 2022 (UTC)Reply[reply]
  • Support per Lev and Boing. Their edits would be closely watched and I’m sure someone would report any potential issues quickly (though I don’t expect there would be any). Mr Ernie (talk) 18:22, 26 December 2022 (UTC)Reply[reply]
  • Oppose, with a caveat. I had a couple of interactions with SashiRolls in the past, and they were not so negative. That was a fair ban in the past, and I do not see what has changed based on the comments and responses by SashiRolls. Perhaps she/he could be unbanned if one of the admins takes a responsibility of observing their future editing and re-blocking SashiRolls again at the first sign of trouble. However, after looking at the very long block record of SashiRolls, it seems such approach had already been tried, so that the chances of success are slim. Based on their comments, SashiRolls is planning to voluntarily stay away from a number of different widely defined subjects and a number of contributors (an equivalent to multiple topic bans and interaction bans). Will it work in practice? If SashiRolls is going to be unbanned, the lists of such topics and contributors should be explicitly defined. This all seem to be problematic. My very best wishes (talk) 18:29, 26 December 2022 (UTC)Reply[reply]
I think this is something for admins to decide because they will be responsible for enforcement. According to Yngvadottir (see below) there are 4 active topic/interaction bans for SashiRolls. If admins think this will not ensure waste of time and drama in the future, then yes, let's unban. My very best wishes (talk) 17:41, 27 December 2022 (UTC)Reply[reply]
The in practice comments are really spot on here for unban considerations. Those are some wide topic ban areas, so if they cross the line there again or start it up in a new topic, how much sniping and denials are editors who try to bring the issues up going to have to deal with? How would that past problem be alleviated? I don't know of a good answer considering past history where it's likely for someone to just paint editors either being pursued by SR or trying to deal with problems as just out to get SR. That's really the can of worms I'm worried about. KoA (talk) 19:44, 27 December 2022 (UTC)Reply[reply]
Yeh, the ability of SashiRolls to stir conflict, even between admins, is definitely a factor here. My very best wishes (talk) 18:26, 28 December 2022 (UTC)Reply[reply]
  • Support per Levivich and Boing!. François Robere (talk) 20:04, 26 December 2022 (UTC)Reply[reply]
    • As an aside, I find it somewhat disingenuous for one to object to the appeal on the grounds of posts made to WPO, when elsewhere they claimed it as a "safe space", writing that "[the] whole point of WPO is that you can say things plainly and directly without genuflecting to the gods of hypocrisy the way you do on Wiki".[33] François Robere (talk) 14:22, 30 December 2022 (UTC)Reply[reply]
  • That block log is pretty terrible; it's not that hard to not rack up a lot of blocks, or heck, to not rack up any blocks. It's fair to assume you probably didn't have the most enjoyable editing experience here? So a blunt and genuine question: why do you still want to participate here, verses just finding another hobby? ProcrastinatingReader (talk) 22:21, 26 December 2022 (UTC)Reply[reply]
    A number of the early blocks are related to a bad actor Sashi and others like me tangled with, who turned out to be a exceptionally skilled former admin socking to avoid a topic ban. These blocks were frequently brought up in later cases and should be considered in the context. If you set the clean slate post the Cirt stuff I don’t think a site ban would ever have been considered. Mr Ernie (talk) 02:56, 27 December 2022 (UTC)Reply[reply]
    In fairness, the point about needing to look past Cirt is a very valid one. For easy access, here is a link to that block log: [34]. The unblock on November 5, 2018, is the unblock resulting from recognizing the Cirt problem. So everything after that, from June 4, 2019 onward, is really what we should consider relevant to the present discussion. And it's still pretty awful, even after making that correction. Again and again, personal attacks, battleground, harassment. Not trivial stuff, and not isolated instances. And violating existing restrictions ([35]). Consider what that means: where some editors argue here that we should unban while setting restrictions, past experience demonstrates a tendency to break those promises. I wasn't exaggerating when I talked (below) about a time-sink. There needs to be a lot stronger case than saying that one opposed the ban in the last discussion, or it's just too much enthusiasm, or at least there's been no socking, or this is a good time to try WP:ROPE because there will be lots of eyes on him. We are ridiculously beyond the point where the WP:ROPE ran out. --Tryptofish (talk) 22:06, 27 December 2022 (UTC)Reply[reply]
  • Oppose. As others have mentioned, their appeal is filled with WP:NOTTHEM language, which is a pretty strong indication they're going to continue the tendentious behavior that got them banned and continue the time sink they created for the community when they were here. We also definitely can't give weight comments calling a ban to correctly prevent community-wide disruption a "mistake" either. One needs only to look at their block log and especially the last straw ban proposal by TonyBallioni [36] and the close by MastCell there. That attitude is just a repeat of what I remember dealing with back when they were here.
Volunteer Marek also makes a good point on relentlessness. SR would often pursue editors on-wiki, and I among others ended up having to try to cleanup major disruptions in the GMO topics because of SR doing that. When folks mention SR's off-wiki activities after the ban especially I'll echo Volunteer Marek that SR was often pursuing editors off-wiki that they had hounded on-wiki. This appeal falls pretty flat after seeing that. The trouble with the relentlessness that I'm seeing revived here again is targets of SR were often hounded and victim-blamed/gaslighted by SR or others. That often complicated cleaning up the disruption or just simply getting action on sanctions because you'd often have people rushing to say it was SR's target that was causing the problems.
Mix that with NOTTHEM comments, they were just getting "riled" up, etc. like I'm seeing in this appeal and we have a recipe for being right back to the situation we were in before the ban. For the amount of disruption they were the center of, the bar for an unban is much higher a general lack of acknowledgement appeal like this. Too much of a time-sink for the community with this apparent attitude continuing. KoA (talk) 22:36, 26 December 2022 (UTC)Reply[reply]
  • Support per Levivich, Boing! and Mr. Ernie. I haven't followed the off-Wiki drama so I won't evaluate that. Opposers fail to convince. I do feel that SR has followed the procedure that leads to reconsideration of an unban. SR obviously knows they are going to be watched, and if SR keeps it clean, the 'pedia wins, and if not, gets rebanned. Simple. Jusdafax (talk) 23:04, 26 December 2022 (UTC)Reply[reply]
For background, a frequent problem at admin boards often were editors such as Jusdafax, Mr. Ernie, and Levivich jumping in to defend SR regardless of the disruption SR caused. The AE where we had to modify SR's GMO ban is a good example of that.[37] Generally you'll see various forms of denial there claiming no disruption by SR despite admins still determining the sanction was needed (and tweaked to clearer language). Similar things happened at SR's site ban thread too despite plenty of evidence.[38] There's also usually bits where those of us who were hounded due to SR's actions were portrayed as just out to get Sashirolls peppered in some of those discussions too.
Denials of SR's behavior have been a recurring issue from vocal minorities, so for those who are entirely uninvolved, I do advise reading the closes, evidence, blocks, etc. where simple denials don't really match up with reality. Those of us who were directly affected by SR's antics had to deal with a lot from SR themselves, but also their supporters muddying the waters or outright lashing out when we tried to get help. While I personally shouldn't have to deal with Sashirolls much due to their topic bans if they came back, I sure wouldn't wish others having to go through what myself or others did. Just punting the buck along to a new topic each time is in part why the community decided on the site ban instead, and crafting an appeal for that needs something pretty substantive rather than merely following unbanning procedure. KoA (talk) 00:31, 27 December 2022 (UTC)Reply[reply]
I am continually surprised that people can hold grudges like this over such petty reasons for so long. I wondered why you came after me at an unrelated AE case a few weeks ago when I didn’t even recognize your name or know we had interacted, but now I understand. The topic bans should handle the areas where there were concerns as you acknowledge so why not let’s give that a try on this volunteer project? Mr Ernie (talk) 03:05, 27 December 2022 (UTC)Reply[reply]
This is exactly the kind of gaslighting multiple editors had to deal with, and you've been repeatedly cautioned about hounding editors like at that AE you mention. Yes, I noticed your behavior issues during the Sashirolls stuff and at that AE, but trying to claim anyone who notices behavior issues from you or others as just having a "grudge" is a tired old WP:BATTLEGROUND tactic. That just disrupts admin boards.
With that, the sniping at those who tried to deal with Sashirolls and related behavior issues clearly hasn't gone away. That is why it's being brought up because it contributed to the issues resulting in SR's ban and is yet another hurdle to navigate in a potential unban. The whole point above was that topic bans didn't help the behavior since it just moved to whatever topic SR moved on to, and whoever got stuck dealing with it had harassment and wikilawyering to deal with. The serious question to answer is why should we burden other parts of the community (yet again) with that likely scenario even in a WP:ROPE situation? There needs to be really good justification rather than talking past it that we've seen from SR's appeal so far. There's a lot of red flag language in that regard. KoA (talk) 18:47, 27 December 2022 (UTC)Reply[reply]
Accusing editors of gaslighting and lying about sanctions they’ve never received is poor form at the admin boards. But par for the course I suppose. I don’t expect anyone to defend me, but maybe this type of behavior will color uninvolved reviewers perspectives on this issue. Mr Ernie (talk) 20:28, 27 December 2022 (UTC)Reply[reply]
I trust that uninvolved reviewers will follow the evidence (diffs and links) in order to gain a perspective, per Dorothy Gambrell, perhaps 🐈. ---Sluzzelin talk 20:44, 27 December 2022 (UTC)Reply[reply]
Indeed. We even needed to craft a new WP:ASPERSIONS principle in the GMO case because of unsubstantiated claims, though that was before SR's involvement. Either way to be clear, the AE section Mr Ernie was referring to earlier[39] is where their previous sanction related to hounding was recently discussed, specifically that they had been banned from WP:AE for a time for hounding/aspersions and that it was a concern again. They were already aware of their past sanction though (and they even referenced that AE I just linked despite the flourish above), so it's really odd that they go on a tangent about an easily verifiable thing being a lie here when it wasn't even in my initial comment. That's a confusing tangent.
My focus was on the links I gave in my main reply above on interactions related to Sashirolls at admin boards with editors repeatedly dismissing SR's issues or things like we're seeing here now accusing others of grudges. There is a WP:BATTLEGROUND mentality that seems to follow SR, in part because of their own actions, but also what we see playing out here from other editors. It just makes an unban appeal even trickier to navigate and why some of us who had to deal with SR are so cautious. KoA (talk) 22:13, 27 December 2022 (UTC)Reply[reply]
It had nothing to do with hounding. Please stop lying. You are the only one who has mentioned hounding, and now you just fait accompli refer to it as that. When you are wrong about something, referring back to it doesn’t make it any more right. Mr Ernie (talk) 23:24, 27 December 2022 (UTC)Reply[reply]
I want to respond to that point about supposedly holding petty grudges. For me, this is no more about holding a grudge, than it is about being an enabler when editors who have long memories about past disputes over GMOs or AmPol come here to support the request on behalf of someone they perceive as having been on their "team". And an awfully high percentage of the editors who have commented here fit that description. So we can go back and forth calling one another grudge-holders or enablers, or we can look at what would be in the best interests of this project. And there's nothing petty about wanting to spare the project the highly predictable time-sink that would result from bringing back someone who has long been a time-sink, and has never, even at their best, been a particularly helpful contributor. --Tryptofish (talk) 19:54, 27 December 2022 (UTC)Reply[reply]
  • Support I was against the ban when it was first imposed and I'm still against it now. LEPRICAVARK (talk) 03:56, 27 December 2022 (UTC)Reply[reply]
  • Support. I have read the statements above by editors who don't trust SashiRolls because they have been hurt in the past. I cannot judge anything SashiRolls has written in the non-public areas of Wikipediocracy, because I'm not a member there, so I hope I'm not slighting the concerns of Volunteer Marek, in particular. So I spent some time reading and re-reading the June 2020 siteban discussion (also linked by SashiRolls at the top of this discussion). And I searched ineptly for restrictions to which they're still subject. It is my understanding that these are: (a) an interaction ban with Tryptofish (whether one-way or two-way has been a subject of some disagreement and/or change); (b) a GMO topic ban; (c) a post-1932 American politics topic ban; (d) a prohibition on commenting on AE requests to which they are not a party, imposed in 2016. Are there any others? It seems to me that the core question is whether these restrictions are sufficient. SashiRolls has pledged to keep away from those who might rile me up and strive to deescalate. I don't think they should be judged harshly for not listing the names, especially since they have an IBan with at least one, and the emphasis in the appeal is on how they intend to stay out of trouble, so I don't find the mention of their own thought processes—getting riled up—to be inappropriate. I also note that their statement I know I can't edit GMOs, Am-Pol or WP:AE corresponds to their edit restrictions; so I see no truculent "I wish I could ... " in it. If there are indeed no other edit restrictions or IBans in place, given that SashiRolls has named several areas where they plan to make edits, has been editing productively on several other projects, and has responded plainly and levelly to questions so far in this appeal, I'm inclined to support. I will add that on my reading, that 2020 ban discussion was very divided; MastCell's key point in closing it was: While there is no numerical threshold for consensus, it would be inappropriate to close a discussion like this—with >2/3 of commenters supporting action—as "no consensus". There has since been a withdrawn appeal, followed by 2 years. Consensus can change in that time. Wikipedia can change in that time, and I have a tiny, inexpert suspicion that after 2½ years, we might today be less inclined to siteban an editor after a discussion that shook out the way that one did (including El_C's attempted intervention). Anyway, we're here now. If the ban is rescinded, it will of course be a WP:ROPE situation, with many eyes on SashiRolls' editing. Perhaps, in addition to the topic bans, the concerns of some of those in opposition could be allayed by addition of some more IBans? Volunteer_Marek, for example? And I would suggest the IBan with Tryptofish should be made 2-way, if it isn't, in order to simplify matters. Yngvadottir (talk) 10:55, 27 December 2022 (UTC)Reply[reply]
A topic ban from Eastern European topics, including Russia, would also be a minimum since I’m not the only one they’ve “followed around” in that topic area. Volunteer Marek 18:39, 27 December 2022 (UTC)Reply[reply]
And I would suggest the IBan with Tryptofish should be made 2-way, if it isn't, in order to simplify matters. One thing we absolutely should not be doing is re-harassing one of SR's old targets from past disputes by doing that, especially since the original 2-way I-ban on appeal was considered a throwing the baby out with the bathwater situation and very uncontroversially changed to 1-way.[40] KoA (talk) 19:44, 27 December 2022 (UTC)Reply[reply]
KoA just beat me to saying what I was going to say, thanks. Yngvadottir, if you're going to say stuff like that about me, please get your facts straight first. There's nothing close to a subject of some disagreement and/or change about it. I suggest that anyone who wants to know what actually happened go to the link that KoA just gave, and open the collapsed AE section to see more than just the closing statement in the header. You will see that the original 2-way version was explicitly designated as having been "no-fault" with respect to me, and you can read for yourselves the admin discussion by Newyorkbrad, Thryduulf, and TonyBallioni. It's worth seeing what three highly trusted admins determined about the merits of the situation. And it's worth noting how they were quite able to see through and dismiss the same kinds of WP:2WRONGS diversions that are being offered again here in this discussion. --Tryptofish (talk) 20:07, 27 December 2022 (UTC)Reply[reply]
Fair enough, Tryptofish; in researching the situation, I missed that discussion. Some of your talk above of editors ... jumping in to defend SR and of vocal minorities strikes me as unpleasant, but you're entirely right, I am not aware of the extent of the disruption SashiRolls has caused in the past, or of the suffering you and others are referring to. Volunteer Marek, I think a lot of editors are also at a similar disadvantage to me in judging whether SashiRolls might be disruptive in the area of Eastern Europe / Russia, since you appear to be basing that judgement on non-public forum posts? I haven't seen anyone mention that as a problematic area in the previous discussions? But then again, there's a new war this year. However, it appears to me that between their pledge to stay away from editors who "rile them up", and the innocuous topics they say they forsee editing here (it seems that apart from my error about the basis of the IBan, I've got it right that those are the 4 in force?), new restrictions shouldn't be necessary. I find myself persuaded they will be a net positive if unbanned. But I admit that's partly because I find the argument that they never were to be exaggerated; respected editors at the banning discussion, when the dispute was hot, made that point. More importantly, it's now two and a half years later; people can change; their appeal is calmly couched and lists good contributions on multiple other projects; they appear to have sensible plans for proceeding (including not being fixated on this particular project). Yngvadottir (talk) 04:13, 28 December 2022 (UTC)Reply[reply]
Thank you for that. However, the "unpleasant" comments that you now attribute to me are not things that I ever said. It was another editor, not me. --Tryptofish (talk) 15:46, 28 December 2022 (UTC)Reply[reply]
Also, one thing that I did say is relevant to the argument about not needing new restrictions. I linked above to blocks for violating existing individual restrictions ([41], also [42]), and I think that history gives pause to being confident about accepting promises on face value. --Tryptofish (talk) 16:06, 28 December 2022 (UTC)Reply[reply]
  • Support - If there's been no socking, during the ban. GoodDay (talk) 17:44, 27 December 2022 (UTC)Reply[reply]
  • Neutral, with a proviso - As one of their victims, I won't !vote. But, if they are unblocked, they should be TBanned from all DS articles and all admin boards. A promise has little meaning. O3000, Ret. (talk) 22:14, 27 December 2022 (UTC)Reply[reply]
  • Oppose unban. Even though I'm not familiar with the history of the case, I am confident that a person with this kind of block log is not going to return as a collegial and productive editor. Sandstein 17:11, 28 December 2022 (UTC)Reply[reply]
    🤦🏼‍♂️ Levivich (talk) 17:44, 28 December 2022 (UTC)Reply[reply]
  • Support - last chance saloon, and beware of controversial areas. starship.paint (exalt) 13:16, 29 December 2022 (UTC)Reply[reply]
  • Oppose guys, this isn't a second chance request. SashiRolls has had multiple chances throughout their involvement on the English Wikipedia, and every time it comes back to one thing: they view every disagreement as a battleground, make up enemies in their head, and relentlessly focus on showing how their enemies are out to get them. Then when people get tired of having to deal with that and point out the problems, they claim it is evidence that what they have been saying is correct, without pausing to consider if whether the objections to their behaviour might have some grounding in facts.
    If we unblock them, there will be another dispute. That dispute will follow just like all the others had. And we won't be able to do anything about it because we just unbanned them and an unban is a get out of jail free card where no admin is willing to take any action against you for 3-6 months. I'm around a lot less these days, so this isn't anything personal against SashiRolls or something that I think will have that huge an impact on me. But I do absolutely think an unban would be a firm net negative to the project and would increase the amount of disruption that admins who work in controversial areas have to deal with. TonyBallioni (talk) 22:24, 29 December 2022 (UTC)Reply[reply]
  • Oppose My thought in supporting or opposing lifting the ban is simple: Do I feel like we will be right back here again in a relative short period of time. In this case, I do. SR has shown that they are going to go bull in a china shop to get their way. The ban WAS the last chance, and if we are back to this again, are we going to be arguing this all over? RickinBaltimore (talk) 22:29, 29 December 2022 (UTC)Reply[reply]
  • Support per Levivich's current (see above) and previous comments: "the incivility from Sashi is narrowly focused at very few people, who frankly aren't blameless themselves. I would support two way IBANs all around, but not a site ban". This would have made much more sense makes even more sense now. The site ban should be lifted, but all other restrictions should remain.
Also of note: the comments about "a person with this kind of block log" seem unnecessary. If you read, most of the recent ones are blocks and unblocks to allow for appeals/ArbCom proceedings. If you feel that something in particular is a problem, please specify. I'd much rather place trust in someone with 30 traffic tickets in 40 years of driving than a one-time murderer (even though the former's "rap sheet" is longer). Buffs (talk) 22:41, 29 December 2022 (UTC)Reply[reply]
Frankly, it's getting pretty old to keep hearing that those of us who have been harassed by SR are the ones at fault. And there are a ton of blocks (post-Cirt) that were not mere adjustments for appeals, but were for personal attacks, battleground conduct, harassment, and violation of existing individual restrictions. I'd say that that's something in particular that's a problem. --Tryptofish (talk) 00:49, 30 December 2022 (UTC)Reply[reply]
  • Support. I am new here, but it looks like there are a lot of strict rules that are easy to break by accident. Wikipedia administrators should be able to give people a second chance when they mess up and they should un-ban SashiRolls. If SashiRolls returns and keeps making the same mistake over and over, then administrators should ban the user again until the problem is fixed. Lobster from Maine (talk) 02:31, 30 December 2022 (UTC)Reply[reply]
    (note - the above is a one day old account) - GizzyCatBella🍁 21:43, 30 December 2022 (UTC)Reply[reply]
  • Support per Levivich mostly. Frankly, I don't see anything preventative about this ban that wouldn't be as easily and comprehensively covered by extant restrictions. And the idea that somehow SR could get away with even breathing in the wrong direction without this ban / a block being (re)imposed quicker than you can imagine. They have clearly been editing productively elsewhere; I suggest that we demonstrate some trust, after some years, and that perhaps if we don't poke the bear, the bear might bring some of that productivity back here. We gain a useful editor, SR behaves themselves, and a happy vista is viewed by all, hein? SN54129 18:03, 30 December 2022 (UTC)Reply[reply]
  • I'm agnostic about unbanning SashiRolls—they're clearly passionate about the project and have contributed substantially, but also seem a poor fit for the social aspects and expectations of this website. Maybe that's changed, although my experience is in line with TonyBallioni's in that I think we're more likely than not to end up back here, with regrets, if we unban them. That said, I could support an unban as long as it's clear that this isn't a second chance, but more like an nth chance, and that there won't be an (n+1)th chance.
    Setting aside SashiRolls, I do have to say that I'm really disappointed by the behavior of some of his supporters—a dynamic that goes back to his original ban. The victim-blaming is just a really shitty thing to do, but there's plenty of it in this thread. We should welcome or even solicit victim-impact statements when we consider unbanning people who were banned for cause, and we should consider the impact of an unban on people who previously bore the brunt of the banned editor's behavior. We should center the time and goodwill of those victims at least as much as we center the banned editor's perceived right to another bite at the apple. Instead, we usually pontificate about forgiveness, patronize the victims for their "pettiness", and pat each other on the back for our greatness of spirit—easy enough to do when the cost will be paid by someone else. MastCell Talk 19:14, 30 December 2022 (UTC)Reply[reply]
    That second paragraph: amen! Thank you for that. --Tryptofish (talk) 19:21, 30 December 2022 (UTC)Reply[reply]
    Music to your ears, Trypto, I'm sure. Anyway, while this appeal doesn't seem likely to pass, at least MastCell, whose stated "agnosticism" here seems highly questionable, doesn't get to WP:SUPERVOTE this one, as such a SUPERVOTE wouldn't be needed. This, folks, is the absurdity. I, the actual victim in the original ban am accused of "victim blaming" (but I'd likely be lauded by Floq, Trypto and MastCell if I were to forever not forgive Sashi). It was I who was disparaged unrelentingly at the WPO during the original ban (though not so much by Sashi). It was I whom WPO admin trantino attempted to doxx back then.
And these carefully-crafted words from MastCell are hurtful, but in my experience from other disputes, that is MastCell's intent—though he cleverly doesn't mention me by name—to cause hurt to the opposition. I've been on the receiving end of it several times in the past few years. Otherwise, I never really see him around. Trypto's grievances of many years, however, are far from "petty." If they were, they'd be easy to overcome.
As for Floq's fire-and-forget animosity, I'm not gonna bother addressing that beyond my now-hatted comments. Obviously, my humor there had the opposite of its desired diffusive effect, as admittedly, I might have miscalculated/forgotten how deep these grievances go, to the point of being seemingly insurmountable. Should we expect anything different in an appeal years from now? And years from then, as well? Et cetera, etc.? Unfortunately, the answer appears to be a resounding no. El_C 18:07, 31 December 2022 (UTC)Reply[reply]
In other words, everyone is being so, so unfair to you, which demonstrates that this appeal has merits. --Tryptofish (talk) 20:07, 31 December 2022 (UTC)Reply[reply]
Yes, yes, poor me, sad merits. But no, Trypto, far from "everyone." But I do expect much disparagements against myself from certain people to pile on high, irrespectively of anything I could possibly say now. It's gonna suck, but it's almost certainly unavoidable. It is what it is. El_C 20:23, 31 December 2022 (UTC)Reply[reply]
MastCell, while I somewhat appreciate the point you were trying to make in your second paragraph, I do not think it was wise or fair to use an emotionally-charged term such as "victim-blaming" to describe what is happening here. In this thread, several editors have argued against the unban by making unsupported negative comments about Sashi. I haven't seen anyone bat an eyelash over that. If that sort of thing is going to be allowed to stand, then I'm afraid we can't have it both ways. Besides, if the full context of Sashi's ban involves problematic behavior by his antagonists, then I think it is highly relevant to bring that up here. So, while your disappointment is noted, I suspect it is misguided. LEPRICAVARK (talk) 17:54, 1 January 2023 (UTC)Reply[reply]
No, you are wrong about that, and your comment should not be allowed to stand unchallenged. If there is a concern about bad conduct by anyone else, then raise it in a separate thread specfically about that, instead of throwing around a vague aspersion in the hope that two wrongs make a right. And if there is a concern about unsupported negative comments about SR, refute them. --Tryptofish (talk) 19:26, 1 January 2023 (UTC)Reply[reply]
Challenge me all you like, but you greatly overestimate my interest in wasting my time on this matter, especially since the community is clearly unwilling to allow Sashi back at this time. At any rate, I haven't really seen any "victim-blaming" in this thread, and I remain of the belief that the background context of Sashi's ban is relevant to this discussion. Opening a separate thread would generate more heat than light, as you undoubtedly realize. And no, the onus is not on me to refute other people's unsubstantiated assertions about Sashi. LEPRICAVARK (talk) 04:21, 2 January 2023 (UTC)Reply[reply]
It's not a challenge to you, personally. But if people are going to complain that what MastCell said was unfair, then it behooves them to back up their claims, rather than just fold when someone asks them to show their cards. --Tryptofish (talk) 18:51, 2 January 2023 (UTC)Reply[reply]
Meh. I don't see MastCell backing up his claims either, and you don't have any problem with that. Heck, last I checked you were quoting him in an essay. LEPRICAVARK (talk) 22:28, 2 January 2023 (UTC)Reply[reply]
Thank you for looking into my edit history. That essay is WP:DEFLECT, which is about, well, deflecting from the issue at hand. MastCell wrote about comments in this thread, so it is self-evident what he was referring to. --Tryptofish (talk) 22:39, 2 January 2023 (UTC)Reply[reply]
Well, as I said earlier, I have not seen any "victim-blaming" in this thread. So regardless of whether a person could infer which comments he was referring to, I wouldn't say that he backed up his claims. LEPRICAVARK (talk) 01:09, 3 January 2023 (UTC)Reply[reply]
  • I'm ambivalent. On the one hand, indefinite doesn't mean permanent and SashiRolls has been doing verifiably good work on other projects. On the other hand, he was given a "last chance" in his 2018 unblock and after two years of issues wound up with this ban. On balance, I don't see myself supporting, but if the community wants to give a "last last chance" given his work on Commons, I wouldn't be strongly opposed, though I agree with MastCell and TonyBallioni that prior history isn't promising. Wug·a·po·des 21:11, 30 December 2022 (UTC)Reply[reply]
  • While I have no opinion about Sashi's request at this time, having read this thread I do have an observation and a thought. My observation is that we don't have good ways of assigning responsibility in a conflict. We essentially end up assigning it as 50/50 or 100/0. If it's really say 60/40 a 50/50 outcome isn't too bad. But sometimes it seems like when it's lopsided - say 90/10 or 95/5 - we're just as likely to default to 50/50 as 100/0, if not formally at least in comments. I don't know what there is to do about that but our lack of nuance in these discussions is something I see reading through comments here and see as the cause of some of the rancor that has happened. My thought is for people with Sashi's general profile, if rather than a straight unblock if something more akin to the unblock ArbCom did with Lightbreather might leave people feeling better. This would also address the general point Tony made above. Best, Barkeep49 (talk) 20:41, 1 January 2023 (UTC)Reply[reply]

Unacceptable username

The following discussion is closed. Please do not modify it. 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)Reply[reply]

You'll have to talk at the people at el.wikipedia about that. --Golbez (talk) 21:14, 27 December 2022 (UTC)Reply[reply]
Neutral comment (this is Greek for 'goddamn it' for those trying to figure it out; no account on at this time) Nate (chatter) 22:51, 27 December 2022 (UTC)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Verbal abuse

The following discussion is closed. Please do not modify it. 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)Reply[reply]

Could you supply a diff for that? Phil Bridger (talk) 20:48, 27 December 2022 (UTC)Reply[reply]

And this editor carries the status of "Veteran Editor III" Advancingreturns (talk) 21:06, 27 December 2022 (UTC)Reply[reply]
"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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
You should consider writing shorter posts on Talk:Sponsianus. Mackensen (talk) 21:29, 27 December 2022 (UTC)Reply[reply]
OP partial blocked. 331dot (talk) 21:34, 27 December 2022 (UTC)Reply[reply]
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

The following discussion is closed. Please do not modify it. 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)Reply[reply]

(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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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? Advancingreturns (talk) 12:22, 28 December 2022 (UTC)Reply[reply]
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)Reply[reply]
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)Reply[reply]
As this user has now moved on to outright vandalism, Favonian has extended the block indefinitely and site-wide. I'll revoke TPA as suggested by Lavalizard101 if there's any further inappropriateness on their talk page. --Yamla (talk) 12:36, 28 December 2022 (UTC)Reply[reply]
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)Reply[reply]
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Coffee News is copied from an advertisement

Hello Wikipedia administrators. The Wikipedia page on Coffee News copies directly from 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)Reply[reply]

I have reverted the edits to the non-advertisement version. Thank you for letting us know. ... discospinster talk 01:44, 30 December 2022 (UTC)Reply[reply]
Fyi, sent to AfD as the restored text is still problematic. Slywriter (talk) 02:06, 30 December 2022 (UTC)Reply[reply]
Thank you. Lobster from Maine (talk) 07:08, 30 December 2022 (UTC)Reply[reply]

Admin with expertise in Korean history requested

There 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)Reply[reply]

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)Reply[reply]
Blocked as a sock puppet of VeryGoodBoy by Bbb23. -- LCU ActivelyDisinterested transmissions °co-ords° 19:16, 30 December 2022 (UTC)Reply[reply]
Yes, this editor was blocked, but this is an unblock request. Phil Bridger (talk) 19:35, 30 December 2022 (UTC)Reply[reply]
much embarrassment, please ignore me -- LCU ActivelyDisinterested transmissions °co-ords° 13:02, 31 December 2022 (UTC)Reply[reply]

How to request a copy of a deleted article?

Sorry if this is the wrong forum. A user on Twitter wants to look at the first and last versions of a deleted article and the last version of the article's talk page, to access some etymology info. What's the procedure for this? link to tweet thread --Anthonyhcole (talk) 07:55, 30 December 2022 (UTC)Reply[reply]

@Anthonyhcole: Which page? :) — TheresNoTime (talk • they/them) 08:08, 30 December 2022 (UTC)Reply[reply]
Yeah np, I could put it up temporarily. Let me know which page it is/was. El_C 08:16, 30 December 2022 (UTC)Reply[reply]
Thank you both. I'll get back to you. --Anthonyhcole (talk) 10:29, 30 December 2022 (UTC)Reply[reply]
What a mystery! Please ping me when you find out because I'm likely to not remember. El_C 12:29, 30 December 2022 (UTC)Reply[reply]
El_C and TheresNoTime, the article name is Castleroid. Could you post it somewhere for a day or two please? Not sure which timezone the request is coming from. --Anthonyhcole (talk) 00:50, 31 December 2022 (UTC)Reply[reply]
I've restored all deleted revisions (from 1st to last), which you can find in the revision history: here. HTH. El_C 01:25, 31 December 2022 (UTC)Reply[reply]
@El C: Just FYI I've also restored Talk:Castleroid per the above — feel free to delete it again when you delete the article Face-smile.svg TheresNoTime (talk • they/them) 01:50, 31 December 2022 (UTC)Reply[reply]
Cool thx. No rush about re-deleting, either, as TheresYesTime (←see what I did there) — take a day, take a week, it's all good. El_C 02:04, 31 December 2022 (UTC)Reply[reply]
Thank you (pl)! I'll ping you when she's finished with it. --Anthonyhcole (talk) 02:25, 31 December 2022 (UTC)Reply[reply]

Outgoing members of the 2022 Arbitration Committee

The Arbitration Committee thanks our outgoing colleagues whose terms end on 31 December 2022:

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)Reply[reply]

Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard § Outgoing members of the 2022 Arbitration Committee

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)Reply[reply]

@Yann:  Done I've undeleted that file revision. Legoktm (talk) 21:51, 30 December 2022 (UTC)Reply[reply]

Hall & Oates

Would 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)Reply[reply]

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)Reply[reply]
Thank you Cullen328. -- Marchjuly (talk) 07:37, 31 December 2022 (UTC)Reply[reply]
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)Reply[reply]

JJMC89 bot deleted the Bangladesh Football Federation logo from their National Team pages (both men & women)

Hello Wikipedia administrators, I seek your highly serious attention to the matter that JJMC89 bot ( ) 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 (talkcontribs) 19:52, 31 December 2022 (UTC)Reply[reply]

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 (talkcontribs) 19:39, 31 December 2022 (UTC)Reply[reply]

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)Reply[reply]
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)Reply[reply]

Circumcision related close

Could 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)Reply[reply]

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)Reply[reply]
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)Reply[reply]
  • 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)Reply[reply]
    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[dubiousdiscuss] 12:58, 2 January 2023 (UTC)Reply[reply]
    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)Reply[reply]
    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[dubiousdiscuss] 14:30, 2 January 2023 (UTC)Reply[reply]
    @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)Reply[reply]
    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[dubiousdiscuss] 21:39, 2 January 2023 (UTC)Reply[reply]

Intentional vandalism by a user

If you observe this 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. (talk) 08:09, 2 January 2023 (UTC)Reply[reply]

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)Reply[reply]

Lublin Airport

Afternoon 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)Reply[reply]

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)Reply[reply]
Thanks. I'm always jumpy when reversions happen. doktorb wordsdeeds 17:00, 2 January 2023 (UTC)Reply[reply]

Please review my block

The following discussion is closed. Please do not modify it. 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)Reply[reply]

  • 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)Reply[reply]
    Though I agree a warning first would have been better. -- ferret (talk) 18:15, 2 January 2023 (UTC)Reply[reply]
    TY for that. That is ALL that I would have needed! Moops T 18:21, 2 January 2023 (UTC)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    the seriousness of the situation 😂  Tewdar  18:40, 2 January 2023 (UTC)Reply[reply]
    I still don't think Moops realises they were doing anything wrong, despite mass spamming people. Secretlondon (talk) 18:50, 2 January 2023 (UTC)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
  • Oppose block. Discussing the matter with Moops should have been the first step. Cullen328 (talk) 18:08, 2 January 2023 (UTC)Reply[reply]
  • It looks fairly draconian to block without discussion under these circumstances... Salvio 18:11, 2 January 2023 (UTC)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
  • Oppose block - you could have asked them to stop first. Black Kite (talk) 18:19, 2 January 2023 (UTC)Reply[reply]
  • Please unblock so they can send me a Happy New Year message. ☹️  Tewdar  18:24, 2 January 2023 (UTC)Reply[reply]
    You got yours coming! :) Moops T 18:32, 2 January 2023 (UTC)Reply[reply]
    Thanks Moops, Happy New Year! 😁👍  Tewdar  18:38, 2 January 2023 (UTC)Reply[reply]
  • Oppose block - A classic case of WP:AGF not being extended to long time regular 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)Reply[reply]
  • 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)Reply[reply]
    • 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)Reply[reply]
    Moops T 18:32, 2 January 2023 (UTC)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    No. That was accurate actually. :) Moops T 19:13, 2 January 2023 (UTC)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    For what it's worth: [43]. I encourage other editors to consider following my lead. --Tryptofish (talk) 19:31, 2 January 2023 (UTC)Reply[reply]
    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)Reply[reply]
  • Comment - I didn't feel disrupted, by Moops' HAPPY NEW YEAR message. GoodDay (talk) 19:18, 2 January 2023 (UTC)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]

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)Reply[reply]

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)Reply[reply]
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)Reply[reply]
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)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    No, it most definitely is not supposed to be standard practice! Boing! said Zebedee (talk) 21:42, 2 January 2023 (UTC)Reply[reply]
    OK. TY Moops T 21:44, 2 January 2023 (UTC)Reply[reply]
  • 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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
    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)Reply[reply]
  • 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)Reply[reply]
  • 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 😊Reply[reply]
  • 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)Reply[reply]
  • 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)Reply[reply]
The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Appeal of partial block on Sca


After months of being blocked from WP:ITN/C, I have come to understand that ITN is serious business, not a venue for jokes or personal comments. I again apologize for posting the wholly inappropriate joke I made about Chinese President Xi on Oct. 26, 2022, and for being too garrulous with my comments at ITN/C in the past. I also realize that ITN is a different place than it was in previous years. I absolutely promise that, if unblocked, I would exercise prudent, judicious conduct, seek to collaborate with other users active at ITN, and work cooperatively to make this Main Page fixture transparently informative and useful to its global audience. Thank you. – Sca (talk) 14:13, 2 January 2023 (UTC)

This is your second block from ITNC. Why should we now believe your promises regarding editing there? 331dot – (talk) 14:57, 2 January 2023 (UTC)Reply[reply]

I'm glad you asked that. I was just about to add to this appeal a suggestion that the recipient review the recent history of my civil and collaborative comments at Featured Picture Candidates (WP:FPC). At FPC I've tried to be polite, circumspect and helpful, and some other users there have indicated appreciation.
FPC is similar in some respects to ITN/C: Proposals are made, comments voiced, and the items are voted up or down. Images that are approved ("promoted") are perforce potential main page Photos of the Day, so in terms of prominence they are analogous to ITN. (I've been active at FPC for years.)

I would add that the experience of being blocked was a harrowing one for me personally and made a deep impression. – Sca (talk) 19:47, 2 January 2023 (UTC)Reply[reply]

Decline – I'm not prepared to unilaterally lift the block; my suggestion is that you make an appeal at either WT:ITN or WP:AN. – 331dot

  • Beeblebrox, What do you think? 331dot (talk) 16:19, 2 January 2023 (UTC)Reply[reply]
    If I'm being completely honest, Sca's reaction in the immediate aftermath of this block was so clueless and directly irritating to me personally (rapidly archiving discussion here, but persistently trying to appeal the block on my talk page instead) that I don't really want anything to do with reviewing this appeal. Beeblebrox 17:44, 2 January 2023 (UTC)Reply[reply]
    That was a technical/procedural mistake on my part. -- Sca (talk) 19:15, 2 January 2023 (UTC)Reply[reply]

Sca (talk) 19:47, 2 January 2023 (UTC)Reply[reply]

  • I won't either accept or decline this myself as I'm aware I'm potentially biased, but I feel it's worth noting that Sca's constant obnoxiousness is the primary reason I stopped engaging with discussions regarding ITN/C, and I'm sure I can't be alone in that. If Sca's continued absence makes ITN/C a better-functioning process (and I find it hard to believe it doesn't) then I'd be inclined to leave the topic ban in place—we currently have 57,232,304 other pages on Wikipedia to which the topic ban doesn't apply, so it's not as if it's causing a massive hardship. ‑ Iridescent 19:53, 2 January 2023 (UTC)Reply[reply]
  • "Inappropriate joke"? More precisely it was a racist joke, wasn't it? At first I thought I might be biased as I hail from South Korea, so I kept quiet. But now I realize I probably wasn't. BorgQueen (talk) 19:58, 2 January 2023 (UTC)Reply[reply]
    Yes, it was a racist joke. Sorry, Sca, it doesn't mean anyone is saying you're a racist, but my immediate association, too, was that of putting on a racist and clichéd accent. I watch TV shows (outside the English speaking world) where to this day white people additionally try to make their eyes look like they have an epicanthic fold, in addition to such linguoracist jokes. If you were actually thinking of an archaic usage of 'erected' (or to be fair, simply creating a possibly figurative one), then that only shows that shooting jokes from the hip (e.g. in what are supposed to be somewhat serious discussions on which events to feature on ITN) can totally misfire. Personally, I'd allow you to return to ITN, provided you stop making jokes, as they don't appear to be your forte. --Sluzzelin talk 20:24, 2 January 2023 (UTC)Reply[reply]
  • To save everyone else here the scavenger hunt, here is the comment/joke in question (despite my signature I'm a white American, so I have no personal stake in this). The Blade of the Northern Lights (話して下さい) 22:45, 2 January 2023 (UTC)Reply[reply]