explain xkcd - User contributions [en]

2174: First News Memory

2019-07-10T19:36:04Z

172.68.133.180: /* Transcript */

{{comic
| number = 2174
| date = July 10, 2019
| title = First News Memory
| image = first_news_memory.png
| titletext = Psychology researchers say our 'flashbulb' memories of big events can be unreliable, but I clearly remember watching live on CNN as Challenger crashed into and destroyed the Berlin Wall.
}}

==Explanation==
{{incomplete|Created by a FAULTY FIRST NEWS MEMORY. Please mention here why this explanation isn't complete. Do NOT delete this tag too soon.}}
The Challenger exploded in 1986, so Harry's teacher was not showing them the launch live.
==Transcript==
{{incomplete transcript|Do NOT delete this tag too soon.}}
[First Panel]
Ponytail: What's your first news memory?
Cueball: I always like this question! Mine was the 1988 Election.
Meghan: Berlin Wall for me. You?
{{comic discussion}}

Talk:2068: Election Night

2018-11-06T22:50:02Z

172.68.133.180:

This is an early example of using red and blue to denote candidates and parties. Here, McKinley (R) gets blue and Bryan (D) red; it wasn't standardized on blue for Democrats and red for Republicans until after the 2000 election. NBC News having used red/R and blue/D that year, Tom Brokaw was the first to speak extensively of "red states" and "blue states" elevating that to political meme status and leading to standardization. [[Special:Contributions/162.158.78.166|162.158.78.166]] 14:36, 5 November 2018 (UTC)

:I was just going to mention the hat :) [[Special:Contributions/108.162.246.191|108.162.246.191]] 14:57, 5 November 2018 (UTC)

I distinctly remember the reporting during the 1980 election (Reagan vs. Carter) that the TV news used blue for Republicans and red for Democrats. I don't know why they later switched, but I have always assumed that Democrats got offended by the use of red (the color of the USSR's flag and many other communist organizations) for their party. [[User:Shamino|Shamino]] ([[User talk:Shamino|talk]]) 15:19, 5 November 2018 (UTC)

:Beyond having one party being red and the other blue, there was no consistent color-coding scheme for the two major parties either from election to election or between news agencies prior to 2000. Both parties still officially list red, white, and blue as their colors. [[Special:Contributions/162.158.79.149|162.158.79.149]] 15:24, 5 November 2018 (UTC)

::There's a long history about red and blue states, all of which comes directly from the media reporting the different parties. It's interesting to note that in Europe, the liberal parties are red and the conservative parties are blue (opposite of the US), and the fact that red is the color of the USSR has nothing to do with the Democrats "not wanting to be red," they didn't choose the colors. [[User:Zachweix|Zachweix]] ([[User talk:Zachweix|talk]]) 16:51, 5 November 2018 (UTC)
::: Actually liberal parties tend to be in the yellow/orange part of the spectrum (see LibDems in the UK or FDP in Germany), red is for parties with more (historical) socialist leanings (Labour, SDP). [[Special:Contributions/188.114.102.4|188.114.102.4]] 19:25, 5 November 2018 (UTC)
:::: Rather most liberal parties in Europe in the last decades moved on the political right of Europe's conservative parties, emphasizing an immigrant-critical, corporate-friendly program over civil liberties. So 'liberals' has another ring to Europeans than to US-Americans. Sebastian --[[Special:Contributions/172.68.110.88|172.68.110.88]] 18:20, 6 November 2018 (UTC)
:: European politics, unlike US politics, is multidimensional. [[User:Erkinalp|Erkinalp]] ([[User talk:Erkinalp|talk]]) 16:59, 5 November 2018 (UTC)

:: IIRC, blue was used for incumbents on some stations, red for challengers, and in 2000, blue stuck as the color of the democratic party, {{unsigned ip|162.158.79.107}}

:::It seems to have been chosen pretty much arbitrarily. As much as I follow politics, I never heard of any clear association where the Democrats were blue and Republicans red -- ''or vice versa'' -- until after election night in 2000. Before then, there was no well-known standard as to which party would get which color on a map. The standard colors we have now only stuck based on the coverage from election night (and afterward) in 2000. --[[Special:Contributions/172.68.150.46|172.68.150.46]] 17:26, 5 November 2018 (UTC)

God I feel awful for the Civil war vets with PTSD who decided to reside in Chicago. [[Special:Contributions/172.69.33.11|172.69.33.11]] 17:05, 5 November 2018 (UTC)

What is the 'Needle' referring to? [[Special:Contributions/162.158.142.4|162.158.142.4]] 17:46, 5 November 2018 (UTC)
: The Traumatic Needle can be found here... https://www.vanityfair.com/news/2018/11/the-new-york-times-election-needle-is-back-with-a-few-new-safety-features {{unsigned ip|162.158.106.126}}

I was reading this, expecting the last page (or the title text) to have someone commenting that lecturing to modern people about how things were in the past is a pretty trivial or bizarre waste of something as momentous as time travel; and top hat guy to reply that he didn't come to bring them a message, he's just avoiding the fireworks because he's fed up of the modern election-night media circus. -- [[User:Angel|Angel]] ([[User talk:Angel|talk]]) 17:50, 5 November 2018 (UTC)

Does anyone have a source for the 1896 reporting via fireworks referred to here? I've done a few Google searches, but so far haven't found anything. Historic issues of the Chicago Tribune is behind a paywall, so I can't go look there directly. [[User:Shamino|Shamino]] ([[User talk:Shamino|talk]]) 18:40, 5 November 2018 (UTC)
: I assume Randall made this up? [[Special:Contributions/173.245.48.171|173.245.48.171]] 18:49, 5 November 2018 (UTC)
::Telling from [https://img.newspapers.com/img/thumbnail/349884040/250/150/5939_4729_418_251/0/yes/5893_4842_511_25.jpg this snippet], it seems legit. --[[Special:Contributions/172.68.50.172|172.68.50.172]] 18:54, 5 November 2018 (UTC)
::: It is legit, scroll through the first result here:[https://chicagotribune.newspapers.com/search/#lnd=1&query=blue+to+indicate+McKinley%27s+election&ymd=1896-11-01]. (Update: I have no idea how to format this properly, somebody that knows how please fix this and feel free to remove this message) --[[Special:Contributions/162.158.79.149|162.158.79.149]] 21:56, 5 November 2018 (UTC)
::::I fixed your problem, just start your comment at the beginning of a line. --[[User:Dgbrt|Dgbrt]] ([[User talk:Dgbrt|talk]]) 22:31, 5 November 2018 (UTC)
::::Thanks for the link. Unfortunately, it is blocked by the Tribune's paywall. [[User:Shamino|Shamino]] ([[User talk:Shamino|talk]]) 22:36, 5 November 2018 (UTC)
:::::Here's the transcription of that article (I have access through my ancestry account): "..."--[[Special:Contributions/172.68.65.6|172.68.65.6]] 14:05, 6 November 2018 (UTC)
::::::Copyright problems. There is a paywall and we don't want to pay for it. Please explain the content with your own words or present a free source which may be possible because it's more than 100 years old. --[[User:Dgbrt|Dgbrt]] ([[User talk:Dgbrt|talk]]) 22:14, 6 November 2018 (UTC)
::::Is the hovertext quote legit, too? –[[User:P1h3r1e3d13|P1h3r1e3d13]] ([[User talk:P1h3r1e3d13|talk]]) 23:15, 5 November 2018 (UTC)

There needs to be a reference to "Dewey Defeats Truman" in the explanation. When Megan says they will get the election results the next day this would not have been the correct reults. The Chicago Daily Tribune published a newspaper with the headline "Dewey Defeats Truman" but the newspaper article was wrong. Because of publishing deadlines they published what they thought was correct but more results came in later and Truman won. With the internet and 24 hour news stations this problem does not exist. Also perhaps there could be a reference to Florida's "hanging chad" which caused caused the election results to be decided in the coarts and not overnight. [[User:Punchcard|Punchcard]] ([[User talk:Punchcard|talk]]) 15:20, 6 November 2018 (UTC)

'''Papal conclave'''

No one else sees parallels to the {{w|Papal conclave#Smoke colors|smoke colors}} after a papal conclave? It's white and black there, but the principle is the same (no telecommunication, ...) --[[User:Dgbrt|Dgbrt]] ([[User talk:Dgbrt|talk]]) 20:15, 5 November 2018 (UTC)

Is the needle a relative of the good old swingometer. The BBc's favoured method of showing predicted General Election results based on polling and a uniform swing. [[Special:Contributions/162.158.39.41|162.158.39.41]] 00:06, 6 November 2018 (UTC)
: As depicted by [https://youtu.be/dVI5ZOT5QEM Monty Python]? [[User:Shamino|Shamino]] ([[User talk:Shamino|talk]]) 13:42, 6 November 2018 (UTC)
Think Top Hat Guy is going to become a new character?

explain xkcd talk:Editor FAQ

2018-10-13T02:55:57Z

172.68.133.180: Comment

Feel free to enter any question about editing this Wiki and don't forget to sign you comment. --[[User:Dgbrt|Dgbrt]] ([[User talk:Dgbrt|talk]]) 21:18, 31 May 2018 (UTC)

== Formatting of explanations ==

Many pages contain tables where a definition list would be 1) easier to read 2) mobile friendly, for example: [https://www.explainxkcd.com/wiki/index.php?title=1957:_2018_CVE_List&oldid=160469 1957].

I was also involved in rewriting the transcript for [[1963]], where the discussion came up about how those should be styled. ("as if you were reading the comic to someone")

I think we should have a small style guide to encourage sane formatting. What else should such guidelines contain?

Edit: One more thing I'd love to see: semantic headlines (i.e. < h3> headlines for explanation subchapters instead of < h2> which is the same level as the explanation itself)

(Sidenote: I've been active on explainxkcd for quite some time, but only now got around making an account.) [[User:Gir|//gir.st/]] ([[User talk:Gir|talk]]) 15:01, 19 August 2018 (UTC)

:Thanks for your remarks. First: There is no need to start every new sentence at a new line. Tables are meant for small content in all other cases it's bad layout. I recently changed this [[2034: Equations]] to a proper floating text. At the transcript tables should never be used, even when there is a table in the comic image it should be described by text. The guide here was mainly written by me because there was nothing like this here before. Some people already helped and I'm happy for any further remarks to enhance it. And this table issue is definitely one; I just not wanted to be the only (arrogant) layout master. Your help is welcome to write something, otherwise I will do so soon.
:For headlines we don't use HTML-code but WIKI-code. The main headlines are written like this: <nowiki>==Explanation==</nowiki>, <nowiki>==Transcript==</nowiki>, and (optional) <nowiki>==Trivia==</nowiki>. Headlines inside that chapters should be done in this way: <nowiki>;Subtitle</nowiki>. The preceding semicolon causes the entire line to be rendered in bold. Only when the explanation really needs sub-chapters it can be done by this: <nowiki>===Sub header===</nowiki> (three equal signs before and after the text). I will put this also into the FAQ.
:Welcome and thanks for helping. PROTIP: Always use the preview button to check the layout before saving. --[[User:Dgbrt|Dgbrt]] ([[User talk:Dgbrt|talk]]) 13:39, 20 August 2018 (UTC)
::hi, I'm aware about the headlines and stuff, it was just shorter to write it this way in the comment. I see you started a bit with a styleguide already; I hope I can contribute to it next week, when things cool down at work a bit. //gir.st/, who is to lazy to log in [[Special:Contributions/172.68.51.190|172.68.51.190]] 06:51, 24 August 2018 (UTC)

So, one more thing, regarding 'What is the proper layout for headers?'. I think we should better use small <code><nowiki>====headings====</nowiki></code> instead of just description titles (<code><nowiki>;bold text</nowiki></code>), since it makes the intent clearer. what is your reasoning behind suggesting it the other way round? greetings, [[User:Gir|//gir.st/]] ([[User talk:Gir|talk]]) 14:49, 25 August 2018 (UTC)
:Thanks for your input and of course Wiki markup headers should be valid. I just believe that the simplest way should also be valid for less experienced writers. When a new explanation starts it's often awful and chaotic; giving a simple but effective structure at the beginning helps against this chaos. So, I'm thinking about dividing the section "What is the proper layout for headers?" (it's a question because it's a FAQ) into two subsections:
:*easy: a semicolon, the colon at the following paragraph may be mentioned - but I'm not sure about the colon because it should be ''easy''
:*advanced: <code><nowiki>===headings===</nowiki></code> if the comic really can be divided into chapters; <code><nowiki>====headings====</nowiki></code> as a replacement for the semicolon; and <code><nowiki>==headings==</nowiki></code> is forbidden because it belongs to expl, trnsc, trivia. The semicolon, colon issue should be mentioned here.
:Please consider that there was many chaos in the past and many writers will do their edits without reading this FAQ. So keeping this simple as possible seems to me to be inevitable. And dividing sections by using the semicolon for a header is still much better than many of those tables. --[[User:Dgbrt|Dgbrt]] ([[User talk:Dgbrt|talk]]) 17:41, 25 August 2018 (UTC)
::Based on this discussion I edited the current comic here: [http://www.explainxkcd.com/wiki/index.php?title=2037%3A_Supreme_Court_Bracket&type=revision&diff=161880&oldid=161841] and compare it to this former version [http://www.explainxkcd.com/wiki/index.php?title=2037:_Supreme_Court_Bracket&diff=prev&oldid=161841]. Do not focus on the edits, just scroll down to the resulting page.
::This brought me to another important issue: NO links in a header. At Wikipedia this is also not welcome. This site isn't Wikipedia but in this case I feel this is a good rule. But the TOC (Table of content) is shown in the preview while it's not at the resulting page. The result is preferred but the TOC in the preview may confuse editors here.
::So, I'm still looking for simple instructions, layouts which advanced people always can enhance.
::And consider that some editors are probably younger than xkcd is. Not sure about this but there are definitely young people here and I welcome them all. And I'm NOT getting old like Randall sometimes feel, I like to support every editor despite any other background. And this has to be simple on the first place. STOP(I could talk much more) --[[User:Dgbrt|Dgbrt]] ([[User talk:Dgbrt|talk]]) 20:49, 25 August 2018 (UTC)
:::Sorry, I missed this. I'd personally go with the "advanced" option, but mentioning both is fine too. Nice work on 2037! Really enjoying our conversations about this, I hope i'm not a bother ;-) [[User:Gir|//gir.st/]] ([[User talk:Gir|talk]]) 11:20, 28 August 2018 (UTC)
OK, after a few days and some more edits (for example see here: [[2035: Dark Matter Candidates]]) I believe this would be the best guide:
*<code><nowiki>====headings====</nowiki></code> should be preferred because the advantage is that each header has it's own edit button. One other advantage is that the header text will be shown at the summary in the history.
*The semicolon may be used as a preliminary layout for new comics until it's clear of what content the explanation is composed of.
*On more rare circumstances the <code><nowiki>===headings===</nowiki></code> may divide the explanation into different larger chapters.
*<code><nowiki>==headings==</nowiki></code> is reserved to the general layout and has not to be used.
And I still oppose to the colon at the beginning of any paragraph at all. Any thoughts? --[[User:Dgbrt|Dgbrt]] ([[User talk:Dgbrt|talk]]) 13:17, 29 August 2018 (UTC)

== Please '''''do not''''' use semicolon-lines as "headings" ==

Hi, sorry to butt in, but I was going to mention this here anyway after I saw it in the FAQ. Please ''don't'' continue to give this advice to editors:
<blockquote>For headlines you have to use Wiki-style code. The simplest way is a preceding semicolon at the beginning of the line which causes the entire line to be rendered in bold.<ref>§ [[explain xkcd:Editor FAQ#What_is_the_proper_layout_for_headers.3F|What is the proper layout for headers?]] of the [[explain xkcd:Editor FAQ|Editor FAQ]]</ref>

====References====
<references/>
</blockquote>

The [[explain xkcd:Editor FAQ#In_which_case_tables_are_meaningful_and_when_not.3F|previous Editor FAQ section]] has it right: in wikicode, the semicolon opens a ''description list'', and will be translated into equivalent HTML. In other words, the wikicode is processed as follows:
{| class="wikitable"
|-
! Wikicode !! HTML
|-
| style="vertical-align:top;" |<pre>; xkcd
: a popular webcomic</pre>
|<pre><dl>
<dt>xkcd</dt>
<dd>a popular webcomic</dd>
</dl></pre>
|}

One or more lines started with a semicolon ''must'' be followed by at least one line that starts with a colon, to provide the <code><dd>...</dd></code> part of the description list block.

It is a {{w|Help:List#Common_mistakes|common mistake}} to use semicolon-lines as "headings". Unfortunately the result is '''invalid HTML''', since the HTML spec requires that a <code><dl></code> block contain:
<blockquote>Zero or more groups each consisting of one or more dt elements followed by one or more dd elements</blockquote>
It's fine to have multiple semicolon-lines in a row (as the HTML standard allows for groups of several <code><dt>...</dt></code> blocks in sequence), but they must '''always''' be followed by at least one <code><dd>...</dd></code> block, created in wikicode by following a line started with a semicolon with another line that starts with a colon.

Just like lines started with <code>*</code> or <code>#</code>, a line started with a <code>;</code> creates a list element, and has syntactic requirements that must be followed. Abusing the description-term wikicode for purposes other than description-list creation not only breaks the HTML on the resulting page, but it makes the content much harder for screen readers and other assistive technologies to parse and accurately reproduce.

(And, yes, technically Mediawiki's use of <code>:</code>-lines for indenting, as on talk pages, is also invalid since it creates a <code><dl><dd>...</dd></dl></code> block with no <code><dt></code> element. So it's bad enough on talk pages, it's 100x worse to encourage doing it on '''article''' pages.) Please consider removing this bad advice from the Editor FAQ. Thanks. -- [[User:FeRDNYC|FeRDNYC]] ([[User talk:FeRDNYC|talk]]) 05:48, 5 September 2018 (UTC)

:Thanks for your remarks, that's why I started this FAQ and the discussion about it. Especially the header section is still preliminary, just check the section above here at the talk page.
:My first purpose is to keep it as simple as possible for writers having not much or no knowledge about wiki code or HTML. After that an advanced section should follow and define the rules for a complete article.
:Please check my summary from 29 August 2018 just above here. You're right the semicolon isn't a header, that's why I'm saying it should be used only temporary. And after reading your remarks here I would propose a single line with bold text and a following empty line instead of that semicolon thing.
:Keep it simple for people who just want to write something here; advanced users will change it to an appropriate layout later. Consider: When a new comic is out the explanation often starts in chaos. And for now I'm really happy that the overwhelming usage of tables is stopped.
:Let me know what you do think about the bold text line (not by semicolon) and the more sophisticated header guidance for the final layout as I've mentioned on 29 August 2018. --[[User:Dgbrt|Dgbrt]] ([[User talk:Dgbrt|talk]]) 12:45, 5 September 2018 (UTC)
::And of course the usage of a semicolon should also be mentioned together with the colon because it's a list. An entire paragraph "How do I format lists?" has still to be written yet. --[[User:Dgbrt|Dgbrt]] ([[User talk:Dgbrt|talk]]) 12:51, 5 September 2018 (UTC)
::One more: I've checked the definition for <code>dd/dt/dl</code> and it's clear the <code>dd</code> tag must be followed by at least one (either <code>dt</code> or <code>dl</code>) child. This tells me that the indent done by a colon is proper HTML. This is very important because every transcript since the first comic uses this indentation. --[[User:Dgbrt|Dgbrt]] ([[User talk:Dgbrt|talk]]) 13:20, 5 September 2018 (UTC)

The FAQ says to use <code><nowiki>{{incomplete transcript|YOUR REASON}}</nowiki></code> but instead of rendering like this (like with the incomplete template):

{{notice|'''This transcript is incomplete:''' ''YOUR REASON'' If you can address this issue, please '''[{{fullurl:{{{target|{{FULLPAGENAME}}}}}|action=edit}} edit the page]!''' Thanks.}}

It renders like this:

{{notice|'''This transcript is incomplete.''' Please help [{{fullurl:{{{target|{{FULLPAGENAME}}}}}|action=edit}} editing] it! Thanks.}}

Can someone please change this? [[Special:Contributions/172.68.133.180|172.68.133.180]] 02:55, 13 October 2018 (UTC)

1963: Namespace Land Rush

2018-10-04T06:51:18Z

172.68.133.180: /* Transcript */ Fixed page being zoomed out. May have gone overboard on the zero-width spaces

{{comic
| number = 1963
| date = March 5, 2018
| title = Namespace Land Rush
| image = namespace_land_rush.png
| titletext = You can also just mash the keyboard at random, but you might end up with a gibberish name no one can pronounce.
}}

==Explanation==

When a new web service starts, such as a forum, a social media server or an email portal, the people who sign up get to choose their username on the service, which, in most cases, blocks future users from using those usernames. Common names such as "john" are likely to be taken quickly. This is analogous to the way that land was distributed in America, with the first to claim able to choose the best land.

This comic is a list of usernames [[Randall]] suggests should be used if they are available.

The title text is a self-reference to "xkcd"; the name of the comic is a purposefully unpronounceable phrase created by Randall.

(Note: for a more serious list of problematic user names to block from a service provider’s point of view, see [https://ldpreload.com/blog/names-to-reserve Hostnames and usernames to reserve] as well as [https://tools.ietf.org/html/rfc2142 RFC 2142].)

==Table==
{| class="wikitable"
!style="width:30%"|Entry
!style="width:70%"|Explanation
|-
!colspan=2|Straightforward (Usernames that a person would use under typical circumstances)
|-
|<Your usual username, if any>
|Most internet users will have settled on some unique handle that they try to use across all platforms. Even if this wasn't a new service, most people would try this first.
|-
|<Your given name>
|More rare is using one's nickname or first name as their username, since the amount of common names will mean many users share a name. Thus, if you can get your given name, you will have a simple username that many others wanted, and without resorting to prefixes or numbers (i.e. Xx_MyName00_xX)
|-
|<Your full name>
|Similar to your given name, but slightly more unique since a last name and/or middle name is added.
|-
|<Initial><Surname>
|A common second choice if a given or full name is already in use.
|-
|<Surname>
|Possibly available if your last name is more uncommon; names like "smith" or "kim" will probably be taken faster than even given names.
|-
!colspan=2|Recognizable (Usernames that would make it look like the email came from an official source within the organization named)
|-
|Google
|Registering the name "Google" would allow for communicating on the site (or even outside of it) with a name that appears to be an official Google account. For any of the examples in this section, you would select the names for the same reason. This has been done in the past with both [https://twitter.com/BiIIMurray humorous] and [http://www.chicagotribune.com/bluesky/technology/ct-russian-twitter-account-tennessee-gop-20171018-story.html nefarious] results.
|-
|iPhone
|Many services would mark messages sent from an iOS client on iPhone as "sent from iPhone".
This could make people believe that your messages are sent from an iPhone even if you don't own one.
|-
|Facebook
|Similiar to Google above.
|-
|Bitcoin
|One could pose as the Bitcoin Core development group by using this handle and/or scam uninformed users interested in cryptocurrencies.
|-
|Obama
|Impersonating a president, supposedly to send messages as them to make them seem bad (or not).
|-
|Canada
|Impersonating a whole country might get you in trouble.
|-
|NFL
|The American "National Football League"
|-
|Garfield
|In the original "GMail" service on the Internet, the G stood for "Garfield"
|-
|<Your city>
|Impersonating the official account for your place of residence.
|-
|NASA
|The American "National Aeronautics and Space Administration". Randall worked there as a contract programmer and roboticist.
|-
|<Name of person who runs the service>
|Impersonating the site owner can get you the trust of users.
|-
!colspan=3|Causing Trouble (Usernames that might cause errors when mixed with the service's back-end code)
|-
|User
|This is usually the default username for a non-administrative account. This may trick a user that this is owned by the operator of the service.
|-
|Username
|See above.
|-
|Name
|See above.
|-
|You
|Many services display "You" as the signed-on user, so naming oneself "You" makes users think that they are you/they are signed on when they aren't.
|-
|Guest
|Attempts to fool users into thinking that they have a guest account.
|-
|Account
|The opposite of "Guest" (someone without an account). However, for someone with an account, their username will usually be displayed.
|-
!colspan=2|Causing More Trouble
|-
|Admin
|Impersonating to be a system administrator will let someone fool people and cause a lot of trouble. In particular, it could be used to obtain SSL certificates by demonstrating ownership of a supposedly internal address.
|-
|Administrator
|See above.
|-
|System
|Pretending to be a system-controlled account - might give permissions if the server checks by name.
|-
|<Name of service>
|Pretending to be the official account of the service.
|-
|Help
|Pretending to be the help account. This could led to many questions from new users.
|-
|Error
|This may trick users to do what the user says as they could claim that it was a legitimate error.
|-
!colspan=2|Impossible to Say
|-
|Hyphen-Emdash
|Could be read "Hyphen hyphen Em dash" or "Hyphen dash em dash"
|-
|Dash-8hyphen-8
|Could be read "Dash dash eight hyphen dash eight" or "Dash hyphen eight hyphen hyphen eight". "Hyphen eight" sounds like "hyphenate".
|-
|Zero0ne2numeral2
|Could be read "Zero zero one two numeral two" or "Zero zero ne two numeral two" or "Zero oh ne two numeral two".
|-
|KrisasinHemsworth
|This would be confusing to say out loud, as it would sound like the user was saying that their username was "Chris," spelled the same way that famous actor {{w|Chris Hemsworth}} spells his name. However, the actual username uses the name "Kris," spelled a completely different way than Chris Hemsworth's name, and the phrase "as in Hemsworth" being also part of the username, rather than a clarification of the spelling of "Kris" as would be assumed.
|-
|TheWord&Ampersand
|This would also be confusing and difficult to communicate, as anyone trying to read the username to someone else would say "The word ampersand ampersand" which could be interpreted as "ampersand&" or "ampersand ampersand". Having the phrase "the word" in front of a symbol makes it quite difficult to communicate which variation of ampersand (word or symbol) is actually being referred to.
|-
|ZettaWith3Teees 
|Read aloud, this would lead the listener to expect a username of 'Zettta'. Clarifying that "with three tees" is text and not description would in turn make it difficult to explain the spelling of 'Zetta' with two 't's, and 'Teees' with three 'e's.
|-
!colspan=2|Misc
|-
|<Single Letters> and <Single Numbers>
|These are highly valuable. The Twitter handle "@n" for example is constantly bombarded with offers and hacking attempts.
|-
|<Common Words>
|Also highly valuable; overlaps with "Recognizable" and "Causing (more) Trouble".
|-
|<SQL/JS Injection>
|Codes such as "Drop Table" intended to cause errors or even damage the service's back-end code. (See [[327|Comic 327]])
|-
|ASDF and QWERTY
|Since those keys are right next to each other (on English language layouts), they are often typed as placeholders.
|-
|Yes
|This might be a Beret Guy-esque misunderstanding when filling out the sign up form. When encountering the form field "Username:" Randall typed "Yes" (as in "yes, I want a username") instead of specifying it.
|-
|Bot and Computer
|Pretending to be a bot.
|-
|Blocked
|When users get banned or blocked, their name is often replaced by a string like this.
|-
|Deleted
|Some services like Reddit keep up user posts and data after account deletion, marking the content as submitted by the user "[Deleted]" or "Deleted".
|-
|Jeeves
|Might refer to {{w|Ask Jeeves}} (now Ask.com), a Internet Search Engine.
|-
|Narrator
|In books, radio plays and movies it is quite common to have a narrator explain parts of the story. In an online forum however, it is not.
|-
|Internet
|"The Internet" sometimes refers to a large group of users, the collective hive-mind if you will. However, there cannot be a single user account speaking on behalf of them, as they aren't a single entity.
|-
|NPC
|Non-player character
|-
|Password
|If the user accidentally typed their (not-very-secure) password into the username field, this would be the result.
|-
!colspan=2|Permissive Character Sets
|-
|<Space>
|Usernames containing only whitespace can not only be confusing for other people, but often systems 'trim' (remove whitespace at the beginning and end) user input. If the username was only made of spaces, after trimming it would be completely empty, which can cause a whole slew of other problems.
|-
|<nowiki>@ é |</nowiki>
|The @ seperates the local part from the domain part of email addresses. If a service decides to create email addresses for their users, they will have a hard time if they allowed the "at" character as part of a username.
é is encoded in many character sets, like Latin-1 and Unicode. In Unicode, it can even be described either "U+00E9 LATIN SMALL LETTER E WITH ACUTE" or as the sequence "U+0065 LATIN SMALL LETTER E" and "U+0301 COMBINING ACUTE ACCENT". If a system uses {{w|Unicode normalization}} after the check if the username is available, this might allow someone to take over someone else's account.
|-
|<nowiki>“ ” " ‘ ’ ' `</nowiki>
|Various quotation marks.
“, ”,‘ and ’ (Unicode quotes): can expose a system's inability to handle multi-byte-encodings. If they are converted to their ASCII counterparts, they might cause code injections.
' and " (ASCII single and double quotes): often used as string delimeter (causing the rest of the name to be interpreted as HTML, or worse, code.
` (ASCII grave / backtick): Sometimes used as string delimeter; Perl (which some websites are still programmed in) executes commands ("shell code") when between backticks.
|-
|<NBSP>
|Unicode character "U+00A0 NO-BREAK SPACE". Similar attack vector as <Space>, but some programming languages will not strip non-ASCII whitespace (therefore the validation will pass).
|-
|<nowiki>\ . #</nowiki>
|The backslash is very often used for "escape sequences", that get expanded to other characters. (\n -> newline, \t -> tab character, \b -> backspace character (deletes the character to its left), etc.)
The period can be problematic in emails. RFC 2822 forbids periods at the beginning or end of the local part or more than one period in a row.
In URLs, the Octothorpe (#) is used as the 'anchor'. Anything following a # will not be transmitted to the server. If a user is named 'logout#blahblah' (which might be a valid username) and the user profile is located at http://example.com/<the_username>, the server might generate the URL http://example.com/logout#blahblah. Since the URL will be truncated at the '#', any user attempting to view this profile will be logged out of the service.
|-
|<RTL override>
|The right to left override is an Unicode character which forces text after it to be laid out right to left. Thus, in left-to-right locales, it flips everything after it. This can be rather amusing if permitted. (See [[1137|Comic 1137]])
|-
|<nowiki>– - _ /</nowiki>
|Includes both the em-dash and the hyphen, which are easily confused and are highly unusual for user names. The forward slash is also the path delimeter for URLs; if user profiles are located at e.g. http://example.com/user/the_username, this can cause obvious issues.
|-
|<Any emoji>
|Current databases are not set up to store emojis as characters.
|-
|","
|In CSV files this separates one column or data item from another. This could cause bugs if the usernames are used as part of a CSV file since the next column on the row could be left blank filled with other data.
|-
|<nowiki>&NBSP</nowiki>;
|The special entity in HTML (web page language) for a non-breaking space, or a space that prevents an automatic line-break at its position. When rendered as part of an HTML page without sanitization, this would only display a space.
|-
|<nowiki></HTML></nowiki>
|This is trying to inject code for the web page using the user name. If the user name is not sanitized and does not have special characters encoded, this HTML end tag could end the HTML document, leading to page errors.
|-
|&LT;/HTML&GT;
|&LT; and &GT; are special character entities in HTML that represent < and >, repectively. So all together, when rendered as part of an HTML document, this would print "<nowiki></HTML></nowiki>" Although this would look similar to the previous <nowiki></HTML></nowiki> entry, it would be unlikely to cause problems as the symbols are not interpreted if encoded as special entities.
|-
|OkThisIsKindOfConfusingButIt's <LessThan\ForwardSlashHTML GreaterThanActualGreaterThan Symbol>Yes,ThatWasAllPartOfThe Name,ButSoIs...Ok,LetMeStartOver”
|The abundance of symbols and symbol related worlds and phrases such as ActualGreaterThanSymbol would make this extremely difficult to vocally communicate to another person. This difficulty is further compounded by the parts at the beginning and end, which sound like they are part of the explanation despite being part of the name itself.
|-
|}

==Transcript==
{{incomplete transcript|Layout not standard (eg. indentation) and a short description at the beginning about what is shown should be given.}}
'''Namespace Land Rush Cheat Sheet'''
(Note: if an item is "quoted", it is meant literally, otherwise the reader is supposed to substitute their own information for words in <angle brackets>)

When a new service appears that lets you register a name, here are some you may want to try and get first:

* Straightforward
** <Your usual username, if any>
** <Your given name>
** <Your full name>
** <Initial><Surname>
** <Surname> (Bold & Slightly Unconventional)

* Recognizable
** "Google"
** "iPhone"
** "Facebook"
** "BitCoin"
** "Obama"
** "Canada"
** "NFL"
** "Garfield"
** <Your city>
** "NASA"
** <Name of person who runs the service>

* Causing Trouble
** "User"
** "Username"
** "Name"
** "You"
** "Guest"
** "Account"

* Causing More Trouble
** "Admin"
** "Administrator"
** "System"
** <Name of service>
** "Help"
** "Error"

* Impossible to Say
** "Hyphen-Emdash"
** "Dash-8hyphen-8"
** "Zero0ne2numeral2"
** "KrisasinHemsworth"
** "TheWord&Ampersand"
** "ZettaWith3Teees" 

* Misc
** <Single Letters>
** <Single Numbers>
** <Common Words>
** <SQL/JS Injection>
** "ASDF"
** "QWERTY"
** "Yes"
** "Bot"
** "Computer"
** "Blocked"
** "Deleted"
** "Jeeves"
** "Narrator"
** "Internet"
** "NPC"
** "Password"

* Permissive Character Sets
** <Space>
** <NBSP>
** <RTL override>
** <Any emoji>
** "<nowiki>&NBSP</nowiki>;"
** "<nowiki></HTML></nowiki>"
** "&LT;/HTML&GT;"
** one or more of the following symbols: <nowiki>@ é | “ ” \ . # " ‘ – - _ / ’ ' `</nowiki>
** "," (including quote marks)
** "OkThisIsKindOfConfusingButIt's<LessThan\ForwardSlashHTMLGreaterThanActualGreaterThanSymbol>Yes,ThatWasAllPartOfTheName,ButSoIs...Ok,LetMeStartOver”"

{{comic discussion}}

Talk:2026: Heat Index

2018-08-30T22:23:29Z

172.68.133.180:

Look at the formula, then at the table and try to tell with straight face that those tables were computed from the formulae and not the other way around. -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 22:38, 30 July 2018 (UTC)
: The Wikipedia page explicitely says that the various formulaes try to approximate the table. Can't be more explicit. [[Special:Contributions/172.69.226.119|172.69.226.119]] 06:36, 31 July 2018 (UTC)
What confuses me is that even at 40% humidity the heat index is a lot hotter than the actual temperature. If 110 degrees at the lowest humidity that occurs commonly feels like 130 degrees, then what does it mean to feel like 110 degrees?[[User:Probably not Douglas Hofstadter|Probably not Douglas Hofstadter]] ([[User talk:Probably not Douglas Hofstadter|talk]]) 15:46, 31 July 2018 (UTC)
: 40% humidity is not a common level for places that typically reach 110f. For Phoenix, AZ, one of the few places that can reach both 110f and 40% humidity during the North American Monsoon, which is a small fraction of the summer, this is dealt with by nearly every indoor area being air conditioned, both to cool the air and to remove humidity. So, what it means for the "typical" 110f is what it feels like standing in front of your oven, rather than in front of a dishwasher on the drying cycle. And yes, 110 and 40% humidity is a severe weather event, and the National Weather Service routinely issues heat advisories and warnings in July and August. [[Special:Contributions/172.68.47.36|172.68.47.36]] 23:59, 22 August 2018 (UTC)

Ironically, it is actually when humidity is at 100% (your sweat can't evaporate) that you feel the actual temperature. The lower humidity makes you feel cooler than the actual temperature. Similarly the windier it is (in cold weather) the more body heat is removed and the closer the actual temperature is to what it feels like.
[[Special:Contributions/162.158.62.141|162.158.62.141]] 21:31, 2 August 2018 (UTC)

I don't think it's accurate that "Human skin does not directly detect temperature - only the rate of heat gain or loss." Isn't it more that skin temperature is a dynamic equilibrium between the body's internal temperature and heat loss? I.e., skin feels colder in cold water than cold air because its equilibrium temperature is lower with faster heat loss? Also, is skin temperature even relevant here, or is it more about core temperature? [[User:JohnWhoIsNotABot|JohnWhoIsNotABot]] ([[User talk:JohnWhoIsNotABot|talk]]) 18:11, 3 August 2018 (UTC)

Could "add a few more degrees" be a pun on degrees of freedom, i.e. adding more variables to a meteorologist's model for heat index until it matches human perception closely enough? --[[Special:Contributions/172.68.133.180|172.68.133.180]] 22:23, 30 August 2018 (UTC)

1819: Sweet 16

2017-04-03T18:49:41Z

172.68.133.180:

{{comic
| number = 1819
| date = April 3, 2017
| title = Sweet 16
| image = sweet_16.png
| titletext = Every year I make out my bracket at the season, and every year it's busted before the first game when I find out which teams are playing.
}}

==Explanation==
{{incomplete|Explain individual markings, explain title text}}
{{w|March Madness}}, with its championship on the day this comic was published, features 68 basketball teams in an elimination bracket. In this comic however, the final 16 (two rounds), called "Sweet 16", are not given as actual names, but as descriptions of the odd circumstances of each team. For example, the first team is "a school with a dog on their team", a reference to {{w|Air Bud}}. The team descriptions become increasingly bizarre, comprising varied sports and pop culture references and and often building on and playing off of previous team descriptions.

The first four teams on the left are comprised partially or completely of pets.

The next two teams consist of some form of baseball-basketball crossover.

The bottom two teams on the left feature developers and players of NBA 2k17, a basketball video game by 2K Games.

The first team on the right, the 1988 LA Lakers is an actual NBA team. They are paired against a team of four kindergarteners and current Cleveland player Lebron James (born 1984), who was also a kindergartner in 1988.

The next two teams feature basketball-boxing crossovers.

The bracket after that features teams on unconventional mobility aids, Segways and stilts.

The final two teams are Cinderella teams. A Cinderella story is when a weak team works hard to achieve success. The final team consists of players wearing glass slippers, often a part of the Cinderella fairy tale.

Related to [[1529: Bracket]]

==Transcript==
:[The comic shows a direct elimination bracket (a single-elimination tournament): there is a single match played by every pair of teams, and the winners of those matches are paired up for the next round of matches, this continues until there are no more matches to be played. There are sixteen teams described here (hence the number in the title), eight on each side of the empty rectangle in the middle. Every two teams are connected, these connectors are then also connected, these connectors are yet again connected, and a final pair of connectors, after making one counter-clockwise right angle turn, end up in the top and bottom edges of the central rectangle. The bracket is empty, no results of any of the matches are indicated.]

:{| class="wikitable" style="background:transparent;border:none;width:100%;"
| style="background:transparent;border:none;" |
 [These are paired.]
 A school with a dog on their team
 A school whose team is entirely dogs

 [These are paired.]
 A dog team with one human
 A dog team with one cat

 [These are paired.]
 A baseball team playing basketball
 A basketball team with baseball gear

 [These are paired.]
 NBA2K17 top players
 NBA2K17 top developers

| style="background:transparent;border:none;" |
 [These are paired.]
 The 1988 Los Angeles lakers
 Four kindergarteners and Lebron James

 [These are paired.]
 Boxers playing basketball
 Basketball players in boxing gloves

 [These are paired.]
 A team playing on stilts
 A team playing on Segways

 [These are paired.]
 A bad team that would make a good Cinderella story
 A good team playing in glass slippers

|}

{{comic discussion}}