explain xkcd - User contributions [en]

2168: Reading in the Original

2026-03-19T05:41:07Z

Graham87: /* Explanation */ copyedit

{{comic
| number = 2168
| date = June 26, 2019
| title = Reading in the Original
| image = reading_in_the_original.png
| titletext = The articles are much shorter, but I assume that's because this version predates the merger with the Hawaiian text that created the modern Hawaiian-Greek hybrid wiki-pedia.
}}

==Explanation==
Many academics and aficionados argue that studying texts in the original language is more valuable than reading translations. The argument is that translations are rarely able to fully capture all of the nuances, linguistic subtleties and intent of the original author, and may even alter the meaning in some way due to the translator's interpretation and word choices. The drawback to this is that it requires the reader to be sufficiently fluent in whatever language the text is written in. Critically, a reader of the original source also needs to understand the cultural and historical context of the original work, something a professional translator might deal with much better. This can even happen when working with archaic texts in the same language, as certain references and phrases may have had a significance which was lost over time.

Cueball's commenting that he read works "in the original Greek" implies a high-level of literary scholarship, as this phrase is associated with scholars studying ancient Greek texts, which form a significant part of the foundational works of Western literature.

A similar thing happens with dubbed movies or TV series/anime, with many people remarking that they instead prefer to watch the original version (sometimes with subtitles), instead of the dubbed version.

The joke in this comic is that Cueball has apparently taken the time to learn Greek in order to read the [https://el.wikipedia.org Greek-language Wikipedia] in that language, believing it to be the "original" one. {{w|Wikipedia}} was originally launched as a single English-language edition encyclopedia, but Cueball apparently treats it as though it was originally written in Greek. (An [https://incubator.wikimedia.org/wiki/Wp/grc Ancient Greek Wikipedia test project] also exists, but is not nearly as large as the modern Greek one and isn't available through the languages box.) Wikipedia has editions in about 300 languages; the 'languages' box that Cueball mentions does link to the corresponding page in other languages when they are available, but such pages are not usually translations of each other, having been written separately. (The 'languages' box was indeed placed in the lower left of the page at the time the comic was published, but moved to the upper right in January 2023, when a [https://slate.com/technology/2023/01/wikipedia-redesign-vector-2022-skin.html new default Skin] was deployed.) Cueball's dedication to appearing to be a committed scholar is therefore contrasted with the ignorance of not understanding that Greek is not the original language of every text. Megan, recognizing that Wikipedia articles were not originally in Greek, exclaims that "That's not how that works!"

The movie ''{{w|Star Trek VI: The Undiscovered Country}}'' has a joke concerning someone speaking of a foreign "original" language of something that actually was originally written in English: Chancellor Gorkon says, "You have not experienced Shakespeare until you've read it in the [[wikia:w:c:klingon:Shakespeare|original Klingon]]." (In context it's heavily implied Gorkon is speaking in jest, and he is well aware Shakespeare was a human who wrote in English, not {{w|Klingon language|Klingon}}.){{Citation needed}}

The title text combines two jokes. First, the reference to pages being "much shorter" is because the English language Wikipedia has the most editors and is the most developed; outside of areas of intense interest to Greeks, most pages would be more complete on the English Wikipedia, which would normally be a sign to Cueball that his interpretation that Greek was the original text is incorrect. Second, the way he explains away this contradiction is an etymology joke, since "Wikipedia" was coined from two parts, "[[wikt:wiki#English|wiki]]", from Hawaiian, and "[[wikt:-pedia|pedia]]", from Greek. However, words having roots in different languages is common and does not signify any link between the separate languages; for example, while the word "Wikipedia" does have etymological roots in Hawaiian and Greek, it is not true that the site was originally composed of texts written in Hawaiian and Greek. In Hawaiian, [[wikt:wiki#Hawaiian|wiki]] means quick. In Greek, the suffix [[wikt:-pedia|pedia]] is related to learning, which makes Wikipedia mean "quick learning" when combining these two languages.

==Transcript==
:[Cueball is addressing Megan. He is holding a hand with a thumb up out toward her. Megan is spreading her arms out as she replies.]
:Cueball: It's in the "Languages" box in the lower left. It took a while to learn, but I find I get so much more out of it by reading it as it was '''''intended'''''.
:Megan: That's not how that works!

:[Caption below the panel:]
:People get mad when I tell them I only read Wikipedia in the original Greek.

{{comic discussion}}

[[Category:Comics featuring Cueball]]
[[Category:Comics featuring Megan]]
[[Category:Language]]
[[Category:Wikipedia]]

2170: Coordinate Precision

2026-03-19T05:31:16Z

Graham87: /* Explanation */ copyedit

{{comic
| number = 2170
| date = July 1, 2019
| title = Coordinate Precision
| image = coordinate_precision.png
| titletext = 40 digits: You are optimistic about our understanding of the nature of distance itself.
}}

==Explanation==

This cartoon gives increasingly precise latitude and longitude coordinates for a location on the planet Earth. However, a given pair of coordinates covers a trapezoidal region of land, and thus leaves some ambiguity; therefore, greater precision requires an increasing count of decimal places in your coordinates. This comic uses this information to roughly identify how precise a given coordinate length might be.

The increasing precision of coordinates in this cartoon is similar to the increasing magnification in the short documentary {{w|Powers of Ten (film)|"Powers of 10,"}} which can be found [http://www.youtube.com/watch?v=0fKBhvDjuy0 here]. (Also parodied in [[271: Powers of One]]).

The coordinates at [https://tools.wmflabs.org/geohack/geohack.php?pagename=Cape_Canaveral&params=28.52345_N_80.68309_W_type:landmark_region:US-FL_scale:10000 28.52345°N, 80.68309°W] (in {{w|decimal degrees}} form; in {{w|geographic coordinate system}} form using degrees, minutes, and seconds, 28° 31′ 24.4″N, 80° 40′ 59.1″W) are pointing to the {{w|Rocket Garden}} at the {{w|Kennedy Space Center}} in {{w|Merritt Island, Florida}} —specifically, the tip of the [https://www.kennedyspacecenter.com/-/media/DNC/KSCVC/Blog-Images/Rocket-Garden/rocket-garden-with-labels.ashx?h=860&w=1173&la=en&hash=7B9ADC7AFF5370E462AC98D9651945B806B77B2C Delta] rocket.

The sixth entry in the table, with seven digits of precision, includes the caveat that, while your coordinates map to areas small enough on the Earth's surface to indicate pointing to a specific person in a room, "since you didn't include datum information, we can't tell who". This is a reference to the ''{{w|geodetic datum}}'' or ''geodetic system'' — different ways of dealing with the fact that the Earth is neither perfectly spherical nor perfectly an oblate ellipsoid. The various datums do not make much difference at six digits of precision, but at seven, there is enough skew depending on which system is in use that the person in a room you are referring to with the coordinates is ambiguous. It is unstated, but the remaining lines in the table with ever-greater precision suffer from this same issue and are equally ambiguous without datum information.

The final entry, with seventeen digits of precision, suggests that either the user is referring to individual atoms in the much-larger-scale whole-Earth coordinate system, or (perhaps more likely) has not bothered to format the values from the GPS module for viewing in the software UI in any way whatsoever, resulting in a value that is {{w|False precision|meaninglessly precise}} because the measurement wasn't that {{w|Accuracy and precision|accurate}} to begin with. See [[2696: Precision vs Accuracy]]. Even if the value is accurate, locating individual atoms by coordinates is not actually useful in most cases, and the motions of multiple systems within our physical world (continental drift, subtle vibrations, {{w|Brownian motion}}, etc.) would render the precise value obsolete rather quickly.

For the decimal places past the 5th on the latitude, the digits given are actually the first part of the decimal expansion of the constant ''e'' (2.7182818284), while for the decimal places past the 5th on the longitude, the digits given are part of the decimal expansion of the constant ''π'' (3.14159265358) starting with the second digit (4).

The title text references how at sufficiently small distances, our understanding of reality itself begins to break down. Smaller than the {{w|Planck length}}, which is more than a quintillion times smaller than the diameter of a proton, the ideals of Euclidean geometry no longer apply and space itself may be composed of a {{w|quantum foam}} where the very geometry of spacetime itself fluctuates, meaning coordinate systems based on an assumption that space doesn't change would no longer work. String theory, on the other hand, assumes that at a short enough distance the world is composed of ten space dimensions, which precludes the use of a two-dimensional coordinate system (not that our “normal” three dimensions don't do so in themselves).

The actual number of longitude digits needed to identify a point to a particular precision depends on its latitude. Near the poles, you need fewer longitude digits than at the equator – starting with one digit fewer at around lat. 85°, past all constantly inhabited human settlements, and with two digits fewer at lat. 89.5°, inaccessible to anyone but polar researchers and the occasional guided tour. The number of latitude digits for some particular accuracy stays essentially the same everywhere.

==Chart==

{| class="wikitable"
|-
! Decimal places
! Resolution*
! In the comic
! Location
! Explanation/notes
|-
| 0
| 110 km (70 mi)
| Something space-related
| Somewhere near the east coast of Florida
| This resolution is enough to point out a large-scale feature like a country, a mountain range, a large lake, or a significant island on a map of the world. It can also be used to tell if certain celestial phenomena are visible from a given location.
|-
| 1
| 11 km (7 mi)
| A specific city
| Cape Canaveral
| Cities typically span a couple kilometers/miles in diameter and are far enough from each other to distinguish them at this resolution. There are exceptions though, and the veracity of this statement depends greatly on the definition of a “city”, which varies by location and history.
|-
| 2
| 1.1 km (¾ mi)
| A neighborhood
| Kennedy Space Center Visitor Complex
|
|-
| 3
| 110 m (360 ft)
| A suburban cul-de-sac
| The Rocket Garden at the Kennedy Space Center
|
|-
| 4
| 11 m (36 ft)
| A particular corner of a house
| Somewhere near the center of the Rocket Garden
|
|-
| 5
| 1.1 m (3½ ft)
| A specific person in a room (given geodetic datum information)
| The [https://www.kennedyspacecenter.com/-/media/DNC/KSCVC/Blog-Images/Rocket-Garden/rocket-garden-with-labels.ashx?h=860&w=1173&la=en&hash=7B9ADC7AFF5370E462AC98D9651945B806B77B2C Thor-Delta] rocket in Rocket Garden
| As the comic notes, the differences between {{w|geodetic datum}}s – different ways to map geodetic coordinates to specific points on the Earth's surface – become large enough that one needs to specify the one in use when supplying coordinates to this degree of precision (or greater, of course). Since the Earth is not a perfect ellipsoid, different parts of the planet conform best to ellipsoids of slightly different proportions, resulting in different coordinates for a specific location; not to mention that locally used datums have local reference points, which means that the local and global standards are slowly drifting away from each other with the tectonical plates.
Note that the comment in the comic concerns only the {{w|North American Datum|NAD 1983}} datum which is fairly close to the international, “one size fits all” standard {{w|WGS-84}}. Other datums may be shifted by tens or even hundreds of meters (yards), making geodetic datum specification necessary for less precise coordinates as well.
|-
| 7
| 1.1 cm (⁷⁄₁₆ in)
| Waldo on a page
| Presumably the very tip of the rocket
| This refers to ''{{w|Where's Wally?|Where's Waldo?}}'', a series of books and magazines containing various scenes (densely packed with people) where one must find Waldo, a character wearing a red and white striped shirt. In the puzzles, he usually stands less than 2 cm (1 in) tall.
Finding Waldo on a page using satellites was also referenced in [[1358:_NRO|#1358]].
|-
| 9
| 0.11 mm (4⅜ thou)
| A specific grain of sand
| rowspan=3 | N/A
|
|-
| 15
| 110 pm (1.1 Å)
| Raw floating point precision or an individual atom
| A double-precision (64-bit) floating point variable stores 52 significant bits (with an implicit 1 in front), so that 180.00000000000000 and 179.99999999999997 may be represented as distinct values. (This is only 14 decimals, however; the larger the integral part, the fewer bits remain to represent the fractional part.) This level of precision is useful for mitigating rounding errors in computations, but this advantage only shows if the last few digits are treated as non-significant and thus, ideally, hidden from view. To work with data that is actually this precise – like tracking individual atoms or representing continental drift up to the second –, one must make allowance for these additional non-significant digits and store the coordinates in ''quadruple'' precision.
To track atoms, however, one needs very sensitive (and expensive) equipment with a severely limited range (according to our current understanding of science and technology). Using a global-scale coordinate system when a micrometer-scale would fit much better is either an abuse of the system and a great waste of memory and computing power, or it means that a significant portion of the Earth's surface has been blanketed by quantum microscopes, which would be an abuse and a waste of many other things as well.{{Citation needed}}
|-
| 40
| 1.1 × 10–11 ym (1.1 × 10–35 m)
| Near (or past) our current understanding of the nature of distance
| This is where the resolution reaches the Planck length (1.6 × 10–35 m). At this scale, the very structure of spacetime (and thus, the notion of distance) may be different than what we know; measuring anything to Planck length precision would necessitate such tremendous amounts of energy in one place that would create minuscule black holes, warping spacetime further (in addition to wreaking havoc with whatever you were trying to pinpoint).
|}
<nowiki>*</nowiki>Since the Earth is not exactly spherical, the actual length of one degree of latitude varies between 110.574 km (68.707 mi) at the equator and 111.694 km (69.403 mi) at the poles, while one degree of longitude is 111.320 km (69.171 mi) at the equator, 55.800 km (34.673 mi) at lat. 60°, and 0 km (0 mi) at the poles.

==Transcript==
:[Single panel containing a table with two columns for "Lat/Lon Precision" and "Meaning" and a caption above the table.]
:Caption: What The Number of Digits in Your Coordinates Means

:[Row 1]
:Lat/Lon: 28°N, 80°W
:Meaning: You're probably doing something space-related

:[Row 2]
:Lat/Lon: 28.5°N, 80.6°W
:Meaning: You're pointing out a specific city

:[Row 3]
:Lat/Lon: 28.52°N, 80.68°W
:Meaning: You're pointing out a neighborhood

:[Row 4]
:Lat/Lon: 28.523°N, 80.683°W
:Meaning: You're pointing out a specific suburban cul-de-sac

:[Row 5]
:Lat/Lon: 28.5234°N, 80.6830°W
:Meaning: You're pointing to a particular corner of a house

:[Row 6]
:Lat/Lon: 28.52345°N, 80.68309°W
:Meaning: You're pointing to a specific person in a room, but since you didn't include datum information, we can't tell who

:[Row 7]
:Lat/Lon: 28.5234571°N, 80.6830941°W
:Meaning: You're pointing to Waldo on a page

:[Row 8]
:Lat/Lon: 28.523457182°N, 80.683094159°W
:Meaning: "Hey, check out this specific sand grain!"

:[Row 9]
:Lat/Lon: 28.523457182818284°N, 80.683094159265358°W
:Meaning: Either you're handing out raw floating point variables, or you've built a database to track individual atoms. In either case, please stop.

{{comic discussion}}

[[Category:Space]]
[[Category:Geography]]
[[Category:Programming]]

927: Standards

2025-10-17T07:06:42Z

Graham87: spelling

{{comic
| number = 927
| date = July 20, 2011
| title = Standards
| image = standards.png
| titletext = Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shit.
}}

==Explanation==
For any engineering task, there are numerous ways a given problem can be solved. The more complex the task, the more room for diversity. That's all well and good for a one-off problem, but if a design is meant to be iterated over time, or if an entire industry is solving that same problem, part reuse and {{w|interoperability}} become issues to deal with. {{w|Technical standards}} thus came to exist so that industries could avoid wasting resources {{w|reinventing the wheel}}, whilst offering their clients a certain amount of simplicity and compatibility between vendors.

But standards have issues of their own. They don't accommodate every {{w|Use Case|use case}}, they might have restrictions or royalties attached, and people tend to be plagued by ''{{w|Not invented here|Not Invented Here syndrome}}''. So competing standards have a tendency to arise to address different perceived needs. After a while, the market for competing standards gets messy and hard to follow, and {{w|system integration|integrating systems}} built around competing standards gets burdensome. As a result, someone eventually takes on the challenge of creating a universal standard that everyone can rally around.

This almost never works. In many cases, a new standard fails to displace the incumbent standards, eventually loses funding and support, and thus becomes a relic of history. In many other cases, it only penetrates far enough to survive, ironically making the situation messier. The latter situation often ends up becoming cyclical, with new standards periodically rising and failing to gain traction.

Three examples are given at the top of the comic: {{w|AC adapter|AC chargers}}, {{w|character encoding}} and {{w|instant messaging}}.
* Power adapters are notorious for varying from device to device - partly to try to prevent dangerous voltage/current mismatches, but partly just because manufacturers all chose different adapter designs. In 2011, Mobile phone chargers had mostly converged on a common USB-based solution, but laptop charging remained still a long way out, despite the adoption of yet another standard, {{w|IEC 62700}}, and Apple mobile devices generally used proprietary Lightning connectors (However that is changing because of European law). Randall notes that there was additional complexity due to the fact that there were also ''competing USB types''; thanks to the European Union's {{w|common external power supply}} specification, micro-USB then won the day. In August 2014, the {{w|USB Type-C}} specification was published and started to displace micro-USB; it gained ground among laptop manufacturers as well. From 2021 to 2022, the EU successfully legislated for its {{w|USB-C#Regulations for compatibility|common use}}.
* Character encoding is, in theory, a solved problem - {{w|Unicode}} is a standard for character sets which currently includes over 135,000 characters. However, Unicode is not an encoding, just an abstract representation of the characters, and there are several implementations which encode Unicode "code points" into usable characters (including the two most common, {{w|UTF-8}} and {{w|UTF-16}}). Despite the [https://w3techs.com/technologies/history_overview/character_encoding/ms/y success of UTF-8 Unicode], older encodings like {{w|Windows-1252}} have stuck around, continuing to cause weird bugs in old software and websites to this day.
* Unlike the other examples, there has been little or no effort by instant messaging companies to make their services interoperable. There's more value to keeping IM as a {{w|closed platform}} so users are forced to use the company's software to access it. Some software, like the {{w|Trillian (software)|Trillian}} chat client, can connect to multiple different services, but there is essentially no way to, for example, send a Twitter message directly to a Skype user. ActivityPub is an example of a standard intended to be universal, so any software using it for instant messaging can be 'federated' with each other, but as the comic points out, all this has led to is yet another competing standard.

The title text mentions mini-USB and micro-USB, which were different standards used in 2011. As of 2019 for most applications of small USB ports (especially for charging / connecting cell phones), mini USB has lost most of its relevance and micro USB is competing with USB-C, as well as some solutions only used by single companies (such as Apple). As of 2023, Apple has also switched entirely to USB-C after pressures from the European Union.

Not all {{w|technical standards|standards}} are created equal. In the development of {{w|technical standards|standards}}, private standards adopt a non-consensus process in comparison to voluntary consensus standards. Private standards in the {{w|Information and Communications Technology}} (ICT) sector and the agri-food industry (governed by the {{w|Global Food Safety Initiative}}) are discussed in a [https://docplayer.net/23885374-International-standards-and-private-standards.html publication from International Organization for Standardization.]

==Transcript==
:[Caption above the panels:]
:How Standards Proliferate
:(See: A/C chargers, character encodings, instant messaging, etc.)

:[A text-only panel.]
:Situation:
:There are 14 competing standards.

:[Cueball and Ponytail stand facing each other.]
:Cueball: 14?! Ridiculous! We need to develop one universal standard that covers everyone's use cases.
:Ponytail: Yeah!

:[Another text-only panel. The word "Soon:" appears in its own box at the upper left of the panel.]
:Soon:
:Situation:
:There are 15 competing standards.

{{comic discussion}}

[[Category:Comics featuring Cueball]]
[[Category:Comics featuring Ponytail]]

explain xkcd:Autoconfirmed users

2025-10-17T07:06:04Z

Graham87: copyedit

{{explainxkcdmeta}}
'''Autoconfirmed''' users are accounts which are (A) more than a week old and (B) which have at least fifty edits. Once a user satisfies these two criteria, they are automatically promoted to the autoconfirmed group, and gain the ability to upload images and files, move pages etc.

A full list of tasks autoconfirmed users can perform can be found at [[Special:ListGroupRights#Autoconfirmed users]].

The list of all current autoconfirmed users can be found at [[Special:ListUsers/autoconfirmed]].

[[Category:User rights]]

810: Constructive

2025-05-25T06:26:58Z

Graham87: copyedit, convert external to internal link

{{comic
| number = 810
| date = October 25, 2010
| title = Constructive
| image = constructive.png
| titletext = And what about all the people who won't be able to join the community because they're terrible at making helpful and constructive co-- ...oh.
}}

==Explanation==
Most online communities (including [[explain xkcd]]) face the problem of dissuading {{w|Spamming|spammers}} from joining and participating. A common solution to this problem is the use of various systems to prevent automated bots' use of the community, while still allowing legitimate users to join. This has resulted in an arms race of sorts between spammers and communities, in which the spammers try to bypass increasingly difficult spam-prevention methods. This CAPTCHA and spamming prevention also has a downside, in that the time it takes to "prove you're human" is sometimes so long as to drive users away because their time is being wasted.

This comic explores the culmination of that arms race, in which an advanced spam-prevention system, built by Cueball, is able to defeat the concept of spamming itself by forcing spammers to contribute constructively to a community. {{w|CAPTCHA}}s are one of the methods used to prevent lots of automated registering of fake usernames used by bots and spammers. It consists of asking a person to prove that they are human before registering them as a user and allowing them to post on sites or forum topics. That is done by using pictures of words and letters that humans may recognize, but bots and OCR software have trouble with.

Now the artificial intelligence (AI) of bots has advanced so far that [[Cueball]] has invented a new system. It asks the users to rate a slate of comments as constructive or not, then asks them to reply with comments of their own. [[Megan]] asks what will happen when spammers find a way around his system, such as making bots that make constructive and helpful comments? Well, it turns out that is what he is trying to accomplish in the first place: a thriving community of bots and humans helping their members with constructive and helpful comments<s>, as well as coming one step closer to the {{w|technological singularity|singularity}}</s>. There is, however, one potential workaround to Cueball's system that defeats the whole point of having the conversation be constructive if spammer bots are numerous enough. Spammers may choose to mark unhelpful comments as helpful (something that can be done purely by analyzing the comment itself), thus making it an uphill battle for constructive comments to be seen as such, making this a potentially worse solution than simply letting the spammers in.

The title text investigates the consequences of such a system further by thinking of people unable to give constructive and helpful comments, which are a sort of person you don't want in your online community anyway. Or it could mean that to join said community, they would have to learn to post helpful and constructive comments, and would then be eligible to join, thus accomplishing Cueball's goal.

CAPTCHAs are a [[:Category:CAPTCHA|recurring theme]] on xkcd.

==Transcript==
:[Cueball is talking to Megan.]
:Cueball: Spammers are breaking traditional CAPTCHAs with AI, so I've built a new system. It asks users to rate a slate of comments as "Constructive" or "Not constructive."

:[Close up of Cueball.]
:Cueball: Then it has them reply with comments of their own, which are later rated by other users.

:[Megan standing next to Cueball again.]
:Megan: But what will you do when spammers train their bots to make automated constructive and helpful comments?

:[Close up of Cueball again.]
:Cueball: ''Mission''. ''Fucking''. ''Accomplished''.

{{comic discussion}}
[[Category:Comics featuring Cueball]]
[[Category:Comics featuring Megan]]
[[Category:CAPTCHA]]

526: Converting to Metric

2023-07-19T09:16:12Z

Graham87: /* Volume */ copyedit

{{comic
| number = 526
| date = January 5, 2009
| title = Converting to Metric
| image = converting to metric.png
| titletext = According to River, "adequate" vacuuming systems drain the human body at about half a liter per second.
}}
==Explanation==
Most people will eventually develop an intuitive feel for how big certain measurements are (e.g., how long an inch or a foot is, how much a pound weighs). This comic points out that people who were brought up using the {{w|United States customary units|United States system of customary units}} probably don't have the same intuitive understanding for metric units and attempts to provide some benchmarks for these people. Most of the benchmarks are common sense, highly-useful ones (e.g., if it's 30 degrees Celsius, you'd be quite comfortable outside dressed for the beach) but some of the benchmarks are humorous and/or completely useless as can be seen below.

Some people argue for switching to metric units in the US, and these people became part of the comic [[1982: Evangelism]].

In the book [[Thing Explainer]] a similar chart for metrics is shown in the explanation for ''How to count things'', with four of the five measures from this comic also explained in simple language. Only volume is left out there. Only thing used in both explanations is the weight of a cat, but in the book it weighs 5 kg rather than 4 kg in this comic.

===Temperature===
*60⁠ °C - {{w|Extremes on Earth|Earth's hottest}}: The hottest temperature recorded on earth is actually {{W|List_of_weather_records#Heat|"only" 56.7 °C}}. There have been reports of temperatures ten-twenty degrees higher (70−80 ⁠°C) but these measurements are not verified or accepted as world records.
*45 °C, 40 °C⁠, 35⁠ °C: Various heat waves. {{w|Dubai}} is a city in the United Arab Emirates, and is smack-dab in the middle of an equatorial desert, so their heat waves can get ''hot!''. The southern United States will typically be a few degrees hotter than the northern United States simply because it's closer to the equator, but as mentioned they're both above "Beach Weather".
*30 °C: A little too hot so perfect for a trip to the beach.
*25 °C: Would as mentioned be too warm for room temperature...
*20 °C: Defined as room temperature in many experimental settings. For some this would feel a little cool.
*10 °C: Definitely wear a jacket. Especially if there is just a little breeze.
*0⁠ °C: The freezing point of water.
*−5 °C, −10 °C: In Moscow −10 °C is not really that cold - it can go "spit goes clink" cold in {{W|Moscow#Climate|Moscow}}, whereas −5 °C in {{W|Boston#Climate|Boston}} may be very cold.
*−20 °C - FuckFuckFuckCold,
*−30 °C - Fuuuuuuuuuuck!: This is implied to be basically what some people would say when they step outside at this temperature. In reality, it would be best to keep ones's mouth firmly closed. At −30 °C, without taking wind chill into account, exposed skin will feel painful in under a minute and frostbite could begin in as little as ten minutes [http://www.ec.gc.ca/meteo-weather/default.asp?lang=En&n=5FBF816A-1]. The differing statements seem to imply that at −20 °C, the user would be saying "fuck" repeatedly, whereas at −30 °C, the user is incapable of closing their mouth after starting the first "fuck", and so extends it into one long one.
*−40⁠ °C - Spit goes "clink": As shown in the drawing your spit would freeze ''before'' it hits the ground. This is the agreement point of the two temperature scales i.e. −40 °C = −40 °F.

See also [[1643: Degrees]] about not being able to choose between the two temperature scales and [[1923: Felsius]] about a compromise between the two scales. In the comic [[1982: Evangelism]], some people are stated to argue for the US to convert to the metric system, except for the Fahrenheit scale which they wish to keep.

===Length===
*1 cm - Width of microSD card, 3 cm - Length of SD card: Refers to the {{w|MicroSD card|memory cards}} used in cell phones, digital cameras, etc.
*12 cm: CD-ROM is a common object so nice to know it is a dozen centimeters.
*14 cm: Most males would probably exaggerate the size of their penis, but 14–15 cm is very average.
*15 cm: A Bic pen.
*80 cm: A typical doorway width is also of standard size. This is barely over the minimum size typically required by codes for buildings (30 inches or 76.2 cm in the US), but more than 50% over the size required for aircraft emergency exits. (It may seem illogical that larger doors are required in buildings than in airplanes, given airplanes are arguably more dangerous. However, there is no real disadvantage to using larger doors in buildings, which are not significantly pressurized, but using larger doors in aircraft would increase the force on the door caused by cabin pressure proportionally.)
*1 m - {{w|Lightsaber|Lightsaber blade}}: Refers to the weapon used in the ''{{w|Star Wars}}'' movie franchise. Canonically, the length of a lightsaber's blade varies greatly depending on the setting of the weapon, but "one meter" is by no means a bad approximation.
*170 cm - {{w|Summer Glau}}: Refers to the height of the actress who portrays the character River Tam on the TV show {{w|Firefly (TV series)|Firefly}}.
*200 cm - {{w|Darth Vader}}: Refers to the height of the main antagonist from ''Star Wars''.
*2.5 m: A ceiling - of course very much depending on which type of building you are in!
*5 m: A car length - also very much depending on the car...
*16 m 4 cm - Human tower of Serenity crew: Again, this refers to the Firefly TV show, which takes place mostly on a space ship called Serenity.
**Presumably, if all the crew of Serenity were stacked on top of each other, this would be their combined height.
**The comic depicts four characters from the show standing on top of each other; the bottom figure is the crew's captain, {{w|Malcolm Reynolds}} in his signature coat. Judging from the other drawing of Summer Glau from the volume section, she is standing on top of the captain.
**The other five members of the crew should also be stacked on top of these four to reach the 16.04 m height - giving them an average height of 1.78 m (8 cm more than Summer Glau's height!)

===Speed===
:Here both the SI unit m/s as well as the more commonly used unit kph (km/h) is given. Note that the SI prefers "km/h" over the non-standard abbreviation "kph".
*5 kph - 1.5 m/s: Walking at a normal pace.
*13−25 kph - 3.5−7 m/s: Jogging to sprinting.
*35 kph - 10 m/s - Fastest human: As of 2009, the fastest a human has been recorded to run in a single sprint is actually 12.4 m/s or 44.7 km/h, a record set by {{w|Usain Bolt}}.
*45−55 kph - 13−15 m/s: Both cats and rabbits go much faster than normal people.
*75 kph - 20 m/s - Raptor: It's a comic written by [[Randall]]; of course a reference to the {{w|velociraptors}} from ''{{w|Jurassic Park (film)|Jurassic Park}}'' was going to be here.
*100 kph - 25 m/s: A slow highway. (25 m/s actually exactly equals 90 km/h.)
*110 kph - 30 m/s - Interstate (65 mph): Refers to the {{w|Interstate|American highway system}}. (65 mph would actually be only 104.6 km/h.)
*120 kph - 35 m/s - Speed you actually go when it says "65": People routinely break the aforementioned speed limit, and the police typically don't mind as long as it's not posing any danger.
*140 kph - 40 m/s - Raptor on hoverboard: The {{w|hoverboard}} and its speed (~88 mph) is probably a reference to the ''{{w|Back to the Future Part II}}'', though hoverboards are a fairly common trope in older science fiction stories. Randall obviously did a lot of google searching on this subject the week before - see [[522: Google Trends]].

===Volume===
*3 mL: The amount of blood in a fieldmouse. A similar amount is used in comic [[434: xkcd Goes to the Airport]].
*5 mL: A teaspoon - a very common measure.
*30 mL - Nasal passages, 40 mL - Shot glass: The comic points out that you could just about fill a shot glass using the mucus from your nose. Since shot glasses are usually used for mixed drinks, the comic jokes that this mucus could constitute a new, disgusting drink - and this is depicted in the drawing. Much later, in [[2673: Cursed mRNA Cocktail]], a similar disgusting drink is suggested to be served in shot glasses. Actually specifically in relation to trying not to get blocked nasal passages as it is in relation to the [[:Category:COVID-19 vaccine|COVID-19 vaccine]].
*350 mL: Soda can (this is roughly correct for the cans used in the U.S., which hold 12 fluid ounces or 355 mL; in Europe, soda cans commonly hold 330 mL or 500 mL).
*500 mL: Water bottle (this is also the volume of a European water bottle).
*3 L - Two-liter bottle: Refers to a bottle which contains 2 L (in the US usually soda). There is debate as to the reason for the discrepancy in volume. It may be a reference to stereotypical Americans consuming a lot of high-calorie foods and drinks. The simpler explanation would be that it is a joke. The two-liter bottle is named using its volume. Labeling it with a volume of three liters is the joke.
*5 L: An adult male has about 5 L of blood in his body (An ''adequate'' vacuuming system could drain this blood out in 10 s - as per the title text!)
*30 L - Milk crate: Refers to a {{w|Milk crate|type of small box}} originally used to transport milk but now often in demand to be used as a bicycle basket, storage spaces, etc.
*55 L - Summer Glau: Again, this refers to the actress from Firefly.
*65 L - {{w|Dennis Kucinich}}: An American politician belonging to the {{w|Democratic Party (United States)|Democratic party}}, noted for his relatively strong (for the US) leftist views.
*75 L - {{w|Ron Paul}}: An American politician, member of the {{w|Republican Party (United States)|Republican Party}} at the time of this comic's release who has since switched back to the {{w|Libertarian Party (United States)|Libertarian Party}}.
*200 L: Volume of a refrigerator.
**As shown in the drawing of this part of the comic, the three persons mentioned above - Glau, Kucinich and Paul (summing up to 195 L) - could in principle all fit inside a standard refrigerator. Cueball thus attempts to push them all inside of one - though human bodies are not likely to be sufficiently malleable for this to succeed.

===Mass===
*3 g - {{w|M&M's|Peanut M&M}}: A small chocolate candy with a peanut inside.
*100 g - Cell phone: The weight of a cell phone very much depends on the age, type etc.
*500 g: A bottle of water contains 500 mL according to the volume section and thus has a mass of 500 g.
*1−3 kg: Different types of laptops.
*5 kg - {{w|LCD monitor}}: A modern flat-screen-style monitor.
*15 kg - {{w|CRT monitor}}: An older-style, cathode ray tube-based monitor.
**This ends the section on computer screens, which overrode the normal sequence by weight as the next two feline inspired entries are lighter than the two before. This was presumably done so that the reader's eye will be confused or amused at seeing (in the comic's caseless captioning font) CRT immediately followed by CAT in the vertical text column.
*4 kg - Cat, 4.1 kg - Cat (with caption): Refers to the internet's love of putting {{w|Lolcat|captions on cats}}. Usually, this is done in a graphics program, but here the cat is actually physically carrying around his caption. The "with caption" part is most likely a reference to [[262: IN UR REALITY]], where [[Black Hat]] glues captions to cats, after running out of staples.
*60 kg - Lady: For instance if she is Summer Glau - could be her again depicted in the comic - the average weight of an adult woman.
*70 kg - Dude: Here depicted as Cueball who is the average guy, and 70 kg is average weight for an adult man.
*150 kg - Shaq: {{w|Shaq|Shaquille O'Neal}}, a famously tall basketball player.
*200 kg - Your mom,
*220 kg - Your mom (incl. cheap jewelry),
*223 kg - Your mom (also incl. makeup)
**The last three refer to a common type of {{w|Your mom}} joking insult whereby someone insults someone else's mother in a (theoretically) creative way. Here, the comic slyly calls your mom fat, then implies she wears way too much jewelry and finally also 3 kg of makeup. This is a common theme in [http://www.explainxkcd.com/wiki/index.php/Category:Your_Mom xkcd]. (20 kg of "cheap" jewelry has several times the volume than 20 kg of gold jewelry, because of the difference in density.)

===Title text===
The title text refers once again to Summer Glau's Firefly character, {{w|River Tam}}, who (after being subjected to a long series of medical experiments) is severely mentally ill and often comes out with macabre — though scientifically accurate — pronouncements. In Firefly episode "Safe" (season 1, episode 7), she says: "The human body can be drained of blood in 8.6 seconds given adequate vacuuming systems."

===Conversion table===
The idea of the comic is to establish new metric reference points and ''not'' to resort to unit conversions. Nevertheless, the following table lists all units from the comic with their US customary equivalents:

{| class="wikitable"
! colspan="2" | Temp.
! colspan="2" | Length
! colspan="3" | Speed
! colspan="2" | Volume
! colspan="2" | Mass
|-
|60 °C||140 °F||1 cm||0.4 in||km/h||mph||m/s||3 mL||0.10 fl oz||3 g||0.11 oz
|-
|45 °C||113 °F||3 cm||1.2 in||5||3||1.5||5 mL||0.17 fl oz||100 g||3.5 oz
|-
|40 °C||104 F||12 cm||4.7 in||13||8||3.5||30 mL||1.0 fl oz||500 g||1.1 lb
|-
|35 °C||95 °F||14 cm||5.5 in||25||16||7||40 mL||1.4 fl oz||1 kg||2.2 lb
|-
|30 °C||86 °F||15 cm||5.9 in||35||22||10||350 mL||12 fl oz||2 kg||4.4 lb
|-
|25 °C||77 °F||80 cm||31 in||45||28||13||500 mL||17 fl oz||3 kg||6.6 lb
|-
|20 °C||68 °F||1 m||3 ft 3 in||55||34||15||3 L||0.8 gal||5 kg||11 lb
|-
|10 °C||50 °F||170 cm||5 ft 7 in||75||47||20||5 L||1.3 gal||15 kg||33 lb
|-
| 0 °C||32 °F||200 cm||6 ft 7 in||100||62||25||30 L||7.9 gal||4 kg||8.8 lb
|-
| -5 °C||23 °F||2.5 m||8 ft 2 in||110||68||30||55 L||15 gal||4.1 kg||9.0 lb
|-
| -10 °C||14 °F||5 m||16 ft||120||75||35||65 L||17 gal||60 kg||130 lb
|-
| -20 °C||-4 °F||16.04 m||52 ft 7 in||140||87||40||75 L||20 gal||70 kg||150 lb
|-
| -30 °C||-22 °F|| || || || || ||200 L||53 gal||150 kg||330 lb
|-
| -40 °C||-40 °F|| || || || || || || ||200 kg||440 lb
|-
| || || || || || || || || ||220 kg||485 lb
|-
| || || || || || || || || ||223 kg||492 lb
|}

==Transcript==
:<big>Guide to Converting to Metric</big>

:[There are five frames with tables for different units. Between the two upper frames is the following text:]
:The key to converting to metric is establishing new reference points. When you hear "26°C", instead of thinking "that's 79°F" you should think, "that's warmer than a house but cool for swimming."
:Here are some helpful tables of reference points:

:[The frame in the top left lists the following temperatures on the left, with the corresponding descriptions on the right. Next to the last three entries we see Cueball spitting on the ground. The spit freezes.]
:Temperature

:60°C    Earth's hottest
:45°C    Dubai heat wave
:40°C    Southern US heat wave
:35°C    Northern US heat wave
:30°C    Beach weather
:25°C    Warm room
:20°C    Room temperature
:10°C    Jacket weather
:0°C      Snow!
:-5°C     Cold day (Boston)
:-10°C   Cold day (Moscow)
:-20°C   Fuckfuckfuckcold
:-30°C   Fuuuuuuuuuuck!
:-40°C   Spit goes "clink"

:Cueball: Ptoo
:Spit: Clink!

:[The frame in the top right lists the following lengths on the left, with their corresponding descriptions on the right. To the right of the table is a human tower of four of the people from the ''Serenity'' crew. The head of the upper person is right below the first entry.]
:Length

:1 cm         Width of microSD card
:3 cm         Length of SD card
:12 cm       CD diameter
:14 cm       Penis
:15 cm       BIC pen
:80 cm       Doorway width
:1 m           Lightsaber blade
:170 cm     Summer Glau
:200 cm     Darth Vader
:2.5 m        Ceiling
:5 m           Car-length
:16 m 4 cm Human tower of Serenity crew.

:[The frame in the bottom left has three columns]
:Speed

:kph   m/s
:5      1.5    Walking
:13    3.5    Jogging
:25    7       Sprinting
:35    10     Fastest human
:45    13     Housecat
:55    15     Rabbit
:75    20     Raptor
:100   25    Slow highway
:110   30    Interstate (65 mph)
:120   35    Speed you actually go when it says "65"
:140   40    Raptor on hoverboard

:[The frame in the bottom middle lists the following volumes on the left, with their corresponding descriptions on the right.
:Volume

:3 mL     Blood in a fieldmouse
:5 mL     Teaspoon
:30 mL    Nasal passages
:40 mL    Shot glass
:350 mL   Soda can
:500 mL   Water bottle
:3 L         Two-liter bottle
:5 L          Blood in a human male
:30 L        Milk crate
:55 L        Summer Glau
:65 L        Dennis Kucinich
:75 L        Ron Paul
:200 L      Fridge

:[Next to the entry on nasal passages and shot glass (starting one entry higher and finishing one entry lower) is the following text:]
:So, when it's blocked, the mucus in your nose could about fill a shot glass.

:[Below this text is a drawing of a mucus filled shot glass.]
:Related: I've invented the worst mixed drink ever.

:[Below this next to the four last entries we see Cueball shoving Summer Glau, Dennis Kucinich and Ron Paul into an open fridge. Above the fridge in a loosely drawn ellipse is the following text:]
:55+65+75 < 200

:[The frame in the bottom right lists the following masses on the left, with their corresponding descriptions on the right

:3 g       Peanut M&M
:100 g    Cell phone
:500 g    Bottled water
:1 kg      Ultraportable laptop
:2 kg      Light-medium laptop
:3 kg      Heavy laptop
:5 kg      LCD monitor
:15 kg     CRT monitor
:4 kg       Cat
:4.1 kg    Cat (with caption)
:60 kg     Lady
:70 kg     Dude
:150 kg   Shaq
:200 kg   Your mom
:220 kg   Your mom (incl. cheap jewelry)
:223 kg   Your mom (also incl. makeup)

:[Next to the entries of cat and cat (with caption) are two drawings of cats. The second one has a caption across its chest.]
:Cat (with caption): Mrowl?
:[Below this and next to the lady and dude entries are drawings of Megan and Cueball.]

{{comic discussion}}
[[Category:Charts]]
[[Category:Comics featuring real people]]
[[Category:Comics featuring Megan]]
[[Category:Comics featuring Cueball]]
[[Category:Velociraptors]]
[[Category:Cats]]
[[Category:Your Mom]]
[[Category:Firefly]]
[[Category:Star Wars]]
[[Category:Comics featuring Summer Glau]]
[[Category:Weather]]

1953: The History of Unicode

2022-12-02T13:09:35Z

Graham87: /* Explanation */ copyedit, use more common date format in US

{{comic
| number = 1953
| date = February 9, 2018
| title = The History of Unicode
| image = the_history_of_unicode.png
| titletext = 2048: "Great news for Maine—we're once again an independent state!!! Thanks, @unicode, for ruling in our favor and sending troops to end New Hampshire's annexation. 🙏🚁🎖️"
}}

==Explanation==
An {{w|character encoding|encoding of a character set}} is a mapping from characters to numbers. For example, the letter "A" might be represented by the value 65. A problem was that each script had its own character set. Different characters could be represented by the same value. Some languages, such as Japanese, had several inconsistent character encodings, so before people could send text, they would have to have agreed which character set to use. {{w|Unicode}} was planned as a way of solving this by providing for a single character encoding for all the various characters used in the world's languages.

Unicode is run by {{w|Unicode Consortium|a consortium}} of major technology companies and stakeholders. The founders of Unicode include {{w|Joe Becker (Unicode)|Joe Becker}}, who worked for Xerox in the 1980s. He has a beard and may be the character featured in the first and third panels.

New characters have continued to be added to Unicode, and recently many "{{w|emoji}}" (picture characters) have been added. Emoji were originally added to be compatible with text message encodings in Japan, but after devices in other countries started supporting them as part of Unicode, they caught on worldwide. Now emoji characters are added for their own sake, not just for compatibility.

The [https://emojipedia.org/lobster/ lobster emoji], 🦞, was approved as part of Unicode 11, for release in 2018. This comic was published on February 10, 2018‎.

This comic shows the creator of Unicode talking about how it would change the way we thought about managing text, which could help with incompatible binary text encoding. This seems to have derailed over the next 30 years, as shown in [https://twitter.com/SenAngusKing/status/961331752718557184 a real tweet] from the junior Senator from {{w|Maine}}, {{w|Angus King}}. In the {{w|Twitter|tweet}}, Sen. King writes that he is excited that the system is getting a new lobster emoji, showing that now the Unicode system is used for more frivolous reasons. He even signs using two emoji to form his name. There is a cattle breed called {{w|Angus cattle}}, so the cow emoji, 🐮, stands for "Angus", and the crown emoji, 👑, of course represents "King". Thus Angus King becomes 🐮👑. This is thus not part of the xkcd joke; it just uses the real tweet for comic effect. The tweet was released February 7th, only two days before this comic; the second comment on the tweet posted this comic and asked which came first, but of course the tweet did. A user comments that Senator King should see it as a badge of honor (🎖) to have his tweet included in an xkcd strip...

The title text imagines that Unicode will gain other unexpected roles in the next 30 years. In particular it acts as an armed force, capable of intervening in military disputes, such as an annexation of Maine by its neighbor, New Hampshire. The title text ends with three Unicode emoji: "🙏" code point 1F64F "PERSON WITH FOLDED HANDS", "🚁" code point 1F681 "HELICOPTER", and "🎖" code point 1F396 "MILITARY MEDAL", suggesting that they are thanking them for their effort in the war, sending helicopters and soldiers to aid them against New Hampshire. The phrase "we're once again an independent state" may also be a political pun, as 2048 should be an election year, and King is an Independent senator.

==Transcript==
:[1988:]
:[A bearded man holds a document labeled "Unicode". Most likely he represents Joe Becker.]
:Bearded man: My "Unicode" standard should help reduce problems caused by incompatible binary text encodings.

:[2018:]
:[A tweet from Twitter is shown. To the left of Senator Angus King's name is his avatar (a face with a mustache) and to the right is the blue checkmark used by Twitter to signify a verified user.]
:Senator Angus King‏
:@SenAngusKing
:Great news for Maine - we're getting a lobster emoji!!! Thanks to @unicode for recognizing the impact of this critical crustacean, in Maine and across the country.
:Yours truly,
:Senator 🐮👑
:2/7/18 3:12 PM

:[Cueball and the bearded man (the latter now grey-haired) are looking at a wall with the Unicode standard, labeled "1988", and Senator King's tweet, labeled "2018", posted on it.]
:Cueball: What... what happened in those thirty years?
:Bearded man: ''Things got a little weird, okay?''

==Trivia==
*Initial version of the comic had "1998" in panel 3 instead of "1988" as shown in panel 1. This was fixed later.

*Ironically, [http://www.explainxkcd.com/wiki/index.php?title=1953:_The_History_of_Unicode&oldid=152168 the first version of this article] (automatically generated by a bot) had problems with emoji encoding.

*At one time the scenario in the title text wouldn't have been ''quite'' as far-fetched as it sounds. Maine and New Hampshire were for many years involved in border disputes, primarily over {{w|New Hampshire v. Maine|fishing rights}} and whether {{w|Seavey%27s Island|Seavey Island}}, located in the middle of the river that forms the border of the two states, was part of Maine or New Hampshire. The latter issue {{w|Piscataqua River border dispute|was not settled until 2002}}. Neither dispute ever quite rose to the level of a full-on shooting war but [http://nhpr.org/post/legacy-nh-maine-lobster-war-and-why-it-may-wage#stream/0 they got surprisingly close].

{{comic discussion}}

[[Category:Comics with color]]
[[Category:Comics featuring real people]]
[[Category:Comics featuring Cueball]]
[[Category:Emoji]]
[[Category:Unicode]]
[[Category:Comics edited after their publication]]

906: Advertising Discovery

2022-11-27T09:19:24Z

Graham87: /* Explanation */ word order

{{comic
| number = 906
| date = June 1, 2011
| title = Advertising Discovery
| image = citations.png
| titletext = When advertisers figure this out, our only weapon will be blue sharpies and "[disputed]".
}}

==Explanation==
On {{w|Wikipedia}}, a well-referenced text or statement indicates credibility. References for particular facts are linked to by bracketed blue little numbers in {{w|superscript}}.<ref>Aha! I fooled you and this is a real ref tag! However, there are no references.</ref>[3][4] When faced with a statement followed by these, readers will normally believe it without further ado,[6][10] since they take it on trust that there are directions on the bottom of the page, leading to a reliable source or two, agreeing with what the statement says. The effect becomes strengthened when such information is often confirmed to be correct.

In the comic, Cueball reads part of an ad for a penis enlargement drug. As the footnote numbers[1][2][3] are not a contiguous sequence[1][3][4] starting from 1, the ad contains other content[5] before the shown portion.[2][4][6]

Advertisers have realized that it has gone so far that people in general will take any nonsense for granted if there is just the right amount of Wikipedia-style reference tags to it. The penis enlargement e-commerce business can suddenly flourish (again?) and the spammers won't even need to bother making up findings to cite.

Turgidax{{w|Registered trademark symbol|®}} is something [[Randall]] formed from ''{{Wiktionary|turgid}}'', meaning swollen. One reason that the attaching of ''-ax'' creates a typically pill-like name is simply that ''-ax'' (and ''-ex'') are common Latin adjectival word endings, and that many drugs have names formed from Latin words. -Ax is also, specifically, the root of the -acious ending in English, as in "audacious" or (appropriately) [http://www.merriam-webster.com/dictionary/bodacious bodacious], meaning "extra" or "especially". Therefore, the name suggests that the drug causes male genitals to become extra or especially turgid.

''{{Wiktionary|Cardiovascular}}'' means relating to the heart and blood vessels. While it is plausible that the enlargement of genitals could increase {{w|sexual attractiveness}}, unless it is so excessive as to cause an {{w|unintended effect}}, enlargement itself is unlikely to affect cardiovascular health.

The title text is about how Wikipedia users have been able to add "disputed"-tags (nowadays "disputed – discuss") after challenged facts, with {{w|Template:Disputed-inline|this template}}, since the dawn of time.[11][disputed – discuss] So when faced with the new advertising trick {{w|Real life|IRL}}, we could counter by scribbling those tags all over with blue {{w|Sharpie (marker)|Sharpie}} marker pens, and so automatically revive the {{w|critical thinking}}.

==Transcript==
:[Caption above the panel:]
:Advertising discovery:
:[Person sits at computer, reading an ad on the screen. The bracketed superscripts are blue.]
:Ad: Turgidax® triples[2] your penis size overnight,[2][5] improving both your sexual attractiveness[2][7] and your cardiovascular health.[7][8][9]
:Person (thinking): Sounds legit.
:[Caption below the panel:]
:Wikipedia has trained us to believe anything followed by little blue numbers in brackets.

==Trivia==
* Randall changed the image name from advertising_discovery.png to citations.png, since adblocking extensions interpreted it as an ad and made the comic blank. He had the same problem just three months earlier with [[870: Advertising]].

== References ==
<references/>

{{comic discussion}}
[[Category:Comics with color]]
[[Category:Comics featuring Cueball]]
[[Category:Penis]]
[[Category:Wikipedia]]

1354: Heartbleed Explanation

2022-10-16T16:35:31Z

Graham87: /* Explanation */ copyedit

{{comic
| number = 1354
| date = April 11, 2014
| title = Heartbleed Explanation
| image = heartbleed_explanation.png
| titletext = Are you still there, server? It's me, Margaret.
}}

==Explanation==
The {{w|Heartbleed bug}} has received a lot of news coverage recently and was also the topic of the previous comic [[1353: Heartbleed]]. This comic explains how the bug may have been discovered and can be exploited to reveal a server's memory contents.

A [[Megan]]-like character named Margaret (or "Meg") sends heartbeat requests to the server, the server responds to the heartbeat request by returning the contents of the body of the request up to the number of letters requested. The first two requests are well formed, requesting exactly the number of characters in the request body. The server's memory is showing Meg's request with many other requests going on at the same time.

Meg then ponders this and tries to submit another request asking for "HAT" but requests that it be 500 letters long instead of only 3; the server —not checking it or simply unaware that 500 letters is larger than the request body— returns "HAT" plus 497 letters that happened to be next to the word "HAT" in its memory (more will follow than are shown in the server's speech bubble as there are only 251 letters/symbols in the shown reply). Included are many sensitive bits of information, including a master key and user passwords. One of the passwords shown is "CoHoBaSt", a reference to [[936: Password Strength]], which suggests using "correct horse battery staple" as a password.

Often popular explanations of security bugs require the issue to be simplified a lot and to leave out a lot of details. In this case [[Randall]] didn't have to do much simplifying; the bug is actually that simple. Also, any client that can connect to the server can typically exploit this bug in the underlying {{w|OpenSSL}} software — the use of the term "User Meg" does not imply that Meg had to authenticate first.

Although Randall shows Meg recording the data by hand, on paper, it is more likely that a person exploiting the bug would have a computer record the data, perhaps on its hard drive or on a flash drive.

The title text is a reference to ''{{w|Are You There God? It's Me, Margaret.}}'', a novel by {{w|Judy Blume}}, and plays off of the "server, are you still there?" line in every panel where she did start a request. The novel is the theme of another comic [[1544: Margaret]] too. ''Meg'' can be a nickname for ''Margaret'' as well as ''[[Megan]]'' who Margaret resembles.

==Transcript==
:[Caption above the panels:]
:'''How the Heartbleed Bug works:'''

:[Meg, a girl with more curly hair than Megan, stands to the left in a panel. At the center of the panel is a black and gray server with red and green diode lights showing. During all six panels the server stays the same. Meg is standing with her arms down in four panels. It will be noted when she does not. Meg talks to the server. The server "thinks" all the time, i.e. we see its memory in all panels. The top and bottom line is breaking the edge of the thought bubble making it difficult to discern. In every second panel it replies to Meg. In these panels the number of letters requested by Meg is highlighted with yellow color.]

:[Meg speaks, server thinks:]
:Meg: Server, are you still there? If so, reply "POTATO" (6 letters).
:Server thinking: <tt>wants pages about "boats". User Erica requests secure connection using key "4538538374224" '''User Meg wants these 6 letters: POTATO.''' User Ada wants pages about "irl games". Unlocking secure records with master key 5130985733435. Maggie (chrome user) sends this message: "Hi</tt>

:[Server thinks, the same as above, although cut a little different at the edges, with POTATO highlighted in yellow and it replies the highlighted part in a rectangular speak bubble.]
:Server thinking: <tt>wants pages about "boats". User Erica requests secure connection using key "4538538374224" '''User Meg wants these 6 letters: POTATO.''' User Ada wants pages about "irl games". Unlocking secure records with master key 5130985733435. Maggie (chrome user) sends this message: "Hi</tt>
:Server: <tt>POTATO</tt>

:[Meg speaks, server thinks:]
:Meg: Server, are you still there? If so, reply "BIRD" (4 letters).
:Server thinking: <tt>User Olivia from London wants pages about "man bees in car why". Note: Files for IP 375.381.283.17 are in /tmp/files-3843. '''User Meg wants these 4 letters: BIRD.''' There are currently 348 connections open. User Brendan uploaded the file selfie.jpg (contents: 834ba962e2ceb9ff89bd3bff8c</tt>...

:[Server thinks, the same as above, although cut a little different at the edges, with BIRD highlighted in yellow and it replies the highlighted part in a rectangular speak bubble. Meg has taken her hand to her chin thinking:]

:Server thinking: <tt>User Olivia from London wants pages about "man bees in car why". Note: Files for IP 375.381.283.17 are in /tmp/files-3843. '''User Meg wants these 4 letters: BIRD.''' There are currently 348 connections open. User Brendan uploaded the file selfie.jpg (contents: 834ba962e2ceb9ff89bd3bff8c</tt>...
:Server: <tt>BIRD</tt>
:Meg: ''Hmm...''

:[Meg has taken her hand down again and speaks, server thinks, now with her line at the top:]

:Meg: Server, are you still there? If so, reply "HAT" (500 letters).
:Server memory: <tt>a connection. Jake requested pictures of deer. '''User Meg wants these 500 letters: HAT.''' Lucas requests the "missed connections" page. Eve (administrator) wants to set server's master key to "14835038534". Isabel wants pages about "snakes but not too long". User Karen wants to change account password to "CoHoBaSt". User</tt>

:[Server thinks, the same as above, although cut a little different at the edges, with everything from (and including) "HAT" highlighted in yellow and it replies the highlighted part and even more in a rectangular speech bubble. Meg has taken a notebook and a pen and is writing something.:]

:Server memory: <tt>a connection. Jake requested pictures of deer. '''User Meg wants these 500 letters: HAT.''' Lucas requests the "missed connections" page. Eve (administrator) wants to set server's master key to "14835038534". Isabel wants pages about "snakes but not too long". User Karen wants to change account password to "CoHoBaSt". User</tt>
:Server: <tt>HAT. Lucas requests the "missed connections" page. Eve (administrator) wants to set server's key to "14835038534". Isabel wants pages about "snakes but not too long". User Karen wants to change account password to "CoHoBaSt". User Amber requests pages</tt>

{{comic discussion}}

[[Category:Comics with color]]
[[Category:Computers]]

926: Time Vulture

2022-10-11T13:12:15Z

Graham87: /* Explanation */ grammar

{{comic
| number = 926
| date = July 18, 2011
| title = Time Vulture
| image = time vulture.png
| titletext = In a way, all vultures are Time Vultures; some just have more patience than others.
}}

==Explanation==
This comic is about the ''time vulture'' (hence the title), a fictional creature made up by [[Randall]]. [[Cueball]] notices that his Cueball-like friend is followed by a time vulture, making the exclamation '' Dude, you've got a time vulture.''

The primary food source for {{w|Vulture|vultures}} is carrion, or rotting meat. A time vulture, as explained by Cueball, is a type of vulture that can live for {{w|Millennium|millennia}}, spending very little energy and it can even slow down its internal clocks so time speeds past, a kind of forward time travel, to the point where its prey dies. In this way, it can thus always wait long enough for the prey to die of natural causes no matter how long it takes, as seen from the prey's point of view. So in principle they kill their prey by using aging, as Cueball explains, although in fact, like any vulture, they just find prey that has already (almost) died, as from their point of view every living thing is just about to die. But as with other vultures, they do not participate in the actual killing. Time vultures thus just need to locate and find any one living creature (of a reasonable size), then it becomes it’s prey as it then just waits until it dies, spending hardly any energy while it waits. Real {{w|List of soaring birds|soaring}} vultures can also stay afloat for considerable time spans without actually using any energy as they just {{w|Lift (soaring)|float}} on {{w|thermals}}.

Thus the time vulture will now keep soaring over Cueball’s friends head for the rest of his life, or until they travel on an airplane (airplanes typically cruise at an altitude too high for a vulture to fly over them, although it is of course possible that the vulture could board the plane as well), and then when he dies (whenever and of whichever cause), it will descend and feast on his carcass. This should, in principle, not make any difference to the friend, since most people already live with the knowledge that they will eventually die{{Citation needed}}, and that their body will end up being destroyed one way or another. Typically it will not be caused by vultures, but for instance by the fire of the {{w|Crematory}} or by the {{w|decomposition}} caused by small animals and germs in the earth we are buried in.

However, it is not very nice to be reminded of this every living second of the rest of your life thus the consternation of the friend and his question and statement; ''But what if the prey doesn't die?'' and ''I'm not about to die...''

At first, the question doesn’t make sense since there are no known examples of terrestrial animals (including humans) that are large enough to matter as prey for a vulture and can survive through the several millennia that a time vulture can wait. The few {{w|List_of_longest-living_organisms|species that can live that long}} and grow at least as large as vulture prey, such as the 2,384 acre (965 hectare) "Humongous Fungus", an individual of the fungal species ''{{w|Armillaria solidipes}}'' in the {{w|Malheur National Forest}}, thought to be between 2,000 and 8,500 years old<ref>http://www.sciencedaily.com/releases/2003/03/030327074535.htm Humongous Fungus A New Kind Of Individual</ref><ref>http://www.scientificamerican.com/article.cfm?id=strange-but-true-largest-organism-is-fungus Strange but True: The Largest Organism on Earth Is a Fungus</ref>, and a {{w|Great Basin bristlecone pine}} (''Pinus longaeva'') measured by {{w|dendrochronology|ring count}} to be over 5000 years old.<ref>http://www.rmtrr.org/oldlist.htm</ref>, are stationary, such as fungi and plants, or aquatic, such as coral and sponges. Thus, the moving land species large enough to be attractive as prey will always die within the lifespan of the vulture (as Cueball tries to explain).

However, the question actually does make sense, because the prey does not have to outlive the vulture to avoid being eaten by the vulture; it simply has to live long enough to get to an airport, get through security screening, and board a flight that goes either too fast or too high for the vulture to follow. Therefore, the vulture would get to eat the prey only if the prey died on the way to the airport, while standing outdoors in line for security screening, or while walking from the terminal to the airplane (if passengers board outdoors instead of using a {{w|jet bridge|passenger boarding bridge (Jetway)}}). It is possible that the prey might not die this soon, unless security screening lines exceed the maximum human lifespan of approximately 120 years.

And because the time vulture can slow down its internal clock, in its point of view, everyone who ever says "But, I'm not about to die", would say so right before they die; actually anything a person ever says after the time vulture has locked on to that person, happens just before they die as seen from the vulture's point of view. In humans' point of view, it could be many years after the statement was made, but for the time vulture, a human lifespan only lasts a mere moment.

Of course, since a human can travel a considerable distance in this time, even around the world, the human would be traveling at an extremely high velocity from the vulture's perspective, so the vulture would be unable to keep up and the human would escape. In a more extreme fashion, since the vulture’s perception of time is significantly slowed, it would be more simple to buy a rifle and kill the Time Vulture.

It is thus really more of a philosophical comic about the fact that we all have death waiting for us, you could say it soars above our head and just wait for it to happen. And in relation to the {{w|deep time}} of the geology of the Earth or the expansion of the universe, the time it takes for people to live their lives is hardly worth mentioning...

In the title text it is stated that all real life vultures are actually a kind of time vultures, as real life vultures also sometimes spot a dying animal, not quite dead yet, and then wait for this prey to die. But time vultures are able to wait for millennia for their prey to die, whereas regular vultures do not have that kind of time, before they need to feed or land, thus the comment that some vultures have more patience than others.

Real vultures and their preying habits were referenced in [[1746: Making Friends]], directly in the title text.
<references/>

==Transcript==
:[Cueball is watching a large black bird, with apparently fractal wings, which hovers above his Cueball-like friend who walks towards Cueball and now turns to look at the bird over his shoulder.]
:Cueball: Dude, you've got a Time Vulture.
:Friend: Holy crap! What is it?

:[Zoom-in on Cueball who now looks at his friend who are now standing close to Cueball looking up at the bird off-panel.]
:Cueball: They're predators that use aging to kill prey.
:Friend: Huh? What do you mean?

:[The panel zooms in on the Cueball's face. The friends reply comes from off-panel.]
:Cueball: They live for millennia and use little energy. They can slow down their internal clocks so time speeds past. To hunt, they lock on to some prey, and when it stops moving, they eat it.
:Friend (off-panel): But what if the prey doesn't die?

:[Zoom out to Cueball and his friend that now look at each other.]
:Cueball: I don't think you quite understand.
:Friend: I mean, ''I'm'' not '''about''' to die...
:Cueball: From the vulture's viewpoint, everyone says that moments before they do.

{{comic discussion}}

[[Category:Comics featuring Cueball]]
[[Category:Multiple Cueballs]]
[[Category:Time]]
[[Category:Animals]]
[[Category:Philosophy]]

927: Standards

2022-10-11T13:09:15Z

Graham87: /* Explanation */ copyedit

{{comic
| number = 927
| date = July 20, 2011
| title = Standards
| image = standards.png
| titletext = Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shit.
}}

==Explanation==
For any engineering task, there are numerous ways a given problem can be solved. The more complex the task, the more room for diversity. That's all well and good for a one-off problem, but if a design is meant to be iterated over time, or if an entire industry is solving that same problem, part reuse and {{w|interoperability}} become issues to deal with. {{w|Technical standards}} thus came to exist so that industries could avoid wasting resources {{w|reinventing the wheel}}, whilst offering their clients a certain amount of simplicity and compatibility between vendors.

But standards have issues of their own. They don't accommodate every {{w|Use Case|use case}}, they might have restrictions or royalties attached, and people tend to be plagued by ''{{w|Not invented here|Not Invented Here syndrome}}''. So competing standards have a tendency to arise to address different perceived needs. After a while, the market for competing standards gets messy and hard to follow, and {{w|system integration|integrating systems}} built around competing standards gets burdensome. As a result, someone eventually takes on the challenge of creating a universal standard that everyone can rally around.

This almost never works. In many cases, a new standard fails to displace the incumbent standards, eventually loses funding and support, and thus becomes a relic of history. In many other cases, it only penetrates far enough to survive, ironically making the situation messier. The latter situation often ends up becoming cyclical, with new standards periodically rising and failing to gain traction.

Three examples are given at the top of the comic: {{w|AC adapter|AC chargers}}, {{w|character encoding}} and {{w|instant messaging}}.
* Power adapters are notorious for varying from device to device - partly to try to prevent dangerous voltage/current mismatches, but partly just because manufacturers all chose different adapter designs. Mobile phone chargers had mostly converged on a common USB-based solution, but laptop charging remained still a long way out, despite the adoption of yet another standard, {{w|IEC 62700}}, and current Apple iPhones now require "lightning" connectors and are not compatible with phone chargers using the USB-based solution. Randall notes that there was initially additional complexity due to the fact that there were also ''competing USB types'', but thanks to the European Union's {{w|common external power supply}} specification, micro-USB comprehensively won the day. Three years after the release of this comic, in August 2014 the {{w|USB Type-C}} specification was published and is currently displacing micro-USB, it's gaining ground among laptop manufacturers as well.
* Character encoding is, in theory, a solved problem - {{w|Unicode}} is a standard for character sets which currently includes over 135,000 characters. However, Unicode is not an encoding, just an abstract representation of the characters, and there are several implementations which encode Unicode "code points" into usable characters (including the two most common, {{w|UTF-8}} and {{w|UTF-16}}). Despite the [https://w3techs.com/technologies/history_overview/character_encoding/ms/y success of UTF-8 Unicode], older encodings like {{w|Windows-1252}} have stuck around, continuing to cause weird bugs in old software and websites to this day.
* Unlike the other examples, there has been little or no effort by instant messaging companies to make their services interoperable. There's more value to keeping IM as a {{w|closed platform}} so users are forced to use the company's software to access it. Some software, like the {{w|Trillian (software)|Trillian}} chat client, can connect to multiple different services, but there is essentially no way to, for example, send a Twitter message directly to a Skype user.

The title text mentions mini-USB and micro-USB, which were different standards used in 2011. As of 2019 for most applications of small USB ports (especially for charging / connecting cell phones), mini USB has lost most of its relevance and micro USB is competing with USB-C, as well as some solutions only used by single companies (such as Apple).

Not all {{w|technical standards|standards}} are created equal. In the development of {{w|technical standards|standards}}, private standards adopt a non-consensus process in comparison to voluntary consensus standards. Private standards in the {{w|Information and Communications Technology}} (ICT) sector and the agri-food industry (governed by the {{w|Global Food Safety Initiative}}) are discussed in a [https://docplayer.net/23885374-International-standards-and-private-standards.html publication from International Organization for Standardization.]

==Transcript==
:How Standards Proliferate
:(See: A/C chargers, character encodings, instant messaging, etc.)

:Situation:
:There are 14 competing standards.

:Cueball: 14?! Ridiculous! We need to develop one universal standard that covers everyone's use cases.
:Ponytail: Yeah!

:Soon:
:Situation: There are 15 competing standards.
{{comic discussion}}
[[Category:Comics featuring Cueball]]
[[Category:Comics featuring Ponytail]]

1755: Old Days

2022-09-27T11:46:41Z

Graham87: /* Table of statements */ copyedit

{{comic
| number = 1755
| date = November 4, 2016
| title = Old Days
| image = old_days.png
| titletext = Lot of drama in those days, including constant efforts to force the "Reflections on Trusting Trust" guy into retirement so we could stop being so paranoid about compilers.
}}

==Explanation==
This comic shows a conversation between (young) [[Cueball]] and (old) [[Hairbun]] about computer programming in the past, specifically {{w|compilers}}. Cueball, having a faint idea of just how difficult and byzantine programming was "in the old days", asks Hairbun to enlighten him on the specifics. Hairbun promptly seizes the opportunity to screw with his head. This later became a [[:Category:Old Days|series]] when [[2324: Old Days 2]] was released more than 3 and a half years later. While her initial agreement that code needed to be compiled for multiple architectures is correct, Hairbun's claims rapidly grow ridiculous.

Hairbun tells Cueball a tall tale about how hard it was back in the '''old days''', making it sound like some of the programming languages used today (C, C++) were written on punch cards and that you had to ship your code in the mail to a computer company ({{w|IBM}} in this case) to compile your code, which would take from four to six weeks. If there was a simple error, you would have to ship it again for another compilation.

This is factually incorrect, but is plausible to those who do not have the knowledge or context to challenge it, similar to a {{w|Snipe hunt}}, or several other cultural myths told about things like the {{w|Tooth Fairy}}. It is clear from Cueball's final ''Wow'' that he falls for it. She then continues to explain more and more implausible so-called facts from the the olden days.

What she says is true in that it was tough and slow to program on punch cards, which were actually used for an extended period of time. However, there is very little in the rest of Hairbun's story that is accurate, except that it was a big deal when the floppy disk was invented. The comment about punching holes in floppy disks is true. However, the nature and purpose of the holes punched this way was dramatically different than in punch cards. 5.25" and 3.5" floppy disks had holes or notches in them to indicate the data capacity and it was common to punch additional holes into cheaper, lower capacity floppy disks to trick the computer into writing more data on them than specified by the manufacturer. With punchcards on the other hand, the holes themselves encoded the data so punching them was itself the act of programming. It is unclear if this was a coincidence, or intentionally included as a humorous aside to the readers who know the history as a misinterpreted truth in a sea of falsehoods.

In the title text, Hairbun continues her musings on the old compiler days, stating that there was ''a lot of drama in those days''. Specifically she references ''[http://www.win.tue.nl/~aeb/linux/hh/thompson/trust.html Reflections on Trusting Trust]'' a famous 1984 paper by {{w|UNIX}} co-creator {{w|Ken Thompson}} in which he described a way to hide a virtually undetectable backdoor in the UNIX login code via a second backdoor in the C compiler. Using the technique in his paper, it would be impossible to discover the hacked login by examining the official source code for either the login or the compiler itself. Ken Thompson may have actually included this backdoor in early versions of UNIX, undiscovered. Ken Thompson's paper demonstrated that it was functionally impossible to prove that any piece of software was fully trustworthy.

Hairbun claims that one of the dramas she refers to was that people tried to force Ken Thompson to retire, so everyone could stop being so paranoid about compilers. In reality, any coder who created the first version of a compiler (or a similar critical component) could inject a similar backdoor into software, so it would be false safety. Even if no one else had thought of this, then Thompson's paper was there for any future hacker to see. Though the problem was (claimed to be) solved in {{w|David A. Wheeler}}'s Ph.D dissertation "[http://dwheeler.com/trusting-trust/ Fully Countering Trusting Trust through Diverse Double-Compiling (DDC)]".

==Table of statements==
{|class="wikitable"
!Statements
!Concepts used
!Explanation
|-
|Compile things for different processors
|{{w|Compiler}}s convert code from a human-readable programming language into a binary code that can be directly executed by computer processors.
|Many popular modern programming languages are either interpreted - meaning that they run directly from source code - or compile to an intermediate bytecode, like Java or common Python implementations. Programs written in such languages are portable across processor architectures - x86 to ARM, for example. {{w|Low-level programming language|Lower-level languages}} must take into account the features available on a given processor architecture and operating system. Before that, programs needed to compile directly into the native machine language for each processor they were intended to run on.
Native {{w|Machine code|machine language}} is dependent on processor architecture. Therefore different processors designed around different architectures will not run the same compiled code (unless the architectures are compatible; AMD64 processors will run i386 code natively, for example.) If the same code needs to be run on multiple architectures, it must be compiled separately for each supported architecture.
|-
|To compile your code, you had to mail it to IBM. It took 4-6 weeks.
|Similar to sending Kodachrome slide film to Kodak to be developed.
|While IBM has released multiple compilers, they sent the compiler to you, you did not send the code to them. There is some kind of truth in the statement, though: when programming on mainframes, programmers submitted their source code in the evening for compilation overnight. When there was an error in the code, they did not get a compiled version of it back, and had to resubmit their code. Sometimes there were time slots available for compilation, and in universities, students would have to wait for their next time slot for another try.
|-
|Before garbage collection, data would pile up until the computer got full and you had to throw it away.
|A {{w|Garbage collection (computer science)|garbage collector}} is a piece of the software that cleans the memory of data that is no longer being used in the execution of a program.
|Garbage collection is a form of memory management that generally destroys objects or frees up memory once a program no longer needs it. In languages without automatic memory management, like C, the program itself must keep track of what memory has been allocated, and free it once it is no longer needed. If the program does not, it can end up trying to use more memory than the computer has, and may crash. This was, however, a ''temporary'' condition. In the worst case, a simple reboot will clear the computer's memory.
|-
|Early compilers could handle code fine, but comments had to be written in assembly.
|A {{w|Comment (computer programming)|comment}} in programming is a text written in natural language that is meant to explain some feature of the source code; it is tagged such that the compiler will discard it to save space. {{w|Assembly language|Assembly}} is a low-level programming language.
|Comments, in code, are portions of one or more lines that are ignored by the compiler. They are commonly used to explain or comment on the code itself. But sometimes the comments are written in a certain way to compile documentation automatically from it. Also, when examining the output of compilers it's a common practice to use assembly code annotated with comments containing the source code of the program from which the assembly code was generated.

Hairbun's comment is thus very strange, implying the compilers of the day could only distinguish between comments and code if assembly was used to insert the separating tags.
|-
|C could only be written on punch cards. You had to pick a compact font, or you'd only fit a few characters per card.
|{{w|C (programming language)|C}} is a programming language. A {{w|punch card}} is a early form of storing data; the pattern of holes and non-holes in a paper or cardboard card represented information.
|Punch cards were used through the late 1970s and early 1980s to enter programs and data in COBOL, FORTRAN and other early languages. Punch cards and punch card machines were being replaced by magnetic storage and {{w|text editor|text editors}} by 1972, when C (or C++) was developed. This site demonstrates a card punch and cards: [http://www.masswerk.at/keypunch/ Keypunch].

Hairbun claims that code was not written using keyboards, but by punching out letter and character shapes in the punch cards, and the computer would read keystrokes that way. Simply put, this was never true. Punch cards store characters in binary; there is no font involved and they store up to fixed limit of characters per card (80 characters in the most common format.)
|-
|C++ was big because it supported floppy disks. It still punched holes in them, but it was a start.
|{{w|C++ (programming language)|C++}} is a programming language. A {{w|floppy disk}} is a form of storing data magnetically. It's way more advanced than punch cards (by several orders of magnitude; a card can store about 80 bytes, vs 1,474,560 bytes of a floppy disk), but it's still obsolete compared to modern storage.
|Hairbun says that the improvement from C to C++ was that C++ finally "supported floppy disks", but then it turns out that in C++ the floppy disks were just used instead of punch cards. So the programming was to make holes in floppy disks rather than punch cards. This would of course not be an improvement as floppy disks store information magnetically, as opposed to physically, as punch cards do. This is likely a play on the concept of punching holes in 5.25" floppy disks to double their storage (see {{w|Double-sided disk}}), or it can also be a reference to the "index hole" of 5.25" floppy disks (see {{w|Floppy_disk#Design|Floppy disk Design}} and the tiny hole at the right of the big central hole in this [https://www.staff.ncl.ac.uk/roger.broughton/museum/floppys/images/201041b.jpg image]). A notch in the side of 5.25" floppy disks indicates when the disk could be written. Though many floppy disks were intended to have only a single side with data, many people used a hole punch to notch the opposite side of the disk, allowing a drive to write data to the other side of the disk in a single sided drive. 5.25" floppies also featured a tiny "index hole" near the central hole of the disk.
|}

==Transcript==
:[Cueball and Hairbun are standing together and Cueball is talking to her.]
:Cueball: What were things like in the old days?
:Cueball: I hear that you had to ... compile things for different processors?
:Hairbun: Yeah

:[Same setting in a slimmer panel, now Hairbun is replying.]
:Hairbun: To compile your code, you had to mail it to IBM.
:Hairbun: It took 4-6 weeks.

:[Close-up of Hairbun from the waist up.]
:Hairbun: Before garbage collection, data would pile up until the computer got full and you had to throw it away.

:[Same setting as in the first panel with Hairbun gesturing toward Cueball raising one hand palm up.]
:Hairbun: Early compilers could handle code fine, but comments had to be written in assembly.

:[In a frame-less panel Hairbun is seen from the front, with both arms out to the side with both hands held palm up.]
:Hairbun: '''C''' could only be written on punch cards.You had to pick a compact font, or you'd only fit a few characters per card.

:[Exactly the same setting as the first panel, but with Hairbun doing the talking.]
:Hairbun: '''C++''' was big because it supported floppy disks.
:Hairbun: It still punched holes in them, but it was a start.
:Cueball: Wow.

{{comic discussion}}

[[Category:Comics featuring Cueball]]
[[Category:Comics featuring Hairbun]]
[[Category:Old Days]]
[[Category:Comics sharing name|Old Days]]
[[Category:Programming]]

1755: Old Days

2022-09-27T11:44:15Z

Graham87: /* Explanation */ copyedit

{{comic
| number = 1755
| date = November 4, 2016
| title = Old Days
| image = old_days.png
| titletext = Lot of drama in those days, including constant efforts to force the "Reflections on Trusting Trust" guy into retirement so we could stop being so paranoid about compilers.
}}

==Explanation==
This comic shows a conversation between (young) [[Cueball]] and (old) [[Hairbun]] about computer programming in the past, specifically {{w|compilers}}. Cueball, having a faint idea of just how difficult and byzantine programming was "in the old days", asks Hairbun to enlighten him on the specifics. Hairbun promptly seizes the opportunity to screw with his head. This later became a [[:Category:Old Days|series]] when [[2324: Old Days 2]] was released more than 3 and a half years later. While her initial agreement that code needed to be compiled for multiple architectures is correct, Hairbun's claims rapidly grow ridiculous.

Hairbun tells Cueball a tall tale about how hard it was back in the '''old days''', making it sound like some of the programming languages used today (C, C++) were written on punch cards and that you had to ship your code in the mail to a computer company ({{w|IBM}} in this case) to compile your code, which would take from four to six weeks. If there was a simple error, you would have to ship it again for another compilation.

This is factually incorrect, but is plausible to those who do not have the knowledge or context to challenge it, similar to a {{w|Snipe hunt}}, or several other cultural myths told about things like the {{w|Tooth Fairy}}. It is clear from Cueball's final ''Wow'' that he falls for it. She then continues to explain more and more implausible so-called facts from the the olden days.

What she says is true in that it was tough and slow to program on punch cards, which were actually used for an extended period of time. However, there is very little in the rest of Hairbun's story that is accurate, except that it was a big deal when the floppy disk was invented. The comment about punching holes in floppy disks is true. However, the nature and purpose of the holes punched this way was dramatically different than in punch cards. 5.25" and 3.5" floppy disks had holes or notches in them to indicate the data capacity and it was common to punch additional holes into cheaper, lower capacity floppy disks to trick the computer into writing more data on them than specified by the manufacturer. With punchcards on the other hand, the holes themselves encoded the data so punching them was itself the act of programming. It is unclear if this was a coincidence, or intentionally included as a humorous aside to the readers who know the history as a misinterpreted truth in a sea of falsehoods.

In the title text, Hairbun continues her musings on the old compiler days, stating that there was ''a lot of drama in those days''. Specifically she references ''[http://www.win.tue.nl/~aeb/linux/hh/thompson/trust.html Reflections on Trusting Trust]'' a famous 1984 paper by {{w|UNIX}} co-creator {{w|Ken Thompson}} in which he described a way to hide a virtually undetectable backdoor in the UNIX login code via a second backdoor in the C compiler. Using the technique in his paper, it would be impossible to discover the hacked login by examining the official source code for either the login or the compiler itself. Ken Thompson may have actually included this backdoor in early versions of UNIX, undiscovered. Ken Thompson's paper demonstrated that it was functionally impossible to prove that any piece of software was fully trustworthy.

Hairbun claims that one of the dramas she refers to was that people tried to force Ken Thompson to retire, so everyone could stop being so paranoid about compilers. In reality, any coder who created the first version of a compiler (or a similar critical component) could inject a similar backdoor into software, so it would be false safety. Even if no one else had thought of this, then Thompson's paper was there for any future hacker to see. Though the problem was (claimed to be) solved in {{w|David A. Wheeler}}'s Ph.D dissertation "[http://dwheeler.com/trusting-trust/ Fully Countering Trusting Trust through Diverse Double-Compiling (DDC)]".

==Table of statements==
{|class="wikitable"
!Statements
!Concepts used
!Explanation
|-
|Compile things for different processors
|{{w|Compiler}}s convert code from a human-readable programming language into a binary code that can be directly executed by computer processors.
|Many popular modern programming languages are either interpreted - meaning that they run directly from source code - or compile to an intermediate bytecode, like Java or common Python implementations. Programs written in such languages are portable across processor architectures - x86 to ARM, for example. {{w|Low-level programming language|Lower-level languages}} must take into account the features available on a given processor architecture and operating system. Before that, programs needed to compile directly into the native machine language for each processor they were intended to run on.
Native {{w|Machine code|machine language}} is dependent on processor architecture. Therefore different processors designed around different architectures will not run the same compiled code (unless the architectures are compatible; AMD64 processors will run i386 code natively, for example.) If the same code needs to be run on multiple architectures, it must be compiled separately for each supported architecture.
|-
|To compile your code, you had to mail it to IBM. It took 4-6 weeks.
|Similar to sending Kodachrome slide film to Kodak to be developed.
|While IBM has released multiple compilers, they sent the compiler to you, you did not send the code to them. There is some kind of truth in the statement, though: when programming on mainframes, programmers submitted their source code in the evening for compilation overnight. When there was an error in the code, they did not get a compiled version of it back, and had to resubmit their code. Sometimes there were time slots available for compilation, and in universities, students would have to wait for their next time slot for another try.
|-
|Before garbage collection, data would pile up until the computer got full and you had to throw it away.
|A {{w|Garbage collection (computer science)|garbage collector}} is a piece of the software that cleans the memory of data that is no longer being used in the execution of a program.
|Garbage collection is a form of memory management that generally destroys objects or frees up memory once a program no longer needs it. In languages without automatic memory management, like C, the program itself must keep track of what memory has been allocated, and free it once it is no longer needed. If the program does not, it can end up trying to use more memory than the computer has, and may crash. This was, however, a ''temporary'' condition. In the worst case, a simple reboot will clear the computer's memory.
|-
|Early compilers could handle code fine, but comments had to be written in assembly.
|A {{w|Comment (computer programming)|comment}} in programming is a text written in natural language that is meant to explain some feature of the source code; it is tagged such that the compiler will discard it to save space. {{w|Assembly language|Assembly}} is a low-level programming language.
|Comments, in code, are portions of one or more lines that are ignored by the compiler. They are commonly used to explain or comment on the code itself. But sometimes the comments are written in a certain way to compile documentation automatically from it. Also, when examining the output of compilers it's a common practice to use assembly code annotated with comments containing the source code of the program from which the assembly code was generated.

Hairbun's comment is thus very strange, implying the compilers of the day could only distinguish between comments and code if assembly was used to insert the separating tags.
|-
|C could only be written on punch cards. You had to pick a compact font, or you'd only fit a few characters per card.
|{{w|C (programming language)|C}} is a programming language. A {{w|punch card}} is a early form of storing data; the pattern of holes and non-holes in a paper or cardboard card represented information.
|Punch cards were used through the late 1970s and early 1980s to enter programs and data in COBOL, FORTRAN and other early languages. The use of punch cards and punch card machines were being replaced by magnetic storage and {{w|text editor|text editors}} by 1972, when C (or C++) was developed. This site demonstrates a card punch and cards: [http://www.masswerk.at/keypunch/ Keypunch].

Hairbun claims that code was not written using keyboards, but by punching out letter and character shapes in the punch cards, and the computer would read keystrokes that way. Simply put, this was never true. Punch cards store characters in binary; there is no font involved and they store up to fixed limit of characters per card (80 characters in the most common format.)
|-
|C++ was big because it supported floppy disks. It still punched holes in them, but it was a start.
|{{w|C++ (programming language)|C++}} is a programming language. A {{w|floppy disk}} is a form of storing data magnetically. It's way more advanced than punch cards (by several orders of magnitude; a card can store about 80 bytes, vs 1,474,560 bytes of a floppy disk), but it's still obsolete compared to modern storage.
|Hairbun says that the improvement from C to C++ was that C++ finally "supported floppy disks", but then it turns out that in C++ the floppy disks were just used instead of punch cards. So the programming was to make holes in floppy disks rather than punch cards. This would of course not be an improvement as floppy disks store information magnetically, as opposed to physically, as punch cards do. This is likely a play on the concept of punching holes in 5.25" floppy disks to double their storage (see {{w|Double-sided disk}}), or it can also be a reference to the "index hole" of 5.25" floppy disks (see {{w|Floppy_disk#Design|Floppy disk Design}} and the tiny hole at the right of the big central hole in this [https://www.staff.ncl.ac.uk/roger.broughton/museum/floppys/images/201041b.jpg image]). A notch in the side of 5.25" floppy disks indicates when the disk could be written. Though many floppy disks were intended to have only a single side with data, many people used a hole punch to notch the opposite side of the disk, allowing a drive to write data to the other side of the disk in a single sided drive. 5.25" floppies also featured a tiny "index hole" near the central hole of the disk.
|}

==Transcript==
:[Cueball and Hairbun are standing together and Cueball is talking to her.]
:Cueball: What were things like in the old days?
:Cueball: I hear that you had to ... compile things for different processors?
:Hairbun: Yeah

:[Same setting in a slimmer panel, now Hairbun is replying.]
:Hairbun: To compile your code, you had to mail it to IBM.
:Hairbun: It took 4-6 weeks.

:[Close-up of Hairbun from the waist up.]
:Hairbun: Before garbage collection, data would pile up until the computer got full and you had to throw it away.

:[Same setting as in the first panel with Hairbun gesturing toward Cueball raising one hand palm up.]
:Hairbun: Early compilers could handle code fine, but comments had to be written in assembly.

:[In a frame-less panel Hairbun is seen from the front, with both arms out to the side with both hands held palm up.]
:Hairbun: '''C''' could only be written on punch cards.You had to pick a compact font, or you'd only fit a few characters per card.

:[Exactly the same setting as the first panel, but with Hairbun doing the talking.]
:Hairbun: '''C++''' was big because it supported floppy disks.
:Hairbun: It still punched holes in them, but it was a start.
:Cueball: Wow.

{{comic discussion}}

[[Category:Comics featuring Cueball]]
[[Category:Comics featuring Hairbun]]
[[Category:Old Days]]
[[Category:Comics sharing name|Old Days]]
[[Category:Programming]]

303: Compiling

2022-09-27T11:40:17Z

Graham87: /* Explanation */ copyedit

{{comic
| number = 303
| date = August 15, 2007
| title = Compiling
| image = compiling.png
| titletext = 'Are you stealing those LCDs?' 'Yeah, but I'm doing it while my code compiles.'
}}

==Explanation==
Computer programming involves writing instructions for a computer to follow, in a specific {{w|programming language}}, which is largely human readable and writable, at least to programmers who understand that language. However, for the computers to follow instructions, they need to be given {{w|machine code}} — the actual "language" that computers "speak" and one that ''can'' be written directly with the correct tools, but would be too tedious and error-prone for just about any practical modern project where alternatives exist, where anything more than a {{w|%22Hello,_World!%22_program|Hello World}} could be awkward to implement straight into machine-code.

Conversion from the more conveniently human-writable code into {{w|computer-executable files}} is performed by {{w|Assembly language#Assembler|assemblers}}, {{w|Interpreter_(computing)|interpreters}}, or {{w|compilers}}.

Programs can be written in {{w|Assembly language|assembly code}}, which is basically just a set of mnemonics that make machine code much easier for a human to remember and correctly parse; the human-written assembly code is then run through a simple assembler to convert it directly into machine code. Assembly coding is necessary whenever one is programming for a completely new architecture (one for which no other tools yet exist), and is still used in some other situations (as it allows the code to be optimized more closely for the system on which it is to run than is possible with other types of coding), but is still fairly tedious and error-prone, and assembly code needs to be completely rewritten if one wants to port it to a computer with a different architecture.

An interpreter (e.g. that for {{w|PHP}} for one example) generally reads through the code, or script, each line at a time as and when required, and has to do a lot of work with various processing overheads and the risk of hitting an invalid instruction or mistake in syntax that it can't handle. It also requires that a relevant version of the interpreter exist on any machine that has to run the script and perhaps some additional knowledge by the end-user.

For widely distributed (and especially commercial) programs, some form of compilation will instead be used. Compiling may have just one computer system read through the man-written code and (barring errors) produces the equivalent stand-alone and direct machine-readable code, suitable for a given range of computers. This process might involve several passes to check for 'obvious' errors in the code, as well as converting some programming concepts that are easiest for humans to understand into equivalent concepts that may be far easier for the computer to work with.

As such, compiling takes a certain amount of time at the time of production. Normally, this takes a few seconds, but, depending on the size of the project and the power of the computer doing the compilation, the time required to compile a program may measure in minutes, or even hours. As of 2015, the {{w|Linux Kernel}} contains over 19 million lines of code, arguably a massive job for any compiler, but if done correctly, it saves time for all the people who will ultimately be using its output.

Thus, when Cueball is caught wasting time at work, he argues that such activities are not worse than any other possible ones, at this moment. If his job is writing code and compiling it, then there may be nothing else that he ''can'' do right now. He cannot usefully tweak the code before it finishes compiling and the expected result checked.

The title text takes this a step further. Cueball claims that ''all'' activities are equally benign while the code is compiling — and that includes committing illegal acts, such as stealing {{w|LCD}}s.

Nine years after this comic was released, [[Randall]] made a comic called [[1755: Old Days]] about how compiling worked in the old days. It was Cueball who asked. The next comic after that, [[1756: I'm With Her]], was released the Monday before the {{w|2016 United States presidential election}}. And in that comic, a Cueball with a sword on an office chair like in this comic is featured. It seems realistic that Randall had that politically loaded comic ready for some time, and when finding and deciding to use this old version of Cueball, he may have been inspired by the compiling theme to make Old Days.

==Transcript==
:The #1 Programmer Excuse for Legitimately Slacking Off: "My code's compiling."
:[Two programmers are sword-fighting on office chairs in a hallway. An unseen manager calls them back to work through an open office door.]
:Manager: Hey! Get back to work!
:Cueball: Compiling!
:Manager: Oh. Carry on.

==Trivia==
*A T-shirt based on this comic is available in the [https://store.xkcd.com/products/compiling xkcd store].
*This comic is available as a signed print in the [https://store.xkcd.com/products/signed-prints xkcd store].

{{comic discussion}}
[[Category:Comics featuring Cueball]]
[[Category:Programming]]
[[Category:Comics with xkcd store products]]

978: Citogenesis

2022-08-13T04:06:42Z

Graham87: /* Explanation */ grammar

{{comic
| number = 978
| date = November 16, 2011
| title = Citogenesis
| image = citogenesis.png
| titletext = I just read a pop-science book by a respected author. One chapter, and much of the thesis, was based around wildly inaccurate data which traced back to... Wikipedia. To encourage people to be on their toes, I'm not going to say what book or author.
}}

==Explanation==
This comic is calling into question the {{w|reliability of Wikipedia}}. This is a favorite pastime of librarians, teachers, and professional researchers, and not usually one of [[Randall]]'s. {{w|Wikipedia}} is a free and freely editable encyclopedia that aims to become a comprehensive, {{w|Wikipedia:Wikipedia in brief|neutral compilation of verifiable and established facts}}. Wikipedia aims to provide only facts backed by {{w|Wikipedia:Identifying reliable sources|reliable sources}}. However, this comic strip details a process in which Wikipedia can not only spread misinformation but make said misinformation seem reliable through a process of "circular reporting".

The title of the comic is a play on the word [http://www.merriam-webster.com/medical/cytogenesis cytogenesis]. Cytogenesis is the formation of cells and their development. {{w|Citogenesis}}, on the other hand, is a [http://www.merriam-webster.com/dictionary/portmanteau portmanteau] of 'Citation' and 'Genesis'. A {{w|Citation}} is a reference to a source, used to back up a specific claim, and [http://mw1.merriam-webster.com/dictionary/genesis?show=1&t=1346949206 genesis] means the origin of something. By extension, citogenesis is the creation of text in a reliable source that can be cited to back up a claim.

In the process described here, someone adds an untrue, but plausible-sounding claim to an article in Wikipedia. A writer for some publication sees the information on Wikipedia and adds it to an article, without bothering to check the sources. The strip describes the writer as "rushed", and in this example, the information likely seems of small enough consequence that she may not have considered that someone might have made it up. Eventually, someone notices the claim in the published source and cites it in the Wikipedia article. The citation now gives the claim credence, as readers don't realize that the official source was based on the Wikipedia article. Thanks to this citation, other reporters, slightly more cautious than the first, consider this bit of information to be reliable and then cite it in articles of their own. Those articles then get cited in Wikipedia, making the claim seem more reliable, encouraging even more reporters (and possibly reporters from more reputable outlets) to believe it and repeat the claim. Eventually, a long list of citations is available, giving an impression of consensus, even though all of it originated with a single article, which was based on an uncited Wikipedia edit.

Four years before, Randall [http://en.wikipedia.org/w/index.php?title=Talk:Xkcd&diff=162077300 commented on Wikipedia] about that process happening to him (on a minor detail), which probably indicates the inception of this comic:
<blockquote>''I've never referred to the [[1: Barrel - Part 1|boy in the barrel]] as "Barrel Lad" -- that seems to have started in this [Wikipedia] article. I've called him "Barrel boy" or "The boy in the barrel". Minor detail, but it's funny how sometimes something can appear on Wikipedia, get referenced in other places, and then Wikipedia cites those other places as supporting references. Hooray {{w|Wikipedia in culture#Wikiality|Wikiality}}!'' — Randall Munroe as user "xkcd", [http://en.wikipedia.org/wiki/Talk:Xkcd/Archive_2#Notes_from_the_author en.wikipedia.org/wiki/Talk:Xkcd#Notes_from_the_author], 3 October 2007</blockquote>

In turn, Randall originated the untrue assertion in this comic that {{w|Steven Chu}}, a physicist, and at the time of the strip the U.S. Secretary of Energy, invented the {{w|Scroll lock}} key, a common button on computer keyboards. Since most people are aware of the scroll lock key but know little about its function or origins, this false information would make for an interesting piece of trivia that would likely spread very quickly.

Following this comic, the actual {{w|Scroll Lock}} and {{w|Steven Chu}} articles {{w|Talk:Scroll_Lock#Thanks_Randall|were}} {{w|Talk:Steven_Chu#Scroll_lock_key|both}} vandalized by "helpful" editors trying to project Randall's reality on Wikipedia. As of May 2022, the Wikipedia article on {{w|Citogenesis}} redirects to the "{{w|Circular reporting#Circular reporting on Wikipedia|Circular reporting on Wikipedia}}" section on the article "{{w|Circular reporting}}". The section credits the term "citogenesis" to Randall Munroe, with a citation linking to this comic. To make matters even more surreal, a Wikipedia editor [https://en.wikipedia.org/w/index.php?title=Reliability_of_Wikipedia&diff=517901534&oldid=517901176 once flagged] the link to this xkcd comic as "Dubious - The material near this tag is possibly inaccurate or non-factual."!

We haven't seen a book like the one Randall describes in the title text. But one example of the misuse of Wikipedia by "reliable sources" concerns the former German minister {{w|Karl-Theodor zu Guttenberg}}. His complete name contains fifteen names/words and reads: Karl-Theodor Maria Nikolaus Johann Jacob Philipp Franz Joseph Sylvester Freiherr von und zu Guttenberg. An anonymous user added one more ("Wilhelm") to the German Wikipedia, just the evening before Karl-Theodor zu Guttenberg was presented as the new Federal Minister of Economics and Technology on February 10, 2009. The next day many major German newspapers published this wrong name ([http://translate.google.com/translate?sl=de&tl=en&js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&u=http%3A%2F%2Fwww.bildblog.de%2F5704%2Fwie-ich-freiherr-von-guttenberg-zu-wilhelm-machte%2F translation of bildblog.de]).

==Transcript==
:Where Citations Come From:
:Citogenesis Step #1
:Through a convoluted process, a user's brain generates facts. These are typed into Wikipedia.
:[Hairy sits at a desk, typing on a laptop.]
:Hairy: (typing) The "scroll lock" key was was designed by future Energy Secretary Steven Chu in a college project.

:Step #2
:A rushed writer checks Wikipedia for a summary of their subject.
:[Ponytail sits at a desk, typing on a desktop.]
:Ponytail: (typing) US Energy Secretary Steven Chu, (Nobel Prizewinner and creator of the ubiquitous "scroll lock" key) testified before Congress today...

:Step #3
:Surprised readers check Wikipedia, see the claim, and flag it for review. A passing editor finds the piece and adds it as a citation.
:[Cueball sits on a couch with a laptop in his lap, typing.]
:Cueball: Google is your friend, people. (typing) <nowiki><ref>{{cite web|url=</nowiki>

:Step #4
:Now that other writers have a real source, they repeat the fact.
:[A flow chart, with "Wikipedia citation" in the center. The word "Wikipedia" is in black, the word "citations" is white with a red background.
:[A black arrow leads from "brain" to "Wikipedia."]
:[A black arrow labeled "words" leads from "Wikipedia" to "careless writers," and a red arrow labeled "citations" leads back to "Wikipedia citations."]
:[A black & red arrow leads from "Wikipedia" to "cited facts" which leads to "slightly more careful writers," which leads to "more citations," which leads back to :"Wikipedia" (all black & red arrows).]
:References proliferate, completing the citogenesis process.

==Trivia==
* The word "was" occurs twice consecutively in the first panel.

{{comic discussion}}
[[Category:Comics featuring Cueball]]
[[Category:Comics featuring Ponytail]]
[[Category:Flowcharts]]
[[Category:Wikipedia]]
[[Category:Comics with color]]

806: Tech Support

2022-07-16T11:52:39Z

Graham87: /* Explanation */ copyedit

{{comic
| number = 806
| date = October 15, 2010
| title = Tech Support
| image = tech support.png
| titletext = I recently had someone ask me to go get a computer and turn it on so I could restart it. He refused to move further in the script until I said I had done that.
}}

==Explanation==
[[Cueball]] runs into some problems with his network connection and contacts his Internet service provider's (ISP's) tech support for help. The customer service agent (represented by [[Hairy]]) is not very helpful, giving clearly pre-scripted advice that has nothing to do with Cueball's problem. Cueball gives up and asks to speak to an engineer, i.e. someone more knowledgeable about the technology and suggest to Hairy what to look for. Noticing a woman with black ponytail who has the stuffed {{w|Tux_(mascot)|Tux}} penguin on her desk and a poster of a bearded dude with swords (a reference to {{w|Richard Stallman}} particularly as he stands in [[345: 1337: Part 5]], and a reference to [[225: Open Source]]) he tells Cueball about her and Cueball recognizes the signs of a {{w|GNU}}/{{w|Linux}} geek and asks to talk to her. Hairy transfers him over to the engineer, who immediately recognizes the problem and fixes it. Then she tells him of a secret word (shibboleet - see below) which, if he speaks on the phone, will transfer him to a tech-savvy person able to help him, something installed already back in the 1990's by the geeks of that time. Cueball is elated but then at this point Cueball wakes up and unfortunately discovers the incident to be just a dream.

Poor customer and technical support is a common complaint of many ISPs. Many ISPs {{w|outsourcing|outsource}} their support staff to foreign countries to reduce costs, and/or they delegate first-tier support to workers with little or no training. Typically, these workers are given general scripts that prompt the customer to try common troubleshooting steps, such as restarting the computer, without any specific knowledge of the customer's complaint. While these scripts may help resolve problems for the average customer, a representative using such a script is usually unprepared to assist someone who has a more advanced problem. Furthermore, these scripts generally assume that the problem is on the customer's end and do not acknowledge problems that occur within the ISP, such as server or line problems.

Customers like Cueball in this comic often find it frustrating to deal with representatives reading from scripts. As [[Randall]] mentions in the title text, this frustration is magnified when the representative refuses to move on to the next step until the customer has performed the previous one, whether or not it is necessary or helpful. In cases like this, it's often necessary to request an escalation to a higher "tier" of support, or to speak to a supervisor who presumably has more knowledge and/or influence, though even that can sometimes be a painful process. Thus, it is easy to see why Cueball would be elated to discover a way to automatically connect with the most helpful technical support representatives whenever he has a problem, and thus also why he get really disappointed when he realizes it was just a dream (dreams being a [[:Category:Dreams|recurring theme]] in xkcd).

Cueball is running {{w|Haiku (operating system)|Haiku}}, an {{w|open source}} operating system which is still in a state of active development, being in an alpha release at the publishing of the comic and in beta since 2018. While low-level tech support operators are given scripts which are predicated on the assumption that many computer problems are actually caused by the actions of clueless end users (as, in fact, they are), it's exceedingly unlikely most of these first-tier operators would have even heard of Haiku, not to mention that their scripts' assumptions would never apply to the sort of person who would be using an experimental OS as opposed to {{w|Windows}}, for instance.

"Shibboleet" is a portmanteau of "shibboleth" and "leet". A "{{w|shibboleth}}" means any word, custom, or other signifier which is used by members of a group to recognize other members or those who are "in the know" about something. Its use originates in the Hebrew Bible, where the precise pronunciation of this word was used to distinguish Gileadites from Ephramites. {{w|Leet}} (based on the word "elite") refers to "leet-speak", a practice of character substitution and abbreviation common across the Internet (or "teh 1n73rn3t", as you would say in leet). Thus, "shibboleet" is a shibboleth used to identify someone whose computer-knowledge is "elite." Leet is again in leet written as 1337 so again a reference back to the [[:Category:1337|1337 comic series]] including the comic mentioned above with Stallman.

Randall mentioned in the title text that this had happened to him recently, and is possibly the reason for this comic.

In [[2633: Astronomer Hotline]] a tech support is also asking very silly questions as it is going through a script.

==Transcript==
:[Cueball is on his cellphone, and holding up a small square piece of hardware with a foot in the other hand. Two wires go from the hardware down to the floor, where one is connected to a box on the floor with two black antennas, and then another wire goes out the other side of this, and both this and the second wire from the hardware Cueball is holding goes under his desk, on top of which is his open laptop.]
:Cueball: ...restart my computer? I know you have a script to follow, but the uplink light on the modem is going off every few hours. The problem is between your office and the modem.

:[Zoom in on Cueball's torso, still on the phone and with the hardware in hand.]
:Cueball: My computer has nothing to do with... OK, whatever, I "restarted my computer."
:Cueball: It's still down, and even if it comes back, it's going to die again in a few hours, because your—

:[Cueball on the phone has walked closer to his desk with the laptop, but holds down the hand with the hardware so it is below the panels frame.]
:Cueball: I don't ''have'' a start menu. This is a Haiku install, but that's not import—
:Cueball: Haiku? It's an experimental OS that I ... oh, never mind.

:[Cueball has paced away from his desk to the left so it is no longer in the panel. He has put the hardware down next to the box with antennas on the floor. Wires going off panel right toward the desk.]
:Cueball: I'm sorry, but this won't get fixed until I talk to an engineer. Can you look around for someone wearing cargo pants, maybe a subway map on their wall?

:[Hairy is the tech support person on the other end sitting in an office chair at a desk. A phone is hooked up on his table with two wires coming out. He is wearing a headset. He leans back in the chair and looks behind him to the right. Cueball talks to him over the phone indicated with a zigzag line.]
:Hairy: There's a chick two phones over with a stuffed penguin doll and a poster of some bearded dude with swords.
:Cueball (on the phone): Perfect. Can you put her on?
:Hairy: Sure.

:[The engineer, a woman with black hair in a ponytail, sits in an office chair at her desk typing on her lap top. She also has a headset. Behind her laptop sits a small penguin doll. Cueball talks to her over the phone indicated with zigzag lines.]
:Cueball (on the phone): Hey, so sorry to bother you, but my connection—
:Engineer: Yeah, I see it. Lingering problems from a server move.
:<type type>
:Engineer: Should be fixed now.
:Cueball (on the phone): Thank you ''so much.''

:[Zoom in on the engineers torso. The back of the chair and the top of her laptop just inside the panel.]
:Engineer: No problem. Hey, in the future, if you're on any tech support call, you can say the code word "shibboleet" at any point and you'll be automatically transferred to someone who knows a minimum of two programming languages.

:[Zoom in on Cueball on the phone scratching his neck. The engineer talks to him over the phone indicated with zigzag lines.]
:Cueball: Seriously?
:Engineer (on the phone): Yup. It's a backdoor put in by the geeks who built these phone support systems back in the 1990's.
:Engineer (on the phone): Don't tell anyone.

:[The last panel is split in two sections. In the top part still with a zoom in on Cueball, he takes the phone down to hang up. Only this section is inside a frame. The frame is normal at the top and half way down to the left, but only a small way down on the right side. The bottom part of the frame connects these two normal parts but with a wavy line to indicate that this is the end of a dream. In the frame-less part of the panel below Cueball is sitting up in his bed, having lifted his head fro the pillow behind him to the left. He lifts him self up with one hand while the other takes the sheet down over his body. The last part it thus drawn outside the rest of the framed part of the comic.]
:Cueball: Oh my god, this is the greatest—

:Cueball: Wha—
:Cueball: ...''Dammit.''

{{comic discussion}}

[[Category:Comics featuring Cueball]]
[[Category:Comics featuring Hairy]]
[[Category:Comics featuring Richard Stallman]] 
[[Category:Computers]]
[[Category:Dreams]]
[[Category:Portmanteau]]
[[Category:Engineering]]

1311: 2014

2022-03-16T09:26:42Z

Graham87: /* Additional information */ copyedit

<noinclude>:''This page refers to the comic named "2014". For comic #2014, see [[2014: JWST Delays]].''</noinclude>
{{comic
| number = 1311
| date = January 1, 2014
| title = 2014
| before = [[#Explanation|↓ Skip to explanation ↓]]
| image = 2014.png
| titletext = Some future reader, who may see the term, without knowing the history of it, may imagine that it had reference to some antiquated bridge of the immortal Poet, thrown across the silver Avon, to facilitate his escape after some marauding excursion in a neighbouring park; and in some Gentleman's Magazine of the next century, it is not impossible, but that future antiquaries may occupy page after page in discussing so interesting a matter. We think it right, therefore, to put it on record in the Oriental Herald that the 'Shakesperian Rope Bridges' are of much less classic origin; that Mr Colin Shakespear, who, besides his dignity as Postmaster, now signs himself 'Superintendent General of Shakesperian Rope Bridges', is a person of much less genius than the Bard of Avon. --The Oriental Herald, 1825
}}

==Explanation==
This [[:Category:New Year|New Year comic]] is to commemorate the {{w|New Year}} by giving us a view of the coming year (2014) from the past. The comic includes many quotes from the 1800s and early 1900s that speak to a time close to 2014. Many of them are for the twenty-first century in general, and only three mention a year that would be 2014 exactly. All but one of them is a prediction, yet some of these are quotes from fictional literature, and therefore are not true predictions. Words are in boldface to highlight the relevant content in the quote. The grey or non-bold text is non-essential to the point Randall is interested in, and only to be used to understand the context of the quote.

The title text refers to a certain British officer, Mr. Colin Shakespeare, who experimented with and [http://books.google.com/books?id=aZRPAAAAYAAJ&pg=PA367 promoted the use of rope suspension bridges in India.] The reference to "The Bard of Avon" is a reference to {{w|William Shakespeare|Shakespeare (the playwright)}}, as {{w|River Avon (Warwickshire)|Avon}} is the river on which {{w|Stratford upon Avon}} is set, and is where the playwright was born and spent his youth. The author of this quote under the guise of eliminating the potential confusion that might result after decades or centuries have washed away the context, ironically and possibly vindictively, makes a point to note that the bridge is not named after the playwright, but Mr. Colin Shakespeare, whom he considers considerably less intelligent. This topic was previously covered in [[771: Period Speech]].

Two years before, another New Years comic with just the new years number as the title was released: [[998: 2012]]. But actually the content of this comic is more related to the comic coming out just before the 2012 comic: [[997: Wait Wait]], which is also a New Year comic, that took a look at what could happen in 2012, just as this one does for 2014... In 2016 another comic, with only the new year as the name theme, occurred again [[1624: 2016]]. For some reason this only seemed to happen in the even years, until [[1779: 2017]] was released, with [[1935: 2018]] being the next one.

The style of the comic is very similar to that of [[1227: The Pace of Modern Life]], which was released half a year earlier.

===Additional information===

{| class="wikitable"
|-
! Quote
! Author or publisher
! Year
! Years realized
! Description
|-
| "It's desirable '''every thing printed should be preserved,''' for we '''cannot now tell how useful it may become''' two centuries hence."
| Christopher Baldwin
| 1834
| Not a prediction
| A good idea. Now, with Google Books, this can be done in an easier manner. Unfortunately, many books that were printed between the mid-19th century and the widespread usage of acid-free wood-pulp paper starting from the early 1990s are either no longer known to exist, are heavily damaged (mostly through deterioration — see {{w|slow fire}}) or are very scarce.
|-
| "I predict that a century hence the '''Canadian people''' will be '''the noblest specimens of humanity on the face of the earth'''"
| Rev John Bredin
| 1863
| Subjective
| Calling the citizens of any nation "the noblest" is difficult to quantify. Canada, in general, has a reputation as a safe, healthy and polite society, but, like any nation, they have both positive and negative qualities. The rest of the quote goes as follows: ''"all that was good in the Celt, the Saxon, the Gaul and other races, combining to form neither English, Irish, nor Welsh, but Canadians, who would take their place among the churches of Christendom and the nations of the earth."'' This religious prediction probably wasn't believed even by its author. It's only a harangue.
|-
| "In the twenty-first century '''mankind will subsist entirely upon jellies.'''"
| The Book Lover
| 1903
| Not yet, but we still have time to do so
| Concentrates, which are gelatin like, form a large part of our food sources. Absurd if taken literally, but if he's talking about processed foods in general then he's not too far off the mark.
|-
| "The twenty-first century baby is destined to be rocked and cradled by electricity, warmed and coddled by electricity, perhaps fathered and mothered by electricity. '''Probably the only thing he will be left to do unaided will be to make love.'''"
| Mrs John Lane, The Fortnightly
| 1905
| 1960s–1980s
| The parameters of this prediction are fairly ambiguous. Certainly, electricity impacts nearly every aspect of modern life, from the time most children are born. While child-rearing is very much a human activity (and parents today arguably spend more time and effort on children than in past eras), electrically powered aids are everywhere. Children are indeed "rocked and cradled" in automatic swings, and "warmed and coddled" by means of electric heaters and incubators (in medical cases). In fact, most aspects of child-rearing can be aided by some electronic gadget or other. As of 2020, no children have been born without biological mothers and fathers, but the process of ''in vitro'' fertilization, in which conception is mediated by technology, has been in use since 1978. As for making love unaided, Mrs. Lane may have underestimated the implications of technology, as there are now a wide range of devices and aides, electronic and otherwise, which are designed to assist in sexual gratification, both with and without partners.
|-
| "To-day, in the city of New York, sixty-six different tongues are spoken. '''A century hence, there will probably be only one.'''"
| The American Historical Magazine
| 1907
| Not realized
| The number of languages spoken in New York City is believed to be greater than 100; some estimate as many as 800 languages are spoken there. The U.S. Census Bureau reports that in the greater New York metropolitan area, almost 7 million people speak a language other than English at home, including over 3.5 million who speak Spanish, 2 million who speak other Indo-European languages, 1 million who speak Asian or Pacific Island languages, and 300,000 who speak other languages. Also, New York City is the location of the headquarters of the United Nations, with diplomats from nearly every country in the world, and several official languages.
|-
| "I often think '''what interesting history we are making for the student of the twenty-first century.'''"
| William Carey Jones
| 1908
| 1900's–present
| Referring to the events that led to {{w|World War I}}. In 1908, {{w|Bosnian crisis|Austria-Hungary annexed Bosnia and Herzegovina}}. This led to the {{w|Assassination of Archduke Franz Ferdinand of Austria|Sarajevo Assassination of Archduke Franz Ferdinand of Austria}} in 1914 that is considered the starting event of the World War.
|-
| "China may be a '''great shoe market''' a decade or a century from now."
| Boot and Shoe Recorder
| 1914
| 1970's–present
| The publication in question appears only interested in footwear, while, in fact, China has become one of the world's largest economies, making it a huge consumer and producer of a full array of products. The range of "a decade or a century from now" makes for a pretty vague prediction. China didn't really qualify as a "great market" for western goods until trade barriers were removed in the 1970's. This was well over a decade from the prediction, but well under a century.
|-
| "'''We cannot settle the problem,''' and I venture the prophecy that perhaps '''a century from now this same question may be brought before some future society and discussed very much as it is tonight.'''
| Dr. Barton C. Hirst (on abortion)
| 1914
| 1914–present
| Abortion is still heavily debated. Various societies have different levels of legal regulation, social stigma, and assumed moral implications, and even within societies there is often not a clear consensus. While laws have changed heavily over the last century, and attitudes have very likely shifted, the debate has certainly not ended, and arguably hasn't substantially changed.
|-
| "By the twenty-first century '''we shall all be telepaths.'''"
| Gumbril, a character in {{w|Aldous Huxley}}'s novel ''{{w|Antic Hay}}''
| 1923
| Not realized
| [http://books.google.com/books?id=pdXj2SZ1mT8C&pg=PA205]: "And it's my firm belief," said Gumbril Senior, adding notes to his epic, "that they [the birds] make use of some sort of telepathy, some kind of direct mind-to-mind communication between themselves. You can't watch them without coming to that conclusion." [...] "It's a faculty," Gumbril Senior went on, "we all possess, I believe. All we animals." [...] "By the twenty-first century, I believe, we shall all be telepaths. Meanwhile, these delightful birds have forestalled us."
|-
| "The physician of the twenty-first century… may even criticize the language of the times, and may find that '''some of our words have become as offensive to him as the term "lunatic" has become offensive to us.'''"
| Dr. C. Macfie Cambell
| 1924
| 1950's–present
| The word "lunatic" is still considered derogatory and because of that it would never be used in a clinical sense. He correctly predicts the trajectory of terms like "{{w|mentally retarded}}", itself adopted by his day to replace earlier terms for the intellectually disabled, such as "moron" and "imbecile", which had become pejorative. Soon enough the word "retard" joined them in that regard, and it has now largely been abandoned as a medical term. This cycle is a common one, known as (among other things) the "{{w|euphemism treadmill}}".
|-
| "Historians of the twenty-first century will look back with well-placed scorn on the '''shallow-minded days''' of the early twentieth century '''when football games and petting parties were considered the most important elements of a college education.'''"
| Mary Eileen Ahern, Library Bureau
| 1926
| Subjective
| This item is likely included somewhat sardonically, because an emphasis on college athletics and wild parties remains an important part of the college experience for many people, and that emphasis is likely at least as common as it was 90 years ago, and probably condemned less often. They're not considered "the most important elements" by most people, either now or then, but many students consider them to be an essential part of being in college. There's little to no evidence that college students have become more studious or less inclined to have fun over the last century.
|-
| "'''In the year A.D. 2014''' journalists will be writing on the centenary of the great war — '''that is, if there has not been a greater war.'''"
| F.J.M, The Journalist
| 1934
| 2014 and 1939 respectively
| At the time of this prediction, {{w|World War I}} was generally referred to as "The Great War". Five years after this prediction was made, {{w|World War II}} began, tragically fulfilling the condition of "a greater war". As bloody and brutal as World War I was, World War II was worse, by almost every possible metric. Journalists definitely wrote articles about World War I on its anniversary, and the war is still remembered and studied, but it has very certainly been overshadowed in most of the world by the "greater war".
|}

==Transcript==
:(This is a series of quotes from various people of various timeframes. Each quote is followed by the author, the document of publication if applicable, and the year.)

:'''Notes from the past'''

:It's desirable '''every thing printed should be preserved,''' for we '''cannot now tell how useful it may become''' two centuries hence.
::Christopher Baldwin
:::'''1834'''

:I predict that a century hence the '''Canadian people''' will be '''the noblest specimens of humanity on the face of the earth'''
::Rev. John Bredin
:::'''1863'''

:In the twenty-first century '''mankind will subsist entirely upon jellies.'''
::''The Booklover''
:::'''1903'''

:The twenty-first century baby is destined to be rocked and cradled by electricity, warmed and coddled by electricity, perhaps fathered and mothered by electricity. '''Probably the only thing he will be left to do unaided will be to make love.'''
::Mrs. John Lane, ''The fortnightly''
:::'''1905'''

:To-day, in the city of New York, sixty-six different tongues are spoken. '''A century hence, there will probably be only one.'''
::''The American Historical Magazine''
:::'''1907'''

:I often think '''what interesting history we are making for the student of the twenty-first century.'''
::Willian Carey Jones
:::'''1908'''

:China may be a '''great shoe market''' a decade or a century from now.
::''Boot and Shoe Recorder''
:::'''1914'''

:'''We cannot settle the problem,''' and I venture the prophecy that perhaps '''a century from now this same question may be brought before some future society and discussed very much as it is tonight.'''
::Dr. Barton C. Hirst on the subject of '''abortion'''
:::'''1914'''

:By the twenty-first century I believe '''we shall all be telepaths.'''
::Gumbriel, character in ''Antic Hay''
:::'''1923'''

:The physician of the twenty-first century… may even criticize the language of the times, and may find that '''some of our words have become as offensive to him as the term "lunatic" has become offensive to us.'''
::Dr. C. Macfie Campbell
:::'''1924'''

:Historians of the twenty-first century will look back with well-placed scorn on the '''shallow-minded days''' of the early twentieth century '''when football games and petting parties were considered the most important elements of a college education.'''
::Mary Eileen Ahern, ''Library Bureau''
:::'''1926'''

:'''In the year A.D. 2014''' journalists will be writing on the centenary of the great war — '''that is, if there has not been a greater war.'''
::F.J.M, ''The Journalist''
:::'''1934'''

{{comic discussion}}

[[Category:New Year]]
[[Category:Language]]
[[Category:Politics]]
[[Category:American football]]
[[Category:Comics sharing name|2014]]

936: Password Strength

2022-03-05T11:15:21Z

Graham87: rm doubled word

{{comic
| number = 936
| date = August 10, 2011
| title = Password Strength
| image = password strength.png
| titletext = To anyone who understands information theory and security and is in an infuriating argument with someone who does not (possibly involving mixed case), I sincerely apologize.
}}

==Explanation==
This comic says that a password such as "Tr0ub4dor&3" is bad because it is easy for password cracking software and hard for humans to remember, leading to insecure practices like writing the password down on a post-it attached to the monitor. On the other hand, a password such as "correct horse battery staple" is hard for computers to guess due to having more entropy but quite easy for humans to remember.

{{w|Entropy (information theory)|Entropy}} is a measure of "uncertainty" in an outcome. In this context, it can be thought of as a value representing how unpredictable the next character of a password is. It is calculated as ''log2(a^b)'' where ''a'' is the number of allowed symbols and ''b'' is its length.

A truly random string of length 11 (not like "Tr0ub4dor&3", but more like "J4I/tyJ&Acy") has log2(94^11) = 72.1 bits, with 94 being the total number of letters, numbers, and symbols one can choose. However the comic shows that "Tr0ub4dor&3" has only 28 bits of entropy. This is because the password follows a simple pattern of a dictionary word + a couple extra numbers or symbols, hence the entropy calculation is more appropriately expressed with log2(65000*94*94), with 65000 representing a rough estimate of all dictionary words people are likely to choose. (For related info, see https://what-if.xkcd.com/34/).

Another way of selecting a password is to have 2048 "symbols" (common words) and select only 4 of those symbols. log2(2048^4) = 44 bits, much better than 28. Using such symbols was again visited in one of the tips in [[1820: Security Advice]].

It is absolutely true that people make passwords hard to remember because they think they are "safer", and it is certainly true that length, all other things being equal, tends to make for very strong passwords and this can be confirmed by using [http://rumkin.com/tools/password/passchk.php rumkin.com's password strength checker]. Even if the individual characters are all limited to [a-z], the exponent implied in "we added another lowercase character, so multiply by 26 again" tends to dominate the results.

In addition to being easier to remember, long strings of lowercase characters are also easier to type on smartphones and {{w|Virtual keyboard|soft keyboards}}.

xkcd's password generation scheme requires the user to have a list of 2048 common words (log2(2048) = 11). For any attack we must assume that the attacker knows our password generation algorithm, but not the exact password. In this case the attacker knows the 2048 words, and knows that we selected 4 words, but not which words. The number of combinations of 4 words from this list of words is (211)4 = 244, i.e. 44 bits. For comparison, the [http://world.std.com/~reinhold/dicewarefaq.html#calculatingentropy entropy offered by Diceware's 7776 word list is 13 bits per word]. If the attacker doesn't know the algorithm used, and only knows that lowercase letters are selected, the "common words" password would take even longer to crack than depicted. 25 ''random'' lowercase characters would have [http://www.wolframalpha.com/input/?i=log2%2826^25%29 117 bits of entropy], vs 44 bits for the common words list.

;Example
Below there is a detailed example which shows how different rules of complexity work to generate a password with supposed 44 bits of entropy. The examples of expected passwords were generated in random.org.(*)

If ''n'' is the number of symbols and ''L'' is the length of the password, then ''L'' = 44 / log2(n).

{|class="wikitable"
!Symbols
!Number of symbols
!Minimum length
!colspan="2"|Examples of expected passwords
!Example of an actual password
!Actual bits of entropy
!Comment
|-
|a||26||9.3||mdniclapwz||jxtvesveiv||troubadorx||16+4.7 = 20.7||Extra letter to meet length requirement; log2(26) = 4.7
|-
|rowspan="2"|a 9
|rowspan="2"|36
|rowspan="2"|8.5
|rowspan="2"|qih7cbrmd
|rowspan="2"|ewpltiayq
|tr0ub4d0r||16+3=19||3 = common substitutions in the comic
|-
|troubador1||16+3.3=19.3||log2(10) = 3.3
|-
|a A||52||7.7||jAwwBYne||NeTvgcrq||Troubador||16+1=17||1 = caps? in the comic
|-
|a &||58||7.5||j.h?nv),||c/~/fg\:||troubador&||16+4=20||4 = punctuation in the comic
|-
|a A 9||62||7.3||cDe8CgAf||RONygLMi||Tr0ub4d0r||16+1+3=20||1 = caps?; 3 = common substitutions
|-
|a 9 &||68||7.2||_@~"#^.2||un$l|!f]||tr0ub4d0r&||16+3+4=23||3 = common substitutions; 4 = punctuation
|-
|a A 9 &||94||6.7||Re-:aRo||^$rV{3?||Tr0ub4d0r&||16+1+3+4=24||1 = caps?; 3 = common substitutions; 4 = punctuation
|-
|rowspan="2"|common words
|rowspan="2"|2048
|rowspan="2"|4
|rowspan="2"|reasonableretailsometimespossibly
|rowspan="2"|constantyieldspecifypriority||reasonableretailsometimespossibly||11×4=44||Go to random.org and select 4 random integers between 1 and 2048; then go to your list of common words
|-
|correcthorsebatterystaple
|1
|Thanks to this comic, this is now one of the first passwords a hacker will try. The only entropy left is a boolean statement: "Is this password correcthorsebatterystaple, yes or no?"
|}

:a = lowercase letters
:A = uppercase letters
:9 = digits
:& = the 32 special characters in an American keyboard; Randall assumes only the 16 most common characters are used in practice (4 bits)

:(*) The use of random.org explains why <code>jAwwBYne</code> has two consecutive w's, why <code>Re-:aRo</code> has two R's, why <code>_@~"#^.2</code> has no letters, why <code>ewpltiayq</code> has no numbers, why "constant yield" is part of a password, etc. A human would have attempted at passwords that looked random.

==People who don't understand information theory and security==

The title text likely refers to the fact that this comic could cause people who understand information theory and agree with the message of the comic to get into an infuriating argument with people who do not — and disagree with the comic.

If you're confused, don't worry; you're in good company; even security "experts" don't understand the comic:

* Bruce Schneier thinks that dictionary attacks make this method "obsolete", despite the comic ''assuming'' perfect knowledge of the user's dictionary from the get-go. He advocates his own low-entropy "first letters of common plain English phrases" method instead: [https://www.schneier.com/blog/archives/2014/03/choosing_secure_1.html#!s!xkcd Schneier original article] and rebuttals: [https://web.archive.org/web/20160305001236/http://robinmessage.com/2014/03/why-bruce-schneier-is-wrong-about-passwords/ 1] [http://security.stackexchange.com/a/62881/10616 2] [http://www.reddit.com/r/technology/comments/1yxgqo/bruce_schneier_on_choosing_a_secure_password/cfp2z9k 3] [http://www.reddit.com/r/YouShouldKnow/comments/232uch/ysk_how_to_properly_choose_a_secure_password_the/cgte7lp 4] [http://www.reddit.com/r/YouShouldKnow/comments/232uch/ysk_how_to_properly_choose_a_secure_password_the/cgszp62 5] [http://www.reddit.com/r/YouShouldKnow/comments/232uch/ysk_how_to_properly_choose_a_secure_password_the/cgt6ohq 6]
* Steve Gibson basically gets it, but calculates entropy incorrectly in order to promote his own method and upper-bound password-checking tool: [https://www.grc.com/sn/sn-313.htm#!s!math%20is%20wrong Steve Gibson Security Now transcript] and [https://subrabbit.wordpress.com/2011/08/26/how-much-entropy-in-that-password/ rebuttal]
* Computer security consultant Mark Burnett ''almost'' understands the comic, but then advocates adding numerals and other crud to make passphrases less memorable, which completely defeats the point (that it is human-friendly) in the first place: [https://web.archive.org/web/20150319220514/https://xato.net/passwords/analyzing-the-xkcd-comic/ Analyzing the XKCD Passphrase Comic]
* Ken Grady incorrectly thinks that user-selected sentences like "I have really bright children" have the same entropy as randomly-selected words: [https://www.hellersearch.com/blog/bid/141527/is-your-password-policy-stupid Is Your Password Policy Stupid?]
* Diogo Mónica is correct that a truly random 8-character string is still stronger than a truly random 4-word string (52.4 vs 44), but doesn't understand that the words have to be truly random, not user-selected phrases like "let me in facebook": [https://diogomonica.com/posts/password-security-why-the-horse-battery-staple-is-not-correct/ Password Security: Why the horse battery staple is not correct]
* Ken Munro confuses entropy with permutations and undermines his own argument that "correct horse battery staple" is weak due to dictionary attacks by giving an example "strong" password that still consists of English words. He also doesn't realize that using capital letters in predictable places (first letter of every word) does not increase password strength: [https://www.pentestpartners.com/security-blog/correcthorsebatterystaple-isnt-a-good-password-heres-why/ CorrectHorseBatteryStaple isn’t a good password. Here’s why.]

Sigh. 🤦‍♂️

==Transcript==
:The comic illustrates the relative strength of passwords assuming basic knowledge of the system used to generate them.
:A set of boxes is used to indicate how many bits of entropy a section of the password provides.
:The comic is laid out with 6 panels arranged in a 3x2 grid.
:On each row, the first panel explains the breakdown of a password, the second panel shows how long it would take for a computer to guess, and the third panel provides an example scene showing someone trying to remember the password.

:[The password "Tr0ub4dor&3" is shown in the center of the panel. A line from each annotation indicates the word section the comment applies to.]

:Uncommon (non-gibberish) base word
:[Highlighting the base word - 16 bits of entropy.]
:Caps?
:[Highlighting the first letter - 1 bit of entropy.]
:Common Substitutions
:[Highlighting the letters 'a' (substituted by '4') and both 'o's (the first of which is substituted by '0') - 3 bits of entropy.]
:Punctuation
:[Highlighting the symbol appended to the word - 4 bits of entropy.]
:Numeral
:[Highlighting the number appended to the word - 3 bits of entropy.]
:Order unknown
:[Highlighting the appended characters - 1 bit of entropy.]
:(You can add a few more bits to account for the fact that this is only one of a few common formats.)

:~28 bits of entropy
:228 = 3 days at 1000 guesses/sec
:(Plausible attack on a weak remote web service. Yes, cracking a stolen hash is faster, but it's not what the average user should worry about.)
:Difficulty to guess: Easy

:[Cueball stands scratching his head trying to remember the password.]
:Cueball: Was it trombone? No, Troubador. And one of the O's was a zero?
:Cueball: And there was some symbol...
:Difficulty to remember: Hard

:[The passphrase "correct horse battery staple" is shown in the center of the panel.]
:Four random common words {Each word has 11 bits of entropy.}

:~52 bits of entropy
:244 = 550 years at 1000 guesses/sec
:Difficulty to guess: Hard

:[Cueball is thinking, in his thought bubble a horse is standing to one side talking to an off-screen observer. An arrow points to a staple attached to the side of a battery.]
:Horse: That's a battery staple.
:Observer: ''Correct!''
:Difficulty to remember: You've already memorized it

:Through 20 years of effort, we've successfully trained everyone to use passwords that are hard for humans to remember, but easy for computers to guess.

==External links==
*An [https://en.wikipedia.org/wiki/Request_for_Comments RFC], RFC7997 ''The Use of Non-ASCII Characters in RFCs'', uses "Correct Horse Battery Staple" in ''Table 3: A sample of legal passwords'' on page 10.[https://www.rfc-editor.org/rfc/pdfrfc/rfc7997.txt.pdf#page=10]
*Some info was used from the highest voted answer given to the question of "how accurate is this XKCD comic" at StackExchange [http://security.stackexchange.com/questions/6095/xkcd-936-short-complex-password-or-long-dictionary-passphrase].
*Similarly, a question of "how right this comic is" was made at AskMetaFilter [http://ask.metafilter.com/193052/Oh-Randall-you-do-confound-me-so] and [[Randall]] responded [http://ask.metafilter.com/193052/Oh-Randall-you-do-confound-me-so#2779020 there].
*Also the Wikipedia article on '{{w|Passphrase}}' is useful.
*In case you missed it in the explanation, GRC's Steve Gibson has a fantastic page [https://www.grc.com/haystack.htm] about this (and may have prompted this comic, as his podcast [http://www.grc.com/sn/sn-303.htm] about this was posted the month before this comic).
* This comic inspired [http://blog.acolyer.org/2015/10/29/how-to-memorize-a-random-60-bit-string/ How to memorize a random 60-bit string] scientific paper (link is to the article about paper, wth paper itself linked)
* [https://github.com/dropbox/zxcvbn zxcvbn password strength estimator] thanks this comic for the inspiration in acknowledgements.
* CMU paper: [http://cups.cs.cmu.edu/soups/2012/proceedings/a7_Shay.pdf Correct horse battery staple: Exploring the usability of system-assigned passphrases]
* [http://research.microsoft.com/pubs/265143/Microsoft_Password_Guidance.pdf Microsoft Password Guidance] (page 8)
* [http://gizmodo.com/the-guy-who-invented-those-annoying-password-rules-now-1797643987 The Guy Who Invented Those Annoying Password Rules Now Regrets Wasting Your Time], August 8, 2017 (this comic is reproduced in the article).

{{comic discussion}}
[[Category:Comics featuring Cueball]]
[[Category:Math]]
[[Category:Computers]]
[[Category:Psychology]]
[[Category:Computer security]]

1172: Workflow

2022-03-02T15:44:28Z

Graham87: copyedit

{{comic
| number = 1172
| date = February 11, 2013
| title = Workflow
| image = workflow.png
| titletext = There are probably children out there holding down spacebar to stay warm in the winter! YOUR UPDATE MURDERS CHILDREN.
}}

==Explanation==
Users will often try to work around bugs in software, and are sometimes able to get used to having the bugs around. Some bugs are even interpreted as features and users complain when the software authors fix them. This phenomenon has been named [https://www.hyrumslaw.com/ Hyrum's law]: the law states that whatever the official feature list actually says, if a program has enough users, eventually every feature (whether intentional, unintentional, or a bug) will be relied upon by someone. A similar effect may be caused by other improvements, particularly those which involve changes in the [https://www.explainxkcd.com/wiki/index.php/1770 user interface].

This comic shows a somewhat extreme example. An unnamed application had a bug causing the CPU to overheat whenever the spacebar was held down too long. In version 10.17, this bug was fixed. Soon, LongtimeUser4 complained that they relied on the fact that the CPU overheats if the spacebar is held down. They had stumbled across this "feature" (which is, again, weirder than usual) and took advantage of it to streamline their workflow, and they wanted an option to re-enable it.

{{w|Emacs}} (name originally derived from ''E''ditor ''MAC''ro''S'') is a text editor originally written at MIT in 1976 and adopted into the GNU project in 1984. The control key sees extensive use in Emacs, and since it's hard to reach, users often remap it to Caps Lock or some other key. LongtimeUser4 fixed the problem very clumsily ("horrifying," as the admin puts it) and is annoyed that their {{w|kludge}} no longer works. The moral of the story is that you can't please everyone.

Examples of real life changes in software which, though often acclaimed by critics, caused great annoyance among the existing user base include ribbons introduced in Microsoft Office 2007 and the Start screens of both Windows 8 and Unity desktop manager bundled with Ubuntu from versions 11.10 through 17.04. In the latter case, developers included an option to use the older interface; for the rest, applications emulating old behavior were developed by third parties.

The title text makes a hyperbole to humorous effect; children will freeze to death during the winter because they won't be warmed by a rather unconventional heater. Making (or creating an illusion of) a connection between one's opinion and {{tvtropes|ThinkOfTheChildren|care for children's welfare}} is a common method of gaining public support, as such arguments are hard to deflect without sounding cruel and uncaring. "holding down spacebar to stay warm" could also be a reference to {{w|space heater}}s.

==Transcript==
:[Changelog for version 10.17 of a piece of software.]
:One change listed: "The CPU no longer overheats when you hold down the spacebar"
:Comments: LongtimeUser4 writes: This update broke my workflow! My control key is hard to reach, so I hold spacebar instead, and I configured Emacs to interpret a rapid temperature rise as "control".
:Admin writes: That's horrifying.
:LongtimeUser4 writes: Look, my setup works for me. Just add an option to reenable spacebar heating.

:Every change breaks someone's workflow.

{{comic discussion}}
[[Category:Computers]]
[[Category:Emacs]]