Wikipedia:Administrators' noticeboard

This user has autopatrolled rights on the English Wikipedia.
This user has extended confirmed rights on the English Wikipedia.
This user has page mover rights on the English Wikipedia.
This user has pending changes reviewer rights on the English Wikipedia.
This user has rollback rights on the English Wikipedia.
This user has template editor rights on the English Wikipedia.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Jossi (talk | contribs) at 15:45, 8 September 2008 (→‎Administrative action review: Tznkai). 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 three days are archived by Lowercase sigmabot III.(archives, search)


    warning template for Hurricane Gustav

    During Hurricane Katrina, Wikipedia had this warning template on the top of the page

    ATTENTION: Residents of areas affected by Hurricane Katrina are advised to seek advice and information from local authorities through television and radio. Information on Wikipedia may not be current or applicable to your area. Do not decide whether to leave your house, shelter, or vehicle based on Wikipedia information.


    I placed one on the page for Hurricane Gustav but someone removed it. I think it should be there and want an admin's opinion on the issue. It may be against the rules but I think the rules should be allowed to be bent in an emergency situation. The page on Katrina had the warning up for days with no objections. One can see so in the edit history--Ted-m (talk) 03:22, 1 September 2008 (UTC)[reply]

    Wikipedia isn't the place for medical advice, and I think in the same vein we shouldn't serve as a PSA system. Der Wohltemperierte Fuchs (talk) 03:23, 1 September 2008 (UTC)[reply]
    (ec) I agree. But that's the whole point of the template. So what's the objection?Basil "Basil" Fawlty (talk) 03:27, 1 September 2008 (UTC)[reply]

    Then how come it was allowed during Katrina?--Ted-m (talk) 03:25, 1 September 2008 (UTC)[reply]

    Cause we made a mistake in allowing it. We have this... http://en.wikipedia.org/wiki/Wikipedia:General_disclaimer NonvocalScream (talk) 03:26, 1 September 2008 (UTC)[reply]
    And this... http://en.wikipedia.org/wiki/Wikipedia:Risk_disclaimer NonvocalScream (talk) 03:27, 1 September 2008 (UTC)[reply]
    I think it should be up there. Privatemusings (talk) 03:27, 1 September 2008 (UTC)[reply]

    (copied from User_talk:CrazyC83, who just reverted my re-addition of the box....)

    On principle? How about the one that your opinion isn't the only one that matters Lar? I especially like your comment on my talk page. - auburnpilot talk 05:20, 1 September 2008 (UTC)[reply]


    I won't revert you, Crazy.. but I do think that it's worth having that box up there for a while. I certainly wouldn't worry about the Manual of Style in this context, because I think it's appropriate to bend the rules a little once in a while for strong reasons.... and our article is the second result in Google, so could well get quite a lot of traffic. Follow your conscience... :-) Privatemusings (talk) 03:34, 1 September 2008 (UTC)this has been mentioned on WP:AN too, so I'll copy this note across there as well....[reply]

    :o) I think it should not be up there.  :) :) Speaking of which, we have an applicable content guideline... over here! :) NonvocalScream (talk) 03:37, 1 September 2008 (UTC)[reply]
    Um, no. I see it now:
    ATTENTION: "Those contemplating Liposuction are advised to seek advice and information from true medical professionals through their websites and in-person visists. Information on Wikipedia may not be current or applicable to your procedure. Do not decide whether or not to get liposuction or other cosmetic surgeries based on Wikipedia Information".
    Yeah, let's not. - auburnpilot talk 03:37, 1 September 2008 (UTC)[reply]
    um.. Auburn... you're comparing a liposuction disclaimer with a note about a very dangerous Hurricane. I see a difference. Privatemusings (talk) 03:41, 1 September 2008 (UTC)[reply]
    PrivateMusens, you are ignoring the content guideline I cited above. NonvocalScream (talk) 03:52, 1 September 2008 (UTC)[reply]
    Lipo is a very dangerous elective surgery (1 death per 5000?). [1][2] In all seriousness, it was just an example of what some may see as equally valid, but most will see as showing how equally unnecessary such warnings are. - auburnpilot talk 03:51, 1 September 2008 (UTC)[reply]
    I agree; part of the point of removing these things is that even at the most narrow scope there's a lot of articles that can be argued to be life or death.--Prosfilaes (talk) 10:43, 1 September 2008 (UTC)[reply]
    Or worse:
    ATTENTION: "Those considering a conversion to Catholicism are advised to seek advice and information from a trusted spiritual adviser. Information on Wikipedia may not be current or applicable to your personal circumstances. Do not decide whether or not to change your religion based on Wikipedia Information".
    -- Mr.Z-man 03:47, 1 September 2008 (UTC)[reply]

    (ec) How about a reminder of/reference to the disclaimers added to {{HurricaneWarning}}? WODUP 03:49, 1 September 2008 (UTC)[reply]

    That still seems pretty ridiculous, I am sure that those affected are very aware of the storms in this date and age. - Caribbean~H.Q. 03:50, 1 September 2008 (UTC)[reply]
    Well I'll be... the risk disclaimer is already linked from {{HurricaneWarning}}. WODUP 04:23, 1 September 2008 (UTC)[reply]

    And another...

    ATTENTION: "Those considering a smoking cessation are advised to seek advice and information from a licensed practioner. Statistics on Wikipedia may not be current. Do not decide whether or not to change your smoking habits based on Wikipedia Information".

    NonvocalScream (talk) 03:55, 1 September 2008 (UTC)[reply]

    Not weighing in on the opinion at hand, but I think the main concern is that a Goggle search string for "Hurricane Gustav" shows it's Wikipedia page as the 3rd result. It seems that users are just concerned that someone may stumble upon the article and may take the information as fact, which could be true or false. I have a feeling that the concerned users are just wanting to make sure that the poor souls who are having to leave their homes, their jobs, their lives, and who could possibly get injured or killed understand that we are not a reporting service and that our content should not be mistaken for advice. This is an extraordinary case that is not easily comparable to other issues, beliefs, or surgeries. I respectfully ask that editors stop making parody templates of the above template and please be respectful so as to not mock the original poster of the template. Obviously s/he had the best of intentions and the joking and comedy over a very serious matter is of very poor taste. Can we please get to the issue at hand and seriously discuss whether the template should be placed or not? Thank you. « Gonzo fan2007 (talk ♦ contribs) @ 03:58, 1 September 2008 (UTC)[reply]
    Nobody is making light of "the poor souls who are having to leave their homes...". The template should not exist, and we've shown why through the use of examples. - auburnpilot talk 04:01, 1 September 2008 (UTC)[reply]
    It is not parody. It is contrast and comparison. Additionally, I don't think anyone will decide evacuation on this article, the PSA/EAS is the responsibility of local city/state and federal authority. We are building an encyclopedia, let us not lose sight of that. NonvocalScream (talk) 04:02, 1 September 2008 (UTC)[reply]
    In any case, why add it it now? Gustav already hit Cuba quite hard and no one seemed to care. Because its entering the United States? What about WP:UNDUE? Its clear that all the commotion its because of the actual state that its going to hit, because I don't see such a haste when they go over Florida. Some users are being influenced by memories of Hurricane Katrina's destructive pass. Sorry it that seems harsh, but I call a spade a spade. - Caribbean~H.Q. 04:05, 1 September 2008 (UTC)[reply]
    (ecX3) Guys! All I am asking is that you just talk about it without being dicks and take the request made by the original poster as a serious request. Just be respectful of the situation. All I am asking is for comments like Caribbean's, which address the issue at hand without mocking the template. « Gonzo fan2007 (talk ♦ contribs) @ 04:08, 1 September 2008 (UTC)[reply]
    Don't be a fucking douchebag. - auburnpilot talk 04:12, 1 September 2008 (UTC)[reply]
    Thiz iz seriouz buzinnezz. NonvocalScream (talk) 04:13, 1 September 2008 (UTC)[reply]
    (e/c)And why only hurricanes? Do we do this for other events? Floods, tornadoes, blizzards, forest fires, riots, wars, chemical spills? At what point is a disaster significant enough to merit a warning? Mr.Z-man 04:14, 1 September 2008 (UTC)[reply]
    Off topic: Am I the only one irritated by edit conflicts? The software really should resolve this automagically. :) NonvocalScream (talk) 04:15, 1 September 2008 (UTC)[reply]
    (ec)In any case, I personally do not believe the template should belong. I understand the reasons for adding it, but making this a special case just doesn't make sense to me. I have a feeling that the template would just be an eye-sore, and it could be argued that this is just systematic bias. Why don't we add templates like this to every big event? I think that the encyclopedia is fine with just reporting the information in an encyclopedic manner, and we should just let our disclaimers do the disclaiming. And yes I am hating the conflicts (especially the one I just had with your comment ;) « Gonzo fan2007 (talk ♦ contribs) @ 04:17, 1 September 2008 (UTC)[reply]

    Why not use one of our other "current" templates, that already warn of such things? -- Ned Scott 04:17, 1 September 2008 (UTC)[reply]

    Because we have content guidelines that should generally be used. NonvocalScream (talk) 04:19, 1 September 2008 (UTC)[reply]
    You seem to be confused. The current templates are article issue templates, not disclaimer templates. -- Ned Scott 04:20, 1 September 2008 (UTC)[reply]
    Oh no, I am very clear. I am very clear that the pink boxes in this section of AN are in fact... disclaimers. Even if in the loosest form, they intend to warn and caveat. Don't call me confused please. NonvocalScream (talk) 04:27, 1 September 2008 (UTC)[reply]
    Just to be crystal clear, I think Ned is referring to the {{current}} templates. - auburnpilot talk 04:36, 1 September 2008 (UTC)[reply]
    Oops. NonvocalScream (talk) 04:37, 1 September 2008 (UTC)[reply]
    ATTENTION: Editors of articles such as Hurricane Gustav are advised to seek advice and information from ArbCom before placing a template such as this. Information in Wikipedia: space may not be current or applicable to your ArbCom's current mood. Do not decide whether to place a template on the article based on Wikipedia policies.

    --NE2 04:34, 1 September 2008 (UTC)[reply]

    ATTENTION: There are hundreds of stupid arguments on AIV, and this is one of them.

    Word. --mboverload@ 04:42, 1 September 2008 (UTC)[reply]

    LOL. Particularly when this was the shape of {{HurricaneWarning}}, a template that survived TFD several times, until September 2007. Titoxd(?!? - cool stuff) 04:44, 1 September 2008 (UTC)[reply]

    Since we're churning out silly disclaimer templates, how about one for Wikipedia:

    ATTENTION: Those considering using Wikipedia are advised to seek advice and information from a trusted reliable source. Information on Wikipedia may not be current or applicable to your personal circumstances. Do not decide whether or not to use Wikipedia based on Wikipedia information.

    It just had to be said. MER-C 10:27, 1 September 2008 (UTC)[reply]

    Perhaps it would be easier for Wikipedia to consider a help page about its own articles and making decisions based on one's trust in their accuracy. That's a question for the offices, most likely.Miquonranger03 (talk) 07:07, 3 September 2008 (UTC)[reply]

    prelude to edit war

    You lot are debating how many angels can dance on the head of a pin, and thus miss the actual point. The style guide matters not, the general principle against disclaimers matters not. They're good ideas, but blanket prohibitions are bad. This is a situation where we may well be getting a large influx of readers who have no idea what WP really is about, and haven't the time or energy to go to the bottom of a page, and then realise they should read a general disclaimer to see if maybe there is something there they ought to read. IAR and add the damn warning template, and stop standing on formality about whether it's in accordance with general principles about not having disclaimers. Wikipedia does not exist in a vacuum. ++Lar: t/c 05:09, 1 September 2008 (UTC)[reply]

    What he said. Titoxd(?!? - cool stuff) 05:11, 1 September 2008 (UTC)[reply]
    IAR only works when it improves the pedia. I would posit that it does not, so IAR is not applicable. NonvocalScream (talk) 05:15, 1 September 2008 (UTC)[reply]
    WP:IAR: "If a rule prevents you from improving or maintaining Wikipedia, ignore it." So, how does this help improve or maintain Wikipedia? It doesn't. We don't add such templates to articles, and this doesn't deserve an exception. - auburnpilot talk 05:15, 1 September 2008 (UTC)[reply]
    Don't be ridiculous. Don't stand on rules. And don't revert me for the sake of some principle. ++Lar: t/c 05:17, 1 September 2008 (UTC)[reply]
    echo Lar. Privatemusings (talk) 05:18, 1 September 2008 (UTC)[reply]
    I don't particularly like the idea of it being there, either, but I think this is one of the cases where we can and should ignore the rules. People have the capacity for incredible stupidity. While I'm generally against the idea of keeping this like this around, not everyone is intelligent enough to realize that at any given point in time, Wikipedia could be hosting information that could result in some bad things if people were dumb enough to use it as a guide for emergency procedures, and that's really not something I want to think about. Remember that Wikipedia does exist in the real world. Celarnor Talk to me 05:20, 1 September 2008 (UTC)[reply]
    I would posit that it does improve the pedia, by sending away the users who really need the info to the proper place, hence making us be a more reliable source of info. That said, please don't edit war over this. This is an extremely unstable article, and hence protections are inappropriate here; I'll be handing out blocks instead of simply elevating the protection level of the page. Titoxd(?!? - cool stuff) 05:22, 1 September 2008 (UTC)[reply]
    echo Lar. WP:IAR. Do what you feel is right. --Duk 05:27, 1 September 2008 (UTC)[reply]
    Indeed, Lar makes an excellent point above. Putting that up there, is simply the right thing to do. SQLQuery me! 07:15, 1 September 2008 (UTC)[reply]
    So you're worried about people who run around the Internet randomly trusting sites, and you think they should be warned away from Wikipedia so they find some blog to trust? You can't honestly say that you're helping people who can't be trusted to use the Internet wisely by warning them away from an updated fairly reliable source.--Prosfilaes (talk) 11:50, 1 September 2008 (UTC)[reply]
    Just so we note, this box violates some of our principles, UNDUE and NPOV. Also, the guideline is a good guideline, this is not what we do (PSA/EAS). NonvocalScream (talk) 05:21, 1 September 2008 (UTC)[reply]
    A guiding principle is "do no harm" and people relying on this article for decisions on evacuation can clearly lead to real harm. The disclaimer should be on the page. Apparently it is presently unprotected so that IP editors and newbies can have their way with it. An Ip editor changed the windspeed in the info box from the correct 115 mph to 390 mph, and it stayed that way for 26 minutes until I restored the correct information. The disclaimer should remain on the article. It is about a pending natural disaster affecting millions of people and tens of billions of dollars property damage, and if a vandal can introduce incorrect information, or if stale or incorrect information is in the article, it could lead people to take actions affecting their safety adversely. And the article should once again be semiprotected, because sufficient established and registered users are working on it that newbies and IP editors are not needed to keep it up to date while the storm is a few hours from landfall. Let the IPs back in when it is a historical matter in a day or so. Edison2 (talk) 05:25, 1 September 2008 (UTC)[reply]
    I have repeatedly stated on that talk page that protection would be extremely inappropriate in this case, but like I said above, I agree with the inclusion of the box. Titoxd(?!? - cool stuff) 05:26, 1 September 2008 (UTC)[reply]
    Well I semi'ed it but feel free to undo that, I won't consider that any sort of wheeling. ++Lar: t/c 05:27, 1 September 2008 (UTC)[reply]
    We have principles, we strive to be an accurate academic institution. This type of thing should no go into our articles, for neutrality, and other reasons as echoed by me above. Incidentally, why are anons not permitted to edit that article? Please undo the prot. NonvocalScream (talk) 05:29, 1 September 2008 (UTC)[reply]
    Question, how does this violate undue or npov? I don't see it but I might be missing something ;) RxS (talk) 05:38, 1 September 2008 (UTC)[reply]
    As above. NonvocalScream (talk) 05:45, 1 September 2008 (UTC)[reply]
    As I said, the only reason that all this argument is going on its because Gustav will hit New Orleans, which received a lot of destruction with Katrina. The decision to add it is directly influenced by the psychological effect of the horrible events seen three years ago. If that wasn't the case a template would have been added when it passed over Cuba, which by the way has also been heavily affected by tropical cyclones in the last years. - Caribbean~H.Q. 05:53, 1 September 2008 (UTC)[reply]
    Perhaps you're right. And perhaps it should have been added earlier. Better late than never. (and I'll say that I don't necessarily have a lot of confidence in the governments of the area and their ability to have learned from Katrina, but I digress). ++Lar: t/c 06:06, 1 September 2008 (UTC)[reply]
    So we if we didn't do something in the past (rightly or wrongly), we can't do it going forward? I know that's not what you're saying but that's the practical effect. Shouldn't we decide if something's a good idea and then work out the application afterwards? Anyway, it seems like a good application of IAR, and it's been worked out so it's all good. RxS (talk) 06:11, 1 September 2008 (UTC)[reply]

    It's a good principle. But sometimes exceptions are needed. This is one of those times. The harm to the encyclopedia from having this disclaimer for a day or 3 is slight. The harm if someone got hurt and it got into the media is immense. No brainer. All principles have exceptions. That's the real world. Deal. ++Lar: t/c 05:31, 1 September 2008 (UTC)[reply]

    I'll compromise here. Lets make sure the template goes away after the disaster subsides. NonvocalScream (talk) 05:32, 1 September 2008 (UTC)[reply]
    Back when it used to be a proper template, that was always the case. Titoxd(?!? - cool stuff) 05:33, 1 September 2008 (UTC)[reply]
    NVS, 4 days from now (or whatever the right time is, it should be short, I agree) I'll baleet it out of there myself... This is a temporary thing only. ++Lar: t/c 05:37, 1 September 2008 (UTC)[reply]
    The other option would be not to pretend to be posting "Current storm information" as if Wiki was providing the latest and greatest. Maybe Wiki shouldn't be a newspaper or public notice system? --Pat (talk) 05:45, 1 September 2008 (UTC)[reply]
    Which is not going to happen unless you intend to kill WP:WPTC and break my third law. Wikipedia has been lauded previously over our hurricane coverage, and even cited in government tropical cyclone coverage, so I don't think we're interested in changing that any time soon. Titoxd(?!? - cool stuff) 05:48, 1 September 2008 (UTC)[reply]
    I myself find it interesting that there has only been interest in putting up this template as the storm hits the United States. I guess the human beings in Cuba, Haiti, Dominican, etc. just aren't as important? Perhaps the current hurricane template should have a link to the risk disclaimer, but putting up this red template only when a disaster happens to the USA looks very unpretty. —Elipongo (Talk contribs) 06:13, 1 September 2008 (UTC)[reply]
    Well, there is the perhaps relevant fact that Cuba, the Dominican Republic etc. are Spanish -speaking countries, Haiti is French-speaking, and we are the English Wikipedia. Ed Fitzgerald "unreachable by rational discourse"(t / c) 06:52, 1 September 2008 (UTC)[reply]
    But Jamaica and the Caymans are English-speaking. Eleven deaths have been reported so far in Jamaica. -- Avenue (talk) 11:10, 1 September 2008 (UTC)[reply]
    Quite true. Perhaps the notice should be affixed to the article on Hanna now, as it seems to be aimed at the Bahamas. Ed Fitzgerald "unreachable by rational discourse"(t / c) 19:54, 2 September 2008 (UTC)[reply]
    There's no ulterior motives here. We used to have it last year; only this year it got edited/redirected to the bland current version (which was being used, by the way), {{current tropical cyclone}} due to the ambox change. As people remembered Katrina, they remembered how the red box, and asked for it back. Titoxd(?!? - cool stuff) 06:16, 1 September 2008 (UTC)[reply]
    Perhaps {{current tropical cyclone}} should itself have a link to the risk disclaimer- maybe even highlighted in red. That way anybody in the path of a storm would be warned not to use Wikipedia for life-safety decisions and we wouldn't be in the position of having to judge when the people affected are "important" enough to warrant a red warning banner.—Elipongo (Talk contribs) 06:31, 1 September 2008 (UTC)[reply]
    That box does include such a link, but we Americans are now in danger so it much be enormous and clearly visible. - auburnpilot talk 06:37, 1 September 2008 (UTC)[reply]
    So... by that interpretation you're saying that we Americans are too dumb to heed the regular disclaimer used for the rest of the world? —Elipongo (Talk contribs) 06:43, 1 September 2008 (UTC)[reply]
    Not to be making light of things, but speaking as an American myself, I'd say better safe than sorry to your question. That can be read many ways, I know. rootology (C)(T) 06:46, 1 September 2008 (UTC)[reply]
    I do feel it's important for people to be reminded not to base life-safety decisions on our data, however things should be the same if the disaster hits Mexico or New Zealand as if it hits the United States. This red banner is a bad idea, the proper course is to make the standard current disaster template a bit clearer about our standard disclaimers. —Elipongo (Talk contribs) 06:53, 1 September 2008 (UTC)[reply]
    I agree, I'm not opposing this because of any guidelines, I'm opposing it because of the precedent it sets. Nobody bothered to respond to my question above, so I'll ask it again down here. And why only hurricanes? Do we do this for other events? Floods, tornadoes, blizzards, forest fires, riots, wars, chemical spills? At what point is a disaster significant enough to merit a warning? Do we put one up after an earthquake warning people there might be a tsunami? Why wait until there's a tornado warning, by then it may be too late, do we put up a warning for every severe thunderstorm watch? What strength of hurricane warrants a template? Do we put one up for a Category 1? A tropical depression? I normally agree with Lar, but I'm disappointed to see him simply dismissing all the opposition as based on formalities. Mr.Z-man 14:56, 1 September 2008 (UTC)[reply]

    (outdent)... I'm sorry if it seems like I was simply dismissing opposition, if I acted brusquely and more forcefully than I normally would. But I came to this discussion and what I saw was a lot of tomfoolery. Sorry, but that's what it looked like to me, despite those pointing out that the stuff being shown was shown to bring forth counterexamples... sure, maybe they were, but they were also funny. That to me suggests this matter wasn't being taken seriously. So I acted. That's what we are supposed to do, after all. Know when deliberation is needed, and know when quick action is needed, and know how to tell the difference. The subsequent discussion seems to show that the consensus, or at least a majority of voices, was in the end, OK with this temporary measure. (and it should be temporary!)

    Now, I think our general rule against specific disclaimers is good. But I think maybe for anything that is worthy of a "current event" tagging, we need a more bold pointer to that disclaimer, right at the top of the article, where it is seen by everyone visiting, rather than buried in fine print towards the bottom (It is on the very bottom line of the page, in small print, after other stirring reads like the Privacy Policy and the About Wikipedia prose... how many people coming to a site when they're in a hurry are going to read that??? NOT MANY.) So I think after this tempest in a teacup about this specific box blows over (sorry!), we need to revisit the design of the current events box. Even if it just points to our general disclaimer, it's good to have that pointer at the top for current events. Tornadoes, fires, bridge collapses, earthquakes, hurricanes, wars, you name it. Anyone using Wikipedia for their first source for advice about hangnail cures is a fool. And the buried disclaimer is fine for them, they have time to regret their foolishness. But people in emergency situations, with not much time? They need a more clear reminder NOT TO TRUST this source for life and death info. What if the vandal who set the speed to 300+ mph for 20 min last night had set it to 15 mph and people made decisions based on that? Do you all standing on policy actually want that on your conscience? I don't. So let's work together to get that box changed while still hewing to our spirit.

    I apologise to anyone I gave offense to last night. It was not my intent, and I'm sorry. But I felt this was important enough to override some of the norms I usually go by. Heck I even reverted something... once. That's pretty shocking behaviour for me! ++Lar: t/c 17:05, 1 September 2008 (UTC)[reply]

    "...sure, maybe they were, but they were also funny. That to me suggests this matter wasn't being taken seriously." - skip on a bit - "So I think after this tempest in a teacup about this specific box blows over (sorry!)...". I hope that my point is clear enough. TalkIslander 09:50, 8 September 2008 (UTC)[reply]

    Actual disaster warning box

    <-- Whats the actual "live disaster" template? I didn't know we had one? rootology (C)(T) 06:57, 1 September 2008 (UTC)[reply]

    {{Current disaster}}—Elipongo (Talk contribs) 07:01, 1 September 2008 (UTC)[reply]
    Heck, this is all silly then. Just to mock it up quick I flipped that to be the speedy type graphically instead of the notice type, and changed the image, to make this:

    visible on this diff
    Isn't that better? rootology (C)(T) 07:09, 1 September 2008 (UTC)[reply]
    Much better, thank you. Anyone object to its use on the article now? —Elipongo (Talk contribs) 07:14, 1 September 2008 (UTC)[reply]
    ATTENTION: Editors considering sticking beans up their nose are advised to seek advice and information from medical professionals and/or horticulturalists prior to attempting to do so. Information on Wikipedia may not be applicable to your nostrils or the type of beans you may have in your pantry. Do not decide whether or not to shove foodstuffs in your bodily orifices based on Wikipedia information.

    Had to be said... caknuck ° is geared up for football season 08:20, 1 September 2008 (UTC)[reply]

    Now you tell me... Kevin (talk) 08:37, 1 September 2008 (UTC)[reply]
    Um... you may wish to link pantry, unless you enjoy resolving pulse (legume)/lingerie issues (I know I do!) LessHeard vanU (talk) 10:11, 1 September 2008 (UTC)[reply]

    What do you think of this? http://en.wikipedia.org/w/index.php?title=Template:Current_tropical_cyclone&oldid=236230043

    --Random832 (contribs) 13:14, 4 September 2008 (UTC)[reply]

    I like it. Looks pretty similar to what WP:SEVERE puts on severe weather outbreak articles (and I'm blanking on the template name there). Rdfox 76 (talk) 12:08, 6 September 2008 (UTC)[reply]
    ATTENTION: Editors seeking medical advice on Wikipedia are advised to remember the old saying,
    "He who doctors himself has a fool for a patient."

    Baseball Bugs What's up, Doc? 03:34, 7 September 2008 (UTC)[reply]

    Note: All the above warnings are in Wikipedia, and therefore unreliable. Waltham, The Duke of 16:23, 7 September 2008 (UTC)[reply]

    Still at it?

    See this discussion, above, regarding a user who was blocked for Incivility and wilful disruption, and then unblocked with a promise to behave. Several of his edits since the unblock have been problematic, as discussed above. The following series of edits are disturbing in that regard: August 31, adds ref to WP article. Another user leaves him a message on his talk page explaining that Wikipedia articles cannot be used as sources for other Wikipedia articles. Sep 1, restores removal of inappropriate source. Sep 1, restores again, with the edit summary "oh yes I can."

    Now, while I think this user wants to contribute usefully, I also think that he's been given an awful lot of slack, and I'm wondering whether it may be time for another block. Exploding Boy (talk) 21:45, 2 September 2008 (UTC)[reply]

    1 week block, and a suggestion they re-examine the way in which they are interacting with other contributors. As usual, I am not so wedded to my actions to need notifying that they may be overturned - but I would hope any unblocking admin ensures they understand that a resumption of the previous mannerisms will not be tolerated. LessHeard vanU (talk) 22:05, 2 September 2008 (UTC)[reply]

    So the record's complete, we have two edits from this morning [3] [4] illustrating a similar attitude. Specifically, after being asked not to, he's re-adding links to myspace and imdb that's the same name as the article's subject but different people, and to a mirror page. justinfr (talk/contribs) 22:32, 2 September 2008 (UTC)[reply]

    Sometimes I think he is trying to contribute usefully and is simply incompetent; at other times I think he's being intentionally disruptive. His behavior at Rhíannon Thomas has been exceedingly bizarre from first to last—especially when he started readding the MySpace link after admitting in the AfD that he was mistaken in identifying the article's subject with two other women. And it's hard to know what to think about this edit (note the article's topic). Deor (talk) 04:11, 3 September 2008 (UTC)[reply]
    Oh, and does anyone other than me find his very first edit (after some messing about in his user space) kind of suspicious? Deor (talk) 04:20, 3 September 2008 (UTC)[reply]
    Note his unblock request reason: "The reason I find it difficult to be civil is because of the fact I have aspergers. I recommend you read the article on it." This screams troll. As an aside, on his talk page he claims to occasionally use this ip, but he has only used it once, and not since the block. I wouldn't be at all surprised to find he's got a bunch of socks either. Exploding Boy (talk) 16:23, 3 September 2008 (UTC)[reply]
    Aspergers my Irish Ass!! Aspergers Syndrome is a high functioning form of Autism where the person who has it cannot understand word play, speak in literal terms only and usually are not capable of lying.

    I'm thinking troll here. KoshVorlon > rm -r WP:F.U.R 11:55, 4 September 2008 (UTC)[reply]

    ...er, Kosh? You might want to do a bit more research on Asperger's Syndrome before making that sort of claim. (I speak from personal experience; I've been recently diagnosed with it, and I love wordplay and am an accomplished liar when it comes to convincing the boss to give me a day off.) More accurately, it's something related to autism that may or may not be a form of high-functioning autism (the jury's still out on that one), and is characterized by severe difficulty with social interactions.
    That said, it still sounds pretty troll-ish to me; I've yet to encounter an HFA or Asperger's person who simply uses it as an excuse for being uncivil to people instead of warning that they just may not be very good at civility. Rdfox 76 (talk) 12:16, 6 September 2008 (UTC)[reply]

    Long-standing attack articles

    Just pretend I'm stupid and explain to me really slowly why the articles listed above don't fall under criterion G10 for speedy deletion. At first I thought, "Surely criticism is being used in the sense of analysis and commentary". But no, these really are just lists of negative stuff that people have said about these people. Needless to say, there are no matching Praise for ... or Agreement with ... articles.

    The only thing stopping me deleting these is that I have enough sense to know what a storm this would create but, after thinking about it for the past couple of weeks, this increasingly seems a cowardly excuse. CIreland (talk) 14:21, 4 September 2008 (UTC)[reply]

    That's not a "cowardly excuse", it's a recognition of the nature of the project. If you did something that you know is going to be disruptive, without taking steps to minimize the disruption by obtaining a consensus for the action, that's tantamount to being disruptive yourself. I think you did the right thing by holding off and posting your request here. Ed Fitzgerald "unreachable by rational discourse"(t / c) 14:28, 4 September 2008 (UTC)[reply]
    • (ec)Because criticism of these figures in mainstream sources is widespread and of encyclopedic concern. Also, because treating that criticism appropriately requires (sometimes) that we split out a section from the main article. An "attack page" is a page that serves only to defame the subject. In this case, these pages serve to give a tertiary look at criticism which already exists. They do have the added unpleasant outcome of being harder to maintain NPOV than the main articles (partly because they don't see the same amount of traffic and partly because their "baseline" POV is a little slanted). But they should certainly not be speedied. Protonk (talk) 14:29, 4 September 2008 (UTC)[reply]
    I would be fine with, for example, Commentary on Tony Blair or somesuch. The trouble is that most of the above receive a good deal of equally verifiable praise in equally reliable sources yet this is barely represented - making our coverage of these people unbalanced. CIreland (talk) 14:35, 4 September 2008 (UTC)[reply]
    The reason they are not called Commentary rather than criticism is that the NPOV tendency would be to "balance" the negative criticism with positive adulation... which is frequently even less analytically based than the negative stuff (and far less common, which ironically leads to a bias upon sources if they are presented "equally"). While positive criticism can be appropriately placed within an article with criticism in the title, the nature of the beast dictates that most content will be negative. LessHeard vanU (talk) 15:24, 4 September 2008 (UTC)[reply]
    We also have Criticism of Franklin D. Roosevelt (edit | talk | history | protect | delete | links | watch | logs | views), Criticism of Ellen White (edit | talk | history | protect | delete | links | watch | logs | views), Criticism of Jesus (edit | talk | history | protect | delete | links | watch | logs | views) and Criticism of Muhammad (edit | talk | history | protect | delete | links | watch | logs | views). Criticism in a sense includes positive criticism, so it's possible to include them as well. Cenarium Talk 15:54, 4 September 2008 (UTC)[reply]
    I realize we also have those articles but I singled out the ones for living people, for obvious reasons. Also, you are correct that "Criticism" can include positive criticism - but in the articles in question it patently does not. For example, this is the lede for Criticism of Tony Blair:
    Criticism of Tony Blair includes accusations of dishonesty, authoritarianism, and subservience in his relationship with U.S. President George W. Bush. Tony Blair has faced particularly severe condemnation for British involvement in the Iraq War, earning him the disparaging moniker of "Bush's Poodle."
    CIreland (talk) 16:00, 4 September 2008 (UTC)[reply]
    Preface the above with "Negative", and tag "Positive criticism includes..." with a couple of examples from the main body would result in a NPOV and comprehensive lede (why do we spell it like that?) Ho, you should have seen the barrage of negative criticism that socialist Prime Ministers used to get - often from fractions within their own party! LessHeard vanU (talk) 16:46, 4 September 2008 (UTC)[reply]
    {Sidebar) The spelling "lede" for the leading sentence, paragraph or section is a journalistic invention designed to differentiate it from "lead", as in the hot lead used to make type. Ed Fitzgerald "unreachable by rational discourse"(t / c) 18:01, 4 September 2008 (UTC)[reply]
    These are all public figures. The normal BLP policies cover this. Public figures can't sue for slander. If the comments/criticisms are not original research, but are cited from reliable and verifiable sources, and there are no personal attacks, the articles should remain. We have to remember that criticisms of Bill Clinton and criticism of Barack Obama are fair game also. As long as we allow fair, cited, verifiable content for any public figure, regardless of their political affiliation, we are being Neutral. For instance the following would be allowable, "Bill Clinton was impeached by the Senate on December 19th, 1998 for among other things, perjuring himself when he denied having "sexual relations" with White House intern Monica Lewinsky." What should not be allowed would be things like "Bill Clinton Will Remain the Worst President Ever"[5] Clearly no one like to hear people criticism a political figure that they have supported. But essential to the political process is free speech that allows our system to correct for problems. Political speech is the highest and most respected form of free speech. Atom (talk) 18:43, 4 September 2008 (UTC)[reply]
    Public figures can sue for defamation, and most of these are forks to deal with bloated criticism sections into which every single tine adverse comment is obsessively added by those who have an agenda against the subjects. WP:BLP does not get shelved for public figures. Having them renamed to "discussion" or some such title, which is less readily misunderstood by those who fail to see the difference between critique and censorious criticism, would be a good idea I feel. Guy (Help!) 22:16, 4 September 2008 (UTC)[reply]
    Right, BLP does not get shelved, which is why I said the BLP has a policy for public figures. We should apply it, and adapt it as needed. I personally don't see the difference between calling the article "criticism of..." and "discussion of...". The content would be critical in nature, and allowed if it is cited, verifiable and from a reliable source, and not allowed otherwise. If it is criticism, let's call it that. By allowing people who are extremely critical to have a place to put it (but still following WP:RELIABLE), it gives a safety valve that should keep some of that out of the primary article. Atom (talk) 23:02, 4 September 2008 (UTC)[reply]

    A "Criticism" article must still remain NPOV and balanced, within its narrow topic. I've preferred the less negative term "Controversy." And then what is notably but controversially asserted about the topic is reported, neutrally, and with attempts to balance it with specific fact or assertions. For example, if a critical comment was that a figure had allegedly embezzled funds, court or other findings or public commentary on that specific point would be apposited with it, so that the reader may make a judgment. Such a format may consist of a list of criticisms, since that is a convenient way to organize it; it's important to find consensus among those who criticise and those who support as to what is really out there in reliable source. Because criticism is sometimes directly verifiable and usable, if from a notable source or recognized expert, sometimes blogs and other sources normally rejected can be used, subject to the policy of verifiability; often this would be where the "positive" material would come from. --Abd (talk) 14:34, 6 September 2008 (UTC)[reply]

    Pardon my ignorance but these pages seem to be large POV forks. People got sick of being denied the privillage of posting negative POV information on the standard BLP's and have simply created articles under the guise of notable media reaction.. when in fact if it was notable enough it should stand on it's own two feet in the namesake's main article. --98.243.129.181 (talk) 04:57, 7 September 2008 (UTC)[reply]
    "Criticism of" articles are inherently POV. It's almost as if we're including an implicit comment in the intros of these articles that says "The following is a list of negative things people have said about this subject". These articles make no more sense than an article called Praise of Windows Vista. While important criticisms do have their place, creating separate "for" or "against" articles is antithetical to our goal of creating an NPOV encyclopedia. Perhaps if we decide opinions/commentary should have their own article (that is an entirely different debate), they should all be united in something like Opinions of Windows Vista. Or perhaps use "criticism" in a more general way, as in the way the term is used in the phrase "art criticism" in that it includes general independent commentary in addition to any positive/negative comments. Not everything is black-and-white, but this is the kind of thinking that this type of article structure encourages. It is absurd to me that we have this type of structure here when it should be clear to anyone that this is so blatantly against one of our core policies. Did I miss the memo that says we're supposed to overlook this POV nonsense? Wickethewok (talk) 05:10, 7 September 2008 (UTC)[reply]

    Newyorkbrad checkuser access

    Arbitrator Newyorkbrad (talk · contribs) has requested and been approved for Checkuser access. This is in order to allow him to more fully review Committee cases, and does not impact on the current Checkuser appointment process.

    FT2 (Talk | email) 01:18, 5 September 2008 (UTC)[reply]

    I thought all arbs had CU privileges? -- lucasbfr talk 12:08, 5 September 2008 (UTC)[reply]
    It is given on request, some arbs opt not to request it. NYB had not requested it until now. MBisanz talk 12:15, 5 September 2008 (UTC)[reply]
    Ok, thanks for the clarification :) -- lucasbfr talk 12:41, 5 September 2008 (UTC)[reply]
    All arbitrators automatically receive Oversight access, but not Checkuser. I had not previously requested Checkuser because I don't have the technical background needed to do sophisticated checking. However, I've decided that access to the database and the checkusers' mailing list will be helpful to me in connection with arbitration cases and related matters. I thank my colleagues on the committee for their approval of my having this access. Newyorkbrad (talk) 15:37, 5 September 2008 (UTC)[reply]
    Just a minor correction. As with the case of CheckUser, the oversight access is not automatic. -- fayssal / Wiki me up® 17:41, 6 September 2008 (UTC)[reply]

    Automatic AFD closing script

    As I noted here, I've been working on an automatic AFD closer script. Instructions and usage notes are at User:Mr.Z-man/closeAFD. Direct any bugs/feature requests/comments to my talk page. Mr.Z-man 02:19, 5 September 2008 (UTC)[reply]

    Yeays!! This rocks most seriously. Add a "relist" button and you have made me (and, I'm guessing a lot of other editors) happy! — Coren (talk) 02:51, 5 September 2008 (UTC)[reply]
    Wicked awesome. Once you get the relist function working I can start using it to clean up the notorious backlog. :) Protonk (talk) 03:30, 5 September 2008 (UTC)[reply]

    A day late and a dollar short, at the request of Cirt, I just updated the old CloseAFD.js to support non-admin closure. -- Gogo Dodo (talk) 07:22, 5 September 2008 (UTC)[reply]

    User:Mr.Z-man/closeAFD is absolutely incredible - many thanks to Mr.Z-man (talk · contribs). Someone should buy him a round of Duff beers. Cirt (talk) 08:20, 5 September 2008 (UTC)[reply]
    In lieu of that I've given him a barnstar. Stifle (talk) 10:59, 5 September 2008 (UTC)[reply]
    Omai, I'm utterly impressed, good work —— RyanLupin • (talk) 11:41, 5 September 2008 (UTC)[reply]
    Holy... that's awesome! Second the barnstar - excellent work! Tony Fox (arf!) 16:08, 5 September 2008 (UTC)[reply]

    I LOVE it. So much easier to use than the old one, and works like a gem in FF3 on my Mac. TravellingCari 05:26, 6 September 2008 (UTC)[reply]

    Relisting added - you may need to bypass your cache of the script to get the newest version. Mr.Z-man 17:24, 6 September 2008 (UTC)[reply]

    {{Support}} {{Oppose}}

    Hi, Is there any reason not to have templates for  Support and  Oppose? I really struggle to accept the 'server load' argument that seemed to dominate the TFD. Regards, Ben Aveling 12:56, 5 September 2008 (UTC)[reply]

    They have them on lots of other projects. I'm sure someone will soon complain about voting, but I don't see the harm unless someone can prove there is a technical science/server reason not to. They were deleted by an ancient and probably not valid consensus from 3+ years ago: [6] I'd say its overdue for review. rootology (C)(T) 13:07, 5 September 2008 (UTC)[reply]
    It was a valid consensus at the time. But I suspect that attitudes have changed. I should probably be taking this to WP:DRV but I just thought I'd solicit some opinions here first. Thanks, Ben Aveling 13:13, 5 September 2008 (UTC)[reply]
    One of the main reasons was because it encourages the notion that we're voting on issues, when we're really trying to develop a consensus. Stifle (talk) 13:27, 5 September 2008 (UTC)[reply]


    Please explain how these might enhance debates and discussions on wikipedia? You ask "is there any reason not to have..?" can I ask "is there any reason to have.."". This is a genuine and not a polemical question.--Troikoalogo (talk) 13:28, 5 September 2008 (UTC)[reply]

    (ec) Consistency with other wikis; it's annoying to type {{support}} and have to change it to support. Also ease of vote counting. There are decisions made here that look like votes but aren't (AFD, for eg). But there are things that genuinely are votes. Maybe a compromise would be to have the templates there, minus the symbols. Personally, I like the added colour, but I understand that there are people who don't. Regards, Ben Aveling 13:37, 5 September 2008 (UTC)[reply]

    Presumably, looking over a discussion with those templates makes it easier to read, especially if we don't split into support and oppose sections. — Werdna • talk 13:31, 5 September 2008 (UTC)[reply]

    "Easier to read"? Methinks, you mean "easier to count". Can't see how it helps me read the actual discussion.--Troikoalogo (talk) 13:34, 5 September 2008 (UTC)[reply]
    Also easier to read selectively. Suppose one is closing an AFD, has made a decision, and wants to be sure that all the opposing arguments have been dealt with. Symbols make that easier to do. Cheers, Ben Aveling 14:00, 5 September 2008 (UTC)[reply]

    Fun to have, but ultimately detrimental. We have enough knee-jerk supports and opposes breaking our processes without providing a set of templates to encourage more. ➨ ❝ЯEDVERS❞ has nothing to declare except his jeans 13:36, 5 September 2008 (UTC)[reply]

    Agree with Redvers. Don't see a benefit for it (just my opinion). -- Alexf42 13:42, 5 September 2008 (UTC)[reply]

    Er - do the little plus and minus symbols really impact how people participate? I see plenty of Support and Oppose comments without detailed rationales, is there is any reason to think we'd see a storm of such comments if we enable the templates? Avruch T 13:43, 5 September 2008 (UTC)[reply]

    If people from other projects are having issues I probably wouldn't be opposed to a template being created that consists of:
    '''Support'''
    that wouldn't change much from what people do anyway. –xeno (talk) 13:44, 5 September 2008 (UTC)[reply]
    • I have to say I like the look of them and the general idea behind them but, I think they may actually make things harder to read/understand if abbused in the same manner as '''support'''/'''oppose'''/'''keep'''/'''delete'''/'''don't delete'''/etc are at the moment. Jasynnash2 (talk) 14:01, 5 September 2008 (UTC)[reply]
    There was a DRV not too long ago for them, and consensus there was still pretty clearly that we don't want them (but that they're kosher in userspace, so feel free to steal my versions at User:Lifebaka/+, User:Lifebaka/-, and User:Lifebaka/=). I'll go dig up the link. lifebaka++ 15:25, 5 September 2008 (UTC)[reply]
    Link is Wikipedia:Deletion review/Log/2008 July 17. Cheers. lifebaka++ 15:32, 5 September 2008 (UTC)[reply]
    If someone with templatre Clue can code it so that there is an argument |reason, and if it's missing then the !vote is not bolded and a comment "(no rationale is given for this comment)" then I think it would add some value. Guy (Help!) 22:27, 5 September 2008 (UTC)[reply]
    Try User:Ben Aveling/support. For eg:
    • {{User:Ben Aveling/support}} gives support (no rationale given)
    • {{User:Ben Aveling/support|Reason being...}} gives Support: Reason being....
    The equivalent templates for Oppose, Neutral and Question can be created once the inevitable bugs are worked out. Regards, Ben Aveling 06:34, 7 September 2008 (UTC)[reply]
    No further comments? I guess that means that there is consensus that templates without icons, as per the example, would be OK? Absent further comments or objections, I'll take this to DRV tomorrow. Thanks, Ben Aveling 09:20, 8 September 2008 (UTC)[reply]

    User:Opinoso

    User:Opinoso continues with disruptive behavior and edition war in Italian_Brazilian and other topics. It is the same in Portuguese Wikipedia.

    Take a look.

    --Quissamã (talk) 00:24, 6 September 2008 (UTC)[reply]

    User:Opinoso insists in disruptive behavior and edition war in Italian_Brazilian article.

    He does not want that tags placed in the text or to provide reliable sources to controversial facts.

    The same User:Opinoso has a long history of disruptive behavior in Portuguese Wikipedia. He is not fit to group work, is renowned for insulting everyone that has a different opinion and does not seem to have a good knowledge of any field that he pretends to contribute.

    --Quissamã (talk) 01:30, 8 September 2008 (UTC)[reply]

    Bizarre block

    The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.
    Resolved. Looks like just a mistake based on a simple misunderstanding or misinterpretation of WP:AIV processes, there's no crisis or ongoing problem, closing thread. Dreadstar † 05:15, 6 September 2008 (UTC)[reply]
    • Note: Please don't inform the stewards of this thread. They've heard already, thanks. Kylu (talk) 01:57, 6 September 2008 (UTC)[reply]

    On the basis of this 'warning': User talk:THEN WHO WAS PHONE?#Warning

    Please do not leave messages on the talk pages of IP addresses. Many IP addresses are public computers used by many people, and a warning against vandolism is pointless as it will never be read by the vandal. Moreover, all you accomplish is to create a new talk page for a user who does not really exist. I know you meant well but it was a mistake, just do not do it again. Slrubenstein | Talk 00:24, 6 September 2008 (UTC)[reply]

    i.e. THEN WHO WAS PHONE was warning IP vandals, Slrubenstein blocked THEN WHO WAS PHONE for 15 minutes. This seems completely bizarre to me. Nunquam Dormio (talk) 01:05, 6 September 2008 (UTC)[reply]

    This is bizarre, and seems to go entirely against common sense. Every IP vandal had to make their first edit at one time or another, and putting a warning on their talk page helps to establish the record of their activity (and warnings) in case it is needed in the future. What policy does this go against, exactly? Ed Fitzgerald "unreachable by rational discourse"(t / c) 01:08, 6 September 2008 (UTC)[reply]
    Agreed. Blocking is completely inappropriate for the perfectly normal process of issuing warnings to IP vandals; if we don't issue warnings, we shouldn't block. Bizarre. --Rodhullandemu 01:14, 6 September 2008 (UTC)[reply]
    This is an entirely improper block, and Slrubenstein should resign his adminship. How else is any IP who repeatedly commits vandalism supposed to get through the warning tree before they can be listed at WP:AIV? There are so many things I want to say in outrage that I've redacted here. Gaaaahhhh. Corvus cornixtalk 01:11, 6 September 2008 (UTC)[reply]
    A very unhelpful and disruptive block. The notion that an editor could be blocked for leaving warnings on IP talk pages is unsettling. Moreover, many IP editors do read their talk pages and answer notes left on them. Gwen Gale (talk) 01:15, 6 September 2008 (UTC)[reply]

    Slrubenstein just placed the same warning at User talk:WadeSimMiser. Corvus cornixtalk 01:17, 6 September 2008 (UTC)[reply]

    And to User talk:Canis Lupus. Corvus cornixtalk 01:18, 6 September 2008 (UTC)[reply]
    • I feel like every week I say "that's the worst block I've ever seen", but wow. Awful. Anybody mind if I note in his block log that the previous block was not supported by policy? - auburnpilot talk 01:17, 6 September 2008 (UTC)[reply]
    Please do, I had the same thought. Gwen Gale (talk) 01:21, 6 September 2008 (UTC)[reply]
    Done. Unfortunately, somebody needs to counsel Slrubenstein. See the message he/she left on my talk page. Wow. - auburnpilot talk 01:27, 6 September 2008 (UTC)[reply]

    Comment - I have engaged User:Slrubenstein via talk page, and several have piled on, and of course there is this thread. Let's try to keep the discourse to policy and away from statements which can cause tempers to flare quickly. We've had enough wheel-warring for one week (at least), and that's coming from someone old enough to remember what "wheel" originally was - like my age has anything to do with it :-)

    I think we can mostly agree that the warnings regarding editors who place warnings IP vandal talk pages are not in keeping with common practice, and that blocking an editor who does so is even less in keeping with common practice. We've alerted the admin in question...let's see what happens from here.  Frank  |  talk  01:26, 6 September 2008 (UTC)[reply]

    Agree. Cenarium Talk 01:33, 6 September 2008 (UTC)[reply]
    Fine by me. I have to agree this was a bad play. I warn IPs all the time, because if they're vandalizing *right now* then they get the message and hopefully stop. That's how I was taught to do it, and that's really the right way to do it. Tony Fox (arf!) 01:36, 6 September 2008 (UTC)[reply]

    I think a block and emergency desysoping should be considered - I can't believe any admin would do something like this, which suggests the account may have been compromised or the admin is acting in bad faith. --Tango (talk) 01:39, 6 September 2008 (UTC)[reply]

    I thought of that, and I'm sure we're not the first to think of it. However, this is a long-time editor whose granting of admin rights doesn't even appear in the user rights log, and there isn't really anything unusual to be seen in the pattern of contributions of this editor. I'm certain there are a dozen people watching very closely; we can request more drastic steps when necessary - but I don't think that is required now.  Frank  |  talk  01:45, 6 September 2008 (UTC)[reply]

    I left a link to this discussion on Slrubenstein's Talk page, but instead of responding here, he's only dealing with people on his Talk page. His most recent edit on this subject: [8] indicates that he has no interest in actually stopping this bizarre behavior. Corvus cornixtalk 01:47, 6 September 2008 (UTC)[reply]

    Oh, my god. In that case, this seems to be a either a compromised account or worse. Should I put in an emergency desysop request on Meta? (actually, where do you do that?) J.delanoygabsadds 01:49, 6 September 2008 (UTC)[reply]

    (ec)It would appear Slrubenstein (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) either has an incredibly bad misunderstanding of official policy in regards to WP:BLOCK, or this account has been hijacked. Either way, the safety of the project looks to be in danger and we should move accordingly. --Kralizec! (talk) 01:51, 6 September 2008 (UTC)[reply]

    I agree that it's possible the account is compromised. Either way, this kind of violation of policy/common sense from somebody with admin tools calls for desysoping. Jamie☆S93 01:55, 6 September 2008 (UTC)[reply]
    You think this block is bad? See Wikipedia:Administrators'_noticeboard/Incidents#Insults_again_and_again_and_again. Outrageous. AlasdairGreen27 (talk) 01:52, 6 September 2008 (UTC)[reply]
    Heh, then contact a CU to see if it's compromised. But it may very well be a misunderstanding. Don't go summon the dragon yet. Cenarium Talk 01:55, 6 September 2008 (UTC)[reply]
    The account has not been compromised, it's just an admin with a poor understanding of policy (to put it mildly). Back in February, Slrubenstein delete several talk pages where an editor left warnings for IP users. Tonight, he/she deleted another 10, where THEN WHO WAS PHONE? (talk · contribs) left warnings. - auburnpilot talk 01:57, 6 September 2008 (UTC)[reply]
    In any case, bureaucrats can't remove sysop access. Titoxd(?!? - cool stuff) 01:59, 6 September 2008 (UTC)[reply]

    (cross posted from user page) Please, folks - calm down. Slrubenstein has been engaged, and please note that none of the behavior in question has occurred since it was initially questioned. We are poking at a sore wound right now, and that is not going to help. If Slrubenstein begins taking actions again that are against policy, we can deal with it then, but there is no point in continuing to discuss it at this point. The behavior has - at least for the moment - stopped. Let's leave it alone for now.  Frank  |  talk  01:58, 6 September 2008 (UTC)[reply]

    I concur, there is no emergency. Calm down all. Cenarium Talk 02:00, 6 September 2008 (UTC)[reply]
    I'm glad that admins blocking other admins for stupid reasons is so commonplace as for you to retain your composure.... (striked since TWWP is not an admin, much to my surprise) --mboverload@ 02:13, 6 September 2008 (UTC)[reply]
    After I read more about this situation, it really does not appear that his account is compromised. And although I agree this isn't exactly an emergency, I still would support removal of the tools if he really plans to continue these actions as an administrator. Jamie☆S93 02:22, 6 September 2008 (UTC)[reply]

    Rubenstein does have a point regarding the difficulty of meaningfully communicating with shared- and/or dynamic-IP users (not that warning templates are meaningful communication, mind you), However they are obviously not within the going definition of "nonsense pages" and this is a very stupid block, and I can only hope PHONE-guy doesn't take it personally. — CharlotteWebb 02:08, 6 September 2008 (UTC)[reply]

    • Comment. This was a bad block, no doubt about it. But let's get one thing straight, while it's come up--Corvus comix and others have stated a couple of times that warning an IP before a block is required: that is not true and never has been. WP:AGF means of course that warnings must be given before a block if there's a reasonable chance of a person changing their behavior, but in cases where there is no such chance (such as renewal of a previous pattern of vandalism on a new IP), blocking on sight is not a problem. That doesn't mean that Slrubenstein is right here, it just means that the extreme opposite point of view is not right either. Chick Bowen 02:15, 6 September 2008 (UTC)[reply]


    Admin Slrubenstein has been engaged on this subject here, here, here, and elsewhere. What seems very much like closure from Slrubenstein appears here. Activity has stopped, and clearly a number of editors below will be watching. It does not appear there is any compromise or need for panic, and if it turns out that such is the case, we can panic later. Otherwise, nothing to see here (anymore).  Frank  |  talk  02:25, 6 September 2008 (UTC)[reply]

    HOLD ON a second

    Why are we discussing meta-wikipedia viewpoints when an admin is pulling this shit? Maybe I'm the last person who things that BLOCKS ARE NOT SMALL THINGS. They are HUGE. I've been blocked once and I still regret it 3 years later. Someone tell me I'm freaking crazy, cause I sure feel like it. --mboverload@ 02:23, 6 September 2008 (UTC)[reply]

    Ok, you're freaking crazy. (hey, you asked for it!)Seriously, though, can we cut it out with the over-reactions and the RANDOM CAPS? Things are happening. The wheels of justice grind slow, but they can grind mighty fine. SirFozzie (talk) 02:26, 6 September 2008 (UTC)[reply]

    Thread closure

    I'll note that there are two editors attempting to mute discussion. I will not revert another closure, but it is disruptive. NonvocalScream (talk) 03:04, 6 September 2008 (UTC)[reply]

    I will also note that topics can change in any given thread, however, templates tend to disrupt the normal discussion flow. Off topic (or change-topic) discussion is not a good reason to add these templates. NonvocalScream (talk) 03:08, 6 September 2008 (UTC)[reply]

    If I may, I wasn't concerned about a compromised account, I was concerned because putting a warning on an empty IP talk page is something I do as a matter of course numerous times almost every day, and I don't want to get blocked! I'm glad to see that most folks here seem to agree that this admin's take on it is not normative. Ed Fitzgerald "unreachable by rational discourse"(t / c) 03:13, 6 September 2008 (UTC)[reply]
    For my own part, I reject the characterization of closing the discussion as attempting to mute it. The point of this thread was to discuss the specific warning and block actions of a specific administrator. That issue has been resolved and deserves to be listed as such. If there is subsequent wikidrama debate about what the exact correct procedures are or should be (good luck with that), even if it was sparked by this thread, that doesn't change the fact that it is peripheral and doesn't belong as part of this thread. This one deserves to be closed as resolved simply for the sake of organization.  Frank  |  talk  03:16, 6 September 2008 (UTC)[reply]
    The admin in question has agreed to stop these actions, so I think the matter is closed unless he decides to try and change the policy, but that wouldn't happen here anyway. I think this thread can be closed for good now. --Tango (talk) 04:55, 6 September 2008 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Response to Chick Bowen's comments in the section above

    Please read WP:AIV:

    Important! – your report must follow these three points:
    1. The edits of the user you are reporting must be considered vandalism.
    2. Unregistered users must be active now.
    3. The user must be given sufficient recent warnings to stop.

    If I (or anybody else who is not an admin and is reporting vandalism at WP:AIV) list a currently-vandalizing user on WP:AIV, if they have not been given the sufficient number of warnings, the listing is always removed with no action being taken. Corvus cornixtalk 02:50, 6 September 2008 (UTC)[reply]

    That applies to AIV. In any case, AIV is not a policy page. Wikipedia:Blocking policy does not specify that warning is necessary. Once again, if there is evidence that a new IP is actually a returning disruptor with a new IP, there is no need for a warning, nor is one routinely given. I'm just describing current practice here--I'm not stating an opinion or, really, anything new. Chick Bowen 03:00, 6 September 2008 (UTC)[reply]
    So how do I get a new IP blocked without going through the warning tree? Post it here or on ANI? You get told "take it to AIV". If I take to AIV without going through the warning tree, the listing gets deleted. Should I admin canvass? Corvus cornixtalk 03:05, 6 September 2008 (UTC)[reply]
    ANI is usually best for the clear-cut stuff--our friends who like to put filthy pictures into prominent articles, that sort of thing. I admit I haven't worked on AIV for quite a long time, but I believe the idea there is that for ordinary schoolboy vandalism the warnings should be gone through. Chick Bowen 03:11, 6 September 2008 (UTC)[reply]
    Now I am thoroughly confused. You yourself said above Corvus comix and others have stated a couple of times that warning an IP before a block is required: that is not true and never has been. Now you tell me that I do have to go through the warnings. I think I'll just continue what I've been doing, since to do anything else will just cause me too much frustration when my listings at AIV get removed without the vandals being dealt with. Corvus cornixtalk 03:20, 6 September 2008 (UTC)[reply]
    Here is my perspective as an admin who has processed AIV reports nearly every day for the past nine months ... WP:BLOCK's statement that "efforts should be made to educate the user about our policies and guidelines" meshes nicely with both WP:AGF and WP:BITE. When it comes to unregistered users, if we do not warn them that their vandalism will not be tolerated, how will they ever learn otherwise? In my experience, a very large fraction of anonymous users receiving talk page warnings quit vandalizing after their first or second warnings. Since most of these "experimenting" vandals are scared off by the warnings issued by our dedicated vandal patrollers ... Slrubenstein`s idea that only admins should deal with these IP users (and only via blocks!) is laughable at best. As if admins are not already busy enough (to say nothing of the fact that is would idle one of our most powerful anti-vandalism tools: our corps of patrollers)! --Kralizec! (talk) 04:10, 6 September 2008 (UTC)[reply]
    Let me just add that as far as I am concerned, there is far too much assumption of bad faith on AIV that the people listing vandals are the bad guys, and that the vandals themselves are just misunderstood. Corvus cornixtalk 03:21, 6 September 2008 (UTC)[reply]
    I suspect that's true. Chick Bowen 03:26, 6 September 2008 (UTC)[reply]
    Corvus, that's not quite true. Whilst I'm less likely to block an IP that hasn't been warned completely, if I look at the contribs and see that it's clearly an IP on a vandalism spree and isn't likely to contribute positively any time soon, then I'll block anyway [9] [10] [11] [12]. However, what I won't do is block if an account is insufficiently warned and appears to be a clueless newbie editor or content dispute (in fact sometimes I won't block these even if they have 4ims). I know a number of other admins work like this too.
    Whilst 90%+ of reporters on AIV are good, there are always people, especially those with semi-automated tools, who are too quick to judge things as vandalism. For example, I have seen reports for people "vandalising" the sandbox, or their own user pages, and once for someone who put "I f*cked up that last edit" in an edit summary. A lot of AIV reports could be prevented by instead of a massive automated boilerplate on their talkpage, just a "Hi there - it's probably a good idea if....". Just my thoughts. Black Kite 12:00, 6 September 2008 (UTC)[reply]

    Why does Kralizek misrepresent me? She writes, "Slrubenstein`s idea that only admins should deal with these IP users (and only via blocks!) is laughable at best." which not only sounds snide, insulting, and an attempt to bait me, it is just not true., Nowhere have I ever written that onlhy admins should deal with IP users, and only via vlocks. In fact, my position is the opposite. I have stated that when the vandalism is of the juvinile sort, and is a case of one or a few edits ove a very short period of time from a public, shared adress, editors 9any editor) should just revert the vandalism. Please tell me where I said only admins should do this, and only via blocks. If I expressed myself unclearly or incorrectly I will apologize immediately. Otherwise apologize for lying about what I wrote. Slrubenstein | Talk 14:34, 6 September 2008 (UTC)[reply]

    Bad-faith accusations of me being insulting or lying ring rather hollow as we can all readily see the proof in your edit history:
      • At 19:24 you said [13] to THEN WHO WAS PHONE?, "Please do not leave messages on the talk pages of IP addresses. Many IP addresses are public computers used by many people, and a warning against vandalism is pointless as it will never be read by the vandal. Moreover, all you accomplish is to create a new talk page for a user who does not really exist." Note that you made zero distinction between static, shared, or public IP addresses in your instructions to this editor.
      • Then 56 minutes later, you said [14] on your own talk page, "If it is an obvious case of vandalism, and it is a shared address, an admin can block the address for six or twelve or twenty-four hours without giving a warning."
    Taken together, it appears that you pretty clearly told a vandal fighter to stop warning IPs and that admins should just block the vandals without ever trying to educate them. I am sorry if this is not what you were meaning, but all we have to go on is the face value of what you wrote, and what you wrote is dangerously out of step with current guidelines, policies, and community consensus. While I have the utmost respect for your long history of contributions to the project, I suspect that your dated understanding of our guidelines and policies means that you would have great difficulty passing a modern RfA. (And for reference, my username is Kralizec! and I am a "he" - and have the wife and three kids to prove it!) --Kralizec! (talk) 22:02, 6 September 2008 (UTC)[reply]

    Thank you for explaining, I appreciate the chance to clear up the misunderstanding. I fear you took two statements out of context. The first statement was indeed a criticism of the creation of new pages for IP addresses. But I did not say that non-admins should not deal with vandals. In fact, I have on several occasions applauded PHONE and others' vigilent reversion of vandalism. That is a way of dealing with vandals that is necessary, tedious, and valuable and I am grateful to any editor who does it, and I certainly do not think that one has to be an admin to do this.

    The second comment was a direct response to another editor who claimed that policy required that one provide a warning before blocking. I quoted the policy that stated that one need not provide a warning before blocking a vandal. That was my only point: that the editor criticizing me was misquoting policy. Note: the issue has to do solely with whether a warning is required prior to a block (and policy explicitly says not always). The issue did not have to do withe whether only admins can block vandals, or whether all editors can block vandals. I simply did not address this particular issue. Now, Wikipedia may have a policy that only admins can block, and if you do not like that policy you can propose to change it. But I di dnot create that policy, and nothing I wrote was a defense of the policy. The conversation at that time was not over whether admins or non-admins could block, it was whether Wikipedia policy required a warning. One editor said it did, and I quoted the policy saying it did not.

    I now understand why you misunderstood me and am willing to grant that you did so with good intentions but you were not assuming good faith on my part. In both instances, I did assume good faith - one can assume good faith in another editor and disagree. In one case I explicitly said I knew the editor was acting in good faith but I though what s/he was doing was a mistake. In the second, I simply assume that the editor was acting in good faith when s/he misquoted policy; I did not question his/her intentions, I just asserted that s/he was mistaken and quoted policy.

    So with all due respect, and acknowledging now your intentions were good, you were mistaken to take two different comments I made to two different editors concerning two different matters, and infer by connecting them that I think only admins should deal with vandals.

    You are right that my view about the pointless or even counter-productive creation of new pages by warning IP addresses is out of step with the community. I hope you will acknowledge that once this was clear to me I stopped doing what I was doing. I do this to defer to the will of the community, not because I agree. But i do agree that neither i nor anyone else should revert these warnings unless - if ever - the community consensus changes. I think there is a need for new discussion on how we handle vandalism, especially from IP addresses. I mean just what I said and i am sincere and it in no way means I question the value of the hard work many editors do in reverting vandalism. I hope it is crystal clear to you and everyone else that I appreciate any editor who reverts vandalism, and thank them for their efforts. Is it possible for us to open up discussion on our policies in this regard while assuming good faith on one another's part? I certainly think someone can disagree with me in good faith. Slrubenstein | Talk 23:17, 6 September 2008 (UTC)[reply]

    Thank you for taking the time to explain your perspective; we all have a much better understanding of your intentions now. Please accept my apologies for being unnecessarily snide, as I see that your intentions were good. --Kralizec! (talk) 23:39, 6 September 2008 (UTC)[reply]

    Kralizic, I canot tell you how much this means to me - thank you. I hope everyone else who was active last night understands that I really thought it was clear that my actions were well intended and I deeply regret the grief I caused so many people. I will wait for things to cool down a bit more before inviting a discussion on our vandalism policy, but when I do it is precisely because I do respect and value the views of the community, and respect wiki process enough to think that we can have a frank discussion while assuming good faith on the part of peoploe with whom we disagree. I realize that people may feel it is noit worth discussion, or the discussion may lead us right back to what I know see is the status quo. I have always valued in Wikipedia the hope that, however difficult, consensus can be balanced with an open, never-ending discussion about a work that will always be "in process." Anywa, I apologize to you and others if I expressed myself unclearly or inappropriately - I know that at least a few times I was curt and eliptical and I know that didn't help things and I regret that. Slrubenstein | Talk 23:50, 6 September 2008 (UTC)[reply]

    I may have missed something, but I don't think I have seen either an apology to TWWP for the block, or an understanding that blocking someone for issuing warnings was clearly contrary to policy. DuncanHill (talk) 23:57, 6 September 2008 (UTC)[reply]
    I would like a straightforward explanation as well, and a clarification of the policy on warning vandals. This vandalism fighter is chilled to the bone by Slrubenstein's action. I thought I was doing the right thing. This could have been me. I could have been blocked. This is not minor, despite the premature archive and the "move along nothing to see" attitude shown by many on this thread. I've never been afraid to edit here before now. Aunt Entropy (talk) 03:20, 7 September 2008 (UTC)[reply]

    Tree Cannon (talk · contribs)

    I posted a report on this user on WP:AIV, but I also wanted to bring this here because this user's activity is giving me bad vibes.

    Tree Cannon (talk · contribs · deleted contribs · logs · filter log · block user · block log) is, from what I can guess based on his user page and contributions, a Japanese user who is unhappy that the English Wikipedia has fair-use images and the Japanese Wikipedia does not, and think it is "discriminatory". About a month ago, they decided to act like a sort of copyright police for Japanese media and removed fair-use images that were Japanese in origin ([15], [16], [17]). This got him blocked for 72 hours.

    The account remained silent until now, when the user began adding random Japanese and some vandalism to his previous targets ([18], [19]). When other editors informed them that their edits were undone, this user began replying entirely in Japanese ([20], [21]). One of these replies, [22], appears to be inflammatory as the text for it translates to: It is from the English [wa]. Another calling and. Already immediately September 11th, the party of arrogant America and the European person died the multitude. It is very happy important commemoration day. The exemption [ji] [te] permitting to that. The [ze] which probably will celebrate that day together. Toast! Another inflammatory comment, this time in English, was added after he was blocked by User:VirtualSteve for the previous edits.

    Though he's been blocked for a week, I think the inflammatory nature of some of his user-space edits and the incivil way he carries himself when commenting in general should warrant a somewhat longer block. NeoChaosX (talk, edits) 04:09, 6 September 2008 (UTC)[reply]

    wow. That sounds like some pretty serious rage. Indef block, anybody? Corvus cornixtalk 04:41, 6 September 2008 (UTC)[reply]
    The text of [23] reads, roughly, "I don't know English, but whatever. Soon it'll be September 11, when lots of arrogant Americans and Europeans died. It's a joyous, important anniversary. In deference to that, I'll forgive you. Let's celebrate that day together. Cheers!" Exploding Boy (talk) 04:55, 6 September 2008 (UTC)[reply]
    Someone needs to refer him/her to Wikipedia:Dude, it's a frickin' online encyclopedia. Chill out, already! (WP:DIAFOECOA for short). caknuck ° is geared up for football season 04:58, 6 September 2008 (UTC)[reply]
    And I thought I'd look at some of the others as well. The edits to (92 above) are just "also known as [name]" and "from a foreign-language DVD version." (93 above) is obviously silly as it's a random Japanese section in an English article. {94 above) is just a question about some edits to Miyazaki Hayao. (95 above) is getting silly. He says that Miyazaki is Japanese, and that he has been familiar with his work since childhood, so the other editor should more or less butt out. Exploding Boy (talk) 05:04, 6 September 2008 (UTC)[reply]
    I got a chuckle of out his comment on his user page: "I talk in Japanese also to those who cannot understand Japanese." So, here's my take on this user. He's obviously got a bee in his bonnet about what he seems to see as theft or unjustified use of images taken from Japanese works. Some of his edits could be seen as constructive, but adding Japanese language sections to English language articles is just silly, and the fact that he's added emoticons to at least one of them suggests that he knows he's being disruptive. Still, he's no worse than some other users we've yet to indefblock, and he's not being unbearably disruptive (yet). His poor English skills (he seems to be using an automatic translator) mean that he'll never be able to contribute very much here anyway. We just need to give him enough rope to hang himself. If he comes back after his block expires and continues to be disruptive, we can simply block him again. Exploding Boy (talk) 05:22, 6 September 2008 (UTC)[reply]
    Seconded.--Tznkai (talk) 05:36, 6 September 2008 (UTC)[reply]
    I'm sorry, I am not comfortable with having an editor here who calls for the celebration of the murders of over 3000 people. Corvus cornixtalk 05:33, 6 September 2008 (UTC)[reply]
    I've asked a native speaker to look over his edits and leave him a note. Exploding Boy (talk) 05:35, 6 September 2008 (UTC)[reply]
    A block of 7 days for incivility is a slap on the wrist and a tacit agreement that their disgusting comments are somehow acceptable. We should make a stand that any such behavior, celebrating the Holocaust, the Madrid or London bombings, the Dresden bombings, any such activities, is not acceptable. Period. Corvus cornixtalk 05:41, 6 September 2008 (UTC)[reply]
    For what it's worth, we are sorry about Dresden. A sincere personal note, it was my grandfather's only regret in life. Keegantalk 06:06, 6 September 2008 (UTC)[reply]
    I disagree that a 7 day block is a tacit agreement that someone's comments are acceptable. And Wikipedia is not in the business of saying what is or is not morally acceptable, just what is or is not acceptable for the encyclopedia. Quite frankly, if he doesn't cause any more ruckus, I don't care what he thinks.--Tznkai (talk) 05:45, 6 September 2008 (UTC)[reply]
    We don't block people for having distasteful opinions. The 7 day incivility block is the appropriate response to his behaviour to this point, most of which hasn't really been that awful. I see no particular reason to come down particularly, disproportionately hard on this user, annoying though he may be. Chances are he'll either get bored and stay away, in which case we don't have to worry about it, or come back and pick up where he left off, in which case we can block him again. Exploding Boy (talk) 05:46, 6 September 2008 (UTC)[reply]
    We require people to remove swastikas from their User pages. We block them when they refuse. Corvus cornixtalk 06:03, 6 September 2008 (UTC)[reply]
    Has this user refused to remove swastikas from his user page? Exploding Boy (talk) 06:04, 6 September 2008 (UTC)[reply]
    Come on, don't be intentionally dense. Apparently it's ok to celebrate the murders of Americans, but not to celebrate the murders of European Jews. Corvus cornixtalk 06:06, 6 September 2008 (UTC)[reply]
    Don't be unnecessarily sensational. Wikipedia isn't Germany or Austria; Holocaust denial is not a crime here. —kurykh 06:08, 6 September 2008 (UTC)[reply]
    This conversation is exhausting its usefulness. You don't like it Corvus, complain to Jimbo.--Tznkai (talk) 06:09, 6 September 2008 (UTC)[reply]

    (Undent) I wish our rules permitted me to block every user with distasteful opinions, but they don't. In my opinion, this user has not (yet) done anything that warrants an indef block. I endorse the 7 day block, and support further, longer blocks if he continues the behaviour, or an indefblock if escalated disruption warrants it. Exploding Boy (talk) 06:11, 6 September 2008 (UTC)[reply]

    Fine. User_talk:Jimbo_Wales#Should_we_allow_an_editor_to_edit_here_who_calls_for_the_celebration_of_the_deaths_of_thousands_of_people.3F Corvus cornixtalk 06:23, 6 September 2008 (UTC)[reply]

    What does Jimbo have to do with it? He is not a court of appeal for AN... Anyway, personally, I would indef block him since there is no point someone that says they can't speak English having an account on the English Wikipedia unless they are involved in some kind of cross-project work which this user doesn't appear to be. Short term blocks are for when we think the user might make useful contributions when they come back, that clearly isn't going to happen here. --Tango (talk) 06:33, 6 September 2008 (UTC)[reply]
    See above. You don't like it Corvus, complain to Jimbo. Corvus cornixtalk 06:36, 6 September 2008 (UTC)[reply]
    I know, the question was really intended for Tznkai, but the thread had been unindented, so I didn't want to reindent it! --Tango (talk) 06:52, 6 September 2008 (UTC)[reply]
    I'm going to have to agree that this user's words have been pretty awful - hate speech, pure and simple, which does nothing but harm our collaborative efforts - and that he shouldn't be permitted to contribute to this project unless we're sure he won't continue his tirades. krimpet✽ 06:37, 6 September 2008 (UTC)[reply]
    Oh, the drama. As I said above, some of his edits could be seen as constructive. Also, we don't prevent people from editing because their English isn't good. A note in Japanese with English translation has been left on his talk page, which reminds him that there are rules here which he must follow, including being civil to other editors. In my view, the issue has been resolved for now. Exploding Boy (talk) 06:41, 6 September 2008 (UTC)[reply]
    I feel silly for making that suggestion, because I never meant it as such, so much as a way of saying "This is the way things are, you don't like it, too bad." And i agree with Exploding Boy--Tznkai (talk) 06:43, 6 September 2008 (UTC)[reply]
    So in other words, stfu? Corvus cornixtalk 06:49, 6 September 2008 (UTC)[reply]
    Let me try it this way. WP is an encylopedia governed by certain policies. One of those is a commitment to neutrality. Another is a commitment to civility. A third is a principle to avoid making gestures, but to concentrate on the encylopedia. None of the policies we have allow us to punish someone just because he said something patently terrible. And finally a 4th is to assume good faith and that everyone has something useful to add, unless they have proven otherwise. That is not just my opinion, that's the way things are (within how I understand them.) I am unwilling to extend the block without further provocation. It seems Exploding boy is also. However, if you really think its a Really Big Deal, your option is, as always, to escalate it to a higher authority, and around here, that's Jimbo. I don't think its a particularly good idea.--Tznkai (talk) 07:04, 6 September 2008 (UTC)[reply]
    I'm not suggesting blocking him just because of his English, I'm suggesting blocking him because he's being disruptive and making it indef because there is little reason not to (cost-benefit analysis and all that). --Tango (talk) 06:52, 6 September 2008 (UTC)[reply]
    I am inclined to agree with Corvus Conrnix (and Tango) here, about the severity of the prolem, although with some qualms; ultimately I basically support the current block although I can see some cause to extend it another week. I highly prize the value of free expression of views, especially offensive views, at Wikipedia because we need to create an inclusive environment for NPOV to work effectively. So this is my standard. It leads to three question I think in this case: (1) would banning this user drive away editors whose points of view are so different from our own, and so offensive to us, that we actually need them at Wikipedia, to ensure that all notable views are included in the encyclopedia? (2) would the continued presense of this editor drive away other editors who make valuable contributions to the project? Finally, (3), does the specific behavior in question contribute to the improvement of any article? This in the end is what it is all about: improving articles. Now, from what i have read, my poiints 1 and 2 do not really apply here or cancel each other out, though I wonder if anyone disagrees with me, i would like to hear it. So I get stuck on my third point. This guy is not calling for the inclusion of an alternate (however offensive) view in an article. he is simply using his own user page to spew hate. This is why I lean towards Corvus Cornix. We should not let anyone hijack Wikipedia to spew hate speech. I have seen other suers make no edits to articles because their edits would violate our core content policies; instead they just edit talk pages or their user page - pages where NPOV and NOR do not apply - and in effect they are making a mockery of our core values. User pages have a value in introducing enough of ourselves to facilitate collaboration. That is there purpose. This is not My Space or Facebook or a blog, user pages do not exist just for individuals to have their own web-page on the web, they serve a function in Wikipedia. Again, this user seems to me to be perverting that function. I am not sure I would ban him but I would consider a long block. Remember, blocks are NOT punitive. They are meant to stop disruptive behavior and provide time for a person to reflect on and reconsider their acts. I would support a block that was long enough to throw a wrench in his disruptive behavior (one week would obviously be reasonable) and also enough to give him time to study our content and personal behavior policies so he can learn the error of his ways - if English is not his first language, two weeks may be called for. This guy is a newbie, and has made some valid edits, so I oppose an indef. ban. I really think we should try a rehabilitation through a block first, and make it clear to him that he cannot abuse his user page or talk pages, and needs to learn our core values via our policies. A block sends the message and provides time for education. Is my reasoning off? Slrubenstein | Talk 06:58, 6 September 2008 (UTC)[reply]
    At least two of the diffs above are not vandalism. One is an edit to the article that did add some relevant information (albeit in Japanese). The other is a request for explanation (again, in Japanese) on a user's talk page. What seems to have provoked the outburst about 9/11 is frustration. Now, I'm not saying I like this guy, and I'm not saying his behaviour is acceptable. This is the English Wikipedia site, and contributions need to be in English (and some of his have been), and civility applies even when there's no reasonable expectation that the target will understand what you've left on their talk page. But as I said above, for now the steps we've taken seem sufficient: we've given him a week-long block (quite proportionate to his behaviour), and we've left messages on his talk page. We've even taken the additional step of leaving a message on his page in his language so that there can be no doubt that he understands it. I still see no reason to upgrade this to an indefblock, yet. Exploding Boy (talk) 07:14, 6 September 2008 (UTC)[reply]
    Current wikipedia policy is that we do not block people for their opinions, whatever they are but only for their behaviour.
    Celebrating 9/11 (as a positive event) is not acceptable behaviour because it is not related with writing an encyclopaedia and because it is not wp:civil, particularly in a project where the majority of the contributors are US citizens or live there.
    The current consensus is that 7 days is a good period for such a vandalism, which remains, in my point of view, a provocation.
    If he goes on, the block will be increased, for the same reasons that the people who refused to remove swastikas were undefinitely (?) blocked.
    Ceedjee (talk) 08:48, 6 September 2008 (UTC)[reply]

    Background and updates

    This reminds me of the banned Kanabekobaton (talk · contribs)/Euroleague (talk · contribs) and this long recent thread. The CU could not confirm Tree Cannon as being Kanabekobaton though. That said, it could have something to do with this 2007 incident instead.

    Anyway, what we got for sure is that 0oors (talk · contribs) is a sockpuppet of Tree Cannon (talk · contribs) and has been blocked indef for sockpuppetry. A week for TC (the master account) is reasonable. We'll see. -- fayssal / Wiki me up® 08:23, 6 September 2008 (UTC)[reply]

    Tree Cannon has left a longish and rather polite post on his talk page in response to the message left in Japanese yesterday. The gist of it is that he is aware of the rules and promises to abide by them from now on (and a bunch of other stuff about different rules for different Wikipedias being unfair, and some other, somewhat more esoteric complaints). Exploding Boy (talk) 16:04, 6 September 2008 (UTC)[reply]
    I can't read Japanese but I do believe you. And, does he say he's got something/nothing to do with the cases I mentioned above? -- fayssal / Wiki me up® 17:28, 6 September 2008 (UTC)[reply]
    You keeping on eye on him?--Tznkai (talk) 16:12, 6 September 2008 (UTC)[reply]
    He's blocked for a couple more days isn't he? Exploding Boy (talk) 16:17, 6 September 2008 (UTC)[reply]

    fayssal: he doesn't mention anything, but he acknowledges that he was being disruptive, and apologizes. He has also been warned that other users have found some of his comments offensive. My guess is that he'll be ok from now on, but if he isn't he has no excuse: he's been made aware of the rules and has acknowledged that he understands them and that his previous behaviour was unacceptable. As a side note, another user has also explained to him that copyright policies on the various Wikipedias (one of his major complaints) are based on various countries' laws rather than on the whim of the various language editions' editors. Exploding Boy (talk) 18:35, 6 September 2008 (UTC)[reply]

    Thanks EB. -- fayssal / Wiki me up® 03:17, 7 September 2008 (UTC)[reply]
    Now Tree Cannon understands the copyright policies and realizes that he was barking up the wrong tree. I was asked to post his apology. To those who I hurt so badly. I am fully aware of what I have done is indefensible. I am ashamed of my thoughtlessness and filled with remorse. Please accept my apology. Oda Mari (talk) 15:02, 7 September 2008 (UTC)[reply]

    Thanks for all your help with that. Exploding Boy (talk) 15:49, 7 September 2008 (UTC)[reply]

    Malfunction on User:BJBot

    User:BJBot appears to be tagging non-free images incorrectly as being orphaned despite them actually containing proper citations and not being orphaned such as Image:ALW-Uniform-OAK.PNG. Also it appears other pages are also being tagged by mistake. Gateman1997 (talk) 06:19, 6 September 2008 (UTC)[reply]

    From User talk:BJBot: "Read this first Sometimes MediaWiki will report an image not being used when it really is, and the bot will tag it in error. If this happens, revert the bot's edit to the image, and make a null edit to the article containing the image (click edit, then save without making any changes)" ~ AmeIiorate U T C @ 12:15, 6 September 2008 (UTC)[reply]
    BJ should fix the bot, users having to do that is some hack job. — Rlevse • Talk • 01:45, 7 September 2008 (UTC)[reply]
    In this case it was triggered by this page blank vandalism, which for a short time, made the image technically orphaned. MBisanz talk 01:54, 7 September 2008 (UTC)[reply]
    (ec) That is actually much more complicated that it seems to appear. What happens is that the tables in MediaWiki do not update when there's high server load; instead, these entries get moved into the job queue. There is no way for a bot (or an editor, by that matter) to know that an image is included in a page because neither the "used in" list at the bottom of image pages, as well as Special:Whatlinkshere shows the image used anywhere. The only way to flush these tables is to force pages through the save parser, which updates all the links tables that point to any given page. Titoxd(?!? - cool stuff) 01:57, 7 September 2008 (UTC)[reply]
    Yeah but... the description page for a "fair use" image is generally expected to link to the article(s) where it is used. It would be easy for a bot to follow these links, do a null edit, then reload the image page and decide whether it's actually orphaned. — CharlotteWebb 19:03, 7 September 2008 (UTC)[reply]
    I updated the message earlier, if isn't done manually two different bots remove the template. BJTalk 02:17, 7 September 2008 (UTC)[reply]

    Kingdom Now theology now a target for the Palin POV pushers

    Resolved

    I'd like to request semiprotection on the page as it's getting hit by rumormongering IPs...Aunt Entropy (talk) 06:24, 6 September 2008 (UTC)[reply]

    I put in a request over at RFPP and pointed them to this discussion. NeoChaosX (talk, edits) 06:34, 6 September 2008 (UTC)[reply]
    I did a partial protection of the article, which should provide time for people to work it out on th talk page. Slrubenstein | Talk 14:28, 6 September 2008 (UTC)[reply]
    Total of 4 IP edits in the 12 hours preceding protection. *awaits chorus of impassioned "it's a wiki" objections that are de rigueur when reg editors find they can't edit* 86.44.29.35 (talk) 07:57, 7 September 2008 (UTC)[reply]
    What on earth does that mean? Regular--that is, logged-in--users can edit. Prince of Canada t | c 08:04, 7 September 2008 (UTC)[reply]
    I was drawing attention to how amusing it is that a decision to semi-protect of any sort rarely draws any scrutiny from registered users, whereas full protection is routinely railed against on these pages using arguments that apply equally to both protection types. 86.44.29.35 (talk) 20:38, 7 September 2008 (UTC)[reply]

    Query about User:Crommorc

    Hi! I'm a newbie admin, so I would appreciate advice as to what should be done here. I was patrolling the New User's contributions, and I noticed one name cropping up time and time again, that of User:Crommorc. This editor's actions appear to consist soley of removing references to anything barefoot, and the edit summary is almost always the same: Removed barefoot fetish vandalism.

    I have no experience of the topics of any of the articles this person has edited, so I don't know if this is genuine vandalism revertion (although there doesn't seem to be any pattern to it), or if this is someone going through censoring Wikipedia from anything to do with bare feet. I know WP:BITE and WP:AGF should apply, and if this is genuine reversion, I don't want to stop it. If it isn't, I would like this nipped in the bud before there is too much to do to revert it all. What should be done? StephenBuxton (talk) 14:10, 6 September 2008 (UTC)[reply]

    Actually, I saw someone else going through and starting to revert the edits, having dropped a query on the talk page. I then decided to help go through the list, and then drop a level one censor warning on the talk page. I'll keep an eye on Crommorc, I think. StephenBuxton (talk) 14:25, 6 September 2008 (UTC)[reply]
    There is, apparently, a "barefoot fetish vandal", indefinitely blocked for disruption, who launches socks from time to time. If someone could provide the SSP link, and review the accounts that Crommorc was reverting, it may be that these are more of the same. LessHeard vanU (talk) 16:02, 6 September 2008 (UTC)[reply]
    They are back as TheBoneWoman (talk · contribs)--118.93.81.226 (talk) 02:32, 8 September 2008 (UTC)[reply]
    Blocked as a sock of Crommorc (talk · contribs), who is apparently a sock of DownTownM (talk · contribs), who is a sock of Seasideplace (talk · contribs), who is a sock of...who? - auburnpilot talk 02:42, 8 September 2008 (UTC)[reply]

    Template:Reflist

    The template is not working properly. The columns options is no longer working. I believe this edit [24] messed up the code. Please fix this a.s.a.p. — Navy  Blue  14:46, 6 September 2008 (UTC)[reply]

    The multi column support for Safari was turned off after extensive discussion, as Safari does not render multiple columns correctly. Please see Template talk:Reflist for more information. DuncanHill (talk) 14:51, 6 September 2008 (UTC)[reply]
    So that it? It's going to stay 1 column? Ok never mind. thanks. — Navy  Blue  14:54, 6 September 2008 (UTC)[reply]
    Until either Safari is updated to stop the links breaking, or someone can design a reflist that works properly (or degrades gracefully in Safari) I hope so. DuncanHill (talk) 14:55, 6 September 2008 (UTC)[reply]
    Bear in mind, it still shows up as two columns on Firefox. It is regrettable that editors using the template from other platforms will be unable to see the precise results of their work. bd2412 T 01:33, 7 September 2008 (UTC)[reply]

    New Meta Logo - Image:Wikimedia_Community_Logo.svg

    Hey can someone update the meta wiki logo on Template:WikipediaSister to [[Image:Wikimedia_Community_Logo.svg]]. Thanks   «l| Ψrom3th3ăn ™|l»  (talk) 15:24, 6 September 2008 (UTC)[reply]

     Done Hersfold (t/a/c) 15:38, 6 September 2008 (UTC)[reply]

    Inappropriate conduct of administrators on Sarah Palin

    Since protection, numerous administrators edited this page without talk page consensus. This of course led to heated discussions, reverts and so on. I had to admonish four administrators until now. I request that other administrators help to take care of this issue. I may report this to the current arbitration case on Sarah Palin. Thanks, Cenarium Talk 16:12, 6 September 2008 (UTC)[reply]

    Wikipedia:Requests for arbitration/Sarah Palin protection wheel war could apply loosely to your claim. Though maybe it doesn't, I havent followed this super closely. Wizardman 16:15, 6 September 2008 (UTC)[reply]
    Cenarium, providing diffs would be helpful to understand what you find objectionable. Ronnotel (talk) 16:18, 6 September 2008 (UTC)[reply]
    I have already submitted possibly incomplete evidence on this to the current case. Please feel free to use my talk if you wish anything to be added to that evidence. 86.44.21.70 (talk) 16:31, 6 September 2008 (UTC)[reply]
    [25], [26], [27], [28] and others more minor or older. Discussion on this happened on the talk page and at Wikipedia:Administrators' noticeboard/Arbitration enforcement#Massive change to Sarah Palin made without consensus. I won't be around until tomorrow. Cenarium Talk 16:33, 6 September 2008 (UTC)[reply]
    This is getting ridiculous. Since the full protection was last reinstated 2 days ago, there's been more than 50 edits. That's about 50 times more than most full protected articles. If this isn't a sign that extended full protection of high-profile current event articles is a bad idea, I don't know what is. Mr.Z-man 16:41, 6 September 2008 (UTC)[reply]
    A few of the cited edits are minor proofing edits, and while probably not a good idea, also not a big deal. People need to step back and calm down--Tznkai (talk) 16:43, 6 September 2008 (UTC)[reply]
    Thanks, Cenarium. Looking at the diffs one by one, 1) i'm not sure about the state of consensus at this time 2) already listed at arbcom case 3) without reading up, my instinct is that rmving blatantly nonconsensual edits is fine, even if it feels a bit disruptive on the talk page when modification of the addition is approaching consensus 4) seems like an honest mistake. Further discussion welcome tomorrow, of course, should you wish it with me. 86.44.21.70 (talk) 16:48, 6 September 2008 (UTC)[reply]

    No, people do not need to calm down, people need to get very very concerned as this sets a very very very very very very bad precedent for wikipedia editing on contentious articles. These admins need to be held accountable for violating Wiki policy, and their admin privileges stripped. LamaLoLeshLa (talk) 16:50, 6 September 2008 (UTC)[reply]

    I've requested the arbs put in a temporary injunction to stop admins from just arbitrarily editing this extremely contentious and hostile protected article here. There's not really any other way to get everyone to calm down besides telling everyone by force to stay hands off that I can see. rootology (C)(T) 16:44, 6 September 2008 (UTC)[reply]

    Shall we start taking bets on when the devs will implement a new protection level? [edit=crat], anyone? Fvasconcellos (t·c) 16:53, 6 September 2008 (UTC)[reply]
    bugzilla:15499. NonvocalScream (talk) 17:02, 6 September 2008 (UTC)[reply]
    OMG!!! Now we can officially kick those pesky habits of self-control and critical reasoning! Fvasconcellos (t·c) 17:10, 6 September 2008 (UTC)[reply]
    • Please note that Kevin chose to revert Bogdangiusca's, but not Moreschi's nonconsensus edits. Bogdangiusca actually put back material Moreschi removed. I would very much like to be informed of how I, a non-admin, can go about requesting sanctions against Moreschi. I feel that when the dust clears, Moreschi's edits will not be viewed favorably even in the context of this fiasco. Phlegm Rooster (talk) 17:21, 6 September 2008 (UTC)[reply]
      • You can propose sanctions or anything else here. D.M.N. (talk) 17:23, 6 September 2008 (UTC)[reply]
        • Moreschi altered her political philosophy to say she was a "classical libertarian" who was endorsing the "minimal state" which is a redirect to Night watchman state. Read what it says at Night watchman state! Moreschi's synthesis is a worse violation of BLP than people recognize. Phlegm Rooster (talk) 20:09, 6 September 2008 (UTC)[reply]
          • If she is indeed a classical libertarian, then she does indeed believe in the Nozickian concept of a night watchman state. Nothing wrong with CM's edit. --Relata refero (disp.) 17:00, 7 September 2008 (UTC)[reply]

    Unprotection requested

    It appears unprotection has now been requested.... D.M.N. (talk) 17:11, 6 September 2008 (UTC)[reply]

    What was the reason for forking my request here? NonvocalScream (talk) 17:18, 6 September 2008 (UTC)[reply]
    To keep others above updated. I noticed you hadn't left a note above saying "I've requested unprotection", so I thought I'd better do it, for clarity. D.M.N. (talk) 17:20, 6 September 2008 (UTC)[reply]
    Yeah, I had not planned on a note here, unprotection requests belong over there. NonvocalScream (talk) 17:21, 6 September 2008 (UTC)[reply]
    I declined the request, as more wheel warring is not the answer. Any admin who unprotects this page will be subject to sanction. - auburnpilot talk 17:27, 6 September 2008 (UTC)[reply]
    I just want to make a point now, that is is not fair that I can't edit, yet the administrators can. What kind of message does that send? That admins are better judges/editors? No self control here. NonvocalScream (talk) 17:29, 6 September 2008 (UTC)[reply]
    I think the point is not to wheel war but rather to build a consensus around whether now is a good time to try reducing the protection level. During the initial AE, today was suggested as a target date and a number of people agreed with that. Given the current state of affairs, it might still be too early to unprotect, but since we need to do it eventually, it is worth discussing what the right time is. What the right forum for that discussion is, I'm not sure, but I think it is premature to say that unprotection is not an option. Dragons flight (talk) 17:34, 6 September 2008 (UTC)[reply]
    I think it should be unprotected, as it is profoundly unfair that only admins are allowed to make complete and utter fools of themselves on that article. We are getting a very limited view of the lack of responsibility of Wikipedians, and the impossibility of achieving consensus by restricting editing to trusted and respectable editors. Why not let us untrustworthy and irresponsible ones see if we can do an even worse job? I know the bar has been set to a very high level, but I'm sure there must be one or two non-admins up to the challenge. DuncanHill (talk) 17:59, 6 September 2008 (UTC)[reply]
    *lol* I laughed, at least :-) henrik o talk 18:31, 6 September 2008 (UTC)[reply]

    Any and all dicussions on protection or non protection should take place here.--Tznkai (talk) 18:36, 6 September 2008 (UTC) Subscript text[reply]

    Cascading protection?

    Should we set the cascading bit to stop vandalism? ffm 03:24, 7 September 2008 (UTC)[reply]

    Is there a problem going on now? NonvocalScream (talk) 03:43, 7 September 2008 (UTC)[reply]
    No, that would be a preventitive measure. ffm 03:52, 7 September 2008 (UTC)[reply]
    I don't see the need as of now, welcome to explore it later. NonvocalScream (talk) 03:57, 7 September 2008 (UTC)[reply]
    Whoops, looked like it happened. ffm 18:02, 7 September 2008 (UTC)[reply]
    Would anyone object to me semi-protecting all currently unprotected templates transcluded on Sarah Palin? I did this with John McCain and Barack Obama, and no one challenged me, but in light of the current ArbCom case surrounding this article, I would like to get a second opinion before acting. J.delanoygabsadds 18:19, 7 September 2008 (UTC)[reply]
    Well, two more templates got vandalized, so I started semi-protecting. Then Mr. Z-man cascade-protected Sarah Palin. Should I semi-protect the templates anyway so that when the cascade-protection is removed from Palin's page, we're still good? J.delanoygabsadds 18:58, 7 September 2008 (UTC)[reply]

    User:138.251.242.2 Concerns

    First, a quick Google search of 138.251.242.2 shows this is the IP of known spammers [29]. Next, you have personal attacks against other users: [30] ("incredible narcissism") and [31] [32] [33] (false accusation of sock puppetry). Third, you have at least one instance of vandalism: [34]. Soft block at the minimum is probably appropriate. Buspar (talk) 03:39, 7 September 2008 (UTC)[reply]

    protection of User_talk:Peter_Damian

    Jimbo recently banned PD, and his userpage and talk page are currently protected. I think the talk page would be a good location for discussion of issues related to this, and think it would be a good idea to unprotect. I've dropped a note on Jimbo's talk page, and am inviting feedback (and hopefully a small 'unprotect' action :-) ) cheers, Privatemusings (talk) 03:50, 7 September 2008 (UTC)[reply]

    From what I can tell, Damian is not welcome to post. Also, we should not be taunting him by posting to the talk page. If you wish to propose an unblock, do so here. I endorse the talk page protection. Incidentally I've asked Wales to clear up the blocklog. NonvocalScream (talk) 03:54, 7 September 2008 (UTC)[reply]
    discussion with the protecting admin indicates that this may be a jimbo / arbcom decision in some way (hopefully we'll get clarification in due course). I still think it's a good idea to unprotect the talk page. Privatemusings (talk) 04:29, 7 September 2008 (UTC)[reply]
    The user is no longer welcome to commit posts to the wiki. In this way, the talk page can remain protected. NonvocalScream (talk) 04:35, 7 September 2008 (UTC)[reply]
    From WP:BAN: "Unlike editors who have been temporarily blocked, banned users are not permitted to edit their user and user talk pages". - auburnpilot talk 04:37, 7 September 2008 (UTC)[reply]
    Adding to that from Wikipedia:BAN#Decision_to_ban Jimbo Wales retains the authority to ban users., and since Jimbo is our Constitutional Monarch/god-King, I'm really really not seeing the point in trying to push an unban dialogue at this time. MBisanz talk 04:40, 7 September 2008 (UTC)[reply]
    Yes, that is still policy, untill Jimmy abdicates that authority or the community takes it. Which will not happen anytime soon - no need. NonvocalScream (talk) 04:55, 7 September 2008 (UTC)[reply]
    ok, ok! - I see PD's very very banned! :-) I still think it'd be healthy to unprotect, and for reasons beyond an 'unban' discssion, but will think on it a bit more... cheers, Privatemusings (talk) 04:51, 7 September 2008 (UTC)[reply]
    Healthy for who? Certainly not for whoever does the unprotecting. SHEFFIELDSTEELTALK 05:27, 7 September 2008 (UTC)[reply]
    for the wiki of course! :-) (your comment made me smile though - and seems accurate at this point!) - my views on this relate to the thinking that 'we' (the en wiki community) are depressingly good at creating, and sustaining 'enemies' in all sorts of ways that we really don't have to pursue.... that, and the fact that it's almost always good to talk :-) Privatemusings (talk) 06:05, 7 September 2008 (UTC)[reply]

    <- While we're here would someone be kind enough to add him to the list of banned users? Monster Under Your Bed (talk) 06:07, 7 September 2008 (UTC)[reply]

    {{sofixit}} :) NonvocalScream (talk) 06:10, 7 September 2008 (UTC)[reply]

    The community needs to discuss this openly, and it won't do to simply say that Jimbo does what Jimbo wants. We need an explanation about this block, and we need to discuss whether we, as a community, feel it was the appropriate solution. Many people, myself included, admire Peter's article work, and that alone should be enough to cause us to a consider other approaches. Even though Peter left of his own accord immediately before the ban, he might decide to return if this ban wasn't in place; furthermore, to slam the door behind a contributor like this adds insult to injury and denigrates all his work. Everyking (talk) 06:15, 7 September 2008 (UTC)[reply]

    According to him, he scrambled his password. The chances that he will return again as Peter Damian therefore seem low. He's demonstrated in the past that he's capable of registering another username. Maybe what you should seek to clarify is whether he is allowed to do so, and under what circumstances if any. It appears as though its left to ArbCom to determine that, so perhaps RfAr is what you want? Avruch T 06:29, 7 September 2008 (UTC)[reply]
    Could somebody please be so kind to explain (NPOV'ishly?), to an outside sometimes-journalist observer, just what this guy did so as to suffer The Wrath Of Jimbo? Note I'm not taking sides at this moment as to whether the action was right or wrong, only trying to figure it out -- Seth Finkelstein (talk) 06:37, 7 September 2008 (UTC)[reply]
    He had been in a dispute with FT2 on some content matters. And he posted this which there was some off-site speculation may have been an aggravating factor--threatening to go to the Sloan Foundation in regards to their pending donation of funding to the WMF, or something like that. rootology (C)(T) 06:40, 7 September 2008 (UTC)[reply]
    A good guess, but the block log leaves us in the dark: "User says he is leaving. Good timing. Please do not unblock without approval from me and/or ArbCom." Not only does it not give a reason, it's insulting. Everyking (talk) 06:46, 7 September 2008 (UTC)[reply]
    Thanks - is there any evidence other than speculation, that the donation was a factor? The comment also discusses other issues. -- Seth Finkelstein (talk) 06:48, 7 September 2008 (UTC)[reply]
    I was entirely unaware of that comment, and so it was no factor whatsoever.--Jimbo Wales (talk) 11:46, 7 September 2008 (UTC)[reply]
    Beats me. I know Damian had a bee in his bonnet to make the Neurolinguistic programming and pederasty related articles totally compliant with WP:NPOV. Your guess is as good as mine otherwise till Jimmy says whats up, since you know as much as I know. I just know this guy was a far above average content editor. rootology (C)(T) 06:50, 7 September 2008 (UTC)[reply]
    Well, at least in this instance there is no question about Jimbo's ego being involved; he is demonstrating no fear of appearing very uncool. LessHeard vanU (talk) 09:16, 7 September 2008 (UTC)[reply]
    I think what we need most of all is: A) an explanation from Jimbo about why he imposed this ban; and B) community discussion of whether Peter should be allowed to edit in the future if he wishes (under whatever account), and whether this ban was appropriate. Everyking (talk) 06:38, 7 September 2008 (UTC)[reply]
    It is definitely disappointing to see Jimbo making such bans (explicitly invoking godking authority in the block notice) but not even posting any explanation anywhere. That's not something the community should tolerate. Fut.Perf. ☼ 06:54, 7 September 2008 (UTC)[reply]
    I suspect, knowing Jimbo, that he will make some kind of statement when he feels able to phrase it without compromising the privacy and dignity of those involved. Guy (Help!) 07:52, 7 September 2008 (UTC)[reply]
    I'm constantly surprised that people seem to assume there is some sort of God-given right to edit Wikipedia and that the removal of said right is potentially a major outrage. The fact is that we are all here by permission of the management, and if the management - in this case Jimbo - decides to withdraw that permission, they have an absolute right to do so, for any reason. -- ChrisO (talk) 11:17, 7 September 2008 (UTC)[reply]
    Jimbo will explain when he has worked out a reason that he thinks will satisfy just enough people. I have no opinion about Peter Damian, but I do feel that it is time that Jimbo started acting like a constitutional monarch (something he has claimed to be) instead of acting like an autocrat. DuncanHill (talk) 11:24, 7 September 2008 (UTC)[reply]
    DuncanHill, it is one thing to disagree with my decision. It is another thing to claim that I am working out an explanation that will satisfy "just enough people". Please Assume Good Faith, eh?
    Please review the users' block log, history of harassment, and off-site attacks. I am drawing a line here in the very strong hopes that the rest of community will feel supported to follow suit and insist that such behaviors are always unacceptable. When we tolerate people who engage in bad-faith personal attacks and sniping and off-site attacks, we poison the goodwill of the community. We are a simple charitable effort to share knowledge, and as such, we often allow ourselves to be victimized by people who are here more to attack us and sow discontent and drama. Let's all get together and say: enough. It's one thing to say "I don't agree with this decision, can we talk about it?" It is quite another thing to say things like "All hail, chief of security and protector of the community, FT2. The bodies of the guilty and the innocent burn together with that sweet sickly smell of death, in the pit, in the morning." Such behavior is absolutely unacceptable and people who do things like that are, quite simply, not welcome to continue in the community. There is a small group of very vocal users (a few of whom you can find in this very thread, complaining about this ban) who seek to defend every trollish user, no matter how bad, to the point that good admins have at times lost the patience or courage to do what needs to be done. I am here to say: ignore the handful of wikianarchists, and let's keep this community healthy by insisting that people who behave that way are not welcome.--Jimbo Wales (talk) 11:46, 7 September 2008 (UTC)[reply]
    Where did he post that rant you're quoting? Didn't see it anywhere. Fut.Perf. ☼ 11:57, 7 September 2008 (UTC)[reply]
    Where did Jimbo state to be a constitutional monarch? I totally love that idea! Perhaps admins should be renamed 'Lords of the Wiki'! :) --Cameron* 11:59, 7 September 2008 (UTC)[reply]
    He (=Peter Damian) posted that on WR. – Sadalmelik ☎ 12:06, 7 September 2008 (UTC)[reply]
    Yep, see here. - Face 14:28, 7 September 2008 (UTC)[reply]
    Okay, thanks, that does make it appear in a different light. Still, I'll echo DuncanHill's comment below; I'd expect some explanation for such a step to be given without prompting, at the time it was made. Fut.Perf. ☼ 12:10, 7 September 2008 (UTC)[reply]
    Here is one example (of Jimbo using the "constitutional monarch" phrase) from Wikipedia, [35]. DuncanHill (talk) 12:07, 7 September 2008 (UTC)[reply]
    Very recently, there was In the English Wikipedia we have a system of "constitutional monarchy,". Actually, English Wikipedia is more like a barbarian kingship, where the tribal chief occasionally personally puts offenders to death. Constitutional monarchs don't go around dispensing King's Justice. This is not to assert that "Jimbo I" :-) is a bad king, per se. But the system sure isn't one with much check on supreme executive power. -- Seth Finkelstein (talk) 13:29, 7 September 2008 (UTC)[reply]
    That comment is pretty disgusting. If Peter Damian had a less problematic history I guess there might be more of a tendency to forgive or at least try to understand and de-escalate, but his behaviour over the NLP business, over which we assumed good faith, combined with that kind of comment, gives a strong appearance of being here solely to pursue a vendetta - and God knows we have quite enough trouble without that kind of thing. So, for what it's worth and to the surprise I guess of nobody, I support the ban. And yes, I feel rather let down here as well, since I had engaged with peter over the NLP issue and generally supported is attempts to scale that back somewhat. Guy (Help!) 12:21, 7 September 2008 (UTC)[reply]
    Oh bollocks, Jimbo. It was not only quite poetic, but was heartfelt and in line with what his view in how best Wikipedia should be served (that would be Good Faith comment, that it would). Not only that, but he later apologised to FT2 - publicly, in the same forum - for his language. Nor did I see FT2, to his credit, take any offence at the language but rather seek to explain further his position. At that place, at least, there is an ongoing dialogue. For what it is worth, I too have been arguing over there against PD's viewpoint; as ever, I am in the minority and am being refuted - but always politely (within context) and in the expectation of being allowed further dialogue. Perhaps you may wish to join the debate? You certainly are more likely to be allowed to express your opinions there than some, many or most of the correspondents there would be here...
    By the way, "bollocks" is simple British English usage meaning rubbish - not vulgar or derogatory. Ask Guy. LessHeard vanU (talk) 16:55, 7 September 2008 (UTC)[reply]
    Hang on. Which bits are poetic? The WR comment quoted above? For what it is worth, some people may be missing an undertone here. When I read "that sweet sickly smell of death, in the pit, in the morning", I think of bodies in pits, and book-burning, and I think of the Nazis and the Holocaust (where bodies were cremated in open-air pits - I should say here that I'm no expert on the Holocaust and my Googling unfortunately brought up a mixture of Holocaust history site and Holocaust denial sites). Not quite sure where the "in the morning" bit comes from. Now, if some of the people here are reacting that way (interpreting this as Holocaust imagery), they should say this upfront, and not just call it "disgusting" and assume people know why it is possibly more disgusting than using other imagery. Carcharoth (talk) 18:09, 7 September 2008 (UTC)[reply]
    • Thanks for pointing this out. I definitely got the same association reading it. Fut.Perf. ☼ 08:04, 8 September 2008 (UTC)[reply]
    I don't think a healthy community would be in the position of having to ask for explanations of your actions - a healthy community would be one in which explanations of extraordinary actions were seen as routine. Both you and arbcom should be aware by now that unexplained acts of this nature serve only to stir up discontent and make it harder to trust people. If you feel the need to exercise your powers as an autocrat, OK, but at least explain at the time. DuncanHill (talk) 11:59, 7 September 2008 (UTC)[reply]
    I've changed Damian's entry on WP:BANNED to something more descriptive, see here. Cheers, Face 12:19, 7 September 2008 (UTC)[reply]

    Whether Peter Damian was justifiably angry or not, I doubt that somebody who threatens to use his off-wiki influence to prevent donations to WP because it's a place filled with "book burners and hooligans" can be expected to contribute constructively from that point on. justinfr (talk/contribs) 12:36, 7 September 2008 (UTC)[reply]

    Agreed. Very few websites would welcome into their community someone which is actively trying to undermine their funding efforts. But that's not the real issue here, it's more that he has essentially declared himself at war with another contributor, one who is in good standing. We have enough disputes already without people coming back after absences to stir up new ones. Guy (Help!) 13:40, 7 September 2008 (UTC)[reply]
    The comment linked above (see here) was made 8 days (over a week) ago. Why is it only being brought up now? If the block is justified, then those who saw the comment at the time, and did nothing, should be apologising for their inaction. And Guy, people in good standing can both lose and regain that good standing (cf. WP:CCC) and those who come back after blocks shouldn't have that fact alone held against them. It is their actions now that matter. Whether they came back after a break or not is irrelevant. And please, can the article issues be resolved? The important things here is to not ignore valid criticisms (if they are valid) merely because the person who raised the criticisms has been banned. If the criticisms are not justified, can we please have an open and clear response explaining why the criticisms are not valid? And I agree that Jimbo's wording in the block log "User says he is leaving. Good timing." (he went on to say more) is open to many interpretations, not all of which will be charitable. Maybe it would be best if Jimbo clarified what he meant there? Carcharoth (talk) 14:25, 7 September 2008 (UTC)[reply]
    I don't think Jimbo, or anyone else in this thread, has said Peter's criticism of some articles were not valid. Consensus on the deletions has shown that they are. But valid criticism in that instance doesn't excuse behavior beyond the pale in many others, which is I think the point Jimmy is trying to make. And the book burning comment above is from a bit ago, but the comment from Peter on WR further up (bodies burning, all hail chief of security) is from yesterday. Avruch T 16:48, 7 September 2008 (UTC)[reply]
    I have asked Jimmy to unblock and reblock with a clear reason... of course I don't think any admin will be desysopped for unblocking and immediately reblocking indef with a clear reason AND Jimbo's instructions. NonvocalScream (talk) 16:15, 7 September 2008 (UTC)[reply]
    That sounds like process-wonkery to me. Simpler to just wait for this discussion to be archived and then link to the archive from his user page. Guy (Help!) 16:26, 7 September 2008 (UTC)[reply]
    This will be the second time in a week I have been told that I was process wonking, I'm sick of it. Waiting for a discussion to conclude is more wonkery than actually going and doing it, no? Please be more careful in the future, calling someones good intentions "wonkery" is offensive. NonvocalScream (talk) 16:52, 7 September 2008 (UTC)[reply]
    I would add that adding links to a user's page is less useful than the block log. User pages of banned and indefinitely blocked users are routinely deleted. Admins (and this includes Jimbo) really must give reasons in the block logs and deletion logs for their actions. Failing to do so makes it harder for people to carry out independent reviews now or later. Carcharoth (talk) 17:05, 7 September 2008 (UTC)[reply]

    To Jimbo Wales: (previous three words added by comment mover) Well, thank you for the response ... But ... THAT WAS IT??? That's a key reason you cite? The 265th post, on a site which often has a large amount of ranting and raving in discussion threads (sorry WR'ers, it's true), significantly moves Jimmy Wales, (co)Founder of Wikipedia, President of $70 million valuation Wikia Inc., to personally ban the supposed miscreant? i.e., a trivial flame-war, which the guy says he's apologized for. I'm not sure which is worse - if that's a real reason, or if it's a poor excuse for a poor excuse (tedious point - this sentence is an attempted humorous commentary on logical possibilities, not an accusation). And before you call me a troll, I'll note I've repeatedly said Wikipedia group dynamics fascinates me, and in fairness you should see why from such a perspective this is simply amazing. Look, I know we often disagree, but take this in good faith - what you're doing comes across as because-I-can, just plain random craziness against some unfortunate minor offender who happens to be in the wrong place at the wrong time when the Godking is in a churlish mood. -- Seth Finkelstein (talk) 14:55, 7 September 2008 (UTC)[reply]

    You've got that completely backwards. If the victim of Damian's attacks had been a plain ordinary user, he would have been booted out of here long ago for sheer nastiness. I would have done it without a second thought, were I a simply an admin; I might nor might not have bothered to post on ANI about it. But because it was FT2, a fellow arbitrator (and of course a rather controversial one at times), I knew that if I had blocked or banned Peter, the masses would have yelled "abuse of power", "cronyism", "bullying", and so on. It was hardly one post that caused the banning; it was a long crescendo of ugliness. But FT2 didn't ban him, and neither did I, and I know a number of admins also demurred, which is why we asked Jimbo to take a look. Does the community feel we should have acted without waiting for Jimbo? Next time, because of what Jimbo has said here, I know I'll be less tolerant of continuing vile attacks here or elsewhere. --jpgordon∇∆∇∆ 17:31, 7 September 2008 (UTC)[reply]
    "We asked Jimbo to take a look" - are you saying that the Arbcom requested Jimbo to look at the editor and do what he thought fit? DuncanHill (talk) 17:44, 7 September 2008 (UTC)[reply]
    No. FT2 did, and then I did a while later. It was not in any way an official ArbCom request; I don't know what FT2 said, but I said "please take a look at FT2's request" when Jimbo took a little while getting around to it and FT2 mentioned it to me. --jpgordon∇∆∇∆ 18:16, 7 September 2008 (UTC)[reply]
    Thanks for the clarification. DuncanHill (talk) 18:19, 7 September 2008 (UTC)[reply]

    How we treat long time editors - make the effort to inform the community

    Jimbo's block may have been perfectly reasonable - but an uninvolved admin would have no way of knowing without spending a lot of time hunting through links and diffs. Peter Damian worked on this project for over five years - he create a lot of quality content. Jimbo, you owe him and the community better. If you want to ban him, take a few minutes and explain to the community why. Have the courtesy to use an accurate and informative block summary. Make the effort to start a note at WP:AN. Don't conduct court behind closed doors. Don't sit around and wait for people to ask. Is this too much to expect of you? Your actions here are nothing short of slovenly. Really, it's not like we're expecting you to break a sweat or anything. --Duk 17:50, 7 September 2008 (UTC)[reply]

    Not only is Jimbo citing personal attacks that occurred on a different website, but Peter subsequently acknowledged that his attacks were excessive, apologized, and even had some kind things to say about FT2's work. I strongly agree with Duk above—long-term, hard-working editors are particularly entitled to fair, reasonable and polite treatment, and this is nothing of the sort; furthermore, the community is entitled to explanations (at the very least) when such bans are handed down. I also think it reflects very poorly on Jimbo that he cannot give his explanation without insulting other people discussing the matter: "a small group of very vocal users (a few of whom you can find in this very thread, complaining about this ban) who seek to defend every trollish user, no matter how bad, to the point that good admins have at times lost the patience or courage to do what needs to be done. I am here to say: ignore the handful of wikianarchists..." This kind of thing seems unfitting for a "constitutional monarch". Everyking (talk) 18:02, 7 September 2008 (UTC)[reply]

    "Long-term, hard-working editors are particularly entitled to fair, reasonable and polite treatment..." Yes, that is exactly right. A good summary of why people believe Peter should be banned. Avruch T 18:17, 7 September 2008 (UTC)[reply]
    Very good point, Everyking, about the "complainers". To be clear, I'm not complain about this ban. I'm complaining about an hour of my life wasted hunting through logs and diffs and histories, all because Jimbo is too lazy to write a note. I wonder how many other administrators wasted their time doing this too. And what about other long time editors who may have respected Peter, only to see him banned without explanation - what do you think the effect on morale will be? --Duk 18:19, 7 September 2008 (UTC)[reply]
    An hour of your life wasted? Well, Damian's block log has quite some info. One log entry contains this diff, and another one reads: "Last chance at WP, no more harassment or disruption will be tolerated". - Face 18:40, 7 September 2008 (UTC)[reply]
    Damian's block log has quite some info. Ya, too bad the log itself notes that it isn't trustworthy.--Duk 18:54, 7 September 2008 (UTC)[reply]
    I must admit that Jimbo's comment there might have, um, discouraged people from participating in this thread! Devil's advocate is a better term than wikianarchist, I think. But I get Jimbo's point. He doesn't want to stop people disagreeing with him (far from it), but he wants discussion to be logical and centred on the specifics of this case, not merely principled opposition. I think if people concentrated on what happened here with regards to Peter Damian, and thrashed out some agreement, then Jimbo might listen to that. Carcharoth (talk) 18:19, 7 September 2008 (UTC)[reply]
    I must be misreading you here because you seem to state that principles have no place on Wikipedia. Hiding T 19:55, 7 September 2008 (UTC)[reply]

    It would be nice, I think, for Jimbo to acknowledge that Damian has made some valuable contributions to the project. It's wrong to suggest that he was just here to troll. He's made hundreds of valuable mainspace edits. Zagalejo^^^ 19:07, 7 September 2008 (UTC)[reply]

    I found this discussion through WR some minutes after wondering why he was banned. WR is pretty nice for determining why someone was banned when the block log and user and talk pages don't say. --NE2 19:35, 7 September 2008 (UTC)[reply]

    • This is not what a constitutional monarch does, Jimbo. Seth is right about this being more "barbarian king" behaviour. Secondly, although Damian had clearly lost his mind as regards FT2, this does not necessarily mean he was incapable of being constructive elsewhere, so long as he is kept away from FT2. As to what he posts on WR...well, who cares? That site has no credence except that which we lend it. Bless their little hearts, all the people I block can rant and rave about me all they like over there. I don't care, that damages nobody except them. They just wind up looking small. Unless Damian had been involved in "outing", this may be excessive. Moreschi (talk) 19:55, 7 September 2008 (UTC)[reply]
    I'm fascinated by the quasi-official status WR is coming to have here. Should we just fold it into project space, make their admins sysops here, and give them two or three seats on the arbcom? Or would it be better to just redirect ANI to their site? Tom Harrison Talk 20:19, 7 September 2008 (UTC)[reply]
    I think a link on PD's user page to the WR thread would suffice. --Duk 22:00, 7 September 2008 (UTC)[reply]

    In line with Carcharoth's suggestion above, I will make a simple outline of what happened as it appears to me:

    1) Personal dispute between Peter and FT2, on both WP and WR, culminating in Peter comparing FT2 to a secret police chief on WR
    2) Peter's comments are widely deemed excessive and out of place by others on WR, and Peter apologizes, going so far as to commend FT2's work on a sockpuppet investigation
    3) Peter leaves WP due to this dispute with FT2 (may have occurred before point 2?)
    4) Jimbo bans Peter without explanation
    5) Jimbo says he banned Peter because of Peter's comments toward FT2 on WR, without noting the subsequent apology.

    Is there agreement on those facts? Everyking (talk) 04:01, 8 September 2008 (UTC)[reply]

    That seems like an oversimplification of the facts. The idea of Jimbo Wales as "god-king" seems more appealing than these endless discussions. Also, one of the endemic problems with Wikipedia is a "do as I say, not as I do" mentality that it's OK for certain long-time users/admins/contributors to use foul/excessive language or engage in their own tribal barbarism. We often see newbies blocked all too quickly, while the admins protect each other's bad behavior (like the "Blue line" in policing). Jimbo's blocking of Peter Damian suggests that no one is immune and after being given seven chances at reform, the 8th was a ban. Yet it may not be a permanent ban, just an "example" ban, to attempt to get others into line.

    Ryoung122 05:46, 8 September 2008 (UTC)[reply]

    You're against double standards, then—but isn't it a double standard if Jimbo is allowed to ban someone for an off-site insult (which was followed by an apology!), when no other admin would be able to make a block on those grounds? Furthermore, isn't it a double standard if Jimbo can ban a long-standing contributor without explanation? And anyway, if my outline is inadequate, please suggest changes. Everyking (talk) 06:25, 8 September 2008 (UTC)[reply]
    Over-simplification, Everyking. 9 month almost non-stop history of this on-wiki and off, block logs on 3-4 accounts for the same thing, recent posts about "this means war", recent comparison to the holocaust, recent and past threats, significant gaming of AGF (enough to get unblocked each time, and then almost immediately resume), repeated warnings to stop by many different admins. (And the compliments cited actually came only 6 hours after being compared yet again to Stalin's First Murderer.) FT2 (Talk | email) 11:15, 8 September 2008 (UTC)[reply]

    For what it is worth, the user in question has indicated elsewhere that he is not requesting an unblock. In the interests of allowing some breathing space for everyone, I suggest that this moots much of the discussion here on the merits of the block, particularly as the user in question is not able to comment on-wiki on the matter.

    He has also pointed out a related issue, which is that a prior block placed when his account was registered under his real name, became something "that colleagues could see," presumably referring to a search engine result. It is questionable whether userspace should appear in searches at all (compare generally, Wikipedia talk:NOINDEX of noticeboards), but it is submitted that in any case, a "NOINDEX" key should immediately be placed in the various indefblock templates, as there is certainly no need for these to be searchable and if anything, this complicates the ability for a banned user to walk away from Wikipedia as well as potentially creating real-world complications for the user. Newyorkbrad (talk) 12:48, 8 September 2008 (UTC)[reply]

    Has been since July 30th, [36] MBisanz talk 12:51, 8 September 2008 (UTC)[reply]
    Thank you. Good change (not sure if it's been made in all of the affected templates, though). Newyorkbrad (talk) 12:54, 8 September 2008 (UTC)[reply]
    Fairly certain Krimpet hit all the templates, it's used on 30,000+ 46,000+ pages at this point, so it would need to be a very obscure and almost never used template to not have been covered. MBisanz talk 12:56, 8 September 2008 (UTC)[reply]

    problems with an archive bot

    Re: MiszaBot III

    To a helpful administrator who has time to help: I think that the bot at the top of my talk page has stopped archiving my talk page as it is coded to do; perhaps there is a problem in the code. Also, I cannot see the names of my archive pages in the archive box in "show preview" mode; if I want to have chronology in the names and to have a chronological archiving bot, I don't know how to do that either. I did contact an administrator who seems familiar w/ such a bot, but have had no response to the request for assistance yet. Perhaps another admin. could take look at the code in "show preview" mode in my current talk page, and see what the trouble might be (if there is one). It is set to archive after 2 days48 hours and after 2 time-stamped signatures, but I don't think it's doing that anymore. I like the way the archive box shows up, but I can't see the names in the archive pages there, only numbers. Is there any way to include chronologies in archive pages 1 to 22 and to have automatic chronology set for the future (23 on) with a different bot? Thank you if you can assist. --NYScholar (talk) 05:29, 7 September 2008 (UTC)[reply]

    Wrong place for this. Try the Bot's talk page or the IRC channel.--Tznkai (talk) 06:19, 7 September 2008 (UTC)[reply]

    Category:Mertozoro

    This is a category for a users subpages. It seems a bit unusual but I really couldn't recall there being anything saying you can't do that. Any opinions? CambridgeBayWeather Have a gorilla 06:50, 7 September 2008 (UTC)[reply]

    As far as I remember, not, but I do not see any reason for such category, with this page existing (and the links already on his/her userpage). I'd say you ask the user to convert the category to a sub-page list and if he/she refuses, to take it to WP:UCFD. SoWhy 09:52, 7 September 2008 (UTC)[reply]

    Gorby2 / 87.251.111.207

    I'm not sure what's going on here. Massive (massive) re-cats of chemical articles with no edit summaries by the anon user, and some similar behaviour by the named user. It seems fishy, and SpyMagician agrees, but we're not sure where to put this. Prince of Canada t | c 06:56, 7 September 2008 (UTC)[reply]

    I'd like to backup this assertion. It's baffling and seems robot assisted. All from one IP address and all in one category of articles. What to do? --SpyMagician (talk) 06:58, 7 September 2008 (UTC)[reply]
    Additionally, the user Gorby2 has now come clean and outlined what he did and explanation why, but does not cite who/what/why he decided to do a massive bot-assisted change to Wikipedia without going through proper channels for a structural change of this level. --SpyMagician (talk) 07:16, 7 September 2008 (UTC)[reply]

    European National Front#Program

    Am I missing something here? 78.149.130.209 (talk) 09:59, 7 September 2008 (UTC)[reply]

    Apparently some fan/member of that party added it to the article to promote the organisation. I have removed the section completely as POV and will watch this page for changes. SoWhy 10:43, 7 September 2008 (UTC)[reply]

    Deletion skirmishes over Kashmir

    Right now, there's so much irregularities going on at Wikipedia:Articles for deletion/Pakistan occupied Kashmir that I want to bring this discussion to the general attention of the administrators. I am not going to provide any examples as interested admins may inform themselves by looking at this page (and its history). __meco (talk) 10:35, 7 September 2008 (UTC)[reply]

    I (who myself is an active party in the debate) would say that there are problems on two fronts. On one hand Nangparbat (talk · contribs), who represents a pro-Pakistani POV in the debate, is constantly disrupting the discussion through various IP number edits. On the other hand, there are canvassing and sockpuppeting cases amongst pro-Indian POV editors. My suggestion is that a the AfD be semiprotected to weed out Nangparbat and the socks from the discussion. --Soman (talk) 10:46, 7 September 2008 (UTC)[reply]
    User:kashmircloud has already been blocked for sockpuppetry and canvassing. Pakistan occupied Kashmir is a PoV fork of Pakistan-administered Kashmir. Wikipedia:Articles for deletion/Pakistan occupied Kashmir has been heavily votestacked towards a keep, but as a content fork the article should either be deleted or merged. Gwen Gale (talk) 11:00, 7 September 2008 (UTC)[reply]
    I'll keep an eye on it. Thanks for the heads-up. -- ChrisO (talk) 11:18, 7 September 2008 (UTC)[reply]
    I support Soman. What we need are constructive inputs and it's being hampered by Pro-Indian and Pro-Pakistani elements. Please semi-protect. Thanks.  S3000  ☎ 12:00, 7 September 2008 (UTC)[reply]
    No protection necessary, the socks are transparent. It may have been votestacked, but there does appeear to be a legitimate difference between Pakistan-administered Kashmir and Pakistan-occupied Kashmir, the latter consisting of five territories while the former consists of only two. They both seem to have sources, perhaps the solution is to attempt to gut both articles to get rid of POV? GlassCobra 17:19, 7 September 2008 (UTC)[reply]
    But the constant disruptions of the dynamic IP user makes the whole debate extremly difficult to read in a sensible way. Nangparbat (the dynamic anon IP user) constantly issues uncivil comments, and many other participants in the AfD are quick to respond. Thus the core issues of the AfD gets sidelined in the discussion. --Soman (talk) 21:58, 7 September 2008 (UTC)[reply]
    This is an interesting aspect, and I wonder if any administrators who have experience in such cases can outline how they deal with discussions that are so entangled that it's almost impossible to attain a clear impression of what is significant and what are elaborate distractions. __meco (talk) 08:43, 8 September 2008 (UTC)[reply]

    Improper protection of a PRODed article

    Resolved
     – semi protection had nothing to do with PROD removal;the contesting of the prod by the anon had been accepted - the article is at AfD. עוד מישהו Od Mishehu 06:48, 8 September 2008 (UTC)[reply]

    The article Semih Aydilek is currently up for PROD. After an anon had repeatedly removed the PROD tag, including once with the summary "please keep" (contesting the deletion), Daniel Case protected the article with a summary which clearly indicates his awareness of the anon removing the PROD tag. As it seems from WP:PROD that anons are allowed to contest PRODs, and this anon was clearly trying to do so, I think the page should be unprotected, and the PROD tag removed as a contested PROD. עוד מישהו Od Mishehu 11:12, 7 September 2008 (UTC)[reply]

    WP:PROD indicates clearly, that removing the PROD-tag needs to be done with a statement, as to why the PROD is contested. As the PROD will go on until Sept. 11, you should notify the IP of that and once he/she explained the reasoning, the PROD tag may be removed and the article unprotected. Just removing tags is considered vandalism and may lead to protection of articles. I would suggest though that if you disagree with the PROD, that you open a AfD-discussion to determine the fate of the article. Regards SoWhy 11:20, 7 September 2008 (UTC)[reply]
    WP:PROD does not require a reason to be given, nor does the instructions on the tag itself. WP:PROD says you should leave a reason and the tag says that "it helps." WP:PROD also says: "If anyone, including the article's creator, removes a {{prod}} tag from an article for any reason, do not put it back, except when the removal is clearly not an objection to deletion (such as blanking the entire article)." That's obviously not the case here. Not should the PROD tag not have been re-added, but semi-protecting the page to force the anon out of a content dispute is a blatant violation of the protection policy. What the hell happened to WP:BITE? Mr.Z-man 15:39, 7 September 2008 (UTC)[reply]
    Completely agree with Z-man. The contested PROD should be taken to AfD. GlassCobra 17:16, 7 September 2008 (UTC)[reply]
    I protected the article, along with some others, because the anon who had already been blocked and whose unblock I denied, had already threatened to use a different IP. As we usually do in such cases, I protected the pages he had been targeting as well as extending the block.

    Yes, the contested prod should go to AfD, but I was giving the original tagger the opportunity to do so as it's really his nom to make. Since he has not done so, I will. Daniel Case (talk) 18:01, 7 September 2008 (UTC)[reply]

    It appears it is now on AfD. Daniel Case (talk) 18:05, 7 September 2008 (UTC)[reply]

    Why was he blocked? This was definitely vandalism, but he stopped after that, and tried to improve Semih Aydilek in a noobish way. For that, he was reverted by a bot. --NE2 07:06, 8 September 2008 (UTC)[reply]

    Fuller response with relevant diffs

    I did not protect the page for any reason connected to the PROD.

    • So, as we usually do in such circumstances, I decided to protect the pages he had been editing disruptively, rather than leave some other admin the headache of possibly having to rangeblock. There were three, of which Semih Aydilek was one. The possible deletion of the article was not an issue to me; the PROD tagger is supposed to start the AFD if the tag is removed, instead of just reverting it back. In addition, I do not believe from his edits above that he would have participated in an AfD. Therefore, the protections were an overall response to his disruptive editing and threats, not an attempt to gain an advantage in a content dispute in which I was not a participant at the time. Daniel Case (talk) 19:59, 7 September 2008 (UTC)[reply]

    RBAG Spam

    Per WP:BOT

    Chris is currently being considered for BAG membership. To view the discussion and voice your opinion, please visit Wikipedia:Bot Approvals Group/nominations/Chris G.

    --Chris 12:42, 7 September 2008 (UTC)[reply]

    IP harassment

    User:Christianthelion/90.201.182.141 is leaving me rude messages on my talk page and now doing the same to degenerate discussion. I translated the first one using google language tools. Wasn't kind. I'm sure the rest aren't either. I've attempted to entract him into a civil discussion for many days but it simply keeps coming down to personal attacks and now its just getting bizarre.Yeago (talk) 16:06, 7 September 2008 (UTC)[reply]

    ....Hello.... I am in the wrong place?Yeago (talk) 22:58, 7 September 2008 (UTC)[reply]

    Sceptre block evasion

    Per a private request, I ran a CheckUser enquiry into the edits of Z388 (talk · contribs) and a possible relationship to Sceptre. This relationship is  Confirmed. I do not have any doubt at all about the link between the two. The check also revealed that the following accounts are also sockpuppets of Sceptre:

    I have blocked all of these as abusive sockpuppets -- although there does not appear to be anything wrong with their edits in themselves, this is block evasion.

    Moreschi recently changed Sceptre's indefinite block to one of two months' duration (block log) as a "final chance". Given the above findings, this probably needs reconsideration.

    Sam Korn (smoddy) 16:11, 7 September 2008 (UTC)[reply]

    So in effect, Sceptre is basically banned, not just blocked? how do you turn this on 16:13, 7 September 2008 (UTC)[reply]
    If it wasn't considered a community ban, it probably should be. The block should go back to indefinite IMHO. —Wknight94 (talk) 16:15, 7 September 2008 (UTC)[reply]
    I'm moving it back to an indefinite ban. Evading blocks and bans is a no-no.--Tznkai (talk) 16:17, 7 September 2008 (UTC)[reply]
    May I ask: what is the difference between a block and a ban? how do you turn this on 16:20, 7 September 2008 (UTC)[reply]
    A block is directed against an account, a ban against the person. A block is a purely technical matter, a ban is a somewhat esoteric social construct (which is enforced e.g. through blocks). See Wikipedia:Banning policy. user:Everyme 16:27, 7 September 2008 (UTC)[reply]
    Ermm No, a block is against the person also, it would be pretty pointless otherwise. You've been disruptive so we'll block this account, feel free to continue with another account... See WP:EVADE your definition of being against the account would make this pointless as it would be impossible to evade a block just directed against an account. --82.7.39.174 (talk) 16:42, 7 September 2008 (UTC)[reply]
    So basically there's no difference? how do you turn this on 16:46, 7 September 2008 (UTC)[reply]
    The ban is the social construct, blocks one mechanism for enforcement of a ban (though blocks will be used other than for ban enforcement), see WP:BAN. --82.7.39.174 (talk) 16:50, 7 September 2008 (UTC)[reply]
    So if you evade a block, you get punished for the same reason as evading a ban? They sound basically the same to me, except a block is the technical part of it and the ban is the part that says that person can't edit. how do you turn this on 16:52, 7 September 2008 (UTC)[reply]

    Shouldn't the accounts be tagged accordingly? user:Everyme 16:22, 7 September 2008 (UTC)[reply]

    • Personally, I'd be inclined to simply reset the clock. Scepte is an annoying immature individual but they do make good edits when they have a mind. Indef and permaban seems a little kneejerk right now but given our history I'm not going to fight in the trenches for him. Spartaz Humbug! 16:27, 7 September 2008 (UTC)[reply]
    Agreed. Kittybrewster ☎ 16:29, 7 September 2008 (UTC)[reply]
    Sceptre was on an indefinite ban for harrasment, so resetting the clock brings us back there, but I am unfamiliar with the details. Also, an administrator who understands the autoblocker will want to review the block.--Tznkai (talk) 16:32, 7 September 2008 (UTC)[reply]
    At least one of those "harassed" (I would have called it childish name-calling, myself) put it down to childish behaviour and asked for an unblock. Something those who were here for the original discussions might remember. The block log entries rarely tell the whole story. Carcharoth (talk) 17:11, 7 September 2008 (UTC)[reply]

    For the record, I endorse the stated relationships (among Sceptre, Z388, TUATW, and Gridlocked Caravans) as  Confirmed, I ran checks myself. At the very least I think a reset to restart the 2 month clock is justified. I leave the rest to the community's discretion, for now. Oh, and thanks again to Risker for some spadework in this matter, and to the WR poster who first spotted the possible connection. ++Lar: t/c 16:39, 7 September 2008 (UTC)[reply]

    Can someone clarify what "stated relationships" means, and what the checkuser confirms, for those of us who have never filed a RFCU and have no idea what that entails? Der Wohltemperierte Fuchs (talk) 16:48, 7 September 2008 (UTC)[reply]
    Sam said the other accounts were "sockpuppets of Sceptre". That's the stated relationship. I ran similar checks to what Sam ran, and my interpretation of the results is that they indeed confirm the relationship Sam stated. (i.e. that Sceptre was the controlling account). I hope that clarifies matters. ++Lar: t/c 16:51, 7 September 2008 (UTC)[reply]
    Not really. I'm talking more about the technical details- how the stated relationship was established, what the evidence was. Der Wohltemperierte Fuchs (talk) 16:59, 7 September 2008 (UTC)[reply]
    I would have thought that you already knew that a checkuser isn't going to tell you that. Spartaz Humbug! 17:03, 7 September 2008 (UTC)[reply]
    Correct. I'm surprised that a user who has been around as long as David has would even ask, actually. ++Lar: t/c 17:07, 7 September 2008 (UTC)[reply]
    I guess I just haven't been in many drama-fests in my time. So how are these socks proven then? Der Wohltemperierte Fuchs (talk) 17:12, 7 September 2008 (UTC)[reply]
    Er, that's the same question. There are a number of ways of telling, but a CU isn't going to tell you which one was used in this case. Black Kite 17:17, 7 September 2008 (UTC)[reply]
    Augh! (head hurts) I must not be making myself clear... what exactly does the checkuser action spit out and how do we determine the likelihood of socks based on it? Der Wohltemperierte Fuchs (talk) 17:21, 7 September 2008 (UTC)[reply]
    Basically? Checkuser can reveal IP range similarities and suspicious timing. That combined with shared interest, tone, and other suspicious activity can reveal a series of logins to be the same person.--Tznkai (talk) 17:23, 7 September 2008 (UTC)[reply]
    There is other technical information that CU can pick up as well. Black Kite 17:31, 7 September 2008 (UTC)[reply]
    • Comment - I support resetting the block to 2 months. Sometimes long-time contributors who end up with a block like this don't have the patience to sit it out. A few resets should be used to get the message home before moving to indefinite. And with respect to User:Tznkai (who I am not familiar with), they have recently returned from a two-and-a-half year hiatus. An edit on 8 February 2006 was followed by an edit on 4 September 2008. I can see from User talk:Tznkai that Tznkai has recently been reaccepted as an ArbCom Clerk, but I would reiterate what has been said elsewhere: it is best to ease back in gently. At the very least, reading the threads around the Sceptre block should be done, and not just going by what is stated in the block logs. For the record, Tznkai has said "I am unfamiliar with the details". Carcharoth (talk) 16:52, 7 September 2008 (UTC)[reply]
    I would also support a reset. Sceptre is a valuable content contributor, and I think this block may just have been a clear note to him to shape up. The socks' contribs were not abusive, as has been pointed out. GlassCobra 17:14, 7 September 2008 (UTC)[reply]

    I definitely support an indef block now. It's pretty clear cut that his final chance is gone, no need to AGF anymore. Wizardman 17:01, 7 September 2008 (UTC)[reply]

    Quick note: it turns out the relationship between two of them is obvious. I've also blocked sleeper sock Paracetamoxyfrusebendroneomycin (talk · contribs). —Wknight94 (talk) 16:58, 7 September 2008 (UTC)[reply]

    And you'll notice that these socks are not new. Sceptre has been dropping sleeper socks for quite some time now... —Wknight94 (talk) 17:02, 7 September 2008 (UTC)[reply]
    In his favour, there is no evidence that he was editing abusively and I see nothing from Moreschi to Sceptre saying this was a final chance. Kittybrewster ☎ 17:07, 7 September 2008 (UTC)[reply]
    Moreschi's entry in the block log says "final chance". I'm hoping Moreschi also left a note on Sceptre's talk page, as not everyone reads block logs for messages like that. Carcharoth (talk) 17:14, 7 September 2008 (UTC)[reply]
    He didn't. Kittybrewster ☎ 17:22, 7 September 2008 (UTC)[reply]
    Hmm. That's not good, is it? Setting up sleeper socks, while still in good standing, for later use? That is troubling. But I'd still give him a few resets. At the very least, this thread might shock him into realising that if he continues this way, he is very close to a ban. Carcharoth (talk) 17:11, 7 September 2008 (UTC)[reply]
    Meh, I oppose a reset. Sceptre knew what he was doing, I'm tired of giving people chance after chance when they blatantly take advantage of it. Wizardman 17:16, 7 September 2008 (UTC)[reply]
    I have no objections to anyone changing my block action, but I will note that block evasion to me justifies not only reset, but escalation to the next interval.--Tznkai (talk) 17:18, 7 September 2008 (UTC)[reply]
    We should give him a second chance now so that we can give him a second chance later (not really). —Wknight94 (talk) 17:19, 7 September 2008 (UTC)[reply]
    What if, in three months, Sceptre turned up all apologetic, saying he has stopped using sockpuppets, promising not to use sockpuppets again, and asking for an unblock? That is probably what the two-month block was meant to do. People who use sockpuppets to make constructive edits are more likely unable to disengage, rather than abusive. Setting up multiple sockpuppets is more worrying, but it was done so naively I'm almost tempted to say people should look further and see whether this is a smokescreen for something else? Carcharoth (talk) 17:25, 7 September 2008 (UTC)[reply]
    Like what? naerii 17:39, 7 September 2008 (UTC)[reply]
    I wouldn't like to speculate. I would hope that the checkusers have picked everything up. Carcharoth (talk) 17:43, 7 September 2008 (UTC)[reply]
    Just out of curiosity, what should be made of this? An at least one of these points to this redlinked cat.
    I did a quick look at the live links where they exist, and they, by and large, look unrelated to this, but... - J Greb (talk) 17:53, 7 September 2008 (UTC)[reply]
    I think Sceptre has been working at WP:ACC. The accounts created in May and earlier are likely his, though. – Sadalmelik ☎ 18:07, 7 September 2008 (UTC)[reply]

    Suggestion

    I am actually quite opposed to a reset as well, but as a compromise - reset now, and make it clear that any more block-evasion will result in an indef. Fair? Black Kite 17:20, 7 September 2008 (UTC)[reply]

    how about resetting to three months with further evasion leading to indefnite? Carcharoth (talk) 17:25, 7 September 2008 (UTC)[reply]
    I'd be fine with that as well. Black Kite 17:30, 7 September 2008 (UTC)[reply]
    I support this. naerii 17:33, 7 September 2008 (UTC)[reply]
    Yep, 3 months is ok. PhilKnight (talk) 17:35, 7 September 2008 (UTC)[reply]
    See also this post and replies to it. WR is not a substitute for WP dispute resolution (nor should we negotiate or whatever there) but the information may be useful. I think someone should undo the redirect of his talk -> user so any conversation that Sceptre chooses to initiate there could flow unimpededly. ++Lar: t/c 17:41, 7 September 2008 (UTC)[reply]
     Done [37] NonvocalScream (talk) 17:51, 7 September 2008 (UTC)[reply]
    Questions: where is the best place to leave the message that this really is the final chance? It should be put in the block log for future admins to see. It should also be placed at User talk:Sceptre (which as Lar says should be un-redirected). Is his e-mail address still enabled? To what lengths should people go to ensure that the message has got across? Carcharoth (talk) 17:42, 7 September 2008 (UTC)[reply]
    I've been chatting with him, I can relay the "ultimatum" if necessary. Der Wohltemperierte Fuchs (talk) 17:46, 7 September 2008 (UTC)[reply]
    He says he already knows. —Wknight94 (talk) 17:51, 7 September 2008 (UTC)[reply]
    WR shouldn't be used instead of talk pages, either. Some on-wiki statement from him (on his talk page) would be nice, but unlikely I suppose. Anyway, let's leave this to develop a bit more and see what consensus emerges. Carcharoth (talk) 17:52, 7 September 2008 (UTC)[reply]
    I think spectre should be brought into this conversation, on wiki. I personally refuse to take care of administrative business on an off site forum--Tznkai (talk) 17:54, 7 September 2008 (UTC)[reply]
    I agree. I'm willing to dialog with people but will make no official representations of how I will or won't act, nor will I claim any sort of agreement has any standing. Here is where we do our own business. Not on WR, not on IRC, not on sekrit mailing lists. ++Lar: t/c 18:13, 7 September 2008 (UTC)[reply]
    I'm probably going to pulled into real life at any moment, so I'm going to go on record with something so there is no confusion. I am endorsing a reversal of my block of Sceptre by any administrator (upon some decision being reached).--Tznkai (talk) 18:25, 7 September 2008 (UTC)[reply]
    I agree that going to a block of three months, with the explicit warning that this will be his last chance, is the best idea. He has made positive contributions, which I think could continue to do if he were so inclined. Hopefully three months distance from the project will help him regain the perspective necessary to edit in a more constantly productive way.   user:j    (aka justen)   17:55, 7 September 2008 (UTC)[reply]
    He has stated in email correspondence that he is amenable to three months as the upper limit. Der Wohltemperierte Fuchs (talk) 17:56, 7 September 2008 (UTC)[reply]
    Perhaps you could relay to him that he doesn't get to "be amenable" to anything. That sounds very much like "anything more than three months and I'll start socking again". Black Kite 18:01, 7 September 2008 (UTC)[reply]
    Amenable may have been David's choice of words, who knows. user:Everyme 18:04, 7 September 2008 (UTC)[reply]
    • For the record, I still believe that the initial ban for those "harassing" edits was totally overblown in the first place. user:Everyme 18:02, 7 September 2008 (UTC)[reply]

    I've a problem with Sceptre's user page being deleted. Is he invoking WP:RTV or something? Since when do blocked puppeteers get to request that their user pages be deleted? —Wknight94 (talk) 18:10, 7 September 2008 (UTC)[reply]

    I don't really agree with that, either. I've long held that userpage and user talk deletions, as opposed to courtesy blankings, should be reserved for RTV situations. David, would you consider reversing your deletion and restoring the history? — Satori Son 19:07, 7 September 2008 (UTC)[reply]
    I have more of a problem with Sceptre calling User:Kmweber a stalker. See his talk page (transcluded below). But I'm going to be charitable and put that down to residual anger. I would hope that, three months down the line, Sceptre might not do that sort of thing, or, if he has genuine concerns, to learn the right way to state them. Carcharoth (talk) 18:34, 7 September 2008 (UTC)[reply]
    • I support the extension to 3 months. I would also strongly encourage offering Sceptre a one-time-only no-penalty opportunity to provide the names of any other alternate accounts to one of the checkusers involved in this case, either Sam Korn or Lar, with the understanding that any further use of alternate accounts at any time in the future will result in immediate indefinite blocking. Risker (talk) 18:36, 7 September 2008 (UTC)[reply]

    BTW, if you're waiting for an apology from Sceptre, don't hold your breath. He's too busy calling me an idiot. —Wknight94 (talk) 19:10, 7 September 2008 (UTC)[reply]

    Just ignore it.--Tznkai (talk) 19:43, 7 September 2008 (UTC)[reply]

    Sceptre's talk page

    Transcluding Sceptre's talk page here. Please copy in text when discussion finished. Carcharoth (talk) 18:28, 7 September 2008 (UTC) [reply]


    Everyone has the right to freedom of opinion and expression; this right includes freedom to hold opinions without interference and to seek, receive and impart information and ideas through any media and regardless of frontiers.

    — Article 19 of the Universal Declaration of Human Rights

    edit 
    Some handy links
    I'm still around, pottering away, editing where I need to.

    The current local time is: 22:55, 29 May 2024 (BST)

    Only 50551 articles (0.74%) are featured or good. Make a difference: improve an article!

    from Erath from FireFox from Cool Cat from Dr. B from Holocron from Brandmeister, originally rotating from Phaedriel from Sergeant Snopake from Ding Xiang from Chili14 from Sergeant Snopake from Springeragh from Springeragh from Chili14 from Springeragh from Springeragh from Springeragh from Springeragh, originally rotating from Springeragh from Springeragh from Springeragh from Riana on behalf of User:E@L on behalf of E@L from Glygly from Felixboy from Springeragh from Darksun, originally rotating from Springeragh from Sharkface217 from Acalamari, originally rotating from I (minor barnstar) from Porcupine from RFerreira from GundamsRus from Orderinchaos from Josiah Rowe from thedemonhog from KillerChihuahua from Bearian from So Why from thedemonhog from Jenuk1985 from Chillum from TheMightyQuill from Ruby2010 from Cirt from Kudpung


    edit 
    Sceptre's talk page

    Orphaned non-free image File:Doomsday (Doctor Who).jpg

    ⚠
    ⚠
    Thanks for uploading File:Doomsday (Doctor Who).jpg. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).

    Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --TedEdwards 20:20, 29 October 2022 (UTC)[reply]

    RM of 90377 Sedna

    Hello Sceptre,

    Thanks for taking the time to assess the RM of 90377 Sedna. Please don't forget to move back Quaoar. Renerpho (talk) 01:28, 22 November 2022 (UTC)[reply]

    Hi Sceptre, Please could you reopen and relist the RM? There wasn't that much participation, !votes were pretty split and I think there was a lot more to be discussed about the matter, warranting a relist. I would certainly vote in favour of the move, as the WP:COMMONNAME in sources is not "90377 Sedna" as far as I can see.  — Amakuru (talk) 23:24, 23 November 2022 (UTC)[reply]
    @Amakuru: FWIW, there's a larger discussion over whether Sedna is definitively a dwarf planet or not going on at the talk page, and I didn't want to tip the scales one way or the other with the closure. The predominant view in the RM was against moving, so I could've closed it as "not moved", but "no consensus to change how we've done stuff, therefore we stick with the status quo ante" is also a valid closure, and FWIW, I don't think another few days of discussion would've created a consensus. Sceptre (talk) 07:12, 25 November 2022 (UTC)[reply]

    ArbCom 2022 Elections voter message

    Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

    The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

    If you wish to participate in the 2022 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:20, 29 November 2022 (UTC)[reply]

    Guild of Copy Editors December 2022 Newsletter

    Guild of Copy Editors December 2022 Newsletter

    Hello and welcome to our latest newsletter, a quarterly digest of Guild activities since October. Don't forget you can unsubscribe at any time; see below.

    Blitz: Our October Copy Editing Blitz focused on July and August 2022 request months; and articles tagged for c/e in December 2021 and January 2022. Seventeen of those who signed up claimed at least one copy-edit, and between them copy-edited forty-six articles. Barnstars awarded are here.

    Drive: In the November Backlog Elimination Drive, thirty editors signed up, twenty-two of whom claimed at least one copy-edit. Both target months—December 2021 and January 2022—were cleared, and February was added to the target months. Sixteen requests were copy-edited and 239 articles were removed from the backlog. Barnstars awarded are here.

    Blitz: Our seven-day-long December 2022 Copy Editing Blitz begins on 17 December at 00:01 (UTC)*. It will focus on articles tagged for copy-edit in February 2022, and pending requests from September and October. Barnstars awarded will be available here.

    Progress report: As of 22:40, 8 December 2022, GOCE copyeditors have processed 357 requests since 1 January, there were seventy-four requests outstanding and the backlog stands at 1,791 articles. We always need skilled copy-editors; please help out if you can.

    Election news: Nomination of candidates for the GOCE's Election of Coordinators for the first half of 2023 is open and continues until 23:59 on 15 December. Voting begins at 00:01 on 16 December and closes at 23:59 on 31 December. All editors in good standing (not under ArbCom or community sanctions) are eligible and self-nominations are welcomed. Coordinators serve a six-month term that ends at 23:59 on June 30. If you've thought about helping out at the Guild, please nominate yourself or any editor you consider suitable—with their permission, of course!. It's your Guild and it doesn't coordinate itself.

    Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers and best seasonal wishes from your GOCE coordinators, Baffle gab1978, Dhtwiki, Miniapolis, Tenryuu, and Zippybonzo.

    *All times and dates on this newsletter are UTC.
    To discontinue receiving GOCE newsletters, please remove your name from our mailing list.

    Sent by Baffle gab1978 via MediaWiki message delivery (talk) 00:26, 9 December 2022 (UTC)[reply]

    Guild of Copy Editors December 2022 Newsletter error

    The GOCE December 2022 newsletter, as sent on 9 December, contains an erroneous start date for our December Blitz. The Blitz will start on 11 December rather than on 17 December, as stated in the newsletter. I'm sorry for the mistake and for disrupting your talk page; thanks for your understanding. Sent by Baffle gab1978 via MediaWiki message delivery (talk) 21:30, 9 December 2022 (UTC)[reply]

    Palestinian exodus close

    Hi, I must take issue with the recent close. It states:

    the closer stated the discussion and arguments were fairly balanced when what the closer actually said was

    While the discussion and arguments seem fairly balanced in number.....my decision that those who support the move have a better understanding of the article and what its title should be

    Furthermore, the review closure also stated

    Please do note that the community takes issue with UtherSRG's method, not his outcome. It will be in order for someone else to re-close this requested move as move if that is their assessment of the consensus

    Afaics, the current close amounts to a vote count that takes no account of the quality of the arguments in support of either the original or the proposed title, the "better understanding", I request that you take another look.

    Thank you. Selfstudier (talk) 11:18, 10 December 2022 (UTC)[reply]

    @Selfstudier: At the same time, I cannot create a consensus where there clearly is none. Nothing happened in the RM after it was re-opened. At the MRV, overturning to no consensus was supported by a good proportion of people, and I agree with them. Sceptre (talk) 14:06, 10 December 2022 (UTC)[reply]
    Agree with Selfstudier, Sceptre, because far too many editors agreed that the first closure, which did find a consensus to move, was correct. You say you did not see a consensus, but you don't say why? The support args far outweighed the oppose args, which is the main reason the first closure's review ended in "vacate" rather than in "overturn to no consensus". Please reassess the arguments to find what we say here is true. That article needs to be renamed as proposed. P.I. Ellsworth , ed. put'r there 06:28, 12 December 2022 (UTC)[reply]
    Yes, agreed. I noted at the MRV that there was consensus to close, just that the previous closer gave a spurious reason for seeing consensus there. Closure is supposed to be viewed through the lens of policy, not by counting heads, and in this case there was strong evidence by those in support, invoking the WP:NPOV policy, that the term "expulsion and flight" is better and more neutral wording than the status quo. I wish I'd cast another "support" !vote at the discussion now, because the arguments to move were vastly more persuasive and rooted in evidence than those in opposition, and I didn't really expect a no-consensus closure after all that had been said at the MRV, it was simply that a more clear close was required than that previously given. Cheers  — Amakuru (talk) 15:09, 12 December 2022 (UTC)[reply]

    Palestinian exodus move

    Your close doesnt seem to address the merits of the arguments at all, and ask that you reconsider by either relisting (it had only been relisted for three days prior to your close) or address the merits of the arguments. When one group provides sources and the other side just says POV that should not result in no consensus. nableezy - 14:53, 12 December 2022 (UTC)[reply]

    I see this has already been requested, if you are going to refuse can you say so in order to open a new move review? nableezy - 14:54, 12 December 2022 (UTC)[reply]
    @Paine Ellsworth, Amakuru, and Nableezy: Hey all. Having a second look at the RM, although the arguments to move were more detailed than those opposing the move, I still cannot create a consensus where there is none. I'm sympathetic to the argument, and personally I believe the people arguing in favour of a move are right. But as a closer, my role is to evaluate the discussion, and I cannot see a consensus either way. Nor was it likely that a consensus was going to develop; there was no participation in the RM after it was reopened. In such circumstances, I can't do anything but close as "no consensus". Sceptre (talk) 17:04, 13 December 2022 (UTC)[reply]
    Yes, you can, you can not close a move that was relisted for 3 days, especially when experienced closers and admins are telling you that you are incorrect in your reading of the discussion and of "consensus". But fine, Ill open a move review. nableezy - 17:10, 13 December 2022 (UTC)[reply]

    Move review for 1948 Palestinian exodus

    An editor has asked for a Move review of 1948 Palestinian exodus. Because you closed the move discussion for this page, or otherwise were interested in the page, you might want to participate in the move review. nableezy - 17:26, 13 December 2022 (UTC)[reply]

    Closure of Maori Party RM

    Hi,

    I request that you reopen and relist your recent closure of this RM. To close this RM based on counting !votes is inappropriate. Consensus is not based on just counting the number of heads.

    In addition, in my opinion your closing statement does not address the arguments raised during the RM. Did you consider WP:CRITERIA-based arguments? Did you consider that the party does not use one name over the other on it's website, when at least three support !votes stated that they do? -Spekkios (talk) 23:58, 10 December 2022 (UTC)[reply]

    @Spekkios: I did consider WP:CRITERIA, and found arguments for "Māori Party" and "Te Pāti Maori" to be relatively equal in weight. At such a point, I have to fall back on the direction of the discussion, which was clearly in favour of the move. Sceptre (talk) 17:04, 13 December 2022 (UTC)[reply]
    If the arguments are relatively equal in weight, that would imply a "no consensus" closure instead of a "move" closure. How does the discussion "direction" or the number of !votes matter if the policy based arguments are equal in weight? --Spekkios (talk) 21:51, 13 December 2022 (UTC)[reply]
    ==Move review for Te Pāti Māori==
    An editor has asked for a Move review of Te Pāti Māori. Because you closed the move discussion for this page, or otherwise were interested in the page, you might want to participate in the move review. Spekkios (talk) 23:33, 17 December 2022 (UTC)[reply]

    Introducing arguments in closures

    Hi, um, slightly awkward to pile on like this, but I don’t actually have any issue with the decision of your closure. Rather I came to advise on a less central detail: you should avoid introducing new arguments in your closures. In this case, the point about NZ English being quick to adopt Māori vocab seems to come out of nowhere and doesn’t reflect the discussion. I think a better summary would have mentioned something like “proponents emphasised that the party refers to itself as te Pāti Māori (in English)”, which seems to be one of two dominant arguments (along with commonness). — HTGS (talk) 01:17, 11 December 2022 (UTC)[reply]

    @HTGS: In hindsight, you're right about the wording. I didn't think the comment came out of nowhere; there is a propensity in NZ-related RMs for people less familiar with NZEng to treat Māori vocabulary as "not English enough", which I felt was being introduced in this RM. But yes, the key point is that the use in English, not the use of English (see also also: Senedd), for which I was satisfied "Te Pāti Māori" was common enough to be a COMMONNAME. Sceptre (talk) 17:04, 13 December 2022 (UTC)[reply]

    Day of reckoning

    I don't notice any objection to moving that to Day of Reckoning (disambiguation). I think that could have been the outcome, rather than "no consensus". —⁠ ⁠BarrelProof (talk) 17:33, 11 December 2022 (UTC)[reply]

    Should no consensus mean reverting to previous title?

    I see you recently closed a requested move as no consensus. I agree there wasn't any consensus. Should this mean that the article should revert back to its previous long-term and stable title? the article was called "Tehrik-i-Taliban Pakistan" from 2008 to May 2022, when it was moved after this discussion. But this discussion doesn't seem to have enough participation to constitute consensus (2 supports and 1 oppose). This rationale was also mentioned by Paine Ellsworth. VR talk 16:44, 14 December 2022 (UTC)[reply]

    For what it's worth, move requests don't need to have a certain magnitude of participation for them to be regarded as legitimate (vide WP:RMNOMIN), as decisions are made by a consensus process, which factors in the policy-based reasoning of participants, and not vote-counting; and an absence of objection does contribute to the consensus too. As someone who participated in the discussion, I find the above bid to solicit a move indirectly without notifying the editors on the talk page to be quite discourteous inasmuch as the magnitude to which it was vehemently opposed (being eloquent of disagreement) by a laundry list of long-term contributors (including Andrewa and Amakuru), who argued against the move on policy grounds, in contrast to the support it garnered from a considerable number of SPAs, block-evading socks, and topic banned users who trivialized the consensus process by construing the discussion to be some sort of a votestacking contest; not to mention the fact that the title had been stable for about half a year until a block-evading IP began, and thereupon tainted the RM with more socks. In my view, the foregoing quite clearly forecloses the possibility of a revert back to old title. MBlaze Lightning (talk) 22:36, 14 December 2022 (UTC)[reply]
    To editors VR and MBlaze Lightning: might have handled this differently; however, the outcome in this case is a reasonable one. And this due to ML's argument above for a set new consensus being in place long enough to matter. And I trust Andrewa's and Amakuru's opinions beyond words. So in the end there's a good possibility I would have closed the same way Sceptre did. P.I. Ellsworth , ed. put'r there 23:15, 14 December 2022 (UTC)[reply]
    On an incidental note, Sceptre, and I say this with all due respect for your prior experience in evaluating consensus-building discussions, and having elucidated the context above, I am curious to understand how you construed the discussion to be resulting in a no consensus. The chief argument of the chief proponent of the move (also the OP arguing for the restoration of old title above) was that the existing title adverted to more than a solitary subject, which was debunked by a reference to WP: PRIMARY TOPIC categorically by at least three editors (who had to presuppose that this was the case in the first place in view of disagreement on this contention). Amakuru, who chimed in late into the discussion and who would have been on the mark and justified in closing the discussion to boot, encapsulated his recapitulation of the discussion as:

    Oppose - it has been clearly demonstrated above, using Google hits as well as G-books hits, that the common name for this group is "Pakistani Taliban". It's also clearly the primary topic for that term, compared to the topic of other Taliban who hail from Pakistan or other groups operating there. Although the !vote here looks split, I think this is a "consensus against move" scenario because the policy arguments for the present title are a lot stronger than those for the alternative
    — User:Amakuru 12:00, 28 November 2022

    Likewise, Andrewa reiterated the underlying essence of his argument, when he proffered: .. If that term is ambiguous and the current article is not the Primary Topic (about which I am not convinced), should it be a DAB? Andrewa (talk) 15:58, 12 November 2022 (UTC). I too had recapitulated the essence of my argument a day before your closure[38]. In consequence, I don't think putting these quality arguments grounded in policies upon the same footing as those advanced by proponents of the move (whose chief reasoning was debunked, with the residual taking the form of rehash, primarily from socks and SPAs) was justified or meticulous. I did give it a food for thought before voicing my dissent, because a few months down the road this is likely to become an issue again with socks crawling out of the woodwork all over once again, and some of us may not be around (as much) on Wikipedia for it. MBlaze Lightning (talk) 11:31, 15 December 2022 (UTC)[reply]
    Yes, thanks @MBlaze Lightning: for this thoughtful response, and that would be my viewpoint as well. There are two separate issues here, firstly whether the May RM was sufficient to establish a "new status quo" to be the baseline default in the event of a subsequent "no consensus", and secondly whether the close of no consensus was itself valid. On the first, I'd say it's borderline; if the RM was very recent, I'd probably include its findings in and amongst the !votes for the second RM; but 6+ months, for an RM which was conclusively decided (i.e. not just moved without discussion) is getting to the point where it should be binding. So (with my obviously biased hat on) I wouldn't fault Sceptre for not moving back to the original name. On the second issue, I agree that it definitely should have been a "consensus against moving" close, when evaluating through the strength of argument, WP policy and evidence. Furthermore, in a contentious and close RM such as this, I would expect a summary from the closer as to why they've come to the conclusion they have... not just a single-line "no consensus"... as indeed was the case at the Talk:1948_Palestinian_exodus#Requested_move_8_September_2022 RM mentioned in the sections above and now at move review. WP:CONSENSUS is formed by viewing !votes through the lens of policy, and both supporters and opposers need to know why a closer reached the conclusion they did. Cheers  — Amakuru (talk) 11:51, 15 December 2022 (UTC)[reply]
    @MBlaze Lightning: this is a rehash of the argument in made during the RM, but you are confusing two different topics here. Just because a title has a WP:PRIMARY TOPIC doesn't mean that that topic unambiguously refers to only that primary topic. A great example is given in policy itself[39], at WP:COMMONNAME, and that is Heart attack. The Primary topic of Heart attack, and the page it redirects to, is Myocardial Infarction. However, heart attack can also refer to cardiac arrest. VR talk 19:49, 15 December 2022 (UTC)[reply]
    User:Vice regent, yeah, thanks for recollecting that you conceded to Amakuru on their primary topic contention in the discussion ([40]). This consensus then should have informed Sceptre's close, for the policy left no room for doubt that the title had to reflect the primary topic (as discerned by common usage in English RS). The guidline is perspicuous: if an expression has a primary topic, then that is what it leads to, per its dictates. This is not to say that its application is ubiquitous: as with any other MOS, exceptions do exist; and medicine domain embodies the niche where the nomenclature is conditioned by the scientific or recognised medical name commonly occuring in "recent, high-quality, English-language medical sources, rather than a lay term (unscientific or slang name)[1] or an historical eponym that has been superseded" (vide WP:NCMED). This is why the colloquial term, Heart attack, redirects to MI, despite being the primary topic. However, such exceptions do not impeach the rule itself; the latter is the established norm; whereas the former, a narrowly carved out exception to suffice the specific needs of a niche community. MBlaze Lightning (talk) 21:20, 15 December 2022 (UTC)[reply]
    Again, I think you're mistaken about Primarytopic. You seem to implying that if a title X has a primary topic Y, then our article on Y must necessarily be called X. But that's not true. The only thing the primary topic implies is that X must point to the article Y, whatever it is called. In fact, we have a whole template (Template:Redirect) that deals with such cases. Besides the "heart attack" example above, other examples include:
    • The primary topic for "Soccer" is Association football. And "soccer" has 647M google hits, vs only 10M hits for "Association Football", yet we pick the less common name.
    • The primary topic for "Western Allies" (2.3M hits) is Allies of World War II (0.2M hits), but we avoid the title that is ambiguous.
    • The primary topic for "Midwest" (171M hits) is Midwestern United States (only 1.2M hits), but again we avoid the ambiguous title. I could go on and on with dozens more examples.
    • The primary topic for "Pakistani Taliban" is indeed "Tehrik-i-Taliban Pakistan". In this case too, we should avoided the ambiguous name even if it gave somewhat more google hits.
    Likewise many times during the discussion I argued that "Tehrik-i-Taliban Pakistan" was more precise, because scholarly sources used the term "Pakistani Taliban" to refer to groups/individuals that were not TTP ([41][42][43]), for example splinter groups from TTP, groups similar to the TTP but never a part of it, as well as Pakistani members of the (Afghan) Taliban. VR talk 00:40, 16 December 2022 (UTC)[reply]
    Merely rehashing that some expression is ambiguous doesn't cut it for an argument where you have acknowledged that there is a primary topic. Matters end right there for all intents and purposes. The redirects embody an exception scenario to the aforesaid guideline, and they occur when any of the conditions set forth in WP:PRIMARYREDIRECT hold good, which wasn't remotely the case with this article; indeed, it was no one's argument, forget an effort that convinced others. The results were lopsided and weighed in favour of the existing title. Your filibustering to derail the efforts to solicit Sceptre's construction of a "no consensus" (which didn't account for the strong policy and evidence based reasoning in oppose) is getting to the point of being unconstructive; this isn't a new RM, where you rehash and even dwell on the issue anew with previously unmentioned examples; desist, please. MBlaze Lightning (talk) 06:39, 16 December 2022 (UTC)[reply]

    Sorbonne

    Please fix the many incoming links to this dab page, which previously pointed to the page now at "(building)". Thanks. PamD 05:28, 17 December 2022 (UTC)[reply]

    Orphaned non-free image File:Doomsday (Doctor Who).jpg

    ⚠
    ⚠
    Thanks for uploading File:Doomsday (Doctor Who).jpg. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).

    Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --TedEdwards 03:16, 31 December 2022 (UTC)[reply]

    Happy New Year, Sceptre!

    Happy New Year!

    Sceptre,
    Have a prosperous, productive and enjoyable New Year, and thanks for your contributions to Wikipedia.
    — Moops ⋠T⋡ 17:21, 2 January 2023 (UTC)[reply]

       Send New Year cheer by adding {{subst:Happy New Year fireworks}} to user talk pages.

    — Moops ⋠T⋡ 17:21, 2 January 2023 (UTC)[reply]

    Closure of Prinz von Preussen RM

    Hello!

    I was curious to know why you closed the recent RM [44] on Franz Willem Prinz von Preussen in favor of the move? The majority (albeit 7-6, by my count) were opposed to the move. Further, the official website of the princes of Prussia [45] refers to "Georg Friedrich, Prince of Prussia" not the current article title. I would suggest revisiting this RM, as it does not even seem reliable english sources use the title. I would also argue the discouragement of hypothetical titles in WP:NCROY doesn't apply because reliable sources do in fact use the title. Here are some: [46] [47] [48][49] Estar8806 (talk) 23:26, 19 January 2023 (UTC)[reply]

    FAR for Partners in Crime (Doctor Who)

    I have nominated Partners in Crime (Doctor Who) for a featured article review here. Please join the discussion on whether this article meets the featured article criteria. Articles are typically reviewed for two weeks. If substantial concerns are not addressed during the review period, the article will be moved to the Featured Article Removal Candidates list for a further period, where editors may declare "Keep" or "Delist" in regards to the article's featured status. The instructions for the review process are here. Z1720 (talk) 16:32, 28 January 2023 (UTC)[reply]

    Mergers

    Hello @Sceptre!

    I had never proposed mergers until recently, and most of my proposals haven't been gaining much traction. I would appreciate your insight on these 3 proposals of mine: 1, 2, 3

    Any insight is greatly appreciated. Thank you for your time! Mooonswimmer 21:40, 28 January 2023 (UTC)[reply]

    @Mooonswimmer: If nobody objects to the proposal after a decent amount of time, just feel free to do the merge yourself. :) Sceptre (talk) 21:48, 28 January 2023 (UTC)[reply]

    1948 Palestinian exodus close

    Why would you close this when you were involved with a previous near-identical close that was challenged and which came up with no consensus on the quality of your close? Part of the complaint was that you did a vote count and didn't expand on the arguments or policy. Now you have closed an almost identical RM (with yourself now arguably involved in the overall imbroglio) and performed what appears to be another vote count without any mention of the arguments or policy, and in part referred to the previous close with which you were involved. In the most unflattering light, this close could even be interpreted as you returning with the specific intent of reiterating your own previous, challenged verdict to make a point. I would strongly suggest that you re-open and leave it to a closer that is more obviously uninvolved. Iskandar323 (talk) 05:04, 29 January 2023 (UTC)[reply]

    WP:INVOLVED explicitly does not apply to actions taken in a purely administrative role. As I've said, if there was truly a consensus to move the article, I would be perfectly happy to do so. But if anything about the past six months of discussion over three extended RM periods and two MRV periods has shown, it's not only that there isn't a consensus, but also that there won't be a consensus forthcoming. If you disagree, you can go for a third move review of this RM, but honestly, I think we'd all be better off if we let the matter rest for a while. Sceptre (talk) 05:35, 29 January 2023 (UTC)[reply]
    Regardless of the letter of the law, your involvement at this stage was unwise to the say the least given your past involvement in a similar case and the subsequent contention. In addition, the combined lack of policy/argument reflection and similarly off-topic reflections on past closes used to justify the close (again) was of course almost guaranteed to raise recurring questions. If you don't have the energy to engage fully with a subject of this nature, don't engage with it. The handling of contentious topic discussions is often best left to administrators. I think you closing this almost guarantees another move review, but if that is an outcome you are happy with, so be it. Iskandar323 (talk) 06:25, 29 January 2023 (UTC)[reply]

    That is an absurd close, and you emphatically do not have authority to impose a moratorium. nableezy - 16:56, 13 February 2023 (UTC)[reply]

    Please see Wikipedia:Move_review/Log/2023_February#1948_Palestinian_exodus nableezy - 17:12, 13 February 2023 (UTC)[reply]

    Royal Rumble 2023

    Thank you for undoing my edits. Yes, at the article Royal Rumble (2023), WWE officially lists Rhea Ripley as staying in the women's Royal Rumble match 1 second longer than Liv Morgan, although other sources say that the match ended as soon as Morgan was eliminated, and Ripley and Morgan set the record. If you have further issues, please discuss it in the article's talk page. GodofDemonwars (talk) 00:18, 1 February 2023 (UTC)[reply]

    Guild of Copy Editors 2022 Annual Report

    Guild of Copy Editors 2022 Annual Report
    Our 2022 Annual Report is now ready for review.

    Highlights:

    • Overview of Backlog-reduction progress
    • Summary of Drives, Blitzes, and the Requests page
    • Membership news and results of elections
    • Closing words
    – Your Guild coordinators: Baffle gab1978, Dhtwiki, Miniapolis and Zippybonzo
    To discontinue receiving GOCE newsletters, please remove your name from our mailing list.

    Sent by Baffle gab1978 using MediaWiki message delivery (talk) 00:30, 6 February 2023 (UTC)[reply]

    Orphaned non-free image File:Doctor Who series 2 soundtrack.jpg

    ⚠
    ⚠
    Thanks for uploading File:Doctor Who series 2 soundtrack.jpg. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).

    Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --B-bot (talk) 18:15, 10 February 2023 (UTC)[reply]

    Recent move

    Hi there,

    How did you determine that the consensus for this move was not the proposed title? Spekkios (talk) 21:00, 10 February 2023 (UTC)[reply]

    @Spekkios:: HTGS's argument was the most persuasive, both to me and other editors in the discussion. When it comes to NZEng, there's no bright line to go to for the English, Māori, or dual names and it ultimately comes down to which has the most evidence to go with. In this case, based mostly on HTGS's comment, I determined it was the Māori one. Sceptre (talk) 14:03, 12 February 2023 (UTC)[reply]
    How are you determining that the argument presented by HTGS was persuasive to other editors? Unless I am mistaken, no other editors are referencing their argument. --Spekkios (talk) 18:12, 12 February 2023 (UTC)[reply]
    Since you haven't clarified further, please see here. --Spekkios (talk) 08:56, 20 February 2023 (UTC)[reply]

    Requested move at WikiProject Ukraine

    Regarding the close at Wikipedia talk:WikiProject Ukraine#Requested move 7 February 2023. The statement about the decision completely ignores the important point about the difference between the names in article titles and parenthetic disambiguation strings, as well as the cited precedent, citing examples that are not analogies for this at all (on top of that, Istanbul and Constantinople are completely different names, not just a spelling variation in a city name that hasn’t changed in over a millennium). It seems a completely unsatisfactory rationale, as in it gives no indication that you read the proposal or considered the points made in it.source] ]]  —Michael Z. 20:52, 16 February 2023 (UTC)[reply]

    @Mzajac: although Constantinople may arguably be or not be an adequate comparison, I believe that Calcutta/Kolkata is; they’re both changes in (Western) English orthography to the local orthography, where the local orthography is more common. However, it’s not always the case that the change is consistent when talking retrospectively; although "Mumbai" is almost universally used these days, usage is split on the 1993 Bombay bombings. Regardless, there isn’t a consensus for a move anyway, and the retrospectivity (or lack thereof) of COMMONNAME was brought up in the discussion. Sceptre (talk) 23:33, 16 February 2023 (UTC)[reply]
    That’s all academic because the change was to the parenthetic disambiguation text, not the name. COMMONNAME doesn’t apply to disambiguation text.
    WP:PRECISION says to use the least-precise version sufficient to disambiguate. The main-article-title spelling of the city is good enough, and there’s no point in narrowing it to a historical spelling that is only used in restricted contexts.
    WP:TITLEDAB reinforces the idea: “use only as much additional detail as necessary.” The examples there make it clear to use the broadest term possible, not one that applies only in a specific context, like a historical one.
    And WP:CONSISTENCY is violated, because the new decision conflicts with the precedent cited in the proposal: the consensus move of a similar article to Folkstsaytung (Kyiv).
    And there is no consensus to use the dated spelling Kharkov in historical contexts.
    It’s not the end of the world if these are not moved, but it seems to be contrary to best practices. I urge you to reconsider the decision or even reopen it to get more input, but I’ve had my say and I won’t belabour it further if you choose not to. Thanks for closing the RM anyway. Cheers. —Michael Z. 04:09, 17 February 2023 (UTC)[reply]

    Maize -> Corn RM

    Thanks for taking the time to read that novel. I'd just like to know what arguments you found most compelling, so I can understand more about Wikipedia guidelines.

    Your reasoning on the talk page itself is that the common name may change from Maize to Corn, but it hasn't yet, similar to Iroquois → Haudenosaunee. However, the arguments used to show that Iroquois is still the most commonly used name is the exact sort used to show why Corn is the most commonly used name. Most relevantly, even in scientific and scholarly papers Maize is used about 1/3rd as much as Corn, as shown in the RM.

    Could you explain the differences between the two situations? Without knowing more about your point of view, one could look at these two examples and assume that the default is 'no consensus' when a tough decision needs to be made. OuroCat (talk) 23:12, 16 February 2023 (UTC)[reply]

    FYI

    Information icon You have recently made edits related to the Arab–Israeli conflict. This is a standard message to inform you that the Arab–Israeli conflict is a designated contentious topic. This message does not imply that there are any issues with your editing. Additionally editors must be logged-in have 500 edits and an account age of 30 days, and are not allowed to make more than 1 revert on the same page within 24 hours for pages within this topic. For more information about the contentious topics system, please see Wikipedia:Contentious topics. nableezy - 13:46, 17 February 2023 (UTC)[reply]

    RM closure

    Hello, Sceptre. Regarding your closure at Aguascalientes City, I notice you wrote that "documentary evidence has been provided to the contrary" only for Chihuahua City, which you exempted... but an even greater volume of documentary evidence was provided for Oaxaca City, which you didn't. Was that intentional, and if so could you share the rationale? Thanks for any clarification. ╠╣uw [talk] 17:09, 20 February 2023 (UTC)[reply]

    I'll add that a lot of evidence was introduced for Queretaro City, as well. Red Slash 17:12, 20 February 2023 (UTC)[reply]

    @Huwmanbeing and Red Slash:: It was completely unintentional, but from looking further at the discussion, I can see there's no reason to not apply that exemption for Oaxaca and Querétaro. I'll happily reverse those moves and amend my closure in those cases. Sceptre (talk) 17:21, 20 February 2023 (UTC)[reply]
    Thank you. Chihuahua City, Oaxaca City, and Querétaro City were the only ones actually tested for evidence of common usage; that they all showed it suggests the others are likely the same. I feel like it would've been preferable for the nominator to investigate this before making the bulk proposal, but it sounds like individual RMs or a second bulk RM will be needed for these now. ╠╣uw [talk] 19:50, 20 February 2023 (UTC)[reply]
    Yes, I didn't test all the other ones, because it would have been exhausting, but I think you probably would've found the same for all the others (possible exceptions might include Colima, which is--slight exaggeration--basically a microstate, or maybe some extremely small cities/states like Aguascalientes itself that don't have much of any English-language coverage at all, but no evidence was offered in the move request whatsoever). Thanks for putting the accent in Querétaro City, btw--my bad for being lazing and omitting it. Red Slash 17:17, 22 February 2023 (UTC)[reply]
    RS: Yes, I think it just comes down to the original bulk request being poorly formed, in that it wrongly assumed that none of the listed cities commonly use the "City" form, whereas spot checks showed that wasn't true for several (and suggested it might not be true for any). I think ideally those that haven't been checked wouldn't be moved until they have, but it's not the end of the world either way and I'm fine with whatever solution's easiest. Recommendations, Scepter? ╠╣uw [talk] 18:19, 22 February 2023 (UTC)[reply]

    Sceptre, I must applaud you for your efforts. But I think there’s a bit of confusion lurking here. There is no community consensus, nor local consensus in this RM, that says that demonstration of some common usage of a given natural disambiguation for a topic means that this natural disambiguation, and not parenthetic disambiguation of the undisputed most common name, must be used as the title. As noted in the discussion, NATURAL merely notes that the natural disambiguation may be preferred. Well, in all of these cases, without any exceptions, consensus in this RM clearly prefers the parenthetic disambiguation. Please close according to community and local consensus. Thank you. —В²C ☎ 02:19, 21 February 2023 (UTC)[reply]

    Sceptre, hello? Would you prefer to address this in an MR? —В²C ☎ 06:15, 22 February 2023 (UTC)[reply]
    Funnily enough, I was considering a move review as well, since no evidence was provided for the vast majority of the cities that the X City name was not common; I provided several counterexamples for Chihuahua and Queretaro specifically (and I believe Huw did the same for Oaxaca), and I think I provided enough evidence to show that if those two or three were off, than everything was off.
    Frankly, I think the move request should've been dropped as no consensus, and then people individually could've made proposals at each one to look at how much English-language usage the X City form had for each one individually. Most likely Chihuahua would've failed (stayed at City); perhaps Aguascalientes itself would've succeeded; in any case, I was thinking of a move review. (Also, B2C, I have so much respect for you, even ywith this disagreement, but like... you gave Spectre 28 hours to respond, give her a bit more time ) Red Slash 17:17, 22 February 2023 (UTC)[reply]
    I repeat, even if evidence of common usage of Name City was shown for every city on the list that wouldn’t be sufficient to override the consensus to move them all to parenthetic disambiguation, as proposed, nonetheless. While lack of common usage is sufficient reason to not use a given alternative name, evidence of common usage is not sufficient to use it rather than parenthetic disambiguation. There are other considerations to be made and ultimately it’s decided by consensus, not the closer. The closer is only supposed to decide what the consensus is. Otherwise it’s a WP:SUPERVOTE. Here, the closer’s unilateral decision to exclude first 1, then 2 then 3, from the list, when consensus for/against the move of each was equal for all, is a super vote. —-В²C ☎ 18:09, 22 February 2023 (UTC)[reply]
    Bizarre as it may seem, I'd say exactly the opposite. Got lots of respect for you, B2C, but to me, saying "yeah the amount of supports for Durango City vis-a-vis Chihuahua City were the same, but Chihuahua City had actual evidence presented and Durango didn't, so I'm going to treat them differently" sounds like something a good closer would do.
    But of course that ignores the more important point that there was no evidence provided whatsoever that Durango City isn't a common name for the city. Which is why we're going to go to Move Review. Red Slash 17:29, 23 February 2023 (UTC)[reply]
    @Born2cycle and Huwmanbeing:: I think this is a problem with these multi-page RMs; indeed, I went into the closing process hoping that I wouldn't have to move the pages. But as it was, the RM was balancing on the scales of "move" vs "no consensus"; the consistency argument isn't as strong given the examples of other cities (in Mexico, Japan, and of course, Cork). I also agree that "X City" would be a decent enough NATURAL disambiguation, were it not for the "don't use natural disambiguations that are obscure" part of WP:NATURAL"; except for the three cases I exempted, I didn't see anything in the RM that adequately rebutted that argument. With all that said, I don't oppose starting new singular RMs if the evidence for "X City" can be shown for the other cities in the list. Sceptre (talk) 19:34, 22 February 2023 (UTC)[reply]
    If you don’t see anything in the RM that adequately rebutted that, it’s because you’re ignoring my rebuttal (in the last comment in the RM discussion) which points out that the "don't use natural disambiguations that are obscure" part of WP:NATURAL simply points out an extreme limit to where natural disambiguations are not to be used. It’s quite a leap not supported by local or community consensus to interpret that to mean, “if the natural disambiguation in question is not obscure then it must be used.” Yet you are inexplicably interpreting it to mean that. The key question here is not about whether the natural disambiguation may be used. I mean, in those cases where it’s obscure it may not be used, of course. But in any case where it’s (at least arguably) not obscure that just means it may be used, not that it must be. So, in those cases where the natural disambiguation is not obscure the key question is which disambiguation form is preferred. And, again, consensus was the same for every city in the list: parenthetic disambiguation is preferred to Name City disambiguation in each of these cases. Whether natural disambiguation is allowed or not by NATURAL due to level of obscurity is entirely besides the point. Yet you chose to take that into account. That’s a SUPERVOTE. —В²C ☎ 21:36, 22 February 2023 (UTC)[reply]

    Move review for Aguascalientes City

    An editor has asked for a Move review of Aguascalientes City. Because you closed the move discussion for this page, or otherwise were interested in the page, you might want to participate in the move review. Red Slash 19:24, 23 February 2023 (UTC)[reply]

    Your userpage

    Hi @Sceptre! I landed on your userpage following a recent ANI post of yours and I just wanted to say that I am really quite impressed with the visual structure. I am sure you get this a lot, but it's such a pleasure to read through. I've probably spent more time editing my userpage than I care to admit (lmao) and it's always nice to see some inspirations. Ppt91talk 20:18, 26 February 2023 (UTC)[reply]

    Murder of Michelle Confait

    Hi. I would ask you to reconsider this close. The nomination and support votes were based on a flawed premise, that Confait identified as a trans woman. As I said in the discussion, there is no reliable evidence for this. An editor added it to the article a few years ago and the editors who supported the nomination clearly just supported without checking the evidence (or lack of). In any case, this is a well-known murder in British criminal history and the victim is invariably referred to as Maxwell Confait. We cannot apply modern ideas to something that happened fifty years ago. The rename is a clear violation of WP:COMMONNAME. Thanks. -- Necrothesp (talk) 11:18, 27 February 2023 (UTC)[reply]

    @Necrothesp: The relevant guideline here is MOS:GENDERID, which applies to anyone whose gender might (operative word) be questioned. There's no dispute that there's a question about Confait's gender, and furthermore, it's not disputed that they preferred to be known as "Michelle". Additionally, WP:COMMONNAME allows divergence if the most common name is problematic; the amount of "per nom" comments indicate a general agreement that that's the case. Sceptre (talk) 11:55, 27 February 2023 (UTC)[reply]
    Yes, but, as I said, the whole nomination seems based on an unsourced edit made to the article some years ago that has clearly been taken as true without any evidence. The supporters have merely accepted that it is true without any knowledge of the situation (note they all came before I pointed this out). Nobody fifty years ago would have referred to themselves as a trans woman. We cannot change history to what we think it should be. We can only report what it was. This is a famous murder case and is invariably referred to as the murder of Maxwell Confait. How is it helping our users to use a name that was never actually used in the many reliable sources on the case? -- Necrothesp (talk) 13:03, 27 February 2023 (UTC)[reply]
    @Necrothesp: Whether Confait would've used the phrase "trans woman" or not isn't within the spirit of MOS:GENDERID; indeed, I have a suspicion that the "might be questioned" line was to catch historical cases such as Sylvia Rivera (et. al) where the line between "homosexual transvestite" and "trans woman" are blurred. I've found two other sources further to what was mentioned in the RM which also talk about Confait in the context of being transgender: Reclaiming Genders by Whittle et al, and this Salon article about Amanda Milan, which talks about Confait's murder being at the top of a long list of murdered trans sex workers. As far as I'm concerned, the Gianassi book, alongside those two sources I've listed in this reply, should be enough to meet the "might be questioned" part of GENDERID. Sceptre (talk) 14:57, 27 February 2023 (UTC)[reply]

    Move review for Murder of Michelle Confait

    An editor has asked for a Move review of Murder of Michelle Confait. Because you closed the move discussion for this page, or otherwise were interested in the page, you might want to participate in the move review. -- Necrothesp (talk) 14:54, 1 March 2023 (UTC)[reply]

    Happy Birthday!

    Talk:1896 Summer Olympics#Requested move 9 February 2023

    Please rethink or undo this close. Closers ought to know how to intepret policy and assess arguments under the lens of policy, but your closing summary indicates you don't know how to do that, and instead ignored policy based on the local consensus. TITLECHANGES can't be used to oppose change just for the sake of opposing change, and all the other policy-based arguments (COMMONNAME, CONCISE) supported the move. Avilich (talk) 00:57, 5 March 2023 (UTC)[reply]

    @Avilich: I did take those into account those policies, and also the previous RM. I did not see a consensus to move the article, just like the previous RM. I'd be happy to relist if you'd like, but in my opinion, it'll probably be closed again in a week with the same result. Sceptre (talk) 21:19, 5 March 2023 (UTC)[reply]
    I respectfully disagree. I won't ask you to relist since it has been a while already, so I'm posting this on move review Wikipedia:Move review/Log/2023 March#1896 Summer Olympics. Avilich (talk) 16:59, 6 March 2023 (UTC)[reply]

    Guild of Copy Editors March 2023 Newsletter

    Guild of Copy Editors March 2023 Newsletter


    Hello and welcome to the March 2023 newsletter, a quarterly digest of Guild activities since December and our Annual Report for 2022. Don't forget you can unsubscribe at any time; see below. We extend a warm welcome to all of our new members, including those who have signed up for our current March Backlog Elimination Drive. We wish you all happy copy-editing.

    Election results: In our December 2022 coordinator election, Reidgreg and Tenryuu stepped down as coordinators; we thank them for their service. Incumbents Baffle gab1978, Dhtwiki, Miniapolis and Zippybonzo were returned as coordinators until 1 July. For the second time, no lead coordinator was chosen. Nominations for our mid-year Election of Coordinators open on 1 June (UTC).

    Drive: 21 editors signed up for our January Backlog Elimination Drive, 14 of whom claimed at least one copy-edit. Between them, they copy-edited 170 articles totaling 389,737 words. Barnstars awarded are here.

    Blitz: Our February Copy Editing Blitz focused on October and November 2022 requests, and the March and April 2022 backlogs. Of the 14 editors who signed up, nine claimed at least one copy-edit; and between them, they copy-edited 39,150 words in 22 articles. Barnstars awarded are here.

    Drive: Sign up now for our month-long March Backlog Elimination Drive. Barnstars awarded will be posted here after the drive closes.

    Progress report: As of 12:08, 19 March 2023 (UTC), GOCE copyeditors have processed 73 requests since 1 January 2023, all but five of them from 2022, and the backlog stands at 1,872 articles.

    Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators Baffle gab1978, Dhtwiki, Miniapolis and Zippybonzo.

    To discontinue receiving GOCE newsletters, please remove your name from our mailing list.

    Proposed deletion of Combat (Torchwood)

    Notice

    The article Combat (Torchwood) has been proposed for deletion because of the following concern:

    Appears to fail notability, nothing found in a BEFORE. Tagged for notability since 2011

    While all constructive contributions to Wikipedia are appreciated, pages may be deleted for any of several reasons.

    You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.

    Please consider improving the page to address the issues raised. Removing {{proposed deletion/dated}} will stop the proposed deletion process, but other deletion processes exist. In particular, the speedy deletion process can result in deletion without discussion, and articles for deletion allows discussion to reach consensus for deletion. DonaldD23 talk to me 16:58, 1 April 2023 (UTC)[reply]

    Nomination of Combat (Torchwood) for deletion

    A discussion is taking place as to whether the article Combat (Torchwood) is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or whether it should be deleted.

    The article will be discussed at Wikipedia:Articles for deletion/Combat (Torchwood) until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.

    Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article until the discussion has finished.

    DonaldD23 talk to me 02:22, 8 April 2023 (UTC)[reply]

    "Weapons of resident evil 4" listed at Redirects for discussion

    The redirect Weapons of resident evil 4 has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Anyone, including you, is welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2023 April 21 § Weapons of resident evil 4 until a consensus is reached. Steel1943 (talk) 20:23, 21 April 2023 (UTC)[reply]

    Always precious

    Ten years ago, you were found precious. That's what you are, always. --Gerda Arendt (talk) 07:37, 27 April 2023 (UTC)[reply]

    Guild of Copy Editors June 2023 Newsletter

    Guild of Copy Editors June 2023 Newsletter

    Hello and welcome to the June 2023 newsletter, a quarterly digest of Guild activities since March. Don't forget you can unsubscribe at any time; see below.

    Election news: Fancy helping out at the Guild? Nominations for our half-yearly Election of Coordinators are open until 23:59 on 15 June (UTC)*. Starting immediately after, the voting phase will run until 23:59 on 30 June. All Wikipedians in good standing are eligible and self-nominations are welcomed; it's your Guild and it doesn't organize itself!

    Blitz: Of the 17 editors who signed up for our April Copy Editing Blitz, nine editors completed at least one copy-edit. Between them, they copy-edited 24 articles totaling 53,393 words. Barnstars awarded are here.

    Drive: 51 editors signed up for the month-long May Backlog Elimination Drive, and 31 copy-edited at least one article. 180 articles were copy-edited. Barnstars awarded are posted here.

    Blitz: Sign up here for our week-long June Copy Editing Blitz, which runs from 11 to 17 June. Barnstars awarded will be posted here.

    Progress report: As of 03:09 on 6 June 2023, GOCE copyeditors have processed 91 requests since 1 January and the backlog stands at 1,887 articles.

    Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators Baffle gab1978, Dhtwiki, Miniapolis and Zippybongo.

    *All times and dates in this newsletter are in UTC, and may significantly vary from your local time.

    To discontinue receiving GOCE newsletters, please remove your name from our mailing list.

    Sent by Baffle gab1978 using MediaWiki message delivery (talk) 03:39, 6 June 2023 (UTC)[reply]

    Move review

    I strongly disapprove of your move of a relatively unknown person to Albert von Sachsen. That person is by no stretch of the imagination the common name or primary topic for such a term, and if the move is not reverted, I will be taking it to move review. DrKay (talk) 07:12, 15 June 2023 (UTC)[reply]

    @DrKay: I think you've got things backwards here. As there isn't another article that should be at Albert von Sachsen (other than the 18th-century Duke of Teschen, where NCROY applies differently), then the man born in 1934 can be assumed to be the primary topic.
    On the subject of COMMONNAME – as has been brought up in several German ex-nobility RMs since the abortive coup attempt last year, the use of princely titles in pretence is a WP:POVTITLE issue, and NCROY's discouragement of the use of such titles has particular weight; the use of these titles has gone from harmless althist nerdery to a far-right shibboleth.
    NPOV – as a fundament of the encyclopedia – clearly requires that in the that a POVTITLE's COMMONNAME status is evidenced. It is not enough to say "X is the common name" to oppose moving away from "X" when it has problems; it must be demonstrated through evidence that the name is overwhelmingly the most common name to the point where POVTITLE is met, and in the majority of these RMs, not even the "evidence it's the common name" bar is met. Sceptre (talk) 09:33, 15 June 2023 (UTC)[reply]
    Ouch, I have to confess I'm a little baffled here. How can you possibly find consensus for a move in such a discussion, when the voting numbers are so clearly not in favour of a move, and the overarching policy argument of WP:COMMONNAME a powerful rationale not to move. Your rationale for closing this, and indeed the previous RM (which I voted against, but then didn't notice it has been closed as moved) rest on the assertion that the long-standing names were "problematic", but the participants in the RM were far from convinced by that argument. As such, your determination as closer doesn't override multiple opinions that thy weren't problematic, which unfortunately makes your close against the numbers a good faith WP:SUPERVOTE. The whole thing is trying to WP:RIGHTGREATWRONGS in a way that isn't supported by sources. Please could you look at both of these RMs again and consider objectively whether there's any way it's a consensus to move?  — Amakuru (talk) 10:17, 15 June 2023 (UTC)[reply]
    @Amakuru: COMMONNAME is not an absolute. As I’ve mentioned here and elsewhere, COMMONNAME allows us to use other article titles if the most common name is problematic, and in none of the ex-German nobility RMs that I’ve closed since then have I been convinced by the arguments the princely titles are not problematic. Mostly, it’s a sea of “per COMMONNAME” arguments without evidence. The onus is on people to prove that COMMONNAMEs pass the higher muster if they’re problematic, and that proof hasn’t been met, and numerical majorities are not a substitute for proof in that regard. Sceptre (talk) 10:43, 15 June 2023 (UTC)[reply]
    "COMMONNAME is not an absolute" - of course, there are some exceptions but on the other hand, COMMONNAME is listed on a policy page and is widely accepted in countless RM discussions down the years as the standard we use, absent strong reason against, and is a close proxy to Wikipedia's philosophy that we reflect the world as it is, through WP:V and WP:NPOV, rather than attempting to chart a course that editors think is more "correct" than real world usage. In this case, where (a) the common name was clearly for the old title, (b) the numbers in the discussion were clearly for the old title, and (c) the old title was the longstanding status quo, there can be no objective reason for choosing something else. Your interpretation of what's problematic above is your opinion, but you know it's not one of which other editors in good standing such as myself and others share. As such, it is your duty to either close in line with consensus, or simply cast a vote yourself. You don't have the right to impose an alternative view on us in this way. Cheers  — Amakuru (talk) 10:55, 15 June 2023 (UTC)[reply]
    Yes, and NPOV – as one of the five pillars – overrides the "use the common name" shorthand. Like I said, in the case of non-neutral titles, it is incumbent on those wishing to use them to provide evidence that it's the common name – as POVTITLE says, in a "significant majority of English-language sources" — and in the related RMs that I've closed, the evidence – when provided – is sorely lacking. Sceptre (talk) 11:42, 15 June 2023 (UTC)[reply]

    Btw, what do you mean by "German ex-nobility" which I've seen you use here and there about people whose families were royalty, not nobility? --SergeWoodzing (talk) 12:35, 15 June 2023 (UTC)[reply]

    Move review for Albert von Sachsen

    An editor has asked for a Move review of Albert von Sachsen. Because you closed the move discussion for this page, or otherwise were interested in the page, you might want to participate in the move review. DrKay (talk) 10:15, 15 June 2023 (UTC)[reply]

    @DrKay: it would be useful to let the discussion above play out before starting a MRV. I also think we should include the December 2022 RM in the mix too, as that also seems to lack consensus and is probably sufficiently recent to challenge.  — Amakuru (talk) 10:19, 15 June 2023 (UTC)[reply]
    @Sceptre:, are you sure you can !vote on your own contested move? It seems to me that your explanation should be prefixed with "Closer's response" or similar, not "Endorse"... Rosbif73 (talk) 12:12, 15 June 2023 (UTC)[reply]

    Nomination of Cult of Skaro for deletion

    A discussion is taking place as to whether the article Cult of Skaro is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or whether it should be deleted.

    The article will be discussed at Wikipedia:Articles for deletion/Cult of Skaro until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.

    Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article until the discussion has finished.

    Piotr Konieczny aka Prokonsul Piotrus| reply here 03:56, 9 July 2023 (UTC)[reply]

    Oppenheimer

    There is no longer any ambiguity regarding the surname when it is at "Oppenheimer (surname)". The primary topic does not need to be mentioned in the lede. The thing you're referring to would apply to Oppenheimer (disambiguation), which I already changed. —Xezbeth (talk) 13:16, 12 July 2023 (UTC)[reply]

    @Xezbeth: At the same time, JRO does need to be in Oppenheimer (surname) (edit | talk | history | protect | delete | links | watch | logs | views). I'm relaxed on where it is, but given the prominence of the primary topic… the lede seemed more appropriate than buried in the weeds; some people might still get to the page by that page! Sceptre (talk) 13:18, 12 July 2023 (UTC)[reply]

    Minor request

    Error: Protected edit requests can only be made on the talk page.

    Hello, I'm cleaning up the dwindling number of fostered content WP:LINT errors on Wikipedia, and only 8 remain within user talk space. One of those is on your User talk:Sceptre/Archive 13 within the "Awww Will!" section. If you would be willing, would you please make the following adjustment?

    portion to change

    Change this 

    {| style="vertical-align:top" |
<div id="Awardbar" class="noprint" style="border:1px solid #000000; background:#fff; margin:0.5em 0.5em 0.5em 1em; text-align:center; padding:6px; float:right; font-size: 0.9em; width: 110px; ">This Barnstar is presented to<br />[[Image:Random Acts of Kindness Barnstar.png|110px]]<br />'''<span style="font-size:1.1em;">'''Will'''</span>'''<br />for always being close to me and willing to make me smile and cheer me up when I need it the most.<br />Thank you! :)<span style="font-size:1em;"><br />[[User:Phaedriel|<b><font color="#009900">P</font><font color="#00AA00">h</font><font color="#00BB00">a</font><font color="#00CC00">e</font><font color="#00DD00">d</font><font color="#00CC00">r</font><font color="#00BB00">i</font><font color="#00AA00">e</font><font color="#009900">l</font></b>]] </span></div>
|}That's ''such'' a beautiful cat, my dear Will - thank you so much! My talk page seems to be filling lately with pictures of lovely cats, how did you even knew I love them? Anyway, hun, I didn't want to go to bed before thanking you - the 4th of July has been tough on me, and I've hardly had any sleep in the last day; but in the meantime, beutiful messages have appeared in my talk page and I "always" reply, even if it takes me some time. I hope you're doing great, and enjoy this - you deserve it! Hugs, [[User:Phaedriel|<b><font color="#00BB00">Phædriel</font></b>]] <b><font color="#FF0000">♥</font></b> [[User talk:Phaedriel|'''<small><font color="#22AA00">tell me</font></small>''']] - 00:27, 6 July 2006 (UTC)

    to this: 

    {| style="vertical-align:top; float:right;"
|<div id="Awardbar" class="noprint" style="border:1px solid #000000; background:#fff; margin:0.5em 0.5em 0.5em 1em; text-align:center; padding:6px; font-size: 0.9em; width: 110px; ">This Barnstar is presented to<br />[[Image:Random Acts of Kindness Barnstar.png|110px]]<br /><span style="font-size:1.1em;">'''Will'''</span><br />for always being close to me and willing to make me smile and cheer me up when I need it the most.<br />Thank you! :)<span style="font-size:1em;"><br />[[User:Phaedriel|<b><span style="color:#009900">P</span><span style="color:#00AA00">h</span><span style="color:#00BB00">a</span><span style="color:#00CC00">e</span><span style="color:#00DD00">d</span><span style="color:#00CC00">r</span><span style="color:#00BB00">i</span><span style="color:#00AA00">e</span><span style="color:#009900">l</span></b>]] </span></div>
|}That's ''such'' a beautiful cat, my dear Will - thank you so much! My talk page seems to be filling lately with pictures of lovely cats, how did you even knew I love them? Anyway, hun, I didn't want to go to bed before thanking you - the 4th of July has been tough on me, and I've hardly had any sleep in the last day; but in the meantime, beutiful messages have appeared in my talk page and I "always" reply, even if it takes me some time. I hope you're doing great, and enjoy this - you deserve it! Hugs, [[User:Phaedriel|<b><span style="color:#00BB00">Phædriel</span></b>]] <b><span style="color:#FF0000">♥</span></b> [[User talk:Phaedriel|'''<small><span style="color:#22AA00">tell me</span></small>''']] - 00:27, 6 July 2006 (UTC)

    This will correct this fostered content issue, and replace the fonts for span style to address the neighboring obsolete tag issues. Thank you! Zinnober9 (talk) 01:53, 1 August 2023 (UTC)[reply]

    @Zinnober9: The page is full-protected so I've added a FPER tag so an admin can do it instead. Sceptre (talk) 20:31, 4 August 2023 (UTC)[reply]
     Done Legoktm (talk) 02:28, 5 August 2023 (UTC)[reply]
    Sorry, I missed that you weren't able to access the page, Sceptre. Thank you for the assist, Legoktm. Zinnober9 (talk) 02:45, 5 August 2023 (UTC)[reply]

    RM close

    Your close at Talk:Federal prosecution of Donald Trump (classified documents case) was way too early; it has literally been only a day and a half since the indictment, which is not enough time for discussion to evolve. Furthermore, the existing !votes don't support that there is any consensus either way yet, especially since the original proposer stated that they no longer exclusively support their original title and is open to further discussion. Please reverse the close and let the RM play out over a normal timeframe. Thanks. Antony–22 (talk⁄contribs) 04:16, 3 August 2023 (UTC)[reply]

    @Antony22: From my reading there's a general consensus that the articles about the two indictments should be similarly titled, and I have no opinion on what form this should take, and no objection to an immediate further RM encompassing both. That said, I don't think the timing of the election interference indictment is that relevant; it had been inevitable for some time, and I don't think there was a dearth of discussion warranting it being deliberately kept in the RM backlog. Sceptre (talk) 20:31, 4 August 2023 (UTC)[reply]
    I see. I'd appreciate it if you could clarify your close that the consensus only applies to there being a parenthetical "government documents" to "classified documents" while discussion was actively ongoing between the two possibilities, and if there was no consensus, then that change shouldn't have been made. I'd rather not have to do another RM over that if possible. Thanks. Antony–22 (talk⁄contribs) 05:22, 22 August 2023 (UTC)[reply]

    Llywelyn ab Iorwerth

    Please review your close here. It does not seem to me reflect the actual consensus or evidence. Srnec (talk) 20:04, 4 August 2023 (UTC)[reply]

    @Srnec: See the discussion section of the move request. It's very clear from the evidence provided by Ham II that the version with the patronymic are the COMMONNAME. The English form is very slightly than with either of the Welsh forms alone, but I don't think it's reasonable to argue that the English form "wins" because of people having different opinions on how much the vocal folds need to vibrate before you use a specific consonant. Sceptre (talk) 20:31, 4 August 2023 (UTC)[reply]

    Page move

    you closed the moving discussion thing in Muhammad ibn Musa al-Khwarizmi but the page didn't get moved Abo Yemen✉ 16:09, 6 August 2023 (UTC)[reply]

    Septermber GOCE newsletter

    Guild of Copy Editors September 2023 Newsletter

    Hello and welcome to the September 2023 newsletter, a quarterly digest of Guild activities since June. Don't forget you can unsubscribe at any time; see below.

    David Thomsen: Prolific Wikipedian and Guild member David Thomsen (Dthomsen8) died in November 2022. He was a regular copy editor who took part in many of our Drives and Blitzes. An obituary was published in the mid-July issue of The Signpost. Tributes can be left on David's talk page.

    Election news: In our mid-year Election of Coordinators, Dhtwiki was chosen as lead coordinator, Miniapolis and Zippybonzo continue as assistant coordinators, and Baffle gab1978 stepped down from the role. If you're interested in helping out at the GOCE, please consider nominating yourself for our next election in December; it's your WikiProject and it doesn't organize itself!

    June Blitz: Of the 17 editors who signed up for our June Copy Editing Blitz, 12 copy-edited at least one article. 70,035 words comprising 26 articles were copy-edited. Barnstars awarded are here.

    July Drive: 34 of the 51 editors who took part in our July Backlog Elimination Drive copy-edited at least one article. They edited 276 articles and 683,633 words between them. Barnstars awarded are here.

    August Blitz: In our August Copy Editing Blitz, 13 of the 16 editors who signed up worked on at least one article. Between them, they copy-edited 79,608 words comprising 57 articles. Barnstars awarded are available here.

    September Drive: Sign up here for our month-long September Backlog Elimination Drive, which is now underway. Barnstars awarded will be posted here.

    Progress report: As of 14:29, 9 September 2023 (UTC), GOCE copy editors have processed 245 requests since 1 January. The backlog of tagged articles stands at 2,066.

    Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators, Dhtwiki, Miniapolis and Zippybonzo.

    To discontinue receiving GOCE newsletters, please remove your name from our mailing list.

    MediaWiki message delivery (talk) 13:55, 10 September 2023 (UTC)[reply]

    User category renamed

    Hi, please update the category code in your boxes.css page from Wikipedia AfC reviewers to Wikipedia Articles for Creation reviewers. – Fayenatic London 07:46, 8 October 2023 (UTC)[reply]

    ArbCom 2023 Elections voter message

    Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

    The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

    If you wish to participate in the 2023 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:22, 28 November 2023 (UTC)[reply]

    Guild of Copy Editors December 2023 Newsletter

    Guild of Copy Editors December 2023 Newsletter

    Hello, and welcome to the December 2023 newsletter, a quarterly digest of Guild activities since September. Don't forget that you can unsubscribe at any time; see below.

    Election news: The Guild needs coordinators! If you'd like to help out, you may nominate yourself or any suitable editor—with their permission—for the Election of Coordinators for the first half of 2024. Nominations will close at 23:59 on 15 December (UTC). Voting begins immediately after the close of nominations and closes at 23:59 on 31 December. All editors in good standing (not under current sanctions) are eligible, and self-nominations are welcome. Coordinators normally serve a six-month term that ends at 23:59 on 30 June.

    Drive: Of the 69 editors who signed up for the September Backlog Elimination Drive, 40 copy-edited at least one article. Between them, they copy-edited 661,214 words in 290 articles. Barnstars awarded are listed here.

    Blitz: Of the 22 editors who signed up for the October Copy Editing Blitz, 13 copy-edited at least one article. Between them, they copy-edited 109,327 words in 52 articles. Barnstars awarded are listed here.

    Drive: During the November Backlog Elimination Drive, 38 of the 58 editors who signed up copy-edited at least one article. Between them, they copy-edited 458,620 words in 234 articles. Barnstars awarded are listed here.

    Blitz: Our December Copy Editing Blitz will run from 10 to 16 December. Barnstars awarded will be posted here.

    Progress report: As of 20:33, 10 December 2023 (UTC), GOCE copyeditors have processed 344 requests since 1 January, and the backlog stands at 2,191 articles.

    Other news: Our Annual Report for 2023 is planned for release in the new year.

    Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators Dhtwiki, Miniapolis and Zippybonzo.

    To discontinue receiving GOCE newsletters, please remove your name from our mailing list.

    Message sent by Baffle gab1978 using MediaWiki message delivery (talk) 20:54, 10 December 2023 (UTC)[reply]

    You've been mentioned at administrators' noticeboard

    Information icon There is currently a discussion at Wikipedia:Administrators' noticeboard/Incidents regarding an issue with which you may have been involved. Thank you. IOHANNVSVERVS (talk) 07:13, 13 January 2024 (UTC)[reply]

    Disambiguation link notification for January 18

    An automated process has detectedthat when you recently edited Revolution (2024), you added a link pointing to the disambiguation page Mike Bennett.

    (Opt-out instructions.) --DPL bot (talk) 05:50, 18 January 2024 (UTC)[reply]

    Happy Birthday!

    March 2024

    Information icon Hello, I'm Cassiopeia. I noticed that you added or changed content in an article, Dustin Poirier, but you didn't provide a reliable source. It's been removed and archived in the page history for now, but if you'd like to include a citation and re-add it, please do so. You can have a look at referencing for beginners. If you think I made a mistake, you can leave me a message on my talk page. Thank you. Cassiopeia talk 02:22, 4 March 2024 (UTC)[reply]


    Hi Sceptre, you are welcome to put back the info if you can provide independent, reliable source to support the claim for verification. Cassiopeia talk 02:23, 4 March 2024 (UTC)[reply]

    Guild of Copy Editors 2023 Annual Report

    Guild of Copy Editors 2023 Annual Report
    Our 2023 Annual Report is now ready for review.

    Highlights:

    • Introduction
    • Membership news, obituary and election results
    • Summary of Drives, Blitzes and the Requests page
    • Closing words
    – Your Guild coordinators: Dhtwiki, Miniapolis and Wracking.
    To discontinue receiving GOCE newsletters, please remove your name from our mailing list.

    Edelman Family Foundation

    Hi @Sceptre

    I am reaching out to you because of your previous participation in one of the discussions regarding the reliability and neutrality of HuffPost/Pink News/ProPublica as sources used on Wikipedia.

    Currently, there is an ongoing issue with the Edelman Family Foundation section in the Joseph Edelman Wikipedia article. The section appears to be biased and lacks a balanced representation of the foundation's activities, as it primarily focuses on a single controversial donation while neglecting to mention the organization's numerous other significant contributions to various causes.

    I would like to invite you to participate in the discussion on the BLP Noticeboard to address the concerns surrounding the section's neutrality and explore ways to improve its content. Llama Tierna (talk) 18:15, 1 April 2024 (UTC)[reply]

    Category:Wikipedia Good Article contributors

    Please would you update your relevant user sub-page from Category:Wikipedia Good Article contributors to lowercase? – Fayenatic London 14:11, 6 April 2024 (UTC)[reply]

    Sorry, I meant to Category:Wikipedia good article contributors – lowercase g too. – Fayenatic London 21:40, 7 April 2024 (UTC)[reply]

    Leeds Wikipedia meetup on Saturday 4th May

    Hello there! Interested in having a chat with fellow Wikipedians? There's a meetup in Leeds on Saturday 4th May 2024, at the Tiled Hall Café at Leeds Central Library.

    Full details here.

    You're receiving this one-off message as you're either a member of WikiProject Yorkshire, you've expressed an interest in a previous Leeds meetup years ago, or (for about 4 of you), we've met :)

    I plan to organise more in future, so if you'd like to be notified next time, please say so over on the meetup page.

    Please also invite any Wikimedia people you know (or have had wiki dealings with) – spread the word! Hope to see you there.

    Jonathan Deamer (talk)

    20:35, 7 April 2024 (UTC)

    Guild of Copy Editors April 2024 Newsletter

    Guild of Copy Editors April 2024 Newsletter

    Hello and welcome to the April 2024 newsletter, a quarterly digest of Guild activities since December. Don't forget you can unsubscribe at any time; see below. We extend a warm welcome to all of our new members. We wish you all happy copy-editing.

    Election results: In our December 2023 coordinator election, Zippybonzo stepped down as coordinator; we thank them for their service. Incumbents Dhtwiki and Miniapolis were reelected coordinators, and Wracking was newly elected coordinator, to serve through 30 June. Nominations for our mid-year Election of Coordinators will open on 1 June (UTC).

    Drive: 46 editors signed up for our January Backlog Elimination Drive, 32 of whom claimed at least one copy-edit. Between them, they copy-edited 289 articles totaling 626,729 words. Barnstars awarded are here.

    Blitz: 23 editors signed up for our February Copy Editing Blitz. 18 claimed at least one copy-edit and between them, they copy-edited 100,293 words in 32 articles. Barnstars awarded are here.

    Drive: 53 editors signed up for our March Backlog Elimination Drive, 34 of whom claimed at least one copy-edit. Between them, they copy-edited 300 articles totaling 587,828 words. Barnstars awarded are here.

    Blitz: Sign up for our April Copy Editing Blitz, which runs from 14 to 20 April. Barnstars will be awarded here.

    Progress report: As of 23:17, 11 April 2024 (UTC), GOCE copyeditors have processed 109 requests since 1 January 2024, and the backlog stands at 2,480 articles.

    Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from Baffle gab1978 and your GOCE coordinators Dhtwiki, Miniapolis and Wracking.

    To discontinue receiving GOCE newsletters, please remove your name from our mailing list.

    A continuous map f:X->Y between topological spaces is said to be null-homotopic if it is homotopic to a constant map

    Hello there.

    It's been a strange year. I let our relationship lapse and I'm sorry. It's mostly, but not entirely, because I abjectly refuse to use Discord anymore and I forgot my Matrix credentials.

    Email would be good. Jitsi coffee dates would be good. I still think of you. But if you don't want to anymore, I completely understand.

    Sasha foxxo (talk) 00:14, 28 April 2024 (UTC)[reply]

    Reminder to vote now to select members of the first U4C

    You can find this message translated into additional languages on Meta-wiki. Please help translate to other languages.

    Dear Wikimedian,

    You are receiving this message because you previously participated in the UCoC process.

    This is a reminder that the voting period for the Universal Code of Conduct Coordinating Committee (U4C) ends on May 9, 2024. Read the information on the voting page on Meta-wiki to learn more about voting and voter eligibility.

    The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members were invited to submit their applications for the U4C. For more information and the responsibilities of the U4C, please review the U4C Charter.

    Please share this message with members of your community so they can participate as well.

    On behalf of the UCoC project team,

    RamzyM (WMF) 23:10, 2 May 2024 (UTC)[reply]

    secondhand notification

    Per a request by SnowFire (talk · contribs), because of your participation in Talk:Michael Larson#Requested move 22 March 2024, you are being brought up to date on developments. After the article "Press Your Luck scandal" was written, "Michael Larson" was turned into a redirect. That redirect has since been undone (though mischaracterized as a "stealth copy & paste move"), and there are now two active discussions in which you may wish to participate, but might otherwise be unaware of:

    I'm certainly involved in these discussions and will be happy to converse with you there if you're inclined. My apologies if this is undue, but it was implied that I have been negligent in my canvassing. — Fourthords | =Λ= | 00:27, 4 May 2024 (UTC)[reply]

    WP:RMNAC explanations needed

    Sceptre, at Talk:1933 NFL Championship Game#Requested move 3 May 2024 and Talk:AFC Championship Game#Requested move 29 April 2024 you simply said "not moved", without saying how you weighed the arguments, and without indicating whether you saw a consensus for uppercase, versus no consensus. Could you please expand on those closing statements? Dicklyon (talk) 22:06, 11 May 2024 (UTC)[reply]

    @Gonzo fan2007: et al had the correct interpretation of MOS:SPORTSCAPS. The pre-Super Bowl championship games (and the conference championships, for that matter) are more often capitalised than not, especially as they're trademarked. Sceptre (talk) 23:56, 11 May 2024 (UTC)[reply]
    Will you be adding those rationales to the close statements, please? Dicklyon (talk) 02:54, 12 May 2024 (UTC)[reply]
    Interesting. Is NFL Draft trademarked? Not that I'd necessarily reopen that can of brain-worms (and, importantly, and unlike the conference championship games, uppercasing does not "lead" in its n-gram derby). Randy Kryn (talk) 04:02, 12 May 2024 (UTC)[reply]
    @Sceptre: I don't think the trademark rationale was used by anyone, was it? And I have some doubt whether it really is trademarked. Consider striking it from your close.—Bagumba (talk) 23:15, 14 May 2024 (UTC)[reply]
    Sceptre, I think I'll need to call a move review if you don't re-list these. Your reasoning sounds too much like a super-vote based on non-facts and unsupported opinions, as opposed to a reasonable weighing of the positions articulated. Dicklyon (talk) 23:19, 12 May 2024 (UTC)[reply]
    I see you haven't edited since before this; I'll be patient (sort of). Dicklyon (talk) 05:16, 14 May 2024 (UTC)[reply]
    @Dicklyon: Apologies, I was off-wiki yesterday. I've added the above rationale to each closure, but I strongly dispute the idea that they're supervotes. Sometimes, the consensus just isn't there. Sceptre (talk) 15:35, 14 May 2024 (UTC)[reply]
    Sceptre, I've no problem with your closures & will endorse them if they're challenged. But, I recommend that you elaborate on your closures at the two RMs, to avoid it being challenged. GoodDay (talk) 00:37, 13 May 2024 (UTC)[reply]

    Move review for AFC Championship Game

    An editor has asked for a Move review of AFC Championship Game. Because you closed the move discussion for this page, or otherwise were interested in the page, you might want to participate in the move review. Dicklyon (talk) 14:12, 15 May 2024 (UTC)[reply]

    Move review for 1933 NFL Championship Game

    An editor has asked for a Move review of 1933 NFL Championship Game. Because you closed the move discussion for this page, or otherwise were interested in the page, you might want to participate in the move review. Dicklyon (talk) 14:12, 15 May 2024 (UTC)[reply]

    It's nice to see that double standards are alive and well

    If this was an ordinary user that no one knew, they'd be blocked indef, no questions asked. Jtrainor (talk) 19:35, 7 September 2008 (UTC)[reply]

    • Yes, I do have sympathy for that view. However, we also have numerous previous examples of blocks being lengthened for sock-puppeting block evasion, both with "high profile" editors and others that "no one knew" as well. Black Kite 19:38, 7 September 2008 (UTC)[reply]
    Sceptre is not an ordinary editor that no one knows. Plain and simple. GlassCobra 19:41, 7 September 2008 (UTC)[reply]
    Agreed. Sceptre has made numerous positive contributions in multiple areas over a long period of time. That's worth making the investment in trying to turn things around, up to a point. IMHO anyway. ++Lar: t/c 19:48, 7 September 2008 (UTC)[reply]
    Where are people arguing that we don't have different standards for established users who have been with the project for a long time? I thought this was a well-known fact. Mr.Z-man 19:52, 7 September 2008 (UTC)[reply]

    (Not) resetting block to 3 months

    Unless anyone else has any major objections, and Sceptre is aware that any more socking will lead to an indefinite block, I am going to reset Sceptre's block to 3 months shortly. Black Kite 19:34, 7 September 2008 (UTC)[reply]

    Please don't. I see no consensus for anything, except possibly for a ban at this point. --MZMcBride (talk) 19:43, 7 September 2008 (UTC)[reply]
    I'm endorsing the 3 month--Tznkai (talk) 19:45, 7 September 2008 (UTC)[reply]
    I object too, and would rather support an indefinite block at this point. As much as I want to AGF, Sceptre has been given so many chances to reform yet has continued to be erratic and a net drain on the project. Jimmy Wales himself said in 2006, in an incident where Sceptre was harassing an underage female admin, "If he does ONE MORE LITTLE THING, he is gone from wikipedia *poof* just then, no arbcom, no nothing, just me banning him myself." He has done many more "things" since - I think the project has had enough. :/ krimpet✽ 19:47, 7 September 2008 (UTC)[reply]
    I'm still iffy on this as well. IF consensus shows that a 3 month block is accepted by most then I'll be fine with it, but right now I'm not sure yet. Wizardman 19:48, 7 September 2008 (UTC)[reply]
    Nope. Indef is totally appropriate at this point. Per Krimpet, etc. —Wknight94 (talk) 19:49, 7 September 2008 (UTC)[reply]
    • OK. Clearly no consensus at this time, so I will leave as indef, something I'm not unconvinced by myself anyway. Black Kite 19:51, 7 September 2008 (UTC)[reply]
    I object also. How many chances do we give him? He was indef blocked and then his block was reduced as a last chance. He has now used that last chance and still is unrepentant about why he was originally blocked. Why keep wasting our time? KnightLago (talk) 19:56, 7 September 2008 (UTC)[reply]
    I'm not positive, but I believe his last chance was given AFTER the sock edits but BEFORE they were discovered.--Tznkai (talk) 19:58, 7 September 2008 (UTC)[reply]
    Huh? The one sleeper sock was created and edited within the last few days. The sock that created that sock also edited on September 1. Sceptre's block log clearly says Moreschi's "Final chance" was in August. Which last chance were you referring to? —Wknight94 (talk) 20:20, 7 September 2008 (UTC)[reply]
    I'm not defending his drama-mongering or his mistakes, but some points. First off, what Jimbo says should not be any reason to conduct our affairs in dealing with users in any different way. We're the community; we decide. Secondly, I disagree with the assertion Sceptre is a "net drain"; he's nominated five successful AfDs and has been an extremely positive asset to Doctor Who. What I've urged everyone to do (and no one has listened) is to try and come to common ground on editors clearly intent on improving Wikipedia but who have caused drama in doing so (Sceptre, Giano, et al). This isn't just one editor, it's an offshoot of a continuing issue. I'm just hoping that we can address this so we don't waste our times in threads like these over each individual user. Also note per above Sceptre has good reason to want his talk and user page salted, as the trolls at Encyclopedia Dramatica already have a sizeable article on him and its unethical to provide them more ammunition. Der Wohltemperierte Fuchs (talk) 20:18, 7 September 2008 (UTC)[reply]
    First, let's not compare Sceptre to Giano. Giano has pointed out what he - and quite a few others - feel are injustices. If he wasn't so dramatic and biting in his choice of language, he'd get a lot more official support. Sceptre is turning out to be a vandal, a harasser, and an abusive block evading sockpuppeteer. No comparison. It's only now that he's been unmasked. Next, what good is there in deleting his user page? It's just a sockpuppeteer tag that helps the community here understand what happened. What information is contained there for ED? —Wknight94 (talk) 20:27, 7 September 2008 (UTC)[reply]
    (ec) That's interesting timing. I believe the "last chance" comment was placed at the end of a block log. I haven't seen any evidence that Sceptre was given the courtesy of being informed on his talk page that this was his last chance. I also don't think dredging up things from 2006 is completely fair, nor is appealing to Jimbo's authority. As can be seen above, Jimbo is quite capable of stepping in when he wants to. What I really want to see here is an acknowledgment from Sceptre that he really is going to step away from Wikipedia for a few months (it can be done, and I believe Sceptre has stated this), and then Sceptre make a statement after those three months in the form of a block appeal. This gives people here a chance to calm down as well. In principle, I think all indefinite or long-term blocks should be reviewed a few months later, merely because people may change opinions they expressed in the heat of the moment. Maybe what I'm arguing for is to leave indefinitely blocked, and to revisit it in three months time? People may feel differently then. Carcharoth (talk) 20:26, 7 September 2008 (UTC)[reply]
    The first thing I'm looking for is a slight hint of repentance. —Wknight94 (talk) 20:29, 7 September 2008 (UTC)[reply]
    You may not get that now, but you might in a few months. Would you be prepared to wait a few months to get a hint of repentence? Carcharoth (talk) 20:40, 7 September 2008 (UTC)[reply]
    • Endorse a reset. Frankly, anything that has been stated here is not even near bannable. The socks weren't abused. Normally, only the socks are blocked due to block evasion. — Edokter • Talk • 20:34, 7 September 2008 (UTC)[reply]
    • If the socks are productive, the master account is not blocked, and there's no abusive sockpuppetry, then you'd usually be right. When the master account is already blocked though, that's block evasion as well. Black Kite 20:40, 7 September 2008 (UTC)[reply]
    • And evading a two-month block before even a few days are gone is a very bad sign. —Wknight94 (talk) 20:42, 7 September 2008 (UTC)[reply]
    Two notes: 1 I believe I understand why sceptre wants his user page space to be deleted, and he has legitimate concerns for trolling, harassment, and other distress. 2. I propose that if Sceptre posts an apology for evading via sockpuppet, we move to a three month ban, courtesy blank his talk page with a block notice and sock notice hidden a layer deep, delete his user page, and move on with life.--Tznkai (talk) 20:43, 7 September 2008 (UTC)[reply]
    Disagree on both counts. His user page has a single edit in it. There is no information there. I didn't undelete the entire history of it. It's just a pointer with information that trolls already have anyway. Next, the blocks and past threats from Jimbo were all based on a common thread of immaturity and sneakiness. Those don't go away in three months. Three years maybe, but definitely not three months. —Wknight94 (talk) 20:49, 7 September 2008 (UTC)[reply]
    If what you say is true, then ban him again in three months. It takes twenty seconds.--Tznkai (talk) 20:53, 7 September 2008 (UTC)[reply]
    The one problem with that is the possible damage an unrepentent sockpupeteer might do. I'm not convinced though that Sceptre would do such damage. Carcharoth (talk) 20:58, 7 September 2008 (UTC)[reply]
    (ec) Wasn't the comment from Jimbo two years ago? But the real point here is that consensus is slowly moving towards a ban, and I think Sceptre is beginning to realise that. Why push for a ban immediately? If Sceptre reforms, that's a good result. If he doesn't, more people will support an indefinite block. If that's what you want, you'll get that eventually, but you don't have to get that immediately. A later indefinite block with firmer consensus is better than one now with opinion divided. Carcharoth (talk) 20:58, 7 September 2008 (UTC)[reply]
    • Endorse 3 month block but firmly opposed to making him grovel to get it. Shorten the block and indef him next time. He is annoying and immature but produces featured content is is a long term contributor. We really need to look for rehabilitation rather then restitution here. Spartaz Humbug! 20:51, 7 September 2008 (UTC)[reply]
    I endorse restarting the 2 month clock. Firmly opposed to seeking to get him to grovel. The original indef blok was way over the top. Kittybrewster ☎ 22:30, 7 September 2008 (UTC)[reply]
    I'd endorse resetting the two month clock, but tacking on a third month seems punitive. For somebody like Sceptre, who lives and breathes Wikipedia, two months is long enough (if he can actually bring himself not to continue socking). I think a reset of the two month clock is a good warning shot, and if he's caught socking again, he should be met with an indefinite block and a discussion regarding a community ban. - auburnpilot talk 00:19, 8 September 2008 (UTC)[reply]

    In case anyone doubted the elusiveness, a WR user noticed Sceptre welcoming and talking to himself - and not recently but four months ago. I'm actually embarrassed for him at this point. —Wknight94 (talk) 03:44, 8 September 2008 (UTC)[reply]

    • Consensus seem to have moved towards a 3 months block and away from an indef at this time. I'll change it round in a couple of hours unless there are further sustained objections. Spartaz Humbug! 05:29, 8 September 2008 (UTC)[reply]
      • It has? I only see a couple people who do so. You, Neil, Auburnpilot, Kittybrewster, and Edokter, since Krimpet's post. I don't see any consensus to change anything in any direction, be it towards a ban, or towards a 3 month block. ⇒SWATJester Son of the Defender 11:10, 8 September 2008 (UTC)[reply]
        • I have as well, as well as other endorsement on sceptre's talk page, and on the suggestions subsection of this topic.--Tznkai (talk) 11:21, 8 September 2008 (UTC)[reply]
      • Endorse a three month block. There's no reason to expect a "full, frank apology" or anything like that. If Sceptre chooses to provide one, great, but it should not be a condition. Neıl ☄ 09:01, 8 September 2008 (UTC)[reply]
    • I agree that ritual abasement is not required here. Guy (Help!) 11:30, 8 September 2008 (UTC)[reply]

    Consensus Estimate

    This is my attempt at seeing of the people who have commented here, who thinks what. Feel free to correct. --Tznkai (talk) 13:46, 8 September 2008 (UTC)[reply]

    • This like consensus to chortern the block but I have not enacted this to allow for further comment and discussion. there is no deadline. Spartaz Humbug! 14:02, 8 September 2008 (UTC)[reply]
    Perhaps more definitively, it looks like a lack of consensus to maintain the indefinite ban. To avoid a wheel war, I can enact whatever remedy is required.--Tznkai (talk) 14:06, 8 September 2008 (UTC)[reply]
    Yep, sounds good. Throw in a trout slap for talking to his own sleeper sock and I'm good with either two- or three-month. —Wknight94 (talk) 14:43, 8 September 2008 (UTC)[reply]

    Rescind indefinite ban

    • tznkai - Open to Two month or three month ban(Note: Blocking admin for most recent block)
    • Carcharoth - Supports two month block, open to three month block, further evasion causes indefinite
    • Naerii - Supports three month block, further evasion causes indefinite
    • Philknight - supports three month block, further envasion causes indefinite
    • User J - supports three month block, further envasion causes indefinite
    • Kitty brewster - supports three month block, supports two month block
    • Edoker
    • Spartaz - supports 3 month block, "opposed to seeking to get him to grovel"
    • auburn pilot - supports 2 month block, does not support 3 month block, further envasion causes indefinite, consider community ban
    • Niel - supports 3 month block
    • Risker - supports 3 month block

    Maintain indefinite ban

    • Krimpet
    • Wknight - Waiting for an apology/ some sign of repentance
    • KnightLago

    Other

    • "For the record, I still believe that the initial ban for those "harassing" edits was totally overblown in the first place. user:Everyme 18:02, 7 September 2008 (UTC)"
    • "Agreed. Sceptre has made numerous positive contributions in multiple areas over a long period of time. That's worth making the investment in trying to turn things around, up to a point. IMHO anyway. ++Lar: t/c 19:48, 7 September 2008 (UTC)"
    • "I'm still iffy on this as well. IF consensus shows that a 3 month block is accepted by most then I'll be fine with it, but right now I'm not sure yet. Wizardman 19:48, 7 September 2008 (UTC)"
    • "OK. Clearly no consensus at this time, so I will leave as indef, something I'm not unconvinced by myself anyway. Black Kite "
    • "I agree that ritual abasement is not required here. Guy (Help!) 11:30, 8 September 2008 (UTC)"

    changes to the templates for Birth/Date age - Still unreseolved

    I previously wrote up this issue and it was archived without resolution so I am writing it up again. The linking for birth date and age templates has been removed which is causing the dates to not link within templates., Infobox military person for example. Although I see under the WP:Dates where someone changed the wording I cannot see where the change was determined through discussion or consensus and therefore should be corrected. If the decision is to not link dates in general fine but it should still be linked in templates such as infoboxes. Additionally,if this is the desire is to not link dates then the bots and AWB that correct dates need to be reviewed (because they are still changing date formatting) and the millions of date links on pages that currently exists needs to be removed. Until somone can show me where this has been changed based on a majority decision and not just a user thinking that its wrong then I am going to continue linking dates.--Kumioko (talk) 17:48, 7 September 2008 (UTC)[reply]

    Ask User:Tony1. He has a page explaining where consensus was reached. See User:Tony1/Information on the removal of DA. Earlier thread was here. Carcharoth (talk) 17:54, 7 September 2008 (UTC)[reply]
    Does he plan to delete all the month/day/year pages once they are completely orphaned? Seriously, what is the point of all this? — CharlotteWebb 20:40, 7 September 2008 (UTC)[reply]
    That point did strike me as well. There must be some cases where we link to years. I suppose from calendars and timelines rather than articles? And from timelines within articles. I think the point is that linking a year is OK, but linking the date and month is pretty pointless. Though knowing all the instances when a date is mentioned in Wikipedia could be useful in some circumstances. But that more linking dates for the sake of using the "what links here" function. We also have "x in year" articles. Tony's argument that there is vast amounts of overlinking is valid as well, and particularly the point that unregistered readers see a mess (though I thought everyone knew that already - I think half the people that create accounts do so in order to improve their reading experience and to access the reading preferences such as 'skins'). Carcharoth (talk) 20:46, 7 September 2008 (UTC)[reply]
    Although I see Tony's point I do not agree that not linking dates at all is the answer and it seems as though he has become the defacto owner of the date formatting for wikipedia. I have reviewed his comments as well as the comments of the supporters and opposers and here are some things that I notice/concerns that I have:
    1. The Opposers and the supporters all have a good point but the supporters opinions seem to be favored heavily.
    2. Tony's page states that the majority support it but when you look at the vote it didn't clearly define support and the number of users who voted was relatively small.
    3. There are bots and apps tat edit dates on pages that need to be modified.
    4. There are millions of date links that need to be unlinked if this is kept.
    5. There are hundreds of date pages that will need to be deleted if this is kept.
    6. I believe that a change like this that affects so many pages and edits should have had more publicity before it was implemented.

    --Kumioko (talk) 21:51, 7 September 2008 (UTC)[reply]

    Part of the problem here is that this debate has been going on for years and has taken place in an enormous number of different places, too many to be easily linked to. In 2006 the whole thing blew up into a wheel war, see relevant block logs. Tony has been consistent and persuasive, and I think he's (probably) right that the significant opposing viewpoints have been answered to the satisfaction of a majority of those who have followed the debates all along. Of course, since this debate affects basically every article and (as you note) a great many templates as well, lots of people are going to notice the actual changes who were not aware of the debate, no matter how well it's publicized. But in this case, consensus of everyone whose watchlisted pages would be affected would be simply impossible (since that's all editors), and there has to be some kind of move forward at some point. Like you I see both sides here, but I also see the downside of continuing the debate for, oh I don't know, another three years. . . Chick Bowen 05:38, 8 September 2008 (UTC)[reply]
    In those earlier debates, was the issue of "what is the purpose of year, month and date articles", addressed, and whether such articles should ever be linked and if so from where? Carcharoth (talk) 07:29, 8 September 2008 (UTC)[reply]
    The links to such pages are only to be removed where they serve no purpose. Where they serve a purpose they will remain. Therefore, the pages will remain, since consensus is that there is a purpose to having on this day in history pages and chronology pages. Hiding T 09:25, 8 September 2008 (UTC)[reply]
    • Response to CharlotteWebb et al.: If all or even a tiny proportion of year-pages were like 1345, we'd be putting them up as FACs, highlighting them in The Signpost and generally being rather proud of them. But they're not like that: I recently surveyed a sample right back to pre-christian days and found them to be most unsatisfactory stubby, fragmentary lists. But even if year-pages were worthy of proper articles/lists, there's an insuperable problem: they provide information about a whole year for the whole planet, and by definition are hard to justify as links that add significantly to the understanding of a topic at hand. If there's one relevant fish in the ocean of a year-page (that is, one that is not just a stubby little collection of one-line statements, it would always be better in the article itself. Year-pages are actually a great idea for something quite different: diversionary browsing. While many editors work to discourage enticements to divert from our focused article through year-links, if more year-pages could be worked up into good articles, I'd be the first to promote them in their own right as worthy for a certain class of reader. There's the challenge.
    • Response to the issue of autoformatting dates in templates: This is quite a different issue from the linking of years and other chronological items. It's simple: templates that generate dates need to (1) avoid linking them and (2) allow editors to choose between the two standard formats, US and international (some citation templates seem to like ISO, which is permitted in ref lists). This arises from major changes to long-standing practice, in MoS (main), MOSNUM, MOSLINK and CONTEXT last month.Tony (talk) 10:36, 8 September 2008 (UTC)[reply]

    Cluebot reverts valid edit but its PHP page to revert invalid reverts is broken

    I attempted to inform Cluebot that it had made a false revert but on submitting my report at http://24.40.131.153/cluebot.php the response page showed just:

    > POST: http://en.wikipedia.org/w/api.php?action=login (0.239742040634 s)
    > GET: http://en.wikipedia.org/w/query.php?what=content&format=php&titles=User%3AClueBot%2FFalsePositives%2FReports (0.188697814941 s)
    > Warning: Invalid argument supplied for foreach() in /home/apache2/domains/default/htdocs/wikibot.classes.php on line 78

    While it says warning rather than error it's hardly the kind of response that would lead one to believe one's submission had been successfully made.

    I was making the report as cluebot reverted my revert of a huge number of edits (over 150) made by Arilang1234 to the article Boxer Rebellion in the last 4 days. My explanation of my actions in my Cluebot report were as follows:

    "This looks like a mass delete but I am reverting over 150 revisions made by Arilang1234 between the 3rd and 7th of September. While not simple childish vandalism these revisions are bizarre and are not the stuff of a coherent Wikipedia piece. Some of it appears scholarly but in fact reflects the personal assertions of an individual (on dates etc.) rather than established historical fact, some reflects non-mainstream opinion on historical events and groups and most is just rambling and irrelevant." 84.74.150.48 (talk) 17:49, 7 September 2008 (UTC)[reply]

    It should be fixed now. It wasn't really even broken, it just wasn't posting it to User:ClueBot/FalsePositives, but it still records the information to the server. -- Cobi(t|c|b) 18:00, 7 September 2008 (UTC)[reply]

    STILL at it.

    Resolved
     – blocked. — Coren (talk) 12:26, 8 September 2008 (UTC)[reply]

    Please refer to [50], above.

    This morning I left a note on blocked user Andy Bjornovich's talk page with concerns that he was continuing to edit using IP 212.159.64.14. This IP was only editing user and talk pages, but I still felt that, with 2 days left of his block, this was unnecessary (it's worth noting that another admin disagreed).

    Just now, however, I noticed another edit to Andy's user page, this time by a different IP. I checked that IP's contributions only to discover 5 article space edits from this morning, so I left a message on Andy's talk page requesting clarification. Following another edit, this time to a template, I have indefblocked 79.73.71.54 for evading a block.

    Andy has just admitted he is using that IP. I have therefore indefblocked his other IP as well.

    Now I propose to increase Andy's original block (already his second) for this evasion. I'd like recommendations on the increase: are we going to give this clearly problematic user yet another chance, or just say goodbye? Exploding Boy (talk) 18:04, 7 September 2008 (UTC)[reply]

    Wait, you indefblocked two IPs? Are they static? J.delanoygabsadds 18:06, 7 September 2008 (UTC)[reply]
    The blocks can easily be changed. I indefblocked for the very reason that the block is...indefinite. Exploding Boy (talk) 18:08, 7 September 2008 (UTC)[reply]
    On reflection, I've reduced the blocks on both IPs to 3 hours. That should give us enough time to discuss what to do with Andy. Exploding Boy (talk) 18:17, 7 September 2008 (UTC)[reply]
    This started with Wikipedia:Administrators' noticeboard/Archive166#User signature. Based upon that incident and the conduct since, I believe an indef block is now warranted. We have already been excessively polite and patient with this user, but there has been no improvement in their behavior or attitude. It's time to move on. — Satori Son 18:26, 7 September 2008 (UTC)[reply]

    With this editor I'm continually going back and forth between whether he's just not getting it, or deliberately trying to test others' boundaries. Even though today's IP edits from 79.73.71.54 were innocuous (except for this one maybe-- does anybody know what this is?). My suggestion would be a last warning to AB with indef ban immediately upon any further edit. At some point, disruption is disruption, regardless of whether the editor seems well-intentioned. justinfr (talk/contribs) 18:32, 7 September 2008 (UTC)[reply]

    This edit is especially strange. justinfr (talk/contribs) 18:33, 7 September 2008 (UTC)[reply]
    Just for clarity, 5 edits from that IP today are to article space, and this user is currently blocked. Exploding Boy (talk) 18:34, 7 September 2008 (UTC)[reply]
    To clarify my comment too--sorry, yes, I think this is a definite problem. The userspace edits and bizarre comments (e.g., [51]) make me think he just doesn't get that he's not supposed to edit at all, under any form, during this. Maybe I'm being naive though. If the consensus is that we've given enough warning I have no problem with that too. justinfr (talk/contribs) 18:39, 7 September 2008 (UTC)[reply]
    And to add a little more weirdness, please see this latest edit by Andy in which he admits to editing article space and says he's incompetent (!??) Exploding Boy (talk) 18:50, 7 September 2008 (UTC)[reply]
    • I'd support a reset of the original block, per WP:EVADE, which seems pretty straightforward. I don't see a very good benefit/drama ratio in extending the block to indef. If I am dead wrong about this, then I think we need to consider updating WP:EVADE to reflect what the community considers appropriate in such circumstances. SHEFFIELDSTEELTALK 19:54, 7 September 2008 (UTC)[reply]
    I agree, WP:EVADE seems quite clear, so reset. I don't think his IP edits were 'blockable behaviour' on their own. justinfr (talk/contribs) 20:07, 7 September 2008 (UTC)[reply]
    Per WP:EVADE the block should be reset. But there's the additional question of whether these edits by this user (whose behaviour has been problematic from the outset and continues to be problematic, and who has already been indefblocked once), along with all his previous edits and the pages of discussion they've generated, should be taken as evidence that he will likely never be able to participate in the project without being disruptive. I'm inclined to believe that they should, especially since even now (at least as of his last edit) he believes that it was acceptable to use an IP to edit article space while blocked. Exploding Boy (talk) 20:55, 7 September 2008 (UTC)[reply]
    Exactly right. This violation of WP:EVADE is only the latest one symptom of a much larger issue. When the totality of this user's contributions are considered (and I encourage those who haven't to carefully look at each and every one), then an indef block is entirely appropriate. — Satori Son 02:50, 8 September 2008 (UTC)[reply]
    Whilst I was favorable to initial attempts at making this user understand the basic rules of Wikipedia, it has become apparent that his agenda is not compatible with writing an encyclopedia. When he's not being insulting, he willfully tries to work around very explicit and very simple rules, or makes "humorous" edits. He's not here to write an encyclopedia, and has been given numerous warnings and a few last chances by patient admins.

    I'm blocking indef; if there is another admin who feels up to setting him up for some sort of mentoring in a strict framework, feel free to take over but I would expect any further time spent on that user is time wasted. We've already collectively lost hours dealing with someone who behaves in very bad faith (his claims of Asperger's are particularly inane, for instance, especially as some sort of excuse for his disruptive behavior). — Coren (talk) 03:48, 8 September 2008 (UTC)[reply]

    I fully endorse this indef block. Exploding Boy (talk) 04:01, 8 September 2008 (UTC)[reply]
    I know this is resolved, but I want to add this. Aspergers does make some one unwillingly and unwantingly stubborn. But it in no way makes some one ignorant to the rules. It can cause confusion of the rules if they are vague. But saying Wikipedia's rules are vague is like saying Duke Nukem Forever will come out in our lifetime. It just isn't true. Rgoodermote  15:43, 8 September 2008 (UTC)[reply]

    Contracted editing

    Earlier I deleted James F. Reda & Associates, LLC which had been created first by the now blocked JFredaLLC (talk · contribs · deleted contribs · page moves · block user · block log) and then by Swiggins2 (talk · contribs · deleted contribs · page moves · block user · block log). The first first creation was deleted by Jj137 (talk · contribs) as spam followed by a username block. I deleted it a copyright violation from here.

    I now get an email from the user which indicated that they are the webmaster and creator of the companies website. They also indicate that they are "...contacted by this company to add the material..." and they have released the material under the GFDL.

    Normally I'd just point them to the contact at Wikipedia:Requesting copyright permission and keep an eye on it. However, the "contacted by this company" bothered me. I read this, perhaps incorrectly, to read "paid to edit", and, if so, should they just be blocked. CambridgeBayWeather Have a gorilla 18:07, 7 September 2008 (UTC)[reply]

    Their company's google results list dozens of self-generated sites, making me believe they're just trying to advertise in as many ways as possible. That being said, why don't we refer them to the process at Wikipedia:BFAQ#COMPANY? We'd also need assurances that they're not account sharing. justinfr (talk/contribs) 19:35, 7 September 2008 (UTC)[reply]
    I think I agree there -- they're more than likely just trying to advertise as much as they can. I may be wrong, but if they're being paid to edit (which is kind of pointless), I'm pretty sure they're just advertising. I have no idea whether or not Swiggins2 is the same person, but considering his first edit was recreating that article (and I hadn't blocked account creation on the first block), it makes me a bit suspicious.   jj137 (talk) 20:41, 7 September 2008 (UTC)[reply]

    Usually even G11-like content released under the GFDL isn't suitable in tone (I've marked it before), but I was pleasantly surprised to see that it wasn't too terrible. Most of it is unusable, but the remaining useful paragraph requires a little cleanup. hbdragon88 (talk) 20:59, 7 September 2008 (UTC)[reply]

    However, the parts that were a copyvio are still listed on the above linked page as "© 2008 James F. Reda & Associates, LLC". The editor either needs to adjust the James F. Reda site to confirm that the material is released under the GFDL or contact the permissions, which I did point out to him. CambridgeBayWeather Have a gorilla 01:04, 8 September 2008 (UTC)[reply]

    Evasion of AfD results by Le Grand Roi des Citrouilles

    The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
    All articles speedied except for Weapons of Gears of War, which there is a running AFD on because it is significantly different than the previously deleted content. LGC blocked 24 hours due to edit-warring on this page.--chaser - t 19:17, 7 September 2008 (UTC)[reply]

    Le Grand Roi des Citrouilles (talk · contribs) has begun to move articles, which were apparently userfied for him by kindly administrators after they were deleted at AfD, back into mainspace as redirects. I've only checked one of them at all carefully—List of fictional aircraft in Ace Combat, which was deleted per this AfD and the history of which LGRdC moved into mainspace as a redirect to List of nations of Ace Combat, with the edit summary "Creating redirect following discussions to merge and redirect". I can find no DRV discussion of the deleted article or any other "discussions to merge and redirect"; nor can I find any evidence that LGRdC has merged any material to the article that's the target of the redirect. This, and his other recent moves of userfied material, seem to be nothing more than end runs around AfD consensus in an effort to get the articles' histories back into mainspace. I have no idea how this matter can or should be dealt with; but the editor in question will clearly do anything in his power to disrupt and negate the AfD process, and it seems to me that something needs to be done here. Deor (talk) 18:11, 7 September 2008 (UTC)[reply]

    I'm inclined to tenuously assume good faith. LGRdC seems about to invoke his right to vanish and is clearing out various user pages. One relatively easy(?) solution might be to delete the histories of these moved articles and restore the redirects he's created. If under a new identity he wants to start/resume working on these materials, he can request an admin. restore the edit history to his user space. In the meantime, Le Grand, rather than creating redirects and moving them to article space, it would be a sign of good faith if you were simply to go to the mainspace area and create the redirect there atop the redlink. Then just request db-user for those articles sitting in user space.
    Meanwhile, though, someone might want to "help" LGRdC with this limbo-RTV status. He twice blanked this section and posted to Deor's talk page citing RTV and harassment as a reason not to write to/about him -- yet LG continues to participate in AFDs, posted welcome messages, etc. Something about cake and eating it. I dunno. --EEMIV (talk) 18:31, 7 September 2008 (UTC)[reply]
    All right, LGRdC has now blanked this thread for the fifth time. I'm now requesting that the account be blocked for a 3rr violation. This thread wasn't indended to be about him so much as about what to do with the redirects he created, but it's becoming personal. Deor (talk) 18:46, 7 September 2008 (UTC)[reply]
    Are you sure you want to go that route? You initiated the thread (which for some people counts for 3RR) and you've restored it three times. That is effectively adding the same (or similar) content four times. Why not talk to LGRdC about this? The thread can be restored later if needed. Carcharoth (talk) 18:51, 7 September 2008 (UTC)[reply]
    (ec)I left a stern warning on LGRdC`s talk page. If he choses to ignore that, then so be it; however unless that happens, I am not willing to block him yet. --Kralizec! (talk) 18:53, 7 September 2008 (UTC)[reply]
    (edit conflict x2)I've already blocked LGRdC for edit warring (he claims to be invoking RtV on an account "not used in many months," a falsehood, since he's edited actively until today) - however, I also caution Deor not to fuel the flames of edit warring like this in the future. krimpet✽ 18:55, 7 September 2008 (UTC)[reply]
    Carcharoth, I don't know how familiar you are with LGRdC communication habits, but it sounds like you never tried to actually talk commonsense with him. He regularly blanks and stonewalls or otherwise disrupts everything that is in the slightest critical of any of his actions. Moreoever, Kralizec is right that RTV does not include the right to remove this section from AN. user:Everyme 19:07, 7 September 2008 (UTC)[reply]

    (outdent) To the best of my knowledge, blanking other users' discussion-page comments falls within the definition of vandalism, and reverting such blanking (as I was only one of three editors to do here) can hardly be considered edit warring. Anyone have any ideas about what to do with the deleted articles that LGRdC has placed in mainspace? Deor (talk) 19:06, 7 September 2008 (UTC)[reply]

    I tagged three Ace Combat-related "deleted" articles for speedy since they included AfDed edit history; PhilKnight erased them. The other things he's created, as far as I can tell from the article history, are just redirects he made in user-space and moved to article-space. So, the AfD-evading thing I think is settled, unless I missed an article/history. --EEMIV (talk) 19:11, 7 September 2008 (UTC)[reply]
    The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

    Question regarding non admin closure of AFD

    Is there any issue with myself closing AFD's as no consensus or any other close other than delete? This is more of a sanity check, I want to check my thinking. NonvocalScream (talk) 19:56, 7 September 2008 (UTC)[reply]

    • WP:NAC is clear; Non-admin closures of XfDs should be limited to the following types of closures:
    • Unanimous or nearly unanimous keep after a full listing period absent any contentious debate among participants.
    • Speedy keep closures, per the criteria at that guideline.
    • Snowball clause closes, where it is absolutely obvious that no other outcome other than keep is possible.
    • Pure housekeeping, such as closing a debate opened in the wrong place, or where the page under discussion has been noncontroversially speedy deleted, yet the debate is not closed.
    • Now NAC is an essay, however I don't see many situations where it would be wrong.
    Black Kite 20:01, 7 September 2008 (UTC)[reply]
    • If as a non-admin you wish to close AfD's as no consensus you are free to do so. Just ignore that rather patronising essay. RMHED (talk) 20:10, 7 September 2008 (UTC)[reply]
    I thought Hammer was correct to reopen this AfD. The others you did today were ok. PhilKnight (talk) 20:17, 7 September 2008 (UTC)[reply]
    Yeah, I had Hammer give it a second look on IRC, we decided that relisting it won't hurt a thing. NonvocalScream (talk) 20:20, 7 September 2008 (UTC)[reply]
    Exactly. The burden of correcting a bogus keep/merge/noconsensus/wrongvenue closure is an order of magnitude less than correcting a bogus delete closure (because the latter requires admin rights and is unfortunately considered "wheel-warring" until proven innocent). — CharlotteWebb 20:27, 7 September 2008 (UTC)[reply]

    When in doubt, non-admins should not close AfDs unless the consensus is obvious. Wizardman 20:23, 7 September 2008 (UTC)[reply]

    Why? NonvocalScream (talk) 20:25, 7 September 2008 (UTC)[reply]
    Because there is no desysopping to threaten them with if they screw up (duh... ). — CharlotteWebb 20:27, 7 September 2008 (UTC)[reply]
    They haven't gained community trust most of the time, ergo I'd be uncomfortable with them closing afds. (Plus, a lot of them have failed RfAs, which shows a lack of community trust.) Wizardman 20:28, 7 September 2008 (UTC)[reply]
    Also, (not in reference to you because you're a former admin and I'm sure you'll get them right) there have been a number of cases where non-admins have closed non-obvious AfDs and got them wrong, which wastes everyones time. If there's not a horrible backlog (which there isn't at the moment), I don't see the point. Black Kite 20:30, 7 September 2008 (UTC)[reply]
    What a ridiculous answer, closing an AfD as No consensus is no big deal. Deleting is the big deal and that is where the trust is required. RMHED (talk) 20:32, 7 September 2008 (UTC)[reply]
    Uh, no consensus is a big deal. That's an interpretation in and of itself, as other admins could see a case as no consensus where others see delete. Wizardman 20:33, 7 September 2008 (UTC)[reply]
    Not ridiculous in the slightest. There are plenty of AfDs which appear to be "no consensus" through a simple vote-counting exercise, but which aren't for various reasons. Getting a N/C wrong and ending up with another AfD is just as timewasting as getting a Delete wrong and ending up with a DRV. Black Kite 20:43, 7 September 2008 (UTC)[reply]
    You make it sound as if judging consensus requires the wisdom of Solomon, it really really doesn't. If it did 99% of our administrators would be in deep shit. RMHED (talk) 20:54, 7 September 2008 (UTC)[reply]
    No, of course it doesn't, you're right. On the other hand, I'm just uncomfortable with the idea of hordes of people trying their hand out at random AfD closing, because I've seen too many examples of people getting it wrong. Black Kite 21:00, 7 September 2008 (UTC)[reply]

    If the outcome would be either nebulous to determine or controversial, I would be fine with a non-admin closing the debate if he conferred with an administrator or two, just to be sure of his judgement. —Animum (talk) 20:32, 7 September 2008 (UTC)[reply]

    So long as the closing non-administrator has clue aplenty, I am happy with him or her dabbling a toe in "no consensus" deletion discussion closures. I advise an abundance of caution to be used when making these closures, however: I've seen contentious non-administrator closures result in some nasty head-biting in the past (mostly justified—non-sysop closures have been known to go poorly—and sometimes not). It's your head; you decide whether it goes on the plate or not! Anthøny ✉ 20:36, 7 September 2008 (UTC)[reply]
    I vaguely recall that when you got into trouble as an admin it was over exercising judgement in controversial areas. I'd avise you to steer clear but, as the man said, its your head and lots of people (not me) will be watching to catch any mistakes for you. Spartaz Humbug! 21:04, 7 September 2008 (UTC)[reply]
    Yeah, I see one DRV where I closed an AFD that I voted in (what was I thinking?) and one AFD that I improperly applied BLP. I learned from those, and don't intend to close any controversial AFD's. NonvocalScream (talk) 21:08, 7 September 2008 (UTC)[reply]

    Summary

    So basically what I get from the above is "Do what you think you can handle, we will let you know if you get it wrong". Is this correct? NonvocalScream (talk) 21:03, 7 September 2008 (UTC)[reply]

    I don't think its that cut and dried. Spartaz Humbug! 21:05, 7 September 2008 (UTC)[reply]
    More like "if it has any possibility of being contentious, avoid it", I think. Black Kite 21:08, 7 September 2008 (UTC)[reply]
    Black kites works for me. NonvocalScream (talk) 21:29, 7 September 2008 (UTC)[reply]
    I used to close AfD's during my downtime at work and found it incredibility frustrating. On the one hand you have users who are much too wrapped up in the outcome of a deletion discussion; once they catch wind that you are not an admin, and then it's all "rv - Oh no you did-n't, you’re not even an admin!" On the other hand, you have certain admins who feel that their RfA somehow uniquely endows them with the ability to make an intelligent determination of consensus, who like to bowbeat you with WP:NAC for their own amusement. Never will anyone point to a problem with the actual close itself, only that it was a non-adminstrator who did the legwork. It’s infuriating, and in your specific case and obvious qualifications I imagine it would only be especially so.
    If you do decide to put up with it though, I’ve successfully closed several debates as delete. Just slap a {{db-xfd}} on the target article and a sensible admin will come along to delete it eventually. HiDrNick! 12:13, 8 September 2008 (UTC)[reply]
    I agree mostly w/ Dr. Nick here. NAC's help the backlog a lot, but they can generate stress. People get REALLY caught up in the outcome and will come banging on your door if you "mess it up" (give them an outcome other than the one they were looking for). further, closing a LOT of deletion debates will make later attempts to become an admin pretty miserable. Protonk (talk) 14:37, 8 September 2008 (UTC)[reply]

    Seen this?

    Consider me chastised if I'm in the wrong place, but have you seen Kerala tourism lately? Kaiwhakahaere (talk) 20:08, 7 September 2008 (UTC)[reply]

    Hey, what is going on here. I just checked and it's ok. Ten minutes ago when I went to the article it had a large photo of McCain on it, accross the actual Kerala page. I saved it as a web archive if anyone is interested. Kaiwhakahaere (talk) 20:13, 7 September 2008 (UTC)[reply]
    That was likely transclusion vandalism, which can be fleeting. Gwen Gale (talk) 20:16, 7 September 2008 (UTC)[reply]
    (ec)There has been some template vandalism involving a picture of an old man, I suspect this is what happened here. There is a report at AIV about it. DuncanHill (talk) 20:17, 7 September 2008 (UTC)[reply]

    Review

    With regards with the tools, I've requested feedback here. Comments are welcome. NonvocalScream (talk) 21:28, 7 September 2008 (UTC)[reply]

    User:Bandsofblue

    First, please see this past thread where I noted User:Bandsofblue (who has been indef blocked from vandalism) was using his talk page to create fake results from various reality TV shows on their talk page, fills them all up and then deletes and restarts a few days later. The worst I think the user could be doing is tracking a fantasy league or something like this around these elements, which would violate the appropriate use of userspace.

    Basically, the user is back at it again modifying their talk page. Again, this may not be harmful, but as I've not yet cleaned out the entry on my watchlist, its hard not to notice. I dunno what can be done short of completely blocking the account; the last time the edits were reverted and deleted but that only seems to be a pattern that will keep on going. --MASEM 23:29, 7 September 2008 (UTC)[reply]

    Re-deleted and re-protected. The account has actually been blocked since 7 December 2007, so there's no need to allow this to continue. - auburnpilot talk 00:10, 8 September 2008 (UTC)[reply]

    User:Screambloodygore667

    Judging by his userpage where he encourages vandalism and his contributions [52] which often consist of curse filled furors in all caps (Example being his edits to Talk:Music [53] ), I'd say this is a troll account. Zazaban (talk) 00:24, 8 September 2008 (UTC)[reply]

    I've notified the editor in question about this discussion. - Revolving Bugbear 00:36, 8 September 2008 (UTC)[reply]
    And I've left him a message asking him to remain civil. Exploding Boy (talk) 00:38, 8 September 2008 (UTC)[reply]
    Keep an eye on him, he's here to 'uphold the glory of metal', which is rarely a good thing. Zazaban (talk) 00:44, 8 September 2008 (UTC)[reply]
    ...Yes. But maybe he can uphold metal's glory while being civil and non-disruptive. Exploding Boy (talk) 00:47, 8 September 2008 (UTC)[reply]
    In my experience, that is never the case. Zazaban (talk) 00:49, 8 September 2008 (UTC)[reply]
    ...In which case we can uphold the glory of Wikipedia by blocking him. Civilly, of course. Exploding Boy (talk) 00:54, 8 September 2008 (UTC)[reply]
    Agreed. Zazaban (talk) 00:55, 8 September 2008 (UTC)[reply]
    (ec)Please give him a break. Way down at the end of his userboxes, he claims to be a liberal and a Christian Democrat so I hardly think he's into biting the heads off bats, drinking the blood of virgins, or really challenging the natural order of things. He will discover the joys of Mozart and Beethoven in all good time. --Rodhullandemu 00:57, 8 September 2008 (UTC)[reply]
    Well according to a university in Scotland his Mozart and Beethoven days may come sooner than expected. As the article explains, Screambloodygore667, is just a gentle, creative persom who is at ease with themselves. CambridgeBayWeather Have a gorilla 01:08, 8 September 2008 (UTC)[reply]
    Hey, Rock is my favourite genre, I think the Music article is really crappy, I'm not some sort of classical elitist, don't get me wrong. Zazaban (talk) 01:15, 8 September 2008 (UTC)[reply]
    None of this is relevant. Is he being disruptive, or do you just not like his tastes in music? - Revolving Bugbear 01:47, 8 September 2008 (UTC)[reply]
    Hey, I actually quite like Metal. As I explained in my first post, he's been ranting and raving and cussing and generally being disruptive. Zazaban (talk) 02:02, 8 September 2008 (UTC)[reply]

    Political positions of Sarah Palin

    Protection is about to expire on the above article. I've laid out suggested ground rules on the talk pages for conduct. In addition, I am recommending here that uninvolved administrators use very short (15 minutes) blocks and page protections to force users to discuss issues with each other on the talk page.--Tznkai (talk) 01:33, 8 September 2008 (UTC)[reply]

    Protection on the article expires in two weeks; it's not "about to expire". Gary King (talk) 01:44, 8 September 2008 (UTC)[reply]
    Whoops. Downgraded the protection now anyway.--Tznkai (talk) 01:48, 8 September 2008 (UTC)[reply]

    Administrative action review: Tznkai

    Tznkai appears to be using his position to POV push and support those who do. I am requesting that User:Jossi be the admin there as he seems to really have a handle on NPOV. Tzanki is apparently not swayed by argument about NPOV. Booksnmore4you (talk) 15:35, 8 September 2008 (UTC)[reply]

    I'll note for the record I havn't made a single content edit to the article. I have made no ( that I can remember anyway) content suggestions on the talk page. I have warned Books repeatedly about violating 3RR, and less so, civility issues. I stand by my actions, which are available for anyone curious. --Tznkai (talk) 15:40, 8 September 2008 (UTC)[reply]
    @Booksnmore4you: Thread with care while you learn the ropes and please Assume good faith. You are welcome to may disagree with Tznkai actions, and best would be to address your concerns directly with him in his talk page. ≈ jossi ≈ (talk) 15:45, 8 September 2008 (UTC)[reply]

    The Little Mermaid: Ariel's Beginning

    The way I understand it, when listing out actors for a cast list, they should be placed in order of importance, or in order of the film's credit listing. User talk:Iluvteletubbies‎ persists in re-ordering the cast list of The Little Mermaid: Ariel's Beginning in (their own words): "To make it easy to read.Puting it in order by smallest to largest,which I'm doing right now." I've raised the issue on the user's talk page, and already reverted their edits twice, so I cannot revert again. Thoughts? Annie D (talk) 01:37, 8 September 2008 (UTC)[reply]

    Where did you find that at? (The way cast lists ought to be?) Wikipedia:WikiProject Films/Style guidelines doesn't list that, nor does the Template:Infobox Film documentation. At least, not that I can see on a cursory first pass of each. I wouldn't say you're wrong per se, but I don't see cast list order as something to push 3RR over, IMVVHO. Will the hypothetical casual Wikipedia reader take notice? LaughingVulcan 04:20, 8 September 2008 (UTC)[reply]
    We really ought to have an MOS bit on that, so we can at least have consistency from one article to the next. Alpha and order of importance make sense. By length of line, not so much. bd2412 T 04:23, 8 September 2008 (UTC)[reply]
    Should I bring up this issue somewhere else, so it will be addressed in the MOS? Annie D (talk) 05:08, 8 September 2008 (UTC)[reply]
    You're right, it isn't in the guidelines, but that was the impression I had from interacting with other more experienced editors in the Wikipedia:Film project, some of whom are quite particular about the order in which actors are listed. I realise it's a petty issue, but the editor has been repeatedly editing the cast list to make it fit by "length", which may be pretty to look at, but doesn't make any logical sense. Annie D (talk) 04:56, 8 September 2008 (UTC)[reply]

    Block helper script

    I've been working on a block script for quite some time (after DerHexer's script regretfully stopped working, actually), but I've just now gotten around to posting about it here. Some of the specifics of working and installing it are available here; if you have any bugs, requests, or anything else worth mentioning about it, feel free to tell me. Please note that this script has only been tested in Firefox. Yours, —Animum (talk) 01:47, 8 September 2008 (UTC)[reply]

    Worked beautifully. Blocked, then tagged the userpage and talk page. Thanks! - auburnpilot talk 02:19, 8 September 2008 (UTC)[reply]

    Anarctica: Vandalism/Hacking

    Can an admin please look up the Antarctica article? There is discriminatory language posted at the bottom of the page —Preceding unsigned comment added by 24.226.110.142 (talk) 02:51, 8 September 2008 (UTC)[reply]

    I took a quick skim but it's quite a long article. Could you be more specific please? justinfr (talk/contribs) 03:16, 8 September 2008 (UTC)[reply]
    I've gone back a week in the history and can't find anything. There was other vandalism that was always quickly reverted. The user left a message on my talk page saying it was within the boxes at the bottom--maybe a template got vandalized somewhere. justinfr (talk/contribs) 11:14, 8 September 2008 (UTC)[reply]

    Shortage of involved admins at DYK

    OK folks, DYK updates have been a bit slow and there's a bit of a shortage of admins actively involved, and some of those who have been doing it for a while could do with a break. We are asking folks who listed themselves on Wikipedia:Did you know/Admins to update details on this page - User:Olaf Davis/DYKadmins, so we can grade everyone's involvement (and who, knows, someone may want to get involved more :)

    I find it a nice change of one is getting a little tired of negative interactions with vandals, POV pushers, reverters etc. so maybe the nice warm group-hug of DYK may good place to recharge.

    Cheers, Casliber (talk · contribs) 04:34, 8 September 2008 (UTC)[reply]

    Please watch me

    http://en.wikipedia.org/wiki/User_talk:Hrafn#Please_read_my_recent_edits_...

    Hrafn and his buddies are about to kick me off. "His" hierarchy of consortial editors (using the same username, passwd, and /or email communications) might now kick in. I would like you to restore my good name as Doug youvan, Nukeh, and MsTopeka, as one in the same. I do not have the editorial skills or ability to do anything other than what I have already done, because I focus on content and edit in good faith. I am sorry for breaking rules, but this consortium is just to fast and well skilled in WP rules for me to do otherwise. MsTopeka (talk) 04:49, 8 September 2008 (UTC)[reply]

    I don't have a clue what you're talking about. Please explain precisely what it is you're asking an admin to do. --Tango (talk) 05:01, 8 September 2008 (UTC)[reply]
    Diffs? Where has hrafn harassed you? And do you have any proof of your accusations of sharing usernames and passwords? That's a serious charge. Aunt Entropy (talk) 05:48, 8 September 2008 (UTC)[reply]
    Given that User:MsTopeka has kindly admitted to being a further sock of banned User:Doug youvan/User:Nukeh, could somebody please ban 'her'. HrafnTalkStalk 06:00, 8 September 2008 (UTC)[reply]
    There he is, hrafn, and I believe that to be a consortium of editors, and a proxy of www.kcfs.org with many editors on the same username. It's possible all edits are piped through Krebs at kcfs, but I don't know anyone who could figure out how to detect such technology. I'm now in their home state, but I will not make any legal threats here. They defame my real name, Doug youvan. One has made a threat of violence. One of their goals is to control WP articles that are supportive of certain public policy positions, such as NO Intelligent Design being taught in school. ID is now a mess on WP and elsewhere, but it tracks back to the ideas of Arrhenius, one of the fathers of thermodynamics.
    My cv includes 8 years of teaching in 2 departments at MIT in chemistry and biology, 20 years ago. Since then, I was the CEO of a biotech company, worked in aerodynamics, cosmology, mathematics, etc. I am Hrafn's worse nightmare in a public debate because of my background in research level science in many fields. On the other hand, his goal appears to be only to influence public policy, e.g., the Kansas State School Board elections. They pervert scientific articles on WP simply to make Darwin stand and ID fall, because they believe ALL of ID is a trick to get Creation back in the schools.
    I broke some WP rules to catch these guys, so what do I do now? I have accumulated evidence here: http://www.childpainter.org, a master website that has links to other websites. I ask you to look at http://www.wikipediaversusthegodofabraham.org. You will also see that MsTopeka has recently tried to alert fellow WP editors to a potential IPO of WP, and has also looked into MACIDs for security reasons. These are not the efforts of the typical bad troll or socketpuppet. They are more akin to an ACLU activity with the goal of continued Freedom of Speech in a society that has lost much to the war on terror, which appears to be the delusions of a dry drunk, Prez Bush, and his money grubbing pals. Please do not lump all Christians in his bag. To do so will recreate 1935 Germany with Chrstians taking the place of Jews in the present day. Hrafn (and Godwin, a pun) would love to see that happen.MsTopeka (talk) 13:38, 8 September 2008 (UTC)[reply]
    Above, I read "that this may be a jimbo / arbcom decision in some way (hopefully we'll get clarification in due course)" on PD. If that is a method unknown to hard working, common, everyday editors, it appears we have still another problem. MsTopeka (talk) 14:14, 8 September 2008 (UTC)[reply]
    ROFLMAO -- I think this pretty much sums 'Ms Doug' up. I've added a report on WP:SSP. HrafnTalkStalk 14:19, 8 September 2008 (UTC)[reply]
    I have no idea what WP:SSP is. So, I ask a senior admin to defend my position. I appear to be pro per (court analogy) in Hfran v Youvan, where Hfran is highly skilled. I am a scientist, mathematician, and proponent of fair play - not a WP "attorney" like Hrafn who wins arguments in article content based on skills in admin stunts. MsTopeka (talk) 14:29, 8 September 2008 (UTC)[reply]

    Username Blocking...

    What's a reasonable amount of time to wait when blocking a username to allow the user to file a request at WP:CHU? I unblocked Vma2008admin after he requested to change his name. Instead of going to CHU, he created an article...--SmashvilleBONK! 05:57, 8 September 2008 (UTC)[reply]

    • I speedied the article, because it was NN. To be honest, I'd block them again but to be less WP:BITEy, leave a note explaining exactly what they need to do. Black Kite 06:03, 8 September 2008 (UTC)[reply]
    (ec) I'd tend to reblock. If the contribution history is limited (as this one is), one might suggest the user simply open a new account with a more Wikipedia-friendly name. Gwen Gale (talk) 06:05, 8 September 2008 (UTC)[reply]
    I agree, I would reblock. Xclamation point 07:09, 8 September 2008 (UTC)[reply]
    I would say that if the user clearly knows that the account is unblocked, and has not yet requested it within 10-15 minutes, he should be reblocked. עוד מישהו Od Mishehu 08:07, 8 September 2008 (UTC)[reply]
    At an administrator's discretion, you may be unblocked for 24 hours to file a request. It's too soon to block. I assume this editor thinks that posting the unblock request (which contains the new username) is all they had to do. I'll see if I can explain. ETA I've been overtaken by events - Smashville has re-blocked (I think the WP database is a bit laggy right now). SHEFFIELDSTEELTALK 14:44, 8 September 2008 (UTC)[reply]

    Recurrent IP vandalism on Hippopotamus

    See [54]. Suggest temporary semi-protection. Jayen466 13:31, 8 September 2008 (UTC)[reply]

    Please add this to the Wikipedia:Requests for page protection Thanks Monster Under Your Bed (talk) 13:48, 8 September 2008 (UTC)[reply]
    Semi-protected for a period of 1 month, after which the page will be automatically unprotected. Wikipedia is not a bureaucracy. עוד מישהו Od Mishehu 15:01, 8 September 2008 (UTC)[reply]

    Need Assistance with Approving Page

    I created the page "Bettertrades" recently, with the intention of putting up a new and useful page about something I knew and had sources for. It was speedily deleted, and I couldn't get either the deleter or the suggestor to specifically explain the issue. I edited the page even more. I have done everything I can to keep neutral POV, assert notability, and adhere to wikipedia standards. I tried requesting help from User:Coren and User:Jerry, since Coren was the deleting admin, and Jerry was the one who restored the page to my userspace. I've been trying to get some approval or editing from anyone who can help me to make sure that I make the page correctly in order to assure that it doesn't simply get deleted at a pass again.

    If no one has any opposition, I would like to move the page from my userspace at http://en.wikipedia.org/wiki/User:Westcoastbiker/Bettertrades to the URL http://en.wikipedia.org/wiki/BetterTrades (note the uppercase "T"). I hope that my exhaustive efforts have proven useful, and that I can move forward with working on other wikipedia interests. Westcoastbiker (talk) 15:41, 8 September 2008 (UTC)Westcoastbiker[reply]

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