Jump to content

Wikipedia:Administrators' noticeboard

Page semi-protected
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Nouniquenames (talk | contribs) at 18:07, 28 January 2013 (→Continuing topic ban violations by Apteva: opp). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
    Welcome — post issues of interest to administrators.
    Shortcuts

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

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

    Sections inactive for over seven days are archived by Lowercase sigmabot III.(archives, search)

    Template:Active editnotice

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

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

      Shortcuts

      Use the closure requests noticeboard to ask an uninvolved editor to assess, summarize, and formally close a Wikipedia discussion. Do so when consensus appears unclear, it is a contentious issue, or where there are wiki-wide implications (e.g. any change to our policies or guidelines).

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

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

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

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

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

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

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

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

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

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

      Technical instructions for closers

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

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


      Other areas tracking old discussions

      Administrative discussions

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

      Requests for comment

      Wikipedia:Requests for adminship/2024 review/Phase II/Mentoring process

      (Initiated 201 days ago on 15 May 2024) Discussion died down quite a long time ago. I do not believe anything is actionable but a formal closure will help. Soni (talk) 04:19, 3 December 2024 (UTC)[reply]

      Wikipedia:Requests for comment/In the news criteria amendments

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

      Talk:Turkey#RfC_on_massacres_and_genocides_in_the_lead

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

      information Note: This is a contentious topic and subject to general sanctions. Also see: Wikipedia:Administrators' noticeboard topic. Bogazicili (talk) 17:26, 21 November 2024 (UTC)[reply]

      Wikipedia:Requests for comment/Shorten recall petition period

      (Initiated 31 days ago on 1 November 2024) Needs an uninvolved editor or more to close this discussion ASAP, especially to determine whether or not this RfC discussion is premature. George Ho (talk) 23:16, 25 November 2024 (UTC)[reply]

      Talk:Arab migrations to the Levant#RfC On the Better of Two Revisions

      (Initiated 15 days ago on 17 November 2024) It probably wasn't even alive since the start , given its much admonished poor phrasing and the article's topic having minor importance. It doesn't seem any more waiting would have any more meaningful input , and so the most likely conclusion is that there's no consensus on the dispute.TheCuratingEditor (talk) 12:55, 25 November 2024 (UTC)[reply]

      Wikipedia:Requests_for_comment/Grey_Literature

      (Initiated 23 days ago on 10 November 2024) Discussion is slowing significantly. Likely no consensus, personally. Bluethricecreamman (talk) 03:09, 2 December 2024 (UTC)[reply]

      Talk:Russian invasion of Ukraine#Request for comment, can we add North Korea as a belligerent?

      (Initiated 17 days ago on 15 November 2024) There's no need for this to go on for a month. Consensus is overwhelming. Can we get an independent close please, as this is a highly contentious topic. TarnishedPathtalk 12:47, 2 December 2024 (UTC)[reply]

      I was about to ask just this. Slatersteven (talk) 14:30, 2 December 2024 (UTC)[reply]
      Second @TarnishedPath here - consensus is in WP:SNOW territory. FOARP (talk) 15:08, 2 December 2024 (UTC)[reply]
       Done —Compassionate727 (T·C) 20:39, 2 December 2024 (UTC)[reply]

      talk:Rajiv Dixit#RFC can we say he peddaled false hoods in the lede

      (Initiated 74 days ago on 19 September 2024) This seems to have rujn its course, but the vote is evenly split, so it's hard to judge consensus as an involved party. Slatersteven (talk) 19:55, 2 December 2024 (UTC)[reply]

       Done —Compassionate727 (T·C) 21:41, 2 December 2024 (UTC)[reply]

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

      Deletion discussions

      XFD backlog
      V Sep Oct Nov Dec Total
      CfD 0 0 19 0 19
      TfD 0 0 12 0 12
      MfD 0 0 1 0 1
      FfD 0 0 15 0 15
      RfD 0 0 67 0 67
      AfD 0 0 0 0 0

      Wikipedia:Categories for discussion/Log/2024 November 5#Category:National artists of Thailand

      (Initiated 43 days ago on 20 October 2024) HouseBlaster (talk • he/they) 00:01, 25 November 2024 (UTC)[reply]

       Relisted on 2 December by Bibliomaniac15. SilverLocust 💬 10:00, 2 December 2024 (UTC)[reply]
       Not done, as above. --Redrose64 🌹 (talk) 19:38, 2 December 2024 (UTC)[reply]

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

      Other types of closing requests

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

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

       Doing... may take a crack at this close, if no one objects. Allan Nonymous (talk) 17:47, 12 November 2024 (UTC)[reply]
      @Allan Nonymous: do you still plan to close this? voorts (talk/contributions) 23:17, 29 November 2024 (UTC)[reply]
      Yes, sorry about this, I forgot I had this outstanding :). Allan Nonymous (talk) 19:33, 30 November 2024 (UTC)[reply]

      Talk:Donald Trump#Proposal: Age and health concerns regarding Trump

      (Initiated 47 days ago on 16 October 2024) Experienced closer requested. ―Mandruss ☎ 13:57, 27 November 2024 (UTC)[reply]

      Talk:Tesla_Cybercab#Proposed_merge_of_Tesla_Network_into_Tesla_Cybercab

      (Initiated 45 days ago on 18 October 2024) This needs formal closure by someone uninvolved. N2e (talk) 03:06, 1 December 2024 (UTC)[reply]

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

      Number of page watchers tool deprecated

      Hi. It's now possible to view the number of page watchers via the "info" action. For example, at <https://en.wikipedia.org/w/index.php?title=Main_Page&action=info>, you can see that Main Page has over 76,500 page watchers. In the coming weeks, I'll be deprecating the watcher tool. --MZMcBride (talk) 17:04, 17 January 2013 (UTC)[reply]

      The info page itself has a link to the old tool at the bottom, under "External Tools" -- I have no idea how that's edited. NE Ent 02:20, 18 January 2013 (UTC)[reply]
      MediaWiki:Pageinfo-footer. 28bytes (talk) 20:36, 18 January 2013 (UTC)[reply]
      Thank you for updating that page. :-)
      The link is also available from MediaWiki:Histlegend. I'm thinking that replacing (rather than removing) the link from there makes more sense, but I think I'd like to develop a better target for the link first. I guess there are two approaches to take: (1) replace the watcher link with a link to action=info; or (2) replace the watcher link with a link to action=info with an anchor to the number of watchers row, preferably highlighted (like we do with clicked references). Option 2 is my preference, but the underlying HTML currently has no support for this. The tool is only deprecated, not yet abandoned, though, so there's time to work all of this out. --MZMcBride (talk) 22:31, 18 January 2013 (UTC)[reply]
      I like (2), and I suppose this is better than nothing. (It's quite bizarre that the id for that sub-table begins with #, though. Is that typical?) AGK [•] 22:56, 18 January 2013 (UTC)[reply]
      I can't code, so I can't solve problems, but I'm good at pointing out problems for others to worry about. Currently, if a non-admin clicks on your (MZMcBride) tool and there are less than 30 watchers, it comes back and explains "fewer than 30 watchers". If a non-admin clicks on the action=info page instead, for a page with less than 30 watchers, the page watchers line is just gone. So for non-admins looking at MediaWiki:Histlegend for a page with less than 30 watchers, clicking on "Number of watchers", for both options (1) and (2), are just going to confuse them. --Floquenbeam (talk) 23:08, 18 January 2013 (UTC)[reply]
      I see three bugs here, but I probably won't have time to file them until later. I'll post here after I do. --MZMcBride (talk) 17:39, 20 January 2013 (UTC)[reply]
      Is it anticipated that a link to the "info" action will replace the link to your tool? Otherwise, it seems the only way to get to the info action page is to manually edit the url. ‑Scottywong| squeal _ 19:13, 21 January 2013 (UTC)[reply]
      If you go to the History tab for a page, there's a "Page Information" link in the toolbox on the left. 28bytes (talk) 19:14, 21 January 2013 (UTC)[reply]
      That link isn't just on the history tab. KTC (talk) 19:18, 21 January 2013 (UTC)[reply]
      Depends on the skin; in MonoBook that's the only place I see it. 28bytes (talk) 19:34, 21 January 2013 (UTC)[reply]

      In both Monobook and Vector, the "Page information" link should be present in the "toolbox" section of the sidebar for any action (history, view, edit, etc.). If it's not, there's a bug.

      AGK: bugzilla:42629 is the bug you're describing, pretty much. Floquenbeam: bugzilla:44252 and bugzilla:44253 are the bugs you want. --MZMcBride (talk) 19:17, 22 January 2013 (UTC)[reply]

      I've updated User:Jake Wartenberg/centijimbo to reflect the change; if I've made any mistakes, someone please correct me, though I've obviously tested it on my own userpage and found no issues. Incidentally, should we perhaps move it to templatespace? It's Wikipedia-related (if not particularly related to improving the encyclopedia), and has been edited mostly by users other than Jake (who appears to be only intermittently active). — PinkAmpers&(Je vous invite à me parler) 21:42, 23 January 2013 (UTC)[reply]

      Er, where is the "Info page" or "Info action?" I see no tab, page or button so labelled. Edison (talk) 03:20, 26 January 2013 (UTC)[reply]
      There's a link to it from the history page. Writ Keeper ⚇♔ 03:22, 26 January 2013 (UTC)[reply]
      In addition, you can add ?action=info to the end of a URL and you'll get the info. Ryan Vesey 03:25, 26 January 2013 (UTC)[reply]
      I believe it's also linked to as "page information" in the toolbox on any page. — PinkAmpers&(Je vous invite à me parler) 08:49, 26 January 2013 (UTC)[reply]

      Translation into Russian

      Every few days I see the edit filter catching translation of wikipedia page into Russian, eg Special:AbuseLog/8140504. Is this malicious or likely to be an accident - eg software that translates a browser page content, and then user hitting save? Graeme Bartlett (talk) 20:57, 23 January 2013 (UTC)[reply]

      That's thoroughly weird. Why would the browser plugin translate some things but not others? But why would someone attempt to translate random words while leaving other random words untranslated? Even putting chunks through Google Translate takes a bunch of time, since there are so many untranslated words; what kind of vandal or other bad-faith editor would put this much effort into turning the page into macaroni? I can't imagine any logical explanation for it. Nyttend (talk) 21:13, 23 January 2013 (UTC)[reply]
      Update: I'm beginning to think that it's somehow automated, rather than being a misguided would-be translator. Look at what it did to the convert template: {{convert|5004|mm|in|1|abbr=on}} becomes {{convert|5004|мм|в|1|abbr=on}}. Wiktionary notes that в is sometimes a preposition with the meaning of "in" — humans would render this as "Дюйм" or keep it as "in", because no human would turn an abbreviation for "inches" into a preposition. Nyttend (talk) 21:23, 23 January 2013 (UTC)[reply]
      Google Chrome offers automatic translation of foreign-language pages, doesn't it? Couldn't this be a result of someone setting the browser to translate English pages to Russian and then trying to edit here? Jafeluv (talk) 18:16, 24 January 2013 (UTC)[reply]
      Here is another: Special:AbuseLog/8125404 a sencond level header translated, which I blocked as a spambot, but I now think this is inappropriate. And another Special:AbuseLog/8080180 just a third level header section being translated; Special:AbuseLog/8080167 another one. Graeme Bartlett (talk) 10:33, 24 January 2013 (UTC)[reply]
      And this one didn't get blocked at all; how did it get through when the others didn't? Nyttend (talk) 14:14, 24 January 2013 (UTC)[reply]
      Edit filters are not guaranteed to run, perhaps due to too many resources being used. So it is not surprising that some are missed. Jafeluv could be on the right track. Graeme Bartlett (talk) 07:50, 25 January 2013 (UTC)[reply]
      That edit was caught. The filter is warn only, though. And the foreign language filter wouldn't catch these because the edit delta was close to 0. Someguy1221 (talk) 10:34, 25 January 2013 (UTC)[reply]
      OK, well here is another caught one. Special:AbuseLog/8151197. So should we treat this as abuse? Or treat it as an accident? Or should we tighten the edit filter to catch this more? Graeme Bartlett (talk) 06:42, 27 January 2013 (UTC)[reply]
      Filtering IP edits that insert Cyrillic charactes into section headers would probably catch most of these. While there are legitimate reasons for using Cyrillic text in articles, I think having it in section headers is a pretty rare case. (Btw, I tested the translation feature with the newest version of Chrome and contrary to my suspicions above it doesn't seem to translate anything inside the edit box.) Jafeluv (talk) 10:28, 28 January 2013 (UTC)[reply]

      Excessive relisting of nominations at AfD

      HERE is our guideline with respect to relisting deletion debates at Articles for Deletion:

      "...if at the end of the initial seven-day period, the discussion has only a few participants (including the nominator), and/or it seems to be lacking arguments based on policy, it may be appropriate for the closer to relist it, to solicit further discussion to determine consensus. A relisted discussion may be closed once consensus is determined without necessarily waiting a further seven days.

      That said, relisting should not be a substitute for a "no consensus" closure. If the closer feels there has been substantive debate, disparate opinions supported by policy have been expressed, and consensus has not been achieved, a no-consensus close may be preferable.

      Relisting debates repeatedly in the hope of getting sufficient participation is not recommended, and while having a deletion notice on a page is not harmful, its presence over several weeks can become disheartening for its editors. Therefore, in general, debates should not be relisted more than twice. Users relisting a debate for a third (or further) time, or relisting a debate with a substantial number of commenters, should write a short explanation (in addition to the "relist" template) on why they did not consider the debate sufficient.


      Extensions at AfD used to be rarities. However, participation at AfD seems to be down while automated tools have made deletion nominations easier than ever and lately these same automated tools are seemingly used to make third and even fourth extensions of debates, ostensibly due to lack of participation. No rationales are provided for these third and fourth extensions, even though the guideline is quite explicit that they should be. Little is to be gained by singling out the administrators who are punching some sort of "EXTEND DEBATE" button or whatever the hell they are doing; a quick glance at any recent daily AfD debate page should be sufficient. I would merely like to note that this is a problem — it clogs up the works at AfD — and the problem is getting worse. It is time for administrators to start exerting a little authority on nominations surrounded by apathy — either No Consensus Keep them or No Consensus Delete them if nobody cares enough to comment one way or the other... Carrite (talk) 18:57, 25 January 2013 (UTC)[reply]

      • I know I frequently relist in excess of the suggested limits. My reasoning is that someone has taken the time to find a problem with an article and, while I may not be knowledgeable enough to opine, I can see there are problems with discussion that are worth further review. Take Wikipedia:Articles for deletion/Institute of Management of Sri Lanka for example. The only two people to comment are in favor of retention, but both of them seem to have a very poor understanding of sourcing. While it would be a candidate for a no consensus close, I have an unproven suspicion that further review by skilled editors would find the sourcing deficient. Leaving it for another relist seems like the best way to do that. MBisanz talk 17:33, 26 January 2013 (UTC)[reply]
      This is of course part of a larger problem. After years of what I would call over-participation at AFD, the community seems to have swung in the opposite direction and AFDs with only one or two edits are now much more common than they used to be, or so it seems to me anyway. I think AFD got a bad rap because there were/possibly still are too many regulars with a WP:BATTLE approach to the process and that turns a lot of people off. Beeblebrox (talk) 17:34, 27 January 2013 (UTC)[reply]
      • I would strongly support the suggestions above to treat an uncontested, uncommented AFD in the same way as an uncontested PROD - perhaps relist once and then delete? This certainly won't solve all the problems of uncommented AFDs, but it'll simplify it a bit. It is certainly strange that we're effectively saying "using PROD is a quicker way to get something deleted" in borderline cases! Andrew Gray (talk) 11:41, 28 January 2013 (UTC)[reply]

      Range block needed

      We've got an IP editor in the 65.88.88.xxx range that is only editing to use the article talk pages as a forum. So far the posted from 65.88.88.253, 65.88.88.203, and 65.88.88.41 (that I'm aware of).

      Is it possible for someone with an understang of how to range blocking to apply few day to week long one to the range?

      Thank,

      - J Greb (talk) 00:03, 26 January 2013 (UTC)[reply]

      Blocking 65.88.88.0/23 might be best, but let me check for collateral damage first. --(ʞɿɐʇ) ɐuɐʞsǝp 00:06, 26 January 2013 (UTC)[reply]
      An anon-only block on that range should be okay. --(ʞɿɐʇ) ɐuɐʞsǝp 00:09, 26 January 2013 (UTC)[reply]
      OK... th down side is, though I've got the mop, I haven't done a range block. Just drop 65.88.88.0/23 into the regular block page? - J Greb (talk) 01:15, 26 January 2013 (UTC)[reply]
      Yes. There's some more info at mw:Help:Range blocks. Legoktm (talk) 01:20, 26 January 2013 (UTC)[reply]
      Oh well. I guess doing a little whack-a-mole with the individual IPs probably won't discourage them either, nothing does. Beeblebrox (talk) 20:35, 27 January 2013 (UTC)[reply]

      Suggest a code of conduct: If you favor article deletion, try to avoid changing the article, particularly removing large sections of it

      This is not a general discussion forum, but a place for administrative process. I think there are policy questions worth discussing. But even more pertinent, is that someone with the username SupportMelissaKetunuti, by definition, has a "conflict of interest" and should consider their own code of conduct. This is a matter for the deletion process more than anything else, the policies of which have been laid out. Beeblebrox has suggested useful forums for continuing any other pertinent discussion. --Errant (chat!) 23:40, 26 January 2013 (UTC)[reply]

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

      I have seen someone put a label on an article to delete it. They then removed over 2kb of text. This message is NOT to complain about a specific article but is to alert others to try to avoid conflicts of interests.

      This is a clear conflict of interest. I can see why some people may want an article deleted. If so, they can start the process. However, they should not start removing text from an article. To really be clear of a conflict of interest, they should actually stop writing anything in that article, though a good faith and genuine attempt to improve it would probably be ok.

      In real life, that might be like petitioning the city to condemn a house and get it torn down. In the mean time, they are allowed to spray graffiti on it or bring in a bulldozer and tear down the garage.

      People should write here to show their support that those who favor an article be deleted should generally refrain from writing in that article, at least temporarily. SupportMelissaKetunuti (talk) 01:09, 26 January 2013 (UTC)[reply]

      Articles are not ever deleted because of the text they do or don't contain (excepting things like widespread copyright violations and the like). There is no "conflict of interest" to deleting an article after text is removed because the absence of that text does not make the article more likely to be kept following an AFD discussion, nor does its presence make it more likely to be retained. The main reason for deletion is the suitability of the topic itself as the basis of an article, and that is quite independent of the amount or quality of the article text. --Jayron32 01:14, 26 January 2013 (UTC)[reply]
      An article can be deleted because it is poorly written. Or it can be an important article but the text that shows its importance is removed. By ruining an article, the chance of deletion increase. Why not just maintain the highest ethics by not removing stuff if you propose that the article be deleted? Jayron, you are encouraging potentially questionable behavior. I am for acting ethically. SupportMelissaKetunuti (talk) 01:22, 26 January 2013 (UTC)[reply]
      Because none of what you said is true, SMK. No article is ever deleted because it is poorly written, unless it is so poorly written as to be incomprehensible. And an article's importance can be stated just as well in the deletion discussion as on the article itself. Furthermore, as you have found, an article's history is preserved regardless, and everyone who participates in a deletion discussion can see it if they choose. Someguy1221 (talk) 01:26, 26 January 2013 (UTC)[reply]
      If references are deleted, for example, then it can be buried in the history and never found except by a detective with hours of spare time.

      Sample

      Look at this article with stuff removed. It looks questionable whether the article should exist. If you look at the unedited article, it's clear that it should exist....

      Geoffrey Till, FKC (born in London, England, on 14 January 1945) is a British naval historian.

      The son of Arthur Till, a Royal Air Force officer, and Violet Till[citation needed], Geoffrey Till studied at King's College London, where he received his B.A. in 1966. Then, he went on to complete his MA in 1968 and PhD in 1976 at the Department of War Studies, King's College London.

      On a NATO Defence Fellowship, he was a visiting scholar at the United States Naval Postgraduate School, Monterey, California.

      POSSIBLE REACTION: So what, delete this Geoffrey Till guy.

      Return to discussion

      I am frankly shocked that people are rushing to the defense of conflicts of interest. It would be ok if someone wrote "that's not too common". However, there is overwhelming support of those who want deletion and, in the meantime, delete parts of the article. If you are for deletion, you should either temporarily stay away for the duration of the debate or only make uncontroversial and clear improvements. SupportMelissaKetunuti (talk) 01:35, 26 January 2013 (UTC)[reply]

      Ethically, if an editor encounters an article that they think does not belong on Wikipedia and has issues, they should propose it for deletion and edit the article. Leaving garbage in an article probably hurts its chances at AFD more than helps as people read it. Removing undue weight, unsourced allegations, poor sourcing - all of that should be done regardless of one's view about an article. That is how to act ethically. Telling someone to ignore a problem is simply unethical. Ravensfire (talk) 01:32, 26 January 2013 (UTC)[reply]
      That's the first logical response so far! Then those that favor deletion AND remove stuff should do so very carefully to avoid a conflict of interest. Those that favor retention will clearly try to improve the article. Those that favor deletion should be extremely careful not to make it look like they are destroying the article. If others agree with the last two sentences, we are on the same page! SupportMelissaKetunuti (talk) 01:37, 26 January 2013 (UTC)[reply]
      There no inherent conflict of interest. The only interest here is the creation of an encyclopedia. That's it. Trying to assign motives to people like you are doing is counter to Wikipedia's goals and pillars. You need to STOP doing that. You aren't happy that an article you created is being proposed for deletion - you aren't the first one. A far better use of your time would be to read up how you can show the subject is notable and work to improve the article through good sources and improve the writing in the article. But trying to blame people for doing what they think is correct (and that nobody else has seen a problem with) is going to lead you down a dark path. Ravensfire (talk) 01:43, 26 January 2013 (UTC)[reply]
      You are wrong. You accuse of me creating an article. I have done nothing like that.
      Besides, Ravensfire, you are also wrong when you write... Trying to assign motives to people like you are doing is counter to Wikipedia's goals and pillars. You need to STOP doing that.....(THEN YOU DO JUST AS YOU ACCUSE, 'TRYING TO ASSIGN MOTIVES TO PEOPLE')......But trying to blame people for doing what they think is correct SupportMelissaKetunuti (talk) 01:46, 26 January 2013 (UTC)[reply]
      You think what you're doing is correct. They think what they're doing is correct. Tough. See dispute resolution for how these things are handled on Wikipedia. We certainly don't handle them by banning people from making edits based on their opinion of a subject's notability. Someguy1221 (talk) 02:38, 26 January 2013 (UTC)[reply]
      • The removal of reams of unsourced personal opinion was, as you put it, an "uncontroversial and clear improvement". Your user name suggests that you are editing with the agenda of advocating for Melissa Ketunuti, which the content of your edits confirms. That's totally not what Wikipedia is about. Reyk YO! 01:58, 26 January 2013 (UTC)[reply]
      • I think SMK is referring to the article Murder of Dr. Melissa Ketunuti and the edits made by WilliamJE. All I can say is go talk with the other editor first if you disagree with an edit. If you still disagree, bring it to the Dispute resolution noticeboard. As for the deletion attempt, you can simply remove the proposed deletion tag if you don't agree with it. I could nominate it for AfD if you would prefer to continue this debate in a more appropriate environment. Funny Pika! 03:34, 26 January 2013 (UTC)[reply]
      • There are two kinds of changes: those meant in good faith to improve the article, and those meant to strip it of meaningful content. I've done many deletions of promotional or copyvio material from articles at AfD to make them more acceptable. Sometimes the amount that needs to be removed is most or even almost all of the article. On the other hand, sometimes people have removed essentially everything, usually with the excuse that the references for it aren't adequate, and sometimes even proposed it for speedy as no content or context. So,Often indeed much of the content of an article is material which cannot be documented or where the documentation is totally unacceptable, but if removing them would leave the material without substance worth saving, the AfD should be the place to say so. If anyone can think of a simple wording to distinguish the possible cases and where to put it, that might be helpful.
      But it isn't wise to try to change policy to accommodate disputes over a single article or to deal with a one-time special case. If something in particular needs doing that isn't covered by the rules, or someone is being disruptive in a way we have not yet specified, that's why we have IAR. DGG ( talk ) 05:44, 26 January 2013 (UTC)[reply]

      Deletion of material can make an article more likely to be kept

      In some cases, a very, very bad article, with a lot of fringe or unreliable content, can switch from Delete to keep after enough of the bad material is deleted, letting the small amount of good material be seen and evaluated. Adam Cuerden (talk) 06:59, 26 January 2013 (UTC)[reply]

      I've removed the prod. It should go to AfD, where it will be deleted. The IP is probably a sock geolocating to Rio. -Nathan Johnson (talk) 14:48, 26 January 2013 (UTC)[reply]
      Editors that are swayed by the remove of content as to keep an article at AFD over a delete need to be reminded that AFD is not for cleanup; an article in bad shape but otherwise meeting inclusion requirements shouldn't be deleted just because its in bad shape. --MASEM (t) 15:12, 26 January 2013 (UTC)[reply]
      The article was AFD by me and not because the story needed cleanup. I've worked on badly written articles, especially those of notorious sockpuppeteer Ryan kirkpatrick, before he was banned. I do however avoid cleanup work on articles I either plan to AFD or think will be deleted eventually simply because I don't feel like wasting my time. Any articles I AFD are for notability, not memorial, etc not because they are sloppy.
      Also I feel a need to comment on the removal of the PROD. On his talk page, Nathan Johnson wrote- "The PROD was contested by a new user. I simply removed the tag for xem." Nathan has to be referring to SMK. SMK was told not once[2] but twice[3] about removal of PRODs. While SMK is a new user, he has been savvy enough to find this board, read up on what SPA means, and more. He had opportunity to remove the prod but chose not to. Nathan overstepped by taking down the PROD....William 15:58, 26 January 2013 (UTC)[reply]
      Proposed deletion is for uncontroversial deletions that don't meet the speedy deletion criteria. This does not meet the speedy deletion criteria. This is not an uncontroversial deletion. Therefore, use articles for deletion. -Nathan Johnson (talk) 16:17, 26 January 2013 (UTC)[reply]
      That wasn't the rationale you wrote[4] on your talk page- "The PROD was contested by a new user. I simply removed the tag for xem."...William 17:10, 26 January 2013 (UTC)[reply]
      • information Administrator note At a glance I don't see that anyone else has mentioned this, so just for processes sake: This is not the place to make policy proposals and the chance of an actual policy change coming from a discussion on this noticeboard is basically zero. If you want to make a real policy proposal that has at least a chance of being implemented use WP:RFC or WP:VPP, and list the discussion at WP:CENT. This is a matter for the broader community, not just admins and those that watch this page. Beeblebrox (talk) 23:37, 26 January 2013 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      Need closers for WT:Requests_for_adminship/2013 RfC/1

      The first round closes around midnight EST on Tuesday. I'd prefer just a little discussion of how the closers want to approach this before the actual deadline, since a theme here is that the standard RfC format hasn't worked for this problem, and I (and the voters) will be looking for your ideas. I was hoping for 3 closers. - Dank (push to talk) 17:44, 27 January 2013 (UTC)[reply]

      I saw this comment as I was about to post a reminder message to WP:BN. I take it no one's offering?—cyberpower ChatOnline 18:38, 27 January 2013 (UTC)[reply]
      I offered before and that stands, but only as part of a panel. Something this major will require deliberation and discussion, not a unilateral decision. Seraphimblade Talk to me 21:33, 27 January 2013 (UTC)[reply]
      Great, was just about to ping you. - Dank (push to talk) 21:54, 27 January 2013 (UTC)[reply]
      I'm happy to serve as part of a panel. Basalisk inspect damage⁄berate 22:03, 27 January 2013 (UTC)[reply]
      I offered as well, and it too stands, but I would also recommend this be a panel because a close this big needs collaboration to ensure absolute neutrality.—cyberpower ChatOnline 22:46, 27 January 2013 (UTC)[reply]
      I'm glad you're offering, Cyber, but this is an unusual RfC: after the first closing statement, the voters will decide whether they want you guys to stick around for the next close ... because you guys are charged with coming up with a good (or least-bad :) compromise later on, and "selling" that compromise to the voters is part of your job. Since there was an objection when you offered before, let's see if we can get 3 closers who don't get any objections. - Dank (push to talk) 22:52, 27 January 2013 (UTC)[reply]
      Fine. I'm ok with that. I'm just here to contribute to Wikipedia and help out.—cyberpower ChatOnline 23:09, 27 January 2013 (UTC)[reply]

      Okay, since everything seems to be running smoothly and we have at least two closers, I'd like to back off and allow the RfC to morph into whatever the participants and closers want it to be. Are you guys okay with asking the participants if they're happy to keep you as closers, after your first closing statement? Are you on board with the idea of trying to craft a compromise that you believe the voters will be able to support? Are you willing to discuss the approach you want to take to the RfC with the voters? If so, then I'm outtie. - Dank (push to talk) 15:54, 28 January 2013 (UTC)[reply]

      Big job for just 2 this. I think you should get another Admin. closer to help share the workload. Leaky Caldron 16:13, 28 January 2013 (UTC)[reply]
      No argument from me. - Dank (push to talk) 16:16, 28 January 2013 (UTC)[reply]
      I agree with Leaky here. I would go as far as adding a fourth to the list of closers.—cyberpower ChatOffline 16:21, 28 January 2013 (UTC)[reply]

      Continuing topic ban violations by Apteva

      As documented here since Jan. 10, Apteva continues to violate the topic-ban that the community overwhelmingly supported, which said (see [5]):

      Apteva's persistent pushing of the theory that en dashes are never appropriate in proper names, such as the names of wars, comets, bridges, and airports, and his pushing of the theory that the MOS does not apply to article titles, has been disruptive. Based on the consensus reaction of the community, Apteva must refrain from any further advocating of these positions, or any position against en dashes or against the MOS being applicable to article titles, and must not make any page moves or RMs based on such theories. Violation of this topic ban will be grounds for an immediate block and/or a request for arbitration.

      Unfortunately, the closer's statement of the ban to Apteva left him too much room to test the boundaries, by omitting mention of the part that I bolded above; he wrote:

      Based upon both the below discussion and the linked RfC/U, it is clear that Apteva has exhausted the patience of the community in this area. On these grounds, the following is enacted: Apteva is topic banned indefinitely from modifying or discussing the use of dashes, hyphens, or similar types of punctuation, broadly construed, including but not limited to at the manual of style and any requested move discussion.

      On Jan. 10, the closer User:Seraphimblade clarified:

      For my own thoughts here, I would say that this edit is clearly related to Apteva's activity in the area of dashes/hyphens, and that this is both a violation of the ban and that no extension of the ban is necessary for it to be covered as such. I would see this as a clear attempt at gaming the ban by not technically mentioning the previous dispute subject.

      Apteva's latest violation of the community-imposed topic ban is yet one more attempt to modify a policy page to not say that the MOS is applicable to TITLE styling: this diff – not just by advocating his approach, which would be banned behavior, but actually modifying the policy page! (I reverted)

      This time, an enforcement block is unquestionably needed. Dicklyon (talk) 18:25, 27 January 2013 (UTC)[reply]

      This is simply an editor who loves to disrupt Wikipedia to make a wp:POINT being disappointed that I was not blocked. The discussion on my behavior wasted countless hours and occupied 134 pages of text (about half a million bytes). Apteva (talk) 18:44, 27 January 2013 (UTC)[reply]
      The fact that you escaped a block (and "merely" received a topic ban) should hardly be read as condoning your behaviour. Andy Dingley (talk) 18:58, 27 January 2013 (UTC)[reply]
      (edit conflict)No, this looks rather to be an editor who likes to WP:GAME the project by testing out the exact limits of their community-imposed topic ban, whether out of spite or just for the hell of it. ~~ Lothar von Richthofen (talk) 18:59, 27 January 2013 (UTC)[reply]
      I certainly did learn from the experience, and have no intention of gaming or testing. I am here solely to improve wikipedia and no other purpose. Apteva (talk) 19:23, 27 January 2013 (UTC)[reply]
      Gotta love it how people quote topics that sound applicable but are not. "Gaming the system means deliberately using Wikipedia policies and guidelines in bad faith to thwart the aims of Wikipedia." My edit was solely to improve the link and make it more useful. Apteva (talk) 19:28, 27 January 2013 (UTC)[reply]
      Baloney. Your Wikilawyering notwithstanding, the standard, applicable definition would be "...using the rules and procedures meant to protect a system in order, instead, to manipulate the system for a desired outcome." It seems you haven't given up your desired outcome which, no doubt, you consider "improving Wikipedia". --Calton | Talk 09:44, 28 January 2013 (UTC)[reply]
      The offending edit removed the see-also link "* Wikipedia:Manual of Style (article titles) – for guidance on styling of titles", replacing it with just a generic link "* Wikipedia:Manual of Style", which was a step in pushing his disruptive agenda to say that the MOS does not apply to TITLE styling (see the bold in the resolution that the community overwhelming supported, above). He has been at this for many months, wasting megabytes of disruptive discussion at many venues, but refuses to ackowledge that consensus is against him. Dicklyon (talk) 20:17, 27 January 2013 (UTC)[reply]
      • (ec) This is part of the continued WP:IDHT problems discussed at the RfC/U and the topic ban. Although with this edit Apteva did not explicitly mention dashes and hyphens, it's part of the same dispute, from what I can see (and similar to what prompted Seraphimblade's clarification quoted above). The final clarification/warning from Seraphimblade has apparently not had much of an impact, so unfortunately we are left with blocking as the next measure. As they have not previously blocked for violating the topic ban, I would suggest a 24-hour block. Paul Erik (talk)(contribs) 19:47, 27 January 2013 (UTC)[reply]
      • I'll reiterate that I think this behavior is clearly part of the problem that led to the topic ban, as "Does MOS apply to titles?" was a common topic of contention during it, and Apteva's involvement with that question was overwhelmingly as relates to dashes. I don't have any particular opinion as to what the answer to that question should be, but it was an area Apteva was involved in as regards dashes and hyphens. I'm not impressed with the behavior here, and would not object to rewording the sanction if we need to do that, but the idea was to stay away from that area, not try to nitpick at technicalities. Seraphimblade Talk to me 21:31, 27 January 2013 (UTC)[reply]
      • Let's see if I can summarize:
      1. Changing, not removing, a see also link is pushing a disruptive agenda (per Dicklyon)
      2. Even if the topic ban wasn't violated, the user should be blocked (per Paul Erik)
      3. Apparently using AE is against a topic ban (per The Devil's Advocate)
      It seems this can be closed as no admin action needed (except maybe some very large trouts). A few individuals need to find something more productive to do, it seems. --Nouniquenames 04:01, 28 January 2013 (UTC)[reply]
      • Wow, that is not even remotely what I said. It is about the fact that he is using AE to report an editor for comments in a discussion about using en-dashes, an editor with whom he has disputed the use of en-dashes. Personally, I think discussing someone's conduct in a discussion about use of en-dashes falls under the "broadly construed" part of the restriction.--The Devil's Advocate tlk. cntrb. 04:08, 28 January 2013 (UTC)[reply]
      • It's not what I said either. I do think the topic ban was violated; Seraphimblade's clarification explains why. The intention of a topic ban is that the user disengage entirely from the topic, which Apteva is not doing. Paul Erik (talk)(contribs) 04:38, 28 January 2013 (UTC)[reply]
      • Block, fairly clear attempt to circumvent exact wording of topic ban. --SarekOfVulcan (talk) 04:50, 28 January 2013 (UTC)[reply]
      • Enough already. Apteva has been disrupting WP:MOS and WP:TITLE pages since October with his unique theory about dashes and comets. The theory got no support, and everyone else has moved on, but Apteva continues to disrupt MOS and TITLE. —Neotarf (talk) 06:10, 28 January 2013 (UTC)[reply]
      • Without advocating a specific course of action (I'll leave that to others) these actions represent an unambiguous violation of his topic ban. The idea of topic bans is to allow a Wikipedia user to use their talents in areas far afield from ones that encourage them to have behavioral issues. Apteva is showing no signs that they wish to comply with this idea; indeed their actions seem to consist of testing the boundaries of the ban, which is a clear sign that they have no real intention of obeying it in the long term. --Jayron32 06:16, 28 January 2013 (UTC)[reply]
      Well said. Andy Dingley (talk) 13:55, 28 January 2013 (UTC)[reply]
      • Concur with Jayron32, SarekOfVulcan, Paul Erik, Rschen7754, et al. (And see below for an issue no one's noticed yet that is blockworthy in and of itself.) Even without Seraphimblade's clarification that this activity is in fact directly covered by Apteva's topic ban, it would still be WP:GAMING/WP:LAWYERing to skirt the exact wording of it. Furthermore, even after the hopefully forthcoming block expires, the topic ban should be extended to cover the Manual of Style and its applicability more generally. Apteva (a.k.a. Delphi234 a.k.a. Oakwillow a.k.a. 199.125.109.*) has been arguing, tendentiously, disruptively and in an unbelievably parent- and forum-shopping manner, about style matters, from hyphenation to capitalization, at MOS, at RMs, VP, everywhere, for months on end, and not only has not slowed down after being RFC/U'd and WP:AN'd and partially topic banned, but has stepped up his pace, even disrupting WT:AT with off-topic rants, and trying to modify the wording of WP:AT against consensus, etc. It's long past time for this to stop.

        Some editors simply are not temperamentally suited, or knowledgeable enough, for collaborative editing and consensus building on style matters, because they are brow-beating prescriptive grammar holywarriors who believe they are "Right" and must "win" to address a "great wrong", by campaigning everyone else half to death, with the aim of simply wearing opposition down until nothing is left of them but a bloody stain. Such editing patterns become the end-in-itself of editing WP, instead of improving the encyclopedia when left unchecked, as Apteva's has. {{em|It's an unfortunate oversight that the topic ban was so narrowly worded, and this should be rectified}, as it was with PMAnderson (general MOS topic ban; he was eventually blocked permanently for abusive sockpuppetry used to evade the ban.)

        Another, now-obvious, alternative is an indef-block of Apteva and an application of such an extended topic ban to his Delphi234 sockmaster account. See this barely-escaped ban/block for deceptive sockpuppetry: User talk:Delphi234#Usage of multiple accounts. The Apteva account was permitted to continue to exist only after this editor clarified that User:Apteva would only be used for editing solar-power articles and related (and Delphi234 would not be used overlappingly). Yet here we are, with User:Apteva moving further and further away from such article writing toward WP:SPA-like, anti-MOS wiki-picketing and editwarring. The editor continues to use both User:Delphi234 and User:Apteva almost every single day to edit solar/wind/nuclear energy articles in a way that makes it seem like two independent editors, despite being administratively warned twice (on pain of loss of one account and a possibly long-term block of the other) against doing so, as impermissibly deceptive, by admins Lucasbfr (now Luk) and Wknight94, over four years ago. That seems like entirely separate grounds for indef-blocking the Apteva account, as well as for a temporary but not trivial block of the Delphi234 alter-ego (which the user says, at that user-talk discussion, is his main account). I repeat what several of us have been asking, at WP:AN and WP:RFC/U: How long is this user going to be permitted to abuse Wikipedia for his own entertainment and POV-pushing? (Reminder: We've been tolerating it, for no reason, since at least October 2008!) The similarity of all this to PMAnderson's pattern of abuse is striking (though his soapboxes tended to actually be considerably more reasonable than Apteva's). PS: For the record, I think Apteva/Delphi234 does good article writing and sourcing on topics he knows a lot about, such as solar power and the energy grid. Style in English-language formal writing, and how WP operates at the policy level are decidedly not among those topics.
        — SMcCandlish  Talk⇒ ɖ⊝כ⊙þ Contrib. 09:52, 28 January 2013 (UTC)[reply]

        This requires more careful review. Delphi234 and Apteva's contributions have not been directly overlapping -- one edits nuclear/wind, the other solar, and every time Delphi slipped up and posted to a WP-space discussion instead of using the Apteva account, they self-reverted. --SarekOfVulcan (talk) 14:26, 28 January 2013 (UTC)[reply]
      • The correct response from Apteva would be something like "Hmmm, I did not think that would be a problem, but if people here think it is, I will make sure to give edits like that a very wide berth in the future". Examples of wrong responses are as shown above: accuse Dicklyon of disrupting Wikipedia, and talk about previous discussions wasting countless hours and taking half a million bytes. That latter point (the amount of time/space taken to discuss Apteva's behavior) would be sufficient to convince most editors to stay a long way away from the topic, but it appears that Apteva is made of sterner stuff than most editors, and more blunt instruments will be required. The next violation should invoke an indefinite block until a convincing reassurance is forthcoming. Johnuniq (talk) 10:01, 28 January 2013 (UTC)[reply]
      Looks like that conversation has already taken place: [6] —Neotarf (talk) 10:13, 28 January 2013 (UTC)[reply]
      • Per blocking policy, blocks are not punitive but preventative and none is warranted as I obviously did not consider that an infraction or infringement in any way of the ban which I am under. I would like to call everyone's attention to the recent warning on my talk page, and suggest that is sufficient. I apologize for the trouble that edit caused. See also links do not have explanations, as what is an explanation for one editor is meaningless for another, and so bare links are all we use. So yes, sorry, and I do promise to do better in not making anyone think I am doing something that I am not in the future. Peace and happy editing. Now all of us I am sure have better things to do. There are certainly 4 million articles and a lot of other issues more important than this one, which has already been dealt with. Thanks. Apteva (talk) 14:23, 28 January 2013 (UTC)[reply]
      • As you say, per the blocking policy, blocks are preventative and a block here would be to prevent you from continuing to violate your topic ban. Precisely because there are 4 million articles to work on, why don't you take the hint from your topic ban and move on to non-MOS related stuff. Blackmane (talk) 14:40, 28 January 2013 (UTC)[reply]
      • Block for 1 month. Testing the edges of a broadly-construed topic ban is a great way to get the ban widened. 1 month block to see if it sinks in. Then offer some WP:ROPE. User has a habitual habit of promising not to be interested in something to avoid sanction, then returning to the same behavior after the waters have calmed (see my user talk). (Noting, as usual, that this does not mean that others involved in this dispute should not be blocked/banned; simply that this user should.) -Nathan Johnson (talk) 15:43, 28 January 2013 (UTC)[reply]
      • Support block - sigh, following on from the topic ban proposal which they show minimal respect for. Also, I still don't understand why this user has 2 accounts, and I still don't see how they think they will ever pass RFA with this kind of behaviour. GiantSnowman 15:51, 28 January 2013 (UTC)[reply]
        • A long block like that would not serve to do anything other than hurt Wikipedia. I recently brought a third article to GA, and would likely a fourth in the next month, which would be delayed a month should a long block like that be administered. This would be a classic case of biting your nose to spite your face. Look. I get it. I do recommend though, dealing with the incivility at the MOS. Not by blocking everyone or topic banning anyone, but by treating the talk page as a DR page and only edited if a DR volunteer is present and issuing warnings to anyone acting incivil, in particular, violating wp:FOC or WP:NPA. Apteva (talk) 16:01, 28 January 2013 (UTC)[reply]
          • Wikipedia will cope without you. Even on articles that you WP:OWN and that clearly no-one else could be capable of working on. Andy Dingley (talk) 16:28, 28 January 2013 (UTC)[reply]
            • That misses the point. Wikipedia is unstoppable, and with or without anyone will do just fine. However, it is not to our advantage to ask anyone to delay their work needlessly. I do not own any articles, but I am expert in a dozen subjects encompassing several hundred articles and I do focus most of my attention there. Apteva (talk) 16:53, 28 January 2013 (UTC)[reply]
      • Question - would such a block apply to the Apteva account, or to this editor's other account(s) too? Andy Dingley (talk) 16:26, 28 January 2013 (UTC)[reply]
        • Both/all - though as stated above I fail to see why they need a second account. It appears to be one used for the disruptive editing, and leaves an ill feeling in my stomach. GiantSnowman 16:29, 28 January 2013 (UTC)[reply]
          • I too would question the good hand / bad hand accounts, especially as they're clearly being used quite contrarily to how they proposed that they would use them. However that is a separate question. Andy Dingley (talk) 16:46, 28 January 2013 (UTC)[reply]
      • Support block very clearly a repeat of the tendentious behaviour that led to the topic ban. Suggest 1 week, to escalate as normal if issues recur. Block should be implement on both accounts and I would endorse an examination of the Delphi234/Apteva overlap--Cailil talk 17:53, 28 January 2013 (UTC)[reply]

      Request for review

      IT'S FINE
      Snow close (revert this close if you actually think it was a bad block, otherwise let's go find something useful to to do NE Ent 01:05, 28 January 2013 (UTC)[reply]

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

      Hi all, earlier today Media-hound- thethird (talk · contribs) was reported on ANI for misusing his talk page while blocked; to make a long story short, I ended up indeffing him without talk page access. I extended the block to indefinite because the user was displaying a massive battleground mentality which, in my opinion, is better handled through an indefinite block than a time-limited one; I also revoked this editor's ability to edit his talk page, because he was clearly abusing it. As such, I believe that both the indefinite part of the block and the no-talk-page one are necessary, because each one addresses part of the disruption caused by him. The combination, however, may appear draconian, as another administrator has pointed out on my talk page. So, here I am, asking for a review of my actions. Salvio Let's talk about it! 21:29, 27 January 2013 (UTC)[reply]

      • I wouldn't have done both at the same time, just indef and then give them a chance to respond to that. (And these days I'm very much coming round to the feeling that letting blocked editors rant on their talk page is generally harmless, unless there's something especially bad.) -- Boing! said Zebedee (talk) 21:48, 27 January 2013 (UTC)[reply]
        Oh, I should say I support the indef - this it not a case where a time-specific block would be likely to work. -- Boing! said Zebedee (talk) 22:35, 27 January 2013 (UTC)[reply]
      • Looking at the sequence of events, Salvio's not quite clear here. FPAS blocked him for 2 weeks on the 25th, then upped it to 120 days about 40 minutes later, after a review of the guy's edits. Media-hound then spent the next two and a half days raining fire and brimstone on just about everyone, until Basalisk removed his talkpage access, without extending the block. Salvio extended the block to indef about 3 mins later, presumably unaware of Basalisk's action. This guy seems to be the archetypal POV warrior, with a great TRUTH to tell, INJUSTICE to right or whatever. I'm sure Amnesty International are bloody thrilled to have him batting for them. In short, no objection here to Salvio's action. The guy still has UTRS and BASC if he wants to keep going. Elen of the Roads (talk) 22:15, 27 January 2013 (UTC)[reply]
      • IMHO it is obvious that any time spent explaining procedures to that user would be time wasted—it would be better to do some work at WP:HELPDESK where editors may consider advice given. The indefinite block (until there is a clear statement that shows an understanding of the problem, and how the editor will work within the community in the future) is essential. The user posted a gentle but clear violation of WP:NLT: "The issue of Wiki fail in having systems and correct signposting for Abuse-Bullying-Harassment is being taken up with the Wiki Foundation UK as there are relevant legal issues due to UK laws changed in November 2012" (diff). Perhaps talk page usage could be restored with a clear explanation that it is not available for general expositions, and must not be used to continue disputes, particularly with hints of legal repercussions. Then remove talk page access after a couple of days if the page is further misused. Johnuniq (talk) 22:18, 27 January 2013 (UTC)[reply]
      • Given Elen's synopsis, I'm not seeing why we should restore talk page access at all - the editor has abused the privilege, and lost them. Given that they're indeffed for NLT, there is no interaction we should be taking with them anyway. Leave both block and lock in place until and unless, as noted above "there is a clear statement that shows an understanding of the problem, and how the editor will work within the community in the future". One puppy's opinion. KillerChihuahua 23:17, 27 January 2013 (UTC)[reply]
      • Wikipedia is not to push causes, not even good ones. Unless there's a clear indication this editor gains understanding of that, which seems unlikely at this point, the block is appropriate and should remain. Seraphimblade Talk to me 23:50, 27 January 2013 (UTC)[reply]
      • I find I agree. Whether or not any of us would have revoked the talk page I see no compelling reason to restore it. On another note, I tried to hat the whole thing in order to highlight the message that they should use UTRS or BASC to appeal further, and for some weird reason it didn't work, some of the content would not be collapsed. Never seen that before. Beeblebrox (talk) 00:19, 28 January 2013 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      PC2 for Mangoeater targets

      After this thread started, Francophonie&Androphilie had his username changed to PinkAmpersand.

      As anyone who monitors AN/I, SPI, CSD, AFD, or even, lately, RFA [7] knows, de facto banned Mangoeater1000 (talk · contribs · deleted contribs · page moves · block user · logs · block log · arb · rfc · lta · SPI · cuwiki) has been incredibly persistent in his disruption, generally in relation to articles on NYU Poly (promoting it) and Cal Poly Pomona (trying to minimize it). It got so bad that two weeks ago Reaper Eternal full-protected Polytechnic Institute of New York University and List of NYU Polytechnic Institute people‎ until March 28 and March 6, respectively. To me this seems unfortunate (though I completely understand and agree with Reaper's decision), especially as both articles are in serious need of improvement. So, I was wondering if we could discuss the option of implementing Pending Changes Level 2 protection (in conjunction with semi-protection, probably). While there was never any community endorsement of its use, neither was there, as King of Hearts pointed out at AN/I recently, explaining his decision to apply PC2 to 1948 Arab-Israeli War, any consensus against its use, meaning that there's nothing to stop the community from making ad hoc IAR decisions to apply it to certain articles. (Elockid has since applied PC2 to First York, Transdev York, and York Pullman.) Clearly it's better to let users edit an article, subject to review, than to not let them at all, and both articles are monitored by several reviewers and admins. Furthermore, Mangoeater has been active since May, had his first sock blocked in July, and has been indeffed since October, so there's no reason to believe he won't just start up again come March. I suggested at the Arab-Israeli War AN/I thread that we hold future discussions PC2 discussions here, as AN/I can be so hostile that well-respected community members steer clear of it, limiting the degree of consensus that can be achieved on anything policy-related. So, I'm putting my money where my mouth is. Thoughts? — Francophonie&Androphilie(Je vous invite à me parler) 00:06, 15 January 2013 (UTC)[reply]

      • Makes me somewhat uncomfortable. Not because I don't think putting PC2 on as an alternative to full-protection is a bad idea to protect against banned socks (etc.) but because the community consensus in the PC RfCs doesn't endorse PC2 and use of it is likely to lead to accusations that we are setting off down a slippery slope, on an express train through some undemocratic wasteland. So, yes, support in theory, but in practice it seems like the community will excrete a brick. —Tom Morris (talk) 01:04, 15 January 2013 (UTC)[reply]
      • Support. Both PC2 and full protection are game-able by socks, but this won't be substantially easier for them, while this will be substantially easier for good-faith editors than it would be to force them to use editprotected requests all the time. Nyttend (talk) 02:41, 15 January 2013 (UTC)[reply]
      • Support per IAR, even though I believe it would be more optimal to gain consensus for its use to avoid any possible shenanigans. I would also think an edit filter would be a good alternative in many cases, but here it seems that the behavior is not truly consistent enough for that.--Jasper Deng (talk) 02:51, 15 January 2013 (UTC)[reply]
      • Support, this seems to be one of those cases for which IAR exists. --Nouniquenames 04:43, 15 January 2013 (UTC)[reply]
      • Note, if anyone would like to reference the note I ended up leaving on the talkpage of the article referenced above, that kind of note should suffice to explain the reasoning for the PC2. As long as we don't go PC2 on everything, I think it's okay for a very select few articles. gwickwiretalkedits 04:47, 15 January 2013 (UTC)[reply]
      • Oppose. A little ironic, because I like PC2 and detest PC1, but with the amount of dishonesty that went on with the original implementation of PC, I think anything that even smells of going against community consensus needs to be avoided. The primary opposition to PC was based on "slippery slope" style of arguments, and this just feeds them.—Kww(talk) 04:58, 15 January 2013 (UTC)[reply]
      • Oppose This is ridiculous. Maybe Elockid added PC2 by accident, but either way this should not be getting implemented like this, period. It can only create confusion for admins and reviewers. So I implore any admin to immediately remove the PC2 protection from any articles that have them. As far as I know this would just be the 1948 Arab-Israeli War article, the Transdev York article, the First York article, and the York Pullman article.--The Devil's Advocate tlk. cntrb. 06:01, 15 January 2013 (UTC)[reply]
      • I know it confused me to see an article on my watchlist (1948 Arab-Israeli War) with PC2 protection when I knew the RfC did not get consensus for that level of protection. You may also have the old "other people are doing so it must be acceptable" reaction and then have admins imposing PC2 protection like any other protection under the impression it is now legit. Not to mention that we don't have a clear procedure set out for reviewing changes of the sort PC2 is being used to stop in these ad-hoc cases. Although not related to the above, the whole notion of half a dozen editors using AN/ANI as a workaround for an RfC that involved several dozen editors is not the sort of thing I endorse.--The Devil's Advocate tlk. cntrb. 06:29, 15 January 2013 (UTC)[reply]
      • I believe TDA is listing the four articles currently under PC2 protection (according to the relevant category; it's possible that others are, but haven't been tagged with {{pp-pc2}}, which auto-categorizes them). In response to TDA's general points, though, I, like, Jasper, don't really follow: This is about as visible a forum as it gets; if it's good enough to ban and unban users, I'd think it's good enough to apply protection to a single article. So I don't really understand what could be confusing about this. I don't see what's ridiculous about trying to stop a lone troll from permanently stalling the improvement of two articles in need of substantial cleanup. — Francophonie&Androphilie(Je vous invite à me parler) 06:26, 15 January 2013 (UTC)[reply]
      • You may find this astonishing, but plenty of people edit Wikipedia without paying any mind to cesspools such as this page and certainly many edit without looking at it on a regular basis. Circumventing a broad and lengthy community discussion involving dozens of editors by using AN because you want to thump on the socks is not appealing to me at all.--The Devil's Advocate tlk. cntrb. 06:40, 15 January 2013 (UTC)[reply]
      • I'm not circumventing consensus; I'm seeking it. Circumventing it would be to find some out-of-the-loop admin and email them to ask if they'd mind downgrading it to PC2. Starting a thread at the board that we use for some of our most substantial discussions is seeking it. "No consensus" is not a valid reason to oppose a proposal, for rather obvious reasons. If the consensus here is that this really needs to be done by RfC, so be it, but WP:PC2012/RfC 1 closed as "No consensus", so it's really not circumventing anything to start a discussion in a prominent community forum as to whether we should apply PC2 to a particular article. — Francophonie&Androphilie(Je vous invite à me parler) 06:52, 15 January 2013 (UTC)[reply]
      • I'd normally agree with you that you can't subvert a "no consensus", but since the original PC trial was marred by such blatant dishonesty and efforts to bypass our normal consensus process, I think we need to tread especially carefully.—Kww(talk) 16:11, 15 January 2013 (UTC)[reply]
      • Oppose I have been a firm supporter of using PC2 in limited circumstances, and this is certainly one of them. But the PC debate has been a feculent clusterfuck of drama in large part because of the failure to end the initial trial on time. As such, doing *anything* new with PC, including any use of PC2, without an explicit and broad community consensus, seems foolhardy due to the risk of disrupting the community. It's "cheaper in the long run", to do this right, even if it means a few full protects in the meantime. Want PC2? I'll be there at the RFC supporting it. But not until. --j⚛e deckertalk 06:35, 15 January 2013 (UTC)[reply]
        Moving to Support in view of listing at WP:CENT, which I believe will reduce the probability of bad splashback. --j⚛e deckertalk 02:35, 16 January 2013 (UTC)[reply]
      • Support In this case, I believe WP:IAR applies. This is a wayyy better solution than full protection here since good faith editors don't need to make edit-requests all the time. It also protects against socks. It's a win-win situation, and it works extremely well here. Vacation9 13:16, 15 January 2013 (UTC)[reply]
      • Support. Gives editors in good standing better leverage against likely POV changes from socks. Binksternet (talk) 14:45, 15 January 2013 (UTC)[reply]
      • Support. Use this as a test case if necessary but the more countermeasures we use for persistent socks the better off we will be.
         — Berean Hunter (talk) 16:06, 15 January 2013 (UTC)[reply]
      • Support, this is definitely the case for PC2 to be implemented on. A little concerned that PC2 had no consensus at the time of PC implementation, but in this context, I like it. Let's see if the community is willing to play ball. -T.I.M(Contact) 00:39, 16 January 2013 (UTC)[reply]
      • Oppose if we were to every use PC2, this would be the type of case. But A) there is no consensus to use it at all and B) as Kww and others have said, there has been way too much drama around this in the past to open up this can of worms now. Fully protect it if needed, but PC2 is a really bad idea as it will create more drama and work than it will save. Hobit (talk) 18:12, 15 January 2013 (UTC)[reply]
      • Oppose. PC2 has never been approved for use on Wikipedia (outside of the trial a couple of years ago). That it was approved was one interpretation of the close in June to the big PC RfC, but during the September RfC specifically on PC2, the case was convincingly made that neither the voters nor the closers in the spring had given PC2 much thought. PC2 would be something not only new, but revolutionary, on Wikipedia (creating a class of Wikipedians whose job it is to decide which edits of everyone else are good enough to stay and which aren't), so turning it on would require consensus; the RfC was closed as no consensus. To use it now is to say that developers and not the Wikipedian community have the authority to decide how we protect pages on Wikipedia. Reading quickly, I don't see evidence that any of the supporters above have considered any of the problems with PC2 that were pointed out in the September RfC. In particular, this is a critical stage for PC1, which is new and unexpected for most editors ... and now, as a result of allowing the use of PC2 here, an editor has just changed the table which is supposed to describe PC1 back into a table giving two PC2 options, which is going to make it even harder for people to get comfortable with PC1. Having said all that: IAR is policy, and I'm always in favor of non-disruptive experimentation. If this were just treated as a lone experiment, with discussion about possible positive and negative consequences and requests for alternatives that might be better than PC2, and if there were no changes to the main PC page, I wouldn't have any strong feelings about it. - Dank (push to talk) 01:24, 16 January 2013 (UTC)[reply]
      • I've respectfully reverted you, Monty; if this proposal is successful, I'm planning on adding a few footnotes explaining that there've been a handful of IAR applications. But considering that the abbreviated table already links to the full one, I think it's unnecessary to revise policy based on the minority of cases. I'd like to make it clear to all who've opposed that I very much feel that a large-scale implementation of PC2 should only be conducted through an RFC, and that this noticeboard is not the place to establish binding precedent. Anyways, Dank, if I clarify that my intention, at least, as original poster, was only to, as you say, treat this as a lone experiment (and, looking through the support !votes, it appears to me that this is the general sentiment among those who support), would you perhaps reconsider your !vote? You make some very good points against PC2 in general, but you seem to concede that it could be effective here. — Francophonie&Androphilie(Je vous invite à me parler) 01:45, 16 January 2013 (UTC)[reply]
      • When this turns into an actual experiment ... with the supporters agreeing that the point is to try new approaches to a difficult problem, discussing pros and cons and alternatives on the article talk page, rather than taking the position that this is an approved protection tool that needs no discussion ... I'll strike my oppose, if this thread hasn't been archived. Note that a form of protection that would be obviously superior to PC2 (if used only for these rare cases of very determined socks) would be to make some pages require 50 (or 100 or 250) prior edits by new accounts; that wouldn't create a special class of editors charged with ruling on everyone else's edits, but it would succeed in frustrating the socks, and would make it easier for us to identify them, possibly before they can even edit their target pages. - Dank (push to talk) 02:49, 16 January 2013 (UTC)[reply]
      • You could think of it that way, though I'd want this to remain rare enough that it wouldn't make sense to talk on-wiki about a new "class" of Wikipedians ... just have the code exclude edits by people with less than 100 (or whatever number works best) contribs, for a handful of articles. Obviously not something we'd want to apply often, but it beats all hell out of PC2 ... particularly in this case, where PC2 is being used to let reviewers rule on whether edits are coming from socks ... when reviewers aren't being selected or encouraged to do any such thing, reviewers are supposed to be checking for vandalism and BLP edits. - Dank (push to talk) 03:06, 16 January 2013 (UTC)[reply]
      • Oppose There exists, as of this posting, 125,500 active users, of whom only 7,000 have reviewer capability(reviewers + admins). Only 3600 editors are watching this page, and obviously many of those are admins. Even if we assume there are zero admin or reviewer watchers, that means only 117,000 or 3% of active editors are monitoring this page. To disable the effective editing capability of 97% of Wikipedia editors without notice is disruptive to the editing process. NE Ent 02:30, 16 January 2013 (UTC)[reply]
      • I don't quite follow: Currently, there are only 848 users who can edit these articles, and very few of them probably ever will; if we implement PC2, any user (or, assuming we combine it with semi-protection, any autoconfirmed user) will be able to; yes, their edits will be subject to review, but I think it's safe to say reviewers will be very cautious before rejecting submissions that wouldn't fall under their purview under PC1. (In fact, we can explicitly mandate this, if desired.) I hate removing editing access to the encyclopedia that anyone can edit as much as the next guy, but that's why I'm suggesting this: Nothing less than PC2 will have any hope of being effective while Mangoeater's out there, and full protection is... awful. The question here is should we leave an article un-edit-able for three months over philosophical objections to the general theory of PC2? — Francophonie&Androphilie(Je vous invite à me parler) 07:39, 16 January 2013 (UTC)[reply]
      • Full protection provides a clear and well known interface; PC2 does not, it provides a "fake edit" interface that makes it appear to autoconfirmed editors they're editing the current view of the page, but they're not. FPP is good because we know it's painful, which mitigates the temptation to overly apply it; because PC2 appears to be cheap there will be a tendency to use it more and more. Long term normal editors will have to become reviewers or the reviewers will have to spend more and more time reviewing. Now is the the time to address the question how will this scale? "Four" articles becomes 40 becomes 400... NE Ent 11:39, 16 January 2013 (UTC)[reply]
      • Philosophical objections? Replying on your talk page. - Dank (push to talk) 11:46, 16 January 2013 (UTC)[reply]
      • I would support using PC2 on the pages only if we agree that it is a test case and the protection is temporary. (Having worked with Dank on some of the recent PC RfCs, I agree with many of his views on the matter.) ~Adjwilley (talk) 03:43, 16 January 2013 (UTC)[reply]
      • Oppose, largely per Kww. Let's not go down this road. We just finished a seemingly interminable process involving multiple RfCs and much contentiousness. Enough is enough for a while. While it may be tempting to make "just one exception" here, exactly how long would it be before someone wants another exception, and another, and another? And if the rationale given in those subsequent requests is compelling, what then? Somehow we got by for more than a decade without PC1, and we seem to be doing all right without PC2 now. Anyone who'd like to modify a fully-protected article can make an edit request. Rivertorch (talk) 10:36, 16 January 2013 (UTC)[reply]
      • Support with the condition that every registered (inserted edit - I meant autoconfirmed) user is given reviewer rights. Otherwise Oppose. Only in death does duty end (talk) 11:51, 16 January 2013 (UTC)[reply]
        • Maybe this is just a case of somewhat-too-deadpan reductio ad absurdum (in which case, well played), but granting all registered users "reviewer" status would not only make PC2 identical to PC1, but reduce both of their protectiony-ness to below that of the current PC1, since it would allow non-autoconfirmed but registered (and therefore reviewer) accounts to bypass the protection. Writ Keeper ⚇♔ 14:56, 16 January 2013 (UTC)[reply]
          • I knew I should have wink-smiley-faced it. One of the reasons PC2 didnt gain consensus was the argument that it would create another layer of trusted users/permission levels/senority, however you wish to word it. Setting the reviewer bar as low as possible would eliminate that concern. However I did mean 'auto-confirmed' in the above, not merely 'registered' so have clarified. But I was only semi-serious. I would support admins ignoring the lack of community consensus regarding PC2 only if the reviewer bar was low, as accusations of power-gathering/protectionism are irrelevant at that point. Otherwise if the 'community' is not going to be made reviewers, then effectively the lack of consensus should stand, otherwise its just another wedge between admins and non-admins. Either respect lack of previous consensus, or hold another PC RFC (yes yes, another one). Only in death does duty end (talk) 15:47, 16 January 2013 (UTC)[reply]
      • Oppose I'm not usually a big fan of slippery-slope arguments, but in this case, it's compelling. We as a community have seen fit to keep PC2 from entering the admin toolbox. We've had one instance of PC2 slipping under the radar already; here we're asking for another. At what point are we admins just overreaching and ignoring the consensus of the community? I don't think this instance puts us over that line, but it's a line that we should be staying far away from. If it's not in our toolbox, we don't get to use it, period. Writ Keeper ⚇♔ 14:48, 16 January 2013 (UTC)[reply]
      • Oppose obviously. WP:PC2012/RfC 1. -Nathan Johnson (talk) 19:39, 16 January 2013 (UTC)[reply]
      • So a lack of consensus is reason to oppose an attempt at getting consensus? Nyttend (talk) 17:22, 17 January 2013 (UTC)[reply]
        • With respect, I think you've got it backwards; it appears to me that the opposers are doing the things normally associated with trying to get consensus, such as pointing to past discussions and weighing pros and cons. I'm not saying that supporters don't know what they're talking about, and don't believe that ... but if I'm just looking at what's on this page, I don't see evidence that the people who supported before I weighed in were either considering past arguments or encouraging people to treat this as an experiment. OTOH, I'm not on board with "just say no", either ... the September RfC closed with a recommendation to look at this again in six to nine months, after we had sufficient experience with PC1 to be able to say something intelligent about where all this is going. Let's make it six months, and let's spend a couple of months looking at PC1, PC2, and alternatives to PC2. My preference, based on what I've seen so far, is stated in my thread above. - Dank (push to talk) 17:55, 17 January 2013 (UTC)[reply]
        • There's no problem attempting to get consensus, there's a problem with claiming consensus for so fundamental a wikitask as article editing on a page which bills itself as "This page is for posting information and issues that affect administrators ... Issues appropriate for this page could include: General announcements, discussion of administration methods, ban proposals, block reviews, and backlog notices." (emphasis original)NE Ent 18:15, 17 January 2013 (UTC)[reply]
          • But this does affect administrators because this thread is about a specific dane-braimaged sock and trying to effectuate countermeasures to halt him. Yes, Dank, my support statement above encourages this to be an experiment but one that needs done now not in one or three months. Mangoeater is wasting too much of our time and we are looking to halt him ASAP. This limited use on what, maybe 10 articles(?), probably would affect less than 100 regular editors. I'm not part of the discussions on PC and hold no particular opinions on them but my ears have perked up at the idea of seeing another tool in grasp for ridding us of some of the worst problem children.
             — Berean Hunter (talk) 18:50, 17 January 2013 (UTC)[reply]
      • Oppose' even though it might make my specific job easier. I am currently dealing with an edit request for one of the related articles, which I am answering in good faith, though it is made by a new SPI, and consists essentially of a request to restore the old and inappropriately promotional material. It is I think easy to justify my edits and non-edits, but I am editing through protection, which is always an uncomfortable position. The reason for my oppose is very simple: irrelevant to the merits of PC2, doing it now is hopelessly confusing. We have enough problems with PC1 being unfamiliar. Let's learn to use it first, and then see if the community wants to make a trial of going to the next level. If the PC1 experience is good, they probably will, so what we should concentrate on is getting PC1 to be part of the accepted and understood routine. DGG ( talk ) 22:32, 18 January 2013 (UTC)[reply]
      • Support as a one-off test case. Much of the opposition to PC2 (IMO) was more about "let's not do this kind of complicated thing yet", with a three-month delay suggested before reviewing the issue again, rather than "absolutely never". The expected flood of articles listed at RFPP for PC did not materialize. The couple of times I've checked, the entire queue has had a single-digit number of changes yet to be reviewed. The predicted endless complaints haven't materialized (well, I haven't seen any, but I am behind on my watchlist, so perhaps I've just not gotten to the pages where the whole world is freaking out). So I think that reality has proven less dire than predicted, and we could probably cut short the planned three-month system for such an appropriate use. (I don't think that I'd support its use at this time with anything less than a significant discussion here at AN.) WhatamIdoing (talk) 01:32, 19 January 2013 (UTC)[reply]
      • Those of you who read F&A's linked discussion may or may not have noticed that my question was never answered. Now, I freely admit my ignorance: I am not very familiar with Mangoeater1000's case, and I don't know much about blocking account creation, but before I weigh in, I'd love to hear an explanation for why a hard block doesn't or wouldn't work on Mangoeater1000. Is he circumventing an account creation block, or is there not one currently in place? Full protection or PCPP 2 both seem excessive when they're essentially only there to thwart one persistent user. I can't disagree that semi-protection is probably insufficient here, but why is further protection the only answer? —Rutebega (talk) 20:49, 19 January 2013 (UTC)[reply]
      Just realized I can see the user's block settings in his block log, sorry. He's justifiably been indef hardblocked since December, which does raise the question of how he's been circumventing that to keep on socking. I'll wait for further comments on this before I cast my !vote. —Rutebega (talk) 21:01, 19 January 2013 (UTC)[reply]
      • "Account creation blocked" only applies to the user account itself, and to its last-used IP address when autoblocked. However, after the autoblock expires, more socks can be created while logged out. Although CheckUser can help prevent this by find out and hardblocking the underlying IP address(es) for extended periods of time, IP hopping can and does occur.--Jasper Deng (talk) 06:50, 20 January 2013 (UTC)[reply]
      • Pretty much everything has been tried. Skimming through a random sampling from Category:Wikipedia sockpuppets of Mangoeater1000, it appears that all (or almost all) of the 79-and-counting socks have been hardblocked. And according to the SPI archive, Avi and DoRD have now blocked at least 6 ranges. I don't know if those ranges were softblocked or hardblocked (or softblocked with account creation disabled), and I see that earlier on there was some hesitation to hardblock an NYU range that Mangoeater was using; if a CU is at liberty to comment on the degree to which IP-blocking actions have been pursued, I think that would be helpful to editors like Rutebega who want to be sure that PC2 is the only feasible alternative to full-protection before they consider supporting this. — PinkAmpers&(Je vous invite à me parler) 16:28, 20 January 2013 (UTC)[reply]

      Comment: If anyone is wondering my rationale for applying PC2 + semi, here it is. As you may or may not have known, getting autoconfirmation is extremely easy. So easy in fact that a number of blocked and/or banned users have decided to take advantage of this ease of attaining autoconfirmation and bypass semiprotection. In some cases full protection has been applied to deal with the disruption, but from what I have seen, editors tend to opt for allowing at least some people (not just admins) to edit an article. There are really no other more feasible means of preventing the disruption while minimizing collateral. Elockid (Talk) 21:31, 22 January 2013 (UTC)[reply]

      • Oppose Many school articles--I would say almost all school articles-are edited mostly or entirely by students or alumni. Obviously, they're the people most likely to be knowledgable & interested. We just can't rely on a 16-year-old high school dropout(PinkAmpersand)--Unitskayak (talk) 22:24, 22 January 2013 (UTC)[reply]
      • See Wikipedia:Sockpuppet investigations/Mangoeater1000 for Unitskayak. 72Dino (talk) 22:26, 22 January 2013 (UTC)[reply]
      • That's a fucking low blow, Pablo, even for you. If you comment here again, I'll initiate proceedings for a formal community ban with the additional rider that talkpage access be summarily revoked for all of your sockpuppets, provided that they're CU-confirmed. I don't know what else we can do to make it clear to you that you are not welcome here, since you persist in this delusion that you'll be able to show up here at AN or at SPI, insult me and/or other editors, and come up with lies to defend your own actions, and wind up with anything other than yet another block. Incidentally, if you're aware that I'm not attending school at the moment, you're also aware that I'm clinically depressed, in which case you might want to take a nice long look in the mirror, and review your priorities here, and in life in general. — PinkAmpers&(Je vous invite à me parler) 15:41, 23 January 2013 (UTC) (the grandson of a former NYU School of Engineering professor, by the way)[reply]
      • Too many comments here seem related to the use of PC2 as a standard form of protection. There's no consensus for it's use in that way, but it's use on certain articles may be beneficial to the encyclopedia. Maybe it can be used in some circumstances, but in each case should be reviewed to determine whether it's the most appropriate form of protection. Certainly protecting poor quality articles (such as Transdev York, which has now been nominated for deletion) isn't the best solution. Peter James (talk) 01:57, 23 January 2013 (UTC)[reply]
      • Support. The use of PC2 exclusively to prevent blatant sockpuppetry from autoconfirmed puppets (assuming this is what is going on here) seems useful, and a good application of WP:IAR. (I really don't think such protection should be for an indefinite duration, though.) Any further use of PC2 (such as to prevent edit warring) should not occur without broader consensus, as there are broader issues at play in those cases. — This, that, and the other (talk) 11:11, 24 January 2013 (UTC)[reply]
      • Two comments (nothing more, since I already spoke above) — first, Unitskayak's opposition is by itself a good reason to support this move. Second, I'd say that we should only use PC2 when full protection is the only other option; we might as well let reviewers edit as well as admins. Nyttend (talk) 03:43, 28 January 2013 (UTC)[reply]

      Violation of WP:NOSHARE

      It has been brought to my attention at Wikipedia:Requests for comment/Epeefleche#Outside view by IZAK that the account MrJuddsStudents (talk · contribs) is a shared account with multiple different "editors" moved in/out based on them being students of Danjel (talk · contribs). There is a reasoning for why the account is set up that way, but this reasoning is not listed as an approved reason for the sharing. I am bringing this question to clarify if this usage is permitted per the User Name conventions.Hasteur (talk) 04:11, 28 January 2013 (UTC)[reply]

      Of note, there is a discussion at ANI regarding Danjel. Danjel has elected to blank the AN notices from both accounts. Hasteur (talk) 04:12, 28 January 2013 (UTC)[reply]
      As stated on my userpage, students propose edits that they want to make, I then directly supervise their work and take responsibility for the edits. This is necessary to protect their privacy and prevent them from posting from identifiable IP's per WP:CHILD as they are too young to legally own their own accounts, and to create a degree of separation between my work as an editor and my work as a teacher.
      The account is clearly marked in several places as being connected with me, including in the edit notice, and on the User talkpage and vice versa on my userpage. The account has not, thus far, edited outside of its own userspace (where a student was preparing some work for later).
      This is now the second thread started at an administrative noticeboard in retaliation by supporters of Epeefleche, whose conduct I have called into question at Wikipedia:Requests for comment/Epeefleche, at which Hasteur is an active participant. The other thread is Wikipedia:Administrators'_noticeboard/Incidents#Short_term_block_proposal:_User:Danjel. This is now taking the form of WP:HARASSMENT, for the purpose of supporting Epeefleche's cause. Yes, I blanked the notices per WP:BLANKING. ˜danjel [ talk | contribs ] 04:22, 28 January 2013 (UTC)[reply]
      Blanking vs dealing with them (or responding to them) has different perceptions. Blanking suggests that you deny the assertion. I cite your lack of any sort of edit summary acknoledging them instead going for a null edit summary or a system automation indicating reversion. Please indicate how calling the policy question on an account that may have been set up both in violation of laws regarding children and in contravention of wikipedia best practices. WP:CHILD is an essay specifically dealing with protecting children from predators whereas WP:NOSHARE is a policy that has very specific exceptions written into it. None of the exceptions seem to fit the situation here, so yes I think it's wise to call the question in front of a larger community if the account should be prohibited. Hasteur (talk) 04:28, 28 January 2013 (UTC)[reply]
      [edit conflict] Thank you for the explanation, Danjel. What you're doing is definitely not permitted by the WP:ROLE policy. However, I seriously question the idea of sanctioning anyone for this account's behavior — it's being used to protect privacy, it's being done under direct supervision of an experienced editor who's taking responsibility for it, and it's being done in full acknowledgement without an attempt to avoid scrutiny. WP:ROLE was definitely not written for this situation, so let's implement WP:IAR here. Nyttend (talk) 04:30, 28 January 2013 (UTC)[reply]
      Nyttend: cheers. The first sane voice I've heard today. ˜danjel [ talk | contribs ] 04:34, 28 January 2013 (UTC)[reply]
      With the implication that the rest of us are not sane? Care to refactor your statement? Hasteur (talk) 04:36, 28 January 2013 (UTC)[reply]
      Nope. ˜danjel [ talk | contribs ] 04:45, 28 January 2013 (UTC)[reply]
      (edit conflict)*2 Please illuminate how information revealed at the RFC/U that I have acted upon in what I the most prudent method constitues harassment? I echo the sentiments at the ANI thread that it appears you see editors who allign on the side of policy and best practices as being in collusion with Epeeflechee and therefore a WP:BATTLEGROUND. I strongly advise you to step back and give experienced editors and administrators the opportunity to consider your actions with regard to this account. Hasteur (talk) 04:35, 28 January 2013 (UTC)[reply]

      Role accounts are not permitted. Period. It doesn't matter what the purpose of the role account is, it's just not allowed, no exceptions. The editors who are using the account can create new personal acconts, or use IP accounts. There is now convincing reason -- except for avoiding scrutiny -- that they must use the role account. Block, please, for blatant violations of policy. Beyond My Ken (talk) 10:59, 28 January 2013 (UTC)[reply]

      Actually they can't make their own accounts. Or at least, Wikipedia shouldn't let them: COPPA. Hence why it's my account, under my responsibility, and I technically hit the "save page" button. ˜danjel [ talk | contribs ] 11:44, 28 January 2013 (UTC)[reply]
      Every rule has exceptions. The reason for wanting to do this is ... significant, anyhow. I don't know whether it's compelling enough, but it merits discussion. The account doesn't at all allow them to avoid scrutiny. We owe them serious consideration, not just unthinking attempts to feast upon new users. WilyD 11:08, 28 January 2013 (UTC)[reply]
      Unless I'm missing something, the MrJuddsStudents account hasn't been used since September 2011, and the edits which were made under it were restricted to user space (and seem entirely inoffensive, and potentially useful). What's the issue here? - there seems to have been no harm caused by the account (even if it does at least technically breech policy), and no particular barrier to Danjel taking a different approach in the future given that this isn't a 'live' project. Nick-D (talk) 11:24, 28 January 2013 (UTC)[reply]
      Err, it was a group account so an elementary school teacher could easily keep an eye on what all the elementary school aged kids were doing. That seems like a worthwhile goal, although it's technically in violation of policy. Why someone's complaining now, I have no idea. WilyD 11:30, 28 January 2013 (UTC)[reply]
      I know why. As I said above, I've raised an RFC/U against a friend of Hasteur's. This ([the thread at ANI calling for me to be blocked]) seems to be retaliation by drama. ˜danjel [ talk | contribs ] 11:44, 28 January 2013 (UTC)[reply]
      Is iar still a pillar? Yep.
      Was content affected? Nope.
      Is this even a current issue? Nope.
      Should we move on? Yep. NE Ent 11:55, 28 January 2013 (UTC)[reply]

      Here is the contribution list for the account.[9] As you can see, the sole activity in the account is on a page in the account’s user space, User:MrJuddsStudents/List of Antarctica Flora and Fauna, and the last contribution by the account was more than a year ago. Interest in this account only arose during an RfC/U about an unrelated matter. See IZAK's view criticism of children's account. I too suggest moving on. Regards, --Bob K31416 (talk) 16:03, 28 January 2013 (UTC)[reply]

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