User talk:WikiWikiWayne/Archive 13

AN/I
I have been forced to raise concerns about your conduct at AN/I. Please see Administrators' noticeboard/Incidents. Josh Milburn (talk) 09:36, 15 June 2016 (UTC)


 * I've left some thoughts over on the ANI thread. While I have refused to block you, I do think some of the communication at your end has been a little blunt and confusing. Supplying sources and understanding citation templates is one of the most taxing things a newcomer can face, and it can sometimes mean the difference between having a new article on the main page under WP:DYK or WP:ITN and being speedy deleted. And even experienced editors can struggle with the variations in style and formatting that are acceptable. In particular, I would say a key problem with your communication is you use acronyms without explaining what they mean. Throwing references to read WP:CITEVAR isn't really helpful, as it (correctly in my view) doesn't take sides on what templates to use. I'm personally a sfn man myself, but if I'm working on an article where harvnb or even bare text citations are established, then I'll just work with what's there. It really doesn't matter in the grand scheme of things, and in my view it is far more important to have an easily-readable article that is factually accurate than any green blob or brown star that might appear in the top right hand corner. Ritchie333 (talk) (cont)  10:09, 15 June 2016 (UTC)
 * Hi, . Thank you for your note here. is a long time talented and experienced editor. He knows a lot about citations; more than most. WP:CITEVAR was cited by Josh many times to me so I did not feel a need to explain it when I later used it. Without taking sides WP:CITEVAR guides us to maintain the status quo, to implement consistency, and to improve cites. Templates are the preponderance in Alasdair Cochrane's textbook article and in the Bibiliography templates were 21:1. WP:CITEVAR guides us that once templates are used we should invoke them and not to remove them. Josh is shooting for a gold blob for the article about Cochrane's textbook and I am happy to help in the promotion to that end. Cheers!   00:30, 16 June 2016 (UTC)


 * I have reverted your edits at the article concerned. WP:CITEVAR does not say what you think it says. If you wish to make changes to the citation style on the article, you need to gain consensus on the article talkpage to do so. BRD applies here. Only in death does duty end (talk) 10:48, 15 June 2016 (UTC)
 * Hi, . Please do expand on that. I am all ears. Cheers!  02:31, 16 June 2016 (UTC)

Books & Bytes - Issue 17
 The Wikipedia Library Books & Bytes

Issue 17, April-May 2016 by The Interior, Ocaasi, UY Scuti, Sadads, and Nikkimaria

 Read the full newsletter The Interior via MediaWiki message delivery (talk) 02:36, 16 June 2016 (UTC)
 * New donations this month - a German-language legal resource
 * Wikipedia referals to academic citations - news from CrossRef and WikiCite2016
 * New library stats, WikiCon news, a bot to reveal Open Access versions of citations, and more!

Kidnapping of Jaycee Dugard GOCE Copy Edit
Hello Checkingfax:

The copy edit of the article Kidnapping of Jaycee Dugard has been completed.

I'm assuming that as part of the FA process you will be archiving all of the URLs to avoid future dead links? I assume you know how to do this, but if not, let me know and I'll provide the details.

Please let me know if you have any questions or concerns.

Kind regards,

Twofingered Typist (talk) 14:33, 11 June 2016 (UTC)


 * Hi, . Thank you so much. Editor is wrapping up the GA review. I have probably hacked up a bit of your fine work so feel free to dress it up if you so feel inclined.


 * I do know how to archive URLs the hard way. I am going to see if doing it via Checklinks would be easier. I does not automate the process but it does have an interface with frames where each link could be done and then batch merged.


 * There is a bot that does this but I do not think it takes individual requests. Plus a bot can detect a live link but it may have the wrong content. Many times older pages redirect to the home page of the content source. Hit me back with some pointers of your workflow for doing this. I have checked all links on Dugard's kidnapping article to be live and germane except for one dead link that there is no archive version of. Cheers!  01:29, 16 June 2016 (UTC)


 * I'm afraid there is only the "hard" way to archive URLs as far as I know. WP does have a bot that archives URLs and notes the link on the article's Talk page requesting that a reader verify that the archiving worked. I can't remember its name, and it does appear to be random as it doesn't archive every link in a specific article. I'm afraid it's cut and paste - boring but effective. Regards. Twofingered Typist (talk) 12:03, 16 June 2016 (UTC)
 * Hi, . Thank you for your reply. That bot is owned by an editor named something like Cyberpower678. The bot is one of a few that he has and I believe the one that performs the dead link archiving attempt is something like Cyberbot II. It only attempts to archive links that are marked as dead links. In a way it is cool because you can tag dead links with Checklinks in a jiffy then wait a day for his bot to find and archive them for you. I did it with one page that had 222 dead links out of 500 total links. There was no way I was going to try to manually archive 222 dead links. Checklinks as mentioned does make archiving links a bit easier and it integrates them with only a bit of cleanup needed. I want the developer to improve Checklinks so the manual cleanup is not necessary but he is broke and busy with other projects. Hopefully he will attend to this and I can be his Alpha tester to get it smoothed out. There is a bot that archives all the links on a page but I do not know which one. The problem with bots is they cannot verify the content of a live page. Now and then the live content is useless. That is where your idea to archive a known good page is a great protocol. When you archive the "hard way" what is your most efficient workflow? Cheers!   18:05, 16 June 2016 (UTC)
 * As you point out, one way or another you're going to have to verify the content - bot or not - so the "hard way" (as in not automated) - would be archiving the URLs as you write the citation in the article. In the end, it is unlikely to take any more time than the other options you've mentioned. I read through the current version of the article and made a few minor tweaks. Regards. Twofingered Typist (talk) 19:58, 16 June 2016 (UTC)
 * Hi, . Good job. Thank you. Just so you know, you added some colons this time and you added some previously. Your previous ones were removed by an intermediate editor. They might remove them again Cheers!   21:12, 16 June 2016 (UTC)

Draft:Shai Baitel
Hello, can you please help? my article was declined twice and i do not understand why! there are so many cites and sources and all in reliable ones.. please help! Theboxny (talk) 08:42, 19 June 2016 (UTC)

Cary Grant
Per BRD the onus is on you to go to the talk page, not edit war because you don't like something. - SchroCat (talk) 08:43, 19 June 2016 (UTC)

Welcome to the Hall of Fame!
--Rosiestep (talk) 09:01, 23 June 2016 (UTC) via MassMessage (To subscribe, Women in Red/Invite list. Unsubscribe, Women in Red/Opt-out list)

Your copyediting style
Hi again Checkingfax,

I feel the need to comment on your copyediting style. You've made these large formatting edits to a few of my pages, most recently yesterday to the Briarcliff Manor Public Library article. However, I end up reverting many of the changes. For one thing, it's very difficult and time-consuming to pick through such a large edit, and it makes it harder to undo any one change. As well, I would recommend you take into habit to not add any line breaks (not press enter) until you make a subsequent edit. This is because the diff system is flawed; any line break shows the entire paragraph moved, and won't show any changes to that paragraph, meaning I have to scan through the whole text for changes, or use a diff viewer hosted somewhere online. Moving images as well makes it look like entire paragraphs were deleted or moved.

As well, I feel your edits have little consideration for the formatting style a particular editor retains. All of the articles I write will maintain the same formatting, including little details like no unnecessary spaces in any ref tag. Please consider the style of the contributing editor(s) before making such changes; they don't even affect the display of the article. My style omits any unnecessary formatting, including line breaks.

I'm also not sure where you obtained the thought that the inflation template utilizes original research. It's a simple formulation, that any amount of money in a historical date can be multiplied by the factor of inflation, to provide the current equivalent dollar amount.

Your reply would be most appreciated. Yours, ɱ  (talk) · vbm  · coi) 15:49, 23 June 2016 (UTC)


 * I find it quite confusing that after nearly 15k edits and being here since 2011 that you would, in all seriousness say, "...my pages" and "the formatting style a particular editor retains". Surely, you know that editors do not WP:OWN articles and cannot claim them as their pages or that the style of a specific editor must be retained at any article simply because said individual has edited it?  Wikipedia articles are meant to be edited by more than one editor and cooperatively so.  Your comments here seem to indicate you think because you have edited the article you mention above that you have a right to declare personal consensus as to how they should be edited.  You realize that is in conflict with policy on article ownership as well as consensus, correct?  One quick note/question: How does one ping you?  Your signature and username are most confusing appear to be "un-pingable".  -- WV ● ✉ ✓  16:52, 23 June 2016 (UTC)


 * Hi, (with cc to ). Using the inflation template for most large numbers is original research. See:
 * I will go modify that one example that is contrary to the ombox above. Cheers!  17:21, 23 June 2016 (UTC) reping    17:24, 23 June 2016 (UTC)
 * Hi, again (with cc to ). Changing the   to   in the custom signature code in your Preferences would salve some of the vexing caused to other editors in their ping attempts to you. Your username is "Ɱ" but you are displaying it as "ɱ" and "ɱ" is an unregistered username. Easy fix. Cheers!   17:46, 23 June 2016 (UTC)
 * Hi, again (with cc to ). Changing the   to   in the custom signature code in your Preferences would salve some of the vexing caused to other editors in their ping attempts to you. Your username is "Ɱ" but you are displaying it as "ɱ" and "ɱ" is an unregistered username. Easy fix. Cheers!   17:46, 23 June 2016 (UTC)


 * You're reading far too deep into my writing. Of course I'm very, very familiar with OWN and have probably read it front-to-back innumerous times. However when one editor is the primary contributor for a page, it's common courtesy to let their formatting apply, if there's no policy or guideline contrary to that formatting, and especially after it reaches GA or FA. As for your other note, you can copy and paste my username, which is located in my signature, to ping me.


 * "You're reading far too deep into my writing" I don't think I am.  You referred twice to the article(s) in a possessive manner.
 * "when one editor is the primary contributor for a page, it's common courtesy to let their formatting apply" Where do you find a policy or guideline regarding such a courtesy, since it is - as you claim - so common?
 * It occurs to me that this discussion should be taking place on the article talk page(s) in question so others who have the article(s) on their watchlist can also comment. In fact, I'm thinking this should be brought up in the form of an RfC in order to reach a real consensus rather than relying on assumption(s) made by editors as to what it appropriate editing style-wise at the article(s) in question.  Any consensus, of course, should go hand-in-hand with policy.  More eyes on this would be a good thing.
 * -- WV ● ✉ ✓ 18:03, 23 June 2016 (UTC)
 * Yes you are, I know you are, I've read OWN back-to-front a ton. Just because I occasionally use words like "my" as it's clear to the reader that I'm talking about articles I steward, or primarily edit, doesn't mean I'm saying I own them. Really, get off my back, this is silly. Also, common courtesy isn't usually backed up by rules, I'm just saying it'd be the nice thing for Checkingfax to do. Regardless, the policy WP:STEWARDSHIP supports that editors shouldn't usually make large edits to FAs or GAs without some discussion. ɱ  (talk) · vbm  · coi) 18:14, 23 June 2016 (UTC)
 * You can believe (or say you believe) I am reading into what you wrote all you like. That still doesn't make it so.  The wording you used was evidence of the ownership you feel you possess.  Further, if you had read all of WP:STEWARDSHIP, you would have seen that the following, "...unless an editor exhibits behaviour associated with ownership, it's best to assume good faith on their part" disqualifies you from claiming stewardship considering your choice to use "my pages".  Nothing we do here is ours, it's the property of the Wikimedia Foundation, we are just guests who are allowed to edit.  Any further discussion on the article(s) in question should be taken to the article talk page(s) for transparency.  Wouldn't you agree, ?  -- WV ● ✉ ✓  18:26, 23 June 2016 (UTC)
 * You're being rude now. I informed you I have no ownership, and used the term you and many others dislike out of carelessness; I usually avoid it because people who read into how someone talks trying to criminalize them will often weaponize that term against people. As I said, I was merely trying to clarify that I was talking about articles I primarily wrote or steward. Stop accusing me, I told you I don't have any belief they're my works or that I own them. How many times do I have to repeat this, and how could I convince you more than such a plain statement? Look at my edit history, how policy-based I am or how many significant works I've been involved in. I'm not some territorial hack. ɱ  (talk) · vbm  · coi) 18:38, 23 June 2016 (UTC)
 * Since you are not feeling territorial about the article(s) in question, then it would stand to reason you won't mind an RfC being started on this issue and consensus being sought (that may differ with your perceived consensus). Correct?  -- WV ● ✉ ✓  18:45, 23 June 2016 (UTC)
 * I do mind somewhat, solely as a waste of time, as I'm very busy in real life with two jobs and many weekend events constantly. What do you even want to RfC on? The amount of control a steward of an article has over details like formatting or the informal use of the phrase "my articles" for clarification purposes alone being not allowed? If it's the former, I'll gladly contribute, but if it's the latter it's silly and basically a witch hunt, trying to accuse editors of crimes that haven't been committed. ɱ  (talk) · vbm  · coi) 19:02, 23 June 2016 (UTC)


 * My original username was User:ɱ, however Wikipedia now recognizes that as a lower-case form of Ɱ (which it sort-of isn't), and thus to preserve the original and preferred form, I had to alter my signature and userpage. I could alter the display of my userpage title to ɱ until very recently. It's too bad, I don't see why these technical restrictions are there. Nobody else has expressed difficulty, perhaps if others do I'll make the change. I believe copying and pasting to be pretty simple and straightforward. ɱ  (talk) · vbm  · coi) 17:55, 23 June 2016 (UTC)
 * Hi, . This is what a front facing copy/paste of your username results in: . Only a copy/paste of the source code version will result in this:  . The former is not a registered username. The latter is also hard to grok even with an electron microscope. Cheers!   18:05, 23 June 2016 (UTC)
 * I meant to say that you can copy and paste from the signature as seen in the edit screen, which you should be at anyway when pinging. The uppercase form may appear as a single box to you if the browser doesn't support the character, another unfortunate aspect of the symbol, and another reason I wish I could resume using the "lowercase" version. ɱ  (talk) · vbm  · coi) 18:14, 23 June 2016 (UTC)
 * Hi, . The lowercase Latin M with hook renders fine for me. It is just useless though with your styling because it is muddied, and it is hard to grok in the first place as it is a crowded font that folds under itself with little whitespace for the hook on the lowercase version.


 * Wikimedia does not allow usernames that start with lowercase. Period. You skated by because of a bug in the system and ended up being able to register . The system, due to a bug, failed to reject it. It should have forced you to register   which you eventually requested a switch to. There is no reason to allow you to have a lowercase letter as your username as that is not permitted by the system for anybody.


 * As for this being the first you've heard of this: [//en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_105#Link_in_history_says_user_does_not_exist I think not]. I know I brought it to your attention as a polite and helpful aside as has also done here. So that is at least three times it has been discussed and maybe there are others that have slipped your mind or that you are unaware of because the majority of people are unable to ping you?


 * Visual Editors do not use Source Code so you probably never hear from them. I have never understood why anybody in a L/R country using Latin keyboard would have the need for a username such as yours, or why they register one username yet display another. Makes it hard to communicate. I would suggest changing the display version of your username as that is where many folks grep your username from. Cheers!  18:43, 23 June 2016 (UTC)
 * Yes Checkingfax, I am aware that people had difficulty with the "lowercase" ɱ being my username. What I'm saying is new, quite clearly I should add, is any difficulty in pinging with my username being "uppercase". However they're not lowercase and uppercase. See "M with hook". A lowercase and uppercase set would be pronounced the same way and used interchangeably, except to capitalize in the beginning of a sentence or with a proper noun. However, ɱ and Ɱ have different pronunciations and are therefore not used interchangeably ever. My usernames and even that conversation predates Visual Editor, however you're wrong because Visual Editor is only on the main space, not talk or user talk pages. I'm sorry for your apparent inconvenience, but it's not an excuse for no contact; copy/paste should always be do-able. As another note, Winkelvi's signature inconveniences me as my CTRL-F function is hard to use because the signature is so colorful, I can't easily find the CTRL-F text. There will always be inconveniences, please learn to adapt when necessary. ɱ  (talk) · vbm  · coi) 19:02, 23 June 2016 (UTC)
 * Hi, . You are correct about the VE angle.


 * I am not a fan of style of signature manipulation as it too is not copyable from the front facing view. Their previous front facing version was unreadable. They switched to something readable. I still do not care for it  from a pinging standpoint.


 * Your username currently is uppercase Latin M with hook. It previously was lowercase Latin M with hook. Our system does not allow the use of lowercase letters as the leading character in a usernames. It slipped by due to a system bug, but you already know that. Cheers!  19:17, 23 June 2016 (UTC)


 * That template only explains that it should not be used, but it doesn't mention why it shouldn't be used. Why are large figures inaccurate using that inflation data? Can we come up with a system that would be accurate? Also, you haven't replied to my other concerns, which as mentioned, I'd really appreciate. Also I'd strongly recommend archiving your talk page more frequently. With 250 conversations, it makes typing here using this server-based computer mildly difficult. Thank you, ɱ  (talk) · vbm  · coi) 17:55, 23 June 2016 (UTC)
 * Hi, . The ombox template at the top of the template documentation page mentions WP:Original research. Cheers!   19:07, 23 June 2016 (UTC)
 * Yes, but it doesn't say why not. Do you have any idea? If so, can we develop something that wouldn't use OR? ɱ  (talk) · vbm  · coi) 19:13, 23 June 2016 (UTC)
 * Hi, . The ombox states in so many words that we would have to hire an accountant for each such use and we would have to back up each such use with a reliably sourced citation. Cheers!  19:20, 23 June 2016 (UTC)

Ping: Question about template:definition needed
You have an answer at Template talk:Definition needed. —Kri (talk) 15:12, 23 June 2016 (UTC)
 * Thank you kindly, . How did you stumble on my inquiry? Cheers!  20:37, 23 June 2016 (UTC)
 * You're welcome. I was watching the page as I had created the template. :) —Kri (talk) 23:54, 23 June 2016 (UTC)

DYK for Caitlyn Jenner
Cas Liber (talk · contribs) 00:01, 24 June 2016 (UTC)

WikiProject X Newsletter • Issue 9
Newsletter • May / June 2016

Check out this month's issue of the WikiProject X newsletter, featuring the first screenshot of our new CollaborationKit software!

Harej (talk) 00:23, 25 June 2016 (UTC)

Tech News: 2016-26
 Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes
 * The ORES service has now moved to a new location. This should make it easier to use ORES. The ORES 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.
 * The order of wikis in collapsed cross-wiki notifications was different than when the list was expanded. This is now fixed.
 * A new category for tracking pages with math errors was added:    :.

Problems
 * The Wikimedia Etherpad crashed on June 23. Some edits done that day have been lost. They can be found at etherpad-restore.wikimedia.org for another few days.

Changes this week
 * Octicons-sync.svg The new 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.

Meetings
 * Octicons-sync.svg 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 on 28 June at 19:00 (UTC). See how 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.
 * 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.
 * 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.
 * Octicons-tools.svg From 29 June git.wikimedia.org (running Gitblit) will redirect all requests to Phabricator. The vast majority of requests should be correctly redirected.
 * 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.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe. <section end="technews-2016-W26"/> 15:42, 27 June 2016 (UTC)

DYK for Margareta Hallin
Cas Liber (talk · contribs) 00:03, 4 April 2016 (UTC)
 * Hi, . I cannot find Hallin's DYK on the April page. Please advise. Cheers!  08:45, 7 May 2016 (UTC)
 * Hi, . I still cannot find Hallin's DYK here or anywhere on the April page. Please help me if you can. Cheers!  17:51, 27 June 2016 (UTC)
 * Weird....I have also looked at history to see if it is there. Bit flummoxed by this....Cas Liber (talk · contribs) 21:23, 28 June 2016 (UTC)
 * Ok, looking in the history of Q5, I can see the credit for the DYK here. Cas Liber (talk · contribs) 21:27, 28 June 2016 (UTC)
 * Allen3 added it to prep 5 here and I moved it to Q5 here...and it's there in Q5 here.. Cas Liber (talk · contribs) 21:32, 28 June 2016 (UTC)
 * Aah I see, removed it here. He provides his reason here. Cas Liber (talk · contribs) 21:42, 28 June 2016 (UTC)
 * Thanks, . Did ever notify  about the pull? Cheers!   00:08, 29 June 2016 (UTC)
 * Looking back at it, I don't think I did. I pinged a few people involved with the DYK nomination, but for some reason (stupid error, nothing nefarious) I forgot BabbaQ. Fram (talk) 06:55, 29 June 2016 (UTC)

Salon des wiki
Just realized the RSVP thing is mandatory and has a cut-off that I missed. I'm in town but I guess I can't go this time. Demmit. 50.1.62.201 (talk) 01:48, 30 June 2016 (UTC) (-- SMcCandlish, offsite)


 * Hi, Stanton. We have figured out a way to satisfy the building security and now RSVP is very helpful to us so we know how much food and drink to order but it is not set in stone any longer. Next time you can come spur of the moment if you miss the cutoff. RSVP is preferred but not mandatory. What is still mandatory is to bring I.D. Cheers!  07:17, 30 June 2016 (UTC)

Editing News #2—2016
Editing News #2—2016 Read this in another language • Subscription list for this multilingual newsletter

Did you know?

It's quick and easy to insert a references list.

Place the cursor where you want to display the references list (usually at the bottom of the page). Open the "" menu and click the "" icon (three books).

If you are using several groups of references, which is relatively rare, you will have the opportunity to specify the group. If you do that, then only the references that belong to the specified group will be displayed in this list of references.

Finally, click "" in the dialog to insert the. This list will change as you add more footnotes to the page.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Arabic and Indic scripts, and adapting the visual editor to the needs of the Wikivoyages and Wikisources.

Recent changes
The visual editor is now available to all users at most Wikivoyages. It was also enabled for all contributors at the French Wikinews.

The single edit tab feature combines the "" and "" tabs into a single "" tab. It has been deployed to several Wikipedias, including Hungarian, Polish, English and Japanese Wikipedias, as well as to all Wikivoyages. At these wikis, you can change your settings for this feature in the "" tab of Special:Preferences. The team is now reviewing the feedback and considering ways to improve the design before rolling it out to more people.

Future changes
The "" button will say "". This will affect both the visual and wikitext editing systems. More information is available on Meta.

The visual editor will be offered to all editors at the remaining "Phase 6" Wikipedias during the next few months. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including: Arabic, Hindi, Thai, Tamil, Marathi, Malayalam, Urdu, Persian, Bengali, Assamese, Aramaic and others.

The team is working with the volunteer developers who power Wikisource to provide the visual editor there, for opt-in testing right now and eventually for all users. (T138966)

The team is working on a modern wikitext editor. It will look like the visual editor, and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices around September 2016. You can read about this project in a general status update on the Wikimedia mailing list.

Let's work together
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready.
 * Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor?  Please sign up for the new VisualEditor Community Taskforce.
 * Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Watch the Tech Talk by Sebastian Karcher for more information.

Whatamidoing (WMF) (talk), 21:09, 30 June 2016 (UTC)

Nomination for adminship
– Corinne (talk) 03:51, 1 July 2016 (UTC)

FYI: no hyphen in "archiveurl" or "archivedate"
Thanks for updating the citation URL in Honey. I noticed, however, that when you (or more accurately, "Checklinks") added to the citation template (see Honey: Difference between revisions) you put hyphens in "archiveurl" and "archivedate" (i.e. "archive-url" and "archive-date"). This unfortunately made the archive URL unclickable. I removed the hyphens and the archive link is now clickable. Just thought I'd let you know about the hyphens. Perhaps "Checklinks" needs to be modified in order for this not to occur with other updates. Thanks again for updating the citation. Akhooha (talk) 00:47, 9 July 2016 (UTC)
 * Hi, . Wow, good eye. That was a while ago. A couple of things:
 * Checklinks only merges archived links after I manually create them.
 * The documentation at states to use a hyphen. Between you and me I have made it work both ways.


 * I would like Checklinks to be modified to do more of the rote effort that it takes me to manually craft archived links.


 * Please alert the Template Editors on the cite web template page that something has changed that has broken those 2 hyphenated template keys. Cheers!  03:08, 9 July 2016 (UTC)
 * UPDATE: I just tested the [//en.wikipedia.org/w/index.php?title=Honey&oldid=728978338 Permalink] for the page version before you edited it, and it the hyphenated version seems to work fine, at least on my setup (Win 10 Ultimate, Firefox, i5 processor, Vector skin). Cheers!  05:13, 9 July 2016 (UTC)
 * Hmmmm, that's odd. I was just starting to write to the citeweb editors about the issue, but I'll hold off. Maybe it's just an issue with my system. I'm using Windows XP, Firefox 43.0. Could be that XP is at fault. Thanks for checking it out. Akhooha (talk) 16:45, 9 July 2016 (UTC)
 * Hi, . My FF is v47.0 if you end up making a report. Keep me in the loop. Cheers!  17:08, 9 July 2016 (UTC)


 * How very strange. I just tried it again with the hyphenated parameters, and it was working properly. I have no idea why it wasn't working last night. Sorry to have bothered you... Akhooha (talk) 22:32, 9 July 2016 (UTC)

Tech News: 2016-28
<section begin="technews-2016-W28"/> Latest tech 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 new image scaler fixed a number of bugs for showing SVG files. Some new problems turned up.
 * Notifications are grouped by types. They are now counted by number of notifications and not by unread groups. That change may increase the number of notifications displayed. The earlier way of counting was often incorrect. Unread notifications will also be displayed first.
 * Special:Notifications now has a maximum width for the notifications list on desktop computers. This allows long titles and descriptions to be cut properly. Notifications are now also better parsed.

Problems
 * On 5 July Wikimedia Commons had problems and could not be edited for 20 minutes. For a short while after that the recent changes log and some gadgets were not working properly. It affected administrative actions on other projects too.
 * Users who have multiple unread notifications can mark them as read by visiting Special:Notifications page on their wiki.

Changes this week
 * Octicons-sync.svg The new version of MediaWiki will be on test wikis and MediaWiki.org from 12 July. It will be on non-Wikipedia wikis and some Wikipedias from 13 July. It will be on all wikis from 14 July (calendar).

Meetings
 * Octicons-sync.svg 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 on 12 July at 19:00 (UTC). See how to join.

Tech news prepared by tech ambassadors and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe. <section end="technews-2016-W28"/> 15:14, 11 July 2016 (UTC)

Wikidata weekly summary #217
<div style="margin-top:10px; padding-left:5px; font-family:Georgia, Palatino, Palatino Linotype, Times, Times New Roman, serif;">Here's your quick overview of what has been happening around Wikidata over the last week. <div style="-moz-column-count:2; -webkit-column-count:2; column-count:2; -webkit-column-width: 400px; -moz-column-width: 400px; column-width: 400px;"> <div style="margin-top:10px; font-size:90%; padding-left:5px; font-family:Georgia, Palatino, Palatino Linotype, Times, Times New Roman, serif;">Read the full report &middot; Unsubscribe &middot; Lydia Pintscher (WMDE) 15:33, 11 July 2016 (UTC)
 * Events/Blogs/Press
 * Connecting OpenStreetMap and Wikidata, blog post by Mapbox
 * Past: office hour on IRC (log)
 * Now: ISMB 2016 Editathon
 * Upcoming: Viquimarató de Wikidata sobre Ramon Llull
 * Upcoming: OpenSym
 * Monitoring the Gender Gap with Wikidata Human Gender Indicators
 * An Empirical Evaluation of Property Recommender Systems for Wikidata and Collaborative Knowledge Bases
 * Mapping street names to Wikidata entities they refer to and enriching OpenStreetMap with linked data
 * Other Noteworthy Stuff
 * The removal of Persondata from the English Wikipedia is completed. There are still much information to migrate to Wikidata at KasparBot's tool.
 * Tour de France data is coming from Wikidata in at least 3 Wikipedias
 * Freebase API will be shut down on August 31
 * TXT Werk is now using Wikidata to identify entities (previously Freebase)
 * Magnus' reference drag and drop script is now a gadget
 * Got an idea for a cool project around Wikidata but need some funding? A project grant might be an option.
 * There are several full PhD/postdoc positions available at TU Dresden with Markus including work on Wikidata
 * Magnus' Wiki Loves Monuments tool now also reads cultural identifiers from Wikidata and was switched to use SPARQL
 * Did you know?
 * Newest properties: archive date, permanent duplicated item, throughput, NAIF ID, point of penalty, Transferred Account Data Interchange Group Code, Estonian Research Portal person ID, bateau d'intérêt patrimonial, Cultural heritage database in Austria ObjektID, Nomisma ID, WikiTree ID, Estonian cultural monument ID, BacDive ID
 * Query examples: timeline of space probes (source), countries with most UNESCO World Heritage Sites (source), places in America named after places in England (source), emergency number by country size (source)
 * Development
 * Working on an infographic to represent the flow of data in Wikidata
 * Work on multi-content revisions in order to be able to store an entity (item, property, mediainfo) and wiki text in the same page (This is needed for Commons) (T107595)
 * Did more interviews with editors as preparation for the work on automated list generation for Wikipedia and co based on Wikidata data
 * Fixed a bug with data parsing in Korean and a few other languages (T139509)
 * Added "non" as a language code for monolingual text values (T137115)
 * Removed display of calendar model for dates with precision of 10 years or larger (T133973)
 * Fixed issues in some of the forms on special pages on mobile (T138413)
 * Disabled PDF export in item and property pages (T136814)
 * Worked on making it possible to have quantities with no bounds set (T115270)
 * Monthly Tasks
 * Hack on one of these.
 * Help develop the next summary here!
 * Contribute to a Showcase item
 * Help translate or proofread pages in your own language!
 * Help merge identical items across Wikimedia projects.
 * Add labels, in your own language(s), for the new properties listed above.

Re: Rosie Stephenson-Goodknight
The reference is after the colon. If you so desire, you can duplicate reference #9 after the block quote. Next time, could you please actually try to address the problem (by eg checking a reference) or leave a talk page message instead of lazily leaving a cn? This will help maintain article quality when people aren't keeping as close of an eye on their watchlists as I do. Thanks. Ed [talk] [majestic titan] 19:36, 11 July 2016 (UTC)

Elsa Peretti page
Hello I was advised by User:Natalie.Desautels to write to you regarding Elsa Peretti's page. My main concern is to make the article compliant with WP's standards and have the alert tags removed. I was wondering if you could help out with this page or suggest how to go about improving it. Thank you very much. NPF-webmaster (talk) 09:42, 10 March 2016 (UTC)
 * Hi . Some of WP's "rules" are over the top


 * I am going to send you a COI notice on your Talk page that has a lot of links instructing you on the proper protocol to put any COI worries to bed. Please do not be offended by it.


 * How close are you to Elsa? Can you get a picture? Can you find out the true name of her alma mater? The full name. Can you get video? Audio? Signature? Examples of her work? They must be properly licensed. is good at piercing that gauntlet.


 * The person placing maintenance tags is supposed to follow certain protocol before and after placing such tags. They are the only ones that can tell you exactly why they placed the tags. Otherwise it's just WP:Drive by tagging.


 * Please explain the precise meaning of your chosen WP username.


 * I am on an Art+Feminism push right now so helping Elsa is right up my alley! To that end I have already made some minor edits. Cheers!  10:40, 10 March 2016 (UTC)


 * Hello I imagine that the username NPF refers to the The Nando and Elsa Peretti Foundation (NaEPF). The best way I like to legally use photos and other media is, well, in this case I would have someone in the NPF who is protected under "person for hire" to upload photos to a Flickr account, mentioning "all rights waived", and then use Flinfo to get all the info and media automatically into Commons; this method is a great time saver. The license I prefer is "Public Domain Dedication (CC0)", which should be easy to ask for and procure for anyone close to Peretti. The direct Commons method is a possibility as well, although I find it more arduous ...more steps. If NPF-webmaster can upload to Flykr, I can do the rest. ...so many images in Google... best wishes, Natalie --Natalie.Desautels (talk) 11:02, 10 March 2016 (UTC)


 * Hello thanks to both of you. I wrote I was the webmaster of the Nando and Elsa Peretti Foundation on my user page when I created the account! NPF was because it was called Nando Peretti Foundation earlier. Natalie, regarding the photos, I'm hoping to receive shortly some material from, among others, Tiffany's. Can we email on this matter so you can tell me exactly the kind of license etc? Thanks! NPF-webmaster (talk) 11:22, 10 March 2016 (UTC)


 * Hello I would be very pleased to help. Copyright issues seem complicated on the surface, but there is a way to greatly simplify them and satisfy Wikipedias' needs. Just write when you are ready and I will take the pleasure to send you a few tips on how to upload to Wikipedia Commons and get your embed code if need be. I think it would be nice to have a photo of the commemorative plaque I recently saw in the vitrine at Tiffany, NY; it was for celebrating their 25 year collaboration. In this instance, without actually embedding this photo in the article, you could link to it as a source to "prove" this 25 year association. Here you use the "file" code, not the "page" code, but more on that when you are ready. It's really not very hard. all my very best, Natalie --Natalie.Desautels (talk) 11:09, 12 March 2016 (UTC)


 * Regarding your revert of the sentence: "In 2000 Elsa Peretti inspired her father Nando to create a charitable foundation called the Nando Peretti Foundation (NPF)." which I had reverted to the correct version: "In 2000 Elsa Peretti established a charitable foundation called The Nando Peretti Foundation.". As you know I am writing on behalf of the Foundation, and therefore rest assured I know quite well when and by whom it was founded!! If you still need to be convinced, please know that Ferdinando Peretti died in 1977. The Foundation was founded by Elsa Peretti in 2000, in honour of her father. These are the kinds of mistakes in the edits of this page that far from being comical, are very frustrating to witness. Kindly revert the sentence to my correct version, thank you.NPF-webmaster (talk) 09:28, 4 April 2016 (UTC)
 * Hi, . OK, I did not revert it, but I refactored it. Let me know what you think now. I believe I hit the sweet spot. Going forward, please try to include edit summaries. Cheers!  10:09, 4 April 2016 (UTC)


 * Hello Checkingfax, just wondering if you think the two alerts left on the page can be deleted. They have been addressed fully in my opinion. If you think they can be removed, would you consider doing so yourself? Thanks. NPF-webmaster (talk) 16:17, 12 July 2016 (UTC)