Jump to content

Wikipedia:Administrators' noticeboard

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Rd232 (talk | contribs) at 09:37, 26 October 2010 (conclude Rich Farmbrough issue). 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


    New AfD tool

    I have had an AfD parser available for a while, but due to some toolserver configuration changes it has broke, Since I am unable to fix the issue that caused the break I re-wrote my parser so that scans all active AfDs. A full listing of all parsed AfDs can be found at tools:~betacommand/reports/afd, However in the process of re-writing the tool I have also implemented a summary tool, its WP:RFASUM but for AfDs which can be found at tools:~betacommand/AFD.html if you have any questions,feature requests, or bugs please let me know. ΔT The only constant 14:52, 22 October 2010 (UTC)[reply]

    PS please note that you can sort that table by any column. ΔT The only constant 14:53, 22 October 2010 (UTC)[reply]
    I have already been finding this the best way to scan quickly the thousand or so open AfDs. Thanks! DGG ( talk ) 06:42, 24 October 2010 (UTC)[reply]
    Please note that you can easily tell if an AfD is expired by sorting on the expired column. (the tool uses the relist template to adjust expiration times when its relisted) ΔT The only constant 23:11, 25 October 2010 (UTC)[reply]

    What a cracking tool. Although I note it is reporting Wikipedia:Articles_for_deletion/Middle_Barton_F.C. as having a start date some time in 2006. Must be something odd in the date formatting for that particular one. --Elen of the Roads (talk) 22:59, 25 October 2010 (UTC)[reply]

    That's because the AfD in question was erroneously created over the top of an existing AfD. Δ, I bet you could explicitly detect such problems in your tool's report, if you're up for useful feature requests. — Gavia immer (talk) 23:07, 25 October 2010 (UTC)[reply]
    That would be because this particular AfD was filed in 2006, see [1] however that AfD was moved and a redirect replaced it pointing to the new AfD. Then it was Sent to AfD this time and the tool checks for the oldest revision to the AfD (when it was filed) and uses that (in this case the first filing not the current one). Not much I can do, this should rarely if ever happen again. ΔT The only constant 23:11, 25 October 2010 (UTC)[reply]

    Image restore

    A request for an admin to undelete File:National Organization for Marriage.gif as it was deleted for being orphaned when a user who meant to remove the Unbalanced tag also inadvertently removed the article's infobox containing the image in September and no one caught this mistake until I just did now. Thanks.   allstar✰echo  19:58, 22 October 2010 (UTC)[reply]

    Hi Allstarecho, I've restored the image. PhilKnight (talk) 20:02, 22 October 2010 (UTC)[reply]
    Thank you Phil.   allstar✰echo  20:04, 22 October 2010 (UTC)[reply]
    That's {{pd-textlogo}} anyway. Someone change the tag, find an SVG version, and transfer to Commons. /ƒETCHCOMMS/ 02:48, 23 October 2010 (UTC)[reply]
    Is it pd-textlogo, though? I think it's a debatable case, but I think interlocking rings may be unoriginal enough. Sceptre (talk) 14:01, 24 October 2010 (UTC)[reply]

    User:Off2riorob

    User has agreed to step away from CC for a few months. I'm hoping that can avoid yet another CC thread. Maybe some others need to voluntarily leave this issue alone for a while. Most of us uninvolved folk are now totally sick of it.--Scott Mac 13:56, 24 October 2010 (UTC)[reply]

    A few hours ago I blocked [[::User:Off2riorob|Off2riorob]] (talk · contribs) for 24 hours in response to a 3RR violation [2]. Upon further investigation, I found a lengthy series of problematic edits (see below), previous blocks, and at least one attempt at editing restrictions. He was previously placed on a 5 week 1RR sanction, which he stated he might continue of his own volition [3]. The blocks since [4], including the present block, seem to indicate a continued problem.

    • In light of these, I wonder if there is community support for a permanent 1RR restriction for Off2riorob.

    Some evidence of problematic edits:

    • April 2009: ANI discussion which resulted in a block. archived discussion The block was reduced when he showed remorse and an intent to improve [5].
    • August 2009: He was again blocked for edit warring [6] and again promised to desist in the future [7]. His block was again reduced[8].
    • July 2010: Personal attacks [9] (deleted edit), which resulted in a block.
    • October 2010: Petty vandalism [10] when questioned about recent reverts (archived discussion).
    • My block for 3RR on William Connelley.

    Keeping in mind he is currently blocked, does anyone have thoughts or suggestions on this? --TeaDrinker (talk) 06:15, 24 October 2010 (UTC)[reply]

    User notified --TeaDrinker (talk) 06:20, 24 October 2010 (UTC)[reply]

    Proposal: 1RR restriction

    • Regarding his most recent block, I didn't see a block notice that is customarily given when a block is issued. Did I miss it? Regarding the sanctions, I would support a 1RR sanction. In addition, Rob has been identifying as vandalism content disputes and using Twinkle in an inappropriate manner. I would also support removing his Twinkle access for now. Basket of Puppies 06:29, 24 October 2010 (UTC)[reply]
    • I agree with the proposal above by TeaDrinker and the comment by Basket of Puppies, and support a permanent 1RR sanction. (Note: Off2riorob was previously blocked for engaging in disruption at a GA-quality article that I wrote.) I would also support removing Off2riorob's access to Twinkle. -- Cirt (talk) 06:30, 24 October 2010 (UTC)[reply]
    • Support both. doesn't this belong on ANI? Access Denied [FATAL ERROR] 06:44, 24 October 2010 (UTC)[reply]
    • Support the proposed permanent 1RR restriction/sanction. Defer to others on Twinkle. I also note that in this November 2009 AN/I, the great bulk of his support was from ChildofMidnight, who has since been banned from Wikipedia for a year.--Epeefleche (talk) 06:47, 24 October 2010 (UTC)[reply]
      • … which is both irrelevant and outdated. (We have an article on what the Institute for Propaganda Analysis called transfer explaining why ChildofMidnight's endorsement is not relevant to Off2riorob's actions.) One could equally try to call Off2riorob a single-purpose account based upon what Cirt said in the April 2009 AN/I discussion. That's clearly outdated now, too. If the compelling evidence for action here is discussions from 2009, then I suggest that people take a look at Special:Contributions/Off2riorob. Early 2009, late 2009, and 2010 are not the same animal. We should not institutionalize hanging onto grudges like this. Uncle G (talk) 13:06, 24 October 2010 (UTC)[reply]
    • I'm not in principle opposed to a restriction, but what's wrong with the standard method of escalating blocks? If he doesn't comply with 3RR, he's not much more likely to comply with 1RR. If a restriction is to be imposed, somebody would need to spell out what exactly is being proposed here (one revert per page per 24 hours, I suppose?). Also, since the current edit war is in the climate change topic area, discretionary sanctions are also a possibility.  Sandstein  06:53, 24 October 2010 (UTC)[reply]
    • One revert per page per 24 hours seems most reasonable. -- Cirt (talk) 06:56, 24 October 2010 (UTC)[reply]
      • Agree that 1-revert-per-pg per-24-hours seems appropriate.

        As to escalating blocks, I note that Off2 was blocked for 24 hours (March 2009), 72 reduced to 48 hours (April 2009), 72 hours (April 2009), 1 week (April 2009), 24 hours reduced to time served (July 2009), 2 weeks (July 2009), 3 weeks (reduced on promise to desist edit warring in the future; August 2009), 31 hours (July 2010). All prior to this 24-hour block. Per our standard method of escalating blocks, which Sandstein refers to, it strikes me that the current 24-hour block is too low — it would have been appropriate for a first-time offender, but this editor has been blocked numerous times in the past year and a half, up to 3 weeks.--Epeefleche (talk) 07:22, 24 October 2010 (UTC)[reply]

    • Support I agree with the 1RR restriction. Off2riorob has also got into lengthy arguments and edit wars on the British National Party and other articles about the British far right, which he thought were written from an anti-BNP bias. TFD (talk) 13:32, 24 October 2010 (UTC)[reply]
    • Oppose And the BNP argument holds no weight with me. Too much sounds like "let's get even" with a valued editor. Collect (talk) 13:52, 24 October 2010 (UTC)[reply]

    Proposal: Climate change topic ban

    • Overall 1RR may be fine for Off2riorob, but one revert per day is 'too lenient for a CC articles. One revert per week is more in line with the type of editing restriction needed to get CC articles to have stability. Otherwise, the result will be tag team edit warring that would be supported by the editing restrictions. I suggest Off2riorob be put on a stricter restriction for the CC articles. FloNight♥♥♥♥ 10:11, 24 October 2010 (UTC)[reply]
      • Completely stepping away from the CC topic (and any other areas where Off2riorob gets heated and loses control) is a better restriction than a blanket 1RR which allow too many problematic edits on controversial topics and perhaps too few where otherwise needed. If there are overall problems beyond reverting then that needs to be determined (maybe with a RFC or ArbCom case) and further editing restrictions or bans can be imposed. So, I support a complete CC topic ban for now. FloNight♥♥♥♥ 13:29, 24 October 2010 (UTC)[reply]
    • I think now would be a good time to ask Off2riorob to step away from the climate change topic entirely. For technical reasons it is not possible at this stage to propose a topic ban at WP:AE, but the conclusion seems reasonable. He is by all accounts a very productive editor elsewhere, but as he admits himself he has a bee in his bonnet about William M. Connolley. --TS 12:05, 24 October 2010 (UTC)[reply]
    • Oppose A 1r restriction on an editor who mostly works BLP`s and the BLP noticeboard would hamstring him from the productive work he does. Everyone make`s mistakes, he ought not be overly punished for this one. mark (talk) 12:39, 24 October 2010 (UTC)This editor is topic banned from processes related to climate change, broadly construed. --TS 12:51, 24 October 2010 (UTC)[reply]
      • Making multiple reverts shouldn't be required in BLPs any more than anywhere else; remember that removing contentious, unsourced information about living persons is one of the exceptions to 3RR and by extension to an imposed 1RR. GiftigerWunsch [TALK] 12:42, 24 October 2010 (UTC)[reply]
        • Yes but there`s the rub, what if it is sourced but not written in a NPOV manner? Or as an attack piece? We see such on BLP`s all the time, if he is restricted to 1r he will quite simply be unable to work the BLP noticeboard. Why not a simple restriction of 1r on this one article? I think that would be more suitable given the nature of this offence mark (talk) 12:47, 24 October 2010 (UTC)This editor is topic banned from processes related to climate change, broadly construed. --TS 12:51, 24 October 2010 (UTC)[reply]
    • I agree with Tony Sidaway, and I suggest that people look away from AN/I to all of the work that Off2riorob does at the Wikipedia:Biographies of living persons/Noticeboard. The slice of history presented here purports to cover a year's worth of editing but is very limited and one-sided, and really isn't the whole picture by any means. It reflects, I suspect, the area where Off2riorob is influenced to err by (a) xyr perception of climate change POV-pushing and (b) the proximity of a subject to Wikipedia itself.

      Contrast that to xyr work at (to pick just one BLPN example) Ed Miliband where xyr work has been edits like this one and efforts to stop our article from labelling Miliband (who has stated for the record that xe does not believe in God) as "the Jewish leader of the Labour Party" and having religion=Jewish in an infobox. When the biography is not climate-change related or close to Wikipedia, there's a rather different Off2riorob here. There's also a significantly different Off2riorob now to the one that Cirt characterized in April 2009, the discussion of whom is being used as evidence for action here. Uncle G (talk) 13:06, 24 October 2010 (UTC)[reply]

    I agree that in considering Off2riorob's editing history we must look at this work at BLPN - I'd be sorry to lose his help there. Dougweller (talk) 13:38, 24 October 2010 (UTC)[reply]
    • Would a community topic ban from Climate Change articles, following the wording of those recently applied to various editors by ArbCom, and a permanent ban from the William Connolley article suffice? LessHeard vanU (talk) 13:23, 24 October 2010 (UTC)[reply]
    • Oppose(ec) Off2 was not mentioned in any CC arbcom discussions, and imposing a topicban is absurd over-reaction. He is a valued editor, and all of this is simply going to be a matter of "let's remove anyone we disagree with" type rationale. In other words -- why not openly say "anyone with any position on CC whatever is to be topic-banned ab initio" as the easiest way to deal with the topic? Nope. Draconian solutions generally do not work, and all this will do is make that more abundantly clear than ever. Meanwhile the BNP is so far rremoved from any reasonable argument on this as to be quite nicely irrelevant - we ought not have personal disagreements with anyone dictate banning a good editor who, as I noted, was never even mentioned at the arbcom discussions on CC. Collect (talk) 13:51, 24 October 2010 (UTC)[reply]
      It's not about opinion, it's about behavior. He edit warred on a BLP in a topic area that was under arbcom-imposed sanctions. The only reason he isn't being topic banned at WP:AE is that arbcom sanctions require prior formal notification. The community has the opportunity to say "enough is enough." --TS 13:54, 24 October 2010 (UTC)[reply]
      The entire point of discretionary sanctions is to allow for editing restrictions for users not named in the ArbCom case. So, this editing restriction is perfectly reasonable given his edit warring on a CC related article within days of the case ending. I see no problem with discussing this here since this is where the discussion started. FloNight♥♥♥♥ 13:59, 24 October 2010 (UTC)[reply]

    Questions

    1. Can each user please state their level of involvement (if any)? Ncmvocalist (talk) 13:53, 24 October 2010 (UTC)[reply]
    2. Why can't ArbCom discretionary sanctions deal with the CC related matters? Why does the Community need to relitigate this aspect here at WP:AN rather than WP:AE? Ncmvocalist (talk) 13:53, 24 October 2010 (UTC)[reply]

    Metadiscussion

    • Question Why was the above discussion archived? I understand that Rob has agreed to modify his editing, but the consensus seemed to be in favor of a 1RR restriction and, possibly, revokation of Twinkle. Basket of Puppies 16:16, 24 October 2010 (UTC)[reply]
      • Because it seems more urgent to de-escalate the CC fiasco, than to worry too much about the rest of it. Besides, after Rob had agreed to step away from the immediate flashpoint, nothing else needed urgent admin action. If you want to pursue more general complaints, then I suggest a user RFC is the normal way.--Scott Mac 16:24, 24 October 2010 (UTC)[reply]
    It's been closed because the issue was resolved and, as Doc has correctly stated, the community is sick and tired of the subject. Tasty monster (=TS ) 16:21, 24 October 2010 (UTC)[reply]
    I am only confused as to why this discussion was closed, seemingly out of process. Isn't it against consensus to close a discussion where a consensus has nearly been reached? The underlying issue of Rob's behavior isn't much of a concern to me as the issue of prematurely closing a discussion. Basket of Puppies 16:31, 24 October 2010 (UTC)[reply]
    And doesn't this belong on /Incidents anyway? Access Denied [FATAL ERROR] 16:32, 24 October 2010 (UTC)[reply]

    It is in the interests of this project to allow issues associated with CC to cool. Rob has seen that, and we should thank him for it and drop this. Sanctions are always a piss-poor substitute for getting agreement and peace. The technicalities of which board and broken process are worthy casualties of drama-ending. Now, walk away. This has ended as well (indeed a lot better) than any other possible ending. And I, for one, don't wish to waste any more time on CC and those who can't let it go.--Scott Mac 16:48, 24 October 2010 (UTC)[reply]

    That was unnecessarily dramatic. Basket of Puppies 17:36, 24 October 2010 (UTC)[reply]
    • I disagree with the closing of the thread. Way too early. And there is no reason to roll it up, other than to conceal its contents from future searches. I don't believe Scott's action in in line with the sentiment of the community on this page. And I don't think his and editor Tasty (who is "sick and tired of the subject" after under 1,000 edits) are reflecting the sentiment on this page in suggesting that we should sweep it under the rug because of their sense that the community prefers that. Rob has made agreements before, which triggered sanction reductions -- and which he has just violated with his edit warring here. --Epeefleche (talk) 18:16, 24 October 2010 (UTC)[reply]
      • Have you discussed your concerns with Rob? If so, unless there's need for urgent admin action, I'd suggest that a user RFC is the place to take ongoing concerns. (For your info Tasy = User:Tony Sidaway, not that the edit count should really matter).--Scott Mac 19:13, 24 October 2010 (UTC)[reply]
    • Let's be clear here. This was quid pro quo. Scott Mac did exactly what he promised, shut down discussion, on the basis of Rob's consent. My personal opinion is that's entirely OK and within the scope of administrator discretion to "talk someone down" like that, but I think that Scott should have been a bit more open here about the deal he offered and concluded. Jclemens (talk) 20:45, 24 October 2010 (UTC)[reply]
    Not sure. However, the user that hatted the thread, noted he did not read it at all: "discussion of whatever it is that they are discussing on AN, and which I am not even going to bother looking at." Most inappropriate to archive and declare something as closed, which one has not even bothered to read. -- Cirt (talk) 21:35, 24 October 2010 (UTC)[reply]
    • This constant hatting of discussion without notification or warning is leaving multiple users (myself included, and i'm not even involved in the discussion) with a sense of bad faith toward the hatters. SilverserenC 22:08, 24 October 2010 (UTC)[reply]
      • I think it should be closed, Rob learned his lesson, no one wants to ban him or but any restrictions on him. He does an excellent job with BLPs, so I'm against any sactions for him. Secret account 00:18, 25 October 2010 (UTC)[reply]
    • Proposal that we all agree to refrain from hatting/archiving/similar action threads when there is ongoing discussion. Additionally, for the hatter/archiver/similar to read and understand what they are doing before the action is undertaken. Agreed? Basket of Puppies 02:20, 25 October 2010 (UTC)[reply]
    • Comment. From what I can read (in what has been rolled up), it appears that the close was a unilateral one done against consensus at the time. In fact, broad comments used by the closer as a basis for the non-consensus closing such as "Most of us uninvolved folk are now totally sick of it" are not supported by the comments of "most of us uninvolved folk" on this page, and I find such comments to be quite curious (as well as contrary to what my own guess would be, reading this thread). I understand that such a non-consensus close is contrary to our core consensus guideline (which, though I agree with the remarks about hatting/archiving, I view as an even graver problem with the goings-on in this string).--Epeefleche (talk) 04:04, 25 October 2010 (UTC)[reply]

    Wikipedia:Miscellany for deletion/User:Geo Swan/review and Wikipedia:Miscellany for deletion/User:Tiamut/Palestine

    Resolved
     – I got one, and User:Horologium closed the other. --RL0919 (talk) 13:48, 24 October 2010 (UTC)[reply]

    Would an admin (or admins) close Wikipedia:Miscellany for deletion/User:Geo Swan/review and Wikipedia:Miscellany for deletion/User:Tiamut/Palestine? Thanks, Cunard (talk) 06:56, 24 October 2010 (UTC)[reply]

    I closed the first one, but I had a personal opinion on the second, so I commented instead. --RL0919 (talk) 13:28, 24 October 2010 (UTC)[reply]

    BLPs and maintenance tags

    I invite participation at a discussion here: Wikipedia:Biographies of living persons/Noticeboard#Maintenance tags. Guy (Help!) 14:03, 24 October 2010 (UTC)[reply]

    Banned users and their userpages

    At this deletion discussion, an issue has arisen concerning a banned user and whether his User page should have the "banned" template while his User Talk has the same template.

    I seem to remember that banned users do not always have a "banned" template placed on their user page, such as when they have retired. I'm also sure there have been instances where a banned editors user page has been blanked for the duration of the ban. Does anyone know of more details or the circumstances? Or is my memory failing me? :( Ncmvocalist (talk) 18:04, 24 October 2010 (UTC)[reply]

    If someone is commenting on this, it may be better to comment here, so the discussion doesn't fork off in three ways (it's also happening at the MfD). /ƒETCHCOMMS/ 21:16, 24 October 2010 (UTC)[reply]

    Rich Farmbrough's persistent disregard for community norms and (semi-)automated editing guidelines

    See also: Wikipedia:Administrators' noticeboard/Incidents/Rich Farmbrough/January 2009-September 2010
    See also: Wikipedia:Administrators' noticeboard/Incidents/Rich Farmbrough/October 2010
    Rich Farmbrough (talk · contribs · count · logs · block log · lu · rfas · rfb · arb · rfc · lta · socks)
    SmackBot (BRFA · contribs · actions log · block log · flag log · user rights)

    Earlier today, I advised Rich Farmbrough (talk · contribs) that I would request both he and his bot be blocked if he continued making trivial and unnecessary changes that have proved controversial without first obtaining consensus for these changes [12].

    Rather than cease making the changes, he simply went on ahead with them on both his bot account ([13] [14] - unnecessary capitalization changes), and his main account ([15] changes spacing around header for no reason; [16] capitalizes template for no reason).

    It is perfectly reasonable to hold the view that all templates should be ucfirst, it is perfectly reasonable to hold the view that headers should have no spacing around them. However, it is unreasonable to push these views on the community without first obtaining consensus for them. The edits today display a shocking disregard for the collaborative editing model and indicate that Rich feels that he does not have to operate within the consensus model.

    This is unacceptable behaviour for a bot operator and administrator and I request he be blocked pending the decision of the proposed restriction below, which has been copied here from the ANI subpage for greater visibility. –xenotalk 22:10, 24 October 2010 (UTC)[reply]

    Proposed editing restriction: Rich Farmbrough

    This is an alternative proposal to more strict proposal here, which generated a fair amount of support for a complete ban on non-manual editing

    Regardless of the editing method (i.e. manual, semi-automatic, or automatic; from any account), Rich Farmbrough (talk · contribs) is indefinitely prohibited from making cosmetic changes to wikicode that have no effect on the rendered page (excepting those changes that are built-in to stock AWB or those that have demonstrable consensus or BAG approval). This includes but is not limited to: changing templates to template redirects, changing template redirects to templates (see here for AWB stock changes on this item, with the understanding that bypassing template redirects will only be done when there is a substantive edit being done), changing the spacing around headers and ordered lists (except to make an aberration consistent with the rest of the page), and changing the capitalization of templates. Furthermore, prior to orphaning/emptying and deleting categories or templates, the appropriate processes (WP:CFD/WP:TFD) should be engaged.

    Thoughts? –xenotalk 15:09, 22 October 2010 (UTC)[reply]

    What about emptying and deleting categories? This is what happened in the immediate incident. --Philosopher Let us reason together. 15:21, 22 October 2010 (UTC)[reply]
    Added a sentence, though that is expected of any editor already. –xenotalk 15:25, 22 October 2010 (UTC)[reply]
    Unless a guideline directs such a change. There's always the potential for future guidelines on the matter. Otherwise, it seems a fine proposal to me. --Bsherr (talk) 15:28, 22 October 2010 (UTC)[reply]
    That's covered by 'demonstrable consensus'. –xenotalk 15:29, 22 October 2010 (UTC)[reply]
    Indeed. Good enough. --Bsherr (talk) 15:31, 22 October 2010 (UTC)[reply]
    • Support --Bsherr (talk) 16:48, 22 October 2010 (UTC)[reply]
    • I think this is agreeable, this has my support. Rich, I hope you will do an effort in checking the diffs before you save, and not save them if they are mere changes of capitalisation, etc. Real mistakes, well, we all make them (as do our bots), I do hope your fellow editors will treat them for what they are. --Dirk Beetstra T C 15:38, 22 October 2010 (UTC)[reply]
    • Now that's a whole lot better, being a lot less disruptive and punitive. But how about discussing with Rich about the categories' name changes and moving, instead of immediately reaching out for punishment? --Ohconfucius ¡digame! 15:40, 22 October 2010 (UTC)[reply]
    • Comment. This proposal is more about setting a bot policy rather than addressing or remedying the allegations. Bot policy should be debated elsewhere. Glrx (talk) 17:25, 22 October 2010 (UTC)[reply]
      Policy already exists to prohibit these changes (WP:AWB#Rules of use #3/4), this is more of a compliance issue. –xenotalk 19:11, 22 October 2010 (UTC)[reply]
    • We're prohibiting him from something that's already prohibited (using a bot or script to make cosmetic changes) and telling him to use the processes that he's already supposed to be using (CFD/TFD). Is there any substantial difference here from doing nothing and hoping the problem resolves itself? Mr.Z-man 21:24, 22 October 2010 (UTC)[reply]
      • I suppose there's also the prohibition of using even manual methods to make those cosmetic changes, and it looks like even if those cosmetic changes are made at the same time as another edit they would still be disallowed (without bot approval, which I suppose is already bot policy). To my mind this is just because it's difficult at times to tell if Rich is making manual, semi-automated or fully automated edits from his account (because, as you know, in violation of the bot policy he appears to make all three from his main account, without using proper edit summaries). Personally I think we should be stopping this problem there. With enforcing the bot policy and stopping him from making any bot like edits from his account, as proposed above. But would also support this alternative proposal after the original one. - Kingpin13 (talk) 21:34, 22 October 2010 (UTC)[reply]
      • The restriction would make it clear that these changes lack consensus and he may be blocked if he continues making them prior to gathering consensus. –xenotalk 22:10, 24 October 2010 (UTC)[reply]

    Nonsense

    This is a storm in a teacup. No one cares about the bot capitalising clean-up templates, except that they think I am offending others by doing it. There are no others, except apparently xeno has moved to-day from neutral about it ("I don't care about the actual minor bits themselves") to opposed ("Me for one") and dePiep is saying the same in the next comment (about 20 minutes ago). Hardly anyone cares about any of them. Those that do have an opinion would almost certainly, by the figures, support capitalising of Infoboxes. I have explained that for technical reasons that I made a choice, some four years ago for Ucfirst rather than lcfirst - after much careful thought. the reason is to enable me to write regexes like:

    • {{\s*(Cleanup|Attention[ _]+\(on[ _]+talk[ _]+page\)|Clean|Cu|CU|Tidy|Cleanup-quality|Cleanup-date|Attention[ _]+needed[ _]+\(article[ _]+page\)|Attn|Attention[ _]+see[ _]+talk|Attention|Attention[ _]+needed[ _]+\(talk[ _]+page\)|Clean[ _]+up|Cleanup-because|Clean-up|Cleanup-reason|Cleanup-since|Ugly|Cleanup-Pitt|Improve|Quality|Clu) *([\|}\n]) => {{Cleanup$2

    and then do the date manipulation on a much simpler regex - a sample of which still runs to maybe 4 or 5 k.

    Here's my proposed solutions:

    1. Forget it and go and write an enyclopedia.
    2. Have an centralized discussion on the case of cleanup templates. Tell me the result. I will implement that.

    Rich Farmbrough, 22:38, 24 October 2010 (UTC).[reply]

    Your dismissive attitude ("No one cares..."; "Forget it and go and write an encyclopedia."; "There is no controversy here. Nothing to see, keep walking.") is a major part of the problem.
    I don't know how many people care about this, but I can tell you that I do. When I consult diffs to evaluate the edits, your bot's inconsequential changes waste my time. I've gone to your talk page to raise the issue, only to be reminded by the existing complaints (and your [non-]responses thereto) that you routinely ignore/dismiss such criticisms. So I don't bother to add my voice to the futile chorus (and I assume that others act in kind). —David Levy 23:56, 24 October 2010 (UTC)[reply]
    Well not bothering hardly helps. Nor does the negative characterisation of my talk page. Nor yet quoting out of context.Rich Farmbrough, 00:05, 25 October 2010 (UTC).[reply]
    Well not bothering hardly helps.
    Nor does wasting still more of my time by posting yet another comment for you to dismiss/ignore.
    Nor does the negative characterisation of my talk page.
    You mean my observation that you routinely dismiss/ignore these criticisms (just as you've done above)?
    Nor yet quoting out of context.
    How have I done so? Two of the quotations are taken from this very section, and I linked directly to the third's diff. —David Levy 00:25, 25 October 2010 (UTC)[reply]
    The diff is not the context. The context is an extensive conversation over several pages. Rich Farmbrough, 00:43, 25 October 2010 (UTC).[reply]
    Please link to whatever threads/diffs you believe provide essential context. —David Levy 00:57, 25 October 2010 (UTC)[reply]
    Incidentally on the substantive point you raise, you can set your w/l to ignore bots. HTH. Rich Farmbrough, 00:07, 25 October 2010 (UTC).[reply]
    And that would not be a reasonable solution. Sometimes people will still want to see bots. We shouldn't have to stop seeing other bots because yours is behaving badly. I will have to agree with the other people in that these edits cause more trouble than help. -DJSasso (talk) 00:18, 25 October 2010 (UTC)[reply]
    I'm well aware of that. I don't want to ignore bots (which would cause me to overlook problematic mass changes, including those caused by malfunctions). I want to be able to monitor their edits without having to wade through the utterly pointless ones that your bot performs. —David Levy 00:25, 25 October 2010 (UTC)[reply]
    I'd add on that score that ignoring bots seems to cause another issue: if, say, an editor vandalises a page, (edit 1) then a bot goes past and makes a change, (edit 2), nothing turns up in your watchlist. As you are set to ignore bot edits, the watchlist code doesn't notify you of any edits, as it only checks to see if the most recent one warrants notification. Thus you are lead to assume that nothing has happened in the article. I found this to be a particular problem with SineBot, but generally that flag causes too many issues to use it. - Bilby (talk) 02:59, 25 October 2010 (UTC)[reply]
    Well as not a great user of watch-lists, I had seen that comment before, but not got round to investigating it. It seems like a suboptimal way for watch-lists to work. Rich Farmbrough, 18:47, 25 October 2010 (UTC).[reply]
    "Expand watchlist to show all changes, not just the most recent" should bypass that particular concern. –xenotalk 18:49, 25 October 2010 (UTC)[reply]
    Also vote for bug 9790. Rich Farmbrough, 02:31, 26 October 2010 (UTC).[reply]
    • Regarding your explanation regex: AWB can do this with the stock engine now without having to change the case (WP:AWB/TR). This is why I asked you to update SmackBot to the latest SVN snapshot. And you're right, I said I don't care about the minor bits themselves - I do care about the unnecessary, disruptive, and distracting changes to the minor bits that lack consensus - I would similarly ask an editor who was going in the other direction to stop. –xenotalk 15:05, 25 October 2010 (UTC)[reply]
      I have uploaded my redirect list, so that should help AWB. There are teething problems here, yet. For example trying to maintain ucfirst/lcfist across redirects has lead to imdb => iMDb name. But there are other problems with template names that are bigger than these minor quibbles. Rich Farmbrough, 02:34, 26 October 2010 (UTC).[reply]

    What actually needs to be done now: Need an uninvolved admin

    I think, at this point, we've discussed this to death. What I think we need is an uninvolved admin who has maybe a couple of hours to read up on this, and then close the discussion and editing restriction proposals at Wikipedia:Administrators' noticeboard/Incidents/Rich Farmbrough/October 2010. A number of different remedies have been offered there, and I think a closing admin can judge a suitable consensus on how best to proceed. I don't think it's worth our time talking about this all over again at this point. Especially when the previous discussion hasn't yet been closed. At this point I feel that the discussion and editing restriction proposals are ripe for closure, as that thread is no longer constructive (it appears to have degenerated to edit warring, repetition, and personal comments, rather than actually furthering discussion on the actual issue tat hand, despite this I think there is already enough content there to reach a consensus). If the solution provided by a closing administrator does not work after some time, then there are other venues, such as a RfC/U, which would be more appropriate, since it appears ANI is not helping this issue much. - Kingpin13 (talk) 09:13, 25 October 2010 (UTC)[reply]

    Agreed. Fram (talk) 09:29, 25 October 2010 (UTC)[reply]

    Yes, we need an uninvolved admin to step in here. Subsequent to this thread being posted, Rich made nearly three thousand edits with SmackBot [17] that 1) do not appear to have BAG approval (I found this, but perhaps it should be revisited - approval should not have been granted for spell-checking) and 2) appear to violate the bot policy on spell-checking (based on new information what happened was the operator had set it wrong, as opposed to the bot running amok) and 3) made obviously erroneous edits like this [18]. We have policies and guidelines on automated and assisted editing for a reason, and flagrant disregard for those norms is unacceptable, especially when the result is editors having to manually review thousands of bot edits for errors. –xenotalk 14:06, 25 October 2010 (UTC)[reply]

    That's a bit of a rabbit out of a hat. "editors having to manually review thousands of bot edits for errors". Rich Farmbrough, 17:31, 25 October 2010 (UTC).[reply]
    Should I assume the one edit I picked out at random and found to be in error was 1 in 3000? Are you going to check the rest of the edits yourself? (I see you ran over the pages to fix World Series of Poker back to how it should be - Thanks for that). –xenotalk 17:59, 25 October 2010 (UTC)[reply]
    Yes I picked up a bunch of other WSOP errors too. Rich Farmbrough, 19:13, 25 October 2010 (UTC).[reply]
    • He also made this edit which does nothing but capitalize a template while tweaking some whitespace. Making disputed edits while they're under discussion at a noticeboard strikes me as inflammatory. –xenotalk 14:23, 25 October 2010 (UTC)[reply]
      Again human error, some small task I started nearly a week ago, and that item was already fixed - by an unassisted human. (I won't say why the task is taking so long - I will mention that it would have just happened in the good old days prior to 29 Spetember.) Rich Farmbrough, 19:13, 25 October 2010 (UTC).[reply]
      So you had it in auto-save mode? –xenotalk 19:19, 25 October 2010 (UTC)[reply]
      Uh.. borrow my deerstalker and meerschaum xeno, they are freshly cleaned. One edit on it's own is very unlikely to be automatic. No I just flipped windows, scanned the diff for errors (which is as automatic for me as reading - look at a printed word and try not to read it) clicked "save" and uttered a choice expletive. Considered reverting myself, but that's a bit nutzoid on a practical level - creating an extra edit to show that you aren't deliberately creating extra edits. Rich Farmbrough, 02:31, 26 October 2010 (UTC).[reply]
    Hmm .. indeed, that last one should not be there. I don't think that I saw any spelling-changes. Most decapitalisations seem OK and proper, but there are some decapitalisations in headers which should actually be capitalised (like the example you gave). Xeno, did you point Rich to these edits, and asked for explanations on the errors and .. useless edits? --Dirk Beetstra T C 14:39, 25 October 2010 (UTC)[reply]
    Yes, but because of obfuscation and handwaving, I've just about exhausted my patience for speaking directly with Rich. (Further reading: Wikipedia talk:Manual of Style (capital letters)#Capitalisation of section titles, Wikipedia talk:Bots/Requests for approval#Probably erroneous approval for a form of spell-checking (SmackBot)) –xenotalk 14:44, 25 October 2010 (UTC)[reply]
    Handwaving! I have supplied pretty much the only hard facts , the majority of the argument is fuzzy to an extreme. Rich Farmbrough, 17:31, 25 October 2010 (UTC).[reply]

    Uninvolved admin would be good. But if they can get through it in a couple of hours I would be amazed. This debate has eaten hundreds of hours of my time, and every time we get close to closing it down there is a change of venue. Rich Farmbrough, 17:31, 25 October 2010 (UTC).[reply]

    Funny enough, I do think that this edit contains two 'errors' .. one title which is probably correct in the current case was (half) converted to a lower case title, while the next section, which should have been converted, was neglected. Whatever the case, I don't think that this gets over 28 errors (i.e., less than 1%; I still refuse to see the capitalisation/whitespace change as an error, I do define it as 'useless'. And though I also think that of the fuss about it is equally useless: Rich, is there really no way of not doing that, it is certainly not necessary (run regexes on the wikitext with the 'i' parameter and it does not care whether it is upper or lowercase, so why uppercase them all), and it will stop the equally, if not more, unnecessary complaining about it?). I also don't think that this falls under a spelling correction, and I do think that it is important enough to be done by a bot - unfortunately it is too error prone (I would suggest to add the standard ones, and record all the rest with statistics, if there are other common ones which need conversion, add those to the list, but be careful with converting them all).
    All these discussions are not worth this fuss, Smackbot makes by design on every task some errors, some inevitable and some avoidable - others should be repaired (and are generally repaired) before continuing. The errors are minimal, diverse, and IMHO Rich either explains that some errors can not be avoided (e.g. the subst problem), most errors don't break things (they annoy people), and for the rest, a lot of complaints are about useless edits. I understand that the regular errors do give a feeling of 'Smackbot makes a lot of errors', but overall I don't believe that there are really thàt many (and then, some are because the bot is fed a broken page to begin with; or other errors which can not be repaired, still get regurgitated over and over). I also think that many errors were resolved, but also still regurgitated. Now, if we take away the annoyances (I suggest that Rich tries to take most annoyances away, and the annoyed to stop complaining about these things that IMHO do not need this much complaining; it is not worth it), and that future errors are met with 'could you do this different, or ignore these terms' (which I then also expect Rich to follow), then it is now time to move on. --Dirk Beetstra T C 19:28, 25 October 2010 (UTC)[reply]
    I actually don't have a huge problem with honest-to-goodness errors; it's the fixing things that aren't broken that I take issue with. As best as I can tell, the main excuse (other than ILIKEIT) for the template capitalization changes is because it's easier to write a regex that results in capitalization changes. Well, that's not a good excuse, and regex can fairly easily be written to maintain the case (and I know Rich is a wizard when it comes to these things - he helped me with some code for Xenobot Mk V); and in fact, AWB now has built-in redirect bypassing at WP:AWB/TR that won't do the unnecessary capitalization changes. So if Rich just worked within that framework, we can be done with this. –xenotalk 19:36, 25 October 2010 (UTC)[reply]

    Conclusion

    This Gordian knot clearly needs cutting, and I hereby cut it: the restriction proposed above is enacted. In essence, Rich is injuncted from making cosmetic changes which do not have demonstrable community support; this is recorded at Wikipedia:Editing restrictions#Placed by the Wikipedia community and as usual enforceable by escalating blocks. I will also clarify that there is no currently demonstrated community consensus on capitalising template calls. In addition, I will say to Rich that the community recognises and appreciates the work you do in using and maintaining a range of powerful tools, but that with power comes responsibility, and you do need to ensure that you err on the side of caution in ensuring that these powerful tools, and your use of them, has sufficiently strong community support. That is all. Rd232 talk 09:37, 26 October 2010 (UTC)[reply]

    Climate Change: enough is enough!

    As an uninvolved admin, I thought the end of the arbcom case would draw a line under this, by spelling out to all those obsessed with it that the community had simply had enough. However, it seems that the participants haven't quite got the message.

    Since the closing of the case, we've had wikilawyering over whether the letter of the topic ban allowed banned users to contribute to the articles by posting comments on their talk pages ("what does topic banned mean?"). We've had two threads on this board regarding disputes.[19] [20] (And probably more I've missed.) And now we've got a dispute on Wikipedia:Arbitration/Requests/Enforcement#Marknutley about whether a banned user can carry on commenting on sanction on another involved user.

    I am thoroughly sick of this. There's a point where some people are simply refusing to hear the community saying "ENOUGH". I thus propose that uninvolved admins agree the following:

    1. Topic banned means "find a different topic", and shall be very broadly construed. It's that simple: take the related articles (and users) off your watchlist and do something else.
    2. Given that the problem wasn't content, so much as the unacceptable interactions between the participants, the ban shall be taken to mean the participants should cease all hostile (or conceivably hostile) interactions. They should cease to comment on each other entirely.
    3. All other editors, who have been party to the conflict, are strongly urged to consider stepping back from the topic - including commenting on enforcement.
    4. Continued hostilities by any user in this area are likely to result in speedy blocks, without too much regard for who started it. All reasonable blocks will be endorsed without lengthy discussion and rule-mongering.

    I'm sure I'm not the only one who's had it with this.--Scott Mac 14:57, 25 October 2010 (UTC)[reply]

    • Leaning to support Put simply, the ruling means that these users are no longer invited to contribute to the shaping of Wikipedia's Climate Change related articles. If other editors act improperly then the topic banned users' contribution is not needed to correct it - uninvolved editors without a history of poor judgment and conduct in the topic area will comment if comment is needed; their comment is not. The ruling is also not intended to swap one major dispute for many small user page disputes. If the topic is raised on a user page the answer is "I am topic banned from responding, please ask [[useful link|here]]". However careless blocking "without too much regard" is not a good response. FT2 (Talk | email) 15:22, 25 October 2010 (UTC)[reply]
    • Support. As another Arb wrote ( Carcharoth, at [21], "My intention, when voting for the topic bans, was that those topic-banned would stay away from the topic area completely (as Beeblebrox has said). If we (ArbCom) had intended to allow limited discussion of sources on user talk pages, we would have made provisions for that. As we didn't, there are no provisions for that to take place." This has gone on long enough. I'm with Scott Mac. —Preceding unsigned comment added by Dougweller (talk • contribs) 15:27, 25 October 2010 (UTC)[reply]
    • Support there is a time for discussion, and a time to knock some heads together. I think the latter has arrived. Jclemens (talk) 15:52, 25 October 2010 (UTC)[reply]
    Note - I've proposed an update to the policy explanation of topic bans to clarify these issues/loopholes, as they affect all topic bans, not just Climate Change related ones. FT2 (Talk | email) 16:09, 25 October 2010 (UTC)[reply]
    • Admins should be able to impose sanctions under CC discretionary sanctions if there is a problem, and the only possible reason any CC related issues should pop up here is in the event of a well-timed and well-framed appeal/review request/special notification. If AE has already dealt with an issue (such as by issuing a warning), it's unhelpful to propose a CC specific sanction at AN or ANI ~10 hours later (in circumstances where no other DR has occurred and the editor has made no other edits since the time that AE thread was closed). Certain users and their approaches are the problem - not the drafting. Therefore, I oppose shaping the rest of the project more (or even less) aggressively because of a single topic area - CC - that is out of control. "I am thoroughly sick of this" hits the nail on the head. Ncmvocalist (talk) 16:28, 25 October 2010 (UTC)[reply]
    • The ArbCom was quite explicit about the intended scope of the topic bans that they imposed, though there does seem to be some attempt by several editors to rewrite those provisions. The case remedies already allow uninvolved administrators to impose discretionary sanctions in response to conduct which is harmful to the project. It is not clear to me why another thread needed to be started here; poor judgement on Scott Mac's part, I think, to ignite another fire to no useful effect. TenOfAllTrades(talk) 16:26, 25 October 2010 (UTC)[reply]
      • Ignite a fire? Help, can't you see the forest is ablaze already. My intention is to draw a line in the sand by saying that those trying to continue this war by other means need to "get it". The topic bans are not limited restrictions, they are intended to close the whole chapter. Some people obviously haven't got this at all.--Scott Mac 17:06, 25 October 2010 (UTC)[reply]
    • Oppose I am very sympathetic to the community reaction to the CC mess. As Ncmvocalist puts it: " 'I am thoroughly sick of this' hits the nail on the head." That said, I don't see how this proposal helps. The numbered list of statements either matches the ArbCom findings or it does not. If it matches, it is redundant, if it does not, it suggests that this group can overturn an ArbCom decision with a simple vote (or !vote). I see deficiencies in the ArbCom decision, but think there are better ways to address it. (FT2's link is a start). I'd also note that hostilities are winding down, and perhaps just letting the AE process get sorted out would be a better approach.--SPhilbrickT 17:15, 25 October 2010 (UTC)[reply]
    There's nothing new in my proposals. They simply are intended as an opportunity for us to say that we will not brook anyone wikilawyering around the spirit of what arbcom has said, and we will have zero tolerance with people simply continuing disputes in some way that arbcom didn't explicitly prohibit. Banned editors should move on entirely, and not pop up in discussions of the userconduct of their old opponents.--Scott Mac 17:28, 25 October 2010 (UTC)[reply]

    Support: FGS ban the lot of them and delete the subject for ever. It's not that I am unsympathetic to polar bears having to live off bananas and the starving millions having to take skiing holidays (I am recycling my yogurt pots and newpapers to help them) but enough is truly enough. This bickering has gone on far too long - let's talk about sex or something interetsting we can all join in.  Giacomo  18:15, 25 October 2010 (UTC)[reply]

    Support 1: those banned are banned inter alia from participating in any Wikipedia process relating to those articles. End of. Rich Farmbrough, 19:24, 25 October 2010 (UTC).[reply]

    • Oppose. This forum seems rather the wrong venue for these suggestions. If the existing ArbCom sanctions/remedies are insufficient, a request for amendment is in order. If the meaning/scope of topic bans is in question, a request for clarification can be filed. However, in the presence of a recent ArbCom ruling, trying to introduce additional restrictions, particularly in relation to the Arbcom topic bans, in another venue, seems to be a recipie for confusion and chaos. Nsk92 (talk) 20:04, 25 October 2010 (UTC)[reply]
    • I agree with Scott Mac's sentiment, but more noticeboard handwringing won't help. Instead, just start blocking these people in application of their topic ban (or under discretionary sanctions) if their continued bickering bothers you. Most tend to get it after the third or fourth block.  Sandstein  20:23, 25 October 2010 (UTC)[reply]
    • I don't believe that the ArbCom decision and subsequent remarks by arbs was intended to create a "free fire zone", but it certainly did empower uninvolved admins to impose sanctions against those people violating both teh word and the spirit of their topic bans. I urge more admins to patrol this area and use the enforcement power you have been given to help bring this subject area under control. I believe that is what the community, as a whole, wants. Beyond My Ken (talk) 22:45, 25 October 2010 (UTC)[reply]
    • Couldn't agree more with the overall sentiment of being sick to death of this conflict and the push after the decision to find holes in the ban to wriggle through. However I also couldn't agree more that it's time to take a less talky, more blocky approach to the situation. Actions speak louder than words and months of talking still have failed to get through to some of the combatants. Beeblebrox (talk) 00:16, 26 October 2010 (UTC)[reply]
    • From my experience with enforcement of the Armenia-Azerbaijan 2 case, there comes a point at which the only thing getting the point across is "Break the rules, you'll get blocked. Push the boundaries, you'll get blocked." The alternative here is to see Wikipedia:Requests for arbitration/Climate Change 2 become a bluelink, and no one in their right mind wants that. Seraphimblade Talk to me 00:37, 26 October 2010 (UTC)[reply]
      Exactly. The goal is to create a change in culture. As Sandstein mentions above, the best way to do that is for a group of admins to mete out some lengthy blocks pour encourager les autres. When people see that arbcom and the admin corps mean business they'll stop pushing. Handwringing over "did the arbs mean this, did they mean that, what about clause (vi) in subpart 2(a) of Finding of Fact 9.2" only prolongs the agony. Short Brigade Harvester Boris (talk) 00:55, 26 October 2010 (UTC)[reply]
    • Strongly Oppose Although understandable, this proposal seems to stem from a "I'm so angry I will nuke the world" mentality. That has no place whatsoever on Wikipedia (WP:Tigers and all that). One of the supposed cases of climate-drama spillover was the AN request I began (to be clear, I am quite peripheral to climate editing, but am now planning to take a much more active interest). It was an ordinary and routine case, requiring ordinary and routine attention--edit-warring across the project after various other attempts to encourage the editor failed. However because one or two edit wars were climate-related, the thread was summarily hatted and protestations ignored. The editor went back to a (non-climate) edit war immediately. Angry is no way to edit an encyclopedia, and never has good results. If you're angry, walk away. Certainly don't propose blocking everyone who annoys you. --TeaDrinker (talk) 00:54, 26 October 2010 (UTC)[reply]
    See this Beyond My Ken (talk) 04:40, 26 October 2010 (UTC)[reply]
    Thanks for the link, I appreciate it! My point is not that blocks should be avoided, only that they should be handed with judicious care. Blocks arising out of frustration are not going to work and should be discouraged. I feel much of this proposal falls into that category. While the frustration is understandable, encouraging reckless and emotionally involved blocks is going to cause far more problems. --TeaDrinker (talk) 05:06, 26 October 2010 (UTC)[reply]
    Also see this recently concluded arbitration enforcement request. It's much harsher than I asked for but it's the result of a two-day discussion and I think it's justifiable. It appears that the arbitration committee, the community and the uninvolved admins at WP:AE are finally united in sending a clear and unmistakable message to the topic-banned editors in the climate change arbitration. --TS 09:12, 26 October 2010 (UTC)[reply]

    Very important: Need an uninvolved admin to help close an RFC

    We need an uninvolved admin to formally close an RFC. Just to give you a little bit of background:

    All we need from someone is to undertake a few tasks.

    1. Close this thread to close the RFC, with some kind of discussion/summary template.
    2. Close this list of principles with some kind of discussion/summary template.

    It was a long and difficult discussion. But the issue is an important one and it would be a shame to lose the consensus principles that this RFC produced. Shooterwalker (talk) 15:19, 25 October 2010 (UTC)[reply]

    I think what you are seeking is an "offical stamp" for your views on the RFC, but although you believe them to be the "consensus", in reality they are actually disputed. I don't see how the administrators can "sign off" your views as being the basis for changes to any policy guideline. Last time I looked, no policy or guideline had to have an admin's Imprimatur. --Gavin Collins (talk|contribs) 15:47, 25 October 2010 (UTC)[reply]
    I'm sorry you feel that way Gavin, but most editors share those views even though you do not. Consensus is not unanimity. Shooterwalker (talk) 17:24, 25 October 2010 (UTC)[reply]
    Noting that Shooterwalker has not in fact asked anyone to endorse his own views. He has asked for the discussion to be formally closed and a summary written. That's exactly correct and this is a suitable venue for the request. The bad faith of "I think..." isn't needed here. FT2 (Talk | email) 19:45, 25 October 2010 (UTC)[reply]
    Thanks FT2. My personal views are actually pretty close to Gavin's. But I'm trying to find a consensus, even where I personally disagree.
    Regardless of the outcome, we need someone independent to read the closing thread to see if there is indeed a consensus. Shooterwalker (talk) 20:10, 25 October 2010 (UTC)[reply]
    • For the record, it is not in fact required that an administrator close an RFC. What is needed is any experienced user who did not participate in the discussion and has not previously indicated strong feelings one way or the other on the subject. At a glance it looks like a bear of a discussion that will require more time than I have open today to close properly, but if nobody steps up soon I may be able to find the time tomorrow or Wednesday. Beeblebrox (talk) 00:49, 26 October 2010 (UTC)[reply]

    Proposal for use of Betacommand's bot

    Hello, all. I've got something of a problem. I'm trying to make Mediation Cabal case pages more streamlined, by taking the creation dates out of the case page names. Problem is, that's how MiszaBot knows which order to list them in. To solve this problem, Betacommand has agreed to have his bot list them properly by date order, without having dates in the name. I know he is under some unique restrictions, so I would like to obtain approval here to allow him to take over MedCab case listings. The WordsmithCommunicate 03:49, 26 October 2010 (UTC)[reply]

    WP:UAA

    If a free admin could help out at WP:UAA that'd be great, there is a huge backlog. Thanks ----Addihockey10e-mail 05:26, 26 October 2010 (UTC)[reply]

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