explain xkcd - User contributions [en]

1433: Lightsaber

2022-06-28T19:19:39Z

172.68.133.65: Undo revision 287798 by 172.68.133.65 (talk)

{{comic
| number = 1433
| date = October 13, 2014
| title = Lightsaber
| image = lightsaber.png
| titletext = A long time in the future, in a galaxy far, far, away, astronomers in the year 2008 sight an unusual gamma-ray burst originating from somewhere far across the universe.
}}

==Explanation==
This comic references a [http://www.youtube.com/watch?v=WDnoczxzQyg scene] from the third theatrically-released ''{{w|Star Wars}}'' movie, ''[[wikia:c:starwars:Return of the Jedi|Return of the Jedi]]'', wherein [[wikia:c:starwars:Darth Vader|Darth Vader]] confronts his son, [[wikia:c:starwars:Luke skywalker|Luke Skywalker]], who had recently surrendered to [[wikia:c:starwars:Galactic Empire|Imperial]] soldiers. In the movie, Vader notes that Luke has constructed [[wikia:c:starwars:Luke Skywalker's lightsaber|a new lightsaber]] following the loss of his [[wikia:c:starwars:Luke skywalker#Lightsabers|original]] during their [[wikia:c:starwars:Duel on Cloud City|duel on Cloud City]] (Luke Skywalker's original lightsaber actually having been [[wikia:c:starwars:Anakin skywalker|Anakin Skywalker's]] second).

Lightsabers are often jokingly referred to as "laser swords" by fans (note that the official French-language translation of Star Wars actually calls them "laser sabers"), and this comic points out that a real laser would not have any way of stopping and would therefore continue forever, making this particular interpretation silly. (The ''Star Wars'' writers cleverly fail to state what exactly a lightsaber's blade is made out of, although this point makes it unlikely to be a laser.) Once Darth Vader turns on the light saber, it goes offscreen and presumably continues in that direction forever, causing much mayhem as it blazes through the stars. Hull breaches are a popular trope in science-fiction, despite curiously being almost entirely absent from the Star Wars films.

The title text refers to {{w|GRB 080319B}}, an unusual gamma ray burst in 2008, the afterglow of which was briefly visible to the human eye. It implies that the source of this burst was a light saber in the Star Wars story, which took place "a long time ago in a galaxy far, far away" according to the {{w|Star Wars (film)|Star Wars}} {{w|Star Wars opening crawl|opening crawl}}.

Luke Skywalker and Darth Vader have had a similar conversation before in [[1397: Luke]]. In that version Luke wishes for Vader not to turn it on, as stated in the title text. He should probably have said this here in this comic!

==Trivia==
*In the comic, Vader's subordinates exclaim they are suffering a hull breach, implying they are on a spaceship (a Star Destroyer) or space station (the second Death Star). In the original movie, the conversation actually took place on the surface of Endor.

==Transcript==
:[Luke Skywalker and Darth Vader are talking. Vader holds the handle of a powered-off lightsaber.]
:Vader: '''''I see you have constructed a new lightsaber.'''''
:[Vader turns it on. The beam of the lightsaber continues upward out of the frame.]
:Lightsaber: Snap-Hisss
:[Vader looks up toward where the beam is pointing.]
:[Vader looks back at Luke.]
:Vader: '''''Where does it end?'''''
:Luke: Doesn't.
:Intercom (out of view): ''Hull breach all along sector five!!''

{{comic discussion}}
[[Category:Star Wars]]
[[Category:Physics]]

1433: Lightsaber

2022-06-28T19:19:20Z

172.68.133.65:

{{comic
| number = 1433
| date = October 13, 2014
| title = Lightsaber
| image = lightsaber.png
| titletext = A long time in the future, in a galaxy far, far, away, astronomers in the year 2008 sight an unusual gamma-ray burst originating from somewhere far across the universe.
}}

==Explanation==
This comic references a [http://www.youtube.com/watch?v=WDnoczxzQyg scene] from the third theatrically-released ''{{w|Star Wars}}'' movie, ''[[wikia:c:starwars:Return of the Jedi|Return of the Jedi]]'', wherein [[wikia:c:starwars:Darth Vader|Darth Vader]] confronts his son, [[wikia:c:starwars:Luke skywalker|Luke Skywalker]], who had recently surrendered to [[wikia:c:starwars:Galactic Empire|Imperial]] soldiers. In the movie, Vader notes that Luke has constructed [[wikia:c:starwars:Luke Skywalker's lightsaber|a new lightsaber]] following the loss of his [[wikia:c:starwars:Luke skywalker#Lightsabers|original]] during their [[wikia:c:starwars:Duel on Cloud City|duel on Cloud City]] (Luke Skywalker's original lightsaber actually having been [[wikia:c:starwars:Anakin skywalker|Anakin Skywalker's]] second).

Lightsabers are often jokingly referred to as "laser swords" by fans (note that the official French-language translation of Star Wars actually calls them "laser sabers"), and this comic points out that a real laser would not have any way of stopping and would therefore continue forever, making this particular interpretation silly. (The ''Star Wars'' writers cleverly fail to state what exactly a lightsaber's blade is made out of, although this point makes it unlikely to be a laser.) Once Darth Vader turns on the light saber, it goes offscreen and presumably continues in that direction forever, tearing through the hill of Vader's spaceship (in the original movie this scene actually took place on a planet) and causing much mayhem as it blazes through the stars. Hull breaches are a popular trope in science-fiction, despite curiously being almost entirely absent from the Star Wars films.

The title text refers to {{w|GRB 080319B}}, an unusual gamma ray burst in 2008, the afterglow of which was briefly visible to the human eye. It implies that the source of this burst was a light saber in the Star Wars story, which took place "a long time ago in a galaxy far, far away" according to the {{w|Star Wars (film)|Star Wars}} {{w|Star Wars opening crawl|opening crawl}}.

Luke Skywalker and Darth Vader have had a similar conversation before in [[1397: Luke]]. In that version Luke wishes for Vader not to turn it on, as stated in the title text. He should probably have said this here in this comic!

==Trivia==
*In the comic, Vader's subordinates exclaim they are suffering a hull breach, implying they are on a spaceship (a Star Destroyer) or space station (the second Death Star). In the original movie, the conversation actually took place on the surface of Endor.

==Transcript==
:[Luke Skywalker and Darth Vader are talking. Vader holds the handle of a powered-off lightsaber.]
:Vader: '''''I see you have constructed a new lightsaber.'''''
:[Vader turns it on. The beam of the lightsaber continues upward out of the frame.]
:Lightsaber: Snap-Hisss
:[Vader looks up toward where the beam is pointing.]
:[Vader looks back at Luke.]
:Vader: '''''Where does it end?'''''
:Luke: Doesn't.
:Intercom (out of view): ''Hull breach all along sector five!!''

{{comic discussion}}
[[Category:Star Wars]]
[[Category:Physics]]

1167: Star Trek into Darkness

2022-06-23T20:24:59Z

172.68.133.65: /* Explanation */

{{comic
| number = 1167
| date = January 30, 2013
| title = Star Trek into Darkness
| image = star_trek_into_darkness.png
| titletext = Of course, factions immediately sprang up in favor of '~*~sTaR tReK iNtO dArKnEsS~*~', 'xX_StAr TrEk InTo DaRkNess_Xx', and 'Star Trek lnto Darkness' (that's a lowercase 'L').
}}

==Explanation==

The talk page of a Wikipedia article is used to discuss changes to the article. An {{w|Wikipedia:Edit warring|edit war}} is a dispute about a specific edit to an article, manifesting as a series of edits alternating between making and reverting the change, and usually accompanied by a more-or-less heated debate on the talk page.

Here, [[Randall]] is referring to a dispute on the Wikipedia article about ''{{w|Star Trek Into Darkness}}'' (an upcoming {{w|Star Trek}} film at the time of the comic's posting). On the day before the comic was published, the article name had a lowercase "into", and the talk page looked [http://en.wikipedia.org/w/index.php?title=Talk:Star_Trek_Into_Darkness&oldid=535542349 like this] (rounded off in a friendly way, with the posting of {{w|User:Frungi/Star Trek Into Darkness capitalization|a summary of the arguments}}, and an exchange of virtual hugs). In summary, the debate centers around whether "Into Darkness" should be treated as a prepositional phrase (as in "Star Trek[king] Into Darkness") or an unpunctuated subtitle (as in "Star Trek[:] Into Darkness"), whether compound prepositions like "into" should be capitalized in titles, and whether the capitalization of the title in the movie's official promotional material is relevant. The intensity and multiple facets of a debate over one tiny letter is apparently entertaining to Randall.

[[Cueball]] changes the title to "~*~ StAr TrEk InTo DaRkNeSs ~*~" so that every other letter is capitalized, and the title as a whole is framed by tildes and asterisks (a common, but childish and ugly way of emphasizing titles online). This is a particularly silly compromise wherein the title is so obviously wrong, both sides will actually agree on something (either agree that Randall's title is wrong or that Randall's title is an acceptable middle ground).

The title text indicates Randall's belief that such arguments are perpetual and will always arise. He suggests that the edit to the Wikipedia page will result in a dispute over variants of Cueballs [[:Category:Compromise|"compromise"]]. One new alternative has the letter cases switched (or shifted, depending on your perspective), one uses a different set of "bracketing" characters (xX_[...]_Xx instead of ~*~[...]~*~), and one uses the original title, but with a lowercase "L" instead of a capital "I" (which appear similar in many fonts).

Alternating-case text later caught on as [https://knowyourmeme.com/memes/mocking-spongebob an internet meme] in 2017 (four years after this comic strip was published) for representing a mocking tone.

[[Megan|Megan's]] line of "They should have sent a poet." is a quote from the film ''{{w|Contact (1997 American film)|Contact}}''. The quote is also referenced in [[482: Height]]. In the movie, the line was meant to convey that only a poet could adequately capture the beauty seen; here, it indicates that prose is insufficient to capture the ironic beauty of the edit war.

The old "favorite edit war" might be the one referenced in the title text of [[878: Model Rail]] or the one resulting from the addition of the [[739: Malamanteau]] article to Wikipedia

==Transcript==
:[Cueball staring at computer screen.]
:Cueball: Oh, ''wow.'' Look at Wikipedia's Talk page for '''''Star Trek into Darkness.''''' I have a new favorite edit war.
:Megan (off-panel): Oh?

:Cueball: Forty ''thousand'' words of debate over whether to capitalize "into" in the movie's title. Still no consensus.
:Megan: That's ''magnificent''.
:Cueball: It's breathtaking.
:Megan: They should have sent a poet.

:Cueball: Well, I'm making an executive decision. I hope both sides accept this as a fair compromise.

:[A Wikipedia page titled "''~*~ StAr TrEk InTo DaRkNeSs ~*~''"]

==Trivia==
After the publication of the comic, the debate continued with full force, complete with {{w|Talk:Star Trek Into Darkness/Archive 5#xkcd Mention|a section of xkcd-inspired suggestions}}. The article itself was soon protected, so that only administrators could edit it. A day later, the title was changed to one including a capital "Into" by the administrator {{w|User:Mackensen|Mackensen}}. (The debate continued on {{w|User talk:Mackensen/Archive20#Star Trek into Darkness move|his talk page}}.) https://en.wikipedia.org/wiki/~*~_StAr_TrEk_InTo_DaRkNeSs_~*~ was a valid redirect link for quite some time, having not been deleted when {{w|Wikipedia:Redirects for discussion/Log/2015 January 25#~*~ StAr TrEk InTo DaRkNeSs ~*~|requested in 2015}}, but {{w|Wikipedia:Redirects for discussion/Log/2016 May 23#~*~ StAr TrEk InTo DaRkNeSs ~*~|2016}}.

{{w|The Independent}} published an article about the "[http://www.independent.co.uk/arts-entertainment/films/news/trekkies-take-on-wikis-in-a-grammatical-tizzy-over-star-trek-into-darkness-8475705.html grammatical tizzy]", and the affair as a whole was added to Wikipedia's humorous list of the {{w|WP:Lamest edit wars|lamest edit wars}}.

{{comic discussion 1167}}

[[Category:Comics featuring Cueball]]
[[Category:Comics featuring Megan]]
[[Category:Star Trek]]
[[Category:Wikipedia]]
[[Category:Compromise]]

Talk:2634: Red Line Through HTTPS

2022-06-21T01:27:58Z

172.68.133.65: comment

HTTPS was standardized in 2000 or so, so 2015 is quite a stretch for a site to not use it because the site was last updated before HTTPS was widely available.
With pretty much any browser now, a red line through HTTPS means that the site _is using HTTPS_, but it is _not trusted by the browser_ (due to e.g. the certificate being self-signed or expired).
[[User:Darrylnoakes|Darrylnoakes]] ([[User talk:Darrylnoakes|talk]]) 04:28, 18 June 2022 (UTC)

:I think the intended joke is that the site's certificate expired in 2015, instead of the site is not using HTTPS. [[Special:Contributions/108.162.221.101|108.162.221.101]] 06:29, 18 June 2022 (UTC)

:2015 is when the first Let's Encrypt certs were issued, and 2016 is when LE became generally available to the public and thus when free SSL/TLS became very very easy for just about anyone setting up a web server, hence the comic citing 2015. However even with a valid cert you might have a number of issues, like [https://www.mixedcontentexamples.com/ mixed content]. At least in Firefox, an expired cert gives a big warning screen that gives you an option to add a security exception; I don't care enough to install Chrom{e,ium} to test its UI. [[Special:Contributions/172.69.69.250|172.69.69.250]] 08:30, 18 June 2022 (UTC)

::Chrome has this warning screen including an option to bypass the warning as well. I believe all browsers do. I think the only exception to this is when a site has strict transport security enabled. [[User:Jespertheend|Jespertheend]] ([[User talk:Jespertheend|talk]]) 10:49, 18 June 2022 (UTC)

:::Until about 2015 no-one complained if you didn't offer HTTPS as long as you didn't request anyone's credit card number or offered .exe files: An internet site offers nothing but inherently untrustable text. It might contain ads that can execute any piece of javascript. It even could contain flash - so why pay a substantial amount of money to make the transport of that data more secure? Nowadays most web browsers tell on you if you don't secure connections and allowing the telco to see what data you download from where is felt as a privacy intrusion. On the other side not every hoster offers https for multiple domains...--[[User:Gunterkoenigsmann|Gunterkoenigsmann]] ([[User talk:Gunterkoenigsmann|talk]]) 15:03, 19 June 2022 (UTC)

Not sure it's true that if there is a problem with HTTPS like an expired cert that the connection is made with HTTP instead. [[Special:Contributions/172.69.79.201|172.69.79.201]] 10:11, 18 June 2022 (UTC)

:It's not, it still uses the https connection. It only indicates that the connection might not be secure anymore and anyone could be listening in at that point. [[User:Jespertheend|Jespertheend]] ([[User talk:Jespertheend|talk]]) 10:49, 18 June 2022 (UTC)

I actually am bemused by this. Not sure if I only visit the wrong (or right?) websites with the wrong (or right?) browsers, but I don't recall ever notably having seen struck-red links. (Perhaps I have, and assumed it was a site informing me that they were dead links, not now followable?) I ''do'' occasionally follow a normal-looking link (maybe locally CSSed in a over-riding manner of format?) and I get the browser load up a whole-screen "Problem with certificate (Are you sure? Jump through hoops for me to progress.)" which I may then take under considered advisement but mostly has me checking I'm not being spoofed as to the destination or something. Is this where the red strikethrough appears for others?
 I also have at least one site that is steadfastly still HTTP-only, and neither I nor my various browsers have any problem with it as I know what I'm doing, whilst the browsers just go there without particular complaint or anything more than usual addressbar clues... I might have "added to exception from warning" once or twice in the distant past, but not in every case. So I'm learning something here, but I don't know what. Sounds like something Edge would do, but I don't use Edge... I'm generally on Chrome, Firefox and a handful of 'lesser' flavours, all definitely updated. [[Special:Contributions/172.70.90.173|172.70.90.173]] 11:21, 18 June 2022 (UTC)

:You can find some examples of the red line on https://badssl.com/, but pretty much in all cases you get a full page warning first that something is amiss. You can also try out the http connection at http://http.badssl.com/, http connections are a bit more complicated. Some browsers don't show a warning at all, while others only show a gray 'insecure' label in front of the url. And as can be seen here [https://blog.chromium.org/2017/04/next-steps-toward-more-connection.html], the plan is to eventually show similar warnings for HTTP sites as what is currently shown for HTTPS sites with a failed certificate. [[User:Jespertheend|Jespertheend]] ([[User talk:Jespertheend|talk]]) 11:32, 18 June 2022 (UTC)
::Ugh, I'd hate that. I have a little webpage of my own, and I'm not in a position to be able to go https, :( That "badssl" site has several example issues, which ones go red/strikethrough? I want to confirm no browser I have does that. [[User:NiceGuy1|NiceGuy1]] ([[User talk:NiceGuy1|talk]]) 04:56, 19 June 2022 (UTC)

:I was about to remark the same thing, :) NEVER seen a strikethrough. I'm rather assuming it's something Chrome does, because I about exclusively use Firefox, and Chrome likes to be weird and non-standard (main reason I generally don't use it), and too many people act like there's no other browser than Chrome. Likewise, most I get is "Security Risk!", then find out it's a Bad Certificate, then it turns out it expired and they just haven't updated it yet. Stop being so dramatic, LOL! [[User:NiceGuy1|NiceGuy1]] ([[User talk:NiceGuy1|talk]]) 04:28, 19 June 2022 (UTC)
::I'm a Chrome user (part of the time, being the "handful of lesser flavours" contributor, above, but using it this very second) and I don't see it. But then I turned off its look-ahead (downloading of pages it thinks I'll go to next) because I'd rather it not, and as some sort of pre-emptiveness seems necessary to know a link ''should'' be red-struckthrough, I probably (hopefully?) neutered that stupid potential exploit too... So don't take my experience as gospel. (But still sounds like an Edge thing, to me, the way that's the new IE in the current browser ecosystem.) [[Special:Contributions/172.70.162.5|172.70.162.5]] 11:32, 19 June 2022 (UTC)
:::It's not links (to other pages) that get the strikethrough. It's the protocol/scheme name in the current page's address bar. See, for example, the picture in https://superuser.com/a/369839/93954. This is far less intrusive than any of the warning pages you've mentioned seeing; maybe you just haven't noticed when it does that? For a current live example, in Edge, I'm seeing the (not red) strikethrough e. g. on https://self-signed.badssl.com/ both on the warning page and after clicking through it to accept the bad certificate. And as it happens, I could swear that just within the last few days I've been on a mixed-content website that displayed the strikethrough, but I'm not certain what website it was and I can't reproduce this now, so I'm probably misremembering. [[User:Chortos-2|Chortos-2]] ([[User talk:Chortos-2|talk]]) 23:44, 20 June 2022 (UTC)

I've made a rather large change to the page to better explain the meaning of a red line through https. I removed any mentioning of using the HTTP protocol as that is incorrect. If a browser uses the HTTP protocol it is shown in the url using 'http://'. Since the comic was talking about a red line through 'https' I'm assuming the usage of the HTTP protocol is unrelated here.
Though it's possible I removed some more information from the page that might still be desired. Such as the mentioning of AI-generated spam sites and man in the middle attacks. These seemed redundant to me for explaining the joke.
I also put some more emphasis on the red line usually meaning that something bad is going on. Browser venders put a lot of effort in security, and having everyone think that a red line is not that big of a problem is the last thing they'd want. [[User:Jespertheend|Jespertheend]] ([[User talk:Jespertheend|talk]]) 11:23, 18 June 2022 (UTC)

While it's true that some browser security warnings are false alarms, I think that paragraph is missing the point of the comic. Cueball is assuming that any site that's been around for years must be operated well. But often the maintainers of the site get complacent and don't update to newer standards. And even if the real site is legit, the security warning can mean that traffic has been intercepted, so you're not actually going to the real site. [[User:Barmar|Barmar]] ([[User talk:Barmar|talk]]) 13:40, 18 June 2022 (UTC)
: Also, someone who hasn't taken the trouble to keep their security certificates up to date is probably more likely to have neglected their server security generally, so it's more likely that someone could have hacked them and be serving you up all kinds of crap. [[Special:Contributions/172.70.85.177|172.70.85.177]] 08:22, 20 June 2022 (UTC)

I presumed this was about using outdated protocols like TLS 1.0 or weak ciphers. [[Special:Contributions/172.70.110.121|172.70.110.121]] 00:28, 19 June 2022 (UTC)

You'd almost think Randall didn't live in the Boston metropolitan area. I was disappointed. [[User:JohnHawkinson|JohnHawkinson]] ([[User talk:JohnHawkinson|talk]]) 04:30, 19 June 2022 (UTC)

Okay, at least two of us don't see this behaviour, so this is NOT as universal as Randall seems to think, could somebody figure out why and put it in the explanation? (I reject the possibility that we just haven't visited the right (wrong) sites. I, for one, go to WAY too many sites, LOL!). My leading theory is that instead of being universal, this behaviour is actually unique to Chrome (as I don't use it much and can easily have never visited an insecure website on it), since I use Firefox primarily, and many people seem to forget that there are other browsers than Chrome, and Google goes out of it's way to be as weird as possible, including being fancy for the sake of fancy (like the colour-coding and strikethrough). [[User:NiceGuy1|NiceGuy1]] ([[User talk:NiceGuy1|talk]]) 04:49, 19 June 2022 (UTC)

Where is Cueball saying that websites with a red line through HTTPS are more secure than modern websites? In the comic he merely says that the red line means that the website is legit, he doesn't make any comparison at all. [[User:Kzkzb|Kzkzb]] ([[User talk:Kzkzb|talk]]) 22:12, 19 June 2022 (UTC)

I think the current explanation is missing a key aspect of the humor. The fact is, it takes minutes to add HTTPS to your site for free (see e.g., https://www.freecodecamp.org/news/free-https-c051ca570324/). A phisher could set up a site with https and have it trick you into giving up your info for a while before being caught and brought down. I think the outdated-ness of the red line through the https indicates that the site has been around for a long time, and therefore is less likely to be a scam. I'll add something small to this effect, but let me know if you disagree, I'm not 100% sure about this. [[User:Jrfarah|Jrfarah]] ([[User talk:Jrfarah|talk]]) 23:04, 19 June 2022 (UTC)

:While you can set up HTTPS certificate for free in minutes, you need to have control over the domain to be able to. This is key aspect in the security - only I can control my domain, therefore if you see green HTTPS on my website, you can be sure it is a genuine one, whereas if you see anything else, it might not be [[Special:Contributions/89.177.163.36|89.177.163.36]] 16:43, 20 June 2022 (UTC)
::Aside from the issue of a previously controlled+certificated domain being hijacked... As far as I'm concerned a <code>style="text-color: green"</code> sort of thing would suffice to produce the exact same effect.
::Nobody has yet satisfactorily explained ''which'' browsers do this, and under ''which'' circumstances... No Chrome doesn't do this. (Not my Chrome, anyway, but maybe I'm just using the wrong one?)
::But, for when it ''does'' happen, does it not override inline/CSS styles, in which case the link 'warning' is entirely disguisable by the link-author. Even in the most incapable and hobbled version of newb-servicing CMS, and definitely with direct markup-editing capability.
::Or they do, in which case (not that I have much sympathy for the absolutist type) I hear the wailings of a thousand web-designers, unable to control every last visual element to their utter and complete desire because the browser spoils their desired pallette, even if they overlook the mythical strikethrough rendering.
::(The amateur web designer I knew who set up a pixel-perfect site by making the page he desired an ''image'' with ''image-mapped'' hotspot-links on the blue-underlined fully rasterised words... It sounds like he would have neutered the HTTPS warning. But in the most annoying and frustrating way.)
:: I assume it's a common sight for Randall, to have inspired him so (and write about it as if we should similarly have a good idea about it). For me, though, I assumed it was a broken-link thing, i.e. a non-available web resource, but then of course a page/site that is entirely offline cannot be so easily hacked. But I take it on trust that the current explanation (as far as it goes) is the real one. [[Special:Contributions/172.70.91.58|172.70.91.58]] 22:37, 20 June 2022 (UTC)
::: No, this isn't rendered on the page. Go to https://badssl.com/ yourself and you'll see you can't use CSS to change how the https is rendered red with strikethrough in the address bar. But I see Chrome use the red strikethrough display while Firefox doesn't, instead showing "Not Secure" next to the security icon.

Removed unnecessary line. The NSA is mentioned absolutely nowhere in the comic, nor any other intelligence agency, and it comes off as nothing more than an unnecessary conspiracy theory.

What if Randall decides to delve into the mysteries of the unlocked padlock? WE NEED A CONTINGENCY PLAN! [[Special:Contributions/172.68.133.65|172.68.133.65]] 01:27, 21 June 2022 (UTC)

2409: Steepen the Curve

2022-05-04T00:20:26Z

172.68.133.65: Undo revision 235606 by X. K. C. D. (talk)

{{comic
| number = 2409
| date = January 8, 2021
| title = Steepen the Curve
| image = steepen_the_curve.png
| titletext = 1. Flatten the curve. 2. Steepen the curve. 3. Hang out.
}}

==Explanation==
This comic is another in a [[:Category:COVID-19|series of comics]] related to the {{w|COVID-19 pandemic}}.

In early 2020, the COVID-19 pandemic rapidly became the main public concern. The virus spread at an exponential rate before initial lockdowns started to reduce the trajectory for a time. The graphic drawn in black depicts exponential growth in the measure of deaths — though it is not clear (without proper units or values on either axis) if this is because it is a cumulative count of deaths or the rate of deaths per day. Such graphs were common in the spring of 2020, enough that Randall has previously parodied them in [[2294: Coronavirus Charts]]. These graphs often showed future projections that compared continued exponential growth vs. curves that did not grow as fast, or even flattened out. Governments around the world realized that if the trend was to continue healthcare services would become overwhelmed, thus all kinds of political, civic and personal efforts were put towards doing things that would cause the 'curve' to flatten and not rise as rapidly as it would do unchecked. "Flatten the curve" thus became the rallying cry for all measures taken to reduce the spread of the virus.

In 2021, the pandemic is ongoing (with second or even third 'waves' of resurgence affecting some populations that had temporarily flattened the curve) but now we have a handful of vaccines available. In [[2278: Scientific Briefing]], [[White Hat]] remarked that many scientific briefings use similar or identical charts, but in this briefing, a chart from the beginning of the pandemic is reprinted verbatim and then crudely updated with red ink. The red overlay intends to update the 'original' graphic to portray the number of vaccines provided (again, it could easily be either cumulative or rate-wise). With the change to what is represented, the line remains the same but the hoped-for outcome is changed accordingly. Making the curve steeper represents getting more people vaccinated faster.

In both cases, there would be an upper limit on the cumulative value, but the ceiling must be well beyond the upper limits (x and y axes) of this graph. If this is a rate-graph, it would show a peak and subsequent decline at the same point in time where a cumulative graph would show an inflection in its gradient, but neither are visible here.

Additionally, the analogy between the number of deaths and the number of vaccinated people could be considered as questionable, as the number of deaths in the initial stages of a pandemic is expected to follow an exponential law, whereas the same cannot be said for the number of vaccinated people.

The title text gives a summary of the overall goal. Flatten the curve (of infections/deaths), Steepen the curve (of vaccinations/immunizations), Hang out. We've done the first, we're starting the second... and the third is where we can (hopefully) all hang out together again, in person, without masks or social distancing. But we have to finish the first two steps successfully to get to the third one.

==Transcript==
:[Line graph shown with a rising curve drawn in black. There is an underlined label above and another label below the graph. The Y-axis line is ending in an arrowhead and also has a label. All this is in black. But the last number in the upper label as well as one word in each of the other two labels, have been scribbled out in red and then another number or word has been written behind or beneath in red.]
:[Caption above the graph:]
:202<s>0</s> 1

:[Y-Axis:]
:COVID <s>Deaths</s> Vaccinations

:[Caption below the graph:]
:<s>Flatten</s> Steepen The Curve

{{comic discussion}}

[[Category:Comics with color]]
[[Category:Line graphs]]
[[Category:COVID-19]]

2247: Weird Hill

2022-05-04T00:20:05Z

172.68.133.65: Undo revision 235597 by X. K. C. D. (talk)

{{comic
| number = 2247
| date = December 27, 2019
| title = Weird Hill
| image = weird hill.png
| titletext = I'm compromising by picking a weird hill to lie on.
}}

==Explanation==
This comic is a joke about the expression [[wikt:hill to die on|"a (weird) hill to die on"]], which refers to holding a position as if it has great importance, and being willing to fight for that position, no matter how much opposition you face, or how little benefit is derived. The term comes from the military practice of capturing and holding hills in disputed areas, in order to command the high ground. Because hills tended to be highly disputed, soldiers would frequently die in their defense. Hence picking "a hill to die on" implies that you're choosing a position that you consider to be so important that you'd defend it at the cost of your own life. The term is generally used to point out the pointlessness of defending a rhetorical position with such fervor, particularly if the point is not especially important, and/or the other party is unlikely to change their views.

In this strip, [[Beret Guy]] interrupts [[Cueball]], who is apparently arguing with [[Duty Calls|someone who is wrong on the Internet]]. Pulling him away from the argument, Beret Guy asks why Cueball should pick a weird hill to die on (fight over an opinion online) when he could pick a soft hill to lie on, going out into nature and relaxing. This comic has a similar message to [[386: Duty Calls]], [[1731: Wrong]], and [[2051: Bad Opinions]]. The theme is sometimes we either assign too much importance to our opinions, or we expend too much effort trying to persuade others, and it's often wiser to simply let the argument go. Leaving a computer problem to relax in nature was also mentioned in [[1024: Error Code]].

The title text is an absurd juxtaposition: that Cueball will pick a weird hill to lie on. In this case, he may be referring to a physical hill, in which case the meaning of "weird" is unclear due to lack of context.

The phrase "a weird hill to die on" was also featured in [[1717: Pyramid Honey]]. (Normally the expression is just "a hill to die on".)

==Transcript==
:[Cueball, frustrated, is sitting on a chair in front of a computer and Beret Guy pulling the chair back]
:Computer: *!$@
:Beret Guy: Why pick a weird hill to die on...

:[Cueball gets up, still frustrated]
:[Cueball and Beret Guy leave the room]

:[Cueball and Beret Guy climbing a hill]

:[Cueball and Beret Guy lying down at the top of a hill]
:Beret Guy: ... when you could pick a soft hill to lie on?
:Cueball: This ''is'' nice.

==Trivia==
* A quick Internet search does not indicate the existence of a properly-named "Weird Hill" on which Cueball could lie{{Citation needed}}, but there is a public park in Massachusetts called {{w|Weir Hill}}. Weir Hill's landscape is a weird patchwork, including several threatened species, because it was used for different agricultural purposes by the Algonquin and then European settlers and American farmers before becoming a park in the 1960s.

{{comic discussion}}

[[Category:Comics featuring Cueball]]
[[Category:Comics featuring Beret Guy]]
[[Category:Puns]]

2235: Group Chat Rules

2022-05-04T00:19:39Z

172.68.133.65: Undo revision 235583 by X. K. C. D. (talk)

{{comic
| number = 2235
| date = November 29, 2019
| title = Group Chat Rules
| image = group_chat_rules.png
| titletext = There's no group chat member more enigmatic than the cool person who you all assume has the chat on mute, but who then instantly chimes in with no delay the moment something relevant to them is mentioned.
}}

==Explanation==
In this comic Randall is outlining the rules of a group chat, such as {{w|Internet Relay Chat}} (IRC), {{w|Slack (software)|Slack}}, {{w|Discord (software)|Discord}}, {{w|WeChat}}, {{w|Discourse (software)|Discourse}}, and the like.

1. '''Once you've sent a typing notification, you have to say ''something,'' c'mon.'''

Typing notification, often called a "typing awareness indicator," is a feature of some instant messaging systems, showing a message such as "Typing..." with the typer's name to the other participants, causing them in many cases to wait to receive the message before typing something of their own. When the typer stops without sending anything, this can seem anticlimactic and potentially disruptive if it recurs. Randall's rule is that you must say something once you've started typing, to avoid the awkwardness of awaiting a person's reply. See also [[1886: Typing Notifications]].

2. '''Show you care by trimming the tracking junk off links you paste.'''

Some URL links may have tracking information attached to the end of them, to show the origin of the URL and other information. {{w|UTM parameters}} are an example of URL parameters (the part of a URL starting with a question mark) which are used to track utilization of the URL from one user to another. Many news and marketing-related websites include such tracking codes with any visit to one of their web pages in an attempt to see the source of the URL for subsequent visits. Many people consider this a violation of privacy as well as a source of clutter, and make an effort to remove the parameters from URLs when they are not necessary for obtaining the requested content. For example, [https://www.dyson.com/sticks/dyson-v8-absolute-nickel-iron.html?ranMID=36310&ranEAID=lw9MynSeamY&ranSiteID=lw9MynSeamY-w42lWd1QYp3RrUefCg_osA&siteID=lw9MynSeamY-w42lWd1QYp3RrUefCg_osA&utm_source=Slickdeals+LLC&utm_medium=affiliate&utm_campaign=us_en__na__na__na__purchase&utm_term=&utm_content=rakuten_1&dclid=CjkKEQiAt_PuBRC2vOSG5pnYqN0BEiQATx34W-U3rsbKLg-BO9ep4IJKz6JxmZrHTqS7JKmZqSrWmKLw_wcB&ranMID=36310&ranEAID=lw9MynSeamY&ranSiteID=lw9MynSeamY-z5miuzSsmyWevVXB._R14g&siteID=lw9MynSeamY-z5miuzSsmyWevVXB._R14g&utm_source=Slickdeals+LLC&utm_medium=affiliate&utm_campaign=us_en__na__na__na__purchase&utm_term=&utm_content=rakuten_1 this url] has a lot of tracking information to show that it was originally accessed from Slickdeals, which can be removed to produce [https://www.dyson.com/sticks/dyson-v8-absolute-nickel-iron.html a much shorter URL] for the same web page. Randall asks the users of group chat to politely remove the tracking code, though other parameters may be involved in an important non-tracking way (such as the lat, lon and zoom level giving the focus of a Google Map link) and it isn't always obvious which parts are which - or both tied together!

3. '''Do not talk about ''Fight Club'' (1999).'''

This is a reference to the 1999 film ''{{w|Fight Club}}'', where the main character forms an eponymous "Fight Club," an underground club for men to fight recreationally. In [http://www.diggingforfire.net/FightClub/ the rules for Fight Club] the first and second "rules" are "You do not talk about FIGHT CLUB.", which Randall parodies in this comic, by making a rule to not talk about the film ''Fight Club'' and placing this rule third in the list. See also [[922: Fight Club]] and [[109: Spoiler Alert]].

4. '''There are two types of chats: those with a relevant group name, and those where the name is random nonsense that changes regularly. Only the second kind are good.'''

Some group chats frequently change the name of their title or the names of their channels, for example to reference upcoming events or inside jokes, or to reflect the topic of the current conversation. Often, these names do not get changed back until someone decides to change it to a new inside joke/etc. Randall claims that those are the only good kind, compared to those that never change group names, perhaps implying a singular focus is less interesting than a dynamic chat that often changes names.

5. '''When mentioning it elsewhere, always just refer to it as "the group chat" to create an aura of exclusive mystery.'''

Many people have to deal with several kinds of group chat in the same organization, so referring to "the group chat" within such an organization may be confusingly ambiguous. Also, calling a chat "the group chat" can serve to exclude those who don't already know about it.

6. '''Robert's Rules of Order are optional but encouraged.'''

''{{w|Robert's Rules of Order}}'' are one of the authoritative codifications of {{w|parliamentary procedure}} used to formalize decision-making in organizations required to document their activities such as governments and sometimes civic organizations and corporations. While people required to use ''Robert's Rules'' might use group chat to plan their {{w|Agenda (meeting)|agenda}} — even going so far as to prepare a {{w|pro forma}} script for a meeting in accordance with parliamentary procedure which represents their positions and deliberations in advance — and to compose, revise, and approve their {{w|minutes}}, it is unlikely that group chat participants would follow ''Robert's Rules'' prior to their formal meeting.

7. '''Periodically part of the group will split off to form a new chat with everyone minus one person. This is how group chats reproduce; don't draw attention to it.'''

Some people who use group chat too frequently or for unimportant messages or both will cause their colleagues to attempt to achieve greater productivity by excluding them from an alternate chat, from which notifications, for example, are less annoying and more useful. Alternatively, a person could be excluded from a chat to hide things from them, such as to plan a surprise for them, or because that one person has been disruptive or annoying to the point that everyone else wants to continue the conversation without their continued input. It appears that the chat is a [https://en.wikipedia.org/wiki/Swarming_(honey_bee) honey bee hive reproducing by swarming]. When purposely excluding someone by creating a new group, you would probably not want them to know you have done so as they might otherwise attempt to re-join in the new chat; that's likely the real reason one should not talk about or draw attention to the fact that it happened.

8. '''Since there's no algorithmic feed, the responsibility for injecting lots of garbage no one asked for falls on you.'''

Tools such as {{w|IFTTT}} and {{w|IRC bot}}s (or "bots" in this context) are used to provide group chat channels with information automatically taken from external sources of various sorts, such as emails to a support address or commits to source code control systems. Randall suggests that when such algorithmically-provided information is not available, it is incumbent upon chat participants to provide sufficiently verbose replacements. The "algorithmic feed" may also refer to the newsfeed type of systems that Facebook or other social networking sites use, to order posts for a user to view.

9. '''The enumeration, in these rules, of certain rights, shall not be construed to deny or disparage others retained by the people.'''

This is a reference to the {{w|Ninth Amendment to the United States Constitution}}, which reserves the various [[Wikipedia:natural rights|natural rights]] not specifically mentioned in the Constitution. Per Wikipedia, this right was included because "future generations might argue that, because a certain right was not listed in the Bill of Rights, it did not exist." The Ninth Amendment was also referenced in [[1998: GDPR]].

10. '''Sorry about all the notifications.'''

Here, Randall apologizes for all the notifications for the messages sent in group chat. Group chat features often result in more notifications than designers of notification systems anticipated or intended. If each of these ten rules were sent as a separate message in group chat, they might likely end with such an apology.

The title text expresses appreciation (and perhaps amazement) for group chat participants who remain silent except for promptly replying on topics pertinent to them.

==Transcript==
:[Title at the top of the comic]:
: Rules for this group chat

:[A numbered list of 10 rules]:

# Once you've sent a typing notification, you have to say ''something,'' c'mon.
# Show you care by trimming the tracking junk off links you paste.
# Do not talk about ''Fight Club'' (1999).
# There are two types of chats: those with a relevant group name, and those where the name is random nonsense that changes regularly. Only the second kind are good.
# When mentioning it elsewhere, always just refer to it as "the group chat" to create an aura of exclusive mystery.
# Robert's Rules of Order are optional but encouraged.
# Periodically part of the group will split off to form a new chat with everyone minus one person. This is how group chats reproduce; don't draw attention to it.
# Since there's no algorithmic feed, the responsibility for injecting lots of garbage no one asked for falls on you.
# The enumeration, in these rules, of certain rights, shall not be construed to deny or disparage others retained by the people.
# Sorry about all the notifications.

{{comic discussion}}

[[Category:Social interactions]]
[[Category:Social networking]]
[[Category:Fiction]]
[[Category:Fight Club]]

2461: 90's Kid Space Program

2022-05-03T07:55:46Z

172.68.133.65: I fixed the typos.

{{comic
| number = 2461
| date = May 10, 2021
| title = 90's Kid Space Program
| image = 90s_kid_space_program.png
| titletext = NASA may not want to admit it, but at this point they ARE the 90's Kid Space Program.
}}

==Explanation==
The "launch system" is just one of the {{w|Eye pepper|rubber pepper toys}} popular in the 1990s. These toys are little rubber hemispheres, about 1" (25 mm) in diameter and 1/8" (3 mm) thick. When turned inside-out and placed on a hard surface, they will, after a short wait, snap back to their original shape, popping up into the air. The joke is that kids who grew up with these toys will think they're a great idea to propel a space ship to orbit, when in fact the toys launch at mere tens of kilometers per hour, far short of the thousands needed to reach {{w|orbital speed}}{{citation needed}}. But now kids playing with these are those that make rockets, hence the title 90's Kid Space Program (KSP).

Even if the popper-based propulsion system could generate enough acceleration to reach orbit, the abrupt impulse would likely cause serious harm to any astronauts.

The title text implies that many working now at {{w|NASA}} were 90s kids. Both categories would include [[Randall]], as he was born in 1984 and previously worked at NASA.

The title is a reference to the {{w|Kerbal Space Program}} (KSP) which has been a [[:Category:Kerbal Space Program|recurring theme]] on xkcd, and it has previously been hinted at that NASA's employees uses this program in [[1244: Six Words]] and [[2204: Ksp 2]]. And also that you learn more about orbital Mechanics by using KSP than from being hired by NASA in [[1356: Orbital Mechanics]].

==Transcript==
:[A command and service module representing the tip of a spacecraft, is attached by four long trusses to four equidistant points on the edge of a giant light green pepper (a green "hill" with a round raised edge around it). The popper is in its inverted configuration, ready to pop. There is a caption beneath the panel:]
:The 90's Kid Space Program prepares for their first orbital launch

{{comic discussion}}

[[Category:Comics with color]]
[[Category:Space]]
[[Category:Kerbal Space Program]]