User talk:Jimp

Archives I, II, III, IV and V

Proposed deletion of Salvo (artist)

The article Salvo (artist) has been proposed for deletion because it appears to have no references. Under Wikipedia policy, this newly created biography of a living person will be deleted unless it has at least one reference to a reliable source that directly supports material in the article. The nominator also raised the following concern:

All biographies of living people created after March 18, 2010, must have references.

If you created the article, please don't be offended. Instead, consider improving the article. For help on inserting references, see Referencing for beginners, or ask at the help desk. Once you have provided at least one reliable source, you may remove the {{prod blp}} tag. Please do not remove the tag unless the article is sourced. If you cannot provide such a source within seven days, the article may be deleted, but you can request that it be undeleted when you are ready to add one. bpage (talk) 03:28, 1 August 2014 (UTC)[reply]

Wikipedia_talk:Manual_of_Style/Dates_and_numbers#Kilowatt-hour

I'm contacting everyone who has commented but who hasn't taken an explicit Support or Oppose position (or if you did, I missed it). In the interest of bringing this discussion to resolution, it might be helpful if you could do that. Thanks. EEng (talk) 12:59, 3 August 2014 (UTC)[reply]

New Zealand English

I've answered your questions on the https://en.wikipedia.org/wiki/Talk:New_Zealand_English page. I realise you might not have wanted specific answers but were simply trying to generate a clarification/rewrite of the "New Zealand English" page. I hope your question and my response lead to some sort of cleanup, because I consider the page unsatisfactory in its present form. Akld guy (talk) 02:30, 15 August 2014 (UTC)[reply]

Strine

I had to look up strine. Funny. Peter Horn User talk 17:09, 8 September 2014 (UTC)[reply]

Still pending

Hi
Still pending at Template talk:Convert/TonCwt to t#Just curious (latest post there)

{{TonCwtQtr to t|26|1|1}} Template:TonCwtQtr to t
{{TonCwtQtr to t|134|18|2|lk=on}} Template:TonCwtQtr to t

Peter Horn User talk 21:52, 9 September 2014 (UTC)[reply]

September 2014

Hello, I'm BracketBot. I have automatically detected that your edit to Lychee may have broken the syntax by modifying 2 "[]"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

fruit provides, among other [[dietary minerals]] in minor amounts, 7% of copper, 4% of phosphorus]] and 4% of potassium (for DV in a 2000-calorie diet) (table). Lychees are low in [[saturated fat]]
ref>{{cite web|title=One Lychee Equals Three Torches. Experts Call for Caution Over Fruit Illnesses)|url=http://www.jkwzw.com/article/27/2007/16423.html|accessdate=17 June 2011}}</ref>

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 08:13, 22 September 2014 (UTC)[reply]

ThinkPad X

I understand changing disp=flip to order=flip. But why replace the convert/flip4 templates with text equivalent? Kendall-K1 (talk) 11:19, 22 September 2014 (UTC)[reply]

Never mind, I should have checked the template talk page first. Kendall-K1 (talk) 16:23, 22 September 2014 (UTC)[reply]

FYI

FYI: [1]. CC.

can you clarify?

Minor talk page dustup: https://en.wikipedia.org/wiki/User_talk:Frietjes#Hands yet another conflict over technical language and a template created with a lot of disusssion and input. Montanabw^(talk) 05:04, 17 October 2014 (UTC)[reply]

Relax M ... convert people are nice—we're not warriors! Johnuniq (talk) 07:06, 17 October 2014 (UTC)[reply]

Then discuss that with Frietjes??? Montanabw^(talk) 07:14, 17 October 2014 (UTC)[reply]

Module:Convert/data

All the wikitext for Module:Convert/data is generated by a script, so manual edits are not desirable. The procedure is to add wanted units to Module:Convert/extra. Later, after confirming the units are wanted (WhatLinksHere for articles), the information is added to the master list of units, which is then processed. One of the drawbacks of the module is that there is no way (other than searching a database dump) of finding whether the units you added (hp/lb, shp/lb, kW/kg) are used. Another drawback is that with all the units in one megalist, I think we should avoid casual requests for new units that would be unlikely to get much use—I have no opinion on these. By the way, I left a rambling response at Talk:Malik Deenar re carpenter's rods. Johnuniq (talk) 06:59, 17 October 2014 (UTC)[reply]

Another feature of makeunits (the script which generates Module:Convert/data) is that it performs various checks, and it would have refused to generate the current data because it would anticipate the following error which is now in Supercapacitor:

{{val|990|u=kW/kg}} → 990 kW/kg

Because no one has defined "kW/kg" at {{val}}, the above ends up calling:

{{convert|1|kW/kg|disp=unit or text|abbr=on}} → kW/kg

That strange disp setting was added for val—the effect is that if the unit code is known, convert outputs its defined symbol; otherwise, it outputs the given text "kW/kg" (it can also handle unit name and links). However, convert assumes the underlying data is valid, and it performs a conversion before deciding what to output. At the moment, that unit exists and has default output PS/kg, but the latter does not exist, so a mouse-over of the above error text shows a complaint that PS/kg is not defined.

I'm providing all this unwanted detail in case it's of interest for the future, and I'm hoping you'll think of a fix, or raise it at convert talk. If you think there is a need for the units you defined, no problem, and I'll get around to adding them to the master list in due course. However, I don't feel like thinking about PS/kg, so I'm hoping you'll do that. A quick way to define units of this kind is as "per" units—search the docs visible at Module:Convert/extra for "per" unit for examples. I hope any new units get used. Johnuniq (talk) 09:07, 18 October 2014 (UTC)[reply]

Okay, so next time I'll add units to {{convert/extra}}, thanks for the info. The reason for adding kilowatts per kilogram was so that we could replace {{convert/scale}} on General Electric T700. It is a bit extravagant to add code for use on only one page but it's less extravagant than having a special template used only five times in articles (three times on General Electric T700 and twice on WAC Corporal, replaced with hard coding). {{Convert/scale}} is just one of many of these special templates which go pretty much unused (as you know). I can see no reason to keep them but the are clung onto for their special features. I hope one day we can do a tidy up i.e. deletions but perhaps some of these features are worth absorbing into the main template. For example, if we could (as input and/or output) take any two (or possibly more) units which are already defined and combine them (by division, multiplication, etc.), {{convert/per}} and {{convert/scale}} would become redundant. As for the kilowatts per kilogram default, I switched it to horsepower per pound, which I'd already added and which I think makes more sense anyway. Jimp 01:27, 19 October 2014 (UTC)[reply]

Sounds good! Cleaning would help here, and also help people who copy an article for translation on another Wikipedia as it reduces the number of templates they have to deal with. Johnuniq (talk) 02:49, 19 October 2014 (UTC)[reply]

Rod as a volume

I'm not sure how active the measurements wikiproject is, so would appreciate your comments at WT:WikiProject Measurement#Rod as a volume. There are some other recent edits from the same source that I'm not sure of, but that can be another time. Johnuniq (talk) 10:14, 18 December 2014 (UTC)[reply]

February 2015

Hello, I'm BracketBot. I have automatically detected that your edit to Conversion of units may have broken the syntax by modifying 1 "[]"s and 1 "{}"s likely mistaking one for another. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

| ≡ {[frac|100}} ch <ref name=CRC71/> ≡ 0.66 ft ≡ 7.92 in
|}

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 16:15, 8 February 2015 (UTC)[reply]

Template:dtsh

I used the DTSH template on tables of fraternity installation dates in sortable tables when the only information available was season, so if I had three fraternity installations as February 1, 1940, Spring 1940 and May 13, 1940, I'd do them as {{dts|1940|2|1}}, {{dtsh|1940|4|1}}Spring 1940, and {{dts|1940|5|13}} how can I do this without dtsh?Naraht (talk) 00:46, 23 February 2015 (UTC)[reply]

You can use |format=hide, i.e. {{dts|1940|4|1|format=hide}}Spring 1940. For more details see Template:Dts#Formatting. Jimp 12:58, 24 February 2015 (UTC)[reply]

Nomination for deletion of Template:Gapsize

Template:Gapsize has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Frietjes (talk) 17:08, 3 March 2015 (UTC)[reply]

subst'ing in5

I'm curious to know about this edit at Old Rosin the Beau. {{in5}} isn't a template I know much about, and the documentation doesn't say anything about when it's supposed to be subst'ed and when it's not. Ibadibam (talk) 00:23, 10 March 2015 (UTC)[reply]

It's not a template many know much about and that's the point. It only serves to make the mark up of articles all the more arcane. It would be better if the thing were simply to vanish. I'm saying that templates which don't actually do anything of value should all be substituted and then deleted. Jimp 05:49, 10 March 2015 (UTC)[reply]

Gotcha. Thanks for taking the time to respond. Ibadibam (talk) 20:11, 10 March 2015 (UTC)[reply]

Mistake in Colorado article

Hello dear user. In the section Demographics in Colordao article there is a mistake.I guess someone tried to create a table, but he failed (look at the middle part of section). Please help. 217.76.1.22 (talk) 12:46, 20 March 2015 (UTC)[reply]

Fixed with this edit Ibadibam (talk) 21:49, 20 March 2015 (UTC)[reply]

Thanks. Jimp 08:42, 21 March 2015 (UTC)[reply]

Template:Change vs. Template:Noc, Template:Nof, and Template:Onc

I am curious as to why you feel that the following Wikicode:

|align=right| <span class="sortkey">19831858</span>19,831,858

|align=right| <span class="sortkey">19567410</span>19,567,410

|align=right| {{change|19567410|19831858|disp=out}}

is superior to:

{{nof|19831858|19567410}}

The later seems much more intuitive, more efficient, substantially shorter, and it is not redundant.

Yours aye,
Buaidh 20:06, 23 March 2015 (UTC)[reply]

My aim was to consolidate {{noc}}, {{nof}}, {{onc}}, {{onf}} and {{change2}} into one place. On two articles it didn't work so I cheated (until it can be got working). You're probably right, though, as long as {{change}} can't handle such long pages, it's probably best to reinstate {{nof}}. Jimp 01:20, 25 March 2015 (UTC)[reply]

It's working now. Jimp 05:48, 25 March 2015 (UTC)[reply]

I tried the same thing some years ago without success. Buaidh 14:49, 25 March 2015 (UTC)[reply]

Infobox person

Hi. Did you changes in Infobox person were discussed somewhere before you do them? Magioladitis (talk) 23:37, 30 March 2015 (UTC)[reply]

It's not required that every improvement be discussed but if you'd like a discussion, I'll start one. Jimp 23:30, 30 March 2015 (UTC)[reply]

I tried to add |weight= with value 75 kg and I get an extra g fro some reason. -- Magioladitis (talk) 23:37, 30 March 2015 (UTC)[reply]

Sorry about that. It should be fixed now. Jimp 23:39, 30 March 2015 (UTC)[reply]

No problem. Since the template is used in more than 100k pages we have to be cautious. I would like to be sure there is consensus for this addition. -- Magioladitis (talk) 23:45, 30 March 2015 (UTC)[reply]

Fair enough. Jimp 23:46, 30 March 2015 (UTC)[reply]

There is a problem at Template:Infobox person/weight/switch. There is an "in" and "cm" line that needs attention, and:

{{infobox person/weight|110 lb}} → 110 lb (50 kg)

Johnuniq (talk) 00:39, 31 March 2015 (UTC)[reply]

I think I fixed it, but someone should double check. I also wrapped a few inside #if: so we can find and review actual uses. Plastikspork _―Œ^(talk) 01:16, 31 March 2015 (UTC)[reply]

We should really have a more complete set of tests for these subtemplates, the output from {{Infobox person/weight|105 lbs}} and {{Infobox person/weight|7.6 stone}} requires attention. Plastikspork _―Œ^(talk) 01:22, 31 March 2015 (UTC)[reply]

We could probably safely use replace instead of sub, e.g. {{#invoke:String|replace|source={{{2|0}}}|pattern=lbs?|count=1|plain=false}}. Better yet, we could rewrite the whole thing in Lua. :-) Alakzi (talk) 01:39, 31 March 2015 (UTC)[reply]

I have a blue-sky plan of putting the functionality in convert for use by infoboxes. I was thinking of using parameter |input= which could specify a space-delimited set of values and units, and convert would use the first set which had a valid number as the value. Then I hit "5 ft 111⁄2 in" and put the idea lower-down on my todo list. Johnuniq (talk) 03:15, 31 March 2015 (UTC)[reply]

I had thought about lbs, meters, etc. It could be dealt with without too much difficulty. Yes, rewriting in Lua would be great if anyone is up for it ... and perhaps you, Johnuniq, will be. I'll look forward to the blue-sky plan (but I know how busy {{convert}} can keep you). Jimp 05:24, 31 March 2015 (UTC)[reply]

Here's code that will deal with such things as lbs.

ft & in ←→ m or cm

{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{{1|}}}<!--
-->|metre|m}}<!--
-->|meter|m}}<!--
-->|centi|c}}<!--
-->|feet|ft}}<!--
-->|foot|ft}}<!--
-->|inches|in}}<!--
-->|inch|in}}<!--
-->|ms|m}}<!--
-->|ins|in}}

in ←→ cm

{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{{1|}}}<!--
-->|centimetre|cm}}<!--
-->|centimeter|cm}}<!--
-->|inches|in}}<!--
-->|inch|in}}<!--
-->|cms|cm}}<!--
-->|ins|in}}

st & lb ←→ lb ←→ kg

{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{#invoke:String|replace|<!--
-->{{{1|}}}<!--
-->|kilogram|kg}}<!--
-->|stone|st}}<!--
-->|pound|lb}}<!--
-->|kgs|kg}}<!--
-->|lbs|lb}}<!--
-->|sts|st}}

Template:Val broken?

Please see my note at Template_talk:Val#Errors. —Quondum 20:33, 3 April 2015 (UTC)[reply]

It's now fixed. Jimp 05:19, 4 April 2015 (UTC)[reply]

Ntss template

Note that the ntss template has a sandbox and just started working on a set of testcases pages if you want to try to convert to using val. Noticed some errors with long which I haven't added test cases for yet. PaleAqua (talk) 02:12, 6 April 2015 (UTC)[reply]

Thanks. Jimp 04:01, 6 April 2015 (UTC)[reply]

Wow looks like you got all the remaining uses. I did fix a couple of them though. Thought about suggesting that last night but figured going through device rates would be a pain. You can consider this a non-objection to the speedy delete as the template creator. Only one other editor touched the template and only a few used it and many of those got replaced a while back as other options became more powerful. The one thing I wonder about is 10^3 vs 2^10 for kB vs kiB. For telecommunications and device rates have always used 10^3 ( 1000 B = 1kB ); as it does more recently with hard drives, in most other computing fields use 2^10 ( 1024 B = 1kB or 1 kiB ). But in most use cases won't make too much differences in sorting even if the wrong one is used. Though might make sense to support something similar to the long scale option in val to make kB etc. act like kiB. Though again that is probably not necessary. PaleAqua (talk) 16:36, 6 April 2015 (UTC)[reply]

There a parameter to sort by a different unit so, for example, {{val|12|u=kB|us=kiB}} will display 12 kB but sort as 12 kiB. Jimp 16:44, 6 April 2015 (UTC)[reply]

Thanks. PaleAqua (talk) 16:54, 6 April 2015 (UTC)[reply]

Age in days

Why insist on changing that? {{age in days nts|month1=02|day1=08|year1=2015}}+ works perfectly well and is easy to understand. There's never been issues with that (at least in the way it's used in pro wrestling championship lists). There are bound to be more errors caused by spelling mistakes, people forgetting the "sortable=on" parameter from the end etc. if we switch to writing out the dates in full. リボン・サルミネン (Ribbon Salminen) #GG (talk) 14:14, 10 April 2015 (UTC)[reply]

Ribbon Salminen,

Thanks for picking up on the errors.

Yes, {{age in days nts|month1=02|day1=08|year1=2015}} does work perfectly well but do you really think it's easy to understand? {{age in days|February 8, 2015|sortable=on}} seems so very much clearer to me; I mean, don't you agree? Okay, the |sortable=on bit is a little obscure but it's used by {{convert}} (which is a commonly used template) and it's arguably less obscure than tacking nts on anyway.

One can make a typo when entering numbers as well as when entering letters. Actually, it's nice that you pointed this out, though, since the this is another benefit of doing thing the way I'm proposing. A spelling mistake will give a visible error message whereas the wrong number will just give a wrong output.

Yes, people might forget to put |sortable=on but they might forget to use {{age in days nts}} and use {{age in days}} instead. You know, what I find? I find it easier to cope with fewer templates doing essentially the same thing but with a few minor (or sometimes not so minor) differences handled using parameters than to cope with a plethora of them going off in all different directions.

I'm aiming to make it easier for users by simplifying and standardising the use of these templates. This means fewer templates and more natural input.

Thanks again for your thoughts. Jimp 14:38, 10 April 2015 (UTC)[reply]

{{Age in years and days}} is acting up after your edits, see WP:VPT#An old problem in a table; it no longer tolerates spaces around values. -- [[User:Edokter]] {{talk}} 07:42, 11 April 2015 (UTC)[reply]

I'm getting an error even with the old code. It's strange that blank space isn't stripped away automatically. Jimp 08:19, 11 April 2015 (UTC)[reply]

"Column alignment"

Please stop, it looks terrible, the columns are much too far apart. BMK (talk) 09:44, 18 April 2015 (UTC)[reply]

Thank you for the explanation as what you see wrong with the edits. If the columns are too far apart, we can use a different value for the width parameter. Jimp 09:48, 18 April 2015 (UTC)[reply]

Template:Val/sortkey/unit

Recently I investigated an esoteric convert bug which was revealed by {{val|1|u=AU/s}}. That led me to notice that val is now transcluding the old convert templates (previewing that val in a sandbox shows Template:Convert/AU/s is used). That does not concern me, but I thought I would mention the issue in case it was unintended. I think it's due to the new {{val/sortkey/unit}}, although I can't figure out why it wants to do that. {{val/units}} calls convert with {{convert|1|AU/s|disp=unit or text|abbr=on}} which displays the defined symbol for the unit, if it is defined, or the given text if it is not. You probably know all this, but I thought I'd mention it so I can cross it off my list of things to check. Johnuniq (talk) 08:03, 30 April 2015 (UTC)[reply]

Yes, is was intentional ... sort of. {{Val}} is calling the old subtemplates to get the conversion factor for the purpose of sorting. I'd wanted to use Module:Convert/data but I couldn't figure out how to input a unit code and get the "scale" value back or whether that would even be possible. Is it? Or, on the other hand, could a |disp=scale be added to get this factor (unformatted & defaulting to 1) like |disp=unit or text gets the unit symbol? This was something I'd been meaning to ask you about. So, instead I used {{convert/{{{1}}}|b|d=projection}} which does the job by getting the "b" (i.e. "scale") from the old subtemplates. Jimp 08:42, 30 April 2015 (UTC)[reply]

Clever! Using the raw data would be hopeless for finding the scale because the SI units are calculated—for example, km is not in the data table. I could never work up the enthusiasm to investigate what has happened to {{ntsh}} since I first examined it a couple of years ago. The result is that the sort key output by convert is no longer exactly the same as that output by ntsh. If it weren't for that incompatibility issue, rather than an option to get the scale, why not an option to get the sort key? Convert now uses the technique you proposed to generate a "standard" sort key, as can be seen by the fact that the following all give the same key (except for ntsh's additions):

{{convert|1,234.56|km|km|disp=number|sortable=on|debug=yes}} → 7006123456000000000♠1,234.56
{{convert|1,234,560|m|m|disp=number|sortable=on|debug=yes}} → 7006123456000000000♠1,234,560
{{convert|1,234,560,000|mm|mm|disp=number|sortable=on|debug=yes}} → 7006123456000000000♠1.23456×10⁹
{{ntsh|1,234,560|debug=yes}} → 7006123456000000000♠

Some new syntax would have to return only the sort key, and the sort key would be based on the given value if the unit code was not known. I've put it on my todo for later contemplation. Johnuniq (talk) 10:08, 30 April 2015 (UTC)[reply]

By the way, AU/s is recognized as an automatic per unit, so it has a scale:

{{convert|1|AU/s|AU/s|disp=number|sortable=on|debug=yes}} → 7011149597870700000♠1.0
{{convert|60|AU/min|mph|disp=number|sortable=on|debug=yes}} → 7011149597870700000♠3.3×10¹¹

Johnuniq (talk) 10:31, 30 April 2015 (UTC)[reply]

It sounds promising. I noticed that the original version of the module was using the old (pre-2011) {{ntsh}} sort key but it that was updated some time ago. {{Ntsh}} hasn't been significantly changed since 2011 except for the addition of the "♠" which was to prevent the displayed numbers following the hidden part from interfering. I think an option to get the sort key might work. It'd take a little more rearrangement at {{val}} but the result would probably be an improvement. Jimp 10:48, 30 April 2015 (UTC)[reply]

I spent quite a while puzzling over the "♠" and it still does not make sense to me. The sort key is 19 digits but is used as a string, so only if two sort keys were identical would "♠" be considered. Since both sort keys would have that symbol as the 20th character, it would be skipped and have no effect on the sort outcome. I think one of the templates also padded with ampersands in a way that I could not understand, although a very quick look fails to find that now. Johnuniq (talk) 03:21, 1 May 2015 (UTC)[reply]

The problem is that it won't always get treated as a string. I can't quite remember where exactly I ran into this problem but it did come up somewhere. Jimp 03:40, 1 May 2015 (UTC)[reply]

Thank you for your work on {{val}}

		The Tireless Contributor Barnstar
		You were one of the first contributors to {{val}} in 2008 and I am very happy to see you still have time to improve it by leaps and bounds almost a decade later! With over 2000 transclusions and versions in almost 40 languages, your edits will surely improve Wikipedia as a whole: keep up the good work! — `SkyLined` (talk) 22:24, 1 May 2015 (UTC)[reply]

Template:Convert/date

Would you mind taking a look at this article and recommending a replacement example? --204.106.251.214 (talk) 05:06, 8 May 2015 (UTC)[reply]

Category:Unit subtemplates of Convert by year

Category:Unit subtemplates of Convert by year, which you created, has been nominated for possible deletion, merging, or renaming. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the Categories for discussion page. Thank you. DexDor^(talk) 12:09, 9 May 2015 (UTC)[reply]

Conversion of units

Are you sure this is what you meant to do? You changed several values and several uncertainties. For instance, {{val|3.08567782|e=16|6|erre=6|u=m}} became {{val|3.0856776|e=16|u=m}} , which would be 3.0856778200(6)×10¹⁶ m vs 3.0856776×10¹⁶ m. Many other changes are similarly suspicious. Headbomb {talk / contribs / physics / books} 19:34, 29 May 2015 (UTC)[reply]

Those which were changed were copied from the articles on the unit in question. Perhaps those articles were wrong and Conversion of units was right. Perhaps it was the other way around. They couldn't have both been right. Jimp 20:26, 29 May 2015 (UTC)[reply]

It most likely is that the individual unit articles are more up-to-date than the one on the conversion article. Either way, the value needs to match the reference given. Headbomb {talk / contribs / physics / books} 22:11, 29 May 2015 (UTC)[reply]

This is true. So, if the individual unit articles are more up-to-date, as is most likely, then we should use their references. Jimp 23:03, 29 May 2015 (UTC)[reply]

Done. Headbomb {talk / contribs / physics / books} 23:34, 29 May 2015 (UTC)[reply]

strange edit failure

Greetings!

I just tried to tweak the table in the Isotopes of hydrogen page, with a curious lack of result. The table somehow has a missing dividing line between the hydrogen-3 and hydrogen-4 sections, despite the (seemingly) identical table-section delimiters. I changed the "SimpleNuclide|Hydrogen|4" formatting (⁴
H
) to just [sup]4[/sup]H (⁴H), and the missing line then showed up in the edit preview, so I saved the change with an appropriate comment/explanation. However, after that save, the table's appearance is unchanged -- the line between the H-3 and H-4 parts is still missing, even after completely refreshing my browser page (to avoid caching problems).

Please tell me what is missing or wrong here...thanx.

---edited to add--- had to "de-format" the SimpleNuclide and Superscript tags to make the presentation here more clear

Silverhill (talk) 19:05, 5 June 2015 (UTC)[reply]

This is likely a failure of rendering at the browser, not a problem in the page itself; I've seen it before. Increase the view zoom, and the missing horizontal dividing line should reappear. —Quondum 20:25, 5 June 2015 (UTC)[reply]

OK, using zoom did indeed make the line show. (It remains strange that all of the other lines, created by the same graphics instructions, show up perfectly....)

I've reverted my edit. Silverhill (talk) 01:32, 9 June 2015 (UTC)[reply]

Please do excuse the belatedness of my getting back to you. I've been distracted by things horrible, ridiculous, amusing, sad, disturbing, depressing, pleasurable and so on. That is to say, life got in the way of Wikipedia ... it's such a nice holiday from this place. Also, I wasted a bit of time on YouTube. I'll have a look but it's either been fixed by now or it's not a WP problem. Jimp 16:49, 4 August 2015 (UTC)[reply]

A long time ago on Dutch WP

Ciao Jimp,

I saw a contribution of you to H-deletion's TP of more than nine years ago as an anonymous. Now you can if you want contribute everywhere with the same registered ID, but you probably know this very well. Thanks to technology improvement! :-) Klaas `Z4␟` V 08:59, 2 July 2015 (UTC)[reply]

Thanks, I should pop over one day (can't speak a word of Dutch though ... [PS] but that can be changed). Jimp 16:57, 4 August 2015 (UTC)[reply]

Request for comment

An editor has asked for a discussion on the deprecation of Template:English variant notice. Since you've had some involvement with the English variant notice template, you might want to participate in the discussion if you have not already done so.—Godsy^(TALK_CONT) 07:10, 14 August 2015 (UTC)[reply]

Convert templates (a note)

I thought I'd let you know that I removed the lvl-4 header from the convert discussion and turned the lvl-5s into 4s. The two nominations are separate entities at the moment. If in the future you decide to bundle other {{convert}} variants, simply list them all under the same heading (see Step II). Cheers, Primefac (talk) 18:23, 8 November 2015 (UTC)[reply]

ArbCom elections are now open!

Hi,
You appear to be eligible to vote in the current Arbitration Committee election. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to enact binding solutions for disputes between editors, primarily related to serious behavioural issues that the community has been unable to resolve. This includes the ability to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate, you are welcome to review the candidates' statements and submit your choices on the voting page. For the Election committee, MediaWiki message delivery (talk) 13:03, 23 November 2015 (UTC)[reply]

Alteration of the "th" sounds in English dialects

Hi Jimp. It turns out that you had tried to merge the articles relating to alterations of the "th" sounds about a decade ago to Phonological history of English dental fricatives and someone undid the merge. I've tried to merge them again under Alterations in the pronunciation of English ⟨th⟩. Now that page is up for deletion. Perhaps you'd like to participate in the discussion. Wikipedia:Articles for deletion/Alterations in the pronunciation of English ⟨th⟩ I personally just thought that merging them would be good as they're basically just alterations of the "th" phoneme, just different dialects doing it different ways. Also the th-alveolarization article was pretty small. Fish567 (talk) 00:17, 24 November 2015 (UTC)[reply]

Template:Covert listed at Redirects for discussion

I've has asked for a discussion to address the redirect Template:Covert → Template:Convert. I thought you might want to participate in the redirect discussion. Si Trew (talk) 07:22, 28 November 2015 (UTC)[reply]

Invitation to a research survey

Hello Jimp,

I am Allen Lin, a computer science PhD student at the University of Minnesota - Twin Cities. Currently, we are working on a project studying the main article and sub article relationship in a purpose of better serving the Wikipedia article structure. We noticed that you've created main/sub article relationship in Paper size for Paper density. So it would be appreciated if you could take 4-5 minutes to finish the survey questions. Thanks in advance! We will not collect any of your personally information.

Thank you for your time to participate this survey. Your response is important for us!

https://umn.qualtrics.com/SE/?SID=SV_bvm2A1lvzYfJN9H — Preceding unsigned comment added by Cheetah90 (talk • contribs) 01:11, 30 November 2015 (UTC)[reply]

Th-alveolarization

I am proposing that th-alveolarization and th-debuccalization should be merged into alterations in the pronunciation of English ⟨th⟩. Maybe you'd like to participate in the discussion at talk:th-alveolarization Fish567 (talk) 23:40, 3 December 2015 (UTC)[reply]

RfC

Request for comments on the plan proposed at Template_talk:In_title#How_to_alter_this_template_and_its_wiki_landscaping.

I'm asserting that

the 9703 pages that use intitle or lookfrom templates must be changed by AWB or other bot to remove a stray bullet from a print preview.
"noprint" code fix in the intitle sandbox is the same one needed for the lookfrom code
Search links have not been allowed in article space (wp:elno rule 9), and so the missing guideline was only just written for this occasion.
Search links should be allowed in article space, but only if they follow "the missing guideline".

It's all clearly spelled out there (and at its predecessor talk-posting). Please comment. Thank you. — Cpiral Cpiral 07:53, 27 December 2015 (UTC)[reply]

Orders of magnitude

Hi.

a little over a year ago, you made this edit. some of the details do not seem right: for instance, according to your edit, a TEU cargo container has a capacity of 33.1 thousand cubic metres, which is clearly wrong. can you please go over this article again, and make sure everything (at least everything you yourself added) is correct? thanks. peace - קיפודנחש (aka kipod) (talk) 17:59, 18 February 2016 (UTC)[reply]

I'm not sure that I actually added anything (or if I did it would have been pretty ordinary). I didn't add the cargo containers. It looks like I added stuff but what actually happened was a merge. Jimp 19:40, 19 February 2016 (UTC)[reply]

Inflation data update

Hello Jimp, Template:Inflation/IN/dataset was created by you in 2013 and last updated by you in 2014. I am wondering how to update this (source). If you can help me with this, I would be glad to keep this live. Thanks, Arun Kumar SINGH (Talk) 08:15, 24 May 2016 (UTC)[reply]

No, thank you. That'd be great. The inflation temple uses these subpages to look up numbers with which to calculate. So, the template gives the subpage a year and the subpage gives a number. For the Indian rupee subpage, this number is the price in rupees of a thing that would have cost 100 rupees in 1953. So, if you give the subtemplate 1953, it'll return 100, and if you give it 1980, it'll give 493. A thing that would have cost 100 rupees in 1953 would have cost 493 rupees in 1980 due to inflation. Of course, we're talking about average things; prices don't all go up uniformly.

Anyway, that's the basics of what the subtemplate does. What it needs is an update. What would this same 100-1953-rupee thing be worth today, last year and in 2014? Yes, I updated it in 2014. I used the 2013 figure I got at Inflation.eu which was 10.92%. So I added the 10.92% to the ₹4,829.7 figure for 2013 to get ₹5357.1032 for 2014. The problem was that this was reverted. So, currently, it only goes up to 2013.

I think I know what the problem was though. I hadn't updated Template:Inflation-fn with the reference but I have now (so, I hope that works). You'll probably notice that in the revert |#default was added. This is good, we'll want to keep that. What that does is give the last value if the year is out of range instead of giving nothing which would cause an error. So, if we put in 2015, it'll give the 2013 number instead but at least it won't break.

Okay, now I'm going to redo the 2014 edit. That's done. All we need to do is the same thing for 2015 and 2016. You should be able to find 2014 and 2015 figures at the Inflation.eu (linked above). You might have a better source but you'd have to update Template:Inflation-fn (or I could, it's a bit tricky) lest you get reverted like I did.

Don't hesitate to ask for help if you need it. Also, Djr13 (who reverted me) might be able to help, he seems to know more about the template than I (I've put a note on his page). Jimp 14:34, 24 May 2016 (UTC)[reply]

Hello, fyi I responded on my talk page. Thanks for looking into updating this! djr13 (talk) 16:34, 24 May 2016 (UTC)[reply]

Hello Jimp, thanks for the quick reply. Editors like you make a lot of different to Wikipedia and I just want to thank you for your valuable contributions. I checked your reply and following is what I understood and have few comments for you and for Djr13;

I assume that average CPI numbers (and not Dec vs Dec) have been picked up from Inflation.eu. That table has data only from 1958 (perhaps they removed 1953 to 1957).
2014 update in not reflecting on a page where the template was used (check this). It still gives value till 2013.
At Inflation.eu, I noticed that 1958 CPI was 4.74%. In the template when I checked, I found that 1957 cost was 105.3 and 1958 cost was 108.4 (YoY CPI increase of 2.94%). Going by 4.74%, 1958 number works out to be 110.2912 (105.3 + 4.74%). Did I understand this incorrectly? Perhaps the inflation number obtained was from a different source, hence this difference. I checked all the years and using the method you explained, I have calculated each years cost numbers as following.

1953= 100
1954= 104.6
1955= 97.5
1956= 92.4
1957= 105.3
1958= 110.29
1959= 115.38
1960= 117.49
1961= 119.47
1962= 123.81
1963= 127.45
1964= 144.36
1965= 158.29
1966= 175.34
1967= 198.36
1968= 205.03
1969= 203.88
1970= 214.26
1971= 220.84
1972= 235.04
1973= 274.5
1974= 352.78
1975= 376.14
1976= 347.66
1977= 376.56
1978= 386.12
1979= 410.18
1980= 456.85
1981= 516.75
1982= 557.72
1983= 623.7
1984= 676.28
1985= 713.82
1986= 776.06
1987= 844.28
1988= 923.55
1989= 989.22
1990= 1077.46
1991= 1227.01
1992= 1372.78
1993= 1459.4
1994= 1608.84
1995= 1773.26
1996= 1932.5
1997= 2072.61
1998= 2345.57
1999= 2459.1
2000= 2557.95
2001= 2654.39
2002= 2768.79
2003= 2874.28
2004= 2982.64
2005= 3109.41
2006= 3289.44
2007= 3499.64
2008= 3790.81
2009= 4201.35
2010= 4710.13
2011= 5127.92
2012= 5604.82
2013= 6216.87
2014= 6612.88
2015= 7001.72
2016= 7397.32

How do you two suggest we update this up and also make sure that the template used in articles are updated with recent values? Thanks again, Arun Kumar SINGH (Talk) 16:41, 24 May 2016 (UTC)[reply]

Remember, as I mentioned in my reply, there are multiple pages which you must update in order for the data to be reflected in calculations. In particular, the template does not know that the latest year available was changed.

Regarding the inflation calculation on RLV-TD#Low cost operations, that doesn't actually use Template:Inflation directly, but rather Template:INRConvert which has its own complex set of issues. In fact I'm surprised it works at all on that page anymore. Look for example how badly this is broken: Template:Indian Rupee. Sooner or later all these inflation templates will need to be consolidated and fixed, which I proposed here: Wikipedia talk:Lua/Archive 4#Currency and inflation templates.

Unfortunately I don't at this moment have the time or mental clarity to help rectifying the two data sources. Make sure you know precisely how and why they differ before attempting to merge them. djr13 (talk) 17:15, 24 May 2016 (UTC)[reply]

@Arun:

There is no need to update the subtemplate until 2017. It has already been updated. Also, there should be no need to update the pages using the template. This should happen automatically if the template is used correctly. The RLV-TD page is working correctly. In edit mode, you'll notice that the |year= parameter in the template call is given the value 2016. So, it's calculating from 2016 to the current year. Since the current year is 2016, it calculates zero inflation. Of course, this means a pretty odd looking output, "₹95 crore (equivalent to ₹95 crore or US$14.1 million in 2016)". It should output "₹95 crore (US$14.1 million)" if the start year is the current year. {{INRConvert}} is in need of an overhaul (which I was going to do a while ago but hadn't had the time). As for the different numbers that were there before, yes, they were from a different source; I'm not sure which though because it was someone else who compiled them (I only added a year or two). Jimp 17:04, 25 May 2016 (UTC)[reply]

@Djr13:

Thanks for you help. I've replaced the plain hyperlink with a proper citation as you've suggested (using {{citation}}). Regarding the #default, I think you've made a good point that it's not desireable as it's misleading; so, let's ditch it. {{INRConvert}} could do with some work. We'll have to account for the possibility of missing years in the datasheet when doing so so as not to have it just fail. Thanks for the tip regarding updating {{Inflation-year}}. It ain't the most user-friendly template design (I should talk). You're right, the whole thing needs a rewrite and possibly a merging into a single simple template. It might as well be done using Lua. Jimp 17:04, 25 May 2016 (UTC)[reply]

I actually changed Template:Inflation to give errors instead of silently ignoring missing years. It resulted in several hundred pages being methodically fixed when these errors were loudly revealed rather than hidden away.

Of course, it also exposed errors in some other templates. Template:INRConvert and Template:PKRConvert were too complex, too fragmented and too flawed due to their reliance on a single arbitrarily-updated conversion rate rather than historical conversion data, for me to try fixing. This is one of the big things that motivated me to write the Lua proposal. If you feel like working on INRConvert anyway, look at the Template:Inflation documentation, I overhauled the documentation with a large number of test cases and caveats. INRConvert will need to readily handle those...and many more. djr13 (talk) 21:22, 25 May 2016 (UTC)[reply]

Also, I must admit, as unhelpful as it is to say without substantiation, that I have a hunch that something was mishandled in the updated inflation index using the new source. As I told the other editor, make sure you know precisely how and why they differ before attempting to merge them. If you're using a new source, and you can't figure out how or why they differ, you can completely replace the old source, but it means you can not just toss the new data on top of the old, you would need to remove all those years 1953-1958 or so which aren't covered by the new source. Like, why did 1958's index increase from 108.4 to 110.3 but 1957's index remained at 105.3? djr13 (talk) 21:30, 25 May 2016 (UTC)[reply]

Hi Jimp & djr13; wow. I did not know that I am "opening a can of worms". It's more complicated and entangled than I thought. Thanks for all your time and do let me know if I can be of some help. Being an India related subject, I would love to offer help in best of my capabilities. Cheers, Arun Kumar SINGH (Talk) 08:21, 26 May 2016 (UTC)[reply]

The can of worms was already open. Actually, if you're keen, though, we are going to need yearly updates to the template. Another thing, if you're interested, that you might like to help with would be keeping the exchange rates at {{INRConvert}} up to date. Jimp 13:57, 26 May 2016 (UTC)[reply]

Namik_(dessert)

Hi! i want to report something. This article is created by Turkish trolls. They want to name "Android N" as "Android Namık". There is no such dessert. This page also deleted in trwiki beacuse of vandalism. 85.110.54.4 (talk) 10:28, 29 May 2016 (UTC)[reply]

Can I suggest you take it up at WP:AFD? I know very little about Turkish food. Jimp 14:30, 29 May 2016 (UTC)[reply]

Template:Change

Hi there,

Thanks for enhancing the percent change template a little while ago, I've used it extensively. I'm wondering if you would be able to help me find a solution to a little glitch in the template. I'm looking to place a reference on one of the numbers, but the "suf=" doubles it, placing it on both numbers. Would it be possible to create "suf1=" and "suf2=" to create individual suffixes for the numbers?

Thanks! Mattximus (talk) 23:17, 23 June 2016 (UTC)[reply]

Done. Jimp 05:16, 25 June 2016 (UTC)[reply]

June 2016

Hello, I'm BracketBot. I have automatically detected that your edit to Decimetre may have broken the syntax by modifying 1 "{}"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

[American and British English spelling differences#-re, -er|American English]]); SI symbol '''dm''') is a [[Units of measurement|unit]] of [[length]] in the [[metric system]], equal to one tenth of a

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 05:08, 27 June 2016 (UTC)[reply]

Hello, I'm BracketBot. I have automatically detected that your edit to Redhead (bird) may have broken the syntax by modifying 1 "[]"s. If you have, don't worry: just edit the page again to fix it. If I misunderstood what happened, or if you have any questions, you can leave a message on my operator's talk page.

List of unpaired brackets remaining on the page:

by mid-March. In western North America, migrants begin arriving in Oregon, British Columbia] and Colorado in February. In central North America, migrants arrive as soon as temperatures open

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, BracketBot (talk) 01:53, 28 June 2016 (UTC)[reply]

DYKtalk template

You made a change with this edit to the DYKtalk template documentation.

According to the documentation, the template uses the form:

But the form that the DYK bot uses is:

Should I change the documentation back to its original form? The FACBot has to be able to parse these entires. Hawkeye7 (talk) 00:54, 23 August 2016 (UTC)[reply]

Perhaps we could talk to the operator of the bot. I guessing that it would have to be easier to get the bot to handle normal whole dates rather than forcing users to separate them into two parameters. Jimp 01:08, 24 August 2016 (UTC)[reply]

Fine for Shubinator, but it won't help me. The FACBot will still have to parse both forms. Hawkeye7 (talk) 04:23, 24 August 2016 (UTC)[reply]

Go with whichever is easier I s'pose. Jimp 10:26, 24 August 2016 (UTC)[reply]

Extended confirmed protection

Hello, Jimp. This message is intended to notify administrators of important changes to the protection policy.

Extended confirmed protection (also known as "30/500 protection") is a new level of page protection that only allows edits from accounts at least 30 days old and with 500 edits. The automatically assigned "extended confirmed" user right was created for this purpose. The protection level was created following this community discussion with the primary intention of enforcing various arbitration remedies that prohibited editors under the "30 days/500 edits" threshold to edit certain topic areas.

In July and August 2016, a request for comment established consensus for community use of the new protection level. Administrators are authorized to apply extended confirmed protection to combat any form of disruption (e.g. vandalism, sock puppetry, edit warring, etc.) on any topic, subject to the following conditions:

Extended confirmed protection may only be used in cases where semi-protection has proven ineffective. It should not be used as a first resort.
A bot will post a notification at Wikipedia:Administrators' noticeboard of each use. MusikBot currently does this by updating a report, which is transcluded onto the noticeboard.

Please review the protection policy carefully before using this new level of protection on pages. Thank you.
This message was sent to the administrators' mass message list. To opt-out of future messages, please remove yourself from the list. 17:49, 23 September 2016 (UTC)

Nomination for deletion of Template:Chem/3

Template:Chem/3 has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Frietjes (talk) 14:04, 30 October 2016 (UTC)[reply]

Thanks. I'd forgotten about those. I've deleted them. Jimp 02:27, 31 October 2016 (UTC)[reply]

Two-Factor Authentication now available for admins

Hello,

Please note that TOTP based two-factor authentication is now available for all administrators. In light of the recent compromised accounts, you are encouraged to add this additional layer of security to your account. It may be enabled on your preferences page in the "User profile" tab under the "Basic information" section. For basic instructions on how to enable two-factor authentication, please see the developing help page for additional information. Important: Be sure to record the two-factor authentication key and the single use keys. If you lose your two factor authentication and do not have the keys, it's possible that your account will not be recoverable. Furthermore, you are encouraged to utilize a unique password and two-factor authentication for the email account associated with your Wikimedia account. This measure will assist in safeguarding your account from malicious password resets. Comments, questions, and concerns may be directed to the thread on the administrators' noticeboard. MediaWiki message delivery (talk) 20:33, 12 November 2016 (UTC)[reply]

A new user right for New Page Patrollers

Hi Jimp.

A new user group, New Page Reviewer, has been created in a move to greatly improve the standard of new page patrolling. The user right can be granted by any admin at PERM. It is highly recommended that admins look beyond the simple numerical threshold and satisfy themselves that the candidates have the required skills of communication and an advanced knowledge of notability and deletion. Admins are automatically included in this user right.

It is anticipated that this user right will significantly reduce the work load of admins who patrol the performance of the patrollers. However,due to the complexity of the rollout, some rights may have been accorded that may later need to be withdrawn, so some help will still be needed to some extent when discovering wrongly applied deletion tags or inappropriate pages that escape the attention of less experienced reviewers, and above all, hasty and bitey tagging for maintenance. User warnings are available here but very often a friendly custom message works best.

If you have any questions about this user right, don't hesitate to join us at WT:NPR. (Sent to all admins).MediaWiki message delivery (talk) 13:47, 15 November 2016 (UTC)[reply]

ArbCom Elections 2016: Voting now open!

Hello, Jimp. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2016 election, please review the candidates' statements and submit your choices on the voting page. MediaWiki message delivery (talk) 22:08, 21 November 2016 (UTC)[reply]

Nomination for deletion of Template:Ordinal/th

Template:Ordinal/th has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Frietjes (talk) 19:00, 22 November 2016 (UTC)[reply]

Nomination for deletion of Template:Numtext/0

Template:Numtext/0 has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Frietjes (talk) 19:05, 22 November 2016 (UTC)[reply]

Template:Vgrsort1 listed at Redirects for discussion

An editor has asked for a discussion to address the redirect Template:Vgrsort1. Since you had some involvement with the Template:Vgrsort1 redirect, you might want to participate in the redirect discussion if you have not already done so. Lordtobi (✉) 10:58, 3 January 2017 (UTC)[reply]

TfD Convert/old

Jimp, in this TfD User:BU Rob13 @ 10:00, 30 December 2016 asked you to confirm the Blacklist for deletion. Can you spend a moment on that? -DePiep (talk) 09:04, 4 January 2017 (UTC)[reply]

@DePiep: & @BU Rob13:: I've had a look and can't see anything we need to save. Jimp 01:22, 5 January 2017 (UTC)[reply]

Thanks. And there is always WP:REFUND, so the risk is limited. -DePiep (talk) 08:48, 5 January 2017 (UTC)[reply]

Administrators' newsletter - February 2017

News and updates for administrators from the past month (January 2017). This first issue is being sent out to all administrators, if you wish to keep receiving it please subscribe. Your feedback is welcomed.

Administrator changes

NinjaRobotPirate • Schwede66 • K6ka • Ealdgyth • Ferret • Cyberpower678 • Mz7 • Primefac • Dodger67

Briangotts • JeremyA • BU Rob13

Guideline and policy news

A discussion to workshop proposals to amend the administrator inactivity policy at Wikipedia talk:Administrators has been in process since late December 2016.
Wikipedia:Pending changes/Request for Comment 2016 closed with no consensus for implementing Pending changes level 2 with new criteria for use.
Following an RfC, an activity requirement is now in place for bots and bot operators.

Technical news

When performing some administrative actions the reason field briefly gave suggestions as text was typed. This change has since been reverted so that issues with the implementation can be addressed. (T34950)
Following the latest RfC concluding that Pending Changes 2 should not be used on the English Wikipedia, an RfC closed with consensus to remove the options for using it from the page protection interface, a change which has now been made. (T156448)
The Foundation has announced a new community health initiative to combat harassment. This should bring numerous improvements to tools for admins and CheckUsers in 2017.

Arbitration

The Arbitration Committee released a response to the Wikimedia Foundation's statement on paid editing and outing.

Obituaries

JohnCD (John Cameron Deas) passed away on 30 December 2016. John began editing Wikipedia seriously during 2007 and became an administrator in November 2009.

Discuss this newsletter • Subscribe • Archive

13:38, 1 February 2017 (UTC)