explain xkcd - User contributions [en]

Talk:1957: 2018 CVE List

2018-02-19T13:11:15Z

Domino: Request for comic lookups to be added to table

[[First]] post!!!!!!!!!!!!!!!!!!!!!!!!!!! Anyway, the explanation looks like a train wreck, and I'm not sure if a rearranging it into a table or just adding bullet points to everything is better. I'm guessing that a table would be better, but I don't know how I can rearrange it. Can somebody help? [[User:Herobrine|Herobrine]] ([[User talk:Herobrine|talk]]) 06:35, 19 February 2018 (UTC)
: Added a table layout to the sandbox. Might be of some use to another editor. [[Special:Contributions/162.158.74.45|162.158.74.45]] 07:32, 19 February 2018 (UTC)
: ''Edit: Looks like it's been adapted in; I've cleared the sandbox for future use.'' [[Special:Contributions/162.158.74.45|162.158.74.45]] 11:53, 19 February 2018 (UTC)
:: Thanks, I think a table is a good way to go. I'm adding it to the article as a place to start. Rather than format the original explanation into the table, I'm leaving the cells blank. The original poorly formatted text can be a starting point, but isn't directly adaptable. --[[User:Quantum7|Quantum7]] ([[User talk:Quantum7|talk]]) 09:55, 19 February 2018 (UTC)
Never ever have I heard anyone pronounce SQL as "sequel" - Is that a reqional dialect? [[Special:Contributions/162.158.93.15|162.158.93.15]] 07:41, 19 February 2018 (UTC)
: I heard it's common among MS-SQL users.--[[Special:Contributions/162.158.91.137|162.158.91.137]] 08:02, 19 February 2018 (UTC)
:: Oh BTW, look at our IPs. Are you an easybell customer? :-) --[[Special:Contributions/162.158.91.137|162.158.91.137]] 08:09, 19 February 2018 (UTC)
: Some people pronounce it that way, yes. Don't know if it is "common among MS-SQL users", though. The only person I encountered saying "sequel" never used MS-SQL. [[User:LordHorst|LordHorst]] ([[User talk:LordHorst|talk]]) 09:54, 19 February 2018 (UTC)

I want to take a moment to congratulate the dedication of whomever wrote the original explanation. Second languages are hard, bro. [[Special:Contributions/108.162.215.10|108.162.215.10]] 07:48, 19 February 2018 (UTC)

Has someone tried contacting Randall about "extploit"? If not, what would be the best way? [[User:Fabian42|Fabian42]] ([[User talk:Fabian42|talk]]) 08:22, 19 February 2018 (UTC)
:Hack his computer to display a message demanding he fix it if he wants his hard drive decrypted.[[Special:Contributions/162.158.155.26|162.158.155.26]] 09:24, 19 February 2018 (UTC)
::Thanks, will do.

::how to hack complooter
::why does google not work
::how to delete text
::[[User:Fabian42|Fabian42]] ([[User talk:Fabian42|talk]]) 09:44, 19 February 2018 (UTC)

Regarding "Factor a prime": Factoring a prime is easy: The prime itself is the only factor, so it's sufficient to use [https://en.wikipedia.org/wiki/AKS_primality_test AKS] or whatever to check that. Public-key encryption relies on how hard it is to factor the product of two primes, which is a much harder problem. Maybe this is a typo in the comic?
: I don't think it is a typo. It's exactly the type of "inside-joke" I would expect from XKCD. :)
:--[[Special:Contributions/162.158.134.214|162.158.134.214]] 10:09, 19 February 2018 (UTC)
:: AFAIK, there aren't any primality tests known to run in O(log n). For instance, AKS runs in O(log n ^ 7.5). So for numpy to actually achieve factoring as stated would require assuming the input is prime and just returning (1,n). --[[User:Quantum7|Quantum7]] ([[User talk:Quantum7|talk]]) 12:45, 19 February 2018 (UTC)

Can I edit some spelling errors? There seems to be some spelling errors here and there.Boeing-787lover 10:19, 19 February 2018 (UTC)
:Of course, that's what a Wiki is for. [[User:Fabian42|Fabian42]] ([[User talk:Fabian42|talk]]) 12:10, 19 February 2018 (UTC)
I think the explanation of the one about injecting arbitrary text onto a page with the comments box is overthinking the joke. I think it really is just about the fact that you can write whatever you like in a comment. Look, I just hacked this page to display the word "penguin". [[User:Jeremyp|Jeremyp]] ([[User talk:Jeremyp|talk]]) 10:26, 19 February 2018 (UTC)

Since when is Bruce Schneier not real? [[Special:Contributions/162.158.93.75|162.158.93.75]] 13:05, 19 February 2018 (UTC)

I've added some clarification to the "CRITICAL" item. I know there are several xkcd comics referencing similar problems but I unfortunately don't have the time to look them up, can someone do that and link them appropriately in the table? [[User:Domino|Domino]] ([[User talk:Domino|talk]]) 13:11, 19 February 2018 (UTC)domino

1957: 2018 CVE List

2018-02-19T13:08:00Z

Domino: Added a lot of detail to several of the table items

{{comic
| number = 1957
| date = February 19, 2018
| title = 2018 CVE List
| image = 2018_cve_list.png
| titletext = CVE-2018-?????: It turns out Bruce Schneier is just two mischevious kids in a trenchcoat.
}}

==Explanation==
{{incomplete|Created by HACKING THIS WIKI VIA THE EDIT BOX - The explanation looks like a list. Explain the comic and put the security vulnerabilities in a table. Do NOT delete this tag too soon.}}

{|class="wikitable"
! style="width: 30%;" | Security Vulnerability
! style="width: 70%;" | Notes
|-
|Apple products crash when displaying certain Telugu or Bengali letter combinations.
|This refers to a real vulnerability in iOS and MacOS publicized a few days before the comic released <ref>https://techcrunch.com/2018/02/15/iphone-text-bomb-ios-mac-crash-apple/</ref>.
|-
|An attacker can use a timing attack to extploit[sic] a race condition in garbage collection to extract a limited number of bits from the Wikipedia article on Claude Shannon.
|Timing Attack to exploit a race condition in garbage collection refers to Meltdown and Spectre CPU flaws that can be exploited in cloud server like the ones in Wikipedia. Claude Shannon was an early and highly influential information scientist whose work underlies compression, encryption, security, and the theory behind how information is encoded into binary digits - hence the pertinence of extracting just some of the bits from his Wikipedia entry.
|-
|At the cafe on third street, the post-it note with the wifi password is visible from the sidewalk.
|Writing passwords in a visible place is a major security flaw. For instance, following the [[wikipedia:2018 Hawaii false missile alert|2018 Hawaii false missile alert]] the agency received criticism for a press photo showing a password written on a sticky note attached to a monitor.<ref>http://uk.businessinsider.com/hawaii-emergency-agency-password-discovered-in-photo-sparks-security-criticism-2018-1?r=US&IR=T</ref> However, if a cafe posts their wifi password for customers then having it visible through the window as well presents a very minor reduction in security.
|-
|A remote attacker can inject arbitrary text into public-facing pages via the comments box.
|Describes a common feature on news sites or social media sites like Facebook. The possibility for users to "inject" text into the page is by design. This is a humorous reference to the relatively common security vulnerability "[[Wikipedia:Cross-site_scripting|persistent cross-site scripting]]", where input provided by the user is displayed to other users in a dangerous fashion that allows attackers to inject arbitrary HTML or Javascript code into e.g. a comment section. It might also be a humorous reference to the events before, during and after the 2016 US Presidential elections where Internet Research Agency employees based remotely in St. Petersburg, Russia, but disguised as US citizens, "injected" arbitrary text in the form of political propaganda into comments on multiple web sites, according to an indictment returned by a federal grand jury on February 16, 2018.
|-
|MySQL server 55.45 secretly runs two parallel databases for people who say "S-Q-L" and "sequel."
|Some people pronounce "SQL" like "sequel", after SQL's predecessor "SEQUEL (Structured English Query Language)". The standard for SQL suggests that it should be pronounced as separate letters; however, the author of SQL pronounces it "sequel", so the debate is persisting (with even more justification than arguments about how to pronounce "GIF"). MySQL is an open-source relational database management system, the latest GA version (at the time of writing) is MySQL 5.7.
|-
|A flaw in some x86 CPUs could allow a root user to de-escalate to normal account privileges.
|This vulnerability refers to DOM0 attacks on Virtualization CPUs, regulary escalate from normal(few privileges) to root (full privileges), this is the inverse.
|-
|Apple products catch fire when displaying emoji with diacritics.
|Diacritics are the accents found on letters in some languages (eg. č, ģ ķ, ļ, ņ, š, ž). These would not be found on emojis. It is also a reference to a common problem of modern gadgets catching fire (usually related to flaws in Lithium-Ion batteries).
|-
|An oversight in the rules allows a dog to join a basketball team.
|This likely refers to the movie {{w|Air Bud}}. It is a movie about a dog playing basketball. This has been a common theme in xkcd comics, see [[115: Meerkat]], [[1439: Rack Unit]], [[1819: Sweet 16]], [[1552: Rulebook]]
|-
|Haskell isn't side-effect-free after all; the effects are all just concentrated in this one. Computer in Missouri that no one's checked on in a while.
|Haskell is a functional programming language, functional programming is characterized by using functions that don't have side effects in other parts of the program. The joke here is discovering that indeed it does have side-effects, but for some unknown (and highly absurd) reason they only manifest on a specific computer in a nondescript location, but no one has noticed.
|-
|Nobody really knows how hypervisors work.
|[[wikipedia:Hypervisor|"Hypervisors"]] are a tool for computer virtualization. Virtualization is an extremely complex topic, as it requires a computer to completely emulate a different computer with its own unique hardware and software. Many IT professionals and businesses rely heavily on various forms of virtualization, but the individual employees would be hard-pressed to explain how it works. Meltdown and Specter are related to this.
|-
|CRITICAL: Under Linux 3.14.8 on System/390 in a UTC+14 time zone, a local user could potentially use a buffer overflow to change another user's default system clock from 12-hour to 24-hour.
|This joke is about arcane systems that are running Linux in exceedingly unique situations, such that reproducing the error would be incredibly difficult or inconvenient, and would only affect a very tiny user base (if any at all). Other xkcd comics make references to such obscure computer-time issues relating to time zones and time conversions, and how many programmers find these issues frustrating or even traumatizing. UTC+14 is a time zone used only on some islands in the Pacific Ocean, i.e., [[Wikipedia:Line_Islands|the Line Islands]], and is also the earliest time zone on earth.
|-
|x86 has way too many instructions.
|The x86 architecture is considered "CISC" (a "complex instruction set computer"), having many instructions originally provided to make programming by a human simpler; other examples include the 68000 series used in the first Apple Mac. In the 1980s, this design philosophy was countered by the "RISC" ("reduced instruction set computer") design movement exemplified by SPARC, MIPS, PowerPC (previously used by Apple) and the ARM chips common in mobile phones - based on the observation that computer programs were increasingly generated by compilers (which only used a few instructions) rather than directly by people, and that the chip area dedicated to extra instructions could be better dedicated to, for example, cache. At the time, there was an internet war about the merits of each approach (with the Mac and PC being on different sides, at one time; owners of other competing systems such as the Archimedes and Amiga had similar arguments on usenet in the early 1990s); this "issue" may be posted by someone who still recalls these debates. Technically, the extra instructions do slightly complicate the task of validating correct chip behaviour and complicate the tool chains that manage software, which could be seen as a minor security risk; however, the 64-bit architecture introduced by AMD and since adopted by Intel does rationalise things somewhat, and all recent x86 chips break down instructions into RISC-like micro-operations, so the complication from a hardware perspective is localised. Recent security issues such as the speculative cache load issue in Meltdown and Spectre depend more on details of implementation rather than instruction set, and have been exhibited both by x86 (CISC) and ARM (RISC) processors.
|-
|NumPy 1.8.0 can factor primes in O(log n) time and must be quietly deprecated before anyone notices.
|NumPy is the fundamental package for scientific computing with Python. If something can find the prime factors of a number this quickly, there are attacks to break many crypto functions used in internet security. However, prime numbers have only a single factor, and "factoring primes" quickly is a simpler problem.
|-
|Apple products grant remote access if you send them words that break the "I before E" rule.
|Another joke on the first CVE and a common English writing rule of thumb, which fails almost as often as it succeeds. Possibly a jab at Apple's image, portraying their software as unable to handle improper grammar or spelling.
|-
|Skylake x86 chips can be pried from their sockets using certain flathead screwdrivers.
|Skylake x86 chips are a line of microprocessors. Yes, you can forcefully remove any processor from his socket with a screwdriver. There are many reports from people not using common sense.
|-
|Apparently Linus Torvalds can be bribed pretty easily.
|Linus Torvalds is the benevolent dictator of the Linux kernel codebase. Normally it is hard to pass a change because he has the last word about what merge to the code base because that code is replicated in all Linux installations, but apparently he is easy to bribe, which would be a severe critical vulnerability to all Linux servers and machines.
|-
|An attacker can execute malicious code on their own machine and no one can stop them.
|The point of an attack is to make someone else's machine perform actions against the owner's will. Anyone can make their own machine execute any code, but this would usually not be described as an attack.
|-
|Apple products execute any code printed over a photo of a dog with a saddle and a baby riding it.
|This could refer to a CVE vulnerability of JPG files where javascript embedded within the image file is executed by some application, only this time is in a printed photo instead of encoded into the image itself.
|-
|Under rare circumstances, a flaw in some versions of Windows could allow Flash to be installed.
|Flash was discontinued because of its notoriously abysmal security record. All security experts advise against install. The joke here relates to the perceived difficulty with keeping Flash up to date or even installed properly to begin with. A common user experience which is the subject of numerous jokes and memes is the constant nagging notification to install or update Flash in order for web pages to display properly. While anecdotal, many IT professionals will bemoan the trouble that Flash has given them in the workplace due to these notifications and problems related to them.
|-
|Turns out the cloud is just other people's computers.
|This refers to a computer meme where replace "cloud" with "other people's computers" must be used in all marketing presentation to CEOs and not computer literate persons to evaluate the security impact of using "Cloud services". Part of the humor here is that "the cloud", in actuality, it simply a term for hosted services, i.e., computers being run by other people (typically businesses that specialize in this type of "Platform As A Service" or "PAAS" service model). Calling "the cloud" as "other people's computers" is, at its core, entirely accurate, though it takes away the business jargon and simplifies the situation in such a way that it might cast doubt on the security, reliability, and general effectiveness of using "cloud" solutions.
|-
|A flaw in Mitre's CVE database allows arbitrary code insertion.[~~CLICK HERE FOR CHEAP VIAGRA~~]
|Mitre's CVE database is the database where all CVE are listed, this is a joke between the 4th CVE in this list pointing that the site is also vulnerable
|-
|It turns out Bruce Schneier is just two mischievous kids in a trenchcoat. (title text)
|Bruce Schneier is security researcher and blogger. He was mentioned in the title texts of [[748: Worst-Case Scenario]] and [[1039: RuBisCO]]. The "two kids in a trenchcoat" is a reference to the Totem Pole Trench trope.<ref>[http://tvtropes.org/pmwiki/pmwiki.php/Main/TotemPoleTrench TV Tropes:Totem Pole Trench trope]</ref> Bruce Schneier .
|}

== References ==
<references/>

==Transcript==
{{incomplete transcript|Do NOT delete this tag too soon.}}

LEAKED LIST OF MAJOR 2018 SECURITY VULNERABILITIES

CVE-2018-????? Apple products crash when displaying certain Telugu or Bengali letter combinations.

CVE-2018-????? An attacker can use a timing attack to extploit[sic] a race condition in garbage collection to extract a limited number of bits from the Wikipedia article on Claude Shannon.

CVE-2018-????? At the cafe on third street, the post-it note with the wifi password is visible from the sidewalk.

CVE-2018-????? A remote attacker can inject arbitrary text into public-facing pages via the comments box.

CVE-2018-????? MySQL server 55.45 secretly runs two parallel databases for people who say "S-Q-L" and "sequel."

CVE-2018-????? A flaw in some x86 CPUs could allow a root user to de-escalate to normal account privileges.

CVE-2018-????? Apple products catch fire when displaying emoji with diacritics.

CVE-2018-????? An oversight in the rules allows a dog to join a basketball team.

CUE-2018-????? Haskell isn't side-effect-free after all; the effects are all just concentrated in this one. Computer in Missouri that no one's checked on in a while.

CVE-2018-????? Nobody really knows how hypervisors work.

CVE-2018-????? CRITICAL: Under Linux 3.14.8 on System/390 in a UTC+14 time zone, a local user could potentially use a buffer overflow to change another user's default system clock from 12-hour to 24-hour.

CVE-2018-????? x86 has way too many instructions.

CVE-2018-????? NumPy 1.8.0 can factor primes in O(log n) time and must be quietly deprecated before anyone notices.

CVE-2018-????? Apple products grant remote access if you send them words that break the "I before E" rule.

CVE-2018-????? Skylake x86 chips can be pried from their sockets using certain flathead screwdrivers.

CVE-2018-????? Apparently Linus Torvalds can be bribed pretty easily.

CVE-2018-????? An attacker can execute malicious code on their own machine and no one can stop them.

CVE-2018-????? Apple products execute any code printed over a photo of a dog with a saddle and a baby riding it.

CVE-2018-????? Under rare circumstances, a flaw in some versions of Windows could allow Flash to be installed.

CVE-2018-????? Turns out the cloud is just other people's computers.

CVE-2018-????? A flaw in Mitre's CVE database allows arbitrary code insertion.[~~CLICK HERE FOR CHEAP VIAGRA~~]

{{comic discussion}}

Talk:1638: Backslashes

2016-08-16T21:45:59Z

Domino: Added comment about seeing an example of this in the wild

It should be noted that this also occurs in almost every programming language where "\" is the escape character. i.e.
print("Hello")
> Hello
print("\"Hello\"")
> "Hello"
print("\\Hello\\")
> \Hello\
Oh, and by the way, isn't this the third comic to mention "Ba'al, the Soul Eater"? Maybe we should start a category. (Others are [http://www.explainxkcd.com/wiki/index.php/1246:_Pale_Blue_Dot 1246] (title text) and [http://www.explainxkcd.com/wiki/index.php/1419:_On_the_Phone 1419].)
[[Special:Contributions/173.245.54.29|173.245.54.29]] 06:14, 3 February 2016 (UTC)
:Did that before seeing you comment, so yes I agree. --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 09:47, 3 February 2016 (UTC)
::But Davidy did not so the category has been deleted again. I have just cleaned up after my mess ;-) so there are no left over links to the dead category... --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 22:27, 8 February 2016 (UTC)

The last entry may also be an oblique reference to the infinitely-expandable recursive acronym "GOD = GOD Over Djinn" mentioned in Richard Hofstadter's Gödel, Escher, Bach.[[User:Taibhse|Taibhse]] ([[User talk:Taibhse|talk]]) 16:42, 3 February 2016 (UTC)

;I don't think the regex is invalid

According to <tt>man grep</tt> you need to specify the <tt>-E</tt> option to use extended regex; without it unescaped parentheses are not interpreted, so they don't need to match.

My - very wild - guess is that it was the command he used to find the line with the most special characters, but I am not confident enough to edit the article (if someone can confirm?). {{unsigned ip|141.101.66.83}}

If it was supposed to do that, it doesn't work. Running it on my bash history matches no lines, and I have lots of special characters in there [[Special:Contributions/197.234.242.243|197.234.242.243]] 07:12, 3 February 2016 (UTC)

Explain it to me like I'm dumb. What is this comic going on about? I think the explanation needs more examples like that hello, above, because that's almost understandable. --[[Special:Contributions/198.41.238.231|198.41.238.231]] 07:47, 3 February 2016 (UTC)
:I agree. But I cannot help either.--[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 09:51, 3 February 2016 (UTC)

This is the third time Randall has mentioned Ba'al the Soul Eater xD [[User:International Space Station|International Space Station]] ([[User talk:International Space Station|talk]]) 08:26, 3 February 2016 (UTC)
:Yes, that was already mentioned a few hours before you comment, see the first comment. --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 09:51, 3 February 2016 (UTC)

After passing the regex through bash, you get <nowiki>\\[[(].*\\[\])][^)\]]*$</nowiki> That is, the literal character \, followed by [ or (, followed by any number of any characters, followed by \, followed by ] or ), followed by any number of characters that aren't ) or ], until the end of the line. [[Special:Contributions/108.162.216.44|108.162.216.44]] 08:33, 3 February 2016 (UTC)
:It sounds like you know what you are talking about. Anyone who can explain it good enough for the explanation, and correct the explanation of the title text if it is wrong to say that it would not work. I have added this as the reason for incomplete. But maybe also examples are needed for people with not programming skills/knowledge. We also enjoy xkcd ;-) --[[User:Kynde|Kynde]] ([[User talk:Kynde|talk]]) 09:51, 3 February 2016 (UTC)
:I'm thinking that it's grepping for regular expressions that contain regular expressions. A regex containing <nowiki>"\[...\]"</nowiki> or <nowiki>"$...$"</nowiki> will match other regular expressions, as almost all non-trivial regexes use either character lists or groups. Now why out.txt is likely to contain not just regexes but rather regexes that search for regexes I have no idea - perhaps he had actually put too many backslashes in and he was trying to grep just for <nowiki>"[...]"</nowiki> or <nowiki>"(...)"</nowiki> (i.e. to locate probable regular expressions in out.txt, or anything else in parenthesis for that matter such as countless kinds of code/markup)? [[Special:Contributions/162.158.152.185|162.158.152.185]] 17:35, 4 February 2016 (UTC)

For fun:
cat ~/.bash_history | xargs -d "\n" -n 1 -I {} bash -c 'chars="$(echo "$1" | grep -o "[a-zA-Z0-9 ]" | wc -l)"; echo "$(( 100 - $(( $chars * 100 / ${#1} )) )) $1"' _ {} | sort -nrk 1 | less

Outputs your bash_history, ordered by relative gibberishness. This was copied by hand from desktop to mobile, might well have a few typos.--[[Special:Contributions/162.158.90.208|162.158.90.208]] 10:04, 3 February 2016 (UTC)
::Besides the fact that -d is a GNU extension to xargs (so it won't exist on OS X, FreeBSD, or anything else but Linux), this is a weird way to calculate gibberishness; I'm guessing functions, variable substitutions, .. and ./, etc. are going to swamp the more unreadable grep and the like. Plus, I think you need a uniq in there somewhere; otherwise, aren't the first few pages are all going to be filled with the 78 copies of "422 cd .." that tied for most gibberishy in my last 500 commands? --[[Special:Contributions/162.158.255.82|162.158.255.82]] 22:51, 7 March 2016 (UTC)

The problem in the comic is not with regexes per se but with situations when the entered text or expression passes through several interpreters, like bash -> grep/sed/awk, or program text -> external shell command. In such cases, you have to escape backslashes for each program in the sequence, and it gets worse if you have 'real' backslashes in the final text that you're processing with the utilities (Windows' file paths, for example). See https://en.wikipedia.org/wiki/Leaning_toothpick_syndrome.
Feel free to lift this to the explanation page, since I'm not good at longer and more careful explanations than this one.
Also, gotta notice that Feedly stripped paired backslashes in the title text (probably passed it through some 'interpreter' embedded in its scripts). [[User:Aasasd|Aasasd]] ([[User talk:Aasasd|talk]]) 10:13, 3 February 2016 (UTC)

:A funny comment about the MediaWiki software, which is even worse than this comic: <code><nowiki><Nikerabbit> I looked the code for rlike and didn't find where it does this. Can you point me to it? <vvv> $pattern = preg_replace( '!(\\\\\\\\\\\\\\\\)*(\\\\\\\\)?/!', '$1\\/', $pattern ); <Nikerabbit> I thought that was ascii art :)</nowiki></code> ([https://phabricator.wikimedia.org/P110$275 source]) --[[Special:Contributions/162.158.91.215|162.158.91.215]] 10:18, 3 February 2016 (UTC)

Interestingly, I first looked at this on my phone (using <strike>Chrome</strike> Feedly for Android), but the title text did not display correctly in that the backslashes didn't appear (which was a little confusing!). In Chrome on my Windows desktop, the title text appeared correctly. [[User:Jdluk|Jdluk]] ([[User talk:Jdluk|talk]]) 11:36, 3 February 2016 (UTC)

enough with the harry potter fancruft. "elder" is a [[Wiktionary:elder|perfectly good word]]. just because you came across it for the first time in harry potter means you are *typing carefully* the kind of person that likes harry potter. unless this is a ''harry potter reference'' wiki, of course. in which case i'll prepare a complete list of every word that appears both here and there and put a list on every page. oh, right, no i won't. --[[Special:Contributions/141.101.106.161|141.101.106.161]] 12:41, 3 February 2016 (UTC)

Remember that "Elder" is used in a lot of RPGs to denote high level enemies or items. I feel like that's what Randall's referring to here, more than Harry Potter or the general sense of the term "Elder." {{unsigned ip|108.162.245.156}}
: +1. Between the fact that harry potter (, ages, or tribes) aren't mentioned anywhere else in the text and the comic being a progressive list, I see this being the most likely explanation. Plus the metion of demons, which are easily the most* common usage of the modifier.
:: (*) or second most, after "elder gods", who are, let's face it, also demons. [[Special:Contributions/162.158.180.125|162.158.180.125]] 14:41, 3 February 2016 (UTC)
::: I'm pretty sure that "Elder backslash" is in reference to the "Elder gods" of Lovecraft. [[Special:Contributions/173.245.54.35|173.245.54.35]] 16:51, 3 February 2016 (UTC)
:::: Note also that it's called 'The Elder Wand' not as an intensifier, as in this comic and the other examples given, but because it is literally ''made from the wood of an [https://en.wikipedia.org/wiki/Sambucus_nigra Elder Tree]'' I'm pretty sure it's not an intentional reference. -Graptor [[Special:Contributions/173.245.54.23|173.245.54.23]] 19:29, 3 February 2016 (UTC)
::::: If it's an intentional reference to anything, it's to Lovecraft (or to something similar). I suspect the Elder Wand was an intentional pun by Rowling, however. --[[Special:Contributions/162.158.180.137|162.158.180.137]] 04:16, 4 February 2016 (UTC)
::::: Since no-one else seemed to want to, I just restructured that paragraph to make it more clear that if anything Harry Potter was inspired by the older examples, not the other way around. Expanded the LOTR reference and added DnD. If anything Randall is likely to be referencing either the Lovecraft references, or the concept of Elder in general. [[Special:Contributions/141.101.64.173|141.101.64.173]] 11:50, 4 February 2016 (UTC)

Attempting to add to the discussion: This regex is not necessarily invalid or incomprehensible. It looks like he was looking for a line with a regular expression or definitely some code. You just have to work your way through the backslashes. Although it might be invalid depending on the precise rules. He has some unescaped closing brackets and closing parenthesis. If these have to always be escaped then the regex is invalid. If however you don't have to escape a closing bracket with no opening bracket, then things are fine. I'm not familiar enough with grep's regex parser to know how it handles that edge case. Presuming those unescaped paren and brackets are fine, his regex searches for:

1. A backslash

2. An opening bracket

3. An opening parenthesis (this is a character set but the only character in it is an opening paren)

4. Any number of any characters

5. A backslash

6. An opening bracket

7. A closing bracket

8. A closing paren (presuming it doesn't have to be escaped when there is no opening paren)

9. A closing bracket (presuming it doesn't have to be escaped when there is no opening bracket)

10. Any number of character that are not a closing paren or closing bracket

11. The end of the line

Basically he is looking for a string that looks like:

\[(AAAAA\[])]AAAAA

Looks like a regex to me, and it looks like this regex also doesn't escape closing paren/brackets that don't have an opening paren/bracket, so I'm guessing that he knows what he is doing and his regex is fine. Maybe he was playing regex golf?
[[User:Cmancone|Cmancone]] ([[User talk:Cmancone|talk]])cmancone

Ninjaed by Cmancone, above. I agree with that result in every respect except for the start-of-string being potentially anything, but putting my own analysis in here because it took long enough to type!

Depth-of-backslash might depend upon depth of utility. In Perl, <nowiki>''</nowiki>-quotes (among others) treat everything within as literal whilst ""-quotes (and variations) interpolates any special characters, variables, etc that you put in it. (Search for "Quote and Quote-like operators" in your favourite PerlDocs source.) '\sss' is a literal backslash followed by three 's' characters , while "\sss" is the special \s escape (a whitespace) followed by two further regular characters. You might need to define the first when you need to use it to provide a not-previously-escaped \s so that it might be escaped within another context. ''Or'' you define it as "\\sss" (escaped-\) the first time, as equivalent to '\sss'. But '\\sss' would be a literal that, later, could be interpreted as an escaped-\ to the input of a further context where the \s finally becomes 'match a whitespace'.

'\\\sss' would be literal, whilst "\\\sss" could be equivalent to '\ ss' (literal backslash, literal space, rest of characters). Then, instead of literal '\\sss', for some purpose, you could interpolate two escaped-backslashes "\\\\sss"... and so on.

Meanwhile I ''think'', just from visual inspection, "'''\\\[[(].*\\\[\])][^)\]]*$'''" in Bash should obey the interpolation rules quite nicely. The first two characters must be a literal backslash (from the escaped-backslash) and a literal open-square bracket (again, escaped). The next open-square and the close-square shortly after depict a character class that contains only an open-parenthesis, and could have been written as '''$'''.

The '''.*''' indicates zero-or-more (the asterix) instances of ''any'' character (the dot). There is then a literal backslash (from the next '''\\''' duo) and a literal open-square (the '''\[''' pair) and close-square (the '''\]''' pair). The ''')''' is literal and does not need escaping (as a parenthesis group had not yet been opened), as is the next ''']''' character. To be sure, I would have written these two as the pair escapes '''$\]''', but horses for courses...

Then there's another character class (the next '''[''' and the final ''']''') required zero-or-more times (the asterix) to use up all the rest of the characters to the end (the ending '''$''' character). As there was no '''^''' character (a.k.a. caret/circumflex/etc) at the start, the match isn't bothered about what unmatched characters appear before the original '''\('''. This character class, however, starts with a '''^''' which in this context (the very first character of a character-class definition, not somewhere where an entire match-string starts) indicates negation of the following selection, so it is all characters ''but'' those specified, which is the regular close-parenthesis and (because it needs to be contained within a '''[]''' pair) the escaped close-square.

So, all matching strings must start with '''\[(''', i.e. the backslash, open-square and open-paren. They can continue with ''any'' further text, before then having a '''\[])]''', i.e. backslash, open-and-close-squares and close-paren, close-square. After this, the match continues just as long as there are no non-closing square/classic brackets before the ending.

The minimum matching literal string would be '''\[(\[])]''' with longer variants being of the form '''X\[(Y\[])]Z''' where X and Y can be replaced by anything (or be absent), and Z can be replaced by anything (or absent!) ''so long as it doesn't contain possibly relevent close-brackets!''. The latter stipulation is likely because the Y (and X) ''is'' allowed to contain these characters, and for some reason you don't want to confuse the test by finding some other '''\[])]''' segment within the X/Y-zones. (In this context, it doesn't actually seem to matter too much. But it might do in ways I haven't spotted or just be a hang-over from a prior permutation of the test.)

The "grep -o" function is working on the output to the file being '''cat'''ed (there are alternate ways of doing this that some people might prefer), to only accept the lines in the file that match the '''X\[(Y\[])]Z''' string. These lines would appear to be lines of out.txt (a fairly generic name that reveals little to its original purpose) that are well-formed for some other purpose. A safety-escaped (i.e. not to be taken literally by any simple parser) '''[]'''-grouping containing a '''()'''-group (''not'' escaped, perhaps reasonably in context) containing potentially random text followed by an empty '''[]''' pair (again, safety-escaped). Depending on the source, the empty '''[]'''-pair could mean many things, as with the other layers. And the lines may end with any further text.

The "out.txt" file might be the result of a prior Grep (string-search function) quote possibly scanning code for lines of particular importance by another pattern and dumping the results to out.txt for further perusal. And then Randall finds the need to dig further into the first result by extracting just those already selected that all have the '''X\[(Y\[])Z]'''-ish pattern to them.

But I could be wrong, and that's way too long for an official explanation.
(Perhaps just something like the penultimate paragraph, if we're not entirely mistaken?) [[Special:Contributions/162.158.152.89|162.158.152.89]] 14:14, 3 February 2016 (UTC)

The regex is supposed to be looking for:
\\\ backslash
[[(] [ or (
.* any character (repeated 0 or more times)
space space
\\\ backslash
[[\])] probably meant to match either [, ] or ). However, it's not correct, it instead matches the literal characters [)]
[^)\]]* probably meant to match any character that isn't ) or ], repeated. Instead it means one character that's not a ), and then a ] zero or more times
$ end of string

The first problem is that you're not supposed to escape ] in a [...], and it also has to be first in the grouping (unless negated with a ^) It should be [][)] or something similar.

The second problem is the same. The last bit should be [^])]*$ and not [^)\]]*$. [[User:Khris|Khris]] ([[User talk:Khris|talk]]) 14:24, 3 February 2016 (UTC)

I was reading through the regex, if using grep you run into an error with an unmatched ")". Removing this gets a string such as \[(AAAAA\[]]AAAAA$ http://regexr.com/3cng8 [[Special:Contributions/162.158.214.230|162.158.214.230]] 14:42, 3 February 2016 (UTC)

The regex relies on several special cases (*surprise*).
First: bash double-quote expansion (see [https://www.gnu.org/software/bash/manual/html_node/Double-Quotes.html#Double-Quotes]). Perhaps non-intuitively, \\\ followed by a character that \ doesn't escape is an escaped backslash followed by a literal backslash, effectively the same as \\\\ followed by that same non-escaped character. After bash double-quote expansion, this results in:

\\[[(].*\\[\])][^)\]]*$

grep interprets this as:

# any leading non-\ characters
# literal backslash
# character class containing [ and (
# zero or more *any* characters
# another literal backslash
# yet another literal backslash, via a character class containing only a backslash. Note this does not contain an escaped ], as it might appear at first glance. See [http://www.gnu.org/software/grep/manual/html_node/Character-Classes-and-Bracket-Expressions.html]
# literal )
# literal ]
# character class of anything except ), \
# zero or more ]
# end of line

Matching examples:
*echo 'asdf\[asdfasdf\\)]a]]]]]]' | grep -o "\\\[[(].*\\\[\])][^)\]]*$"
*echo '$\$]P' | grep -o "\\\[[(].*\\\[\])][^)\]]*$"

----
[[Special:Contributions/108.162.216.34|108.162.216.34]] 16:14, 3 February 2016 (UTC)rb

One key thing to understand is that \ is not a special character when it's in a bracket expression - you can't escape characters in bracket expressions. So [^)\] simply means any character other then ) or \. Also, ( and ) are just regular characters unless they are escaped in basic regular expressions - extended regular expressions reverse this rule. {{unsigned|Kalfalfa}}

I don't know about the regular expression in the title text, but I think the explanation is incorrect in that it starts off talking about regular expressions. Escaping backslashes is an issue with strings in programming in general. [[Special:Contributions/173.245.54.46|173.245.54.46]] 17:12, 3 February 2016 (UTC)
----
I suspect that Randall may have used the regexp in the title text to *find* malformed regular expressions in a file (out.txt) that he (or someone) had previously filled with output from some error message (or collection of error messages, or at least the output of something where a regular expression had been expected to work but had not worked as expected). [[Special:Contributions/162.158.252.227|162.158.252.227]] 19:06, 3 February 2016 (UTC)

You can use metacharacters in character classes, the only metacharacters in a character class that must be escaped are the closing square bracket (]), the backslash (\), the hyphen, and the carat and hyphen (^) if they are the first listed item in the set. The closing square bracket requires escaping because including it without would signal the end of the set otherwise, which then means the backslash must also be escaped. The hyphen must be escaped because, without it, it signals a range (unless it is listed first, then it is literal without escaping). Carat when listed first because otherwise it signals a negative set. 
Therefore, the end of the title text regex matches a backslash followed by either ] or ), which is then followed by any number (including none) of characters so long as they are not ] nor ) which means the whole regex can match "\[something\] more" or "$something$more" or "\[something\) more" as well as "\[something\]". — [[Special:Contributions/162.158.255.117|162.158.255.117]] 01:16, 4 February 2016 (UTC)

I'll add that I use an ''almost identical'' regex in my mail server for matching mailing-list subject lines which often have a format of "[Listname] normal subject line" which made it pretty recognizable to me. — [[Special:Contributions/162.158.255.117|162.158.255.117]] 01:24, 4 February 2016 (UTC)

;Example of a match

First, the shell will do some escaping substitution. So, in order to easily read it, let's see what grep really receives:

$ echo "\\\[[(].*\\\[\])][^)\]]*$"
\\[[(].*\\[\])][^)\]]*$

Let's break it out:

* <code>\\</code> matches a <code>\</code>
* <code>[[(]</code> matches either a <code>[</code> or a <code>(</code>
* <code>.*</code> matches any series of characters until the next match
* <code>\\</code> matches a <code>\</code>
* <code>[\]</code> matches a <code>\</code>
* <code>)]</code> matches <code>)]</code>
* <code>[^)\]</code> matches anything but <code>)</code> or <code>\</code>
* <code>]*</code> matches any number of <code>]</code> (including none)
* <code>$</code> matches the end of the string

So the string '''\[aaa\]\\)]a]]]]]]''' matches! {{unsigned ip|108.162.228.167}}

...Maybe it's meant to search for all Game Grumps transcripts which make mention of the "[http://gamegrumps.wikia.com/wiki/Grep Grep]" gag? [[Special:Contributions/108.162.216.55|108.162.216.55]] 15:53, 3 February 2016 (UTC)

...Wow, guys, and here I was thinking he wanted to put the cat out, when the cat didn't want to go out.... [[Special:Contributions/108.162.249.158|108.162.249.158]] 04:03, 4 February 2016 (UTC)

What I think is that Randall probably ''intended'' the regex to match "backslash, opening round or square bracket, anything, backslash, closing round or square bracket, anything that doesn't involve closing round or square brackets", since (unlike most other possibilities given) that actually looks like something one might want to search for. Whether it ''does'', in fact, match that or something else (or indeed anything at all) is another question entirely. (For all we know, it didn't work, Randall figured out it didn't, and wrote the correct thing the next line over.) Unrelatedly: this comic (and the backslash proliferation in general) reminded me of the Telnet Song. --[[Special:Contributions/162.158.180.137|162.158.180.137]] 04:16, 4 February 2016 (UTC)

That explanation is wrong: <code>[\]</code> does not match a literal backslash; it would still need to be escaped inside the brackets. That backslash escapes the next character, a ], so the group doesn't end there. The actual expression there is <code>[\])]</code>, a character group containing an escaped ] and a ). Just like the first part. It is most likely intended to catch content surrounded by [ ] or ( ). [[Special:Contributions/141.101.104.15|141.101.104.15]] 13:43, 4 February 2016 (UTC)
:To clarify: this makes the expression catch anything that starts with a block surrounded by escaped round or square brackets. So stuff like '''$Hello world$more text here''' but with either round or square brackets (or combinations, since there's nothing enforcing they have to match. I'd have made it an OR case with two groups with matching brackets, personally) -[[Special:Contributions/141.101.104.15|141.101.104.15]] 13:51, 4 February 2016 (UTC)
:You're making the same mistake Randall did: while many (most?) regex dialects use \ as escape inside a character class, this is not true for grep's default syntax. I've expanded that interpretation in my comment below, however the analysis by 108.162.228.167 is a correct explanation of how this expression is ''actually'' interpreted by grep. --[[Special:Contributions/141.101.75.185|141.101.75.185]] 15:42, 4 February 2016 (UTC)

Your analysis is thorough and correct, however it is unlikely this is what the regex was intended to accomplish. More likely, Randall is more accustomed to other regex dialects such as Perl(-compatible) regex where a backslash ''does'' work to escape special characters inside a character class. Under that assumption the regex (with some whitespace inserted for readability) would break up as:
* <code>\\ [[(]</code> an escaped opening bracket or paren
* <code>.*</code> anything
* <code>\\ [\])]</code> an escaped closing bracket or paren
* <code>[^)\]]* $</code> no closing bracket or paren occurring on the remainder of the line
Although the final condition is still a bit obscure, this still makes a ''lot'' more sense. Unfortunately it also crushes Randall's hope the regex worked as intended, since this simply isn't how the expression is parsed with grep's default syntax (which is why I always use <code>grep -P</code>). --[[Special:Contributions/141.101.75.185|141.101.75.185]] 15:34, 4 February 2016 (UTC)
----
Did anyone notice the [https://en.wikipedia.org/wiki/Cat_%28Unix%29#Useless_use_of_cat Useless Use of Cat]? [[Special:Contributions/141.101.106.101|141.101.106.101]] 19:36, 4 February 2016 (UTC)

:Yup - I hereby award Randall with the Useless Use of Cat Award of the day. Cherish it.
:[[User:Zedn00|Zedn00]] ([[User talk:Zedn00|talk]]) 03:51, 5 February 2016 (UTC) Zedn00
----
;Changed Regex
At some point before 2016-02-09 18:00 +0100, Randall has modified the bash command in the title text!

Original command:
cat out.txt | grep -o "\\\[[(].*\\\[\])][^)\]]*$"
New command:
cat out.txt | grep -o "[[(].*[])][^)]]*$"

For the old command, 108.162.228.167's and 108.162.216.34's explanations above were correct.

The new command matches:
[[(] either a '[' or a '('
.* an unbounded and possibly empty sequence of arbitrary characters
[])] either a ']' or a ')'
[^)] any character except for a ')'
]* an unbounded and possibly empty sequence of ']'
$ anchored at end of line

It now e.g. matches '''123[abc.<>)x]]]]]''':
$ echo "123[abc.<>)x]]]]]" | tee /dev/stderr | grep -o "[[(].*[])][^)]]*$"

This makes hardly more sense than the original command.
--[[User:Markus|Markus]] ([[User talk:Markus|talk]]) 17:38, 9 February 2016 (UTC)
----
Funny enough, I'm literally looking at some other dev's code right now that actually implements an eight backslash regex sequence, with just the comment "backslash". I'm still scratching my head over what they were trying to accomplish or even communicate with this. [[User:Domino|Domino]] ([[User talk:Domino|talk]]) 21:45, 16 August 2016 (UTC)domino
----

1695: Code Quality 2

2016-06-17T19:06:03Z

Domino: Made edits based on suggestions

{{comic
| number = 1695
| date = June 17, 2016
| title = Code Quality 2
| image = code_quality_2.png
| titletext = It's like you tried to define a formal grammar based on fragments of a raw database dump from the QuickBooks file of a company that's about to collapse in an accounting scandal.
}}

==Explanation==
{{incomplete|first edits}}

The comic is a continuation of [[1513: Code Quality]], in which we see [[Ponytail]] being introduced to the {{w|source code}} [[Cueball]] has written, and where he is warning her that he is self-taught so his code probably won't be written the way she is used to.
She then continues to describe poetically the total mess of a code she encounters, using references to recipes created by corporate lawyers or the transcript of a couple arguing at IKEA.

The second panel makes a reference to "OCR" ({{w|Optical Character Recognition}}), a technique for recognizing text in a picture using software. In this case she is referring to a picture of a {{w|Scrabble}} game, which is a popular word-making game in which players have a pseudo-randomized set of letters and must arrange them on a grid to form interlocking words. OCR software is notoriously imperfect at the time of writing, and the criss-crossing semi-random words on a Scrabble board fed through an OCR program would likely produce dubious results, certainly not fit for current code standards. This is further compounded by Ponytail's suggestion that Cueball made rampant use of JavaScript reserved words in his declarations, which is [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar#Keywords strictly forbidden] by the language. Scrabble's point system is based on the value of individual letters, combined with certain modifier squares on the game board which can boost points. "Triple points" is the highest class of modifier available in the game (though it can be for triple points on a specific letter, or the entire word) and is highly-sought-after by players.

The third panel continues Ponytail's rant, this time referencing naval weather forecasts, avian interference and indentation. A weather forecast is a complex, multidimensional array of data used in predicting or assessing the atmospheric conditions of a geographical area over a set time. One such example of a "naval weather forecast" [https://www.fnmoc.navy.mil/wxmap_cgi/cgi-bin/wxmap_DOD_area.cgi?area=efs_nvg_nlant&set=EFS may be this one], which would generally be unreadable to an untrained individual. Transcribing it would be a long and typing-intensive process which could result in an even more unreadable product, further complicated by a {{w|woodpecker}} (a bird noted for its rapid successive pecking motions) "hammering" (pecking) the Shift key on the keyboard, which would result in many letters being randomly capitalized. Indentation is the practice of shifting a section of text further from the starting margin, which in coding is typically used to organize functions and statements, but if done "randomly" would only serve to scramble the code hierarchy.

The fourth panel references famous poet {{w|E. E. Cummings}} and user name suggestions. Edward Estin Cummings was a poet (pseudonym "e e cummings" or "E. E. Cummings") who used capitalization, punctuation, and line breaks in unconventional ways. Websites that offer membership often also require that users create a pseudonym (known as a "username") for use in tracking/authenticating their actions on the site, as well as identifying them to the site's community. Many of these sites also require usernames be unique. On popular sites, many common words, phrases and names have already been reserved by users, so when signing up for them many people run into situations where the name they want has already been taken. On many sites where this happens, the site may suggest alternate usernames, usually based on the one that was entered to begin with. For example, if the username "Hedgeclipper" is already reserved, the site may recommend "Hedgeclipper1234" or "H3dg3clipp3r" instead, depending on the algorithm behind the suggestions. In other cases, websites requiring users to enter personal information such as their name may suggest a username based on their name with a string of digits after it, such as "Joshua1128". An E. E. Cummings poem written entirely out of these semi-random suggestions would make the resulting poem even more "unusual" than his work is already considered.

The last panel's simile involves {{w|Markov chaining}}, {{w|Chatterbot|chat-bots}} (presumably), bus schedules and potential [http://timesofindia.indiatimes.com/city/kolkata/Air-India-plane-unfit-to-fly-may-be-scrapped-after-bus-crash/articleshow/50307194.cms gross vehicular negligence]. Applied Markov chaining is a process used in many computer algorithms that try to simulate real-world concepts such as speech simulation and decisions-making. Its inherent randomness also makes it a candidate for unpredictable things such as stock market analysis and speech recognition. Bus schedules are [http://elb-jpinstances-1463028547.us-east-1.elb.amazonaws.com/ccg3/XSLT_STT_REQUEST?mode=direct&line=ccg:01065:%20:H:y15&sessionID=0&requestID=0&itdLPxx_template=tableResults&type_stt=any&language=en&coordOutputFormat=WGS84%5Bdd.ddddd%5D&outputFormat=0&name_stt=10111816&contentFilter=allstops often complicated and full of notation], and are notorious for confusing people who are not used to reading them. Chat-bots using applied Markov chains to recognize and respond to speech/text rely on the input being clear and well-organized in plain language. "Feeding" bus schedules to such a bot would likely result in the returns being complete gibberish and unreadable. The issue is further complicated when Ponytail suggests that the schedules are from a city where "the [http://www.heapsoffun.com/pictures/20120106/funny_bus_crash_1002.jpg buses] [http://data.whicdn.com/images/45882595/original.jpg crash] [http://blog.taxiforsure.com/wp-content/uploads/indian-traffic-bus.jpg constantly]", which would be horrifying if it happened so [http://i3.kym-cdn.com/entries/icons/original/000/002/842/unexplainable.jpg regularly] that the schedules actually took [http://baddogneedsrottenhome.com/images/emails/527927c6cbfff.jpg crashes] into account. Even more horrifying would be the further unpredictability of the output of the chat-bot from such unpredictable input.

Cueball finally comments that "...it runs fine for now" which indicates he knows the code has problems but it reluctant to fix them because it's more-or-less serving its function. Ponytail quips back that "So does a [http://scarboroughwhat.com/wp-content/uploads/2015/06/bitch-im-a-burning-bus.jpg burning bus]", which is technically true, but the "for now" part implies that disaster and injury could result at any moment, as would likely happen on a burning bus.

==Transcript==
Side view of Ponytail sitting at a computer in all five panels.

First panel, tall vertical. 
Ponytail: Ugh, I hate reading your code. 
Offscreen: I know, I know.

Second panel is wider, shows her in an office chair. 
Ponytail: It's like you ran OCR on a photo of a Scrabble board from a game where Javascript reserved words counted for triple points. 

Third panel zooms in and shows just her head. 
Ponytail: It looks like someone transcribed a naval weather forecast while woodpeckers hammered their shift keys, then randomly indented it. 

Fourth panel, similar to second, though slightly narrower. 
Ponytail: It's like an e e cummings poem written using only the usernames a website suggests when the one you want is taken. 

Fifth panel zooms in, shows her head and the screen. 
Ponytail: This looks like the output of a Markov bot that's been fed bus timetables from a city where the buses crash constantly. 
Offscreen: Whatever, it runs fine for now. 
Ponytail: So does a burning bus.

{{comic discussion}}

1695: Code Quality 2

2016-06-17T14:53:58Z

Domino: Added final touches to links

{{comic
| number = 1695
| date = June 17, 2016
| title = Code Quality 2
| image = code_quality_2.png
| titletext = It's like you tried to define a formal grammar based on fragments of a raw database dump from the QuickBooks file of a company that's about to collapse in an accounting scandal.
}}

==Explanation==
{{incomplete|first edits}}

The comic is a continuation of [[1513: Code Quality]], in which we see [[Ponytail]] being introduced to the {{w|source code}} [[Cueball]] has written, and where he is warning her that he is self-taught so his code probably won't be written the way she is used to.
She then continues to describe poetically the total mess of a code she encounters, using references to recipes created by corporate lawyers or the transcript of a couple arguing at IKEA.

The second panel makes a reference to "OCR" which is an acronym for [https://en.wikipedia.org/wiki/Optical_character_recognition Optical Character Recognition], a technique for recognizing text in a picture using software. In this case she is referring to a picture of a [https://en.wikipedia.org/wiki/Scrabble Scrabble] game, which is a popular word-making game in which players have a pseudo-randomized set of letters and must arrange them on a grid to form interlocking words. OCR software is notoriously imperfect at the time of writing, and the criss-crossing semi-random words on a Scrabble board fed through an OCR program would likely produce dubious results, certainly not fit for current code standards. This is further compounded by Ponytail's suggestion that Cueball made rampant use of JavaScript reserved words in his declarations, which is [http://www.javascripter.net/faq/reserved.htm strictly forbidden] by the language. Scrabble's point system is based on the value of individual letters, combined with certain modifier squares on the game board which can boost points. "Triple points" is the highest class of modifier available in the game (though it can be for triple points on a specific letter, or the entire word) and is highly-sought-after by players.

The third panel continues Ponytail's rant, this time referencing naval weather forecasts, avian interference and indentation. A weather forecast is a complex, multidimensional array of data used in predicting or assessing the atmospheric conditions of a geographical area over a set time. One such example of a "naval weather forecast" [https://www.fnmoc.navy.mil/wxmap_cgi/cgi-bin/wxmap_DOD_area.cgi?area=efs_nvg_nlant&set=EFS may be this one], which would generally be unreadable to an untrained individual. Transcribing it would be a long and typing-intensive process which could result in an even more unreadable product, further complicated by a [https://en.wikipedia.org/wiki/Woodpecker woodpecker] (a bird noted for its rapid successive pecking motions) "hammering" (pecking) the Shift key on the keyboard, which would result in many letters being randomly capitalized. Indentation is the practice of shifting a section of text further from the starting margin, which in coding is typically used to organize functions and statements, but if done "randomly" would only serve to scramble the code hierarchy.

The fourth panel references famous poet [https://en.wikipedia.org/wiki/E._E._Cummings E. E. Cummings] and user name suggestions. E. E. Cummings was noted for his "unusual" style of poetry which combined words and phrases in ways that were a-typical for English speech, resulting in constructs that might easily confuse someone who doesn't natively speak the language. Websites that offer membership often also require that users create a pseudonym (known as a "username") for use in tracking/authenticating their actions on the site, as well as identifying them to the site's community. Many of these sites also require usernames be unique. On popular sites, many common words, phrases and names have already been reserved by users, so when signing up for them many people run into situations where the name they want has already been taken. On many sites where this happens, the site may suggest alternate usernames, usually based on the one that was entered to begin with. For example, if the username "Hedgeclipper" is already reserved, the site may recommend "Hedgeclipper1234" or "H3dg3clipp3r" instead, depending on the algorithm behind the suggestions. An E. E. Cummings poem written entirely out of these semi-random suggestions would make the resulting poem even more "unusual" than his work is already considered.

The last panel's metaphor involves [https://en.wikipedia.org/wiki/Markov_chain Markov chaining], [https://en.wikipedia.org/wiki/Chatterbot chat-bots] (presumably), bus schedules and potential [http://timesofindia.indiatimes.com/city/kolkata/Air-India-plane-unfit-to-fly-may-be-scrapped-after-bus-crash/articleshow/50307194.cms gross vehicular negligence]. Applied Markov chaining is a process used in many computer algorithms that try to simulate real-world concepts such as speech simulation and decisions-making. It's inherent randomness also makes it a candidate for unpredictable things such as stock market analysis and speech recognition. Bus schedules are [http://elb-jpinstances-1463028547.us-east-1.elb.amazonaws.com/ccg3/XSLT_STT_REQUEST?mode=direct&line=ccg:01065:%20:H:y15&sessionID=0&requestID=0&itdLPxx_template=tableResults&type_stt=any&language=en&coordOutputFormat=WGS84%5Bdd.ddddd%5D&outputFormat=0&name_stt=10111816&contentFilter=allstops often complicated and full of notation], and are notorious for confusing people who are not used to reading them. Chat-bots using applied Markov chains to recognize and respond to speech/text rely on the input being clear and well-organized in plain language. "Feeding" bus schedules to such a bot would likely result in the returns being complete gibberish and unreadable. The issue is further complicated when Ponytail suggests that the schedules are from a city where "the [http://www.heapsoffun.com/pictures/20120106/funny_bus_crash_1002.jpg buses] [http://data.whicdn.com/images/45882595/original.jpg crash] [http://blog.taxiforsure.com/wp-content/uploads/indian-traffic-bus.jpg constantly]", which would be horrifying if it happened so [http://i3.kym-cdn.com/entries/icons/original/000/002/842/unexplainable.jpg regularly] that the schedules actually took [http://baddogneedsrottenhome.com/images/emails/527927c6cbfff.jpg crashes] into account. Even more horrifying would be the further unpredictability of the output of the chat-bot from such unpredictable input.

Cueball finally comments that "...it runs fine for now" which indicates he knows the code has problems but it reluctant to fix them because it's more-or-less serving its function. Ponytail quips back that "So does a [http://scarboroughwhat.com/wp-content/uploads/2015/06/bitch-im-a-burning-bus.jpg burning bus]", which is technically true, but the "for now" part implies that disaster and injury could result at any moment, as would likely happen on a burning bus.

==Transcript==
Side view of Ponytail sitting at a computer in all five panels.

First panel, tall vertical. 
Ponytail: Ugh, I hate reading your code. 
Offscreen: I know, I know.

Second panel is wider, shows her in an office chair. 
Ponytail: It's like you ran OCR on a photo of a Scrabble board from a game where Javascript reserved words counted for triple points. 

Third panel zooms in and shows just her head. 
Ponytail: It looks like someone transcribed a naval weather forecast while woodpeckers hammered their shift keys, then randomly indented it. 

Fourth panel, similar to second, though slightly narrower. 
Ponytail: It's like an e e cummings poem written using only the usernames a website suggests when the one you want is taken. 

Fifth panel zooms in, shows her head and the screen. 
Ponytail: This looks like the output of a Markov bot that's been fed bus timetables from a city where the buses crash constantly. 
Offscreen: Whatever, it runs fine for now. 
Ponytail: So does a burning bus.

{{comic discussion}}

1695: Code Quality 2

2016-06-17T14:46:37Z

Domino: Added links to bus crashes

{{comic
| number = 1695
| date = June 17, 2016
| title = Code Quality 2
| image = code_quality_2.png
| titletext = It's like you tried to define a formal grammar based on fragments of a raw database dump from the QuickBooks file of a company that's about to collapse in an accounting scandal.
}}

==Explanation==
{{incomplete|first edits}}

The comic is a continuation of [[1513: Code Quality]], in which we see [[Ponytail]] being introduced to the {{w|source code}} [[Cueball]] has written, and where he is warning her that he is self-taught so his code probably won't be written the way she is used to.
She then continues to describe poetically the total mess of a code she encounters, using references to recipes created by corporate lawyers or the transcript of a couple arguing at IKEA.

The second panel makes a reference to "OCR" which is an acronym for [https://en.wikipedia.org/wiki/Optical_character_recognition Optical Character Recognition], a technique for recognizing text in a picture using software. In this case she is referring to a picture of a [https://en.wikipedia.org/wiki/Scrabble Scrabble] game, which is a popular word-making game in which players have a pseudo-randomized set of letters and must arrange them on a grid to form interlocking words. OCR software is notoriously imperfect at the time of writing, and the criss-crossing semi-random words on a Scrabble board fed through an OCR program would likely produce dubious results, certainly not fit for current code standards. This is further compounded by Ponytail's suggestion that Cueball made rampant use of JavaScript reserved words in his declarations, which is [http://www.javascripter.net/faq/reserved.htm strictly forbidden] by the language. Scrabble's point system is based on the value of individual letters, combined with certain modifier squares on the game board which can boost points. "Triple points" is the highest class of modifier available in the game (though it can be for triple points on a specific letter, or the entire word) and is highly-sought-after by players.

The third panel continues Ponytail's rant, this time referencing naval weather forecasts, avian interference and indentation. A weather forecast is a complex, multidimensional array of data used in predicting or assessing the atmospheric conditions of a geographical area over a set time. One such example of a "naval weather forecast" [https://www.fnmoc.navy.mil/wxmap_cgi/cgi-bin/wxmap_DOD_area.cgi?area=efs_nvg_nlant&set=EFS may be this one], which would generally be unreadable to an untrained individual. Transcribing it would be a long and typing-intensive process which could result in an even more unreadable product, further complicated by a [https://en.wikipedia.org/wiki/Woodpecker woodpecker] (a bird noted for its rapid successive pecking motions) "hammering" (pecking) the Shift key on the keyboard, which would result in many letters being randomly capitalized. Indentation is the practice of shifting a section of text further from the starting margin, which in coding is typically used to organize functions and statements, but if done "randomly" would only serve to scramble the code hierarchy.

The fourth panel references famous poet [https://en.wikipedia.org/wiki/E._E._Cummings E. E. Cummings] and user name suggestions. E. E. Cummings was noted for his "unusual" style of poetry which combined words and phrases in ways that were a-typical for English speech, resulting in constructs that might easily confuse someone who doesn't natively speak the language. Websites that offer membership often also require that users create a pseudonym (known as a "username") for use in tracking/authenticating their actions on the site, as well as identifying them to the site's community. Many of these sites also require usernames be unique. On popular sites, many common words, phrases and names have already been reserved by users, so when signing up for them many people run into situations where the name they want has already been taken. On many sites where this happens, the site may suggest alternate usernames, usually based on the one that was entered to begin with. For example, if the username "Hedgeclipper" is already reserved, the site may recommend "Hedgeclipper1234" or "H3dg3clipp3r" instead, depending on the algorithm behind the suggestions. An E. E. Cummings poem written entirely out of these semi-random suggestions would make the resulting poem even more "unusual" than his work is already considered.

The last panel's metaphor involves [https://en.wikipedia.org/wiki/Markov_chain Markov chaining], [https://en.wikipedia.org/wiki/Chatterbot chat-bots] (presumably), bus schedules and potential [http://timesofindia.indiatimes.com/city/kolkata/Air-India-plane-unfit-to-fly-may-be-scrapped-after-bus-crash/articleshow/50307194.cms gross vehicular negligence]. Applied Markov chaining is a process used in many computer algorithms that try to simulate real-world concepts such as speech simulation and decisions-making. It's inherent randomness also makes it a candidate for unpredictable things such as stock market analysis and speech recognition. Bus schedules are [http://elb-jpinstances-1463028547.us-east-1.elb.amazonaws.com/ccg3/XSLT_STT_REQUEST?mode=direct&line=ccg:01065:%20:H:y15&sessionID=0&requestID=0&itdLPxx_template=tableResults&type_stt=any&language=en&coordOutputFormat=WGS84%5Bdd.ddddd%5D&outputFormat=0&name_stt=10111816&contentFilter=allstops often complicated and full of notation], and are notorious for confusing people who are not used to reading them. Chat-bots using applied Markov chains to recognize and respond to speech/text rely on the input being clear and well-organized in plain language. "Feeding" bus schedules to such a bot would likely result in the returns being complete gibberish and unreadable. The issue is further complicated when Ponytail suggests that the schedules are from a city where "the [http://www.heapsoffun.com/pictures/20120106/funny_bus_crash_1002.jpg buses] [http://data.whicdn.com/images/45882595/original.jpg crash] [http://blog.taxiforsure.com/wp-content/uploads/indian-traffic-bus.jpg constantly]", which would be horrifying if it happened so regularly that the schedules actually took [http://baddogneedsrottenhome.com/images/emails/527927c6cbfff.jpg crashes] into account. Even more horrifying would be the further unpredictability of the output of the chat-bot from such unpredictable input.

Cueball finally comments that "...it runs fine for now" which indicates he knows the code has problems but it reluctant to fix them because it's more-or-less serving its function. Ponytail quips back that "So does a burning bus", which is technically true, but the "for now" part implies that disaster and injury could result at any moment, as would likely happen on a burning bus.

==Transcript==
Side view of Ponytail sitting at a computer in all five panels.

First panel, tall vertical. 
Ponytail: Ugh, I hate reading your code. 
Offscreen: I know, I know.

Second panel is wider, shows her in an office chair. 
Ponytail: It's like you ran OCR on a photo of a Scrabble board from a game where Javascript reserved words counted for triple points. 

Third panel zooms in and shows just her head. 
Ponytail: It looks like someone transcribed a naval weather forecast while woodpeckers hammered their shift keys, then randomly indented it. 

Fourth panel, similar to second, though slightly narrower. 
Ponytail: It's like an e e cummings poem written using only the usernames a website suggests when the one you want is taken. 

Fifth panel zooms in, shows her head and the screen. 
Ponytail: This looks like the output of a Markov bot that's been fed bus timetables from a city where the buses crash constantly. 
Offscreen: Whatever, it runs fine for now. 
Ponytail: So does a burning bus.

{{comic discussion}}

1695: Code Quality 2

2016-06-17T14:29:00Z

Domino: Fixed panel names. Added fourth panel explanation and wrap-up

{{comic
| number = 1695
| date = June 17, 2016
| title = Code Quality 2
| image = code_quality_2.png
| titletext = It's like you tried to define a formal grammar based on fragments of a raw database dump from the QuickBooks file of a company that's about to collapse in an accounting scandal.
}}

==Explanation==
{{incomplete|first edits}}

The comic is a continuation of [[1513: Code Quality]], in which we see [[Ponytail]] being introduced to the {{w|source code}} [[Cueball]] has written, and where he is warning her that he is self-taught so his code probably won't be written the way she is used to.
She then continues to describe poetically the total mess of a code she encounters, using references to recipes created by corporate lawyers or the transcript of a couple arguing at IKEA.

The second panel makes a reference to "OCR" which is an acronym for [https://en.wikipedia.org/wiki/Optical_character_recognition Optical Character Recognition], a technique for recognizing text in a picture using software. In this case she is referring to a picture of a [https://en.wikipedia.org/wiki/Scrabble Scrabble] game, which is a popular word-making game in which players have a pseudo-randomized set of letters and must arrange them on a grid to form interlocking words. OCR software is notoriously imperfect at the time of writing, and the criss-crossing semi-random words on a Scrabble board fed through an OCR program would likely produce dubious results, certainly not fit for current code standards. This is further compounded by Ponytail's suggestion that Cueball made rampant use of JavaScript reserved words in his declarations, which is [http://www.javascripter.net/faq/reserved.htm strictly forbidden] by the language. Scrabble's point system is based on the value of individual letters, combined with certain modifier squares on the game board which can boost points. "Triple points" is the highest class of modifier available in the game (though it can be for triple points on a specific letter, or the entire word) and is highly-sought-after by players.

The third panel continues Ponytail's rant, this time referencing naval weather forecasts, avian interference and indentation. A weather forecast is a complex, multidimensional array of data used in predicting or assessing the atmospheric conditions of a geographical area over a set time. One such example of a "naval weather forecast" [https://www.fnmoc.navy.mil/wxmap_cgi/cgi-bin/wxmap_DOD_area.cgi?area=efs_nvg_nlant&set=EFS may be this one], which would generally be unreadable to an untrained individual. Transcribing it would be a long and typing-intensive process which could result in an even more unreadable product, further complicated by a [https://en.wikipedia.org/wiki/Woodpecker woodpecker] (a bird noted for its rapid successive pecking motions) "hammering" (pecking) the Shift key on the keyboard, which would result in many letters being randomly capitalized. Indentation is the practice of shifting a section of text further from the starting margin, which in coding is typically used to organize functions and statements, but if done "randomly" would only serve to scramble the code hierarchy.

The fourth panel references famous poet [https://en.wikipedia.org/wiki/E._E._Cummings E. E. Cummings] and user name suggestions. E. E. Cummings was noted for his "unusual" style of poetry which combined words and phrases in ways that were a-typical for English speech, resulting in constructs that might easily confuse someone who doesn't natively speak the language. Websites that offer membership often also require that users create a pseudonym (known as a "username") for use in tracking/authenticating their actions on the site, as well as identifying them to the site's community. Many of these sites also require usernames be unique. On popular sites, many common words, phrases and names have already been reserved by users, so when signing up for them many people run into situations where the name they want has already been taken. On many sites where this happens, the site may suggest alternate usernames, usually based on the one that was entered to begin with. For example, if the username "Hedgeclipper" is already reserved, the site may recommend "Hedgeclipper1234" or "H3dg3clipp3r" instead, depending on the algorithm behind the suggestions. An E. E. Cummings poem written entirely out of these semi-random suggestions would make the resulting poem even more "unusual" than his work is already considered.

The last panel's metaphor involves [https://en.wikipedia.org/wiki/Markov_chain Markov chaining], [https://en.wikipedia.org/wiki/Chatterbot chat-bots] (presumably), bus schedules and potential gross vehicular negligence. Applied Markov chaining is a process used in many computer algorithms that try to simulate real-world concepts such as speech simulation and decisions-making. It's inherent randomness also makes it a candidate for unpredictable things such as stock market analysis and speech recognition. Bus schedules are [http://elb-jpinstances-1463028547.us-east-1.elb.amazonaws.com/ccg3/XSLT_STT_REQUEST?mode=direct&line=ccg:01065:%20:H:y15&sessionID=0&requestID=0&itdLPxx_template=tableResults&type_stt=any&language=en&coordOutputFormat=WGS84%5Bdd.ddddd%5D&outputFormat=0&name_stt=10111816&contentFilter=allstops often complicated and full of notation], and are notorious for confusing people who are not used to reading them. Chat-bots using applied Markov chains to recognize and respond to speech/text rely on the input being clear and well-organized in plain language. "Feeding" bus schedules to such a bot would likely result in the returns being complete gibberish and unreadable. The issue is further complicated when Ponytail suggests that the schedules are from a city where "the buses crash constantly", which would be horrifying if it happened so regularly that the schedules actually took crashes into account. Even more horrifying would be the further unpredictability of the output of the chat-bot from such unpredictable input.

Cueball finally comments that "...it runs fine for now" which indicates he knows the code has problems but it reluctant to fix them because it's more-or-less serving its function. Ponytail quips back that "So does a burning bus", which is technically true, but the "for now" part implies that disaster and injury could result at any moment, as would likely happen on a burning bus.

==Transcript==
Side view of Ponytail sitting at a computer in all five panels.

First panel, tall vertical. 
Ponytail: Ugh, I hate reading your code. 
Offscreen: I know, I know.

Second panel is wider, shows her in an office chair. 
Ponytail: It's like you ran OCR on a photo of a Scrabble board from a game where Javascript reserved words counted for triple points. 

Third panel zooms in and shows just her head. 
Ponytail: It looks like someone transcribed a naval weather forecast while woodpeckers hammered their shift keys, then randomly indented it. 

Fourth panel, similar to second, though slightly narrower. 
Ponytail: It's like an e e cummings poem written using only the usernames a website suggests when the one you want is taken. 

Fifth panel zooms in, shows her head and the screen. 
Ponytail: This looks like the output of a Markov bot that's been fed bus timetables from a city where the buses crash constantly. 
Offscreen: Whatever, it runs fine for now. 
Ponytail: So does a burning bus.

{{comic discussion}}

1695: Code Quality 2

2016-06-17T14:03:01Z

Domino: Added second panel explanation

1695: Code Quality 2

2016-06-17T13:51:43Z

Domino: Further explanation of the JavaScript reserved words and Scrabble analogy

1695: Code Quality 2

2016-06-17T13:45:06Z

Domino: Began fleshing out explanations of panels

1616: Lunch

2015-12-14T17:39:39Z

Domino: Added ingredient explanations

{{comic
| number = 1616
| date = December 14, 2015
| title = Lunch
| image = lunch.png
| titletext = I'm trying to be healthier, so after I eat this brick of cheese, I'll have a spoonful of grease-soaked vegetables.
}}

==Explanation==

{{incomplete|refine the explanation of the title text to a single explanation}}

The explanation is in the comic itself: Pizza seems way grosser if you imagine eating just the ingredients. Many people, for example, would find simply eating "a block of cheese" as repulsive, but would not object if the same amount of cheese were integrated with a whole meal as in a cheese pizza. Tomato sauce is also typically something that is not served alone (especially not in a glass) though it is a common ingredient in many dishes. Bread may be eaten alone more frequently than the rest of the ingredients but doing so is popularly considered indulgent or not healthy due to bread only having simple carbohydrates and little other nutritional value. Salt is also never supposed to be served by itself, since it is a seasoning.

The title text may refer to a vegetable pizza, which is perceived as a healthier choice due to the presence of vegetables, despite the high fat content of the cheese and oil that are also included on the pizza. The vegetable comment could also be interpreted as having a side salad in addition to the pizza. Common ingredients of certain salads, such as Caesar Salads, is cheese, oil and croutons (bread fried in butter) and is in fact not as healthy as "salads" commonly are believed to be. These fat components could be roughly or derogatorily interpreted as being "grease" which also high in fat and typically referred to in a negative context (e.g.: "That fried fish was greasy and disgusting.")

==Transcript==
:[Cueball and a Cueball-like guy are behind a table. Visible on the table are a bread, a glass, a box with “cheese” and a small heap]
:Friend: What're you having for lunch?
:Cueball: The usual - half a pound of cheese, white bread, a glass of tomato sauce, and some salt.
:Friend: Eww.

:[Caption below the panel]
:Pizza seems way grosser if you imagine eating just the ingredients.

{{comic discussion}}

[[Category:Comics featuring Cueball]]
[[Category:Multiple Cueballs]]

1616: Lunch

2015-12-14T17:30:52Z

Domino: Merged theories about the vegetables line

Talk:1616: Lunch

2015-12-14T17:28:14Z

Domino: Added comment about salt

... I don't think pizza is that bad. Those are sort of things people could really eat ... -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 13:36, 14 December 2015 (UTC)

That's not that gross, IMO. Tomato sauce is pretty much thought of as thick tomato juice. White bread. Salt. Normal things. And this seems to be assuming I wouldn't want to eat a brick of cheese. I do this regularly-ish with brie. [[User:International Space Station|International Space Station]] ([[User talk:International Space Station|talk]]) 13:51, 14 December 2015 (UTC)

I'm not American, so what does he mean by cheese and grease soaked vegetables? {{unsigned ip|162.158.153.101}}
:The cheese is a common ingredient in the pizza seen in the comic, which might be a plain cheese pizza. As for the veggies, this might be a reference to french fries, which is essentially potatoes cooked in a deep fryer which is filled with oil (though I can't be sure with the English definition correlation between grease and oil). {{unsigned ip|108.162.218.148}}
:On this side of the lake pizza's made with dough (white bread), tomato sauce, cheese, and apparently salt the way Randall makes it. Some people put veggies on their pizza, which later get greasy and oily thanks to the cheese; nothing to do with french fries, though I'm told fries on pizza is actually pretty good Though I suppose you'd call them chips over there. {{unsigned|Legofan613}}
::Salt is usually an ingredient in dough, although why it's listed separately is anyone's guess. [[User:Rawmustard|Rawmustard]] ([[User talk:Rawmustard|talk]]) 16:55, 14 December 2015 (UTC)
:::Many pizza places (at least in the central/midwest of the US) will put salt down under the dough to help prevent it sticking to the pan, and also to add a little flavor. Examples would be places like Donatos, Little Cesars, Marions, LaRosas, as well as many Chicago-style pizza joints. The big chains tend not to do this though, not sure why because in my opinion it's details like that that really make the smaller places more delicious. [[User:Domino|Domino]] ([[User talk:Domino|talk]]) 17:28, 14 December 2015 (UTC)Domino

I believe that the "grease soaked vegetables" refers to a "caesar salad" or similar salad arrangement containing oil-based dressing and other ingredients with high fat content. [[User:Spongebog|Spongebog]] ([[User talk:Spongebog|talk]]) 17:23, 14 December 2015 (UTC)

1446: Landing

2015-06-26T20:26:03Z

Domino: Removed incomplete tag - page was properly updated 10 days ago

{{comic
| number = 1446
| date = November 12, 2014
| title = Landing
| image = landingAnimated.gif
| titletext = [LIVE]
}}
Frames of the comic began appearing at midnight ({{w|Eastern Time Zone|EST}}) on November 12, 2014 and updated every five minutes. Together, the images form a {{w|flip book}} which is shown here above. You can find the individual images by clicking on the latest image of the comic on xkcd (go to that by clicking the date above or find it directly at [http://xkcd1446.org xkcd1446.org]).

==Explanation==
This comic changed over time during 12 hours and 15 minutes starting at 0:00 EST (when the comic normally is released) posting 143 pictures that tracked the progress of the {{w|Philae (spacecraft)|Philae}} lander separating from the {{w|European Space Agency}}'s {{w|Rosetta (spacecraft)|Rosetta}} probe to land on comet {{w|67P/Churyumov–Gerasimenko}}. More info can be found here: [http://rosetta.esa.int rosetta.esa.int].

The comic presents the imagined anthropomorphic "thoughts" of the Rosetta spacecraft and the Philae lander (and occasionally other parties) during the hours approaching separation from each other, approach to the comet and finally the apparently successful landing on the comet.

Beginning at [[Media:???65.png|11:05]], the comic includes a '''"Status Report"''' in the lower right corner which summarizes the status of various interested parties and accomplishments, beginning with "Rosetta", "Philae lander", "Mission Control", "Comet 67P", and "Have we landed on a comet?". As events occur in the comic, more status summaries are added to keep track of the changes to the situation and the supposed emotions behind them.

In many pictures a whale can be seen on the surface of the comet - often marked with a "?" as are almost all other parts of the unknown surface at this time. There is also drawn a [[Cueball]] on the surface also marked with a "?" Both are then at some point marked with a ''probably not'' - starting from [[Media:???83.png|12:35]]. The whales are also mentioned in the "Status Report" where they for instance may be listed as "calm" or "(probably) not in space". At [[Media:???122.png|16:00]] the when the entire Earth goes ''AAAAAAAAAAA'' the whales are listed as saying this as well (along with Mission control and U.S. scientists). From this moment "Dolphins and fish" are also mentioned in the report. They are asking if it is the whales that scream. The reference to whales comes from the fact that Philae brought along two harpoons that should have been used to anchor it to the comet. On Earth, harpoons have mainly been used to hunt whales; Randall previously brought up that comparison in [[1402: Harpoons]], suggesting that Philae was programmed to believe it was sent to kill the comet. It is Philae that "dreams" about whales on the surface of the comet which can be seen in the picture for [[Media:???93.png|13:25]] and in the status report.

Some {{w|Douglas Adams}} fans believe these whales and dolphins are references to ''{{w|The Hitchhiker's Guide to the Galaxy}}'' and ''{{w|So Long, and Thanks for All the Fish}}.'' Whales in space have been appearing in fiction and art since the 1960s. However, with the above mentioned reasons for whales, dolphins and fish, this seems less and less likely.

Shortly after release from Rosetta ([[Media:???56.png|10:15]]), Philae calls out 'Spaaaaaaaaaace'; this mimics the {{w|Portal 2}} 'Space core' who, on finally reaching space in the last scenes, gives the same elated cry.

US Scientists presumably wake up at 7:40 EST ([[Media:???96.png|13:40]] UTC) and in the report they now says "Bluuurghhh. What time is it?" to indicate their tiredness. This does not change until 10:25 EST ([[Media:???115.png|15:25]] UTC) so they are slow to wake (2 hours 45 minutes). At this point, they becomes anxious as there are only 10 minutes to landing. This last until there is 15 minutes until news of landing (a reference to the 28 minutes time delay due to the huge distance to the comet). From then on ([[Media:???120.png|15:50]]) they and the mission control (MC) say "AAAAAAA". They stop this when the news should be there - the NOW ([[Media:???122a.png|16:05]]) - and everybody holds their breath indicated by [...] - also MC. Finally ([[Media:???125.png|16:25]]) they and MC become proud (along with Earth) when Philae announces ''I got you a comet.'' It should have stopped there but as Philae bounced around, they then becomes anxious again [[Media:???128.png|16:40]], and then this changes to nervous [[Media:???129.png|16:45]] (switching those emotions with MC). And then suddenly ([[Media:???130.png|16:50]]) it is no longer US Scientists but just plain Scientists - that are nervous. It stays like this during the last few pictures, although they again become anxious, but when Philae announces ''I did it'', they drink wine as indicated with "[wine]" in the report from the second to last picture ([[Media:???134.png|17:10]]).

Randall has written "A big thank-you to [https://twitter.com/elakdawalla Emily Lakdawalla] for help and advice on this comic" in the xkcd page header for [http://www.xkcd.com/1446/ Landing], revealing the possible source of his near real-time data.

At [[Media:???124.png|16:20]] the status report had announced a big '''Yes''' to the questions "Have we landed on a comet" and "Do harpoons work on comets". According to [http://www.bbc.com/news/science-environment-30026398 BBC News], the harpoons did, however, not fire as planned and the lander may have landed, bounced off, and landed again. This would explain the change in "Do harpoons work on comets" to "Don't know" at [[Media:???127.png|16:35]] and the change in "Have we landed on a comet?" to "Yes, at least once" at [[Media:???130.png|16:50]]. According to [http://www.nytimes.com/2014/11/13/science/space/european-space-agencys-spacecraft-lands-on-comets-surface.html?_r=0 The New York Times], radio contact with Philae fluctuated, which would explain the "Anxious", "Nervous", and "Confused" statuses around that time. In the end the lander did land and whereas the Do harppons work status did not change, so did the have we landed on a comet which changed back to '''Yes''' at [[Media:???134.png|17:10]].

The lander bounced three times and ended up in a place where the solar panels where mainly in the shadow. This resulted in the lander shutting down when its own battery ran out of power after only 2-3 days on the ground. This seemed sad, as there was only a small chance that the seasons on the comet would change so that the panels would later receive sun again. However, in the few hours that Philae had on the ground, it still managed to analyze the surface and obtain a lot of useful data - so that part of the mission was still a success already. This all happened after the comic stopped updating.

On June 13, 2015, it was announced that signals had been received on earth indicating that Philae had awoken and that the solar panels were functioning. Ironically, had Philae landed in a place originally out of shadow, it would have already failed before this time (due to overheating), so it was actually fortunate that it landed as it did and would be able to operate during the time that the comet would be closer to the sun. To celebrate the lander's revival, Randall updated the comic, depicting the lander saying "Hi." on the comet's surface.

The comic title was originally "???" (probably to not give away too early what the comic was about), but changed to "Landing" when Randall came on live at five in the morning EST. At that moment the title text also changed from "..." to "[LIVE]". It was also then that the timestamps' timezone switch. At 5:00 AM (EST) the time stamp in the picture naming scheme switched from EST to {{w|Coordinated Universal Time|UTC}} as used in ESA's time keeping, resulting in a jump from [[Media:???53.png|04:55]] to [[Media:???54.png|10:00]] without actually any such delay between the two pictures.

There were however a few pictures with more than 5 minutes of delay (about 11 times five minutes without an update in total during the "live" transmission). The update seemed to have stopped after 137 pictures at 17:15 UTC, 12 hours and 15 minutes after the first picture. (The first picture has number 0, so the last had number 136). But later, sometime after 17:15 UTC, the counter for the last picture was increased to 142 (143 pictures in total), so maybe Randall inserted 6 extra pictures later - however he must then have changed the numbers on the pictures, since the last picture remained the same until mid-June, but with number 142 instead of 136. It is thus now difficult to find out which pictures would have been added later. However, eight pictures were not included in the original table with the [[#Frame by Frame Breakdown|Frame by Frame Breakdown]] below. So it must have been some of those missing pictures that were added later - maybe all of them, as the last three may already have been added before the last picture was released (All 143 pictures are included in the flip-book gif image shown here above). But even 143 pictures at 5 minutes intervals only spans 11 hours and 50 minutes, thus there are still five ''5 minute intervals'' without any picture. See which in the [[1446: Landing/Frame by Frame Breakdown|table]].

==Frame by Frame Breakdown==
*Here is a [[1446: Landing/Frame by Frame Breakdown|link to a table]] with a frame by frame breakdown of all 143 pictures.
*Here is a [[1446: Landing/All pictures|page with all the pictures]] frame by frame.

==Transcript==
:[This transcript gives only the text in the last of the 143 pictures shown in the comic. That which is now shown when clicking to the comic on xkcd.]

:[This is the from the picture with time stamp 17:15.]
:[Showing Philae on a comet.]
:Rosetta: Philae?
:Rosetta: Is everything OK?
:Philae: I landed!
:Philae: I'm on a comet.
:Philae: I'm OK and I'm on a comet.
:[Status report at the bottom-right corner.]
:Status report:
::Rosetta: In space
::Philae lander: Landed
::Mission control: !!!!!
::Comet 67P: Landed on
::Whales: Calm
::Scientists: [Wine]
::Harpoons: Tricky
::Dolphins and Fish: OK
::Have we landed on a comet?: '''YES'''
::Do harpoons work on comets: Don't know
::Earth: !!!!!
::Has anybody tried this before: Nope

:[For the '''full transcript''' of all 143 pictures see '''[[1446: Landing/Transcript]]'''.]

==Trivia==
*There appears to be a brief error between 02:35 and 02:45, where the time until lander separation is shown as 1 hour, counting down to 50 minutes, before being corrected to 75 minutes at 02:50.
**Since this was supposed to be during the "non-live" section before Randall got up (and got live) it is not sure whether this was a "real" mistake, or if he was up anyway, and corrected this timing error when he discovered the plans had change during the approach flight.

{{comic discussion}}
[[Category:Dynamic comics]]
[[Category:Space]]
[[Category:Comics with color‏‎]]
[[Category:Comics featuring Cueball‏‎]]
[[Category:Animals‏‎]]

1527: Humans

2015-06-25T12:05:12Z

Domino: Further explanation of title text. Removal of incomplete tag

{{comic
| number = 1527
| date = May 20, 2015
| title = Humans
| image = humans.png
| titletext = At this point, if we're going to keep insisting on portraying dinosaurs as featherless because it's "cooler", it's time to apply that same logic to art involving bald eagles.
}}

==Explanation==
The comic is set in the future, with two hovering robots discussing ancient history, in particular the clothing styles of kings and queens of the now extinct human species. It appears that robot archeologists have long ago unearthed remains from one or more human civilizations, providing evidence to build a concept of what humans must have looked, acted and even sounded like. Recently they must have discovered or determined new evidence, which presumably indicates the wearing of colorful clothing by human monarchs. Until this occurred they had very little if any reason to believe that any humans wore clothing. Noting the previous knowledge that some humans had metal rings around their heads, they have drawn the conclusion that these formed a separate species "Human Kings" and the crown is a natural outgrowth of the skeleton.

When {{w|dinosaur}} bones were first dug up, the idea that dinosaurs were scaly, reptilian-like creatures was developed with the information available at the time. In recent times, it's been discovered that most dinosaurs actually had {{w|Feathered dinosaur|feathers}}, and in well preserved specimens, often from the {{w|Jiufotang Formation}} in Northern China, feathers of various forms are clearly visible.

As this runs counter to the widespread and long-held image of dinosaurs as dramatic reptiles, the public has been reluctant to accept this new discovery, especially as the addition of feathers often conjures up the image of a giant chicken. (See [[1104: Feathers]]). Had it been discovered that dinosaurs were in fact covered with 6-inch long razor tipped spikes, people may have accepted this immediately as it conforms to the stereotype of dinosaurs as killing machines.

In the same way, the new information on kings and queens being covered in fabric runs counter to the movie inspired image that the robot on the right had about humans, picturing them as being pink warriors that could grow metal out of their heads. The head-metal image may have been inspired by the discovery of kings and queens buried or entombed with their crowns lying on top of their skulls - for example the [http://www.nature.com/news/the-last-medici-may-not-have-died-of-syphilis-after-all-1.12435 Electress Palatine Anna Maria de'Medici]. If the robot beings in this comic don't know enough about human anatomy, they may assume that the metal crown is a specialized part of the human skeleton. Since they themselves are made of metal, they may conclude that that humans also were part metal.

Shown at least some evidence pointing to the truth - that humans typically wore clothing, and that a monarch's crown is only a symbol worn atop the head and not part of his or her body - the robot is predictably disappointed. Humans wearing clothing reduces them, in its opinion, to "big pillows," much like dinosaurs with feathers reduces them from primal beasts to "big chickens." Something made of cloth (or covered in it), at least in this robot's mind, cannot be a significant actor in history.

The robot fails to reason that, among other things, history was what it was, and its wanting things to have been a certain way does not make it so. In addition, just as the clothing-wearing human is more than a mere pillow, and would have held much fearsome power over the world, a feathered dinosaur is not necessarily merely a giant chicken, but is still a powerful killing machine.

The reference to colorful fabric may also be indicative of the popular and mistaken view that all ancient statues (particularly ancient Roman and Greek sculpture) were white. Instead, many of the statues were painted (sometimes rather gaudily due to the low availability of various dyes) and the paint has merely worn off, leading to the present belief that ancient [http://www.smithsonianmag.com/arts-culture/true-colors-17888/?no-ist Athens] was a city of shining white marble porticoes, colonnades and statues. Major landmarks in Washington, DC, were planned to emulate this (perhaps inaccurately) perceived style, including the Capital building and the White House, which, although popularly believed to have been painted white to cover fire damage from the War of 1812, was already being called the "White House" in 1811, well before the fire.

The title text references our failure to change the popular image of dinosaurs to reflect the way they truthfully once were. [[Randall]] jokingly suggests that we should apply the same "featherless is cooler" logic to popular images of bald eagles ([[1211: Birds and Dinosaurs|since they are modern dinosaurs]]), and remove their feathers (only in depictions of them, presumably), leaving them entirely bald. He appears hopeful that such a direct comparison, using the national symbol of the US no less, would provoke the public to change its mind about how dinosaurs are viewed, since modern raptors (birds of prey) are typically viewed with awe and respect, and are not often associated with the "chicken" stereotype mentioned above.

==Transcript==
:[Two robots are hovering in mid-air in the comic; what appear to be their optical arrays are facing each other.]
:Robot 1: You know, new research suggests ancient human kings and queens were covered in colorful fabric.
:Robot 2: Ugh, I like '''movie''' humans more. Screaming pink warriors with metal crowns poking through the skin on their heads!
:Robot 2: Now they're, what, big pillows?
:Robot 2: Science ruins everything.

==Trivia==
It is worth noting that this comic was released a few weeks before the scheduled release of ''{{w|Jurassic World}}'', a reboot of the {{w|Jurassic Park}} movie franchise. This new movie, while supposedly aware of recent advances in dinosaur research, still depicts dinosaurs as giant lizards without feathers. It seems likely that the robot's comment about "pink humans" is targeted at this movie, especially given Randall's many earlier [[:Category:Jurassic Park|references to Jurassic Park]] and his [[:Category:Velociraptors|fear of velociraptors]].

{{comic discussion}}
[[Category:Robots]]
[[Category:Science]]
[[Category:Dinosaurs]]

1527: Humans

2015-06-25T12:02:12Z

Domino: Cleaned up and clarified

{{comic
| number = 1527
| date = May 20, 2015
| title = Humans
| image = humans.png
| titletext = At this point, if we're going to keep insisting on portraying dinosaurs as featherless because it's "cooler", it's time to apply that same logic to art involving bald eagles.
}}

==Explanation==
{{Incomplete|Title text explanation needs improvement. Cleaning up required.}}
The comic is set in the future, with two hovering robots discussing ancient history, in particular the clothing styles of kings and queens of the now extinct human species. It appears that robot archeologists have long ago unearthed remains from one or more human civilizations, providing evidence to build a concept of what humans must have looked, acted and even sounded like. Recently they must have discovered or determined new evidence, which presumably indicates the wearing of colorful clothing by human monarchs. Until this occurred they had very little if any reason to believe that any humans wore clothing. Noting the previous knowledge that some humans had metal rings around their heads, they have drawn the conclusion that these formed a separate species "Human Kings" and the crown is a natural outgrowth of the skeleton.

When {{w|dinosaur}} bones were first dug up, the idea that dinosaurs were scaly, reptilian-like creatures was developed with the information available at the time. In recent times, it's been discovered that most dinosaurs actually had {{w|Feathered dinosaur|feathers}}, and in well preserved specimens, often from the {{w|Jiufotang Formation}} in Northern China, feathers of various forms are clearly visible.

As this runs counter to the widespread and long-held image of dinosaurs as dramatic reptiles, the public has been reluctant to accept this new discovery, especially as the addition of feathers often conjures up the image of a giant chicken. (See [[1104: Feathers]]). Had it been discovered that dinosaurs were in fact covered with 6-inch long razor tipped spikes, people may have accepted this immediately as it conforms to the stereotype of dinosaurs as killing machines.

In the same way, the new information on kings and queens being covered in fabric runs counter to the movie inspired image that the robot on the right had about humans, picturing them as being pink warriors that could grow metal out of their heads. The head-metal image may have been inspired by the discovery of kings and queens buried or entombed with their crowns lying on top of their skulls - for example the [http://www.nature.com/news/the-last-medici-may-not-have-died-of-syphilis-after-all-1.12435 Electress Palatine Anna Maria de'Medici]. If the robot beings in this comic don't know enough about human anatomy, they may assume that the metal crown is a specialized part of the human skeleton. Since they themselves are made of metal, they may conclude that that humans also were part metal.

Shown at least some evidence pointing to the truth - that humans typically wore clothing, and that a monarch's crown is only a symbol worn atop the head and not part of his or her body - the robot is predictably disappointed. Humans wearing clothing reduces them, in its opinion, to "big pillows," much like dinosaurs with feathers reduces them from primal beasts to "big chickens." Something made of cloth (or covered in it), at least in this robot's mind, cannot be a significant actor in history.

The robot fails to reason that, among other things, history was what it was, and its wanting things to have been a certain way does not make it so. In addition, just as the clothing-wearing human is more than a mere pillow, and would have held much fearsome power over the world, a feathered dinosaur is not necessarily merely a giant chicken, but is still a powerful killing machine.

The reference to colorful fabric may also be indicative of the popular and mistaken view that all ancient statues (particularly ancient Roman and Greek sculpture) were white. Instead, many of the statues were painted (sometimes rather gaudily due to the low availability of various dyes) and the paint has merely worn off, leading to the present belief that ancient [http://www.smithsonianmag.com/arts-culture/true-colors-17888/?no-ist Athens] was a city of shining white marble porticoes, colonnades and statues. Major landmarks in Washington, DC, were planned to emulate this (perhaps inaccurately) perceived style, including the Capital building and the White House, which, although popularly believed to have been painted white to cover fire damage from the War of 1812, was already being called the "White House" in 1811, well before the fire.

The title text references our failure to change the popular image of dinosaurs to reflect the way they truthfully once were. [[Randall]] jokingly suggests that we should apply the same "featherless is cooler" logic to popular images of bald eagles ([[1211: Birds and Dinosaurs|since they are modern dinosaurs]]), and remove their feathers (only in depictions of them, presumably), leaving them entirely bald. He appears hopeful that such a direct comparison, using the national symbol of the US no less, would provoke the public to change its mind about how dinosaurs are viewed.

==Transcript==
:[Two robots are hovering in mid-air in the comic; what appear to be their optical arrays are facing each other.]
:Robot 1: You know, new research suggests ancient human kings and queens were covered in colorful fabric.
:Robot 2: Ugh, I like '''movie''' humans more. Screaming pink warriors with metal crowns poking through the skin on their heads!
:Robot 2: Now they're, what, big pillows?
:Robot 2: Science ruins everything.

==Trivia==
It is worth noting that this comic was released a few weeks before the scheduled release of ''{{w|Jurassic World}}'', a reboot of the {{w|Jurassic Park}} movie franchise. This new movie, while supposedly aware of recent advances in dinosaur research, still depicts dinosaurs as giant lizards without feathers. It seems likely that the robot's comment about "pink humans" is targeted at this movie, especially given Randall's many earlier [[:Category:Jurassic Park|references to Jurassic Park]] and his [[:Category:Velociraptors|fear of velociraptors]].

{{comic discussion}}
[[Category:Robots]]
[[Category:Science]]
[[Category:Dinosaurs]]

1138: Heatmap

2015-06-24T16:29:44Z

Domino: Fine-tuning

{{comic
| number = 1138
| date = November 23, 2012
| title = Heatmap
| image = heatmap.png
| titletext = There are also a lot of global versions of this map showing traffic to English-language websites which are indistinguishable from maps of the location of internet users who are native English speakers.
}}

==Explanation==
{{incomplete|no explanation of title text}}
In the comic, by comparing three graphs, [[Cueball]] comes to the conclusion that the audience (presumably the owners/operators of "our site") should adjust their content or advertising to cater to {{w|Martha Stewart}} and {{w|furry fandom|furry}} porn fans. The actual reason the graphs are same is they all match the population concentration in the US, because there is no statistically-significant relation between geographic location and any of the mentioned sub-population.

The title text reflects a similar situation in world maps where the website written in English is read by English-speaking users no matter the location, because their ISP and search providers direct them primarily to English websites, so the visitors' geographic graph matches the graph of the global English-speaking population.

==Transcript==
:[Three near-identical charts of the 48 contiguous United States are shown with heatmaps depicting population density. The first chart is labelled "Our site's users," the second chart is labelled "Subscribers to ''Martha Stewart Living''," and the third chart is labelled "Consumers of furry pornography." Cueball is standing with a stick pointing at the charts.]
:Cueball: The business implications are clear.
:Pet peeve #208:
:Geographic profile maps which are basically just population maps

{{comic discussion}}
[[Category:Comics featuring Cueball]]
[[Category:Comics with color]]
[[Category:Charts]]
[[Category:Statistics]]
[[Category:Furries]]
[[Category:Pet Peeves]]

1138: Heatmap

2015-06-24T16:27:18Z

Domino: Clarified title text

{{comic
| number = 1138
| date = November 23, 2012
| title = Heatmap
| image = heatmap.png
| titletext = There are also a lot of global versions of this map showing traffic to English-language websites which are indistinguishable from maps of the location of internet users who are native English speakers.
}}

==Explanation==
{{incomplete|no explanation of title text}}
In the comic, by comparing three graphs, [[Cueball]] comes to the conclusion that the audience (presumably the owners/operators of "our site") should adjust their content or advertising to cater to {{w|Martha Stewart}} and {{w|furry fandom|furry}} porn fans.

The actual reason the graphs are same is they all match the population concentration in the US, because there is no relation between geographic location and any of mentioned sub-population. The title text reflects a similar situation in world maps, where the website written in English is read by English-speaking users no matter the location, because their ISP and search providers direct them primarily to English websites, so the visitors' geographic graph matches the graph of the global English-speaking population.

==Transcript==
:[Three near-identical charts of the 48 contiguous United States are shown with heatmaps depicting population density. The first chart is labelled "Our site's users," the second chart is labelled "Subscribers to ''Martha Stewart Living''," and the third chart is labelled "Consumers of furry pornography." Cueball is standing with a stick pointing at the charts.]
:Cueball: The business implications are clear.
:Pet peeve #208:
:Geographic profile maps which are basically just population maps

{{comic discussion}}
[[Category:Comics featuring Cueball]]
[[Category:Comics with color]]
[[Category:Charts]]
[[Category:Statistics]]
[[Category:Furries]]
[[Category:Pet Peeves]]

User talk:Domino

2015-06-24T13:15:32Z

Domino: -

Bourbon [[User:Domino|Domino]] ([[User talk:Domino|talk]]) 15:59, 22 June 2015 (UTC)Domino

Milk [[User:Nk22|The Twenty-second. The Not So Only. The Nathan/Nk22]] ([[User talk:Nk22|talk]]) 13:01, 24 June 2015 (UTC)

But not at the same time! [[User:Domino|Domino]] ([[User talk:Domino|talk]]) 13:15, 24 June 2015 (UTC)Domino

User talk:Domino

2015-06-22T15:59:05Z

Domino: F1RST P0ST

Bourbon [[User:Domino|Domino]] ([[User talk:Domino|talk]]) 15:59, 22 June 2015 (UTC)Domino

User:Domino

2015-06-22T15:57:46Z

Domino: Initial publication

Whisky?

Talk:719: Brain Worms

2015-06-22T15:57:02Z

Domino: Added a comment about the corrections I made

I'd like to actually try that. Does anyone know where you can find statistics on most common dreams? [[Special:Contributions/141.101.89.202|141.101.89.202]] 20:19, 13 September 2014 (UTC)

Kinda expected to find it here :-)
This is a list that seems plausible, but it is not exactly scientific study: http://www.thecrazyfacts.com/top-10-common-dreams-meanings/10/

Falling is probably the most common, I have experienced it many times. On the other hand, I have never dreamed of being naked in front of people, although it is supposedly very common.
[[Special:Contributions/141.101.97.206|141.101.97.206]] 09:36, 1 March 2015 (UTC)

I took a stab at expanding the description as requested. If it looks good to you guys feel free to remove the incomplete tag! [[User:Domino|Domino]] ([[User talk:Domino|talk]]) 15:57, 22 June 2015 (UTC)Domino

719: Brain Worms

2015-06-22T15:53:52Z

Domino: Made the requested changes, explaining the individual dreams more thoroughly

{{comic
| number =719
| date =March 26, 2010
| title =Brain Worms
| image =brain_worms.png
| titletext =Hey, it says here that if you dream about your teeth falling out, it means they're spreading.
}}

==Explanation==
{{incomplete|Needs details on the dreams, what they mean and this also goes for the effect of the title text dream - I gave it a shot, what do you guys think?}}

[[Cueball]] is tricking [[Megan]] by pretending to read from a book about a brain worm whose symptoms include specific dreams that she has been having. Many people experience similar dreams with common imagery and feelings, due to sharing common factors in life. One example is cars. Since the majority of the developed world has spent much time driving or riding in cars throughout their lives, cars often become a common theme in dreams. While dream interpretation is far from an exact science, it is generally accepted that driving or riding in a car in your dreams expresses how you feel about your control over your own life. A dream about not fitting or not being comfortable in a car could indicate the dreamer feels out-of-place or uncomfortable in their own life, while dreams about losing control of a car could indicate the dreamer feels their life is out of control.

[[Megan]] of course does not have an infection from these fictional brain worms. [[Cueball]] is taking a "shot in the dark," playing on fears possibly carried by many people that these types of dreams hold a deeper significance which they can't identify. In the comic, Megan appears not to realize that he is pulling a prank on her and begins to get scared.

The title text continues the joke with another common dream, this time about teeth. The commonly-accepted meaning of teeth falling out is a loss of confidence or power in one's life.

==Transcript==
:[Megan sits at a computer desk, and Cueball stands near her holding a book.]
:Cueball: Weird-this parasitic worm infects the brain, damaging the areas responsible for spatial reasoning in dreams. Signs of infection include dreams about not fitting in your car comfortably, driving from the backseat, or veering all over the road.
:Megan: (thinking) Oh God.

:My Hobby: Taking advantage of the fact that some specific dreams are weirdly common, but not everyone who has them realizes this.

{{comic discussion}}
[[Category:Comics featuring Cueball]]
[[Category:Comics featuring Megan]]
[[Category:My Hobby]]
[[Category:Biology]]
[[Category:Dreams]]

1540: Hemingway

2015-06-19T14:36:51Z

Domino: Clarified title text intent

{{Incomplete|New Page}}
{{comic
| number = 1540
| date = June 19, 2015
| title = Hemingway
| image = 1540.jpg
| titletext = Instead of bobcat, package contained chair.
}}

==Explanation==
{{Incomplete|}}

This comic is a reference to the six-word short story {{w|For sale: baby shoes, never worn}}, which has been attributed to famous author {{w|Ernest Hemingway}}, however, [[Randall|Randall Munroe]] explicitly states that this might not be the case at all. The comic plays on the fact that the original story takes the form of a short advertisement that might have been seen in a newspaper, and puts it in a more modern form as titles of products from websites like Amazon and Craigslist.

In keeping with the theme of the original short story, all of these stories are exactly six words.

*For sale: This Gullible Baby's Shoes
*Baby Shoes For Sale By Owner
*<strike>Actually, There's no evidence Hemingway wrote</strike>
*Free Shoes, Provided You Overpower Baby
*For Sale: Weird Baby's Toe Shoes
*For Sale: Baby Shoes [an "Amazon Prime eligible" logo]
**Amazon Prime is a service that offers free shipping of goods purchased on [http://www.amazon.com www.amazon.com].
*<strike>Though popularly attributed to Hemingway, the</strike>
*This Weird Trick Covers Baby Feet!
**For another weird trick see [[1426: Reduce Your Payments]]
*For Sale: Baby Shoes, Just Hatched
*Sale: Seven-League Boots (Expedited Shipping)
*Complete this survey for free shoes!
*''Shoes'', by Ernest Hemingway [citation needed]
**This imitates Wikipedia labeling of dubious claims.
*This is my greatest short story.
*For sale: Baby shoes (-1) [cursed]
*<blink><marquee>Baby Shoes!</marquee><blink>
:Note that the end fof the line is missing a "/". It should be </marquee></blink>.
**<code><nowiki><blink></nowiki></code> is an HTML tag that makes text blink. <code><nowiki><marquee></nowiki></code> is an HTML tag that makes text move from left to right. Both of them are deprecated (intended to be removed later), and are considered to be excessive and annoying.
*For Sale: Baby-sized Saddle, Bobcat
*Hemingway Busted for Craigslist Shoe Scam

The title text, itself another six-word story, makes a reference to the third pane of [[A-Minus-Minus|325: A-Minus-Minus]] in which [[Cueball]] says: 'Instead of office chair, package contained bobcat'

==Transcript==
[Caption above comic:] 
Hemingway's Rough Drafts 
[A list of rough draft titles] 
For sale: This Gullible Baby's Shoes 
Baby Shoes For Sale By Owner 
<strike>Actually, There's no evidence Hemingway wrote</strike> 
Free Shoes, Provided You Overpower Baby 
For Sale: Weird Baby's Toe Shoes 
For Sale: Baby Shoes [an "Amazon Prime eligible" logo] 
<strike>Though popularly attributed to Hemingway, the</strike> 
This Weird Trick Covers Baby Feet! 
For Sale: Baby Shoes, Just Hatched 
Sale: Seven-League Boots (Expedited Shipping) 
Complete this survey for free shoes! 
''Shoes'', by Ernest Hemingway (citation needed) 
This is my greatest short story. 
For sale: Baby shoes (-1) [cursed] 
<blink><marquee>Baby Shoes!</marquee><blink> 
For Sale: Baby-sized Saddle, Bobcat 
Hemingway Busted for Craigslist Shoe Scam 
{{comic discussion}}

1539: Planning

2015-06-17T17:55:24Z

Domino: Smoothed out vocabulary and expanded on some sections

{{comic
| number = 1539
| date = June 17, 2015
| title = Planning
| image = planning.png
| titletext = [10 years later] Man, why are people so comfortable handing Google and Facebook control over our nuclear weapons?
}}

==Explanation==
{{incomplete|First attempt at an explanation.}}
[[Ponytail]] asks [[Megan]] why people seems to be comfortable with {{w|Google}} and {{w|Facebook}} getting so much control of their lives through access to a wealth of personal information. For example, online advertisements are often tailored to the viewer based on their Google searches or web browsing history.

Megan says she does not know. Then she compares Ponytail's comment with the fact that humans have built thousands of {{w|nuclear weapons}}, once used as a source of political control, which are now stored in bases and silos all over the world. She comments that now no one seems to care anymore, and world concerns have moved on to other things like internet privacy, as indicated by Ponytail's original question. In reality there is still much world concern surrounding nuclear weapons proliferation, but it is not the common household topic that it was in, for example, the 1980s.

Megan's best solution to appease Ponytail is to just go with the flow, since this kind of big-picture planning actually doesn't exist (it just seems to happen on auto-pilot), without anyone actually thinking about the consequences. This is of course a scary thought, but it seems like [[Randall]] believes this is what happens in the world (perhaps as human nature), and probably not just with weapons and data. Innovation throughout history has happened to solve specific short-term problems, and rarely has long-term consequences in mind, as evidenced by the debate over {{w|Climate change}} brought about in large part by atmospheric pollution that comes from innovations in transportation, manufacturing and industry.

In the title text we move ahead 10 years, to a similar conversation where the two parts of the above have been inexplicably mixed. A future equivalent to Ponytail asks why we all think it is OK to hand over the control of our nuclear weapons to Google and Facebook, which would certainly be a nonsensical route to take.

This comic was posted on the day after {{w|Vladimir Putin}} had [http://www.nytimes.com/2015/06/17/world/europe/putin-40-new-missiles-russian-nuclear-arsenal.html announced] that Russia would add 40 new {{w|intercontinental ballistic missile}}s to its nuclear stockpile this year.

==Transcript==
:[Megan and Ponytail are walking]
:Ponytail: Why are people so comfortable handing Google and Facebook all this control over our lives?
:Megan: I dunno.
:Megan: Our species built thousands of nuclear weapons, scattered them around the planet, and then moved on to other things.
:Megan: Maybe it's best to accept that some of this big-picture planning is just happening on autopilot.

{{comic discussion}}
[[Category:Comics featuring Ponytail]]
[[Category:Comics featuring Megan]]