Wikipedia:Administrators' noticeboard: Difference between revisions

Source: Wikipedia, the free encyclopedia.
Content deleted Content added
Monty845 (talk | contribs)
→‎Intervention, and possible block, for VarunFEB2003: Close: Consensus for Indef Block, no appeal for 3 months. No consensus on whether it should be called a block or ban
Line 716: Line 716:
A prolific sock puppeteer is currently using my signature to leave false warning templates on the Talk Pages of various users ([https://en.wikipedia.org/w/index.php?title=User_talk%3ADangerousJXD&type=revision&diff=743985513&oldid=743769691]). I suspect that the same user may have been behind [https://en.wikipedia.org/wiki/User:DangerouslyJXD this] impersonation account. If you receive any reports from someone appearing to be me, I would suggest making sure it actually is before taking it seriously. '''[[User:Darkknight2149|Dark]]'''[[User talk:Darkknight2149|Knight]]'''[[Special:Contributions/Darkknight2149|2149]]''' 15:45, 12 October 2016 (UTC)
A prolific sock puppeteer is currently using my signature to leave false warning templates on the Talk Pages of various users ([https://en.wikipedia.org/w/index.php?title=User_talk%3ADangerousJXD&type=revision&diff=743985513&oldid=743769691]). I suspect that the same user may have been behind [https://en.wikipedia.org/wiki/User:DangerouslyJXD this] impersonation account. If you receive any reports from someone appearing to be me, I would suggest making sure it actually is before taking it seriously. '''[[User:Darkknight2149|Dark]]'''[[User talk:Darkknight2149|Knight]]'''[[Special:Contributions/Darkknight2149|2149]]''' 15:45, 12 October 2016 (UTC)
:I have semi-protected [[User talk:DangerousJXD]] &mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 15:52, 12 October 2016 (UTC)
:I have semi-protected [[User talk:DangerousJXD]] &mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 15:52, 12 October 2016 (UTC)

== [[Wikipedia:Arbitration/Requests/Case/The Rambling Man]] ==

An arbitration case regarding The Rambling man has now closed and the final decision is viewable at the link above. The following remedies have been enacted:
#{{user|The Rambling Man}}'s resignation as an administrator is to be considered under controversial circumstances, and so his administrator status may only be regained via a successful [[WP:RFA|request for adminship]].
#{{user|The Rambling Man}} is prohibited from insulting and/or belittling other editors. If The Rambling Man finds himself tempted to engage in prohibited conduct, he is to [[Wikipedia:Dispute resolution#Disengage|disengage]] and either let the matter drop or refer it to another editor to resolve. If however, in the opinion of an uninvolved administrator, The Rambling Man does engage in prohibited conduct, he may be blocked for a duration consistent with the [[Wikipedia:Blocking_policy#Duration_of_blocks|blocking policy]]. The first four blocks under this provision shall be arbitration enforcement actions and may only be reviewed or appealed at the [[Wikipedia:Arbitration/Requests/Enforcement|arbitration enforcement noticeboard]]. Should a fifth block prove necessary, the blocking administrator must notify the Arbitration Committee of the block via a [[Wikipedia:Arbitration/Requests/Clarification and Amendment|Request for Clarification and Amendment]] so that the remedy may be reviewed. The enforcing administrator may also at their discretion fully protect The Rambling Man's talk page for the duration of the block.<p>Nothing in this remedy prevents enforcement of policy by uninvolved administrators in the usual way.
#{{user|The Rambling Man}} and {{user|George Ho}} are indefinitely prohibited from [[WP:IBAN|interacting with, or commenting on]], each other anywhere on Wikipedia (subject to the [[Wikipedia:Banning policy#Exceptions to limited bans|ordinary exceptions]]).
#{{user|George Ho}} is indefinitely restricted from participating in selecting main page content. For clarity, this means he may not participate in:
#:# Any process in which the content of the main page is selected, including [[WP:DYK|Did you know?]], [[WP:ITN|In the news]], [[WP:OTD|On this day]], [[WP:TFA|Today's featured article]], [[WP:TFL|Today's featured list]], and [[WP:TFP|Today's featured picture]].
#:# Any process in which possible problems with the content of the main page are reported, including [[WP:ERRORS]] and [[Talk:Main Page]].
#:# Any discussion about the above processes, regardless of venue.
#:He may edit articles linked from or eligible to be linked from the main page (e.g., the current featured article) and may participate in content review processes not directly connected to main page content selection (e.g., reviewing [[WP:FAC|Featured article candidates]]). He may request reconsideration of this restriction twelve months after the enactment of this remedy, and every six months thereafter.
#The community is encouraged to review the selection process for the [[WP:DYK|Did you know]] and [[WP:ITN|In the news]] sections of the main page. The community is also reminded that they may issue topic bans without the involvement of the Arbitration Committee if consensus shows a user has repeatedly submitted poor content, performed poor reviews, or otherwise disrupted these processes.

For the Arbitration Committee, [[User:Ks0stm|<font color="009900">'''Ks0stm'''</font>]] <sup>([[User talk:Ks0stm|T]]•[[Special:Contributions/Ks0stm|C]]•[[User:Ks0stm/Guestbook|G]]•[[User:Ks0stm/Email|E]])</sup> 05:01, 13 October 2016 (UTC)
:Discuss this at: '''[[Wikipedia talk:Arbitration Committee/Noticeboard#Wikipedia:Arbitration/Requests/Case/The Rambling Man]]'''

Revision as of 05:01, 13 October 2016

    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)

    Template:Active editnotice

      You may want to increment {{Archive basics}} to |counter= 38 as Wikipedia:Closure requests/Archive 37 is larger than the recommended 150Kb.

      Use the closure requests noticeboard to ask an uninvolved editor to

      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

      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.

      move discussion
      processes have more rules for non-admins to follow.

      Technical instructions for closers

      Please append {{

      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

      Wikipedia:Administrators'_noticeboard/IncidentArchive1156#Boomerang_topic_ban_proposal_for_User:Hcsrctu

      (Initiated 26 days ago on 9 May 2024) Ratnahastin (talk) 03:35, 28 May 2024 (UTC)[reply]

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

      Requests for comment

      RfC: Change INFOBOXUSE to recommend the use of infoboxes?

      (Initiated 80 days ago on 15 March 2024) Ready to be closed. Charcoal feather (talk) 17:02, 27 April 2024 (UTC)[reply]

      new closer needed
      The following discussion has been closed. Please do not modify it.
      Before I try to close this I wanted to see if any editors believed I am
      WP:INVOLVED. I have no opinions on the broader topic, but I have previously participated in a single RfC
      on whether a specific article should include an infobox. I don't believe this makes me involved, as my participation was limited and on a very specific question, which is usually insufficient to establish an editor as involved on the broader topic, but given the strength of opinion on various sides I expect that any result will be controversial, so I wanted to raise the question here first.
      If editors present reasonable objections within the next few days I won't close; otherwise, unless another editor gets to it first, I will do so. BilledMammal (talk) 04:43, 13 May 2024 (UTC)[reply]
      I am involved in the underlying RfC, but my opinion on the issue is not particularly strong and I am putting on my closer hat now. Per WP:INVOLVED, "[i]nvolvement is construed broadly by the community". In the Rod Steiger RfC, you stated: [T]o the best of my knowledge (although I have not been involved in these discussions before) every recent RfC on including an infobox has been successful. From this it is clear that the topic is settled, and insisting on RfC's for every article risks becoming disruptive. Although the underlying RfC was on a very specific question, your statement touches on the broader question of whether editors should be allowed to contest including an infobox in a particular article, a practice that you said risks becoming disruptive because the topic is settled. That makes you involved—construing the term broadly—because answering this RfC in the affirmative would significantly shift the burden against those contesting infoboxes in future discussions. That said, if you can put aside your earlier assessment of consensus and only look at the arguments in this RfC, I don't see an issue with you closing. It wouldn't be a bad idea to disclose this at the RfC itself, and make sure that nobody there has any objections. voorts (talk/contributions) 21:43, 18 May 2024 (UTC)[reply]
      Pinging @BilledMammal. voorts (talk/contributions) 21:45, 18 May 2024 (UTC)[reply]
      if you can put aside your earlier assessment of consensus and only look at the arguments in this RfC, I don't see an issue with you closing; per
      WP:IDHT
      issue, but it can also indicate that a local consensus is out of step with broader community consensus. Either way, additional local discussions are unlikely to be productive, but a broader discussion might be.
      Per your suggestion I'll leave a note at the RfC, and see if there are objections presented there or here. BilledMammal (talk) 02:37, 21 May 2024 (UTC)[reply]
      I don’t think that !voting in an RfC necessarily equates to being too involved, but in this case, the nature of your !vote in the Steiger RfC was concerning enough to be a red flag. Is it still your contention that “every recent RfC on including an infobox has been successful. From this it is clear that the topic is settled, and insisting on RfC's for every article risks becoming disruptive”? That was wrong (and rather chilling) when you wrote it and is still wrong (and still chilling) now, as the current RfC makes rather clear. - SchroCat (talk) 03:30, 21 May 2024 (UTC)[reply]
      Is it still your contention that “every recent RfC on including an infobox has been successful. From this it is clear that the topic is settled, and insisting on RfC's for every article risks becoming disruptive”? No. I've only skimmed the RfC, but I see that while a majority have been successful a non-trivial number have not been - and the percentage that have not been has increased recently. BilledMammal (talk) 04:13, 21 May 2024 (UTC)[reply]
      Part of my problem is that you said it in the first place. It was incorrect when you first said it and it comes across as an attempt to shut down those who hold a differing opinion. As you're not an Admin, I'm also not sure that you can avoid
      WP:BADNAC, both of which seem to suggest that controversial or non-obvious discussions are best left to Admins to close. - SchroCat (talk) 06:44, 21 May 2024 (UTC)[reply
      ]
      In general, any concern that
      WP:IDHT
      behavior is going on could be seen as an attempt to shut down those who hold a differing opinion. I won't close this discussion, though generally I don't think that raising concerns about conduct make an editor involved regarding content.
      However, I reject BADNAC as an issue, both here and generally - I won't go into details in this discussion to keep matters on topic, but if you want to discuss please come to my talk page. BilledMammal (talk) 07:53, 21 May 2024 (UTC)[reply]
      There was no IDHT behaviour, which was the huge flaw in your comment. You presumed that "every recent RfC on including an infobox has been successful", which was the flawed basis from which to make a judgement about thinking people were being disruptive. Your opinion that there was IDHT behaviour which was disruptive is digging the hole further: stop digging is my advice, as is your rejection of WP:BADNAC ("(especially where there are several valid outcomes) or likely to be controversial"), but thank you for saying you won't be closing the discussion. - SchroCat (talk) 08:10, 21 May 2024 (UTC)[reply]

      Talk:Ariana Grande#RFC: LEAD IMAGE

      (Initiated 61 days ago on 4 April 2024) This RFC was kind of a mess and I don't think any consensus came out of it, but it could benefit from a formal closure so that interested editors can reset their dicussion and try to figure out a way forward (context: several editors have made changes to the lead image since the RFC discussion petered out, but these were reverted on the grounds that the RFC was never closed). Note that an IP user split off part of the RFC discussion into a new section, Talk:Ariana Grande#Split: New Met Gala 2024 image. Aoi (青い) (talk) 22:52, 1 June 2024 (UTC)[reply]

      WP:RSN#RFC:_The_Anti-Defamation_League

      (Initiated 58 days ago on 7 April 2024) Three related RFCs in a trench coat. I personally think the consensus is fairly clear here, but it should definitely be an admin close. Loki (talk) 14:07, 6 May 2024 (UTC)[reply]

      Wikipedia:Requests for comment/Enforcing ECR for article creators

      (Initiated 57 days ago on 8 April 2024) Discussion appears to have died down almost a month after this RfC opened. Would like to see a formal close of Q1 and Q2. Awesome Aasim 00:11, 8 May 2024 (UTC)[reply]

      Talk:Brothers of Italy#RfC on neo-fascism in info box 3 (Effectively option 4 from RfC2)

      (Initiated 56 days ago on 8 April 2024) Clear consensus for change but not what to change to. I've handled this RfC very badly imo. User:Alexanderkowal — Preceding undated comment added 11:50, 1 May 2024 (UTC)[reply]

       Comment: The RfC tag was removed the same day it was started. This should be closed as a discussion, not an RfC. voorts (talk/contributions) 22:03, 18 May 2024 (UTC)[reply]

      Talk:Mukokuseki#RfC on using the wording "stereotypically Western characteristics" in the lead

      (Initiated 54 days ago on 11 April 2024) ☆SuperNinja2☆ TALK! 09:41, 21 May 2024 (UTC)[reply]

      See Talk:Mukokuseki#Close Plz 5/21/2024 Orchastrattor (talk) 20:34, 21 May 2024 (UTC)[reply]

      Talk:SpaceX Starship flight tests#RfC: Should we list IFT mission outcome alongside launch outcome?

      (Initiated 44 days ago on 20 April 2024) An involved user has repeatedly attempted to close this after adding their arguments. It's a divisive topic and a close would stop back and forth edits. DerVolkssport11 (talk) 12:42, 22 May 2024 (UTC)[reply]

      To clarify, the RfC was closed in this dif, and an IP editor unclosed it, with this statement: "involved and pushing"
      In just over an hour, the above editor voiced support for the proposal.
      I reclosed it, and the same IP opened the RfC again, with this message: "pushing by involved users so ask for more comments".
      I reclosed once more. And then the editor who opened this requests opened it. To avoid violated WP:3RR, I have not reclosed it, instead messaging the original closer to notify them.
      The proposal itself was an edit request that I rejected. The IP who made the request reopened the request, which I rejected once more. They then proceeded to open an RfC. Redacted II (talk) 12:58, 22 May 2024 (UTC)[reply]

      Talk:Hunter Biden#RfC: Washington Post report concerning emails

      (Initiated 40 days ago on 24 April 2024) There's been no comments in 5 days. TarnishedPathtalk 03:20, 22 May 2024 (UTC)[reply]

      Talk:International Churches of Christ#RfC: Ongoing court cases involving low profile individuals

      (Initiated 33 days ago on 2 May 2024) RfC template has been removed by the bot. TarnishedPathtalk 13:21, 3 June 2024 (UTC)[reply]

      Talk:Andy Ngo#RfC: First sentence of the lead

      (Initiated 31 days ago on 3 May 2024) Discussion has slowed with only one !vote in the last 5 days. TarnishedPathtalk 11:09, 2 June 2024 (UTC)[reply]

      Talk:Ben Roberts-Smith#RFC: War criminal in first sentence of the lede

      (Initiated 27 days ago on 8 May 2024) Last !vote was 27 May, 2024. Note: RfC was started by a blocking evading IP. TarnishedPathtalk 11:23, 3 June 2024 (UTC)[reply]

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

      Deletion discussions

      XFD backlog
      V Mar Apr May Jun Total
      CfD 0 9 36 0 45
      TfD 0 0 12 0 12
      MfD 0 0 2 0 2
      FfD 0 0 4 0 4
      RfD 0 2 23 0 25
      AfD 0 0 0 0 0

      WP:Redirects for discussion/Log/2024 May 11#Colonia Ulpia Traiana

      (Initiated 66 days ago on 30 March 2024) * Pppery * it has begun... 22:35, 31 May 2024 (UTC)[reply]

      Wikipedia:Redirects for discussion/Log/2024 April 24#Phone computer

      (Initiated 63 days ago on 2 April 2024) * Pppery * it has begun... 22:35, 31 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 April 21#Category:Crafts deities

      (Initiated 61 days ago on 3 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 April 23#Category:Mohave tribe

      (Initiated 58 days ago on 6 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 April 27#Category:Unrecognized tribes in the United States

      (Initiated 58 days ago on 7 April 2024) This one has been mentioned in a news outlet, so a close would ideally make sense to the outside world. HouseBlaster (talk · he/him) 13:56, 17 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 April 27#Category:Indian massacres

      (Initiated 57 days ago on 7 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 April 23#Category:Dos Santos family (Angolan business family)

      (Initiated 57 days ago on 8 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 April 27#Category:Volodimerovichi family

      (Initiated 57 days ago on 8 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

      Wikipedia:Redirects for discussion/Log/2024 May 13#Genie (feral child and etc.

      (Initiated 56 days ago on 9 April 2024) mwwv converseedits 18:02, 29 May 2024 (UTC)[reply]

      Wikipedia:Redirects for discussion/Log/2024 May 6#Larissa Hodge

      (Initiated 56 days ago on 9 April 2024) * Pppery * it has begun... 22:35, 31 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 April 29#Category:Muppet performers

      (Initiated 53 days ago on 12 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 April 30#Category:First Nations drawing artists

      (Initiated 51 days ago on 13 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

      Wikipedia:Redirects for discussion/Log/2024 April 30#Jackahuahua

      (Initiated 50 days ago on 14 April 2024) * Pppery * it has begun... 22:35, 31 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 April 30#Category:Neo-Latin writers

      (Initiated 50 days ago on 15 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

      Wikipedia:Redirects for discussion/Log/2024 May 1#Hornless unicorn

      (Initiated 47 days ago on 17 April 2024) * Pppery * it has begun... 22:35, 31 May 2024 (UTC)[reply]

      Wikipedia:Redirects for discussion/Log/2024 May 19#Dougie (disambiguation)

      (Initiated 46 days ago on 18 April 2024) * Pppery * it has begun... 22:35, 31 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 May 13#Category:Pocatello Army Air Base Bombardiers football seasons

      (Initiated 40 days ago on 24 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

      Wikipedia:Redirects for discussion/Log/2024 May 13#Sucking peepee

      (Initiated 40 days ago on 24 April 2024) * Pppery * it has begun... 22:35, 31 May 2024 (UTC)[reply]

      Wikipedia:Redirects for discussion/Log/2024 May 6#Supplemental Result

      (Initiated 40 days ago on 25 April 2024) * Pppery * it has begun... 22:35, 31 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 May 4#Category:Fictional West Asian people

      (Initiated 38 days ago on 26 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 May 4#Natural history

      (Initiated 38 days ago on 26 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 May 13#Category:Fictional animals by taxon

      (Initiated 38 days ago on 27 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 May 13#Roman Catholic bishops in Macau

      (Initiated 36 days ago on 28 April 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

      Wikipedia:Redirects for discussion/Log/2024 June 3#Frances and Richard Lockridge

      (Initiated 34 days ago on 30 April 2024) * Pppery * it has begun... 22:35, 31 May 2024 (UTC)[reply]

      Wikipedia:Miscellany for deletion/Wikipedia:Stress marks in East Slavic words

      (Initiated 29 days ago on 6 May 2024) * Pppery * it has begun... 17:30, 19 May 2024 (UTC)[reply]

      Wikipedia:Miscellany for deletion/Draft:Amina Hassan Sheikh

      (Initiated 28 days ago on 6 May 2024) If the consensus is to do the selective histmerge I'm willing to use my own admin tools to push the button and do it. * Pppery * it has begun... 17:07, 24 May 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 May 17#Category:Extinct Indigenous peoples of Australia

      (Initiated 25 days ago on 9 May 2024) * Pppery * it has begun... 22:53, 31 May 2024 (UTC)[reply]

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

      Other types of closing requests

      Talk:Tamil_genocide#Merge_proposal

      (Initiated 76 days ago on 19 March 2024) Merge discussion which has been occurring since 19 March 2024. Discussion has well and truly slowed. TarnishedPathtalk 14:34, 31 May 2024 (UTC)[reply]

      Talk:Rupert_Sheldrake#Talkpage_"This_article_has_been_mentioned_by_a_media_organization:"_BRD

      (Initiated 48 days ago on 16 April 2024) - Discussion on a talkpage template, Last comment 6 days ago, 10 comments, 4 people in discussion. Not unanimous, but perhaps there is consensus-ish or strength of argument-ish closure possible. Gråbergs Gråa Sång (talk) 07:24, 23 April 2024 (UTC)[reply]

      It doesn't seem to me that there is a consensus here to do anything, with most editors couching their statements as why it might (or might not) be done rather than why it should (or should not). I will opine that I'm not aware there's any precedent to exclude {{Press}} for any reason and that it would be very unusual, but I don't think that's good enough reason to just overrule Hipal. Compassionate727 (T·C) 01:01, 13 May 2024 (UTC)[reply]

      Talk:Press_Your_Luck_scandal#Separate_articles

      (Initiated 32 days ago on 2 May 2024) Please review this discussion. --Jax 0677 (talk) 01:42, 11 May 2024 (UTC)[reply]

      Talk:Republican_Party_(United_States)#Poll:_Should_the_article_include_a_political_position_for_the_Republican_Party_in_the_infobox?

      (Initiated 20 days ago on 14 May 2024) The topic of this poll is contentious and has been the subject of dozens of talk page discussions over the past years, so I am requesting an uninvolved editor to close this discussion. Cortador (talk) 20:28, 29 May 2024 (UTC)[reply]

      Talk:Prosecution of Donald Trump in New York#Merge proposal

      (Initiated 4 days ago on 30 May 2024) Commentators are starting to ask for a speedy close. -- Beland (talk) 06:18, 3 June 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 (34 out of 7803 total) (Purge)
      Page Protected Expiry Type Summary Admin
      2024 ICC Men's T20 World Cup Group A 2024-06-04 02:18 2024-06-11 02:18 move
      Move warring
      : per RFPP
      Daniel Case
      Robert Adams (spiritual teacher) 2024-06-04 01:59 2024-06-25 01:59 edit,move
      Edit warring / content dispute
      : per RFPP
      Daniel Case
      Rescue of Ori Megidish 2024-06-04 00:52 indefinite edit,move
      Arbitration enforcement
      ScottishFinnishRadish
      Combat operations in 1964 during the Indonesia–Malaysia confrontation 2024-06-03 23:20 2024-07-03 23:20 edit,move Persistent
      WP:RfPP
      Daniel Quinlan
      User talk:Leonidlednev 2024-06-03 22:41 2024-10-08 05:50 move Persistent vandalism Daniel
      Clancy (album) 2024-06-03 22:03 2024-07-03 22:03 move Persistent vandalism and disruptive editing Carlosguitar
      Israel–Maldives relations 2024-06-03 21:13 2025-06-03 21:13 edit,move
      WP:RfPP
      Daniel Quinlan
      Sporting CP 2024-06-03 17:42 2024-09-03 17:42 edit,move Persistent disruptive editing: Enough. ECR protected. Black Kite
      Economy of England 2024-06-03 09:21 2026-06-03 09:21 edit,move Persistent
      WP:RfPP
      Daniel Quinlan
      Draft:Yash Shah 2024-06-03 01:47 indefinite create
      Repeatedly recreated
      Daniel Case
      Joseph Kallarangatt 2024-06-02 20:25 indefinite edit,move Persistent disruptive editing: per RFPP; raising to ECP Daniel Case
      Wikipedia:Articles for deletion/Unzela Khan 2024-06-02 20:21 2024-06-09 20:21 edit Persistent vandalism Star Mississippi
      Template:Copy to Wikimedia Commons in 2024-06-02 18:00 indefinite edit,move High-risk template or module: 2571 transclusions (more info) MusikBot II
      Battle of Sulaymaniyah (1991) 2024-06-01 21:55 indefinite edit,move
      WP:CT/KURD
      Daniel Quinlan
      Hossein Kamalabadi 2024-06-01 21:06 indefinite create
      Repeatedly recreated
      Extraordinary Writ
      Free Palestine Party 2024-06-01 20:32 indefinite edit,move
      Contentious topic
      restriction: per RFPP and ARBPIA
      Daniel Case
      List of characters in Yeh Rishta Kya Kehlata Hai 2024-06-01 19:01 2024-06-22 19:01 edit,move Persistent disruptive editing: per request at RFPP; going longer this time Daniel Case
      Jogi (caste) 2024-06-01 18:04 indefinite edit,move
      WP:GS/CASTE
      and recent disruption
      Daniel Case
      FCSB 2024-06-01 17:55 indefinite edit a number of issues involving confirmed accounts, see TP Black Kite
      Imran Khan 2024-06-01 15:43 indefinite edit Arbitration enforcement RegentsPark
      Draft:Amir Sarkhosh 2024-06-01 13:47 indefinite create
      Repeatedly recreated
      - lowering per request at WP:AN
      Amortias
      Kol insurrection
      2024-06-01 11:44 indefinite edit,move Persistent
      WP:CASTE
      RegentsPark
      John Spencer (military officer) 2024-06-01 10:47 2025-06-01 10:47 edit,move
      WP:RfPP
      Robertsky
      List of presidents of Israel 2024-06-01 10:44 2025-06-01 10:44 edit,move
      WP:RfPP
      Robertsky
      Koli rebellion 2024-06-01 03:42 indefinite create Abecedare
      Kol uprising 2024-06-01 03:28 indefinite edit,move Persistent
      WP:GSCASTE
      Abecedare
      Koli rebellion 2024-06-01 03:25 indefinite edit,move Persistent
      WP:GSCASTE
      Abecedare
      Moroccanoil 2024-05-31 22:56 2025-05-31 22:56 edit,move
      WP:CT/A-I
      ToBeFree
      Draft:Ranjan Bose 2024-05-31 20:31 indefinite create
      Repeatedly recreated
      ; not notable; promotional; copyvio
      Diannaa
      User talk:GOOD-OLD-GEORGE2 2024-05-31 18:51 2024-06-07 18:51 edit,move LTA target Antandrus
      User:Leonidlednev 2024-05-31 15:32 2024-12-01 06:48 edit,move Increase to extended-confirmed edit protection, as
      user pages are already implicitly semi-protected by a filter
      Sdrqaz
      Nemo (singer) 2024-05-31 14:50 indefinite edit,move
      Contentious topic
      restriction: per RFPP and GENSEX; will log at CTOPS
      Daniel Case
      Israeli Public Broadcasting Corporation 2024-05-31 12:36 indefinite edit,move
      Contentious topic
      restriction
      Primefac
      List of killings and massacres in Mandatory Palestine 2024-05-31 05:27 indefinite edit Arbitration enforcement Johnuniq

      Content translator tool creating nonsense pages





      Machine translation gadget

      There is currently a gadget called GoogleTrans which allows the straight dropping of google translate into the content translation tool. (See here). I just did a test, and I was able to produce a machine translated article into english without leaving wikipedia using this gadget. Pinging the creator of the gadget: @Endo999:. I do not think this gadget should be present on the English wikipedia, and certainly not when it seems to explicitly endorse machine translations. Fortunately, it doesn't get around the edit filter, but it still sends a terrible message. Tazerdadog (talk) 09:02, 3 August 2016 (UTC)[reply]

      Thank you, I didn't remember about that gadget; I surely can make good use of it. That's the kind of tools that may be invaluable time savers in the hands of us who know how to use them, making the difference between translating a stub right now when you first stumble upon it (thanks to the kick-start of having part of the work already done), or leaving it for another day (and never coming back to it).
      Given that the CTX tool has been restricted to experienced editors, and that the GoogleTrans gadget needs to be explicitly activated, the combination of the two won't be at the hands unexperienced newbies in the way that created the current backlog. The GoogleTrans doesn't insert translated content into text fields, it merely shows the translation in a pop-up; so I don't agree that it "explicitly endorses machine translations". Any editor with your experience should know better than copy-paste machine translated text unedited into an article. Diego (talk) 10:39, 3 August 2016 (UTC)[reply]
      I am the creator of the GoogleTrans gadget and it does do Machine Translation Under The HTML Markup when used in the Content Translation system. I have used this to translate 226 articles from the frwiki to the enwiki and got all of them reviewed okay. The Machine Translation is a starting point. You still have to manually change each and every sentence to get the grammar and meaning right. It's not very sensible to ban it because, without human followup, it produces a bad article. The point is that it is a tool to quicken the translation of easy to medium difficulty articles, especially for good language pairs like English-French. Wikipedia, itself, uses both Apertium and Yandex translation engines to do machine translation and these have been used to good effect in the Catalan and Spanish wikipedias. GoogleTrans does the same thing as Apertium in the Content Translation system, except it uses Google Translate, which most people feel is a better translation engine. As Diego says this needs to be explicitly turned on, so it tends to restrict usage to competent editors. To stress the point, Machine Translation, as done by GoogleTrans gadget, is a starting point, it is not the end product. Human intervention is required to massage the MT into decent destination language text and grammar, but Machine Translation can help start the translation quite a bit. Wikipedia feels that Machine Translation is worth doing, because it has it as a feature (using both Yandex and Apertium machine translation engines) Endo999 (talk) 11:45, 3 August 2016 (UTC)[reply]
      Except that we have a policy against machine translation on en.wikipedia, because the requirements for correcting its output are far higher than users tend to realise; in fact it is easier and faster to translate from scratch than to spend the necessary time and effort comparing the original with the translation to find the errors. Hence the whole long discussion above and the agreement that machine translations can be deleted as such. Yngvadottir (talk) 19:13, 3 August 2016 (UTC)[reply]
      There is no policy against Machine Translation on the enwiki. That would have to be posted on the Content Translation blog, and it isn't. I've done 226 of these articles successfully and I can tell you there is more editing for non text issues, like links around dates coming from the frwiki, editing getting references right, manual changing of TAGS because their parameter headings are in the origin language. The actual translation work postprocessing, when polished up by a person competent in the destination language is far less than you say. But style differences between the wikis take more of the editors time. Endo999 (talk) 19:44, 3 August 2016 (UTC)[reply]
      The policy is at
      Iridescent 19:49, 3 August 2016 (UTC)[reply
      ]
      The policy is against unedited machine translation. It doesn't apply to using machine translation as a starting point to be cleaned up by hand. Diego (talk) 20:12, 3 August 2016 (UTC)[reply]
      MACHINETRANSLATION isn't a policy. It isn't even a guideline. WhatamIdoing (talk) 16:14, 8 August 2016 (UTC)[reply]
      I have never claimed that Machine Translation first drafts are good enough for articles on the enwiki. They aren't, but responsible use of Machine Translation, as a first draft, that is then worked on to become readable and accurate in the destination language is quite okay and even helpful. Endo999 (talk) 20:40, 3 August 2016 (UTC)[reply]
      The consensus is pretty clear that unless you are translating at a professional level, machine translation is a trap. It looks good at first glance, but often introduces bad and difficult to detect errors, such as missed negations or cultural differences. Even if a human caught 9 out of 10 of these errors, the translation would be grossly unacceptable and inaccurate. I'd request that this gadget be disabled, or at minimum, de-integrated from the content translation tool. Tazerdadog (talk) 23:33, 3 August 2016 (UTC)[reply]
      Well. I'm pretty far from being a fan of machine translations, but it's always been possible to copy/paste from Google Translate. Anyone autoconfirmed can do that without going to all the trouble of finding and enabling this gadget. The problem is fundamentally behavioural rather than technological. The specific problem behaviour is putting incomprehensible or misleading information in the mainspace. Over-reliance on machine translation is a cause of this, but we can't prevent or disable machine translation entirely, and there's not much point trying. I think the position we should adopt is that it is okay to use machine-aided translations provided you don't put them in the mainspace until they've been thoroughly checked by someone who reads the source language and writes the target language fluently. I suggest the approach we take to Endo999's tool is to add some warnings and instructions rather than try to disable it.—S Marshall T/C 23:51, 3 August 2016 (UTC)[reply]
      Don't forget that the use of Machine Translation in the Content Translation system is expanding all the time, and I'm am pretty much the only regular user of my GoogleTrans gadget for translation purposes. Why is the gadget being singled out? Yandex machine translation is being turned on by the Content Translation people all the time for various languages, like Ukranian and Russian. The Catalan and Spanish wikipedias are at the forefront of machine translation for article creation and they are not being flamed like this. I reiterate that the majority of edits per my frwiki-to-enwiki articles are over differences in the frwiki for an article than for articles in the enwiki. The treatment of dates and athletic times is one such difference. You need to do postediting after the document has been published in order to please the editors of the destination wiki. This usually has nothing to do with the translated text but is actually the treatment of links, the treatment of dates, the removal of underlines in links, the adding of categories, the transfer of infoboxes, the addition of references (the fiwiki is particularly good for references of track and field athletes), and other wiki standards (that are different from the origin wiki). There's always going to be some postediting of translated articles because of these nontranslation specific items. It's just inherent in wiki to wiki article movement. Endo999 (talk) 00:24, 4 August 2016 (UTC)[reply]
      We don't care about what happens on other wikipedia language versions, basically. Some are happy to have 99% bot-created articles, some hate bot-created articles. Some are happy with machine-translated articles, some don't. It may be true that "the use of Machine Translation in the Content Translation system is expanding all the time", but at enwiki, such a recent "expansion" started all this as the results were mostly dreadful. "Why is the gadget being singled out? Yandex machine translation is being turned on by the Content Translation people all the time for various languages, like Ukranian and Russian." Your gadget is in use on enwiki, what gadgets they use on ruwiki or the like is of no concern to us. We "single out" tools in use on enwiki, since this is an enwiki-only discussion. And this discussion is not about the long list of more cosmetic things you give at the end (or else I would start a rant about your many faux-bluelinks to frwiki articles in enwiki articles, a practice I truly dislike), it is (mostly) about quality of translation, comprehensability and accuracy. Yours are a lot better than most articles created with ContentTranslation, luckily.
      Fram (talk) 07:07, 4 August 2016 (UTC)[reply
      ]
      • @Endo999: I just happened to check Odette Ducas, one of your translations from French. You had Lille piped to read "Little". This is a good illustration of how easy it is to miss errors, and it's not fair, in fact counterproductive, to encourage machine-based translation and depend on other editors to do the necessary painstaking checking. Yngvadottir (talk) 17:20, 6 August 2016 (UTC)[reply]
      Thanks for catching that error (Lille translated at Little). I had seen and corrected that problem in a later article on a french female track athlete from Lille, but didn't correct the earlier translated article. Don't forget that Wikipedia is about ordinary people creating Wikipedia articles and through the ARGUS (many eyes) phenonmenon having many people correct articles so they become good articles. This is one example of that. Wikipedia is not about translation being restricted to language experts or simply experts for article creation. Your argument does tend towards that line of thought. Endo999 (talk) 18:56, 6 August 2016 (UTC)[reply]
      I don't think it does (for one thing, all you can know of my level of expertise is what I demonstrate). The wiki method is about trusting the wisdom of the crowd: this tool hoodwinks people. It's led you to make a silly error you wouldn't have otherwise made, and it's led to at least one eager new editor being indeffed on en.wikipedia. It rests on condescending assumptions that the editing community can't be left to decide what to work on, in what order. (Not to mention the assumptions about how other Wikipedias must be delighted to get imported content just because.) Yngvadottir (talk) 19:04, 6 August 2016 (UTC)[reply]

      I'ld like to retract my compliment about Endo999's use of his translation tool. I have just speedy deleted his machine translation of

      Fram (talk) 08:01, 12 August 2016 (UTC)[reply
      ]

      Almost everyone of the articles I have translated, using the GoogleTrans gadget, has already been reviewed by other editors and passed. I can only translate the existing French, which is sometimes not well written. In Fatima Yvelain's case I transferred over all the sources from the frwiki article. Can you tell me which reference didn't work out. You've deleted the article, without the ordinary seven day deletion period, so you deleted the article without any challenges. Are you and a few other reviewers systematically going through every article I have translated looking for things to criticize? Endo999 (talk) 01:54, 13 August 2016 (UTC)[reply]
      That's how Wikipedia rolls; it's the easiest way to demonstrate supposed incompetence, and since incompetence on the part of the creator reflects on the tool, it is therefore the easiest way in which to get the tool removed (along with phrases such as "I'd like to retract my compliment", which I hate as much as Fram hates faux-bluelinks). Simples. jcc (tea and biscuits) 11:00, 13 August 2016 (UTC)[reply]
      Having just checked the article for myself, if it was really "reviewed by other editors and passed" it reflects just as badly on those other editors as it does on you, given that it contained an entire paragraph of grossly libellous comments sourced entirely to an alleged reference which is on a completely unrelated topic and doesn't mention the subject once. (
      Iridescent 15:46, 13 August 2016 (UTC)[reply
      ]

      I realise this isn't a vote, but I agree with Tazerdadog that having such a tool easily available is sending the wrong message. It needs to be restricted to experienced users, with plenty of warnings around it. Deb (talk) 13:28, 17 August 2016 (UTC)[reply]

      You are all panicking. There's nothing wrong with using the GoogleTrans gadget with the Content Translation system if the appropriate editing happens alongside it. The ordinary review process can uncover articles that are not translated well enought. I'm being punished for showing ingenuity here. Punishing innovation is a modern trait I find. Endo999 (talk) 07:31, 18 August 2016 (UTC)[reply]
      No, our reveiw processes are not adequate for this. Both the problems with translated articles, and the unrelated but similar problems with tool created articles (now discussed at
      Fram (talk) 09:19, 18 August 2016 (UTC)[reply
      ]

      User:Fram
      per "We don't care about what happens on other wikipedia language versions" please speak only for yourself. Some of us care deeply what happens in other language version of Wikipedia.
      User:Endo999 tool is not a real big issue. It does appear that the Fatima Yvelain needs to have its references checked / improved before translation. And of course the big thing with translation is to end up with good content you need to start with good content. Doc James (talk · contribs · email) 17:41, 18 August 2016 (UTC)[reply]

      We, on enwiki, don't care about what happens at other language versions: such discussions belong either at that specific language or at a general site (Wikimedia). These may involve the same people of course. 19:45, 18 August 2016 (UTC)

      Do people feel that a RFC on this topic would be appropriate/helpful? The discussion seems to have fixated on minute analyses of Endo999's editing, which is not the point. The discussion should be on whether the presence of the gadget is an implicit endorsement of machine translated materials, and whether its continued presence sends the wrong message. Tazerdadog (talk) 22:33, 23 August 2016 (UTC)[reply]

      Yes, I believe an RfC would be helpful assuming it is well prepared.--Ymblanter (talk) 05:49, 24 August 2016 (UTC)[reply]
      The GoogleTrans gadget has been running on the enwiki for the last 7 years and has 29,000 people who load the gadget when they sign into Wikipedia. It's quite a successful gadget and certainly, wiki to wiki translators have concentrated on the gadget because while they may know English (when they are translating articles between the enwiki and their home wikis) they like to get the translation of a word every once in a while. Endo999 (talk) 17:05, 24 August 2016 (UTC)[reply]
      Discussion on this matter seems to have mostly died down, but I was unaware of this discussion until now and I feel the need to speak up on behalf of translation tools. I don't believe the tool being discussed here is the one I am using, since *it* does not provide a machine translation into english. However. I do put english into French based on the machine translation. I repeat, *based on*. Many of my edits to date have been translation and cleanup after translation, so I am probably close to an ideal use case. The tool, Yandex.Translate, appeared on my French wikipedia account and I do find it useful, although it produces text that needs to be gone over 4-5 times, as, yes, it sometimes creates inappropriate wikilinks, often in the case where a word can mean a couple of different things and the tool picks the wrong one. And it consistently translates word by word. I have submitted a feature request for implementation of some basic rules -- for example in German the verb is always the last word in the sentence and in French the word order is almost always "dress blue" not "blue dress". But there are many many MANY articles with word order problems on Wikipedia; it's just usually more subtle that that when the originating editor was human but not a native English speaker. So it's a little like fixing up the stilted unreferenced prose of someone who can't write but yea verily does know MUCH more about the topic than I do. And has produced a set of ideas, possibly inelegantly expressed, I would not have conceived of. The inelegant writing is why we have all this text in a *wiki*
      For the record, I agree that machine-translated text is an anathema and have spent way too many hours rescuing articles from its weirdnesses, such as "altar" coming through as "furnace branch" in Notre-Dame de la Garde. BUT. Used properly, machine translation is useful. For one thing it is often correct about the translation for specific obscure words. I deeply appreciated this when, for example, I was doing English into French on a bio of a marauding Ottoman corsair who, at one point or another, invaded most of the Mediterranean. I am an English speaker who was educated in French and has spent years operating in French, but the equivalent terms for galleon, caravel, Papal States, apse and nave, for example, not to mention Crusader castles and Aegean islands, weren't at the tip of my tongue. Its suggestions needed to be verified, but so do Google Search results. I could look these words up, sure, and do anyway, but Yandex gives my carpal tendons a break, in that I can do one thing at a time, ie translate a bit of text like "he said" then check to make sure that wikilink is correct, move down to the next paragraph and do some other simple task like correcting word order while I mull why it is that the suggested translation sounds awkward, walk away and come back... All of this is possible without the tool, but more difficult, and takes much longer. I have translated more articles in the past month, at least to a 0.95 version, that I had in the entire previous several years I've been editing wikipedia. Since the tool suggests articles that exist on one wikipedia but not the other, I am also embarking on translations I otherwise would not, because of length or sheer number of lookups needed to refresh my memory on French names for 16th-century Turkish or Albanian settlements or for product differentiation or demand curve or whatever. Or simply because while the topic may be important it's fundamentally tedious and needs to be taken in small doses, like some of the stuff I've been doing with French jurisprudence and which is carefully labeled, btw, as a translation in progress on those published articles that are still approaching completion.
      I agree that such tools should not be available to people who don't have the vocabulary to use them. I don't really have suggestions as to what the criteria should be, but there is a good use for them. They -- or at least this tool -- do however make it possible to publish a fully-formed article, which reduces the odds of cranky people doing a speedy delete while you are pondering French template syntax for {{cn}} or whatever. This has happened to me. The tool is all still kinda beta and the algorithm does ignore special characters, which I hope they remedy soon. (In other words ê becomes e and ç becomes c etc.) Also, template syntax differs from one wiki to another so infoboxes and references often error out when the article is first published. Rule of thumb, possibly: don't publish until you can spend the hour or so chasing this sort of thing down down. And the second draft is usually still a bit stilted and in need of an edit for idiom. But the flip side of that is that until you do publish, the tool keeps your work safe from cranky people and in one place, as opposed to having to reinvent the version management wheel or wonder whether the draft is in Documents or on the desktop. Some people complain within 3 minutes of publication that the article has no references without taking the time to realize that the article is a translation of text that has no references. As the other editor said above, translation tools aren't magic and won't provide a reference that isn't there or fix a slightly editorial or GUIDEBOOK tang to language -- this needs to come next as a separate step. When references are present the results are uneven, but I understand that this issue *is* on the other hand on the to-do list. Anyway, these are my thoughts on the subject; as you can see I have thunk quite a few of them and incidentally have reported more than one bug. But we are all better off if people like me do have these tools, assuming that there is value in French wikipedia finding out about trade theory and ottoman naval campaigns, and English wikipedia learning about the French court system. Elinruby (talk) 08:39, 31 August 2016 (UTC)[reply]


      Articles created by block-evading sock using the WMF translation tool

      My attention was drawn at a site I should not link to and therefore will not name (however, the thread title is "The WMF gives volunteers another 100K articles to check") to the fact that Duckduckstop created several articles using the WMF translation tool. They were blocked on 5 April as a sock of a blocked user, and their edits are thus revertable. I checked one translated article as a test, John of Neumarkt, and I've seen worse, but it is clearly based on a machine translation and contains at least one inaccurate and potentially misleading passage: "Auch in Olmütz hielt sich Johannes nur selten auf" does not mean "Also in Olomouc, John held only rarely"; it means he rarely spent any time there, but a reader might either not understand that or think it meant he rarely claimed the title. Wikipedia:Administrators' noticeboard/CXT/Pages to review contains thousands of pages, the vast majority still to be checked. Only a few of us are working there. I feel guilty having taken a few days off to write 2 new articles. I haven't looked through Duckduckstop's page creations to see what proportion were created with the translation tool, but that one has not been substantially edited by anyone else. I suggest that in this emergency situation, it and others that fall into both categories—translation tool, and no substantial improvements by other editors—be deleted under the provision for creations by a blocked/banned user. Yngvadottir (talk) 17:42, 27 August 2016 (UTC)[reply]

      Hi there. I have had a look today at that list, but haven't really been posting comments since as far as I could see nobody else has been there in several days. I do not know what happened with duckduckstop but as to the articles on the list
      - I do not understand why an article about a French general who invaded several countries under Napoleon is nominated for deletion as far as I can tell solely on based on authorship? Do we not trust the content because of the person who wrote it? Can someone explain this to me? I glanced at the article quickly and the English seems fine. This is a serious question; I don't get it. Also, why did we delete Genocide in Guatemala? It was already redlinked when I noticed it, but unless the article was truly astonishing bad, I would have made an effort to clean that one up. Personally. Considering that some of the stuff that's been on the "cleanup after translation" list the past few years --- we have had articles on individual addresses in Paris. We have lists of say, songs on a 1990s album in Indonesian, sheriffs of individual municipalities in Wales (one list per century), and government hierarchies in well, pretty much everywhere.
      - I have a suggestion: The person who decides that we need a set of articles for each madrasa in Tunis, water tower in Holland or mountain in Corsica is responsible for finishing the work on the articles in the set to a certain standard. Which can be quite low, incidentally. I have no objection to some of the association football and track and field articles that are being nominated for deletion. They may not be sparking entralling prose but they are there and tell you, should you want to know, who that person is. Similarly the articles about figures in the literature of Quebec, while only placeholders, do contain information and are preferable to nothing. Although I don't see machine translation as the huge problem some people apparently do, the translation tool also does need work. It might be nice if it sent articles to user space by default, and the articles could then be published from there there after polishing. Elinruby (talk) 14:26, 8 September 2016 (UTC)[reply]
      Fram (talk) 08:56, 12 September 2016 (UTC)[reply
      ]
      Heh. That's not unusual. But see there *is* an article, which was my primary concern. I should have checked before using it as an example. Here is the point I was trying to make. Since apparently I didn't, let me spell it out. -- I have put in a considerable amount of time on the "cleanup after translation" list so yes, I absolutely agree that horrible machine translations exist. I have cleaned many of them up. But. Many of the articles we keep are extremely trivial. Many get deleted that seem somewhat important, actually, just not to the particular person who AfD's them. I have seen articles on US topics get kept because of a link to Zazzle. (!) Perhaps my POV is warped by the current mess I am trying to straighten out in the articles on the French court system, but it seems to me that the english wiki is rather dismissive of other cultures. (Cour d'assises != Assizes, just saying; this is what we call a cognate.) That is all; just something that has been bothering me. Elinruby (talk) 05:59, 13 September 2016 (UTC)[reply]

      The interim period ends today

      But most articles have not been reviewed--it will apparently take many months. Of the ones still on the list that I have reviewed, I am able to find at least one-third which are worth rescuing and which I am able to rescue. We need a long continuation.If this is not agreed here, we will need to discuss it on

      WP:ANB. I would call the discussion "Emergency postponement of CSD X2" DGG ( talk ) 04:15, 6 May 2017 (UTC)[reply
      ]

      My understanding was that we were still working out how to begin the vaccination process. I'm happy if we simply moved to draft space instead of deleting at the end of the two weeks, but I'm not sure if that would address your concern. Tazerdadog (talk) 22:15, 6 May 2017 (UTC)[reply]

      @:
      I call "
      reltime
      " on the section title! ;-) But seriously, it does end in a few days, and although I've been active in pushing to stick with the current date (June 6) to finalize this, so I almost hate to say this, but I'd like to ask for a short postponement, for good cause. This is due to two different things that have happened in the last few days, that materially change the picture, imho:
      A postponement would give us the time to save all the clobbers, and make a significant dent in the articles from Asian and other languages for which we don't have a lot of expertise. Mathglot (talk) 06:19, 1 June 2017 (UTC)[reply]

      Notes

      1. ^ That is to say, four days less than it took Dr. Frank-N-Furter to make Rocky a man.
      My understanding is that the clobbers have all been taken care of. This leaves the Asian language articles. I'm sure that if someone with the needed language skills comes along in the future, admins would be more than happy to mass-undelete the drafts so that they could be reviewed. However, I don't see a reason to postpone in the hope that this will occur. Tazerdadog (talk) 18:45, 2 June 2017 (UTC)[reply]
      Clobbers *are* taken care of, because we (two of us) have been taking care of them. Asian (and other) languages have plenty of translators td.hat could take care of them, it's not a matter of "hoping" for anything in the future, they exist now, so all we have to do is continue the effort begun only a few (5) days ago
      Cryptic and Elinruby:. Mathglot (talk) 07:52, 3 June 2017 (UTC)[reply
      ]
      Still need to recruit de, bg and ru. Also still very distracted by real life -- I have had one parent die and another go into hospice in the course of this project, and we have still gotten all this done, so it's not like we are dragging this out into never-never land. A majority of these articles are rescuable, esp as we bring in new editors who are not burned out by re-arranging the word order of the sentences for the 10,000 time. I think the really stellar articles have all been flagged now, but we have still found some very recently and I have said this before. Beyond the really stellar though are the many many not-bad articles and the more mediocre ones that are nonetheless easier to fix than to do over.I am in favor of an extension, personally, though as we all know I would not have started this at all if it were up to me. Many of the really bad articles were already at PNT.
      I will be flying almost all day today but will check into wikipedia tonight. Elinruby (talk) 16:19, 3 June 2017 (UTC)[reply]
      I'm involved in many other things, and get here as I can, and each time I do, I find more than can and should be rescued. There are whole classes of articles, like those of small towns or sports stadiums, which have merely been assumed to be of secondary importance and not actually looked at. If we delete now, we will be judging article by the title. It is very tempting to easily remove all the junk by removing everything, but that;'s the opposite of sensibler ,and the opposite of WP:PRESERVE/ DGG ( talk ) 09:45, 5 June 2017 (UTC)[reply]
      I found a couple today that kind of amazed me, they were so good. But let's play out the chinese fire drill. I'm afraid we're going to find out that we've all done a huge amount of work to delete 30 articles that need to be deleted and 350 whose authors will will not contribute again. Anyway. I have not touched stadiums, personally, because I suspect they will be deleted for notability so why? Ditto all these people with Olympic gold medals because I already have plenty to do without getting involved with articles that are certain to be deleted, not to mention all the argentinian actresses and whatnot.... grumble. Gonna go recruit some chinese and norwegians, because the articles are just going into some other namespace we can still send links to right? Elinruby (talk) 02:14, 6 June 2017 (UTC)[reply]
      The plan is to draftify the articles prior to deletion, but I think deletion can be postponed basically indefinitely once they are draftified Tazerdadog (talk) 02:31, 6 June 2017 (UTC)[reply]
      @Tazerdadog: I'd like to be sure of that. This is why you lose editors, wikipedia... anyway. Am cranky at the moment. Let me get done what I can with this and then I'll have some things to say. Hopefully some intelligent and civil things. Are we really getting articles from PootisHeavy still? Elinruby (talk) 02:46, 6 June 2017 (UTC)[reply]
      @Elinruby: Fixing pings like you just did doesn't work. Pings only work if you sign your post in the same edit and do nothing but add content. Pppery 02:49, 6 June 2017 (UTC)[reply]
      @Elinruby: The second part statement I made above is a departure from the established consensus as I understand it. The plan which achieved consensus was to draftify, hold in draft for just long enough to check for massive clerical errors, and then delete. I floated the above statement to try to gain consensus to hold the articles in draft space for longer (or indefinitely). While it is important to get potential BLP violations and gross inaccuracies out of mainspace in a timely manner, i don't think it is nearly so important to delete the drafts, especially if salvageable to good articles are regularly being pulled out of them. Tazerdadog (talk) 03:06, 6 June 2017 (UTC)[reply]
      @Tazerdadog: Thanks for the suggestion. I think that would help limit the potential for damage and it would alleviate some of my concerns. My assessment differs widely from what I keep reading on this board, but, hey. If anyone cares I would say that 10% of these articles are stellar and very advanced and sophisticated translations. Don't need a thing. Another 10% are full or partial translations, quite correct, of articles that do not meet en.wiki standards for references or tone but do faithfully reflect the translated article. Many of these are extremely boring unless you are doing nitty-gritty research into something like energy policy in Equatorial Guinea, but they then become important... About another 5% I cannot read at all and let's say another 10% are heavy going and require referencing one or more equivalent articles in other languages. Say 5% if anyone ever gets around to dealing with PootisHeavy. The rest are... sloppy english but accurate, unclear but wikilinked, or some other intermediate or mixed level. This has not, in my opinion, been a good use of my time and I have stopped doing any translations, personally, until we get some sanity here. The whole process, it seems to me, simultaneously assumes that translation is easy and also that it is of no value. If wikipedia does not value translation then -- argh. It just makes me to see a good organization eat its own foot this way, is all. Off to see if I can catch us a nepali speaker ;) Elinruby (talk) 03:26, 6 June 2017 (UTC)[reply]
      @
      no Nepali articles in the batch, afaict. Also, Pootis stopped translating
      following a March 23 addition to his talk page, currently at #53 on the page.
      @
      there if anyone wants to volunteer). I'll want to modify the editor recruitment template so that it can blue-link articles in whatever new location they reside in, so hopefully it will be a nice, systematic mapping of some sort so a dumb template can easily be coded to figure out the new location, given the old one. Just wanted to mention that, so that you can keep it in mind when you come up with the move schema. Naturally, if it's just a move to Draft
      namespace, then it will be an easy fix to the template.
      There is one article in Nepali. I have not invited anyone for it yet, though I did do some of the less populated languages like latvian, indonesian and polish. I have several answers (da, es, pt as I recall) and most articles passed. I will put translated templates and strike those articles shortly. And yes, I just now struck one today. Anything about 3-d modeling is notable imho and I will work on it as long as I can read it at all. Also some of the bad translations about historical documents may be fixable given the response we are getting. If either of you gets enough help/time there are quite a few es/pt/de articles that I did that I believe to be correct but cannot myself certify in terms of the translated template Elinruby (talk) 00:29, 8 June 2017 (UTC)[reply]
      @DGG: I withdraw my aspersions on the section title name. This offer valid for twenty-four hours. Mathglot (talk) 08:24, 6 June 2017 (UTC)[reply]
      I do not understandd what you mean by this. I assume you mean you are withdrawing the attempt to start mass deletions immediately. If not, please let me know--for I will then proceed to do what I can to prevent them--and , if possible to try to change policy so that no X- speedy criteria can ever again be suggested. The more of these translations I look at, them ore I find that should be rescued. DGG ( talk ) 23:59, 7 June 2017 (UTC)[reply]

      Request for re-close of an old RfC (and closure of a disruptive RfC)

      I would like to request a review of the closure of this RfC regarding the page Paul Singer (businessman). It was discussed with the closer here.

      The previous RfC for this same issue (12/10/15) can be found here where consensus was established six months prior to the RfC in question. Between the two RfCs, the closer had created a number of discussions (possibly in violation of

      WP:FORUMSHOP) here: [1] [2] [3] [4]
      . These discussions failed to garner much attention and mostly reinforced the 12/10/15 consensus.

      It must be noted that the RfC in question is rather old (29/04/16) and editors protested the closure since it was closed by the same editor who opened both the RfC itself and all other discussions, and was not necessarily reflective of consensus which does appear to reinforce that set out in the 12/10/15 RfC.

      The improper close of the RfC would normally not be an issue, however, yet another RfC has opened, claiming that the last discussion was "inconclusive" and we must therefore have another discussion.

      I would argue that this has all been incredibly disruptive considering the huge number of editors involved (36) in the prior 8 discussions from a 16/07/14 RfC to the 29/04/16 RfC is plenty of discussion for something which editors have considered relatively uncontroversial - 23 have been in favour of the current consensus and 6 against, with 7 somewhere in between. Furthermore, consensus has often not been respected in the rare points of calm between discussion, with some of the "6 against" editors making against-consensus edits and reversions.

      This is a messy situation, but to conclude, I would like to request the evaluation of the close here and the closure of the current RfC, considering the arguements made by other editors at Talk:Paul Singer (businessman)#RfC is Nonsense. Thanks. SegataSanshiro1 (talk) 19:42, 26 August 2016 (UTC)[reply]

      The issue is bifurcated in the prior RfCs. There was a limited consensus that a company could be called a "vulture fund" but no consensus that a person should be described as a "vulture capitalist" in the lead of a BLP. My own position has always been that specific pejorative terms should only be used as opinions ascribed to the persons holding the opinions, and that use of pejoratives about individuals should very rarely be allowed at all. To that end, I suggest that reversing prior closes is inapt, and the claims made that the prior RfCs support calling a living person a "vulture" are incorrect. The company can have cites of opinions that it is a "vulture fund" cited and used as opinions, but the use of that pejorative as a statement of fact about a living person falls under
      WP:BLP. The current RfC has 6 editors specifically noting that the use of the pejorative in the lead about a person is wrong, 1 says the person is absolutely a "vulture capitalist", 1 asserts that every RfC supports calling the person a "vulture" and one says we should not have any more RfCs - that the issue is settled and we should call the living person a "vulture capitalist" in the lead on that basis. I rather that the current 6 to 3 opposition to use of the term in the lead indicates a substantial disagreement with the assertions made here, and the request that a close be overturned out of process. Collect (talk) 21:08, 26 August 2016 (UTC)[reply
      ]
      There has been no RfC to discuss whether someone should be called a vulture. I myself have said in past discussions that doing so, especially in WP's voice, would be contrary to what this encyclopaedia is about. Please do not mis-represent my views - it's things like that which have made these constant ongoing RfCs so toxic. My view is that Singer is most notable (
      WP:RS) which confirm this and thus this fact should be made clear in the lede. Claiming that mentioning his company in an article equates to WP calling someone a vulture is nonsense and not a new arguement - this is the same line those same editors took over and over again in these discussions to no avail. SegataSanshiro1 (talk) 21:32, 26 August 2016 (UTC)[reply
      ]
      Note that I specify the issue at hand is with regard to using the pejorative with regard to the single living person in the lead. A number of sources have branded him a "vulture capitalist" as distinct from his role at EMC, which has been called a vulture fund.. The two catenated uses of the pejorative are different here - ne is with regard to how some have categorized the fund, the other as a personal pejorative in the lead about the person. Do you see that distinction? Especially when the single sentence uses the term "vulture" twice? Collect (talk) 23:09, 26 August 2016 (UTC)[reply]
      You also failed to mention 2 more editors who had been in favour of using the term vulture fund in the lede but refused to partake in this particular discussion since they have made it clear that there have already been to many. SegataSanshiro1 (talk) 21:39, 26 August 2016 (UTC)[reply]
      Again - the word "vulture" is used twice now in a single sentence in the lead - once with regard to opinions held about the fund (for which the prior RfC found the use of the opinion as opinion about the fund was allowable), and the second, the problematic one, with regard to the use of a pejorative about a living person in the lead of the BLP. Collect (talk) 23:09, 26 August 2016 (UTC)[reply]
      I am the creator of the most recent RfC. Frankly SegataSanshiro1 forced this RfC to happen in the first place by refusing to engage in talk page discussion on the vulture point. I would like to request that anyone participating in this discussion carefully read Wikipedia:Status quo stonewalling, and then refer directly to each of SegataSanshiro1's actions leading up to this RfC, and his actions in this one as well. Whatever SegataSanshiro may personally believe, a slur in a lead is Always A Very Big Deal, and not something to be brushed under the rug. As WP:Biographies of living people says, "we must get it right." It seems clear to me that several parties want to freeze an ongoing discussion at a point they find satisfying. Yvarta (talk) 21:51, 26 August 2016 (UTC)[reply]
      I have been involved in these ongoing discussions for quite some time now. As I've stated before, using a pejorative to describe an individual on a BLP is unacceptable, especially in the lead. That being said, the previous RfC was closed once discussion went stale. There were ample opportunities and there was more than enough time to provide arguments. Once users agreed upon a version, which limited use of the term "vulture", the user who closed the RfC made the edits in question but was reverted and the term was included an additional three times.
      SegataSanshiro1's antics on Singer's page has gotten out of control and his motive on the page is clear. Now that consensus on the newest RfC is shifting highly in favor of removing the slur from the lead, SegataSanshiro1 is grasping at straws to get the previous RfC reviewed. If SegataSanshiro1 had an issue with how the previous RfC was closed, why didn't he follow through with an secondary discussion after this one went stagnant? After realizing consensus is shifting, not in his favor, he wants to call this new productive RfC "disruptive". Also, after the last RfC was closed, an admin came in and suggested a new RfC so do not throw out
      WP:FORUMSHOPPING accusations. Meatsgains (talk) 02:39, 27 August 2016 (UTC)[reply
      ]
      Meatsgains, consensus is not shifting as you cannot establish consensus in a discussion which half of the editors can't even take seriously. You have been at the heart of this whole drama. Every time there was an RfC or discussion and consensus was established to use the term, you actively went about making against-consensus edits and other highly disruptive behaviour (which myself and other editors have called you out on time and time again) such as misrepresenting the results of other discussions, claiming sources weren't reliable when they were and even making up terminology like "distressed securities funds" to avoid using actual terminology. You are the only editor who has been involved in every single one of these discussions - very possessive behaviour all in all and along with the other things, you should have been sanctioned and barred from editing on that page.
      Still, you continue to misrepresent what happened. There were five editors (myself included) who have said that this RfC is daft. If that were not the case, I wouldn't have opened this discussion on the noticeboard. I'm not going to let you make me lose it again, so please stop referring to me - I want absolutely nothing to do with you, and I know I shouldn't be addressing editors directly, but I really want to make that absolutely clear. Something hypothetical you might want to think about though:
      After you've rolled the dice so many times trying to prevent
      WP:RS from an article and failed miserably, let's say that now after 8 or so attempts at getting your way you finally do. How seriously do you think other editors would take that consensus? Would they simply carry on doing as they wished to the page regardless as you have? Would they simply call another RfC in three months time and pretend the others never happened as you have? I very much doubt I'll stick around after this because I'm sick of this page, but I have a feeling you will, and if you do and you carry on acting as you have, you will be doing this for years. Please don't answer me. SegataSanshiro1 (talk) 03:09, 27 August 2016 (UTC)[reply
      ]
      I have weighed in on this on multiple occasions and will do my best to promptly summarize my opinion on the topic. The original dispute over the use of the term vulture has been over the derogatory nature of the term on vulture fund’s page. Subsequent discussions have taken place regarding the general use of the term, however the scope of the debate later concentrated on the term’s use in a BLP, specifically Paul Singer’s page. Some editors, whom I will not name, act as if they
      wp:own the article and have done everything in their power to keep vulture fund and vulture capitalist in the article. Some users have actually made the argument that "vulture" is not derogatory whatsoever (one even argued that it should be taken as a compliment. No reasonable and neutral arbitrator could disagree with the fact that “vulture fund” is a slur, invented by people who are deeply opposed to their entirely legal investments. Comatmebro User talk:Comatmebro 17:05, 27 August 2016 (UTC)[reply
      ]


      Reverted 1 edit by Collect (talk): You're hardly the person to close this RfC... is a splendid example of grotesque snark. I did not "close the RfC" and that snark is ill-suited for rational discussion. In addition, I left in the "vulture" opinion about EMC, and note that the lead is supposed to be in summary style. I am concerned that this sort of snark is poisonous to any discussion, and ask that any editor who feels such personal attacks should be used should get the aitch away from here. Collect (talk) 21:32, 27 August 2016 (UTC)[reply]

      Collect, it's quite understandable that a number of editors are very much on edge considering this has been discussed to death and the conduct of a couple of editors in particular. I think what Nomoskedasticity meant by that remark is that you were making edits about something which was being discussed... Were you not one of those supporting an RfC after all?
      From my own personal perspective, I think mentioning his main business area is running a culture fund, then including other references to him specifically in some sort of criticism section would be ideal. That and removing references to philanthropy from the lede as per
      WP:UNDUE. SegataSanshiro1 (talk) 22:18, 27 August 2016 (UTC)[reply
      ]
      • Comment: first of all I wish to state my astonishment at not being pinged when I was directly involved with one of the RfCs called into question.
        ownership of the Paul Singer article. Every time any editor makes a serious attempt at a copy edit (no matter how minor), a concerted effort by the same bunch of editors reverses all possible changes. Just look at the edit history. Serious and pragmatic comments aimed at stemming this dreadlock are conveniently brushed aside, such as DGG's - "It's appropriate to use it in the article, since there is good sourcing, but it is not appropriate to use it in the lede. Ledes should be relatively neutral". If civil discussion cannot come about and admin action is required, so be it, but it does set a sad precedent. We had originally copy edited the lede back in October, trimming the use of "vulture" down to a single mention. This was of course then reverted maniacally even though discussion had concluded in that precise path. I don't see why a reasonable review of each instance of the word's use cannot take place. FoCuS contribs; talk to me! 22:59, 27 August 2016 (UTC)[reply
        ]
      Focus, this wasn't intended to be "guerilla antics" - we had actually discussed a re-close prior to this and you were involved, together with a number of other editors who I did not ping since I figured they would not want to be dragged into this again - I take it you're a page watcher anyway and I mentioned this discussion on the talk page. I also never had a problem with you being
      WP:BOLD
      and closing the discussion (in fact if I recall correctly, me and other editors were all for it), what myself and other editors had a problem with was the closing remarks, in particular "the RfC question was not unequivocally answered" when in reality it had, for the nth time that it is appropriate to use this particular word in this particular article - that's beyond discussion at this point. To this day, I agree with the path of compromise we embarked on, what I did not agree with was the sheer amount of forums this was taken to and the manner in which the discussion was closed. To be honest, that close made me question your good faith and took away any desire on my part to be collaborative.
      The issue with these discussions is that they're never clear, we're never discussing on a point by point basis since one or two editors (should be fairly obvious who) take these discussions as an attempt to remove all mention of the terminology, digging in their heels until we're back in 2014 again discussing whether we should censor it entirely (again, always the same editors). All the while, creating serious NPOV issues by removing statements backed up by RS and adding in things which are UNDUE in an attempt to whitewash. If that stops, then I'm sure normal discussion could ensue and general anger levels could be drastically reduced along with the tedium. I have already said that I'm of the opinion that "vulture capitalist" should be discussed, but that's hardly going to happen if we still have editors claiming a vulture fund is not a thing, and the very presence of the term (what Singer is most notable for, if I may add) equates to Wikipedia calling a living person a vulture. That's not new, that's not productive and you're as aware of that as I am. SegataSanshiro1 (talk) 23:46, 27 August 2016 (UTC)[reply]
      • It was a middle of the road close. . There is a distinction between someone being personally a vulture, which implies that he acts in that manner in all his activities or is of that personality type, and running a fund that shares some similar characteristics and goes by the common name of vulture fund. We cannot avoid using the full term, because even those sources that endorse the profession use it as a matter of course. But we can try to avodi personalizing things that don't need personalizing, especially things that some people are likely to consider highly negative. DGG ( talk ) 03:30, 28 August 2016 (UTC)[reply]
      And to the point - any BLP which stresses the use of "vulture" seventeen times is likely to be perceivable as making a point in itself. I just do not understand the concept that name-calling is something Wikipedia should actively pursue, and that editors who even remove a single use from the lead are somehow evil here. Argh. Collect (talk) 12:46, 28 August 2016 (UTC)[reply]
      It doesn't appear 17 times. I only see 6 mentions in the article itself and one of them was actually about an antisemitic cartoon - the rest are mentions in references. --Lemongirl942 (talk) 12:49, 28 August 2016 (UTC)[reply]
      That's INCREDIBLY misleading. Most of those are references, hence more reason to include it. Of the 6 ACTUAL uses, none of them are in WP's voice. SegataSanshiro1 (talk) 14:29, 28 August 2016 (UTC)[reply]
      @SegataSanshiro1: You keep claiming that "Singer is most notable for" his "vulture fund". This is your own opinion. Do a google news search and tell us how many pages you have to dig through before coming across a page that uses the slur? This is a false assumption, which you have consistently done throughout this dispute. Meatsgains (talk) 17:10, 28 August 2016 (UTC)[reply]
      Stop pinging me. This isn't my own opinion and
      WP:COMMONNAME - you should also remember this since there were two discussions, both on the talk page and at WP:W2W which undid that rather stealthy move and established rather firmly that vulture funds are indeed a thing and that is indeed what they are called, while Singer's EMC is one of the most prolific. Why have you consistently misrepresented information and lied to other editors? There's plenty more examples where you have been called out on doing this, want me to give more? Meatsgains, you are the only editor (along with Comatmebro, actually) who has been involved in every discussion to do with Singer, vulture funds and Elliott Management Corporation and consistently used some very dodgy tactics to get your way, ranging from ignoring consensus and making edits regardless to protecting all these pages like a hawk (or vulture, more appropriately?) and claiming sources aren't reliable based on your own opinions. I'm still shocked you're still around and you haven't been sanctioned. SegataSanshiro1 (talk) 18:19, 28 August 2016 (UTC)[reply
      ]
      "This isn't my own opinion and vulture fund is not a slur" - Yes it is and yes it is. Also, do not dilute this discussion with attacking me. Meatsgains (talk) 20:15, 28 August 2016 (UTC)[reply]

      Thank you, DGG; that's a fair representation of my basic thoughts as well. As I just posted on the Singer talk page, we're trying to discuss the use of "vulture" as a descriptor of a human being. "Vulture" is as such a charged word in the sense that we're liable to annex this valued meaning to a word that is used in the context of a business endeavour. Handling a vulture fund is not the same as BEING a vulture. I am utterly amazed people fail to see that. The previous close was precisely that, a "middle of the road close". The "vulture fund" practices are thoroughly discussed throughout the article in the context of what quality sources have to say about the matter. Using the term through a personal angle by making a de facto generalisation in an article's lede is another story, and I believe we were making some progress back in October in this regard. I would very much like to see us return to that stage and come up with a neutral and balanced solution. FoCuS contribs; talk to me! 21:17, 28 August 2016 (UTC)[reply]

      Agree that handling a vulture fund does not equate to being a vulture - that's the main flawed premise that has been holding this back. I still disagree that the close was "middle of the road", since using vulture terminology does not violate NPOV (the question raised in the RfC) since it is WP:DUE - only a tiny, tiny number of people have said that all reference to vultures should be gone from the article. The Samsung affair and other criticism (such as "vulture capitalist") needs to go in a criticism section rather than the lede - Singer has received enough criticism from multiple sources to warrant one. Vulture fund, on the other hand, should remain firmly in the lede - that's what he's known for and what a large chunk of the article is about. I know you have argued that he has other investments, but that's akin to leaving out the Iraq war in Tony Blair's page. SegataSanshiro1 (talk) 22:30, 28 August 2016 (UTC)[reply]
      Yet again you are wildly, amazingly off topic. There is already an RfC discussing this issue, in case you forgot, and a talk page to discuss general improvements. This discussion, SegataSanshiro, you started to determine if the RfC creations are inappropriate. As you seem to have forgotten, I would like to remind you that you reverted my lead change on the grounds that I needed to first discuss, and now you are trying to shut that very discussion down - that, or apparently force it to stagnate by repeating the same arguments while ignoring the arguments of others. As far as I am concerned, you specifically continue to stonewall and disrupt a natural consensus building process. You are either nearing either an epiphany (i.e. that this is not a battle you are trying to win), or nearing a topic ban. Yvarta (talk) 23:45, 28 August 2016 (UTC)[reply]
      Not me specifically. There have been five editors (including me) who have questioned the validity of this RfC. SegataSanshiro1 (talk) 15:47, 30 August 2016 (UTC)[reply]
      Hopefully I haven’t given the impression I think those other four are guilty of actively stonewalling. If so, I apologize for being thoughtless and rude. Yvarta (talk) 18:30, 4 September 2016 (UTC)[reply]
      • Comment I am not opposed to having an administrator re-close a previous RFC if the stated consensus was incorrect (I was the one who suggested coming to AN on the Singer talk page as SegatSanshiro continues to question it), just for the sake of clarity and any subsequent discussions. I do not support closing the current RFC though. I don't see it as disruptive as opinion is clearly divided and the issue is contentious, the previous RfC was over 4 months ago and the closing and consensus is disputed, so getting new editors involved to seek consensus should be a good thing (I only joined this discussion thanks to this most recent RfC). As for my opinion about the underlying issue, I've already posted to the RfC and it may not be relevant here, but I believe that mainstream reliable sources do not refer to Singer as a "vulture." He is called a hedge fund manager by these sources. Therefore the term vulture should only be used when it is ascribed to a specific person or entity (i.e., his critics). My reading of the current RfC and previous ones is that most editors agree with that position. FuriouslySerene (talk) 17:30, 30 August 2016 (UTC)[reply]
      • Comment I have never edited this article and am in this because the RfC bot asked me to give my opinion. The person who started the RfC however has repeatedly told me I am off-topic when I try to explain the BLP policy. As best I can tell however the person's argument is that the appellation is inappropriate because Singer is a living person, and they appear to be ready to repeat this argument indefinitely. I would also like to mention that while I personally believe that "vulture capitalist" is a specialized bit of vocabulary that is not particularly pejorative, the current wording does not use it in wikipedia's voice either, which many of the comments on this seem to assume. It says he has been called a vulture capitalist and provides no less than nine sources for the statement. I believe we should remove the weasel wording and explicitly quote one or more people. I would agree with the idea expressed at one point of balancing out concerns about due weight, assuming that is what they are, by adding other details of his business dealings. However as far as I can tell there are no such details; Singer seems to be a specialist in this type of transaction, and to have been for decades. Elinruby (talk) 20:07, 30 August 2016 (UTC)[reply]
      Explaining BLP policy is not off topic - however, long accusations of COI (without basis) and facts focused on Singer's details are very off topic to this particular RfC, as I've pointed out that many businessmen have similar, nigh identical press coverage concerning the "vulture" phrase. If you would like to start another RfC on a different nuance or topic, you are welcomed to. Yvarta (talk) 14:41, 4 September 2016 (UTC)[reply]
      Heh. The heart of my point is that Singer is a public figure and therefore under WP:PUBLICFIGURE it matters very much whether the statement is true. As for my COI concerns, well, normally we don't comment on editors but your actions do suggest one in my opinion, yes. You are very concerned, astonishingly concerned, with the PR of this billionaire, shrug. I didn't actually start with that assumption, mind; I just told you it was ok to be a paid editor if you declared yourself as such. But you say you are not, so. AGF. You *still* never ever answer any other editors questions, and dismiss them as irrelevant unless they support your desired outcome. Elinruby (talk) 12:39, 8 September 2016 (UTC)[reply]
      • Comment - Anyone look at the nominator's (i.e. Yvarta's) edit history? Yvarta, this looks like it was not your first account. Who were you editing as prior to this account? NickCT (talk) 14:30, 4 September 2016 (UTC)[reply]
      Feel free to ask any questions about my experience on my talk page/email. My editing history relates to personal details of my life, and so I haven't shared that here/in the RfC. Yvarta (talk) 14:36, 4 September 2016 (UTC)[reply]
      • Comment - This RfC makes for a dramatic read. My perception of things, after also skimming the older RfCs linked about halfway through, is that the prior RfCs were imperfectly framed, and as a result conversations were bogged down by arguments over whether Singer himself was a vulture, not whether vulture should be a descriptor in any lead at all. The RfC certainly has broader implications than one biography, as the overall precedent on Wikipedia most definitely favors avoiding such descriptors in bio leads. Has anyone else been able to find a biography or corporation with an animal slur used in the intro? I tried with several creative search phrases, and have so far utterly failed. This RfC is far from perfect as well, but I do applaud its attempt to focus the issue away from Singer. Most constructive so far, in my opinion, is that the argument that excluding vulture from the lead equals censorship has been debunked several times. Leads are certainly not required to include every detail of a criticism section, and per prior arguments, any concept that could be carried across by "vulture" could also be carried across with an alternate explanation.
      Note to whoever closes this RfC: However long this discussion needs to continue, I would like to note that there is obviously not a clear consensus in favor of keeping vulture in the lead, even though the reverts apparently leading to this discussion were founded entirely on the argument that prior RfCs had reached consensus. As such, I would like to note that all three of those reverts have been proven to have been without basis, even if they were done in good faith. A number of contributors, several of obvious neutrality and experience, have agreed that a slur of denigration is inappropriate in a lead when applied to a person or company, especially since both the criticism and the neologism can be fully explained with neutral and more conservative words. As such, the argument that there is a violation of the neutral tone mandated by
      WP:BLPSTYLE is at the very least plausible, however this consensus concludes itself. Until that time, however, the assessment that biography leads must be treated with extra delicacy is absolutely correct, and I agree with Yvarta's bold action to remove "vulture" when he/she did, just like I would have agreed with a decision to remove "rat" or "loan shark" or "pig." Basically, until something is settled, there is currently no consensus', and I believe "vulture" should be again removed until consensus is reached and the barn is built.Bbmusicman (talk) 00:24, 15 September 2016 (UTC)[reply
      ]
      Here are examples of why I answered as I did, if anyone is interested:
      My point is that when derogatory information *is true* then we are not required to pretend it's not there.
      - btw, for a dispassionate take on what a vulture capitalist actually is. I think people should read vulture fund and vulture capitalist -- nothing there about animals. Hope that helps. Elinruby (talk) 00:36, 8 October 2016 (UTC)[reply]
      I highly encourage you to take some good examples to the RfC, where contributors can see them (this discussion isn't linked on that talk page anymore, after archiving). I'm a bit confused by your examples, though? Shrimp isn't very deragatory, except perhaps to a very short and insecure person, and "dictator" is actually a relatively neutral, especially compared to synonyms such as "tyrant" or "monster" or "fiend." Other phrases, like "mass-murderer," also have negative connotation, but they are clinical and exact, without cartoonish connotation making the phrases more
      loaded than necessary. Perhaps other examples? Yvarta (talk) 22:41, 10 October 2016 (UTC)[reply
      ]
      • Observations: (1) SegataSanshiro1, who opened this AN thread and who has written more than double the amount of text of the article than any other editor [7], is Argentinian (as noted on his userpage) and has a very strong POV and agenda about the article, since Singer's most controversial debt-funds are Argentinian. (2) In my opinion FoCuSandLeArN should not have closed the previous
        WP:RfC (nor should he have made the edit[s] presumed to be "consensus" -- at the very least, another editor should have made any edits springing from the RfC), since he started the RfC and has also been involved in the contentious debate(s). One can withdraw an RfC one has started, but one cannot close it. Only an uninvolved editor can formally close an RfC. See WP:Requests for comment#Ending RfCs. (3) That said, SegataSanshiro1 has opened this AN thread in a very non-neutral, POV manner, and as Meatsgains commented above, SegataSanshiro1 had no problem with FoCuSandLeArN's 5-month-old close until now. (4) What seems to need to happen is for an uninvolved administrator to look at and close the current RfC that is now on the talk page awaiting closure. (5) I believe Collect, a neutral and highly experienced editor, has encapsulated the issue well in his three comments above. Softlavender (talk) 03:04, 9 October 2016 (UTC)[reply
        ]

      Self-promotion by User:Calibrador

      This complaint is about

      User:GageSkidmore, for blatant conflict of interest and using Wikipedia for promotional purposes. Specifically, he inserts photos he has taken into multiple articles (I would guess hundreds), and the file titles always include his name, as in [[File:John Doe by Gage Skidmore]]. This is a clearly promotional practice since he is a professional photographer. To be clear, he does not make any money from these photos since they are from Commons, but he "gets his name out there," a form of advertising, every time Wikipedia uses one. He has been doing this for years - the Commons category "Photographs by Gage Skidmore" has 11,000 entries [8]
      - but he has recently become particularly insistent on inserting them into Wikipedia articles.

      I first encountered him a few weeks ago, over the question of putting new images into the infobox at the articles

      United States presidential election, 2016. On September 1 he offered some new pictures (taken by him, and with his name in the filename) of Trump. Discussion at Talk:Donald Trump was very extensive. It went on for days, and Calibrador became more and more insistent and argumentative. Twice [9] [10]
      he introduced his own picture into the article, claiming "most people" preferred it, even though the discussion was still ongoing; he was promptly reverted. Meanwhile, he added his pictures of Trump and Mike Pence ("by Gage Skidmore") to other articles. He has also been adding photos of other, lower-profile people to their articles at a great rate; in the first 10 days of September I counted a dozen such.

      Some people will say: they are good photos, they are free, what's the problem? That's a valid comment. To me the problem is that he is using Wikipedia to promote himself, and his insistent promotion of his own photos is becoming disruptive. At the Donald Trump talk page, as of September 11 he had made 47 edits since September 2, virtually all of them about the pictures. He repeatedly praises his own photo without mentioning that he is the photographer (most editors would not realize that), and he badgers opposing !voters. Some of his comments at that page:

      • Arguing in favor of his own picture (photo C): [11] [12] [13]
      • Declaring that his photo C has consensus: [14] [15]
      • Arguing with people who prefer a different picture: [16] [17] [18]
      • Arguing that some people's !votes (for another picture) should not count: [19] [20] [21]

      The same pattern can be seen at the Mike Pence talk page: he proposed a change of photo on the talk page, urging one of his own (photo A, with his name attached). During the ensuing discussion he repeatedly argued with people who favored a different one: [22] [23] [24] [25]

      For another example see Anne Holton, where he inserted one of his own pictures to replace an old blurry one, then kept re-inserting it when other people preferred another photo that was also taken by him -- possibly because the one he wanted to use has "by Gage Skidmore" in the filename and the one other people preferred (which is clearly a better picture) does not.

      On September 10 I warned him about his apparent

      conflict of interest.[26]
      He promptly erased my comment from his talk page (along with a year's worth of previous warnings about non-free content, edit warring, etc., although he kept all of the positive or complimentary messages).

      When I looked to see if this was discussed before, I found the same issue came up at ANI in June 2015: Wikipedia:Administrators' noticeboard/IncidentArchive891#User: Stemoc. He himself filed a complaint against another user, first changing his username from GageSkidmore to Calibrador - a change that several people thought was bad faith. The discussion quickly turned into a possible boomerang against him for promoting his own photos, with his name in the filename, as a form of self-promotion or advertising. Several proposals were made. The most popular proposal, suggested by User:Nick, was that he should be "either restricted from removing an existing image from a page and replacing it with an image he has taken/uploaded himself, unless discussion has taken place prior to the switching of images and consensus is in favour of the change; or else there's a 1RR restriction, so he can make the switch without discussion, but if it's reverted, it needs to be discussed before the edit can be reinstated. If a page lacks an image, then Calibrador can add any image he so wishes." Several people agreed with that proposal; a few proposed an indef block; a few said he should be left alone because his pictures are so good. The thread was never closed and no action was taken.

      It appears that the same issues are still at work, except that now he is more insistent, IMO approaching disruption when discussion or controversy ensues. I am not proposing any particular course of action, but I think something should be done to limit or stop this promotional use of Wikipedia by an admittedly COI editor. I apologize for the length of this, but I wanted to be thorough. --MelanieN (talk) 15:41, 12 September 2016 (UTC)[reply]

      P. S. See also this May 2015 discussion at the 3RR noticeboard: Wikipedia:Administrators' noticeboard/3RRArchive280#User:GageSkidmore reported by User:Davey2010 (Result: Warned). --MelanieN (talk) 15:49, 12 September 2016 (UTC)[reply]
      The other user involved is stalking my contributions and changed the photo simply to undermine (prior to my edit, they had never contributed to the article). I preferred the other photo for technical reasons, especially sharpness, not because of the title. And the titles of images is a Commons issue not a Wikipedia issue, an issue that is not against any rule at Commons and was used by other photographers such as David Shankbone for years. Calibrador (talk) 16:38, 12 September 2016 (UTC)[reply]
      That was also proposed at the previous ANI. It would have the advantage of retaining his photos (which really are good) while eliminating the advertising aspect. We would still also need to deal with his excessive promotion of them, but a warning might suffice. --MelanieN (talk) 16:31, 12 September 2016 (UTC)[reply]
      Have not warnings already failed to suffice? I haven't time to review all the evidence now but if I believe what you write I'm thinking a topic ban from adding or discussing the use of his images is the way to go. BethNaught (talk) 16:45, 12 September 2016 (UTC)[reply]
      There was in fact a warning issued at the 3RR discussion, by User:EdJohnston: " User:GageSkidmore is warned that they may be blocked for disruptive editing if they continue the pattern of edits documented in this complaint. In particular, any warring to promote your own photos over those taken by others can be sanctioned. Continuing to revert regarding a picture where it's evident that you don't have consensus may lead to a block." He probably did violate it at the Anne Holton article, and possibly others. --MelanieN (talk) 16:53, 12 September 2016 (UTC)[reply]
      (Non-administrator comment) 1. Rename all photos. 2. Allow him unlimited contributions to Commons, like anybody else. 3. TBAN from advocating any of his own photos. This would remove his existing vote at Talk:Donald Trump, which has so far been allowed after discussion, unless we grandfathered that case. 4. Handle any disruptive editing like any other disruptive editing.
      If any of his photos is in fact superior to the alternatives, other editors will find it and routine consensus-building will choose it. They won't need selling. In the end, his past behavior in this area appears self-defeating; some editors who are aware of it may tend to find reasons to oppose his photos simply because they don't like his history of fuzzy-ethics tactics. ―Mandruss  16:55, 12 September 2016 (UTC)[reply]
      Well he is right, if the photos are sourced from commons, naming of photos at commons is a commons issue. So realistically the only recourse here would be to remove them all from the articles they are used in. But doing that merely because they are named after the author is hardly benefiting the encyclopedia. Likewise unless there is actually a quality issue (are his pictures being replaced with higher quality ones?) using a lower quality picture just to avoid using one with his name in it is also not benefiting the encyclopedia. Limiting him to 0 reverts where he adds a photo should probably solve the issue? Only in death does duty end (talk) 17:02, 12 September 2016 (UTC)[reply]
      If my edit is reverted legitimately by a user not stalking my contributions, violating
      WP:Hounding (users like Winkelvi who follows me around from article to article), I don't have any issue with someone reverting my photo. The only time I can think of where I may have reverted was when I thought there was enough consensus, and even then it was not more than once or twice that I reverted within a span of a few days. And I was unaware of any rule of advocating for your own photo. Winkelvi has twice, or probably more, chosen to upload their own photos (not taken by them, but uploaded by them) in an attempt to replace an uncontroversial edit by me. Calibrador (talk) 17:08, 12 September 2016 (UTC)[reply
      ]
      My warning to
      User:GageSkidmore/User:Calibrador from May 2015 has been mentioned above by User:MelanieN. Technically, he has now engaged in the behavior I warned him against, ("warring to promote your own photos over those taken by others") since he reverted three times at Anne Holton on September 11 to restore his own photo to the article. Unless he makes a suitable assurance about this future behavior, I think a block is called for under my previous warning. EdJohnston (talk) 17:19, 12 September 2016 (UTC) Withdrawing my first comment. This is indeed a pattern of edit warring by User:Calibrador, but it's not a simple question of preferring his own picture over ones taken by others. At Anne Holton he was reverting to provide a different picture from his collection, which also had the effect of providing a caption that contains his own name. EdJohnston (talk) 17:59, 12 September 2016 (UTC)[reply
      ]
      Both of the photos involved were my own. And the user reverting has been
      WP:Hounding my edits across many articles. Calibrador (talk) 17:20, 12 September 2016 (UTC)[reply
      ]
      Yes, "warring to promote your own photos over those taken by others" is irrelevant when he's putting in his own picture in place of his own picture. This doesn't rule out sanctions for "Warring..." or for general disruption, if they're appropriate, but check the page history before assuming that he's promoting his own picture over someone else's work. Nyttend (talk) 17:47, 12 September 2016 (UTC)[reply]
      Nyttend, Melanie's point was that the photo he preferred had his name in the file name and the other didn't. --NeilN talk to me 17:53, 12 September 2016 (UTC)[reply]
      That was the only reason I could think of why he would prefer this picture File:Anne Holton by Gage Skidmore.jpg over this one File:Anne Holton DNC Hdqtrs Phoenix AZ Sept 2016.jpg, which to an amateur eye is a much better picture of her. BTW the final reversion to the second picture was done by an uninvolved third party, purely on quality grounds. --MelanieN (talk) 18:37, 12 September 2016 (UTC) P.S. The editor who posted the second picture has explained their reasons for doing so on the talk page. Calibrador has not commented there, just reverted. --MelanieN (talk) 18:43, 12 September 2016 (UTC)[reply]
      If it were any other user, I would've gladly participated in a talk discussion, but I chose to use their own words from when they reverted an uncontroversial change I'd made to an article that they objected to nearly a week after I'd made the edit, as I saw it as a double standard, and no use in discussing with someone who simply intends to disrupt because I made the edit. Calibrador (talk) 18:48, 12 September 2016 (UTC)[reply]
      (edit conflict) I've added photos I've taken uploaded by someone else without my name in the title in the past, and I had absolutely no issue in the case of the Holton photo. You'll notice that they reduced the image size to 200px on the Holton article, this was because it was out of focus, and something I do not necessarily worry about on Flickr where it is best to upload as many photos as possible, unless they are completely out of focus and thus unusable. My intention of reverting was because the photo I uploaded was sharp, and the user was intentionally following me around from article to article to undermine contributions, and adding their own uploaded versions. You can see a similar instance at the article Landon Liboiron, which Winkelvi had also never edited until I made an edit. They are tracking my edits to revert me, participate in discussion where I participate, and intentionally making edits in order to create conflict. Calibrador (talk) 18:02, 12 September 2016 (UTC)[reply]
      I was just going by the comment from Ed just above mine, "...in the behavior I warned him against...", which didn't say anything about filenames. Nyttend (talk) 17:58, 12 September 2016 (UTC)[reply]

      I think any action taken should be solely based on behavior, not on the fact that the file name has his name in it. I don't see that as a problem, assuming everything else is above board. 🔯 Sir Joseph 🍸(talk) 17:24, 12 September 2016 (UTC)[reply]

      • I've never agreed with the naming and have made it known I disapprove of them, I recall there being a discussion somewhere (may of been AN3) where we were basically told all of these names are a Commons issue ..... I really don't know how to say this without being offensive .... Ummm most people at at Commons aren't the brightest of people .... so having a discussion about it over there would simply end up with me repeatedly smashing my face against a brick wall hence why I've not done anything about it, As I said I disagree whole heartedly with the promotional names however I know Commons won't do jack about it and I know we can't do anything here either .... So unless WMF gets involved (which would be extremely unlikely) there's nothing no one can do except allow it to continue. –Davey2010Talk 20:54, 12 September 2016 (UTC)[reply]

       Comment: Commons does not have a 'file naming' policy.... we have a proposed one, that will probably never be adopted as official. Instead, we commons:COM:RENAME, which is on the 'more relevant' subject of renaming files to better names. A major concern with filenames, and the reason why any proposal to bulk-rename the 2,339 files with "by Gage Skidmore" in the name is a dead letter, is filename stability... renaming should be as uncommon as possible, to avoid breaking external links. Like it or not, Commons does not 'exist' to serve merely as an image archive for Wikipedia... we have many external 'customers', and renaming files breaks hotlinking, and possibly even proper attribution. Breaking this is exactly why I removed Gage's right to rename files... as well as a prolonged refusal to discuss the matter.

      The files can be renamed, per Commons guidelines, to 'better' filenames that more accurately describe the subject of the image, but we're not going to arbitrarily rename them just because people dislike the existing one. If you are going to start prohibiting the use of files merely because the filename includes that of the author, there are a lot of images of 'old masters' paintings I can point you at. We also have many (many, like hundreds of thousands) of images such as HABS photos that include attribution in the filename, and it's unquestionably appropriate. Reventtalk 04:59, 13 September 2016 (UTC)[reply]

       Comment: Calibrador is also editing under the username User:Gage, both on this wiki and at the Commons and seven other wikis. — Diannaa 🍁 (talk) 05:37, 13 September 2016 (UTC)[reply]

      I've never contributed to Wikipedia with that username. The only time that there were contributions was when I renamed three files at Commons which made an edit on Wikipedia as part of the automatic file naming system, something that's not manual and thus unavoidable on my part. Calibrador (talk) 07:23, 13 September 2016 (UTC)[reply]
      Good catch @Diannaa:, he basically used that account to "abuse" his "move" rights on commons (its automated, when you change the name of an image on commons, your accounts on other wikis will make the change on every wiki where the image is used on)..he abused his rights there to change the image name of Bryan Fuller and Kiefer Sutherland to carry his byline (name) in the image name and yet he will claim here that he did not abuse his rights ...lol..--Stemoc 10:58, 13 September 2016 (UTC)[reply]
      That's not true; User:Gage has not moved any files since July, and had his file mover right removed on August 4. User:Calibrador does not have the file mover right, as far as I can tell. — Diannaa 🍁 (talk) 13:26, 13 September 2016 (UTC)[reply]

      Calibrador: arbitrary break

      • If someone is looking for more insight into Winkelvi and Calibrador's interactions, I suggest you check out [27]. You can draw your own conclusions.
        ¤ 20:19, 12 September 2016 (UTC)[reply
        ]
      This wasn't in the interaction report, but Winkelvi also took it upon himself to make a series of edits to the
      ¤ 22:26, 12 September 2016 (UTC)[reply
      ]
      Looks like he took it upon himself to improve an article. I see nothing remotely improper there, but I tweaked it. ―Mandruss  22:50, 12 September 2016 (UTC)[reply]
      • Winkelvi does have a habit of following people around. I think this does change the full focus of this discussion. One question that should be addresses is if there's a difference between regular photo reverts and edits and those with Winkelvi. 🔯 Sir Joseph 🍸(talk) 20:21, 12 September 2016 (UTC)[reply]
      • I just added the arbitrary break That interaction link is conclusive, and edits like this are particularly damning; I suppose I can imagine someone watching a bunch of Trump-related articles without previously editing them, but who watches wikiproject templates for talk pages? If you're long-term feuding with various people, and you're willing to be following people around to confronting them on pages you've never edited and not likely to have watched, you're being quite disruptive. Blocking for two months, since the previous one-month block didn't dissuade Winkelvi from
        treating Wikipedia like a battleground. Nyttend (talk) 20:39, 12 September 2016 (UTC)[reply
        ]
      This is really quite sad, Nyttend, you should really try to follow the drama that comes with Calibrador/Gage Skidmore, he uses wikipedia to not only promote himself but he is also in the habit of crying foul when people point out to him that he is using wikipedia to self promote himself and then he would claim those users are "hounding" him and yet he has never really been blocked for a longer term. I'll put that down to the failure of the administration system on enwiki more than anything else..playing victim has always worked for many of our incorrigible trolls on this wiki and its quite sad that they are protected. This isn't the first time this has happened, Calibrador/Gage brought me to this same board last year for the same reason and then he brought another user a few months later, both of us were telling him not to use the wiki to promote himself and not only that, he would intentionally remove another previous image and replace it with one of his own and one with his own byline (xxx by Gage Skidmore). It has been mentioned above by User:MelanieN. I haven't reported him to WP:ANI because I know that the failure of the system means that nothing would be done and it will be just a waste of time but since you have gone ahead and blocked Winkelvi who was just trying to stop Gage/Calibrador from using wikipedia to self-promote himself for 60 days, I hope you give a similar punishment to Calibrador.....It's bad enough a person is punished for trying to stop a 'crime', but to let the perpetrator walk free is even worse. Either you be balanced with your judgement or remove the block on Winkelvi. Yes Harassment is apparently a big issue on enwiki but it usually does go both ways..You cannot just block one person for it..There is something else you should know. Calibrador has another account on commons, Gage. Last month, 2 of his rights were removed due to abuse. Those rights were move rights because he would blatantly change the name of images on commons with the one carrying his byline (name) and his Licence Reviewer right, a right given to trusted Commons users who review images from flickr to ensure that those images fulfill our inclusion criteria and he used that right to 'pass' his images or images that were added by him which are not allowed. Again, i urge you to really go through everything that has been said on this ANI before coming with a decision. I do not agree with the judgement you passed on Winkelvi but its even worse that you only did it to one of the perpetrators..Last year we agreed with @Nick:'s proposal in regards to this but like the many other threads about him that have come on this board, non have ever ended with a final solution, so maybe this time we should..We cannot play this cat and mouse game, we cannot keep allowing wrong people from being blocked because the admins refuse to do whats right and we should definitely not continue to waste time with this. We block users who use the project to self promote themselves (articles/namespace), so why do we have a different rule for images?...Can we end this madness this week? there are much more pressing issues that needs to be discussed instead...--Stemoc 03:48, 13 September 2016 (UTC)[reply]
      Few people need to look at Winkelvi's block log to know of his long, exasperating, exhausting history of behavior issues. He has to inflate everything into a virtual religious crusade, doing at least as much harm as good. He is very quick to anger, seemingly unable to shake his perpetual battleground mentality despite the years of complaints about it. If I had my way he'd be banned from policing other editor behavior because he simply lacks the temperament for it. To be clear, I'm not siding with GS over WV, they are both culpable. And I doubt Nyttend is either. For some reason that baffles me, these conflicts are always treated as binary, as if only one of the parties is at fault and our job is to decide who it is. But that is almost never the case. ―Mandruss  04:08, 13 September 2016 (UTC)[reply]
      I'm not really defending Winkelvi, I'm aware of his Battleground attitude, I just feel that atleast the blocks should be fair..How many times has WV been brought to this board? or ANI? the difference may be that there was never any solutions/sanctions passed in regards to Calibrador even if there were strong support for it..He has been brought here on or ANI more than 5 times already and the worst (and infact ONLY) block he ever got was a 3RR (which i also got then)..Infact, quite a few people mentioned in that last ANI that if we don't come up with a solution, it will happen again, and we are here now..Its obvious now that even if we tell Calibrador to stop adding images with his name as the byline, he will completely ignore that request, just look at his commons talk page, the last time he actually "replied" to anyone regarding his images was back in July 2013 ..we are way past that as a solution, its either a sufficient block (1 month or more) and a final warning or an indefinite ban, anything else would be just a slap in the face of our own policies...--Stemoc 05:01, 13 September 2016 (UTC)[reply]
      Well you laid down a large post including (1) "This is really quite sad, Nyttend", apparently referring to the block of WV, (2) "punished for trying to stop a 'crime'", and so on. How is that "not really defending Winkelvi"? Looks like defending to me. I think the block is fair, per Nyttend's rationale and WV's history, and I don't link that to Calibrador in any way. If you're under the impression that WV's block precludes a sanction against Calibrador, or that it ends this issue, you're mistaken. ―Mandruss  05:24, 13 September 2016 (UTC)[reply]
      Did it sound like i was defending Winkelvi or did it it sound like i was asking Nyttend to block Calibrador too? I agree that Winkelvi deserves a block because he took it a bit too far this time, but 60 days and yet at the same time, the problematic user walks away scott-free? I do not see a justice in that, do you? Its about being fair, always two sides of a coin, we know what WV did to get his block, now lets flip the coin around and see why Calibrador should get a similar one too..Please, blocking one editor to warn another is not really a sanction is it?..This thread is about Calibrador and yet somehow for possibly the 4th time (if not more), someone else gets blocked....I see a trend here and its not something that gives you hope of a proper outcome..Personally, for now, WV should be unblocked so he can come make his case here, it was a bit silly to block him before allowing him a chance to explain himself, I think we all would like to know what led to this discussion and blocking one of (if not "THE" main) parties involved beforehand is not really a solution--Stemoc 05:43, 13 September 2016 (UTC)[reply]
      Who's walking away scot-free? The Calibrador issue remains very open and that's crystal clear. His issue is more complex so it takes longer than half a day to resolve. You seem to be reading Nyttend's action and comment like a close of this discussion. It simply is not. ―Mandruss  05:51, 13 September 2016 (UTC)[reply]
      @Stemoc: I completely agree. Winklevi didnt even get a chance to make one reply on this thread. Also, you were not defending Winkelvi, but this thread was started for the behavior of Calibrador not Winklevi. That is a whole other issue, We should be focusing on his edits and behavior, not that of others. Doing a wrong because someone else does a wrong, doesnt make your wrong right. Chase (talk) 05:54, 13 September 2016 (UTC)[reply]
      I believe that admins can issue blocks without discussion, the discretion is theirs. Winkelvi is free to appeal the block, if he is unable to see that it's more gift than punishment and make effective use of his two months away from this madness. I say we leave that issue to him and the admin corps and drop this line of discussion. At least I've said all I'm going to about it. ―Mandruss  06:10, 13 September 2016 (UTC)[reply]
      That aside, I believe the block is just and right, unless something is not done about Calibrador as well then it would be severly unfair. Chase (talk) 06:21, 13 September 2016 (UTC)[reply]
      Just would like to quickly note that Davey2010 and Stemoc have also tracked my contributions in the past, in one instance Davey2010 reverted me across a dozen or more articles where I'd contributed a photo including articles that did not have a photo (he then removed them) and was warned and reverted by another user, possibly an admin, but I don't recall specifically. I'm guessing that's how both of them found this discussion was from looking at my contributions to see what they could follow me around and oppose today. Calibrador (talk) 07:49, 13 September 2016 (UTC)[reply]
      If you're persistently following someone around without very good reason (long-term, not merely reverting a big group of edits all together), you need to be shown the door, at least for a period of time, if not indefinitely: this is a project for building an encyclopedia, not for tearing down other people, and editors focused on harassing others fundamentally aren't here to build an encyclopedia. Had I somehow discovered Winkelvi's actions independently, without any input from other people, I would have been strongly inclined to block without warning; the biggest thing that would hold me back was a question of "am I seeing this rightly, or have I misunderstood somehow", and the fact that others also came to the same conclusion first, plus the fact that he'd previously been blocked for battleground behavior, removed that doubt. Also, regarding the next subsection: I'm not going to issue any sanctions against Calibrador because (1) I've checked his recent editing at Commons and haven't seen any policy violations (the only instances of people rejecting Commons policies in this discussion are people who are urging violations of the file naming policies in opposition to him), so with my Commons admin hat on, I say that nothing's wrong; and (2) I've not checked his recent editing here, or carefully read through what his opponents have said here at this discussion about his editing here. It's not a blatant case such as childish vandalism or clear POV-pushing, so would be reckless for me to issue a block or support other sanctions without careful checking. I won't support any proposals and won't oppose any proposals. Nyttend (talk) 12:21, 13 September 2016 (UTC)[reply]
      Ofcourse you won't take any actions on Calibrador, that is what i was telling Mandruss earlier because if you intended to take actions against him, you would not have blocked his only critic in Winkelvi without giving him a chance to explain himself. You decided to jump the gun instead because of your own personal assumptions of him, "Oh yeah, WV has a habit of Battleground behavior so yeah its his fault, I'll block him now"..May I ask, which account of Calibrador did you look under cause I'm pretty sure he does not use that account on commons and furthermore, @Nyttend:, as a commons admin, I'm sure have you been following the Commons: ANU board and may have noticed this last month and 2, its apparent you have not been following the recent drama on this wiki so I'm sorry to say but you are probably not the right admin to make such a decision since you are misinformed, maybe you should let another admin who is aware of the situation decide then? ..--Stemoc 12:50, 13 September 2016 (UTC)[reply]
      I tend to stay away from COM:ANU because (unlike the other COM:AN pages) it tends to be populated with drama warriors. If you are familiar with Commons policy, you will see that the big issue there was renaming files that didn't meet the renaming criteria (thus disrupting other projects, and potentially off-wiki uses) and misusing the reviewer right. As far as the issue of blocking Winkelvi: other people alleged, with some links, that he had been engaging in long-term policy violations, and after doing my own investigation, I could see that they were right. Given
      WP:EQUAL, I don't care who you are: if I see that you're engaging in long-term stalking, doing your best to harass someone else over a long period of time, I'll block you for an extended period of time, regardless of who you are. Nyttend (talk) 13:00, 13 September 2016 (UTC)[reply
      ]
      @Stemoc: you are probably not the right admin to make such a decision - As I said, WV can appeal. Appeals have to be processed by a different admin, precisely because of the potential for error. As I said, I would enjoy my involuntary wikibreak if I were in WV's place, but he is free to ask a different and uninvolved admin how he feels about it. I suggest you let that process work as it was designed, and cease your attack on an experienced and respected admin for doing a very tough, thankless, and pay-free job to the best of his ability. ―Mandruss  14:01, 13 September 2016 (UTC)[reply]
      Ofcourse WV can appeal, that isn't really the issue here is it? and what do you mean to 'cease my attack'? All i see is an admin who did not do his homework trying to make a decision which affects many people and not just this project but possibly commonswiki as well, its not an attack, its an observation and again, i'd be happy to stand back and see some form of solution be found but as i said in my other posts, this user has been brought to WP:AN (and WPAN/I) either by himself or by other editors many times and has NEVER faced any consequences of his actions so pardon me if I refuse to wait another 14 months to come back here to discuss the same problems again and again and basically see the same outcome, which is basically 'no action'..remember the old saying "fool me once..."? ...yeah not falling for that again... --Stemoc 15:15, 13 September 2016 (UTC)[reply]
      I see things differently. No admin is required to answer to a single over-excited, emotionally-invested editor who shows little grasp of what it is to be an admin, and I think Nyttend has already given you more explanation than you deserved. Continue your ranting all you like, but not with me. ―Mandruss  15:37, 13 September 2016 (UTC)[reply]

      Calibrador: Can we get back to the main point here, please?

      My goal in filing this report was not about blocking Winkelvi. That was a side issue, and I'm sorry it happened. (In the space of 20 minutes from beginning to end, with no time for discussion or evaluation - but what's done is done.) Now can we get back to considering what we are going to do about Calibrador/Skidmore's conflict of interest, promotionalism, and disruptive edits? --MelanieN (talk) 03:36, 13 September 2016 (UTC)[reply]

      @MelanieN: That's still ongoing in the parent section, if slowly. ―Mandruss  03:40, 13 September 2016 (UTC)[reply]
      Calibrador's attitude towards other users has definitely caused a problem. Every warning that has been given to him has been ignored and something must be done because he continues to cause animosity with others. He continues to promote his pictures as being better, simply because they are his and
      WP:BLUD. My personal feeling is the Winkelvi should not have been banned so soon in this discussion, especially since we have not come to some sort of resolution to Calibrador's disruptants of Wikipedia, creating this discussion and several others from his behavior when all of our time could be spent improving Wikipedia. If WInkelvi is going to have a ban, then Calibrador, the one that started the whole issue in the first place should have the same punishment, if not more rash. Chase (talk) 04:49, 13 September 2016 (UTC)[reply
      ]
      Blocked, not banned. ―Mandruss  05:14, 13 September 2016 (UTC)[reply]
      @Mandruss: Thank you for correcting me. Someone said "topic-ban" earlier and my dyslexia mixed up my jargen. Chase (talk) 05:16, 13 September 2016 (UTC)[reply]
      Responding to CCamp2013's accusations, disregarding the fact that they have opposing opinions in many of the discussions they're referring to, the only time I can think of that I've advocated my photos over someone else's in an extensive debate is the Talk:Donald Trump discussion, which is very recent. In this instance, it's not as if I'm the only one advocating for my photos to be added, there's currently a simply majority among at least a dozen or more other users who have agreed, and a little less than that who have taken the opposing view point (just to give context for uninitiated users). In instances where I thought it was appropriate to respond, given that it is a discussion that is meant to come to a consensus among two or more opposing parties, I took the time to respond to points made by a couple of other users. From this, I don't recall any unwarranted conflict being created, but I was not aware at the time that responding to multiple people was against any sort of rule. Same with advocating for a photo you took, I'm still not aware of any rule against that. If that's a COI then I have no problem with disclosing fully my role, or not participating in said discussion in a way that causes disruption. Calibrador (talk) 07:36, 13 September 2016 (UTC)[reply]
      @
      Talk:United States presidential election, 2016, and then only notified certain users here, which interestingly enough all were in favor of your picture that weighed in, those same users proceeded to the Donald Trump page. You have also displayed this type of behavior for the Mike Pence photo. Here and here the editor states he is changing the photo per discussion, but i fail to see where the discussion took place, just a suggection here that it looked good according to you and User:TL565. he also made this edit in which he states "introduce based on talk and most agreeing, this is also more than a year newer, as it is from this week", but in another page states "You must obtain consensus on the talk page to change the photo, recentism does not award you consensus" here. There are countless examples I could recite, but in all of them you can see each photo had his name on the filename. This is how he is promoting his pictures, in favor of others. Chase (talk) 08:30, 13 September 2016 (UTC)[reply
      ]
      In response to the statement you quoted, I was referring only to one instance, which taken out of context looks like I'm speaking about all my contributions. I was only referring to the Trump discussion. Calibrador (talk) 08:36, 13 September 2016 (UTC)[reply]
      • Photos named and stored at commons are a non-starter for reasons explained above. You can argue its self-promotion and google index it yadda yadda, but its not prohibited and how google displays its search results is not a concern of wikipedia.
      • Unless there is actually a *quality* issue with the photos, removing good quality photos from articles because of how they are named at commons is not improving the encyclopedia. In fact I would argue its actively harming it.
      • The only substantial issue I can see is that there have been instances of edit-warring over their own photos (which taking into acocunt the WV issue above have not all been entirely of Calibrador's own making) a simple 1rr restriction limited to images in articles should solve that? Only in death does duty end (talk) 07:59, 13 September 2016 (UTC)[reply]
      I don't recall, except maybe in a very, very rare instance edit warring (especially within 24 hours), for an article to include my photo. Most of the edits I make in regards to photos would probably be considered uncontroversial. The Anne Holton instance is an anomaly as Winkelvi was plainly obviously following me around article to article and doing the things that I listed above that I don't want to rehash. I'd also suggest that you would probably have to look out for contributions by certain users who know that there would be a 1RR and would revert me knowing that I can't revert back (for instance, users like Davey2010 or Stemoc who take issue with the file names despite it being a Commons issue, and there being no rules against it on Commons). Calibrador (talk) 08:10, 13 September 2016 (UTC)[reply]
      You're quite correct that on Commons, we allow files to be uploaded under a wider range of filenames, and with over 33 million media files, appending usernames to filenames is something that eases the search and location of media files. I generally upload images with my username as part of the file name.
      English Wikipedia, is free to restrict the use of any media files from Commons, something we do with the 'Bad image list' and if community consensus here is that we will not use media files with usernames or full names as part of the filename, then you would need to respect any consensus which emerges on that basis (not that I see any consensus for that, or that serious discussion has been undertaken to establish if that consensus exists).
      I would again re-iterate my original comments which MelanieN linked to in the opening comment of this page - your contributions are valuable but we (both here on English Wikipedia and on Commons) want to give other contributors reason to take photographs specifically for Wikimedia projects, and to upload their existing material to Commons. That means that other contributors must have a fair chance of seeing their images being used.
      I would re-iterate my option for resolving this is to allow Calibrador to add images to pages which have no images freely without restriction, but where he is replacing other photographers work, he be subject to a 1RR restriction. I would also suggest that Stemoc and Davey2010 be similarly restricted in the frequency they can remove Calibrador's images so nobody has an upper-hand in this dispute. Nick (talk) 09:44, 13 September 2016 (UTC)[reply]
      This seems reasonable. Only in death does duty end (talk) 10:35, 13 September 2016 (UTC)[reply]
      @Nick: A clarification: When you say 1RR restriction, you mean 1 revert period, right? Not one revert per 24 hours, as the term is used at Discretionary Sanctions? Thanks. --MelanieN (talk) 16:52, 13 September 2016 (UTC)[reply]
      @Nick: we have already had this option last year (As linked above my MelanieN), nothing has changed since then..Infact I have not reverted any of his changes since last year on enwiki bar one as I have realise that he is "protected" by the admins on this site. He is just using Davey2010 and me as an excuse to continue "vandalising" (Sadly that is the correct term for what he is doing) by shutting out those who criticize his actions...please read the previous discussion we had on that ANI which he filed on me and compare it with his edits since then, nothing has changed, if anything, he has become worse. He is obsessed currently with Donald Trump because he has been able to "forcefully" add his images to other politician pages (from both the democratic and republican sides), all except Donald Trump where users have preferred the image taken by Michael Vadon (another photographer who releases his images freely but doesn't force its use on every article or adds his name to the byline of every image). As i said last year, for Gage its either you use his IMAGES or he will take you to WP:AN/I for "hounding" him...I have never been against him using /adding images to those articles without images but he has the habit of replacing images added by others with those belonging to him and carrying his name in the byline ( not to mention trying to rename images on Commons and add his name to the image title) and that is abuse.. Implementing the 1RR rule will not work, what he deserves is a block and a final warning, enwiki admins have been ignoring his abuse for far too long....Wikipedia is grateful for his contribution but if he is going to use that to blackmail or force users to do his will then by all means, we are better without him, remember, we do not need him, he needs us, he needs One of the top 10 most visited sites to "promote" himself..Yes Commons policies are stupid because they have not been updated in ions, whose fault is that really? not those trying to stop users from abusing the outdated policies we have surely...So if you want things to change, it should start here, we need to toughen our policies on what we deem as self promotion because that is exactly how he has managed to escape getting blocked for the last 7 years...I'm against the 1RR idea put forward by Nick, this would have worked a year ago when it was brought up on WP:AN/I but its far too late for that now, he would just make the changes using his IPs like he has done before..--Stemoc 11:26, 13 September 2016 (UTC)[reply]
      There's the wall of text of accusations and bias based on non-existent policy! I was waiting for it. Calibrador (talk) 11:32, 13 September 2016 (UTC)[reply]
      Yep, I realised its the only way to get you out of your cave as WV has unknowingly done ..lol..now just waiting for your accusations of HOUNDing and stalking :) ..--Stemoc 11:43, 13 September 2016 (UTC)[reply]
      I'll assume
      good faith and trust you didn't come upon this discussion from my contribution history. Maybe review Wikipedia:Get over it? Calibrador (talk) 11:51, 13 September 2016 (UTC)[reply
      ]
      @Stemoc: Implementing the 1RR rule will not work Why not?
      You seem to be emotionally invested in this issue, and I question whether your involvement is helping much. In contrast, I had never heard of Calibrador or Gage Skidmore until a few days ago, but I think I'm adequately up to speed on the history from reading the comments made here. ―Mandruss  12:35, 13 September 2016 (UTC)[reply]
      That's their way of saying they just want me blocked. Calibrador (talk) 12:42, 13 September 2016 (UTC)[reply]
      If Calibrador is a human being, I don't see how he can possibly put Wikipedia's interest first, comparing his photo to another with complete detached objectivity. He necessarily has a completely natural bias favoring his own work, and I'm not certain he understands that. Going forward, the vast majority of Wikipedia editors will be unaware that Calibrador = Gage Skidmore = photographer of the photo. I could live with the suggestion in Nick's closing paragraph with the added requirement of full-disclosure edit summaries. Calibrador stated above, I have no problem with disclosing fully my role, so he shouldn't object.
      Adding image of my own work
      Replacing image with one of my own work, which I feel is superior because...
      Calibrador, we already have policies in place to address stalking and harassment issues. One two-month block was applied for that yesterday, as you know, and two months is hardly a wrist-slap block. So how about we agree to cross that bridge if we come to it? As for I'd also suggest that you would probably have to look out for ..., I suspect it would be up to you to bring any such behavior to community attention if it happens, as no one will have the time to monitor the situation on your behalf. I would hope that you would distinguish fairly between that kind of behavior and normal content dispute, although that's often not easy when there are repeated normal content disputes with the same editor(s). As I said previously, you will probably receive some opposition resulting from the bad rep that you created for yourself by persistent and long-term disruption, refusing to play by the rules of editing process, and in my opinion that's inevitable until you have changed the rep through years of much-improved behavior. ―Mandruss  12:43, 13 September 2016 (UTC)[reply]
      I wasn't implying that someone should monitor the 1RR and those other users on my behalf, I was just forewarning as I thought that could easily be a potential result. Calibrador (talk) 12:47, 13 September 2016 (UTC)[reply]
      Mandruss, I urge you to read up on the previous discussion linked by MelanieN in the Original Post....long story short, He changed his name from GageSkidmore to Calibrador because he did not want people to figure out he was intentionally forcing his images into articles so he got his name changed to "fool wikipedians" into thinking he has no links to the photographer, yes, i used the term "fool wikipedians", its hurtful but its the truth..anyone that knew that and pointed it out was seen by him as people who were either stalking his edits or wikihounding him (his words)..If you went through his edits and linked the times where he has forced his own images onto articles by replacing previous images that were not taken by him, he called them
      Hounders..so basically collecting facts about his abuse made you a hounder...If that is his definition of a hounder , then yes, I'm totally a hounder and I will "hound" him until an admin decides that its about time he faced the consequences of his long running abuse of our policies and his consistent and persistent attacks on users who disagreed with his images being "forced" onto articles..Last i checked, We were here to build an encyclopedia, not the Yellow pages--Stemoc 15:33, 13 September 2016 (UTC)[reply
      ]
      Once again assuming bad faith in regards to username, which they were previously warned about. Also, you regularly "force" your own uploads into articles, granted they are not your photos but you uploaded them. One example from just today. Calibrador (talk) 15:46, 13 September 2016 (UTC)[reply]
      this seems like Déjà vu... You are deflecting again, its not 'bad faith', its 'facts'..sometimes you notice these things as days before the name change, you were called up on trying to force your own images onto articles, even on the day of your usurpation and after it (you want me to add more links?) and all because @William S. Saturn: caught you and reported you to 3RR and because you did not want your customer to find out hat you were doing, you blanked your talk page not once but twice after another editor whose images we used pointed out to you that u were self promoting your images and you very next edit was to change your name because you knew it would affect your "business" ...Are you gonna claim something else now? oh and btw, this is not hounding, its finding proof and calling you out..oh and regarding Suu Kyi, it was a 3 year old image, I found a good new one, replaced it..there is no issue with that..--Stemoc 16:08, 13 September 2016 (UTC)[reply]
      What did you say about forcing your own uploads into articles? I couldn't hear you over the BS. Calibrador (talk) 16:27, 13 September 2016 (UTC)[reply]
      @Calibrador: Wait, was the point of all those links to try to convince people you are forcing your photos into articles? Because that is what it did for me. In all of the instances you supplied, and ill admit I went through the first like five because i started to see it was wasting my time, Stemoc was either inserting a photo for the first time and never went to the talk page to promote his preferred picture or in one instance, was changing the photo back to the one that had been their after Winkelvi changed it. Stemoc never engaged in the kind of behavior you did, guiding the discussion, after you started the discussion, and challenged all that opposed you. He respected the decision of some one who reverted him as far as I could tell. Chase (talk) 16:55, 13 September 2016 (UTC)[reply]
      * Comment: Okay, I went through the last few links and I can indeed say, it was a waste of my time and only got worse. In the last, all but the first five, he changed the photo and all were unopposed! These are completely different situations than what is going on here. Chase (talk) 17:00, 13 September 2016 (UTC)[reply]
      So I should discuss any change I make, but don't discuss it too much especially with people that disagree with you. You're grossly blowing things out of proportion, it's one or two discussions, and largely based on perception. I was not aware of this "bludgeon" policy prior to its mentioning, and I haven't done anything to violate it since. I was simply responding as an active talk page participant, and I have an opposing viewpoint to yours so not surprising that you continue to harp on this. If I reverted on the article itself, it was after I thought there was at least a semblance of consensus, and I did not revert more than once or twice. Stemoc is not a nice person. While looking through their edit history, I found this edit summary:

      "restore external links , dumbass removed it"

      Stemoc was complaining about me inserting photos into articles using "force," most if not all of which were non-controversial and were not reverted, and I responded with instances where they had done the same thing. I was responding to Stemoc's accusation and pointing out their hypocrisy. Calibrador (talk) 17:07, 13 September 2016 (UTC)[reply]
      @
      WP:BLUDGEON, especially with almost 30,000 edits? Chase (talk) 17:26, 13 September 2016 (UTC)[reply
      ]
      You're constantly pointing out one instance. I could find many instances where I did not revert if I was reverted. Calibrador (talk) 17:31, 13 September 2016 (UTC)[reply]
      I'd like to see some of those. Recent, please. --MelanieN (talk) 17:42, 13 September 2016 (UTC)[reply]
      here, here, here, here, here, here, here. So one instance? Chase (talk) 18:06, 13 September 2016 (UTC)[reply]
      @MelanieN: Did you see my examples? Chase (talk) 23:04, 13 September 2016 (UTC)[reply]
      [29] [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] Calibrador (talk) 18:47, 13 September 2016 (UTC)[reply]
      Thank you. It is clear that you don't always restore your photos if they are reverted. --MelanieN (talk) 00:01, 14 September 2016 (UTC)[reply]
      @MelanieN: You do realise most of the images he does not change back are actually his own images which were either uploaded via his flick feed or cropped from his own uploads but not carrying his byline? or those added by other sources or established editors and admins and none of those were "reverts" or "undos" of his edits, they were photo replacements, as in the image were updated, not rollbacked to a previous version before his..He is still lying here..checks those links again..I urge you :)--Stemoc 01:29, 14 September 2016 (UTC)[reply]
      • I just wanted to mention that I've commenced a discussion at Wikipedia_talk:Conflict_of_interest#Self-promotion_via_images on whether the issues raised in this discussion should be addressed in our COI guideline. Coretheapple (talk) 16:32, 13 September 2016 (UTC)[reply]
        • You might have just dropped a link to this discussion there. Now we'll have two parallel discussions of the same issues. We should resolve this issue before we think about changes to WP:COI, in my opinion. ―Mandruss  16:40, 13 September 2016 (UTC)[reply]
          • I think you mean the COI Noticeboard. Talk:COI is for discussion of the guideline, and I would think that a discussion of the guideline is independent of however this specific situation is resolved. COI is a behavioral guideline, not policy, and really doesn't impact very much on what is happening here. But if you think discussion there should be put on hold there until this resolves, I have no problem with that. Coretheapple (talk) 16:45, 13 September 2016 (UTC)[reply]
            • Yeah, it's still a parallel discussion of the same closely-related issues, with the possibility of different discussions reaching different conclusions, which then have to be resolved in a third discussion. Messy messy. ―Mandruss  16:48, 13 September 2016 (UTC)[reply]
              • No, I think the underlying issue in the above multiple walls of text is pretty straightforward. But feel free to ask on the WT:COI page for a moritorium on the discussion there, as I see someone has already weighed in. Coretheapple (talk) 17:04, 13 September 2016 (UTC)[reply]

      Calibrador: arbitrary break 2

      Per Wikipedia tradition, we have an enormous and growing wall of text of bitter, often petty bickering between the primary involved parties, with no end in sight. This is never productive in my experience. I propose that Stemoc and CCamp2013/Chase leave the discussion and trust that more detached, dispassionate participants have enough information to resolve this in the project's interest. Calibrador needs to stay to defend his position, but not to directly involved editors with dogs in the fight. ―Mandruss  17:32, 13 September 2016 (UTC)[reply]

      Thank you. I was about to see if I can summarize what has been said up to now. I don't find much or any support for the following options: some kind of block; topic ban against adding photos; renaming of his photos; removal of his photos. What I do find as a possible proposal, a merger of ideas from User:Nick, User:Mandruss, and myself:

      Proposed action: (from Nick) Allow Calibrador to add images to pages which have no images freely without restriction, but where he is replacing other photographers work, he be subject to a 1RR restriction. I would also suggest that Stemoc and Davey2010 be similarly restricted in the frequency they can remove Calibrador's images so nobody has an upper-hand in this dispute. (from Mandruss) Require full-disclosure edit summaries, such as "Adding image of my own work" or "Replacing image with one of my own work, which I feel is superior because…" (from me) Limit his discussion at the talk page to a single !vote, including commentary and disclosure, per discussion section or subsection; a ban on replying to or arguing with other discussants unless they directly addressed him; a ban on attempting to assess or claim consensus, unless it is unanimous. Thoughts? --MelanieN (talk) 17:49, 13 September 2016 (UTC)[reply]
      @MelanieN: I agree with everything. Chase (talk) 18:15, 13 September 2016 (UTC)[reply]
      @Mandruss: I will not leave the discussion and I'm hardly a primary party involved. Discussion is an important part of Wikipedia. I am not overly passionate about or attached to the issue, but seeing what Calibrador is doing is wrong. So yes, I will put input into the conversation. Especially when false accusations are made. I have no biased. I just prefer one pic over another, and if the other pic gets consensus, I will respect that decision (neither picture is the best in my opinion). Chase (talk) 18:13, 13 September 2016 (UTC)[reply]
      As I said, we have enough information. Although less severe than Stemoc, your comments are generating far more heat than light. I can't force you to leave, but I have made the proposal and you will leave if there is a consensus for you to do so, else be guilty of
      WP:DE. ―Mandruss  18:19, 13 September 2016 (UTC)[reply
      ]
      CCamp2013/Chase has agreed on his talk page not to address Calibrador directly, and I have stricken his username from my proposal. ―Mandruss  19:07, 13 September 2016 (UTC)[reply]
      • Comment - I cannot be arsed to reply above so I'll shove it here instead - I used to revert Gage on quite a few articles however since being told about commons etc etc I haven't bothered reverting and probably won't bother (if he's adding an image to an imageless-article then I wouldn't revert however if he'd replaced for instance a donald trump image with his own without any discussion then of course I'd smack revert, In regards to the above I agree with that idea - If he's reverted by anyone then it should be brought straight to the talkpage and IMHO the 1RR should apply to everyone the project not just me or Stemoc (Me and Stemoc aren't the only people to have reverted Gages images), And last but not least a bit unrelated but I'm simply using Gage as it's the easiest thing I can spell so not trolling them or winding them up, Anyway thanks. –Davey2010Talk 18:18, 13 September 2016 (UTC)[reply]
      Someone brought up this issue at Wikipedia talk:Conflict of interest#Self-promotion_via_images. I commented that AN/I seemed to be handling the problem. Thanks. John Nagle (talk) 18:30, 13 September 2016 (UTC)[reply]
      Yes, I saw that. John, do you mean AN? This discussion? I see nothing at ANI. Coretheapple (talk) 21:50, 13 September 2016 (UTC)[reply]

      Calibrador: Proposal

      I've been watching this image dispute drama for months, and it has recently devolved into edit warring on multiple articles and outright harassment by three editors, the worst of whom was rightfully blocked. Calibrador has been legitimately and repeatedly warned not to edit war over image content, especially where he arguable has a conflict of interest. Whatever solution is settled on should attempt to accomplish the following

      1. Reduce disruption, including edit warring and pointless bickering
      2. It should not discourage Calibrador from continuing to make valuable contributions of his photographic work to Wikipedia and Commons
      3. It should minimize the likelihood of harassment

      In my opinion, the best solution that comes close to accomplishing all of these goals, and what I am proposing is, Calibrador, Winkelvi, is indefinitely limited to 1RR for any edits adding, removing, or changing any image in any article.

      I also propose: Winkelvi, Davey2010 and Stemoc are indefinitely limited to 1RR for any edit removing any image created by Calibrador.- MrX 18:12, 13 September 2016 (UTC)[reply]

      • Support. I have been watching this image-dispute saga play out over the past three months. (I personally don't get the passions over images; my own views is that the choice of image rarely makes an article much better or worse). I would like the image drama to not metastasize, and this 1RR restriction seems like the best way to do it. Neutralitytalk 18:38, 13 September 2016 (UTC)[reply]
      the choice of image rarely makes an article much better or worse - You've been around the wikiblock once or twice, so I'm sure you know that literally no issue is too minor to argue endlessly about. ―Mandruss  18:48, 13 September 2016 (UTC)[reply]
      Oh, indeed. This one wouldn't even make it to the honorable mentions section of
      WP:LAME. Neutralitytalk 18:57, 13 September 2016 (UTC)[reply
      ]
      • Support Oppose. Something has to be done or the behavior will most likely continue. I am tired of contributing to this topic when we could be deloping the pages itself instead of agreeing to disagree who's photo is the best. I like a lot of Calibrador's photos and as a photographer myself, understand the feeling that an article featuring your photo can bring you, but don't agree with the method of integrating them into the Wikipedia. I also think the name of the file is an issue, not on commons, but here. It is promoting, his business, which is against Wikipedia policy. Which should result in all of them being renamed or removed from being used for violating Wikipedia's policy, not a commons. Seeing as he has TONS of images on Wikipedia, that is unlikely to happen. Nothing will be done about it though, so this is a great solution. (I know I have said this already). Just re-iterating that in my support, I am not also supporting the filenames. I also want to state, Many people, not just four, have been uncivil regarding this topic and had it not been for User:Mandruss and I coming to some sort of system, consensus would have never been able to be reached in regards to the Donald Trump photo. Chase (talk) 18:56, 13 September 2016 (UTC) Most of what I said I still agree with, but some clarifications were made that I no longer agree with dealing with this proposal. That is why I have amended my support to oppose and now support a proposal by the OP, MelanieN, who seems to understand the problem more than most. Chase (talk) 20:53, 14 September 2016 (UTC)[reply]
      • Comment I have no problem with most of what you listed, but can you better detail what 1RR means in regards to the users you listed involved with reverting me? If I am limited to 1RR and one of those users that you listed reverts me, what does that mean to me? Calibrador (talk) 19:06, 13 September 2016 (UTC)[reply]
        • I think it means that if you replace an image in an article with one of your own, and that image has recently been added or replaced (within the past month) then that's your one revert. If the image has been in the article for a long time, then your first edit is a bold edit. If you follow
          WP:BRD, and if someone reverts your bold edit, you should discuss it on the talk page, although you could technically revert them without violating 1RR.- MrX 21:17, 13 September 2016 (UTC)[reply
          ]

      Support as it originates in an old proposal of mine. I would just clarify that my intention was for the restriction to be 1RR until consensus is determined on how to proceed. The overall idea for the restrictions I discussed is for Calibrador to continue adding their own images to articles and if any addition of an image is reverted, discussion must commence and consensus on how to proceed established. 1RR gives Calibrador a little flexibility to revert images being removed without good reason and it gives Stemoc et al a little extra flexibility to revert the addition of what may be an inappropriate image addition.
      I would also add that any tag-teaming should be treated as a collective 1RR for all the named participants. Nick (talk) 19:25, 13 September 2016 (UTC)[reply]

      • Oppose as inadequate. This only deals with edit-warring over the insertion of pictures. It does nothing to stop the disruptive behavior at the talk page. MelanieN (talk) 19:53, 13 September 2016 (UTC) P.S. I'd also like to see disclosure in his edit summaries of his COI, but he kinda-sorta said above that he kinda-sorta might start doing that. IMO it be a good idea to confirm it though, or to get an actual commitment from him to do it. --MelanieN (talk) 19:55, 13 September 2016 (UTC)[reply]
      • I'd also really prefer to see a formal requirement to disclose in every edit summary. I was fooled by the username change, and still can't think of a good-faith reason for it that's compatible with both leaving his real name in the image filenames and continuing to edit them into articles on enwiki. —
        Cryptic 20:21, 13 September 2016 (UTC)[reply
        ]
      • Oppose - Sorry but how exactly did i get added to this proposal? I'm not the problem, I was trying to be the solution but instead I'm apparently the part of the problem now? and people wonder i have no respect for people on this wiki, for the umpteenth time the 1RR idea is nonsense, it will not work, all it does is protect him, not those trying to remove his "vandalism"..This was a good idea 2 years ago, but we have moved from that..again i have NO ISSUES with him adding images to articles which previously had no images, my only issue is when he intentionally changes an article which already has an image with one carrying his byline....there was a time he would also add his name to the caption of the image, we stopped him a few years back from doing that..and people who still think he isn't using wikipedia to self promote himself are really living under a rock...--Stemoc 00:38, 14 September 2016 (UTC)[reply]
        • WP:NOTVANDALISM.- MrX 01:21, 14 September 2016 (UTC)[reply
          ]
          • You should read my comments at
            WT:COI as to what i'm saying and why there is a need to change our policy in regards to what exactly is 'vandalism' when it comes to situations like this..I spent a better part of a decade fighting cross-wiki vandalism which included mainly self promotional stuff including articles and links to websites only to be told that its OK to do so on enwiki...yeah..its quite funny.. --Stemoc 01:38, 14 September 2016 (UTC)[reply
            ]

      Support, and yes, this should include Stemoc. Jonathunder (talk) 00:46, 14 September 2016 (UTC)[reply]

      • Oppose: per MelanieN this is inadequate. A TBAN on discussions is needed. Skidmore can continue to upload to Commons. If editors want to replace an image with one by him, fine, but please cut out the disruption such as at Trump's article. Also uneasy including other editors in the restrictions. Harassment is already disallowed and can be sanctioned without any further rules being imposed here (such as Winkelvi's block, though I don't like that either). BethNaught (talk) 08:18, 14 September 2016 (UTC)[reply]
        • BethNaught, if are you opposing this because it's inadequate, then wouldn't it make sense to support it and propose an additional remedy? It might help if you could explain "TBAN on discussions". It's not clear how that would work.- MrX 12:31, 14 September 2016 (UTC)[reply]
          • BethNaught and @MelanieN: His 'vandalism' in not only limited to this wiki, he randomly uses his commons account (Gage) to overwrite other images because he wants his version to be used, this and as you can see, he used both his accounts...this was last month and then after he was questioned by a commons user, he gave vague reply that he was not socking and then later he blanked that section along with the part where an admin told him his move rights were remove for abuse..He is trying to keep his page clean so that his "customers" don't question him why his rights were removed....I don't understand why people refuse to see that he is using wikipedia to fund his own business, when did we become a repository like Gettyimages? cause if he is allowed to use commons to promote himself financially, we won;t be able to stop anyone else doing the same in the future....oh and you may find this interesting, he even reverted an image today added by the now blocked Winkelvi (on enwiki) whilst this discussion was happening and added his own version because as usual, he wants his own "version" to be used in articles even if it does not carry his byline, its either his images and his versions or none...For those who follow his contributions on commons, he does that regularly and usually without a valid reason..see his edits using the Gage account on commons and you will get a bigger picture as to why he 1RR is a bad idea..--Stemoc 02:29, 16 September 2016 (UTC)[reply]
      • Support - and I find it rather disconcerting that COI is even a consideration for a number of reasons, including the terms of licensing. Atsme📞📧 15:47, 15 September 2016 (UTC)[reply]
      • Support - his clear talk page COI in promoting photos that have his name in the title is clear, and since a mass rename is unlikely, I think this is the best way forward. jcc (tea and biscuits) 11:44, 24 September 2016 (UTC)[reply]
      • Any chance we can get an admin or experienced editor to close this? Apparently the disruption continues.- MrX 12:58, 27 September 2016 (UTC)[reply]

      Calibrador: Alternative to 1RR proposal

      • I !voted "oppose" above. I still oppose that proposal, but my rationale is now different. My concerns about his talk page behavior are satisfied (AGF) by his agreeing to my proposed limitations. My reason for opposing now is that I don't think we should use a "1RR" standard, as defined for Discretionary Sanctions, because that is too complicated and too subject to gaming. (We have all seen the arguments "you reverted me!" "no, you reverted me!") I would rather have a straightforward restriction something like this: "Calibrador may add his image to any article once. If it gets reverted, he may not re-add it without consensus." No gamesmanship, no difference based on the previous status of the article - i.e., previously no picture vs. long-standing picture vs. recently added picture - just that he is free to add it, but if it gets challenged, he can't be the one to re-add it, except per consensus. Of course it could be re-added by his fans, several of whom are present at this discussion. --MelanieN (talk) 17:03, 14 September 2016 (UTC)[reply]
      Clarification, in case it was unclear: The proposal covers all three types of articles: articles which did not previously have a photo, articles which previously had a longstanding photo, and articles where a new photo has recently been added. These are handled differently under the 1RR standard, because of what kind of action is defined as a "revert". My proposal is much more straightforward because it treats all three types of articles the same. --MelanieN (talk) 21:17, 14 September 2016 (UTC)[reply]
        • Comment @MelanieN: Your proposal mentions articles without photos, which seems counterproductive to me. Calibrador (talk) 20:59, 14 September 2016 (UTC)[reply]
          • Clarifying, biographical articles where there are no free photos of a person. Calibrador (talk) 21:23, 14 September 2016 (UTC)[reply]
        • Comment The proposal states Calibrador can add photos to any article, even ones with a photo already, but just once. Chase (talk) 21:03, 14 September 2016 (UTC)[reply]
            • I thought you agreed to not address me unless I addressed you. Calibrador (talk) 21:05, 14 September 2016 (UTC) Note the bullet demotion. Calibrador (talk) 21:09, 14 September 2016 (UTC)[reply]
          • Comment To be clear, I wasn't addressing Calibrador directly, but to clarify everyone who might read the proposal and is confused like I was when first reading it, what the proposal is actually stating. I also didn't mean to add three "***" when making my first comment, so I demoted it. Chase (talk) 21:15, 14 September 2016 (UTC)[reply]
            • 'Twas clear enough to me, Chase, but maybe Calibrador doesn't know that "addressing" is not the same as "referring to". Calibrador, I was not addressing you in the preceding sentence, but I am in this one. See the diff? I hope we can dispense with any further misunderstanding in that area. ―Mandruss  21:26, 14 September 2016 (UTC)[reply]
              • Based on their bulleting at the time of my comment, I thought that was their answer to my statement, despite it not actually answering to what I had stated. Calibrador (talk) 21:33, 14 September 2016 (UTC)[reply]
                • I suggest you let others police that agreement from now on. ―Mandruss  21:36, 14 September 2016 (UTC)[reply]
                  • Can I get an answer to my actual concern? Calibrador (talk) 21:37, 14 September 2016 (UTC)[reply]
                    • Calibrador, what is your concern? I thought you were just asking what is an "article with no photo". Are you asking why I am including this type of article in my restriction? Because it makes sense to me to have the same rule - namely, you can add a photo once but can't add it back if someone removes it - every time you add a picture to an article, whether or not it previously had one. Do you see a problem with that? --MelanieN (talk) 22:07, 14 September 2016 (UTC)[reply]
                      • Yes. If an article's subject has no free photo, and someone removes it for some reason unbeknownst to me, but should it present itself, a photo-less article is preferred? Makes no sense. Calibrador (talk) 22:12, 14 September 2016 (UTC)[reply]
                        • As an example. Last year, Davey2010 reverted my addition of photos to a whole host of articles, including ones that previously had no photo. He was warned by an admin for doing that, if I recall correctly. Calibrador (talk) 22:15, 14 September 2016 (UTC)[reply]
                          • I'm certainly open to input on this. Let's see what others say - or if this proposal is even going anywhere. --MelanieN (talk) 01:59, 15 September 2016 (UTC)[reply]
                            • I think your proposal as written looks a lot like
                              WP:DR cover that adequately? Anything I'm missing here? Wouldn't it be weird if the product of all this is: Follow Existing Process? ―Mandruss  03:18, 15 September 2016 (UTC)[reply
                              ]
                          • Calibrador - Not arguing but do you have any diffs of me being warned by any admin?, I honestly don't remember that and I'm intrigued now, I probably did have some sort of vendetta back then however since the AN3 report I don't think I've reverted you since. –Davey2010Talk 13:15, 15 September 2016 (UTC)[reply]
      • Support: This would drastically improve the tension and conflicts that have been created by Calibrador and by default his opposition. I personally think he just needs to be banned all together especially with the evidence that was presented in the below subsection by MelanieN and the indirect answers he has given, but there seems to be little support for that so far. Chase (talk) 20:48, 14 September 2016 (UTC)[reply]
      • Support: I also agree with MelanieN’s proposal. Should a rare exception happen then of course Calibrador should flag it up, however it should be the exception and done before any reverts. NJA (t/c) 09:00, 24 September 2016 (UTC)[reply]

      Calibrador: Propose TBANs

      Proposal withdrawn by author following unanimous opposition

      I propose TBAN for Stemoc vis-a-vis Calibrador and images. His comment above clearly demonstrates the Winkelvi-like righteous crusading battleground mentality - and the same inability to accept constructive criticism from the community - and that is anything but part of the solution here. While I'm at it, I'll propose the same for Winkelvi. ―Mandruss  00:52, 14 September 2016 (UTC)[reply]

      95% of the work i do on enwiki is to find and add free images from flickr and other sites to articles on enwiki, I do not get involved in petty fights related to Gage unless it directly involves an image he has changed on my watchlist..again I'm not an issue here, I do not call my self a wikipedia anymore, I'm more of a wikimedian and a TBAN on me is pretty much forcing me to stop my work on commons. I gain nothing from this, neither monetary nor in fame and yet somehow you assume that Winkelvi and I are the same? I'm sorry but you are wrong, stop trying to be self righteous and try to see the issue before making your own prejudicial assumption...You haven't been the one looking for the solution to this problem for 4 years now, I have so before you try to judge somebody who has been frustrated with the fact that admins on enwiki for the last 4 years have turned their blind eye to the situation even when reported to this board and
      WP:ANI...You really need to read up on what a battleground approach is, I follow the rules to find justice..My account on enwiki doesn't just have one purpose (unlike Calibrador who uses it only to force his images into articles) so if you refuse to see the issue here, Its not really my fault now is it?..I'm not going to come back here in another 14 months seeking justice, If the project actually stood for what it claims it does, people like him would no longer be allowed to contribute to the project --Stemoc 01:16, 14 September 2016 (UTC)[reply
      ]
      forcing me to stop my work on commons - To clarify, I'm speaking of situations involving Calibrador and images, not one or the other. Unless all your work on Commons involves Skidmore images, this does not stop your work there. people like him would no longer be allowed to contribute to the project - I rest my case. If you feel that strongly - at an emotional level - that Calibrador should be indeffed, when the community disagrees, you are the last person who should be interacting with him, and your doing so will only add fuel to a fire that the community is trying hard to put out. You need to step away. -―Mandruss  01:20, 14 September 2016 (UTC)[reply]
      You do realise my work on commons entails adding images of politicians and celebrities too right? Infact I generally deal with those sections cause I feel i'm experienced in that section and Calibrador uploads mainly US politicians and celebrity images so yes, lines will definitely be crossed, intentionally or not even though the last time i spoke to Gage on commons was probably years ago and the last time i was involved in anything related to Gage was when i caught him abusing 2 of his rights on commons and duly reported on one of those abuses last month, you should probably read that section first where 5 commons admins agreed on his rights to be removed for abuse..again, I have no issue with him, he may have one with me because apparently I'm a hindrance in his 'work'..lol... and regarding the 2nd issue, I'm sorry if you do not under stand the self promotion policy on wikipedia, it actually applies to all wikis and not just this one and if we are going to block users who use the project to promote themselves then I do not see how in the future this will not include 'all forms of promotion' ..I don't want him to be indeffed, I never said that, I just want him to face the consequences of his actions as he seems to be in the habit of deflecting and passing the blame onto others which is actually a good trait to have if one wishes to be a politician...If I was from Arizona, I'd vote for him for Governor ;)--Stemoc 02:57, 14 September 2016 (UTC)[reply]
      Clarification: I believe that nothing we do here at enwiki would apply to Commons. --MelanieN (talk) 09:17, 14 September 2016 (UTC)[reply]
      • Oppose: This seems mighty retaliatory. I've dealt with Gage as well and it is so painfully obvious that they are only here to promote themselves and their photography work. This proposal is just deflecting the actual issue onto someone else. The problem here is Gage and his self-promotional behavior regarding his images. --Majora (talk) 03:08, 14 September 2016 (UTC)[reply]
      • Comment - Some feel that opposition to battleground mentality represents support for, or defense of, the target of that battleground mentality. That is a
        false binary, folks. Calibrador needs to be dealt with, but it does not serve the project to deal with him that way. If you disagree, if you feel that the problem can't be managed without the flamethrower services of Stemoc and Winkelvi, please Oppose. But don't twist my intent. ―Mandruss  04:23, 14 September 2016 (UTC)[reply
        ]
      I haven't said anything thus far but you keep comparing Winkelvi to me, I assume you have an issue with Winkelvi, so you are personalizing this attack on me now? The only person with a battleground mentality in his thread apart from the person in question is you..You are deflecting from the main issue, You also seem to be coming with assumptions pointing out things I did not say and trying to make it seem like I'm the fuel to Calibrador's fire..I'm not mate, I'm the guy with the fireman's uniform trying to put it out..I just noticed your comments on MajoraWP's page, that is a really low move mate..I'm sorry to say this but you are making it personal, I'd give you the same advice I would give others before you to drop the stick. Its bad enough we have one person trying to deflect from the issue, now we have another doing the same. This is why this issue has not been solved for over 4 years now because people who have no idea about the problem try to insert themselves into the situation just so that they can derail it, which mate, is what you are doing right now.....I have provided facts and proof of abuse all throughout this discussion, the only thing you have provided is unrelenting attacks on me and your somewhat battleground mentality..Winkelvi does have a battleground mentality, no doubt, but son, you do too..--Stemoc 06:08, 14 September 2016 (UTC)[reply]
      No point in further arguing, but my proposal stands until defeated. ―Mandruss  07:56, 14 September 2016 (UTC)[reply]
      • Oppose: we need to be dealing with the actual problem first. BethNaught (talk) 08:06, 14 September 2016 (UTC)[reply]
      • Oppose Let's quit trying to change the subject here. The subject is
        WP:COI, i.e., Gage Skidmore using Wikipedia to advance his own career. Last time I looked, this kind of promotionalism was "strongly discouraged" at Wikipedia. Are we going to simply give Skidmore a green light, go ahead, promote yourself all you want? And anyone who tries to protect Wikipedia will get ordered to stop? --MelanieN (talk) 08:47, 14 September 2016 (UTC)[reply
        ]
        • I'm sorry MelanieN, but I'm really struggling to understand your point of view. Several people in the discussions above, including myself, have rejected the idea that there is a COI problem of a magnitude that would be sanctionable. To claim that someone is using Wikipedia to advance their career requires better evidence than file names and making multiple comments on talk pages. Edit warring can be dealt with by limiting reverts. Calibrador has already agreed to limit talk page comments where his images are the subject of a dispute. I think it would help us if you could explain how applying more sanctions would help Wikipedia, or not applying them would hurt Wikipedia. In practical terms.- MrX 12:21, 14 September 2016 (UTC)[reply]
          • He has voluntarily agreed to my proposed sanctions in the section below. His excessive promotion at talk pages was the area of concern to me since that was clearly COI editing, but with his voluntary agreement I am satisfied on that point. He certainly IS using his Commons pictures to advance his career - if you need evidence, consider this from an off-wiki source: "Creative Commons in my mind is a vehicle for my photos to be easily disseminated, and at first was a way to simply get my name out there."[41] But as long as he does not excessively push for his own photos, it appears that Wikipedia is OK with using them. I still oppose this proposal because I think it is aimed at the wrong people. --MelanieN (talk) 16:50, 14 September 2016 (UTC)[reply]
            • Thank you for that very clear evidence MelanieN. I now agree that Calibrador has used the project for self-promotion. Based on that, I'm warming up to the idea of a full ban on him being able to add his photos to any article, unless he has a good explanation for why that should not be the case.- MrX 17:59, 14 September 2016 (UTC)[reply]
              • I was referring to "Creative Commons" not Wikimedia Commons to be clear, and was referring to my Flickr, where most people obtain my photos and have over 48,000 photos under the Creative Commons license listed. Calibrador (talk) 18:14, 14 September 2016 (UTC)[reply]
                • I approach my involvement with Wikipedia as simply wanting to be helpful in providing high quality images to freely be used to illustrate article subjects. I point you to this interview with David Shankbone conducted by Wikimedia Foundation, (Shankbone also puts his name in the title of images, which are credited at the end of the video.) My involvement with Wikipedia is not promotional, I don't link to my website or anything like that in the file descriptions, my intention is to provide charitable photos of quality to be used freely. Here is the link to the interview with Shankbone by Wikimedia: https://www.youtube.com/watch?v=byqcaqVuJgw

      Calibrador: Talk page restrictions

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


      When one of Calibrador/Skidmore's pictures is challenged or removed, he sometimes (not always) becomes very aggressive at the talk page trying to restore it. Because of his

      Conflict of Interest, this behavior is far more problematic than if he was simply arguing about a wording or an inclusion of text; it is an example of the kind of COI editing which is "strongly discouraged" at Wikipedia. Based on his documented activities at multiple articles, I propose the following where one of his own photos is involved: limit his discussion at the talk page to a single !vote, including commentary and disclosure, per discussion section or subsection; a ban on replying to or arguing with other discussants unless they directly addressed him; and a ban on attempting to assess or claim consensus, unless it is unanimous. --MelanieN (talk) 09:11, 14 September 2016 (UTC)[reply
      ]

      P.S. If he would voluntarily agree to accept these restrictions, I would AGF, take his word, and withdraw this as a formal proposal. --MelanieN (talk) 09:21, 14 September 2016 (UTC)[reply]
      I agree to those restrictions. Calibrador (talk) 09:37, 14 September 2016 (UTC)[reply]
      Thank you. I withdraw this proposal. I do believe that you were unaware of essays like
      WP:BLUDGEON and did not realize that this kind of behavior could be seen as offensive. --MelanieN (talk) 10:03, 14 September 2016 (UTC)[reply
      ]
      @MelanieN: My question is how does this affect the situation over at Talk:Donald Trump? Since Calibrador was directly involved? Chase (talk) 19:00, 14 September 2016 (UTC)[reply]
      This agreement is not retroactive. Whatever he said there still stands. I assume he will abide by these restrictions from now on. --MelanieN (talk) 19:47, 14 September 2016 (UTC)[reply]
      Okay thanks. Chase (talk) 20:26, 14 September 2016 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      Recent massive deletion of content under the claim that it was unparaphrased copy of copyrighted text

      Note: Please move this discussion to

      talk) 20:17, 30 September 2016 (UTC)[reply
      ]


      A few hours ago
      Diannaa deleted large parts of the additions that I made between 28 and 29 september to the article religion in China, on which I have been working for months, arguing that they were unparaphrased copy of copyrighted text from the source author (Didier). All of this without discussing and without leaving me the time to enhance the text as I replied to her that I would have done. Indeed, I think that the indicted text was paraphrased enough to stay.

      I ask administrators to restore the content and verify that it is not a copycat of the sourced text.--

      talk) 18:39, 30 September 2016 (UTC)[reply
      ]

      A mere rewording frequently is not enough to make copied text "not a copyright infringement", see
      WP:CLOP. Jo-Jo Eumerus (talk, contributions) 18:53, 30 September 2016 (UTC)[reply
      ]
      In the policy I read that "limited close paraphrasing is appropriate within reason, as is quoting (with or without quotation marks), so long as the material is clearly attributed in the text...". In my text, all the indicted parts, closely paraphrased and not excessively long, were appropriately attributed to Didier (2009), in total accordance with the policy.--
      talk) 19:07, 30 September 2016 (UTC)[reply
      ]
      I had the intention to continue to work on the history sections of the article today, obviously paraphrasing the content of sources as I have always done in these years of contribution to Wikipedia, but after Diannaa's deletions the text's meaning is disrupted and it would require a lot further work to recover.--
      talk) 19:34, 30 September 2016 (UTC)[reply
      ]
      You are more than free to rework the content in a text editor until it is no longer a copyright violation. No admin is going to give you blessing to keep a copyvio on an article simply because it's a work in progress. But this really is no big deal and you should see that. Work on it offline, and once the content is acceptable, return it to the page. Diannaa's revert doesn't prevent you from doing that. Someguy1221 (talk) 20:38, 30 September 2016 (UTC)[reply]
      I opened this discussion precisely because I don't think the additions were copyvio, as I have said above. Anyway, I do not have the text of the article as it was as of 29 September 2016‎, h 23:54.--
      talk) 20:52, 30 September 2016 (UTC)[reply
      ]
      I do have the text of the article as it was, and just by dropping bits of your additions into Google (try "immanent in the universe, that responded positively to humaneness and rightness") can see that this was a cut-and-paste. Diannaa is correct here. ‑ 
      Iridescent 21:00, 30 September 2016 (UTC)[reply
      ]
      Most of the parts that are close paraphrases (technically, I did not "cut-and-paste") of the original text are properly attributed as per WP:CLOP. If that part is not introduced by "Didier (2009) says" or something like that, it is because I missed it.--
      talk) 21:20, 30 September 2016 (UTC)[reply
      ]
      You may not, at any point, have copyright violations on any page on Wikipedia. Diannaa is correct here, and it needs to stay deleted. As you were told above, you're welcome to work on it in an offline text editor if you want to start out with the copyrighted material and paraphrase from there, but you may not do it on Wikipedia. However, the paraphrasing can't just be tweaking a few words. The text must either be a properly attributed, short direct quote, or else be written and paraphrased entirely in your own words. Sorry, but this really isn't negotiable. Seraphimblade Talk to me 21:26, 30 September 2016 (UTC)[reply]
      Then send at my email address the text of the entire article as it was at 23:54, 29 September 2016. All of this is quite ironic, as other users have often complained that I reword too much the text of the sources.--
      talk) 21:34, 30 September 2016 (UTC)[reply
      ]

      Looks like part of the misunderstanding might come from Aethelwolf's quote from

      WP:CLOP: "with or without quotation marks". As written, it could easily be misunderstood as "quotation marks are optional". Though I may be overlooking something, I went ahead and removed those words from the lead of that essay and opened a discussion on the talk page. That doesn't excuse copyright violations and isn't an argument to restore material, but I can appreciate someone being frustrated by having content removed after reading that. — Rhododendrites talk \\ 13:29, 1 October 2016 (UTC)[reply
      ]

      @
      talk) 10:46, 2 October 2016 (UTC)[reply
      ]
      @
      Iridescent: (sorry for the notification for those of you still watching the thread). — Rhododendrites talk \\ 13:19, 2 October 2016 (UTC)[reply
      ]
      Email has now been sent. — Diannaa 🍁 (talk) 11:58, 4 October 2016 (UTC)[reply]

      The trouble is

      WP:CLOP is only an essay, and is probably wildly over conservative. We could really do with something more robust and nearer reality. All the best: Rich Farmbrough, 12:49, 8 October 2016 (UTC).[reply
      ]

      Strange editor

      I'm posting here because I have no clue where else to go. There's a user, Savagecoverman, who creates articles on racehorses and rodeo topics. All their subjects are notable, being either Grade 1 winners or Hall of Famers. That's not the issue; the issue is they cannot write. Just take a look at Midnight (horse). This is a very notable saddle bronc that was infamous in the 1930s for throwing cowboys, yet I'm not sure the article should exist in it's current form. It's like it was written by a ten-year-old who is more interested in their own opinion than the facts. I think it would be easier to blow it up and start over than it would to fix it. This editor does not respond to talk page queries, I've tried that route and got nowhere. Can a person be kept from creating pages, but not kept from contributing otherwise? White Arabian Filly Neigh 20:50, 3 October 2016 (UTC)[reply]

      Please don't
      bite the newbie. They've been here for barely 3 months and have racked up just over 80 edits. The language needs a lot of work but that sort of thing comes with experience. If they were actively disruptive with lots of poorly written articles, then that would be another thing, but I don't see anything that warrants action at this point. Blackmane (talk) 21:07, 3 October 2016 (UTC)[reply
      ]
      I disagree. I'd personally say just merge or be bold and revert... Montanabw(talk) 21:08, 3 October 2016 (UTC)[reply]
      • It's really not optional to notify people when they've been brought up here. I've taken care of that, and given the editor some advice. [42] Seraphimblade Talk to me 21:22, 3 October 2016 (UTC)[reply]
      E/C I agree with Montanabw. We need to retain editors and working on the article in a collegiate manner will be a much friendlier way of doing that. @WAF, if you discuss an editor here, you must notify that editor. DrChrissy (talk) 21:25, 3 October 2016 (UTC)[reply]
      Editor has been notified by Seraphimblade. They are cutting a pretty wide swath here, I can see why there is frustration, their stuff reads like some kid's school project. I have also alerted WikiProject horse racing... I think we just have to trot around after them for a bit and see if they get clue or not... if they do, we have a new editor, if they don't we will be back here for behavior. Montanabw(talk) 21:30, 3 October 2016 (UTC)[reply]
      Yes, I agree there are some issues here. The OP's use of apostrophes would certainly benefit from a little gentle advice! Plank, eye? MPS1992 (talk) 21:32, 3 October 2016 (UTC)[reply]
      No, this situation is beyond typos. This is a new editor, and needs a LOT of help, and the usual people who help with this stuff are all kind of busy IRL at the moment... but at the rate this editor is working, they can create a mess, so they DO need some mentoring ... see e.g. Chicken on a Chain. Montanabw(talk) 21:55, 3 October 2016 (UTC)[reply]
      Hmmmmm...this problem may be greater than I originally thought. I have been copy-editing Midnight (horse). Perhaps the greatest problem is the lack of in-line referencing. This makes it difficult for other editors to verify and/or clarify content. I have also looked at their contributions and the problem is more widespread than I thought previously. Is there any way we could stop the editor creating more problems until they have shown competence in writing in-line references? DrChrissy (talk) 22:30, 3 October 2016 (UTC)[reply]
      The editor knows talk pages exist however their only edit to one seems to be to alter another editor's comment [43] - not a good sign. I am afraid if they continue as they have without communicating a
      WP:DE block may be the only way to get their attention. It is not possible to mentor or help someone who does not communicate. JbhTalk 22:52, 3 October 2016 (UTC)[reply
      ]
      • WP:COMMUNICATE but they haven't done anything that would force them too yet. Still, it is worth while to try. I don't see anything worth blocking over. Dennis Brown - 23:11, 3 October 2016 (UTC)[reply
        ]
      I think this account is their sock or prior account. [44] Compare the writing and use of words, like "carier" for career. Same lack of talk communication, too. This is what had been bugging me ever since I saw the comment above about how this guy has only been registered since July. I had distinctly remembered interacting with somebody similar back in May, and posting on their talk page explaining what was wrong with their edits. I went through the history of Tizway and bingo. White Arabian Filly Neigh 21:55, 5 October 2016 (UTC)[reply]
      That previous account isn't blocked or sanctioned, so even if that's so, they're really not doing anything wrong by dropping it and creating a new one. Could be something as simple as forgetting the password and not having a valid email to recover it. Seraphimblade Talk to me 06:04, 7 October 2016 (UTC)[reply]
      The latest edit at Midnight (horse) by this editor is effectively a reversion to a previous version without discussion and an addition of unsourced material. I really hate to say this, but it might be a competence issue. Whatever, the editor is creating work for other editors. DrChrissy (talk) 19:46, 8 October 2016 (UTC)[reply]
      Hi all, I know I'm new to editing in Wikipedia. But I'm technical writer and I have a long history with rodeo, especially bull riding. I came in early this week with the intent to start editing and writing about bull riding. White Arabian Filly points out the topic Chicken on a Chain. Not only does it have a citation problem, it leaves out important information or explains it in an unclear way. For example in talking about the PBR. And it still needs work. Also, I point out the topic Skoals Pacific Bell, which is half the topic the writer rewording what is in the ProRodeo Hall of Fame topic about the bull. The other half is good info, the writer is knowledgeable about bulls, you just don't now where from. The title part Skoals does match the Hall of Fame, which has Skoal Pacific Bell. And it needs lots of cleanup. The topic says it lacks inline citations. There aren't more. Just because the bull is notable does not mean there's enough verified content for a topic. There are more topics...Dawnleelynn (talk) 03:38, 10 October 2016 (UTC)[reply]

      Vandalism by user 46.238.25.84 on several articles related nomadic people

      Hello,

      I want to report vandalism by the user 46.238.25.84 on several articles about nomadic people of Euro-Asia as follows:

      1. Article "Xionites" - the user has deleted sourced information without any explanation, only a fake excuse "WP:SCOPE" : [45]

      2. Article "KIDARITES" - the user 46.238.25.84 deleted several times content supported by accademic sources. No real explanation was given, only some vague stupid, and obviously fake "Back to neutral content" : [46]

      3. Article "Sabir people' - source falsification and pushing wrong ideas [47]

      4. Article "Bulgar language" - deletion of sourced content, the most famous paper on the subject (published by Harvard University) is shorten to 1 sentence; paper published by Gothenburg University ( and supporting the information from Harvard paper) is also shorten to 1 sentence; the sentence where Pritsak is sited is fake - this is an outrage, Pritsak ( Harvard University) never uses the term Oghur. Once again source falsification. [48]

      5. Article "Massagetae" : Source falsification [49]

      Thank you --216.75.21.32 (talk) 22:42, 4 October 2016 (UTC)[reply]

      • First, vandalism should be reported at
        WP:AIV, not here. Second, he isn't vandalizing. He's actually engaging with Doug Weller, an Arb, as we speak, and his edits seem to be in good faith. That doesn't mean they are correct, just that he isn't "vandalizing", which means to destroy with ill intent. Dennis Brown - 23:29, 4 October 2016 (UTC)[reply
        ]

      And what good faith is there to delete 8-10 books from the article Kidarites? What good faith is there to obviously falsify the sources in the article Massagetae? Is there any good faith to delete information from the article Xionites? For me this guy is obviously playing some childish games that are not innocent - I can understand when someone doesn't have good knowledge on a subject to do a mistake, but in this case, for me this is an intentional vandalism. --216.75.21.32 (talk) 00:24, 5 October 2016 (UTC)[reply]

      • Why is deleting content necessarily bad? Articles are naturally built by adding and removing information over time. Were the edits made to Massagetae obviously false? If it's obvious, prove it, and then it should be obvious to us as well. It sounds like you simply don't like the edits he has made, and instead of resolving the issue by discussing it with him, you ran here and want someone to simply ban him. That's not going to happen unless you make a much stronger case, though I'd strongly suggest you just try to talk to him first. Someguy1221 (talk) 00:30, 5 October 2016 (UTC)[reply]

      ok let's see this edit on Massagetae [50] where he/she has replaced the word Getae with the word Jats( meaning Jat people) at the beggining of the second paragraph. Sources 11-14 clearly states that Massagetae are believed to be related to Getae, not to Jat people. Only on source 13 we have "getae(Jats)" which clearly means that both words have similar prononciation, nothing more. The source 13 doesn't state that Jats are the same people as Massagetae. The connection is much more subtle, Massagetae are believed to be connected to Yuezhi that 7 centuries later dispersed into north India. This is clearly explained on the article, Wario-Man who never editted the article before that has observed it and corrected it with very clear explanation : "Source falsification" - and that is also my opinion. --216.75.21.32 (talk) 01:01, 5 October 2016 (UTC)[reply]

      • And that is why it isn't "vandalism". If he replaced with "YoU R tHe suX!", that would be vandalism. You simply have a difference of opinion on the content, and you might very well be right, I don't know, but admin don't decide content, that is up to the editors. We only deal with obvious vandalism and acts in bad faith. This doesn't look like that. Being wrong isn't bad faith, and I have no idea if he is right or wrong. Dennis Brown - 01:03, 5 October 2016 (UTC)[reply]

      ok - I will be honest - I believe that the guy behind this ip(46.238.25.84) is someone else. Of course you don't have idea who is right/wrong because these articles require some knowledge. They are not nuclear physics, but everyone needs at least a couple of hours to study them. I think the guy 46.238.25.84 have very good knowledge on these topics and he intensionally are twisting them. In my opinion he is the same guy as the ip=88.203.200.74 and the ip=212.5.158.21 and the ip=212.5.158.18 This is obvious from his edits on the article Kidarites [51]. --216.75.21.32 (talk) 01:31, 5 October 2016 (UTC)[reply]

      Yes, those three IPs obviously belong to the same person. And it looks like he got into a bad edit war a couple weeks ago. But I'm still not seeing anything right now that demands an administrator's attention. You are assuming a lot about this guy's motives, but so far you've shown at most he's mistaken about something. Look, this guy actually responds to people who message him. Try to talk to him about it. Someguy1221 (talk) 01:36, 5 October 2016 (UTC)[reply]

      I have encountered him on other Wikipedia. Talking with him is useless, if he is the same guy, and I am almost 100% sure of that. Basically he believes that all nomadic people are of Turkic origin, especially if these nomads are some warriors. That's why he is trying to delete information from the article Kidarites, for the same reason he has deleted the information about cranial deformation among Xionites - this may link them to the western Huns, and he firmly believes that western Huns were Turks. Which is far from proven. Anyway, he spents 24 hours per day on 3 WP's, 7 days per week, which makes me think that he gets money for these edits. Of course, I can't prove this, but clearly I can trace the same edits on 2 other WP's in addition to the English Wikipedia. --216.75.21.32 (talk) 02:12, 5 October 2016 (UTC)[reply]

      This seems to be a losing battle for the OP; and I'm wondering if you're someone else as well, especially considering that your very first edit just happens to be opening an AN thread.
      Are we in Australia again? Erpert blah, blah, blah... 02:55, 5 October 2016 (UTC)[reply
      ]

      If you are in Australia I don't know, I am not there. What I know is that I do not delete content from WP articles without a valid reason. Deletion of 3 books from an article and shrinking the most important paper (Harvard) from 1 paragraph to 1 sentence, as this edit here [52], can significantly change the entire meaning of the article. Which is not going to happen. --216.75.21.32 (talk) 18:47, 5 October 2016 (UTC)[reply]

      Okay, you missed that one. But seriously, everyone has already explained to you that the activity from the IP whom you're reporting isn't vandalism, so you're pretty much
      beating a dead horse here. Erpert blah, blah, blah... 19:40, 5 October 2016 (UTC)[reply
      ]
      If it's true that this IP is someone who's POV was rejected from the Bulgarian Wikipedia, that's something to consider, but I don't see significant contributions to other languages by this user under any of his IP addresses. Someguy1221 (talk) 20:58, 5 October 2016 (UTC)[reply]

      well, I am against suppressing anyone's opinion here on WP, it is against the basic principles of WP as an open project. I don't want him really banned, what irritates me is deletion of content. I don't mind if he/she writes seperate paragraph/s to express his point of view on any of these articles(with proper citations of books of course) but he shouldn't delete/modify contributions of other editors without valid reasons. May be some simle warning from an administrator will suffice for the time being. --216.75.21.32 (talk) 00:43, 6 October 2016 (UTC)[reply]

      Many of these articles actually need attention from professionals.--216.75.21.32 (talk) 00:46, 6 October 2016 (UTC)[reply]
      As is clearly stated on the homepage, Wikipedia is "the free encyclopedia that anyone can edit". What about that is hard to understand? Erpert blah, blah, blah... 21:24, 8 October 2016 (UTC)[reply]

      User:98.167.194.3

      98.167.194.3 (talk · contribs) edit summaries (when they do them) sound crazed / belligerent. 69.58.42.90 (talk) 00:37, 6 October 2016 (UTC)[reply]

      I left a note on the IP's talk page. עוד מישהו Od Mishehu 05:03, 6 October 2016 (UTC)[reply]
      Thank you. 69.58.42.90 (talk) 19:52, 7 October 2016 (UTC)[reply]

      WP:NORN

      Could probably use a few more folks watching this board. Looks like the last five threads have so far had no outside input with the earliest posted 19SEP.

      TimothyJosephWood 20:25, 6 October 2016 (UTC)[reply
      ]

      Intervention, and possible block, for VarunFEB2003

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


      I have been assuming good faith for a good long while now, but events of the last 36 hours have made me think that VarunFEB2003 might need at best a mentor/handler, and at worst a temporary block from editing Wikipedia.

      Varun, like most editors I presume, started off with good intentions, but has been told off for one thing or another seemingly every day/week since the beginning of August. I started to list the worst of the admonishing but honestly it's probably just faster to look through their archives. However, in brief:

      • AFC
        reviews - insufficient experienced, asked twice to leave the project (both requests accepted)
      • GOCE
        - asked to leave the project (accepted)
      • Deletion stuff (
        AFD
        ) - questioned several times about their actions
      • BITING
        : at least four discussions about their tone and/or actions.

      It seems like every time something comes up, they say "ok I'll fix it" and then they move on to something else. There are a few editors I have seen multiple times commenting on their actions, and I'm sure they're just as tired as I am to be cleaning up after Varun all the time. However, I'm drawing a line in the sand after what's happened on their talk in the last 36 hours, namely performing tasks they have repeatedly said they would stop doing, and uploading copyright material and then blatantly lying about it.

      It's becoming clear to me that Varun is very excited about Wikipedia but very incapable of dealing with it, either due to an

      CIR issues, or a combination of both. I don't know what needs to be done, but something has to be done about it. My first thought was to get them a mentor, someone to watch over what they do any provide assistance, but it's becoming clear (based on the multiple people who are watching their contributions and commenting on their talk) that anything said to them goes in one ear and right out the other. A 3-month block from editing Wikipedia may help them step back and evaluate what it really is they want to be doing here. Primefac (talk) 00:37, 7 October 2016 (UTC)[reply
      ]

      • I warned him about this roughly 2.5 weeks ago. Looks like he didn't heed the warning, or follow my suggestion and continued to dive in things he's inexperienced in.—cyberpowerChat:Offline 00:54, 7 October 2016 (UTC)[reply]
        Two weeks ago, one week ago, a month ago... it's just a carousel of suggestions and no clear improvement. Primefac (talk) 01:09, 7 October 2016 (UTC)[reply]
      • The copyright thing is very odd. A topic ban from image uploading and/or deletion could help here. ThePlatypusofDoom (talk) 00:52, 7 October 2016 (UTC)[reply]

      Proposal

      I hate to be so blunt, but this a

      WP:CIR
      issues, which may be appealed to the community in one year, and every 6 months after that if needed.

      • Support as proposer. It isn't personal, but it is necessary. Dennis Brown - 01:32, 7 October 2016 (UTC)[reply]
      • Support as someone who has had to intervene on behalf of other editors when VarunFEB2003 failed to have the basic competence required to either read or understand clear instructions – in this case, how to copy edit. I tried to be nice and give helpful advice, as have many, many editors. VarunFEB2003 has repeatedly failed to follow that advice and has caused problems in many areas of the English Wikipedia. – Jonesey95 (talk) 02:41, 7 October 2016 (UTC)[reply]
      • Comment I'm also one of the many editors who has been, through necessity, 'keeping half an eye' on Varun, and intervening when he goes too far. I hate situations like this, because I have little doubt that Varun wants to be a positive contributor. The problem is, it's almost as though he has read some imaginary "How to become an admin in 6 months with minimum effort" guide. He attempts to mimic the actions of those he sees as "successful", but due to inexperience and language issues he misses the nuances of complex tasks and ends up making a mess which others need to clean up, and adversely impacting both the experienced editors who clean up and inexperienced ones who may be "bitten" or take his incorrect actions/advice as coming from the 'authority' position he adopts. Because he lacks the skills himself he copies others - his user page text lifted from another page, inappropriately imo since the text describes experience which cannot be the same - he copies and pastes scripts written by others, sticks a tag on them saying he is the author, then tries to promote them as his own work. These things are not, in themselves, direct breaches of policy, but they are not the "done" thing, and demonstrate over eagerness combined with lack of ability. The worst disruption is the repeated incompetence in 'meta' areas, and the inability to restrain himself from this after promising to do so. More than anything the problem is the sheer time involved in "nannying" Varun - he has, in effect, half a dozen "mentors", all of whom he pays lip-service to, but ultimately ignores.

        Varun is, I think, young, and 12 months is an eternity when you are young. I think a shorter appeal period would be in order, provided Varun could put together a plan for how he would address these issues when unblocked, with a very short leash in that case because of the inability he has shown to stick to promises regarding changing his approach. I'd hate for us to lose someone with potential for ever, but I think taking no action now would make that more likely, not less, as he is only likely to alienate more and more editors if unchecked. -- Begoon 03:07, 7 October 2016 (UTC)[reply]

      • Partial support I agree with Begoon's comment that 12mo is probably a bit long (especially for a first block); I was thinking somewhere in the 3-6mo range, but I suppose it all depends on how Varun responds to this discussion. Primefac (talk) 03:28, 7 October 2016 (UTC)[reply]
      • Just to clarify, I agree with the block being indefinite, since all that means is that it will not expire with the issues unaddressed. I think a shorter time period for appeal would be preferable, with unblock on a short leash once Varun can agree a plan for a trouble free restart. -- Begoon 03:55, 7 October 2016 (UTC)[reply]
      Good point. My above comment is still valid (lack of a preposition... whoops), but I'll amend/clarify here that it's the appeal that is probably too long as proposed. Primefac (talk) 04:13, 7 October 2016 (UTC)[reply]
      • @Primefac, Cyberpower678, ThePlatypusofDoom, Dennis Brown, Jonesey95, and Begoon: Hello to all, this is the thing I had feared for a long time. I agree that my history has been disruptive and caused a lot of work for the other community members. I have this proposal - I wish to contribute to the encyclopedia and give to the community whatever I can. I propose that I be blocked for a period of 1 week after which I will start again from a clean slate (with this account only) and not contribute in the following areas till the time the community feels my disruptivity has dies -
      1. My userspace
      2. NPP, AfC, AfD, GOCE and all other maintenance tasks
      3. Uploading images that can be controversial (includes all images that I have not created myself from scratch)
      4. Administrative Areas, other areas where my edits are not required and/or are not useful (includes "meta" areas)
      My block will teach me to take thing (which I currently didn't more seriously). I will not cause any any disruption to the encyclopedia, and I pledge this in front of the whole Administrators Board. Please I really want to contribute and for my own and community's good I request this self requested block to implemented from today (for a period of a week) and this case be closed as soon as possible. Thank you all. VarunFEB2003 04:34, 7 October 2016 (UTC)[reply]
      Thanks for engaging with us here. I would prefer to see VarunFEB2003 state the specific areas in which he will edit, with everything else off-limits, sort of the opposite of a topic ban. That way there is less gray area. – Jonesey95 (talk) 04:41, 7 October 2016 (UTC)[reply]
      Varun, why do you say "(with this account only)"? Have you been using other accounts? -- Begoon 04:49, 7 October 2016 (UTC)[reply]
      No Begoon it was a reply to this line of yours - plan for a trouble free restart which I understood as a clean new restart (with a new account).
      I shall continue to work on translation, encyclopedic content and as a feedbacker (hope that's a word) for the new things coming up (described at Village Pump Technical) VarunFEB2003 04:53, 7 October 2016 (UTC)[reply]
      @Begoon and Jonesey95: Forgot to ping. VarunFEB2003 04:55, 7 October 2016 (UTC)[reply]
      Ah, then you misunderstood me - I simply meant recommencing editing after an agreed unblock. There was no "clean slate", or fresh account under discussion, merely the way an agreement to unblock you might work. (there's no need to ping me to a discussion I am active in) -- Begoon 05:02, 7 October 2016 (UTC)[reply]
      Oh okay sorry for misunderstanding you. VarunFEB2003 05:05, 7 October 2016 (UTC)[reply]
      • See Wikipedia:Help Desk#DYK. Given the disruption and the drain on user resources, support an immediate indef block, with an option to appeal anytime. Administrators have always been reluctant to impose CIR blocks in cases like these. What I’d like to see is an unequivocal close showing community support for an administrator to impose escalated blocks the next time there is even a whiff of disruption from this user. - NQ (talk) 06:37, 7 October 2016 (UTC) struck, on second thought. 07:36, 7 October 2016 (UTC)[reply]
      I appeal for a last warning please. VarunFEB2003 06:51, 7 October 2016 (UTC)[reply]
      • Support block: A real shame to do this, but I agree with NQ - a block should be applied now but with the option to be immediately appealed. Varun can propose their self-defined restrictions in an ublock request. A lot of good faith has been expended here, and although I believe Varun has always acted with the project's interests at heart we've asked them many times to put the brakes on to no avail. I think its time to put the brakes on for them -- samtar talk or stalk 07:22, 7 October 2016 (UTC)[reply]
      • I confirm my support for an indefinite block at this time. I would like to see the option available for Varun to appeal after the week he has suggested, with unblock strictly conditional on Varun convincing an admin he has a plan to resume editing without disruption. As mentioned, the leash should be short after any unblock, and the block reimposed at the first sign of further disruption. -- Begoon 07:23, 7 October 2016 (UTC)[reply]
      • Oppose indefinite block. (On mobile, let me expand later.)
        Pocketed 08:07, 7 October 2016 (UTC)[reply
        ]
      Ffs,
      Pocketed 08:32, 7 October 2016 (UTC)[reply
      ]

      I have indefinitely blocked him. Normally I would let the discussion run its course, but the ongoing disruption during this (the DYK), after he agreed already to a one-week block and staying away from problem areas, show that the problems don't even top while a discussion about an indef block and restrictions is ongoing. Obviously the discussion here can continue and whatever the result of it may be implemented without further consulting me.

      Fram (talk) 08:28, 7 October 2016 (UTC)[reply
      ]

      Proposal #2

      As per my comments above, turn the indef block into an indef community ban which can be appealed after 3 months.

      • Support as proposer. Boing! said Zebedee (talk) 10:25, 7 October 2016 (UTC)[reply]
      • Support More nuanced approach; along the lines with what I was considering above.
        Pocketed 11:26, 7 October 2016 (UTC)[reply
        ]
      • Support This is clearly the better idea. ThePlatypusofDoom (talk) 11:48, 7 October 2016 (UTC)[reply]
      • Support - it's a shame that Varun's behaviour has come to the point where an indef block was in fact, in order, and I'm disappointed that he did not listen to the community's advice prior to his block - even when he was suggesting remedies himself. I believe Boing!'s comments are spot on, and a community ban would be better. It's clear that Varun is young (username suggests he was born in 2003?), and I won't make any comments on that, considering I am only a bit older myself - but maybe three months to reflect on his behaviour is what he needs - maybe he will have matured and be in with a chance of coming back. Patient Zerotalk 11:53, 7 October 2016 (UTC)[reply]
      • Support Agree with Boing and Patient Zero (though I'm not close in age...) Hobit (talk) 12:25, 7 October 2016 (UTC)[reply]
      • Support I like the fact he's eager to help and work on the project, but this is a community project, and he needs to listen when there are concerns. 3 months is I hope sufficient enough from Varun to get a better idea of how to work better collaboratively. RickinBaltimore (talk) 12:35, 7 October 2016 (UTC)[reply]
      • Support: It's pretty sad to see this happening to someone who's just trying to help. But the thing is that Varun is young and have a time understanding how collaboration works. I think community ban is a better option. Ayub407talk 12:47, 7 October 2016 (UTC)[reply]
      • Support. Regrettable, given that there is clearly a lot of enthusiasm here to help out. Unfortunately you cannot build an encyclopædia out of good intentions; it needs quality contributions from people who take the time to understand what they are doing. Lankiveil (speak to me) 13:08, 7 October 2016 (UTC).[reply]
      • Support as per above - It's great he wants to help in every way possible however unfortunately in the 3 months of being here he didn't heed any of the warnings nor the advice, Best course of action IMHO. –Davey2010Talk 14:08, 7 October 2016 (UTC)[reply]
      • Comment - I'm a little uncomfortable with this. Everything I said above about the seriousness of his actions, and the need for intervention stands, but... Sure, we've allowed Varun's disruption to escalate, and we should have acted sooner. What we've done is allowed him to sink into a mindset where he thinks, ok, I can do these things, and some people will shout at me, but nothing serious will happen. Who knows what a day, or week block earlier would have achieved? Instead, we now say: hey, that's enough - here's your first real punishment - you're community banned, and can't even appeal for three months. I know how a teenage me would have felt about that. Seems I'm in a minority, though.
        I'm not advocating that we should "go easy" - I firmly believe that we need to make sure that Varun is not unblocked until he has properly re-evaluated his participation, and thoroughly convinced us that he has a plan to return to editing without any disruption. I further believe it needs to be crystal clear that any new disruption after an unblock will result in the block being instantly reinstated, with escalated restrictions on appeals. I just am not convinced, in these circumstances, that we should be saying, on this first occasion where serious action is taken, that none of that can happen for three months. -- Begoon 16:04, 7 October 2016 (UTC)[reply]
      • Support - On first glance the length of the ban gives me pause, however the outright attempts at deception regarding copyrights speak volumes, to me. I don't think it's so much a
        assuming good faith) issue or a maliciousness issue. If the former, hopefully three months will lead to some personal growth, and if the latter it will either change his ways or dissuade him from using Wikipedia as a source of entertainment. PGWG (talk) 17:16, 7 October 2016 (UTC)[reply
        ]
      • Support Sadly, I think it's time to do this. Iridescent and I had a conversation about him several weeks ago and nothing has improved since then. An appeal after three months gives adequate opportunity for reflection. I hope he matures some in that time, because he's definitely enthusiastic. He just needs to channel that enthusiasm into a productive editing pattern. Katietalk 19:39, 7 October 2016 (UTC)[reply]
      • Support per nominator and Patient Zero - This user has a lot of enthusiasm to help contribute to Wikipedia. Unfortunately, Varun had a pattern of disruptive behavior and unwillingness to work with others for the last three months that he has been here. Hopefully by the next three months, he will have a better understanding of how to collaborate with others. Lord Sjones23 (talk - contributions) 19:53, 7 October 2016 (UTC)[reply]
      • Comment I'm with Begoon on this, and support in principle the sentiment Boing is shooting for. Varun's enthusiasm is commendable, if partly to blame for his problems. As mentioned above, I think the 2003 in his username is indicative. All this said, his major problems are excessive speed over too wide of an area, and not learning from the dozens of messages. I don't think any of it was intentional or vindictive, but rather concomitant with youth. I would prefer not to call this a ban, just for the implications it gives to one unfamiliar with the nuances we have here. I would support (and will suggest) unblock when appropriate subject to 2 conditions: Mainspace edits only, and zero use of the {{ }} characters, either manually or via Twinkle (exception given to adding references only). I think most issues would be curbed by not using those innocuous braces, and a mainspace restriction will let him contribute and learn how things are done here. CrowCaw 21:54, 7 October 2016 (UTC)[reply]
      • Oppose the wording of this on technical grounds. Per
        WP:STANDARDOFFER. Otherwise, an indef block suffices and covers everything. Softlavender (talk) 00:49, 11 October 2016 (UTC)[reply
        ]

      Discussion

      I concur. As a point of note, "indef block" is Proposal #1. Primefac (talk) 01:20, 8 October 2016 (UTC)[reply]
      Agree, plus the "appealable in three months" is illogical with a ban. Softlavender (talk) 00:55, 11 October 2016 (UTC)[reply]
      • Hello all! So I have been blocked - I am not too surprised. I preempted this. I would like to appeal this block to be change into an indefinite ban. I am ready to the conditions Crow said in there - only only mainspace contributions (without disruption). I do not want to leave this place and I am therefore appealing this block be changed to a ban. Any administrator can block me again if I cause even one disruption after me being unblocked. Give me as long as a ban appeal time I'll agree but please don't indefinitely block me. Please..... With still some hope left in my heart that someone will help me I write this message hope this isn't a false hope. Thank you so much. VarunFEB2003 06:00, 8 October 2016 (UTC) <comment copied from user's talk>- NQ (talk) 06:18, 8 October 2016 (UTC) [reply]

      Close?

      Could an uninvolved admin close the thread? No one has commented in three days, Varun is pinging everyone left and right about this, and we need to bring an end to the discussion. Katietalk 14:43, 10 October 2016 (UTC)[reply]

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

      Backlog

      If anyone is bored, head on over to

      whisper in my ear 10:28, 7 October 2016 (UTC)[reply
      ]

      Enormous backlog at
      WP:OAFD

      There have been hundreds of outstanding deletion discussions ready for closure for almost a week now. Some help cleaning up the older ones would be appreciated, although a lot of them are "tricky" cases that will need a bit of untangling and possibly some unpopular decisions. Lankiveil (speak to me) 12:23, 7 October 2016 (UTC).[reply]

      Arbcom Electoral Commission

      Just a heads up for those who are interested in this sort of thing; we are once again selecting an Arbcom Electoral Commission. See Wikipedia:Requests for comment/Arbitration Committee Elections December 2016/Electoral Commission --Guy Macon (talk) 18:24, 7 October 2016 (UTC)[reply]

      Interlanguage moves

      I came here from Wikipedia talk:Requested moves#Interlanguage moves. So we have this article at WP:Pages needing translation into English#Dubravko Klarić, which wiki-conventionwise seems ok, except for the language. I was wondering if it is possible to move a page to an other-language wikipedia (hr.wikipedia.org in this case) with retention of the page history, which seems possible via export/import, although special rights are needed for that. --HyperGaruda (talk) 05:01, 8 October 2016 (UTC)[reply]

      For some reason that I don't understand, import into en:wp is restricted to a few major languages, a group that doesn't include Croatian — you can't import from hr to en. I believe that this is locally set (either by local admins or by developers editing local settings), so hr:wp may nevertheless be able to import from en. In this case, we can just skip the page history: aside from the infobox, which depends on local template names being similar to ours (probably not the case), this version of the article is quite similar to the current version, and literally the only edit by anyone other than the creator is the addition of {{
      WP:PNT. Nyttend (talk) 00:44, 9 October 2016 (UTC)[reply
      ]
      HyperGaruda, see this note from the user that I mentioned; to use en:wp terminology, apparently Dubravko Klarić's article would be considered a spammy autobiography about someone who's not notable in the first place. We might as well delete it here. Nyttend (talk) 12:00, 9 October 2016 (UTC)[reply]
      Glad to see that a native speaker has taken a look. Thanks to you both, Nyttend and Srdjan m. Deletion is on its way. --HyperGaruda (talk) 13:28, 9 October 2016 (UTC)[reply]

      Comments on CheckUser and Oversight candidates: last call!

      The Arbitration Committee has invited comments from the community on this year's candidates for the CheckUser and Oversight permissions. The community consultation phase will end at approximately 23:59, 8 October 2016. Any final comments may be posted at Wikipedia:Arbitration Committee/CheckUser and Oversight/2016 CUOS appointments or emailed privately to the arbitration committee at arbcom-en-c@lists.wikimedia.org. Opabinia regalis (talk) 06:34, 8 October 2016 (UTC)[reply]

      Nancy O'Dell

      Extra eyes or protection to Nancy O'Dell, who is being mentioned in connection with the latest over-the-top Donald Trump audio/video by the Daily Fail. Carrite (talk) 15:23, 8 October 2016 (UTC)[reply]

      At some point we'll need an dedicated noticeboard for all the issues surrounding this election. Jo-Jo Eumerus (talk, contributions) 15:28, 8 October 2016 (UTC)[reply]
      Also Arianne Zucker‎‎. Probably wouldn't hurt to have more sober eyes on Billy Bush. People are lovely. Kuru (talk) 16:32, 8 October 2016 (UTC)[reply]

      Orphan images backlog

      100+ orphaned images now eligible for deletion. Thanks. Lugnuts Precious bodily fluids 09:57, 9 October 2016 (UTC)[reply]

      Backlog of eligible files cleared. This is really a task for an adminbot though, and I remember we already had one. Jo-Jo Eumerus (talk, contributions) 12:17, 9 October 2016 (UTC)[reply]

      Block

      i try to speeded delete my mother talk page by using orphaned talk page it was last use 2013 And I try to delete fire : that I did not know how to provide the copy write so I can use the same name I was block from both place and administer page

      And the person who report this leave the comment ....... If the negative thing not show in google results it would be fine

      I created my mom page and have the not want thing in same Google search last name can you delete what I try to delete and unblock me it a process . Am I allowed to delete the thing older than 7 days in my own talk page.? Am I allowed to deleted talk page that not active for three year?

      I think I should be unblock ......Can I put {{
      talk • contribs) 21:33, 9 October 2016 (UTC)[reply
      ]

      It'd help us greatly if you told us who you are-and I'm guessing English isn't your first language.Some bits of your complaint I'm afraid are just gobbledegook- 'have the not want thing in same Google search last name' means nothing.

      If I'm deciphering this correctly,you want to be unblocked(again,we need to know who you are and what you did to be blocked),and delete a talk page that you haven't used since 2013,using the Speedy Deletion tag. If you can identify yourself,we can then see if it's reasonable for you to be unblocked. Lemon martini (talk) 21:33, 9 October 2016 (UTC)[reply]

      @Lemon martini: This has to do with Commons. Not anything we can help with. They are blocked there for vandalism. --Majora (talk) 21:37, 9 October 2016 (UTC)[reply]

      Ah many thanks for clearing that up!There were precious few clues in their post Lemon martini (talk) 21:40, 9 October 2016 (UTC)[reply]

      I'm guessing English isn't the OP's first language, but I have no idea what's going on here. Anyone else? Erpert blah, blah, blah... 22:38, 9 October 2016 (UTC)[reply]
      @
      Erpert: It is a Commons issue. Nothing we can do here. --Majora (talk) 22:43, 9 October 2016 (UTC)[reply
      ]
      Ah. Well, an uninvolved user will close this thread soon enough then. Erpert blah, blah, blah... 22:45, 9 October 2016 (UTC)[reply]
      talk · contribs) has made several edits to the photo used in the infobox for Thita Manitkul so that is one possibility. If that is a pic of TM then it is one from many years ago. MarnetteD|Talk 22:46, 9 October 2016 (UTC)[reply
      ]

      I do not know why o; missing information may be my ip was block — Preceding

      ) 00:31, 10 October 2016 (UTC) I was block from several {{}} my own and my mother because I notice it on Google search I want to use the name of the file and l also did not want some mistake to show in public. I didnot know that much about. Wikimedia and got attack. If I did not use my real last name l will not offence. If you can not unblock me can you use{{
      talkcontribs) 00:49, 10 October 2016 (UTC)[reply
      ]

      Is he trying to say that Thita Manitkul is his Mother? And probably he wants to delete or hide something in the article. Can Kudpung speak Thai language? 1.39.36.47 (talk) 06:24, 10 October 2016 (UTC)[reply]
      As far as I can tell: both his and his mother's account got blocked when he tried to fix "some mistake" on his userpage or elsewhere; which he interpreted as being "attacked". He is asking admins to delete both talk pages (his and his mother's) as he is very concerned about this "mistake" that he doesn't want to be seen by the public. -- ChamithN (talk) 07:59, 10 October 2016 (UTC)[reply]
      No, their surnames are same. He created the page
      User talk:Pandamanitkul is about the same article. 1.39.38.5 (talk) 09:12, 10 October 2016 (UTC)[reply
      ]

      LavaBaron's editing restrictions - review

      Removal of advanced permissions – community comments

      The Arbitration Committee is seeking community feedback on a proposal to

      Removal of permissions. Your comments are welcome at the motion page. For the Arbitration Committee, Kevin (aka L235 · t · c) 15:49, 10 October 2016 (UTC)[reply
      ]

      Discuss this at : Wikipedia:Arbitration/Requests/Motions#Motion to modify removal of advanced permissions ArbCom procedure

      To block this user

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


      This user name (User:WHAT THE FUCK ARE YOU DOING) is against Wikipedia policy. I kindly request admins to block that specified user name. Gopala Krishna A (talk) 19:06, 10 October 2016 (UTC)[reply]

      @Gopala Krishna A: Already blocked -- samtar talk or stalk 19:07, 10 October 2016 (UTC)[reply]
      @Samtar: Thank you. --Gopala Krishna A (talk) 19:13, 10 October 2016 (UTC)[reply]

      @

      WP:UAA. Cheers, ansh666 19:44, 10 October 2016 (UTC)[reply
      ]

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

      Move request for
      Mac OS

      Closed by Cúchullain. Samvscat did not need an AN post here,

      non-admin closure
      )

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

      Can someone who was not involved in the discussion please close out the discussion

      Talk:Mac OS#Requested move 1 October 2016 and perform any subsequent actions? Thank you! —Samvscat (talk) 20:16, 10 October 2016 (UTC)[reply
      ]


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

      Noticeboard backlogs

      Hi all, just to let you know that

      UAA, have a backlog dating back a few days. TIA. -- LuK3 (Talk) 23:47, 10 October 2016 (UTC)[reply
      ]

      Administrator Assistance Required

      at Wikipedia:Files for discussion#Old discussions where the backlog dates back to July 4, 2016. Most of these are straightforward, non-contentious closures, and all administrators are invited to spend a few minutes to help reduce the backlog -FASTILY 01:43, 11 October 2016 (UTC)[reply]

      Very basic backlogs

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


      Lately, we've been running backlogs at very basic administrative processes that are high importance. Things like

      WP:AIV are not getting the rapid attention they used to. The latter two backlogs are particularly concerning because we can't expect our counter-vandalism editors to effectively combat vandals without swiftly protecting pages and blocking editors when large amounts of damage are being done. In the short-term, it would be helpful for admins to chip in a few spare minutes whenever they have a chance in those areas. In the long-term, we need more admins. ~ Rob13Talk 03:41, 11 October 2016 (UTC)[reply
      ]

      We need at least one successful RFA every month. And the oppose votes in RFAs that administrators must be content creators (Read FA, GA) is not helpful, if these backlogs must be cleared. Majority of the content creators will continue creating content after experimenting with their newly found administrative tool for one month. There are 300+ active editors who can be a good administrator, but they don't get nominated. Wikipedia needs content creators, but Wikipedia also needs Administrators to protect the content, not just add an userbox on their userpage "This user is an administrator" (who likes using their administrator tool, once in a year). — Preceding unsigned comment added by 1.39.38.191 (talk) 06:23, 11 October 2016 (UTC)[reply]
      Does anyone have a good plan on how to get more admins? Tazerdadog (talk) 07:35, 11 October 2016 (UTC)[reply]
      We have well over 500 active admins. They just don't seem to be currently interested in clearing out the backlogs. Softlavender (talk) 07:49, 11 October 2016 (UTC)[reply]
      No, there are actually 330 administrators who have some interest. Still, we need more administrators. 1.39.38.105 (talk) 08:32, 11 October 2016 (UTC)[reply]
      It might feel like it, but only CSD is particularly backlogged: User:EsquivalienceBot/Backlog. I suspect CSD is mostly backlogged with non-controversial content that probably needs to be seen to but isn't particularly problematic. It may be that we don't have enough admins, and that all of these should be 0 (and there are other processes undocumented therein--Esquivalience needs a little bugging to see if he will add the others), but I am not so sure. I am sure that there are people who know that we don't need more admins, evidence or no.... --Izno (talk) 11:44, 11 October 2016 (UTC)[reply]
      The current RFA arrangement is crazy. Adminship is not a priesthood. We should instead be giving out adminships left right and centre to editors in good standing who have (a) a lengthy history of real, positive contributions, and (b) no, or a very low number, of blocks or warnings, relative to their account age, and (c) a history of civil interaction with other users. Adminship should not be a big deal; it can easily be revoked if they misuse the tools. Perhaps we should try this for 50-100 new admins, and see how it goes? -- The Anome (talk) 14:31, 11 October 2016 (UTC)[reply]
      This. 1000x This. I'd love to give each crat the ability to just promote 5 admins after the minimum community review to make WMF happy. Failing that, I'd love to see experienced admins mentor an experienced editor through early adminship. I'm at the point where I think it could be a net positive for the project if we admined everyone with 15K edits and a clean block log, and then took the bit away from anyone who misused it. Tazerdadog (talk) 15:58, 11 October 2016 (UTC)[reply]
      The Anome, Tazerdadog; you may already be aware. In the event you're not:Wikipedia:Perennial_proposals#Automatically_grant_adminship_to_users_with_a_certain_number_of_edits_or_time_editing Tiderolls 17:16, 11 October 2016 (UTC)[reply]
      I'm aware, the above was mostly just wishful thinking. Tazerdadog (talk) 18:02, 11 October 2016 (UTC)[reply]
      "Perhaps we should try this for 50-100 new admins, and see how it goes?" - Agree. But we all know how it'll pan out on here. There will be a lengthy RfC, with a ton of users being too pig-headed to see the net benefits and shooting it down before it gets going. Everyone will waste their time with that and nothing will change. There's a ton of user who do admin-esque tasks without the full rights, but will never pass an RfA. Give them a go at it. How hard can it be? Sure, there might be one or two who
      hang themselves, but it can't be any worse than it is now. They'll still all be accountable and subject to desyoping if they go mad with power. But I'm preaching to the converted here. We all know this thread won't a) kickstart this or b) have any impact in reforming the process. Now to go back to finding some pesky redlinks and unredlinking them. Lugnuts Precious bodily fluids 18:19, 11 October 2016 (UTC)[reply
      ]

      What Wikipedia really needs a substantial influx of new active editors, probably representing some new and largely untapped demographics. Short of radically unbundling admin tools, that is the only way to significantly increase the number of active admins. Nsk92 (talk) 19:22, 11 October 2016 (UTC)[reply]

      Yes, but only if you first assume that this 'untapped demographic' would be insane enough to attempt RfA. I wouldn't count on it, to be honest. -FASTILY 00:24, 12 October 2016 (UTC)[reply]
      Amen to that. I have no interest in being put through the ringer again and getting dinged for "lack of content creation." There are gnomes in the world. I prefer my inputs to be minor but worthwhile (maybe even significant). Primefac (talk) 01:05, 12 October 2016 (UTC)[reply]
      I don't know about that. I think that if there were to be a big influx of new regular editors, a definite fraction of them would later try for an RfA, insane or not. It is a natural process and a feature of how large groups work. As for the RfA itself, I feel that the main problems in RfA are caused by bigger issues affecting Wikipedia as a project. The main problem is that over the last 15 years Wikipedia has become logistically very complex, with a highly developed and still developing system of technical rules and tools for dealing with various aspects of the project. The admiship is still configured as an `all or nothing' package, as in the early days of Wikipedia. Only now that the project has become incredibly more complicated, the substantive knowledge of the various aspects of the project needed for demonstrating basic competency has become much harder to attain. That's the main reason why the de facto standards for passing RfA had been creeping higher and higher, at least until recently. At the same time the number of regular users increased only modestly (after the initial explosive growth), and in the last few years the growth has been not far above flat. We can't credibly solve this problem by tinkering with the process and trying to artificially lower the bar for passing RfA. That will just create a lot of resentment from people who feel that they cannot trust the candidates who are being forced through the system, and ultimately there will be an ugly revolt of some kind. The only credible solutions are to either dramatically increase the supply of experienced editors under the current system (while I agree that this is not very likely), or to radically reconfigure adminship itself. Nsk92 (talk) 01:16, 12 October 2016 (UTC)[reply]
      I agree with Nsk2, every editor can't know all the technical details of Wikipedia. So, any RFA candidate with more than 69% support votes should be made administrator. — Preceding unsigned comment added by 1.39.36.202 (talk) 03:54, 12 October 2016 (UTC)[reply]
      It's not strictly an admin shortage that causes the backlogs at CSD. It is often filled with articles that aren't valid speedy deletion candidates, so they languish for days until an admin comes along that doesn't mind stretching the definition of A7 or G11 to get rid of them. More admins won't change that. —Xezbeth (talk) 05:20, 12 October 2016 (UTC)[reply]
      I think you'll find that most admins have no problem just declining a speedy that clearly does not meet any criteria. I've been doing CSDs the last few days and I don't see any unusual backlogs anyway.
      talk) 05:45, 12 October 2016 (UTC)[reply
      ]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.
      CSD looks pretty normal. Other non admins can also decline speedy deletes that are not applicable, or fix up easy to rectify problems, such as lack of fair use rationales. So it is not just deficiency of admins. Instead it means that people want to different things, such as write articles! Graeme Bartlett (talk) 08:21, 12 October 2016 (UTC)[reply]

      Stupid mistake. Can an admin rectify this?

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


      When trying to report TransformersBatman (talk · contribs) for vandalizing the page Kevin Durant, I made a stupid mistake and pasted the wrong name. Hence Kevin Durant (talk · contribs) got blocked undeservedly, while the vandal is still unblocked. Can a friendly admin please rectify the situation and block the correct vandal? Thanks and apologies. Kleuske (talk) 13:29, 11 October 2016 (UTC)[reply]

      Kevin Durant has been blocked since 2007 so it's nothing to do with your report. I'll check out the other user now. — Martin (MSGJ · talk) 13:30, 11 October 2016 (UTC)[reply]
      Phew... Kleuske (talk) 13:31, 11 October 2016 (UTC)[reply]
      And TransformersBatman (talk · contribs) just blocked by User:Widr — Martin (MSGJ · talk) 13:32, 11 October 2016 (UTC)[reply]
      I posted TransformersBatman to AIV for you, I saw what you were trying and was going to reach out to you about it. The KD accounts like MSGJ said has been indeffed for over 9 years now for impersonation of a public figure, as well as vandalism. RickinBaltimore (talk) 13:32, 11 October 2016 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      Non-free image in need of deletion

      I just uploaded a lower resolution version of this non-free image. It would be helpful if the original version of the file was deleted. As far as I'm aware, that's Wikipedia policy. DarkKnight2149 21:16, 11 October 2016 (UTC)[reply]

      No need to report that to this board. A bot automatically identifies those that qualify and dozens qualify every day and get deleted after seven days (for some reason several hundred today but that's an aside)--S Philbrick(Talk) 21:31, 11 October 2016 (UTC)[reply]
      @
      subst:orfurrev}}. --Redrose64 (talk) 23:49, 11 October 2016 (UTC)[reply
      ]
      Alright, I'll keep those in mind. DarkKnight2149 23:52, 11 October 2016 (UTC)[reply]

      Note to adminstrators

      A prolific sock puppeteer is currently using my signature to leave false warning templates on the Talk Pages of various users ([53]). I suspect that the same user may have been behind this impersonation account. If you receive any reports from someone appearing to be me, I would suggest making sure it actually is before taking it seriously. DarkKnight2149 15:45, 12 October 2016 (UTC)[reply]

      I have semi-protected User talk:DangerousJXD — Martin (MSGJ · talk) 15:52, 12 October 2016 (UTC)[reply]

      An arbitration case regarding The Rambling man has now closed and the final decision is viewable at the link above. The following remedies have been enacted:

      1. request for adminship
        .
      2. The Rambling Man (talk · contribs) is prohibited from insulting and/or belittling other editors. If The Rambling Man finds himself tempted to engage in prohibited conduct, he is to disengage and either let the matter drop or refer it to another editor to resolve. If however, in the opinion of an uninvolved administrator, The Rambling Man does engage in prohibited conduct, he may be blocked for a duration consistent with the blocking policy. The first four blocks under this provision shall be arbitration enforcement actions and may only be reviewed or appealed at the arbitration enforcement noticeboard. Should a fifth block prove necessary, the blocking administrator must notify the Arbitration Committee of the block via a Request for Clarification and Amendment so that the remedy may be reviewed. The enforcing administrator may also at their discretion fully protect The Rambling Man's talk page for the duration of the block.

        Nothing in this remedy prevents enforcement of policy by uninvolved administrators in the usual way.

      3. interacting with, or commenting on, each other anywhere on Wikipedia (subject to the ordinary exceptions
        ).
      4. George Ho (talk · contribs) is indefinitely restricted from participating in selecting main page content. For clarity, this means he may not participate in:
        1. Any process in which the content of the main page is selected, including
          Today's featured picture
          .
        2. Any process in which possible problems with the content of the main page are reported, including
          WP:ERRORS and Talk:Main Page
          .
        3. Any discussion about the above processes, regardless of venue.
        He may edit articles linked from or eligible to be linked from the main page (e.g., the current featured article) and may participate in content review processes not directly connected to main page content selection (e.g., reviewing
        Featured article candidates
        ). He may request reconsideration of this restriction twelve months after the enactment of this remedy, and every six months thereafter.
      5. The community is encouraged to review the selection process for the
        In the news
        sections of the main page. The community is also reminded that they may issue topic bans without the involvement of the Arbitration Committee if consensus shows a user has repeatedly submitted poor content, performed poor reviews, or otherwise disrupted these processes.

      For the Arbitration Committee, Ks0stm (TCGE) 05:01, 13 October 2016 (UTC)[reply]

      Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard#Wikipedia:Arbitration/Requests/Case/The Rambling Man