Cannabis Ruderalis

    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 three days are archived by Lowercase sigmabot III.(archivessearch)

    Start a new discussion

    Template:Active editnotice

      Use the closure requests noticeboard to ask an uninvolved editor to assess, summarize, and formally close a Wikipedia discussion. Do so when consensus appears unclear, it is a contentious issue, or where there are wiki-wide implications (e.g. any change to our policies or guidelines).

      Do not list discussions where consensus is clear. If you feel the need to close them, do it yourself.

      Move on – do not wait for someone to state the obvious. In some cases, it is appropriate to close a discussion with a clear outcome early to save our time.

      Do not post here to rush the closure. Also, only do so when the discussion has stabilised.

      On the other hand, if the discussion has much activity and the outcome isn't very obvious, you should let it play out by itself. We want issues to be discussed well. Do not continue the discussion here.

      There is no fixed length for a formal request for comment (RfC). Typically 7 days is a minimum, and after 30 days the discussion is ripe for closure. The best way to tell is when there is little or no activity in the discussion, or further activity is unlikely to change its result.

      When the discussion is ready to be closed and the outcome is not obvious, you can submit a brief and neutrally worded request for closure.

      Be sure to include a link to the discussion itself and the {{Initiated}} template at the beginning of the request. A helper script can make listing discussions easier.

      Any uninvolved editor may close most discussions, so long as they are prepared to discuss and justify their closing rationale.

      Closing discussions carries responsibility, doubly so if the area is contentious. You should be familiar with all policies and guidelines that could apply to the given discussion (consult your draft closure at the discussions for discussion page if unsure). Be prepared to fully answer questions about the closure or the underlying policies, and to provide advice about where to discuss any remaining concerns that editors may have.

      Non-admins can close most discussions. Admins may not overturn your non-admin closures just because you are not an admin, and this should not normally be in itself a problem at closure reviews. Still, there are caveats. You may not close discussions as an unregistered user, or where implementing the closure would call to use tools or edit permissions you do not have access to. Articles for deletion and move discussion processes have more rules for non-admins to follow.

      Technical instructions for closers

      Please append {{Doing}} to the discussion's entry you are closing so that no one duplicates your effort. When finished, replace it with {{Close}} or {{Done}} and an optional note, and consider sending a {{Ping}} to the editor who placed the request. Where a formal closure is not needed, reply with {{Not done}}. After addressing a request, please mark the {{Initiated}} template with |done=yes. ClueBot III will automatically archive requests marked with {{Already done}}, {{Close}}, {{Done}} {{Not done}}, and {{Resolved}}.

      If you want to formally challenge and appeal the closure, do not start the discussion here. Instead follow advice at WP:CLOSECHALLENGE.


      Other areas tracking old discussions

      Administrative discussions

      Place new administrative discussions above this line using a level 3 heading

      Requests for comment

      Talk:Battle_of_Kosovo#RfC Should Muzaka and Jonima be included in the infobox?

      (Initiated 164 days ago on 7 November 2023) I mistakenly assumed an admin would automatically closure the RfC, so that's why the discussion has turned old. However, it stills needs a final result. Latest comment: 87 days ago and 16 editors involved in the discussion. --Azor (talk) 22:08, 1 April 2024 (UTC)[reply]

      Talk:Awdal#RFC - Habr Awal/Isaaq clan

      (Initiated 116 days ago on 24 December 2023) ScottishFinnishRadish (talk) 21:17, 24 January 2024 (UTC)[reply]

      Wikipedia talk:Naming conventions (Korean)#RFC

      (Initiated 64 days ago on 14 February 2024) First time I've ever requested a close, please lmk if done wrong. Think conversation has slowed and it's been a while since it started. toobigtokale (talk) 02:16, 28 March 2024 (UTC)[reply]

       Doing... voorts (talk/contributions) 17:21, 19 April 2024 (UTC)[reply]
       Done voorts (talk/contributions) 17:41, 19 April 2024 (UTC)[reply]

      Wikipedia:Requests for adminship/2024 review/Phase I closes

      (Initiated 64 days ago on 15 February 2024) As the first round of Phase I reaches 30 days in action, I'll be listing discussions here as they reach time. Once the final discussion has been closed, this heading can be archived. Proposals ripe for closing:

      Thanks! theleekycauldron (talk • she/her) 18:56, 19 March 2024 (UTC)[reply]

      I've closed 3b and 7. I believe 13 and 14 are also overdue now too. – Joe (talk) 13:34, 24 March 2024 (UTC)[reply]
      Updated, thanks! theleekycauldron (talk • she/her) 06:28, 25 March 2024 (UTC)[reply]
      Nearly every proposal can now be closed. Soni (talk) 22:48, 4 April 2024 (UTC)[reply]
      and I think now any and all can be closed. theleekycauldron (talk • she/her) 03:38, 12 April 2024 (UTC)[reply]
      4 was closed User:Wehwalt. Nagol0929 (talk) 12:41, 9 April 2024 (UTC)[reply]

      Talk: Interstate 90#RFC: Infobox junctions

      (Initiated 49 days ago on 29 February 2024) Discussion is about to expire and will need closure. RoadFan294857 (talk) 15:37, 28 March 2024 (UTC)[reply]

      Wikipedia talk:Criteria for speedy deletion#RfC: enacting X3

      (Initiated 43 days ago on 7 March 2024) SilverLocust 💬 22:51, 30 March 2024 (UTC)[reply]

      Talk:Paul_Atreides#RfC_on_the_infobox_image

      (Initiated 40 days ago on 9 March 2024) Trying this one again. Latest comment: 3 days ago, 98 comments, 21 people in discussion. Admins are involved, vigorous WP:NFCC discussion. Closure would be good. Gråbergs Gråa Sång (talk) 09:13, 26 March 2024 (UTC)[reply]

      Thanks for posting this; I was about to do so myself. The consensus seems pretty clear, but given this is a copyright issue I think a formal close is beneficial. InfiniteNexus (talk) 04:56, 3 April 2024 (UTC)[reply]

      Talk:Jonathan Glazer#RfC: The Zone of Interest section of article

      (Initiated 31 days ago on 19 March 2024) Legobot has removed the RfC template. TarnishedPathtalk 11:13, 18 April 2024 (UTC)[reply]

      Talk:Fani Willis#RfC: Nathan Wade relationship

      (Initiated 31 days ago on 19 March 2024) Legobot has removed the RfC template. TarnishedPathtalk 06:06, 19 April 2024 (UTC)[reply]

       Done voorts (talk/contributions) 17:13, 19 April 2024 (UTC)[reply]

      Talk:SpaceX Starship#RfC on IFT-3

      (Initiated 29 days ago on 21 March 2024) This is a contentious issue with accusations of tendentious editing, so the RfC would benefit from a formal closure. Redraiderengineer (talk) 14:48, 14 April 2024 (UTC)[reply]

      A note for the closing editor... an inexperienced editor attempted to close this discussion and didn't really address the arguments. There's been some edit warring over the close, but it should be resolved by an experienced, uninvolved editor. Nemov (talk) 19:28, 19 April 2024 (UTC)[reply]

      Talk:StoneToss#RfC:_Exclusion_of_StoneToss's_website_from_the_article

      (Initiated 25 days ago on 25 March 2024) Has been running for 10 days but discussion has slowed down considerably recently. Contentious topic, so requesting formal closure here. — Czello (music) 12:48, 4 April 2024 (UTC)[reply]

      RfC: Is the OCB RS?

      (Initiated 24 days ago on 26 March 2024) This WP:RSN RfC was initiated on March 26, with the last !vote occurring on March 28. Ten editors participated in the discussion and, without prejudicing the close one way or the other, I believe a closer may discover a clear consensus emerged. It was bot-archived without closure on April 4 due to lack of recent activity. Chetsford (talk) 21:51, 4 April 2024 (UTC)[reply]

      Talk:StoneToss#RfC: Should the revelation of StoneToss's identity be referred to as doxxing?

      (Initiated 23 days ago on 27 March 2024) Discussion has slowed. 6 days since last vote. TarnishedPathtalk 05:33, 11 April 2024 (UTC)[reply]

      Place new discussions concerning RfCs above this line using a level 3 heading

      Deletion discussions

      XFD backlog
      V Jan Feb Mar Apr Total
      CfD 0 0 5 13 18
      TfD 0 0 0 6 6
      MfD 0 0 0 2 2
      FfD 0 0 0 1 1
      RfD 0 0 0 30 30
      AfD 0 0 0 0 0

      Wikipedia:Templates for discussion/Log/2024 March 17#Template:Officially used writing systems in India

      (Initiated 33 days ago on 17 March 2024) Frietjes (talk) 15:37, 9 April 2024 (UTC)[reply]

      Place new discussions concerning XfDs above this line using a level 3 heading

      Other types of closing requests

      Talk:Eat_Bulaga!#Merger_of_Eat_Bulaga!_and_E.A.T.

      (Initiated 104 days ago on 6 January 2024) The discussion wasn't inactive for 7 days. It seems there's no clear consensus on merging those two articles into one. 107.185.128.255 (talk) 18:16, 3 February 2024 (UTC)[reply]

      It's been over a month. So, it could be a good time to close that discussion. 107.185.128.255 (talk) 17:55, 28 February 2024 (UTC)[reply]

      Talk:Charles_XI_of_Sweden#Requested_move_13_January_2024

      (Initiated 97 days ago on 13 January 2024) – Requested move open for 2 months, needs closure. Natg 19 (talk) 16:55, 27 March 2024 (UTC)[reply]

      Has now been open for three months. 2601:249:9301:D570:9012:4870:54CD:5F95 (talk) 04:22, 13 April 2024 (UTC)[reply]

      Talk:Frederik_IX_of_Denmark#Requested_move_15_January_2024

      (Initiated 95 days ago on 15 January 2024) – Requested move open for 2 months, needs closure.98.228.137.44 (talk) 18:36, 30 March 2024 (UTC)[reply]

      Now has been open for three months. 170.76.231.175 (talk) 15:17, 15 April 2024 (UTC)[reply]

      Talk:Maersk Hangzhou#Second merge proposal

      (Initiated 86 days ago on 24 January 2024) Merge discussion involving CTOPS that has been open for 2 weeks now. Needs closure. The Weather Event Writer (Talk Page) 04:46, 8 February 2024 (UTC)[reply]

      @WeatherWriter: I would give it a few days as the discussion is now active with new comments. GoldenBootWizard276 (talk) 00:00, 3 March 2024 (UTC)[reply]
      As nominator, I support a non consensus closure of this discussion so we can create an RFC to discuss how WP:ONEEVENT applies in this situation. GoldenBootWizard276 (talk) 21:56, 9 March 2024 (UTC)[reply]

      Talk:1985_Pacific_hurricane_season#Proposed_merge_of_Hurricane_Ignacio_(1985)_into_1985_Pacific_hurricane_season

      (Initiated 80 days ago on 30 January 2024) Listing multiple non-unanimous merge discussions from January that have run their course. Noah, AATalk 13:50, 15 March 2024 (UTC)[reply]

      Talk:2003_Pacific_hurricane_season#Proposed_merge_of_Hurricane_Nora_(2003)_into_2003_Pacific_hurricane_season

      (Initiated 80 days ago on 30 January 2024) Noah, AATalk 13:50, 15 March 2024 (UTC)[reply]

      Talk:Pharnavaz_I_of_Iberia#Requested_move_6_February_2024

      (Initiated 73 days ago on 6 February 2024) Requested move open for nearly 2 months. Natg 19 (talk) 17:46, 27 March 2024 (UTC)[reply]

      Talk:David_III_of_Tao#Requested_move_9_February_2024

      (Initiated 70 days ago on 9 February 2024) – Requested move open for nearly 2 months, needs closure. Natg 19 (talk) 16:55, 27 March 2024 (UTC)[reply]

      Talk:Amytis_of_Babylon#Requested_move_12_February_2024

      (Initiated 67 days ago on 12 February 2024) – Requested move open for several months, needs closure. Natg 19 (talk) 22:29, 18 April 2024 (UTC)[reply]

      Talk:2 World Trade Center#Split proposal 16 February 2024

      (Initiated 63 days ago on 16 February 2024) Split discussion started over a month ago. TarnishedPathtalk 11:19, 23 March 2024 (UTC)[reply]

      Talk:Tupelo_(disambiguation)#Requested_move_17_February_2024

      (Initiated 62 days ago on 17 February 2024) – Requested move open for over a month, needs closure. Natg 19 (talk) 17:11, 27 March 2024 (UTC)[reply]

      Talk:Isabella_II#Requested_move_18_February_2024

      (Initiated 61 days ago on 18 February 2024) – Requested move open several months, needs closure. Natg 19 (talk) 22:29, 18 April 2024 (UTC)[reply]

      Talk:South_Western_Railway_(train_operating_company)#Requested_move_25_February_2024

      (Initiated 53 days ago on 25 February 2024) – Requested move open several months, needs closure. Natg 19 (talk) 22:29, 18 April 2024 (UTC)[reply]

      Talk:Genital_modification_and_mutilation#Requested_move_26_February_2024

      (Initiated 53 days ago on 26 February 2024) – Requested move open several months, needs closure. Natg 19 (talk) 22:29, 18 April 2024 (UTC)[reply]

      Talk:Vyaz_(Cyrillic_calligraphy)#Requested_move_26_February_2024

      (Initiated 53 days ago on 26 February 2024) – Requested move open several months, needs closure. Natg 19 (talk) 22:29, 18 April 2024 (UTC)[reply]

      Talk:Edward_V_of_England#Requested_move_29_February_2024

      (Initiated 50 days ago on 29 February 2024) – Requested move open for a month, needs closure. Natg 19 (talk) 17:11, 27 March 2024 (UTC)[reply]

      Talk:Shukan_Shincho#Requested_move_29_February_2024

      (Initiated 50 days ago on 29 February 2024) – Requested move open several months, needs closure. Natg 19 (talk) 22:29, 18 April 2024 (UTC)[reply]

      Talk:Lusitania#Requested_move_29_February_2024

      (Initiated 49 days ago on 29 February 2024) – Requested move open for a month, needs closure. Natg 19 (talk) 21:06, 1 April 2024 (UTC)[reply]

      Place new discussions concerning other types of closing requests above this line using a level 3 heading

      Pages recently put under extended-confirmed protection

      Report
      Pages recently put under extended confirmed protection (23 out of 7611 total) (Purge)
      Page Protected Expiry Type Summary Admin
      Mainspace 2024-04-19 22:06 indefinite create Repeatedly used by mistake by new editors Liz
      User talk:郊外生活 2024-04-19 20:59 2025-04-19 20:59 edit,move childish harassment Drmies
      Chitra Ramanathan 2024-04-19 15:57 indefinite create Repeatedly recreated Joe Roe
      Lana Antonova 2024-04-19 15:43 indefinite create Repeatedly recreated Joe Roe
      Oura Health 2024-04-19 14:30 2025-04-19 14:30 edit,move Persistent sock puppetry, see ticket:2024040510007342 Joe Roe
      2024 Israeli retaliatory strikes in Iran 2024-04-19 04:04 indefinite edit,move Contentious topic restriction: per RFPP and ARBPIA Daniel Case
      Jishnu 2024-04-19 04:00 indefinite edit,move Restore prior salting since I think the socks will come back Pppery
      Shakya (surname) 2024-04-19 03:43 indefinite edit,move Community sanctions enforcement: per RFPP and WP:GS/CASTE Daniel Case
      Raid on Tendra Spit 2024-04-19 03:38 indefinite edit,move Community sanctions enforcement: per RFPP and WP:RUSUKR Daniel Case
      Battle of Chasiv Yar 2024-04-19 03:35 indefinite edit,move Community sanctions enforcement: per RFPP and WP:RUSUKR Daniel Case
      2024 Israeli strikes in Iran 2024-04-19 03:29 indefinite edit,move Contentious topic restriction: per RFPP and ARBPIA Daniel Case
      Indigenous peoples of Mexico 2024-04-18 16:30 2024-07-18 16:30 edit,move Edit warring / content dispute Ohnoitsjamie
      Talk:Cullen Hussey 2024-04-18 04:56 2024-04-25 04:56 create Repeatedly recreated Liz
      Mongol invasions of Durdzuketi 2024-04-17 22:25 2025-04-17 22:25 edit,move Contentious topics enforcement for WP:CT/EE; requested at WP:RfPP Daniel Quinlan
      Occupation of the Gaza Strip by Israel 2024-04-17 22:20 indefinite edit,move Contentious topics enforcement for WP:CT/A-I; requested at WP:RfPP Daniel Quinlan
      Samma (tribe) 2024-04-17 05:10 indefinite edit,move Community sanctions enforcement: per RFPP and WP:GS/CASTE Daniel Case
      Portal:Current events/2024 April 16 2024-04-16 23:12 2024-05-16 23:12 edit,move Contentious topics enforcement for WP:CT/A-I; requested at WP:RfPP Daniel Quinlan
      Category talk:Motherfuckers 2024-04-16 22:03 indefinite create Repeatedly recreated Smalljim
      Mike Johnson (Louisiana politician) 2024-04-16 21:55 2025-04-16 21:55 edit,move Contentious topic restriction: WP:CT/AP. The underlying indefinite semi-protection by Courcelles should be restored afterwards; I hope I'll remember to do so. ToBeFree
      Hezbollah–Israel conflict 2024-04-16 21:53 indefinite edit,move Contentious topics enforcement for WP:CT/A-I; requested at WP:RfPP Daniel Quinlan
      Template:Atopr 2024-04-16 18:00 indefinite edit,move High-risk template or module: 2505 transclusions (more info) MusikBot II
      Wikipedia talk:Reno Fahreza 2024-04-16 05:57 indefinite create Repeatedly recreated Liz
      Lockheed Martin F-35 Lightning II Israeli procurement 2024-04-16 03:06 indefinite edit,move Contentious topic restriction: WP:PIA, WP:ECR El C

      Rename request from SuperSucker

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


      Hey, I am posting this on the behalf of User:SuperSucker, since they requested a renaming and are blocked on English Wikipedia. (A little discussion about this is here). 17:40, 14 November 2018 (UTC) — Preceding unsigned comment added by 1997kB (talk • contribs)

      User:SuperSucker is still under an indefinite block per this ANI from 28 March. Their block notice refers to WP:NOTHERE plus repeated IP socking. Since the editor still has access to their talk page, they could post an unblock request at User talk:SuperSucker. EdJohnston (talk) 18:18, 14 November 2018 (UTC)[reply]
      Unblock has been declined by NRP per IP socking. I see no reason to grant a rename here. TonyBallioni (talk) 05:40, 15 November 2018 (UTC)[reply]
      I don't personally see a reason to oppose renaming since they seem in good standing on commons and they can be required to ensure to mention their previous username on any unblock request here. I mean if there's fear someone will try and push their images onto articles and people won't recognise the creator, we could always notify of the username change on relevant article talk pages. Or in other words, I don't see how them being renamed harms us in any way and they have a reason for wanting to be renamed, despite being blocked here. (It's obviously normally a waste of time to rename people if they're not editing anywhere.) After all, if they were to ever successfully unblocked, we'd surely allow a rename right after. And while people sometimes have to put up with the consequences of their ill advised choices, having a username SuperSucker must be super sucky. But I'd oppose an unblock if they've been editing with an IP less than 6 months ago. Nil Einne (talk) 10:24, 15 November 2018 (UTC)[reply]
      • Oppose rename - if they can convince one of the other wikis to rename them then fine, but if they're blocked here and socking, I've no interest in doing them any favours. Username's inconvenient for editing other projects? Not English Wikipedia's problem. Ivanvector (Talk/Edits) 14:37, 15 November 2018 (UTC)[reply]
        • Comment @Ivanvector: AFAIK the user is not asking the English wikipedia to rename them. They asked at meta, but were denied because they are blocked here. It may not be the English wikipedia's problem, but I don't see a reason to deny them the right to rename on meta, which is what we are doing by opposing a rename since meta has explicitly told them that they need to convince us to allow a rename. (Not implement it, but allow it.) Refusing a user the right to rename elsewhere because they've been disruptive here, and the rename will not actually make one iota of difference to us reeks of punishment rather than preventing disruption to me. Nil Einne (talk) 18:17, 15 November 2018 (UTC)[reply]
      "Oppose unblock" is I suppose what I should have said, owing to their ongoing block evasion. If their disruptive behaviour here means that meta won't honour their request, tough shit. Don't evade blocks. Ivanvector (Talk/Edits) 18:25, 15 November 2018 (UTC)[reply]
      Comment @Ivanvector: But why oppose a rename? As I've said, there's no reason it has to concern us. We can oppose an unblock, but have no objection to a rename elsewhere as I've done. Tough shit is fine, but you seem to me to be intentionally punishing another editor by refusing to allow them a rename for no reason. IIRC it was you who reverted one of my comments trying to help another editor because you regarded is as grave dancing. While I can understand this was comment was poorly phrased, I find it a little surprising that you're now effectively advocating punishing another editor by refusing to allow them being elsewhere, because they are blocked here. Now if meta refuses to allow them to be renamed without being unblocked that's fine, but the original discussion is ambigious and seems to suggest that it's possible they can be renamed, if they convince us to allow it, despite being blocked here. All we have to do is say oppose unblock but don't give a damn about a rename, as I've done. What happens from there on is none of our concern. Instead we're wasting time IMO trying to punish an editor simply because they were badly disruptive here, but I've seen absolutely no reason why it harms us if they are renamed elsewhere, nor how it prevents disruption here, by allowing the editor to get on with whatever they want to do elsewhere, hopefully in accordance with their policies and guidelines so they aren't blocked there too. Nil Einne (talk) 18:34, 15 November 2018 (UTC)[reply]
      I presume you're referring to this, and I don't exactly recall the circumstances there but I don't see what that has to do with this. If you think I'm opposing this because of some grudge I hold against you, you are very badly mistaken. The disruption that would result from this blocked user being renamed is all of the admin time we would then have to waste jumping through hoops (as you've helpfully itemized in your reply to Dlohcierekim below) for an editor who has repeatedly ignored our policies (via block evasion) but has suddenly learned that, oh shit! they need us to do them a favour. I'm not here for it. If you think that's punitive then so be it. Score one for the "being a jerk on the internet should have consequences" crowd. Ivanvector (Talk/Edits) 19:12, 15 November 2018 (UTC)[reply]
      Just to be absolutely clear even if you're intending on not following the conversation any more, I respect your approach here and very highly value any editor who is willing to assume good faith and go to bat for someone asking for help. I find the user's request highly disingenuous in this case, but had you come here with any other editor in this situation who wasn't evading a block as recently as last week, I'd be right there advocating with you. I'm sorry that we disagree in this instance. Ivanvector (Talk/Edits) 19:16, 15 November 2018 (UTC)[reply]
      • regretful oppose The reason for not renaming is the block. not visa versa. This is to prevent problems from cropping up. Any unblock can accompany a renaming at that time.-- Dlohcierekim (talk) 18:22, 15 November 2018 (UTC)[reply]
        • Comment @Dlohcierekim: Can you outline what problems you believe may crop up? As I've said above, it seems to me any possible problems can be resolved by ensuring that they mention any previous username in an unblock request and perhaps keep a message on their user page or talk page or both clearly mention the rename, at least until they've been unblocked. if it's felt that admins may still miss it, or that the editor may remove the stuff and not mention it on their unblock request, their block log can always be annotated although yes that would require someone here to take action which is unfortunate but IMO so minor that it's not worth worrying about. We can notify on relevant article talk pages if there's concerns over IPs trying to push images they've created onto articles. Heck I can do that myself if people feel it's necessary. I'm fine with opposing a rename if there is some real problem/disruptive it would cause, but I just can't see how it would do so here so IMO even though unintentionally we're actually punishing them by refusing a rename rather than preventing disruption. Again if there's some possibility I've missed, I'd be happy to hear it. Nil Einne (talk) 18:47, 15 November 2018 (UTC)[reply]
          • Comment Just to let people know, if this rename is implemented and people want me to do anything like inform editors on relevant article talk pages, please let me know on my talk page as I won't be following this discussion further, for personal reasons. (I excluded the explanation from here since it's probably not helpful, but if you're wondering I did post it here [1] although regretfully on my talk page. I don't think it has that many watchers but I've removed it to reduce canvassing concerns as far as possible.) Nil Einne (talk) 19:05, 15 November 2018 (UTC)[reply]

      @Nil Einne: Do you mean besides the issues that led to the block and the loss of community trust in the first place? What Tony says below. Oh, Floquenbeam, you say the darnedest things. Besides, with what I've been through this (expletive deleted) week, Karma (expletive deleted) owes me.-- Dlohcierekim (talk) 02:13, 16 November 2018 (UTC)[reply]

      • There’s no local or global policy on this, and it’s handled mainly by convention. The norm is that we don’t rename blocked users unless it’s a new account and there are compelling privacy reasons. I don’t see a reason to deviate from that here. I’d also suggest closing this thread. TonyBallioni (talk) 19:22, 15 November 2018 (UTC)[reply]
      • Sure, why not. Don't unblock but allow a rename. It's good karma to do a favor for someone who doesn't really deserve one. And God knows AN needs all the karma it can get. --Floquenbeam (talk) 19:24, 15 November 2018 (UTC)[reply]
      • Support. If the user's in good standing at another wiki, why get in the way of its processes? Maybe we need to revisit our renaming-while-blocked standard, if they have the effect of impeding editing at other projects. Nyttend (talk) 14:56, 17 November 2018 (UTC)[reply]
      • Just noting they have already withdrawn the rename request on meta ([2]). Also note that while it's not noted in the log, they are blocked by a checkuser for IP socking, have had their unblock declined by a different checkuser for ongoing IP socking, and have two more checkusers in this thread suggesting they not be unblocked given the circumstances. For what it's worth. If they can be renamed in a way that does not involve their being unblocked here, I am not opposed but neither do I support. Ivanvector (Talk/Edits) 15:10, 17 November 2018 (UTC)[reply]
      • Ivanvector, if I understand rightly, the thing from Meta is basically "if you get permission from en:wp, you can be renamed", so this is basically a request for permission, rather than a request for us actively to do something. If I can misquote WP:BAN — what's going on here is a social decision about the right to be renamed, while a block is a technically imposed enforcement setting. [At least that's the understanding by which I supported the request; I'm not supporting a change to the local enforcement setting.] I continue to support the request, since a user's actions on one wiki should never result in sanctions on another wiki where they're behaving fine, unless the situation gets bad enough that a global block/lock/ban is warranted. Should SuperSucker decide to make another Meta request, the request shouldn't have to be put on hold because we haven't granted permission. Nyttend (talk) 17:29, 17 November 2018 (UTC)[reply]
      I'm fine with that. So long as whatever they want to do on the other wiki does not require them being unblocked here, I don't really care. I object to the view of "giving permission": this is a matter of meta policy, and if the admins at meta (or stewards, or whatever) want to make an exception to their policies for this user, that's out of our hands. Ivanvector (Talk/Edits) 18:01, 17 November 2018 (UTC)[reply]
      Yes, the idea that we have to give permission seems rather nutty to me too. Nyttend (talk) 18:58, 17 November 2018 (UTC)[reply]
      • As a global renamer I see no policy-based or common-sense reason for preventing an editor who's in good standing on another project from being able to use the name they want on that project unless the proposed name violates one of our username policies here. That the account is blocked here should have no bearing on the global login they want to use on other projects where they are not blocked. However, as the request has been withdrawn, this particular thread can be closed, which I will do now. 28bytes (talk) 09:19, 22 November 2018 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      Rogue civility sanctions in edit notices; non-admins adding AC/DS sanction templates to talk pages; permission needed to clean up this mess

      In this AN discussion last week we had unanimous consensus to vacate the "civility" sanction on all pages affected by {{American politics AE}}. I made the change to the template and relevant edit notices. I later came across {{Post-1932_American_politics_discretionary_sanctions_page_restrictions}} which is basically a sister template to "American politics AE" but without the civility sanction. Because the sanctions are now identical with only minor differences in the templates themselves, I've started replacing the "Post-1932..." templates with the "American poligics AE" template which has better documentation and a sub-template to use in edit notices. However when I started looking at the corresponding edit notices for the pages affected by the "Post-1932..." template I noticed that some of them made reference to the "civility" sanction. So there was a discrepancy between the talk page notice and the edit notice. I initially assumed the discrepancy was a result of widespread copy-pasting of the edit notice code without paying close attention to the sanctions on the page they were copied from, but the few that I spot checked showed that it was User:Coffee who added the civility restriction (presumably forgetting to update the corresponding template on the talk page). Would there be any objections to me removing these rogue civility sanctions from the edit notices as I find them? ~Awilley (talk) 20:33, 17 November 2018 (UTC)[reply]

      Another problem I'm encountering is that there are a lot of talk pages with DS templates that don't have the required corresponding edit notices. Initially I thought this was because of sloppy admins forgetting to create the edit notices, but it has come to my attention that non-admins have been adding the templates to talkpages. Here are 5 examples of just one user creating talk pages with the DS templates, having copied them from other American Politics talk pages, and apparently thinking they were Wikiproject banners: [3] [4] [5] [6] [7]. I haven't counted, but I would guess that there are about 50 pages that have the template on the talk page but no edit notice. The most straightforward way of correcting the problem would be to simply remove the sanctions templates from pages that don't have an edit notice, but doing that I risk reversing DS placed by an actual admin. That leaves us with the slow method of digging through the talkpage history with the wikiblame tool to track down who placed the notice, and cross-referencing with the last couple of years of AE logs (I don't trust that admins who forgot to create an edit notice always remembered to update the log). That's more work than I'm feeling like doing at the moment. May I just remove the talkpage templates from all the pages that don't have edit notices, and then make a note of those pages in the AE log? ~Awilley (talk) 00:20, 18 November 2018 (UTC)[reply]
      • From my reading of the discussion, it seemed like everyone was pretty much on the same page—deprecating the 'civility restrictions' en masse was mostly viewed as an uncontentious procedural measure, due to the fact that the concept of civility restrictions is redundant, unused, unenforceable, and pointless; effectively, not even a real restriction. I don't think it would be contentious to remove the outstanding civility restrictions as you come across them. The articles with no edit notices are a bit more tricky. The edit notice requirement is fairly new, having only been added this year, so it's likely that you're seeing some older pages that have never been updated, some admin laziness, and some non-admin additions. All the older articles in the logs should probably be reviewed to make sure they have all been updated with the required editnotice, and anything not logged should have any DS notices removed, of course. However, the practical matter of actually making this happen would be so monumental that it's an unrealistic task. So, I would say that yes, your technique is likely the best we're going to get, but rather than removing them outright, leave them be but still make the list and post it in the log, and then we can check them against the log via Ctrl+F. Anything not in the log can be removed, anything in the log can be updated with an edit notice, but it would probably most efficient and easy doing it that way.  Swarm  talk  07:06, 18 November 2018 (UTC)[reply]
      • I think an edit filter should be created to prevent non-admins from adding (or removing) {{American politics AE}} and similar templates, to prevent mistaken additions like that. Galobtter (pingó mió) 11:27, 18 November 2018 (UTC)[reply]
      • An edit filter would be nice. Here's an instance of an IP editor adding the American politics AE template: [8] ~Awilley (talk) 15:29, 18 November 2018 (UTC)[reply]
      • @Winged Blades of Godric: Thank you for working on the filter. Looking at [9] would it not be better to use "{{American politics AE" instead of "{{American politics AE}}" since the template has optional codes like {{American politics AE|consensusrequired=no}}? ~Awilley (talk) 01:40, 25 November 2018 (UTC)[reply]
      • Thanks, that's what I was looking for. It would be nice if the policy said, specifically, "Only administrators can..." blah blah blah. Beyond My Ken (talk) 22:05, 18 November 2018 (UTC)[reply]
      • Beyond My Ken I think this is only talking about notices that impose restrictions, not the notices that are put on the talk page that inform you that the topic is subject to discretionary sanctions. Natureium (talk) 22:22, 18 November 2018 (UTC)[reply]
      • I see. Does that mean that non-admins can place DS notices on articles that clearly fall with a DS area, but that they should also create the necessary edit notice? Beyond My Ken (talk) 22:28, 18 November 2018 (UTC)[reply]
      • I think this really needs to be stated more clearly, but from what I've been able to figure out, I think that the edit notices are for the pages that have DS restrictions imposed. Only admins can impose DS restrictions, and only admins are able to create edit notices. I haven't been able to find anything that states that only admins can place notices stating that an article is in an area subject to DS or that there are edit notices to go with those. Natureium (talk) 22:33, 18 November 2018 (UTC)[reply]
      • OK, I was unaware that only admins could create edit notices (my only experience with them is the one on my user talk page), so if an edit notice is required, and only admins can create them, then only admins can place the DS notice on an article talk page. Still, in terms of what the policy actually says it looks like a gray area which should be tightened up with some explicit language. Beyond My Ken (talk) 22:58, 18 November 2018 (UTC)[reply]
      • On putting sanction templates on talk pages (what was happening here), I don't see that as very gray. It's like a non-admin putting "you have been blocked" templates on the page of a user who is not blocked. The case of non-admins putting informational templates about general topic areas being under general discretionary sanctions, I don't think that's against policy, but I don't know for sure. ~Awilley (talk) 02:39, 19 November 2018 (UTC)[reply]
      • I'm pretty certain that anyone can put an informational template on an editor's user talk page, informing then that an article is under Discretionary Sanctions. The point of such an action is simply to notify the editor, which does not presume any wrongdoing on the editor's part (I believe the template even says that). Beyond My Ken (talk) 04:41, 19 November 2018 (UTC)[reply]
      • There are the talk page notices like the one on Talk:Alternative medicine that inform people that sanctions are possible and then there are talk page notices like the one on Talk:Jared Kushner that start with "WARNING: ACTIVE ARBITRATION REMEDIES" and list restrictions for the page. The latter can only be placed by administrators and I think the Wikipedia:Arbitration Committee/Discretionary sanctions#Page restrictions is clear about that. The former... I don't know and haven't found any where that talks about it. Because you are not imposing any restrictions but rather informing people of the ruling already made by arbcom, I don't see why being an admin should be necessary but it's not really about common sense, now is it? Natureium (talk) 15:33, 19 November 2018 (UTC)[reply]
      • No, I guess not. DS are a very necessary evil, but they're still basically a bureaucratic tool, which means that the ins and outs of them can be complex. The personal lesson I'm drawing from this is simply to stay away from posting informational DS notices on article talk pages even when it's indisputable that the article falls withing the penumbra of an existing DS, and go get someone of a higher pay grade to deal with it. In a way, that should be a relief for non-admins such as myself, since we don't have to shoulder the responsibility of taking that action. My experience is that the vast majority of active admins are reasonable folks who are likely to respond positively to such a request. Beyond My Ken (talk) 19:03, 19 November 2018 (UTC)[reply]
      • (Just to be clear, DS are very necessary, not very evil.) Beyond My Ken (talk) 19:39, 19 November 2018 (UTC)[reply]
      Beyond My Ken, Basically, the edit-notices are located at places whose roots are forbidden by the Title-Blacklist and anybody who does not have the tb-override flag, can't create such pages. Thus, post the recent grant of abilities to Page-Movers to over-ride Title-Blacklist (for completely different issues), currently any Template Editor or Page-Mover or Administrator can install edit-notices at any page.WBGconverse 13:52, 24 November 2018 (UTC)[reply]

      OK, here's a list of edit notices that don't currently exist for articles that have sanctions templates on the talk page.

      1. Template:Editnotices/Page/Andrew Napolitano
      2. Template:Editnotices/Page/Aziz v. Trump
      3. Template:Editnotices/Page/Blumenthal v. Trump
      4. Template:Editnotices/Page/Bob Menendez
      5. Template:Editnotices/Page/CNN v. Trump
      6. Template:Editnotices/Page/CREW v. Trump
      7. Template:Editnotices/Page/Cannabis policy of the Donald Trump administration
      8. Template:Editnotices/Page/Clinton Foundation–State Department controversy
      9. Template:Editnotices/Page/D.C. and Maryland v. Trump
      10. Template:Editnotices/Page/DREAM Act
      11. Template:Editnotices/Page/David Bowdich
      12. Template:Editnotices/Page/Deferred Action for Childhood Arrivals
      13. Template:Editnotices/Page/Dismissal of Sally Yates
      14. Template:Editnotices/Page/Doe v. Trump
      15. Template:Editnotices/Page/Donald Trump Jr.
      16. Template:Editnotices/Page/Donna Brazile
      17. Template:Editnotices/Page/Executive Order 13767
      18. Template:Editnotices/Page/Frank Gaffney
      19. Template:Editnotices/Page/Gary Johnson
      20. Template:Editnotices/Page/Gays for Trump
      21. Template:Editnotices/Page/Jill Stein
      22. Template:Editnotices/Page/Knight First Amendment Institute v. Trump
      23. Template:Editnotices/Page/LGBT protests against Donald Trump
      24. Template:Editnotices/Page/Legal challenges to the Trump travel ban
      25. Template:Editnotices/Page/List of Donald Trump presidential campaign endorsements, 2016
      26. Template:Editnotices/Page/List of Hillary Clinton presidential campaign endorsements, 2016
      27. Template:Editnotices/Page/List of Hillary Clinton presidential campaign non-political endorsements, 2016
      28. Template:Editnotices/Page/List of Hillary Clinton presidential campaign political endorsements, 2016
      29. Template:Editnotices/Page/List of Trump administration dismissals and resignations
      30. Template:Editnotices/Page/List of lawsuits involving Donald Trump
      31. Template:Editnotices/Page/List of people granted executive clemency by Donald Trump
      32. Template:Editnotices/Page/List of proclamations by Donald Trump
      33. Template:Editnotices/Page/Marijuana policy of the Donald Trump administration
      34. Template:Editnotices/Page/Open space accessibility in California
      35. Template:Editnotices/Page/Operation Faithful Patriot
      36. Template:Editnotices/Page/President Trump's immigration bans
      37. Template:Editnotices/Page/Reactions to Executive Order 13769
      38. Template:Editnotices/Page/Reactions to the Special Counsel investigation (2017–present)
      39. Template:Editnotices/Page/Republican Party presidential primaries, 2020
      40. Template:Editnotices/Page/Stone v. Trump
      41. Template:Editnotices/Page/Tim Canova
      42. Template:Editnotices/Page/Tootkaboni v. Trump
      43. Template:Editnotices/Page/Trump Tower meeting
      44. Template:Editnotices/Page/United States Ambassadors appointed by Donald Trump
      45. Template:Editnotices/Page/United States withdrawal from the Paris Agreement
      46. Template:Editnotices/Page/Vladimir Putin
      47. Template:Editnotices/Page/Voter suppression in the United States

      (pats self on back for getting lucky on ballpark estimation of 50) ~Awilley (talk) 15:00, 18 November 2018 (UTC)[reply]

      OK, I've been using the AWB list compare tool to compare the above list of articles to articles that are LINKED from the arbitration enforcement logs back to 2015. Of the 47 pages above, the articles of 44 of them are not linked in the log, and the 3 that are linked (Frank Gaffney, Jill Stein, Vladimir Putin) are links from individual editors being topic banned from the individual articles. Note that I'm only looking at links, not text, so if an admin made a log entry that said "Jill Stein placed under 1RR and Consensus Required" without linking Jill Stein I wouldn't see that. ~Awilley (talk) 15:41, 18 November 2018 (UTC)[reply]
      I've removed the AE templates from the talkpages associated with the nonexistent edit notices above. ~Awilley (talk) 19:17, 19 November 2018 (UTC)[reply]

      Also here's a list of edit notice templates that were created but that didn't have entries that I could find in the AE log. Since these were all created by administrators I will create an entry in the log for the items in this list.

      1. Template:Editnotices/Page//r/The Donald Lord Roem (forgot to log)
      2. Template:Editnotices/Page/2016 Democratic National Committee email leak Coffee (forgot to log)
      3. Template:Editnotices/Page/2016 Democratic National Convention Zzyzx11 (forgot to log)
      4. Template:Editnotices/Page/Devin Nunes Coffee (forgot to log)
      5. Template:Editnotices/Page/Efforts to impeach Donald Trump El C (forgot to log)
      6. Template:Editnotices/Page/Environmental policy of the Donald Trump administration Coffee (forgot to log)
      7. Template:Editnotices/Page/Erik Prince Coffee (forgot to log)
      8. Template:Editnotices/Page/Executive Order 13768 Doug Weller (forgot to log)
      9. Template:Editnotices/Page/Jared KushnerAd Orientum (forgot to log)
      10. Template:Editnotices/Page/List of executive actions by Donald Trump Ad Orientum (forgot to log)
      11. Template:Editnotices/Page/Mike Pence Zzyzx11 (forgot to log)
      12. Template:Editnotices/Page/Results of the Democratic Party presidential primaries, 2016 Coffee (forgot to log)
      13. Template:Editnotices/Page/Results of the Republican Party presidential primaries, 2016 Zzyzx11 (forgot to log)
      14. Template:Editnotices/Page/Roger Stone Coffee (forgot to log)
      15. Template:Editnotices/Page/Stop Trump movement El C (forgot to log)

      ~Awilley (talk) 16:52, 18 November 2018 (UTC)[reply]

      Some of these problems would go away if the AC/DS template had a signature field, so we would know from viewing the article talk page who placed the notice and the date when they did so. EdJohnston (talk) 22:32, 18 November 2018 (UTC)[reply]
      That's a good idea. I'm not sure how to force a signature on a template that is transcluded (as opposed to substituted) but I'll look into it. ~Awilley (talk) 19:17, 19 November 2018 (UTC)[reply]
      @Awilley and EdJohnston:, try substituting Template:ZHYXCBG onto any talk-page and check the result. (Input {{subst:ZHYXCBG}} ) It notes down the signature of the user, (who installs the template), within a comment (which is prepended/appended to the template-code) but the main notice is directly transcluded onto the t/p, as we do now:-)
      See this edit of mine, for an example.WBGconverse 12:58, 24 November 2018 (UTC)[reply]

      Help with heuristics for auto-detecting paid revisions

      Hi admins. I'm doing a little research on automatically detecting paid revisions. Part of my process involve coming up with weak heuristics for determining whether a particular edit is likely to be paid. But since I'm no experienced editor, I don't have a great intuition for developing these heuristics. I'd highly appreciate your help with brainstorming.

      The framework I'm working with (and supporting publication). — Preceding unsigned comment added by Apiarant (talk • contribs) 20:31, 18 November 2018 (UTC)[reply]

      For some related work being done by the WMF, see https://ores.wikimedia.org. My impression is that they are using machine learning to identify edits that might be vandalism. There is a list of people here. EdJohnston (talk) 21:21, 19 November 2018 (UTC)[reply]
      Thanks Ed. I got in contact with the ORES group. A major difference between their work and mine is that I'm interested in whether a particular way of modeling crowd-sourced heuristics can drastically improve models like those that ORES works with. But I'd need less technical help than community help. I'm pretty new to the community here; would you happen to know where I can find admins experienced with or interested in paid edits? Apiarant (talk) 10:38, 20 November 2018 (UTC)[reply]
      Wikipedia talk:Conflict of interest/Noticeboard is probably the best place to find people with an interest in the topic. Per my comment on your initial proposal, I think this proposal is vanishingly unlikely to be accepted, since it will be flagging huge numbers of good-faith editors as potential spammers, which will violate Wikipedia's most fundamental principle of assuming good faith. ‑ Iridescent 10:49, 20 November 2018 (UTC)[reply]
      Thanks a bunch for your help! Indeed, if the method falsely flags too many good-faith editors, it's unacceptable. I'm personally unsure how difficult reducing false positives here might be until I get to the modeling myself. However, I do have faith that with enough time and work, a reasonable job can be done: it doesn't appear that any part of the problem is (under my current understanding) insurmountable. Would you mind sharing what you've seen and why you think the method will over-flag good-faith editors? You might save me a few dozen hours of time! Apiarant (talk) 22:53, 23 November 2018 (UTC)[reply]

      TBAN Appeal

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


      Hi, I am here by requesting appeal against the TBAN which was enforced almost a year ago on me on the all AFDS, so now the minimum time duration of TBAN 3 months have passed reequest and appeal to lift TBAN please. I have read and understood the Wikipedia General Notability Guidelines as well. JogiAsad  Talk 14:24, 19 November 2018 (UTC)[reply]

      The topic ban was imposed in this discussion. It was appealed in this discussion (May 2018), this discussion (September 2018), and this discussion (November 2018). JogiAsad seems to post these "please lift my ban" messages intermittently, then wander off without answering any questions. He did answer a question last time, but he did so by editing the archived discussion after it had been moved to an archive. NinjaRobotPirate (talk) 16:28, 19 November 2018 (UTC)[reply]
      JogiAsad, on 30 September, Galobtter asked you to provide "an explanation of how your understanding of notability has improved so that your behaviour at AfD will be better". You did not respond at that time, and now you are back here with another appeal that again fails to address the problem that led to the topic ban. Your topic ban was imposed on 9 April 2018 so that is nowhere near a year ago. Accuracy is important. What you must do is convince the editors participating here that your understanding of notability has improved and that you will not be disruptive at AfD in the future. Stating that you have read GNG is not enough. Until we hear from you in much greater detail, I oppose lifting the topic ban. Cullen328 Let's discuss it 18:07, 19 November 2018 (UTC)[reply]
      Yup, appeal is obviously inadequate; the repeated appeals without being able to explain himself are further concerning regarding his competence to evaluate sources for notability. Oppose obviously, and suggest a further six month moratorium upon decline of this appeal. JogiAsad please provide that explanation to show that you have "have read and understood the Wikipedia General Notability Guidelines". Galobtter (pingó mió) 18:25, 19 November 2018 (UTC)[reply]
      • Oppose as per the above, and endorse Galobtter's suggestions of a 6 month moratorium on appeals. Beyond My Ken (talk) 19:38, 19 November 2018 (UTC)[reply]
      • After the dialogue in the section below, I maintain this position. The OP does not believe he or she did anything wrong to deserve a TB, and therefore it is impossible for them to assure the community that their future behavior will be different. Beyond My Ken (talk) 18:59, 20 November 2018 (UTC)[reply]
      • Oppose It was my comment that JogiAsad responded to in the Archived post. Their editing is so sporadic that there's no real way of determining that they really do get what they are topic banned for. Furthermore, as has been said, the appeal statement is inadequate. --Blackmane (talk) 05:00, 20 November 2018 (UTC)[reply]
      • Oppose and support moratorium per Galobtter; it's slightly worrying that these appeals keep getting made, and the same questions ignored, with no actual reflection—perhaps even understanding—at all. ——SerialNumber54129 10:51, 20 November 2018 (UTC)[reply]
      • Yes. Unfortunately, if this sanction passes appeal is denied, and the OP comes back after 6 months and appeals without responding to questions, I think the next logical step would be a CIR-based CBAN. Beyond My Ken (talk) 13:23, 20 November 2018 (UTC)[reply]
      • Oppose lifting of the topic ban and support a 6 month moratorium on any further appeals. GiantSnowman 10:52, 20 November 2018 (UTC)[reply]
      • Oppose Editor refuses to engage in timely discussions over his prior behavior, or demonstrate that he intends to change his behavior. Also support the 6-month moratorium on appeals noted above. --Jayron32 13:48, 20 November 2018 (UTC)[reply]
      • Oppose lifting of the topic ban for @JogiAsad:. Period. A bad faith user who still hurling canvassing accusations at me. --Saqib (talk) 23:26, 20 November 2018 (UTC)[reply]
      • Oppose lifting the Tban, and support a 6-month moratorium on appeals. While JogiAsad might have an intermediate linguistic competence in English (that's purely a matter of which grade a certification examiner gives you), their communicative competence is clearly not sufficient for participation in XfD discussions - their statements and responses in this thread make that very clear. On top of that, there is still a refusal to listen, not just an inability to understand, and that has been part of the problem all along. --bonadea contributions talk 11:49, 24 November 2018 (UTC)[reply]

      Response by JogiAsad

      Hi Everyone, I have read all the General Notability Guidelines (GNG), and you may ask me anything about the GNG I would respond. And regarding those who said above comments that I have appealed repeatedly, no I just had replied to the comments and when I was advised to appeal and then I appealed, and I have some personal reasons that I didn't be active all the times. I did replied to the archived due to there was asked me queries during which I was not active/online, and when I managed to be active or online I had no choice but to respond and I am sorry for that If I have replied in the archived discussion. The and this discussion was a misunderstanding the the nominator, which I had not done any spamming and neither I did any on-wiki canvassing or any kind of off-wiki canvassing, all those users voted as per their own. Even if some of the users who are saying that my this appeal is inadequate, sincerely I didn't have any idea how to appeal in a better way. So here I request that this TBAN be lifted as I have understood all the GNG, you may ask me anything about the GNG. Expecting a positive and a dignified role from you and I request arbitration committee to do a justice please. Thank you all...JogiAsad  Talk 17:36, 20 November 2018 (UTC)[reply]

      You have not beeen asked to repeat by rote what you just read, you were asked to provide:
      • "an explanation of how your understanding of notability has improved so that your behaviour at AfD will be better"
      Please do so now. Be certain to focus on your behavior, and how it will change. Beyond My Ken (talk) 17:48, 20 November 2018 (UTC)[reply]
      Beyond My Ken, could you please guide me or provide me the sample how to respond to that query's which you have written in italic. Or should I repeat each and elaborate each words in GNG i.e. what is Reliable, sources, primary or secondary etc?, Here I ensure that I have read and understood all the GNG and I ensure that I have and I will show an improved behavior at afds.JogiAsad  Talk 17:59, 20 November 2018 (UTC)[reply]
      This appears to be drifting into CIR territory. John from Idegon (talk) 18:03, 20 November 2018 (UTC)[reply]
      Yes, the OP appears either not to understand, or not to want to understand that the question is not about his or her knowledge of the notability guidelines, but about how that knowledge will change their behavior. Beyond My Ken (talk) 18:22, 20 November 2018 (UTC)[reply]
      I have an intermediate understanding of English in written, reading and listening, The question was about the GNG not about WP:CIR, If you ask me anything about GNG I would answer.JogiAsad  Talk 18:12, 20 November 2018 (UTC)[reply]
      And despite of assurance by me about GNG and improved behavior at afds, If any user is still Oppose or in favor of TBAn ,Then its making a sense to me that nobody wants me to remain here as a Wikipedian Editor and they wants me to leave Wikipedia forever.JogiAsad  Talk 18:15, 20 November 2018 (UTC)[reply]
      Well nobody has said that as of yet, but you're making a pretty good case for it yourself by your inability or refusal to answer the question put to you. Again, no one wants to quiz you on GNG, what everyone wants to know is this: Now that you think you understand GNG, how will you behave differently? Can you please answer that? Beyond My Ken (talk) 18:22, 20 November 2018 (UTC)[reply]
      The answer is simply yes, I Think that I have understood the WP:GNG after reading it, and I ensure that I'll behave well manner.JogiAsad  Talk 18:26, 20 November 2018 (UTC)[reply]
      JogiAsad please explain what you mean by, "I'll behave well manner." ~ ONUnicorn(Talk|Contribs)problem solving 18:37, 20 November 2018 (UTC)[reply]
      I'll behave well manner, means that I'll follow the GNG guidelines when participating in discussion and I'll try to respond timely as well.JogiAsad  Talk 18:40, 20 November 2018 (UTC)[reply]
      • Let's try again. JogiAsad, why were you topic banned from XfDs? Beyond My Ken (talk) 18:45, 20 November 2018 (UTC)[reply]
      • I was Topic banned because the nominator assumed that I have done any kind of On-wiki canvassing, Which I had not....JogiAsad  Talk 18:48, 20 November 2018 (UTC)[reply]
      • OK, you're off to a bad start. The first step to having your topic ban lifted is to recognize what you did wrong which deserved the TB. If you don't know what was wrong about your previous behavior, there is no way for you to change, and that's what the community is interested in knowing, that your behavior will change.
        I'll stop now, as there's little point in proceeding. I maintain my position as above: no lifting of the topic ban, and a moratorium on appeals for 6 months. Beyond My Ken (talk) 18:56, 20 November 2018 (UTC)[reply]
      I understand why was topic ban, but how can I recognize, I didn't any wrong neither I had done any canvassing, but If you look at User:Saqib canvassed onwiki-canvassing by asking an admin to participate in the discussion, I have ensured that I have not did any wrong or any type of Canvassing, If I have not did any wrong or Canvassing, why should I recognize such activity which I have not done.JogiAsad  Talk 19:13, 20 November 2018 (UTC)[reply]

      Idea

      It seems JogiAsad is having trouble articulating what he would do differently in AFDs were the topic ban to be lifted. Does anyone think it would help if, for a period of time (let's say one month), JogiAsad keep a sandbox in user-space where he links to some current AFDs and writes (on the sandbox page - not on the AFD itself) what he would write if there were no topic ban? That way we can better judge if his understanding of GNG and his discussion rationales have improved. Then he can come back here and we can try this again with something more concrete to go on. ~ ONUnicorn(Talk|Contribs)problem solving 19:08, 20 November 2018 (UTC)[reply]

      I'd be more interested in knowing why JogiAsad wants so badly to be able to edit at XfD. Is there some problem that they are seeing that only they can fix? Maybe it's my own relative disinterest in XfD, but it seems to me that a ban from XfD is one that would be very easy to endure. Why is JogiAsad so determined to delete articles? Beyond My Ken (talk) 19:19, 20 November 2018 (UTC)[reply]
      I am not determined to delete any article.JogiAsad  Talk 19:23, 20 November 2018 (UTC)[reply]
      Then are you determined to save some kinds of articles? Why is editing at XfD important to you? Beyond My Ken (talk) 19:25, 20 November 2018 (UTC)[reply]
      I am also not determined to save any article if it does not meet the criteria of GNG.JogiAsad  Talk 19:29, 20 November 2018 (UTC)[reply]
      • I was keeping this question for a later time, glad to see Beyond My Ken asked already. But User:JogiAsad has either not understood the question properly or decided not to answer it. If there is nothing that you want to delete or save, then please explain why it is so important for you to contribute at AfD ? Are there any problems you are facing with this BAN ? XfD contributors should have enough language competence to be able to review multiple sources and understand the policy and guidelines. --DBigXray 19:43, 20 November 2018 (UTC)[reply]
      There is no problem but If the time period of TBAN is passed and I am appealing with ensuring that I have read and understood the GNG and I ensure that I would be politely and will not vote for any save or delete article afds until that article don't meet the criteria of GNG. so why still this ban is lingering over me.JogiAsad  Talk 19:58, 20 November 2018 (UTC)[reply]
      Sorry, as to ONUnicorn's suggestion: I doubt it would be of much use, since the majority of problems at XfD have to do with interactions with other editors and behavior related to it, so a "dry run" sandbox just wouldn't be the equivalent, in my opinion. If they were TB'd because of canvassing, why would they be tempted to canvass to a sandbox, since nothing is at stake? Beyond My Ken (talk) 19:25, 20 November 2018 (UTC)[reply]
      And Here I say that I have not canvassed in any way neither I did any on-wiki canvassing nor I did it through any type of Sandbox, try to understand my point of view that I didn't canvassed neither I determined to save or delete any article unless it meets the criteria of GNG.JogiAsad  Talk 19:33, 20 November 2018 (UTC)[reply]
      • User:ONUnicorn, nice idea but oppose this idea for now. May be we can do this exercise to gauge his understanding, the next time JogiAsad comes up with a decent appeal. --DBigXray 19:43, 20 November 2018 (UTC)[reply]
      Can you please guide me how to appeal decently, is there any sample of previous appeals which I could read and get an idea how to appeal decently?, And please put some light on which type of understanding you intends to gauge?.Thanks..JogiAsad  Talk 19:49, 20 November 2018 (UTC)[reply]
      Can you answer this Question I added above ?--DBigXray 20:00, 20 November 2018 (UTC)[reply]
      I have answered please read...JogiAsad  Talk 20:02, 20 November 2018 (UTC)[reply]
      So based on your answer, it seems it is not important for you to participate at AfD, then I see no pressing reason to remove the ban. This ban was an indefinite ban, and it will continue to linger because the community feels that your answers and understanding of Questions are not sufficient in convincing them to lift this ban, at this time. So just wait some more and contribute in other areas where you are not banned for now. --DBigXray 20:05, 20 November 2018 (UTC)[reply]
      The Ban was for 3 months which have passed, and I have tried to convince and assure that I have read and understood the GNG and will participate politely as well.JogiAsad  Talk 20:43, 20 November 2018 (UTC)[reply]
      JogiAsad, with all due respect, you have been given a great deal of guidance in how to "appeal decently", but it appears that you are unable to follow that guidance. I can't help but think that your somewhat weak command of English is part of the problem (you call it "intermediate, but I would judge it to be less than that). In my opinion, judging from this discussion, your English language abilities are not sufficient for you to be editing or creating articles on English Wikipedia, or to be participating in XfD at all. I note that you are a sysop at Sindhi Wikipedia, where you have twice as many edits as you have here, and yet en.wiki is marked as your home wiki. I think this is a problem. Writing an English-language encyclopedia requires a high level of English language competency, which you do not seem to have. There are still many things you can do to contribute here which don't require such skills, but I'm afraid that with your current ability with English, writing and editing articles and participating in XfDs is simply not one of them. I know this is a harsh appraisal, but it is the situation as I see it, and I think you're going to be caught in this loop for a long time, and perhaps eventually be site banned from en.wiki, if you don't recognize it and adjust your expectations accordingly. Beyond My Ken (talk) 20:12, 20 November 2018 (UTC)[reply]
      All that you asked I responded in well manners, you asked me "Now that you think you understand GNG, how will you behave differently?", I answered I have understood the GNG after reading it, and I have also ensured that I am not in favor of any save or delete any article until it doesn't meet the GNG Criteria. are these not sufficient answers? so satisfy your query?. And regarding my English language command I have appeared in the Competitive Examinations of Pakistan CSS and I also write in newspapers and blogs as well, English Wikipedia is my home wiki because its where I had started my journey as a Wikipedian in July 2011, and since then I have contributed in enwiki. English language is not a problem, almost all over the world people read, speak and talk in English even if its not their native language, so sorry to say your judging and appraisal is not 100 percent precise. If you people are stubborn and insist on embargo, then its very disappointing for a sincere contributor. JogiAsad  Talk 20:43, 20 November 2018 (UTC)[reply]
      No, I'm sorry to say, my judging is quite correct, and the paragraph above is an excellent example of the problem: you don't know English as well as you think you know English, I'm afraid. I salute you on the ability to speak another language to the extent you do, it's one that I don't share, but the harsh fact is that it's just not enough to be working on articles here. Beyond My Ken (talk) 21:08, 20 November 2018 (UTC)[reply]
      No your judging and appraisal is not correct dear, and you are neither here certificate issuer nor here is the test of English competency, So please avoid personal statements.JogiAsad  Talk 21:17, 20 November 2018 (UTC)[reply]
      Again, you provide us all with an example which verifies my estimation. You might wish to read First Law of Holes, because you're not doing yourself any good. And, BTW, don't call me, or anyone else that you do not know very well, "dear". Beyond My Ken (talk) 21:22, 20 November 2018 (UTC)[reply]
      Okay I take back that word and dear word be omitted, and thanks for sharing the First law of holes.JogiAsad  Talk 21:33, 20 November 2018 (UTC)[reply]
      Beyond My Ken, AFAIK, home-wiki is nothing but the wiki, wherein the account was first registered. Many editors do register in en.wiki (courtesy it's prominence), then move to own-language-wikis, once aware of it.WBGconverse 20:49, 20 November 2018 (UTC)[reply]
      WBG, Thanks for elaborating it .JogiAsad  Talk 21:01, 20 November 2018 (UTC)[reply]
      Mine as well. I also understand that the prominence and influence of en.wiki is why many other-languaged editors wish to edit here, but sometimes that unfortunately gives rise to situations such as what this seems to me to be. Beyond My Ken (talk) 21:03, 20 November 2018 (UTC)[reply]
      After reading this lengthy exchange, I want to reiterate my opposition to lifting the topic ban. JogiAsad, congratulations on performing well on your English proficiency exams in Pakistan. You definitely speak English far better than I speak Urdu or any other language. But I am sorry to have to say that you are not fully fluent in written English. You have made quite a few English mistakes in this conversation, but that would not be a problem if you had given fully responsive answers to the questions you have been asked. If you had, minor errors in grammar and phrasing could be excused. But you have failed to convince me that you fully understand the question and your answer seems pro forma to me, and unresponsive and inadequate in the final analysis. Cullen328 Let's discuss it 01:33, 21 November 2018 (UTC)[reply]
      Cullen328 Thanks for drawing my attention towards my English fluency in written, may be I am not fluent in written English and thanks for excusing my minor errors in grammar and phrasing but I have tried my best to answer the queries which were asked here, and I'll also try me best to convince you and respond to your queries in better and concise way.JogiAsad  Talk 09:47, 21 November 2018 (UTC)[reply]
      @JogiAsad: I have had to work with a very large number of people in real life who do not speak English as a native language: as such, I'm familiar with the issues involved. I'm afraid I agree with what others have written above: your English is not quite good enough for us to remove this topic ban. Part of why I say this is that you still seem to believe that your ban was a temporary one, that would be lifted in three months if you did not misbehave. That just isn't true. Your ban was indefinite; it will remain until you can show us it is not required. To do that, you have to explain what was wrong with your behavior in the first place; and despite a number of requests above, you have not done so. It's not that you've been rude, or that you've behaved badly; it's that you haven't understood what's being asked of you. In fact your request for a "sample" is a part of the problem: if you need to copy a "sample" to be able to provide an answer that's satisfying, it's clear you haven't understood the question in the first place. This isn't an English language exam: it's a place where we need to be able to communicate clearly, and you're not able to do so. This isn't a moral failing on your part, but it seems fairly clear you are not able to understand the complexities of discussions on the English Wikipedia, and you shouldn't participate in them until you do. In fact I'm hesitant to even suggest you should stick to working on articles, but at the moment I'm okay with that. I would suggest that this appeal be declined, and that you do not appeal again for a few months, because people are going to lose patience with you if you keep doing so. Vanamonde (talk) 16:23, 21 November 2018 (UTC)[reply]
      Also: while I applaud ONUnicorn for their abundance of good faith, I cannot support their proposal unless and until we have a set of editors willing to take on the role of mentoring JogiAsad through the XfD process. It's not a responsibility I'm willing to take on; I cannot inflict it on someone else unless they're explicitly stepping forward to take it on. Vanamonde (talk) 16:25, 21 November 2018 (UTC)[reply]
      First of all let me clarify that I have never ever been rude, neither I am rude nor I can think so and I have never misbehaved, I am always remained polite. Initially it was stated that TBAN is for 3 months after that can be appealed so I appealed here after some users advised me to do so, My behavior in the first place was not rude never I intends to be rude. I have ensured that I have read and understood GNG and I'll never be rude neither I have been rude ever nor I intends to be. And if you perceive that this appeal be declined and I shouldn't appeal for a few months, then its Okay I shall keep patience, do so what you think is right at the moment and also let me know how much time (months) I shouldn't appeal and I know there is also Wikipedia Teahouse where some senior Users teach and mentor.JogiAsad  Talk 18:15, 21 November 2018 (UTC)[reply]
      @JogiAsad: Do you have any plans to go to deletion review for Iqbal Jogi and Amb Jogi? --Saqib (talk) 07:27, 22 November 2018 (UTC)[reply]
      Here as well. I can't unravel this at all. Beyond My Ken (talk) 04:05, 26 November 2018 (UTC)[reply]

      Deletion Review

      A question was asked of JogiAsad in the previous section, if they intended to go to Deletion Review about two deleted articles. I have a question for admins: since JogiAsad is topic banned from XfDs, and since Deletion Review is a place where XfDs are discussed, does JogiAsad's topic ban preclude them from participating at Deletion Review? My inclination is to say that it does, because topic bans are generally held to hold anywhere on Wikipedia. Thoughts? Beyond My Ken (talk) 22:46, 22 November 2018 (UTC)[reply]

      "JogiAsad is indefinitely topic banned from all deletion discussions (known on en.wiki as "XfD"). This editing restriction may be appealed after three months of the closure date. Clarification: the topic ban includes all deletion discussions, including deletions for review and requests for deletion."—WP:RESTRICT. NinjaRobotPirate (talk) 20:22, 23 November 2018 (UTC)[reply]
      Thanks. Mea culpa, I should have checked the original ban notice. Beyond My Ken (talk) 22:28, 23 November 2018 (UTC)[reply]
      Template:Tg Thanks for elaborating it, And what is closure date?JogiAsad  Talk 07:49, 24 November 2018 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      Appeal my 1RR restriction

      About 2+12 years ago, following my successful appeal here against a community ban, I had three restrictions applied as conditions of the lifting of that ban: a topic ban from units of measurement, 1RR on the rest of Wikipedia and being limited to one account and prohibited from editing whilst logged-off. About 17 months ago I successfully appealed the general 1RR restriction and about 14 months ago successfully appealed to get my topic ban on measurement converted to a 1RR restriction.

      Today I am appealing to get that 14-month-old 1RR restriction lifted please. I have, to the best of my knowledge, never contravened that restriction - having made around 3000 edits in that time - generally turning to discussion rather than continually reverting. And to be honest, I plan to continue keeping reverts to the minimum and using the discussion route to improve articles - I have found discussion to be more productive, resulting in a more stable article than is achieved with continuous flip-flopping of content.

      The main reason for my appeal is to continue along the path back to full good standing within the community. Please give this appeal your full and careful consideration. Thanks. -- DeFacto (talk). 20:05, 20 November 2018 (UTC)[reply]

      @DeFacto: While in theory I would usually support such a request, please would you explain this sequence of edits from just a month ago and explain how they do not breach 1RR: [10], [11], [12]. Thanks. Fish+Karate 13:42, 22 November 2018 (UTC)[reply]
      Also these two: [13], [14] Fish+Karate 13:44, 22 November 2018 (UTC) My error. Fish+Karate 14:35, 22 November 2018 (UTC)[reply]
      Hi Fish and karate, my 1RR only applies to units of measurement related stuff, I am completely unrestricted (other than by the general 3RR, etc.) on the rest of Wikipedia. I hope that answers your concerns. -- DeFacto (talk). 14:21, 22 November 2018 (UTC)[reply]
      Hi, it does, I realised this and just edit-conflicted with you trying to correct myself, apologies, I do see these sets of reversions aren't related to units of measurement. In that case I have no objection to lifting the restriction, with the usual caveat about backsliding into old habits will be viewed dimly. Fish+Karate 14:34, 22 November 2018 (UTC)[reply]
      • Support - A hallmark example of a community banned user successfully returning to the project. Ben · Salvidrim!  19:59, 23 November 2018 (UTC)[reply]
      • Support this seems likely to be non-controversial; from a quick review this is a constructive editor. power~enwiki (π, ν) 02:25, 24 November 2018 (UTC)[reply]
        Can we get a close for this, please, it seems uncontroversial (which is probably why it hasn't had many contributors). I'd do it but I've already posted just up there ^^ Thanks. Fish+Karate 09:30, 26 November 2018 (UTC)[reply]

      User Lurking Shadow blanking entire important articles on grounds that they "were created by a copyright violator"

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


      I am a content creator, I don't pay much attention to administrative goings-on and I was shocked this morning to find that an article I re-wrote and have maintained for years, Persecution of Christians in the Roman Empire had all its content removed, completely blanked and replaced by a notice that it was up for speedy deletion -edit summary 'delete|per Wikipedia:Contributor copyright investigations/20100114 and WP:copyright violations#Addressing contributors; created by copyright violator'. This is an important article that gets up to 1000 views a day and is linked to on many other pages. Blanking it is very very disruptive, I would call it vandalism.So when I look at that page Contributor copyright investigations/20100114 I see diffs from when the article was created back in 2007, apparently by an editor suspected (?) of copyvios. I left a note on the talk page of the article saying that the article has been completely re-written since then,Lurking shadow, who blanked the article, says it doesn't matter, it has to be deleted anyway. No evidence has been supplied that the article currently contains any copyvios or that it ever contained any copy vios, just that the article was created eleven years ago by someone who somebody else put on a list of "copyright violators" although that editor wasn't blocked for such activities. Lurking shadow did the same thing with Criticism of the Catholic Church , Catholic Church and Nazi Germany, Heresy in Christianity,History of the Eastern Orthodox Church,History of Christian theology, Catholic Church and slavery, History of the Russian Orthodox Church , and Catholic Church sex abuse cases in the United States, without supplying any evidence whatsoever that the articles contain copyvios, only that they were created by supposed "copyright violator"s and has made it clear that this is only the start of a campaign to delete thousands upon thousands of articles. I restored all the articles. If there are copyvios in these articles, they should be identified and re-written or removed, not have the whole article blanked because all versions are "tainted" by being created by a "copyright violator" (also asserted with no evidence). This must stop now.Smeat75 (talk) 20:22, 20 November 2018 (UTC)[reply]

      I have placed a comment on Lurking Shadow's talk page: with 175 edits to the project, they're not in any way qualified to be deleting huge chunks of articles based on the vague possibility of copyvio contamination. I have strongly suggested that they stop, and report their concerns to admins and experienced editors who work in the copyvio area. Beyond My Ken (talk) 20:32, 20 November 2018 (UTC)[reply]
      Although there is a campaign to delete thousands and thousands of articles(in a RFC), these articles were merely a test on how long such a process needs. I will not continue such things until conclusion of the RFC(and then there will be likely a more drastic measure taken).
      But these deletions are actually not vandalism at all. They are based on policy. Addressing contributors allows everyone to assume that all contributions by repeat copyright violators are copyright violations(because there is no trust that they are not, and a pattern of violations. It allows full removal of any and all content needed to be removed to fully heal the copyright violations if the community is unable to examine these suspected cases in detail.
      As there is a backlog of over 80000 contributions to be checked(these were from 2010), this is obviously the case. Unfortunately, this old backlog necessiates the deletion of thousands of pages, maybe even nearly all 80000 pages - some with thousands of versions - but the exact method is something I won't do on my own anyways.Lurking shadow (talk) 20:42, 20 November 2018 (UTC)[reply]
      I'm sorry, someone who doesn't even know how to properly indent their comments is just not the best person to be blanking articles because of copyvios. I suggest that if Lurking shadow returns to this behavior they be temporarily blocked until they agree to stop. Beyond My Ken (talk) 21:10, 20 November 2018 (UTC)[reply]
      I have asked on the talk page of CCI that an admin or editor experienced in copyright violations comment on this thread. Beyond My Ken (talk) 21:13, 20 November 2018 (UTC)[reply]
      The basis of these page blankings is highly suspect imo "all versions are tainted because the article was created by a copyright violator." User:Pseudo-Richard created Persecution of Christians in the Roman Empire and look at that editor's block log, he was never blocked for copyvios or anything else. On what basis is he labelled a "copyright violator"? Certainly not a reason to insist that an important article be deleted.Smeat75 (talk) 21:19, 20 November 2018 (UTC)[reply]
      Derivative work is an issue with articles that once were copyright violations. If an article gets to the present state through incremental editing of a previous copyright violating version, then it could be considered a derivative work and thus a copyright violation itself even if it's fairly different. If at some point someone decided to throw out the old article content wholesale and to write their own version (as I did on Coropuna here, notice the odd mismatch between my first edit - which was on a sandbox version - and the preceding edit - which was on the overwritten page) or if the current version is totally, completely distinct, then it may not be a problem. Does it apply in this case? Jo-Jo Eumerus (talk, contributions) 21:22, 20 November 2018 (UTC)[reply]
      Another question is whether the presumptive removal of suspected copyright violations is appropriate in this situation. Sometimes it is. Is that the case for this copyright violator? Jo-Jo Eumerus (talk, contributions) 21:22, 20 November 2018 (UTC)[reply]
      As I said in the comment previous to yours, where is the evidence that User:Pseudo-Richard, the creator of these articles that were blanked today, is a "copyright violator" at all? He was never blocked, there are no warnings on his talk page about copyvios (although he might have removed them of course). Somebody decided to list his articles on WP:CCI "Wikipedia:Contributor copyright investigations/20100114" Open investigations seven years ago, that's the only evidence I can see. An investigation is not proof.Smeat75 (talk) 21:40, 20 November 2018 (UTC)[reply]
      Yes. Examine this section.Lurking shadow (talk) 21:42, 20 November 2018 (UTC)[reply]
      In Wikipedia:Contributor copyright investigations/20100114 a substantial part of the reviewed contributions were identified as copyright violations. The answer is yes(This is the oldest case still open(from 2010) so part of the work was already done(although more than hundred pages remain).Lurking shadow (talk) 21:29, 20 November 2018 (UTC)[reply]

      If a page has been up for 10 years it is going to be tough to prove copyvio. Wikipedia gets copied all over the place so many hits will be copied from here. Lurking shadow seems ill prepared for dealing with such a difficult area of editing so early. Legacypac (talk) 21:50, 20 November 2018 (UTC)[reply]

      But that's literally the point - there is already evidence that the contributions could be copyright violations(because the contributor made many copyvios) and this means that you need to prove that every of their contributions to the page is not a copyright violation.Lurking shadow (talk) 21:53, 20 November 2018 (UTC)[reply]
      • I've taken a look at Persecution of Christians in the Roman Empire, created by Pseudo-Richard. If someone has a substantial record of copyright violations then policy does permit us to deem their other contributions as copyvio even if we haven't got hard evidence of that (which for edits of this age is going to be difficult anyway). The editor in question here does have a significant copyvio record, even though they weren't blocked for it (they were desysopped).
        However Lurking shadow is taking this rather too far in blanking the entire article. Policy only allows you to blank Pseudo-Richard's contributions to the article, not the article itself. Although Pseudo-Richard did create the article originally the edit summary indicates he merely copied the text from another page. Some of his additions do smell rather strongly of copyvio, e.g. [15], and [16] also appears here (which claims to predate Wikipedia's existence). However this text appears to have been edited out of existence in the intervening decade, so it can't be used as a reason to blank the article now. I am aware of one important case in which we did pre-emptively blank all pages contributed by someone with massive copyright problems, but that was a very different situation and it isn't general practice at all. I suggest that Lurking shadow stop blanking these pages unless s/he can get consensus for it somewhere. Hut 8.5 21:56, 20 November 2018 (UTC)[reply]
      "However this text appears to have been edited out of existence in the intervening decade, so it can't be used as a reason to blank the article now" Thats not actually the case. See Jo-Jo's explanation above. Even if the original text has been removed, if it was a copyright violation, the incremental editing over time taints all subsequent versions unless there is a very sharp cutoff. Only in death does duty end (talk) 22:09, 20 November 2018 (UTC)[reply]
      If the intervening edits are enough to effectively constitute a rewrite of the content then it's a rewrite and not a derivative work. Hut 8.5 22:14, 20 November 2018 (UTC)[reply]
      Only if done in a short enough timespan that rev-deletion of the affected content is feasible. Given you said 'in the intervening decade' that is way beyond the span of time where that is possible. (in the event the original content was a copyvio). Only in death does duty end (talk) 22:29, 20 November 2018 (UTC)[reply]
      Yes, there may well be some copyvio revisions in the history and it wouldn't be practical to revdel those, but that's not a big deal. Provided the current version is clean we can leave those if necessary. We certainly wouldn't delete an article just because the edit history has too many copyvio revisions to revdel. Hut 8.5 22:37, 20 November 2018 (UTC)[reply]
      These revisions are copyright violations - they can not just be left alone, they have to be deleted(and that's not possible without making further copyright violations. The result is the deletion of the entire article(or, in one case of these, the revert to the version before copyvio("reverted to version X by Y") and the revision deletion of every edit in between)Lurking shadow (talk) 23:24, 20 November 2018 (UTC)[reply]
      You are not listening to what people are saying here, you do not get to pronounce that important articles "have to be deleted". If you do not drop this I think you should be blocked.Smeat75 (talk) 23:42, 20 November 2018 (UTC)[reply]
      I am listening. Did you see me undoing your edits or writing new speedy deletion requests?Lurking shadow (talk) 00:34, 21 November 2018 (UTC)[reply]
      • A useful piece of information in all this would be Lurking shadow's previous edit history under whatever other accounts they've used before. The odds that this meets WP:SOCK#LEGIT hovers around 10%. --Floquenbeam (talk) 21:57, 20 November 2018 (UTC)[reply]
        I am actually not a sock. I edited under IP for a long time(and not only here), then made this account. Shortly after, for reasons I will not disclose here, I stopped editing, mostly. Until - now.Lurking shadow (talk) 22:06, 20 November 2018 (UTC)[reply]

      1268 edits by scores of different editors suggests what exists today is incrimental creation. Legacypac (talk) 22:01, 20 November 2018 (UTC)[reply]

      • The people commenting here are all long-term experienced editors, so you can assume that they've read this relatively short thread before commenting here. Jo-Jo Eumerus's opinion is certainly to be given weight, but so are those of the others commenting. What you should be taking away from this is that dealing with copyright violations on Wikipedia is not as cut-and-dried as you appear to believe it is, it's a complicated thing because of the way our cumulative copyright works. And please note that even Jo-Jo Eumerus has not said that your blankings were justified - they were certainly made without due consideration for the overall status of the article. The long and the short of it is, you are simply not qualified to be making those blankings. Beyond My Ken (talk) 23:24, 20 November 2018 (UTC)[reply]
      I actually considered that all the full deletions were subject to tens of big edits by the copyright violator. Yes, copyright is complicated, but these deletion cases are cut-and dried: A repeat violator edited them in a manner that could violate copyright, I am allowed to assume that they made copyvios, revision deleting copyvios isn't possible but necessary(versions are distinct articles and copyrighted versions need to be removed, obviously; but revision delete creates further copyvios), which means total deletion.Lurking shadow (talk) 23:32, 20 November 2018 (UTC)[reply]
      I am allowed to assume that they made copyvios - says who?Smeat75 (talk) 00:00, 21 November 2018 (UTC)[reply]
      Lurking shadow can take the fact that an article has been created or edited in a major way by a person suspected of serial copyright violations as a reason to investigate those edits, or, better still, to report the articles to CCI, where people competent in copyright can examine it, but Lurking shadow cannot simply blank an entire article and the contributions of all the non-violating editors who contributed to it on the mere assumption that there must be copyright violations in it. I know of nothing in policy that supports that contention. If Lurking shadow has a policy to cite to back up their statement, I think everyone here would like to see it. Beyond My Ken (talk) 00:09, 21 November 2018 (UTC)[reply]
      WP:Copyright violations#Addressing Contributors;Wikipedia:Contributor copyright investigations#Accepted Cases(Sentence 4);WP:CRD(criteria for revision deletion, not possible)Lurking shadow (talk) 00:34, 21 November 2018 (UTC)[reply]
      Wikipedia:Contributor copyright investigations#Accepted Cases is not a policy, it is an instructional page for dealing with the CCI process. It is addressed to editors who presumably have sufficient judgment to be part of such an investigation. Sentence 4 does say:
      • If contributors have been proven to have a history of extensive copyright violation, it may be assumed without further evidence that all of their major contributions are copyright violations, and thus removed indiscriminately, in accordance with Wikipedia:Copyright violations.
      But it is immediately followed by sentence 5:
      • If such indiscriminate removal would be controversial or cause considerable collateral damage, an effort must be made to assemble a volunteer force sufficient to evaluate problematic contributions.
      The fact that we are here at AN is a pretty good indication that your removals have been deemed "controversial". Your judgment in these matters is being questioned and found wanting. Beyond My Ken (talk) 00:48, 21 November 2018 (UTC)[reply]
      and then it is followed by sentence 6: If insufficient volunteers are available to manage clean-up, presumptive wholesale removal is allowed. The current state of WP:CCI is very good evidence that this is the case. There are not enough volunteers to manage it. Yes, the removals are controversial. But no, the volunteers are simply missing since 2010.Lurking shadow (talk) 06:58, 21 November 2018 (UTC)[reply]
      Lurking shadow, I must point out again that you don't know how to indent your comments correctly: any response to a comment should have one more indent that the comment itself. (I fixed yours above.) This is a totally trivial matter, but I point it out because it's a clear indication that you're trying to fly a commercial jet liner when you've only just learned how to walk, and haven't quite tackled running. Again: dealing with copyright violations is, at this time, well above your pay grade (mine too, for that matter), and you should not be blundering around in it. WP:BOLD has limits, and you have hit one of them. Beyond My Ken (talk) 23:39, 20 November 2018 (UTC)[reply]
      Also, please note that the standard in written English is to put a space between the end of a word and the open parentheses mark which follows it. You constantly write "word(like this)" when it should be "word (like this)". As to what you are "allowed" to do -- the bottom line is that you are not allowed to disrupt Wikipedia, which is what you are doing. Beyond My Ken (talk) 23:43, 20 November 2018 (UTC)[reply]
      • What is your point about "derivative work"? A derivative work generally creates a new copyright for parts of a work that were not in the original.[17] The copyright is then held by the creator of the derivative work, and if the derivative work is created on Wikipedia it is under a free licence. -- Alanscottwalker (talk) 23:37, 20 November 2018 (UTC)[reply]
      • Question. User:Lurking shadow are you going to stay away from copyvio voluntarily or should we be formalizing a topic ban for you? Legacypac (talk) 06:07, 21 November 2018 (UTC)[reply]
        I will certainly not continue any mass deletion(or something like that)of copyvios unless it is being agreed upon(which I currently do not see here, there is significant opposition). I am reading what you say(did you see me continuing mass deletion?). What I'm trying to do here is to convince you that I'm right.Lurking shadow (talk) 06:51, 21 November 2018 (UTC)[reply]
      • That's not responsive to the question. Again, will you voluntarily stay away from anything dealing with copyright violations? If not, then someone here is almost certainly going to craft a proposal that you be forced to stay away from it by a community topic ban. Beyond My Ken (talk) 14:17, 21 November 2018 (UTC)[reply]
      I'm writing as someone active in copyright who still manages to get yelled at. We have too few volunteers willing to work on this largely in this area, so I have mixed emotions when I see someone interested in helping yet stumbling a bit. I'd like to make an observation which will lead to a suggestion.

      Copyright review is hard. While some investigations are almost mindlessly easy, that's a trap, as some others look almost identical yet turn out to be reverse copyvios, or properly licensed (with a proper license on an obscure sub page) or other minefields. There are three main areas in which volunteers can work:

      These are roughly listed and increasing orders of difficulty, for the simple fact that copy patrol deals with very recent (last day or two) edits, copyright problems deals with older edits, and CCI deals with edits that might be many years in the past. The main problem with age is the proliferation of Wikipedia mirrors, and the tendency of some lazy writers to create content by copying from Wikipedia. The Wayback machine helps, but is sketchier on older information.

      I suggest that an editor with very little copyright experience should not start with the toughest of problems with the easiest of problems. It would make some more sense for @Lurking shadow: to start there for several reasons:

      1. these are the easiest to evaluate (but I'll emphasize the scale doesn't run from easy to hard, it runs from hard to hair pulling)
      2. the tool makes it easy for experience copyright review is to monitor the actions of others
      3. mistakes can be easily rectified and are somewhat less significant (accidentally removing a two day old article is a little less upsetting than removing a 10-year-old article; both require fixing but if fewer ruffle feathers)

      I can't speak for @Diannaa:, but I hope that she would agree, along with myself, to monitor some of the decisions and provide counsel. I do say this with some trepidation, because I take on board the comment by @Beyond My Ken: that someone who doesn't know how to indent on the talk page is raising some red flags, but my hope is that understanding wiki markup and understanding copyright are very different skills.--S Philbrick(Talk) 14:27, 21 November 2018 (UTC)[reply]

      For my part, if someone with a strong copyvio background would volunteer to mentor Lurking shadow in copyright matters, and if Lurking shadow would voluntarily agree not to make copyvio-related edits except as approved by that mentor (with the exception of talk page comments), until the mentor agrees that LS is ready to go it alone, then a formal topic ban may not be necessary. Beyond My Ken (talk) 14:34, 21 November 2018 (UTC)[reply]
      Why?
      I blanked and tagged a few articles for deletion that happened to be made by a copyright violator. I assumed that WP:CCI and WP:Copyright would allow that, and that it was necessary(and I still think it is). Someone complained, and we talked about it.

      I continued to defend what I did until the matter landed here. There are comments in this discussion that some of these articles might really have to be removed, although more people argued against. It is a mere disagreement - nothing more. Lurking shadow (talk) 14:55, 21 November 2018 (UTC)[reply]

      Lurking shadow, The CCI page clearly states that blanking is permitted if there aren't enough volunteers to address it as clean up. I think reasonable people can disagree whether that situation applies, but I think it's clearly a good faith assumption, given the volume of old CCI's, that we are short of volunteers to do the cleanup. I think this is merely a matter of disagreement not a fundamental misreading of the instructions. That said, I put some time into a good-faith proposal which deserves a response.--S Philbrick(Talk) 15:03, 21 November 2018 (UTC)[reply]
      Hi Lurking shadow. User:Sphilbrick pinged me to comment here. I noticed yesterday your report at WP:CP about Health in Rwanda, which you noticed had a lot of overlap with this page. Have a closer look at the page: it's a copy of the Wikipedia article on Rwanda - it's got section headers, notes, references, external links - what to me are obvious hallmarks of what we call a Wikipedia mirror. In other words, the Wikipedia article Rwanda is the source of some of the content in Health in Rwanda. This type of error is not helpful; in fact it generates work for other users. I do wish more people would help with copyright cleanup, but I don't think you have the experience or skills at present to do the work effectively, and I don't have time to assist you. My opinion is that you need to find a different way to contribute please, unless there's someone who has time to mentor you for this extremely complex and time consuming task. Blanking or deleting articles is not a good solution, because it does more harm than good. — Diannaa 🍁 (talk) 15:10, 21 November 2018 (UTC)[reply]
      Sorry for that. I know that content from Wikipedia can also be copied somewhere else, but I erroneously skipped the part with the import and just assumed that the contribution had been made in 2018 - an error I will strive not to repeat.Lurking shadow (talk) 15:23, 21 November 2018 (UTC)[reply]
      Thank you for the helpful comments User:Sphilbrick and Diannaa. I hope User:Lurking shadow will heed them. On the talk page of Wikipedia:Contributor copyright investigations [18] Lurking Shadow has declared that he is on a mission to delete every article that was ever edited by any of the "copyright violators" on the main page, some 80,0000 articles. He doesn't think that would be any big deal [19] The deletion of 80000 articles is not the end of the world. He caused a lot of disruption yesterday and must stop before causing any more.Smeat75 (talk) 15:29, 21 November 2018 (UTC)[reply]
      I agree. — Diannaa 🍁 (talk) 15:32, 21 November 2018 (UTC)[reply]

      Proposal

      In the absence of any positive response from Lurking shadow:

      Lurking shadow is indefinitely topic banned from making any edits anywhere on Wikipedia in regard to copyright violations, with the exception that they may comment about copyvios on any pertinent talk page. Specifically, but not exclusively, Lurking shadow is banned from blanking any article or removing any material from articles which they believe to be copyright violations. The editor may report suspected copyright infringement to CCI, WT:CP if they can show that they have investigated those suspicions to a reasonable extent, but repeated false CCI reports may lead to an extension of this ban to cover those reports as well. Lurking shadow can appeal this topic ban after 6 months from its imposition, and may do so earlier if they engage as a mentor an admin or editor experienced in copyright matters to advise them and guide their actions.

      Edited to change "CCI" to WT:CP per Hut 8.5's suggestion below. Beyond My Ken (talk) 19:40, 21 November 2018 (UTC)[reply]
      • Support as proposer. Beyond My Ken (talk) 16:49, 21 November 2018 (UTC)[reply]
      • Support topic ban per above. D4iNa4 (talk) 17:04, 21 November 2018 (UTC)[reply]
      • (Non-administrator comment) Support per nom. -A lainsane (Channel 2) 17:12, 21 November 2018 (UTC)[reply]
      • Oppose, obviously. Wikipedia:Copyright problems is the avenue for reporting copyright violations, while CCI is the avenue to report editors who repeatedly violated copyright and need their contributions checked. Banning me from the former while allowing the latter does not make any sense. I made a mistake(in labeling Healthcare in Rwanda as possible copyright violation) and I made a decision to ask for the deletion of pages that was disagreed with. You are trying to ban me from copyright violation investigations just because you strongly disagree with the deletion(understandable) and because I made a mistake(which unfortunately can happen, but should not happen repeatedly).Lurking shadow (talk) 17:16, 21 November 2018 (UTC)[reply]
      • Support absolute refusal to understand they are going about this wrong and the stated desire to kill 80,000 articles is the wrong attitude. Legacypac (talk) 17:24, 21 November 2018 (UTC)[reply]
      • Support, obviously. It is very troubling that the editor continues to insist that there is no problem or that the problem is minor, despite many more experienced editors telling them that they are unprepared for this highly complex and sensitive work. Their refusal to back off is disqualifying. Cullen328 Let's discuss it 17:25, 21 November 2018 (UTC)[reply]
      • Support. Lurking shadow has not accepted any of the advice given him above but continues to insist that we are all wrong - I blanked and tagged a few articles for deletion that happened to be made by a copyright violator. I assumed that WP:CCI and WP:Copyright would allow that, and that it was necessary(and I still think it is), What I'm trying to do here is to convince you that I'm right, among his comments from the above section. He has not backed off his plans for further disruption and there needs to be action taken to prevent any more.Smeat75 (talk) 17:59, 21 November 2018 (UTC)[reply]
      • Support doesn't appear to have the necessary judgement/skills to work in this area (which is tricky and not very suitable for inexperienced editors). I suggest that the exempted venue for reporting copyright violations be changed to WT:CP, as WP:CP is the usual venue for general copyright investigations. Hut 8.5 18:51, 21 November 2018 (UTC)[reply]
      • I have made that change, if anyone wishes to reconsider their !vote. Beyond My Ken (talk) 19:40, 21 November 2018 (UTC)[reply]
      • Support amended proposal. Lurking shadow doesn't have the experience or skill set to do this work unsupervised at this time. — Diannaa 🍁 (talk) 21:12, 21 November 2018 (UTC)[reply]
      • Support, per everyone above. When someone simply won't listen, there's little option. Boing! said Zebedee (talk) 21:22, 21 November 2018 (UTC)[reply]
      • (Non-administrator comment) Support Per support comments above, and also after witnessing the blanking of the History of the Eastern Orthodox Church (edit | talk | history | protect | delete | links | watch | logs | views) without a satisfactory explanation or warning on talk. I also don't see any reflection on the part of this editor to indicate even the slightest understanding of the problems s/he is causing. This approach to editing is wp:disruptive and should stop. Dr. K. 01:58, 22 November 2018 (UTC)[reply]
      • Question- Since there is unanimous support here for a topic ban for Lurking Shadow as defined by User:Beyond My Ken, except from Lurking Shadow of course, why doesn't an admin go ahead and impose a topic ban? I have never understood why clear cut cases like this one need to be dragged out the way they are.Smeat75 (talk) 05:08, 24 November 2018 (UTC)[reply]
      • I assume that admins are simply waiting to see if anyone else chimes in with an oppose, or if the SNOWing will continue. In any case, as long as Lurking shadow doesn't start up their behavior again, there's no particular rush to impose the TB -- although that doesn't mean that it shouldn't be put it place, it should, if only because the editor has not acknowledged the problems discussed here. It may also have something to do with the extended Thanksgiving holiday in the U.S. Beyond My Ken (talk) 05:19, 24 November 2018 (UTC)[reply]
      • I have acknowledged the problems discussed here - I already said that missing the backwards copy was a mistake I don't intend to make again, and I have acknowledged that there is not enough support for the deletion of the articles at present(although I still disagree with that, but that should be ok). Right now I am waiting for this discussion to be closed(whenever this is).Lurking shadow (talk) 08:15, 24 November 2018 (UTC)[reply]
      • You have not acknowledged the sense of this discussion that you lack the experience and judgment to work in the copyvio area. The fact that you are "waiting for this discussion to be closed", presumably to begin taking similar actions again, is an indication as to why the topic ban is necessary. Beyond My Ken (talk) 16:21, 24 November 2018 (UTC)[reply]

      Request for close

      • Once again I ask that an admin act on the unanimous request for a topic ban on Lurking Shadow. Or tell us that we are all wrong. Or something. Rather than just letting this sit here until it is archived.Smeat75 (talk) 01:48, 27 November 2018 (UTC)[reply]
      • I agree that this really should be closed with suitable action per the clear consensus of the community. Beyond My Ken (talk) 03:58, 27 November 2018 (UTC)[reply]
      • Admins have been preoccupied with having their accounts hacked lately, and some threads like this one are falling by the wayside. Thanks for your patience. Ivanvector (Talk/Edits) 16:19, 27 November 2018 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      User:Ritchie333 doubling down on personal attacks

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


      Ritchie333 (talk · contribs) cast aspersions against Praxidicae (talk · contribs) without providing evidence ("although Praxidixae is not named nor the specific person responsible for Donna Strickland, I know from first-hand experience they are close to it"). When called out, Ritchie333 declined to provide any evidence and effectively said that no, Praxidixae was in fact not close to Strickland in any meaningful way beyond having declined unrelated drafts, and Ritchie333 didn't remember anything specific that they might have done or not done, and then went on with accusations of misconduct without evidence: "if you spent more time writing the encyclopedia and less time bashing people over the head who disagree with you, people wouldn't get that impression". The thread on Ritchie333's talk page, beyond some back-and-forth bickering, contains multiple third-party requests to clarify those accusations, none of them followed up by Ritchie333. Instead, Ritchie333 tried to shut down valid concerns over his personal attacks (see WP:Casting aspersions: Yes, those are personal attacks) by complaining about the tone of the concerns.

      There's apparently quite some history between Ritchie333 and Praxidicae. Ritchie333 has previously tried to bait Praxidicae (that "smile" comment is a deliberate provocation because it refers to this conversation on Ritchie333's talk page and Ritchie333 knew exactly that it would be seen as sexist and telling a woman to better conform to her role as eye candy).

      If Ritchie333 has a genuine concern with Praxidicae's conduct (and I'm not saying that Praxidicae is blameless, though I haven't seen anything close to these examples), they should know where WP:AN/I is and what to do about it. Maligning another editor, refusing to provide evidence or retract the accusation, and engaging in further personal attacks is not the way to go and is unbecoming of an administrator. I would have thought that this could be resolved by a trout and an apology, except it's not a one-off and no acknowledgement of inappropriate behaviour, much less an apology, seems forthcoming. So instead of joining the chorus who has expressed concerns on Ritchie333's talk page I'm bringing it here. Huon (talk) 10:48, 21 November 2018 (UTC)[reply]

      I don't think Praxidicae's conduct rises to the level of ANI; I just want them to be more reflective and recognise that other people have different views and opinions on notability and procedures, that AfC has caused problems in the real world by people doing things in good faith, and that they have an overly aggressive attitude. Part of the problem with diffs (such as this) is that they were made on an old account and I didn't want to fall foul of WP:OUTING, and the problem is not so much the incidents themselves (which were only a handful) but the overly aggressive and defensive attitude towards them. If that means I come across like Gordon Ramsay berating a chef in a loss-making restaurant, well that's just the sort of person I am I guess and I do apologise as I'm not here to upset people, though in my view "Your attitude is harmful and drives people away, please stop" is not a personal attack. I have tried to be conciliatory towards them in the past, but was ignored. I know they had a huge bunfight with The Rambling Man on my talk page, but I stayed out of that as it was unproductive, and they don't work on any articles I do so I find it easy to switch off and do something else. Ritchie333 (talk) (cont) 11:09, 21 November 2018 (UTC)[reply]
      Don't drag me into this again... I was threatened enough last time round, and I don't want to go over it all again thanks. The Rambling Man (talk) 11:15, 21 November 2018 (UTC)[reply]
      Sigh, I wonder how long it will take for people to realize that piling onto someone isn't going to make them change their ways even if they are unequivocally and irrefutably wrong. Never, of course, but that's beside the point. Ritchie333, may I calmly suggest that you strike the comment about Praxidicae on compassionate grounds (if none other) from User talk:Micha Jo#Outsider view. It's obviously upset them – valid/invalid understood/misunderstood isn't important now. Then may I suggest that this be let go. Mr rnddude (talk) 13:32, 21 November 2018 (UTC)[reply]
      Sure, and done. Ritchie333 (talk) (cont) 13:38, 21 November 2018 (UTC)[reply]
      Compassion isn't what's needed, a recognition of unbecoming behavior, in my opinion, is. This doesn't change the overall issue brought up here and that is the purposely antagonistic comments but also the flat out lie and aspersions cast, not to mention the constant deflection even after being asked directly to substantiate these claims, of which they've made several. Instead calm requests even from outside parties have been met with non-response, changing the subject or hostility by pinging unrelated users into the conversation. Praxidicae (talk) 13:48, 21 November 2018 (UTC)[reply]
      And if editor retention is a concern here regarding my behavior, please look into the mirror first. Your constant attacks on people who don't participate the way that you like but are valuable editors, is what forces people out, not someone reviewing a draft and declining it when it is poorly sourced or otherwise unsuitable for mainspace. Praxidicae (talk) 13:50, 21 November 2018 (UTC)[reply]
      I think everyone here could work harder on their tone. The Rambling Man (talk) 14:18, 21 November 2018 (UTC)[reply]
      You won't get any introspection in this heat. An amicable resolution may be possible to arrive if approached in better temperaments. I've long since taken Ritchie's valuable advice and moved away from these dispute boards for solutions, only for punishments [and I generally don't aim to punish]: resolutions are rare, just look at this 150k+ byte abomination over at AN/I. Mr rnddude (talk) 14:43, 21 November 2018 (UTC)[reply]
      I'm genuinely confused as to how this discussion even started. Looking at the message left on Micha Jo's talk page here, it appears that Ritchie333 got nearly every detail of that post wrong.
      The draft was declined by several reviewers. After it was accepted, I worked on it for several hours trying to find additional sources to verify what was written. The best I can tell is that Jovanovic is a very controversial figure, but there aren't enough sources written about him to qualify for GNG, and the existing article was very one-sided and promotional. Any changes that I made to the article were undone by Micha Jo, and any attempts to work with them to provide better sourcing were met with arguments and accusations. I then nominated it for AfD.
      Andrewa then got involved and voted to keep the article, and began trying to work with Micha Jo to improve the sourcing. At the same time, he left me an email in defense of Micha Jo, which I responded to on his talk page. Ritchie333's assertion that Andrewa has been unnecessarily aggressive and badgering towards Micha Jo is unfair, as he was on Micha Jo's side throughout the AfD, and on Micha Jo's talk page.
      Praxidicae voted delete on the AfD. Once additional sockpuppets voted on the same AfD, Praxidicae opened an SPI, which was then reviewed by at least two checkusers and other administrators, who blocked Micha Jo and all the socks. Outside of these two (the keep vote, and the SPI), I'm not aware of any other involvement by Praxidicae. Ritchie333's comment I am disappointed that Praxidixae wants to bash people over the head for writing articles, which started this whole thread, is unfounded and unfair, as Praxidicae did no so such thing. The follow-up comment although Praxidixae is not named nor the specific person responsible for Donna Strickland, I know from first-hand experience they are close to it is even more confusing, as I was the one who declined that draft, not Praxidicae.
      I would urge Ritchie333 to read through the deleted article's history, the talk page thread, the thread on Andrewa's talk page, and the history of Micha Jo's talk page (the talk page has been edited and rearranged extensively, so view the history), and then form a fresh opinion. The "Outsider view" posted on Micha Jo's talk page misses the mark on almost every point, and should be removed. Bradv 15:12, 21 November 2018 (UTC)[reply]
      I would like to write a new article on Jovanovic, but I can't make head nor tail of the sources (is "Le Quotidien" as in Quotidien, Le Quotidien (newspaper) or Le Quotidien de Paris?), not so much over the French language as that I'm not really familiar with the range of French media and what normally counts as a reliable sources or not. It's frustrating because it sounds like the sort of person we should have an article on, if only we could find the sources. I spent time talking to Andrewa on this yesterday, and I think we're both in agreement that that's what needs to happen. (As you have probably seen, I have given Andrew a barnstar for his efforts as he gave a well-reasoned, accurate and civil account of events that was persuasive and convincing). Everything else as far as I'm concerned is just noise and I think people just got carried away a bit.
      I did say that I am sympathetic to your situation at the moment Bradv, as you're being gently roasted on a spit by the Executive Director of the Wikimedia Foundation for making one simple mistake months and months ago, and that people should go easy on you for it. But it is key to my central point, which is that Wikipedia is in the real world, and even though we can do things to chapter and verse and adhering to our policies and guidelines with absolute impeccability, we can still get bad press. The Independent is factually wrong to say "Someone had created a Wikipedia page for Strickland, which was subsequently flagged for deletion and removed from the encyclopaedia. The entry was determined not meet Wikipedia’s notability requirements, and all three of these criteria are biased in favour of men". However, it's also one of the most respected British newspapers and one of my "go-to" news sources that I would trust enough to generally use on BLPs. So it seems reasonable to me that if we want to change this perception, we need to go easy on people who are trying to help and not bash them over the head with policies. And if I see somebody declining AfCs and being (in my view) unreasonably defensive about it even though they may be right when examined against policy, then I think it's a reasonable concern to suggest they may want to think about how the outside world views them. Otherwise we will continue to gather bad press and those of us working on the administrative side of things will probably start to feel like it's a siege.
      Despite the impression you may have got, I do actually want to find out why people have different views for mine, even if I struggle to articulate that. Because once I know that, I can try and see if we've got a solution that will please all sides. Ritchie333 (talk) (cont) 15:41, 21 November 2018 (UTC)[reply]
      @Ritchie333: This really doesn't address the issues I raised above. I fear you have misread the history of the article and our interactions, and somehow blame Andrewa and Praxidicae. I'm glad you have resolved things with Andrewa and struck your comments, but I believe Praxidicae also deserves an apology. I'm particularly confused by your comments about blaming Praxidicae for Strickland, and not me.
      That said, I believe that AfD can be treated as a soft delete (not deleted and salted as on the French Wikipedia), so if you feel there are enough sources to write an article no one will stop you. This will probably be easier to do with Micha Jo blocked, as they were quite insistent that the information be presented only one way.
      I share your concerns about the reputation of Wikipedia in the wake of the Strickland incident, but I do not believe that the solution is to lower our standards of inclusion to a point where we keep unverifiable and promotional material. I would be happy to discuss this further with you on a different forum if you like. Bradv 15:59, 21 November 2018 (UTC)[reply]
      Okay, I did say that this was my opinion and that I might not be right and everyone else was allowed to disagree (or maybe I didn't make that clear enough :-/), and my viewpoint was primarily geared towards whether we could get a decent article produced above everything else. I'm happy to apologise over misreading Praxidicae's intent in this specific circumstance, and I am sure they do everything in good faith; however I can't change my views over their attitude because I've got no evidence. Supposing that instead of running to my talk page and screaming "You're either being fed lies by someone or outright bullshitting." (as I said elsewhere, that basically has the same effect as "Fuck you!"), they wrote something like "I understand Wikipedia's problematic reputation with the press, but we can't just lower standards to assuage hurt feelings. Happy to chat more about this." (which is kind of chapter and verse in WP:CIVIL#Dealing with incivility, and basically the last line of what you've written above) then I am certain the discussion would have taken a more productive route. I think also part of the problem is I seem to be the only one here that thinks Praxidicae has a civility problem and is prepared to call them out on it - if more people shared that view, I probably won't feel as motivated to do something about it. Ritchie333 (talk) (cont) 16:13, 21 November 2018 (UTC)[reply]
      I seem to be the only one here that thinks Praxidicae has a civility problem and is prepared to call them out on it that's not true. I agree, and have said as much here and elsewhere. The Rambling Man (talk) 16:15, 21 November 2018 (UTC)[reply]
      @Ritchie333: You still made bad faith accusations against Praxidicae though. Your admission of that error should not be dependent on how they react to the accusations. Bradv 16:18, 21 November 2018 (UTC)[reply]
      I really wish I could agree with you here, and you can call what I did misguided, foolish, ill-advised, unnecessary, overblown etc etc .... but it was done from a genuine concern for the project, so I can't describe it as bad faith. Ritchie333 (talk) (cont) 16:24, 21 November 2018 (UTC)[reply]
      @Ritchie333: Making unfounded accusations toward other users is bad faith though. I would still urge you to recognise that your comments were inappropriate, and demonstrate good faith towards Praxidicae in an effort to heal this rift between you. You have an opportunity here to make steps toward resolving your long-standing disputes, and for the good of the project I hope you take it. Bradv 17:05, 21 November 2018 (UTC)[reply]
      It's not unfounded. I have formed the opinion that Praxidicae has a civility problem and their attitude (formed primarily from incivil and unsolicited messages on my talk page like this - this was for an AfD that closed unanimously as "keep", or seeing a continual lack of response to good faith questions on their talk page such as this, this, this and this) is likely, in my view, to cause an incident like Donna Strickland sooner or later if they don't appreciate there is a problem. You might not agree with my assessment, or might think it was inflammatory, or might think my reasons are spurious, or even bringing this up is likely to be productive, but you can't say it was without foundation. Anyway, it wasn't bad faith, and if you can't accept that, I don't think there's much else I can say to persuade you, I'm afraid. Ritchie333 (talk) (cont) 17:23, 21 November 2018 (UTC)[reply]
      If you can't see how implying that someone is somehow responsible for something they had nothing to do with is bad faith and a personal attack, I don't think you should be in the business of evaluating anyone else's actions. zchrykng (talk) 17:33, 21 November 2018 (UTC)[reply]
      I did not do that. If you thought I did, then you have misunderstood my intentions. Assume good faith. Ritchie333 (talk) (cont) 17:36, 21 November 2018 (UTC)[reply]
      @Ritchie333: The two comments left here, namely Praxidixae wants to bash people over the head for writing articles and Praxidixae is not named nor the specific person responsible for Donna Strickland, I know from first-hand experience they are close to it are both unfounded. As I mentioned above, Praxidicae's frustration in dealing with these accusations does not justify the accusations themselves, and certainly do not warrant additional personal attacks. The comments you make now are just deflecting, and still do nothing to heal the rift between you. You are both respected editors, and the project would be a lot stronger if you two got along. Bradv 17:44, 21 November 2018 (UTC)[reply]
      • All of this aside, are you going to substantiate your claim that I initially asked about or are we going to continue this charade of everything being my fault for your actions? Or are you just trying to prove a point? I don't know how this question can be asked of you in a more clear or direct way. Provide diffs. Praxidicae (talk) 18:11, 21 November 2018 (UTC)[reply]
      Also your further accusations that I'm uncivil or otherwise disruptive are ridiculous. You're just making things up now and you're just trying to find something to justify your own behavior. This diff you provided is adequately explained at the AFD. This one I helped via the help chat. This was straight up someone spamming their own website and my warning adequately explained it. And the last one, well frankly, I've gone back and forth with that editor to the point that it got nowhere and I forgot about it. None of this is justification for you treating editors like trash and making false accusations. And more importantly, your perception that I don't respond is way off base as I help most of these people that I interact with via our help chat and if you have a problem with that, like everything else you've brought up, take it up at the appropriate venue. This is about 'your behavior and conduct. Since you've also seem to take a liking to trashing me at AFC, please go get consensus to remove me or drop it. Praxidicae (talk) 19:03, 21 November 2018 (UTC)[reply]

      Two-way IBAN proposal

      As much as I'd love to agree with Bradv's comment that "the project would be a lot stronger if you two got along", it's rather clear that's not going to happen - this has gone on for far too long, and is causing upset on both sides. I would like to propose a two-way interaction ban to stop this escalating further. Please - TNT 💖 18:47, 21 November 2018 (UTC)[reply]

      For clarity, I am proposing this IBAN between Ritchie333 and Praxidicae - TNT 💖 19:19, 21 November 2018 (UTC)[reply]
      • Support as proposer - TNT 💖 18:51, 21 November 2018 (UTC)[reply]
      • Um, an IBAN between which users? Jo-Jo Eumerus (talk, contributions) 19:15, 21 November 2018 (UTC)[reply]
      • Support assuming the one-way proposal below goes nowhere. zchrykng (talk) 19:18, 21 November 2018 (UTC)[reply]
      • Oppose Support – although I was hoping this would be resolved with an apology, I agree that does not appear to be forthcoming. While I'm not sure I see the advantage in extending this both ways, I do note that most, if not all, of Praxidicae's interactions with Ritchie333 are in reaction to comments he made about her editing, so both varieties of IBAN will essentially accomplish the same thing. Bradv 19:23, 21 November 2018 (UTC)[reply]
        Upon further review, I can't find any evidence of wrongdoing or "abuse" on Praxidicae's part. The messages left on Ritchie333's talk page were a justifiable reaction to the unfounded allegations made against her, and there is no reason that she should be punished for this. I realize that a one-way IBAN is difficult to enforce, but a two-way in this case is simply unfair. Therefore I'm changing my vote in favour of the option below. Bradv 20:56, 21 November 2018 (UTC)[reply]
      While I realise administrators should take it on the chin and deal with stuff, and WP:CIVIL is a busted flush, I have to say I found this message quite mean-spirited and was upset by it. Ritchie333 (talk) (cont) 21:01, 21 November 2018 (UTC)[reply]
      Ritchie333, yes, she was clearly quite upset when she wrote that. But it was in reaction to something that you wrote about her, which she termed a "total, unsubstantiated and outright lie". You've agreed above that the accusation was "misguided, foolish, ill-advised, etc.", but you still have not apologised to her for it. It's completely unfair to then punish her for being upset. Bradv 21:06, 21 November 2018 (UTC)[reply]
      Hmm, a justifiable reaction, unfair, punish... I'll have to remember that for next time. The Rambling Man (talk) 21:09, 21 November 2018 (UTC)[reply]
      It was nowhere near as mean-spirited as this, given Ritchie had been reminded just a few weeks earlier that telling women to smile when you disagree with them is inappropriate. That was not even in the same league. Fish+Karate 10:34, 22 November 2018 (UTC)[reply]
      It seems I have been naive and ignorant over that. In this case "Don't forget to smile" means "Good grief, if you can't accept my point of view, at least be nice about it", and specifically this. Yes, I shouldn't have been sarcastic and I apologise for that, but why is gender important? Ritchie333 (talk) (cont) 10:45, 22 November 2018 (UTC)[reply]
      Start here. Fish+Karate 10:53, 22 November 2018 (UTC)[reply]
      • Support as this would prevent any further talk page abuse. The Rambling Man (talk) 19:34, 21 November 2018 (UTC)[reply]
      • Support as first option. Nihlus 19:41, 21 November 2018 (UTC)[reply]
      • Support Two prolific editors with diametrically opposed views on content creation vs maintenance and who are continually rubbing each other up the wrong way. A formal two-way ban is the best option. -- Pawnkingthree (talk) 19:57, 21 November 2018 (UTC)[reply]
      • Second choice if the 1-way i-ban doesn't pass. --Floquenbeam (talk) 20:30, 21 November 2018 (UTC) strike in favor of GMG's proposal, see below. --Floquenbeam (talk) 00:55, 22 November 2018 (UTC)[reply]
      • Support: Certainly preferable to a one-way IBAN pbp 20:40, 21 November 2018 (UTC)[reply]
      • Support This needs to stop. —k6ka 🍁 (Talk · Contributions) 20:41, 21 November 2018 (UTC)[reply]
      • Oppose - Hmmm. I'm surprised to only be the second opposer here. Perhaps there is more to this than I can glean through the diffs in this thread, but I cannot see an evidence of major long-term disruption that would merit this. Beyond that, I cannot see substantial disruption in mainspace/article talk. Perhaps I am missing something, but if it's primarily on each other's talk pages, then they can request the ibans themselves. I.e. I would want to see that it's something they want, rather than something imposed on them. Otherwise I can see this iban causing more disruption than not having an iban. A couple trouts earned, but that's all, pending more diffs showing a longer-term disruption by one or both parties. — Rhododendrites talk \\ 02:44, 22 November 2018 (UTC)[reply]
      • Support as someone who considers both of these users to be friends I think this is the best option. I respect GMG's option below, but I honestly don't think it will work. I also would like to clarify that I see this as no fault: neither party particularly seems to like one another, and they tend to be drawn to conflicts involving the other.
        It's easy to say "let's all get along", but like TNT above, I think this has reached the point where it is having a negative impact on both of their experiences on Wikipedia, and, now that it's at AN, its starting to impact others. This is the sort of things that 2 way IBANs are good for: taking good faith contributors who don't get along and giving both of them help not to have to worry about it going forward. If we go with a "let's all get along" option, I think there's a halfway decent shot this will be back here again, and I'm not particularly a fan of kicking the can down the road. I respect and like both users, and I think this is the best option. TonyBallioni (talk) 03:31, 22 November 2018 (UTC)[reply]
      • Oppose, we don't have to fly headlong into an IBAN every time two editors fall out. It's intended for preventing disruption to the encyclopedia. But in this case there is no disruption being caused to the encyclopedia, nobody is being particularly harassed or vilified, it's just a bucket of snark on both sides. An apology from both to one another and a willingness to move forward and do something else would be ample. Fish+Karate 10:34, 22 November 2018 (UTC)[reply]
      • Oppose in favour of voluntary ban rather than something binding. Alex Shih (talk) 11:00, 22 November 2018 (UTC)[reply]
      • Oppose- I agree that a voluntary effort to avoid each other is a better option than a strict ban. Reyk YO! 11:07, 22 November 2018 (UTC)[reply]
      • Support per TonyBallioni. Talk of a voluntary effort seems redundant when it's clear that has failed in the past. Formalise it, and the two can hopefully live their lives without antagonising each other. I also don't think either one is more to blame than the other. In fact, as Tony says, no need to blame anyone because they just don't get along and we're all human.  — Amakuru (talk) 11:26, 22 November 2018 (UTC)[reply]
      • Comment. I am not really happy with this proposal. In my experience, users recently have been too keen of immediately jumping on sanctions. We have seen a user with over 100K contribution site-banned after a day (or was it two days, I do not remember) of a discussion at ANI. We have recently seen that a former arbitrator who behaved weirdly for an hour but had no previous blocks have been proposed to be site-banned with piling up a couple of dozen votes in an hour or so. I have on this very forum a month or so ago advocated that an indefinite block of a user with several hundred edits, one prior warning and no blocks, per NOTHERE is not necessarily the most optimum solution, and nobody listened to me, and the block still stands. Now we have two users, both with between 50K and 100K contributions to Wikipedia, with no prior warnings related to their interaction - and we start with the interaction ban? With an option of snow close? Is this really the first measure which needs to be taken? And next we will have site ban snow closed in two hours? Seriously? Give them warnings for incivility (on the talk pages), advise to stay clear from each other, and see what happens. If they really can not avoid each other and stay civil, fine, propose a two-way interaction ban. But of we continue behaving like this, soon we are just out of editors, and then usual outcry "Wikipedia is falling apart" would resume.--Ymblanter (talk) 13:09, 22 November 2018 (UTC)[reply]
        I agree with most of this. Blocks, interaction bans, and so on should be last resorts, not first options. Fish+Karate 13:23, 22 November 2018 (UTC)[reply]
      • Oppose per arguments from others, and better option in the section 2 below this. --Dweller (talk) Become old fashioned! 13:36, 22 November 2018 (UTC)[reply]
      • Oppose - This project seems far too keen on banning and blocking users. I feel sure the two users concerned can moderate their behaviours and we can all get on with building an encyclopedia. Cwmhiraeth (talk) 14:14, 22 November 2018 (UTC)[reply]
      • Comment As suggested above, this way is 'mutually assured destruction' (MAD) it goes something like this: 'we need to ban the article creator for their alleged misfeasance, we need to ban the reviewer for their alleged misfeasance, we need to ban the admin for their alleged misfeasance.' Now, I agree that the admin is most to blame, here, they should have reversed the cycle not accelerate it, but now all that's left is for us to not jump on the MAD train, and tell the admin to do better. Alanscottwalker (talk) 15:44, 22 November 2018 (UTC)[reply]
      • Oppose. I think interaction bans are an excellent tool in situations where one editor brings out the worst in another without there being anything wrong with their behavior as such. We've plenty of examples of such seemingly allergic reactions. This is not one such. I do wish Ritchie had not said what he did, and I do wish Praxidicae had not responded with a certain aggressiveness (yes, there were mitigating circumstances, but mitigation only runs up to a point). Still, this does not rise above a level where it could be talked out: I for one trust that Ritchie has received enough feedback in this very thread to prevent any further incidents (and in saying this I trust to the fact that he is reasonable enough to take this comment and the feedback above in the spirit in which it is intended, which itself is indication that no restriction is required). Vanamonde (talk) 05:46, 23 November 2018 (UTC)[reply]

      One-way IBAN proposal

      Generally two-way IBANs should only be used when the provocation is coming from both sides. I'm not seeing that here, so I think a one way IBAN on Ritchie333 from Praxidicae would be more appropriate. zchrykng (talk) 19:18, 21 November 2018 (UTC)[reply]

      • @Ritchie333: Are you agreeing to a formal, one-way IBAN from Praxidicae? If so, we can cut short this bureaucratic crap - TNT 💖 19:29, 21 November 2018 (UTC)[reply]
      I am happy to take a de facto interaction ban - by that I mean I will not consciously go and look for trouble or criticise them; however, if I accidentally see an article at CAT:CSD that they happen to have tagged as CSD G11 that I agree with and delete (without noticing who tagged it, as often I just evaluate things on their own merits), I don't think that should be block worthy (and that is the stuff that interaction bans trips up on). In return, I ask that they stay off my talk page. I am pretty comfortable with all of that, and hopefully you are too. Ritchie333 (talk) (cont) 19:32, 21 November 2018 (UTC)[reply]
      I'd like to think any administrator here wouldn't "consciously go and look for trouble". I'm not comfortable with anything less than a formal IBAN, be it a one-way or two-way. We can wait for a consensus either way - TNT 💖 19:39, 21 November 2018 (UTC)[reply]
      All I really want is for them to leave me alone and stay off my talkpage. Ritchie333 (talk) (cont) 19:46, 21 November 2018 (UTC)[reply]
      Sounds more like the IBAN needs to be in the other direction. The Rambling Man (talk) 19:48, 21 November 2018 (UTC)[reply]
      Then I need to know what happens if they tag an article for administrative assistance (most obviously CSD) and I agree with it and delete it without realising it's them? What if they tag a gross BLP violation as G10? (In fact I would say probably 90% of the time at least I agree with their CSD tags and delete the article, but these never generate controversy so nobody hears about them). These questions need to be asked up-front, because (as Black Kite suggests below) I've seen too many occasions where people have used IBANs as "aha" gotchas. Ritchie333 (talk) (cont) 19:56, 21 November 2018 (UTC)[reply]
      Oh yeah, they're definitely there for the "gotchas". You will be left in a position that you will not be able to do anything about anything they tag, rightly or wrongly. You'll need to double check who added the tag and walk away if it's someone you're one-way IBANned with. It's a horror show. The Rambling Man (talk) 20:00, 21 November 2018 (UTC)[reply]
      • Oppose Ritchie shouldn't be subject to an open house on abuse left on his talkpage. No way. The Rambling Man (talk) 19:34, 21 November 2018 (UTC)[reply]
        • I assume you have diffs of something that can objectively be called abuse, since you are leveling accusations? zchrykng (talk) 19:38, 21 November 2018 (UTC)[reply]
          • I think all you need to do is look at the threads on Richie's talkpage, and the diffs he's already offered. But thanks. The Rambling Man (talk) 19:49, 21 November 2018 (UTC)[reply]
      • Support as second option. Nihlus 19:41, 21 November 2018 (UTC)[reply]
      • Oppose You only have to look at the original message that Praxidicae left on Ritchie's talk page to see that this should be either a 2-way ban, or nothing. (Edit: but support the below suggestion by GMG) Black Kite (talk) 19:45, 21 November 2018 (UTC)[reply]
        Black Kite, that message was in response to the unfounded allegations made here. Bradv 19:48, 21 November 2018 (UTC)[reply]
      • Nevertheless, 1-way I-Bans are rarely useful, and only where there is only abuse being thrown in one direction. That isn't the case here - there's clearly an issue going in both directions. Black Kite (talk) 19:51, 21 November 2018 (UTC)[reply]
      • Oppose That would imply that the blame is all on one side, which is not the case. -- Pawnkingthree (talk) 19:52, 21 November 2018 (UTC)[reply]
      • Oppose, I do not see sufficient justification for a one-way interaction ban.--Ymblanter (talk) 19:56, 21 November 2018 (UTC)[reply]
      • I don't know what's gotten into Ritchie here, and I'm disappointed but not surprised (this being WP) that this couldn't have been worked out without resorting to formal banning. I know a lot of people I respect disagree, but I'm not personally persuaded that 1-way I-bans are inherently impractical; if Praxidicae abuses it, then she can always easily be sanctioned, but I see no reason to believe a priori that she will. The annoyances of having an Iban imposed are part of why people usually try harder to change their behavior so as not to be subject to them. --Floquenbeam (talk) 20:29, 21 November 2018 (UTC) strike in favor of GMG's proposal below. --Floquenbeam (talk) 00:56, 22 November 2018 (UTC)[reply]
        No, that's not true at all. What happens is people get slapped with a one-way IBAN, sometimes ex process, with no opportunity to "change their behavior" (sic), whether they need to or not, and then it's impossible to have that IBAN removed. No-one on Wikipedia works to avoid one-way IBANs, no-one, ever. And in any case, Ritchie's concerns are less with the ongoing talk page abuse, more with inadvertently carrying out an admin task and infringing those "terms". The Rambling Man (talk) 20:34, 21 November 2018 (UTC)[reply]
      Exactly that. I really am all ears for what I could have done instead, Floq (and if you find email easier, I'm willing to listen). I didn't start this thread, it happened in response to an unsolicited message on my talk page, which in turn came from a ping I got from a blocked user who specifically wanted my help. I've apologised for going over the mark - why can't other people? I'll even accept a two-way interaction ban because it at least sounds fair. Now, my challenge is: will the other party agree to a two-way IBAN and we can close this down with the minimum of fuss? Ritchie333 (talk) (cont) 20:43, 21 November 2018 (UTC)[reply]
      Email sent. --Floquenbeam (talk) 21:08, 21 November 2018 (UTC)[reply]
      I wouldn't worry too much, this is snow-closeable shortly with universal consensus in favour of a two-way ban, regardless. The Rambling Man (talk) 20:47, 21 November 2018 (UTC)[reply]
      • Oppose - For basically the same reasons as above. — Rhododendrites talk \\ 02:45, 22 November 2018 (UTC)[reply]
      • Oppose If anything, Praxidicae's confrontational approach is equally at blame here if not more. Alex Shih (talk) 10:57, 22 November 2018 (UTC)[reply]
      • Oppose. Unfair to blame one side when it's a mutual failure to get along.  — Amakuru (talk) 11:26, 22 November 2018 (UTC)[reply]
      • Oppose in principle, all 1-way IBANS. They're too easy to game. And this one in particular is wrong headed. --Dweller (talk) Become old fashioned! 13:34, 22 November 2018 (UTC)[reply]
      • The admin is most to blame, but just tell him to do better. Alanscottwalker (talk) 16:10, 22 November 2018 (UTC)[reply]
      • Oppose, per above. Vanamonde (talk) 05:46, 23 November 2018 (UTC)[reply]

      Propose being growed-ups

      • IBANS among two of our most active users who are also active in similar areas is going to be a nightmare. Propose ending with the strong suggestion that both users be growed-ups, leave each other be, and go do something else, without all the bureaucratic minutiae of an IBAN either way, and with the understanding that if that doesn't work, the bureaucratic nightmare is the next option (and with all the ensuing bickering about who edited what first, and with what intention). I like both these folks; I wish they liked each other, but they don't seem to. So put on your adult pants, and go your separate ways without needing the forms filled out in triplicate. GMGtalk 23:09, 21 November 2018 (UTC)[reply]
      • GMG is right, of course. An I-ban sucks bad enough (with blocks for screw-ups) that I have some faith that they will observe an unofficial near-but-not-100% i-ban. With a 1 or 2-way i-ban in our quiver if this comes back here. Thanks for the reality check, and de-escalation, GMG, I think I got swept up too. --Floquenbeam (talk) 00:59, 22 November 2018 (UTC)[reply]
      • Support as sensible. Mr rnddude (talk) 01:43, 22 November 2018 (UTC)[reply]
      • What rnddude said. -A lainsane (Channel 2) 01:52, 22 November 2018 (UTC)[reply]
      • It's a nice thought, but "being growed-ups" hasn't worked for the past several months (or however long this conflict has been going on). An actual solution is needed. Natureium (talk) 01:56, 22 November 2018 (UTC)[reply]
      • I've interacted with both these users quite a bit, I have no doubt in my mind the both of them have nothing but the best interest of the project at heart, and I expect that a community admonishment to kindly fuck off will probably be well enough for both of them to do so. GMGtalk 02:33, 22 November 2018 (UTC)[reply]
      • Support Please find some way to work out your differences. It would suck to see two people I hold in very high regard screw each other over. It really sucks and is disheartening to see you two fight like this. I don’t usually comment on ani threads but I feel as though that sanctions may §lead to valuable editors like Ritchie and P being lost. So please, find some way to work something out.💵Money💵emoji💵💸 03:21, 22 November 2018 (UTC)[reply]
      • Oppose per my comments above. Hoping for the ideal when there is a clear solution that would make sure neither would have to interact with one another would be a forced deescalation. Kicking the can down the road does no one any good. TonyBallioni (talk) 03:33, 22 November 2018 (UTC)[reply]
      • I support this. Interaction ban is most certainly not a "clear solution" in this case, but only to delay us from dealing with underlying issues, being the easy way out for spectators. If there is a pattern of unfounded accusations by Ritchie333, that needs to be resolved. If there is a pattern of problematic AfC patrolling by Praxidicae, that needs to be resolved. If neither is a problem that requires sanction or continued discussion at this point, well then whoever that is pushing it needs to stop. Not tackling underlying issues but simplifying the matter as merely two people that don't get along is not productive. Move along. Alex Shih (talk) 11:12, 22 November 2018 (UTC)[reply]
      • Strong support --Dweller (talk) Become old fashioned! 13:35, 22 November 2018 (UTC)[reply]

      For the profit of any other newcomer

      All these events occurred in relation with a now deleted article centered on a person who is none of the 45 people listed at the Jovanovic disambiguation page, but another one, whose given name is Pierre. Pldx1 (talk) 15:41, 22 November 2018 (UTC)[reply]

      In an ideal Wikipedia

      Disclosure: I am heavily involved in the discussions (past and probably future) over the article in question.

      The best solution would be to simply warn both editors that wp:NPA is a policy and that further breaches will not be tolerated, not to punish either of them but simply to protect Wikipedia.

      The problem being that this can't be an idle threat, and enforcement would be most unfair when nobody else is held to this standard, and that gives M. J more ammunition should he choose to use it. But it might be worth a try even so. See wt:Administrators' noticeboard#NPA. Andrewa (talk) 18:41, 22 November 2018 (UTC)[reply]

      The day someone enforces WP:NPA against admins is the day I reveal I'm secretly Jimmy - TNT 💖 18:44, 22 November 2018 (UTC)[reply]
      Sorry but no one here needs a reminder of what NPA is or that it is a policy; the sky is blue. It has always been about what construes as "personal attacks" when involving experienced editors; the line will always remain debatable as there are always many elements including context to consider. We do not need civility policing, but we also do not need people not dealing with one another without the basic respect one would expect if it was a real world interaction; and that needs to be mutual. Alex Shih (talk) 22:17, 22 November 2018 (UTC)[reply]
      Thanks for those thoughts.
      Agree that the key is respect. And discouraging all personal attacks encourages mutual respect, while allowing them encourages escalation of a disagreement to become a conflict. That's the beauty of the policy of NPA.
      But that's exactly the question I was asking. Has the environment here changed to the point that this is now seen as important? I'm glad you think that no one here needs a reminder of what NPA is... etc. but not convinced!
      But disagree that It has always been about what construes as "personal attacks" when involving experienced editors; the line will always remain debatable as there are always many elements including context to consider... the policy is quite explicit. Insulting or disparaging an editor is a personal attack regardless of the manner in which it is done. It's about what to do about it when it happens.
      Agree that We do not need civility policing. Civility issues are often raised as an excuse for ignoring NPA, but it's generally a red herring. The two policies are related but not the same thing at all. And if by policing you mean blocks, bans and other sanctions, agree again. When we as admins need to resort to those, in a sense we and the policies have both already failed. Andrewa (talk) 23:08, 22 November 2018 (UTC)[reply]
      Sadly that turns out to be not the case. The policy is anything but explicit, and admins' failure to recognise that is the reason why fine editors like Eric Corbett eventually give up and find something more adult to occupy their time. One person's insulting behaviour is another person's vigorous banter; what one may see as disparaging, someone else will find to be justified criticism; my rudeness could be your bluntness; and so on. While we have a system which allows admins to jump to a conclusion and then become judge, jury and executioner in one, we will continue to lose hugely valued contributors who will no longer volunteer to be treated like that. The last thing we need is hold the sort of threats that are envisaged in this thread over the heads of such valued contributors. When will folks learn that the "stick" isn't the key to behaviour modification? --RexxS (talk) 00:31, 23 November 2018 (UTC)[reply]
      This probably belongs at wt:AN#NPA where I tried to start a conversation, or even at wt:NPA. But I'm so thrilled to get any interest.
      Agree that the "stick" isn't the key to behaviour modification. But that misses the point in any case. This isn't about behaviour modification. It's about protecting Wikipedia. Yes, if someone can modify their behaviour to avoid making personal attacks, that's a good outcome. But that's irrelevant unless we can at least agree that personal attacks are always a bad idea and we seem to have lost sight even of that.
      One person's...... Exactly. So the bar needs to be set high if we're to retain editors. And it is set very high. But that is being ignored, and you can't blame people for continuing to ignore it if personal attacks pass without negative comment. That doesn't mean ban anyone who steps over the line. It means, take the trouble to say to them, maybe you meant it well but that was offensive to the other party and we have a policy that says that's unacceptable. And yes, some editors will say, if I can't tell other editors off whenever I like I'm taking my bat and ball and going home. And that is OK. This is a collaboration, we work by consensus, and not everyone is cool about that. And they simply don't belong here. Andrewa (talk) 01:05, 23 November 2018 (UTC)[reply]
      It's becoming easier. Not sure whether that's good or bad. But it would not be good to use it only against admins. More severely, yes. Andrewa (talk) 23:08, 22 November 2018 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      Wikipedia:InstallAware Software

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


      Hello, could an Admin please remove the G13 eligibility template from Wikipedia:InstallAware Software. Thank you, JMHamo (talk) 11:33, 21 November 2018 (UTC)[reply]

      @Joe Roe: as the protecting admin.--Ymblanter (talk) 13:02, 21 November 2018 (UTC)[reply]
       Done. Just had to add |demo=yes. Will likely revert to the un-substed version just for readability ease. Primefac (talk) 13:44, 21 November 2018 (UTC)[reply]
      • I'm not thrilled that we're intentionally, permanently, publicly shaming the company in project space; pretending that this is in the service of helping other companies avoid the same problem is a cover story that should be beneath us. Why lower ourselves to their level? Deleting outright would be better. --Floquenbeam (talk) 14:56, 21 November 2018 (UTC)[reply]
      Yeah, I'm with Floq on this one. I don't mind rewriting it to be fictitious, that might be the answer. Ritchie333 (talk) (cont) 14:59, 21 November 2018 (UTC)[reply]
      You know, I had the same feeling when reading that page. Spammers are an annoyance but venting your frustration about them by hanging one of their pages on a pillory like that is childish and ineffective. Jo-Jo Eumerus (talk, contributions) 15:18, 21 November 2018 (UTC)[reply]
      Agreed. And the irony is that the company now has their "article" on Wikipedia. Jauerbackdude?/dude. 15:23, 21 November 2018 (UTC)[reply]
      I joined the thread purely to stop the G13 happening, my "admin hat" comment would be... WP:MFD is thataway. Primefac (talk) 15:36, 21 November 2018 (UTC)[reply]
      It is, indeed, thataway: Wikipedia:Miscellany for deletion/Wikipedia:InstallAware Software is now live. --Floquenbeam (talk) 17:02, 21 November 2018 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      Editors copying and pasting barnstars intended for others onto their userpages

      Just curious as to whether there's any policy or guideline which addresses editors copying and pasting barnstars originally posted on other editors userpages onto their own userpages. This seems to be what DeanBWFofficial has done. While I understand that awarding yourself a barnstar might not be seen as inappropriate but not a policy/guideline violation, copying and pasting those posted by others on another editor's userpage (including signatures of other editors) onto your userpage seems like it might possibly be a problem per WP:CWW and WP:UP#NOT. DeanBWFofficial appears to be a new editor and I'm not trying to get them blocked, but maybe someone can advise them as to whether this kind of thing is allowed. -- Marchjuly (talk) 09:33, 22 November 2018 (UTC)[reply]

      I do not think we have any policy on this, and I do not think we might undertake any action. This is clearly a signal that the user is not yet fully ready to edit Wikipedia, and possibly that they confuse it with a social media site, and this means their contribution might need some inspection, but that's it.--Ymblanter (talk) 12:57, 22 November 2018 (UTC)[reply]
      FWIW, these appear to have been borrowed from The Banner's User talk:The Banner page; and now already removed/reverted by User:Abelmoschus Esculentus in Special:Diff/870093581. —Sladen (talk) 13:56, 22 November 2018 (UTC)[reply]
      These users should be too embarrassed to do this, but I don't think heavyhanded action is called for. But it might be construed a misuse of userspace. A gentle word would probably be best. --Dweller (talk) Become old fashioned! 14:02, 22 November 2018 (UTC)[reply]
      Did I merit the "Barnstar of Telling the Obvious" for remarking that using the name "DeanBWFofficial" together with asserting I am also work for International Badminton World Federation as a editor team is not so obvious ? Pldx1 (talk) 14:19, 22 November 2018 (UTC)[reply]
      Hello, I reverted some of his disruptive talk page edits which pasted the whole mainspace page verbatim, but I was reverted by Denisarona (talk · contribs) who seems to view my removals as vandalism. I did, however, repair the attribution that was lacking but necessary for the Wikipedia CC-BY-SA 3.0 licensing. I do not see the need to have the mainspace pages' content replicated on the talk page. 2600:8800:1880:188:5604:A6FF:FE38:4B26 (talk) 15:27, 22 November 2018 (UTC)[reply]
      This user's interest in Asian beauty pageants and page-moving them smells much like Wurtzbach (talk · contribs). 2600:8800:1880:188:5604:A6FF:FE38:4B26 (talk) 15:38, 22 November 2018 (UTC)[reply]
      Blocked user Deanarthurl (talk · contribs) seems quite interested in someone named "David Lim" - coincidence? 2600:8800:1880:188:5604:A6FF:FE38:4B26 (talk) 16:06, 22 November 2018 (UTC)[reply]
      Hmmm, I think I take this as flattery...
      But in the past there were several sockfarms editing articles about pageants. I think this is a reincarnation of one of the socks. (But I do not dig any deeper) The Banner talk 15:29, 22 November 2018 (UTC)[reply]
      I didn't consider that this might be a case of WP:SOCK, only that it seems inappropriate for this editor to copy and paste barnstars you have received from others onto their talkpage. A "gentle word" about this seems fine as some others have suggested. If, however, there are serious concerns of socking, then maybe a SPI would help clarify whether this is the case. -- Marchjuly (talk) 01:12, 23 November 2018 (UTC)[reply]
      I would agree pasting barnstars including the signature of another editor is inappropriate. It may lead others to believe that the person gave a barnstar to someone they didn't. Anyway I noticed Wikipedia:Administrators' noticeboard/Incidents#Help:Reverting which reminded me of this thread. DeanBWFofficial and User:DPIDAMU have been blocked as socks. Nil Einne (talk) 08:59, 26 November 2018 (UTC)[reply]

      Bad faith accuations by User:SNUGGUMS

      Would an admin like to look over the exchanges at Wikipedia:Templates for discussion/Log/2018 November 21#Template:Demi Lovato songs and User talk:SNUGGUMS#November 2018 2 where this user is accusing me of "lying" and "pretending"? --woodensuperman 15:17, 22 November 2018 (UTC)[reply]

      The only possible need for an admin would be for closing that TFD. Assumption of bad/good faith doesn't mean I can't call out flaws when I see them. SNUGGUMS (talk / edits) 15:27, 22 November 2018 (UTC)[reply]
      I do not see an urgent incident or chronic, intractable behavioral problems requiring administrative action. Woodensuperman, please try to develop slightly thicker skin. SNUGGUMS, be conscious that some people don't react well to the word "lying". Now go and find something better to do. Fish+Karate 15:32, 22 November 2018 (UTC)[reply]
      Seriously? Per Wikipedia:Assume good faith#Dealing with bad faith: "Wikipedia administrators and other experienced editors involved in dispute resolution will usually be glad to help". Also, I was under the impression that the "urgent incident or chronic, intractable behavioral problem" were for WP:ANI which is why I posted here. --woodensuperman 15:41, 22 November 2018 (UTC)[reply]
      This is wholly correct. Please therefore provide the clear and specific evidence policy-breaching conduct you have thus far failed to provide. Also this probably should be moved to ANI, I don't really care but someone will probably move it as this isn't an "issue affecting administrators generally", it's a "specific problem". Fish+Karate 15:45, 22 November 2018 (UTC)[reply]
      This was an informal request, which is why I didn't post at ANI. I've being trying to resolve with the user, who is still making the same accusations and who cannot see what is wrong with that. --woodensuperman 15:52, 22 November 2018 (UTC)[reply]
      Sorry if my comments on "lying" were taken the wrong way. More than anything else, I was frustrated with how woodensuperman insisted how proposed changes were ideal when they really weren't. SNUGGUMS (talk / edits) 16:59, 22 November 2018 (UTC)[reply]

      A Small Edit Request

      In the box(i guess it's a template) that appears in the user contribution page for those users whose accounts are currently blocked, please verify whether there exist any sort of lint error. I guess it's an obsolete tag error. I was able to find that in [this] page. Since those need admins access, I am posting this request here.Adithyak1997 (talk) 15:31, 22 November 2018 (UTC)[reply]

      Adithyak1997, that user's block notice appears normal to me. Home Lander (talk) 15:43, 22 November 2018 (UTC)[reply]
      @Home Lander:, in my account, I have enabled the tool User CSS from [this] page which displays all the errors in the colour pink. So I thought the above mentioned one is also such an error. Sorry for the wrong problem.Adithyak1997 (talk) 18:29, 22 November 2018 (UTC)[reply]

      Religion in... statistics vandalism

      Just raising this here in case anyone recognises it as a returning vandal, and to ask for others to help keep an eye on things. On the 20th November I noticed 83.51.5.88 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) falsifying cited stats in "Religion in..." articles. Today I noticed an identical edit to one of the articles by 46.6.190.64 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log). IPs are both Spanish. DuncanHill (talk) 15:53, 22 November 2018 (UTC)[reply]

      This is continuing today, latest IP is 83.51.5.206 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) DuncanHill (talk) 18:22, 26 November 2018 (UTC)[reply]
      Also 85.192.74.246 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log). DuncanHill (talk) 18:26, 26 November 2018 (UTC)[reply]
      Blocked 83.51.5.206 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) for 31 hours. 85.192.74.246 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) hasn't edited for several hours, I do not see a block serving any purpose at this point. Vanamonde (talk) 18:36, 26 November 2018 (UTC)[reply]

      Level 1 desysop of Esanchez7587

      Under the Level 1 desysopping procedures the administrator permissions of Esanchez7587 (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) have been temporarily removed as a suspected compromised account.

      Supporting: Worm That Turned, BU Rob13, Mkdw, Opabinia regalis, and KrakatoaKatie.

      For the Arbitration Committee;

      WormTT(talk) 17:53, 22 November 2018 (UTC)[reply]

      Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard#Level 1 desysop of Esanchez7587

      Discussion on admin activity requirements

      I have opened a discussion about changing the activity requirements for administrators and the procedure for removal of permissions for inactive admins. If you would like to participate, please see Wikipedia:Village pump (policy)#Proposal to tighten administrator inactivity procedure. Ivanvector (Talk/Edits) 19:17, 22 November 2018 (UTC)[reply]

      TPA removal request

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


      Can someone remove TPA from Mate Bulic Fakjea For making personal attacks while blocked. My first request was refused by Iridescent I guess they don't want to do Admin stuff. Really their response is quite unbelievable coming from an Admin, or maybe I'm asking too much. - FlightTime Phone (open channel) 22:58, 22 November 2018 (UTC)[reply]

      I've explained why you reverted their edits. Hopefully that'll take, if they tell me to go jump in a lake then yeah I'll turn access off. Ritchie333 (talk) (cont) 23:06, 22 November 2018 (UTC)[reply]
      (edit conflict) Or more accurately, Iridescent explained in detail why I don't consider revoking talk page access—a last resort only to be used to address continued abuse, something explicitly spelled out in the blocking policy—is appropriate to address a single piece of venting by someone who's just been blocked, after you randomly canvassed me for no apparent reason demanding I strip Mate Bulic Fakjea of talk page access purely on your say-so. ‑ Iridescent 23:08, 22 November 2018 (UTC)[reply]
      Iridescent It won't happen again, I assure you. A snigle ping ≠ canvassing - FlightTime Phone (open channel) 23:13, 22 November 2018 (UTC)[reply]
      Um, why retain talk page access? The only significant reason blocked users retain talk page access by default is to facilitate unblock requests, and this is rather far from that. This kind of statement can get a block on sight, without the say-so of the target, and we have less reason to be lenient to someone who's already blocked than to someone who's not been previously. Meanwhile, this was rather obviously not on the say-so of the target: you were pinged to the page where it had occurred, and you had the ability to look for yourself. Furthermore, editing of the user's talk page should be disabled only in the case of continued abuse of their user talk page means that it's generally a bad idea to shut it down, not that it's prohibited (read this, for example), and we have lenience to do that without invoking IAR. Nyttend (talk) 12:15, 23 November 2018 (UTC)[reply]
      • I also oppose the revocation of TPA on just a simple bit of venting. Be bigger, ignore, move on. And, FlightTime Phone, if you don't like personal attacks against you then perhaps you might consider not making attacks on others? Just a thought. Boing! said Zebedee (talk) 12:28, 23 November 2018 (UTC)[reply]
      I've been trying to tell FlightTime to use less templates and more personal communication for years, but it doesn't seem to sink in and when I've brought it here, I found there was no community consensus that he's doing anything wrong, so these days I just manage it accordingly. Ritchie333 (talk) (cont) 12:59, 23 November 2018 (UTC)[reply]
      • Pile on opposition to removing talk page access.--v/r - TP 19:45, 23 November 2018 (UTC)[reply]
      • Oppose also. Govindaharihari (talk) 19:49, 23 November 2018 (UTC)[reply]
      • (edit conflict) Oppose removing TPA access for now. Nyttend has already removed the said attack. If the user restores or doubles down on personal attack, then I will support TPA revoke as mentioned in the edit summary. WP:NPA is taken seriously, no leniency on such blatant cases.--DBigXray 20:01, 23 November 2018 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      Level 1 desysop of Garzo

      Under the Level 1 desysopping procedures the administrator permissions of Garzo (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) have been temporarily removed as a suspected compromised account.

      Supporting: Worm That Turned, Euryalus, Opabinia regalis, DeltaQuad, Mkdw, and KrakatoaKatie.

      For the Arbitration Committee;

      WormTT(talk) 20:03, 23 November 2018 (UTC)[reply]

      Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard#Level 1 desysop of Garzo

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


      I was wondering if this edit in the history should be striked, [20], cheers, Govvy (talk) 20:21, 23 November 2018 (UTC)[reply]

      That's just standard vandalismpromotionalism, nothing meets our RD criteria. Primefac (talk) 20:28, 23 November 2018 (UTC)[reply]
      Really, I found it rather offensive that someone would try to advertise their right wing group, I would prefer it strike deleted. Govvy (talk) 20:32, 23 November 2018 (UTC)[reply]
      Well, RD2 is grossly insulting/offensive, and simply being promotional does not fit that bill. Primefac (talk) 20:39, 23 November 2018 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

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


      Really, promoting a right wing group on wikipedia isn't a strike offence? I am surprised admins would allow that, sickens me that you haven't striked it and are allowing it to stand in the history of the article. Very sick, Govvy (talk) 21:59, 23 November 2018 (UTC)[reply]

      Please do read the criteria which govern when material is hidden from articles' histories. While this edit was correctly reverted, it comes nowhere near the threshold for revision deletion. Nick-D (talk) 22:15, 23 November 2018 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      History-merging :: help needed again

      Proposing a temporary measure to assist in protecting the Main Page

      As many Wikipedians have noticed, several accounts have recently been compromised. Three of these compromised accounts have been administrator accounts, and all three compromised admin accounts focused on vandalizing the Main Page, the public face of the project. The most recent compromised administrator account is that of a highly active administrator. I am part of the team investigating this series of events, along with stewards, other checkusers, and WMF Security and Trust & Safety staff. There are several actions taking place in the background, mainly for security and/or privacy requirements, that will not be discussed in this thread.

      One proposed temporary measure to mitigate the damage being caused by this vandal is to restrict editing of the Main Page to administrators who also hold Interface Administrator permissions. There is rarely a need to edit the Main Page itself — almost all of the work is done in the background using templates — so the impact of this temporary measure is minimal.

      As noted, this is intended to be a temporary measure that will give both the community and the investigating team some "breathing space" to focus on the vandal rather than the impact of the vandalism. It was suggested that we bring this change to the community for discussion prior to implementing it. Does anyone have any feedback on this proposal? Thanks for your participation. Risker (talk) 21:30, 24 November 2018 (UTC)[reply]

      Is it technically possible? The Main Page itself may not need many edits but the templates transcluded on it which are cascade protected are a different matter. Jo-Jo Eumerus (talk, contributions) 21:32, 24 November 2018 (UTC)[reply]
      Yes. Adding a protection level is relatively trivial to do in the MediaWiki back-end. Just needs consensus. -- Ajraddatz (talk) 21:35, 24 November 2018 (UTC)[reply]
      Yes. This can be done by private filter from what I’ve been told. TonyBallioni (talk) 21:36, 24 November 2018 (UTC)[reply]
      Sorry, I wasn't clear: Is this possible without all the templates transcluded on it also becoming it-protected? Because that would be hefty collateral damage. Jo-Jo Eumerus (talk, contributions) 21:51, 24 November 2018 (UTC)[reply]
      @Jo-Jo Eumerus: what @TonyBallioni: said been added. — xaosflux Talk 00:00, 25 November 2018 (UTC)[reply]
      • Support enough is enough. TonyBallioni (talk) 21:36, 24 November 2018 (UTC)[reply]
      • Support. Take this c**t down. —Jeremy v^_^v Bori! 21:37, 24 November 2018 (UTC)[reply]
      • Support could be done in MediaWiki, or possibly with an edit filter. --Rschen7754 21:41, 24 November 2018 (UTC)[reply]
      • As the front page of the site, the Main Page is arguably an interface page in spirit. Reasonable protection mechanism. ~ Amory (ut • c) 21:41, 24 November 2018 (UTC)[reply]
      • Support - and once this current outbreak has died down, an RfC should be run to make this change permanent. Beyond My Ken (talk) 21:42, 24 November 2018 (UTC)[reply]
      • Yup, filter please - TNT 💖 21:43, 24 November 2018 (UTC)[reply]
      • (edit conflict)x4 Support No need for this nonsense. (Please make sure there are some intadmins checking out the errors page every once in a while.) Natureium (talk) 21:44, 24 November 2018 (UTC)[reply]
      • Support, even with an option of protecting other higly visible pages such as Donald Trump for a short time.--Ymblanter (talk) 21:45, 24 November 2018 (UTC)[reply]
        This was already done earlier. Killiondude's account compromise rendered it useless. —Jeremy v^_^v Bori! 21:47, 24 November 2018 (UTC)[reply]
        Exactly my point. I mean moving these pages into mediawiki namespace so that only interface admins can edit.--Ymblanter (talk) 22:05, 24 November 2018 (UTC)[reply]
        @Ymblanter: sysops can edit MediaWiki pages already. The only pages restricted to interface admins are cascading style sheets and javascript pages. — xaosflux Talk 22:09, 24 November 2018 (UTC)[reply]
        Thanks, and as an interface admin on three projects I should have thought well before writing this. Anyway, my point is that the main page can be protected such that only interface admins can edit it (e.g. by adding a new protection level), then other highly visible pages can only get similar protection for a short time.--Ymblanter (talk) 22:16, 24 November 2018 (UTC)[reply]
        Striken the option. In view of the office action requiring TFA for all interface admins, it is absolutely not ok if only users who can afford a smartphone (or at least a laptop) will be able to edit articles such as Donald Trump.--Ymblanter (talk) 21:04, 26 November 2018 (UTC)[reply]
      • Yes, but I'd like to hear that the cascading protection issues have been fully considered. -- zzuuzz (talk) 21:50, 24 November 2018 (UTC)[reply]
        Oppose (temporary position), it's clear from some of the objections that the cascade issue hasn't been fully considered, and that this will either prevent updates to the main page or won't be at all effective. -- zzuuzz (talk) 10:44, 26 November 2018 (UTC)[reply]
      • Support I support all reasonable measures to protect the encyclopedia against this vile attack and similar incidents in the future. Cullen328 Let's discuss it 21:51, 24 November 2018 (UTC)[reply]
      • Oppose per WP:CREEP. This is not what the interface admin right was introduced for and the talk of this measure being temporary is already being subverted above. So far as I can see, the recent incidents have been handled just fine, with no significant impact or press coverage. The main page says that Wikipedia is "the free encyclopedia that anyone can edit". Limiting access to a tiny handful of people is blatantly contrary to this fundamental principle. Andrew D. (talk) 21:56, 24 November 2018 (UTC)[reply]
        • It's already restricted to only admins. How is restricting access to intadmins "blatantly contrary to this fundamental principle" if limiting it to admins isn't? Natureium (talk) 22:22, 24 November 2018 (UTC)[reply]
          • Andrew, please. I'm glad you have an opinion on everything, but that these very incidents happened means things are not "just fine". Drmies (talk) 01:41, 25 November 2018 (UTC)[reply]
      • At least temporarily some additional WP:BEANS controls have been added, these are far from perfect but may help and should not be in the way of daily workflow. — xaosflux Talk 22:00, 24 November 2018 (UTC)[reply]
      • Support Seriously Andrew, "the free encyclopedia that anyone can edit" does not mean "continually replace Donald Trump's article with a picture of an ejeculating penis". I think just about anyone knows that. Ritchie333 (talk) (cont) 22:17, 24 November 2018 (UTC)[reply]
      • Support I disagree with Andrew Davidson's comment. The Main Page already isn't editable by 99.999999999999% of the world's population; what will restricting access even further do anything more to the fact that the Main Page already doesn't fit with the whole "anyone can edit" philosophy? As for how the incidents have been handled, you may very well commend our team of stewards for acting quickly to stop further disruption, but in the case of admin accounts getting compromised it seems to be a better solution to prevent such events from happening in the first place rather than having an "oopsies" moment when the Main Page is replaced with Commons porn, even if it's reverted within ten seconds. —k6ka 🍁 (Talk · Contributions) 22:26, 24 November 2018 (UTC)[reply]
      • Support – fairly obvious, really. SNOW-close, please. Bradv 22:32, 24 November 2018 (UTC)[reply]
      • Support, but let's not let "I need to edit the Main Page" become a new reason to hand out intadmin rights. What the attacker could do with an intadmin account is much, much worse, and I'd like to keep the number of such accounts as low as possible. Suffusion of Yellow (talk) 22:34, 24 November 2018 (UTC)[reply]
        Didn't really think this one through. I'd oppose but I don't know how to explain my rationale without getting BEANsy. Suffusion of Yellow (talk) 07:17, 26 November 2018 (UTC)[reply]
      • Support solely for the main page; I agree with the comments that due to the nature of transclusions, that page is already similar to an interface page (and assume that transcluded pages would not be affected). I don't think this will be effective for other pages; rationale withheld per WP:BEANS. power~enwiki (π, ν) 22:35, 24 November 2018 (UTC)[reply]
        • There seems to be some discussion that this would also affect transcluded pages. In that case, I'd only support if it was a separate permission from INTADMIN. Ideally, it would be a permission that could be given to trusted non-admins, specifically The Rambling Man. power~enwiki (π, ν) 17:41, 26 November 2018 (UTC)[reply]
      • Support. Regardless of what the best approach should be, there are times when one has to use whatever tool is at hand, and build better tools later. Perhaps we should start looking at a scheme of progressive protection where "anybody" can edit at the bottom of the pyramid, but increasing experience and trust are required to move up to vital or more developed pages.
      As a side note, I have long thought that "the free encyclopedia that anyone can edit" – which isn't even true – should be changed to "the collaborative free encyclopedia", emphasising working together. ♦ J. Johnson (JJ) (talk) 22:38, 24 November 2018 (UTC)[reply]
      I could be wrong, but I don't believe that the WMF uses that tag line anymore. Beyond My Ken (talk) 23:03, 24 November 2018 (UTC)[reply]
      Wrong! Beyond My Ken (talk) 01:38, 25 November 2018 (UTC)[reply]
      • Support (x10,000). Porn on the main page by compromised accounts is a severe problem. We have active interface admins and as others have mentioned, the main page itself doesn't need editing frequently, so I think this would clearly do more good than it would harm. But is there a way to protect a page with cascading protection at a certain level, but then have a higher local protection level? If it isn't possible, then I definitely would not support intadmin-protecting all pages transcluded onto the main page.--SkyGazer 512 Oh no, what did I do this time? 22:41, 24 November 2018 (UTC)[reply]
        We've done that now, but it is more of a speed-bump than a road-block. — xaosflux Talk 23:13, 24 November 2018 (UTC)[reply]
      • Support I've been an admin for 11 years, and never needed to edit it (well, apart from this evening, and someone even beat me to that by fractions of a second, so thanks for that). Black Kite (talk) 23:50, 24 November 2018 (UTC)[reply]
      • Support temporarily as proposed for the Main Page. -- KTC (talk) 00:31, 25 November 2018 (UTC)[reply]
      • Support as a temporary measure (but how would this work? A new form of protection, since this isn't in the MediaWiki namespace?) SemiHypercube 00:41, 25 November 2018 (UTC)[reply]
        Also, I don't think using an edit filter will be completely effective, not saying the weakness per you-know-what, but one could figure out what it is. SemiHypercube 17:08, 25 November 2018 (UTC)[reply]
      • Support The attacker is doing us a favor by highlighting the weaknesses. They will move on to the next weak link but protecting the main page is obviously required. Re "how would this work?": developers can do anything and they will quickly fix the problem. Johnuniq (talk) 01:35, 25 November 2018 (UTC)[reply]
      • Support, since I just got back from dealing with this guy. GABgab 01:52, 25 November 2018 (UTC)[reply]
      • Support - I wouldn't dare to touch it, anyway. Jauerbackdude?/dude. 01:55, 25 November 2018 (UTC)[reply]
      • Support I wouldn't mind if this is a permanent change; the Main Page itself doesn't need editing very often. funplussmart (talk) 05:00, 25 November 2018 (UTC)[reply]
      • Support  temporary measure. Orientls (talk) 05:00, 25 November 2018 (UTC)[reply]
        Support, Sensible measure. Ammarpad (talk) 05:53, 25 November 2018 (UTC)[reply]
      • Oppose Upon further reflection, I understand this will not solve the problem without cascading and with cascading, it creates bigger problem. –Ammarpad (talk) 12:32, 26 November 2018 (UTC)[reply]
      • Support as if I'm reading this right, only the actual Main Page will receive this additional protection, not T:DYK etc. I'd be willing to support this as a permanent change, too. Anarchyte (talk | work) 06:36, 25 November 2018 (UTC)[reply]
      • Weak support I think Andrew's comment is being wrongly ignored as the discussion above seems to be the creation of a new level of page protection which I do not think should exist or be used on this project except for this specific instance. I do not think having or applying IAdmin protection to anything except javascript pages is something that I would ever want, and the only reason I would be in favor of this is because of the recent security concerns. I do not think we should ever have a protection level that restricts editing to 14 people. For comparison, twice as many people are in the staff group (a little over 30), allowing them to edit superprotected pages, than are IAdmins on enwiki. The admonition against WP:CREEP should be taken more seriously and the temporary nature of this use emphasized. Wugapodes [thɑk] [ˈkan.ˌʧɹɪbz] 07:38, 25 November 2018 (UTC)[reply]
        • My weak support has now become Oppose given a lot of the subsequent discussion. Jimbo's account has been compromised before, IAdmins can be compromised, and restricting editing to these few people, while more likely to prevent abuse, will make resolving any actual abuse more difficult. I'd rather greater risk but quicker response than less risk and slower response. I also think this whole thing has turned into a catch-22. I'm opposed to cascading protection for the Main Page, since it would turn IAdmin into something it was never supposed to be, but not cascade protecting the main page would result in the vandals moving on to the templates themselves. I really think this is just generally a bad idea the more I think about it. Wugapodes [thɑk] [ˈkan.ˌʧɹɪbz] 01:05, 27 November 2018 (UTC)[reply]
      • Comment I have been busy so I'm not up to play. I'm not opposed to the idea although I'm not sure this will help a great deal from what's been said. I appreciate per BEAN etc that maybe details can't be discussed for this very reason so maybe there can be no clarification. But I don't think what I'm saying here is likely to be reveal anything not already obvious to prying eyes. It sounds like the plan is to still allow admins to make changes to the templates without requiring an interface admin to approve them. In that case, it seems like the vandal will just move on to vandalising the templates. I mean they're probably already working out what to do. While I appreciate they have been directly editing the main page so far, they haven't had a reason not to. And while trying passwords from previous leaks (which I assume is probably what's happening) is not really that technically demanding if you only have a few to try, it seems unlikely to me anyone capable of this won't figure it out fairly fast. Again maybe no comment can be offered, but is it believed the templates can somehow be protected against this vandalism in ways the actually main page can't? Nil Einne (talk) 10:38, 25 November 2018 (UTC)[reply]
      • Weak support only until a stronger solution is determined. The attacker (or an attacker, maybe not this one) has already demonstrated they can compromise 2FA-enabled accounts. Restricting access to intadmins reduces our security exposure, but will just focus the attacks on a different class of user. Ivanvector (Talk/Edits) 21:19, 25 November 2018 (UTC)[reply]
        • Wait which 2FA account got hacked? I hope what you're saying isn't true, it would mean that even 2FA isn't enough to stop the attack. funplussmart (talk) 21:23, 25 November 2018 (UTC)[reply]
        I don't know which accounts specifically. 2FA is a good solution but it's not perfect. Ivanvector (Talk/Edits) 21:34, 25 November 2018 (UTC)[reply]
        Hi, none of the accounts compromised in this attack had 2FA. We currently believe all compromises in this attack were due to people using the same password on other websites which presumably got hacked. 2FA is of course not a magic bullet - it won't fix every security problem (e.g. If someone steals your computer well logged in, 2FA is not going to stop that. If you add malicious Javascript to your special:mypage/common.js, 2FA can't stop that) but 2FA would have stopped this attack if the admins in question had enabled it. I strongly encourage all admins to enable 2FA. BWolff (WMF) (talk) 22:49, 25 November 2018 (UTC)[reply]
      • No, come on. Really? I'd much rather have compromised admin accounts announcing themselves to us by editing the main page than do other things. As it is, I don't think this is worth anywhere near the community time or consternation we have all spent on this. Kevin (aka L235 · t · c) 06:07, 26 November 2018 (UTC)[reply]
        • ^^^This. Compromised admin accounts used to be immediately detectable to every other logged-in admin on the site back when they announced themselves by making "Main Page" go red on every page. Now that it isn't deleteable because of the same sort of technical measure being proposed here, they have to "settle" for goatseing it. Some improvement. The last thing we want to do is make them settle for one of the couple dozen ways you can cause real and/or irreversible harm with a sysop bit. —Cryptic 11:11, 26 November 2018 (UTC)[reply]
      • Oppose int-admin cascading protection, but I do support a MediaWiki imposed int-admin protection to the Main Page itself, and perhaps a few others, as is the status-quo with filter 943. The filter was an emergency measure. Using interface admin isn't really the right way to go. I agree with others below that there shouldn't be non-technical people in the technical user group. We either need a new user group, or only int-admin protect the main page itself, and not the pages transcluded on it. Better yet, phab:T210192#4771932, phab:T150826 and phab:T150576. Sorry if I misled anyone MusikAnimal talk 06:45, 26 November 2018 (UTC)[reply]
      • Support until other security measures can be implemented or the vandalism subsides. GorillaWarfare (talk) 06:37, 26 November 2018 (UTC)[reply]
      • Oppose in contrast to the discussion about removing the unblockself permission this would create a real problem if one of the accounts with interface-editor were to be compromised, it would leave us with little means to reverse their actions. For this to work it would also need to be cascading protection as otherwise something could just be added to a page transcluded to the main page, that severely restricts the number of people who can put anything on the main page. Fix that by adding more people to the usergroup and we're back where we started. We should be looking at a technical solution to solve the problem, maybe some sort of double confirmation by two admins to put things on the main page (similar to pending changes in a way, but without auto accept). Callanecc (talk • contribs • logs) 06:49, 26 November 2018 (UTC)[reply]
        @Callanecc:. It seems to me you're opposing based on wrong assumption that: the protection must propagate (cascade) to all transcluded pages, DYK, ITN etc... thereby limiting placing items to only less than 10? techadmins. But from what I understand that's not what will happen. Only the "Mainpage" will be protected with this above-admin level, this will be done via MediaWiki backend and question of "how" is beyond the scope of this discussion. What's is just needed is the consensus. –Ammarpad (talk) 07:23, 26 November 2018 (UTC)[reply]
        Thanks for asking Ammarpad, my point was that the only way for protection like this to be effective would be to protect transclusions at the same level. I'm opposed to protecting the transclusions so also to protecting the main page in this way. However, maybe something like pending changes for admins to edit the main page (or transcluded pages) where it required two admins to make a change (one to initiate and one to approve) would be a good solution. In the meantime the status quo should prevail so that we can more easily deal with any further compromised accounts. Callanecc (talk • contribs • logs) 09:14, 26 November 2018 (UTC)[reply]
        The notion of there being less ways to revert vandalism is one of the only reasons I'm partially reconsidering my support vote. However, I do think that if we have a mandatory 2FA enabled intadmin account hacked, we have more on our hands than just the main page being changed, and the person behind these attacks know this. Unless they just want to make a statement for publicity, they can do a lot worse (which is why intadmin exists in the first place). Anarchyte (talk | work) 10:58, 26 November 2018 (UTC)[reply]
        Anarchyte, There are a number of ways a 2FA-secured account can become compromised - and while I won't list them all here, physical theft of device (most likely a phone or chromebook/laptop) would be the first one that would come to mind for me. SQLQuery me! 01:12, 27 November 2018 (UTC)[reply]
        @SQL: I'm aware. I'm saying that given WMF Office has now forced all intadmins to enable 2FA, if they get hacked we have something bigger on our hands. An intadmin can do real damage and I'm sure that's what a hacker would do with one, unless they only want to change the main page for publicity. An admin account can do a lot but we can no longer truly break the site. Anarchyte (talk | work) 07:03, 27 November 2018 (UTC)[reply]
      • I'm not "opposing" but I would just like to ensure this is thought through fully before being implemented.
      1. If the protection cascades then we have an issue:
      a) The existing small number interface admins will be responsible for all DYK, OTD, POTD, FA, FL updates. this is clearly not going to work, so:
      b) We will have to make a bunch of new interface admins. Not a good idea, the whole idea of the role is to minimize the number of people with that kind of access.
      2. If the protection does not cascade then it's not actually going to prevent a compromised admin account from vandalizing the main page, without specifying details, and in fact might make it harder slower to track down and resolve the problem.
      I think rather than misuse the interface admin permission, which sounds like a neat idea in principle but a bad one when considering the detail, something else would need to be done. I am not in favour of uncoupling admin permissions, because we have a small pool of administrators anyway and adding further obstacles to admins who (for example) have never edited the main page but want to help when they see a backlog or an issue arise will silo things up even more and make things less flexible. I don't have the right solution, but I have concerns about the proposed one for the reasons above. Fish+Karate 09:56, 26 November 2018 (UTC)[reply]
      • Support Non-essential admin area and page that generally requires minimal change. Restrict to those who actually need it. talk to !dave 14:48, 26 November 2018 (UTC)[reply]
      • I have the same problems that Fish and karate has. Everything on the Main Page – DYK, ITN, all of it – is cascaded. We're about to make a very small group of people responsible for carrying out all the updates to the Main Page, If those people are prepared to do that, including updating DYK however often it has to be updated, I'm fine with it. If not, we either have to make more intadmins, which kind of defeats the purpose of having intadmins in the first place, or find another solution. Katietalk 16:01, 26 November 2018 (UTC)[reply]
      • Support - Per all supports and K6ka - FlightTime (open channel) 17:55, 26 November 2018 (UTC)[reply]
      • Strong Oppose - For starters, this is not what the intadmin permission was intended for. And when one of those accounts becomes compromised (intadmin isn't a magic flag that makes your account unhackable), there will be even fewer around that can undo the damage. Additionally, Fish and karate makes a fantastic point about narrowing who can work on the main page. SQLQuery me! 18:08, 26 November 2018 (UTC)[reply]
      • Oppose if we keep the cascading protection then you will need to be an interface admin to work on WP:DYK, WP:ITN/C, WP:ERRORS, etc. This massively restricts the pool of people who can work on those processes. The people who are interface admins were chosen for their technical skill at HTML/CSS/etc and don't necessarily have any interest in or ability to deal with those processes. We could appoint a load more interface admins to do this work, but that would rather defeat the point of the proposal. On the other hand if we turn cascading protection off then we make the whole of the main page much less secure, and even if we manage to manually protect everything transcluded on the main page I'm sure the attacker is capable of going after one of those pages instead. People I talk to about Wikipedia in real life usually have little or no idea that the main page even exists, I don't think it's a huge problem as advertised. Hut 8.5 18:34, 26 November 2018 (UTC)[reply]
      • Support if temporary. Should be reverted to be only admin when the compromised accounts are taken care of. Kirbanzo (talk) 19:12, 26 November 2018 (UTC)[reply]
      • Oppose This creates more problems than it solves. I think Callanecc is on the right track with a modified PC. Crazynas t 19:47, 26 November 2018 (UTC)[reply]
      • Support but via the already made EF. Optionally support int-admin to MP by way of the same backed protection system that prevents move/delete. — xaosflux Talk 20:49, 26 November 2018 (UTC)[reply]
        And if anyone wants to say but what about EFM issues - I think we should make EFM be along the same process as int-admin, including expiring it from admins that haven't actually used it in a while. — xaosflux Talk 20:52, 26 November 2018 (UTC)[reply]
        Agree on both counts. ~ Amory (ut • c) 22:57, 26 November 2018 (UTC)[reply]
      • Support would support this as a permanent measure --Tom (LT) (talk) 23:30, 26 November 2018 (UTC)[reply]
      • Oppose. Aside from the bits that I'm seeing below, about admins being able to edit the component content (or requiring interface-admin rights to edit pages like On This Day), remember that Jimbo's account was compromised two years ago and used to vandalise the Main Page. (Admin-only link, and someone appropriately uses rollback on that edit.) Even super-admin accounts with rights like interface admin or founder can be compromised, and when it requires super-admin rights to edit the Main Page, it will sometimes take a good deal longer to revert vandalism: it's easy to find an admin to revert vandalism to a protected page rather quickly, but finding an interface admin or a steward may take a good number of minutes. We mustn't pretend that interface admins, stewards, or founders are 100% immune from compromise, so we shouldn't imagine that restricting Main Page editing to them will prevent this kind of vandalism. Nyttend (talk) 00:54, 27 November 2018 (UTC)[reply]
        @Nyttend: Though "super-admin" accounts like int-admin and founder are much less likely to be compromised, since int-admins are required by the WMF to use two-factor authentication, and Jimbo probably uses 2FA (does anyone know this for sure?) SemiHypercube 13:36, 27 November 2018 (UTC)[reply]
      • Oppose. After reading this through, I'm unable to see a resolution to the cascading protection issue. I would support the main page being protected without cascading protection being applied, to slightly reduce the target for any potential vandals, but I doubt that would do much. I suspect the best option here would be to create a new user group and new protection level intended purely for the main page and its constituent elements. I would also support making 2FA mandatory for this group. Vanamonde (talk) 04:51, 27 November 2018 (UTC)[reply]
      • Oppose, beyond the measures already taken. The cure is worse than the disease here; while I'd be willing to help out as an intadmin with maintaining the Main Page, there just aren't enough of us to go around, and increasing the numbers of intadmins to do off-mission stuff like this defeats the purpose of spinning intadmins off in the first place. Writ Keeper ♔ 13:43, 27 November 2018 (UTC)[reply]
      • Oppose (go PC) - the cascading issue is too major. Int-admins are, by design, a tiny group (they didn't even let in 4 trusted technical non-admins). Without cascading we don't really do anything. With it we'd need far more to cover everything, including blocking certain areas that were the main reason some admins actually joined up. Additionally, it seems bold of us to add such a job to the int-admin remit without at least half of them saying yes (this is a secondary concern). Getting an admin-only Pending Changes approach seems much better. Obviously more than 1 admin can have their account compromised but it should significantly reduce the frequency of issues. Nosebagbear (talk) 16:01, 27 November 2018 (UTC)[reply]
      A note - an alternate mooted strategy of main-page admins (functionally granted on request, though presumably after a delay to stop immediate requests than vandalism) would seem less preferable because of a patient vandal to abuse. That said, it would also be an alternate potential method. Nosebagbear (talk)
      • Oppose per Andrew D. Enterprisey (talk!) 20:23, 27 November 2018 (UTC)[reply]
      • Oppose until someone comes up with a solution to the cascading problem and allow timely updates to ITN and DYK.-- Pawnkingthree (talk) 20:51, 27 November 2018 (UTC)[reply]

      How temporary?

      There seems to be support for the measure above but several supports are predicated on it being temporary. Seems like it would be worthwhile to have some form of consensus of how long temporary is prior to any implementation. Best, Barkeep49 (talk) 06:08, 25 November 2018 (UTC)[reply]

      That's a pretty good question, Barkeep49. I think it can be said for certain that this change would be reverted as soon as it's fairly certain the vandalism issue has been resolved and the editing restriction is no longer needed. It's difficult to predict this; we've only been working on it for 72 hours, and it's a long weekend for US WMF staff (who have been very responsive), so the investigation is in its very early stages. Once we have more experienced eyes looking at things, including those who have the knowledge to suggest other options or methods for addressing the issues we're seeing, it's possible that a different/less intrusive option will be identified. It's also possible that after we've tried this for a few days, we find out that it's not really working. There's also the possibility that it becomes necessary to consider a permanent solution, either because no other less intrusive means has been identified to prevent this kind of vandalism, or because the efforts at vandalism haven't abated. Would it be reasonable to suggest that, if it still seems necessary to keep editing of the main page very restricted by 7 January 2019, it would be time to have a further community discussion about what options are available? These situations often take a few weeks to resolve, and there will be some extended holiday breaks in the next six weeks, so early January feels right. I'd be happy to hear other suggestions. Risker (talk) 07:45, 25 November 2018 (UTC)[reply]
      Yes, that sounds good. The problem with emergency/quick fixes to a crisis situation is not coming back to it once the urgency is gone. I think we have enough editors watching this to avoid that. And, incidentally, thanks for keeping us informed. ♦ J. Johnson (JJ) (talk) 00:39, 26 November 2018 (UTC)[reply]
      • 07/01/19 seems a reasonable time - so long as it is agreed that the consensus appearing for this is not a consensus for a permanent introduction - i.e. if the problem hasn't been resolved or an alternate solution proposed, a new RfC must be introduced in January to retain this mechanism Nosebagbear (talk) 19:29, 26 November 2018 (UTC)[reply]
      While there is some support for having this as a permanent fix, I don't believe anyone would accept that without further discussion. ♦ J. Johnson (JJ) (talk) 22:15, 26 November 2018 (UTC)[reply]

      How long do we have to debate this before it's implemented?

      This has nearly unanimous support and it's only a temporary change. What are we waiting for? Natureium (talk) 19:27, 25 November 2018 (UTC)[reply]

      First, it has to be open for at least 24h, and possibly, since now it is a weekend, possibly longer. Then it needs to be closed by an uninvolved administrator. Then some technical issues need to be implemented, for which a fabricator ticket should be opened.--Ymblanter (talk) 19:32, 25 November 2018 (UTC)[reply]
      Note: From the technical side - as an emergency measure I can implement it as soon as (if) you all agree that its the right thing to do (weekend or not). BWolff (WMF) (talk) 19:40, 25 November 2018 (UTC)[reply]
      Great, this is good to know.--Ymblanter (talk) 19:45, 25 November 2018 (UTC)[reply]
      @BWolff (WMF): can you clarify whether, if this is implemented, admins will still be edit pages transcluded onto the main page? -- zzuuzz (talk) 19:47, 25 November 2018 (UTC)[reply]
      • Answers to some questions and statuses that keep coming up:
        1. We have already done something about edits to the Main Page.
        2. If a new "higher" protection level is applied and cascading protection is enabled, then all of the cascaded items will be protected at the new level. Tested at testwiki:Main Page2 and its template testwiki:Template:MPtemp1 using the "centralnotice" protection level
      • xaosflux Talk 20:18, 25 November 2018 (UTC)[reply]
        Thanks. So we're either going to need a bunch of new interface admins or check in with the existing ones. This needs to be done before implementation. -- zzuuzz (talk) 20:28, 25 November 2018 (UTC)[reply]
        @Zzuuzz: "A bunch of new interface admins" would be a step backwards in security. Would it be possible to create (yet) another protection level (call it "Main page protected"), and another user group ("Main page editors"), then quickly add the ITN/DYK/etc. regulars to that group? Suffusion of Yellow (talk) 20:33, 25 November 2018 (UTC)[reply]
        Also pinging @Xaosflux and BWolff (WMF): Suffusion of Yellow (talk) 20:46, 25 November 2018 (UTC)[reply]
        I don't disagree; I'd also point out that one of those admins in potential new user group was compromised 24 hours ago. I'd want to see 2FA compulsory for whatever is implemented, which I think needs a little more thought. -- zzuuzz (talk) 20:55, 25 November 2018 (UTC)[reply]
        Yes, all these things are possible. We don't have automated ways to require 2FA for a specific group, but its definitely possible given a list of people in a group to manually check which have 2FA enabled. BWolff (WMF) (talk) 21:12, 25 November 2018 (UTC)[reply]
      • Does anyone know if the MediaWiki software could be changed so two protection levels could be applied simultaneously? (int-admin, non-cascading protection for just the Main Page, with full cascading protection for protecting transcluded templates) We've never had to deal with anything similar, since cascading protection with anything lower than full-protection is impossible and we haven't had a protection level higher than full-protection. With one infamous exception. SemiHypercube 02:18, 26 November 2018 (UTC)[reply]
      • I fell that the language used here is too relaxed. A: If a new "higher" protection level is applied and cascading protection is enabled, then all of the cascaded items will be protected at the new level is only a definition of cascading. B: Tested at ... is only checking that cascading is correctly implemented. C: If this is implemented, will admins... is a question that should be answered by: the proposal is to enforce this and that, and the result for this_kind_of_people (should the proposal be applied) will be this and that while the result for that_kind_of_people will be this and that. A great advice about this kind of wording is RFC2119. Best regards. Pldx1 (talk) 10:56, 26 November 2018 (UTC)/ modified Pldx1 (talk) 11:00, 26 November 2018 (UTC)[reply]


      • A note - while an early close probably would have been justified on, say, Sunday, there have been a fair number of recent opposes plus 3 conversions from support to oppose. I obviously have at least some bias (since almost all participants have cast a !vote I suppose that's fairly universal here) but would say it's worth leaving open at least another 48 hours to see if that's a sea change or a blip. Nosebagbear (talk) 16:19, 27 November 2018 (UTC)[reply]

      Post (initial) closure

      Clarification of the closure requested. I'm not seeing the mechanics of this finalized, especially in light of active discussions about them still taking place. — xaosflux Talk 03:29, 26 November 2018 (UTC)[reply]

      This also seems a bit rushed. Regarding the 2FA notes for interface admins, WMF is going to deal with that for now under OFFICE rules. I'm also a bit concerned about greatly increasing the number of interface admins and forcing 2FA (via the OFFICE rule) on to people that want to maintain things like DYK and ITN can have negative impacts: (a) non-technical people with technical access (b) removal from editorial tasks for admins that can't or don't want 2FA at this time. — xaosflux Talk 03:35, 26 November 2018 (UTC)[reply]
      • Closure review requested as this was a very early closure while discussion was still active. — xaosflux Talk 03:37, 26 November 2018 (UTC)[reply]
      • Given the nature of the proposal concerning yet another security incident, third one in the last 60 days, and the near unanimous support after 24 hours of the proposal as worded, I felt it appropriate to expedite closing this proposal. If this is a mistaken thought, I will happily reverse the close.—CYBERPOWER (Around) 03:42, 26 November 2018 (UTC)[reply]
        I think the early responses here are enough to give credibility to what is going on with filter 943, but that's it so far. For example, do we really need User:DYKUpdateBot and its operator to also become 2FA required int-admins right now, every contributor to Template:In the news, etc? — xaosflux Talk 03:46, 26 November 2018 (UTC)[reply]
        Nevermind, I re-opened it again. If there is concern with this close, I'd rather just re-open it, as I'm headed to bed and don't want to leave it as is.—CYBERPOWER (Around) 03:48, 26 November 2018 (UTC)[reply]
      • I'm probably harping on the point by now, but if this proposal results in more intadmins, we're doing it wrong. Either the existing intadmins need to take up all the main page responsibilities, or we need a new "Main Page Editor" right. I suspect maybe 1/10th of admins will even express an interest in this, so even without any 2FA requirement, this will do away with 90% of the attack surface. We can talk about requiring 2FA later. Suffusion of Yellow (talk) 04:10, 26 November 2018 (UTC)[reply]
      Again I don't disagree, though it still wouldn't have prevented the latest attacks and it would have prevented any admins fixing it in a hurry. Another alternative, which I'd prefer, is a bespoke software solution similar to how admins can't delete or move the main page, without all the cascading issues. -- zzuuzz (talk) 05:34, 26 November 2018 (UTC)[reply]
      Good point about the slower response, but I don't see evidence that Esanchez7587 or Garzo had ever edited anything MP-transcluded, so it would have prevented 2 of the 3 latest attacks. Suffusion of Yellow (talk) 05:57, 26 November 2018 (UTC)[reply]
      I've now had some coffeee and a chance to think this through a bit, and I can see how this could work without a software change. We already have a number of main pages lying around which cascade-protect the main page content. I don't properly know how the system works, so someone will need to confirm, and we'll probably want more. So then we basically remove the cascade from the main main page, and apply the new protection level to the main page only without cascade. This would leave the main page content editable by sysops, which doesn't really provide any benefit. So we once again return to the question of how to protect the main page content whilst keeping it updateable without making security actually worse. -- zzuuzz (talk) 10:18, 26 November 2018 (UTC)[reply]
      I think at this point, the most likely feasible idea should be a new protection level roughly based on what Callanecc said above. All edits to Mainpage directly and templates it pulls from (ITN, DYK...) should be subjected to four eyes principle; that means they must be approved by another admin before going live. It will be very hard and unlikely for a vandal to get two different admin accounts solely to bypass this restriction. Its efficacy will be the same as if all admins enabled 2FA. And with this protection level, we can safely apply the cascading and simultaneously allow all admins to edit the Mainpage and its templates normally. And the vandal's edit... will surely be caught waiting to be "approved"–Ammarpad (talk) 13:27, 26 November 2018 (UTC)[reply]
      You're basically describing a version of WP:pending changes. Is it feasible to implement an admin-only version of that? ‑‑ElHef (Meep?) 15:05, 26 November 2018 (UTC)[reply]
      Indeed I am. If you know the basic framework of PC2 you'll know this is feasible, though I don't know how simple or hard that implementing it will be. –Ammarpad (talk) 15:53, 26 November 2018 (UTC)[reply]
      • Q: How many of the (currently 13) human interface administrators stand ready to take up the workload that will be created? –xenotalk 19:22, 26 November 2018 (UTC)[reply]
        @Xeno: as an int-admin I think its safe to say most of us would have no issue dealing with formatting of the wikitext on Main page or certain included templates (via edit requests). I know I don't want to do things like manage the "content" (e.g. placing the Featured Article, updating DYK, updating ITN, etc). — xaosflux Talk 20:31, 26 November 2018 (UTC)[reply]
        FWIW the current EF is already enforcing that. — xaosflux Talk 20:32, 26 November 2018 (UTC)[reply]
        Xeno, I will answer any edit request that comes by.—CYBERPOWER (Chat) 20:58, 26 November 2018 (UTC)[reply]
      • @Cyberpower678: (and anyone else who believes IntAdmins will be able to handle all main page content): With respect, you're greatly underestimating the number of tweaks made to the main page every day. There have been 40 edits to the various main page sections in the last week alone: most of these are fixes or clarifications of some kind, that need to be made fairly quickly. Many of these are also not quick tweaks but require assessing consensus, at ERRORS or ITN/C or WT:DYK or elsewhere. I suspect that if the 13 IntAdmins are the only ones able to make these changes, we're going to have some trouble. Vanamonde (talk) 04:37, 27 November 2018 (UTC) Resigning to fix ping. Vanamonde (talk) 20:45, 27 November 2018 (UTC)[reply]

      Cascading

      One of the three main oppose reasons is the cascading issue - I thought it worth splitting out the issue of discussing whether this Int-Protect would cause knock on protection to be implemented, if those qualified to discuss such could answer. Nosebagbear (talk) 20:24, 26 November 2018 (UTC)[reply]

      I'm not exactly following your question @Nosebagbear:. In the current software if "cascading" protection is applied whatever level is applied also gets applied to everything transcluded. — xaosflux Talk 20:29, 26 November 2018 (UTC)[reply]
      There is a query in the discussions above on whether all the constituent aspects of the Main Page (DYK etc) are going to have to have this int-protection (presumably enacted via cascade) for the main page to actually be safe. It is disputed, but I wouldn't say it is made precisely clear. Since the MP is primarily made up of a bunch of transclusions, presumably more than just the MP itself will need this protection level. Nosebagbear (talk) 20:37, 26 November 2018 (UTC)[reply]
      This is answered in the section just above, and we have a choice: Without cascading protection, admins can still edit the content, so there aren't any real benefits to the new protection. Using cascading int-admin protection will greatly reduce the number of people able to edit ITN/DYK/OTD and other things which are regularly updated. Alongside this is a really bad idea - increase the number of int-admins. An alternative has been proposed which is to create a new user group, and a new cascading protection level, which only allows editing content displayed on the main page. No decisions have been made, and it's not always clear above exactly what people are agreeing to. The proposal itself contains this sentence, "almost all of the work is done in the background using templates — so the impact of this temporary measure is minimal", but with cascading protection that's simply not the case. -- zzuuzz (talk) 20:51, 26 November 2018 (UTC)[reply]
      Wow, clarification is needed. Adding lots more intadmins to handle all details of what is transcluded on the main page would be very dubious. Further, some templates/modules are used frequently and often appear somewhere on the main page, and people would need an intadmin to update them. Johnuniq (talk) 00:49, 27 November 2018 (UTC)[reply]

      Level 1 desysop of Killiondude

      Under the Level 1 desysopping procedures the administrator permissions of Killiondude (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) have been temporarily removed as a suspected compromised account.

      Supporting: DeltaQuad, Worm that Turned, BU Rob13.

      For the Arbitration Committee;

      -- Amanda (aka DQ) 20:33, 24 November 2018 (UTC)[reply]

      Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard#Level 1 desysop of Killiondude

      For the arbitration committee, --Cameron11598 (Talk) 23:29, 24 November 2018 (UTC)[reply]

      Return of tools

      The Arbitration Committee has verified Killiondude is back in control of their account via multiple methods. Therefore the committee reinstates their administrative userright, which was previously removed by motion. The committee also urges them to enable 2 factor authentication on their account.

      Supporting: KrakatoaKatie, Callanecc, Newyorkbrad, Premeditated Chaos, Worm That Turned, Opabinia Regalis, Mkdw, DeltaQuad.

      For the Arbitration Committee, -- Amanda (aka DQ) 22:51, 24 November 2018 (UTC)[reply]

      Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard#Return of tools

      For the arbitration committee, --Cameron11598 (Talk) 23:29, 24 November 2018 (UTC)[reply]

      Infobox and series on Donald Trump

      Hi, in light of the recent publicised vandalism on Donald Trump (The Verge, Independent), we decided to replace the primary target of the vandalism, the infobox, with a fully protected template. This means that once the temporary full protection on the main article ends business as usual can continue. However, given the discussion had a relatively low level of participation, Ymblanter suggested I make a thread here.

      Should we keep this template in the article (temporarily) or should we go back to having the infobox directly inside the article? Note that a compromised admin account could technically still vandalise the article, it would just mean they'd have to go through an extra step (that has significantly less watchers). @MelanieN, Enigmaman, Ymblanter, GreenC, Awilley, and DannyS712: Pinging those who were involved with the discussion at Talk:Donald Trump. Cheers, Anarchyte (talk | work) 09:13, 25 November 2018 (UTC)[reply]

      @Anarchyte, MelanieN, Enigmaman, Ymblanter, GreenC, Awilley, and DannyS712: While I am in favour (obviously) of stopping the vandalism, wouldn't having it located on a page with a lot less watchers be even riskier? --TheSandDoctor Talk 09:55, 25 November 2018 (UTC)[reply]
      In principle, it is correct that the template is watched by a far lower number of people, but as it is full protected, one needs another compromised admin account to vandalize it. So far all compromised admin accounts were discovered within minutes (though it still takes time to lock them). Page as it is now can be edited by extended confirmed users, and we have a plenty of extended confirmed accounts to compromise.--Ymblanter (talk) 10:06, 25 November 2018 (UTC)[reply]
      • Me thinks this to be unnecessary; though the efforts are quite well thought-out and deserves praise:-). EFs can be easily exploited.WBGconverse 12:36, 25 November 2018 (UTC)[reply]
      • This is fine as a temporary solution. The problem is that admin accounts have been compromised and the template will have far fewer watchers than the article. A solution that addresses the root cause is what we need long term. Compromised accounts have been editing the article and some related articles for more than two years. They are easily identified by their edit history. - MrX 🖋 14:17, 25 November 2018 (UTC)[reply]
      • I actually think this is a fine idea and could be maintained indefinitely. The entire infobox has been subject to lots of discussion and is now in a consensus-defined condition - so that virtually all changes to the infobox nowadays get reverted. In other words there is no problem with keeping the infobox in a permanently locked state. We would just have to make sure that lots of us put the infobox template on our watchlists. -- MelanieN (talk) 14:27, 25 November 2018 (UTC)[reply]
      I think that would be inconsistent with policy. I would strongly object to any article content that can only be edited by admins. Also, nothing prevents a compromised account from removing the template from the article, and restoring a vandalized version of the infobox. Something needs to be done about the cause. In other words, the compromised accounts.- MrX 🖋 14:33, 25 November 2018 (UTC)[reply]
      • I support this idea for this article only for a period of time needed but not forever. It's not a grand sweeping slippery slope of top down control over Wikipedia content, but a pragmatic temporary solution for a single article under special circumstances. -- GreenC 15:42, 25 November 2018 (UTC)[reply]
      • I support this as a temporary measure, but in the long(er) term suggest using an edit filter, as discussed on the talk page. This would allow constructive extended-confirmed editors (hopefully like myself) to edit the rest of the infobox, series, etc without needing to submit a protected-edit request. --DannyS712 (talk) 02:53, 26 November 2018 (UTC)[reply]

      Page history merging

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


      Hello!

      Please merge this two pages' history:

      Thank you very much! Bencemac (talk) 14:28, 25 November 2018 (UTC)[reply]

      Looking into this.--Ymblanter (talk) 14:29, 25 November 2018 (UTC)[reply]
       Done--Ymblanter (talk) 14:37, 25 November 2018 (UTC)[reply]
      @Ymblanter: Many thanks! Regards, Bencemac (talk) 14:49, 25 November 2018 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      Aditya Birla Payments Bank Undisclosed paid edits

      This has been created through by an undisclosed paid editor on Upwork. Jon posted at https://www.upwork.com/job/Wikipedia-Content-Editor_~0167379bb6e4c6a4e9/ — Preceding unsigned comment added by 189.188.64.111 (talk) 15:13, 25 November 2018 (UTC)[reply]

      the things are wrong — Preceding unsigned comment added by Zhangliping (talk • contribs) 15:29, 25 November 2018 (UTC)[reply]

      Unknown issues with oversight

      I am able to see this message on main page history without even logging in. Is there some issue with the Oversight privileges? https://drive.google.com/file/d/1xM9FCmBMGwW3Wb4x0nSFI6OOHwOYZHYj/view?usp=drivesdk — Preceding unsigned comment added by 125.63.125.251 (talk) 15:39, 25 November 2018 (UTC)[reply]

      No, just something weird with a template not substing properly. Primefac (talk) 16:23, 25 November 2018 (UTC)[reply]
      Additionally, those edits were not "oversighted" they were only "deleted", just seems like an odd template preview in mobile view. — xaosflux Talk 16:27, 25 November 2018 (UTC)[reply]

      Use of ticket system by site-banned user to get warning about abuse of email removed?

      [21]

      Courtesy pinging TheDragonFire (talk · contribs) although I must stress that this is not about them, as I suspect that there's a conflict of policy on this point, and at the very worst TDF made a good-faith mistake in carelessly not reading the messages they were blanking.

      Catflap08 (talk · contribs) last week sent me an email that would have been somewhat offensive if it didn't consist of laughably silly request that I not accuse him of being a Malaysian IP that harassed me a little before that (I had actually only mentioned him to say it clearly wasn't him or anyone who had interacted with me before 2018, as it they seemed completely unaware of my conflict with Catflap), and a year or so ago he sent me a much longer, more abusive email, which fact I was unwilling to disclose at that time. After the more recent incident, I requested he not send me any more emails or I would request his email access be revoked, and a week later the page was blanked. Curiously, he does not have talk page access disabled, so he is perfectly free to blank his page himself if he thinks policy allows him to do so, so using the ticket system is ... well, weird. It looks like he knows he's misbehaving and so wants to trick other people into covering his tracks for him.

      He's been evading his ban by editing while logged out, and his continued use of email clearly implies he does not intend to respect his SBAN, so I'm wondering what could be done about it at this point? Just remove talk and email access and leave a notice on the page asking other editors to be careful if they receive requests to "courtesy blank" the page?

      Hijiri 88 (やや) 15:42, 25 November 2018 (UTC)[reply]

      Users are entirely free to remove messages they receive on their talk pages, and it is very standard practice for OTRS to handle courtesy blanks of user talk pages to help users move on a little. If however, this user is continuing to cause disruption then by all means remove email access and SPI into oblivion. TheDragonFire (talk) 16:48, 25 November 2018 (UTC)[reply]
      it is very standard practice for OTRS to handle courtesy blanks Okay, so that's the "conflict of policy" thing I mentioned above. Our policy on blocked editors is not that they are entirely free to remove messages they receive on their talk pages when those messages are appeal denials, and while that doesn't necessarily apply to non-admin, involved warnings about abuse of the email system, we must also bear in mind that Catflap is not just blocked, he is subject a site ban (those exact words were used) and so is no longer considered to be a member of the English Wikipedia community, so standard practice when it comes to editors editing their own user pages also doesn't necessarily still apply. And yeah, Catflap has most definitely been abusing his continued permission to use email, was probably abusing the ticket system given that he still has talk page access enabled, and has been actively evading his ban apparently whenever he feels the urge to do so, so ... yeah, I think email access, and probably also talk if he's gonna continue using the ticket system, also needs to be withdrawn in this case. Hijiri 88 (やや) 00:42, 26 November 2018 (UTC)[reply]

      The guideline only relates to what the editors themselves may do, not what we may do. In any case it's irrelevant here because Catflap08 did not have anything on their page which couldn't be removed (unless it was removed before). There's definitely nothing in the guidelines which apply to warnings about misuse of the email system whether from admins or anyone else. Those can be removed at any time, just as with any other warnings.

      Also I think it's clear from many previous discussions that our blanking policy still applies no matter whether editors are cbanned or whatever else. No matter how atrocious an editor's behaviour is, we do not punish them by leaving around unnecessary content. We only keep stuff we've determined we should keep for reasons of administrative efficiency, tracking misbehaviour etc.

      I don't see any evidence of abuse of the ticket system. The fact that talk page access remains doesn't mean they are forbidden from using the ticket system to ask for stuff to be removed from their talk page especially if they are unclear on what they may do. Anyone who has dealt with this before knows there's a lot of confusion about what editors may remove from their talk page and when, and your own comment seems to support this. In fact this case seems even more confusing since IIRC they are still ibanned from interacting with you and while it seems a moot point while they are cbanned, they could have had apprehension about removing content you posted.

      I do agree from your description they have misused email and there's already justification for removal and it definitely should be remove if it continues. While I'm not completely opposed to removal of talk page access especially since they have been socking plus misusing email so are unlikely to be able to file an appeal anytime soon, but there also doesn't seem to be any real reason to do so since it doesn't seem like they've misused access. I mean they didn't even blank like they were allowed to but instead asked for it via a ticket.

      Nil Einne (talk) 09:27, 26 November 2018 (UTC)[reply]

      @Nil Einne: It's peripheral, but no, Catflap08 is not technically banned from interacting with me, except insofar as interacting with me on-wiki or by means of inappropriate use of the email function could be considered a violation of his site ban. And he knows this, because his last logged-in edit was to remove a message from me, specifically informing him of the discussion on this noticeboard to remove our IBAN. So good-faith apprehension about removing a message from me would not explain the use of OTRS. Hijiri 88 (やや) 16:15, 26 November 2018 (UTC)[reply]
      I would personally suggest that moving (calmly I might add) off-wiki after being sanctioned shows more restraint than most banned users have. Either way, if someone really wants to unblank their talk page then go right ahead, but I think it's needless grave dancing. King of Hearts or Oshwah, if you consider it prudent please flip Catflap08's TPA and email bits, and we can all have ourselves a beverage of our choice. Cheers. TheDragonFire (talk) 11:14, 26 November 2018 (UTC)[reply]
      FWIW, I suggested talk access be removed not because I think Catflap08 has been abusing his talk page privileges (how could he, when he hasn't used them in 20 months?) but because he is already acting like it has been removed. I can take that or leave it. The email thing, though ... well, I received a forwarded email from User:Sturmgewehr88 back in April 2015 that was essentially a coy, passive-aggressive forerunner to what became Catflap's recurring "Hijiri 88 and Sturmgewehr 88 are both neo-Nazis" schtick (out of context, which is how it was originally received, we both agreed it looked like weird but benign tomfoolery, but given how he later harped on about our Nazi-like usernames in public it was clearly meant as a threat), the harassing message he sent me in July 2017, and the above-mentioned email from last week, combined with the fact that he was almost definitely using email to violate our IBAN by proxy back when it was still in place ... I can't honestly think of any reason why his email access would still be enabled. Hijiri 88 (やや) 16:06, 26 November 2018 (UTC)[reply]
      I'm happy to restore remove the user's talk page access if others believe it to be necessary - just let me know. :-) ~Oshwah~(talk) (contribs) 23:43, 26 November 2018 (UTC)[reply]
      @Oshwah: There seems to be a misunderstanding. Cetflap08 already has talk page access enabled, but used the OTRS system for some reason that is difficult to take in good faith due to his block evasion and abuse of the email service. I'm fine with him maintaining talk access as long as he's not abusing it -- and I recognize that acting like he already doesn't have it is not in itself an abuse -- but he probably should have email disabled. Hijiri 88 (やや) 00:11, 27 November 2018 (UTC)[reply]
      Sorry, I used the wrong word in my response - fixed. I'll be more clear in my response here: If he's not abusing talk page access directly, then we should leave it alone. OTRS has the ability to handle issues of abuse if it's deemed to be necessary (like removing email access) - I'll leave that for them to do. If the community has any concerns or reasons why talk page access should be revoked, let me know. I apologize for my ambiguity earlier. :-) ~Oshwah~(talk) (contribs) 00:16, 27 November 2018 (UTC)[reply]

      Hzh at Sci-Hub

      prior discussions

      The content dispute is about how to describe a) how Sci-Hub obtains credentials and b) how Sci-Hub uses credentials it obtains. (Briefly, Sci-Hub obtains (through various means) legitimate user names and passwords, and presents them to libraries, misrepresenting itself as the person to whom the credentials were granted, in order to get access to paywalled content, which it then stores on its servers).

      Per the stats above, this posting is about Hzh's behavior at Talk:Sci-Hub. It is not about the content dispute. They have

      • a) WP:BLUDGEONed the talk page (the 183 edits);
      • b) continually misrepresented what other editors are saying and what sources say (see two warnings above for examples; I can provide more -- this has been incredibly frustrating); and
      • c) has always said "not this" or "not that" and never helped propose comprehensive content summarizing what the sources actually say about how the site obtains credentials (e.g diff, diff; and
      • d) in their "not this" comments, consistently
        • (i) criticized the content of the sources (e.g here with opening ground-shifting snark and here, and here) and
        • (ii) demanded that content quotes the sources, instead of summarizing them (e.,g diff, diff) and
        • (iii) constantly ground-shifting, making it impossible to move forward and resolve issues (snark diff above, see also diff, diff (what does that comment even mean?), diff bringing up other issues about "dangers" which this RfC proposal was not addressing - ARGH).

      If you try to review the talk page, you will find that almost every section is derailed, mostly by Hzh. We have not made progress resolving the issues after more than a month. Their very first comment argued strenuously that there is some actual difference between "piracy" and illegal copyright infringement. That is pretty much how it has gone since then. Guy has said to them many times that WP is not a place to RGW or where we can act as though law is not what it is, first gently and then with increasing clarity. (this is what prompted Hzh's ANI filing). To show the depth of the RGW/IDHT here, in this diff they compared copyright law to laws making homosexuality illegal. That is about as close to the Godwin's law as one can get without going there.

      This has been the definition of tendentious behavior at a talk page, and is wasting everyone's time. I am not sure what the most appropriate solution is, but some kind of restriction seems appropriate, so that we can get work done. Jytdog (talk) 02:58, 26 November 2018 (UTC)[reply]

      • This shit again? Remind me again why Hzh wasn't TBANned after the last ANI? Hijiri 88 (やや) 04:43, 26 November 2018 (UTC)[reply]
      • Reply I think it should be noted that this ANI came about after I requested opinions on RSN on a source given by Jytdog to support the content he added - [22]. He said I had misrepresented the source - Another misrepresentation, and made two demands to change. For the first demand, as I explained, it was his own confusion of "review process" with editorship (the two things are different for publication of research papers), but although many would consider the review process to be essential, it is not that an important point on the question of the validity of this particular source to waste time arguing over, I struck off the wording. However I refused to accede to his second demand, at which point he decided that I had been disruptive and that an ANI is necessary. Note also that the RSN came about only because I had questioned the source in a number of places (it was also questioned by another editor Smartse [23]), but Jytdog indicated that he would not reply to me on the source because I did not discuss it at the section he wanted it discussed - [24]. This I duly did, [25], but he chose not to reply, at which point I took the issue to the RSN [26].
      I'll address the issues involved as best as I can:
      • The questions I raised in the Sci-Hub talk page are related to the basic policies of WP:V and WP:NPOV. Allegations are stated as facts in the article, Where words like "allegedly" [27] or "publishers have alleged" [28] are found in the sources, they are ignored. I raised some of the issue at Talk:Sci-Hub#Problematic wordings.
      • If it is necessary to summarise the sources, then the sources actually need to say what the content says. Words in the sources like "allegedly" should not be ignored, and accusation should not be stated as fact. In the case of the "black market", the validity of the Scholarly Kitchen source is being examined in the RSN, and the only valid source given did not use the word "black market", and it also did not offer any evidence for the claim. Although it is asserted that the content is well-sourced, when examined closely, the sources are problematic, for example the SK article in the RSN.
      • I'm just one of a number of editors who objected to the way the word "illegal" is used (e.g. Kashmiri), and our objection had been accepted. A number of other editors also agree on NPOV, e.g. Elephanthunter on the use voice of Wikipedia [29], Guy Macon and others. The discussion on piracy is quite wide-ranging, and I would suggest that those who want to take a close look then should read the full discussion rather than address the specific here (although I won't mind discussing it here if others want to).
      • The RfC was due to the claim that proofs are unnecessary for the claims made by Guy in the article [30]. Since this is a violation of Wikipedia policies on WP:V, it made it hard to phrase it in a way that does not tell us what the answer must be.
      • As for the warnings, Jytdog issued a 3RR warning for the 2 reverts I made, but ignore the 2 reverts made by another who agreed with him [31][32]. He asked me to discuss when I was still discussing. He had actually decided to edit the article on the contested use of such words [33][34] just saying that he would not discuss further [35]. Other warnings appear to be his misunderstanding of what I wrote, and he appears to ignore my explanations. He warned about mispresentation (which appeared to his misundertandings), but misrepresented the source given (claiming that it better supported the content when that is not true) as well as what I did on the talk page e.g. You have never offered any content suggesting how to better summarize the sources, when I did in a few places, e.g. [36][37], one of which he even accepted [38].
      • I have no idea where the charge of ground-shifting comes from since they refer to different things, for example. one is about his use of a self-published attack site [39], another is about the validity of the source Scholarly Kitchen (a blog established by Society for Scholarly Publishing, therefore an organisation with a conflict of interest), while a third is a discussion on the word "fraudulent" that is not supported by the sources used, including the SK one, etc. I'm not aware that you need to discuss only one topic in different discussions. I'm not sure what issue Jytdog has with the others since it is quite clear what I wrote, for example, I stated my concerns, and that we can go back to it later. Everything may become clearer when other issues get addressed, and the RfC may become simpler. I simply don't see how I could be derailing anything. As Jytdog himself later objected to Elephanthunter's proposal, his objection should not be taken as derailing the discussion, nor indeed in other parts where Guy has agreed with my suggstions but Jytdog had objected [40]. This is just part and parcel of a discussion.
      It should be noted that many of the issues had been caused by edits by Jytdog. His behaviour has not been helpful in the discussing his edits, for example making trivial complaints about the word "darknet" I used, insisting that I used "black market" [41], then saying the two words have no important differences in meaning [42], then complained that I was too "literal" in demanding sources that support the wording [43] when the sources used don't mention "darknet" or "black market". The wording should be how he decides it to be, even when it is contested, for example the use of the word fraud and fraudulent I gave earlier - he stopped discussing [44] then made these edits [45][46].
      As for the edit counts, since I started commenting on this talk page, I have made 95 signed comments (9 more are duplication by Jytdog as he wanted to reorganised the comments), Guy made 91 (11 more are duplications by Jytdog in the reorganisation), Jytdog made 77 (these are rough counts, but the true number should not be far off). I have a higher edit count as I tend to copyedit and adjust before anyone else has replied, which is acceptable practice per WP:REDACT. If racking up edit counts because of copy-editing and adjustments before someone else has replied is not acceptable, then I apologise and will refrain from doing so again. The reason I did not make more edits to the article itself is because I thought they should be discussed properly first before they are added, and talk page is the place for discussion on contentious edits. Hzh (talk) 14:26, 26 November 2018 (UTC) (adjusted)Hzh (talk)[reply]
      To cut down on the number of edits due to copy editing and adjustments, try using 'Show preview' before you publish your changes. Preview can be used repeatedly until your edit looks the way you want it to. BlackcurrantTea (talk) 15:01, 26 November 2018 (UTC)[reply]
      That is true, and I do use it, but I will use it more often. I guess I developed the habit to avoid edit conflict where a large edit sometimes becomes lost when saving, but I guess a wall of edits by one person can be off-putting to others, so I will try to cut it down next time. Hzh (talk) 15:20, 26 November 2018 (UTC)[reply]
      What Hzh did there with "darknet" directly on point. They have been insisting on literal support for the negative ideas -- this has been a constant theme. So no, the exact word is not trivial to them at the talk page. So you see, they misrepresent things (now their own behavior) even here. Their post in general is full of distraction and ground-shifting. This is what we have been dealing with at the talk page. It is not about content. Jytdog (talk) 17:11, 26 November 2018 (UTC)[reply]
      Hzh's comment entirely exemplifies the problem. See, for example, the comment on the word "illegal". The article changed to "piracy" (a term Sci-Hub apparently embraces), but for weeks afterwards, Hzh challenged use of the word illegal even on Talk on the basis that taking credentials to which you have no right, using them to download copyright material, and offering that copyright material free to download, is somehow not "illegal" in some corner of the world he has yet to actually identify. He also relentlessly opposes the use of the term computer fraud to describe the use of other people's credentials to take material from publishers' servers, mainly because it contains the word "fraud" and in Hzh's mind Sci-Hub are brave mavericks, not crooks. The possibility that one can be both at the same time, as pretty much every single sources says Sci-Hub is, does not seem to be a valid argument to him. Guy (Help!) 17:59, 26 November 2018 (UTC)[reply]
      It seems like you are arguing you should be able to use any word just because it is the talk page, whether it is correct or not. For example you insisted all over the talk page that copyright infringement is theft, just a few here - [47][48][49], when the US Supreme Court has already specifically ruled that this is not so in the Dowling v. United States (1985) case. Perhaps if you are more careful with your wordings, others wouldn't challenged you, or are you arguing that you shouldn't be challenged in your assertions and say anything you want in the talk page? Hzh (talk) 23:29, 26 November 2018 (UTC)[reply]
      • Comment I'm involved, but this is just an ordinary content dispute and I see no need for administrative action. SmartSE (talk) 17:28, 26 November 2018 (UTC)[reply]
      I believe we could have worked out this content dispute a long time ago, if it weren't for Hzh's behavior. Jytdog (talk) 17:42, 26 November 2018 (UTC)[reply]
      • TBAN please. Hzh is basically sealioning and has been for weeks. Guy (Help!) 17:51, 26 November 2018 (UTC)[reply]
      Thus far I have seen the issue only at Sci-Hub, though presumably we'd also have to include Alexandra Elbakyan. There's been none of the pointy removals of links to Elsevier or addition of other dubious "free" links that we saw with other users. Guy (Help!) 23:47, 26 November 2018 (UTC)[reply]
      • I don't remember how I originally found the article. I came back to it because Guy invited me to on my talk. I helped negotiate the "piracy compromise" IIRC. I tried to come back to it a couple times, but the discussion was so disjointed and exceedingly difficult to make sense of, it just crossed my eyes and I went on and did something else instead.
      Umm...Hzh is incessant at editing their own comments. So any raw edit count is pretty misleading as an argument for bludgeoning. From what I can tell, they've not been super congenial on the talk, but neither has everyone else. There's walls of text here and there for sure, but they don't all belong to Hzh, nor the longest of them as far as I can tell. There is likely a good argument to be had that, when using controversial terms, we need to stick closely to what the sources say. It is perfectly possible that Hzh is only slightly sympathetic and is being wrongly characterized as (to borrow a phrase) "a fanboy". Which that phrase is not terribly helpful even if true. I don't like the idea that if "I have friends and you don't, and you're civil, then you're sealioning". That's not always the case. I tend to agree that this is a content dispute and repeated efforts by the more noticeboard-savvy-side to file noticeboard complaints is probably less evidence of a problem, and more evidence that the more noticeboard-savvy-side has tried repeatedly to seek sanctions and has failed.
      I've worked with and disagreed with both Jyt and Guy. And I admit to just not caring enough about SciHub to invest that much personal time. But it's hard to see this as more than a content dispute. GMGtalk 00:31, 27 November 2018 (UTC)[reply]

      Topic ban appeal by Sbelknap

      Sbelknap is currently topic-banned "from all articles, pages, and discussions involving finasteride, dutasteride, or sexual health, broadly construed" (per AN discussion). The user approached me a day or so ago requesting to lift the ban. I observed he had been editing and commenting on topics related in my view to sexual health, and asked to confirm he was sure he wanted to appeal to this noticeboard, noting possible adverse outcomes. In response, he explained that in his view my description of a ban on "sexual health" was vague, and so he presumed the scope of the ban based on a perfectly relevant technical criterion (you can see this conversation on my talk page); in a nutshell he interpreted "sexual health" as "sexual dysfunction", and then made every effort to abide by that restriction. I believe this misunderstanding to be genuine and in good faith: Sbelknap is a medical practitioner who has published research in this area, while I spent much of the last decade working for a sexual health education advocacy organization in an administrative capacity; it's natural that our interpretations of the broadness of "sexual health" would not align perfectly. At any rate, no other editors have seen reason to object to Sbelknap's many content contributions in the interim, as far as I can tell, except for one incident which he himself noted (again, see my talk page). As such I believe that Sbelknap has abided by the restriction in good faith (in that he has not deliberately tried to game the restriction, for example), thus I am presenting this appeal to the community without prejudice. Ivanvector (Talk/Edits) 16:58, 26 November 2018 (UTC)[reply]

      • Support in the spirit of the standard offer and AGF, with the understanding that a return to the previous form will likely result in more extensive sanctions. ——SerialNumber54129 17:19, 26 November 2018 (UTC)[reply]
      • Am posting a notice of this at WT:MED.. Jytdog (talk) 18:05, 26 November 2018 (UTC)[reply]
      • I don't think so. This was just over 6 months ago and his editing was egregious, vanity spamming and pushing a POV that he hoped to elevate from its current fringe position by popularising it through Wikipedia. Guy (Help!) 23:55, 26 November 2018 (UTC)[reply]
      • Oppose at this time. In May, I described Sbelknap as a "bullheaded editor claiming some special level of expertise as justification to push their own point of view". Before lifting the topic ban, I want to see convincing evidence that this editor has abandoned bullheadedness and POV pushing. Cullen328 Let's discuss it 01:23, 27 November 2018 (UTC)[reply]
      • oppose per Cullen --Ozzie10aaaa (talk) 10:17, 27 November 2018 (UTC)[reply]
      • Oppose the important part of WP:SO is not merely the six month wait, it's the convincing evidence that they have changed and improved. Absent clear evidence of that, the standard offer is not automatic, and I'm going to have to agree with Cullen on this. If we don't have evidence anything has changed, we have to presume they will continue. --Jayron32 17:36, 27 November 2018 (UTC)[reply]
      • Oppose What Jayron said, basically. No evidence of intent to do differently, then no change in the status quo. Courcelles (talk) 17:40, 27 November 2018 (UTC)[reply]
      • Oppose - Also per Cullen328. - FlightTime (open channel) 17:49, 27 November 2018 (UTC)[reply]
      • weak oppose - I like to assume good faith, but an appeal after six months is premature without substantial evidence of a change in behaviour. I might support an appeal in the future, e.g., after 12 months, if there are no further incidents of concern.--Literaturegeek | T@1k? 17:57, 27 November 2018 (UTC)[reply]
      I have made every effort to comply with the topic ban. The topic ban did not provide much detail, so I interpreted it as covering topics related to the ICD-10 schema for sexual dysfunction. (Shortly after the topic ban, I suggested to Doc James that he add a meta-analysis to the testosterone article, but then learned that even posting a suggestion on a talk page on a banned topic might be considered a violation of the topic ban, so I haven't done that again.) I have made more than 1,000 edits since the topic ban; I believe nearly all of these would be considered constructive by any objective standard. I have also resurrected a redirected stub for the Dietary Guidelines for Americans wikipedia article - expanding this into a decent article, and engaged in productive collaboration with numerous editors on multiple topics. (For example, chlortalidone, Long-term effects of alcohol consumption, metformin, amoxicillin, chloramphenicol, Ford Taurus, moose, and others). The question you all are asked to answer is this: does six months of diligent effort as a wikipedia editor, with many productive contributions, constitute evidence of improvement as an editor? Sbelknap (talk) 21:38, 27 November 2018 (UTC)[reply]
      • Weak oppose Well Sbelknap is getting better, they still regularly forget to sign their talk posts. And still provide undue weight to specific positions. So not ready yet for a very controversial topic area. Would recommend they try again in another six months. Doc James (talk · contribs · email) 23:14, 27 November 2018 (UTC)[reply]
      • Support per Serial Number 54129's reasoning. We actually need subject-matter professionals, working in the topics they know well. I think the opposers are asking to prove a negative. The editor hasn't been in "bullheaded editor claiming some special level of expertise as justification to push their own point of view" trouble since the T-ban (that I know of). Utter temperamental perfection isn't something we demand of people, and what is or isn't due weight in medicine is a hotly argued topic (see WT:MEDRS and its very long archives, and intense topic-by-topic debates about sourcing at topics like e-cigarettes, etc.). So there's not an objective, diffed fault I see here, but a subjective, loosey-goosey feeling, like not quite a full pound of flesh has been extracted yet. Finally, many first-time topic bans are only for 1-3 months; 6 months seems like a reasonable timespan to appeal one, by someone who's not some asshat here to convince the world that [insert religion here] is the one true way, or blithely running toward a site-ban due to aggressively promoting some company or product. PS: forgetting to sign posts, and other such trivia, has nothing to do with the matter.  — SMcCandlish ¢ 😼  01:53, 28 November 2018 (UTC)[reply]

      Community Wishlist

      People watching this page might be interested in looking through the specific category at m:Community Wishlist Survey 2019/Admins and patrollers. At the moment, the most popular proposal that is specifically admin-related is m:Community Wishlist Survey 2019/Admins and patrollers/Create an integrated anti-spam/vandalism tool.

      For the newer folks: Voting is open for approximately another four days. The Community Wishlist uses straight approval voting (i.e., "oppose votes" are pointless). Vote for as many proposals as you want. The top 10 vote-getters will be addressed by the devs. There is a ===Discussion=== section on each proposal, and that's the best place to report any concerns or document particular use cases. WhatamIdoing (talk) 19:47, 26 November 2018 (UTC)[reply]

      @WhatamIdoing, to be more accurate "oppose votes aren't counted towards the total". They're not 'pointless', since opposing something with an explanation of why you think it's a bad idea can make other potential supporters reconsider, and also acts as a marker to the devs that "although this has made it into the top ten you should probably stop and consider whether we should really be doing this". (As you know, the wishlist survey is very much an advisory referendum rather than a binding vote; if the WMF are genuinely committed to implementing any proposal that made it into the top ten regardless of how bad an idea it is, give me half an hour on Reddit and I could assemble a binding consensus to replace the death star logo on every page with goatse.) ‑ Iridescent 23:12, 26 November 2018 (UTC)[reply]
      Sigh, is there any chance of old wishes becoming fulfilled? I wished back in 2016 that you would fix the "hiding" bug (link) (The phabr ticket is from 2007 (!))...but, frankly, it looks as if the task is just shuffled from one incompetent developer to another. Huldra (talk) 23:27, 26 November 2018 (UTC)[reply]
      Personally, I use old lists to see what would be nice to work on. The Community Tech team doesn't look at them, though, so wishes that aren't taken on by the team must be resubmitted each voting period until they are. Enterprisey (talk!) 00:34, 27 November 2018 (UTC)[reply]
      Iridescent, the oppose vote (the vote itself, rather than any comments that follow it) is pointless. Informative comments about why the proposal is a bad idea (or how it must not infringe upon a particular non-obvious process, etc.), however, can be extremely helpful.
      CommTech's promise is to "address" the top 10 vote-getters. Usually, if the "addressing" is going to involve words like "the PM says you'll implement that only over his dead body", then the proposal is removed before the voting stage. But in the general case, there is a gap between "addressing" and "implementing", and I hear (although I've not bothered to check) that one or two wishes most years end up not getting implemented (e.g., if the proposal is significantly more complicated than initially estimated).
      Huldra, maybe next year we should all band together and try to push that one to the top. I think these last couple of years have shown that the first-place position goes to the organized. As it stands now, I don't think that any admin-specific proposals are likely to win. WhatamIdoing (talk) 01:46, 27 November 2018 (UTC)[reply]
      WhatamIdoing, well that bug isn't really admin-specific, it is the reason I miss out major vandalism, as changes do not come up on my watch list if there has been a bot editing after the vandalism.(You can, eg first vandalise, then at the same time add a cn template....a bot will come along in minutes and add the date to the cn template, and presto: your vandalism does not come up on peoples watch lists...) And I am totally, utterly disgusted by the incompetence of the WMF developers, who haven't managed to fix this major bug in over a decade. To be blunt: I have given up asking for anything from the WMF developers. Huldra (talk) 22:26, 27 November 2018 (UTC)[reply]

      Flag removal

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


      I am on a wikibreak from ACC, can someone remove my flag until a later time. Thank you, - FlightTime (open channel) 01:15, 27 November 2018 (UTC)[reply]

      done. --Floquenbeam (talk) 01:22, 27 November 2018 (UTC)[reply]
      Thank you :) - FlightTime (open channel) 01:24, 27 November 2018 (UTC)[reply]
      Come back soon, FlightTime! ...But ...obviously when you're ready to. ;-) ~Oshwah~(talk) (contribs) 08:39, 27 November 2018 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      Revoking rights of the following users

      These users were indefinitely blocked as a compromised account, their rollback rights have to be removed. --B dash (talk) 01:28, 27 November 2018 (UTC)[reply]

        • Why? --Floquenbeam (talk) 01:29, 27 November 2018 (UTC)[reply]
          • Yeah, I was kind of wondering. Now, I get that rollback was abused by whoever compromised the account; however, the account is globally locked and can't to anything at all at this point. Since the original owner does not appear to have attached an email address, it is very unlikely the true owner would be able to regain access to the account, so the global lock is (in all likelihood) permanent. Removing the permission won't have an impact on the account. B dash, is there some other reason to do this? Maybe we're missing something. On the other hand, I have no opposition to stripping any compromised accounts down to "confirmed user". Risker (talk) 01:36, 27 November 2018 (UTC)[reply]
            • No, just for security concern, regards. --B dash (talk) 01:43, 27 November 2018 (UTC)[reply]
              • If they do somehow regain control of the account (and it's unlocked), they would need to be given back rollback, taking up a bit of time that would have otherwise been saved. Currently, they can't do anything with it since they can't login. I don't see a reason to remove the permissions. Vermont (talk) 01:48, 27 November 2018 (UTC)[reply]
      The accounts are globally locked, meaning that login and authentication abilities for them are completely cut off and across all WMF sites and projects... they're essentially completely dead accounts and 100% inaccessible and unusable by anyone. Hence, there's no need to remove the user permissions from these accounts (see this section of Wikipedia:User access levels for the typical norm regarding this situation). If a Steward decides that unlocking the accounts are appropriate, it's because they have checked, verified, and are satisfied that the rightful owners have regained access to them. ~Oshwah~(talk) (contribs) 08:34, 27 November 2018 (UTC)[reply]
      Well technically, as the footnote you linked says, it's because we had an RfC about this, which confirmed that there's no reason to remove perms like this in situations like this. Stewards don't make enWiki policy. ~ Amory (ut • c) 12:15, 27 November 2018 (UTC)[reply]

      Unblockself right removed on wikimedia wikis

      Per T150826, admins and crats can no longer unblock themselves, unless they placed the block initially. SQLQuery me! 02:42, 27 November 2018 (UTC)[reply]

      • It should be noted for the record that this change was unilaterally and globally implemented by a few WMF devs who were aware of an ongoing discussion at WP:VPP, and arbitrarily decided to ignore it. Thanks WMF!  Swarm  talk  03:22, 27 November 2018 (UTC)[reply]
        Discussion link SQLQuery me! 03:31, 27 November 2018 (UTC)[reply]
      @Swarm: It certainly makes a change from the self-same WMF devs generally ignoring and then taking months to implement community decisions :D ACPERM, anyone...? ——SerialNumber54129 08:42, 27 November 2018 (UTC)[reply]
      Minor correction. Years, not months. --Jayron32 17:27, 27 November 2018 (UTC)[reply]
      Counterexample:
      Community making a decision: Wikipedia:Village pump (policy)/RfC: Wikimedia referrer policy
      Closing comments for above RfC: "From the below discussion, there seems to be a consensus for Question 5 (As far as possible/practical, should referrer information contain no information? (silent referrer))." and "The majority seem to favour prioritising user privacy over assisting external sites."
      WMF Ignoring the consensus of the community: Wikipedia talk:Village pump (policy)/RfC: Wikimedia referrer policy#Response to RFC.
      I'm just saying. --Guy Macon (talk) 14:30, 27 November 2018 (UTC)[reply]
      • On the whole, I'm mostly unconcerned about this. I voted the other way in the discussion, but I can also see where recent compromises to site security may have pushed the devs hand to move faster than the community would have otherwise. The self-block exemption removes most of my objections anyways (my only block was an accidental self-block that I reversed a few seconds later. It's not that hard to do when you have multiple tabs open and click the block button with the wrong tab open...), and it allows us to more quickly respond when another compromised admin account goes rogue. I'd rather it didn't have to come to this, but wishing we didn't live in a world where this was probably necessary doesn't bring that world into existence. --Jayron32 17:32, 27 November 2018 (UTC)[reply]
      • Hopefully there is also a block rate limitation, so that out-of-control blockers can be limited in their damage. Perhaps one block per minute is acceptable. Graeme Bartlett (talk) 22:15, 27 November 2018 (UTC)[reply]
      @Graeme Bartlett: Checkusers often block many accounts (easily 20+) in a single click from the CU interface.-- Jezebel's Ponyobons mots 22:27, 27 November 2018 (UTC)[reply]
      In that case we may need a limit of say 100 per hour. Graeme Bartlett (talk) 23:24, 27 November 2018 (UTC)[reply]
      Or 10 admins per hour... :) --Floquenbeam (talk) 23:42, 27 November 2018 (UTC)[reply]
      That would do! Graeme Bartlett (talk) 02:08, 28 November 2018 (UTC)[reply]

      Unblock appeal by TheGracefulSlick

      TheGracefulSlick (talk · contribs · deleted contribs · logs · filter log · block user · block log)

      TheGracefulSlick has submitted an unblock request at User talk:TheGracefulSlick#Unblock request. Per discussion of admins there, I am copying this here for community review. There is further discussion at that talk page, but the text of the main appeal is as follows:

      Over three months ago, I was blocked for socking. Wikipedia, at the time, became a unhealthy environment for me and, admittedly, faith in myself took a nose-dive. The site offers viable solutions to handle what I was putting myself through, but I failed to invest the necessary time to understand what would have worked best for me, as well as the project. Instead, I took a disruptive approach, hoping an admin would block me for my socking. Writing and my friends outside of Wikipedia have helped me rebuild my confidence. After taking a two month break from anything related to Wikipedia, I began writing articles for WikiNews. I introduced myself to entirely new editors, who welcomed me despite the behavior that led to my block. If I am granted re-entry into the community, I intend to apply the lessons the editors at WikiNews taught me. I will remove myself from controversial topic areas of Wikipedia such as present-day politics for the next six months, then honestly evaluate my progress with an administrator. I look to finish editing GA projects in my sandbox and collaborate on other historical subjects; long-term, I plan to improve the remaining studio albums by the Doors to GA status, write articles on books, and contribute more to content on women. By joining Women in Green, I look to set positive goals for my editing. In the unlikely event I find myself relapsing, I know now I have strong support in the community, to not feel ashamed to ask for help, and I have the ability to ask for a self-block. This is a route I should have understood more prior to making my mistake. If it is the opinion of the admin that my request here is insufficient or something needs clarifying regarding my plans, please prompt me further.TheGracefulSlick (talk) 21:05, 23 November 2018 (UTC)

      Note, that this unblock appeal is short of the standard 6 months, but there seemed to be agreement to test for consensus at AN. The community is invited to comment on this appeal. TonyBallioni (talk) 07:07, 27 November 2018 (UTC)[reply]

      • Support- I'm not sure what waiting another three months would accomplish. TGS is one of the good people, and I don't see much chance of a repeat of the behaviour that got him blocked. Reyk YO! 07:16, 27 November 2018 (UTC)[reply]
      • Oppose. Three months is too little time; the editor has shown far too many and too serious instances of very poor judgment, including outrageously socking in 2016 (two socks, which were attacking Garagepunk66 and masquerading as CrazyAces489). Even when confronted with clear evidence from Mike V. and DeltaQuad that CU results showed incontrovertibly that the two impersonators were TGS, he kept denying it over and over and over (see this thread and this thread). Not having learned his lesson, he socked again three months ago to cast two votes in an RFA. He also continued to harass Garagepunk66 after being unblocked from his first socking, to the point to the point that Garagepunk66 had to reach out to Bishonen to request an interaction ban [50], and even after that the harassment did not stop. Although TGS is a good content creator, I'm afraid these violations are quite egregious when taken together, and that TGS has lost the community's trust. I think that three months is too soon for an unblock. At the very least, he should wait six months, per standard offer. Softlavender (talk) 07:21, 27 November 2018 (UTC)[reply]
      • Support. Normally I'd want to wait for the usual six months Standard Offer period, but I don't see what difference that would make in this case and I see no need for it. The unblock request is one of the most open I've seen and ticks all the boxes, and I can't think how a new appeal in six months could be any better - if anything, it's a model appeal. Yes, the socking back in 2016 was bad, but it's clearly been addressed and TheGracefulSlick appears genuinely remorseful about it. There should be no element of punishment in a block, and that's all it will be if it's maintained any longer - I certainly see no justification for keeping a block in place for things that happened two years ago. Boing! said Zebedee (talk) 07:33, 27 November 2018 (UTC)[reply]
        • All of the poor behavior didn't happen two years ago -- he deliberately socked three months ago to cast two !votes in an RfA (hence the current block), when he had already been blocked as a sock previously. Also, I'm not sure if the harassment of Garagepunk66 had abated by the time TGS was blocked three months ago -- I'd like to hear from him, although I see his editing seems to have slowly petered out since June. Softlavender (talk) 07:46, 27 November 2018 (UTC)[reply]
          • I didn't mean to suggest that all of the poor behaviour was two years ago, but all much of the specific stuff that you bring up above was two years ago. Boing! said Zebedee (talk) 07:57, 27 November 2018 (UTC)[reply]
      • Split the difference This is a more self reflective and honest unblock request than most, but on the other hand, Softlavender is correct that the misconduct (which surprised me) was serious and we need a stronger commitment that harassment and socking will never, ever happen again from this editor. I suggest that we ask this editor to return in mid-January instead of three months from now, and that they offer a more detailed commitment to avoid disruptive behavior at that time, with an understanding that any more misconduct will result in a much longer block. Cullen328 Let's discuss it 07:35, 27 November 2018 (UTC)[reply]
        I also agree with Softlavender that the original socking was indeed egregious, but you do realize all that really bad stuff was two years ago, don't you? I'm surprised that you seem to think another six weeks will make any difference. Boing! said Zebedee (talk) 07:40, 27 November 2018 (UTC)[reply]
        Either they are ready, or they are not. Holding them for another 6 weeks seems purely punitive. I don't see the extra purpose it's going to serve to add that. -- Amanda (aka DQ) 08:24, 27 November 2018 (UTC)[reply]
      • Support unblock now, good editor, no reason to leave blocked. Legacypac (talk) 07:37, 27 November 2018 (UTC)[reply]
      • Comment. Earlier this year, the user joined a harassment campaign against me, which ultimately forced me to go to low activity for some time. Whereas it is good that they are capable of self-reflection, I would like to remark that socking was not the only problem with them, and I do not see references to problematic interaction with other users in the request. I will probably not oppose an unblock at this point, but I would like to see assurances that if problems re-emerge, and the user is incapable of addressing them, a block will be quickly reinstated.--Ymblanter (talk) 07:45, 27 November 2018 (UTC)[reply]
      • Split the difference Taking into consideration Ymblater and Softlavander comments I think we should wait a little longer so I support Cullen328 proposal --Shrike (talk) 07:57, 27 November 2018 (UTC)[reply]
        Again, I really don't understand how "a little longer" makes any sense at all - there isn't a specific timeout period after which it's all fine, and unblocks are decided by the quality of the appeal and not by the calendar. (Even the SO period is only a suggestion). Boing! said Zebedee (talk) 08:09, 27 November 2018 (UTC)[reply]
      • Support Yes, the SO is early, but editors of "sufficient standing" (no sitting down on the job please!) have been impressed by the thoughtful and nuanced unblock appeal to outweigh the red tape of waiting another few months. I agree that the worse behaviour was "a long time ago", while also noting that it is not long enough for the WP:ROPE to have run out.
        @Ymblanter: it is a little unfair to blame TGS for making a single comment in a discussion that involved five others, and where your severest criticism came from two admins, not TGS. ——SerialNumber54129 08:02, 27 November 2018 (UTC)[reply]
        It was not a single comment, but a series of comments, in several discussions. And, as I said, I am not opposed to an unblock, I just want to make sure it does not happen again.--Ymblanter (talk) 08:08, 27 November 2018 (UTC)[reply]
        And to make a more general point here, we all do different things and are known from different sides. It I take myself as an example, for not offending anybody else, people who work on CfD know me (hopefully) as someone who does the necessary job on a regular basis and makes sure it does not stay there longer than necessary, people who work on the Wikiproject Russia know me as a content creator working on Russian localities, and some other people who have little interaction with me beyond drama boards know me as someone who occasionally has rage outbursts and rarely says anything wothwhile listening to. Well, this is a fact, does not matter what I think about it, and I need to find some way of working in the project which would maximize my interaction with the first two groups of users and minimize my interaction with the third group. The same is valid for all of us, and the same is also valid for TheGracefulSlick. Some people know them as content creator, but some other people know them as a problematic user who can come out of nowhere to attack someone they never interacted with before, and even to engage in socking to make this more efficiently. We should show first where the bright line is - and I see a reflection on this point in the unblock request. But we also need to help them to find their place in the project provided they do not cross the bright line - and in this sense all comments are valuable, because different users know them from different sides, and having the big picture must help them to orient and to adjust their behavior.--Ymblanter (talk) 08:27, 27 November 2018 (UTC)[reply]
      • Support The appeal, above seems sincere, and there's always WP:ROPE if it goes pear-shaped. Hopefully it doesn't. Lugnuts Fire Walk with Me 08:23, 27 November 2018 (UTC)[reply]
      • It would be interesting to see a count of what percentage of ROPE unblocks end up reblocked. --Guy Macon (talk) 08:56, 27 November 2018 (UTC)[reply]
      • Oppose unless full disclosure of wrongdoings When you were blocked and apparently emailed some admins, you were told that if you appeal in six months or so, you have to be transparent about everything. Maybe you were transparent about your feelings, but you only stated that you socked because you wanted to get caught. Since the socking that led to the block isn't documented at SPI, we have to read what users like Softlavender know about it. Softlavender writes that at first you did not even admit to socking, which is pretty concerning. So it would be important to recognize all the wrongdoings at this stage to know if you own up to it. --Pudeo (talk) 08:53, 27 November 2018 (UTC)[reply]
        • Since Alex Shih wrote that message on TGS's talkpage, it would be good to have his input here. Softlavender (talk) 09:03, 27 November 2018 (UTC)[reply]
          • The impression I get from this unblock request is that TGS seems to implicate that for whatever WP:THERAPY reason, they started socking and hoped someone would block them for doing so. This seems to contradict the fact that the sock account Nobody's Keeper was created four months before I made the block. I wouldn't be opposed to early unblock but to me this unblock request is not only too early and also incomplete. Alex Shih (talk) 09:17, 27 November 2018 (UTC)[reply]
        • @Pudeo:, since your comment was seeking a response, I feel I should clarify something. Softlavender is referring to my 2016 block when I did, admittedly, deny any socking, despite obviously being behind it. I do not recall denying wrongdoing with this current offense and described everything I did here at my talk page, per Bbb23’s request. Hope that helps address your concerns.TheGracefulSlick (talk) 09:38, 27 November 2018 (UTC) (Copied from user talk page. Boing! said Zebedee (talk) 09:42, 27 November 2018 (UTC))[reply]
      • Question: How do we know that TGS is being honest about the reason for his recent socking? He blatantly and brazenly lied 24 times about his earlier socking: [51], [52], [53], [54], [55], [56], [57], [58], [59], [60], [61], [62], [63], [64], [65], [66], [67], [68], [69], [70], [71], [72], [73], [74]. This recent time, he socked to !vote twice in a borderline RfA. He says in his unblock appeal that he socked in the hopes that someone would notice and block him. If he wanted to be blocked, he could have easily asked for a self-requested block -- he's been around long enough to know about them. Softlavender (talk) 09:45, 27 November 2018 (UTC)[reply]
        Every single example of lying you have pointed out there is from two years ago. Do you have any evidence of any recent lying? Boing! said Zebedee (talk) 11:12, 27 November 2018 (UTC)[reply]
      • Oppose until disclosure of wrongdoings As mentioned above. He should at least admit to what he has done before an unblock. Still, it's easy to do this kind of write-up. Stand your guards until he admits. Oshawott 12 ==()== Talk to me! 10:05, 27 November 2018 (UTC)[reply]
      Just so Oshawott 12. You are clearly speaking from the experience that led you to warn an IP that had been blocked nearly an hour and a half earlier... ——SerialNumber54129 10:43, 27 November 2018 (UTC)[reply]
      Oh. uhm... That was embarrassing. I saw his talk, saw no warning for blanking ANI, and thought he wasn't blocked. Apparently I was wrong. By the way, I voted before I did tried to warn, so you could have noticed that too. Oshawott 12 ==()== Talk to me! 10:51, 27 November 2018 (UTC)[reply]
      I did notice, thank you. ——SerialNumber54129 11:07, 27 November 2018 (UTC)[reply]
      @Oshawott 12: Have you read the discussion on the user talk page? What is it that you think he has not yet admitted? Boing! said Zebedee (talk) 11:13, 27 November 2018 (UTC)[reply]
      We don't know if he's honest about everything yet. Even if he is, I still think he needs more time to reflect. He deserves at least 4 months before he should return. Oshawott 12 ==()== Talk to me! 14:12, 27 November 2018 (UTC)[reply]
      So you have no idea whether there are any other undisclosed wrongdoings but you're happy to accuse him of them, and you think he'll suddenly turn honest in another four weeks? Have I got that right? And where does the simple passage of a fixed amount of time for an indef-blocked user come from? What policy is that? Boing! said Zebedee (talk) 14:25, 27 November 2018 (UTC)[reply]
      • Support: They're either going to return as a good productive editor, in which case there's nothing to be served by keeping them blocked for longer, or they're going to return to their disruptive and deceptive practices, in which case we will have to deal with that when it happens. There's still nothing to be served by keeping them blocked for longer if that's the case, since we will still have a massive ANI thread and lots of bullshit being spread far and wide if they repeat their previous behaviour. I would also add, for the avoidance of doubt, further fucking about will result in my endorsement of a 2 year ban. Nick (talk) 12:10, 27 November 2018 (UTC)[reply]
      • Question:"Harassment" is discussed above, and I may have missed it, but I do not see the TheGracefulSlick addressing it. Do they have anything to say on that? Alanscottwalker (talk) 14:32, 27 November 2018 (UTC)[reply]
      • Support. It's encouraging to see TGS open up about past mistakes. It shows an objectivity which will help control problem behavior in the future. TGS has a record of excellent article creation and expansion work in music topics, and I will be glad to see an unblock. Binksternet (talk) 15:10, 27 November 2018 (UTC)[reply]
      • Support - TGS is a great net-plus editor, I think they have learned a lesson, no need to enforce the whole SO in this case. I think Nick hit the nail in the first part of their cmt. - FlightTime (open channel) 15:18, 27 November 2018 (UTC)[reply]
      • Support - Yes the behavior was egregious. Measure that against past and possible future contributions. And, we’re closer to four months than three. But mostly, this is the best phrased appeal I’ve seen in ages. O3000 (talk) 15:40, 27 November 2018 (UTC)[reply]
      • Support L293D ( • ) 15:45, 27 November 2018 (UTC)[reply]
      • Support per Nick, and noting TGS should be aware they're on their very last chance here. Courcelles (talk) 16:49, 27 November 2018 (UTC)[reply]
      • Oppose per Cullen (i.e. I endorse Cullen's suggestion to wait longer). I'm a strong believer that users who genuinely recognize their mistakes in a block appeal ought to be given a chance to demonstrate their sincerity, especially those blocked for socking since so many just go on socking. On the other hand, I'm also a strong believer that outright harassment should be punished, and in the preventive value of deterrence blocks. So, I realize this may be an unpopular opinion, but if treating this harasser harshly deters others from engaging in harassment, the block is preventive and I support it. Ivanvector (Talk/Edits) 16:52, 27 November 2018 (UTC)[reply]
        The suggestion that a block should contain an element of punishment is not merely unpopular, it is contrary to Wikipedia policy. Boing! said Zebedee (talk) 16:58, 27 November 2018 (UTC)[reply]
        • (edit conflict) Isn't that rather at odds with WP:NOTPUNITIVE? ——SerialNumber54129 17:00, 27 November 2018 (UTC)[reply]
          • @Boing! said Zebedee and Serial Number 54129: WP:NOTPUNITIVE is a contender to be the most misunderstood policy on Wikipedia, and no, Ivanvector isn't violating it here. Yes, blocks shouldn't be used purely to punish, but blocking to act as a deterrent is not only permitted, it's specifically advised in the blocking policy. I'm not saying I agree with Ivanvector here—I don't see who is being deterred by leaving TGS blocked since no other harasser is likely to be aware of this case, and if anything leaving him blocked sends the signal "once you're out you're not getting back in" and we have another Thekohser or VX4C on our hands—but his is an entirely valid viewpoint. ‑ Iridescent 17:11, 27 November 2018 (UTC)[reply]
            • The operative phrase—deter the continuation of present, disruptive behavior—specifies the disruption has to be ongoing, and I think anyone would be hard pushed to argue that disruption can be on-going after a three-month block. Sans socking of course. ——SerialNumber54129 17:19, 27 November 2018 (UTC)[reply]
            • Hmm, OK, thanks. Boing! said Zebedee (talk) 17:25, 27 November 2018 (UTC)[reply]
      • Extremely cautious support - I'm conflicted about this. This person has demonstrated a huge capacity for malice and deception, and I don't think "it was 2 years ago" is a good reason to ignore that; on the contrary, we can't ignore it. TGS has demonstrated that they're able to be willfully and persistently malicious over the long term, even to antagonize their supposed 'friend', and then turn around and play the innocent, sympathetic victim in order to escape the consequences. They had previously made a perfectly reasonable unblock request in order to get their sock unblocked so they could continue being abusive, and that was nearly a year before the socking even came to light. In that incident, they disingenuously accepted unblock conditions, which they proceeded to ignore. Once they were blocked for socking, they repeatedly played an innocent victim. Then, as of this year, they're still socking. I'm definitely more hesitant than these other supporters to take their statement at face value; this is clearly a person who knows what they're supposed to say, but not necessarily someone whose words should be trusted implicitly, and I'm wondering why everyone is so impressed by it. That said, TGS is a huge asset to the project, and, as far as we know, is currently only blocked for double voting in an RfA. But if that attempt had not been caught, I wonder how far the socking would have gone. I'm inclined to support an early SO unblock, but it should be understood that this is certainly a 'last chance', and I would also support a long term ban should there be any further issues.  Swarm  talk  17:07, 27 November 2018 (UTC)[reply]
      • Support TGS's work on another Wikimedia site (as they said in their unblock request) shows they can be productive again and they are contrite so I would give them another shot. JC7V (talk) 17:53, 27 November 2018 (UTC)[reply]
      • Cautious Support - I'd like to support unreservedly because of the many extremely productive things TGS has done here, and I've certainly never had anything but positive interactions with them. But TGS has also shown a callous, manipulative side which is hard to ignore. I'm supporting because I see no difference whether we unblock now or unblock later. If no further disruption occurs then I'm mighty glad and welcome back! If further disruption occurs, might as well get it over with. 78.26 (spin me / revolutions) 18:05, 27 November 2018 (UTC)[reply]
      • Oppose: I dislike the support votes basically saying that there should be one set of rules for editors perceived as "extremely productive" and another for everybody else. I too have seen the callous, manipulative side of Grace, and that combined with the actions that led to her block in the first place have not really engendered any sympathy on my part pbp 18:19, 27 November 2018 (UTC)[reply]
      • There is absolutely no reason why we should not take the utility of an editor into account when considering an unblock. That's not to say that highly productive editors should get a free pass on disruptive behaviour, but there's certainly far more logic in unblocking a productive editor than one whose editing history is, for example, mostly arguing at the talk pages of contentious articles. Black Kite (talk) 18:53, 27 November 2018 (UTC)[reply]
      • Conditional support - I support the use of rope, provided we aren't fooled more than once by sincere heartfelt appeals from the same editor. We either get a productive editor back, new and improved, or we shorten the path to community ban. Either way it's a win for the project. But the italicized part is crucial and, from what I've seen, anything but guaranteed. If the community is unwilling to accept that condition, count me as an Oppose—and as a Strong Oppose in any future sincere heartfelt appeal that I'm not around to respond to. ―Mandruss  19:15, 27 November 2018 (UTC)[reply]
      • Regarding the difference between appealing after three months and six months: patience is one of the key desirable characteristics in a Wikipedia editor, particularly one who's had issues with collaboration. Although it can be difficult to demonstrate other improvements in one's behaviour while blocked, demonstrating patience is more straightforward, by waiting for the period of time that the community generally accepts as a minimum. I believe we should be encouraging blocked editors to take the opportunity to show their patience. isaacl (talk) 19:17, 27 November 2018 (UTC)[reply]
      • Oppose currently / Support after 6 months - I would like to get TGS back to productive editing, but their violations were egregious enough that shortening the time period before the standard offer can come into play does not seem warranted. Double voting at RfA and AfD is, to me, well beyond the pale, as is the behavior described by Swarm, so I see no reason that we should bend over backwards to unblock at this time. So I add my voice to those who hold that TGS should be unblocked as a matter of course, but only after the block has run for 6 months, barring any additional information whichmight come to light in the meantime. Beyond My Ken (talk) 19:26, 27 November 2018 (UTC)[reply]
      • Support as noted above was two years ago. Govindaharihari (talk) 19:41, 27 November 2018 (UTC)[reply]
      • Support - Usually I would scream "Wait 6 monhths" like a banshee but in this case I feel remaining blocked is punitive rather than productive, The unblock request is very open and honest so in this specific case I would support unblocking. –Davey2010Talk 19:59, 27 November 2018 (UTC)[reply]
      • Cautious support, primarily per B!sZ. We can always reblock if needed. Miniapolis 23:12, 27 November 2018 (UTC)[reply]

      When is a name problematic enough to be immediately hardblocked?

      I noticed earlier today the block of User:Nevergonnagiveyouup69 by User:Drmies as a "Username violation, hard block" one minute after creation of the account, and without any edits. I feel that this username, while it can be read in ways indicating disruption, isn't unambiguously so, and could just as easily be the name of an innocent, well-meaning editor. Drmies disagrees, stating "The combination of rickrolling and 69 (sex position) should be enough". Some clarification would be nice whether such a name really warrants immediate hardblocking without warnings or explanation towards the editor, or whether such blocking is WP:BITEy. Fram (talk) 19:32, 27 November 2018 (UTC)[reply]

      • Is someone naming themselves after a years-old meme likely here to contribute constructively? I don't know, I probably would have waited for the account to edit, but WP:DISRUPTNAME is probably not too far off. I pretty much just assume Drmies knows what he's doing - the fact that the account was one minute old might be more relevant to this than you can see on the surface. Ivanvector (Talk/Edits) 19:38, 27 November 2018 (UTC)[reply]
      • (edit conflict) Unless there's something oversighted, awful block. Drmies, what the hell? Rick Astley is still a huge star in the UK (I can't speak for elsewhere) and there are about a zillion legitimate uses of the number "69"; this editor could have been born in 1969, be a fan of Deep Purple, the Magnetic Fields or Bryan Adams, or just be the 69th person to use the name somewhere and have accepted the autosuggestion. ‑ Iridescent 19:39, 27 November 2018 (UTC)[reply]
      • In the last week a bunch of odd username accounts (if there are references to memes or other stuff, I have no clue). Just like the one blocked by Drmies, none of them edited except one, who made one vandalistic edit. I blocked that one user, left the others alone, mainly because of my cluelessness in this area. Iridescent, please try to be less tactful in your comments. Far too sweet.--Bbb23 (talk) 19:50, 27 November 2018 (UTC)[reply]
      • It's borderline, and I'd have erred on the side of not blocking. Waiting for the first edit on borderline accounts is fine by me. I usually only instablock accounts with obviously vulgar (the seven dirty words is a good start), bigotted, or otherwise obvious-its-a-returning-troll type stuff. For things that are just mildly rude (like the number 69) or questionable, I'll keep their contribs list tab open on my browser for a few minutes just to see if they do anything that is a problem. Otherwise, I'll let that stuff go. This one, to me, is clearly in the "watch but don't block yet" category. "Fuckrickastleysmother69" would be the sort of thing i'd have instablocked. --Jayron32 20:09, 27 November 2018 (UTC)[reply]
      • The worst thing here is that I now have that damn song in my head. I'm literally mad with with rage. Lugnuts Fire Walk with Me 20:56, 27 November 2018 (UTC)[reply]
      • Oh, I see. This is actually just a move in a pissing contest at Drmies' arbcom election questions page; Fram's just digging thru Drmies' contribs, looking for ammunition. Which is a dick move and shouldn't really be rewarded. But since the affected user isn't part of the muckracking, and since there's clear consensus here that the block was too soon, I'll unblock. --Floquenbeam (talk) 21:13, 27 November 2018 (UTC)[reply]
        • That's fine, Floq, thank you, but be careful with handing out ROPE to an editor when Fram is involved. Drmies (talk) 21:31, 27 November 2018 (UTC)[reply]
        • BTW I don't think that the unblock is a reward for the dick move. If there's a consensus to unblock, there's a consensus to unblock, which I gladly accept--the unblock is on the merits of the case, not a comment on who brought it up, and I thank Fram for bringing it up. Drmies (talk) 21:33, 27 November 2018 (UTC)[reply]
          • But... that's exactly what I said... ---Floquenbeam (talk) 21:35, 27 November 2018 (UTC) Wait, I think I misread; you're agreeing with me, right? For some reason I read that as a disagreement the first time thru. --Floquenbeam (talk) 21:37, 27 November 2018 (UTC)[reply]
            • |Hmm "dick move" may be true, who knows, but the unblock, if by consensus, is fine. And if the unblock is fine it doesn't matter who brought it up or for what reason. Is that better? ;) So I agree with your unblock, and I don't agree with seeing it as a reward for a dick move, and so I think you don't have to feel bad about it (if you were). Now let's all have some hot chocolate. Drmies (talk) 01:10, 28 November 2018 (UTC)[reply]
              • There's more than one sex position? ―Mandruss  02:23, 28 November 2018 (UTC)[reply]
      • Events had moved beyond this thread before I saw it, but for what it's worth, I think this was a reasonable username block. The odds that this is a good-faith editor are minimal. Newyorkbrad (talk) 21:57, 27 November 2018 (UTC)[reply]
        What are the odds of any new account being a good-faith editor? DuncanHill (talk) 22:01, 27 November 2018 (UTC)[reply]
        This question probably has a precise answer (which I do not know), but my guess is above 99%.--Ymblanter (talk) 22:07, 27 November 2018 (UTC)[reply]
        By DuncanHill's logic none of us should be having this conversation. We were all babies once. It's a bit paradoxical as who would there be to block the new users.--Bbb23 (talk) 22:49, 27 November 2018 (UTC)[reply]
        Not my logic, Brad's. DuncanHill (talk) 23:08, 27 November 2018 (UTC)[reply]

      Leave a Reply