<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://www.explainxkcd.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=172.70.210.41</id>
		<title>explain xkcd - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://www.explainxkcd.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=172.70.210.41"/>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php/Special:Contributions/172.70.210.41"/>
		<updated>2026-06-25T16:31:19Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.30.0</generator>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:1425:_Tasks&amp;diff=333063</id>
		<title>Talk:1425: Tasks</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:1425:_Tasks&amp;diff=333063"/>
				<updated>2024-01-17T22:24:22Z</updated>
		
		<summary type="html">&lt;p&gt;172.70.210.41: Bird Buddy and the AX Visio have made this technology a reality!&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;the source of title text maybe is Szeliski, ''Computer Vision: Algorithms and Applications'' (2010), p. 10. --[[User:Valepert|valepert]] ([[User talk:Valepert|talk]]) 06:59, 24 September 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
[http://www.wired.com/2012/06/google-x-neural-network/ Google’s Artificial Brain Learns to Find Cat Videos] might be useful as a description of the problem [[Special:Contributions/108.162.250.219|108.162.250.219]] 08:34, 24 September 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
:Sorry for editing your comment but external links have different syntax that internal links so it wasn't working. -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 11:21, 24 September 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
Nice Superman joke there, Pudder! --[[Special:Contributions/141.101.99.49|141.101.99.49]] 10:26, 24 September 2014 (UTC)&lt;br /&gt;
:It had been removed in an edit, so I shoehorned in back in :P --[[User:Pudder|Pudder]] ([[User talk:Pudder|talk]]) 12:25, 24 September 2014 (UTC)&lt;br /&gt;
Isn't there an xkcd where the estimate of 5 years of work is equivalent to &amp;quot;might take forever?&amp;quot; [[User:Rtanenbaum|Rtanenbaum]] ([[User talk:Rtanenbaum|talk]]) 13:16, 24 September 2014 (UTC)&lt;br /&gt;
:I'm pretty sure you're refering to 678. [[Special:Contributions/173.245.52.132|173.245.52.132]] 15:00, 25 September 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
The link in the description is to a document by {{w|Seymour Papert}} and the [http://books.google.com/books/about/The_Summer_Vision_Project.html?id=qOh7NwAACAAJ book] on the project is also by Papert.  Is there any contemporary evidence that it was actually Minsky who assigned the project?  I think he just got interested in it later. 14:17, 24 September 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
[http://xkcd.com/678/ 678: Researcher Translation] is probably what you're thinking of, Rtanenbaum. [[User:Ndgeek|Ndgeek]] ([[User talk:Ndgeek|talk]]) 17:44, 24 September 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
Is it possible that Randall's selection of bird rather than another naturally occurring object is a subtle reference to the Birdsnap app (http://engineering.columbia.edu/it-crow-or-raven-new-birdsnap-app-will-tell-you-0) which has solved some of the aspects of this problem?  [[Special:Contributions/173.245.48.137|173.245.48.137]] 22:02, 27 September 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
Hopefully I can add that this also seems to make reference to the U.S. Forest Service intention to make everyone have a permit to take pics, etc., in national parks.  https://www.yahoo.com/travel/dont-take-that-picture-the-u-s-forest-service-might-98484656432.html {{unsigned ip|108.162.216.21}}&lt;br /&gt;
&lt;br /&gt;
Post the picture to an online forum, say it's a bird, if it's not everyone will correct you as per http://xkcd.com/386/, so scrape forum and if there's a lot of attention it's not a bird, if there isn't much attention it probably is a bird. [[Special:Contributions/141.101.99.78|141.101.99.78]] 23:06, 3 October 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
A dev team at Flickr took this comic as a challenge, and set up a PoC at http://parkorbird.flickr.com/ (that seems to work fairly well). --[[Special:Contributions/108.162.210.135|108.162.210.135]] 20:08, 20 October 2014 (UTC)&lt;br /&gt;
:I was duly impressed. It doesn't recognize big bird very well, though. ;) [[User:Suspender guy|Suspender guy]] ([[User talk:Suspender guy|talk]]) 20:26, 17 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
A 'picture of a bird' from a CS perspective is a reverse engineering problem.  The picture is a 2 dimensional rendering of a 3-dimensional world and a 'bird' is a 3-dimensional object.  It takes years for the mind of a newborn human to be able to recognize a majority of objects based on their 'first look' at a stereoscopic (two-eyes) image presented by their visual cortex.  The software equivalency of this would be to create a 3 dimensional representation of objects and create a linear-algebra algorithm that can define the statistical probability that any given shape is within a certain degree of exclusion a matrix representation of the target shape (area) of the 3 dimensional object (bird) based on distance (using spacial reconstruction).  It's not impossible, it's just really really hard.  - nerd answer {{unsigned ip|173.245.54.166}}&lt;br /&gt;
:To be honest I don't think it is impossible to replicate any function of human intelligence and mental capacity on a computer system. It just requires sufficient processing ability, appropriate hardware, and of course, an understanding of how humans do it in the first place. -Pennpenn [[Special:Contributions/108.162.250.162|108.162.250.162]] 03:29, 17 September 2015 (UTC)&lt;br /&gt;
&lt;br /&gt;
Or just give Google a little less than two years, and they'll make [https://cloud.google.com/vision/ Google Cloud Vision API] for you [[User:Gpk|Gpk]] ([[User talk:Gpk|talk]]) 20:39, 13 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
I read somewhere that when you ask CS/IT specialist for a probable ETA for solving an interesting problem, you need to multiply the given time to the ETA by 4 and take the next larger unit (a minute becomes 4 hours, an hour becomes 4 days etc.). Can't find the source of that though. [[Special:Contributions/141.101.70.229|141.101.70.229]] 15:47, 12 September 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
== GIS being &amp;quot;easy&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
All these years later, I still struggle with the classification of &amp;quot;are we in a national park&amp;quot; as &amp;quot;easy&amp;quot;..&lt;br /&gt;
&lt;br /&gt;
It 'only' requires a functioning GPS-system. A military super-project, whose [https://nation.time.com/2012/05/21/how-much-does-gps-cost/ initial setup cost 12 billion], still costs ~2 million a day, and whose principles of operation depend on [https://skeptics.stackexchange.com/questions/20230/does-gps-use-general-relativity both special '''and''' general relativity] for correctness.&lt;br /&gt;
And that's ''before'' we add the record-keeping and (internet?)logistics involved with providing each phone an accurate GIS-database. The OpenStreetMap (most likely free/gratis source of this type of data, for a cheap app) is a massive undertaking!&lt;br /&gt;
&lt;br /&gt;
(sarcasm on) GIS-lookup sure is easy! Only took a minor Manhattan-project, a literal Einstein, and an army of internet volunteers to solve!(sarcasm off)&lt;br /&gt;
&lt;br /&gt;
(I'm leaving out mobile internet access while in said National Parks (Telecom operators are among the wealthiest companies in the world, and those phone-towers-disguised-like-trees don't come cheap...), because the App would probably be shipped with a hardcoded park-database, not do live queries.)&lt;br /&gt;
&lt;br /&gt;
-- Jules @ [[Special:Contributions/162.158.91.77|162.158.91.77]] 08:13, 18 May 2020 (UTC)&lt;br /&gt;
&lt;br /&gt;
:This is about implementation of something existing, not inventing it from scratch. The use of the word &amp;quot;app&amp;quot; implies, that this comic is happening in the smartphone area, so GPS on phones should be a regular thing. --[[User:Lupo|Lupo]] ([[User talk:Lupo|talk]]) 09:57, 18 May 2020 (UTC)&lt;br /&gt;
&lt;br /&gt;
:: &amp;quot;app&amp;quot; sets the real-world context, but the punchline is about the comparative hardness '''in CS'''.&lt;br /&gt;
:: For the pragmatic app-developer, &amp;quot;previously solved&amp;quot; equals &amp;quot;easy&amp;quot;; for a doctorate in computational theory, it doesn't :-)&lt;br /&gt;
:: -- Jules @ [[Special:Contributions/162.158.91.77|162.158.91.77]] 12:16, 18 May 2020 (UTC)&lt;br /&gt;
:::That might be true, but this comic is definitely about developing an app, so it doesn't matter if GPS involves complicated hard- and software setups outside of the app or not. And unless you focus on the theoretical work also for a computer scientist, it is easy to use established GPS methods. --[[User:Lupo|Lupo]] ([[User talk:Lupo|talk]]) 12:45, 18 May 2020 (UTC)&lt;br /&gt;
&lt;br /&gt;
now deep learning is common you not need research team and five years anymore&lt;br /&gt;
&lt;br /&gt;
:And it took about five years since the comic was posted to get to that point...&lt;br /&gt;
&lt;br /&gt;
This comic is referring to doing a GIS lookup which is a glorified sql Query which has nothing to do with GPS and the the USGS spatial data a GIS database is commonly populated with is not derived from GPS information anyway. A GIS Lookup IS easy. Gathering the spatial data is difficult, though as previously mentioned its already widely and freely available for use. --[[User:PlatterMonkous|PlatterMonkous]]&lt;br /&gt;
:The GIS data is being looked at to determine if GPS-derived metadata lies within one of its boundaries, surely?  Without GPS, the query has no sensible question to ask.&lt;br /&gt;
:(Then again, none of my own pictures have that sort of EXIF information. Either they're taken on a 'dumb' digital camera, that doesn't have inbuilt GPS, or even ''if'' they're done via my GPS+Camera-equipped tablet (rare) I've likely not allowed the one to be fed data that the other one knows. If it's even turned on. But the comic scenario clearly assumes otherwise.) [[Special:Contributions/172.70.86.62|172.70.86.62]] 20:21, 10 November 2022 (UTC)&lt;br /&gt;
&lt;br /&gt;
I think that, like in a number of other comic explanations, the explanation of the humour has given way to the technical exposition of the situation. What made me chuckle about this comic is the old adage in the software industry that: ''It takes 5% of the time to implement the first 95%, but 95% of time to complete the last 5%''. Even when experienced programmers correctly identify the difficult element of a problem and attempt to compensate for that difficulty in their implementation schedules, they can still be ''wildly'' off the mark. In this case, 60 years and counting... [[Special:Contributions/172.71.94.28|172.71.94.28]] 10:55, 9 August 2023 (UTC)&lt;br /&gt;
&lt;br /&gt;
The year is 2024, and there is an ArsTechnica article about the problem in this comic now being solved. https://arstechnica.com/information-technology/2024/01/famous-xkcd-comic-comes-full-circle-with-ai-bird-identifying-binoculars/ [[Special:Contributions/172.70.210.41|172.70.210.41]] 22:24, 17 January 2024 (UTC)&lt;/div&gt;</summary>
		<author><name>172.70.210.41</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=2880:_Sheet_Bend&amp;diff=332980</id>
		<title>2880: Sheet Bend</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=2880:_Sheet_Bend&amp;diff=332980"/>
				<updated>2024-01-16T06:38:37Z</updated>
		
		<summary type="html">&lt;p&gt;172.70.210.41: /* Explanation */ Removed random ampersand&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 2880&lt;br /&gt;
| date      = January 12, 2024&lt;br /&gt;
| title     = Sheet Bend&lt;br /&gt;
| image     = sheet_bend_2x.png&lt;br /&gt;
| imagesize = 317x244px&lt;br /&gt;
| noexpand  = true&lt;br /&gt;
| titletext = A left-handed sheet bend creates a much weaker connection, especially under moderate loads.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|Created by a SHEET BOND - Seems like there are way too much about the security problems with this connector and less about explaining the comic. Do NOT delete this tag too soon.}}&lt;br /&gt;
This is the seventh installment in the series of [[:Category:Cursed Connectors|Cursed Connectors]] and presents Cursed Connectors #46: The Sheet Bend. At the time of release this was the lowest number used for a cursed connector, replacing [[2495: Universal Seat Belt|#65: Universal Seat Belt]] (with [[2507: USV-C|#286: USV-C]] being the one with the highest number).&lt;br /&gt;
&lt;br /&gt;
This comic shows two double-core cables being joined in a knot to make an electrical connection. The knot used to tie the two halves of the cable is a {{w|sheet bend}}, which is often used to join two ropes of different thicknesses, and explains the name for this type of cursed connector, which seems to be made by ensuring each cable end is terminated with identical electrical connections to the outer sleeving in a manner similar to various 'ring' connections in {{w|Phone connector (audio)|'phone' connectors}}, but as significantly longer and more separated sleeves.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- NOT SURE IF THIS IS NEEDED... A conventional join between two cables might be to have a plug attached to one cable and a socket to the other, or possibly using a {{w|Gender of connectors and fasteners#Gender changers|gender-changer}} back-to-back socket to which two plug-ended cables can be attached. Depending upon the type of plugs/sockets, this might not also be able to withstand much physical tension between the cables, and could come loose. For a permanent fix, directly wiring each cable's cores into something like a {{w|screw terminal block}} or a {{w|punch-down block}} within a {{w|junction box}}, or even directly soldering the correct ends together (which might require reinsulating, as necessary, to prevent the wrong wire-ends from touching each other) would be more usual. Such a setup might even be expected to resist more pull on each wire, through the use of integrated cable grip (or {{w|Cable gland|gland}}) to resist such in-use loads. Threading wires around a specifically designed smoothly twisted entry path can also be used to add resistance upon cables entering/exiting an electrical housing, and some of these wrappings may involve what is practically a knot. The method(s) used would depend upon the expected treatment of the cable, although could do nothing once the forces involve approaching the limits of the cable's own resiliance to being stretched. Historically, ''directly'' tying wires together has been used to connect simple wires, with one example being the {{w|Western Union splice}}, used to connect telegraph lines. this splice was to be used on single-strand conductors (with or without insulators), the return part of the circuit would consist of a parallel wire, probably with its own splice(s) in it as required.   ...TRYING IT WITHOUT IT BEING VISIBLE, JUST WHILE I FURTHER MULL ON IT --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In contrast to more normal methods, [[Randall]] has proposed yet another of his 'cursed' connectors. This one requires ''no'' additional plugs, sockets, enclosures or even tools to use. Any two cables with such ends can be brought together and simply knotted together. This particular knot, and the specific spacing of its two external conductors, appears to be chosen in order to rather elegantly create consistent connections between the respective contacts, with a minimum of fuss. &lt;br /&gt;
&lt;br /&gt;
However, there are potentially many unaddressed but conspicuous problems with this connection method, thus rendering it a 'cursed' connector. Among the issues are:&lt;br /&gt;
* The need to have suitable ends to any cables, which would involve issues in the manufacture (and the materials used) as cable's cores must be separately tapped and reliably connected to an external length of conductive sleeving.&lt;br /&gt;
* The consistent ability of a cabler to tie the correct knot, which is a skill that will need practice. Done wrongly the electrical connections may not be made correctly, or at all (including as discussed in the title text).&lt;br /&gt;
* Even if initially tied correctly, knots can slip or distort when subsequently pulled more taught.&lt;br /&gt;
* The external conducting patches of the cable are an uncommon feature of electrical junctions, with issues in both high-power and low-power situations.&lt;br /&gt;
** If the cables are supposed to carry high voltages, any bare conductors ought to be safely isolated from easy contact with equipment/people. In particular, plugs and sockets that carry anything approaching mains-voltages have active and passive elements integrated which protect the person connecting or disconnecting the equipment. There is no physical precaution visible to prevent the person tying or untying the cable from potential shock, who must rely upon the ''other'' end of the potentially 'live' cable being disconnected. And, when left unattended, there would continue to be a high risk of injury (including death), fire or more basic damage due to the lack of any proper physical isolation.&lt;br /&gt;
** Low-voltage cables that pass signals between equipment (e.g. networking data or audio signals) are susceptible to external contact disrupting the flow. Random static charges, built up and transfered into the connector, instead make other equipment or people the potential threat to the cabled-up equipment. Or at least disrupt the normal purpose of the cable, where a more standard plug-and-socket/hard-wired connection would not.&lt;br /&gt;
&lt;br /&gt;
The title text says that a left-handed sheet bend would provide a weaker connection. The difference between a left-handed and right-handed sheet knot is that the two free ends of the knotted 'cords' are in the same orientation for a right-handed sheet knot (here, both on the lower side of the image), but on opposite sides for a left-handed sheet knot. A left-handed sheet bend provides less strength to the knot, due to the possibility of distorting (e.g. {{w|Knot#Capsizing|''capsizing''}}) and/or allowing one or both cables to pull through the knot.&lt;br /&gt;
&lt;br /&gt;
This makes the title text a pun on the double meaning of &amp;quot;moderate load&amp;quot;, which could be a moderate amount of physical tension applied through the cables ''or'' a moderate amount of electrical current passing through them. Together, it would be expected that tension drawing two conductive surfaces together would create less resistance between them, strengthening the electrical connection as well, but only if the knot holds as expected.&lt;br /&gt;
&lt;br /&gt;
Knots was also the subject of the relatively recent [[2738: Omniknot]].&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[Above the drawing there is a header. Below the header there is a double-core wire going in from the left and stopping just past the middle of the picture. It shows how the inside of the wire looks and how the silver and golden wires inside are connected to two rectangular pieces of silver and golden material respectively. The golden piece is to the left and the silver piece to the right, closest to the end of the wire. Beneath this wire is shown two double-core wires forming a knot of the sheet bend type. Here it becomes clear that the silver and golden pieces are on the outside of the wires (but connected to the wires running inside the wires). In the knotted part of the wires gold touches gold and silver touches silver, without them touching the other color. Beneath this knot there is a label for the connector.]&lt;br /&gt;
:Cursed Connectors #46:&lt;br /&gt;
:The Sheet Bend&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Cursed Connectors]]&lt;br /&gt;
[[Category:Comics with color]]&lt;/div&gt;</summary>
		<author><name>172.70.210.41</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=2830:_Haunted_House&amp;diff=323989</id>
		<title>2830: Haunted House</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=2830:_Haunted_House&amp;diff=323989"/>
				<updated>2023-09-19T16:40:47Z</updated>
		
		<summary type="html">&lt;p&gt;172.70.210.41: /* Explanation */ add note&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 2830&lt;br /&gt;
| date      = September 18, 2023&lt;br /&gt;
| title     = Haunted House&lt;br /&gt;
| image     = haunted_house_2x.png&lt;br /&gt;
| imagesize = 278x349px&lt;br /&gt;
| noexpand  = true&lt;br /&gt;
| titletext = You can leave at any time through the door over there. It's a Louisville door, so you'll need to find a compatible knob. No, don't be silly, that one is a Lexington knob! Of course it won't fit.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|Created by a BOWLING GREEN-PADUCAH DOORKNOB ADAPTER - Please change this comment when editing this page. Do NOT delete this tag too soon.}}&lt;br /&gt;
The ISO ({{w|International Organization for Standardization}}) and ANSI ({{w|American National Standards Institute}}) are organizations that create standards for commonly used objects such as electrical sockets, preferably so that there would exist standardized forms everywhere (or at least across large areas). The comic depicts an office Halloween party, which is a common event on the celebration of Halloween. A &amp;quot;{{w|Haunted attraction (simulated)|haunted house}}&amp;quot; is a house or other building/room designed to induce fright in the participants, typically by including well-known/cultural scary elements such as vampires or zombies. The haunted house in this comic is tailored to scare members of these organizations by suggesting a world where nothing is standardized (e.g. different electrical wiring from state to state). The title text furthers the joke by implying that something which is usually standardized (door/doorknob interfaces) would be different from city to city even within a state (Kentucky, in this case). Further, it confounds ''types'' of &amp;quot;knobs&amp;quot;, where &amp;quot;[https://www.google.com/search?client=firefox-b-1-e&amp;amp;q=lexington+knobs Lexington]&amp;quot; is a hardware style collection for actual drawer knobs and such, whereas the &amp;quot;{{w|Louisville Knobs}}&amp;quot; are a set of geological mound features in the region.&lt;br /&gt;
&lt;br /&gt;
In reality, electrical current is standardized within any given country ({{w|Electricity sector in Japan|usually...}}), but it does vary worldwide, with different countries providing different voltages, frequency, and outlet shapes. The International Electrotechnical Commission maintains [https://www.iec.ch/world-plugs a web site where these differences are catalogued.] International travelers often require adapters that will plug into different outlets and adjust the current to one their devices can use.&lt;br /&gt;
&lt;br /&gt;
Other comics about standardization include [[927: Standards]], [[1179: ISO 8601]], [[1643: Degrees]].&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
{{incomplete transcript|Do NOT delete this tag too soon.}}&lt;br /&gt;
&lt;br /&gt;
:Ponytail: Welcome! If you need to charge your phones, note that this house has Pennsylvania wiring, but we have New Jersey and Delaware adapters available.&lt;br /&gt;
:Megan and Cueball: AAAAAA!&lt;br /&gt;
&lt;br /&gt;
:[Caption below the panel:]&lt;br /&gt;
:The haunted house at the ISO/ANSI office Halloween party&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Comics featuring Ponytail]]&lt;br /&gt;
[[Category:Comics featuring Megan]]&lt;br /&gt;
[[Category:Comics featuring Cueball]]&lt;/div&gt;</summary>
		<author><name>172.70.210.41</name></author>	</entry>

	</feed>