User talk:Mr. Stradivarius

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Welcome to my talk page! Pull up a chair, and feel free to ask me anything.

Urvashi rautela content[edit]

Hi Stardivarius, This is prashant manager of urvashi rautela who handle her all online activities and promotion. The few content was wrong and mention for un necessary reason. The ref video was upload as youtube ref. Her official website is under progress. The Rautela was subsequently dethroned is unwanted news. My email id is and Urvashi Rautela <> is the actual id of urvashi if you want cross verify you can mail her directly. ImUrvashiRautela i am trying to recorrect and update unwanted news. You can suggest how to improvise and avoid unwanted content that affect urvashi as a women who is growing public figure in India. You can check Mar 2, 2015, 12.00AM IST TNN content in leading paper

{ Ahmedabad's most eagerly awaited annual event, the Times Food Awards 2015, just got bigger and better this year! On a pleasant evening, all roads led to the Courtyard by Marriott, Ahmedabad, the hospitality partner for the event. Bollywood heartthrob Ali Fazal and the gorgeous Urvashi Rautela, actress and Miss Universe India 2012, were the chief guests for the evening. } if she was dethroned in 2012 times of india wont mention in march 2 2015 as Urvashi Rautela, actress and Miss Universe India 2012.

So humble request please dont put back dethroned words again which affect somebody public figure career.

Regards Prashant — Preceding unsigned comment added by ImUrvashiRautela (talkcontribs) 17:12, March 3, 2015‎

Nancy Ganz[edit]

Hi Mr. Stradivarius,

I submitted the article recently. This wikipedia world is so fascinating and scary for me, because I don't know what the heck I'm doing. I submitted the page and followed the directions and now have no idea where it floated off to. I hope you can find it. I can't even find my own user page. Geez. The name of the article is Nancy Ganz. Unfortunately, I did not copy the link because again I don't have a clue where to begin or end. I hope you can help. Feliciamedina78 (talk) 19:06, 16 March 2015 (UTC) ?

@Feliciamedina78: Hi Felicia! Your article is at Draft:Nancy Ganz. I found that by looking through your contributions to the site - you can do that too by clicking on the "contributions" link at the very top-right. I know that Wikipedia can be a little overwhelming at first, so try Wikipedia:Tutorial for a good place to start. I'll take a look at the article later when I'm feeling a little more awake. — Mr. Stradivarius ♪ talk ♪ 23:23, 16 March 2015 (UTC)
It looks rudely ready for publication, I did a few small fixes. Never pulled the trigger on an AFC before, however. ResMar 02:36, 17 March 2015 (UTC)
@Resident Mario: If you think it's ready, go ahead! I would prune some of the promotional wording, though, e.g. I would change "entrepreneur and leader" to just "entrepreneur". And don't forget to check for copyvio. You can turn the AfC script on in your preferences, but you will also need to add yourself to the list of users if you haven't already. — Mr. Stradivarius ♪ talk ♪ 02:43, 17 March 2015 (UTC)

@mr.stradivarius :: aha! I found you. Okay still trying hard to navigate around all this. I'll remove promotional wording and appreciate your advice so much! Feliciamedina78 (talk) 21:25, 10 April 2015 (UTC)

Hi Mr. Stradivarius,

I made changes to the page [[1]] as you mentioned. Could you tell me if it meets your approval? Thanks again. Feeling a little more comfortable in wiki world. Feliciamedina78 (talk) 03:37, 14 April 2015 (UTC)

@Feliciamedina78: I've gone through and removed most of the promotional wording (I don't think your edit went nearly far enough). Let me know if you have any questions about my edit. — Mr. Stradivarius ♪ talk ♪ 08:57, 14 April 2015 (UTC)

Signpost (4)[edit]

Hey, how's it coming along with the tag-by-year thing? Anyway, just wanted to ask if you could on the side implement a module for Wikipedia:Wikipedia Signpost/Templates/Tag series. It's meant to serve as a replacement for Wikipedia:Wikipedia Signpost/Templates/Series (whoo! no more manually gathering fourteen stories at a time! or having to update them!), but has two issues:

  1. formatdate doesn't seem to work on Lua output, so I can't format the date to the format we use for instance here.
  2. More seriously, the series template implements breakpoints below which stories are hidden for brevity. Otherwise the template gets to be way too long and messes up formatting on old articles. I can't do it the really complicated way I did it in the series template because the script outputs the info in a single block, but I'm sure you can do it from your end.

Thanks! ResMar 16:01, 27 March 2015 (UTC)

I'll be busy for a couple of days so I won't be able to code anything up right now, but there's already a fix in place for the date formatting. You can't use parser functions with the rowformat parameter, as they are all expanded before they enter Lua. The fix is to use a special row template, as described at Wikipedia:Wikipedia Signpost/Templates/Article list maker#Row templates. Best — Mr. Stradivarius ♪ talk ♪ 05:50, 28 March 2015 (UTC)
Yes check.svg Done See Template:Signpost series. ResMar 18:50, 28 March 2015 (UTC)
See also: Wikipedia:Wikipedia Signpost/Index#To-do. ResMar 16:17, 29 March 2015 (UTC)
Would it be too bad to have you to run the script again? I'm doing research for a sister projects report and realized I'd forgotten half of them. Whoops... ResMar 18:37, 7 April 2015 (UTC)
@Resident Mario: Sure, I've just started it running now. By the way, I've been working on a user script for updating the tags, and when it's deployed we'll have to stop using the python script if we don't want people's tags to be obliterated. So if there are any other tags you've missed, now's your chance. :) — Mr. Stradivarius ♪ talk ♪ 19:01, 7 April 2015 (UTC)
Hmm. The trouble is that there's always more to be added! For instance, I could go with stripping a list of all of the chapters and throwing it in there. A list of all countries, too. Are you saying that after the script is deployed it will no longer be possible to have the script sniff up and index past articles? ResMar 19:08, 7 April 2015 (UTC)
@Resident Mario: That's right. The python script isn't clever enough to know what was added by a human and what was added by filtering keywords. It just makes a new list every time and overwrites the old one. Trying to update it to separate human and robot edits would be very hard - it's probably better to just make a final decision about what keywords to use and then fine-tune the tags with the tagger gadget. — Mr. Stradivarius ♪ talk ♪ 19:43, 7 April 2015 (UTC)
Hmm, you are right. In the end it'll require manual tagging anyway but there's no reason that we can't knock out the biggest missing tags now. ResMar 19:53, 7 April 2015 (UTC)
I saw the new user-script. Wonderful! Ok, so, a small modification in the way the Lua script works: when you generate a link to an article, can you add #tagname to the end of the tag? By combining that with anchors it'll allow us to pretty seamlessly link directly to particular articles about a topic. See, for instance, {{Ib}}.
This will be really easy to implement going forward. Just wire it up as an issue compilation operation.
Doing this in archival issues may be more difficult. ResMar 01:19, 13 April 2015 (UTC)
@Resident Mario: What if an article has more than one tag? How do we decide which one to use in the page link? As for the gadget, there are still a few things that I want to check/test, particularly security-related things. I want to be sure that there are no problems with things like cross-site scripting before people start using it. Also, before people start using it we will need to finalise the list of tag keywords, and run the python script again. So you've got one final chance to make the list as good as possible - no pressure. ;) And finally, are there any other features you'd like to see in the tagger gadget? I'm thinking it might be nice to autodetect some tags based on the subpage name when a tag subpage is first created. So when you write a new "News and notes" article, the script would see that the subpage name was "News and notes" and automatically add the "newsandnotes" tag to the tag edit box. But if you have any other suggestions, I'd love to hear them. — Mr. Stradivarius ♪ talk ♪ 11:18, 13 April 2015 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── I need to format this, which will take a little bit, but it looks like this. The first call-string in the list will be unspaced. This is because when throwing the tag at preloadparams, a_b is read differently from a b, the latter of which just breaks—it's read as a, because of the space. So, in order for that to work consistently the first alias in this list of them has to be un-spaced. This is also true of section-links: a link in the form #A B will send you to #A. However, if we consistently use un-spaced invocation names as the first element of the list and then section-link using that when calling a particular tag, it can be made to work in both cases: by calling that first tag manually with preloadparams, and by making that the parameter of choice when making section links. So for instance if Story matches a tag, and the first item in that tag's list is suegardner, the list mechanism will return Story#suegardner and the equivalent preloadparams invocation will be preloadparams[]=suegardner.

The actual linking will be handled by anchors. Placing them going forward will be easy, it's just an operation for the writers and editors to perform. Doing it backwards though might be more tricky: it'll require the introduction of the templates I'm working on at the moment, easy enough, and then the writing-in of the tags, much harder. Since it's basically regex, I guess that AWB can we be used for this task? So it becomes a two-step process:

  1. Replace section headers with the appropriate anchored templates, and fill out those templates' tags.
  2. Use the script to save those tags to the Lua hit-list.

Then invoking the module will report back the #link already coded into the anchoring template, and readers will be bounced to the correct section on load.

I'll work on the tags list.

I pinged you on your own talk page. Ha! ResMar 13:37, 13 April 2015 (UTC)

(edit conflict) Also, about pages that are tagged with duplicate tags like "edit filter" and "editfilter" - I don't think that's such a good idea, as it is going to make the tag list harder to maintain. Instead, how about just automatically removing spaces and punctuation from tags? We could remove them when people save them with the gadget, and then when people search for the tag "edit filter", we could silently correct it so that they are searching for "editfilter". — Mr. Stradivarius ♪ talk ♪ 13:42, 13 April 2015 (UTC)
@Resident Mario: The module now adds tags as a section name when you use the new fullpage parameter. Take a look at the updated documentation at Wikipedia:Wikipedia Signpost/Templates/Article list maker#Parameters. I've also updated the module, the python script and the gadget to automatically remove all spaces and punctuation from tags. Note that this is mainly for ease of maintenance of the tag data - you can actually have section names with spaces in, as long as you encode them properly. With this, I think everything is pretty much ready to go - just have one last look over the tag data and I'll run the python script one last time before we start manual tagging. — Mr. Stradivarius ♪ talk ♪ 18:58, 13 April 2015 (UTC)
Silently formatting input sounds like a very, very good idea, and I'm happy to see you implement it. One more thing: can you write a capacity (perhaps a different script?) to return the number of instances of a tag within a certain time period? Also, on full-page, I...can't figure out how it works :) ResMar 00:58, 14 April 2015 (UTC)
Oh, and also: hold off on finality until I can go through the tags and punch them into better shape. Before we can go gold, so to speak, the tags and their meta-information has to be in order. I've worked up a modified tabulated structure for the index page in my sandbox: User:Resident Mario/sandbox. Advantages: sort-ability. Disadvantages: no obvious place to place additional visual meta-data. (time? place? sectionality?). I think I'll run with this, once I water down the colors. Additional data can be displayed via a more detailed invoke template. ResMar 03:23, 14 April 2015 (UTC)
Last time for today, I promise: new tag invocation interface. ResMar 04:08, 14 April 2015 (UTC)
@Resident Mario: I've added a counting feature to the module, and you can access it at Wikipedia:Wikipedia Signpost/Templates/Article count. As for how to use fullpage, just use it as a row format parameter or a row template parameter. For example, try {{Wikipedia:Wikipedia Signpost/Templates/Article list maker|rowformat=* [[${fullpage}]]|rowseparator=newline|tags=semi-protection, pending changes}}. — Mr. Stradivarius ♪ talk ♪ 06:32, 14 April 2015 (UTC)

Archive integrity[edit]


Have you ever considered that one might vandalize your talk page archives and you might not notice?

Best regards,
Codename Lisa (talk) 19:14, 5 April 2015 (UTC)

@Codename Lisa: Are you talking about this subtle vandalism? ;) Funnily enough, I just added all my future archives up to number 50 to my watchlist the other day, so I'll probably notice if anyone does something silly. And by the time I get to archive 50, hopefully we will have Flow and I won't have to worry about posts being edited by other people. — Mr. Stradivarius ♪ talk ♪ 03:23, 6 April 2015 (UTC)
My God, your little joke hurts! But now that I think, I edit archives a lot, when I move a file. I've had no reverts so far and have been thanked a dozen times. And I distinctly remember that at least once, I couldn't unlink a backlink because it was in an edit-protected admin's archive. I even remember visiting a wiki, in which a User:ArchiveBot had the archive-bot right that enabled it to create pages, edit-protect them and archive messages in them. (I fancy autoconfirmed users can't edit these pages.)
But I am remembering these just now; when I posted my original message, it was just a concern that suddenly gripped me.
Best regards,
Codename Lisa (talk) 08:10, 6 April 2015 (UTC)

Nomination for merging of Template:Edit template-protected[edit]

Template:Edit template-protected has been nominated for merging with Template:Edit protected. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. —capmo (talk) 12:45, 6 April 2015 (UTC)

Tech News: 2015-15[edit]

15:42, 6 April 2015 (UTC)

Nomination for deletion of Template:Comment from uninvolved editor[edit]

Ambox warning blue.svgTemplate:Comment from uninvolved editor has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Steel1943 (talk) 23:41, 7 April 2015 (UTC)

Please comment on Template talk:Freenode[edit]

The feedback request service is asking for participation in this request for comment on Template talk:Freenode. Legobot (talk) 00:10, 9 April 2015 (UTC)

The Signpost: 08 April 2015[edit]

General Sanctions: Electronic Cigarettes.[edit]

Commons-emblem-notice.svg Please read this notification carefully:
A community discussion has authorised the use of general sanctions for pages related to electronic cigarettes.
The details of these sanctions are described here.

General sanctions is a system of conduct regulation designed to minimise disruption in controversial topic areas. This means uninvolved administrators can impose sanctions for edits relating to these topics that do not adhere to the purpose of Wikipedia, our standards of behaviour, or relevant policies. Administrators may impose sanctions such as editing restrictions, bans, or blocks. An editor can only be sanctioned after he or she has been made aware that general sanctions are in effect. This notification is meant to inform you that sanctions are authorised in these topic areas, which you have been editing. It is only effective if it is logged here. Before continuing to edit pages in these topic areas, please familiarise yourself with the general sanctions system. Don't hesitate to contact me or another editor if you have any questions.

This message is informational only and does not imply misconduct regarding your contributions to date.

I'm aware you don't need informing of these sanctions, given that you instated them, I was just going through by rote every editor who popped up as editing a page affected by them since the sanctions came into force. Didn't spot I'd gone past you. No offence is intended. SPACKlick (talk) 11:32, 10 April 2015 (UTC)

Don't worry, no offence taken - although I will admit to getting a little chuckle out of it. :) — Mr. Stradivarius ♪ talk ♪ 12:59, 10 April 2015 (UTC)



I have a concern that I do not want act directly about it. So, I was wondering you could help.

A user called "Lumia930uploader" has recently registered on Wikipedia. Looks like a bona fide user but his username is certainly in violation of WP:PRODNAME; see Microsoft Lumia. But he is now in that phase that gets reverted left and right. (Ah, the memories! I was there too. I made friends. Face-smile.svg) And I am the one doing some of them. I think if a user he had never seen before told him, he'd feel less offended.

What do you say?

Best regards,
Codename Lisa (talk) 20:08, 12 April 2015 (UTC)

@Codename Lisa: I'm not actually so sure that their username is a violation of PRODNAME. I took it as saying that they upload stuff with the Lumia 930, not that they represent Microsoft or Nokia. Compare with a user like Shinkansen Fan - just having a username that says you are a fan or a user of something doesn't make it a username violation, I would say. Although feel free to ask others for their opinions - I don't have that much experience with WP:UAA, etc. — Mr. Stradivarius ♪ talk ♪ 11:00, 13 April 2015 (UTC)

User Box WP Japan[edit]

Hi. I have a discussion up at Wikipedia talk:WikiProject Japan#Membership Roll? which concerns users who display {{User WikiProject Japan}} on their user page.

If I can get consensus, I would like to list you all under Category:WikiProject Japan participants. As of now, you will not be listed unless you switch to the other User box {{User WP Japan}}.

And if you really do not want to get listed, would you still mind switching to the other User box and use the feature that suppresses listing?
If you don't want to be listed, replace {{User WikiProject Japan}} with {{User WP Japan|nocat=true}}, or on your {{Babel}} replacing your |WikiProject Japan| with |special-boxes={{User WP Japan|nocat=true}}|
Thanks. --Kiyoweap (talk) 11:00, 13 April 2015 (UTC)

Tech News: 2015-16[edit]

16:41, 13 April 2015 (UTC)

Signpost (5)[edit]

I've begun the process of getting the initial lot of tags into order. This is going to be a long and gradual process. Once it's done I've got to reformat how the Signpost handles tagging in its own templates, then it's community tagging time. I wonder if it'll be finished by the end of this year... ResMar 01:26, 15 April 2015 (UTC)

Oof. Another request ;). Can you add an option to limit the number of characters of a title displayed, creating a "..." after a certain point? See: this output for why. ResMar 20:11, 15 April 2015 (UTC)
@Resident Mario: That shouldn't be too hard - it's going to mean yet another parameter though. How many characters do you think the title should be limited to? — Mr. Stradivarius ♪ talk ♪ 20:18, 15 April 2015 (UTC)
The issue is that the visualizations can only be limited to a certain px width. Ok: but then the bar-chart option for Module:Chart does not respect center! Attempting to use the tag shifts the chart off-center. So I cannot define that bounding box using percentages. The output I linked to is configured use float for that reason. Maybe you can investigate the configuration and see if it's something that can be fixed on this end? A more elegant solution would be to break the titles themselves along the spaces and I don't know why it doesn't do that. ResMar 20:43, 15 April 2015 (UTC)
A quick check shows it's a float problem. Damn. ResMar 21:13, 15 April 2015 (UTC)
@Resident Mario: Welcome to the joys of web design. :) You need to set an explicit width on the div that houses the long titles - that will make them wrap. Otherwise, the total width of that div is the total width of the text, and seeing as you are floating the box on the right, if the width of the div on the left plus the width of the box on the right adds up to more than the width of the page, the box on the right will be forced to move underneath. I set the div to 500px for you to show you what it looks like. — Mr. Stradivarius ♪ talk ♪ 21:42, 15 April 2015 (UTC)
I considered that, but it's not a great solution—it leaves large screens with a lot of dead room. Can remove some of it using center but...guess that's got to be the work-around. ResMar 22:20, 15 April 2015 (UTC)
I made some adjustments but it should be fine. Re: this edit. It's tough on editors if there's only one precise arrangement of words which links to the series. For instance, someone might try to use {{Signpost series|tag=arbitration committee elections|type=inline}} and be discouraged when nothing comes up—even though, say, {{Signpost series|tag=ace|type=inline}} works fine. It's also a good thing from the taggers' end—you can tag with whichever of the tags comes to mind first, and be reasonably sure that whether you use jimmywales or jimbowales the result will be the same. What's up? ResMar 15:17, 17 April 2015 (UTC)
This is starting to get rather complicated and before I proceed much further I will need to do a technical write-up. But here is yet-another-thing: is it possible for you to write a module which, given a section title, returns the number that that section occupies on a page, or returns an empty space otherwise? This would allow creating section editing links with only the section titles, not their (in the case I am thinking of, arbitrary) position on the page. ResMar 16:58, 18 April 2015 (UTC)
@Resident Mario: It's technically possible to search the entire page text, parse it, and find the section number. But that parsing is expensive and error-prone, and probably isn't the best way to do whatever you're trying to do. Why do you want to create a section editing link that's not the standard one used in MediaWiki? About the duplicate tags, there is a difference between using jimmywales and using jimbowales. If taggers don't tag each matching article with both "jimmywales" and "jimbowales", then a search for "jimmywales" would turn up a different set of articles than a search for "jimbowales". Allowing the duplicates would mean a great deal of effort spent in cross-checking each article's tags to make sure that all the variants are included. It would be better to either just use one tag per subject, or to make some kind of technical fix so that we only have to define the variant tags in one place. (I'll have a think about how/whether that can be done.) — Mr. Stradivarius ♪ talk ♪ 17:17, 18 April 2015 (UTC)
I wish to store the descriptions for specific tags as they appear at Wikipedia:Wikipedia Signpost/Index at a single separate location; generate links that will allow editing those descriptions on a one-by-one basis; and generate transclusions that can be placed on other pages: the Index description, specifically, and a new "what'sit" in the invocation output. This will greatly increase ease of maintenance.
Taking into account what you've said: it's a big table so if it's an expensive function to execute there's real reason not to execute it. But the section ordering won't change, or shouldn't change! So we'd only need to run the function once, and substitute the answer into the table :).
Here's the idea: I have a new tag idea. I go to the table and put it in there using a "provisional tag" template, leaving the description blank. I hit a "create description" link to create a new section titled with the tag search-string, and input a description there, and save; I'm actually saving to some Descriptions page which acts as a database of these. Another editor, a "tag maintainer", comes along and checks the provisional tag. If they approve it, they substitute in an "approved" template which has a {{subst:#invoke:Module:Find section number by name|tag_name}} in it; when the page is saved that substitution replaces the substitution statement with the numeral indicating that section's position on the descriptions list-page. This, in turn, is used by an edit link: [{{subst:#invoke:Module:Find section number by name|tag_name}} edit description], which becomes [ edit description] after the page is saved. ResMar 19:29, 18 April 2015 (UTC)
I sketched the tech. ResMar 16:01, 19 April 2015 (UTC)


Hello, Mr. Stradivarius. Please check your email – you've got mail!
It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{YGM}} template.

Dear Mr. Stradivarius, Having learned that I must research to be a better addition to Wikipedia, it it with great promise that I give you my word that I'll not edit nor attempt to add any articles until I feel confident enough to do so. I certainly wish to be an asset to this site and not an embarrassment. Thank you for your patience and understanding, which are both greatly appreciated. Sincerest Regard, Lady Sonia Lorraine ... LsL©.

Broken script[edit]

after your change to my script, it no longer works for me in Linux/Firefox. Frietjes (talk) 22:11, 15 April 2015 (UTC)

@Frietjes: D'oh, sorry about that - that was a stupid mistake. It worked when I tested it on User:Mr. Stradivarius/findargdups.js, but I must have done something stupid like forgot to clear my browser cache. (Stupid + stupid = not a good day...) The problem was that the myContent variable wasn't available inside the scope of wpFindDuplicateArgs, because I put it inside the function that ran on $(document).ready. As long as it's available somehow it should work - if you don't like wrapping the whole script with a function, you could pass myContent in as a parameter, or just fetch it using document.getElementsByName again. — Mr. Stradivarius ♪ talk ♪ 22:43, 15 April 2015 (UTC)

The Signpost: 15 April 2015[edit]

Year in other calendars[edit]

Hi Stradivarius, thanks for fixing my code. I think, however, that the FRC should stay in the first position, as it displays only in fourteen years, during which it was the most important calendar after the Gregorian. And where you put it now it won't be noticed. Otherwise it would be necessary to add the year manually as I did in 1793. Maybe we should discuss that on the respective discussion page to reach a consensus. In the meantime I will edit the code some more, in order to have a different heading for the Paris Commune.--Hyphantes (talk) 08:34, 18 April 2015 (UTC)

Hi Stradivarius, I've made a lot of progress with my ancient Greek calendar, but ultimately I got stuck (no wonder because I never worked with that language before). Now it runs, but displays the wrong Olympiad and does not display the winners nor the 2nd, 3rd or 4th year. It would be kind if you had a look at it. Currently it is disabled, but you can easily test it by changing the second value in the timeframe. Test it with the years 496 BC or 495/94/93 BC, because that's for the moment the only entry in the data sheet. I'll include the rest of the data as soon as the project is more defined regarding the data format.

A suggestion regarding the box in general: we should use the if function to delimit the timeframe for the display of calendars yielding N/A, for example British regnal year before 1066, similar as I did with the French Revolutionary calendar. That would make the box a lot more "relevant" and as a result people should be less inclined to want it collapsed.--Hyphantes (talk) 14:23, 18 April 2015 (UTC)

@Hyphantes: Thanks for working on the new calendar! I've moved your code to the sandbox for now, because we probably shouldn't test things out on the live module in case it causes script errors, etc. I'll have a look at it now. As for not displaying years instead of N/A, that sounds like a reasonable idea. Could you propose it on Template talk:Year in other calendars so that other editors have a chance to make their opinion known before we do the work to convert the module? Also, the best way to implement it would probably be to alter the calendar object to not display anything if the year was outside a certain range, rather than to use if/then logic in all the individual calendars. Perhaps we could define years with a function rather than just a year number or a year string. That would need a little more thinking about, but we need to make sure there's consensus to make the changes first. Best — Mr. Stradivarius ♪ talk ♪ 15:19, 18 April 2015 (UTC)
Also, you're probably right about the position of the French Revolutionary calendar, so I've left it at the top. I don't think we should have two versions of the same calendar displayed at the same time, though, so I've removed the Paris commune one. — Mr. Stradivarius ♪ talk ♪ 15:23, 18 April 2015 (UTC)
@Hyphantes: I've edited Module:Ancient Olympiads to fix the stuff that I knew was wrong, and left some comments about the things I didn't understand how to fix. Have a look at the edit summaries and at the comments for my thoughts, and let me know if you still need any tips. Best — Mr. Stradivarius ♪ talk ♪ 15:53, 18 April 2015 (UTC)
@Hyphantes: About the ref tags: to understand those properly means learning a bit about how Scribunto and MediaWiki fit together. Scribunto is run halfway through the page parse, so its input is neither standard wikitext, nor HTML. First, the wikitext parser preprocesses the wikitext, expanding templates, {{#if: ...}} statements, etc. What Scribunto sees as input is this expanded wikitext. One of the preprocessing steps that the wikitext parser does is to turn extension tags like <ref>...</ref> and <nowiki>...</nowiki> into a unique string called a strip marker. So, if you use foo <ref>bar</ref> as input to a module, first the "bar" part gets converted to a strip marker. If you then output that same strip marker from the Lua module, then the "bar" reference will show up in the rendered HTML. However, if you just output the string foo <ref>bar</ref> from the module, then the parser won't have done the preprocessing necessary to turn it into a strip marker, so it will just show up as plain text. Hope this helps. :) — Mr. Stradivarius ♪ talk ♪ 17:05, 18 April 2015 (UTC)
Thanks for correcting my mess. A lot of stuff was in there because I started from the British Regnal years calendar without understanding what it means. There still seems to be something wrong, because now I get an error in line 68 (now 69) of the Module:Ancient Olympiads. Maybe you cancelled a definition that is needed there?
Regarding the Paris Commune calendar you probably didn't notice that it was limited to a single year: 1871. Since I disactivated that year for the French Revolutionary Calendar there was never a double display of the same calendar. I simply moved the Paris Commune calendar down from second position to letter P. So you actually have it twice in the list, but it displays for different years and with a different headline. You might argue that it is a waste to have a calendar for a single year and then I could reactivate that year in the FRC like it was before. But that would put it back up in second position which is justified for 1793-1805, but not for 1871. So I think my solution was the best.
Regarding the suppression of calendars in N/A years I'll follow your advice and start a discussion. I agree with you that each calendar should better have inherent mechanisms regarding display. But I'm afraid that this is a lot of work. With if then lines it is much easier to implement and to control too. In any case I have learned that we need to specify the range of display in a comment line in order to avoid misunderstandings.
Control is necessary, because I have already found an error in the ab urbe condita calendar. It displays the year 754 BC as O and 755 BC as -1. I don't think that this is correct (it should be -1 and -2) and we should check if other calendars have the same error.--Hyphantes (talk) 21:05, 18 April 2015 (UTC)
@Hyphantes: With the Paris Commune calendar, my issue is that putting code for the same calendar in twice violates the DRY principle. I don't really mind whether we put the calendar at the top or in the middle, but whichever way we do it we should only define the calendar once. If we really need to have a different location for 1871 than for the other years, it would be better to implement some kind of mechanism to reorder calendars based on the current year rather than use the same code twice. The DRY principle is also the issue I have with adding lots of if/then statements to the code. It would mean we would have to write the year calculation twice, when ideally once should be enough. I agree that it is good to have controls for errors, though. As an alternative to if/then, how about exposing the calendar-generating algorithms to other Lua modules, and then writing some test cases? Also, the Paris Commune discussion should probably happen on the template talk page as well - other editors might want a say in the matter of how important the French Revolutionary calendar might be. :) — Mr. Stradivarius ♪ talk ♪ 21:27, 18 April 2015 (UTC)

I have started a discussion on display suppressions at the talk page. I understand your professional ethos as a programmer. My simple solutions are a result of my limited competence in the field. Regarding the Paris Commune year I think I can go back to your first line which inclued 1871. But I'll need two more if then functions to change the reading of 1871 to "Paris Commune". So the script amount will be more or less the same. Well, I actually think that my DRY-infraction was on the whole the better solution. Still undecided. The discussion page looks quite deserted, so I doubt that we may get any opinion there on such a limited matter.

No progress with the Olympiads. I've put some questions in the script, but the more important thing would be to get it running again so that I can play around and learn what works and what not.--Hyphantes (talk) 23:18, 18 April 2015 (UTC)

@Hyphantes: I've edited the Olympiads script to be something like what I think you're aiming at. Well, it runs. :) As for the other stuff, if there's a consensus to change the French Revolutionary calendar location depending on the year, then I can work up the code to do it. The back-end could use a little love anyway, so it would be a good opportunity. The actual sorting would probably just be a matter of defining a custom sort function to use with Lua's table.sort function - I shouldn't think it would be too difficult. — Mr. Stradivarius ♪ talk ♪ 00:02, 19 April 2015 (UTC)
I'm testing it here: [25]
You need to change the line reading "if year >= -776 and year < -776 then" to something less disenabling like "if year >= -776 and year < -76 then"
Then test with Preview page 496 BC or 495 BC. There it is not running :(
But now it's getting late here in Italy. So I think I'll get back to it tomorrow. Good night and thanks.--Hyphantes (talk) 00:31, 19 April 2015 (UTC)
@Hyphantes: If you're loading Module:Ancient Olympiads from another Lua module, you should use the _main function, not the main function. The whole reason that there are two functions is so that there is a convenient place to access the module from other Lua modules, so you should use it. :) — Mr. Stradivarius ♪ talk ♪ 00:44, 19 April 2015 (UTC)
I had seen the debug console, but what I was missing was the fact that I had to press Enter :D.
Now I see that it actually works although it needs some refining.
This is the current result:
3rd Olympiad, held in -768 and won by Androclus of Messenia.
I would like:
3rd Olympiad, (victor
and for the following year - 767:
3rd Olympiad, year 2
accordingly for - 766:
3rd Olympiad, year 3
and for - 765
3rd Olympiad, year 4
But still remains the fact that it's not working in the page.
I guess that is what you're addressing in your last post. So maybe we are close to a solution. I'll stay up another 20 minutes then.--Hyphantes (talk) 00:49, 19 April 2015 (UTC)
Hello Mr. Stradivarius. Thanks to your valuable input I've fixed everything in the module and as far as I can see it runs perfectly for all the years in question with results as posted above. The only problem is that it still doesn't run in the calendar. You said I should use the _main function, not the main function, but I don't know how to do that. Should I write _main instead of p.main or should it be p._main ? And which of the two functions? --Hyphantes (talk) 21:14, 19 April 2015 (UTC)
I've solved the problem and now it displays in the calendar. There is still a problem with the year which is wrong by 2. I don't know why, but I'm almost there. Probably it will be enough to adjust the value in the module. I'll let you know.--Hyphantes (talk) 21:32, 19 April 2015 (UTC)
@Hyphantes: To use the _main function, you need to replace require('Module:Ancient Olympiads').main with require('Module:Ancient Olympiads')._main. When you use require, it gives you the return value of the module you ask for. In our case, Module:Ancient Olympiads has return p right at the end, so when we use require on it, we get a reference to the p table. require('Module:Ancient Olympiads').main gives us the value "main" in the p table, i.e. p.main, and require('Module:Ancient Olympiads')._main would give us the "_main" value in the p table, i.e. p._main. — Mr. Stradivarius ♪ talk ♪ 06:53, 20 April 2015 (UTC)

User:Mr. Stradivarius/chessboardfix.js[edit]

could you modify the comments in your script so this page isn't in the tracking category? Frietjes (talk) 18:51, 19 April 2015 (UTC)

@Frietjes: That's a good point! Done - thanks for letting me know. — Mr. Stradivarius ♪ talk ♪ 19:03, 19 April 2015 (UTC)

WikiProject banners and Lua[edit]

Hello Mr. Stradivarius! Technical 13 recommended I get in touch with you for an idea I have. I'm working on WikiProject X, a project to re-design the WikiProject, and as part of that I'm working on a replacement to the WIkiProject banner system. The template I came up with, ProjectTags, removes a lot of the redundancy of having a box for each WikiProject, and will be an option for WIkiProjects that want to use it. It is intended only for WikiProjects that need nothing more than the basic article assessment system, since the goal is to present less information more clearly. Because it's intended to be minimalist, I am not about to propose requiring every WikiProject to use it. I am fine with projects that need dedicated banners because they've made them support all sorts of complex use cases, but I suspect most projects have similar use cases.

What especially will make this template shine will be the use of Lua to allow the input of multiple projects. This is far superior than the approach currently taken by {{WPBannerMeta}} of nesting templates within templates. This is where you come in—do you think this is something you would be able to help with? Any support you could offer would be tremendously wonderful. I have more information on the specification here. Thanks, Harej (talk) 19:56, 19 April 2015 (UTC)

@Harej: Sure, I can help you with this. We'll have to think about exactly what features we're going to support and how the projects will be displayed. Also we need to think about how the banner will be deployed to talk pages. Probably the best way to do that would be to have a bot substitute WikiProject banners for projects that have been converted, but this will require millions of edits, so we will need consensus among the community first. — Mr. Stradivarius ♪ talk ♪ 13:19, 20 April 2015 (UTC)
I'd suggest getting the Lua module written, and am willing to help if I can, first. That way it will be available for new wikiprojects. Then, I'd be happy to run a proposal for a T13bot (task list (1) · logs (actions · block · flag) · botop (e · t · c) · contribs · user rights) task to run through and convert the existing ones through WP:BAG. — {{U|Technical 13}} (etc) 13:38, 20 April 2015 (UTC)
Thank you both for agreeing to help with this. With respect to features, I am fine with making it support more features than my current mockup (which only supports quality/priority assessments) if those features are important to most WIkiProjects, but I am reluctant to make the template support too many features. Otherwise you end up with feature creep and a massive template that is almost impossible to support. Were there additional things you two had in mind that would be useful for the template?
For deployment, I will be working on a project-by-project basis for deployment. As the creator of WikiProject Women in Technology I'm already on board; I could probably also convince my friend who runs WikiProject NIOSH to switch over (the project is brand new and it's basically one person at this point). So that's two WikiProjects right there. I think we are more likely to reach consensus if we take the slow and steady approach. Thoughts? Harej (talk) 16:31, 20 April 2015 (UTC)
@Harej and Technical 13: Thinking about this some more, I'm not sure that we should be aiming for a solution that's guaranteed to only work for a subset of projects. That would create situations like this where some projects used the new template but bigger projects stuck with their own template. That would also mean that the "Message WikiProjects" button would only reach the smaller projects, who are less likely to have editors actively watching for messages. I think a better solution would be to implement this as a MediaWiki extension. That would enable all sorts of useful features, for example rating articles directly from the article page, rating articles by selecting the rating from a drop-down menu instead of by editing a template, and having the message button default to a special page if users don't have JavaScript enabled. Doing it as an extension would also make sure that it was properly written and secure, as any updates to the extension code would need to go through code review. The sticking points would be how to get all the projects on board, and working out how to deprecate the existing banner template system. It would be more work than writing a new Lua module, but I think the end results would be worth it. — Mr. Stradivarius ♪ talk ♪ 00:08, 26 April 2015 (UTC)
  • An extension sounds fine to me. Even better is that by it being an extension, it can be PHP and avoid needing to use JavaScript at all. I directed Harej here with the goal of a Lua module, because I knew it was something you were good at and I was under the impression that you were already working on some kind of WP banner template to Lua conversion. If we're thinking extension instead, I'm thinking it might not be a bad idea to get a little more input from Jackmcbarn perhaps. :) — {{U|Technical 13}} (etc) 02:33, 26 April 2015 (UTC)
What exactly would you want the MediaWiki extension to do? Jackmcbarn (talk) 15:00, 26 April 2015 (UTC)

Incidentally, I do have a proposal for a WikiProject extension for the upcoming Wikimedia Hackathon in France. The idea is to streamline a lot of the work that goes into creating and maintaining WikiProjects. My question is, can we get an extension coded and deployed in the next two months? I doubt it. Code review takes a very long time, so I am inclined to think of an extension as a long-term project.

The ProjectTags concept is a good short-term solution. I am not too worried about the larger projects keeping their own banners, so long as there is a net reduction in banner usage. (We can probably also do without the "Message WikiProject" button for the time being.) At the same time, I would like it to support as many projects as possible. What would the template need to support in order to do this? Harej (talk) 18:36, 27 April 2015 (UTC)

Please comment on Wikipedia:Village pump (proposals)[edit]

The feedback request service is asking for participation in this request for comment on Wikipedia:Village pump (proposals). Legobot (talk) 00:09, 20 April 2015 (UTC)

Signpost (6) Δ[edit]

Holy cow, your talk-page is busy.

If you take a look at Wikipedia:Wikipedia Signpost/Index again you will see that I did what I threatened to do: I moved all of the descriptions to a unified database and enabled editing links there and back again. The module I was suggesting earlier, a per-item section counter, is not necessary: the data is hard-coded in. Since new tags will require heavy lifting by maintainers, it seems reasonable to make adding the required hard-numbered parameter, | editnumber=N, a part of their job. So the workflow looks like this:

  1. Adds a tag using the tag template.
  2. Go to the Descriptions page and create a new tag description.
  3. Manually link the edit button to the description.
  4. Add the item to the module index list.

There's one last stage I frame that needs to be built, besides a little template work here or there. I need a module that, like in your Signpost script, automatically globs a tag—like VisualEditor or Jimmy Wales—into its associated search string—visualeditor or jimmywales respectively in this case. This will remove the redundant | tag_string=X parameter in the index, which right now basically does just that, but manually. ResMar 05:05, 20 April 2015 (UTC)

@Resident Mario: We are starting to have a worrying amount of tag duplication. We have duplicate tags in the index modules, and now we have this new tag page that you've made, which adds another place that we will need to keep in sync with the index modules. The problem is that when someone decides to rename a tag, they will probably rename it in one place and forget (or not know) about all the other places where it would need to be changed. This will result in the pages slowly getting out of sync with each other, and the usefulness of the data will decrease. How about this: we create another submodule of Module:Signpost that stores tag names, tag aliases, and tag descriptions. We use this module to generate your database page, and to normalise tag aliases both in Module:Signpost and in the tagger gadget. — Mr. Stradivarius ♪ talk ♪ 13:37, 20 April 2015 (UTC)
Tag descriptions need to be editable-by-section: this is the one element of the index that we actually expect users to get involved in. Generating new tags or removing old ones should only be done with or by Signpost editors who know what they're doing and are doing it a part of regular maintenance activities. I think instead we should keep the current system and remove all tag aliases except for the first one; and standardize the first alias as a text-transform Display Name -> displayname. So, name the tag, create a new item for it in the description list, then create a new item for it in the module's list.
To make it easy, I can put the required hard-coded section number into an edit-notice by doing a {{String count}} on == in the descriptions page (there may be a more elegant solution), and set up the template so that when a description entry does not exist it provides edit-links to both the descriptions page and to the module list. So: edit the index page, add a tag, hit preview, open each of the other links in a new tab, and follow edit-notice instructions from there.
I think that's reasonable. ResMar 14:06, 20 April 2015 (UTC)
Some further thoughts, having now "finished" doing things as they are now and having gotten a more complete picture of what the maintenance activities will look like.
The ideal solution would be basically what you've described: a Lua database containing all of the tag metadata, or at least, at a minimum, their descriptions. My concern was that this would make it difficult to edit individual entries on their own, but I now realize that another user-script—something I described early on, but dropped after a while—could handle this problem: the user-script could embed a (modify) string at the end of the description, and allow users to change all of the parameters at once using a dialog much like the one you've written to tag articles with, saving the changes to a linked metadata Lua table. The same table would contain the display-name of the tag, as well as the reg-ex search string, and the concatenated display-name that's used as input for preloadparams= and for the article list maker. The current system is workable; but yours would be better. :)
I'm not sure how technically possible this is, but I'd like to suggest a couple of improvements on your tagger.
Right now the workflow looks like this: hit edit, then replace the article headers and minor item headers with a template ({{Ib}} in the latter case; still have not written a template for the former case). Put the tags into the templates and save the page. Then hit "Manage tags" and submit what you've put together, without modifying input (otherwise, #jump won't work).
It'd be better if one could mouse over a header and it would change color slightly. Click, and you get a dialog box: here are the tags; do you want to add tags to this entry? If so, input them here; if the header needs to get converted to {{Ib}} along the way, it can handle that too. Click save and the changes in tags are sent to the Lua list.
We can handle the aliasing problem this way: as you input an entry a drop-down box comes up which tells you which tags match the input you have entered so far. So I enter arb and after a pause it brings up arbitration report and arbitration committee as possible options. ResMar 21:07, 21 April 2015 (UTC)
@Resident Mario: I like these thoughts. :) This is going to be a lot of code to write, though - I'll have to actually use my to-do list for once. Could you give a rough priority for each bit of code that needs writing? I should probably get the important stuff done first. — Mr. Stradivarius ♪ talk ♪ 21:14, 21 April 2015 (UTC)
Our primary task right now is to get the system completely worked out, at least in design, and to generate as complete as possible an initial list of tags for the Python script to pick up before we start manual processing. So, it makes sense to focus on the indexing scripting now. Also, further modifications to the tagger will depend in large part on whether or not you go through with a fully Lua data-table.
And while you finish up with the tagger I can go around talking anyone that will listen into contributing missing pieces to the tag-list. ResMar 23:34, 21 April 2015 (UTC)

Voter template fireworks[edit]

Did you change the default output for the string count module? The voter template now explodes, unfortunately, something that was definitely not true last I worked with it. Maybe you ought to deploy that Lua version you were working on (low priority, though). If it breaks after just a month it's not really tenable. ResMar 04:47, 22 April 2015 (UTC)

Tech News: 2015-17[edit]

15:30, 20 April 2015 (UTC)

Re: User:UBX @ zh:User talk:Liangent[edit]

Done. Sorry for the problem. Fortunately there isn't a bot tagging user pages of non-existent account for CSD U2 here (while there is such a bot on zhwiki...).

Replying here in case you're coming to zhwiki less frequently. Liangent (talk) 11:33, 22 April 2015 (UTC)

Thank you! — Mr. Stradivarius ♪ talk ♪ 11:36, 22 April 2015 (UTC)
That account is global-locked :( Liangent (talk) 15:53, 23 April 2015 (UTC)
I'm familiar with the steward who locked it, and it was locked soon after I created the global account. Maybe I asked him to do so? I forgot the exact situation at that time anyway :/ Liangent (talk) 15:56, 23 April 2015 (UTC)
@Liangent: Ah, I didn't realise it was locked... that complicates things. Could you ask the steward involved? Or if that's undesirable, I can make a request at m:Steward requests/Global. Best — Mr. Stradivarius ♪ talk ♪ 17:11, 23 April 2015 (UTC)
I found a steward on #wikimedia-stewards to unlock it and I've got its local account created. Thanks Shanmugamp7. Liangent (talk) 07:08, 24 April 2015 (UTC)
Thanks again, both of you. :) — Mr. Stradivarius ♪ talk ♪ 08:44, 24 April 2015 (UTC)

Please comment on Template talk:Infobox person[edit]

The feedback request service is asking for participation in this request for comment on Template talk:Infobox person. Legobot (talk) 00:02, 23 April 2015 (UTC)

Japanese help[edit]

I believe that I promised to let you know about requests like this: w:ja:Wikipedia‐ノート:ビジュアルエディター. Japanese is one of the top priorities (perhaps it is even fair to say that it is the #1 priority), but it is not an emergency. If you have time to look into this type of testing any time during the next couple of weeks, that would be helpful. Thank you for your help, as always. Whatamidoing (WMF) (talk) 04:59, 23 April 2015 (UTC)

The Signpost: 22 April 2015[edit]

Please comment on Template talk:Editnotices/Page/Wikipedia:Requests for permissions/Rollback[edit]

The feedback request service is asking for participation in this request for comment on Template talk:Editnotices/Page/Wikipedia:Requests for permissions/Rollback. Legobot (talk) 00:08, 25 April 2015 (UTC)

May need semi_pp at Buckley[edit]

Not sure what's going on there now or why, but it's very disruptive. Can you do a semi-pp?? Thx AtsmeConsult 17:16, 25 April 2015 (UTC)

@Atsme: At Buckley? No-one's edited it since January... — Mr. Stradivarius ♪ talk ♪ 20:19, 25 April 2015 (UTC)
Please accept my apologies, Mr. S - I forgot to include the wiki link. William_F._Buckley,_Jr. I am (little by little) prepping it for a GA review. AtsmeConsult 20:48, 25 April 2015 (UTC)
There's only one recent vandalistic edit, so I don't think it really needs protecting. — Mr. Stradivarius ♪ talk ♪ 20:57, 25 April 2015 (UTC)

Tech News: 2015-18[edit]

15:11, 27 April 2015 (UTC)

Please comment on Template talk:Cite isbn[edit]

The feedback request service is asking for participation in this request for comment on Template talk:Cite isbn. Legobot (talk) 00:11, 28 April 2015 (UTC)

Support request with team editing experiment project[edit]

Dear tech ambassadors, instead of spamming the Village Pump of each Wikipedia about my tiny project proposal for researching team editing (see here:, I have decided to leave to your own discretion if the matter is relevant enough to inform a wider audience already. I would appreciate if you could appraise if the Wikipedia community you are more familiar with could have interest in testing group editing "on their own grounds" and with their own guidance. In a nutshell: it consists in editing pages as a group instead of as an individual. This social experiment might involve redefining some aspects of the workflow we are all used to, with the hope of creating a more friendly and collaborative environment since editing under a group umbrella creates less social exposure than traditional "individual editing". I send you this message also as a proof that the Inspire Campaign is already gearing up. As said I would appreciate of *you* just a comment on the talk page/endorsement of my project noting your general perception about the idea. Nothing else. Your contribution helps to shape the future! (which I hope it will be very bright, with colors, and Wikipedia everywhere) Regards from User:Micru on meta.

British Foreign Office 'hardest languages' article[edit]

Did you manage to track this down eventually? I would love to have a look at it if you did...Coolazice (talk) 11:55, 30 April 2015 (UTC)

@Coolazice: I don't remember this article. Where did you see me mention it? Knowing the name or seeing the context would help, I think. — Mr. Stradivarius on tour ♪ talk ♪ 20:44, 1 May 2015 (UTC)

This was the original context.Coolazice (talk) 07:55, 2 May 2015 (UTC)

Please comment on Wikipedia:Village pump (proposals)[edit]

The feedback request service is asking for participation in this request for comment on Wikipedia:Village pump (proposals). Legobot (talk) 00:04, 1 May 2015 (UTC)

The Signpost: 29 April 2015[edit]

Tech News: 2015-19[edit]

15:16, 4 May 2015 (UTC)