Wikipedia:Administrators' noticeboard

Source: Wikipedia, the free encyclopedia.

This is an old revision of this page, as edited by Deepfriedokra (talk | contribs) at 03:26, 11 June 2020 (→‎Unblock request review for AlexanderHovanec: will close as there is no consensus to unblock after one week.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

    Welcome – post issues of interest to administrators.

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

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

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

    Template:Active editnotice

    Open tasks

    XFD backlog
    V Apr May Jun Jul Total
    CfD 0 0 12 5 17
    TfD 0 0 5 5 10
    MfD 0 0 0 0 0
    FfD 0 0 1 1 2
    RfD 0 0 4 0 4
    AfD 0 0 0 0 0

    Pages recently put under extended-confirmed protection

    Report
    Pages recently put under extended confirmed protection (35 out of 7998 total) (Purge)
    Page Protected Expiry Type Summary Admin
    User:Naveed Hussain Taj 2024-07-11 14:54 2024-07-12 14:54 create Repeatedly recreated BusterD
    Draft:Saeed Khan Bozdar 2024-07-11 12:19 indefinite create Repeatedly recreated Amortias
    Zionism 2024-07-11 04:39 indefinite move Edit warring / content dispute: Time to stop editing the article and discuss on the talk page. Just noting that I've made this indef to prevent the article auotmatically becoming unprotected and it's a normal admin action so any admin can change it back to ECP. Callanecc
    China–Israel relations 2024-07-11 00:14 indefinite edit,move Contentious topics enforcement for WP:CT/A-I; requested at WP:RfPP Daniel Quinlan
    1st Tank Brigade (Ukraine) 2024-07-10 22:05 indefinite edit,move Community sanctions enforcement: per RFPP and WP:RUSUKR Daniel Case
    Death of Nex Benedict 2024-07-10 19:31 indefinite edit,move Contentious topics enforcement for WP:CT/GG; requested at WP:RfPP Daniel Quinlan
    Module:WritingCredits 2024-07-10 18:00 indefinite edit,move High-risk template or module: 3656 transclusions (more info) MusikBot II
    Template:Non-album single 2024-07-10 18:00 indefinite edit,move High-risk template or module: 2503 transclusions (more info) MusikBot II
    Template:Film lists by country 2024-07-10 18:00 indefinite edit High-risk template or module: 2789 transclusions (more info) MusikBot II
    Template:Fa bottom 2024-07-10 18:00 indefinite edit,move High-risk template or module: 2503 transclusions (more info) MusikBot II
    Al-Awda School massacre 2024-07-10 17:47 indefinite edit,move Arbitration enforcement Pppery
    Russian annexation of Donetsk, Kherson, Luhansk and Zaporizhzhia oblasts 2024-07-10 16:44 indefinite edit Move warring Robertsky
    Channel 14 (Israel) 2024-07-10 15:09 indefinite edit,move Arbitration enforcement; requested at WP:RfPP CambridgeBayWeather
    June 2024 northern Gaza City airstrikes 2024-07-10 14:52 indefinite edit,move Arbitration enforcement CambridgeBayWeather
    9 July 2024 Gaza attacks 2024-07-10 14:49 indefinite edit,move Arbitration enforcement CambridgeBayWeather
    Tim Sheehy (American politician) 2024-07-09 23:36 indefinite edit,move Per AFD discussion Liz
    Mostafa Momeni 2024-07-09 22:40 indefinite move See Special:Permalink/1233594577#Administrator needed. Robertsky
    Mostafa Momeni (geographer) 2024-07-09 22:38 indefinite move Robertsky
    First Balkan War 2024-07-09 21:39 indefinite edit,move Contentious topics enforcement for WP:CT/EE; requested at WP:RfPP Daniel Quinlan
    Operation Azm-e-Istehkam 2024-07-09 17:35 indefinite edit,move Arbitration enforcement CambridgeBayWeather
    Talk:Wikilink 2024-07-09 16:58 indefinite create Repeatedly recreated SuperMarioMan
    Talk:WBD 2024-07-09 03:35 2024-07-12 03:35 edit,move Apparent (i.e., fairly obvious) IP sock puppetry BD2412
    8 July 2024 Ukraine missile strikes 2024-07-09 02:40 indefinite edit,move Community sanctions enforcement: WP:RUSUKR Johnuniq
    3rd Assault Brigade 2024-07-08 23:45 indefinite edit,move Community sanctions enforcement: per RFPP and WP:RUSUKR Daniel Case
    Robert Ford (outlaw) 2024-07-08 19:40 2024-07-22 19:40 edit,move Persistent disruptive editing from (auto)confirmed accounts CambridgeBayWeather
    128th Mountain Assault Brigade (Ukraine) 2024-07-08 07:17 indefinite edit,move Community sanctions enforcement: WP:GS/RUSUKR El C
    47th Mechanized Brigade (Ukraine) 2024-07-08 06:08 indefinite edit,move Community sanctions enforcement: WP:GS/RUSUKR El C
    59th Motorized Brigade (Ukraine) 2024-07-08 06:08 indefinite edit,move Community sanctions enforcement: WP:GS/RUSUKR El C
    Noodle and Bun 2024-07-08 04:22 indefinite create Repeatedly recreated BusterD
    Draft:Noodle and Bun 2024-07-08 04:02 indefinite create Repeatedly recreated BusterD
    Felicia Fox 2024-07-08 03:56 indefinite create Repeatedly recreated BusterD
    China and the Russian invasion of Ukraine 2024-07-08 03:10 indefinite edit,move General sanctions enforcement: WP:RUSUKR.; requested at WP:RfPP: Special:Permalink/1233247791#China and the Russian invasion of Ukraine Red-tailed hawk
    Adnan Hussain 2024-07-08 02:03 2025-07-08 02:03 edit,move Contentious topics enforcement for WP:CT/A-I; requested at WP:RfPP Daniel Quinlan
    Late Ottoman genocides 2024-07-07 22:50 indefinite edit,move Arbitration enforcement WP:GS/AA Rosguill
    July 2020 Armenian–Azerbaijani clashes 2024-07-07 22:49 indefinite edit,move Arbitration enforcement WP:GS/AA Rosguill

    Did SharabSalam call me a "pro-Trump, pro-Saudi troll"?

    Hi, it seems to me that User:SharabSalam might have made a WP:PERSONAL attack against me: diff. Normally, I would not care but because SharabSalam has already been blocked 4 times (and unbclocked twice), and personal attacks were a contributing factor once, perhaps some action is advisable; I want to draw others' attention to it. Also it seems he was to "avoid articles related to slavery" per one of the unblocks but from time to time he edits them: diff (NB he self-reverted this edit, and his other edits related to slavery seem to be reverting obvious vandalism, though I did not delve deep into the history of any slavery-related page). Generally, it makes me think SharabSalam thinks little of the (un)blocks. As for me, even though I found his comment offensive, I do not know what action would be adequate, and if no action is deemed necessary, I am OK with it. (Also not sure if another/longer block would improve his behavior...) I suppose he makes useful contributions but I am just not sure other editors need to put up with this kind of behavior as Wikipedia is not only about content. Thanks, WikiHannibal (talk) 17:58, 1 June 2020 (UTC)[reply]

    SharabSalam has a tendency to attack-by-implication and then later apologize, so multiple violations are forgiven, until the next round, at least. I, for one, am getting a bit tired of seeing him as either the OP or the subject of multiple admin noticeboard reports. El_C 18:10, 1 June 2020 (UTC)[reply]
    Did you check what this report is about?...--SharʿabSalam▼ (talk) 18:51, 1 June 2020 (UTC)[reply]
    I did, and I reverted your attack, to boot [1]. Anyway, so not even an apology this time? I'm sorry but that does not inspire confidence. El_C 19:05, 1 June 2020 (UTC)[reply]
    WikiHannibal, where did I call you a Saudi troll? I said the source [2] says that "sympathizer of Muslim brotherhood" is used by pro-Saudi and Trump bots. Also, I was not banned from slavery articles. I said I will avoid them for 6 months which I did and that was last year.--SharʿabSalam▼ (talk) 18:48, 1 June 2020 (UTC)[reply]
    It looks like in the first dif they gave where you said oh wait that's the same language that pro-Trump, pro-Saudi trolls use per [3]. How coincidental! PackMecEng (talk) 18:51, 1 June 2020 (UTC)[reply]
    And where does that says that he is a Saudi troll?--SharʿabSalam▼ (talk) 18:56, 1 June 2020 (UTC)[reply]
    I think it was the "how coincidental" part. PackMecEng (talk) 18:57, 1 June 2020 (UTC)[reply]
    No that doesnt say that. I was saying that there is no source available that says Jamal was a "Muslim brotherhood sympathizer" except according to the report, from Saudi bots, and that it was a coincidental that it was the same edit that was added by WikiHannibal.--SharʿabSalam▼ (talk) 19:01, 1 June 2020 (UTC)[reply]
    SharabSalam, that is not at all what you said, and I for one am rapidly running out of WP:AGF here. You compared WikiHannibal's edits to pro-Trump and pro-Saudi trolls, then adding "how coincidental" in a sarcastic manner in order to imply that WikiHannibal is, in fact, such a troll. creffett (talk) 19:04, 1 June 2020 (UTC)[reply]
    No, I wasnt implying that. I was implying that WikiHannibal got that from Saudi bots. Something is so innocent and I really didnt mean any personal attack against him.--SharʿabSalam▼ (talk) 19:09, 1 June 2020 (UTC)[reply]
    SharabSalam, I have to agree with El_C here. Considering that you were just at AN/I a month ago for personal attacks, and you've gotten plenty of warnings regarding your interactions with other editors, I have a question: why shouldn't you get a temporary block for personal attacks? creffett (talk) 18:50, 1 June 2020 (UTC)[reply]
    Creffett, when did I make a personal attack here? I never made any personal attack. All I said is that "sympathizer of Muslim brotherhood" is used by Saudi trolls "[4]" You cant block me when I havent made any personal attack.--SharʿabSalam▼ (talk) 18:56, 1 June 2020 (UTC)[reply]
    How dumb do you think we are?--Jorm (talk) 19:01, 1 June 2020 (UTC)[reply]
    Is that a trick question? PackMecEng (talk) 19:02, 1 June 2020 (UTC)[reply]

    I don't think "Saudi Barbaria" belongs on Saudi-related articles. —DIYeditor (talk) 19:04, 1 June 2020 (UTC)[reply]

    Oh yea. Now all the people who I had dispute with are going to gather in this thread. I have said that in the context of their press freedom in WP:RSN thread. Their regime is barbaric and there is no freedom of press, therefore all of their sources should be considered state-owned sources.--SharʿabSalam▼ (talk) 19:07, 1 June 2020 (UTC)[reply]
    I'm not taking issue with you calling it a barbaric regime. I'm taking issue with you wanting to edit controversial articles related to that regime when you feel the need to make characterizations like that. —DIYeditor (talk) 19:15, 1 June 2020 (UTC)[reply]
    It is a fact that the Saudi regime is a barbaric regime. It is not not just my feeling. Its the consensus of acadmic scholars who are expert on the subject.--SharʿabSalam▼ (talk) 19:21, 1 June 2020 (UTC)[reply]

    @SharabSalam:(perplexed frown) For someone who does not mean to make personal attacks, you certainly seem to make a lot of them. Perhaps you could better consider your remarks? Saudi ‘’Barbaria’’? You seem to have difficulties editing in a neutral manner about this subject. Perhaps things would be calmer with a TBAN on such a subject? --Deep fried okra User talk:Deepfriedokra 19:41, 1 June 2020 (UTC)[reply]

    Question @SharabSalam: Do you still think that "Israeli sites are mostly unreliable" as you said here [5]? --Shrike (talk) 18:14, 2 June 2020 (UTC)[reply]

    Shrike, in I/P area? Yes.--SharʿabSalam▼ (talk) 18:16, 2 June 2020 (UTC)[reply]

    I think that person that think "Israeli sites are mostly unreliable" and affirms it[6] shouldn't edit IMO about ARBPIA conflict as he can't edit in neutral way but I like to hear more opinions about this matter --Shrike (talk) 18:20, 2 June 2020 (UTC)[reply]

    Shrike, that’s probably better for WP:AE than here. Different discussions, imo. TonyBallioni (talk) 18:24, 2 June 2020 (UTC)[reply]
    To me it seems its just one of symptoms of same problem.The user cannot neurally edit about political issues and contemporary conflicts --Shrike (talk) 18:31, 2 June 2020 (UTC)[reply]

    Note - This user got renamed, possibly courtesy vanishing. Interstellarity (talk) 13:05, 3 June 2020 (UTC)[reply]

    Congrats, everyone. What a bloody shame. starship.paint (talk) 01:38, 4 June 2020 (UTC)[reply]

    Proposed topic ban from Saudi Arabia

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


    I think a topic ban from Saudi Arabia is in order. This has been ongoing for more than a year on multiple projects. See this diff from meta where he effectively accused Alaa and other non-Saudi editors from ar.wiki who he was in a dispute with of being agents of the Saudi government when several of the editors who he is discussing have known RL identities and they are most certainly not Saudi. I see his finding of pro-Saudi internet trolls around every corner also continues on en.wiki. Therefore, I'm proposing the following:

    SharabSalam is topic banned from Saudi Arabia, broadly construed.
    • Support as proposer. This has been going on in multiple projects for over a year. The English Wikipedia is not the place for a continued dislike of ar.wiki and conspiracy theories and personal attacks on editors for being Saudi-sympathizers and/or agents. TonyBallioni (talk) 19:43, 1 June 2020 (UTC)[reply]
      Tony - is this his first t-ban? I'm not seeing a time frame - maybe 3 or 6 mos if his first? Atsme Talk 📧 00:06, 2 June 2020 (UTC)[reply]
      @Atsme: It is not his first T-Ban. At the moment, SharabSalam is T-Banned from post-1978 Iranian politics as a result of this discussion. –MJLTalk 03:31, 2 June 2020 (UTC)[reply]
      I have not called anyone a Saudi agent. Read my comment. I said there are Saudi agents in that Wikipedia. Which is possible since they have agents in Twitter who were spying on Americans [7].--SharʿabSalam▼ (talk) 19:49, 1 June 2020 (UTC)[reply]
      You're not helping. This is part of the trend above, you make broad statements with obvious implications. In that thread you'd accused باسم of intentionally undoing every edit you make after you called out people for supporting "Saudi [Barbaria"], the implication being he was one of them. He's also publicly identified as Lebanese, not Saudi. Another example: you made this reply denying accusing anyone, while saying there were agents on ar.wiki and that people only came after they were notified. The implication in clear.
      Anyway, that's all meta, not en.wiki, but it shows you have the habit of making ridiculous insinuations: neither Ala'a or باسم are Saudi, and both are well-respected cross-wiki. They're not trying to drive a Saudi agenda. While that's another project, it's relevant here because it shows that you see pro-Saudi editors on three Wikimedia projects, even when it's pretty obvious the people you are discussing don't have a bias towards the Saudis. They just don't hate them as much as you. You were welcome to edit Saudi topics on en.wiki so long as you followed our guidelines. It seems you can't follow our behavioural guidelines here, just like you couldn't follow the behavioural guidelines on other projects in this topic area. We have a tool to deal with that here. TonyBallioni (talk) 20:03, 1 June 2020 (UTC)[reply]
      They just don't hate them as much as you. OMG, I hate Saudis?
      Can anyone stop this?? This admin has completely manipulated what I said. I have never said I hate Saudis. That's such an extremely offensive thing to say to me. I said that there are Saudi agents in Arabic Wikipedia. I never said someone is a Saudi agent. For the reverts, you can see here that I and other editors got reverted by باسم without any reason. Yes, literally no reason for the reverts. They dont say why they reverted you. Your manipulation of what I said is completely offensive to me. If you want to block me, block me but dont accuse me that I hate Saudis. I dont and I dont hate Saudis.--SharʿabSalam▼ (talk) 20:33, 1 June 2020 (UTC)[reply]
      Apologies. I was using standard English shorthand for: They just don't have as universally negative views on things involving Saudi Arabia as you do. No one is saying that the Saudi regime is the model of human rights. What we are saying is that you have a history on multiple Wikimedia projects of not being able to act within our behavioural norms on this subject area. TonyBallioni (talk) 20:43, 1 June 2020 (UTC)[reply]
      I do have a negative view of the Saudi regime, not "on things involving Saudi Arabia". Most Yemenis do have a negative view of the Saudi regime. However, I have never made any disruptive, POV edit in Saudi Arabia-related articles. I have always remained neutral in these topics. I have said the word "Saudi Barbaria" once on Wikipedia, and I was talking in the reliable sources noticeboard about the Saudi regime press freedom. They kill journalists as we saw in the Jamal case. My point was that Saudi-based sources are as bad as Saudi-owned sources because of there is no freedom of press. And that was the whole point of what I said.--SharʿabSalam▼ (talk) 20:54, 1 June 2020 (UTC)[reply]
    • Reluctant support even though I suggested it. I can't see how anyone who calls Saudi Arabia Saudi Barbaria can approach the subject objectivvely. Tony makes some good points. --Deep fried okra User talk:Deepfriedokra 20:10, 1 June 2020 (UTC)'[reply]
      Note: I oppose an on Islam TBAN. --Deep fried okra User talk:Deepfriedokra
      I have literally used that word once on Wikipedia and it was in the context of their press freedom in WP:RSN and not in the article. Barbaric means cruel. The Saudi regime is a cruel regime in the context of their press freedom. And I was making a point, Saudi-based sources are not free even if they are not owned by the government, therefore, they are not reliable in some cases.--SharʿabSalam▼ (talk) 20:33, 1 June 2020 (UTC)[reply]
    • Neutral on the proposed tban on Saudi Arabia, but strongly opposed to a much broader tban covering Islam-related articles, as is being proposed below. A ban on editing anything related to a major religion is a very strong action. If an editor had a tendency to remove content critical of the Catholic Church, claiming it to be poorly sourced, we would not rush to tban such an editor from all Catholicism-related articles. I've tangled with such editors, especially on matters relating to abortion, but I've always been able to rely on consensus of other editors on those content issues and have never believed that those Catholic editors needed to be banned. As a non-Catholic, I believe that Wikipedia should not take punitive action against those Catholic editors (unless an extreme case occurred); and as a non-Muslim, I also believe that Wikipedia should not ban from Islam-related articles an editor who on occasion has objected to what they perceive as anti-Islam content, even if their objections to it sometimes were not well-grounded. Religious tolerance and even-handedness are important here. NightHeron (talk) 23:29, 1 June 2020 (UTC)[reply]
    • Support per TonyBallioni and El_C above for consistent POV editing and personal attacks. Also, per Debresser below, I believe we should stronger consider a broader topic ban covering Islamic subjects in general. YUEdits (talk) 02:26, 2 June 2020 (UTC)[reply]
      Note: YUEdits has made fewer than 500 contributions to Wikipedia, dating to 2017, and this is their first ever post to any administrator noticeboard. They've only edited 1 article talk page and 1 other noticeboard. Interesting, I would say. starship.paint (talk) 04:08, 4 June 2020 (UTC)[reply]
    • Support I am in agreement that this topic ban is not as broad as we probably need here. I would be also fine with "topic ban from anything related to Muslims". Orientls (talk) 03:51, 2 June 2020 (UTC)[reply]
    • Note: I oppose an Islam TBAN. The argument below is that he removed anti-Muslim content sourced to unreliable sources. Are we really going to sanction an Arab editor for removing anti-Muslim speech in a way that doesn’t violate any policy or attack any editor? If I did that I’d be given a barnstar. I think SharabSalam sees Saudi spies around every corner and needs a sanction because of that, but being paranoid about the Saudi government and calling others Saudi trolls, etc. is what’s disruptive. Removing an anti-Muslim hate blog is laudatory. TonyBallioni (talk) 04:08, 2 June 2020 (UTC)[reply]
      • He makes hundreds of edits so that is not really surprising, but also see other edits mentioned in the section below. What one should also see is that the existing topic ban on him from Iranian politics (1978 - present) emerged on ANI and this subject involves Islamic politics. Now we are discussing the Saudi Arabia related editing issues which again involves a Islamic country. I don't see how country-specific bans are really going to work anymore, thus it is better to make a broader topic ban. Orientls (talk) 05:25, 2 June 2020 (UTC)[reply]
        • I wouldn’t object to a broader Middle East topic ban, but I’d pretty strongly oppose an Islam one. Like I said, he accused a Lebanese CU of being a pro-Saudi POV pusher and basically said the only Arab steward was a Saudi spy for opposing a local dialect wiki (full disclosure: علاء is probably my closest friend on Wikimedia so I’m still angry about that.) Now he’s doing the same crap on en.wiki that he was doing on meta and ar.wiki: the thing is, removing religionofpeace and synthesis/original research of primary sources from religion articles is almost always a good thing. TonyBallioni (talk) 05:40, 2 June 2020 (UTC)[reply]
          • I have never accused anyone of being a Saudi spy. Also, I have being completely neutral while editing ME articles. I have expanded geographicall articles about Yemen.[8] I have always being helpful in that area. I dont think this is because of the meta wikimedia thing. I think this is because I supported a standard section header in AN/I. I have noticed that since then you started attacking me. It is also clear that you want to become a steward.--SharʿabSalam▼ (talk) 05:54, 2 June 2020 (UTC)[reply]
            • You realize I’m trying to prevent you from being unjustly sanctioned for removing anti-Muslim hate speech, right? As for your attacks on me: I turn down people asking me to run for steward every year because it doesn’t interest me. The odds of my running for steward are approximately zero, and are also not relevant to this discussion. And no, I’m not mad about you supporting standardized section headers. I’ve admitted I’m not particularly happy with you over your attacks on Ala’a, and that’s a bias, but you’re doing the exact same thing on this project, and since I know the history on meta and ar.wiki that is relevant, and others don’t, I’m going to raise it. I have said that I think your actions on this project have become increasingly a net negative over time, and because I am active cross-wiki and am very familiar with ar.wiki and meta, I know your history on those projects, which is applicable here since you’ve shown the same behaviour on multiple projects, and it’s been disruptive on all of them. TonyBallioni (talk) 06:05, 2 June 2020 (UTC)[reply]
              WTF are you even talking about? I have never attacked Alaa. You have got to be kidding me. Are you instigating Arab users against me?. That issue happened between me and the whole Arabic Wikipedia system. I have been so nice with Alaa. See my talk page in Arabic Wikipedia!. I have only objected the way they revert edits, all of them. They don't write edit summaries. I don't think you know Arabic Wikipedia. I have never had any issue with you. It all started when I supported a proposal to have a standard AN/I. Before that you were so nice with me. Even in meta Wikimedia.[9] I have been blocked in Arabic Wikipedia because of the username only, nothing about my contributions. I wasn't able to speak English very well when I joined English Wikipedia but I just joined because every edit I make in Arabic Wikipedia is being reverted. Most articles in Arabic Wikipedia don't make any sense, because they are clearly translations and when someone tries to fix that he gets reverted. Months ago, someone emailed me telling me to make a complaint in meta Wikipedia and to provide evidence. I didn't want to do that but now I will, when I have time, make a complaint and provide tons of evidences of non-free Arabic Wikipedia. In any case, you dont seem to be neutral. You have said many mean things to me like saying that other editors dont hate Saudis like I do "They just don't hate them as much as you" and that I am "being paranoid about the Saudi government ". Do think saying someone has a mental health is not offensive? Do you think saying that I hate Saudis is not offensive?. I told you before, if you want to block me, block me, but dont say these mean stuff to me.--SharʿabSalam▼ (talk) 06:32, 2 June 2020 (UTC)[reply]
    • Support: Unfortunately, the editor’s strong personal view about the country appears to be impairing their ability to cooperatively and civilly edit in the area. — MarkH21talk 05:59, 2 June 2020 (UTC)[reply]
    • Neutral on Saudi Arabia TBAN per discussion with SlimVirgin below; oppose Middle East TBAN per comments by MJL below; oppose a ban on Islam or Muslim topics per my original rationale. 03:16, 3 June 2020 (UTC) Support Saudi Arabia TBAN per the problems here. Weak support for Middle East TBAN given the pattern with Iranian politics. Strong oppose to a ban on Islam or Muslim topics as way too broad. Wug·a·po·des 06:17, 2 June 2020 (UTC) edited 03:16, 3 June 2020 (UTC)[reply]
    • Support topic ban from the subject of Saudi Arabia. Partly after reading this here, and partly after reading the recent discussion on SharabSalam's talk page with TonyBallioni, I have to conclude that SharabSalam does not appear to be open to considering how he is coming across or to listening when other people try to explain it. The clearest example is right here, in that "oh wait that's the same language that pro-Trump, pro-Saudi trolls use ... How coincidental!" comment. Even if that wasn't intended as a personal attack likening an editor to a pro-Trump, pro-Saudi troll, it's undoubtedly how it comes across. And I see a steadfast refusal to even consider that. In fact, had I seen that comment before the discussion here commenced, I would have blocked for it. My fear is that SharabSalam is heading for an eventual exclusion from this project, which would be unfortunate, and I hope a topic ban here might act as a wake up call and prevent that happening. Boing! said Zebedee (talk) 11:11, 2 June 2020 (UTC)[reply]
    • Support as I said at the ANI thread back then, SharabSalam is emotionally invested in the topics they edit on: first Iranian politics, now Saudi Arabia? I have a gut feeling that we're going to end up looking at a t-ban from the entire Middle East. But, per WP:ROPE, this, for the time being. ——Serial # 17:11, 2 June 2020 (UTC)[reply]
    • Support Saudi Arabia TBAN, alternatively support Middle East TBAN (or should that be MENA to make the WMF happy?), oppose Islam TBAN. Echoing SN54129 and Boing!, I'm not filled with confidence that even an ME topic ban will be enough of a wakeup call given that they didn't seem to get the message after the IRANPOL TBAN, but ROPE and all that. I also would like to express my disappointment that SharabSalam has been told by multiple editors how their "pro-Saudi trolls" line sounds and yet hasn't even retracted the comment. creffett (talk) 18:49, 2 June 2020 (UTC)[reply]
      How to redact that comment when it is already removed. I didnt intent to call any editor Saudi troll. I said that the content that was added was promoted by Saudi bots according to reliable sources. If I knew that I would have been understood that way, I wouldnt have said it.--SharʿabSalam▼ (talk) 19:04, 2 June 2020 (UTC)[reply]
    • Support The proposed ban and the ban from Middle East as per this comment [[10] --Shrike (talk) 20:15, 2 June 2020 (UTC)[reply]
    • Oppose. Can someone post examples of the problematic edits or comments about Saudi Arabia on enwiki? So far, the only one offered is "oh wait that's the same language that pro-Trump, pro-Saudi trolls use ... How coincidental!" in response to a proposed poorly sourced edit that arguably undermined Jamal Kashoggi, the Saudi dissident who was assassinated. SarahSV (talk) 22:11, 2 June 2020 (UTC)[reply]
      • It seems that SharabSalam has retired. Looking briefly through his edits, it seems he's an Arab editor with excellent English who understands the sourcing policies, including a good understanding of OR/SYN and the misuse of primary sources. In case I'm wrong about that, or in case it's an incomplete picture, can someone please post some of his problematic edits or comments about Saudi Arabia? SarahSV (talk) 22:36, 2 June 2020 (UTC)[reply]
        • @SlimVirgin: On its own I would agree with you. For me, the context I would want you to consider is that this seems to be continuation of the behavior that led to the ban from post-1978 Iranian politics. While those accusations were more direct than the incident you mention, the oblique accusation, Tony's diff from meta (among others), the Saudi Barbaria comment at RSN, and the Iran TBAN collectively make me think that the editor has issues assuming good faith or behaving civilly (i.e., not rude) in this topic area, and that what they learned from the post-1978 Iran TBAN was to make accusations by implication rather than directly. Wug·a·po·des 00:47, 3 June 2020 (UTC)[reply]
    • Comment. I don't want to fully weigh in here, but I have to say that idea we would TBAN SharabSalam for that "Saudi Barbaria" comment would be pantently absurd. (1) The dude is not a native English language speaker and probably has no clue the deeper implications behind call a place barbaric. He didn't even know what "whiny *****" meant.link (2) He lives in Yemen. You guys know there is an active civil war there, right? It's just a wee bit tense there.. (3) Saudi Arabia has done some pretty awful things, so let's not pretend that a user biased against them is all that surprising.
      If people want to support this TBAN for the reasons Tony outlined, that's one thing. To TBAN for that one single comment from five months ago, that's pretty absurd.
      I'd also completely oppose a ban on the broad topic of the Middle East. That's like TBANing an English person from the entire topic of Western Europe. That's greatly disproportional to anything I have seen be alleged SharabSalam to have done. –MJLTalk 02:43, 3 June 2020 (UTC)[reply]
      If people want to support this TBAN for the reasons Tony outlined, that's one thing. - I've read through Tony's link for meta.wiki and I have a different interpretation. I do not think SharabSalam was targeting Tony's acquaintances, I think it was a general comment. If you combine every allegation SharabSalam made as if they all referred to the same people, yes, it would look bad. But I do not think one is obliged to combine all the allegations. It is one way to look at it, but it is not the only way. starship.paint (talk) 14:42, 3 June 2020 (UTC)[reply]
      To be honest, I thought along very similar lines. I just figured I must've been missing some context or something. –MJLTalk 21:31, 3 June 2020 (UTC)[reply]
    • Comment Given Saudi Arabia’s influence in the region, is it even feasible to devise a TBAN from Saudi Arabia but not from the Middle East? P-K3 (talk) 11:39, 3 June 2020 (UTC)[reply]
      The behavior here is very concerning because I don't believe people don't quite understand the implications of what they're saying, and what it could mean or the consequences it could bring to people who live in different countries from the US or UK, especially where religion and customs are held in the highest regard. Please measure your words carefully. Atsme Talk 📧 21:55, 3 June 2020 (UTC)[reply]
      @Pawnkingthree: Considering we have a general sanction regime in place for Iran.. well there you go. –MJLTalk 23:16, 3 June 2020 (UTC)[reply]
    • The behavior clearly justifies the proposed TBan. Beyond My Ken (talk) 22:52, 3 June 2020 (UTC)[reply]
    • Oppose per SarahSV and MJL. Furthermore, I have stated above, I do not believe the meta.wiki comment was targeted at anyone in particular (of that discussion). Let's also remember that this dispute started with the OP labeling Jamal Khashoggi as a Muslim Brotherhood "sympathizer". What we should be doing, if SharabSalam ever returns, is to have them clearly state the targets of their criticism every time. starship.paint (talk) 08:28, 4 June 2020 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Vanishing

    My subsequent follow-up comment was lost in an edit conflict. While I realize this is a courtesy vanishing, it’s a highly irregular one, given the ongoing conversation, and that it was requested from a WMF steward. I’d prefer Sotiale justify why they did so. Symmachus Auxiliarus (talk) 01:53, 4 June 2020 (UTC)[reply]
    Global renames are often requested in private. Sotiale does not need to "justify" anything. ST47 (talk) 02:09, 4 June 2020 (UTC)[reply]
    ST47, for the record, I don’t have an issue with user vanishing. But as I understand it, these sorts of things are not to be done with a user’s conduct being discussed on a noticeboard. My issue here is with a WMF steward acting out of process. Symmachus Auxiliarus (talk) 02:14, 4 June 2020 (UTC)[reply]
    Look, Sotiale is Korean and doesn’t really edit this project. He had no reason to know that this was in the middle of a sanctions discussion or that the user was already under sanctions. The simple solution is to reverse the vanishing, because you are correct, he isn’t entitled to one while under sanctions or being discussed at a noticeboard. It’s not big deal. These things happen on a global website. TonyBallioni (talk) 02:43, 4 June 2020 (UTC)[reply]
    Let me tell you something: English Wikipedia is not the center of Wikimedia-sphere and we (S and GRNs) do not need to check for every project/every contribs every time to check stuff before acting on something. Vanish runs on honor systems: we assume good faith and act on bad faiths if found. — regards, Revi 03:01, 4 June 2020 (UTC)[reply]
    I would expect a Steward to be familiar with policy and understanding that they may not be the best individual to process certain items at times. We have a plethora of renamers, especially ones whose home wiki is enwiki. There is hardly ever an instance where renames need to be processed immediately. I will be reversing the rename soon, unless anyone can think of a reason not to. Nihlus 03:04, 4 June 2020 (UTC)[reply]
    Yes, I think if you reverse the rename that would be good and would also be the end of the discussion on it. TonyBallioni (talk) 03:06, 4 June 2020 (UTC)[reply]
    I'm sorry, I know this is a tangent, but I'm confused; how is User:Nihlus going to undo the rename? They aren't a steward or a global renamer. Tony's reply makes me think they can, and I'm missing something. --Floquenbeam (talk) 03:11, 4 June 2020 (UTC)[reply]
    Why would anyone want to reverse his vanishing? He wants to leave. Let him go. SarahSV (talk) 03:14, 4 June 2020 (UTC)[reply]
    SlimVirgin, it is against global policy to rename someone who is embroiled in controversy and who may be using the rename to obfuscate their conduct. Floquenbeam, I am a global renamer and have been for sometime now. Anyway, the rename has been reversed. Nihlus 03:19, 4 June 2020 (UTC)[reply]
    Ah yes, let us not only make English Wikipedia more myopic and parochial, but let's do it in the most tortuous way possible. Forgive me for actually reading WP:VANISH, but there it says: "Vanishing is not a way to avoid criticism, sanctions, or other negative attention, unless you really mean to leave permanently. As such, it might not be extended to users who have been disruptive, who leave when they lose the trust of the community, or when they are blocked or banned." That unless clause (combined with the 'might not' in the following sentence) tells me this is something you chose to do. That's fine. I am entitled to think you're a bad person for doing so. Dumuzid (talk) 03:22, 4 June 2020 (UTC)[reply]
    He isn't "embroiled in controversy". WP:VANISH is poorly written, but my understanding is: don't do this to wriggle out of trouble temporarily; you do have to intend to leave. SarahSV (talk) 03:31, 4 June 2020 (UTC)[reply]

    The reason for the norm to be declining a vanishing in the middle of a sanctions discussion is that people who vanish in the middle of sanctions discussions usually aren't actually vanishing. They're usually trying to set up for an invalid clean start and will be back. Because of that, the vanishing policy both locally and on meta is traditionally read similar to the en.wiki WP:CLEANSTART policy since despite the wording saying vanishing is not a clean start, they tend to be linked in practice.

    It keeps things cleaner if you wait until after it is over, and easier to figure out who is under sanctions and who isn't if they do come back in another incarnation. Basically, I do agree with reversing this, but I think we could have better explained the reasoning behind it besides global policy says so. I think there's a good reason for that norm, but its not intuitive if you don't work in the area.

    Basically, my understanding of VANISH is that if you wouldn't otherwise be eligible to clean start, you shouldn't be vanished. There is of course wiggle room and grey areas, but I don't think they really apply here since it isn't a real name account or one with privacy concerns. TonyBallioni (talk) 03:35, 4 June 2020 (UTC)[reply]

    Addendum: m:Global rename policy is a bit clearer on this saying that in seeking a rename The user is not seeking the rename to conceal or obfuscate bad conduct. which is another reason turning down requests during sanctions discussions has become more of a normal way of handling it. TonyBallioni (talk) 03:40, 4 June 2020 (UTC)[reply]
    TonyBallioni, so renaming and vanishing are now the same procedure? One sort of anticipates further contribution from the editor. One does not, no? Dumuzid (talk) 03:44, 4 June 2020 (UTC)[reply]
    Vanishing is done using the rename function, so normally the global rename policy is applied. Like I said, there's also a sometimes spoken sometimes unspoken assumption that rage quits happen, and are more likely to happen when someone is under stress of being discussed at a noticeboard. Eventually a lot of the people who try to vanish when there's controversy come back. TonyBallioni (talk) 03:49, 4 June 2020 (UTC)[reply]
    • Nihlus, where does meta:Global rename policy say anything that meant this vanishing had to be reversed? SarahSV (talk) 03:41, 4 June 2020 (UTC)[reply]
      (edit conflict × 5) Dumuzid, there is quite a bit in WP:VANISH as well as m:Global rename policy that explains what renaming is not to be used for. The main takeaway though is that the user is a user in good standing and that renaming ... might not be extended to users ... who leave when they lose the trust of the community, or when they are blocked or banned. So yes, this is something that I, in agreement with the original renamer and Tony, chose to do in accordance with policy. I disagree with your need to personally attack me and request that you remove it. Thank you.
      SlimVirgin, the fact that a topic ban is being discussed on AN means a rename would be under controversial circumstances. And this is something that we avoid for obvious reasons, as mentioned in my previous comment. I left more comments on the user's talk page prior to renaming. There is nothing that said it had to be reversed. The original renamer said it was okay to reverse, and two global renamers agreed that it should be reversed. The original request had no mention of privacy concerns, so there wasn't any need to look into it further. Nihlus 03:46, 4 June 2020 (UTC)[reply]
    Nihlus, I am sure you are a wonderful person in your day-to-day life, and probably on Wikipedia as well. I have drawn a conclusion regarding your specific conduct here. Do what you want with that. Cheers. Dumuzid (talk) 03:49, 4 June 2020 (UTC)[reply]
    Nihlus, when this has closed, we should discuss at Wikipedia:Courtesy vanishing how to avoid this kind of situation in future. The local guideline should apply. SarahSV (talk) 05:27, 4 June 2020 (UTC)[reply]
    SlimVirgin, the local policies should and do apply in this situation. If, after this discussion, SharabSalam would like to vanish and is eligible, then I will be happy to process it for him at that time. Nihlus 05:46, 4 June 2020 (UTC)[reply]
    Nihlus, there isn't much point in arguing about it in this thread. According to my reading of WP:VANISH, he is eligible. According to yours, he is not. That means there is a problem with the way the guideline is written, and it would be good to resolve it. SarahSV (talk) 05:56, 4 June 2020 (UTC)[reply]
    • Renamer note As a renamer, I can tell you that SharabSalam is probably "under a cloud" and probably should not have been vanished. --Deep fried okra (schalte ein) 03:46, 4 June 2020 (UTC)[reply]
    • Reversing the rename/vanishing, while defensible by policy, was a mistake. Nothing is gained by keeping someone here who wants to walk away. Newyorkbrad (talk) 03:58, 4 June 2020 (UTC)[reply]
      Then you should change the policy at WP:VANISH, until then it was the correct decision. A bit of nuance would explain that this policy is not about keeping people but letting obviously malicious editors ineligible for courtesy vanishes so they can resume their behaviour with a new account. Requesting vaishing in the middle of a sanction discussion is basically running away from criticism and community sanctions, hence quite clearly VANISH does not apply. --qedk (t c) 06:20, 4 June 2020 (UTC)[reply]
      Yes, except that I don't believe we are dealing here with an "obviously malicious editor." Newyorkbrad (talk) 07:35, 4 June 2020 (UTC)[reply]
      I'm aware yes, but where do you draw the line on "malicious", that's the spirit of the policy and the only way to enforce the spirit is by enforcing the letter. If there was no sanction discussion where proponents supported the sanction, it would be per policy but again, that's not the case here. --qedk (t c) 08:37, 4 June 2020 (UTC)[reply]
      the only way to enforce the spirit is by enforcing the letter What? WP:IAR and WP:5P5 seem to suggest that's not the case. This just sounds like wikilawyering for a reason to punish someone who wants to leave. Also, if anyone who argues too passionately and discourteously for a topic they care about is now "malicious" under your definition, you might want to go see our "malicious" community trustee that just got a TBAN for similar conduct. Wherever the grey line of bad faith editing is, we're clearly very far away from it. Wug·a·po·des 21:02, 4 June 2020 (UTC)[reply]
      It's not a grey line, it's a grey area - if we allowed a repeat evader to vanish would that be okay? What about an editor who has been blocked for a day? What about someone in the middle of an arbitration request where they are a party? If you wish to invoke WP:IAR, so be it, but presenting thousands of alternative cases and not applying policy as it's meant to be is your cross to bear (go for it, it makes no difference to me either way). Not once did I state that SharabShalam is malicious and I don't know why both of you would misconstrue it as so, I am simply stating the intent of why RTV is disallowed in some cases. --qedk (t c) 18:43, 6 June 2020 (UTC)[reply]
      QEDK, here's how I view it. Someone wants to vanish, fine, they get to vanish. As long as they're not some prolific vandal or something (and SharabSalam is not, regardless of whether any of us might agree or disagree with him) then let them go. Once. Whatever shit they may happen to be in at that point. "I choose to walk away" should always be an option.
      If they return with an attempted clean start, then they can declare that, and we can look at it case by case. Guy (help!) 20:15, 6 June 2020 (UTC)[reply]
      @QEDK: It's not that you said they were malicious, but you brought up a point about maliciousness in a case where it supposedly did not apply. If you don't believe Sharab is malicious, why do we need to argue about where the line is? Since Sharab was editing in good faith, if the spirit is avoiding harm from malicious users, then not following the letter better complies with the spirit. My point is and was that focusing on the specific letter of the policy isn't helpful. As Nil Einne explains below, it's not even clear that the wording you point to has particularly broad consensus.
      Despite the page name, I (and perhaps others) view this as a right not a courtesy. The meatball:RightToVanish essay was the basis for our early vanishing policy and--along with Barnstars and Assume Good Faith--the right to vanish represents one of the oldest parts of our community. SarahSV created our RTV policy page in 2007, copying it from meta. Meta's right to vanish was created in 2004 and was spun out from our first privacy policy where it was added by an IP in 2003. People change, communities change, and risks change. Unlike social media accounts or blogs, if we change our mind and want to abandon our connection to the content we've created, Wikipedians cannot simply delete our accounts or content (and people used to do that on wikis: c2:WikiMindWipe). As a matter of privacy and decency, we should afford good faith editors the right to renounce their connection to their contributions through vanishing should they choose to leave our project permanently. If we need to reverse the vanishing later so be it, but either way all the important stuff is kept. We gain nothing from a weak right to vanish but stand to lose a lot without a strong one. Wug·a·po·des 07:50, 10 June 2020 (UTC)[reply]
      I'm with NYB here. I agree this is all within the letter of policy, but I'm saddened that we couldn't just let him go as he apparently wishes. And no, this is someone who has problems with their interactions with others, but I really don't think there's any malicious intent. Oh well. Boing! said Zebedee (talk) 11:02, 4 June 2020 (UTC)[reply]
    • I am very much of the view that the harder we make it for people to leave with dignity, the more we stoke resentment and invite further abuse. If someone wants to leave, let them. Honestly. This is not some vandal we need to keep track of long term abuse. I've had my run-ins with him but this just makes us look spiteful. Sorry, I know that's harsh, but - well, just let the guy leave. Guy (help!) 20:10, 6 June 2020 (UTC)[reply]
      All of you do realize that you can leave anyway right, without executing a RTV? If someone wants to leave, all they need to do is scramble their password. RTV is just so you can be renamed into some gibberish and possibly have a clean start, edit history and talk pages are always preserved anyway, so the fact that a few more things are retained has literally no bearing on a clean start and is mostly extended as a courtesy to editors in good standing (in case of SharabSalam, that's unclear, since they were the subject of a sanction discussion at the time of requesting RTV). Hope that clarifies it. --qedk (t c) 20:32, 6 June 2020 (UTC)[reply]
      @qedk: SharabSalam has had an active sanction against him since before this discussion started (linked above), so there is very little chance of him being an eligible for a clean start (without explicit invocation of WP:IAR or something).
      Regarding the RTV/leaving thing, I'd just let people say what they're going to say. If people want to express their positive opinion of an editor or opine that a certain and specific courtesy should've been shown to them on their way out, then I can't see that doing any harm. At the end of the day, the policy has still been followed. –MJLTalk 02:05, 7 June 2020 (UTC)[reply]
      But people can have strong attachments to their user names, especially if they have been used outside Wikipedia, and often even when they aren't. So even when an account name cannot be easily tied to a real name, demanding that we keep unnecessary connections seems, well unnecessary. Both WP:RTV makes it clear that editors who have engaged in that process cannot undergo a clean start. If they want to return, their vanishing is liable to be reversed or at least their connection to the old account will need to be clearly disclosed and will be considered in any request to return to editing. I think that's fair enough too. And as others have said, when the it's necessary to keep that connection so help us in tracking them e.g. for a known sock, sure it's fair enough that RTV is denied. But I agree with others that it's not clear why it was needed in this case. There seems to be no benefit to us, but there is potential harm to both us and the editor involved. Note that I have no real feelings about the editor either way. I just don't see any reason why we need to keep the unnecessary stuff when there is no apparent need to track them anymore and we already make it clear that if you later decide to return you will need to come back under you original identity so your return can be properly assessed. But until then, if you want to stay away, and you do stay away, then we're not going to keep unnecessary connections. The edit history, AN//I discussions etc will be preserved as they need to be and always will be. The other stuff especially the username in the editor history, we can remove. The most confusing thing to me about this is I'm fairly sure I've seen RTV afforded to editors who are under strong sanction e.g. an indef block, or I think even a community ban or arbcom ban afforded the RTV in the past. Also some where the vanishing does risk causing problems i.e. an editor with a known sock history. And indeed a read Wikipedia talk:Courtesy vanishing/Archive 1 seems to agree with me. Have we gotten a lot stricter recently, or is it just that because this editor decided to RTV when they were under discussion and therefore additional scrutiny, even if it seemed clear that any outcome would be no worse than when we normally allow RTV, they were treated different? P.S. If you check out that page, User:Risker's comments back in 2016 [11] are similar to how I feel now. Nil Einne (talk) 20:34, 9 June 2020 (UTC)[reply]
      @Wugapodes, Nil Einne, and MJL: As I've explained before, it's just how WP:RTV is written, do I have a personal opinion? Not really - because as I said, it's not a big deal. People's attachments to their usernames are also not a big deal, if you wish to execute RTV then that attachment becomes irrelevant. It's equivalent to wanting it both ways, ensuring that things you do aren't tied to your username as well being able to wipe your history (to a limited extent). The way I see it is WP:RTV is a courtesy and if you feel that's not how it should be then you should propose changing it, what's not OK is justifying written policy with arbitrary notions. Should the RTV policy be more lenient? Maybe, whether the community feels that way should be debated in a RfC and not at an AN thread. I'm sure there have been cases where RTV has been done on a indeffed account because someone didn't read through WP:RTV or just straight-up invoked WP:IAR but that's never a suitable reason to subvert policy. What I do agree with is what Wugs' said here, As a matter of privacy and decency, we should afford good faith editors the right to renounce their connection to their contributions through vanishing should they choose to leave our project permanently. And I believe the real question lies in identifying "good" faith and whether sanctioned or under-a-cloud editors apply for the same. So, the real crux of the issue comes down to the letter of the policy and as it stands now, it's not something we can or should resolve unilaterally. --qedk (t c) 08:08, 10 June 2020 (UTC)[reply]
      We're not resolving it unilaterally; we're having a discussion about it because it was dealt with unilaterally when the renaming was reversed. I struggle to find in the text of that policy such a strict interpretation as you seem to understand. As Sarah has discussed above, nothing in the text requires we deny vanishing to those "under a cloud" or even indefinitely blocked users. Consider: Vanishing is not a way to avoid criticism, sanctions, or other negative attention, unless you really mean to leave permanently (emphasis added). From my understanding of what "unless" means, it seems plain that what I and others have said is squarely within the text. Similarly, it might not be extended to users...who leave when they lose the trust of the community... (emphasis added). From my understanding of what "might" means, it does not denote a requirement but rather a description of what could happen. The meta policy is arguably less restrictive. Saying that we need to propose a change is nonsense; we've advocated an interpretation that is squarely within the literal meaning of current policy text and given historical evidence for the spirit of the policy which led to the development of the current text. Wug·a·po·des 19:49, 10 June 2020 (UTC)[reply]

    Censoring

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


    I just had a closer look at this editor, who recently tagged my talkpage with a warning template, and found that on many occasions he has removed negative information about Islam on grounds that seem trumped up to me (excuse the pun). Claiming primary source, unreliable source or original research he removed large paragraphs in edits like [12][13][14][15][16][17][18]. Primary sources is not in itself a reason to remove information, and frankly these claims seem trumped up in order to allow this editor to remove information which he feels is compromising for Islam. By the way, please notice that I am not claiming to have researched the reliability of each and every source and the sourcing of each and every claim he has removed. I am however seeing the bigger picture here, and it looks very suspicious. Since this is a long-term problem, and one that is much harder to recognize than a personal attack, I don't know what should be done, although I for myself have reached the conclusion that this editor should be banned from all Islam-related articles or simply blocked, since the long-term effects of his edit pattern are very detrimental to the project. Debresser (talk) 20:48, 1 June 2020 (UTC)[reply]

    You have not researched the reliability of these sources? Like did you see thereligionofpeace? Did you also see that these sources are all primary and all the content is original research?. You just reverted me without seeing whether what I said was wrong or not. For the template, you were editwarring and you got warned for editwarring. The admin at the editwarring noticeboard also warned you. As I said, all of those who I had dispute with are going to gather here lol.--SharʿabSalam▼ (talk) 21:02, 1 June 2020 (UTC)[reply]
    As I said, primary sources are not forbidden, and are actually often used in articles about religion. And no, I don't think that this content is all original research. And again, I am more concerned with the pattern that is emerging from these edits than with the fact that one of these edits was sourced to an advocacy group, which, by the way, is specifically not forbidden by the relevant policy. Debresser (talk) 21:05, 1 June 2020 (UTC)[reply]
    But original research is forbidden. You didnt actually look at any of what I said. You, as you said above, assumed that I removed that content because I "feel is compromising for Islam." Thats interesting. Why did you assume that and not look at whether what I said was wrong or not?. You have provided many diffs and I have explained my edits in all of them. If you have a content dispute, we can discuss that in another place. You brought this here, why? You said I am removing content because I "feel is compromising for Islam." Could you provide any evidence? The diffs are all justified. Can you tell me where I was wrong in each of these diffs and why?. I would appreciate if you provided more insight to the problem that you are accusing me of.--SharʿabSalam▼ (talk) 21:17, 1 June 2020 (UTC)[reply]
    And there is a diff to the Ghassanids, how is that relevant to Islam? Could you tell what is wrong with this edit!! that you added in the diffs??--SharʿabSalam▼ (talk) 21:24, 1 June 2020 (UTC)[reply]
    To be fair, I think thereligionofpeace.com is a bogus website. I am not certain of that though, as I don't really want to load such a page to review it. I read about it second hand. —DIYeditor (talk) 21:27, 1 June 2020 (UTC)[reply]
    And by the way, User:Koreangauteng is confirmed sockpuppet of a user who is known for pushing anti-Muslim view and adding original research as you can see the sockpuppet investigation.--SharʿabSalam▼ (talk) 21:33, 1 June 2020 (UTC)[reply]
    Debresser, at least one of those sites is an anti-muslim hate blog. I'd have made the same edits myself. Guy (help!) 23:25, 1 June 2020 (UTC)[reply]
    As I said, I didn't have the time to check each statement and each source. Blogs are of course bad sources, regardless of their POVs, no doubt. It is the ease with which whole paragraphs with a certain type of general content are removed, that triggers my suspicion, and I think this should be looked into. Debresser (talk) 23:42, 1 June 2020 (UTC)[reply]
    All of what I removed was unreliable. You have not explained how any of what I removed should not have been removed. You are accusing me of "censoring" but you have provided no evidence. You said at the top and at the very beginning of your post "who recently tagged my talkpage with a warning template", is this the real problem? Is this why you came here. You were editwarring and you got warned by an Admin. You continued to editwar regardless. Clearly you are treating Wikipedia as a battleground.--SharʿabSalam▼ (talk) 03:41, 2 June 2020 (UTC)[reply]
    • Speaking generally: I don’t see this as relevant to the discussion. Removing anti-Muslim hate blogs and synthesis/original research from religion articles is a good thing. Most religion articles here are filled with it, and an Arab editor removing it is no different than my gutting Catholic articles sourced to early 20th century Protestant polemics: obviously a good thing. If there are specific instances where the sourcing has actually been evaluated, raise it on the article talk page first. TonyBallioni (talk) 06:15, 2 June 2020 (UTC)[reply]
    Okay, now he is edit warring about it.[19] Please notice that he removed primary sources and The Economist, which is in Wikipedia:Reliable_sources/Perennial_sources as a "generally reliable source". His edit summary was "Rv unreliable sources". This is unacceptable as 1. censoring 2. removal of sourced information without consensus 3. edit warring 4. using inaccurate/misleading edit summaries. Debresser (talk) 13:49, 2 June 2020 (UTC)[reply]
    You forget to mention he was also removing religionofpeace. I’d be much more likely to support a sanction against you for restoring an anti-Muslim hate blog than him for removing it. TonyBallioni (talk) 14:02, 2 June 2020 (UTC)[reply]
    It is also unrelated to Abomination (Judaism)--SharʿabSalam▼ (talk) 14:10, 2 June 2020 (UTC)[reply]
    • The fact that you started your post with "who recently tagged my talkpage with a warning template" shows that it is the main reason you came here. It is also not recent, its two months ago, in April. You were editwarring, you got warned. You clearly think this is a battleground.--SharʿabSalam▼ (talk) 14:17, 2 June 2020 (UTC)[reply]
    I simply think you are a problematic editor. Why 2 months would not be recent, and what you see wrong with an unjustified warning on my talkpage being the trigger to investigate your edits, I fail to understand. Debresser (talk) 22:18, 2 June 2020 (UTC)[reply]

    References

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

    Unblock request review for AlexanderHovanec

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


    AlexanderHovanec (talk · contribs · deleted contribs · page moves · block user · block log)

    (User still globally locked, but that's for the stewards on Meta.)

    User has an extensive history of declined unblock requests, socking, resocking, and declined UTRS appeals. Not all of them visible to reviewing eyes. Many of those UTRS appeals are no longer available, making it harder to evaluate. Most recently, I declined UTRS 30529 and responded thusly: :

    I'm sorry, but I cannot unblock you. I am declining your unblock request because it does not address the reason for your block, or because it is inadequate for other reasons. Please describe how your editing was unconstructive and how you would edit constructively if unblocked.

    To be unblocked you must address your edit warring and your use of photos. You must agree to 1RR-- https://en.wikipedia.org/wiki/Wikipedia:Edit_warring#Other_revert_rules

    You must agree to not add images to Wikipedia. If you are unblocked on Commons, you must not upload images there for use on Wikipedia.

    You also have created concerns about sourcing, especially on biographies of living persons. You must address your adding of unsourced poorly and unsourced content to Wikipedia.

    Please read Wikipedia's Guide to appealing blocks for more information. (https://en.wikipedia.org/wiki/Wikipedia:Guide_to_appealing_blocks)

    Your account is globally locked. Should you successfully request unblock on en.wiki, you will still need to ask the Stewards-- stewards@wikimedia.org.to unlock your account.

    Thanks for your attention to this matter.

    User then responded agreeably to my conditions in UTRS 30600 thusly

    I will: - Abstain from reverting edits (edit warring) - Stop uploading pictures on Commons to be used on Wikipedia - Be strict with my sources and abstain from adding irrelevant information - Listen to any instructions given by administrators - Never sock-puppet again (I haven’t sock-puppeted in roughly a year and I’ll continue to not sock-puppet.)

    I gave it some time (~24 hours) to await further input and then unblocked, but it was brought to my attention afterward that WP:THREESTRIKES probably applies. (Not immediately obvious in reviewing of talk page.) So I seek confirmation or rejection of my decision to unblock. I don't know how user would reply as globally locked. --Deep fried okra (schalte ein) 02:58, 3 June 2020 (UTC)[reply]

    Request If the unblock is overturned, could someone please indicate on user talk page that he is CBANned with a permalink to this discussion? --Deep fried okra (schalte ein) 11:46, 3 June 2020 (UTC)[reply]
    • Reading their talk page and the reasons for blocks (Copyvios, BLP vios, socking, socking and more socking), I don't think I'd trust this user for 5 minutes. Additionally, the previous 2 blocking admins expressed concern which gives me pause; unless they agree I would not support. The global lock seems rather lame (blocked on Commons, blocked on enWiki, flooding UTRS), so I don't put much stock into that. I think I would feel better if a CU could confirm a clean sock record. But before I could support (if ever), I would need a better reason than just agreeing to your terms; they must state how they will do it within the appropriate policies, and then state a convincing understanding of each policy. Their current agreement is most unconvincing. Rgrds. --Bison X (talk) 04:17, 3 June 2020 (UTC)[reply]
    • Yes, this is precisely the problem I have. With previously dealing with this editor, they would frequently say one thing, and then get caught doing the exact opposite elsewhere if you watched his edits. Sometimes with block evading, sometimes with things as simple as agreeing to not make unsourced edits, and then proceeding to make additions to an article without adding a source. And then he’d argue with you at length, about things like this where it was clear as day that he was lying. It makes it very difficult to trust him. Sergecross73 msg me 04:25, 3 June 2020 (UTC)[reply]
    • I'm open to the possibility of him being unblocked with editing restrictions, but I would also like better examples of what he plans to work on and how. As for trusting him, it's difficult. He constructed stories and identities behind several socks, claiming different names, ages, genders, locations, background such as working in various industries and attending different schools, UTRS claims of visiting this friend or that friend and being caught unfairly in sweeps of someone they "never heard of", being sisters, brothers, and everything in between. It was elaborate and calculated and went on for at least a year. I like to believe in giving people a chance and redeeming blocked editors but it's difficult on this one. -- ferret (talk) 11:52, 3 June 2020 (UTC)[reply]
    • It's been over two years and he still wants to come back, so maturity should be taken into consideration. I had good interactions with the editor during his time here, and in this case believe that another chance is warranted. Randy Kryn (talk) 15:00, 3 June 2020 (UTC)[reply]
    • I suspect we're being trolled. It takes work to get globally locked, and this guy socked a lot. Why would you want to come back to that reputation? Guy (help!) 20:21, 6 June 2020 (UTC)[reply]
    • He is banned per WP:3X so he'd need a community unban here before he could start editing again, but more importantly the account is globally locked, and I generally do not think we should be unblocking users until they have dealt with the global lock on their account. Reblock locally and tell him to appeal to the stewards. If they unlock (unlikey... locks tend to be hard to get out of) we can discuss then. TonyBallioni (talk) 20:29, 6 June 2020 (UTC)[reply]
    • As a non-admin who dealt somewhat extensively with this user, I'm confused as to why this was unblocked without discussion to begin with - he socked extensively and created so much disruption he had to be globally locked. It seems incredibly premature to have unblocked without a discussion and community input on conditions. His word isn't enough. Praxidicae (talk) 17:02, 10 June 2020 (UTC)[reply]
    • Oppose unblock per Ferret: An editor who invents "stories and identities behind several socks, claiming different names, ages, genders, locations, background such as working in various industries and attending different schools, UTRS claims of visiting this friend or that friend and being caught unfairly in sweeps of someone they "never heard of", being sisters, brothers, and everything in between [which] was elaborate and calculated and went on for at least a year" may have a role on the project; but not yet. ——Serial # 17:17, 10 June 2020 (UTC)[reply]
    • It's one of those unblocks that makes me breath in through my clenched teeth. I've just had a look at their behaviour on Commons too, and there's a massive issue with their copyright understanding/flagrant disregard for copyright legislation, and for that alone I need to oppose both an unblock here and an unlock globally. Nick (talk) 17:32, 10 June 2020 (UTC)[reply]
    • If someone could close tihs, I'll reblock as a CBAN with a permalink to this thread in the block notice. --Deep fried okra (schalte ein) 18:27, 10 June 2020 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    George Floyd film career allegations

    There's a rumor on the internet that George Floyd appeared in an adult film. This is being reported on some websites (including porn websites), but AFAIK, not in any actual RSes. I don't think we're anywhere near the level of RS coverage where we would even consider including this content, though I could be wrong about that. Editors have been adding this content to the various Floyd articles, and talk pages. It's been a bunch of different editors, but almost all new accounts or IPs. The articles themselves have been semiprotected, which has more or less stopped the addition of this content in mainspace. However, on talk pages like Talk:George Floyd and Talk:Killing of George Floyd, IPs and new editors are repeatedly making edit requests or otherwise raising the issue, sometimes not linking to any sources, other times linking to substandard sources (blogs) or really inappropriate sources (porn websites). My question is: can/should anything be done? First, should these talk page discussions be deleted, closed, or archived? (There is some mild edit warring, with some editors deleting these sections outright, and others restoring them.) Should the talk pages be protected? Should an edit filter be used? Should we just let it be? What is the protocol? Thanks in advance, Levivich[dubiousdiscuss] 18:23, 5 June 2020 (UTC)[reply]

    Per BLPTALK, at least one section where some discussion that explains why the information won't be included due to lack of RS, should probably be kept, closed, and then, if needed linked to via a talk page FAQ, so that if a new editor comes by to ask/add the same, the information or new talk page section can be removed and you can point to the FAQ/archived thread as to why instead of having to explain over and over again. I don't know why that information is even relevant (what info is specific to him on George Floyd can be summarized on the event page, making extraeous details like that even if sourcable not needed, per BLP) so just establishing the consensus against it once and being able to point to it should be sufficient to revert all future attempts to add or talk about it. --Masem (t) 18:55, 5 June 2020 (UTC)[reply]
    I guess the one section is Talk:George Floyd#George Floyd a film actor, and El C dropped an admin note there laying out a protocol. Thanks, C! Levivich[dubiousdiscuss] 17:21, 6 June 2020 (UTC)[reply]
    Anytime, Levivich. Yes, my evaluation of the (unsourced or poorly-sourced) film career mention and its prohibition therefrom, applies across the wiki. El_C 17:25, 6 June 2020 (UTC)[reply]

    Articles giving religious doctrine from primary sources

    User:Oct13 has created several articles giving Catholic doctrine, entirely (or almost entirely) using primary Church sources. One such article Church Fathers and abortion, which was a POV fork of Catholic Church and abortion, went through AfD and was deleted 3 months ago. But there are others: Holy obedience, Miraculous plague cure of 1522, Christian Socioeconomics, Hell in Catholicism, and Catholic theodicy. The last two, created last Sunday, seem to be POV forks of Problem of Hell and Existence of God, respectively. How should this be handled? Bring each one individually to AfD? Or speedy AfD? Should User:Oct13 be asked to stop doing this? Thanks. NightHeron (talk) 19:44, 5 June 2020 (UTC)[reply]

    Hi. If the articles aren't up to standards, please delete them. I was actually thinking of making an article about Forgiveness in Christianity, but would it be allowed? Oct13 (talk) 03:44, 6 June 2020 (UTC)[reply]
    Oct13: To clarify, I'm referring to two issues. First, your sources in several of the articles you created are almost entirely primary sources that you combine to create an interpretation (please read WP:RSPRIMARY and WP:OR). Second, instead of, for example, expanding the coverage of Catholic views on Hell in the main article Problem of Hell and interacting with other editors on the talk page of that article, you created a separate article on your own in which you synthesized the official statements of the Church without any perspective from secondary sources (which could be by Catholics or non-Catholics). There could possibly be good reasons to create a separate article titled "Hell in Catholicism" if there is enough discussion and debate in secondary sources and if an adequate treatment of the topic in the main article Problem of Hell would be unwieldy. But my point is that a separate article needs to be compliant with policies regarding excessive use of primary sources, original research, and POV forks. Note that the deletion process WP:AFD normally takes at least 7 days and involves an investment of time by many editors. It's not a good idea to keep creating articles that are likely to be deleted, since that wastes people's time. NightHeron (talk) 12:19, 6 June 2020 (UTC)[reply]
    Thanks for clarity! My main issue with problem two is that I have trouble finding non-primary sources for Catholic teachings that aren't self-published Catholic sites.Oct13 (talk) 20:00, 6 June 2020 (UTC)[reply]
    In that case you don't have adequate sourcing for an article on the subject. For example, concerning Hell in Catholicism, before creating an article based on primary sources you might have looked at several Wikipedia articles that already have material on the subject, and then interacted with other editors on the talk-pages to perhaps add material to those sections. See Christian views on Hell#Roman Catholicism, Christian views on Hades#Roman Catholic, Problem of Hell#Christianity, and Hell#Christianity. The same applies to other topics on which you've written articles based on primary sources. NightHeron (talk) 21:37, 6 June 2020 (UTC)[reply]
    Please also note that those article sections cite secondary sources. Since religious studies is a large field of scholarship, it should be possible to find secondary sources for any important notion in the history of theology (Hell, existence of God, forgiveness, etc.). NightHeron (talk) 21:52, 6 June 2020 (UTC)[reply]
    I removed a large addition [20] by Oct13 from The Bible and violence with similar problems. Gråbergs Gråa Sång (talk) 10:54, 7 June 2020 (UTC)[reply]

    Is this where we have the content dispute? Where is the discussion centralized? Elizium23 (talk) 21:16, 7 June 2020 (UTC)[reply]

    This is not a content dispute. This is a procedural question about how best to deal with a good-faith editor's repeated creation of new poorly sourced articles. NightHeron (talk) 11:06, 8 June 2020 (UTC)[reply]

    I'd argue that where sourcing Catholic doctrine is the intent, primary sources would be just fine. After all, official Catholic sources tend to know how Catholicism works. But of course other sources would be quite the good idea, to keep things balanced - for Catholic sources of course tend to be biased towards Catholicism (I know, shocker). -- a lad insane (channel two) 18:00, 9 June 2020 (UTC)[reply]

    AfD discussion: Miraculous plague cure of 1522

    The article Miraculous plague cure of 1522 has been nominated for deletion here. NightHeron (talk) 20:23, 7 June 2020 (UTC)[reply]

    Personal attacks and disruptive editing by Miko2020

    As if adding OR to articles wasn't bad enough, Miko2020 has decided to slowly but surely take it to the next level with personal attacks, escalating from this (see edit summary), this (see comment) to this and culminating with this comment left on my talk page.

    Here's a quick look at some of the edits of the user who's attacking me and accusing me of vandalism:

    • Couscous. [22] This speaks for itself and was reverted by another editor.
    • Kaftan.[27] Sourced content removal, addition of factually incorrect OR and content based on a misrepresented source, which I explained on the talk page. Instead of addressing what I said, they created an article that they filled with OR and introduced the same misrepresented source. You could be forgiven for thinking that they are new and maybe don't know about WP:VERIFY, but this edit of theirs on another article leaves no doubt that they do.

    In fact, their edits are almost undistinguishable from that of another editor (Jamaru25) whose edits consist mainly of adding OR, misrepresenting sources and even using fictitious sources. While I don't mind cleaning up the disruptive edits, unwarranted personal attacks such as this are not something that I'm willing to tolerate. M.Bitton (talk) 22:52, 5 June 2020 (UTC)[reply]

    For what it's worth, Miko2020 left a message on my talk page complaining, falsely, that M.Bitton had been replacing Morocco with Algeria. I looked at a couple of the articles Miko2020 mentioned to me and saw that, on the contrary, there were cases where Miko was removing references to Algeria and Tunisia so that only Morocco remained, or else was replacing North Africa with Morocco. In a case where I'd reverted one of Miko2020's edits, I was restoring Tunisia and Algeria based on sourced information. Largoplazo (talk) 23:31, 5 June 2020 (UTC)[reply]

    user Sms2sms

    The Sms2sms (talk · contribs) is only active in the English Wikipedia to continue the conflict of the deWP on discussion pages. See his contributions (German)-131.117.153.103 (talk) 05:42, 6 June 2020 (UTC)[reply]

    • They had been using their enwiki page to talk to the .de administrator that blocked them, but on 26 April posted that any further discussion should be on their meta page (since when there has been no activity) so I don't think there's anything to do here at the moment. Black Kite (talk) 12:53, 6 June 2020 (UTC)[reply]

    Discretionary sanction warning on the talk page of new editors should be considered as WP:BITE

    If a new editor, who did not receive any warning for disruptive behaviour, personal attacks, edit warring, adding contentious unsourced content and vandalism, then giving them Discretionary sanctions alert on first day is biting the new editor.

    This should not be done on first day. https://en.wikipedia.org/w/index.php?title=User_talk:Zubisko&oldid=951918392

    The editor has not edited since then.

    It's like RegentsPark identifying a potential opponent and scaring them off.

    User:Slatersteven and User:SerChevalerie interacted with the editor. — Preceding unsigned comment added by 42.110.247.116 (talk) 06:55, 6 June 2020 (UTC)[reply]

    I disagree. This is a no-fault alert that aims at informing users of the discretionary sanctions regime. El_C 06:57, 6 June 2020 (UTC)[reply]
    ^^^Thus spake El_C: arguably, too, alerts are even more important for new users as, while an established editor might be assumed to not need reminding of the restrictions (yet still is), a new editor will have no idea. By not advising them of the sanctions in place, in fact, you're making it more likely that they'll be breached. Which results, possibly, in an even less friendly welcome for the new editor. ——Serial # 07:25, 6 June 2020 (UTC)[reply]
    How are we defining "new" exactly? I suggest 2–3 years. Levivich[dubiousdiscuss

    ] 07:38, 6 June 2020 (UTC)

    Suggest 6 years, 7 months and 25 days... at least. ——Serial # 07:46, 6 June 2020 (UTC)[reply]
    What they said. It's a lot better to issue a neutral "you're dealing with a topic where the usual rules don't apply, if you're not confident that you understand all the rules around NPOV, sourcing, and inter-editor interaction, we suggest you start off in a less contentious area" warning from the outset. The alternative is that someone in good faith tries to add something they read on the internet about homeopathy/climate change/gun control, or thinks in good faith that they're improving Wikipedia by adding/removing an infobox on every page, and promptly gets themselves blocked. I do agree that the wording of the templates is incomprehensible and intimidating, but thus far nobody has come up with an alternative; that big gobbet of Bradspeak is unfortunately necessary if we're to convey precisely what "discretionary sanctions" does and doesn't mean. ‑ Iridescent 08:13, 6 June 2020 (UTC)[reply]
    It's less bitey than the alternative, which is a rapid move to blocking. Guy (help!) 09:39, 6 June 2020 (UTC)[reply]
    User:Levivich Don't go for the heading only. The editor in question was one day account only. What harm would happen if the sanction alert is given after one week of non-disruptive editing? What did I say? Don't warn them ever? Warning should be given if they show signs of disruptive editing at the beginning. You gave them welcome message, then even before they have finished reading the welcome message properly, you give them sanction alert. Within one second he will read the links mentioned in welcome message? What is he going to read first? Discretionary sanction alert or welcome message? Welcome message given at 16:04, sanction alert given at 16:05. https://en.wikipedia.org/w/index.php?title=User_talk:Zubisko&action=history Can't you people have some patience? — Preceding unsigned comment added by 42.110.218.253 (talk) 10:51, 6 June 2020 (UTC)[reply]
    With edits that are likely to blow up into a war? No. Guy (help!) 13:31, 6 June 2020 (UTC)[reply]
    I often DS template new editors. But, I always preface with a welcome if one doesn’t exist. As the welcome says their contributions are welcome and we hope they stay, it further softens the warning. Experienced editors are regularly sanctioned on DS articles. If they run into difficulties; new editors need some sort of heads-up that they’ve jumped into the deep end. O3000 (talk) 10:31, 6 June 2020 (UTC)[reply]
    The very first thing the box says is "This is a standard message to notify contributors about an administrative ruling in effect. It does not imply that there are any issues with your contributions to date." It absolutely, positively identifies itself as not a scolding. It's an alert to someone who's entered a particularly fraught topic, that's all. It's like worrying that someone is going to be scared off of driving at all by a "one-way" sign at the beginning of the one-way street, and asking what harm could come from placing it where it won't be visible until a driver has already covered the first 100 meters of the one-way section the wrong way. Largoplazo (talk) 12:29, 6 June 2020 (UTC)[reply]
    • The notification is neutrally worded and contains information that any editor, new or old, wading into the topic should be aware of and I don't see this as a problem. In particular, it would be wrong not to let someone wading into that particular controversial article that their edits will receive extra scrutiny. I'm sorry that the editor chose to not return but it doesn't follow that they should have been kept in the dark about the sanctions. Technically, it is not correct that they dropped out after the warning because they appear to have made two edits before the warning (and the welcome!) and two edits after.--regentspark (comment) 14:10, 6 June 2020 (UTC)[reply]
      Assuming that you're talking about User:Zubisko I think you've misread the edit history. There were 3 edits before the alert, and 1 after. Nil Einne (talk) 07:11, 7 June 2020 (UTC)[reply]
      You're right. I guess I misread the time. Probably not important anyway since it is likely that they either saw the notice after their last edit or have never actually seen it.--regentspark (comment) 13:14, 7 June 2020 (UTC)[reply]
    • It's bitey in that it's a huge warning with incomprehensible text. Only someone who is already familiar with how Wikipedia works can even figure out what it's warning you about. I want to point out that the linked page WP:ACDS is completely unintelligible to a newbie, and that both of the terms "discretionary" and "sanction" just seem like arcane legalese. – Thjarkur (talk) 15:05, 6 June 2020 (UTC)[reply]

    (EC) I strongly disagree. It's not a warning. It's explicitly says it's not a warning. It's unfortunate that some people interpret it that way, but there's no real way we can avoid that. So the idea we should wait for misbehaviour goes completely against the purposes of alerts which is not to warn but to alert. This doesn't mean we should give alerts for every editor who makes one edit, IMO this generally isn't necessary although it will also depend on the topic. But you should guide yourself mostly by "is this editor editing enough in the area that they probably need to know?"

    Which gets into my next point, new or old, editors need to take care when editing DS areas. In fact, DS areas tend to have admins more sensitive to problems even without using the DS process. In other words, behaviour which may earn at worst, strong rebuke may earn a block if it's happening in a DS area even if it's not through the DS process. It's good for editors to know quickly that they need to take special care, consider carefully what they are doing, listen, read our policies and guidelines, seek advice and be far less bold then we normally encourage editors to be.

    Also, in some areas we get a lot of SPAs, or worse socks. While there are measures which could be put in place for specific articles e.g. long term ECP or even long term semi protection to reduce problems, these can be controversial themselves and they can't be applied to all articles. To give one specific example, consider Wikipedia:Administrators' noticeboard/Incidents#User:777 persona 777 and Talk:Christopher Langan#Intelligent design. While okay, ECP could probably be applied to the article, I don't think it would be a good idea to do it to the talk page. But there are a lot of SPAs who keep popping up. Often these don't last very long. Giving them alerts quickly ensures that they are aware they need to take special care, and also that if necessary, they can be restricted quickly. AFAIK that hasn't even happened yet (there have been some blocks, but not under DS). Note that while me and others have alerted some of the editors, others haven't been alerted yet have disappeared, so I don't think there is even compelling evidence that they are being scared off. Frankly, in this particular case, I'm not sure if it's even harmful to scare off an editor who seems to only be here to push for or against the theories of some random person with a high IQ. To be clear, if these editors would be welcome to branch out into other areas, but most of them have only done a small amount in other areas, and even there it's often highly related.

    Note that as I've said before, personally I greatly prefer it when editors alert someone who is on their "side" (for lack of a better word) because as I said, we can't stop people misinterpreting it as a warning so it's better if it's someone who may come across as "look I agree with you, but you need to take care when editing this area". However for a new editor it may not be so obvious anyway, plus I'd still prefer someone to alert. So provided editors are consistent in when they alert, I don't see any harm.

    Nil Einne (talk) 15:20, 6 June 2020 (UTC)[reply]

    • I also disagree strongly. (1) As noted above, the alert notification is neutrally worded. (2) Not allowing newbies to be alerted, while continuing to alert other editors, puts the newbies in a unwarranted protected class. (3) Further, if the newbie has been misbehaving ina DS area, and continues to misbehave, admins would not be able to impose DS sanctions on them because they had not been alerted.
      In my opinion, the proposal is ridiculous on its face. Beyond My Ken (talk) 00:51, 7 June 2020 (UTC)[reply]
    • Let's face it: many articles under discretionary sanctions are haunted by WP:SOCKS. A sock will pretend to quit because an editor threatened him/her with discretionary sanctions, but in fact it is a circus acts merely done as trolling. Everyone who has access to a botnet could create lots of usernames in order to accuse an established editor of WP:BITE and harassment. If one knows when an editor is online and which articles he/she edits, it is very easy to pull out this trick. Yup, botnet access is for sale on the dark web. Being honest means that the rules of the game are spelled out in advance. I do not see how hiding the knowledge of those rules from newbies would help them. E.g. a creationist POV-pusher, who only comes to Wikipedia in order to spew out creationist memes, will pretend that he/she did not know that that's against policies and guidelines. Someone has to tell them as it is: not in an offensive way, but in a clear and honest way. Tgeorgescu (talk) 02:02, 7 June 2020 (UTC)[reply]
    Whether they support or oppose, but let other participants in this thread see this comment by Tgeorgescu, "If one knows when an editor is online and which articles he/she edits, it is very easy to pull out this trick." There are many editors who can give discretionary sanction alert. User:Tgeorgescu is saying that the new user was able to control who will post welcome message and discretionary snaction alert on his talk page. Socks can create new accounts, but you are saying that the editor wanted to trap RegentsPark, by editing when he was online. This is like you belive in fortune teller, soothsayer? — Preceding unsigned comment added by 42.110.228.164 (talk) 03:06, 7 June 2020 (UTC)[reply]
    I am agnostic about whether it was the case for RegentsPark, but, yes, it would be easy for socks to game the system if such restriction upon placing notifications of discretionary sanctions would be enforced. Tgeorgescu (talk) 04:19, 7 June 2020 (UTC)[reply]
    User:Tgeorgescu I don't support full restriction. I am suggesting that the new editor should show at least one trait of disruptive editing. If you are not happy with that, then give some time(more than one second) to the new editor to read the welcome message properly and then give sanction alert. 42.110.228.164 (talk) 04:37, 7 June 2020 (UTC)[reply]
    I give them to new editors who make good edits as well. I try to be impartial and prefer not to even know the content of their edits, although sometimes it's blazingly obvious. I also think that it would be in a sense unfair not to alert people asap, it might help them avoid ever making bad edits and perhaps gaining a bad reputation. Doug Weller talk 10:07, 7 June 2020 (UTC)[reply]
    Agreeing with Doug Weller. Why do people assume that a warning message is some kind of punishment or dunning? It is just a warning, like not to drive over the speed limit in a construction zone or use a hair dryer in a bathtub. - Julietdeltalima (talk) 16:19, 8 June 2020 (UTC)[reply]

    Proposal

    Add a Twinkle notification to alert new users that they have stepped into a controversial area along the lines of:

    Hello. I notice that you have edited $ARTICLE, which is in a controversial topic area on Wikipedia. As a new editor, it is probably wisest to discuss any changes on the article's Talk page prior to making them. There are special restrictions around many such articles, and this can lead to a frustrating and intimidating experience for newcomers. Feel free to ask for help at the tea house if you need guidance on how to edit this topic.

    How would that be? Guy (help!) 11:37, 9 June 2020 (UTC)[reply]

    I think that's a good proposal Guy; not at all bitey but doesn't dance around the point, would take the sting out of any DS notice, and offers a friendly place to get help ~ if nothing else on all the acronyms which must surely puzzle the new user; happy days, LindsayHello 18:40, 10 June 2020 (UTC)[reply]

    RfC close review, please?

    A few hours ago I made this close, and an editor has indicated on my talk page that they feel my close was mistaken. I invite community scrutiny and, if I have erred, I will be delighted to self-revert.—S Marshall T/C 13:14, 6 June 2020 (UTC)[reply]

    Endorse. Looks like a well-thought-out, detailed and comprehensive close. El_C 13:16, 6 June 2020 (UTC)[reply]
    Endorse close, as neutral who took no part in the RfC. A well thought-out, nuanced close of a pretty obfuscating discussion. ——Serial # 13:26, 6 June 2020 (UTC)[reply]
    A masterpiece. You closed the discussion with the only possible result, and you gave some helpful hints for next steps from a neutral third party. You may take the rest of the day off if you like. Guy (help!) 13:27, 6 June 2020 (UTC)[reply]
    Endorse. "No consensus" is the only possible result there, and those uninvolved helpful suggestions are above and beyond the call of duty. Boing! said Zebedee (talk) 14:53, 6 June 2020 (UTC)[reply]
    Endorse, as the only logical choice. The added suggestions seem quite helpful in starting a discussion towards compromise. Dennis Brown - 10:05, 8 June 2020 (UTC)[reply]

    ENGAGE issues

    Typically we have responded to WP:ENGAGE problems by blocking until the user begins to engage on their User talk page. Given that we now have partial blocks, I wonder if we should adopt a recommended practice of partial blocking from main space in such cases? I have it in mind that this could become a templated response with the aim of being less bitey than a full block, especially because it allows them to do the exact thing we want them to do, which is to discuss their changes on article talk pages. Guy (help!) 13:24, 6 June 2020 (UTC)[reply]

    I've already been doing that. It is a sound approach that minimizes damage to the editor in question, leaving avenues of communication and dispute resolution more open-ended. El_C 13:27, 6 June 2020 (UTC)[reply]
    Yes. Paul August 13:32, 6 June 2020 (UTC)[reply]
    JzG, Sounds like a good idea to me. S Philbrick(Talk) 18:27, 6 June 2020 (UTC)[reply]
    JzG, absolutely agree. Glen 18:36, 6 June 2020 (UTC)[reply]

    Anti-harassment RfC open

    The Arbitration Committee has opened the anti-harassment RfC, and invites discussion from interested editors. Maxim(talk) 13:56, 6 June 2020 (UTC)[reply]

    Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard#Anti-harassment RfC open
    The RfC is here. Beyond My Ken (talk) 00:14, 7 June 2020 (UTC)[reply]

    User:Evelynkwapong539

    This user has been making edits about Looney Tunes Cartoons, but has had a really rude attitude in their edit history when it comes people who disagree with their edits. I just want this user to understand that it's really not cool to have this attitude. c 14;51, 6 June 2020 (UTC)

    Please provide evidence in the form of diffs. El_C 14:53, 6 June 2020 (UTC)[reply]
    https://en.wikipedia.org/w/index.php?title=Looney_Tunes_Cartoons_%28season_1%29&type=revision&diff=960970798&oldid=960970723 , title=Looney_Tunes_Cartoons_(season_1)&diff=prev&oldid=961088536title=Looney_Tunes_Cartoons_(season_1)&diff=prev&oldid=961088536 , https://en.wikipedia.org/w/index.php?title=Boo!_AppeTweet&diff=prev&oldid=960973304 , https://en.wikipedia.org/w/index.php?title=List_of_Looney_Tunes_Cartoons_characters&diff=prev&oldid=960601738 , https://en.wikipedia.org/w/index.php?title=List_of_Looney_Tunes_Cartoons_characters&diff=prev&oldid=959726277

    Hope this is enough Noelephant 15;01, 6 June 2020 (UTC)

    @Noelephant: There's now a report at WP:AN/EW over this, so if you wish to comment there... There's also a discussion on the relevant article talk page, which is the best bet to resolve this without any further drama. Cheers, RandomCanadian (talk / contribs) 15:35, 6 June 2020 (UTC)[reply]
    Will do, I'm just going to let this settle, was really not trying to edit war but I can see where it can be assumed as such, thanks again. Noelephant 15:40, 6 June 2020 (UTC)[reply]
    Evelynkwapong539 was not informed of this report, Noelephant. I have done this for you. I did, however, issue a warning to them to remain civil. El_C 15:46, 6 June 2020 (UTC)[reply]

    Restore page and allow all editors to edit while AFD is ongoing

    Any chance an admin could restore Derek Chauvin to this edit. https://en.wikipedia.org/w/index.php?title=Derek_Chauvin&oldid=960677089 . Also, could you remove the edit protection? I think it will make the AFD more objective and allow editors (who are interested) to work on the article. No evidence of behavior problems here, I don't think.Casprings (talk) 19:04, 6 June 2020 (UTC)[reply]

    Casprings, that version has a speedy tag on it, so probably not the best? My suggestion is to leave it as-is, per WP:BLP, and link to an old version in the AfD so people can read it. Just my $0.02. Guy (help!) 20:29, 6 June 2020 (UTC)[reply]

    Get help drafting RFCs

    The "regulars" at WT:RFC have been talking about some common problems we see in RFCs, and we are going to try a bit of an experiment this month. This month, you can ask for help with writing your RFC question at WT:RFC.

    This is not required, but it may be helpful. If you are all lucky, then having us provide a little experienced advice may reduce the number of RFCs that get mentioned here. I particularly recommend this when:

    • a group of editors is already in conflict or someone is saying that a proposed RFC question isn't 'neutral' enough,
    • you're starting a "major" RFC (e.g., significant changes to a policy or to a contentious article), and
    • someone wants to hold a vote on what the wording of a sentence should be.

    Feel free to refer any and all new/future RFCs our direction. If editors want this service, then we may make it permanent. WhatamIdoing (talk) 19:17, 6 June 2020 (UTC)[reply]

    This certainly looks like an excellent idea, as long as the people giving the help are better placed than the people asking for it in terms of neutrality, and knowledge of Wikipedia processes. Many RFCs don't get past one of the first hurdles of having a neutrally worded question. Phil Bridger (talk) 19:52, 6 June 2020 (UTC)[reply]

    User has recreated deleted articles many, many times and created pages and contributions with little/no refs many times, as you can see on their talk page. Worth looking into. Doublah (talk) 18:07, 7 June 2020 (UTC)[reply]

    RFPP backlog

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


    Hello all, it looks like there is a backlog over at WP:RFPP. There are almost 40 requests with a few more than a day old. Thank you. -- LuK3 (Talk) 20:32, 7 June 2020 (UTC)[reply]

    I'm working through the BLPs now...-- Jezebel's Ponyobons mots 20:42, 7 June 2020 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Bundled AFD on hoax articles and stale socking

    Hello! I need help/guidance about Wikipedia:Articles for deletion/Aaitabare. I would like opinion on whether a category can ever be included in a bundle at an AFD. More importantly though, if the AFD can not be salvaged, it should probably be closed by an admin, summarising things I absolutely should not have done, and advising the proper procedures. Especially, about alleging socking, it looked fairly WP:DUCKY to me but how do I go about establishing that, if I should do it before I can bring that up at AFD? I understand ANI doesn't take stale cases, and SPI has told me once or twice not to report stale accounts. There are surely better places to ask these questions one at a time (like I probably should have done the AFD), but it's a sort of an against the clock issue, since it pertains to an ongoing AFD. So, please forgive me the things I have done wrong, and can we please discuss this here? Usedtobecool ☎️ 06:03, 8 June 2020 (UTC)[reply]

    IMHO the cat. should not be in the AfD; strike it and proceed with the AfD containing articles only. If the articles are deleted the cat can then be speedily deleted as a C1 CSD. Cats should never be brought to AfD, UnitedStatesian (talk) 07:31, 8 June 2020 (UTC)[reply]
    UnitedStatesian, thank you for responding. I have removed the category from my nomination. Usedtobecool ☎️ 12:53, 8 June 2020 (UTC)[reply]
    See WP:CFD for categories. Sorry, when I initially saw your nom I thought it was of legit VDCs created by me. Unfortunately Nepal has now become like India and Pakistan and are subject to crappy edits and hijacking and they're off the radar.† Encyclopædius 14:28, 8 June 2020 (UTC)[reply]

    Prohibited characters in user name

    I was prohibited from generating User talk:𝐼𝐿𝒾𝓀𝑒𝒯𝑜𝐸𝒹𝒾𝓉0 because of prohibited characters. Error message was: ""User talk page modification: Failed to save edit: The title "User talk:𝐼𝐿𝒾𝓀𝑒𝒯𝑜𝐸𝒹𝒾𝓉0" has been banned from creation. It matches the following blacklist entry: " .*[^\0-\x{FFFF}].* <casesensitive> # Very few characters outside the Basic Multilingual Plane are useful in titles"

    It obviously doesn't make sense to permit characters in the creation of user names which aren't allowed in page names. --David Biddulph (talk) 08:35, 8 June 2020 (UTC)[reply]

    The problem with that is that we control page names locally on the English Wikipedia but user names are global across all Wikimedia projects. Either a discussion needs to take place on meta to restrict user names (where I'm sure you would come across the objection that there may be a language/script where such characters are valid) or we can decide to change the blacklist here to allow such pages, at least in User and User talk spaces. Phil Bridger (talk) 09:16, 8 June 2020 (UTC)[reply]
    Judging by the number of users blocked, or with no contributions, in this list, a reasonable heuristic would be to indef anyone with a similar user name. Johnuniq (talk) 10:01, 8 June 2020 (UTC)[reply]
    If an indef becomes the standard, that should probably be added to the username policy. I'm personally a fan of the taking off the blacklist for userspaces, then having some sort of notice about it anyway. -- a lad insane (channel two) 11:41, 8 June 2020 (UTC)[reply]
    Don't quote me on this, but I believe edit filters can work for detecting usernames meeting certain patterns. Unsure what happens if you disallow creations, though. CC User:MusikAnimal, who wrote Special:AbuseFilter/1023 (by the way, should 1023 match "autocreateaccount"?). --Mdaniels5757 (talk) 21:11, 8 June 2020 (UTC)[reply]
    Yes edit filters can be made to disallow account creation matching any pattern. However you could argue this case is just a social problem, while Special:AbuseFilter/1023 is a workaround for a bug. Using an edit filter is an option but I probably would just update the username policy and block when these come up, as Johnuniq suggests. Other wikis may not agree and will permit these kinds of usernames.
    I did change 1023 to use "contains" rather than "==", which should account for auto-account creation. Which reminds me, this should really be implemented at meta:Title blacklist rather than a local filter. MusikAnimal talk 21:56, 8 June 2020 (UTC)[reply]

    No Great Shaker vandalism

    On Churchill war ministry No Great Shaker made edits that deleted the entire ministerial section of the article. I re-added the ministerial table that the editor had deleted, for no apparent reason, however I then saw that the reason they have for deleting it was ‘moving horrendous and unnecessary list’ meaning they deleted it because they didn’t like it: https://en.wikipedia.org/w/index.php?title=Churchill_war_ministry&diff=927805078&oldid=927796948, therefore showing that he deleted a huge chunk of vital information for no reason and with no consensus. The table was deleted in November 2019 and NGS said he was going to redo it but as of June 2020 he had not done. When I re added the deleted info, No great shaker then attempted to delete the info I had readded but was fortunately stopped by another editor called GraemeLeggett who got involved and stopped his vandalism. No great shaker had now used personal attacks, such as blocked user, when I have tried to stop him from reverting the information again, and has now changed the article again so it no longer matches the similar ones at List of British governments. If you look at the articles about ministries, eg National Government (1935-1937) or Asquith coalition ministry you will see that the layout is: Office, name, date took office etc yet no great shaker has tried to change the article for no reason and is vandalising it, by changing the format and by deleting the table altogether. Please stop him. SallyWho (talk) 16:52, 8 June 2020 (UTC)[reply]

    • As the named third party in all this, I'd better say something. From my vantage point both sides are using "vandalism" when actually it's a content dispute. The Churchill war ministry page had since 2013 and until a while back had the same section ("List of Ministers") as other ministries from 1707 to 2007 - a list of the positions and the ministers who filled them. In November 2019 the list of ministers was removed by No Great Shaker as an "unnecessary list" and ended up in Draft space as it was uncited. SallyWho it to the Churchill war ministry article yesterday (7 June) , No Great Shaker removed it again on the grounds of still unsourced, and SallyWho put it back shortly after. As I thought it belonged in the article, I decided to add to add some cites as that was the reason for previous removals. Since then No Great Shaker has made corrections and additions to the table. No Great Shaker then edited the table to remove any Ministers already covered in the preceding section which lists the members of the cabinet in the ministry , renaming the disputed section "Ministers outside the War Cabinet". SallyWho reverted that change and after that it's a back and forth with No Great Shaker calling SallyWho's reverts "troll" and SallyWho calling No Great Shaker's reverts "vandalism". GraemeLeggett (talk) 18:19, 8 June 2020 (UTC)[reply]
    • Ymblanter, I'll accept your decision on this but I think I would like you to adjudicate at the article talk page. I'll go there now and explain how I have been trying to improve the article. The account by GraemeLeggett above is a fair summary of what has happened. I may have overstepped the mark by suggesting that SallyWho is a probable block evader but it seems very odd to me that someone with a mere handful of edits should be so passionate about how another editor is trying to improve an article that has not, lets face it, been in very good shape. I cannot see how such an extreme reaction can suggest anything other than a vested interest in the article through past involvement. That's my opinion. Anyway, I'll say no more about that and will go to the article talk page to discuss the state of the article and how it can be improved. Thank you. No Great Shaker (talk) 19:55, 8 June 2020 (UTC)[reply]
    • Hmmm. SallyWho (talk · contribs · deleted contribs · logs · filter log · block user · block log) is a "brand new user" whose early edits Right Great Wrongs committed in 2019. Am I the only one who thinks that's a bit sus? Guy (help!) 08:44, 9 June 2020 (UTC)[reply]
    • Just to note that No Great Shaker added a retirement template on their talk page and accused me in driving them out of Wikipedia. Sorry, I find this accusation completely out of place and can not accept it. --Ymblanter (talk) 08:18, 10 June 2020 (UTC)[reply]

    Derek Chauvin

    Should the article for Derek Chauvin be shown while Wikipedia:Articles for deletion/Derek Chauvin is ongoing? Please {{ping}} me when you reply. --Jax 0677 (talk) 20:24, 8 June 2020 (UTC)[reply]

    • @Jax 0677: I kept it hidden out of an abundance of caution (since some in the DRV raised BLP issues), but I have no opinion on the matter. -- King of ♥ 20:28, 8 June 2020 (UTC)[reply]
    • @Jax 0677: I'm the one that suggested that it not be, but that we have a link to to a version of it in the AfD. It's unusual but not unreasonable. DRV often has discussions of material that has been "temp-undeleted" where people can look at the history. I don't think it should be SOP, but I think it's a good compromise (have the discussion but don't have the article until we decide to). Hobit (talk) 02:06, 9 June 2020 (UTC)[reply]
    • User:Jax 0677: Yes, keep it visible unless there are really serious content problems with it. It should be unprotected too. There's really not much we can write that can damage the guy compared to the beatings (I don't know what other word to use) he's taking in the general media. So I wouldn't freak out about it. I looked at the last substantial version in the revision history and it's pretty tame, all the same stuff that's been everywhere in the news, all well cited, and missing some updates.[28] A drastic step like hiding the content is sometimes warranted when there's agenda pushing or scandalizing going on, or if the person doesn't otherwise have much notoriety. This isn't one of those times. The article content is quite mainstream and the writing is staid. That said, I'm always in favor of {{noindex}}ing articles about living people. 2602:24A:DE47:BB20:50DE:F402:42A6:A17D (talk) 10:57, 9 June 2020 (UTC)[reply]
    Hadn't seen this, but FWIW I declined a G4 request at Talk:Derek Chauvin earlier today. I'd consider this section done with, but YMMV. ~ Amory (utc) 00:18, 11 June 2020 (UTC)[reply]

    Joe Lewis talk page

    Not sure, but isn't a post like this [29]? some kind of policy breach? Govvy (talk) 21:18, 8 June 2020 (UTC)[reply]

    Reverted; user warned. DrKay (talk) 21:41, 8 June 2020 (UTC)[reply]
    Oh. I indef blocked. I can undo this if i stepped on toes. --Floquenbeam (talk) 21:44, 8 June 2020 (UTC)[reply]
    k, I thought a post like that was suppose to be striked, cheers. Govvy (talk) 22:02, 8 June 2020 (UTC)[reply]
    Govvy, it contains contact details. Guy (help!) 08:45, 9 June 2020 (UTC)[reply]

    @JzG: If the edit you revdel'ed is the same as their others, then they have 6 other posts to revdel. Rgrds. --Bison X (talk) 00:28, 9 June 2020 (UTC)[reply]

    Bison X, done. Guy (help!) 08:34, 9 June 2020 (UTC)[reply]
    heh, didn't realise there was six other posts, bit strange to post that on wikipedia when there are dark web noticeboards for that! Clearly it was amateur day for that editor! Govvy (talk) 15:49, 9 June 2020 (UTC)[reply]

    Request for close review

    Back in February, I closed an RfC at Talk:Ronald Reagan. In my close, I found rough consensus to include a concise mention of some remarks, but suggested further discussion regarding the precise wording. Earlier today, Springee opened another RfC asking the same question of whether or not the remarks ought to be included. After I left a comment indicating that I consider their formulation of the RfC to be inconsistent with my prior close, they replied raising several objections to the close. Could an admin look over my close from February, decide whether or not it is valid, and then help organize the follow-up discussion that is starting to take place? Thanks, {{u|Sdkb}}talk 03:51, 10 June 2020 (UTC)[reply]

    I would like to note that I and another editor both found the previous closing to be problematic. First, the non-admin closing conclusion of "rough consensus" was questionable based on numbers. Sdkb said it came down to numbers and they felt it was 10:5 in favor. As a personal rule of thumb I feel consensus by numbers is anything over 2/3rds so at best they are borderline. However, there were 19 !votes; 9 yes, 5 no, 5 were "wait". That means only 47% of the !votes were yes. More importantly, the closing editor's neutrality on the matter suggests a strong POV for inclusion. I will repeat that I don't think their POV is inherently problematic but upon closing the RfC the Sdkb became involved with other aspects of the Reagan biography page in a way that suggested a clear POV on what sort of material should be in the article. They initiated a RfC here [[30]] . After several months no editors had actually acted on the closed RfC. Sdkb pinned the RfC so it wouldn't be archived[[31]] and solicited other editors to make the changes they felt the RfC dictated[[32]]. Based on the evidence that the closing was not handled in a neutral fashion and the mathematically questionable determination of consensus I considered challenging the original closing. However, since no editors had decided to act upon the RfC it seemed a moot issue. Now that it is 9 months later and a number of editor's replies were "wait" I see no issue with opening a new RfC that can be closed by an uninvolved editor. Springee (talk) 04:44, 10 June 2020 (UTC)[reply]
    I have not expressed any opinion about the inclusion of the remarks, and I do not think it would be my role as closer to do so. I invited two editors I noticed working on the article a month or so after the close (I don't know the political tendencies of either) to participate in the follow-up discussion about the wording since that discussion wasn't really happening; that is different than "solicited other editors to make the changes they felt the RfC dictated". {{u|Sdkb}}talk 06:03, 10 June 2020 (UTC)[reply]
    I looked into this a bit more as I had always assumed this was a formal RfC. It never was. Rather it was an informal survey that simply died out. That might explain why nothing happened between the end of discussions in October 2019 and the Sdkb's "closing" in February 2020. Springee (talk) 17:00, 10 June 2020 (UTC)[reply]

    Request for easy, non-controversial closure of informal discussion

    By an admin or experienced editor here. Although only an informal discussion, it's been open about a week and the consensus is pretty clear. If you could then action your decision too. Thanks in advance! ☕🍟🍰 ——Serial # 09:24, 10 June 2020 (UTC)[reply]

     Done, with assistance from Atlantic306. {{u|Sdkb}}talk 18:34, 10 June 2020 (UTC)[reply]

    Another RfC close review please?

    I'm sorry for having two of these open at the same time; it's because I've been going through the more contentious unclosed discussions on ANRFC. Anyway, a few hours ago I made this close, and an editor has indicated on my talk page that they feel my close was mistaken. I invite community scrutiny and, if I have erred, I will be delighted to self-revert. The complainant concurs with my determination that there's no consensus, but disputes my view that the status quo ante is the version without the disputed graphic.—S Marshall T/C 15:38, 10 June 2020 (UTC)[reply]

    @S Marshall: I hope you don't mind me being blunt? And no criticism of that (or any other) close. But just file at RfA please: it'll be a piece of cake. All the best, ——Serial # 15:55, 10 June 2020 (UTC)[reply]
    Totally out of the question.—S Marshall T/C 16:05, 10 June 2020 (UTC)[reply]
    Endorse close The summary was an accurate reflection of the discussion. I had been looking into the same discussion and would have posted nearly the same one myself. Eggishorn (talk) (contrib) 16:22, 10 June 2020 (UTC)[reply]
    (edit conflict) @Eggishorn: I agree with S Marshall's conclusion that none of the two sides of the dispute managed to reach consensus. I discussed with them on their talk page on what version of the article constitutes status quo ante. As I see things, the version with the pic in the lede is that version. After the pic was added to the lede, several months passed and, if I am not mistaken, some 30 edits were made on the article with nobody challenging that edit. Is not that counted as "silent consensus"? After "silent consensus", is not a new consensus needed to make a change? Those two questions are what I am not persuaded about in the RfC closure. Ktrimi991 (talk) 16:35, 10 June 2020 (UTC)[reply]
    Fair point. What counts as longstanding text should ordinarily be determined by local consensus, where the level of activity of the article would be a key component in determining WP:SILENCE. Because this time the status quo ante was decided by the closer (which is to say, singularly), perhaps an explanation by them as to their respective determination to that effect is due. El_C 16:43, 10 June 2020 (UTC)[reply]
    @Ktrimi991:, might I suggest reviewing WP:CHALLENGECLOSE? The close was ... a reasonable summation of the discussion and the closer has no history that would make them involved in the discussion. If the close accurately summarized the discussion, even if that discussion was based on faulty premises, then the discussion is still closed. It is not up to the closer to correct the participants. Doing so results in a WP:Supervote. I can see your point about the sequence of events but I feel S Marshall also accurately summarized those in your challenge on their talk page. Eggishorn (talk) (contrib) 16:46, 10 June 2020 (UTC)[reply]
    @Eggishorn: I am aware of what is said on WP:CHALLENGE. I came here after the proposal to do so by S Marshall. I thanked him for his review process, and I have not asked him to correct any participant. The point I would like clarification about could probably be summarized this way: If I challenge an edit made 1 year ago, and after discussion there is no consenus, then the version I support should stay as a pre-dispute one? If that is the rationale applied, then one can easily remove content added years ago and those who disagree should not revert but just seek a "new consensus" on the talk page per WP:BRD. Is that the right way of action? Ktrimi991 (talk) 17:55, 10 June 2020 (UTC)[reply]
    Also, if one today decides to remove content that was added a year or several months ago, can we say that the dispute started a year or several months ago? Ktrimi991 (talk) 18:08, 10 June 2020 (UTC)[reply]
    • Endorse. As the principal admin who has been attending to the article in question, I'd like to thank you, S Marshall, for once again taking on these difficult closes. Your efforts are greatly appreciated and I hope you keep up the good work. El_C 16:30, 10 June 2020 (UTC)[reply]
    • Endorse. The default position should be not to include contentious content. This was a brave close, in the proper sense of the term "brave". Phil Bridger (talk) 19:27, 10 June 2020 (UTC)[reply]
    @Phil Bridger: On what Wiki policy is your opinion that contentious content should not be kept on the article based on? Ktrimi991 (talk) 19:41, 10 June 2020 (UTC)[reply]
    It's based on common sense, which is more important than any policy. Phil Bridger (talk) 19:47, 10 June 2020 (UTC)[reply]
    "Common sense" can cause disputes rather than solve them in controversial Balkan topics. No wonder Balkan topics on Wikipedia have so many problems and conflicts. The rationale of that "common sense" implies that one can remove content from an article and they do not even need consensus because "contentious content" should not be on the article. I was aware of the fact that editors in general tend to support decisions such as RfC closures, but I expected some justification based on well-defined rules, not that kind of "common sense". It is no wonder then that Wiki has lost so many editors during the years. Anyways, I do not see any reason to further continue this discussion, as it has already become pointless. Ktrimi991 (talk) 19:58, 10 June 2020 (UTC)[reply]
    • After reading all the input on this discussion, I do sympathize with Ktrimi991. The effect of the decision I made is to crystallize what Ktrimi991 feels is the wrong version of the article -- and I can see why, when I have sat the "stable version" such a long time in the past, this user might feel as if I've played a bit fast and loose with the rules.
      My position is that encyclopaedia-writers are educators, and that puts us under a basic duty not to mislead people. Properly analyzing sources is fundamental to what we do. In this case, independent and normally-reliable sources like the CIA World Factbook do seem to use the figures on this 2011 census -- but there are other, also independent and normally-reliable, sources that describe it as wildly inaccurate. We're dealing with research that's disputed, or even, suspect. In those circumstances, I took the view that the last "stable" version was the one that doesn't include an infographic based on the disputed research, and my view on that was certainly coloured by the possibility that the infographic is wrong.
      Please note that in doing so, I've backdated the last "stable" version well over a year from the start of the RfC. In that respect my decision was unusual, so Ktrimi991's outrage is understandable. We need to be fair, and although I'm grateful for all the "endorses" above, I do feel that some more careful, sober analysis from uninvolved editors is called for, and I'm completely open to being overturned if I was wrong.—S Marshall T/C 00:57, 11 June 2020 (UTC)[reply]

    Hiya pals,

    ProcrasinatingReader dropped this in front of me after noticing Paolocmartin (talk · contribs)'s confusing and slightly messy contribs in the RC feed, apparently in assocation to the linked project.

    I've dropped a note on the talkpage of JenOttawa (talk · contribs), who appears be associated with the project's organisation and also seems to have a clue.

    No admin-y action required from anyone yet: I just wanted to put this on your radar because I expect Paulocmartin might end up being blocked, and this provides a little bit of context that's not immedately obvious from the first page of their contributions.

    On a more general note, we've really gotta do something about the intersection of academia / education and Wikipedia. Although this isn't necessarily one of those cases, I keep seeing very low quality content from WikiEd participants - it would suggest we're not communicating well enogh, or providing enough resources. Perhaps this is something that the WMF should be spending money on.

    Cheers,

    -- a they/them | argue | contribs 21:17, 10 June 2020 (UTC)[reply]

    JenOttawa is handling - cheers all. -- a they/them | argue | contribs 22:54, 10 June 2020 (UTC)[reply]
    Seems mostly cleared up. Thanks for looking into it Allie!
    An admin may wish to do a final clean-up by deleting/moving pages like Wikipedia:Welcome/Research and Wikipedia:Welcome/About etc as appropriate. ProcrasinatingReader (talk) 00:32, 11 June 2020 (UTC)[reply]

    CGDNSAA update/lots of sock puppets to block

    Good news! The vids were just restored to a playlist I can access, which means my vandalism is actually done. What's more, here is a big long list of socks you can block now since I won't be needing them, in numerical order (the number before each is not part of the name, just my way of organizing it in a Google Doc which was too much trouble to remove for the copy and paste, but the same number at the end of each username is):

    long list of socks
    The following discussion has been closed. Please do not modify it.
    • 136. Barefoot136
    • 137. Sandals137
    • 138. FlipFlops138
    • 139. FeetInTheWater139
    • 140. ToesInTheSand140
    • 141. Hannah141
    • 142. Emma142
    • 143. Kelsey143
    • 144. Adele144
    • 145. Rebecca145
    • 146. Evan146
    • 147. Sparkles147
    • 148. Liam148
    • 149. Luke149
    • 150. Dorothy150
    • 151. CallMeWhatYouWant151
    • 152. IDontCare152
    • 153. HeartThrowerOuter153
    • 154. RealLifeGirl154
    • 155. Fellwood155
    • 156. Cinderella156
    • 157. Aurora157
    • 158. Mulan158
    • 159. Jasmine159
    • 160. Ariel160
    • 161. Rapunzel161
    • 162. Tiana162
    • 163. Moana163
    • 164. Anna164
    • 165. Merida165
    • 166. Elsa166
    • 167. Alice167
    • 168. Pikachu168
    • 169. Eevee169
    • 170. Piplup170
    • 171. Totoro171
    • 172. Mario172
    • 173. Zelda173
    • 174. Luigi174
    • 175. Sonic175
    • 176. January176
    • 177. February177
    • 178. March178
    • 179. April179
    • 180. July180
    • 181. May181
    • 182. June182
    • 183. August183
    • 184. September184
    • 185. October185
    • 186. November186
    • 187. December187
    • 188. Pancakes188
    • 189. Sushi189
    • 190. Pizza190
    • 191. FaceMask191
    • 192. HandSanitizer192
    • 193. Lysol193
    • 194. SixFeet194
    • 195. OnlineMeeting195
    • 196. NiceTry196
    • 197. NoLuck197
    • 198. ComingBack198
    • 199. BetterThanBefore199
    • 200. Alta200
    • 201. OneWay201
    • 202. OrAnother202
    • 203. TheTruth203
    • 204. IsComing204
    • 205. Back205
    • 206. Nada206
    • 207. Nothing207
    • 208. Zip208
    • 209. Zilch209
    • 210. Bupkis210
    • 211. Sierra211
    • 212. Appalachian212
    • 213. Rocky213
    • 214. Fuji214
    • 215. Everest215
    • 216. Car216
    • 217. Bus217
    • 218. Train218
    • 219. Boat219
    • 220. Plane220
    • 221. Essential221
    • 222. Service222
    • 223. Information223
    • 224. Facts224
    • 225. Education225
    • 226. Star226
    • 227. Sun227
    • 228. Moon228
    • 229. Earth229
    • 230. Cloud230
    • 231. Up231
    • 232. Down232
    • 233. Left233
    • 234. Right234
    • 235. Forward235
    • 236. Backward236
    • 237. North237
    • 238. South238
    • 239. East239
    • 240. West240
    • 241. C241
    • 242. G242
    • 243. SF243
    • 244. HB244
    • 245. W245
    • 246. CountByTwos246
    • 247. Always247
    • 248. Double248
    • 249. SpringForFall249
    • 250. QuarterThousand250
    • 251. HavingFun251
    • 252. TyingShoe252
    • 253. ClimbingTree253
    • 254. ClosingDoor254
    • 255. StillAlive255
    • 256. PickUpSticks256
    • 257. ImInHeaven257
    • 258. ClosingGate258
    • 259. DoingFine259
    • 260. YoureMyHero260

    — Preceding unsigned comment added by 73.94.194.11 (talk) 21:52, 10 June 2020 (UTC)[reply]

    Seems like a hoax. After checking a dozen of the user names, none of these seem to be real user's name. CBS527Talk 22:36, 10 June 2020 (UTC)[reply]
    Regardless of the overall validity of this every one I've checked is a genuine account created over the last 3-4 weeks. Check the log for each user. ~ mazca talk 22:40, 10 June 2020 (UTC)[reply]
    They are real accounts, but haven't made any edits. But I don't think blocking them would be necessary now that the vandal is off Wikipedia? TryKid[dubiousdiscuss] 22:45, 10 June 2020 (UTC)[reply]

    Bot to add missing protection templates, including fully-protected articles

    See the BRFA at Wikipedia:Bots/Requests for approval/MusikBot II 4. MusikAnimal talk 01:07, 11 June 2020 (UTC)[reply]