User talk:Hike395/Archive 20

Archive 15

←

Archive 18

Archive 19

Archive 20

Archive 21

Archive 22

Archive 23

hey

Hey, i hope you didn't mind my comments at Wikipedia:Articles for deletion/Death Valley ecoregion which I myself was thinking were too strong, too dismissive. After I wrote that you were wrong I was thinking I was probably wrong in that, that you were probably right technically in what you said, as you later said in the AFD. I responded too strongly given it was you, when I found the page 177 passage, though I still think you could have been less provocative and more clear about what you thought was wrong in your nomination. I went to reconsider my own comments and perhaps revise them but didn't have access to that page 177 passage again myself to compare wording more closely. I hope/trust there is no bad feeling--I'm sorry if there is--and I'm glad you're keeping going considering and refining Wikipedia articles on the U.S. West. cheers, --doncram 04:12, 12 June 2016 (UTC)

@Doncram: I am an inclusionist: I very rarely create AfDs --- maybe less than 5 times in the last 13 years? I only call for a deletion of an article when I think it truly has no redeeming qualities. Otherwise, I'll do lots of work to research to clean up and keep articles (e.g., the discussion on the U.S. Forest Service Architecture Group or the discussion on Ecology of California).

Thanks for asking --- I'm not angry or upset or anything. My only request is that if you think a nominator could be mistaken, ask a question, rather than assuming he/she is wrong. Due to bad timing luck, the AfD was closed before we could come to a mutual understanding and consensus and now we're stuck with a sub-stub. But, I know the process is semi-arbitrary, anyway, so I'm not emotionally invested in the outcome. —hike395 (talk) 05:01, 12 June 2016 (UTC)

Thanks, and your request is reasonable, and that was where I was heading, I would have revised my comments towards asking what you meant differently than what the page 177 stuff had to say if I coulda sorted out anything coherent to ask. You did strongly assert wrongness without yourself posing a question at the Talk page (and I assume not at the article creator's Talk page) though, and I kinda followed your example. :) I just reacted without paying attention to your name which should have given me more pause, and did give me pause after. And you're right i shoulda asked a question rather than assumed wrongness, no matter who had started the AFD, as that seems to go better always when I've done that or seen it done. I think we agree pretty much how these things should go. Again (or if i didn't say so before) I do v. much appreciate your participation before, during, after the Architects of the United States Forest Service AFD, and I didn't know about the Ecology of California one though I see you helped greatly there. My wp:AFDSTATS show I'm inclusionist too, and I have only started a few AFDs in my history too. cheers, --doncram 06:20, 12 June 2016 (UTC)

Infobox mountain

Unless you hear from someone else from that thread or here, I recommend posting at WP:BOTREQ and asking if anyone would be into helping out with the autolinking update. If no one responds timely, I might be able to help out, as I don't think this is too difficult. I have a couple upcoming plans with a bot, but doesn't include this task, and I'd be more comfortable if I already had BRFA experience... but give it a week or so and let me know as a last resort. Thanks — Andy W. (talk · ctb) 14:50, 21 June 2016 (UTC)

Infobox settlement

That's...very strange. I looked at a couple earlier, when I started the AWB run, and everything looked fine. I'm not sure what's changed in the interval. --Ser Amantio di Nicolao^{Che dicono a Signa?}_{Lo dicono a Signa.} 08:24, 4 July 2016 (UTC)

Saw your comment elsewhere - sorry about that. It's not something that even would have occurred to me, and I'm afraid I'm in the same boat as you are in that I don't know how to code a fix. I'll hold off on any more settlement map changes for the moment and stick to finishing the National Register sites - that infobox doesn't seem to be affected at all. --Ser Amantio di Nicolao^{Che dicono a Signa?}_{Lo dicono a Signa.} 08:27, 4 July 2016 (UTC)

@Ser Amantio di Nicolao: Thanks. I took a look at {{Infobox NRHP}} and it should not provoke the bug.

Nothing has changed in the code: this was a bug that was present from when the #-separated map list feature was implemented.

Over at WP:WikiProject Cities, we had a discussion a year ago about pushpin maps for cities. The discussion was long and contentious, but two relevant ideas came out of it:

• Many of the very short town articles don't have pushpin maps, and adding them shouldn't be done automatically, because that could break their layout.
• Towns in Canada have a map the location within the province, and then have an inset that shows the location of the province in Canada. This "Canadian model" seemed to have some support. That is why I added |pushpin_image=California Locator Map with US.PNG to Mono Mills, California: there is a calibrated map of California that shows an inset of location in the US.

One thing we may wish to consider is using AWB to use this map on California towns. If you agree, it would be simple:

• Set |pushpin_map=California
• Set |pushpin_image=California Locator Map with US.PNG

This would mean redoing your AWB run from yesterday. If you tell me the filter that you used to find those towns, I can do it. Or you can do it (assuming that you agree with the inset maps). —hike395 (talk) 12:19, 4 July 2016 (UTC)

Sure - I don't mind redoing the map run. I'm in the middle of something else, but once that's done I can do this. If you'd rather, the parameters I searched for were simply everything in the category Category:Unincorporated communities in California (as that contains all such communities in the state) and everything in Category:Ghost towns in California and its subcats. --Ser Amantio di Nicolao^{Che dicono a Signa?}_{Lo dicono a Signa.} 18:09, 4 July 2016 (UTC)

OK, I've begun redoing the maps, and am working on a handful now...let me know if you see any problems. I've checked a couple, and they look fine from my end. --Ser Amantio di Nicolao^{Che dicono a Signa?}_{Lo dicono a Signa.} 01:51, 5 July 2016 (UTC)

@Ser Amantio di Nicolao: Jackmcbarn was a good citizen and did a quick fix to Module:Location map, so everything should work now. I think the California map with inset looks good --- it probably doesn't need a second USA map, imo.

Your reversion of my edit to "Template:Seattle weatherbox"

Greetings and felicitations. I noticed that you reverted my edit to Template:Seattle weatherbox. I deleted the line "|imperial first = Y" because when editing the Seattle article it generates the error message in red under the weather box:

Warning: Page using Template:Weather box with unknown parameter "imperial first" (this message is shown only in preview).

because the Template:Weatherbox (no longer?) has a field "imperial first"/"imperial_first". The template's instructions state:

• You can enter data in imperial units or metric units or both.[…]
  

Will convert and display metric values automatically.

Thus an "imperial first" field is extraneous. If you want to include a comment to the effect that imperial measurements should be the primary ones used, that's fine, but I respectfully request that you reinstate my edit.—DocWatson42 (talk) 04:18, 17 July 2016 (UTC)

@DocWatson42: You're right -- there's only metric_first. I reverted back to your version. —hike395 (talk) 04:43, 17 July 2016 (UTC)

Thank you. ^_^ —DocWatson42 (talk) 04:46, 17 July 2016 (UTC)

Speedy deletion nomination of Template:Include-USGov/Test

If this is the first article that you have created, you may want to read the guide to writing your first article.

You may want to consider using the Article Wizard to help you create articles.

Hello, and welcome to Wikipedia. This is a notice that the page you created was tagged as a test page under section G2 of the criteria for speedy deletion and has been or soon may be deleted. Please use the sandbox for any other tests you want to do. Take a look at the welcome page if you would like to learn more about contributing to our encyclopedia.

If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be removed without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. If the page is deleted, and you wish to retrieve the deleted material for future reference or improvement, then please contact the deleting administrator, or if you have already done so, you can place a request here. MrLinkinPark333 (talk) 05:58, 29 July 2016 (UTC)

@MrLinkinPark333: Thanks for finding this: it seems to be an out-of-date version of Template:Include-USGov/testcases, so can be deleted. —hike395 (talk) 10:41, 29 July 2016 (UTC)

Precision of conversion from cm and mm to fractions of inches

Hey, could you explain what you meant in your edit summary in Pinus balfouriana? I don't see anything in MOS:CONVERSIONS about being "conservative". I have been adding conversions to pages on plant species, and generally I convert millimeters to 1⁄32 of an inch (and cm to 1⁄4 in, 0.5 cm to 1⁄8 in), because 1 mm is 0.0394... inch and 1⁄32 inch is a little less than that value, 0.03125. As I understand it, the default is for conversions to be slightly more precise than the original value: thus, in the MOS, 2,320 miles converts to 3,734 km, not 3,730 km, with a precision of 1 km, even though 10 miles are more than one kilometer and to be conservative, they would convert with a precision of 10 km, not 1 km. But my math reasoning could be wrong... — Eru·tuon 02:13, 9 September 2016 (UTC)

Another way to explain my reasoning: I made a series of tables converting values to various fractional values. Converting increments of 1 cm to 1⁄2 inch, increments of 5 mm to 1⁄4 inch, increments of 1 mm to 1⁄16 inch sometimes results in the same inch value for two metric values separated by one unit. Thus, I have used a fraction half of those sizes. That avoids the problem of, for example, 4–5 mm being converted to 3⁄16–3⁄16 in — Eru·tuon 02:46, 9 September 2016 (UTC)

@Erutuon: First, I want to say that I really like and appreciate you adding |frac= to the {{convert}} template that describes small objects. I think it makes the measurements more intuitive for our U.S. readers: 4–6 centimetres (1+1⁄2–2+1⁄2 in) is easier to understand than 4–6 centimetres (1.6–2.4 in).

Second, the precision guidelines are a combination of MOS:UNCERTAINTY and MOS:CONVERSIONS (I should have been clearer in my comment). MOS:UNCERTAINTY talks about conservative rounding. MOS:CONVERSIONS talks about using a level of precision similar to the original value and warns against false precision. For decimal rounding, both of these guidelines lead to the default behavior of {{convert}}, which preserves the number of significant figures of a value, e.g., 2320 miles has three significant figures and hence {{convert|2320|mi|km}} produces 2,320 miles (3,730 km).

The MOS doesn't state what to do with the |frac= parameter for convert. My interpretation is that, given 1 cm of precision, ideally we should close to |frac=2.54, but a little conservative, so use |frac=2. For 1mm of precision, we should be close to |frac=25.4, but a little conservatism would be |frac=16.

Now, this isn't purely mechanical. MOS:CONVERSIONS says that neither 1 mm (1⁄32 in) nor 1 mm (1⁄16 in) is correct, but instead we should use 1 mm (1⁄32–1⁄16 in). Also, just because a number ends in a zero doesn't mean it is only accurate to 10 units. Sometimes we can tell from context --- 10–12 centimetres (3.9–4.7 in) versus 10–20 centimetres (4–8 in), and sometimes we need to go back to the source (which can be tedious). I think your argument about 4–5 millimetres (5⁄32–3⁄16 in) has value, although I suspect 4–5 mm (3⁄16 in) may be clearer.

So, I think we just have to use our judgement for each convert call, with a bias toward underprecision.

Does that make sense? —hike395 (talk) 08:50, 9 September 2016 (UTC)

Ecozone

Hi Hike395, could you take a look at Talk:Ecozone? Zorahia (talk) 03:26, 13 September 2016 (UTC)

I've made some propositions at the talk page.Zorahia (talk) 04:58, 21 September 2016 (UTC)

Commons: Rocky Mountain National Park

Hello,

I've added more subcategories to category Rocky Mountain National Park and wondered if any examples from the new subcategories should be added to the Rocky Mountain National Park page. What do you think?--CaroleHenson (talk) 18:19, 1 November 2016 (UTC)

I think enough cats have been added as "see also cat"s to Rocky Mountain National Park. Thanks! —hike395 (talk) 02:00, 2 November 2016 (UTC)

Ok, cool! Love the new formatting - pretty! I thought the {{c}} template was for commons. But I must have read the interlinking documentation wrong. Thanks for getting what I was talking about from the header!--CaroleHenson (talk) 21:16, 2 November 2016 (UTC)

Thanks!

		The Random Acts of Kindness Barnstar
		Thanks so much for fixing Template:HHS content! I was struggling to make it work. Jytdog (talk) 08:58, 19 November 2016 (UTC)

@Jytdog: Thanks for making the template and for the barnstar! Because you wanted to use just a url without a title, I fixed a longstanding bug in the core {{Include-USGov}} template. —hike395 (talk) 13:01, 19 November 2016 (UTC)

:) thanks very much. i was actually trying to figure out how to make the template read the "title" field and you fixed that here. so happy. Jytdog (talk) 13:08, 19 November 2016 (UTC)

Infobox protected area

Please check this edit at Olympic Coast National Marine Sanctuary. I have to go and right now I can't see why that caused a coord error. Strange. However, I can see why the convert has failed. Your regex should have set the field to area_sqmi rather than area_acre (and stripped out the convert), and I'm letting you know rather than trying to fix it in case you want to check the AWB settings. Johnuniq (talk) 05:18, 16 January 2017 (UTC)

@Johnuniq:  Fixed Thanks for catching this and letting me know! —hike395 (talk) 14:13, 16 January 2017 (UTC)

Flower sorting

Hi, Hike395. Thanks for that! -- Rrburke (talk) 11:39, 11 February 2017 (UTC)

dont give up

There are MOS harassers, wikilawyers and others who really give a sense that it is a brick wall or Vogons that you are speaking to/with - they are a daily presence, and some more belligerent, and some are even admins, unfortunately. Better to wait for a while, and try again - never give up - in the end, good sense does prevail - although it might not seem that way at this stage JarrahTree 01:50, 20 February 2017 (UTC)

@JarrahTree: thank you for your kind words, they certainly cheer me up. I would not classify the editors at WT:WikiProject Geology as MOS harassers, wikilawyers, or Vogons -- they just didn't believe in my arguments or data. No poetry appreciation chairs were used in the debate. :-) —hike395 (talk) 02:09, 20 February 2017 (UTC)

Hiking to M*A*S*H site

Taking the trail to the Mash site was very memorable. I do have to add pick early morning or early evening for your hike. Time restraints made us start this hike at 12:30pm. That day in 2016 presented temps at 100 degrees with the ground hotter than that. Picking the right time and month will make it more enjoyable. Pack along plenty of water. Light colored clothes and a good hat. This being if stuck in same situation I was. Hiker is correct on parts being very narrow. Depending on age, stamina and temperature,changes the degree of " easy " to talking to other people who turned back to the park. Totally unprepared as I was visiting my son i wore the clothes on my back. Jeans, wrong boots, dark shirt in 100 degree heat. The mash site has changed since Hikers article. The sign post only has a few boards left. The staked out site was tore up by someone. There is also a old jeep there but covered in graffiti. The small bldg does still have some pics left but it has definitely changed. This being said, I would do it all over again but bringing my proper gear. The feeling is awesome as you scan the area, picturing the helicopter coming in. If you like MASH and hiking don't pass it up. There were no signs leading the way. We did take the lower trail and not much shade. Groups of people sought out any shade they could find. Volunteers do patrol the trail in case you find yourself in trouble. Coming back to the park the trail has a steady incline at one point and once again every piece of shade was taken. One woman even attempted it with a baby stroller. She didn't make it far. I agree with Hiker as it being "easy" if done at the correct time of day and proper clothing. I'm 60 and the heat did start to get to me. Luckily though the creek provided relief. This hike was done in late May and already hot. If you have time check out the Sultan sea. Check sp. May be Sulton. It's not a hike but you can see remnants of a once thriving park, boat launch, all sorts of buildings with only foundations left. The lake devastated by pollution and algae blooms shows very little life. You don't walk on sand but old fish bones instead. One little store with a few food items and rusted old trailers is all that is left. The beach area measured 110 degrees. So once again dress properly. This area is desert. Robcr11 (talk) 19:56, 19 February 2017 (UTC)

@Robcr11: Not sure what this is about, but I'm glad you enjoyed your hike to the MASH site. This is at Malibu Creek State Park, right? —hike395 (talk) 02:17, 20 February 2017 (UTC)

Template causing errors

Your recent edit at {{Infobox cave}} may have broken the template. See articles with script errors. I would have reverted your edit to limit the damage but your contribs suggest you are working on other things so it might be better for you to examine the situation. Johnuniq (talk) 06:53, 11 March 2017 (UTC)

Hmm, I clicked that link for a second time and the number of broken articles had doubled. That caused me to check it was that edit, so I did revert it. Try the preview function when editing the template to verify. Johnuniq (talk) 06:57, 11 March 2017 (UTC)

@Johnuniq: I experimented with the edit in the sandbox to check against the test cases, but it looks like the test coverage was not good enough. Thanks for catching this. —hike395 (talk) 06:59, 11 March 2017 (UTC)

Stuff happens, happy editing! Johnuniq (talk) 07:01, 11 March 2017 (UTC)

@Johnuniq: Should be fixed now. Let me know if some other disaster crops up :-/ —hike395 (talk) 07:11, 11 March 2017 (UTC)

Commons

Hello Hike,
I left you a message on Commons:Template talk:VNIW.
Regards Liné1 (talk) 15:47, 28 July 2017 (UTC)

Chamerion anagallidifolium

Hi Hike395;

Do you remember why you relabeled Epilobium anagallidifolium to Chamerion anagallidifolium?[1] Jepson, WTU Herbarium and E-Flora BC all call it the former. Best wishes, Walter Siegmund (talk) 16:14, 3 August 2017 (UTC)

Hi, Walter! I did the edit because the Commons gallery is Chamerion anagallidifolium, and the wikidata item is also Chamerion anagallidifolium. If you'd like to do a global fix, please feel free -- I was trying to make things least inconsistent. —hike395 (talk) 22:03, 12 August 2017 (UTC)

I've added it to my "To Do" list. Thanks for your response. Best wishes, Walter Siegmund (talk) 15:48, 16 September 2017 (UTC)

Three Sisters FAC

Hi hike395, just wanted to give you a heads up that Three Sisters is at FAC. Let me know if you think the article is missing anything, especially in the geography/geology sections, since I want it to be as comprehensive as possible if it's to become an FA. Thanks, ceranthor 19:30, 24 November 2017 (UTC)

Token of gratitude

		The Volcanoes Barnstar
		Hike395 - thanks for your gracious help with getting Three Sisters (Oregon) to featured article status. Your extensive content addition, painstaking image searches, and research was invaluable to reaching this milestone, and I look forward to working together in the future! ceranthor 15:54, 8 December 2017 (UTC)

Thanks! It was fun --- the best part of editing WP is when several editors cooperate to make a high-quality article. —hike395 (talk) 22:09, 9 December 2017 (UTC)

That geologic time template...

Would it be possible to expand it to the lower ranked time units like Late Cretaceous and Maastrichtian? And could we include those color markers on the lower ranked units as well? Abyssal (talk) 16:44, 12 January 2018 (UTC)

@Abyssal: Here's my current thinking. For categories about eras and periods, we use {{Phanerozoic eon nav}} to allow readers to easily move sideways to other eras/periods. For categories about epochs, we use a period-specific navbox to allow readers to move to other epochs in the same period, or the previous/next preiod. We can update the period-specific navbox to use the new formatting.

There are three reasons to use this strategy:

1. I don't think readers who are looking at (say) Mississippian animals will need (or want) to jump in one click to (way) Pleistocene animals.
2. I can't easily automatically detect whether the period categories are even populated. There's a limit on the number of automated page existence tests you can run. So expanding the Phanerozoic navbox could be filled with red-links, which doesn't help our readers and in fact, goes against WP:NAVBOX.
3. If you make these navboxes even bigger, then I predict the consensus will settle on deleting them entirely. I'm trying to find some middle ground which is acceptable to everyone.

Does this sound ok to you? I'm going through and cleaning up the era and period categories -- after that, I was going to go back to the epochs and substitute period-specific navboxes. —hike395 (talk) 17:02, 12 January 2018 (UTC)

Sounds good! Abyssal (talk) 17:04, 12 January 2018 (UTC)

The general cleanup is excellent - thanks for the awb work in the geology category main space - goodwork! JarrahTree 23:06, 12 January 2018 (UTC)

Once again - very impressed by your cleaning up the geology category space - thank you for your hard work - apologies if you find anything created by me, they (the category pages) look so much better JarrahTree 09:45, 18 January 2018 (UTC)

@JarrahTree: Thanks! I'm glad you like it -- it's a lot simpler now. —hike395 (talk) 18:57, 18 January 2018 (UTC)

Jefferson

Thanks for this; I'm still slowly working on it. I'll try to finish it up today or tomorrow and submit to GAN! ceranthor 18:59, 21 January 2018 (UTC)

Template:Infobox mountain

Upon what are you basing the assertion that the "template does not support etymology", when it does? The documentation was only updated to reflect the capacity of the existing template. An Errant Knight (talk) 01:49, 5 February 2018 (UTC)

@An Errant Knight: My mistake. When I searched the template, my "whole words" button was clicked, and it didn't find {{{etymology|}}}. Sorry for the mixup. —hike395 (talk) 02:14, 5 February 2018 (UTC)

@An Errant Knight: Where is it implemented in {{Infobox valley}}? I don't see it anywhere. —hike395 (talk) 02:16, 5 February 2018 (UTC)

Apologies, attempted to update the {{Infobox valley}} template, but decided not to do so at this time; and then forgot that the documentation was already updated in anticipation of the change (that wasn't made, yet). Thanks for catching that! An Errant Knight (talk) 02:45, 5 February 2018 (UTC)

@An Errant Knight: Ah, ok. No problem. I usually update the documentation after I edit a template (but then have the opposite problem when I forget to document new features!) —hike395 (talk) 02:48, 5 February 2018 (UTC)

Rollback

You can revert Look2See1's edits if you want (for that reason I've just now given you rollback), or let me know and I can do it. Nyttend (talk) 11:38, 21 March 2018 (UTC)

@Nyttend: Thanks for the rollback right! I just undid the latest 250 edits of the sock, took me about 30 minutes. Looks like this will be about 4 hours of work (perhaps I'm doing it inefficiently -- I'm just rolling back using the User Contributions page). I can chip away at this --- if you want to step in and share the drudgery, feel free! —hike395 (talk) 14:04, 21 March 2018 (UTC)

Template barnstar

		The Template Barnstar
		A belated thanks for your creative and diligent work dealing with the navbox nuisance. This barnstar may seem paradoxical, but pruning is an important part of a healthy template ecosystem! RockMagnetist(talk) 15:53, 19 April 2018 (UTC)

@RockMagnetist: Thanks for the barnstar! —hike395 (talk) 02:15, 20 April 2018 (UTC)

Wondering

If you would be interested in getting this link to turn blue? — xaosflux ^Talk 13:30, 26 May 2018 (UTC)

@Xaosflux: Thanks for asking! Admins do a tough job of dealing with wiki-drama. I have enough tools (e.g., templateeditor) to keep me occupied. So I will decline your generous offer. —hike395 (talk) 15:57, 26 May 2018 (UTC)

No worries, I've been looking for some people to nominate lately and you sort of checked many of my boxes as someone would could be a positive on the technical aspects of administration, including with some of the more advanced File space maintenance that has less volunteers. While admins can do lots of extra things, they are not required to do any of them- for example you could never block someone or close an xfd and still be a net positive. If you change your mind or have any questions feel free to ping me, I'd be happy to nominate you even focusing only on a subset of actives you would want to focus on. It looks like it was 10+ years since someone asked you on your talk, maybe I'll poke you again in ten more! Happy editing, — xaosflux ^Talk 17:23, 26 May 2018 (UTC)

Infobox River

YO. Wanted to make sure you saw this thread about merging {{geobox}} with {{infobox river}}. Particularly the comments lower down on the thread about the issues with the current river infobox. You did wonders with {{Infobox valley}} so thought you might be interested. I'm going to try to take a stab at it tonight but very interested in your thoughts. --Zackmann (^{Talk to me}/_{What I been doing}) 23:05, 22 October 2018 (UTC)

@Zackmann08: I'm afraid I won't have any time for serious template hacking over the next week or so. Good luck! —hike395 (talk) 15:16, 23 October 2018 (UTC)

No worries mate! Ping me when you're back at it. Hope all is well. :-) --Zackmann (^{Talk to me}/_{What I been doing}) 18:11, 23 October 2018 (UTC)

I have real concerns about this thread... Would appreciate if you could help keep an eye on it. --Zackmann (^{Talk to me}/_{What I been doing}) 20:30, 28 October 2018 (UTC)

Nomination for deletion of Template:Infobox hiking trail/main

Template:Infobox hiking trail/main 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) 15:40, 5 November 2018 (UTC)

A barnstar for you!

	The Tireless Contributor Barnstar
	For your diligent work on {{Infobox settlement}}. You have disagreed with me on a number of fronts, but I appreciate the way in which you have done so. On top of that, you have never let disagreements sacrifice the quality of your work or take away from having diplomatic conversations. Keep up the great work! Zackmann (Talk to me/What I been doing) 23:44, 11 November 2018 (UTC)

@Zackmann08: Thanks! Looking forward to the day when Geobox is deprecated! —hike395 (talk) 00:18, 12 November 2018 (UTC)

Technically all we are waiting for is the official deprecation for Protected Area's. Everything else already has been. --Zackmann (^{Talk to me}/_{What I been doing}) 00:19, 12 November 2018 (UTC)

Do you think we can get Briarcliff Manor, New York converted over now? I honestly don't want to make any edits to that page for fear of getting into another edit war... --Zackmann (^{Talk to me}/_{What I been doing}) 20:30, 12 November 2018 (UTC)

Template:Infobox settlement/sandbox

You still working on Template:Infobox settlement/sandbox? It shows as still in use... --Zackmann (^{Talk to me}/_{What I been doing}) 22:54, 13 November 2018 (UTC)

@Zackmann08: The sandbox was part of my proposal, which hasn't gotten much feedback. I've moved the proposal to Template:Infobox settlement/sandbox2 and re-synced the sandbox to the main template. Please go ahead and use the sandbox. —hike395 (talk) 15:54, 15 November 2018 (UTC)

Infobox settlement

FYI, due to a number of issues, including some sound advice from EdJohnston that I avoid some areas where I have been causing conflict, I am intentionally abstaining from commenting on the thread on Talk:Briarcliff Manor, New York. If you feel appropriate, feel free to add this quote from me to that page... Re your statement that Usually no one helps me do grunt work like this: it would take me months of calendar time to fix. I actually manage a bot account (ZackBot), so if you get the thread going on the talk page to {{Infobox settlement}} and if/when it is given the greenlite, I'll write you a bot, submit a BRFA and get it done! I know what a pain this stuff can be so more than happy to help out! As for re-arranging the fields, I agree that needs to be discussed on the template's talk page. I actually don't see an issue with it, but then again I didn't see an issue with motto/motto(s) and we all saw how that blew up... lol. Anyway, hope all is well! --Zackmann (^{Talk to me}/_{What I been doing}) 05:12, 16 November 2018 (UTC)

Italian comune parameters

Since you added some parameters to {{Infobox Italian comune}}, should they be added to the whitelist at the end of the template coding? If you do change this list, can you please remove "short_description"? I decided not to add that parameter after all but forgot to take it off the whitelist (I'm not permitted to edit it myself) and decided not to submit another request for something relatively trivial. Thx. David Brooks (talk) 21:42, 19 November 2018 (UTC)

@DavidBrooks: Hey, thanks for catching that! I added all four parameters to the whitelist, including |short_description= —hike395 (talk) 22:03, 19 November 2018 (UTC)