This is anarchive of past discussions withUser:Xaosflux.Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on thecurrent talk page.
Blank single-author pages
Hi. You asked a while back at DBR about a better version ofWikipedia:Database reports/Blank single-author pages. If it's any help, I've replicated the query with a bigger limit atQuarry. It needs some tidying up - you will have to download the results and manually translate the namespace number to actual namespace using the table at the top ofWikipedia:Namespace, so "1 AltiGator" needs to becomeTalk:AltiGator and so on, and the handling of Unicode characters needs some attention, but apart from that it should be good enough for your purposes. Cheers.Le Deluge (talk)15:55, 15 April 2016 (UTC)
In the "Talk" part of your signature, could I interest you in #4c924c instead of #00ff00 . The colour hurts my eyes (it's trivial but wouldn't hurt to ask, would it). --QEDK(T ☕C)16:45, 18 April 2016 (UTC)
The discussion around the rights to be bundled in Page mover has set me thinking.move-subpages would seem to be of most use in relation to templates which, in the cases which require TE attention, usually come with the set of /sandbox, /testcases, and /doc. Should the priv be added to the TE set? Can't say that I've come across a situation in the 9 months I've been servicing requests atTPERTable, but it seems a logical step to ensure that TEs would be able to service the full set of requests. Your thoughts please?Bazj (talk)19:01, 21 April 2016 (UTC)
@Bazj: I don't specifically object to this, but don't think it is that needed. The place it is the most needed is talk pages, which may have tons of archives. Most templates that are TE protected are fairly "stable" - and not often renamed (moved). If someone was involved in moving template around a lot, then they certainly could qualify for the proposed page-mover as well. —xaosfluxTalk21:15, 21 April 2016 (UTC)
I am sure your closes are right, but looking at a couple:
Wikipedia:Miscellany for deletion/User:Shiva eng2002/Veeramani.K "Non-notable musician with no references". These are so common and so obvious, it should be a speedy criterion? Little issue with a SNOW delete, except maybe for a SNOW on the first day on the basis on the nomination statement, maybe in your close you should assert that the nom is right?
Hi@SmokeyJoe: Unless you want to really contest these, I'm not going back to them (in which case I'll revert and let them run) - but will try to put more context in to future snow closes. If I'm closing per snow it is not strictly a CSD criteria, but those that I think really have no chance at MfD (regardless of the nominators statement). We've had a huge backlog at MfD lately and I'm trying to get it under control. I do look at every page I delete prior to deleting and am a huge advocate of merging histories to ensure even the smallest oldest attributions are maintained. I think we still have a project wide gap on what should and what should not be allowed in non-article space, including all the variants of sandboxes and drafts that are "core content" related; I can see the POV's of the people that say who cares-put anything and the "this better become an article very soon" camps - but the overall community consensus is still very gray. Sorry to ramble on and on here - let me know if you want to actually object to any speedy I make, I will almost always revert unless it is obvious disruption (attack pages/blatant copyvio/etc). —xaosfluxTalk03:59, 2 May 2016 (UTC)
Hi Xaosflux. No, no intention to contest, but just a little more context would be great. Thanks for working on the horrendous backlog. --SmokeyJoe (talk)04:04, 2 May 2016 (UTC)
(talk page stalker)@SmokeyJoe: (and also directed at Xaosflux) What would your thoughts be on proposing a couple obvious speedy deletion criteria to help limit the needed nominations? I've admittedly been one of the worst offenders in contributing to the backlog because I've been trying to weed out some of the incredibly obvious spam from the draft/user space. There's probably a few categories that could be made into speedy deletion criteria for the draftspace (not userspace) with no major objection. The one that comes to mind immediately is "Biographies of living persons where the primary subject is a minor (less than eighteen years of age) or group of minors and no reliable sources are provided." ~RobTalk08:24, 2 May 2016 (UTC)
I have long noted a missing BLP CSD. BLP deletions are longstanding practice, but undocumented. I suggest "Unsourced private information on a child or private individual, or any unsourced negative material on any living person." Pages consisting predominantly of this should be deleted. Small amounts in an otherwise acceptable page should be removed per WP:BLP. Use ofWikipedia:Revision deletion may be appropriate. I think this would cover BU Rob13's desire.
New CSD criteria need to be well drafted to get a serious hearing.
In regards to a new CSD, I don't think the age of the subject should be a primary factor; GNG is too rigorous for drafting, but perhaps a DNG where there should be some assertions that the GNG will ever be reachable should be required within some timeline of starting the draft. —xaosfluxTalk11:26, 2 May 2016 (UTC)
I don't think my page is the best place to come up with an answer, but personally I thinkWP:DRAFTPROD should be revived, but tweaked, perhaps a longer wait period (a month?) and be inclusive of any encyclopedic content that is being drafted (not necessarily only the draft namespace, but also user subpages exclusive of generic sandboxes -- which can easily be reset). —xaosfluxTalk11:26, 2 May 2016 (UTC)
I'll let y'all decide whether to bring this up. Last time I made a policy proposal, I was personally attacked, so I'm not too keen to repeat that. You guys have more experience in this area than I do as well. Drop me a talk page message if you propose any draft CSD criteria. ~RobTalk02:51, 3 May 2016 (UTC)
Why can't I find your rights log where you were granted sysop and more....
@QEDK: They are hidden away, just kidding they areright here, but not easily retrieved due to a bug (they were issued using the old interface that allowed inputting a lowercase letter for the first character and executing the change). Thanks for the nod, I've thought about it, but the needs for crats is pretty low still - I was about to "run" for oversight last time, but a personal commitment was keeping me off line for a bit - will probably throw my hat in to that one if it comes around again. —xaosfluxTalk19:32, 2 May 2016 (UTC)
Seriously, why aren't you a crat yet? You've been around for so long, you are one of our most active behind the scenes admin and someone who knows all the policies inside out. You already oversee the BAG and regularly provide valuable input at BN. Yours would be a much welcome addition to the bureaucrat group. -NQ(talk)19:38, 2 May 2016 (UTC)
Ofc he would be and I'm pretty sure he'd sail through RfB too. Iinsist that you run for crat, considering you're one of our long-standing and valuable admins of the community. --QEDK(T☕C)11:50, 3 May 2016 (UTC)
I was curious, so I searched the system and I could only ever find one appeal (UTRS appeal #13364) that was related to one of your blocks. It appears that very few users find your blocks arguable.--v/r -TP01:42, 6 May 2016 (UTC)
Hi. My point is never to make work for other editors. So, in the future, if I come upon a stale draft which was incorrectly created on the main sandbox of a user, should I simply blank and put the sandbox template on the page (as you did)? Or should I still G13 it, and let an admin do it? Thanks.Onel5969TT me12:51, 8 May 2016 (UTC)
@Onel5969: There was nothing "wrong" with what you did, and these are very much a case-by-case type of call. Basically when these are contested they end up at MFD and normally then unless there is a good argument (like copyright violation, attack page, serious blp concerns, etc) the trend is thatUser:User/Sandbox type pages are normally just blanked, whileUser:User/SomeArticleSoundingName get more discussion as to redirecting/mergering/moving to draft/etc. I've found the best way to deal with other people's primary sandboxes is normally to just ignore them, however if they are in categories/using non-free images then{{usersandbox}} or{{Inactive userpage blanked}} can easily be applied. I tend to use the later if there was significant content of only one subject. Hope this answers your questions, please let me know if I missed anything. —xaosfluxTalk13:23, 8 May 2016 (UTC)
Hi, and thanks for the response. I'll keep those parameters in mind. However, I guess I was asking regarding the specific instance at G13. As I said, my goal isnever to create more work for other editors, so if I can do something differently which makes it unnecessary for another editor to get involved, I'm more than willing to do it. With that in mind, if I come across a sandbox at G13 is it appropriate for me to do an editlike this? Or should I G13 it? Thanks again.Onel5969TT me14:00, 8 May 2016 (UTC)
I think blanking it like that is the most appropriate in that case, had it beenUser:Pankaj1989007/Institute of Aeronautical engineering though I'd go the G13 route - the only difference being a page title - but the MfD trend leans in that direction. There is still much discussion going on regarding "draft" type cleanups in the various forums. If you do go the G13 route, I'd leave the user who's page you nominated a note as well on their main talk so that if they come back they know what went on - this is also subjective but is more useful if the editor is recent (say last edit within the year) and "younger" (say this was their only edit, or they had very few edits) - so as not to confuse them (newer editors can get lost looking at log messages). Please note, this is not "official policy", just my experience as a long time admin. —xaosfluxTalk16:18, 8 May 2016 (UTC)
Please help me. You deleted a page I've been working on for months. Called "Redefy Real Estate". This is my first attempt at a Wiki and I had submitted it several times, each time working on the things that needed to be improved. I went back to add more references because it needed more to be notable. I was surprised to find it deleted. Please, please, is there a way to get the code back? I really am working to get this published and I don't want to start over. Please respond! Thank you.— Precedingunsigned comment added bySRoberts1988 (talk •contribs) 20:31, 13 May 2016 (UTC) Oh sorry, I didn't see your reply below. I sent you my email address. Thank you!SRoberts1988 (talk)20:38, 13 May 2016 (UTC)
I will happily email you a copy of the article if you want to develop it outside of wikipedia for a future try - if you want this use the Email this user link to the left so I can get your email address, then leave a note here. —xaosfluxTalk22:58, 13 May 2016 (UTC)
Extended confirmed protection prevents edits from all IP editors and any registered user with fewer than 30 days tenure and 500 edits. This level of protection is to be applied in topic areas authorized by theArbitration Committee or the community.[1] Pages with this level of protection can be edited only by editors with theextended confirmed user access level, granted automatically to editors with 30 days tenure and 500 edits.
Currently this level is used onGamergate controversy, and the related talk pages,[2] as well asBrianna Wu[3] andAnita Sarkeesian.[4] It may be used on any article that can be reasonably construed as belonging to the Arab–Israeli conflict[5] and is used on several caste-related articles.[6] When used as an arbitration discretionary sanction, this level may only be applied in response to persistent sockpuppetry or continued use of new, disruptive accounts where other methods (such as semi protection) have not controlled the disruption.[7]
ArbCom isn't making claim to owning this "protection level" , but does allow for it to be used as a remedy. Some points for use outside of remedies are that it must have a community consensus developemed, and must only be used after other methods have failed. —xaosfluxTalk20:23, 15 May 2016 (UTC)
I removed the last sentence (as redundant), but that looks good to me otherwise. Thanks for doing the mock-up.Kevin (akaL235·t·c)20:33, 15 May 2016 (UTC)
@L235: - you don't think the new expectation are appropriate? There has been some back and for on other pages about how this can/can not be used (outside of arb remedies) and having the policy only say "or the community" is very broad. —xaosfluxTalk20:50, 15 May 2016 (UTC)
Outside of arbitration decisions, it is expected that extended confirmed protection may only be applied in response to persistent sockpuppetry or continued use of new, disruptive accounts where other methods (such as semi protection) have not controlled the disruption.<ref>[[Special:PermaLink/720421803#Arbitration_motions_regarding_extended_confirmed_protection]]
Hmm, I haven't actually seen those other discussions; do they establish a consensus for using this level outside of arb-authorized conditions? The community is certainly free to develop its own policy, but so far as I am aware, the community has only authorized use where ArbCom authorizes.Kevin (akaL235·t·c)20:53, 15 May 2016 (UTC)
The RfC closure to create the protection level allows for use by armcom "or the community" - I'm reading this new arbcom motion to layout the "expectation" for use outside of arbcom - this would still be coupled with the requirement that the use is allowed by the community - a very loose topic. What did you read that as meaning? —xaosfluxTalk21:58, 15 May 2016 (UTC)
Hmm, particularly with Kelapstick's comment thatNote that this is, in my mind, only applicable to the use of 30/500 when used as a Discretionary Sanction/Arbitration Enforcement. Should the community decide to extend the use of this protections use beyond DS/AE (and amend the protection policy), that is outside our remit. In other words, the committee does not own this protection level on the whole, but we can determine how it is used to for DS/AE. If that makes sense., I view that as the only time it may be appliedas a discretionary sanction; ArbCom is not authorizing admins to use it outside of arbitration enforcement. (I think.)Kevin (akaL235·t·c)23:07, 15 May 2016 (UTC)
ArbCom doesn't have the authority to authorize or not admins to use software features (such as a protection level), because ArbCom does not make policy (the community does).☺ · Salvidrim! · ✉23:14, 15 May 2016 (UTC)
Hello. I was about to post a new section on the articleWalling and noticed the talk page was empty and had the following;
A page with this title has previously been deleted.
If you are creating a new page with different content, please continue. If you are recreating a page similar to the previously deleted page, or are unsure, please first contact the deleting administrator using the information provided below.
23:56, 28 November 2015 Xaosflux (talk | contribs) deleted page Talk:Walling (G6: Housekeeping and routine (non-controversial) cleanup)
As far as I was aware talk pages were for discussion, and are not to be cleaned up or deleted? In fact I read that they are not to even be archived if it is potentially controversial or if someone objects. May I ask why you deleted the talk page and what it's content was before deletion?
I do not think with all of the server space available to Wikipedia as a whole that we are running out of room any time soon and would submit to you that any form of cleaning up--besides speedy deletions, nonsensical content, duplicate content, or spam et cetera--is not only a waste of everyone's time but could be presumed to have sinister intent especially by the kinds of conspiretards we all run into on here!
You might want to reconsider that in future, ESPECIALLY on a subject like human torture. Because while I'M thinking "I wonder what was on the page before he deleted it?" you know THEY will be thinking "I bet the CIA were exposed and Wikipedia is in on it." and then they'll spend the next six years on a rampage defacing stuff about how they have proof that we're all illuminati agents because Xaosflux deleted a talk page. :P Out of fear of association in the eyes of said conspiretards I'm now too scared to restart the talk page, but thought I'd mention it to you because it is poor form (not just because of the kooks we deal with day to day) to employ any form of censorship and unnecessary deletion of information could readily be categorized as that intrinsically. <!//– ☠ ʇdɯ0ɹd ɥsɐq ☠ //user //talk //twitter //–>09:37, 17 May 2016 (UTC)
Hi. You recently deleted some talk pages and a template directed me to contact you. Just wondering what's up and if there are any issues with creating new talk pages.Reidgreg (talk)20:06, 23 May 2016 (UTC)
(Deletion log); 11:00 23 May 2016 . . Xaosflux deleted pageTalk:Last Day on Earth (The Walking Dead) ((G7: One author who has requested deletion or blanked the page) (TW))
(Deletion log); 11:00 23 May 2016 . . Xaosflux deleted pageTalk:Not Tomorrow Yet ((G7: One author who has requested deletion or blanked the page) (TW))
(Deletion log); 11:00 23 May 2016 . . Xaosflux deleted pageTalk:Twice as Far ((G7: One author who has requested deletion or blanked the page) (TW))
(Deletion log); 11:00 23 May 2016 . . Xaosflux deleted pageTalk:East (The Walking Dead) ((G7: One author who has requested deletion or blanked the page) (TW))
okay, for example, in that thread someone linked to "Special:blockedlist" which has all current blocks...this is a page/function that must not have existed at some point in time and was then created...how was it created and by who? thanks.68.48.241.158 (talk)16:00, 29 May 2016 (UTC)
@Music1201: I don't think it is a bug,Wikipedia:Moving_a_page#Moving_over_a_redirect has a proviso "If the new title already exists but is just a redirectto the old title" - but it appears you are trying to do multi-page moves. As this doesn't appear urgent you can either let a pagemover take care of it, or tag it for speedy deletion. If you think you are running in to a bug against the directions, please try to recreate it (use multiple of your own sandboxes) and we can get a trouble ticket open. —xaosfluxTalk02:04, 1 June 2016 (UTC)
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Recent changes
MathML/SVG is now the default<math> rendering mode on Wikimedia projects.[1][2]
Changes this week
The history page can tell you if a page on your watchlist was updated since you last visited it. This now works the same way inVector as in otherskins. The change broke local designs on some wikis. This will be fixed this week.[3]
Thenew version of MediaWiki will be on test wikis and MediaWiki.org from 7 June. It will be on non-Wikipedia wikis and some Wikipedias from 8 June. It will be on all wikis from 9 June (calendar).
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.
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.
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Recent changes
Wikimedia wikis now useAuthManager. If you have new problems related to logging in or being logged in,report them.[4]
VisitingSpecial:Notifications doesn't automatically mark notifications as read anymore. You can go between read, unread or all notifications onSpecial:Notifications. Notifications onSpecial:Notifications are grouped by day. You can mark every daily group as read individually. Notifications are displayed by groups of 50 onSpecial:Notifications and you can find former notifications by using navigation arrows.[5][6][7][8]
Changes this week
You can filter user contributions to hide minor edits.[9]
It will be easier to edit galleries with the visual editor.[10]
Thenew version of MediaWiki will be on test wikis and MediaWiki.org from 14 June. It will be on non-Wikipedia wikis and some Wikipedias from 15 June. It will be on all wikis from 16 June (calendar).
Blog:Why I proofread poetry at Wikisource Poetry: “it is the stuff of the soul; it speaks to the body, the mind, and the spirit alike.” Sonja Bohm worked for years to get all of Florence Earle Coates’ poetry online, and now proofreads poetry on the English Wikisource, the free library. We asked why.
Almost 186,000 for every template in that category combined (minus the couple I've already done or am doing manually because I'm combining this with other cleanup tasks that must be semi-auto). The actual edits would be significantly lower. For instance,{{Infobox basketball biography}} has 11,731 transclusions but pre-parse brings the number of edits down to just 550. If a similar percentage applies to other templates, we could expect under 10,000 edits. It could be higher, though, since the editors in the basketball topic area tend to be fairly diligent with using endashes. ~RobTalk23:27, 19 June 2016 (UTC)
@BU Rob13: I think we'd invite community discussion for a bit longer then normal due to the run size, but if there is support I don't see a problem with the scope being large. The biggest opposition is likely that this isprimarily a cosmetic change (from the point of view of readers). —xaosfluxTalk04:08, 20 June 2016 (UTC)
Yes, this kind of straddles the line of what is cosmetic, but hyphens and endashes are intended for grammatically different purposes on computers. Other than just a stylistic and grammatical concern, using hyphens to denote date ranges can cause issues with machine readability. ~RobTalk07:44, 20 June 2016 (UTC)
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Recent changes
Notifications were not always marked as read when you followed a link from an email notification. This will now happen.[11]
Changes this week
The list of other languages an article is available in will be shorter on small Wikipedias and non-Wikipedia projects. This is to make it easier to find the most relevant languages for each user. You will still be able to see the other languages.[12][13]
Alerts (the red badge) will not be automatically marked as read when you open the Notifications popup.[14]
When you get several thanks you can see them as one notification. This is instead of one notification for each thanks.[15]
Thenew version of MediaWiki will be on test wikis and MediaWiki.org from 21 June. It will be on non-Wikipedia wikis and some Wikipedias from 22 June. It will be on all wikis from 23 June (calendar).
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Recent changes
TheORES service has now moved toa new location. This should make it easier to use ORES. TheORES review service is now available as a beta feature on Wikidata and Persian Wikipedia. ORES is an artificial intelligence system for Wikimedia wikis to help editors.[16]
The order of wikis in collapsed cross-wiki notifications was different than when the list was expanded. This is now fixed.[17]
Thenew version of MediaWiki will be on test wikis and MediaWiki.org from 28 June. It will be on non-Wikipedia wikis and some Wikipedias from 29 June. It will be on all wikis from 30 June (calendar).
The way to mark notifications as read or unread will be changed to be more clear.[21]
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on28 June at 19:00 (UTC). Seehow to join.
Future changes
The Collaboration team at the Wikimedia Foundation will look at developing better tools for edit review. This is because research suggests we scare away newcomers who want to help.[22]
An e-mail from the Editing Department explains the technical work that is planned and being researched for the future. Items include better wikitext and visual editing, prompts for edits, language improvements, annotations, and meta-data separation.[23]
The sorting of Notifications into the two fly-out menus is going to change on July 5 to 7. Bundled notifications should be easier to explore and mark as read individually.[24][25][26]
From 29 June git.wikimedia.org (running Gitblit) will redirect all requests to Phabricator. The vast majority of requests should be correctly redirected.[27]
Catalan and Polish Wikipedias will have Wikidata descriptions added to articles in the mobile view by default. This is currently a beta option for the mobile versions. This might come to other wikis later.[28]
Note: All columns in this table are sortable, allowing you to rearrange the table so the articles most interesting to you are shown at the top. All images have mouse-over popups with more information. For more information about the columns and categories, pleaseconsult the documentation and please get in touch onSuggestBot's talk page with any questions you might have.
SuggestBot picks articles in a number of ways based on other articles you've edited, including straight text similarity, following wikilinks, and matching your editing patterns against those of other Wikipedians. It tries to recommend only articles that other Wikipedians have marked as needing work. We appreciate that you have signed up to receive suggestions regularly; your contributions make Wikipedia better — thanks for helping!
Latesttech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you.Translations are available.
Recent changes
A daily email summary of notifications could be sent even when there were no notifications from the wiki. Now no email will be sent if there is no activity.[29]
Changes this week
The "⧼citoid-citefromidtool-title⧽" button in the visual editor's toolbar will move into the "Insert" menu except for Wikipedias, Wikibookses and Wikiversities. This is to make it less prominent on wikis that don't use it as much.[30]
Thenew version of MediaWiki will be on test wikis and MediaWiki.org from 5 July. It will be on non-Wikipedia wikis and some Wikipedias from 6 July. It will be on all wikis from 7 July (calendar).
Meetings
You can take part in the next office hour for Wikidata on IRC on July 8 at 16:00 (UTC). Seehow to join.
One of your answers has a sentence commencing "I occasionally processing requests ..." You may wish to tweak it. All the best:RichFarmbrough,18:56, 5 July 2016 (UTC).
Hello, Xaosflux. Please check your email; you've got mail! Message added 19:48, 2 July 2016 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You canremove this notice at any time by removing the{{You've got mail}} or{{ygm}} template.
I think I've encountered your name at literally every backlog I've run into today. Closing MfD discussions, approving bot trials, handling full protection edit requests, etc. etc. etc., you're managing to do it all. Thanks! ~RobTalk03:49, 1 May 2016 (UTC)