Revision as of 07:07, 18 February 2012 editThe Devil's Advocate (talk | contribs)19,695 edits →Topic ban proposed← Previous edit | Revision as of 07:14, 18 February 2012 edit undoMONGO (talk | contribs)Autopatrolled, Extended confirmed users, File movers, Pending changes reviewers, Rollbackers76,644 edits →Topic ban proposed: cNext edit → | ||
Line 756: | Line 756: | ||
::::Just so anyone here understands. It was not just that he hatted my comments, but ''how'' he hatted them. Last comment here on this personal dispute.--] (]) 06:27, 18 February 2012 (UTC) | ::::Just so anyone here understands. It was not just that he hatted my comments, but ''how'' he hatted them. Last comment here on this personal dispute.--] (]) 06:27, 18 February 2012 (UTC) | ||
*'''Comment''' As some are wanting me to be clear, I don't see anything more that should or could be reasonably brought to ANI or deletion. You can call it "dropping the stick" if you like, though I see it as all legitimate options being exhausted with regards to this area and the MfD. I should also note that, in the ANI discussion that prompted this proposal, I raised more issues about the DRV close than S Marshall not being an admin. As I had no interaction with the user prior to the DRV I had no reason to think he was in such good standing concerning that space that mentioning his non-admin status would spark the reaction it did. Had I known that, I would have focused on those other issues I had with his closure so as not to offend him or others who know him. All the same, I see no good reason to try and re-argue his closure given the level of support given for it.--] (]) 07:07, 18 February 2012 (UTC) | *'''Comment''' As some are wanting me to be clear, I don't see anything more that should or could be reasonably brought to ANI or deletion. You can call it "dropping the stick" if you like, though I see it as all legitimate options being exhausted with regards to this area and the MfD. I should also note that, in the ANI discussion that prompted this proposal, I raised more issues about the DRV close than S Marshall not being an admin. As I had no interaction with the user prior to the DRV I had no reason to think he was in such good standing concerning that space that mentioning his non-admin status would spark the reaction it did. Had I known that, I would have focused on those other issues I had with his closure so as not to offend him or others who know him. All the same, I see no good reason to try and re-argue his closure given the level of support given for it.--] (]) 07:07, 18 February 2012 (UTC) | ||
*'''Support''' The Devil's Advocate is heading to arbcom sooner or later...disruptive in numerous forums and articles...tedious, time consuming and not here for anything other than general anarchy...folks need to open their eyes...he was on a 30 day topic ban on 9/11 related articles...once the ban was lifted, he resumed his regularly scheduled programming...has two frivilous Wikiquette Assistance requests going on at the same time...been blocked twice in the last 3 months...now disruptive to the ARS...what's next one wonders.--] 07:14, 18 February 2012 (UTC) | |||
=== Motion to close === | === Motion to close === |
Revision as of 07:14, 18 February 2012
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 |
- For urgent incidents and chronic, intractable behavioral problems, use Misplaced Pages:Administrators' noticeboard/Incidents.
- If you are new, try the Teahouse instead.
- Do not report breaches of personal information on this highly visible page – instead, follow the instructions on Misplaced Pages:Requests for oversight.
- For administrative backlogs add
{{Admin backlog}}
to the backlogged page; post here only if urgent. - Do not post requests for page protection, deletion requests, or block requests here.
- Just want an admin? Contact a recently active admin directly.
- If you want to challenge the closure of a request for comment, use
{{RfC closure review}}
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)
Start a new discussion
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 |
This page has archives. Sections older than 2 days may be automatically archived by Lowercase sigmabot III. |
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 |
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
- Misplaced Pages:Requested moves#Elapsed listings
- Misplaced Pages:Articles for deletion/Old
- Misplaced Pages:Redirects for discussion
- Misplaced Pages:Categories for discussion/Awaiting closure
- Misplaced Pages:Templates for discussion#Old discussions
- Misplaced Pages:Miscellany for deletion#Old business
- Misplaced Pages:Proposed mergers/Log
- Misplaced Pages:Proposed article splits
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)
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)
- 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)
- 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)
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)
- 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)
- 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)
- 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)
- @Compassionate727: Still working on this? — Red-tailed hawk (nest) 17:18, 18 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)
- Consensus seems clear, I don't think my Indian-ness poses a WP;COI here, closed. Soni (talk) 22:03, 24 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)
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)
Place new discussions concerning RfCs above this line using a level 3 heading
Deletion discussions
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 79 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)
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)
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
WP:TFD deletions by admin User:Fastily
Probably many of you admins have heard of me since I have been around for quite a while and have done a lot of stuff. Although my main responsibilities are a bit out of the way (WP:CHICAGO, WP:FOUR and WP:WAWARDS) and, generally, I don't like to spend a lot of time in lengthy discussions, I am pretty experienced at them. My two most recent WP:TFD nominations have ended with closures that were surprising to me based on my experience. In January, Misplaced Pages:Templates_for_discussion/Log/2012_January_10#Template:OlivierAward_DanceAchievement was closed one opinion to delete (plus the nominator) and three opinions to keep as a consensus to delete. I spent several days seeking an explanation at User_talk:Fastily/Archive_5#Misplaced Pages:Templates_for_discussion.2FLog.2F2012_January_10.23Template:OlivierAward_... and the long and the short of it was that after a few days of ignoring my queries, he claimed to be happy to explain his decision and felt the proper way to explain such a decision was to delegate the responsibility of explaining it to the nominator. Eventually, the nominator and I agreed that these should be restored with minor modifications based on discussions now located in three places:
- User_talk:Fastily/Archive_5#Misplaced Pages:Templates_for_discussion.2FLog.2F2012_January_10.23Template:OlivierAward_...
- User_talk:Frietjes#Misplaced Pages:Templates_for_discussion.2FLog.2F2012_January_10.23Template:OlivierAward_...
- User_talk:TonyTheTiger/Archive_66#Templates
Today, I found another odd closure decision at Misplaced Pages:Templates_for_discussion/Log/2012_January_24#Template:New_York_cities_and_mayors_of_100.2C000_population when a discussion with four deletes and three keeps was closed as consensus to delete. In my experience at various WP:XFD, even if you count the nominator if 3-5 out of 8 people are on one side of and issue and 3-5 out of 8 are on the other, generally, this is regarded as a no consensus. This particular decision may effect a total of 35 similar templates (most of which are listed at Category:United States mayors templates by state) in the near future. My alternatives are to pursue a WP:DRV. However, since the first step in a DRV is to talk to the discussion-closing editor, I would be back on Fastily (talk · contribs)'s page. He has already expressed a belief that the proper way to explain your decision is to ask the nominator to do so, I feel pursuing that would be fruitless.
I am curious about the closure because there is a possibility that no consensus is no longer considered a discussion resolution. I see my options as follows:
- Accept the decision
- Pursue a WP:DRV
- Find a place to discuss
- whether no consensus is still used in TFD resolutions
- whether Fastily's understanding that the nominator is responsible for explaining a TFD closure for DRV purposes
- whether Fastily may be too aggressive in closing TFD discussions I have been involved in.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 14:41, 7 February 2012 (UTC)
Remember that the number of !votes on either side is irrelevant - the quality of the arguments matter. Number 57 14:51, 7 February 2012 (UTC)
- Indeed; the arguments for keeping the NY mayors template amounted to "It's useful" (without actually specifying how) and "You didn't nominate all these other templates at the same time". Fastily was perfectly justified in analyzing the quality of the arguments rather than just counting numbers. (FULL DISCLOSURE: I nominated the NY mayors template for deletion.) Powers 15:09, 7 February 2012 (UTC)
- The whole point of templates is that they're useful. WP:USEFUL isn't a valid reason for keeping an article, but it's the only valid reason for having templates such as {{Pp-meta}}. Nyttend (talk) 02:42, 8 February 2012 (UTC)
- You might want to read WP:USEFUL again, Nyttend. It says that being useful can be a valid reason for keeping (whether article or not), but it has to be explained rather than simply asserted. Powers 03:00, 8 February 2012 (UTC)
- Umm, navboxes are pretty much always useful for navigating from article to article within related topics, which these are. It's definitely on those advocating deletion to explain why a specific example of such a common type of template is an aberration from the common pattern. Nyttend (talk) 18:30, 11 February 2012 (UTC)
- That doesn't make a simple declaration of "it's useful" in any way a valid argument for keeping. Powers 19:26, 11 February 2012 (UTC)
- Umm, navboxes are pretty much always useful for navigating from article to article within related topics, which these are. It's definitely on those advocating deletion to explain why a specific example of such a common type of template is an aberration from the common pattern. Nyttend (talk) 18:30, 11 February 2012 (UTC)
- You might want to read WP:USEFUL again, Nyttend. It says that being useful can be a valid reason for keeping (whether article or not), but it has to be explained rather than simply asserted. Powers 03:00, 8 February 2012 (UTC)
- The whole point of templates is that they're useful. WP:USEFUL isn't a valid reason for keeping an article, but it's the only valid reason for having templates such as {{Pp-meta}}. Nyttend (talk) 02:42, 8 February 2012 (UTC)
If you disagree with what the closer says take it to DRV. I think you are reading way too much into Fastily asking the nominator to comment. To me it looks like he was fed up of you badgering him, so asked someone else who might be able to explain without getting annoyed at you. I could be wrong of course. Also, you don't have to look very hard to find no-consensus closes by fastily (e.g. http://en.wikipedia.org/Wikipedia:Templates_for_discussion/Log/2012_January_22#Template:Closed_down). Polequant (talk) 15:03, 7 February 2012 (UTC)
- It is hard to disagree with what a closer says if he won't say anything and hard to take it to DRV when the first step is to talk with the closer when the closer won't say anything.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 18:16, 7 February 2012 (UTC)
- Well DRV will in fact hear it in cases like this; and it frequently does get the occasion to hear it, because Fastily does not explain his closes at the time he makes them, and often not on his talk p. either. Considering that a reasonable number of his closes have been overturned there, I don't think his continuing this way is constructive behavior for an admin. For everyone who take s the matter to DRv, there are probably ten who are not willing to undergo the further bureaucracy. Since many of these are people who would be making their first contribution here, closing discussions in this way, let alone avoiding discussing them, is has the effect of discouraging new contributors, at a time when we should be doing everything possible to encourage them (Most of his closes are good, of course, but an editor, especially a new editor, deserves an explanation--a good explanation of why something must be deleted will often keep the editor. Some of this should be dealt with by a rule requiring meaningful rational for non-unanimous XfD closings, but changing deletion process in practice seems to require unanimous consent. In the meantime, we can strongly urge Fastily to change his work habits in this respect. Yes, he wouldn't be able to do as many closes, but there are a few hundred other good administrators. DGG ( talk ) 19:24, 7 February 2012 (UTC)
- I proposed just that a couple of years ago. It was shot down in flames by other admins circling the wagons to defend their own laziness and highhandedness: Misplaced Pages talk:Deletion process/Archive 5#Closing rationales - optional or not?. Fences&Windows 00:32, 8 February 2012 (UTC)
- Well DRV will in fact hear it in cases like this; and it frequently does get the occasion to hear it, because Fastily does not explain his closes at the time he makes them, and often not on his talk p. either. Considering that a reasonable number of his closes have been overturned there, I don't think his continuing this way is constructive behavior for an admin. For everyone who take s the matter to DRv, there are probably ten who are not willing to undergo the further bureaucracy. Since many of these are people who would be making their first contribution here, closing discussions in this way, let alone avoiding discussing them, is has the effect of discouraging new contributors, at a time when we should be doing everything possible to encourage them (Most of his closes are good, of course, but an editor, especially a new editor, deserves an explanation--a good explanation of why something must be deleted will often keep the editor. Some of this should be dealt with by a rule requiring meaningful rational for non-unanimous XfD closings, but changing deletion process in practice seems to require unanimous consent. In the meantime, we can strongly urge Fastily to change his work habits in this respect. Yes, he wouldn't be able to do as many closes, but there are a few hundred other good administrators. DGG ( talk ) 19:24, 7 February 2012 (UTC)
- Dare I suggest that Misplaced Pages:Requests for Comment/Fastily may be in order? If this is a long term, widespread problem then that would seem the next logical step. Beeblebrox (talk) 04:40, 8 February 2012 (UTC)
- AFAIK, this is appears to be a personal vendetta of Tony's. Awhile back, he contested one of my TfD closes on my talk page. I informed him that I would userfy the templates and that I was busy in RL and would provide my reasoning shortly, but he immediately dismissed it as fallacious. Annoyed by the lack of collegiality and respect I was being shown, I asked a participant in the TfD to comment in the meantime. Somehow, Tony perceived this as an attack, and literally accused me of canvassing and conspiracy. At any rate, User:Frietjes was able to work out a compromise, and the templates were moved back to the mainspace. I had believed the matter to be resolved, and so did not feel it necessary to provide rationale, granted that the concern was moot. I've said it before, and I'll say it again. I will always provide rationale for my closures when they involve contentious and/or complicated matters. I do not provide rationales when the result of the discussion is, IMO, unambiguous; nonetheless, I have never had any issues with explaining my closes/correcting errors (with and without publicly stated reasons) when requested. If that approach is so wrong, my god, we'd better start RfCs on some 20 other-odd admins who follow similar procedures. -FASTILY 07:09, 8 February 2012 (UTC)
- You are in some twisted universe where when I note your consistent efforts to close discussions regarding templates I have created as delete, when normal closing procedure would be to either keep or no consensus close them as my personal vendetta. All I am doing is noting your apparent vendetta to close my TFDs as delete even when to do so is non-sensical. You sound like someone explaining to the police officer that the victim's face was in front of my fist as I innocently moved my arm forward repeatedly at high velocity. Then, he went on a vendetta of screaming about how I was abusing him.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 07:26, 8 February 2012 (UTC)
- Lol, if you're determined to resort to personal attacks, my job is done here. Cheers, FASTILY 07:32, 8 February 2012 (UTC)
- Is that a personal attack? I was making an analogy. You have no reason to be running around deleting my templates in contravention of procedures and then claiming I am on a vendetta for pointing out your actions.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 07:42, 8 February 2012 (UTC)
- Lol, if you're determined to resort to personal attacks, my job is done here. Cheers, FASTILY 07:32, 8 February 2012 (UTC)
- You are in some twisted universe where when I note your consistent efforts to close discussions regarding templates I have created as delete, when normal closing procedure would be to either keep or no consensus close them as my personal vendetta. All I am doing is noting your apparent vendetta to close my TFDs as delete even when to do so is non-sensical. You sound like someone explaining to the police officer that the victim's face was in front of my fist as I innocently moved my arm forward repeatedly at high velocity. Then, he went on a vendetta of screaming about how I was abusing him.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 07:26, 8 February 2012 (UTC)
- I hate to say it, because I hold Fastily in high esteem, but his talk page has been on my watchlist for a couple of years, and Beeblebrox is right. This is a regular issue—whether it's files, articles, or templates, somebody seems to dispute Fastily's deletion of something every few days.
Fastily, don't get yourself dragged into a nasty RfC—you need to slow down a little and properly explain your rationale when closing a deletion debate and when people come to your talk page disagreeing with your close. HJ Mitchell | Penny for your thoughts? 08:47, 8 February 2012 (UTC)
- Not only deletions, keeps as well of course. I haven't asked for an explanation of his close of Misplaced Pages:Templates for discussion/Log/2012 January 30#Template:Persondata, but a TfD with that many comments, and with rather divided and lengthy opinions, could do with an argued close (e.g. indicating why it isn't closed as a no consensus instead of a keep, and what the opinion, if any, was about the other elements in the nomination) instead of a simple "keep". I'm planning to start an RfC on this template anyway, so it won't make a huge difference probably, but I felt that the close of that TfD was rather disappointing, not because of the actual result, but the manner it was presented. Fram (talk) 08:58, 8 February 2012 (UTC)
- (edit conflict) @HJ Mitchell, I agree with this sentiment. Just yesterday I had an unclear deletion of an image and Fastily gave an unsatisfactory explanation of the deletion reason and the process followed. I asked for further clarification and I'm still waiting. We can't require everybody to devote time to Misplaced Pages, but administrators should be held to a higher standard since their actions can't be reversed by us entry-level editors. Great power, great responsibility; if Fastily is not willing to explain his actions in detail then s/he should refrain from closing controversial discussions. Diego (talk) 09:04, 8 February 2012 (UTC)
- I cannot comment on any long-term trends, but in this specific case, I think it's clear Tony was being unreasonable in demanding immediate explanations, to the point of checking Fastily's contributions log to see when Fastily had been editing most recently. Can we agree, at least, that if better explanations are required, that they at least be requested in a calm and civil manner? Powers 01:08, 9 February 2012 (UTC)
- Did I say anything uncivil? I was using the contributions log to get an understanding of the likelihood that he was ducking me. He has yet to give any explanation why he considered three keep votes and one delete vote consensus to delete. I continue to await an explanation by anyone who might be able to expalain that one. We may never know since we worked out a compromise.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 01:40, 9 February 2012 (UTC)
- The discussion on Fastily's talk page looked to me like you were badgering Fastily (due, apparently to your own admitted "impatience"). Furthermore, you jumped immediately to the conclusion that Fastily was "ducking" you rather than acknowledging that Fastily might be busy and is volunteering his/her time to this project. Powers 15:47, 9 February 2012 (UTC)
- Did I say anything uncivil? I was using the contributions log to get an understanding of the likelihood that he was ducking me. He has yet to give any explanation why he considered three keep votes and one delete vote consensus to delete. I continue to await an explanation by anyone who might be able to expalain that one. We may never know since we worked out a compromise.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 01:40, 9 February 2012 (UTC)
- comment I'm noticing a trend here. But as it is, I've repeatedly seen Fastily's name come up over disputed deletions and other related matters, and it's beginning to give me a sense of deja vu. There comes a point where we have to stop saying "it's every body else" maybe there is a problem with the way this user is going about things and their process should be improved. I've found him a little quick on the trigger when a cursory examination of something might solve the problem. This comes across as a binary mindset that has gotten other editors in conflicts in the past, often over similar issues.--Crossmr (talk) 14:23, 9 February 2012 (UTC)
- Diffs? - Aaron Brenneman (talk) 02:05, 10 February 2012 (UTC)
- , , here he seems to jump into a situation he just isn't really informed on and revert a bunch of stuff that doesn't need it, while old, this is simply to show that it's an on-going and long-term issue for him, etc. I don't have time right now to paw through the AN/I archives for all the times I've seen his name come up over questionable behaviour, or deletions just my opinion based on the interactions I've had with him and the discussions I've seen come up.--Crossmr (talk) 05:21, 10 February 2012 (UTC)
- Diffs? - Aaron Brenneman (talk) 02:05, 10 February 2012 (UTC)
- In my defense, all of these are extremely old, resolved, and irrelevant to the matter at hand. If anything, I hereby agree to self-abstain from closing long, contentious discussions without providing a statement of some sort. At any rate, I no longer plan on closing such discussions anyways, so I guess that makes the concerns we're having here moot :P Cheers, FASTILY 10:48, 10 February 2012 (UTC)
- Not fair, we won't get our dose of wikidrama now. Diego (talk) 11:17, 10 February 2012 (UTC)
- December 2011 is "extremely" old? You have a rather interesting definition of "extremely". The concerns were not just about closing discussions. This is talking about deletions, so I can't see how this makes anything moot.--Crossmr (talk) 00:27, 11 February 2012 (UTC)
- In my defense, all of these are extremely old, resolved, and irrelevant to the matter at hand. If anything, I hereby agree to self-abstain from closing long, contentious discussions without providing a statement of some sort. At any rate, I no longer plan on closing such discussions anyways, so I guess that makes the concerns we're having here moot :P Cheers, FASTILY 10:48, 10 February 2012 (UTC)
- There may be an issue here that goes beyond closing deletion discussions. I have no particular memory of previously interacting with Fastily, but for what it's worth, I am semi-regularly editing DRV and I remember closing (or commenting in) an uncommonly high number of review requests that concerned an clearly mistaken speedy deletion by Fastily. Sandstein 07:49, 11 February 2012 (UTC)
- Comment Is it appropriate to ask that Fastily explain his reasoning for the two closes that caused me to initiate this discussion.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 18:42, 11 February 2012 (UTC)
- Fastily thankfully deletes a whole lot of things - templates, images, etc. So much so that he has a simple page that describes his reasonings. Typically, if you approach them, they point you there and if you want more info, simply ask for a follow-up ... usually, unless the question is already answered the first time, Fastily is more-than-willing to give some extra explanation. By sheer ratio, I would actually bet that the number of just fine deletions to questionable is better than most of us. Just like the average American has heard of more problems with Plymouth Sunfire automobiles than Jaguar XJC's, it's a matter of quantity for the most part (talk→ BWilkins ←track) 12:51, 12 February 2012 (UTC)
- Unfortunately, in coping with the large number of inquiries about deletion, the boilerplate responses may come off badly with good faith editors who recognise the general concern, but don't understand the specifics as to what was wrong with their article. I understand that this is a wider issue, especially with over-use of warning templates, and I don't necessarily think that Fastly should be specifically highlighted here, but it does seem to cause issues. Otherwise there is no question that Fastly does lots of great work, and the one time I raised a problem it was fixed quickly and without any hassles at all. - Bilby (talk) 13:20, 12 February 2012 (UTC)
- I support the suggestion of an RfC/U on Fastily per the comments here by Beeblebrox and Sandstein above; there have been related problems raised on ANI and with his bot Fbot. In all cases administrative tasks were performed in a mechanized manner without the need to provide careful justification either at the time or later when queried. Mathsci (talk) 17:09, 13 February 2012 (UTC)
- I was troubled by this recent (4 days ago) section at ANI. Article is deleted as G11, the editor asks if they can have a copy, Fastily's response is a link to G11 that ignores the clear request for a userfied version (and then another admin cleans up after Fastily at ANI). If Fastily has enough time to delete a hundred articles, but not enough time to adequately communicate with the users he affects, then Fastily doesn't have enough time to delete a hundred articles. Theoldsparkle (talk) 17:31, 13 February 2012 (UTC)
- In fairness to Fastily, he has done over 170,000 deletions, so this instance and those cited above represent a vanishingly small percentage of his actions and I suspect are in-line on a percentage-basis with all other administrators. He's just doing more work, so more people notice any mistakes. MBisanz 17:46, 13 February 2012 (UTC)
- If the proportion is no higher than others it would explain mistaken deletions; but it also explains, though does not excuse his frequent failure to give adequate reasons or engage in genuine dialog. It would seem to show that he is doing too many deletions to work accurately or keep track or deal with the people involved. Bu I'm not sure that;s true. But that the proportion is no higher remains to be shown. As I take an opposite approach than he, while still finding plenty to delete--though my count is only 8% of his-- I have generally refrained from challenging his deletions, in order to facilitate the necessity of working together. Perhaps others have done likewise. NPP and related activities can not be done accurately fast. DGG ( talk ) 17:30, 14 February 2012 (UTC)
- That is true. I would say he probably is working accurately, but doesn't have time to deal with the people involved. Otherwise, I would agree with you. MBisanz 17:37, 14 February 2012 (UTC)
- That's a huge problem since we're a community after all. We've seen similar behaviour from other long term users that ends up generating endless drama. Often eventually leading to them getting blocked, banned, etc. As DGG said, above he dismissed the links I provided to earlier AN/I discussion claiming they were all "extremely old" and yet one of them is from December. Good faith doesn't extend to time travel.--Crossmr (talk) 00:00, 15 February 2012 (UTC)
- That is true. I would say he probably is working accurately, but doesn't have time to deal with the people involved. Otherwise, I would agree with you. MBisanz 17:37, 14 February 2012 (UTC)
- Comment - This is not related to deleted templates but it's along the same lines. It seems Fastily just speedy deleted the article Aunt Bam's Place under G8. G8 states: Examples include talk pages with no corresponding subject page; subpages with no parent page; image pages without a corresponding image; redirects to invalid targets, such as nonexistent targets, redirect loops, and bad titles; and categories populated by deleted or retargeted templates.. Now, this was an ARTICLE, not a talk page, subpage, image page, redirect or anything of the sort. EVEN IF somehow this article qualified for speedy deletion, G8 is obviously the wrong reason. The thing is that IT DID NOT qualify for a speedy deletion. What has been going on is that an anon IP has been going around monkeying around with articles related to Tyler Perry , and has been repeatedly nominating this page for speedy deletion, seemingly for laughs (or who knows, anyway, "disruptively"). Now I'm not THAT familiar with Mr. Perry's ouvre, and maybe I'm missing something, but "Aunt Bam's Place" appears to be an actual play (by one of the highest paid producers in Hollywood). Unless there's some widespread internet wide hoax going on, the article deserved at the very least an AfD. It's obvious that Fastily didn't bother to check details, or even glance at the subject but just saw a "speedy delete" template and then deleted it. And then made up a bs reason - or at least gave a completely wrong reason - for the deletion. Per discussion above, it's obvious that this isn't the first time this kind of thing happen. And unlike with TonyTheTiger I can't be accused of perusing a grudge here. So either Fastily is a bit out of control, or s/he simply doesn't know what the heck he's doing. Either way this is going towards sufficient reasons for removal of admin tools. Before that happens, how about a topic-ban from deletions (including closing AfDs and speedies) is tried?VolunteerMarek 02:36, 16 February 2012 (UTC)
- That was a fairly silly deletion; just because something is tagged G8, doesn't mean it is a G8. You have to look at it. I've restored the article and its talk page. --Floquenbeam (talk) 02:44, 16 February 2012 (UTC)
- Thanks. I'm starting to think that the "170,000 deletions" is actually a symptom of the problem rather than an indication that everything's ok. You do that many deletions, they're gonna be sloppy. It's very much "quantity over quality" and I don't see a point of trying to up one's deletion/edit count this way if it just keeps causing work for others.VolunteerMarek 02:49, 16 February 2012 (UTC)
- I've seen Fastily around doing good work, also (and only recently) a couple of things I'd have questioned. Maybe it's just perceived "pressure of work"? (I will add, as I often do, that every time I have looked at any deletion process in detail I have seen stuff being deleted that should be kept, this however is not just about deletes.) Rich Farmbrough, 11:35, 16 February 2012 (UTC).
- I've seen Fastily around doing good work, also (and only recently) a couple of things I'd have questioned. Maybe it's just perceived "pressure of work"? (I will add, as I often do, that every time I have looked at any deletion process in detail I have seen stuff being deleted that should be kept, this however is not just about deletes.) Rich Farmbrough, 11:35, 16 February 2012 (UTC).
- Thanks. I'm starting to think that the "170,000 deletions" is actually a symptom of the problem rather than an indication that everything's ok. You do that many deletions, they're gonna be sloppy. It's very much "quantity over quality" and I don't see a point of trying to up one's deletion/edit count this way if it just keeps causing work for others.VolunteerMarek 02:49, 16 February 2012 (UTC)
- That was a fairly silly deletion; just because something is tagged G8, doesn't mean it is a G8. You have to look at it. I've restored the article and its talk page. --Floquenbeam (talk) 02:44, 16 February 2012 (UTC)
- I'd buy that for a dollar. Give his attempt above to misdirect/dance around the issue and these kinds of on-going deletion issues, a break might be in order. If he doesn't want to take it himself, then perhaps he should be encouraged to do so.--Crossmr (talk) 00:30, 17 February 2012 (UTC)
Audit Subcommittee appointments (2012): Invitation to comment on candidates
The Arbitration Committee is seeking to appoint at least three non-arbitrator members to the Audit Subcommittee, and is now seeking comments from the community regarding the candidates who have volunteered for this role.
Interested parties are invited to review the appointments page containing the nomination statements supplied by the candidates and their answers to a few standard questions. Community members may also pose additional questions and submit comments about the candidates on the individual nomination subpages or privately via email to arbcom-en-blists.wikimedia.org.
Following the consultation phase, the committee will take into account the answers provided by the candidates to the questions and the comments offered by the community (both publicly and privately) along with any other relevant factors before making a final decision regarding appointments.
The consultation phase is scheduled to end 23:59, 19 February 2012 (UTC), and the appointments are scheduled to be announced by 29 February 2012.
For the Arbitration Committee, –xeno 04:00, 9 February 2012 (UTC)
Requesting reappraisal of a block
- Edgeform (talk · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
User:Edgeform was blocked a while back as a result of the above SPI. I have become concerned that there are some contradictions in the behavioral evidence of socking, and that a good faith user may, perhaps, have been blocked in error. I've discussed this with HelloAnnyong, the blocking admin, and he thinks that I'm mistaken, which I might well be, but I would be more comfortable if some more eyes would take a look at this. I'm also notifying the two checkusers who have been involved in the SPI. This gets rather complicated, sorry, but please bear with me.
The case centers around the BLP of a San Diego-based neuroscientist, Vilayanur S. Ramachandran, and some of the pages about topics of his research. These topics include autism, which (in ways unrelated to the BLP subject himself) is something that sometimes attracts editing agendas. I originally raised the SPI that led to the block (the second in the archive linked above), based upon an IP edit, , that has a now-hidden edit summary, claiming to be an "edit by , aka Neurorel/Edgeform". At the time, it appeared to be a blatant admission of socking, and the checkuser data indicated that the accounts, including the IP, all geolocated to the San Diego area, with the two named accounts having a shared history of interest in editing in these topics.
I have also been editing the BLP, because my attention was drawn at my talk to content disagreements in which the two named accounts were among those involved. I don't always agree with either Neurorel or Edgeform, but I don't see them editing in bad faith. Their edits tend to have the same point of view, but not necessarily the same writing style. Other editors, who self-identify as being in the BLP subject's San Diego lab, tend to be very sensitive about what they perceive as criticisms of the BLP subject, and these concerns led to an earlier SPI, the first in the archive linked above, and also led to the request in my talk to look at the BLP in the first place.
After the block, an IP claiming to be Edgeform contacted me at my talk, based on my own history of editing in the BLP, and sought my help in overturning the block: here. The edits by the "outing" IP had been rather clumsy, whereas the IP claiming to be Edgeform was reasonably articulate. I discussed it with HA here, and we agreed then that there would have to be a request for block review, which never happened, perhaps because Edgeform gave up.
Since that time, there have repetitively been troll-ish edits from various IPs using public computers in the San Diego area, repeating the "edit by , aka Neurorel/Edgeform" edit summary, see: 1, 2, and 3. However, that third incident, the most recent, was different, in that only Neurorel, and not Edgeform, was named in the edit summary. Googling the supposed real life "", gives two possibly related results: a professional baseball player based in San Diego, and a young boy who has autism and whose mother writes a blog about him. I doubt that either of these persons is actually doing the editing; it could be a third person who just happens to have that name also, or it could be a sarcastic use of the name by a troll. What bothers me is that there seems to be a pattern of repeatedly trying to get both Neurorel and Edgeform blocked, by making these "look at me!" edits that are really just about the edit summary, and that, with Edgeform blocked, the edit summaries have started only naming Neurorel, who is not blocked. It does not make sense to me that a single person would be behind both the Neurorel and Edgeform accounts and also be making these accusatory/boastful edit summaries. It's plausible that the IP is someone else who actually knows of genuine socking, but it is awfully strange that they would be so persistent after the person they are accusing has been limited to a single account. Behaviorally, it seems more like someone else in the San Diego area (perhaps associated with the lab?? – but not the editor who contacted me at my talk, I'm quite sure) who just wants some editors removed from editing the subject area.
I know it's complicated and ambiguous, but I'd appreciate some additional opinions. Thanks. --Tryptofish (talk) 00:09, 10 February 2012 (UTC)
- Looking purely at their use of edit summaries the two are very similar but there are also subtle differences. Both like to use caps and finish sentences/sentence fragments will full stops, Neurorel slightly more consistently. Both prefer double speech marks for quotations. Neurorel makes a few more typos and likes the word "reorganize", whereas Edgeform never uses it. If I was forced at gunpoint to make a decision I'd say perhaps
meatpuppetry or some other form of collusionsimilar interests and points of view rather than socking, but since the effect is the same I doubt it makes very much difference (and I'm certainly not sure enough to want to firmly contradict HelloAnnyong). EyeSerene 12:27, 10 February 2012 (UTC)- Neurorel is not currently blocked, fyi, although the template on their userpage says they are. - Burpelson AFB ✈ 20:11, 10 February 2012 (UTC)
- Let me, then, ask this: If (if!) we think it's more likely to be meatpuppetry than sockpuppetry (which makes sense to me, regardless of whether the accusing IP is acting in bad faith), then does it really make sense to block one account and leave the other account alone? I understand the rationale for socking (limit one user to a single account), but it doesn't seem to make sense for meatpuppets. --Tryptofish (talk) 20:25, 12 February 2012 (UTC)
- timestamp --Tryptofish (talk) 21:59, 14 February 2012 (UTC)
- And remember the principle is against abusive sockpuppetry. Unless these accounts are !voting or revert tag-teaming (which shouldn't happen anyway) there is little issue here, regardless. Rich Farmbrough, 23:35, 14 February 2012 (UTC).
- Both users have been active at Roger Bingham too. I am inclined to give the benefit of the doubt here, despite the similarities in style. It would be easier if the accounts would disclose if there is a relationship. Rich Farmbrough, 23:45, 14 February 2012 (UTC).
- That would certainly clear things up. I tend to agree that we should give Edgeform the benefit of the doubt and unblock. I find Tryptofish's explanation for the IP editor(s) behaviour plausible, and if we have no evidence that Edgeform and Neurorel have been tag-teaming there seems little point in keeping Edgeform blocked. Related to that I've struck some of my earlier comment, which came across rather more strongly that I'd intended. EyeSerene 13:02, 15 February 2012 (UTC)
- Thanks, both of you! I have previously left notes on the talkpages of the two checkusers who took part in the SPI. Tiptoety said that he doesn't currently have anything to add, while WilliamH said that he is looking into it further, so I'd be inclined to give him time to reply here if he should choose to. As for the question of tag-teaming, my observation would be that, although the two accounts consistently tend to reflect similar perspectives about editing the pages that interest them, I really see no evidence of them actually tag-teaming, in the sense of working together at the same time to support one another's edits or talk comments. --Tryptofish (talk) 20:23, 15 February 2012 (UTC)
- Neither did I to be honest, which is why on reflection I struck part of my earlier post. EyeSerene 12:37, 16 February 2012 (UTC)
- timestamp --Tryptofish (talk) 23:26, 17 February 2012 (UTC)
- Neither did I to be honest, which is why on reflection I struck part of my earlier post. EyeSerene 12:37, 16 February 2012 (UTC)
- Thanks, both of you! I have previously left notes on the talkpages of the two checkusers who took part in the SPI. Tiptoety said that he doesn't currently have anything to add, while WilliamH said that he is looking into it further, so I'd be inclined to give him time to reply here if he should choose to. As for the question of tag-teaming, my observation would be that, although the two accounts consistently tend to reflect similar perspectives about editing the pages that interest them, I really see no evidence of them actually tag-teaming, in the sense of working together at the same time to support one another's edits or talk comments. --Tryptofish (talk) 20:23, 15 February 2012 (UTC)
- That would certainly clear things up. I tend to agree that we should give Edgeform the benefit of the doubt and unblock. I find Tryptofish's explanation for the IP editor(s) behaviour plausible, and if we have no evidence that Edgeform and Neurorel have been tag-teaming there seems little point in keeping Edgeform blocked. Related to that I've struck some of my earlier comment, which came across rather more strongly that I'd intended. EyeSerene 13:02, 15 February 2012 (UTC)
- And remember the principle is against abusive sockpuppetry. Unless these accounts are !voting or revert tag-teaming (which shouldn't happen anyway) there is little issue here, regardless. Rich Farmbrough, 23:35, 14 February 2012 (UTC).
- Neurorel is not currently blocked, fyi, although the template on their userpage says they are. - Burpelson AFB ✈ 20:11, 10 February 2012 (UTC)
Are these very long-term blocks on shared IPs really necessary?
I'm beginning to see a big increase in long-term blocks on shared IPs, especially those belonging to schools, colleges, and libraries, but also on other shared IPs. For example, this IP was blocked for three years. Three years! Think about it, high school in the United States lasts for four years; anyone that was a freshman at that school in 2010 will be a senior before they can touch the edit button from that network! This one was blocked for two years in 2011. I understand as much as anyone that administrators and vandal fighters are tired of the bullsh*t that some of these people keep dumping on us, but some of these IPs represent many, many individuals, and anybody accessing our wiki from these IPs are barred from improving our project because of a handful of troublemakers, unless of course they have an account. To be honest, this is beginning to remind me of TK's rangeblocks on Conservapedia, don't get me wrong, I liked TK and I'm proud to be a member of Conservapedia myself, but most agree that the ruthless mass rangeblocks were just too much, and most of those blocks have been lifted because of their potential to negatively impact the project. We're supposed to be the 💕 that anyone can edit, yet some people are unable to edit because their IPs are blocked.
Abuse reports could potentially be a good alternative to these long blocks, I know a lot of people here will say that abuse reports don't work, but I've had great successes with them at Conservapedia and Misplaced Pages. For example, no vandalism has come from this IP since I contacted the school about some vandalism referencing several students' names. The school was very cooperative, and was apparently able to trace down the vandal and punish her/him. Keep in mind that was a small school, so I'm guessing everybody heard about what happened and will not want to follow in that vandals shoes. An abuse report might not stop all vandalism at a larger school, but it can stun it. This IP stopped vandalizing for a month at least after an abuse report. The problem is of course that it probably wasn't the same users vandalizing each time. Enough abuse reports and word might make it around that Misplaced Pages is not to be messed with. Another thing that has been brought up is what if filing abuse report causes problems for someone in real life. Why should we care if John Doe can't go to prom or Jane Doe gets kicked off the cheerleading squad because they vandalized Misplaced Pages? Obviously the vandal doesn't, because (s)he wouldn't be breaking the rules if (s)he did. Unless we're talking about someone in Cuba or North Korea, I would guess that someone would usually get a warning and perhaps something like detention unless they've been in trouble before for internet abuse.
I propose that we limit blocks on shared IPs to one month except where networks outright refuse to cooperate or actively encourage vandalism. But that's just my opinion. PCHS-NJROTC 01:18, 11 February 2012 (UTC)
I propose that we limit blocks on shared IPs to one year, and require ISP/School/Employer/Etc contact before issuing blocks for longer than one month. PCHS-NJROTC 03:19, 11 February 2012 (UTC)
- There's nothing preventing them from creating accounts. The Mark of the Beast (talk) 01:29, 11 February 2012 (UTC)
- My first thought is that I don't like this idea. However, I'm curious: have you ever made an abuse report for an IP, and the vandalism stopped, and productive edits started coming from there? If not, then why in the world would your labor intensive solution be better than a long block? If so, then I'll think about it some more. Three years does seem like a long time, but I routinely make {{schoolblock}}s of one year, and if those switched to 1 month, you would dramatically increase the amount of crap we'd have to deal with. --Floquenbeam (talk) 01:30, 11 February 2012 (UTC)
- I've seen some of these IPs that have had productive contributions in addition to the malicious ones while unblocked, particularly college and university IPs. For example, this one, although never reported for abuse, was blocked for a whole year after a vandalism spree, and it has had a mixture of malicious and constructive edits. PCHS-NJROTC 01:45, 11 February 2012 (UTC)
- Almost forgot, this one, belonging to West Franklin High School, has been to abuse reports and has a mixture of malicious and productive contributions. PCHS-NJROTC 01:51, 11 February 2012 (UTC)
- If three years is far too long, then one month is far too short. It is great to imagine the isolated cases where a new editor might first contribute from one of the problem IPs (positive: more editors), however we should also remember the draining effect on established editors of continuously dealing with the same crap (big negative: known good editors despair and depart). There have been several cases where an obviously mature individual from a school IP has requested that the IP be blocked because the individual is dismayed that their colleagues are damaging the encyclopedia—such potentially excellent editors understand the reason for long blocks and can work around them (make an account; edit from elsewhere). Johnuniq (talk) 02:28, 11 February 2012 (UTC)
- On the contrary. I am quite sure that a large proportion of the "please block my IP, there are many bad people here!" anonymous IPs are just trolls. However, you are right that three years is too long and one month is too short. Thirteen months is a sensible maximum. --Demiurge1000 (talk) 02:38, 11 February 2012 (UTC)
- e/c I imagine there are times when long blocks are the best solution, and yes, filing ARs is tedious, but I think slapping another long, one year (or longer) block on a shared IP not long after another one has expired is the wrong approach; I think it might be more appropriate to start over with a shorter block and escalate back up to a year. As Johnuniq has described, abuse can cause established users anguish, and if an IP is harassing established users, then we need to do anything reasonable to stop the harassment. Something that disturbs me is when I see IPs that were once blocked, and didn't vandalize immediately after the block expired, but when an isolated incident of vandalism occurred, an administrator escalated to a longer block length. Misplaced Pages is supposed to be an open project, and we're supposed to assume good faith, but I can see it getting to a point where most schools and a significant number of universities and libraries are unable to edit Misplaced Pages. That's sad, to me any way. I also have to wonder about the effectiveness of blocking these shared IPs, since it seems to me that if someone wants to vandalize and can't do it at school that they would just do it elsewhere, unless they have no internet access elsewhere. I remember, when I was in high school, I would sometimes correct errors in pages (mainly typos and unnoticed vandalism) without logging into my account because I didn't want to get distracted from what I was doing (usually researching a topic). I imagine a lot of people would be bothered going home or registering an account to fix such things if they don't already have an account here. PCHS-NJROTC 02:57, 11 February 2012 (UTC)
- Also note, I never thought that we shouldn't use one year blocks, I just think that we should at least contact the network administrators to let them know that we've blocked the IP due to abuse and can lift the block if they'll cooperate. Some schools would probably just assume it remain blocked, but it should be our goal to minimize the need for long-term blocks. PCHS-NJROTC 03:02, 11 February 2012 (UTC)
- To answer the question in the header: yes. Absolutely. We frequently get multiple people vandalising from school IPs over a period of time, so reporting to the school and getting one kid detention (if the school bothers to do anything at all) isn't going to solve the problem—there'll be another one, and another one. So we block them, and no matter how long the block is, it's usually not long after it expires that somebody is vandalising from that address again, so it gets blocked again. Renewing the block every few days or weeks instead of every few years would massively increase admins' workload.
By way of a possible counter-proposal, we could allow account creation from schools we block, since it's easy to just indefinitely block any vandalism-only accounts that spring up. But the autoblock on those accounts would still catch anybody who tried to edit from that IP for the next few days. HJ Mitchell | Penny for your thoughts? 03:23, 11 February 2012 (UTC)
- That is a good idea, except the autoblocks are hardblocks (if I'm not mistaken) and could potentially create more havoc for legitimate registered users than the soft-blocks with account creation disabled. PCHS-NJROTC 03:27, 11 February 2012 (UTC)
- As a rebuttal to the notion that abuse reports do nothing as different people would keep vandalizing, we should encourage the IT departments to monitor the contributions from their IP address(es) for vandalism. Assuming they don't have a ton of IPs that they don't even need, it should take about a minute to pull up the contributions page every couple of days and pop every single one of the vandals for policy violations. Sooner or later, all of the users would figure out that vandalizing Misplaced Pages results in the vandal getting in trouble. Personally, if I was director of IT at an educational institution, I would do this and recommend to the principal that their computer access is revoked for the remainder of the school year as most of the ones that vandalize probably engage in other policy violations as well, especially the one's that engage in cyberbullying on here, and the OCD ones that keep coming back for more. It's their job to monitor for such policy violations. PCHS-NJROTC 03:54, 11 February 2012 (UTC)
- Do you have any real-life examples in mind where school authorities have done anything to "monitor the contributions from their IP address(es) for vandalism", to your knowledge? Remember we need a few thousand such instances, for it to be worthwhile... --Demiurge1000 (talk) 04:12, 11 February 2012 (UTC)
- Someone, supposedly a cheerleader from what I've heard, got caught vandalizing Misplaced Pages in another high school in the local school district in '06, seemingly without Misplaced Pages even contacting them (and I'm still not sure if it was someone at the district or that school that caught them). This is what she did the next day, and the district blocked all of Misplaced Pages as a result. Obviously that's something we should stress that they do not need to do to stop the vandalism, and that we can manage the vandalism at our level without them needing to block all access. Additionally, when I was on the phone with an IT department for a school district in Illinois regarding Conservapedia vandalism, the IT person mentioned that they had similar problems with Misplaced Pages and dealt with it; apparently that school district would revoke the vandals' internet access for the entire school year over it. Also, I've seen evidence of action taken when vandals have sent me harassing messages from somewhere else after I reported them, in one case when I reported them to their DSL provider at home, and in one case when I reported them to their cellular provider. PCHS-NJROTC 04:28, 11 February 2012 (UTC)
- (Per your notice on my talk), PCHS-NJROTC, I would love to stop blocking those schools and restart my writing. The current reality is that we don't have enough admin-hours even to amply warn and block, let alone contact the schools - i.e. we never know how many good editors do we scare away by blocks (surely we do), but we do know how many vandal edits come out from there. Further, more and more single-purpose accounts are being created recently for vandalism only (i.e. they are prepared to spend time on registration). A solution is more than welcome, but it needs proper thinking and a wide community discussion. Reaching out to IT departments is certainly a good idea, but I and most other admins simply do not have time for that (can WMF/ambassadors help there? - it is a top priority after all). I did have first-hand experience teaming with a college sysop to catch local Napster spam - he was a dedicated sysop and managed to identify real people with IPs in real time, but I saw how tricky that was. Materialscientist (talk) 04:10, 11 February 2012 (UTC)
- I'm glad to see some openness to my idea, and I do understand that ISP is a cumbersome task; I do a lot ISP contacting for Conservapedia and it does take time to research everything and try to get them to work with you, and trying to work that in along with a job can seem damn near impossible at times. I also know that persistant vandals are annoying; I've been here since 2007 and have seen plenty of them. PCHS-NJROTC 04:18, 11 February 2012 (UTC)
- I've only once contacted anybody over vandalism: it was for this edit (note that it's been revdeleted; sorry, non-admins), and I got cooperative responses from a school admin, a police officer, and the kid that was responsible. Nyttend (talk) 04:50, 11 February 2012 (UTC)
- I usually make contact whenever someone goes bashing other people, like that girl (I assume that it was a girl based on the edit) in Indiana that's rev deleted, but that's not the only times. PCHS-NJROTC 05:00, 11 February 2012 (UTC)
- I've only once contacted anybody over vandalism: it was for this edit (note that it's been revdeleted; sorry, non-admins), and I got cooperative responses from a school admin, a police officer, and the kid that was responsible. Nyttend (talk) 04:50, 11 February 2012 (UTC)
- Something else I'd like to add is that it's not always schools that end up in this situation; I recall coming across an IP belonging to the United States Department of Homeland Security that was producing very childish and vulgar edits like the ones we see from schools, and it was on the fast track to getting blocked like the schools do. The sad thing is that it was obviously one person doing it and there were many other contributions that were legitimate from the IP, but I sent a report to Sprint's abuse contact (since it was through Sprint) and the vandalism ceased. This was sometime between '07 and '09. PCHS-NJROTC 05:00, 11 February 2012 (UTC)
- Then why not continue blocking IP's the way we have been doing all along, but if someone wants to contact the school, and it results in a satisfactory response, we can just lift the block? If it works, it's almost the same effect as contacting the school first. If it doesn't, then there's no harm done. --Floquenbeam (talk) 16:53, 11 February 2012 (UTC)
- Students in schools will vandalize on the internet, and most schools do have a policy about this, but unless they actually censor outgoing traffic, it is very hard to stop them; bored students in a computer lab will try anything. Some schools I've known sometimes try to ignore the problem, some try to come down much too hard. I am reluctant to involve school administrators except in truly exceptional cases, because all too few of them are likely to take a reasonable course of action. I think long-term blocks on schools are inhibiting good faith would-be contributors as well as the others, and we need those contributors. A short term block to stop a major campaign of harassment makes sense, but long term inhibits sensible participation also. We can deal with vandalism much better than when the practice of school blocks began: we have the edit filters, which has reduced vandalism in general very considerably, and the response of anti-vandalism patrol for the ones that get through is usually very fast. We just don't need this. I suggest we end all such blocka at the end of the current school year, and see again what happens in September. DGG ( talk ) 19:40, 11 February 2012 (UTC)
- Considering the block logs of those two IPs that you link to, I would say yes. Absolutely were the lengthy blocks necessary. I understand from a non-admin's perspective these may seem bizarrely long or excessive— I had a question on my RfA about unusually long blocks and I said something along the lines of "I would rarely, if ever, impose a lengthy block". I couldn't have been more wrong. Just working intermittently at AIV in my few months as an administrator, I've had to impose seven two year blocks and one three year block. These situations are far more common than you may realize. Also, we already have an abuse response team. Nothing's stopping our non-admin vandal fighters from going to them. Swarm 22:36, 11 February 2012 (UTC)
- WP:ABUSE has been around for quite some time, and I was actually a member of the abuse team for a while. Unfortunately, it's horribly insufficient in my opinion; it's always required IPs to have been blocked at least five times, and now it requires that an IP has been blocked for a year at least once. PCHS-NJROTC 03:44, 13 February 2012 (UTC)
- Most school IPs that I've warned or blocked have never contributed a single productive edit, so there's no loss to Misplaced Pages when they are blocked. Furthermore, I figure that with most long-term school blocks, Misplaced Pages is doing the school's faculty a favor, as the kids are not supposed to be editing Misplaced Pages while in the computer lab, and once editing is blocked from an IP, editing Misplaced Pages becomes one less distraction available to the bored kids in the computer lab. --Orlady (talk) 22:24, 11 February 2012 (UTC)
- In my opinion, Orlady's second sentence hits the nail on the head: I've encountered what she mentions in the first sentence, but the second has never occurred to me. Why should we tolerate behavior that's already problematic if it's prohibited by the school's rules in the first place? My first thought is that this idea is contrary to our policy of encouraging editing by people in countries where Misplaced Pages is restricted, but I then remember that there's a massive difference between editing around government censorship that harms the whole society and editing around simple school rules that don't hurt anyone. Nyttend (talk) 02:00, 12 February 2012 (UTC)
- This idea assumes all contributions from shared IPs are happening during class time/work time when students/employees are supposed to be studying/working. In high school, I used to edit Misplaced Pages from the library during lunch time, using a work around to access Misplaced Pages that only a few people knew about. The school administrators and district IT were okay with this. Every situation is unique. PCHS-NJROTC 00:19, 13 February 2012 (UTC)
- By the way, that comment I posted from a shared corporate IP while on a lunch break, which is allowed by policy. PCHS-NJROTC 03:44, 13 February 2012 (UTC)
- We can only judge IPs (or ranges) on their edits, and trying to second-guess whether there are multiple people behind the edits can often be a wild goose chase. If a school IP produces a hundred vandal edits, I don't care whether it's a hundred different student or just one persistent student; the net result from en.wikipedia's perspective is the same, and the 101st edit is extremely unlikely to be productive in either case. Similarly, if the IP has made a mixture of positive and negative edits, we can't distinguish between a mixture of good/bad students, or just one Jekyll & Hyde student; in either case, a short block might be an appropriate reaction to a sequence of bad edits. bobrayner (talk) 00:34, 12 February 2012 (UTC)
- Yes We already have more than enough headaches with Vandalism. It takes a significant amount (or very disturbing) of non-productive editing to get an IP editor a block. I do however recognize the need for parole, therefore if the address has done enough to get a longer duration block (more than 6 months) that the block be limited to expire prior to the start of a new "term" for the educational institution and no more than 1 year for non-educational institutions. The purpose is to allow peer/community pressure to influence the bad apples to clean up their act. Hasteur (talk) 00:45, 13 February 2012 (UTC)
- I'm on the fence about this one. On the one hand, I agree with you, Hasteur, that having the school blocks expire at the end of the school term would be nice. The only reason I'm not 100% behind this is that, assuming the vandalism patterns don't change, every August/September the community will have to deal with all the vandalism, and the admins will have to deal with re-blocking all the schools. This is a potentially huge pile of work at the start of every school term. I'm very tempted to say "let the kids who want to edit either do it at home, or register an account." I get that we are the encyclopedia that anyone can edit, but that shouldn't come at the expense of being the encyclopedia that anyone can freely vandalize. If someone can show me why using another IP or registering an account is too high a bar, then I'll change my mind, but otherwise I can't support changing the existing procedures for school blocks. Livit⇑/What? 14:45, 13 February 2012 (UTC)
- I agree with all the admins here that vandalism is a pain, but my thoughts are that we are supposed to be an open wiki that assumes good faith. I'm usually pretty conservative and support blocking, but of kids want to vandalize, there's nothing stopping them from doing it at home or from a mobile device, so why long term block the schools and keep constructive editors from editing? -PPCHS-NJROTC 208.62.154.8 (talk) 17:00, 13 February 2012 (UTC)
- Users who wish to edit constructively via a school computer can do so simply by logging in under their own account. Rklawton (talk) 17:05, 13 February 2012 (UTC)
- If they have an account or are willing to create an account.
208.62.154.85 (talk) 14:36, 14 February 2012 (UTC)Forgot to log in. PCHS-NJROTC 14:38, 14 February 2012 (UTC)
- If they have an account or are willing to create an account.
- Either the student (and I pray it's not Faculty/Staff) will either mature and learn not to vandalize or they will graduate. My thoughts for non college level is something like 3~4 months so that at the start of Fall/Spring terms the educational institution is given a limited leash. With the history we keep we can spot trends early on. For College Level I see more of a Fall/Spring/Summer rotation. Yes it means more disruptive editors for a few weeks and a few Administrator headaches to sort out the vandals, but also demonstrates our AGF that the disruptive elements have moved on to other forums for their trolling needs. Hasteur (talk) 22:28, 13 February 2012 (UTC)
- You do realize that new students enter schools every year, right? Kids will be doing this every year in perpetuity. — The Hand That Feeds You: 23:29, 13 February 2012 (UTC)
- Surely we can make the AGF assumption that the entire school isn't filled with students who get their kicks by vandalizing WP. It's the reason why we have the 6 and 12 month reviews on long term blocks, because we assume that people will change and are willing to correct their behavior. Hasteur (talk) 13:25, 14 February 2012 (UTC)
- Which is difficult when virtually the only edits from a school are vandalism. By the way, between British schools starting summer vacation around the end of June, and American schools (and some British) going back mid-August or so, there isn't much time the schools in these two countries aren't open. And as someone who does a lot of school templating, can I ask people to check IPs more with WHOIS to see if the IP is a school. Dougweller (talk) 15:04, 14 February 2012 (UTC)
- Surely we can make the AGF assumption that the entire school isn't filled with students who get their kicks by vandalizing WP. It's the reason why we have the 6 and 12 month reviews on long term blocks, because we assume that people will change and are willing to correct their behavior. Hasteur (talk) 13:25, 14 February 2012 (UTC)
- You do realize that new students enter schools every year, right? Kids will be doing this every year in perpetuity. — The Hand That Feeds You: 23:29, 13 February 2012 (UTC)
- I'm on the fence about this one. On the one hand, I agree with you, Hasteur, that having the school blocks expire at the end of the school term would be nice. The only reason I'm not 100% behind this is that, assuming the vandalism patterns don't change, every August/September the community will have to deal with all the vandalism, and the admins will have to deal with re-blocking all the schools. This is a potentially huge pile of work at the start of every school term. I'm very tempted to say "let the kids who want to edit either do it at home, or register an account." I get that we are the encyclopedia that anyone can edit, but that shouldn't come at the expense of being the encyclopedia that anyone can freely vandalize. If someone can show me why using another IP or registering an account is too high a bar, then I'll change my mind, but otherwise I can't support changing the existing procedures for school blocks. Livit⇑/What? 14:45, 13 February 2012 (UTC)
- In my experience, other than one hugely helpful sysadmin I ran across a few years ago, no-one is interested in abuse reports and nothing gets done about them. However in principle I'd support a maximum block length for known educational institutions of perhaps six months as a compromise. EyeSerene 13:37, 15 February 2012 (UTC)
I am one of the admins who hands out such blocks as well. I do that generally only after the editor has been blocked a good handful times, and they are schoolblocks. I see often cases, and one of the cases above (Special:Contributions/204.193.118.11, blocked by Materialscientist) is a good example, where there are two 6-month blocks. The first 6-month block ends on the 2nd of June (six months from the 2nd of December). Their first edit: this on the 3rd of June. Then there is summer holiday (nothing from the 30th of June until the 26th of August), but on the 31st of August the editor gets blocked again for 6 months. After that block ends (28th of February) the first edit is a vandalism edit on the 3th of March with this. Between the last 6 month block, and the next 2 year block, there is about 2 weeks. In those two weeks, there is NOTHING but vandalism. It also suggests that the editors keep trying to edit while blocked - how else do you figure out that you can vandalise so fast after a block ends. I share the sentiment that those IPs are used by schools with kids, and in half a year there will be another group of kids sitting there who may be willing to work constructively. But fact remains that it is either a 2 year block, or 4 6-month blocks in short succession. The vandalism, unfortunately, will not stop. I would be in favour of checking whether IP blocks over 6 months of length still target the same institution every 6 months, sometimes IPs do change. For the rest I believe that our editors have better things to do than to run after bunches of schoolkids who (seen that the vandalism starts sometimes so fast after a block ends) do nothing but try to vandalise Misplaced Pages. --Dirk Beetstra 14:08, 15 February 2012 (UTC)
- I'm seeing a lot of people speak of different kids causing problems all the time, but this morning I was reminded of one of the main reasons I brought this proposal here. If you analyze the vandalism coming from IPs that aren't constantly under a school block, like this one, it often appears that most of the vandalism comes from one individual or a small handful of individuals that are addicted to vandalism. Never mind the fact that educational and corporate IPs often represent 1,000+ users. It's so obvious that one person has been behind a lot of the vandalism from that IP because there were incidents on 02/15/2012, 02/10/2012, and 11/16/2012 where similar incidents of vandalism occurred; a notable person's name was replaced with a person with a particular last name, the more recent ones being female and the one from November being male. What are the chances that these two are related? What are the chances that one of them is responsible for the vandalism? Those posts should probably be oversighted, but may I ask that they are not oversighted until I can send links to logs of the abuse to the technology department at that school district tomorrow? Granted that IP has engaged mostly in vandalism, but you might notice there are a few good edits in there; I've seen other IPs that had been under constant school block where the vandals must have moved on and several constructive contributions were generated as a result of the blocks expiring. When shared IPs of any nature (not just schools) are constantly under a schoolblock or an anonblock, how would we know what constructive contributions have been thwarted? PCHS-NJROTC 03:15, 16 February 2012 (UTC)
- This has gone on long enough. If you have spotted edits that should be oversighted, please send the diffs to the oversight mailing list (Email this user at User:Oversight will do fine). PCHS, these IPs are soft-blocked in most cases; the students can go and start accounts at home or they can request an account through account creation. If there is classroom-approved editing, teachers and school officials can make arrangements to have accounts created for their students. Deliberately leaving edits in article histories that ought to be suppressed for the purpose of trying to get someone punished at their school is contrary to what this project is about. Risker (talk) 04:48, 16 February 2012 (UTC)
- Yes, sometimes schools have over 1000 users, but most don't edit. According to wp:About we have over 16 million registered users, of whom only about 90 thousand are regular editors. If that ratio holds, such a school might have six editors. Forcing these six to register in order to edit from school is not that odious a price for keeping vandalism in check. LeadSongDog come howl! 05:54, 16 February 2012 (UTC)
- LeadSongDog has hit the nail on the head. Having been through such a school environment in the not-too-distant past, I can tell you that the vast majority of students who use Misplaced Pages at school (for projects, etc.) couldn't give a rat's ass about editing. A fair number of those who edit do so maliciously; I can recall one instance where I was editing a page during class and several guys sitting near me thought it would be great fun to vandalise that page just for kicks. And those who wish to edit productively are quite receptive to creating an account (seriously, not that hard). While this proposal is well intentioned, I am not convinced that it presents a realistic view of the situation at all. ~~ Lothar von Richthofen (talk) 06:44, 16 February 2012 (UTC)
- Yes, sometimes schools have over 1000 users, but most don't edit. According to wp:About we have over 16 million registered users, of whom only about 90 thousand are regular editors. If that ratio holds, such a school might have six editors. Forcing these six to register in order to edit from school is not that odious a price for keeping vandalism in check. LeadSongDog come howl! 05:54, 16 February 2012 (UTC)
- This has gone on long enough. If you have spotted edits that should be oversighted, please send the diffs to the oversight mailing list (Email this user at User:Oversight will do fine). PCHS, these IPs are soft-blocked in most cases; the students can go and start accounts at home or they can request an account through account creation. If there is classroom-approved editing, teachers and school officials can make arrangements to have accounts created for their students. Deliberately leaving edits in article histories that ought to be suppressed for the purpose of trying to get someone punished at their school is contrary to what this project is about. Risker (talk) 04:48, 16 February 2012 (UTC)
PCHS-NJROTC, you are right, but whether there is one person behind an IP, or 1000 behind one IP, if all the edits that we see here are vandalism, then this is, unfortunately, the only solution. I try to go through the edits since a last block and see if there are a significant number of non-vandalism ones, but sometimes IPs remain unblocked for a month or 2, there may be only 1, maybe 2 reasonable edits, and 100 plain vandalism ('Gary was here', 'Lizzy is a moron', 'poop!' - and way worse getting into BLP type issues 'Our teacher, Mr John Doe, is screwing Jane Doe!'). In perspective, the damage that the kids sometimes, unknowingly, can do is quite big. Yes, sure, such block may hit an occasional good editor. Do note that we do block regular editors sometimes if they go on a bad spree - editors get banned by ArbCom because they are deemed 'a net negative' - that does not mean that they do not do good work, many do good work, and can return after the block/ban expires. Those editors are after that on a short(er) leash (for a while), school IPs have the same, they get blocked for vandalism, if vandalism continues (on a significant scale) after the block expires, they will just be reblocked. Good editors are unfortunately forced to create an account (for instructions they can see the block message), those who have an account can just edit on without problem, and I hope that some who want to edit and can't ask the organisation to have a look what is going on, and get awareness that their fellow students are causing Misplaced Pages to block them, and I hope that the organization then does something about it (but I am afraid that is an idle hope). --Dirk Beetstra 07:03, 16 February 2012 (UTC)
- Did you see the block log on the 208 IP? It is epic. There are 14 blocks. When the 1 year block first went down, the IP was blocked again within 2 days of its release. And after that one, within the next 2 days. The next block was exactly what the OP's talking about I think, which is to be conscientious about school schedules when doing school blocks: it was 8 months long. And it stayed quiet during the summer. But blocked again by November, and after that one, vandalizing within 4 days. That's just an example.
IPs don't get blocks this long unless there's a long history. The history stretches over 5 years on that one too. Either there's some really bad student there, or the vandalizing is done by multiple people over multiple years. While I'm sympathetic to the idea of school year duration blocks, if a block of 1 year is appropriate it's because the IP has a long history. Usually I suspect it's due to 1 IP representing lots of students. Allowing login edits is probably the best response in this case.
I also agree with DGG that we've gotten a lot better about monitoring a lot of vandalism. With that in mind I would encourage blocking admins to look at the nature of the vandalism. If it's stuff that ClueBot's going to catch, then shorter blocks are acceptable, because the workload they create is smaller. But persistent, malicious, and subtle vandalism needs longer blocks since they extract a higher cost. Shadowjams (talk) 22:23, 16 February 2012 (UTC)
- I'm actually very familiar with the history of abuse from the Lely High School IP address; finding its listing at WP:ABUSE in search engine results was how I learned about so-called Misplaced Pages vandalism back in 2007. In 2007, not only was it vandalizing Misplaced Pages, but it was also spewing out spam emails until I notified the school of those activities. Some IPs probably have several vandals whereas some IPs have one person vandalizing a lot; in the case of lhs.collier.k12.fl.us, there's no way that a person who vandalized in 2006 would still be there now unless a> it's a faculty member, or b> it's a student that was held back two years, so it's very likely that it's different individuals in that case.
- Indeed, that IP has a bad history, but I expect we'd have similar problems if major ISPs like Centurylink and Comcast had one IP to represent entire zip codes. Anyone remember the problems we had with AOL? I wasn't here for that, but I've read about it, and we never did one year blocks on AOL that I know of. PCHS-NJROTC 00:51, 17 February 2012 (UTC)
- That's because AOL used like 6 proxies to represent a /10, which is 4 million IP addresses. Not even close to the same thing. J.delanoyadds 01:01, 17 February 2012 (UTC)
Template:Rescue
Having been deleted following Misplaced Pages:Templates for discussion/Log/2012 January 13#Template:Rescue, the deletion reviewed at Misplaced Pages:Deletion review/Log/2012 January 27 the template has been re-created, I have taged to for WP:G4 (which was removed with the edit sum Its no longer been added to anything. I don't think you can speedy delete it. No harm in leaving it for historical reasons and to prevent broken links) I then restored it to the Deteted template messages version which has also been reverted. Can a administrator please look into what's going on and protect the page. Mtking 00:26, 12 February 2012 (UTC)
- Historical retainment of templates (and many other things) is commonplace. It is clearly not meant to be in use, as it states on the page, but is retained so that old page revisions that would contain it do not have broken links instead. I don't see the problem here. Historical things shouldn't be deleted. Silverseren 00:29, 12 February 2012 (UTC)
- Mtking, not sure you realize, but the rescue template is wrapping inside of a template of it's own that marks it as an old template on any pages it's used on. Go try to use it in the Sandbox and see for yourself.--v/r - TP 00:40, 12 February 2012 (UTC)
Sorry, but no, the ARS should not be allowed to retain it in this fashion like some sort of martyr's rock. If it is to remain as something other than a redlink, then it should be clearly labeled as a deleted template and not still fly the lifesaver imagery. Tarc (talk) 00:48, 12 February 2012 (UTC)
- Tarc, that seems a bit harsh. We don't need to hold over their head our 'victory' in TfD and DRV. The template is clearly marked and wraped in another template that prevents it from being used. It only exists in this fashion to prevent the redlink {{rescue}} in old revisions of articles.--v/r - TP 00:50, 12 February 2012 (UTC)
- Why is the "This template is deprecated" text not enough? Reyk YO! 01:02, 12 February 2012 (UTC)
- Agreed the "This template is deprecated" text is enough, it is not as if the template contains any information that related to the article it was placed on. Mtking 01:16, 12 February 2012 (UTC)
- Note. Due to the (silly) ongoing edit war on the template, I have just protected it for three days. I'm off to sleep now; fellow admins, feel free to unprotect without asking me should a consensus emerge here. Salvio 01:20, 12 February 2012 (UTC)
Shouldn't {{Tdeprecated}} be used in these cases? →Στc. 01:35, 12 February 2012 (UTC)
- I don't think so: it says that the deprecated template has been replaced by another one, while it was my impression that the TFD said that this one should be removed and not replaced. Nyttend (talk) 01:46, 12 February 2012 (UTC)
- Keep Its not being used any longer, nor hurting anything at all. What possible reason would there to be to destroy it? You won. You somehow got enough people to show up to convince the opinion of the closing administrator to prevent it from being placed on any articles in need of Rescue. For historical places that link to it, its best to show what it was, instead of a dead red link. Dream Focus 01:49, 12 February 2012 (UTC)
- This isn't a deletion discussion; you don't need to add a vote to your comment. By the way, is this edit considered simple enough and housekeeping-like enough that it's appropriate while the template is protected? I immediately self-reverted; the only reason I did it was to make it easy for you to understand what I'm asking about. Nyttend (talk) 01:50, 12 February 2012 (UTC)
- I don't think it much matters either way on the categories. Those categories could only show up if the template was transcluded from a live page with a revisionid older than the template deletion. Since all such transclusions were removed, these categories can never show up on a live version of a page because any new edits will have a higher revisionid. --Tothwolf (talk) 03:15, 15 February 2012 (UTC)
- I'm sorry, but this is an obvious G4 speedy. Kept because article histories contain its usage? Seriously? There are literally hundreds of deleted templates that show up as redlinks in article histories. I'd like to see a very good reason why this one deserves special treatment. Resolute 01:54, 12 February 2012 (UTC)
- I agree. There doesn't seem to be any real need to keep it around, other than some kind of shrine. Reyk YO! 01:58, 12 February 2012 (UTC)
- We generally delete templates because they're unfixable, because they're redundant, because they're unused and won't be used, or because they violate core policies. As this one was deleted because of the way it was frequently used, rather than because of a design problem or because it was never used, deletion isn't as helpful of a solution. The discussion's goal was to ensure that this template wasn't transcluded or substed in other namespaces; its preservation with the notice of deprecation will go along with the result of the TFD without causing the problems with tons of article histories that would result from deletion. Nyttend (talk) 02:13, 12 February 2012 (UTC)
- One of the prominent arguments in the deletion debate was that this was redundant to the real AfD template. Also, this is now unusued and won't be used. So tell me again why this shouldn't be speedy deleted? Resolute 05:42, 12 February 2012 (UTC)
- If you look at the discussions at AFD and DRV, it's clear that the consensus was not for pseudo-deletion or faux-deletion, but for deletion. How is this not a {{db-repost}}?
Tangentially, I tagged {{ARS/Tagged}} and {{Afdrescue}} for CSD yesterday (although the former was removed, for some reason). Both of them should go to the same place that {{ARSnote}} is now, and where {{rescue}} ought to be. Dori ☾Talk ⁘ Contribs☽ 02:27, 12 February 2012 (UTC)
- As soon as it is unprotected, I will file another TfD, then. This isn't about lording over ARS...if I wanted to do that I would have joined the recent ANI attacks against their deletion discussions...it is about respecting the consensus of the Misplaced Pages community. The consensus was that this thing should be deleted, not left intact with some weird "we won't use it" pledges. Tarc (talk) 03:53, 12 February 2012 (UTC)
- And shit like this is why ARS has the reputation it does. Creating nothing but pointless drama. Resolute 05:40, 12 February 2012 (UTC)
- Question Do we keep other old transcluded templates to help make sure previous versions of articles appear correct? If or if not, why is
{{rescue}}
special such that it should deviate from the norm? In other words, can we de-politicalize this and look at the underlying (at least, as stated) issue. Jclemens (talk) 04:02, 12 February 2012 (UTC)
- Templates are routinely deleted without any consideration as to how they will make old versions of the page look. I happen to think that's a mistake (it is probably technically feasible to have articles display the template as it looked at the time the revision was made, even if the template has been edited since), but common practice is what it is at the moment. NW (Talk) 04:19, 12 February 2012 (UTC)
- In this case since the template added nothing of significance to the article, why not just have it produce "white space" then fully protect the template. Mtking 06:26, 12 February 2012 (UTC)
- Jclemens' question is the relevant one here. I've never seen a deleted template get re-created for the sole purpose of ensuring that old revisions look nice. It may be that it happens from time to time and I've never come across it, or it may be that it happens rarely or never. If it does happen from time to time, I highly doubt it would happen on something that doesn't affect the content of an article, like a maintenance template. I can't imagine it would ruin someone's day to see Template:Rescue on an old revision instead of the life-preserver template. If this type of template re-creation is truly as uncommon as I think it is, then I see no reason to apply special treatment to this particular template. —SW— 08:58, 12 February 2012 (UTC)
- Right, who cares if our articles look like crap, as long as the bureaucratic niceties are preserved? Beyond My Ken (talk) 12:50, 12 February 2012 (UTC)
- It's old article revisions. They arn't exactly pretty with or without the template because of that big red bar at the top. I personally don't care if the template is kept for historical purposes, but that argument is flawed.--v/r - TP 14:06, 12 February 2012 (UTC)
- Right, who cares if our articles look like crap, as long as the bureaucratic niceties are preserved? Beyond My Ken (talk) 12:50, 12 February 2012 (UTC)
- Jclemens' question is the relevant one here. I've never seen a deleted template get re-created for the sole purpose of ensuring that old revisions look nice. It may be that it happens from time to time and I've never come across it, or it may be that it happens rarely or never. If it does happen from time to time, I highly doubt it would happen on something that doesn't affect the content of an article, like a maintenance template. I can't imagine it would ruin someone's day to see Template:Rescue on an old revision instead of the life-preserver template. If this type of template re-creation is truly as uncommon as I think it is, then I see no reason to apply special treatment to this particular template. —SW— 08:58, 12 February 2012 (UTC)
- In this case since the template added nothing of significance to the article, why not just have it produce "white space" then fully protect the template. Mtking 06:26, 12 February 2012 (UTC)
- Delete. ((TFD==Delete) && (DRV==Endorse) == Redlink). Page histories are full of redlinks and other brokeness; relax and breath normally; this is ok. This is a camel's nose to get this all overturned. Alarbus (talk) 16:22, 12 February 2012 (UTC)
- I knew the ARS radicals were getting desperate, but his is just stupid. We don't need to discuss this, because we already did, twice as a matter of fact. The community has already spoken, and it said to delete thos template, and then it said it again. Whoever recreated it needs to be blocked for deliberate disruption per WP:POINT and the template, in accordance with the already clearly expressed will of the community, needs to be deleted. Beeblebrox (talk) 18:07, 12 February 2012 (UTC)
- It wasn't recreated; it was restored, along with the talk page. Kanguole 02:56, 13 February 2012 (UTC)
- Actually, not quite: it was first recreated (as an empty, and non-functional, {{Deleted template}} stub) by the previous deleting admin Ironholds ; then the old content was recreated on top of that by Rich Farmbrough and the prior history restored. The first step may not have been speedy-worthy but didn't technically do what was intended; the second step should never have been done without authorization from a DRV, and in my view does fall under speedy-repost. Fut.Perf. ☼ 07:12, 13 February 2012 (UTC)
- It wasn't recreated; it was restored, along with the talk page. Kanguole 02:56, 13 February 2012 (UTC)
- Question: Correct me if I'm wrong, but wasn't the instructions for the template that after the article survived the AfD the template was to be removed? I ask because if the only argument for restoring the deleted template is that it preferves the look and feel of the article historically at that point it shouldn't be restored in it's full glory. A simple 1 liner of "This article was tagged with the Rescue template" that links to the ARS (or it's successor) page explaining about what the rescue template was. It satisfies the need to indicate that the article was tagged and also minimizes the amount of influence said tag has. Hasteur (talk) 01:31, 13 February 2012 (UTC)
- One (of the meany issues) that were discussed at the TfD was the wikiproject "advert" in main space, so any link to the ARS would not be acceptable, I also don't see it as acceptable to keep a template for only history reasons (see my comments below). Mtking 03:19, 13 February 2012 (UTC)
- So you're all for confusing future editors in wondering what this template was intended to do just so you can stick it to ARS? Take your pound of flesh and move on. The template is consensus deleted, we're just quibbling over the final disposition of a few edge cases. Unless your permanently volunteering to provide a NPOV explanation of what the template was about every single time an editor asks about what the template was supposed to do. Hasteur (talk) 12:52, 13 February 2012 (UTC)
- One (of the meany issues) that were discussed at the TfD was the wikiproject "advert" in main space, so any link to the ARS would not be acceptable, I also don't see it as acceptable to keep a template for only history reasons (see my comments below). Mtking 03:19, 13 February 2012 (UTC)
- It is not true that this treatment is totally unprecedented. See Template:Expand and Template:Deleted template. Not common practice but not totally invented out of whole cloth by the "desperate" ARS. 169.231.55.218 (talk) 03:00, 13 February 2012 (UTC)
- not to mention the fact that it was recreated (albeit just with the "this template was deleted" text) by the admin who deleted it in the first place! 169.231.55.218 (talk) 03:06, 13 February 2012 (UTC)
- Can you point me to the community discussion about using this
{{Deleted template}}
? as it seams to be the work of just one editor ? I can perhaps see the logic for having while current versions of articles use a deleted template, however when all examples have been removed then the template should just be removed.Mtking 03:19, 13 February 2012 (UTC)- We generally use {{being deleted}} while removing templates. {{deleted template}} was the work of quite a number of people and has never been controversial in and of itself. There was a community discussion about {{deleted template}} and there was also a notification left at WT:TFD after it was created. There was also further discussion on AN and probably elsewhere. --Tothwolf (talk) 18:08, 13 February 2012 (UTC)
- As the deleting admin, I have no problem keeping it as a deprecated template. Ironholds (talk) 06:46, 13 February 2012 (UTC)
- (edit conflict) I don't understand why User:Ironholds wasn't notified of this discussion; I thought it was required/polite. I've now done so. Dori ☾Talk ⁘ Contribs☽ 06:47, 13 February 2012 (UTC)
Seriously? There was no consensus in either discussion for it to stay as a deprecated template. And the ARS wonders why they have such a bad reputation for creating such needless drama. Are we seriously going to have to go through another tfd. This should definitely be speedied. -DJSasso (talk) 13:53, 13 February 2012 (UTC)
- The "Us vs Them" comments by a small number of editors above are part of the reason we've ended up here in the first place.
To clarify a few things which others commented or touched upon:
I asked Ironholds to restore {{rescue}}'s talk page and edit history and add {{deleted template}}. He indicated he was swamped with other community issues and with his blessing I asked Rich Farmbrough to handle it. I knew Rich Farmbrough would know how to apply {{deleted template}} since he had done some of the initial work on the template (I've made quite a few complex logic code changes to improve it since then).
Talk pages of templates are routinely deleted under CSD G8 and the talk page of a template which has a long history and lots of discussion should be left intact for historical purposes. Using {{deleted template}} makes this fairly straight forward and easy.
Using {{deleted template}} also further discourages someone from creating a new template with the same name. This has happened a number of times and that really tends to break old page revisions.
The logic code used for {{deleted template}} works like this:
Old page revisions prior to the template's deletion show the original message box of the {{rescue}} template.
New transclusions and edits display the red notice and do not display {{rescue}}'s original message box, and are categorized in the Category:Pages containing deleted templates maintenance category.
The template page for {{rescue}} itself shows both the red notice and the original message box.{{rescue}} does not fall under CSD G4 and I would caution the handful of individuals who are threatening to TfD {{rescue}} yet again that doing this is not productive and will further waste the community's time. It does not harm Misplaced Pages in any way to preserve the talk page and edit history of the template, and while doing so had not historically been routinely done, we didn't have a working solution for doing this until the latest {{expand}} discussion in January 2011.
With the above out of the way, the handful of individuals ranting about Ironholds, Rich Farmbrough, and ARS need to double check who they are ranting about. If they really want to rant about someone, they can rant about me, since I'm the one who asked Ironholds and Rich Farmbrough to handle this task. ARS didn't have anything to do with it, and while I've occasionally "rescued" some "hopeless" articles at AfD, I'm not a "member" of ARS and I have rarely participated in discussions at WT:ARS. That said, I'm likely to ignore any ranting directed my way because it doesn't serve any constructive purpose and doesn't help improve Misplaced Pages. --Tothwolf (talk) 16:43, 13 February 2012 (UTC)
- Tothwolf asserts that G4 doesn't apply to that template. I think that's a grey area, and it might be worthy of a WT:CSD discussion. But essentially for G4 to apply to a page, the page would have to be:
- A sufficiently identical and unimproved copy of the page that was deleted.
- Given a deletion result per consensus during its most recent deletion discussion.
- A page where the reason for the deletion must still apply.
- Not "userfied".
- Not undeleted via DRV.
- That third criterion above might be the sticky point. If a template is no longer in active use, does the reason for its deletion still apply? With the text stating that it's a deprecated template, it won't be effective as canvassing or a rallying cry or an advertisement for ARS or whatever objection someone would have to it even if someone does try to use it. Does that deprecation effectively remove that criterion from any template? In that case, why don't we just add such text to every template at TfD that should no longer be used rather than deleting them? -- Atama頭 23:35, 13 February 2012 (UTC)
- Well, and as I mentioned above, should someone attempt to transclude {{rescue}} via a new edit, it will only display the red text and if the page is saved anyway, it will be added to the maintenance category where we can monitor and remove the transclusion. This is far better than having confused editors who didn't know of the TFD getting a red link when they attempt to use the template, etc.
I know some editors thought such an approach might work for all templates, but I'm not sure we would really need that. The current design of {{deleted template}} works well for message box templates, but might not work well for other templates in it's current form. For message box templates which have previously been heavily used, {{deleted template}} seems right now to be the best way to handle them. --Tothwolf (talk) 01:50, 14 February 2012 (UTC)
- Atama, if a template is no longer in active use, it would be deleted at TFD anyway. And Tothwolf, clearly if the template is deprecated it would be better for it to show up as a red link that doesn't work than to allow it to exist in any fashion any more. If it is necessary to keep the template so it can be prevented from use, then simply include the coding that allows it to be tracked but remove the former functionality and formatting.—Ryulong (竜龙) 09:27, 14 February 2012 (UTC)
- Or you could simply salt the template so it doesn't get recreated. -DJSasso (talk) 16:54, 14 February 2012 (UTC)
- Atama, if a template is no longer in active use, it would be deleted at TFD anyway. And Tothwolf, clearly if the template is deprecated it would be better for it to show up as a red link that doesn't work than to allow it to exist in any fashion any more. If it is necessary to keep the template so it can be prevented from use, then simply include the coding that allows it to be tracked but remove the former functionality and formatting.—Ryulong (竜龙) 09:27, 14 February 2012 (UTC)
- Well, and as I mentioned above, should someone attempt to transclude {{rescue}} via a new edit, it will only display the red text and if the page is saved anyway, it will be added to the maintenance category where we can monitor and remove the transclusion. This is far better than having confused editors who didn't know of the TFD getting a red link when they attempt to use the template, etc.
- Tothwolf asserts that G4 doesn't apply to that template. I think that's a grey area, and it might be worthy of a WT:CSD discussion. But essentially for G4 to apply to a page, the page would have to be:
- Ryulong, please go back and re-read what I wrote above. New transclusions of the template do not display any "former functionality of formatting". Only old page revisions accessed via edit history links with a revisionid prior to the template's deletion will display the original template's message box. Any new transclusions display a red notice and are added to a maintenance category.
While I think a small number of people have been blowing a lot of things out of proportion, the very idea some have put forth that "ARS is going to continue to use {{rescue}} now that its history and talk page have been restored" is simply absurd. The code in {{deleted template}} simply doesn't work that way or allow it.
<soapbox>
I can understand how some editors might not understand how {{deleted template}} works, which is why I explained its logic code above, but beyond that, I'm growing tired of the anti-ARS propaganda (both blatant and disguised) that I've been seeing both here and elsewhere. Such propaganda and fear mongering fly in the face of our policies and if it were being done towards any other "group" of editors here on Misplaced Pages, such as say new page patrollers or FA writers or whatever, it would have been stopped and/or brought before ArbCom long before it got to the point where it is at with the current anti-ARS crowd. In fact, if ARS itself simply didn't exist, those pushing the anti-ARS propaganda would certainly be doing the same thing to some other group.On an individual level, members of ARS appear to be very tolerant and I've noticed that despite the persistent attacks by the anti-ARS camp, while a few ARS members tend to fall into a pattern of being baited and then finally lashing out, the majority of ARS' members simply ignore the anti-ARS rhetoric. I can't say the same for the opposing camp however. At times I've been astonished at the level of intolerance I've seen from the anti-ARS camp.
Individual members of ARS apparently genuinely feel that keeping whatever material they are discussing is in the best interests of Misplaced Pages and helps improve our coverage of a particular subject. While that may or may not be the case depending on the particular discussion, everyone is entitled to their own opinions and beliefs and should still be able to feel secure that they won't be persecuted here on Misplaced Pages for voicing them.
So... why am I speaking out if I'm not even a "member" of ARS? As a community, this is our problem, and somebody needs to say it.
To the anti-ARS crowd: The majority of the community has been able to co-exist with ARS just fine. The problem is you, not them. Suck it up, work things out, and go write an article or find something else constructive to do. --Tothwolf (talk) 17:12, 14 February 2012 (UTC)
- You tell others to assume good faith while assuming stunningly bad faith of them. You tell your perceived opponents to stop being intolerant, while comparing them to nazis. What is wrong with you? Reyk YO! 20:50, 14 February 2012 (UTC)
- My perceived opponents? I think you need to re-read some of what I wrote above because I've made it quite clear that I'm not in either of these camps. I've been sitting back and watching people go at it for weeks and I'm now simply calling it as I see it. If you feel offended by my reference to First they came… above then I apologize. My intent however was to point out the apparent "persecution" of ARS by a small anti-ARS minority within the Misplaced Pages community who've chosen to turn the TFD of {{rescue}} into a cause célèbre and use it as a staging ground to further propagandize and attack their perceived enemies within ARS. Given that, I feel my reference was spot on. --Tothwolf (talk) 22:45, 14 February 2012 (UTC)
- You tell others to assume good faith while assuming stunningly bad faith of them. You tell your perceived opponents to stop being intolerant, while comparing them to nazis. What is wrong with you? Reyk YO! 20:50, 14 February 2012 (UTC)
- Ryulong, please go back and re-read what I wrote above. New transclusions of the template do not display any "former functionality of formatting". Only old page revisions accessed via edit history links with a revisionid prior to the template's deletion will display the original template's message box. Any new transclusions display a red notice and are added to a maintenance category.
- This is a blindingly obvious G4. The deleted revisions thing is BS many templates that no longer exist appear in deleted revisions. This is slighting the community concencus by bringing back a contraversial template without discussion. --Guerillero | My Talk 06:24, 15 February 2012 (UTC)
- Are you in the right place? Please see the top of the page: "Review of a deletion or undeletion of a page → deletion review.". The template was at TfD multiple times and so it seems right and proper that it should have several performances at DRV too. See also WP:LIGHTBULB. Warden (talk) 10:13, 15 February 2012 (UTC)
- On a related note, if an administrator could restore the documentation subpage and add {{Historical}}, this should allow the red notice to properly display directly below the original message box on the template page itself (see {{Expand}} for an example). Right now the preloaded documentation message box is being displayed in between the original message box and the red notice and it might be possible for some people to miss seeing the red text on the template page itself. This doesn't have any effect on the logic code used by {{deleted template}} so any potential transclusions will display the red notice text correctly anyway. --Tothwolf (talk) 16:35, 15 February 2012 (UTC)
- Done I think. MBisanz 16:48, 15 February 2012 (UTC)
- The
|name=
parameter for {{Ambox}} was what was causing the restored documentation page box to display in the wrong location. I'm not sure why just yet, but I've removed that parameter so it displays the red notice text correctly now. --Tothwolf (talk) 17:34, 15 February 2012 (UTC)
- Ah, here as go. {{Ambox}} includes the code which would cause this to happen:
- The
{{#ifeq:{{FULLPAGENAME}}|Template:{{PAGENAME:{{{name}}}}} |{{#ifeq:{{{doc}}}|no| |{{Documentation}}<!-- Transclude documentation on template page --> }} }}
- It also looks like the
|subst=
parameter cannot be used without|name=
, so either|doc=no
has to be passed to {{Ambox}}, or the subst: check has to be done externally to {{Ambox}} when {{deleted template}} is used. --Tothwolf (talk) 18:04, 15 February 2012 (UTC)
- It also looks like the
- This is absurd. Consensus at the TfD and DRV was clear, and that was that the template should be deleted. Not quasi-pseudo-half way deleted but retained as some kind of memorial. Deleted. Are we going to start restoring articles because other articles have redlinks in their histories now? How ridiculous can you get? And congratulations to Tothwolf, who with his extensive explanations of the coding feasibility and "BAWWW! I'm, like, totally neutral but the ARS are blameless angels fighting the evil hordes" handwringing, has managed to deflect from the real issue- which is that the template should not have been undeleted at all. The consensus is what it is, and people simply need to accept that. G4 and salt. Reyk YO! 21:51, 15 February 2012 (UTC)
- From my viewpoint, neither "side" is particularly happy with the current situation. ARS doesn't have their template anymore, and the hardcore anti-ARS camp isn't happy that the template has been wrapped in {{deleted template}} in order to prevent new transclusions and allow old page revisions to continue to work.
As a member of the larger community, I for one am glad that the talk page which had been speedied under CSD G8 is visible to non-administrators now. Deletion of the talk page resulted in a loss of transparency as to the discussions which had been taking place there prior to the TFD and incoming links to the talk page had been made non-functional. --Tothwolf (talk) 00:24, 16 February 2012 (UTC)
- From my viewpoint, neither "side" is particularly happy with the current situation. ARS doesn't have their template anymore, and the hardcore anti-ARS camp isn't happy that the template has been wrapped in {{deleted template}} in order to prevent new transclusions and allow old page revisions to continue to work.
- Things I see above: "Sorry, but no, the ARS should not be allowed to retain it in this fashion like some sort of martyr's rock." "And shit like this is why ARS has the reputation it does. Creating nothing but pointless drama." "knew the ARS radicals were getting desperate, but his is just stupid." "And the ARS wonders why they have such a bad reputation for creating such needless drama." Ummm, Really?. You guys are creating your own drama. Who cares about this, really? You are arguing about the proper treatment of a deleted template for historical purposes. As some are doing above, figure out the standard rule, discuss it, come to a result. Meanwhile I'll work on building an encyclopedia.--Milowent • 14:39, 16 February 2012 (UTC)
TfD once again
Nomination for deletion of Template:Rescue
Template:Rescue has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page.
It is a shame that some just refuse to accept the community consensus and edit was to keep a sentimental/historical copy of what was deleted in project space, but it seems an official TfD is the only thing that will work here, as one wikiproject saw fit to edit war to keep speedy tags off and keep the old template itself in. Tarc (talk) 14:03, 16 February 2012 (UTC)
- Yes, the ARS is sitting around a fire perusing the template history and listening to .--Milowent • 14:50, 16 February 2012 (UTC)
Talk page archives
Could an administrator please restore the talk page archives and sandbox edit history?
I've been able to find 4 talk page archives and another talk page so far, but there may be others as well. --Tothwolf (talk) 19:03, 16 February 2012 (UTC)
- Could an administrator like, not do that, and not take any more admin actions related to this until the current TFD is closed? Thanks. Beeblebrox (talk) 19:25, 16 February 2012 (UTC)
- With your comment at TFD and now here, I certainly don't understand what exactly it is you don't want us to see in the talk page archives. --Tothwolf (talk) 19:33, 16 February 2012 (UTC)
- I don't know or care what is in them so I'll thank you to leave your backhanded accusations at the door. They were deleted as a result of a community decision to delete the template. A decision that was upheld at DRV. None of this should have been restored without a new discussion first that clearly overturned the previous consensus. That's how WP works, as I'm sure you are already aware. Beeblebrox (talk) 20:48, 16 February 2012 (UTC)
- If you don't particularly care what is in the talk page archives, then you shouldn't really be all that concerned if they are restored for transparency reasons, either. The talk page was not deleted per any sort of community discussion so it might be best if you stop attempting to mislead others who may be following this discussion. If the deletion of the template itself was as non-controversial as you and a few others have tried to claim, then there also wouldn't be any reason for a small minority of individuals to try to prevent non-administrators from seeing the talk page archives now would there? --Tothwolf (talk) 21:59, 16 February 2012 (UTC)
- I don't know or care what is in them so I'll thank you to leave your backhanded accusations at the door. They were deleted as a result of a community decision to delete the template. A decision that was upheld at DRV. None of this should have been restored without a new discussion first that clearly overturned the previous consensus. That's how WP works, as I'm sure you are already aware. Beeblebrox (talk) 20:48, 16 February 2012 (UTC)
- With your comment at TFD and now here, I certainly don't understand what exactly it is you don't want us to see in the talk page archives. --Tothwolf (talk) 19:33, 16 February 2012 (UTC)
- Because speedy deletion is supposed to only be used for non-controversial deletions, and because the G8 criteria for speedy deletions specifically excludes talk page archives:
"This excludes any page that is useful to Misplaced Pages, and in particular deletion discussions that are not logged elsewhere, user pages, user talk pages, talk page archives, "
I again ask that an administrator please restore these pages for the purposes of transparency. --Tothwolf (talk) 22:17, 16 February 2012 (UTC) - And I again ask that they not for issues of ignoring a clearly established consensus that we are now being asked to ignore for completely specious reasons. Beeblebrox (talk) 01:32, 17 February 2012 (UTC)
- This is on the verge of being seen as disruptive, IMO. The Template is gone; it only exists at the moment because of the extremely poor judgement of Rich Farmbrough, and will likely be deleted for good as no one has put forth an actual argument as to why a prior finding of delete should not be honored. There is no need to retain discussions abotu a template that does not exist. Tarc (talk) 04:23, 17 February 2012 (UTC)
- Actually, I think the talk page archives will likely provide a useful insight into how the template evolved, how it was perceived, and the problems that led to its removal. I do not see the value in leaving those discussions deleted, lest we reinvent the same issues and errors again. Jclemens (talk) 07:57, 17 February 2012 (UTC)
- I wouldn't be terribly opposed to moving the contents of the talkpage and related subpages to some subsection of the ARS project page if you really wish to preserve the conversations. Tarc (talk) 17:23, 17 February 2012 (UTC)
- I think Tarc's suggestion makes a lot of sense, frankly. 28bytes (talk) 18:48, 17 February 2012 (UTC)
- I wouldn't be terribly opposed to moving the contents of the talkpage and related subpages to some subsection of the ARS project page if you really wish to preserve the conversations. Tarc (talk) 17:23, 17 February 2012 (UTC)
- Actually, I think the talk page archives will likely provide a useful insight into how the template evolved, how it was perceived, and the problems that led to its removal. I do not see the value in leaving those discussions deleted, lest we reinvent the same issues and errors again. Jclemens (talk) 07:57, 17 February 2012 (UTC)
- The fact that this is even at TfD again is frankly deplorable. It should have been speedily deleted (which is why I again CSDed it; Milowent reverted me). What little esteem I had for the ARS is now completely gone; they refuse to respect two consensuses Purplebackpack89≈≈≈≈ 16:45, 17 February 2012 (UTC)
- It's back at AFD. If there is a consensus in that discussion, then whatever that consensus is can we please please please please please please please please please just implement it and put an end to these layers of meta-discussion? --BrownHairedGirl (talk) • (contribs) 02:17, 18 February 2012 (UTC)
Anybody else interested in helping out at the copyright problems board?
I would dearly love some increased admin involvement over there. I was, I have to admit, struggling with burnout on that work months ago (having focused on it for years), and while I'm still putting time into it every weekend I cannot keep up. More assistance there would be very much appreciated. I'm happy to offer guidance based on my own work there to anybody who's interested in helping out. We also have WP:CPAA with guidance for admins interested in helping. This area is sorely in need of some additional hands. :/ --Moonriddengirl 01:34, 13 February 2012 (UTC)
- I'll try to lend a hand at it. I'm always worried that I might miss a copyvio, so I don't tend to do this. Reaper Eternal (talk) 13:27, 14 February 2012 (UTC)
- Marvelous! If you ever want a second opinion, please feel free to drop by my talk page or just place a note at CP with your own impressions and wait for me or another admin to come by. Second opinions are sometimes helpful at CP. --Moonriddengirl 12:04, 15 February 2012 (UTC)
- Start by asking all the people in the thread below who accused Rlevse/PumpkinSky of "massive plagiarism." If they haven't helped you out, I think it is time they did! (I mean this in good faith, there are a lot of them down there, obviously concerned about the issue. What a great pool to draw from!) It is tough work -- I worked on the CCI on that user just mentioned and I also worked on reviewing the zillions of articles on the ItsLassieTime sock-- which kind of burned me out. I agree more people are needed and that yes, miss one and everyone jumps on you, that is a worry. It's also why I've stopped submitting or reviewing GA and FA articles unless I have a team of at least four people to help me, too scary to do these things alone any more. Montanabw 01:59, 16 February 2012 (UTC)
- I considered lending a hand there some time ago, after having filed one or two reports myself. Frankly, the templates and procedures used over there look extremely intricate to an outsider, downright foreboding. The instruction themselves also discourage participation, besides not being particularly well written, e.g.: "If the article is tagged for {{copyvio}}, you should allow an administrator or copyright problems clerk to remove the tag. If the article is tagged for {{copy-paste}} or {{close paraphrasing}}, you may remove the tag from the article when the problem is addressed (or disproven), but please do not close the listing on the copyright problems board itself." ASCIIn2Bme (talk) 09:07, 17 February 2012 (UTC)
- I recently had a problem summarized here which I did not manage to resolve and after which I decided I am not going to help there anymore.--Ymblanter (talk) 09:10, 17 February 2012 (UTC)
Is this a G6 or not?
Plastomer (disambiguation). I've had a G6 denied a couple times. This is a dab with one blue link and two reds. It disambiguates nothing. Anyone want to tell me how in the flying hell this is NOT a G6? I see no reason to let this rot in AFD. Ten Pound Hammer • 20:25, 14 February 2012 (UTC)
- Personally, I believe that page could reasonably have been deleted per WP:G6; edit summaries such as this one, however, are completely unwarranted and over the top. That said, the AfD will be snow closed quite soon I'd wager. Salvio 20:31, 14 February 2012 (UTC)
- FWIW, the edit summary was "(Undid revision 476889682 by Nyttend (talk) don't be an idiot)", and the diff (for admins only) is now here. Graham87 02:00, 15 February 2012 (UTC)
- Hello, why was the page speedy deleted as uncontroversial when I had already declined it? "Uncontoversial" means that nobody disagrees, and I daresay an when an attempt is declined multiple times, it's controversial. Moreover, why did I only learn about this discussion by browsing this page? Why was I not notified? Nyttend (talk) 02:48, 15 February 2012 (UTC)
- FWIW, the edit summary was "(Undid revision 476889682 by Nyttend (talk) don't be an idiot)", and the diff (for admins only) is now here. Graham87 02:00, 15 February 2012 (UTC)
- This three time renomination for speedy deletion was inappropriate behaviour by TenPoundHammer, but this has already been discussed by those involved. The close of the AFD is also not the best as it should have waited for a full delete decision as a declined speedy delete should not be speedy deleted. However snow deletion could have been fine if it waited a while. Because it has only been deleted with a G6 if it is recreated there is no recourse to delete it again immediately, which if the AFD had been fully debated would have allowed a G4 delete on recreation. Graeme Bartlett (talk) 09:11, 15 February 2012 (UTC)
- I am at a loss to understand why Nyttend thought the G6 criterion didn't apply. {{db-disambig}} clearly says: disambiguates two or fewer extant Misplaced Pages pages and whose title ends in "(disambiguation)". This was obviously the case here. Nyttend simply misread the rule. No point in making a fuss about it now. I also don't see how the technical distinction between a G4-able AfD decision and a speedy makes any practical difference here. If anybody should ever recreate the page, then either there will still be no more than a single target, in which case the dab will automatically again fall under G6, or such targets will have been created, in which case the dab will undoubtedly have become legit. Fut.Perf. ☼ 11:24, 15 February 2012 (UTC)
- I would have deleted that as a G6 myself, but someone's decline should still be respected. Graeme Bartlett (talk) 11:41, 15 February 2012 (UTC)
- If the original decline is based on such an obvious factual error about the rule? I don't see why. Fut.Perf. ☼ 11:59, 15 February 2012 (UTC)
- Avoidance of drama, perhaps? Rich Farmbrough, 13:59, 16 February 2012 (UTC).
- Avoidance of drama, perhaps? Rich Farmbrough, 13:59, 16 February 2012 (UTC).
- If the original decline is based on such an obvious factual error about the rule? I don't see why. Fut.Perf. ☼ 11:59, 15 February 2012 (UTC)
- I would have deleted that as a G6 myself, but someone's decline should still be respected. Graeme Bartlett (talk) 11:41, 15 February 2012 (UTC)
- I am at a loss to understand why Nyttend thought the G6 criterion didn't apply. {{db-disambig}} clearly says: disambiguates two or fewer extant Misplaced Pages pages and whose title ends in "(disambiguation)". This was obviously the case here. Nyttend simply misread the rule. No point in making a fuss about it now. I also don't see how the technical distinction between a G4-able AfD decision and a speedy makes any practical difference here. If anybody should ever recreate the page, then either there will still be no more than a single target, in which case the dab will automatically again fall under G6, or such targets will have been created, in which case the dab will undoubtedly have become legit. Fut.Perf. ☼ 11:24, 15 February 2012 (UTC)
- That page was an obvious G6 candidate. I'd like Nyttend to explain why he thought G6 did not apply, as it seems he did not explain himself other than by asserting that "neither of those cases is true". Jafeluv (talk) 12:35, 16 February 2012 (UTC)
PumpkinSky return request
Request withdrawn. 28bytes (talk) 00:34, 16 February 2012 (UTC) |
---|
User:PumpkinSky (formerly User:Rlevse) has posted on his talk page a request to return to editing. A recent community ban proposal was closed with consensus against the ban, but he remains blocked. The ban proposal focused on several legitimate concerns with his editing, mainly copyright/close paraphrasing issues, and presenting himself as a new user instead of a returning/unvanished one. He is offering an apology for the misleading presentation of himself as a new user, and has proposed some safeguards to help prevent any copyright issues from entering the mainspace. A number of editors, including myself, have volunteered to act as mentors to help make sure the copyright concerns don't recur. This editor has made some mistakes, but he has a lot to offer the project, and I hope my fellow editors will consider supporting his return to editing. Thanks, 28bytes (talk) 21:51, 14 February 2012 (UTC)
Discussion of return requestNOTE: I have unblocked user:PumpkinSky for the sole purpose of responding to questions to this request. I have advised him that any deviations may result in immediate reblocking and may jeaopardize his request.---Balloonman 23:49, 14 February 2012 (UTC)
There is new evidence of massive sock-puppetry using web hosts, colocation centers, and open proxies to edit articles on scouting and engage in attacks against other editors at a FAR, all while he was using the PumpkinSky account in parallel. Evidence will be introduced here within a day or so. If you're impatient, check out User_talk: Geometry guy. ASCIIn2Bme (talk) 12:34, 15 February 2012 (UTC)
Restrictions if unblockedI, personally, am opposed to unblocking PS before he has served out a 6-month standard offer period, however I recognize that many editors whom I respect feel otherwise, so I like to open this additional discussion about possible restrictions to his editing should the community see fit to unblock him. Specifically:
I have reservations not so much about Rlevse's intent to return to editing, but about the way this has been proposed. If my concerns are addressed, I may consider adding myself to the support column, but I have serious reservations that Rlevse might not yet understand the gravity of all that he's done recently, evidenced by the way this return to editing was put forward.
So, considering everything, why are we not putting stronger restrictions on his possible return to editing? With satisfactory answers to my concerns, mentors who are not all his friends and supporters and would be willing to rein him in, no participation in DYK, FAC and FAR for some trial period, and with an adequate trial period that includes mentors who would be willing to re-block should he revert to bad habits, I would be willing to support. But what I see in his plan so far is that he found five friends who aren't likely to rein him in, and there are still questions about the accounts he operated and his potential participation at DYK and FAC. SandyGeorgia (Talk) 02:34, 15 February 2012 (UTC)
I do not agree with unblocking based upon this discussion and on those conditions. Note that Misplaced Pages:Requests for comment/Rlevse is a red link, propose return to status quo of blocked until more clear plan with wider support and more time for discussion appears. There's no rush on this, let's take the time to think it through. - Aaron Brenneman (talk) 05:11, 15 February 2012 (UTC)
Maybe this is better structured at an RfC/U (with support AND oppose sections)PS: The only option as far as mentors/Reviewers would be editors firm on copyright. I'd be keen to hear from Moonriddengirl, Laser Brain, Wizardman and Ucucha to name a few as to whether this is feasible, not the mentors suggested already. Casliber (talk · contribs) 12:31, 15 February 2012 (UTC)
Two: Balloonman, you unblocked him so he could respond here. He's generally not responding here.
Demeanor (with the latest account)Just a quick note that looking at PumpkinSky's first few edits this conversation struck me. And you should also read the "followup", six weeks later. I see the same harboring of grudges and petty vindictiveness in action there that we saw when PumpkinSky went after the FAC/R regulars with whom he had past disputes. I dare say: that was conduct unbecoming of an Arbitrator, even a former one. And it qualifies as WP:HARASSMENT in my view, especially the 2nd thread where he barged in on an unrelated conversation to resume his six weeks old grudge. Yeah, new page and recent changes patrollers can and do make mistakes. I've been on the receiving end of some of those myself. But I don't see anything that Nasnema did which that might qualify for a six-weeks-later repeat abuse of that kind. ASCIIn2Bme (talk) 22:00, 15 February 2012 (UTC) |
Unblock request withdrawn
PumpkinSky has e-mailed me and asked me to withdraw the unblock request, as he recognizes there is no consensus for letting him return to editing at this time. He is disappointed, obviously, but says he will respect the community's wishes. I have re-imposed the indefinite block, until such time as there is consensus for his return. Thank you to everyone who commented here for considering his request. 28bytes (talk) 00:32, 16 February 2012 (UTC)
- I'm very sorry about this. Many editors supported Pumpkin Sky's return, and I don't think the supporters where in the minority. There was as well a lot of assumptive evidence being presented as if it was fact which can be typical on Misplaced Pages but is still disturbing no matter how many times I see it. I'd have liked to see this go to arbitration. (olive (talk) 01:07, 16 February 2012 (UTC))
The underlying issues here still need to be worked out. For example, prodded by a discussion at the RefDesk I slightly expanded Anorexia (symptom) with this edit (), based on Now this doesn't seem that far from what has been called "plagiarism" by PumpkinSky at . Now I don't feel this is plagiarism; I have to stay that close to avoid "original research" and maintain the logical sequence of material. But admittedly I wouldn't write a paper this way - I'd read all the sources I could at once and be able to mix and match a lot more. The combination of WP:OR and adding one edit at a time drives us closer to the boundary. So we need to have some agreement on where it is rather than abruptly branding people as plagiarizers without any real consensus on the rules. Wnt (talk) 17:41, 17 February 2012 (UTC)
Betacommand 3 closed
An arbitration case regarding Betacommand (Δ) has now closed and the final decision is viewable at the link above. The following remedies have been enacted:
- The existing community sanctions on Betacommand were a valid response by the community to prior problems with Betacommand's editing, and that Betacommand was required to abide by those sanctions if he wished to continue editing. However, given that interpretation and implementation of those sanctions has led to ongoing disputes, the community sanctions are superseded by the more straightforward remedies provided for in this decision.
- Betacommand is banned from Misplaced Pages for a period of no less than one year.
- After one year has elapsed from the date of his ban, Betacommand may request that the ban be lifted. As part of any such request, Betacommand shall be required to submit a plan outlining his intended editing activity and demonstrating his understanding of and intention to refrain from the actions which resulted in his ban. The Committee shall present this plan to the community for review and comment prior to any modification of Betacommand's ban.
For the Arbitration Committee, --Guerillero | My Talk 01:58, 15 February 2012 (UTC)
- Most appreciated. The return of the arbcom resolution summary is very welcome. NativeForeigner 07:54, 15 February 2012 (UTC)
- Return? It's precisely the same format it has been for a long time. --Alexandr Dmitri (talk) 11:40, 15 February 2012 (UTC)
- Yes, but it's usually not posted at AN in this level of detail - usually just a link to the discussion or announcement, unless I've missed one or two. UltraExactZZ ~ Did 13:36, 15 February 2012 (UTC)
- Return? It's precisely the same format it has been for a long time. --Alexandr Dmitri (talk) 11:40, 15 February 2012 (UTC)
- Speaking of discussion - the discussion of this case may be found Here. UltraExactZZ ~ Did 13:56, 15 February 2012 (UTC)
Please delete copyvio picture
Please delete copyvio picture File:Aryanshiva.jpg, it's from facebook, thanks--Musamies (talk) 13:24, 15 February 2012 (UTC)
Done Thanks for the notification. EyeSerene 13:30, 15 February 2012 (UTC)
RS/N recommends preventative action against encyclopaedia disruption
As a result of the following discussion, where systemic and disruptive deceit in relation to references was uncovered, WP:RS/N recommends preventative action regarding User:Legolas2186's editing and would like administrator action on the matter. Fifelfoo (talk) 21:31, 15 February 2012 (UTC)
After becoming suspicious of a source used by User:Legolas2186 in a recent GAN entry, I looked further and found some more suspicious references used by Legolas2186 to support other recent GA expansions that he has been undertaking. I have asked Legolas to respond but I have not been satisfied that the sources are not faked. Here are the cites I have a problem with:
- Was used in Madonna: Like an Icon until I removed it:
- Used in Keep It Together (Madonna song) and Oh Father:
- Zollo, Paul (May 1989). "Madonna on her turbulence". SongTalk. 10 (5). Mortimer Zuckerman: 21.
- Used in Saqib Saleem:
- Deb, Anupama (2011-11-09). "Saqib Saleem: From Cricketer to Actor". Starweek Magazine. Bennett & Coleman Ltd: 19–22.
All of the above-listed cites were added by Legolas2186 as part of a drive to bring the article to GAN. If anybody here can help him by verifying one or more of the cites, please do so. Otherwise, it would appear that Legolas2186 has been fabricating references in order to create or expand articles and thereby gain credit for GA. Binksternet (talk) 19:14, 15 February 2012 (UTC)
- (ec)A search of People magazine website does not show such an article, nor can I find "Christina Jansen" who is meant to be the author. Darkness Shines (talk) 19:29, 15 February 2012 (UTC)
- Considering that Legolas lives in India and the time now is ± 00:00, Binksternet hasn't waited to Legolas to reply him and immediately started to research in the articles he mentioned challenging offline sources (just because he can't access to them (Talk:Saqib Saleem/GA2)). I suggest Bink to wait until Legolas explanation before he starts to question the reliablility of an user (WP:AGF). Tbhotch. Grammatically incorrect? Correct it! See terms and conditions. 19:26, 15 February 2012 (UTC)
- See also. Tbhotch. Grammatically incorrect? Correct it! See terms and conditions. 19:30, 15 February 2012 (UTC)
- This is not newly discovered today, so it doesn't matter whether it is midnight somewhere. I signaled the serious nature of the unverifiable cite at Talk:Madonna: Like an Icon/GA1 on February 7, eight days ago. Legolas did not respond even though he edited other articles during that time. On February 10, I asked him about a problematic reference at Talk:Saqib_Saleem#Major question about major source and he responded very quickly there on the talk page and also by offering to send me scans of the physical pages, but he has not yet sent me any scans. On February 10, I began looking at other articles he was involved with and found that he had used an unverifiable Becky Johnston article from June 1989 Rolling Stone so I corrected it to the same Becky Johnston in May 1989 writing for Interview under a different title. (This unverifiable source was added by Legolas in August 2011.) This appeared to be sloppy work, not necessarily bad faith, since the writer's name was correct and the quotes were correct. Yesterday and today, I looked for more recent sloppy work in articles that Legolas was involved with and I found the Paul Zollo cites that I cannot verify anywhere online. Legolas has not posted here for three days but I am not willing to wait for him to respond before I ask the community to try and help me find whether the cites listed above can be verified by other means. Binksternet (talk) 20:00, 15 February 2012 (UTC)
- It does matter that is midnight, as he is sleeping right now (see his contributions, he rarely edits at this time), and it matters as I told you that is seems like you can't wait until he answers. As you said he offered you the scans, but you never asked to him send them to you, the only thing that you did was start to check all his recent work to see if his offline sources are "falsified". This sounds more like a revenge of something rather than a concerned editor. Tbhotch. Grammatically incorrect? Correct it! See terms and conditions. 20:10, 15 February 2012 (UTC)
- Actually I asked him for the scans soon after his offer. He continued editing for two more days but he did not respond yes or no about the scans. This thread is not about whether Legolas is sleeping right now, it is about whether he has been putting sloppy citations into articles since August 2011, or possibly putting knowingly wrong citations into articles more recently to attain GA credit. The first step is a plea to others in the community to see if the cites are verifiable. As such, it does not require Legolas to respond. Binksternet (talk) 20:24, 15 February 2012 (UTC)
- I regret to say that I can find no evidence of that People Weekly article in databases that catalog the magazine. That issue doesn't even seem to exist. --Laser brain (talk) 20:17, 15 February 2012 (UTC)
- It is not just the references listed above. - in that edit a vast amount of information was added, including the sentence With SongTalk magazine, Madonna explained that "isolated by fame and shaken by the failure of my marriage, I could only reach out to the stability of my family roots, and 'Keep It Together' is for that only." supposedly sourced by one of the references listed above and page 122 of the book Madonna: Like an Icon by Lucy O'Brien. The book is viewable on 'Look inside' option on Amazon.com, and there is nothing of the kind on page 122. Page 131 does however say There is the sense that Madonna, isolated by fame and shaken by the failure of her marriage, is reaching back to the stability of family roots. but that is written solely by the author, and not a quote from Madonna. I find the suggestion that an editor has fabricated references and a quote from a living person to be very troubling, and would suggest this is moved to another noticeboard. 86.186.68.76 (talk) 20:37, 15 February 2012 (UTC)
- Agreed. A People issue from Jaunary 2008 would one of the following:
- Vol. 69 Issue 3 - 1/28/2008
- Vol. 69 Issue 2 - 1/21/2008
- Vol. 69 Issue 1 - 1/14/2008
- not volume 581 issue 50 dated Jaunary 5th. A database search turned up no articles by that title or author. Major US magazines have different overseas versions, so this editor may be using the Indian version of People, if such a thing exists. But that would have a different ISSN, and the ISSN provided is for the US People. Gamaliel (talk) 20:55, 15 February 2012 (UTC)
- According to that book the edition was published in August 1989, several months after the alleged May 1989 publication date. From what I have been able to learn about SongTalk it was published quarterly with "Spring", "Summer", "Fall" and "Winter" names used not months. There is a full transcript of the interview from the summer 1989 edition, it does not contain the quote attributed to Madonna, so neither of the references added are real even if we accept by "May 1989" what was really meant was "Summer 1989". I have no reason to doubt the accuracy of the transcript as it matches the excerpt in the book I linked to, I certainly believe it more than Legolas2186 at this point. 86.186.68.76 (talk) 20:57, 15 February 2012 (UTC)
- The Songtalk interview is also in Zollo's book "Songwriters on songwriting" (ISBN 0306812657) so it might be worth checking there. It's not currently available at my library so I can't check it. 67.117.145.9 (talk) 07:05, 16 February 2012 (UTC)
Could administrators comment on appropriate actions and enact them? Fifelfoo (talk) 21:31, 15 February 2012 (UTC)
- I note that Fifelfoo closed the discussion at RSN here with the summary RS/N recommends preventative actions over sustained and deceitful encyclopaedia disruption This has been moved to WP:AN to request preventative actions. However the discussion as closed does not contain anything like a consensus for "sustained" or "systemic" "deceit", nor any mention, let alone "requests", of "administrator action on the matter". Considering that discussion of the verifiability of the disputed edits was still in progress at the close, I would suggest that this request is at best premature and at worst disruptive in itself. Cusop Dingle (talk) 21:47, 15 February 2012 (UTC)
- At least two works that simply do not exist—it is deceit, and this kind of violation of good faith, encyclopaedic conduct and standards has previously been treated as block-on-sight. IP 86.186 suggests fairly clearly that such action is necessary ("this is moved to another noticeboard"). Fifelfoo (talk) 21:55, 15 February 2012 (UTC)
- As I said, there is no consensus, discussion is continuing, and one user saying "moved to another noticeboard" is very far from being a consensus asking for "administrator action on the matter". If you believe that disruption justifying block-on-sight exists, bring it to AN/I under your own name, just don't claim support from a non-existent consensus. Cusop Dingle (talk) 22:00, 15 February 2012 (UTC)
- Bullshit. If he's falsifying sources he needs to be blocked, end of. The evidence in this thread (I have not read the RS/N thread as of yet) is enough to block him until this gets sorted out (and nobody is going to object to blocking someone who's quite blatantly making up sources). —Jeremy v^_^v 22:15, 15 February 2012 (UTC)
- If you disagree with another editor, please find a more acceptable way of saying so. Cusop Dingle (talk) 22:22, 15 February 2012 (UTC)
- You are wikilawyering. While the first word in Jeske's response might be regrettable, the sentiment he's expressing is one that I, and probably others, agree with. Fifelfoo was right to bring this here. Sven Manguard Wha? 00:06, 16 February 2012 (UTC)
- If you disagree with another editor, please find a more acceptable way of saying so. Cusop Dingle (talk) 22:22, 15 February 2012 (UTC)
- Bullshit. If he's falsifying sources he needs to be blocked, end of. The evidence in this thread (I have not read the RS/N thread as of yet) is enough to block him until this gets sorted out (and nobody is going to object to blocking someone who's quite blatantly making up sources). —Jeremy v^_^v 22:15, 15 February 2012 (UTC)
- As I said, there is no consensus, discussion is continuing, and one user saying "moved to another noticeboard" is very far from being a consensus asking for "administrator action on the matter". If you believe that disruption justifying block-on-sight exists, bring it to AN/I under your own name, just don't claim support from a non-existent consensus. Cusop Dingle (talk) 22:00, 15 February 2012 (UTC)
- At least two works that simply do not exist—it is deceit, and this kind of violation of good faith, encyclopaedic conduct and standards has previously been treated as block-on-sight. IP 86.186 suggests fairly clearly that such action is necessary ("this is moved to another noticeboard"). Fifelfoo (talk) 21:55, 15 February 2012 (UTC)
- Slow down. Let's not block anyone "until this gets sorted out". Let's sort it out first, and then decide what to do next. I don't know Legolas myself, but I see his name pop up frequently in productive or helpful places, and he's been here a long time and does a lot of writing. I'm not saying it's impossible that there is intentional falsification, but I'd be really surprised if it is; I suspect there's a less sinister explanation. One that may still need to be addressed, perhaps, but intentional falsification of references is a pretty strong thing to be assuming. I think it would have made the most sense to leave this at RS/N until we heard from him, but I guess that ship sailed already. But there should be no blocks, or threats of imminent blocks, until we hear from Legolas. --Floquenbeam (talk) 23:54, 15 February 2012 (UTC)
- If he dosen't come here and address these issues within an hour of resuming editing, I'd say that an indefinate block be issued with the unblock condition that he explain himself on the talk page before being unblocked. I agree we shouldn't move to block him before he responds, but this is serious enough to warrant an immediate response from him. Sven Manguard Wha? 00:04, 16 February 2012 (UTC)
- If he dosen't come here and address these issues within an hour of resuming editing, I'd say that an indefinate block be issued Is this a threat? He has a life, you know, he is at work right now, and doesn't our policy state "block are preventive not puntatives? What will a block prevent, vandalism from his account? Tbhotch. Grammatically incorrect? Correct it! See terms and conditions. 02:46, 16 February 2012 (UTC)
- Yes actually, given that there's demonstration that in two sampled instances he violated WP:V through deceptive citations that appear on the surface to be good but are non-existent. Citing non-existent texts is a heinous attack on WP:V, and there is a reasonable assumption of future bad faith given the deceptive nature of the attack on V. It is conduct in the territory of copyright violation and plagiarism. Fifelfoo (talk) 03:23, 16 February 2012 (UTC)
- I really don't see the issue Tbhotch. I didn't say "he has to drop everything including his real life and address this right now", I essentially said "he can't go back to editing the project until this is addressed". He might not have time to make any edits to Misplaced Pages for several days, and that's fine by me, but it wouldn't be appropriate for him to edit Misplaced Pages, when he does have the time to do so, until after he comes here and addresses this. As to the second piece of your comment, I would see this as a preventative block, the aim being to prevent him from adding any more sources to articles, since there appears to be a problem with his sources not existing. Sven Manguard Wha? 03:33, 16 February 2012 (UTC)
- As for me, I think Legolas2186 should be made aware that this is the first issue he should address upon resuming editing. A block would serve, and it would be easier to administer than a half dozen admins constantly visiting his contributions page to see if he has resumed. However, the latter method would work fairly well, and with so many eyes on the issue, I seriously doubt Legolas will get away with faking another reference in the near future. Moreover, I wish that Legolas will learn from the experience and will resolve to use only true blue citations in the future. He has been a valuable editor but he needs to know that snubbing WP:V cannot continue. Binksternet (talk) 04:11, 16 February 2012 (UTC)
- I strongly agree with the previous point, the outcome I'd like to see is rehabilitation and improvement. Fifelfoo (talk) 04:15, 16 February 2012 (UTC)
- As for me, I think Legolas2186 should be made aware that this is the first issue he should address upon resuming editing. A block would serve, and it would be easier to administer than a half dozen admins constantly visiting his contributions page to see if he has resumed. However, the latter method would work fairly well, and with so many eyes on the issue, I seriously doubt Legolas will get away with faking another reference in the near future. Moreover, I wish that Legolas will learn from the experience and will resolve to use only true blue citations in the future. He has been a valuable editor but he needs to know that snubbing WP:V cannot continue. Binksternet (talk) 04:11, 16 February 2012 (UTC)
- I really don't see the issue Tbhotch. I didn't say "he has to drop everything including his real life and address this right now", I essentially said "he can't go back to editing the project until this is addressed". He might not have time to make any edits to Misplaced Pages for several days, and that's fine by me, but it wouldn't be appropriate for him to edit Misplaced Pages, when he does have the time to do so, until after he comes here and addresses this. As to the second piece of your comment, I would see this as a preventative block, the aim being to prevent him from adding any more sources to articles, since there appears to be a problem with his sources not existing. Sven Manguard Wha? 03:33, 16 February 2012 (UTC)
- Yes actually, given that there's demonstration that in two sampled instances he violated WP:V through deceptive citations that appear on the surface to be good but are non-existent. Citing non-existent texts is a heinous attack on WP:V, and there is a reasonable assumption of future bad faith given the deceptive nature of the attack on V. It is conduct in the territory of copyright violation and plagiarism. Fifelfoo (talk) 03:23, 16 February 2012 (UTC)
- If he dosen't come here and address these issues within an hour of resuming editing, I'd say that an indefinate block be issued Is this a threat? He has a life, you know, he is at work right now, and doesn't our policy state "block are preventive not puntatives? What will a block prevent, vandalism from his account? Tbhotch. Grammatically incorrect? Correct it! See terms and conditions. 02:46, 16 February 2012 (UTC)
- If he dosen't come here and address these issues within an hour of resuming editing, I'd say that an indefinate block be issued with the unblock condition that he explain himself on the talk page before being unblocked. I agree we shouldn't move to block him before he responds, but this is serious enough to warrant an immediate response from him. Sven Manguard Wha? 00:04, 16 February 2012 (UTC)
Fabrication of material is about as serious a charge as is possible, and, if shown, should result in a community ban on the perpetrator. One of the few places I support "draconian soutions." Collect (talk) 13:18, 16 February 2012 (UTC)
- I'd say pause this discussion until he chimes in with his side of the story. He may have simply written the wrong magazine name (very easy to do if he was starting to look at People while citing his material from a different magazine) or done something like that. Reaper Eternal (talk) 13:27, 16 February 2012 (UTC)
Web search finds Christina Jansen is credited as the photographer of Lucy O'Brien in this interview (in French), that looks like it contains the types of info cited to "Meeting the woman behind She-Bop" in the Madonna: Like an Icon article (perhaps someone who reads French can check a detail or two). Lucy O'Brien is apparently the author of another book called "She-Bop" (about female rock musicians) so I wonder if some overseas edition of People Magazine had a translation of this interview, and the interviewer's name got garbled by the magazine or by Legolas. Or perhaps the French interview's credits were incorrect, or maybe there is another interview with O'Brien someplace that was actually done by Jansen. As an aside, the "Like an Icon" article looks excessively promotional IMHO, from the brief glance I took at it. I didn't make any attempt to check into how it got that way. 67.117.145.9 (talk) 20:52, 16 February 2012 (UTC)
Topic ban proposed
Moved from Related discussion on ANI Nobody Ent
A proposal: User:The Devil's Advocate may not bring up threads at ANI or any other noticeboard regarding the Article Rescue Squad, broadly construed, and may not nominate for deletion any pages that are part of the ARS project or bring them up for Deletion Review. This includes pages and templates used by the ARS and complaints about ARS members (loosely defined) as regards their activities as ARS members (loosely defined).
- Rationale: too many fishing expeditions and divisive, disruptive, and time-wasting threads in various forums. Violating this ban may be punishable by
tickle death ora block. Please phrase this better if you can. Drmies (talk) 05:13, 16 February 2012 (UTC)
- Funny that you would say "complaints about ARS members (loosely defined)" as you would probably be including complaints about yourself in that situation. Also, it would appear to deny me the ability to make any note of the numerous uncivil remarks you and other editors involved with ARS have made about me pretty much from the outset. You are making this out like I am just going after the ARS for no discernible reason.
- The reality is that I saw an article that should be deleted, nominated it for deletion, and saw the ARS was back to its old tricks just weeks after they got a big wake-up call from the rest of Misplaced Pages (anyone is free to look at that first ANI discussion and the TfD about the rescue tag). I am not repeatedly bringing up the same issue to try and get a different result. The first ANI thread in this latest instance did not directly name a case and focused instead on the fact that the editor most complained about in the previous discussion created the list almost immediately after the rescue tag got deleted in what would seem to be a blatant case of WP:IDHT. That discussion was closed by you, an involved admin (having commented at listing there before going to vote keep in the AfD I started), within five hours based on the MfD result.
- I asked another admin how I should proceed given your involvement and he said the close was premature, but suggested that if I have a specific case to mention I should start a new ANI thread about it and so I did. The result was that more editors came in and several expressed serious concerns about the list and the way it was being used by the editors in question. However, several editors insisted the MfD settled the matter and when that ANI discussion got closed within 17 hours, not including the repeated disruptive closings by involved editors, based on "no consensus for action" (not claiming that there were no legitimate issues as some are insisting) I decided to move the discussion to the MfD. An hour after it was re-opened, before I could even leave my delete vote, an admin stepped in and closed the discussion after a single hour based on there not being a delete vote. So, I asked the admin to re-open, but the admin did not wish to reverse the action and suggested I could put it up for review, which I did.
- This ANI discussion is about someone closing that discussion inappropriately even as more votes were coming in favoring relisting. How exactly could this editor know there would not be more editors who might take an interest and see cause for relisting? Why did this editor not consider the fact that a significant portion of the votes were from members of the project whose page was up for deletion and were not actually providing reasons against relisting? Did this editor intend, as he seems to state, on closing it as having been endorsed either way and just waited until it had a little more input so as to avoid making it look premature? So, you see, it is not about me raising the same issue over and over. Only my call for the closing admin to re-open the MfD and the DRV was trying to restart an old discussion, a discussion that I myself think was initiated prematurely before more people could be drawn to the issue at ANI so that it wouldn't essentially just get ARS members and people who frequent the list voting to keep their beloved page.--The Devil's Advocate (talk) 07:05, 16 February 2012 (UTC)
- Devil's Advocate, "complaints about ARS members (loosely defined)" is an incomplete citation: notice the second part, "as regards their activities as ARS members (loosely defined)" (that should be amended to "in regard to"). You are free to complain about any one of those people, including me (hell, I'll sign up with the ARS if that makes it easier for you to pigeonhole me), Northamerica1000, Dream Focus, the Colonel, Milowent, S Marshall, Spartaz...(let's paint with a broad brush), but not in their activities as ARS members--that is, related to that list or templates or whatever. And I'm not saying you're going after the ARS for no discernible reason: I think there probably are a couple of reasons, but that's not relevant here. Finally, a deletion review may have been the proper step, formally speaking, but that doesn't make it a smart thing to do. You have been told, time and again, that the horse is dead. S Marshall is only the last one of a couple of editors who tried to put it out of its misery. I want to prevent further animal carcass abuse.
I got nothing against you, and I have had few interactions with you outside of those ARS discussions. You were trolled, for instance, and I offered what little help I could give you. Others have complained on your talk page about endless discussions and your tenaciously holding on to sticks (well, straws, probably), and that won't make you any more friends. But I'm focused on this one. I hope you have other things to do beside what appears to be a vendetta against the ARS; I can assure you that those things are probably more likely to be rewarding to you as a Misplaced Pages editor. Drmies (talk) 14:54, 16 February 2012 (UTC)
- Devil's Advocate, "complaints about ARS members (loosely defined)" is an incomplete citation: notice the second part, "as regards their activities as ARS members (loosely defined)" (that should be amended to "in regard to"). You are free to complain about any one of those people, including me (hell, I'll sign up with the ARS if that makes it easier for you to pigeonhole me), Northamerica1000, Dream Focus, the Colonel, Milowent, S Marshall, Spartaz...(let's paint with a broad brush), but not in their activities as ARS members--that is, related to that list or templates or whatever. And I'm not saying you're going after the ARS for no discernible reason: I think there probably are a couple of reasons, but that's not relevant here. Finally, a deletion review may have been the proper step, formally speaking, but that doesn't make it a smart thing to do. You have been told, time and again, that the horse is dead. S Marshall is only the last one of a couple of editors who tried to put it out of its misery. I want to prevent further animal carcass abuse.
- This ANI discussion is about someone closing that discussion inappropriately even as more votes were coming in favoring relisting. How exactly could this editor know there would not be more editors who might take an interest and see cause for relisting? Why did this editor not consider the fact that a significant portion of the votes were from members of the project whose page was up for deletion and were not actually providing reasons against relisting? Did this editor intend, as he seems to state, on closing it as having been endorsed either way and just waited until it had a little more input so as to avoid making it look premature? So, you see, it is not about me raising the same issue over and over. Only my call for the closing admin to re-open the MfD and the DRV was trying to restart an old discussion, a discussion that I myself think was initiated prematurely before more people could be drawn to the issue at ANI so that it wouldn't essentially just get ARS members and people who frequent the list voting to keep their beloved page.--The Devil's Advocate (talk) 07:05, 16 February 2012 (UTC)
- Support, for reasons I detailed almost immediately above this section. Kevin (talk) 05:17, 16 February 2012 (UTC)
- Support He doesn't seem to be likely to give up, no matter how many people try to reason with him. No sense having the same exact discussion every few days from the same determined editor. Dream Focus 08:13, 16 February 2012 (UTC)
- Support TDA's editing here is becoming disruptive and a time-sink. Mathsci (talk) 08:42, 16 February 2012 (UTC)
- Support. The Devil's Advocate needs to go do something else for a while. 28bytes (talk) 10:16, 16 February 2012 (UTC)
- I was doing something else before Marshall's closure brought me right back into it. Even if the only the result of my efforts was the MfD going from keep to no consensus I would be satisified, because it would at least not be presented as a consensus in favor of what ARS is doing (something that I think should go without saying). The funny thing is, I was once more dragged into the ARS stuff because I was trying to cool off from another topic area by going on recent change patrol only to step into this shit again while doing that without even trying. Should you want to make this about conduct, I say you stow this talk of banning me from discussing this and let us all have a broader discussion about ARS in general that isn't going to get closed every few hours. I can provide more than enough evidence of disruptive behavior by more than "a few" editors.--The Devil's Advocate (talk) 10:23, 16 February 2012 (UTC)
- Then do so. Your constant nebulous hints about "having evidence I could provide" are weakening your position and making it seem more like you have an anti-ARS WP:BATTLEGROUND mentality. (And a preemptive caution with regards to WP:CIVIL might not be amiss.) - The Bushranger One ping only 12:44, 16 February 2012 (UTC)
- I was doing something else before Marshall's closure brought me right back into it. Even if the only the result of my efforts was the MfD going from keep to no consensus I would be satisified, because it would at least not be presented as a consensus in favor of what ARS is doing (something that I think should go without saying). The funny thing is, I was once more dragged into the ARS stuff because I was trying to cool off from another topic area by going on recent change patrol only to step into this shit again while doing that without even trying. Should you want to make this about conduct, I say you stow this talk of banning me from discussing this and let us all have a broader discussion about ARS in general that isn't going to get closed every few hours. I can provide more than enough evidence of disruptive behavior by more than "a few" editors.--The Devil's Advocate (talk) 10:23, 16 February 2012 (UTC)
- Support Nobody Ent 13:08, 16 February 2012 (UTC)
- Support Sadly to be sure. Noting that the ban does not prevent you from !voting on any issues - just that you need to take a break from being Sisyphus yourself, as a minimum. Note: "bring up" should be "initiate", and change the "ANI or any other noticeboard" to "any page in projectspace" as being clearer and slightlyy more encompassing, and thus removing the stuff about "deletion review" etc. as it is covered as being in "projectspace".
- User:The Devil's Advocate may not initiate anything on any page in projectspace directly or indirectly referring to the Article Rescue Squad.
- Hoping this is pretty clear. Collect (talk) 13:26, 16 February 2012 (UTC)
- Collect, thank you for rephrasing. As I said to Nobody Ent on my talk page (they kindly left me a note about having moved the section here and retitled it), I was tired when I wrote this up but I wanted to get it started. As for Nobody Ent's move, I've seen such topic ban discussions on ANI and thought it best to keep it in the ANI section that spawned it, but I have no problems with it being moved or edited. Thanks again, Drmies (talk) 14:58, 16 February 2012 (UTC)
- Support, tendentious and disruptive crusading. postdlf (talk) 13:50, 16 February 2012 (UTC)
- Yup, support. User needs help to drop the stick and leave the deceased equine in peace.—S Marshall T/C 14:05, 16 February 2012 (UTC)
- yes please, and I'm most definitely not aligned with ARS... Spartaz 14:43, 16 February 2012 (UTC)
- Support. If there's evidence in the future of the type of behavior that TDA believes he's witnessing, then someone else will bring it to wider attention. TDA's recent contributions on this topic are rapidly approaching disruptive, and a topic ban will allow him to keep contributing elsewhere, unlike a full block for disruptive editing. --SarekOfVulcan (talk) 14:47, 16 February 2012 (UTC)
- support — Ched : ? 14:51, 16 February 2012 (UTC)
- Oppose - Not that I necessarily agree with Advocate's arguments, but this isn't the way to fix the problem. Shutting an editor up with a topic ban is more likely to frustrate that editor and cause him to quit the project than it is to make him see the errors of his ways. I see no reason why these concerns can't be resolved through normal means, i.e. allow his DRV to last the full 7 days, and when it closes the way we all know it will, then Advocate will have no further place from which to argue. Forcibly suppressing the good faith complaints of an editor is very "un-wiki", and should only be considered in extreme cases. —SW— 14:56, 16 February 2012 (UTC)
- Honestly, all I want is to have a discussion that actually lasts for a reasonable duration and is reviewed fairly by someone who doesn't have some sort of bias on the outcome (whatever the bias might be). So far the only discussion that has made it past a day was the deletion review.--The Devil's Advocate (talk) 15:02, 16 February 2012 (UTC)
- Scotty, I think we are dealing with an extreme situation here. And if The Devil's Advocate is the only one to bring up these issues, then maybe that means it isn't much of an issue. Drmies (talk) 15:10, 16 February 2012 (UTC)
- I disagree that it is extreme enough that we have to tell Advocate the equivalent of "Just shut up already!" Advocate is being reasonable in his communication, he's not being uncivil, and he's not asking for unreasonable things (it's not uncommon for someone to complain about an early snow closure when the votes aren't unanimous). Unless I'm unaware of the full history of the situation (in which case, please enlighten me), a topic ban to prevent an editor from even expressing his opinions about a protected class of editors seems pretty extreme. Banning someone from starting ANI threads on a particular topic is one thing, but restricting someone from even mentioning certain editors is overly authoritarian. —SW— 17:28, 16 February 2012 (UTC)
- I don't want him to shut up. I am not proposing a topic ban that would disallow him from expressing an opinion. The topic ban is to disallow him to start ANI threads, deletion reviews, etc (think TfD, for instance) about the ARS. "Restricting someone from even mentioning certain editors"--that's not what I said. Drmies (talk) 19:29, 16 February 2012 (UTC)
- The topic ban includes a restriction preventing Advocate from making "complaints about ARS members (loosely defined) as regards their activities as ARS members (loosely defined)". I'd say that's pretty close to "restricting someone from even mentioning certain editors". It's like using a hatchet instead of a scalpel. —SW— 23:47, 16 February 2012 (UTC)
- I don't want him to shut up. I am not proposing a topic ban that would disallow him from expressing an opinion. The topic ban is to disallow him to start ANI threads, deletion reviews, etc (think TfD, for instance) about the ARS. "Restricting someone from even mentioning certain editors"--that's not what I said. Drmies (talk) 19:29, 16 February 2012 (UTC)
- I disagree that it is extreme enough that we have to tell Advocate the equivalent of "Just shut up already!" Advocate is being reasonable in his communication, he's not being uncivil, and he's not asking for unreasonable things (it's not uncommon for someone to complain about an early snow closure when the votes aren't unanimous). Unless I'm unaware of the full history of the situation (in which case, please enlighten me), a topic ban to prevent an editor from even expressing his opinions about a protected class of editors seems pretty extreme. Banning someone from starting ANI threads on a particular topic is one thing, but restricting someone from even mentioning certain editors is overly authoritarian. —SW— 17:28, 16 February 2012 (UTC)
- Scotty, I think we are dealing with an extreme situation here. And if The Devil's Advocate is the only one to bring up these issues, then maybe that means it isn't much of an issue. Drmies (talk) 15:10, 16 February 2012 (UTC)
- Honestly, all I want is to have a discussion that actually lasts for a reasonable duration and is reviewed fairly by someone who doesn't have some sort of bias on the outcome (whatever the bias might be). So far the only discussion that has made it past a day was the deletion review.--The Devil's Advocate (talk) 15:02, 16 February 2012 (UTC)
- (edit conflict)Oppose pretty much per ScottyWong; I think that there has been quite enough discussion already about the various Arstefacts, but clearly The Devil's Advocate disagrees. It is difficult to know the best way to proceed with a such a dedicated horse-percussionist, but if the substance of his current complaint is that discussion is being stifled, it makes little sense to stifle it further. pablo 15:11, 16 February 2012 (UTC)
- Comment Drmies, I am the one starting the ANI discussions, but definitely not the only one who has concerns. The ANI discussion several weeks ago clearly revealed a lot of disapproval towards the Article Rescue Squadron as a whole. CrossMR and Mbisanz are two I can think of most readily who raised objections about the list this time around.--The Devil's Advocate (talk) 15:24, 16 February 2012 (UTC)
- Sure, but there has always been disagreement with the ARS. Their rescue template is gone now, which I'm sure has appeased a lot of people. (For the record, I don't disagree with the deletion, but I was always more bothered by its injudicious application, which all of a sudden became a topic due to one single editor's activities). But how those threads evolved and were closed reveals a greater impatience with the complaint on the part of the community than it does disagreement with the ARS and how it operates. And here we are again, caught up in yet another discussion. Drmies (talk) 15:33, 16 February 2012 (UTC)
- Further note, look at all the delete votes in the TfD over the rescue tag. Most of those editors I have not seen comment on this recent issue at all.--The Devil's Advocate (talk) 15:31, 16 February 2012 (UTC)
- Ahem. I believe I commented on a thread involving the ARS list that it looked open to collusion and maybe they were trending in that direction, but my comments were refuted and the broader community didn't care; so I dropped it. I then supported the quick closure of the MFD on that topic at DRV as procedurally proper. I haven't been the one starting these discussions or filling walls of text in them. MBisanz 15:47, 16 February 2012 (UTC)
- Weak support, mostly because, whether he's right or wrong about the ARS, it ought to be clear to TDA that his threads about it are not gaining traction on ANI, and aren't likely to. The Devil's Advocate, if you feel that the ARS or its members are being disruptive, you need to take it to an RfC at this point, rather than continually tilting at windmills here on the admin noticeboards. A fluffernutter is a sandwich! (talk) 15:49, 16 February 2012 (UTC)
- Can't exactly take it to an RfC if I am banned from bringing it up altogether. Honestly, if editors here committed to having an RfC on this general issue of the Article Rescue Squadron I would have no issue accepting a ban from mentioning this at places like ANI for some fixed duration of time so long as there is allowance that I be able to contribute to that RfC discussion.--The Devil's Advocate (talk) 16:14, 16 February 2012 (UTC)
- Hm. I think the wording that's up there now is not the wording I saw when I made my initial comment here, or else I wasn't totally awake when I read it. In any case, I'll specify now so I make more sense: I would support TDA being prohibited from opening new AN, ANI, VPP, etc threads about the ARS, to encourage him to use an RfC as the next step in dispute resolution. I very strongly oppose a comprehensive topic ban that prevents him from participating in discussions with or about the ARS, or nominating articles under their protection for deletion and the like. The objective here is to funnel the dispute into proper dispute resolution procedures, not to protect the ARS from criticism. A fluffernutter is a sandwich! (talk) 16:26, 16 February 2012 (UTC)
- Fluffernutter, my proposal (or Collect's rewording) does not prevent, I hope, DA from participating in discussions. Please check to see if your phrasing, TDA prohibited from opening new AN, ANI, VPP, etc threads about the ARS, agrees with my (poorly written) proposal or Collect's proposition. I think it does. Drmies (talk) 16:37, 16 February 2012 (UTC)
- The wording "This includes complaints about ARS members (loosely defined) as regards their activities as ARS members (loosely defined)" is the sticking point in your proposal, Drmies. It would prohibit him from following dispute resolution procedures or, quite frankly, ever criticising ARS members' activities, anywhere, no matter who started the discussion or where it was. Basically, I'm on board with "don't do this here," but I can't support "and also, you may not express a negative opinion about this protected class of people or their club, period." A fluffernutter is a sandwich! (talk) 16:46, 16 February 2012 (UTC)
- I want them to not initiate such complaints about the ARS or about editorsinregardtotheirARSactivities, so to speak. My concern is that complaints will be filed about individual members that turn out to be, in a more or less direct way as the case may be, about the ARS as a whole--such as the very existence of a list of articles that are brought to the attention of the ARS. But I will leave this to the community. What about Collect's short and sweet sentence? Drmies (talk) 16:58, 16 February 2012 (UTC)
- Collect's sentence ("User:The Devil's Advocate may not initiate anything on any page in projectspace directly or indirectly referring to the Article Rescue Squad.") would also prevent TDA from pursuing dispute resolution via places like RfC entirely (and might, in effect, end up banning him from AfD and DRV, since creating anything in those spaces could be considered an indirect reference to the project that patrols them), so I also can't agree with that one. A fluffernutter is a sandwich! (talk) 17:05, 16 February 2012 (UTC)
- I want them to not initiate such complaints about the ARS or about editorsinregardtotheirARSactivities, so to speak. My concern is that complaints will be filed about individual members that turn out to be, in a more or less direct way as the case may be, about the ARS as a whole--such as the very existence of a list of articles that are brought to the attention of the ARS. But I will leave this to the community. What about Collect's short and sweet sentence? Drmies (talk) 16:58, 16 February 2012 (UTC)
- The wording "This includes complaints about ARS members (loosely defined) as regards their activities as ARS members (loosely defined)" is the sticking point in your proposal, Drmies. It would prohibit him from following dispute resolution procedures or, quite frankly, ever criticising ARS members' activities, anywhere, no matter who started the discussion or where it was. Basically, I'm on board with "don't do this here," but I can't support "and also, you may not express a negative opinion about this protected class of people or their club, period." A fluffernutter is a sandwich! (talk) 16:46, 16 February 2012 (UTC)
- Fluffernutter, my proposal (or Collect's rewording) does not prevent, I hope, DA from participating in discussions. Please check to see if your phrasing, TDA prohibited from opening new AN, ANI, VPP, etc threads about the ARS, agrees with my (poorly written) proposal or Collect's proposition. I think it does. Drmies (talk) 16:37, 16 February 2012 (UTC)
- Hm. I think the wording that's up there now is not the wording I saw when I made my initial comment here, or else I wasn't totally awake when I read it. In any case, I'll specify now so I make more sense: I would support TDA being prohibited from opening new AN, ANI, VPP, etc threads about the ARS, to encourage him to use an RfC as the next step in dispute resolution. I very strongly oppose a comprehensive topic ban that prevents him from participating in discussions with or about the ARS, or nominating articles under their protection for deletion and the like. The objective here is to funnel the dispute into proper dispute resolution procedures, not to protect the ARS from criticism. A fluffernutter is a sandwich! (talk) 16:26, 16 February 2012 (UTC)
- Can't exactly take it to an RfC if I am banned from bringing it up altogether. Honestly, if editors here committed to having an RfC on this general issue of the Article Rescue Squadron I would have no issue accepting a ban from mentioning this at places like ANI for some fixed duration of time so long as there is allowance that I be able to contribute to that RfC discussion.--The Devil's Advocate (talk) 16:14, 16 February 2012 (UTC)
- Support per fluff --Guerillero | My Talk 15:55, 16 February 2012 (UTC)
- Support I'm going to support this to try to help this area of the project calm down. MBisanz 15:57, 16 February 2012 (UTC)
- Question - per sandwich, any chance on allowing him one RfC, on whatever this is? Alanscottwalker (talk) 17:25, 16 February 2012 (UTC)
- Here are the relevant pages: first ANI discussion involving the list, second ANI discussion involving the list, and deletion review on the list.--The Devil's Advocate (talk) 20:01, 16 February 2012 (UTC)
- I see there seems to be a dispute about canvassing. I see allot of disputes about what is canvassing and what is notice, in allot of areas, so I don't know if you can be blamed for that. Perhaps, an RfC or mediation can help you guys out.Alanscottwalker (talk) 21:10, 16 February 2012 (UTC)
- Here are the relevant pages: first ANI discussion involving the list, second ANI discussion involving the list, and deletion review on the list.--The Devil's Advocate (talk) 20:01, 16 February 2012 (UTC)
- Support: if for no other reason than that he's not exactly telling the truth about the timing of the DRV closure...it was closed less than 24 hrs. early according to the signature Purplebackpack89≈≈≈≈ 17:41, 16 February 2012 (UTC)
- That's not true. I can only assume you misunderstood something. The discussion was placed in February 10, but I had actually posted it on February 11th so that may be the cause of your confusion.--The Devil's Advocate (talk) 19:27, 16 February 2012 (UTC)
- The discussion wasn't closed until February 16... Purplebackpack89≈≈≈≈ 20:05, 16 February 2012 (UTC)
- That's not true. I can only assume you misunderstood something. The discussion was placed in February 10, but I had actually posted it on February 11th so that may be the cause of your confusion.--The Devil's Advocate (talk) 19:27, 16 February 2012 (UTC)
- Oppose The Devil's Advocate doesn't seem especially annoying and I don't see why he should be singled out when there are other editors with a longer history of such agitation: Snotty, Reyk, Tarc, &c. Warden (talk) 20:26, 16 February 2012 (UTC)
- Oppose Firstly, I want to say that Warden has shown a lot of maturity by the first part of his oppose and I just want to note that it has increased my respect for him. Secondly, although I strongly respect Drmies, I can't help but feel this is retaliation by the ARS. I don't mean to assume bad faith here and I know TDA's ANI threads have become a bit tedious, but trying to silence his concerns is inappropriate. The specific part I disagree with is "complaints about ARS members (loosely defined) as regards their activities as ARS members (loosely defined)." I would prefer a tighter definition, not a loose one.--v/r - TP 21:03, 16 February 2012 (UTC)
- Comment I kinda agree with this. I think the best approach would be TDA pursuing an RFC at this point. He wants a broader discussion about the ARS, and he should be afforded the option of pursuing it rather than squelching him altogether. I don't think he really wants to continue piddling away with canvassing accusations around one specific AFD at a time. I do think the repeated ANI listings have become somewhat disruptive, so I support the nomination only insofar as it might prevent that practice from continuing, but I oppose it being so loosely-defined as to prevent TDA from pursuing the most valid avenue for his concerns: an RFC. ɠǀɳ̩ςεΝɡbomb 21:07, 16 February 2012 (UTC)
- I am not opposed to a rewrite. I can live with Fluffernutter's TDA being prohibited from opening new AN, ANI, VPP, etc threads about the ARS. Tparis, I am not a member of the ARS; if I'm retaliating, it's not on their behalf. (I'm actually not sure if they have membership; I don't have their card or user box.) As for Colonel Warden, I began respecting him a lot more a few years ago already, though I make it a matter of principle to always disagree with him even when he's right. Drmies (talk) 21:48, 16 February 2012 (UTC)
- Oppose This seems like overkill. There are a lot of users with much more of a history of anti-ARS activism. AniMate 21:24, 16 February 2012 (UTC)
- Support It's just gotta stop! Beyond My Ken (talk) 22:00, 16 February 2012 (UTC)
- Oppose - Start the RFC and have wider community involvement. But silencing an editor on a wiki-political topic through a ban? Wow. It was a silly DRV but that leads to this? Tellingly we don't see the laundry list of links to disruptive actions that we normally would in this instance. I'm a little stunned that this was even proposed. Shadowjams (talk) 22:03, 16 February 2012 (UTC)
- That's probably because this was started at AN/I, where the regulars have gotten to be able to set their clocks by the anti-ARS threads this editor has created. - The Bushranger One ping only 23:00, 16 February 2012 (UTC)
- What is? That there's no laundry list? You'll have an inaccurate watch if this is how you set it. I saw 2 ANI discussions (linked above), the one from over a month ago, and then the DRV. One of which was closed by Drmies. Is this the low bar for disruptive now? These seem to be separate complaints in each one, each in response to separate actions by different people. All seem reasonable issues to open (although none of them have consensus for the action TDA wants). TDA should probably cool it only because these generate senseless walls of text that don't seem to go anywhere (which is why we should have an RfC, which might be a senseless wall of text that has the potential to go somewhere). But nowhere in any of this is a reason for a topic ban, particularly when the primary supporters seem to be the people that TDA aggravated. Shadowjams (talk) 23:11, 16 February 2012 (UTC)
- "TDA should probably cool it only because these generate senseless walls of text that don't seem to go anywhere" - yes, that's pretty much the reason there's a topic ban proposal. If you can persuade him to cool it without a topic ban I'll be happy to switch to "oppose". 28bytes (talk) 23:17, 16 February 2012 (UTC)
- I see a distinction between what he should choose to do for sake of efficiency and what the community might force him to do. Silencing someone for what is the wiki equivalent of political speech sets a dangerous precedent. Undoubtedly someone will declare that this is in fact disruptive, but I don't think an objective outside viewer would see this as disruptive, and especially not rising to the level of a ban. Shadowjams (talk) 23:30, 16 February 2012 (UTC)
- That's a fair distinction, but at some point I didn't hear that kicks in, and I think we've reached that point. Really, if TDA were to say "OK, I get that this is annoying a lot of people, I'll drop the stick", we could just archive this and move on. 28bytes (talk) 23:53, 16 February 2012 (UTC)
- Well, there was another ANI discussion about the DRV close provided at the tippy-top of this section, which is what sparked this proposal. All the cards have been played here as far as I am concerned, though, and obviously the deck is stacked against me when it comes to this area of the site. Seems an RfC is the next logical step.--The Devil's Advocate (talk) 00:23, 17 February 2012 (UTC)
- I see a distinction between what he should choose to do for sake of efficiency and what the community might force him to do. Silencing someone for what is the wiki equivalent of political speech sets a dangerous precedent. Undoubtedly someone will declare that this is in fact disruptive, but I don't think an objective outside viewer would see this as disruptive, and especially not rising to the level of a ban. Shadowjams (talk) 23:30, 16 February 2012 (UTC)
- "TDA should probably cool it only because these generate senseless walls of text that don't seem to go anywhere" - yes, that's pretty much the reason there's a topic ban proposal. If you can persuade him to cool it without a topic ban I'll be happy to switch to "oppose". 28bytes (talk) 23:17, 16 February 2012 (UTC)
- What is? That there's no laundry list? You'll have an inaccurate watch if this is how you set it. I saw 2 ANI discussions (linked above), the one from over a month ago, and then the DRV. One of which was closed by Drmies. Is this the low bar for disruptive now? These seem to be separate complaints in each one, each in response to separate actions by different people. All seem reasonable issues to open (although none of them have consensus for the action TDA wants). TDA should probably cool it only because these generate senseless walls of text that don't seem to go anywhere (which is why we should have an RfC, which might be a senseless wall of text that has the potential to go somewhere). But nowhere in any of this is a reason for a topic ban, particularly when the primary supporters seem to be the people that TDA aggravated. Shadowjams (talk) 23:11, 16 February 2012 (UTC)
- That's probably because this was started at AN/I, where the regulars have gotten to be able to set their clocks by the anti-ARS threads this editor has created. - The Bushranger One ping only 23:00, 16 February 2012 (UTC)
- Comment None of this prevents anyone from participating in a discussion - it simply prevents TDA from being the one initiating anything about the "ARS" - which seems the prevailing consensus at this point. Cheers. Collect (talk) 00:10, 17 February 2012 (UTC)
- oppose Did you take this to RfC? or try other forms of dispute resolution? What were the results when you tried mediation? No compelling reason for a ban other than a group that can't take the heat.--Crossmr (talk) 00:35, 17 February 2012 (UTC)
- Move to close No action. Looks like DA agreed to drop any stick he may have been holding, at least with respect to running around with it on AN/I and AN. Alanscottwalker (talk) 01:05, 17 February 2012 (UTC)
- comment If this can all be resolved without more fuss, I'm fully willing to withdraw my support of a ban. I always prefer to see fewer restrictions, unless they are needed. — Ched : ? 01:44, 17 February 2012 (UTC)
- Devil's Advocate, what do you say? Will you drop this stick? Drmies (talk) 04:32, 17 February 2012 (UTC)
- Actually, that's what I want to know as well. Someone else saying that TDA dropped the stick is no substitue for a direct statement from the user. Beyond My Ken (talk) 05:21, 17 February 2012 (UTC)
- I was referring to his last comment in response to the Shadowjams Oppose above, where DA is responding to 28 bytes, which is about 7 comments above, this one. Alanscottwalker (talk) 10:45, 17 February 2012 (UTC)
- I don't think WP:HORSE ever applied, but I don't think there is anything else to do at ANI or DRV. My opinion is that all options have been exhausted here and so it is time to move it somewhere more appropriate where disruption is a lot less likely, such as an RfC as has been suggested.--The Devil's Advocate (talk) 18:55, 17 February 2012 (UTC)
- Actually, that's what I want to know as well. Someone else saying that TDA dropped the stick is no substitue for a direct statement from the user. Beyond My Ken (talk) 05:21, 17 February 2012 (UTC)
- Support the AN part, oppose the XfD part. I'm tired of this repeated drama over virtually nothing. If more templates need to be deleted etc., there are clear venues for that. AN is not among them. ASCIIn2Bme (talk) 04:39, 17 February 2012 (UTC)
- Reluctant support Based on the reply to Shadowjams and this reply to Drmies above, it still doesn't appear TDA will let this go without the community stepping in. I watched many other editors and administrators attempt to convince TDA to let this go and not make additional posts without evidence of wrongdoing, but it simply hasn't stopped. I myself stated in the discussion TDA initiated regarding ARS and myself: "although if he continues the behaviours he has been exhibiting, is it highly likely the community itself will ultimately put a stop to it" so it isn't like he had no way of knowing what would happen if he continued these same behaviours. --Tothwolf (talk) 20:31, 17 February 2012 (UTC)
- Toth, your comments towards me elsewhere can certainly give people an idea of why I wouldn't really pay your objections much mind. Indeed, anyone can go to your talk page right now to see what you did there in response to a comment I left asking you to stop making accusations of bad faith. You saying that your support for a ban is "reluctant" is belied by your comments elsewhere.--The Devil's Advocate (talk) 21:17, 17 February 2012 (UTC)
- Sigh. This doesn't really help you. Yes, perhaps I was a little grumpy when I hatted your comments on my talk page earlier in the week. Perhaps I even could have just ignored them instead of hatting them. You immediately turning around and filing another discussion thread while lashing out at me because I hatted them only served to further escalate matters though. In fact, if it would help deescalate things, I suppose I can unhat them. --Tothwolf (talk) 02:48, 18 February 2012 (UTC)
- Just so anyone here understands. It was not just that he hatted my comments, but how he hatted them. Last comment here on this personal dispute.--The Devil's Advocate (talk) 06:27, 18 February 2012 (UTC)
- Sigh. This doesn't really help you. Yes, perhaps I was a little grumpy when I hatted your comments on my talk page earlier in the week. Perhaps I even could have just ignored them instead of hatting them. You immediately turning around and filing another discussion thread while lashing out at me because I hatted them only served to further escalate matters though. In fact, if it would help deescalate things, I suppose I can unhat them. --Tothwolf (talk) 02:48, 18 February 2012 (UTC)
- Toth, your comments towards me elsewhere can certainly give people an idea of why I wouldn't really pay your objections much mind. Indeed, anyone can go to your talk page right now to see what you did there in response to a comment I left asking you to stop making accusations of bad faith. You saying that your support for a ban is "reluctant" is belied by your comments elsewhere.--The Devil's Advocate (talk) 21:17, 17 February 2012 (UTC)
- Comment As some are wanting me to be clear, I don't see anything more that should or could be reasonably brought to ANI or deletion. You can call it "dropping the stick" if you like, though I see it as all legitimate options being exhausted with regards to this area and the MfD. I should also note that, in the ANI discussion that prompted this proposal, I raised more issues about the DRV close than S Marshall not being an admin. As I had no interaction with the user prior to the DRV I had no reason to think he was in such good standing concerning that space that mentioning his non-admin status would spark the reaction it did. Had I known that, I would have focused on those other issues I had with his closure so as not to offend him or others who know him. All the same, I see no good reason to try and re-argue his closure given the level of support given for it.--The Devil's Advocate (talk) 07:07, 18 February 2012 (UTC)
- Support The Devil's Advocate is heading to arbcom sooner or later...disruptive in numerous forums and articles...tedious, time consuming and not here for anything other than general anarchy...folks need to open their eyes...he was on a 30 day topic ban on 9/11 related articles...once the ban was lifted, he resumed his regularly scheduled programming...has two frivilous Wikiquette Assistance requests going on at the same time...been blocked twice in the last 3 months...now disruptive to the ARS...what's next one wonders.--MONGO 07:14, 18 February 2012 (UTC)
Motion to close
... with no action; let TDA open an RFC if required, this will at least attract wider participation and perhaps be a better opportunity to gauge the opinion of the wider community. pablo 20:21, 17 February 2012 (UTC)
- With 17/24 in support of the topic ban (a support ratio of 70.8%), this should be closed, but with the topic ban enacted. McJEFF 05:40, 18 February 2012 (UTC)
- I would be in favor of leaving this open a little longer. I may yet change my support above, depending on TDA's response. There are a few other editors above who are also on the fence. --Tothwolf (talk) 05:52, 18 February 2012 (UTC)
On the "no consensus to unblock" conundrum
Newyorkbrad has on several occasions drawn attention to the following conundrum:
I would like to propose a way of dealing with this problem. My proposal is simple in outline, so I am airing it here to get a feeling for whether something like this is workable, not for an agreement on detail. My proposal is to take advantage of the fact that blocks have duration and to agree upon a minimum and maximum time for which a bad/contested/controversial/difficult/courageous short block would be tolerable, no matter one's viewpoint, in cases where there is no consensus on whether to overturn the block. This time period might on some occasions provide an opportunity for further thought and cooler heads to prevail (perhaps leading to a reblock with better reasoning and/or a more appropriate duration).
Concretely (for example), if the minimum and maximum times were 24 and 48 hours respectively, then a specific proposal could be that for blocks contested at ANI where no consensus for blocking or unblocking is reached, the block should be procedurally reduced (if possible, and without prejudice concerning reblocking) to the longer of: 48 hours total or 24 hours from the application of the procedure (if this would not reduce the block, then it should be allowed to expire in the normal way).
I won't add to the length this initial post extolling the virtues/benefits of such an approach, but encourage editors to think about whether something like this might have been helpful in past situations they are familiar with. There are obviously similar ways to deal with contested unblocks, but I think it would be simpler to focus on the contested block case first. Geometry guy 23:00, 16 February 2012 (UTC)
- I have to think through all the implications of this, but it's worth considering.--Wehwalt (talk) 23:39, 16 February 2012 (UTC)
- (edit conflict)If there's no consensus to unblock or reduce the length of block imposed, it should not be reduced. What should happen is discussion of what the blocked editor needs to do to get unblocked. This should be done in a respectful supportive manner. By that I mean an editor should not be required to say I am scum of the earth and deserve to die and am grateful you will deign to unblock me, rather, a statement in the vein of When I did X I considered it to be an okay thing to do but now that the community has discussed the situation I understand it's not an okay thing to do and won't do it anymore. Nobody Ent 23:45, 16 February 2012 (UTC)
- I agree with Nobody Ent. No consensus is no consensus to overturn. No consensus means no actions should be taken as a result of the discussion; which means that no unblock should occur. I also want to stress that any discussion on ANI should be 24-72 hours of discussion and most blocks would expire by then anyway.--v/r - TP 23:56, 16 February 2012 (UTC)
- The problem is that this condones a process in which any admin can make a controversial block (perhaps indefinite, or for several days, weeks or months) and immediately bring it to ANI, where support is received from those in favor, and so no consensus is reached to overturn the block, despite the objections from those opposed.
- Consequently, the block stands, for its entire duration, irrespective of whether there was consensus for such a block in the first place. The ability of admins to do this is something felt across the 'pedia and has widespread ramifications, from resentment to allegations of corruption. Blocking policy should be inspired by the ideal of a collective responsibility to use it wisely. There should be no "mover advantages", be they first, second or third and beyond. Geometry guy 00:34, 17 February 2012 (UTC)
- I agree with the collective responsibility concept but don't see it as meaning the block must stand. Editors who disagree with the block shift the discussion to what the unblocking criteria are. Nobody Ent 00:41, 17 February 2012 (UTC)
- correct me if I'm in error, but I understood G Guy to be concerned with the more undetermined type of blocks. Meaning, "indefinite" (which is not supposed to = infinite), rather than the defined 24 - 72 hour, or even 1 week blocks. I think this is worth some consideration, but I'd prefer to think on it (and see some other views) a bit before saying much more. — Ched : ? 00:06, 17 February 2012 (UTC)
- (ec) I think all blocks need to be discussed, but the idea I am proposing would have no effect on the duration of short blocks: instead it might discourage arguing over controversial blocks of less c. 36 hours (based on the figures I proposed); just let them expire, and consider in the longer term whether they were good or bad blocks. If the arguments are unlikely to resolve the validity of the block before it expires, then simply let it expire. Geometry guy 00:34, 17 February 2012 (UTC)
- I understood that to be the case; my suggestion applies to all blocks imposed by a single administrator. Would not apply to community bans and ArbCom blocks. Nobody Ent 00:27, 17 February 2012 (UTC)
- I firmly believe that the default condition if there is no consensus, whether it's a block discussion or an unblock discussion, should be unblocked. Blocks should only remain if there is a consensus for them (because they should only have been enacted if the blocking admin honestly believed there would have been consensus for them if it had been discussed first). That's my strong first preference. However, if (as appears to be the case) there's no consensus for or against this position either, I think something along Geometry Guy's suggestion is a reasonable compromise. People sometimes forget that compromise is at the heart of consensus-based decision making, and this is a good idea for bridging the gap. --Floquenbeam (talk) 00:44, 17 February 2012 (UTC)
- Agreed. It is basically a BRD situation with the R put on hold pending the resolution of said discussion. If consensus doesn't support a block, the block should not remain in effect. Resolute 00:53, 17 February 2012 (UTC)
- I very much agree with this viewpoint that Floquenbeam expresses. Basically per the front page statement:
- Welcome to Misplaced Pages, the 💕 that anyone can edit. For any new editor, IP or registered, the default condition when entering our community is one of "unblocked". I'd rather that there be a strong consensus before relegating editors to the banishment side of "indef". — Ched : ? 01:17, 17 February 2012 (UTC)
- I agree with Floquenbeam on all counts: default-unblocked would be ideal when there's a legitimate disagreement over a block, but if we can't have that, then Geometry guy's proposal is a reasonable compromise. 28bytes (talk) 01:47, 17 February 2012 (UTC)
I'd prefer that we do not over-regulate this, or even over-think it. As it stands, there's no clear margin, agreed, by which we unblock. But there's never a clear margin, and administrators are paid to make the hard calls. Someone says "I see consensus to unblock and I'm doing it." or even "I've done it." We see if it sticks. We find out quite a bit about the decision-making abilities of the people involved. When has this been enough of a problem that we need to make a rule about it? - Aaron Brenneman (talk) 01:26, 17 February 2012 (UTC)
- That's my question - what problem is it that we are solving? "Hard cases make bad law", and here we seem to be making a bad "law" simply in anticipation of a hard case. It seems unnecessary to me. Beyond My Ken (talk) 02:19, 17 February 2012 (UTC)
- Also, "no consensus" should always mean "No change in the status quo." An article exists, someone thinks it should not exist, so it's brought to AfD. The discussion is closed as "no consensus" and the article continues to exist - the status quo continues. Another article is deleted, and is taken to DRV. There's no consensus there to overturn the deletion, so the article stays deleted - again, the status quo remains. Someone proposes a topic ban or an interaction ban, but the discussion comes to nop consesnsus, so there is no ban - the status quo prevails. Someone is blocked, and the block is discussed on a noticeboard, there's no consensus to overturn the block, so the block remains in place (just as it would have if no one had brought it to the noticeboard), since "no consensus" always preserves the status quo. To have it do different things in different contexts is rather illogical, really. Beyond My Ken (talk) 02:32, 17 February 2012 (UTC)
- I think you can stretch that analogy both ways. Is the block the nomination for deletion? If so, in the case of "no consensus" the block should revert to unblock just as an AfD-tagged article reverts to its prior, untagged state if there's no consensus to delete it. The problem with the default-blocked position is that it encourages admins to block when they know there will be neither consensus for keeping the block nor for overturning it. If the default is "unblocked", then admins will be encouraged to seek discussion first in controversial cases, since they gain no advantage by blocking first and then seeking discussion. 28bytes (talk) 02:42, 17 February 2012 (UTC)
- No, it really doesn't work both ways.. There are times when there are discussions on the noticeboard about whether a block should take place or not. When those discussions end in "no consensus", there is no blocked issued. IN each situation, a discussion takes place about an issue raised -- should there be a deletion, should a deletion be overturned, should ther be a ban, should ther be a block, should a block be overturned -- and in each and every case, a "no consensus" closes leaves things exactly as they were before, which is precisely the way it should be. To have "no consensus" result in an overturning of the status quo flies in the face of logic and reason. Beyond My Ken (talk) 06:59, 17 February 2012 (UTC)
- You seem to be saying that it is a problem that admins wiil, when they are unsure about the community's views, use their own judgment -- but isn't that why we pay them the big bucks, because they are trusted to make those kinds of decisions? When the community's will is clear, any newbie could be allowed to push the proper buttons, but when things are not as clear, an admin needs to use their best judgment and make a decision on our behalf. Maybe it's "right" and maybe it's "wrong", but if they have a sound and honorable basis for making it, (most of) the community will understand, even if they decide to overturn it. Beyond My Ken (talk) 07:06, 17 February 2012 (UTC)
- I started to draft a reply, but then noticed Shadowjams' comment below, which says what I was going to say better than I would have been able to. 28bytes (talk) 12:20, 17 February 2012 (UTC)
- No, it really doesn't work both ways.. There are times when there are discussions on the noticeboard about whether a block should take place or not. When those discussions end in "no consensus", there is no blocked issued. IN each situation, a discussion takes place about an issue raised -- should there be a deletion, should a deletion be overturned, should ther be a ban, should ther be a block, should a block be overturned -- and in each and every case, a "no consensus" closes leaves things exactly as they were before, which is precisely the way it should be. To have "no consensus" result in an overturning of the status quo flies in the face of logic and reason. Beyond My Ken (talk) 06:59, 17 February 2012 (UTC)
- Diffs? I'm not aware of cases where someone "rushed" a block knowing it would not have consensus. - Aaron Brenneman (talk) 02:52, 17 February 2012 (UTC)
- A diff of someone's intention? I don't think that's implemented in the current Mediawiki version. 28bytes (talk) 02:59, 17 February 2012 (UTC)
- Oh we only wish. I walked into that one, I'll agree. Do we have diffs (or even just verbal examples) of where it looked like and/or was agreed that someone "got in first"? - Aaron Brenneman (talk) 03:27, 17 February 2012 (UTC)
- Well, I'm torn. I can think of a couple of cases that looked really obvious to me that that's what had happened... but I am extremely reluctant to reopen those cans of worms. Which is a bit of a cop-out, I will admit. 28bytes (talk) 03:38, 17 February 2012 (UTC)
- Oh we only wish. I walked into that one, I'll agree. Do we have diffs (or even just verbal examples) of where it looked like and/or was agreed that someone "got in first"? - Aaron Brenneman (talk) 03:27, 17 February 2012 (UTC)
- A diff of someone's intention? I don't think that's implemented in the current Mediawiki version. 28bytes (talk) 02:59, 17 February 2012 (UTC)
- I think you can stretch that analogy both ways. Is the block the nomination for deletion? If so, in the case of "no consensus" the block should revert to unblock just as an AfD-tagged article reverts to its prior, untagged state if there's no consensus to delete it. The problem with the default-blocked position is that it encourages admins to block when they know there will be neither consensus for keeping the block nor for overturning it. If the default is "unblocked", then admins will be encouraged to seek discussion first in controversial cases, since they gain no advantage by blocking first and then seeking discussion. 28bytes (talk) 02:42, 17 February 2012 (UTC)
- Also, "no consensus" should always mean "No change in the status quo." An article exists, someone thinks it should not exist, so it's brought to AfD. The discussion is closed as "no consensus" and the article continues to exist - the status quo continues. Another article is deleted, and is taken to DRV. There's no consensus there to overturn the deletion, so the article stays deleted - again, the status quo remains. Someone proposes a topic ban or an interaction ban, but the discussion comes to nop consesnsus, so there is no ban - the status quo prevails. Someone is blocked, and the block is discussed on a noticeboard, there's no consensus to overturn the block, so the block remains in place (just as it would have if no one had brought it to the noticeboard), since "no consensus" always preserves the status quo. To have it do different things in different contexts is rather illogical, really. Beyond My Ken (talk) 02:32, 17 February 2012 (UTC)
- This is when it's enough of a problem. Nobody Ent 02:30, 17 February 2012 (UTC)
- It is often a problem. And as NYB says it's currently first-mover advantage, which means in non-consensus cases someonewill block, so block becomes the default, which is probably the reverse of what it should be. We don't like reverting blocks, which sharpens the issue a little. Maybe the common sense answer is GG's idea to make relatively short blocks if consensus has not emerged, and clearly label them as such, without necessarily making a rule about it. Rich Farmbrough, 02:38, 17 February 2012 (UTC).
- If we are talking about how to deal with blocks (or lack of them) for civility, let's discuss that. The whole "first mover's advantage" question is a distraction. - Aaron Brenneman (talk) 02:41, 17 February 2012 (UTC)
Actually, it's a bit chaotic what happens in cases like this. Sometime someone unblocks during the "no consensus" discussion, and sometimes nobody does. It seems to depend on the popularity and number of admin friends the blocked editor has. ASCIIn2Bme (talk) 04:18, 17 February 2012 (UTC)
fat chance of this passing |
---|
The following discussion has been closed. Please do not modify it. |
Different proposalProposal: "No consensus" block discussions with more than ten participants are automatically transferred to a RfC/U discussion. My rationale is that there are really only two means of effective any behavioral change around here: technical means in a imbalance or rights situation (like blocks) and peer pressure. ASCIIn2Bme (talk) 04:07, 17 February 2012 (UTC)
↓↓↓ Oh, hey, here's someone we can ask about how great RfC/Us are. 28bytes (talk) 05:15, 17 February 2012 (UTC)
Simple proposal, thenAfter 24hrs of discussion, in a "no consensus" situation, the block shall be lifted by an administrator. Simple enough, I hope. ASCIIn2Bme (talk) 05:20, 17 February 2012 (UTC)
|
- In other words, the current procedural status quo is fine or at least no worse than the alternatives. Case closed. ASCIIn2Bme (talk) 05:40, 17 February 2012 (UTC)
- After reading much of the above, I think Floquenbeam's proposal is the simplest. We shouldn't complicate the question with vote tallies, nor should we pretend this kind of policy change would have that much practical consequence. What it does have is symbolic meaning in the sense that we defer to open editing, and we defer to open discussion. I think that's a good change. The concept of consensus is wide enough that this won't change anything short-term, but it's an important statement about how we use blocks/bans. Shadowjams (talk) 11:45, 17 February 2012 (UTC)
- I think it would be useful to distinguish two situations: in one, half the administrators want to unblock because the behavior was not that bad, or "the sinner has repented". In the other, they want to unblock because the behavior was not wrong. If it is simply a question of the "punishment" applied, then defer to the original admin; but if half the admins looking at a case think someone's behavior was acceptable and did not deserve sanction at all, then you certainly cannot expect an editor to know any better. Wnt (talk) 17:47, 17 February 2012 (UTC)
- I have two problems with what Wnt has said. First of all, it isn't a consensus of administrators that matters. It is a consensus of editors that matters. Administrators merely have access to tools to do the community's will, they do not have special rights to be the sole arbitors of who gets blocked and when. I hope that was merely a slip of the tongue, and not a genuine belief that only administrators can discuss blocks, or that only administrators opinions should be counted when considering consensus. That would be a completely rediculous policy, and there is nothing at Misplaced Pages to support such an idea. All discussions are open to all members of the community at all times, and all opinions count the same regardless of the presence or absense of advanced positions. Period; that is non-negotiable, as far as I am concerned. Secondly, (hoping that that particular issue was merely a slip of the tongue), is that we shouldn't be splitting hairs to that level. Either a person should edit Misplaced Pages or should not edit Misplaced Pages. That's it. If enough people believe they should be allowed to edit, they should be allowed to edit (whatever "enough people" means, which is a seperate idea). The particular internal emotional processes of the people who believe that idea are irrelevent to the conclusion we should draw. The only thing that matters is if people believe that there will be no future problems. --Jayron32 19:01, 17 February 2012 (UTC)
- Not sure if Wnt's post qualifies, but I see a rampant problem with admins routinely ignoring the opinions of editors. Heck, even the name of this page is "The ADMINISTRATOR'S noticeboard", as if nobody else is allowed into the discussions. A better term would be "The incident noticeboard". (I'm reminded of U-turns on highways which are labelled "For emergency vehicles only" as opposed to "For emergencies only". This means policemen on their way to the donut shop for a break can legally use it, but citizens trying to get to the hospital before their child bleeds to death can not.) StuRat (talk) 19:45, 17 February 2012 (UTC)
- @StuRat: You've made a very specific and deliberate accusation against me. Could you please provide a diff where I discounted, ignored, or belittled anyone because they are not an administrator, here or anywhere else? Because until you produce evidence that I have done so, you can't just go around claiming that I have. --Jayron32 23:46, 17 February 2012 (UTC)
- I said "administrators" because the hypothetical case involved only administrators voting, so there was no need to complicate things (I see how well that worked out... ;). I fully recognize that other users can participate (after all, I am) but the votes of IPs, moderately experienced editors and admins might not be counted as equally, especially where the judgment call of how long to block an editor is concerned.
- It is true that trying to work out the thought processes can be complicated, but actually that's what you'd do in a vote with various levels of users involved. More to the point, especially if neutral and experienced admins are the ones voting, it's possible that they could voluntarily self-label their votes honestly. For an admin to say that someone did nothing wrong is a stronger statement (which reflects back on them to some degree) than to say that someone should get off with a warning; this would compensate for it having more power in a case of 'no consensus'. Wnt (talk) 20:23, 17 February 2012 (UTC)
- Not sure if Wnt's post qualifies, but I see a rampant problem with admins routinely ignoring the opinions of editors. Heck, even the name of this page is "The ADMINISTRATOR'S noticeboard", as if nobody else is allowed into the discussions. A better term would be "The incident noticeboard". (I'm reminded of U-turns on highways which are labelled "For emergency vehicles only" as opposed to "For emergencies only". This means policemen on their way to the donut shop for a break can legally use it, but citizens trying to get to the hospital before their child bleeds to death can not.) StuRat (talk) 19:45, 17 February 2012 (UTC)
- I thing the relevant policy is NOT BURO. Who happens to go first or second is not necessarily relevant to the justice of the issue, and bright line rules of this kind are an encouragement to wikilawyering. If our premier expert of procedure has concerns, and brings them here, my inclination is to think that he is probably right. Of course, arb com could solve this by refusing to deadmin when that would not be equitable, and sometimes it does so decide. But this is an unsafe chance for an admin to rely on, when trying to get something right. DGG ( talk ) 18:35, 17 February 2012 (UTC)
It seems to me that editors are now discussing the title of this thread, rather than the original post, which was much more meta. The problem here is not a shortage of well-argued views on blocking and unblocking, but that these views are not all compatible.
- I agree with Shadowjams that Floquenbeam's view ("the default condition... should be unblocked") is simple and appealing, but closing a discussion as "no consensus" and then unblocking can be controversial, given other reasonable views (TParis, Beyond My Ken) that "no consensus" should mean "no action or change".
- I also appreciate the distinctions made by Wnt on different reasons for no consensus, as well as the issues Rich Farmbrough, Aaron Brenneman and DGG raise about overregulation, bright-line policies, and the first/second mover advantage associated with WP:WHEEL.
The meta-point is that there are many reasonable positions here: there is no agreement on "the default", nor on whether first movers or second movers have the advantage, nor on whether this matters at all. So how do we deal with such disagreements when they affect an actual case? We can't rehash them every time we are faced with a no consensus block.
- If the block were for a matter of hours, such disagreement would rapidly become moot.
This is the main idea that led to this thread. Consensus is not just about agreement, but compromising, and accepting something less than perfect because perfection is unattainable. As well as striving for what we want from Misplaced Pages, we need to consider what we are willing to accept. Reducing a block to one that nobody wants to argue about may often be just a first step in moving a discussion on from the original block to the issues that lie behind it. Geometry guy 23:40, 17 February 2012 (UTC)
- Time-limited blocks for anyone except dynamic IP addresses are usually useless (yes, there are a few isolated specific cases where they are not, so don't bother listing them. I concede them). The only reason for a block is because you believe that a person will, if not blocked, interfere in some way with the effective work at Misplaced Pages. If they will be a disruption, then there is no sense in letting them be a disruption in 24 hours. If they will not be a disruption, then there is no reason to block in the first place. Short blocks are basically completely pointless. If a person is justly blocked, then there isn't any reason to unblock them unless and until they can demonstrate they will not repeat the behavior that led to the block. If a person is unjustly blocked, then being unjustly blocked for a limited time is still unjust. Having a short time-limited block serves no purpose in most cases. It should be the exception, and not the norm, in dealing with disruption. --Jayron32 00:11, 18 February 2012 (UTC)
- I agree with a lot of what you say. At the Civility Arbcom workshop, I argued that blocking experienced editors was a fruitless activity: when or where experienced editors prove to be systematically unhelpful they should be banned, not blocked. (But blocks are needed to enforce bans, contrary to your "only reason".) However, this is not the point. The point is that we may agree on such wise words, but other experienced editors have similar wise words which support completely different positions. The meta-issue is: what do we do about that in practice? Geometry guy 01:04, 18 February 2012 (UTC)
- Time-limited blocks for anyone except dynamic IP addresses are usually useless (yes, there are a few isolated specific cases where they are not, so don't bother listing them. I concede them). The only reason for a block is because you believe that a person will, if not blocked, interfere in some way with the effective work at Misplaced Pages. If they will be a disruption, then there is no sense in letting them be a disruption in 24 hours. If they will not be a disruption, then there is no reason to block in the first place. Short blocks are basically completely pointless. If a person is justly blocked, then there isn't any reason to unblock them unless and until they can demonstrate they will not repeat the behavior that led to the block. If a person is unjustly blocked, then being unjustly blocked for a limited time is still unjust. Having a short time-limited block serves no purpose in most cases. It should be the exception, and not the norm, in dealing with disruption. --Jayron32 00:11, 18 February 2012 (UTC)
- WP:DGAF. Seriously. The key is to remain emotionally detatched and intellectually engaged. Be willing to rationalize and provide reasons for your position, but be indifferent to losing the specific debate in question. If consensus doesn't go your way, then it doesn't. Its no big deal. The only time you lose is when you become emotionally attached to the result of any discussion. On most issues, there will always be reasonable people who disagree. That you do not agree with me does not make you unreasonable; it is not unreasonable to have a different perspective or different priorities or different experiences which give you a different way to judge a situation. So in practice, we all discuss it out, and a neutral party comes along after some time and reads the discussion and makes their best assessment of a reasonable conclusion. That's how it should work. When it doesn't, it's because someone GAFed. If we all obeyed WP:DGAF slavishly, it would all go much better.
- Off the meta-issue, and back on the issue at hand, I pretty much agree that the default position should always be to remain unblocked, regardless of who had the "first move". If the discussion starts before the block, and there is no consensus to block, no block is issued. If the discussion starts after the block, and there is no consensus that the block was appropiate, the person should be unblocked. Status quo is "able to edit". From my perspective, the first change to the status quo is the block if the person is blocked before a discussion takes place. No consensus should always default to THAT status quo, regardless of whether the order goes "Discussion then block" or "Block then discussion". --Jayron32 01:16, 18 February 2012 (UTC)
- Okay, that's an alternative solution: all editors should obey WP:DGAF slavishly. I like the essay too, so perhaps we should make it into a policy. Geometry guy 01:36, 18 February 2012 (UTC)
- No, it exists, which is good enough. Policies, guidelines, and essays should all be followed if they are useful. They should all be ignored if they are not. That's one of Misplaced Pages's core values. The label we apply to a "best practice" is irrelevent; it doesn't matter what we call a good idea: it doesn't become better because we change the label on it. If it works, do it. If it doesn't, don't. DGAF works, so we should do it. --Jayron32 01:40, 18 February 2012 (UTC)
- Sure, but there are a lot of "should"s going on here, and the problem is, not everyone agrees on them or what they imply... Geometry guy 02:16, 18 February 2012 (UTC)
- No, it exists, which is good enough. Policies, guidelines, and essays should all be followed if they are useful. They should all be ignored if they are not. That's one of Misplaced Pages's core values. The label we apply to a "best practice" is irrelevent; it doesn't matter what we call a good idea: it doesn't become better because we change the label on it. If it works, do it. If it doesn't, don't. DGAF works, so we should do it. --Jayron32 01:40, 18 February 2012 (UTC)
- Okay, that's an alternative solution: all editors should obey WP:DGAF slavishly. I like the essay too, so perhaps we should make it into a policy. Geometry guy 01:36, 18 February 2012 (UTC)
Started a thread at WT:BLOCK
I started a thread at WT:BLOCK with a proposed change to the blocking policy based on comments here and NYBs initial presentation of the conundrum. Since the discussion stems on clarification/change to the existing policy, any actual changes and discussions thereof should happen at the policy talk page. Welcome any comments, criticisms, fixes, or counterproposals there. --Jayron32 01:52, 18 February 2012 (UTC)
Please delete copyvio picture
Picture File:A Shiva.jpg are same than in Facebook--Musamies (talk) 06:19, 17 February 2012 (UTC)
- Done. For future reference, you can use {{db-f9}} to request speedy deletion of copyvio images. Jafeluv (talk) 07:04, 17 February 2012 (UTC)
Reviewer flag
I was surprised to see in my watchlist an admin add "reviewer" to an editor's user rights yesterday. Upon looking into it further, I noticed that a couple of other admins were handing them out as well. It appears the reviewer right, previously used for the pending changes trial, has been "repurposed" to support reviewing feedback left with the Article Feedback tool. (Scroll down to "reviewer" at Special:ListGroupRights.)
Basically, it appears that the reviewer right is currently being granted:
- To support an editor's work with the article feedback tool
- When restoring permissions from a desysopped account, transferring permissions from an old account to a new one, etc., and
- To people with no immediate need for it, just in case pending changes ever comes back.
I've got no problem with #1, of course, and #2 is probably fine (albeit unnecessary if the editor doesn't intend to do AFT work.) But since Misplaced Pages:Requests for permissions/Reviewer is now closed to further requests, I wonder if we should be discouraging #3, i.e. just handing it to anyone who'd like to add another right, even a "useless" one, to their hat collection. (Related discussion here.)
If the response here is "meh, let people have useless hats if they want them, it doesn't do any harm", that's fine, but I did want to get more people's thoughts on it. 28bytes (talk) 13:03, 17 February 2012 (UTC)
- Note: Cyberpower678 (talk · contribs) has been courtesy notified of this discussion as an edit of his was mentioned above. Strange Passerby (talk • cont) 13:13, 17 February 2012 (UTC)
- Thanks, but I'd already notified him of the discussion, on Ks0stm's talk page. 28bytes (talk) 13:15, 17 February 2012 (UTC)
- Yes, #3 is what I've done, though never alone, always with rollbacker. I stopped doing it once it was questioned on my talk. I figured that it could come back, it would save work then, and that reviewer was unlikely to be changed so dramatically that any rollbacker wouldn't handle it responsibly.--Wehwalt (talk) 13:12, 17 February 2012 (UTC)
- I wasn't actually expecting Ks0stm to give it to me. That fact that he did was unexpected to me. I added just added that bit to my userpage as I wanted to fix the Rollback statement on my account. Since it's useless at this time, I don't see the big concern to hand it out to editors that follow editing guidelines. If pending changes protection were reinstated, I could strongly assume that the articles that I like to edit would be one of the first to get that protection since a lot of reversions take place there. I would've at that point requested it anyways. I'm not here to collect rights. I'm here to edit Misplaced Pages and to help out. @28bytes: I would kindly ask you to please remove the link to my page as you are making it sound like I am here to collect rights.—cyberpower (Chat)(WP Edits: 517,272,664) 13:21, 17 February 2012 (UTC)
- I think you're missing the point of the reviewing tool — pending changes protection would not affect an autoconfirmed user's ability to edit an article so protected. That said, perhaps 28bytes would be good enough to remove the link, because I agree I don't see your edit as 'button collecting'. Just my non-admin opinion. Strange Passerby (talk • cont) 13:26, 17 February 2012 (UTC)
- In the interest of peace and harmony I have removed the link. 28bytes (talk) 13:34, 17 February 2012 (UTC)
- Let me reword this into what I meant. The pages I edit would've undoubtedly get that protection and and edits that need to be accepted or denied would quickly accumulate and that's when I would request the reviewer right for that page anyways. A lot of reversions take place on that page. I am to the point where I may blow under stress right now and my mind isn't sound right now.—cyberpower (Chat)(WP Edits: 517,274,736) 13:38, 17 February 2012 (UTC)
- In the interest of peace and harmony I have removed the link. 28bytes (talk) 13:34, 17 February 2012 (UTC)
- I think you're missing the point of the reviewing tool — pending changes protection would not affect an autoconfirmed user's ability to edit an article so protected. That said, perhaps 28bytes would be good enough to remove the link, because I agree I don't see your edit as 'button collecting'. Just my non-admin opinion. Strange Passerby (talk • cont) 13:26, 17 February 2012 (UTC)
- I wasn't actually expecting Ks0stm to give it to me. That fact that he did was unexpected to me. I added just added that bit to my userpage as I wanted to fix the Rollback statement on my account. Since it's useless at this time, I don't see the big concern to hand it out to editors that follow editing guidelines. If pending changes protection were reinstated, I could strongly assume that the articles that I like to edit would be one of the first to get that protection since a lot of reversions take place there. I would've at that point requested it anyways. I'm not here to collect rights. I'm here to edit Misplaced Pages and to help out. @28bytes: I would kindly ask you to please remove the link to my page as you are making it sound like I am here to collect rights.—cyberpower (Chat)(WP Edits: 517,272,664) 13:21, 17 February 2012 (UTC)
- (Non-administrator comment) I agree with 28bytes. I see no reason for admins to be randomly handing out the reviewer tool on the basis of a possible reinstatement of pending changes. If an admin is giving it for the purposes of the article feedback tool v5 trial, or to restore rights to a de-adminned user, that seems perfectly legit. Strange Passerby (talk • cont) 13:28, 17 February 2012 (UTC)
- I've been giving it out pretty much under #3 assuming that there wasn't any problem with it and understanding, perhaps incorrectly, that the goal was to actually roll out pending changes again at some point in the future. I'm perfectly happy to not give it out in the future if people would prefer it not be given out at the present time, though. Ks0stm 15:34, 17 February 2012 (UTC)
- I've had the reviewer right given and taken away (see Misplaced Pages talk:Pending changes level two protection for problematic BLPs#Reviewer bit concerns and ). In the interest of further troubleshooting, and as a Refdesk regular, I think I'd be interested to get the bit if it is required for reviewing article feedback to see what it looks like. (though I'm not clear on why this should be - why not send the feedback straight to a talk subpage?) On the other hand I'm not interested in rollbacking - I never figured out a use for that; it sounds like a poor cousin to the Undo button. I continue to oppose Pending Changes, and note that we still have no policy for what criteria should be used either by and toward PC reviewers. How do you decide what to do? Wnt (talk) 00:33, 18 February 2012 (UTC)
- It's going to be one of the userrights that lets someone hide and review the feedback; you can still enact changes based on feedback without it. And, as to sending the feedback to the talkpage: if the numbers hold up (and I hope to god they don't) we'll be getting 127,000 pieces of AFT5 feedback per day. Ironholds (talk) 02:33, 18 February 2012 (UTC)
Campaign for "santorum" neologism RFC close request
This close is on the near horizon - there is no objection to the fact that it is ready for closing - one user just wants to say - please close this - the comments below are mine - this is a hotly disputed issue and needs a strong close to resolve the dispute -
- Involved Users are looking for two combined experienced administrators, that have no ascertainable involvement in this sector under discussion and are willing to close the complicated and lengthy RFC discussion on the "santorum" neologism article. - Talk:Campaign for "santorum" neologism#RfC - Youreallycan 22:14, 17 February 2012 (UTC)
- They should also not have a strong history of taking a particular POV on BLP issues. B——Critical 22:24, 17 February 2012 (UTC)
- WP:BLP - is an en wikipedia policy not an issue - Youreallycan 22:26, 17 February 2012 (UTC)
- There might be people who have been, just for example, involved in forming the policy, and would have the policy go further. At any rate, the admin should come to this fresh without strong POVs about how the policy should be applied. B——Critical 23:01, 17 February 2012 (UTC)
- Yes, it's a policy, and one which people can have different views on. The Blade of the Northern Lights (話して下さい) 22:34, 17 February 2012 (UTC)
- Right, and as with any policy, editors can have a strong POV on how it should be applied. That's all I was saying. B——Critical 23:01, 17 February 2012 (UTC)
- WP:BLP - is an en wikipedia policy not an issue - Youreallycan 22:26, 17 February 2012 (UTC)
- Colleagues, the administrator who chooses to close this will make sure they are uninvolved. You don't need to propose criteria for who can close this. Jehochman 23:25, 17 February 2012 (UTC)
- Just a side observation on one of the comments above, while BLP is a policy, there can still be “BLP issues” with an article….it’s standard terminology. Dreadstar ☥ 23:49, 17 February 2012 (UTC)
Marathon
Resolved – Article protected. Salvio 01:57, 18 February 2012 (UTC)
Help needed to due rash of vandalism in Marathon. Thanks! Location (talk) 01:47, 18 February 2012 (UTC)
- Thanks! Location (talk) 01:52, 18 February 2012 (UTC)
- You're welcome. Salvio 01:57, 18 February 2012 (UTC)