Jump to content

Wikipedia:Administrators' noticeboard

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Fastily (talk | contribs) at 01:46, 12 December 2011 (→User:TreasuryTag unblock request – December 2011: support). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

    Welcome — post issues of interest to administrators.
    Shortcuts

    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.(archives, search)

    Template:Active editnotice


    "WP:CR" redirects here. You may be looking for Wikipedia:Cleanup resources, Wikipedia:Categorizing redirects, Wikipedia:Copyrights, Wikipedia:Competence is required, Wikipedia:Dispute resolution, Wikipedia:Content removal and WP:Criteria for redaction.
    "WP:ANC" redirects here. You may be looking for Wikipedia:Assume no clue.

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

      Shortcuts

      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/Archive366#IBAN_appeal

      (Initiated 32 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]
      Thanks for letting me know. It is back in the archive, and hopefully someone can close it there. Heartfox (talk) 05:23, 9 November 2024 (UTC)[reply]

      Wikipedia:Administrators'_noticeboard/Archive366#Is_WP:RECALL_a_policy?

      (Initiated 21 days ago on 28 October 2024) Discussion has slowed for the last week. I think the consensus is pretty clear, but I'm involved. – Joe (talk) 17:24, 11 November 2024 (UTC)[reply]

      information Note: discussion has been archived. voorts (talk/contributions) 16:52, 16 November 2024 (UTC)[reply]

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

      Requests for comment

      Wikipedia talk:Notability (species)#Proposal to adopt this guideline

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

       Closed by editor Tamzin. P.I. Ellsworth , ed. put'er there 08:23, 19 November 2024 (UTC)[reply]

      Talk:Memorial_Hall_(Harvard_University)#Rfc_on_use_of_"imposing"

      (Initiated 97 days ago on 14 August 2024)

      Coming up on two months since the last comment. Consensus seems pretty clear, but would like an uninvolved party to look it over. Seasider53 (talk) 23:13, 18 November 2024 (UTC)[reply]

      Talk:International Churches of Christ#RfC: Referring to International Churches of Christ (ICOC) as a cult in the lead

      (Initiated 61 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]
      @Compassionate727: just checking in here. voorts (talk/contributions) 16:53, 16 November 2024 (UTC)[reply]
      I'm still working on this, and I apologize for the delay. Because of my health problems, I only occasionally have days where I am fit to take on complex stuff like closures, and this particular one is testing me. I do have an outline of my findings in a document, but need to flesh it out and proof it against the discussion. I could finish this as soon as tomorrow, depending on how things go, but I can't promise anything. —Compassionate727 (T·C) 19:39, 16 November 2024 (UTC)[reply]
      No worries. Your health always comes first. Best, voorts (talk/contributions) 23:12, 16 November 2024 (UTC)[reply]
      I fear I gave the wrong impression. My health is in no jeopardy whatsoever, I just have intractable problems with fatigue and focus that frequently keep me from doing the things I want and intend. I appreciate your concern, though. —Compassionate727 (T·C) 19:37, 17 November 2024 (UTC)[reply]

      Wikipedia:Reliable sources/Noticeboard/Archive 456#RfC: using photos of record labels from Discogs?

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

      Archived. P.I. Ellsworth , ed. put'er there 20:53, 9 November 2024 (UTC)[reply]

      Wikipedia:Requests for comment/In the news criteria amendments

      (Initiated 42 days ago on 7 October 2024) Tough one, died down, will expire tomorrow. Aaron Liu (talk) 23:58, 5 November 2024 (UTC)[reply]

      Talk:Turkey#RfC_on_massacres_and_genocides_in_the_lead

      (Initiated 41 days ago on 8 October 2024) Expired tag, no new comments in more than a week. KhndzorUtogh (talk) 21:48, 13 November 2024 (UTC)[reply]

      Talk:David Lammy#RfC: First sentence

      (Initiated 35 days ago on 15 October 2024) Discussion has died down. The last vote was on 4 November. Khiikiat (talk) 10:10, 15 November 2024 (UTC)[reply]

      Talk:One_Direction#RfC: Band status and members in the infobox

      (Initiated 32 days ago on 18 October 2024) Expired today, last comment was three weeks ago. The consensus on this RfC appears to lean one way among the participants, but because of the high-profile and contentious nature of the change under discussion, I think an uninvolved editor should close. Thesixthstaff (talk) 19:25, 18 November 2024 (UTC)[reply]

      Wikipedia talk:Administrator recall#RfC: Should we add text prescribing just signatures, no discussion?

      (Initiated 16 days ago on 3 November 2024) The amount of no !votes relative to yes !votes coupled with the several comments arguing it's premature suggests this should probably be SNOW closed. Sincerely, Dilettante 16:53, 5 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 35 35
      TfD 0 0 0 3 3
      MfD 0 0 0 5 5
      FfD 0 0 0 2 2
      RfD 0 0 5 58 63
      AfD 0 0 0 0 0

      Wikipedia:Categories for discussion/Log/2024 November 8#Confederation of the Rhine

      (Initiated 19 days ago on 31 October 2024) HouseBlaster (talk • he/they) 23:15, 17 November 2024 (UTC)[reply]

      Wikipedia:Categories for discussion/Log/2024 November 9#Category:Fictional characters from the Solar System

      (Initiated 10 days ago on 9 November 2024) HouseBlaster (talk • he/they) 21:18, 18 November 2024 (UTC)[reply]

       Done —Compassionate727 (T·C) 02:07, 19 November 2024 (UTC)[reply]

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

      Other types of closing requests

      Talk:Feminist art movement#proposing merge of Feminist art into Feminist art movement

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

       Doing... may take a crack at this close, if no one objects. Allan Nonymous (talk) 17:47, 12 November 2024 (UTC)[reply]

      Talk:List of pholidotans#Merge to Manidae

      (Initiated 19 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]
      @Cowboygilbert: So what should I do now? Wait until the discussion is a week old? Wolverine X-eye (talk to me) 11:14, 5 November 2024 (UTC)[reply]
      @Wolverine X-eye:, Yes. Cowboygilbert - (talk) ♥ 17:04, 5 November 2024 (UTC)[reply]
      @Cowboygilbert: It's now 7 days... Wolverine X-eye (talk to me) 14:09, 7 November 2024 (UTC)[reply]
      @Compassionate727: You still interested in closing this? Wolverine X-eye (talk to me) 04:04, 8 November 2024 (UTC)[reply]
      This isn't a priority, given all the much older discussions here. I'll get to this eventually, or maybe someone else before me. In the meantime, please be patient. —Compassionate727 (T·C) 13:34, 11 November 2024 (UTC)[reply]
      @Compassionate727: It's now been 7 days...I know this isn't a priority to you but can you at least take a look at it this week, even if it's not today? Thanks for your time, Wolverine X-eye (talk to me) 04:26, 18 November 2024 (UTC)[reply]

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

      ClueBot NG appears to be down

      Resolved
       – CBNG is back online - Rich(MTCD)T|C|E-Mail 00:49, 10 December 2011 (UTC)[reply]

      The anti-vandalism bot, ClueBot NG, currently appears to be down. The bot has not edited in almost 24 hours. As the bot has several maintainers, I assumed this would be the best place to post the notification. If I am incorrect, I apologize. Best, Alpha_Quadrant (talk) 04:36, 29 November 2011 (UTC)[reply]

      Hi Alpha, thanks for reporting this. I've had a look at ClueBot's run page and that seems to be looking ok to me. I've emailed Cobi to make him aware of the issue--5 albert square (talk) 23:45, 29 November 2011 (UTC)[reply]
      Actually, I just saw that someone has asked about this on Damien's talk page, apparently it was originally down to maintenance work but now the server seems to be offline? Like I've mentioned above, I've emailed Cobi, hopefully he'll be able to give an ETA of when CBNG should be back.--5 albert square (talk) 01:00, 30 November 2011 (UTC)[reply]
      OK, a response from Damian, this is apparently a server issue which we're waiting on Rich to take a look at. There's currently no ETA of when this will be fixed, so until it is, I've put a notice on CBNG's talk page saying the bot is down.--5 albert square (talk) 01:43, 1 December 2011 (UTC)[reply]
      Does anyone have any further information. ClueBot has now been down for about 90 hours. Andrew Kurish (talk) 02:02, 2 December 2011 (UTC)[reply]
      Hi Andrew, I don't think there's any further information yet, there wasn't an ETA when I put together the notice for ClueBot NG's talk page. Hopefully it won't be too long :)--5 albert square (talk) 23:08, 2 December 2011 (UTC)[reply]
      Hi all, I apologise for CBNG's downtime, this is due to me not being able to pay for the server and hence it being suspended by the host. I can assure you that the server will be back alive on the 9th of December which is when I get paid next. Sorry again for the confusion - Rich(MTCD)T|C|E-Mail 23:49, 3 December 2011 (UTC)[reply]
      Hi Rich, thanks for the explanation. I saw Tedders suggestion on your talk page, do you know if that would be possible?--5 albert square (talk) 16:05, 4 December 2011 (UTC)[reply]
      How much does hosting cost? I may be able to help, if you want. bobrayner (talk) 00:49, 5 December 2011 (UTC)[reply]
      Seconded. Sven Manguard Wha? 16:46, 5 December 2011 (UTC)[reply]

      (Reset Indent)This may not sound smart but why can't you just get a toolserver account? --Kangaroopowah 02:39, 5 December 2011 (UTC)[reply]

      Its actually a valid thought, however the toolserver has restrictions on how much resources any one user is allowed to consume. Given what Cluebot does it probably uses too much resources. ΔT The only constant 00:59, 6 December 2011 (UTC)[reply]

      Update - The server will now be back on the 8th, however we will be moving it over to a Wikimedia Labs instance ASAP. - Rich(MTCD)T|C|E-Mail 23:49, 6 December 2011 (UTC)[reply]

      I've been trying to contact Rich on Skype and IRC without luck for the past two days after he suggested I might be able to help pay for it. ClueBot NG contributions indicates it is still down, so I asked on #wikimedia-labs for an update, and petan said the VM instance is created and Rich tried to start it without success. Nobody has heard from him since yesterday when he said he was busy (he's a student and works too.) I commented out the {{resolved}} header above for the time being; please check contribs before replacing it. 67.6.163.68 (talk) 14:43, 8 December 2011 (UTC)[reply]

      Update 2 - Okay, OVH have made me rage! They decided in their wisdom to fully terminate the server... so I've lost EVERYTHING(!). Me and Damian can get it back, albeit not fully taught... but it may take a couple of days. I am extremely sorry that this has happened and hopefully we can get it back up ASAP. When it is back up, we are going to need more and more community members to assist looking though the false postives so the database can be re-filled, anyone wishing to help can send me an e-mail or a talk page message and I will get you set up. Many thanks for your continued patience. - Rich(MTCD)T|C|E-Mail 19:29, 8 December 2011 (UTC)[reply]

      Per Skype, the installation problem has been resolved on WMF Labs and ClueBot is compiling there presently. This thing apparently uses an artificial neural network (ANN) simulation to judge false positives. Anyway, a lot of help is going to be needed to review logs to get it working well again because the ANN database, which is usually stored in RAM apparently, was lost when the OVH ISP terminated the account. 67.6.163.68 (talk) 21:04, 8 December 2011 (UTC)[reply]
      For clarity are you refering to the review interface? Crazynas t 22:26, 9 December 2011 (UTC)[reply]
      The review interface just feeds back to the (currently missing) report interface which was databased in the same location as ClueBot itself. That's what the IP was referring too - Rich(MTCD)T|C|E-Mail 00:49, 10 December 2011 (UTC)[reply]

      Quick question about "email this user"

      Sorry, I never get into trouble so I don't know this stuff :) If I click on "email this user" and send them an email, and they later claim that I said something completely different from what I said, does anyone on-wiki have a way to check it? If not, what method do you guys prefer if you're trying to keep something private because you don't want to be publicly pointing a finger at someone, but you want to protect yourself in case they claim you said something different? - Dank (push to talk) 21:43, 5 December 2011 (UTC)[reply]

      Unless you're emailing a mailing list there is no record of the email sent, and no way to verify if someone lies about its content. The best you can do is select the "E-mail me a copy of my message" option on the email user form--Jac16888 Talk 21:50, 5 December 2011 (UTC)[reply]
      Okay, thanks. - Dank (push to talk) 21:53, 5 December 2011 (UTC)[reply]
      Being slightly pedantic: that is not entirely true. I ask a CU to comment below.  Chzz  ►  22:05, 5 December 2011 (UTC)[reply]
      Right, checkuser can verify an email was sent but there is still no way to see the content of the email. –xenotalk 22:06, 5 December 2011 (UTC)[reply]
      Yep, thanks, Xeno, that was my pedantic point.  Chzz  ►  03:18, 6 December 2011 (UTC)[reply]
      I was under the impression that in case of an absolute emergency, the Devs could see the contents of the email. Was this an incorrect impression? Sven Manguard Wha? 06:31, 6 December 2011 (UTC)[reply]
      Yeah, that's the correct impression. Sysadmins can view the contents of an email. -FASTILY (TALK) 06:44, 6 December 2011 (UTC)[reply]
      Where do you have this information from? I don't know that any emails are being logged, not see it in mail config. Petrb (talk) 15:53, 6 December 2011 (UTC)[reply]
      That doesn't mean it's not true, it may be logged but I just don't think that Petrb (talk) 16:01, 6 December 2011 (UTC)[reply]
      I had a quick look at my own little MediaWiki installation, and did a text search in a database dump, and I don't seem to see stored sent mails anywhere in that, but maybe I missed it. More likely any "logging" is somewhere else (in the mail subsystem used by WP servers, for instance... developers could access that, and the mail subsystem could be configured to log outgoing mail). Alternatively, if it is correct, perhaps it's a particular configuration of the MediaWiki version for WMF sites (or just WP). Begoon talk 03:05, 7 December 2011 (UTC)[reply]

      When a user sends an email via Special:EmailUser from this (English Wikipedia) wiki, currently: The MediaWiki system records the username (if registered), the IP address of the sender, the date/time that the email was sent, the sender's User agent, and an encoded version of the user-name and address of the user it was sent to. That information is only available to people with checkuser access (ie, checkusers, and Wikimedia/Jimbo, etc). The actual content of the email is not recorded by the currently deployed software - although, in theory, the server operators could store any and all information they see fit to (e.g. the content could be cached somewhere). Meta:Privacy policy applies in all cases.  Chzz  ►  04:00, 9 December 2011 (UTC)[reply]

      (Deep breath.) If you wanted to you could mail a public key signed message, or merely a suitably checksummed message, and post the sig/checksum of the message on wiki, notifying your victim correspondent on their talk page. If they then wish to claim much later that you said something else they would have to produce a signed message by you with the required sig/checksum. You, conversely would be able to prove that you had sent the message you claimed (if any message). The only thing they could then say was that they received no message or didn't check the sig/checksum. Rich Farmbrough, 19:58, 10 December 2011 (UTC).[reply]
      Send a copy at the same time to a trusted person, crat., steward or whatever. Leaky Caldron 20:16, 10 December 2011 (UTC)[reply]

      Good news: User:CorenSearchBot is back

      I don't know if this has been mentioned in any well-read fora, but User:CorenSearchBot is back for now. A few extra eyes on Wikipedia:Suspected copyright violations would be very much appreciated. MER-C 08:20, 7 December 2011 (UTC)[reply]

      Huzzah! We just need ClueBot NG back and we can go back to letting the robots run everything. —Tom Morris (talk) 08:52, 7 December 2011 (UTC)[reply]
      I, for one, welcome our new robot overlords. ~Alison C. (Crazytales) 18:00, 7 December 2011 (UTC)[reply]
      As long as they don't like beer (Did the Good News heading make anyone else think of a certain professor?) Crazynas t 09:59, 9 December 2011 (UTC)[reply]
      It is better to combat and fight vandalism. Its back when it was shut down on July 2011. --Katarighe (talk) 18:49, 10 December 2011 (UTC)[reply]

      Closers wanted for WP:V RfC

      Hi. The RfC regarding the lead section of WP:V ended a little over a month ago. There was an agreement that it would be closed by User:Newyorkbrad, User:Black Kite and User:HJ Mitchell. However, this has not happened because of the low availability of two of those.

      Would anyone be interested in joining the process so that it can get back on track?

      There is an existing understanding that closers should be three in number, be admins in good standing, not have participated in discussions leading up to this point and not have commented elsewhere in such a way that their impartiality might be questioned.

      It's a responsibility to be taken seriously. A minor change is at stake, but it is one about which there are strongly-held views. It's also the RfC with the highest ever level of participation on Wikipedia. So there is a lot to read and it will probably not be an open and shut case.

      Any takers? If so, please put yourself forward by making your mark below. --FormerIP (talk) 15:52, 8 December 2011 (UTC)[reply]

      Tempted. Am I wrong, or is that RFC archived twice on that page? UltraExactZZ Said ~ Did 16:18, 8 December 2011 (UTC)[reply]
      Yes, I guess that will make it twice as much work. --FormerIP (talk) 16:46, 8 December 2011 (UTC)[reply]
      Could be persuaded. Depends how urgent it is, as there's a lot to read and I'm busy this weekend. WormTT · (talk) 16:21, 8 December 2011 (UTC)[reply]
      I don't think it is urgent is the sense that a decision is needed by 10 am. But I think editors want to know that it is moving in a forward direction. --FormerIP (talk) 16:46, 8 December 2011 (UTC)[reply]
      I'm willing to step in if the two above me cannot or someone below me has more enthusiasm.--v/r - TP 16:32, 8 December 2011 (UTC)[reply]
      I could do it... --SarekOfVulcan (talk) 16:39, 8 December 2011 (UTC)[reply]
      Maybe SlimVirgin could work with you. Leaky Caldron 16:41, 8 December 2011 (UTC)[reply]
      I'll have plenty of time starting Monday and am willing to wade through the stuff. --regentspark (comment) 16:47, 8 December 2011 (UTC)[reply]
      Excellent. I don't have the time to do it justice before Monday anyway so that suits me. If Worm will join us, we'll have the requisite three admins. HJ Mitchell | Penny for your thoughts? 16:59, 8 December 2011 (UTC)[reply]
      From my limited knowledge of the three of you, that should be good. But can I suggest making yourselves known on the WP:V talkpage first? There has been a little concern there about the risk of a runaway train of biased and incompetent admins. Yes, its a tautological concept. --FormerIP (talk) 17:03, 8 December 2011 (UTC)[reply]
      Sounds good to me. If no one has mentioned it at the RfC by tomorrow, I'll mention it then. Lots of reading to do... yay! WormTT · (talk) 21:50, 8 December 2011 (UTC)[reply]
      We are playing rugby now? :P --Guerillero | My Talk 18:42, 9 December 2011 (UTC)[reply]

      Wikipedia:Government: "A government can also be agreed to in order to close very contentious RFCs. A notable example of this was the 2011 closure of the RFC on the "not truth" issue in the Verifiability policy text. While in principle any univolved Admin is free to close a RFC, in this case it was decided that a group of 3 editors should have the exclusive right to do this. While no other Admin was formally prohibited from ignoring that decision and close that RFC him/herself, in practice any such closure would have been swiftly reverted." Count Iblis (talk) 19:29, 8 December 2011 (UTC)[reply]

      That proposal was pretty clearly rejected, Count Iblis -- taking the Rejected tag off is not a good idea. --SarekOfVulcan (talk) 20:04, 8 December 2011 (UTC)[reply]
      I've rewritten it to reflect current practice. Count Iblis (talk) 20:51, 8 December 2011 (UTC)[reply]
      • Comment It is my understanding that the permission class of a user that the Wikipedia community trusts to specifically judge consensus already exists. If we're going to limit this close to a certain class of editor based on permissions held why not entrust it to the people we already trust to make difficult decisions regarding consensus(send it to 'crat chat)?Crazynas t 20:42, 8 December 2011 (UTC)[reply]
      In no way is the above meant to disparage or attack the neutrality or objectiveness or ability to judge consensus of any of the administrators that have volunteered, more of a procedural question. Crazynas t 20:50, 8 December 2011 (UTC)[reply]
      I don't think you're understanding is correct, actually, Crazynas. Admins/bureaucrats don't have the exclusive privilege of closing RfCs. --FormerIP (talk) 21:13, 8 December 2011 (UTC)[reply]
      No I do understand that, which is why my second sentence was conditional. This is a question for this particular closure (and others of this nature) why we're limiting the close to a subset of editors that are not selected primarily for their ability to judge consensus when there already exists a usergroup that is scrutinized on their neutrality and ability to gauge consensus. (in other words, allow any editor in good standing to assist the close, or limit it to the well defined group of users that are promoted based on this specific type of trust to judge consensus). Crazynas t 21:29, 8 December 2011 (UTC)[reply]
      Oh I see. Yes, actually, that makes sense, except bureaucrats do not present a very large pool. I think, in this particular case it is just a case of consensus, for better or worse, between involved editors that they wanted admins. --FormerIP (talk) 21:37, 8 December 2011 (UTC)[reply]
      I'm going to go ahead and finish what I started on my userpage. I hope you all find it helpful in reaching a conclusion on the RfC. Cla68 (talk) 22:08, 8 December 2011 (UTC)[reply]
      Folks, we have what is one of the largest RFC's ever, and its about a month after comments were closed it looks like we don't even have the closers picked. May I suggest that we create the short list of potential folks here, vett them not only for having no relevant issues, but also for anything that someone could successfully pretend is a relevant issue. And if that doesn't get it down to three, flip a coin and pick three and then roll. North8000 (talk) 14:03, 9 December 2011 (UTC)[reply]

      In my naiveness, I'm listing the above volunteers and the original three, so other folks can starting paring or adding to the list, please consider this to be editable (not like a part of my post). North8000 (talk) 14:16, 9 December 2011 (UTC)[reply]

      • HJMitchell
      • Black Kite
      • NewYorkBrad
      • Ultraexactzz
      • Worm
      • Regentspark
      • SarekOfVulcan
      • Cla68

      I interpret the above discussion to mean that the "new team" of closers consists of HJ Mitchell, RegentsPark and Worm That Turned. Isn't that correct? Neutron (talk) 22:38, 9 December 2011 (UTC)[reply]

      All three indicated that they would be willing... I would just like them to confirm that they are actually taking this on. Blueboar (talk) 22:41, 9 December 2011 (UTC)[reply]
      Yes, please. North8000 (talk) 22:48, 9 December 2011 (UTC)[reply]
      That was my understanding, but I also said that I won't be up to it until Monday. I'll probably spend a good chunk of monday afternoon on it. HJ Mitchell | Penny for your thoughts? 22:51, 9 December 2011 (UTC)[reply]
      I don't think that people are in a super hurry, they just want to know that it is heading forward, which, right now means hearing a clear statement something like: "HJ Mitchell, RegentsPark and Worm That Turned are the trio that is or will soon be working on closing this" Can somebody say that? Thanks. North8000 (talk) 00:00, 10 December 2011 (UTC)[reply]
      Or to be more specific, can ALL of THEM say that? Neutron (talk) 02:40, 10 December 2011 (UTC)[reply]
      I'm certainly reading through. I hereby commit to the trio of closers. WormTT · (talk) 08:54, 10 December 2011 (UTC)[reply]
      I've scanned the discussion but won't be able to read it carefully till Monday. Since a Monday-Tuesday timetable seems acceptable, I too hereby commit to the trio of closers. --regentspark (comment) 12:13, 10 December 2011 (UTC)[reply]

      Closure of image compromise at Muhammad

      I'd be grateful if an uninvolved admin could try and close the image compromise discussion at Talk:Muhammad/images. The exact section link is Talk:Muhammad/images#Proposed_image_solution, although there is other further discussion elsewhere on the talk page. -- Eraserhead1 <talk> 17:53, 8 December 2011 (UTC)[reply]

      • I'd certainly hope no one claims that wall of text is a closable discussion. Hold an RfC or something, but that's just an argument that is difficult to parse and too long to follow. Voting is evil, but unorganized walls of text are worse. There is just no way outsiders to that discussion could possibly follow or comment intelligently on it without spending at least 30 minutes. It currently stands (if I counted correctly) at more than 31,000 words. That's a third of a novel. At most I'd hope it would be closed as "hold an RfC". Disclaimer/comment: I personally believe a handful of editors are creating these walls more-or-less on purpose in an attempt to get their way on censorship related issues. WP:NOT's talk page being a good example, with the pregnancy image debate being another one (but it at least was readable). Hobit (talk) 22:06, 8 December 2011 (UTC)[reply]
        • I tend to agree. Frankly, the discussion got trainwrecked by a couple editors (one on each side), and movement forward is unlikely as a result. An RfC would be pointless for the same reason. Resolute 00:47, 9 December 2011 (UTC)[reply]
            • I don't have the time to read it all just now, and probably wouldn't if I did. You're talking about Ludwigs and whom? If you think they're an impediment to reaching a stable article, would you support an article ban for both? I find it impossible to discuss the topic with every thread being derailed into a battle of the egos. --Anthonyhcole (talk) 05:19, 11 December 2011 (UTC)[reply]
              • And Tarc. But remove the former, and you remove the latter as well. Ludwigs goes somewhere, repeats the same arguments he made 100 times already, and Tarc replies with the same rebuttal he made 100 times already. Ludwigs moves to the next forum, rinse, repeat. And voila, 500kb of "discussion". Resolute 06:21, 11 December 2011 (UTC)[reply]
                • My problem is not with Ludwigs' position - that it's a net negative for the encyclopedia to be gratuitously offending our readers - with which I agree, but with his style of argument, seemingly more intent on impressing posterity or silent watchers with his considerable eloquence and logical prowess than engaging and convincing his interlocutor. I thought you Erasorhead, Jayen, Mathsci and the others (excluding Alan, IP and Tarc) were working towards something there but once Ludwigs returned from his month away, the delicate and elegant resolution you'd proposed just got shoved aside while the various gladiators preened and posed. I don't think I've ever called for an article ban before but I'm seriously tempted here. I'll let Ludwigs know about this. --Anthonyhcole (talk) 06:54, 11 December 2011 (UTC)[reply]
                  • While Ludwigs has definitely been annoying and over-argued, he has been prepared to compromise. I'm sorry but I strongly object to topic banning an editor who has behaved significantly better than the editors on the other side. If you want to do a two sided topic ban (so Alan, IP, Tarc and Ludwigs) I'm OK with that, and I'm OK with blocking whoever you think is the worst offender - and that isn't Ludwigs. -- Eraserhead1 <talk> 09:38, 11 December 2011 (UTC)[reply]
          • I was hopeful that someone might try and close it, but fair enough. I thought it was a better option than escalation. -- Eraserhead1 <talk> 07:33, 9 December 2011 (UTC)[reply]

      Punishment of exposing someone's identity

      I recognized an old user who used to edit under a different username last year, but ended it and started a new one. I went to his new user-page and called him with his old user ID (essentially exposing his old "user" identity). I wonder if I qualify for any sort punishment.69.232.73.16 (talk) 05:10, 9 December 2011 (UTC)[reply]

      If you are genuinely concerned that you've outed someone's identity, pointing out that you've outed someone's identity on this noticeboard is going to further compound rather than resolve the problem. —Tom Morris (talk) 08:41, 9 December 2011 (UTC)[reply]
      Yes, genuinely revealed the old username of a current user and my IP has been blocked by an administrator for one month(saying that he knows the user corresponding to this IP). I am asking here if that is a fair punishment.--69.232.73.16 (talk) 12:57, 9 December 2011 (UTC)[reply]
      Of course it is. And evading that valid block by editing with a new IP address isn't good either. (talk→ BWilkins ←track) 13:03, 9 December 2011 (UTC)[reply]
      Even though the rule says, an IP must not be blocked for more than a few hours?

      "Most IP addresses should not be blocked more than a few hours," --69.232.73.16 (talk) 13:46, 9 December 2011 (UTC) By the way, I did not expose his name/address or anything; just his old user ID. Does that also violate the policy?69.232.73.16 (talk) 13:48, 9 December 2011 (UTC)[reply]

      "Should not" ≠ "must not". I'm not sure whether you're genuinely concerned or just trolling us; if the former, you should contact WP:OVERSIGHT, and if the latter, you should stop before an admin less charitable than I blocks you. The Blade of the Northern Lights (話して下さい) 00:03, 10 December 2011 (UTC)[reply]
      That's kinda what I hinted at above ... (talk→ BWilkins ←track) 00:08, 10 December 2011 (UTC)[reply]
      Some IP's are blocked for months or years, just not "indefinite", unless maybe they're open proxies. ←Baseball Bugs What's up, Doc? carrots→ 05:11, 11 December 2011 (UTC)[reply]

      Selective deletion request (again)

      The usual. Want to unclutter the page history.Jasper Deng (talk) 05:13, 9 December 2011 (UTC)[reply]

       Done. --Jayron32 02:39, 10 December 2011 (UTC)[reply]

      AWB backlog

      Hi, can an admin please address the small backlog and requests at Wikipedia talk:AutoWikiBrowser/CheckPage. Thanks, Ma®©usBritish [Chat • RFF] 22:57, 9 December 2011 (UTC)[reply]

      I've done a couple, but there are a few more; I'd prefer a more experienced admin handle them. The Blade of the Northern Lights (話して下さい) 23:48, 9 December 2011 (UTC)[reply]

      Salting

      I have been seeing a lot of MediaWiki talk:Customusertemplate-ACP2(something else) type pages being created example: MediaWiki talk:Customusertemplate-ACP2-Be a part of Wikipedia (Technology, Copyediting) which has been deleted 3 time now. Is there some way that we can forbid creation of any page with that prefix unless a user is autoconfirmed? ΔT The only constant 01:39, 10 December 2011 (UTC)[reply]

      It can be done by using the MediaWiki:Titleblacklist. Maybe you could request that on the talk page. →Στc. 02:10, 10 December 2011 (UTC)[reply]

      Oops, my bad.

      There was an RM to fix the 4-Acetoxy-DiPT article (which had incorrect spelling, -DIPT at the end). In the discussion it was said that it couldn't be moved because just changing the capitalization was invalid... anyhoo, I figured I could move it to an interim page, then just move it back with the correct spelling. I didn't realize that the redirect page would block the move back, so now it's stuck at a wayyyy wrong title that I intended to only be for 2 seconds while I moved it back. Oh man. Can someone move this back for me? 4-Acetoxy-DiPT 0101 -> 4-Acetoxy-DiPT. :( -Kai445 (talk) 04:49, 10 December 2011 (UTC)[reply]

      It's fixed. Thank you :). -Kai445 (talk) 05:25, 10 December 2011 (UTC)[reply]

      The usual...

      Selective deletion please.Jasper Deng (talk) 05:32, 10 December 2011 (UTC)[reply]

       Done CharlieEchoTango (contact) 05:43, 10 December 2011 (UTC)[reply]
      There's more to do now.Jasper Deng (talk) 05:57, 10 December 2011 (UTC)[reply]

      Jimbo's straw poll on SOPA

      Please help me publicize this widely. I'm interested in getting a feeling from the broad community.--Jimbo Wales (talk) 07:47, 10 December 2011 (UTC)[reply]

      How about watchlist banners? →Στc. 07:58, 10 December 2011 (UTC)[reply]

      Wikipedia:Miscellany for deletion/User:NWA.Rep

      Would an admin close Wikipedia:Miscellany for deletion/User:NWA.Rep? The discussion has been open 10 days.

      I ask that the closer not be an arbitrator or arbitrator candidate as NWA.Rep (talk · contribs) is an arbitrator candidate.

      I further ask that the closer not be a writer of an arbitrator voter guide because the user has said: "the lynch mob (namely the arbcom voters guide writers) wants me out of this project and are disgracefully trying to sneak this Mfd through when all the people who support it are the 'arbcom voter guide' writers". Thanks, Cunard (talk) 04:44, 11 December 2011 (UTC)[reply]

      If that guy manages to get elected to the ArbCom, it should be a cinch for me the next time I run for admin. :) ←Baseball Bugs What's up, Doc? carrots→ 05:10, 11 December 2011 (UTC)[reply]
      I'll do it. 28bytes (talk) 16:56, 11 December 2011 (UTC)[reply]
       Done. 28bytes (talk) 17:31, 11 December 2011 (UTC)[reply]

      Closure of VPR

      Hi could you please review and close http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28proposals%29#.22Blocked.22_template_tweak it's blocker for deployment. Petrb (talk) 15:44, 11 December 2011 (UTC)[reply]

      I don't think the thread needs closure per se. It's quite clear that there is consensus in support of the proposal. You now need to convince developers to turn it on.  Sandstein  17:07, 11 December 2011 (UTC)[reply]
      I am a developer it can't be deployed if discussion isn't closed. https://bugzilla.wikimedia.org/show_bug.cgi?id=32819 Petrb (talk) 18:43, 11 December 2011 (UTC)[reply]

      User:TreasuryTag unblock request – December 2011

      User:TreasuryTag has requested to be unblocked. I am taking no position on that, but per his request will copy the unblock request here for the community to discuss, as his previous declined unblock request was judged to be a community ban, and this is the venue for considering whether to rescind such bans. 28bytes (talk) 19:24, 11 December 2011 (UTC)[reply]

      I've been gone for more than two months now, and I daresay some people have noticed the peace and quiet broken only by occasional orchestrated assaults on the project!
      Meanwhile, I've been racking up a lot of edits I want to make. Edits that need to be made. Not controversial; not deletion-related; not Doctor Who-related – completely free of the areas where I seem to have generated trouble in the past.
      I understand that I caused a lot of problems, understand how it happened, and fully intend to stop it from happening again. I'm already topic-banned from initiating any sort of deletion for six months after being unblocked, so there can't be any issues in that department, and as I say, I've discovered new areas of editing to go into which are (a) away from my past fault-lines and (b) sorely in need of an experienced, good-faith editor like myself.
      Please let me back in! Best, ╟─TreasuryTag►quaestor─╢ 19:01, 11 December 2011 (UTC)

      This unblock request is so accomplished that I find it almost irresistible. Hans Adler 20:35, 11 December 2011 (UTC)[reply]

      Personally, I can resist it. A longer break will do wonders for TT's attitude when he returns. A thought: it might help his case if we could see some evidence of trouble-free contribution on another Wikimedia project. The block is not a global one across his unified account. --Dweller (talk) 21:03, 11 December 2011 (UTC)[reply]

      • One minor point on the phrasing of the copied-over statement, regarding: "Edits that need to be made". No, no edit "needs to be made"; we don't need any contributor, especially if they are unable to collaborate with other people. Having said that, I'm of two minds about the appeal. Two months is not very long, and I find it hard to believe that TT's combative attitude has vanished. His unblock statement is heartening, and suggests the break did him some good, but did it do him enough? If a little is good, more must be better: I'm not sure the break was long enough, but if TT (and everybody who comments here) thinks so then I don't see a problem with letting him return. He certainly did good work when he was around and tried to be professional. For the purposes of the closing administrator, this is a tentative support. AGK [•] 21:17, 11 December 2011 (UTC)[reply]
      • Support unblock I've never wished to see TT blocked long-term, merely for him to stop being so gratuitously abrasive when there was no call for it. If he'd go along with that, I'd welcome him back. Andy Dingley (talk) 21:22, 11 December 2011 (UTC)[reply]
      • Support' The potential benefit of giving a second chance here far outweighs the potential discomforts of having to block him again if he doesn't deliver on his promises.·ʍaunus·snunɐw· 21:23, 11 December 2011 (UTC)[reply]
      • Support unblock he's done enough time and seems to have made significant progress of understanding the issues that caused the block and seems positive about avoiding them. -- Eraserhead1 <talk> 21:27, 11 December 2011 (UTC)[reply]
      • Oppose (with regret) I was quite unimpressed when the last discussion was interpreted as a "de facto ban", something that appeared to come from left side and was unfair on TreasuryTag. I've had a couple of editors come to me and suggest that whilst they were opposing at the time, it was only for that specific discussion, and not for future ones. Having said that, I am not sure I can support an unblock of TreasuryTag, with no restrictions besides the topic ban. When HJ Mitchell unblocked him a few months ago, his restrictions were lax and TreasuryTag flouted them - I'm not sure that I believe he will not return to his old behaviour. Perhaps with mentoring or strongly enforced restrictions or even evidence that he has changed, I could support, but the unblock request does not persuade me. WormTT · (talk) 21:46, 11 December 2011 (UTC)[reply]
      • Oppose (also with regret). I've seen TT around a lot, and I fully acknowledge his great contributions and I really would like him back on the project. But with his extensive history of abrasive and aggressive confrontation with others, and the past breaking of promises, I could only support an unblock with some sort of reasonably strict mentorship, restrictions, or other supervisory plan in place - and I do hope that can be achieved in the not-too-distant future -- Boing! said Zebedee (talk) 22:02, 11 December 2011 (UTC)[reply]
      • Comment one has to wonder if we need an unblock option for 1 day and so on. So that we can give an editor a chance to demonstrate that they are reformed. They can ask for longer periods each time and maybe get back to normal status. Probably not worth the effort to implement, but I think the concept still makes sense. Vegaswikian (talk) 22:39, 11 December 2011 (UTC)[reply]
      "Probation" is a common practice in the real world. The point is that it is much easier to reinstate the e.g. block if the terms are violated; starting over from scratch is not required. Setting up such a thing might be good. From their wording where "you need me" is emphasized (including in the selection of a link) the and "I've changed" is barely there, I'm guessing that they they have not changed much, but that would be a way to find out, and possibly a way to modify their behavior. North8000 (talk) 23:21, 11 December 2011 (UTC)[reply]
      I understood Vegaswikian's proposal as saying that just like a user can be blocked for a specific amount of time, so that they are automatically unblocked afterwards, we might want to unblock a user with an automatic block later on. It would be even better if we coud set this up periodically, so that e.g. an editor would be allowed to edit only 2 hours per day or so. I suspect that many of the behavioural difficulties on this site have to do with its addictive nature. This is a way in which many blocked editors would still be able to contribute productively, and I think quite a few editors who would otherwise start full-time socking might be led to find a better real-life/Wikipedia balance instead. Hans Adler 00:39, 12 December 2011 (UTC)[reply]
      • Comment  While on the one hand, the behavior here in making an unblock request is obsessing and bounds testing; fuel to the fire is the vagueness of the indef block, which must be frustrating.  Suggest changing the indef block to a two-month block to be followed by the start of the six-month topic ban.  Unscintillating (talk) 23:44, 11 December 2011 (UTC)[reply]
      • Support Unblock- basically because if this is opposed then we might as well add the following to the indef blocking policy: "An indefinite block is permanent and irreversible, with no possibility of appeal, under any circumstances, ever." What we have here is an editor who has contributed a lot of good stuff to the encyclopedia and can certainly continue to, but who has got himself in trouble by being obnoxiously opinionated and combative. After two months out of the game there is strong evidence of a change in outlook and a commitment to stay away from the areas that got him into trouble. What more can be demanded? Further, the long and messy discussion that led to the indef block was vague, confusing and frustrating to all involved, and I think indef blocks with a lingering air of dodgyness should be easier to reverse than clear-cut ones. If we unblock, there are two things that could happen. Either TT stays out of trouble, in which case we gain a productive editor, or he reverts back to being objectionable, in which case he can't do much harm because everyone will be watching him. Unblocking has only upside and no downside. If we refuse to unblock, TT's gone for good and it makes a joke of principles like WP:OFFER and "indef != permanent"- only downside and no upside. Thanks. Reyk YO! 00:49, 12 December 2011 (UTC)[reply]
      • Oppose, with great regret (sorry, TT, it's nothing personal) and noting my disagreement with the above comment by Reyk. To address Reyk's comment first, declining to unblock an editor at this stage does not banish them to the waste bin of history—it merely says that more time is required—and you would find me vehemently opposed to any proposal to permanently remove TT from this project. However, I do not feel that sufficient time has yet passed for TT to fully appreciate where he went wrong and for the wounds he caused to heal. TT has previously been unblocked under fairly lenient restrictions—themselves imposed to mitigate the potential for him to get himself into trouble in the same way that led to his original indefinite block—and made next to no effort to adhere to them, so I am sceptical that, just a few weeks down the line, he is ready to be released from his third indefinite block in six weeks. That said, I would very much like to see TT back at some point; I just feel that now is too soon. I would suggest another appeal once the block has been in effect for between three and six months. HJ Mitchell | Penny for your thoughts? 01:41, 12 December 2011 (UTC)[reply]
      • Support Unblock. It's been a little over two months since TreasuryTag was blocked, and, as demonstrated in his unblock request, he has clearly learned a lot from that experience. Furthermore, he has agreed to stay away from the topics and areas that resulted in him being blocked in the first place. Like those above, I'm more than ready to give him a chance to prove his worth and contribute constructively to the encyclopedia. -FASTILY (TALK) 01:46, 12 December 2011 (UTC)[reply]

      User:Greg L unblock request (baffling block) – December 2011

      I can't make any sense of the block of Greg L (talk · contribs), allegedly for disruption (the only evidence is to a discussion at Talk:Yogurt which was mostly caused by a misunderstanding, but was resolved much better and quicker than most disagreement I see on talk pages). Greg has asked for an unblock review, but so far no response from anyone. If I was so blatantly wrongfully blocked, I would hope someone would try to get the attention of an admin to unblock me, so here I am doing that for Greg. --Born2cycle (talk) 00:44, 12 December 2011 (UTC)[reply]

      If anyone should be blocked for disruption, it should be the admin who blocked Greg. --Born2cycle (talk) 00:51, 12 December 2011 (UTC)[reply]
      Agree with Born2cycle. The block by User:2over0 needs to be explained to the community. GFHandel ♬  00:54, 12 December 2011 (UTC)[reply]
      • I agree. 2/0 needs to explain his block to the community. It looks like a terrible block to me. I see nothing blockworthy in anything Greg said at Talk:Yoghurt. It looked like an animated but ultimately productive discussion to me. Reyk YO! 00:59, 12 December 2011 (UTC)[reply]

      This was 2over0's first action after 2 two weeks of inactivity and he hasn't done anything since, either. It looks as if there is only boilerplate text, so maybe he just pressed the wrong button somewhere and isn't aware of what he has done? (Admins will know better if that idea makes sense.) Or maybe his account is compromised or something.

      It seems pretty much out of character, so the situation should be monitored and maybe the account blocked if things don't get clearer soon. Hans Adler 01:02, 12 December 2011 (UTC)[reply]

      Given the extensive instructions at User:2over0#Security, it almost looks as if he suspected something like this to happen at some point. Hans Adler 01:05, 12 December 2011 (UTC)[reply]

      I have unblocked Greg L. There was no reason for him to be blocked at all, especially without any sort of warning or discussion from the blocking admin. Horologium (talk) 01:06, 12 December 2011 (UTC)[reply]

      To answer Hans's question, it is easy to block/unblock the wrong user if you regularly have a dozen tabs open at once. I've never done it, but I've protected/unprotected the wrong page before now!! However, this was the chap's only edit in two weeks, and only admin action in similar time. He doesn't appear to have been doing or looking at anything else on the project. Have to wait for an explanation I guess. Elen of the Roads (talk) 01:12, 12 December 2011 (UTC)[reply]

      Thanks to all for your help. I am now unblocked and able to edit. My block was indeed curious because 2over0’s contribution history shows he was off of Wikipedia for two weeks, dropped in to make just a single edit (block me) and immediately fell silent—even after others inquired on his talk page. I don’t profess to be super-expert on all-things-Wikipedia, but I do know human nature and find that unusual. Anyway, I very much appreciate my wiki‑friends stepping in here as well as other editors with whom I have had little-to-no interaction with stepping in here to do what they saw was the right thing. Regards. Greg L (talk) 01:36, 12 December 2011 (UTC)[reply]

      Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Administrators%27_noticeboard&oldid=465388101"