Jump to content

Wikipedia:Administrators' noticeboard: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Dualus (talk | contribs)
Line 334: Line 334:


Could someone please take a look at [[Wikipedia_talk:WikiProject_Color#RfC:_.22Shades_of_red.22_vs_.22Variations_of_red.22_or_.22Tones_of_red.22.3F|the RfC regarding names a few color-related articles]]. The RfC is over 30 days old and needs to be closed one way or another. Or perhaps changed into a request for move. Thanks. --[[User:Noleander|Noleander]] ([[User talk:Noleander|talk]]) 12:37, 6 November 2011 (UTC)
Could someone please take a look at [[Wikipedia_talk:WikiProject_Color#RfC:_.22Shades_of_red.22_vs_.22Variations_of_red.22_or_.22Tones_of_red.22.3F|the RfC regarding names a few color-related articles]]. The RfC is over 30 days old and needs to be closed one way or another. Or perhaps changed into a request for move. Thanks. --[[User:Noleander|Noleander]] ([[User talk:Noleander|talk]]) 12:37, 6 November 2011 (UTC)

== RfC summary update ==
I would like to [http://en.wikipedia.org/w/index.php?title=Template_talk:Health_care_reform_in_the_United_States&diff=459381116&oldid=459355551 reverse this] deletion of updates and clarifications I made to an RfC header, but I have been accused of disruptive editing so I am asking that an administrator revert that instead, please. [[User:Dualus|Dualus]] ([[User talk:Dualus|talk]]) 00:55, 7 November 2011 (UTC)

Revision as of 00:55, 7 November 2011

    Welcome — post issues of interest to administrators.

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

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

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

    Template:Active editnotice


      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

      (Initiated 18 days ago on 18 October 2024) This shouldn't have been archived by a bot without closure. Heartfox (talk) 02:55, 3 November 2024 (UTC)[reply]

      @Heartfox: The page is archived by lowercase sigmabot III (talk · contribs), which gets its configuration frum the {{User:MiszaBot/config}} at the top of Wikipedia:Administrators' noticeboard. Crucially, this has the parameter |algo=old(7d) which means that any thread with no comments for seven days is eligible for archiving. At the time that the IBAN appeal thread was archived, the time was 00:00, 2 November 2024 - seven days back from that is 00:00, 26 October 2024, and the most recent comment to the thread concerned was made at 22:50, 25 October 2024 (UTC). This was more than seven days earlier: the archiving was carried out correctly. --Redrose64 🌹 (talk) 22:16, 3 November 2024 (UTC)[reply]
      There was no need for this because archived threads can be closed too. It is not necessary for them to remain on noticeboard. Capitals00 (talk) 03:28, 4 November 2024 (UTC)[reply]

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

      Requests for comment

      (Initiated 87 days ago on 9 August 2024)

      Wikipedia talk:Notability (species)#Proposal to adopt this guideline is WP:PROPOSAL for a new WP:SNG. The discussion currently stands at 503 comments from 78 editors or 1.8 tomats of text, so please accept the hot beverage of your choice ☕️ and settle in to read for a while. WhatamIdoing (talk) 22:22, 9 September 2024 (UTC)[reply]

      (Initiated 46 days ago on 19 September 2024) Legobot removed the RFC template on 20/10/2024. Discussoin has slowed. Can we please have a independent close. TarnishedPathtalk 23:11, 24 October 2024 (UTC)[reply]

       Doing... I've read the whole discussion, but this one is complex enough that I need to digest it and reread it later now that I have a clear framing of all the issues in my mind. Ideally, I'll close this sometime this week. Compassionate727 (T·C) 20:23, 27 October 2024 (UTC)[reply]
      Thanks. This issue has been going on in various discussions on the talk page for a while so there is no rush. TarnishedPathtalk 03:26, 29 October 2024 (UTC)[reply]

      (Initiated 37 days ago on 28 September 2024) Discussion has died down and last vote was over a week ago. CNC (talk) 17:31, 2 November 2024 (UTC)[reply]

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

      Deletion discussions

      XFD backlog
      V Aug Sep Oct Nov Total
      CfD 0 0 0 0 0
      TfD 0 0 7 0 7
      MfD 0 0 1 0 1
      FfD 0 0 2 0 2
      RfD 0 0 44 0 44
      AfD 0 0 8 0 8

      (Initiated 49 days ago on 16 September 2024) No new comments in the last week or two. Frietjes (talk) 15:26, 4 November 2024 (UTC)[reply]

      (Initiated 37 days ago on 28 September 2024) No new comments in the last week or two. Frietjes (talk) 15:25, 4 November 2024 (UTC)[reply]

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

      Other types of closing requests

      (Initiated 293 days ago on 16 January 2024) It would be helpful for an uninvolved editor to close this discussion on a merge from Feminist art to Feminist art movement; there have been no new comments in more than 2 months. Klbrain (talk) 13:52, 4 November 2024 (UTC)[reply]

      (Initiated 195 days ago on 23 April 2024) Opened for more than six months now, no new comments. CarmenEsparzaAmoux (talk) 06:27, 31 October 2024 (UTC)[reply]

      I believe this discussion is too stale, especially given how half of voters picked "wait." I think that if somebody wants to merge this article, they should feel free to boldly undertake it, or if they'd rather clarify things, start a fresh discussion on the talk page of one of the proposed parents. I'll leave this open in case another closer feels differently, though. Compassionate727 (T·C) 14:55, 2 November 2024 (UTC)[reply]
       Closed. P.I. Ellsworth , ed. put'er there 05:26, 4 November 2024 (UTC)[reply]

      (Initiated 161 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]

       Doing...— Frostly (talk) 22:35, 17 July 2024 (UTC)[reply]
      @Frostly Are you still planning on doing this? Soni (talk) 16:57, 22 July 2024 (UTC)[reply]
      Soni, yes - have drafted close and will post by the end of today. Thanks! — Frostly (talk) 17:56, 23 July 2024 (UTC)[reply]
      I wanted to note that this is taking slightly longer than expected, but it is at the top of my priority and will be completed soon. — Frostly (talk) 05:14, 27 July 2024 (UTC)[reply]
      @Frostly Just checking, would you like someone else to help with this? Soni (talk) 07:31, 11 August 2024 (UTC)[reply]
      @Frostly: also checking in. voorts (talk/contributions) 00:33, 22 August 2024 (UTC)[reply]
      Hi Voorts and Soni, thanks for the pings! I've unfortunately been in the hospital for the past week but am now feeling better. I apologize for the long delay in putting out the close and appreciate your messages! Best, — Frostly (talk) 03:59, 22 August 2024 (UTC)[reply]
      I'm sorry to hear that; a week-long hospitalization is not fun. But, I'm glad that you're feeling better. Best, voorts (talk/contributions) 19:06, 22 August 2024 (UTC)[reply]
      Ping @Frostly again (I saw you've been editing Commons). Hope your still better, and if you don't feel like doing this one anymore, just let people know. Gråbergs Gråa Sång (talk) 17:02, 3 September 2024 (UTC)[reply]
      Archived. P.I. Ellsworth , ed. put'er there 13:32, 24 July 2024 (UTC)[reply]
      Just a note here that Frostly has not edited in over a month. Might be best for someone else to close. --Super Goku V (talk) 07:45, 3 October 2024 (UTC)[reply]
      • I can't touch that cos I !voted, but although that was a productive and thought-provoking discussion, it's not a discussion that has an actionable outcome. I personally feel it can lie in the archives unclosed.—S Marshall T/C 11:36, 3 October 2024 (UTC)[reply]
      • This isn't a priority given S Marshall's input, but I'll save it for offline reading. If I have time while I'm in Cuba next week, I'll take a look at it and see if I can't summarize some of the broader points and ideas potentially worth pursuing. Compassionate727 (T·C) 23:27, 15 October 2024 (UTC)[reply]
        Sorry, I haven’t accomplished anything on this. I couldn’t find a way to save a readable copy of the discussion to my iPad, and the government of Cuba has disabled the Internet nationwide to suppress news of the ongoing blackout. Compassionate727 (T·C) 22:46, 25 October 2024 (UTC)[reply]
      • Thanks for the notes @Gråbergs Gråa Sång, @Super Goku V, @Compassionate727, and I appreciate your input @S Marshall! Sorry for not getting to this earlier; I've had some unexpected personal commitments that have taken up most of my bandwidth. Given that it looks like this would be left best as an unclosed discussion, I'll mark this request as resolved for now ( Not done). Frostly (talk) 03:35, 4 November 2024 (UTC)[reply]
        @Frostly and Compassionate727: Personally, I think it would be useful to try to discern some sort of conclusion from it, if only to provide editors some level of guidance as to how to respond to future notifications in that form.
        I’ve marked it for not done for now, to prevent it being auto archived before this comment can be read, but if you’re confident closing it won’t be useful I won’t object to remarking it as done. BilledMammal (talk) 04:29, 4 November 2024 (UTC)[reply]

      (Initiated 32 days ago on 3 October 2024) No new comments in a bit over three weeks. Can we get an independent close please. TarnishedPathtalk 13:25, 4 November 2024 (UTC)[reply]

      (Initiated 10 days ago on 26 October 2024) Request an admin or very confident closer sorts this out. Controversial subject, and although consensus may be found, it is also necessary to close an out of process AfD now started [[1]] that was started to confirm the merge discussion. Thanks. Sirfurboy🏄 (talk) 07:40, 4 November 2024 (UTC)[reply]

      It's a messy situation, but I argue that the most logical thing to do now is treat this as a deletion discussion, to be evaluated at AfD (ignoring the filer's framing as a merge discussion). — xDanielx T/C\R 15:50, 4 November 2024 (UTC)[reply]

      (Initiated 4 days ago on 31 October 2024) Discussion only occurred on the day of proposal, and since then no further argument has been made. I don't think this discussion is going anywhere, so a close may be in order here. Wolverine X-eye (talk to me) 07:03, 4 November 2024 (UTC)[reply]

      I'm reluctant to close this so soon. Merge proposals often drag on for months, and sometimes will receive comments from new participants only everything couple weeks. I think it's too early to say whether a consensus will emerge. Compassionate727 (T·C) 14:52, 4 November 2024 (UTC)[reply]
      @Compassionate727: OK, so what are you suggesting? Will the discussion remain open if no further comments are received in, say, two weeks? I also doubt that merge discussions take months to conclude. I think that such discussions should take no more than 20 days, unless it's of course, a very contentious topic, which is not the case here. Taken that you've shown interest in this request, you should be able to tell that no form of consensus has taken place, so I think you can let it sit for a while to see if additional comments come in before inevitably closing it. I mean, there is no use in continuing a discussion that hasn't progressed in weeks. Wolverine X-eye (talk to me) 15:52, 4 November 2024 (UTC)[reply]
      @Wolverine X-eye, I don't think thats what they are saying. Like RfC's, any proposals should be opened for more than 7 days. This one has only been open for 4 days. This doesn't give enough time to get enough WP:CONSENSUS on the merge, even if everyone agreed to it. Cowboygilbert - (talk) ♥ 21:24, 4 November 2024 (UTC)[reply]

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

      Village pump (proposals) closures needed

      Would an admin (or admins) close Wikipedia:Village pump (proposals)#RfC: Structure WP:WQA conversations and Wikipedia:Village pump (proposals)#Remove ability for new users to create other accounts? Both discussions were listed at Template:Centralized discussion and delisted to Wikipedia:Centralized discussion/Archive owing to inactivity. Thanks, Cunard (talk) 10:14, 25 September 2011 (UTC)[reply]

      Thank you, DeltaQuad (talk · contribs), for closing the WQA RfC. Cunard (talk) 05:54, 27 September 2011 (UTC)[reply]

      Future timestamp to prevent archiving. Cunard (talk) 23:59, 22 September 2011 (UTC)[reply]

       Done Closed the Account creation one also, changed timestamp to today. -- DQ (t) (e) 17:04, 22 October 2011 (UTC)[reply]
      Thank you, DQ, for closing and summarizing this lengthy debate. Cunard (talk) 22:40, 22 October 2011 (UTC)[reply]

      Bugzilla request to enact the consensus found in this closure

      Would an admin or editor who is experienced with Bugzilla file a request to enact the consensus found in this closure? Please provide a link to the Bugzilla request at the Village Pump as a postscript to DQ's closure. Thank you, Cunard (talk) 22:44, 22 October 2011 (UTC)[reply]

      Future timestamp to prevent archiving. Cunard (talk) 22:44, 22 October 2012 (UTC)[reply]

      Unblock discussion User:Kci357

      User:Kci357 (edit | talk | history | links | watch | logs)

      Well over a month ago, Kci357 contacted me asking about an unblock. Since then, I have been in discussion with him, and I did explain that I couldn't simply unblock him, but I did talk to him about what he could do to receive an unblock. In my talking to him, I do believe he is sincere about wanting to contribute constructively if he is unblocked. I have the following points to mention:

      1. Kci357 has told me that there will not be any socking.
      2. He has promised not to edit-war, and instead, he will discuss in future.
      3. He knows that there will be plenty of people watching him if he does slip, and another chance after another block is very, very unlikely.
      4. I e-mailed the original blocking admin, Fox, and he is okay with an unblock. However, since Kci357 has had unblock requests declined since then, I've contacted a couple of the admins declining those requests rather than overrule them.
      5. There hasn't been any strong agreement with those admins to unblock or keep blocked, so now I'm starting a discussion here, with Kci357 being okay with me doing that.

      Personally, I don't see the harm in giving Kci357 a second chance. If he immediately goes back to the behavior that got him blocked, he will just be reblocked, and I will be very disappointed after the all discussion I had with him. If he is unblocked, keeps his promises, and edits constructively, then a positive outcome will have been achieved. Acalamari 10:53, 1 November 2011 (UTC)[reply]

      Acalamari did contact me, as one of the admins who had declined an unblock. To me, the editor just didn't get it. It was so bad, that his talkpage access was removed. Apparently, it was restored to allow the editor to, in his own words, make his unblock request - which he has not done. Although I WP:AGF, if the editor cannot follow WP:GAB, cannot express his own request sincerely, cannot show that they recognize their behaviours that led to the block (and later talkpage locking), and relies on others to express these things on their behalf, I'm not sure that the editor has either the sincerety nor WP:COMPETENCE to edit Wikipedia. (talk→ BWilkins ←track) 13:12, 1 November 2011 (UTC)[reply]
      • To be honest, I would say the odds of this working out are almost zero, and I wouldn't unblock myself. However, in cases where there is no consensus either way among the declining admins, I strongly feel that the default should be to unblock, not leave blocked. I don't see any irreparable harm in deferring to Acalamari's judgement and giving it a try.

        Assuming that the sock tag on his user page is correct (and behavioral evidence leads me to think it is), you should also make it a condition for unblocking that he not abuse the reference desks. Needs to be on his absolute best behavior every edit he makes, though. --Floquenbeam (talk) 13:34, 1 November 2011 (UTC)[reply]

      • I'm inclined to agree with BWilkins on this. If the user is not sufficiently competent to explain for themselves why they should be unblocked and must resort to doing it by proxy I can't see any benefit to unblocking them. A look at the few edits they have made on their talk page since access was restored re-affirms that feeling. Beeblebrox (talk) 16:12, 1 November 2011 (UTC)[reply]
      • Floquenbeam says above "I don't see any irreparable harm in deferring to Acalamari's judgement and giving it a try" and that's pretty much how I see it as well. Let's give him a shot, and if it doesn't work out, it's simple enough to reblock. 28bytes (talk) 16:41, 1 November 2011 (UTC)[reply]
        • I do accept the concerns here, especially given Kci357's short editing history, talk page, and blocks (I'd have no problem with a condition in an unblock for him to keep away from the reference desks, too). I thought of all that myself, but then I thought again that in cases like this, the unblocked editor is always watched, and with one wrong move they're blocked again. It goes without saying that I'll be someone watching him.
        • As for Kci357 not requesting the unblock himself, he contacted me just before the time his talk page was unblocked, and I think the reason he has not requested anymore unblocks is because of him discussing his block with me (I also told him that I would do the contacting, as I have done). If anything, I consider it a good thing he hasn't posted more unblocks, but that's just me.
        • Assuming he is unblocked, it would be very embarrassing for me and an error to have helped if Kci357 did get himself reblocked, but again, I'm hoping he won't do that. Acalamari 17:17, 1 November 2011 (UTC)[reply]
      @Acalamari: giving an editor a chance is a worthy goal, and should not result in your embarrassment no matter the outcome. There is just no way to get a realistic vibe from someone typing. It's hard enough to do it in person and humans are much better at that than constrained mediums like this.
      I say unblock him, and reblock on the first significant violation. Lesser violations like etiquette and guideline confusion can be ignored or for any interested editor to educate. He has been warned adequately. It should be quickly apparent if he will be a benefit to Wikipedia or a time waster. —EncMstr (talk) 20:51, 1 November 2011 (UTC)[reply]

      Unarchiving as this was archived without resolution. 28bytes (talk) 14:11, 4 November 2011 (UTC)[reply]

      • Support unblock on the basis of a rope.
      • If he is found socking, then a week-long block should do; if a second sock is later found, indef block.
      • If he engages in an edit war, he will be warned the first time, but blocked immediately for a short duration the second time.
      • If unblocked, they must display competence and cooperate. If a similar situation arises again, instant-indef block.

      HurricaneFan25 14:23, 4 November 2011 (UTC)[reply]

      I certainly wouldn't quite agree to that pattern of blocking. A new sock? Indef, done, finit. Edit-warring would typically continue a pattern of escalation, as required. It's admin's reading of the situation (talk→ BWilkins ←track) 22:26, 4 November 2011 (UTC)[reply]
      No comment on the unblock request but just as a note, this user's problems stretch back further then the Kj650 account. They are the same as Thekiller35789 and had a whole host of other identites which were never blocked, they tended to give up on accounts after they got enough complaints and another easily recognisable account would appear. They were annoying on the RD, but the far bigger problem was their tendency to remove source info or add stuff to articles without sources, apparently to better reflect theirPOV. However for a while, it was low level enough that those of us who recognised it couldn't really be bothered persuing it. Nil Einne (talk) 18:04, 5 November 2011 (UTC)[reply]


      • As an RD semi-regular (lurking if not posting), I agree with Nil Einne's points. I tried to interact and guide some of the user behind Kci357's other accounts, receiving one reply to a questioned, unjustified removal of article content. To the best of my knowledge, I can't remember any other successful interaction attempts, which has left me with a rather low opinion of the user in question. Some of the accounts were quite sharp in their interactions with people who undid the unexplained (and very messy - sentences left hanging, words chopped in half) deletions of article content. The user had a habit of posting an unusual mixture of questions about carpentry, building codes and internet gore videos on the ref desk, and never seemed satisfied with the response, continually asking for clarification when a clear and concise answer had already been given. It has been demonstrated time and time again that this user is not interested in engaging with others, taking care in their edits to the mainspace or being beneficial to this project in any way. He's been given enough rope in the past to rig a man-o'-war. I don't think any benefit will come from an unblock, but if the problematic behaviour returns then a swift – and final – indef has all the justification it needs. Brammers (talk/c) 23:07, 5 November 2011 (UTC)[reply]

      Help urgently needed on unblock-en-l - barnstars available

      Who wants to earn some barnstars?

      The unblock request mailing list, unblock-en-l@lists.wikimedia.org , is around for blocked users to appeal blocks when they do not know how or are unable to do so on-wiki. Unfortunately, and despite the fact that there are over 100 people subscribed to this list and receiving email from it, I am handling the vast majority of the requests this list receives completely by myself. It's been this way for a few weeks, before which User:DeltaQuad was the only one actively reviewing appeals. In short, we really really really need some help!

      If you are not subscribed to this list and would like to assist with reviewing block appeals, please go to https://lists.wikimedia.org/mailman/listinfo/unblock-en-l and sign up. Why should you do so? Many of the people emailing us are trying to edit Wikipedia for the first time, but are unable to due to a rangeblock or autoblock on their IP address. By reviewing these appeals in a timely manner, you're helping new editors get started on Wikipedia. Furthermore, there's an added incentive for you...

      For the remainder of the month of November, I am offering an Admin's Barnstar to anyone who handles at least 15 appeals send to this list. It may sound like a lot, but this list often receives more than a dozen appeals each day, so you're sure to get there quickly if you check your email regularly. Furthermore, the three admins other than myself who respond to the most appeals for the remainder of November will receive Bronze, Silver, and Gold Wiki Awards for their exceptional service. Fine print follows my signature.

      If you want to help but aren't sure how, don't worry - subscribe and stick around for a bit. You'll find a lot of the emails we send are boilerplate text that you can copy from previous responses and then edit as needed. So sign up and help today! Hersfold (t/a/c) 00:24, 5 November 2011 (UTC)[reply]

      Fine print: In order to receive credit towards either award, any response you send must be cc'd to the unblock mailing list per standard procedure. Each admin may only get credit once per appealing user; i.e., if you respond to an appeal asking for more information, you don't get credit for two appeals by responding again when they user sends the information you need. Also, except where replies are sent within a few minutes of each other, only the first admin to respond to a given stage of an appeal gets credit; i.e., if Admin A responds to a user's request, then Admin B sends another response an hour later, only Admin A is going to get credit because it had already been dealt with. List-only emails do not receive credit. You receive credit just for sending a useful response; you need not unblock (or decline to unblock) a user. Currently subscribed users are also eligible provided they actually start helping like DQ and I have been asking them to do for weeks :-P.

      EDIT I will also back this up with my Sectional Dedication Award for anyone who handles 20 in a month (from beginning to end of the month in question) on the same terms that Hersfold is using above. -- DQ (t) (e) 18:15, 5 November 2011 (UTC)[reply]
      I actually have to echo this request, because the situation hasn't gotten better since I started to go on wikibreak. (And I don't have the tools anymore, so my help is sometimes not enough) I see unblock requests on wiki dealt with in hours, where as just later yesterday (and no pressure on Hersfold here) I saw a backlog of about 15-20 emails that had not been responded to in 4 days. This is really shocking personally that there is such a backlog. As Newyorkbard echoed just a while ago on ANI, this list needs attention, and we have gotten new members, but very few have stepped up for the few emails that have been handled by others. I have a statistical document that I have upload that shows just how bad things are getting. This file is not 100% accurate, but add or subtract a bit of salt to these numbers and they should be fine. Also note the last page is not specifically unblock-en-l requests, but all emails (not that the numbers would be affected much without). Some of the ridiculous statistics include:
      • In october, there were 34 requests that took over a week to respond to. (That's from when I started to take a break from the list)
      • ~21% of requests are taking over 3 days to get responses.
      • Since May 19th, 157 requests have been left not responded to.
      Please any admins who can help at this time, we need you! Not sure how to start replying to emails? use the templates. -- DQ (t) (e) 14:09, 5 November 2011 (UTC)[reply]

      Also note the cross-thread @ ANI. -- DQ (t) (e)

      Doesn't this use respondent's own email addresses? I'd be a lot more willing if it was an OTRS queue, because my email address isn;t necessarily something I want to give out to blocked users. HJ Mitchell | Penny for your thoughts? 14:29, 5 November 2011 (UTC)[reply]
      Is there some reason {{unblock}} can not be used on these requests? Jeepday (talk) 14:41, 5 November 2011 (UTC)[reply]
      Like he said, some people don't read the instructions, or don't understand them, or are caught in rangeblocks that they don't get ... and then there are those whose talkpages get locked due to abuse of the process (talk→ BWilkins ←track) 14:53, 5 November 2011 (UTC)[reply]
      @HJ Mitchell: Yes, it does, and were trying to get an interface going but the programming only started just recently, and people still have day to day lives. The problem is the the Foundation (well Legal more directly) has turned down an OTRS queue (and they've been asked a few times) because of the privacy policy and retention of data policies, because the list contains IP addresses.
      @Jeepday: You would have to tell that to the users making the requests...but Bwilkins is right + again special security measures for a user that is caught in a hardblock, needing an IPBE, but doesn't want to post their IP, or most often of what we get, autoblocks or anon-vandal blocks (collateral damage) asking for accounts. -- DQ (t) (e) 17:11, 5 November 2011 (UTC)[reply]
      Tell me how I can help with the interface. --Shirik (Questions or Comments?) 18:01, 5 November 2011 (UTC)[reply]
      I'll get you on the list and give you an update when Hersfold rolls in tonight. (Or sooner if I figure out a few things) :) -- DQ (t) (e) 18:15, 5 November 2011 (UTC)[reply]
      I won't be properly online until tomorrow, but the first requirement for helping with the interface is a toolserver account, and a basic knowledge of one or more of the following: PHP, HTML, CSS, SQL. If you aren't familiar with any of these languages, we can still use beta testers (later on), and you won't need an account for that. :-) Once you have a toolserver account, send me or DQ a note and we'll get you in. Hersfold (t/a/c) 05:48, 6 November 2011 (UTC)[reply]

      Closure Required

      A discussion about Chesdovi and Debresser just archived for a second time. Significant enough progress was made in the "moving forward" that I believe someone would be able to step in a close the discussion. I personally do not wish to de-archive myself, and was hoping some wise (or otherwise) soul would determine consensus, and enact the fair proposals. (talk→ BWilkins ←track) 08:51, 5 November 2011 (UTC)[reply]

      I'm working on this close. Gwen Gale (talk) 20:23, 5 November 2011 (UTC)[reply]

      Re-creation of previously deleted page

      Blackwater_(novel) was just recently created by someone, but it appeared on my watchlist, so it's been deleted before. Could an admin please check the history to see if the re-creation is legit and not/act accordingly? Thanks. → ROUX  09:30, 5 November 2011 (UTC)[reply]

      It's a different book. The previous one was apparently by C. D. Blizzard. Often in the case of G4 the most informative thing to do is to simply find the previous AfD from what links here. -- zzuuzz (talk) 09:49, 5 November 2011 (UTC)[reply]
      ...and either way, this one has an award, which likely improves notability (talk→ BWilkins ←track) 09:51, 5 November 2011 (UTC)[reply]

      Shouldn't this be closed by an administrator? ASCIIn2Bme (talk) 09:53, 5 November 2011 (UTC)[reply]

      Um, see two threads above this ... (talk→ BWilkins ←track) 10:11, 5 November 2011 (UTC)[reply]

      Expired PRODs

      Noonvale, Bloodwrath, Conqueror's Quest, Sword of Martin, Tears of All Oceans and Silvamord have all gone 7 uncontested days at prod. Can someone delete these? Ten Pound Hammer(What did I screw up now?) 17:37, 5 November 2011 (UTC)[reply]

       Done for all except Conqueror's Quest, which you'll need to take to AfD. 28bytes (talk) 19:44, 5 November 2011 (UTC)[reply]
      There's a lot more. 55, to be exact. — Train2104 (talk • contribs • count) 19:46, 5 November 2011 (UTC)[reply]
      this sort of backlog at that process is rarely much of an emergency. DGG ( talk ) 00:49, 6 November 2011 (UTC)[reply]

      Problem with WP:V watchlist msg

      Any Admin available to look at this please? [2] Leaky Caldron 18:20, 5 November 2011 (UTC)[reply]

      This should be fairly straightforward, has it just been overlooked? Leaky Caldron 11:50, 6 November 2011 (UTC)[reply]

       Done. Cheers. Salvio Let's talk about it! 12:16, 6 November 2011 (UTC)[reply]

      I have no idea why this has been salted blacklisted, but please create this page for me. I created the article today without any problems: Michael Hishikushitja, and I would like to nominate it for T:TDYK. Thanks a lot, Pgallert (talk) 19:11, 5 November 2011 (UTC)[reply]

       Done. 28bytes (talk) 19:28, 5 November 2011 (UTC)[reply]

      Delete userbox

      http://en.wikipedia.org/wiki/User:Joyson_Noel/my_userboxes/Fernandes_Prabhu_Moodubelle

      Joyson Noel Holla at me! 19:31, 5 November 2011 (UTC)[reply]

       Done. 28bytes (talk) 19:33, 5 November 2011 (UTC)[reply]

      Jesse Dirkhising

      I don't know where else to ask this so I'll ask it here. The image of Jesse Dirkhising was deleted without an explanation. Nothing on the talk page of Murder of Jesse Dirkhising mentions it. I left a post on the talk page but recieved no response. I have no idea as to why it was deleted because I see no discussion in regards to it being up for deletion. Can someone tell me why it was removed or who nominated it to be taken down? Why was Jesse Dirkhising's picture deleted and not those of Matthew Shepard and Larry King? Why keep two but not three? I'd like to see the image of Jesse restored. Caden cool 20:57, 5 November 2011 (UTC)[reply]

      The image removal bot left an edit summary linking to the deleted image, which mentions Wikipedia:Files for deletion/2011 July 17#File:JesseDirkhising.jpg in the deletion log. --OnoremDil 21:03, 5 November 2011 (UTC)[reply]
      Thank you but I don't see consensus for it being deleted? I don't understand it. Caden cool 21:09, 5 November 2011 (UTC)[reply]
      This File:Matthew Shepard.jpg and this File:LawrenceFobesKing.jpg are not free images. Why keep these images and not Jesse's? Something is wrong here. Caden cool 21:23, 5 November 2011 (UTC)[reply]
      I don't know...because the nominator missed them? --OnoremDil 21:28, 5 November 2011 (UTC)[reply]
      I doubt that. Something else is going on. Caden cool 21:32, 5 November 2011 (UTC)[reply]
      (e/c with Onorem and Caden) If you want to challenge the deletion, the correct forum is deletion review. Alternatively, if you want to start a community discussion about the use of non-free images of people who are deceased, you may want to consider starting a discussion at WP:VP/P. I do see the inconsistency here and, frankly, I believe that images of deceased people, in articles about them or about their deaths, has long been accepted fair use on Wikipedia. --Philosopher Let us reason together. 21:38, 5 November 2011 (UTC)[reply]
      Thanks. I didn't know about WP:VP or deletion review. Caden cool 22:51, 5 November 2011 (UTC)[reply]

      I have tried unsuccessfully to engage in conversation with the nominator User:SchuminWeb (an admin no less) who deleted the image. I tried here [3] and here [4] and all I got was this [5]. That's unacceptable behavior from an admin to refuse to explain what appears to me as a double standard. He has no problem keeping non-free images of Shepard and King but found it necessary to delete Dirkhising? He and his actions make no sense. It's a double standard and it's plain wrong. Caden cool 00:42, 6 November 2011 (UTC)[reply]

      SchuminWeb did not delete the image. The image was was deleted by Fastily. If you disagree with the close of the discussion you should discuss it with the admin who deleted the file. If you are not satisfied with the outcome there, the next step is asking for it to be reviewed at WP:DRV. There are files and articles that are deleted while similar files/articles are kept. This is a byproduct of the way wikipedia is set up with discussions and different editors taking part in different discussions. It is not necessarily a double standard by any editor. GB fan 01:29, 6 November 2011 (UTC)[reply]

      I don't have a strong opinion on the matter but clarification is always good, thus Wikipedia talk:Non-free content#RFC: Clarifying policy on pictures of deceased persons. Herostratus (talk) 02:45, 6 November 2011 (UTC)[reply]

      @GB Fan. Okay so Fastily deleted it. Well although I disagree with his closure when there was no consensus to do that, I'm unable to do anything about it. We bumped heads about a year ago over his mass deletion of images and he told me to never contact him again. So the option to communicate is impossible. In regards to the main topic, I still see a double standard practice. I asked multiple times as to why Shepard and King's non-free images remain and I have yet to be given a realistic explanation. @Herostratus. I do agree that clarification is good and that was what I was asking for but in this case I don't feel that SchuminWeb was willing to do that. Instead he decided to ignore me on his talk page. Not good at all when he's the admin who nominated the image of Jesse Dirkhising for deletion in the first place. Had I read his talk page in the first place I wouldn't have bothered contacting him to begin with. Two editors questioned his abuse of power on his talk page. Had I seen that I would never have bothered to contact him. Caden cool 20:39, 6 November 2011 (UTC)[reply]
      So then the next step is WP:DRV. It isn't here and it isn't at WP:REFUND. GB fan 22:54, 6 November 2011 (UTC)[reply]
      Never heard of either and honestly I wouldn't know how to do that. Even if I did I would be accused of forum shopping. Funny how all the rules on wiki are quite literally set up as one road block after another. Caden cool 23:09, 6 November 2011 (UTC)[reply]
      You would certainly not be accused of forum-shopping if you took a disputed deletion to WP:DRV, because that's exactly the right place to take it. Black Kite (t) 23:40, 6 November 2011 (UTC)[reply]
      Maybe you don't recognize the shortcut WP:REFUND, but you have posted there asking for this file to be undeleted. But as that page states it is not for anything that is deleted do to a discussion. No one should say you are forum shopping by going to deletion review to have a deletion that you disagree with reviewed. GB fan 23:48, 6 November 2011 (UTC)[reply]
      I filed for undeletion thingy yesterday and as yall know I also came here to the noticeboard and I attempted to communicate with the nominee on his talk page, so even if I understood how to file a DRV, I'd be accused of forum shopping. Caden cool 23:56, 6 November 2011 (UTC)[reply]
      No, you wouldn't. In fact, DRV suggests that you contact the closing admin first, so you've already done that. Filing a DRV isn't actually that difficult; I will post on your talkpage. Black Kite (t) 23:59, 6 November 2011 (UTC)[reply]
      Okay thanks Kite. Caden cool 00:01, 7 November 2011 (UTC)[reply]

      More stuff to delete

      Category:Redwall characters. At CFD for 7 days with consensus to upmerge. I've already done this, so the category can be safely deleted. Also, Category:Redwall locations is now empty, so it can be flushed via G6. Ten Pound Hammer(What did I screw up now?) 21:57, 5 November 2011 (UTC)[reply]

      Overdue RfC

      There's an RfC overdue for closure to do with astrology, here.

      Appreciate that an RfC being overdue is not necessarily something to panic about too much, but there is still some discussion and maybe a hint of edit-warring there which could potentially be stopped in its tracks.

      Thanks. --FormerIP (talk) 23:15, 5 November 2011 (UTC)[reply]

       Done --Jayron32 01:50, 6 November 2011 (UTC)[reply]

      User protecting own talkpage

      Saravask has protected their own talkpage to stop users leaving messages. Is this allowed? I was trying to leave a message regarding an orphaned image but could not do so. Cloudbound (talk) 01:39, 6 November 2011 (UTC)[reply]

      Left a note on their talk page--Jac16888 Talk 01:44, 6 November 2011 (UTC)[reply]
      Admins, more then anyone else, should never be allowed to have a fully protected talk page. Monty845 01:47, 6 November 2011 (UTC)[reply]
      Saravask has posted on his userpage that he's currently on vacation and won't be online. Perhaps this is simply an attempt to avoid people leaving messages that he won't be able to respond to? (Not the best way to handle it, but more understandable than it would be otherwise.) Newyorkbrad (talk) 01:49, 6 November 2011 (UTC)[reply]
      Saravask has been editing since protecting the page, and judging from some of the edit summaries, engaging in disputes. Disputes are an important reason communication channels like a user talk page should remain open. Monty845 01:52, 6 November 2011 (UTC)[reply]
      Hmmm. This is true. Newyorkbrad (talk) 01:56, 6 November 2011 (UTC)[reply]
      Thanks for your replies. Cloudbound (talk) 01:55, 6 November 2011 (UTC)[reply]
      I'd like to hear Saravask's explanation; he did take about 36 hours off of editing; maybe he just forgot to remove the protection when he became active again. Still, it doesn't look good, and I don't see where his user talk page was a target of vandalism even before his "vacation." --Jayron32 02:01, 6 November 2011 (UTC)[reply]

      Community Discussion of Topic Ban and Interaction Ban


      Request and protest

      A notification of unblocking and bans has been posted on my talkpage. Please see there that I ask to reconsider, that the ban should not include talkpages. Arguments there. See also my protest against an additional injunction against me in comparison with the injunctions against Chesdovi. Since the notification was posted on my talkpage, not here, I have replied on my talkpage, and kindly ask you to see there. Debresser (talk) 01:44, 6 November 2011 (UTC)[reply]

      I have moved this discussion back from the archives per Debresser (talk · contribs)'s contesting of the close. Cunard (talk) 03:35, 6 November 2011 (UTC)[reply]
      To the extent this is an appeal of a discretionary sanction, it must be appealed to WP:AE and not here. T. Canens (talk) 03:41, 6 November 2011 (UTC)[reply]
      I see. Thank you. In the mean time, all who care, please feel free to read the gist of my problem with this sanction on my talkpage. Debresser (talk) 07:37, 6 November 2011 (UTC)[reply]
      I'm pretty sure that protesting against a sanction preventing you from calling others "anti-semitic" by claiming that the restriction itself is anti-semitic was not the brightest thing you've ever done; however, as T.Canens says above, this is the wrong venue. Black Kite (t) 11:49, 6 November 2011 (UTC)[reply]
      It did appeal to my sense of humor. See also Jewish humour. And of symmetry. In any case, if I think it is true, I have a right to say it on talkpages. Restricting this right because I might (stress that, since I admit to no such thing) have misused the term once, is unjust. And I find that especially strange (and that is a very large understatement) in view of the fact that none of the proposals above included such a clause. Anyway, your interest in this case is appreciated. Debresser (talk) 14:02, 6 November 2011 (UTC)[reply]
      Posted at Wikipedia:Arbitration/Requests/Enforcement#Request_concerning_Debresser. Debresser (talk) 14:12, 6 November 2011 (UTC)[reply]
      He doesn't want to play within the rules, indef him and be done with it. This is a rabbit hole that none need to go down - we've wasted enough time on an editor who fails to see/accept the repercussions of their own actions. How frustrating to see a reasonbly good editor implode. (talk→ BWilkins ←track) 16:19, 6 November 2011 (UTC)[reply]

      user:rozitaa

      Some one hacked user:Rozitaa password in en.wiki and writes some spam in here page. she is active in fa.wiki and she doesn't access to here account to write in this page. is it possible to reset here page to here password that is in fa.wiki? if it is not please block here user page and her pageDiscussion until some one could solve this problem. Reza1615 (talk) 09:20, 6 November 2011 (UTC)[reply]

      please block user:Rozitaa Some one hacked this name.Roozitaa (talk) 09:48, 6 November 2011 (UTC)[reply]

      Blocked by User:Closedmouth as compromised. — Moe ε 10:27, 6 November 2011 (UTC)[reply]

      RfC closure needed

      Could someone please take a look at the RfC regarding names a few color-related articles. The RfC is over 30 days old and needs to be closed one way or another. Or perhaps changed into a request for move. Thanks. --Noleander (talk) 12:37, 6 November 2011 (UTC)[reply]

      RfC summary update

      I would like to reverse this deletion of updates and clarifications I made to an RfC header, but I have been accused of disruptive editing so I am asking that an administrator revert that instead, please. Dualus (talk) 00:55, 7 November 2011 (UTC)[reply]