<?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=Cmancone</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=Cmancone"/>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php/Special:Contributions/Cmancone"/>
		<updated>2026-04-26T02:13:48Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.30.0</generator>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134350</id>
		<title>1791: Telescopes: Refractor vs Reflector</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134350"/>
				<updated>2017-01-27T16:33:23Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: /* The real problems with refractor telescopes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1791&lt;br /&gt;
| date      = January 27, 2017&lt;br /&gt;
| title     = Telescopes: Refractor vs Reflector&lt;br /&gt;
| image     = telescopes_refractor_vs_reflector.png&lt;br /&gt;
| titletext = On the other hand, the refractor's limited light-gathering means it's unable to make out shadow people or the dark god Chernabog.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|The section [[#The real problems with refractor telescopes|The real problems with refractor telescopes]] could need someone with a major in optics looking over it. And probably the rest could also be smartened up?}}&lt;br /&gt;
This comic compares two types of telescopes: {{w|Refracting Telescope}} vs {{w|reflecting telescope}}. &lt;br /&gt;
&lt;br /&gt;
It first looks like the comic is simply trying to show that refracting has many flaws, such as expense, size and visibility (see more [[#The real problems with refractor telescopes|details below]]). However, the punchline invalidates these complaints with the (apparently major) flaw listed with the reflecting telescope: It can't see space vampires. &lt;br /&gt;
&lt;br /&gt;
The unstated reason for this is that {{w|vampires}}, {{w|Vampire#Apotropaics|according to some cultures}}, cannot be seen in a mirror. As {{w|space vampires}} (like earth vampires) are widely believed to be {{w|Vampire#Origins_of_vampire_beliefs|made up}} and thus unlikely to interest most stargazers, this complaint is superfluous, and the reflecting telescope effectively has no flaws in comparison to the refracting telescope.&lt;br /&gt;
&lt;br /&gt;
The eyepiece of the refracting telescope appears to include either a mirror or a prism (possibly {{w|Porro prism}} or {{w|Amici roof prism}}). These make the image upright and allow the observer to look through the telescope from a more comfortable position. A mirror would invalidate the advantage it has over reflecting telescopes, but as can be seen on the Wikipedia page for Refracting telescope  {{w|Refracting_telescope#Refracting_telescope_designs|it does not need the mirror}} drawn by [[Randall]]. So in principle such a telescope could then see vampires that do not show up in mirrors. But Randall's version would not be able to do so because of the mirror at the base. So it is for sure an error if it should be explained by the mirror folklore. Frequently, however, the right-angle transition at the base of the refractor telescope is done with a prism (an &amp;quot;image erector&amp;quot;). This uses the optical principle of total internal reflection. Since mirror-non-appearance of vampires is presumably due to the interaction of evil with silver, the refractor could still see vampires. On this theory, however, the reflector could too, since modern astronomical mirrors are coated with aluminum, not silver.&lt;br /&gt;
&lt;br /&gt;
The title text expands on the seeing of supernatural beings, as another negative point is added to the refracting telescope; it apparently can't see {{w|Shadow person|Shadow People}} or the Slavic god {{w|Chernobog}}, both of which are apparently equally important to the telescope's merit despite neither the {{w|Shadow_person#History_and_folklore|shadow people}} or {{w|Chernobog#Folklore|the god}} exists. In reality, &amp;quot;shadow people&amp;quot; are a psychological phenomenon wherein humans ascribe human shapes and movements to shadows in dark spaces. Chernabog is a 12th century Slavic diety, whose name translates to ''black god''. His most famous appearance in modern media was in the 1940 Disney movie {{w|Fantasia (1940 film)|''Fantasia''}}. Because shadows are dark and the god is also dark, they cannot be seen by the refracting telescope due to the reduced light-gathering which has already been mentioned as a drawback in the main comic.&lt;br /&gt;
&lt;br /&gt;
Telescopes has been the subject of [[:Category:Telescopes|many comics]] on xkcd. Recently one about space telescope was released [[1730: Starshade]] and before that a large &amp;quot;private&amp;quot; telescope was shown in [[1522: Astronomy]].&lt;br /&gt;
&lt;br /&gt;
==The real problems with refractor telescopes==&lt;br /&gt;
The basic performance of a telescope is determined by its size: a wider telescope catches more light, making it easier to see faint objects, while a longer telescope is better for high magnification viewing. For looking at stars, the width is actually more important. No matter how much you zoom, a star is too far away to make bigger, but with a big aperture, you can see stars too faint for the naked eye. Planets benefit more from magnification, and distant galaxies need both.&lt;br /&gt;
&lt;br /&gt;
In both respects, it's much easier to make a big reflector telescope than a big refractor one. Since a lens can only be held in place by its edge, the center of a large lens sags due to gravity, distorting the images it produces. This means most reflector telescopes make do with narrow apertures only a couple of inches across. Reflector telescopes are sometimes called &amp;quot;light buckets&amp;quot; because they can have extremely big openings that can catch light from even very faint stars. In addition, because it has a mirror at one end, the reflector telescope is, in effect, twice as long as it appears - a refractor just cannot compete.&lt;br /&gt;
&lt;br /&gt;
For Randall's points:&lt;br /&gt;
&lt;br /&gt;
*More expensive&lt;br /&gt;
**Grinding a high quality lens is more expensive than producing an equivalent mirror - {{w|Crown glass (optics)|crown glass}}, which is needed for good quality telescope lenses, is expensive.&lt;br /&gt;
*Less compact&lt;br /&gt;
**In theory, a refractor ''could'' be made compact, but the image quality would be awful, because the lens would have to be extremely fat. The longer the telescope is, the less dramatic the focusing needs to be. &lt;br /&gt;
*{{w|Chromatic aberration}}:&lt;br /&gt;
**In optics, chromatic aberration is an effect resulting from dispersion in which there is a failure of a lens to focus all colors to the same convergence point, producing a rainbow effect around the image familiar to people who glasses with prisms. It occurs because lenses have different refractive indices for different wavelengths of light. Each colour is therefore focused slightly differently by the lens. Mirrors don't have chromatic aberration, since the light is reflected off the front of the mirror. The {{w|achromatic lens}} can reverse this effect, but it's expensive and its size is limited. Nevertheless, before telescope mirrors were perfected in the early 20th century, the best telescopes were achromatic refractors.&lt;br /&gt;
***Note that this effect has also been mentioned in relation to photography by [[Black Hat]] in [[1014: Car Problems]], in a completely different context, but shows this is an issue Randall has considered before.&lt;br /&gt;
*Reduced light-gathering&lt;br /&gt;
**Apart from generally needing to be smaller than reflector telescopes a further problem comes from glass defects, striae or small air bubbles trapped within the glass. In addition, glass is opaque to certain wavelengths, and even visible light is dimmed by reflection and absorption when it crosses the air-glass interfaces and passes through the glass itself. All of this reduce the light gathered.&lt;br /&gt;
*Suspending a lens&lt;br /&gt;
**Another important difference (and a big reason why large refracting telescopes don't exist) is that the lens of a refracting telescope has to be supported by the edges, so that light can pass through it.  As a result there comes a point where it is no longer feasible to mount a large lens in a telescope due to its weight and the need to support it from the edges.  In contrast the mirror of a reflecting telescope is supported from behind, and any support structures for the primary mirror are not in the path of the light.  As a result, substantially larger mirrors can be easily mounted and supported.  As an additional benefit this behind-the-mirror support has led to the creation of {{w|Adaptive_Optics|Adaptive Optics}}, a technique (which is impossible for refracting telescopes) that allows some of the atmosphere's distortions to be corrected for.&lt;br /&gt;
**Finally, a mirror can be segmented to make a larger reflecting surface out of smaller (and hence easier to build/mount/support) mirrors.  By using a {{w|Segmented_mirror|segmented mirror}} it is possible to build an effective aperture much larger than what could be built even from a single mirror, which is itself much larger than the largest possible lens that might be built for a refracting telescope.&lt;br /&gt;
&lt;br /&gt;
It is worth noting that:&lt;br /&gt;
:'''A reflecting telescope also has disadvantages compared to a refracting telescope'''.  &lt;br /&gt;
*The main disadvantage is that in almost all reflecting telescope designs the focal point is directly in front of the mirror, i.e. in between the mirror and the target of interest.  &lt;br /&gt;
**As a result a {{w|Secondary_mirror|secondary mirror}} is commonly used to direct the focal point somewhere outside of the field of view.  However, this secondary mirror (and the struts that support it) will still block part of the field of view - although the focus of the telescope means that the secondary mirror is not visible when looking at distant objects, it will result in diffraction patterns that also hinder the image quality.  In fact, this is the source of the {{w|Diffraction_spike|diffraction spikes}} around stars which are commonly seen in astronomical images. &lt;br /&gt;
*A reflecting telescope is also harder to maintain:&lt;br /&gt;
**The mirrors need to be very precisely aligned (this is called collimation), and this can be a laborious process. They may also need re-polishing.&lt;br /&gt;
**The telescope is open at one end, allowing dust and dirt to enter.&lt;br /&gt;
*A reflecting telescope is not very portable. This is why birdspotters use small refractor telescopes as an easy way to get a closer view of birds.&lt;br /&gt;
&lt;br /&gt;
Despite this disadvantage, reflecting telescopes are used almost exclusively in modern astronomy because of practical limitations in making large refracting telescopes. Very few amateur astronomers use refracting telescopes - nowadays, they most exist to con people looking for Christmas presents in department stores (just because a telescope promises 100x zoom doesn't mean the image quality is any good!)&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[A one panel comic showing two different telescope designs next to each other with labels above them and a bullet list of points below the them. The left drawing will be described first then the right.]&lt;br /&gt;
&lt;br /&gt;
:[Left:]&lt;br /&gt;
:&amp;lt;big&amp;gt;Refractor&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:[A slim telescope design is shown. At the top the light enters shown in a light yellow shade between two thin parallel light gray lines that just fits inside the opening of the telescope which is slightly wider at the top than at the lens sitting a short way into the opening. The lens causes the light to focus just where the telescope again changes dimensions, and the light enters a small opening at the bottom of the long pipe of the telescope. Here the yellow light is a point as the two gray lines cross each other at that point. The light then broadens slightly again and the thin yellow light cone hits a mirror at the bottom of the telescope and is reflected to the left and out through the eyepiece. Below are the following points:]&lt;br /&gt;
:*More expensive&lt;br /&gt;
:*Less compact&lt;br /&gt;
:*Chromatic aberration&lt;br /&gt;
:*Reduced light-gathering&lt;br /&gt;
&lt;br /&gt;
:[Right]&lt;br /&gt;
:&amp;lt;big&amp;gt;Reflector&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:[A much broader (more than 150% of the first) but also much shorter (66%) telescope design is shown. At the top the light enters shown in a light yellow shade between two thin parallel light gray lines that still just fits inside the opening of the telescope. On it's way down to the bottom of the telescope the light passes by a small mirror turned down towards the bottom. When the hits the curved bottom mirror light is focus on it's way back back and a small light cone hits the small mirror mentioned before sitting almost at the top of the telescope. This mirror reflects the light to the left into an even thinner light cone that goes out through the eyepiece located near the top of the telescope. Below are the following point:]&lt;br /&gt;
:*Can't see space vampires&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Comics with color]]&lt;br /&gt;
[[Category:Telescopes]]&lt;br /&gt;
[[Category:Rankings]]&lt;br /&gt;
[[Category:Science]]&lt;br /&gt;
[[Category:Astronomy]]&lt;br /&gt;
[[Category:Space]]&lt;br /&gt;
[[Category:Religion]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134349</id>
		<title>1791: Telescopes: Refractor vs Reflector</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134349"/>
				<updated>2017-01-27T16:31:43Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: /* The real problems with refractor telescopes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1791&lt;br /&gt;
| date      = January 27, 2017&lt;br /&gt;
| title     = Telescopes: Refractor vs Reflector&lt;br /&gt;
| image     = telescopes_refractor_vs_reflector.png&lt;br /&gt;
| titletext = On the other hand, the refractor's limited light-gathering means it's unable to make out shadow people or the dark god Chernabog.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|The section [[#The real problems with refractor telescopes|The real problems with refractor telescopes]] could need someone with a major in optics looking over it. And probably the rest could also be smartened up?}}&lt;br /&gt;
This comic compares two types of telescopes: {{w|Refracting Telescope}} vs {{w|reflecting telescope}}. &lt;br /&gt;
&lt;br /&gt;
It first looks like the comic is simply trying to show that refracting has many flaws, such as expense, size and visibility (see more [[#The real problems with refractor telescopes|details below]]). However, the punchline invalidates these complaints with the (apparently major) flaw listed with the reflecting telescope: It can't see space vampires. &lt;br /&gt;
&lt;br /&gt;
The unstated reason for this is that {{w|vampires}}, {{w|Vampire#Apotropaics|according to some cultures}}, cannot be seen in a mirror. As {{w|space vampires}} (like earth vampires) are widely believed to be {{w|Vampire#Origins_of_vampire_beliefs|made up}} and thus unlikely to interest most stargazers, this complaint is superfluous, and the reflecting telescope effectively has no flaws in comparison to the refracting telescope.&lt;br /&gt;
&lt;br /&gt;
The eyepiece of the refracting telescope appears to include either a mirror or a prism (possibly {{w|Porro prism}} or {{w|Amici roof prism}}). These make the image upright and allow the observer to look through the telescope from a more comfortable position. A mirror would invalidate the advantage it has over reflecting telescopes, but as can be seen on the Wikipedia page for Refracting telescope  {{w|Refracting_telescope#Refracting_telescope_designs|it does not need the mirror}} drawn by [[Randall]]. So in principle such a telescope could then see vampires that do not show up in mirrors. But Randall's version would not be able to do so because of the mirror at the base. So it is for sure an error if it should be explained by the mirror folklore. Frequently, however, the right-angle transition at the base of the refractor telescope is done with a prism (an &amp;quot;image erector&amp;quot;). This uses the optical principle of total internal reflection. Since mirror-non-appearance of vampires is presumably due to the interaction of evil with silver, the refractor could still see vampires. On this theory, however, the reflector could too, since modern astronomical mirrors are coated with aluminum, not silver.&lt;br /&gt;
&lt;br /&gt;
The title text expands on the seeing of supernatural beings, as another negative point is added to the refracting telescope; it apparently can't see {{w|Shadow person|Shadow People}} or the Slavic god {{w|Chernobog}}, both of which are apparently equally important to the telescope's merit despite neither the {{w|Shadow_person#History_and_folklore|shadow people}} or {{w|Chernobog#Folklore|the god}} exists. In reality, &amp;quot;shadow people&amp;quot; are a psychological phenomenon wherein humans ascribe human shapes and movements to shadows in dark spaces. Chernabog is a 12th century Slavic diety, whose name translates to ''black god''. His most famous appearance in modern media was in the 1940 Disney movie {{w|Fantasia (1940 film)|''Fantasia''}}. Because shadows are dark and the god is also dark, they cannot be seen by the refracting telescope due to the reduced light-gathering which has already been mentioned as a drawback in the main comic.&lt;br /&gt;
&lt;br /&gt;
Telescopes has been the subject of [[:Category:Telescopes|many comics]] on xkcd. Recently one about space telescope was released [[1730: Starshade]] and before that a large &amp;quot;private&amp;quot; telescope was shown in [[1522: Astronomy]].&lt;br /&gt;
&lt;br /&gt;
==The real problems with refractor telescopes==&lt;br /&gt;
The basic performance of a telescope is determined by its size: a wider telescope catches more light, making it easier to see faint objects, while a longer telescope is better for high magnification viewing. For looking at stars, the width is actually more important. No matter how much you zoom, a star is too far away to make bigger, but with a big aperture, you can see stars too faint for the naked eye. Planets benefit more from magnification, and distant galaxies need both.&lt;br /&gt;
&lt;br /&gt;
In both respects, it's much easier to make a big reflector telescope than a big refractor one. Since a lens can only be held in place by its edge, the center of a large lens sags due to gravity, distorting the images it produces. This means most reflector telescopes make do with narrow apertures only a couple of inches across. Reflector telescopes are sometimes called &amp;quot;light buckets&amp;quot; because they can have extremely big openings that can catch light from even very faint stars. In addition, because it has a mirror at one end, the reflector telescope is, in effect, twice as long as it appears - a refractor just cannot compete.&lt;br /&gt;
&lt;br /&gt;
For Randall's points:&lt;br /&gt;
&lt;br /&gt;
*More expensive&lt;br /&gt;
**Grinding a high quality lens is more expensive than producing an equivalent mirror - {{w|Crown glass (optics)|crown glass}}, which is needed for good quality telescope lenses, is expensive.&lt;br /&gt;
*Less compact&lt;br /&gt;
**In theory, a refractor ''could'' be made compact, but the image quality would be awful, because the lens would have to be extremely fat. The longer the telescope is, the less dramatic the focusing needs to be. &lt;br /&gt;
*{{w|Chromatic aberration}}:&lt;br /&gt;
**In optics, chromatic aberration is an effect resulting from dispersion in which there is a failure of a lens to focus all colors to the same convergence point, producing a rainbow effect around the image familiar to people who glasses with prisms. It occurs because lenses have different refractive indices for different wavelengths of light. Each colour is therefore focused slightly differently by the lens. Mirrors don't have chromatic aberration, since the light is reflected off the front of the mirror. The {{w|achromatic lens}} can reverse this effect, but it's expensive and its size is limited. Nevertheless, before telescope mirrors were perfected in the early 20th century, the best telescopes were achromatic refractors.&lt;br /&gt;
***Note that this effect has also been mentioned in relation to photography by [[Black Hat]] in [[1014: Car Problems]], in a completely different context, but shows this is an issue Randall has considered before.&lt;br /&gt;
*Reduced light-gathering&lt;br /&gt;
**Apart from generally needing to be smaller than reflector telescopes a further problem comes from glass defects, striae or small air bubbles trapped within the glass. In addition, glass is opaque to certain wavelengths, and even visible light is dimmed by reflection and absorption when it crosses the air-glass interfaces and passes through the glass itself. All of this reduce the light gathered.&lt;br /&gt;
*Suspending a lens&lt;br /&gt;
**Another important difference (and a big reason why large refracting telescopes don't exist) is that the lens of a refracting telescope has to be supported by the edges, so that light can pass through it.  As a result there comes a point where it is no longer feasible to mount a large lens in a telescope due to its weight and the need to support it from the edges.  In contrast the mirror of a reflecting telescope is supported from behind, and any support structures for the primary mirror are not in the path of the light.  As a result, substantially larger mirrors can be easily mounted and supported.  As an additional benefit this behind-the-mirror support has led to the creation of {{w|Adaptive_Optics|Adaptive Optics}}, a technique (which is impossible for refracting telescopes) that allows some of the atmosphere's distortions to be corrected for.&lt;br /&gt;
**Finally, a mirror can be segmented to make a larger reflecting surface out of smaller (and hence easier to build/mount/support) mirrors.  By using a {{w|Segmented Mirror}} it is possible to build an effective aperture much larger than what could be built even from a single mirror, which is itself much larger than the largest possible lens that might be built for a refracting telescope.&lt;br /&gt;
&lt;br /&gt;
It is worth noting that:&lt;br /&gt;
:'''A reflecting telescope also has disadvantages compared to a refracting telescope'''.  &lt;br /&gt;
*The main disadvantage is that in almost all reflecting telescope designs the focal point is directly in front of the mirror, i.e. in between the mirror and the target of interest.  &lt;br /&gt;
**As a result a {{w|Secondary_mirror|secondary mirror}} is commonly used to direct the focal point somewhere outside of the field of view.  However, this secondary mirror (and the struts that support it) will still block part of the field of view - although the focus of the telescope means that the secondary mirror is not visible when looking at distant objects, it will result in diffraction patterns that also hinder the image quality.  In fact, this is the source of the {{w|Diffraction_spike|diffraction spikes}} around stars which are commonly seen in astronomical images. &lt;br /&gt;
*A reflecting telescope is also harder to maintain:&lt;br /&gt;
**The mirrors need to be very precisely aligned (this is called collimation), and this can be a laborious process. They may also need re-polishing.&lt;br /&gt;
**The telescope is open at one end, allowing dust and dirt to enter.&lt;br /&gt;
*A reflecting telescope is not very portable. This is why birdspotters use small refractor telescopes as an easy way to get a closer view of birds.&lt;br /&gt;
&lt;br /&gt;
Despite this disadvantage, reflecting telescopes are used almost exclusively in modern astronomy because of practical limitations in making large refracting telescopes. Very few amateur astronomers use refracting telescopes - nowadays, they most exist to con people looking for Christmas presents in department stores (just because a telescope promises 100x zoom doesn't mean the image quality is any good!)&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[A one panel comic showing two different telescope designs next to each other with labels above them and a bullet list of points below the them. The left drawing will be described first then the right.]&lt;br /&gt;
&lt;br /&gt;
:[Left:]&lt;br /&gt;
:&amp;lt;big&amp;gt;Refractor&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:[A slim telescope design is shown. At the top the light enters shown in a light yellow shade between two thin parallel light gray lines that just fits inside the opening of the telescope which is slightly wider at the top than at the lens sitting a short way into the opening. The lens causes the light to focus just where the telescope again changes dimensions, and the light enters a small opening at the bottom of the long pipe of the telescope. Here the yellow light is a point as the two gray lines cross each other at that point. The light then broadens slightly again and the thin yellow light cone hits a mirror at the bottom of the telescope and is reflected to the left and out through the eyepiece. Below are the following points:]&lt;br /&gt;
:*More expensive&lt;br /&gt;
:*Less compact&lt;br /&gt;
:*Chromatic aberration&lt;br /&gt;
:*Reduced light-gathering&lt;br /&gt;
&lt;br /&gt;
:[Right]&lt;br /&gt;
:&amp;lt;big&amp;gt;Reflector&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:[A much broader (more than 150% of the first) but also much shorter (66%) telescope design is shown. At the top the light enters shown in a light yellow shade between two thin parallel light gray lines that still just fits inside the opening of the telescope. On it's way down to the bottom of the telescope the light passes by a small mirror turned down towards the bottom. When the hits the curved bottom mirror light is focus on it's way back back and a small light cone hits the small mirror mentioned before sitting almost at the top of the telescope. This mirror reflects the light to the left into an even thinner light cone that goes out through the eyepiece located near the top of the telescope. Below are the following point:]&lt;br /&gt;
:*Can't see space vampires&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Comics with color]]&lt;br /&gt;
[[Category:Telescopes]]&lt;br /&gt;
[[Category:Rankings]]&lt;br /&gt;
[[Category:Science]]&lt;br /&gt;
[[Category:Astronomy]]&lt;br /&gt;
[[Category:Space]]&lt;br /&gt;
[[Category:Religion]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134347</id>
		<title>1791: Telescopes: Refractor vs Reflector</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134347"/>
				<updated>2017-01-27T16:22:04Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: /* The real problems with refractor telescopes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1791&lt;br /&gt;
| date      = January 27, 2017&lt;br /&gt;
| title     = Telescopes: Refractor vs Reflector&lt;br /&gt;
| image     = telescopes_refractor_vs_reflector.png&lt;br /&gt;
| titletext = On the other hand, the refractor's limited light-gathering means it's unable to make out shadow people or the dark god Chernabog.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|The section [[#The real problems with refractor telescopes|The real problems with refractor telescopes]] could need someone with a major in optics looking over it. And probably the rest could also be smartened up?}}&lt;br /&gt;
This comic compares two types of telescopes: {{w|Refracting Telescope}} vs {{w|reflecting telescope}}. &lt;br /&gt;
&lt;br /&gt;
It first looks like the comic is simply trying to show that refracting has many flaws, such as expense, size and visibility (see more [[#The real problems with refractor telescopes|details below]]). However, the punchline invalidates these complaints with the (apparently major) flaw listed with the reflecting telescope: It can't see space vampires. &lt;br /&gt;
&lt;br /&gt;
The unstated reason for this is that {{w|vampires}}, {{w|Vampire#Apotropaics|according to some cultures}}, cannot be seen in a mirror. As {{w|space vampires}} (like earth vampires) are widely believed to be {{w|Vampire#Origins_of_vampire_beliefs|made up}} and thus unlikely to interest most stargazers, this complaint is superfluous, and the reflecting telescope effectively has no flaws in comparison to the refracting telescope.&lt;br /&gt;
&lt;br /&gt;
The eyepiece of the refracting telescope appears to include either a mirror or a prism (possibly {{w|Porro prism}} or {{w|Amici roof prism}}). These make the image upright and allow the observer to look through the telescope from a more comfortable position. A mirror would invalidate the advantage it has over reflecting telescopes, but as can be seen on the Wikipedia page for Refracting telescope  {{w|Refracting_telescope#Refracting_telescope_designs|it does not need the mirror}} drawn by [[Randall]]. So in principle such a telescope could then see vampires that do not show up in mirrors. But Randall's version would not be able to do so because of the mirror at the base. So it is for sure an error if it should be explained by the mirror folklore. Frequently, however, the right-angle transition at the base of the refractor telescope is done with a prism (an &amp;quot;image erector&amp;quot;). This uses the optical principle of total internal reflection. Since mirror-non-appearance of vampires is presumably due to the interaction of evil with silver, the refractor could still see vampires. On this theory, however, the reflector could too, since modern astronomical mirrors are coated with aluminum, not silver.&lt;br /&gt;
&lt;br /&gt;
The title text expands on the seeing of supernatural beings, as another negative point is added to the refracting telescope; it apparently can't see {{w|Shadow person|Shadow People}} or the Slavic god {{w|Chernobog}}, both of which are apparently equally important to the telescope's merit despite neither the {{w|Shadow_person#History_and_folklore|shadow people}} or {{w|Chernobog#Folklore|the god}} exists. In reality, &amp;quot;shadow people&amp;quot; are a psychological phenomenon wherein humans ascribe human shapes and movements to shadows in dark spaces. Chernabog is a 12th century Slavic diety, whose name translates to ''black god''. His most famous appearance in modern media was in the 1940 Disney movie {{w|Fantasia (1940 film)|''Fantasia''}}. Because shadows are dark and the god is also dark, they cannot be seen by the refracting telescope due to the reduced light-gathering which has already been mentioned as a drawback in the main comic.&lt;br /&gt;
&lt;br /&gt;
Telescopes has been the subject of [[:Category:Telescopes|many comics]] on xkcd. Recently one about space telescope was released [[1730: Starshade]] and before that a large &amp;quot;private&amp;quot; telescope was shown in [[1522: Astronomy]].&lt;br /&gt;
&lt;br /&gt;
==The real problems with refractor telescopes==&lt;br /&gt;
The basic performance of a telescope is determined by its size: a wider telescope catches more light, making it easier to see faint objects, while a longer telescope is better for high magnification viewing. For looking at stars, the width is actually more important. No matter how much you zoom, a star is too far away to make bigger, but with a big aperture, you can see stars too faint for the naked eye. Planets benefit more from magnification, and distant galaxies need both.&lt;br /&gt;
&lt;br /&gt;
In both respects, it's much easier to make a big reflector telescope than a big refractor one. Since a lens can only be held in place by its edge, the center of a large lens sags due to gravity, distorting the images it produces. This means most reflector telescopes make do with narrow apertures only a couple of inches across. Reflector telescopes are sometimes called &amp;quot;light buckets&amp;quot; because they can have extremely big openings that can catch light from even very faint stars. In addition, because it has a mirror at one end, the reflector telescope is, in effect, twice as long as it appears - a refractor just cannot compete.&lt;br /&gt;
&lt;br /&gt;
For Randall's points:&lt;br /&gt;
&lt;br /&gt;
*More expensive&lt;br /&gt;
**Grinding a high quality lens is more expensive than producing an equivalent mirror - {{w|Crown glass (optics)|crown glass}}, which is needed for good quality telescope lenses, is expensive.&lt;br /&gt;
*Less compact&lt;br /&gt;
**In theory, a refractor ''could'' be made compact, but the image quality would be awful, because the lens would have to be extremely fat. The longer the telescope is, the less dramatic the focusing needs to be. &lt;br /&gt;
*{{w|Chromatic aberration}}:&lt;br /&gt;
**In optics, chromatic aberration is an effect resulting from dispersion in which there is a failure of a lens to focus all colors to the same convergence point, producing a rainbow effect around the image familiar to people who glasses with prisms. It occurs because lenses have different refractive indices for different wavelengths of light. Each colour is therefore focused slightly differently by the lens. Mirrors don't have chromatic aberration, since the light is reflected off the front of the mirror. The {{w|achromatic lens}} can reverse this effect, but it's expensive and its size is limited. Nevertheless, before telescope mirrors were perfected in the early 20th century, the best telescopes were achromatic refractors.&lt;br /&gt;
***Note that this effect has also been mentioned in relation to photography by [[Black Hat]] in [[1014: Car Problems]], in a completely different context, but shows this is an issue Randall has considered before.&lt;br /&gt;
*Reduced light-gathering&lt;br /&gt;
**Apart from generally needing to be smaller than reflector telescopes a further problem comes from glass defects, striae or small air bubbles trapped within the glass. In addition, glass is opaque to certain wavelengths, and even visible light is dimmed by reflection and absorption when it crosses the air-glass interfaces and passes through the glass itself. All of this reduce the light gathered.&lt;br /&gt;
*Suspending a lens&lt;br /&gt;
**Another important difference (and a big reason why large refracting telescopes don't exist) is that the lens of a refracting telescope has to be supported by the edges, so that light can pass through it.  As a result there comes a point where it is no longer feasible to mount a large lens in a telescope due to its weight and the need to support it from the edges.  In contrast the mirror of a reflecting telescope is supported from behind, and any support structures for the primary mirror are not in the path of the light.  As a result, substantially larger mirrors can be easily mounted and supported.  As an additional benefit this behind-the-mirror support has led to the creation of {{w|Adaptive_Optics|Adaptive Optics}}, a technique (which is impossible for refracting telescopes) that allows some of the atmosphere's distortions to be corrected for.&lt;br /&gt;
&lt;br /&gt;
It is worth noting that:&lt;br /&gt;
:'''A reflecting telescope also has disadvantages compared to a refracting telescope'''.  &lt;br /&gt;
*The main disadvantage is that in almost all reflecting telescope designs the focal point is directly in front of the mirror, i.e. in between the mirror and the target of interest.  &lt;br /&gt;
**As a result a {{w|Secondary_mirror|secondary mirror}} is commonly used to direct the focal point somewhere outside of the field of view.  However, this secondary mirror (and the struts that support it) will still block part of the field of view - although the focus of the telescope means that the secondary mirror is not visible when looking at distant objects, it will result in diffraction patterns that also hinder the image quality.  In fact, this is the source of the {{w|Diffraction_spike|diffraction spikes}} around stars which are commonly seen in astronomical images. &lt;br /&gt;
*A reflecting telescope is also harder to maintain:&lt;br /&gt;
**The mirrors need to be very precisely aligned (this is called collimation), and this can be a laborious process. They may also need re-polishing.&lt;br /&gt;
**The telescope is open at one end, allowing dust and dirt to enter.&lt;br /&gt;
*A reflecting telescope is not very portable. This is why birdspotters use small refractor telescopes as an easy way to get a closer view of birds.&lt;br /&gt;
&lt;br /&gt;
Despite this disadvantage, reflecting telescopes are used almost exclusively in modern astronomy because of practical limitations in making large refracting telescopes. Very few amateur astronomers use refracting telescopes - nowadays, they most exist to con people looking for Christmas presents in department stores (just because a telescope promises 100x zoom doesn't mean the image quality is any good!)&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[A one panel comic showing two different telescope designs next to each other with labels above them and a bullet list of points below the them. The left drawing will be described first then the right.]&lt;br /&gt;
&lt;br /&gt;
:[Left:]&lt;br /&gt;
:&amp;lt;big&amp;gt;Refractor&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:[A slim telescope design is shown. At the top the light enters shown in a light yellow shade between two thin parallel light gray lines that just fits inside the opening of the telescope which is slightly wider at the top than at the lens sitting a short way into the opening. The lens causes the light to focus just where the telescope again changes dimensions, and the light enters a small opening at the bottom of the long pipe of the telescope. Here the yellow light is a point as the two gray lines cross each other at that point. The light then broadens slightly again and the thin yellow light cone hits a mirror at the bottom of the telescope and is reflected to the left and out through the eyepiece. Below are the following points:]&lt;br /&gt;
:*More expensive&lt;br /&gt;
:*Less compact&lt;br /&gt;
:*Chromatic aberration&lt;br /&gt;
:*Reduced light-gathering&lt;br /&gt;
&lt;br /&gt;
:[Right]&lt;br /&gt;
:&amp;lt;big&amp;gt;Reflector&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:[A much broader (more than 150% of the first) but also much shorter (66%) telescope design is shown. At the top the light enters shown in a light yellow shade between two thin parallel light gray lines that still just fits inside the opening of the telescope. On it's way down to the bottom of the telescope the light passes by a small mirror turned down towards the bottom. When the hits the curved bottom mirror light is focus on it's way back back and a small light cone hits the small mirror mentioned before sitting almost at the top of the telescope. This mirror reflects the light to the left into an even thinner light cone that goes out through the eyepiece located near the top of the telescope. Below are the following point:]&lt;br /&gt;
:*Can't see space vampires&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Comics with color]]&lt;br /&gt;
[[Category:Telescopes]]&lt;br /&gt;
[[Category:Rankings]]&lt;br /&gt;
[[Category:Science]]&lt;br /&gt;
[[Category:Astronomy]]&lt;br /&gt;
[[Category:Space]]&lt;br /&gt;
[[Category:Religion]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134286</id>
		<title>1791: Telescopes: Refractor vs Reflector</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134286"/>
				<updated>2017-01-27T14:36:49Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: /* Explanation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1791&lt;br /&gt;
| date      = January 27, 2017&lt;br /&gt;
| title     = Telescopes: Refractor vs Reflector&lt;br /&gt;
| image     = telescopes_refractor_vs_reflector.png&lt;br /&gt;
| titletext = On the other hand, the refractor's limited light-gathering means it's unable to make out shadow people or the dark god Chernabog.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
This comic shows two types of telescopes: {{w|Reflecting Telescope|Reflecting}} and {{w|Refracting Telescope|Refracting}}. It first looks like the comic is trying to show that refracting has many flaws, such as expense, size and visibility. However, the punchline invalidates these complaints with the (apparently major) flaw listed with the reflecting telescope: it can't see space vampires. The unstated reason for this is that vampires cannot be seen in a mirror. As space vampires do not exist {{Citation needed}}, this complaint is moot, and the reflecting telescope technically has no flaws in comparison to the refracting telescope. The title text expands on the seeing of supernatural beings, as another negative point is added to the refracting telescope- it apparently can't see shadow people or the Slavic god {{w|Chernabog}}, both of which are apparently equally important to the telescope's merit despite also not existing {{Citation needed}}.  Although unclear, refracting telescopes presumably can't see shadow people or Chernabog because both are &amp;quot;dark&amp;quot;, and with their smaller collecting areas, refracting telescopes do a worse job of seeing faint things.&lt;br /&gt;
&lt;br /&gt;
An error in the comic would seem to be that both telescope illustrations contain a mirror (in the refracting, it's at the eyepiece). This would invalidate the advantage it has over reflecting.  However, refracting telescopes don't have to have a mirror: the one in the comic just happens to be drawn with one.&lt;br /&gt;
&lt;br /&gt;
The title text adds an additional drawback to a refracting telecsope: it cannot see {{w|Shadow person|Shadow People}} or {{w|Chernobog|Chernabog}}. In reality, &amp;quot;shadow people&amp;quot; are a psychological phenomenon wherein humans ascribe human shapes and movements to shadows in dark spaces. Chernabog is a 12th century Slavic diety, whose name translates to ''black god''. His most famous apperance in modern media was in the 1940 Disney movie {{w|Fantasia (1940 film)|''Fantasia''}}.&lt;br /&gt;
&lt;br /&gt;
It is worth noting that a Reflecting Telescope also has disadvantages compared to a refracting telescope.  The main disadvantage is that in almost all reflecting telescope designs the focal point is directly in front of the mirror, i.e. in between the mirror and the target of interest.  As a result a {{w|Secondary_mirror|secondary mirror}} is commonly used to direct the focal point somewhere outside of the field of view.  However, this secondary mirror (and the struts that support it) will still block part of the field of view and result in diffraction patterns that also hinder the image quality.  In fact, this is the source of the {{w|Diffraction_spike|diffraction spikes}} around stars which are commonly seen in astronomical images.  Despite this disadvantage, reflecting telescopes are used almost exclusively in modern astronomy because of practical limitations in making large refracting telescopes.&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
{{incomplete transcript}}&lt;br /&gt;
[The comic is one panel showing two different telescope designs.]&lt;br /&gt;
REFRACTOR&lt;br /&gt;
More expensive&lt;br /&gt;
Less compact&lt;br /&gt;
Chromatic aberration&lt;br /&gt;
Reduced Light-gathering&lt;br /&gt;
&lt;br /&gt;
REFLECTOR&lt;br /&gt;
Can't see space vampires&lt;br /&gt;
&lt;br /&gt;
Title text:&lt;br /&gt;
On the other hand, the refractor's limited light-gathering means it's unable to make out shadow people or the dark god Chernabog&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Comics with color]]&lt;br /&gt;
[[Category:Science]]&lt;br /&gt;
[[Category:Astronomy]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134284</id>
		<title>Talk:1791: Telescopes: Refractor vs Reflector</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134284"/>
				<updated>2017-01-27T14:31:42Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Nitpick:  The refracting telescope, drawn correctly, has a mirror in the optical path (image inverter), but it is made with a special vampire reflecting material Ichorium.&lt;br /&gt;
Doesn't the one in this image have a mirror too? at the bottom to make the image come out at the side instead of the end? [[Special:Contributions/162.158.89.187|162.158.89.187]]&lt;br /&gt;
Something went wrong on my comment - only the part after &amp;quot;doesn't&amp;quot; is from me, the part before was what i was commenting on, idk why it is not seperated [[Special:Contributions/162.158.89.187|162.158.89.187]]&lt;br /&gt;
&lt;br /&gt;
That's a good point: as drawn, the refracting telescope still has a mirror and also wouldn't be able to see space vampires.  However, the refracting telescope doesn't have to have a secondary mirror, and there are plenty that don't, so it is more the drawing that is wrong rather than the text of the comic.[[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]]) 14:31, 27 January 2017 (UTC)&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134283</id>
		<title>1791: Telescopes: Refractor vs Reflector</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134283"/>
				<updated>2017-01-27T14:29:12Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: /* Explanation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1791&lt;br /&gt;
| date      = January 27, 2017&lt;br /&gt;
| title     = Telescopes: Refractor vs Reflector&lt;br /&gt;
| image     = telescopes_refractor_vs_reflector.png&lt;br /&gt;
| titletext = On the other hand, the refractor's limited light-gathering means it's unable to make out shadow people or the dark god Chernabog.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
This comic shows two types of telescopes: {{w|Reflecting Telescope|Reflecting}} and {{w|Refracting Telescope|Refracting}}. It first looks like the comic is trying to show that refracting has many flaws, such as expense, size and visibility. However, the punchline invalidates these complaints with the (apparently major) flaw listed with the reflecting telescope: it can't see space vampires. The unstated reason for this is that vampires cannot be seen in a mirror. As space vampires do not exist {{Citation needed}}, this complaint is moot, and the reflecting telescope technically has no flaws in comparison to the refracting telescope. The title text expands on the seeing of supernatural beings, as another negative point is added to the refracting telescope- it apparently can't see shadow people or the Slavic god {{w|Chernabog}}, both of which are apparently equally important to the telescope's merit despite also not existing.  Although unclear, refracting telescopes presumably can't see shadow people or Chernabog because both are &amp;quot;dark&amp;quot;, and with their smaller collecting areas, reflecting telescopes can see fainter objects than refracting telescopes.&lt;br /&gt;
&lt;br /&gt;
An error in the comic would seem to be that both telescope illustrations contain a mirror (in the refracting, it's at the eyepiece). This would invalidate the advantage it has over reflecting.&lt;br /&gt;
&lt;br /&gt;
The title text adds an additional drawback to a refracting telecsope: it cannot see {{w|Shadow person|Shadow People}} or {{w|Chernobog|Chernabog}}. In reality, &amp;quot;shadow people&amp;quot; are a psychological phenomenon wherein humans ascribe human shapes and movements to shadows in dark spaces. Chernabog is a 12th century Slavic diety, whose name translates to ''black god''. His most famous apperance in modern media was in the 1940 Disney movie {{w|Fantasia (1940 film)|''Fantasia''}}.&lt;br /&gt;
&lt;br /&gt;
It is worth noting that a Reflecting Telescope also has disadvantages compared to a refracting telescope.  The main disadvantage is that in almost all reflecting telescope designs the focal point is directly in front of the mirror, i.e. in between the mirror and the target of interest.  As a result a {{w|Secondary_mirror|secondary mirror}} is commonly used to direct the focal point somewhere outside of the field of view.  However, this secondary mirror (and the struts that support it) will still block part of the field of view and result in diffraction patterns that also hinder the image quality.  In fact, this is the source of the {{w|Diffraction_spike|diffraction spikes}} around stars which are commonly seen in astronomical images.  Despite this disadvantage, reflecting telescopes are used almost exclusively in modern astronomy because of practical limitations in making large refracting telescopes.&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
{{incomplete transcript}}&lt;br /&gt;
[The comic is one panel showing two different telescope designs.]&lt;br /&gt;
REFRACTOR&lt;br /&gt;
More expensive&lt;br /&gt;
Less compact&lt;br /&gt;
Chromatic aberration&lt;br /&gt;
Reduced Light-gathering&lt;br /&gt;
&lt;br /&gt;
REFLECTOR&lt;br /&gt;
Can't see space vampires&lt;br /&gt;
&lt;br /&gt;
Title text:&lt;br /&gt;
On the other hand, the refractor's limited light-gathering means it's unable to make out shadow people or the dark god Chernabog&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Comics with color]]&lt;br /&gt;
[[Category:Science]]&lt;br /&gt;
[[Category:Astronomy]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134282</id>
		<title>1791: Telescopes: Refractor vs Reflector</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134282"/>
				<updated>2017-01-27T14:27:53Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: /* Explanation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1791&lt;br /&gt;
| date      = January 27, 2017&lt;br /&gt;
| title     = Telescopes: Refractor vs Reflector&lt;br /&gt;
| image     = telescopes_refractor_vs_reflector.png&lt;br /&gt;
| titletext = On the other hand, the refractor's limited light-gathering means it's unable to make out shadow people or the dark god Chernabog.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
This comic shows two types of telescopes: {{w|Reflecting Telescope|Reflecting}} and {{w|Refracting Telescope|Refracting}}. It first looks like the comic is trying to show that refracting has many flaws, such as expense, size and visibility. However, the punchline invalidates these complaints with the (apparently major) flaw listed with the reflecting telescope: it can't see space vampires. The unstated reason for this is that vampires cannot be seen in a mirror. As space vampires do not exist {{Citation needed}}, this complaint is moot, and the reflecting telescope technically has no flaws in comparison to the refracting telescope. The title text expands on the seeing of supernatural beings, as another negative point is added to the refracting telescope- it apparently can't see shadow people or the Slavic god {{w|Chernabog}}, both of which are apparently equally important to the telescope's merit despite also not existing.  Although unclear, refracting telescopes presumably can't see shadow people or Chernabog because both are &amp;quot;dark&amp;quot;, and with their smaller collecting areas, reflecting telescopes can see fainter objects than refracting telescopes.&lt;br /&gt;
&lt;br /&gt;
An error in the comic would seem to be that both telescope illustrations contain a mirror (in the refracting, it's at the eyepiece). This would invalidate the advantage it has over reflecting.&lt;br /&gt;
&lt;br /&gt;
The title text adds an additional drawback to a refracting telecsope: it cannot see {{w|Shadow person|Shadow People}} or {{w|Chernobog|Chernabog}}. In reality, &amp;quot;shadow people&amp;quot; are a psychological phenomenon wherein humans ascribe human shapes and movements to shadows in dark spaces. Chernabog is a 12th century Slavic diety, whose name translates to ''black god''. His most famous apperance in modern media was in the 1940 Disney movie {{w|Fantasia (1940 film)|''Fantasia''}}.&lt;br /&gt;
&lt;br /&gt;
It is worth noting that in reality a Reflecting Telescope also has disadvantages compared to a refracting telescope.  The main disadvantage is that in almost all reflecting telescope designs the focal point is directly in front of the mirror, i.e. in between the mirror and the target of interest.  As a result a {{w|Secondary_mirror|secondary mirror}} is commonly used to direct the focal point somewhere outside of the field of view.  However, this secondary mirror (and the struts that support it) will still block part of the field of view and result in diffraction patterns that also hinder the image quality.  In fact, this is the source of the {{w|Diffraction_spike|diffraction spikes}} around stars which are commonly seen in astronomical images.  Despite this disadvantage, reflecting telescopes are used almost exclusively in modern astronomy because of practical limitations in making large refracting telescopes.&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
{{incomplete transcript}}&lt;br /&gt;
[The comic is one panel showing two different telescope designs.]&lt;br /&gt;
REFRACTOR&lt;br /&gt;
More expensive&lt;br /&gt;
Less compact&lt;br /&gt;
Chromatic aberration&lt;br /&gt;
Reduced Light-gathering&lt;br /&gt;
&lt;br /&gt;
REFLECTOR&lt;br /&gt;
Can't see space vampires&lt;br /&gt;
&lt;br /&gt;
Title text:&lt;br /&gt;
On the other hand, the refractor's limited light-gathering means it's unable to make out shadow people or the dark god Chernabog&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Comics with color]]&lt;br /&gt;
[[Category:Science]]&lt;br /&gt;
[[Category:Astronomy]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134278</id>
		<title>1791: Telescopes: Refractor vs Reflector</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1791:_Telescopes:_Refractor_vs_Reflector&amp;diff=134278"/>
				<updated>2017-01-27T14:26:03Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: /* Explanation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1791&lt;br /&gt;
| date      = January 27, 2017&lt;br /&gt;
| title     = Telescopes: Refractor vs Reflector&lt;br /&gt;
| image     = telescopes_refractor_vs_reflector.png&lt;br /&gt;
| titletext = On the other hand, the refractor's limited light-gathering means it's unable to make out shadow people or the dark god Chernabog.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|stub}}&lt;br /&gt;
This comic shows two types of telescopes: {{w|Reflecting Telescope|Reflecting}} and {{w|Refracting Telescope|Refracting}}. It first looks like the comic is trying to show that refracting has many flaws, such as expense, size and visibility. However, the punchline invalidates these complaints with the (apparently major) flaw listed with the reflecting telescope: it can't see space vampires. The unstated reason for this is that vampires cannot be seen in a mirror. As space vampires do not exist {{Citation needed}}, this complaint is moot, and the reflecting telescope technically has no flaws in comparison to the refracting telescope. The title text expands on the seeing of supernatural beings, as another negative point is added to the refracting telescope- it apparently can't see shadow people or the Slavic god {{w|Chernabog}}, both of which are apparently equally important to the telescope's merit despite also not existing.&lt;br /&gt;
&lt;br /&gt;
The title text adds an additional drawback to a refracting telecsope: it cannot see {{w|Shadow person|Shadow People}} or {{w|Chernobog|Chernabog}}. In reality, &amp;quot;shadow people&amp;quot; are a psychological phenomenon wherein humans ascribe human shapes and movements to shadows in dark spaces. Chernabog is a 12th century Slavic diety, whose name translates to ''black god''. His most famous apperance in modern media was in the 1940 Disney movie {{w|Fantasia (1940 film)|''Fantasia''}}.&lt;br /&gt;
&lt;br /&gt;
It is worth noting that in reality a Reflecting Telescope also has disadvantages compared to a refracting telescope.  The main disadvantage is that in almost all reflecting telescope designs the focal point is directly in front of the mirror, i.e. in between the mirror and the target of interest.  As a result a {{w|Secondary_mirror|secondary mirror}} is commonly used to direct the focal point somewhere outside of the field of view.  However, this secondary mirror (and the struts that support it) will still block part of the field of view and result in diffraction patterns that also hinder the image quality.  In fact, this is the source of the {{w|Diffraction_spike|diffraction spikes}} around stars which are commonly seen in astronomical images.  Despite this disadvantage, reflecting telescopes are used almost exclusively in modern astronomy because of practical limitations in making large refracting telescopes.&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
{{incomplete transcript}}&lt;br /&gt;
[The comic is one panel showing two different telescope designs.]&lt;br /&gt;
REFRACTOR&lt;br /&gt;
More expensive&lt;br /&gt;
Less compact&lt;br /&gt;
Chromatic aberration&lt;br /&gt;
Reduced Light-gathering&lt;br /&gt;
&lt;br /&gt;
REFLECTOR&lt;br /&gt;
Can't see space vampires&lt;br /&gt;
&lt;br /&gt;
Title text:&lt;br /&gt;
On the other hand, the refractor's limited light-gathering means it's unable to make out shadow people or the dark god Chernabog&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Comics with color]]&lt;br /&gt;
[[Category:Science]]&lt;br /&gt;
[[Category:Astronomy]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1032:_Networking&amp;diff=134233</id>
		<title>1032: Networking</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1032:_Networking&amp;diff=134233"/>
				<updated>2017-01-26T14:59:41Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: Added a quick note on Eusociality for &amp;quot;Eusocial Media Ventures&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1032&lt;br /&gt;
| date      = March 21, 2012&lt;br /&gt;
| title     = Networking&lt;br /&gt;
| image     = networking.png&lt;br /&gt;
| titletext = Our company is agile and lean with a focus on the long tail. Ok, our company is actually a polecat I found in my backyard.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
Obviously, [[Beret Guy]]'s [[1021|business plan]] worked.&lt;br /&gt;
&lt;br /&gt;
Networking, in business, is the act of expanding your group of contacts in order to help your career down the line. Here, in this comic, [[Beret Guy]] meets Chief Technology Officer (CTO, an executive level position overseeing development of new technologies) Connr Clark (perhaps a typo for &amp;quot;Connor&amp;quot; or perhaps a reference to common &amp;quot;Web 2.0&amp;quot; names like the businesses {{w|Flickr}}, {{w|Tumblr}}, etc.) and Beret Guy is as strange as he usually is: Although he is a business professional he has just photocopied a burrito.  He also has a business card; usually this would contain contact information, but his only says &amp;quot;This is my business card&amp;quot;. He calls his briefcase, or suitcase, a &amp;quot;handlebox&amp;quot;, and it is full of a quarter of a million dollars in cash. Then Beret Guy proceeds to eat Connr's business card. All of these things are not common behavior.{{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Networking&amp;quot; is often an over-hyped, empty affair. There are zillions of networking meetings of every description going on every day everywhere, and mostly people trade cards and continue to not make money. So that's the joke – Beret Guy does the networking {{w|schtick}}, badly, and yet is somehow making huge amounts of money at it.&lt;br /&gt;
&lt;br /&gt;
The comic is also likely a joke on the idea that many people are excited about becoming a &amp;quot;business professional&amp;quot; who carries a briefcase, hands out business cards, and makes tons of money, without having an adequate plan for how to make those things happen, or possibly even knowing what their actual job would be. Beret Guy never says what he does, simply introducing himself as a &amp;quot;business professional,&amp;quot; and explains his piles of cash with &amp;quot;I am a business grown-up who makes business profits!&amp;quot; In this world —and in people's dreams— when you &amp;quot;grow up&amp;quot; and start a business, money magically appears. Obviously, that's not how it works.{{Citation needed}}&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Eusocial&amp;quot; in &amp;quot;Eusocial Media Ventures&amp;quot; is a reference to {{w|eusociality}}, the highest level of social cooperation found in the animal kingdom.  Eusocial animals (termites being a common example) cooperate together to raise their young, have different generations living in the same colony, and have specialized individuals for reproductive and non-reproductive tasks.&lt;br /&gt;
&lt;br /&gt;
The title text is a pun on three common business buzzwords: agile, lean and long-tail. An agile business is one that can change course quickly based on customer demands and the business environment. A lean business is one with minimal inventory or assets; nothing is idle or warehoused, so everything in active use or on the move. Long-tail describes the strategy of offering a large number of unique items with relatively small quantities sold of each – usually in addition to selling fewer popular items in large quantities. Netflix is a popular example of long-tail because they have (almost) every movie imaginable, including rare titles that only a few people would be interested in.&lt;br /&gt;
&lt;br /&gt;
And of course, the pun here is one animal that is agile and lean with a long ''tail'' is a {{w|polecat}}.&lt;br /&gt;
&lt;br /&gt;
Furthermore, although &amp;quot;agile&amp;quot; and &amp;quot;lean&amp;quot; do mean a quick, nimble, and efficient business, they also refer to specific practices, as in {{w|agile software development}}, {{w|lean manufacturing}} and {{w|lean Six Sigma}}. Many people think these terms have devolved to overused jargon. While agile development is supposed to be a highly structured method to get programmers to produce more working code quickly, when someone from the marketing department says &amp;quot;''agile''&amp;quot; it often means &amp;quot;''We don't know what we're supposed to be producing, so we'll just chuck some stuff together, and keep those bits that the customer says he likes. We'll then do it all over again until we've got something that he'll pay for.''&amp;quot; &amp;quot;''Lean''&amp;quot; is supposed to mean that a business keeps its costs as low as possible, employing one person to do marketing and PR, not really having a Human Resources department, etc. But, in practice it often becomes &amp;quot;''Keep as little stock as possible so that we don't have a lot of money tied up in it, and don't need a big warehouse; make stuff just before it is supposed to ship so that we don't have to store it either; make frequent prayers and virgin sacrifices to whatever gods we can find to ensure that nothing slips up anywhere along the line that our lawyers can't get us out of.''&amp;quot;&lt;br /&gt;
&lt;br /&gt;
See also [[1117: My Sky]].&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[A man approaches Beret Guy at a party and they extend arms to shake hands. Beret Guy is holding a metal briefcase. Ponytail is a waitress in the background, carrying a tray with a wine glass on it.]&lt;br /&gt;
:Man: I'm Connr Clark, CTO at Eusocial Media Ventures.&lt;br /&gt;
:Beret Guy: I'm a business professional! Earlier I photocopied a burrito!&lt;br /&gt;
&lt;br /&gt;
:[The man hands Beret Guy a business card. Beret Guy takes it and hands the man another business card. Beret Guy has put his suitcase on the floor.]&lt;br /&gt;
:Man: You should check us out! Here's my card.&lt;br /&gt;
:Beret Guy: Here's mine! Networking!&lt;br /&gt;
&lt;br /&gt;
:[The man takes a closer look at the card, and Beret Guy holds up his case.]&lt;br /&gt;
:Man: ...this just says &amp;quot;This is my business card!&amp;quot;&lt;br /&gt;
:Beret Guy: Do you like it? I have more in my handlebox.&lt;br /&gt;
&lt;br /&gt;
:[Beret Guy puts his case on a table and opens it to reveal it is full of cash. The man looks on in shock.]&lt;br /&gt;
:Man: Uh, that's ok, I think I'll— &lt;br /&gt;
:Beret Guy: Here, have ten of them!&lt;br /&gt;
:Man: —holy shit that thing is full of ''cash!''&lt;br /&gt;
&lt;br /&gt;
:[The man raises his arms in excitement. Beret Guy turns to face him and chews on the man's business card.]&lt;br /&gt;
:Man: Where did you ''get'' that?&lt;br /&gt;
:Beret Guy: I am a business grown-up who makes business profits!&lt;br /&gt;
:Man: That's like a quarter of a million dollars!&lt;br /&gt;
:Beret Guy: Yay! Business is fun! Do you have more of your cards? They're ''delicious!''&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
[[Category:Comics with color]]&lt;br /&gt;
[[Category:Comics featuring Beret Guy]]&lt;br /&gt;
[[Category:Comics featuring Hairy]]&lt;br /&gt;
[[Category:Beret Guy's Business]]&lt;br /&gt;
[[Category:Comics featuring Ponytail]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:836:_Sickness&amp;diff=127879</id>
		<title>Talk:836: Sickness</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:836:_Sickness&amp;diff=127879"/>
				<updated>2016-09-27T18:06:45Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: Retracing previous comment&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Someone evidently didn't understand Hamlet too well.  In &amp;quot;To be or not to be&amp;quot; he's contemplating suicide.  &amp;quot;Take arms against...&amp;quot; means 'kill yourself so you won't have to put up with life's crappy bits.  I would rewrite the Hamlet reference myself, but I'm too lazy.  Could someone with a good understanding of the play do it?  Please?[[Special:Contributions/173.245.48.85|173.245.48.85]] 01:42, 12 March 2014 (UTC)&lt;br /&gt;
:Agreed. Change made. [[User:Orazor|Orazor]] ([[User talk:Orazor|talk]]) 08:03, 21 July 2014 (UTC)&lt;br /&gt;
:&amp;quot;Take arms against a sea of troubles...&amp;quot; does not mean to commit suicide. It means to fight against the struggle referred to the in the previous line &amp;quot;the slings and arrows of outrageous fortune&amp;quot;. The contemplation of suicide is expressed in the phrase &amp;quot;When he himself might his quietus make / With a bare bodkin&amp;quot; when one could end one's life with a dagger. [[Special:Contributions/141.101.70.151|141.101.70.151]] 08:35, 22 August 2014 (UTC)&lt;br /&gt;
::Yes, &amp;quot;to take arms against a sea of troubles&amp;quot; in this context does in fact does mean to commit suicide. The struggle refered to in the previous line is whether to put up with the unbearable situation he (Hamlet) has been placed in, or, in the next line(s), to exit the situation via suicide. Elsewise, why would he suddenly transition from &amp;quot;overcoming obstacles&amp;quot; to considering death? Doesn't make sense. For your reference, check out http://www.nosweatshakespeare.com/quotes/hamlet-to-be-or-not-to-be/.[[User:Orazor|Orazor]] ([[User talk:Orazor|talk]]) 10:53, 19 September 2014 (UTC)&lt;br /&gt;
: Why commit suicide. His mother tries to get him to accept the inevitable that his father's killer is now in power and get on with life instead of pretending to be daft.&lt;br /&gt;
:A bare bodkin is an arrow tipped with steel, a war arrow. As opposed to a neutered one for harmless purposes.&lt;br /&gt;
:[[User:Weatherlawyer| I used Google News BEFORE it was clickbait]] ([[User talk:Weatherlawyer|talk]]) 20:34, 24 January 2015 (UTC)&lt;br /&gt;
&lt;br /&gt;
I'm going to add some more discussion to the explanation, as I have always read this comic completely differently.  I saw white hat's question as asking if Cueball considered seeking cures for his illness outside of science, i.e. in pseudoscience.  Given the wide variety of &amp;quot;cures&amp;quot; for all manner of illnesses (especially cancer) in alternative medicine, this seems like the most straight-forward meaning of his question &amp;quot;are you looking for answers outside of science&amp;quot;.  Randall has obviously made plenty of comics about pseudoscience, so it is a relevant theme for him.  It also brings the comic together nicely, as Cueball is basically answering &amp;quot;Science has given us plenty of great tools: no need to rely on that crap!&amp;quot;.  Frankly, I'm a bit confused as to how the explanation went to discussions of suicide.  I understand that &amp;quot;Slings and arrows of fortune&amp;quot; is a Hamlet reference that involves a discussion of suicide, but the comic makes way more sense if you understand it as a contrast between the tools of modern medicine and the &amp;quot;tools&amp;quot; of ancient/alternative medicine.  I don't really think suicide was what Randall was aiming for.  However, I'll leave that all in as an alternative explanation for someone else to remove, if desired. [[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]]) 18:01, 27 September 2016 (UTC)&lt;br /&gt;
:Having read everything over again, I think the current explanation is fine.  I realized that the explanation talks less about suicide than the discussion, and that the explanations understanding of &amp;quot;Beyond science&amp;quot; is a better fit than him asking about alternative medicine.  So ignore me [[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]]) 18:06, 27 September 2016 (UTC)&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:836:_Sickness&amp;diff=127878</id>
		<title>Talk:836: Sickness</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:836:_Sickness&amp;diff=127878"/>
				<updated>2016-09-27T18:01:42Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: It's about modern medicine vs alternative medicine: not suicide&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Someone evidently didn't understand Hamlet too well.  In &amp;quot;To be or not to be&amp;quot; he's contemplating suicide.  &amp;quot;Take arms against...&amp;quot; means 'kill yourself so you won't have to put up with life's crappy bits.  I would rewrite the Hamlet reference myself, but I'm too lazy.  Could someone with a good understanding of the play do it?  Please?[[Special:Contributions/173.245.48.85|173.245.48.85]] 01:42, 12 March 2014 (UTC)&lt;br /&gt;
:Agreed. Change made. [[User:Orazor|Orazor]] ([[User talk:Orazor|talk]]) 08:03, 21 July 2014 (UTC)&lt;br /&gt;
:&amp;quot;Take arms against a sea of troubles...&amp;quot; does not mean to commit suicide. It means to fight against the struggle referred to the in the previous line &amp;quot;the slings and arrows of outrageous fortune&amp;quot;. The contemplation of suicide is expressed in the phrase &amp;quot;When he himself might his quietus make / With a bare bodkin&amp;quot; when one could end one's life with a dagger. [[Special:Contributions/141.101.70.151|141.101.70.151]] 08:35, 22 August 2014 (UTC)&lt;br /&gt;
::Yes, &amp;quot;to take arms against a sea of troubles&amp;quot; in this context does in fact does mean to commit suicide. The struggle refered to in the previous line is whether to put up with the unbearable situation he (Hamlet) has been placed in, or, in the next line(s), to exit the situation via suicide. Elsewise, why would he suddenly transition from &amp;quot;overcoming obstacles&amp;quot; to considering death? Doesn't make sense. For your reference, check out http://www.nosweatshakespeare.com/quotes/hamlet-to-be-or-not-to-be/.[[User:Orazor|Orazor]] ([[User talk:Orazor|talk]]) 10:53, 19 September 2014 (UTC)&lt;br /&gt;
: Why commit suicide. His mother tries to get him to accept the inevitable that his father's killer is now in power and get on with life instead of pretending to be daft.&lt;br /&gt;
:A bare bodkin is an arrow tipped with steel, a war arrow. As opposed to a neutered one for harmless purposes.&lt;br /&gt;
:[[User:Weatherlawyer| I used Google News BEFORE it was clickbait]] ([[User talk:Weatherlawyer|talk]]) 20:34, 24 January 2015 (UTC)&lt;br /&gt;
&lt;br /&gt;
I'm going to add some more discussion to the explanation, as I have always read this comic completely differently.  I saw white hat's question as asking if Cueball considered seeking cures for his illness outside of science, i.e. in pseudoscience.  Given the wide variety of &amp;quot;cures&amp;quot; for all manner of illnesses (especially cancer) in alternative medicine, this seems like the most straight-forward meaning of his question &amp;quot;are you looking for answers outside of science&amp;quot;.  Randall has obviously made plenty of comics about pseudoscience, so it is a relevant theme for him.  It also brings the comic together nicely, as Cueball is basically answering &amp;quot;Science has given us plenty of great tools: no need to rely on that crap!&amp;quot;.  Frankly, I'm a bit confused as to how the explanation went to discussions of suicide.  I understand that &amp;quot;Slings and arrows of fortune&amp;quot; is a Hamlet reference that involves a discussion of suicide, but the comic makes way more sense if you understand it as a contrast between the tools of modern medicine and the &amp;quot;tools&amp;quot; of ancient/alternative medicine.  I don't really think suicide was what Randall was aiming for.  However, I'll leave that all in as an alternative explanation for someone else to remove, if desired. [[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]]) 18:01, 27 September 2016 (UTC)&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:1701:_Speed_and_Danger&amp;diff=123252</id>
		<title>Talk:1701: Speed and Danger</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:1701:_Speed_and_Danger&amp;diff=123252"/>
				<updated>2016-07-12T17:18:24Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--Please sign your posts with ~~~~--&amp;gt;&lt;br /&gt;
;Worst Comic&lt;br /&gt;
I think this might be a strong contender for worst comic on xkcd. Although [[1384: Krypton]] definitely makes for stiff competition. [[Special:Contributions/108.162.216.102|108.162.216.102]] 14:28, 1 July 2016 (UTC)&lt;br /&gt;
:Perhaps &amp;quot;in worst taste&amp;quot; might be a better term than simply &amp;quot;worst&amp;quot;. Certainly the fatality '''rate''' (in fatalities/crash) for rocket crashes is higher, but placing motor sports crashes to the extreme end of the safety-danger axis is a bit suspect in light of https://en.wikipedia.org/wiki/Driver_deaths_in_motorsport . [[Special:Contributions/108.162.237.242|108.162.237.242]] 02:25, 2 July 2016 (UTC)&lt;br /&gt;
::This is a great comic, but taste differs. It's not like he is making a joke of people who die in NASCAR crashes, but on this scale it is just not dangerous compared to crashing with a rocket heading for space. This is exactly the same as if he had put in the coconut in on of his most controversial comics, and another scatter plot [[388: Fuck Grapefruit]]. In the title text of that comic he mentions that the whole charts would have lost meaning if he included the coconut. But here he did put it in (the rocket) since he likes rockets and will not use the F word on those like he did with grape and coconuts. It may not be one of the best, but I like it :-) --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 11:55, 2 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
The worst? Have you looked at the first few hundred? [[Special:Contributions/108.162.246.119|108.162.246.119]] 15:09, 1 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
I think this comic is actually enlightening on a certain (albeit narrow level). People frequently lack a proper sense of perspective, and this comic illustrates this fact. While we might say &amp;quot;Wow, that Indy car is really moving fast!&amp;quot;, it pales in comparison to other vehicles that some fortunate few travel in. {{unsigned|BobTheMad}}&lt;br /&gt;
:And I totally wanted to learn that from a '''comic''' that's supposed to be humorous... --[[Special:Contributions/108.162.219.7|108.162.219.7]] 16:50, 1 July 2016 (UTC)&lt;br /&gt;
::::Yeah well there are countless people who learned everything they know about space travel from 'The Martian' (as well as a ''lot'' of wrong things). So I really don't think that it's that uncommon for information on a subject to come from popular culture, however unfortunate it may be.--[[User:Snewmark|Snewmark]] ([[User talk:Snewmark|talk]]) 03:24, 4 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
[[1699]] and [[1680]] would like to have a word with you. Also [[1675]].&lt;br /&gt;
Actually, all of the last 25 or so comics would. I really don't know how the xkcd forums put up with being 500x smarter than all the comics they praise every day. [[User:Youforgotthisthing|Youforgotthisthing]] ([[User talk:Youforgotthisthing|talk]]) 17:18, 1 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
; Referencing Something?&lt;br /&gt;
Is there something this is referencing? [[User:Saklad5|Saklad5]] ([[User talk:Saklad5|talk]]) 14:41, 1 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
I believe this is in response to the recent crash of a Tesla car while running on autopilot - possibly the first recorded fatality of an autonomous car. {{unsigned ip|108.162.249.156}}&lt;br /&gt;
:Seems unlikely, as there is no mention of normal cars or Tesla. And although Elon Musk also do rockets launches (so far without humans as far as I know), there seem to be no relation to Tesla. --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 11:55, 2 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
To me the reference seems to be the Formula 1 &amp;quot;Halo&amp;quot; discussion. The last month I saw a few news articles about prominent F1 people calling this new safety measure &amp;quot;too safe&amp;quot; etc. To me this is a ridiculous argument and the comic is spot-on about it. The title text also seems to refer somewhat from that discussion. [[Special:Contributions/141.101.104.72|141.101.104.72]] 19:55, 3 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
;Sarcasm&lt;br /&gt;
Is sarcasm to be encouraged in explanations? “Here, Randall makes the '''truly astounding''' observation that the danger of a crash is directly proportional to its speed….” [Emphasis mine.] ''&amp;amp;mdash; [[User:Tbc|tbc]] ([[User talk:Tbc|talk]]) 15:29, 1 July 2016 (UTC)''&lt;br /&gt;
:In this case it's definitely warranted...Jesus Randall, this wouldn't exactly have been hard to make funny/interesting. --[[Special:Contributions/108.162.219.7|108.162.219.7]] 15:51, 1 July 2016 (UTC)&lt;br /&gt;
:No it should not be in the explanation. Keep the sarcasm here  ;-) --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 11:55, 2 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Well a rocket to achieve orbit hits about 18,000 MPH http://spaceflight.nasa.gov/shuttle/reference/basics/launch.html&lt;br /&gt;
Where as NASCAR is only ~200 MPH https://en.wikipedia.org/wiki/Stock_car_racing&lt;br /&gt;
Formula 1 is only ~257 MPH https://en.wikipedia.org/wiki/Formula_One_car#Top_speeds&lt;br /&gt;
[[Special:Contributions/162.158.68.71|162.158.68.71]] 16:51, 1 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
I'm kinda shocked Randall didn't reference Star Trek for this comic, considering the number. - Michael C. [[Special:Contributions/141.101.98.85|141.101.98.85]] 17:00, 1 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
;Why only 4 examples?&lt;br /&gt;
&lt;br /&gt;
Why not put things like biking, driving a regular car, WWI planes, WW2 planes, supersonic jets, satellites, Apollo, New Horizons... {{unsigned ip|108.162.244.67}}&lt;br /&gt;
:It was not interesting as they would all overlap and there would be not enough place for labels. The whole idea is that any sport bound to Earth is slow compared to a rocket launch. 100 m dash or Formula one is on the same scale when comparing. Reminds me of when he compared the speed of New Horizon to the speed of a bullet, which would also have been in the left side if New Horizon had been entered... --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 11:55, 2 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
;Sports or Sports Cars?&lt;br /&gt;
I don't think the comic intended to say &amp;quot;Normal Sports CARS,&amp;quot; as the explanation currently says, I think it means what it says, &amp;quot;Normal SPORTS&amp;quot; like foot ball, or hockey.   On the linear scale of 0-to-rocket, running or walking is close to race car speed, compared to how fast a rocket is, and the graph illustrates that.  Also, crashing a normal sports CAR is far more dangerous than crashing a professional race car because of all the safety equipment, so a sports car would be more toward the dangerous side. {{unsigned ip|108.162.219.81}}&lt;br /&gt;
:Agreed.  I was assuming the reference was to various contact sports such as football, hockey, and quidditch where collisions between players regularly happen. [[Special:Contributions/108.162.237.132|108.162.237.132]] 20:52, 1 July 2016 (UTC)&lt;br /&gt;
::Yes of course. My bad, I just read the three dots like different types of car, and did not think further about it. For sure I see now that it is any sports not using motor powers (maybe also not anything about going fast down-slope like bobsleigh etc.) --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 11:55, 2 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
;What is the point of this comic and where is the fun&lt;br /&gt;
&lt;br /&gt;
I don't know, I feel like people is missing the point of the comic, where is the funny on it.&lt;br /&gt;
&lt;br /&gt;
I think finding Formula one on the slow an secure quadrant of the chart is surprising, so near to regular sports, until you understand that it is only compared to a rocket launch. People sure think of F1 as fast and dangerous, so this comic plays with our expectations. &lt;br /&gt;
&lt;br /&gt;
Not exactly hilarious, but neither the worst XKCD comic.&lt;br /&gt;
&lt;br /&gt;
[[User:Inconexo|Inconexo]] ([[User talk:Inconexo|talk]]) 20:19, 1 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
One thing I think it might be interesting to indicate is how this is the first one of these plots where everything is in only two quadrants. There is no slow but dangerous crash nor fast but safe crash. Usually at least one these quadrants would have an entry, and probably a facetious one. &lt;br /&gt;
:True but there has only been three (with this) comic with a four quadrant scatter plot, the other being [[388: Fuck Grapefruit]] and [[1501: Mysteries]]. The other scatter plot are either in one square or not really scatter plots that can be compared to this one. So it may be too slim a data set to say this is special for xkcd. But still interesting enough that there are no fast safe or slow dangerous crashes. --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 12:22, 2 July 2016 (UTC)&lt;br /&gt;
::I didn't mean just scatter plots. I mean any time he's compared to variables. There was a recent one where it was a just a table with four entries, one for each &amp;quot;quadrant.&amp;quot; The joke is usually one silly item. [[User:Trlkly|Trlkly]] ([[User talk:Trlkly|talk]]) 14:53, 5 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
I also think the part about scale could be expanded to more than just the &amp;quot;relative to the speed of light.&amp;quot; Something like &amp;quot;While we tend to speak of race cars as going fast, they are slow compared to rockets.&amp;quot; --[[User:Trlkly|Trlkly]] ([[User talk:Trlkly|talk]]) 22:27, 1 July 2016 (UTC)&lt;br /&gt;
:Please feel free to improve with better examples. --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 11:55, 2 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
I'm not sure why that line about the speed of light is in the explanation.   What's it relevant to in the comic?&lt;br /&gt;
Speaking of it, though, if you DID want to chart fast/safe collisions, visible light photons hitting something would probably rate!&lt;br /&gt;
(And if you wanted slow/dangerous, maybe the Titanic hitting crashing into an iceberg, or an army tank crashing into...anything.) {{unsigned ip|108.162.219.56}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fatality rate is not 100% as shown by [[wikipedia:List_of_spaceflight-related_accidents_and_incidents#Non-fatal_incidents_during_spaceflight|Non-fatal incidents during spaceflight]] [[User:Wyrme|Wyrme]] ([[User talk:Wyrme|talk]]) 03:22, 2 July 2016 (UTC)&lt;br /&gt;
:None of those events resulted in a crash. All crashes have been fatal as far as I can see.  A crash involves the rocket hitting something.  --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 12:04, 2 July 2016 (UTC)&lt;br /&gt;
::By that definition, has there ever been a fatal rocket crash (excluding rockets fired as weapons hitting their target)? Thinking of the US space program: Apollo 1 was a fire in the capsule on the ground, not a crash. Challenger was an explosion in mid air, not a crash. Columbia was a break up on re-entry, not a crash. [[User:Jeremyp|Jeremyp]] ([[User talk:Jeremyp|talk]]) 13:05, 2 July 2016 (UTC)&lt;br /&gt;
:::Columbia crashed into the atmosphere. [[User:Psu256|Psu256]] ([[User talk:Psu256|talk]]) 19:32, 5 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
When I saw this comic, I immediately though of Little Bobby Tables (https://xkcd.com/327/) {{unsigned ip|141.101.70.193}}&lt;br /&gt;
&lt;br /&gt;
'''Fewest data points?''' [[605: Extrapolating]] shows a scatter plot with only two points (and a line extrapolating them). --[[Special:Contributions/198.41.242.240|198.41.242.240]] 11:27, 4 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
I think it's worth noting that this chart also shows how unlike a mathematical scatter plot, the position of the points relative to the axes isn't really meaningful.  Randall could have chosen to have the entire chart only show the lower right quadrant, and place the other sample points close to the origin, but his choice of presentation emphasizes the discrepancy.  Formula 1 car crashes aren't simply &amp;quot;less dangerous&amp;quot; than rocket crashes, compared to rockets they are extremely slow and safe - words that one generally wouldn't use to describe formula 1.  20:28, 5 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
I removed the comment about logarithmic axes: &amp;quot;The scatter plot uses logarithmic scales.  If they were linear, the origin would be at the bottom left.  With a logarithmic scale you can have fast, slow, safe and dangerous unbounded in all 4 directions.&amp;quot;  Having spent lots of time doing plots (logarithmic and otherwise) I'm pretty sure this comment is incorrect.  In fact, logarithmic scales cannot go through zero because log(0) is undefined, meaning that logarithmic plots are the ones that can't be unbound in all four directions.  Also, in linear plots there is no requirement that the origin has to be at the bottom left.[[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]]) 17:18, 12 July 2016 (UTC)&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1701:_Speed_and_Danger&amp;diff=123251</id>
		<title>1701: Speed and Danger</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1701:_Speed_and_Danger&amp;diff=123251"/>
				<updated>2016-07-12T17:06:54Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: Removed comment about logarithmic axes&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1701&lt;br /&gt;
| date      = July 1, 2016&lt;br /&gt;
| title     = Speed and Danger&lt;br /&gt;
| image     = speed_and_danger.png&lt;br /&gt;
| titletext = NASCAR removed the passenger seats because drivers hated how astronauts kept riding along with them and loudly announcing &amp;quot;Ahh, what a nice and relaxing drive.&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|More on the speed of sport cars and the race cars. How much faster does it feel for a human to see a regular sports car on a high way and then a formula one car. More on why a rocket seems slow? Also worth noting: the acceleration (deceleration) experienced in a high-speed car crash greatly exceeds what astronauts typically experience...}}&lt;br /&gt;
&lt;br /&gt;
In this {{w|scatter plot}} [[Randall]] plots the speed of several vehicles (including people on foot for &amp;quot;normal sports&amp;quot;) and how disastrous a crash would be. The punchline is that space {{w|rocket}}s travel so dangerously fast, and crashes are so utterly catastrophic, that it pushes literally every other kind of crash to the &amp;quot;slow and safe&amp;quot; corner by comparison. (A similar punchline was used in the title text of [[388: Fuck Grapefruit]].)&lt;br /&gt;
&lt;br /&gt;
With the plot Randall makes the observation that the danger of a crash is greatly influenced by its speed and highlights the concept of relativity between what we perceive as &amp;quot;fast,&amp;quot; normal sports and two different types of racing cars, vs. a much faster vehicle, a rocket during launch. A rocket may appear to ascend slowly (and of course it begins its ascent slowly), but on the way to orbit it ends up moving very fast. But before it reaches the more extreme speed regime it will be far away from the ground (and the casual observer), where there is nothing to compare this speed to as opposed to a race car speeding by a spectator during a race. (Of course rockets are slow compared to the speed of light.)&lt;br /&gt;
&lt;br /&gt;
Apart from the high speed, there is also the altitude to take into account for a rocket launch, and the vast amount of fuel needed to get into orbit, and any sort of catastrophic failure is almost certainly fatal. &lt;br /&gt;
&lt;br /&gt;
Racing cars are often involved in crashes, but at that speed it is possible to construct them so even serious crashes may not be fatal. Although rockets are also made as safe as possible, it is a completely different regime of ''speed and danger'', and the risk of something going wrong during a take off is much higher, and it is impossible to prevent a lethal disaster if the launch fails during the ascent. This results in a much higher mortality rate for each crashed rocket (probably 100%) vs. crashed sports/race cars.&lt;br /&gt;
&lt;br /&gt;
Rocket launches are compared to &amp;quot;normal {{w|sports}}&amp;quot; (presumably meaning people running approximately 25 km/h, and possibly also {{w|polo}} {{w|horse}}s galloping approximately 40 km/h), {{w|NASCAR}} (which reaches speed of 320 km/h), and {{w|Formula One}} (F1), where the fastest race cars go 380 km/h. Although peak speed for an F1 car is higher than NASCAR, the average lap speed is much lower as F1 tracks have slow corners while NASCAR ovals can be negotiated with much less speed variation. It is also arguable whether F1 is more dangerous than NASCAR - there have been fewer fatalities in F1 this millennium, though fewer cars compete and races are of shorter duration.&lt;br /&gt;
&lt;br /&gt;
A rocket launched to reach the {{w|International Space Station|ISS}} needs to match the speed of the space station which moves at 27,600 km/h. A rocket that needs to {{w|Escape velocity|escape}} from Earth needs to reach 40,270 km/h, but so far no humans have escaped. However, the astronauts going to the Moon came close, with {{w|Apollo 10}} setting the {{w|List_of_spaceflight_records#Fastest|speed record}} for manned flights with 39,896 km/h. (It was only about [https://www.quora.com/Why-was-Apollo-10-the-fastest-of-all-the-Apollo-missions 0.4% faster] than the next 7 missions that, in contrast to Apollo 10, were supposed to land on the Moon). The lowest of the rocket speeds mentioned above  is still more than 70 times as fast as the highest speed for race cars.&lt;br /&gt;
&lt;br /&gt;
The title text serves to emphasize the point further, as an astronaut (used to the several G's of acceleration during takeoff and overall much higher speeds) would likely find a NASCAR car moving at ~300 km/h paltry compared to what they're acclimated and has supposedly aggravated NASCAR drivers by making a point of saying so. And thus this is used to explain why there are no passenger seats in NASCAR cars, to prevent astronauts from joining the drivers for a nice, slow ride.&lt;br /&gt;
&lt;br /&gt;
Of the many [[:Category:Charts|charts in xkcd]] this one is notable for containing the fewest sample points of any [[:Category:Scatter plots|scatter plots]] in xkcd.&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[A two-axis diagram with two double headed arrows centered in the middle of the panel. Each arrow is labeled. There are four large dots in the diagram, three close together in the top left corner and one in the bottom right corner. Each dot is labeled.]&lt;br /&gt;
&lt;br /&gt;
:[Y axis:]&lt;br /&gt;
:Top: Crashes are safe&lt;br /&gt;
:Bottom: Crashes are dangerous&lt;br /&gt;
&lt;br /&gt;
:[X axis:]&lt;br /&gt;
:Left: Slow&lt;br /&gt;
:Right: Fast&lt;br /&gt;
&lt;br /&gt;
:[Dots from top left to bottom right:]&lt;br /&gt;
:Normal sports&lt;br /&gt;
:NASCAR&lt;br /&gt;
:Formula One&lt;br /&gt;
:Rocket launches&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Scatter plots]]&lt;br /&gt;
[[Category:Sport]]&lt;br /&gt;
[[Category:Space]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:1700:_New_Bug&amp;diff=122631</id>
		<title>Talk:1700: New Bug</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:1700:_New_Bug&amp;diff=122631"/>
				<updated>2016-07-01T12:58:38Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Italic text''&amp;lt;!--Please sign your posts with ~~~~--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
I'm new. For the explanation: A bug, as in a computer (programming) bug, can be reported and tracked, and many systems allow collaboration on the reporting and tracking of problems, or bugs, in code, and their solutions. Cueball reported a problem (bug) he found in the code, which presumably caused the server (program)&amp;amp;mdash;which he wrote as part of his project&amp;amp;mdash;to try to read the passwords as URLs before storing them. This exposes serious cross-site scripting attacks and other serious security vulnerabilities, and since handling password and user account information usually requires a lot of programming, this would be difficult to fix, which is why the character off-panel suggests burning the project down, as that would be much easier, and would solve any security problems, much more quickly than fixing the bug would. The comment text refers to Cueball's horrid solution to a horrid problem: Instead of solving the problem that is causing the server to read passwords as URLs, he can instead leverage a known problem in the programme which reads URLs which prevents it from reading a particular way of representing text in binary form, by adding a few characters to the user's password that the URL-reading program can't read. This would also &amp;quot;salt&amp;quot; the user's password, which is a security technique that makes passwords harder to figure out when they are stored properly. Cueball thinks this would solve the original problem, and two other problems at the same time, the second problem being the fact that user's passwords aren't salted (a security problem). The third solved problem is difficult to deduce.   &amp;amp;emsp;[[User:Zyzygy|Zyzygy]] 05:40, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
: The third bug is the unicode handling, which would need to be solved in order to salt passwords with emoji since these are unicode only character. Although I'm not sure if salting with emoji really increases security since as a rule i'd say nobody uses emoji in their passwords. [[Special:Contributions/162.158.85.123|162.158.85.123]] 06:34, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
::Password: 👍🐎🔋Π [[Special:Contributions/141.101.98.131|141.101.98.131]] 10:11, 29 June 2016 (UTC)&lt;br /&gt;
:::That is a really funny password, [[936: Password Strength|but is it strong ennough?]] :-) --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 20:22, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
:Actually, nobody using emoji in their password would be reason salting with emoji is MORE effective. Salting doesn't really increase security of single password, but it does increase security of whole password database, because you can hash some string - like, [http://www.telegraph.co.uk/technology/2016/01/26/most-common-passwords-revealed---and-theyre-ridiculously-easy-to/ 123456] and check whole database for users having that as password. If every password is salted with different emoji, this strategy will not work, because while you KNOW which emoji is used - the salt is stored unhashed with the password hash - it's always different so you need to compute new hash for every line in password database. Hashing takes MUCH more time than just comparing strings. And how it's even more effective? Because someone might actually get multiple databases and search for entries with same salt, hoping there will be enough of them to be worth it. And salt with emoji likely wouldn't be so common ... -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 09:54, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
From 108.162.221.22 (long rant)&lt;br /&gt;
:Two comments: first, the explanation on password salting is incorrect.  The current version says &amp;quot;Salting passwords increases security by adding random data to the passwords which primarily helps defend against dictionary attacks.&amp;quot;.  Password salting only protects against particular kinds of (common) attacks in specific situations.  Most importantly, it is designed to protect passwords only in the event ofa database breach, when a malicious user has gained direct access to the database itself.  Password salting provides no protection when brute force attacks (aka dictionary attacks) are directed at the application itself, as the application automatically takes hashes into account.  Instead, proper password salting randomizes the hash for each password, ensuring that if two users have the same password, they will not have the same hash.  This makes it much more difficult to guess passwords through attack vectors like lookup tables, reverse lookup tables, and rainbow tables.  However, because the salt has to be stored with the password (otherwise the application would not be able to make sense of the hash itself), password salting does not secure passwords against dictionary attacks even in the event that a malicious user has managed to acquire the database itself.  I will update the explanation with a brief description of what password salts do.&lt;br /&gt;
:Finally, I think there is a big misunderstanding throughout this explanation.  In a web services context the &amp;quot;server&amp;quot; (referenced in the comic) is a very different thing than the application that a programmer builds.  A server can refer to either the computer itself or the software that is responsible for responding to web requests and executing the actual application.  In a professional context, the application (which is what cueball would be building) would never be referred to as the &amp;quot;server&amp;quot;.  It is possible that this is a mis-use of terminology on the part of cueball or Randall, but I suspect that the term was used properly and intentionally.  The reason is because if cueball's application is crashing the *server*, it takes the level of incompetence up to completely new (and unusual) levels, in much the same way that he has done in the past.  Normally the programming language used to build the application, the software hosting the application, and the operating system itself have a number of safe guards in place to ensure that if an application misbehaves, the only thing that crashes is the application itself.  For cueball's application to break through all those safeguards and crash the server itself (either the operating system or the web server software) would require cueball to have developed a program that operates *well* outside the bounds of normal procedures.  Just for reference, as someone who has been building web software for over 15 years, I wouldn't even know where to start to crash the server from within an application. It would probably have to involve either exploiting a previously unknown bug in the programming language or some *very* poorly designed system calls.   [[Special:Contributions/108.162.221.22 15:11, 29 June 2016‎ 108.162.221.22]] (Rememeber to sign your comments) &lt;br /&gt;
&lt;br /&gt;
::If you by 'server' means Apache it is not completely unexpected that a sloppy coded extension to Perl or PHP could crash part of the server – and I still maintain mod_perl code that does 'fancy' stuff. I wouldn't be surprised if Cueball still wrote web-application as he did when mod_perl was the hot stuff. Today it is a common setup to have a chain of servers. In the front nginx for SSL termination, maybe an application level firewall filtering out spooky requests,  then Varnish for caching and load-balancing and finally the application server running the actual web-application – all layers implementing the HTTP protocol. Which of these are 'the server'? At least it is often easy for the application developer to make the last server in the chain unresponsive (i.e. crashed). [[User:Pmakholm|Pmakholm]] ([[User talk:Pmakholm|talk]]) 12:08, 1 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
:::Writing an extension to your language of choice would probably be a good way of crashing the server, although I would say that writing extensions to the language itself is not a common thing for most people to do.  I suppose I'm arguing from experience (which is not always accurate) but in years of PHP and python programming I've never once had to write a language extension, nor did I ever need to for my very complicated thesis work.  So I would say that the general point still stands: if Cueball is crashing any part of the server, he is doing things very wrong or at least very different.[[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]]) 12:58, 1 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Regarding those last two points: sorry for my long unsigned rant.  Didn't realize I wasn't logged in.  Still haven't figured out how to sign comments.  Gonna try it this time. [[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]]) 16:51, 29 June 2016 (UTC)&lt;br /&gt;
:You made it ;-) --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 20:22, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Explanation says &amp;quot;There is no reason for password handling code to access urls&amp;quot; but that is somewhat wrong -- Password handling code frequently perform heuristics on the password to assess the strength, for example checking if part of the password is a dictionary word -- similar heuristics could be done to check thatthe password is not a URL, such as &amp;quot;xkcd.com&amp;quot; applying DNS and other internet resources as an extention of the concept of &amp;quot;dictionary&amp;quot;. [[User:Spongebog|Spongebob]] ([[User talk:Spongebog|talk]]) 16:11, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
:I think http://xkcd.com/correct/horse/battery/staple/ would be a perfectly fine password, even though it is also an URL – but a heuristic that just looks at the length of the password and if it only contains alphanumeric characters would probably be fooled. Trying to detect the scheme used to generate the password could be helpful in choosing a relevant heuristic for deciding the password strength. Ont the other hand, I would consider it very bad to actually test whether the URL is resolvable in any way that leaks information about the password to the outside. [[User:Pmakholm|Pmakholm]] ([[User talk:Pmakholm|talk]]) 11:11, 1 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Currently the explanation says: &amp;quot;Finally, emoji will often include unicode characters, which means that, if one can effectively salt passwords with emoji, then the passwords should be able to be stored in unicode (although that *probably* doesn't require anything outside the Base Multilingual Plane, so that might not need full unicode support after-all).&amp;quot;  I'm fairly convinced that this doesn't make sense and is incorrect.  Regardless of what character encoding the password is in, hashing will convert the entire thing into binary.  This binary is then typically stored as a base64-encoded string in the database.  Ergo, it doesn't matter whether the original password strings were in unicode or not: they will be stored in the database as ascii (or binary), not unicode.  I'm going to go ahead and remove this comment from the explanation.  I'm pretty certain that there isn't enough information in the comic to figure out why salting passwords with emoji would fix a unicode-handling bug in the URL request library.  So I suspect that there is no explanation there: either Cueball is entirely confused and his statement makes no sense, or there is simply not enough information given to help us understand why this solution might fix the problem.  However, I'm not going to make any updates to the explanation about this yet, because perhaps I'm missing something someone else will notice. [[User:Cmancone|Cmancone]] 12:50, 29 June 2016 (ETC)&lt;br /&gt;
:I suspect that the salting with emoji is to ensure that the password does not resolve as a URL (since the library cannot understand the encoding), and thus the issue of the crash is resolved, the issue of unsalted passwords is solved, and the issue of the unicode handling bug is &amp;quot;solved&amp;quot; by virtue of it now being a feature relied on by the system. [[Special:Contributions/173.245.56.68|173.245.56.68]] 20:50, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
I removed from the explanation the discussion about how Cueball's system might be checking passwords to see if they are resolvable URLs as a check against weak passwords.  The problem with this explanation is that if that is where the crash was happening, then salting the password with emoji would not fix the crash.  For salting to fix the crash (as Cueball suggests it will) requires that the crash be happening during the hashing process, not during password validation.  The reason is because password validation is performed on the original password itself, while only hashing happens on the salted password.  So for salting to fix the crash it must be happening during hashing, not validation.  If the bug is happening while checking passwords for strength then Cueball's suggestion of fixing it by adding in a salt will not actually fix the crash at all.  It could be that Cueball is simply completely wrong about everything, but I think it makes more sense to go with an explanation where the title text didn't just get everything wrong.[[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]]) 13:12, 30 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
In the nomenclature I am familiar with mailto:somebody@example.com is a URL.  If you accept that mailto (and other protocols) are also URLs some of the description is untrue.  Fortunately the untrue bits are also unnecessary and can be deleted or generalized.--[[Special:Contributions/108.162.219.11|108.162.219.11]] 04:51, 1 July 2016 (UTC)&lt;br /&gt;
Definitely a sequel to 1084[[Special:Contributions/108.162.221.92|108.162.221.92]] 08:27, 1 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
The explanation of 'Resolveable URL' is very confusing and mostly wrong, it is mixing up technologies like HTTP and DNS and is confusing FQDN's with URLs. Though admittedly, the term 'resolveable URL' is a bit of a misnomer by itself. URLs are typically not resolved, they contain an FQDN that is resolved via DNS to an IP(v6) address and optionally port. The remainder of the URL can be used to identify a resource on that server, but how this is done and signaled is quite application/protocol dependent (and shouldn't be called 'resolving'). So if you hit a 404 the FQDN actually resolved but the HTTP resource could not be found. A non-resolveable URL would give a browser error like 'unknown host'. [[Special:Contributions/162.158.83.198|162.158.83.198]] 09:59, 1 July 2016 (UTC)&lt;br /&gt;
:Feel free to adjust the text as desired.  I think in this case it is best to understand &amp;quot;Resolvable URL&amp;quot; as Cueball meant it, which (I think) is as any valid URL you might stick in your web browser.  I don't think he meant any of the more technical possible definitions.  In that sense a resolvable URL would be something that points to a server, potentially followed by a resource on the server.  At least, that is how I would think to describe it.  Feel free to give it a go.&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:1700:_New_Bug&amp;diff=122629</id>
		<title>Talk:1700: New Bug</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:1700:_New_Bug&amp;diff=122629"/>
				<updated>2016-07-01T12:43:49Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''Italic text''&amp;lt;!--Please sign your posts with ~~~~--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
I'm new. For the explanation: A bug, as in a computer (programming) bug, can be reported and tracked, and many systems allow collaboration on the reporting and tracking of problems, or bugs, in code, and their solutions. Cueball reported a problem (bug) he found in the code, which presumably caused the server (program)&amp;amp;mdash;which he wrote as part of his project&amp;amp;mdash;to try to read the passwords as URLs before storing them. This exposes serious cross-site scripting attacks and other serious security vulnerabilities, and since handling password and user account information usually requires a lot of programming, this would be difficult to fix, which is why the character off-panel suggests burning the project down, as that would be much easier, and would solve any security problems, much more quickly than fixing the bug would. The comment text refers to Cueball's horrid solution to a horrid problem: Instead of solving the problem that is causing the server to read passwords as URLs, he can instead leverage a known problem in the programme which reads URLs which prevents it from reading a particular way of representing text in binary form, by adding a few characters to the user's password that the URL-reading program can't read. This would also &amp;quot;salt&amp;quot; the user's password, which is a security technique that makes passwords harder to figure out when they are stored properly. Cueball thinks this would solve the original problem, and two other problems at the same time, the second problem being the fact that user's passwords aren't salted (a security problem). The third solved problem is difficult to deduce.   &amp;amp;emsp;[[User:Zyzygy|Zyzygy]] 05:40, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
: The third bug is the unicode handling, which would need to be solved in order to salt passwords with emoji since these are unicode only character. Although I'm not sure if salting with emoji really increases security since as a rule i'd say nobody uses emoji in their passwords. [[Special:Contributions/162.158.85.123|162.158.85.123]] 06:34, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
::Password: 👍🐎🔋Π [[Special:Contributions/141.101.98.131|141.101.98.131]] 10:11, 29 June 2016 (UTC)&lt;br /&gt;
:::That is a really funny password, [[936: Password Strength|but is it strong ennough?]] :-) --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 20:22, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
:Actually, nobody using emoji in their password would be reason salting with emoji is MORE effective. Salting doesn't really increase security of single password, but it does increase security of whole password database, because you can hash some string - like, [http://www.telegraph.co.uk/technology/2016/01/26/most-common-passwords-revealed---and-theyre-ridiculously-easy-to/ 123456] and check whole database for users having that as password. If every password is salted with different emoji, this strategy will not work, because while you KNOW which emoji is used - the salt is stored unhashed with the password hash - it's always different so you need to compute new hash for every line in password database. Hashing takes MUCH more time than just comparing strings. And how it's even more effective? Because someone might actually get multiple databases and search for entries with same salt, hoping there will be enough of them to be worth it. And salt with emoji likely wouldn't be so common ... -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 09:54, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
From 108.162.221.22 (long rant)&lt;br /&gt;
:Two comments: first, the explanation on password salting is incorrect.  The current version says &amp;quot;Salting passwords increases security by adding random data to the passwords which primarily helps defend against dictionary attacks.&amp;quot;.  Password salting only protects against particular kinds of (common) attacks in specific situations.  Most importantly, it is designed to protect passwords only in the event ofa database breach, when a malicious user has gained direct access to the database itself.  Password salting provides no protection when brute force attacks (aka dictionary attacks) are directed at the application itself, as the application automatically takes hashes into account.  Instead, proper password salting randomizes the hash for each password, ensuring that if two users have the same password, they will not have the same hash.  This makes it much more difficult to guess passwords through attack vectors like lookup tables, reverse lookup tables, and rainbow tables.  However, because the salt has to be stored with the password (otherwise the application would not be able to make sense of the hash itself), password salting does not secure passwords against dictionary attacks even in the event that a malicious user has managed to acquire the database itself.  I will update the explanation with a brief description of what password salts do.&lt;br /&gt;
:Finally, I think there is a big misunderstanding throughout this explanation.  In a web services context the &amp;quot;server&amp;quot; (referenced in the comic) is a very different thing than the application that a programmer builds.  A server can refer to either the computer itself or the software that is responsible for responding to web requests and executing the actual application.  In a professional context, the application (which is what cueball would be building) would never be referred to as the &amp;quot;server&amp;quot;.  It is possible that this is a mis-use of terminology on the part of cueball or Randall, but I suspect that the term was used properly and intentionally.  The reason is because if cueball's application is crashing the *server*, it takes the level of incompetence up to completely new (and unusual) levels, in much the same way that he has done in the past.  Normally the programming language used to build the application, the software hosting the application, and the operating system itself have a number of safe guards in place to ensure that if an application misbehaves, the only thing that crashes is the application itself.  For cueball's application to break through all those safeguards and crash the server itself (either the operating system or the web server software) would require cueball to have developed a program that operates *well* outside the bounds of normal procedures.  Just for reference, as someone who has been building web software for over 15 years, I wouldn't even know where to start to crash the server from within an application. It would probably have to involve either exploiting a previously unknown bug in the programming language or some *very* poorly designed system calls.   [[Special:Contributions/108.162.221.22 15:11, 29 June 2016‎ 108.162.221.22]] (Rememeber to sign your comments) &lt;br /&gt;
&lt;br /&gt;
::If you by 'server' means Apache it is not completely unexpected that a sloppy coded extension to Perl or PHP could crash part of the server – and I still maintain mod_perl code that does 'fancy' stuff. I wouldn't be surprised if Cueball still wrote web-application as he did when mod_perl was the hot stuff. Today it is a common setup to have a chain of servers. In the front nginx for SSL termination, maybe an application level firewall filtering out spooky requests,  then Varnish for caching and load-balancing and finally the application server running the actual web-application – all layers implementing the HTTP protocol. Which of these are 'the server'? At least it is often easy for the application developer to make the last server in the chain unresponsive (i.e. crashed). [[User:Pmakholm|Pmakholm]] ([[User talk:Pmakholm|talk]]) 12:08, 1 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Regarding those last two points: sorry for my long unsigned rant.  Didn't realize I wasn't logged in.  Still haven't figured out how to sign comments.  Gonna try it this time. [[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]]) 16:51, 29 June 2016 (UTC)--&lt;br /&gt;
:You made it ;-) --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 20:22, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Explanation says &amp;quot;There is no reason for password handling code to access urls&amp;quot; but that is somewhat wrong -- Password handling code frequently perform heuristics on the password to assess the strength, for example checking if part of the password is a dictionary word -- similar heuristics could be done to check thatthe password is not a URL, such as &amp;quot;xkcd.com&amp;quot; applying DNS and other internet resources as an extention of the concept of &amp;quot;dictionary&amp;quot;. [[User:Spongebog|Spongebob]] ([[User talk:Spongebog|talk]]) 16:11, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
:I think http://xkcd.com/correct/horse/battery/staple/ would be a perfectly fine password, even though it is also an URL – but a heuristic that just looks at the length of the password and if it only contains alphanumeric characters would probably be fooled. Trying to detect the scheme used to generate the password could be helpful in choosing a relevant heuristic for deciding the password strength. Ont the other hand, I would consider it very bad to actually test whether the URL is resolvable in any way that leaks information about the password to the outside. [[User:Pmakholm|Pmakholm]] ([[User talk:Pmakholm|talk]]) 11:11, 1 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Currently the explanation says: &amp;quot;Finally, emoji will often include unicode characters, which means that, if one can effectively salt passwords with emoji, then the passwords should be able to be stored in unicode (although that *probably* doesn't require anything outside the Base Multilingual Plane, so that might not need full unicode support after-all).&amp;quot;  I'm fairly convinced that this doesn't make sense and is incorrect.  Regardless of what character encoding the password is in, hashing will convert the entire thing into binary.  This binary is then typically stored as a base64-encoded string in the database.  Ergo, it doesn't matter whether the original password strings were in unicode or not: they will be stored in the database as ascii (or binary), not unicode.  I'm going to go ahead and remove this comment from the explanation.  I'm pretty certain that there isn't enough information in the comic to figure out why salting passwords with emoji would fix a unicode-handling bug in the URL request library.  So I suspect that there is no explanation there: either Cueball is entirely confused and his statement makes no sense, or there is simply not enough information given to help us understand why this solution might fix the problem.  However, I'm not going to make any updates to the explanation about this yet, because perhaps I'm missing something someone else will notice. [[User:Cmancone|Cmancone]] 12:50, 29 June 2016 (ETC)&lt;br /&gt;
:I suspect that the salting with emoji is to ensure that the password does not resolve as a URL (since the library cannot understand the encoding), and thus the issue of the crash is resolved, the issue of unsalted passwords is solved, and the issue of the unicode handling bug is &amp;quot;solved&amp;quot; by virtue of it now being a feature relied on by the system. [[Special:Contributions/173.245.56.68|173.245.56.68]] 20:50, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
I removed from the explanation the discussion about how Cueball's system might be checking passwords to see if they are resolvable URLs as a check against weak passwords.  The problem with this explanation is that if that is where the crash was happening, then salting the password with emoji would not fix the crash.  For salting to fix the crash (as Cueball suggests it will) requires that the crash be happening during the hashing process, not during password validation.  The reason is because password validation is performed on the original password itself, while only hashing happens on the salted password.  So for salting to fix the crash it must be happening during hashing, not validation.  If the bug is happening while checking passwords for strength then Cueball's suggestion of fixing it by adding in a salt will not actually fix the crash at all.  It could be that Cueball is simply completely wrong about everything, but I think it makes more sense to go with an explanation where the title text didn't just get everything wrong.[[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]]) 13:12, 30 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
In the nomenclature I am familiar with mailto:somebody@example.com is a URL.  If you accept that mailto (and other protocols) are also URLs some of the description is untrue.  Fortunately the untrue bits are also unnecessary and can be deleted or generalized.--[[Special:Contributions/108.162.219.11|108.162.219.11]] 04:51, 1 July 2016 (UTC)&lt;br /&gt;
Definitely a sequel to 1084[[Special:Contributions/108.162.221.92|108.162.221.92]] 08:27, 1 July 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
The explanation of 'Resolveable URL' is very confusing and mostly wrong, it is mixing up technologies like HTTP and DNS and is confusing FQDN's with URLs. Though admittedly, the term 'resolveable URL' is a bit of a misnomer by itself. URLs are typically not resolved, they contain an FQDN that is resolved via DNS to an IP(v6) address and optionally port. The remainder of the URL can be used to identify a resource on that server, but how this is done and signaled is quite application/protocol dependent (and shouldn't be called 'resolving'). So if you hit a 404 the FQDN actually resolved but the HTTP resource could not be found. A non-resolveable URL would give a browser error like 'unknown host'. [[Special:Contributions/162.158.83.198|162.158.83.198]] 09:59, 1 July 2016 (UTC)&lt;br /&gt;
:Feel free to adjust the text as desired.  I think in this case it is best to understand &amp;quot;Resolvable URL&amp;quot; as Cueball meant it, which (I think) is as any valid URL you might stick in your web browser.  I don't think he meant any of the more technical possible definitions.  In that sense a resolvable URL would be something that points to a server, potentially followed by a resource on the server.  At least, that is how I would think to describe it.  Feel free to give it a go.&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1700:_New_Bug&amp;diff=122600</id>
		<title>1700: New Bug</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1700:_New_Bug&amp;diff=122600"/>
				<updated>2016-06-30T13:16:28Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: I think we are complete now.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1700&lt;br /&gt;
| date      = June 29, 2016&lt;br /&gt;
| title     = New Bug&lt;br /&gt;
| image     = new_bug.png&lt;br /&gt;
| titletext = There's also a unicode-handling bug in the URL request library, and we're storing the passwords unsalted ... so if we salt them with emoji, we can close three issues at once!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
&lt;br /&gt;
[[Cueball]] asks if an off-panel character can look at his bug report. The person asks if it's a &amp;quot;normal one&amp;quot; and not a &amp;quot;horrifying&amp;quot; one which &amp;quot;proves that the whole project is broken beyond repair and should be burnt to the ground&amp;quot;. This implies that there have been reports of the &amp;quot;horrifying&amp;quot; variety in the past. &lt;br /&gt;
&lt;br /&gt;
Cueball promises that it is a normal one but it turns out that the server crashes when a user's password is a resolvable URL, which implies that the server is in some way attempting to resolve passwords as if they were URLs. A resolvable URL is one that is syntactically correct and refers to a find-able and accessible resource on the internet (i.e. does not return a {{w|HTTP_404|404 error}} or equivalent when resolved).  Therefore a resolvable URL is a {{w|Fully_qualified_domain_name|fully qualified domain name}} or a valid ip address that points to a valid server, and it can optionally specify a resource that exists on that server.  Normally there is no reason for a system to treat a password as if it were a URL.&lt;br /&gt;
&lt;br /&gt;
Also, Cueball specifically states that the server is crashing, rather than his application.  While this could be an example of misused terminology on the part of Cueball or Randall, given Cueball's history his choice of terms is probably accurate.  In the context of web services the server refers to either the computer itself or the program that responds to web requests and executes the user's (i.e. Cueball's) application.  Cueball would be in charge of building the application.  The importance of this distinction is that a typical system has safe guards in place at many levels to prevent a misbehaving application from crashing anything other than itself.  So for his application to crash the server (either the computer itself or the server software hosting his application) would require his application to be operating in a way far outside of the norm, which has been the case for Cueball in previous comics.  Alternatively, the project might include its own server software without the safeguards.  In either case it is clear that Cueball's issue is far from normal, for which reason the off-panel person gives up and decides that burning the project to the ground is the only solution, telling Cueball ''I'll get the {{w|Charcoal_lighter_fluid|lighter fluid}}''. &lt;br /&gt;
&lt;br /&gt;
In the title text another two issues with Cueball's program are mentioned, together with a possible solution that would fix all three problems at once. The second problem is a unicode-handling bug in the URL request library, and the third is that the passwords are stored unsalted.  The proposed solution is to salt the passwords with {{w|emoji}} (unicode, multi-byte characters), which is claimed to solve all three issues at once.  {{w|Salt (cryptography)|Salting}} passwords means that random characters are added to the password before it is cryptographically-secured and stored in the database. Salting increases security in the event that the database is compromised by ensuring that users with the same password will not have the same password hash.  This makes some attacks that can be used to crack hash databases, such as {{w|Rainbow table|rainbow tables}}, effectively impossible.&lt;br /&gt;
&lt;br /&gt;
Salting passwords with emoji can potentially &amp;quot;fix&amp;quot; these bugs in different ways.  First, emoji and other unicode characters are not valid characters in URLs.  As a result the salted-passwords will no longer be resolvable URLs. This will presumably circumvent (but not actually fix) the bug that causes the server to crash.  In addition, the passwords will now be salted, increasing security.  There is no obvious way that this would actually fix a unicode-handling bug in the URL request library.  Given Cueball's general approach to problems like this, the best explanation is probably that he hasn't &amp;quot;fixed&amp;quot; the bug but rather that it is no longer a bug because he is relying on its behavior to help fix these other issues, i.e. the classic [http://www.urbandictionary.com/define.php?term=It%27s%20not%20a%20bug%2C%20it%27s%20a%20feature it's not a bug, it's a feature].&lt;br /&gt;
&lt;br /&gt;
The title text shows that his general approach to problems is not to actually fix bugs but to work around them and even rely on them for other behavior.  This approach to software development makes for terrible code, which is likely how Cueball got into this trouble in the first place.  Therefore the title text shows that he still has yet to learn from his mistakes, further supporting the suggestion to just burn the whole thing down.&lt;br /&gt;
&lt;br /&gt;
Given that this comic comes only five comics after [[1695: Code Quality 2]] it seems likely that the off-panel person is [[Ponytail]] and as could be seen in the first of those two comics, [[1513: Code Quality]], the perpetrator is indeed Cueball. In the title text of the first, using emoji in variable names is mentioned.&lt;br /&gt;
&lt;br /&gt;
In [[1349: Shouldn't Be Hard]] Cueball is also programming and finding it very difficult, although he thinks it should be easy. An off-panel person suggests burning the computer down with a blowtorch, much like the off-panel person in this one suggests burning the whole project (including the computer) to the ground with lighter fluid. In the next comic, with multiple storylines [[1350: Lorenz]], one [http://xkcd.com/1350/#p:2ed958de-badf-11e3-8001-002590d77bdd story line] results in a computer being [http://www.explainxkcd.com/wiki/images/a/a6/lorenz_-_laptop_9.png burned with a blow torch].&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[Cueball sits at his desk in front of his computer leaning back and turning away from it to speak to a person off-panel.]&lt;br /&gt;
:Cueball: Can you take a look at the bug I just opened?&lt;br /&gt;
:Off-panel voice: Uh oh.&lt;br /&gt;
&lt;br /&gt;
:[Zoom out and pan to show only Cueball sitting on his chair facing away from the computer, which is now off-panel. The person speaking to him is still of panel even though this panel is much broader.]&lt;br /&gt;
:Off-panel voice: Is this a '''normal''' bug, or one of those horrifying ones that prove your whole project is broken beyond repair and should be burned to the ground?&lt;br /&gt;
&lt;br /&gt;
:[Zoom in on Cueballs head and upper torso.]&lt;br /&gt;
:Cueball: It's a normal one this time, I promise.&lt;br /&gt;
:Off-panel voice: OK, what's the bug?&lt;br /&gt;
&lt;br /&gt;
:[Back to a view similar to the first panel where Cueball has turned towards the computer and points at the screen with one hand.]&lt;br /&gt;
:Cueball: The server crashes if a user's password is a resolvable URL.&lt;br /&gt;
:Off-panel voice: I'll get the lighter fluid.&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Comics featuring Cueball]]&lt;br /&gt;
[[Category:Computers]]&lt;br /&gt;
[[Category:Programming]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:1700:_New_Bug&amp;diff=122599</id>
		<title>Talk:1700: New Bug</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:1700:_New_Bug&amp;diff=122599"/>
				<updated>2016-06-30T13:12:45Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--Please sign your posts with ~~~~--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
I'm new. For the explanation: A bug, as in a computer (programming) bug, can be reported and tracked, and many systems allow collaboration on the reporting and tracking of problems, or bugs, in code, and their solutions. Cueball reported a problem (bug) he found in the code, which presumably caused the server (program)&amp;amp;mdash;which he wrote as part of his project&amp;amp;mdash;to try to read the passwords as URLs before storing them. This exposes serious cross-site scripting attacks and other serious security vulnerabilities, and since handling password and user account information usually requires a lot of programming, this would be difficult to fix, which is why the character off-panel suggests burning the project down, as that would be much easier, and would solve any security problems, much more quickly than fixing the bug would. The comment text refers to Cueball's horrid solution to a horrid problem: Instead of solving the problem that is causing the server to read passwords as URLs, he can instead leverage a known problem in the programme which reads URLs which prevents it from reading a particular way of representing text in binary form, by adding a few characters to the user's password that the URL-reading program can't read. This would also &amp;quot;salt&amp;quot; the user's password, which is a security technique that makes passwords harder to figure out when they are stored properly. Cueball thinks this would solve the original problem, and two other problems at the same time, the second problem being the fact that user's passwords aren't salted (a security problem). The third solved problem is difficult to deduce.   &amp;amp;emsp;[[User:Zyzygy|Zyzygy]] 05:40, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
: The third bug is the unicode handling, which would need to be solved in order to salt passwords with emoji since these are unicode only character. Although I'm not sure if salting with emoji really increases security since as a rule i'd say nobody uses emoji in their passwords. [[Special:Contributions/162.158.85.123|162.158.85.123]] 06:34, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
::Password: 👍🐎🔋Π [[Special:Contributions/141.101.98.131|141.101.98.131]] 10:11, 29 June 2016 (UTC)&lt;br /&gt;
:::That is a really funny password, [[936: Password Strength|but is it strong ennough?]] :-) --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 20:22, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
:Actually, nobody using emoji in their password would be reason salting with emoji is MORE effective. Salting doesn't really increase security of single password, but it does increase security of whole password database, because you can hash some string - like, [http://www.telegraph.co.uk/technology/2016/01/26/most-common-passwords-revealed---and-theyre-ridiculously-easy-to/ 123456] and check whole database for users having that as password. If every password is salted with different emoji, this strategy will not work, because while you KNOW which emoji is used - the salt is stored unhashed with the password hash - it's always different so you need to compute new hash for every line in password database. Hashing takes MUCH more time than just comparing strings. And how it's even more effective? Because someone might actually get multiple databases and search for entries with same salt, hoping there will be enough of them to be worth it. And salt with emoji likely wouldn't be so common ... -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 09:54, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
From 108.162.221.22 (long rant)&lt;br /&gt;
:Two comments: first, the explanation on password salting is incorrect.  The current version says &amp;quot;Salting passwords increases security by adding random data to the passwords which primarily helps defend against dictionary attacks.&amp;quot;.  Password salting only protects against particular kinds of (common) attacks in specific situations.  Most importantly, it is designed to protect passwords only in the event ofa database breach, when a malicious user has gained direct access to the database itself.  Password salting provides no protection when brute force attacks (aka dictionary attacks) are directed at the application itself, as the application automatically takes hashes into account.  Instead, proper password salting randomizes the hash for each password, ensuring that if two users have the same password, they will not have the same hash.  This makes it much more difficult to guess passwords through attack vectors like lookup tables, reverse lookup tables, and rainbow tables.  However, because the salt has to be stored with the password (otherwise the application would not be able to make sense of the hash itself), password salting does not secure passwords against dictionary attacks even in the event that a malicious user has managed to acquire the database itself.  I will update the explanation with a brief description of what password salts do.&lt;br /&gt;
:Finally, I think there is a big misunderstanding throughout this explanation.  In a web services context the &amp;quot;server&amp;quot; (referenced in the comic) is a very different thing than the application that a programmer builds.  A server can refer to either the computer itself or the software that is responsible for responding to web requests and executing the actual application.  In a professional context, the application (which is what cueball would be building) would never be referred to as the &amp;quot;server&amp;quot;.  It is possible that this is a mis-use of terminology on the part of cueball or Randall, but I suspect that the term was used properly and intentionally.  The reason is because if cueball's application is crashing the *server*, it takes the level of incompetence up to completely new (and unusual) levels, in much the same way that he has done in the past.  Normally the programming language used to build the application, the software hosting the application, and the operating system itself have a number of safe guards in place to ensure that if an application misbehaves, the only thing that crashes is the application itself.  For cueball's application to break through all those safeguards and crash the server itself (either the operating system or the web server software) would require cueball to have developed a program that operates *well* outside the bounds of normal procedures.  Just for reference, as someone who has been building web software for over 15 years, I wouldn't even know where to start to crash the server from within an application. It would probably have to involve either exploiting a previously unknown bug in the programming language or some *very* poorly designed system calls.   [[Special:Contributions/108.162.221.22 15:11, 29 June 2016‎ 108.162.221.22]] (Rememeber to sign your comments) &lt;br /&gt;
&lt;br /&gt;
Regarding those last two points: sorry for my long unsigned rant.  Didn't realize I wasn't logged in.  Still haven't figured out how to sign comments.  Gonna try it this time. [[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]]) 16:51, 29 June 2016 (UTC)--&lt;br /&gt;
:You made it ;-) --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 20:22, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Explanation says &amp;quot;There is no reason for password handling code to access urls&amp;quot; but that is somewhat wrong -- Password handling code frequently perform heuristics on the password to assess the strength, for example checking if part of the password is a dictionary word -- similar heuristics could be done to check thatthe password is not a URL, such as &amp;quot;xkcd.com&amp;quot; applying DNS and other internet resources as an extention of the concept of &amp;quot;dictionary&amp;quot;. [[User:Spongebog|Spongebob]] ([[User talk:Spongebog|talk]]) 16:11, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Currently the explanation says: &amp;quot;Finally, emoji will often include unicode characters, which means that, if one can effectively salt passwords with emoji, then the passwords should be able to be stored in unicode (although that *probably* doesn't require anything outside the Base Multilingual Plane, so that might not need full unicode support after-all).&amp;quot;  I'm fairly convinced that this doesn't make sense and is incorrect.  Regardless of what character encoding the password is in, hashing will convert the entire thing into binary.  This binary is then typically stored as a base64-encoded string in the database.  Ergo, it doesn't matter whether the original password strings were in unicode or not: they will be stored in the database as ascii (or binary), not unicode.  I'm going to go ahead and remove this comment from the explanation.  I'm pretty certain that there isn't enough information in the comic to figure out why salting passwords with emoji would fix a unicode-handling bug in the URL request library.  So I suspect that there is no explanation there: either Cueball is entirely confused and his statement makes no sense, or there is simply not enough information given to help us understand why this solution might fix the problem.  However, I'm not going to make any updates to the explanation about this yet, because perhaps I'm missing something someone else will notice. [[User:Cmancone|Cmancone]] 12:50, 29 June 2016 (ETC)&lt;br /&gt;
:I suspect that the salting with emoji is to ensure that the password does not resolve as a URL (since the library cannot understand the encoding), and thus the issue of the crash is resolved, the issue of unsalted passwords is solved, and the issue of the unicode handling bug is &amp;quot;solved&amp;quot; by virtue of it now being a feature relied on by the system. [[Special:Contributions/173.245.56.68|173.245.56.68]] 20:50, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
I removed from the explanation the discussion about how Cueball's system might be checking passwords to see if they are resolvable URLs as a check against weak passwords.  The problem with this explanation is that if that is where the crash was happening, then salting the password with emoji would not fix the crash.  For salting to fix the crash (as Cueball suggests it will) requires that the crash be happening during the hashing process, not during password validation.  The reason is because password validation is performed on the original password itself, while only hashing happens on the salted password.  So for salting to fix the crash it must be happening during hashing, not validation.  If the bug is happening while checking passwords for strength then Cueball's suggestion of fixing it by adding in a salt will not actually fix the crash at all.  It could be that Cueball is simply completely wrong about everything, but I think it makes more sense to go with an explanation where the title text didn't just get everything wrong.[[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]]) 13:12, 30 June 2016 (UTC)&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1700:_New_Bug&amp;diff=122598</id>
		<title>1700: New Bug</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1700:_New_Bug&amp;diff=122598"/>
				<updated>2016-06-30T13:05:04Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: Reworded, reworked, and removed some text which seemed incorrect (added my reasoning to the discussion)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1700&lt;br /&gt;
| date      = June 29, 2016&lt;br /&gt;
| title     = New Bug&lt;br /&gt;
| image     = new_bug.png&lt;br /&gt;
| titletext = There's also a unicode-handling bug in the URL request library, and we're storing the passwords unsalted ... so if we salt them with emoji, we can close three issues at once!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|How does salting with emoji fix the unicode-handling bug in the URL request library?  Does it really? Additionally, this explanation requires a thorough grammar and spelling fix from the fourth paragraph onward.}}&lt;br /&gt;
&lt;br /&gt;
[[Cueball]] asks if an off-panel character can look at his bug report. The person asks if it's a &amp;quot;normal one&amp;quot; and not a &amp;quot;horrifying&amp;quot; one which &amp;quot;proves that the whole project is broken beyond repair and should be burnt to the ground&amp;quot;. This implies that there have been reports of the &amp;quot;horrifying&amp;quot; variety in the past. &lt;br /&gt;
&lt;br /&gt;
Cueball promises that it is a normal one but it turns out that the server crashes when a user's password is a resolvable URL, which implies that the server is in some way attempting to resolve passwords as if they were URLs. A resolvable URL is one that is syntactically correct and refers to a find-able and accessible resource on the internet (i.e. does not return a {{w|HTTP_404|404 error}} or equivalent when resolved).  Therefore a resolvable URL is a {{w|Fully_qualified_domain_name|fully qualified domain name}} or a valid ip address that points to a valid server, and it can optionally specify a resource that exists on that server.  Normally there is no reason for a system to treat a password as if it were a URL.&lt;br /&gt;
&lt;br /&gt;
Also, Cueball specifically states that the server is crashing, rather than his application.  While this could be an example of misused terminology on the part of Cueball or Randall, given Cueball's history his choice of terms is probably accurate.  In the context of web services the server refers to either the computer itself or the program that responds to web requests and executes the user's (i.e. Cueball's) application.  Cueball would be in charge of building the application.  The importance of this distinction is that a typical system has safe guards in place at many levels to prevent a misbehaving application from crashing anything other than itself.  So for his application to crash the server (either the computer itself or the server software hosting his application) would require his application to be operating in a way far outside of the norm, which has been the case for Cueball in previous comics.  Alternatively, the project might include its own server software without the safeguards.  In either case it is clear that Cueball's issue is far from normal, for which reason the off-panel person gives up and decides that burning the project to the ground is the only solution, telling Cueball ''I'll get the {{w|Charcoal_lighter_fluid|lighter fluid}}''. &lt;br /&gt;
&lt;br /&gt;
In the title text another two issues with Cueball's program are mentioned, together with a possible solution that would fix all three problems at once. The second problem is a unicode-handling bug in the URL request library, and the third is that the passwords are stored unsalted.  The proposed solution is to salt the passwords with {{w|emoji}} (unicode, multi-byte characters), which is claimed to solve all three issues at once.  {{w|Salt (cryptography)|Salting}} passwords means that random characters are added to the password before it is cryptographically-secured and stored in the database. Salting increases security in the event that the database is compromised by ensuring that users with the same password will not have the same password hash.  This makes some attacks that can be used to crack hash databases, such as {{w|Rainbow table|rainbow tables}}, effectively impossible.&lt;br /&gt;
&lt;br /&gt;
Salting passwords with emoji can potentially &amp;quot;fix&amp;quot; these bugs in different ways.  First, emoji and other unicode characters are not valid characters in URLs.  As a result the salted-passwords will no longer be resolvable URLs. This will presumably circumvent (but not actually fix) the bug that causes the server to crash.  In addition, the passwords will now be salted, increasing security.  There is no obvious way that this would actually fix a unicode-handling bug in the URL request library.  Given Cueball's general approach to problems like this, the best explanation is probably that he hasn't &amp;quot;fixed&amp;quot; the bug but rather that it is no longer a bug because he is relying on its behavior to help fix these other issues, i.e. the classic [http://www.urbandictionary.com/define.php?term=It%27s%20not%20a%20bug%2C%20it%27s%20a%20feature it's not a bug, it's a feature].&lt;br /&gt;
&lt;br /&gt;
The title text shows that his general approach to problems is not to actually fix bugs but to work around them and even rely on them for other behavior.  This approach to software development makes for terrible code, which is likely how Cueball got into this trouble in the first place, showing that he still has yet to learn from his mistakes, and once again emphasizing the need to just burn the whole thing down.&lt;br /&gt;
&lt;br /&gt;
Given that this comic comes only five comics after [[1695: Code Quality 2]] it seems likely that the off-panel person is [[Ponytail]] and as could be seen in the first of those two comics, [[1513: Code Quality]], the perpetrator is indeed Cueball. In the title text of the first, using emoji in variable names is mentioned.&lt;br /&gt;
&lt;br /&gt;
In [[1349: Shouldn't Be Hard]] Cueball is also programming and finding it very difficult, although he thinks it should be easy. An off-panel person suggests burning the computer down with a blowtorch, much like the off-panel person in this one suggests burning the whole project (including the computer) to the ground with lighter fluid. In the next comic, with multiple storylines [[1350: Lorenz]], one [http://xkcd.com/1350/#p:2ed958de-badf-11e3-8001-002590d77bdd story line] results in a computer being [http://www.explainxkcd.com/wiki/images/a/a6/lorenz_-_laptop_9.png burned with a blow torch].&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[Cueball sits at his desk in front of his computer leaning back and turning away from it to speak to a person off-panel.]&lt;br /&gt;
:Cueball: Can you take a look at the bug I just opened?&lt;br /&gt;
:Off-panel voice: Uh oh.&lt;br /&gt;
&lt;br /&gt;
:[Zoom out and pan to show only Cueball sitting on his chair facing away from the computer, which is now off-panel. The person speaking to him is still of panel even though this panel is much broader.]&lt;br /&gt;
:Off-panel voice: Is this a '''normal''' bug, or one of those horrifying ones that prove your whole project is broken beyond repair and should be burned to the ground?&lt;br /&gt;
&lt;br /&gt;
:[Zoom in on Cueballs head and upper torso.]&lt;br /&gt;
:Cueball: It's a normal one this time, I promise.&lt;br /&gt;
:Off-panel voice: OK, what's the bug?&lt;br /&gt;
&lt;br /&gt;
:[Back to a view similar to the first panel where Cueball has turned towards the computer and points at the screen with one hand.]&lt;br /&gt;
:Cueball: The server crashes if a user's password is a resolvable URL.&lt;br /&gt;
:Off-panel voice: I'll get the lighter fluid.&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Comics featuring Cueball]]&lt;br /&gt;
[[Category:Computers]]&lt;br /&gt;
[[Category:Programming]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1700:_New_Bug&amp;diff=122569</id>
		<title>1700: New Bug</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1700:_New_Bug&amp;diff=122569"/>
				<updated>2016-06-29T16:59:52Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: /* Explanation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1700&lt;br /&gt;
| date      = June 29, 2016&lt;br /&gt;
| title     = New Bug&lt;br /&gt;
| image     = new_bug.png&lt;br /&gt;
| titletext = There's also a unicode-handling bug in the URL request library, and we're storing the passwords unsalted ... so if we salt them with emoji, we can close three issues at once!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|How does salting with emoji fix the unicode-handling bug in the URL request library?  Does it really?}}&lt;br /&gt;
&lt;br /&gt;
[[Cueball]] asks if an off-panel character can look at his bug report. The person asks if it's a &amp;quot;normal one&amp;quot; and not a &amp;quot;horrifying&amp;quot; one which &amp;quot;proves that the whole project is broken beyond repair and should be burnt to the ground&amp;quot;. This implies that there have been reports of the &amp;quot;horrifying&amp;quot; variety in the past. &lt;br /&gt;
&lt;br /&gt;
Cueball promises that it is a normal one but it turns out that the server crashes when a user's password is a resolvable URL, which implies that the server is in some way attempting to resolve passwords as if they were URLs. A resolvable URL is one that is syntactically correct and refers to a find-able and accessible resource on the internet (i.e. does not return a {{w|HTTP_404|404 error}} or equivalent when resolved).  This can be because it contains a {{w|Fully_qualified_domain_name|fully qualified domain name}} or a valid ip address, and optionally (in either case) a resource that exists on the destination server.&lt;br /&gt;
&lt;br /&gt;
Also, Cueball specifically states that the server is crashing, rather than his application.  While this could be an example of misused terminology on the part of Cueball or Randall, given Cueball's history his choice of terms is probably accurate.  In the context of web services the server refers to either the computer itself or the program that responds to web requests and executes the user's (i.e. Cueball's) application.  Cueball would be in charge of building the application.  The importance of this distinction is that a typical system has safe guards in place at many levels to prevent a misbehaving application from crashing anything other than itself.  So for his application to crash the server (either the computer itself or the server software hosting his application) would require his application to be operating in a way far outside of the norm.  Alternatively, the project might include its own server software without the safeguards.   &lt;br /&gt;
&lt;br /&gt;
While there appears to be little reason for the code that processes passwords to attempt to resolve the input string as a URL, then a common function in password programs is the functionality of assessing the strength of a password, using a combinations of heuristic testing for uniqueness, length, good use of mixed characters and dictionary lookups for common words -- this password function have extended the dictionary lookups to using {{w|DNS}} names and URLs, so people choosing a password like &amp;quot;XKCD.com&amp;quot; would be given a low strength score, even that no part of it is a dictionary word and it contain both upper, lower case and special characters.  However, accessing the internet in any security function like password creation open up, not only possibility of new bugs like the one mentioned, but also a completely new set of security issues which is not what you want from a critical function handling passwords.  Realizing the wealth of new security issues, the off-panel person resigns and decides that burning the project to the ground is the only solution, telling Cueball ''I'll get the {{w|Butane|lighter fluid}}''. &lt;br /&gt;
&lt;br /&gt;
In the title text another two issues with Cueballs program are mentioned together with a possible solution that would fix all three problems at once. The second problem is unicode-handling bug in the URL request library, and the third is that the passwords are stored unsalted. {{w|Salt (cryptography)|Salting}} passwords increases security in the event that the database is compromised by ensuring that users with the same password will not have the same password hash.  This makes some attacks used to decipher hash databases, such as {{w|Rainbow table|rainbow tables}}, effectively impossible.&lt;br /&gt;
&lt;br /&gt;
The proposed solution is to salt the passwords with {{w|emoji}}, which is claimed to solve all three issues at once.&lt;br /&gt;
&lt;br /&gt;
When the passwords are salted with emoji, the URL request library will fail to resolve any (salted) passwords because emoji are not valid characters in URLs. Since the server only crashes on ''resolvable'' URLs, this should mean the server won't crash anymore. In addition, the passwords will now be salted.&lt;br /&gt;
&lt;br /&gt;
Given that this comic comes only five comics after [[1695: Code Quality 2]] is seems likely that the off-panel person is [[Ponytail]] and as could be seen in the first of those two comics, [[1513: Code Quality]], the perpetrator is indeed Cueball. In the title text of this first one, using emoji in variable names is mentioned.&lt;br /&gt;
&lt;br /&gt;
In [[1349: Shouldn't Be Hard]] Cueball is also programming and finding it very difficult in-spite that he thinks is should be easy. An off-panel person suggest burning the computer down with a blowtorch much like the off-panel person in this one suggest burning the whole project (including the computer) to the ground with lighter fluid. In the very next comic, the multi storyline [[1350: Lorenz]], one [http://xkcd.com/1350/#p:2ed958de-badf-11e3-8001-002590d77bdd story line] results in a computer being [http://www.explainxkcd.com/wiki/images/a/a6/lorenz_-_laptop_9.png burned with a blow torch].&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[Cueball sits at his desk in front of his computer leaning back and turning away from it to speak to a person off-panel.]&lt;br /&gt;
:Cueball: Can you take a look at the bug I just opened?&lt;br /&gt;
:Off-panel voice: Uh oh.&lt;br /&gt;
&lt;br /&gt;
:[Zoom out and pan to show only Cueball sitting on his chair facing away from the computer, which is now off-panel. The person speaking to him is still of panel even though this panel is much broader.]&lt;br /&gt;
:Off-panel voice: Is this a '''normal''' bug, or one of those horrifying ones that prove your whole project is broken beyond repair and should be burned to the ground?&lt;br /&gt;
&lt;br /&gt;
:[Zoom in on Cueballs head and upper torso.]&lt;br /&gt;
:Cueball: It's a normal one this time, I promise.&lt;br /&gt;
:Off-panel voice: OK, what's the bug?&lt;br /&gt;
&lt;br /&gt;
:[Back to a view similar to the first panel where Cueball has turned towards the computer and points at the screen with one hand.]&lt;br /&gt;
:Cueball: The server crashes if a user's password is a resolvable URL.&lt;br /&gt;
:Off-panel voice: I'll get the lighter fluid.&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Comics featuring Cueball]]&lt;br /&gt;
[[Category:Computers]]&lt;br /&gt;
[[Category:Programming]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:1700:_New_Bug&amp;diff=122568</id>
		<title>Talk:1700: New Bug</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:1700:_New_Bug&amp;diff=122568"/>
				<updated>2016-06-29T16:51:49Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--Please sign your posts with ~~~~--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
I'm new. For the explanation: A bug, as in a computer (programming) bug, can be reported and tracked, and many systems allow collaboration on the reporting and tracking of problems, or bugs, in code, and their solutions. Cueball reported a problem (bug) he found in the code, which presumably caused the server (program)&amp;amp;mdash;which he wrote as part of his project&amp;amp;mdash;to try to read the passwords as URLs before storing them. This exposes serious cross-site scripting attacks and other serious security vulnerabilities, and since handling password and user account information usually requires a lot of programming, this would be difficult to fix, which is why the character off-panel suggests burning the project down, as that would be much easier, and would solve any security problems, much more quickly than fixing the bug would. The comment text refers to Cueball's horrid solution to a horrid problem: Instead of solving the problem that is causing the server to read passwords as URLs, he can instead leverage a known problem in the programme which reads URLs which prevents it from reading a particular way of representing text in binary form, by adding a few characters to the user's password that the URL-reading program can't read. This would also &amp;quot;salt&amp;quot; the user's password, which is a security technique that makes passwords harder to figure out when they are stored properly. Cueball thinks this would solve the original problem, and two other problems at the same time, the second problem being the fact that user's passwords aren't salted (a security problem). The third solved problem is difficult to deduce.   &amp;amp;emsp;[[User:Zyzygy|Zyzygy]] 05:40, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
: The third bug is the unicode handling, which would need to be solved in order to salt passwords with emoji since these are unicode only character. Although I'm not sure if salting with emoji really increases security since as a rule i'd say nobody uses emoji in their passwords. [[Special:Contributions/162.158.85.123|162.158.85.123]] 06:34, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
::Password: 👍🐎🔋Π [[Special:Contributions/141.101.98.131|141.101.98.131]] 10:11, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
:Actually, nobody using emoji in their password would be reason salting with emoji is MORE effective. Salting doesn't really increase security of single password, but it does increase security of whole password database, because you can hash some string - like, [http://www.telegraph.co.uk/technology/2016/01/26/most-common-passwords-revealed---and-theyre-ridiculously-easy-to/ 123456] and check whole database for users having that as password. If every password is salted with different emoji, this strategy will not work, because while you KNOW which emoji is used - the salt is stored unhashed with the password hash - it's always different so you need to compute new hash for every line in password database. Hashing takes MUCH more time than just comparing strings. And how it's even more effective? Because someone might actually get multiple databases and search for entries with same salt, hoping there will be enough of them to be worth it. And salt with emoji likely wouldn't be so common ... -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 09:54, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
From 108.162.221.22 (long rant)&lt;br /&gt;
:Two comments: first, the explanation on password salting is incorrect.  The current version says &amp;quot;Salting passwords increases security by adding random data to the passwords which primarily helps defend against dictionary attacks.&amp;quot;.  Password salting only protects against particular kinds of (common) attacks in specific situations.  Most importantly, it is designed to protect passwords only in the event ofa database breach, when a malicious user has gained direct access to the database itself.  Password salting provides no protection when brute force attacks (aka dictionary attacks) are directed at the application itself, as the application automatically takes hashes into account.  Instead, proper password salting randomizes the hash for each password, ensuring that if two users have the same password, they will not have the same hash.  This makes it much more difficult to guess passwords through attack vectors like lookup tables, reverse lookup tables, and rainbow tables.  However, because the salt has to be stored with the password (otherwise the application would not be able to make sense of the hash itself), password salting does not secure passwords against dictionary attacks even in the event that a malicious user has managed to acquire the database itself.  I will update the explanation with a brief description of what password salts do.&lt;br /&gt;
:Finally, I think there is a big misunderstanding throughout this explanation.  In a web services context the &amp;quot;server&amp;quot; (referenced in the comic) is a very different thing than the application that a programmer builds.  A server can refer to either the computer itself or the software that is responsible for responding to web requests and executing the actual application.  In a professional context, the application (which is what cueball would be building) would never be referred to as the &amp;quot;server&amp;quot;.  It is possible that this is a mis-use of terminology on the part of cueball or Randall, but I suspect that the term was used properly and intentionally.  The reason is because if cueball's application is crashing the *server*, it takes the level of incompetence up to completely new (and unusual) levels, in much the same way that he has done in the past.  Normally the programming language used to build the application, the software hosting the application, and the operating system itself have a number of safe guards in place to ensure that if an application misbehaves, the only thing that crashes is the application itself.  For cueball's application to break through all those safeguards and crash the server itself (either the operating system or the web server software) would require cueball to have developed a program that operates *well* outside the bounds of normal procedures.  Just for reference, as someone who has been building web software for over 15 years, I wouldn't even know where to start to crash the server from within an application. It would probably have to involve either exploiting a previously unknown bug in the programming language or some *very* poorly designed system calls.   [[Special:Contributions/108.162.221.22 15:11, 29 June 2016‎ 108.162.221.22]] (Rememeber to sign your comments) &lt;br /&gt;
&lt;br /&gt;
Regarding those last two points: sorry for my long unsigned rant.  Didn't realize I wasn't logged in.  Still haven't figured out how to sign comments.  Gonna try it this time. [[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]]) 16:51, 29 June 2016 (UTC)--&lt;br /&gt;
&lt;br /&gt;
Explanation says &amp;quot;There is no reason for password handling code to access urls&amp;quot; but that is somewhat wrong -- Password handling code frequently perform heuristics on the password to assess the strength, for example checking if part of the password is a dictionary word -- similar heuristics could be done to check thatthe password is not a URL, such as &amp;quot;xkcd.com&amp;quot; applying DNS and other internet resources as an extention of the concept of &amp;quot;dictionary&amp;quot;. [[User:Spongebog|Spongebob]] ([[User talk:Spongebog|talk]]) 16:11, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Currently the explanation says: &amp;quot;Finally, emoji will often include unicode characters, which means that, if one can effectively salt passwords with emoji, then the passwords should be able to be stored in unicode (although that *probably* doesn't require anything outside the Base Multilingual Plane, so that might not need full unicode support after-all).&amp;quot;  I'm fairly convinced that this doesn't make sense and is incorrect.  Regardless of what character encoding the password is in, hashing will convert the entire thing into binary.  This binary is then typically stored as a base64-encoded string in the database.  Ergo, it doesn't matter whether the original password strings were in unicode or not: they will be stored in the database as ascii (or binary), not unicode.  I'm going to go ahead and remove this comment from the explanation.  I'm pretty certain that there isn't enough information in the comic to figure out why salting passwords with emoji would fix a unicode-handling bug in the URL request library.  So I suspect that there is no explanation there: either Cueball is entirely confused and his statement makes no sense, or there is simply not enough information given to help us understand why this solution might fix the problem.  However, I'm not going to make any updates to the explanation about this yet, because perhaps I'm missing something someone else will notice. [[User:Cmancone|Cmancone]] 12:50, 29 June 2016 (ETC)&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:1700:_New_Bug&amp;diff=122567</id>
		<title>Talk:1700: New Bug</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:1700:_New_Bug&amp;diff=122567"/>
				<updated>2016-06-29T16:49:29Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--Please sign your posts with ~~~~--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
I'm new. For the explanation: A bug, as in a computer (programming) bug, can be reported and tracked, and many systems allow collaboration on the reporting and tracking of problems, or bugs, in code, and their solutions. Cueball reported a problem (bug) he found in the code, which presumably caused the server (program)&amp;amp;mdash;which he wrote as part of his project&amp;amp;mdash;to try to read the passwords as URLs before storing them. This exposes serious cross-site scripting attacks and other serious security vulnerabilities, and since handling password and user account information usually requires a lot of programming, this would be difficult to fix, which is why the character off-panel suggests burning the project down, as that would be much easier, and would solve any security problems, much more quickly than fixing the bug would. The comment text refers to Cueball's horrid solution to a horrid problem: Instead of solving the problem that is causing the server to read passwords as URLs, he can instead leverage a known problem in the programme which reads URLs which prevents it from reading a particular way of representing text in binary form, by adding a few characters to the user's password that the URL-reading program can't read. This would also &amp;quot;salt&amp;quot; the user's password, which is a security technique that makes passwords harder to figure out when they are stored properly. Cueball thinks this would solve the original problem, and two other problems at the same time, the second problem being the fact that user's passwords aren't salted (a security problem). The third solved problem is difficult to deduce.   &amp;amp;emsp;[[User:Zyzygy|Zyzygy]] 05:40, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
: The third bug is the unicode handling, which would need to be solved in order to salt passwords with emoji since these are unicode only character. Although I'm not sure if salting with emoji really increases security since as a rule i'd say nobody uses emoji in their passwords. [[Special:Contributions/162.158.85.123|162.158.85.123]] 06:34, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
::Password: 👍🐎🔋Π [[Special:Contributions/141.101.98.131|141.101.98.131]] 10:11, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
:Actually, nobody using emoji in their password would be reason salting with emoji is MORE effective. Salting doesn't really increase security of single password, but it does increase security of whole password database, because you can hash some string - like, [http://www.telegraph.co.uk/technology/2016/01/26/most-common-passwords-revealed---and-theyre-ridiculously-easy-to/ 123456] and check whole database for users having that as password. If every password is salted with different emoji, this strategy will not work, because while you KNOW which emoji is used - the salt is stored unhashed with the password hash - it's always different so you need to compute new hash for every line in password database. Hashing takes MUCH more time than just comparing strings. And how it's even more effective? Because someone might actually get multiple databases and search for entries with same salt, hoping there will be enough of them to be worth it. And salt with emoji likely wouldn't be so common ... -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 09:54, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
From 108.162.221.22 (long rant)&lt;br /&gt;
:Two comments: first, the explanation on password salting is incorrect.  The current version says &amp;quot;Salting passwords increases security by adding random data to the passwords which primarily helps defend against dictionary attacks.&amp;quot;.  Password salting only protects against particular kinds of (common) attacks in specific situations.  Most importantly, it is designed to protect passwords only in the event ofa database breach, when a malicious user has gained direct access to the database itself.  Password salting provides no protection when brute force attacks (aka dictionary attacks) are directed at the application itself, as the application automatically takes hashes into account.  Instead, proper password salting randomizes the hash for each password, ensuring that if two users have the same password, they will not have the same hash.  This makes it much more difficult to guess passwords through attack vectors like lookup tables, reverse lookup tables, and rainbow tables.  However, because the salt has to be stored with the password (otherwise the application would not be able to make sense of the hash itself), password salting does not secure passwords against dictionary attacks even in the event that a malicious user has managed to acquire the database itself.  I will update the explanation with a brief description of what password salts do.&lt;br /&gt;
:Finally, I think there is a big misunderstanding throughout this explanation.  In a web services context the &amp;quot;server&amp;quot; (referenced in the comic) is a very different thing than the application that a programmer builds.  A server can refer to either the computer itself or the software that is responsible for responding to web requests and executing the actual application.  In a professional context, the application (which is what cueball would be building) would never be referred to as the &amp;quot;server&amp;quot;.  It is possible that this is a mis-use of terminology on the part of cueball or Randall, but I suspect that the term was used properly and intentionally.  The reason is because if cueball's application is crashing the *server*, it takes the level of incompetence up to completely new (and unusual) levels, in much the same way that he has done in the past.  Normally the programming language used to build the application, the software hosting the application, and the operating system itself have a number of safe guards in place to ensure that if an application misbehaves, the only thing that crashes is the application itself.  For cueball's application to break through all those safeguards and crash the server itself (either the operating system or the web server software) would require cueball to have developed a program that operates *well* outside the bounds of normal procedures.  Just for reference, as someone who has been building web software for over 15 years, I wouldn't even know where to start to crash the server from within an application. It would probably have to involve either exploiting a previously unknown bug in the programming language or some *very* poorly designed system calls.   [[Special:Contributions/108.162.221.22 15:11, 29 June 2016‎ 108.162.221.22]] (Rememeber to sign your comments) &lt;br /&gt;
&lt;br /&gt;
Explanation says &amp;quot;There is no reason for password handling code to access urls&amp;quot; but that is somewhat wrong -- Password handling code frequently perform heuristics on the password to assess the strength, for example checking if part of the password is a dictionary word -- similar heuristics could be done to check thatthe password is not a URL, such as &amp;quot;xkcd.com&amp;quot; applying DNS and other internet resources as an extention of the concept of &amp;quot;dictionary&amp;quot;. [[User:Spongebog|Spongebob]] ([[User talk:Spongebog|talk]]) 16:11, 29 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Currently the explanation says: &amp;quot;Finally, emoji will often include unicode characters, which means that, if one can effectively salt passwords with emoji, then the passwords should be able to be stored in unicode (although that *probably* doesn't require anything outside the Base Multilingual Plane, so that might not need full unicode support after-all).&amp;quot;  I'm fairly convinced that this doesn't make sense and is incorrect.  Regardless of what character encoding the password is in, hashing will convert the entire thing into binary.  This binary is then typically stored as a base64-encoded string in the database.  Ergo, it doesn't matter whether the original password strings were in unicode or not: they will be stored in the database as ascii (or binary), not unicode.  I'm going to go ahead and remove this comment from the explanation.  I'm pretty certain that there isn't enough information in the comic to figure out why salting passwords with emoji would fix a unicode-handling bug in the URL request library.  So I suspect that there is no explanation there: either Cueball is entirely confused and his statement makes no sense, or there is simply not enough information given to help us understand why this solution might fix the problem.  However, I'm not going to make any updates to the explanation about this yet, because perhaps I'm missing something someone else will notice.&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1700:_New_Bug&amp;diff=122557</id>
		<title>1700: New Bug</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1700:_New_Bug&amp;diff=122557"/>
				<updated>2016-06-29T15:49:13Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: /* Explanation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1700&lt;br /&gt;
| date      = June 29, 2016&lt;br /&gt;
| title     = New Bug&lt;br /&gt;
| image     = new_bug.png&lt;br /&gt;
| titletext = There's also a unicode-handling bug in the URL request library, and we're storing the passwords unsalted ... so if we salt them with emoji, we can close three issues at once!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|How does salting with emoji fix the unicode-handling bug in the URL request library?  Does it really?}}&lt;br /&gt;
&lt;br /&gt;
[[Cueball]] asks if an off-panel character can look at his bug report. The person asks if it's a &amp;quot;normal one&amp;quot; and not a &amp;quot;horrifying&amp;quot; one which &amp;quot;proves that the whole project is broken beyond repair and should be burnt to the ground&amp;quot;. This implies that there have been reports of the &amp;quot;horrifying&amp;quot; variety in the past. &lt;br /&gt;
&lt;br /&gt;
Cueball promises that it is a normal one but it turns out that the server crashes when a user's password is a resolvable URL, which implies that the server is in some way attempting to resolve passwords as if they were URLs. A resolvable URL is one that is syntactically correct and refers to a find-able and accessible resource on the internet (i.e. does not return a {{w|HTTP_404|404 error}} or equivalent when resolved).  This can be because it contains a {{w|Fully_qualified_domain_name|fully qualified domain name}} or a valid ip address, and optionally (in either case) a resource that exists on the destination server.&lt;br /&gt;
&lt;br /&gt;
Also, Cueball specifically states that the server is crashing, rather than his application.  While this could be an example of misused terminology on the part of Cueball or Randall, given Cueball's history his choice of terms is probably accurate.  In the context of web services the server refers to either the computer itself or the program that responds to web requests and executes the user's (i.e. Cueball's) application.  Cueball would be in charge of building the application.  The importance of this distinction is that a typical system has safe guards in place at many levels to prevent a misbehaving application from crashing anything other than itself.  So for his application to crash the server (either the computer itself or the server software hosting his application) would require his application to be operating in a way far outside of the norm.&lt;br /&gt;
&lt;br /&gt;
There is no reason for the code that processes passwords to attempt to resolve the input string as a URL, so any bug provoked by such input suggests a fundamental error in the way the server handles passwords.  Realizing this, the off-panel person resigns and decides that burning the project to the ground is the only solution, telling Cueball ''I'll get the {{w|Butane|lighter fluid}}''. &lt;br /&gt;
&lt;br /&gt;
In the title text another two issues with Cueballs program are mentioned together with a possible solution that would fix all three problems at once. The second problem is unicode-handling bug in the URL request library, and the third is that the passwords are stored unsalted. {{w|Salt (cryptography)|Salting}} passwords increases security in the event that the database is compromised by ensuring that users with the same password will not have the same password hash.  This makes some attacks used to decipher hash databases, such as {{w|Rainbow table|rainbow tables}}, effectively impossible.&lt;br /&gt;
&lt;br /&gt;
The proposed solution is to salt the passwords with {{w|emoji}}, which is claimed to solve all three issues at once.&lt;br /&gt;
&lt;br /&gt;
When the passwords are salted with emoji, the URL request library will fail to resolve any (salted) passwords because emoji are not valid characters in URLs. Since the server only crashes on ''resolvable'' URLs, this should mean the server won't crash anymore. In addition, the passwords will now be salted. Finally, emoji will often include unicode characters, which means that, if one can effectively salt passwords with emoji, then the passwords should be able to be stored in unicode (although that *probably* doesn't require anything outside the Base Multilingual Plane, so that might not need full unicode support after-all).&lt;br /&gt;
&lt;br /&gt;
Given that this comic comes only five comics after [[1695: Code Quality 2]] is seems likely that the off-panel person is [[Ponytail]] and as could be seen in the first of those two comics, [[1513: Code Quality]], the perpetrator is indeed Cueball. In the title text of this first one, using emoji in variable names is mentioned.&lt;br /&gt;
&lt;br /&gt;
In [[1349: Shouldn't Be Hard]] Cueball is also programming and finding it very difficult in-spite that he thinks is should be easy. An off-panel person suggest burning the computer down with a blowtorch much like the off-panel person in this one suggest burning the whole project (including the computer) to the ground with lighter fluid. In the very next comic, the multi storyline [[1350: Lorenz]], one [http://xkcd.com/1350/#p:2ed958de-badf-11e3-8001-002590d77bdd story line] results in a computer being [http://www.explainxkcd.com/wiki/images/a/a6/lorenz_-_laptop_9.png burned with a blow torch].&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[Cueball sits at his desk in front of his computer leaning back and turning away from it to speak to a person off-panel.]&lt;br /&gt;
:Cueball: Can you take a look at the bug I just opened?&lt;br /&gt;
:Off-panel voice: Uh oh.&lt;br /&gt;
&lt;br /&gt;
:[Zoom out and pan to show only Cueball sitting on his chair facing away from the computer, which is now off-panel. The person speaking to him is still of panel even though this panel is much broader.]&lt;br /&gt;
:Off-panel voice: Is this a '''normal''' bug, or one of those horrifying ones that prove your whole project is broken beyond repair and should be burned to the ground?&lt;br /&gt;
&lt;br /&gt;
:[Zoom in on Cueballs head and upper torso.]&lt;br /&gt;
:Cueball: It's a normal one this time, I promise.&lt;br /&gt;
:Off-panel voice: OK, what's the bug?&lt;br /&gt;
&lt;br /&gt;
:[Back to a view similar to the first panel where Cueball has turned towards the computer and points at the screen with one hand.]&lt;br /&gt;
:Cueball: The server crashes if a user's password is a resolvable URL.&lt;br /&gt;
:Off-panel voice: I'll get the lighter fluid.&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Comics featuring Cueball]]&lt;br /&gt;
[[Category:Computers]]&lt;br /&gt;
[[Category:Programming]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1698:_Theft_Quadrants&amp;diff=122412</id>
		<title>1698: Theft Quadrants</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1698:_Theft_Quadrants&amp;diff=122412"/>
				<updated>2016-06-27T13:17:06Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: /* Explanation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1698&lt;br /&gt;
| date      = June 24, 2016&lt;br /&gt;
| title     = Theft Quadrants&lt;br /&gt;
| image     = theft quadrants.png&lt;br /&gt;
| titletext = TinyURL was the most popular link shortener for long enough that it made it into a lot of printed publications. I wonder what year the domain will finally lapse and get picked up by a porn site.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|How difficult would it be to steal TinyURL, really? Is it a real problem?}}&lt;br /&gt;
&lt;br /&gt;
This is a &amp;quot;{{w|Time management#The Eisenhower Method|Eisenhower box}}&amp;quot; comparing how difficult it is to steal a specified thing with the severity of the theft.&lt;br /&gt;
&lt;br /&gt;
It is very hard to steal {{w|Gold Codes|nuclear launch codes}}. They are protected by many layers of federal security. That's a good thing, too, since if they were stolen, they could be used to start a {{w|Nuclear warfare|nuclear war}} which would be bad{{Citation needed}}.&lt;br /&gt;
&lt;br /&gt;
It is also hard to steal the {{w|Crown Jewels of the United Kingdom|Crown Jewels}}, since they are protected by a [http://yeomenoftheguard.com/Windsor%20Castle.jpg complex security system]. But if they were stolen, it wouldn't be so bad for most people.&lt;br /&gt;
&lt;br /&gt;
It wouldn't be too hard to steal the a {{w|Wienermobile}} (a car shaped like a hot-dog, advertising the Oscar Mayer brand). There have been made several versions of this car, and it would not be more difficult to steal than any other car, although harder to hide though.  [[Randall]] seems to considers that such a stolen vehicles would not be too bad, although he has previously refereed to a stolen Wienermobile in [[935: Missed Connections]], which is driven recklessly almost hitting someone. But it is not bad enough to consider it a big problem in a context where it is compared with stolen nuclear codes.&lt;br /&gt;
&lt;br /&gt;
It also wouldn't be hard (or at least, not as hard as stealing nuclear launch codes or the Crown Jewels) to steal the {{w|TinyURL|tinyurl.com}} domain name, but the consequences of that could be significant and is thus listed under very bad. The joke if of course that this is listed as just as bad as the risk of a nuclear war, and of course it is not as significant, but it could swiftly result in damage to a lot of important computers, and ruin references in journals etc.&lt;br /&gt;
&lt;br /&gt;
TinyURL offers a URL shortening service. They provide short URLs that redirect to long ones. This is useful if you want to write down a very long URL as it saves typing and is more accurate. Other companies, including [https://bitly.com/ bit.ly],[https://goo.gl/ Google] and Twitter offer a similar service. TinyURL was, for a while, the most popular of these URL shortening services. If their domain name were stolen, all the redirects from short URLs could be changed to forward traffic to sites hosting, for example, malware. This would have significant effects on a large number of people, because TinyURL is used in many places both online and (as the title text notes) even sometimes offline.&lt;br /&gt;
&lt;br /&gt;
Domain hijacking is relatively common {{Citation needed}}. If a cracker can obtain personal information about the domain owner, they can impersonate them to the domain registrar, and obtain control of the domain, and with that control [[792: Password Reuse|defraud a large number of people]].&lt;br /&gt;
&lt;br /&gt;
A [https://reports.internic.net/cgi/whois?whois_nic=tinyurl.com&amp;amp;type=domain whois search] as of June 2016 finds that the tinyurl.com domain is next due for renewal in June 2018.  However, [https://www.icann.org/resources/pages/expired-2013-05-03-en rule changes made by ICANN] (the organization in charge of domain name registrations) now make it effectively impossible to steal a domain name because the owner allowed its registration to lapse.  Current rules for .com registrations now allow for the original owner to renew their domain name after it expires during a 0-45 day auto-renew grace period.  The exact length of this grace period depends on what company the domain is registered with.  All registrars are then required to give a 30 day redemption grace period during which the domain may be renewed with penalty.  As a result, tinyurl.com would have a 30-75 day period after expiration during which the domain is not available for registration by a third party.  ICANN rules state that DNS resolution must be stopped during the redemption grace period, which means that there will be a 30 day period during which tinyurl.com will no longer work but the company will have the ability to quickly restore ownership of their domain.  It is very unlikely that any company that is still in business would not notice that their domain name has expired before the end of the 30 day redemption grace period.&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[A chart with an Eisenhower box, consisting of four labeled squares. To the left the rows are labeled and two lines goes to from these labels to a description of what the labels refer to. Below is a similar labeling of the columns also with two lines going from these labels to the description.]&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| rowspan=&amp;quot;2&amp;quot;|&amp;lt;p align=&amp;quot;right&amp;quot;&amp;gt;How hard&amp;lt;br /&amp;gt;thing would&amp;lt;br /&amp;gt;be to steal&amp;lt;/p&amp;gt;&lt;br /&gt;
| Hard&lt;br /&gt;
| &amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;The Crown&amp;lt;br /&amp;gt;Jewels&amp;lt;/p&amp;gt;||&amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;The nuclear&amp;lt;br /&amp;gt;launch codes&amp;lt;/p&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Easy&lt;br /&gt;
| &amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;The Oscar Mayer&amp;lt;br /&amp;gt;Wienermobile&amp;lt;/p&amp;gt;||&amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;The tinyurl.com&amp;lt;br /&amp;gt;domain name&amp;lt;/p&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; rowspan=&amp;quot;2&amp;quot;|&lt;br /&gt;
| &amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;Not that bad&amp;lt;/p&amp;gt;&lt;br /&gt;
| &amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;Very bad&amp;lt;/p&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|colspan=&amp;quot;2&amp;quot;|&amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;How bad it would be&amp;lt;br /&amp;gt;if someone stole it&amp;lt;/p&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Charts]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1698:_Theft_Quadrants&amp;diff=122411</id>
		<title>1698: Theft Quadrants</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1698:_Theft_Quadrants&amp;diff=122411"/>
				<updated>2016-06-27T12:57:30Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: /* Explanation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1698&lt;br /&gt;
| date      = June 24, 2016&lt;br /&gt;
| title     = Theft Quadrants&lt;br /&gt;
| image     = theft quadrants.png&lt;br /&gt;
| titletext = TinyURL was the most popular link shortener for long enough that it made it into a lot of printed publications. I wonder what year the domain will finally lapse and get picked up by a porn site.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|How difficult would it be to steal TinyURL, really? Is it a real problem?}}&lt;br /&gt;
&lt;br /&gt;
This is a &amp;quot;{{w|Time management#The Eisenhower Method|Eisenhower box}}&amp;quot; comparing how difficult it is to steal a specified thing with the severity of the theft.&lt;br /&gt;
&lt;br /&gt;
It is very hard to steal {{w|Gold Codes|nuclear launch codes}}. They are protected by many layers of federal security. That's a good thing, too, since if they were stolen, they could be used to start a {{w|Nuclear warfare|nuclear war}} which would be bad{{Citation needed}}.&lt;br /&gt;
&lt;br /&gt;
It is also hard to steal the {{w|Crown Jewels of the United Kingdom|Crown Jewels}}, since they are protected by a [http://yeomenoftheguard.com/Windsor%20Castle.jpg complex security system]. But if they were stolen, it wouldn't be so bad for most people.&lt;br /&gt;
&lt;br /&gt;
It wouldn't be too hard to steal the a {{w|Wienermobile}} (a car shaped like a hot-dog, advertising the Oscar Mayer brand). There have been made several versions of this car, and it would not be more difficult to steal than any other car, although harder to hide though.  [[Randall]] seems to considers that such a stolen vehicles would not be too bad, although he has previously refereed to a stolen Wienermobile in [[935: Missed Connections]], which is driven recklessly almost hitting someone. But it is not bad enough to consider it a big problem in a context where it is compared with stolen nuclear codes.&lt;br /&gt;
&lt;br /&gt;
It also wouldn't be hard (or at least, not as hard as stealing nuclear launch codes or the Crown Jewels) to steal the {{w|TinyURL|tinyurl.com}} domain name, but the consequences of that could be significant and is thus listed under very bad. The joke if of course that this is listed as just as bad as the risk of a nuclear war, and of course it is not as significant, but it could swiftly result in damage to a lot of important computers, and ruin references in journals etc.&lt;br /&gt;
&lt;br /&gt;
TinyURL offers a URL shortening service. They provide short URLs that redirect to long ones. This is useful if you want to write down a very long URL as it saves typing and is more accurate. Other companies, including [https://bitly.com/ bit.ly],[https://goo.gl/ Google] and Twitter offer a similar service. TinyURL was, for a while, the most popular of these URL shortening services. If their domain name were stolen, all the redirects from short URLs could be changed to forward traffic to sites hosting, for example, malware. This would have significant effects on a large number of people, because TinyURL is used in many places both online and (as the title text notes) even sometimes offline.&lt;br /&gt;
&lt;br /&gt;
Domain hijacking is relatively common [citation needed]. If a cracker can obtain personal information about the domain owner, they can impersonate them to the domain registrar, and obtain control of the domain, and with that control [[792: Password Reuse|defraud a large number of people]].&lt;br /&gt;
&lt;br /&gt;
A [https://reports.internic.net/cgi/whois?whois_nic=tinyurl.com&amp;amp;type=domain whois search] as of June 2016 finds that the tinyurl.com domain is next due for renewal in June 2018.  However, [https://www.icann.org/resources/pages/expired-2013-05-03-en rule changes made by ICANN] (the organization in charge of domain name registrations) now make it effectively impossible to steal a domain name because the owner allowed its registration to lapse.  Current rules for .com registrations now allow for the original owner to renew their domain name after it expires during a 0-45 day auto-renew grace period.  The exact length of this grace period depends on what company the domain is registered with.  All registrars are then required to give a 30 day redemption grace period during which the domain may be renewed with penalty.  As a result, tinyurl.com would have a 30-75 day period after expiration during which the domain is not available for registration by a third party.  ICANN rules state that DNS resolution must be stopped during the redemption grace period, which means that there will be a 30 day period during which tinyurl.com will no longer work but the company will have the ability to quickly restore ownership of their domain.  It is very unlikely that any company that is still in business would not notice that their domain name has expired before the end of the 30 day redemption grace period.&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[A chart with an Eisenhower box, consisting of four labeled squares. To the left the rows are labeled and two lines goes to from these labels to a description of what the labels refer to. Below is a similar labeling of the columns also with two lines going from these labels to the description.]&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| rowspan=&amp;quot;2&amp;quot;|&amp;lt;p align=&amp;quot;right&amp;quot;&amp;gt;How hard&amp;lt;br /&amp;gt;thing would&amp;lt;br /&amp;gt;be to steal&amp;lt;/p&amp;gt;&lt;br /&gt;
| Hard&lt;br /&gt;
| &amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;The Crown&amp;lt;br /&amp;gt;Jewels&amp;lt;/p&amp;gt;||&amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;The nuclear&amp;lt;br /&amp;gt;launch codes&amp;lt;/p&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Easy&lt;br /&gt;
| &amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;The Oscar Mayer&amp;lt;br /&amp;gt;Wienermobile&amp;lt;/p&amp;gt;||&amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;The tinyurl.com&amp;lt;br /&amp;gt;domain name&amp;lt;/p&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; rowspan=&amp;quot;2&amp;quot;|&lt;br /&gt;
| &amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;Not that bad&amp;lt;/p&amp;gt;&lt;br /&gt;
| &amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;Very bad&amp;lt;/p&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|colspan=&amp;quot;2&amp;quot;|&amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;How bad it would be&amp;lt;br /&amp;gt;if someone stole it&amp;lt;/p&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Charts]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=1698:_Theft_Quadrants&amp;diff=122410</id>
		<title>1698: Theft Quadrants</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=1698:_Theft_Quadrants&amp;diff=122410"/>
				<updated>2016-06-27T12:55:12Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: /* Explanation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{comic&lt;br /&gt;
| number    = 1698&lt;br /&gt;
| date      = June 24, 2016&lt;br /&gt;
| title     = Theft Quadrants&lt;br /&gt;
| image     = theft quadrants.png&lt;br /&gt;
| titletext = TinyURL was the most popular link shortener for long enough that it made it into a lot of printed publications. I wonder what year the domain will finally lapse and get picked up by a porn site.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==Explanation==&lt;br /&gt;
{{incomplete|How difficult would it be to steal TinyURL, really? Is it a real problem?}}&lt;br /&gt;
&lt;br /&gt;
This is a &amp;quot;{{w|Time management#The Eisenhower Method|Eisenhower box}}&amp;quot; comparing how difficult it is to steal a specified thing with the severity of the theft.&lt;br /&gt;
&lt;br /&gt;
It is very hard to steal {{w|Gold Codes|nuclear launch codes}}. They are protected by many layers of federal security. That's a good thing, too, since if they were stolen, they could be used to start a {{w|Nuclear warfare|nuclear war}} which would be bad{{Citation needed}}.&lt;br /&gt;
&lt;br /&gt;
It is also hard to steal the {{w|Crown Jewels of the United Kingdom|Crown Jewels}}, since they are protected by a [http://yeomenoftheguard.com/Windsor%20Castle.jpg complex security system]. But if they were stolen, it wouldn't be so bad for most people.&lt;br /&gt;
&lt;br /&gt;
It wouldn't be too hard to steal the a {{w|Wienermobile}} (a car shaped like a hot-dog, advertising the Oscar Mayer brand). There have been made several versions of this car, and it would not be more difficult to steal than any other car, although harder to hide though.  [[Randall]] seems to considers that such a stolen vehicles would not be too bad, although he has previously refereed to a stolen Wienermobile in [[935: Missed Connections]], which is driven recklessly almost hitting someone. But it is not bad enough to consider it a big problem in a context where it is compared with stolen nuclear codes.&lt;br /&gt;
&lt;br /&gt;
It also wouldn't be hard (or at least, not as hard as stealing nuclear launch codes or the Crown Jewels) to steal the {{w|TinyURL|tinyurl.com}} domain name, but the consequences of that could be significant and is thus listed under very bad. The joke if of course that this is listed as just as bad as the risk of a nuclear war, and of course it is not as significant, but it could swiftly result in damage to a lot of important computers, and ruin references in journals etc.&lt;br /&gt;
&lt;br /&gt;
TinyURL offers a URL shortening service. They provide short URLs that redirect to long ones. This is useful if you want to write down a very long URL as it saves typing and is more accurate. Other companies, including [https://bitly.com/ bit.ly],[https://goo.gl/ Google] and Twitter offer a similar service. TinyURL was, for a while, the most popular of these URL shortening services. If their domain name were stolen, all the redirects from short URLs could be changed to forward traffic to sites hosting, for example, malware. This would have significant effects on a large number of people, because TinyURL is used in many places both online and (as the title text notes) even sometimes offline.&lt;br /&gt;
&lt;br /&gt;
Domain hijacking is relatively common [citation needed]. If a cracker can obtain personal information about the domain owner, they can impersonate them to the domain registrar, and obtain control of the domain, and with that control [[792: Password Reuse|defraud a large number of people]].&lt;br /&gt;
&lt;br /&gt;
A [https://reports.internic.net/cgi/whois?whois_nic=tinyurl.com&amp;amp;type=domain whois search] as of June 2016 finds that the tinyurl.com domain is next due for renewal in June 2018.  However, rule changes made by [https://www.icann.org/resources/pages/expired-2013-05-03-en ICANN] (the organization in charge of domain name registrations) now make it effectively impossible to steal a domain name because the owner allowed its registration to lapse.  Current rules for .com registrations now allow for the original owner to renew their domain name after expires during a 0-45 day auto-renew grace period.  The exact length of this grace period depends on who the domain is registered with.  All registrars are required to give a 30 day redemption grace period during which the domain may be renewed with penalty.  As a result, tinyurl.com would have a 30-75 day period after expiration during which the domain is not available for registration by a third party.  ICANN rules state that DNS resolution must be stopped during the redemption grace period, which means that there will be a 30 day period during which tinyurl.com will no longer work but the company will have the ability to quickly restore ownership of their domain.&lt;br /&gt;
&lt;br /&gt;
==Transcript==&lt;br /&gt;
:[A chart with an Eisenhower box, consisting of four labeled squares. To the left the rows are labeled and two lines goes to from these labels to a description of what the labels refer to. Below is a similar labeling of the columns also with two lines going from these labels to the description.]&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
| rowspan=&amp;quot;2&amp;quot;|&amp;lt;p align=&amp;quot;right&amp;quot;&amp;gt;How hard&amp;lt;br /&amp;gt;thing would&amp;lt;br /&amp;gt;be to steal&amp;lt;/p&amp;gt;&lt;br /&gt;
| Hard&lt;br /&gt;
| &amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;The Crown&amp;lt;br /&amp;gt;Jewels&amp;lt;/p&amp;gt;||&amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;The nuclear&amp;lt;br /&amp;gt;launch codes&amp;lt;/p&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Easy&lt;br /&gt;
| &amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;The Oscar Mayer&amp;lt;br /&amp;gt;Wienermobile&amp;lt;/p&amp;gt;||&amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;The tinyurl.com&amp;lt;br /&amp;gt;domain name&amp;lt;/p&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; rowspan=&amp;quot;2&amp;quot;|&lt;br /&gt;
| &amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;Not that bad&amp;lt;/p&amp;gt;&lt;br /&gt;
| &amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;Very bad&amp;lt;/p&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|colspan=&amp;quot;2&amp;quot;|&amp;lt;p align=&amp;quot;center&amp;quot;&amp;gt;How bad it would be&amp;lt;br /&amp;gt;if someone stole it&amp;lt;/p&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{{comic discussion}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Charts]]&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:1698:_Theft_Quadrants&amp;diff=122409</id>
		<title>Talk:1698: Theft Quadrants</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:1698:_Theft_Quadrants&amp;diff=122409"/>
				<updated>2016-06-27T12:42:09Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Come to think of it, I haven't accidentally hit a porn site in years. Is Randall even referring to a real problem? Anyone remember whitehouse dot com? And for the record, kids, [http://purl.net/net/tbc/writing/xxx.htm don't do porn]. ''&amp;amp;mdash; [[User:Tbc|tbc]] ([[User talk:Tbc|talk]]) 12:27, 24 June 2016 (UTC)''&lt;br /&gt;
&lt;br /&gt;
I think the sentences &amp;quot;It is hard to steal nuclear launch codes. And a good thing too since they could be used to start a nuclear war.&amp;quot; are weird... to me on the first read it sounded like it is a good thing to steal them... [[Special:Contributions/162.158.85.63|162.158.85.63]]&lt;br /&gt;
&lt;br /&gt;
What is it with Randall and stealing wienermobiles? [http://www.xkcd.com/935/ xkcd 935] [[Special:Contributions/173.245.52.62|173.245.52.62]] 15:12, 24 June 2016 (UTC)&lt;br /&gt;
:I added it to the explanation, thanks! [[User:Elipongo|Elipongo]] ([[User talk:Elipongo|talk]]) 16:16, 24 June 2016 (UTC)&lt;br /&gt;
:There's also a wienermobile in xkcd 1110 parked to the right of the Burj. [[Special:Contributions/198.41.239.33|198.41.239.33]] 11:03, 27 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
A somewhat similar thing really happened in one of the URL shortening services in Taiwan. This case is not that the domain is stolen; the problem is that its database storing shortened URL mappings, because of some mis-operation in converting database data, is rolled back and some shortened URLs are &amp;quot;double-booked.&amp;quot; According to the announcement of the service, this affects over 234 thousand entries in the database. This leads to PTT, the largest terminal-based bulletin board system in Taiwan, bans shortened URLs from this service. --[[Special:Contributions/108.162.222.40|108.162.222.40]] 20:21, 24 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
''sites can be particularly vulnerable if they do not maintain their web site'' - what? You can have domain name without ANY web site at all. &amp;quot;lapse&amp;quot; likely refers to owners stopping paying. -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 11:09, 25 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
(Trying again... the CAPTCHA is glitching out on me.) &amp;quot;It is also hard to steal the {{w|Crown Jewels of the United Kingdom|Crown Jewels}}, since they are protected by a [http://yeomenoftheguard.com/Windsor%20Castle.jpg complex security system].&amp;quot; - The items that are the first linked items are not at the location the second link points to... [[Special:Contributions/141.101.98.131|141.101.98.131]] 16:20, 25 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
In line with the above comments: the whole section on the crown jewels and the wienermobile seem to miss the point and get hung up on very minor details. Stealing the crown jewels would make a few people fabulously rich, a few people significantly poorer (or jailed, or court-martialled, depending), but would hardly affect anyone else in real terms other than making millions of people - all around the world - very upset. Saying that ''Randall erroneously assumes'' that there would be little consequence to stealing the wienermobile is just silly: there is nothing erroneous about it since it could never have a material effect on more than a few individuals, and the possibility of someone being injured or killed during the robbery is irrelevant since it applies equally well to the nuclear or crown jewels options. [[Special:Contributions/108.162.229.44|108.162.229.44]] 16:12, 26 June 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
In regards to stealing tinyurl.com, I don't think it would actually be that easy.  In the title text Randall suggests picking up the domain name when it expires.  Because some domains were stolen that way in the past, ICANN has changed the rules for the major top-level-domains, including .com.  Now, after a domain name expires, the original register has a 45 day auto-renew grace period where they can re-register it without penalty.  If they miss that period, they have an additional 30 day grace period where it can be re-registered with a penalty.  The domain name stops working when it initially expires so it would be nearly impossible for a company like tinyurl to get to the end of both grace periods without noticing and fixing the problem.  These new rules make it effectively impossible for an organization to lose its domain name by failing to renew on a timely basis.  [https://www.icann.org/resources/pages/expired-2013-05-03-en Reference]&lt;br /&gt;
&lt;br /&gt;
Since Randall only mentioned domain expiration as the way it might be stolen, it is unclear whether or not he was considering a more direct domain name hijacking.  I'm less familiar with how easy domain hijacking might be but considering that their entire business depends on their domain name, I can't imagine it would actually be that easy.&lt;br /&gt;
&lt;br /&gt;
Regarding the current explanation (and has been pointed out already), saying that &amp;quot;sites can be particularly vulnerable if they do not maintain their web site&amp;quot; is very wrong.  This has nothing to do with maintaining a website, and only has to do with maintaining thei domain name.  The website and domain name are two very different things, so this isn't just a matter of nitpicking.  However, as I have explained above, the entire concept is no longer correct.  There is now a grace period up to 75 days long for .com domains during which registrars are not allowed to sell the domain name to another third party.&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:1638:_Backslashes&amp;diff=110560</id>
		<title>Talk:1638: Backslashes</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:1638:_Backslashes&amp;diff=110560"/>
				<updated>2016-02-03T14:08:14Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;It should be noted that this also occurs in almost every programming language where &amp;quot;\&amp;quot; is the escape character. i.e.&lt;br /&gt;
 print(&amp;quot;Hello&amp;quot;)&lt;br /&gt;
 &amp;gt; Hello&lt;br /&gt;
 print(&amp;quot;\&amp;quot;Hello\&amp;quot;&amp;quot;)&lt;br /&gt;
 &amp;gt; &amp;quot;Hello&amp;quot;&lt;br /&gt;
 print(&amp;quot;\\Hello\\&amp;quot;)&lt;br /&gt;
 &amp;gt; \Hello\&lt;br /&gt;
Oh, and by the way, isn't this the third comic to mention &amp;quot;Ba'al, the Soul Eater&amp;quot;? Maybe we should start a category. (Others are [http://www.explainxkcd.com/wiki/index.php/1246:_Pale_Blue_Dot 1246] (title text) and [http://www.explainxkcd.com/wiki/index.php/1419:_On_the_Phone 1419].)&lt;br /&gt;
[[Special:Contributions/173.245.54.29|173.245.54.29]] 06:14, 3 February 2016 (UTC)&lt;br /&gt;
:[[:Category:Ba'al|Did that]] before seeing you comment, so yes I agree. --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 09:47, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
;I don't think the regex is invalid&lt;br /&gt;
&lt;br /&gt;
According to &amp;lt;tt&amp;gt;man grep&amp;lt;/tt&amp;gt; you need to specify the &amp;lt;tt&amp;gt;-E&amp;lt;/tt&amp;gt; option to use extended regex; without it unescaped parentheses are not interpreted, so they don't need to match.&lt;br /&gt;
&lt;br /&gt;
My - very wild - guess is that it was the command he used to find the line with the most special characters, but I am not confident enough to edit the article (if someone can confirm?). {{unsigned ip|141.101.66.83}}&lt;br /&gt;
&lt;br /&gt;
If it was supposed to do that, it doesn't work. Running it on my bash history matches no lines, and I have lots of special characters in there [[Special:Contributions/197.234.242.243|197.234.242.243]] 07:12, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Explain it to me like I'm dumb. What is this comic going on about? I think the explanation needs more examples like that hello, above, because that's almost understandable. --[[Special:Contributions/198.41.238.231|198.41.238.231]] 07:47, 3 February 2016 (UTC)&lt;br /&gt;
:I agree. But I cannot help either.--[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 09:51, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
This is the third time Randall has mentioned Ba'al the Soul Eater xD [[User:International Space Station|International Space Station]] ([[User talk:International Space Station|talk]]) 08:26, 3 February 2016 (UTC)&lt;br /&gt;
:Yes, that was already mentioned a few hours before you comment, see the first comment. --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 09:51, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
After passing the regex through bash, you get &amp;lt;nowiki&amp;gt;\\[[(].*\\[\])][^)\]]*$&amp;lt;/nowiki&amp;gt; That is, the literal character \, followed by [ or (, followed by any number of any characters, followed by \, followed by ] or ), followed by any number of characters that aren't ) or ], until the end of the line. [[Special:Contributions/108.162.216.44|108.162.216.44]] 08:33, 3 February 2016 (UTC)&lt;br /&gt;
:It sounds like you know what you are talking about. Anyone who can explain it good enough for the explanation, and correct the explanation of the title text if it is wrong to say that it would not work. I have added this as the reason for incomplete. But maybe also examples are needed for people with not programming skills/knowledge. We also enjoy xkcd ;-) --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 09:51, 3 February 2016 (UTC)&lt;br /&gt;
For fun: &lt;br /&gt;
 cat ~/.bash_history | xargs -d &amp;quot;\n&amp;quot; -n 1 -I {} bash -c 'chars=&amp;quot;$(echo &amp;quot;$1&amp;quot; | grep -o &amp;quot;[a-zA-Z0-9 ]&amp;quot; | wc -l)&amp;quot;; echo &amp;quot;$(( 100 - $(( $chars * 100 / ${#1} )) )) $1&amp;quot;' _ {} | sort -nrk 1 | less&lt;br /&gt;
&lt;br /&gt;
Outputs your bash_history, ordered by relative gibberishness. This was copied by hand from desktop to mobile, might well have a few typos.--[[Special:Contributions/162.158.90.208|162.158.90.208]] 10:04, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
The problem in the comic is not with regexes per se but with situations when the entered text or expression passes through several interpreters, like bash -&amp;gt; grep/sed/awk, or program text -&amp;gt; external shell command. In such cases, you have to escape backslashes for each program in the sequence, and it gets worse if you have 'real' backslashes in the final text that you're processing with the utilities (Windows' file paths, for example). See https://en.wikipedia.org/wiki/Leaning_toothpick_syndrome.&lt;br /&gt;
Feel free to lift this to the explanation page, since I'm not good at longer and more careful explanations than this one.&lt;br /&gt;
Also, gotta notice that Feedly stripped paired backslashes in the title text (probably passed it through some 'interpreter' embedded in its scripts). [[User:Aasasd|Aasasd]] ([[User talk:Aasasd|talk]]) 10:13, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
:A funny comment about the MediaWiki software, which is even worse than this comic: &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;Nikerabbit&amp;gt; I looked the code for rlike and didn't find where it does this. Can you point me to it? &amp;lt;vvv&amp;gt; $pattern = preg_replace( '!(\\\\\\\\\\\\\\\\)*(\\\\\\\\)?/!', '$1\\/', $pattern ); &amp;lt;Nikerabbit&amp;gt; I thought that was ascii art :)&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; ([https://phabricator.wikimedia.org/P110$275 source]) --[[Special:Contributions/162.158.91.215|162.158.91.215]] 10:18, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Interestingly, I first looked at this on my phone (using &amp;lt;strike&amp;gt;Chrome&amp;lt;/strike&amp;gt; Feedly for Android), but the title text did not display correctly in that the backslashes didn't appear (which was a little confusing!). In Chrome on my Windows desktop, the title text appeared correctly. [[User:Jdluk|Jdluk]] ([[User talk:Jdluk|talk]]) 11:36, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
enough with the harry potter fancruft. &amp;quot;elder&amp;quot; is a [[Wiktionary:elder|perfectly good word]]. just because you came across it for the first time in harry potter means you are *typing carefully* the kind of person that likes harry potter. unless this is a ''harry potter reference'' wiki, of course. in which case i'll prepare a complete list of every word that appears both here and there and put a list on every page. oh, right, no i won't. --[[Special:Contributions/141.101.106.161|141.101.106.161]] 12:41, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Remember that &amp;quot;Elder&amp;quot; is used in a lot of RPGs to denote high level enemies or items. I feel like that's what Randall's referring to here, more than Harry Potter or the general sense of the term &amp;quot;Elder.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Attempting to add to the discussion: This regex is not necessarily invalid or incomprehensible.  It looks like he was looking for a line with a regular expression or definitely some code.  You just have to work your way through the backslashes.  Although it might be invalid depending on the precise rules.  He has some unescaped closing brackets and closing parenthesis.  If these have to always be escaped then the regex is invalid.  If however you  don't have to escape a closing bracket with no opening bracket, then things are fine.  I'm not familiar enough with grep's regex parser to know how it handles that edge case.  Presuming those unescaped paren and brackets are fine, his regex searches for:&lt;br /&gt;
&lt;br /&gt;
1. A backslash&lt;br /&gt;
&lt;br /&gt;
2. An opening bracket&lt;br /&gt;
&lt;br /&gt;
3. An opening parenthesis (this is a character set but the only character in it is an opening paren)&lt;br /&gt;
&lt;br /&gt;
4. Any number of any characters&lt;br /&gt;
&lt;br /&gt;
5. A backslash&lt;br /&gt;
&lt;br /&gt;
6. An opening bracket&lt;br /&gt;
&lt;br /&gt;
7. A closing bracket&lt;br /&gt;
&lt;br /&gt;
8. A closing paren (presuming it doesn't have to be escaped when there is no opening paren)&lt;br /&gt;
&lt;br /&gt;
9. A closing bracket (presuming it doesn't have to be escaped when there is no opening bracket)&lt;br /&gt;
&lt;br /&gt;
10. Any number of character that are not a closing paren or closing bracket&lt;br /&gt;
&lt;br /&gt;
11. The end of the line&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Basically he is looking for a string that looks like:&lt;br /&gt;
&lt;br /&gt;
\[(AAAAA\[])]AAAAA&lt;br /&gt;
&lt;br /&gt;
Looks like a regex to me, and it looks like this regex also doesn't escape closing paren/brackets that don't have an opening paren/bracket, so I'm guessing that he knows what he is doing and his regex is fine.  Maybe he was playing regex golf?&lt;br /&gt;
[[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]])cmancone&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	<entry>
		<id>https://www.explainxkcd.com/wiki/index.php?title=Talk:1638:_Backslashes&amp;diff=110559</id>
		<title>Talk:1638: Backslashes</title>
		<link rel="alternate" type="text/html" href="https://www.explainxkcd.com/wiki/index.php?title=Talk:1638:_Backslashes&amp;diff=110559"/>
				<updated>2016-02-03T14:06:25Z</updated>
		
		<summary type="html">&lt;p&gt;Cmancone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;It should be noted that this also occurs in almost every programming language where &amp;quot;\&amp;quot; is the escape character. i.e.&lt;br /&gt;
 print(&amp;quot;Hello&amp;quot;)&lt;br /&gt;
 &amp;gt; Hello&lt;br /&gt;
 print(&amp;quot;\&amp;quot;Hello\&amp;quot;&amp;quot;)&lt;br /&gt;
 &amp;gt; &amp;quot;Hello&amp;quot;&lt;br /&gt;
 print(&amp;quot;\\Hello\\&amp;quot;)&lt;br /&gt;
 &amp;gt; \Hello\&lt;br /&gt;
Oh, and by the way, isn't this the third comic to mention &amp;quot;Ba'al, the Soul Eater&amp;quot;? Maybe we should start a category. (Others are [http://www.explainxkcd.com/wiki/index.php/1246:_Pale_Blue_Dot 1246] (title text) and [http://www.explainxkcd.com/wiki/index.php/1419:_On_the_Phone 1419].)&lt;br /&gt;
[[Special:Contributions/173.245.54.29|173.245.54.29]] 06:14, 3 February 2016 (UTC)&lt;br /&gt;
:[[:Category:Ba'al|Did that]] before seeing you comment, so yes I agree. --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 09:47, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
;I don't think the regex is invalid&lt;br /&gt;
&lt;br /&gt;
According to &amp;lt;tt&amp;gt;man grep&amp;lt;/tt&amp;gt; you need to specify the &amp;lt;tt&amp;gt;-E&amp;lt;/tt&amp;gt; option to use extended regex; without it unescaped parentheses are not interpreted, so they don't need to match.&lt;br /&gt;
&lt;br /&gt;
My - very wild - guess is that it was the command he used to find the line with the most special characters, but I am not confident enough to edit the article (if someone can confirm?). {{unsigned ip|141.101.66.83}}&lt;br /&gt;
&lt;br /&gt;
If it was supposed to do that, it doesn't work. Running it on my bash history matches no lines, and I have lots of special characters in there [[Special:Contributions/197.234.242.243|197.234.242.243]] 07:12, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Explain it to me like I'm dumb. What is this comic going on about? I think the explanation needs more examples like that hello, above, because that's almost understandable. --[[Special:Contributions/198.41.238.231|198.41.238.231]] 07:47, 3 February 2016 (UTC)&lt;br /&gt;
:I agree. But I cannot help either.--[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 09:51, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
This is the third time Randall has mentioned Ba'al the Soul Eater xD [[User:International Space Station|International Space Station]] ([[User talk:International Space Station|talk]]) 08:26, 3 February 2016 (UTC)&lt;br /&gt;
:Yes, that was already mentioned a few hours before you comment, see the first comment. --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 09:51, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
After passing the regex through bash, you get &amp;lt;nowiki&amp;gt;\\[[(].*\\[\])][^)\]]*$&amp;lt;/nowiki&amp;gt; That is, the literal character \, followed by [ or (, followed by any number of any characters, followed by \, followed by ] or ), followed by any number of characters that aren't ) or ], until the end of the line. [[Special:Contributions/108.162.216.44|108.162.216.44]] 08:33, 3 February 2016 (UTC)&lt;br /&gt;
:It sounds like you know what you are talking about. Anyone who can explain it good enough for the explanation, and correct the explanation of the title text if it is wrong to say that it would not work. I have added this as the reason for incomplete. But maybe also examples are needed for people with not programming skills/knowledge. We also enjoy xkcd ;-) --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 09:51, 3 February 2016 (UTC)&lt;br /&gt;
For fun: &lt;br /&gt;
 cat ~/.bash_history | xargs -d &amp;quot;\n&amp;quot; -n 1 -I {} bash -c 'chars=&amp;quot;$(echo &amp;quot;$1&amp;quot; | grep -o &amp;quot;[a-zA-Z0-9 ]&amp;quot; | wc -l)&amp;quot;; echo &amp;quot;$(( 100 - $(( $chars * 100 / ${#1} )) )) $1&amp;quot;' _ {} | sort -nrk 1 | less&lt;br /&gt;
&lt;br /&gt;
Outputs your bash_history, ordered by relative gibberishness. This was copied by hand from desktop to mobile, might well have a few typos.--[[Special:Contributions/162.158.90.208|162.158.90.208]] 10:04, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
The problem in the comic is not with regexes per se but with situations when the entered text or expression passes through several interpreters, like bash -&amp;gt; grep/sed/awk, or program text -&amp;gt; external shell command. In such cases, you have to escape backslashes for each program in the sequence, and it gets worse if you have 'real' backslashes in the final text that you're processing with the utilities (Windows' file paths, for example). See https://en.wikipedia.org/wiki/Leaning_toothpick_syndrome.&lt;br /&gt;
Feel free to lift this to the explanation page, since I'm not good at longer and more careful explanations than this one.&lt;br /&gt;
Also, gotta notice that Feedly stripped paired backslashes in the title text (probably passed it through some 'interpreter' embedded in its scripts). [[User:Aasasd|Aasasd]] ([[User talk:Aasasd|talk]]) 10:13, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
:A funny comment about the MediaWiki software, which is even worse than this comic: &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;Nikerabbit&amp;gt; I looked the code for rlike and didn't find where it does this. Can you point me to it? &amp;lt;vvv&amp;gt; $pattern = preg_replace( '!(\\\\\\\\\\\\\\\\)*(\\\\\\\\)?/!', '$1\\/', $pattern ); &amp;lt;Nikerabbit&amp;gt; I thought that was ascii art :)&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; ([https://phabricator.wikimedia.org/P110$275 source]) --[[Special:Contributions/162.158.91.215|162.158.91.215]] 10:18, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Interestingly, I first looked at this on my phone (using &amp;lt;strike&amp;gt;Chrome&amp;lt;/strike&amp;gt; Feedly for Android), but the title text did not display correctly in that the backslashes didn't appear (which was a little confusing!). In Chrome on my Windows desktop, the title text appeared correctly. [[User:Jdluk|Jdluk]] ([[User talk:Jdluk|talk]]) 11:36, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
enough with the harry potter fancruft. &amp;quot;elder&amp;quot; is a [[Wiktionary:elder|perfectly good word]]. just because you came across it for the first time in harry potter means you are *typing carefully* the kind of person that likes harry potter. unless this is a ''harry potter reference'' wiki, of course. in which case i'll prepare a complete list of every word that appears both here and there and put a list on every page. oh, right, no i won't. --[[Special:Contributions/141.101.106.161|141.101.106.161]] 12:41, 3 February 2016 (UTC)&lt;br /&gt;
&lt;br /&gt;
Remember that &amp;quot;Elder&amp;quot; is used in a lot of RPGs to denote high level enemies or items. I feel like that's what Randall's referring to here, more than Harry Potter or the general sense of the term &amp;quot;Elder.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Attempting to add to the discussion: This regex is not necessarily invalid or incomprehensible.  It looks like he was looking for a line with a regular expression or definitely some code.  You just have to work your way through the backslashes.  Although it might be invalid depending on the precise rules.  He has some unescaped closing brackets and closing parenthesis.  If these have to always be escaped then the regex is invalid.  If however you  don't have to escape a closing bracket with no opening bracket, then things are fine.  I'm not familiar enough with grep's regex parser to know how it handles that edge case.  Presuming those unescaped paren and brackets are fine, his regex searches for:&lt;br /&gt;
&lt;br /&gt;
1. A backslash&lt;br /&gt;
2. An opening bracket&lt;br /&gt;
3. An opening parenthesis (this is a character set but the only character in it is an opening paren)&lt;br /&gt;
4. Any number of any characters&lt;br /&gt;
5. A backslash&lt;br /&gt;
6. An opening bracket&lt;br /&gt;
7. A closing bracket&lt;br /&gt;
8. A closing paren (presuming it doesn't have to be escaped when there is no opening paren)&lt;br /&gt;
9. A closing bracket (presuming it doesn't have to be escaped when there is no opening bracket)&lt;br /&gt;
10. Any number of character that are not a closing paren or closing bracket&lt;br /&gt;
11. The end of the line&lt;br /&gt;
&lt;br /&gt;
Basically he is looking for a string that looks like:&lt;br /&gt;
&lt;br /&gt;
\[(AAAAA\[])]AAAAA&lt;br /&gt;
&lt;br /&gt;
Looks like a regex to me, and it looks like this regex also doesn't escape closing paren/brackets that don't have an opening paren/bracket, so I'm guessing that he knows what he is doing and his regex is fine.  Maybe he was playing regex golf?&lt;br /&gt;
[[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]])cmancone&lt;/div&gt;</summary>
		<author><name>Cmancone</name></author>	</entry>

	</feed>