(Translated by https://www.hiragana.jp/)
User talk:71.41.210.146/Archive 6 - Wikipedia Jump to content

User talk:71.41.210.146/Archive 6

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
 < Archive 5    Archive 6   
All Pages:  1 -  2 -  3 -  4 -  5 -  6 -  ... (up to 100)


Hi! Thanks for keeping an eye out and letting me know! In case you're interested in such comparison graphics, I've made another... cmɢʟeeτたうκかっぱ 01:09, 18 January 2015 (UTC)[reply]

Comparison of side elevations of some notable bridges to scale

thank you.

Thank you for the merge User talk:DavidCary#Merge of PEM nut into Swage nut complete.

p.s.: I see from #EM6600 core that you are interested in 4-bit processors.

I suspect there is a lot of "hidden history" around 4-bit processors that would make a great Wikipedia article. Much of that history was kept secret for years because of NDAs and other secrecy agreements. I suspect many of those agreements have a time limit that has already expired, and I hope that people will tell their piece of the story before it is forgotten.

There's a little more discussion of 4-bit processors at Talk:List of common microcontrollers.

--DavidCary (talk) 17:55, 4 February 2015 (UTC)[reply]

March 2015

Information icon Hello, I'm XLinkBot. I wanted to let you know that I removed one or more external links you added to the page Schuppan 962CR, because they seemed to be inappropriate for an encyclopedia. If you think I made a mistake, or if you have any questions, you can leave me a message on my talk page, or take a look at our guidelines about links.  
Your edit here to Schuppan 962CR was reverted by an automated bot that attempts to remove links which are discouraged per our external links guideline. The external link(s) you added or changed (https://www.youtube.com/watch?v=51VJgvZ7Hxg) is/are on my list of links to remove and probably shouldn't be included in Wikipedia. If the external link you inserted or changed was to a media file (e.g. a sound or video file) on an external server, then note that linking to such files may be subject to Wikipedia's copyright policy, as well as other parts of our external links guideline. If the information you linked to is indeed in violation of copyright, then such information should not be linked to. Please consider using our upload facility to upload a suitable media file, or consider linking to the original.
If you were trying to insert an external link that does comply with our policies and guidelines, then please accept my creator's apologies and feel free to undo the bot's revert. However, if the link does not comply with our policies and guidelines, but your edit included other, constructive, changes to the article, feel free to make those changes again without re-adding the link. Please read Wikipedia's external links guideline for more information, and consult my list of frequently-reverted sites. For more information about me, see my FAQ page. Thanks! --XLinkBot (talk) 05:52, 2 March 2015 (UTC)[reply]
If this is a shared IP address, and you didn't make the edit, please ignore this notice.

Thank you, LinkBot, but as the edit comment said, I meant to do that. 71.41.210.146 (talk) 09:46, 2 March 2015 (UTC)[reply]

WWVB, again

Thank you again for your continued work on this article, in particular your recent additions to the details of the phase-modulated time code. Jeh (talk) 08:28, 14 March 2015 (UTC)[reply]

Hi, I'm afraid I had to undo your move of this article to Metre water equivalent. Pages shouldn't be moved without the history because our licence requires attribution, and I'm also not sure how uncontroversial it is -- these spelling changes require consensus, I think, and I got more google hits for "meter water equivalent" than "metre water equivalent". Wikipedia:Requested moves/Controversial seems to be the correct process here. ekips39 (talk) 20:29, 2 April 2015 (UTC)[reply]

Thanks for the notice; if there were a way to move the page with history, I would have done it. 71.41.210.146 (talk) 23:24, 2 April 2015 (UTC)[reply]

Warning

This is a warning that this IP was used to vandalize the Thirty Meter Telescope article by removing accurate, sourced content. It was unconstructive and only brings more eyes upon this page and the above information about the IP's owner.--Mark Miller (talk) 08:17, 3 May 2015 (UTC)[reply]

WTF does that even mean? Which page is "this page"? This talk page here? By the way, WP:ATWV.71.41.210.146 (talk) 09:10, 3 May 2015 (UTC)[reply]
[1].--Mark Miller (talk) 19:16, 3 May 2015 (UTC)[reply]
I know which edit; I only made one recently. Obviously, I felt it was constructive; I felt the phrasing I changed was giving an WP:UNDUE impression of the "global" protests, so I kept the fact (there were protests outside the islands) while trying to describe the scale better.
The part I completely failed to understand is the one I quoted: "only brings more eyes upon this page"... it's almost phrased as if it's a threat or intimation of undesired consequences. A warning that people might read Wikipedia? Does not compute.
71.41.210.146 (talk) 22:42, 3 May 2015 (UTC)[reply]

Reference errors on 4 May

Hello, I'm ReferenceBot. I have automatically detected that an edit performed by you may have introduced errors in referencing. It is as follows:

Please check this page and fix the errors highlighted. If you think this is a false positive, you can report it to my operator. Thanks, ReferenceBot (talk) 00:27, 5 May 2015 (UTC)[reply]

Fixed; thank you. 71.41.210.146 (talk) 00:54, 5 May 2015 (UTC)[reply]

Your request at Files for upload

Hello, and thank you for your request at Files for Upload! The file has been uploaded. You can find it at File:Tel two parts AZ and ALT test 3.png. See Wikipedia:Images#Using images to learn image syntax, or Wikipedia:Creation and usage of media files for other types of files. Regards, Nick⁠—⁠Contact/Contribs 18:07, 3 August 2015 (UTC)[reply]

Also, File:Tel two parts AZ and ALT profile.png. --Nick⁠—⁠Contact/Contribs 18:11, 3 August 2015 (UTC)[reply]
Thanks. Um, RFU instructions suggest renaming files to make names less ambiguous (like including "LSST" in the name!); going to request a rename before using.71.41.210.146 (talk) 18:28, 3 August 2015 (UTC)[reply]
Replied on my talk page. --Nick⁠—⁠Contact/Contribs 18:34, 3 August 2015 (UTC)[reply]

Template:Infobox telescope "bodystyle" parameter

Please see Template talk:Infobox telescope#"bodystyle" parameter. Alakzi (talk) 19:37, 7 August 2015 (UTC)[reply]

Convert

Re you post at Template talk:Convert, one school of opinion is that the template should force people to follow the MOS guidelines at WP:UNIT. If you don't share that view, try:

  • This old revision of Help:Convert.
  • {{convert|6.5x6.5x42|m|ft|abbr=on}} → 6.5 m × 6.5 m × 42 m (21 ft × 21 ft × 138 ft)
  • {{convert|6.5xx6.5xx42|m|ft|abbr=on}} → 6.5 × 6.5 × 42 m (21 × 21 × 138 ft)
  • {{convert|6.5*6.5*42|m|ft|abbr=on}} → 6.5×6.5×42 m (21×21×138 ft)

Johnuniq (talk) 02:21, 16 August 2015 (UTC)[reply]

Ooh, exactly what I wanted. Thank you very much! 71.41.210.146 (talk) 02:26, 16 August 2015 (UTC)[reply]

Teahouse reply

Hello, 71.41.210.146/Archive 6. Your question has been answered at the Teahouse Q&A board. Feel free to reply there!
Please note that all old questions are archived after 2-3 days of inactivity. Message added by Cordless Larry (talk) 07:00, 15 September 2015 (UTC). (You can remove this notice at any time by removing the {{teahouse talkback}} template).[reply]

Coordinates question at Teahouse

Thank you for your follow-up to my answer to Action Hero's question over at the Teahouse! You're right that I (or someone) should have linked to the coordinates template page for its documentation. Thanks for taking care of it. —GrammarFascist (talk) 10:59, 16 September 2015 (UTC)[reply]

I do a fair bit of adding ISO 3166-2 region codes and similar hidden metadata to coordinates. (Along with, as you noted, fixing up dashes!) 71.41.210.146 (talk) 11:07, 16 September 2015 (UTC)[reply]

Recognition of your good, quasi-anonymous work

Hello again! I thought you might like to know that you're one of the IP users identified on my user page as "longstanding editors who use a static IP address rather than a Wikipedia account yet make many valuable contributions to Wikipedia". Thanks for all you do to make Wikipedia a better encyclopedia and a better place. —GrammarFascist contribstalk 02:54, 17 October 2015 (UTC)[reply]

Your edits to SHA-1

Information icon Hello, I'm Intgr. I noticed that you made a change to an article, SHA-1, but you didn't provide a reliable source. It's been removed and archived in the page history for now, but if you'd like to include a citation and re-add it, please do so! If you need guidance on referencing, please see the referencing for beginners tutorial, or if you think I made a mistake, you can leave me a message on my talk page. Thank you. -- intgr [talk] 08:17, 27 October 2015 (UTC)[reply]

Thank you, I know all about referencing. I assumed the reference to "The Fappening" and "Snapchat#The Snappening" was so glaringly obvious that it was unlikely to be challenged, and thus per WP:V did not need a citation. I was only documenting it for later years when the those terms are no longer current. But since you have challenged it, I'll try to find something. The problem is, some things are so obvious that news writers do not feel it's necessary to document them explicitly. 71.41.210.146 (talk) 08:37, 27 October 2015 (UTC)[reply]
Hi! Thanks for replying. I don't find it "obvious", personally; all of these terms are derived from "happening". And I think this is a very relevant place for WP:OR and Verifiability, not truth: WP should not claim something just because "it seems that way". Either a source exists, or we don't have a basis for that claim.
A consensus on Talk:SHA-1 would probably be OK too, but I don't think you'll find many people agreeing with you.
PS: You don't need to copy your response to my talk page. You should reply here and use {{ping|intgr}} to automatically send a notification about your reply. -- intgr [talk] 09:03, 27 October 2015 (UTC)[reply]
Well, you said "leave me a message on my talk page", so that's what I did; I just also wanted to include at least a brief reply here, too. 71.41.210.146 (talk) 09:09, 27 October 2015 (UTC)[reply]
Ah ok, sorry, that comes with the "unsourced" template. :) -- intgr [talk] 09:24, 27 October 2015 (UTC)[reply]

Gray code

Please do not optimize C code as was done at Gray code. Articles are to explain concepts and a short program can be helpful for that, but not if it uses syntax like num ^= num >> 2. The loop was clear, and inserting clever code will only result in it being removed as unhelpful. Johnuniq (talk) 01:09, 4 November 2015 (UTC)[reply]

It wasn't a micro-optimization; it reduced 32 steps to 5, and got rid of a bunch of hard-to-follow loop control as well. I can avoid op= syntax if you think that's confusing, but it seems like an important and useful change, not a stylistic one. Note that I also added a comment explaining it as well. 71.41.210.146 (talk) 01:12, 4 November 2015 (UTC)[reply]
How does that change look? The two versions correspond to the optimization cited in the preceding text. 71.41.210.146 (talk) 01:28, 4 November 2015 (UTC)[reply]
I don't have time/energy to look now, but might later. I just wanted to alert you in case you start on other articles. Stuff which looks too much like a program (that is, it deviates too far from understandable pseudocode) is routinely deleted. Johnuniq (talk) 01:44, 4 November 2015 (UTC)[reply]
Well, that certainly hasn't been my experience. I agree that WP is not a place to dump source code, but the goal of example code is to be useful, which includes reasonably efficient. 71.41.210.146 (talk) 05:24, 4 November 2015 (UTC)[reply]
From an algorithmic perspective, I think you confuse conciseness with efficiency. For algorithms, the focus is usually on something countable such as comparisons and often ignores overhead issues. Efficiency is minimizing the count. For the Gray code, we can compare doing 32 shift-XORs versus 5 shift-XORs. That's the gem. Trying to minimize the number of instructions is not an algorithm issue but rather a programming/compiler issue. It may be very important for an actual implementation, but it's not about the algorithm. Glrx (talk) 16:10, 7 November 2015 (UTC)[reply]

Talkback

Hello, 71.41.210.146. You have new messages at I dream of horses's talk page.
Message added 15:37, 4 November 2015 (UTC). You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.[reply]

Your expertise with coordinates

Hello again! I was hoping you could help me add coordinates to Shooting of Jeremy Mardis — either by making the edit yourself, or by walking me through the process. Both an intersection and a building with a known address are substantiated as the location where the shooting occurred... do I just go to Google Maps and input that information to find the coordinates? Thanks in advance, GrammarFascist contribstalk 01:19, 18 November 2015 (UTC)[reply]

That's one way that works fine. Template:Coord explains most of it; it's just the "coordinate parameters" that are weird. They're all glommed together in one template argument right after the coordinates proper, in the form "name:value_name:value_...". I started from an existing location Marksville State Historic Site, used GeoHack to pull that up on both Google maps and OpenStreetMap.
The I'm guessing the dead end is 31°07′30.4″N 92°02′59.7″W / 31.125111°N 92.049917°W / 31.125111; -92.049917 (Dead end near intersection of Martin Luther King Drive and Taensas Street), the stub between the intersection and the gate visible on satellite view. Does that seem right to you?
Coordinate parameters I added are:
  • type:event — this is a one-time event, not a landmark.
  • region:US-LA — The ISO 3166-2 region code for the U.S. state of Louisiana.
  • dim:50 — Show a 50 m diameter are around the coordinate; it's a pretty local event.
If you want to cut & paste that in, decide if you want it displayed in line, at the top of the article, or both, and adjust the "display=" parameter accordingly: "i" or "inline", "t" or "title", or "it" or "inline,title".
Also change the "name=" parameter, or delete it entirely if the article title is fine.
71.41.210.146 (talk) 09:59, 18 November 2015 (UTC)[reply]
P.S. I went ahead and WP:BOLDly edited the article. Please check if it's okay! 71.41.210.146 (talk) 10:07, 18 November 2015 (UTC)[reply]
That's fantastic, 71.41.210.146, thanks so much! I did move the title display into the infobox, because I at least find that my eye ignores title-level coordinates if there's also an infobox in the article in question. This way the infobox display will also be preserved if some other editor boldly removes the inline coordinates template entirely. Anyway, thanks again, and let me know if there's ever anything I can give you a hand with. —GrammarFascist contribstalk 13:16, 18 November 2015 (UTC)[reply]
Ah, didn't see the infobox. Made the infobox coord have the extra info (why'd you delete it when copying?), removed the one in line with the text, added a comment describing how the coordinate was derived. 71.41.210.146 (talk) 13:31, 18 November 2015 (UTC)[reply]
Thanks again! I think the info is most accessible yet least intrusive the way you did it. (As for why I left out the other info when I put the coordinates into the infobox, it was entirely because I didn't actually know what I was doing. ) You are a peachy keen Wikipedian. —GrammarFascist contribstalk 02:39, 19 November 2015 (UTC)[reply]

Hi 71.41.210.146! I responded to you over at Talk:Shooting of Jeremy Mardis about the circa issue, and also started a new section I hope you'll comment on. Thanks again for your continued contributions to this article, they've been very helpful. —GrammarFascist contribstalk 23:35, 21 November 2015 (UTC)[reply]

I have made one edit to SNOLAB and also responded to you at Talk:SNOLAB. —GrammarFascist contribstalk 20:09, 6 December 2015 (UTC)[reply]

Hello, 71.41.210.146. You have new messages at Talk:ACCC conductor.
You can remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.