Jump to content

Wikipedia:Administrators' noticeboard: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Line 288: Line 288:
* Absolutely '''support''' an unblock. This was clearly a misunderstanding. But Nakon needs to be the one to unblock (provided he shows up in the next 12–24 hours). That's all. --[[User:IJBall|IJBall]] <small>([[Special:Contributions/IJBall|contribs]] • [[User talk:IJBall|talk]])</small> 06:59, 9 January 2016 (UTC)
* Absolutely '''support''' an unblock. This was clearly a misunderstanding. But Nakon needs to be the one to unblock (provided he shows up in the next 12–24 hours). That's all. --[[User:IJBall|IJBall]] <small>([[Special:Contributions/IJBall|contribs]] • [[User talk:IJBall|talk]])</small> 06:59, 9 January 2016 (UTC)
:*Have you seen this thread: [[User_talk:Nakon#Indef_of_EEng.3F]]? It seems it was intentional and Nakon is standing by it. [[User talk:HighInBC|<b style="color:Chocolate">HighInBC</b>]] 07:02, 9 January 2016 (UTC)
:*Have you seen this thread: [[User_talk:Nakon#Indef_of_EEng.3F]]? It seems it was intentional and Nakon is standing by it. [[User talk:HighInBC|<b style="color:Chocolate">HighInBC</b>]] 07:02, 9 January 2016 (UTC)
::* I'm still assuming a misunderstanding here. At the least, Nakon should have the opportunity to explain/defend his actions. I've dealt with Nakon enough to believe that this has just got to be an mistake... --[[User:IJBall|IJBall]] <small>([[Special:Contributions/IJBall|contribs]] • [[User talk:IJBall|talk]])</small> 07:04, 9 January 2016 (UTC)

Revision as of 07:05, 9 January 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 assess, summarize, and formally close a Wikipedia discussion. Do so when consensus appears unclear, it is a contentious issue, or where there are wiki-wide implications (e.g. any change to our policies or guidelines).

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

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

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

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

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

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

      Include a link to the discussion itself and the {{Initiated}} template at the beginning of the request. A helper script can make listing easier. Move discussions go in the 'other types' section.

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

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

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

      Technical instructions for closers

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

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


      Other areas tracking old discussions

      Administrative discussions

      Wikipedia:Administrators'_noticeboard/IncidentArchive1156#Boomerang_topic_ban_proposal_for_User:Hcsrctu

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

      {{not done}} Ratnahastin; ANI reports that have been archived will not be closed. ~~ AirshipJungleman29 (talk) 14:06, 9 June 2024 (UTC)[reply]
      Restored the request because AirshipJungleman 29 has refused to clarify his above misleading response.[1] Ratnahastin (talk) 04:15, 18 June 2024 (UTC)[reply]
       Not done. There is no consensus for anything there. One uninvolved editor's opinion does not a consensus make. ScottishFinnishRadish (talk) 14:50, 27 June 2024 (UTC)[reply]

      Wikipedia:Administrators'_noticeboard#Block_review_User:Jamiesonandy

      (Initiated 12 days ago on 15 June 2024) Most participants believe that there is consensus around the issue(s) at hand. Likely to be unarchived if it is archived by a bot. –LaundryPizza03 (d) 16:20, 26 June 2024 (UTC)[reply]

       Done. ScottishFinnishRadish (talk) 15:03, 27 June 2024 (UTC)[reply]

      Wikipedia:Administrators' noticeboard/Incidents#Riposte97: time sink

      (Initiated 6 days ago on 22 June 2024) Obvious consensus has formed for a community imposed topic ban from "Indigenous peoples of North America, broadly construed". Admin close required. TarnishedPathtalk 09:49, 24 June 2024 (UTC)[reply]

       Closed by editor ScottishFinnishRadish. P.I. Ellsworth , ed. put'er there 20:07, 26 June 2024 (UTC)[reply]

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

      Requests for comment

      Wikipedia:Reliable_sources/Noticeboard/Archive_436#RfC: Entertainment coverage of the New York Post (including Decider and Page Six)

      (Initiated 103 days ago on 16 March 2024) Given that the discussion has now archived, it seems ripe for formal closure. — Red-tailed hawk (nest) 14:47, 27 June 2024 (UTC)[reply]

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

      (Initiated 80 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 78 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:Climate_change#RFC:_Food_and_health_section

      (Initiated 72 days ago on 17 April 2024) This was part of DRN process (Wikipedia:Dispute_resolution_noticeboard/Archive_245#Climate_change). It is ready to be closed [2] [3]. Bogazicili (talk) 18:39, 11 June 2024 (UTC)[reply]

       Done Sunrise (talk) 05:31, 26 June 2024 (UTC)[reply]

      Talk:Line of Duty#Request for comment: Listing Jed Mercurio in the Infobox as a showrunner

      (Initiated 61 days ago on 28 April 2024) Discussion on the actual RfC seems to have slowed. Consensus appeared clear to me, but I was reverted attempting to implement the edits so I'm requesting a formal closure. There is additional information on this topic (overall and about the page in question specifically) at Template_talk:Infobox_television#Alternatives_to_writer_and_director_parameters that I'd request a closer reads over. TheDoctorWho (talk) 05:25, 27 June 2024 (UTC)[reply]

      RFA2024, Phase II discussions

      Hi! Closers are requested for the following three discussion:

      Many thanks in advance! theleekycauldron (talk • she/her) 04:27, 17 June 2024 (UTC)[reply]

      If re-requesting closure at WP:AN isn't necessary, then how about different various closers for cerain section(s)? I don't mind one or two closers for one part or another or more. --George Ho (talk) 17:39, 18 June 2024 (UTC)[reply]

      During Phase I of RFA2024, we had ended up having multiple closers for different RFCs, even the non-obvious ones. I think different people closing subparts of this should be acceptable Soni (talk) 09:22, 28 June 2024 (UTC)[reply]

      Wikipedia:Reliable sources/Noticeboard/Archive 440#RfC: RFE/RL

      (Initiated 51 days ago on 7 May 2024) Archived Request for Comment. 73.219.238.21 (talk) 23:32, 4 June 2024 (UTC)[reply]

      Wikipedia talk:WikiProject Weather#Discussion -- New Proposal for layout of Tornadoes of YYYY articles

      (Initiated 48 days ago on 10 May 2024) RFC outcome is fairly clear (very clear majority consensus), however, a non WikiProject Weather person should close it. I was the RFC proposer, so I am classified too involved to close. There were three “points” in the RFC, and editors supported/opposed the points individually. Point one and three had 3-to-1 consensus’ and point two had a 2-to-1 consensus. Just need a non WP:Weather person to do the closure. The Weather Event Writer (Talk Page) 14:39, 13 June 2024 (UTC)[reply]

      Talk:Yasuke#RfC:_Should_the_view_that_Yasuke_was_a_samurai_be_added_to_the_article

      (Initiated 37 days ago on 21 May 2024) It's a bit buried in a header designed to group similar discussions together (because there have been so many of them). I would like to request an experienced or admin closer, as this page has had a lot of new or WP:SPA accounts on it recently, so some more advanced weighting of the consensus here may be necessary. Loki (talk) 21:57, 22 June 2024 (UTC)[reply]

      Wikipedia:Requests for adminship/2024 review/Phase II/Discussion-only period#Early close

      (Initiated 28 days ago on 31 May 2024) Since it's an injunctive discussion, I was hoping someone could step in and close after I withdrew my own. Thanks! theleekycauldron (talk • she/her) 07:26, 18 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 0 7 23 30
      TfD 0 0 0 7 7
      MfD 0 0 0 1 1
      FfD 0 0 0 0 0
      RfD 0 0 0 18 18
      AfD 0 0 0 1 1

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

      Other types of closing requests

      Talk:Allegations of genocide in the 2023 Israeli attack on Gaza#Requested move 3 May 2024

      (Initiated 55 days ago on 3 May 2024) Contentious issue but I feel like basically all that's going to be said of substance has been said, and it's been plenty of time. I'm also still a bit new to being active again to feel comfortable closing myself, so I just turned my evaluation of what's been said into a !vote. Kinsio (talkcontribs) 22:06, 27 June 2024 (UTC)[reply]

      Talk:Anti-Normanism#Requested move 22 May 2024

      (Initiated 36 days ago on 22 May 2024). Should be closed by an uninvolved admin.--Berig (talk) 07:47, 16 June 2024 (UTC)[reply]

      Hi @Berig, does it really need an admin? Tom B (talk) 04:58, 19 June 2024 (UTC)[reply]
      No, that is true. However, as an involved admin and the discussion having been quite lengthy and contentious, I thought it could be appropriate.--Berig (talk) 05:04, 19 June 2024 (UTC)[reply]
      After looking at it, I can see why an admin was requested, Tom B (talk) 14:52, 20 June 2024 (UTC)[reply]
       Closed by editor S Marshall. P.I. Ellsworth , ed. put'er there 20:03, 26 June 2024 (UTC)[reply]

      Wikipedia:Village_pump_(policy)#Notifying_Wikiprojects_and_WP:CANVASS

      (Initiated 31 days ago on 28 May 2024) Latest comment: 3 days ago, 79 comments, 37 people in discussion. Closing statement may be helpful for future discussions. Gråbergs Gråa Sång (talk) 10:29, 11 June 2024 (UTC)[reply]

      Talk:Srebrenica massacre#Requested_move_2_June_2024

      (Initiated 26 days ago on 2 June 2024), then relisted 10 June, Tom B (talk) 09:51, 17 June 2024 (UTC)[reply]

      Wikipedia:Reliable sources/Noticeboard#Dani Cavallaro

      (Initiated 24 days ago on 4 June 2024) A formal closure would be helpful to solidify consensus for future reference. Thanks! TechnoSquirrel69 (sigh) 15:42, 16 June 2024 (UTC)[reply]

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

      Review of Revision Deletion

      At the request of Prodego, I'd like to seek some additional viewpoints from other administrators about a recent revision deletion. (The action can be found here.) I don't believe that the revision meets the criteria of purely disruptive material. (Allegations, harassment, grossly inappropriate threats or attacks, malicious websites, etc.) Personally, I don't think one ping is enough to be considered harassment that requires revision deletion and a simple revert and block would have been appropriate. I propose to reverse the action and would appreciate some input before doing so. Mike VTalk 22:55, 31 December 2015 (UTC)[reply]

      • Hihacking the top here to give my reply. As I mentioned on my reply on my user talk page (linked by Mike above), in this case I felt a revision deletion was appropriate. This appears to be purely disruptive content (WP:RD3) - specifically an attempt by a user banned for harassing other editors to harass another editor. Harassment is specifically called out as an example where RD3 applies. I came to the conclusion that these edits were harassment and a threat to continue to harass based on the content of the edits, and the use of {{ping}}. I did not rev delete the other edits by this account, which didn't appear to be harassing. I understand the concern though, as I'm usually pretty stingy with revision deletions myself. I'm happy to have some third party review. Prodego talk 23:49, 31 December 2015 (UTC)[reply]
      While I'm not sure I would have gone out of my way to delete these edits, I think it's fair to say they fall under the description of edits which are "of little or no relevance or merit to the project" and I can see the merit in deleting the edits of a banned user trying to get attention. Sam Walton (talk) 23:04, 31 December 2015 (UTC)[reply]
      Yes, the edits have little relevance or merit to the project but that condition is dependent whether or not they're considered to be purely disruptive material. While I don't encourage banned users to get any additional attention, I don't believe that revision deleting the edits is supported by policy. I find it hard to equate highly disruptive edits (linking to malware, threatening others with harm, shock pages, etc.) with the edits linked above. Mike VTalk 23:22, 31 December 2015 (UTC)[reply]
      • The criterion for RevDel are sufficiently vague that almost any disruptive edit can be shoehorned into them, so as a matter of policy I can't say these don't qualify for it, espescially when coming from a banned user. That being said, I doubt I would have bothered doing it in this case. Blanking the content and revoking talk page access is sufficient. At the end of the day (or the end of the year) it really doesn't make much difference one way or the other. Beeblebrox (talk) 02:06, 1 January 2016 (UTC)[reply]
      • I've probably done more of these deletions than anyone, and yes, any contribution by a banned editor falls under revision deletion if it can be performed without deleting any contributions by another editor. Since they could be speedily deleted under G5, the contribution can be excised under RD5. It would serve the project well if someone edited the policy to make it clear that RD3 (being "purely disruptive") isn't some kind of gating factor or overriding criterion. It's not: it's just one condition among six.—Kww(talk) 16:51, 1 January 2016 (UTC)[reply]
      • This is probably symptomatic of a larger issue. There is a massive disparity between what many admins think is "disruptive" enough to require a revdel. And as Beeblebrox notes, the policy is so vague that almost any vaguely vandalistic edit can be interpreted to meet the threshold. Jenks24 (talk) 05:01, 3 January 2016 (UTC)[reply]
      • In my view, these edits are "purely disruptive material that is of little or no relevance or merit to the project", and therefore meet the revision deletion criteria. No opinion as to whether revision deletion was the best way to address this, though.  Sandstein  20:16, 6 January 2016 (UTC)[reply]
      • I agree that the standards of what should be rev-deleted varies quite a bit. I've looked at deletions that were called insulting and grossly offensive and just found harshly worded disagreements, definitely not obscene personal attacks. I wouldn't have rev-deleted those comments but they could have been seen as disruptive. Liz Read! Talk! 01:15, 9 January 2016 (UTC)[reply]

      What to do with articles that actively WP:HOAX, but do so incompletely?

      Carnism is a neologism created in Why We Love Dogs, Eat Pigs, and Wear Cows: An Introduction to Carnism. The book is somewhat notable, and, as such, the name of the book is quoted, in full, in several sources, often summarising Joy's work, but the term is basically unknown outside of these explicit summaries. The article acts as a WP:HOAX by adding in large numbers of concepts where the sources do not mention carnism, outside of, perhaps, a reference to Joy's book in another part of the work or list of sources. These are then used to claim the concept has expanded beyond Joy's work. There are also at least one person who personally knows the author floating around, which helps muddy the waters

      I have analysed the references at Wikipedia:Articles for deletion/Carnism (4th nomination). As you can see, they're... appalling. 30 of the 59 sources provably don't mention carnism (outside, perhaps, Joy's book title), 10 are Melanie Joy herself, 5 are summaries of Joy's work, 12 are partially or completely inaccessible, one is in French, and one uses the term independent of Joy, but is completely unnotable. However, because the book is notable, it's always possible to find another place summarising the book, or which includes Joy's book in a reference list, and they can always Gish Gallop with a google search.

      It's an appalling situation. Adam Cuerden (talk) 22:22, 1 January 2016 (UTC)[reply]

      After two deletes and a no-consensus-tending-delete, the fans of the term still have not got the hint? This is a classic case of WP:NEO. I have !voted delete and redirect, which is what we should have done last time, but unless the editors are WP:SPAs there's bugger all we can do about it here, I'm afraid. Guy (Help!) 22:32, 1 January 2016 (UTC)[reply]
      @Adam Cuerden: While I am certain that you really do believe that this is a hoax, I am concerned that your creation of a merge discussion, a biased advertizement for said discussion on WP:FTN, a deletion discussion that actually argues for the same merge, another biased advertizement for that on WP:FTN, and now this message, has the appearance of campaigning. --Sammy1339 (talk) 02:21, 2 January 2016 (UTC)[reply]
      I really do wish you wouldn't keep making things up. I linked the discussion of deleting a fringe neologism on FTN, and asked about the problems raised here. I don't quite see where on earth you're getting a claim the deletion is a merge. Adam Cuerden (talk) —Preceding undated comment added 03:13, 2 January 2016 (UTC)[reply]
      Why is this an issue for admins? Lugnuts Dick Laurent is dead 09:56, 2 January 2016 (UTC)[reply]
      If you are paying attention to Wikipedia:Articles for deletion/Carnism (4th nomination), please also note Wikipedia:Miscellany for deletion/Draft:Psychology of eating meat. Bit I agree it is not an issue for this noticeboard. (yet) Graeme Bartlett (talk) 09:10, 3 January 2016 (UTC)[reply]
      I wanted to bring that up: there's a procedural paradox. Adam Cuerden created a discussion at Talk:Why We Love Dogs, Eat Pigs, and Wear Cows#Carnism merge, and people weighed in; then a different editor, seemingly unaware of the un-bannered [4] merge discussion, created Wikipedia:Miscellany for deletion/Draft:Psychology of eating meat after the latter page was accused of being a WP:POVFORK of Carnism, and !voters there are expressing opinions about the fate of the Carnism article; and then Adam Cuerden created Wikipedia:Articles for deletion/Carnism (4th nomination), a nomination which has been accused of forum-shopping and canvassing [5]. How is a closer supposed to decide which discussion has "jurisdiction" here? FourViolas (talk) 13:03, 3 January 2016 (UTC)[reply]
      It's a mess alright, but in the end since there's only one subject the only real question is where does the final article go. Guy (Help!) 14:13, 4 January 2016 (UTC)[reply]
      Alas, it's not that simple. Joy's original book is uncontroversially notable; there are masses of sources in the draft which would be flagrant OR in the book's article or in Carnism; and several editors (including myself) believe that Carnism is notable independent of either Joy's book or Psychology of eating meat. Does anyone have experience closing discussions which have been unintentionally split among forums like this? Do we need to start over with one overarching RfC? FourViolas (talk) 00:23, 5 January 2016 (UTC)[reply]

      WP:UAA backlog

      There's a backlog of almost 5 days at WP:UAA, please could admin(s) take a look? Joseph2302 (talk) 01:41, 3 January 2016 (UTC)[reply]

      @Joseph2302: Thanks for leaving a note here. I took care of a handful of the oldest cases just now (while on a flying machine— so fancy!) . I, JethroBT drop me a line 07:34, 5 January 2016 (UTC)[reply]

      WP:RfPP backlog

      It's only about 15 hours backed up or so, but with NeilN off there are fewer eyes over at WP:RfPP and there's currently a bit of a backlog, so if any Admins want to wander over there... --IJBall (contribstalk) 07:27, 5 January 2016 (UTC)[reply]

      Don't really have any regular clerking admins, would be nice to have some so we don't have one admin shouldering the majority until another admin steps in. tutterMouse (talk) 09:53, 5 January 2016 (UTC)[reply]
      We definitely do have regular clerking admins, who are at the time NeilN, KrakatoaKatie, BethNaught, Ged UK and me. I might have missed someone else due to the time difference (I am mostly working in the European morning and evening), which would make it even more admins. But indeed in the last several days we tend to be backlogged for whatever reason.--Ymblanter (talk) 10:22, 5 January 2016 (UTC)[reply]
      I usually check in throughout the day but I caught a stomach bug last week that's knocked me for a loop. Doing a little better now. It seems its worst to me in the American very early morning and late afternoon/early evening. If somebody with football knowledge could have a look on a regular basis, it would help a lot. The football/footballer articles sometimes sit for a while because we American admins can be clueless about it (I know I am). Katietalk 13:10, 5 January 2016 (UTC)[reply]
      As a European, I am fine with the football articles, and also 90% it is transfer rumors not yet confirmed by sources which are persistently added to the articles.--Ymblanter (talk) 13:16, 5 January 2016 (UTC)[reply]

      Help me, please!

      Look, what a vandal Илья Драконов 2 is doing with my pages! Ilya Drakonov (talk) 15:38, 5 January 2016 (UTC).[reply]

      The account was blocked as being an impersonation account of your account it appears. RickinBaltimore (talk) 15:45, 5 January 2016 (UTC)[reply]
      Thanks. Could you protect my talk page for a few weaks? Ilya Drakonov (talk) 15:56, 5 January 2016 (UTC).[reply]
      I'd suggest going to WP:RFPP for that to request it there. I'm not an admin so I can't help in that regard :) RickinBaltimore (talk) 16:00, 5 January 2016 (UTC)[reply]

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


      This page has become a major time/energy sink, having gone through four AfDs and several DRVs, not to mention various threads at other venues. It's a complicated one, and to give us the best shot at a quasi-lasting outcome, I wonder if we could get a panel of, say, 3 uninvolved admins to do the close. The seven days ends today, and although it wouldn't be unreasonable to relist given the length of the page produced in the first week, it doesn't seem like substantial new arguments are being raised and there haven't been any new !votes in the last 24h.

      The precedent I'm drawing from in suggesting a panel of closers is Wikipedia:Articles for deletion/Cultural Marxism (2nd nomination), another highly contentious article that spanned many discussions. Of course not everybody was happy with the result, but it seems to have been "sticky", and I imagine that's in part due to the manner in which it was closed. — Rhododendrites talk \\ 17:47, 5 January 2016 (UTC)[reply]

      • Let me just add that ArbCom has indeed received a report about canvassing; consensus in our secret cabal is that a. it involves (ALLEGEDLY!) a relatively small number of votes, and b. this is nothing that the admins can't handle. Speaking of admins: good luck to the multi-headed panel called upon to close this. I propose a poll is taken to find out which admins are somehow involved in the topic, by which I mean, you know, the actual topic, not the article. Just to be fair. We gotta have representation from all fields of activity. Please do not post results of said poll anywhere. Drmies (talk) 18:19, 6 January 2016 (UTC)[reply]

      Just bumping this (it'll be the only time). We've passed the 8-day mark without a relist or anyone expressing an inclination to close. Normally not a big deal, but the whole thing seems rather toxic. Better to send this through WP:ANRFC? Or too soon? — Rhododendrites talk \\ 13:17, 7 January 2016 (UTC)[reply]

      I support going to ANRFC immediately. Fatigue is becoming an issue in that discussion. This needs to end. Townlake (talk) 17:51, 7 January 2016 (UTC)[reply]
      Did we get any other admins to volunteer? I'm willing to tackle this one, and would like to coordinate the closing statement. UltraExactZZ Said ~ Did 20:46, 7 January 2016 (UTC)[reply]
      I'm considering it, need to do a little more reading to see if I have the time though. Sam Walton (talk) 20:54, 7 January 2016 (UTC)[reply]
      OK. Let me know. Remind me - if the coin lands heads, we Keep it, right? I'm kidding, guys. UltraExactZZ Said ~ Did 21:16, 7 January 2016 (UTC)[reply]
      I'll join, I think this is manageable. And yes, though from what I've seen, if it lands tails we take the discussion to DRV and vote to do a new AfD. Sam Walton (talk) 21:24, 7 January 2016 (UTC)[reply]
      OK, let me get my thoughts and notes together and we'll see where we are once we get a third. UltraExactZZ Said ~ Did 22:04, 7 January 2016 (UTC)[reply]
      I would volunteer but I am not an admin. However, would anyone be against the idea of salting subsequent nomination pages, as these are starting to become textbook cases of the "I don't like it" argument, and are not becoming worth it to keep having. Kevin Rutherford (talk) 22:13, 7 January 2016 (UTC)[reply]
      There's almost certainly a consensus in that discussion for salting and/or not having any more discussions about this page for a while. Sam Walton (talk) 22:25, 7 January 2016 (UTC)[reply]
      • Policy for discussion length: A deletion discussion should normally be allowed to run for seven full days (168 hours). Beyond seven days, it's fair game to close it whenever if closing administrators come to a conclusion. ~ Cyclonebiskit (chat) 00:39, 8 January 2016 (UTC)[reply]

      I have closed the debate as Delete and Salt, have posted a joint statement explaining the close, and have deleted and salted the article. UltraExactZZ Said ~ Did 17:25, 8 January 2016 (UTC)[reply]

      Resolved

      Thanks to Ultraexactzz, Samwalton9, and Nihonjoe for tackling this. — Rhododendrites talk \\ 18:03, 8 January 2016 (UTC)[reply]

      Can someone point the way to DRV? This close deserves a relisting — Preceding unsigned comment added by 107.72.98.205 (talk) 19:18, 8 January 2016‎ (UTC)[reply]

      Go here ;) Grüße vom Sänger ♫ (talk) 20:39, 8 January 2016 (UTC)[reply]
      It is hidden pretty well at WP:DRV. ···日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 20:54, 8 January 2016 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      UAA Backlog

      Not sure if this has been a regular occurrence recently, but UAA has been filling up. Requests have been open since the beginning of the year, if anyone wants to tackle a few. Thanks, ~SuperHamster Talk Contribs 03:52, 6 January 2016 (UTC)[reply]

      I cleared a few out. Now I don't want to sound like a broken record but I can see at least one case where the editor had created one article that was speedy deleted a week ago, there was no warning about the username policy, and there were no edits since. I warned and closed the report as "wait for more edits", then a few hours later, and another admin comes along, slaps a big orange template on their talk and indef blocks them. Sorry, I can't see the point of a block, and it appears to contradict the policy ie: "Remember that blocking a new user is not actually something we want to do, it is something we do when it is needed to protect Wikipedia from harm." - what's the actual consensus for these sorts of things? Ritchie333 (talk) (cont) 09:49, 7 January 2016 (UTC)[reply]
      OTOH, accounts in violations of username policy, especially for corpnames, cannot be allowed to edit with that username because of our attribution rules. If there is a not a quick reply-and-rename following the initial warning, then they must be blocked in case they come back to the account weeks, months or years later.  · Salvidrim! ·  17:26, 8 January 2016 (UTC)[reply]

      The committee has resolved Palestine-Israel articles 1RR by motion that:

      • (1) The General 1RR restriction that is part of the Palestine-Israel articles case is rescinded including all modifications of the remedy.
      • (2) In its place, the following remedy is enacted: Editors are limited to one revert per page per day on any page that could be reasonably construed as being related to the Arab-Israeli conflict. Reverts made to enforce the General Prohibition are exempt from this limit. Also, the normal exemptions apply. Editors who violate this restriction may be blocked without warning by any uninvolved administrator, even on a first offense.

      Passed 10 to 0 by motion on 7:30 am, Today (UTC+0)

      For the Arbitration Committee, Mdann52 (talk) 08:13, 6 January 2016 (UTC)[reply]

      Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard#Palestine-Israel articles case modified

      DrChrissy's topic ban which currently states that "DrChrissy is indefinitely topic-banned from all pages relating to genetically modified plants and agricultural chemicals, broadly interpreted; appeals of this ban may be requested no earlier than twelve months since the date the case closed" is replaced with "DrChrissy is indefinitely topic-banned from all pages relating to genetically modified organisms, commercially produced agricultural chemicals, and the companies that produce them, broadly interpreted; appeals of this ban may be requested no earlier than twelve months since the date the case closed."

      For the Arbitration Committee Amortias (T)(C) 23:05, 6 January 2016 (UTC)[reply]

      Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard#Genetically modified organisms case modified

      Hello, I filed a request for mediation yesterday for this topic https://en.wikipedia.org/wiki/Racism_in_Italy but did not get any notification. As this is my first such request, I am hoping an Admin can help guide me through the process to get a resolution. Much regards, Trinacrialucente (talk) 21:50, 7 January 2016 (UTC)[reply]

      I see no evidence in your edit history that you filed such a request. Please follow the instructions at Wikipedia:Requests for mediation/Guide. Miniapolis 23:27, 7 January 2016 (UTC)[reply]
      For some reason the link I provided in the original request above was not showing under my edit page. I did it a 3rd time and now it is showing https://en.wikipedia.org/wiki/Wikipedia:Requests_for_mediation/Racism_in_ItalyTrinacrialucente (talk) 01:38, 8 January 2016 (UTC)[reply]
      As the request for mediation was rejected by Transporterman, I would like to ask what the next step here is? After on editor challenged me to provide citations and evidence for a topic on the Talk page, I did so. Then another editor (who has been blocked 3 times for edit warring and who did not take part in any discussion on the Talk page) simply reverted the page. This is seriously anti-scholarly behavior and Wikipedia is being held hostage by a few POV-pushing individuals here.Trinacrialucente (talk) 18:39, 8 January 2016 (UTC)[reply]

      Edit requests backlog

      Some help is needed from autoconfirmed editors to help with the backlog at Category:Requested edits and Category:Wikipedia semi-protected edit requests. There are currently 140 requested COI edits and 74 requested semi-protected edits. Mz7 (talk) 06:21, 8 January 2016 (UTC)[reply]

      Taking a look at these now. Nakon 01:55, 9 January 2016 (UTC)[reply]

      Topic bans for Gamergate?

      Yes, the Gamergate controversy mess again. It is well known that there are SPAs and more-or-less SPAs operating there, of which ForbiddenRocky (talk · contribs) is a prominent one. All sorts of elaborate rules have been created, some apparently by ArbCom, but the net effect seems to be to stifle valid debate about the entire concept of the article, let alone its appearance. The fall-out has, of course, been massive and extends well beyond en-Wikipedia itself. At least anecdotally, there have been site bans here for off-wiki harassment relating to it.

      We've got to break this cycle before it subsumes a massive number of experienced contributors who could probably sort things out but, like me, tend to be discouraged by the sheer ferocity and tenacity of those who are far too closely attached to it. I propose that we start with ForbiddenRocky, who recently hatted a comment by me in the belief that it should be on some sort of subpage. Splitting things apart like this falls into the hands of those who want to control through wikilawyering. How many newbies would look at the subpage, or even realise it exists (I certainly didn't until recently). My comment discussed no editor in particular, specifically mentioned "both sides" and was a terse analysis of the problem that is at the heart of why the article is as it is. I subsequently added this.

      Yes, topic banning ForbiddenRocky purely on the basis of this one thing is ludicrous but I am becoming very frustrated with the pattern on that article and I am sure that other people could find other examples (I've seen loads but am not in a great state to look for them right now). It needs to be opened up and I think the easiest way to do that is to offload those who spend far too much time there for, apparently, very little gain - bearing in mind that the article seems to be as unstable now as it has ever been and that the same arguments keep arising week in, week out involving mostly the same people.

      I'm happy to voluntarily ban myself (I've said very little there anyway and don't think I've edited the article at all) if only we can find a way to break the deadlock. Even topic bans of, say, one month in duration would probably help if we could find some metric for application.

      Not sure where to post this - I do realise that it is not an isolated incident, hence here rather than at ANI. - Sitush (talk) 07:07, 8 January 2016 (UTC)[reply]

      I had thought of something based on if an editor's contributions indicated > X% of total edits to this or related articles (which I think are mostly BLPs). However, the 30/500 rule in force might make that impractical - my brain is a bit fried at the moment and I can't work it out. - Sitush (talk) 07:32, 8 January 2016 (UTC)[reply]
      You did two reverts of ForbiddenRocky, which is not permitted. You should have asked for help before the second revert. However I agree that you talk should not have been hatted. 08:28, 8 January 2016 (UTC) — Preceding unsigned comment added by Graeme Bartlett (talkcontribs)
      Isn't it on the talk page? That plays straight into the hands of the wikilawyers. Regardless, my main point here is not that specific incident but rather how to find a way out of the morass. Perhaps it needs some sort of revision to past ArbCom remedies - I really don't know because it isn't the sort of thing I'm usually involved with. - Sitush (talk) 08:37, 8 January 2016 (UTC)[reply]
      As an editor of video game articles, this is one of those topics Id rather not get involved with under any circumstance. However, I am neutral on the matter and could provide a fresh perspective on the whole situation. → Call me Razr Nation 10:22, 8 January 2016 (UTC)[reply]
      Dont do it. Also no doubt someone will claim you have a COI because you love gaming mice or other such nonsense ;) Gamergate is a conflict between a tiny subset of forum/reddit/chan gamers (and I mean *tiny* given the % of the population of the world who play electronic games), journalists and rent-an-activists. For the majority of the happily gaming population and the entirety of the games industry proper, it is a non-event. Best keep it that way. Let them argue amongst themselves and keep doing your thing. Only in death does duty end (talk) 10:30, 8 January 2016 (UTC)[reply]
      I tend towards this sentiment but then I think, hey, if we keep brushing this under the carpet then the attrition will continue. It only takes a few experienced contributors to turn a mess round, provided they get a level playing field. Quite a few of the higher-profile caste articles were pretty much sorted out in this way and, yes, those too tended to be frequented by SPAs. - Sitush (talk) 12:54, 8 January 2016 (UTC)[reply]
      786 edits to that talk page, which is over half their total number of edits. But they rank only #6 for most contributions on that talk page... Drmies (talk) 16:06, 8 January 2016 (UTC)[reply]
      Only in Death hits the nail on the head. According to recent surveys around 178 million Americans are regular gamers (multiple hours per week). Average age of men being 35, women being 43. 99.9% of these people couldn't care less about GG and the only reason they'd even heard of it, if they have at all, is because of the abuse and harassment GG has heaped on women because that's all they're notable for. The article right now is a battleground of a tiny subset of vocal gamers fighting over something that's barely notable in the community that it concerns. If the article stuck to the actual notable events surrounding GG, that are mostly years old now, it would be a fifth of its size. Capeo (talk) 17:21, 8 January 2016 (UTC)[reply]
      The claim that you discussed no editor would sound way more plausible if you hadn't responded to a comment of "I've put in an incredibly bold edit," by an editor you have repeatedly attacked as an SPA with, "The idea of SPAs making incredibly bold edits here doesn't surprise in the slightest, although of course they shouldn't be allowed within a mile of the article anyway." 107.72.99.29 (talk) 12:17, 8 January 2016 (UTC)[reply]
      "They" is plural, ie: SPAs shouldn't be allowed within ..., etc. And this is the last time I respond to an anon in this thread. Anons in this topic area are in my opinion almost entirely people trying to avoid scrutiny. I see, by the way, that ForbiddenRocky has now activated the Wikibreak Enforcer. I suppose that is a start. - Sitush (talk) 12:50, 8 January 2016 (UTC)[reply]
      Sitush - there's a bit of a pattern on that page of people turning up, claiming to be super-neutral and only concerned about article quality, then making the suggestion that we ignore usual source policies/block a bunch of users/include a bunch of stuff that goes against UNDUE/delete the article entirely. This pattern does not generally increase article quality and frequently leads to a suspicion that such users are not really all that neutral after all, I would avoid repeating it. Artw (talk) 16:20, 8 January 2016 (UTC)[reply]
      There is certainly a pattern of people getting shouted down by entrenched contributors, quite a few of whom seem to contribute to little but that and related articles. That so many people have queried the quality and even the "sense" of it (ie: they read it and haven't got much clue what it is dealing with) suggests that new blood would be A Good Thing. Not mine, obviously. - Sitush (talk) 16:27, 8 January 2016 (UTC)[reply]
      When editors show up to ask and question the neutrality and then get labeled as Gamergate supporters by entrenched editors simply because they are questioning the article's narrative, that is a problem. I note I have not looked at the page since September per my voluntary ban, but what Sitush is saying is what has been happening even before the ArbCom case and was the basis for it. Note that there needs to be a larger discussion on dealing with ongoing controversies and the methods of the media today and how they intersect with WP policies that GG is only one recent example of, as what I've seen happening across WP lately is the use of UNDUE and FRINGE as shotgun approaches to shut down any deviation from mainstream sources, encouraging the type of behavior Sitush describes. --MASEM (t) 16:44, 8 January 2016 (UTC)[reply]
      • I don't beiieve this is the right approach to this discussion. This was an extremely contentious arbcom case, bringing it here when the community was already unable to handle the situation seems unlikely to produce the desired result. A filing it WP:AE or WP:ARCA seems like a better approach. Beeblebrox (talk) 16:19, 8 January 2016 (UTC)[reply]
      • Perhaps. I did say that I wasn't sure where would be best. I don't think there is anything from the case that could be enforced, so I guess ARCA would be the better of those two options. - Sitush (talk) 16:27, 8 January 2016 (UTC)[reply]

      My User Page

      Lrwx has logged into the new username, so closing. ···日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 00:17, 9 January 2016 (UTC)

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

      Hi, can't create my user page. Its on local or global blacklists. Could anybody help me. --Lrwx------ (talk) 12:03, 8 January 2016 (UTC)[reply]

      If we create it for you, you will not be able to edit it. You could make a draft page, and someone could move it for you. But... How about you chose a username with less than 6 consecutive symbols in it? Graeme Bartlett (talk) 12:27, 8 January 2016 (UTC)[reply]
      The talk page will not work either, so definitely change your username . Graeme Bartlett (talk) 12:29, 8 January 2016 (UTC)[reply]
      @Lrwx------: The rename help page is Wikipedia:Changing username, it also links to the pages where you can ask for a rename.Jo-Jo Eumerus (talk, contributions) 15:30, 8 January 2016 (UTC)[reply]
      Seems like a flaw in the system that a user could even create a username that the software will not allow a user or talk page for. . Would they even have been warned about this when creating the account? Beeblebrox (talk) 16:22, 8 January 2016 (UTC)[reply]
      hmmm Didn't see it on the blacklist, but I can understand why it would be troublesome, it's a set of linux permissions usually associated to files, so theoretically User:Lrwx---- would mean User(is) Linked (with) read, write & execute permissions. Yeah, I'd say a name change is needed . KoshVorlon 16:30, 8 January 2016 (UTC)[reply]
      Your account has been renamed to Lrwx on commonswiki, cswiki, dewiki, enwiki, enwikibooks, enwikinews, enwikiquote, enwikisource, enwikiversity, enwikivoyage, enwiktionary, frwiki, incubatorwiki, loginwiki, mediawikiwiki, metawiki, nlwiki, plwiki, ruwiki, specieswiki, svwiki, trwiki, and wikidatawiki. You will need to logout of your account, then login again using "Lrwx" as your username and then whatever your existing password is. Hope that helps. ···日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 18:47, 8 January 2016 (UTC)[reply]

      Also, it may be good to point some developers at this issue so something can be added to prevent such usernames in the future. ···日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 18:49, 8 January 2016 (UTC)[reply]

      Devs probably can't do a lot. It appears to be a local blacklist - so as the account was not actually created here, it would have bypassed it. Nothing can be done, unfortunately. Mdann52 (talk) 21:39, 8 January 2016 (UTC)[reply]
      Even if it's local, it should still be something looked at in order to prevent such issues in the future. ···日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 21:45, 8 January 2016 (UTC)[reply]

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

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


      Hi, Please see in my opinion the talk page's Bruskom. Urmia lake is located in West Azerbaijan in Iranian Azerbaijan region, Iran and this user write this lake for region of Kurdistan. also west Azerbaijan Province: the majority of west Azerbaiajn are Iranian Azerbaijanis & only large minority Kurds living in province. but User:Bruskom write all of the West Azerbaijan is Kurdistan's geographical my neutralization.please consider it--SaməkTalk 19:34, 8 January 2016 (UTC)[reply]

      Content dispute. Read the dispute resolution policy. Discuss on article talk page. If that fails, follow one of the content dispute resolution procedures, such as third opinion. Report conduct issues at arbitration enforcement after reading the boomerang essay. Robert McClenon (talk) 19:41, 8 January 2016 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      Standard offer request for Bazaan

      Hello,

      I am passing along a Standard offer unblock request from Bazaan (talk · contribs · deleted contribs · logs · filter log · block user · block log). This request was sent to UTRS. The user has requested that the content of the unblock request be forwarded to the noticeboard. The relevant content is as follows:

      I agree to another Standard Offer if necessary, although it would be the second time. I would like the content of my unblock request to be forwarded to the noticeboard. I promise to never repeat the behaviour which led to my initial block, and the subsequent indefinite block.

      Why do you believe you should be unblocked? It's been six months, please give me another chance. At least give me a rope.

      If you are unblocked, what articles do you intend to edit? Most South Asian, but wide ranging

      Why do you think there is a block currently affecting you? If you believe it's in error, tell us how. I purposefully brought a sock puppetry ban on my account. It's my fault. I have suffered enough, including tremendous personal attacks.

      Is there anything else you would like us to consider when reviewing your block? Plenty of accounts have been blocked in my name, although most aren't mine.

      The ones used by me are Bazaan, Rainmaker23, Uck22, JKhan20 and Merchant of Asia.

      The user has not received any additional blocks on the account and is therefore tentatively eligible for Standard Offer consideration. Thanks, Nakon 01:23, 9 January 2016 (UTC)[reply]

      • There were issues concerning Bazaan and his or her socks other then sockpuppetry itself, which the editor doesn't mention. Search on "Bazaan" in the noticeboard files. I'd like to hear what the editor has to say about that behavior. BMK (talk) 01:52, 9 January 2016 (UTC)[reply]
      • I've modified Bazaan's block to permit him to edit his talk page: if we're willing to consider unblocking someone, the situation isn't so bad that talk access should remain disabled, and it's easier if the user can post messages on his own talk page instead of relying on UTRS assistance. Nakon, would you mind sending Bazaan an email asking him to make further replies on his talk page? Nyttend (talk) 02:31, 9 January 2016 (UTC)[reply]
        I've sent User:Bazaan an email update regarding their talk page. Thanks, Nakon 02:34, 9 January 2016 (UTC)[reply]
      • Apart from the sockpuppetry, there was some copyright issues way, way back. Is there anything else, from a content perspective, that would merit a conditional unblock? By which I mean, an "unblock conditional on an acceptance of a topic ban in articles relating to XYZ." Blackmane (talk) 06:01, 9 January 2016 (UTC)[reply]
      • Comment - I may be unusually strict, but I oppose any sort of standard offer when there has been SOCK|sockpuppetry/ I don't think that anyone who has engaged in sockpuppetry can be trusted at their end, at least not until the twenty-second century. That is my opinion. It just reflects a distinction between editors who make mistakes and editors who choose to game the system. I know that other editors are more forgiving than I am, and I am very forgiving of flaming, but not of sockpuppetryl Robert McClenon (talk) 06:48, 9 January 2016 (UTC)[reply]

      Review of EEng's indefinite block

      I think a review of EEng's indefinite block by Nakon is needed. I know EEng and although I acknowledge that his sense of humour is not everyone's cup of tea, I also know that it cannot possibly be the reason for an indefinite block. The block was placed without prior warning with a rationale of NOTHERE with talkpage/email access removed initially, then restored after a complaint by another editor. Also EEng's user and talk pages were blanked. These actions that are rather strong and unwarranted in this case concerning an editor in good standing. Various editors have talked to Nakon, including myself, but s/he currently appears to have stopped editing. Consequently, I am requesting a review of the block. In an attempt to minimise drama I am requesting the review here rather than ANI. Thank you. Dr. K. 06:11, 9 January 2016 (UTC)[reply]

      Yes, it was a mistake. But let's give Nakon at least a few minutes to reverse himself, and give Drmies a few minutes to chime in here... "Cowboy unblocks" of other Admins' blocks is one of the more vexing issues we've had to deal with lately, and let's not add this one to the pile... --IJBall (contribstalk) 06:19, 9 January 2016 (UTC)[reply]
      While I agree that caution is needed for any action, I don't think reversing this faulty block asap qualifies as a cowboy unblock. Also Nakon appears to be offline currently. Dr. K. 06:25, 9 January 2016 (UTC)[reply]
      Generally we give a reasonable amount of time for the blocking administrator to explain their position. EEng seems to be offline right now too. HighInBC 06:25, 9 January 2016 (UTC)[reply]
      When I wrote the above I had not realized that the blocking admin has already explained their position on their talk page. HighInBC 06:55, 9 January 2016 (UTC)[reply]
      Drmies seems offline right now as well. --IJBall (contribstalk) 06:31, 9 January 2016 (UTC)[reply]
      Generally, I would agree. But this block is extraordinarily bad. In any case, I don't wish to rush anyone. This is just my opinion. Dr. K. 06:28, 9 January 2016 (UTC)[reply]
      No – the blocking Admin should be the one to undo their mistakes. This is exactly the problem we have right now – Admins stepping all over each other, which is just leading to bad feelings. If EEng is owed an apology, I fully expect one will be forthcoming shortly. Let the process play out. --IJBall (contribstalk) 06:31, 9 January 2016 (UTC)[reply]
      (edit conflict) Ideally, I agree that the blocking admin should undo their mistake. But this should be done in a reasonable amount of time. If that time is exceeded, someone else has to step in and reverse the block. Dr. K. 06:39, 9 January 2016 (UTC)[reply]
      A "reasonable amount of time" is measured in hours (on Wikipedia), not minutes or seconds. Currently, it looks like the 3 main parties to this are offline. The place isn't on fire, so there's no need to rush. --IJBall (contribstalk) 06:42, 9 January 2016 (UTC)[reply]
      Did I say I wanted this resolved in minutes or seconds? Or that I wanted to rush this? In fact, just above I explicitly mentioned that I don't wish to rush anyone. Dr. K. 06:48, 9 January 2016 (UTC)[reply]
      I think there must be more involved. A bit of snarky behaviour deserves a trouting at best. HighInBC 06:51, 9 January 2016 (UTC)[reply]

      What is the background to this block? Is it purely from this discussion? -- Ricky81682 (talk) 06:44, 9 January 2016 (UTC)[reply]

      • I'm still assuming a misunderstanding here. At the least, Nakon should have the opportunity to explain/defend his actions. I've dealt with Nakon enough to believe that this has just got to be an mistake... --IJBall (contribstalk) 07:04, 9 January 2016 (UTC)[reply]