Jump to content

User talk:TonyBallioni: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
Really?: new section
Line 365: Line 365:


You're going to arbitration even before reaching out to me on my talk page? Thanks. Much appreciated. Terrific example of how to address disagreements. --[[User:Born2cycle|В²C]] [[User_talk:Born2cycle#top|☎]] 17:51, 6 March 2018 (UTC)
You're going to arbitration even before reaching out to me on my talk page? Thanks. Much appreciated. Terrific example of how to address disagreements. --[[User:Born2cycle|В²C]] [[User_talk:Born2cycle#top|☎]] 17:51, 6 March 2018 (UTC)
:I'm sorry, but given the above thread on this page and the threads on the other pages, I felt it would likely have just generated more heat than light. [[User:TonyBallioni|TonyBallioni]] ([[User talk:TonyBallioni#top|talk]]) 17:54, 6 March 2018 (UTC)

Revision as of 17:54, 6 March 2018


Quick question

If an editor challenges/removes a block of text from an article that is under 1-RR/consensus to restore, and another editor reverts that removal without getting consensus to restore, is that a violation of DS that requires consensus to restore a challenged edit, or is that ok as that editor's 1RR? The way I see it, an editor can revert once as long as that 1st revert is not restoring a challenged edit. Right or wrong? Atsme📞📧 23:48, 22 February 2018 (UTC)[reply]

Atsme, El C has written a quick and dirty guide to those questions at WP:CRP. I think that page deals with the question in a pretty straightforward way, but if it doesn't answer the question or if I'm missing something, let me know. TonyBallioni (talk) 23:57, 22 February 2018 (UTC)[reply]
Ohhh, my head hurts. In the following sequence:
  1. Editor 1 removes text, Editor 2 reverts/restores - that is 1 RR for Editor 2, or not❓ and Editor 1 must get consensus to add back remove it again, right?
  2. Editor 3 adds text - all cool (breaks the consecutive sequence of editor 1) ✅
  3. Editor 1 adds text in a different section on article, Editor 2 reverts it - does that not count as a 2 RR vio for Editor 2 who now has 1 restore and 1 revert.
  4. Editor 1 removes another block of text - is that now a 2 RR vio for Editor 1? Editor 2 reverts/restores. Editor 2 is now at 2RR vio, or is it ok to revert/restore as many times as needed without a vio? Yes, no? ???
  5. Editor 3 removes text that Editor 2 restored in #1 - is that a vio? In other words, if more than 2 editors are going back & forth, can a 3rd editor revert the material Editor 2 restored?
  6. Editor 3 reverts Editor 2's revert in #3, adding back Editor 1 text - is that a vio?
In real life editing, it's not always a simple 1-2. It can be a 1, 1, 1, 2, 1, 1, 2, 1, 1 if you get what I mean. That's where I get confused. If editor 2 can do unlimited "restores" of editor 1's removals in a 24 hr period, that invites WP:STONEWALLING and promotes WP:OWN. Please feel free to interperse your comments within the applicable numbers in the sequence. Atsme📞📧 01:03, 23 February 2018 (UTC)[reply]
I'll try to respond to this later tonight or tomorrow. Had an early morning today and not much sleep, so I'm a bit too foggy to delve into DS-land now. Just wanted you to know I wasn't ignoring it :) TonyBallioni (talk) 17:52, 23 February 2018 (UTC)[reply]
Atsme, the situation above is complicated, and I might be misunderstand you, so I'll try to respond the best I can, with the disclaimer that admins typically look at the totality of the situation when determining these things (i.e. is it normal editing or a revert).
  1. This would not be a revert for the person who removes the text if the text is in general just there and you can't tell without spending an inordinate amount of time who added it. That's normal editing. Reverts are typically seen as undoing specific edits, in whole or part, not just removing text. Restoring the text by editor 2 would be a revert.
  2. Not a revert, all good.
  3. Editor 2 would have two reverts now, yes.
  4. It depends on if the text was a revert or just normal editing. Editor 1 hasn't reach a revert yet in this scenario if all this is is normal editing and not reverting specific edits. It looks like editor 2 is on 3 reverts now.
  5. At this point, it's getting confusing in hypotheticals, but if I'm reading it correctly, editor 3 restored an edit that was challenged via reversion (the removal of text). This is in violation of the consensus required provision. The best thing at this point is to talk about it, because it is getting into a multi-party edit war.
  6. I'm not going to count vios here, because even reading this scenario, I'm getting confused as to who did what :) I'd likely full protect if it wasn't full protected already as it appears to be a multi-party edit war, but that's just my personal way of handling things. Other admins might view it differently.
Again, so much depends on the context of the specific article in question. In general, the rule of thumb should be "if in question, don't revert." Talking on the talk page is always preferred :) TonyBallioni (talk) 13:35, 24 February 2018 (UTC)[reply]
Ok, what you described is what I was thinking - yes, it's confusing but it's what we're dealing with day-to-day in the trenches, and it can all take place in less than an hour.😳 The DS warning in edit view states: "must not reinstate any challenged (via reversion) edits without obtaining consensus on the talk page of this article" but editors are misinterpretating that statement; e.g. editor 1 removes a block of text, challenging it as noncompliant with NPOV in a BLP (policy considers the 2 inseparable). Editor 2 reverts (restores) the text without getting consensus first. Per the 1RR-consensus in the banner, the vio would be editor 2 restoring (by reverting) challenged material without getting consensus first. Drumroll, please...here comes the confusion...Wikipedia:Consensus_required#Removal contradicts what the banner states. WP:CRP overrides 1RR-consensus and encourages status quo stonewalling by giving Editor 2 (the reverting editor) the advantage in both Addition and Removal. The result we're getting is that Editor 2 controls the article by not allowing new information to be added or any existing material to be removed. See what I mean? I'm pinging El C regarding this issue and would very much appreciated his input regarding the latter. I think it's important that we get clarity or we're going to lose more editors to TB and blocks. Atsme📞📧 14:46, 24 February 2018 (UTC)[reply]
Well, the point of the restriction is to promote the status quo. It's about challenged edits not challenged material. Galobtter (pingó mió) 14:57, 24 February 2018 (UTC)[reply]
Actually, promote article stability/reduce edit warring which means promoting the status quo. Galobtter (pingó mió) 15:05, 24 February 2018 (UTC)[reply]
That works well for long established articles that are stable, such as GAs and FAs, but not so well for political and other controversial topics that are not, especially BLPs where NPOV is at issue. Then it can quickly become Wikipedia:Status_quo_stonewalling or OWN which is disruptive behavior. It also gives paid/COI/advocacy editors an advantage, which can be harmful to the project.
In cases of DS 1RR-consensus only, when a standing edit is challenged and removed based on a policy vio, it should not be restored until after consensus has been reached. If a new edit is added and later reverted, the editor who reverted should be responsible for providing a PAG-based edit summary to justify the revert, which eliminates the "IDONTLIKEIT" revert. If no policy is cited, the editor who added it should be free to revert once. Then if removed again by a 3rd editor, consensus would be required. Each revert should count as 1RR.
Adding:
Editor 1 adds
Editor 2 reverts (1RR) - provides policy based edit summary
Editor 1 reverts (1RR)
Editor 3 reverts (1RR)
Editor 1 needs consensus to add.
Removal:
Editor 1 removes standing text (1RR)
Editor 2 restores text (1RR)
Editor 3 removes text (1RR)
Consensus is needed to restore.
What am I not seeing that prevents us from doing it that way? Atsme📞📧 17:20, 24 February 2018 (UTC)[reply]

Is this paraphrasing too close?

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


[1]

Not asking for revdel here because the problem is that quotation marks were removed without sufficient changes to the text. Assuming I'm reading it correctly. Am I crazy?

The quotes were not "too long or numerous" to begin with, IMO, just that without inline attribution it looked like we were attributing them to the wrong person, so I don't think having the quotes would be a copyright problem, but I suspect not having them in quotation marks might be.

Hijiri 88 (やや) 08:25, 23 February 2018 (UTC)[reply]

I'll try to look at this later today. If I don't get back, please feel free to poke me. TonyBallioni (talk) 17:53, 23 February 2018 (UTC)[reply]
Hijiri 88, yeah, that's too close. I've fixed it and revdel'd. Margin1522, it might be easier to include attribution to the source in the sentence if the concern is that the reader will think someone other than the source quoted said it. TonyBallioni (talk) 13:17, 24 February 2018 (UTC)[reply]
Thanks. That would be wise – with a Japanese source it's usually better to assume that quote marks mean paraphrase. Maybe someone will do that. I added one quote that I was able to verify in the original UN document, but right now I don't feel like doing much more with this article (having been mocked on the Talk page).– Margin1522 (talk) 16:38, 24 February 2018 (UTC)[reply]

Sorry...

... but what about this? The source says The prime minister explained that the word was used initially by Japanese facing food shortages in the past when they told their children to make sure there were no leftovers and our article currently says In 2005, Japan's Prime Minister Junichiro Koizumi explained that Mottainai was initially used in the past by people facing food shortages, they telling their their children there were no leftovers. The only paraphrasing is inserting the name of the prime minister, replacing "the word" with the word in question (not italicized or placed in quotes; if I had copyedited it without examining the source I might have accidentally changed it back to "the word") and some ungrammatical stuff at the end. Hijiri 88 (やや) 22:24, 25 February 2018 (UTC)[reply]

Ugh This edit summary made me suspicious. Every edit from the page's creation to the most recent included this unmarked copy-pasted text, and I don't have time to check the other sources right now. What's the policy here? Revdelling the entire history seems like essentially the same as page deletion, but are you WP:INVOLVED now that I posted this on your talk page rather than proposing speedy deletion? This is a mess... Hijiri 88 (やや) 22:39, 25 February 2018 (UTC)[reply]
See this and this. I am beginning to think Dream Focus (talk · contribs) might need a serious talking to about close paraphrasing and unmarked quotations, and maybe even a block if this continues (entirely aside from his continued personal attacks). Hijiri 88 (やや) 23:20, 25 February 2018 (UTC)[reply]
Hijiri 88, I've revdel'd the content you asked about at 22:24. Since I don't have access to a source, I would suggest you list the other article at WP:CP specifying the offline source. This will give you time to look at other sources and verify if it is G12 eligible or if it just needs revdel. TonyBallioni (talk) 00:25, 26 February 2018 (UTC)[reply]
Which source do you mean? All three of the ones in Mottainai Grandma are online and linked in the article (although I have not checked all of them yet). The text I removed (as part of the Japan International Cooperation Agency efforts in India) was lifted almost directly from the source (as part of the Japan International Cooperation Agency (JICA)'s efforts in India), and I was since reverted. The only way it could not be copyvio is if the phrase as part of the Japan International Cooperation Agency efforts in India is brief enough that copying it word-for-word is acceptable. Hijiri 88 (やや) 00:55, 26 February 2018 (UTC)[reply]
Sorry, misunderstood you as to where the material was coming from. I don't mind doing any of this (I like copyvio work), but it is easier for me if I can see the source. If you're removing copyvio material, the way I suggest doing it is to have an edit summary such as rmv copyvio from http://wwww.example.com/abc123, that makes it easier to deal with. I've cured the copyvio above, and revdel'd. It's short, but there is a plausible paraphrase that works better. I've gone ahead and revdel'd. TonyBallioni (talk) 01:04, 26 February 2018 (UTC)[reply]
Cheers! Yeah, I'll try to do that in the future. The problem here is actually that the article was created to make a WP:POINT, by an editor who clearly hadn't read either the book itself or any of the sources very closely. He has repeatedly described it as a "novel" (even a "bestselling" one) when it is in fact a short children's picture book. I think the ultimate fate of the page should be to be redirected to the main mottainai article, which would make all the copyvio stuff kinda redundant (I guess it could be the difference between deleting and redirecting and just redirecting). Hijiri 88 (やや) 01:15, 26 February 2018 (UTC)[reply]
I did not make the article to make a point. I have created articles in the past for books I have never read nor care about, as well as documentaries, and random other things. See User:Dream Focus/Articles I created which no one successfully managed to delete. Your accusations of it being Pointy, is as baseless as all the others you have made against me since the whole ARS argument started. You need to stop focusing on me and find something else to do. Dream Focus 00:51, 28 February 2018 (UTC)[reply]
  • I've basically cleared Immigration Street of copy-pasted text (although I may have inadvertently turned it into a quote-farm in the process). Would you mind rev-delling everything up to this edit?
More generally, his response to my warning doesn't look promising, and the more digging I do, the worse it seems to get. This is the oldest I've located, but per AGF I can't be certain it was verbatim plagiarized; the blanking I did was motivated as much by the content being inappropriate. He doesn't seem to add substantial amounts of prose to articles very often, but the samples I've checked included copy-pasting (or close paraphrasing) around two thirds of the time. His reliance on free online sources at least makes checking relatively easy (when he directly cites the sources), but he has almost 30,000 edits going back more than ten years, which is very concerning, and the older ones (such as this one) don't seem to cite their sources, which would make checking very difficult.
Do you think another CCI report is in order?
Hijiri 88 (やや) 05:43, 27 February 2018 (UTC)[reply]
As for Super Cauldron article from 2009, a lot of Atari game articles I saw back then just listed the brief information about them from the game box. When I did that it said in a reference that was from the game box. [2] With games like that, nothing else you can say about them, there not much to them. As for Immigration street, I answered that [3]. I'd appreciate an administrator responding to that. Dream Focus 16:05, 27 February 2018 (UTC)[reply]
Just noticed this. @Dream Focus: If there is "nothing else you can say about" a product than what is on the box it came in, then the topic does not meet GNG. I'm sorry to bring this up again, but someone who has !voted in as many AFDs as you have should understand our notability guidelines better than that. This is basically unrelated to copyright concerns, mind you. Hijiri 88 (やや) 00:04, 28 February 2018 (UTC)[reply]
Dream Focus, I asked Primefac to take a second look at the Immigration Street article as well. I'll let him post his thoughts here, but my initial thoughts are that at least some of the content in that article constitute a violation of the English Wikipedia's copyright policy as a close paraphrase. Given the above concerns, I do think that a WP:CCI is likely the best way forward here. TonyBallioni (talk) 16:12, 27 February 2018 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

SPI

You may wish to see this SPI, given your extensive knowledge about the user-work-styles etc.:)~ Winged BladesGodric 07:31, 24 February 2018 (UTC)[reply]

Godric, yeah, I saw it. Bbb23 was right to close. No evidence there (and I looked through the contribs myself before he closed it.) TonyBallioni (talk) 12:41, 24 February 2018 (UTC)[reply]

Please don't.

Resolved

- clearly, I am not on the same page as the community on this one. Mr rnddude (talk) 06:38, 3 March 2018 (UTC)[reply]

With regards to this, you are a brand new admin of well less than six months. Nominators should be experienced and respected admins with an excellent track record. Bluntly, you do not fit that profile. Mr rnddude (talk) 12:12, 24 February 2018 (UTC)[reply]

There is no requirement that nominators be experienced admins, or admins, or experienced. As I'm sure you well know, there have been self nominations which have succeeded, and nominations by some of our most experienced users with access above sysop which have failed. To be blunt, I'm not sure it's necessary to be so blunt when sharing what is essentially only your personal opinion. GMGtalk 12:19, 24 February 2018 (UTC)[reply]
Mr rnddude, first, you will notice that I never said I was going to offer to nominate Lourdes. I said I was intending to email her. That email was going to encourage her to run, and explicitly encourage her to find an experienced nominatior. It likely would have included the line “I’d be fine nominating, but I’m sure you can find someone much better than me.” Also, in terms of nominations in general Wikipedia:Requests for adminship/Joe Roe was the first successful RfA after my own. Joe did all the heavy lifting there to be sure, but to my knowledge at least, my being a nominator doesn’t seem to have been held against him. TonyBallioni (talk) 12:39, 24 February 2018 (UTC)[reply]
Tony, with the most substantial tenure, experience, contributions and faith of the community you have here, you'd be the best nominator even if you weren't an administrator. I'm not quite sure why rndude wrote what he did, but I don't agree with his understanding of who can be nominators, and I'm confident the community too doesn't. Lourdes 12:43, 24 February 2018 (UTC)[reply]
I didn't !vote on JoeRoe's adminship as I don't know anything about them. I don't vote on editors RfAs I know nothing about, or where I don't have a strong opinion one way or another. E.g. I don't know Lourdes, so I'm not voting on their RfA. Mr rnddude (talk) 12:58, 24 February 2018 (UTC)[reply]
Nominators should be experienced and respected admins with an excellent track record 100% not true. Nominators can and should be anyone, and have frequently been non-sysop users. In fact, I think it'd be better if more nominators weren't sysops. ~ Amory (utc) 12:46, 24 February 2018 (UTC)[reply]
I'd be less bothered by a non-sysop nom, than a fresh admin nom. It's the fresh admin bit that bothers me here. I'm not saying TonyBallioni is a bad admin, just that a fresh admin pulling in new admins impacts on my view negatively. Very negatively. I'm just one person though. Mr rnddude (talk) 12:58, 24 February 2018 (UTC)[reply]
I can assure you that you are in the very small minority on this one. Nihlus 13:04, 24 February 2018 (UTC)[reply]
"Nominators should be experienced and respected admins with an excellent track record" smacks somewhat of an attack on Tony's record. Anyway, that sort of statement is probably better off in a personal opinion essay than as an accusatory statement of fact on an editor's talk page. Ivanvector (Talk/Edits) 13:06, 24 February 2018 (UTC)[reply]
Meh, I know how WikiPolitics works. There are certainly better nominators out there than me. I'll be the absolute first person to admit that, and frequently do when people ask me about RfA. The statement about new admins not being nominators isn't really true though, at least within the last 18 months or so. After his own RfA, TNT did a several successful nominations, and those seem to have turned out fine. I think you can have a good discussion as to the impact the choice of nominator(s) has on an RfA, but generally, being a newer admin doesn't seem to have a huge negative impact unless that admin also has a bad reputation elsewhere (which who knows, I might. There are certainly people who don't like me around.) Anyway, all the best. TonyBallioni (talk) 13:10, 24 February 2018 (UTC)[reply]
Hmmm... I'm not interested in WikiPolitics. That's why I addressed you directly. I chose to present my concern to you, rather than drop it on a talk page (I mean talk page other than your own). – And to you. Mr rnddude (talk) 13:22, 24 February 2018 (UTC)[reply]
(edit conflict) I know of few who fit the desirable profiles and combined qualities as Tony and Lourdes, both of whom I've found to be knowledgeable, patient, willing collaborators who served well in the trenches, and with the kind of fortitude and humility we seek in our administrators. Tony has proven to be an excellent admin right out of the box, and I have no doubt that we'll see the same from Lourdes. We could use 100 more just like them. Atsme📞📧 13:23, 24 February 2018 (UTC)    [reply]
Agreed. Mr rnddude is entitled to his opinion, but like others here I don't share it. Tony and others should be positively encouraged to nominate suitable candidates, as indeed Lourdes has proved to be, because by all accounts we are facing an admin shortfall these days. If I understand correctly, the concern here is that having gained the bit, Tony now plans to to head-hunt and recruit other admins sympathetic to some hypothetical nefarious aim of his, and wreak havoc on our wonderful encyclopedia. But even if this highly bizarre hypothesis were actually true, a nomination does not an automatic admin make. The community would vet and scrutinise each nominee as they always do, and the candidate would be promoted or otherwise on their own merits.  — Amakuru (talk) 17:42, 24 February 2018 (UTC)[reply]
Indeed, if there is such a thing as an admin shortfall, then it's not resolved by stopping nominations...if the editor (not admin) is experienced, that's all that will matter. In any case, potential admin recruits know not to accept noms off anyone but: a noob making a nom will—almost always—be declined and G6'd sharpish. >SerialNumber54129...speculates 18:14, 24 February 2018 (UTC)[reply]

Uploaded files

Hello, you said yesterday that you were interested in Catholicism. Well, I am very interested too, and I have just uploaded these files, but I'm not sure where to put them. Could you also show me some articles about Catholicism that would need work? Thanks. L293D () 15:44, 24 February 2018 (UTC)[reply]

I mainly do early modern Catholic history (conclaves in particular are my thing on Wikipedia). Gerda Arendt does a lot of work with German hymns and is one of our most prolific music contributors. She’d probably be able to give better advice than me on this topic. TonyBallioni (talk) 15:53, 24 February 2018 (UTC)[reply]
(talk page watcher) @L293D: The first two of those files already have articles, so they're the obvious choice—and would benefit from their addition; and, having three other files with no articles means...they have to be written! Excellent results all round-Go for it! >SerialNumber54129...speculates
Do you think they would be notable enough? L293D () 16:00, 24 February 2018 (UTC)[reply]
I'm afraid I don't really know; I've tried to avoid them since they were the scourge of my schooldays  :) but, tbh, I don't really see why some (like the ones we already have) would be, and these not. Especially the old Victorian ones, as they have their own historical tradition. A good way of finding out, L293D, is to do a Google search—but narrow it down to Googlebooks. That way, you omit the cruft, as it were. Like this, for example. >SerialNumber54129...speculates 16:06, 24 February 2018 (UTC)[reply]
Thanks for asking me, - perhaps The C of E knows more about English hymns, even if not Catholic. You can search within Wikipedia for these titles, which may appear in lists of songs, or as some lyricist's work, where a sound file would also be good. A Protestant German example of how to include it is "Gelobet seist du, Jesu Christ". --Gerda Arendt (talk) 16:14, 24 February 2018 (UTC)[reply]
Holy, Holy, Holy and Lift High the Cross already have their own pages. The C of E God Save the Queen! (talk) 16:33, 24 February 2018 (UTC)[reply]

Any help around Psalm 84 - hymns based on it, place in liturgy etc - welcome. --Gerda Arendt (talk) 23:35, 28 February 2018 (UTC)[reply]

  1. Psalms (Understanding the Bible Commentary Series)—Broyles, C. G.
  2. Eerdmans Commentary on the Bible—Dunn, J. D. G. & Rogerson, J. W.
  3. The Early History of God: Yahweh and the Other Deities in Ancient Israel—Smith, M. S.
  4. Studies in the History of Religions—Layton, B.
  5. In the Shadow of History: Jews and Conversos at the Dawn of Modernity—Faur, J.
  6. A History of Baroque Music—Buelow, G. J
  7. Biblical Narrative and Palestine's History: Changing Perspectives 2—Thompson, T. L.
  8. Gender Differences and the Making of Liturgical History: Lifting a Veil on Liturgy's Past—Berger, T.
  9. A History of Pastoral Care—Evans, G. R.
  10. Exploring Psalms: An Expository Commentary, Volume 1—Phillips, J.
and more generally (although most of the above also discuss psalms holistically)
  1. Abiding Astonishment: Psalms, Modernity, and the Making of History—Brueggemann, W.
  2. The Psalms as Christian Worship: An Historical Commentary—Waltke, B. K., Houston J. M. & Moore, E.
  3. Encountering the Book of Psalms: A Literary and Theological Introduction—Bullock, C. H.
  4. The Psalms: A Historical and Spiritual Commentary—Eaton, J. H.
  5. Psalms—Mays, J. L.
  6. The Oxford Handbook of the Psalms—Brown, W. P.
Etc.
Apologies to TB for the mild breach of WP:NOTBIBLIOGRAPHY on his page... ...SerialNumber54129...speculates 13:19, 4 March 2018 (UTC)[reply]
Thank you! You could place it on the talk of Psalm 84 ;) - Will get to it later, - protest song mood today, - see my talk. --Gerda Arendt (talk) 13:29, 4 March 2018 (UTC)[reply]

Rollback

Hey, Tony. I previously requested Rollback and was intercepted by Oshwah, who politely refused and advised garnering more experience with vandalism. My contributions feed should now host a few examples of my intercepting vandalism through Pending Reviewership. Shall I continue or is this sufficient to proceed into Rollback? - Conservatrix (talk) 09:57, 26 February 2018 (UTC)[reply]

Wouldn't this be a better question to ask Oshwah? Primefac (talk) 13:28, 26 February 2018 (UTC)[reply]
Yes, Oshwah is better for such things than me :) TonyBallioni (talk) 13:44, 26 February 2018 (UTC)[reply]
I have pinged Oshwah in the past but he does not respond. - Conservatrix (talk) 02:32, 27 February 2018 (UTC)[reply]
Make a request at WP:PERM then. It is easier to review there, and other people can have a look too, which I think is good. TonyBallioni (talk) 02:34, 27 February 2018 (UTC)[reply]

Bots Patrolling and Moving

Hi TonyBallioni, you mentioned me in Wikipedia:Village_pump_(proposals)#A_Bot_for_Creating_Arthropod_Stubs,_Trial. Can you describe the step-by-step scenarios that need some blanks filled in a little more? Some notes:

  • Bot flagged accounts include autopatroll, if they create a page (e.g. a Draft) it will already be patrolled, if the page is later moved to mainspace by the bot it will also still be patrolled.
  • If an autopatroller (such as a bot) makes a draft, and a non-autopatroller moves it to mainspace it will be in the newpages feed, and be un-reviewed. Does that help? — xaosflux Talk 14:27, 26 February 2018 (UTC)[reply]
Yes, perfect, you answered the questions without my needing to explain it. I was unaware that bots are autopatrolled (which I still find somewhat disturbing for mainspace, but that's another matter). Thanks as always for your help. TonyBallioni (talk) 14:30, 26 February 2018 (UTC)[reply]
Though, Xaosflux, before I say something stupid at VPR, could you verify that an account with the autopatrolled permission moving an autopatrolled draft to mainspace will not cause it to be autopatrolled. It seems implied in your last bullet, but just want to be clear. Thanks again. TonyBallioni (talk) 14:32, 26 February 2018 (UTC)[reply]
Bots are autopatrolled because their edits are supposed to be made by trusted editors using an approved process. Keep in mind that some bots create pages in namespaces besides (Article) and that patrolling is used in all namespaces (example: unpatrolled new user-talk pages).
So for the example you want:
  1. A page is created in Draft: space by a bot
  2. The same page is moved by the same bot to mainspace. (Assuming w/ redirect, with talk page?)
Correct? — xaosflux Talk 14:41, 26 February 2018 (UTC)[reply]
Yes, I get it in terms of the non-article namespaces . No the process I was asking about was:
  1. Bot creates Draft:Foo, it is autopatrolled.
  2. Human Editor A who is autopatrolled moves the draft to mainspace.
Would the article hit the new pages feed? Thanks again. TonyBallioni (talk) 14:45, 26 February 2018 (UTC)[reply]
I went ahead and DID this so you can see. A bot (User:Fluxbot) created Draft:The weather in London in winter and an autopatrolled editor (User:Xaosflux ep) moved it to The weather in London in winter. It is ALREADY reviewed and PATROLLED. All pages hit the NewPages feed, however most people would filter it out as it is already patrolled:

Take a look at it, let me know if you have any more questions before I delete it. — xaosflux Talk 14:58, 26 February 2018 (UTC)[reply]

Perfect, thanks! Feel free to delete it now! Sorry for being so annoying on this. Bots typically aren't my thing (and I have no strong opinions on bot policy as a whole), but the creation of new pages is something I do care about. All the best! TonyBallioni (talk) 15:01, 26 February 2018 (UTC)[reply]
Please also note, the "being patrolled" in mainspace was about the person doing the move, not about how it was created in Draft so much; if a non-autopatrolled person move the page it would be unpatrolled in mainspace. — xaosflux Talk 15:15, 26 February 2018 (UTC)[reply]
Yep, got that. Thanks again. TonyBallioni (talk) 15:16, 26 February 2018 (UTC)[reply]

recently uploaded files

Hello, someone just said on my commons talk page that the files listed here are 'deriviative works' and may be deleted. Could you explain? L293D () 16:09, 26 February 2018 (UTC)[reply]

L293D, it means you haven't listed who the original composer is and the information for that. i.e. none of these melodies are your original composition. Lucky for you, the first three appear to be out of copyright. To Jesus Christ Our Sovereign King is actually the tune ICH GLAUB AN GOTT, and the version you are likely playing off of is copyright 1986 (and the Harmonizer is British and died in 2010, which means it will lapse out of copyright in 2080.) It will have to be deleted on Commons (I'll tag it as such after this). The other three appear to be in copyright. The tune for Holy, Holy, Holy is called Nicea and was composed by John Bacchus Dykes in 1861. He died in the 19th century, so has been dead for more than 70 years. Thaxted (tune) (the tune for O With Thy Benediction) lapsed out of copyright in 2004 as Gustav Holst died in 1934. Crucifer (Lift High the Cross) lapsed out of copyright as of May 2017. Hope this is helpful. TonyBallioni (talk) 16:52, 26 February 2018 (UTC)[reply]
Also, the tune for Rejoice the Lord is King was composed in the 18th century [4]. You should be good on that one . You might also find c:Commons:Copyright rules by territory helpful. TonyBallioni (talk) 16:56, 26 February 2018 (UTC)[reply]
L293D, I've updated the sourcing information on Commons, which should be enough to save the existing files for deletion. I've also asked an admin there about moving File:O With Thy Benediction.ogg to something such as File:Thaxted (Holst).oga as the tune is used in several popular songs (I Vow to Thee, My Country being the most known song played to this tune. In terms of Church music, O God, Beyond All Praising is likely more popular than O With Thy Benediction in the United States currently, at least in Catholic circles, and I suspect it'd likely be the same for Anglicans.) TonyBallioni (talk) 15:43, 27 February 2018 (UTC)[reply]
Great! Just one thing: why is it named File:Thaxted (Holst).oga when its an .ogg file? L293D () 19:29, 27 February 2018 (UTC)[reply]
I suspect a typo. Primefac (talk) 19:34, 27 February 2018 (UTC)[reply]
Ogg is just a container, and can be used with various file types. .ogg is ambiguous, so the .oga (.ogv, .ogx) extensions are used to indicate the type of file. The software automagically changes .ogg to the more specific extension when renaming files. --AntiCompositeNumber (talk) 19:58, 27 February 2018 (UTC)[reply]
AntiCompositeNumber is my official technology advisor because of shit like this. TonyBallioni (talk) 20:08, 27 February 2018 (UTC)[reply]

Reviewer rights

Thanks for accepting my request. Best. Eagleash (talk) 14:46, 27 February 2018 (UTC)[reply]

2FA / AWB

Hi TonyBallioni, just FYI: we were able to get Alaa's AWB working using Wikipedia:Using AWB with 2FA. — xaosflux Talk 15:15, 28 February 2018 (UTC)[reply]

Thanks, Xaosflux, we seemed to cross paths there. Glad everything is working. TonyBallioni (talk) 15:26, 28 February 2018 (UTC)[reply]

You may wish to revoke the talk page access as well. —MBL talk 16:25, 28 February 2018 (UTC)[reply]

I would support it and for PH's own benefit, who seems hell-bent to dig his own grave.~ Winged BladesGodric 16:35, 28 February 2018 (UTC)[reply]

Sarah Jane Brown

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


Hi Tony - just to say thanks for the closure, but I'd like to ask you to look at one thing. Your close cites WP:NATURALDIS, but applies it wrongly. The wording clearly says "Using an alternative name that the subject is also commonly called in English reliable sources", but it was amply demonstrated in the discussion that "Sarah Jane Brown" is not at all common in sources. That was by far the main reason why the current title is not valid per our policies. The only justification for retaining it there is because of an IAR type situation. Please could you look at this again, because although I don't see that issue addressed one way or the other. Thanks  — Amakuru (talk) 18:31, 28 February 2018 (UTC)[reply]

Thanks, Amakuru, yes I agree with that and addressed it slightly when I was thinking about it, but I don't think it made it's way into the final close. The naming policy generally prefers natural disambiguations even when they aren't the most common name, just common enough. I think you were the one who pointed out that the question was whether or not the reader will think it is the wrong person when they reach the page. The discussion as a whole tended to think there wasn't a strong case that they would be confused. There was sourcing presented for Sarah Jane, but it was relatively minor. If it had been stronger, it would likely have tipped the discussion fully to not moved in my view, but I think it was sufficient to make what you call the IAR votes have some basis in the policy so not as to completely be IAR. I think the wording used in the close was slight preference, and it really is just that, slight. I'll ping @Primefac and SkyWarrior: for their thoughts. TonyBallioni (talk) 18:46, 28 February 2018 (UTC)[reply]
Thanks for the close. Didn't go down the way I wanted, but your judgment of the consensus was accurate, and you were kind to all sides. --GRuban (talk) 19:18, 28 February 2018 (UTC)[reply]
TonyBallioni, I was just going to ask the same question that Amakuru did, and I don't find your answer to be satisfactory. The definition of natural disambiguation is "an alternative name that the subject is also commonly called in English reliable sources". The discussion clearly showed that the subject of the article is not commonly called "Sarah Jane Brown" in English reliable sources (she's called that in almost no sources - this was not disputed), and is therefore NOT a natural disambiguation. So I'm troubled that even in your answer here, as well as in the close where you even say "it comes down to a question of policies and guidelines", you continue to refer to this name as natural disambiguation. It's missing the whole point of the decade-long objection to this title. Frankly, that's exasperating.
I had a second question too. While I agree the raw !vote counts cannot be totally ignored, I hope we agree what needs to be given far more consideration is the weighted !vote counts. Yes, there were JDLI arguments on all sides, but there were strong policy-based arguments too. Did you actually do a count after discounting all of the "this option is better than the current title" !votes accordingly? I ask because I did not see any indication in the close that this was done. If it wasn't, can you please do so now? I'm curious as to the outcome.
While I'm at it, did you look at the previous RM from a weeks ago which I withdrew early for reasons specified there? Did you take any of that discussion into account in your decision? --В²C 19:56, 28 February 2018 (UTC)[reply]
This was a three person close, and upon reading it, we all came to the independent conclusion that there was definitely no consensus for a move. The question was between no consensus, no consensus to move, and not moved. None of us felt any justification for a move based on the discussion, and while you are correct on the definition of natural disambiguation, it was a point of discussion that was raised during the RM. Those opposing the stable title disagreed that it was met, but those opposing a move either felt it met or were unconvinced by the arguments against it. I get the whole point of the decade long objection to the title, but for a five years, no one has been able to achieve consensus to move it or achieve consensus that the objection was a good reason to have a different title, and the move to it was endorsed at a move review, so it isn't like this title hasn't gone through enough vetting. Finally, I personally didn't take into account the previous RM, as there was more than enough to read in the one we closed, and it had been listed on the centralized discussion, meaning that there was going to be a much wider audience commenting. This also means that I didn't expect them to cite the ALLCAPS policies and guidelines that RM regulars are familiar with, but looked at the policy basis for those arguments. RMs are not !votes, but a move over the numbers from a stable title needs to be done with a strong policy backing, and I don't think there was a strong enough reason to do so, especially as this has been a stable title for so long.
To the point of people who preferred the other titles to the current one, yes, I took it into consideration. I also took into consideration the people who supported the current title and said that they opposed all the others without opposing them. There simply isn't a consensus for a move at this time, just as there hasn't been at any of the 8 previous RMs trying to change the title. You are free to ask for a move review, but I expect that will be an even bigger mess than the RM itself was, and don't think it will change the eventual outcome. TonyBallioni (talk) 20:42, 28 February 2018 (UTC)[reply]
Tony, respectfully, and I'm kind of addressing this to you because you're the senior admin on the panel, you've been around the block as much as we have, and you know how these things go. I am not upset at the result per se - I was hopeful we might get a different outcome, but was pragmatic about the possibility that the close might be to retain the current title. What I didn't expect was what to me is what looks like a fairly bland dismissal as "no consensus" without much explanation. Respectully again, I don't get the impression from the two paragraph close that the panel really got down into the detail (and believe me, we have collectively spent *a lot of time and effort* discussing that detail over the past 2 weeks). In particular, the assertion was made many times in the discussion that WP:NATURALDIS is off the table for this article, because "Sarah Jane Brown" is not a common name. NATURALDIS simply doesn't apply, yet the close cited it a a valid reason to retain the status quo. The aim of this exercise was to put the question to bed, so that we can all feel that the correct result was achieved, and I just don't feel that has happened. It's not a question of going to move review, you're probably right that the decision would be endorsed, it's a question of seeing evidence that the panel considered everything in the discussion, and that the result was really policy based, with the relevant policies set out in black and white, rather than a head count. Thanks, and I hope that makes some sense.  — Amakuru (talk) 21:07, 28 February 2018 (UTC)[reply]
Amakuru and Born2cycle, another factor to take into account is that Sarah Brown is a public-relations specialist—she has held PR-related positions since she left university over 30 years ago—so it's safe to assume that she understands the importance of a name. If she had objections to Sarah Jane Brown, she would have made those known. SarahSV (talk) 21:29, 28 February 2018 (UTC)[reply]
SlimVirgin, while her having objections to it, and making them known, would make the case against using it a bit stronger, usage in reliable sources is our definitive guidance for titles for every other article on WP, as far as I know. Subject preference is not that important (unless it is reflected in reliable source usage). Otherwise we would move Cat Stevens to Yusuf Islam. Frankly, I'm baffled by how many very experienced editors seem so willing to dismiss the source usage evidence in this one case. I can't think of another example like it. Why does it not matter here? I just don't get it. --В²C 21:55, 28 February 2018 (UTC)[reply]
A BLP subject objecting to a title matters a great deal. It's not definitive, but it's certainly important.
There is very little source usage that is helpful in this context. The sources describe her as Gordon Brown's wife, because his notability outweighs hers. But describing someone and deciding what to use as a biography title are different issues. Often they coincide, but don't let that blind you to the fact that they are separate processes. Titling the article as "someone's wife" would be inappropriate for all the reasons others have explained. Alternative parenthetical descriptions—such as Sarah Brown (public relations)—have failed to gain consensus.
And so we have fallen back on what she calls herself. Sarah Brown isn't available, but there is also Sarah Jane Brown (e.g. the Companies House registry) and Sarah (Macauley) Brown (e.g. the LinkedIn page). Given that the article has been at Sarah Jane Brown for nearly five years, I have to assume that she's aware of it and doesn't mind. SarahSV (talk) 22:19, 28 February 2018 (UTC)[reply]
There are hundreds of reliable secondary sources that refer to her as Sarah Brown and describe her as GB's wife. None of them use SJB. Yes, it turns out, there are one or two primary sources that use SJB, which finally someone dug up, but these are not anywhere near sufficient to qualify as natural disambiguation (because it is not a name "that the subject is also commonly called in English reliable sources". That qualification is in there for very good reason. Therefore we must use parenthetic disambiguation. The whole discussion should be about which parenthetic disambiguation to use; SJB should not even be on the table. Her lack of objecting is hardly relevant (we can agree to disagree on how much it would matter if she did object); I don't understand why you even bring that up. --В²C 22:33, 28 February 2018 (UTC)[reply]
  • Amakuru, I understand your point and frustrations (and I never mind having discussions with you because you are always so clear and raise such good arguments, and I appreciated reading them in the RM). Primefac wrote the draft of the close and is about a year "senior" to me on the admin status, but the thoughts there incorporated my thoughts that I had expressed already, which are basically what I am laying out here. I understand your objection based on the sourcing to the natural disambiguation argument.
    You are correct that it is not the most commonly used name or even that common at all, but there was sourcing provided beyond the mere Companies House listing to show that it is used by some. This was specifically mentioned in some of the supports and is implicitly invoked in others that thought it did meet NATURALDIS. While I do seriously understand your views and took (and take) them very seriously, I don't think we can entirely discount the arguments.
    B2C, I know you have made the argument that this name doesn't exist, but it was shown pretty clearly in the RM that it does for the purposes of WP:V. Experienced editors were satisfied with the sourcing for that, and enough of them preferred the stable title (or opposed the other titles for policy based reasons) to make it so that there really wasn't any way that this could be moved. I understand your common name arguments, but there were enough people opposed to the parentheticals on policy reasons that a move didn't make sense. It isn't a vote, but the policy based reasoning for the two options that were expressed for (born 1963) or (née Macaulay) were not strong enough to overcome the support for Sarah Jane Brown.
    There were some who supported that title on IAR grounds, but there were others who had a legitimate policy disagreement with you all over NATURALDIS (namely, they thought the sourcing showed it was common enough that no one would be confused). I don't believe that those arguments can be completely cast aside, just like I don't believe that your arguments can be completely cast aside because other disagreed with you. There was not a consensus for a move after a thorough consideration of all the options by the community at large after it was advertised at CENT. I know how frustrating this is especially after you put so much work into it, but I think that we did consider all the opinions and went back and forth over the exact way it should be closed. I hope this answer sheds a bit more light for both of you as to my thought process at least, even if you disagree with parts of it. TonyBallioni (talk) 22:23, 28 February 2018 (UTC)[reply]
In ten years nobody ever produced a single source using "Sarah Jane Brown" until late into this latest RM discussion. Not being British I did not immediately understand their validity as primary sources. My assertion that the name didn't exist (not exactly what I said, but whatever) was made before I was made aware of these sources, and is probably what prompted someone finally to produce something. However, to try to draw a distinction of significance between "the name is never used in sources" (what I initially argued) and "the name is never used in reliable secondary English sources" (what I would have modified my position to be had I not been pulled into an AN/I for commenting too much there), is quite a stretch. Even now you don't seem to understand how irrelevant these tiny number of primary sources are compared to the hundreds of thousands of reliable secondary sources of which none use SJB and are secondary and reliable, as far as I can tell. But even if there are a few, again, that doesn't come close to meeting the "natural disambiguation" hurdle of "commonly called in English reliable sources". Not even close. If you didn't realize that, as you appear to not have realized, you really should consider rethinking your decision. As far as I can tell, you (the panel, not just you personally) did not appreciate that the current SJB title is not natural disambiguation, you relied heavily on counting raw !votes and not at all on counting weighted !votes with JDLI !votes filtered out to determine consensus, in particular you clearly did not discount the opposes to "wife of" none of which were based on policy or guidelines, and you did not realize the dearth of reliable secondary sources that use SJB. In short, you did not seriously look at finding the best alternative supported by policy to SJB, did you? --В²C 23:02, 28 February 2018 (UTC)[reply]
(talk page stalker) There's clearly not a consensus supporting any of the move options: the (activist)-like options, the (wife of Gordon Brown)-like options, or the (born 1963) option. And as I said in my !vote, there's ample precedent for using uncommonly-used middle names as natural disambiguation of page titles on other articles; there's no policy reason that can't be the title. power~enwiki (π, ν) 23:14, 28 February 2018 (UTC)[reply]
(edit conflict) Just because you have a strong opinion that others are wrong does not mean that they are. I am completely neutral on this topic and evaluated it as I would evaluate any RM: taking into account that people can have legitimate disagreements as to whether sourcing is sufficient for guidelines and not placing my personal views in it.
I also very much disagree with your assumption that we are required by policy to seek to replace the title. The obligation is on those seeking a move to demonstrate consensus exists to move from a stable title. This is especially true when the stable title has been stable for a significant period. It isn't just a numbers game or just a policy game. The reason we have discussions is so we can see how the community thinks based on policies and guidelines, and we are supposed to take into account the differing views of people on this. If there was a single correct interpretation of policy, we wouldn't need RMs.
I get that you and Amakuru don't like the sourcing on this, but a significant number of people disagreed with you on whether that policy condition was satisfied. We don't just discount their opinions because they have a different view than you do. Nor were your opinions discounted: they had weight and they caused it to not close as a full not moved closure. TonyBallioni (talk) 23:18, 28 February 2018 (UTC)[reply]
We are entitled to our own opinions, but not our own facts. That there is a dearth of usage of SJB in reliable sources is an indisputable fact and, therefore, SJB is not natural disambiguation is also a fact, by definition. That "wife of..." is not opposed on policy grounds is yet another fact (or somebody would cite the policy that supports opposing "wife of"). That there was no "consensus" (dictionary meaning) to move is also a fact. But your job is not to find "consensus"; it is to find WP:CONSENSUS, and that is very different. In particular, it means looking at facts, policies and strength of arguments. With all due respect, it appears you did none of this. How it looks to me, and you've said nothing to indicate to the contrary, is you counted raw !votes and decided there was no "consensus", and the rest is rationalization. If you're satisfied with your job on this, that's very disappointing. But you're not alone to do this; conflating "consensus" with WP:CONSENSUS is exactly why many similar years-long title disputes didn't get resolved sooner either. I have a list on my user page. --В²C 23:51, 28 February 2018 (UTC)[reply]
I am satisfied with my reasoning here, yes. I know you aren't, but I did take into account policies and guidelines and all views. There is no starting assumption that we must move the title anywhere that would be policy based, and the point of an RM was not to find the alternative to this, but to decide if it should be moved, and if so, to where. There was not consensus to move it at all, considering all the factors, which includes policies and guidelines as the participants in the RM thought they best applied to this article. If I were to take the position you take, I should have !voted rather than closed, as I would have made my mind up to the first question (that a move was required by policy) without consulting the legitimate views of others and the legitimate objections to other titles. TonyBallioni (talk) 23:57, 28 February 2018 (UTC)[reply]
I never said there was a "starting assumption that we must move the title anywhere that would be policy based". That should have been a mid-way point you discovered, through WP:CONSENSUS finding. The point is that the WP:CONSENSUS, as determined by policy-based arguments in the discussion, clearly showed that the current title was not natural disambiguation and therefore not a valid disambiguation of the topic's WP:COMMONNAME, which is "Sarah Brown" (another undisputed fact). Therefore the WP:CONSENSUS of the community (though not the "consensus" of the RM participants) was that the title should be "Sarah Brown" disambiguated parenthetically. Look, it was a complicated RM, but I think you could have handled it. You just didn't dig much. You went by surface appearances, by what the "consensus" was. I get it. In most RMs "consensus" and WP:CONSENSUS are the same, so it's easy to forget the differences. But sometimes the differences are critical, and that's what the case was here. --В²C 00:10, 1 March 2018 (UTC)[reply]
I think you missed the point, B2C. The title doesn't fucking matter in any way. What matters is that we stop having debates about the title. You're just pissed because you didn't win. My point is that even if you had "won", it would be irrelevant. The only important part of the close is the moratorium. It makes next to no difference what the title is, just that the interminable debates stop. If it had been moved, it wouldn't have stopped the debates, so moving would have not stopped the problem.--Jayron32 05:06, 1 March 2018 (UTC)[reply]
I think the point Born2cycle was making is that if the title was moved towards a parenthetical the dispute would've ended foreverish like in the examples above rather than delayed for two years, because while people may not like the parenthetical such as (born 1968) that much, they're generally neutral/not overtly policy violating enough that no one really would care to restart the move discussions. Galobtter (pingó mió) 07:43, 1 March 2018 (UTC)[reply]
That's exactly it. I don't have a crystal ball, but in my view Sarah Brown (born 1963) or some other neutral parenthetical is the long-term stable title for this article. In 10-20 years, that's where it will be, and nobody will request for it to be moved again. That disambiguator is accurate, precise, inoffensive (in a way that "wife of GB" clearly isn't), and although people don't generally know her precise year of birth, it's in the right ballpark, and will be vastly more recognizable for that reason than the current misleading title. It also has decent precedent in the Barbara Bush (born 1981) example. What we needed in this close, was either a panel bold enough to make that move now, or to give us a proper convincing reason why we're wrong when we say the current title is bad and flouts our policies. To use the graph on the right as an analogy, we're currently at the point marked "local minimum", it looks somewhat stable, and some people feel happy enough, but where we really want to be is "global minimum" - it takes some effort to get there, but when we do, the whole thing will be in a more stable state, just like all those articles B2C lists above.  — Amakuru (talk) 09:49, 1 March 2018 (UTC)[reply]
Amakuru, I think you know me well enough to know I’m not going to supervote on a preference and that if I thought there was consensus for a move I would have made it (or advocated for it with the other closers since it was a panel). I don’t have a problem moving against the numbers when justified, but I don’t see how that was possible here. If I were the primary drafter I would have probably done a bit more explaining the balancing of various factors, but that’s a stylistic approach that I take when writing closes, and I still have no problem endorsing the language used in it. If another RM occurs at some point in the future and a parenthetical gains consensus, I’d have no problem moving it, but none of the options had consensus here. Anyway, as always thanks for your comments both in the RM and in this thread. They’re appreciated and highly valued . TonyBallioni (talk) 13:35, 1 March 2018 (UTC)[reply]
TonyBallioni you don't seem to distinguish consensus of the participants and consensus of the community. In fact, given the close and everything you've written since, it appears you gave no consideration at all to consensus of the community as reflected in policy, guidelines, and conventions. The support of "Sarah Jane Brown" as "natural disambiguation" flies in the face of what WP:NATURALDIS says. The opposition to "wife of ..." is not supported by any policy or usage, and is blatant violation of NPOV. You apparently totally and completely ignored all of this in determining "consensus". No one is questioning your genuineness. You really believe there was no "consensus" to move. In fact, no one even disagrees with this. Yes, among the participants there was no consensus to move. But your job was to determine the consensus of the community as well, and you did not do that at all. --В²C 17:41, 1 March 2018 (UTC)[reply]
His job is to assess and close the discussion and assess the consensus thereof; there is no universal already established proper way to name the article; if there were there wouldn't have been a disagreement to begin with. The participants and the admins in question were all well aware of the guideline and policy pages you keep bringing back up; there is just a disagreement over what they mean and how they apply in this case. Because there is a disagreement, there wasn't any consensus to move it. Different is not wrong, and there are just different understandings of what those guidelines and policies mean and how to apply them. --Jayron32 17:46, 1 March 2018 (UTC)[reply]
You're making the same mistake he is. You're conflating disagreeing about what the title should or shouldn't be with disagreeing what policy and usage says the title should or shouldn't be. Those favoring Sarah Jane Brown and disfavoring "wife of..." disambiguation erred in thinking WP:NATURALDIS supported SJB, and didn't even try to support their opposition to "wife of" with policy. No one argued how or why NATURALDIS supports SJB - they just asserted it did. No one countered the argument in the proposal that SJB was not supported by NATURALDIS because SJB was not commonly used in sources (and no one disputed that fact). Tony did not do his job. He did not evaluate the strength of the arguments based on policy. --В²C 17:52, 1 March 2018 (UTC)[reply]
Yes, I did. This was a community-wide RM that was advertised at CENT. That a significant number of experienced editors disagreed with your reading of the policy is highly suggestive your interpretation of the community consensus is not the only valid one. It was not my job to make the empirical judgements, it is the job of the discussion participants to apply the community consensus to a particular article and interpret how it should be applied. I will again repeat that there is absolutely zero policy basis for requiring a move here and that your frame of reference for what this RM was supposed to achieve is not in line with policy: the first question before all others is if there was either a community or local consensus to move. There wasn’t. TonyBallioni (talk) 18:02, 1 March 2018 (UTC)[reply]
No, I'm not claiming that at all. What I am saying is that quoting policy is not a trump card that overcomes the differences people have in interpreting that policy. You don't get to just point at a policy page and say "Look Policy!" as though that is sufficient to win any argument. People are aware of that policy, they even agree that the policy is there and valid. What they disagree with is your interpretation of that policy. Policy does not interpet itself, and its existence does not mandate any single outcome. It can help guide discussions by recognizing common outcomes and behavioral norms at Wikipedia, so it certainly leads discussions in certain directions, but policy is not like a law of physics where the universe simply automatically obeys it. Policy requires interpretation and application, and there is the disagreement. You can't just shout "you're wrong" at people who are reading the same policies you are and reaching different conclusions. --Jayron32 18:25, 1 March 2018 (UTC)[reply]
That sounds great in theory guys, but there was none of that in the discussion. No one was arguing that WP:NATURALDIS should, or even could, be interpreted to support "Sarah Jane Brown". The supporters of SJB just ignored it. No one argued that there was policy opposing "wife of...", much less how to interpret some particular policy to support it. No policy was even cited to support that view. This was not a dispute about policy interpretation - this was a dispute about whether to follow or ignore policy. --В²C 18:34, 1 March 2018 (UTC)[reply]
  • I'd support a WP:MRV on this one. No offence to the closers TonyBallioni, SkyWarrior and Primefac who were confronted with a hell of a job, but seeing a lack of "policy-based reasoning for moving a page" (there was plenty of that nonetheless and basing the outcome exclusively on policy-founded !votes would have shown something completely different), and then starting to misrepresent policy ("WP:NCDAB states that natural disambiguation is preferred" – it doesn't, or, at least, the current article title does not conform to the minimal requirements for natural disambiguation which include "... commonly used in English ..." as made explicit in the WP:MIDDLENAME guidance) shows a lack of experience in this type of closures (and does indeed amount to a supervote). Not less important, several procedural irregularities were mentioned by participants in the RM: the closers didn't even address the question whether these irregularities might have influenced the outcome. --Francis Schonken (talk) 06:32, 1 March 2018 (UTC)[reply]
    • See my responses to B2C: just because you think policy mandates one thing, doesn’t mean that others who disagree with you are wrong. Others considered your arguments on this and disagreed with your interpretation of the policies in this case and made their own arguments based on the same policies and sourcing. One of the biggest points of an RM is to determine how we apply policies and guidelines to specific articles given the empirical data. Your arguments were heard, but so were the arguments of those who had a different view than you. In terms of experience closing RMs, Amakuru can tell you that I’m pretty experienced in this realm (even though he disagrees with this closure). TonyBallioni (talk) 13:19, 1 March 2018 (UTC)[reply]
      • Yes I read the discussion above, and that's why I proposed DRV in my first comment: reasoning on this page seemed to have already come to a dead end before I started to participate. --Francis Schonken (talk) 13:31, 1 March 2018 (UTC)[reply]
        • Thats your perogative, like I said to B2C, it’d likely be a bigger mess than the RM itself and at best end up as no consensus to overturn (and like Amakuru said, likely end up endorse). I think I’ve been pretty clear with my personal reasoning here, I think it’s policy based, and I’m familiar enough with RMs and closing RMs to know that there wasn’t a reasonable outcome that ended with a page move after that discussion. I’ve closed plenty of complicated RMs before, and while this one was more complicated, the outcome was pretty clear at the end. TonyBallioni (talk) 13:45, 1 March 2018 (UTC)[reply]
          • Please don't put words in my mouth: I don't contest the no-move result (although, frankly, keeping it open somewhat longer before closing would have been a viable option too). So please stop your straw man argumentation, it doesn't impress me for one bit. --Francis Schonken (talk) 13:52, 1 March 2018 (UTC)[reply]
  • (talk page stalker) Procedurally, the RM was a shitshow, but that was largely due to the efforts of people complaining now about the outcome. I understand the argument why a parenthetial disambiguation would be better, though I still don't agree with it. I don't have the slightest idea how there's supposed to be a consensus for "wife of Gordon Brown" as the disambiguator, apart from the fact that some very noisy people seem obsessed with it. power~enwiki (π, ν) 07:51, 1 March 2018 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Hello

I appreciate your recent reply to me.[5] I want to say that you never said a thing out of the way to me that even remotely seemed to besmirch my sensibilities. My expressions were self loathing, generated out of frustration, and mostly, they were misplaced in that comment! I did wish that I had participated in the discussion where the details of the proposal were decided. In fact, it just occurred to me that you'd have done yourself a great service had you linked that discussion at the RfC's outset. It would seem that forgoing uninformed commentary like mine is the way forward. And I'd have been glad to give you such a break too. Is there such a link? Even now, I'd like to see it (perhaps even more; now) Cheers.--John Cline (talk) 00:42, 1 March 2018 (UTC)[reply]

John Cline, the on-wiki discussion is at User talk:TonyBallioni/Ban reform workshop. I also got feedback from other admins off-wiki, and if I recall that is what led to the "publicly documented" bit. TonyBallioni (talk) 00:46, 1 March 2018 (UTC)[reply]

Thank you

Thanks for deleting my user page. Can you also delete my talk page? DBZFan30 (talk) 01:55, 1 March 2018 (UTC)[reply]

(talk page stalker) User talk pages are not generally deleted per WP:DELTALK. You can archive it or blank it if you wish. --Majora (talk) 01:59, 1 March 2018 (UTC)[reply]
DBZFan30, as I have told you three times now: we do not delete user talk pages except in very exceptional circumstances. Yours is not an exceptional circumstance. There is also nothing I can see there that qualifies for revision deletion. Same goes with the All Star article. If you want a rename, you can request it at Special:GlobalRenameRequest and a steward or global renamer will action it. I would recommend you do that last part now as it will speed up the process by which you are renamed. I'm sorry for being blunt here, but I've already told you the same thing twice, and There'sNoTime has as well. The answer is not going to change if you keep asking: administrators on this Wikipedia would be violating policy if we were to do what you asked. TonyBallioni (talk) 02:01, 1 March 2018 (UTC)[reply]
@Majora: Archiving and blanking my talk page won't do anything.
@TonyBallioni:, I'm asking you nicely to delete my talk page right now, no questions asked. You won't be violating any policies. DBZFan30 (talk) 02:27, 1 March 2018 (UTC)[reply]
@DBZFan30: I’m telling you right now that there is not a single administrator on this project who is going to delete your talk page. TonyBallioni (talk) 02:39, 1 March 2018 (UTC)[reply]

Rollback

Hello, could you make my rollback right permanent? Its expiring tomorrow. Thanks, L293D () 02:53, 1 March 2018 (UTC)[reply]

Tony suggested just going back to WP:PERM/R to be reassessed, but I've gone ahead and made it permanent, it's been used well enough. L293D, please remember that rollback is only to be used for obvious vandalism, and make sure to check the entire diff as well as the edits before it, especially if from the same editor. ~ Amory (utc) 12:30, 1 March 2018 (UTC)[reply]

Unblock leoleo7495

What i would do in the future will be to bring information and to correct if there are errors if necessary in user talk not in the talk page of the article unlike i used to to.leoleo7495(talk) —Preceding undated comment added 12:16, 2 March 2018 (UTC)[reply]

leoleo7495, Acroterion was the blocking administrator, so they would be better to talk to than me. I just declined the unblock request. From what I recall, the issue was that you were using the talk page as a forum for disputes over which animal was better and the like, and not using it to discuss things that were relevant to a Wikipedia article. TonyBallioni (talk) 13:43, 2 March 2018 (UTC)[reply]

Revert

Tony, I saw that you reverted me. Don't worry, I won't touch your revert. However, I disagree that the topic ban is clear at all. Sandstein's link goes to, just like I said, a section that's been archived and noted as "NOT AN AE BLOCK" therefore, there's nothing to support the topic ban. Further consensus on the AN page shows SVG did nothing worthy of the block to begin with, therefore there should be no reason for a ban. I disagree that this shouldn't be discusses and left to consensus, but I'm a bit biased as I'm under one myself, so like I said, I'll leave it alone.  К Ф Ƽ Ħ Speak 14:14, 2 March 2018 (UTC)[reply]

Hi KoshVorlon, Sandstein unblocked MapSGV. This was his regular non-AE admin action. He specifically stated that he was lifting the block to be replaced with a topic ban. He then followed through and made it an AE topic ban, which he logged at the AELOG for 2018. AE actions are taken upon the discretion of individual administrators, and do not require consensus to impose. The editor who has been sanctioned is free to appeal to either AE or AN, but only they are allowed to make the appeal. Other editors are not. See Wikipedia:Arbitration_Committee/Discretionary_sanctions#Appeals_by_sanctioned_editors, which I quoted on your talk page. I reverted your reopening of that thread, because it was asking for a review of a sanction that no longer existed and because you don't have the ability to ask for the review of another editor's sanctions. If they want to appeal, they should do it on their own, and I would suggest them doing it at WP:AE, though AN is an option. TonyBallioni (talk) 14:32, 2 March 2018 (UTC)[reply]

More mottainai copyvio

Hey, I don't think I have the source, but the relevant text was quoted on the talk page and IMO it's much too close. Everything between here and here will have to go.

There's a talk discussion as to whether a paraphrase would even be useful; it technically misrepresents the source, as it was apparently lifted from a single paragraph (on the second page of the article, just outside the free preview range) but pretends to cite a 21-page section of the journal.

Hijiri 88 (やや) 19:34, 2 March 2018 (UTC)[reply]

Messaging you again as it seems likely you logged in, saw a new messages notification, and only noticed the most recent one. Hijiri 88 (やや) 00:27, 3 March 2018 (UTC)[reply]
Yeah, saw this. I'll look at it in a bit (probably tomorrow). Been pulled in a bunch of different directions here today, and need now RL stuff calls. TonyBallioni (talk) 00:34, 3 March 2018 (UTC)[reply]

User still refusing to listen

This definitely doesn't look good. The editor appears to think I was just using copyright as a cheap trick to "win" a content dispute, and now that he has "surrendered" is acting as though I am "gloating" at having "won". He seems completely incapable or unwilling to accept that his edits might have actually constituted copyright violation.

I did a bit more sleuthing and the editor's other articles cited to English-language sources seem to be largely copy-vio; like Dream Focus, their edits are mostly gnomish and don't add significant amounts of prose, so searching for those that do is not easy:

  • James Hamilton (1819–1878) is almost entirely copy-vio,
  • as is the text Margin added to Heartwood Forest;
  • Book-to-bill ratio contained some close paraphrasing, but most of it is based on charts and lists that Margin converted to prose, apparently in his own words;
  • his edits to Jōshin'etsu region are an accurate reflection of the content of a sub-optimal Japanese-language blog, but at least there's no plagiarism;
  • Nicola Alexandrovich Benois closely paraphrases two of its online sources here and here, accounting for virtually an entire section of the article;
  • the final sentence of Matsura Takanobu (1592–1637) (the only sourced one) is lifted right out of this book (some of the source's words were pruned, but none added or changed);
  • I couldn't find any copyvio in The Nimmo Brothers, but my eyes glazed over when I looked at the sources, which do not seem to fully verify the content attributed to them, and are all primary sources anyway -- and I can only assume the reason there is no copyvio is that he just translated the de.wiki article, as Google Translate's rendition of that article would be identical to ours with some copy-editing.

Based on the above, I'd say the editor has a Japanese level similar to my own or Curly Turkey's, and when he translates from Japanese sources he seems to do so accurately, but becomes lazy when using English sources. The exception is when he expands content from lists of data into original prose. But the above sample is hardly comprehensive; the editor has almost 8,000 mainspace edits.

Hijiri 88 (やや) 00:02, 4 March 2018 (UTC)[reply]

I'll look at this tomorrow or Monday. TonyBallioni (talk) 00:14, 4 March 2018 (UTC)[reply]
To be clear, I'm not asking for rev-del (yet). I thought it was too much work to figure out exactly which parts needed to go and whether it would be worth keeping properly paraphrased versions anyway, and wouldn't ask you to do that work. It's a user-conduct, WP:IDHT issue, and I'm asking you to talk to him since apparently he wants nothing more to do with me, but he can't be allowed continue to do what he has been. Hijiri 88 (やや) 00:27, 4 March 2018 (UTC)[reply]

Move review

Hi, while closing the discussion on Requested move 22 February 2018, relating the title of general article on anti-Eastern Orthodox sentiment, you decided to rename the article to Persecution of Eastern Orthodox Christians, in spite of fact that during the entire discussion there was no response to questions that were raised regarding the consequent change of scope (reduction to "persecution" only), and also there was no clear consensus on the final style of the title. As it was stated several times during the discussion, similar denominational articles like Anti-Catholicism or Anti-Protestantism have not been subjected to such reduction, since Persecution of Catholics correctly redirects to Anti-Catholicism as a wider concept, and Persecution of Protestants correctly redirects to Anti-Protestantism, also a wider concept. Therefore, applying different criteria to similar denominational article on anti-Eastern Orthodox sentiment would constitute a clear example of double standards. That is also part of a much wider problem, since earlier in February a failed attempt was made to delete the entire article (see: Articles for deletion: Anti-Orthodoxy), not to mention numerous disruptive edits and recent deletions of entire sections. Clearly, there are several important issues regarding this article, and the attempted reduction of its scope is one of them. As it was stated during the discussion, such reduction would be not only unjustified but also quite problematic, since the term "Anti-Eastern Orthodox" has been adopted by the FBI as official designation for negative sentiments and animosities towards Eastern Orthodoxy (see more than 800 hits on Google Search), and that term is commonly used (see more than 1800 hits on Google Search). In light of that, correct title for the article in question would be "Anti-Eastern Orthodox sentiment" and such title would reflect the full scope of its content. Also, such title would be consistent with similar denominational titles, like Anti-Catholicism, Anti-Protestantism and others. So please, would your reconsider the final conclusion? I am dressing you on this subject, because such procedure is indicated on the Wikipedia:Move review page. Sorabino (talk) 21:52, 2 March 2018 (UTC)[reply]

Sorabino, I stand by the close. As you said, there was a clear consensus to move somewhere, and this seemed like the version that was the most consensus version. In terms of change of scope, that can be addressed through talk page discussion and possible splitting of the article, but while I think you had a good point, it doesn't change that there was a consensus to move (NOTAVOTE and whatnot, but one person repeatedly making the same point isn't enough to prevent a move from going forward, even if it is a good point.) Those supporting the move were unconvinced by your arguments, and the previous AfD was also highly supportive of renaming. Anything that needs to be changed because of the scope can be sorted out on the talk page, which is fine and not really part of the RM process. I understand how frustrating and complex religious RMs can be, but I think that this was the best close based on that discussion. I'm fine if you want to take this to a move review. TonyBallioni (talk) 22:06, 2 March 2018 (UTC)[reply]
There is no doubt that some change of title was necessary, but still there are several issues regarding the final conclusion, and the entire discussion process. First, there was not only "one" user who objected the proposed change of title style and reduction of the scope. Second, reduction proposal to "persecution" only was not explained by a single word during the entire discussion, and all questions regarding that question were left unanswered. So, there was no discussion on the subject! Third, proposed change of style was actively supported by some users who only few days ago voted for the deletion of the entire article. Fourth, regarding your proposal to split the article, that is a fine example of unnecessary problems created now by the new title style. Since you mentioned "frustrating and complex religious" issues, and you participate in Wikipedia:WikiProject Catholicism, would you reduce Anti-Catholicism to Persecution of Catholics, and would you split sections on Persecution of Catholics from Anti-Catholicism? Since no-one is creating new problems there, please lets not create such problems regarding the general article on anti-Eastern Orthodox sentiment. Sorabino (talk) 22:38, 2 March 2018 (UTC)[reply]
Sorabino, I read the whole discussion, there were those who objected, but as a whole, the consensus favoured a move to the Persecution title, and there was not a consensus that the issues you raised were enough to prevent that move (and there was at least some willingness to discuss a change of scope.) I think it was strong enough for a moved close, but even if it weren't, per WP:RMCI, the next best close would have been consensus to move, no consensus to title, in which case I would have still moved it to this title per the instructions. If you want to start a new RM proposing a different title to test consensus between the current title and one you favour, I think that would be fine, and likely be quicker than a move review, but I also have no problem if you want a move review. TonyBallioni (talk) 23:04, 2 March 2018 (UTC)[reply]
Yes, there was consensus to move, but no real consensus on the new title. And thank you for reading the entire discussion again. I hope that you noticed the total lack of any response to questions regarding the reasons for proposed reduction of scope to "persecution" only. Even those users who proposed and supported such reduction did not want to state their arguments, in spite of being asked several times. I also hope that you noticed that no-one denied the basic validity of official FBI terminology, that uses the style "anti-Eastern Orthodox". And now, after having no real discussion on those crucial subjects, we have new title that reduces the scope of the article and creates new problems. This is one of those cases when a very important issue, regarding here the general article on negative sentiments towards an entire denomination, is discussed by only a handful of users, during few days, while it is clear that such complex issues require wider participation and longer discussion. That is why I would favor "move review" as a next step, because I think that wider community should take notice of this entire affair regarding the recent attempt to delete this article, in relation to consequent reduction of its scope and deletion of entire sections by the same users who originally tried to kill the article. Sorabino (talk) 23:52, 2 March 2018 (UTC)[reply]
Sorabino, that's fine. Feel free to request one. I get your objections, but having read the discussion three times now, I don't see a different plausible outcome based on the discussion. Like I said, I really do appreciate your frustrations (religious naming questions can be very complex, and they are often the least bad option rather than the best). Anyway, hope I've been somewhat helpful, even if it's not the answer you want. TonyBallioni (talk) 00:36, 3 March 2018 (UTC)[reply]
OK, I initiated the procedure for the move review. Sorabino (talk) 00:08, 4 March 2018 (UTC)[reply]
Got the ping and made a statement there. Thanks for letting me know. All the best, TonyBallioni (talk) 00:13, 4 March 2018 (UTC)[reply]

An editor has asked for a Move review of Persecution of Eastern Orthodox Christians. Because you closed the move discussion for this page, or otherwise were interested in the page, you might want to participate in the move review. Sorabino (talk) 00:08, 4 March 2018 (UTC)[reply]

Cat-holic question

Excuse me. Catholic. This source states that this guy was the "color bearer" for the American Federation of Catholic Societies. I'm inclined to think that's a reference to the figurative use of modern day standard bearer. But, I honestly don't know if that might have some specialized meaning in Catholic theology or social activism. GMGtalk 17:08, 3 March 2018 (UTC)[reply]

Nope. Also don't think it is something I haven't come across as it doesn't appear to be a derivative of any Latin term, which suggests it likely isn't a Church office. TonyBallioni (talk) 17:11, 3 March 2018 (UTC)[reply]

Re: COI advantages at AfC

Hi TonyBallioni, you recently wrote at VPP that I'll save you my rant on the issues that are involved with AfC and COI (tl;dr, it is a system that has structural advantages to being a COI editor rather than a non-COI editor.). This is a topic I'm curious about, since I routinely refer COI editors on IRC to AfC, and I'd love to get your perspective on it. Could you help me understand why AfC is an area COI editors have advantages over non-COI editors in? AfC seems to me to be equally frustrating for COI and non-COI editors to use. (Perhaps you have already explained this somewhere else and could link it for me?) Best, Kevin (aka L235 · t · c) 00:37, 4 March 2018 (UTC)[reply]

Sure, Kevin. So, first off, I'll say how much respect I have for the people who regularly work AfC: it's a tough job and they do a lot of good work. My issues with the process have to do with how the structure tends to advantage COI editors over non-conflicted contributors. It's important to remember that AfC was originally created to let good faith IPs create articles, and later moved to working to help good faith new editors, and now has become the designated place for COI editors to create articles (which is better than them creating it in mainspace, I'll agree in general).
The structural issue here is that the system is designed thinking of the good faith non-conflicted editor, and is designed to help them get articles into Wikipedia: it is supposed to encourage direct interaction between new editors and established editors to help them get articles we want into Wikipedia. The problem arises in how rejections are handled: if you are a new editor who is writing about a notable historical figure who has been convered in academic sourcing and books, and you write an article with crap formatting and offline references, odds are that the article is going to be rejected at AfC and you will be given a template that doesn't apply to your situation, and when you ask for help, you'll be quoted WP:42, and sent on your merry way. You will likely quit because it is absolutely infuriating to have your article on a notable 19th-century mechanical engineer rejected by a 17-year-old Pokémon fan six weeks later because the formatting was a bit wonky, and you don't particularly feel like having a talk page conversation with someone who has no clue about the subject are using a weird markup that you've never user before so you just give up and go back to your other hobby of fly-fishing.
Switch to the COI/PAID/spammer editor. They have a financial or emotional incentive to keep asking questions and getting feedback. They will often latch on to the same reviewer, who typically will give them general answers (see again, WP:42) and they keep coming back with sources until the draft looks much better than it did before, so it gets accepted. NPP likely ignores it because it's been accepted by AfC, so it must be good, and on the off chance it goes to AfD, it is guaranteed at least two keep !votes, one of whom being the no-longer-actually-independent AfC reviewer showing up to defend their accept (but treated independent by the closer. All the while it is actually a native advertising piece with nicely formatted crap sourcing (that AfD didn't go through the back and forth with a reviewer bit, but it's the most recent AfC AfD I was a part of, and I put a lot of work into explaining the issues with that article.)
In terms of what can be done? I'm not sure. I advocate for doing BEFORE when someone asks for help and not giving them general answers, but actually telling them one way or another whether or not the draft has any chance of being part of Wikipedia. Most of the time in COI cases the answer is no, and we're not doing anyone any favours by saying "All you have to do is find more sourcing!" Lest anyone think that I'm entirely opposed to COI editors using AfC, no, I'm not: I brought George Baldanzi to DYK and basically wrote the article entirely myself after the nephew of the subject created it as a one-line stub in AfC. AfC does have a place in the COI process, but the current system is skewed to the benefit of COI editors over non-COI editors. I'm not sure if there is an easily implementable solution other than not leading people along on unacceptable drafts, but I'll raise the issue for general consideration. TonyBallioni (talk) 02:37, 4 March 2018 (UTC)[reply]
Thanks, Tony. I think the phenomenon of Wikipedians becoming jaded after doing something for a while is one of our biggest problems. AfC reviewers start rejecting drafts as quickly as possible on the flimsiest of reasons to reduce the backlog (yes, because the formatting was a bit wonky); IRC helpers say the snippiest policy-compliant non-response response to get the annoying helpee off their plate; NPPers clearly-inappropriately CSD articles because they don't want to spend energy writing up an AfD. I've worked all of those areas in the past, each pretty intensely for at least a month. For me, clerking for ArbCom has been less frustrating than remaining perfectly patient as I explain GNG to the 15th IRC uncooperative COI helpee that day, as I review the 260th AfC with bland sources and terrible formatting, as I provide feedback to the eleventy-millionth editor whose article is probably going to be deleted at AfD no matter what (pre-ACTRIAL).
I recently revisited each of these areas – reviewed a few AfCs, did a bit of NPPing, spent a few days answering #wikipedia-en-help. I wrote personalized, 700-character AfC comments, actually investigated the history of NPP articles instead of doing a cursory review and tag-bomb, and personally edited IRC helpees' userpages to help them declare COIs. I also noticed when others could've been more thorough, more careful, more understanding, less BITEy. But I also recognized that had I done this for another month, there was no way I could've managed to stay as helpful or cheerful as I was in my first AfC/NPP/IRC work in a year.
And that's the broader problem with all of our new editor-facing processes, not just AfC. I mean, we're a thousand experienced uncoordinated volunteers, tops (on any given day, at least), handling the entirety of the public-facing maintenance of a top-5 website. How do we even try to make that more friendly? Most stranger-to-stranger interactions only work because at least one party is getting paid. Think customer support at call centers – you think the staff would stay if they were asked to volunteer? Here, the support staff isn't getting paid – so pretty much the only people who can handle the unpleasant interaction are those who have outside incentives to keep at it.
This is why it frustrates me a bit when content creators on this site look down upon WikiGnomes and maintenance work. I mean, speaking firsthand, writing articles is so, so much more pleasant than painstakingly explaining over 20 minutes to someone on IRC why their non-notable company does not qualify for a Wikipedia article. I get to freely edit six million articles because others keep an eye out for spam and vandalism – why should I then regard them with contempt, as the community seems to do sometimes?
I see that I got on a bit of a soapbox above. I also have little idea what to actually do about any of this. I mean, it's a miracle any of this works in the first place. Perhaps we could encourage people to rotate between different areas of maintenance work to prevent getting quite as jaded and losing the big picture? Best, Kevin (aka L235 · t · c) 04:02, 4 March 2018 (UTC)[reply]
Much of my experience matches with Kevin's and the idea of rotation is quite nice:) I was once heavily active in AFC followed by NPP and other maintenance areas but after a month or so, one definitely starts getting jaded-out.~ Winged BladesGodric 05:29, 4 March 2018 (UTC)[reply]
Whilst I agree with most of your observations, I guess All the while it is actually a native advertising piece with nicely formatted crap sourcing is a bit of over-generalization.AFC manages to screen off a quite mountainesque amount of paid-spam/rubbish, which is written/formatted way-too nicely.
And, I think that these bad accepts are mostly from new AFCReviewers in the sphere of corp-articles/vanity-bios primarily arise from the fact that not many are able to identify independence and reliability of sources, context-wise, when it comes to company-articles.Frankly, the official requirements to be inducted as a AFC reviewer--90 days and 500 edits is too low to properly gauge these issues.I don't think that even if you wind-backwards to your days as a newbie and participate in the AFD, you would have been able to reason as beautifully, as you did at the linked AFD.
One good step to remove the COI-bias at play over AFC, would be to advice all new AFCReviewers to not indulge in reviewing/accepting CORP-articles until they have participated in several CORP-AFDs and can demonstrate that they are capable to gauge the complex-requirements of sourcing in the area.~ Winged BladesGodric 05:29, 4 March 2018 (UTC)[reply]
About to go to bed, will respond to Kevin tomorrow, but wanted to reply to Godric lest I get angry AfC people here in the AM thinking I don’t like them: Yes, AfC does fend off a lot of spam, and I’m very grateful for it. I suppose my point is that if you speak standard North American or British English you can likely ask enough questions to get anything approved, and that favours people with financial or other motives besides just building an encyclopedia. It’s not an individual problem with any particular reviewer, it’s a structural problem. TonyBallioni (talk) 06:05, 4 March 2018 (UTC)[reply]
I'm definitely not angry, esp. given that your post above is probably the most impressionable set of observations about AFC, I've come-across till-date.I will definitely agree on the point of structural flaw but it's general human tendency to help those who ask/pester for it--a thing COI-editors are usually heavily proficient at.
I've at at some point of time started telling off the submitants straightaway that:-- You're putting in your efforts for hopeless cases which may be better directed elsewhere but apparently some people at HelpDesk, TeaHouse etc. (who are all quite-nice folks and I ain't criticizing their view) believe that we still ought to guide them in expending hundreds of edits behind that draft which is never-ever going to get live.Perspective and mileage vary:)~ Winged BladesGodric 06:27, 4 March 2018 (UTC)[reply]

Autopatrol Right - Article I didnt create

H TonyBallioni, I have requested Autopatrol right about 3 months ago - see here [6] - The two articles actually pass the WP:GNG but failed the WP:NMMA. Since then (since July 2017) I have created 55 published articles. The one named శ్రీ వెలుగొండ వేంకటేశ్వర స్వామి (on item 6 on the list) [7] was NOT created by me. I CSD the article and somehow user RHaworth deleting while my edit still open and I didnt notice it and made the edit and for such it appear on my creation log - see the conversation here User talk:RHaworth#శ్రీ వెలుగొండ వేంకటేశ్వర స్వామి. I requested RHaworth to delete it and was told some how it could not. I would like to request for autopatrol and now it will hamper the right since this occur. I DIDNT crate the article, and who like to (1) request the name page to be deleted from my creation log and (2) I would like to request autopatrol and how this would effect me (if I request now at the request site) and I will be surely denied. kindly assist and thanks in advance. CASSIOPEIA(talk) 10:40, 4 March 2018 (UTC)[reply]

Hi, CASSIOPEIA, if you think you meet the requirements for autopatrolled, you should apply at WP:PERM. I haven't reviewed your most recent contributions, and I think it is typically better for a different admin to look at it the second time someone applies for something. TonyBallioni (talk) 01:37, 5 March 2018 (UTC)[reply]

Really?

You're going to arbitration even before reaching out to me on my talk page? Thanks. Much appreciated. Terrific example of how to address disagreements. --В²C 17:51, 6 March 2018 (UTC)[reply]

I'm sorry, but given the above thread on this page and the threads on the other pages, I felt it would likely have just generated more heat than light. TonyBallioni (talk) 17:54, 6 March 2018 (UTC)[reply]