User talk:Lightmouse/Archives/2009/February

Date script edit summaries
Hello Lightmouse, I was wondering if you could shorten the edit summaries automatically added by your date script (specifically by looking at alternatives to the link targets you've chosen). For instance, here's one possible fix: script-assisted date/terms audit; see mosnum, wp:overlink to script-assisted date/terms audit; see mosnum, wp:overlink which by itself shaves 21 characters off the length of the inserted edit summary. Setting up a shortcut link to your script (maybe something like WP:DATESCRIPT, which would save another 24 characters) would serve to further shorten the length of the summary text and provide users with more space for their summary. It would aso be nice if the script would warn if the edit summary's insertion would exceed the maximum length for edit summaries. Thanks in advance! 「ダイノ ガイ 千 ？！」(Dinoguy1000) 17:58, 31 January 2009 (UTC)


 * I have shortened the edit summary. You won't see the change until you clear your cache. I haven't added a warning because I don't know how. I hope that helps. Lightmouse (talk) 11:28, 1 February 2009 (UTC)


 * Thanks. The warning should be a simple matter of comparing the provided summary length against the length limit (which is 200 characters according to Help:Edit summary). If you want to look into implementing a warning, you could try talking to User:Cameltrader, whose Advisor script includes such a feature, for advice and assistance. 「ダイノ ガイ 千 ？！」(Dinoguy1000) 19:03, 2 February 2009 (UTC)

Notify
AKAF (talk) 12:01, 2 February 2009 (UTC)
 * Also see Wikipedia talk:Requests for arbitration/Date delinking/Workshop, an editor removed almost every instance of your "back off" comment. Dabomb87 (talk) 03:42, 5 February 2009 (UTC)

Wikipedia_talk:Requests_for_arbitration/Date_delinking/Workshop
If you see the above link, you'll see there's been some discussion about Earle Martin removing your comments. I've warned him for it and I just wanted to let you know that you're free to readd them if you so wish and they won't be removed again.  Ryan Postlethwaite See the mess I've created or let's have banter 15:03, 5 February 2009 (UTC)


 * Thanks. I try to stay away from there because a large proportion of the debate is ad hominem. Somebody suggested to me that failing to express a view might be misinterpreted in a bad way. So I expressed my view and that was also misinterpreted in a bad way. If my comments are restored by somebody other than myself, that would be nice. But I see there are still claims that my comments are disruptive and it is best if I don't restore them myself. I should have followed my initial instinct and stayed away. Lightmouse (talk) 16:18, 5 February 2009 (UTC)
 * Your comment on WT:AC/N was moved. The Arbitration committee noticeboard is just for Arbitration committee announcements.--Tznkai (talk) 19:54, 5 February 2009 (UTC)

Script deactivated?
Hi Lightmouse, I'm aware there is an injunction against using the script, does that mean you've turned it off? I installed it to look at the edits it would produce and have re-cached the browser but I'm not getting the menu choices underneath "What links here". Is that the status quo currently? Not sure if I'm doing something wrong. I don't intend to apply any changes with it until the ArbCom decision is rendered or they lift the injunction. Cheers, ⋙–Berean–Hunter—►  ((⊕)) 17:23, 5 February 2009 (UTC)


 * Note that the injunction wording is very specific and not all use of the script is banned. It isn't turned off. So you must be doing something wrong. The menu choices only appear when you have a page in edit mode. I hope that helps. Lightmouse (talk) 17:27, 5 February 2009 (UTC)
 * I'm looking per this request, and have that page open in edit mode right now in another tab but "Related Changes" is what is underneath "What links here". I'm using the Modern skin on Firefox in Ubuntu. I already use Twinkle, friendly, HotCat, etc. My monobook for reference. I've tried re-caching multiple times and even logged out and rebooted the computer to make sure. It is good to hear that it isn't completely restrained by injunction. ⋙–Berean–Hunter—►  ((⊕)) 17:37, 5 February 2009 (UTC)

That is on secure.wikimedia.org. Try http://en.wikipedia.org/wiki/List_of_American_Civil_War_battles I hope that helps. Lightmouse (talk) 17:41, 5 February 2009 (UTC)
 * I just verified that if you are logged into the secure site, the secure link does work, and the script was able to delink/fix the dates on the page in question. If it's not a problem of not being logged in, it could be a problem with one of your other scripts having a bug, and causing the entire monobook to crash. Plastikspork (talk) 17:44, 5 February 2009 (UTC)
 * Aha, it is the skin! (Those are both the same Wikipedias above, I'm simply logged in through the secure server)..I just tried switching out of the "Modern" skin and it works (lots of menu choices now). At least I know it isn't me now...Thank you, <b style="color:#00C">⋙–Ber</b><b style="color:#66f">ean–Hun</b><b style="color:#00C">ter—►</b>  (<b style="color:#00C">(⊕)</b>) 17:49, 5 February 2009 (UTC)
 * I think you'd need to add it to your modern.js instead then. but keep the injunction in mind. – xeno  ( talk ) 17:55, 5 February 2009 (UTC)
 * Yes, thank you, that is the proper fix...works fine in Modern skin now. I'll go review the injunction again now. Cheers, <b style="color:#00C">⋙–Ber</b><b style="color:#66f">ean–Hun</b><b style="color:#00C">ter—►</b>  (<b style="color:#00C">(⊕)</b>) 18:05, 5 February 2009 (UTC)

Odd error
Just wanted to let you know about this edit to Boardman, Ohio, apparently some coding error with your AWB. I've changed the convert template so that it converts the right amount. Nyttend (talk) 18:50, 5 February 2009 (UTC)


 * Yikes. That is a silly error due to copying and pasting code. I will fix it. Thanks you very much. Lightmouse (talk) 18:51, 5 February 2009 (UTC)

Conversion of acres
Just a note to say that the usual conversion of acres is to hectares (ha) and not square metres (m2). Mjroots (talk) 06:54, 6 February 2009 (UTC)

Conversion of bell weights
Hi Lightmouse. I have just done a partial revert on your convert units change to. It is traditional for the weights of bells made or installed in the UK to be specified in the old cwt/quarters/lb units. It did not make sense to convert only the lb part of the weight. Best wishes. Oosoom Talk 10:46, 6 February 2009 (UTC)


 * Thanks. You are quite right, it doesn't make sense to do a partial conversion. Is it possible for you to provide a complete conversion into kilograms? Lightmouse (talk) 10:49, 6 February 2009 (UTC)


 * Well, the calculation is 112xcwt + 28xqtr + lb. According to Dove's Guide to Bells, American readers might also prefer the weight in total lbs as well. I wonder how many articles have/will mention bell weights. There are over 5,000 churches with bells. Oosoom Talk 11:05, 6 February 2009 (UTC)

There is nothing to stop other people adding stones or shekels, or whatever later. My primary concern is accessibility for the huge number of metric readers. If it has a kilogram value, that will be an big improvement worthy of the effort. Lightmouse (talk) 11:12, 6 February 2009 (UTC)

AWB conversion runs
Hi, Lightmouse, I've got a question for you. You just added some conversion templates/etc. to Roon class armored cruiser (here). My question is, since the figures for the gun sizes are already converted earlier in the same paragraph, is there a way to tweak your AWB parameters to check for already-present conversions and not suggest adding redundant ones? I don't use AWB, so I don't know if that's possible. If not, could you be a little more careful on your runs? Thanks and regards, Parsecboy (talk) 13:42, 6 February 2009 (UTC)

I think it is difficult, if not impossible for the code to be aware of previous conversions. At least, with my current skills. I will try to watch out for this, as you suggest. I have updated the paragraph to reduce duplication of values and I think that improves the flow. With less duplication of values, there will be the secondary benefit of reduced conversions by humans with or without scripts. Thanks for the feedback. Lightmouse (talk) 13:57, 6 February 2009 (UTC)

Conversion of taxation hp
I have had to change back some of your recent conversions.

On some of these you have converted tax or fiscal hp to kW. This doesn't work as these hp figures was purely for taxation purposes and had no relationship with engine output power.Malcolma (talk) 13:25, 6 February 2009 (UTC)

Ah. I didn't know that. I bet a lot of readers don't know that. Perhaps ordinary 'hp' and 'hp (tax)' should be distinguished. What do you think? Lightmouse (talk) 13:28, 6 February 2009 (UTC)


 * It is usually so that taxation is with capital letters HP and horsepower should be hp --<span style="font:bold 11px Arial;display:inline;border:#151B8D 1px solid;background-color:#DFDFDF;padding:0 3px 0 4px;">Typ932 T&middot;C 12:57, 7 February 2009 (UTC)

Grand Prix motorcycle racing
Hi there,

I've just undone your edits to Grand Prix motorcycle racing, as we have a consensus (see article talk page) that these do not have a space between the number and the cc. Whilst this is in opposition to the MOS, in this case they are specific motorcycle category names used by the governing body (FIM), rather than simply a measure of capacity. The same will apply to other motorcycle racing pages. I don't believe there would be a problem adding a space on article about motorcycles (or cars) generally. Hope that makes sense! --Ged UK (talk) 13:31, 6 February 2009 (UTC)


 * It seems a little odd to me and I am sure you will get other editors coming along and doing the same thing. But I don't particularly mind. Thanks for letting me know. Lightmouse (talk) 13:32, 6 February 2009 (UTC)


 * Aye, well, it is a little odd i grant you, but that's the way the consensus went. Personally i like it because i don't like spaces between numbers and symbols, but that's just mean. In this case it's definitly right! If other editors come along, i'll explain it to them too. :) --Ged UK (talk) 13:40, 6 February 2009 (UTC)


 * It may be worth your time to notify editors on the MOS' talk page, in case it's worth an addition. 「ダイノ ガイ 千 ？！」(Dinoguy1000) 19:24, 6 February 2009 (UTC)

Miles at sea
Hi. I would not be as quick as you to assume that "miles" in ship articles, when based on naval sources, are statute miles (1.61 km) by default, rather than nautical (1.85 km). E.g., , ,. —WWoods (talk) 19:36, 6 February 2009 (UTC)


 * One of the problems with the old system is that ambiguity is concealed. For some readers, the word 'mile' means statute, for others it means 'nautical', for others is means 'Scottish'. The author cannot blame the reader for the original ambiguity. The benefit of metric units is that it removes the concealed ambiguity. The benefit of the conversion template is that it is easy to change. I would be delighted if somebody improved the articles by eliminating the original ambiguity. Perhaps this could be discussed in one of the project talk pages, or at mosnum. Lightmouse (talk) 10:11, 7 February 2009 (UTC)


 * The trouble is, the ambiguity is real. I think those are nautical miles, but I don't know. Therefore it seems better to me not to tacitly assert that they're statute miles by converting them as such. If you still want to convert them, why not assume they're nautical miles and use that conversion?
 * —WWoods (talk) 18:07, 7 February 2009 (UTC)

Hope
I have no longer been following the complicated delinking arbcom case, but I hope you are doing well and not feeling put down by it all. My interactions with you have always been extremely pleasant, and I have enjoyed you script immensely (although now I am afraid to use it!) I'm hoping arbcom will see the light and understand that the problem is not you or your script. The problem is that there is no good rationale for linking to random years. Regards, &mdash; Mattisse (Talk) 15:28, 7 February 2009 (UTC)


 * Thank you. One kind comment like that is antidote against a thousand hostile comments. I really appreciate it. Lightmouse (talk) 15:36, 7 February 2009 (UTC)

Issue with commas in unit conversion
I made this edit to fix an error in unit conversion on Oroville Dam. The commas in the original value were producing 'Expression error: Unrecognised punctuation character ","' in the converted value. Removing the commas fixed it without affecting how the original value was displayed. Either your script will need to strip commas in the original values or the code which performs the actual unit conversion will need to be updated to handle them. —Preceding unsigned comment added by DonovanHawkins (talk • contribs) 18:45, 7 February 2009 (UTC)


 * Thank you. I will investigate and fix the problem. Thanks for the feedback. Lightmouse (talk) 19:44, 7 February 2009 (UTC)

The Palace Hotel On 1st St and Cook Ave. in New Mexico
Hi,Im new to this so please bear with me. I've seen your name on the discussion list and was wondering if you care to assist me in any way.Please understand that I take no offense if this is not possible.

I am looking for information on the Palace Hotel located in the Historical District in Raton. It is listed as number 23 and is located on the corner of 1st street and Cook ave. Between 1975-77. I was a teenager and live and worked there. I am now researching the building's history and appreciate anything you can provide.

Thank you in advance. —Preceding unsigned comment added by Susanjxp (talk • contribs) 23:36, 7 February 2009 (UTC)


 * I am sorry I can't help you. Lightmouse (talk) 10:50, 8 February 2009 (UTC)

Question
Hi Lightmouse, hope you are doing well. About a month ago, I created this proposal as a way to settle the dispute about when to link dates. After the Arbcom case picked up steam, I sort of left it by the wayside. However, recently, Greg L seized on the idea with much gusto, and others have warmed to it as well. Greg asked if it was possible for you to configure your bot (or script) to those guidelines, with a reasonably low false positive rate. I completely understand if it is not possible, as some of the proposals are very detailed, but it would be interesting it have your feedback all the same. Cheers, Dabomb87 (talk) 05:02, 7 February 2009 (UTC)


 * Part of it is easy:
 * Where an article title is about a date, it is easy i.e. your examples: 1789, January, 1940s, Sunday.


 * Part of it is difficult, if not impossible:
 * Holidays: It is difficult for a bot to know what is a holiday. You gave the example of April Fools' Day as a holiday, but I would not have guessed that it was. The same applies to your other two examples. I don't want to get into a dispute about which days are holidays in which regions and religions. This could be solved by having a list of articles for the bot to avoid.
 * 'Global' or 'historical' context. It is difficult for a bot to decide. This could be solved by having a list of articles for the bot to avoid.
 * Birth and death dates. It is difficult for a bot to determine that a date is a birth or death date. This could be solved by having a list of articles for the bot to avoid.
 * I think your idea has a future. I hope that helps. Lightmouse (talk) 10:29, 7 February 2009 (UTC)

There is absolutely no consensus that dates of birth and death should be linked. This is a zany idea put about by those who want a foot in both camps. Since most visitors and, indeed, Wikipedians, do not consult MOSNUM et al, but follow what they see in existing articles, linking the opening two dates in our many biographical articles will result in many many editors' believing that all dates should be autoformatted. In addition, extended blue-wash right at the opening of an article typically runs up against other, high-value links; sometimes it places them directly adjacent to these low-value date-links. It is a bad idea indeed, and I would be one of many people to object to it. Tony  (talk)  13:41, 7 February 2009 (UTC)


 * I never proposed that birth and death dates be linked. If you see, the proposal merely says "under discussion". Dabomb87 (talk) 14:14, 7 February 2009 (UTC)


 * Tony, can you point me to a study that shows that date links "devalue" other "high value" links? I see this assertion made repeatedly (here, at MOSNUM and at the ArbCom case) but I've never seen anything definitive and unbiased to back it up. —Locke Cole • t • c 12:07, 8 February 2009 (UTC)
 * Any grant body that funded a study for that purpose would be laughing stock, since it doesn't take Einstein to realise such an obvious fact. But now you raise it, I suspect that the field of perception (within psychology) is replete with data that show an analogous dilution effect over a number of modes—one of them colour. I might follow this up with User:Holcombea, a notable scientist in this field, although it hardly seems necessary under the circumstances. Tony   (talk)  12:39, 8 February 2009 (UTC)


 * If I understand the issue correctly, it is a matter of eyes trying to detect a signal within noise. That is why animals make themselves look the same as the background. If you raise the noise, the signal detection rate goes down. It is not a linear effect and I believe there can be reversals when signals are extremely low (e.g. detecting bombs in luggage, rare cancers in medical images) but that doesn't apply here. There are plenty of resources on signal to noise theory available for anyone that doubts that noise causes problems in signal detection. Lightmouse (talk) 12:52, 8 February 2009 (UTC)


 * Yet but if there's no quantifiable impact on our readers it seems we're much ado about nothing. Have readers complained about the date links impacting their ability to recognize non-date links? Have they complained about the impact of "trivia" articles being linked next to other highly relevant links? I guess my question is two fold: where does this idea come from, and how did it spring to mind? Surely someone complained somewhere to set this off? —Locke Cole • t • c 15:26, 8 February 2009 (UTC)


 * But how are the "readers" to complain? The millions of "readers" each day of Wikipedia are almost entirely unregistered and do not have a clue how to "complain" to Wikipedia if they wanted to do so. Even for a "member of the Wikipedian community", it is difficult to know where to "complain" about some things. How to complain? Submit a "policy" suggestion somewhere? Post on AN/I? Complain on various talk pages and have an RFC? Go to ArbCom? From my experience reviewing hundreds of GANs, the vast number of Wikipedian editors do not prefer date linking to years. However, there is no data regarding the views of Wikipedia editors in general because there is no means of obtaining it. In any case, this does not apply to Wikipedia's vast, anonymous, worldwide readership. &mdash; Mattisse (Talk) 15:57, 8 February 2009 (UTC)


 * Exactly. Our readers do not "complain" about redundancy, poor grammar and organisational problems in our writing; nor copyright infringements in our images and sound bites. This is irrelevant to the making of a superb information source. Tony   (talk)  16:00, 8 February 2009 (UTC)


 * The original question was whether eliminating low value links has an effect on high value links. The response was that as you increase the noise, the signal to noise ratio falls. Human performance is affected by signal to noise ratio. I assume that we are in agreement about that. If we aren't in agreement, then it is such a big challenge to the science that it belongs on another page, not my talk page.
 * We now have an entirely new thread about user complaints. That is nothing to do with the science of signal to noise ratio. Why are we talking about this on my talk page? Lightmouse (talk) 16:35, 8 February 2009 (UTC)


 * Because Tony states these things as fact on your talk page, then runs with them. At least I now understand that he has no direct complaints from our readership to base his claims on, I wasn't aware of that. We're in this situation because of his assumptions. —Locke Cole • t • c 09:01, 10 February 2009 (UTC)


 * OK, I hope that is the end of this thread on my talk page. Lightmouse (talk) 09:56, 10 February 2009 (UTC)

Dabomb87, 'Category:Births by year' and 'Category:Deaths by year' are relevant to the debate about birth and death years. I can't see any mention of these categories. I didn't want to mess up your page by adding something myself. Could you mention those please? Lightmouse (talk) 14:41, 7 February 2009 (UTC)


 * Linking dates of birth? I missed that *under discussion* biz in Dabomb87’s Summary. The linking of dates of birth was the primary reason we are all bogged down in this holy war. It’s time to break out of unnecessary logjams. Dabomb87’s summary is supposed to be a summary of the RfC consensus and I see no basis for thinking the RfC results says that the linking birth dates is allowable. If one is reading up on Angela Lansbury, who is an actress born in 16 October 1925, and you click on that year (or God forbid, the day), there is nothing in the 1925 article that is germane and topical to the subject of “Angela Lansbury” except for her birth date; the reader already knew that before clicking the link. Again, links should be topical and germane to the subject matter and shouldn’t be used as an invitation for what editors think might be a fun treasure hunt on matters entirely unrelated to the subject. Greg L (talk) 16:58, 7 February 2009 (UTC)
 * I put that little note there after a discussion with Locke Cole on the talk page. Clearly, I was wrong. Dabomb87 (talk) 18:09, 7 February 2009 (UTC)


 * That explains a lot. No harm. Given that date linking is such a gray area, your very comprehensive, detailed proposed guideline is just the sort of specificity that might resolve this dispute. I note above that Lightmouse is saying that there are several classes of dates where date linking would be appropriate and it would be quite difficult to avoid those with a bot. Does anyone have an idea how many there would be of such appropriately linked dates as compared to all the ones that need to be delinked? If it is wildly lopsided, then it makes far more sense for a bot to go do its thing and manual re-link. Greg L (talk) 19:22, 7 February 2009 (UTC)

Greg, my comments should not be considered as endorsement of date links. I am merely suggesting boundary rules for an unsupervised bot. By definition, it has to be much more cautious than a human. Rather like archaeologists getting a local firm with a motorised digger to remove 80% of the top soil, then students using trowels for 80% of whats left, then archaelogy specialists using toothbrushes. In the end, only the important stuff will remain. Lightmouse (talk) 19:57, 7 February 2009 (UTC)


 * If you want to estimate the number of articles in need of delinking, one method might be to look at articles that link to todays date and see for yourself how many look like bot fodder. Lightmouse (talk) 20:17, 7 February 2009 (UTC)


 * Well that was an interesting experiment. I did as you suggested and looked at the first ten links and the last ten links (a total of 20). In every single case where the date was used in body text, it was just a plain old link to the date for the sake of autoformatting and/or linking to dates for the sake of linking to dates (where the link is not topical or germane to the subject matter). There were about five cases in the last set of ten that were all like these two: Luke McLean, and Marian Pop. They have some sidebars with “this was retrieved on” or “this was fetched on” templates. I assume it would be a no-brainer to avoid those. I am concluding, from these 20 semi-randomly chosen articles, that if you can avoid the sidebars, then the number of false-positives would be a very small portion (comparatively speaking) to all the links that properly need to be de-linked. Do you concur? Greg L (talk) 03:24, 8 February 2009 (UTC)

I don't know what you mean by 'sidebar'. I had forgotten that the wikiterm is “info boxes”. In print, all those sort of things are called sidebars. Greg L (talk) 16:25, 8 February 2009 (UTC) In summary, I can't see any dates in those two articles that require links. I would be interested to hear the views of the citation people, they have been working on date linking policy for some time and were going to update citation templates Real soon now. Lightmouse (talk) 11:18, 8 February 2009 (UTC)
 * I looked at your example of Luke McLean. It had the term 'Retrieved on' followed by the unlinked text '8 February 2009'. So it is not a special case. Perhaps you are talking about the date '2008-11-08' prior to it. That is linked but as a human editor, I would delink it. That doesn't seem particularly special to me either. In in the infobox, it contained '29 June 1987' (not linked) and '8 February 2009' (not linked). I can't see anything special about those.
 * I looked at your example of Marian Pop. It didn't contain the term 'Retrieved on' or 'Fetched on'. In in the infobox, it contained 'January 15, 1990' (not linked) and 'February 7, 2009' (linked). I can't see anything special about those.


 * Just to clear something up: I think dabomb's "summary" was—in its frame—an excellent piece of work. It's the kind of thing I might have attempted myself (perhaps not as well). I held off assessing the summary in my own mind until I'd had a look at the long-winded, voluminous RfCs at issue. It was only when I did that I realised that the data were contaminated in the first place, in some cases fatally. This is why my analyses targeted an earlier "link in the chain". Tony   (talk)  11:57, 8 February 2009 (UTC)


 * It seems we are homing in on a workable, specific solution to propose to ArbCom for the arbitrators to consider. My question of you, Lightmouse, is this: If you were to take the first ten and last ten articles that link to today’s date and apply Lightbot to them in a way that is as compliant as you can reasonably make it with Dabomb87’s proposed guideline, how many false-positives would there be? I note that some of yesterday’s articles contained multiple date fragments (both years and days) per article. So even if the false-positive count is one or two, the number of properly de-linked dates would likely be something on the order of 24. I’m not seeing a problem at all here if that would prove to be the true ratio across a larger population; it would be far, far more laborious to manual de-link dates than it would be to restore the wildly smaller number of false positives. Greg L (talk) 16:25, 8 February 2009 (UTC)

The first ten articles that link to todays date are:
 * April - would not be parsed by bot: all 12 'month' articles would be avoided
 * August - would not be parsed by bot: all 12 'month' articles would be avoided
 * April 6 - would not be parsed by bot: all 366 'month+day_number' articles would be avoided
 * April 12 - would not be parsed by bot: all 366 'month+day_number' articles would be avoided
 * April 15 - would not be parsed by bot: all 366 'month+day_number' articles would be avoided
 * April 30 - would not be parsed by bot: all 366 'month+day_number' articles would be avoided
 * August 22 - would not be parsed by bot: all 366 'month+day_number' articles would be avoided
 * August 27 - would not be parsed by bot: all 366 'month+day_number' articles would be avoided
 * August 6 - would not be parsed by bot: all 366 'month+day_number' articles would be avoided
 * August 9 - would not be parsed by bot: all 366 'month+day_number' articles would be avoided

The last ten articles that link to todays date are: I hope that helps. Your point about 'sidebar' and 'infobox' being synonyms noted. Lightmouse (talk) 18:14, 8 February 2009 (UTC)
 * Jean-Achille Benouville - All linked dates would be delinked. I count 2 linked dates and several unlinked dates.
 * Nicholas Byron Cavadias - All linked dates would be delinked. I count 1 linked date and several unlinked dates.
 * Kazutsugi Nami - All linked dates would be delinked. I count 9 linked dates and several unlinked dates.
 * List of Cabinets of Iceland - All linked dates would be delinked. I count 93 linked dates and 1 unlinked date.
 * Murray Takes It To The Next Level - All linked dates would be delinked. I count 2 linked dates and 3 unlinked dates.
 * List of The Veronicas tours - All linked dates would be delinked. I count 89 linked dates and several unlinked dates.
 * Institute for Health Freedom - All linked dates would be delinked. I count 10 linked dates and no unlinked dates.
 * 2009 in British music - would not be parsed by bot: all ' in ' articles would be avoided
 * Il Giorno (newspaper) - All linked dates would be delinked. I count 2 linked dates and several unlinked dates.
 * The Fat Tail: The Power of Political Knowledge for Strategic Investing - All linked dates would be delinked. I count 3 linked dates and several unlinked dates.

'Holidays'

 * When I say "holiday", I mean an annual event that occurs on the same day every year. Dabomb87 (talk) 14:16, 7 February 2009 (UTC)

The requirement to avoid 'annual events' is a larger scope for exclusion than holidays. But perhaps this is such a simple issue, it isn't a problem. When we talk about exclusions from bot scope, we have two aspects: I hope that helps. Lightmouse (talk) 14:41, 7 February 2009 (UTC)
 * links *within the article*
 * A bot will remove links within articles about annual events. It has no way of knowing that Burning Man is an annual event. It will delink dates in that article, just as it would in Burning Wheel. If such articles are to be excluded, then it needs to be given a list. It can also work with simple rules (e.g. any article with ' Day' in the title - note upper case 'D').
 * links *to an article*
 * A bot is unlikely to remove links to annual events. This is not a deliberate action, it is just how it works i.e. the software has not been created to find square brackets around text 'Burning man' or 'April Fool's Day'.
 * Here, I am only talking about links to, say, January 1 in New Years Day or December 25 in Christmas. I wasn't talking about removing links to holidays themselves. Dabomb87 (talk) 18:10, 7 February 2009 (UTC)
 * I suppose I could provide a list. Dabomb87 (talk) 18:11, 7 February 2009 (UTC)

An alternative to providing a list of articles to avoid is for Lightbot and/or Lightmouse's script to honor the Bots template. The documentation for the template explains how bot code can be modified to honor the template. --Gerry Ashton (talk) 18:31, 7 February 2009 (UTC)


 * I don't know how the script could do it. But Lightbot could do it with that template or any other. Lightmouse (talk) 20:05, 7 February 2009 (UTC)
 * That would just be licensing anyone who wants to ignore the MoS and do things their own way to slap a ((bots)) template on all the articles they feel they 'own'. A related but much more selective approach is the suggestion I've made in the RfAr workshop: a template that could be used as a protective wrapper on any individual linked date, so that the unlinking bot would bypass it. The template syntax would require a reason to be provided, so other editors could discuss whether the protection was desirable, and future editors could understand the reason for protection without having to comb through reams of old discussions. Colonies Chris (talk) 13:34, 8 February 2009 (UTC)
 * Further, I believe that Chris probably has in mind not any old reason pasted in from some rotated list of generic "reasons", but one that specifically relates to the actual context of the article. Is that right, Chris? Tony   (talk)  13:58, 8 February 2009 (UTC)
 * That's right. The template would be to protect specific special cases that can't be readily categorised in a way that the bot could be programmed to avoid. (And to avoid article 'ownership' issues, claims such as "local consensus to do things differently here" would need to be supplemented with evidence that at least two active editors in that field support the supposed consensus). Colonies Chris (talk) 16:57, 8 February 2009 (UTC)
 * I want to be even-handed about this. Proposals to keep date links in the hope that some day date autoformatting might be improved carry no weight with me, because there is no clear plan on how to do it, and no commitment to implement the plan. Similarly, a proposal to wrap individual dates carries no weight with me until there is a clear enough plan that the template can be written, and a commitment that the bots approval group will not approve any date-delinking bot that does not honor the new template. --Gerry Ashton (talk) 17:17, 8 February 2009 (UTC)
 * What's "active editors in that field" supposed to mean and who decides whether they exist? Of course, you entirely miss the point about article-consensus prevailing over the mere recommendations of the Manual of Style, and your proposal would only lead to more edit warring.  Tennis expert (talk) 23:28, 8 February 2009 (UTC)


 * I think this is unworkable: two "active" editors "in the field"? Never would it have been so easy to generate supposed consensus. That's Tennis expert and one other person he finds, overruling all of his colleagues at the WikiProject. Naaaah. Tony   (talk)  23:53, 8 February 2009 (UTC)
 * Ah, now WikiProjects are relevant to you. Thanks for finally recognizing that the Manual of Style is merely a set of recommendations that may be ignored by local consensus.  We're making progress.  Tennis expert (talk) 00:41, 9 February 2009 (UTC)
 * Incorrect. Tony said Tennis expert and AN Other do not constitute 'local consensus'. TE do not even have the support of his fellows at WP:Tennis even when he is editing "normally", as there are ample comments which testify to this on his own talk page. Ohconfucius (talk) 01:46, 9 February 2009 (UTC)
 * The requirement for two active editors isn't intended to be decisive, it's a minimum to have such a claim even taken seriously. I make this proposal in the full knowledge that Tennis expert can't find even one other editor to support his spurious claims of 'local consensus'. Could that be why he's opposed to it? Colonies Chris (talk) 08:26, 9 February 2009 (UTC).

The Gram(me)y awards
Thanks for the tip. I'm sending you this direct because the archive is closed, and I have no urgent need to start a new topic on the overloaded current page as opposed waiting for someone else to raise the question anew.

I have a slight general bias towards British spelling and usage since I grew up in London, moved to Rhode Island when I was six, moved back when I was eight, and moved back to the States for good when I was eleven, at which point I resisted re-Americanization. However there also are many U.S. usages which I prefer on the basis of logic, clarity, ease or style (e.g. NATO over Nato, acknowledgement over acknowledgment). In the case of meter/metre, the need to avoid confusion with meters and micrometers argues for ~metre, and in the MOSNUM discussion of this, someone said that for that reason, ~metre is now the preferred scientific usage. In the case of ~gram(me), I'd think that people (and thus readers) in Anglo-French bilingual countries, of which the most prominent is Canada, would prefer to just use ~gramme and ~metre in English as it's already used in French (e.g. on packages). On the theoretical level, some argue that meter, liter and gram are closer to the original Greek (not written in our alphabet), but after all the French, who did invent the metric system, seem just as deserving of credit. —— Shakescene (talk) 05:34, 9 February 2009 (UTC)

Google Street View bot?
Do you think it would be possible to design a bot that if a landmark has the address listed in the infobox, and the location is covered by Google Street View, that an external link to that location on Street View would automatically be placed on the page? I have been trying to place Google Street View links on the pages of many landmarks, but there are perhaps millions around the world, and I can never get to them all. I don't know of any one else who is actively doing this. Sebwite (talk) 01:04, 10 February 2009 (UTC)


 * I don't know how to do it. But you could ask at Bot requests. Regards Lightmouse (talk) 08:46, 10 February 2009 (UTC)

SI Units
I notice that your bot has corrected the placing of the some of the units at Radar signal characteristics, eg GHz, kHz and km. However, in the same page the units ps are used, but these haven't been corrected and neither have some instances of kHz. Can I suggest that you add this? Terry C (talk) 17:34, 11 February 2009 (UTC)


 * You raise some interesting points. I will try to answer them as best I can:
 * The code has lots of rules to avoid false positives. Unfortunately, that increases the rate of 'misses'.
 * Adding spaces before units is a secondary priority for the code.
 * I have not considered targetting ps before. This is probably because the unit 'pferdestärke' and the unit 'picosecond' have similar symbols.
 * On the basis of your feedback, I can see if I can amend the code to improve it. Or I can create some special code and run it to target these precise issues. I will have a think about it, leave it with me. Thanks. Lightmouse (talk) 11:56, 12 February 2009 (UTC)

Date format
In November you contacted me regarding the use of your tool to change date formats to dmy or mdy etc. Just recently there seems to be a change in the result so that a comma appears in the dmy format, giving 9 February, 2009 rather than the correct format 9 February 2009. Is this a temporary glitch or has there been some significant change of which I'm not aware? Daemonic Kangaroo (talk) 22:39, 9 February 2009 (UTC)


 * The code is updated with from time to time. It is possible that one of the updates has caused that. In response to your feedback, I have made a change that should fix the issue. Please clear your cache and try again. If the problem still exists, please give me an example page and I will investigate further.
 * P.S. A tip is to add User:Lightmouse/monobook.js/script.js to your watchlist. Each time you see it updated, clear your cache. This will ensure that your computer is working with the latest version.
 * Thanks for letting me know. Lightmouse (talk) 23:25, 9 February 2009 (UTC)

That all seems OK now. Cheers. Daemonic Kangaroo (talk) 08:54, 10 February 2009 (UTC)
 * I find it rather irresponsible, Lightmouse, that you neglected to point out that there is currently an injunction against mass unlinking dates in this manner. Please disable the unlinking function of your script while the injunction is active. – xeno  ( talk ) 13:41, 10 February 2009 (UTC)


 * There is no injunction against individual editors using Lightmouse's tool via User:Lightmouse/monobook.js/script.js on individual articles. I asked about this at the delinking Arbcom case. The individual use of user scripts is permitted. This is the way Lightmouse's script is mostly used. It seems like Daemonic Kangaroo was using it this way. &mdash; Mattisse  (Talk) 16:28, 10 February 2009 (UTC)
 * There is an injunction against a mass program and the above user seems to be using it on all articles he is working on, "en-masse". Can you point me to the clarification? – xeno  ( talk ) 16:30, 10 February 2009 (UTC)
 * The injunction specifically mentions "scripts", and as the proposer of the injunction I explicitly had Lightmouses script in mind. —Locke Cole • t • c 17:10, 10 February 2009 (UTC)
 * But I believe I was told that the injunction did not apply to individual editors working on individual articles, not "en masse". Not having Lightmouse's script is a huge burden on us. I believe Karanacs also brought up the importance of Lightmouse's script for this use in the delinking Arbcom. Disabling it would be a huge burden on copy editors such as we are.  &mdash; Mattisse  (Talk) 17:39, 10 February 2009 (UTC)
 * Yes, I've been using it as I work on articles. I'm trying to bring several articles close to FAC status, and they must meet the MOS, thus no date links. Karanacs (talk) 18:14, 10 February 2009 (UTC)
 * Why would featured articles need to meet a MOS guideline which is presently disputed (and under arbitration, at that)? —Locke Cole • t • c 18:23, 10 February 2009 (UTC)
 * The guideline is not under arbitration, rather the strategy of enforcing the guideline is. Arbcom is not deciding whether the guideline is correct or not. Dabomb87 (talk) 23:08, 10 February 2009 (UTC)
 * Yes, the guideline is under arbitration. It is the locus of the dispute (and where the relevant behavioral problems exposed themselves). Many of the proposals on the workshop do deal with the findings of the RFC, consensus on issues, and so forth. Pointing to this indefinitely protected page as being anything other than the wrong version would be investing far too much in it at this stage. FA should not be enforcing MOSNUM in considering articles for promotion. —Locke Cole • t • c 23:14, 10 February 2009 (UTC)
 * Seeing as FA and FL accepted the change a long time ago (and as such, few—if any—articles come to FAC/FLC with linked dates anymore), this is a moot point. Most of those editors (who are active in those areas) don't participate in these discussions anyway and don't know much about the current arbitration or disputes. Dabomb87 (talk) 23:18, 10 February 2009 (UTC)
 * So, you're saying that a local consensus concerning FA and FL makes the Manual of Style irrelevant? Tennis expert (talk) 01:33, 11 February 2009 (UTC)
 * See my comment below. Dabomb87 (talk) 02:42, 11 February 2009 (UTC)
 * I don't see how delinking articles at a slower pace represents any less of a fait accompli strategy, but ok. cheers, – xeno  ( talk ) 19:46, 10 February 2009 (UTC)
 * Perhaps a request for clarification should be made... – xeno  ( talk ) 17:48, 10 February 2009 (UTC)
 * What about edits to articles in which there are no linked dates, and the edits are only done to make the date format consistent? Dabomb87 (talk) 23:06, 10 February 2009 (UTC)
 * The injunction wouldn't have any bearing on that. Have at it. – xeno  ( talk ) 23:07, 10 February 2009 (UTC)
 * I don't think Arbcom is addressing FAC criteria. I believe that FAC sets its own criteria, and so far Arbcom or any other body outside FAC has not interfered with the FAC process. If FAC has consensus within itself that dates are to be delinked, I don't see how that is impinged by the current arbitration. &mdash; Mattisse  (Talk) 23:20, 10 February 2009 (UTC)
 * Ah, a local consensus trumping the Manual of Style.... Interesting.  Tennis expert (talk) 01:31, 11 February 2009 (UTC)

(outdent) No, the local consensus is to follow the Manual of Style. The criteria does not take "disputes" into account. Dabomb87 (talk) 02:42, 11 February 2009 (UTC)
 * And why shouldn't the disputed nature of MOSNUM be considered? —Locke Cole • t • c 06:37, 11 February 2009 (UTC)
 * Not going to say anything further here, but the proper place to take that up is at the talk page of the FA criteria. Dabomb87 (talk) 02:25, 12 February 2009 (UTC)

This thread has drifted. The MOS, RFC, and Arbcom etc are not specific to my talk page. Please take these discussions elsewhere. Lightmouse (talk) 08:37, 11 February 2009 (UTC)

Interesting case
I came across. It breaks the mediawiki feature, and probably very few scripts have regular expressions that would match this case. This quirk stayed around for over a year. Gimmetrow 01:31, 12 February 2009 (UTC)


 * If I understand you correctly, you are talking about a space prior to <close square bracket character>. I used to code to fix that error. However, this is now part of AWB 'General fixes' so I removed the feature from my code. See my comments in the discussion at AWB. Regards. Lightmouse (talk) 11:21, 12 February 2009 (UTC)

Lightbot error
Your bot, User:Lightbot, just converted dates to something else (what I don't know) and caused nice big red text to appear in the dates place. Apparently it thought HP was a unit. Here's the diff. I undid the changes to the years. – Andrew Hampe Talk 04:05, 12 February 2009 (UTC)


 * Thanks for the feedback and providing the diff. There were two errors:
 * it thought that things like '2006 HP' refer to horsepower values and added a convert template. You probably guessed that.
 * it migrated a comma from things like '1984, HP' into the convert template. The convert template didn't like the comma and produced the big red text.
 * The second problem relates to the first. It should be easy enough to fix. I will work on it. Thanks for reverting it and thanks for your clear and informative feedback. Lightmouse (talk) 11:31, 12 February 2009 (UTC)

Proposed at ArbCom
(Perma-link)

Proposal to end this all

Greg L (talk) 04:32, 12 February 2009 (UTC)


 * Thanks. Lightmouse (talk) 11:34, 12 February 2009 (UTC)

Lightbot corrupted a verbatim quote of text inscribed on a monument
Lightbot edited the Thwing page on 24 December, corrupting my verbatim quote of the inscription cut in stone on the face of the monument. I have reverted the two changes.

I've inserted html comments beside them which will warn any human editors not to make any similar change. How should I warn bots like Lightbot to leave this text alone?

Cheers. -- Euchiasmus (talk) 08:32, 14 February 2009 (UTC)


 * No bot will change/convert the units of measure or the dates in the inscription now. Ohconfucius (talk) 09:11, 14 February 2009 (UTC)

Euchiasmus, thanks for bringing this to our attention. Ohconfucius, unfortunately you are wrong. The changes you made (adding a nbsp character) will not guarantee protection. It will protect the dates from Lightbot but neither of us can speak for other bots. Furthermore, it would be a very inefficient bot that failed to convert units just because they contained the nbsp character. There is no such thing as guaranteed protection by all bots but I have added a quote template and many bots including Lightbot try to respect that template. Lightmouse (talk) 12:40, 14 February 2009 (UTC)
 * I stand corrected. Ohconfucius (talk) 14:10, 14 February 2009 (UTC)

Reverted Lightbot edit (restoration of thread from January)
This seems to have been archived from the previous discussion while I was attending to other matters. I am restoring the history here to give my reply proper context, and am replying only in order to clarify my second point (especially since, under the "Temporary injunction" in effect pursuant to Requests for arbitration/Date delinking, the central issue of the original post is, for the time being, rather moot). --Geoff Capp (talk) 13:07, 16 February 2009 (UTC)

I have reverted your bot's edit at Cistercians Abbey in Wąchock because the single link it undid serves to place the article within its proper historical context without adding unnecessary data to the article itself, and because the edit does not actually appear to be within the approved "date fragment delinking" purview of the bot. If you wish to discuss this, please contact me via my talk page of that of the article itself (which is on my watchlist). --Geoff Capp (talk) 11:09, 15 January 2009 (UTC)


 * If I understand your first point correctly it is: 'something that happened within a time period should link to other events in the same time period'. I think it has to be something a lot stronger than that. Your second point is that you couldn't see the relevant part of Lightbot approval for delinking dates. The relevant section is within Bots/Requests for approval/Lightbot 3 "This includes but is not limited to seconds, minutes, hours, days, weeks, fortnights, months, years, decades, centuries, eras, and can be in any sequence or format." I hope that helps. Lightmouse (talk) 11:22, 15 January 2009 (UTC)


 * No, my first point is that, in this specific case, the structure referenced has historical relevance as being an exemplar of the culture and architecture of a specific place (linked) and period of time (unlinked by bot, relinked by me) with which the reader may not be familiar. Just as the article should be linked to the article regarding the specific place, rather than being filled with extraneous detail on said location, it should also be linked—once, unobtrusively—to the article that gives similar background on the relevant time period, rather than being filled with an otherwise unnecessary treatise on the architecture and history of 12 century Europe.  My second point is that, while Bots/Requests_for_approval/Lightbot_3 requested approval to "add, remove or modify links to dates", the approval section notes that this was approved "per previous approval requests" and the previous approvals at Bots/Requests_for_approval/Lightbot_2 and Bots/Requests_for_approval/Lightbot approved use of the bot for delinking only of fragmentary and damaged dates.  This date was neither fragmentary nor damaged, and was completely appropriate in context.  I delete most date links I find myself, so I understand the reason for the bot doing so during this era of date-link deprecation; but one of the reasons why such links are deprecated rather than forbidden is because sometimes they make sense.  This is such a time.  --Geoff Capp (talk) 13:05, 15 January 2009 (UTC)


 * I won't argue with you on the first point. I would rather defer to third party opinion. The approval in Bots/Requests_for_approval/Lightbot_3 did indeed build on the two previous ones. Are you saying that the phrase: "This includes but is not limited to seconds, minutes, hours, days, weeks, fortnights, months, years, decades, centuries, eras, and can be in any sequence or format." is invalid because of what was said in the two earlier approvals? Lightmouse (talk) 13:14, 15 January 2009 (UTC)


 * Regarding the second point, the short answer to your question is "no." What I am saying is that the sentence "This includes but is not limited to seconds, minutes, hours, days, weeks, fortnights, months, years, decades, centuries, eras, and can be in any sequence or format" is valid but (subject to the aforementioned temporary injunction) is limited in its application to "fragmentary and damaged dates."  Such was the mandate granted in Bots/Requests_for_approval/Lightbot (approved, in relevant part, for "Fixing damaged date links that damage autoformatting ... Fixing dates that are damaged by autoformatting [and] Unlinking date fragments) and Bots/Requests_for_approval/Lightbot_2 (approved, in relevant part, to "Make it explicit that the categories of date fragments to be delinked includes solitary years.") This mandate was not expanded by Bots/Requests_for_approval/Lightbot_3, which notes that date delinking was "Approved. per previous approval requests," and so the limitations stand.  Therefore Lightbot should NOT delink any date in any sequence or format UNLESS that date is fragmentary (including solitary years) and/or damaged, even if and when the temporary injunction is lifted, without seeking a further approval to do otherwise.  Therefore also, Lightbot should not alter any validly formed link to 12th century, as it did in the instant case, nor to any other century page, as such links are not solitary years, are not fragmentary, and neither damage nor are damaged by autoformatting.  Please do let me know if this is still unclear.  --Geoff Capp (talk) 13:07, 16 February 2009 (UTC)

Proposal about bot deflagging at Village Pump
Hi, you may have seen this already, but I thought I'd let you know just in case. Cheers, --Goodmorningworld (talk) 16:14, 20 February 2009 (UTC)

Lightbot misfire
Hi Lightmouse, I just wanted to draw your attention to a mistake by Lightbot (this edit). It mistook the company name 'BHP' with brake horsepower, apparently. Cheers, - Gump Stump (talk) 05:43, 24 February 2009 (UTC)