Misplaced Pages

:Administrators' noticeboard: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 17:44, 27 January 2013 editDank (talk | contribs)Autopatrolled, Extended confirmed users133,970 edits Need closers for WT:Requests_for_adminship/2013 RfC/1: new section← Previous edit Revision as of 18:25, 27 January 2013 edit undoDicklyon (talk | contribs)Autopatrolled, Extended confirmed users, Rollbackers476,371 edits Continuing topic ban violations by Apteva: new sectionNext edit →
Line 209: Line 209:


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 (]) 17:44, 27 January 2013 (UTC) 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 (]) 17:44, 27 January 2013 (UTC)

== Continuing topic ban violations by Apteva ==

As documented since Jan. 10, Apteva continues to violate the topic-ban that the community overwhelmingly supported, which said (see ):
{{quotation|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:
{{quotation|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 ] :
{{quotation|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: – 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. ] (]) 18:25, 27 January 2013 (UTC)

Revision as of 18:25, 27 January 2013

Noticeboards
Misplaced Pages's centralized discussion, request, and help venues. For a listing of ongoing discussions and current requests, see the dashboard. For a related set of forums which do not function as noticeboards see formal review processes.
General
Articles and content
Page handling
User conduct
Other
Category:Misplaced Pages noticeboards
    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.(archivessearch)

    Start a new discussion

    Template:Active editnotice

    "WP:CR" redirects here. You may be looking for Misplaced Pages:Cleanup resources, Misplaced Pages:Categorizing redirects, Misplaced Pages:Copyrights, Misplaced Pages:Competence is required, Misplaced Pages:Dispute resolution, Misplaced Pages:Content removal and WP:Criteria for redaction. "WP:ANC" redirects here. You may be looking for Misplaced Pages:Assume no clue.
    Noticeboards
    Misplaced Pages's centralized discussion, request, and help venues. For a listing of ongoing discussions and current requests, see the dashboard. For a related set of forums which do not function as noticeboards see formal review processes.
    General
    Articles and content
    Page handling
    User conduct
    Other
    Category:Misplaced Pages noticeboards

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


      Archives

      Index no archives yet (create)



      This page has archives. Sections older than 2 days may be automatically archived by ClueBot III when more than 4 sections are present.
      Shortcuts

      Use the closure requests noticeboard to ask an uninvolved editor to assess, summarize, and formally close a Misplaced Pages 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

      Misplaced Pages:Administrators'_noticeboard/Archive367#RfC_closure_review_request_at_Talk:Rajiv_Dixit#RFC_can_we_say_he_peddaled_false_hoods_in_the_lede

      (Initiated 20 days ago on 5 December 2024) - Ratnahastin (talk) 07:18, 24 December 2024 (UTC)

       Done voorts (talk/contributions) 19:44, 25 December 2024 (UTC)

      Misplaced Pages:Administrators' noticeboard/Archive367#Close challenge for Talk:1948 Arab–Israeli War#RFC for Jewish exodus

      (Initiated 12 days ago on 13 December 2024) challenge of close at AN was archived nableezy - 05:22, 24 December 2024 (UTC)

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

      Requests for comment

      Misplaced Pages:Requests for adminship/2024 review/Phase II/Mentoring process

      (Initiated 224 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)

       Not done I don't think that a formal closure will be helpful given that there are several sub-discussions here on various issues. voorts (talk/contributions) 19:50, 25 December 2024 (UTC)

      Misplaced Pages:Requests for comment/In the news criteria amendments

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

      Talk:Turkey#RfC_on_massacres_and_genocides_in_the_lead

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

      information Note: This is a contentious topic and subject to general sanctions. Also see: Misplaced Pages:Administrators' noticeboard topic. Bogazicili (talk) 17:26, 21 November 2024 (UTC)
      information Note: Not sure if anyone is looking into this, but might be a good idea to wait for a few weeks since there is ongoing discussion. Bogazicili (talk) 16:33, 12 December 2024 (UTC)
       Done voorts (talk/contributions) 00:31, 26 December 2024 (UTC)

      Wikipedia_talk:Talk_page_guidelines#Request_for_comment:_Do_the_guidelines_in_WP:TPO_also_apply_to_archived_talk_pages?

      (Initiated 70 days ago on 16 October 2024) Discussion seems to have petered out a month ago. Consensus seems unclear. Gnomingstuff (talk) 02:34, 11 December 2024 (UTC)

      information Note: Needs admin closure imho, due to its importance (guideline page), length (101kb), and questions about neutrality of the Rfc question and what it meant. Mathglot (talk) 21:28, 16 December 2024 (UTC)
      And in true Streisand effect fashion, this discussion, quiescent for six weeks, has some more responses again. Mathglot (talk) 01:30, 22 December 2024 (UTC)
      {{doing}} voorts (talk/contributions) 23:35, 25 December 2024 (UTC)
      Oops; I put this in the wrong section. voorts (talk/contributions) 00:30, 26 December 2024 (UTC)

      Misplaced Pages:Reliable sources/Noticeboard/Archive 459#RFC_Jerusalem_Post

      (Initiated 58 days ago on 28 October 2024) Participation/discussion has mostly stopped & is unlikely to pick back up again. - Butterscotch Beluga (talk) 21:15, 7 December 2024 (UTC)

      information Note: This is a contentious topic and subject to general sanctions. - Butterscotch Beluga (talk) 21:15, 7 December 2024 (UTC)
      Archived. P.I. Ellsworth , ed.  22:26, 8 December 2024 (UTC)

      Misplaced Pages:Requests_for_comment/Grey_Literature

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

      Option 2 was very clearly rejected. The closer should try to see what specific principles people in the discussion agreed upon if going with a no consensus close, because there should be a follow-up RfC after some of the details are hammered out. Chess (talk) (please mention me on reply) 03:10, 6 December 2024 (UTC)
       Doing...Compassionate727  13:43, 12 December 2024 (UTC)
      @Compassionate727: Still working on this? — Red-tailed hawk (nest) 17:18, 18 December 2024 (UTC)
      Ugh… in practice, no. I'm still willing to do it, but it's in hiatus because of the three(!) pending challenges of my closures at AN, while I evaluate to what extent I need to change how I approach closures. If somebody else wants to take over this, they should feel free. —Compassionate727  22:16, 18 December 2024 (UTC)
      Taking a pause is fair. Just wanted to double check. — Red-tailed hawk (nest) 00:52, 19 December 2024 (UTC)
      asking for an update if possible. I think this RFC and previous RFCBEFORE convos were several TOMATS long at this point, so I get that this might take time. Bluethricecreamman (talk) 16:34, 23 December 2024 (UTC)

      Wikipedia_talk:Requests_for_comment#RFC_on_signing_RFCs

      (Initiated 42 days ago on 13 November 2024) - probably gonna stay status quo, but would like a closure to point to Bluethricecreamman (talk) 06:14, 17 December 2024 (UTC)

      Misplaced Pages:Reliable sources/Noticeboard#RfC: Check Your Fact

      (Initiated 42 days ago on 13 November 2024) RfC has elapsed, and uninvolved closure is requested. — Red-tailed sock (Red-tailed hawk's nest) 15:49, 17 December 2024 (UTC)

      Misplaced Pages talk:Manual of Style/Dates and numbers#RfC Indian numbering conventions

      (Initiated 39 days ago on 16 November 2024) Very wide impact, not much heat. Aaron Liu (talk) 15:30, 23 December 2024 (UTC)

      Talk:List of fictional countries set on Earth#RfC on threshold for inclusion

      (Initiated 35 days ago on 20 November 2024) TompaDompa (talk) 17:50, 20 December 2024 (UTC)

      Misplaced Pages talk:Naming conventions (music)#RfC about the naming conventions for boy bands

      (Initiated 17 days ago on 8 December 2024) No further participation in the last 7 days. Consensus is clear but I am the opener of the RfC and am not comfortable closing something I am so closely involved in, so would like somebody uninvolved to close it if they believe it to be appropriate.RachelTensions (talk) 16:00, 19 December 2024 (UTC)

      I'm not comfortable closing a discussion on a guideline change this early. In any case, if the discussion continues as it has been, a formal closure won't be necessary. —Compassionate727  13:00, 20 December 2024 (UTC)

      Misplaced Pages talk:WikiProject Articles for creation#RfC: Should a bot be created to handle AfC submissions that haven't changed since the last time they were submitted?

      (Initiated 40 days ago on 15 November 2024) This RfC expired five days ago, has an unclear consensus, I am involved, and discussion has died down. JJPMaster (she/they) 22:56, 20 December 2024 (UTC)

      Talk:Len_Blavatnik#RfC:_NPOV_in_the_lead

      (Initiated 9 days ago on 16 December 2024) RFC is only 5 days old as of time of this posting, but overwhelming consensus approves of status quo, except for a single COI editor. Bluethricecreamman (talk) 21:04, 21 December 2024 (UTC)

      The CoI editor has now accepted that consensus is for the status quo, but I think a formal close from an uninvolved editor, summarizing the consensus would be helpful, since the issue has been coming up for a while and many editors were involved. — penultimate_supper 🚀 16:35, 23 December 2024 (UTC)
      yes, despite multiple posts to WP:BLPN, WP:NPOVN, WP:3O, several talk page discussions, and now an RFC, I doubt the pressure to remove word oligarch from the lede of that page will stop. An appropriate close could be a useful thing to point at in the future though. Bluethricecreamman (talk) 16:40, 23 December 2024 (UTC)
       Done by Nomoskedasticity. —Compassionate727  13:30, 25 December 2024 (UTC)

      Template talk:Infobox country#Request for comment on greenhouse emissions

      (Initiated 89 days ago on 27 September 2024) Lots of considered debate with good points made. See the nom's closing statement. Kowal2701 (talk) 09:47, 24 December 2024 (UTC)

       DoneCompassionate727  13:29, 25 December 2024 (UTC)

      Talk:Israel#RfC

      (Initiated 33 days ago on 22 November 2024) Legobot has removed the RFC notice. Can we please get an interdependent close. TarnishedPath 23:08, 24 December 2024 (UTC)

      Talk:Chloe Melas#RFC on allegation of making a false allegation (resubmission)

      (Initiated 31 days ago on 24 November 2024) The bot has removed the RFC notice. Can we please get an independent close. TarnishedPath 23:03, 24 December 2024 (UTC)

       DoneCompassionate727  13:44, 25 December 2024 (UTC)

      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 0 26 26
      TfD 0 0 0 8 8
      MfD 0 0 2 2 4
      FfD 0 0 1 6 7
      RfD 0 0 9 70 79
      AfD 0 0 0 1 1

      Misplaced Pages:Articles for deletion/List of songs recorded by Mohammed Rafi (A)

      (Initiated 25 days ago on 30 November 2024) Please review this discussion. --Jax 0677 (talk) 17:29, 21 December 2024 (UTC)

      The discussion has now been relisted thrice. --Jax 0677 (talk) 00:42, 23 December 2024 (UTC)
       Done voorts (talk/contributions) 00:42, 26 December 2024 (UTC)

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

      Other types of closing requests

      Talk:Arab migrations to the Levant#Merger Proposal

      (Initiated 92 days ago on 25 September 2024) Open for a while, requesting uninvolved closure. Andre🚐 22:15, 20 December 2024 (UTC)

      Talk:LGBT history in Georgia#Proposed merge of LGBT rights in Georgia into LGBT history in Georgia

      (Initiated 80 days ago on 7 October 2024) A merge + move request with RM banners that needs closure. No new comments in 20 days. —CX Zoom 20:16, 10 December 2024 (UTC)

       DoneCompassionate727  14:11, 25 December 2024 (UTC)

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

      (Initiated 70 days ago on 16 October 2024) Experienced closer requested. ―Mandruss  13:57, 27 November 2024 (UTC)

      Talk:Tesla Cybercab#Proposed merge of Tesla Network into Tesla Cybercab

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

      I think it would be better to leave that discussion be. There is no consensus one way or the other. I could close it as "no consensus," but I think it would be better to just leave it so that if there's ever anyone else who has a thought on the matter, they can comment in that discussion instead of needing to open a new one. —Compassionate727  14:15, 25 December 2024 (UTC)

      Talk:Stadion Miejski (Białystok)#Requested move 5 November 2024

      (Initiated 50 days ago on 5 November 2024) RM that has been open for over a month. Natg 19 (talk) 02:13, 11 December 2024 (UTC)

      Talk:JTG Daugherty Racing#Requested move 22 November 2024

      (Initiated 33 days ago on 22 November 2024) Pretty simple RM that just needs an uninvolved editor to close. ―"Ghost of Dan Gurney" (hihi) 17:40, 21 December 2024 (UTC)

       DoneCompassionate727  14:37, 25 December 2024 (UTC)

      Talk:Williamsburg Bray School#Splitting proposal

      (Initiated 28 days ago on 27 November 2024) Only two editors—the nominator and myself—have participated. That was two weeks ago. Just needs an uninvolved third party for closure. ~ Pbritti (talk) 18:37, 13 December 2024 (UTC)

       Doing... BusterD (talk) 20:28, 15 December 2024 (UTC)

      Talk:Winter fuel payment abolition backlash#Merge proposal

      (Initiated 58 days ago on 29 October 2024) There are voices on both sides (ie it is not uncontroversial) so a non-involved editor is needed to evaluate consensus and close this. Thanks. PamD 09:55, 17 December 2024 (UTC)

      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/search/?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)

      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)
      MediaWiki:Pageinfo-footer. 28bytes (talk) 20:36, 18 January 2013 (UTC)
      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)
      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)
      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)
      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)
      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)
      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)
      That link isn't just on the history tab. KTC (talk) 19:18, 21 January 2013 (UTC)
      Depends on the skin; in MonoBook that's the only place I see it. 28bytes (talk) 19:34, 21 January 2013 (UTC)

      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)

      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 Misplaced Pages-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& 21:42, 23 January 2013 (UTC)

      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)
      There's a link to it from the history page. Writ Keeper 03:22, 26 January 2013 (UTC)
      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)
      I believe it's also linked to as "page information" in the toolbox on any page. — PinkAmpers& 08:49, 26 January 2013 (UTC)

      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)

      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)
      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)
      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)
      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)
      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)
      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)
      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)
      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)

      Do we need a site notice regarding the main page update problem?

      We're getting LOTS of repeat questions regarding the main page update problem which is being discussed at this thread, among other places. Every few hours or minutes or so, a new user, unaware of the problem, posts a thread somewhere asking what is going on. Maybe something to the affect of "Yes, we know that there's a problem and we're working on it" may head off some of the questions. Any thoughts or ideas? --Jayron32 15:41, 25 January 2013 (UTC)

      Sounds reasonable -- do we know if it's affecting all the projects or just English Misplaced Pages? If it's all the projects maybe we should kick it to WMF. NE Ent 16:23, 25 January 2013 (UTC)
      Editnotice set. Take it down when needed or if you disagree with the idea of having it there. Nyttend (talk) 17:45, 25 January 2013 (UTC)

      Well that was spectacular -- reformat every Misplaced Pages page for three minutes! Maybe test in sandbox first next time? NE Ent 17:57, 25 January 2013 (UTC)

      • I previewed and nothing appeared to be wrong. Apparently it only applies the coding to the rest of the page (or to other pages) when it actually exists. Nyttend (talk) 18:01, 25 January 2013 (UTC)
      • Ah, don't worry about it - these thing happen. You just have to deal with about 25 IP accounts complaining that the service they don't pay anything for doesn't work ;-) Ritchie333 18:04, 25 January 2013 (UTC)
      • Some things you gotta sandbox, not just preview. Like create in one sandbox and test substitute in another. That said, Ritchie's right, not the end of the world. And most or all of the 25 IPs won't know who to blame. NE Ent 18:10, 25 January 2013 (UTC)

      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)

      • 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 Misplaced Pages: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 17:33, 26 January 2013 (UTC)
      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)

      Images available as a set of tiles

      Was poking around wars that are underrepresented at FP. I don't think this is quite there - it's not exactly a high-EV item, it's sabre-rattling propaganda with an unrealistic composition: http://dl.lib.brown.edu:8080/ImageServer/scrollnav.jsp?filename=1176346232375000.jp2 Still, propoganda has its place in historical documentation, and it's in use. However, when it was uploaded to Misplaced Pages it was cropped. Now, there's reasonable debates to have about including the information outside the main lithograph borders in specific Misplaced Pages uses. However, A. we should have the version with the title and such, which was definitely part of the artistic intent, and B. If the image is tilted, it should be rotated before cropping. If you look on the left of the version we have updated, you'll see a triangular wedge, showing it wasn't rotated to straight before cropping.

      Anyway, the image that led me to the site probably isn't the most valuable on it. Something like http://dl.lib.brown.edu/repository2/repoman.php?verb=render&id=1302200074363500 or http://dl.lib.brown.edu/repository2/repoman.php?verb=render&id=1203005953500000 is probably far more valuable to us - but I get off topic.

      To get to the point: For the common situation where the highest-resolution version of the image can only be downloaded as a set of tiles, what software, people, or alternate message board should I go to? Adam Cuerden 22:03, 25 January 2013 (UTC)

      Not even sure this is the question you're asking, but if you need an extremely high filesize file to be uploaded (past max upload limit), you can file a request in bugzilla for it to be done server side. Legoktm (talk) 22:25, 25 January 2013 (UTC)
      (edit conflict) commons:Help:Zoomable_images is a good place to start, although at a glance it doesn't look like any of the scripts will work with the brown.edu site unmodified. If that's actually the case and you don't feel like coding but are still determined to get an image, you can just get the tiles by hand one at a time and then use Photoshop/GIMP/Imagemagick to stitch them together. VernoWhitney (talk) 22:26, 25 January 2013 (UTC)
      At full zoom, there are literally thousands of images to stitch together, which is effectively impossible to do by hand. Adam Cuerden 22:43, 25 January 2013 (UTC)
      I know ImageMagick handles hundreds of files just fine, so it should be able to do thousands as well, and setting up a script to just download them all as a batch shouldn't be too hard. Was that first file for the 18th Royal Irish the one you were really interested in for right now? VernoWhitney (talk) 22:58, 25 January 2013 (UTC)

      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)

      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)
      An anon-only block on that range should be okay. --(ʞɿɐʇ) ɐuɐʞsǝp 00:09, 26 January 2013 (UTC)
      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)
      Yes. There's some more info at mw:Help:Range blocks. Legoktm (talk) 01:20, 26 January 2013 (UTC)

      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 23:40, 26 January 2013 (UTC)

      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)

      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)
      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)
      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)
      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, 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)

      Ethically, if an editor encounters an article that they think does not belong on Misplaced Pages 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)
      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)
      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 Misplaced Pages'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)
      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 Misplaced Pages'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)
      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 Misplaced Pages. 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)
      • 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 Misplaced Pages is about. Reyk YO! 01:58, 26 January 2013 (UTC)
      • 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 03:34, 26 January 2013 (UTC)
      • 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)
      • In this case, the removal of this was absolutely correct anyway, the article itself isn't the place for claims about its own notability, nor for documentating an imaginary Misplaced Pages "incident". Black Kite (talk) 23:29, 26 January 2013 (UTC)

      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 06:59, 26 January 2013 (UTC)

      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)
      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)
      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 but twice 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)
      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)
      That wasn't the rationale you wrote 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)
      • 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)
      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)

      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 ):

      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)

      Categories: